yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] magnamentis:
contradictory a bit :)

so if you have no consumers there will be no consumption. so if you have high consumption of juice you have to have consumers. conclusion, if you are not that consumer in terms that you know what exactly consumes your battery by using the device and its resources willingly, then you MUST have background tasks that cause it and thus MUST have wakelocks. whether a wake lock is weird, or not is partly subject to you judgment but if you have a sub-optimal battery life and at the same time deny that something weird, unwanted, unknown and/or unexpected is going on ( is consuming your battery ) you restrict yourself and the probability to find a solution. there is no magic in physics :) if your phone is consuming power ? then search the consumer, it must be there. solutions can only be found when the problem is recognized and admitted. a certain amount of work lays seemingly ahead for you :)

EDIT: if nothing else works, then [MENTION=3685904]ak[/MENTION] 's solution a few posts before thisone is certainly the way. clean install, format everything possible and start from scratch without gapps and user apps and add them in increments until the device starts to misbehave.
[ONE Original Android Development] shaker2k:
Just my 2cents. If you guys have location, google search from any screen, sync, or any other thing on you will get wakelocks. Expecially with location and Google search on.

To me that's called using your phone and not disabling everything. If I can get through the day with 4-5 hours sot and still have 20 to 30% battery. I'm a happy camper.

The beauty of this phone and the big battery is the ability to run with everything on and not have to charge during the day.
[ONE Original Android Development] polaris68:
Been having major app freezes and lags with the slimsaber May 31 and AK254 + per panel firmware combo. Just flashed the freeze test kernel and will report back but initial impressions are that it has solved the problem.
[ONE Original Android Development] wcn:
Reporting that AK256 is working great with EuphoriaOS as always. CPU: Smartmax, mV: -75. So far so good, no problem.
[ONE Original Android Development] néonaloj:
Does it mean you don't recommend we use 69mHz under interractive???
[ONE Original Android Development] gianton:
Latest SlimSaber with v.256 everything is rock stable as usual.
[ONE Original Android Development] clock51:
I use Euphoria as secondary MultiROM, AK256 does not have problems with this rom, my SETTING, UV -75, GOV smartmax CPU, I / O fiops, CPU freq min 69 max 1958
[ONE Original Android Development] bakshi:
Sunlight enhancement in 256

Thanks AK for releasing the new Synaptic driver. Just flashed 256 on my PA 5/28 build.

The only bug which I've encountered is "Sunlight enhancement" re-enabling itself after every reboot.
[ONE Original Android Development] CorB3n:
Flashed with stock kernel everything works fine except ghost touches.. For me [MENTION=3685904]ak[/MENTION] your kernel is not compatible with slim saber... With no reasons...
[ONE Original Android Development] Chevan94:
I personally suffer from random touches all over the screen on Euphoria 1.1. It happens randomly during usage. It looks like you placed your whole palm on the screen and moved it around. Never happened before version 256.
[ONE Original Android Development] HamsterHam:
So far no issues with 256 on SlimSaber. Will keep you posted if there are issues [MENTION=3475639]ak.[/MENTION] ?
[ONE Original Android Development] S@lvatio:
will this kernel work on cm11s..

any issues
[ONE Original Android Development] kantjer:
Let me tell you a secret (hardly anybody knows this) try entering "cm11s", in that order, in the search box on top of this page and hit the enter button and watch the magic happen.

But please don't tell this to anyone :silly:
[ONE Original Android Development] GeoTox:
Guys should i re-flash my ROM if I have never flashed a kernel before? I'm on COS12. I have only flashed a radio from OxygenOS.
[ONE Original Android Development] kantjer:
if you haven't flashed a custom kernel on the ROM you are now using there is no reason to re-flash the ROM.
[ONE Original Android Development] GeoTox:
Thanks!

And what is the difference between this kernel and stock COS12 one? I have searched a lot, but haven't found an answer. I understand that there's some changes in TouchScreen drivers and better performance/governor settings. Is there any other major difference? Thanks!
[ONE Original Android Development] Jole7:
Yes there is it's called speed!!
[ONE Original Android Development] GeoTox:
Lol, thanks! Will try this kernel. Hope I won't mess up my phone :D
[ONE Original Android Development] ak:
What is the problem ? You can revert in one second.

Sent from my A0001
[ONE Original Android Development] ak:
Good to know [emoji18] [emoji18] [emoji18]

