yashsingh1/xdaforums huggingface dataset:
[One (M8) Android Development] xlightwaverx:
BlissRom Gerrit is up. If you find Patrick let him know, he's off the airwaves.
[One (M8) Android Development] TheKnux:
Anyone else getting a super long bootloop on latest nightly (12/9)? It's not even dimming the screen to let you know it's about to boot to the system.
[One (M8) Android Development] str8str:
Yes seems some are then it works fine
[One (M8) Android Development] riaan0010:
Yes I did, but booted for about 5secs and went back to bootloader
[One (M8) Android Development] fizbanrapper:
Thanks for all the feedback guys. ROM change keeps me from building tonight. Hopefully tomorrow night well be better.
[One (M8) Android Development] mcwups1:
I pulled it from the EXPERIMENTAL folder. It's still named NIGHTLY in the file though.

Sprint M8 Converted HK 4.25.654.14
[One (M8) Android Development] fizbanrapper:
Yeah I just noticed that myself. Sorry about that
[One (M8) Android Development] fBx:
So if I Flash a new Version my phone won't boot? Still on that 8/24 experimental with split trees.
[One (M8) Android Development] Mjduddin:
9/1 nightly boots without difficulty. Appreciate all the hard work by the developers/maintainers. They're awesome.
[One (M8) Android Development] Derodraaa:
still unable to flash latest ROM

Tried flashing the 9/1 build. Seemed fine for a few seconds then automatically booted into bootloader and stuck in bootloop when trying to get into system. I've extracted the recovery.log in the hope it gives some clues to where the problem lies. Good luck and appreciate the hard work.

HTC One M8 (Vodafone UK)
[One (M8) Android Development] fizbanrapper:
The log shows a nandroid, then you flashed some candy pack zip. That's it. :(
[One (M8) Android Development] mcwups1:
When my phone rings, I can't answer it. The screen doesn't turn on.

I am on the 8/9 build.

Sprint M8 Converted HK 4.25.654.14
[One (M8) Android Development] fizbanrapper:
Disable screen off gestures and ambient display.

If that doesn't help, freeze devicehandler and easy access service apps.
[One (M8) Android Development] fizbanrapper:
Does the reboot happen the second you flash the ROM? Or does it seem to get most of the way through? I'm wondering if it's flashing the system partition perfectly, but panicking in the kernel as soon as it gets to the boot.img.

If so, I might know how to fix it.
[One (M8) Android Development] eskimosound:
Is this a full ROM of do I have to dirty flash over something?

200 odd MB?

It seems tiny...

Oh I see I download the ROM then download the software GApps... yeah yeah Google Apps... mmm

Ok, I liked the Black Octopus theme I saw, should I use the experimental one?
[One (M8) Android Development] pstrang:
The ROM does complete the flash, it reports "successful". But then within seconds it will reboot to bootloader. From there, you can boot into the ROM okay, however, you cannot get back into recovery without a power cycle.

