yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] franciscofranco:
I would love to help, but I don't see any error. Looking at the log with care I see a couple strange things:

This shows up a lot, which means you have some app WakeLocking your device preventing it to sleep.

[ 265.893507] last active wakeup source: PowerManagerService.WakeLocks

[ 265.893728] Freezing of tasks aborted after 0.003 seconds (263 tasks refusing to freeze, wq_busy=0):

Then this shows up:

[ 279.545366] dpm_run_callback(): platform_pm_suspend+0x0/0x54 returns -16

[ 279.545378] PM: Device alarm failed to suspend: error -16

[ 279.632188] PM: Some devices failed to suspend

Doesn't look that fancy, which then follows this:

[ 400.168636] Freezing user space processes ...

[ 400.172048] active wakeup source: ipc0000009b_FLP Service Cal

[ 400.172149] active wakeup source: PowerManagerService.WakeLocks

[ 400.172259] active wakeup source: alarm

[ 400.172370] Freezing of tasks aborted after 0.003 seconds (262 tasks refusing to freeze, wq_busy=0):

This is spammed for a while until it stops. I'm not saying this is the cause for your ****, but I would seriously consider you to check what your apps are up to. It's not normal to have reboots everyday. I think I haven't had a random reboot in months.
[ONE Original Android Development] oxxshadow:
will the cm11s version work on the cm11 nightiles?
[ONE Original Android Development] Tzfardaya:
No
[ONE Original Android Development] Savant:
Sarcasm implied?

Sent from my OnePlus-One.
[ONE Original Android Development] Tzfardaya:
No, the cm11s kernel does not work with the cm11 nighties...

---------- Post added at 08:47 PM ---------- Previous post was at 08:46 PM ----------

Everybody say it with me...

Cm11s kernel is for cm11s only....

Everything else uses the aosp kernel...
[ONE Original Android Development] Savant:
I know, I wasn't expecting a cut and dry answer from you.

Sent from my OnePlus-One.
[ONE Original Android Development] paychex:
Thanks. It has pretty good deep sleep. It does seem like it has fallen off a bit recently. The only thing that seems like it has high wakelock is google wallet. And it's really not that high, just seems like it shouldn't be as high as it is. Like I said, clearing cache and dalvik seems like it fixed the issue. If it persists. I'll look for those entries in the last_kmsg first
[ONE Original Android Development] Tzfardaya:
Even I give straight answers from time to time... You can tell them because they're only one word long...
[ONE Original Android Development] dbaler:
I'm having trouble getting the FKU app to set the voltages on boot. Was told to post here by the guy above.
[ONE Original Android Development] Anthonok:
A little OT but I've noticed wallet randomly keeping my phone awake the past few days for no apparent reason.
[ONE Original Android Development] Tunasty:
Are you running the beta? If yes, then it's WIP

-Tunasty
[ONE Original Android Development] toyota86:
Flashed r23 for the latest awesomeness
[ONE Original Android Development] dosiwi:
I get some freaking random reboots like psyched. Thought I am the only one :( https://mega.co.nz/#!k1F3TKDD!NJ7IB-KpkN19tiqD1RCVda_o7npMPNvUtTpeuqY8Inw

Seems to be happen after a longer idle time.

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] feihtkrad:
I am also having touchscreen problem(random ghost touches I have never encounter before) with r23...flashed back to r22 for now.
[ONE Original Android Development] gpelekanos1:
I got similar issues. Flashed back to r22 and then reflashed r23 and seems to be working fine now. I ll report by end of day though.
[ONE Original Android Development] ChefChaudart:
( Guys, are you sometimes reading what´s Franco says ??? )
[ONE Original Android Development] irony17:
Good morning @ all ;)

Couldn't find the answer to my question in the thread so i'll drop it here in case someone can help :

in "setting / performance profiles / activate per app profiles "

I checked the box as it it supposed to choose the best adapted profile but is it still working with this kernel ?

I saw an option in FKU where you can manually set the per app profiles but I find it more convenient automatically....

thx in advance ;)
[ONE Original Android Development] Daedulus Minion:
Can I flash this over latest 38R OTA? I am kinda addicted to this kernel :P
[ONE Original Android Development] Addicteddddd:
Anyone getting fairly reduced battery life in r23 vs r22?
[ONE Original Android Development] zephiK:
It should work, try it and report back.

If it doesn't boot then reflash boot.img from 38R. Daedulus, could you do me a favor and get framework.jar from /system/framework and attach it for me?
[ONE Original Android Development] Daedulus Minion:
Yes sure. But I haven't updated it yet. So you may have to wait. Is it fine?
[ONE Original Android Development] zephiK:
I'm not using XNPH38R, I'm on a custom ROM. It should work as it does have the newest and latest commits.

