Develop Bugs

[APP] Lumos backlight manager 1.0

Today Lumos 1.0 final is released, besides other changes now has better support for HVGA in settings dialog.

never tried this on other phones, but it sounds fantastic
going to give it a whirl and see if anything improves

Well, I was about 6 monthes with previous release and it really helps to save battery.
Just played a little to make own backlight profile.

to be quite honest, cant really get the hang of it. keeps changing the level almost randomly with little to no reason as to why (lightning outside the phone remains the same).
any ideas as to what im doing wrong?

I’ve tried ‘LumosWizard’ 5 month ago but I’ve never managed to make it work correctly
So that, I use ‘Mylostblog Mylight’ now.
Not the same but its easy to use with a shortcut in "Cookie’s Home Tab".

Well, just try run calibration correctly, my sensor's range is 0..1904,
minimum level 1, maximum level 5.
There are issues with g-sensor games - lookup the original Lumos thread.
tkur said:
to be quite honest, cant really get the hang of it. keeps changing the level almost randomly with little to no reason as to why (lightning outside the phone remains the same).
any ideas as to what im doing wrong?
Click to expand...
Click to collapse

[BUG] Screen Sensitivity Issue-Lag (4.0.4-4.1.x)

Problem summary
Known cause (might be others): selecting an app from the Recents list (Task Switcher)
Temporary fix: turn the screen off, then back on
Workaround: avoid using Recents list (you can use a 3rd party task switcher instead)
How to test: open Messaging, hit Home, hit Recents, select Messaging from the list. Your screen will be less sensitive until you turn the screen off and back on. You can view the pressure by going to Settings -> Developer Options -> turn on Pointer Location. This will allow you to see the Prs of each tap in your status bar. Normally your lightest taps that register will show anywhere from 0.28 to 0.32. However, after this bug is activated, you will mostly get values over 0.40 for your light taps. This is actually a very noticeable increase, especially when trying to type quickly.
Please report any other known methods to "activate" this bug. After re-assigning my Recents button to a 3rd party app (I'm using Simple Task Switcher), I haven't seen this bug at all. It seems that a couple of people have seen it produced by something other than Recents, but they haven't narrowed it down (or reliably reproduced it on purpose).
Please star this issue officially so Google can fix:
Link is http://code.google.com/p/android/issues/detail?id=29734
Note: Downloading & using Screen filter application from play store, with brightness set to

Your hands are really dirty or really dry. Try moisturizer or something.

Been using my screen for almost hour straight now. No issues.
--------+++--------
iphone. helping computer illiteracy become popular since 2007.

Hehe yes this s gonna be a difficult one to confirm. But it is definitely not dirty hands. To clarify, a quick press of the power button to lock then unlock completely fixes the issue. Same fingers suddenly register perfectly. This is driving me nuts as the phone is not even usable right now. Literally.

@rbiter said:
Been using my screen for almost hour straight now. No issues.
--------+++--------
iphone. helping computer illiteracy become popular since 2007.
Click to expand...
Click to collapse
ios 6.2 doesnt get issues.

I don't know about your other experiences, but as far as the browser goes I have the same scrolling effects as you do. I think this is how it is meant to be. They tightened the scrolling a lot and I kinda like it. Before one small flick would send me across the whole page, which was kinda annoying. Just my preference.

I'm not having this problem. It would drive me crazy too. Been using my phone alot over the past two days and I didn't run into this problem even after almost 1h of continuous surfing. Also a few checkpoints of Shadowgun didn't trigger it.
But you can confirm your problem if you enable "cursor position" in the dev options (hope that's what it 's called in english). "Prs" and "Size" should need a lot more than around 0.30-0.40 to register your touch if you have the problem you describe.

I am sorry that you're experiencing this, but 4.0.4 has nothing to do with this. 4.0.4 is just software, Galaxy Nexus is not a pressure-sensitive device, it is merely touch-sensitive. Which means that software gets an analogue signal from the touchscreen, either 1 or 0. It has no 'range' of sensitivity, so it cannot decrease in sensitivity in software (if it did, then it would not work at all).
This is entirely hardware issue and I suggest either making sure your screen is clean, your screen protection thing (if you use one) isn't acting up or if your hardware has become faulty (have you dropped it recently?).
If problem persists then return under warranty.

My wife had this issue once.
It was the third party launcher she was using.
I don't think its a matter of touch sensitivity dropping, its a matter of the system just being too slow to really work right.
It was ADW EX, fwiw.

kristovaher said:
I am sorry that you're experiencing this, but 4.0.4 has nothing to do with this. 4.0.4 is just software, Galaxy Nexus is not a pressure-sensitive device, it is merely touch-sensitive. Which means that software gets an analogue signal from the touchscreen, either 1 or 0. It has no 'range' of sensitivity, so it cannot decrease in sensitivity in software (if it did, then it would not work at all).
This is entirely hardware issue and I suggest either making sure your screen is clean, your screen protection thing (if you use one) isn't acting up or if your hardware has become faulty (have you dropped it recently?).
If problem persists then return under warranty.
Click to expand...
Click to collapse
Lol that is hilarious. You forgot the step where its the OS that actually processes the input data, so in that process, a ton of problems can arise.
And personally, since 4.0.4 I have also been experiencing a "similar" issue. When scrolling down (and only down), I experience a kind of "lag" like if it only registers the swipe movement half an inch lower. Its not a big deal, but still an issue.
Edit : What he explains as "pressing very hard" is most likely the fact that when you press harder you actually cover more surface, so the amount of extra input data can definitely impact the behavior.

I had issues for a few hours after the 4.0.4 update, where my softkey buttons weren't responding. Thankfully, it seems to be fine now, but it was a cause for concern.
Sent from my Galaxy Nexus

gokpog said:
I'm not having this problem. It would drive me crazy too. Been using my phone alot over the past two days and I didn't run into this problem even after almost 1h of continuous surfing. Also a few checkpoints of Shadowgun didn't trigger it.
But you can confirm your problem if you enable "cursor position" in the dev options (hope that's what it 's called in english). "Prs" and "Size" should need a lot more than around 0.30-0.40 to register your touch if you have the problem you describe.
Click to expand...
Click to collapse
Thank you my friend, I should have thought of this; now I have numbers to confirm this. So with cursor option enabled I can get down to 0.30, managed 0.28 once. However when the bug starts, I can confirm that I cannot get below 0.60. It just refuses to register that input for some reason.
I lock the screen, 1 second is all it takes, and now it registers down to 0.30 again and all touch works properly. Its almost like some type of memory leak issue is the way it feels to me. It only starts happening after a few min of use.
Its definitely an issue now that I can see the pressure numbers. The question is what the hell can I do about it. I flashed aokp29 with the latest 4.0.4 ota merged in, problem still occurs. I'm gonna try stock 4.0.2 or 4.0.1 just to see. Thanks.

I have never had much luck upgrading Linux versions. That's why I start fresh every time with Android. Lol
Sent from my Galaxy Nexus using Tapatalk

Before I start digging, anyone know specifically which driver controls the touch input? I'll try looking thru github.
Also I was on stock 4.0.1 prior to this. So this could be normal behavior for everyone but everybody is used to it since nobody stayed on 4.0.1 like me. Cause I can easily say this is difficult to notice if you aren't paying attention. The question is, why does locking the screen temporarily change it back...

I can confirm some of what you are saying..sometimes when I'm browsing the scrolling tightens up..I lock the phone then unlock it and it is smooth again..doesn't happen all the time tho..doesn't bother me but I've noticed it
Sent from my Galaxy Nexus using XDA

I can also confirm. This morning I found the Swiftkey was lagging on Facebook. Something like the phone did not receive the touch. Then I rebooted and now it is ok.
I did not get this issue on 4.0.2 and I don't install anything new on 4.0.4.
The way I installed 4.0.4 was from the official factory image, so my phone is fresh! I reinstalled all apps manually as well. Nothing fancy apps.

I know this is my first post, but I can definitely confirm this issue.
I use my Galaxy Nexus for development, so the screen is always on. The sensitivity goes down very quickly.
My phone was an International GNEX that I loaded the US firmware on and then I flashed the OTA 4.0.4 update.

kristovaher said:
I am sorry that you're experiencing this, but 4.0.4 has nothing to do with this. 4.0.4 is just software, Galaxy Nexus is not a pressure-sensitive device, it is merely touch-sensitive. Which means that software gets an analogue signal from the touchscreen, either 1 or 0. It has no 'range' of sensitivity, so it cannot decrease in sensitivity in software (if it did, then it would not work at all).
This is entirely hardware issue and I suggest either making sure your screen is clean, your screen protection thing (if you use one) isn't acting up or if your hardware has become faulty (have you dropped it recently?).
If problem persists then return under warranty.
Click to expand...
Click to collapse
Just to point out, the phone is all digital. It does not get an analog signal from touching the screen. Also to that point you said analog but then described digital with the 1 and 0

Has anyone affected tried going between 4.0.2 and 4.0.4? To check the possibility of a driver or some related value changing.
Also, if not fixed by going back to 4.0.2, this could be due to current leakage from somewhere causing the touch to not work properly. I've seen it on other capacitive touch devices, though mainly when a non-compatible charger is connected. When you shut the screen off, the charge causing the problem/interference with the touch is temporarily dissapated, but then comes back after you use it again. Probably very unlikely in this case, unless Google changed something in the touch driver that makes it more sensitive to interference, which in turn messes with actual input from fingers.

TechNoir said:
Has anyone affected tried going between 4.0.2 and 4.0.4? To check the possibility of a driver or some related value changing.
Also, if not fixed by going back to 4.0.2, this could be due to current leakage from somewhere causing the touch to not work properly. I've seen it on other capacitive touch devices, though mainly when a non-compatible charger is connected. When you shut the screen off, the charge causing the problem/interference with the touch is temporarily dissapated, but then comes back after you use it again. Probably very unlikely in this case, unless Google changed something in the touch driver that makes it more sensitive to interference, which in turn messes with actual input from fingers.
Click to expand...
Click to collapse
Its possible. I was on 4.0.1 so perhaps this issue originated in 4.0.2 but I never noticed since I didn't update then. I can add that I did multiple wipes and clean flashes, and also tried both aokp 28 and 29 (new 4.0.4 ota merged), and happened on both.
I'll post what I just sent to arbiter which gives more insight.
From my extra testing under normal use my light touches register 0.28-0.33. Especially on swipes, the end of the swipe registers 0.28 as the finger travel breaks contact with the screen giving that swipe extra input which pushes the swipe motion further extra boost. When the bug starts the touch swipe won't even break 0.38-0.40, and that extra swipe data is lost resulting in the end of the swipe data points being excluded and swipes travel half the distance.
This gets exacerbated on the keyboard when fast typing light pressed. Its so bad it frustrates my face off cause typing just ceases to be possible. Such a difficult issue to diagnose.
Click to expand...
Click to collapse
Yes my face literally flew off!

Weird screen cluttering when trying to open camera

Hello,
Today me and a friend of mine noticed something really weird on the Nexus 5X. If you have the factory default wallpaper enabled (the one that appears on the box of the phone) and try to access the camera while the screen is locked the top of the screen starts to clutter.
In order to observe this you have to have:
1) The wallpaper set to the factory default one.
2) The phone locked.
Then you have to start dragging the camera icon at the lower right corner of the screen slowly without releasing. At some you will notice that a small portion at the top of the screen starts to clutter and display weird colors. At first I thought that this a hardware related issue (faulty screen) but I have verified that the same thing happen on other devices as well. Setting the wallpaper to any other, other than the default one seems to not cause this.
Both phones I tested this on where running Android 6.0.1 and had all the latest updates installed. I know this is something really minor and mostly unnoticeable but it would be really nice to know what could cause this.