Unlocked, S-OFF, VZW 5.1 FW (DH's carrier agnostic)

TWRP 2.7

Hope this helps.
[One (M8) Android Development] COMpulse:
Tried 09-02 unofficial. rebooted during install. Pretty sure it happened during ROM install, before it got to installing gapps.

Tried 08-31 nightly. rebooted during install. Last message was "installing gapps", so I tried booting to recovery and installing just gapps, but it still rebooted to bootloader.

Both times rebooted to bootloader and a reboot just hung at HTC white screen.

VZW
[One (M8) Android Development] dechoder:
My screen doesn't turn on when the phone rings either, even after disabling screen off gestures & ambient display. I have an international M8 and on the 8/27 official build.

I can find the devicehandler ok.. but what are easy access service apps? Can't seem to find them.

Also, another minor problem. I can't seem to change the lock screen clock widget to an analog clock, even after changing it in the Bliss interface | Lock screen options | xxx...

Other than that, everything is working nicely... Thanks!
[One (M8) Android Development] fizbanrapper:
It's called EasyAccessService. You will be able to find it with titanium backup. You may need to reboot for the changes to take effect.
[One (M8) Android Development] fizbanrapper:
UPDATE - still a problem... UGH!!!

I deleted the zip from the server. Don't flash it if you've had problems!!!!

Just uploaded a new EXPERIMENTAL ... which is where they're all going to go until I get the all clear from someone with the reboot bug, that can confirm that all is well now.

I made some changes to the ramdisk which I suspect to be the source of the problems. If this fix works, the problem was caused by the split of the trees. The ramdisk tries to load FIOPS, but FIOPS must not play well with kandy kernel during the boot sequence, so I changed it back to the default of ZEN.

Also dropped min frequency default to 268k. No reason to have it at 300k.

If you've had the bug, please flash this ASAP and let me know if the problem is fixed. I have a few other ideas and will try them if this doesn't work, but I don't want to make those changes if it does work. If someone can give me a status update, I may have time to get out another build tonight.
[One (M8) Android Development] TheKnux:
Can't find the latest experimental you're talking about on the server. Unless you meant on your AFH?
[One (M8) Android Development] Derodraaa:
My bad... the date modified on recovery.log is quite old. Seems to be the only log though unless it could get written to somewhere else. Found this in the root directory of internal SD.
[One (M8) Android Development] fizbanrapper:
I deleted it from the server the second I heard that it didn't fix the problem. I didn't want any more people needlessly flashing a bad zip file.

No worries. Thanks for trying!

So I'm basically putting my bliss build into recovery/debugging mode now. I don't know which commit broke it, so I'm not authoring or picking any new ones until I find the offending commit(s).

If the bug is in the rom itself, the problem will still be present when you flash my next build. Until it's resolved, I'll be posting stuff like this for a little while

device/htc/m8 ad2cab4eca22cc34d0db83bdf50487da579281d7

kernel/htc/msm8974 92220de318ef334c6f8f6a5b00d9ba03922f7484

vendor/htc f0c7171703f715d446e9523befc30fba194c9424

These are the SHA's to what is basically equivalent to a "last-known-good" configuration. This is the state of the device repos, prior to the device tree split and merging in a bunch of kernel commits. Assuming all is well on my next build (I will announce when it's up), I'll move up to more recent SHA's until it breaks again. Until the issue is resolved, all builds will be in the EXPERIMENTAL folder unless otherwise noted.

Jenkins may still roll out some "OFFICIAL" builds and I have no control over that. Don't flash those until I give the all-clear. Jenkins is using my very latest commits, which clearly aren't working out so well. I'm going to try to get a build up there before I leave for work, but I have doubts that it'll be done by then.

Thanks for your patience guys.
[One (M8) Android Development] fizbanrapper:
New build is up now. See my last post for explanation of changes.

http://downloads.blissroms.com/BlissPop/Experimental M8/

If you've had the reboot problem, please QUICKLY post your experience with the latest upload. It's a favor to both me, and fellow Bliss users.
[One (M8) Android Development] Derodraaa:
Success!! Flashed fine... booting into system now. let you know if anything goes pear shaped.
[One (M8) Android Development] munkyvirus:
Booting up, no errors.

Boots to black screen, hard rebooted and its rebuilding the ART cache again.

Booted up, Play Services is gone and Evernote is freaking out, but that may be my fault.

Rebooted again after manually installing Play Services. Rebuilt ART for 8 more apps, Play Services didn't stay installed. Rolling back to my GPe nandroid until the next build.
[One (M8) Android Development] fizbanrapper:
The Google play services backup script isn't working at the moment. That's on the ROM side and they're looking into it.

In the meantime, there's an easy fix. Download open gapps PICO and flash it. Everything should work fine after that.

Can you confirm that you used to have the reboot issue and now it's ok?

THANKS!!!
[One (M8) Android Development] munkyvirus:
Used to have the boot issue and it boots now, but rebuilt the Art cache twice, don't know if that matters.
[One (M8) Android Development] yasars:
From official (latest) to experimental (latest)

All wirking fime with gapps pico.... Dirty flash...

Fine thank you... I meen the phome is faster ::)))
[One (M8) Android Development] DizZyRaScaL:
[MENTION=5676253]fizbanrapper[/MENTION]

When will we start seeing new officials releases?
[One (M8) Android Development] fizbanrapper:
If it was up to me, not for quite a while.

Official builds really should be very stable builds that have been tested for an extended period of time without many recent significant commits. You should be able to flash them and not have to worry.

Nightly builds will have the latest code, but maybe some bugs.

Experimental is where we're at now. Significant risks of serious bugs. Though it would appear that the latest experimental build turned out to be nightly quality.

Screen off gestures don't work in that build, btw. I had to disable them temporarily.
[One (M8) Android Development] mcwups1:
Installed flawlessly and working well.

Sprint M8 Converted HK 4.25.654.14
[One (M8) Android Development] fizbanrapper:
Glad the last build seemed to have cured the problem. Unfortunately we're not out of the woods just yet. I still don't know what jacked up the build... so I'll make one change at a time until it breaks again... then I'll figure out the offending commits and revert them.

