An interesting (and incredibly useful) idea would be a simple app to toggle screen resolutions and lcd densities. This would alow you to run 90% of your stuff at the Kaiser native 240 x 320 lcd density 120 and toggle to something better to run apps or games that require the andoird native resolution to show the whole screen. Not sure if this would be a simple app to write or if it would be very difficult to do...I'm not a programer...just an observer, but this sort of app would be useful across ALL builds of android.
I'm pretty sure this isn't possible. Someone else could confirm that.
roberto188 said:
An interesting (and incredibly useful) idea would be a simple app to toggle screen resolutions and lcd densities. This would alow you to run 90% of your stuff at the Kaiser native 240 x 320 lcd density 120 and toggle to something better to run apps or games that require the andoird native resolution to show the whole screen. Not sure if this would be a simple app to write or if it would be very difficult to do...I'm not a programer...just an observer, but this sort of app would be useful across ALL builds of android.
Click to expand...
Click to collapse
I have two HaRET-startupfiles, one with QVGA and one with the resolution from the G1. But switching needs a restart.
Does anyone know how to change resolution in Android manually? Maybe we could make a simple shell script.
Well, if you're using a Kaiser, the fact that it's determined by your default.txt/startup.txt is exactly why you need to reboot - because they're already determined before booting up (that is, each time you boot Android, it looks at what resolution to use). Because it's being determined there, you can't change it while it's booted up. I don't know if it would be possible to have the resolution be determined somewhere else, but that's the way it is at least for now.
Moved as software idea and not ROM Development
Related
I have the sprint vogue that I ran Android 1.5 from my sd card with sprint network. I updated to eclair on the sd card but find my phone says T-Mobile, don't think its a big deal.When I was running 1.5 I was able to find apps like pandora to down load, know on t-mobile network and eclair a lot of apps are missing? Is their a way to unlock the market.
You need market enabler.
http://code.google.com/p/market-enabler/
Edit: This pretty much just adds paid apps.
skipbarker said:
You need market enabler.
http://code.google.com/p/market-enabler/
Click to expand...
Click to collapse
I don't know if that will work cause he was able to download Pandora before and that's a free app, market enabler just to gives you paid apps
My bad. I misunderstood.
http://forum.xda-developers.com/showthread.php?t=628353
Read #5
It's a problem with the Android SDK.
Starting with 1.6, Google introduced screen sizes: Small, Medium, and Large. Our devices have Small Screens (along with the HTC Tattoo). The G1/Dream has a Medium screen, and the Droid/Nexus a Large screen.
The problem is the SDK defaults to Medium and Large screens. It's up to the application developer to test the application for Small screens and proactively add the indicator for Small screen support.
Most developers never bother to indicate the app can run on Small screens, so it gets excluded from your view.
I'm not sure if the small screen thing is linked to the /data or your Google user account. If I knew which, I'd figure out some way to spoof it, so we can get the full market on small screens. If it's on the /data somewhere, then that's a much easier fix.
The fact that clearing your /data and booting up a 480x320 fixes it, seems to indicate it's a value in the /data. It'd be interesting to do a dump of two /data directories with only the market resolution changed and see how they differ on a binary level. Then perhaps we can add a patch to the menu of NoMoRootfs (or a patch that's applied every bootup... or lock down the file that's modified).
If it's on the account, then either you'd have to intercept the Market App's data packet that indicates screen size and modify it proactively, or you'd have to change parts of the SDK to report the screen size as larger than it really is (this would be hard to do because apps use that interface too... you'd have to be able to detect if the request is coming from the Market App).
jnadke said:
It's a problem with the Android SDK.
Starting with 1.6, Google introduced screen sizes: Small, Medium, and Large. Our devices have Small Screens (along with the HTC Tattoo). The G1/Dream has a Medium screen, and the Droid/Nexus a Large screen.
The problem is the SDK defaults to Medium and Large screens. It's up to the application developer to test the application for Small screens and proactively add the indicator for Small screen support.
Most developers never bother to indicate the app can run on Small screens, so it gets excluded from your view.
I'm not sure if the small screen thing is linked to the /data or your Google user account. If I knew which, I'd figure out some way to spoof it, so we can get the full market on small screens. If it's on the /data somewhere, then that's a much easier fix.
The fact that clearing your /data and booting up a 480x320 fixes it, seems to indicate it's a value in the /data. It'd be interesting to do a dump of two /data directories with only the market resolution changed and see how they differ on a binary level. Then perhaps we can add a patch to the menu of NoMoRootfs (or a patch that's applied every bootup... or lock down the file that's modified).
If it's on the account, then either you'd have to intercept the Market App's data packet that indicates screen size and modify it proactively, or you'd have to change parts of the SDK to report the screen size as larger than it really is (this would be hard to do because apps use that interface too... you'd have to be able to detect if the request is coming from the Market App).
Click to expand...
Click to collapse
That is a great idea.
Do you have the capacity to perform the differential on the two directories?
I have deodexed the 1.6 Vending.apk and can post the source for everyone to review. I think the more eyes on this the better.
The only reason I run 320x480 is because I want a full market 100% of the time.
All is working, I used the link that PacyWhitter gave, followed Tatnai directions and know have full market!!!
myn said:
That is a great idea.
Do you have the capacity to perform the differential on the two directories?
I have deodexed the 1.6 Vending.apk and can post the source for everyone to review. I think the more eyes on this the better.
The only reason I run 320x480 is because I want a full market 100% of the time.
Click to expand...
Click to collapse
Yeah, I can do it, though it'd be easier to do it on two data.img files (might have to go back to WinMobile for that). Or I guess I could flash the kernel and wipe my data and export the result each time to a binary file. I'd still be interested in seeing the Vending.apk.
I already know where the Market apk is getting its info from. In android.utils there's a class called DisplayMetrics. The Market apk is likely getting its info from there. It'd be possible to spoof it by recompiling the source with a hardcoded value, but that'd affect applications as well. It'd be much harder to do it for only the Market/Vending apk.
The thing I'm interested in, is that obviously if the "boot up at one resolution, switch back" trick works, then it's not sending the resolution to the server every time. This means it has to be storing the data, or a hash of the data, somewhere.
This guy has a fascinating website on similar subjects:
http://strazzere.com/blog/
There's also a way to use the Market from the emulator:
http://www.anddev.org/viewtopic.php?p=28991
Perhaps I can start there and see if I can reproduce the problem, then produce the solution in a controlled environment.
graphic914 said:
All is working, I used the link that PacyWhitter gave, followed Tatnai directions and know have full market!!!
Click to expand...
Click to collapse
People seem to indicate it resets after a few days, so you will have to redo it until I have time to see if I can fix it.
jnadke said:
This guy has a fascinating website on similar subjects:
http://strazzere.com/blog/
Click to expand...
Click to collapse
That is one of my fav sites for Android dev. Great site .
Started Community Market Project here
I've had my prop.build changed for a while from the default 240 to 190 and love the high-res look it provides, but obviously some apps don't automatically scale right with the change.
I heard something about either turning Compatibility Mode on or off to fix the problem, but have no clue where to make this change.
TL;DR
How do I turn compatibility mode on or off?
There's no such thing. Once you change that file, the display driver will display everything at 190PPI. It's not an application based thing (which is what what you're talking about sounds like), so if you want to run an application that doesn't support the res hack, you'll just have to edit prop.build back to 240 and reboot. It's pain, and that's why I haven't bothered with it.
Edit: Just speculation; you capitalized 'Compatibility Mode' as if it were an actual setting somewhere. Just to make sure, the res hack is in no way supported by Samsung or default AOSP settings.
Yeah I assumed it was a setting somewhere but I guess I must have read something and misconstrued it to apply to what I was thinking about.
SG Pillar said:
Yeah I assumed it was a setting somewhere but I guess I must have read something and misconstrued it to apply to what I was thinking about.
Click to expand...
Click to collapse
I'd assume so. But yeah, just bear in mind that if you're editing files like that, then it's most likely not going to be very well supported, and normally there isn't going to be a fix (unless it's built into a ROM by a dev, in which case the dev probably wouldn't think to release a standalone fix anyway). But that's the joy of Android, right?
download Spare Parts in the market. its in there.
Hi,
I've set my Note to 240 density but find that the S-Memo page is now the size of a tiny post-it. Is this something you have to live with or is there a way of increasing the size of the memo page?
Cheers for any feedback.
I'm afraid it is too late for me to search, but there is a post in the 'themes & apps' forum about a customised apk to handle this.
Frankly I gave up with changing the DPI as most apps were impossible to install on the Market. I gather I may be able to fix that, but life is a little too short.
I think he means this thread
jeromepearce said:
I'm afraid it is too late for me to search, but there is a post in the 'themes & apps' forum about a customised apk to handle this.
Frankly I gave up with changing the DPI as most apps were impossible to install on the Market. I gather I may be able to fix that, but life is a little too short.
Click to expand...
Click to collapse
In order not to have compatibility problem with market apps your DPI needs to be one of those officially supported by Android:
320,240,160...
If you're at 240 dpi, then there should be no problem installing apps from the market at all. I use the memo apk from here: http://forum.xda-developers.com/showpost.php?p=20803605&postcount=41 as it works with the later roms in particular.
I just switched from Android after a couple of years and so far I really like it. I do have a few issues/questions. I decided to try WP8 but didn't want to drop a lot of money on it so I went with the Nokia Lumia 520.
I notice that when I go to some apps or resume them, it gives me that 'Resuming' or whatever message for a few seconds. It just doesn't seem as snappy as my Galaxy S2 was. Is this Windows speed problem, or a limitation of the device that I have (520)?
I love the live tiles idea (widgets really). Am I able to resize them in any way?
Also, themes? I realize that you can only really change the tile colors, but what about fonts and things like that? I'd like more of a selection of my background color rather than just light or dark too.
Other than this, I'm really liking this phone! I might go all out and get a 1020 later after the price drops a bit.
tsantsa said:
I just switched from Android after a couple of years and so far I really like it. I do have a few issues/questions. I decided to try WP8 but didn't want to drop a lot of money on it so I went with the Nokia Lumia 520.
I notice that when I go to some apps or resume them, it gives me that 'Resuming' or whatever message for a few seconds. It just doesn't seem as snappy as my Galaxy S2 was. Is this Windows speed problem, or a limitation of the device that I have (520)?
I love the live tiles idea (widgets really). Am I able to resize them in any way?
Also, themes? I realize that you can only really change the tile colors, but what about fonts and things like that? I'd like more of a selection of my background color rather than just light or dark too.
Other than this, I'm really liking this phone! I might go all out and get a 1020 later after the price drops a bit.
Click to expand...
Click to collapse
Dude ....windows OS is way different from android ....
These are different types of platforms
The things u can do in android ....probably u can't do in windows phone 8.....so go with the flow ...
Sent from my HTC Explorer A310e using xda premium
Apex-Predator said:
Dude ....windows OS is way different from android ....
These are different types of platforms
The things u can do in android ....probably u can't do in windows phone 8.....so go with the flow ...
Sent from my HTC Explorer A310e using xda premium
Click to expand...
Click to collapse
I understand that.
So, with my issue with it being a tad slow, is it WP8 or the device?
Could be your device. My Ativ S is fast as hell.
You can try a reset. I don't know, how it is named in english, but it should be somewhere at "About Phone".
No, that won't help.
First of all, you did buy one of the lowest-end Windows phones currently available. Don't buy a Tata and expect it to perform like a Ferrari. They'll both get you where you're going, but the experience won't be the same.
Second, the problem is almost certainly either with high-RAM apps that got "tombstoned" (suspended to disk, removed from RAM) when you switched to another task, or legacy Windows Phone 7.0 apps which didn't support fast resume at all. It could also be that the app runs a bunch of code when it gets resumed, which is just the developer's fault and there's nothing to do about it.
You can resize the live tiles by pressing-and-holding on them, then tapping the button that appears in the corner of the tile. All have a "normal" size and a "small" (1/4 of normal) size; some will also offer a "wide" size (twice the width of normal).
Unfortunately, Change Background Color (or even set a Background Picture) is actually not possible on WP8. I hope this changes with WP 8.1 So the only design Change you can make is to Change the Accent Color atm.:cyclops:
Thanks.
Has anyone noticed that the sides of the screen when playing certain games is actually badly scaled, so the game is essentially playing off screen.
Only about 5mm on each side. But in certain circumstances you can miss something.
I use FHD, couple of the games I've noticed it on is Arkanoid Vs Space invaders (great game)
Sonic forces (not so Great)
Same thing on QHD.
Is this just a bug in OnePlus' new system? Or is it an Android 12 /12.1 issue?
Cheers
PS: notice the left side is missing text
dladz said:
Has anyone noticed that the sides of the screen when playing certain games is actually badly scaled, so the game is essentially playing off screen.
Only about 5mm on each side. But in certain circumstances you can miss something.
I use FHD, couple of the games I've noticed it on is Arkanoid Vs Space invaders (great game)
Sonic forces (not so Great)
Same thing on QHD.
Is this just a bug in OnePlus' new system? Or is it an Android 12 /12.1 issue?
Cheers
PS: notice the left side is missing text
Click to expand...
Click to collapse
I just tried to duplicate what you mentioned but was unable to replicate this. Did you by any chance change the fonts/display/installed a different font? I do recall from my OnePro 7 days when i had display font/zoom combo set too high and I was unable to use few apps with the same effect you mentioned here. Just a thought
Gr8man001 said:
I just tried to duplicate what you mentioned but was unable to replicate this. Did you by any chance change the fonts/display/installed a different font? I do recall from my OnePro 7 days when i had display font/zoom combo set too high and I was unable to use few apps with the same effect you mentioned here. Just a thought
Click to expand...
Click to collapse
Oooh I'm not too sure but I have only replicated what I used to have on my 8 pro, never had this issue.
Let me have a look. It's worth a punt.
I am getting old so need slightly bigger fonts
Gr8man001 said:
I just tried to duplicate what you mentioned but was unable to replicate this. Did you by any chance change the fonts/display/installed a different font? I do recall from my OnePro 7 days when i had display font/zoom combo set too high and I was unable to use few apps with the same effect you mentioned here. Just a thought
Click to expand...
Click to collapse
Here's my display settings for font and display.
Both at default.
DPI is also unchanged.
Tested all settings within scaling with no affect.
Also this does not affect all apps, only the two I mentioned and potentially others.. if you didn't test with them apps then it wouldn't be a valid test.
Unless you did. Then I'm stumped.