yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Android Development] apophis9283:
It was yoinx who came up with the solution. I just implemented it. So huge thanks to the new RC Yoinx
[Nexus 6 Android Development] WhiteEVO:
Pvs bin: 5

Speed bin: 2
[Nexus 6 Android Development] xenx:
For what it's worth, I double checked the md5. I even tried reflashing and no change.
[Nexus 6 Android Development] str8str:
Just thought I'd chime in and say I've yet to have any issues with booting on this kernel. 2.2 booted rite up. Testing the rest

Straight Shooter

---------- Post added at 01:48 ---------- Previous post was at 01:21 ----------

I never touch the voltage settings I leave them alone. I know for a fact that over clocking and under bolting usually cause more issues than they do save battery. I think a lot of people's issues can be directly related to that. I never touch them and I never see the problems others are.

Straight Shooter
[Nexus 6 Android Development] head_banger:
V2.2 is booting now

Edit: rebooted phone, got stuck at google screen again :(
[Nexus 6 Android Development] :
If you're able to get it to boot again, it's be really curious to see the dmesg.
[Nexus 6 Android Development] head_banger:
Tried but no success unfortunatly
[Nexus 6 Android Development] Mr_S:
This was my fav lp kernel but due to court case need stability so can only test weekend (2moz) but am enjoying seeing the progress and the 2 devs that are on it have awesome interaction with users,I like this and I will return.....mwahahaha
[Nexus 6 Android Development] jolly_roger_hook:
Everything works for me except certain governors will not sick after a reboot everything else sticks just fine
[Nexus 6 Android Development] mhsbrian:
I'm not sure what the deal is, the 2.2 gave me issues in the beginning as I noted but now it won't boot up at all anymore, I noticed my phone was getting pretty warm as well during this. I have switched back to another kernel for the moment. If I can be of anymore assistance guys let me know.
[Nexus 6 Android Development] S0UTHPAWK1LLA:
Only issue I had was that battery issue where it shows 4500%... Seems to be a common issue across multiple kernels. r26 commit conflict?
[Nexus 6 Android Development] apophis9283:
This can be fixed. Ive already reverted the commit
[Nexus 6 Android Development] apophis9283:
We will keep going til it works for everyone.
[Nexus 6 Android Development] apophis9283:
Heres another test version. Everyone is welcome to flash it, more feedback the better

https://www.androidfilehost.com/?fid=24269982086995316
[Nexus 6 Android Development] head_banger:
Sorry tried but can't get past google logo,

Must have something to boot.img that comes with rom
[Nexus 6 Android Development] apophis9283:
That sounds like a bad download or flash. If it hangs at the logo or reboots to the logo constantly. Thats usually something else. Although I finally decided to update my wifes phone and it went to boot all the way, but then it stopped and stuck on the google logo. Which means. If my wifes phone isnt booting I may be able to find out why
[Nexus 6 Android Development] mexiken:
I wouldn't mind trying to test, however I flashed CM. Since its based on AOSP I should be good right????
[Nexus 6 Android Development] mhsbrian:
It's my exact issue, I flash it and it appears to boot one time, fails, then forever hangs at the boot logo.
[Nexus 6 Android Development] apophis9283:
Itll be sunday before ill be able to sit down with her phone. Ill still update the kernel if i need to. Hoping her phone holds some answers
[Nexus 6 Android Development] S0UTHPAWK1LLA:
I tried the test and it looks like the battery was fixed but I had issues with layers not sticking and random reboots when streaming. I had to go back to my backup real quick cause I needed my phone for work (spaced getting the log)
[Nexus 6 Android Development] mexiken:
I'm running an alpha build of CM 13, and can't get past boot screen either. Although, it could be my build. Latest test and 2.2 didn't work for me.
[Nexus 6 Android Development] Mr_S:
Flashed newest build and it looped the google logo once then booted fine on pure nexus.

All seems fine so far,tweaked a ton of features and have to say I'm pretty impressed with the amount of settings. Good work

First impressions are that it's all smooth, first thing I noticed and I had this on lp is in synapse,when I try to back up a profile it says enter a name but after entering 'xyz' and clicking backup it reverts to 'none' and won't save.

No biggie,just mentioning it.

Will charge and test and report any findings with logs if possible
[Nexus 6 Android Development] apophis9283:
After you name a profile or config, you have to go to the top and click the checkmark. Once thats done go back done and tell it to save. pretty much to be able to see the save, reboot the phone
[Nexus 6 Android Development] apophis9283:
I will have another test build very soon. Hopefully this gets it
[Nexus 6 Android Development] apophis9283:
Please give this a try and report back

https://www.androidfilehost.com/?fid=24269982086996241
[Nexus 6 Android Development] DreamFX:
In case anyone hasn't noticed Xposed MM is out and working wonderfully overall!
[Nexus 6 Android Development] str8str:
Settings still don't stick after reboot. Sorry
[Nexus 6 Android Development] apophis9283:
I know its an issue, but not my main focus. Right now its all about getting everyone up and running. That will come after.
[Nexus 6 Android Development] apophis9283:
I will have another official build up tonight, Ive been wanting to bring in a governor called performance may cry. As you guess its a very battery friendly governor. But I realized it was just a modified smarttmax governor. So I took the tuneables from PMC governor and made our smartmax governor as much like performance may cry. In the next release it will be there. Be warned, smartmax is now an extremely battery friendly governor.

Like i said i based it off a governor call performance may cry
[Nexus 6 Android Development] apophis9283:
2.3 is up some minor changes but worth the flash, you can now choose to lower gpu to 110. if you have lockup issues simply bump it up
[Nexus 6 Android Development] apophis9283:
I know some people are still having issues, and synapse settings dont stick all the time. Besides that, is there anything you want or removed?

I first started making thise kernel because I LOVE OPTIONS! Other kernel devs may not think the same way. I am open to giving anything a shot. I will continue to work on making it so everyone can flash with no issues, just need a break from stuff like that
[Nexus 6 Android Development] jamescable:
Steaven, pm me
[Nexus 6 Android Development] mexiken:
Tried 2.3, still no luck here. Just boot loops the Google screen.

Really bummed, since you mentioned you emulated PMC. That was my favorite governor :(
[Nexus 6 Android Development] fedef12evo:
No boot for me aswell on octos m
[Nexus 6 Android Development] sefurd:
Booted up fine for me however I lost mobile data... On Benzo.
[Nexus 6 Android Development] apophis9283:
Just really odd. Ive reverted aything that should cause issues. We are up to date with everything that matters. We used stock mm source and to make sure i didnt miss anything, I did a diff between stock mm and ours. Besides the features and 1 or 2 small tweaks they are identical.
[Nexus 6 Android Development] fedef12evo:
I extracted zimage from your flashable zip and repacked it in benzocore zip flashable and now it is working without problem
[Nexus 6 Android Development] apophis9283:
Going off the information the user above has pointed out. I have made it so it should be like benzo cores. Here is a test build. I would love for EVERYONE to test and report back please and thank you.

test build

https://www.androidfilehost.com/?fid=24269982086997697
[Nexus 6 Android Development] xenx:
Still stuck at Google logo.
[Nexus 6 Android Development] apophis9283:
Do this, once at the google boot logo. after it sits for a second. Long press power+vol up+ vol down. It will reboot the phone. Then see if it goes past the google logo
[Nexus 6 Android Development] fedef12evo:
I used it 10 mins repacked in that flashable zip then i rebooted device and stucked again dont know why, but at least i got it booted for a while
[Nexus 6 Android Development] apophis9283:
Ok everyone, going a different route. This is a boot.img. You dont need adb or fastboot. Simply put this on your internal storage reboot into TWRP.

Theres a drop down menu that will set it to flash boot.img's. Simply dpo that select the boot.img and test. See if that helps any

https://www.androidfilehost.com/?fid=24269982086997821

might help if i post the link
[Nexus 6 Android Development] :
Keep in mind, this was created from chroma. Using it on another rom may cause issues since it's not preserving anything in that roms boot image. It should boot regardless, just may misbehave the rom.

Make sure to backup your boot partition first.

Basically, we're trying to rule out issues with anykernel at this point.
[Nexus 6 Android Development] xenx:
Tried this, same results. I also tried the previous recommendation of manually rebooting when it loops and it made no difference.
[Nexus 6 Android Development] apophis9283:
Well Kernel Version 2.4 is up in op. Enjoy!

We will keep trying to fix the non-boot issue
[Nexus 6 Android Development] :
Can you send a dmesg from a working kernel from boot up.
[Nexus 6 Android Development] apophis9283:
Anyone can flash this. Its aimed at the people who cant get it to boot

https://www.androidfilehost.com/?fid=24269982086997990
[Nexus 6 Android Development] an21281:
Still getting stuck at Google splash, flashes off then back....
[Nexus 6 Android Development] apophis9283:
Im at a loss here, weve tried compression, no compression, boot.img, and quite a few code changes. I just re-added chainfires sepolicy. Ill continue looking to see if i cent find something
[Nexus 6 Android Development] an21281:
Almost all vortex mm kernels flashed fine for me, I noticed after changing the name I have only been able to successfully boot one build about a week ago and that bootlooped after 30 secs with no changes. So not sure if that helps but hope you can get it working again for all. Could always flash an older vortex build I guess
[Nexus 6 Android Development] apophis9283:
I just found something that may be tied into people having issues. When i finish tomorrrow ill release a test build. no promises
[Nexus 6 Android Development] an21281:
Nice, will give it a test once your ready
[Nexus 6 Android Development] apophis9283:
Im probably just gonna release it as 2.5. A bunch of small stuff. Like GPU doesnt need to be at 605, so I changed it to even 600. It looked stupid with the 5. Ive also reverted more stuff. What I was talking about what some code min/max being defined twice in the same file and defined in defconfig. It shouldnt need all those defines of min/max. Also we had a commit that was fixing something but as the min he had 300 instead of 35.

I could release a build tonight but I want to go through this stuff with a fine tooth comb
[Nexus 6 Android Development] mexiken:
Thank you guys for being patient with us, and helping us. I tried the 1st test kernel, and then the boot.img, and then the 2nd test kernel, and nada.

Trying to get you guys a dmesg log. Having trouble booting my old kernel back on now :(
[Nexus 6 Android Development] apophis9283:
Thank you for being patient and understanding. Ill either have a test version tomorrow or release a new build
[Nexus 6 Android Development] sefurd:
Flashed test kernel and booted with no problems. Mobile data is working as well. Looks like you are on the right track. Synapse settings not sticking (known issue), just thought I would confirm on test kernel.

Thanks for your hard work!
[Nexus 6 Android Development] apophis9283:
I just edited the OP, to reflect what we have as of now. It was off by a few features
[Nexus 6 Android Development] apophis9283:
Anyone can flash this as it has a few addition, but yet again this is aimed at people who cant get it to boot. Feedback would be awesome. Logs would be more awesome

Kernel = https://www.androidfilehost.com/?fid=24269982086998583

UKM-TEST = https://www.androidfilehost.com/?fid=24269982086998594 ( ONLY IF YOU USE SYNAPSE)

Flash those together please
[Nexus 6 Android Development] xenx:
I've been a bit busy, but hopefully it helps. http://pastebin.com/hieMii90

---------- Post added at 11:30 AM ---------- Previous post was at 11:29 AM ----------

Same issue at google logo with that test.
[Nexus 6 Android Development] apophis9283:
In that case, whats your bin?
[Nexus 6 Android Development] xenx:
13
[Nexus 6 Android Development] apophis9283:
Yeah, that could be causing it. If everyone who cant get it to boot. Post your bin.
[Nexus 6 Android Development] :
What baseband is .104? I don't think that's the mm one.

Also, that's a kernel that's working perfectly fine for you? Because there's a crash trace in the first second or two of the boot up.
[Nexus 6 Android Development] xenx:
It's MRA58K for the baseband. The kernel is just the default Pure 11/13 kernel. If it's having trouble, I'm not seeing it. I've also run the 11/13 Hydra kernel and Despair R38 kernel. I could load them up and grab a dmesg if that'll help.
[Nexus 6 Android Development] :
If you have the time, I'd be curious.

From what I'm seeing in your log...

You have a krait clock crash real early on.

It's throwing a ton of named gpio errors. Disregard, I have these too.

Your cpu is getting hot enough within the first 1.5 secs of boot that the thermal driver is Limiting it to the min freq... But I don't ever see it scale back up... Which is weird to say the least.

There's also a ton of init entries trying to write things that don't exist... not really anything I care about.. But might be worth mentioning to BeansTown so that he can remove them from his init files, or at least correct them to the right paths.
[Nexus 6 Android Development] xenx:
Hydra - http://pastebin.com/y582bib8

Despair - http://pastebin.com/bAM4efZa
[Nexus 6 Android Development] :
Thanks, I'll take a look at them.

*edit*

weird. Same crash trace on both of those too. Must not be related.

*edit 2*

We're running out of ideas... Maybe it's the toolchain?

This was rolled all the way back to google's prebuilt 4.8 toolchain. Could someone with the Google Logo/No Boot test this zip and see if it works? It booted fine here, so it won't cause any issues... just trying to see if it fixes anything for the couple people with issues.

https://www.androidfilehost.com/?fid=24269982086998780

Sorry folks, I know this "Please test flash this" repeatedly gets a little old... But it's the only way that we can test things since neither of us are experiencing this problem.
[Nexus 6 Android Development] buckmarble:
I have found some small changes in init.rc and init.shamu.rc in some of the aosp roms that will prevent booting past the Google logo on stock based roms. And visa versa, if those things aren't in there, it'll boot stock but stuck at Google on aosp. I had to remove these two files from our any kernel zip in order to make it compatible with both types of roms. So this might be something to look at, especially if you are shipping your builds out as a boot img.
[Nexus 6 Android Development] :
Thanks for the info. We don't though, we use anykernel.

The only files we push to the ramdisk are chainfire's modified sepolicy (to try and avoid people having to flash his boot.img) the power init (probably not even needed anymore honestly) and fstab (for f2fs support). We only modify a couple things in the other files, make sure verity is disabled, add init.d support... The typical anykernel stuff.

That's what's so frustrating about this. The only thing that I've seen in common so far amongst the people having issues that have sent me dmesgs is that they are all binned as 2/13... which is about as bad as the chipset can get and all support all stock frequencies starting at 14 the stock table doesn't even go to 2.6ghz. After resetting the voltages for that bin back to stock, some people started being able to boot. Other people started being able to boot once then it wouldn't boot again. We actually reset all the stock freq voltages back to stock at that point. Imo, undervolting doesn't give that big of a boost for the issues it can cause, plus it's all tunable in userspace anyway.

The past that kills me is that it works for most everyone... Just a handful so far that it doesn't, and the binning is the only common factor I've found. Which honestly, if it was my phone and it was binned to that end, I'd probably and it in for a warranty replacement anyway and hope for a better chip. Just my opinion... Not that I'm trying to blame people's hardware since it works on other Kernels. Just at that end of the doping, you lose the ability to oc/uv to a large extent. It ends up being kind of handicapped.

I have noticed though that a lot happens during the title logo. I always thought that was essentially just the unpack of the boot.img and initial startup. But it isn't. It's got a lot going on by the time that the boot animation comes up.

Anyway, sorry for the long post. Appreciate the suggestion, but I don't believe it applies. If you have any other ideas, I'd love to hear them though. This problem is driving us nuts... Especially since neither of us have the issue and we're troubleshooting basically blind.
[Nexus 6 Android Development] xenx:
So, between work hell and XDA/Browser not actually posting my reply this is a bit delayed. I got the same results with the posted test kernel.
[Nexus 6 Android Development] apophis9283:
Im trying to get a list of people who cant get it to boot. Make a post saying you cant get it to boot. Name, Rom, Pvs Bin: number. Any mods you may use, even go as far as what radio/bootloader. As much info as you can. Thanks
[Nexus 6 Android Development] mexiken:
I tried the first test kernel, nada.

I flashed Despair, it booted. I tried using: adb shell su -c dmesg > dmesg.log and I get an error denied. What am I doing wrong????

Edit: Got past that. Now I get a can't create, read only file system :(
[Nexus 6 Android Development] xenx:
Write it to like /sdcard/dmesg.log.
[Nexus 6 Android Development] mexiken:
adb shell su -c dmesg > sdcard/dmesg.log

/system/bin/sh: adb: not found

127|root@shamu:/ #
[Nexus 6 Android Development] xenx:
If you're doing it from term on the device.. just do "dmesg > /sdcard/dmesg.log"
[Nexus 6 Android Development] mexiken:
I was plugged into computer and used Minimal ADB. I'll try on terminal emulator on device.

I get the same error on the phone terminal: can't create sdcard/dmesg: permission denied.

Did just an adb shell dmesg

Dumped stuff. I put into pastebin.

http://pastebin.com/d1dvq5db

I would assume this is the important stuff you need:

[ 0.244399] clock-krait-8974 f9016000.qcom,clock-krait: Speed bin: 2

[ 0.244433] clock-krait-8974 f9016000.qcom,clock-krait: PVS bin: 5

[ 0.244445] clock-krait-8974 f9016000.qcom,clock-krait: SVS PVS bin: 13

[ 0.244458] clock-krait-8974 f9016000.qcom,clock-krait: PVS version: 1

I run CM 13 Alpha. I don't have any mods, no Xposed or anything. Just a CM theme. Don't even use Greenify.

Radio: 104

BL: moto-apq8084-71.15
[Nexus 6 Android Development] str8str:
This is really weird that this works on most but not all. I don't think I've seen this happen before. I've been able to boot all versions with no issues of this kernel and feel frustrated for those who can't. Hope we can get this figured out cause the suspense is killing me. Lol
[Nexus 6 Android Development] apophis9283:
Alright, everyone who hasnt been able to use our kernel, please try this and report back! :)

Hopefully you get to enjoy it.

https://www.androidfilehost.com/?fid=24269982086999243
[Nexus 6 Android Development] fedef12evo:
now it is booting :good:
[Nexus 6 Android Development] :
Just to verify...

You're one of the Speed 2 Bin 13 guys right?

You can check it in synapse on the status page if it booted (make sure you used UKM)

Also, if you are... and this booted, can you pull a dmesg before you reboot and possibly get stuck with it not booting back up again?
[Nexus 6 Android Development] fedef12evo:
i rebooted lot of times and it is booting very well, no problems, only thing had to do is disable msm limiter because using an hotplug will overclock cpus even setting max cpu at 2649 and then it reboots, but disabling msm limiter now is all ok, gonna see what pvs i have
[Nexus 6 Android Development] apophis9283:
Just updated OP, we are at V2.5. IT SHOULD BOOT FOR EVERYONE NOW!!!!

Hope you all enjoy.
[Nexus 6 Android Development] :
That's kinda weird... That's exactly what msm_limiter is trying to prevent.

Was that with any hotplug, or just certain ones? Did you have the "hotplug boost" set?
[Nexus 6 Android Development] fedef12evo:
i got reboots with all hotplugs,hotplug boost was on, and msm limiter on, then reboot, if I turn off msm limiter no reboots, or if i turn off hotplug boost no reboots
[Nexus 6 Android Development] :
yeah, you should leave msm_limiter on then, with the max at 2.6ghz or less and just turn off the hotplug boost option (my advice).

I'll have to look into what hotplug boost is doing wrong. Since it sounds like it's ignoring the msm_limiter max freq.
[Nexus 6 Android Development] fedef12evo:
ok going to try, if i look at frequencies, it bounce back at 3033 even if freq limit is set to 2649

edit: hotplug boost off, and it rebooted itself, I was able to see what freq bounced and i saw 2726 with stock settings, havent touched anything, this msm limiter is driving me crazy
[Nexus 6 Android Development] :
Could you do this?

echo 7 > /proc/sys/kernel/printk
dmesg > /sdcard/dmesg.txt

then send me your dmesg.txt from the sdcard? You can do those from the adb shell as well, just change the dmesg one, adb shell dmesg > dmesg.txt will put dmesg.txt in your current terminal/cmd directory.
[Nexus 6 Android Development] fedef12evo:
im not able to boot the phone because if reboots itself after 10 sec lol, but i was able to try without hotplug 4 cores online no problems, or without hotplug boost no problems even using hotplug,so the problem is hotplug boost, now im running it with auto smp hotplug and without hotplug boost and no problems,but if i reboot, the time that synapse start my settings phone will reboot itself because of hotplug boost lol
[Nexus 6 Android Development] apophis9283:
try reflashing the kernel and ukm
[Nexus 6 Android Development] fedef12evo:
already tried, if phone dont reboot until synapse apply settings, then it will not reboot anymore, it is that time that with stock setting hotplug on(mako) and hotplug boost on,if for example kernel will boot with zen decision (4 cores online) on stock settings there will be no problems at all
[Nexus 6 Android Development] :
Sorry, I think there's a bit of a language barrier. I'm guessing English isn't your first language? You have a lot of information in there, it's just not extremely coherent.

If I'm reading this right, the two things that are causing issues now are mako hotplug and hotplug boost?
[Nexus 6 Android Development] fedef12evo:
sorry for my english :(, what is causing issues are hotplugs combined with hotplug boost and overclock.

because with no overclock no more problems,using overclock hotplugs and hotplug boost cause problems freq will go to 3033, using 4 cores online no problems at all.But stock kernel settings are hotplug(mako) and hotplug boost, so no time to set my settings on synapse and it reboot
[Nexus 6 Android Development] :
No need to apologize. Just had a hard time making out what you were trying to say.

It sounds like we may be able to just change a few default settings as a quick fix, until we can figure out why those other two items aren't honoring the max freq like they should.

Apophis is looking into it a bit now.

Thanks by the way for the in depth info.