yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] hughfollett:
Couldn't belive it either. Watched "Shutter Island" and "The Prestige" on the train in those 8 hours too!!
[ONE Original Android Development] mamba720027:
Oh I haven't come around to testing out video playback drain per cycle so good to know. I been watching "Arrow" on Netflix. Will see how it does on WiFi + Netflix a day. The governor/cores scales nicely.

This what my current drain n usage looking like with a -100mv ish undervolt across the CPU I'm playing with.
[ONE Original Android Development] hughfollett:
Oh I wasn't streaming tho, the movies were on the phone storage. I don't play with uv, never seen any real advantage and I don't want to mess with it. Sind good governor settings like Franco's one are better
[ONE Original Android Development] kaibosh99:
Thanks, I have been waiting for something like this. The screen on the OPO is sharp as franco's teeth but every time I turn on my Note 2 I realize how lifeless the colour is. Hoping to gain something back from your tweaks... ;)
[ONE Original Android Development] mamba720027:
Yep I knew that :D

The UV just helps reduce heat energy and keep the device at a cooler temperature which in turn reduce battery drain. But yea it don't bring that big a difference unless u undervolt the CPU/GPU/ Memory and board. Which is alot of work I believe for the dev's to implement I'm assuming.

Hope it helps then. I couldn't go back to the normal stock colors after playing with those RGB color adjustments :p
[ONE Original Android Development] Rycon33:
This 'lost sdcard partition' happened to me last time when I flashed via "flashify" app. I thought maybe a reboot could solve it but didn't, instead I was greeted with even another issue "CMlockscreen has stopped". I then booted in twrp and wipe cache/dalvik cache, problem solved afterwards, sdcard partition is back and cmlockscreen fc is gone also.

I normally don't wipe cache/dalvik cache when I flash kernel but that step did it for me when I encountered those issues I mentioned above. I stopped using flashify app since then, to avoid encountering same issue again.

Anyways, I was only pointing out the same issue as yours that I encountered before. Yours could be due to other things, we don't know.
[ONE Original Android Development] paychex:
[MENTION=3292224]franciscofranco[/MENTION] I'm still getting reboots. When I looked at the logcat yesterday I saw and error message "E/QCOM PowerHAL( 808): Failed to acquire lock." and "E/QCOM PowerHAL( 229): Invalid hint ID." spamming the log. I flash system and boot via fastboot and the spamming went away on the CM kernel

http://pastie.org/9690615

and returned on FK

http://pastie.org/9690625

Hopefully something here can help for anyone getting random reboots

Also. He's the latest last-kmsg http://pastebin.com/rRqEZuMy

A lot of fast charge stuff spamming it I haven't seen before
[ONE Original Android Development] kaibosh99:
I wipe my dalvik/cache if I so much as change my wallpaper. I wipe my dalvik/cache more often than I wipe my own hairy ass.
[ONE Original Android Development] franciscofranco:
Nice troll, you caught me there :)

Those power hal thingys are related to the MPdecision being disabled, don't worry.

I can't understand those random reboots. Your sensors are just ****ing up and keeping your device awake all the time, WLAN sometimes as well, some other display related wakes too probably from the gestures... there's no actual error... I don't know dude, I strongly suggest a full re-install from scratch.

You're doing something very very wrong if that is the case. :cyclops:
[ONE Original Android Development] paychex:
Thanks for the help. That's what I'm working towards... but trying to avoid. What I don't get is that the phone deep sleeps around 70% of the time. It must be some app starting that then goes bat **** crazy.
[ONE Original Android Development] franciscofranco:
Maybe... Or simply corrupted /persist or some other **** I don't wanna go into. The sensors keeping your device awake a long time scares me a little.
[ONE Original Android Development] guitarhero2:
Thank you for this awesome kernel francisco! The battery juat doesn't want to go down [emoji16]
[ONE Original Android Development] ken_alpha24:
Kernel settings?
[ONE Original Android Development] guitarhero2:
All stock, -75 undervolt
[ONE Original Android Development] ladarkphoenix:
?