Sent from my A0001
[ONE Original Android Development] GeoTox:
After installing Synapse app, will it change something in system settings or will it just get default values from system?
[ONE Original Android Development] EasyGoingXD:
[MENTION=3685904]ak[/MENTION] got one blackscreen with the newest v.256, no error in logfile sry :/ going to try the newnew v.256 for slimsaber...btw running slimsaber so hopefully this will help :)
[ONE Original Android Development] tenkaishy:
Governor

Sorry if this is a stupid question, but im not good in all the kernel related stuff, but just to know what governor do you guys use that is good in term of smoothness and battery life. Im using interactive but from what i understand is that it can be less good for the battery life?

Thanks for the help
[ONE Original Android Development] CorB3n:
Lot of ppl with slimsaber & AK kernel got black screen/freezes etc. How can we help to investigate ? That's crazy we just can use combination of best ASOP ROM and best KERNEL :silly: :silly: :silly:
[ONE Original Android Development] EasyGoingXD:
Best AOSP rom?, best rom EVER!
[ONE Original Android Development] CorB3n:
As perfect as Euphoria @ CM ;)

But I really appreciate Slimsaber with fusionjack's reactivity, listening users. I'm so frustrated to not being able to continue on it..
[ONE Original Android Development] GeoTox:
I was using SmartassV2 on my Xperia Arc S and it was quite good! Also I remember that Smoothass and Lagfree were pretty good too. But I can't tell how this governors work with 1+1.
[ONE Original Android Development] ak:
You can flash the test version posted some post ago if you want

Sent from my A0001
[ONE Original Android Development] ak:
I'm using cm12.1 nightly for verify possible problems but all is OK for now (2gg)

A lot of YouTube + castscreen

Sent from my A0001
[ONE Original Android Development] Spaulding89:
Hm it's really strange that for some people like me the Kernel with Slimsaber works and for other not.

Sent from my slimmed Bacon
[ONE Original Android Development] CorB3n:
Using AK 256 exp on Euphoria right now, everything is working fine... Don't know why on it it works & not on slimlp
[ONE Original Android Development] ak:
i don't know, i'm not a rom maker.
[ONE Original Android Development] anjo88:
I use with cm12s my phone freeze 2 times in 30 minutes when I goo to ak app to export log log out in blank any tip?
[ONE Original Android Development] ak:
Please use test kernel posted before.

Sent from my A0001
[ONE Original Android Development] brath23:
Ak 256 working Perfect here with Cyanogen OS 12 with kernel stock settings.

It's still early to tell about battery life but I think it's safe to say there is no abnormal drain
[ONE Original Android Development] Chevan94:
I mentioned that the digitizer goes crazy sometimes on Euphoria. See attachments.

I disabled all gestures. Reverting to stock kernel (or earlier version of the kernel) fixes the problem.
[ONE Original Android Development] robbieast:
Im using latest AK version and slimsaber.

i can't change wifi scan interval. any one else facing this issue?
[ONE Original Android Development] DJMartini:
Same issue here and I'm on temasek, but I think ak already caught this and fixed it in next release.
[ONE Original Android Development] HamsterHam:
No more freezes for me on SlimSaber using AK.256.OPO.CM12.1.zip
[ONE Original Android Development] Aurellion:
I also have the issue with random freezes. It first occurred on Cyanogen OS, so I tried out pure CM12.1 and after having the same problem there I'm now on SlimSaber. The problem occurred beginning with v251 and is still present with the new test version 25X in all the above mentioned roms.

Could this be a device specific problem, cpu revision or something like that? [MENTION=3685904]ak[/MENTION] Your trying (test build and concern for us etc.) to figure that out is much appreciated, thank you.
[ONE Original Android Development] ak:
yes its fixed in the new version.

how i can replicate the problem?

good
[ONE Original Android Development] ak:
you have to wait rom update.
[ONE Original Android Development] CorB3n:
Euphoria, Tk Gapps,AK Kernel, same crash. Definitely a problem with it. Do I have to tweak smthing I forget ?!?!
[ONE Original Android Development] anjo88:
I flash new freze kernel I will give feedback soon
[ONE Original Android Development] ak:
At this point I don't know I'm waiting a crash on my phone .... [emoji18]

Sent from my A0001
[ONE Original Android Development] CorB3n:
Maybe Synapse problem, have you a link to the latest with battery drain?
[ONE Original Android Development] Aurellion:
I can't say how to replicate the error, the logs seem clean and the freezes just happen randomly, also without usage the phone crashes and reboots. So I just install the kernel and wait, it never took more then one h to see it happen.
[ONE Original Android Development] ak:
Noo impossible.

Sent from my A0001
[ONE Original Android Development] ak:
Softreboot?