I would never have noticed this if it weren't for this thread. It seemed to only happen with the default wallpaper as stated by the OP. Most people would never notice this because they customize the wallpaper and probably never use the camera shortcut on the lock screen.
Sent from my Nexus 5X using Tapatalk

Strange edge lighting behaviour

So I have a really strange thing going on with edge lighting which is driving me crazy.
Whenever I play Elder Scrolls Blades the edge lighting appears but only in the bottom of the screen. As far as I been able to tell this only happens in this app though I can't be 100% sure.
Now what is strange other than it happens only in the bottom of the screen is that it keeps happening every few seconds, there is no notifications received and it happens, if I disable edge lighting it still happens, no matter to what effect I set the lighting it always happens in stock blue.
I can't possibly figure out what is this and I tried everything, any ideas would be appreciated.

Same thing here, in at least 2 games...
Thought it was related to spen, but it seems not...
Tried to disable Game Launcher but still got these random bottom screen notification pulse... And stock blue aswell. Got no clue atm

Thanks for letting me know I'm not the only one experiencing this. I tried literally everything and nothing seems to fix it. What's also weird is that the lighting comes in irregular intervals, sometimes just going crazy and sometimes appearing much less.

I have just discovered this issue appears in all games so it's a bigger problem then I originally thought. If disabling the game launcher does nothing then it makes it even more strange and annoying.

