Hi,
anyone had photo problems after the latest O2 Rom upgrade.
I seem to have 'lines' at the top (or right depending on orientation) of the photos
Thanks
Yes I'm now having exactly the same problem after the recent O2 ROM upgrade.
In landscape mode, there are now lines of what can best be described as pixellated noise evenly across the top of the picture.
In portrait mode, there is a wedge of such noise down the right side, which is very thin at the top (literally starting in the top right corner) and then becomes progressively wider as it goes down the screen, to the point where its about 1/3 of the way across the screen at the bottom of the picture.
Oddly, in the preview just after you've actually taken the picture, the noise isn't visible, it all looks fine. But when you view the images they all have the effect.
Hi - I upgraded my O2 HTC HD2 from 1.43 to the stock 1.72 yesterday and don't experience any issues like this with the camera. There doesn't seem to be a pink hue on the images either. Which is good.
The one problem I've still got with this ROM is the Sense music player, which still has trouble displaying all the albums when it is first opened. Sliding over to the Music tab in Sense results in a blank screen for about 10 seconds before the album art, track details and play controls appear. Slide out to another tab, and slide back, and I get the same delay. Have installed HTC's Music Stability update of 27th April 2010 but still get the same delay. Oh dear!
Further to yesterdays post, I think my problems may have been caused by an incautious restore (using Sprite, my problem, not its) after the 1.72 firmware upgrade.
While I had tried to be careful not to restore anything from the backup made before the ROM upgrade, that might have caused conflicts, obvioiusly I wasn't entirely successful in that!
So today I did a hard reset. In that fresh configuration, the camera worked fine again, with no trace of the pixellated corruption. Which suggested clearly that it was indeed the restore that had done the damage.
I then spent an hour or so deliberately reconfiguring things manually, one by one, back to the way the phone had been before the 1.72 firmware upgrade. Checking all they way, each time I installed or configured something, that it didn't interfere with the camera.
At the end of which, I've managed to get everything set back as it was before the 1.72 firmware upgrade and the camera is still taking good pictures.
What I still don't know though, is exactly what it was that caused the conflict and picture corruption. Other than this time through I obviously didn't apply any of the HTC updates that are specifically for ROMs older than 1.72.
I'm guessing I must therefore have had just such an update that I'd fiorgotten about, that was integrated into the restore I applied, which had been made with ROM 1.43 and which thus caused this issue.
Lesson learned!
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.
Hey everyone, thought you all might be able to help with an issue I'm having. Ever since I've upgraded to the c900b395 update, which I did OTA rather than a full install my light sensor is gone. I've rolled back, changed to arrow and tried to flash stock with no luck. When I install sensor reading apps the light sensor doesn't even show up as being in the phone.
It's like I'm missing a driver package or something. I forgot how convenient having auto brightness and the phone screen turning off during a call was. Any ideas? The original firmware was a New Zealand spark rom but I clean degraded it.
Did you find a fix?
Have the same problem
Just bought a Ze552kl off Amazon for a pretty sweet price of ₹16,725 (£191.14/$256.16) couple of days ago.
Though it was running Nougat 7.0 right out of the box, there were some minor UI bugs like on pulling down the notification panel it'd sometimes get stuck and the only way out would be to get to the home screen.
An update fixed that, but scrolling lag still persisted.
To rule out hardware issues I performed touch tests and though it managed to pass, it was difficult. I had to run it multiple times because it involved user input. It requires you to trace the boundaries of four shaded areas which are quite slim.
(Factory reset didn't seem to make a difference either)
I then tried a couple of touch calibration apps which brought noticeable improvements but it's still not enough.
So did I receive a faulty set or is it some software issue ?
Are you on the latest version of the ASUS ROM? I have a slightly different model than you, but I found the initial Nougat update to be very slow and buggy. Subsequent updates seems to have fixed most issues...
I guess, yeah, because I haven't received any more updates post the latest one mentioned on their website.
I really don't have any issues with this ROM except for the not-so-great touch response. It is a bit laggy, but that's all.
EDIT: Oh, and the Firmware is WW-14.2020.1708.56