Did I flash ak kernel incorrectly? - OnePlus 2 Q&A, Help & Troubleshooting

Hello all. There seems to be an issue with ak kernel on my oneplus 2. On ak 15, I was only scoring 45k on antutu and getting no more than 4 hours SOT. I didn't know what was wrong so I waited it out. Anyway, today I updated from ak kernel 15 to ak kernel 18 using the official ak kernel updater. I ran a benchmark and still only scored 45k.. What could be the issue? I originally flashed ak 15 over a clean flash of oxygen os. Not sure what the issue is. Can anyone help?

Alexh221 said:
Hello all. There seems to be an issue with ak kernel on my oneplus 2. On ak 15, I was only scoring 45k on antutu and getting no more than 4 hours SOT. I didn't know what was wrong so I waited it out. Anyway, today I updated from ak kernel 15 to ak kernel 18 using the official ak kernel updater. I ran a benchmark and still only scored 45k.. What could be the issue? I originally flashed ak 15 over a clean flash of oxygen os. Not sure what the issue is. Can anyone help?
Click to expand...
Click to collapse
Not quite sure why you're getting those antutu score, but as far as being washed out, I had this issue too. I was able to correct it by going into Synapse and changing the Saturation setting, under Gamma, to 275. Hope that helps!

jbw716 said:
Not quite sure why you're getting those antutu score, but as far as being washed out, I had this issue too. I was able to correct it by going into Synapse and changing the Saturation setting, under Gamma, to 275. Hope that helps!
Click to expand...
Click to collapse
I'm not having the washed out issue. Only thing I'm bummed about is that I see people getting 62k on antutu or better, and with at least 5 hours SOT, while I'm stuck at 45k in antutu with no better than 4 hours SOT

It's good thing to dirty flash Oxygen OS 2.1.1 and then the AK Kernel v0.18, like suggested from the developer.
The antutu benchmark was influenced by many factor, try it after a reboot with all applications closed and the phone in a cold state after some minutes of non utilization.
The high temperature of cpu give less performance in benchmark.

VampireHeart said:
It's good thing to dirty flash Oxygen OS 2.1.1 and then the AK Kernel v0.18, like suggested from the developer.
The antutu benchmark was influenced by many factor, try it after a reboot with all applications closed and the phone in a cold state after some minutes of non utilization.
The high temperature of cpu give less performance in benchmark.
Click to expand...
Click to collapse
I tried countless reboots and with no apps open and still, 45k score. I Even let the cpu stay idle for hours. Something else is the issue.

You can try to put your phone in the freezer some minutes and retry
Is better if you trough AppOps if you have root, to disable the autostart of many applications, otherwise they start on boot.
Finally the benchmark isn't a indispensable thing, if your system run smoothly this is the important thing.

Related

[Kernel] - 3-23-11 - v.5b - Impressive Sounding Name Kernel

