Database Users

speed up auto rotate?

Is there a way to speed up auto rotate or change the amount of tilt before the screens auto rotation happens?
I've searched without avail.
Thanks for any info

To my knowledge, I don't think you would be able to speed up the auto-rotation. But hey, im sure one of our more technological swavvy and programming gods can do it some day

auto-rotate?
AroundTheWorld said:
To my knowledge, I don't think you would be able to speed up the auto-rotation. But hey, im sure one of our more technological swavvy and programming gods can do it some day
Click to expand...
Click to collapse
I agree. by the way, auto-rotation is nice for many things but it can sometimes be a little annoying when it auto-rotates the screen in the middle of something u didn't need it or when you are in an uncomfortable position and it starts rotating a lot..I don't know, probably it only happens to me. on the other hand, it would be more interesting to have a faster and smoother "apps Menu" drawing. when you slide the apps menu you can notice the lag. so let's hope for cupcake to be what we actually expect it to be.

the lag you speak of is directly proportional to the number of apps you have running and how many are on your phone. if you are like me and have 100 apps on the phone and they are on your class 4 sdcard then you are gonna have a little more lag pulling up the menu as it is reading from the sdcard, if you have them on a class 6 or on internal memory they will come up faster. also if you have a lot of apps all running in the background eating RAM you are gonna experience more lag just like when you have 100 windows open on your comp at home or work. try looking at what apps you have running or get a faster sd card and the app menu will respond better. the tilt is gonna respond based on available ram as it takes power and processes to change the orientation of the screen.

I'm using a class 6 card and only have 4 programs installed. "52MB of free space on phone"
yes shadowhacker I feel the same way,
I set my PocketPC to use a hotkey, so if you press the cameras shutter button it would set screens orientation to portrait or landscape. If in landscape the PocketPC was also clever, it used the dialer screen and call status in portrait.
I hate to say it but... the G1 is a pain and boring me.

phew
I only have 5 extra apps, but the lag has always been there since I got my G1, and every G1 I have seen is the same. the drawing speed (given by the speed the CPU is set up) is too low and probably it could only be fixed if some update comes with a CPU tweak (just like the iphone, remember? 400mhz then 412.) That's what I mean.

shadowhacker27 said:
I only have 5 extra apps, but the lag has always been there since I got my G1, and every G1 I have seen is the same. the drawing speed (given by the speed the CPU is set up) is too low and probably it could only be fixed if some update comes with a CPU tweak (just like the iphone, remember? 400mhz then 412.) That's what I mean.
Click to expand...
Click to collapse
the overclock app in the market tweaks the cpu, makes a big difference for me, some say its a placebo effect, but im getting much higher FPS in Neocore and Kid GBC when i tweak it up, and lower when not tweaked up. its a dollar in the market, worth a try

The over clocking works to an extent, but if you opened alot of apps recently the flip still seems to lag

(Q) DPI settings throwing apps scalling out

Recently changed my dpi to 200 and unticked compatability in spare tools. Question is the apps that dont automatically scale is there a way to manually make them fit the screen? Cant live without my full screen papertoss but dont want to go back to the ugly large 240 dpi

I'd bump this because I can't find the answer anywhere, maybe my search terms suck.

I noticed the same annoying thing.
BUMP, for an answer...
Sent from my HTC HD2 using XDA App

Im confused ... I use 200 DPI and all my apps do rescale perfectly full screen after spare parts compatibility un-check and a reboot. Even paper toss... Only thing i noticed with papertoss was that I had to uninstall it and download it again from the market...

bigblanko09 said:
Im confused ... I use 200 DPI and all my apps do rescale perfectly full screen after spare parts compatibility un-check and a reboot. Even paper toss... Only thing i noticed with papertoss was that I had to uninstall it and download it again from the market...
Click to expand...
Click to collapse
Some apps are simply developed with 240 dpi in mind. Typically, it appears that they use Android APIs to draw bitmaps unscaled. Even though the Spare Parts setting allows them to "see" the higher logical resolution, the bitmaps are not scaled correctly.
Most of these apps can still be used (or played). There's not much to do except making the app developers aware of this problem.
Here are some apps with issues:
- Abduction
- GOTO lock screen
- Hyperactive Ninja
- Hello Kids
- Tower Bloxx
- Mini Shot Basketball

Performance tips for the A7+