Give it a try, if it doesn't work then flash the stock kernel with XNPH38R.

I'll make a flashable zip with XNPH38R stock kernel for you. Give me a minute, im also mirroring the 38R update

Edit: https://www.androidfilehost.com/?fid=95747613655042878 XNPH33R to XNPH38R zip

https://www.androidfilehost.com/?fid=95747613655042881 XNPH38R Stock Kernel.

Flash Franco r23 on XNPH38R. If it doesn't boot then flash XNPH38R stock kernel in the zip above. Franco r23 should boot on XNPH38R as it stays up to date with commits. If it boots, someone confirm.
[ONE Original Android Development] Daedulus Minion:
Thanks :)
[ONE Original Android Development] wollax:
With latest franco r23 OTA install fails with errors checking system folder/files regarding thermal thing ... I think franco copies some files for thermal control inside system partition and this blocks update .... even restoring 33R kernel doesn't solve for the moment ....

I will try to understand which files are blocking this OTA !

anyone can help ?
[ONE Original Android Development] black nebur:
Thanks for your awesome work!!! :good::good::good:

Anyway I'll gonna wait for some more opinions cause I'm at work and cant risk to soft brick and cant access to fastboot and ADB :p

You're the man!!!
[ONE Original Android Development] zephiK:
:p for the XNPH38R stock kernel all you have to do is flash the zip. no fastboot or adb needed.

Try the modified OTA script, http://xdaforums.com/showpost.php?p=55877574&postcount=46
[ONE Original Android Development] benthe:
There's a modified zip that has a modified updater script which doesn't check for it here.

I just installed it after running into the same issue as you did.

---------- Post added at 12:23 PM ---------- Previous post was at 12:04 PM ----------

Just tried flashing r23 on 38R and got in a boot loop.

Guess we're waiting for r24 to be compatible with 38R then.
[ONE Original Android Development] cypher21:
Franco doesnt work on 38R :(

I did backup a boot.img of the original kernel but can't fix it at work unfortunately....

Darn it..

edit.

Reflashed 38R OTA fixed it (duh..)
[ONE Original Android Development] zephiK:
Guess you'll have to wait for Franco to take a look at it when he has the time tomorrow. I'm off to bed, 5:26 AM here.

And to those who are using custom roms, heres the new camera from 38R https://androidfilehost.com/?fid=95747613655042893 has some extra goodies (raw image).
[ONE Original Android Development] wollax:
perfectly working the modified script .... I will try r23 asap over new OTA !!!! thanks again
[ONE Original Android Development] chr0m:
Hmm, tried flashing with TWRP and I get "Error executing updater binary in zip"

I guess I need the modified updater script?

That mediafire link is sloooooow. The unmodified one on androidfilehost came much quicker :)
[ONE Original Android Development] ChefChaudart:
ok for me.

What I did ;

1. Installed zip posted by zephIQ ( cm-bacon-XNPH38R.zip )

2. While in recovery, I directly installed XNPH38R-Stock-Kernel.zip

So, no Franco´s kernel for now, but at least everything is working.
[ONE Original Android Development] Manholas:
will work, trickster :victory::angel::D
[ONE Original Android Development] chr0m:
Why do step 2? Doesn't the stock kernel get installed as part of step 1? So you didn't need to use the update with the modified updater script?
[ONE Original Android Development] Manholas:
I pulled the stock kernel will, to the forum. May give way to someone. :cyclops:

Thanks to zephiK:good:
[ONE Original Android Development] ChefChaudart:
Just to be sure :p
[ONE Original Android Development] shure2:
Got some graphics glitches today, black lines on the screen, not seen them before but I'm sure its nothing to do with r23?
[ONE Original Android Development] fredzen14:
Try disable HW overlay located under setting<developer option.
[ONE Original Android Development] black nebur:
Hahahahahahahahaha Thanks!!!
[ONE Original Android Development] bernard134:
Waiting for Franco Kernel to support latest OPO 38R OTA before upgrading!! Oh yeah!!
[ONE Original Android Development] paulo111:
also wondering this :o
[ONE Original Android Development] tsiftsism:
I have read many posts in here suggesting to some users that they should disable HW overlay but i couldn't understand why to do this because i had no issues.