Most of what is below is still accurate, but see this post for links to the kernel download and important infoshttp://forum.xda-developers.com/showpost.php?p=12397646&postcount=580
1-18-11
v.4 - GB’s Impressive Sounding Name Kernel
* As always, many, many thanks to xcaliburinhand.
* Consolidating Steam and Voodoo/CWM kernels into one thread. The two kernels are the same except for recovery, and jfs support in the Steam kernel.
* Started using a proper changelog
* Implemented Impressive Sounding Name Technology AND Dynamic Naming Technology patches; next update to include Dramatic Use of Imagery, with possible Reference to Mythical Creatures patch.
* Cherry-picked some recent commits not included in JPX source. (Will post source this evening, I hadn’t planned on releasing this just yet, but it seems as though it’s already being packaged into a ROM so might as well, right?)
* CONFIG_ARM_THUMBEE=y, enables ThumbEE processor mode, should give some minor JIT performance improvement.
* config_hz=100. With this value, kernel hz = user hz which eliminates HZ <--> USER_HZ conversions. It should also slightly increase battery life without affecting performance.
* Increased default overclock to 1280 MHz. Your may want to revise your undervolt settings, 1280MHz runs at the same voltage as 1200MHz did/does, so you **may** not be able to undervolt as much at 1280. (Yes, I previously said I wouldn’t go past 1200MHz, but, I feel ok going to 1280 since the voltage hasn’t changed and it’s still well below the max vdd_arm.) Use voltage control or setCPU to limit clock speed if you don’t want to use this. Delete your Voltage Control boot settings before booting this kernel. I’m currently using Voltage Control 3.0a.
* Added Voodoo Sound. I hadn’t really planned on it but there were a lot of requests for it.
* Removed i9000 splash screen and replaced with an old familiar one.
* Want lower screen brightness? I know Hardcore did tinkering with the kernel source to do this, but I really like Screen Filter, it even has a Tasker plugin.
* From previous versions: Backlightnotification 2.3, Voodoo color/video fixes re-enabled against my better judgment and even though single-blind testers couldn't tell me which kernels had it and which did not. .
Downloads of v.4 - The file you want is something like rGB-v.4-011811-XXXXX.zip/tar
By clicking any of these links, you agree to flash delete your Dalvik cache and remove any oc/uv boot settings you have before booting. v.4 ClockworkMod zip at the bottom of this post, tar files of Voodoo5/CWM and Steam below for those of you who like to use Odin.
tar of v.4 with Voodoo5 & CWM recovery
tar of v.4 with Steam recovery
Credits
Xcaliburinhand, supercurio, raspdeep, SztupY, sorry if I forgot anyone else.
Stuff I wrote a while ago and may or may not be accurate any more.
1-6-11
This seems to be stable again. Started over from scratch and added in BLN 2.3. Everyone who was affected by charging problems with the previous kernels has not had a shutdown over the last two days of testing. Hopefully we're good again.
1-4-11
Closed testing on newer kernels until I'm fairly confident the issue is resolved again. I had still been getting intermittent reports of charger instability from the reoriented-balls-1-3-11-ocuv-bln23.zip (#47) kernel. Anyone affected by this please switch back to the 'f' builds below, which is the last known rock solid (I think) version.
-----------------------------------------------------------------------------------------------
This kernel is fast, and this kernel is stable. It's overclocked by default to 1.2GHz, but if you don't want to overclock at all, just install either setCPU or download xan's app which I have attached to this post and set the max clock speed to 1.0GHz. This kernel supports init.d scripts, so you have save your settings and have them load at boot.
1100-1200+ Quadrant score on RFS at 1GHz. 1500-1700+ on /data, /dbdata, and /cache on ext4. ~14.1 Linpack at 1GHz. Compare that to any other kernel available here at the same speed and I think you'll see this one comes out on top. I'm not doing this for donations, I just want to my experience with the phone as good as possible. Since this is a Voodoo 5 kernel, you can also make /system ext4 as well for an even smoother experience. This kernel has great battery life and is very stable as well. And when I say stable, I mean, you can use the phone however you want to, you don't have to do any workarounds to keep it from freezing. (edit - as long as you're using one of the build f kernels it seems...) Although, as always, if you aren't 100% satisfied with any of my products, I will give you a full refund.
What this kernel is -
Kernel for 2.2.1 ROMs, (may work on 2.2, but I haven't personally tested it), built from JPX source, with Supercurio's Voodoo 5, overclocked by default to 1.2GHz with raspdeep's code, and Neldar's backlight notification enabled, and re-oriented with xcaliburinhand's code. The undervolting code has been fixed to keep your phone from dying while charging. I'll not be supporting anything beyond 1.2GHz. I hardly use 1.2GHz myself, and from what I've read, many users (but obviously not all) have stability issues with anything much beyond that. This post from one of the senior Android engineers at Google also struck a nerve with me, and is also part of the reason I'll not support anything past 1.2GHz. Samsung actually wrote most of the code for 1.2GHz into the kernel source but had it commented out, so I don't have a problem providing software that will allow users to push it to that level.
Again, for voltage control, use xan's app. I've attached an older version of the app as I'm not sure if the newer one is backwards compatible with the 'older' methods of power management.
Also, standard disclaimers about how if this blows up your phone or tells your girlfriend she's getting fat, it's not my fault. I've had this kernel on my phone for a couple days, so none of that should happen.
How to install - Either flash in ClockworkMod, or use Neldar's really awesome kernel flashing app.
gb-reorient-12-23-build-f.zip is a zip tarred zImage. Unzip, then flash the tar with Odin, or extract the zImage and flash it with Heimdall or Neldar's kernel flashing app.
gb-reorient-fixed-ocuv-f-cwm.zip is a ClockworkMod flashable kernel.
Some thoughts on undervolting
The whole point of undervolting is to safely do the same amount of work with your CPU while using less energy (ie more battery life). Your phone is idle most of the time, so you can the most from undervolting lower frequencies more. Undervolting is safe WHEN you find the settings that work for your phone. Generally, -75mV seems to be stable for everyone. If you want to push it further, go ahead, but realize that if you push it too far, you phone will freeze, and you'll have to pull the battery. Relatively harmless, but, be aware it can happen. Personally, my phone is perfectly stable at the following settings (from 100MHz to 1000MHz) -125mV, -100mV, -100mV, -100mV, -75mV. These settings may not work for your phone. You might find that you can get by with undervolting a little more, but your system will freeze randomly, so if that happens, don't undervolt as aggresively. So, for example, I found that I can usually get by with -150, -125, -125, -125, -100, but every once in a while the phone will freeze up. And since I want a stable system, I've backed down from that. I can't tell you what to do though, but keep in mind that undervolting too much may lead to system instability.
- If you still want to try to find a oc/uv kernel which works for you, don't undervolt at all and tell me if it still happens with kernel #7 (12-23 build from my other thread). As far as I know, no one has had an issue with charger instability on that kernel. If it does still happen, I need to know the kernel version # and for good measure, the production code under your battery (can someone tell me what the name for this is again, I don't feel like shutting off my phone to check), it will be a number like 08.10, 10.10, etc.
- If even with the 12/23 build f kernels and not undervolting at all, you're still get shutdowns when charging, you probably want to get a different kernel. If you insist upon using that one anyway, try charging via USB instead of the wall outlet, it seemed to happen less frequently on older kernels, and I haven't had a charge death in weeks now, so, I'm good at least.
- See if your phone is one of the ones being recalled. If your phone is under recall and these don't work for you, I'm not sure what else I can do.
- These fixes work for me and a lot other people who had the same problem with other oc/uv kernels. Like I said, we're running these out of spec, so a few unlucky souls might not have phones that can handle this. Or maybe some of these kernels have been sprinkled with pixie dust and others haven't. If you find a different kernel that works for you by all means use it. It's all about choice people.
Thanks. Going to try it now.
I flashed 'em at 94%, so we'll see.
But FWIW- I think I've had MAYBE 2 charge deaths when I was on perception. But I was using Setiron's kernels, so I dunno...
I'll report back in a bit.. gonna let it over-charge for a bit and see what happens.
Darky 7.0.1 with your kernel and 100% battery power for 2.5 hours plugged in to the wall and no power off yet. Hopefully this is the fix, I am tired of leaving my computer on all night to charge on usb
thank you so much for this...been looking for something exactly like this, and seems sleep death is gone
darky 7.0.1 here also.
I had it charge around an hr and a half past 100% and no death!
So we'll see how it does overnight
I'll try it out and let you know how it goes, i charge by ac overnight so I should have the results of it to you by morning I'm using it with Assonance 5.2 by the way.
Well no charge death for me last night...
Sent from my GT-I9000 using XDA App
Absolutely no problem, left on ac all night with an undervolt and everything. Great job with this, it made oc/uv usable for me.
Doc's 6.1.3 + your kernel = 100% joy
I found your thread last night after a long and happy Christmas day with the family. Followed your instructions to the letter. Charged overnight from 45% and woke up to find the phone operating fine. This might be the answer to all our prayers!! Thank you so much!
Runs great with eugenes ginger clone. Slightly better benchmarks than other rom/kernel combos. I peak out at 1.3ghz so 1.2 seems like a good medium. One request though is to look into changing the divider for the gpu. I know we don't need it but its good for bragging. Unhelpful had this and I could set the gpu down to 166.750 For lower clocks to save battery and up to 222.334 (stable) for benchmarks. I never tried other clocks so I don't know if it would work on other settings. It depends on how his code works. but it seems by my math the gpu is divided off a 2000 or 2001mhz frequency. There is a margin of error I guess. and stock is divided by 10. In unhelpfuls code it is divided by 9 (222.334) default but could be set to 10 or 12. If we bump that up to 15 or 20 we might reduce battery consumtion with a gpu clock at 133 or even 100mhz. Id also like to try the divider at 8 for 250mhz. Im curious as to how that would benchmark if its stable.
Sent from my SAMSUNG-SGH-I897 using Tapatalk
Ive been charging since 2pm yesterday and its still on. I think you got the fix
No problems here charging overnight. For those who care about quadrant scores, mine was about 250 points higher than the other 1.2ghz kernel I was using.
I get better quadrant scores too vs.my setiron 1.47 1200 kernel. I don't know if it's due to this kernel, but for some reason I'm getting much better battery life since flashing it.
opcow said:
I get better quadrant scores too vs.my setiron 1.47 1200 kernel. I don't know if it's due to this kernel, but for some reason I'm getting much better battery life since flashing it.
Click to expand...
Click to collapse
Same here, battery life seems better..I've noticed it not draining so quickly, im at 85% when usually id be at 50-60%
Sent from my Captivate
I've found Darky's 7.01 works best on my phone, could it be true this makes it run faster? Do I need to have full charge or can i flash this at any battery level?
I didn't look at the actual quadrant score. But my fps is on average about 2-3 greater. Similar to running at 1300 on other kernels. Battery life is much improved over the kernel in eugenes ginger clone rom.
Sent from my SAMSUNG-SGH-I897 using Tapatalk
I just flashed it over SetiroN 1.5.6 and can see a speed difference already. 1200 O/C is perfect, I really like the kernel. Working great on Darkys 7.0.1
I too just installed over Darky's 7.0.1, bit more speed is noticable but i mainly did it for the possibility of better battery because right now thats all i am after.
i just installed but i want some more about voltage control
how can i modified that option?
thx a lot!