Yeah, same here, happens on basically all the games.
Maybe related to game booster?
Let's try to compare our setup : are you using any notification enhancement app? (like aodNotify)
Are you using your spen while playing?
But yeah, this random glow line **** is driving me crazy too!

Currently I am using aodNotify though I tried uninstalling it and the problem persists, I also have goodlock installed and the edgeslighting+, same thing with and without it. I am not using the spen, but I have tried just taking it out while the game is running and leaving it out for 5 mins, no change. I have disabled and enabled the stock edge lighting as well and the problem is still there. Nothing seems to effect it. Its ridiculous

i tried on mobile legend adventure, no problem on it, perhaps a scaling issue?

Will try to tweak full screen mode.
Increasing dpi doesn't change the weird thing, neither switching from Samsung stock launcher to Nova...
Also I'm using gestures based navbar, but I also tried with or without tips display, standard navbar... Still occurring.
Did you go from a scratch Note 10+ or used SideSync to switch? (I was coming from a Note 8)

I don't think it has anything to do with scaling, I tried setting the game on full screen and automatic, both giving the same results.
I used Smartswitch from Note 9.
Later today the camera effect from aodnotify started appearing in the game aswell (landscape mode), along with the edge lighting.?
I uninstalled aodnotify afterwards, found out there is a aodnotify Manager plugin which stays after uninstalling the main app.
Uninstalled the plugin aswell, opened edgescreen from the system app and cleared cache.
It was showing the app was using RAM with high frequency.
I don't have the time to check now does this fix the problem but will let you know once I do.
The only other thing left to do if this doesn't work is to clear edge screen data.