Mostly that was suggested to people that were using not updated roms if can recall, but today it's the first time i've seen those black lines on my screen as well.
[ONE Original Android Development] suaverc118:
Not sure if its Vanir or the kernel bit have had the black line for the last 2-3 days. Vanir was 10-1 and I've been on r22-23 too. It comes and goes
[ONE Original Android Development] chayesfss:
Yea I'm doing the same thing. Not worth it to F up the phone cause I can't wait a day or 2
[ONE Original Android Development] J0ker 82:
Yeah, lol, i installed r23 on KTU84U and i got stuck on boot. Waitin for FK update :D
[ONE Original Android Development] TjPhysicist:
Higher Bitrate audio

Currenly most version of android sample all losslesss files to 44.1/16bit. The new 38R update for Cm11S now has support for upto 96Khz/24Bit audio WITHOUT resampling it down to 44.1/16bit. Are there any plans to add this to franco? Would this require a userland change as well that was done in CM11s/38R or am I right in assuming this is purely a kernel level change? As I always use a USB DAC I would LOVE to have this on my phone.
[ONE Original Android Development] franciscofranco:
Guys don't bother trying to use r23 with the new OTA. As I suspected they are now running a much newer display userspace firmware and I need some time to check things up. Hopefully it's sooner than later.

All changes are always up-to-date with CM's Kernel repo. It's a combination between the Kernel and userspace changes present on 38R.
[ONE Original Android Development] shuweee:
What exactly does 38r ota address? I just check for update and nothing came through

Sent via Oneplus One + CM11S + franco r22
[ONE Original Android Development] franciscofranco:
Lot's of new ****, specially an awesome feature, Partial Updates!!!!!!!!!!! Moar battery savings from the display.
[ONE Original Android Development] franciscofranco:
I'm very happy to announce that cm nightlies branch and stock CM11S branches are now TOGETHER :D You can boot the Kernel that's inside AOSP branch on the new OTA and it works :)
[ONE Original Android Development] andresantos:
how do I revert back to stock kernel? any flashable zips? I can't install the new update and would like to try it.
[ONE Original Android Development] ohhcrapitstim:
I am really looking forward to an update so that I can update to CM 38R :o
[ONE Original Android Development] franciscofranco:
Read two posts up...
[ONE Original Android Development] franciscofranco:
By the way if you try to flash the OTA or sideload or whatever it will give you an assert error. Rename /system/bin/thermal-engine.bak to /system/bin/thermal-engine and you'll be able to flash it.
[ONE Original Android Development] ohhcrapitstim:
Just realized this and updated to r23.

This is the error I was getting and thought I needed to revert to the stock kernel or something, but this worked for me and I successfully updated to CM38R.
[ONE Original Android Development] andresantos:
you were able to install the unmodified version of the OTA? I renamed the thermal engine.bak but still doesn't install the ota. I'm pretty sure I haven't modified anything else. only installed franco.
[ONE Original Android Development] tcapote:
Thanks Franco, I used Root Explorer, renamed the file to /system/bin/thermal-engine, booted in to TWRP, installed from my downloads directory and get a "failed" . It is saying "Error executing updater binary in ZIP" any thoughts?

Thanks for any guidance
[ONE Original Android Development] ohhcrapitstim:
I updated to franco r23 and renamed thermal-engine.bak to thermal-engine. This allowed me to install the ota. It installed the CM kernel, so I tried flashing the franco kernel and now my phone won't boot :/ So I am going to try flashing the CM38R rom and go from there.
[ONE Original Android Development] irony17:
what version did you take ?

from what I read earlier on 38R you should flash FK R23 AOSP version
[ONE Original Android Development] ohhcrapitstim:
I tried the CM11S version, maybe that was the issue. I will try flashing the AOSP version first and see if that works.
[ONE Original Android Development] Spewmonic:
Life saver

This saved me a lot of time. Thank you for that. :)
[ONE Original Android Development] irony17:
Thanks for letting me know :)

To summarize :

you just renamed the .bak and then flashed from recovery ?

which version of R38 did you use ?
[ONE Original Android Development] andresantos:
so i should install aosp version of franco 23 for my otherwise stock cm11s rom? then ill be able to install the ota through twrp? i tried franco 23 cm11s version rename thermal engine and stilln not able to install 38R
[ONE Original Android Development] tcapote:
Do I rename before I boot to recovery or is there another way? I went to file manager in TWRP, and browse to the folder, but I don't see any files listed?

Thanks in advance!
[ONE Original Android Development] cypher21:
yes, thats what he said ;)

