[Kernel][GPL] msm_hsic_host wakelock fix (Now with WiFi notification fix!) - Nexus 4 Android Development

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 !

Related

[KERNEL][STOCK] KosiKernel 006 (build 20120605)

Since I've been asked several several times now to release the kernel I'm running on my own phone I took some hours and prepared it (clean build, cleanup of commit comments, etc.).
Beware that this kernel is build for my own purpose and usage-pattern so it may or may not work well for you. I have a pretty tight schedule with a full time job and also working on my master thesis therefore I cannot guarantee any support for this. That's also the reason why I keep this short and simple. Nevertheless if you try it please report some feedback on your experience. Don't let the version 006 irritate you, this is the first publicly available version.
Big thanks go to all developers who made this possible in the first place: spica1234, StefanGünthör, vadonka, and all others who provide the current sources of their kernels
Usual disclaimer
This software is intended for advanced users. You're using this on your own responsibility. I'm not liable for any damages to any hardware and/or data caused by using this software.
Incomplete feature list (see Changelog for detailed changes)
(based on spica1234's SR3R)
spica's powersave mode "2" by default
optimized compilation flags for tegra
removed (for me) unneeded kernel features and useless modules on tegra platform
Ext3/4 support
OC/UV enabled
ramzswap (with snappy)
reduced logging and debugging features
JRCU
loads of small changes to improve performance, stability, efficiency; including cross- and backports from other and 3.x kernels.
non-fancy name
no support guarantee
Known Issues
slowdown after long usage without reboot
sometimes instabilities with WiFi
Download
http://db.tt/LCGOUc1E (kosi006.zip, MD5: cd289d7f9fb378181f85d817121b7e63)
Installation
As usual install ZIP through CWM after performing the obligatory backup. Wipe of dalvik-cace and cache partition recommended.
Can also be combined with spicas Performance Packs for additional performance.
If instabilities arise, try increasing voltage by +25mV (worked on my phone).
Source
https://github.com/kosi2801/LGP990_KosiKernel
I try to credit all the changes I integrate from elsewhere by the appropiate origin both in the commitlog as well as in the Changelog. If you identify a uncredited change please let me know and provide me with the publicly available source so I can give proper reference.
reserved
reserved too
wish you the best of luck sir, new dev are always welcome
Thanks man, my wish came through, thanks for sharing and good luck mate
Sent from latest Django Manouche with Spica Sr2r2 Kernel
Yes there my man comes!
Kosi bro felt very gr8 seeing your kernel. Congrets.
And thank you for giving TRUE honour by using SR3R as base sources with revolutionary OTF. I really feel good that atleast my SR3R sources are belived to be usefull, as Today i can see almost all stock kernels being either fully/partially based on performant SR3R sources. That's a great matter of HONOUR and PLEASURE to me. Thanking you to using it.
BTW you are free to ship Official OTF HP 2X OTF Tweaker Application with your build. I preffer newer Myrt OTF so you can use both but from my side you're free to use any of my work without my permission
I'm eager to flash. To be very frank I found your kernel building tutorials very easy for newbies. Keep updating that thread also, with new tips for newbies.
Once again congrets and keep releasing newer kernels, if you cant manage time then atleast once in a 10-15 days
How nice, also to see yet another Austrian flag on top of a kernel developer thread
kosi2801 said:
Known Issues
slowdown after long usage without reboot
[*]sometimes instabilities with WiFi
Click to expand...
Click to collapse
Would it be correct to say WiFi instabilities cannot be fixed until LG releases an updated driver?
First impression coming from Spica1234 sr2r2 kernel my first notice is reduced smoothness, but it's also well known that sr2 had great smoothness. Anyways it seems to run fine and stable so once again thanks for sharing
Sent from latest Django Manouche with Kosi2801 006 Kernel
akyp said:
Would it be correct to say WiFi instabilities cannot be fixed until LG releases an updated driver?
Click to expand...
Click to collapse
I'm not sure. I integrated some fixes from NVidia directly and tried out some other changes (CONFIG_DEEPSLEEP => only "hibernating" WiFi driver on disable, not completely unloading kernel module). The deepsleep made no change in the short run and locked up in the long run so I deactivated it again. The NVidia patches made it a tad more stable (at least that's my impression) but it's still far from rock-solid.
There are however several other options which are still on my todo list:
check and try bcm4239 driver from CM
check and try bcm4239 experimental driver from Stefan Günthörs repository
check and try bcm4239 driver from NVidia/Broadcom repository (which lacks the LG adaptions and is therefore much more work)
look for other possible sources of updated/changed bcm4239 driver on Tegra boards
check individual commits and fixes in all repositories and integrate/merge/port the sane and safe ones
So there is still some work possible on my side but the possible outcome of each single option is still unknown.
IF, however, LG would make another update to the WiFi driver publicly available this would surely be another highly relevant try/source to have a look on.
Thank you. Glad to know I am not the only one bothered by WiFi problems. I have tried many ROM/kernel combinations and it's the same story everytime: At first it works as it should, then speed begins to drop, then it refuses to be turned on or off, causing a crash. I think I will give the v20s a try.
akyp said:
I think I will give the v20s a try.
Click to expand...
Click to collapse
Please give me a short notice if that solves the issues for you
kosi2801 said:
Please give me a short notice if that solves the issues for you
Click to expand...
Click to collapse
Tried rebuilt v20s for a few days. Sadly the slowdown is still there, but the driver seems a bit more resilient -- I haven't got any errors when turning it on and off.
akyp said:
Tried rebuilt v20s for a few days. Sadly the slowdown is still there, but the driver seems a bit more resilient -- I haven't got any errors when turning it on and off.
Click to expand...
Click to collapse
Did you try with standard LG Mobile update?
wals46 said:
Did you try with standard LG Mobile update?
Click to expand...
Click to collapse
No, only tried the CWM version by Flix: http://forum.xda-developers.com/showthread.php?t=1699106
akyp said:
No, only tried the CWM version by Flix: http://forum.xda-developers.com/showthread.php?t=1699106
Click to expand...
Click to collapse
If you want to test the standard 2x features you'd better to flash the original lg rom distributed in your country, baseband included. After mobile update do a factory reset. If you have problems contact the local lg support. If everyting is ok and want to waste time, try custom rom/kernel. Then all the problems will be between you and xda forum.