Where do you undervolt? I'm very new to this whole stuff, would happy if you could answer.. my battery is **** on my OPO and I just installed the kernel
[ONE Original Android Development] kimikim0:
hey sir, what app you use for kernel setting, undervolt etc. ? tq :)
[ONE Original Android Development] Roman91:
must buy the FKU app (about 4$) ..or dont know...try some other app for kernels (boeffla app, kernel tuner ec)
[ONE Original Android Development] guitarhero2:
I use fku paid for setting up the kernel :) otherwise you can use trickstermod
[ONE Original Android Development] souljaboy:
Thats what I have too. Personally had 10h48min as max. No wifi off though.

Ak kernel never came close. I was doing 5-6h screen times, franco always has 8-9.5h, with same setting.
[ONE Original Android Development] dafonehacker:
[MENTION=3292224]franciscofranco[/MENTION] the cpu frequency still goes to 2.5 ghz on the battery saver profile after waking the phone on r30 for me.
[ONE Original Android Development] involver:
[MENTION=802807]guitarhero[/MENTION]:

Is that on r30? 'Cause I just rolled back to r28 because of some huge drain. On r28 I did 2d 6h+ :good: with normal usage (ie MY normal usage pattern) and approx 4 hrs SOT. BUT after flashing r30 all went tits up and I've lost 50% in just 8 hours :silly: .... rolled back and afaik battery usage is back to what I was used to. No different apps installed, just simply flashed r30 two days ago and flashed back to r28 today...
[ONE Original Android Development] elderonj:
I've always used Franco kernel, today I've tried to flash AK kernel but the WiFi doesn't work. So I flashed back franco and everything is OK.

I've tried with the stock kernel and I've obtained the same result: the WiFi doesn't work.

It seems that it lacks something when I flash a kernel different from Franco kernel.

In both case I've also tried to wipe cache and davlik
[ONE Original Android Development] Theshawty:
Reflash the ROM before flashing another kernel. This issue has been mentioned a gazillion times before.
[ONE Original Android Development] franciscofranco:
Uh... are you sure you don't have anything doing that for you? A Tasker profile, some app you set up, some script... because see the code: https://github.com/franciscofranco/one_plus_one/commit/1a900c31b90f861f650f916974b7169f06f4047a

I'm saving the frequencies in a struct before the devices goes to sleep, and when it wakes up I'm restoring them back, so if before sleep the freqs were 1GHz, they are restored after wards. It works flawlessly for me, I've tested it extensively...

It's been mentioned a gazillion times. Starting with r31 that won't be needed anymore and I'll provide a .zip to restore the Wi-Fi firmware to stock for users who been flashing and have the different firmware.
[ONE Original Android Development] dafonehacker:
No not that I know. Does a logcat show the saving/restoring of the frequency? If so, what should I look for?
[ONE Original Android Development] guitarhero2:
Yes, r30.
[ONE Original Android Development] franciscofranco:
cat /proc/kmsg does. Something like this if you're with that Power-saving profile:

// good night

<6>[ 4465.241342] CPU0 -> 1036800

<6>[ 4465.241398] CPU1 -> 1036800

<6>[ 4465.241435] mako_hotplug: suspend

// good morning

<6>[ 4467.241342] CPU0 -> 1036800

<6>[ 4467.241398] CPU1 -> 1036800

<6>[ 4467.241435] mako_hotplug: resume
[ONE Original Android Development] dafonehacker:
Found something: it said CPU1->2457600

In the //good morning part

CPU0 is correct and now I noticed it's indeed only the second core going beyond 1 ghz. I'll upload a full log of it later if needed because I was just looking in terminal emulator and my device's battery is almost dead. Here's a screenshot though.
[ONE Original Android Development] franciscofranco:
Interesting...

I'm reworking my suspend/resume routines on the Hotplug driver based on your report. I'm not entirely sure how that disparity between cpu0 and cpu1 max freq happens, but I got some ideas.
[ONE Original Android Development] ravvio:
After a lot of reading i went for purchase of your kernel franco hope to see some good results. Also will report any issues or feedback upon use. Hoping for the best.
[ONE Original Android Development] franciscofranco:
Can you test with the attached boot.img please, as soon as possible.
[ONE Original Android Development] dafonehacker:
Just tested it and this is strange: in the logcat it now shows the correct freq for cpu0 and cpu1 when resuming, but system monitor still says the second core operates at freq higher then 1 ghz.
[ONE Original Android Development] franciscofranco:
It's not logcat, it's the Kernel log.

My system monitor shows everything fine.