Guess FKU needs to be updated since that downloads the cm11s version
[ONE Original Android Development] gpelekanos1:
Same problem here
[ONE Original Android Development] ohhcrapitstim:
I renamed the .bak and then updated via OTA.
[ONE Original Android Development] gpelekanos1:
Franco, i flashed r23 cm11s kernel renamed the bak file and still cannot flash. Shall i instead flash r23 aosp kernel rename bak file and then flash OTA? Thx.
[ONE Original Android Development] shure2:
How strange all three of us have experienced this only in the last few days. Maybe the screen changes in r38 will get rid of these (if it all hasn't been merged in cm11 nightly already). Still its not a big problem, only experienced for a minute or 2 today.

When I disabled HW overlays the transitions got noticeably worse.
[ONE Original Android Development] Tzfardaya:
Rename file, flash OTA, flash kernel
[ONE Original Android Development] dmarden:
You guys are making this way too hard on yourselves, lol... presuming no other changes than running franco kernel, presuming running CM11S 33R, just:

1. Rename the thermal file as franco noted, then install the OTA. Then do nothing, just run the included kernel for now until things settle and franco gets stuff updated.

2. Don't rename the file and just install the OTA with the modified update script. Then do nothing, just run the included kernel for now until things settle and franco gets stuff updated.

:)
[ONE Original Android Development] irony17:
from what i understand you should :

1/ rename the .bak file

2/ flash OTA

3/ eventually flash FK R23 aosp version

did you uninstall xposed if you have it installed ?
[ONE Original Android Development] gpelekanos1:
That is what i did but cannot flash OTA.
[ONE Original Android Development] Tzfardaya:
Cm11s or aosp?
[ONE Original Android Development] gpelekanos1:
Cm11s, shall i flash aosp instead?

---------- Post added at 02:45 PM ---------- Previous post was at 02:44 PM ----------

The problem i have is that i cannot flash OTA i get assert error so cannot proceed anw.
[ONE Original Android Development] andresantos:
installing aosp version of kernel on cm11s ended up in a bootloop for me. good job i just made a backup
[ONE Original Android Development] vomer:
people on fk or people with mods on 33R - follow these steps to get to 38:

http://xdaforums.com/showpost.php?p=55882576&postcount=229
[ONE Original Android Development] ohhcrapitstim:
I just flashed the AOSP version and this solved my issue!
[ONE Original Android Development] Tzfardaya:
Have you renamed the file yet?
[ONE Original Android Development] Vonnegut:
Franco, you know i admire both you and your work...but, when you change a system file, you have to tell anyone about it in the OP.

Does the AOSP version of your kernel change that binary too?
[ONE Original Android Development] grilopt:
Sounds reasonable, or put in OP instructions to revert to stock.

Great work anyway! Thumbs up for you Franco!
[ONE Original Android Development] Tzfardaya:
Dirty flash rom to return to stock... Same as any kernel.. :P
[ONE Original Android Development] 1/4 Life:
Can't wait for the next Franco Kernel update! It's going to be great having a good version of CM11s again along with FK.
[ONE Original Android Development] zephiK:
Flash the aosp kernel for cm11s 38r and it'll work.
[ONE Original Android Development] 1/4 Life:
Have you done that already? There were a couple people earlier complaining about bootloops, though it sounds like some of them were thinking the AOSP version is a fix for 38R not flashing or something.
[ONE Original Android Development] zephiK:
http://xdaforums.com/showpost.php?p=55881369&postcount=4841
[ONE Original Android Development] 1/4 Life:
Yeah, the people complaining about bootloops came after that.

I guess I'll give it a try! Thanks for the heads up.
[ONE Original Android Development] fueleh:
So we need to wipe our phones?
[ONE Original Android Development] 1/4 Life:
Have you installed anything other than Franco Kernel?
[ONE Original Android Development] fueleh:
Hmm busybox and twrp app to update twrp and supersu is what i have.
[ONE Original Android Development] Tzfardaya:
Shouldn't... Just rename the file as Franco instructed earlier then try again... Worked for me, didn't even have to flash stock kernel
[ONE Original Android Development] 1/4 Life:
Same as me then, I updated fine. Tzfardaya has you covered.
[ONE Original Android Development] Tzfardaya:
I'm covering what now?
[ONE Original Android Development] P1f:
No we do not, at least I didn't had to.

What I did was:

1. flash CM stock kernel for 33R on top of Franco r23 (found it on google)

2. updated to CM 11S 38R (the version with the modified update scripts)

3. flash the CM stock kernel 38R (not sure if this was needed or if it was already included in the 38R update)

Now I am a bit afraid to try Franco AOSP, I will wait to see if he makes a r24 release for the CM 11S kernel or if he will keep only 1 kernel from now on.

