Hello every one, I am new here and may have posted in a wrong section but I am in major trouble and need help.
Yesterday I bought this (quite expensive for me) tablet, the Asus ZenPad 10. It's beautiful and I like it but I ran into a very big issue after using it for a while.
I recently noticed that during videos or sliding through pictures the screen will turn itself darker when it's already dark and brighter when the picture/video is already bright. It is very annoying and I tried everything from switching screen and power saving options, color management and so on. Also tried un-installing and re-installing every feature like Asus Splendid, Boost Mode and so on. Please do not suggest to turn off auto-brightness or any setting of this kind as I am not a total newb regarding this matter and already cycled through every option of this sort plus the ones in the *Settings* tab.
Call it whatever you want : screen auto-dimming, gamma correction, LCD backlight adjustment, auto-contrast etc. but do help me out here as I am one step away of returning the tablet.
I would also like not to root the tablet if possible, if not, I'll just go for it and do it ( might need help with rooting as well ).
Thanks in advance and I wish everyone best of luck! :good:
Were you ever able to remedy this situation?? I just picked up a budget ZenPad S 8.0 and have the same frustrations with screen dimming. And now, to top it all off, i'm getting spammed with this "unfortunately, Splendid has stopped." I've made all the same/similar adjustments that you have, and even read about it before buying an ASUS device, but figured -- how bad could this really be? Since the ASUS Splendid color adjustment software is no longer working, i'm at a loss for how to proceed.
Running Android Marshmallow, if that matters.
Looks like my brand new Z300M has the same peculiarity. Disabling auto-brightness seems to be the only thing that helps.
Related
Hello
I have been having some problems with the main camera on the A500. It has different tints to it. Sometimes the picture seems to be divided in 4 and all 4 squares have a different hue to them. Restoring to factory settings seem to take care of it for a while. Initially I thought it was "skype" that messed it up, but it is not.
I just restarted the tablet and the camera is giving me a yellow tint, with a clear horizontal stripe about 3/4 inch wide through the middle.
The tab has stock 3.2 on it.
I was wondering if anyone has experienced similar problems and if there was a solution to the problem.
Thank you
Well, I would think the problem seems to be some app/apps you have installed. Based on when you do a factory reset, it goes away.
I would just do another factory reset. Then verify it went away. Run it for a couple of days WITHOUT installing any apps. This will probably rule out a hardware issue.
Then install apps, 1 at a time. Use the camera, and look for issues.
Thanx. I will give that a try.
I traced it back to Swift Key X keyboard for tablets. How is that even possible?
Also yahoo messenger is another one that ruins the camera. As soon as I install any of those apps and reboot, the camera is back to normal.
Does anyone out there use either of those apps?
mobilebone said:
I traced it back to Swift Key X keyboard for tablets. How is that even possible?
Also yahoo messenger is another one that ruins the camera. As soon as I install any of those apps and reboot, the camera is back to normal.
Does anyone out there use either of those apps?
Click to expand...
Click to collapse
So, everything is ok?
Rule #1,
Stay away from apps meant for phones.
Yes, they "may" have tested it it on "1" tablet, then gave it a clean bill of health. Maybe.
Moscow Desire said:
So, everything is ok?
Rule #1,
Stay away from apps meant for phones.
Yes, they "may" have tested it it on "1" tablet, then gave it a clean bill of health. Maybe.
Click to expand...
Click to collapse
I thought it would be ok. But after restarting a few times, the camera colors are off. I'm going to root and install a custom 3.2 to make sure it is not the hardware.
Spasiba for all your help )
any news about this problems.
it seems that my iconia has the same problem- i never noticed it because i dont use the rear camera.
i sold it it today and the guy who bought has described something like what you folks are talking about
the strange thing is that i had done a clean boot before i sold it, and the buyer hasnt installed anything on it yet.
im waiting to hear back from him after he tries another clean boot.
anyone else have any ideas ?
I'm having the same problem. I don't use it much, but the camera was ok before. When I tried using it this weekend, it showed colored translucent squares on the sides. It is not a config problem, as there are no effects turned on. The front camera works 100%. I will post a sample when I get home.
If I change the "whites" config to Incandescent, it kind of solves the problem. Sometimes, the squares appear, but not for most the time.
I believe this is not a harware issue, unless that whites configuration is made with hardware (highly doubt it). I don't have Swift key, or Yahoo messenger, or any other apps that use the camera (other than Skype, but it was already installed when the camera worked).
Did anybody find a fix to this? It seems it is only a problem on stock 3.2.
Edit: not an exclusive 3.2 stock issue, it appears that custom roms have this problem as well.
I have the same issue after ICS ota upgrade...
Any ideas?
I haven't had the issue since the ICS upgrade. Only tested once or twice, but it is working properly.
What I did to partially fix it was changing the White Balance to "Incandescent".
I've just noticed that the brightness slider moves from end to end with no change in screen brightness.
Anyone got a fix?
Android 5.0.2
Yes, I have the same problem. Mine is weird though. Mine will sometimes get bright and match the setting, but a majority of the time it goes to the most dim level on the screen regardless of where the brightness level is set. I'm hoping that it is something that I can fix, but I don't know if people will say that it's a hardware issue. My Tab is rooted again after I reinstalled the stock firmware again to try and fix the problem. Hopefully someone can offer an insight to this problem. I'm wondering if taking it apart and heating up the processor with a heat gun would cause it to work. That worked as a temporary fix on an Apple computer.
I have the same problem after I rooted the tablet. The only solution I found is install the app Screen Filter.
Are you on a custom ROM?
Can you reproduce the issue with a stock ROM?
If not,its probably the custom ROM have bugs.
Or maybe sth else
I've noticed that the Always On Display now lights up the entire screen, not just the pixels for the clock and date. As you can see in the pics, even the areas that are supposed to be black (i.e. unlit) are lit up in a dark black-ish kind of glow. This seems to be appearing after the most recent update. Is anyone else seeing this issue on their phones? Is this a software issue or a display problem? Would appreciate some insights on this. Thanks.
I dont have this problem
vrblr2405 said:
I've noticed that the Always On Display now lights up the entire screen, not just the pixels for the clock and date. As you can see in the pics, even the areas that are supposed to be black (i.e. unlit) are lit up in a dark black-ish kind of glow. This seems to be appearing after the most recent update. Is anyone else seeing this issue on their phones? Is this a software issue or a display problem? Would appreciate some insights on this. Thanks.
Click to expand...
Click to collapse
Technically speaking black color on AMOLED displays just turns off the pixels of the phone, it won't light up like what I saw from your picture.
If you are using a screen filter app such as twilight or night owl disable it and check, if not maybe try to reset your phone and I hope that is software related nothing more.
sa3d12 said:
Technically speaking black color on AMOLED displays just turns off the pixels of the phone, it won't light up like what I saw from your picture.
If you are using a screen filter app such as twilight or night owl disable it and check, if not maybe try to reset your phone and I hope that is software related nothing more.
Click to expand...
Click to collapse
Not using those apps. I did a phone reset, but the problem persists.
Did You purchase Your phone from an official Samsung seller? Only phones with non AMOLED panel would light up the whole screen.
Edit: just checked my AOD, Your AOD looks slightly different than mine. On my AOD I can see a date and two small icons.
Can you post similar pictures with the default AOD clock widget?
I'm also experiencing the same issue with my S7 Edge. Problem started out of the blue two days ago; there might have been Play Store updates but I dont reckon any system updates that day. I've been using the night clock for weeks and it was working fine before now.
The problem seems to affect only AOD and night clock, since the edge feed (rubbing the side) works completely fine - only lights the used pixels. AOD and night clock light up the whole screen (not much, but clearly visible in a dark room, grayish background)
Tried resetting and flashing older firmwares via Odin but nothing changed. Hope we find an answer to this, it's shame I cant use the night clock nor the AOD since its killing battery now. :/
I remember S6 edge having the same issue with night clock?
vrblr2405 said:
I've noticed that the Always On Display now lights up the entire screen, not just the pixels for the clock and date. As you can see in the pics, even the areas that are supposed to be black (i.e. unlit) are lit up in a dark black-ish kind of glow. This seems to be appearing after the most recent update. Is anyone else seeing this issue on their phones? Is this a software issue or a display problem? Would appreciate some insights on this. Thanks.
Click to expand...
Click to collapse
Mine is working fine. You must have received an update to something in the last few days if it worked before. Either that or it's a hardware issue.
This seems like a LCD and not AMOLED.. Did you get your display changed due to any reason?
OP stated that the problem occured after an update, so I think it was working fine before that? So I wouldnt say he has S7 edge with LCD display (for whatever reason that's even possible). I can say this for sure about my situation anyway. No display changes or any other repairs, it just started malfunction for no apparent reason.
I tried a third party app for AOD and it worked flawlessy... so the built-in AOD (& night clock) lights the whole screen, while edge feed and 3rd party AOD don't. Confusing.
@vrblr2405 : did you try night clock or 3rd part aod? Is the problem still there?
amritpal2489 said:
This seems like a LCD and not AMOLED.. Did you get your display changed due to any reason?
Click to expand...
Click to collapse
No. This is not an LCD, it's an AMOLED. This is an S7 Edge that I bought two weeks ago. Haven't changed the display or anything like that.
McKis said:
OP stated that the problem occured after an update, so I think it was working fine before that? So I wouldnt say he has S7 edge with LCD display (for whatever reason that's even possible). I can say this for sure about my situation anyway. No display changes or any other repairs, it just started malfunction for no apparent reason.
I tried a third party app for AOD and it worked flawlessy... so the built-in AOD (& night clock) lights the whole screen, while edge feed and 3rd party AOD don't. Confusing.
@vrblr2405 : did you try night clock or 3rd part aod? Is the problem still there?
Click to expand...
Click to collapse
This is the native AOD that comes preinstalled. Version 1.4.02. I've noticed that the edge clock also lights up the whole screen. Could you tell me which third party AOD app to use ? That way I can check and identify if it is a display problem or a software issue.
Try a fresh ODIN install of latest stock firmware
vrblr2405: I used (well, tried) Always on Screen by FayaX. Just make sure you disable the built-in AOD first and give the app the permissions it's asking for. Could you also check if the edge feed is working properly and doesn't lit up the screen? You know, the rubbin' thingy If those two work properly, I'm certain we are facing the same issue
@amritpal2489 : flashing stock didn't help on my situation, but of course it's always good to try.. I've been going through different (stock)firmwares now, just to see if something would change. No luck so far, downloading third one now.
Is there more to reset than the 4 files (AP, BL, CP, CSC)? How's the re-partition in Odin?
I'm unrooted, so I'll stick with stock fw's, but I'm wondering if there is something that's not "resetting" or if I can do something more to get to start every bit and piece from scratch.
Don't even think about re-partitioning in ODIN.. Its not required.
Moreover if you have already flashed stock firmware using ODIN then it is surely a hardware fault buddy. Get it checked at authorised service centre even if it is out of warranty. They will let you know the exact issue. Getting it repaired through them is your choice finally.
Yeah I guess that's what I need to do. Luckily there is a Samsung Service Center nearby.
I just can't understand why would the exactly same function work on a different app if it's hardware related. That's the reason I'm baffled with things to try to get it working.
@vrblr2405, let me know how it works out and share your thoughts, thanks!
McKis said:
vrblr2405: I used (well, tried) Always on Screen by FayaX. Just make sure you disable the built-in AOD first and give the app the permissions it's asking for. Could you also check if the edge feed is working properly and doesn't lit up the screen? You know, the rubbin' thingy If those two work properly, I'm certain we are facing the same issue
@amritpal2489 : flashing stock didn't help on my situation, but of course it's always good to try.. I've been going through different (stock)firmwares now, just to see if something would change. No luck so far, downloading third one now.
Is there more to reset than the 4 files (AP, BL, CP, CSC)? How's the re-partition in Odin?
I'm unrooted, so I'll stick with stock fw's, but I'm wondering if there is something that's not "resetting" or if I can do something more to get to start every bit and piece from scratch.
Click to expand...
Click to collapse
So I downloaded the app you said. The AOD works fine with that app. I tried a couple of other third party AOD apps. The AOD works fine - only the pixels for the clock light up. So it seems to be a software issue with the Samsung AOD.
I tried the edge feeds and it works fine. No lighting up the entire screen. The entire screen being lit up happens only with the preinstalled aod apparently.
I don't intend to root my phone at least till the warranty is valid, so sticking with the original Samsung software. Will go to a service center get this checked.
usmanyasin.bk201 said:
Can you post similar pictures with the default AOD clock widget?
Click to expand...
Click to collapse
Which is the default AOD clock?
Just a dumb thought. Wondering if the clock type might make difference. The default one is just a simple white one. Image attached.
usmanyasin.bk201 said:
Just a dumb thought. Wondering if the clock type might make difference. The default one is just a simple white one. Image attached.
Click to expand...
Click to collapse
I thought so too initially. Tried with all the different clock faces. Entire screen still lights up.
Weird. Have you ever rooted the device or is rooted right now?
Hey all.
So I got my MXP about a month ago, as my faithful Nexus 6 has long been deteriorating (#RIPshamu), and I wanted to try something a little different. I love the device and have almost gotten it tweaked and set up just the way I like it. However, I'm currently facing an issue that I can't seem to fix.
When I have a dark gray image on screen, such as the dimming when you pull down the notification bar over a white screen, the left side of my screen flickers rapidly from dark to normal, as if changing brightness. It is most noticeable on higher brightness settings, but plenty present enough on lower ones anyhow. I have made sure that no odd display tweaks in GravityBox are interfering with system presets, and I can't figure out what might be causing this.
I'm hoping it is software-related; I bought the device off-contract and without warranty, as I do with all my handsets, but if the problem is with hardware I should be able to fix it on my own so long as I know what part is causing the issue.
I'm running TruPureXMM with FrankenClark kernel. (systemless SU, magisk/systemless-xposed if any of that matters to you). Can provide logs upon request, but things seem normal to me at first glance.
Anyone else experienced this or have a fix?
I too am running TruPure and Frankenclark. I've been having a similar issue with the display, except it's the bottom half of the screen that is dimmed. I've also noticed that the 'dimming' takes on vertical lines of color depending on what the screen is displaying. The 'dimming' has consistently been transparent for me.
I originally thought that it may have started because I changed some settings using kernel adiutor, however changing those settings back did not fix the issue. I've yet to try returning to stock. I've also noticed the same display issue on boot up and in TWRP, which suggests a hardware problem, not a software one.
Some research online suggests that there is a known display bug with the Moto pure, and that the temporary fix is to reboot, but that doesn't solve the problem for me.
I think I'll try reverting to stock first, and if that is unsuccessful, then I'll try to reseat the display connector.
I've just purchased a Tab S5e but appear to be having some issues with the touchscreen. I first noticed it when scrolling, occasionally the scrolling would stop and the device would click on anything that was under my finger. I also noticed this when playing a game where a finger needed to be held on the screen, it was sometimes appear to the game that my finger was removed.
I recorded a video of what i'm experiencing here: https://drive.google.com/file/d/1-33ixSpHRijjhb8g-MNLvbjMvuPRuGrQ. I did not remove my finger at all whilst drawing in white, but gaps appear.
I guess my question is has anyone else experienced this, or could this be a hardware fault? I thinking of returning this and waiting for the S6e or similar rumoured to be out soon.
Thanks all!
I'm experiencing touch screen problems where I sometimes need to tap the display 3 or 4 times before the screen will register the touch. I've only had mine for a few days but Im thinking about returning as well.
I was going through the threads for the first time to see if there were similar issues reported or tips to minimize the issue.
After switching from the Huawei Mate 20 Pro to the Samsung S10+ and from a Huawei tablet to this I have to say I'm seriously underwhelmed with Samsung.
jhs39 said:
I'm experiencing touch screen problems where I sometimes need to tap the display 3 or 4 times before the screen will register the touch. I've only had mine for a few days but Im thinking about returning as well.
I was going through the threads for the first time to see if there were similar issues reported or tips to minimize the issue.
After switching from the Huawei Mate 20 Pro to the Samsung S10+ and from a Huawei tablet to this I have to say I'm seriously underwhelmed with Samsung.
Click to expand...
Click to collapse
Did you somehow solve the probelm?
k.bergmann2 said:
Did you somehow solve the probelm?
Click to expand...
Click to collapse
Nope. The problem doesn't occur when playing games or using apps that test the display--but does with pretty much everything else. Some apps also have very pronounced jelly effect while scrolling including the Samsung Members App--scrolling through posts has so much jelly effect it makes me feel like I'm going blind.
Earlier Galaxy Tab devices had a calibration setting to adjust touch sensitivity but the type of panel used in the S5e apparently can't be user calibrated. Some people have claimed that the pointer speed setting is the same thing but touch sensitivity and response speed aren't the same thing and increasing that setting to the max didn't improve anything for me. If you want a faster response that's one thing but if the touch doesn't even register in the first place then there isn't anything to speed up.
The game optomizer service running in the background clearly ramps up the kernel when playing games to eliminate or minimize the touch issues and display test apps are treated like games and also get the extra performance boost--but with a locked bootloader I don't think there are any user options besides not purchasing Samsung in the first place.
Would a custom rom solve this?
k.bergmann2 said:
Would a custom rom solve this?
Click to expand...
Click to collapse
I always check before buying a tablet to make sure there is developement of custom ROMs in XDA. And the first thing I do when I get one is to root and install one. Are there still "touch problems" with my ROM? Yes and no. I've noticed with this and other tablets that when the tablet first boots, there can be a lag in touch response. But I don't think it has anything to do with "touch sensitivity". I think the problem is that the OS is still "setting up" and just isn't ready to accept touches. (Try it on a Win 10 box. There is a terrific delay between the time the desktop screen first appears and the time it is ready.) This can also be true of apps. The screen can display before the app is ready for input. IMNSHO, I think some people just love to find reasons to knock "the vendor they love to hate".:crying:
Since I bought this tablet, I noticed that issue, the screen detects the touch, but it does not perform the action I want, open an app, select something,etc. I learned to live with it, but that is annoying !!, I installed a Custom ROM specifically [ROM] [UNOFFICIAL] [gts4lvwifi] [10] LineageOS 17.1 and I can confirm that the issue disappears, the problem for which I returned to STOCK, is the cut down quality of Amazon Prime Video, Netflix, because Widevine Level certification . and now in STOCK, I lost Samsung PASS, because it detects that I have the rooted device. fyi, my model is SM-t720.