There's nothing that I can do more than this, I'm working directly with the cpu policies in the Kernel.
[ONE Original Android Development] paychex:
Flashed userdata as well. Is that where /persist resides? I wouldn't mind you going into detail.
[ONE Original Android Development] franciscofranco:
/persist is a separate partition. It's probably not your problem, I did some reading and with the fsck check on boot the partition is recovered if for some odd reason it gets corrupted.
[ONE Original Android Development] paychex:
that's above my head, but I appreciate the effort
[ONE Original Android Development] dafonehacker:
I tried a few more times: set profile, lock, wait +-10 seconds, unlock. every time the kernel log shows the correct values, but all apps I tried (cpu z, perfmon and system monitor) still showed frequencies above 1ghz on cpu1 on their live monitors. When I quickly lock/unlock immediately, it works as it should, sometimes. I'm running cm11s and I'm almost certain there's nothing else on my phone that could mess with that. Is there anything else I can try or log? Should I provide a full kernel log from boot to end? (if so can a kernel log contain personal information? Otherwise I'll have to search it completely)

I can also flash a stock cm11s zip in multirom (if multirom doesn't impact the way the kernel or profiles functions) and test it on that? I just find it very strange and irritating that I'm the only that has this issue. If some other people can test?
[ONE Original Android Development] chr0m:
Ok, after a week of touchscreen issues, someone suggested going back to r26. I did and my touchscreen has been fine ever since.
[ONE Original Android Development] nicola1989:
Guys small ot, If I wanna exit from the beta app and came back to the old app. What I have to do?

---------- Post added at 11:28 PM ---------- Previous post was at 11:25 PM ----------

Edit : found my self
[ONE Original Android Development] zephiK:
Leave the opt in for the FKU Beta app and then uninstall app, reinstall app from Play Store and you'll go back to the non-beta app.
[ONE Original Android Development] ajpatel:
I'm running the FKU beta app and on power saving profile. I tried undervolting -75 mV but it didn't stick in the settings even though I hit apply on boot.

And another question is any other ideas for reducing that battery drain during screen on times? The idle battery load is down phenomenally.
[ONE Original Android Development] paychex:
Just got a reboot with a complete wipe. last_kmsg pretty much the same.
[ONE Original Android Development] jahrule:
Can someone confirm this because I am still having touch screen issues.
[ONE Original Android Development] Technecium:
Try flashing r26. Then you will know.
[ONE Original Android Development] bluedragon1982:
r30 is the first Kernel i get sporadic "ghost touches" with
[ONE Original Android Development] Technecium:
Just had a reboot on restart.

I'm on 38r and r30. I had updated my host file via Adaway and rebooted the device. I looked at the device, it had successfully booted up to my launcher. I looked away and back again and it was at the boot logo screen. I grabbed this last_kmesg.

http://www.pastebin.com/06a0480N
[ONE Original Android Development] N4Solomon:
Confirmed!! Went back to r26 and after several hours of tweeting no ghost touches

My WiFi seems to be working fine again after dirty flashing my rom and flashing r26
[ONE Original Android Development] someth1ng:
Yeah, r26 has really nice touch.
[ONE Original Android Development] europizza:
R30 (but it happened with a previous version too) at boot I had the min CPU clock at the same of the max instead of 300mhz. It's only the second or third time since I run Franco. Also I hadn't the min CPU applied at boot (on the kernel settings) , like the max CPU, so that my solve the issue. Just to report.
[ONE Original Android Development] amirnew:
Can I flash the kernel with twrp on stock 38r os right away? As a regular zip.

Or should I do something special.

Thanks

Amir
[ONE Original Android Development] theooo:
Nope, just flash kernel zip via twrp. Make sure you're using the correct version for cm 11s.
[ONE Original Android Development] chr0m:
Touch still fine on r26 here. It can't be coincidence. I had an awful time for a week on various newer versions of FK. whatever commits CM have made, they didn't agree with my device.
[ONE Original Android Development] franciscofranco:
Those of you saying "omg r26 touch is better" just so you know all touch related changes are simply merges from CM, in this case, the touch panel firmware and it's not related to FK per-se.

Sorry, I cannot reproduce at all.

Your signal is raping your battery...

I don't have a clue then. I suggest you to run 100% stock.

There was a crash on the internal sdcard:

[ 87.890084] mmc0: Timeout waiting for hardware interrupt.

It timed when waiting for an IRQ (no clue why) and then all hell broke lose. MMC drivers are 100% stock, so unrelated to FK.

That's impossible unless you have some script or app doing it for you.
[ONE Original Android Development] ajpatel:
[MENTION=3292224]franciscofranco[/MENTION] anyone else having issues with undervolting not sticking in the FKU beta?
[ONE Original Android Development] irony17:
same here. + on max frequency going back to max.

I have to reboot the device and then everything goes back to normal
[ONE Original Android Development] xythiii:
I've seen a video on youtube a fast scrolling mod flashed on fk kernel, can you include that in next r31
[ONE Original Android Development] franciscofranco:
That's not Kernel related AFAIK.
[ONE Original Android Development] paychex:
I am now. Still getting reboots. Pretty sure it's an app causing it. Trying to find the culprit. Again, thanks for looking through a ton of logs
[ONE Original Android Development] Technecium:
Fair enough. I did have an otg device connected recently so maybe something buggered there. Thanks for checking.
[ONE Original Android Development] franciscofranco:
Pushed r31:
[ONE Original Android Development] jukiewalsh:
Did fku get a material update at some point I missed?
[ONE Original Android Development] EnterLordVader:
Awesome!

Compatible with Nov 2nd Mahdi?
[ONE Original Android Development] 1/4 Life:
Flash and find out

FKU Beta
[ONE Original Android Development] 1337jay:
Working perfectly on Mahdi 1102, flashed WLAN_stock_firmware.zip before the kernel via TWRP.
[ONE Original Android Development] franciscofranco:
Not yet finished. I was 4 days in London which practically rendered coding time null, and now back in Portugal I've been working on Kernels. Wrapping things up for FKU for the next days.
[ONE Original Android Development] wrinklefree:
Hmm lost my cellular connection after flashing R31.
[ONE Original Android Development] dafonehacker:
So with the new WiFi driver location, does that mean that it stops breaking WiFi on other kernels? So when we want to try a different kernel all we have to do is flash it?
[ONE Original Android Development] 1337jay:
Correct, no need to dirty flash rom again before switching.
[ONE Original Android Development] jmazzamj:
WLAN drivers on AICP

I'm running AICP 11.02, based on CM.

Shall I flash the WLAN firmware before I update to R31?

What about next time I update AICP? Shall I flash it every time I update my ROM?

What if I change ROM?

Thank you
[ONE Original Android Development] 1337jay:
You should first flash the firmware and then the kernel. If you update/or change your rom you will just have to reflash the kernel.
[ONE Original Android Development] LoveMyNewTelephone:
Is it recommended to flash the WLan before upgrading to r31?
[ONE Original Android Development] 1337jay:
It doesn't matter untill new OTA or switching to another kernel I guess. But it only takes a second so why not.
[ONE Original Android Development] LoveMyNewTelephone:
If doesn't hurt, I would prefer that, so everything works out of the box when I flash an OTA
[ONE Original Android Development] hanny562:
Seems like there is some problem of version r31..I get bootloop after update r31 from r30
[ONE Original Android Development] franciscofranco:
Coincidence.

Yes. You only need to flash it once, from r31 onwards it doesn't inject the files anymore.

Read my post above.
[ONE Original Android Development] franciscofranco:
No there's no problem with r31.
[ONE Original Android Development] hanny562:
But it's weird I have try update through FKU and also download and flash it manually..but still get me into the bootloop..now i'm flashing back to r30 and try again
[ONE Original Android Development] Peri-:
Edit: nvm.
[ONE Original Android Development] matrixceccano:
maybe post it in first page ... is better?

do not need to write "****ing" in any response, I use your kernel for years ... I bought your app ... and obviously I have not found an answer with a search .. and I took the liberty of asking here ...
[ONE Original Android Development] vomer:
Flash WLAN -> Flash r31 -> ponies!
[ONE Original Android Development] Theshawty:
He has to when people keep posting useless crap or ask the same question that's been asked a lot.

Franco is a human being, believe it or not and even his patience can run out.
[ONE Original Android Development] EnterLordVader:
Link to WLAN please?
[ONE Original Android Development] edgie168:
Dude, franco tells you exactly where to download it in the changelog.
[ONE Original Android Development] Tzfardaya:
Perhaps you need to practice your search skills more...

Some suggestions to improve.

-Use search this thread instead of search xda (bottom Search bar on browser, not top)...

-Try multiple sets of search terms.

-dug deeper into search results, your answer may not be on the page, unless you have dialed in your terms perfectly..

Using a single search, I was able to find a dozen answers to your query, not counting the several times Franco himself had answered that same question previously..
[ONE Original Android Development] droodski:
So if I am coming from r30, I don't need to do anything but upgrade to 31?

Or should I still flash the zip and then upgrade to 31
[ONE Original Android Development] franciscofranco:
Whatever you want. I think I've explained it well enough in the changelog.
[ONE Original Android Development] Theshawty:
Flash the zip, then upgrade.
[ONE Original Android Development] alpha2zulu00:
I've been trying to use this kernel since r28 and am still having Wifi issues. Completely stock, signed into Play Store but no apps installed, then I install this kernel and my wifi blinks off an on intermittently. I like the performance when I'm on the go but I'd rather not waste my data when I'm at home or in the office. Any guesses as to what's wrong?
[ONE Original Android Development] vomer:
http://kernels.franco-lnx.net/OnePlusOne/WLAN_stock_firmware.zip
[ONE Original Android Development] Theshawty:
Does that happen even with r31?
[ONE Original Android Development] alpha2zulu00:
Yes it does, I just finished testing it.
[ONE Original Android Development] Theshawty:
Have you tried wiping data?
[ONE Original Android Development] FSOP:
Flashed wifi zip and updated to r31, no issues here
[ONE Original Android Development] alpha2zulu00:
Hm not immediately before flashing the kernel, I think. I'll try that now. Meanwhile here are some of my previous posts, for reference. I'm suffering the same symptoms no matter what I try.

I am running stock CM11S 38R. Flashed this kernel, WiFi goes wonky. After switching to AK it works fine...
[ONE Original Android Development] Theshawty:
Try reflashing the system and boot images from 38R, then flash Franco r31, then report back.
[ONE Original Android Development] Tzfardaya:
Have you tried a clean reinstall of the rom, then flash Franco?
[ONE Original Android Development] alpha2zulu00:
Just completed the following:

1)Performed factory reset (wipe data)

