Related
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.
Update: I installed Spare Parts, as mentioned by appelflap later in this thread, disabled compatibility mode, then followed the directions in this post, and I have a working status bar, good resolution, and in a better place in most cases.
Update: Check out appelflap's APK that makes this whole process a lot easier. Note that some users are reporting a black screen after using the file, so be prepared in case you have to use adb shell to put your original build.prop file in place. If you do not want to risk it, Notepad++ makes for an easy edit once you pull the file to your PC. If you have fallen prey to the black screen problem, lpsi2000 found a solution that uses an update.zip approach.
In the /system/build.prop file, I changed this line:
ro.sf.lcd_density=240
Click to expand...
Click to collapse
to this:
ro.sf.lcd_density=160
Click to expand...
Click to collapse
This is a setting that Google normally recommends if you have a larger screen (like Dell's Streak), but the side effect of using it on the 800x480 screen of the captivate is that everything is smaller.
With this, menus have smaller text (more options on screen), in-app buttons are smaller, and it just has the same feeling of being on a PC and moving from a low resolution LCD monitor to a high resolution LCD monitor.
There are a couple of glitches so far. It appears that some apps want to render in the previous resolution. For example, Skyfire and Root Explorer would not render in full screen, Android Market renders full screen but the search is in the old resolution, and the status bar is slightly garbled but still usable. Also, the dial pad is smaller (as you would expect showing a picture made for a low res display on a high res display) but the rest of the phone app is fine. The camera app fills the screen just like it did before.
With this setting, I really feel like I'm getting some use out of the high resolution display on this phone.
The apps that are rending in the low res mode of the original setting seem to be pulling their setting from somewhere else. Does anybody have an idea where that setting may be? After trying this, I can't imagine going back to what almost seems like an "accessibility mode".
I've only used LauncherPro with this setting, so no idea how the Samsung launcher looks. I attached screenshots of what some things look like. I can put some game screenshots in another post if anybody is interested. 3D games look sharper to me in this mode, but I have no scientific way of testing if it is because it is rendering in higher res or if my own excitement is clouding my vision.
Update: I suspect the missing setting is found in the /system.prop file. It has the ro.sf.lcd_density=240 setting. I tried changing it to 160, but it keeps going back to 240 after a reboot of the phone. Any ideas how to make this stick?
Warning:: TWLauncher does not play well with these changes. Make sure to have LauncherPro set up as your default launcher before trying this.
So you're pulling it off the cappy then editing putting back....do you need to change permissions?
The way that I pulled it out to edit on my PC was with this:
adb pull /system/build.prop
Click to expand...
Click to collapse
You will need root access in order to put the changed file back. What I did was
adb push build.prop /sdcard
Click to expand...
Click to collapse
I then used Root Explorer to copy the build.prop from /sdcard to /system. I didn't change any permissions other than just copying the file and rebooting.
Wow man that's pretty cool, it's got a few little glitches but nothing serious. One of the things I wish I could so though is make my Beautiful widgets clock go all the way across the top. I'm not sure if this is a placebo effect (I donno if that's possible since this should have nothing to do with it) but it seems like my soft buttons respond more often....I'm prolly nuts but it doesn't seem like I need to push....push...%$^&*^ PUSH.....and back to home.
I'm hoping someone will have a great idea on how to keep the /system.prop file from updating itself on boot. I'm thinking that if we can get the ro.sf.lcd_density=240 setting to stick to 160 after a reboot, that might fix the few instances where an app won't render full screen.
I've tried chmod 666 system.prop and chown root.root system.prop but it still gets returned to normal after rebooting.
Wow I'm excited to test this out. Couldn't we get someone to code this into the startup script theoretically?
Edit: Tried it out. Really really nice. If only we could get the rest of the apps to work the right way... right res.
One thing also that's cool is in launcherpro you can add more columns to the drawer so you can fit an insane amount of apps on screen.
Sent from my GT-I9000 using Tapatalk
Also out of curiosity, have you tried any other DPI like 200? Our does it need to be either or to keep it proportional?
Sent from my GT-I9000 using Tapatalk
Lower resolution works as well. Here are some comparisons. 160, 240, 320. 200, since someone asked.
wow, this could REALLY be nice.. Just need to fix everything, but like others have said no HUGE things that cause it to be unusable, but I would love to see everything correct.
Also out of curiosity, have you tried any other DPI like 200? Our does it need to be either or to keep it proportional?
Click to expand...
Click to collapse
No, the only reason I chose 160 was because it is listed as "MDPI" in the Android SDK. (We were using "HDPI" with 240.)
I only figured it was a "supported" number, so I started there, but most any number will do. You can see a chart where it recommends certain numbers based on resolution or screen size, but I think these recommendations are to cover everybody, which includes folks who can't (easily) see small text or icons.
The chart that shows Google's recommendations is here.
reading around, it seems that the files need to be put back to read only.
phlunkie said:
reading around, it seems that the files need to be put back to read only.
Click to expand...
Click to collapse
I thought so also, but you don't need to. All I'm doing is copying it with root explorer to sd, then using astro to edit the line and root explorer to put it back. Reboot and your GTG. Everything works fine.
Sent from my GT-I9000 using Tapatalk
So the settings are sticking after a reboot? I will have to try this when I get home.
Sent from my SAMSUNG-SGH-I897 using XDA App
phlunkie said:
So the settings are sticking after a reboot? I will have to try this when I get home.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
After I edited the build.prop and the build.prop.bak files in the /system directory it works fine after reboot. A problem that I have is that TouchWiz force closes after editing the files.
Using this on SGS made:
- notification bar unreadable (kindof text overlap@240160 setting).
- Launcher pro works.
- Market scales nice.
- big list's buttons are now nice
//edit: changed to 200 - seems to be great compromise.
@up
Bad practice. U shouldnt have edited ur build.prop.bak file, becouse it is actually a backup of original build.prop, made by RootExplorer (guess). In case u want to revert to original content, u just delete edited file and delete .bak from this one.
xan said:
Using this on SGS made:
- notification bar unreadable (kindof text [email protected] setting).
- Launcher pro works.
- Market scales nice.
- big list's buttons are now nice
//edit: changed to 200 - seems to be great compromise.
@up
Bad practice. U shouldnt have edited ur build.prop.bak file, becouse it is actually a backup of original build.prop, made by RootExplorer (guess). In case u want to revert to original content, u just delete edited file and delete .bak from this one.
Click to expand...
Click to collapse
Any pics? Love to see the difference.
Sent from my Nexus One using XDA App
Here they are.
I'm trying to figure out how to make those other applications also use the full screen when at a different resolution. I tried the method here
http://forum.xda-developers.com/showthread.php?t=739647
to run a script that rewrites the /system.prop file, and it didn't fix anything, so either that is not where the applications are getting the property from, or we need to rewrite the file earlier in the boot process.
Are you sure those apps are graphically able to scale? Maybe touchwiz does not take scaling into account (at least with native apps) because the screens are all 4 inches.
I'm finding the standard LCD density too small and prefer a setting of at least 200 on my Streak. I also find that 3rd party widgets tend to look better on a setting of at least 200 and best on 240.
Only issue I have is various stock apps no longer look right at the higher setting e.g. the Gallery doesn't display the buttons at the top correctly, the dialer shortcut doesn't appear correctly in the Stage launcher, when receiving an incoming call in landscape mode the number is not fully visible, dialer looks weird and I'm sure I will find more things.
Basically, the two biggest annoyances for me are the dialer and the gallery. Can versions of these apps be baked into a rom that is designed to be used at the higher LCD dencity?
THANKS!!!
Krisbo
agreed the high density looks very sharp, I like it.
but trying to enter text in some fields, you cant even see the input field, Dialer incall buttons and contact names become b0rked, among other things,
Can anyone fix this so they dont get so blown out of proportion?
Thanks. The highest I went is 200, but back to 160 on djsteves 1.5.1 because of issues mentioned above.
I do believe you'd have to open up each apk and completely redo all the graphics so they don't look out of proportion blown up. I guess all you'd have to do is make them all smaller but it will probably be much more complicated than that!
So yes, it can be done. But i doubt anyone will do it.
Could you copy an apk from another phone with a higher pixel density? E.g. nexus one I think has 252ppi.
nexus by default is 240 yes, ill have a look at doing a 1.5.1 huge version wen i get a sec
You are awesome!
Could you possibly make it no baseband because I use a rebel sim?
Thanks
Before flashing the zip, unpack the whole thing and open system/build.prop with a text editor (like notepad or your favorite IDE). Then search for "ro.sf.lcd_density=160" and change it to a value you like. Save the file and repack it into the zip file (with WinRAR for example). Flash the ROM using StreakMod or ClockWorkMod and have fun with it!
Another option is to get Root Explorer - or a similar program - and go to system/build.prop. Set the permissions to r+w. Now you can edit this file using Root Explorer or copy it to your MicroSD and edit it like I said before. After the edit copy it back if you have too or save it. Then set the permissions back to r+o and reboot.
I have mine set to 220, which is a great size but I guess 200 is nice too!
alex3305 said:
Before flashing the zip, unpack the whole thing and open system/build.prop with a text editor (like notepad or your favorite IDE). Then search for "ro.sf.lcd_density=160" and change it to a value you like. Save the file and repack it into the zip file (with WinRAR for example). Flash the ROM using StreakMod or ClockWorkMod and have fun with it!
Another option is to get Root Explorer - or a similar program - and go to system/build.prop. Set the permissions to r+w. Now you can edit this file using Root Explorer or copy it to your MicroSD and edit it like I said before. After the edit copy it back if you have too or save it. Then set the permissions back to r+o and reboot.
I have mine set to 220, which is a great size but I guess 200 is nice too!
Click to expand...
Click to collapse
I think we understand that, the issue we have is that anything higher than stock 160 and apps get blown out of proportion, escpecially phone app for me, 180 is the highest /usable/ for me. I would love to have to cranked to the max, after owning an iphone 4 for a while, sweet display; but software is too simple.
Thanks DJ_Steve for looking into this,
please see if you can sort out the blurry contact pictures in-call, they look horrible even on stock 160, is it just me?
chrisrotolo said:
I think we understand that, the issue we have is that anything higher than stock 160 and apps get blown out of proportion, escpecially phone app for me, 180 is the highest /usable/ for me. I would love to have to cranked to the max, after owning an iphone 4 for a while, sweet display; but software is too simple.
Thanks DJ_Steve for looking into this,
please see if you can sort out the blurry contact pictures in-call, they look horrible even on stock 160, is it just me?
Click to expand...
Click to collapse
Exactly. I'm running mine at 220 but if the phone happens to put itself in landscape mode while it's ringing (happens sometimes) I can't see who is calling.
sorry i don't get it. how is the pixel density supposed to increase if the resolution of the LCD screen is fixed (480 by 800 pixels, not one more not one less)? to clarify, I am not denigrating, I just do not understand
Very frustrating. I dont have "ro.sf.lcd_density=160" in my build prop. Im on official ota update from a couple days ago
Hi Steve,
Any news on this?
Krisbo
carhigh said:
Very frustrating. I dont have "ro.sf.lcd_density=160" in my build prop. Im on official ota update from a couple days ago
Click to expand...
Click to collapse
Me neither.
Sent from my Dell Streak using XDA App
deekdeek said:
Me neither.
Sent from my Dell Streak using XDA App
Click to expand...
Click to collapse
I don't think this line is in the stock build.prop. Just add it under #other edits. If that's not their either, look for either debug.sf.hw=1 or debug.sf.hw=0 and add it after that.
You can use Incoming Call Plus (beta) as a replacement for incoming calls. This works great and has no negative side-effects for me.
Krisbo said:
I don't think this line is in the stock build.prop. Just add it under #other edits. If that's not their either, look for either debug.sf.hw=1 or debug.sf.hw=0 and add it after that.
Click to expand...
Click to collapse
Adding it worked. Thanks, i can read more now
alex3305 said:
You can use Incoming Call Plus (beta) as a replacement for incoming calls. This works great and has no negative side-effects for me.
Click to expand...
Click to collapse
That's not bad although the answer/reject buttons are UGLY!!! Does the job though and I can see who is calling
Any progress Steve?
I took this Gallery apk out from the Cyanogen Mod HTC Evo zip. It should scale properly when you change your DPI although stuff becomes real small when you go back to stock 160 DPI. It also fixes the "this is an audio file only" or whatever the hell that is if that wasn't already fixed.
It seems Dell changed the DPI of the dialer and gallery app to make use of the screen real estate while also using 160 dpi for the rest of the system.
Tried that apk n didn't do **** for me but I might have done it wrong...no biggy 1.5.3 looks like it might have this area sown up
Sent from xda app Dell streak dj 1.5.2
1190=1861qrdnt
First off, I cannot take credit for finding this, I was referred to a bug report thread on the Google Android site by XDA user aweaver33, who I thank VERY much for pointing me on the right direction.
So, several of us have had this issue with various custom kernels, where after typically 24-48 hours, the phone would slow to a crawl. If you were to open an app like System Panel, you would see that the CPU load was pegged at 95%+, and speed would be maxed out. You would also see that the process using all the CPU is Android System.
The problem has to do with the file "time_in_state", which literally keeps track of how much time the CPU spends at any given speed in MHz. There is a limit to the size this file is supposed to reach, 256 bytes. Once it exceeds this size, the next time Android tries to access it, it flips out and gets stuck trying, and pegs the CPU. A lot of devs and users blamed SetCPU, and it is true that SetCPU does have an EFFECT on this issue, it does NOT cause it, and indeed the issue can occur whether SetCPU is installed or not.
The issue is brought on by custom kernels that add additional frequency steps for the CPU to choose from, which causes that log file to grow. Which is why older or stock kernels will not cause this. Some ROMS incorporate a workaround so you may not have this issue.
Anyways, the issue is explained better in the link aweaver33 gave me. I will link to the original thread I posted with the conversation we had and the link he gave. I can confirm that, using the info he gave me, the issue has been fixed. I am currently just over 120 hours of uptime with no problems.
Here is the link: http://forum.xda-developers.com/showthread.php?t=1082363&highlight=stock+kernel+gpu+
EDIT: attached the script files for those who want them. You can drop one or the other (NOT BOTH) in /etc/init.d if your rom has this folder already (creating the folder and adding it won't work), or you can download Autostart (root) from the market for free, and drop the file in /data/opt (create the opt folder). This difference between the two is one runs only once at boot, the other runs every five minutes. If you use SetCPU, you need the one that runs every five mins, as every time you open SetCPU it resets permissions on the time_in_state file.
flashable zip? not everyone is comfortable with code and scripts
If I knew how, I would. I wasn't even comfortable with it. But I was so tired of the locking up, I was willing to try anything (after a Nandroid of course). I'm not sure you *could* do this in a flashable zip. I can post the script I'm using. It only runs once after reboot, unlike aweaver's, which runs every five mins (good if you're using SetCPU, as opening SetCPU resets the permissions of the time in state file).
This script should work if dropped into /etc/init.d. *If* your ROM has that folder by default. Mine does not, so I had to download a free app from the market called Autostart which is free and very small. For that app you create a folder in /data/ and drop the script in there.
Sorry guys but I'm no dev so this is the best I can do, maybe someone else can make it flashable?
would it also be fixed by simply deleteing the log file as well rather than setting it to unreadable
It can't be deleted. System instantly replaces it.
bast525 said:
It can't be deleted. System instantly replaces it.
Click to expand...
Click to collapse
:/ i suppose when it is replaced it would be with a fresh one deleting would fix it for 24-48 hours till it got filled again humm i wonder if a script could be auto executed every 12 hours to delete it rather than just make it unreadable.
Do you know if it is a problem in gingerbread as well?
mirrin said:
:/ i suppose when it is replaced it would be with a fresh one deleting would fix it for 24-48 hours till it got filled again humm i wonder if a script could be auto executed every 12 hours to delete it rather than just make it unreadable.
Click to expand...
Click to collapse
I don't think you can delete it. I can't figure out how to.
mirrin said:
Do you know if it is a problem in gingerbread as well?
Click to expand...
Click to collapse
Issue 9733 is still listed as New, so either Google hasn't fixed it in Gingerbread or they just don't bother statusing their bug reports.
Why do you feel the need to delete it? If you are trying to delete it, you are likely using Root Explorer. Why not just use that to change the permissions of the file? Tap and hold, select permissions, and unchecked all permissions except for the top left one. This will stop the bug, but the permissions will be reset after a reboot, or after opening SetCPU.
I imagine that deleting the file might actually cause FC's or may cause the same bug but I dunno since it wont delete.
dyetheskin said:
flashable zip? not everyone is comfortable with code and scripts
Click to expand...
Click to collapse
I've never created a flashable zip before, but I'd be willing to look into it if the demand is really there. The problem I see is that I'd have to make certain assumptions about how everybody's ROMs are configured. It looks like the most portable approach would be to append a line to the end of /bootcomplete.inc.rc. Do people really find it easier to boot into recovery and flash a zip than to add one line to a file themselves? Personally, I'm always hesitant to flash a zip other than a full ROM because I'd be uncertain how it interacts with other changes I've made to my system.
Inc is
not bad
But. 48hours?
Sent overrow from my Optimized Inc using XDA App
In this thread we should share our own little tweaks to this amazing ROM.
I'll add to this first post any stuff that is proven to increase speed or makes using the ROM easier or more enjoyable
Note, this isn't intended to include mods and addons, as there is already a great thread for that
IMPORTANT:
Always backup stuff! And reboot after teaking!
Please note that, the ones I've found more useful, I add a USEFUL tag in front of them
____________________________________
BUILD.PROP tweaks
With root explorer or any other method of your liking, go to /system/ and edit the file build.prop.
- To increase max fps limit possible, add:
Code:
windowsmgr.max_events_per_sec=150
I'm not sure this one is really useful, I think android already sets this already to around 1.5x screen refresh rate. The gains could be negligible.
- Disable error checking, add:
Code:
ro.kernel.android.checkjni=0
- USEFUL Stop debugging icon from appearing in status bar (doesn't disable adb), add:
Code:
persist.adb.notify=0
- USEFUL Force home launcher into memory, add:
Code:
ro.HOME_APP_ADJ=1
_______________________________________________
OTHER TWEAKS AND TRICKS
- VERY, Extremely, Mega-USEFUL - Go to:
Code:
/system/lib/elg
Open egl.cfg and delete the 1st line (0 0 android), reboot the phone.
Everything should be much smoother, I notice this especially opening folders with a lot of icons in Apex Launcher. I think this disables the default android software rendering method and uses only GPU. Don't ask me if this is different than setting composition mode to gpu in build.prop, I don't know, I just know everything is much faster
USEFUL - Only works with Aurora 2.07+ and synaptics screen - Tweak your screen duplicate filter, like in x5settings for .32 kernels.
Go to:
sys/module/synaptics_i2c_rmi_1564/parameters/sensitivity
Open the file "sensitivity" and tweak the value. Default is 4. Higher values reduce screen flickering/jitter but screen can become less sensitive, lower values, the contrary. Personally I use 8, works very good for my fingers, adjust you value accordingly. Note, this takes effect immediately, but doesn't stick after a reboot. To make it stick after a reboot, go to "/system/etc/", open one of the scripts, I recommend "ini.qcom.post_boot.sh", and add this at the end:
Code:
echo 8 > sys/module/synaptics_i2c_rmi_1564/parameters/sensitivity
where 8 is the value you want. Save, reboot and check is the value is there, in the "sensitivity" file.
- USEFUL - Great tips on how to save battery without turning everything off (bonus, doesn't use BS calibration myth):
http://www.androidcentral.com/keeping-your-charge-how-improve-battery-life-your-android-phone
Works AMAZINGLY thank you
Edit1: Also may i ask what CPU settings do you use? any overclocks/governor?
Edit2: I got that funny text glitch just before, i decided to wipe cache and dalvik and i haven't had it again yet. Ill get a screen shot if it happens again but im pretty sure you know what i mean, all the text for apps look like squiggly lines/really odd ive seen this happen normally in previous versions of aurora but oh well ill come back with more info if anything else happens thanks again!
thank you mate. Two quick questions. If i disable kernel debugging will this affect logcat? And what cpu composition does?
Cheers
Sent from my U8800 using xda premium
spirosbond said:
thank you mate. Two quick questions. If i disable kernel debugging will this affect logcat? And what cpu composition does?
Cheers
Sent from my U8800 using xda premium
Click to expand...
Click to collapse
Regarding the logcat, yes, probably disables that functionality, I've read in other sites, it just disables checking for errors, thus performance improvements. When I have time, I'll check if logcat is still there... the composition thing I think it tells the OS to always use GPU no matter what, I see a great improvement with that one, don't know if anything is affected, but so far, everything is great
EDIT: these tweaks were from here:
http://forum.xda-developers.com/showthread.php?t=1578065
Sent from my U8800
Here are some more:
http://www.freeyourandroid.com/guide/build-prop-modifications
If you try some, please post results, to add to first post.
spirosbond said:
thank you mate. Two quick questions. If i disable kernel debugging will this affect logcat? And what cpu composition does?
Cheers
Sent from my U8800 using xda premium
Click to expand...
Click to collapse
Logcat still works
Added synaptics TS setting like there was in X5settings app (Touchscreen Filter).
fjsferreira said:
Added synaptics TS setting like there was in X5settings app (Touchscreen Filter).
Click to expand...
Click to collapse
hi there, i have changed it right now to value 10 and its the same, its trembling...
i have kernel v3 from Dzo 2.0.5 rom.
and have restart the phone too
r1c4rd0 said:
hi there, i have changed it right now to value 10 and its the same, its trembling...
i have kernel v3 from Dzo 2.0.5 rom.
and have restart the phone too
Click to expand...
Click to collapse
Yes, I think so, maybe it was just placebo... also, it doesn't stick after a reboot, the ROM would need init.d startup script support and a script to change the value everytime... try change it to 40 or something, and report, it it still trembles, I'll remove from the first post...
fjsferreira said:
Yes, I think so, maybe it was just placebo... also, it doesn't stick after a reboot, the ROM would need init.d startup script support and a script to change the value everytime... try change it to 40 or something, and report, it it still trembles, I'll remove from the first post...
Click to expand...
Click to collapse
will try it right now
edit: changed the value and no diference... then i restart and no diference too...
I think it doesn't work... I've changed it to 1 and notice no difference... I'll remove that thing from front post and post here if anyone wants to study it...
- Something to try, it seems not to work... - Improve synaptics screen sensitivity!
Do you miss x5Settings setting about touchscreen filter? I've been studying x5settings source code and found out what file needs to be changed to achieve the same result in Aurora. Go to:
- sys/module/synaptics_i2c_rmi_1564/parameters/
Edit the file "sensitivity" and set a value appropriate for you. I've set it to 8 and touchscreen seems better now. Maximum value I think is 64, and that works great too. I think this isn't placebo Pinch to zoom in pics doesn't "tremble" when holding the fingers on the screen as it did before, here.
EDIT: it doesn't stick after a reboot! And values change by itself, don't know why, maybe it doesn't even work... Try it for your self
fjsferreira said:
- Something to try, it seems not to work... - Improve synaptics screen sensitivity!
Do you miss x5Settings setting about touchscreen filter? I've been studying x5settings source code and found out what file needs to be changed to achieve the same result in Aurora. Go to:
- sys/module/synaptics_i2c_rmi_1564/parameters/
Edit the file "sensitivity" and set a value appropriate for you. I've set it to 8 and touchscreen seems better now. Maximum value I think is 64, and that works great too. I think this isn't placebo Pinch to zoom in pics doesn't "tremble" when holding the fingers on the screen as it did before, here.
EDIT: it doesn't stick after a reboot! And values change by itself, don't know why, maybe it doesn't even work... Try it for your self
Click to expand...
Click to collapse
hey fjsferreira if you want stick after a reboot, you must to paste this command "echo 8 > /sys/module/synaptics_i2c_rmi_1564/parameters/sensitivity" (without the quotes) into 1 of the files in /etc/init.d
number 8 is choise by us... but make 8 for this example
r1c4rd0 said:
hey fjsferreira if you want stick after a reboot, you must to paste this command "echo 8 > /sys/module/synaptics_i2c_rmi_1564/parameters/sensitivity" (without the quotes) into 1 of the files in /etc/init.d
number 8 is choise by us... but make 8 for this example
Click to expand...
Click to collapse
The problem is, there isn't an /etc/init.d :S maybe it can be added to one of the scripts in /etc/
fjsferreira said:
The problem is, there isn't an /etc/init.d :S maybe it can be added to one of the scripts in /etc/
Click to expand...
Click to collapse
yes it can...
r1c4rd0 said:
yes it can...
Click to expand...
Click to collapse
Yes, it did, thank you... now I'm waiting to see if dzo responds in Aurora thread confirming this is working. I have a sense it works somehow, damn placebo is powerful!
fjsferreira said:
Yes, it did, thank you... now I'm waiting to see if dzo responds in Aurora thread confirming this is working. I have a sense it works somehow, damn placebo is powerful!
Click to expand...
Click to collapse
yes it works, but i think its related to his new v3.0 kernel...
in .35 kernel, if i´m not worng, we can change that value.
i think placebo dont work with me lol
fjsferreira said:
Yes, it did, thank you... now I'm waiting to see if dzo responds in Aurora thread confirming this is working. I have a sense it works somehow, damn placebo is powerful!
Click to expand...
Click to collapse
I tried 8 and 10 but the flickering didn't reduce. Thanks for the tip though. I hope you get it working...
Question:
What is the difference between the mod:" get rid of cpu composition" and setting the line
debug.composition.type=gpu
at build.prop?
By making the above change doolde jump graphics where improved
Cheers
You have ro.HOME_APP_ADJ=0 to force the launcher into the memory, but wouldn't the right value be 1?
FlashTH said:
You have ro.HOME_APP_ADJ=0 to force the launcher into the memory, but wouldn't the right value be 1?
Click to expand...
Click to collapse
Correct. I've fixed it, thank you!
Sent from my U8800
i dont know if you notice, but wen the phone is charging touchscreen feels more jumpy...
can anyone confirm this?
maybe this will interest dzo in the ics port? in this site there are the amtel and synaptics drivers:
port ics input drivers
drivers from HTC Legend touch the same as desire:
drivers synaptics from htc
thanks