Introduction
If you think there is a drain in Lollipop this is not that fix. This fix the "high cell standby mobile radio active time" bug. You can still test this if you want.
Some people are writing that this patch "only" fix the battery radio active time counter. I say that if you know java and take a look on the code you will note that the side effects of this bug includes, among others, not calling various NetworkManagementEvent observers that will have role in other modules of the inner core of Android, and not only the battery stats. So you say me what are the other side effects fixed.
Other people are saying that this patch doesnt fix the "cell standy radio active time" bug, so take your chances, or wait until Marshmallow :fingers-crossed:.
If after the patch you see a "miscellaneous" item in the battery stats, I am sorry for you but this indicates a bug in your RIL module (or other module) which this patch not solve. The bug in the RIL module was only masked by the Lollipop radio active time bug.
Hi,
I'm working on a fix to the Cell standby / Mobile radio active time issue. The bug manifests as a high mobile radio active time on the Cell Standby in the battery stats.
I think I found the bug in the inner core of Android, and I made some fix to test if it works.
In this thread you will find a Cyanogenmod 12.1 (Android 5.1) build for Odin/Xperia ZL with the fix applied. I already flashed this build onto my odin device and the bug seems to be fixed.
So now I want some of you to test this build and see if the bug is definitely gone.
NOTES
- Your device must have bootloader unlocked.
- CyanogenMod and my work comes with NO WARRANTY as usual. Don't blame me for anything you think I deserve.
- This is my other work on fixing droids: http://forum.xda-developers.com/showthread.php?t=1312398
Patches
I submitted the fix patches to AOSP/Google and CM.
https://android-review.googlesource.com/#/c/168231/
http://review.cyanogenmod.org/#/c/107828/
FAQ
How to install
-Make a backup (using recovery or your preferred tool)
-Download .zip and copy to the phone external sd card
-Boot into recovery (TWRP recommended)
-Install zip cm-12.1-20150827-UNOFFICIAL-odin.zip
-Wipe dalvik/cache
-If you was not on CM12.1 before then Wipe Data
-Reboot
-Wait Android installing apps
How to test
-Enable mobile data (with wifi off)
-Use mobile data (now the bug was triggered)
-Disable mobile data
-Use your device normally and then some hours later look for the mobile radio active time on the battery stats.
-On normal circumstances the display should be the bigger drain. The bug manifests as the Cell Standby being the bigger drain with a high mobile radio active time.
-Please report in this thread if it works or not for you. Thank you!
Can I have a Xposed module of this
- Yes. Thanks to @pyler
http://forum.xda-developers.com/xpo...oactivefix-t3189393/post62570773#post62570773
Download: flashable ZIP
- 2015-08-27 v1 (new)
http://www.mediafire.com/download/2f0igf17ixs52zc/cm-12.1-20150827-UNOFFICIAL-odin.zip
MD5: 3c3641ad6738fad953a90a5d3e745f75
Info about the patches
How to reproduce the bug:
-Enable mobile data (with wifi off)
-Use some mobile data (radio active timer starts in battery stats)
-Disable mobile data (radio active timer keeps running in battery stats)
After some investigation on the issue I found that the BatteryStats
service was not receiving the radio power down notification. The
investigation lead me to the NetworkManagementService.java, where
I found that some code was discarding the radio power change
notifications after the first radio power on.
The problem is that in NetworkManagementServer.java the
notifyInterfaceClassActivity method is discarding the notifications
of radio power change to the BatteryStats (via noteMobileRadioPowerState)
if the fromRadio parameter is false after it's being true some time before.
Even after a detailed analysis, it was unclear what is the real role of
the fromRadio parameter. Changing it to true in the calling methods
solved the issue in the testing unit (Sony Xperia ZL).
Change that introduced the code with the potential to trigger the bug:
-Introduction of "boolean fromRadio" in
NetworkManagementService.java / notifyInterfaceClassActivity()
https://android.googlesource.com/platform/frameworks/base/+/2ffa11e4b71c545e34533ef827bdc1a07fbe8246
Change that triggered the bug:
-Uncommenting the code that calls notifyInterfaceClassActivity
with fromRadio=true
https://android.googlesource.com/platform/frameworks/base/+/2d4b4ed681efcfb64c4d2b4d2a2d236aae1dc7ee
Instructions on how to make an Xposed Module from this patch
XDA member pyler is working on a Xposed module to apply thish patch:
http://forum.xda-developers.com/xpo...oactivefix-t3189393/post62570773#post62570773
---
You can use and Xposed module to apply this fix on-the-fly. If you decide to make an Xposed module from this patch, please credit my work and put a link to this thread.
How to do:
- on package com.android.server class NetworkManagementService (NetworkManagementService.java)
- verify if the method assinature for notifyInterfaceClassActivity method is correct (have the fromRadio parameter)
- intercept the call for the notifyInterfaceClassActivity method
- change the value of the fromRadio parameter to true
- and then call the original method
package com.android.server
class NetworkManagementService
private void notifyInterfaceClassActivity(int type, int powerState, long tsNanos, boolean fromRadio)
For devs
- CyanogenMod: you can repopick the patch 107828 before building.
- Other ROMS: apply the patch manually, it's tiny. The project is frameworks_base.
- There is no APK alone that solves this, only the xposed module.
Supporters
Unexpected but not least important, the following people appreciated my work and made a donation or special thanks:
phoneturf
I submitted the fix patches to AOSP/Google and CM.
https://android-review.googlesource.com/#/c/168231/
http://review.cyanogenmod.org/#/c/107828/
good work! finally a patch
Sounds Awesome!!! @jgcaap Could you please spin a build with this patch and let us all know if it fixed it on bacon as well?
@YoshiShaPow @kantjer @fusionjack @temasek
This is what Android has become, the bug second most stared on their tracker is fixed by volunteers on XDA.
In general that does not make me very happy, but the work you did for them is awesome, thank you!
I'm a little confused now... Does this really fix the battery drain or is it just a fix for false measurement in batterystats? Because battery life on mobile data is much worse than on wifi for me since Android 5/5.1
It appears from your patch that this is only a reporting issue in the battery stats, and that the mobile radio IS being shut down, it just isn't being reported properly. If this is the case, do you have any idea why the battery performance in Lollipop is som much worse than KitKat?
acwest said:
It appears from your patch that this is only a reporting issue in the battery stats, and that the mobile radio IS being shut down, it just isn't being reported properly. If this is the case, do you have any idea why the battery performance in Lollipop is som much worse than KitKat?
Click to expand...
Click to collapse
Yes. In my device the radio IS being shut down properly. But in fact the code is a mess and I think there are many other bugs in the networking module.
I was on stock Kitkat and now I'm getting the same battery duration on CM12.1 (4h display on + 30m GPS/3G). Need more tests to detect more issues.
Anyway, I found another issue that I want to investigate that is the mobile data radio being activated and deactivated for a few seconds every time the wifi is connected.
Bazoocaze said:
Yes. In my device the radio IS being shut down properly. But in fact the code is a mess and I think there are many other bugs in the networking module.
I was on stock Kitkat and now I'm getting the same battery duration on CM12.1 (4h display on + 30m GPS/3G). Need more tests to detect more issues.
Anyway, I found another issue that I want to investigate that is the mobile data radio being activated and deactivated for a few seconds every time the wifi is connected.
Click to expand...
Click to collapse
Interesting. I was beginning to suspect that the Radio active time being displayed was a reporting issue, if the radio was really turned on as much as it claims, I think battery life would be much worse. Your patch is useful in that I now have a good idea of where to add logging statements to try see if there ARE issues with the actual radio active time.
reaper90 said:
I'm a little confused now... Does this really fix the battery drain or is it just a fix for false measurement in batterystats? Because battery life on mobile data is much worse than on wifi for me since Android 5/5.1
Click to expand...
Click to collapse
I do not know for sure. This will only solve the "mobile radio active time" issue on my device, where there is not a drain, but only the false measurement.
But if there is a problem in the RIL module of your device this patch will not solve the drain.
acwest said:
Interesting. I was beginning to suspect that the Radio active time being displayed was a reporting issue, if the radio was really turned on as much as it claims, I think battery life would be much worse. Your patch is useful in that I now have a good idea of where to add logging statements to try see if there ARE issues with the actual radio active time.
Click to expand...
Click to collapse
You ARE CORRECT.
I concluded the same when I put the decice in ariplane mode for several hours: the battery percent was the same at the end, but the mobile radio active counter keeps running for several hours, indicanting that the radio was turned of properly (same battery percent) but the timer keeps running.
Bazoocaze said:
You ARE CORRECT.
I concluded the same when I put the decice in ariplane mode for several hours: the battery percent was the same at the end, but the mobile radio active counter keeps running for several hours, indicanting that the radio was turned of properly (same battery percent) but the timer keeps running.
Click to expand...
Click to collapse
This is a good news/bad news situation. Good news, you have found the cause of the high radio active times. Bad news, something is still draining the battery. At least now we have better information...
Excellent work on pathing the issue, by the way...
abhibnl said:
Sounds Awesome!!! @jgcaap Could you please spin a build with this patch and let us all know if it fixed it on bacon as well?
@YoshiShaPow @kantjer @fusionjack @temasek
Click to expand...
Click to collapse
Concept seems interesting. Lemme look at the commits first before we go as far as building :good:
abhibnl said:
Sounds Awesome!!! @jgcaap Could you please spin a build with this patch and let us all know if it fixed it on bacon as well?
@YoshiShaPow @kantjer @fusionjack @temasek
Click to expand...
Click to collapse
Done
jgcaap said:
Done
Click to expand...
Click to collapse
Nice!
Still trying to put this into an xposed module, gonna take ages for me to do it
merewood bebox said:
Still trying to put this into an xposed module, gonna take ages for me to do it
Click to expand...
Click to collapse
I will make an detailed explanation on the first topic.
----
EDIT: done
So anyone here has made the module for xposed?
Sent from my Oneplus One using Tapatalk
---------- Post added at 12:58 PM ---------- Previous post was at 12:54 PM ----------
jgcaap said:
Done
Click to expand...
Click to collapse
@jgcaap would you like to share link for your build that has this patch?
Thanks
Sent from my Oneplus One using Tapatalk
Bazoocaze said:
I will make an detailed explanation on the first topic.
----
EDIT: done
Click to expand...
Click to collapse
thank you very much
Could anyone make either a xposed module or a flashable zip that we can use on bacon OnePlus One 5.1.1 to fix the mobile radio active issue? Thanks
Related
[Android General] Android Tips & tricks (UPDATE 14/03/10) HUGE UPDATE! 3 uselful tips
I have fought that the Android/Blackstone community would be happy to learn some tips and tricks to enjoy their configuration better.
You can post yours for sure
TIPS AND TRICKS:
1) Do you find your XAndroid build very slow and not as responsive as you expected ?
Install CleanRAM under WinMo (6.x), set it to "Level 3" (Fundamental Purge). Normally, your build will be faster and more responsive, it works for me !
Feel free to post your feedback
2) Do you find your battery life is not at least good ?
Disabling Wi-Fi toggle can be useful, even if you aren't connected to your favourite Network, let it drains the battery faster than everything...
3) An other battery tip ! Disable Animations in Settings Menu.
It won't change important things, it's almost unnoticeable.
4) You don't use the 3G network ? Disable this option into the comm manager under WinMo 6.x , you'll notice an important changing as regards your battery life
5) Have you found an app which doesn't fit the whole screen ? Open STARTUP.txt and try to change lcd.density from 220 to 240.
(Thanks Slaming)
6) Many many users don't manage to answer their incoming calls. Last night i found a trick. Don't use your finger, but press a bit hard the green circle on your screen with your stylus (no risk for your screen), you'll be finally able to answer your calls !
7) I just found a PERFECT package: http://zimages.googlecode.com/svn/a...sm-android/zImage-modules-20100215_000813.tar
If you don't know how to use it, there are some FAQs
8) Do not forget that your WinMo settings matter !
(Especially Screen settings, comm manager settings, etc, i'll give more details soon)
9) How to install glemsom's packages according to Slaming:
"to install this just download the zip and place it in your sd card then edit the starup and change zimage to the name of the zimage you are uing so in this case it will be zImage-20100215_000813 when its booting you will see the kernel script and it will say new image or something. hope this helps.
and dont forget don't unzip the other file inside the original zip just place it in the sd card normally."
10) I think i have found a temporary fix as regards DEEP SLEEP ISSUES (I test it for three days and the conlusion is impressive !).
There are the instructions:
1) Download the app SetCPU (included in Glossy's packages)
2) Install the app via the market (if you've downloaded it via your phone) or Astro file manager (If you have the .apk)
3) Launch SetCPU and choose "Auto Detect" (at the end of the list)
4) Set Max at 528MHz and Min at 245MHz, enable "Set on Boot" and let CPU Governor as "On demand"
5) Exit the app, test my tip and leave your feedback
Warning: Your battery life won't be shorter, don't worry.
11) Your Network drops down sometimes and never reappear ? Select your network manually, and if it doesn't work, don't reboot, it can take some time
I'm french so i do: Paramètres (Settings) => Réseaux sans fils (top of the list) => Paramètres réseaux mobiles (bottom of the list) => Recherche manuelle (Manually search ?), wait 10 sec and select your favorite network.
12) Boot failed to mount sd card ? Try this: http://groups.google.com/group/beagleboard/browse_thread/thread/ef88a97aaef9116b?pli=1
13) Tired of installing all your APKs ? Just put your precious APKs in "Androidapps" folder, it will auto-install apps when booting. Thanks Brodos123
14) Deep Sleep problems are getting on your nerves ? Try to use the "board-htcblackstone-panel.no_bkl_off=1" in the cmdline in startup.txt. Thanks Brodos123
15) Tired of seeing all this "fsck0001", "fsck0002" ? You can delete them without having any issue ! Thanks N!ghty
16) Want to use your personnal wallpapers ? Try to put your JPEG, or GIF, or any image file into sdcard\media\resource\ , and select one of them with your favorite wallpapers manager. Thanks N!ghty
[11/02/2010] Update !
[13/02/2010] Update ! Thanks Slaming
[14/02/2010] Update !
[16/02/2010] Update ! [Perfect Glemson Package added !]
[17/02/2010] Update ! [Warning about WinMo Config]
& How to install Glemsom's packages (thanks slaming).
[19/02/2010] Update ! DEEP SLEEP ISSUES ALMOST FIXED !
[27/02/2010] Update ! Fix for when the network drop down.
[05/03/2010] Update ! "Failed to mount sd card" fixes.
[13/03/2010] Update ! How to auto-install all your APKs.
[14/03/2010] Update ! HUGE UPDATE ! (3 new useful tips) Thanks Brodos123 and N!ghty.
finding apps aren't taking up the whole screen open the startup txt and change lcd.density from 220 to 240
WinningDays said:
TIPS AND TRICKS:
1) Do you find your XAndroid build very slow and not as responsive as you expected ?
Install CleanRAM under WinMo (6.x), set it to "Level 3" (Fundamental Purge). Normally, your build will be faster and more responsive, it works for me !
Feel free to post your feedback
2) Do you find your battery life is not at least good ?
Disabling Wi-Fi toggle can be useful, even if you aren't connected to your favourite Network, let it drains the battery faster than everything...
3) An other battery tip ! Disable Animations in Settings Menu.
It won't change important things, it's almost unnoticeable.
4) You don't use the 3G network ? Disable this option into the comm manager under WinMo 6.x , you'll notice an important changing as regards your battery life
5) Have you found an app which doesn't fit the whole screen ? Open STARTUP.txt and try to change lcd.density from 220 to 240.
(Thanks Slaming)
6) Many many users don't manage to answer their incoming calls. Last night i found a trick. Don't use your finger, but press a bit hard the green circle on your screen with your stylus (no risk for your screen), you'll be finally able to answer your calls !
7) I just found a PERFECT package: http://zimages.googlecode.com/svn/a...sm-android/zImage-modules-20100215_000813.tar
If you don't know how to use it, there are some FAQs
Click to expand...
Click to collapse
How is the wake up on sleep problem in this kernel?
No problem for me It should be the same for you.
The same sleep problem. Put the phone into sleep mode and leave it in your pocket for 15 minutes and see.
There hasn't really been any notable progress as far as fixing what is broken on Blackstone (or any of the features that don't work like camera, bluetooth, etc.) since December.
If you've been following the notes on the zimage builds, you'll see how slow progress really is. Although I appreciate how difficult it is for those working it, I think they'll still be working on it long after we've upgraded to another a phone, and with what they're up against, I wouldn't hold my breath about getting new features to work.
Besides, HTC Bravo/Desire will be available in March... Snapdragon? new Sense UI? Yes please.
I've woken up my device about 500 times and this problem have appeared only 2 or 3 times.
WinningDays said:
TIPS AND TRICKS:
7) I just found a PERFECT package: http://zimages.googlecode.com/svn/a...sm-android/zImage-modules-20100215_000813.tar
If you don't know how to use it, there are some FAQs
Click to expand...
Click to collapse
to install this just download the zip and place it in your sd card then edit the starup and change zimage to the name of the zimage you are uing so in this case it will be zImage-20100215_000813 when its booting you will see the kernel script and it will say new image or something. hope this helps.
and dont forget don't unzip the other file inside the original zip just place it in the sd card normally.
what do you mean by "perfect"?
how perfect it is and in what aspect?
It is meaningless to say perfect with no content at all.
Perfect for what we have at the moment
BT, headphones and camera still doesn't work, but this package make Android smooth, fast, wifi works perfectly, 3g too, and i didn't have any trouble with deep sleep
WinningDays said:
Perfect for what we have at the moment
BT, headphones and camera still doesn't work, but this package make Android smooth, fast, wifi works perfectly, 3g too, and i didn't have any trouble with deep sleep
Click to expand...
Click to collapse
Leave it charging over night in sleep mode, then try and wake it up. Doesn't work.
Although this is an overall good package, it suffers the same current bugs that have yet to be resolved. Every zimage build has had this problem since they added sleep functionality last month, and unfortunately its marked as a 'low priority' bug in the forum.
I leave my phone charging every night when android is booted and i have no problem.
on Diamond?
Can i put this on Diamond? afaik, it should go, since I am only replacing the zImage.
re-Posted: http://forum.xda-developers.com/showpost.php?p=5662770&postcount=74
mod may delete....
You'd better post in the Android Questions for this, put i'll try to answer your question.
I think you can only put modules and zImage, but i'm not sure...
sraaj said:
Can i put this on Diamond? afaik, it should go, since I am only replacing the zImage.
re-Posted: http://forum.xda-developers.com/showpost.php?p=5662770&postcount=74
mod may delete....
Click to expand...
Click to collapse
all of these builds are generic the only that changes is the startup hope this helps
Update concerning Deep Sleep issues
WinningDays said:
Update concerning Deep Sleep issues
Click to expand...
Click to collapse
doesnt work for me... at all
WinningDays said:
Update concerning Deep Sleep issues
Click to expand...
Click to collapse
Hey!
Tottaly worked for me.
Using glossy 1.7 and had sleep problems before.
used SETCPU and worked.
Thanks.
Left charging all night and today it woked up from sleep.
Never did this before.
Worked for me too!
Testing it for two days and didn't had one sleep problem.
Keep up the good work!
If you experiencing battery drain problems in new JVO release then this package is for you!
Package includes:
- turned off debug infos in most framework modules
- FM Radio is turned off by default instead of stock always loaded!
- optimized timings for light animations and refresh rate of various things
- new broadcom wifi/bt module from Nexus S
- updated flash library from Galaxy S2
- new bootlogo and bootsound in format .ogg instead of .wav from Galaxy S2
- custom volume level notification sounds feature instead of simple "beep" ported from HTC
- new media_profiles.xml with redefined values for even better video recording/playback and sound fidelity
After apply clean battery stat infos in recovery charge your battery to the full and watch "Android System" process in battery usage menu after few hours
If you use custom ROM with other lockscreen than stock Glass or with extended power menu you will LOOSE THESE FEATURES!
Download link (FIXED VERSION):
http://www.multiupload.com/N0VLGNQHLU
Apply via recovery!
Can u clarify what features get lost if using a different lockscreen
fatjoez said:
Can u clarify what features get lost if using a different lockscreen
Click to expand...
Click to collapse
You'll simply reverse lockscreen to the stock one (TouchWiz Glass).
Lukiqq? You're from samdroid.net? Spica user ?
Sent from my GT-I9000 using Tapatalk
not working. installation always aborted.
Looks nice, will try this one out !
bududroid said:
Lukiqq? You're from samdroid.net? Spica user ?
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
Yes I'm. w8, will find out why it aborts.
Sent from my GT-I9000 using XDA Premium App
Brotuck said:
Looks nice, will try this one out !
Click to expand...
Click to collapse
So what's your verdict, "Yea" or "Nay"?...(and how does it get along with Damien's Beta 7? Do they play well together?)
eternal-intent said:
So what's your verdict, "Yea" or "Nay"?...(and how does it get along with Damien's Beta 7? Do they play well together?)
Click to expand...
Click to collapse
If such ROM is based on JVO then why not
eternal-intent said:
So what's your verdict, "Yea" or "Nay"?...(and how does it get along with Damien's Beta 7? Do they play well together?)
Click to expand...
Click to collapse
I had to remove the modified framework files and the wifi driver i already got.
But the other "tweaks" i am testing right now.
It is for batterylife so i am able to tell something in a few days.
But the integration with damian's kernel works great until now.
Lukiqq said:
If such ROM is based on JVO then why not
Click to expand...
Click to collapse
GingerMod is......
Brotuck said:
I had to remove the modified framework files and the wifi driver i already got.
But the other "tweaks" i am testing right now.
It is for batterylife so i am able to tell something in a few days.
But the integration with damian's kernel works great until now.
GingerMod is......
Click to expand...
Click to collapse
Modified framework files and wifi module are critical to battery life. Other things in package are just eye candy
Lukiqq said:
Modified framework files and wifi module are critical to battery life. Other things in package are just eye candy
Click to expand...
Click to collapse
Yes i would think so, but the tricky part of it is that almost everybody uses his / her own framework files.
Can/are you willing to modify mine with the tweaks ?
Sure i can decompile the mods you made and compare them to my framework, but it's nicer to ask you.
Brotuck said:
Yes i would think so, but the tricky part of it is that almost everybody uses his / her own framework files.
Can/are you willing to modify mine with the tweaks ?
Sure i can decompile the mods you made and compare them to my framework, but it's nicer to ask you.
Click to expand...
Click to collapse
I would like to but I don't have enough time for such things :/ Try it tell me how it works after few hours. If you like it I'll modify some popular frameworks.
Lukiqq said:
Modified framework files and wifi module are critical to battery life. Other things in package are just eye candy
Click to expand...
Click to collapse
framework might work be but wifi even compiled from latest sources gives nothing in exchange
interesting aproach anyways
$omator said:
framework might work be but wifi even compiled from latest sources gives nothing in exchange
interesting aproach anyways
Click to expand...
Click to collapse
I'm not sure about wifi, but total time about 8h, 3h with wifi, web browsing, xda app etc. gave me results:
LCD display - 60%
Wi-Fi - 9%
Standby - 8%
Android System - 2% + 3% (before about 20%)
And the rest.
mostly placebo mate ;]
i got same aos % usage wo a single tweak
well lies, i have *%load of tweaks but only two of them are aimed at bat. and those are not changing much tbh.
one makes scan for new ap every 2min not 15sec and second makes wifi go to sleep on screen off after 10 seconds at place of 15minutes set by default
battery likes to drain a bit after flash or even after a via recovery file update but after cycle or two it goes back into normal -0 -1 -2% of bat during night sleep. thats ok for me ;]
but keep up the good work as people like to say ;]
$omator said:
mostly placebo mate ;]
i got same aos % usage wo a single tweak
well lies, i have *%load of tweaks but only two of them are aimed at bat. and those are not changing much tbh.
one makes scan for new ap every 2min not 15sec and second makes wifi go to sleep on screen off after 10 seconds at place of 15minutes set by default
battery likes to drain a bit after flash or even after a via recovery file update but after cycle or two it goes back into normal -0 -1 -2% of bat during night sleep. thats ok for me ;]
but keep up the good work as people like to say ;]
Click to expand...
Click to collapse
I'm not forcing anyone to use this mod. Compare adb logcat with modified and original ones, you'll see the different. Stock framework throw so much useless garbage...
just want to point those:
- few random tweaks not bat related here and there - curiosity
- uncertain benefit of disabled logcat (personaly i think dimming the screen a bit at options or setting cpu to conservative would make much more difference for bat)
- all previous lockscreens/power menu/overscroll glow and so on modifications stop working
and at the end logcat is usefull ;] but ofc unnoticable for every day user
as said previous well done
could you please publish the source/list of changes/diff file for framework? can't life without a number of mods but improved battery life would be quite nice as well...
Installation aborted...
Hello,
I'm reactivating this thread since I cannot talk with samm every now and then to update the OP from this thread here.
What works:
It is stable for a daily driver but there are definitely things that doesn't work. For starters, the Hero is too small for ICS since we don't have any GPU posibility. Adreno 130 drivers are oh, too small and too bad for animations on ICS, they suck even in GB and Froyo. Still, the statusbar and fling are much smoother than other android releases because that's how ICS is built. It is more RAM friendly and it looks, well, sexy!
Will try and update this rom when it will be possible. We might jump on the bandwagon of 4.0.4 if I can make it to move faster than it moves right now (yes, I have an experimental build).
If one of you want to join me to develop this rom further, send a PM and I will send you some details about what is in the works, how far it is. I know there are few people that can work on builds here on Hero thread but if we work together, we can pull this out one more time.
FLASH THIS AT YOUR OWN RISK. I AM NOT RESPONSIBLE FOR:
- YOUR BRAIN
- YOUR HOUSE
- YOUR PHONE!
ON with the ROM. What has been changed:
Added:
Code:
- Google Music apk (yes, official google music app);
- Explorer.apk
- Latest and greatest LV Kernel 1.2+
- Revert to Evtoolbox back from 4.0.3 builds
- Set the cpu to scale at 352-672 from startup
- Tweaked the build.prop a little (added some experimental lines)
Why this is v3?
Because the memory management inside the kernel (remember, INSIDE THE KERNEL) is tweaked and fixed to nice values in order to allow our hero to better multitasking (you can find these values in my other rom called 1ceCream BEAST Flavor). No need for tweaks in init.d to do the job, no bull****.
Just plain and simple!
If you are texting someone, sending an email, playing a game, doing something, and you are locking the screen, after unlocking you will find that the application is ON the screen, and is not closed how it is in many other roms for hero. The multitasking with my values is so much better, you will definitely like it!
Click to expand...
Click to collapse
The rom moves fast, even if it is ICS, I have the animations on and no force GPU in Developer settings and it is still moving so much fast than the older builds.
Overall, I am happy with this release and I hope you will be too! Post me some of your opinion and tell me if it is fast or am I dreaming!
Some user's feedback:
Loxxy said:
wow 'HeroICS v3' is running on rocket power !!! what the hell
amazing job
Click to expand...
Click to collapse
Carrier Internet connection issue:
- Create Manual APN for provider's internet connection.
DOWNLOAD HeroICS v3
If you make these changes maybe you'll see better performance, the hero can't handle dithering on anything higher than stock GB or Sense froyo and doesn't have enough RAM for 48mb of dalvik heapsize. I may be wrong but these always worked for me in the past altough ICS is supposed to be better on RAM.
dalvik.vm.execution-mode=int:fast
dalvik.vm.heapsize changed to 24m or 32mb
persist.sys.use_dithering=0
Good work. Flashing now.
How about keeping this as lite as possible, only the absolute essentials pre-installed, everything else as optional zips / apk. For instance, I personally have no use for the music player.
I would really like to see a bare bones, fast and stable ics rom where you just add what you need.
---------- Post added at 03:56 AM ---------- Previous post was at 03:16 AM ----------
Unexpected reboot just as I was about to install Opera Mini. Followed by: "New Sim Detected, reboot required." Never seen that before.
I've applied CSL00's values.
Wonder if V6 Supercharger or Auto Memory Manager can improve things.
Play Store is noticeably faster. Unsure if was CSL00's values or the introduction of AMM.
Regarding the error message: 'No more room on this home screen.'
In Play Store app. Menu > Settings > Deselect Auto-add widgets.
Second unexpected reboot, otherwise things are getting faster. No wifi issues, BT still won't pair.
Running AMM on 'Aggressive.'
CSL00 said:
If you make these changes maybe you'll see better performance, the hero can't handle dithering on anything higher than stock GB or Sense froyo and doesn't have enough RAM for 48mb of dalvik heapsize. I may be wrong but these always worked for me in the past altough ICS is supposed to be better on RAM.
dalvik.vm.execution-mode=int:fast
dalvik.vm.heapsize changed to 24m or 32mb
persist.sys.use_dithering=0
Click to expand...
Click to collapse
dalvik execution mode was on fast until I changed it in the last second to "jit".
vm.heapsize was changed to 48 because I was testing 32 mb and I saw that it takes a little while to enter in one application. With 48 mb the time is reduced somehow. Please feel free to change it to 32 mb if you want. Dithering, well here is a mistery, I don't know if this works in ICS. It does look a little better than with it changed to 0 and my phone can suport dithering pretty well.
About the reboots, please install set cpu and set your max cpu frequency to a respectable value such as 691 or lower. I suggest using governor smartassV2.
The whole rom does feel a little snappier but we have an issue when someone calls you and after 20 seconds the call gets interrupted. I'll look into that today after work and see if I can fix it somehow.
I've tried Supercharger, the V8 doesn't wanna start on ICS and when applied V6 with option 6, the phone just got stuck on bootloop.
The reason that I've made it like this with apk.s that you can easly uninstall is that I didn't want you guys to have to flash any other optional zips or anything. But as I said, feel free to do what ever you want and uninstall those unused apps.
Oh, If you want to try supercharger yourself, you have to first delete these scripts from /etc/init.d:
03tweaks
04netspeed
05fixsdcardspeed
06loopy_smoothness_tweak
15cleanup_init_ram
16sqlite_optimize
17speedy_modified
Just to avoid any unexpected issues.
L.E:
CAN SOMEONE PLEASE, make a LOGCAT while you are in a call and save it to a txt? I want to see if we can narrow down the problem of disconnecting. I am unable to make a logcat atm.
1ceb0x, back to using your original build.prop, and Setcpu. Things seem more stable.
I'm looking for a notification toggle (cm-style) that has no icon when running (or only hides it, leaves a space.)
I will make a logcat, but I've tried aLogrec and all it seems to produce is an empty file. Should it not be dumping info on any activity I do?
lost101 said:
1ceb0x, back to using your original build.prop, and Setcpu. Things seem more stable.
I'm looking for a notification toggle (cm-style) that has no icon when running (or only hides it, leaves a space.)
I will make a logcat, but I've tried aLogrec and all it seems to produce is an empty file. Should it not be dumping info on any activity I do?
Click to expand...
Click to collapse
Seems stable than samm000's build.prop?
Glad to hear this.
As for the logcat, you cannot use any of the readers on the market because they will not work on ics. I've tried to make a log using android sdk but it seems that we need a file called 'main' in /dev/logs. I tried to make the file manually but then I've encountered an EOF read error on cmd. I forgot to make permissions for the respective file. Will make it again now and see how it goes.
As for cm notification toggle, I don't know what are you talking about. The notification toggle on ICS is nicer than any other available .
Tell me if you have calls issue (your call is disconnected after some seconds)?
Well it is probably more stable because I reduced the cpu speed.
In a voicecall now, 2mins+. Call lost around 3 mins.
6mins+ this time and still going...
lost101 said:
Well it is probably more stable because I reduced the cpu speed.
In a voicecall now, 2mins+. Call lost around 3 mins.
Click to expand...
Click to collapse
Did you checked the box "Force GPU rendering" in Develop Options?
Is it stable because I've added graphical tweaks and some tweaks to speed...
Yeah, 'Force GPU rendering' is enabled. In a voicecall now, 10mins+.
I ended the call myself at 22mins.
lost101 said:
Yeah, 'Force GPU rendering' is enabled. In a voicecall now, 10mins+
Click to expand...
Click to collapse
10 minutes without disconnecting? What's your settings on network? GSM ONLY, or WCDMA preferred?
(to see this, please go to dialer and dial *#*#4636#*#* , then go to Phone information, scroll down and you will see the value above the button "Turn Off Radio").
as default the version is WCDMA preferred. What Radio firmware are you using?
also, did you installed Habarug's tweak to hide the end button call during a call? (it's in samm000's thread).
this information will be helpful! cheers
WCDMA preferred. Radio: 63.18.55.06PU_6.35.15.11
I have not installed Habarug's tweak.
lost101 said:
WCDMA preferred. Radio: 63.18.55.06PU_6.35.15.11
I have not installed Habarug's tweak.
Click to expand...
Click to collapse
and you had 10 minutes without disconnecting? you were able to end the call normally?
1ceb0x said:
and you had 10 minutes without disconnecting? you were able to end the call normally?
Click to expand...
Click to collapse
It was 22mins when I ended the call myself.
Regarding notification toogle this is what I mean: 15 toggle status bar as implemented in this rom. Check the video.
Very ODD.
I have 63.18.55.06OU_6.35.15.01 on my device with WCDMA preferred but I keep getting call disconnected after 10 seconds or so.... regarding the notification status bar power widget, I don't know what to say. I'm not a dev so...
i'm trying to find a way to make a log cat of the calling issue because I don't really want to change my radio because my version seems to be battery friendly...
thank you for your support
Obviously the notification thing isn't even important right now. I shouldn't really have mentioned it.
I thought this radio was considered one of the best to be using, and find the battery life to be good on it.
Don't know if its the best really. But I've flashed it anyway. Since this will end my calling interrupt, it will be a small price to pay if the battery doesn't play well.
Will test the voice calling. Btw, I am maybe working on RC2, with some new tweaks and fixed latinime.apk keyboard..
can confirm right now that the latinime.apk is fixed.
@Habarug: are you using my mod or sam's rom?
Thanks lost, will try your radio, im on .14 atom
Just to clarify, the radio I am using still has calls dropping with ics. It seems to happen at random times. 1 minute into a call, 3 minutes or not at all. Maybe it's because of the numbers I am ringing. I can't be sure they would not drop anyway. But it sounds like it is doing better than some other radios.
Also, what about having a build based off ics 4.0.4?
lost101 said:
Just to clarify, the radio I am using still has calls dropping with ics. It seems to happen at random times. 1 minute into a call, 3 minutes or not at all. Maybe it's because of the numbers I am ringing. I can't be sure they would not drop anyway. But it sounds like it is doing better than some other radios.
Also, what about having a build based off ics 4.0.4?
Click to expand...
Click to collapse
we have to fix this issues first and then talk about another version. anyhow, 4.0.4 is much laggier than this version. i saw a bit of logcat and some awkwardly errors regarding the "animations" but i was unable to save the log for future use.
I've asked Maclaw, a dev from Galaxy Gio/Fit/Mini who made CM9 possible on those device to look at our build and maybe with some luck he can see something that make this calls drop...
managed to past 3 minutes in call with your radio version lost101. cheers
L.E: I am unable to send PM's. so i cannot ask Maclaw for help.. too bad! I'll just have to post on their op!
Come on people.. test the build!
This is a formal request for any developer capable of doing so, to take a look at this problem.
There is a growing number of users noticing a severe battery drain and hot phone at times, caused by the runaway process; (gsiff_daemon)
The threads discussing this as of now are scattered and unorganized, and with the number of users experiencing this problem, it would be excellent to have one central thread for everyone to work together on this.
Here's what we know so far:
The problem occurs for most on a hot-boot, and can be triggered by forcing a hot-boot.
It is not carrier specific, At&t, Tmobile, and Verizon users have all confirmed this problem.
The only reliable way to rid of this at this time, is a reboot, although some have had luck ending the gsiff_daemon process, or renaming the file, although this requires further testing.
Here are a few threads that have been started on the issue, with some good reading:
http://forum.xda-developers.com/showthread.php?p=30074303#post30074303
http://forum.xda-developers.com/showthread.php?t=1800812&page=3
Anyone capable of looking into this, and know what they are looking at enough to determine the cause, will be eternally thanked, and i will personally donate a case of beer(or soda) to whoever fixes it.
Thanks!
is this Gsiff_Daemon issue only for rooted users? I just got it too...after rooting...I never had this issue since june 30, since I've had the phone
I just renamed the file.. problem went away. it doesn't run anymore.. and haven't had any negative effects that I can tell....
do any of you guys have the "increase volume in pocket" setting on in phone-->settings?
also do any of you have motion settings enabled and/or autorotation on?
Seems it has to do with the gyro issue
also are you guys rooted or non-rooted?
Crapppp
Jellybean didn’t solve it. Gsiff_daemon just popped up for me. Just renamed it AGAIN.
Hopefully it won't pop up again
Sent from my SPH-L710 using xda app-developers app
tjb433 said:
The problem occurs for most on a hot-boot, and can be triggered by forcing a hot-boot.
Click to expand...
Click to collapse
FULL REPORT
HARDWARE and OS
I747m, Stock LH1 4.0.4, Rooted
SOFTWARE
SetCpu 384-1512mhz OnDemand
System Tuner Pro 2.5.5 (STP)
Rebooter 1.6.0, Author: DAVIDJR621
BetterBatteryStats 1.11.0.0
Battery: /menu/settings/battery/
NORMAL OPERATION
- Reboot normally until system settles in fully loaded and in idle
- check SetCpu. Scaling should hover at 384mhz and with occasional spikes usually up to 1512.
- check BetterBatteryStats, switch top drop down selection to "Process" and secondary selection to "Since Unplugged". "gsiff_daemon" should NOT be listed there
REPRODUCING THE ISSUE
- Open Rebooter app and launch the HOT REBOOT option and wait for the system to reboot and settle.
- Open SetCpu and you should notice that the scaler will be at 1512mhz >90% of the time. IF NOT...repeat the hot reboot step.
- Open BetterBatteryStats as you did above and notice that "gsiff_daemon" is now listed in there.
- Open Battery info and notice that ANDROID SYSTEM is at the top of the list usually around 60%. Now STARE at Android system and click the refresh button...and notice for a brief Milli Second you will see,,,,"gsiff_daemon". Not sure about this but interesting.
- Open STP, launch it's built in Task Manager, make sure you allow viewing of SYSTEM and KERNEL. (at the bottom you can click on their ICONS) Scroll down near the bottom third of the list where it shows KERNEL elements, and you will see /system/bin/gsiff_daemon. Click on /system/bin/gsiff_daemon. Under CPU Consumption....you can watch the % climb.
- at this point, if you KILL /system/bin/gsiff_daemon, the CPU will settle back down to 384mhz and the statistics of cpu usage will not climb/grow.
WORKAROUNDS
- kill /system/bin/gsiff_daemon/ after a hot reboot or reboot your S3
- with a Root File Explorer, rename your /system/bin/gsiff_daemon to /system/bin/gsiff_daemonBAK and reboot normally. This should prevent the issue but it is not known whether it is adversely affecting any system components.
- /system/bin/gsiff_daemon/ should not show up in STP if you have renamed the file.
themadproducer said:
FULL REPORT
HARDWARE and OS
I747m, Stock LH1 4.0.4, Rooted
SOFTWARE
SetCpu 384-1512mhz OnDemand
System Tuner Pro 2.5.5 (STP)
Rebooter 1.6.0, Author: DAVIDJR621
BetterBatteryStats 1.11.0.0
Battery: /menu/settings/battery/
NORMAL OPERATION
- Reboot normally until system settles in fully loaded and in idle
- check SetCpu. Scaling should hover at 384mhz and with occasional spikes usually up to 1512.
- check BetterBatteryStats, switch top drop down selection to "Process" and secondary selection to "Since Unplugged". "gsiff_daemon" should NOT be listed there
REPRODUCING THE ISSUE
- Open Rebooter app and launch the HOT REBOOT option and wait for the system to reboot and settle.
- Open SetCpu and you should notice that the scaler will be at 1512mhz >90% of the time. IF NOT...repeat the hot reboot step.
- Open BetterBatteryStats as you did above and notice that "gsiff_daemon" is now listed in there.
- Open Battery info and notice that ANDROID SYSTEM is at the top of the list usually around 60%. Now STARE at Android system and click the refresh button...and notice for a brief Milli Second you will see,,,,"gsiff_daemon". Not sure about this but interesting.
- Open STP, launch it's built in Task Manager, make sure you allow viewing of SYSTEM and KERNEL. (at the bottom you can click on their ICONS) Scroll down near the bottom third of the list where it shows KERNEL elements, and you will see /system/bin/gsiff_daemon. Click on /system/bin/gsiff_daemon. Under CPU Consumption....you can watch the % climb.
- at this point, if you KILL /system/bin/gsiff_daemon, the CPU will settle back down to 384mhz and the statistics of cpu usage will not climb/grow.
WORKAROUNDS
- kill /system/bin/gsiff_daemon/ after a hot reboot or reboot your S3
- with a Root File Explorer, rename your /system/bin/gsiff_daemon to /system/bin/gsiff_daemonBAK and reboot normally. This should prevent the issue but it is not known whether it is adversely affecting any system components.
- /system/bin/gsiff_daemon/ should not show up in STP if you have renamed the file.
Click to expand...
Click to collapse
isn'ttthere a period before bak?
eyecon82 said:
Crapppp
Jellybean didn’t solve it. Gsiff_daemon just popped up for me. Just renamed it AGAIN.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
What JB ROM are you using? I had the issue when I was running stock, rooted, with the Sammy KT747 kernel, but after flashing CM10, landing the AOKP KT747 Kernel, and running Pimp My ROM on it, I've never seen it crop back up. (knocking on wood here).
78c10 said:
What JB ROM are you using? I had the issue when I was running stock, rooted, with the Sammy KT747 kernel, but after flashing CM10, landing the AOKP KT747 Kernel, and running Pimp My ROM on it, I've never seen it crop back up. (knocking on wood here).
Click to expand...
Click to collapse
I am using rooted stock rom
This is only an issue with touchwiz, so you won't see it on cm10
Sent from my SPH-L710 using xda app-developers app
eyecon82 said:
isn'ttthere a period before bak?
Click to expand...
Click to collapse
NOPE!
Specifically though, I used uppercase BAK....doubt that makes a difference.
themadproducer said:
NOPE!
Specifically though, I used uppercase BAK....doubt that makes a difference.
Click to expand...
Click to collapse
What is the difference of having or not having a period?
Upper casing probably doesn't make a difference though
eyecon82 said:
What is the difference of having or not having a period?
Upper casing probably doesn't make a difference though
Click to expand...
Click to collapse
Eyecon82...really...don't worry about the period. It's irrelevant.
So long is the file is renamed, it wont be triggered/found by whatever normally triggers/finds it.
http://pastebin.com/siAGdxp4
It looks like it's sending gyroscope and accelerometer data to the locapi, (location application interface) and there's some reference to sns there as well.
So, why would a location app need accelerometer data? Or maybe the question is why would someone who's getting my location data need my accelerometer data, too? What's in it for Samsung that they would bother developing it and roll it out? Why wasn't it there in June?
Ok, having a little fun speculating, but perhaps blackboxing for car accidents? Your phone log is the first thing they check and see if you were texting, or whatever, right before impact. Oh, wait, if they have a location-accessing app, they don't need your locally stored log. Nah, probably something technical with the compass....
Janis;34345281It looks like it's sending gyroscope and accelerometer data to the locapi said:
Yes, I don't have any evidence to support this other than what just happened on my phone. I was out for about a 15 minute walk and I got back. Phone was hot and i noticed a severe drop in battery. I remember reading that Goog Now tabulates how far you walked/jogged monthly or something. Maybe this process is capturing that motion/data for it? Just my speculation. No evidence. I think I'll try renaming the file as I dont really GAF about how far Goog thinks I've walked.
Click to expand...
Click to collapse
I am having this issue. I've just rooted my phone and the file seems to no longer be in /system/bin and running a search for it the file isn't found. Yet it's completely killing my battery. It's quite annoying to have to monitor battery use and kill this off or restart the phone so renaming it would be nice to disable it fully but I can't seem to find the file
harryshepard said:
I am having this issue. I've just rooted my phone and the file seems to no longer be in /system/bin and running a search for it the file isn't found. Yet it's completely killing my battery. It's quite annoying to have to monitor battery use and kill this off or restart the phone so renaming it would be nice to disable it fully but I can't seem to find the file
Click to expand...
Click to collapse
You sure it's gsiff_daemon that's causing the issue? Have you renaming qosmgr in system/bin?
Sent from my SGH-I747 using Tapatalk 2
Sorry, didn't have reply notification. Yes I am sure. I Google'd it after seeing it using 30% of my battery with about 50s use. I will try renaming qosmgr but how do you diagnose which process is actually doing it? This time battery doesn't specifically say gsiff_daemon but not sure if that's where I saw it before.
I have attached my battery use screenshot. Game and screen a the top, fair enough. But 13 hours on battery and 75% drained, 6% of which is 7 seconds of the gpsd process. It's a little odd
Sent from my GT-I9300 using xda app-developers app
fix yet ? mines doing same
gsiff_daemon
Mine has been doing the same ever since the kitkat update.
I am running an unrooted EE note 3 (n9005) in the UK.
Gsiff_daemon is constantly my top battery drainer according to the battery app (35% - 47%).
I have not been able to find any consistent method to either activate this rogue app or to get rid of it.
Is there any solution without rooting it as I understand that renaming it should do the trick?
+1 from me about this problem.
Uprooted, up to date Note 3.
No solution so far, will try turning off WiFi when screen off and auto rotation... Let's see...
Hopefully it'll be fixed soon or in next version. It's a shame, though, my Windows phone pals are teasing me!
Best regards,
Doncho
Kernel
FOR STOCK BASED ROMS ONLY
features :
- kexec-hardboot(multirom support)
- CPU governor - smartmax
- other stuff which I don't remember
SmokeKernel+ProfilesApp+LiveDisplayApp(new updates always will be here)
Performance profiles App
Description :
Power profiles for Smoke kernel
The monitoring window is closed by double-tapping on it
Requirements:
Root access
Necessary actions for the full work of the performace profiles application in android 4.4
1) add app to autostart
2) allow the application to display pop-ups
3) Delete the file power_mode.sh, which lies on the path /bin/
LiveDisplay App
Description :
The application allows you to change the color temperature of the screen
at 8:00 a daily value is set
at 20:00 the night value is set
Requirements:
Root access
Instruction:
1) Install zip via recovery
2) Install Performance profiles and LiveDisplay apps
Changelog:
30.05.2017
31.05.2017
03.06.2017
11.06.2017
16.06.2017
18.06.2017
23.06.2017
06.07.2017
10.05.2018
XDA:DevDB Information
Smoke, Kernel for the Xiaomi Mi Pad
Contributors
Artemka2008, DbIm4pda
Kernel Special Features: Custom performance profiles App, custom powerHAL
Version Information
Status: Testing
Current Stable Version: 1.3.4.1
Stable Release Date: 2017-07-06
Created 2017-05-26
Last Updated 2017-07-06
reserved
Will work on Lineage OS 14? (Oops: didn't see "boot.img for LineageOS14.1(7.1.2)")
Update 1: Works on Lineage OS 14. Testing to see if battery is better on this kernel and performance profile app (only browsing, no gaming)
Coule you make a flashable .ZIP please?
vickdu31 said:
Coule you make a flashable .ZIP please?
Click to expand...
Click to collapse
I'm lazy. I have already completely described the installation. May be later
Thank you for effort. Could anybody compare with F1xy kernel?
Thanku @Artemka2008 and @Dblm4pda
.
.
.
.
Btw Anyone tried antutu with this kernel ?
So far, so good.
I did not yet install the custom powerhal or whatnot. What does it even do?
FYI: You have to reroot the tablet after installing this boot.img.
Anyway, of the performance profiles the high is the only useful if one watches youtube. All other profiles results in occasional jerk/lag in the video.
Deep sleep battery consumption so far has been minimal for me. Usage battery consumption might be a tad higher, at least with the high profile, which is the only useful one unfortunately.
This kernel like f1xy and Foxy all suffer from the same wifi problem that when you wake the tablet from deep sleep and wifi is turned off (wifi option Keep awake: never), it takes 30+ secs for the wifi to activate and reconnect. You can't even enable the wifi by yourself during this time, you basically have to just wait...
I haven't run any antutu etc test cos I don't care what the numbers say. All I care is how it works and feels and how the battery lasts.
I'll keep testing.
I am running LOS14 with the new blobs. Which reminds me, I think I get more of the graphical glitches now than I did before. But this all too subjective atm. to say conclusively if it is the kernel or not.
Tautologica said:
So far, so good.
I did not yet install the custom powerhal or whatnot. What does it even do?
FYI: You have to reroot the tablet after installing this boot.img.
Anyway, of the performance profiles the high is the only useful if one watches youtube. All other profiles results in occasional jerk/lag in the video.
Deep sleep battery consumption so far has been minimal for me. Usage battery consumption might be a tad higher, at least with the high profile, which is the only useful one unfortunately.
This kernel like f1xy and Foxy all suffer from the same wifi problem that when you wake the tablet from deep sleep and wifi is turned off (wifi option Keep awake: never), it takes 30+ secs for the wifi to activate and reconnect. You can't even enable the wifi by yourself during this time, you basically have to just wait...
I haven't run any antutu etc test cos I don't care what the numbers say. All I care is how it works and feels and how the battery lasts.
I'll keep testing.
I am running LOS14 with the new blobs. Which reminds me, I think I get more of the graphical glitches now than I did before. But this all too subjective atm. to say conclusively if it is the kernel or not.
Click to expand...
Click to collapse
Problems with wi-fi are not due to kernels, these are the problems of the system
Artemka2008 said:
Problems with wi-fi are not due to kernels, these are the problems of the system
Click to expand...
Click to collapse
I am not sure what you mean by "system" in this context.
The particular wifi issue I mentioned above does not happen with a stock kernel, only with custom kernels. And it is the only wifi issue I have encountered. No breaking off, nothing else, just a slow reconnection after deep sleep. But if it is a necessary evil while changing the kernel, so be it cos with stock kernel I have much bigger problems and I rather use a custom kernel to get more fluidity of use.
Spassiba for the kernel komrad!
does this kernel support vulkan API?
I ran into a same kind of issue I have with stock kernel; After waking from deep sleep the mipad is usually slow as hell for a minute or 2. Like everything is lagging. A bit like a cold engine which is warming up.
Anyway, I moved back to F1xy cos of this which doesn't suffer from the same issue.
Does this kernel support MIUI?
Richard20000321 said:
Does this kernel support MIUI?
Click to expand...
Click to collapse
all miuis run on Android 4.4.4, do you really think this kernel can run on Android 4.4.4?it only works on Android 7.1.2
---------- Post added at 08:11 AM ---------- Previous post was at 08:08 AM ----------
Richard20000321 said:
Does this kernel support MIUI?
Click to expand...
Click to collapse
there's a "miui smoke rom"using this kernel, maybe you can try that rom, it's also using this kernel
Update
cameras works now
Artemka2008 said:
Update
cameras works now
Click to expand...
Click to collapse
Does this mean camera will work on ROM with new blobs?
maccafan said:
Does this mean camera will work on ROM with new blobs?
Click to expand...
Click to collapse
It's not a kernel problem
maccafan said:
Does this mean camera will work on ROM with new blobs?
Click to expand...
Click to collapse
No
Please make it a flashable zip... Cheers...
Update
Update for performance profiles application
Changelog:
- application was rewritten with Kotlin
- added current RAM freq displaying
- increased low power mode performance
You do not need to reflash the kernel(if u use SmokeKernel), just update the application