Will try this aswell, and restore all the notifications and edge lightning settings...

What I wrote above didn't work so I disabled the option for edge screen to show on top of other apps, so far this seems to fix the problem.

Unfortunately I was wrong and nothing above fixes the problem. I also wiped the entire edge screen memory, no effect. This is the weirdest thing I ever encountered in my years of Samsung phones and it's extremely annoying that there is no fix.

Strange, I don't have any issue.
Did you try with and without locking the screen orientation to see if edge lightning follows settings as it should?
I personally only use auto orientation.

I also use auto rotation and it happens the same way in landscape and portrait, the most annoying thing is that it happens really much, like 2-3 times in 10 seconds, or sometimes doesn't happen for few minutes then starts going like crazy, and as I said before there is no notifications or anything.

Same here, auto rotate on, only occurring during games.
I don't even know if I can debug which process is running these random edge notifications, without dig into tons of log files...
And if not, I guess I'll try to factory reset and re-sync again..

Its incredible that a factory reset seems like only possible solution left but I hope maybe some future update will fix it since I hate doing factory reset. Please keep me posted if you discover anything new.

Hating doing it aswell but this is too damn annoying..
If no clue, I'll go for a restore without restoring system settings... Maybe some notifications behaviors have been messed up
I'll keep you in touch for sure

