This kernel is based on teamhacksung's kernel for Jellybean
Many Thanks to:
Teamhacksung
Zacharias.maladroit
Onecosmic
ytt3r
TK Glitch
Ezekeel
Eugene373
franciscofranco
Sunra
scheichuwe
perka
sztupy, for his great work, to get usb host mode driver
mialwe
stratosk
F4k for the idea to flash bigmem libs
...
sources:
https://github.com/DerTeufel
Click to expand...
Click to collapse
Working on this kernel is taking many hours almost every day. With a small donation, you show me, that my work is appreciated by you.
If you like this kernel, please donate to me
Download link and changelog can be found here:
http://www.hellybean.com/jelly.html
Click to expand...
Click to collapse
Kernels with VC in the name are coming with Voodoo Color
reserved for later
Awesome kernel.
Just a heads up Devil3_1.4.1_Jellybean_vibrant_CFS_BLN_VC_20120905 is causing CM10 nightly 9-17 to fail boot up. When you would normally see the blue Cyanogenmod circle, all you get is a black screen after flashing Devil 1.4.1. I've tried reflashing many times with Devil 1.4.1 to no avail. I can confirm that it is not a corrupt file as I have verified that the sha256 hash of the file is f7e321eee1992f35f7b963ccc23f987d319b86f82c04936e094edfc430d9ae40.
closedcircuit said:
Just a heads up Devil3_1.4.1_Jellybean_vibrant_CFS_BLN_VC_20120905 is causing CM10 nightly 9-17 to fail boot up. When you would normally see the blue Cyanogenmod circle, all you get is a black screen after flashing Devil 1.4.1. I've tried reflashing many times with Devil 1.4.1 to no avail. I can confirm that it is not a corrupt file as I have verified that the sha256 hash of the file is f7e321eee1992f35f7b963ccc23f987d319b86f82c04936e094edfc430d9ae40.
Click to expand...
Click to collapse
I'll upload new version tomorrow. There have been gpu changes.
Sent from my GT-I9000 using Tapatalk 2
any new version? I am also on 0917 nightly and is waiting
I just noticed that the new Devil3 Kernel 1.5.2 is out! (Check download link)
Will that work with the newest CM10 nightlys?
Edit: Just installed on CM10 0919 and working great. Thanks!
new kernel + changelog at my website: http://www.hellybean.com/jelly.html
Flashed the latest kernel on top of the latest AOKP build... Screen goes blank and doesn't respond after the Devil boot logo.
This kernel should be compatible with AOKP, shouldn't it?
gunks said:
Flashed the latest kernel on top of the latest AOKP build... Screen goes blank and doesn't respond after the Devil boot logo.
This kernel should be compatible with AOKP, shouldn't it?
Click to expand...
Click to collapse
Gunks, did you flash a cleaning script ? I so that's what it is. I noticed that KCS breaks stuff on JB. I just flash new kernels now just dirty
Dougfresh said:
Gunks, did you flash a cleaning script ? I so that's what it is. I noticed that KCS breaks stuff on JB. I just flash new kernels now just dirty
Click to expand...
Click to collapse
I actually just flashed it right on top of it. Once getting the blank screen I pulled battery, went into recovery, and used KCS, flashed kernel again and the same thing happened. But yeah I think you are right probably best not to use that outdated script anymore. I think my issue is that AOKP may not have merged the CM teams gpu changes. Which I find weird, I thought they used the latest CM code... Oh well, guess it'll work in the next build.
So many thanks for this! This is seriously the first time in probably a year that the GPS actually works on this damn phone! That and it's the first kernel I've ever used that consistently lets me overclock my phone without issues galore.
This kernel with CM10 is seriously the best Android experience I've ever had on my phone.
gunks said:
I actually just flashed it right on top of it. Once getting the blank screen I pulled battery, went into recovery, and used KCS, flashed kernel again and the same thing happened. But yeah I think you are right probably best not to use that outdated script anymore. I think my issue is that AOKP may not have merged the CM teams gpu changes. Which I find weird, I thought they used the latest CM code... Oh well, guess it'll work in the next build.
Click to expand...
Click to collapse
I recall using aokp jb2 a few days ago with semaphore (sorry der!) and it booted fine..I might have used Devils, but not the one that came out today. Try 1.4.x
Dougfresh said:
I recall using aokp jb2 a few days ago with semaphore (sorry der!) and it booted fine..I might have used Devils, but not the one that came out today. Try 1.4.x
Click to expand...
Click to collapse
1.4.x works well. been using with aokp2 for last 2 days now.
Aokp is not updated yet. It should be working soon again
Gesendet von meinem GT-I9000 mit Tapatalk 2
gunks said:
I actually just flashed it right on top of it. Once getting the blank screen I pulled battery, went into recovery, and used KCS, flashed kernel again and the same thing happened. But yeah I think you are right probably best not to use that outdated script anymore. I think my issue is that AOKP may not have merged the CM teams gpu changes. Which I find weird, I thought they used the latest CM code... Oh well, guess it'll work in the next build.
Click to expand...
Click to collapse
Same here. No cleaning script, I came from stock SlimBean and flashed Devil right on top of it. Had to pull battery to get into recovery, now running Stock SlimBean again and eagerly waiting for Devil to work.
Weitermachen!!
I have the same issue with 1.4.1, black screen on CM10 0917 nightly. Only after I rebooted, I can't even get to recovery.
Correction: I booted once, but with black screen. Try to "adb reboot recovery" and it sat forever on the Samsung screen. Tried to pull battery, can't get to recovery.
It's tricky getting back into recovery after the 1.4.1 flash with CM10 0917 nightly. You need to hold "Volume Down + Home & Power" until it cycles through the Devil kernel boot screen, and as soon as it reboots and shows the the "Vibrant" boot screen, release the power button while still holding onto Volume down & Home. It take a little timing and a few tries to get the power release correct.
Der I just flashed Devil 1.5.2 JB kernel on top of Blackbean v4 rom after fully booting the rom with it's stock kernel. Everything was super smooth except for the fact that I get an "Unknown error code during application install:"-24" when downloading any app via the Play Store. The stock kernel doesn't exhibit this problem and it downloads apps fine. Do you have any idea what in the DEVIL JB kernel could be causing this error? Have you noticed any ill effects of having VSYNC enabled in Devil JB v1.5.2? It feels smoother to me with it enabled. Does the latest HB0921 kernel have VSYNC enabled? I noticed the HB0917 and up builds feel smoother then previous HB builds so maybe VSYNC enabled is the reason for the extra speed. Thank you so much Der for continuing to support Voodoo Color with all your Vibrant kernel builds even when all the other devs have no interest to compile a VC kernel. There are quite a few of us VC freaks who can't use anything but VC kernel. I have shown my Vibrant to numerous people comparing VC vs CMC on the same homescreen and everybody chose the VC by a long shot saying that the overall contrast, colors, and sharpness blew away CMC. I can't even look at the Galaxy S2 screen with it's bland Samsung stock colors when compared to my fabulous rich VC screen with better pixel density.
hurtz777 said:
Der I just flashed Devil 1.5.2 JB kernel on top of Blackbean v4 rom after fully booting the rom with it's stock kernel. Everything was super smooth except for the fact that I get an "Unknown error code during application install:"-24" when downloading any app via the Play Store. The stock kernel doesn't exhibit this problem and it downloads apps fine. Do you have any idea what in the DEVIL JB kernel could be causing this error? Have you noticed any ill effects of having VSYNC enabled in Devil JB v1.5.2? It feels smoother to me with it enabled. Does the latest HB0921 kernel have VSYNC enabled? I noticed the HB0917 and up builds feel smoother then previous HB builds so maybe VSYNC enabled is the reason for the extra speed. Thank you so much Der for continuing to support Voodoo Color with all your Vibrant kernel builds even when all the other devs have no interest to compile a VC kernel. There are quite a few of us VC freaks who can't use anything but VC kernel. I have shown my Vibrant to numerous people comparing VC vs CMC on the same homescreen and everybody chose the VC by a long shot saying that the overall contrast, colors, and sharpness blew away CMC. I can't even look at the Galaxy S2 screen with it's bland Samsung stock colors when compared to my fabulous rich VC screen with better pixel density.
Click to expand...
Click to collapse
Did the market error go away, after flashing back the default kernel? Normally, this is nothing, the kernel controls, and the error codes don't tell me anything.
Vsync has been enabled long time ago, but it seems like it was causing about 5% CPU load. This got fixed now.
The hb kernel always has the same features, as I am testing new things before, and I only use my Rom.
Gesendet von meinem GT-I9000 mit Tapatalk 2
Related
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.
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
---------------------------------------------------------------------------------------------------------------------
This kernel is based on @pabx work with most features from Trinity 4
by @morfic added (back to Trinity roots again )
Zombie Kernel Source
Downloads:
Zombie-AOSP-build1
Zombie-AOSP-build2
Zombie-AOSP-build3
Zombie-AOSP-build4
------------------------------------------------------------------------------------------------------------------------
Features already done by @pabx:
*Vibration Sysyfs Control
*Double tap to Wake
*Upstream to Linux 3.4.94
*Many more..
Additional Features:
*Compiled with Linaro GCC 4.9 and -02 Optimisations and tuned CFlags
*Hotplug-free
*Removed wasteful debugging
*ROW-Scheduler and various Scheduler-Optimisations
*TCP_CONG_CONTROL (Westwood default)
*F-Sync-Control
*Leaner build
Note:
This kernel is based on @pabx AOSP-Kernel and will most likely
only work on his AOSP-Builds.
Credits:
@morfic for Trinity
@alnikki25k and @DooMLoRD for helping and tutorials;
@faux123, @franciscofranco, @mrg666, @mathkid95, @motley, @Christopher83, @morfic, @pabx, @show-p1984
XDA:DevDB Information
Zombie, ROM for the Sony Xperia Z
Contributors
Tommy-Geenexus
Version Information
Status: Beta
Beta Release Date: 2014-06-22
Created 2014-06-22
Last Updated 2014-06-30
Changelog:
build 1:
*Initial release
*All features from OP added
build 2:
*merged latest CAF-Updates
*Increased bus freq @ 128mhz gpu clock
build 3:
*Added (absolute) Voltage Control
This control differs from others, more infos here
build 4:
*Updated Makefile Optimisations
*Fixes to Voltage-Control (range now from 750-1300 mA)
*Adjusted kernel fairness
*Merged latest updates by @pabx
Great to see a new kernel for AOSP.
Wait for a long time.
Edit: not suitable for slimKAT 5.9 build. The device didn't boot and stick at the slim logo.
I know you've said it'll probably only work on AOSP ROMs.
But curiosity got the best of me and I tried it on PAC ROM, I'm guessing there'll be a lot more like me who would want to try this on various ROMs so i'll just keep adding the ROMs I've tried the kernel on and whether it booted or not.
PAC ROM (21-06 nightly) - Stuck at boot animation.
AOKP- Won't boot
Beanstalk- same as above
PS: I do not expect you to debug these or even reply to this.
Thanks for the kernel. :good:
It works only on @pabx 4.4.4 AOSP builds, sorry.
I can't and won't add support for other roms, because then it becomes a mess again..
Xperia Z / AOSP 4.4.4
venky716 said:
I know you've said it'll probably only work on AOSP ROMs.
But curiosity got the best of me and I tried it on PAC ROM, I'm guessing there'll be a lot more like me who would want to try this on various ROMs so i'll just keep adding the ROMs I've tried the kernel on and whether it booted or not.
PAC ROM (21-06 nightly) - Stuck at boot animation.
PS: I do not expect you to debug these or even reply to this.
Thanks for the kernel. :good:
Click to expand...
Click to collapse
Try the AOSP build mentioned, it's running great
Xperia Z / AOSP 4.4.4
I recommend pabx aosp build. Will test your kernel
toby913 said:
I recommend pabx aosp build. Will test your kernel
Click to expand...
Click to collapse
let me know how it goes
Xperia Z / AOSP 4.4.4
runs smooth.
encountered some problems while directly flashing the kernel, the Wifi didn't work, but after a clean install and flashing userdata.img it worked.
Phone is without a charger since last night and i still have 76% battery with my usage.
toby913 said:
runs smooth.
encountered some problems while directly flashing the kernel, the Wifi didn't work, but after a clean install and flashing userdata.img it worked.
Phone is without a charger since last night and i still have 76% battery with my usage.
Click to expand...
Click to collapse
Yeah battery life is quite good, i'm surprised.
Lost 3% over 7h deep sleep, which is great for a aosp rom with the messy play services
Xperia Z / AOSP 4.4.4 / Zombie
Installed over kitkat(the one you mentioned) , and booted up but soft rebooted after "android starting apps" phase... gonna retry and see if i can get a log.
hussainr said:
Installed over kitkat(the one you mentioned) , and booted up but soft rebooted after "android starting apps" phase... gonna retry and see if i can get a log.
Click to expand...
Click to collapse
No need for a log, it works just fine ?!
Flash rom and gapps, reboot into OS.
Then flash the kernel.
Xperia Z / AOSP 4.4.4 / Zombie
Tommy-Geenexus said:
No need for a log, it works just fine ?!
Flash rom and gapps, reboot into OS.
Then flash the kernel.
Xperia Z / AOSP 4.4.4 / Zombie
Click to expand...
Click to collapse
didn't work , exactly what i did twice but no luck after "starting Apps" i get soft reboot and it just stuck on
boot animation,
Update: worked, after waiting on boot animation for a while , but and error which doesnt let me to interact
with os, com.android.process... stopped. so reverted back to pabx own kernel. any ideas ?
hussainr said:
didn't work , exactly what i did twice but no luck after "starting Apps" i get soft reboot and it just stuck on
boot animation,
Click to expand...
Click to collapse
There should be no "optimizing apps" as it's not kernel related.
Did you clean install latest pabx aosp build?
Xperia Z / AOSP 4.4.4 / Zombie
Tommy-Geenexus said:
There should be no "optimizing apps" as it's not kernel related.
Did you clean install latest pabx aosp build?
Xperia Z / AOSP 4.4.4 / Zombie
Click to expand...
Click to collapse
yes clean install, wiped everything...before and after install, then booted into os installed some apps
after that rebooted into recovery for kernel installation.
hussainr said:
yes clean install, wiped everything...before and after install, then booted into os installed some apps
after that rebooted into recovery for kernel installation.
Click to expand...
Click to collapse
Flash stock boot, rom and userdata.
Then reboot once and flash kernel.
Using it on @pabx AOSP.
Working very well, super smooth and great battery life.
One request, could you also try your hand at making a CM based kernel, we desperately need a battery friendly kernel for XZ.
Thanks a lot.
AW: [Kernel]Zombie(AOSP-4.4)
venky716 said:
Using it on @pabx AOSP.
Working very well, super smooth and great battery life.
One request, could you also try your hand at making a CM based kernel, we desperately need a battery friendly kernel for XZ.
Thanks a lot.
Click to expand...
Click to collapse
I could, yeah.
But:
-Stock CM is sluggish and i don't feel like building a kernel for it
-Thomas' CM is nice, already has a custom kernel included.
Also my time is limited atm, you can contact other devs of f.e. slimkat to adopt some of my changes, which i'll doubt will happen
Had a play with this one.
Not bad at all maybe pull in voltage adjustments?
I tend to cook my own from pabx with much lower voltages.
But this one is pretty decent
Sent from my C6603 using Tapatalk
fards said:
Had a play with this one.
Not bad at all maybe pull in voltage adjustments?
I tend to cook my own from pabx with much lower voltages.
But this one is pretty decent
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
I'm quite unsure if i should lower some voltages.
It may introduce some problems for the unlucky ones having a lower binned chipset, plus makes games laggy.
Probably i'll add the (awesome) voltage control by morfic, as this kernel is intended to be in-line with Trinity.
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