Just got the G5 to move back from iPhone to android. Hate iPhone! But it's silly that my iPhone 6S can fit more content on the screen and it is a highly inferior screen than the G5...
Is there any easy way to change DPI without being root? What's the recommended DPI for this screen without breaking apps like camera?
Ideally would like to root and install app settings & xposed but not sure if my model can be rooted yet. It's the international model bought from EE in the UK.
How do I check for locked bootloader?
Rockin my G5
Hello, I know i'm late but I just got my G5 today and was looking for information much like you were but didn't find any so i experimented. to note, i do have the t-mobile variant so obviously if you have a different version of the phone your results could be different. I haven't tried any DPI's lower than 560 but that being said 560 seems to be perfectly stable and was easily changed through adb! and WOW does it make a difference on this device! for me at least, 560 seems to be the sweet spot! Really, i don't understand why OEM's don't set their DPI's to reasonable settings in the first place.. i mean, we have quad-hd displays for androids sake, LET US USE THEM.. anyways, rant aside:
You'll want to install ADB and the LG drivers obviously but once that's setup go to your phone, enable developer options and enable USB debugging and OEM unlock (the latter may not be necessary but my device wasn't being recognized initially so i enabled it. Also, for some reason i'm finding with this phone that it doesn't want to be recognized in MTP (file transfer) mode but seems to work fine in "camera mode".
first, type "adb devices" to make sure that the device is being recognized.
once your device is being recognized by adb (it may say unauthorized, ignore this) simply type the following command.
"adb shell wm density 560 && adb reboot"
or you can obviously change out the number to whatever DPI you want, but the lower you go the higher the chance that things like the camera will stop working properly. So far i have not had any issues at all with any system apps, the camera seems to have scaled perfectly as it should and this is generally the app that breaks for me. if i find any apps or anything not working i'll update my post here, but so far so good!
I hope this helps you out! If you have any further questions let me know!!
(little update, first and ONLY thing i've had issues with is the "always on display" doesn't seem to show time correctly.. oh well!! its a very fair trade and since the always on display can be shut off in settings its not even an eyesore. )
Hey bud,
Tried setting it to 560 using this method, think its probably a tiny bit too small, would probably prefer maybe in the middle between 640 (stock) and 560. I noticed that on 560 swiftkey didnt work properly (cant live without swiftkey!!) and as you said, the always on display showing time - signature works fine though.
Have reverted it for now, maybe yourself or someone will find a perfect number which gives minimal issues with apps. Otherwise, might just wait on root to edit the build.prop instead.
mcall_r said:
Hey bud,
Tried setting it to 560 using this method, think its probably a tiny bit too small, would probably prefer maybe in the middle between 640 (stock) and 560. I noticed that on 560 swiftkey didnt work properly (cant live without swiftkey!!) and as you said, the always on display showing time - signature works fine though.
Have reverted it for now, maybe yourself or someone will find a perfect number which gives minimal issues with apps. Otherwise, might just wait on root to edit the build.prop instead.
Click to expand...
Click to collapse
so try a different DPI? just replace 560 in the command with whatever you want to and see how it looks. only takes a couple minutes to do. also, if you like swiftkey.. you should really try Swype. much better keyboard and it scales perfectly with and dpi i've ever tried on any phone.
Anyone seen the drivers for the LG G5 or or alternative that will work?
anothervictim. said:
Anyone seen the drivers for the LG G5 or or alternative that will work?
Click to expand...
Click to collapse
ya know, i owned the lg v10 before this phone and never updated my drivers. works just fine. does lg not have drivers posted for the g5??
ngoblirsch said:
ya know, i owned the lg v10 before this phone and never updated my drivers. works just fine. does lg not have drivers posted for the g5??
Click to expand...
Click to collapse
I didn't see it listed. I'll check out the v10. I imagine it's the same. Thanks!
ngoblirsch said:
ya know, i owned the lg v10 before this phone and never updated my drivers. works just fine. does lg not have drivers posted for the g5??
Click to expand...
Click to collapse
You need to search for the LG H850 on LG's website. H850 is the actual model number. But as other comments suggest, the drivers for the V10 will probably work fine.
Any working dpi's without bootloops? I don't use always on Display
Sent from my LG-H850 using XDA Labs
I've got my dpi set to 540, anything lower causes stability issues.
Ixstala said:
I've got my dpi set to 540, anything lower causes stability issues.
Click to expand...
Click to collapse
Thanks, 540 is working very well. I like it
Sent from my LG-H850 using XDA Labs
Lycidias said:
Thanks, 540 is working very well. I like it.
Click to expand...
Click to collapse
Are there any issues with any of the apps at 540 DPI? Any chance you could post a picture of the settings screen or something with the DPI at 540?
xPhantom said:
Are there any issues with any of the apps at 540 DPI? Any chance you could post a picture of the settings screen or something with the DPI at 540?
Click to expand...
Click to collapse
No issues, everything is working fine
Sent from my LG-H850 using XDA Labs
Lycidias said:
No issues, everything is working fine
Click to expand...
Click to collapse
Thank you! That looks awesome. I'm going to do this now.
Edit: SwiftKey does not seem to like the new DPI... keyboard is all messed up looking, haha.
I'm using 600 on mine, everything seems fine.
Is this a code that can be used on any phone? Could I use this on my Xperia Z5?????
I'm using 560 as someone suggested, and LastPass doesnt scale properly and PlaySTore, the blue top dev icon is too large, otherwise no problems at all.
I tried this with 540. Here's the list of things that weren't working right:
Uber | sprites like cars and pins were tiiiiiiiiiiny or squished. Still useable but not pretty.
Anything that required photo cropping or editing (Instagram, Bumble, etc) the photos were multiples larger than they should be | For instance, in instagram, you'd share a photo to it and it'd show up in the initial cropping window as huuuuuge and unscalable, but if you hit next it'd be normal size. So you just had to use guesswork to position the photo.
Swiftkey keyboard | As reported, also displayed HUGE, even though it responded to key presses in the right places.
Starbucks | Also seeing the "dots" on the map that show locations as super tiny. Not a big deal here.
In general, it seems anything that overlays graphical elements or that brings up photos for editing is at risk. I miss how this worked on my G4, but I guess that's because I did it via root. Can't wait.
Reseted the dpi but the always on Screen and the home button are still broken.
Weird thing. I used "wm density x" too, and, well... anything different than 640 (default), and android.process.phone keeps crashing....
fonix232 said:
Weird thing. I used "wm density x" too, and, well... anything different than 640 (default), and android.process.phone keeps crashing....
Click to expand...
Click to collapse
I'm sorry to those of you having problems.. Not sure what to tell you though, I changed my dpi to 560 the day I got my phone and the one and only issue I've had so far is my always on display not working right. Every other app has worked flawlessly. For those having problems, what variant of the phone do you own? H830 here
Related
In trying to optimize my CM7, RC4 setup, I realized that changing the LCD density from 161 to 160 allowed a game that I never got to work before to run perfectly...The game is "fruit slice"...Now I wonder how important this may be with multitudes of games and apks? Anyone else notice this on other apps?? If you've figured one out, or a complete workaround that cures this scaling issue, please offer any insights you might have.I'd rather not have to make folders of certain apps that only work at so-and-so density..but..
Delivered by a little dude that lives behind your screen.
What are you using to change your Density. I'm new to my Rooted Nook Color and trying to learn all I can about it
Sent from my Android.
mazook98 said:
In trying to optimize my CM7, RC4 setup, I realized that changing the LCD density from 161 to 160 allowed a game that I never got to work before to run perfectly...The game is "fruit slice"...Now I wonder how important this may be with multitudes of games and apks? Anyone else notice this on other apps?? If you've figured one out, or a complete workaround that cures this scaling issue, please offer any insights you might have.I'd rather not have to make folders of certain apps that only work at so-and-so density..but..
Delivered by a little dude that lives behind your screen.
Click to expand...
Click to collapse
I've heard that a density of 160 prevents Maps from working. Does yours?
lyam23 said:
I've heard that a density of 160 prevents Maps from working. Does yours?
Click to expand...
Click to collapse
Haven't checked yet..
Will do...ps…for ^that other? ...density can be changed thru either nook utils app found here on forum...thru apk from beansoft, thru root explorer (change build.prop under/system, or with adb..)
Sent from my PC36100
I've been using 140 pretty much exclusively. I don't like the Fisher Price look of the big huge icons you get with 200 that so many here are fond of.
I set mine at 210. The only app that doesn't scale correctly is Google Reader.
Bossbollin said:
What are you using to change your Density. I'm new to my Rooted Nook Color and trying to learn all I can about it
Sent from my Android.
Click to expand...
Click to collapse
I would like to know this also.
lyam23 said:
I've heard that a density of 160 prevents Maps from working. Does yours?
Click to expand...
Click to collapse
Maps working okay for me at a 160LCD density.
*oops* - i was wrong. market and maps crash at 160..
hoodwinked said:
Maps working okay for me at a 160LCD density.
Click to expand...
Click to collapse
Good to know, thanks.
After changing to 160 i get a black screen on boot but i fixed it. Does this work on honeycomb?
For those asking how to change it, there is an app in the market (although I've never used it), or you can use Root Explorer to edit the build.prop file in your system folder. Just scroll down until you see something about LCD Density (sorry, don't have my Nook in front of me) with a 161 after it, change that number to one of the numbers listed in this thread. I use 140, some use much higher numbers. You'll have to reboot for the change to take effect.
philburkhardt said:
I set mine at 210. The only app that doesn't scale correctly is Google Reader.
Click to expand...
Click to collapse
210...first one I tried was that fruit slice again, and no go....sigh...
Sent from my PC36100
mazook98 said:
210...first one I tried was that fruit slice again, and no go....sigh...
Sent from my PC36100
Click to expand...
Click to collapse
Funny how that is. I just tried Fruit Slice at 210, 161 & 160. 160 was the only one that worked.
I would suggest Fruit Ninja for 210, but it's a paid app. I bought it a long time ago, and it works great at 210. It was the free app of the day on on the Amazon Appstore the other day, and I have seen the free apps repeat.
...or you could just go with 160.
I have fruit ninja too...I was just wondering if there was some magic cure-all for all apps when used on the nook, or was the reason perhaps just lazy coding by certain app devs.
Sent from my PC36100
LCDensity from the Market works great. And it's free!
Ill have to check it out
honeycombgoodyeahyeahyeah said:
After changing to 160 i get a black screen on boot but i fixed it. Does this work on honeycomb?
Click to expand...
Click to collapse
(didn't realize people were still using hc)...can you use bluetooth/gpstether/fullgraphics yet on hc? I digress...If memory serves...HC MUST be set at 161 or higher....Since Android developed it for tablets, this req. was probably added to keep it off of phones....
Sent from my PC36100
mazook98 said:
(didn't realize people were still using hc)...can you use bluetooth/gpstether/fullgraphics yet on hc? I digress...If memory serves...HC MUST be set at 161 or higher....Since Android developed it for tablets, this req. was probably added to keep it off of phones....
Click to expand...
Click to collapse
I dual boot HC and Froyo but i only use Froyo for N64oid. Bluetooth doesnt work, im not sure about gps tether as ive never used it (dont have an android phone to pair it with) but i found this video of someone who got it working: http://www.youtube.com/watch?v=oS0WsNNuvNA
What do you mean by full graphics?
My HC version is actually set to 140 by default.
honeycombgoodyeahyeahyeah said:
I dual boot HC and Froyo but i only use Froyo for N64oid. Bluetooth doesnt work, im not sure about gps tether as ive never used it (dont have an android phone to pair it with) but i found this video of someone who got it working: http://www.youtube.com/watch?v=oS0WsNNuvNA
What do you mean by full graphics?
My HC version is actually set to 140 by default.
Click to expand...
Click to collapse
Sorry. I meant fully working video hardware decoding...does Froyo run things like youtube in HD at full framerate...does 10.2 work well with all the streaming apks like in CM7?..I've never used froyo on the nook, since gb does everything I ask it too..HC was way too flaky and buggy without MAJOR tweaking.
Sent from my PC36100
Ahh i dont know about that. I only use Froyo for N64oid and im never really watch youtube videos so youd have to ask someone else about that. I didnt know they had gb for Nook...ill have to check that out. HC from here works fine:
http://forum.xda-developers.com/showthread.php?t=947071
Hi everyone.
I am using the SalsaSense ROM. I am unable to post in that thread because I am new here, so I'm hoping someone here will be able to help me.
In the stock SMS app there is the option to delete old messages once a limit has been reached. I installed the ROM, recovered my messages, and enabled the option in the stock app with the limit set at 200. But my old messages are not being deleted. With one contact I have 7k+ messages, and since enabling the option I have sent and received several messages with them. When I had Elelinux-7.1.0-Hero-v2.6 installed beforehand, following these steps was enough to provoke it to keep my inbox in check. But not now.
Is this a problem with the ROM, or the stock app, or am I just unlucky?
I'm hoping someone here may have come across this and can help me out.
Many thanks, BurnseyBoi
I think you've been unlucky. It sounds like a ROM problem since it's beta.
You could delete them using an app like SuperSMS Delete (I think it's that).
Yeah, guess I'll just have to wait for an update to it. I had a look round the market and found the app you were referring to. Worked a charm, thanks very much! Now my phone is a bit speedier.
Yeah i noticed this, unfortunately its a problem with the ROM. I've got a lot of issues to iron out so it takes me a while to solve each one, rest assured though it will be fixed
Sent from my Hero using XDA Premium App
Awesome, glad to hear it
I love this ROM! I forgot how much I missed the little Sense features and looks. My friend just got himself a Sensation, which is where I got the idea to browse around for a Sense ROM. Many thanks!
JieeHD said:
Yeah i noticed this, unfortunately its a problem with the ROM. I've got a lot of issues to iron out so it takes me a while to solve each one, rest assured though it will be fixed
Click to expand...
Click to collapse
I'm trying to follow the build.prop editing suggestion, but adb doesn't list my phone under connected devices. I've tried while the phone is on, and in recovery.
Is there another way of successfully editing it?
Yeah, you can use Root Explorer from the Market. ES File explorer may work too, look in the app's settings for Root options.
Navigate to the directory with the build.prop and long press and I think there's an edit option if you use Root Explorer. Then you can just edit as you would normally via the phone.
Thanks! I already had ES File Explorer, didn't realise it had root options though.
Made both changes that JieeHD suggested, then powered it off and back on. I've never seen my phone go from power button to lock screen that fast in the 2 years I've had it! I definitely notice a speed improvement from making those changes. Everything just feels sharper and more responsive.
Many thanks!
BurnseyBoi said:
Thanks! I already had ES File Explorer, didn't realise it had root options though.
Made both changes that JieeHD suggested, then powered it off and back on. I've never seen my phone go from power button to lock screen that fast in the 2 years I've had it! I definitely notice a speed improvement from making those changes. Everything just feels sharper and more responsive.
Many thanks!
Click to expand...
Click to collapse
I've tried them and can confirm they do speed things up.
Wish there was some option to use a standard notification bar, I think it would help.
hero_pt said:
I've tried them and can confirm they do speed things up.
Wish there was some option to use a standard notification bar, I think it would help.
Click to expand...
Click to collapse
I agree. I tried following the instructions in this thread but I couldn't get it to work. Has anyone else using this ROM been able to successfully do this?
Has anyone successfully adjusted the DPI on the galaxy S4? Curious how to do it safely and what DPI setting works best.
yes! i was wondering the same thing. i figured i'd wait until ROMs come out before i raised the question though since some cooks will bake this into their ROMs.
yyhd said:
yes! i was wondering the same thing. i figured i'd wait until ROMs come out before i raised the question though since some cooks will bake this into their ROMs.
Click to expand...
Click to collapse
answer - get root, build.prop editor, do 320. 240 is too low.
bryho said:
Has anyone successfully adjusted the DPI on the galaxy S4? Curious how to do it safely and what DPI setting works best.
Click to expand...
Click to collapse
What benefit is there to this ????
mexiken said:
What benefit is there to this ????
Click to expand...
Click to collapse
you can see *far* more on the screen than normal. Great for a big high res screen like this
bryho said:
answer - get root, build.prop editor, do 320. 240 is too low.
Click to expand...
Click to collapse
Word. Thanks. I'm rooted. Will edit build.prop now.
yyhd said:
Word. Thanks. I'm rooted. Will edit build.prop now.
Click to expand...
Click to collapse
I'm still running touchwiz but am using nova launcher. I adjusted my DPI but all the touchwiz elements, like phone and calculator, are kinda wacked up, any way to fix that?
Oh, and chrome is a little off too, like the tab button.
Word of advice - NO MATTER what I did, changing the DPI on my S4 (and possibly all phones) always causes issues. I have spent the past week experimenting with trying to make it work right. If you change the overall phone DPI in the build.prop (I have tried 320, 420, 440, 460), you WILL trigger the Market issues with certain apps no longer showing up for you in a search- unless you type the name in the search but then select the actual item from the predictive box below (instead of actually searching). But, even after you are brought to the page, at the top you will still get the 'incompatible with your device' message and cannot download or update on the phone. Trying to do it on a desktop PC in the Store also does not work. So far, this happened to me with YouTube, Google Keyboard, and a few other Google or common apps.
I tried several methods of modding the market or different apps that have supposed options for spoofing what DPI the Play Store sees, but in the end, the issue always came back, every time eventually (may take a reboot or two). Clearing data on Google Framework and Play Store and clearing cache/Dalvik cache never is a permanent fix, it will always recognize it eventually.
Oh and also, there were always a few apps that would become wonky looking or cut off, like the stock Samsung camera and gallery apps, among others.
In the end, the only thing that worked is to leave the overall DPI alone, and just adjusting the DPI of certain apps individually using something like Hyperdrive Control in the Hyperdrive ROM or equivalent app (I ended up just changing the DPI of Nova Launcher and nothing else- at least the launcher/icons then can become smaller resolution).
If there IS a method that works and does not cause this issue in the Store eventually, please let me know! I tried em all!
To the above poster:
First off - calm down. Everything will be alright
Here's how to change the DPI without issue.
1. Edit build.prop to desired value. Do not reboot. (I like 400)
2. Download a multi DPI play store. (Google for an xda link. I use inverted multidpi)
3. Reboot to recovery and flash multidpi play store. Reboot.
2. Use any launcher except TouchwizHome
3. Install the xposed framework and per app DPI module.
4. Set all the Samsung apps to the stock 480 dpi
Easy.
Sent from my SCH-I545 using Tapatalk 4 Beta
Hey. There's a much easier way of you want to adjust specific apps
1) Download/install the Xposed framework
2) Download/install App Settings
From there, you can pick from the list of apps and change dpi to whatever you want. On the phone now so I don't have links but do a quick search. The App Settings for the AT&T S4 works for ours.
Sent from my SCH-I545 using xda premium
Metallice said:
To the above poster:
First off - calm down. Everything will be alright
Here's how to change the DPI without issue.
1. Edit build.prop to desired value. Do not reboot. (I like 400)
2. Download a multi DPI play store. (Google for an xda link. I use inverted multidpi)
3. Reboot to recovery and flash multidpi play store. Reboot.
2. Use any launcher except TouchwizHome
3. Install the xposed framework and per app DPI module.
4. Set all the Samsung apps to the stock 480 dpi
Easy.
Sent from my SCH-I545 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Lol I'm calm don't worry. Just explaining it all to people that don't know any better.
just4747 said:
Lol I'm calm don't worry. Just explaining it all to people that don't know any better.
Click to expand...
Click to collapse
How do they not know any better? About what? That phrase doesn't make any sense in this context.
Sent from my SCH-I545 using Tapatalk 4 Beta
Metallice said:
How do they not know any better? About what?
Sent from my SCH-I545 using Tapatalk 4 Beta
Click to expand...
Click to collapse
To people who do not know that changing DPI affects some Play Store apps like this.
And your method may work, but it's tedious to have to change every Samsung app's individual DPI afterward, and also you won't always get the latest Play Store update until the newest version is again manually modded for multi-DPI. But yes, doable.
just4747 said:
To people who do not know that changing DPI affects some Play Store apps like this.
And your method may work, but it's tedious to have to change every Samsung app's individual DPI afterward, and also you won't always get the latest Play Store update until the newest version is again manually modded for multi-DPI. But yes, doable.
Click to expand...
Click to collapse
Oh. I see what you meant. Just say "for those unaware" lol. The phrase "don't know any better" doesn't apply as you are referring to knowlege rather than behavior
And there's no "may" about it. It does work. It worked on my galaxy nexus, and it works on my S4.
And I've never had a problem getting the newest play store update. The thread I get them from is pretty on top of it.
Unfortunately manually setting the DPI for Samsung apps is the only way unless you want to hack apart the apk and deal with overall buggyness. Samsung is lazy and only cares to make the app work for one device... Unlike play store apps.
I really don't think the initial two minutes of my time to fix the 4 or 5 samsung apps that have issues is that big of a deal.
Sent from my SCH-I545 using Tapatalk 4 Beta
kcellb said:
Hey. There's a much easier way of you want to adjust specific apps
1) Download/install the Xposed framework
2) Download/install App Settings
From there, you can pick from the list of apps and change dpi to whatever you want. On the phone now so I don't have links but do a quick search. The App Settings for the AT&T S4 works for ours.
Sent from my SCH-I545 using xda premium
Click to expand...
Click to collapse
Hate to throw the newb card but how do I do that lol? How do install xposed and the app settings? Thanks!!
milzinga said:
Hate to throw the newb card but how do I do that lol? How do install xposed and the app settings? Thanks!!
Click to expand...
Click to collapse
Check out this thread
http://forum.xda-developers.com/showthread.php?t=2291826
DPI Fix Tool 1.4.1 will fix it
I use DPI Fix Tool v1.4.1 on my AT&T Galaxy S4 and it works perfectly. I've used this tool before on my Sensation 4G. It modifies the Buildprop and the play store so you can still access everything on the market. Link is provided: http://forum.xda-developers.com/showthread.php?p=37326035
Enjoy :fingers-crossed:
ponp74 said:
I use DPI Fix Tool v1.4.1 on my AT&T Galaxy S4 and it works perfectly. I've used this tool before on my Sensation 4G. It modifies the Buildprop and the play store so you can still access everything on the market. Link is provided: http://forum.xda-developers.com/showthread.php?p=37326035
Enjoy :fingers-crossed:
Click to expand...
Click to collapse
I used the tool too, but play store wont start.
What dpi setting you use for play store ? I tried 480 and 320.
Not sure if you have fixed this issue yet, but newer ROMs for the T-Mobile and AT&T S4 variants us ethe Exposed Framework. From there you can use a module called Play Store Fixes (follow directions). Manually change the DPI setting in the build.prop and reboot. Mine is set to 320 and I can see everything in the playstore.
Current ROM: Danvdh-GE-4.4.2-01232014b
AT&T S4 unlocked on T-Mobile's LTE network
Galaxy S4 4.4.2 stock phone DPI change
Hi everyone,
I have the Omega ROM v20 (4.4.2) installed on my galaxy s4 i9500. It came with the Xposed installer 2.5.1 and the App Settings 1.8. I have already installed the framework in the Xposed installer and selected the app settings under the modules and rebooted the device.
I have changed the phone's DPI to 320 form the original 480 by manually updating the build.prop file in /system. A few Samsung apps, including the touch wiz, the calculator and some others started acting up and pieces where out of place. I managed to fix all of that by migrating to the Apex launcher and also the extensive use of the DPI changing feature of the App Settings application.
The DPI changing utility seems to be working on every application, including the Google play app store, but not for the phone app. Even though the App Settings says that the 480 DPI has been applied to the phone application the dialer and its pieces once launched are still out of place. The phone application on the ROM is the stock samsung 4.4.2 i9500 phone app and I have tried it every which way but still no go!
I was wondering if another application's DPI also needs to be changed for it to work or maybe I have ran into an App Settings bug of some kind!
Any help would be most appreciated
Many thanks
Anyone else noticed in the developer options, the setting to change the DPI (minimum width) is just not there? Never run into an Android phone on Nougat missing this setting before. Anyone know if there's a way to adjust it or get it back?
It was missing on the G6 too. Bastards, lol.
Moostafa29 said:
It was missing on the G6 too. Bastards, lol.
Click to expand...
Click to collapse
Is there any kind of workaround? The default sizing of everything is just too big.
My G6 is my backup phone, so I haven't tried anything to remedy this. I did read that there is a way to do it through ABD commands, but I haven't tried it myself. We used to have root for US LG phones, and changing the dpi was one of the first things I'd do. Changing the dpi would break several of the LG apps, so perhaps they removed the option in order to avoid that.
I remember trying to use ADB commands when I had the AT&T LG G6, and it didn't work. I assume that the V30 won't work either, so I haven't even tried. If you want to try, Google how to change dpi with ADB command, then let us know if it works or not. :good:
Anyone get this to work on their Pixel 4a? I saw this thread, went to check it out on the play store. Installed it, tried to activate it but the app said my device isn't supported. Strange because it says right in the app description "supports Google Pixel4a"
Which exact one did you download...
It works perfectly fine for me
Yep works great for me
It didn't work for me either. At first, I thought it might have something to do with having changed the device fingerprint via MagiskHide Props Config to a Pixel 3a in order to pass SafetyNet. I set it back to a 4a and rebooted but it still didn't work. Perhaps there is something else that's interfering
banjker said:
It didn't work for me either. At first, I thought it might have something to do with having changed the device fingerprint via MagiskHide Props Config to a Pixel 3a in order to pass SafetyNet. I set it back to a 4a and rebooted but it still didn't work. Perhaps there is something else that's interfering
Click to expand...
Click to collapse
Again...
I will ask... Which EXACT one did you download... As there are a few different versions of the app for different devices
rignfool said:
Again...
I will ask... Which EXACT one did you download... As there are a few different versions of the app for different devices
Click to expand...
Click to collapse
I did see there were different versions. I tried the Energy Ring - General Edition! version from the Play Store,
usafle said:
Anyone get this to work on their Pixel 4a? I saw this thread, went to check it out on the play store. Installed it, tried to activate it but the app said my device isn't supported. Strange because it says right in the app description "supports Google Pixel4a"
Click to expand...
Click to collapse
you have to allow energy ring to get a inerne connection
without it won´t work at the first start
after the first start id dont need internet
Works for me, just using the Universal Edition out of the play store.
After a bit of searching I got rid of the battery percentage from the Settings and the normal battery icon by using the Activity Launcher app. So much cooler with just the ring.
The ring idea would have been great if Google had cooked it directly into Android, it's a lot cooler and turns the punch hole screen lens into more of a feature.
Anyone else with an issue on Android 12? It seems to render the top of the screen non-responsive in apps/home screen. Only place it doesn't seem to have this effect, is in Settings.
goofball2k said:
Anyone else with an issue on Android 12? It seems to render the top of the screen non-responsive in apps/home screen. Only place it doesn't seem to have this effect, is in Settings.
Click to expand...
Click to collapse
Yes, I experienced this issue on my Pixel 4a after the A12 install. Very odd. Had to uninstall Energy Ring to resolve it.
It works flawlessly for me even after all a12 updates to present.
I use Energy Ring - Universal Edition on my Pixel 4a running Stock Pixel A12 and it works perfectly