Need help with Faux Kernel Ultimate

I'm in a huge dilemma right now, I want to install the "Ultimate" version of Faux's kernel but when I'm using it, my N4 always reboots on start up. From this, it's obvious that that my N4 cannot handle the OC at 1.8ghz and every time I attempt to lower the CPU frequency in trickster mod, my N4 reboots before I get a chance. Anyone out there have a version of Faux's Ultimate kernel that doesn't come at 1.8ghz by default when you install it?
You could try waiting for your device to cool down then booting it up and changing the frequency. I'm undervolted -100 and I'm using intellidemand and I have no problems with 1.8. The battery life is still unbelievably good - 88% with 1h SOT right now (ran quadrant 5 times).
Sent from my Nexus 4 using Tapatalk

Anyone using a highly overclocked kernel which is actually stable?

Few days ago I wanted to test all the major kernels which are existing for the Note 3, and I did. I wanted the kernels which are overclocked, to 2.6 or 2.7 GHz, but not a single kernel I tested was stable. I mean whenever I ran Antutu to check whether it is stable or not it would just reboot or go stuck at around 30% or some level. Not a single time Antutu's benchmark process was finished successfully. And yes, I also did increase the voltage to make sure the overclocked frequency is getting enough power to be stable.
Now I don't know, but is that normal? I see a lot of people using those kernels without any complaint. But why was it like that for me?
Anyone using a kernel which is stable at 2.6 or 2.7 GHz?
Thanks in advance.
Could be the processor in your phone just doesn't like running at high frequencies. Just like with desktop PC processors, overclocking isn't a guarantee

