Related
Hi guys,
As I understand on most modern android devices, the "max" wallpaper size is 960x800. That is, it is 2 screens wide, but pans a percentage of the width from side to side depending on how many home screens you have.
One thing I have been wondering for a while is if there is any way (of course preferably without root, though either way really) to allow for a full 480px wide image for every home screen you swipe through? On an evo, I suppose this would mean a 3360x800 image. A bit extreme, of course, but probably would make for some great customization effects. This functionality idea is basically stolen from the N900.
that would be cool since very screen on my phone has a different theme. tools/games/ media and whatnot
This will let you do just that....Havent tried it on the Evo but theres a comment on the Cyrket page saying it works
http://www.cyrket.com/p/android/com.creativecore.wallpaperplus/
As an Android nut and graphic/industrial/UI designer I've been thinking a lot about this recently, and just had to get it off my chest. Here goes:
UI styling should be about the content, not the interface. Glossy elements just distract from their actual content. There should be a move away from what Apple does with iOS (emulating analogue elements digitally) towards what Microsoft did with WP7. WP7 showed that you can have an interface without any sort of shininess/gradient or analogue elements and still have it be completely usable and beautiful at the same time.
But what I'm really interested in is the future of Android. Gingerbread was a great step ahead in terms of UI styling. But I wonder what we will see when Sense UI, Motoblur, TouchWiz etc. are updated to 2.3? Sense is notorious for faux glossiness and TouchWiz is notorious for being plain ugly. Will WP7 and Gingerbread help these companies realize that the trend is moving away from iOS-eque styling and towards WP7-esque styling? Or will they continue to blindly copy iOS and ignore Google's attempts to beautify Android? My guess is that they will eventually catch on, but it might take a while. Perhaps if WP7 takes off and commands a decent market share these companies will take notice. We've already seen previews of Sony Ericsson's 2.3 TimeScape skin and LG's 2.3 whatever-it's-called skin and they both appear to have abandoned Gingerbread's gradient-less notifications bar and title bar and replaced them with gradients. Too bad.
Also, what will Honeycomb bring? We've now seen previews of the tablet version, and I can see many 2.3 styling cues in 3.0. One thing I noticed though is that it uses blue as the 'accent color'. Gingerbread strongly reinforced orange as Android's accent color so I wonder why they would change this. What I'm hoping is that the accent color can be changed- it's certainly plausible, as the accent color seems to play a huge part in the Honeycomb previews I've seen. Or perhaps phones will remain orange and tablets will be blue? It seems like a strange differentiation.
Hints at UI change in the phone-version of Honeycomb include new text-entry fields (looks like the Android keyboard spacebar symbol but stretched), a new look and swiping interaction for tabs within apps (seen in the leaked Music 3.0 app, the 2.1 News and Weather app and the new YouTube app), and like I mentioned, color accents everywhere. Videos of Honeycomb show pop-ups, scroll bars, loading rings/bars and menus featuring the glowing blue accent.
What I'm wondering about is this 'UI overhaul' that everyone is talking about. Is it going to be mostly visual like the stuff I mentioned above or is it going to completely change the UI paradigms of Android? I think a huge change in UI akin to the WM6.5 > WP7 transition would alienate a lot of users and break a lot of apps. Therefore I'm thinking 3.0 is going to be a few tweaks to the interaction part of the UI, but a huge change to the visuals. I predict they will update almost all of the core apps to match the graphics we are seeing in 2.3 and 3.0, to finally put to rest those complaints that Android looks 'hacked together'. The changes in 2.3 were probably a catalyst, to get developers thinking in this new design language. Google needs a name for it, just like WP7 'Metro'. After all it's up to the developers to make apps that match this style.
I'm a Nexus fan and would never buy a phone without stock Android so maybe this is just me dreaming of an end to carrier/manufacturer skins, but what do you think?
As long as it have the look and feel of ADW.Launcher. It can have what ever UI.
chrizzled said:
As an Android nut and graphic/industrial/UI designer I've been thinking a lot about this recently, and just had to get it off my chest. Here goes:
UI styling should be about the content, not the interface. Glossy elements just distract from their actual content. There should be a move away from what Apple does with iOS (emulating analogue elements digitally) towards what Microsoft did with WP7. WP7 showed that you can have an interface without any sort of shininess/gradient or analogue elements and still have it be completely usable and beautiful at the same time.
But what I'm really interested in is the future of Android. Gingerbread was a great step ahead in terms of UI styling. But I wonder what we will see when Sense UI, Motoblur, TouchWiz etc. are updated to 2.3? Sense is notorious for faux glossiness and TouchWiz is notorious for being plain ugly. Will WP7 and Gingerbread help these companies realize that the trend is moving away from iOS-eque styling and towards WP7-esque styling? Or will they continue to blindly copy iOS and ignore Google's attempts to beautify Android? My guess is that they will eventually catch on, but it might take a while. Perhaps if WP7 takes off and commands a decent market share these companies will take notice. We've already seen previews of Sony Ericsson's 2.3 TimeScape skin and LG's 2.3 whatever-it's-called skin and they both appear to have abandoned Gingerbread's gradient-less notifications bar and title bar and replaced them with gradients. Too bad.
Also, what will Honeycomb bring? We've now seen previews of the tablet version, and I can see many 2.3 styling cues in 3.0. One thing I noticed though is that it uses blue as the 'accent color'. Gingerbread strongly reinforced orange as Android's accent color so I wonder why they would change this. What I'm hoping is that the accent color can be changed- it's certainly plausible, as the accent color seems to play a huge part in the Honeycomb previews I've seen. Or perhaps phones will remain orange and tablets will be blue? It seems like a strange differentiation.
Hints at UI change in the phone-version of Honeycomb include new text-entry fields (looks like the Android keyboard spacebar symbol but stretched), a new look and swiping interaction for tabs within apps (seen in the leaked Music 3.0 app, the 2.1 News and Weather app and the new YouTube app), and like I mentioned, color accents everywhere. Videos of Honeycomb show pop-ups, scroll bars, loading rings/bars and menus featuring the glowing blue accent.
What I'm wondering about is this 'UI overhaul' that everyone is talking about. Is it going to be mostly visual like the stuff I mentioned above or is it going to completely change the UI paradigms of Android? I think a huge change in UI akin to the WM6.5 > WP7 transition would alienate a lot of users and break a lot of apps. Therefore I'm thinking 3.0 is going to be a few tweaks to the interaction part of the UI, but a huge change to the visuals. I predict they will update almost all of the core apps to match the graphics we are seeing in 2.3 and 3.0, to finally put to rest those complaints that Android looks 'hacked together'. The changes in 2.3 were probably a catalyst, to get developers thinking in this new design language. Google needs a name for it, just like WP7 'Metro'. After all it's up to the developers to make apps that match this style.
I'm a Nexus fan and would never buy a phone without stock Android so maybe this is just me dreaming of an end to carrier/manufacturer skins, but what do you think?
Click to expand...
Click to collapse
Just my two cents here but.... I don't get everyone saying android has no polish. I love my Nexus One, I love stock (vanilla) android. I think Touchwiz is an abomination and said as much when that thread came out to put touchwiz on the N1. Sense is pretty but too bloated in my opinion. Don't get me started on Motoblur... I agree earlier versions of android needed work. >2.2 {in my opinion} Personally I think android is fine. (iOS IS pretty, but so what it's also got an evil ecosystem...) The tweaks done to
2.3 are nice but unnecessary (IMHO). I love the way Android looks.... Oh, and I heartily agree with your statement that "UI styling should be about content...."
Sent from my Llama powered N1 courtesy of the xda app! Llama Power!!
If android could come up with a functional UI I might jump back aboard. Til they do WP7 is the only way to go.
Love the look of stock Android on my Nexus One. Love the new Gingerbread visual tweaks and look forward to the OTA.
HATE 3rd party U.I.
z33dev33l said:
If android could come up with a functional UI I might jump back aboard. Til they do WP7 is the only way to go.
Click to expand...
Click to collapse
Android HAS a perfectly functional UI. Thank you.
Sent from my Llama powered N1 courtesy of the xda app! Llama Power!!
Babydoll25 said:
Android HAS a perfectly functional UI. Thank you.
Sent from my Llama powered N1 courtesy of the xda app! Llama Power!!
Click to expand...
Click to collapse
I used to think so too... now it just seems laggy regardless of launcher...
z33dev33l said:
I used to think so too... now it just seems laggy regardless of launcher...
Click to expand...
Click to collapse
What lag? {unless ur using a SGS} I have never experienced this lag u speak of sir. My N1 flies I tell you, flies!!! (I have seen in Samsung's phones however...)
(That is why I don't buy them...)
Sent from my Llama powered N1 courtesy of the xda app! Llama Power!!
Babydoll25 said:
What lag? {unless ur using a SGS} I have never experienced this lag u speak of sir. My N1 flies I tell you, flies!!! (I have seen in Samsung's phones however...)
(That is why I don't buy them...)
Sent from my Llama powered N1 courtesy of the xda app! Llama Power!!
Click to expand...
Click to collapse
Didnt notice it on my Nexus one til I got WP7, now I just gave the nexus to my brother... just seems slow and jumbled by comparison
im glad the orange accents are gone in honeycomb, the blue looks way better, also im glad the green icons didnt made the cut, i really hope this look becomes the standard for both the tablet and the smartphone versions of the os
Android is ok but can be boring....
Personally I love the idea to have more than 1 OS on your device, so you can easily change whenever you want
With Matias Duarte on board we should see some drastic changes in the UI in the upcoming versions.
Look at the Honeycomb on tablets, we're now not required to have physical buttons, virtual controls are there, the switch tasking panel now actually shows us the current snapshot of the appss in the background - awesome idea from WebOS if you ask me.
z33dev33l said:
Didnt notice it on my Nexus one til I got WP7, now I just gave the nexus to my brother... just seems slow and jumbled by comparison
Click to expand...
Click to collapse
I'm a phone addict and I try out almost every phone and OS that comes out. I still don't see what you are talking about, WP7 didn't feel any faster or more polished. It's got a new look and has some ooomph too it, but nothing that noticeable.
Sent from my Llama powered N1 courtesy of the xda app! Llama Power!!
Babydoll25 said:
I'm a phone addict and I try out almost every phone and OS that comes out. I still don't see what you are talking about, WP7 didn't feel any faster or more polished. It's got a new look and has some ooomph too it, but nothing that noticeable.
Sent from my Llama powered N1 courtesy of the xda app! Llama Power!!
Click to expand...
Click to collapse
As am I and I will still admit that the nexus one was the smoothest experience I recieved from an android phone. In all honesty I never thought I'd jump ship and I thought live tiles looked completely retarded. I didnt really think a GPU accelerated UI would mean anything but it did... its just smoother... virtually lag free and though I'm not trying to insult I dont see how you cant see the difference....
z33dev33l said:
As am I and I will still admit that the nexus one was the smoothest experience I recieved from an android phone. In all honesty I never thought I'd jump ship and I thought live tiles looked completely retarded. I didnt really think a GPU accelerated UI would mean anything but it did... its just smoother... virtually lag free and though I'm not trying to insult I dont see how you cant see the difference....
Click to expand...
Click to collapse
I mean don't get me wrong, live tiles rock (and roll) but maybe it's just my N1 {and Sparky's but I set his up so...}, but I didn't see an overwhelming difference even with the hardware acceleration. I guess it all boils down to (after a certain point) how you have your individual phone configured... I have not yet seen anything worthy of N1 abandonment...t least not yet.
Sent from my Llama powered N1 courtesy of the xda app! Llama Power!!
I thought my N1 was smooth until I tried a Nexus S... now I can't go back.
The Gingerbread stock launcher is silky smooth. WP7 smooth. The scrolling and 3D app drawer is much smoother than LauncherPro or ADW Launcher. Live Wallpapers do not affect performance at all. The new UI elements make android look much more refined. The screen-off animation and the scrolling overshoot glow are amazing. And that's just the UI...
Long live stock Android and Nexus devices!
UI of Android
- The current browser UI is driving me crazy! Especially the back operation could jump to another app is un-acceptable.
- We need to have a mechanism for something like a pop up app. For example, when reading, a quick pop-up to look up a word or access wikipedia. It just need to : select, open with selection. Since Android let all apps open, the user just go back to the last app to continue
- I agree that data is important. The contact is the central of a phone. It can be mail, phone, sms, im, photo, calendar, ... The owner is of-cause need to be part of the contact. And there should be able to browse, jump, classify contacts quickly. I would like to suggest allow tags. An extendable contact db will be very nice.
- Moreover, for tabalet, there should be multi-users, switching profiles, encrypt data, etc. the lock screen should allow change of user
- Please consider the actual usage of a phone or tabalet together with other devices. Android should be part of a bigger system instead of a single computer. Cross interaction with desktop, other tabalets, is a must: ssh should be a standard on every device. There should be neighbour or friends nodes (not people, but devices) that can registers long term or short. There should be a easy way to find the new ip or connection method(bt) for the device. a bluetooth message send to allow register the device and provide a instant connection is good. Porting synergy allow share keyboard, (mouse) and clipboard is good, but need to address the situation where mouse is missing. Send screen shot is useful too. exchange pic, contacts, calendar events, ....
- Make index a ready service, update of index can be done when charging. It can be a mode call sleep, which will do house keeping like : update indexing, clean up space, calculate statistics, exchange data with cloud. The phone would work but will be slow. User can understand that the phone go sleep a while to keep healthy. The index is very valuable : provide fast browsing for things, faster search, and support a multi-dimension browsing experiende.
- clipboard : with multi-history
- Please check lePhone : use of gesture instead of soft key.
- Fast switch between opened apps
- notice : allow user to block call, sms, ... to interrupt. There can be a priority and the user can set the current lock level, priority lower the lock level would not sound, visual or virbaton
- I am not very sure about this : there should be scene : like meeting, driving, atHome, atOffice, etc. which can be auto-detect by various sensers. But too smart a phone can also be troublesome.
allow two phones to compare the app list, find common contacts, temporary play a game with connection (like NDS download play), peer chat (group of devices), share camera, audio, borrow book
current desktop background is not good. Make it easier for user to dress up their phone.
I'm looking for an entry level android phone.
I've narrowed down my choices to a couple of units.
One of the unit has Android 2.1 with HVGA resolution.
The other unit has Android 2.2 with QVGA resolution.
I understand that both os version and screen resolution has some effects and limitations to the type of apps you can install.
My question is... Which one is more important to take advantage of the maximum number of apps availability?
Do more apps require 2.2? Or do more apps require HVGA?
As you can see, i can't have both. So i'll have to choose between the two. Please help to give me an idea on which feature i should prioritize.
Thanks.
Most apps require 2.1 upward these days. I do not recall seeing anything that won't run on 2.1 that will on 2.2 (2.3 does though).
Most common screen res is 480x800 which is what 98% of apps aim for when developing and then devs amend the apps afterwards for other sizes (not always amended though so this screen size is the best for droid - also moto tend to use 480x854 but believe this can run most 480x800 apps?)
I believe 240x320 is the next common screen res so this would be mt second choice and have more compatibility than all others (bar 480x800).
Higher resolution, root it, flash cm. Android 2.3
I'd go with the HVGA resolution although qVGA isn't bad at all. The reason for HVGA: some of the apps on the market don't show if you have a qVGA display.
Personally though, I have the X10 mini pro (qVGA). Love the small size that's why I'm sticking to it ATM.There is a hacked market on XDA which allows me to see the apps which require HVGA resolution so I get the best of both worlds. Some of the HVGA apps aren't customized for qVGA but are usable.
Hello everybody, and before all, sory for my english
The main objetive of this thread is to provide a guide to increase performance on high density screen GPU bound devices, for example, the nexus 10.
The last year android devices start shiping with very high definition screens, but without the necesary GPU muscle to make them work good.
Since I was a PC gamer, I know the terrible impact of high definition on the gaming performance, and, on this screen size, this is a useless impact, since the extra resolution are practicaly unperceptible.
The past week I spend a lot of time trying to change my device's resolution (a nexus 7) and with kernel modding, it is posible, but don't are great since I only play 1/3 of the devices usage, and the 1280x800 resolution are great for chat, browsing (or posting on the forum ).
Finally I find a great program that allow me to temporary change the display resolution of my device, and with the free version I was allowed to change resolution to 720x450, and on gaming performance, that was a GREAT performance updrade, even, with the wuality sacrifice (and on a 7 inch display, this wasn't a great lose.
In order to do that, I need to disable soft keys, since they bug A LOT with the resolution change, and to use a custom launcher because the default launcher bug too (go launcher ex is my favourite and the only one I test).
So, I leave a guide on how to prepare your device to use this mod to increase gaming performance, and to provide help to everyone who want it.
First of all, you NEED to be rooted.
Now, start with the device preparing.
Wee need a soft keys replacement, I recomend this one, work great and are really simple to customize.
https://play.google.com/store/apps/details?id=jun.ace.piecontrol
Now, you need to remove the soft keys in order to gain extra screen space and to protect yourself from potential bugs on the user interface.
To do that, you need to edit your build.prop with an editor or manually with a text editor and add this line.
qemu.hw.mainkeys=1
Now, on the next boot your device have the soft keys disabled.
To protect the status bar from being bugged, we need to change the lcd density of our display in order to allow a phone status bar (the phablet one bug on low resolution displays, and on tablets without sofkeys, we need a status bar.
To do that, we need to edit from the build.prop editor the "ro.sf.lcd_density" parameter and set it to something above 214 (nexus 7 have 213 and it enable the phablet interface, and on 214 it enable a full phone interface, but with small icons and more work space, you need to test and find the most usefull dpi for your device)
Now, we need to install the "magic app", and start testing resolutions and trying to find the most confortable for us, I have the paid version and use on the nexus 7 (16:10 or 8:5) 480x768 since it allow GREAT performance improvement and a good image quality for my screen size.
https://play.google.com/store/apps/details?id=com.nomone.resolution_changer
One example of a game that work GREAT with this trick is N.O.V.A. 3, on the tegra 3 plataform it is almost inplayable, and with the trick, on my nexus 7, it looks like this.
So, start testing this, and post your results, configs and devices.
Help us resolving the screen resolution fragmentation on devices!
And mods, please, help the post with a good language correction XD
Edit: Changed the APK link, to a new one, the new app have onscreen buttons to fix the navbar problems, so, pie controls are no longer needed, I leave the link here onlfy for people to know another alternative, thx for NoMone Devs!
i am planning to buy a 7 or 8" android with high resolution and was a bit worried about gaming performance because of the high resolution.. can you post a video of the performance gain plz?
Whoa! I might give this a go when I get home. Good Job.
i am interested for feedbacks in other heavy games like modern combat 4
this!
what android device and other mobile devices lacks.
there's no setting to set the resolution!
people out there always suggest me to change the dpi, but hell no!
"dpi" is not physical resolution, it just changing icon and other ui element to small or big.
this terms confuse many people.
they think DPI is the screen resolution.
and.... i just cannot understand the hype,
many vendors put high res 1080p on 5" device?
what the heck!? is it necessary?
what's next? ultra 4K res on 4" screen?
come on.. it's unnecesary and waste of battery.
gpu works hard to get the job done in that resolution. especially gaming.
thank you for sharing this trick for us.
google should consider to put resolution changer on the next android.
and android vendor should realize put hi-res on small screen is just plain dumb.
-----
Sent from Android device
i will try this thank you. . .:good:
It's hard to take a video without a camera, but to give youman example, on 500x800 asphalt 7 give me 60fps on the shangai track, with my 800x1280 default resolution, I have 20fps aprox with a lot of fluctutations, it's a great app, and with GMD hide buttons, is almost perfect.
Antara33 said:
It's hard to take a video without a camera, but to give youman example, on 500x800 asphalt 7 give me 60fps on the shangai track, with my 800x1280 default resolution, I have 20fps aprox with a lot of fluctutations, it's a great app, and with GMD hide buttons, is almost perfect.
Click to expand...
Click to collapse
ah that indeed seems to be very nice! i have tried it on my htc desire not it does not work nothing changed
yeahman45 said:
ah that indeed seems to be very nice! i have tried it on my htc desire not it does not work nothing changed
Click to expand...
Click to collapse
Yes, on the HTC Desire 480x800 display, you need to set it to something lower that it, for example, 360x600, it increase the gaming performance, this trick work great on high res display like the nexus 7 or nexus 10 displays for example, try to reduce the resoution to something that retain the original aspect ratio and be lower that 480x800, 360x600 or 240x400 make a grat change, but im not sure about image quality on this device...
Antara33 said:
Yes, on the HTC Desire 480x800 display, you need to set it to something lower that it, for example, 360x600, it increase the gaming performance, this trick work great on high res display like the nexus 7 or nexus 10 displays for example, try to reduce the resoution to something that retain the original aspect ratio and be lower that 480x800, 360x600 or 240x400 make a grat change, but im not sure about image quality on this device...
Click to expand...
Click to collapse
ok thx i have tried to set it to 360x640 on the free version.. but nothing happens.. it just say "Display scaler free has been granted root superuser permissions" and nothing happens
Mh, maybe this is a device specific issue, have you posted a review or sended the autor an feedback email about it?
Antara33 said:
Hello everybody, and before all, sory for my english
The main objetive of this thread is to provide a guide to increase performance on high density screen GPU bound devices, for example, the nexus 10.
The last year android devices start shiping with very high definition screens, but without the necesary GPU muscle to make them work good.
Since I was a PC gamer, I know the terrible impact of high definition on the gaming performance, and, on this screen size, this is a useless impact, since the extra resolution are practicaly unperceptible.
The past week I spend a lot of time trying to change my device's resolution (a nexus 7) and with kernel modding, it is posible, but don't are great since I only play 1/3 of the devices usage, and the 1280x800 resolution are great for chat, browsing (or posting on the forum ).
Finally I find a great program that allow me to temporary change the display resolution of my device, and with the free version I was allowed to change resolution to 720x450, and on gaming performance, that was a GREAT performance updrade, even, with the wuality sacrifice (and on a 7 inch display, this wasn't a great lose.
In order to do that, I need to disable soft keys, since they bug A LOT with the resolution change, and to use a custom launcher because the default launcher bug too (go launcher ex is my favourite and the only one I test).
So, I leave a guide on how to prepare your device to use this mod to increase gaming performance, and to provide help to everyone who want it.
First of all, you NEED to be rooted.
Now, start with the device preparing.
Wee need a soft keys replacement, I recomend this one, work great and are really simple to customize.
https://play.google.com/store/apps/details?id=jun.ace.piecontrol
Now, you need to remove the soft keys in order to gain extra screen space and to protect yourself from potential bugs on the user interface.
To do that, you need to edit your build.prop with an editor or manually with a text editor and add this line.
qemu.hw.mainkeys=1
Now, on the next boot your device have the soft keys disabled.
To protect the status bar from being bugged, we need to change the lcd density of our display in order to allow a phone status bar (the phablet one bug on low resolution displays, and on tablets without sofkeys, we need a status bar.
To do that, we need to edit from the build.prop editor the "ro.sf.lcd_density" parameter and set it to something above 214 (nexus 7 have 213 and it enable the phablet interface, and on 214 it enable a full phone interface, but with small icons and more work space, you need to test and find the most usefull dpi for your device)
Now, we need to install the "magic app", and start testing resolutions and trying to find the most confortable for us, I have the paid version and use on the nexus 7 (16:10 or 8:5) 480x768 since it allow GREAT performance improvement and a good image quality for my screen size.
https://play.google.com/store/apps/details?id=com.nexter.miniscalerfree
One example of a game that work GREAT with this trick is N.O.V.A. 3, on the tegra 3 plataform it is almost inplayable, and with the trick, on my nexus 7, it looks like this.
So, start testing this, and post your results, configs and devices.
Help us resolving the screen resolution fragmentation on devices!
And mods, please, help the post with a good language correction XD
Click to expand...
Click to collapse
Hey I bought the app and it works fine i tried most of the resolutions and even a custom one but it seems that no resolution lower than my physical one will go full screen i always get black borders do you get this too?
thanks a8 soc
I tried tweaking my resolution to a higher one yet nothing happens on my Alcatel OneTouch T10. Any fix on this?
Sory for the lazy responce, I have so much time working and other personal things I read on the store that the apk only make the new resolution use the full screen on 4.2+ so if you are on 4.1-, you have it with black borders, sory, but I cant do anything for this :/
is there any way after change resolution for fix buttom touch key(it doesnt work physical touch key)? or any idea where is touch key config file or something like that related in root?
THUNDERASS said:
is there any way after change resolution for fix buttom touch key(it doesnt work physical touch key)? or any idea where is touch key config file or something like that related in root?
Click to expand...
Click to collapse
I don't know, I suppose, android mao this keys as a touchscreen surface or something like that, the most easybway is using gmd hide softkeys and with it, trigger a softkeys quick navbar and play with this, I am using Paranoidandroid right now and with the pie controls I fix all my problems, and on smanager I created 2 scripts to execute the commands to change resolution, one for the 500x800 for gaming and the other to 1280x800, the default resolution of the nexus 7.
Try it and leave me a comment with your experience.
Antara33 said:
I don't know, I suppose, android mao this keys as a touchscreen surface or something like that, the most easybway is using gmd hide softkeys and with it, trigger a softkeys quick navbar and play with this, I am using Paranoidandroid right now and with the pie controls I fix all my problems, and on smanager I created 2 scripts to execute the commands to change resolution, one for the 500x800 for gaming and the other to 1280x800, the default resolution of the nexus 7.
Try it and leave me a comment with your experience.
Click to expand...
Click to collapse
Thanls for your reply.i have mtk quad core 6589T 1.5 ghz device with powervr 544MP1 and 1 gb ram . My screen is 1080p. i think gpu cant handle this resolution sometimes occur wierd lag and some highend games cant playable.After change resolution to 720p and 320 dpi everything perfect games performance increase %80-100 even memory consumption decreasing.(100mb).i am using with pie control but i want to using continiusly 720p i think after change resulotion touch key coordinates change over screen size.if i found that responsible cfg file or something maybe i can handle this.i am still searching..
THUNDERASS said:
Thanls for your reply.i have mtk quad core 6589T 1.5 ghz device with powervr 544MP1 and 1 gb ram . My screen is 1080p. i think gpu cant handle this resolution sometimes occur wierd lag and some highend games cant playable.After change resolution to 720p and 320 dpi everything perfect games performance increase %80-100 even memory consumption decreasing.(100mb).i am using with pie control but i want to using continiusly 720p i think after change resulotion touch key coordinates change over screen size.if i found that responsible cfg file or something maybe i can handle this.i am still searching..
Click to expand...
Click to collapse
For me, the way to go is sticking with default res for everything except gaming, as I say, I have two scripts on 2 widgets on my main screen, one with the commands
su
wm size 500x800
And the other with the commands
su
wm size reset
on jely bean 4.3 this commands set the override resolution of the screen.
on android 4.2.x the wm have to be replaced with am.
The app launch this terminal commands and override our resolution, but since I cant buy the app because of credit card and legal issues on argentina, I made my own scripts with smanager and swidgets . Quick on the fly change, and "letz rack!"
i am using this fantastic program on my thl w8s to scale resolution from 1080p to 720p during games and the speedup is fantastic...i set tasker to autolaunch the app when i click on the game icon, and once finished the game just click on fixes/reset resolution to bring everything back to 1080p . this program is great and the only one i have found...let's hope the developer doesn't abandon it and keeps making it better....and with a better integration in tasker maybe
Hello,
I am visually impaired and I want to use a tablet as a phone, because everything looks bigger on a big screen.
But some apps look different on a tablet than on a smartphone.
They show more content on one screen if you use a tablet than if you use a smartphone.
If you then set large fonts and an enlarged display, elements overlap in the display.
Is it possible to use a tablet as a phone and make the app believe, that it is a smartphone when it is a tablet?
My smartphone is rootet and I have already tried some things.
I have changed ro.build.characteristics=tablet to "phone" (build.prop)
But that did not help.
Andreas
Change DPI. Lower means bigger. You can adjust that in developer settings, in the "smallest width". Play with that number until you find the good value. Keep in mind, every restart will reset that value to default.
Note that the Android's window size and the device's screen size are not the same. . For example, the area within the window that is used by an app can change if the window becomes too big to fit on the screen.
Read here:
Android: How to use "adb shell wm" to simulate other devices
So I bought a Nexus 10 for development and was super excited by the prospect of being able to simulate other devices using the "adb shell wm" command, with its size, density, and overscan subcomman...
stackoverflow.com
BTW:
Smartphones usually have a screen measuring between 3.5 – 4.3 inches. The screens of tablets measure between 7 – 10.5 inches, they look like a large smartphone but with additional capabilities
xXx yYy said:
Smartphones usually have a screen measuring between 3.5 – 4.3 inches. The screens of tablets measure between 7 – 10.5 inches, they look like a large smartphone but with additional capabilities
Click to expand...
Click to collapse
That is right. Tablets look like a large smartphone. The screen of my tablet has three times the space of the screen of my smartphone. This could mean, that everything is three times as big as on my smartphone. But that is unfortunately not the case.
If you then set large fonts and an enlarged display, elements overlap on the display.
I would like to have a tablet, that behaves identical to a smartphone and everything on the screen looks exactly like on the smartphone, only three times as big.
The tablet knows the physical size of the screen. Otherwise it would not know the ppi-Value. Does anybody know in which file this information is?
Maybe the tablet knows the physical size of its screen ( screen size ), but that's absolutely not of any interest in your case: it's Android's window size ( viewpoint - resolution ) what matters.
You have to find the suitable combo of PPI related to resoulution ( window size ). Both values
wm size
wm density
can get set in Android's system file
/data/data/com.android.providers.settings/databases/settings.db
what is a SQL database