Anyway here's the next build.

http://downloads.blissroms.com/Blis...issPop-v4.0-m8-EXPERIMENTAL-20150904-2158.zip

I'm thinking that the problems started with the split of the trees, so I advanced the kernel SHA to current. Please let me know if you have problems. If you don't speak up, I will assume there are no problems and move on!

device/htc/m8 ad2cab4eca22cc34d0db83bdf50487da579281d7

kernel/htc/msm8974 369023a278cb97848776d56c0194f411f087f5be

vendor/htc f0c7171703f715d446e9523befc30fba194c9424
[One (M8) Android Development] pstrang:
VZW/5.1 FW

1) Wiped Dalvik, Cache, and System.

2) Flashed ROM; seemed to go much quicker for a lzma compressed ROM (235 MB?). Did NOT reboot to bootloader...good sign.

3) Installed Gapps (BaNkS-dynamic-gapps-5.x.x-8-18-15.zip); reboot.

4) No boot. :(

5) Hard reset; flashed a kernel I built on 9/1; wiped Dalvik and Cache (no errors....good sign); reboot.

6) Booted up; took a long time on 'optimizing', but eventually booted up. Probably due to Play Services problems.

7) Installed Google Play Services standalone apk; seems to be running okay; not much time or testing yet.

Recall on 9/2/15, I cherry picked 5 commits to bring my repo in sync with yours. Perhaps you could look at those on my github? I can't now, but I need to build another kernel with those commits and test it. I'll try later this weekend.

I'm glad you're working on this. We'd have been in deep doo-doo without you! :highfive:
[One (M8) Android Development] TheKnux:
[MENTION=5676253]fizbanrapper[/MENTION] latest experimental (904-2158) doesn't work for me. When I reboot it just reboots to the splash screen over and over. Had to go back to 8/27 official.

AT&T variant on T-Mobile

1) wiped system, dalvik, & cache

2) flashed rom, gapps, v73 official xposed

3) wiped dalvik & cache again
[One (M8) Android Development] heavymetall66:
Confirm ,last nightly is not booting, only splash Boot !

Pico gapps

International m8

Super cid

Twrp
[One (M8) Android Development] _moelle:
its running for me. - m8 international with developer edition firmware (sense) - super cid and multirom ( lates one from op )
[One (M8) Android Development] heavymetall66:
Multirom ?? And i mean lastest experimental blisspop !
[One (M8) Android Development] pstrang:
Good news! *Confirmed*

The 9/1/15 Candy kernel boots, but the 9/2/15 build (after those 5 commits) does *NOT*.

Later this weekend I can revert those commits one by one and find the "bad" one. Just can't today. Thanks for your support [MENTION=5676253]fizbanrapper[/MENTION] !!
[One (M8) Android Development] djbeck811:
See other post.
[One (M8) Android Development] eskimosound:
Hi I flashed BlissPop-v4.0-m8-OFFICIAL-20150905-0757.zip and the Google pay store will not let me buy anything. It refuses my Payment details and also wont allow me to charge to my service provider. It says Declined/Refused.

I know both these methods should be working .