overheat

Hi I'm using redmi 2 prime and I'm on cm13 official ROM I have been facing a lot of overheating issue in stock miui ROM too but why is it happening 2gb ram is more than enough and do anyone know how much temp is harmful for my device I get up to 43 to 45 degree Celsius is it OK ??
That temperatures are not normal, I only get those numbers when all cores are running at maximum speed for some time. If you are getting this numbers on both OSs there must be something in common. Since you are on CM and rooted, you can do some tests.
First, to discard a hardware issue you should use a lower max frequency speed than 1200 MHz, use 800 MHz for some minutes and watch and feel your mobile temperature. I hope this will decrease that heat!
Second, if the heat went away, you should identify what is causing it. Typical heat causes are GPS and 3G/4G usage. Make sure these are off for now and list all those apps you are using on both OSs. Go to battery in settings and uninstall those apps which are consuming the most battery, one by one with maxspeed set to 1200 MHz and watch and feel your temperature.
Notice that recent nightly builds are being reported by users as draining battery too fast. If nothing is helping try an older nightly build, previous to 23rd august. Always do a nandroid backup, before updating your ROM and keep a close eye into official CM13 thread.
If you want a quick advice, do this downgrade first and restore your installed apps from a nandroid backup.
Try this CPU settings using Kernel Adiutor on Interactive Governor [Root Needed]
Can anyone give me the link for 0822 nightly of CM 13 official rom.
akshay0036 said:
Hi I'm using redmi 2 prime and I'm on cm13 official ROM I have been facing a lot of overheating issue in stock miui ROM too but why is it happening 2gb ram is more than enough and do anyone know how much temp is harmful for my device I get up to 43 to 45 degree Celsius is it OK ??
Click to expand...
Click to collapse
Try to flash custom kernel if you want to stay in CM13. Then dowload kernel adiutor to change CPU speed, hotplug and etc. We are here to help