After some poking and prodding at my A7+, I was surprised by some of it's short comings. A couple in particular are easily rectified. The following changes require root access and some means of editing your /system/build.prop file (Root Explorer is real nice).
The first problem was that the screen was not as sharp and crisp as I would have expected for a 7 inch tablet running at 1024x600. As someone on these forums pointed out the LCD density is set incorrectly for the display, and that causes some problems with position/size of things in various apps. To fix this you need to change a line in /system/build.prop.
Code:
Default: ro.sf.lcd_density=200
Correct: ro.sf.lcd_density=160
The next problem is that the device reports OpenGL ES 1.1 when queried through the Android APIs, but when queried through the OpenGL APIs it reports OpenGL ES 2.0. This is a kinda big problem if you like playing indie games because few programmers will bother with low level calls when there is a decent framework to take care of that for them (let's them focus on their product instead of the boilerplate under it). To change this so that it reports correctly in the Android APIs you must add the following to the bottom of /system/build.prop.
Code:
ro.opengles.version=131072
The last problem I've not found an elegant solution for. The tablet doesn't seem to want to engage the second processing core unless a program explicitly demands it. The workaround for this is to install System Tuner, go to CPU, and slide the second CPU (left slider) all the way up, it will not keep this setting upon reset, it does keep it through sleep though. It is much more battery intensive with the CPU full engaged like that, so you'll want to kick it back down when you don't need it. One example where this made a huge difference: I was trying to watch a video encoded in x264 hi10p, without the second CPU engaged the video played slowly while the audio played full speed, with the second CPU engaged it played full speed without so much as a stutter.
I'm going to dig into the tablet a bit more now that I have a terminal emulator and ssh server set up on it. If there are power profiles like the stuff I've had to tweak on my laptop, can likely squeeze out a lot more performance with some fine tuning.

eideticex said:
After some poking and prodding at my A7+, I was surprised by some of it's short comings. A couple in particular are easily rectified. The following changes require root access and some means of editing your /system/build.prop file (Root Explorer is real nice).
The first problem was that the screen was not as sharp and crisp as I would have expected for a 7 inch tablet running at 1024x600. As someone on these forums pointed out the LCD density is set incorrectly for the display, and that causes some problems with position/size of things in various apps. To fix this you need to change a line in /system/build.prop.
Code:
Default: ro.sf.lcd_density=200
Correct: ro.sf.lcd_density=160
The next problem is that the device reports OpenGL ES 1.1 when queried through the Android APIs, but when queried through the OpenGL APIs it reports OpenGL ES 2.0. This is a kinda big problem if you like playing indie games because few programmers will bother with low level calls when there is a decent framework to take care of that for them (let's them focus on their product instead of the boilerplate under it). To change this so that it reports correctly in the Android APIs you must add the following to the bottom of /system/build.prop.
Code:
ro.opengles.version=131072
Click to expand...
Click to collapse
Wow. The lcd change is really nice- everything is much smaller but fits and looks sharper and cleaner. I saw that same post awhile ago but didn't pay much attention to it. Videos also look better.
I'm going to dig into the tablet a bit more now that I have a terminal emulator and ssh server set up on it. If there are power profiles like the stuff I've had to tweak on my laptop, can likely squeeze out a lot more performance with some fine tuning.
Click to expand...
Click to collapse
I really hope you continue to work on this tablet- it definatly needs some work. You should talk to Jam4 over at TR about this. He is making a HC ROM, and I bet he could bake the CPU changes right into the ROM.

I'm new to this stuff but where does the density come from? when I did my own math it seemed closer to 170.

Naidosh said:
I'm new to this stuff but where does the density come from? when I did my own math it seemed closer to 170.
Click to expand...
Click to collapse
Sorry been busy with my coding projects, so haven't popped into the forums in awhile. If I'm right in assuming you calculated that based on the visible screen space and resolution, you have to consider that screens have a metal trim around the edge which covers a few pixels of width and height on each border. If you dig through the source code that eLocity released, there are padding values in place to compensate for those when rendering to the screen. Almost every display out there does this, LCDs are pretty good about minimal over size, but old CRTs would have as much as 20% of the screen tucked behind the bezel for a nice border.

[TIP]Galaxy s6 the best boost .... (Resolution Change)

Hi all i have now latest 5.1.1 Lollipop STOCK ROM + root + Xposed(unofficial) on my Galaxy s6 Duos (G9200 HK)
I used Resolution Change. Now use 720x1280 resolution (Default is 1440x2560).
But default using i think is without sense, because this resolution is good for laptops and big monitors... i on my laptop have 1280x720...
On 720x1280 you don't a major change in graphic quality. Only small insignificant changes e.g. when you click recently used apps you see they in window "BIG"
I tested more resolution smallest 180x320(for fun xD NOT RECOMENDED) but optimal is 720x1280.
Lower revolutions than 720x1280 crash touchwiz ( need to use another loader) and samsung keyboard can have problems and sometime problems with interf. sys.
Now i have between 1,4GB to 1,5GB free RAM
And without Xposed i think i can have 200MB RAM more because i use some modules and with those system use more RAM.
720x1280 = 1/4 from 1440x2560
When i enter task manager on 1440x2560 settings app use 220 RAM +/-
On 720x1280 settings app use 110 RAM +/-
More apps working like it.
The best performance is in full screen games. Phone isn't heat.
Change resolution give nice boost to Galaxy s6 but you can too use greenify and another app to boost your phone more.
When you try Resolution Change you change resolution on your risk!!!!!!!!!!
I recommended USB Debuging mode active and know how use ADB for reset resolution. Some resolution changer APPs restore resolution after short time. Such Apps i recomended when you want test resolution. When you have problems after short time resolution back to last actived and approved resolution.
For me problem with touchwiz and keyboard isn't problem what i must reset my phone to factory... but some people can have problem with that.

I believe we should leave ram management to android. Coz it knows what's best,(isn't the ram which is not occupied is wasted ram?). So I don't see why one should lower his s6's resolution unless it has a huge effect on saving battery.
What's your avg sot with that configuration?

sapnesh said:
I believe we should leave ram management to android. Coz it knows what's best,(isn't the ram which is not occupied is wasted ram?). So I don't see why one should lower his s6's resolution unless it has a huge effect on saving battery.
What's your avg sot with that configuration?
Click to expand...
Click to collapse
Effect on saving battery does not come from nothing. Resolution 1/4. Your Graphics do less calculations. Your phone no heat up as normal resolution.
I don't know why apps use less RAM when resolution is lower when i tested that i wanted have smaller graphic usage lower heat phone in games and longer battery life but i tested that on settings.apk and another apps and i see effects.
I'm not specialist but i think after graphics have his work done all counted images stay in RAM and you can see RAM usage lower, because image 1440x2560 use more memory than 720x1280.
i don't know what it can work in settings.apk here isn't hard couting for gpu as 3D games...
When i changed resolution I did not expect such a decrease RAM usage.
But when someone better know why RAM usage is lower when resolution is lower can write :]