Lets talk about CM10 and ICS - with POLL

Hi peeps!
So... moving away and not spam the other dev and general threads, I just wanted to open a new one where we can discuss about the differences between CM10 on old bootloader (cause the other roms are soooo 2011 ) and the new STOCK ICS great tuned roms on NEW BOOTLOADER
I was using DM v30b ICS for a long time and I was pretty satisfied! But after I saw the call bug fix on the official CM10, I didn't even think about it and replaced it
Not that the DMs version isnt fine, but I was remembering that the CM10 version on old bootloader was pretty awesome!
Im using the CM10 official and the only thing I would say against it is the battery life Everything else is awesome!
P.S. This thread is not for DEVs, cause I dont want to offend anyone with posts like "This ROM is much better than this".
Every dev here is FUK*n AWESOME and the jobs they do are amazing... Be honest... before our devs started to tune the phones, we would all be on some freakin apple ****s! (sorry for my language!).
Keep up that good job and ignore our post and threads, its just sharing opinions between consumers
PUT yOUR OPINIONS IN HERE RIGHT NOW !
That's right, Official CM10 is Awesome since LG release their source code. But I will be honest, I tried the first Stock ICS v30a and I was not happy with it because of the speed...even if we have 2 cores. Then I return to cm10...but since we have official source code, the devs start making custom kernel which are really AWESOME, seriously. So, I'm now on cm10 (old bt) with Pidocchio kernel (old bt) for about 5-6 weeks...and it rocks. :good:
Sent from my LG-P990 using xda premium
django manouche x1.2 is good, it has ios 7 onboard
CM10 for new bootloader by pengus77
Flashed it yeastarday and the battery life is amazing.
I think cm 10 is pretty awesome, the only thing holding it back for me using it is the battery drain
And LG's official ICS was ***t if u need something thats stable ( i know it doesn't really belong here ) i think u need to back to GB like temasek's builds, but that's my meaning
pengus77 is doing a very nice job. and like marsgod took his fix to gerrit to be reviewed by cm team and they included into official repository, i think pengus77 job should too. in that way, no need to continue with the new bootloader cause is a waste of space and a mess for everybody to move there with nvflash. id we can continue using our gb bootloader and partition layout, that one we used during about 1 year, why not continue if it is working alright? my vote for cm10 official with those all changes commited into cm repository.
I'm using original locked and unrooted 30B in Italy even it is made for ESA region.
I think that this rom is near to be a definitive stable rom: very smooth and fast, no problems except for a battery drain still high (20 hours autonomy with 40% wifi); the camera could be better, too.
I'm very happy of it and I'm waiting for the same LG release for EU.
I never used overclocking or custom kernels even if I tested most of the custom roms available here on XDA. I must say that I never found a real advantage nor stability testing these roms, maybe now the time for them is near to be over.
Sent from my LG-P990 using xda app-developers app
CM10 for new bootloader by pengus77 for me
No bug, just perfect!
thanks for the opinions! I hope that the new ones here are gonna appreciate it!
Sent from my LG-P990 using xda app-developers app
I am still on Temasek's CM7 as I needed long battery and rock solid/stable operation... Waiting for our CM10 team to fix the battery drain (old boot loader) and I'll take the dive
I have a question about the call bug: when does it usually show up?
I have never experienced it, but at the same time none of my calls are ever longer than 5 minutes.
I'm still on a really early version of CM10, and I've never run into the call bug.
Only problem really is the WiFi drain. Has that been fixed? I haven't been keeping up with the latest nightlies.
deewhy said:
I have a question about the call bug: when does it usually show up?
I have never experienced it, but at the same time none of my calls are ever longer than 5 minutes.
I'm still on a really early version of CM10, and I've never run into the call bug.
Only problem really is the WiFi drain. Has that been fixed? I haven't been keeping up with the latest nightlies.
Click to expand...
Click to collapse
The call bug was said to be caused by a race condition - meaning it creeps up unexpectedly depending on the activity done with the phone in that timeframe.
As for wifi drain, flash the kernel tonyp compiled (containing pengus77's fix), onto any CM10 nightly that came out after the V30a sources dropped (basically December onwards).
You really should get a nightly from December onwards - a lot of things, not just the call bug, were fixed or improved along the way. I'm on 01/03 and having an improved experience over the SU660-based sources.
CM10 by arcee is very stable for me with self-compiled kernel of 24mb ramhack and patches from wkpark(including the lg twin boot logo fix). Very smooth and no BSODs and call bug. Just waiting for cm10.1 to be released by arcee.
aldyu said:
CM10 by arcee is very stable for me with self-compiled kernel of 24mb ramhack and patches from wkpark(including the lg twin boot logo fix). Very smooth and no BSODs and call bug. Just waiting for cm10.1 to be released by arcee.
Click to expand...
Click to collapse
Sound pretty good to me, why dont you share the kernel with US consumers
any news about rhe arm kernel from nicholas?
Sent from my LG-P990 using xda app-developers app
machoman1337 said:
The call bug was said to be caused by a race condition - meaning it creeps up unexpectedly depending on the activity done with the phone in that timeframe.
As for wifi drain, flash the kernel tonyp compiled (containing pengus77's fix), onto any CM10 nightly that came out after the V30a sources dropped (basically December onwards).
You really should get a nightly from December onwards - a lot of things, not just the call bug, were fixed or improved along the way. I'm on 01/03 and having an improved experience over the SU660-based sources.
Click to expand...
Click to collapse
Just to clarify, I flash the ROM first and then flash the kernel afterwards? Do I need to re-flash the kernel every time I flash a new nightly?
deewhy said:
Just to clarify, I flash the ROM first and then flash the kernel afterwards? Do I need to re-flash the kernel every time I flash a new nightly?
Click to expand...
Click to collapse
Yes and yes (since a new nightly will overwrite whatever kernel you have).
machoman1337 said:
Yes and yes (since a new nightly will overwrite whatever kernel you have).
Click to expand...
Click to collapse
Thanks!
And just one last question:
So the callbug is fixed on the newest nightlies, but the WiFi fix has not been submitted/merged yet? So if I want the WiFi fix I still have to flash the kernel tonyp compiled, which I'm assuming is this: http://forum.xda-developers.com/showpost.php?p=36032539&postcount=661 ?
just like that bro
Sent from my LG-P990 using xda app-developers app
just try CM10 by pengus77,it's freaking awesome.Nice power saving and no call bug.

[Kernel][GPL][4.3 JS][August 6][a5] m_plus kernel for mako

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

[KERNEL] Modded MiRaGe

Modded Mirage
Hi All,
Here is the latest kernel I am using which fits my needs.
This will be always synced with MiRaGe and I will add more feature If I need or highly requested from community.
- Synced with latest MiRaGe kernel
- init.d support
- Stratosk's DT2W
- A lots of camera fixes
- Undervolt interface
- Faux123's Dynamic FSync Control
- added busybox
- added mpdfake to resolve touchboost messages
Download:
http://forum.xda-developers.com/devdb/project/?id=3426#downloads
Installation:
fastboot flash boot boot<ver>.img
Please leave your comments below.
Special thanks to;
@stratosk
@mrg666
@faux123
@bedalus
Thanks,
XDA:DevDB Information
Modded MiRaGe, a Kernel for the Google Nexus 4
Contributors
ihancioglu, ihancioglu, mrg666
Kernel Special Features:
Version Information
Status: Beta
Current Beta Version: 2
Beta Release Date: 2014-04-03
Created 2014-03-25
Last Updated 2014-04-04
First comment for future use
aosp or cm based?
and 2nd for future fun
AOSP based kernel and tested on stock rom
I have a dream: a dream that one day, a developer, even someone new to the game, will come along and make an optimized stock kernel, i.e. a kernel with stock mpdecision, but with various optimizations that make it faster. I have high hopes for this kernel, please make my dream come true. Don't make another frankenstein-kernel.
i will test your build and report back.
Updated to v0.0.5
Changes;
- KGSL updates
- Reworked at L2 bus speed optimizations (more responsive now)
- Power efficient workqueue patch
- Simple GPU governor added / enabled by default
- GPU undervolt a little bit to reduce heat
Please test If you interest and let me know.
Thanks,
Hi!
These are my first cycle results with version 0.0.1 and stock rom. I am gladly impressed.
Not hooked to any wifi APs just 3G.
A zip file would be helpful so we could flash it through recovery
Sent from my Nexus 4 using xda app-developers app
fluffier said:
Hi!
These are my first cycle results with version 0.0.1 and stock rom. I am gladly impressed.
Not hooked to any wifi APs just 3G.
A zip file would be helpful so we could flash it through recovery
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Thanks for your results.
I think battery will be better with v5 as well as smoother. Please let me know GPU performance as well If you are playing games.
I can prepare the zip file in next versions. Also you can flash my boot images via Flashify without enter even Recovery
Thanks,
Unable to download new version
message deleted
Hi,
I am not playing any GPU intensive games. Thank you for the tip about Flashify Will report back with v5 results.
Hi there!
These are my results with v5, not hooked to any APs just 3G. As you can see SOT has gone down and i am pretty sure the use i gave to the phone was the same as when i had v1.
I am going back to v1 to see if my previous results stand.
Sent from my Nexus 4 using xda app-developers app
fluffier said:
Hi there!
These are my results with v5, not hooked to any APs just 3G. As you can see SOT has gone down and i am pretty sure the use i gave to the phone was the same as when i had v1.
I am going back to v1 to see if my previous results stand.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I think the reason of this, highest L2 speed for 1026Mhz which is touch boost freq. I just decreased a bit for 1026Mhz.(in v11) Performance is in between v1 and v5 but battery stays much longer like v1.
v11;
- L2 bus speed decreased for 1026Mhz for better battery life
- Synced with Linux 3.4.85
Thanks,
hello @ihancioglu.. if its not a bother could u please provide future versions with any-kernel updater for us custom rom users, as some roms have some modifications in the ramdisk which would be removed by flashing the boot.img.
thanks
Hello!
Using v11 i got some random reboots. It also happened with the other versions but only at the end of the battery cycle and so i thought it was due to the battery finishing even though the indicator still showed 4% or the like. This time the reboots happened pretty often.
Sent from my Nexus 4 using xda app-developers app
fluffier said:
Hello!
Using v11 i got some random reboots. It also happened with the other versions but only at the end of the battery cycle and so i thought it was due to the battery finishing even though the indicator still showed 4% or the like. This time the reboots happened pretty often.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Hi my friend,
Thanks for your reports!
I also realize some random reboots with v11 which causes a bug on slub.c.
I don't have much time for now. So I created a new version with Mirage backend. This is completely stable. You can use it safely.
I will continue my project as soon as have free time.
Thanks,
jjblaster3 said:
hello @ihancioglu.. if its not a bother could u please provide future versions with any-kernel updater for us custom rom users, as some roms have some modifications in the ramdisk which would be removed by flashing the boot.img.
thanks
Click to expand...
Click to collapse
Okay I will create a version with any kernel updater method for you.
Thanks,
apatal said:
I have a dream: a dream that one day, a developer, even someone new to the game, will come along and make an optimized stock kernel, i.e. a kernel with stock mpdecision, but with various optimizations that make it faster. I have high hopes for this kernel, please make my dream come true. Don't make another frankenstein-kernel.
i will test your build and report back.
Click to expand...
Click to collapse
The default mpdecision is the worst inefficient/bloated code I would like to have in such an optimized kernel. That is why I have removed it along with touchboost, dcvs, run_queue_stats. I have developed MiRaGe with the same mindset you describe: optimized stock kernel.
Can I request f2fs support? Patches are linked here.
mrg666 said:
The default mpdecision is the worst inefficient/bloated code I would like to have in such an optimized kernel. That is why I have removed it along with touchboost, dcvs, run_queue_stats. I have developed MiRaGe with the same mindset you describe: optimized stock kernel.
Click to expand...
Click to collapse
Ahh, now that you put it that way....
ihancioglu said:
Okay I will create a version with any kernel updater method for you.
Thanks,
Click to expand...
Click to collapse
i appreciate it buddy.. thanks

Mourta Kernel, the continuation of IODAK's excellent work.

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

Categories

Resources