!!! PLEASE READ THIS ENTIRE POST BEFORE PROCEEDING !!!
!!! I AM NOT RESPONSIBLE FOR ANY PROBLEMS THAT OCCUR WHILE INSTALLING/USING THIS !!!
This is kernel for the LG VS980 running stock-based firmware. My preference is a more basic/lean kernel with an emphasis on battery life, reliability and speed. As such, I'm not interested in adding addtional drivers or features. There are plenty of other devs who do a good job with that already.
Basic Features:
Based on VS98024A source
CAF interactive gov that has been tuned for this device
CAF cpu-boost with input boost enabled (currently @ ~1GHz, but can be changed via sysfs)
Tuned ondemand gov (default) that stays true to stock LG
Choice of stock QCom (default) or Showp/Bricked mpdecision
NOTE: If you want to use interactive governor, it should be paired with alternate (showp's) mpdecision or there will be a delay turning the screen on using knock-on. This can be accomplished via sysfs or in an app like trickster by turning off qualcomm's mpdec, hitting the MP-Decision Control button and turning on "enabled" and "scroff_single_core"
Removed unnecessary governors (only interactive, ondemand, performance remain)
Westwood+ (default) TCP congestion control
Row is still default I/O sched
v1.0.0-1.1.1 compiled with linaro tc v4.7.4
Full list of commits available at github
Changelog:
Version 1.1.1:
Showp's mpdec screen off single core default to off
Correct qcom thermal freq for G2
Version 1.1.0:
OIS+ updates from G Pro 2 (including updated fw)
Other commits I found while chasing down the random HDR crash.
Version 1.0.0:
Initial release
How to Install:
Back up your existing kernel using recovery or make sure you have a way to reinstall it on your device already.
Download the appropriate zip below and flash via recovery (TWRP recommended)
Downloads:
LGD Panel (99% of you want this):
xdabbeb's vs980 kk kernel v1.0.0 - MD5: 267531b33cf8668d81d6f5dbf54468a6
xdabbeb's vs980 kk kernel v1.1.0 - MD5: e9ec66ef0d420fd6b798bde6a6b6bb69
xdabbeb's vs980 kk kernel v1.1.1 - MD5: 3a33d10cb6b70ef3ef8ee755192272dc
JDI Panel:
xdabbeb's vs980 kk kernel v1.0.0 - MD5: c375cbd890ace0ee22a6b83f2912ce49
xdabbeb's vs980 kk kernel v1.1.0 - MD5: f85ed58acf0131b8f6470bb2565dae86
xdabbeb's vs980 kk kernel v1.1.1 - MD5: 169b18b5587602c41a64870eb1f994cf
Stock/Unmodified:
stock vs98024a kernel - MD5: c7bb6eff41546a40dfaa7dae0407e5fe
Devs: Feel free to include this in your roms. No need to ask, just give credit in your OP.
XDA:DevDB Information
XDABBEB's VS980 KK Kernel, Kernel for the Verizon LG G2
Contributors
xdabbeb
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 1.1.1
Created 2014-06-04
Last Updated 2014-06-22
reserved
reserved #2
xdabbeb's vs980 kk kernel v1.1.0 - MD5: 6556b6cf3a1592df3ce3b4076012aaec
Hate to ask. But just trying to make sure.
Will this work with your Rom? I saw your comment and was just making sure this kernel went with the 24a as well.
Is the kernel called xdabbeb_vs98024a_kernel_google_gcc.zip the same as this one here called stock?
VZW G2 (VS980)
jesssiii said:
Is the kernel called xdabbeb_vs98024a_kernel_google_gcc.zip the same as this one here called stock?
VZW G2 (VS980)
Click to expand...
Click to collapse
Yes
Sent from my Vs980 running Mahdi Rom
---------- Post added at 05:00 PM ---------- Previous post was at 04:59 PM ----------
barrackOBAMA said:
xdabbeb's vs980 kk kernel v1.1.0 - MD5: 6556b6cf3a1592df3ce3b4076012aaec
Hate to ask. But just trying to make sure.
Will this work with your Rom? I saw your comment and was just making sure this kernel went with the 24a as well.
Click to expand...
Click to collapse
Yes. His ROM is 24a base, so these are 24a base kernels.
Sent from my Vs980 running Mahdi Rom
OFF TOPIC -- I love trailer park boys...
...Continue
Lawlrus said:
Yes
Sent from my Vs980 running Mahdi Rom
---------- Post added at 05:00 PM ---------- Previous post was at 04:59 PM ----------
Yes. His ROM is 24a base, so these are 24a base kernels.
Sent from my Vs980 running Mahdi Rom
Click to expand...
Click to collapse
First boot and interactive is default gov... Op lists ondemand.. And no, I did not have kernel settings to set on boot.
Sent from my VS980 4G using Tapatalk
ffejy462 said:
First boot and interactive is default gov... Op lists ondemand.. And no, I did not have kernel settings to set on boot.
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
If you're using my v1.1.1 rom then I had an init script doing that...which is something that can happen with any rom, really. If you want ondemand you can either switch it via an app (i.e. trickster) or just change the init script.
xdabbeb said:
If you're using my v1.1.1 rom then I had an init script doing that...which is something that can happen with any rom, really. If you want ondemand you can either switch it via an app (i.e. trickster) or just change the init script.
Click to expand...
Click to collapse
I planned on giving both a whirl. Just thought I'd share.
Sent from my Nexus 7
Same kernel(s) as ROM(s)?
@xdabbeb
Maybe this is a dumb question, but if we are already running your ROM, are these newer kernels, or do they coincide with the releases of the ROM?
LTunez said:
@xdabbeb
Maybe this is a dumb question, but if we are already running your ROM, are these newer kernels, or do they coincide with the releases of the ROM?
Click to expand...
Click to collapse
V1.1.0 is newer then the kernel baked into his 1.1.1 rom
Sent from my Vs980 running Xdabbeb's 24a v1.1.1
Both 1.0.0 and 1.1.0 are newer. The only difference between them (per OP) are a number of camera-related commits and I wanted to give people who weren't interested in them an option.
Very much appreciated XDABBEB. You've been an awesome developer and your work is top notch.
on the move..
Flashed the 1.1.0 kernel last night over the latest @xdabbeb ROM. Anyone else notice incredible lag with knock on? Really incredible. I'd tap the screen twice, I'd see the LED light up acknowledging it worked, then there'd be a two second delay before the screen would come on. Knock off worked fine. I restored my backup and the lag was gone. I did nothing to alter any kernel settings - just ran it however it came.
Rodeojones said:
Flashed the 1.1.0 kernel last night over the latest @xdabbeb ROM. Anyone else notice incredible lag with knock on? Really incredible. I'd tap the screen twice, I'd see the LED light up acknowledging it worked, then there'd be a two second delay before the screen would come on. Knock off worked fine. I restored my backup and the lag was gone. I did nothing to alter any kernel settings - just ran it however it came.
Click to expand...
Click to collapse
I had that and then my phone completely locked up while navigating. I'm going to wait until the new ROM release comes out and fresh flash.
Sent from my VS980 4G using Tapatalk
Flashed the 1.1.0 kernel last night, wiped Dalvik and cache, and rebooted...everything seemed fine. Rebooted this morning, and the screen was a garbled mess. It looked almost like white noise (only colored). Managed to reboot again, and the garbled mess was gone, but then I saw some vertical white lines in various places of the screen. Rebooted into recovery, wiped Dalvik and cache, and it seems ok for now, but I wonder what might be going on. Could this having anything to do with what the following thread addresses?
http://forum.xda-developers.com/showpost.php?p=52414185&postcount=122
P.S. Not having the "knock on" lag here...
LTunez said:
Flashed the 1.1.0 kernel last night, wiped Dalvik and cache, and rebooted...everything seemed fine. Rebooted this morning, and the screen was a garbled mess. It looked almost like white noise (only colored). Managed to reboot again, and the garbled mess was gone, but then I saw some vertical white lines in various places of the screen. Rebooted into recovery, wiped Dalvik and cache, and it seems ok for now, but I wonder what might be going on. Could this having anything to do with what the following thread addresses?
http://forum.xda-developers.com/showpost.php?p=52414185&postcount=122
P.S. Not having the "knock on" lag here...
Click to expand...
Click to collapse
I can't say I've seen white lines, but I did flash a font last night and when it went to boot it looked like the lg splash was smeared, it then bootlooped until I went back into recovery and flashed a different font
The white line issue is normally not on our device because most screens are lgd not jdi.
There is a thread in the g2 android development section for a tool that checks your screen type made by bender_007.
You can try that to double check screen type.
Sent from my Vs980 running Xdabbeb's 24a v1.1.1
I unfortunately had that happen this morning. Initially it flashed and booted perfectly last night. This morning I rebooted and got the white lines, my first incident of this. According to the Panel app I do have the lgd panel.
on the move..
Lawlrus said:
I can't say I've seen white lines, but I did flash a font last night and when it went to boot it looked like the lg splash was smeared, it then bootlooped until I went back into recovery and flashed a different font
The white line issue is normally not on our device because most screens are lgd not jdi.
There is a thread in the g2 android development section for a tool that checks your screen type made by bender_007.
You can try that to double check screen type.
Sent from my Vs980 running Xdabbeb's 24a v1.1.1
Click to expand...
Click to collapse
Thanks for the info...the tool shows mine is ldg/lgit.
Don't know if this could affect anything, but the only thing I changed this morning (since flashing the new kernel last night), was to "defrost" (in TiBU), the full version of Swiftkey (because the latest beta expired). So, that's causing the known Gapps crash on boot, but in the past, that crash hasn't seemed to affect performance or anything...hmm...
Related
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
July 24: this is my build with Dorimanx kernel compiled with Linaro 4.9 arm-eabi and the rest compiled with Linaro 4.9 arm-linux-eabi. In short, all facets of this ROM are compiled with Linaro 4.9.
Link here: AOSB_All_Linaro
I use this as my daily driver. Works perfectly so far!
As always, I'm not responsible for any damage or problems you may experience with this ROM
ishyesh said:
This is my compiled version of AOSB 1.3.6 with two different 4.4.2 Kernels: JackpotCalvin's and Dorimanx'
JackpotCalvin:
aosb_kk_1.3.6_vs980.zip
Dorimanx:
aosb_kk_1.3.6_vs980_dorimanx.zip
I haven't had a chance to flash these yet.
As always, I'm not responsible for any damage or problems you may experience with this ROM
Click to expand...
Click to collapse
Where did u find dorimax that can run asop roms? Bout to load and flash...
Sent from my VS980 4G using Tapatalk
kenbrownstone said:
Where did u find dorimax that can run asop roms? Bout to load and flash...
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
Bart from vanir patched it to make it work.
Sent from my Vs980 running Jackpotclavins Cm11 4.4.4
Flashed the JC version. So far so good. Still loading up apps.
@ishyesh
Thanks again for the builds. Still haven't flashed your jackpotclavin build, I downloaded the dorimanx version, I'll give that a flash first.
Edit, nvm, I forgot Mahdi uses n5 sounds versus lg
Sent from my Vs980 running Jackpotclavins Cm11 4.4.4
Running dorimanx version and it is running great. Thanks!
Lawlrus said:
@ishyesh
Thanks again for the builds. Still haven't flashed your jackpotclavin build, I downloaded the dorimanx version, I'll give that a flash first.
Edit, nvm, I forgot Mahdi uses n5 sounds versus lg
Sent from my Vs980 running Jackpotclavins Cm11 4.4.4
Click to expand...
Click to collapse
So far the JC build is great. I forget how much I miss AOSP. I'm loving the hover and having Halo again. I installed V4A and the volume is great.
After running for awhile, I wasn't able to get the ROM to sleep at all. Wakelock detector really didn't show anything and neither did better battery stats.
fordmanck said:
So far the JC build is great. I forget how much I miss AOSP. I'm loving the hover and having Halo again. I installed V4A and the volume is great.
After running for awhile, I wasn't able to get the ROM to sleep at all. Wakelock detector really didn't show anything and neither did better battery stats.
Click to expand...
Click to collapse
I can confirm on the dorimanx build, that the same thing is keeping it from sleeping as well.
Seems like a lot of cm base Roms are having the issue. Gotta love cm butchering commits.
Sent from my Vs980 running Jackpotclavins Cm11 4.4.4
Do core 3 and 4 not respond to any changes in CPU frequency governors? The best way to test would be to try and change the governor from conservative to performance. What should happen is that core 3 and 4 should be going full blast on the performance governor but not the conservative governor.
Thanks!
Lawlrus said:
I can confirm on the dorimanx build, that the same thing is keeping it from sleeping as well.
Seems like a lot of cm base Roms are having the issue. Gotta love cm butchering commits.
Sent from my Vs980 running Jackpotclavins Cm11 4.4.4
Click to expand...
Click to collapse
ishyesh said:
Do core 3 and 4 not respond to any changes in CPU frequency governors? The best way to test would be to try and change the governor from conservative to performance. What should happen is that core 3 and 4 should be going full blast on the performance governor but not the conservative governor.
Thanks!
Click to expand...
Click to collapse
I actually tried both builds and it didn't sleep on either. I won't have time tonight but I'll restore tomorrow and give it a whirl.
Sent from my VS980 4G using Tapatalk
ishyesh said:
Do core 3 and 4 not respond to any changes in CPU frequency governors? The best way to test would be to try and change the governor from conservative to performance. What should happen is that core 3 and 4 should be going full blast on the performance governor but not the conservative governor.
Thanks!
Click to expand...
Click to collapse
Seems like cm pushed a fix for the sleep issue, at least on crDroid. I had an issue with it not sleeping, then after the build today, no issues at all.
Sent from my Vs980 running crDroid 4.4.4
Lawlrus said:
Seems like cm pushed a fix for the sleep issue, at least on crDroid. I had an issue with it not sleeping, then after the build today, no issues at all.
Sent from my Vs980 running crDroid 4.4.4
Click to expand...
Click to collapse
Good to know. I'll flash this over when there's a new build. I'd prefer the JC kernel if possible just because I won't have to redo anything on my backup. I've commenced operation "Drink Beer" already so it won't happen today. Happy 4th to all!
Sent from my VS980 4G using Tapatalk
Thanks for the update! I'll hunt down the commit and compile soon! Enjoy July 4th =)
I'm running though some trouble with SystemUI repetitive force closing on my latest AOSB builds...I have a hard time tracing what's wrong. Whenever I get a build running properly, I'll post it right away!
New builds!
Alright everyone, I've posted new builds for the vs980 with the Dorimanx and the Render kernels. I haven't had a chance to test these out yet, my phone is getting back from warranty replacement.
Also, you'll notice there are d800 builds present. I'm not going to start a thread in the LG G2 AT&T forums because AOSB officially supports d800. However, please feel free to use these. I haven't yet tested out the d800 builds either.
EDIT: I haven't seen any changes on the Beanstalk github page, so I'm going to focus my efforts on compiling AOSB for now.
ishyesh said:
Alright everyone, I've posted new builds for the vs980 with the Dorimanx and the Render kernels. I haven't had a chance to test these out yet, my phone is getting back from warranty replacement.
Also, you'll notice there are d800 builds present. I'm not going to start a thread in the LG G2 AT&T forums because AOSB officially supports d800. However, please feel free to use these. I haven't yet tested out the d800 builds either.
EDIT: I haven't seen any changes on the Beanstalk github page, so I'm going to focus my efforts on compiling AOSB for now.
Click to expand...
Click to collapse
I'll download and give them a whirl tomorrow. Have you read anything about mms issues? I know I was seeing it and I've read others were too.
Sent from my VS980 4G using Tapatalk
I downloaded and installed the render version, constant system.ui errors on the set up screen.
mjones73 said:
I downloaded and installed the render version, constant system.ui errors on the set up screen.
Click to expand...
Click to collapse
Guess i'll be holding off then. Lol
Thanks
Hi all, new build is up which is compiled with ALL linaro 4.9 toolchains. I have a vs980 in hands now, and have tested it out. ROM works flawlessly. Kernel, even more so =D
ishyesh said:
Hi all, new build is up which is compiled with ALL linaro 4.9 toolchains. I have a vs980 in hands now, and have tested it out. ROM works flawlessly. Kernel, even more so =D
Click to expand...
Click to collapse
Have you tried booting in art? Can't seem to get it working for me after removing xposed and app settinga
Sent from my LG-VS980
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
RealONE Kernel for Moto X 2014!
Only CM or based CM versions like RR,NX...
And only Android M too
Features:
Compiled with UBERTC 4.9.4
Optimized Entropy
FauxSound
Power Suspend
Improved accuracy of MultiCore
CRC disabled by default( 30% extra perfomance on I/O)
Swappiness reduced to 15%
UnderClock CPU (268 Mhz)
Activated Power Eficcient Worqueues
#Governors:
ZZmove
Intellidemand
Smartmax Extreme Power Saver (eps)
Intelliactive
#Hotplugins:
MSM_Hotplug
Intelliplug
Alucard
MSM MP Decision
#I/O Schreduler:
Added Zen
All credits goes to Michel Borges
Thanks Leonardo Augusto
Thanks Faux123
Source of the Kernel on github:
https://github.com/RealOne-Kernel/RealOne-Victara-Kernel
could you give instructions on how to flash a kernel in our device?
marquesini said:
could you give instructions on how to flash a kernel in our device?
Click to expand...
Click to collapse
This is not the place for that.
jlink38 said:
This is not the place for that.
Click to expand...
Click to collapse
oh, ok.
then I dunno, pm me an external link for that ? i really want to try change the kernel, but don't want to mess up the device, i could google it but preffer a recommendation of a tutorial by someone who understands more about it than i dunno.
anyway, thanks.
Hello, your kernel is very good, very fluid and good battery consumption in CM13, it would be possible in the future to add support KCAL?, can change the saturation, contrast, etc., thank you for your work.
[DEV][PATCH] KCAL - Advanced color control for Qualcomm MDSS 8x10/8x26/8974/8084/8939
Great kernel. Has improved battery life quite a bit !
Thanks!! Testing on CM13... Looks good
Good battery consumption.
Sent from my XT1095 using Tapatalk
Great kernel so far, thanks for making a custom kernel for 6.0, I've been waiting for one.
Would it be possible for you to add support for DriveDroid to your kernel?
http://forum.xda-developers.com/showthread.php?t=2196707
https://play.google.com/store/apps/details?id=com.softwarebakery.drivedroid&hl=en
Thxx , give me more feedbackk ! And I'll take a look at suggestions at the weekend guys !!
Can't wait to see what this can do..bout to flash now!!!
some people say they are taking random reboots .. anyone had ? maybe a log for me ?
MichelBorgess said:
some people say they are taking random reboots .. anyone had ? maybe a log for me ?
Click to expand...
Click to collapse
Yes i had that issue, but i reflashed cm, I'll retry tomorrow and get you some logs (hopefully i have time, I'm doing my finals now...).
MichelBorgess said:
some people say they are taking random reboots .. anyone had ? maybe a log for me ?
Click to expand...
Click to collapse
I'll try.its happened a few times to me
---------- Post added at 08:47 AM ---------- Previous post was at 08:39 AM ----------
Where can I post my logcat?
http://pastebin.com/ try this
Your kernel its a dream hahahaha I was waiting for a kernel with fauxsound since I've bought this phone. So, first of all, thank you very much for your kernel and we appreciate your work and your time spent with this kernel. But lets get to the facts:
1) In RR 5.6.0 your kernel cause bootloop;
2) In CM13 (specifically 2015-12-12 build) I had a lot of random reboots and the sound (specifically Play Music and Deezer) sometimes was cracking or just not played;
3) In CrDroid I had the same thing in CM13 but the rom has some serious bugs, so we don't count it;
4) In Nexus Experience 10.0.4 I just had ONE random reboot (take note: the first boot, so lets blame the instability of the rom) and, since then, my phone is working completely perfect.
5) With kernel auditor all of my preferences are saved and sticked after a reboot (in Nexus Experience 10.0.4)
Note: All of the Roms was fresh installed, wiped everything (including internal storage) then installed ROM->GAPPS (NX GApps in Nexus Experience and OpenGApps in the other roms)->KERNEL
Maybe with some work in your kernel and in the newer roms, this phone will gain some fresh air!
Thank you again!
Ps.: not an american guy, so please, I'm sorry for any english mistake
victor19 said:
Your kernel its a dream hahahaha I was waiting for a kernel with fauxsound since I've bought this phone. So, first of all, thank you very much for your kernel and we appreciate your work and your time spent with this kernel. But lets get to the facts:
1) In RR 5.6.0 your kernel cause bootloop;
2) In CM13 (specifically 2015-12-12 build) I had a lot of random reboots and the sound (specifically Play Music and Deezer) sometimes was cracking or just not played;
3) In CrDroid I had the same thing in CM13 but the rom has some serious bugs, so we don't count it;
4) In Nexus Experience 10.0.4 I just had ONE random reboot (take note: the first boot, so lets blame the instability of the rom) and, since then, my phone is working completely perfect.
5) With kernel auditor all of my preferences are saved and sticked after a reboot (in Nexus Experience 10.0.4)
Note: All of the Roms was fresh installed, wiped everything (including internal storage) then installed ROM->GAPPS (NX GApps in Nexus Experience and OpenGApps in the other roms)->KERNEL
Maybe with some work in your kernel and in the newer roms, this phone will gain some fresh air!
Thank you again!
fix in next build
Click to expand...
Click to collapse
Yo guyss ! I redid the kernel, and apparently restarts stopped .. is still simpler, more 'll keep updating
zzmoove
intelliplug
IO Zen
https://www.androidfilehost.com/?fid=24340319927533603
I don't understand this thread. The OP has a different username the one above who has released v2? And why hasn't this been moved to 'original development'?
floepie said:
I don't understand this thread. The OP has a different username the one above who has released v2? And why hasn't this been moved to 'original development'?
Click to expand...
Click to collapse
I just asked for Vinicius post for me , since I had not yet allowed to post in section ...