Sent from my A0001
[ONE Original Android Development] Aurellion:
The last time it was a softreboot, but most of the times I didn't wait and did the reboot myself.

For now I'm back on v141 and no freeze since 50min.
[ONE Original Android Development] ak:
What ROM? V141 is too old .... You using an old one.

Sent from my A0001
[ONE Original Android Development] king conan:
Running fine the latest AK kernel with latest temasek rom. Thank you AK!

I had ghost touches and with the test kernel and the one of today, screen works great, responsive and fast like new.

I would like to ask AK and the rest of you your opinion.

I was so tired of customer service and I was so sure the screen issue is a design flaw that a asked a refund to paypal and it was approved yesterday. Now I have 10 days to return my phone and get my money back.

BUT,

The new screen driver inside AK kernel actually works great so it's real, not a workaround, I guess.

So, now I have to decide if the famous ghost touch issue is no more a problem with the new driver or it is masking a hardware issue (with constant recalibration as some people say in official forum)...

What would you do in my case, return and refund or keeping the phone with big dose of faith?
[ONE Original Android Development] Aurellion:
Yes it is old, but no freezes.

Now I'm on SlimSaber, where the freezes occurred from v251 onwards.
[ONE Original Android Development] kantjer:
I'm jealous at you guys, no matter what I try I can't get my phone to freeze or random reboot ;)
[ONE Original Android Development] EdgA#1:
Me too, Power using, turn on off, playing surfin no Crash... Slimsaber and ak... No problems, only Problem, no FC ?:D
[ONE Original Android Development] m4ssnet:
Ok, ak you are GOD.

Finally fixed my touchscreen... So it was only a sw problem ! Wtf!!

Sorry but i'm happy ;)

I was certain tha it was the display (ghost touch and non respons touch), now it's all fixed !
[ONE Original Android Development] Spaulding89:
+1 my friend

Now i thought maybe the people with Problems used xposed before and maybe xposed isnt complete deleted and because of this the Problems appears. Just my thought...

Sent from my slimmed Bacon
[ONE Original Android Development] ak:
+1

Sent from my A0001
[ONE Original Android Development] :
I use Dirty Unicorns with xposed. Never had freezes or reboots.
[ONE Original Android Development] ak:
This phone have a very low cost ... I love it ... And it perform very good.

I don't know if you have to return to vendor ....

This is your decision .... Test the new drivers for some days for verify if all is fixed.

Thanks a lot for support.

Sent from my A0001
[ONE Original Android Development] abhi08638:
[MENTION=3685904]ak[/MENTION] I'm thinking about adding a build.prop editor in synapse. Although you wont be able to directly see the build.prop, you will be able to search for/add/delete lines. I'll let you know how it goes :thumbup:
[ONE Original Android Development] 1ceb0x:
So let me share my story. I have latest AK kernel 256, latest SlimSaber 31 May. My phone is a PVS 9, SPEED 3 - it can whitstand heavy undervolt -75 uV. I personally only went as far as -65. Now.. in my current combo, it was set at first, at -60. After a few hours, opened camera, bam! freeze + soft reboot. when it booted up, in 10 seconds got another freeze. Then i decided to turn off the gauges and went to -50. Got another freeze but after many hours later. Now i keep it at -35 uV and I had 0 freezes/reboots etc.

Maybe... you guys are having cpu min at the lowest point 69, paired with a heavy -uV (which at 69 will be pretty low), and your phones cannot take it?

How many of you with reboots/freezes have stock -uV and stock cpu speeds?
[ONE Original Android Development] ak:
Oh yessssss [emoji350] [emoji350] [emoji350] [emoji350] [emoji350]

