Develop Bugs

[Q] Camera issue help

Does anyone have any camera issues no matter what ROM they flash (including the original out of the box stock froyo 2.2 ROM)? It seems whenever I take pictures, the LED flash from the camera lights up first but the picture taken is delayed approx. 2 seconds which is right when the LED flash shuts off making the picture taken dark. I've tried to leave the flash on but it refuses to. The best luck of having it taking pictures with the LED flash simultaneously was when I was on the out of the box stock 2.2 froyo ROM but even that sometimes had the same issues I'm having now. Anyone else having these problems or know a solution to enlighten me? Thanks.

Coak5 said:
Does anyone have any camera issues no matter what ROM they flash (including the original out of the box stock froyo 2.2 ROM)? It seems whenever I take pictures, the LED flash from the camera lights up first but the picture taken is delayed approx. 2 seconds which is right when the LED flash shuts off making the picture taken dark. I've tried to leave the flash on but it refuses to. The best luck of having it taking pictures with the LED flash simultaneously was when I was on the out of the box stock 2.2 froyo ROM but even that sometimes had the same issues I'm having now. Anyone else having these problems or know a solution to enlighten me? Thanks.
Click to expand...
Click to collapse
Maybe you should try to autofocus first and then take pictureб?
Sent from Mars

jecustoms said:
Maybe you should try to autofocus first and then take pictureб?
Sent from Mars
Click to expand...
Click to collapse
Even autofocus first does not work. The picture is taken directly after the LED flash turns off.

Strange dimming bug...

I've been having a a bit of a strange bug with my GN...
When i unlock and open for instance messaging app to look at SMS's...i see the screen dim a lot and come back again. If i open up settings screen dims like an LCD panel with no backlight. If i click back, screen comes back again or if i lock and unlock screen, all is OK.
I've done some fiddling about and it only seems to happen on apps with white backgrounds i.e. messaging, gtalk, gmail etc. If i open dark background apps i.e. phone app, settings or gallery it doesnt happen.
But for all those other apps when i launch them, screen appears to flicker (dim) and come back again...messaging is the only one where it dims completely in settings.
Has anybody else noticed this?
And more wierdness...in the messaging settings menu, if i scroll to the bottom the brightness goes completely and then comes back again, and starts flickering a lot...
maybe i'll try turning off auto brightness and see if it still does it...

I've had a couple of customers come in already saying they always felt like the brightness was on notch to low sometimes or just very dim. Considered it user error, just got my nexus in the mail and after set up brightness just dropped randomly to almost nothing...
soooo guess we'll see

ah well still did it with auto brightness off
wonder if i've got a borked phone or if others do it and they just dont notice...
EDIT: if anybody's interested in seeing it i've just uploaded a vid here
And i know i still have the front screen cover on...havent wanted to take it off yet!

Restored stone to factory settings this morning and i've not installed anything else or changed any settings (other than turning off NFC, wifi and mobile data)...and it still does it.
Think i might have a defective handset then...annoying though, it's only 2 weeks old but the place i got it from states
Phones that are faulty out-of-box as determined by our warehouse can also be returned for an extended period of up to 7 days from date of delivery.
Click to expand...
Click to collapse
So if i can't get a replacement out of them, what are the odds of samsung replacing it for a new handset?

Hmm pretty sure it's hardware, set desktop picture to something quite bright/white and sure enough when i was scrolling through the 5 homescreens brightness was flickering from one to the next...
What are the odds of getting a replacement handset after 2 weeks? :|

I had this same issue when I got my phone. I had a yakjuwx build in my phone.
Ever since I flashed over to yakju I haven't experienced it.
You may want to check and see what you have.
Sent from my Galaxy Nexus using xda premium

El Daddy said:
I had this same issue when I got my phone. I had a yakjuwx build in my phone.
Ever since I flashed over to yakju I haven't experienced it.
You may want to check and see what you have.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Hi, thanks for the reply.
Mine is already running yakju from new :/ I might try re-flashing it tonight though just for the hell of it.
Is this not a bit weird that it happens only on bright/wight screens/backgrounds/apps? And that it's suddenly fine when you lock the screen...
If it was a laptop i'd be fitting a new panel to it but then i dont know what amoled's are like (especially combined with a light sensor)

