Rebooting issue after flashing the devel image

[TarotChen]

$ system-image-cli -i
current build number: 188
device name: krillin
channel: ubuntu-touch/devel-proposed/krillin.en
last update: 2015-08-31 03:03:51
version version: 188
version ubuntu: 20150830
version device: 20150821-736d127
version custom: 20150821-887-33-32-vivid

Steps to reproduce:
1.Connect DUT with PC
2.Flash with devel image
3.Observe the result

Actual result:
1.DUT failed to reboot after flashing the devel image
2.Sometimes DUT could reboot right after flashing, but it failed to rebooting again after restarting

Expected result:
Be able to reboot DUT successfully

Other info:
1.Error can reproduce on Arale, Mako as well
2.Long press "power" key doesn't help to reboot

[Evan Wang (wsy324)]

Boot loop issue still exists on latest devel image on all devices, Arale/Krillin/Mako, even if your were lucky enough to not meet the boot loop issue during wizard, it also could be caused very easily after wizard.

[Víctor R. Ruiz (vrruiz)]

I can reproduce the boot loop with ubuntu-touch/devel-proposed/krillin.en on mako. Steps to reproduce:

- ubuntu-device-flash touch --bootstrap --channel=ubuntu-touch/devel-proposed/krillin.en --wipe --device mako --developer-mode --password 1234
- Go through the wizard.
- After the wizard is finished, the device reboots.
- Boot loop: Ubuntu logo is shown during start, but then reboots.

[John McAleely (john.mcaleely)]

Can we test this on flo? For the builds either side of mako not working, can you test on flo? this may be a bug that is being seen differently between commercial devices and the archive devices.

[Dave Morley (davmor2)]

Flo is working. Arale on ubuntu works too however the minute you put arale on meizu.en you get the boot loop issue. Also the issue isn't triggered until you have entered into the System for the first time for me at least. To that end I would suggest the boot loop fault lies somewhere in the custom tarball.

[Jean-Baptiste Lallement (jibel)]

I believe this is fixed. The watchdog was causing the device to reboot when a service kept respawning. It was the case with espoo and location services.