Related
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
Hello XDA,
I have a problem, and its bothering me every day.
After installing my first ROM, the Bionix V, a small part of my vibrant screen got broken. Is a 0,3 cm from bottom?
I can handle fine almost every app, but in some that use this part I can do nothing.
Now I using the 1.3.1 Bionix Rom ( very good ROM )
So I tried to buy new Touch Screen, but is too expensive now ( is close to 300 dolars in my country). So I will w8 a little bit to get cheap.
Until then, I need to use some cheat to use the program that use that small LCD part. It’s a Rotation tool.
The problem is, some app doesn’t turn Left or Right, and even I command the app in the rotation tool. I tried to use a lot of rotations tools, but some app (Games is the majority) don't turn.
So I just ask if there’s a way to cracked some part of the android to unlock the ability to turn every app to every side I want (the called 270º).
I wanna to play a lot of games that use that tinny part of the LCD but can't do nothing....
Can u help me guys?
PS: Sorry the bad English....
Cyanogen mod allows you to do that as default for every app.
The rom is worth flashing, especially in your case
crazy25000 said:
Cyanogen mod allows you to do that as default for every app.
The rom is worth flashing, especially in your case
Click to expand...
Click to collapse
How?
I unchecked every rotation except 270, but apps can still overide. Angry birds, for instance, still loads at 90.
beren28 said:
How?
I unchecked every rotation except 270, but apps can still overide. Angry birds, for instance, still loads at 90.
Click to expand...
Click to collapse
If you have other display settings or an app that modifies system settings, they might interfere with it.....LauncherPro rotation settings used to conflict with my system settings...just an example, but not sure if that would be why =/...I'll mess around with my settings and see why it would do that.
I run launcher pro, but even when I switched to ADW, angry birds still insists on 90 degree.
This is worth looking at, coding might be different..
http://forum.xda-developers.com/showthread.php?t=1084850
Hello.
Im currently using Cognition V1.31, this rom includes the new Market.
What happens when I changed the DPI is that some apps wont install trough market, it says that my device is not supported. (The install button isnt present)
If I delete the new Market, and replace it with the old market everything works again.
Apps that wouldn't install using new market and DPI is, Skype and Lookout
Anyone else that have the same issues?
Yeah, Im having this problem with a lot of apps. I didn't know it was because of the DPI change, i thought it was just the new market that was having these problems?
Set dpi to 240, install apps and then set dpi back to desired custom dpi
For me it happens also with old market app.
Keeping the old market until its fixed.
Sent from my GT-I9100 using XDA Premium App
App incompatibility with custom dpi = Android bug?
I'm on an Evo, but have the same problem. I spoke to the developer of one affected app, (AutoKiller,) and to the best of their knowledge the incompatibility issue is not related to their code.
The problem is also evident at market.android.com, which identifies many apps as incompatible as of late, when using custom dpi scaling.
After picking through the manifest files of a handful of apps, I've found no relation between the apps that exhibit this problem, or even anything that sets them apart from apps that will still install normally. AutoKiller even specifies in the manifest that any density screen should be supported. Additionally, there is no apparent connection to the target and required SDK versions.
I'm about ready to call this an Android bug, maybe a Market bug, even. The Android Dev Guide page on "Supporting Multiple Screens" implies that valid ranges for an hdpi display are between 200 and 279. I tested this range on my Evo and found that not a single framework resource breaks within it. Immediately outside this range - i.e. 199 or 280 - certain screen elements fail to display properly.
Honestly, it's getting annoying really fast. If I have some more time to look into it later, I may file a bug at Google Code. At the very least, the cause of this "incompatibility" nonsense should be documented in the Android Dev Guide, so that it can be anticipated, understood, and avoided when appropriate.
(I can't post links yet, so find the "Supporting Multiple Screens" document @ developer.android.com/guide/practices/screens_support.html if interested.)
Im running on an Xperia Play with a DPI of 200 (Default: 240) and cant download essential apps that have said bug (Ex. Facebook). Hopefully we find a solution.
I thought I was the only one with this problem. I just recently started using Gingermod asop rom and everything was working perfect until I changed DPI and tried to update some apps.
doesnt do anything with the dpi but.
http://amip.tools-for.net/wiki/android/marketaccess
It's not a bug, it's a feature. The market checks your device resolution against what the dev reported to work. If it's too high the app might not work at all or draw incorrectly. Some apps have HD versions which work with higher DPI's check those out.
GIR said:
It's not a bug, it's a feature. The market checks your device resolution against what the dev reported to work. If it's too high the app might not work at all or draw incorrectly. Some apps have HD versions which work with higher DPI's check those out.
Click to expand...
Click to collapse
Devs I have spoken to report that they have NOT intended for this to happen. Additionally, I have yet to find a single APK which suffers from this problem and has DPI constraints defined within its AndroidManifest.xml.
I have ripped apart over half a dozen apps trying to find the cause of this, and as a matter of fact, the first one I opened up explicitly specifies compatibility with ANY screen density.
Feature? That's not what it's called when even the devs don't have control over it.
(For clarity, an optional declaration in an application's AndroidManifest.xml is what determines screen density constraints, if any. By default, applications willingly install and run on any screen density for which they have fitting resources. From the dev's standpoint, these densities are not measured in exact pixels, but instead in named ranges (ldpi, mdpi, hdpi, and xhdpi.) When outfitted with resources that match the screen density range, the system scales resources at runtime to meet its exact needs. For more information about how Android handles screen density, please review the article I referenced before.)
You guys are on the right track.
Custom dpi (lcd density) seems to cause the "incompatible" problem with the new market.
http://forum.xda-developers.com/showthread.php?t=1196417
Going back to 240 dpi and clearing market data makes everything work as it should.
You can then go back to your custom dpi, but most users are reporting the problem comes back after a while.
Thanks for the heads-up - I had no idea it would have been from the DPI setting.
It would be great if there were a way to spoof density, so the market always identifies at 240dpi, (or appropriate.) Switching and rebooting all the time sucks. Anyone with some smali skills want to try hard-coding it into the new Market.apk? I will be trying, but I've had zero luck with APK modding thus far
Sent from gingerbread-evo-deck
Google is apparently aware of the problem and considering what to do about it. Post: "Anyone with different LCD density and Market issue, look here"
In the meantime, I have found that doing a soft-reversion to 240 with LCDDensity For Root when I want to run updates is not too much hassle.
thanks bazofia
bazofia said:
Set dpi to 240, install apps and then set dpi back to desired custom dpi
Click to expand...
Click to collapse
Thanks man!
Check out this thread, worked for me:
http://forum.xda-developers.com/showthread.php?t=1839871
Just download one of the attached files and flash in CWM.
Sent from my GT-I9100
I've been in touch with Google the past few weeks cause I hardly get any updates through the market since about three months.
Google noticed that everybody or at least most users with a non-standard screen density have this issue. Many apps give a 'your device is not compatible with this application' error when browsing the internet/desktop market version (not the phone market app).
And than in the market you won't see your apps under 'My Apps'
When you switch back to 'default density (240) the problem is gone.
Google is investigating the issue but does not know yet if they will support non-standard densities.
If this is a double post, sorry for that.
They dont't need to support non standard dpi but they should let applications to show up in Market. This is the reason I downgraded the Market version on my phone, but this is not a solution. I hope Google will let the users decide what dpi is best for them.
Yep but as long as they fear claims and complaints nothing may happen...
At the same time the 2 persons I've been dealing with have been very cooperative and asked me lots of questions. Gave them app details, logs and after a few weeks they came back with this conclusion.
Which sort of makes respect them, after all, I'm only one of nearly 200 million Android users!
blackspp said:
I've been in touch with Google the past few weeks cause I hardly get any updates through the market since about three months.
Google noticed that everybody or at least most users with a non-standard screen density have this issue. Many apps give a 'your device is not compatible with this application' error when browsing the internet/desktop market version (not the phone market app).
And than in the market you won't see your apps under 'My Apps'
When you switch back to 'default density (240) the problem is gone.
Google is investigating the issue but does not know yet if they will support non-standard densities.
If this is a double post, sorry for that.
Click to expand...
Click to collapse
Seen a couple of these pop up so far. The problem has been affecting me for a while now, but I just figured out what caused it last week. Lots of people (myself included) seem to have thought nobody else had this problem.
Post: Changing DPI and new market makes apps incompatibility
Post: [Q] Cannot update multiple installed apps, is it the new market?
blackspp said:
Yep but as long as they fear claims and complaints nothing may happen...
At the same time the 2 persons I've been dealing with have been very cooperative and asked me lots of questions. Gave them app details, logs and after a few weeks they came back with this conclusion.
Which sort of makes respect them, after all, I'm only one of nearly 200 million Android users!
Click to expand...
Click to collapse
I'm almost surprised it took so long for them to notice that trend, considering they surely have facilities to notice trends in their databases. Score one for XDA! (Very cool of Google to provide such tailored support, though!)
So, no "permanent" dpi change solution for now?
I kinda missed my streak because of this high DPI on the SGS2. Everything getting so big, i losed some of my productivity...
schizo said:
So, no "permanent" dpi change solution for now?
I kinda missed my streak because of this high DPI on the SGS2. Everything getting so big, i losed some of my productivity...
Click to expand...
Click to collapse
To "permanently" change your DPI to "XYZ", add these lines to /data/local.prop:
Code:
ro.sf.lcd_density=XYZ
qemu.sf.lcd_density=XYZ
(Note: If /data/local.prop does not exist, you may create it yourself.)
- OR -
If you would prefer that the change not persist when flashing a new ROM, you could edit /system/build.prop, which should already contain the "ro.sf.lcd_density" property unless you're on a 160dpi device. /system/build.prop will be overwritten any time you flash a new ROM, even if you do not wipe first.
Both of these methods will require a reboot for changes to take effect.
---
Alternately, if you would like to avoid editing system files by hand, there is an app called Blade Buddy which allows you to modify various properties in /data/local.prop, including LCD density.
To save your changes from Blade Buddy, tap Menu -> Save. If you choose not to reboot, you can then tap Menu -> Apply to apply the changes in RAM and restart the UI to see them in action. (Applying density without rebooting seems to be hit-or-miss.)
---
Regardless of how you set your LCD density, the Market will exhibit the incompatibility bug.
As a workaround, I have set my density "permanently" with Blade Buddy and use LCDDensity for Root to revert to default once and a while, so I can launch the Market and get all my updates. LCDDensity for Root is designed specifically to change density temporarily, on-the-fly, and on as many devices as possible.
Thanks, Mr. Bezeek. Actually what I'm looking is the permanent solution of not having to temporarily switch back and forth. As for editing .props I already have experience before with my Streak. Hehehehe
But still, thanks anyway and hope you not offended. I like it the way you help others in precise and detailed manner. Keep it up, bro *thumbs_up*
Not a problem, just doing my bit to make sure the information is out there.
As far as avoiding the temporary switching goes, I'll be on vacation for the next week, but I intend to try a little hacking when I get back, to see if I can find a way to spoof the dpi. That is, if Google doesn't throw us a bone in the meantime.
Users have reported that older versions of the Market still work. The one shipped with the latest OTA for my Evo worked for me, and I suspect that any version released before they changed the Market UI will. YMMV.
Just thought I'd toss this out there... I have a Droid X. When running MIUI 1.8.19 on it, I don't have this problem. I can set my density to 200 and the newest market (3.1.3) still works as expected. Seems as though with all the other ROMs I've tried (both blur and 2nd init), I couldn't access a lot of stuff unless I set density back to 240. I can't remember for sure, but I might have been able to set stock .602 (rooted) to 200 with no problems as well - but I'm a little iffy on that. So it would seem that MIUI has done something (perhaps not intentionally) to work around the problem. I just wish I had the smarts to figure out what that might be.
Edit: I realize that this is not a Droid X forum, but I was thinking this info might help somehow. Thanks.
tslovejoy1969 said:
Just thought I'd toss this out there... I have a Droid X. When running MIUI 1.8.19 on it, I don't have this problem. I can set my density to 200 and the newest market (3.1.3) still works as expected. Seems as though with all the other ROMs I've tried (both blur and 2nd init), I couldn't access a lot of stuff unless I set density back to 240. I can't remember for sure, but I might have been able to set stock .602 (rooted) to 200 with no problems as well - but I'm a little iffy on that. So it would seem that MIUI has done something (perhaps not intentionally) to work around the problem. I just wish I had the smarts to figure out what that might be.
Edit: I realize that this is not a Droid X forum, but I was thinking this info might help somehow. Thanks.
Click to expand...
Click to collapse
Good to know! Being able to compare a "working" ROM to mine will surely make it easier to identify a workaround.
Nice info never noted this before!! yeah i dint get any updates over a last few weeks. Im at 200 dpi.
I've been switching back to 240 periodically to get updates, not a big deal to me, but would be nice if things worked normally. My only real issue with running lower dpi (160 here) is that some apps don't scale properly. IE the Dialer.
blackspp said:
I've been in touch with Google the past few weeks cause I hardly get any updates through the market since about three months.
Google noticed that everybody or at least most users with a non-standard screen density have this issue. Many apps give a 'your device is not compatible with this application' error when browsing the internet/desktop market version (not the phone market app).
And than in the market you won't see your apps under 'My Apps'
When you switch back to 'default density (240) the problem is gone.
Google is investigating the issue but does not know yet if they will support non-standard densities.
If this is a double post, sorry for that.
Click to expand...
Click to collapse
Thank for this information! I've been wondering why some standard apps weren't compatible.. It's weird, since they work if you side load them ...
I hope google finds a solution.
---------- Post added at 02:59 PM ---------- Previous post was at 02:51 PM ----------
I just switched from 190dpi to 160. Angry birds seasons is now compatible( wasn't with 190dpi)
Dank U vriendelijk
Wow. This has been driving me crazy trying to work out why apps where missing. Guess I need to swap to 240 occasionally for updates.
I am using 200 / 192 DPIs from day one. (3 months). its working fine.I never faced incompatibility issue with market. however some games doesn't run correctly which usually i don't play.
i have a workaround idea, and i started a thread to discuss here: http://forum.xda-developers.com/showthread.php?t=1288150
The google support thread for this is here: http://code.google.com/p/android/issues/detail?id=19744#makechanges
I still have this issue and if you do a web search you'll see that many still do. Reply in the support thread to raise awareness ! or if you have a workaround please share You also might want to check out his Idea thread, if you have some developing skill please help.
schizo said:
So, no "permanent" dpi change solution for now?
I kinda missed my streak because of this high DPI on the SGS2. Everything getting so big, i losed some of my productivity...
Click to expand...
Click to collapse
I came from a streak as well and it's this is the biggest annoyance I've had with the sgsii.
The reason why i enjoy Android over any other mobile OS is because i can tailor the OS to how i want it. Not allowing me to download apps because I'm using a non standard density is crippling.
For now, i urge everyone to go to the google support thread and simply press click the star. No need to comment (unless you found a fix), the more stars the issue gets, the more likely Google will look into it.
Seems to be fixed with the latest market version.
Sent from my GT-I9100 using XDA App
Ke11ett said:
Seems to be fixed with the latest market version.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
yeah i seem to be ok ive just got the version from androidpolice last night. im on 3.3.11 now, still cant install stuff from the website though says my phone is incompatible for everything lol
For the sake of completeness (most of you will have noticed this app already): For a change, Samsung have done a fantastic job and released a great app called "Game Tuner". It's simple to use, doesn't even need root, and renders all of the stuff I wrote below obsolete!
What it does is, it renders each game at an individual screen resolution, frame rate, and texture quality (texture quality only working for me since MM upgrade).
All you have to do is install Game Tuner from Google Play (above link), start it, follow the instructions to install GameMode through Galaxy Apps, and you're good to go. Create a custom profile, set default values (e.g. 75% resolution=1080p), activate the profile. Set different resolutions for other games. And if you want to control apps other than games, tap top left menu, and chose "Apps".
I've done the same benchmarks as with the method below, and the results were exactly the same, so it's really working, but without messing up the UI or impairing system apps like the camera.
Hey folks,
I've decided to put together a little wrap-up of the stuff I found regarding the sometimes rather poor 3D performance of the Note 4. This is only for experienced users who are familiar with things as rooting, backups, adb, in general: unbricking their phone if bad things happen. As usual, I don't take any responsibilty if you brick your phone or destroy it in any other way. Just make sure to activate USB debugging, and if anything goes wrong, either follow this guide, or simply reflash your ROM.
Just make sure you make a Nandroid or at least Titanium backup before you try this. Better safe than sorry...
It comes as no surprise that running a cpu at almost 3GHz takes its toll. Demanding games such as Real Racing 3 or XCOM:EW, or emulators such as PPSSPP cause the cpu to heat up rapidly, until it reaches ~80°C, before it gets mercilessly downclocked to cool down. At this point, you start noticing more or less pronounced performance drops. There isn't really much you can do, except using a custom kernel to downclock cpu & gpu, before your phone does.
But apart from that, there is another, even greater performance hog, which is also one of the main reasons for the overheating issue: the QHD resolution of our Note 4's screen. We're talking about a 3.69 megapixel resolution, that's almost twice as much as Full HD (2.07 MP), and exactly four times as much as HD (0.92 MP). Gorgeous and brilliant, beautiful to look at during everyday use, but pushing the Adreno gpu to its limits when it comes to gaming.
So, an ingenious guy called NOMone has created a nifty little tool called "NOMone Resolution Changer", already some time ago. It's available for free at Google Play. It's been widely discussed here on xda and on other forums, but I want to share my experience specifically on the Note 4.
Btw, it seems he only posted here two times, so he's most likely not active anymore, but you should head over and thank him anyway.
Now, if you're thinking "no way, why should I deliberately sacrifice my QHD resolution?", read on nonetheless. Because this tool is extremely easy to use, and if you only switch the resolution before playing a game, and revert afterwards (it's only one click), you won't have to sacrifice any visual quality. The settings stick after a reboot, so make sure to really restore defaults if you want to go back to QHD.
The trick is to use the appropriate resolution and dpi values, so your screen doesn't get mixed up.
The results are impressive, sometimes even staggering. Has anyone ever wondered why PPSSPP doesn't perform better on a Note 4 than it does on a Note 2? Here's the reason. PPSSPP gains so much performance , it's almost unbelievable.
I've also done some benchmark runs to measure the improvements (yeah, I know, benchmarks are bad, but still :angel: ). The improvement is clearly visible and, even more important, reproducable:
GFXBench GL Benchmark 3.1 (Manhattan):
1. 1440p: 449,4 frames, 7.2 fps
2. 1080p: 800,6 frames, 13 fps (+78%)
3. 720p: 1621 frames, 26 fps (+261%)
4. 480p: 2728 frames, 44 fps (+507%)
This is plain awesome. The Note 4 is listed even lower, with 434 frames, in the device list, while the 1080p Galaxy S5 reaches 775 frames.
AnTuTu (gpu score only):
1. 1440p: 16210
2. 1080p: 21253 (+31%)
3. 720p: 22524 (+40%)
4. 480p: 22523 (+40%)
Obviously, by comparing scores 3 and 4, the Note 4 hits the fps limit at HD resolution, so there's no more room for improvement in AnTuTu.
Seascape Benchmark (detail setting: Very High):
1440p: 26.9 fps
1080p: 46.6 fps (+73%)
720p: 53.4 fps (+99%, sometimes hits the frame limit of 59.0 fps)
480p: 59.0 fps (+119%, hits the frame limit constantly).
This is a beautiful OpenGL ES 2.0 test, so no cpu scores interfering with the result. Again the fps limit prevents a higher score, but nonetheless, this is pretty amazing.
Other benefits: if you're using a custom kernel, you can run gpu-intensive games at lower cpu speeds to keep the cpu temperature in check. In my case, XCOM:EW runs smoothly @ 30% (!!) cpu speed. This way, the cpu doesn't heat up to more than 60°C, which means it doesn't get downclocked while playing. If you like, you can also automate the process of setting the cpu speed with the aptly named app "Automate" . Which is fantastic, btw.
Now what about visual quality?
Seriously: it's hard to tell the difference. If you look very closely, you can see the display isn't as sharp in FHD as in QHD. But if you look that closely, you're in constant danger of triggering some random app with the tip of your nose. At normal viewing distance, especially while gaming, it's impossible to tell the difference.
So, are there any drawbacks?
Yes, there are: the UI gets messed up a bit (e.g. bigger status bar, some Samsung apps don't fit on screen anymore), and NOMone Resolution Changer doesn't seem to work with CM12.1. Well, at least for me, and other users reported so as well. I tested it some time ago, while I was on CM12.1, and even thought it was a fake app, which it isn't! Seems that the resolution is somehow hard coded into CM12, and you can only switch dpi. There's probably nothing you can do when you're running CM, except try your luck.
But if you are running a Touchwiz ROM, stock or custom, it should work as intended (Emotion Revolution ROM r10.1 in my case). And you can simply ignore the UI issues, as long as you only switch the resolution for gaming. It's not a real issue then, because the status bar is hidden anyway while the game is running.
If you want to keep your device running at FullHD permanently, it's a bit more complicated: first, you'll need Xposed, so you can use the App Settings module to set Android System and SystemUI to 480 dpi. This'll fix the UI (Not needed. Just reboot)
Some apps like phone, contacts, S-Note scale down to the lower dpi setting, whereas Samsung keyboard and the camera won't (camera works, see post #10 below).
So you'll have to install another keyboard like SwiftKey (if you don't have it already), find a working camera app (3rd party or hacked Note 4 camera), and clear your Google Play data (at least I had to, it wouldn't install any apps after the changes), and you're good to go. There might also be other issues I'm not aware of yet. But apart from the ones I described, everything's working fine so far.
Have fun!
you don't need root to change the dpi and the resolution.
enable usb debugging and adb the following:
adb shell wm density 480
adb shell wm size 1080x1920
adb reboot
if you want to revert back:
adb shell wm size reset
adb shell wm density reset
adb reboot
the changes persist after reboot.
I am using it like that for some time. Everything is much faster. Even the browsing..
the only 2 bugs I noticed is the Samsung keyboard (i switched to swiftkey) and the action memo (c'mon Samsung devs, code properly..)
mitko76 said:
you don't need root to change the dpi and the resolution.
enable usb debugging and adb the following:
adb shell wm density 480
adb shell wm size 1080x1920
adb reboot
if you want to revert back:
adb shell wm size reset
adb shell wm density reset
adb reboot
the changes persist after reboot.
I am using it like that for some time. Everything is much faster. Even the browsing..
the only 2 bugs I noticed is the Samsung keyboard (i switched to swiftkey) and the action memo (c'mon Samsung devs, code properly..)
Click to expand...
Click to collapse
You're right, you don't necessarily need this tool. All it does is simplify the process. And you should really be able to use adb commands to fix your phone when you mess it up. But NOMone's tool comes in very handy when you're away from your pc and need to switch resolutions quickly. In my case, it's when I want to use the camera: the UI is messed up at 1080p and I haven't found a way to fix it yet, except switch back to QHD. Or the other way round: if you want to play a demanding game on the train at lower resolution, but go back to QHD again.
I'm using 1080p resolution permanently now, because I get a smoother UI, a cooler phone, better battery life, and much better performance. I hope they don't give us 5" UHD screens next...
Could you please explain what is wrong with the camera on 1080p 480dpi? I am using these settings and have 0 problems with the camera. Just curious.. If possible please attach a screen shot. Cheers
The UI is messed. I can't see most of the buttons, and can't take a photo, see attached screenshot.
Xelasarg said:
The UI is messed. I can't see most of the buttons, and can't take a photo, see attached screenshot.
Click to expand...
Click to collapse
Using my method and my values, it is absolutely fine for me. Do you restart after changing the resolution and the dpi?
I am on UK BTU 5.1.1
mitko76 said:
Using my method and my values, it is absolutely fine for me. Do you restart after changing the resolution and the dpi?
I am on UK BTU 5.1.1
Click to expand...
Click to collapse
I even wiped /cache and /dalvik. Strange. My device is a Snapdragon N910F. Is yours an Exynos N910C perhaps? If not, would you mind sending me your camera apk for testing?
Thanks!
Xelasarg said:
I even wiped /cache and /dalvik. Strange. My device is a Snapdragon N910F. Is yours an Exynos N910C perhaps? If not, would you mind sending me your camera apk for testing?
Thanks!
Click to expand...
Click to collapse
very strange indeed. My device is n910f as well. Not rooted and fully stock. I used the Debloater app to disable all unused apps (works via adb) and the method descried in my other post to change the resolution and dpi. The camera is working absolutely fine i.e. no visual changes or glitches. As I am not rooted I am not sure if I can give you the camera apk. It is basically the same apk as in the stock 5.1.1 BTU rom. Try my method on the stock rom with my values and I am sure it will work.
Cool
mitko76 said:
very strange indeed. My device is n910f as well. Not rooted and fully stock. I used the Debloater app to disable all unused apps (works via adb) and the method descried in my other post to change the resolution and dpi. The camera is working absolutely fine i.e. no visual changes or glitches. As I am not rooted I am not sure if I can give you the camera apk. It is basically the same apk as in the stock 5.1.1 BTU rom. Try my method on the stock rom with my values and I am sure it will work.
Click to expand...
Click to collapse
Well, I went ahead and downloaded _alexndr's COI3 stock debloated rom base (Deodexed), extracted SamsungCamera3.apk, replaced the one in my /system/app dir, set permissions, rebooted, and everything's working fine now. :good:
No idea what the Emotroid guys did to the camera app.
I've attached the apk to this post in case anyone else is having this issue.
Man, I've been playing XCOM:EW at 720p, and my phone didn't get warmer than 59°C, even after 2+ hours. And the performance boost is just so incredible... Turns out I don't even mind the 720p resolution in 3D games, it didn't bother me at all.
Just a warning:
I just managed to render my phone useless with this. After changing resolution and DPI, the phone did a soft reboot (as it should), startet booting, then, after the initialisation of systemUI reboots. Has been Bootlooping the past hour. ADB doesn't work, as reboot it's unauthorised and boot loop doesn't allow for any authorisation. Tried resetting via build.prop and userinit.sh. Even Direct Script Injection into init.rc didn't work.
Cache wipe -> no chance
System wipe and reflash -> Nope
In the End i ended up factory resetting and reflashing complete rom. This did work. Not to rant or anything, just a little story for those that are not capable to troubleshoot problems: This might screw your Installation!
domsch1988 said:
Just a warning:
I just managed to render my phone useless with this. After changing resolution and DPI, the phone did a soft reboot (as it should), startet booting, then, after the initialisation of systemUI reboots. Has been Bootlooping the past hour. ADB doesn't work, as reboot it's unauthorised and boot loop doesn't allow for any authorisation. Tried resetting via build.prop and userinit.sh. Even Direct Script Injection into init.rc didn't work.
Cache wipe -> no chance
System wipe and reflash -> Nope
In the End i ended up factory resetting and reflashing complete rom. This did work. Not to rant or anything, just a little story for those that are not capable to troubleshoot problems: This might screw your Installation!
Click to expand...
Click to collapse
Hence the warning at the beginning of the thread.
But seriously: which method did you use? The NOMone app or the adb commands? Because only the adb command needs a reboot to take effect, NOMone does not reboot: it changes the resolution on the fly, then waits 10 seconds for confirmation and switches back to default resolution otherwise.
It's impossible to tell what went wrong in your case, might have been anything from a bad adb command to a malfunction of the app or your rom. I guess if you enter bad values, both methods might break your SystemUI. I managed to do so by using Automate to activate the shell commands on app launch (no bootloop, though, only permanent FC of SystemUI), but I was able to fix it with adb easily.
It's a shame it didn't work for you, most people who are using this method are very happy with it.
THANKS !
dooes this improve battery as well /
gonna try this
Boody hegan said:
THANKS !
dooes this improve battery as well
Click to expand...
Click to collapse
Yes, it does, at least a bit. The screen does still burn a lot of juice because it's so big and bright, but the cpu stays much cooler. Less heat=less power consumption.
Thanks alot , i'm on simplrom v5c and googy max kernel v2
can this still work ..
Xelasarg said:
Hence the warning at the beginning of the thread.
But seriously: which method did you use? The NOMone app or the adb commands? Because only the adb command needs a reboot to take effect, NOMone does not reboot: it changes the resolution on the fly, then waits 10 seconds for confirmation and switches back to default resolution otherwise.
It's impossible to tell what went wrong in your case, might have been anything from a bad adb command to a malfunction of the app or your rom. I guess if you enter bad values, both methods might break your SystemUI. I managed to do so by using Automate to activate the shell commands on app launch (no bootloop, though, only permanent FC of SystemUI), but I was able to fix it with adb easily.
It's a shame it didn't work for you, most people who are using this method are very happy with it.
Click to expand...
Click to collapse
It was completely my fault. I knew what i was getting into, so no problem. It's just that, the "mistakes" i did could easily be done by accident by some less experienced users.
First off, i'm on CM12. NOMones Sollution doesn't seem to work there. CM does a "Hot Reboot" to reload the system UI. No matter what you set in NOMones app, the resolution doesn't change. DPI does though. This seems to be a CM related issue. Maybe they hardcode the resolution at build time...
After that i tried another app, which had the Orientation labeled backwards. So it set 1920x1080 landscape instead of portrait. After that the Phone Bootlooped the System UI. It would always boot up to the PIN Enter Screen and then reboot.
As said, no big Problem. I knew what to do and was able to bring my phone back to working state. Just make sure that you are 100% sure about the numbers you put into such apps and keep in mind that even with such "small" changes you should always have a up to date Backup of everything.
Boody hegan said:
Thanks alot , i'm on simplrom v5c and googy max kernel v2
can this still work ..
Click to expand...
Click to collapse
It should, unless SimplROM is CM12-based. NOMone Resolution Changer, as well as similar apps and the adb method, aren't limited to specific devices. In theory, they may all work on all Android phones. You'll have to try it out yourself, just make a backup before you do so!
domsch1988 said:
It was completely my fault. I knew what i was getting into, so no problem. It's just that, the "mistakes" i did could easily be done by accident by some less experienced users.
First off, i'm on CM12. NOMones Sollution doesn't seem to work there. CM does a "Hot Reboot" to reload the system UI. No matter what you set in NOMones app, the resolution doesn't change. DPI does though. This seems to be a CM related issue. Maybe they hardcode the resolution at build time...
After that i tried another app, which had the Orientation labeled backwards. So it set 1920x1080 landscape instead of portrait. After that the Phone Bootlooped the System UI. It would always boot up to the PIN Enter Screen and then reboot.
As said, no big Problem. I knew what to do and was able to bring my phone back to working state. Just make sure that you are 100% sure about the numbers you put into such apps and keep in mind that even with such "small" changes you should always have a up to date Backup of everything.
Click to expand...
Click to collapse
Right, thanks for clarification. I don't remember the hot reboot in CM12, but I know the resolution switch didn't work when I tried it on my Note 2 some time ago. Funny that for once Touchwiz is more customizable than CM.
If you're still interested, but hate the Samsung colour scheme (like me), you can try out Emotion Revolution ROM r10.1. It's based on the latest COI3 TW firmware, but they themed the notifcation/status bar and toggles to somewhat more like stock Android, see attached screenshot. Looks pretty sleek, performance is easily on par with CM12, and the Emotion kernel has tons of great tweaking options. Or you can go for their Port Note 5 r2.1 ROM, also based on COI3, which should offer full Theme Store support. That's the one I'll flash next. :good:
Xelasarg said:
Right, thanks for clarification. I don't remember the hot reboot in CM12, but I know the resolution switch didn't work when I tried it on my Note 2 some time ago. Funny that for once Touchwiz is more customizable than CM.
If you're still interested, but hate the Samsung colour scheme (like me), you can try out Emotion Revolution ROM r10.1. It's based on the latest COI3 TW firmware, but they themed the notifcation/status bar and toggles to somewhat more like stock Android, see attached screenshot. Looks pretty sleek, performance is easily on par with CM12, and the Emotion kernel has tons of great tweaking options. Or you can go for their Port Note 5 r2.1 ROM, also based on COI3, which should offer full Theme Store support. That's the one I'll flash next. :good:
Click to expand...
Click to collapse
Nah, TW is no option... I choose CM because of the straight forward no bllsht Apps approach. Plus Nightly builds via OTA... In no possible way am i going back to TW
AnTuTu Benchmark @ 1080p, performance governor, stock cpu frequency (2.65 GHz): :highfive:
(OK, cpu was also very cool when benchmark started, 28°C).