Sent from my A0001
[ONE Original Android Development] kantjer:
My phone also is a PVS 9, Speed 3, I don't undervolt, minimum CPU frequency is set to 146 MHz and the phone is stable as rock
[ONE Original Android Development] Formhault:
Not sure how you guys get SODs and random reboots and fire raining down the sky, but I uv`ed by -75mV and it still works fine :confused:

PVS 8, Speed bin 3 (for what it's worth).

ROM : Euphoria. But I've been on CM12.1 with the same setup and free from issues, too.
[ONE Original Android Development] Aurellion:
I had the same thought, I have pvs 10, speed 3. I tried all the new versions of the kernel without any uv. Doesn't help with the freezes.
[ONE Original Android Development] HamsterHam:
[MENTION=3685904]ak[/MENTION] - noooo, got my first freeze. Time to test freeze experimental kernel.
[ONE Original Android Development] jmascarell:
Last release with SlimSaber crashed my OPO. I can't boot into the room even using the UKM AK Uninstaller. What can I do? Thanks
[ONE Original Android Development] Aurellion:
I will now check at which version the error starts to occur, maybe that helps.
[ONE Original Android Development] kantjer:
Flash the ROM again and stay on the stock kernel for now.
[ONE Original Android Development] 1ceb0x:
are you using stock settings? it's worth to mention at least...
[ONE Original Android Development] ak:
This is fantastic.

Sent from my A0001
[ONE Original Android Development] kantjer:
True, that's the risk with a highly tweakable kernel like this one. So many ways to f***k up.
[ONE Original Android Development] jmascarell:
I did it 4 times and it keeps crashing on the boot animation and then restarting again (bootlop?)

EDIT: It's strange because it only boots when the USB is plugged in. When I disconnect the phone from the USB it freezes and restarts.
[ONE Original Android Development] kantjer:
If your phone doesn't even boot with either AK or stock kernel then there is most likely a problem with your data/settings

Restore a backup, or do a clean flash.
[ONE Original Android Development] ak:
Your data is corrupted probably .... You have to doing a clean install.

Sent from my A0001
[ONE Original Android Development] 1ceb0x:
Uh oh... sorry for OT - i thought it might be news to some :)
[ONE Original Android Development] dev0lver:
Pvs 10, speed 3 by me

Undervolting - 75 every time, rock solid, no crashes for more then 10 versions of kernel

One time I had - 95, also without problems, but I don't need to go extreme
[ONE Original Android Development] néonaloj:
I think you've missed my question? Does this mean you don't recommend to edit cpu frequencies to 69MHz?
[ONE Original Android Development] HamsterHam:
Stock settings, pvs and speed bin 3.

Flashing experimental screen freeze kernel now.
[ONE Original Android Development] ak:
No you can use without problem.

Sent from my A0001
[ONE Original Android Development] Formhault:
PVS 3?!
[ONE Original Android Development] ak:
Can you try to test kernels from 251 to 254 please ?

When the problems begin?

Thanks

PS

Have you try to flash cm12.1 latest nightly and then slim ?

Sent from my A0001
[ONE Original Android Development] Formhault:
Low PVS should mean... higher voltages :eek: Oh well...
[ONE Original Android Development] jmascarell:
Thanks! It's done and fully working right now. I'm gonna wait for the compatible kernel.
[ONE Original Android Development] mapolidori:
I'm running 256 on the latest euphoria. UV -50 global, have tried multiple governors with no issues at all. And I was having serious touch issues, which are now completely gone. Battery life is also back to what it was before the TC versions. As always, it's a solid kernel that gets better with every version.
[ONE Original Android Development] ak:
For all users:

I think the best is a clean install bit before the preferred ROM a dirty flash of the latest cm12.1 nightly.

Thanks a lot to all for support ....

Sent from my A0001
[ONE Original Android Development] HamsterHam:
Okay, I'll do that. I'll run 251 tomorrow and everyday move up if I don't get a freeze. You sure you don't want me to test the screen freeze test kernel @ak?
[ONE Original Android Development] Formhault:
@ak

I don't think the Charge Levels Interface in Synapse is reporting input current correctly. It says 513 ~ 803 mA (it jumps up & down quote a lot), while my charger doctor reports 1.20A (charging off of a charger limited to 5V~1A).
[ONE Original Android Development] Mecca EL:
Crap, my device just froze, on 256. I'll check logcat to see what happened. Reboot seems non responsive also. I'll uninstall UKM, and reinstall 256 again. I'm on VM12.1.1 ROM, a CM mod.

Per panel update in the next nightly, which should be ready in about 2-3 hours.
[ONE Original Android Development] gugas123:
Cm kernel changes?

http://review.cyanogenmod.org/#/c/99607/
[ONE Original Android Development] xddawg:
quick question about this kernel. does this kernel have any benefits over the stock kernel that is coming up on the 6/2 nightly? i am not planning to change any cpu settings
[ONE Original Android Development] Formhault:
Yeah, we already have that. What about it?
[ONE Original Android Development] _ASSASSIN_:
[MENTION=3685904]ak[/MENTION] thank god for this release. Finally my OnePlus One actually has comparable battery life compared to what I used to get on kitkat with 256 + latest 5.1.1 slimsaber.

Good work my friend! Same goes for you [MENTION=1228651]fusionjack[/MENTION]
[ONE Original Android Development] Mecca EL:
Hopefully I got the correct info
[ONE Original Android Development] Skyrocket2Paradise:
I've found 2 bugs.

With 256 I cannot adjust the wifi scan interval. If I change it in synapse every time I hit the check mark it slides back to 15.

The other bug I found is that in synapse you cannot backup your kernel profile. Whenever I try to backup it clears out my profile name and says I must enter one in order to backup
[ONE Original Android Development] _ASSASSIN_:
The lack of the ability to edit the build.prop is a known issue at this point. He has a test build that has no toolchain optimizations to try and fix that
[ONE Original Android Development] mapolidori:
Same here. I never save my kernel profile, but I always max out the wifi scan interval. It's definitely moving back to 15 seconds when I apply it. Are you on euphoria?
[ONE Original Android Development] Striatum_bdr:
Man it's a known bug, stated a couple of pages ago, will be fixed in next version. Nothing to do with Rom....
[ONE Original Android Development] Skyrocket2Paradise:
bliss

edit: god i wish you could delete posts.. lol
[ONE Original Android Development] aa212121:
I tried to install the v256 but my phone is stuck at the 1+ logo.

I have multirom, I'm installing this kernel on my main rom, wiped cache/dalvik; my phone freezes before I get the ak skull screen(this screen comes before multirom menu); my firmware version is 15/5.

I have to hard reboot my phone and then install a previous version of kernel to boot up my phone. At first I thought it was a bad download, but I downloaded through the updater app at first, then manually through link in this thread, but same result.
[ONE Original Android Development] mapolidori:
I was just letting him know it's a problem multiple people are experiencing. Also, just curious which ROM he's on.
[ONE Original Android Development] Rahulrulez:
I wasn't on AK before.. with AK or without AK. my phone freezes and reboots a lot of time with recent nightlies.. :(
[ONE Original Android Development] ak:
Thanks a lot for your report ..... [emoji7] [emoji7] [emoji7] [emoji7]

Sent from my A0001
[ONE Original Android Development] HamsterHam:
[MENTION=3685904]ak[/MENTION] the freeze test kernel froze this morning so I'm testing v248. If that freezes I'll go to v246.
[ONE Original Android Development] ak:
yes thanks a lot, but if you have froze with 248 i don't think is kernel related.
[ONE Original Android Development] HamsterHam:
Yeah, I thought that. Don't think I had any freezes with 248 before so fingers crossed.
[ONE Original Android Development] kalpik:
Yes, I too believe it's not kernel related. I get these freezes too. What happens is that everything starts to slow down, and the suddenly phone freezes. I'm thinking it has something to do with RAM management on the ROM side.

P.S: You get these freezes with RAM heavy apps like Chrome, 9gag, etc.
[ONE Original Android Development] fm988:
Hi, I m having problem installing ANY version (including latest version) later than 233 on any roms (blisspop, cm12.1 nightly, slimsaber) I have tried with full wipes. Any other versions I tried are giving me bootloop between AK logo and Oneplus logo. Can anyone please give me a hand? Thanks in advance.
[ONE Original Android Development] DrWhatever:
Recovery version?

Try flash 44s/05q through fastboot (without userdata.img and recovery) and then flash firmware(latest from blisspop would be ok)+ROM+kernel, I think it would work
[ONE Original Android Development] CorB3n:
I get exactly same freeze, I think too it's not a kernel problem the phones looks like struggle then freeze. Like if 3 CPU shutted down or if RAM vanishes sudden try
[ONE Original Android Development] ak:
Thanks no I can sleep [emoji18] [emoji18] [emoji18]

Sent from my A0001
[ONE Original Android Development] fm988:
Recovery TWRP 2.8.6.0.

For flashing 05q through fastboot (without userdata.img and recovery), can I follow exactly method 2 on this post: https://forums.oneplus.net/threads/fix-assert-failed-errors-when-flashing-cm-11s-05q-in-twrp.265865/ ?
[ONE Original Android Development] Formhault:
Hmm... This again?

Speaking of Wi-Fi, I haven't had dropouts since v256 anymore. I used to get dropouts like crazy. 4 hours on Wi-Fi rock solid, then, all the sudden... dropouts every 10 minutes (if the screen was off).

Edit : spoke too soon. Once again, dropouts. :(
[ONE Original Android Development] DrWhatever:
Nope, this method includes only boot and system images, when you also need 4.4 modem (as far as I know its NON-HLOS.bin). Of course you can try, but we need to make it work 100%, arent we? :) Flashing whole update through fastboot is a proven way to make everything work :p

Also I reccomend TWRP 2.8.6.0.5 with EFS backup by [MENTION=4021423]ketut.kumajaya[/MENTION].