Related
Well since we have a thread for everything else and no place for general discussion. Here it is.
zenulator said:
Well since we have a thread for everything else and no place for general discussion. Here it is.
Click to expand...
Click to collapse
i don't know about anyone els but the one and only problem i have with hero is incoming call response time, zenulator and others have worked hard on speed. and right now i'm using the latest vogue hero.sqfs bundle. and it is pretty fast. i just need to be able to receive calls a little faster instead of one ring before vm.
i'm asking anyone that codes or knows how to code to look into what can be done to improve this.
i know that having phone not vibrate on calls, using ogg ringtones help a little, the renicer script aswell. but is there anything else we can do?
jamezelle said:
i don't know about anyone els but the one and only problem i have with hero is incoming call response time, zenulator and others have worked hard on speed. and right now i'm using the latest vogue hero.sqfs bundle. and it is pretty fast. i just need to be able to receive calls a little faster instead of one ring before vm.
i'm asking anyone that codes or knows how to code to look into what can be done to improve this.
i know that having phone not vibrate on calls, using ogg ringtones help a little, the renicer script aswell. but is there anything else we can do?
Click to expand...
Click to collapse
if someone ports the htc ril, this might fix the problem.
tatnai said:
if someone ports the htc ril, this might fix the problem.
Click to expand...
Click to collapse
Speaking of that, whats this all about on the Vogue-Hero google page? I've downloaded it to keep a copy on hand but what improvements will we see with that file?
i was using the latest hero build with the basefiles from 9/08 and everything was pretty smooth. then i updated this morning to basefiles from 9/15 and everything is slower. takes longer to switch pages and respond to anything i do.
tatnai said:
if someone ports the htc ril, this might fix the problem.
Click to expand...
Click to collapse
The HTC RIL is closed source. Its not a question of porting.
Here is my problem. I keep trying the latest donuts and sqsh based systems and even with fresh data files, I always get the dreaded Blank home screen with no icons. It takes around a minute to repaint them. The version I keep going back to is the cupcake-based hero themed system. It is distinguished by only having one arrow on the left side of the app drawer handle. It works great and hardly ever does the slow down thing. I just hope that when we get BT all sorted out that either the image will work with this system or the sqsh based systems are up to the same level of performance that this one is.
Cheers.
katmandu421 said:
Here is my problem. I keep trying the latest donuts and sqsh based systems and even with fresh data files, I always get the dreaded Blank home screen with no icons. It takes around a minute to repaint them. The version I keep going back to is the cupcake-based hero themed system. It is distinguished by only having one arrow on the left side of the app drawer handle. It works great and hardly ever does the slow down thing. I just hope that when we get BT all sorted out that either the image will work with this system or the sqsh based systems are up to the same level of performance that this one is.
Cheers.
Click to expand...
Click to collapse
I don't have any of these problems with my builds so you might be missing a step or using the wrong files. Granted the xrom and cyanogen builds at vogue-hero are experimental/beta quality and hence why they stay there and don't go to the main vogue-android page. The latest xrom is using cupcake/donut built from the android master branch and is as fast as any build out there with the right setup and you can't use it with an existing data.img because it has a different code base. And sqsh has nothing to do with the level of performance of any build infact it should be faster than cramfs. It's the code that the system image is based off of and what extra apps and libraries and frameworks are included that determines how fast it's going to be.
Zen since you seem to be up and responding I have a quick question that I am not looking for too in depth of a response, just a brief overview...
What exactly is the user.conf responsible for? If I am running just the basic ION version is there any reason to keep the rogers or hero based files? Are they ever called upon when running the regular ION build?
Thank you!
BJNK said:
Zen since you seem to be up and responding I have a quick question that I am not looking for too in depth of a response, just a brief overview...
What exactly is the user.conf responsible for? If I am running just the basic ION version is there any reason to keep the rogers or hero based files? Are they ever called upon when running the regular ION build?
Thank you!
Click to expand...
Click to collapse
you don't need them if your running ion. the user.conf files are just for people to tweak their own settings for each build. so you have the ability to turn compcache/swap on/off things like that. ion doesn't really need it but it does help it out it you run a lot of programs and widgets.
I've got a vogue and a diamond on sprint that I switch back and fourth between pretty often.
I thought maybe I could get a vzw htc vogue off of ebay, and get it working on my sprint plan, and put android on it.
If I did that, would GPS be crippled on it in android?
The main reason I wanted to do it was I like the white case and the vzw screens are all nice, I have a sprint vogue with a bad screen.
I'm excited that Zen said he was repackaging the nkhero release as it is essentially the latest-stable Ion build. The experimental builds are nice and essential to advancing development but alot of users are looking for everyday stable usage (and the added Hero theme is always sweet eye-candy)!
pmos69 said:
The HTC RIL is closed source. Its not a question of porting.
Click to expand...
Click to collapse
so I guess the question is, can it be cracked/hacked, or not possible?
i recommend everyone try out the opera mini beta 5 with android. Make sure you have Java installed on your build. I use the latest hero-vogue build. go to m.opera.com/next on your android browser and click download to pc. download the jar. it will run with java and is awesome. it runs smoother and has more eye candy than any browser i ever tried. and i really like the keyboard that comes with it!
incubus26jc said:
i recommend everyone try out the opera mini beta 5 with android. Make sure you have Java installed on your build. I use the latest hero-vogue build. go to m.opera.com/next on your android browser and click download to pc. download the jar. it will run with java and is awesome. it runs smoother and has more eye candy than any browser i ever tried. and i really like the keyboard that comes with it!
Click to expand...
Click to collapse
Nice tip. This thing is wicked fast. I just tried 4.x yesterday but this is way better for touch screens!
zenulator said:
I don't have any of these problems with my builds so you might be missing a step or using the wrong files. Granted the xrom and cyanogen builds at vogue-hero are experimental/beta quality and hence why they stay there and don't go to the main vogue-android page. The latest xrom is using cupcake/donut built from the android master branch and is as fast as any build out there with the right setup and you can't use it with an existing data.img because it has a different code base. And sqsh has nothing to do with the level of performance of any build infact it should be faster than cramfs. It's the code that the system image is based off of and what extra apps and libraries and frameworks are included that determines how fast it's going to be.
Click to expand...
Click to collapse
OK, this is the first non-mssmison build I've tried in a while. I'm trying xrom 1.5. New data, and fresh files all around. Seems to be pretty good, but still the browser chokes a bit more than the non-sqsh build. Is there a way to limit app processes anymore? I looked for dev tools but it is not included.
hey zen, is it normal for me to be getting these fsck000.REC fsk0001.REC ect..
files on my storage card? if not, do you know what they are? the number just keeps goin up after every reboot and just keeps adding files.
Also, has anyone got a driver to work with Vista?
katmandu421 said:
OK, this is the first non-mssmison build I've tried in a while. I'm trying xrom 1.5. New data, and fresh files all around. Seems to be pretty good, but still the browser chokes a bit more than the non-sqsh build. Is there a way to limit app processes anymore? I looked for dev tools but it is not included.
Click to expand...
Click to collapse
Squashfs has nothing to do with the browser. If your compairing the1.5 xrom to the 1.4 then the differences are due to different browser builds aand the fact that the 1.5 build has some donut parts that 1.4 didn't have.
incubus26jc said:
hey zen, is it normal for me to be getting these fsck000.REC fsk0001.REC ect..
files on my storage card? if not, do you know what they are? the number just keeps goin up after every reboot and just keeps adding files.
Also, has anyone got a driver to work with Vista?
Click to expand...
Click to collapse
You can delete them.
Probably something to do with the basefiles, but I haven't tracked the cause yet.
They're the result of the automatic filesystem check on the sdcard fat partition on boot.
pmos69 said:
You can delete them.
Probably something to do with the basefiles, but I haven't tracked the cause yet.
They're the result of the automatic filesystem check on the sdcard fat partition on boot.
Click to expand...
Click to collapse
anyway patiently awaiting tattoo. it should be out today in some way or another. i just want to get a hold of the pure dump before it gets messed with.
So Dzo has a thread going on flashing Android to the NAND.... SWEET!!!!!!!!!
I am going to try it out, but I want input from you all.
there are SO MANY different flavors of Android (1.5 1.6 2.0 cupcake eclair ion) and I would like to try them all for myself, but obviously this isn't realistic, so I want to know what you guys like the best?
So please... Anyone, EVERYONE.... Which build do you like best on the Vogue?!
And if you tell your favorite, please tell us as well what basefiles build, Rootfs and zImage build you use for the Version
Otherwise we must ask that again...
160bpm said:
And if you tell your favorite, please tell us as well what basefiles build, Rootfs and zImage build you use for the Version
Otherwise we must ask that again...
Click to expand...
Click to collapse
Precisely bpm.
Ion 1.5 for its speed and stability.
Using latest basefiles.
I recommend a Donut build based on cyanogens work. He's added alot more features to the aosp making it more stable and including some of the best developments including the updated contacts and phone apps etc.
mssmison said:
I recommend a Donut build based on cyanogens work. He's added alot more features to the aosp making it more stable and including some of the best developments including the updated contacts and phone apps etc.
Click to expand...
Click to collapse
Wanna spoonfeed me your link?
mfpreach said:
Wanna spoonfeed me your link?
Click to expand...
Click to collapse
he means to port one(yourself) from cyanogens work
if you are flashing your phone and ridding yourself of windows, keep in mind that donut 1.6 does not have working GPS yet, so you if that is something you use, you might want to stick with a 1.5 build.
standard ion build is nice and stable.
xrom 1.5.4 build has some nice addons (better browser, customizable launcher and home screen numbers). the new launcher can be just a touch slow, however. this is what I use.
sense UI builds (tattoo, hero types) look sweet, and can run well if tweaked just right, but I hate that sms error, drives me insane. don't know if that annoying problem has been worked out yet.
if you never use GPS, flash zen's droid themed donut 1.6, or plemen's AOSP donut, and just wait until the rootfs/initrd get updated for GPS functionality. but remember that unless you keep your resolution in 320x480 from first boot, you will not always see all market apps.
for me, I won't be using NAND until we get full GPS functionality (which will be a while, if ever); I can't live without my turn-by-turn tts gps. i don't use bluetooth much, so I would not miss that. on the upside, NAND flashing gives you a r/w system, and usb mass storage, so you must weigh the pros and cons of what you use most. it'll be while before i'm flashing because i'm married to full GPS, and I don't see that being implemented on android on the vogue for a while as it is not the priority right now.
perfect solution: donut 1.6 with full gps, with market problem fixed for 240x320, then I'm flashing my NAND in a heartbeat and donating again ($50 this time) to dzo and the gang. and you can hold me to that.
hmmm something to think about I suppose....
One of the main reasons I love Android is because there is so much free software that utilizes the GPS.... I wonder just how long it will be until someone finds the missing link...
I personally like donut (1.6). I'm not a fan of the Hero UI or the Tatoo UI, I just like standard android.
I'm using all of the latest basefiles except the zimage, which I compiled from the git repository for the vogue kernel. The rootfs is the one found on dzo's website (it's the one required to even flash to NAND).
tatnai said:
if you are flashing your phone and ridding yourself of windows, keep in mind that donut 1.6 does not have working GPS yet, so you if that is something you use, you might want to stick with a 1.5 build.
standard ion build is nice and stable.
xrom 1.5.4 build has some nice addons (better browser, customizable launcher and home screen numbers). the new launcher can be just a touch slow, however. this is what I use.
sense UI builds (tattoo, hero types) look sweet, and can run well if tweaked just right, but I hate that sms error, drives me insane. don't know if that annoying problem has been worked out yet.
if you never use GPS, flash zen's droid themed donut 1.6, or plemen's AOSP donut, and just wait until the rootfs/initrd get updated for GPS functionality. but remember that unless you keep your resolution in 320x480 from first boot, you will not always see all market apps.
for me, I won't be using NAND until we get full GPS functionality (which will be a while, if ever); I can't live without my turn-by-turn tts gps. i don't use bluetooth much, so I would not miss that. on the upside, NAND flashing gives you a r/w system, and usb mass storage, so you must weigh the pros and cons of what you use most. it'll be while before i'm flashing because i'm married to full GPS, and I don't see that being implemented on android on the vogue for a while as it is not the priority right now.
perfect solution: donut 1.6 with full gps, with market problem fixed for 240x320, then I'm flashing my NAND in a heartbeat and donating again ($50 this time) to dzo and the gang. and you can hold me to that.
Click to expand...
Click to collapse
same here, bluetooth is a must for me though I don't speak on the phone without it, holding the phone is so cumbersome!
I like Zen's Droid-ION followed by Msmisson/Kb7sqi's Roger's.
Zen-droid-Donut-ION has been very smooth and I get to use it with 320 x 240 res. + with Donut, app variety in market is more.
tatnai said:
if you never use GPS, flash zen's droid themed donut 1.6, or plemen's AOSP donut, and just wait until the rootfs/initrd get updated for GPS functionality. but remember that unless you keep your resolution in 320x480 from first boot, you will not always see all market apps.
Click to expand...
Click to collapse
You mean resolution in defualt.txt right? Do you have to do it before creating a google account or just as long as your signing in the initial time when setting up your device? I've changed my default.txt but even after the change when I run Haret for the first time the resolution looks like normal qvga. Maybe I am not doing something right here's my 320 x 480 default.txt prior to signing into my google account the initial time...
I'm running Windows Mobile / Haret boot /11-16-09 Basefiles
sqsh:
http://www.mediafire.com/file/gjt2wo...stem_v233.sqsh
Rootfs (polyrythmic):
http://forum.xda-developers.com/show...&postcount=212
your default.txt is correct for 320x480. your google account does not matter, what matters is that the first time you make a data.img with a donut build (1.6) that you boot it with resolution of 320x480 (the lcd.density actually doesn't matter) and sign in to google services and use the market at that resolution. then if you change the resolution, it will actually still work for you for a while, but after a couple days or so the market will become limited again to apps designated OK for donut with lower resolutions. i don't know of a way to go back and fix it without creating a new data.img; if you want to run in a resolution other than 320x480, you could just archive your old data image each time, boot up a new on in 320x480 and log into the market, then shut down and boot back with your old resolution and data.img and you would be good again for a little while. hopefully soon enough all the apps (or all the ones that matter) will begin to show up at 240x320, but who knows how long that will take.
So will I notice a physical difference in resolution when android boots up on my vogue to reflect the 320 x 480 resolution? Larger icons, screen cut-off, etc.? Just wanting some evidence that the market thinks I'm not QVGA.
Reddog80p said:
So will I notice a physical difference in resolution when android boots up on my vogue to reflect the 320 x 480 resolution? Larger icons, screen cut-off, etc.? Just wanting some evidence that the market thinks I'm not QVGA.
Click to expand...
Click to collapse
depends what you set your lcd.density to - and lcd density of 110-120 on 240x320 will look similar to 320x480 at a density of 160. however, you should notice a slight squashed appearance at 320x480 because the aspect ratio is off, and the sreen appears just a touch fuzzy. when you boot into 320x428 or 240x320 for the first time, you will note a marked difference in the sharpness of the screen for that reason. like taking oily glasses off for the first time. you are booting from haret (not from nand) right? because the default.txt is not used when you boot from the nand.
The biggest thing I noticed with density 160 (besides the obvious blurring) is that the touchscreen is flakier (rounding / touch location -> pixel mapping issues? I haven't looked into how it's implemented yet...) when doing precise motions - for example, it's almost completely impossible to drag widgets in a Sense UI build or a stock build running with density 160 whereas a build running at native resolution is fine.
And re: the thread, Zen's Donut Droid-ION is my favorite build by far - fast, dead stable, reliable, and not too flashy.
He said over at http://forum.xda-developers.com/showpost.php?p=5137740&postcount=105 that he's going to have a working Eclair with radio and GPS hopefully today - I'm really excited for that.
Bump.
Any others out there?!!!
been running plemen's Donut AOSP, I must say it is even faster than dzo's droid donut. my new fav.
tatnai said:
been running plemen's Donut AOSP, I must say it is even faster than dzo's droid donut. my new fav.
Click to expand...
Click to collapse
Yes, do try Plemen's Donut AOSP. It is very fast and responsive. Most users switch away though due to screen lock issues and stuff. There is a fix and it is to restart your phone a few times and log into google your 2nd. Hope that helps
I don't have data to spare to test things myself until next month, and have a fairly stable PPP setup anyway.
But I figured if someone wants to experiment the following might be worth a shot.
What I've done is attach a zip with 4 sample options files for pppd that attempt to address issues I've seen with pppd. Specifically the crash with memory issues due to compression, and pppd dying when disconnected and needing to be restarted (eg by LeTama's v0.3 wrapper). If you want to try these out I would suggest using them in conjunction with his wrapper as I'm unsure how other versions may work: http://forum.xda-developers.com/showthread.php?t=824413
The 4 versions for testing are as follows:
option1
- Makes the buffer size used for compression as small as possible.
- Tries to make the connection persistant.
option2
- Disables compression.
- Tries to make the connection persistant.
option3
- Makes the buffer size used for compression as small as possible.
option4
- Disables compression.
To use them they will need to be copied to your /etc/ppp/ folder as "options" and you'll need to ensure it's readable.
If you don't know what I mean I suggest you don't bother trying this.
If you do know what you're doing then you can try experimenting with the different options and see if they make things better/worse.
option3 is probably the safest, option4 may be needed if things still crash due to memory issues with option3.
option1 would be the ideal, but I can't guarantee the persist option is possible.
If option1 or option3 prove to improve things and prevent the crash, then the values used could be slowly increased (to a max of 15) to see if crashes start happening again.
Anyway, just something else the more adventurous and tech savvy users out there with PPP issues can try.
Can I copy these over via ADB push while Android is running, or do I need to put them in the Android root folder so they'll get copied into place on reboot?
Well with Option 1 the data connections drops almost instantly, Option 2 is doing without drops for 10 min now, but it is too early to say if it's an improvement over the old options.
Does compression influence the connection speed? Option 2 works as fast as possible on HSDPA... Option 2 dropped after about 15 minutes when downloading from the market, but downloading from the market was much faster than before.
Should we be copying it as "options" with no file extension or "options.smd"?
Probably as options.smd, that's what I did and it seemed to have some effect...
Now testing option3, will mess with it for the rest of the day and see what happens. At first glance, it seems a bit slow, but that's anecdotal at best.
MAsterokki said:
Well with Option 1 the data connections drops almost instantly, Option 2 is doing without drops for 10 min now, but it is too early to say if it's an improvement over the old options.
Does compression influence the connection speed? Option 2 works as fast as possible on HSDPA... Option 2 dropped after about 15 minutes when downloading from the market, but downloading from the market was much faster than before.
Click to expand...
Click to collapse
Seems like I drew my conclusion from Option 1 too early, after a reboot it works great, I have been downloading MDJ newest rom for 10 min now which resulted 20% of 170mb (from multiupload). No drops untill now, definitely a huge improvement over the old options.smd. Thanks alot Hastarin!
question when i get to the ppp file in i see options.smd and a options.smd1 do i just add this new option to it or delete the old ones and replace with this one?
imphoking said:
question when i get to the ppp file in i see options.smd and a options.smd1 do i just add this new option to it or delete the old ones and replace with this one?
Click to expand...
Click to collapse
I would backup your original files first, although the orig options.smd is probably blank anyhow.
Replace the options.smd with the renamed options from hastarin.
Hastarin, do you happen to know the default options when we were using the default "blank" options.smd? Does it use compression etc. Thanks for your efforts!
noellenchris said:
Hastarin, do you happen to know the default options when we were using the default "blank" options.smd? Does it use compression etc. Thanks for your efforts!
Click to expand...
Click to collapse
The wrapper supplies nodetach, debug and something I can't recall atm (should be in IRC logs).
Compression will be used by pppd by default but I couldn't find information on what size buffer it uses by default.
Google pppd man page for more information.
You are right about options.smd being the safest option. Using options file may affect other things that use pppd if there are any.
Sent from my HTC HD2
Option1 seems to be working fine for me right now. I will report more in a few hours while I'm out.
Hey just wanted to say that I am checking out these options also. So far using option1 and I haven't had any data drops or freezes. Haven't been able to test it extensively yet but will over the next few hours.
With option 1 can you make sure you can switch between WiFi and data and back again? And that you can turn mobile data off and on? And perhaps airplane mode and back to be thorough?
Thanks
Sent from my HTC HD2
It seems after some time options.smd gets reset to blank by itself? Anyone noticed?
Sent from my HTC HD2 using XDA App
memin1857 said:
It seems after some time options.smd gets reset to blank by itself? Anyone noticed?
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
I haven't rebooted yet, but mine is still there and not blank. I will try to toggle wifi etc next. Otherwise it's still rolling well, no disconnects yet or hangs.
memin1857 said:
It seems after some time options.smd gets reset to blank by itself? Anyone noticed?
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
I set mine to read only in case this actually happens lol.
noellenchris said:
I haven't rebooted yet, but mine is still there and not blank. I will try to toggle wifi etc next. Otherwise it's still rolling well, no disconnects yet or hangs.
Click to expand...
Click to collapse
Lucky.. I still can't get mine to last longer than 5 seconds.
Ok with option1 I started experiencing some data freeze again. It happened while downloading a large file and then again when I switched to wifi tethering. The freeze actually freezes my entire system and then my phone runs really really slow. It may be the build that I am using so I am going to try an older build that did not seem to have this problem. I will run option1 for a while again and then try the others.
Option 1 is no good - I think the persist option keeps 3g "connected" even though I'm getting timeouts, instead of dropping and reestablishing data connection.
Will test the other options once I upgrade to 0.4 ril wrapper and S4 mdeejay kernel.
EDIT: oh yeah, I noticed though the default options.smd is blank, when pppd is running it creates a options1.smd in /etc/ and it has the words "user dummy" in it?
i am running cm7 nightly 44 on my DX and ive installed the v6 surpercharger with awesome results, when i tried out the 3g turbocharger, and kernel tweaks, i reboot like SM says and when i do, i get no data no cell signal wifi wont work, and airplane mode wont toggle. ive tried a few times with the same results. Ive searched and found nothing specific to my setup either. what am i doing wrong? any help would be appreciated! thanks!
You probably have 2.3.4 and its made for 2.3.3.
Sent from my DROIDX using XDA App
Actually I'm on 2.3.5 so that explains it too
It's weird... on the same phone wifi will be fine with stock but not okay with a custom rom.
Android version doesn't matter.
But I made a change to 3g TurboCharger that needs testing...
Edits to build.prop...
Code:
ro.ril.hsxpa=3
ro.ril.gprsclass=34
ro.ril.hep=1
ro.ril.enable.dtm=1
ro.ril.hsdpa.category=28
ro.ril.enable.a53=1
ro.ril.enable.a52=0
ro.ril.enable.3g.prefix=1
ro.ril.htcmaskw1.bitmask=4294967295
ro.ril.htcmaskw1=268449905
ro.ril.hsupa.category=9
ro.ril.def.agps.mode=2
ro.ril.def.agps.feature=1
ro.ril.enable.sdr=1
ro.ril.enable.gea3=1
ro.ril.enable.fd.plmn.prefix=23402,23410,23411
ro.ril.disable.power.collapse=0
Difference between this and update 2:
ro.ril.gprsclass=34 (instead of 12)
ro.ril.htcmaskw1=268449905 (instead of 14449)
I've actually seen gprsclass=32 in the past but 12 is the most common setting so I had used 12.
After researching today, seems that 32 would indeed be better than 12 BUT there is a new gprs class 34 so this would be a first for testing it at 34! (as far as I know) lol
So, I'd be interested in seeing if this is better than the 3G TurboCharger update 2 tweak
Ill try the update ill let you know. Thanks.
Or how would I implement that? Editing the build.prop?
yes.. if you have update 2 applied it only involved changing 2 entries
I applied both tweaks and edited the build.prop with the new values you suggested and with 34 I got no 3g no cell signal airplane wouldn't toggle and error when turning on wifi. I then tried 32 and no 3g no cell signal and error for wifi but airplane would toggle then.
ok.. 34 is out of the equation...
At 32 its the same as before
Well I wonder what's not working then I apply the kernal tweaks first then 3g Turbo then reboot. All with script manager
Does the baseband matter?
Does the 3g turbocharge work on all android devices or strictly the DX? I want to do this on my Evo 4g, but the process seems a bit over my head.
Is the increased 3g speed attributed to ONLY the changed values in the build.prob? If so, can this be done manually by editing build.prop with a text editor, to achieve the same results?
Evo! said:
Does the 3g turbocharge work on all android devices or strictly the DX? I want to do this on my Evo 4g, but the process seems a bit over my head.
Is the increased 3g speed attributed to ONLY the changed values in the build.prob? If so, can this be done manually by editing build.prop with a text editor, to achieve the same results?
Click to expand...
Click to collapse
I don't know about all android devices, but I have an EVO 4g, and it seems to work fine for me. Still messing with it cause i think the 98kickasskerneltweak isn't working, but I'm working on that now
Dramanis420 said:
I don't know about all android devices, but I have an EVO 4g, and it seems to work fine for me. Still messing with it cause i think the 98kickasskerneltweak isn't working, but I'm working on that now
Click to expand...
Click to collapse
Me too...
FYI...
Updated September 3: - V6 SuperCharger Update9 Beta3
Fixed - Cleaning of local.prop. It was leaving a mess behind.
Enhanced - User notification of events a little more
Updated September 3: - 98KickAssKernelTweaksInstallerUpdate3 test3
Fixed - A big error (I doubt the io scheduling tweaks were being applied in Update 3 test 2)
Improved - Application of io scheduling tweaks so that it is much more selective and safer
Runs - 98kickasskernel after creating 98kickasskernel!
Notifies - You of the I/O Scheduler in use - Before AND After running 98kickasskernel
Defaults - To using Deadline (of available) instead of Noop io schedular.
Updated September 3: - 3GTurboChargerInstallerUpdate3 test 9
Added - Complete menu with 4 configurations!
Installs - /sdcard/3GTurboCharger.txt which has specific details of the 4 options.
This is what it looks like:
Code:
================================================
\\\\ 3 G T U R B O C H A R G E R - M E N U ////
==============================================
1. Fast?
2. Faster?
3. Fastest?
4. Experimental!
5. UnTurboCharger
6. REBOOT! (WARNING - There is NO Warning!)
7. Exit
Your Mileage WILL Vary!
View settings in /sdcard/3GTurboCharger.txt!
Test all 4 to see which works best for you!
The SpeedTest.Net app is highly recommended :)
Please enter option [1 - 7]:
Download from the usual place http://forum.xda-developers.com/showpost.php?p=15948434&postcount=1127
All 4 updated files are 100% untested by me... so good luck
How much speed increase does this actually help
Sent from my DROIDX using xda premium
Ok a couple of more updates... on account of me being a n00b
Updated September 4: - 98KickAssKernelTweaksInstallerUpdate3 test4
Tweaked - io scheduling tweaks some more so that it is even more selective and safer
Updated September 4: - 3GTurboChargerInstallerUpdate3 test 10
Fixed - Yesterday's file (Update 3 test9) didn't apply ANY variations so now it's fixed.
Added - Another configuration. Some people reported great results with yesterday's version (removes limits?) so added a "nulled" configuration.
what does 98KickAssKernelTweaks do?
Thank to Workshed for finding the errors!
Universal Script for Android Phone No more RING lag phone rings by the 2nd ring and screen and caller ID pops right up.
There are a few vers to test I am uploading my ver of it now it has a few tweaks removed for the CPU and kernals. But added a few thats it works much better now and it will get along with other Twaeks like supercharger.
All Zips from this post are flashable from recovery.
Here is the link to the OP I found it on. http://forum.xda-developers.com/showthread.php?t=1205259
This Is VER 2 there where errors in the 1st ver and also on the OP that i found this on.
I patched it up and also tested it and the file is running great without any errors as far as I can see.
By the end of the 2nd ring the phone lights right up with caller ID and rings even with custom ringtone. The dialer when placing a call is so much faster when it opens it just POPS.
#!/system/bin/sh
#00Ring_lag_v2 computerfreek#
MAX_PHONE() # remove lag when answering phone calls
pidphone=`pidof com.android.phone`;
if [ $pidphone ];
then
echo -17 > /proc/$pidphone/oom_adj; # exclude com.android.phone from oom-killer;
renice -20 $pidphone; # set highest nice level for com.android.phone;
log -p i -t ScreenState "*** MAX phone *** set oom_adj(-17) and nice(-20) for com.android.phone";
exit;
else
sleep 1;
MAX_PHONE;
# Background process to check screen state;
(while [ 1 ];
do
cat /sys/power/wait_for_fb_wake;
AWAKE_MODE;
cat /sys/power/wait_for_fb_sleep;
SLEEP_MODE;
then
# One-time process to optimize com.android.phone;
(while [ 1 ];
sleep 10;
MAX_PHONE;
; \ fi
Click to expand...
Click to collapse
Here is the Links
http://dl.dropbox.com/u/17779317/New%20folder/00Ring_Lag_v2.sh
http://dl.dropbox.com/u/17779317/00Ring_Lag_v2 Raw TEXT to place in a file and add it to your init.d folder.
http://dl.dropbox.com/u/17779317/ringlagv2/00ring_lag_v2.zip Flashable Ver 2
If you are runing the v4.0 of worksheds GSB then here is a Patch that will replace the One on ROM with V2 http://dl.dropbox.com/u/17779317/ringlagv2/00ring_lag_v2_GSB_patch.zip
computerfreek said:
OH that sucks ! Download prankdial from market and prank your self! lol it will call you.
If you pm me your number and I can call you from my gv.
Hows the phone runing with other things after adding the script?
Click to expand...
Click to collapse
Sorry to jump threads on you, I didn't want to clog up CondemnedSoul's thread with questions/comments specifically about this script....
After loading & rebooting, I didn't notice any problems. The phone seems a bit snappier with this in general, although I still haven't tested the incoming calls thoroughly yet. I am running this script on Comndemned v17 S2h in combination with the v6 SuperCharger, and the 3G & Kernel Tweaks. Based on a recommendation from CS, I also modified the following line in the build.prop from
ro.telephony.call_ring.delay=500
to
ro.telephony.call_ring.delay=0
I haven't noticed any conflicts or issues yet, but I wouldn't necessarily classify myself as a heavy user.
I have another question for you. Since it was easy enough to modify the CPU speed, if I change the governor in the following line
GOVERNOR_SCALE="ondemand";
to smartass so that it will match my CM7 performance settings, will that cause any issues? Does this script need to be set to ondemand in order to work correctly?
computerfreek said:
I found this Universal Script for Android Phone it just ROCKS I am testing it on GSB3.8 workshed and now when I call my cell it starts ringing after just 1 ring! I tested it on Gin-sen-tazz but I don't think it is working on GINGER SENSE ROMS
Here is the link to the fourm I found it on. http://forum.xda-developers.com/showthread.php?t=1205259
The only thing I changed on the it was the MAX CPU from 800 to 710 and it all seems to be working great. I will see in a few hours after leting the phone sit and then calling it.
Hope this will help Others on CM7 GB roms.
Here is the one I am useed on my phone. http://dl.dropbox.com/u/17779317/00tweaks
Click to expand...
Click to collapse
So all you have to do is copy 00tweaks and put it in your init.d folder???
PillClinton said:
Sorry to jump threads on you, I didn't want to clog up CondemnedSoul's thread with questions/comments specifically about this script....
After loading & rebooting, I didn't notice any problems. The phone seems a bit snappier with this in general, although I still haven't tested the incoming calls thoroughly yet. I am running this script on Comndemned v17 S2h in combination with the v6 SuperCharger, and the 3G & Kernel Tweaks. Based on a recommendation from CS, I also modified the following line in the build.prop from
ro.telephony.call_ring.delay=500
to
ro.telephony.call_ring.delay=0
I haven't noticed any conflicts or issues yet, but I wouldn't necessarily classify myself as a heavy user.
I have another question for you. Since it was easy enough to modify the CPU speed, if I change the governor in the following line
GOVERNOR_SCALE="ondemand";
to smartass so that it will match my CM7 performance settings, will that cause any issues? Does this script need to be set to ondemand in order to work correctly?
Click to expand...
Click to collapse
That shouldn't cause any issues at all. It should just default your governor to smartass instead of ondemand.
CondemnedSoul said:
That shouldn't cause any issues at all. It should just default your governor to smartass instead of ondemand.
Click to expand...
Click to collapse
Done, & no issues to report yet. I also changed
GOVERNOR_FREQENCY_MIN="245760"; to GOVERNOR_FREQENCY_MIN="480000"; for the purpose of matching my CM7 settings.
bigdaddyblues said:
So all you have to do is copy 00tweaks and put it in your init.d folder???
Click to expand...
Click to collapse
Well you chave to copy and set the permissions.
Or use flashable ver of the 710MHZ for eris http://dl.dropbox.com/u/17779317/00tweaks.zip
PillClinton said:
Done, & no issues to report yet. I also changed
GOVERNOR_FREQENCY_MIN="245760"; to GOVERNOR_FREQENCY_MIN="480000"; for the purpose of matching my CM7 settings.
Click to expand...
Click to collapse
I don't think matching it matters so much as it is set to RUN the the CPU speed set 1 time on start up be for cm7 sets it's speed. CM7 looks like it will override it after it's booted. So even if you load the 710MHZ ver and have cm7 set at 600mhz it will drop to 600 after cm7 is fully loaded.
I think there may be a conflict between this script & zeppelin's v6 supercharger. I had 3 screen redraws today for the first time in ages. When I was using the supercharger by itself, I had no problems.
I removed the 00tweaks & rebooted for now.
Sent from my Condemned Eris
One other question about the 00tweaks. I looked through the script & noticed it has some tweaks built in for dialer one. Since I don't use dialer one, could it be modified to tweak go contacts ex instead?
Sent from my Condemned Eris
PillClinton said:
One other question about the 00tweaks. I looked through the script & noticed it has some tweaks built in for dialer one. Since I don't use dialer one, could it be modified to tweak go contacts ex instead?
Sent from my Condemned Eris
Click to expand...
Click to collapse
I was thinking the same thing I don't see why not it looks like it will work for any service app I don't know if contacts is a service or not. You can PM tazz811 on the OP. And see if you can help you with that. Link to OP If you get it working for other apps please post back here so we can all use it. http://forum.xda-developers.com/showthread.php?t=1205259
PillClinton said:
I think there may be a conflict between this script & zeppelin's v6 supercharger. I had 3 screen redraws today for the first time in ages. When I was using the supercharger by itself, I had no problems.
I removed the 00tweaks & rebooted for now.
Sent from my Condemned Eris
Click to expand...
Click to collapse
I have been testing it with and without supercharger and it seems fine for me. However it be nice if we can just make a new script for just rintone lag so there will be no conflicts at will even if your just OC with CPUboost.
I think we will see soon DEV apping just the phone LAG stuff into there ROMS. This way we can just boost or OC with any other apps or scripts.
I don't think they are playing well. I don't usually use the super charger script, but had applied multi tasker setting after a few apps were killed by system that I wanted running in background. First, I notice extremely poor battery life - some service kept the phone awake all night so it didn't fully charge. This also happened yesterday with xda app, but don't know what did it last night. Also, notice that the super charger minfree values did not stick, so the 00tweaks must over ride them at startup. I was having the background app problem before the tweaks, so I suspect that the super charger kernel tweaks conflict with the 00tweaks. Undid both for now
Sent from my ERIS using XDA App
Getting rid of the 00Tweaks seems to have solved my screen redraw issue for the moment. I was also having some issues with lag after leaving certain apps, and that is gone too.
klobkelosh said:
I don't think they are playing well. I don't usually use the super charger script, but had applied multi tasker setting after a few apps were killed by system that I wanted running in background. First, I notice extremely poor battery life - some service kept the phone awake all night so it didn't fully charge. This also happened yesterday with xda app, but don't know what did it last night. Also, notice that the super charger minfree values did not stick, so the 00tweaks must over ride them at startup. I was having the background app problem before the tweaks, so I suspect that the super charger kernel tweaks conflict with the 00tweaks. Undid both for now
Sent from my ERIS using XDA App
Click to expand...
Click to collapse
What desktop launcher are you rinning ? I am running launcherpro plus with no redraws.
Adw stock with cm7.
Sent from my ERIS using XDA App
klobkelosh said:
Adw stock with cm7.
Sent from my ERIS using XDA App
Click to expand...
Click to collapse
Maybe it the laucher or the ROM your on mine is working great, But has also been the same with or without supercharger is I do not get redraws or any teaking. I am Runing worksheds last release 3.8 and it is working great. I never use ADW so can't tell you if it is that or not. As if I test or use a rom and it has ADW or any other lanucher on it I always add lancher pro on it and resign the rom befor I even install it.
Maybe you can talk to TAZZ811 on the like from the OP. and see if he can help use out with just the phone lag tweak with no mem or kernals tweaks. Thats what I think we need.
I am sicking with it on my phone I hate missing calls And with this tweak my phone lights right up with the caller ID and it's ringing just as the 2nd ring starts. I hope others try this out and see if they get the same thing.
It maybe as easy as just removing or #out the kernal and mem tweaks on the script.
The 00tweaks universal script does a lot of things I'd rather control elsewhere or not muck with. So, I isolated the portion of the script that pertains to the ring lag. I pushed the attached file to the init.d folder.make sure you remove the .txt part. No adverse effects that I notice yet. Phone sounds on the second ring. Good luck.
klobkelosh said:
The 00tweaks universal script does a lot of things I'd rather control elsewhere or not muck with. So, I isolated the portion of the script that pertains to the ring lag. I pushed the attached file to the init.d folder.make sure you remove the .txt part. No adverse effects that I notice yet. Phone sounds on the second ring. Good luck.
Click to expand...
Click to collapse
Nice, I did the same thing. I tried leaving in a few of the other tweaks to see if I notice any difference (either way). If I start running into problems again, I'll check your version out.
klobkelosh said:
The 00tweaks universal script does a lot of things I'd rather control elsewhere or not muck with. So, I isolated the portion of the script that pertains to the ring lag. I pushed the attached file to the init.d folder.make sure you remove the .txt part. No adverse effects that I notice yet. Phone sounds on the second ring. Good luck.
Click to expand...
Click to collapse
Nice I was testing with that also. I hope it all works out for you with your setup. I can make a flash .zip ver of each one to make it easy for others.
Thanks for testing this out. I hope DEV's just start rolling it in there roms.
klobkelosh said:
The 00tweaks universal script does a lot of things I'd rather control elsewhere or not muck with. So, I isolated the portion of the script that pertains to the ring lag. I pushed the attached file to the init.d folder.make sure you remove the .txt part. No adverse effects that I notice yet. Phone sounds on the second ring. Good luck.
Click to expand...
Click to collapse
klobkelosh, sorry for the newbie question... how do i get to the init.d folder? and i tried deleting the extension in file manager with no luck