Nope, still does it after a re-flash :/

Got a replacement handset now...
Like my first one, it was one of the early opened and re-sealed with samsung label handsets (and they hadnt put the battery door on properly, fingerprint on the SIM card slot!)
But anyways, waiting for the OTA update on this one
It's obviously running ITL41D and no OTA has come through yet whereas on my first handset it came through pretty much straight away.
Would the fact i've already had the OTA on one handset stop this coming through? :|

[Q] Colored snow, screen distortion, earphone speaker not working on Tilt2

Hey everyone,
I'm currently running the latest Jackos and I believe everyone was fine with the speaker you hold to your ear in conversation until about 2 weeks ago. Maybe a week or so after I installed the newest Jackos. Now I can't hear anything on it, but the microphone works fine. Speakerphone works fine, and my bluetooth earpiece works fine. I've searched for help on this and can't find anything to fix this problem.
The other problem is right when I boot the phone, instead of getting the black screen with the red diagnostic text, I get a white screen with colored speckles all over the screen. The speckles don't move at all and if I let it sit for 20 seconds or so, it will then show the HTC logo on black and continue booting. I can't get into the bootloader, I can't hard reset the phone, etc. Any ideas how to fix this? I haven't tried flashing the same/another ROM yet, but I don't know if that's even possible with this snow screen problem.
I've run Task29 and all the usual stuff every time I've flashed and I have never seen this happen until a couple of weeks ago. It does it NEARLY every time I soft reset or shutdown and boot or pull the battery and boot. The battery charges fine and it runs fine otherwise.
The screen will get random glitches in it, even when the battery is full and it makes me suspect maybe the battery's going bad but it'll run all day without problems and it doesn't get warmer than usual or anything like that.
Also, sometimes it says there's no SIM inserted and I've pulled it out, the contacts are nice and gold and nothing seems wrong.
Any ideas?
My sig is out of date but I have to head out right now and can't switch it yet, but it's the latest Jackos with 6.5.
Thanks,
Eric

I would flash a different/stock ROM and see if anything changes.
If no, hardware problem. If yes, software problem .
You seem to think you cannot, but AFAIK if you can task29, you can flash a ROM. Either way, putting an nbh on the SD card and doing power+vol up+reset should work regardless, unless the device is really bricked - in which case it wouldn't be booting.

Okay thanks, I'll see what I can do with it.. It does boot fine, though for a week I thought it was bricked because of the snow, but I decided to just let it sit for a week and gave it a shot, and poof! no snow on the first boot. It had the regular red text on black. Then I reset it from the slide to reset menu item and it went to snow again. I let it sit there and about the duration that it would be on the diagnostic screen, it was snow, then magically showed me the HTC logo and booted normally.
So it seems to me that it somehow doesn't want to show diagnostic info but does everything else.. So maybe the bootloader mode IS working, I just can't view that. I'll see what I can do.
Does the screen corruption/no sound in earpiece seem like a ROM issue, or battery related, or phone going bad problem to you?
And I've been looking for a while trying to find a suitable replacement, but haven't seen anything that I really find appealing (either in Android or WP7).. Any thoughts on that?
Thanks again,
Eric