Tried to wipe cache partition, still no clues...
Did this also got triggered in portrait mode game?
So confusing...

Yes it happens in all games no matter of the screen orientation. I really have no more ideas aswell

Got some news, another post is talking about this : https://forum.xda-developers.com/galaxy-note-10+/help/strange-blue-bar-games-t3963939
Seems related to the new game booster feature "temp and cpu monitoring"
Will try to disable this for a specific game and see...

Redmi note 8t huge issue with screen please help!

So I've gotten Redmi Note 8t half a month ago or so.. and about the time I updated to MIUI 11 I've started experiencing this weird bug.. Any app or screen or page or icons from the home screen or buttons from apps that remain turned on for some time (literally anything longer than 15 seconds) kind of stay "etched" on my screen for some time (relatively equivalent to the time the relevant app/screen/page was turned on).
I have no idea why this is happening so any help would be massively appreciated. A photo of the problem attached.
Ps this bug appears on every darker screen, not just on home screen.

novak.vujacic97 said:
So I've gotten Redmi Note 8t half a month ago or so.. and about the time I updated to MIUI 11 I've started experiencing this weird bug.. Any app or screen or page or icons from the home screen or buttons from apps that remain turned on for some time (literally anything longer than 15 seconds) kind of stay "etched" on my screen for some time (relatively equivalent to the time the relevant app/screen/page was turned on).
I have no idea why this is happening so any help would be massively appreciated. A photo of the problem attached.
Ps this bug appears on every darker screen, not just on home screen.
Click to expand...
Click to collapse
the images don't seem to be loading for me, but looking at your description it appears to be a burn-in problem.
I'd suggest you bring it to a service center to have it checked.

jc9896 said:
the images don't seem to be loading for me, but looking at your description it appears to be a burn-in problem.
I'd suggest you bring it to a service center to have it checked.
Click to expand...
Click to collapse
Thanks for your reply. Try opening them by clicking on the link and then tapping on "view full image" - it's the only way they'll load I've no idea why, today the whole xda website behaved very unresponsive for me, maybe they didn't upload properly.
Anyway I've just now googled "burn-in" (yep I'd never heard about this before) and from whar I've seen it seems pretty similar to my problem.
Although, in my case, the icons/buttons/keyboard letters that "etch" themselves into the screen after being used for some time do disappear after some time (usually dependant on the time those apps/icons/letters were shown/used on the main screen.
PS The thing is new, I've no idea how this could have happened.

jc9896 said:
the images don't seem to be loading for me, but looking at your description it appears to be a burn-in problem.
I'd suggest you bring it to a service center to have it checked.
Click to expand...
Click to collapse
I had this issue with a Moto G5, apparently it is not permanent, wich is nice, because when its permanent like in the case of amoled displays, the only real solucion is to replace the display. In this case to minimize it I downloaded a blue screen filter app and lowered the screen brightness to around 70 or less, btw this usually happens when you are watching bright stuff or when the phone is hot, also try to use dark mode whenever you can.

FOUND A SOLUTION
After tampering with many a setting, I found out that setting the colour temperature of the display in the stock settings of the phone to cool renders the burn-in almost completely invisible.

novak.vujacic97 said:
FOUND A SOLUTION
After tampering with many a setting, I found out that setting the colour temperature of the display in the stock settings of the phone to cool renders the burn-in almost completely invisible.
Click to expand...
Click to collapse
nice to see your problem has been solved!
some LCDs have screen retention when displaying certain colour temperatures.
also, seems like your attached photos are working again