Hi
on the new 4.4.3 roms from ARHD and Maximus i get the glitch shown in the picture.
Does anyone know why ?
At first i flashed the rom with the 1.54 firmware. then i noticed the glitch. then i updated the firmware and installed the rom again with full wipe .
but the glitch still persists.
does anyone how i can get this fixed ?
thanks
i mean the grey frame around the settings ^^
i have the international phone
What has this got to do with the camera?
the glitch only appears in camera
Related
Hi @all,
i tried to find a solution for my problem, but i still couldn't find one.
My Desire HD:
ROM: CoreDroid HD GB 2.3.3 V5.0 & FROYO V3.3
Android Version: 2.3.3
Sense Version: 2.1
Baseband: 12.28e.60.140fP_26.04.04.17_M2
Kernel Version: 2.6.35.10-g1418c33
Software Number: CoreDroid Desire HD V5.0
My Problem:
I flashed my original ROM with the CoreDroid HD GB 2.3.3 V5.0. Everything works fine, except the camera. If I try to make a picture, it seems, that the color depth is like 8bit. -> See attached picture.
Flashing another ROM like RCMixHD_v5.6_ORG -> same problem.
Is there still existing a thread for this Problem or does some knows what i can do?
Greetz Andy
That looks awesome
A question: Does the live view of the camera show the same picture? Or is it correct and only changes when saving?
Anyway I would recommend a full wipe & reflash of the ROM. If that doesn't fix the problem, there might be a serious problem.
The picture looks also on live view so bad.
I tried different ROMs and for wipe datas i allways used the Full_wipe_1.3.zip
I don't think that it's a hardware problem, because with the original ROM it allwaxs worked fine before i flashed.
I did following things:
- had original ROM
- downgraded from Baseband 1.75.x to 1.32.x (followed Forum Thread HOWTO...)
- Radio S-OFF and ENG S-OFF
- Flashed new ROM CoreDroid
- Radio Update to 12.28e.60.140fP_26.04.04.17_M2
I hope this helps....
Thanks
Did you already try other ROMs? It might fix the problem, if you do a full wipe and flash a different ROM, if it is ROM specific.
Have you already tried to go back to stock ROM and checked whether the problem persists?
Yeah, i tried the RCMix ROM and the Revolution HD ROM.
I didn't try stock rom yet. Didn't still found the thread with stock ROMs, so, don't know where to download from.
Does someone knows the title of the stock ROMs Thread?
Its definetely a ROM issue . So my suggestion to you is :
- Either the issue come from not properly functioning ROM or not properly functioning KERNEL . By re-flashing them , I guess you would managed to fix the problem .
- If you have made a BACKUP before flashing your new ROM , you should just restore your previous ROM and maybe the issue would disappear .
Ok, so i'll make a Kernel Update and try another ROM or Stock ROM (tomorrow) and then post you my results.
I hope that works
I die a kernel update, Radio Update, flashed stock rom 1.32 but this didn't fix the Problem.
Any other ideas that can be a solution für my Problem?
Hi,
I have the exact same problem with my DHD. Was a solution ever found?
For me, 'till today, sadly not
I think the camera sensor is busted. If you already flash lots of different roms and still not fixing it, best probable guess would be the hardware itself.
HTC M8 international .. rooted and installed CM11 for 3 weeks .. i decided to revert back to i flashed latest stock the problem is the camera quality sucks so blurry same as it was on cm11 .. i compared with another m8 .. i definitely have problem with mine ... is there any chance that cm11 did something with the camera firmware ? i flashed 2 stock roms with same problem ?
is there any way to flash camera firmware or something ?
So you noticed that the camera was blurry, suspected it was CM11, ruled out that it was CM11 by flashing stock, and now you're still asking if it was CM11?
I'll ask you a question: Do you think it's possible it wasn't caused by CM11?
Hello everyone,
I'm posting on here because I can't find any solution to my dilemma which I am sure that other people in the AOSPA legacy community have also experienced. I have been using Paranoid Android on my T989 since the 4.4.3 update and I have regularly updated my roms since then. Somehow ever since I updated my phone to 4.5 beta 3, something prevents me from being able to hear or be heard during regular phone calls around an hour after I restart my phone.
I have tried everything to try to make my phone back to normal, I have updated my versions of AOSPA, I have downgraded to stable versions, I have gone to a debloated stock rom (which worked perfectly fine but who likes touchwiz android 4.1.2?) and back to AOSPA, I tried the latest Carbon nightly rom and the problem persisted, I have wiped my internal memory, cache, davlik, etc. multiple times. I am at a total loss as to what I should do to fix this issue. I'm currently running it on 4.6 beta 1 and I still have the issue.
I really love my GS2 and I don't want to part with it or have it running stock. Please help me.
I really appreciate it,
Chris
I've had the same issue , I was running the latest liquid smooth rom . I just flashed back to stock using Odin and all is fine on the stock rom . I just rooted again and am hesitant to install another kitkat rom for fear of this calling issue ........ Anyone else with this problem ?
Playnhooky said:
I've had the same issue , I was running the latest liquid smooth rom . I just flashed back to stock using Odin and all is fine on the stock rom . I just rooted again and am hesitant to install another kitkat rom for fear of this calling issue ........ Anyone else with this problem ?
Click to expand...
Click to collapse
I am also getting this problem on Slim 7.8....must be an audio-caf issue....Can someone go back to an old KK rom (one from earlier months) and see if they experience the same issue? Preferably cyanogenmod
I flashed to stock rom via oden and spent the weekend with the phone and all was good , I flashed to the latest cm-11 with no addons , stock cm-11 kernal and after an hour or so I lost call audio again . We must have done something to the phone in a previous rom cause not many people are having this issue . Now I have flashed about 75 different roms with no issue , I hope someone finds the problem cause I'm not to keen on the stock rom !
I've seen posted that snapchat was the cause of the no call audio problem we are having , I flashed the latest liquid smooth rom last night , download all my apps that I usually do except snapchat and I've had no issues with the calling bug . All is working great .
Hey guys,
I've been trying to remedy this for a couple weeks now and am having no luck at all. The problem first started after updating from stock 4.1.2 to Slimkat 4.4.4. I'm rooted and I couldn't update over Kies, so I went straight to custom.
The Rom in general is fantastic and I would have liked to continue using it but in third party apps (snapchat) the front camera gave has the wrong aspect ratio, resulting in a stretched image and being ultimately unusable. I use snapchat a lot, and this was a dealbreaker for me. I asked in the qa thread, no reply so I tried others. The normal front camera works fine.
I've been flashing roms like crazy trying to find ones that worked for me, and I've found that the only ones that work are samsung based touchwiz ones.
I've googled around and the resounding answer is that it shouldn't be happening after CM updated, but every CM based rom results in the same issue.
I really like CM and it's derivatives and I'd like to go back to using it. Not a fan of touchwiz.
I've been through (in order):
Stock 4.1.2 (everything worked fine)
Slimkat 4.4.4 (fantastic, camera problem)
Dirtyunicorn (fantastic, camera problem)
CarbonRom (fantastic, camera problem)
CM11 (fantastic, camera problem)
AOSPA 4.6 (fantastic, camera problem)
Liquidsmooth 5.0 (favourite, but same front camera distortion)
Stock 4.4.2 (everything works, still touchwiz)
Likewise S5 4.4.2 (everything works, awesome rom, currently using)
if I try back to AOSPA 4.6 and same problem as before occurs
Every time it's a full wipe, fresh gapps install, etc
Thanks in advance.
E: All Rom versions are the current stable release as of about a week ago.
E: Using the current TWRP now, was using the current CWM touch up until I got a bootloop and had to odin in twrp to fix it.
Bump?
dr-salt said:
Bump?
Click to expand...
Click to collapse
just a real shot in the dark , but tried clearing cache in snapchat ; or uninstalling then reinstalling. or if have tibu then restore from 4.1.2 when was working. is there a Q&A for snapchat ? sorry dont have more , probably already tried these. ¿
or here is a different version/style , dont know if it would make a difference tho.
http://forum.xda-developers.com/showthread.php?t=2318103
"all I can really do , is stay out of my own way and let the will of heaven be done"
Hi there, I've try many android 6.0 ROM on my LG F180 (Korean version Optimus G). Seems like everyone of them's rotation function is not working. If I flash back to 5.X rom or kitkat roms. Then it gets back to normal. Does anyone got the same problem? Does anyone know how to fix it? Or I did something stupid? Thanks!
Mine is working just fine with Nitrogen OS (E975)
Hi there!
I am having these issues ever since I flashed 5.1 unofficial CM12. The rotation and auto-brightness went broken. Here's what helped recently:
- did a backup of my ROM in TWRP
- plugged the phone to a PC and got all my data properly copied, including the TWRP backup (it turned out to be essential, but that's just my fault)
- downloaded original KK firmware for my phone edition, also downloaded LGFlashTool 2014
- went back to stock using instructions from XDA
- rooted again and got TWRP recovery up and running
- did a full wipe, yes, including internal storage (yet I don't know if you need this, I just went for it)
- flashed the ROM I chose (im my case it was the CM12 backup I had cause of gapps issues with 6.0)
Don't know why but the sensors worked perfectly for me at that moment. I have broken them again by flashing another custom ROM over the CM12 and today I am going to give it another go.
Also, while browsing XDA I came across various posts stating that when you downgrade to stock or actually even another ROM based on official KK and only then flash the custom ROM it should all work again. In my case it seems like a coincidence, or the internal storage wipe worked miracles.
Good luck!
Mine is working. Did you tried the XenonHD 5.11 or the XenonHD 6.0 rom?
got the same problem
rext3r said:
Mine is working. Did you tried the XenonHD 5.11 or the XenonHD 6.0 rom?
Click to expand...
Click to collapse
I did try on XenonHD 6.0 rom, but the rotation still doesn't work. All others Kit Kat or Lollipop ROM are fine for me. BTW, Are U having F180? or E975?
kitty_kitty said:
I did try on XenonHD 6.0 rom, but the rotation still doesn't work. All others Kit Kat or Lollipop ROM are fine for me. BTW, Are U having F180? or E975?
Click to expand...
Click to collapse
I've got the E975.
Did you do a full wipe?(dalvik cache , etc..)
I think you did , because you tried everything , but maybe not
I've got a massive battery drain issue with 6.0 Xenon HD. (50-70% overnight)
I've installed all the same apps as on my previous rom.(1-2% overnight)
Anyone else?
how about the camera? do you are able to do photosphere or panorama pictures with google camera app??