I recently built a CM7 O2x kernel from my G2x (cm-kernel based) source for a O2x user who now uses a Pre^3 and thus i am feedback less.
If someone who is not afraid of a possible non boot would test the kernel (test build is a 1.0GHz kernel aimed at saving battery) I could build O2x versions of my kernel on a more regular basis if feedback shows everything indeed works.
If the initial obstacle is cleared, i would build my 1.5+GHz version next.
http://goo.gl/CgbVD is ELP-O2x-10092011, so built 3 days ago.
Thanks in advance for any feedback.
here i am...
EDIT:Just tryed on latest miui and work well...
yes it works
yes everything works fine and can you make your 1.5GHz version
{
"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"
}
It works fine
Sent from my Optimus 2X using Tapatalk
Hi, great to see you here morfic. Finally . Your kernels for the NS were simply amazing....
I flashed it and so far everything works...
Looking forward to an e-penis kernel.
gaeng4665 said:
Looking forward to an e-penis kernel.
Click to expand...
Click to collapse
+1
Sent from my Optimus 2X using Tapatalk
possibly a stupid question but this kernel can be applied to stock rom 10d?, my English is bad and may not say it to understand what kind of rom is
No it is ONLY for CM7 based roms!
BTW i'm getting killer benchmark scores, can't say so much about battery life though (too little time since i flashed it),
After the gym i had a SOD, but didn't run alogcat, so i'm not saying it is related to the kernel.
It's just meant as a piece of info....
Hope you build the 1.5 Ghz kernel soon...
Very smooth but lot of sudden deaths
Sent from my Optimus 2X using Tapatalk
http://goo.gl/5C12v T15-O2x-14092011
we have a lot of half truths in G2x land, like that G2x can't run 216MHz minimum frequency without SoD.
With this kernel and the "ELP" one, 216MHz is no problem in G2x land.
it's possible the rumor is from applying O2x experiences to G2x early on.
In which case i could dig through the source and see if there is anything obvious that fixed it for G2x, but not O2x
(raise minimum frequency on either kernel if you do experience a SleepOfDeath/SoD)
Keep in mind this is a 1560MHz kernel i linked in this post, with the obvious differences in hardware, let me know if 1560MHz is not for O2x, many people love it on G2x, i can drop to 1540MHz or lower for stability (yes, that 20mhz difference might be all it needs)
1.6GHz is not stable, and i am not ready to further up the voltage as the voltage would go in the "are you serious to run this much voltage?" territory.
the more voltage you pump in, the more DTT will throttle the chip.
let the feedback roll in
and if you do not run cm7, let me know which kang or miui you run (kernel runs fine with whitehawkx's miui on G2x)
This kernel is not for any roms based on stock 2.3.3 gingerbread.
It works so far but why cant we modify the voltage though pimp my cpu or setcpu?
fry92 said:
It works so far but why cant we modify the voltage though pimp my cpu or setcpu?
Click to expand...
Click to collapse
it's disabled for testing
for T15 i can enable it later
for ELP it will stay off, there is not really any headroom to go any lower than it is.
kernels are meant to be flashed and then you forget about them and go on and use your phone, this holds particularly true on the 1.0GHz undervolted version.
The T15 could benefit from finding the lowest stable settings on each individual phone.
I had another SOD. If it is related with the 216 Mhz min frequenzy, you should check the source of vorkkernel (that kernel runs perfectly at 216 Mhz, but just can not compete with your kernel elp performance wise).
Going to try your 1.5 Ghz...
Thx
Sent from my Optimus 2X using XDA App
I tried the 1,5ghz and it seems to be stable for me. I ran a couple benchmarks and surfed a few websites and no crashes, lags or whatever.
Sent from my Optimus 2X using Tapatalk
Hi, installed and works ok.
One problem: when the screen Goes off during à Call.
And you leave it off for About 20 seconds, then It isn't possible anymore to get the screen on again.
Only way to get the screen on again is to pull the battery.
To be sure it is THE kernel That causes this, i tried vorkkernel and the problem doesn't occur using The vorkkernel.
Btw: i only use basesband 502; THE only baseband that gives good Callas quality.
jan1000 said:
Hi, installed and works ok.
One problem: when the screen Goes off during à Call.
And you leave it off for About 20 seconds, then It isn't possible anymore to get the screen on again.
Only way to get the screen on again is to pull the battery.
To be sure it is THE kernel That causes this, i tried vorkkernel and the problem doesn't occur using The vorkkernel.
Btw: i only use basesband 502; THE only baseband that gives good Callas quality.
Click to expand...
Click to collapse
Thanks, I look at proximity stuff.
Vork's kernel should perform very similarly on purely performance side of things.
We ended up sharing ideas.
So the other comment about it being smoother than vork is surprising and intriguing to be honest.
I enjoy building kernels, and since I had 'elp' built already wanted feedback, that comment I didn't expect.
Sent from my A501 using Tapatalk
jan1000 said:
Hi, installed and works ok.
One problem: when the screen Goes off during à Call.
And you leave it off for About 20 seconds, then It isn't possible anymore to get the screen on again.
Only way to get the screen on again is to pull the battery.
To be sure it is THE kernel That causes this, i tried vorkkernel and the problem doesn't occur using The vorkkernel.
Btw: i only use basesband 502; THE only baseband that gives good Callas quality.
Click to expand...
Click to collapse
Strange, I had the same screen blanking issue with CM7 Kang I built 2 days back. Doubt if it kernel related or common to both.
hackworks said:
Strange, I had the same screen blanking issue with CM7 Kang I built 2 days back. Doubt if it kernel related or common to both.
Click to expand...
Click to collapse
Hm, that will make it harder to track.
For one I need to change my G2x / O2x to 'anykernel' ....before vork spanks me for not using it.
I pulled this ramdisk 4 days ago.
Doing this w/o phone at hand I'll be better of using 'anykernel' then.
Sent from my A501 using Tapatalk
Hey, just wanted to report another SoD after i hung up on a call. Those are the only SoD i get, but i get it pretty much after every call.
Never happens on Vork's kernel or the stock cm7 kernel.
I am running the ELP kernel.
Hope I could help.
i'm testing the T15 on latest miui and seems all ok....just a note ,the battery consumption seems to much high....
Related
http://board.teamwhiskey.com/viewtopic.php?f=3&t=53&start=0
Project is simple in design and is a work in progress, overclock as far as we can go with ample supplied voltage for maximum stability. These are the screenshots taken last night from the last few builds of the evening, were up to something like 40 builds so far trying to get everything just the way we want it to run, look, and feel.
Currently we are overclocking both the GPU and CPU using both base frequency modifiers and multipliers. This is allowing us to directly push the GPU to its stable limit while adjusting out the CPU accordingly.
Project Developers
Morfic and Viralblack of Team Whiskey. This is and will continue to be Morfic's baby until the phone prints money and/or can transform into a jet.
The Short and Long term goals are the following:
-To optimize the kernel with the best toolchains available to us
-Inject vital code enhancements for stability and to extend the feature set of the SGS Vibrant line
-To determine Min/Max Voltage, Bus Clock, and Multiplier values for Maximum Overclock and Maximum Effecient Overclock
-Continue to push the GPU to its theoretical maximum independant of CPU clock values.
Target Numbers and Current Results.
CPU Target 2.0GHz, Current Maximum Overclock 1.6 Stable (Time limitation only, havent rebuilt to try more)
GPU Target 85 FPS Stable Bench, Current 78 FPS
At current this is a JFD Stable build thats more than fairly bulletproof on battery life. To use with JI6 builds just flash Eugene's JFD/JI6 support package.
{
"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"
}
This is NOT a hoax or scam, these are real DDMS screenshots from the build currently in progress, as it has not yet been released we do not have code or kernels available until we know its running smoothly. The following zImage is a prerelease alpha. Its strictly for proof of concept. This kernel is mildly optimized and includes the CPU and GPU overclocks. In three of three test phones the CPU was stable, in two of three phones the GPU was stable. One test phone was not able to complete neocore under this coding.
Battery life has proven about the same as traditional OC/UV kernels. This is NOT our finished product, this is an Alpha for proof of concept for other developers. Run at your own risk. There is no failsafe, this does not require SetCPU to engage. It comes out of the box at 1.6GHz with steppings of 1,2,4,8,16
Currently, tested incorporations with the zMod have shown that overclocking renders the zMod unstable and bricks the device. I personally preferred to use RyanZAs OCLF v2.2 APK.
I had one out of 20 quadrant runs fail because I switched scheduler away from deadline. CFQ proved to be less stable for one reason or another when running quadrant.
This thread will be updated as work progresses, Do not flash this if you do not know what youre doing. Suggestions are welcome for integrated features you would like to see in this kernel, we will not however be fielding bug reports as this right now is staged as a Prerelease Alpha or RC0.
If when this is flashed your phone crashes and is unable to work, my suggestion is odin the stock kernel back in place and wait for a lighter overclock version to be released.
Download -
Removed while core is being rewritten
EDIT 10/28:
To update the project and to iterate why the download link was removed, the kernel seems to be misbehaving and we havent yet nailed down the correction as of yet.
As many people pointed out once it was released, the kernel seems to slow down 3D graphics. With this information and taking a day to go through all the options and data available to me, we discovered this issue isnt limited to just 3D graphics.
Imagine if you were running at 10MPH, and while you were running time slowed down but the slowdown didnt effect you. So youre still running at 10MPH but to the rest of the slowed down world, now youre running at 15MPH, even though your speed and direction havent changed.
The changes in the code for one reason or another arent playing nice with the Android system. Instead of pushing the clock up, in most cases, what its doing is simply slowing the internal clock down to the tune of about 30%. This is what is actually providing the benchmark gains that were being recorded, not an actual gain. This doesnt mean that the project is dead, we are recompiling to get a stable overclock with the new configurations. This doesnt mean the project was a failure, it just means we need to rewrite the alpha.
Edit 10/30 -
So, we are having distinct issues removing the timing error from the kernel while maintaining the integrity of the time system. So, being that the timing is much more important, we began rewriting it all from scratch. This is currently marked as Project Core in the same forums. Core is taking the best of the overclocking and fine tuning that this kernel has and combining it with energy effeciency and stability a daily driver phone needs.
So, we will be balencing the high end power thats desired and the low power use that is needed in this new project. With that being said, I dont believe that 1.6GHz (in my own humble opinion) is even remotely necessary for 99 percent of phone, let alone for daily use. This project is being succeeded by Core to make a power friendly daily driver kernel.
The kernel will still be available from the forums Alpha/Beta Download Section, but will not be supported as its being replaced by Core.
We found the redline Now we need to find the happy medium. If you enjoyed this release, youll love Core and Core with zMod.
Thread Locked until release, OP PM me when you want to release it
Good work TW
You guys should start working on a 2.2 version (Once you get this one smooth)
Thanks, but....
The processor already gets too hot at 1ghz.
I don't feel like cooking it just to say "hey wow, look how high I pushed it before it died".
Y'all really need to let people know that overclocking creates more heat and in the confined area of a tiny little cellphone there is next to zero cooling.
It's just asking for trouble.
Not that I don't appreciate the effort you guys are putting into the tweaks tho....
n2ishun said:
Thanks, but....
The processor already gets too hot at 1ghz.
I don't feel like cooking it just to say "hey wow, look how high I pushed it before it died".
Y'all really need to let people know that overclocking creates more heat and in the confined area of a tiny little cellphone there is next to zero cooling.
It's just asking for trouble.
Not that I don't appreciate the effort you guys are putting into the tweaks tho....
Click to expand...
Click to collapse
My phone never gets hot?
But they did put a warning, and you are the one modding your device.
Oh wow! This is great! I have an Epic 4g, will I be able to benefit from this awsome project?
Eazail70x7 said:
Oh wow! This is great! I have an Epic 4g, will I be able to benefit from this awsome project?
Click to expand...
Click to collapse
Hopefully yes, the kernel will be ported to all SGS Variants if possible, Right now we have in our possession Vibrants and Captivates, were looking to expand and will probably be working with other developers to get this kernel ported across.
Master™ said:
My phone never gets hot?
But they did put a warning, and you are the one modding your device.
Click to expand...
Click to collapse
Yeah, mine will get warm, but I've never seen it get real hot.
testing now . just flash with clockwork? this is super cool guys. props
blackerwater said:
testing now . just flash with clockwork?
Click to expand...
Click to collapse
Yes, its CWM flashable, but be careful with it. There is no failsafe, if your phone cant handle the overclock itll just crash as its set automatically to 1.6GHz topend
So far so good. Just got a linpack of 12.062. Outstanding job guys!
doesn't work yet. just sits on vibrant screen. its cool ill just flash back ji6 zimage then it should boot. im on stock ji6..... I have a vibrant that can handle 1.3mhz for sure and voodo so ill keep playing with it.
Will this run with stock ji6?
Thank you so much for uploading! I reread about it in phandroid and was about to ask around for it
Sent from my SGH-T959 using XDA App
I flashed again just to make sure . it wont boot on ji6 stock but my ji6 kernel works just fine. so maybe if i was running a bionix rom?
blackerwater said:
I flashed again just to make sure . it wont boot on ji6 stock but my ji6 kernel works just fine. so maybe if i was running a bionix rom?
Click to expand...
Click to collapse
Right now ive only tested it on Fusion personally
Viralblack said:
Hopefully yes, the kernel will be ported to all SGS Variants if possible, Right now we have in our possession Vibrants and Captivates, were looking to expand and will probably be working with other developers to get this kernel ported across.
Click to expand...
Click to collapse
Excellent. I hope you guys can get an Epic soon and work some magic. Also good to hear thatyou'll be working with other devs. Good luck
blackerwater said:
I flashed again just to make sure . it wont boot on ji6 stock but my ji6 kernel works just fine. so maybe if i was running a bionix rom?
Click to expand...
Click to collapse
I have stock JI6 rom but have the "backwards compatibility for JFD kernels" flashed so maybe that's it.
Have you tried flashing the back kernel support file for JI6 then flash this kernel?
Whitehawkx said:
I have stock JI6 rom but have the "backwards compatibility for JFD kernels" flashed so maybe that's it.
Click to expand...
Click to collapse
ok ill give that a shot. thanks
Will this work with voodoo?
Bionix Fusion 1.0 Jacs Xmod Oc/Uv Kernel Color fix Voodoo
It's DoW if you owned a Vibrant before, Trinity is the name in its passport though.
-------------------------------------------------------------------------------------------
Files and source:
www . Der Kernel . com
-------------------------------------------------------------------------------------------
ICS:
Voodoo Sound V10 (Thanks supercurio)
Trinity Spice (based on voodoo color V1 by supercurio)
BLN (Backlight notification) (Big Thanks Neldar)
Backlight dimmer by Ezekeel
Based on Samsung git source.
Safeboot to lower clock, higher need a tool like setcpu or no-frills CPU control
New Trinity bootanimation by @rascarlo
TUN module (Tunneling/VPN support)
CIFS module (Samba support)
EXT4 tweaks
Most lean build achievable.
Not a rebooter.
JB: WIP
For CM, to use this kernel flash the CM Black Screen Fix (Thanks JackpotClavin and lurtis)
Thanks to @RyanMacG for euroskank hosting
When "Just Flash It" didn't work:
Flash rom.
Flash kernel.
Power off.
Pull battery for 2 minutes.
Put battery back
Now boot phone.
---------------------------------------------------------------------------------------
GPS woes? Try this .apk, worked wonders on GB.
Endursa shared this GL fixing link. Follow it, see 65fps on Quadrant planet like it was meant to be.
T for Trinity
UV for undervolt (you would want to uninstall setcpu like apps and just run it)
EUV represents a 880MHz top speed power savings kernel, snappy still? You Bet'cha!
144 for 1.44GHz (I will rethink this when the 10GHz phones hit the market)
-Any means it uses Koush's anykernel scripting to install trinity using the original ramdisk, making it possible to use it on m(any) roms w/o needing a special version.
(X)A new kernel just born by my slacker hands, feel free to use it, we think it's good even if it was eXperimental just moments ago. (X) comes off when we feel it's a daily driver.
maybe i need this later
Hmmm, interesting :3
I'll test it right now
edit: Freeze after playing games or using the 3d drawer
dario3040 said:
Hmmm, interesting :3
I'll test it right now
edit: Freeze after playing games or using the 3d drawer
Click to expand...
Click to collapse
Launcher Pro? Or do you mean adw's 4D?
Sent from my Nexus S
morfic said:
Launcher Pro? Or do you mean adw's 4D?
Sent from my Nexus S
Click to expand...
Click to collapse
Google's stock android 2.2/2.3 launcher.
{
"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"
}
Yea I will say this is the fastest kernel I have ever used, scored averaging 3700, best being almost 4000...Solid work morfic.
adewey234 said:
Yea I will say this is the fastest kernel I have ever used, scored averaging 3700, best being almost 4000...Solid work morfic.
Click to expand...
Click to collapse
Thanks for some positive feedback.
This is the longest tested of all kernels I built.
Simms22 is not much of a tester, his phone runs about any crazy oc and uv I throw at it, so I added time to testing it
Unfortunately no oc kernel will ever run stable on all phones, if they did, samsung would charge us for that.
Sent from my Nexus S
morfic said:
Thanks for some positive feedback.
This is the longest tested of all kernels I built.
Simms22 is not much of a tester, his phone runs about any crazy oc and uv I throw at it, so I added time to testing it
Unfortunately no oc kernel will ever run stable on all phones, if they did, samsung would charge us for that.
Sent from my Nexus S
Click to expand...
Click to collapse
Unfortunately not stable on my device. Ran a couple of quadrants (4015) but froze during smartbench.
morfic said:
Thanks for some positive feedback.
This is the longest tested of all kernels I built.
Simms22 is not much of a tester, his phone runs about any crazy oc and uv I throw at it, so I added time to testing it
Unfortunately no oc kernel will ever run stable on all phones, if they did, samsung would charge us for that.
Sent from my Nexus S
Click to expand...
Click to collapse
Naw it runs 100% on full OC 1440. I only have issues with radio occassionally, but thats because i cant make up my mind which is better, KB1 or KB3. But yea, mos def a daily driver. Ive drained my battery in 1/3 of the time i usually do, playing with my phone so much. Much appreciated sir, if you need more experienced feedback, let me know, I've done some work with android, just dont have the time as of late, but logcats etc are easy and not that taxing on my time
morfic said:
Thanks for some positive feedback.
This is the longest tested of all kernels I built.
Simms22 is not much of a tester, his phone runs about any crazy oc and uv I throw at it, so I added time to testing it
Unfortunately no oc kernel will ever run stable on all phones, if they did, samsung would charge us for that.
Click to expand...
Click to collapse
except for that damned 1.7ghz kernel. one of these days..
jlevy73 said:
Unfortunately not stable on my device. Ran a couple of quadrants (4015) but froze during smartbench.
Click to expand...
Click to collapse
the phone commited murphacide
adewey234 said:
Naw it runs 100% on full OC 1440. I only have issues with radio occassionally, but thats because i cant make up my mind which is better, KB1 or KB3. But yea, mos def a daily driver. Ive drained my battery in 1/3 of the time i usually do, playing with my phone so much. Much appreciated sir, if you need more experienced feedback, let me know, I've done some work with android, just dont have the time as of late, but logcats etc are easy and not that taxing on my time
Click to expand...
Click to collapse
i used(on uv now, will use again) this kernel, as a daily driver, longer than any other. it definitely deserves respect. btw, i use KB1, and also had a hard time decided which radio i liked best
Hey Morfic, I have a question, when you were applying the patches for the kernels with BFS, were you using this file or a different one? 2.6.37-sched-bfs-363.patch
adewey234 said:
Hey Morfic, I have a question, when you were applying the patches for the kernels with BFS, were you using this file or a different one? 2.6.37-sched-bfs-363.patch
Click to expand...
Click to collapse
359 and later 363, but been a while.
Curious to see if superuser still hangs in "VM_WAIT" with 363 now or not.
Sent from my Nexus S
Mine was stable at 1.4ghz, but crashing constantly at 1.44ghz.
terryhau said:
Mine was stable at 1.4ghz, but crashing constantly at 1.44ghz.
Click to expand...
Click to collapse
Exactly the same issue I had.
How can you guys get almost 4000 in quadrant scores.
The maximum I got w/ this kernel was 3100, for me the phone is reallly fast but if you have more I want this more that I don't have.
Thanks,
liquelt said:
How can you guys get almost 4000 in quadrant scores.
The maximum I got w/ this kernel was 3100, for me the phone is reallly fast but if you have more I want this more that I don't have.
Thanks,
Click to expand...
Click to collapse
set your cpu to 1440/1440, then test 4 times in a row. the 1st is always much lower then the rest. the 3rd or 4th test should be more accurate.
First - 3091
Second - 3247
Third - 3770
Forth - 3813
Fifth - 3591
So here is my results, thanks for this FANTASTIC KERNEL.
liquelt said:
First - 3091
Second - 3247
Third - 3770
Forth - 3813
Fifth - 3591
So here is my results, thanks for this FANTASTIC KERNEL.
Click to expand...
Click to collapse
there you go, good ole #4
@800MHZ is the voltage the same or lower than 1GZ?
Howdy,
I've been using the CM7 nightly builds for a while now and figured it'd be nice to have a kernel that's based on CM7 with overclocking, RAM hack and couple of other tweaks. This kernel is pretty similar to the volkKernel but I wanted to have my own
Changes:
* Overclocking up to 1500 mhz (only through pimp my cpu at the moment)
* Default I/O scheduler of NOOP
I'll try to keep it up to date with the latest CM7 kernel sources.
[Releases]
Third release based on nightly #114
http://www.mediafire.com/?r57gqyuvhujwk6g
Second release based on nightly #101
* Removed RAM hack
* Balanced out the CPU clock values a little bit
http://www.mediafire.com/?1waipap3c71hat3
Initial release based on nightly #79
http://www.mediafire.com/file/w3e0s3vxwtznclz/cm7_79.zip
very nice welcome on board ^^
fallout0 said:
Howdy,
* Overclocking up to 1500 mhz (only through pimp my cpu at the moment)
Click to expand...
Click to collapse
Can't use setcpu?
i would like to use OC via CMParts ^^
Hmmm pardon me for asking, but why is it a 32mb RAM hack now instead of 64mb? Is it to resolve the gallery bugs?
I am using the original cpujauste o/c code that's why it only works with pimp my CPU. ill look into the others tomorrow to get that working
The 64mb hack caused issues for people with 1080p recording and the gallery. ill try it again and see how it works
ok, i found some bugs.
1. Reboot doesn't work. I guess thats because of the 32MB Ram Hack (for the vorkkernal, reboot doesn't work either)
2. After running a couple of hours, you only get around 50% of your CPU performance. Maybe the scheduler isn't optimized well. I recognized it by playing n64oid and it has lagged. Also I only get 3900 points at Antutu instead of ~5000 points.
ranrick said:
ok, i found some bugs.
1. Reboot doesn't work. I guess thats because of the 32MB Ram Hack (for the vorkkernal, reboot doesn't work either)
2. After running a couple of hours, you only get around 50% of your CPU performance. Maybe the scheduler isn't optimized well. I recognized it by playing n64oid and it has lagged. Also I only get 3900 points at Antutu instead of ~5000 points.
Click to expand...
Click to collapse
I think it's actually booting at ~700mhz by default so unless you set it up in pimp my cpu it'll stay at ~700 mhz. Probably why it's lagging.
We need more people working on kernels, thanks for doing so. Any improvements on battery life? Personally I find CM7 battery life to be pretty bad.
fallout0 said:
I think it's actually booting at ~700mhz by default so unless you set it up in pimp my cpu it'll stay at ~700 mhz. Probably why it's lagging.
Click to expand...
Click to collapse
Yep, now running with 1ghz again ^^
Can i request Voodoo Sound support?
Hey fallout0,
Nice work mate.
I think the general consensus is to not have the 64mb hack in kernels judging from a couple of poles about only 20% wanting the hack, probably less now.
I prefer to not have the hack at all imho, far too many instabilities for zero gain that being said I have yet to find a completely stable o/c kernel to use - stock seems to be the only completely stable kernel.
Be trying yours later on today so keep up the good work!
-smc
somemadcaaant said:
Hey fallout0,
Nice work mate.
I think the general consensus is to not have the 64mb hack in kernels judging from a couple of poles about only 20% wanting the hack, probably less now.
I prefer to not have the hack at all imho, far too many instabilities for zero gain that being said I have yet to find a completely stable o/c kernel to use - stock seems to be the only completely stable kernel.
Be trying yours later on today so keep up the good work!
-smc
Click to expand...
Click to collapse
Hey
Cheers
The ram hack and even overclocking support are pretty nasty hacks. Having said that I like the ability of adjusting voltages/maximum frequencies and until there is a better solution I think it's worth having this one
I agree about the RAM hack. I tried volkKernel and besides the reboot issue I didn't have any problems with the 32mb RAM hack. However the extra 32mb of RAM might not even be that useful.
I'll see how things pan out with this one then remove/add things as people complain
fallout0 said:
Hey
Cheers
The ram hack and even overclocking support are pretty nasty hacks. Having said that I like the ability of adjusting voltages/maximum frequencies and until there is a better solution I think it's worth having this one
I agree about the RAM hack. I tried volkKernel and besides the reboot issue I didn't have any problems with the 32mb RAM hack. However the extra 32mb of RAM might not even be that useful.
I'll see how things pan out with this one then remove/add things as people complain
Click to expand...
Click to collapse
Can't the reboot issue be easily resolved? According to RC, the bootloader expects the reboot-information to be at 128MB + 11 bytes, while the system writes it to [MB Reserved for Graphics]+11 bytes. As long as no ram-hack is applied, it'll of course be in the right place. Shouldn't it be easy for a kernel to just copy what is at [MB RESERVED]+11 to [128MB]+11 before shutdown?
Just talking by the seat of my pants here, haven't looked at any of the sourcecode, but it certainly feels feasible.
::Trym
I wish for that kernal:
- option on 32mb hack
- AVP/SD ram OC
- CMPart OC settings
thats it ^^
He-hey!))) This kernel is almost burnt my phone off.... Came upstairs after the dinner and found the phone off and very-very hooot... So, now I'm waiting for it to cool down a bit... Hope it'll turn on again)))
Update: Thank God that it didn't turn into BRICK))) Came on again and I've flashed it back to vorkkernel.
I am using MIUI ROM.
Very good works!! I have now tested with CM7 ROM "nightly full-77" version.
Fantastic Quadrant Score!!!
{
"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"
}
TrymHansen said:
Can't the reboot issue be easily resolved? According to RC, the bootloader expects the reboot-information to be at 128MB + 11 bytes, while the system writes it to [MB Reserved for Graphics]+11 bytes. As long as no ram-hack is applied, it'll of course be in the right place. Shouldn't it be easy for a kernel to just copy what is at [MB RESERVED]+11 to [128MB]+11 before shutdown?
Just talking by the seat of my pants here, haven't looked at any of the sourcecode, but it certainly feels feasible.
::Trym
Click to expand...
Click to collapse
I thought about it, and decided against it. Writing random information into active RAM is never a good idea.
so far so good with this kernel on RC1...
we want more OC !!!
moooooooore!
Hi guys,
I think I am at the point in my ownage of the incredible s where I am about ready to launch it off the wall as its driving me mad. It seems to work ok for a little bit then gradually lags and lags and lags until its almost unresponsive. Rebooting the phone just seems to make it go weird, with the gallery losing all the photos/videos etc and requiring a rescan to show everything back where it should be. Apps become so slow that i dont use them (worst of which is Songpop) and im now at the end of my tether.
Is this a common theme with this phone? It is currently unrooted, with the stock 4.0.4 android, and sense 3.6. would rooting it and putting a new rom on solve this?
cheers everyone
Ray
labpedro said:
Hi guys,
I think I am at the point in my ownage of the incredible s where I am about ready to launch it off the wall as its driving me mad. It seems to work ok for a little bit then gradually lags and lags and lags until its almost unresponsive. Rebooting the phone just seems to make it go weird, with the gallery losing all the photos/videos etc and requiring a rescan to show everything back where it should be. Apps become so slow that i dont use them (worst of which is Songpop) and im now at the end of my tether.
Is this a common theme with this phone? It is currently unrooted, with the stock 4.0.4 android, and sense 3.6. would rooting it and putting a new rom on solve this?
cheers everyone
Ray
Click to expand...
Click to collapse
It should. The stock sense ROM was quite bloated and slow. In comparison, even optimized sense stock based ROMs like blackout ICS run circles around stock. A new kernel will do a good job too
I had major slowdowns on stock but on blackout ICS (which is probably the stockest sense ROM I can recommend) everytnkngs much better
That's my opinion on it
Sent from my Nexus 7 using the xda app
markj338 said:
It should. The stock sense ROM was quite bloated and slow. In comparison, even optimized sense stock based ROMs like blackout ICS run circles around stock. A new kernel will do a good job too
I had major slowdowns on stock but on blackout ICS (which is probably the stockest sense ROM I can recommend) everytnkngs much better
That's my opinion on it
Sent from my Nexus 7 using the xda app
Click to expand...
Click to collapse
Cheers Mark, I'll have a look at rooting and see what happens
Ray
labpedro said:
Hi guys,
I think I am at the point in my ownage of the incredible s where I am about ready to launch it off the wall as its driving me mad. It seems to work ok for a little bit then gradually lags and lags and lags until its almost unresponsive. Rebooting the phone just seems to make it go weird, with the gallery losing all the photos/videos etc and requiring a rescan to show everything back where it should be. Apps become so slow that i dont use them (worst of which is Songpop) and im now at the end of my tether.
Is this a common theme with this phone? It is currently unrooted, with the stock 4.0.4 android, and sense 3.6. would rooting it and putting a new rom on solve this?
cheers everyone
Ray
Click to expand...
Click to collapse
A factory reset could already get it better ( don't forget to backup important data like contacts ) but if you install a custom ROM you will be able to get the best result for the reasons stated in previous post
Sent from my Incredible S using xda app-developers app
well, I did a factory reset on sunday and its running a lot better with no huge slowdowns (yet). I did look at the guides for rooting/s-offing the inc s however whilst I am not a n00b, and consider myself to be proficient in most things, the guide has me baffled as to what to do.
Ah well, looks like im stuck with stock for now
labpedro said:
well, I did a factory reset on sunday and its running a lot better with no huge slowdowns (yet). I did look at the guides for rooting/s-offing the inc s however whilst I am not a n00b, and consider myself to be proficient in most things, the guide has me baffled as to what to do.
Ah well, looks like im stuck with stock for now
Click to expand...
Click to collapse
try bootloader unlock. its easier and you just have to remember to fastboot flash the boot.img after a rom flash my inc s absolutely speeds on a custom rom but now i use my gs3 as my main device and my inc s is a lag piece of crap compared to that thing quad core <333
poondog said:
It should. The stock sense ROM was quite bloated and slow. In comparison, even optimized sense stock based ROMs like blackout ICS run circles around stock. A new kernel will do a good job too
I had major slowdowns on stock but on blackout ICS (which is probably the stockest sense ROM I can recommend) everytnkngs much better
That's my opinion on it
Sent from my Nexus 7 using the xda app
Click to expand...
Click to collapse
Hello poondog. I have no permitted to post to development-related forums.
I use Kangaroo Kernel r8, and I overclock to 1.497Ghz,then it stuck;after reboot, I oc to 1.2Ghz, and then it also stuck.
I changed the vdd_level but the problem not solved.
But I use redux 0.8 kernel and oc to 1.497Ghz with default vdd_level, it's works fine, no stuck.
Any idea with this problem?
Volftooth said:
Hello poondog. I have no permitted to post to development-related forums.
I use Kangaroo Kernel r8, and I overclock to 1.497Ghz,then it stuck;after reboot, I oc to 1.2Ghz, and then it also stuck.
I changed the vdd_level but the problem not solved.
But I use redux 0.8 kernel and oc to 1.497Ghz with default vdd_level, it's works fine, no stuck.
Any idea with this problem?
Click to expand...
Click to collapse
Hi
Yeah something is messed up in the acpu table, szezso also had the same as me and he reverted it. I think I will do the same
Its not your fault its mine, ever since I changed stuff in the acpu table from 3.4
Next release will have it fixed, thanks for your interest
poondog said:
Hi
Yeah something is messed up in the acpu table, szezso also had the same as me and he reverted it. I think I will do the same
Its not your fault its mine, ever since I changed stuff in the acpu table from 3.4
Next release will have it fixed, thanks for your interest
Click to expand...
Click to collapse
Thanks for your reply.
I will waiting for your next release.
Volftooth said:
Thanks for your reply.
I will waiting for your next release.
Click to expand...
Click to collapse
No problem I am doing it now
poondog said:
No problem I am doing it now
Click to expand...
Click to collapse
You are so fast!!
I tried the newest r9 kernel.oc cpu to 1.2GHz 1.4GHz works fine, up to 1.497Ghz it stuck.
And I guess you might missing 184320 and 192000 in freq table.
because I see them in CPU Voltages list use Trickster MOD, and I not see them in OC options drop-list when I tap it.
{
"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"
}
Waiting for your answer.
ps: 2 posts left I can post to the development-related forums
sorry for op I borrowed your thread
Volftooth said:
You are so fast!!
I tried the newest r9 kernel.oc cpu to 1.2GHz 1.4GHz works fine, up to 1.497Ghz it stuck.
And I guess you might missing 184320 and 192000 in freq table.
because I see them in CPU Voltages list use Trickster MOD, and I not see them in OC options drop-list when I tap it.
Waiting for your answer.
ps: 2 posts left I can post to the development-related forums
sorry for op I borrowed your thread
Click to expand...
Click to collapse
Nearly there
Must be the voltages don't like your device. (too low)
Because it works fine on my phone :thumbup:
Even 2GHz works
I do not have 184 or 192 cause imo it doesn't need them, they are too close to 122 and 245. Too many frequences close together is not always good, especially for some governors
Try this: Boot the phone again to default settings, go to voltages, bump them all up by like 50 or 100 and then try set it to 1.5
poondog said:
Nearly there
Must be the voltages don't like your device. (too low)
Because it works fine on my phone :thumbup:
Even 2GHz works
I do not have 184 or 192 cause imo it doesn't need them, they are too close to 122 and 245. Too many frequences close together is not always good, especially for some governors
Try this: Boot the phone again to default settings, go to voltages, bump them all up by like 50 or 100 and then try set it to 1.5
Click to expand...
Click to collapse
You are right! I bump up by 50 and it works.The voltage on 1497600 now is 1300.
But I have a qustion: I used Redux 0.8 kernel before, and I adjust the voltage on 1497600 is 1200, it works fine.
why kangaroo r9 can not running on 1497600 by voltages 1200 ?
Volftooth said:
You are right! I bump up by 50 and it works.The voltage on 1497600 now is 1300.
But I have a qustion: I used Redux 0.8 kernel before, and I adjust the voltage on 1497600 is 1200, it works fine.
why kangaroo r9 can not running on 1497600 by voltages 1200 ?
Click to expand...
Click to collapse
Not entirely sure, it might be a combination of a lot of things. Kangaroo and Redux are two entirely different beasts
Hello everyone...i know we all share the same question...which kernel is better in terms of battery...so i decide (I had done this before but an admin lock the threat) but i decide to do it again..cause i really want this anwer, at least a part of it, to be answered...so i decide to stick with one rom, difficult don't try this, and simply flash all available kernels there is out there...run AnTuTu battery benchmark and compare the results
Im not so good with words so here it goes...
Rom Aokp Preview...I know all you start saying that this is a preview rom i should test this with a more stable rom...but all i want is to test the kernel it self...not the rom...so none or if a bit of rom bugs/drains will cause this test to fail cause i didnt use the phone at all, the whole 2 hours of the benchmark...
All my apps..i have at least Android is upgrating said 150 apps Titanium sais 98 without the system...i want to see the kernel working at a normal setup...maybe its nothing but who knows...
Wifi on 3G off...as i said i want this to be run at normal usage..we all have wifi open if not 100% 85% of our usage...
And for the end...i left all kernel settings pure default...i dont use FKU,Fauxclock,Semamanager or not even Trickster...if a dev as for example @morfic wants Trinity to work 2cores its fine by me...I didnt change nothing no UV no OC no UC no nothing....
The test needs 100% battery to run...of course..and a straight 2H and some minutes depenting on kernel to run from 100% to 73% to 46% and finaly to 19% by mesuring the time it took it to drain all this juice we found the drain per minute that we need to compare our kernels...
Test also mesures battery temp..so we mesure average battery temp...i have cpu temp widget but i can't stare the screen all this hours to check the temp when a sertane percedance is reached...also...for those who wanter why i haven't test francos yet...i also said this to @franciscofranco on google+ at 85%+- of the test i notice that the cpu gets really hot..im talking about 86C so the test stops..i manage to test it once by leaving my phone to my floor that cold but i mistakanly forgot 3G on and the test finish on 40minutes!
Anyway..here is my spreadsheet feel free to comment if i made something wrong specially on sums..and on the attachments i will add 3 pics of each kernel showing the end screen of the test,the rating of the test and the drain line on settings...
26/09/13:I decide to enable UnderVolt to the kernels from here and on...Matrix 11 just like franco...and semaphone for some strange reason don't have a proper thermal throtle...at 86C the test just stops...so im hopping i can keep it below that temp to be able to run the test!!
Thanks and remember this is just benchmark..feel free to test kernels yourself to see which one fits you best...and sorry that i kill your language!!
Next kernel: Bricked
21/09/13 Base rom changed to PSX....all kernels will be re-tested...sorry for the delay...
22/09/13:Finish benchmark for Faux123 26m
23/09/13:Finish benchmark for Trinity T4h
24/09/13:Finish benchmark for Stock 4.3
25/09/13:Finish benchmark for Franco 184*Retest needed
26/09/13:Finish benchmark for Matrix 11**-112mV enabled
26/09/13:Finish benchmark for Sema 1.6.5**-100mV enabled
27/09/13:Finish benchmark for AK 25+
28/09/13:Finish benchmark for NEO 12**-112mV enabled
28/09/13:Finish benchmark for Hells-core B38**-125mV enabled
29/09/13:Finish benchmark for Franco r184**-125mV enabled
30/09/13:Finish benchmark for Reborn90 r184**-125mV enabled
1/10/13:Finish benchmark for Bricked 20/9**-125mV enabled
{
"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"
}
Wow I can already tell this is going to be very useful and answer a lot of questions, thanks in advance for this!!
a thought maybe.. how about adding the default nexus 4 android kernel to the graph? it would make the comparison more interesting
I think this is very utility, wating for franco kernel.
Wow OP.. By any chance after these test could you use the best kernel out of these test and also do a analysis on the radios of mako. I think 3g test can predict the difference on battery drain using each one of them.
simms22 said:
a thought maybe.. how about adding the default nexus 4 android kernel to the graph? it would make the comparison more interesting
Click to expand...
Click to collapse
I could use the stock 4.3 kernel to check the difference...its a good advice....
arjunv said:
Wow OP.. By any chance after these test could you use the best kernel out of these test and also do a analysis on the radios of mako. I think 3g test can predict the difference on battery drain using each one of them.
Click to expand...
Click to collapse
With 3G open the results are gonna hurt many devs...as i said the only success test with franco kernel with 3G open but not in use cause of open wifi...the test from 2.04hours of faux it goes to 40minutes with franco....im using hybrid .34 modem right now....even than im not be able to get any 4G signal... :/
Also thanks for you kind words....i thought by now the threat cause be locked by a admin like the 1st one!!
Nice thread! Will solve some general problems regarding kernels maybe.
3mperror said:
Nice thread! Will solve some general problems regarding kernels maybe.
Click to expand...
Click to collapse
As i said they are just benchmarks...its gives an idea of what each kernel can do...at least of a non stop benchmarking point of view...
I finished semaphones benchmark but after the reboot i saw that from 18% the battery goes to 36% so there is something wrong with the batterystat.bin file...so i have to redo this benchmark so i can be as accurade as i can!!!
Very usefull thread,good job
Sent from my Nexus 4 using Tapatalk 4
Correct bench of Semaphone 1.6.5 next kernel again..franco r185!!!
intresting.....
waiting for Matr1x results
Some one out there have been doing the exact same thing over the past week with me then ! hahaha - I have Carbon Rom as a base, I have had it on Franco, Faux, Sema & Matrix - All same setup, same apps, same usage - And the best results I have had so far is Carbon + Matrix Kernel. Looking forward for your experience.
Ensifolk said:
Some one out there have been doing the exact same thing over the past week with me then ! hahaha - I have Carbon Rom as a base, I have had it on Franco, Faux, Sema & Matrix - All same setup, same apps, same usage - And the best results I have had so far is Carbon + Matrix Kernel. Looking forward for your experience.
Click to expand...
Click to collapse
you didnt do trinity kernel, id consider it one of the major kernel :crying:
just teasing
did you do the stock kernel, to use as a base?
simms22 said:
you didnt do trinity kernel, id consider it one of the major kernel :crying:
just teasing
did you do the stock kernel, to use as a base?
Click to expand...
Click to collapse
Simms mate! Hehehe, first, love your pics on twitter! Second, I am still in the testing process - Gonna flash Trinity on a day I know Im gonna be on full wifi and free on time - I want the test to remain objective and under the same past conditions.
S2 has/had a similar thread. Great!
Excellent thread, I cannot wait till you finish your table, and btw, thanks for doing this man, big big help for all of us
Sent from my Nexus 4 using xda app-developers app
Thanks for all your kind words!!!
Is the antutu battery tester only causing heavy load? Because that would ignore kernel's idle drain
Also, I'd chose always the most recent kernel version to test. hellcore is at b37 right now (maybe just a typo?)
ccab said:
Is the antutu battery tester only causing heavy load? Because that would ignore kernel's idle drain
Also, I'd chose always the most recent kernel version to test. hellcore is at b37 right now (maybe just a typo?)
Click to expand...
Click to collapse
Good question !
Sent from my Nexus 4 using xda app-developers app
This is a very use full piece of work, thank you for your time, and I look forward to seeing how matrix does. one point to note as well as the comments about idle, is that different kernels behave differently sometimes depending on the ROM that they are paired with, so possibly repeating the test with a cyanogen based ROM and some 3rd ROM for all of the kernels before taking an average might be an interesting test. But of course it is up to you, I don't know how much time you have :thumbup:
Sent from my Rooted NEXUS 4