I know, tons of stuff released, some may be similar, but I've had people waiting for me to release these for some reason, so I am. Not sure what I do differently that makes people choose what I release over someone else, but here they are.
What I've done is started with the source jt1134 has provided as a base, and went from there. I haven't had time to change much else yet, but in due time, I'm hoping to have a lot of changes and updates. If you feel like supporting the development, consider signing up for Dropbox and help give me more space to store kernels.
0808
Merge pull request from Times_infinity to fix missed call problem
0804
New Kernel/Ramdisk based on ED05 sources
Updated root script to root phone on boot
Updated recovery to latest CWM
Fixed busybox issue (I think)
Voodoo Sound V10
Only one undervolt level - same as previous "100" kernel
0531
navenedrob's ext4 formatting options put into Voodoo conversion script - disable lagfix, then re-enable to take advantage of it
V(R) IO Scheduler
Fixed backup/restore/wipe errors for android_secure (I think) - thanks squash
0530
Fix mount USB Storage in recovery (Thanks times_infinity)
0529
Fix 0523
Root ROM on boot (if not already rooted)
Move files to initramfs so changes can travel between ROM Flashes
No more AOSP kernels, waiting for CM7
0523
Voodoo Sound V9
Use Linaro Toolchain to compile
Switch to bmlwrite to flash
0426
Fixed auto-brightness
0425
Voodoo Sound V8 (thanks supercurio)
Updates to initramfs to try and prevent bootloop when wiping data/cache
Update to CWM 3.x and make CWM 3.x compatible zips
0415
Simple IO Scheduler
Moved SD Card speed tweak to init.d script so users can change the value
-> Default value is 4096
Updated source to ED01 from Samsung
Built with 2010q1 toolchain, updated from 2009q3
0408
Updated initramfs from jt1134
Kernel config changes from jt1134
Voodoo sound patches from jt1134/supercurio
"Fixed" Smartass, still doesn't work properly though, set conservative back to the default
Increased voltage on 100 kernel at 1000MHz
CFS Tweaks to try and help performance some
TCP settings to help make 3G more consistent
Built AOSP kernels
0330
Smartass CPU Governor added and set as default <- not working yet
VFAT patch
Voodoo Sound mic/recording fixed and added back - thanks jt1134/supercurio
0329
Upstream EXT4 patches
Changed UV levels for greater compatibility
init.d support
SirGatez patch to force audio to headphones when they are plugged in (off by default)
-> run "headphones" from a shell prompt to enable
-> run "default" to restore normal functionality
0328
jt1134's source is the base, includes BLN, Voodoo Color, Voodoo Sound V7, Voodoo lagfix (if applicable), and anything else jt had in is source when i synced it.
Stock voltage, and undervolted kernels available
Updated CPU Scaling - keeps the processor running as slow as possible without overworking it
Updated compile flags - from Eclair, may not do anything noticeable
SirGatez's battery hack to allow for non-oem batteries
To Do:
Get 600MHz working
NOTES:
If you are experiencing problems, I need detailed info to be able to fix it or help you out. Failure to provide detailed info will mean I'm just going to ignore your problem as user error. Details would be something such as which kernel you are flashing (filename) and steps to reproduce the issue. Also, if you used any other kernels that had the same problem or didn't have the problem.
Legend
voodoo/novoodoo - voodoo has the lagfix, novoodoo doesn't (I hope this was obvious)
sv/50/100 - Undervolt level. sv = stock, 50 = 50mv off 400-1000mhz/75mv off 100-200mhz, 100mv off 400-1000mhz/125mv off 100-200mhz
Sweet thanks! I always had great luck with your kernels on Eclair. Flashing the 100 uv now.
Sent from my SCH-I500 using XDA App
Woohoo first in. Trying the 50 now.
*dammit, not first*
good day.
going to try the 100uv
I've tried probably 3-4 kernels in the past couple of days.. someone needs to make a thread up and discuss the differences.
am I correct in saying 100uv is - so far - the lowest UV kernel around?
thanks!
Woohoo 3rd. Thanks nutz
Dang. 4th.
Sent from my SCH-I500 using XDA App
Sweet
I was waiting for the imnuts kernals. Just flashed the 50, I can see the difference already! Just kidding but so far so good. Thanks!
Was I supposed to say fifth? I don't know the etiquette yet
khanable said:
am I correct in saying 100uv is - so far - the lowest UV kernel around?
Click to expand...
Click to collapse
You probably won't find a lower UV than my 100. It gets kinda useless after 100mv undervolt anyway.
ryanf said:
Woohoo 3rd. Thanks nutz
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
More like 4th
Anyone else had any luck? I can't get it to boot. I am now on my third battery pull.
Man I'm psyched to see this!!! Thank you imnuts!
Nice can't wait for aosp.
Sent from my SCH-I500 using XDA Premium App
Thanks for your work. Flashing now!
xceebeex said:
Anyone else had any luck? I can't get it to boot. I am now on my third battery pull.
Click to expand...
Click to collapse
Voodoo or novoodoo? I'm using the 100 voodoo right now and it's fine. If you're on novoodoo, you need to wait, as I mentioned in IRC shortly after posting the list as something is messed up in it that will likely cause the problem you're seeing.
imnuts said:
Voodoo or novoodoo? I'm using the 100 voodoo right now and it's fine. If you're on novoodoo, you need to wait, as I mentioned in IRC shortly after posting the list as something is messed up in it that will likely cause the problem you're seeing.
Click to expand...
Click to collapse
I am on voodoo and I am trying to use the 100 as well. It looks like it just booted, after the third battery pull. We will see how it goes.
Thanks again!
EDIT: It froze at the unlock screen, so I am trying a 4th battery pull.
https://dl-web.dropbox.com/get/Public/FamilyGuy-PeanutButterJellyTime.mp3?touch=6FiWCQ==&w=2e02a09b
Sent from my SCH-I500 using XDA App
This isn't oc'd, right?
Sent from my Froyo'd Fascinate via Tapatalk
xceebeex said:
I am on voodoo and I am trying to use the 100 as well. It looks like it just booted, after the third battery pull. We will see how it goes.
Thanks again!
EDIT: It froze at the unlock screen, so I am trying a 4th battery pull.
Click to expand...
Click to collapse
The 100 may be to much of an undervolt for your phone then, try the 50 or sv to see if you can reproduce the issue.
cpark_12 said:
This isn't oc'd, right?
Sent from my Froyo'd Fascinate via Tapatalk
Click to expand...
Click to collapse
Stock clock speeds. IMO, overclocking is useless on our phones for anything besides given you a bigger quadrant score, and it does little for actual usage.
It is definitely pretty screwed up for me. It keeps vibrating and there was no signal and nothing was working, but I was able to reboot to recovery so I am going to try flashing again and see what happens.
For those about to flash if you're using set cpu uncheck enable on boot before flashing, i've had the problem of freezing on boot before and this seemed to have solved the problem.
Dang it, I'm never gonna calibrate battery the way I'm flashing kernels the past few days...flashing now!
Sent from my SCH-I500 using XDA Premium App
Related
So I finally got the 10 posts I need to post here and for my first post I would like to ask, when are we getting Froyo for the Fascinate? I have been waiting for so long and I would like to say that I am starting to get tiJUST KIDDING
Against the backdrop of an imminent 2.2 release, I would like to share these kernels I haxed (read: kanged) together, because nobody else did and I was lazy. Based upon jt1134's recent kernel with the Voodoo sound patch that those of us with decent headphones have been having such a ball with these days, I integrated some fixes from the codebases of some of the very talented devs who are working on this phone.
Included in all of these are the Voodoo lagfix, Voodoo sound, and SirGatez's USB fix for the phone being recognized as a CD drive (also used by Adrynalyne).
Additionally, these kernels include SirGatez's fix to disable the VZW battery check, allowing batteries for the other Galaxy S phones as well as third-party batteries to charge on the Fascinate. Although it looks like for the vast majority of us with the OEM battery, nothing has changed and everything will continue to work as it has, this is untested. While the $6 battery I got from Hong Kong for the i9000 appears to charge fine, I haven't tested charging it very much yet and I must disclaim ALL RESPONSIBILITY should there be some issue with overcharging or batteries exploding. Again, this is only a concern if you are not using a Samsung-branded battery for the Fascinate. Well, the full battery popup works with the Chinese battery I have, and the phone is no longer charging it. Probably means that the fix is good for everyone with no battery explosions. Hooray! I still disclaim ALL RESPONSIBILITY as indicated above
As with all of the kernels based on jt1134's codebase, also included is the new red Voodoo-aware Clockworkmod Recovery. BLN is supported as well.
All in all, I am really happy that all these fixes from near and far work (well, AFAIK) together. I can't think of any fix/tweak that is missing, except for some of the more hardcore things like changing around the task scheduler and memory settings that don't affect day-to-day functionality of the phone as much, but are implemented by some of the real devs out there.
Update 1/31/2011: So as people have been discovering, the 7-step OC is causing some weird problems as far as call signals dropping out and various instability issues for some people, but perhaps not for others. I have spoken to SirGatez about the issue and it is a known issue with timings and such that largely boils down to faulty Samsung code (instead of waiting for a reply when using I2C to talk to peripherals as should be the case, Samsung likes to just shove more data down the pipe, or something like that). Luckily SirGatez seems to know his **** and has almost fixed the issue already in his codebase. As it turns out, although he is on a slightly newer codebase than pretty much everyone else still building DJ05/DL09 kernels (Linux 2.26.9.6 as opposed to 2.26.9, IIRC), the fact that the exact same issues showed up in my kernel and his with the 7-step OC helps him narrow his search considerably. Glad it helped, SirGatez.
For the moment, I would not recommend flashing an OC kernel - I've gone back to 1GHz myself because of the problems. I will see if his fixes are amenable to inclusion into my source tree with the view of releasing a new batch of kernels at some point in the near future.
Frankenkernel download links: (Voodoo only!)
1000MHz, 100% stock (standard) voltage settings: dropbox
1000MHz, Adrynalyne's more aggressive undervolt settings: dropbox
1200MHz, SirGatez's regular 7-speed OC settings: dropbox
1200MHz, SirGatez's undervolted OC settings: dropbox
It bears repeating that I take no responsibility for breaking anything. That said, it should all work fine, but here is an Odin package to go back to an earlier Adrynalyne-built Voodoo kernel + recovery if something breaks working on your phone. I believe this is Test6 from his current thread. dropbox This should also be useful for your after-Odin-to-stock hijinx, if you know what you're doing.
All credit should go not to me, codestealing kanger that I am, but to jt1134, Adrynalyne, SirGatez, and the other devs and users who I either stole code from, have asked lots of annoying noob questions to, or have flashed and tested my kernel. Especially SirGatez, who is apparently a decent dev, but has been toiling away in obscurity. Thanks for getting my $6 battery working, man, come say hi to the rest of us on IRC!
"included in all of these are the Voodoo lagfix, Voodoo sound, and SirGatez's USB fix for the phone being recognized as a CD drive (also used by Adrynalyne)."
Thank you!!!
Cool stuff, thanks. I look forward to trying some of these out and seeing how they run.
quick question.
If I wanted to flash the 1200 MHz UV kernel over my current kernel (adrynalyne's 1/21 UV voodoo), would I have to do any additional steps? I mean, it should be as easy as booting into red cwm and flashing it, right? I just want to be 100% sure.
tripacer99 said:
quick question.
If I wanted to flash the 1200 MHz undervolted kernel over my current kernel (adrynalyne's 1/21 UV voodoo), would I have to do any additional steps? I mean, it should be as easy as booting into red cwm and flashing it, right? I just want to be 100% sure.
Click to expand...
Click to collapse
Yes u can just flash it
Sent from my SCH-I500 using XDA App
So far, very nice! I flashed the iv/ 1200 and its running smooth!
I really like the hack for the batteries. I use a couple on Hong Kongers and it was always a pain the rear to pull them out and charge separate.
Thanks!
Sent from my SCH-I500 using XDA App
tapout27 said:
Yes u can just flash it
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Thanks!
btw, the 1200 UV kernel is running great and smooth! Voodoo sound is nice addition too.
Is the uv 1200 kernel also a 7 slot?
Also, if not already done can you upgrade this to BLN 2.3+? It adds blinking capability in BLN control and the newest blinky.
Sent from my SCH-I500
n0yd said:
Is the uv 1200 kernel also a 7 slot?
Also, if not already done can you upgrade this to BLN 2.3+? It adds blinking capability in BLN control and the newest blinky.
Click to expand...
Click to collapse
Yes, it's a 7-slot.
I'm not sure if it's BLN 2.3+ but I just tested on Blinky. It says the enhanced BLN is not found but blinks fine when I test it. Does that mean it's not 2.3+?
SirGatez is definitely an interesting character. Seems to be in his own little world, doing his thing.
Gps
Using adrenalyns kernel, seems to have broke gps on mine. Using super clean. 4 Dl09 with the Dl09 modem.
i know / read that the voodoo sound fix does wonders for the headphone jack listening... however, what about for bluetooth media? (not calls, but actual streaming mp3's over bluetooth to a stereo... which sucks and I want it to sound better ).
anyone that has tried it and can respond, thanks.
dnoyeb said:
i know / read that the voodoo sound fix does wonders for the headphone jack listening... however, what about for bluetooth media? (not calls, but actual streaming mp3's over bluetooth to a stereo... which sucks and I want it to sound better ).
anyone that has tried it and can respond, thanks.
Click to expand...
Click to collapse
This was the First thing I tried as I only use bluetooth headphones with my fascinate. And i can tell you that voodoo sound does nothing about the Bluetooth Audio.
I flashed this last night and was loving the battery life, but today I discovered that I couldn't make phone calls - when I click on the call button a box pops up that says I have no service. I flashed back to one of adrynalyne's test kernels and now it works. Just thought I'd let you know - other than that it was great tho, thank you!
Sent from my SCH-I500 using XDA App
Great!
Flashed the 1200 SV Kernel last night and I've been running great with no obvious glitches. GPS, phone calls, battery life all look good! Thanks!
Flashed this yesterday on top of Superh 09. Runs great with setCPU processor runs a lot cooler. Thanks!
Sent from my SCH-I500 using XDA App
Whitepaint said:
This was the First thing I tried as I only use bluetooth headphones with my fascinate. And i can tell you that voodoo sound does nothing about the Bluetooth Audio.
Click to expand...
Click to collapse
Bluetooth is something that will be looked into. Go find the sound thread in the i9000 forum to see planned features and keep track of development.
I've posted these details in SirGatez thread for his kernel, thought I'd share them here since it's also applicable.
When using your kernel with SirGatez' OC settings, the CPU throttling is really high, it likes to spend times at higher clock rates when at rest. My remedy to it was setting a minimum processor speed of 200 MHz, then the at rest throttling was SUPER TAME, giving the greatest resting battery life I've ever experienced with no performance issues at all.
BUT, sadly your kernel shares the exact same "No Service" bug that SirGatez' does, causing erratic loss of service that has to be waited out, Airplane Mode switch is frozen at this time. This sadly had me have to give up the 7-slot kernel. Otherwise, great experience.
CrushD said:
I've posted these details in SirGatez thread for his kernel, thought I'd share them here since it's also applicable.
When using your kernel with SirGatez' OC settings, the CPU throttling is really high, it likes to spend times at higher clock rates when at rest. My remedy to it was setting a minimum processor speed of 200 MHz, then the at rest throttling was SUPER TAME, giving the greatest resting battery life I've ever experienced with no performance issues at all.
BUT, sadly your kernel shares the exact same "No Service" bug that SirGatez' does, causing erratic loss of service that has to be waited out, Airplane Mode switch is frozen at this time. This sadly had me have to give up the 7-slot kernel. Otherwise, great experience.
Click to expand...
Click to collapse
That's what I had - a "No Service" bug. Glad I am not alone on this one, I was really puzzled when I saw that pop up!
Sent from my SCH-I500 using XDA App
I want to flash the 1200 kernel but I was wondering if there is a significant difference between the regular and uv
gonna be building some kernels - in an attempt to see what gets better battery life and/or what kills it.
it comes down to this -> this is a science experiment. everyone on XDA knows i can make a kernel out perform any other, but this is not about that. this is about battery life. so I will only add 1 thing at a time, and way 1 day between releases. I know how to fix issues with htc base, but to keep my testing valid, I will not do that. If you want performance - flash my QC kernels. if you want to help me help you, flash this and report back.
PLEASE if you flash, stay with the one you flashed for at least 24 hours and report battery life and any issues you may have.
I already did this in the past with qualcomm base as well as HTC base, but with a different compiler, and the results were BAD - so lets see how the info provided by dodava does
if your gonna flash to help provide feedback, please be on the same rom and version for ALL your tests, changing your rom between test versions can invalidate any tests.
when providing feedback - please provide the following information
1) rom name and version
2) did you FLASH anything over the rom (besides this kernel)
3) did you FLASH a kernel prior to this one (other than what came with the rom), if so, what kernel
4) did you add, modify, or delete any init.d or init.post_boot scripts
5) do you use any system tuner apps (setcpu, cpu master, system tuner pro, etc)
6) time on kernel (how long did you run this kernel)
7) battery drain over 6 hours
8) battery drain overnight
9) any issues
10) battery % at time of flash (95+ is recommended)
11) how does it perform to other kernels you tried
Report your findings here:
https://docs.google.com/spreadsheet/ccc?key=0AozA1RN8QEKydGozeHhlUGRIOVdwLXVQWkxrUjJNb0E
download link: (public - no login required) http://www.androidfilehost.com/main/EVO_3D_Developers/chad.goodman/KERNELS - XDA (PUBLIC KERNELS)/
changelogs:
please note: each build will only contain ONE update, as to isolate where battery drain is comming from. I will only release 1 update per day, to eliminate the URGE to flash before your 24 hour test is up.
Code:
Anthrax_Shooter-sense-HTCBASE-rls03
-set default min/max cpu clock, default to 1.5ghz vs max clock
Anthrax_Shooter-sense-HTCBASE-rls02-fixed
-Reduced max OC and use dodava's OV/UV values
--> this fixed reboot/noboot issue. funny how the qualcomm base can OC more than the HTC base before people have issues :(
Anthrax_Shooter-sense-HTCBASE-rls02
-add OC and fix cpu drivers (1.78) // allow for under-over volt
-adjust PERFLOCK TABLE
-remove redundant code re: cpu clock management from PowerManagement
-adjusted DEFCONFIG to allow use of PGM only because there should be NO impact to battery life or performance
Anthrax_Shooter-sense-HTCBASE-rls01
-100% stock HTC ( shooter-gb-mr-2.6.35-277012f )
-compiled with NDK 7c, toolchain 4.4.2
-patched in fastcharge from [email protected] (only added cause it will have ZERO impact on battery drain and performance)
-compile directions provided by [email protected]
-compiler version provided by [email protected]
-makefile and config files from [email protected]
-unlocked 1.5GHz
-100% default qualcomm acpuclock-8x60.c file (except the 1.5 unlock) (added so that the voltages, FSB, and L2 match whitepaper spec)
next build will include:
Code:
-optimize build to atleast -o2 and add neon (and msm8x60) specific optimizations
source (minus beats) https://github.com/ChadGoodman/anthrax_shooter_htcbase
reserved #2
First for the first time
ssojyeti2 said:
First for the first time
Click to expand...
Click to collapse
Second. will give it a shot. Thx Chad. Good to see you back on XDA - even if limited.
ssojyeti2 said:
First for the first time
Click to expand...
Click to collapse
CONGRATULATIONS!
......thanks chad
I'll try for sure....
Sent from my PG86100 using Tapatalk 2
chad i'll flash these after i finish my other test with rls04_1858
Will do
Sent from my 3D
Cool thanks
Definitely going to try one out. Chad's kernels set the bar!
So I've been running this for about 15 minutes now and the battery life is awful!
Kidding!
Looks good though chad.
Unknownforce said:
So I've been running this for about 15 minutes now and the battery life is awful!
Kidding!
Looks good though chad.
Click to expand...
Click to collapse
****, its HTC base, i wont even flash it once you go QC, you dont go back
j/k - but the QC kernels on my phone on the sony xplod rom last me all day then some... i charge every night anyway... and i use the phone a lot. gtalk is always running, etc...
I see your cat is hard at work coding. Make sure he gets tuna for this.
sent from my AnthraX infused Evo3D running Infectedrom Eternity using xda premium
chad is this the kernel that was supposed to be just like the old 2.08 rls 9???? i kno on the infected site u said u will be coming out with a kernelike the old rls 09 kernel
Y you no talk to me anymore?!
Glad to see you back. You know where I am if things get crazy..
OK lets go, gonna help out
Sent from my PG86100 using xda premium
pstevep said:
Y you no talk to me anymore?!
Glad to see you back. You know where I am if things get crazy..
Click to expand...
Click to collapse
sup boss
HI!!
thinks are always crazy
Nice to see you chad with a thread here at XDA .
evod3 said:
chad is this the kernel that was supposed to be just like the old 2.08 rls 9???? i kno on the infected site u said u will be coming out with a kernelike the old rls 09 kernel
Click to expand...
Click to collapse
no - i just got sick of people complaining of battery life, so im doing some tests so see if battery issues can be fixed
the RLS9 test is in the hands of freeza, and it didnt go as expected
full change log in OP for this one
woot, its good to see more kernels from the master him self on the site again.
Here is my project that I have been working on for a few weeks now. It is currently for Testing Only in its present condition.
My goal is to adjust the settings of the Kernel to squeeze out as much battery life as I can without sacrificing performance to our phones.
It is initially based on the DSC Kernel.
I have added I/O Schedulers as well as numerous Governors. I intend to narrow down the ones to just maybe 2 or 3 of the best ones. as well as adjust the CPU settings and speeds to give the most optimum configurations.
Here is the list so far, but will be reduced with further testing.
I/O Schedulers
cfq
deadline
noop
sio
vr
Governors
brazilianwax
conservative
interactive
interactivex
lagfree
lazy
liionheart
minmax
ondemand
performance
powersave
savagedzen
scary
smartassv2
smoothass
userspace
The biggest hurdle to get through right now, since it is my main focus, is the the screen is rotated which makes it NOT useable yet. Once I get past that, I can adjust settings and make other modifications.
Any suggestions or help will be greatly appreciated. I created a Github account and will try to figure out how to use it. I have also attached a Test5 Kernel as well as a reset Kernel.
I am reserving this section just in case I need it
Until the attachments are working again on XDA, I will post links to files shortly.
Does those kernel can patch to MIUI / Longhorn / DSC / CM ?
ps000000 said:
Does those kernel can patch to MIUI / Longhorn / DSC / CM ?
Click to expand...
Click to collapse
if i not mistaken.. the kernel is being optimized for longhorn ROM... and it is based on DSC kernel...
if my understanding is correct...
Actually it is based on the Phoenix Kernel. I intend on it it being a universal kernel. Once the base is setup and working, then I can test and tweak it further.
i have always felt droid does too much in the background causing quite an effect on battery life.
Too many processes auto loaded.
This may not be at linux kernel level, but rather above it on the droid's scheduler etc.,
Basically what i would like is to do is disable auto starting apps.
for eg., i dont want yahoo messenger ever to be in process list if i have not started it. and when killed should stay killed.
I guess that should improve the battery life quite a bit.
macexplorer said:
i have always felt droid does too much in the background causing quite an effect on battery life.
Too many processes auto loaded.
This may not be at linux kernel level, but rather above it on the droid's scheduler etc.,
Basically what i would like is to do is disable auto starting apps.
for eg., i dont want yahoo messenger ever to be in process list if i have not started it. and when killed should stay killed.
I guess that should improve the battery life quite a bit.
Click to expand...
Click to collapse
oh... we have apps called autostarts though (search for it).... but becareful... you might accidentally disabled key apps for the phone to function properly... last time i disabled so many to the point that i need to reflash the ROM back... lol.. silly me...
---------- Post added at 11:22 PM ---------- Previous post was at 11:21 PM ----------
tenorntex said:
Actually it is based on the Phoenix Kernel. I intend on it it being a universal kernel. Once the base is setup and working, then I can test and tweak it further.
Click to expand...
Click to collapse
lol... i get the feeling it is from phoenix kernel...
deysmacro said:
oh... we have apps called autostarts though (search for it)....
Click to expand...
Click to collapse
Yes. I use it in my Streak. But it kind of feels useless at times. Sometimes apps on reinstalling, get reset from autostarts..
its just no where close to 100% effective.
And it doesnt retain state. TI backup and full restore doesnt return it back to previous settings.
But actually to launch or not should be a user control, not a forced sarcastic maybe that droid is given me. Hence a deeper level of control is required.
sad to say but that how android works unfortunately... and since i cant afford iphone and also i pretty much hate symbian, well... had to stick to android at the moment.. lol...
Thanks Ten,
Do you think Bluetooth driver update?
That is a possibility. But that will be later down the road. The Kernel itself is a lot of come to go through, so baby steps right now.
Hey.!Ten just an idea .!!! Can u add drivers or edit kernel for (10 point multitouch screen)
Sent from my Dell Streak using xda premium
djmax81 said:
Hey.!Ten just an idea .!!! Can u add drivers or edit kernel for (10 point multitouch screen)
Sent from my Dell Streak using xda premium
Click to expand...
Click to collapse
10 point? wow... even to get to 5 point is quite tough... but if that even possible, i am all for it... drooling now... lol...
Yeah.!in short I meant more then 2points multitouch lol would be Nice :beer:
Sent from my Dell Streak using xda premium
I installed CM10.1 nightly on my fascinate a few days back and it has been working pretty good. I had to install a memory manager to kill tasks more often for me. Then I remembered an old app I purchased a couple years back. set cpu, I went ahead and installed that and overclocked 1200/400 and it made the phone come to life. things seem to run really smooth. Not an advertisement as much of helpful hint in case you were not aware.
Thanks for all your guys help this week setting me strait on getting my phone working.
Xceptiona1noob said:
I installed CM10.1 nightly on my fascinate a few days back and it has been working pretty good. I had to install a memory manager to kill tasks more often for me. Then I remembered an old app I purchased a couple years back. set cpu, I went ahead and installed that and overclocked 1200/400 and it made the phone come to life. things seem to run really smooth. Not an advertisement as much of helpful hint in case you were not aware.
Thanks for all your guys help this week setting me strait on getting my phone working.
Click to expand...
Click to collapse
Your not suppose to use a task killer it hurts the phone very badly if you enable KSM in performance menu and zram you will notice it works the best. And set CPU has problems with jb like it could boot loop your device its better to use the built in performance menu
Sent from my SCH-I500 using Tapatalk 2
Yes, the stock Performance menu options are your better choice for over-clocking and memory management.
If you don't see the Performance menu under system settings, you need to enable developer mode by selecting About Phone, then tapping on the android version info about a dozen times.
Regarding zram, I'll need to give it another try... Definitely go with ksm enabled.
Sent from my SCH-I500 using xda premium
The reason task-killers don't work well is because android changed the way it handles multi-tasking so that once you kill a process, it will bring it back anyway, so that if you keep trying to kill things you will actually waste more battery because it will constantly be coming back. Android is actually very good at managing memory and doesn't need your help to do it.
I only use KSM myself because I was getting lag after a while using zram, but maybe it was something I was doing wrong with the settings. My other settings as of now are Interactive governor (min 200 - max 1200) and noop scheduler.
Crawshayi said:
The reason task-killers don't work well is because android changed the way it handles multi-tasking so that once you kill a process, it will bring it back anyway, so that if you keep trying to kill things you will actually waste more battery because it will constantly be coming back. Android is actually very good at managing memory and doesn't need your help to do it.
I only use KSM myself because I was getting lag after a while using zram, but maybe it was something I was doing wrong with the settings. My other settings as of now are Interactive governor (min 200 - max 1200) and noop scheduler.
Click to expand...
Click to collapse
Noop is one of the worse schedulers not asking you to change but row an so is the best
Sent from my SCH-I500 using Tapatalk 2
bbrad said:
Noop is one of the worse schedulers not asking you to change but row an so is the best
Sent from my SCH-I500 using Tapatalk 2
Click to expand...
Click to collapse
I usually use SIO but since I'm on the default kernel it's not an option. I tried ROW for a few days but it was making my music skip sometimes for some reason (especially while mutli-tasking while playing music), and noop doesn't seem to give me as many problems like that... so I'm not really sure. CFQ didn't seem to be that great either, so I'm hoping SIO will be added soon
Crawshayi said:
I usually use SIO but since I'm on the default kernel it's not an option. I tried ROW for a few days but it was making my music skip sometimes for some reason (especially while mutli-tasking while playing music), and noop doesn't seem to give me as many problems like that... so I'm not really sure. CFQ didn't seem to be that great either, so I'm hoping SIO will be added soon
Click to expand...
Click to collapse
Sio has always been great to me even the benchmarks give me crazy scores when using sio
Sent from my SCH-I500 using Tapatalk 2
zRam seems a zero-sum gain - or worse - on this phone
Crawshayi said:
The reason task-killers don't work well is because android changed the way it handles multi-tasking so that once you kill a process, it will bring it back anyway, so that if you keep trying to kill things you will actually waste more battery because it will constantly be coming back. Android is actually very good at managing memory and doesn't need your help to do it.
I only use KSM myself because I was getting lag after a while using zram, but maybe it was something I was doing wrong with the settings. My other settings as of now are Interactive governor (min 200 - max 1200) and noop scheduler.
Click to expand...
Click to collapse
I just gave zRam a spin and experienced noticeable lag with what I do as a result. I have "Allow purging of assets" and KSM checked.
For the I/O Scheduler, ROW seems better than the CFQ I had been running. Running the interactive CPU governor. 1200/100 CPU speeds.
Seems good.
bmeek said:
I just gave zRam a spin and experienced noticeable lag with what I do as a result. I have "Allow purging of assets" and KSM checked.
For the I/O Scheduler, ROW seems better than the CFQ I had been running. Running the interactive CPU governor. 1200/100 CPU speeds.
Seems good.
Click to expand...
Click to collapse
Ditto, except with purging checked I'm pretty sure I was getting lag from that too after a while, so on mine I only left KSM on. ROW also does seem the best, however lately it seems no matter what scheduler I choose I get music that skips every couple of minutes or so, but I think that's a rom issue and not so much a scheduler issue. I've always used 200 minimum so that my phone is snappier when waking up, but that's just a personal preference.
Crawshayi said:
Ditto, except with purging checked I'm pretty sure I was getting lag from that too after a while, so on mine I only left KSM on. ROW also does seem the best, however lately it seems no matter what scheduler I choose I get music that skips every couple of minutes or so, but I think that's a rom issue and not so much a scheduler issue. I've always used 200 minimum so that my phone is snappier when waking up, but that's just a personal preference.
Click to expand...
Click to collapse
I don't get music skipping hellybelly
Sent from my SCH-I500 using Tapatalk 2
bbrad said:
I don't get music skipping hellybelly
Sent from my SCH-I500 using Tapatalk 2
Click to expand...
Click to collapse
I definitely do want to try hellybelly, but right now I just don't have the patience to set up all my apps again so maybe on my day off I'll git it a whirl. How's battery life on it?
Crawshayi said:
I definitely do want to try hellybelly, but right now I just don't have the patience to set up all my apps again so maybe on my day off I'll git it a whirl. How's battery life on it?
Click to expand...
Click to collapse
You might try a dirty flash to Helly after taking a backup (just wipe cache & Dalvik). It's based on cm10.1 so you should be all right...
Sent from my SCH-I500 using xda premium
Crawshayi said:
I definitely do want to try hellybelly, but right now I just don't have the patience to set up all my apps again so maybe on my day off I'll git it a whirl. How's battery life on it?
Click to expand...
Click to collapse
Battery life is crazy good and I wouldn't recomeend dirty because it includes a whole different kernel and such and a lot of little things changed from cm10.1
Sent from my SCH-I500 using Tapatalk 2
---------- Post added at 06:40 AM ---------- Previous post was at 06:39 AM ----------
bmeek said:
You might try a dirty flash to Helly after taking a backup (just wipe cache & Dalvik). It's based on cm10.1 so you should be all right...
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
Its nothing like cm10.1 lol it has a whole different kernel and a while lot of other stuff lol
Sent from my SCH-I500 using Tapatalk 2
Thanks man, I've been looking into changing settings recently, might try it out.
dirty-flash between CM10 and HellyBean = no problem (apparently)
bbrad said:
Battery life is crazy good and I wouldn't recomeend dirty because it includes a whole different kernel and such and a lot of little things changed from cm10.1
Sent from my SCH-I500 using Tapatalk 2
---------- Post added at 06:40 AM ---------- Previous post was at 06:39 AM ----------
Its nothing like cm10.1 lol it has a whole different kernel and a while lot of other stuff lol
Sent from my SCH-I500 using Tapatalk 2
Click to expand...
Click to collapse
I simply said that Helly is based upon CM10.1, and it is. Anyway, I just did a dirty flash (cache+dalvik wipe only) from the 02/22 build of CM10.1 to the latest HellyBean and it works fine. Actually, with the 1400mHz overclocking it was working really smoothly - although the rate of battery drain was apparent...
My hesitation in sticking with hellybean is based on my lack of understanding on how/if all of JT1134's ongoing fascinate-specific kernel/framework efforts, that are going into the CM10 nightlies, are being merged into the hellybean kernel... I guess I should go over to DT's thread and ask . Perhaps he's got all that happening whenever he merges the CM10 source updates...
bmeek said:
I simply said that Helly is based upon CM10.1, and it is. Anyway, I just did a dirty flash (cache+dalvik wipe only) from the 02/22 build of CM10.1 to the latest HellyBean and it works fine. Actually, with the 1400mHz overclocking it was working really smoothly - although the rate of battery drain was apparent...
My hesitation in sticking with hellybean is based on my lack of understanding on how/if all of JT1134's ongoing fascinate-specific kernel/framework efforts, that are going into the CM10 nightlies, are being merged into the hellybean kernel... I guess I should go over to DT's thread and ask . Perhaps he's got all that happening whenever he merges the CM10 source updates...
Click to expand...
Click to collapse
All the merges go fine the merges to the cm kernel merges into the devil kernel
Sent from my SCH-I500 using Tapatalk 2
Well I decided to try Helly Bean and so far so good, on SmartassV2 and ROW - no skipping music and everything is really snappy. Battery life seems noticeably worse than pure CM 10.1 but nothing that still can't get me through the day. I wish the Devil settings were baked into the rom settings like they used to be, it's annoying to have to use 3rd party apps to control it. I really like the standalone AOKP performance settings apk but settings don't stick after reboot
Crawshayi said:
Well I decided to try Helly Bean and so far so good, on SmartassV2 and ROW - no skipping music and everything is really snappy. Battery life seems noticeably worse than pure CM 10.1 but nothing that still can't get me through the day. I wish the Devil settings were baked into the rom settings like they used to be, it's annoying to have to use 3rd party apps to control it. I really like the standalone AOKP performance settings apk but settings don't stick after reboot
Click to expand...
Click to collapse
They are baked in just tap build number 10 times it only has the stuff available in performance right now the only other feature that isn't in performance is touch wake
Sent from my SCH-I500 using Tapatalk 2
bbrad said:
They are baked in just tap build number 10 times it only has the stuff available in performance right now the only other feature that isn't in performance is touch wake
Sent from my SCH-I500 using Tapatalk 2
Click to expand...
Click to collapse
Oh thanks man, totally missed that one. Also, it's missing all of the RAM settings like XL and such but I never used that anyway so this will work just fine so thanks again
Crawshayi said:
Oh thanks man, totally missed that one. Also, it's missing all of the RAM settings like XL and such but I never used that anyway so this will work just fine so thanks again
Click to expand...
Click to collapse
Well I done even thinks that's available yet dt is still in the procces of adding features like that
Sent from my SCH-I500 using Tapatalk 2
Drop this file in your /system/etc folder, replacing the stock one. Cleaned up, and modified to work with a stock kernel or lean kernel.
Please open up the file, and read some of the notes I added, so you know what this does and how to change it if you so desire. It is very basic and straightforward.
Also, please remember one thing, if you want to go to the stock kernel, simply change any words in the scripts from "interactiveX" to "interactive".
Recommended lean kernel 3.16 with these scripts.
Designed to work with ALL Galaxy Note 3's running touch wiz 4.4.2 ROMs and running lean kernel or stock kernel. Other kernels are not guaranteed due to the voltages applied.
This will make a huge difference in performance and battery. Been using this (developed by me) for a long time now.
Summary:
*I/O optimization
*tuned interactive parameters
*fixed sysfs permissions for cpu's (root now has full control of sysfs tuneables)
*GPU sysfs identified for user to customize
*screen off frequency set to 1.2 GHz (can be changed by user)
*custom voltage set for bin 2 device. (Read instructions within file to adjust for others bins accordingly)
*custom mpdecision tuning and other relevant instruction regarding mpdecision binary
*general CPU tweaks for better performance, responsiveness and battery life (yes all 3 can be achieved, and are)
Again, open the file with a file explorer (or notepad+ in windows). Read it, understand it, adjust what you want, or leave it be. These settings are very much dialed in for the interactiveX governor of LK. It won't get much better. I'd say take a look at the voltage portion and mpdecision for now (found at the end).
Once more, drop file into the /system/etc directory... Replace the existing one, and reboot.
FILE DOWNLOAD
Updated today... many useful changes, and fixes (set up for stock kernel for now)
https://www.dropbox.com/s/tjlygujptls3lks/init.qcom.post_boot.sh?dl=0
Thanks man!
Thanks man best Antutu score.
Best. Disclaimer. Ever.
Sent from my SM-G900V using XDA Free mobile app
Hahahahahahah I love the disclaimer.
Thanks! Helps a lot
Sent from my SM-N900V using xda app-developers app
I've noticed my phone lags alot less now and some things I had going wrong (if I turned torch on more than 15 seconds it would freeze and Multiwindow didn't like to work) work now. I don't know why or how or even if it is supposed to do anything to those things and it's just a very odd coincidence. But I've noticed my battery life is horrible now. Running it with Alliance 2 and with my ZeroLemon I used to get 10-11 hours on screen time and that's down about half to 5 or 6 hours. I know you said you could tweak stuff but I have no idea about that. Any recommendations for me to change in the script? Thanks again if for anything my phone running smoothly again!
amebiasis said:
I've noticed my phone lags alot less now and some things I had going wrong (if I turned torch on more than 15 seconds it would freeze and Multiwindow didn't like to work) work now. I don't know why or how or even if it is supposed to do anything to those things and it's just a very odd coincidence. But I've noticed my battery life is horrible now. Running it with Alliance 2 and with my ZeroLemon I used to get 10-11 hours on screen time and that's down about half to 5 or 6 hours. I know you said you could tweak stuff but I have no idea about that. Any recommendations for me to change in the script? Thanks again if for anything my phone running smoothly again!
Click to expand...
Click to collapse
If you aren't using lean kernel, you need to change the governor in the script to NOT say "InteractiveX"... Stock, or all other kernels need "interactive"... Otherwise the governor will be stuck on performance.
That is likely your issue.
Most people don't know that the note 3 boots with the performance governor enabled. The /system/etc/init.qcom.post_boot.sh file executes after the boot complete flag and changes the governors, among other things.
Edit the file, change the governor call out to "interactive".
Should fix it.
Thank you sir!
Running amazing after changing things over to "interactive" in the script with the stock kernel. Much more fluid speed on Eclipse with the battery life a bit better. Thanks for sharing! :highfive:
Wow night and day difference by changing that script to just interactive. Been flying all day playing games and watching movies total SOT (with my ZeroLemon) is just over 5 and a half hours screen brightness at about 65% using Lux and Bluetooth and I'm only at 67% awesome job man and thank you for steering me in the right direction!
Is the 300 slot removed from this script?
Also to my understanding this is mainly for the dev edition and lean kernel correct. But most of us r on the retail. Is there anything else to change besides the interactive for better performance?
Sent from my SM-N900V using xda app-developers app
stalls said:
Is the 300 slot removed from this script?
Also to my understanding this is mainly for the dev edition and lean kernel correct. But most of us r on the retail. Is there anything else to change besides the interactive for better performance?
Sent from my SM-N900V using xda app-developers app
Click to expand...
Click to collapse
I can tell you for sure...this scripts works fine for plain jane stock kernel (because that is all you can use on retail Verizon N3) as long as you change the "interactiveX" to just plain "interactive"
Obviously you need root to swap out the script.
Sent from my Note 3 via Tapatalk
donc113 said:
I can tell you for sure...this scripts works fine for plain jane stock kernel (because that is all you can use on retail Verizon N3) as long as you change the "interactiveX" to just plain "interactive"
Obviously you need root to swap out the script.
Sent from my Note 3 via Tapatalk
Click to expand...
Click to collapse
Big difference in battery life when i changed interacticeX to interactive. Thanks for this OP. :thumbup:
Just want to provide my stats after using the script on eclipse rom 2.2./interactive. Screen on time was 6.5 hours with the phone. Before the script I would average about 4 hours. I want to thank the OP, this was a great tweak. Thumbs up.
Just giving you all a heads up.... I think there may have been a few errors in the stock init.qcom.post_boot file (they are human too, remember).
I am testing a few small changes to certain lines in the "factory" script to make sure. A brief explanation of it is that there are certain lines I removed from the one you all are using right now, and I did so because the file paths being called out did not exist!
However, I was going over this again tonight, getting ready for the official LP release and decided to review this odd discrepancy one more time. After doing some digging, I found that the file that some of those values were intended to be written to, were actually somewhere else!
Doh! - Sammy/QC. It is very possible that this location changed from a previous design or fs structure and somebody simply forgot to modify the script. Very interesting indeed.
Anyways, after I run this for a couple of days and do a little bit more investigating, I'll post the updated script for all of you.
Updated link and file. Please update if you were using this before, as there are many changes that were critical to stability and performance (errors made in this stock script)
Other devs, I recommend working this into your ROMs, given that fact.
red_can_soda said:
Updated link and file. Please update if you were using this before, as there are many changes that were critical to stability and performance (errors made in this stock script)
Other devs, I recommend working this into your ROMs, given that fact.
Click to expand...
Click to collapse
Question. So if this new file is set up for stock kernel for now, is it set to interactive or do we still need to change from interactiveX on retail?
Edit: was being lazy. Went ahead and went through script. Didn't see interactiveX anywhere.
red_can_soda said:
Updated link and file. Please update if you were using this before, as there are many changes that were critical to stability and performance (errors made in this stock script)
Other devs, I recommend working this into your ROMs, given that fact.
Click to expand...
Click to collapse
I'm not so sure the latest script is good or not....on my stock kernel Verizon N3 (NC4 firmware and kernel with NK1 radio) using the new script seems to have killed my battery life. I went from 33% to 20% in about 20 to 30 minutes.
I reset by restoring original script...rebooting...restoring your original script (interactiveX changed to interactive)...rebooting
I had to charge the phone so can't give a real check until I get back to 33% or so.
Sent from my Note 3 via Tapatalk
donc113 said:
I'm not so sure the latest script is good or not....on my stock kernel Verizon N3 (NC4 firmware and kernel with NK1 radio) using the new script seems to have killed my battery life. I went from 33% to 20% in about 20 to 30 minutes.
I reset by restoring original script...rebooting...restoring your original script (interactiveX changed to interactive)...rebooting
I had to charge the phone so can't give a real check until I get back to 33% or so.
Sent from my Note 3 via Tapatalk
Click to expand...
Click to collapse
Same here on battery drain. Not as smooth either running biggins rom "possible reason". I might try this on a stock Rom to see if that makes a difference. Hard to beat untouched biggins right now though.