Paranoid Android 7.3.0 vs. Lineage OS 14.1 - Doze / power / sleep?

Good morning Le Pro3 forum -
I've been switching between Paranoid Android and Lineage OS for the past few weeks. One thing I've noticed very specifically is that PA 7.3.0 (and 7.2.0...) does not seem to effectively go into 'doze' as well as Lineage OS. What I mean is that battery drain overnight is pretty high on PA (10-20%) while Lineage is very low (less than 5%) using the same applications.
So that I can better understand and troubleshoot, would anyone be willing to point me to other forum posts either here or on other forums that dive into troubleshooting this kind of thing? I'm not finding anything that useful that is *recent*.
Thanks in advance!
mdkathon said:
Good morning Le Pro3 forum -
I've been switching between Paranoid Android and Lineage OS for the past few weeks. One thing I've noticed very specifically is that PA 7.3.0 (and 7.2.0...) does not seem to effectively go into 'doze' as well as Lineage OS. What I mean is that battery drain overnight is pretty high on PA (10-20%) while Lineage is very low (less than 5%) using the same applications.
So that I can better understand and troubleshoot, would anyone be willing to point me to other forum posts either here or on other forums that dive into troubleshooting this kind of thing? I'm not finding anything that useful that is *recent*.
Thanks in advance!
Click to expand...
Click to collapse
Slightly tangential, but how is the battery life overall compared to LineageOS? I've been running LineageOS and while it performs well, the battery life isn't nearly as good as stock EUI. As for over night battery drain, I get about 10% in 8-9 hours in stand by.
Hey. I tried every single rom out there from MoKee to Lineage and i can asure u one thing. Best for battery is Omni ROM (latest) + BlackScreen kernel version 3.6
Now i am a medium - heavy user. Lots of time on snapchat and playin games for about half an hour to a hour. I got 6 hours of screen on time wich is great really compared to other roms.
Now i also tried various combinations of using different governors and so on so i tested an option for about three days and then tried another one. I was seeking for the best possible battery life while don't have any stuttering or lags. Cuz if u put the cpu governor for example on impulse and then underclock it too... It lags like hell.
Soo what do u need to do to get also good standby performance?? I loose less than 3% over night.
Try following:
IN KERNEL AUDITOR
CPU: Both big and little cores governor set on alucard
Underclock the big cores to 1900 and little cores to 1440
GPU: governor set to msm-adreno-tz; underclock max frequency to 560 MHz; enable Adreno idler
I/O sheduler: set governor to noop; read-ahead 128 kB
Low Memory Killer: set profile to Agressive
Misc: Vibration strenght set on about 15%, disable Fsync, TCP must be westwood.
_________________________________________
Developer options:
Set logger buffer size to off
Set all three animation scales on 0.5x
_________________________________________
That is it. If u have any questions or something doesn't work as written -> reply back
P.S. turn off wi-fi during night. Helps a bunch.
insomnixXx said:
Hey. I tried every single rom out there from MoKee to Lineage and i can asure u one thing. Best for battery is Omni ROM (latest) + BlackScreen kernel version 3.6
Now i am a medium - heavy user. Lots of time on snapchat and playin games for about half an hour to a hour. I got 6 hours of screen on time wich is great really compared to other roms.
Now i also tried various combinations of using different governors and so on so i tested an option for about three days and then tried another one. I was seeking for the best possible battery life while don't have any stuttering or lags. Cuz if u put the cpu governor for example on impulse and then underclock it too... It lags like hell.
Soo what do u need to do to get also good standby performance?? I loose less than 3% over night.
Try following:
IN KERNEL AUDITOR
CPU: Both big and little cores governor set on alucard
Underclock the big cores to 1900 and little cores to 1440
GPU: governor set to msm-adreno-tz; underclock max frequency to 560 MHz; enable Adreno idler
I/O sheduler: set governor to noop; read-ahead 128 kB
Low Memory Killer: set profile to Agressive
Misc: Vibration strenght set on about 15%, disable Fsync, TCP must be westwood.
_________________________________________
Developer options:
Set logger buffer size to off
Set all three animation scales on 0.5x
_________________________________________
That is it. If u have any questions or something doesn't work as written -> reply back
P.S. turn off wi-fi during night. Helps a bunch.
Click to expand...
Click to collapse
Hi mate, thank you for your detailed review. It helped me especially for kernel auditor settings. But i have an objection in my honest oppinion. I have tried both roms, AICP 12.1 and OmniROM and AICP is much better at battery department. But both rom is great in the rest.
SUMMERBREEZE said:
Hi mate, thank you for your detailed review. It helped me especially for kernel auditor settings. But i have an objection in my honest oppinion. I have tried both roms, AICP 12.1 and OmniROM and AICP is much better at battery department. But both rom is great in the rest.
Click to expand...
Click to collapse
Really, well u know it is mostly how u use it. Cuz for my type of usage Omni works perfect. I was using AICP for a month before i tried other roms as described and it was really good but idk... When i was using it i got 4h and 30min at best with my kind of usage but with omni i got easily 6h. It depends from user to user but well... I will give AICP another shot anyway. I am glad that my review helped u.
insomnixXx said:
Really, well u know it is mostly how u use it. Cuz for my type of usage Omni works perfect. I was using AICP for a month before i tried other roms as described and it was really good but idk... When i was using it i got 4h and 30min at best with my kind of usage but with omni i got easily 6h. It depends from user to user but well... I will give AICP another shot anyway. I am glad that my review helped u.
Click to expand...
Click to collapse
yes it helped a lot. especially kernel tweaking thing. both rom is great imho and 1-1.5 hr screen on time difference may marry -as you said- on which programs/apps we use. we must be glad that our le pro 3 has a great nougat support from these beautiful devs and i dont know how to thank to them. i just used 2-3 days this AICP rom and i will give also a shot to OmniROM to compare them again. I love both roms and i am sure i will keep switching between the two

Categories

Resources