shep2112 said:
So it seems to me that it somehow doesn't want to show diagnostic info but does everything else.. So maybe the bootloader mode IS working, I just can't view that. I'll see what I can do.
Click to expand...
Click to collapse
Flash stock, it re-flashes everything... Make sure it works, then flash back to Jacko's.
shep2112 said:
Does the screen corruption/no sound in earpiece seem like a ROM issue, or battery related, or phone going bad problem to you?
Click to expand...
Click to collapse
This is what we're trying to troubleshoot .
shep2112 said:
And I've been looking for a while trying to find a suitable replacement, but haven't seen anything that I really find appealing (either in Android or WP7).. Any thoughts on that?
Click to expand...
Click to collapse
Talk about loaded questions! I haven't found anything that's appealing with a hardware keyboard yet... The supposed TP3 (on Sprint it's the "Arrive"...) was a real disappointment.
MT4GS looks decent, if you can live with tmo...

Thanks for your replies, I'm going to try to flash to stock in a little while and see how that goes.
The new Glide phone that AT&T has sounded promising until I read a review of it. Slow camera, 480x800 on a larger screen, etc. It didn't seem as cool as I had hoped it would be after that.
I'll write back with my progress or lack thereof with this TP2.
Eric

I installed HTC's official AT&T ROM and the screen corruption seems to be less extensive but looks different too. The snow at startup is still present though.
There was a radio that came with Jackos ROM, is there any chance that's to blame? Though it worked fine for a couple weeks before these weird screen things started happening.
I haven't tried making a voice call yet to test the earpiece/earphone/loudspeaker or whatever the proper name is for it but since nothing else is really 'fixed' I'm not sure it will work either.
Thanks,
Eric

shep2112 said:
I installed HTC's official AT&T ROM and the screen corruption seems to be less extensive but looks different too. The snow at startup is still present though.
There was a radio that came with Jackos ROM, is there any chance that's to blame? Though it worked fine for a couple weeks before these weird screen things started happening.
I haven't tried making a voice call yet to test the earpiece/earphone/loudspeaker or whatever the proper name is for it but since nothing else is really 'fixed' I'm not sure it will work either.
Thanks,
Eric
Click to expand...
Click to collapse
The stock ROM should've come with a radio as well...
task29 & flash stock? Otherwise perhaps you have a hardware problem... I don't know what to make of this snow .

The earpiece/loudspeaker thing isn't fixed either. I'll try a Task29 tomorrow or tonight if I can't sleep (thinking about this stupid phone! ) and then flash this ROM again and see what happens and let you know.
Thanks again

Screen unresponsive for a minute after unlocking

Any time the screen turns off and I turn it back on, I have to wait 30 seconds to a minute before the touch screen is responsive at all. I've tried using my fingerprint or removing all screen security and that doesn't seem to make a difference. Has anyone else run into a similar issue? Any idea on how to fix it?

zebinadams said:
Any time the screen turns off and I turn it back on, I have to wait 30 seconds to a minute before the touch screen is responsive at all. I've tried using my fingerprint or removing all screen security and that doesn't seem to make a difference. Has anyone else run into a similar issue? Any idea on how to fix it?
Click to expand...
Click to collapse
What android version are you running? Do you have many apps installed? Have you tried restoring back to factory defaults?

I believe it started after upgrading to 9 manually a few weeks ago. But I've tried a few different ROMs with the same situation. I have not rolled back to 8 to test that yet. It happens right out of the gate without installing any additional apps as well. I've done multiple full wipes, including unlocking the bootloader that for sure wiped everything with no change to the situation.

zebinadams said:
I believe it started after upgrading to 9 manually a few weeks ago. But I've tried a few different ROMs with the same situation. I have not rolled back to 8 to test that yet. It happens right out of the gate without installing any additional apps as well. I've done multiple full wipes, including unlocking the bootloader that for sure wiped everything with no change to the situation.
Click to expand...
Click to collapse
Fastboot upgrade? If not, i'd download 9 stock RETAIL and just flash it all with fastboot

Ok, I'll try that when I get a chance. we'll see if it works.

marcost22 said:
Fastboot upgrade? If not, i'd download 9 stock RETAIL and just flash it all with fastboot
Click to expand...
Click to collapse
I just re-flashed via fastboot 9 stock RETAIL found here. Looks like I'm still having the same issue as before with the touch screen not being responsive after turning the screen back on. Even if it's only been off for half a second, it will still not be responsive for a minute
Any further ideas? Or is there a better location to get the RETAIL image for XT1710-01?

zebinadams said:
I just re-flashed via fastboot 9 stock RETAIL found here. Looks like I'm still having the same issue as before with the touch screen not being responsive after turning the screen back on. Even if it's only been off for half a second, it will still not be responsive for a minute
Any further ideas? Or is there a better location to get the RETAIL image for XT1710-01?
Click to expand...
Click to collapse
This is gonna sound weird, but have you changed your screen at all?

marcost22 said:
This is gonna sound weird, but have you changed your screen at all?
Click to expand...
Click to collapse
Actually, yes. Just after getting the phone, it was dropped and the screen had to be replaced. The fingerprint sensor has been loose ever since then too. But this was never an issue until flashing a new ROM

zebinadams said:
Actually, yes. Just after getting the phone, it was dropped and the screen had to be replaced. The fingerprint sensor has been loose ever since then too. But this was never an issue until flashing a new ROM
Click to expand...
Click to collapse
did you have someone else replace your screen? If so, and it might sound weird, they might have installed an LCD screen instead of OLED; and then modified the stock rom for that. You might not know, but OLED and LCD have very different power profiles, so when turning LCD on you can just blast it, meanwhile oled you need to slowly bring the power up. This is what might be causing your issues

marcost22 said:
did you have someone else replace your screen? If so, and it might sound weird, they might have installed an LCD screen instead of OLED; and then modified the stock rom for that. You might not know, but OLED and LCD have very different power profiles, so when turning LCD on you can just blast it, meanwhile oled you need to slowly bring the power up. This is what might be causing your issues
Click to expand...
Click to collapse
Yeah, I had someone else install the screen for me. How would I go about checking if its LCD vs OLED? And do you know what would need to be modified in order to fix it if it is LCD?

zebinadams said:
Yeah, I had someone else install the screen for me. How would I go about checking if its LCD vs OLED? And do you know what would need to be modified in order to fix it if it is LCD?
Click to expand...
Click to collapse
You would need to remove the screen. Otherwise you can use something like AOD and check if the whole display lights up vs only the clock or whatever. On an LCD screen the whole display will light up a tiny bit vs complete black on OLED.
You would need to modifiy the dtb's and kernel, but it's something i would be able to do for you

marcost22 said:
You would need to remove the screen. Otherwise you can use something like AOD and check if the whole display lights up vs only the clock or whatever. On an LCD screen the whole display will light up a tiny bit vs complete black on OLED.
You would need to modifiy the dtb's and kernel, but it's something i would be able to do for you
Click to expand...
Click to collapse
It looks to me like OLED to me with only the clock lighting up. I could still take the screen off at some point to verify if needed.
Thanks for all of your help by the way

zebinadams said:
It looks to me like OLED to me with only the clock lighting up. I could still take the screen off at some point to verify if needed.
Thanks for all of your help by the way
Click to expand...
Click to collapse
I don't know if it's the reflection, but is there some bleed around the clock? Like is the dark areas lighter compared to the rest of the screen?

marcost22 said:
I don't know if it's the reflection, but is there some bleed around the clock? Like is the dark areas lighter compared to the rest of the screen?
Click to expand...
Click to collapse
I think it's just the reflection? Here's a shot of my Nexus 6p right beside it and I think they look basically the same.
The phone is used almost exclusively for kids videos so it's not the end of the world if I never get it fixed, but at the same time, it would alleviate some frustration when I'm helping my daughter turn a show on.

zebinadams said:
I think it's just the reflection? Here's a shot of my Nexus 6p right beside it and I think they look basically the same.
View attachment 5544389
The phone is used almost exclusively for kids videos so it's not the end of the world if I never get it fixed, but at the same time, it would alleviate some frustration when I'm helping my daughter turn a show on.
Click to expand...
Click to collapse
Yeah, to me it still looks significantly brighter around the clock

marcost22 said:
Yeah, to me it still looks significantly brighter around the clock
Click to expand...
Click to collapse
Ok, I'm willing to try modifying the ROM if that'll get rid of the stupid touch screen delay. How difficult is it? I know you said you would be willing to do it for me, but if it's not something that will persist through an update (I had been running AICP) and it's something that I could learn to do, all the better. If that's not realistic, that's fine as well.

zebinadams said:
Ok, I'm willing to try modifying the ROM if that'll get rid of the stupid touch screen delay. How difficult is it? I know you said you would be willing to do it for me, but if it's not something that will persist through an update (I had been running AICP) and it's something that I could learn to do, all the better. If that's not realistic, that's fine as well.
Click to expand...
Click to collapse
[REFERENCE] How to compile an Android kernel
Introduction Hello everyone, I will be going over how to compile a kernel from beginning to end! Prerequisites: A Linux environment (preferably 64-bit) Knowledge of how to navigate the command line Common sense A learning spirit, there will be...
forum.xda-developers.com
Is a great guide, you'd need to follow the clang guide tho, as our kernel IS clang-compiled, and i recommend repacking the boot.img
You'd need to change this line
kernel_motorola_msm8953/msm8953-albus.dtsi at 7befedacd91b84ed737b691671c088c89e394f66 · AICP/kernel_motorola_msm8953
Contribute to AICP/kernel_motorola_msm8953 development by creating an account on GitHub.
github.com
In your source to be
qpnp,qpnp-labibb-mode = "lcd";
If i'm right, after doing that and flashing it the issue will be fixed. Otherwise when you try to turn on the display it will cause a kernel panic
You would need to reflash this boot.img after every update, and redownload sources everytime i do something to kernel.

Question High brightness mode for HDR not working

Hi all, this may be a dumb problem to have but a few weeks ago, I started watching an HDR video on YT and noticed the HBM didn't kick in. Since then, I have tried everything to fix it that I can on a non-rooted phone to no avail. I opened a support case with Google, they suggested the standard factory reset which didn't work as I told them it wouldn't. After that, they requested a bug report in which I did send. Without any explanation, they offered to replace the phone. I asked for details on the bug report and what was wrong but they ignored my request. I got so annoyed I declined the replacement and said I would just trade the phone for a pixel 7 which I did order and receive.
First thing I did when I got it was test HDR content and it worked as it should by kicking in HBM. The problem is, I am a victim of a poor screen on the 7 with washed out colors and a greenish yellowish tint. Now I'm back to the 6 pro after ordering a replacement for the 7 and back to trying to figure out why HBM isn't working.
I want to try to figure this out as I'm pretty sure the replacement 7 pro I get will have the same drab screen colors so will likely just return it all together and stick with the 6 pro.
Anyone have any suggestions on how to fix this? I think HBM is a function of the kernel so I thought perhaps reflashing the kernel could fix it but I'm not sure and I'm not rooted (can't bc I use my phone for work and some of the apps we use for business detect rooted phones and deny use). I have used the android flash tool to do a full clean flash of A13 when it first came out so I'm guessing the kernel would have been updated then. Perhaps that broke it? I'm not sure when it did but I know HBM worked at some point in the past. I used the android flash tool like 4 or 5 times until it seemed all the weird quirks were mostly ironed out (I was one of the people posting in the thread about A13 weird issues when it first came out like battery drain, etc).
Anyone come across this and know how to fix?

Not sure of this could help settings display then colours either try natural boosted adaptive maybe they have something to do with the HDR

liggerz87 said:
Not sure of this could help settings display then colours either try natural boosted adaptive maybe they have something to do with the HDR
Click to expand...
Click to collapse
The color profile has nothing to do with this bc when HDR kicks in, it super saturates the colors no matter what profile you're on.
I am still trying to find out if anyone else has this issue and if so, is high brightness mode a function of the kernel or something else in the software?

jrg67 said:
The color profile has nothing to do with this bc when HDR kicks in, it super saturates the colors no matter what profile you're on.
I am still trying to find out if anyone else has this issue and if so, is high brightness mode a function of the kernel or something else in the software?
Click to expand...
Click to collapse
True I thought it might have had something to do with it least that's got ruled out sorry I'm no help