m_plus kernel for Nexus 4 (mako)!
Hi All,
In an attempt to reduce the confusion related to the two versions of 4.3, I have decided to split my m_plus thread into 3 versions, a version for 4.2 (the previous thread: http://forum.xda-developers.com/showthread.php?t=2256887), a version for 4.3 JS AOSP builds (this one) and a version for 4.3 JW builds (not yet up, but will be in the future).
Disclaimer: As usual, I am not responsible for anything that may or may not happen to your device as a result of using this kernel or any other flashable zips posted by me in this thread.
Kernel Features:
Based on the latest Google Source for 4.3
Built with the Linaro 4.7.3 toolchain (2013.07)
insecure ramdisk (ro.recure=0, ro.debuggable=1)
init.d support (by flashing the full ramdisk, requires busybox installed to /system/xbin)
Undervolting support (down to 600mV)
Gamma Control support (motley, faux and franco interfaces available)
Faux Sound Control support including poweramp
dynamic fsync
simple GPU governor
Builds:
Sources: https://github.com/thracemerin/kernel-Nexus4/tree/m_plus_43_exp_JS
Warning: These builds are for 4.3 builds beginning with the letters JS only, if you flash it on a JW based build you will have all sorts of strange graphical issues.
Personal Request: If you plan to make unofficial builds with features not included in the builds posted by me, please don't link them in the thread, all this does is result in confusion especially if someone has a problem with something you have added, it is much easier for me to provide support if I know that everyone in the thread is running the same builds I am. If you want to make a kernel with these features, feel free to start another thread so that they can be discussed and supported as appropriate.
http://goo.im/devs/thracemerin/mako/m_plus_43/JS_builds/alphas
Latest:
Alpha 5:
Flashable (anykernel): m_plus_43_alpha_5JS.zip
Note: if you need the full ramdisk for init.d support/insecure ramdisk, flash the ramdisk package alpha 4 first.
What's Added:
USB force fast charge
Enable Krait Retention
Various patches and enhancements from CAF
Previous:
Alpha 4:
Note: The anykernel version doesn't include init.d support and insecure ramdisk unless your ROM already has it, if you were on alpha 3 you will retain it.
Note 2: If you flash the ramdisk version on CM, the built-in superuser will stop working, CM includes init.d support anyway.
Flashable (ramdisk included): m_plus_43_alpha_4JS_ramdisk.zip
Flashable (anykernel): m_plus_43_alpha_4JS.zip
What's Included:
all the stuff listed in kernel features
freezer patches by Colin Cross
Thanks:
Google
LG
Qualcomm/CodeAurora
CyanogenMod
_motley
faux123
show-p1984
franciscofranco
stratosk
anyone else I failed to mention (if you feel as though you deserved to be thanked by name, please PM me)
Reserved
PowerHAL Fix:
There is an issue in the stock AOSP powerHAL where the mpdecision touch boost requests are being sent to the wrong socket, as a result there will be unexpectedly poor UI performance. Show-p1984 fixed this problem in his Stockified AOSP build and I pulled the powerHAL and made it flashable for everyone. Just flash it in recovery and reboot, if you want to go back to the stock one just dirty flash your ROM. This shouldn't cause any problems on any ROM even if it has the fix already cooked in, but if it does you can just dirty flash your ROM to remove it. Thanks to show-p1984 for the fix.
43_powerhal_fix.zip MD5: c7cebad04b5f71d067df1a45c6e538f7
One More for Science!
Just flashed. I was losing wifi connection with semaphore when phone went into deep sleep. Ill report back. :good:
do you have to be rooted in order for init.d to work?
keda said:
do you have to be rooted in order for init.d to work?
Click to expand...
Click to collapse
Yep, need to have busybox installed too.
First of all, thanks for your work.
I want to make sure I understand the procedure correctly.
If I use CM10.2, I flash "m_plus_43_alpha_4JS.zip" to maintain the built in superuser.
init.d will still work, cause cm already supports it.
Right now I am on Alpha3 with SuperSU 1.51. So to update to alpha4 I can simply flash over.
If I want to go back to the built in superuser I have to reflash CM, then flash alpha4 via zip.
Is this correct?
Wont stay connected to Google services when phone goes into deep sleep, bars and signal are grey when i turn screen on. I thought Google fixed all the wifi issues with N4 in 4.3 kernel?
AcmE85 said:
First of all, thanks for your work.
I want to make sure I understand the procedure correctly.
If I use CM10.2, I flash "m_plus_43_alpha_4JS.zip" to maintain the built in superuser.
init.d will still work, cause cm already supports it.
Right now I am on Alpha3 with SuperSU 1.51. So to update to alpha4 I can simply flash over.
If I want to go back to the built in superuser I have to reflash CM, then flash alpha4 via zip.
Is this correct?
Click to expand...
Click to collapse
Dirty flash CM, then flash A4 should do it, that's what I did and it worked.
ScumDroid said:
Wont stay connected to Google services when phone goes into deep sleep, bars and signal are grey when i turn screen on. I thought Google fixed all the wifi issues with N4 in 4.3 kernel?
Click to expand...
Click to collapse
Strange, it's working fine for me now.
Thanks, just wanted to reply. Works as you said.
After the first boot I had some strange behaviour,
min cpu clock did not go below 1,026 ghz and GPU Clock did not go above 200 mhz.
A restart fixed it, incase somebody notices similar behaviour.
AcmE85 said:
Thanks, just wanted to reply. Works as you said.
After the first boot I had some strange behaviour,
min cpu clock did not go below 1,026 ghz and GPU Clock did not go above 200 mhz.
A restart fixed it, incase somebody notices similar behaviour.
Click to expand...
Click to collapse
Weird, I didn't notice that.
thracemerin said:
Strange, it's working fine for me now.
Click to expand...
Click to collapse
Mabye its an app i have installed. Kernel is flying btw, nice work.
Is it just me or the option to give location eve with wifi off is ****ing with repeaters... I have two access points in my house and when the option was on the wifi keep disconnecting... Maybe cause In some parts I can have signal from both access points... So weird
Sent from my Nexus 4 using xda app-developers app
ScumDroid said:
Wont stay connected to Google services when phone goes into deep sleep, bars and signal are grey when i turn screen on. I thought Google fixed all the wifi issues with N4 in 4.3 kernel?
Click to expand...
Click to collapse
+1 for this. i am also having same problem.
yash295 said:
+1 for this. i am also having same problem.
Click to expand...
Click to collapse
What ROM are you using?
thracemerin said:
What ROM are you using?
Click to expand...
Click to collapse
Cm 10.2 unofficial nightly.
Sent from my Nexus 4 using Tapatalk 4 Beta
yash295 said:
Cm 10.2 unofficial nightly.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
hmm...working perfectly for me, CM10.2 unofficial and this kernel.
thracemerin said:
hmm...working perfectly for me, CM10.2 unofficial and this kernel.
Click to expand...
Click to collapse
Oh yeah cm might be the problem. Sorry for the inconvenience
Sent from my Nexus 4 using Tapatalk 4 Beta
Related
Hi Folks
I have been trying to solve the msm_hsic_host wake lock problem without introducing the data drop/lockup issues that have been introduced into other kernels by adding the patches from code aurora.
Disclaimer: The usual statements apply, I'm not responsible for your device being bricked, ebola outbreaks, nuclear war, etc... resulting from the use of this kernel, flashing this kernel should be done at your own risk, that being said I have been running various variations of this for the last few days without my phone having any issues.
All Versions now in post 2 below.
What's in this release?
4.2.1 versions: Simply the CM stock kernel pulled from their github here: https://github.com/CyanogenMod/lge-kernel-mako with patches from CAF that I cherry-picked in an attempt to fix the msm_hsic_host wake locks without causing 3G data problems.
4.2.2 versions: Stock AOSP pulled from the android-msm-mako-3.4-jb-mr1.1 repo at https://android.googlesource.com/kernel/msm/ with patches from CAF that I cherry-picked in an attempt to fix the msm_hsic_host wake locks without causing 3G data drops.
What do I do if I get a data drop?
Post here, be as detailed as possible, logs would be extremely helpful so I can see what's going on with your device, because these data drops seem to be somewhat random and don't affect everyone it's very difficult to actually reproduce them on another device on another network, as a result the more information you can give me the better.
My WiFi drops while the screen off resulting in delayed notifications!
To be clear, this is not the same issue, the issue with WiFi disconnecting while the screen off seems to be an Android 4.2.1 issue and exists on all kernels and even different devices running Android 4.2.1, this kernel doesn't do anything to address this issue, whether it fixes it or doesn't is entirely independent of the kernel. A potential fix for this is available from this thread: http://forum.xda-developers.com/showthread.php?t=2072930 Note: It would appear that this hasn't been fixed in 4.2.2 despite Google claiming that it has been, the fixes outlined in that thread still work however. Possible Fix in Post 2
The wakelock is reduced but my battery life is the same or not significantly improved
Well, without these patches the wakelock keeps the phone awake, but if the screen is off and nothing else is going on the kernel is just waiting for the USB bus to suspend so the CPUs are either offline or at their lowest clock speed so they aren't likely using that much power. That being said there should be some improvement in battery life over a 100-0 drain cycle, how much will depend on factors that are mainly not kernel related (time on WiFi, 3G signal strength, apps syncing in the background, etc...).
Wasn't this fixed in 4.2.2? My msm_hsic_host wakelock is way down.
Yes and no, Google took 2 patches that were included in the set I was using on 4.2.1, these two fixes significantly reduced the msm_hsic_host wakelock while on WiFi but not really while on 3G. So, if you use WiFi primarily your msm_hsic_host wakelock will be reduced but if you use your phone primarily on 3G it will continue to be high, though probably lower than it was on the stock 4.2.1 kernel.
Thanks to:
LG - for making such an awesome device
Google - for providing us with the AOSP sources
CyanogenMod - I used their kernel as a base
Code Aurora Forums - for solving the issue
Harsh - for pointing me in the right direction on which CAF patches I was missing
franciscofranco - additional CAF patches that might help
molesarecoming - for the color calibration halfbreed v4 settings.
Koush - the original anykernel format
_motley - the zip file for the anykernel version for N4
jakejm79 - for testing various builds with various patches for me and giving me good feedback
veyka - for testing this build and confirming that he doesn't have data issues with it
socali - for his testing and research on the WiFi delayed notification issue.
4.2.2 Version
Experimental WiFi Fix
Confused about all the fixes floating around? Maybe this will help: http://forum.xda-developers.com/showpost.php?p=40432746&postcount=578
Date: April 15, 2013
Download: hsic_fix_nexus4_wlan_v6.zip
MD5: 8ba0f874efc894c8aaa2e115c5fe2438
See here: http://forum.xda-developers.com/showpost.php?p=40340768&postcount=522
Revert Zip: wlan_revert.zip
MD5: 381013687035626bcb1cbaf609ea431
Note: Flash this if you have flashed any of the WiFi fix versions prior to switching to a different kernel.
Stable Version: (anykernel)
Date: March 04, 2013
Download (any kernel): hsic_fix_nexus4_4.2.2v1.zip
MD5: 17127c1ce03ce0489c49ed7377204a6c
Source: https://github.com/thracemerin/Mako (branch: jb-hsic-rel tag: release-v1)
4.2.1 Version (anykernel)
Date: Feb 04, 2013
Download (any kernel): https://hotfile.com/dl/192620778/4b1c43e/hsic_fix_nexus4_v2.zip.html
MD5: 22be4821f3c16087a04a8084cc0d5703
Source: https://github.com/thracemerin/lge-kernel-mako
Fingers crossed for this, will be testing tomorrow!
With this test kernel I got 11min of hsic wakelock in 11h, which is very simular to what I get on harsh's kernel. (when I was trying it out last night)
I also had no data stuck issue, where as on previous attempts I was always able to reproduce the problem within a few min!
Just to be clear, these patches reduce the hsic wakelock by a lot, while preventing the issue where data would get "stuck", signal would show, but nothing would go in or out.
Edit: as well as fixing the hsic issue, these patches should also reduce power consumption while on mobile data, a general win/win.
Sods law states that the moment we truly have this under control, google will push 4.2.2 with all these fixes anyway
Thanks a lot for bothering todo this!
Sent from my Nexus 4 using Tapatalk 2
Going to give it a try too, thanks for the work mate !
I'm wondering, does the CM team will merge these patches if all work properly ? I don't know the point of view of CM about CAF
Bluewall said:
Going to give it a try too, thanks for the work mate !
I'm wondering, does the CM team will merge these patches if all work properly ? I don't know the point of view of CM about CAF
Click to expand...
Click to collapse
Well, a bunch of the fixes got pushed initially to the CM kernel, but were reverted because of the 3G data stalls, if this works out and 4.2.2 doesn't drop soon or doesn't fix the problem I'd consider resubmitting them to Gerrit, I would want some solid evidence that this works before I go through the trouble however.
Can you please post a flashable zip?
Sent from my Nexus 4 using xda app-developers app
Hi,
It seems to be working.
I have about 6h on battery, 93% left and the msm_hsic_host used 15 m, 4%. No problems with 3g so far.
Firefox17 said:
Can you please post a flashable zip?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I'll get on that later today.
In the mean time I had a few mins to repack it for stock, for the moment it's untested (my device is elsewhere atm), if you're brave feel free to try it, I'll post here later when I confirm it works unless someone beats me to it. Update: Confirmed Working
thracemerin said:
I'll get on that later today.
In the mean time I had a few mins to repack it for stock, for the moment it's untested (my device is elsewhere atm), if you're brave feel free to try it, I'll post here later when I confirm it works unless someone beats me to it. Update: Confirmed Working
Click to expand...
Click to collapse
Any kernel version is now in post 2, I've confirmed that it works on CM, but I can't see why it wouldn't work on other ROMs. Big thanks to _motley for the zip file I used.
Indeed I can also confirm this one really works I have tested for a few hours and the results are great.
Thank you
What is the build date of the CM kernel, just so I can match it with the same date nightly
jakejm79 said:
What is the build date of the CM kernel, just so I can match it with the same date nightly
Click to expand...
Click to collapse
1/15 I believe, the anykernel one that works with CM was built on 1/16, either should work on today's nightly as there were no modifications to the ramdisk in the CM repos.
thracemerin said:
1/15 I believe, the anykernel one that works with CM was built on 1/16, either should work on today's nightly as there were no modifications to the ramdisk in the CM repos.
Click to expand...
Click to collapse
Ok thanks, I will test tonight/tomorrow with the 1/17 nightly
Re: [Kernel][GPL][anykernel][WIP] msm_hsic_host wakelock fix
On MinCo v6 + Franco kernel r34, the zip is giving me bootloops. Tried twice, once on a fresh install.
Sent from my Nexus 4 using xda app-developers app
Re: [Kernel][GPL][anykernel][WIP] msm_hsic_host wakelock fix
spncrmoo said:
On MinCo v6 + Franco kernel r34, the zip is giving me bootloops. Tried twice, once on a fresh install.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Franco's kernel uses a non stock ramdisk which I gather from other threads is only compatible with his kernel, you will probably have to either flash the stockboot.img from here or use one of the reset kernels floating around the forums before flashing this.
Sent from my Nexus 7 using Tapatalk 2
Re: [Kernel][GPL][anykernel][WIP] msm_hsic_host wakelock fix
I haven't tested it fully yet but it really looks like I'm finally getting a normal deep sleep.
Sorry if this post is ignorant, but I just started using CyanogenMod for the first time having gotten a Nexus 4, and I'm not 100% familiar with it yet.
I've flashed your kernel and it is working great with no wakelocks, but will updating to the latest nightly flash the stock CyanogenMod kernel again? meaning I would to reflash yours? Not that it would be a problem given that I have the flashable zip, but just for future reference as to whether I need to reflash your kernel every time I update for nightlies.
Re: [Kernel][GPL][anykernel][WIP] msm_hsic_host wakelock fix
Yes you have to reflash everytime you flash a nightly.
Same here, seems to work great, good job !
Notice: Probably won't be keeping up with this much longer. CM has a slew of other commits, but I've only been including the two responsible for the discoloration...
Franco:
I've compiled franco's kernel with two cherrypicks from CM's github: c53fb6d134 and 07cbfb9a9c
These are required for recent nightlies of CM and its derivatives (caveat: if your rom specifically has commits reverted to not require such a workaround, then of course this isn't pertinent to you).
No changes to ramdisk or .config. Compiled using arm-linux-androideabi-4.7 from android ndk r9.
It should go without saying that you shouldn't flash this unless you understand what those commits are for and have a need for them. Those using the "colorfix" zip or otherwise reverting to an earlier liboverlay.so will find that method no longer "works" with newer builds (it spewed errors in dmesg nonstop when it worked).
IMPORTANT: Make sure you update to the new liboverlay.so if you're currently using the old one or you will have problems. Flash this on a rom that doesn't have the corresponding rom-side commits and you will of course have problems too (and I will laugh at you). As well, make sure to remove any addon.d script that you may have been using, if applicable. I don't know if there are multiple "colorfix" zips in circulation, but the one that I came across looks like it creates /system/addon.d/95-cm.sh. After deleting this file, you should be able upgrade/reflash the rom to bring liboverlay.so back up to date. Or if you're lazy/inept, wipe /system and reflash your rom+gapps.
Because of ramdisk customizations (incompatibilities) among roms/kernels, this zip will attempt to patch your existing ramdisk with franco's changes during flash. Things can obviously go wrong, so be ready.
4.4: 2013.11.29 1411ET: [franco-r195-cm-ziddey.zip]
4.4: 2013.11.25 0257ET: [franco-r194-cm-ziddey.zip]
4.3: 2013.10.26 2049ET r193: [JWR] [JSS/JLS]
-------------------------------------
Faux:
I built faux's kernel with the two commits as well.
4.4.1/4.4.2:
Faux: [030u-CM] [030m-CM]
4.4:
Faux: [029u-CM] [029m-CM]
4.3:
Faux: [028u-JSS] [028m-JSS] [028u-JWR] [028m-JWR]
Faux: [027u-JSS] [027m-JSS] [027u-JWR] [027m-JWR]
Note this is an "anykernel" and uses whatever the existing ramdisk is. If switching from Franco (or another kernel that includes a ramdisk), a "reset" kernel is recommended (reflash rom).
Built with arm-linux-androideabi-4.7, with bfd linker instead of gold.
Same as cm10_colorfix.zip?
Thanks alot! I will see if I can comment on any improvement in battery life or performance.
Sent from my Nexus 4 using Tapatalk
I don't think that these two patches will improve performance or battery life.
droidjam said:
I don't think that these two patches will improve performance or battery life.
Click to expand...
Click to collapse
But the use of incompatible library and the constant stream of errors caused by it may impact negatively on them.
Sent from my Nexus 4 using Tapatalk
Thanks alot for doing this.
Will be flashing this soon, all of @ziddey's mods have worked great!
Using this kernel for a while now. Working good if not better.
Thanks ziddey , for filling in such gaps whenever needed. That helps in keeping the ecosystem open to choices
Sent from my Nexus 4
Just flashed will test battery ect
Sent from my Nexus 4 using xda app-developers app
Is there a specific build I should be on when using PAC? I'm on the 16 and even with colorfix I can only use one other kernel that I know of, hells core. Others don't let me pass the boot animation. The same thing happens with this kernel. No colorfix and I used jss
Sent from my Nexus 4 using Tapatalk 4
Thanks a lot, it works great! I hope you will keep this updated when Franco releases a new version.. I should definitely learn how to compile it by myself
Inviato dal mio Nexus 4 con Tapatalk 4
NUNsLAUGHTER92 said:
Is there a specific build I should be on when using PAC? I'm on the 16 and even with colorfix I can only use one other kernel that I know of, hells core. Others don't let me pass the boot animation. The same thing happens with this kernel. No colorfix and I used jss
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
link to kernel source for pac
ziddey said:
link to kernel source for pac
Click to expand...
Click to collapse
RoliSoft said:
According to this https://github.com/PAC-man/android_vendor_pac/blob/cm-10.2/dependencies/mako.dependencies dependency list, the complied kernel for mako is this: https://github.com/zyonee/android_kernel_google_msm
Click to expand...
Click to collapse
And you said as of which build did it stop working, 10/16? There haven't been any new kernel commits since 10/3: https://github.com/zyonee/android_kernel_google_msm/commits/cm-10.2
Further, here's the cm kernel git for comparo: https://github.com/CyanogenMod/android_kernel_google_msm/commits/cm-10.2
https://github.com/PAC-man/android_vendor_pac/blob/cm-10.2/dependencies/mako.dependencies
It uses cm's mako repo.
ziddey said:
And you said as of which build did it stop working, 10/16? There haven't been any new kernel commits since 10/3: https://github.com/zyonee/android_kernel_google_msm/commits/cm-10.2
Further, here's the cm kernel git for comparo: https://github.com/CyanogenMod/android_kernel_google_msm/commits/cm-10.2
https://github.com/PAC-man/android_vendor_pac/blob/cm-10.2/dependencies/mako.dependencies
It uses cm's mako repo.
Click to expand...
Click to collapse
I haven't been able to since I used the 10/9 nightly. If there haven't been any other changes then I don't know why it won't work. I wiped data before going to the nightly on the 16th and it would boot if I didn't flash a different kernel, but if I did then it'd stay on the boot animation forever. It does that for the 20th too, although I didn't wipe data before going to the nightly.
Sent from my Nexus 4 using Tapatalk 4
Thank you thank you thank you!
Stock camera wont start with this kernel for me on latest 2013-10-21 nightly for me.
Fine here. Referring to gallerygoogle and not gallery2
Sent from my phone. Please forgive typos and brevity.
build r192 is available on Franco's thread
http://forum.xda-developers.com/showpost.php?p=46663872&postcount=50533
Uh huh
Sent from my phone. Please forgive typos and brevity.
Features at a Glace Video
The kernel included is enhanced with:
-Linux v3.4.99 compiled with Linaro GCC 4.9 2014.07 (courtesy Christopher83)
Download:
Install at your own risk
ROM Here md5sum: 8d231f18e4878a205424b9f3b0fbf21e
GApps :: PA works well or Slims works ONLY with dalvik (credit TripFX)
Mahdi Theme
Installation instructions
Installing Mahdi-Rom for the first time, or coming from another ROM:
- Make sure you're running a properly working ClockworkMod-Recovery/Team Win Recovery Project
- Copy GApps and ROM ZIP to your SDCard
- Boot into Recovery
- Flash Mahdi-Rom zip from SDCard
- Reboot system
- Boot back into Recovery
- Flash GApps zip from SDCard
- Reboot system
- Don't restore system data using Titanium Backup!
Upgrading from an earlier version:
- Copy the ROM ZIP to your SDCard
- Boot into Recovery
- Flash the ROM zip from SDCard
- Reboot
Also thanks to:
Google
Cyanogenmod
Slim ROM
Omni ROM
ChameleonOS
ParanoidAndroid
showp1984
Stratosk
faux123
A special thanks to:
Mahdi786 for providing source and layout. Please thank or donate accordingly.
Moose0704 who maintains the Nexus 5 thread
dsmitty166 for helping build this amazing ROM when needed
Manelscout4life
arco68, jocala
det0xx, TripFX, skyrmion
Source:
GITHUB: here
Changes:
Detailed: here Short: here
Reserve
Reserved
I think this may be the rom that will hit over the 3k barrier. at the moment hitting constant 29XX mark in quadrant even with first 3D test staying on avg between 40-60FPS, 38-44FPS 2nd 3D and 23-25FPS on last 3D.
My Setup
Gapps: Banks Min 4.4 7/29/14 build
Runtime: Art
CPU Freq: 1.4Ghz 1.2mV
Govener: Ondemand
I/O Sch: SiO
Additional Tweaks
Malive Booster v2.0
Flashable Seeder by ryu found in seeder op
Hyper Cola v1.6
Once again , Thanks @jfbs for another treat.
To others who are curious, this rom is stacked feature wise, responsive and impressive
Flashed this earlier today and I agree with @det0xx, this ROM has some great customization features and is very responsive!
I've only noticed a few bugs here and there (long pressing location tile doesn't navigate to location menu, needed to re-check and then un-check to disable flip tile effect, unable to remove torch tile), but nothing major. Overall, this is one impressive ROM! Great job @jfbs!
One bug I have is the lockscreen wallpaper disappears and stays black. Did a fresh install, not a major issue, just wanted to report it. Thanks for the rom, really nice.
Sent from my SGH-T679 using XDA Free mobile app
Dvarl said:
One bug I have is the lockscreen wallpaper disappears and stays black. Did a fresh install, not a major issue, just wanted to report it. Thanks for the rom, really nice.
Sent from my SGH-T679 using XDA Free mobile app
Click to expand...
Click to collapse
odd i haven't got that issue or at least not yet. Mind giving more feedback as to
Gapps used/using: List all the ones you have tried only that has this issue. CM, PA, Banks, and/or etc. vers such as 4.4.2 -.4 and build date.
Theme: default or 3rd party if 3rd party link or name of theme
Wallpaper: used gallery or 3rd party app to set it.
Runtime: Art or dalvik
Gapps: banks standard 4.4.4 7-24 build, standard theme. Wallpaper set through gallery, dalvik runtime. The problem seems to come and go. I'm not really concerned with it as at the moment I'm using this device as a media player. If nobody else is having the issue maybe I messed something up when adjusting my settings. When I have the chance I will see if I can sort it out.
Sent from my SGH-T679 using XDA Free mobile app
Dvarl said:
Gapps: banks standard 4.4.4 7-24 build, standard theme. Wallpaper set through gallery, dalvik runtime. The problem seems to come and go. I'm not really concerned with it as at the moment I'm using this device as a media player. If nobody else is having the issue maybe I messed something up when adjusting my settings. When I have the chance I will see if I can sort it out.
Sent from my SGH-T679 using XDA Free mobile app
Click to expand...
Click to collapse
Sorry for the delayed reply been tweaking to hit a constant and stable 3k benchmark. at 2950-98 atm for constant and stable. i've hit 3k just recently however phone becomes unstable. if your phone can handle 1.5ghz oc without problems then the 3k is already possible but battery life i'd assume would drop quite a bit. i've also hit unstable 3k using 1.4ghz and tweaking some settings but haven't messed with it much yet. anyways as far as your issue. yeah it has me stumped without physically seeing everything. If your not worried about and at least to my knowledge no one else is having the same issue. let us know if you do figure out what it is that is causing it.
I got my issue resolved. I'm not sure what caused it, but I fixed it by re-flashing the rom.
Sent from my SGH-T679 using XDA Free mobile app
Dvarl said:
I got my issue resolved. I'm not sure what caused it, but I fixed it by re-flashing the rom.
Sent from my SGH-T679 using XDA Free mobile app
Click to expand...
Click to collapse
prolly just flashed without wiping davlik and not 1 zip at a time per a reboot.
I used this ROM on my s4, it is a really nice ROM. Think I will pull out the exhibit and give it a try.
Well this rom is awesome.
And I finally figured out what I did wrong when trying jfbs's roms. It turns out I was not always loading just one zip at a time, and not leaving it alone long enough after booting the rom.
This time I left it be but with the settings screen on and CPU overlay enabled in developer options so I could tell when it finally stopped thrashing the IO subsystem in the phone (over 90% usage in the overlay, showed blue for a good 20 minutes).
So far so good! Been running it now for a day and no major issues.
Though one niggling thing is no way to adjust the hard buttons back light. I prefer to have it always on with the screen instead of timing out after 5 seconds.
Sent from my SGH-T679 using XDA Free mobile app
helppppp
do i have to flash this ROM with twrp v2.6.3.0 or can i flash it with the latest one?
Andresakapaco04 said:
do i have to flash this ROM with twrp v2.6.3.0 or can i flash it with the latest one?
Click to expand...
Click to collapse
i believe either but i would prefer and recommend the latest TWRP
det0xx said:
i believe either but i would prefer and recommend the latest TWRP
Click to expand...
Click to collapse
correct about either and i 2nd that motion for latest twrp.
TripFX said:
correct about either and i 2nd that motion for latest twrp.
Click to expand...
Click to collapse
thanks well i dint flash with the latest one it worked ...would it make any difference in the ROM speed ..and one more question do i have to flash a kernel to optimize my battery or should i leave Rom as it s... im just trying to make this phone work as best as possbile ???? thanks bye the way
Andresakapaco04 said:
thanks well i dint flash with the latest one it worked ...would it make any difference in the ROM speed ..and one more question do i have to flash a kernel to optimize my battery or should i leave Rom as it s... im just trying to make this phone work as best as possbile ???? thanks bye the way
Click to expand...
Click to collapse
nahh, but if you have issues later on than just flash using updated version. And no the stock kernal is fine
Andresakapaco04 said:
thanks well i dint flash with the latest one it worked ...would it make any difference in the ROM speed ..and one more question do i have to flash a kernel to optimize my battery or should i leave Rom as it s... im just trying to make this phone work as best as possbile ???? thanks bye the way
Click to expand...
Click to collapse
if you really want to get the most follow my oc guide in general op. Note battery life decreases past stock voltage. however higher frequency does not. i would also recommend waiting til you try the phone for a little bit before overclocking. however if you want better battery life and lower cpu temps now without sacrificing performance you can always undervolt the cpu for stock frequency. Stock if i remember correctly is 1ghz at 1.2mV i know almost if not everyone using the galaxy w (which is where most of our stuff comes from) can run 1ghz at 1.1mV as far as i know all our exhibits can as well. I could be wrong but at least from others and my own experience 1.1mV works flawlessly for 1ghz. as far as flashing a kernel to do it with jfbs roms you dont need to flash anything with cars1198's roms you do. Also i would not recommend starting at 1.1mV as a starting point.
EDIT: @jfbs so been running this rom for some time now and i can honestly say this beats AOIP by a long shot now. rock solid, still constant 29xx .8%hr sleep, 24%hr (max 4hr15mins) at stress test usage oc'd at 1.4ghz @ 1.2mV. No rom/kernel sided bugs encountered.
Featuring a new cpufreq interface, AbyssplugV2, intelliplug and a whole host of new additions that are not available in any other kernel for the x3.
Among them are updates only found in this kernel, saner defaults via config, better optimizations for the actual code and a rewritten version of devfreq.
It also have an updated baseband configuration and built in rather than to keep a module as it makes no sense to have a vital function as a module.
https://bitbucket.org/mourta/liquid_kernel_lge_p880-stable/
Kernel: http://www.mediafire.com/download/viy5a3dtaccd0gm/mourta-stable-08-23.zip
If there is a request for it i also have a ROM available based on grouper blobs, AD optimizations and a build around this kernel with a new dev tree.
For kernel install, it's anykernel, you can install it on any custom ROM, for stock and the lastest updates you will have to head over to Modaco and my original thread.
Note that this is a one time release, if you like it you'll have to head over to modaco to get updates.
it should be noted that the recommended settings is using intelliplug (you may need to use kernel tweaker or trickster mod for that if you're not running my ROM, and abyssplugv2, i also recommend ROW for a sheduler and Westwood for your congestion handling.
Note that you can now overclock to any frequency and it will feed the GPU chip with the needed volatage, this is great for cooking a roast beef but not for any practical use.
Quadrant scores are 8k and the last Antutu was at 16487, no overclocking but you won't reach that without using my ROM.
And with that... i'm done.
Thanks to the IODAK, Fransico, Adam77Root, Faux123 and others that provided code and/or input.
Oh, what I see here? The awesome kernel I'm testing with @ottomanhero and lucaarx and the great dev and friend @IcanhasLG coming back on xda? Let's rock hard&heavy, right now!
peppethustra said:
Oh, what I see here? The awesome kernel I'm testing with @ottomanhero and lucaarx and the great dev and friend @IcanhasLG coming back on xda? Let's rock hard&heavy, right now!
Click to expand...
Click to collapse
We'll see how this goes.
Thankfully i am in touch with a mod that will keep this drama free,
And for anyone wondering, peppethustra is head of my testing crew, you get stable releases because of them.
It should be noted that i'm still going to prefer the forum that greeted me over the one that shunned me from the get go, updates here will be sporadic at best but on time on the other forum.
It's great to see your work on XDA.Now everyone can experience your awesome work
P.S. you can find neccessary links in my signature
Great work, running your kernel now.
But Iodak was not updated since long ago and its sources does not contain many great fixes from cm11 kernel.
Thats why Demetris relased Cyodak kernel in Android development section. It's Iodak brought up to date with latest cm 11 kernel .
It would great to see Muorta Kernel based on Cyodak instead of old Iodak. We would have your exclusive features with up to date cm11 kernel upgrades. But maybe you already upgraded iodak's source, let us know
FunkyRasta said:
Great work, running your kernel now.
But Iodak was not updated since long ago and its sources does not contain many great fixes from cm11 kernel.
Thats why Demetris relased Cyodak kernel in Android development section. It's Iodak brought up to date with latest cm 11 kernel .
It would great to see Muorta Kernel based on Cyodak instead of old Iodak. We would have your exclusive features with up to date cm11 kernel upgrades. But maybe you already upgraded iodak's source, let us know
Click to expand...
Click to collapse
Obviously, the real necessary updated patches have been implemented yet ("continuation" means this, too), so it's not necessary nor in Mourta's plans to base it on cyodak (which really isn't the only way to find updated code for our device)
peppethustra said:
Obviously, the real necessary updated patches have been implemented yet ("continuation" means this, too), so it's not necessary nor in Mourta's plans to base it on cyodak (which really isn't the only way to find updated code for our device)
Click to expand...
Click to collapse
That's what I wanted to know, as OP didn't explicitly stated it. Thanks
FunkyRasta said:
That's what I wanted to know, as OP didn't explicitly stated it. Thanks
Click to expand...
Click to collapse
Outdated sources never are a good base for developing a fresh new kernel or ROM, if there is a new compatible code implementation ready to be merged into the code That's the first thing a good developer checks (and if you can, look at Mourta's bitbucket linked in the OP to view his commits, there will be all the principal news about new code implementations)
Tried this but I loose my modem every now and then and the screen won't wake sometimes.
baxtex said:
Tried this but I loose my modem every now and then and the screen won't wake sometimes.
Click to expand...
Click to collapse
Go to Modaco and find newer version (26/8/2014) . It will resolve problems like yours
Okay will do.
How's the deep sleep ?
Written from my Optimus 4X powered by Omni 4.4
LGaljo said:
Go to Modaco and find newer version (26/8/2014) . It will resolve problems like yours
Click to expand...
Click to collapse
this version, according to trickster mod, does not use deep sleep state and still screen won't wake up sometimes. so i dropped it for now.
greetings
peter
peter_altherr said:
this version, according to trickster mod, does not use deep sleep state and still screen won't wake up sometimes. so i dropped it for now.
greetings
peter
Click to expand...
Click to collapse
Can you give more info about your ROM, kernel settings, setup etc. and provide a logcat if possible? That's a rare issue you're having there.I've used my phone for 20 hours now, (%3 battery left) and it slept for about 15 hours, same version.
I suggest you to try flashing the kernel twice.I had such problems with iodak kernel back in the time and flashing it twice had fixed the deep sleep issue.
ottomanhero said:
Can you give more info about your ROM, kernel settings, setup etc. and provide a logcat if possible? That's a rare issue you're having there.I've used my phone for 20 hours now, (%3 battery left) and it slept for about 15 hours, same version.
I suggest you to try flashing the kernel twice.I had such problems with iodak kernel back in the time and flashing it twice had fixed the deep sleep issue.
Click to expand...
Click to collapse
+1
@peter_altherr And more important thing: have you at least wiped cache and dalvik before flashing the kernel? If yes, try wiping system partition too (no factory reset, you can leave /data partiton intact) then reflash ROM, gapps and kernel, and see how it goes..wait 3 or 4 minutes before trying to wake up device, after the first boot, and deep sleep would start without problems
I have tried the 26/8 version but that still gives me RIL problems, I get no signal whatsoever. I cannot grab a logcat as I need my phone to work right now but I'm Running latest beanstalk version.
baxtex said:
I have tried the 26/8 version but that still gives me RIL problems, I get no signal whatsoever. I cannot grab a logcat as I need my phone to work right now but I'm Running latest beanstalk version.
Click to expand...
Click to collapse
Wait for next version, great changes will come even about this issue
@peter_altherr you should unplug it from charger and try unplugged.
when charging cpu never reaching deepsleep.
@ whoever had freeze/sod problems with last kernel version: a new fixed release has been uploaded (it's a minor release: reverted GPU OC, which was causing the problem). Check official thread for the download link
my phone does not see SD card with 0902
and yes im 100% sure its kernel problem....recovery sees my sd, and so iodak kernel
PixN Kernel​So this is the only custom kernel currently available. It's got a custom hotplugging solution and built-in exfat support. The camera fixes are iffy at 2.99b, works in 2.99
This is best used with my custom rom, here, but will work with any AOSP N based rom.
Maybe it'll work on CM devices too but I'm not sure. You may lose recovery on flashing this. Don't panic, just flash Zach's TWRP recovery after the kernel.
Eventually this will see many optimizations.
Built with the regular 4.9 toolchain. (Uber from 3.2)
About the screen dimmer:
You can echo 0 to disable and echo 1 to enable it via the sys path /sys/module/mdss_fb/parameters/backlight_dimmer
Click to expand...
Click to collapse
Or just use ExKernel Manager.
Downloads
In the DevDB Downloads tab. Since for some odd reason DevDB is giving me 410 when I tried to upload the newest kernel, it's uploaded as a 7z file. Extract it and flash/profit.
DevDB is down right now so the latest release is hosted on MEGA (from version 3.4)
The link to the folder is here
Changelogs
Release 1
Initial Release
Added (off by default) brightness dimmer.
Several tweaks for memory management/performance
Some commits for camera management, may or may not help.
Release 2
Interim Release
Added sdcardfs (test exfat behavior?)
Elementalx Governor
Row i/o scheduler
Westwood TCP Congestion Algorithm
Release 2.99
Beta Release
Fixed Camera
Bluetooth temporarily broken
Memory, touch input fixes
Fixed a rare random reboot
Fixed the ipa wakelock and some others
Release 2.99b
Beta Release
Bluetooth still temporarily broken (Will be broken on all 2.99, wait for 3.)
Added the impulse, intelliactive and intellidemand governors
Added proper powersuspend
Also added the Alucard Hotplug
NATIVE EXFAT SUPPORT! (Forgot to enable, sorry)
Release 2.99b1
This is a MAJOR release, but the bluetooth isn't working so still 2.99. Everyone should please use this one for battery and performance. Can't comment on the camera.
Beta Release + Super Stable Battery
Bluetooth still temporarily broken (Will be broken on all 2.99, wait for 3.)
Massive zswap and zram improvements
Fsync on/off support
Frandom
Faster Boot
Adreno Idler
Overclocking
NATIVE EXFAT SUPPORT!
Release 2.99b1b
This is a bugfix release.
Fixed slow charging.
Release 3.1b
This is a major release.
Added color control.
Fully tickless.
Bunch of other stuff.
FIXED BLUETOOTH!!
Rebuilt kernel for single sims with an older config to hopefully fix the SD Card (Needs testing)
Release 3.1b
This is a major release.
Built with Uber.
Also with Clang optimizations.
Rebase config to stock to fix bugs.
Added CPUQuiet.
Release 3.3
This is a major release.
Built with Uber 6.
Bunch of optimizations.
Added Nightmare, Darkness, Chill governors.
Added Alucard Boost.
Also added the Thunderplug Hotplug.
There's a new fiops interactive i/o scheduler.
A lot of wakelocks have been exposed but don't disable them and start filing bug reports, they're as per user discretion.
Release 3.4
This is a major release.
Fixed the Optimizations
More Wakelocks
Updated sources to reflect latest upstream additions
Might have fixed Bluetooth disconnects
Release 3.4
This is a major release. Go for it. It's on DevDB
Lots of Optimizations
Uses Power Efficient Workqueues
Added ARM64 cpuidle
Fixed Zen_interactive
XDA:DevDB Information
PixN Kernel, Kernel for the Sony Xperia Z5
Contributors
HaoZeke
Source Code: http://github.com/HaoZeke/kernel
Kernel Special Features: Camera, Dimmer, Sdcardfs, Overclock, Adreno Idler, Frandom, exFAT
Version Information
Status: Beta
Current Stable Version: 3.3
Stable Release Date: 2016-12-25
Current Beta Version: 3.5
Beta Release Date: 2017-01-12
Created 2016-11-16
Last Updated 2017-01-11
The e6653 kernel will be uploaded in a few hours...
HaoZeke said:
The e6653 kernel will be uploaded in a few hours...
Click to expand...
Click to collapse
Couldv you add exfat support?
albertobom said:
Couldv you add exfat support?
Click to expand...
Click to collapse
Sure, but I think that also needs the rom to specifically add the module too..
(I'll add that to the linked rom)
@HaoZeke, I have been using your rom for almost 2 days now. It is much similar to the other AOSP Nougat. In both the cases, the battery drains fast. Does not even last half a day. The UI is not very smooth. The touch also needs some work on it.
ganeshbiyer said:
@HaoZeke, I have been using your rom for almost 2 days now. It is much similar to the other AOSP Nougat. In both the cases, the battery drains fast. Does not even last half a day. The UI is not very smooth. The touch also needs some work on it.
Click to expand...
Click to collapse
Ok... Did you try the new kernel? The latest version (coming) has elementalx as the governor (enable by kernel auditor mod)..
My battery seems to do ok with the suggestions in the op...
Touch seems ok too.. Actually I build multiple times a day, it's possible an issue sneaked in.
The main reason for this rom is basically the native substratum support..
Does your substratum app show substratum or substratum legacy? In the uploaded release 1 for e6653 there was a small bug which was fixed for 1.1
EDIT:- I'm grateful for the feedback but this thread is for the kernel and related issues... Please post in the right thread...
HaoZeke said:
Ok... Did you try the new kernel? The latest version (coming) has elementalx as the governor (enable by kernel auditor mod)..
My battery seems to do ok with the suggestions in the op...
Touch seems ok too.. Actually I build multiple times a day, it's possible an issue sneaked in.
The main reason for this rom is basically the native substratum support..
Does your substratum app show substratum or substratum legacy? In the uploaded release 1 for e6653 there was a small bug which was fixed for 1.1
EDIT:- I'm grateful for the feedback but this thread is for the kernel and related issues... Please post in the right thread...
Click to expand...
Click to collapse
Sorry for posting in the wrong section. I recognized this after posting, so left it at that.
I am contnuing this in the right section.
Latest version uploaded for both variants. Extract the 7z and fastboot (or twrp) flash the kernels. This release fixes camera issues.
Could e6653 users with sdcard issues please test this kernel?
albertobom said:
Couldv you add exfat support?
Click to expand...
Click to collapse
Added exFAT support...
HaoZeke said:
Added exFAT support...
Click to expand...
Click to collapse
I will wait for a full flashable zip file with your amazing rom and kernel.
Keep up the amazing work.
albertobom said:
I will wait for a full flashable zip file with your amazing rom and kernel.
Keep up the amazing work.
Click to expand...
Click to collapse
Actually a full flashable version isn't currently a priority, since actually the system.img is a bit large to be zipped (cuz of the addition of gapps).
Eventually I'll start zipping the kernels, but again, not a priority..
It should be easy enough to set up.
First download the latest system.img from the ROM thread.
Then get the latest kernel here. (or whichever feature-set you want)
Also grab the recovery.
Put the phone in bootloader mode.
fastboot flash boot boot.img (or whatever the kernel is called)
fastboot flash recovery recovery.img
fastboot flash system system.img
Hey the latest build is up for anyone interested... This might be the last release for a while...
I feel like it's significantly improved... The camera needs work and some other bugs...
Battery life is around 1-1.5% idle.
Testers please post feedback.
@HaoZeke i flash the rom yesterday and the kernel. For me everything was working fine except the camera, whis is upside down. I like the rom, very smooth, i cant tel the battery cause i have 12 hs with it. The kernel you put for test for me is working fine. This kernel will work on CM?
Zaisesl said:
@HaoZeke i flash the rom yesterday and the kernel. For me everything was working fine except the camera, whis is upside down. I like the rom, very smooth, i cant tel the battery cause i have 12 hs with it. The kernel you put for test for me is working fine. This kernel will work on CM?
Click to expand...
Click to collapse
Excellent, I'm glad the test kernel is working, could you try 2.99b1? That has many battery and performance fixes, the older kernels were giving me around 2-3% battery usage per hour, with the new one it's 1-1.5%..
CM I'm not sure, it should maybe work with cm-14.0 but cm-14.0 has been depreciated in favor of cm-14.1 ...
I don't know if there is a cm14.0 for the Z5..
By the way, if I may ask, why are you interested in CM ? Any particular feature?
I ported substratum on AOSP since the cyanogen theme engine wasn't ready for nougat...
So I was wondering if there was anything else people particularly wanted...
HaoZeke said:
Excellent, I'm glad the test kernel is working, could you try 2.99b1? That has many battery and performance fixes, the older kernels were giving me around 2-3% battery usage per hour, with the new one it's 1-1.5%..
CM I'm not sure, it should maybe work with cm-14.0 but cm-14.0 has been depreciated in favor of cm-14.1 ...
I don't know if there is a cm14.0 for the Z5..
By the way, if I may ask, why are you interested in CM ? Any particular feature?
I ported substratum on AOSP since the cyanogen theme engine wasn't ready for nougat...
So I was wondering if there was anything else people particularly wanted...
Click to expand...
Click to collapse
I will give a try tonight. I line cm cause allways works very good for me. Mm.. I like you dont need to flash supersu to get root. But with your rom and cm. There is no diference. Just cm is 7.1 and yours 7.0. I really like both, the only thing i dont like and more useful for me are camera and fingerprint, which both arent working. I will test the new kernel and will tell you in a few hours. Thanks!
Zaisesl said:
I will give a try tonight. I line cm cause allways works very good for me. Mm.. I like you dont need to flash supersu to get root. But with your rom and cm. There is no diference. Just cm is 7.1 and yours 7.0. I really like both, the only thing i dont like and more useful for me are camera and fingerprint, which both arent working. I will test the new kernel and will tell you in a few hours. Thanks!
Click to expand...
Click to collapse
I'm glad the rom is working well... Actually hold off the kernel, in a short while I'll upload another (really the last for a few days)
Actually the sony sources for 7.1 aren't ready since sony uses 3.18 as a Linux kernel base...
The integrated su I was planning to add for the next rom release..
I used to be a huge cm fan but recently I feel cm has left supporting sony phones.. So.. I switched to aosp
HaoZeke said:
I'm glad the rom is working well... Actually hold off the kernel, in a short while I'll upload another (really the last for a few days)
Actually the sony sources for 7.1 aren't ready since sony uses 3.18 as a Linux kernel base...
The integrated su I was planning to add for the next rom release..
I used to be a huge cm fan but recently I feel cm has left supporting sony phones.. So.. I switched to aosp
Click to expand...
Click to collapse
Yes, al cm roms are unofficial. I like aosp and cm cause the battery was allways better. But i do love stock for the camera, fingerprint and stability. And im allways changing roms. I like your aosp rom. For now is very stable. When can i try the kernel i will tell you. Thank!
Camera fix out.
New release fixing the charging.