So far the battery on stock kernel seems good, I will try and test it a little bit before putting back FK
[ONE Original Android Development] 1/4 Life:
As in your instructions are right and that's all he needs to do. I need not say more.
[ONE Original Android Development] vomer:
that process does not wipe your apps
[ONE Original Android Development] Tzfardaya:
Why afraid? It's working for me...

Odds are once the cm11s and cm11 nighties diverge again, he will need two kernels...
[ONE Original Android Development] P1f:
to be honest I believe is worth a try on the stock kernel as well, it makes me appreciate even more Franco's work when I can compare the 2 kernels
[ONE Original Android Development] fueleh:
Can u please link the files :) im not getting it to work...

EDIT: BTW i get incompatible data when i try to flash it, maybe not the asset error?

EDIT2: And i rename the file with cm fileexplorer but after reboot its back to .bak file.
[ONE Original Android Development] cyanoviper:
unfortunately renaming the thermal engine does nothing for me, i get an assert error for /system/app/Drive.apk o.O
[ONE Original Android Development] 1/4 Life:
You've got some other changes made outside of this Kernel. Check the CM11s thread, there's some tutorials on how you can fastboot a stock system image. Then you can update no problem.

Also, running great on AOSP Franco! Thanks a lot guys.
[ONE Original Android Development] dmarden:
Yeah, looks like you removed one or more system apps. Always better to freeze them than remove them for reasons like this.
[ONE Original Android Development] spelaben:
I renamed the thermal-engine.bak file, flashed the OTA zip with modified updater binary in TWRP and now I'm stuck at the boot logo. Tried to sideload today's AK kernel but still doesn't boot, does anyone have a .zip or .img for the stock kernel from today's ota or any other advices?

//Edit: Okay, found the boot.img in the OTA zip, flashed the img with fastboot and it's still not booting. :(

//Edit2: The OPO is recognized by my computer though and even shows me the contents of the sdcard, but the device still shows the bootlogo...
[ONE Original Android Development] vomer:
http://xdaforums.com/showpost.php?p=55882576&postcount=229
[ONE Original Android Development] Tzfardaya:
Just rename the file as instructed by franciscofranco then flash the OTA zip...

Use a file browser with root access... I don't know if the cm one does or not...

And try redownloading the zip.

---------- Post added at 12:16 PM ---------- Previous post was at 12:10 PM ----------

Are you using multirom?

If you renamed the dot bak file you shouldn't have needed the modified binary, just flashed the OTA zip as was...
[ONE Original Android Development] franciscofranco:
1 - Nobody really cares about the OP

2 - There's no need to tell people what I change all the time, 99% of you won't understand why and I can't be bothered to explain the reasons

3 - I made that change to disable the built-in thermal-engine daemon because I'm using my own Kernel driver now

4 - I posted instructions to update to 38R

5 - Yes, AOSP version does that change as well

:)
[ONE Original Android Development] franciscofranco:
I'm gonna repeat myself, for the last time. To flash the OTA you need to:

1 - Rename /system/bin/thermal-engine.bak to /system/bin/thermal-engine

2 - If you've made framework changes or uninstalled System apps you gotta reflash stock System.img (but that's outside my responsibility and you should know what you do to your phone).

3 - Get the ota.zip from whatever source you want

4 - Recovery -> apply update -> adb sideload -> choose the zip file

5 - After it boots up if you want to flash FK you need to flash the version INSIDE the AOSP directory as I already said before

6 - DO NOT AUTO-FLASH FROM FKU

7 - ???

8 - Profit.

I'm gonna update the production FKU today with the appropriate changes for auto-flash to work properly with all these new changes.
[ONE Original Android Development] dmarden:
Seriously... it's quite obvious virtually no one even reads the posts on the same page as their own question, let alone the OP or a post on any other page. :P
[ONE Original Android Development] spelaben:
No I'm not, I had another modified file error, some *.jar file. Suspected it might be xposed but just used the modified OTA instead of properly removing xposed.

Just followed vomers' instructions and everything seems to work now. :) Thanks!
[ONE Original Android Development] Tzfardaya:
Don't what?
[ONE Original Android Development] :
[MENTION=3292224]franciscofranco[/MENTION] with the new update, will there be just one kernel for CM11s and CM11, instead of AOSP kernel and CM11s kernel?
[ONE Original Android Development] franciscofranco:
Yes, but for legacy/compatibility reasons I will push the same versions for both cm11s and AOSP directories. They will be the same nonetheless.