Is there a workaraound?
[One (M8) Android Development] yasars:
Official latest i have bootloader loop.... In recovery he say /cache not fount unmound failed...
[One (M8) Android Development] djbeck811:
New 4.0 official for M8 not working :(

Dirty flashed BlissPop-v4.0-m8-official-20150905-0757.zip on M8 and all I got was HTC logo bootloop. During one of the bootloops I tried to put my phone into Recovery and it did not see the recovery.img. The only way I could recover the phone is by powering the phone down from the bootloader and restart the phone. I pressed the power button, held the volume down and selected Recovery from bootloader and it gave me access to Recovery and I could recover the phone from the nandroid backup and recovered my last good image.

I then tried a clean flash and also got the same bootloop and same problem. I select Recovery from bootloader and it momentarily says "entering recovery" then goes straight to the bootloader again. Once again the phone did not see the recovery.img unless the phone was powered down completely, reboot into bootloader and select Recovery from there. Once again I could restore my last good image.

Any ideas???

CID-11111111 HBOOT-3.19.0.0000 S-Off, Telus (GSM) Canada, TWRP 2.8.7.0.
[One (M8) Android Development] Mjduddin:
BlissPop-v4.0-m8-EXPERIMENTAL-20150904-2158 clean flashed and booted without difficulty. At&t s-on. HBOOT 3.19.0.000
[One (M8) Android Development] fizbanrapper:
Please don't flash officials I until I give the all clear. They roll out of Jenkins and I can't control it. Sorry. I will likely be posting some test kernels later tonight or tomorrow.
[One (M8) Android Development] fizbanrapper:
Ok everyone, your feedback has been tremendously helpful to me in developing a good strategy to figure out where things went wrong. Now that I know the issue is in the kernel repo it makes it MUCH easier for me to compile the kernel at different points in time. Compiling the kernel bootimage is much quicker too.

Let me explain what's below. DATE_##_SHA

DATE - This is the date I compiled it. Nothing more.

## - 00 is last-known-good. 01 is just a few commits later, whereas 03 (in this case) is the newest, and is the commit just prior to last-known-fail.

SHA - This is the commit ID, which helps me to know the state of the kernel repo when I compiled each particular bootimage.

NOTE: These kernels are for the purpose of testing a specific issue with rebooting to bootloader on recent Bliss builds. IF YOU HAVE NOT BEEN having any issues with recent Bliss builds I DON'T NEED YOUR INPUT ON THIS UNLESS IT FAILS.

While these have funny names, I simply renamed the boot.img. It makes no difference. You can flash via recovery all the same.

0904_00_92220de.img

0905_01_8c10396.img

0905_02_2e92a8a.img

0905_03_28402f9.img

When providing feedback, please provide 3 pieces of information 1 - Had you experienced the recent reboot issue (only a few variants do) 2 - What's the file name of the oldest working bootimage, and 3 - What's the file name of the oldest failed bootimage.

Thanks a ton guys! I really appreciate it! The sooner I can figure out the offending commit, the sooner I can move on to the next step and get us back to stable nightlies again. Best-case scenario is the 28402f9 SHA works for everyone, so I'd only have to revert one commit, then I can start debugging the device tree (Far fewer commits to test there).
[One (M8) Android Development] xaoup:
This goes to a bootloop after flashing, it will automatically reboot without letting you flash gapps then nightmare of a bootloop. I have to try twice to see it there is something wrong that i have done during the process but nope same issue. BOOTLOOP. Yes.

Goes back to ViperOne for good measure

Thanks anyway.
[One (M8) Android Development] fizbanrapper:
This? What?

This is zero help to everyone
[One (M8) Android Development] munkyvirus:
Probably installed the latest nightly without reading the thread.
[One (M8) Android Development] xaoup:
Guys look at the same issue experienced by djbeck811, what else should i be referring instead of this rom?

It goes to BOOTLOOP after the flash without even letting me flash the gapps and will leave the

uninitiated scratching their heads beacuse this issue just won't let you go to RECOVERY that easy

I just followed the instructions before i flashed this or do anthying else that's why i said i TRIED TWICE but same gruelling issue
[One (M8) Android Development] pstrang:
[MENTION=5676253]fizbanrapper[/MENTION], *all* of these kernels boot for me! :)

1 - I have experienced the kernel no boot issue. This test is checking the kernel boot problem, not the reboot to bootloader issue after a ROM flash.

2-3) ALL of these kernels boot for me. Currently running 0905_03_28402f9.img.

Thanks!
[One (M8) Android Development] yasars:
I have install over your experimental (latest) the new official after boitlopp i flash this boot img0905_03_28402f9.img and my phone start up normaly... Thank you
[One (M8) Android Development] mcwups1:
I know it's low on the pecking order right now, but I can't change font size, or screen record on this version...

Edit: screen record works, but doesn't show up in notifications with an option to delete.

Sprint M8 Converted HK 4.25.654.14
[One (M8) Android Development] tonymut:
There is something I would like to point out to both the developers and the other fraternity:

1. Currently I am using One M8 International version;

2. I am on S-ON

3. I was on the BlissPop-v4.0-m8-EXPERIMENTAL-20150904-0803 which was stable before flashing the latest Official (BlissPop-v4.0-m8-OFFICIAL-20150906-0158) and Experimental (BlissPop-v4.0-m8-EXPERIMENTAL-20150904-2158)

4. They both bootloop and can be a menace especially in the recovery mode

That said, I realized as fizbanrapper had said that the boot.img might be the problem. As such, the first trick was to get into the recovery section without having to be kicked out before I can flash. To do that, I had to rush into the Wipe mode and the first to wipe was system. After that, the menace for being rebooted out of recovery after 30 or so seconds stopped.

Thereafter, using 7zip, I was able to replace the boot.img with the more stable one from BlissPop-v4.0-m8-EXPERIMENTAL-20150904-0803 into the latest Official as listed earlier on. After copying it back to the SD card I flashed successfully and was able to revert back to my phone and no more restarts.