Alternative method:
Type in terminal emulator (after "su")
wm size (size you want)
Es. wm size 720x1280

enij said:
Alternative method:
Type in terminal emulator (after "su")
wm size (size you want)
Es. wm size 720x1280
Click to expand...
Click to collapse
Yes but when you test lower resolution you can have problem to back to usable resolution. (Keyboard can crash)
I recommended use Program what after short time back to usable resolution or know how use ADB.
And in ADB "wm size reset" ;]

Where can I download this Resolution Change xposed module. Cannot find it in the exposed download section...

Vinzie said:
Where can I download this Resolution Change xposed module. Cannot find it in the exposed download section...
Click to expand...
Click to collapse
This is no Xposed module i wrote "i have xposed" because it use some my RAM.
You can Resolution change with programs in Google Play

HOWTO: Reduce screen resolution, preserve battery life enhance framrate

I thought it would be good to have this in one seperate thread. The PRIV has a great qHD display but I don't think qHD resolutions make any sense on mobile devices. Problems like framedrops, low framerates, heat and battery draining can be the result.
Luckily, although the PRIV is unrootable, the commands wm density and wm size still work when applied through adb shell with USB debugging turned on. (If you don't know how to do this, there are many tutorials out there).
The PRIV has a native resolution of 2560x1440 @ 560ppi. We will change this to 1920x1080 @ 420ppi. To do so enter the following two lines:
Code:
adb shell wm size 1080y1920
adb shell wm density 420
Then reboot your device manually or simply enter:
Code:
adb reboot
To reset everything to normal enter:
Code:
adb shell wm size reset
adb shell wm density reset
Then reboot.
Hope this is helpful to you. Now I really like my PRIV and get stellar battery life and SoT:

WORKING ! thank You for that

After applying and rebooting, only a third of the screen was filled by the UI in the center and was very small. The rest was blank, not even navigation displayed.
Tried on the Priv bought from Blackberry direct on the latest update.

Calnyx said:
After applying and rebooting, only a third of the screen was filled by the UI in the center and was very small. The rest was blank, not even navigation displayed.
Tried on the Priv bought from Blackberry direct on the latest update.
Click to expand...
Click to collapse
Worked for me.
did execute these commands in this order on my computer with adb:
adb shell wm size 1920x1080
adb shell wm density 420
adb reboot
Done.

its wrong because to put it correct should be
adb shell wm size 1080x1920 ( not 1920x1080 )

Been at 1080p for the past couple of months and haven't had any issues
Used this: http://forum.xda-developers.com/note-4-verizon/general/dpi-resolution-changer-program-root-t3217199
Sent from my STV100-3 using XDA-Developers mobile app

Working
Nice, great man

Rotkaeqpchen said:
...
The PRIV has a native resolution of 2560x1440 @ 560ppi. We will change this to 1920x1080 @ 420ppi. To do so enter the following two lines:
Code:
adb shell wm size 1920x1080
adb shell wm density 420
...
Click to expand...
Click to collapse
Setting a higher density enlarges the fonts for better readability (which might be important for people in their 40ies ). I experienced setting values 450 or 480 is still OK. Higher values hide some things from the productivity bar.
Unfortunately, picture password is not working any more.
It seems that the display needs about 150 mAh per hour with the reduced resolution. Can someone check the initial energy consumtion to quantify the gain (if any).
Thanks

Here is a screenshot of the current energy consumption.
I will try out the commands later.

For comparison:
Time on: 2h 4m 25s
Computed power use: 436 mAh
With default resolution.

Anyone know how to correct the corrupt BBM icon in the HUB after the resolution/DPI change? The BBM icon turns huge on any density change and it looks incredibly ugly.

After having the reduced resolution active for one week, I'm switching back to default. It seems that for daily use there isn't much difference. I observed a couple of scaling issues (mainly with BB apps but also others) and decided it's not worth. I guess it will make one for sure when playing 3d games, but that's not my device usage.

p09 said:
After having the reduced resolution active for one week, I'm switching back to default. It seems that for daily use there isn't much difference. I observed a couple of scaling issues (mainly with BB apps but also others) and decided it's not worth. I guess it will make one for sure when playing 3d games, but that's not my device usage.
Click to expand...
Click to collapse
The reason why BlackBerry apps get affected is because they don't follow proper Material design guidelines. Sadly I feel that this is something that will plague devices for a while to come. So far I too am not noticing much difference in performance or battery life.

is there a way to pin the image on the bottom right of the screen?
also, does it completely ignore touches outside of the image? ...or am I reading wrong and the image will be stretched over the entire screen?
Sent from my STV100-1 using XDA-Developers mobile app

p09 said:
After having the reduced resolution active for one week, I'm switching back to default. It seems that for daily use there isn't much difference. I observed a couple of scaling issues (mainly with BB apps but also others) and decided it's not worth. I guess it will make one for sure when playing 3d games, but that's not my device usage.
Click to expand...
Click to collapse
The screen uses only almost half of the energy when it's in FullHD mode. That's a HUGE difference I can live with those little scaling issues here and there.

priv resolution, dpi
i change just the resolution, does it have a point, i do not wana change the dpi for the fact that is going to overscale a lot of thing, and for exemple i can not change my whatsapp photo if i change the dpi....

What about 720p-mode which is more natural to upscale on qHD than 1080p? Has anyone tried?

u.b.o.o.t said:
What about 720p-mode which is more natural to upscale on qHD than 1080p? Has anyone tried?
Click to expand...
Click to collapse
I tried but it's very ugly so I prefer 1080p

phong1892 said:
I tried but it's very ugly so I prefer 1080p
Click to expand...
Click to collapse
Interesting thread. I just bought a new phone because the priv battery is dying, and I couldn't find a new one. But I had to drop screen resolution to do that, since I didn't want a physically larger device. I miss the sharp resolution and greater "real estate" of the priv screen.
Sent from my moto x4 using Tapatalk