After being a long time lurker here in XDA and having successfully fulfilled some requests on another thread, I thought I'd try to give something to the great community here.
You probably remember Ivan's kernels that provided the community with a version of intersectRaven's Hybrid AVS with 1113MHz overclocking. Unfortunately it looks like Ivan been very busy and is unable to update his kernels. So I have provided recent updates of intersectRaven's truly awesome kernels that includes the 1113MHz overclock for you all to enjoy. (I see this request a lot so maybe now intersectRaven won't be bothered by it again )
I absolutely take no creative credit in making these kernels as all I have done is used the open source code on intersectRaven's github and compiled it. The real credit goes to all the other coders here in this forum (cyan, pershoot, and especially intersectRaven).
When time permits, I'll try to update these kernels when improvements and/or bug fixes are made but I realistically only see myself updating these once or twice a week.
I'm open to requests (like no audio boost) and such. Just let me know the one kernel you want modified and if its within my ability, I'll make one for you when time permits. I have not yet made a super all-in-one compiling script, so it would take me far too long to make a requested modification on all versions. Edit: Due to having virtually no free time, I don't think I can get fulfill requests in a timely manner... I'll try but I can't promise it. So sorry everyone -_-;
If you have the time and the will, I highly suggest you learn how to compile for yourself as I find it pretty fun and rewarding to make something for yourself. Guides and instructions can be found throughout the XDA forum and also on Cyanogen's wiki.
Before updating with these kernels, all I ask is that you make a nandroid backup in case something goes wrong.
Q & A:
-What's the difference between CFS and BFS?
See this short post for the difference between Completely Fair Scheduler and Brain F*** Scheduler. In summery, CFS is better for multitasking, BFS is better for user interactions (keyboard, homescreen swiping, etc).
-What's the difference between SVS and AVS?
Static Voltage Scaling will change the voltage based on a set table created by the kernel maker. Example: At a certain speed, say 245MHz, 925mV is feed into the CPU. At 998MHz, 1225mV is used.
Adaptive Voltage Scaling will change the voltage depending on temperature and CPU needs. Personally, AVS is running rock solid for me but I can't say for sure if it will be for everyone so SVS kernels will continue to be made available.
-What is this "No Audio Boost Version"?
Many of the custom kernels posted in this forum and the kernels used by default in the CM6 roms have this feature where it increases the loudness of the speakers during calls. Its been reported that some bluetooth headsets are overly sensitive to the increased loudness and some have reported that it distorts the audio quality even though volume has been lowered by the user. Due to an overwhelming request to make a kernel without this feature, I have included a separate set with each release that does not boost the volume.
-Can you make a higher overclock version of your kernel?
I was really against this because when I first tried to do this, my phone got really hot. But the requests kept on coming so I revisted this and possibly discovered a way to keep the temperature under control by limiting the max voltage to 1300mV. You'll find a 1190MHz version of my kernel here (Mirror Link).. Most users should be able to handle 1152MHz without any problems but some won't on 1190MHz. You'll know when your CPU can't handle a certain speed if you start to experience a sudden decrease in performance, lag, force closes, and spontaneous reboots. This won't be alievated unless more voltage is feed to the CPU but I'm not comfortable going beyond 1300mV. Now before you try these kernels out I gotta say this. I am not responsible if these kernels result in damaging your phone. Its purely for testing purposes and I really dont recommend using it as your everyday use kernel. If you do continue to use it, you should limit the max to 1113MHz or better yet 1075MHz (see previous question for the reason) if you care about battery life.
-I'm getting a black screen whenever I launch the camera app. Why? (720p related question)
The latest kernels with the 720p code only works with roms that has the 720p stock camera app and now the HTC camera app on Enomther's [ROM] as of 8/10/10. The latest cm6 nightly that has the 720p camera app as well as a few other roms out there that are based on cm6. You can try flashing charnsingh_online zip that contains the updated camera app if you don't want to use the nightly but I don't know for sure if his camera app is compatible with roms under RC2. Another alternative is to send in a request for a custom kernel and I'll make one for you without the 720p code.
2.6.38 kernels:
(Tested on Cyanogenmod 7 Nightlies)
Grab the kernels here: Mediafire
-Changes since 090311
-Set default sleep ideal freq to 128mhz for smartassV2 governor
-Bug fix for 1190MHz kernels, properly set max voltage to 1325mV
-Compiled HAVS 1190MHz kernels for those phone that can handle it
-Changes since 062411
Rebase source from IntersectRaven's Github
Highlights include:
-msm: Add support for voice call recording
-PM: Back off suspend if repeated attempts fail
-lib/sha1: use the git implementation of SHA-1
-arm: remove “optimized” SHA1 routines
-Fix AVS thread not being started.
-Added erasmux’s Smartass governor Version 2
-Changes since 062311
-Fixed ext4 partition support on sdcard.
-Changes since 052711
-Rebase to kernel version 2.6.38.8 from IntersectRaven's Github, with it 2 new governors (InteractiveX and SavageZen)
-Changes since 052611
-Rebased kernel source from intersectRaven's Github With it comes the smartass governor (default set to ondemand because I like it better)
-Switched to Tiny Preempt RCU with RCU boost (To match with Cyanogenmod stock kernel)
-Revert WiFi souce code used in previous release. (Didn't want to take a chance in WiFi not working for some.)
-Changes since 042111
-Rebased kernel source from intersectRaven’s Github With it comes the smartass governor (default set to ondemand because I like it better)
-Switched to Tiny Preempt RCU with RCU boost (To match with Cyanogenmod stock kernel)
-Revert WiFi souce code used in previous release. (Didn’t want to take a chance in WiFi not working for some.)
-Changes since 040911
-Bug fixes relating to USB file transfer speeds and addressed probable cause of WiFi problems for some.
____________________________________________________
If you want, you can buy me a drink (I like orange juice)
Have these kernels been tried and tested? Does the following work:
- Youtube
- Camcorder
- Googles
- Flash
- Unmounting sd card
- Wifi locations
and can you tell us more about the battery life by using this kernel?
p.s. Thanks for posting this btw...
- Youtube Works
- Camcorder works
- Flash works
- sd card problem persists on the .34
- wifi works
EDIT:
I LOVE this kernel! THX wildmonkey ^^
i testet the .34 on both 2.2 and 2.1.... works so far!
RinTinTigger said:
- Youtube Works
- Camcorder works
- Flash works
- sd card problem persists on the .34
- wifi works
Click to expand...
Click to collapse
Thats gr8...what about battery life? how do yo fare by using this kernel?
nazrin313 said:
Thats gr8...what about battery life? how do yo fare by using this kernel?
Click to expand...
Click to collapse
Well....i like 800mV UV and OC, giving me the best balance between battery life and speed.
couldnt do an excact test on the time, but it lasts enough for my usage ^^
nazrin313 said:
Thats gr8...what about battery life? how do yo fare by using this kernel?
Click to expand...
Click to collapse
Speaking for myself, I've been averaging 1-2% on standby. I can't tell you what I get at the end of the day because I usually plug my phone in the charger when I'm in the car...
RinTinTigger said:
- Youtube Works
- Camcorder works
- Flash works
- sd card problem persists on the .34
- wifi works
EDIT:
I LOVE this kernel! THX wildmonkey ^^
i testet the .34 on both 2.2 and 2.1.... works so far!
Click to expand...
Click to collapse
Glad you like it! You know it was partly you that made me want to start this thread.
great! i am really looking forward to it!
wildmonks said:
Speaking for myself, I've been averaging 1-2% on standby. I can't tell you what I get at the end of the day because I usually plug my phone in the charger when I'm in the car...
Glad you like it! You know it was partly you that made me want to start this thread.
Click to expand...
Click to collapse
"partly"
^^
xD
everything including goggles seems working on 800 bfs.. 41 linpacks.. cool
That was my result with linpack and this kernel!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
forgot to setcpu doh
44.738 mflops
upd.. and bootloop =)
just got my nexus one so you could say i'm kinda new to this^^
just wondering what the difference between CFS and BFS kernels are? and what are the pros and cons with 800 / 925 mV kernels?
i am running rooted stock froyo atm, so all i need to do is install a .34 kernel through recovory if i am right? do kernel installs requier a wipe?
thx
wildmonks said:
I'm open to requests (like no audio boost) and such. Just let me know the one kernel you want modified and if its within my ability, I'll make one for you when time permits. I have not yet made a super all-in-one compiling script, so it would take me far too long to make a requested modification on all versions.
Click to expand...
Click to collapse
I am running CM5.0.7.1 and I would love to have a kernel that did not include the audio hack, I have a feeling that everyone must be deaf because this thing sounds real bad at higher volumes ever since the audio hack was implemented. I get so much distortion in-calls that I have to turn the volume down to a level that negates any audio boost - so what is the point?
So.. yeah, if you are taking specific requests:
1. Stock speeds (or OC if it has to be, I can control that).
2. 925mV.
3. CFS (though I haven't messed with BFS since CM4.xx days on my G1, I still think it has a long way to go).
4. No audio hack.
Seems perfect to me.
mardox said:
just got my nexus one so you could say i'm kinda new to this^^
just wondering what the difference between CFS and BFS kernels are? and what are the pros and cons with 800 / 925 mV kernels?
i am running rooted stock froyo atm, so all i need to do is install a .34 kernel through recovory if i am right? do kernel installs requier a wipe?
thx
Click to expand...
Click to collapse
CFS: http://de.wikipedia.org/wiki/Completely_Fair_Scheduler
BFS: http://en.wikipedia.org/wiki/Brain_Fuck_Scheduler
Just flashed it...camcorder, video playback, youtube and WIFI works as normal.
Brilliant kernel in terms of performance, as speedy as preshoots...
Linpack scores varies from 40-44 mflops
Quadrant score is a hefty 1495...
Now, im gonna test the battery life tonight...
nazrin313 said:
Just flashed it...camcorder, video playback, youtube and WIFI works as normal.
Brilliant kernel in terms of performance, as speedy as preshoots...
Linpack scores varies from 40-44 mflops
Quadrant score is a hefty 1495...
Now, im gonna test the battery life tonight...
Click to expand...
Click to collapse
when you say "test battery life tonight" does that mean you are going to leave the phone over night and see how much battery is consumed in standby or are you actually going to use the device?
hondaguy said:
when you say "test battery life tonight" does that mean you are going to leave the phone over night and see how much battery is consumed in standby or are you actually going to use the device?
Click to expand...
Click to collapse
Im gonna charge it to 100% then leave it whilst I sleep...Tommorow im gonna im actually gonna use it
from my own usage since installing Froyo here is what I have found from testing various kernels (Unplugged at 7am)
- Froyo Kernel: Lasted till 10pm ish (Display on > 3 hrs)
- Preshoot 33.4 kernel: lasted me till 3pm ish (Display on approx 2 hrs)
P.s:
Tested on quadrant again and I got a whopping 1668...thats the highest ive seen my phone do...
daveid said:
I am running CM5.0.7.1 and I would love to have a kernel that did not include the audio hack, I have a feeling that everyone must be deaf because this thing sounds real bad at higher volumes ever since the audio hack was implemented. I get so much distortion in-calls that I have to turn the volume down to a level that negates any audio boost - so what is the point?
So.. yeah, if you are taking specific requests:
1. Stock speeds (or OC if it has to be, I can control that).
2. 925mV.
3. CFS (though I haven't messed with BFS since CM4.xx days on my G1, I still think it has a long way to go).
4. No audio hack.
Seems perfect to me.
Click to expand...
Click to collapse
Here yah go:
2.6.33.5_AVS-925mV_CFS_NoAudBoost_v2_060210.zip
I think all those years of listening to loud music has affected my hearing so I need the audio boost
I tested it out and it seems audio levels are back to standard (noticeably lower) but let me know if it doesn't work or if there are any other problems with it.
Update: Doh! I found a bug that I introduced into this no audio boost version. Seems that I broke music playback O_O. I fixed it and updated the above link. Sorry to those that download the other version -_- . . .
Audioboost is so necessary, i cant use any kernels without!
RinTinTigger said:
That was my result with linpack and this kernel!
Click to expand...
Click to collapse
t0ol said:
forgot to setcpu doh
44.738 mflops
upd.. and bootloop =)
Click to expand...
Click to collapse
nazrin313 said:
Tested on quadrant again and I got a whopping 1668...thats the highest ive seen my phone do...
Click to expand...
Click to collapse
Interesting observation you all are getting. Must be the combination of BFS and OC? But I would not be surprised if battery life suffers a little... But very cool nonetheless
Related
AOSP Kernels for HTC's 8x50, 7x30, and 8x60 Devices
Also available for the Motorola Xoom
Tiamat kernels are designed for use on all ROMs that are built from the AOSP source code. This includes ROMs built from MIUI, CyanogenMod, and others.
Tiamat receives no support for use with ROMs based on HTC's Sense - use at your own risk.
Click to expand...
Click to collapse
Tiamat Kernels
You can find full details about Tiamat Kernels at our website. The site is up and running and serves as a more centralized location to get updates, downloads, and changelogs for all Tiamat Kernels. There is no forum or Registration, it’s just a more convenient way to keep things organized as we work to add support for more devices.
Click to expand...
Click to collapse
Support
Join the Tiamat Kernel developers on IRC at irc.freenode.net, #tiamat. Support and questions are generally handled faster there than the forums. You can easily join via webchat here.
Click to expand...
Click to collapse
Special Thanks to:
toastcfh, slayher and the CyanogenMod team for the base kernels and everything else they do for the Android community
bcnice20 for generally being awesome
TeamWin for also generally being awesome
netarchy, chad0989, cuviper, and invisiblek for some great code
intersectRaven and redstar3894 for the Mjolnir compiler
JasonK75 for updating threads
Click to expand...
Click to collapse
Quick Links
Click to expand...
Click to collapse
8x50 Changelog
8x60 Changelog
7x30 Changelog
Downloads
FAQ
Source Code
reserved for later
This kernel has been around for the Inc and the Evo. Now I'm bringing it to the N1 and the Desire!!
Great stuff, always nice to have more kernel choices
MOD : Can you post only Nexus One kernel on your post please (more readable)
Had been having some wifi issues this past week using cm7 nightly along with various kernels. Wifi was frequently dropping or just very slow. Spent most of Sunday screwing with my home network which seems stable now. I think comcast must have been doing something. however, my phone wifi was still poor. installed this kernel last night and so far phone is performing as it should on wifi. the difference was immediate. not sure whats going on. cant comment on battery life yet, but it's looking very good through this mornings use. Thank you!
allofusjw said:
Had been having some wifi issues this past week using cm7 nightly along with various kernels. Wifi was frequently dropping or just very slow. Spent most of Sunday screwing with my home network which seems stable now. I think comcast must have been doing something. however, my phone wifi was still poor. installed this kernel last night and so far phone is performing as it should on wifi. the difference was immediate. not sure whats going on. cant comment on battery life yet, but it's looking very good through this mornings use. Thank you!
Click to expand...
Click to collapse
I'm glad it's working for you, but that is strange... The only change I make to wifi from CM is undervolting it. And now that I think about it, I may have forgotten to bring that tweak over to the n1 and desire...
Can you summarize how your kernel differs from the others (CM, pershoot, wildmonks, redstar).
mr_raider said:
Can you summarize how your kernel differs from the others (CM, pershoot, wildmonks, redstar).
Click to expand...
Click to collapse
Versus the main CM kernel, this has unrestricted overclocking, HAVS, smartass, undervotling, sysfs interface and several other tweaks/improvements. I don't have a N1 and honestly dont know anything about the other kernels out there for it. The kernel started on the Inc and Evo, mostly around MIUI, and I was asked by a few people to bring it over to the N1 and Desire, so I figured I would post it up for everyone.
Hi all,
Been running this since 0800 this morning (its now 1800) no problems at all.
Can't say its faster or better on the battery for sure but its certainly no worse than CM stock.
Whats the smartass govenor? Just the same as on demand as it seems to replace it?
Oh, just one thing, although it has the option (in SetCPU) to go down to 128mhz, I've not seen it go lower than 245mhz which makes me wonder if its clocking down to 128 with the screen off.
Anyone else?
bryanchapman9999 said:
Hi all,
Been running this since 0800 this morning (its now 1800) no problems at all.
Can't say its faster or better on the battery for sure but its certainly no worse than CM stock.
Whats the smartass govenor? Just the same as on demand as it seems to replace it?
Oh, just one thing, although it has the option (in SetCPU) to go down to 128mhz, I've not seen it go lower than 245mhz which makes me wonder if its clocking down to 128 with the screen off.
Anyone else?
Click to expand...
Click to collapse
The on demand governor was removed to force the default to smartass (the default is usually set to on demand by the ramdisk and is not affected by setting the default in the kenrel), but the two are not similar. Smartass was built off the interactive governor.
As for the 128Mhz floor - that is something finicky about the smartass governor. It should drop to 128 on any other governor though.
Smartass Governor shows real potential...thanks for this!
what about the wonk?
From what I gather the wonk is due to something in CM7 kernel. I also noticed that it is absent from stock 2.3.3 and also absent from AOSP builds.
Has anyone tried CM7 with this kernel?
thanks for the N1 kernel.
I'll try ASAP.
I will try this kernel now, thanks for posting. New kernel cooks are always welcomed.
After about 18 hrs on this kernel, the results are pleasing.
Extremely stable on the Smartass Governor, which is surprising because I've had friends compile me kernels incorporating this governor, and the end result = unusable.
Battery life seems fantastic so far.
Clocked 128-998. No profiles.
Thank you again for this kernel.
Results on N1
I have been running this kernel for 24hrs at 128/1228 and it's been running great with smartass selected on my AT&T N1. I tried going even higher than 1228 but that causes it to crash immediately (I'm surprised it can even handle 1228.) Linpack is a little low at 23 compared to other kernels that can get up to 40. Quadrant also comes up behind at only 1051.
tried going at the highest setting & it crashed my N1 , BACK TO RESDTAR'S kernel .
Been using the kernel for a few hours, Kernel seems stable but definatly doesnt feel snappy.
phewizzo said:
Been using the kernel for a few hours, Kernel seems stable but definatly doesnt feel snappy.
Click to expand...
Click to collapse
same here, got some freeze
btw oc at 1267 without any crash
image sources: mik_os' profile and franciscofranco's dev thread
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
True, there are (tho outdated) threads like [Q] CM7 + Franco's Kernel??? and [Q] MIk + Franco but now this is NOT ONLY A THREAD FOR QUESTIONS.
As I've seen many people asking questions about this combination in one of the ROM/Kernel thread and they can't get answers from experienced users of this combination,
(some in mik's thread dont use franco, some in franco uses devoid only)......
QUESTIONS ARE NOW OPEN!
But make sure yourself is not a noob! if you are, try [READ FIRST] [REF] Dictionary for n00b - What is.../What does ...mean? first
Introduction
Many users have found that this combination is totally cool right?
however there may still be bugs in this combination
because mik_os' ROM is Android 2.3.x Gingerbread
and franco.Kernel is made for Android 2.2 Froyo <<< Yay BFS version for 2.3 is out XD
If you want to ask questions based only on mik_os' rom?
Here: [discussion]LG P500 mik_os's port of cyanogenMOD7, problems, questions, and answers.
If you want to ask questions based only on franco.Kernel?
Here: [Q] franco kernel problem
If you want to ask questions about the fantastic combination?
If you absolutely want to flash and try yourselves, but sometimes would prefer searching in XDA in advance and see what the others' results are?
or if you have tried this combination out, and would like to share to others so they can take your results as references before flashing?
Here, this thread, is what you want.
Btw, feel free to vote the poll at the top
Their Development Threads
[DEV][UNOFFICIAL][ROM][stable:version/testing:version] CyanogenMod version
[KERNEL][date of update] franco.Kernel |version|VR|CFS|SLQB|SMARTASS|TinyRCU|ZRAM|GPU+|. 39 |
Main Purpose of This Thread
- To share our results after flashing the combination
- When they update, we update!
- Confirm it if a bug has solved in later versions!!
- Questions are now open! Just make sure you've searched around and not wasting time here
- Only share your results after you confirm the errors are bugs of the combination instead of your own problem
- Also, we can directly answer the problem of a result if you know it is just human error instead of a bug BETWEEN THE COMBINATION!
- All other discussions are totally welcome!
Complete Results Sharing Form (if needed)
Italic words as examples
Bold words for you to copy
ROM version: 6.5.2
Kernel version: v15.1
App2SD: Darktremor 2.7.5.3-beta04
Data2SD: None
Additional information: ZRAM enabled
Stable Overclocking: 600/806 InteractiveX
Benchmark scores:
Quadrant 2000
Neocore 60fps
Error(s) or bug(s) discovered:
Bluetooth doesnt work
Call waiting disabled
Any suggestions for this thread are totally welcome!!
Hope this can help other users which are new to this combination but get tempted by the great performance comments everywhere
Remember, only share your results after you have tested the combination for at least 12 hours, thanks!
Myself as the first
ROM version: 6.5.2
Kernel version: v15.0
App2SD: Darktremor 2.7.5.2-1
Data2SD: None
Additional information: ZRAM enabled
Stable Overclocking: 122/729 SavagedZen
Benchmark scores: (if you want to share)
Quadrant 1534
Error(s) or bug(s) discovered: (if there is)
Random shutdowns/reboots!
with the latest v16 franco's kernel cmparts error on boot is gone
overclock settings are applied correctly, no need of setcpu anymore.
well done! there's still just the battery temperature bug though
vizzze said:
with the latest v16 franco's kernel cmparts error on boot is gone
Click to expand...
Click to collapse
what do you mean by cmparts error on boot?
You mean, there wont be random shutdowns when im using the phone?
there was, when it is v15
Miasmic said:
what do you mean by cmparts error on boot?
You mean, there wont be random shutdowns when im using the phone?
there was, when it is v15
Click to expand...
Click to collapse
never happened to me the shutdown problem... i mean the cmparts process that couldn't start on andoid boot because of franco's kernel
vizzze said:
never happened to me the shutdown problem... i mean the cmparts process that couldn't start on andoid boot because of franco's kernel
Click to expand...
Click to collapse
oooh would appreciate a lot if someone can tell me whether the shutdown problem has solved in v16
anyway thanks
for me
Cm7 6.5.2
kernel v15.1
zram enabled
oc 480/768 smartass
neocore 59.9
quadrant 1638
bug, kernelpanic with oc at 806 Mhz
indian65 said:
for me
Cm7 6.5.2
kernel v15.1
zram enabled
oc 480/768 smartass
neocore 59.9
quadrant 1638
bug, kernelpanic with oc at 806 Mhz
Click to expand...
Click to collapse
cool!! there are no random shutdowns in 15.1? did u experience v15.0 before
Sent from my LG-P500 using XDA Premium App
No random shutdowns in v16 ...
I'm on miks cm 6.5.2 with Franco kernel + zram and 320/748 oc on interactiivex.
Sent from my LG-P500 using XDA Premium App
I just flashed this kernel and zram and the quadrant scores at 806 mhz are almost the same scores I get with the original CM 7 kernel. Performance wise I think in games and just regular use it feels a lot more smoother. I just don't see it in the scores.
Heheheh Im now flashing the combination of miks 6.5.4 and franco's v16 BFS version
report to u guys 2 days later!
Cyanogenmod 7 by mik_os 6.5.4-stable with Franco's Kernel v16fix @729/480 smartass governor, no App2sd nor Data2sd due to my ****ty stock SD...
Linpack >= 8.8
Neocore (w/ audio): 57.3
Neocore (no audio): 60.5
Quadrant: 1486
6.5.4 Stable + v16.0 BFS Results
Ok so hey guys after using the newest combination for about a day ive come up with a detailed report for u
ROM version
6.5.4 Stable
Kernel version
v16.0 BFS for andy and mik
App2SD
Darktremor 2.7.5.2-1
Data2SD
None
Additional information
ZRAM enabled
Stable Overclocking
122/710 SavagedZen
Benchmark scores
Quadrant ~1400
(idk may be i got too many apps lol around 400)
LIST OF BUGS OR UNUSUAL ISSUES DISCOVERED AND COMMENTS
*"pure" = mik's rom + mik's kernel (the one attached with the rom)
- USB debugging icon is missing even it has solved in 6.5.4
- (already found this in older versions of the combination but didnt post) the keyboard sometimes doesnt pop out when necessary and wastes one more click (for me, App Protector Pro password insert page)
- My phone was stable @748 max using this combination but yesterday it panics at 729 and i was like =.=
- Performance boost is not as significant as when i was at 6.5.3 + v15.0 + zram
- (very disappointing) The CPU is not sensitive/reactive as before, even less reactive than pure 6.5.3, so i had to increase the minimum from 122 to 480 (I tested this with SeePU on at 0.5 second interval and scrolling homescreens, launching benchmarks etc.)
- Yea the camera crashes when restoring defaults in recording mode as stated in mik's dev thread
- The phone's temperature is average 39 degree vs pure's 33 degree
- Temperature displays incorrectly (39 degree as 3.9 degree) vs correctly in pure
CONCLUSION
lol mainly because of the insignificant performances boost even zram is on, im back to mik's pure now
good luck to u all and hope these help
Miasmic said:
Ok so hey guys after using the newest combination for about a day ive come up with a detailed report for u
ROM version
6.5.4 Stable
Kernel version
v16.0 BFS for andy and mik
App2SD
Darktremor 2.7.5.2-1
Data2SD
None
Additional information
ZRAM enabled
Stable Overclocking
122/710 SavagedZen
Benchmark scores
Quadrant ~1400
(idk may be i got too many apps lol around 400)
LIST OF BUGS OR UNUSUAL ISSUES DISCOVERED AND COMMENTS
*"pure" = mik's rom + mik's kernel (the one attached with the rom)
- USB debugging icon is missing even it has solved in 6.5.4
- (already found this in older versions of the combination but didnt post) the keyboard sometimes doesnt pop out when necessary and wastes one more click (for me, App Protector Pro password insert page)
- My phone was stable @748 max using this combination but yesterday it panics at 729 and i was like =.=
- Performance boost is not as significant as when i was at 6.5.3 + v15.0 + zram
- (very disappointing) The CPU is not sensitive/reactive as before, even less reactive than pure 6.5.3, so i had to increase the minimum from 122 to 480 (I tested this with SeePU on at 0.5 second interval and scrolling homescreens, launching benchmarks etc.)
- Yea the camera crashes when restoring defaults in recording mode as stated in mik's dev thread
- The phone's temperature is average 39 degree vs pure's 33 degree
- Temperature displays incorrectly (39 degree as 3.9 degree) vs correctly in pure
CONCLUSION
lol mainly because of the insignificant performances boost even zram is on, im back to mik's pure now
good luck to u all and hope these help
Click to expand...
Click to collapse
Excuseme how can i found mik_os's kernel??
chessy018 said:
Excuseme how can i found mik_os's kernel??
Click to expand...
Click to collapse
It is attached with the zip mik has provided in his dev thread
you have to flash the rom in order to get the attached kernel
for reference, the version of the kernel is displayed 2.6.32.41 on about-phone now
good luck!
ok guyz
i haven't tried 6.5.4 yet coz 6.5.3 working well until now ..
i have 6.5.3+ franco kernel 16 (old one) no zram nothing else
and performance is quit Good bt i think it was more better in Franco 15 kernel ..bt may b its only my thinking coz i analyze when we use data 3g wi fi phone getting heated nt tht much bt u can feel it don;t know..may b its only me feeling bt i have seen some users who already told me about that ..ok then as far as performance concern here check my attachment
battery is nt that bad at normal uses its around 30 hr long
Y.u.v.i said:
ok guyz
i haven't tried 6.5.4 yet coz 6.5.3 working well until now ..
i have 6.5.3+ franco kernel 16 (old one) no zram nothing else
and performance is quit Good bt i think it was more better in Franco 15 kernel ..bt may b its only my thinking coz i analyze when we use data 3g wi fi phone getting heated nt tht much bt u can feel it don;t know..may b its only me feeling bt i have seen some users who already told me about that ..ok then as far as performance concern here check my attachment
battery is nt that bad at normal uses its around 30 hr long
Click to expand...
Click to collapse
lol yea for me even zram activated there are significant performance regression of v16, could really feel it! i think its probably the "cpu responsiveness" ive mentioned
but well the 15 gives random shuts hate it
thx for ur info
I'm running an updated kernel (haven't released yet) with Andy's 2.3 rom and I find no stutters, no random shutdowns, no panics, no battery drains, no nothing. Just pure performance. BFS does a lot of difference for performance and battery. I'll release this update later today.
Overclock is around 480/768 with interactive or smartass depending on my mood.
Remember something, from 122 to 480 overclock there is no change in battery usage because they all share the same voltage. Actually battery life with 480 should be better as CPU enters idle faster, so more power saving.
franciscofranco said:
I'm running an updated kernel (haven't released yet) with Andy's 2.3 rom and I find no stutters, no random shutdowns, no panics, no battery drains, no nothing. Just pure performance. BFS does a lot of difference for performance and battery. I'll release this update later today.
Overclock is around 480/768 with interactive or smartass depending on my mood.
Remember something, from 122 to 480 overclock there is no change in battery usage because they all share the same voltage. Actually battery life with 480 should be better as CPU enters idle faster, so more power saving.
Click to expand...
Click to collapse
Haha franco thx for giving advice in this thread
oh ur tempting me mate thats cool
just a side question do i have to wipe anything except cache, dalvik, battery stats? if i give it a try to swap from mik's to andy's
or do i have to wipe everything and do a complete titanium lol
also why cant i see ppl using or comment about savagedzen? i personally use it idk why
and yeah thanks ive been searching for that for a while but cant find the clue and you answered me directly all my profile mins are 480 now!
franciscofranco said:
I'm running an updated kernel (haven't released yet) with Andy's 2.3 rom and I find no stutters, no random shutdowns, no panics, no battery drains, no nothing. Just pure performance. BFS does a lot of difference for performance and battery. I'll release this update later today.
Overclock is around 480/768 with interactive or smartass depending on my mood.
Remember something, from 122 to 480 overclock there is no change in battery usage because they all share the same voltage. Actually battery life with 480 should be better as CPU enters idle faster, so more power saving.
Click to expand...
Click to collapse
yes excuseme how do i change mik to andy? wipe which? thanks very.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Are you a ParanoidAndroid user on P500?
Welcome to the Discussion thread, here you shall ask all the general questions/ queries/ problems related to this specific ROM.
The development thread isn't meant for asking questions on HOW-TO, its meant to report serious bugs and should be used if you are ready to help in the development.
This thread is only for Bytecode's build from source ROMs based on Android 4.1.2 JellyBean.
Downloads can be found here.
Have any questions? Shoot! I will and others also who are aware of your answers shall try and help you
Until then I will upload some F.A.Q. to the post #2
:Reserved:
I was wondering about the picture quality taken with the camera.
sovikhaque said:
I was wondering about the picture quality taken with the camera.
Click to expand...
Click to collapse
Its the exact same as ICS
Have tried to flash ICS and JB ROMs (lupohirp, hephappy, Arjen, Adfad666. laz3r96, Rashed , incl. Bytecode's PA v2.2. and 2.52) on LG P500, however the device with all those ROMs failed to be detected as USB modem by Linux machine. It's not happened with openOptimus GB ROM (franco kernel), where p 500 is detected as USB modem out of the box. I think its related with how the kernel is configured (ppp and setserial). Unfortunately, I'm incapable to compile android kernel myself, but linux. I tried flash both DJNoXD and thachtunganh's kernel, but failed, while franco kernel just for GB!
Have anyone experienced such issue and how to fix it? Which kernel you used it? Really, I'm very much expecting to use ICS/JB p500 as usb modem (not usb tethering!). Well no need to buy a new USB GSM Modem
Any help is highly appreciated
xu3sno said:
Have tried to flash ICS and JB ROMs (lupohirp, hephappy, Arjen, Adfad666. laz3r96, Rashed , incl. Bytecode's PA v2.2. and 2.52) on LG P500, however the device with all those ROMs failed to be detected as USB modem by Linux machine. It's not happened with openOptimus GB ROM (franco kernel), where p 500 is detected as USB modem out of the box. I think its related with how the kernel is configured (ppp and setserial). Unfortunately, I'm incapable to compile android kernel myself, but linux. I tried flash both DJNoXD and thachtunganh's kernel, but failed, while franco kernel just for GB!
Have anyone experienced such issue and how to fix it? Which kernel you used it? Really, I'm very much expecting to use ICS/JB p500 as usb modem (not usb tethering!). Well no need to buy a new USB GSM Modem
Any help is highly appreciated
Click to expand...
Click to collapse
Even if it doesn't show "USB Modem" in ICS/ JB ROMs, still then have you tried to use it as a modem?
Wow thank you for this thread! Anyway,about the USB,I think it's because of netd's UsbController (we were using a custom one on gb but it was removed in ics),I'll try building with that.
Hi!
Do you plan to fixe wi-fi and bluetooth tethering?
Thanks.
Anyone got tips to increase battery life? My god I love this rom but it eats my battery to death just from sitting on my desk.
Herox said:
Anyone got tips to increase battery life? My god I love this rom but it eats my battery to death just from sitting on my desk.
Click to expand...
Click to collapse
Same here. I remember having Rashed's build with Performance CPU governor but now I had to change to SmartAssV2 since, for some reason I can't identify yet (even looking at BetterBatteryStats) the phone stays awake much longer than before, which means more time at higher CPU speed. With Wifi the battery will drain in just a few hours... In those weekends at home I can't leave it with wifi on. Do any of you guys have a good battery experience?
Herox said:
Anyone got tips to increase battery life? My god I love this rom but it eats my battery to death just from sitting on my desk.
Click to expand...
Click to collapse
filipeataide said:
Same here. I remember having Rashed's build with Performance CPU governor but now I had to change to SmartAssV2 since, for some reason I can't identify yet (even looking at BetterBatteryStats) the phone stays awake much longer than before, which means more time at higher CPU speed. With Wifi the battery will drain in just a few hours... In those weekends at home I can't leave it with wifi on. Do any of you guys have a good battery experience?
Click to expand...
Click to collapse
The battery life is pretty good with this ROM but YES! some minor tweak here and there are still required and Bytecode is already aware of that :highfive:
Secondly, never compare battery life with higher CPU frequencies. Bugs are excepted only at maximum freq. set to 600MHz. Higher frequencies suck battery life sometimes and you should choose an apt governor, performance is not good for battery.
Thirdly, make sure you have uninstalled all the apps you have installed before reporting anything. Background apps like facebook, maps, IMs etc acquire a lot of RAM which equates on using more battery life.
Lastly, try to keep "sync" switched off when you don't need it, provides you with some extra battery life.
Remember this, you are running Jelly Bean on a low end device, bugs and problems are expected, all you have to do is to cope and choose the right ROM according to your requirements :angel:
DJoptimus-One said:
Even if it doesn't show "USB Modem" in ICS/ JB ROMs, still then have you tried to use it as a modem?
Click to expand...
Click to collapse
Yep. I tried out to use it as USB modem on all ROMs (ICS and JB) and the results were same. When I run wvdialconf command on linux machine, the message is as follow:
wvdialconf /etc/wvdial.conf
Editing `/etc/wvdial.conf'.
Scanning your serial ports for a modem.
Modem Port Scan<*1>: S0 S1 S2 S3
Sorry, no modem was detected! Is it in use by another program?
Did you configure it properly with setserial?
Please read the FAQ at http://alumnit.ca/wiki/?WvDial
while on GB:
Editing `/etc/wvdial.conf'.
Scanning your serial ports for a modem.
Modem Port Scan<*1>: S0 S1 S2 S3
WvModem<*1>: Cannot get information for serial port.
ttyACM0<*1>: ATQ0 V1 E1 -- OK
ttyACM0<*1>: ATQ0 V1 E1 Z -- OK
ttyACM0<*1>: ATQ0 V1 E1 S0=0 -- OK
ttyACM0<*1>: ATQ0 V1 E1 S0=0 &C1 -- OK
ttyACM0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK
ttyACM0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
ttyACM0<*1>: Modem Identifier: ATI -- Manufacturer: LG Electronic Inc
ttyACM0<*1>: Speed 4800: AT -- OK
ttyACM0<*1>: Speed 9600: AT -- OK
ttyACM0<*1>: Speed 19200: AT -- OK
ttyACM0<*1>: Speed 38400: AT -- OK
ttyACM0<*1>: Speed 57600: AT -- OK
ttyACM0<*1>: Speed 115200: AT -- OK
ttyACM0<*1>: Speed 230400: AT -- OK
ttyACM0<*1>: Speed 460800: AT -- OK
ttyACM0<*1>: Max speed is 460800; that should be safe.
ttyACM0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
Found an USB modem on /dev/ttyACM0.
Modem configuration written to /etc/wvdial.conf.
ttyACM0<Info>: Speed 460800; init "ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0"
---------- Post added at 01:12 PM ---------- Previous post was at 01:04 PM ----------
Bytecode said:
Wow thank you for this thread! Anyway,about the USB,I think it's because of netd's UsbController (we were using a custom one on gb but it was removed in ics),I'll try building with that.
Click to expand...
Click to collapse
Understood, since you built optimusOne yourself. Hope you can build with JB too. :good: Wish you luck! Can't wait to have that custom kernel!.
DJoptimus-One said:
The battery life is pretty good with this ROM but YES! some minor tweak here and there are still required and Bytecode is already aware of that :highfive:
Secondly, never compare battery life with higher CPU frequencies. Bugs are excepted only at maximum freq. set to 600MHz. Higher frequencies suck battery life sometimes and you should choose an apt governor, performance is not good for battery.
Thirdly, make sure you have uninstalled all the apps you have installed before reporting anything. Background apps like facebook, maps, IMs etc acquire a lot of RAM which equates on using more battery life.
Lastly, try to keep "sync" switched off when you don't need it, provides you with some extra battery life.
Remember this, you are running Jelly Bean on a low end device, bugs and problems are expected, all you have to do is to cope and choose the right ROM according to your requirements :angel:
Click to expand...
Click to collapse
I changed now for max 600 and expect to have a slight gain in battery life. On the background apps do you use any alternatives? As for now I can only increase the time interval for sync on FB. I dont use IMs although I have google+. I have no replacement for facebook or maps.
DJoptimus-One said:
The battery life is pretty good with this ROM but YES! some minor tweak here and there are still required and Bytecode is already aware of that :highfive:
Secondly, never compare battery life with higher CPU frequencies. Bugs are excepted only at maximum freq. set to 600MHz. Higher frequencies suck battery life sometimes and you should choose an apt governor, performance is not good for battery.
Thirdly, make sure you have uninstalled all the apps you have installed before reporting anything. Background apps like facebook, maps, IMs etc acquire a lot of RAM which equates on using more battery life.
Lastly, try to keep "sync" switched off when you don't need it, provides you with some extra battery life.
Remember this, you are running Jelly Bean on a low end device, bugs and problems are expected, all you have to do is to cope and choose the right ROM according to your requirements :angel:
Click to expand...
Click to collapse
Yes but this may be a bug here. My wifi does not turn off when the phone is idle/asleep. Wifi stays on and that burns battery too. Last rom I had before this was cm7.2 nightly I think and yea, it turned my wifi off after so long. Is there a way to make it time out after like a minute of idle?
Herox said:
Yes but this may be a bug here. My wifi does not turn off when the phone is idle/asleep. Wifi stays on and that burns battery too. Last rom I had before this was cm7.2 nightly I think and yea, it turned my wifi off after so long. Is there a way to make it time out after like a minute of idle?
Click to expand...
Click to collapse
You have benefits of apps, search the play store for wifi related apps, I am quiet sure that you will get what you need :highfive:
Herox said:
Yes but this may be a bug here. My wifi does not turn off when the phone is idle/asleep. Wifi stays on and that burns battery too. Last rom I had before this was cm7.2 nightly I think and yea, it turned my wifi off after so long. Is there a way to make it time out after like a minute of idle?
Click to expand...
Click to collapse
Superpower will let one set up stuff like this. There may be other small apps just for wifi and gs data shutdown as well.
Thanks for the tips guys. I also set the cpu so it can down clock as far as it can. That way when its idle it uses less power too. No need to sit at 300mhz when its not being used. And I switched the governor to conservative. Not sure which governor is best for balanced power usage.
Herox said:
Thanks for the tips guys. I also set the cpu so it can down clock as far as it can. That way when its idle it uses less power too. No need to sit at 300mhz when its not being used. And I switched the governor to conservative. Not sure which governor is best for balanced power usage.
Click to expand...
Click to collapse
You are using the right governor, stick to it.
Things have been soooo quiet in paranoid-land lately, hiding out I guess
2.54? Mic-fix?
I noticed that build.prop is set for ... triple buffering. Is this nonsense or is this actually implemented? Vsync is disabled and likely kernel mods are needed to use that.
The 4.2 buzz:
There is no room for that keyboard on system but I have swype anyway. I actually installed the 4.2 KB as a user-app but it fc'd. Did not have the libs so that might have been the problem (the first apks, zips that listed were missing some pieces). Could try it again, properly, but nothing really compelling here. Google is playing catch-up with this one.
I have the gallery installed along with its three libs/jni's. Camera crashes the gallery and hides the dialog with an artifact--tapping there will dismiss normally. The new photo edit functions will sometimes work, more usually simply blink and disappear. The legacy-camera still works independently so no harm in keeping this around (but I suspect it might be causing lagginess elsewhere!). For the photosphere capability, a modded camera version will need to use the compass/magnetometer instead of the gyroscope--I do not think we have one.
Put on the new Play and gmscore (which was with the gallery/camera zip!). Works like the older one, see no changes. I do not use gmail app but this new one has impressive improvements--worth a try if one makes use of it.
Clock looks interesting, might play with that tomorrow, but users of more advanced handsets have had fc's with it.
In all, there are 175 meg work of gapps. Do not dare attempt to flash this. Like no room for any of it. Extract items one wants to try and install as user apps. Specific libs and be pushed to /system/lib. However, all those jni's are likely not opensource and may be compiled for ARMv7 rendering them useless for our phones. No harm trying them out.
More 4.2 Buzz:
Put on the clock. Not very pretty but nice new functionality. I replaced with the blue version on the 4.2 goodies thread, a bit nicer. This widget could use some visual design improvement. Layout of world-clock functions (and others as well) is too large but we have the means to fix that, huh!
New Maps and StreetView. Maps has little more pizzazz. Problem I encountered was continued GPS activity after closing it, attempting to toggle on the status bar caused a reboot. I had not rebooted after updating the apps so might be my fault. See if problem repeats. (I have been having problems with the status bar lately and I suspect memory problems or other caused by the Gallery.) That the new streetview works without a hitch would indicate that the Camera/Gallery problems are not ARMv6 related.
Google TTS has no "certificate" so could not simply reinstall. I have this as a user APP from before but might have achieved this manually (I do really believe I saw it once installable from Play!) like I did for a transparent-modded GenieWidget found on XDA. I leave this one for now.
I placed the ThinkFree doc viewer instead of the Kingsoft Office which I had uninstalled before flashing this ROM (since these larger-dexed apps need to be uninstalled before reflash). I'll decide which to use later on--editing docs on this device does not seem too practical so the viewer, which works really nicely, might stay.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DESCRIPTION
This is a custom based Kernel for the D855/D852/D851/D850/VS985/LS990 variants of the LG G3 with performance enhancements and bug fixes that I have been using personally for a few months, thought it is time to share since I have had no inconvenient bugs and quite a big performance increase and smooth UI benefits. The intention is to have a minimal light-weight kernel that is fine tuned for the device.
FEATURES
User space voltage control
Backport MSM devfreq features from 3.18 Kernel for the smoothest experience, includes adding cache fabric frequency scaling and better bus utilization as well as the mincpubw governor
User space display color calibration (KCAL)
Deeper memory controller power savings on suspend (deeper power savings while sleep)
Two new L2 cache frequency steps: 1.88 & 2.03 GHz, allows for better multi-core utilization and hit rates
Wireless roaming disconnecting is now fixed
IRQ Balancer enabled with proper SELinux support to spread out the interrupts of our SoC
IntelliPlug to allow lower thermal dissipation by keeping some cores alive to distribute loads and keep frequencies lower accross SoC die
Reduced heat when using wireless chargers
Memory and cache subsystem optimizations, you will feel it int the UI
Adreno Idler to get better GPU frequency utilization and battery life [removed as msm-adreno now idles properly]
Interactive governor tweaks to focus on lower frequencies while still maintaining fluidity in the UI
BFQ IO scheduler set by default to avoid slow-downs on task intensive scenarios
No overclocking was chosen to avoid unnecessary heat, optimizations were focused on other different areas
Kernel Samepage Sharing enabled with deferred timer by default to gain some memory usage optimizations
Compiled with GCC 6.x optimized toolchain and -O3 plus other hardware specific flags
Undervolted the Adreno 330 GPU voltage rail to keep things cooler, and reduced the GPU min frequency to 27 MHz while keeping it's temperature cool to reach 620 MHz overclock
Default thermal values work ok, since GPU voltage rails and others were shaved a few mV
100 Hz tick to prevent excessive battery usage, the smoothness of the UX does not come alone from raw processing -- there are many other changes in the subsystem that helped achieve the fluidity
An ultra low value in the interactive min_sample_time so that the interactive governor does not hover on excessive frequencies
Heavily tuned the GPU bandwidth and bus requirements to match closer the capabilities of the device and thus preventing micro-stutters
Optimized the MSM crypto engines thanks to @waau
Updated the KGSL drivers so that we can use the Adreno userspace drivers version Adreno-MOB30M-for-LG-G3-AOSP.zip
DOWNLOADS
AnyKernel: Click Here (Check Top of the Post, Download Tab)
SOURCE
D85X-Kernel-Gamma GitHub Source
NOTES
I recommend turning NFC off for way better idle battery consumption :victory:
KNOWN BUGS
FM Radio is causing hangs, still needs investigation
<< If you like my work here is my hat, please donate! >>
XDA:DevDB Information
Gamma Kernel , Kernel for the LG G3
Contributors
Omar-Avelar
Source Code: https://github.com/oxavelar/D85X-Kernel-Gamma
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 90.0.0
Stable Release Date: 2018-05-10
Created 2016-08-09
Last Updated 2018-05-13
Thank you for this kernel, I have a question:
Fast charging is implemented?
Thanks again
@Omar-Avelar Download link for d855 leads to d851 version and vice versa..
Sent from my caseless LG G3, because I believe in myself
Is there a sound mod for headphone gain?
download link need to update, will try it and report.
THANK YOU!!!!!
after instelling the kernel on my d855 with the xenon rom it doesnt charge via usb in the pc... i am at work right now and cant check in the wall socket.
@agdish84, I have now updated the links, thanks... I missed that.
Hey @jochem86, USB charging is working on CM ROM's so I wonder if Xenon ROM is doing anything funky, mmm... I will check if Xenon has anything strange but it is not touching anything charge related.
This Kernel does not support USB force fast charge because fast charging will cause batteries to age faster. It's a trade-off, and usually ends up providing more heat. Not sure if I will put support on forced USB fast charge or not.
Omar-Avelar said:
@agdish84, I have now updated the links, thanks... I missed that.
Hey @jochem86, USB charging is working on CM ROM's so I wonder if Xenon ROM is doing anything funky, mmm... I will check if Xenon has anything strange but it is not touching anything charge related.
This Kernel does not support USB force fast charge but might do add it in the week if a lot of people feel the need of it. [Btw, personally this is the main reason why I did not enable fast charging enabled sysfs force control - URL]
Click to expand...
Click to collapse
Dirty flashed the xenon again and it charges again without any problem. I have to say some other roms it doesnt charge in usb when i am using it... with xenon it doest but very slow, that is normal. But also in deep sleep, it doenst charge a bit... i guess in xenon the fast charge is enabled and other roms not bu default. i hope you figure out whats messign it up.
jochem86 said:
Dirty flashed the xenon again and it charges again without any problem. I have to say some other roms it doesnt charge in usb when i am using it... with xenon it doest but very slow, that is normal. But also in deep sleep, it doenst charge a bit... i guess in xenon the fast charge is enabled and other roms not bu default. i hope you figure out whats messign it up.
Click to expand...
Click to collapse
Thanks for the update, and do let me know how do you feel this Kernel in terms of performance against the others you've used. It doesn't have to be immedeatly, use it for a while and give me some feedback on things you see are working good too, thanks a lot
Omar-Avelar said:
Thanks for the update, and do let me know how do you feel this Kernel in terms of performance against the others you've used. It doesn't have to be immedeatly, use it for a while and give me some feedback on things you see are working good too, thanks a lot
Click to expand...
Click to collapse
That was my intention to give you my experience but my batt was pretty low so i changed it back to stock kernel... as i am on my work right now but for those few minutes i tried it felt pretty smooth.
Omar-Avelar said:
Thanks for the update, and do let me know how do you feel this Kernel in terms of performance against the others you've used. It doesn't have to be immedeatly, use it for a while and give me some feedback on things you see are working good too, thanks a lot
Click to expand...
Click to collapse
In terms of performance? Oh yes, give me time to flash CM13 and test UI smoothness, I have feeling this is right thing for that. Waiting for this for a long time.
@Omar-Avelar do you have any plans on adding gamma control? I'm really enjoying myself atm running it with Zephyr os rom. Ty for your hard work!
Sent from my caseless LG G3, because I believe in myself
AICP booted, the 10 seconds I have had it on it seems really snappy, will let you know how it goes.
stuck on splash screen after installing...
D855 32GB - Fullmics ROM
grymmy said:
stuck on splash screen after installing...
D855 32GB - Fullmics ROM
Click to expand...
Click to collapse
Fulmics is stock based from what I have read (I've never installed it personally). But I am glad to hear that you tried it out there but too bad it doesn't work on Fulmics!
I will add some notes to the thread to let other people know.
Jagdish84 said:
@Omar-Avelar do you have any plans on adding gamma control? I'm really enjoying myself atm running it with Zephyr os rom. Ty for your hard work!
Sent from my caseless LG G3, because I believe in myself
Click to expand...
Click to collapse
I think I will do that, it might be about the only things that are do needed and won't interfere as much with stability. Gimmie a few weeks to get some free time.
Omar-Avelar said:
Fulmics is stock based from what I have read (I've never installed it personally). But I am glad to hear that you tried it out there but too bad it doesn't work on Fulmics!
I will add some notes to the thread to let other people know.
Click to expand...
Click to collapse
thank you for such speedy feed back. I'm about to install Zephyr os rom and test...thanks again
Using this kernel made me love my phone again. Was using Latest CM 13 and UI was time to time laggy and slow. Flashed this kernel and device runs smooth as butter. Love that kernel does not overclock anything so i know that i don't shorten life span of my cpu. Kudos to @Omar-Avelar for developing something like this!
Could you add DT2S and DT2W on your kernel?
#ParanoidAndroid
Phone heats up a lil while charging... Didn't use it or anything, just picked it up to see the time and it felt rather warm to me, using zephyr rom and a lil undervolting. Btw, during regular usage phone is stone cold, kudos!
Sent from my caseless LG G3, because I believe in myself
Below you will find a couple of kernels that I put together for various roms and purposes. Most of these will be included into my other builds, but I thought that I would share them here as well, in case they are useful on any other roms. You are welcome to use and abuse these kernels or the source code for any purpose that you see fit!
It all started over a year ago when I wanted to add some governors to a kernel, and it didn't work very well. However, praise God, I learned a lot of things and was able to add the governors in! From there I played around with various sources and have put together some developer kernels as well (including kexec and other tools). None of my work is purely original, I typically beg or borrow from other kernel developers by looking at their source. Please feel free to use any of the materials here if it will help you in any way (including adding it to a different rom).
Feel free to comment if you have tried them on another rom, successful or not, or to leave feedback on these kernels as well. These can be flashed on any tblte variant of phone, but I have only personally tested them on tbltetmo. They should work on any tbltexx phone as well, and maybe others.
This is, however, specifically not for TW roms. This is for AOSP/CM etc., based roms.
Post #2: Thanks
Post #3: Marshmallow kernels
Post #4: Change logs
Source: https://github.com/alaskalinuxuser
Post created: 10/26/16
Last updated: 12/22/16
The big thanks!
As with any project, it starts somewhere, and while I want to give God the glory for my work, I also want to thank a few other people who helped me (directly or indirectly) along the way:
@OldDroid
@Mickey387
@deadman96385
The Emotroid Team
For AOKP 6.0.1, may also work with PAC and CM.
Download:
http://www.mediafire.com/file/zodtgo623rkj09f/AKLU-AOKP-M-TBLTE-intelliplug-20161222.zip
For PACROMS 6.0.1, may also work with AOKP and CM.
Download:
http://www.mediafire.com/file/bafiwx8epkiqteb/AKLU-PAC-M-TBLTE-intelliplug-20161222.zip
For SLIMROMS 6.0.1, may also work with LS.
Download:
http://www.mediafire.com/file/bb5ns8nq4ybt376/AKLU-SLIM-M-TBLTE-intelliplug-20161222.zip
Features:
- CPU over clocked to 2688 MHz.
- GPU over clocked to 633 MHz.
- Intelli_plug by @faux123!
- Bioshock, Darkness, Nightmare, and Lionheart Governors!
- CPU boost, DVSF input boost disabled so you can use CPU boost for input.
OLD KERNELS:
https://www.mediafire.com/download/3hdl2bl4j3eqbdw
https://www.mediafire.com/download/waz9bklaj808o90
https://www.mediafire.com/download/nh1oa058qdqa708
PAC/AOKP 6.0 baseline:
http://www.mediafire.com/file/h9b68aaon1yvr11/aokp_pac-mm-kernel-baseline.zip
Slim 6.0 baseline:
http://www.mediafire.com/file/bt4qw03m8jko53a/slim-mm-kernel-baseline.zip
Developer kernel for AOKP and PAC ROM:
https://www.mediafire.com/download/6q16143xjmf6hje
Features:
- Kexec enabled
- Modules enabled
- CPU over clocked to 2688 MHz.
- GPU over clocked to 633 MHz.
- Bioshock, Darkness, Nightmare, and Lionheart Governors!
- CPU boost, DVSF input boost disabled so you can use CPU boost for input.
- DANGEROUS! USE WITH CAUTION!
Notes:
May require a clean flash over fresh ROM. I have had trouble where I also needed to wipe coach after flashing. ATAGS is enabled. This kernel is potentially a security risk, but may allow you to play with multirom or other multiple boot options.
Change Log:
20161222
+ Added Intelli_plug by @faux123!
20161116
+ Over clocked CPU to 2688 MHz.
+ Over clocked GPU to 633 MHz.
20161115
+ Added the Bioshock Governor.
+ Added the Lionheart Governor.
+ Added the Nightmare Governor.
+ Added the Darkness Governor.
- Removed FIOPS I/O Scheduler.
- Removed ZEN I/O Scheduler.
Removed extra I/O schedulers due to recurrence of the random reboots.
20161114
+ Added ZEN and FIOPS I/O Schedulers.
20161109
+ Disabled DVSF INPUT BOOST, which locked the CPU at 1267 MHz when you touch the screen or use the SPEN. Now you can use CPU boost in Kernel Aduitor to select the amount of boost you want when input is detected (or not to boost at all).
+ Started over from the ground up to get rid of the random reboot problem.
Keep in mind:
Just something to keep in mind, these kernel features (more as they are added) are not always enabled by default. You will need tools like the Kernel Adiutor app to control, enable, or use these features.
Any are welcome to chime in on thoughts, requests, and settings! Be sure to stay tuned, more will be added regularly!
I am aware of kernel vulnerability CVE-2016-5195 "Dirty C0W" and am working on implementing a fix to secure these kernels from that vulnerability. If you need information about it, you can read up on it here:
https://github.com/dirtycow/dirtycow.github.io/wiki/VulnerabilityDetails
AlaskaLinuxUser said:
I am aware of kernel vulnerability CVE-2016-5195 "Dirty C0W" and am working on implementing a fix to secure these kernels from that vulnerability. If you need information about it, you can read up on it here:
https://github.com/dirtycow/dirtycow.github.io/wiki/VulnerabilityDetails
Click to expand...
Click to collapse
U could share the kernel buiding lol I've been trying so hard to find files for gpu/cpu can u point me to those? Also how would I turn zimage into a boot.img..... the android kitchen thing is a little confusing
Excellent work as always Alaska. It'd be fantastic if we could get some hotplugging alternatives alongside the governor's, as mpdescision never plays well with over or under clocking.
Also I don't want to nag, but any luck exterminating that damn touchboost up to 1.2-1..7 ghz on core 0 and 1? I've found that whenever the pen is hovering near the digitizer it locks both cores at 1.2 which aside from being wholly unnesacary, definatly isn't helping the meagre battery life. Was also wondering if power to the digitizer might be a kernel function. And if so, whether power could suspended from the array whenever the spen is inserted. Mostly shooting in the dark, but TW ROMS have the ability to disable detection of the pen being distant from the handset. Dunno if the sensors that perform that function are being called by AOSP or CM, but it might be worth looking into having an option to disable them to save more power.
beany23 said:
U could share the kernel buiding lol I've been trying so hard to find files for gpu/cpu can u point me to those? Also how would I turn zimage into a boot.img..... the android kitchen thing is a little confusing
Click to expand...
Click to collapse
Beany23,
I can put together a little how to if you would like, I like working on kernels, it is a great learning experience, and it is fun. I over clocked my kernel on my phone, and am testing stability right now. The oc is small, but I made no increase in voltage or amperage, so it is a free boost. I plan to post it tomorrow. Working on kernels is really a lot of fun.
Aaren11 said:
Excellent work as always Alaska. It'd be fantastic if we could get some hotplugging alternatives alongside the governor's, as mpdescision never plays well with over or under clocking.
Also I don't want to nag, but any luck exterminating that damn touchboost up to 1.2-1..7 ghz on core 0 and 1? I've found that whenever the pen is hovering near the digitizer it locks both cores at 1.2 which aside from being wholly unnesacary, definatly isn't helping the meagre battery life. Was also wondering if power to the digitizer might be a kernel function. And if so, whether power could suspended from the array whenever the spen is inserted. Mostly shooting in the dark, but TW ROMS have the ability to disable detection of the pen being distant from the handset. Dunno if the sensors that perform that function are being called by AOSP or CM, but it might be worth looking into having an option to disable them to save more power.
Click to expand...
Click to collapse
Aaren11,
Yes, I agree. I have disabled the boost in my testing, but then could not get the kernel to boot. The kernel I am working with has many of Mickey378's fingerprints on it, so I am sorting some of those out. Then I can delve more into those. For instance, when I run " make mrproper " it looks for /home/mickey/android...... And errors, so I am trimming his work while maintaining the great work he did to actually make it function for AOSP ROMs. I also am experimenting with other kernel sources like OldDroid's and others. Keeping in mind that only Mickey had a 100% fully functional ROM.
I do want to say though, I couldn't agree more, the mandatory touch boost is a pain. It should be adjustable, but it doesn't take when we set it.
But, work is progressing. One step at a time.
Sent from my unknown using XDA-Developers mobile app
I would love to try the kexec-hardboot kernel if you'd be kind enough to share. Multirom on this dying device would be nothing short of a miracle.
Sent from my unknown using XDA-Developers mobile app
AlaskaLinuxUser said:
Beany23,
I can put together a little how to if you would like, I like working on kernels, it is a great learning experience, and it is fun. I over clocked my kernel on my phone, and am testing stability right now. The oc is small, but I made no increase in voltage or amperage, so it is a free boost. I plan to post it tomorrow. Working on kernels is really a lot of fun.
Aaren11,
Yes, I agree. I have disabled the boost in my testing, but then could not get the kernel to boot. The kernel I am working with has many of Mickey378's fingerprints on it, so I am sorting some of those out. Then I can delve more into those. For instance, when I run " make mrproper " it looks for /home/mickey/android...... And errors, so I am trimming his work while maintaining the great work he did to actually make it function for AOSP ROMs. I also am experimenting with other kernel sources like OldDroid's and others. Keeping in mind that only Mickey had a 100% fully functional ROM.
I do want to say though, I couldn't agree more, the mandatory touch boost is a pain. It should be adjustable, but it doesn't take when we set it.
But, work is progressing. One step at a time.
Sent from my unknown using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes plz the would be awesome!!!
Aaren11 said:
Excellent work as always Alaska. It'd be fantastic if we could get some hotplugging alternatives alongside the governor's, as mpdescision never plays well with over or under clocking.
Also I don't want to nag, but any luck exterminating that damn touchboost up to 1.2-1..7 ghz on core 0 and 1? I've found that whenever the pen is hovering near the digitizer it locks both cores at 1.2 which aside from being wholly unnesacary, definatly isn't helping the meagre battery life. Was also wondering if power to the digitizer might be a kernel function. And if so, whether power could suspended from the array whenever the spen is inserted. Mostly shooting in the dark, but TW ROMS have the ability to disable detection of the pen being distant from the handset. Dunno if the sensors that perform that function are being called by AOSP or CM, but it might be worth looking into having an option to disable them to save more power.
Click to expand...
Click to collapse
Just a quick comment, mpdescision is actually a really big battery saver, unless you use a hotplugging governor. You can check this for yourself:
Enable mpd, enable nightmare, turn on caffeine or set screen to stay on 5 minutes. Watch the screen. Open KA and watch the CPU settings screen. The CPU will drop to one core at 300 MHz and pretty much stay there.
Then, disable mpd, now watch the CPU screen, you will see 3 or 4 cores on at all times.
In my other kernels for other Samsung phones, I always leave mpd on, and I can still over/under clock/volt. So I intend to leave mpd, but I do agree we need to ditch the mandatory touch boost, especially for just having the spen out.
Sent from my unknown using XDA-Developers mobile app
New kernel is up!
Hi all! Praise God, another successful kernel build. This time is just some very light CPU overclocking without any negative battery drain! See main posts for details and downloads!
20161027
+CPU overclocked to 2688 MHz without increasing voltage or amperage. (+39 MHz)
See commit here: https://github.com/alaskalinuxuser/...mmit/9bb23d0d9cc805bf7e1b8e3fe829fcbb0542af31
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
AlaskaLinuxUser said:
Just a quick comment, mpdescision is actually a really big battery saver, unless you use a hotplugging governor. You can check this for yourself:
XDA-Developers mobile app
Click to expand...
Click to collapse
Errr...Alaska? I wasn't contending that mpdescision (a hotplug) is somehow less energy effcient than NO HOTPLUG. But it is one of the least effcient ones out there. Espceially when over or underclocking. Because Mpdesicion will override anything other than the stock clocks.
Also unless you disabled it, Nightmare does it's own hotplugging.
Aaren11 said:
Errr...Alaska? I wasn't contending that mpdescision (a hotplug) is somehow less energy effcient than NO HOTPLUG. But it is one of the least effcient ones out there. Espceially when over or underclocking. Because Mpdesicion will override anything other than the stock clocks.
Also unless you disabled it, Nightmare does it's own hotplugging.
Click to expand...
Click to collapse
"Nightmare
A PegasusQ modified, less aggressive and more stable. A good compromise between performance and battery. In addition to the SoD is a prevention because it usually does not hotplug."
http://ajgupta.github.io/android/2015/01/28/CPU-and-GPU-governors/
As you can see from my previous posts, if you disable mpd in KA, then you can watch the CPU cores. Nightmare will not turn them off except in rare instances on my phone with the screen on. That is one of the principle differences between Nightmare and PegasusQ.
Also, mpd is currently accepting my overclock input in the kernel. So mpd doesn't always have to cause problems with over/under frequencies, I am no expert, but I believe this stems from how the table is built.
In either event, there are a lot of really great hotplugging options, on that we agree. Now, less you think I am being facetious, I actually quite enjoy your input and discussion, so please don't take this as anything other than great discussion. The great thing about Android/Linux/kernels is that they are like ice cream, with so many flavors, everyone is bound to find one they like, or a combination that they think is the best, and there will always be a difference of opinion.
I also still have a lot to learn on the subject myself.
beany23 said:
Yes plz the would be awesome!!!
Click to expand...
Click to collapse
Beany23,
Still a work in progress, but for what it's worth, here is the guide:
http://forum.xda-developers.com/note-edge/general/guide-build-aosp-roms-kernels-note-edge-t3488840
AlaskaLinuxUser said:
Beany23,
Still a work in progress, but for what it's worth, here is the guide:
http://forum.xda-developers.com/note-edge/general/guide-build-aosp-roms-kernels-note-edge-t3488840
Click to expand...
Click to collapse
Can u tell me where the files are regarding cpu/gpu? And one more thing....I'm so glad someone has some love for this device lol great work and keep on keepin!
AlaskaLinuxUser said:
A PegasusQ modified, less aggressive and more stable. A good compromise between performance and battery. In addition to the SoD is a prevention because it usually does not hotplug.".
Click to expand...
Click to collapse
Dammit, I misread that very same passage. Ah well thanks for the correction.
AlaskaLinuxUser said:
Also, mpd is currently accepting my overclock input in the kernel. So mpd doesn't always have to cause problems with over/under frequencies, I am no expert, but I believe this stems from how the table is built..
Click to expand...
Click to collapse
That's definatley good news. On TW, any kernel with interactive would allow mpdescision to bump the clocks to stock values. Disabling mpdescision could make your under or overclock stick,but then you'd have no hotplugging.
AlaskaLinuxUser said:
I actually quite enjoy your input and discussion, so please don't take this as anything other than great discussion. The great thing about Android/Linux/kernels is that they are like ice cream, with so many flavors, everyone is bound to find one they like, or a combination that they think is the best, and there will always be a difference of opinion.
Click to expand...
Click to collapse
Likewise, I'm honestly beyond grateful someone finally started making non-TW ROMS and kernels for this device, and I'm always interested for a good Android discussion. Especially when it drives progress like this.
beany23 said:
Can u tell me where the files are regarding cpu/gpu? And one more thing....I'm so glad someone has some love for this device lol great work and keep on keepin!
Click to expand...
Click to collapse
The CPU Governor files are in the drivers/cpufreq/ folder, and all start with cpufreq_{DRIVERNAME.c}.
E.G. Nightmare = cpufreq_nightmare.c
You can read about it in more detail on Post #8 of the guide.
AlaskaLinuxUser said:
The CPU Governor files are in the drivers/cpufreq/ folder, and all start with cpufreq_{DRIVERNAME.c}.
E.G. Nightmare = cpufreq_nightmare.c
You can read about it in more detail on Post #8 of the guide.
Click to expand...
Click to collapse
I meant the frequency tables lol