I am not sure as to whether this should go to the general, or the development thread. But I think developers as well as other users gotta know if there's something that can improve rom performance.
So, I've noticed apart from 16 bit transparency, there's another tweak in the later cm7.2 roms of
debug.sf.hw=1
debug.composition.type=gpu
These lines forces GPU to render graphics. In the early gingerbread leak roms debug.sf.hw=1 is the source of a pain for all users, slowing ALL popup animations and lagging them badly, and also rendering the screenoff animation inexistent. The solution was to comment out the line itself.
Later these lines became a standard in Cm7.2 roms. I commented them out anyways, bringing a very slight improvement to performance.
But now, I believe there is a better tweak. Debug.composition.type has 2 settings of gpu or cpu. Out of curiosity I wrote 2 lines into build.prop, in an attempt to make BOTH CPU and GPU to work the graphics.
After rebooting I found that there WAS indeed an improvement in touch response time, and graphics seems to be smoother.
A long time spent in xda made me think about the placebo effect. But I tested this on many occasions with many roms and found, to my pleasure that there is indeed a difference. Believe me, I spent time STARING at some touch events and I do feel a difference.
So here I recommend you all to do the same.
Flash the updated adreno libraries, which adds the above 2 lines into build.prop. Following this, add a next line of debug.composition.type=cpu following the gpu line. Fairly easy to do with a root browser; I use root explorer.
I hope this thread doesn't get moved until this becomes a standard! I post in no attempt to hoard thanks, or donations, I just want everyone else following xda with a **** phone like the Ace to make their lives a little better. Well, you all are here, undeniably, because you are OCD about your phone speed.
Thanks for reading and have a nice day!
Cool
I hope this help developers to boost performance on their ROMs.
If this works, I'd prob start using CM7.2
Thanks for the tip bro!
Have you tried these lines on stock roms ?
Sachin_22 said:
Have you tried these lines on stock roms ?
Click to expand...
Click to collapse
I used it on Myth2. If that monster could go smoother, it did.
It made the scrolling too smooth. But anyways :good:
I think this is interesting, but I didn't understand well the procedure. Do I just have to write these lines in build.prop? I suppose they are meant to be placed in a specific position am I right?
Could you please write down the precise lines to copy and the position in which doing that?
Sent from my Ace on Apocalypse Rom
consegregate said:
I used it on Myth2. If that monster could go smoother, it did.
Click to expand...
Click to collapse
I confirmed this I made new update 1.0b for Myth Users 2 days ago Nice tip, my bro
Jar3112 said:
I think this is interesting, but I didn't understand well the procedure. Do I just have to write these lines in build.prop? I suppose they are meant to be placed in a specific position am I right?
Could you please write down the precise lines to copy and the position in which doing that?
Sent from my Ace on Apocalypse Rom
Click to expand...
Click to collapse
Yup, in build.prop.
Begin on a new line. Doesn't matter where you place it, you could write the below debug.composition.type=gpu if you like, or you could just add it to the bottom.
Scrolling increase after add this !
Open root explorer
Go in system
Press and hold build.prop and "Open in Text Editor"
Add this lines if you don't have :
debug.composition.type=gpu
debug.composition.type=cpu
Hit menu, then Save changes!
Restart
If i get it wrong correct me
Nice tip bro
Done. Will give feedback in 24 hrs!
Edit: i did not flash latest adreno libs, is it the same? I am on apocalypse rom!
Sent from my Ace on Apocalypse Rom
Problem found: Opera mini does not start anymore. (Most likely problem after flashing latest adreno libs)
Don't think this will work anyway, first it gets set to gpu, and after that it will change to cpu.
_Roysten said:
Problem found: Opera mini does not start anymore. (Most likely problem after flashing latest adreno libs)
Don't think this will work anyway, first it gets set to gpu, and after that it will change to cpu.
Click to expand...
Click to collapse
I didn't think it would work as well. But it did. Well it never hurts to try.
Opera mini runs regardless of what I did with build.prop. Nope, no such problems.
Can someone explain to me why two different values for the debug.composition.type?
debug.composition.type=gpu
debug.composition.type=cpu
Shouldn't it be debug.composition.type=gpu only? Kindly explain.
In stock ddkq8 there is also a line debug.composition.type=mdp
What about this ? Do we have to comment it ?
testing in stock rom sgs2 v9, didnt notice anything straight away, will be testing though
Thanks for the tip.. will try
Sent from my GT-P6200 using Tapatalk 2
OP or someone need to illuminate us about this.
Works on cm7 / stock ?
What lines have to be edited in build.prop ?
Explane man because how you post this only confuses us !
Sorry 2 say this but is nasty ordered post.
Little more
I guess We all know these
Code:
debug.performance.tuning=1 - Increases touch responsiveness.
video.accelerate.hw=1 - Increases touch responsiveness.
windowsmgr.max_events_per_sec=120 - Increases scrolling responsiveness.
@OP, excellent tweak mate! Keep up the good work :good:
Related
UPDATE
Due to unforeseen issues with this build and a plethora of people incapable of reading even simple notes, this release is being pulled while we work out some issues with our own internal testers.
Thank you.
Kernels. The final pain in the arse. These are the voyages of the dev team Ninphetamine. Our continuing mission, to break strange new code. To seek out new bugs and strange implementations. To boldly go where no phone has gone...before.
*cue musical score*
It's been some time since I last graced the Android community. Draped in the success of FroydVillain 1.5, empowered from my victories over Froyo's poor (and non existent) AOSP implementation for the HTC Hero, onward I charged into the task of dragging the ancient kernel of the Hero into the 21st century. However, after seeing how HTC are as likely to stick to recommended kernel practices as I am likely to win a Miss Universe contest, (This is highly unlikely and the least significant reason is that I am not female.) I buckled like a jet fighter made from tin foil and surrendered faster than an agoraphobic Frenchman. There has been some advances into more modern kernels for the Hero but as I predicted they're still plagued with issues, all of which can be blamed squarely on HTC.
It took some major rehabilitation to get me back into the Android development scene, a key factor in that rehab being the ownership of a Samsung Galaxy S. A delightful phone, still in my opinion the best single core Android phone that money can buy. Beautiful screen, fast, elegant and excellent on battery. It nursed me through those dark days of waking up in cold sweats with github commits circling through my head, kernel debug symbols blinking in the dark of the night like Vietnam flashbacks, breaking down into incoherent rants on IRC development channels ending eventually with "YOU WEREN'T THERE MAN, YOU JUST DON'T UNDERSTAND, HTC WILL COME AND GET YOU EVENTUALLY, THEN YOU'LL KNOW". Oh how I longed to find a high up HTC developer in a bathroom to blow them away before ending my own bitter misery. Alas, it was not to be.
After a successful tour of duty as a regular non developing user on the Samsung Galaxy S, I treated myself to a brand new and shiny Samsung Galaxy S II. As soon as I used the device and checked out the available source code for it, I knew I was ready, I knew I was fully recovered to be able to break free from the oppression of HTC, I knew that I was capable to step once more unto the breach and step back into Android development. The stage set, the orchestra struck...all that remained was to see if the Samsung Galaxy II could dance.
And dance it can. Accompanied by my trusty partner in crime netarchy (because this time if I go down in a gibbering wreck I'm damn sure taking someone with me) there is at last another phone with the magic, capabilities and horsepower to endure the test of time and upgrades, that like the Hero has carved out a niche of not only being the good of its generation but being the very best of its generation. Such hardware deserves only the best development efforts and here we are.
The best kernel for a phone that any human hand is capable of producing at this very moment in time. This will of course be rendered moot with the next release BUT RIGHT NOW, this is it boys and girls. Download it, flash it, use it with whatever ROM you wish (VillainROM of course for those with an IQ north of my shoe size) and enjoy the liberated freedom, speed and stability that those whoever owned a HTC Hero became accustomed to.
After much arguing with Samsung's inane practices, lack of logic, bizarre design decisions and enough harrassment via their support interface that I confidently expect a restraining order any day now, I bring you...
Ninphetamine version 1.0, the beginning.
Features:
Overclocking up to 1.6GHz. The phone is blisteringly fast at stock 1.2GHz so be happy you can push it to 1.6GHz. We will not provide higher, if you want higher then make your own.
Full voltage control interface. Via SetCPU you can set voltage as low as 800mV or as high as 1500mV for each speed in the database. If you're possessed with the intelligence of a baboon and destroy your phone as a result, do not come crying to us. All you'll get is a quote in this thread with much mocking from myself and your peers.
Patches and bug fixes up to and including 2.6.35.11. We're working on going up to 2.6.35.13 however the important fixes are in already. As well as some that never made it to 2.6.35.y -at all-.
Fully tested performance optimisations. This kernel comes with BFQv2-r1 IO scheduler enabled as default along with some tweaked parameters for this scheduler. These were painstakingly tested over many many many many many MANY different benchmark tests. These are the best. Anyone who claims otherwise or says that noop or deadline or CFQ is better, they're wrong. Why? Because I say so and I'm right.
A customised and trimmed down initramfs, including Clockworkmod. Many thanks to ogdobber for this who kindly gave me the template including ClockWorkMod that I took and further improved upon. All storage mounts are optimised for performance and data throughput, busybox is included as well as a much improved shell that by default provides tab completion even via adb shell. Please note that by default, adb is insecure, this means that adb shell, adb remount etc all work and give root access immediately.
So there you have it. Please download, flash, test and report any issues/bugs in this thread. I'll then either completely ignore the dumb posts or take on board constructive ones and use those reports/suggestions, incorporate them into the next version and then take all the credit.
Thanks to:
This release would not have been possible without the awesome and tireless work of netarchy, of Nexus S and Asus Transformer fame. Thanks also to ogdobber and supercurio for their assistance. Also thanks to mattgirv, Lenny, Rawat, Obihoernchen, geko95gek and Ante0 for being my guinea pigs for the many many test builds that were made before this final release, no doubt without them there would be a lot more bugs in this release than there already are. Also not forgetting of course, the everlasting patience of my wonderful wife, without which I never would have bothered picking Android up again at all.
Bugs/Issues:
Please of course report them in this thread, however before doing so, please:
Wipe dalvik.
Ensure you have no other OC software installed such as Tegrak. The only OC software supported by this kernel is SetCPU (or setting manually via command line of course).
Are you using a custom ROM? See if you still get issues with stock Samsung firmware or VillainROM. I cannot test with every single custom ROM out there, so I test with stock Samsung (naturally) and my ROM of choice.
If you're still having issues such as random hangs/crashes/reboots and if these issues still occur at stock speeds/voltages then please do the following:
Install the Android SDK if you have not already done so.
In a command window, do the following:
Code:
adb logcat > USERNAME-logcat.log
Then in another window:
Code:
adb shell cat /proc/kmsg > USERNAME-kmsg.log
Naturally replacing USERNAME with your name and make these logs available either via attachment or pastebin or whatever. Please do not paste them directly into posts as these logs can become quite large quite quickly.
Known Issues:
adb install <package> currently does not work.
Version 1.1
Changelog:
Some minor edits to the initramfs to fix adb install <application>.apk and a few other path issues. Loses the nice adb shell with tab completion, but fixes some issues. Download links updated.
Version 1.2
Changelog:
More initramfs changes to fix an issue with nandroid backups.
Making nandroid backups work again may have broken the "adb install" package install method, but I figure working nandroid and needing to push the apk to the phone to then install with Application Manager beats broken nandroids. I'll look further into the adb install issue later today.
Version 1.4
Changelog:
Some configuration changes to try and track down the random hangs/reboots people are experiencing.
Support for startup scripts in /system/etc/init.d added should ROM makers wish to use them.
Added debugging code, which prevents deep sleep in version 1.4, but makes crashes easier to diagnose.
FAQ/General Points
I hate Odin. It is a giant buggy piece of ****. Things can inexplicably go wrong for no other reason than Odin is a big heap of proprietary fail. Before reporting issues with the kernel, please either flash it with CWM or Heimdall. I highly recommend Heimdall, it will flash a jpeg to your kernel filesystem if you tell it to and somehow it'll boot anyway. I do all my testing with Heimdall so it's safe to assume that if I'm posting it, Heimdall will flash it. Heimdall also has the advantage of being open source and completely cross platform. Please take the time to download it and get used to using it, it will save you a lot of pain in the future.
This kernel has been tested with 2.3.3 KF2 and 2.3.4 KG1. There is no reason it shouldn't work with any ROM revision.
Somewhat amazing that I need to point this out, but you MUST FLASH THE KERNEL FOR THE VOLTAGE TAB TO APPEAR IN SETCPU.
Don't use tegrak with this kernel. DO. NOT. USE. TEGRAK. WITH. THIS. KERNEL.
The voltage that's adjusted is the CPU core voltage.
Major_Sarcasm said:
Just a FYI for those people that can't make logical connections; if you have Tegrak OC installed when you flash this kernel, you might end up with a boot loop. Go back to default settings in the app, then uninstall it before flashing.
Click to expand...
Click to collapse
More will be added to this post as the need arises.
pulled for now
SUPER !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Thank you !!!
netarchy said:
Use the voltage interface in SetCPU.
Click to expand...
Click to collapse
OOOO who is here!!! famous netarchy
Hacre said:
Reserved
Click to expand...
Click to collapse
Welcome. Will give it a try.
2.3.3, 2.3.4 ... all ok w this universal kernel?
EDIT: Great... I see you edited Post #2, and the answer is yes.
Thanks for the kernel. Does this have the multi-touch fix included?
jlevy73 said:
Thanks for the kernel. Does this have the multi-touch fix included?
Click to expand...
Click to collapse
I've not noticed an issue with multi-touch, of what do you speak?
*subscribes to thread*
netarchy said:
Use the voltage interface in SetCPU.
Click to expand...
Click to collapse
Okay maybe this is a dumb question, how do you undervolt using setcpu? I know I use it to underclock, and AFAIK it's different from undervolting. I've check the interface of setcpu just now trying to find undervolting options
mach0boi said:
Okay maybe this is a dumb question, how do you undervolt using setcpu? I know I use it to underclock, and AFAIK it's different from undervolting. I've check the interface of setcpu just now trying to find undervolting options
Click to expand...
Click to collapse
Make sure you're using the latest version, and use the voltages tab.
mach0boi said:
Nice! So how will you do the undervolting here?
Click to expand...
Click to collapse
Ummm...
Hacre said:
Full voltage control interface. Via SetCPU you can set voltage as low as 800mV
Click to expand...
Click to collapse
If only I'd mentioned it in the OP...
netarchy said:
Make sure you're using the latest version, and use the voltages tab.
Click to expand...
Click to collapse
Ooh okay i didn't knew there was such feature! thank you!
Hacre said:
Ummm...
If only I'd mentioned it in the OP...
Click to expand...
Click to collapse
I'm sorry maybe I'm just using an outdated version and never knew you could actually do that. Forgive my ignorance
sorry i am new to android so i do not know about undervolt or overclock, can anyone please tell me best combination of voltages on 1.6ghz that does not effect battery life?
ravian29 said:
sorry i am new to android so i do not know about undervolt or overclock, can anyone please tell me best combination of voltages on 1.6ghz that does not effect battery life?
Click to expand...
Click to collapse
The stock max voltage of the CPU is 1275-1300mV. Anything under this improves battery life, anything over this harms battery life from the standard "stock" expectations. Just like with a PC, not all processors are created equal. There is no setting for 1.6GHz that will not affect battery life as at best you'll need to increase voltage from the standard max setting. If you're not sure, use our defaults, these have been tested on two different handsets. There isn't even a guarantee that 1.6GHz will even work on your handset.
If you're not sure or are not confident, don't touch it. Any settings you set past 1.2GHz/1300mV are at your own risk, may damage your handset or even rip a hole in the space-time continuum, then you'll not only look an idiot with a broken handset but Stephen Hawking will be really pissed and you really don't want him trying to crush your toes in that tank he calls a wheelchair.
Best case scenario, try our defaults and only increase voltage in 25mV steps. If you find yourself a 1450mV and your phone still isn't stable then 1.6GHz isn't going to work for you. If battery life is your concern, then consider undervolting in 25mV increments at 1.2GHz or even 1GHz or 800KHz.
mach0boi said:
Ooh okay i didn't knew there was such feature! thank you!
Click to expand...
Click to collapse
I am using the latest version 2.24, i don't see a voltage tab there..I only see Main, Profiles, Advanced, Info, About
@hacre cheers mate
umair9001 said:
I am using the latest version 2.24, i don't see a voltage tab there..I only see Main, Profiles, Advanced, Info, About
Click to expand...
Click to collapse
In Settings -> About Phone what does the Kernel version show?
umair9001 said:
I am using the latest version 2.24, i don't see a voltage tab there..I only see Main, Profiles, Advanced, Info, About
Click to expand...
Click to collapse
Yeah also checked it and I'm also using the latest version. Was about to ask this. Another question, is that voltage tab option kernel related? I'm using cfroot kernel and cannot find that damn voltage tab I'm using tegrak to undervolt. If I knew there's a feature like this in SetCPU, I should've not bought tegrak
I am constantly playing with and 'tweakin' my Streak and have put together what I think is a good, lite, fast, and stable rom. I made this for my own use and decided to share it with the rest of you.
I started with 354 then removed all apps that could be downloaded from the market. I also removed alot of stuff that I didn't think was necessary (such as all the verification*.apk's, don't even know what they are). There are only 17 apps in the drawer on a fresh install! I added DJ Steve's kernel and some memory tweaks from using the HTC Kitchen. VTL Launcher ADW is the included launcher as well as Swype for the keyboard. There are also some customization provided by UOT Kitchen as well as a modified Settings.apk that I got from somewhere on here. I'd love to thank whoever made it, but I have lost track so if it's your's---thank you!
I'm getting Quadrant scores in the 1400's and battery life seems pretty decent. I gave up on Quadrant scores. My best guess would be low 800's for this version. I have found through trial and error that higher Quadrant scores mean less stability, and honestly I can't tell the difference in real world performance between an 800 QS and a 1400 QS. I can't tell you exact battery life because I haven't hardly put this thing down since I installed this.
I am not an expert by no means and have only gotten these results from tinkering and trial and error. I think this is good, but am open to suggestions for improving it.
I started off by installing stock 354 using stock recovery, then installed this using Streakmod recovery and did a Factory Reset (Dell's, not Streakmod's). I have had no issues so far.
I have seen this posted before and liked it so I'm going to use it here: If you find a bug, you get to keep it. If this breaks your Streak, you get to keep the pieces. Obviously installing a custom rom breaks your warranty, and I am not responsible for whatever happens if you install mine.
Thanks to everyone whose ideas I stole/used/borrowed/whatever. Without the true experts on this board, I wouldn't have had anything to tinker with.
What works: Everything I can think of
What doesn't work: Waiting for you to tell me. The time in the status bar is black and the status bar is blackish...makes it hard to see. I don't know why and haven't yet figured out how to fix this. If someone has a link to a good tutorial and I can make it work, I'll be happy to resolve it!
So without further ado, I present Streakin' 354v1 354 v1.1:
http://www.multiupload.com/1MVM3O34AN v1.1 *newest*
http://www.multiupload.com/BHI4Y4XD69 I'm leaving this link for those that prefer v1.
I do intend on maintaining this rom and tweakin' it more based on recommendation, more stuff that I learn, etc. I do have a full time job, so even though I want to answer questions immediately, it's not always practical. If it takes me a while to respond, I apologize in advance.
Edit 09/24/11 - If you prefer landscape mode, simply flash the attached file below in recovery. Be sure to wipe cache and dalvik-flash after flashing. After doing this it took 5-6 minutes for my phone to boot, but it did....eventually. You may want to backup first! I also added a portrait mode file in case you decide you don't like landscape after all. Enjoy.
Edit 09/25/11 - It was pointed out to me that this ROM does not have a init.d folder. I forgot to add it, although the support to run scripts in init.d is there. Until the next version comes out, using Root Explorer, or similar, create a folder named init.d in /system/etc/ and set the permissions to rwx,r_x,r_x. That should be all you need. Thanks.
downloading now
thats great--regards for posting--downloading now-will check and report in a few hours
i like lite..... ill give it a go
EDIT
its not for me i dont like the launcher & it does not have portrait lock ill stick with simplestreak for now
scdsone said:
i like lite..... ill give it a go
EDIT
its not for me i dont like the launcher & it does not have portrait lock ill stick with simplestreak for now
Click to expand...
Click to collapse
Get a different launcher ................turn off screen rotation in the android system settings............................................................................................................................................................
in the settings.apk, are there any theme changes? or are they performance tweaks?
and what files are you using with dj steve's kernel that keep your wifi working?
Thanks in advance.
I'll give it a try - and thank you for your efforts in advance
rsalib said:
in the settings.apk, are there any theme changes? or are they performance tweaks?
and what files are you using with dj steve's kernel that keep your wifi working?
Thanks in advance.
Click to expand...
Click to collapse
It's just a themed change....colored icons and such for settings.apk.
As far as the files, I'm not at my computer (I'm at work), so I'll have to get back to you on this.
scdsone said:
i like lite..... ill give it a go
EDIT
its not for me i dont like the launcher & it does not have portrait lock ill stick with simplestreak for now
Click to expand...
Click to collapse
I didn't like VTL Launcher either, until I went into the settings and turned the left and right dockbars off. Now it's not much different than ADW and rightfully so, since it's based off of it.
7h 15 min running the rom
The rom running well
I have changed the launcher to go launcher after loading the rom running fine
battery life--15% in 7h 15 min
few voice call few minutes of data usuage two skype video call about 15 minutes of usuage and 7h standby
so far good running
15% used or left?
Sent from my Dell Streak using XDA App
lordmorphous said:
15% used or left?
Sent from my Dell Streak using XDA App
Click to expand...
Click to collapse
Probably 85% left.
Sent from my Dell Streak using xda premium
Try "orientation control" by "coin soft" to lock your streak in whatever orientation you want. I've got it on my streakdroid and it works fine
Just an observation here. You might want to contemplate recreating this ROM using 360 as a base instead of 354 due to the more complete language support in the former compared to the latter.
Strephon Alkhalikoi said:
Just an observation here. You might want to contemplate recreating this ROM using 360 as a base instead of 354 due to the more complete language support in the former compared to the latter.
Click to expand...
Click to collapse
I had contemplated using that rom as my base, but noticed everyone had better battery life with 354. 360 was listed as being an "update" 351, which gave me horrible battery life. If someone can tell me different as far as battery, I don't think it would be difficult to redo this based on one of the others (360 or maybe 364?)
Grateful your work!
Grateful your work! I am pleased that contains the settings for Japanese.
Parts of the screen is also very beautiful!
I will continue to use this ROM for a while.
scdsone said:
i like lite..... ill give it a go
EDIT
its not for me i dont like the launcher & it does not have portrait lock ill stick with simplestreak for now
Click to expand...
Click to collapse
I see no reason why the portrait mode file located here wouldn't work:
http://forum.xda-developers.com/showthread.php?t=1084850
Just choose the one for 354.
OK, I woke up to find my phone stuck on the Dell logo. I had plugged it in before going to sleep. A battery pull later and all seems well. Anyone want to tell me how to start troubleshooting this?
Sent from my Dell Streak using XDA App
OK, I removed DJ Steve's kernel and replaced some files that were changed to accomodate it. My quadrant scores are now in the 800's and I'll report back with the 'feel' of the device and stability over the next day or so. I love seeing high scores, however must admit I've never really noticed a difference in day to day use with the higher scores. I will take stability over high benchmark scores, but will take noticeable speed increase over a little stability if that makes sense.
Quadrant is too overrated as a benchmark. Stick to a reliable & stable build
haynesteve said:
Quadrant is too overrated as a benchmark. Stick to a reliable & stable build
Click to expand...
Click to collapse
I think I believe you...so far (about 3 hours or so) and I can't tell the difference in performance. Granted I don't use 3D games and such...
I added your rom to the big Wiki Rom List
if something is off for your rom feel free to tell me, or change it directly
You might find this useful as this is most of the changes you mentioned in your rom: List of safe to remove apks
Hello,
Firstly sorry for my english, i'm new here that i cant put images from standard method that i must put it in attachments sorry for trouble. That's my problem on every every CM mod when i load "cm-7.1-oc-kernel-2.6.35.7-perf-CL562111.zip"i have problem with touch screen.
(screenshot1 from attachments)
The above screen shows the twirling finger rings. It is very irritating when you look through post office or browse the Internet
But when i put cm-7.1-kernel-2.6.35.7-perf-CL562111.zip everthing is ok. (screenshot2 from attachments)
This is cm-7.1-kernel-2.6.35.7-perf-CL562111.zip: nothing problem with touchscreen
(screenshot3 from attachments))
But when i use OC kernel : i have very big problem witch touchscreen
this problem This problem regards each one CM, CM 7.1 CM 7.2 JAF, Griff, KANG, Icecream Sunday2, BehradGH, GingercruztV2.3. EVERY ONE.
I tried to upload KPB, KS9, KS2, KPY, everything WIPE. Always end the same.
Thank You
Please Help
Then don't use the overclock kernel .
Sent from my GT-S5830 using XDA App
EmoBoiix3 said:
Then don't use the overclock kernel .
Sent from my GT-S5830 using XDA App
Click to expand...
Click to collapse
Thanks for the very constructive and wise answer. I think that my 5 year old child that could advise me the same thing
icemanhi said:
Thanks for the very constructive and wise answer. I think that my 5 year old child that could advise me the same thing
Click to expand...
Click to collapse
Well , you chose to use the kernel , it's your fault
Sent from my GT-S5830 using XDA App
icemanhi said:
Thanks for the very constructive and wise answer. I think that my 5 year old child that could advise me the same thing
Click to expand...
Click to collapse
I know it's not the most helpful response, but there really isn't a good solution. If you choose to overclock the phone there is a price to pay. Your price unfortunately, is touch screen issues. Others have stability issues and others cannot o/c at all. Personally I think the only reason to use an o/c kernel on the Ace is for the scheduler choices.
Sent from a ZTE Crescent with an app.
Look man,OC is not a thing to play with,in your case it was touchscreen issues,others have other problems.Dont use oc in my opinion
Hey @icemanhi...
Firstly, your english is fine... I can understand you & I'm sure others can too...
Now, lots of people saying "Don't do it" but nobody offers help... Come on guys, give @icemanhi a break... @Prawesome is correct though to a degree... OC'ing is not for everyone but with a little care & patience, you can achieve some significant performance gains...
@icemanhi... There are a couple of things that you can try that may correct this touch screen issue that you have got. It is possible that when you flash @ketut's OC kernel, it corrupts your screen variables or changes them to un-usable values. If you search the SGA development forum you will find several scripts that enhance & tweak your touch screen (response, sensitivity etc)... some of them are flashable via CWM (clockwork Mod manager), some of them you must manually place the script in the correct location within your phone...
I suggest you try one of the flashable versions unless you are savvy to file placement & permission setting...
Flashing the screen Mod will re-callibrate your screen to the new improved variable settings, hopefully correcting any corruption that was left from flashing @ketuts kernel...
Please remember though, that I am not providing a cure, I am just suggesting a method that in theory should do the trick. I can not say I have tried this as I have experienced no problems at all using Ice cream sunday2 by @jusada... On the other hand, I have used the touchscreen tweaks (I am using them now) & they work wonderfully... I barely have to brush my screen & I get a response...hehe
Check below my signature for my Rom & setup...
Stay Breezy n Be Lucky...
Peace...
Are you having "my phone won't boot past the splash screen" issues with the latest OTA, and you're not using one of the Stock ROMs?
Mine wouldn't boot either, and it was because of this line in build.prop
debug.sf.hw=1
It was part of the "use gpu to render" tweaks that I'm not even sure do anything.
Anyway, remove that line and all should be well.
freeza said:
Are you having "my phone won't boot past the splash screen" issues with the latest OTA, and you're not using one of the Stock ROMs?
Mine wouldn't boot either, and it was because of this line in build.prop
debug.sf.hw=1
It was part of the "use gpu to render" tweaks that I'm not even sure do anything.
Anyway, remove that line and all should be well.
Click to expand...
Click to collapse
Hmm, I have no idea why but my build.prop has the "debug.sf.hw=1" line in it, I'm not using a stock rom and I have no problem booting after flashing freeza's (your) AIO (didn't flash the whole OTA).
The comment in front of the debug.sf.hw=1 line in build.prop says "#Render GUI with GPU instead of CPU", so if you remove the debug.sf.hw=1 line are you giving up hardware acceleration on GUI?
oldjackbob said:
Hmm, I have no idea why but my build.prop has the "debug.sf.hw=1" line in it, I'm not using a stock rom and I have no problem booting after flashing freeza's (your) AIO (didn't flash the whole OTA).
The comment in front of the debug.sf.hw=1 line in build.prop says "#Render GUI with GPU instead of CPU", so if you remove the debug.sf.hw=1 line are you giving up hardware acceleration on GUI?
Click to expand...
Click to collapse
The thing is, it doesn't affect the firmware or radio updates, only the actual OTA. That's why you're not having any problems.
After a bit of research, I've come to the conclusion that that line isn't really responsible for GPU rendering at all. In fact, I'm not sure any of those do anything. That one for sure doesn't.
freeza said:
The thing is, it doesn't affect the firmware or radio updates, only the actual OTA. That's why you're not having any problems.
After a bit of research, I've come to the conclusion that that line isn't really responsible for GPU rendering at all. In fact, I'm not sure any of those do anything. That one for sure doesn't.
Click to expand...
Click to collapse
It actually does make a difference, but for some reason it seems to only work with the OTA before this one. Yes, this is far from scientific proof, but try scrolling the app drawer without the setting and then again with it on. You will notice a difference. Its far from major but it's really noticeable. It's also the only way I could notice a difference. But like I said, its enough that you can tell that at least it does something... seriously, roll back and see for yourself, I promise you will see it too.
but for some reason it doesn't seem to do work with this OTA.. maybe there's a connection... idk.
That line was needed for crt animations to work. Removing it made crt animations stop working, so it did (or used to) do something.
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums
Moving to Q&A
Though there is a question in the o.p., I dont think the thread in general is a question.
Via My HTC Evo 3D On The Now Network From Sprint.
another mod i come across have tried the first mod with flow control set to 10 slowed me down it seemed but I left it blank and seems like huge improvement maybe just me figured I share see what else others can get. haven't tried the second mod looks a little risky to me if you try it please post results for others and if it works for you make sure to thank the right person (not me)
;-)
http://forum.xda-developers.com/showthread.php?t=1466245
spleef said:
another mod i come across have tried the first mod with flow control set to 10 slowed me down it seemed but I left it blank and seems like huge improvement maybe just me figured I share see what else others can get. haven't tried the second mod looks a little risky to me if you try it please post results for others and if it works for you make sure to thank the right person (not me)
;-)
http://forum.xda-developers.com/showthread.php?t=1466245
Click to expand...
Click to collapse
Do you intend to try the Mod 2? I'm going to try this in a bit and will post my results.
El Shaddai's Wrath said:
Do you intend to try the Mod 2? I'm going to try this in a bit and will post my results.
Click to expand...
Click to collapse
yeah thinking about it going to spend next 20-30 reading through all the info surrounding it then if i understand how to do it and how to go back to the way it was before ill give it a go
spleef said:
yeah thinking about it going to spend next 20-30 reading through all the info surrounding it then if i understand how to do it and how to go back to the way it was before ill give it a go
Click to expand...
Click to collapse
I can not find code: "persist.ril.uart.flowctrl=1"
Tried Root Explorer and Rom Toolbox and neither showed this. I am running Joker's 1.4 kernal not sure if that could possibly make any difference???
what rom cm doesn't have it think its only stock or stock based I'm on rocko and its there also just did the file swap can't say it helped yet but no problems with it so far don't think in going to try the unthrottle mod though looks terribly risky of having to sbf the line in my prop is immediately after cdma ril........
Sent from my MB855 using xda premium
Currently running CM7.2 and the code literally isn't there at all which leads me to believe that you could just delete the entire thing and it would either help or hurt your speed on Sprint's network.
El Shaddai's Wrath said:
Currently running CM7.2 and the code literally isn't there at all which leads me to believe that you could just delete the entire thing and it would either help or hurt your speed on Sprint's network.
Click to expand...
Click to collapse
idk thread says if you put a 0 you lose internet and zep was looking into it saying it can only be turned on or off not adjusted but then again said maybe it could be seems like it needs more research/testing but hell as horrible as sprint network in my areas is especially without 4g and flakey wifi anything that can help im trying
so i have been running this for a full day now and can say both mods seemed to have improved my stability and speed of internet saying this because in my are the 3gs are more like no gs and withe mod1 and 2 in place ive gotten a very reliable connection and much improved ( not to the point of worth shouting about but ) i a using null settings on mod 1 just leaving it blank and ive done the file swap in the second mod i want to try the unthrottle bit but im no dev and dont want to play with it not knowing exactly what it could do to my magnificent mopho. gl folks hope this works for you guys as well as it "appears" to be for me
Im on cm9 and its also not there, well it wasn't i added persist.ril.uart.flowctrl=10 to the ril sections, and my results where better data speeds on the cm9 which has been terrible btw. going to try mod 2 while im at it.
grimproductions said:
Im on cm9 and its also not there, well it wasn't i added persist.ril.uart.flowctrl=10 to the ril sections, and my results where better data speeds on the cm9 which has been terrible btw. going to try mod 2 while im at it.
Click to expand...
Click to collapse
Coolness think im going to try the unthrottle today i just flashed new rom havent set anything up yet if it messes things up wont lose nothing starting over
Sent from my MB855 using xda premium
So doesn't Zep's 3G Tweak script do essentially the same or is this different somehow?
As far as I know his scripts don't but he is testing it to maybe include it or thats what I understood from reading his posts.....
Just did the whole unthrottle mod was much easier than I thought everything running great no problems at all too early to tell if it improved anything but we will see and ill report if anything has
Sent from my MB855 using xda premium
grimproductions said:
Im on cm9 and its also not there, well it wasn't i added persist.ril.uart.flowctrl=10 to the ril sections, and my results where better data speeds on the cm9 which has been terrible btw. going to try mod 2 while im at it.
Click to expand...
Click to collapse
You still running that mod without problems? Have you tried adding the line to CM7.2 RIL section?
jbb2388 said:
You still running that mod without problems? Have you tried adding the line to CM7.2 RIL section?
Click to expand...
Click to collapse
using rocko's unlocked rom with it nulled out (left it blank) maybe placebo but feels like its better so far as adding it to cm i think cm already removes the flow control im not 100% on that but if you wanna try it make sure you nandroid and or put a .bak after your prop so you can fix if something goes awry.
grimproductions said:
Im on cm9 and its also not there, well it wasn't i added persist.ril.uart.flowctrl=10 to the ril sections, and my results where better data speeds on the cm9 which has been terrible btw. going to try mod 2 while im at it.
Click to expand...
Click to collapse
Any specific place u added the line? And guessing # precedes it?
Sent from my CM9 Electrify.
Android 17 said:
So doesn't Zep's 3G Tweak script do essentially the same or is this different somehow?
Click to expand...
Click to collapse
his script took me from 200-500kpbs to 1000-2000kpbs 3g supercharged script with 1-5 settings setting 5 experimental took me to 2000 but up and down whole way setting 3 was pretty constant on 1500 so that is where i stayed
grdead25 said:
his script took me from 200-500kpbs to 1000-2000kpbs 3g supercharged script with 1-5 settings setting 5 experimental took me to 2000 but up and down whole way setting 3 was pretty constant on 1500 so that is where i stayed
Click to expand...
Click to collapse
Be nice to get speeds like this with CM9.
i thought i read some post where it worfed on cm9 not sure thou read the v6 scrip and look for the info there in the theme section
grdead25 said:
i thought i read some post where it worfed on cm9 not sure thou read the v6 scrip and look for the info there in the theme section
Click to expand...
Click to collapse
Good Question!
I an trying to know that too.
Sent from my MB855 using Tapatalk
roundeye1987 said:
Any specific place u added the line? And guessing # precedes it?
Sent from my CM9 Electrify.
Click to expand...
Click to collapse
The location should'nt matter. You definitely dont want a # before a line that you want parsed. A # is essentially voiding that line out. It is called a comment in technical terms.
Sent from my MoPho. All typos are the phones fault.