Related
The Instructions:
Short, sweet, and straight to the point: So, here's what you do... you will want to download the app called Screen Filter with the market link provided below. After you do that, within the Screen Filter app you will want to drag that brightness bar to say 85.1% and then hit enable. This won't lower your current screen brightness very much so no worries there. You should hopefully notice a difference for the better all around, especially viewing from an odd angle. It helps to reduce that white backlight look you get from a side view. I will typically set the in app brightness to either 85.1%, 75.5%, or 72.5%, and my actual system brightness to 50%. It works quite well without being too bright or too dark. And it goes without draining much, if any battery life. Feel free to try other brightness settings to fit your personal needs.
Try it on other Android devices as well, it works great! The best way to test it out is to use the widget. You can turn it off and on while changing your viewing angle to compare and see the difference for yourself on your homescreens. Forget about a complicated method and get yourself a better screen today with Screen Filter!
Screen Filter Can Be Found Here:
https://market.android.com/details?id=com.haxor&feature=search_result
Showing Off Side Angle View:
You will be able to notice that in the after screenshot the green bar across the top of the market app is quite a bit more vibrant and has more of a green color than the before screenshot. And you will also notice that the white back light color will be enhanced as well, giving a better appearance from the side viewing angles. A nifty little quick fix, if you will.
Before:
After:
Screen Filter Known Issues Reported By Users:
*Being completely stock and using the stock system apps seems to be causing some major lag issues (Xoom)
*Cannot seem to click install when you are manually installing an apk without disabling (Xoom)
*Cannot compose emails without disabling (Nexus S)
You can add to this list. If you find anymore issues please post them here and I will add them to my list above. After we gather most/all issues that we are having I will let the dev know what we have found and we can make some positive results for all! Maybe we can even have some new features added in a new release. Once the Honeycomb source gets released and we start getting custom ROMs, expect user interface tweaks such as what you find in Cyanogenmod. Until then, use this. It's the easiest and best tool we have for now.
Note For Screen Filter:
This method may only be effective on the 3G version of the Xoom. It appears that it may not be noticeable as much, if at all on the Wifi model.
Make That High Def Screen Even Higher:
For this you will need to be a root user, and always be sure to have a current Nandroid backup handy just in case.
You will want to download the free app called LCD Resolution (Root). You can find it on the market here. Open the app, and then you will see your current density setting as well a list of density options for you to choose from. The default density value for the Xoom is 160. I do not recommend that you go below 140, as certain screen elements may become misaligned. Just dropping the value down by 10 to 150 makes a nice noticeable difference.
Basically: The default density value for the Xoom is 160. I recommend using either 150, or 140 as your density value and nothing less. I think 150 seems to be right where most people would want their screen to be if they wanted to go just a bit higher def. It makes the resolution a little nicer without going too overboard. After you choose your density setting, don't forget to check the "Always Set on Boot" box. This makes it so much easier so that you will not have to worry about setting this up with every single time you boot. Then hit apply, reboot your Xoom, and then make sure that the settings stick. Done!
Apply one of the density settings I have listed with one of the Screen Filter settings also listed for a nice effect. It's almost as if you have a whole new tablet when you combine the two!
Currently: I am using the 140 density value on my Xoom, and I couldn't be happier!
Default Density Value 160:
Density Value 150:
Density Value 140:
If these tips have helped you out toss me a thanks. If I get more positive feedback I will be adding some more great helpful tips for us Xoomers. Thanks for stopping by!
Thank you for a great tip. My Xoom screen look better now. This is why I love to visit XDA everyday.
Will check with Acer A500.
im not really seeing a difference.
patass said:
im not really seeing a difference.
Click to expand...
Click to collapse
The difference is there. Try viewing from different angles instead of straight on and compare. I added my own screenshots of my Xoom just now and you should be able to see a nice difference from the before and after. This method really helps the side viewing angles a lot by reducing the white backlight that causes the screen to distort when not looking directly down on it. But it looks really great all around, not just from the side.
so what do i put the system brightness at? and what do I put the screen filter percentage at?
incrediblenotinstock said:
so what do i put the system brightness at? and what do I put the screen filter percentage at?
Click to expand...
Click to collapse
You can customize and set it to whatever you like. Me, for normal usage I like to use 50% for the system brightness and 85.1% for the Screen Filter brightness. I think it works quite well this way without being too dark or too bright. I use this setting on both my Xoom and my OG Droid.
I see what your saying, the viewing angle is alot better now, thanks OP
wow, makes a huge difference for me, thanks
How does it impact battery usage at the 50/85?
Brolloks said:
wow, makes a huge difference for me, thanks
How does it impact battery usage at the 50/85?
Click to expand...
Click to collapse
It really does not impact the battery life very much if at all. In fact it possibly might save a little bit of battery life if anything. I've been using this setup for months and it has been working great.
my home screen n browser seems laggy when using it. Anyone has the same issue with me?
omnia1994 said:
my home screen n browser seems laggy when using it. Anyone has the same issue with me?
Click to expand...
Click to collapse
Yep...real laggy. Uninstalled
omnia1994 said:
my home screen n browser seems laggy when using it. Anyone has the same issue with me?
Click to expand...
Click to collapse
Hmm.. interesting. I use it all the time without any kind of problem. What launcher and browser are you using? And are you stock or rooted?
I'm using both Adw Launcher and Launcher Pro depending on my mood and they both work great with Screen Filter enabled.. no lag of any kind. And my browser of choice is always Dolphin HD and it also works without any lag. I'm on a rooted 3.1 Xoom with the latest tiamat kernel. Maybe I can help solve the problem?
i am curious why one would jack their screen brightness up to 85% in the first place, 33% gets a perfectly view able screen indoors. Not to mention the savings wrt battery life.
Kokanee483 said:
i am curious why one would jack their screen brightness up to 85% in the first place, 33% gets a perfectly view able screen indoors. Not to mention the savings wrt battery life.
Click to expand...
Click to collapse
The 85% is for filter not brightness.
Sent from my PC36100 using XDA App
omnia1994 said:
my home screen n browser seems laggy when using it. Anyone has the same issue with me?
Click to expand...
Click to collapse
Yep, nice for off angles but for sure adds all types of lag. Bonse stock 3.1 no root. Factory launcher... isn't their a color control like what's available for the Nexus S? You would think with the screen wash out complaints someone would have come up with an answer by now.
Just tested another app. Really liked the effect on off angles so I'm searching the market for other stuff. There is another app called back light filter. It alowsyou to adjust the Alpha levels along with individual colors. Have to tinker to find the best fit but no home screen lag.
lstrike said:
Just tested another app. Really liked the effect on off angles so I'm searching the market for other stuff. There is another app called back light filter. It alowsyou to adjust the Alpha levels along with individual colors. Have to tinker to find the best fit but no home screen lag.
Click to expand...
Click to collapse
I've tested this app before and it's so so. Most users will want something easy to use without much tinkering or setup. It works pretty well through, but it could use some more features, it lacks a widget, and there is no notification bar icon for fast access. Good comment though. Maybe the people who are completly stock everything should give this a go since they are reporting lag issues.
I don't see any difference.
Sent from my Xoom using XDA Premium App
diablo2224 said:
I've tested this app before and it's so so. Most users will want something easy to use without much tinkering or setup. It works pretty well through, but it could use some more features, it lacks a widget, and there is no notification bar icon for fast access. Good comment though. Maybe the people who are completly stock everything should give this a go since they are reporting lag issues.
Click to expand...
Click to collapse
I agree with you on the simplicity of the app in the original post. If the developer can dial out the lag it is definately the best tool for screen filtering on the xoom. I just wish the OEMs would provide simple calibration tools for screens.
I know that the most common way people have been switching between phone and tablet modes in AOSP builds of ICS is by changing the lcd density. Well, I'm here to tell you that there is an easier way to do it, and it doesn't create weird looking out-of-aspect-ratio artifacts in certain apps (like Google Music in portrait orientation in tablet mode).
So, in your build.prop, instead of using the traditional ro.sf.lcd_density= line, you can remove that entirely, and use:
ro.build.characteristics=
and after the "=" just put either tablet or phone.
That's it! Easy peasy!
Jade Eyed Wolf said:
I know that the most common way people have been switching between phone and tablet modes in AOSP builds of ICS is by changing the lcd density. Well, I'm here to tell you that there is an easier way to do it, and it doesn't create weird looking out-of-aspect-ratio artifacts in certain apps (like Google Music in portrait orientation in tablet mode).
So, in your build.prop, instead of using the traditional ro.sf.lcd_density= line, you can remove that entirely, and use:
ro.build.characteristics=
and after the "=" just put either tablet or phone.
That's it! Easy peasy!
Click to expand...
Click to collapse
Thanks for the tip mate
That was added in CNA v5 and i think it created problems and was changed back in v5.1.
Fyi, tablet mode changes the dpi to 160, at the moment i use 200 because 160 is a tad bit small for me.
Good tip tho, interested to see if it creates any issues with Imilika v8..
Sent from my GT-N7000 using XDA
Great tip, although this really belongs in the "General" section.
Expect more from someone with almost a thousand posts...
sundazetoo said:
That was added in CNA v5 and i think it created problems and was changed back in v5.1.
Fyi, tablet mode changes the dpi to 160, at the moment i use 200 because 160 is a tad bit small for me.
Good tip tho, interested to see if it creates any issues with Imilika v8..
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
exactly
If you didn't create it... this belongs in general...
Sent from my GT-N7000 using xda premium
Jade Eyed Wolf said:
I know that the most common way people have been switching between phone and tablet modes in AOSP builds of ICS is by changing the lcd density. Well, I'm here to tell you that there is an easier way to do it, and it doesn't create weird looking out-of-aspect-ratio artifacts in certain apps (like Google Music in portrait orientation in tablet mode).
So, in your build.prop, instead of using the traditional ro.sf.lcd_density= line, you can remove that entirely, and use:
ro.build.characteristics=
and after the "=" just put either tablet or phone.
That's it! Easy peasy!
Click to expand...
Click to collapse
So basically you keep the DPI @ 320 & change the above parameter to tablet?
Will this give me the tablet like two panes in settings, gmail & google play?
Screen shot please, and stop crying about this brlongs here ore there. Cry babys
daddymatt said:
If you didn't create it... this belongs in general...
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Spot On
Thread Moved To General
prgopala said:
So basically you keep the DPI @ 320 & change the above parameter to tablet?
Will this give me the tablet like two panes in settings, gmail & google play?
Click to expand...
Click to collapse
So basically ICS has 2 modes, tablet mode and phone mode. To my understanding this is dependent on the dpi, anything lower than 213 dpi will display ICS in tablet mode i.e. 2 panes on most apps. Apparently 160 dpi is the official tablet mode..and i think 320 dpi is the standard phone mode. I currently run mine in 200 dpi and most apps show 2 panes.. I am sure there is a better explanation somewhere
Sent from my GT-N7000 using XDA
sundazetoo said:
That was added in CNA v5 and i think it created problems and was changed back in v5.1.
Fyi, tablet mode changes the dpi to 160, at the moment i use 200 because 160 is a tad bit small for me.
Good tip tho, interested to see if it creates any issues with Imilika v8..
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
So far, I haven't had any issues with Imilka's build. Then again, the stock keyboard still looks funky in portrait tablet mode, but that's nothing new. Everything else works perfectly.
More than anything, this fixes things like tablet portrait Google Music recent's.
sundazetoo said:
So basically ICS has 2 modes, tablet mode and phone mode. To my understanding this is dependent on the dpi, anything lower than 213 dpi will display ICS in tablet mode i.e. 2 panes on most apps. Apparently 160 dpi is the official tablet mode..and i think 320 dpi is the standard phone mode. I currently run mine in 200 dpi and most apps show 2 panes.. I am sure there is a better explanation somewhere
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
Absolutely... i don't think just changing the build characteristics parameter to 'tablet' will give you true tablet mode...I guess it will help in apps like music etc where the controls are screwed up in tablet mode...did you try it btw, i mean keeping the DPI below 213 & setting the characteristics to tablet and then check the music app for e.g.
Can sum1 tell me plz ...
what shud i edit in build.prop in order to run gameloft games ...
bcz for default setting it sayz
" your device not compatble blah blah and request for refund "
Using ICS STUNNER ROM
Can ne1 help me out wid dis thing or wts the workaround for this ???
Are any body trying make the screen resolution better or higher by any apk as pimp my rom app or by another way
WiFi issues
When I using single app as a browser or Facebook there is no broplem is fast &smooth but if I use multiple app using wifi (multitasking) they run very slowly nearly killed
But when I make same thing with my phone LG optimus 3d that problem doesn't exist
Is that normal in this tablet or there is a hardwar or software issue
Resolution: absolutely not. They only build the pixels you got, and there is no way to change this but buying a different tablet with a different screen.
Wifi: no. check powersave settings
ps: normally you make different threads for each topic.
cars10k said:
Resolution: absolutely not. They only build the pixels you got, and there is no way to change this but buying a different tablet with a different screen.
Wifi: no. check powersave settings
ps: normally you make different threads for each topic.
Click to expand...
Click to collapse
Thanks a lot man
I will do next time because i just new member, i am learning
So I saw this in the build prop
"qualcomm sensors enable
#
# LGE CHANGE_S, 2013-10-29, [email protected]
# below sensor is default true by HAL source.
#ro.qualcomm.sensors.qmd=true
#ro.qc.sdk.sensors.gestures=true
#ro.qualcomm.sensors.pedometer=true
#ro.qc.sensors.step_detector=true
#ro.qc.sensors.step_counter=true
#ro.qualcomm.sensors.pam=true
#ro.qualcomm.sensors.scrn_ortn=true
#ro.qualcomm.sensors.smd=true
#ro.qualcomm.sensors.game_rv=true
#ro.qualcomm.sensors.georv=true
# LGE CHANGE_E, 2013-10-29, [email protected]"
Not sure if anything there can help, but I know that the sharpening is applied when there's something light on a dark background or vice versa and also if you have any type of floating menu it'll sharpen everything in the background.
Samsung does this as well but as far as I know only in multi window mode.
Its not a screen issue as its not always apparent. And as far as I know the oppo find 7 has the same panel and doesn't exhibit these effects.
So anyone have any ideas?
Kernel related ?
Display drivers?
Maybe we should all email lg and ask them for an option to remove it.
Just fyi oppo use japan display inc panel while lg use their own panel
I think the only way to defeat the sharpening is with a custom kernel and possibly an app to tweak the display unless LG of course turn this 'feature' off in the future themselves via an OTA update.
daleski75 said:
I think the only way to defeat the sharpening is with a custom kernel and possibly an app to tweak the display unless LG of course turn this 'feature' off in the future themselves via an OTA update.
Click to expand...
Click to collapse
Hope they do. Its pointless.
So anyways I came across another thing.
If you tune the display with a kernel app as in colors. If you tune all the colors down and make the colors darker and such, everything will have the sharpening applied. So it seems like the software sees that and applies it to everything.
Hoping it's just kernel
Lostatsea23 said:
Hope they do. Its pointless.
So anyways I came across another thing.
If you tune the display with a kernel app as in colors. If you tune all the colors down and make the colors darker and such, everything will have the sharpening applied. So it seems like the software sees that and applies it to everything.
Hoping it's just kernel
Click to expand...
Click to collapse
I am just guessing as I am not a developer by any shape of the imagination but this sounds like it's built into the OS so possibly a tweak to prevent this behaviour from getting triggered which will turn off the sharpening effect.
daleski75 said:
I am just guessing as I am not a developer by any shape of the imagination but this sounds like it's built into the OS so possibly a tweak to prevent this behaviour from getting triggered which will turn off the sharpening effect.
Click to expand...
Click to collapse
Yes I think so. If someone can baksmali the ROM maybe they can find something. Id get in touch with a Dev but as this time it seems like no one owns the device.
Lostatsea23 said:
Yes I think so. If someone can baksmali the ROM maybe they can find something. Id get in touch with a Dev but as this time it seems like no one owns the device.
Click to expand...
Click to collapse
When it finally rolls out to the USA then I think it will get better dev support.
I'll have the device soon, but I'm not sure we're able to turn it off since it may be the part of the driver. Haven't done it yet, but if we can debug the running code and binary patch the trigger effect into not signaling, we may fix it. If it IS a trigger at all; e.g. we should find when it does signal the driver/gpu to apply sharpening and just switch code from JE to JNE or similar to kill the trigger and never apply it.
Theoretically.
Hopefully LG can turn it off and not a hardware combo issue with the 801 and this particular display tech.
It can be turned off. They purposely added it
Lostatsea23 said:
It can be turned off. They purposely added it
Click to expand...
Click to collapse
I wonder if anyone knows the purpose. Because any sane person would turn it off after seeing it in action.
toncij said:
I wonder if anyone knows the purpose. Because any sane person would turn it off after seeing it in action.
Click to expand...
Click to collapse
The purpose is either, they want to emphasize the need for it so they make things extra sharp over 1080p not realizing it actually looks worse when its sharpened. Or its because the contrast ratio is low so to do that they sharpened it in areas where it would be more noticeable to make it more legible. Again, doesn't really help.
On the galaxy phones it would produce this on multi window mode as stated and when putting a cm ROM on it you wouldn't get any of that since there's no window mode. But... If you go into screen settings and change the screen aliasing type or whatever, if you change from standard to reading mode it would make the display sharp exactly like we see on this one. So once we get kernel support for screen modes (cm adds modes such as movie mode and sharpness ect) then we should be fine.
Lostatsea23 said:
The purpose is either, they want to emphasize the need for it so they make things extra sharp over 1080p not realizing it actually looks worse when its sharpened. Or its because the contrast ratio is low so to do that they sharpened it in areas where it would be more noticeable to make it more legible. Again, doesn't really help.
On the galaxy phones it would produce this on multi window mode as stated and when putting a cm ROM on it you wouldn't get any of that since there's no window mode. But... If you go into screen settings and change the screen aliasing type or whatever, if you change from standard to reading mode it would make the display sharp exactly like we see on this one. So once we get kernel support for screen modes (cm adds modes such as movie mode and sharpness ect) then we should be fine.
Click to expand...
Click to collapse
Well, I don't believe a whole bunch of smart engineers, designers and such in dev and QA would not notice it sucks...
And for screen modes, after so much hassle, I hope and expect LG is preparing us a "turn bloody thing off" setting...
Well once it comes out in the states I will be contacting some devs about it. We need a boot loader unlock as well though
toncij said:
I wonder if anyone knows the purpose. Because any sane person would turn it off after seeing it in action.
Click to expand...
Click to collapse
Without seeing it in person, it probably was added to make their simple UI have more of a pop to it. They were probably trying to make it stand out more in stores, like how tvs usually have horrible settings when on display at a store.
flaring afro said:
Without seeing it in person, it probably was added to make their simple UI have more of a pop to it. They were probably trying to make it stand out more in stores, like how tvs usually have horrible settings when on display at a store.
Click to expand...
Click to collapse
They're dumb because it makes it look worse. In almost positive a fix will be found. If anything maybe the carrier releases will have this fixed already.
Guess what...
I installed bravia engine v3 from Android Tweaker 2 and...
I think my display is more clear and the sharpening is slightly gone!
You guys better try it and tell your impression
Sent from my LG-D855 using XDA Free mobile app
haris182 said:
Guess what...
I installed bravia engine v3 from Android Tweaker 2 and...
I think my display is more clear and the sharpening is slightly gone!
You guys better try it and tell your impression
Sent from my LG-D855 using XDA Free mobile app
Click to expand...
Click to collapse
Nope. Exactly the same. Placebo
Sugar pills taste so good
rushless said:
Sugar pills taste so good
Click to expand...
Click to collapse
Lol. If an update to remove this isn't out in the next couple weeks. Bye bye G3
Import this little profile here to tasker
PLEASE TRY IT WITH QHD
Follow the steps within profile
Beta 2 will theorically will let you run strictly on 60hz and will run you back to 120 whenever you open an app that you desire to be refreshing at 120
Needed
Tasker
Patient
Knowledge on how to run adb commands until there's root.
If it isn't being force on let's say Gmaps but it is set to 120hz most likely it will drop down to 60 to save battery. And this can happen with other apps as well.
Please enjoy and report back.
Update Beta V2
https://taskernet.com/shares/?user=...WrgmW2Mlw=&id=Profile:Selective+120hz+Per+App
gmaps is garbage, especially the navigation it doesnt even run at 20fps, i am still using old maps pre big update where the navigation was separate
suffeks said:
gmaps is garbage, especially the navigation it doesnt even run at 20fps, i am still using old maps pre big update where the navigation was separate
Click to expand...
Click to collapse
Does it even run smoothly on pixels? It never ran smoothly on any of my phones, especially when zooming out during navigation, pathetic.
Has anyone successfully used this yet? I'm more interested in tying it to the power mode like high performance or optimized. Is that possible?
peachpuff said:
Does it even run smoothly on pixels? It never ran smoothly on any of my phones, especially when zooming out during navigation, pathetic.
Click to expand...
Click to collapse
Yes it runs smoothly on pixel 4
I'm using this and working very well. Running all apps besides video playback apps and gmaps at 120hz.
Takes a second or 2 for refresh rate to change but I think this is a great idea in general, app controllable refresh rate
jasons1004 said:
Running all apps besides video playback apps
Click to expand...
Click to collapse
Damn this is what I wanted... I've never had tasker and don't know how to use it and don't want to buy it just to test something to find out it doesn't work at the end. Can you please test if the video app kodi can be run at 120hz please?
chieco said:
Damn this is what I wanted... I've never had tasker and don't know how to use it and don't want to buy it just to test something to find out it doesn't work at the end. Can you please test if the video app kodi can be run at 120hz please?
Click to expand...
Click to collapse
It should
Download the profile and import to tasker
Pick which apps you want to run in each and you're good to go.
That being said I installed kodi and it seems like 120hz.
Easy to tell 120 from 60.
I don't think worth running video playback apps in 120 as video won't run in 120 anyway.
I don't understand how to import this into Tasker. When I click on the link from my phone, it doesn't give me the option to open it with Tasker. Is there any way you can post the actual file here?
steelersmb said:
I don't understand how to import this into Tasker. When I click on the link from my phone, it doesn't give me the option to open it with Tasker. Is there any way you can post the actual file here?
Click to expand...
Click to collapse
When you click link in thread, click import and then click yes, this should open in tasker. Then you click on choose apps and pick which apps to run in 120 and rest go to 60.
You have installed tasker right?
I don't think this is working at all for me. There's a noticeable difference when I enable/disable the setting manually regardless of whether the Tasker profile is applying (which it says it is).
peachpuff said:
Does [google maps] even run smoothly on pixels? It never ran smoothly on any of my phones, especially when zooming out during navigation, pathetic.
Click to expand...
Click to collapse
Someone said it does and they're wrong. It seems to run at about 15-30fps, just verified on my Pixel 4XL.
Places where this is evident are any in-app animations, for example if you tap on your blue location dot, it will animate to fill the screen with blue. Or if you search a location and tap its card, it will animate to pull the card up. Or you can just fling the map around. There's no way anybody with decent vision can confuse this with 60fps let along 120fps.
Kevtrejo37 said:
Please enjoy and report back.
Click to expand...
Click to collapse
Hi Kev,
first of all thank you for the thread's and tasker profile regarding the 120Hz tingz!
The 120Hz experience on the S20 line imho is ULTRA disappointing!
Not the Display itself but more the way stupid Sammy implemented it Software wise.
First disappointment, the limitation of only FHD+
but this was known even before the S20 line was officially announced so I actively decided to look pass that. Even though most people say FHD+ is enough and you don't see any pixels or whatever, I have to say coming from a S10 with a smaller display and and higher dpi, I do notice how much softer the image quality on the S20+ is! It's noticeably less sharp.
The Second disappointment no one warned me about is the fact that half of the apps revert back to 60Hz!!!
No one told me this! and I ****ing hate this. Maybe I was naive, maybe it's the fact that I had no experience with a phone that has a high refresh rate display, but to my understanding if I set my phones display to 120Hz, everything, the UI and all apps would be displayed @*120Hz! But no! this already is like on the leaked Firmware Screenshot wich shows the "Dynamic" option in the middle! it's not locked.
Just shows again how important root is. The ability to take control of the device you own and not giving control to stupid Sammy dev's...
Your method with tasker works fine, but I had no experience with tasker prior and I only using it during it's trial period. After the trial ends, I'm not going to buy the full version.
Is there maybe a adb command that can globally set the phone to a fixed 120Hz refresh rate? Since I don't need a per app selection.
again thank you for this tasker profile so far.
Thanks for the profile! But there is one issue: it's works only once for my S20, then after launching few apps refresh rate drops to 60Hz ((( Even rebooting my phone doesn't help (