Camera not working after repair on jellybean roms - Sprint HTC One (M7)

i hope someone can help me with this. i have sent my HTC One back to HTC for repair and since i have gotten it back the camera no longer works on anything but kitkat. There are some roms i want to try that are jellybean such as miui. (which prior to sending it back it worked beautifully) now on the miui rom it only loads the ffc and looks terrible. on other roms it just doesnt load at all. i will attach a logcat. any help with this would be great. please dont suggest that it is a hardware defect. as stated it works fine on kitkat roms,
https://www.dropbox.com/s/f9suxolaev93e85/miuilogcat.txt

nwo122383 said:
i hope someone can help me with this. i have sent my HTC One back to HTC for repair and since i have gotten it back the camera no longer works on anything but kitkat. There are some roms i want to try that are jellybean such as miui. (which prior to sending it back it worked beautifully) now on the miui rom it only loads the ffc and looks terrible. on other roms it just doesnt load at all. i will attach a logcat. any help with this would be great. please dont suggest that it is a hardware defect. as stated it works fine on kitkat roms,
https://www.dropbox.com/s/f9suxolaev93e85/miuilogcat.txt
Click to expand...
Click to collapse
Thes same thing is happening to me..i have sent my htc one to service centre for replacement of mic btu after the day of repairing my front camera is not opening on any rom....i think they have done something to my phone..

I also sent my phone in but before JB or KK and now when i update my firmware the camera works but video doesn't. The good thing for me i guess is ViperROM has been a solid rom..

Well let's not mix this up please.
My issue is only when using a jellybean Rom that only the ffc works or the camera doesn't work at all. The camera works perfectly well on kitkat roms.
Sent from my HTCONE using Tapatalk

If you don't believe you have a hardware issue and you have the latest firmware either by ruu or other ways the only real thing you can do is wait for the next ruu or update to come out and see if that fixes your issue. I dont think (could be wrong) devs are going to fix issue for one phone. Try taking it to Sprint and see what they can do for you...

But how could it be hardware if it works on kitkat roms? If it were hardware I don't think it would work on any roms.
Sent from my HTCONE using Tapatalk

Are you s-off? When you installed JB Rom did you install the firmware from the JB update. It could be that your KK firmware is your issue.

I believe I ruud back to the original firmware when I was trying a few weeks ago I can check again when I have more time
Sent from my HTCONE using Tapatalk

I will take an educated guess on experience. Chances are that you got a new camera with that new camera is a completely different camera that doesn't have JB drivers, only KK.
Also can see Sprint/HTC (end even Google) that KK is the standard today, that JB is outdated and your phone probably came back from the repair center with KK on it.

I was wondering if that could be it. You are correct it came with kk on it after the repair job.
Sent from my HTCONE using Tapatalk

Related

Strange camera problem

