This may have been asked before but when i tried to search it said "Search is disabled for 10 minutes..." ... so heres the question
Compared to my samsung galaxy s i9000 the SE X10i screen sensativity to finger touches is really not that great.
I realize the screens are different but one fact remains -- they are both capacitive. On GSM Arena the specifications list the X10 as TFT capacitive touchscreen and while the GalaxyS as having Super AMOLED capacitive touchscreen.
Fine. so moving on. the problem is when it comes to gaming and some applications. i find myself with my X10 having to really put some pressure to get a reaction from the device ....
i was playing Armored strike yesterday and even the chat box in the left hand corner of the screen is hardly press-able. i have to literary put lots of pressure and try all sorts of finger positions to get a reaction.
Owning a WM-HD2 before i have seen many utilities out there that tweak settings like this so the question stands... is there a way to tweak the sensitivity on android and especially on our X10s??
Do you still have the screenprotector on the device that came with it?
Sent from my AOSP on Xperia (US) using XDA App
Cablekevin said:
Do you still have the screenprotector on the device that came with it?
Sent from my AOSP on Xperia (US) using XDA App
Click to expand...
Click to collapse
oops i forgot to add that to my original post.
no i removed the protector from the phone. its now "naked".
Both of mine are extremely sensitive. Are you sure yours is not defective mate?
Sent from my X10i using XDA App
Why don't you try adding this line
windowsmgr.max_events_per_sec=26
To your build.prop it has increase the responsiveness of my screen a lot... Just go to /system using Root Explorer and mount as r/w, open your build.prop with text editor and add that command to the bottom. Reboot your phone...
cheers
JIM
Sent from my X10i
jimbo77 said:
Why don't you try adding this line
windowsmgr.max_events_per_sec=26
To your build.prop it has increase the responsiveness of my screen a lot... Just go to /system using Root Explorer and mount as r/w, open your build.prop with text editor and add that command to the bottom. Reboot your phone...
cheers
JIM
Sent from my X10i
Click to expand...
Click to collapse
Why 26 and not 60 or 200?
Lord Takyon said:
Both of mine are extremely sensitive. Are you sure yours is not defective mate?
Sent from my X10i using XDA App
Click to expand...
Click to collapse
i cant really say. i live in baghdad and this unit was brought from europe. it first had a vodafone firmware on it until i got rid of it and made it normal.
i can only compare it to the SamsungGalaxyS.
@3dawg
I'll try that and report.
Thanks
3dawg said:
Why 26 and not 60 or 200?
Click to expand...
Click to collapse
Because numbers above 33 increase the latency. 26 seems to be the optimal value for low latency and good sensitivity.
jimbo77 said:
Why don't you try adding this line
windowsmgr.max_events_per_sec=26
To your build.prop it has increase the responsiveness of my screen a lot... Just go to /system using Root Explorer and mount as r/w, open your build.prop with text editor and add that command to the bottom. Reboot your phone...
cheers
JIM
Sent from my X10i
Click to expand...
Click to collapse
Which part of the build.prop should I add? anywhere?
ok so i did all that and it made a somewhat negligible difference ... the sensitivity is still not as great as the SGS. on the SGS i can hover my finger a full 1cm away and it detects it. on the X10 i have to apply pressure 2x more.
about the windowsmgr.max_events_per_sec
This defines the max event window manager;
yet this ONLY afect Scrolling through the app drawer and contacts and any lists but the fact is i`ve put 200 and GOSH!!! it is quick!!!
jimbo77 said:
Why don't you try adding this line
windowsmgr.max_events_per_sec=26
To your build.prop it has increase the responsiveness of my screen a lot... Just go to /system using Root Explorer and mount as r/w, open your build.prop with text editor and add that command to the bottom. Reboot your phone...
cheers
JIM
Sent from my X10i
Click to expand...
Click to collapse
just did thisss and its realyyy much faster
or put 200 like rendeiro2005 would be better?
anab said:
just did thisss and its realyyy much faster
or put 200 like rendeiro2005 would be better?
Click to expand...
Click to collapse
lol mine by default is already 290..using wolfbreak ROM...
Related
Info from this thread originally - http://forum.xda-developers.com/showthread.php?t=760805
Since we are using larger screens google recommends we change our dpi from 240 to 160, this probably looks fine for stock builds but on sense builds everything looks crazy. I currently have mine(on a sense build) at 210 however feel free to change it to what is best for you.
to perform this modification
pull the build.prop from /system/build.prop
open the file using a text editor and change ro.sf.lcd_density=240 to ro.sf.lcd_density=160(or whatever number you choose)
then push the file back to /system/build.prob
(i used a paid app called root explorer for this process)
if you want you use terminal emulator or adb here are the commands:
su
cp /system/build.prop /sdcard
then once youve edited the file
cp /sdcard/build.prop /system
you can use the same commands over adb by entering adb shell
download the spare parts app from the market and untick the compatibility mode then reboot (this fixes the issues some apps have with scaling)
the result of this mod is more things fit on the screen e.g. lists and web pages and games like raging thunder 2 look better as they arent being stretched out as much.
i recommend for a sense build: 200 to 220
for a vanilla build 160-220
if anyone has any better numbers please post
SCREENSHOTS ON NEXT PAGE
TO MAKE USE OF THE EXTRA SPACE ON THE HOMESCREEN INSTALL ADW LAUNCHER AND SET THE COLUMNS AND ROWS TO 6X6 (SCREENSHOTS ON PAGE 6) , THE SAME CAN BE DONE FOR THE APP DRAW
http://members.ping.de/~sven/dpi.html
input the values for HD2, you get ~217 dpi if you want to be anal about it
I wonder what effect not specifying any DPI would have...
this would be great if the lockscreen wallpaper would be retained... changing the dpi messes with the static wallpapers set...
I've tried 200, looks ok. I've always thought that we need to up the dpi, at 240 its way too huge for our screen.
160 messed everything up for me, the notification bar etc only filled half the screen. Other than that it looked awesome though! 200 might be the best, would be good to hear other opinions, not got a great deal of time to test
Is there a way to do it without Root Explorer?
FreakyFerret said:
Is there a way to do it without Root Explorer?
Click to expand...
Click to collapse
Go to your windows mobile, then edit the same file from the same folder of the Android. (not sure whether this works on all build, Shu8i build does work)
jubeh said:
http://members.ping.de/~sven/dpi.html
input the values for HD2, you get ~217 dpi if you want to be anal about it
I wonder what effect not specifying any DPI would have...
Click to expand...
Click to collapse
217 looks like 220 and leaving it blank sets it 160(thats what it looks like i cant tell really since it is blank)
pongster said:
this would be great if the lockscreen wallpaper would be retained... changing the dpi messes with the static wallpapers set...
Click to expand...
Click to collapse
would using a higher res wallpaper fix this?
Jragar said:
160 messed everything up for me, the notification bar etc only filled half the screen. Other than that it looked awesome though! 200 might be the best, would be good to hear other opinions, not got a great deal of time to test
Click to expand...
Click to collapse
160 on sense didn't mess up my status bar although some widgeds dissappeared. Which build are you using?
Interesting thread. I am using Mattc 1.5b Froyo. Anybody tries this? I am afraid of screwing my almost perfect setup.
Let me know what setting you used.
xkravenx said:
Interesting thread. I am using Mattc 1.5b Froyo. Anybody tries this? I am afraid of screwing my almost perfect setup.
Let me know what setting you used.
Click to expand...
Click to collapse
im on the same build as you with 210
copy out ur android folder onto ur hardisk as backup before u do the mod and u are safe if ur screen becomes black or u dun like it or it glitches badly and u cant modify it since u cant see the screen display properly..
This is sick,now my screen looks massive.Thx 4 the info..
"I pity the fool that owns an iPhone 4"
Sent from my HD2 using XDA App
please can you post before and after pictures
with 220 most of the apps doesnt scale properly and some doesnt work at all. Back to 240.
I set mine to 210.
It's hard to see the difference. I use MattC 1.5b with Froyo version...
The icons for "folder organizer" look smaller. But everything else seems to be the same. e.g. the htc sense applications, home, etc.
Maybe my mind is playing tricks on me.
here are some screenshots from the dpi changed from 240 to 200
xcooling said:
please can you post before and after pictures
Click to expand...
Click to collapse
This is what I've tried with mattcnexusleo1.1_512....
the 240 / 200:
I like the 200, it makes the keyboard smaller enough for me to type easier.
**mods please delete my post. JJbdoggg raced me to it...only sec's late sorry...
the settings wont keep on shu8i builds... weird... i tried modifying build.prop both on the phone and on pc... after pushing and rebooting it doesnt change, it actually changes back to 240... i tried the spare parts workaround, unchecking compat. mode and still no luck. any ideaS?
palosjr said:
the settings wont keep on shu8i builds... weird... i tried modifying build.prop both on the phone and on pc... after pushing and rebooting it doesnt change, it actually changes back to 240... i tried the spare parts workaround, unchecking compat. mode and still no luck. any ideaS?
Click to expand...
Click to collapse
Yeah your right same goes with me. I can't change it either that is why i used mattcnexusleo1.1_512 build. It worked with it...
palosjr said:
the settings wont keep on shu8i builds... weird... i tried modifying build.prop both on the phone and on pc... after pushing and rebooting it doesnt change, it actually changes back to 240... i tried the spare parts workaround, unchecking compat. mode and still no luck. any ideaS?
Click to expand...
Click to collapse
/android/root/system/build.prop
apeatan said:
Yeah your right same goes with me. I can't change it either that is why i used mattcnexusleo1.1_512 build. It worked with it...
Click to expand...
Click to collapse
You change build for that ? o-o
Shubcraft have cyanogen mod, wich is much more easier to make updates, no need to push anything and its great if you do a mistake see post above
-great tip thanks ! My screen looks really huge now at 200.. The appdraw is impressive too ... I'll wait for tomorrow to see if these smaller fonts are still readable with the sun.
Hey Guys,
Here is a new x8 gesture module for pinch zooming in SE X8 & X10mini.
This module works likely real dual touch & it response very quickly.
New in this module:
1. Much sensitive even can recognize little finger contact
2. Can be used in multitouch supported game
3. Supports all app with pinch zooming features
4. More correct pinch zoom than any other x8gesture modules
Installation:
Installation is same as previous x8gesture installation
- Remount /system as rw
- Copy the attached x8gesture.ko below to /system/lib/modules
- Change hw_config.sh in your /system/etc, add this code at the beginning
insmod /system/lib/modules/x8gesture.ko #dx: add gestures
- Push modified hw_config.sh back to your phone, reboot
** This is not real dual touch
** Use multi touch visualizer to calibrate & check the correctness
** It can not recognize more than two finger
I wish someone will make an update.zip for this module.
Don't forget to say thanks if it is useful for for you
Also, Sorry for my horrible English
Already testing.. thanks
Sent from my X8 using XDA Premium App
There isn't game mode.. I can't activate it. Btw it has less bug.
b.pet93 said:
There isn't game mode.. I can't activate it. Btw it has less bug.
Click to expand...
Click to collapse
Already tried with Angry birds & is working. I will re check & will fix it. Please keep reporting bugs to improve the module
I havent tried game mode because im not using it but accuracy of zooming pages is much improved.Good work man
and it was created on 15 april???
Godra said:
I havent tried game mode because im not using it but accuracy of zooming pages is much improved.Good work man
Click to expand...
Click to collapse
Thanks, don't forget to press the thanks button if you like it
dotsen9 said:
and it was created on 15 april???
Click to expand...
Click to collapse
The original x8gesture was created in April,2008 but can't remember the actual date. The module is new but the original one is old & I have added some new pseudo to it
How about cypress? I understand this is sinaptics only?
elderduke said:
How about cypress? I understand this is sinaptics only?
Click to expand...
Click to collapse
Cypress have already real dual touch & it works withax8mt module made by AnDyX. But Synaptics is not really dual touch capable. If you have X8 with cypress then u r lucky, use ax8mt module & enjoy real dual touch
elderduke said:
How about cypress? I understand this is sinaptics only?
Click to expand...
Click to collapse
Cypress already have dualtouch
Landscape:"Btw it is. Realllly. Hard. Too. Wriite. In lanndscape..."
Portrait:"Btw it ios really hard to write iin landscape."
EDIT: youtube video
http://www.youtube.com/watch?v=0ogKfHhHKJY
Sent from my X8 using xda premium
I have just tried to type in landscape and just as ponanovn said its very hard to write a word correctly. Hope it will be fixed in next realase
ponanovn said:
Cypress already have dualtouch
Landscape:"Btw it is. Realllly. Hard. Too. Wriite. In lanndscape..."
Portrait:"Btw it ios really hard to write iin landscape."
Sent from my X8 using xda premium
Click to expand...
Click to collapse
True landscape is not working but in portrait mode i can move fingers all across screen but need to move them also when put two fingers on the screen cordinates are wrong after moving them its perfect.
Is it possible too to move only one finger but having other one pressed?
Godra said:
I havent tried game mode because im not using it but accuracy of zooming pages is much improved.Good work man
Click to expand...
Click to collapse
Same. Good work! +1
ponanovn said:
Cypress already have dualtouch
Landscape:"Btw it is. Realllly. Hard. Too. Wriite. In lanndscape..."
Portrait:"Btw it ios really hard to write iin landscape."
EDIT: youtube video
http://www.youtube.com/watch?v=0ogKfHhHKJY
Sent from my X8 using xda premium
Click to expand...
Click to collapse
Godra said:
I have just tried to type in landscape and just as ponanovn said its very hard to write a word correctly. Hope it will be fixed in next realase
Click to expand...
Click to collapse
True landscape is not yet possible, but it can be simulated i think.
XperianPro said:
True landscape is not working but in portrait mode i can move fingers all across screen but need to move them also when put two fingers on the screen cordinates are wrong after moving them its perfect.
Is it possible too to move only one finger but having other one pressed?
Click to expand...
Click to collapse
At this moment this is not possible. But it can be done, will try in next version
is there ant update or zip i can just flash on xrecovery?
Questioner said:
is there ant update or zip i can just flash on xrecovery?
Click to expand...
Click to collapse
Hope someone will make an update.zip & don't have enough time to do this right now
link not working for me, could someone post again please
Raqib said:
Hey Guys,
Here is a new x8 gesture module for pinch zooming in SE X8 & X10mini.
This module works likely real dual touch & it response very quickly.
New in this module:
1. Much sensitive even can recognize little finger contact
2. Can be used in multitouch supported game
3. Supports all app with pinch zooming features
4. More correct pinch zoom than any other x8gesture modules
Installation:
Installation is same as previous x8gesture installation
- Remount /system as rw
- Copy the attached x8gesture.ko below to /system/lib/modules
- Change hw_config.sh in your /system/etc, add this code at the beginning
insmod /system/lib/modules/x8gesture.ko #dx: add gestures
- Push modified hw_config.sh back to your phone, reboot
** This is not real dual touch
** Use multi touch visualizer to calibrate & check the correctness
** It can not recognize more than two finger
I wish someone will make an update.zip for this module.
Don't forget to say thanks if it is useful for for you
Also, Sorry for my horrible English
View attachment 711965
Click to expand...
Click to collapse
is this a mirror based pinch zoom method ?! thanks man i'm really glad to see some one willing to play with the FDT (fake dual touch) modules again
ASHLEY117 said:
link not working for me, could someone post again please
Click to expand...
Click to collapse
there is nothing wrong with the link try again
Okay I found a way to be enable the camera shutter option on the camera app. You have to be rooted and I used root explorer.
1.) Open root explorer
2.) go to System folder
3.) Enable R/W ability
4.) Hold down on build.prop and open in text editor mode
5.) Look for 'ro.media.capture.shuttertone' without quotes
6.) It will say 0 change it to 1
7.) Click the menu button and choose save and exit.
8.) Reboot - not sure if you need to, but I did.
9.) Open the camera app and click menu, settings.
10.) You will now have the option to enable or disable the shutter sound.
Pics provided. Please thank me if this is helpful.
Side note, there are a lot of options in the build prop, but the interesting part is there is a whole section for LTE settings, and it keeps refering to verizon wireless at least thats what I think VZW stands for.
It worked. for some reason when I first had my phone it made the shutter sound. Than somehow it went away. Now I applid your fix and I can enable it or disable it. Thanks.
Simply brilliant.
I've also noticed a ro.camcorder.videoModes=false parameter. Wonder what that does if set to true.
It requires a reboot, but it works really well. There are quite a few options in build.prop. Wonder if there are any other tweaks.
Sent from my MB855 using xda premium
devilsshadow said:
Simply brilliant.
I've also noticed a ro.camcorder.videoModes=false parameter. Wonder what that does if set to true.
Click to expand...
Click to collapse
It gives you two additional video modes.
Slow motion and fast motion.
Sent from my MB855 using xda premium
blakkheartt12 said:
It gives you two additional video modes.
Slow motion and fast motion.
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
Do those modes work?
Sent from my MB855 using xda premium
This method to allow enabling/disabling of shutter tone worked after reboot! Thanks!
Blakeheartt12- Please clarify....will buildprop tweaks need to be restored to the original settings in order to receive future ota updates.
I believe I read something about that in another thread.
anoroc44 said:
Blakeheartt12- Please clarify....will buildprop tweaks need to be restored to the original settings in order to receive future ota updates.
I believe I read something about that in another thread.
Click to expand...
Click to collapse
That I'm not sure about. I do not think enabling a setting will keep an update from happening. If it does its real quick and easy to change back.
Sent from my MB855 using xda premium
blakkheartt12 said:
It gives you two additional video modes.
Slow motion and fast motion.
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
Awesome, even more options! I'll have to enable that as well. Also, root explorer automatically makes a backup of the original file so if need be, you can easily restore the file to stock.
I tried the new video options but didnt see any difference. So my guess is they are not working.
Sent from my MB855 using xda premium
blakkheartt12 said:
I tried the new video options but didnt see any difference. So my guess is they are not working.
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
Makes sense that they were disabled then.
But the shutter sound option was a great find. Never understood why camera phones needed that. There is no shutter so why does there need to be a fake sound? I know some old schoolers might like it and I don't mind it as an option, but why remove the option to enable/disable it. Stupid motoblur.
Sent from my MB855 using xda premium
tried it and worked perfectly... thanks a ton!!! i wouldn't have minded the sound of it except it being so damn loud... lol... great find!!
Thanks for the tip much appreciated
Sent from my MB855 using XDA App
MultiDev said:
Makes sense that they were disabled then.
But the shutter sound option was a great find. Never understood why camera phones needed that. There is no shutter so why does there need to be a fake sound? I know some old schoolers might like it and I don't mind it as an option, but why remove the option to enable/disable it. Stupid motoblur.
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
Re: the shutter sound is actually a requirement in many states (lot of creepers out there to keep up w/ evolving technology, i guess lol).
Re: add'l build prop tweaks I've found so far -
1) LCD Density setting *ro.sf.lcd_density"* (default is 240, you can go as low as 200 w/o causing conflict w/ system apps)
2) dalvik.vm.heapsize_48m (default is 48, can set as high as 64 w/o causing conflict w/ system apps, and as low as 32m). I'd personally leave this setting alone until development on this progresses, not sure how much of an impact this would have w/ stock kernel and other configurations. I put it @ 64m and ran w/ it for a few hours and noticed no significant improvements.
Awesome directions - worked great on my phone - LOVE the no sound click. So easy a newb can do it!
pwrmedia said:
Re: the shutter sound is actually a requirement in many states (lot of creepers out there to keep up w/ evolving technology, i guess lol).
Re: add'l build prop tweaks I've found so far -
1) LCD Density setting *ro.sf.lcd_density"* (default is 240, you can go as low as 200 w/o causing conflict w/ system apps)
2) dalvik.vm.heapsize_48m (default is 48, can set as high as 64 w/o causing conflict w/ system apps, and as low as 32m). I'd personally leave this setting alone until development on this progresses, not sure how much of an impact this would have w/ stock kernel and other configurations. I put it @ 64m and ran w/ it for a few hours and noticed no significant improvements.
Click to expand...
Click to collapse
On my phone, the heapsize was set to 42.
pwrmedia said:
Re: the shutter sound is actually a requirement in many states (lot of creepers out there to keep up w/ evolving technology, i guess lol).
Click to expand...
Click to collapse
Ugh, stupid politicians making stupid unenforceable policies. Don't they have better things to deal with.
A determined pervert could simply do this hack or tape over the speaker with a thick cloth (like velour).
On the other hand, being able to turn off the shutter sounds have many very legit purposes. I personally use my camera to take pictures of notes during conferences and to take pictures of books in the library. Also, when I did community theatre, I would take pictures of my audio patchbay so I could check my hookups whenever we needed to change mics for whatever reason backstage during the show.
Thank you. Much better fix than "disable STREAM_SYSTEM_ENFORCED" solution.
Anyway to disable the beep sound and vibrate whenever I power down my phone?
I had earlier posted this in the CM9 thread in the dev section but since no one was replying i thought id come to the general section
Our phone looks so beautiful when the lcd density is changed to 140:
And now the problem :
When i try to make a call or there is an incoming call the phone gives this error-
"Unfortunately com.android.phone has stopped working", and it becomes okay if i revert the density back to 160. This did not happen with CM7 and is there only in CM9.
I believe this is a prob with the phone.apk but i dont know how to edit system files
Can someone PLEASE make a fix for this
EDIT
Guys guess what I fixed it myself
Now you can can lower the density of your screen with the help of this
I just used the phone.apk file from a lower resolution phone's ICS unfortunately I don't remember which phone it was(I think it was htc wildfire). Link to phone.apk attatched.
Oh and I will take full responsibility for any damage this may cause to my phone but none if you try it and something happens to yours ;-)
I had this problem too, but I didn't know that density was the problem, so I went back to CM7. If someone can help fix this issue would be great. I appreciate the effort for anyone that tries to help.
Believe me it would be amazing if somebody could fix this. Our phone begins to look like higher end phones when the density is lowered.
Just wondering, in the screenshot with the status bar pulled down, did changing the density shift the blue circle on the bar (on the bottom) to the left?
Yeah but it still looks better ;-).
Sent from my LG-P500 using XDA
Problem solved.
See first post if you want to try it
What do you mean with Density ?
The Pixel-Density ?
kind regards
xSyntaX
changing the density makes our device look ugly imo.. i like our default density, its perfect.. there is also pixelation here and there with lower density and smaller fonts.. u can increase font size, but well, doesnt suit me.
xSyntaX said:
What do you mean with Density ?
The Pixel-Density ?
kind regards
xSyntaX
Click to expand...
Click to collapse
Yeah pixel density.
harshdoshi25 said:
changing the density makes our device look ugly imo.. i like our default density, its perfect.. there is also pixelation here and there with lower density and smaller fonts.. u can increase font size, but well, doesnt suit me.
Click to expand...
Click to collapse
Technically lowering the density should make our device look ugly. But I find setting the density to around 140 makes the device(and the resolution) look perfect
and iv never faced any pixilation at that density, though setting it to 120(default ldpi) does make it look little pixelated and a bit ugly(and everything too small)
rishabh22 said:
Yeah pixel density.
Technically lowering the density should make our device look ugly. But I find setting the density to around 140 makes the device(and the resolution) look perfect
and iv never faced any pixilation at that density, though setting it to 120(default ldpi) does make it look little pixelated and a bit ugly(and everything too small)
Click to expand...
Click to collapse
call me mad, but i just tried 140 and reverted immediately ! eww ! oh and u on testing kang by lupo ? do u have the problem of grey search box and the line above dockbar ? it becomes white for a milli sec when menu pressed.. plz confirm or deny. (only on testing kang and the update by hephappy)
awesome..
nicce work
harshdoshi25 said:
call me mad, but i just tried 140 and reverted immediately ! eww ! oh and u on testing kang by lupo ? do u have the problem of grey search box and the line above dockbar ? it becomes white for a milli sec when menu pressed.. plz confirm or deny. (only on testing kang and the update by hephappy)
Click to expand...
Click to collapse
Guess uv got too used to the normal density
And iv removed the line from settings so cant say about that but no I don't have any prob with the search box
Edit
I just checked the dock divider and no I don't have any prob with that either :/
hey will this tweak work on xperia x8 with cm9 ?
Yeah it should. I cant tell for sure because I cant try it.
There's no harm in giving it a shot. Just backup before trying.
rishabh22 said:
Guess uv got too used to the normal density
And iv removed the line from settings so cant say about that but no I don't have any prob with the search box
Edit
I just checked the dock divider and no I don't have any prob with that either :/
Click to expand...
Click to collapse
maybe but u dont get that problem ? the search box (the ics square one) is completly white ? thats odd ! ppl did confirm this bug !
u using the new drivers rom right ?
Looks good on ics, I tried on gb and result was : ahhh my eyes
Sent from my LG-P500 using XDA
xperia x8 - not working
androidnerd2 hey will this tweak work on xperia x8 with cm9 ?
rishabh22 Yeah it should. I cant tell for sure because I cant try it.
There's no harm in giving it a shot. Just backup before trying.
I have tried on X8 - not working... error with dialer - not able to place/receive call....Androidnerd - have u tried it? Is it wokring for u?
Thanks
harshdoshi25 said:
maybe but u dont get that problem ? the search box (the ics square one) is completly white ? thats odd ! ppl did confirm this bug !
u using the new drivers rom right ?
Click to expand...
Click to collapse
Im using whatever drivers were there in lupo's test by default
I do have colour banding in some apps like whatsapp, but nothing with the search box.
PEKA22 said:
androidnerd2 hey will this tweak work on xperia x8 with cm9 ?
rishabh22 Yeah it should. I cant tell for sure because I cant try it.
There's no harm in giving it a shot. Just backup before trying.
I have tried on X8 - not working... error with dialer - not able to place/receive call....Androidnerd - have u tried it? Is it wokring for u?
Thanks
Click to expand...
Click to collapse
Works fine on my phone. Which phone.apk are you using the default one or the one iv linked?
Cresqo said:
Looks good on ics, I tried on gb and result was : ahhh my eyes
Sent from my LG-P500 using XDA
Click to expand...
Click to collapse
I had been using this with perfect peso(cm7.2 nightly based) and had got so used to it that at normal density ics was looking ugly to me
Thank you very much for this. I tried the same sort of thing myself, but because I have no idea what I'm doing, I tried taking the Phone.apk from a GB ROM that I was able to change the density on instead of one from a lower-res CM9 ROM and it caused a whole mess of problems, haha. Running Quattrimus CM9 alpha on my OV in beautiful 120 density.
This is my first post here.
I recently switched from iPhone to Note 2. I was very drawn towards a large screen with lots of real estate. The note 2 out of the box didn't do it for me. However, I read the discussions about the international version and people changing the DPI with ROMs and other methods and figured if they could do it, so could I.
After waiting 5 weeks for my pre-order to arrive, then a week for the developers to provide a root option, I finally have my wish. Here is how I did it.
1. Root
2. Install a custom launcher (I installed nova, which works for me.) Set it as default
3. Install a new keyboard and set it as default
4. Install LCD Resolution from play store. I found nowhere that discussed this option, but I tested on a GS3, GS1, and Droid Charge and it worked better than the other DPI changers.
5. Set PPI to 240 in LCD Resolution. Uncheck Always Set on Boot until you know it will be stable. This caught me in a boot loop on the GS3. The only other res I tried was 160 and it failed.
6. Reboot.
It should work great. There are a few things to note:
1. The camera looks bad. I have not replaced it with a new one yet. - Please post any suggestions.
2. The calculator and dialer dont look amazing but are usable.
3. Email in portrait doesn't use the whole screen. I use it in landscape and it great.
4. Clock does not work, but can be replaced easily. I have not found a new alarm to use yet. - Please post any suggestions.
If you get another DPI to work well, let us know.
Otherwise, this is a great mod if you need more real estate on your new screen without loosing any of the s-pen or other stock functionality.
Thanks to those of you who helped root...
hmm, doesn't seem to work for me. The prompt in the app to reboot doesn't do anything.
Can we see some screen caps?
just do it manually it doesnt cause boot loops. You can change it to any DPI you want.
Use root explorer
navigate to "System/Build props"
Hold down "build props"
choose "open with"
then choose "text editor"
scroll down a few lines look for "ro.sf.lcd_density=320"
Change the 320 to whatever you want, I use 240.
click "save and exit",
reboot your device,
profit.
Why would you want to change it if it makes stuff look bad?
you can also edit the build.prop via rom toolbox really easily and the results are attached. 240dpi is first 320dpi is second.
Your Samsung keyboard will also crash at 240dpi but you can replace it with this one made by bala_gamer http://forum.xda-developers.com/attachment.php?attachmentid=1501015&d=1353535434
blackbass595 said:
Why would you want to change it if it makes stuff look bad?
Click to expand...
Click to collapse
I haven't done it yet but a lower dpi would be great on this phone. It would let you take more advantage of such a large screen real estate.
guthrien said:
I haven't done it yet but a lower dpi would be great on this phone. It would let you take more advantage of such a large screen real estate.
Click to expand...
Click to collapse
maybe but i just dont wont to change something that breaks other things. to each his own though.
blackbass595 said:
maybe but i just dont wont to change something that breaks other things. to each his own though.
Click to expand...
Click to collapse
It doesn't really break anything from what I've noticed, just makes a few things appear a bit differently, but still fully functional. It's worth a shot if you're interested in doing it, and you can always change back if you find it unmanagable. Personally, a per app dpi would be ideal, because you don't always prefer every app to be at 240 dpi. But I really like it, especially with the on screen nav buttons, which even those make some apps SLIGHTLY off, but still plenty usable, and worth the small inconvenience. To each their own though.
Sent from my SCH-I605 using xda premium
sleevasteve said:
It doesn't really break anything from what I've noticed, just makes a few things appear a bit differently, but still fully functional. It's worth a shot if you're interested in doing it, and you can always change back if you find it unmanagable. Personally, a per app dpi would be ideal, because you don't always prefer every app to be at 240 dpi. But I really like it, especially with the on screen nav buttons, which even those make some apps SLIGHTLY off, but still plenty usable, and worth the small inconvenience. To each their own though.
Sent from my SCH-I605 using xda premium
Click to expand...
Click to collapse
Where did you get the nav keys?
Thanks.
Sent from my SCH-I605 using Tapatalk 2
leyvatron said:
Where did you get the nav keys?
Thanks.
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=35037379
Sent from my SCH-I605 using xda premium
Mibuix0r said:
you can also edit the build.prop via rom toolbox really easily and the results are attached. 240dpi is first 320dpi is second.
Your Samsung keyboard will also crash at 240dpi but you can replace it with this one made by bala_gamer http://forum.xda-developers.com/attachment.php?attachmentid=1501015&d=1353535434
Click to expand...
Click to collapse
Is there anyway I can get the steps to you method I tried using the apps but it didn't work and now I got a white line at the top of the screen. Am flashing back to stock root to see if it will remove it. I also tried root explore but would lose the multi window edit option. Now am going for ROM tool box. Any pointers would be great.
dandel0074 said:
Is there anyway I can get the steps to you method I tried using the apps but it didn't work and now I got a white line at the top of the screen. Am flashing back to stock root to see if it will remove it. I also tried root explore but would lose the multi window edit option. Now am going for ROM tool box. Any pointers would be great.
Click to expand...
Click to collapse
The white line is probably the miui battery bar, see if its on in settings> custom settings> battery bar settings. As far as the dpi, just use a root explorer to go into system>Apps>build.prop, then long press build.prop and open in text editor and change the line with "screen/lcd density" and change the value to 240(or whatever you want). Hit menu and save/exit then reboot. You are correct that you lose the edit function in multi windows, but you can always change back to edit your apps, then switch back. The change only takes 10 seconds.
Sent from my SCH-I605 using xda premium
sleevasteve said:
http://forum.xda-developers.com/showthread.php?p=35037379
Sent from my SCH-I605 using xda premium
Click to expand...
Click to collapse
Cant get it to work.
What am I doing wrong? Do I have to be 240 dpi?
Root explorer > edit prop > scroll to bottom and add > qemu.hw.mainkeys=0 > and save
Sent from my SCH-I605 using Tapatalk 2
leyvatron said:
Cant get it to work.
What am I doing wrong? Do I have to be 240 dpi?
Root explorer > edit prop > scroll to bottom and add > qemu.hw.mainkeys=0 > and save
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
Now reboot. You don't have to be at any certain dpi.
Sent from my SCH-I605 using xda premium
Why you would want to is easy. Ever used a tablet and seen tablet mode on apps? Stock DPI prevents apps from entering tablet mode and that was one feature I was looking very forward to with such a big screen.
leyvatron said:
Cant get it to work.
What am I doing wrong? Do I have to be 240 dpi?
Root explorer > edit prop > scroll to bottom and add > qemu.hw.mainkeys=0 > and save
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
I couldn't get that to work either. I think it ma be a touchwiz conflict.
Just experienced my 2nd screen/sleep of death today, and unfortunately I'm thinking it's from the dpi. Going to change and will report back if I discover otherwise. I'll also leave my nav bar on, just to eliminate that variable. Bummer...I really hope we can incorporate a per app dpi on this phone at some point, maybe paranoid android(as long as it's reasonably compatible with the s-pen).
I also noticed my "android system" under battery was going through the roof. It was going over the screen %, but now that I changed the dpi back, it's already back under.
Sent from my SCH-I605 using xda premium
I get a error in root explorer when trying to edit the dpi in the build.prop
It will not let me change the setting to 240...any ideas? yes im rooted, root permissions granted for root explorer...etc.
droidstyle said:
I get a error in root explorer when trying to edit the dpi in the build.prop
It will not let me change the setting to 240...any ideas? yes im rooted, root permissions granted for root explorer...etc.
Click to expand...
Click to collapse
Make sure to use text editor or something similar. I had to long press it and "open with" for it to let me edit anything.
Sent from my SCH-I605 using xda premium