I hope this helps those having issues out there.
[One (M8) Android Development] fizbanrapper:
BlissPop-v4.0-m8-EXPERIMENTAL-20150906-1115.zip is uploading to the EXPERIMENTAL folder right now.

Based on feedback, the most recent kernel commit had been causing problems. That's gone now, so the above is compiled with CURRENT kernel repo and SHOULD WORK!!!

The above zip is the full rom, with the latest known-working kernel commits.

SHA heads are unchanged in device, device-common, and vendor repos though. We're not quite out of the woods just yet, but we should be one step closer.

Note about ROM bugs: I don't plan on syncing with the Bliss repos until I get the device trees working right. Any bugs in the ROM itself might have been fixed, but its possible that other bugs would come along with those fixes. I know my ROM repos work right now, and don't want to taint them by syncing.
[One (M8) Android Development] djbeck811:
[MENTION=5676253]fizbanrapper[/MENTION],

Edit: LOL after all that I see your above post. I'll try this and let you know.

The last working build for my phone was BLISSPOP-V3.9-M8-OFFICIAL-20150827-0154.ZIP. The V4 versions did not work and I had the problems I previously mentioned in my last post (#6821). With the first kernel 0904_00_92220de.img it seemed to work fine but when I booted up for the first time I received the following message "Google Play Services - Google Play Music relies on Google Play services, which is not supported by your device. Contact the manufacturer for assistance." I also noted my "Playstore" app has disappeared.

I wiped and restored to the 20150827 official build and tried the second kernel 0905_01_8c10396.img and it booted fine and I obtained the same results as the first.

I wiped and restored to the 20150827 official build and tried the third kernel 0905_02_2e92a8a.img and it booted fine into the Blisspop splash screen and stayed there for over 30 minutes at which time I did a hard reboot. After the hard reboot it went into the blisspop splash screen and stayed there for another 15 minutes so I did another hard reboot and restored my last working version.

After the restore I dirty flashed the latest official (BlissPop-v4.0-m8-OFFICIAL-20150906-0158.zip) and then flashed the last kernel (0905_03_28402f9.img) in your list. It booted into the BlissPop splash screen and looked promising as the screen showing the optimizing of the apps and completed. After all the updates the phone went back to the Bliss Pop splash screen and then booted up normal. Once again the "Playstore" was missing and I had the same warning "Google Play Services - Google Play Music relies on Google Play services, which is not supported by your device. Contact the manufacturer for assistance." The phone seems to work fine other than the missing Google Play Services.

I then booted into Recovery and flashed the GAPPS to see if it would reinstall or fix the problem but it failed to install due to insufficient space on partition.

I wiped the phone and installed BlissPop-v4.0-m8-OFFICIAL-20150905-0757.zip and then the GAPPS but got the same error.

I wiped the phone once again and installed BlissPop-v4.0-m8-OFFICIAL-20150905-0757.zip then booted into Bootloader. Once there I flashed the kernel 0905_03_28402f9.img. I then rebooted the phone and it went into the optimizing the apps (without any GAPPS). The phone booted normally and seemed to have no issues.

I then booted into Recovery to see if it would let me install the GAPPS. I received the same error about the partition size. One point to note is when I opened my Android File Transfer it would only see the ext sdcard and NO internal memory storage.

After all this, I just can't get the phone to boot properly without causing issues with the partition or GAPPS.

I have restored the phone to my last good Nandroid.

Hope these steps help in the fault finding in someway, it's taken me all morning and part of the afternoon.

Dave

CID-11111111 HBOOT-3.19.0.0000 S-Off, Telus (GSM) Canada, TWRP 2.8.7.0.
[One (M8) Android Development] fizbanrapper:
BlissPop-v4.0-m8-EXPERIMENTAL-20150906-1144.zip is uploading now. It is the same as BlissPop-v4.0-m8-EXPERIMENTAL-20150906-1115 except 1144 is compiled with CURRENT SPLIT TREES AND VENDOR BLOBS!

If 1144 doesn't work, 1115 should work.
[One (M8) Android Development] djbeck811:
I tried the BlissPop-v4.0-m8-EXPERIMENTAL-20150906-1115 via a dirty flash and had the same issues. I also tried it as a clean install and attempted to flash the GAPPS but again I get an error and again my Android File Transfer did not see anything but the exteranal SD Card.

I recovered my last working recovery and dirty flashed BlissPop-v4.0-m8-EXPERIMENTAL-20150906-1144.zip and then clean installed but had all the same issues.

This is getting frustrating lol.

Good luck!