Whenever I flash a custom ROM from stock eclair, the camera just doesn't work half the time. The camera app would open and it would just be a blank viewfinder. I found that closing and reopening the camera like 3 or 4 times fixes it temporarily. When I leave the phone sitting for a while and try to open the camera, it always opens with the blank viewfinder.
I tried searching about this but I guess it isn't a common issue at all, so if anyone can offer any advice I'd appreciate it
drktigger said:
Whenever I flash a custom ROM from stock eclair, the camera just doesn't work half the time. The camera app would open and it would just be a blank viewfinder. I found that closing and reopening the camera like 3 or 4 times fixes it temporarily. When I leave the phone sitting for a while and try to open the camera, it always opens with the blank viewfinder.
I tried searching about this but I guess it isn't a common issue at all, so if anyone can offer any advice I'd appreciate it
Click to expand...
Click to collapse
Well this really depends on the ROM you are flashing when coming from Eclair, which ROM did you try, and which kernel with that?
Well, I was on Team Hacksung's ICS build 17(icy glitch v14 b6), AOKP(same kernel), Doc's Master(the kernel that came with it), and Slim ICS 3.1(the kernel that came with it). I also tried a custom gingerbread ROM which I can't remember the name of atm.
drktigger said:
Well, I was on Team Hacksung's ICS build 17(icy glitch v14 b6), AOKP(same kernel), Doc's Master(the kernel that came with it), and Slim ICS 3.1(the kernel that came with it). I also tried a custom gingerbread ROM which I can't remember the name of atm.
Click to expand...
Click to collapse
OK, I think the problem is that all of the roms you've been flashing are ics builds and all of the ics builds for the galaxy s are ported at the moment, and because they are ported they don't always work. So my guess is that your camera doesn't work because of your ics builds, why don't you try a ROM built for captivate like fasty ROM or darky ROM or even cyanogenmod7?
Sent from my SAMSUNG-SGH-I777 using XDA
I actually have tried cm7 but the camera would not open at all with that one.
Sent from my SGH-I897 using Tapatalk 2
None of the CM build are made for the captivate, try a rom built from stock and see if the issue happens on that. Maybe try legend rom from crt it is a very good rom based off of stock kk4.
Sent from my SGH-I897 using xda premium
Wdustin1 said:
None of the CM build are made for the captivate, try a rom built from stock and see if the issue happens on that. Maybe try legend rom from crt it is a very good rom based off of stock kk4.
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
I've tried flashing legend but that got me into a bootloop. I have successfully flashed Simply Stock, but I had the same camera issue.
This was a while ago, but I remember having camera problems as soon as I got the official gingerbread update from froyo. If I remember correctly the camera would always force close as soon as I opened it.
you must have a hardware problem.
camera works fine on ICS for the past 2 months at least. nothing but bad advice in this thread. i am running AOKP right now. used camera today.. used it now.. it works.
cm camera works fine, cm IS built for captivate, or in those thoughts... CM isnt built for any phone..??..
Well, I should also make it clear that the camera always seems to open with no problems on stock eclair or froyo, so yeah... it's a pretty strange case. I don't really want to trade everything else great about ICS and go back to froyo because of my ocd lol.
cm camera works fine, cm IS built for captivate, or in those thoughts... CM isnt built for any phone..??..[/QUOTE]
That's kind of what i meant lol its not a stock build.
Sent from my SGH-I897 using xda premium
Um, so is it unlikely I'll ever be able to fix this issue then?
Had same problem with every ICS rom I've tried. Seems camera only works with LCD density set to 220, at least on my phone. Check if it makes a difference on your phone. Under Settings > ROM Control> General UI> LCD Density

[Q] Problems with call quality

Hello XDA community!
I'm a new user here and fairly new to rooting my HTC IncS.
Well anyway a few days I rooted my phone and flashed it with the latest lacoste 4.1.2 mod. All is running brilliantly except one thing.
When I first tested calling function I was told that i'm echoing and that the background noise is terrible, then I saw that noise suppression setting was off. After I turned it on everything seemed normal again.
Although today the noise and echoing was back, and the suppression was still on. I tried turning it off and it got normal again, no echo no noise.
Unfortunately during the call it got worse again, just randomly, I didn't touch the settings.
I tried searching for that problem with CM10 but seems that nobody has it, can somebody help me ?
All the best,
Erlend
Try re flashing the ROM. Or try the unofficial CM10. If this problem still persists, I guess you'll have to S-OFF and flash a different radio.
Sent from my Incredible S using XDA
InsertDumbNick said:
Try re flashing the ROM. Or try the unofficial CM10. If this problem still persists, I guess you'll have to S-OFF and flash a different radio.
Sent from my Incredible S using XDA
Click to expand...
Click to collapse
Okay, ill try reflashing it tomorrow, but if I need to flash another radio, which one to choose. Im currently running 20.74.30.0833U_3831.18.00.11_M.
Is there a newer one out there for jelly bean?
Thanks,
Erlend
Well it's more dependent on the area you're staying in. I've been using the same one since gb and I have no issues.
Sent from my Incredible S using XDA
ErlendPetker said:
Okay, ill try reflashing it tomorrow, but if I need to flash another radio, which one to choose. Im currently running 20.74.30.0833U_3831.18.00.11_M.
Is there a newer one out there for jelly bean?
Thanks,
Erlend
Click to expand...
Click to collapse
Try the one in my sig, latest one.
Sent from one of the few remaining Incredible S'

Flashing 4.2.2 over 4.3

