Hey guys i was looking arroun xda and stumbled appon this. http://forum.xda-developers.com/showthread.php?t=1961353.
EDIT: TESTED DOES NOT WORK!!
It says it
-Increase internet speed (EDGE, 3G, WLAN, VPN). Works with all browsers including Opera with all APNs.
- Compressing pages and then decompressing for less data usage & smooth browsing.
- Bypass slow downloads and let you full speed downloads from some file sharing site which requires premium account for fast downloads. Like depositfiles etc.
- Boosting network signal strength so to have no call drops.
Click to expand...
Click to collapse
I have been running iy for about 7 hours now, and have to say that it does do some of what it claims.
3g speed seems to have increased and remain steady at over 1mbps. However wifi (wlan) seems no faster but no worse either. I did not test vpn as i do not have one setup.
The browser compression also seems to work, as pages load quicker. It also seems the whole page loads all at once instead of piece by piece.
The full speed downloads dosent seem to work, at least not from depositfiles.
The network signal boot also dosent work, as my db's are the same as usual, high 80s to low 90s.
Even though several things dont seem to work, they dont break anything either. I think just for the 3g tweak and browser compression, it is worth it. Also i know it says for android 2.3.6+, but works fine on 2.3.4.
I don't expect much from these type of tweaks and think they're more placebo than anything. There's nothing on the ROM side that can improve signal.
Browser compression sounds like an interesting idea. If you're familiar with the protocol rsync, it can use compression to transfer and use less bandwidth. However, I haven't heard of compression remote webpages prior to sending them which is really the only way this would logically work. That doesn't mean it doesn't exist.
The 3g speed tweak I'm also wary of. I think it may be placebo as network speeds vary and Verizon can already achieve 1mbps+ on their network.
As far as the bypassing slow downloads, that's definitely possible; however, it sounds wrong.
The only differences between Android 2.3.6 and 2.3.4 are a few bug fixes.
Edit: A little extra feedback after viewing the script.
I don't think any of the service lines will actually work as some of these look designed for init.rc, not init.d which is shell scripts.
As far as the network signal strength booster, it calls a legacy device script (goldfish which is the emulator and not a real device).
Not sure about the speed tweaks or slow download bypassing.
tiny4579 said:
I don't expect much from these type of tweaks and think they're more placebo than anything. There's nothing on the ROM side that can improve signal.
Browser compression sounds like an interesting idea. If you're familiar with the protocol rsync, it can use compression to transfer and use less bandwidth. However, I haven't heard of compression remote webpages prior to sending them which is really the only way this would logically work. That doesn't mean it doesn't exist.
The 3g speed tweak I'm also wary of. I think it may be placebo as network speeds vary and Verizon can already achieve 1mbps+ on their network.
As far as the bypassing slow downloads, that's definitely possible; however, it sounds wrong.
The only differences between Android 2.3.6 and 2.3.4 are a few bug fixes.
Click to expand...
Click to collapse
The browser compression and 3g seem to work, pages load faster and seem snappier. I know vzw is capable of 1mbps, but i rarley ever got half that before the tweak. Now i get it consitentlty at all times of the day. I dont think its placedo, and the the poll on that thread suggest people are happy with it. Its worth a shot if you have some free time. And its easy to remove if you dont like it, just delete 2 files and a folder
cmlusco said:
The browser compression and 3g seem to work, pages load faster and seem snappier. I know vzw is capable of 1mbps, but i rarley ever got half that before the tweak. Now i get it consitentlty at all times of the day. I dont think its placedo, and the the poll on that thread suggest people are happy with it. Its worth a shot if you have some free time. And its easy to remove if you dont like it, just delete 2 files and a folder
Click to expand...
Click to collapse
Try running it from the terminal or adb shell by doing sh init.d script name and I'm pretty sure it will bomb out on you like it did for me. I tried the bottom one and the second attachment from the OP there.
Below is my error:
Code:
[email protected]:/storage/sdcard0 # sh netforks_tweak
netforks_tweak[12]: syntax error: '(' unexpected
tiny4579 said:
Try running it from the terminal or adb shell by doing sh init.d script name and I'm pretty sure it will bomb out on you like it did for me. I tried the bottom one and the second attachment from the OP there.
Below is my error:
Code:
[email protected]:/storage/sdcard0 # sh netforks_tweak
netforks_tweak[12]: syntax error: '(' unexpected
Click to expand...
Click to collapse
Lol, never even thought of trying that. Your right i het the same error. The init-goldfish.sh file that the init.d script runs also fails on execution, but that is a stock system file. I wonder why my 3g speeds are better? Im getting double what i usually get, and its actually consistent and not bouncing all over the place. Mabey vzw put up a new tower or something. And i guess with increased speed the browser would seem snappier. Oh well thought i stumbled on something cool, but its just garbage i guess. Thanks for clearing it up tiny.
cmlusco said:
Lol, never even thought of trying that. Your right i het the same error. The init-goldfish.sh file that the init.d script runs also fails on execution, but that is a stock system file. I wonder why my 3g speeds are better? Im getting double what i usually get, and its actually consistent and not bouncing all over the place. Mabey vzw put up a new tower or something. And i guess with increased speed the browser would seem snappier. Oh well thought i stumbled on something cool, but its just garbage i guess. Thanks for clearing it up tiny.
Click to expand...
Click to collapse
According to the dev, the ( error is ok.
So, if you want to test it again to verify, type getprop and see if anything shows from the tweaks script as far as the setprop lines. I have a feeling nothing will but I want to validate 100% that this doesn't work.
I've done some testing on my own by making shell scripts and confirming an error should not bomb out the whole script but just abort at the point of the error.
But really, this thing does nothing, even zeppelinrox shot it down.
tiny4579 said:
According to the dev, the ( error is ok.
So, if you want to test it again to verify, type getprop and see if anything shows from the tweaks script as far as the setprop lines. I have a feeling nothing will but I want to validate 100% that this doesn't work.
I've done some testing on my own by making shell scripts and confirming an error should not bomb out the whole script but just abort at the point of the error.
But really, this thing does nothing, even zeppelinrox shot it down.
Click to expand...
Click to collapse
No nothing from the script shows in getprop. I would say the whole things a bust.
Related
In the advanced settings for the Internet connection there are options to enable these two things - do they actually help?
(bump)
Has no one ever tested these?
we're waiting on your indepth report before we try it!
just my thoughts but I doubt it will do anything.as I understand it header compression requires both ends have it enabled to work, so I would assume is pretty rare.
I've never used it either, but from what I know it's not gonna make anything faster. You would just transport a marginal amount less data. To be honest, I sort of shrugged when I heard of it and didn't think it was a big deal. I obviously could be wrong about that though.
Have you tried it Shasarak?
I've had both options switched on for a while and haven't noticed any ill effects, but it's hard to be sure. Is there a good source of compressible data somewhere that I could try downloading for benchmark purposes?
Back in 28kb/s modem days, software compression made a big difference to performance; you could easily double download speeds for a text file (although not, of course on a zip file, a video, or a jpeg or png image).
NEW THREAD HERE
http://forum.xda-developers.com/showthread.php?t=765822
THIS IS NOW AVAILABLE IN EXT2, EXT3, AND EXT4 VARIATES(DOES NOT REQUIRE CUSTOM KERNEL!)
IF YOU ARE USING JH2/JH3 FIRMWARE, READ THIS POST, IT IS VERY VERY VERY IMPORTANT:
http://forum.xda-developers.com/showpost.php?p=7650658&postcount=312
The reason this step is important is that the JH2 firmware is a test build, and as a test build it has GPS logging enabled... this uses an absolutely ludicrous amount of storage space- and the real kicker? It uses the space OUTSIDE of this fix, meaning your phone will encounter low space warnings very quickly if not instantly upon applying the fix!
THIS NOTE IS FOR EVERYONE. THESE FIXES WORK BETTER FROM A FRESH FLASH. THEY *CAN* WORK WITHOUT A CLEAN FLASH BUT REALIZE THAT YOU ARE POTENTIALLY PUTTING YOUR DATA AT RISK!
What this does (Shamelessly stolen from RyanAZ's OP)
Creates a VIRTUAL EXT2 filesystem inside the stock RFS filesystem on the internal SD card, with a 4KB block size. This means that this lag fix creates a buffer between the real filesystem and the android system. This buffer should reduce the amount of disk I/O required for all operations by utilizing EXT2 buffering, as well as not writing file access times to disk, etc.
PROS
Doesn't rely on external SD
Easy to do
Reverse-able
Real, noticeable performance increases outside of Quadrant (Seriously don't pay attention to Quadrant, but if that's what you care about this will make your pants tighter)
CONS
Uses EXT2 file system which is non-journaled and CAN become corrupted, frequent backups are strongly recommended! (2.2 Implements error checking every 30 mounts)
It's also up for debate as to whether this adds extra strain on your internal memory.
1.0 SECTION WILL FOLLOW 2.0 STUFF
AS WITH ANY FIX: READ THE INFO, KNOW WHAT YOU'RE DOING, AND UNDERSTAND POTENTIAL CONSEQUENCES!
LINKS TO GET THE GOODS BELOW!!
The RyanZA version that does EXT2 is Available at the thread linked below
http://forum.xda-developers.com/showthread.php?t=751864
RyanZA has put out an APK version of the fix for people less comfortable doing the update.zip or batch file methods! (This is the V1 lagfix, so for people having issues with the newer fixes this one might work for you!)
TEMPORARILY DOWN UNTIL VERSION 2.3
http://forum.xda-developers.com/showthread.php?t=760571
There is also an update.zip version that does EXT2, EXT3 (1500 Quadrant), or EXT4 (1800 quadrant) versions thanks to Tayutama! I've tested this to work on JH2, and JM5 firmwares! There is also a special version for Captivate JH2 (It also works for JH3) that fixes the GPS Log issues so no need to edit the XML's yourself!
http://forum.xda-developers.com/showpost.php?p=7632258&postcount=208
praveer01 threw up a handy writeup for those of you running Unbuntu or any other Linux system:
http://forum.xda-developers.com/showpost.php?p=7671640&postcount=583
READ THE INSTRUCTIONS AND REMEMBER THIS IS *VERY* BETA, NEITHER RYANZA OR MYSELF WILL TAKE RESPONSIBILITY FOR MELTING YOUR DEVICES OR KILLING YOUR DOG IF THIS FAILS. That said, this thread has been very good about helping people who borked their Captivates with 1.0
Here's the reasons you'd want to do this:
Benefits over version 1
1.7GB of application data available, with no data loss. (Up from < 1GB)
e2fsck of the EXT2 partition on each boot. (To scan and fix corruption!)
Correct busybox version included! YES! (Because no one can get it right =P)
/app directory included in the fix for faster application installs.
Mounts instead of symlinks for extra performance as OS does less work (about 100 or so more quadrant).
2.3 Changelog
/dbdata has been removed. This fixes maps issues.
/app-private is now a symlink to /app/app-private. This fixes paid apps issues.
2.2 Changelog
/app-private is included
A second EXT2 partition is created in fast /dbdata storage. /dbdata/databases are moved inside here for increased speed in applications that use it. (System apps mostly, I think)
Proper parameters for e2fsck.
0% space reserved in the EXT2.
EXT2 partition reduced from 1.7GB to 1.5GB to allow more space for captivate users.
Running from a stock install of JH2 I'm currently getting 2300 quadrant scores with ALL AT&T BLOATWARE AND TW ENABLED!
IF YOU'RE NEW TO THIS KIND OF THING, OR ARE WORRIED ABOUT POSSIBLY HAVING TO REFLASH YOUR PHONE, YOU PROBABLY SHOULD WAIT A LITTLE WHILE FOR MORE PEOPLE TO TEST THIS!
___________________________________________________________________________
Found this over in the i9000 forums and tested it myself- I'm getting 2100+ quadrants scores with the stock Captivate kernel and it doesn't hang up on the I/O portion like all the other fixes... in addition you don't require an SDcard for this to work.
Original thread:
http://forum.xda-developers.com/showthread.php?t=748596
One of the folks over there created a one-click lagfixer and it DOES work for the Captivate:
http://forum.xda-developers.com/showthread.php?t=749495
FOR PEOPLE WHO DONT WANT TO READ THE ORIGINAL THREAD
This fix creates a 1GB file formatted in EXT2 and moves all of your apps, data, dbdata into it which DRASTICALLY improves I/O performance. One advisory SHUT YOUR PHONE DOWN PROPERLY, this means no yanking the battery out. Due to it being EXT2, non graceful shutdowns CAN cause corruption.
Edit: No wake up lag either- not sure if that's due to using a non-modded kernel or because the ext2 file is located on the internal memory.
Edit 2: Make *SURE* before attempting this that you have Busybox 1.17.1 or the boot animation script calls won't work!
Link to Busybox 1.17.1
http://forum.xda-developers.com/showpost.php?p=7574130&postcount=229
DO NOT UPGRADE BUSYBOX TO 1.18! 1.18 REMOVES MAKEFS WHICH IS NECESSARY FOR THIS PROCESS
Edit 3: I haven't used the stock Captivate ROM for a while, but this feels quite fast- Also worth noting that this SHOULD work with any ROM- including i9000, I might test that later but I'm enjoying having functioning haptic feedback. 2200 Quadrant with Shootme and market running! Since seeing is believing I've thrown in a screen cap.
Confirmed working with JM5 ROM
IF YOU USE A MAC OR JUST CAN'T GET ADB TO WORK THIS FIX CAN BE PERFORMED WITHOUT A PC- SEE THE POST BELOW:
http://forum.xda-developers.com/showpost.php?p=7583565&postcount=116
Ha! it worked thanks dude you should rename this thread with brackets. " [Fix][Lag] Alternative by {author name} - alpha " .. so it can gain more attention. Just we need two more fixes GPS and my attenna issues then i'm good with my captivate.
[edit]omg my phone is flying see this is how my phone should have been out the box it flies!
rebooting from this now. I should not that I had to run the shell script manually because it kept not prompting me for SU...? No biggy though.
Will test, can't post screen from work though.
Edit: running quadrant....
Edit: ... *thud* 1961, 2237 ( FB, gmail, etc were running & syncing in background last time!)
mykenyc said:
Ha! it worked thanks dude you should rename this thread with brackets. " [Fix][Lag] Alternative by {author name} - alpha " .. so it can gain more attention. Just we need two more fixes GPS and my attenna issues then i'm good with my captivate.
[edit]omg my phone is flying see this is how my phone should have been out the box it flies!
Click to expand...
Click to collapse
Title change done!
Glad this is working for you guys, I've tried every fix so far and this one is MILES ahead of the others in terms of real world improvement (At least for me).
Zilch25 said:
Title change done!
Glad this is working for you guys, I've tried every fix so far and this one is MILES ahead of the others in terms of real world improvement (At least for me).
Click to expand...
Click to collapse
I agree! waking up this morning in fear of being fired from my job, this made my day a little lol.
Besides downloading the .zip file, do i need anything else?
Also, i am assuming we install this by booting into recovery mode?
Thanks
Sent from my SAMSUNG-SGH-I897 using XDA App
LockeCPM4 said:
Besides downloading the .zip file, do i need anything else?
Also, i am assuming we install this by booting into recovery mode?
Thanks
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Nope just run lagfixme.bat this in the zip file, run and leave your phone screen on so you can see the root request permission.
LockeCPM4 said:
Besides downloading the .zip file, do i need anything else?
Also, i am assuming we install this by booting into recovery mode?
Thanks
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Nope, you don't need anything else. Also nope, no recovery mode shenanigans, just unzip the file, turn on debugging mode on your phone, plug her in, and run the batch file!
Also you MUST undo any prior lag fix
Sent from my SAMSUNG-SGH-I897 using XDA App
again, those high quadrant scores mean nothing unless you get no lag in real world testing. Such tests can be done in the following apps: Dolphin HD browser, facebook, twitter, touchdown, k-9 email
All common applications that have serious lag on the SGS. Assuming that this method does fix I/O problems (Especially the I/O quadrant tests), there should be no lag in those apps. Anyone try?
I noticed this in the original thread:
EDIT3 09 aug 0033HKT:
it's not for the benchmark only, instead, it has very good effects on ur phone's io
Click to expand...
Click to collapse
Sounds good, I'll give it a try
andy2na said:
again, those high quadrant scores mean nothing unless you get no lag in the following apps: Dolphin HD browser, facebook, twitter, touchdown, k-9 email
All common applications that have serious lag on the SGS. Assuming that this method does fix I/O problems (Especially the I/O quadrant tests), there should be no lag in those apps. Anyone try?
Click to expand...
Click to collapse
I know you have your reservations about these fixes, and you've been very vocal about your opinions on the matter. I happen to agree with you on most points, but as someone who has tried all of these, I can tell you this doesn't feel like the placebo effect. I'll install DolphinHD and toy with it, but everything I've messed with so far seems much snappier. Feel free to try it yourself, it literally takes less than 5 minutes to install, and is completely reverse able.
Edit: So far with dolphin HD things feel snappy, the only exception is pages absolutely laden with flash lite ads... but that's not really an I/O issue, if you've got any particular web site recommendations I'd be glad to check them out and let you know my mileage
So far so good, I recently erased my phone (130mb lag fix not big enough). And this is working wonderfully so far, dolphon browser HD(my favorite browser) works very fast. So far so good, I'll report back when I've tried it for the whole day.
Zilch25 said:
I know you have your reservations about these fixes, and you've been very vocal about your opinions on the matter. I happen to agree with you on most points, but as someone who has tried all of these, I can tell you this doesn't feel like the placebo effect. I'll install DolphinHD and toy with it, but everything I've messed with so far seems much snappier. Feel free to try it yourself, it literally takes less than 5 minutes to install, and is completely reverse able.
Edit: So far with dolphin HD things feel snappy, the only exception is pages absolutely laden with flash lite ads... but that's not really an I/O issue, if you've got any particular web site recommendations I'd be glad to check them out and let you know my mileage
Click to expand...
Click to collapse
Thanks! I'll give it a try as I don't like being tied down to 130mb for application storage using the NAND fix.
Basic usage should be snappy:
- opening\closing\switching tabs
- scrolling with the volume buttons
- pinch zooming
- loading multiple pages
On stock, and even mimocan's fix, it would lag horrible to the point of unusability.
The only way to make it run smoothly and quickly was to move all your /data/ to the /dbdata/ on the NAND (but limited to 130mb of app space)
I guess my install question wasnt answered. You said run the .BAT file, do i run it on my pc? And what software on the pc side must i have installed?
Thanks for helping a noob!
Sent from my SAMSUNG-SGH-I897 using XDA App
Zilch25 said:
I know you have your reservations about these fixes, and you've been very vocal about your opinions on the matter. I happen to agree with you on most points, but as someone who has tried all of these, I can tell you this doesn't feel like the placebo effect. I'll install DolphinHD and toy with it, but everything I've messed with so far seems much snappier. Feel free to try it yourself, it literally takes less than 5 minutes to install, and is completely reverse able.
Edit: So far with dolphin HD things feel snappy, the only exception is pages absolutely laden with flash lite ads... but that's not really an I/O issue, if you've got any particular web site recommendations I'd be glad to check them out and let you know my mileage
Click to expand...
Click to collapse
Tested:
Gmail, FB (official), GVoice, messaging, TWC, stock browser, andoku (yeah, I can SEE it faster. and thats a simple app!)
LockeCPM4 said:
I guess my install question wasnt answered. You said run the .BAT file, do i run it on my pc? And what software on the pc side must i have installed?
Thanks for helping a noob!
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Plug it into your pc making sure the USB debugging is on. Download the zip file, extract all of it. Run the Lagfixme.bat and make sure you leave the phone screen on (tap it if low time out) to accept the super user permission request. After that it will finish on it's own. Just reboot the phone by shutting it down. The zip file contains all the necessary files.
Edit: and make sure your phone is rooted / has the drivers installed!
LockeCPM4 said:
I guess my install question wasnt answered. You said run the .BAT file, do i run it on my pc? And what software on the pc side must i have installed?
Thanks for helping a noob!
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
The zip file actually contains a copy of the adb as needed, so other than the drivers to be able to connect via USB Debugging, nada.
All I can say is wow. Definitely not placebo. Certain apps used to take forever to initialize (i.e. Facebook, Market). They now start up almost instantly.
I have not tried any of the other "fixes" because to me they break more than they fix. I don't want to use my external SD in a way that makes it non-swappable and I don't want to be restricted to 130mb for apps. This fix is the best so far. I'm guessing it may not be necessary once we have Froyo (double the RAM) but it does the trick for now.
Seemingly didn't work for me, my Quadrant scores are still sitting at 948. I'm on the stock ROM, and undid the previous speed fix I had.
LockeCPM4 said:
I guess my install question wasnt answered. You said run the .BAT file, do i run it on my pc? And what software on the pc side must i have installed?
Thanks for helping a noob!
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
It was answered:
You need root
Download zip file- unzip it.
Put phone into debug mode and plug in USB
run the included .bat file from the zip file and it will do the rest for you.
It has it's own adb.exe but you might need to install the SDK if you haven't already. That's it though.
edit: Most devs have added this to their roms already so don't be surprised if you find it in the build.prop already.
So I saw this mentioned in a tweet by the dev for Launcher Pro:
To get really nice smooth scrolling on your Eris add the following line to your build.prop:
Code:
windowsmgr.max_events_per_sec=60
To add it into your build.prop follow these steps using your adb tool:
Code:
adb remount
adb pull /system/build.prop
(Go into your tools folder and open it with notepad. Add the line I posted and save.)
Code:
adb push build.prop /system/build.prop
Reboot into recovery, wipe dalvik cache, and start the phone up. This can a while to boot up right after because of the wiping dalvik cache. You should notice that scrolling on your phone is much smoother.
I AM NOT RESPONSIBLE FOR YOUR PHONE. IF YOU BREAK YOUR PHONE DOING THIS (it's unlikely!) I AM SORRY BUT I CAN'T HELP YOU.
I currently have mine set to 70 and it's not any noticeably smoother than 60 that I can tell but it is stable so if anyone wants to try bumping it up to 90 or 120 feel free.
Thanks for the advice last night on this Hungry Man. I did this and notice a definite difference in the scrolling. I moved my Launcher pro scrolling speed down now from 100 to 45 because I no longer need it high with this fix. I also didn't wipe Davlik after pushing, but the file is in there when looking with Estrong file manager and the scrolling is definitely better now..
Thanks again..
Glad I could help! Wiping the Dalvik cache isn't really necessary I suppose, I just find it's good practice after doing anything to your build.prop to avoid possible glitches.
any reason why this wouldnt work on other devices?
Where exactly do I add this line? Thanks.
dev/null/ said:
Where exactly do I add this line? Thanks.
Click to expand...
Click to collapse
Just add it to the end of build.prop file.
Worked, I thank you for the reply and to the OP for the info.
Twidroyd
Could I get someone to fire up Twidroyd after applying this patch? Seems to cause super-heavy lag+slowdown in scrolling, but it appears that Twidroyd is the main offender.
This seems to work just fine for me. I guess it seems smoother... I can't really tell. Definitely not laggier.
Wouldn't you be able to open the build prop in something like Root Explorer's text editor and get the same result? I'm just not around my regular computer with adb setup... Thanks.
es0tericcha0s said:
Wouldn't you be able to open the build prop in something like Root Explorer's text editor and get the same result? I'm just not around my regular computer with adb setup... Thanks.
Click to expand...
Click to collapse
yes you can do this also.
Sent from my FroyoEris using XDA App
Implemented this tweak in my latest ROM and it definitely makes a difference
Sent from my nonsensikal froyo
I tried obtaining access through Root Explorer and it says that build.prop is read only?
drtchocky said:
I tried obtaining access through Root Explorer and it says that build.prop is read only?
Click to expand...
Click to collapse
You have to remember to make the directory R/W at the top of the screen.
Can't really tell if it made a difference. Has anyone experimented with setting the number even higher?
EDIT: Upon further review, it seems to have made my scrolling slightly smoother but also more likely to 'hitch'
Yeah, I think this is what I was seeing in Twidroyd. Scrolling is smoother in a list you've already scrolled through, but will stutter as it loads new table cells (a guess on my part, but it seems to make sense.)
Izeltokatl said:
You have to remember to make the directory R/W at the top of the screen.
Click to expand...
Click to collapse
Thanks! Rebooting now....
I think it's likely that if you aren't overclocking your phone may not be able to handle the extra load. If you aren't overclocking your phone or you're usually on a low cpu setting try chaing to 50. Anything above 35 will increase the smoothness, though not to the same extent. I don't suggest passing 60, I'm at 70 and the differences are negligable.
As for the lag and stutters, I haven't experienced that.
I did it. Didn't break anything, but didn't really seem to change anything either.
I have seen a huge difference in smoothness in screen scrolling as well as app drawer. I have large amt of apps and app drawer flies. One thing though I do not have a space before or after the equal sign on my line. Some of you who aren't seeing a huge difference take the spaces out and see if anything changes.
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?
While poking around today, I discovered that I could deterministically cause "rild" to segfault - every time I tried it.
The method I used was to turn on WiFi with the Mobile Data network already running, and then I would launch the app "Wifi Analyzer" (farproc). Almost immediately the "rild" (Radio Interface Layer Daemon) would segfault. (Strictly speaking, I don't know if using WiFi Analyzer was necessary - my WiFi has beacons turned off, and sometimes I can't establish a session straight away; using a scanner seems to get my AP to come out of it's sleep).
That consistency convinced me to use strace to attach to the already-running "rild" daemon, and spew to a log file.
Note that historically, the SIGSEGV faults that were logged to the logcat output at the moment of the "undead call" implicated a problem in the fclose() call - almost as if something was trying to close a file that had not been opened correctly.
So, there in the strace output, was this:
Code:
16:43:23 writev(6, [{"\3", 1}, {"HTC_RIL\0", 8}, {"(t=1297817003)%% $HTC_3GIND:0\\r\\n\0", 35}], 3) = 44
16:43:23 open("/data/data/com.android.dmportread/history", O_WRONLY|O_CREAT|O_APPEND, 0666) = -1 ENOENT (No such file or directory)
16:43:23 chmod("/data/data/com.android.dmportread/history", 0666) = -1 ENOENT (No such file or directory)
16:43:23 writev(6, [{"\3", 1}, {"HTC_RIL\0", 8}, {"at_notify_cdma_g23_data_entry():Can't open /data/data/com.android.dmportread/history successfully \r\n\n\0",102}], 3) = 111
16:43:23 --- SIGSEGV (Segmentation fault) @ 0 (c) ---
a quick peek at /system/lib/libhtc_ril.so shows that - yep - buried in there is a reference to
/data/data/com.android.dmportread/history
So, I tried the following:
Code:
[COLOR=green][B]
mkdir /data/data/com.android.dmportread
chown radio:radio /data/data/com.android.dmportread
touch /data/data/com.android.dmportread/history
chown radio:radio /data/data/com.android.dmportread/history
[/B][/COLOR]
and guess what - no more segfaults. [SIZE=+3]YES![/SIZE]
If this is the cause of the "undead" call (seems highly likely), the explanation appears to be due to a bug in the HTC vendor library lbhtc_ril.so : a file open() fails, but the corresponding "close()" operation takes place anyway, and that is where the fault (segmentation violation) occurs. There is a stupid dependency of the libhtc_ril.so file on the DMPortRead.apk app.
Probably the only reason that this bug does not express itself in HTC "factory" 2.1 ROMs is because of the presence of DMPortRead.apk app - presumably that creates/maintains the history file.
[SIZE=+1]See the 3rd post of this thread for downloadable patch/script files[/SIZE]
If any of you are consistently experiencing the "undead call" problem, please consider testing the above to see if you think it is the fix. (I believe it is.)
bftb0
I knew I liked you!
I'll have to try this out when I get home.
Here's a flashable .zip and also a shell script which may be used in Gscript lite - you need to unpack the "unpackme.zip" file to get to them. ("unpackme" is NOT flashable).
I realized after I was 95% of the way through putting together the installer script that there was absolutely no reason to do this in an offline fashion (that is, "overflashing" it during a recovery boot) - it is perfectly fine to do what needs to be done in a shell script any time you please with the regular OS is running. Oh well, the ROM devs can look at it and use whatever they want from it (or nothing at all).
You can run the CureUndead_v0.9.sh script either from within the Gscript Lite app (you need to give the script root privilege), or you could use adb to push it to /data/local and chmod it and execute it by hand. Note that Gscript Lite on GingerBread has this annoying bug where it prints "stderr:" for every line in the original script. It's not my script that's doing that - it's either a problem with Gscript Lite, or something unusual about GSB.
Oh, yeah - the way the script is written, you can run it as many times as you want; as a side effect, this will truncate to zero length any prior history file.
MD5's and sizes of contents of "unpackme.zip":
0bf8c49312e61c436d379a24255b12f3 CureUndead_v0.9.sh - 421 bytes
9d459f9f598f51fffa98cf832c524e50 CureUndead_v0.9.zip - 2,678 bytes (this one is flashable)
Going to try it out... Thanks for this!
nice work...
Very interesting... so this is something that would need to be done post flash, what do you think...
... we use that lights.sh script conap put together in /system/xbin/ that runs @ every boot to initialize the lights for trackball/notifications... would it work if I added the lines to that? I'm not sure if it would cause issues running it @ each boot or not?
Trying to figure out a different way to add this pre-build too.
This is huge if it's the fix. Incredible work.
oceanminded said:
This is huge if it's the fix. Incredible work.
Click to expand...
Click to collapse
I think it is the fix
workshed said:
Very interesting... so this is something that would need to be done post flash, what do you think...
... we use that lights.sh script conap put together in /system/xbin/ that runs @ every boot to initialize the lights for trackball/notifications... would it work if I added the lines to that? I'm not sure if it would cause issues running it @ each boot or not?
Trying to figure out a different way to add this pre-build too.
Click to expand...
Click to collapse
Well, I'm putting together a flashable "fix" file that just uses the installer script, so it could be rolled up into a ROM install as well.
The one thing you might want at boot (rather than only at ROM install time) is some kind of zero-ing out of the history file every once in a while, so that it doesn't grow without bound. I only watched it for a short period of time, and it was only 4 lines long; it might not ever grow big, but that seems like the right thing to do.
So I guess I'll wait until one of you genuises makes this "point and click" simple. I don't have a clue how to implement this on my own. Awesome work bftb0 !
Sheesh you're a brain OP. Awesome job!
Sent from my Ginger Tazz using XDA App
Interesting... what's the undead call bug you're talking about? I've been getting this funny bug on long calls where sometimes the phone app just crashes after 15-30mins or so. I get the crash window, and if I force quit, it shows no signal until I reboot the phone. If that's the one, a fix would be really nice. Running KaosFroyo v39 and never flashed a new radio BTW.
I've also seen the same thing on the WiFi signal. I have SSID broadcast turned off, and it takes it's sweet time picking it up on its own, but running WiFi analyzer seems to wake it up.
ufmace said:
Interesting... what's the undead call bug you're talking about? I've been getting this funny bug on long calls where sometimes the phone app just crashes after 15-30mins or so. I get the crash window, and if I force quit, it shows no signal until I reboot the phone. If that's the one, a fix would be really nice. Running KaosFroyo v39 and never flashed a new radio BTW.
I've also seen the same thing on the WiFi signal. I have SSID broadcast turned off, and it takes it's sweet time picking it up on its own, but running WiFi analyzer seems to wake it up.
Click to expand...
Click to collapse
What he is referring to is during a call you get the tones and vibration like the call has been dropped but then you can hear the person on the other end again and the call was never dropped. What you are describing is a new one to me...
CondemnedSoul said:
What he is referring to is during a call you get the tones and vibration like the call has been dropped but then you can hear the person on the other end again and the call was never dropped. What you are describing is a new one to me...
Click to expand...
Click to collapse
Ah yeah, I've had that happen too. I didn't think of it, though, since it wasn't all that annoying to me. I already ran the fix anyways, so I'll see if it helps either problem.
I haven't had the problem for some reason, but I just entered all that in a terminal window on my phone (and wasn't that tedious). Thanks!
Scott586 said:
So I guess I'll wait until one of you genuises makes this "point and click" simple. I don't have a clue how to implement this on my own. Awesome work bftb0 !
Click to expand...
Click to collapse
I put up a script in the 3rd post in this thread which you could use in the Gscript Lite app. You will still need to figure out how to use Gscript Lite, but at least no "adb" or command-prompt typing is needed.
Everybody else - I would appreciate hearing back from you after you try this, especially if you have been experiencing the "undead call" bug frequently. (I've used my phone for calling so little recently I don't think it has happened to me in more than 5 weeks.) The more often it was happening to you in the past, the more valuable your feedback is now.
bftb0
bftb0 said:
I put up a script in the 3rd post in this thread which you could use in the Gscript Lite app. You will still need to figure out how to use Gscript Lite, but at least no "adb" or command-prompt typing is needed.
Everybody else - I would appreciate hearing back from you after you try this, especially if you have been experiencing the "undead call" bug frequently. (I've used my phone for calling so little recently I don't think it has happened to me in more than 5 weeks.) The more often it was happening to you in the past, the more valuable your feedback is now.
bftb0
Click to expand...
Click to collapse
thanks for the script bf, that's all I needed to add it in the rom. I'll be a tester also, as I do experience the bug quite often, but only on long calls which isn't as frequent for me currently. Bravo sir!
P.S. I will be sure to add "# Undead call fix by bftb0" in the rom and OP page
workshed said:
thanks for the script bf, that's all I needed to add it in the rom. I'll be a tester also, as I do experience the bug quite often, but only on long calls which isn't as frequent for me currently. Bravo sir!
P.S. I will be sure to add "# Undead call fix by bftb0" in the rom and OP page
Click to expand...
Click to collapse
dope
this is good news. great job op and workshed if u add it to your gb rom lol
love you both!
flashed it on gsb1.4. i'll let you know how it goes.
:O OMG! That always happens, but I thought I was crazy XD So I'm going to try this.
Sent from my Droid Eris ♥ (running Ginger Tazz v5 [eat your heart out Jobs])