2) Put phone in Fastboot mode.

3) Downloaded factory zip from https://cyngn.com/products/oneplusone/

4) Extracted system.img and boot.img from zip

5) fastboot flash system system.img

6) fastboot reboot-bootloader

7) fastboot flash boot boot.img

Okay so what should I do now? Flash the franco boot.img, then try it out?
[ONE Original Android Development] Theshawty:
Yes, exactly!
[ONE Original Android Development] alpha2zulu00:
Mmkay done. And, no good.

WiFi stays on for a few seconds, goes off for 5, comes back on. Repetitively.
[ONE Original Android Development] Chikko:
With r30 i had a great battery drain, only sot 2 over 13h of standby...
[ONE Original Android Development] nikzDHD:
Totally opposite of what I experienced. I had good battery life. It's not the kernel check for rogue apps and such as mentioned many times in this thread.
[ONE Original Android Development] jmazzamj:
Thank you, Franco, very appreciated.
[ONE Original Android Development] shadeofgrey:
On newest mahdi 11/02 and when I flashed r31 all my apns disappeared. Not sure what happened. Have no cellular connection either.
[ONE Original Android Development] Vonnegut:
That reminds something that is not to supposed to happen anymore...

Are you rooted? Check the persist folder in the root of your phone...is that empty?
[ONE Original Android Development] shadeofgrey:
Reflashed rom, reflashed r31 and all seems to be fine now. Didn't get a chance to check the persist folder.
[ONE Original Android Development] Vonnegut:
Fine :good:
[ONE Original Android Development] thepktrckt:
Hmm I did it backwards didn't I?

I flashed R31 and then the WiFi zip. Had to restore to r30 to get wifi and cell back.

I've read the change log and the order wasn't clear to me but I don't claim to rise much above the level of dummy.

So it's WiFi zip and then R31?
[ONE Original Android Development] Tzfardaya:
Did the wifi work properly after flashing system and boot but before flashing Franco?
[ONE Original Android Development] franciscofranco:
Doesn't matter which order, absolutely irrelevant, the zip is just to allow the next OTA to flash, nothing else.