Hi guys,
I just want to ask if it is possible to flash any 4.2.2 Rom over a 4.3 one without changing the Bootloader or Modem (as far as I know kernel there are no other things updated in 4.3 except some features in stock Rom and kernel). I'm sorry if there is a thread like this one out there but I couldn't find it on my phone app
Thanks in advance for your time and help
Sent from my Nexus 4 using xda app-developers app
Now why would you do that? It's like installing windows ME over Windows 7
Sent from my Nexus 4 using Tapatalk 4
It's because I like to have all the possibilities to personalise nz phone, and Roms like MIUI won't get 4.3 support in the next time it's just my opinion
Sent from my Nexus 4 using xda app-developers app
4.3's stock kernel sucks hard. I've experienced "unexpectedly closed" errors with certain apps and the device sometimes reboots itself without apparent reason. Had to flash the latest franco's nightly kernel in order to get this faulty release somewhat stable.
Nice GoinGoogle.
deleted
It is possible with custom recovery, not possible with fastboot without updating the bootloader. You may use any modem. You need 4.3 kernel.
EDIT: my bad, it was other way around. Yes, it is possible.
4.3 stinks like hot garbage. I'm not upgrading, and I'm going to downgrade my new N7 to 4.2.2 if possible. 4.3 is like windows ME.
I still have 4.2.2 on my N4 and have only tried 4.3 on my Kindle Fire. From my experience I have little interest in upgrading my N4 for the time being, since 4.3.x will likely fix all the JSS and JWR issues.
Fatherboard said:
4.3's stock kernel sucks hard. I've experienced "unexpectedly closed" errors with certain apps and the device sometimes reboots itself without apparent reason. Had to flash the latest franco's nightly kernel in order to get this faulty release somewhat stable.
Nice GoinGoogle.
Click to expand...
Click to collapse
I think your problem is caused by your usage pattern / apps which are not updated for 4.3, combined with unstable root. Don't blame Google unless you experience the same behaviour on unrooted stock.
Sent from my Nexus 4 using Tapatalk 4
Wrong.
I experienced those crashes while on stock, even with google applications. that's a faulty release, not faulty device nor usage. for god sake, even "settings" menu has "unexpectedly closed" on me once.
Misledz said:
Now why would you do that? It's like installing windows ME over Windows 7
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
I think it'd be more like going back to Windows 7 Sp1 from Windows 8
Sent from my Nexus 4 using Tapatalk 4
I have had totally different experience with 4.2.2. To be honest I didn't like it at all. I didn't find it as "rock solid" as many other users here. (I came from Galaxy Nexus. Android 4.2 compared to really rock solid jzo54k 4.1.2 was imo buggy as hell. It didn't bring any performance boost but rather did the opposite: BT, WIFI issues, mem leak etc.) Plus I found this low touch sensitivity extremaly irritating. I use rooted stock 4.3 and so far I haven't noticed any bigger issues. Even if I do I really don't see a point to go back to still buggy 4.2.2. I think my device performs much better on 4.3. Maybe it's just a placebo effect, but it feels snappier and smoother. Just my subjective opinion.
Of course I do understand people that miss their favorite custom roms, whose 4.3-versions are still unavailable.
4.2.2 had and has clearly wifi/bt issues (major data stalls, difficulties in re-enabling bt after 20-30 hours of uptime).
These issues were solved. however, I'd expect 4.3 to be as stable as it can be, especially when it took more than 5 months for its release. Unfortunately, that's not the case. not even close, which is rather embarrassing.
I really was expecting for iOS-like smoothness and stability by now.
Fatherboard said:
4.2.2 had and has clearly wifi/bt issues (major data stalls, difficulties in re-enabling bt after 20-30 hours of uptime).
These issues were solved. however, I'd expect 4.3 to be as stable as it can be, especially when it took more than 5 months for its release. Unfortunately, that's not the case. not even close, which is rather embarrassing.
I really was expecting for iOS-like smoothness and stability by now.
Click to expand...
Click to collapse
Maybe that's been your experience but my experience has been the exact opposite. It's made my N4 even more of a pleasure to use. It's smoother, snappier, and battery life is amazing. Mind you, I've never really had any problems with 4.2.2 except maybe GPS locking problems, which 4.3 solved. The only real problem with 4.3 is this whole JWR/JSS nonsense.
Fatherboard said:
4.2.2 had and has clearly wifi/bt issues (major data stalls, difficulties in re-enabling bt after 20-30 hours of uptime).
These issues were solved. however, I'd expect 4.3 to be as stable as it can be, especially when it took more than 5 months for its release. Unfortunately, that's not the case. not even close, which is rather embarrassing.
I really was expecting for iOS-like smoothness and stability by now.
Click to expand...
Click to collapse
Not sure what's going on your end but my phone has been rock solid with no FCs at all since upgrading to 4.3 using the factory image (I never go the OTA route)
In case you're both running a stock 4.3 (unrooted), you're more than welcomed to run "angry gran run - running game" by ace viral and watch it boldly & proudly crash. If not on beginning, after few minutes. Just only one example out of many.
Tapatalked
Not sure if this is the right place but here goes.
I am on AOKP milestone 1 might update to milestone 2 soon. But what do I have to keep in mind when making the jump to 4.3? Will I be able to downgrade later without problems? I dont understand the modems and bootloader stuff. Plus if I flash 4.3 I will lose root, so how do I flash 4.3 without loosing root? do I root the phone again after flashing? or is there a shortcut?
DeepPurple15X said:
Not sure if this is the right place but here goes.
I am on AOKP milestone 1 might update to milestone 2 soon. But what do I have to keep in mind when making the jump to 4.3? Will I be able to downgrade later without problems? I dont understand the modems and bootloader stuff. Plus if I flash 4.3 I will lose root, so how do I flash 4.3 without loosing root? do I root the phone again after flashing? or is there a shortcut?
Click to expand...
Click to collapse
You can flash a 4.3 rom in recovery, but its recommended to flash radio and bootloader in recovery.
Sent from my Nexus 4 using xda app-developers app
DeepPurple15X said:
Not sure if this is the right place but here goes.
I am on AOKP milestone 1 might update to milestone 2 soon. But what do I have to keep in mind when making the jump to 4.3? Will I be able to downgrade later without problems? I dont understand the modems and bootloader stuff. Plus if I flash 4.3 I will lose root, so how do I flash 4.3 without loosing root? do I root the phone again after flashing? or is there a shortcut?
Click to expand...
Click to collapse
Android 4.3 ROMs require radio version .84 (or a hybrid 27/84 or 33/84 radio) and bootloader version makoz20i. As Thibaultvw points out radio version .84 and bootloader version makoz20i are both available as flashable zip files and should both be installed before installing a 4.3 based ROM. In addition, Android 4.3 requires SuperSU version 1.51 for working root privileges.
After upgrading the radio and bootloader for Android 4.3, you can restore or install an Android 4.2.2 ROM without changing the bootloader or radio.
frajobs said:
Hi guys,
I just want to ask if it is possible to flash any 4.2.2 Rom over a 4.3 one without changing the Bootloader or Modem (as far as I know kernel there are no other things updated in 4.3 except some features in stock Rom and kernel). I'm sorry if there is a thread like this one out there but I couldn't find it on my phone app
Thanks in advance for your time and help
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Give it a hard go bud lemme know how it works!

[Q] roms broken?

I tried a few roms out an seem to all have removed prl update, poor to little signal, broken gps locking, an a few other issues. My concern today I'm bringing up is wondering if anyone could supply me a clean stock rom. I need to wipe and install it. I feel going back to stock is my best option at this time so atleast my functions could work. Just at the moment kind of lost. sorry for the noob help.
What rom are you using that it's broken on? Working fine on tranquil but its far from a stock rom
Sent from the bowels of hell
Stock rom is more stable & fast, but I don't like the UI.
Using CM, works fine.
sent from my m7spr using tapatalk 4

Camera not working in 4.1.2

I have to use 4.1.2 becuase of GSM. (I cannot use 4.3/4.4 because it will connect to T-Mobile HSPA but not send/recieve data.) Camera will work on 4.3 and 4.4 easily. But, on 4.1.2 using stock deodexed, it won't start the camera. The camera just force closes. I am on the first firmware, too.
eduardog131 said:
I have to use 4.1.2 becuase of GSM. (I cannot use 4.3/4.4 because it will connect to T-Mobile HSPA but not send/recieve data.) Camera will work on 4.3 and 4.4 easily. But, on 4.1.2 using stock deodexed, it won't start the camera. The camera just force closes. I am on the first firmware, too.
Click to expand...
Click to collapse
Have you tried a third-party camera app?
StormyNight said:
Have you tried a third-party camera app?
Click to expand...
Click to collapse
Yeah, I have even tried that.
If you sent your phone in for repairs or got it new post the camera fix then the camera module isn't backward compatable with some roms like miui u will not get access to the back camera
eduardog131 said:
Yeah, I have even tried that.
Click to expand...
Click to collapse
Hmm that shouldn't be happening. Kind of strange. A possible solution however, is to flash the latest firmware, but I'm not sure how that would react to the old Android version. So if you want to be adventurous, try that out. If not though, go to Sprint/HTC and get it fixed from them.
After using SVN checkout on that Sense 5 and 4.2.2 ROM, and installing it camera worked. But only the front facing one, and it had the pink tint (I fixed it by changing settings though). I tried replacing libs from newer ROMs and made it worse. So, I'm getting close.
eduardog131 said:
After using SVN checkout on that Sense 5 and 4.2.2 ROM, and installing it camera worked. But only the front facing one, and it had the pink tint (I fixed it by changing settings though). I tried replacing libs from newer ROMs and made it worse. So, I'm getting close.
Click to expand...
Click to collapse
I have the same issue that you did. I cannot upgrade my android version cause of GSM and my camera isn't working would you be kind enough to explain how you were able to fix it, I would really appreciate it, thank you

Categories

Resources