This is a last-ditch effort to get some input before I go blow some money on a new phone. Hoping someone can help! It's possible that I haven't found an answer yet because what I'm doing is futile but I'll go through the story just in case...
Looks like quite a few internet people are having trouble with their HTC Incredible 2 cameras, and over Christmas I joined the fray. Upon launching camera or camcorder, I only see a black screen. The only thing I can think that could have prompted a camera failure was a short (<2ft) drop, but there’s no damage otherwise.
At first I tried but had no success with:
Restarting the phone
Clearing cache, clearing data, and/or force stop in Applications/Manage Applications/All/Camera/ (it’s running v3.00.000.120826.605 if that matters at all)
Restarting the phone in safe mode
Performing a factory reset
Unmounting SD card
Using diagnostic apps (some combination of doms diagnostic tools, androsensor, and msherlock) I’ve confirmed that although both front and rear cameras are recognized by the phone, accessing them for diagnosis freezes the diagnostic app. Strangely, the flash diagnostic tool freezes also, although the flashlight app works fine. Since I don’t think my drop could have busted both cameras and the flash at once, I guess there are two options: it DID wiggle loose a wire that does all the camera-related stuff, or it’s a software problem.
Since my warranty is a few months expired I figured I’d root the phone today, just to be double-dog sure it’s not something easily fixable. I followed http://forum.xda-developers.com/showthread.php?t=1931096, http://forum.xda-developers.com/showthread.php?t=1687590, used Android Commander to look at system files. On recommendation from http://androidforums.com/incredible-2-all-things-root/433350-camera-problem.html#post3361181, I tried to delete the current system/apps/HTCCamera.apk and replace with a different one; both one from http://www.teambamf.net/topic/1737-romgb-skyraider-zeus-13-inc2-update-11222011/ and also a standalone MiuiCamera.apk download were tried, but to no success.
I (attempt to) work with fortran77 during my day job so I can’t say I’m super happy to have blown a Saturday on yet more programming work. Unfortunately I’m a complete noob at this, and am not really sure how to further mess around with anything camera-related. It seems like the only thing I haven’t tried is to install a different ROM, but would it even be useful to do so? Have I missed anything? The Verizon agent I spoke to told me just to replace my phone, but since everything else works okay I wanted to be completely sure there wasn’t anything else I could do to fix the camera function. Does seem like I’m toast, though…
Thanks so much!
Excellent first post.
I have no idea how to help you. I would, However flash a ROM just to be sure. Tsm sense or andybonestock come to mind. It wouldn't hurt, you know?
Sent from my Incredible 2 using xda app-developers app
If that doesn't work try a aosp ROM like dkstunnas cm9 for a last ditch effort. I believe it interacts a Lil different with the camera then sense roms. Maybe
The camera is a replaceable part, so if you cant get it working a new one is less than $20.
Thanks for your suggestions!
I've learned a lot this week (like SMS Backup + should have been installed before the Verizon guy factory reset my phone...whoops, bye texts) and also tried to download "an app that uses the camera but not as a camera" as per http://forum.xda-developers.com/showpost.php?p=36239149&postcount=2 but that didn't work.
Looking at videos that take apart Dinc2's (http://www.youtube.com/watch?v=Qk91u3aqGAQ) I think replacing the camera would be quite outside my comfort zone...also, since both cameras and the flash refuse to work, that seems like a bigger job than I could handle. Unless they're like xmas lights where one goes out and they all go out, but still. I've only soldered maybe once in my life...
On to ROM switching, then. I used this tutorial to guide me through: http://www.incredibleforum.com/forum/htc-incredible-hacks/5514-flashing-roms-tutorial.html#post49612.
I've seen some threads about asop camera weirdness so I figured I'd try the strange one (http://forum.xda-developers.com/showthread.php?t=1932573) first. But, after a few different tries, I couldn’t get it to work…just got stuck on the white htc screen. After 25 minutes of waiting, I pulled out the battery and did the power-voldown thing to get to a menu. Then did a clockworkmod restore and tried andybonestock (http://forum.xda-developers.com/showthread.php?t=1392516) instead, which was successful in booting but not successful in starting my camera (BOO, but who is surprised). Went back to the asop a few more times (aeroevan kernel v14 and v15) as I’m thinking it has the best shot at a camera back door, but I just couldn’t get it to flash. White screen every time. I thought about doing ViperINC (http://forum.xda-developers.com/showthread.php?t=1953899) just for some variety but it uses more things I’m not familiar with (twrp? aroma? boot.img?) and I’m feeling done with this for the day. In any case it was a long shot, and if one ROM flash and a bunch of data clearing didn’t help, probably nothing will.
Looking like I may use this phone as a backup VOIP in the apartment (http://forum.xda-developers.com/showpost.php?p=34335798&postcount=20). Off to probably get an Incredible 4G LTE. Maybe all of the steps outlined in this thread will help someone with a less-severe camera issue…
Related
So the other day the app Widgetsoid releases a "Completely rewritten" update for their sweet app. I was obviously excited to play with this and set about recreating all of my toggles. One toggle I have is to toggle the camera flash on/off which is very handy to have a widget for on the homescreen. Another one I use toggles the screen always on/off which is handy when reading long articles. So I was using the screen always on toggle as a reading light (as the camera LED can be overly bright) when, after some time, my phone locked up. Following my natural instinct I pulled the battery and powered it back on. When it came back on I noticed that the screen always on toggle was still in the "on" position though I believe (honestly can't remember for sure) that the screen was timing out as if it were off. Anyways I put this out of my mind and decided to use the flashlight toggle as the screen hadn't been quite as bright as I wanted. However, upon toggling the flashlight to "on" The toggle froze in mid activation. I could see that I had clicked it but the animation never finished and the flashlight never turned on. I gave it several minutes to sort itself out and when it didn't I did another battery pull thinking that would clear it up. Well it didn't. Upon the phone restarting I was greeted by "Tango has stopped responding". Then when I tried the flashlight toggle again I got "Gallery has stopped responding" which flashed up and disappeared too quickly for me to click on it. I tried opening the camera to no avail. "Gallery has stopped responding". So one bug led to another to another to another as bugs so often do. No biggie, I was planning on doing a factory reset soon anyways so I backed up my data and went ahead with that. Unfortunately, when I finished the setup and went back to the camera app it gave me the same error. (please note that I did not restore anything after the reset.) So I did another just for sanity's sake but no change. I went into the bootloader and into recovery, cleared the cache and then did another factory reset. Nada. I downloaded a flashlight app to see if it could tell me anything new, which it sort of did. "Cannot connect to camera", it said when I turned it on. In my search on this forum for a similar issue I came across a post to a different issue talking about how when an app uses the camera it might not have let go when it was finished which causes problems for other apps. This makes enough sense except that I figured the reset would have resolved that issue. Unless, of course, the problem lies in the hardware which I am desperately hoping someone will tell me is foolish.
I'm not really sure what to try next in my troubleshooting short of unlocking the bootloader and flashing either the stock back over it or another ROM. I would prefer to try other possible solutions before this. Correct me if I'm wrong but shouldn't the factory reset restore the system and stock apps to their default state? Almost literally bit for bit? If that is the case then that means the issue isn't with the system or the camera app and must fall to the camera hardware itself? I feel it is worth noting that on about the third factory reset, during the initial setup (quite literally on the first screen) a popup popped saying "Talk has stopped responding". Why the Talk app would stop responding due to some issue with the camera seems out of place. Though as I said and we all know, bugs have a way of spreading to the places you least expect.
Anyways any help, suggestions or questions would be greatly appreciated. This really has me stumped.
I guess the question it boils down to (besides the three I've already asked) is how can I do a full wipe/reset that will actually reset everything? Or is it that the camera is really hung and if so any possible fixes for that? Anyone see any bright red flags waving violently in the storm?
Thanks in advance for any help you can provide
patrioticparadox
I am running 4.1.1 on a Verizon Galaxy Nexus build JRO03O
patrioticparadox said:
So the other day the app Widgetsoid releases a "Completely rewritten" update for their sweet app. I was obviously excited to play with this and set about recreating all of my toggles. One toggle I have is to toggle the camera flash on/off which is very handy to have a widget for on the homescreen. Another one I use toggles the screen always on/off which is handy when reading long articles. So I was using the screen always on toggle as a reading light (as the camera LED can be overly bright) when, after some time, my phone locked up. Following my natural instinct I pulled the battery and powered it back on. When it came back on I noticed that the screen always on toggle was still in the "on" position though I believe (honestly can't remember for sure) that the screen was timing out as if it were off. Anyways I put this out of my mind and decided to use the flashlight toggle as the screen hadn't been quite as bright as I wanted. However, upon toggling the flashlight to "on" The toggle froze in mid activation. I could see that I had clicked it but the animation never finished and the flashlight never turned on. I gave it several minutes to sort itself out and when it didn't I did another battery pull thinking that would clear it up. Well it didn't. Upon the phone restarting I was greeted by "Tango has stopped responding". Then when I tried the flashlight toggle again I got "Gallery has stopped responding" which flashed up and disappeared too quickly for me to click on it. I tried opening the camera to no avail. "Gallery has stopped responding". So one bug led to another to another to another as bugs so often do. No biggie, I was planning on doing a factory reset soon anyways so I backed up my data and went ahead with that. Unfortunately, when I finished the setup and went back to the camera app it gave me the same error. (please note that I did not restore anything after the reset.) So I did another just for sanity's sake but no change. I went into the bootloader and into recovery, cleared the cache and then did another factory reset. Nada. I downloaded a flashlight app to see if it could tell me anything new, which it sort of did. "Cannot connect to camera", it said when I turned it on. In my search on this forum for a similar issue I came across a post to a different issue talking about how when an app uses the camera it might not have let go when it was finished which causes problems for other apps. This makes enough sense except that I figured the reset would have resolved that issue. Unless, of course, the problem lies in the hardware which I am desperately hoping someone will tell me is foolish.
I'm not really sure what to try next in my troubleshooting short of unlocking the bootloader and flashing either the stock back over it or another ROM. I would prefer to try other possible solutions before this. Correct me if I'm wrong but shouldn't the factory reset restore the system and stock apps to their default state? Almost literally bit for bit? If that is the case then that means the issue isn't with the system or the camera app and must fall to the camera hardware itself? I feel it is worth noting that on about the third factory reset, during the initial setup (quite literally on the first screen) a popup popped saying "Talk has stopped responding". Why the Talk app would stop responding due to some issue with the camera seems out of place. Though as I said and we all know, bugs have a way of spreading to the places you least expect.
Anyways any help, suggestions or questions would be greatly appreciated. This really has me stumped.
I guess the question it boils down to (besides the three I've already asked) is how can I do a full wipe/reset that will actually reset everything? Or is it that the camera is really hung and if so any possible fixes for that? Anyone see any bright red flags waving violently in the storm?
Thanks in advance for any help you can provide
patrioticparadox
I am running 4.1.1 on a Verizon Galaxy Nexus build JRO03O
Click to expand...
Click to collapse
I would honestly try to flash another ROM. its hard to tell what is exactly causing this prob but I highly highly highly doubt its hardware. Make sure you wipe data and dalvik a couple times and go to mounts and storage and wipe system too. Do those a couple times, I always do just to be sure it works. Then after that try to flash another ROM stock or custom doesnt matter. This will help a lot.
Just a recommendation, I use and LOVE Codename Android Rom. Very very fast and stable with a lot of features.
Anyways, post back when you wipe everything out and flash a new ROM on there and let me know the outcome.
nothing yet...
myboyblake said:
I would honestly try to flash another ROM. its hard to tell what is exactly causing this prob but I highly highly highly doubt its hardware.
Click to expand...
Click to collapse
Just finished flashing the 4.1.1 back and still the same issue (did all of the data wiping). I'll try a custom ROM now though I doubt its going to make any difference.
What in the world has got a hold of my camera?
No dice
"Unfortunately Talk has stopped responding" on the first screen. "Gallery has stopped responding" when trying to open Camera app.
So despite several wipes and two distinct ROM flashes (used PARANOIDANDROID the second time) my device is still acting up.
Please help me out people. What is causing this error that is lasting across ROM flashes? What can I try to resolve this issue?
Rewiped everything and reflashed PARANOIDANDROID (2.23) just to be sure and still the camera doesn't work
seems like perhaps the registers ended up in an odd state.. know this is for a different phone, but you might give it a shot..
http://www.droidforums.net/forum/dr...amera-app-stoped-working-wont-initialize.html
---------- Post added at 05:03 PM ---------- Previous post was at 04:46 PM ----------
Looks like OMAPFlash can do a full reset on all the camera registers from looking at:
./Targets/Definitions/definitions_omap4.txt
in the OMAPFlash zipfile..
It might be worth a shot..
Slide opultl
No dice... I assume you were referring to clearing the cache and data. I had tried this before but gave it another shot anyways. In case you meant the screenshot part, I did that too and the screenshot captures fine but still the camera does not function. Also holding down the volume down and power keys never shuts the phone off I assume that is device specific (though several seconds after the screenshot captured the screen did flash off then on very quickly). I have tried disabling Gallery and rebooting in the hopes that would free up the hardware. Failed.
I am uber stuck on this.
Why is this persisting across flashes and what can I try to resolve it?
edit: just noticed that the bottom of your post was more info and not a signature. I'll look into that. Ran out of "thanks" for today but I'll get you yours
Since it won't delete....
As an update: I have tried contacting both Verizon and Samsung about the issue. Both recommend returning the device under warranty (as was expected). This would be fine except that I LEARN NOTHING! If the Samsung techies have a protocol/enumeration/anything to discover and resolve the issue then so can I (potentially), which means the general public should have this knowledge too, right? WHAT IS MY NEXT STEP?
(still have not yet OMAP_Flash'ed as I haven't found SOLID documentation on this yet.) (Google searching led me somewhere but left me confused. Please post documentation or the correct link if you have it and thank you) I am open to trying anything. Understand that my bottom line is giving Asurion $50 USD. "I LOST my phone, send me a [new] one". Phone gets replaced and I get to trash the old one. Sweet for everyone right? Wrong.
I don't give two runny, stinky butt creams about the phone itself. Which is not entirely, or honestly, even close to true. I'd hate to see a Nexus that can be saved be completely obliterated. If its totally bricked (which its very hard to do to a Nexus) then go for it. Smash that ***** up! But if, like mine, its recoverable then you owe it to the developer to try to save it. This Galaxy Nexus SCH-I515 reminds me of my SCH-a950. I loved that phone and literally (because of a now EX girlfriend) BEAT THE LIVING SNOT OUT OF IT. I literally threw it at my front porch as hard as I could from a good 30 yards away and yet it survived. Not only did it survive, it thrived. Never failing me (even until I finally upgraded) despite the "wear and F'ing tear" I had inflicted upon it.
I have actually dropped my Nexus several times. I have a massively cracked screen that I would love to show you all, yet the screen still functions as if there were no crack. I can click on the "options" toggle that is in the bottom right corner of many apps as if there were not a MASSIVE chunk of screen missing there. The phone is quite amazing. And before anyone says "oh you dropped it, that could have to do with the errors in the camera", NO. The camera worked just fine until what I described above. Samsung has done quite a magnificent job with this device (and all of their hardware, {I own a 26" computer monitor that kicks ass too}) making it resilient to adversity.
Now please, help me out....
I am hesitant to try the OMAP_flash as I haven't found decent documentation. PLEASE PLEASE post a link.
As I said I can always "lose" the phone and get a new one through insurance. So I'm not worried about screwing the phone, I just want to LEARN about the issue at hand.
What do YOU think is causing this issue?
If someone could post a link to the relevant info about the OMAP_flash then I will be happy to go forward with it.
Aside from all this I am shocked at the relative dismissal of this thread. I am seeking information from experienced members who have expertise on this device and while many are available I have gotten no replies as of yet. (this is not to discount those who have replied as I am very grateful for those suggestions as well) Please take two minutes and give me your thoughts. I don't believe this issue is similar to any other posts here and if you do believe it, kindly point me in that direction.
http://forum.gsmhosting.com/vbb/f63...-i9100g-via-usb-cable-freeeeeeeeeeee-1465412/
Here's a link, sorry I didn't post soon - I don't check back here often..
patrioticparadox said:
(still have not yet OMAP_Flash'ed as I haven't found SOLID documentation on this yet.) (Google searching led me somewhere but left me confused. Please post documentation or the correct link if you have it and thank you) I am open to trying anything. Understand that my bottom line is giving Asurion $50 USD. "I LOST my phone, send me a [new] one". Phone gets replaced and I get to trash the old one. Sweet for everyone right? Wrong.
I don't give two runny, stinky butt creams about the phone itself. Which is not entirely, or honestly, even close to true. I'd hate to see a Nexus that can be saved be completely obliterated. If its totally bricked (which its very hard to do to a Nexus) then go for it. Smash that ***** up! But if, like mine, its recoverable then you owe it to the developer to try to save it. This Galaxy Nexus SCH-I515 reminds me of my SCH-a950. I loved that phone and literally (because of a now EX girlfriend) BEAT THE LIVING SNOT OUT OF IT. I literally threw it at my front porch as hard as I could from a good 30 yards away and yet it survived. Not only did it survive, it thrived. Never failing me (even until I finally upgraded) despite the "wear and F'ing tear" I had inflicted upon it.
I have actually dropped my Nexus several times. I have a massively cracked screen that I would love to show you all, yet the screen still functions as if there were no crack. I can click on the "options" toggle that is in the bottom right corner of many apps as if there were not a MASSIVE chunk of screen missing there. The phone is quite amazing. And before anyone says "oh you dropped it, that could have to do with the errors in the camera", NO. The camera worked just fine until what I described above. Samsung has done quite a magnificent job with this device (and all of their hardware, {I own a 26" computer monitor that kicks ass too}) making it resilient to adversity.
Now please, help me out....
I am hesitant to try the OMAP_flash as I haven't found decent documentation. PLEASE PLEASE post a link.
As I said I can always "lose" the phone and get a new one through insurance. So I'm not worried about screwing the phone, I just want to LEARN about the issue at hand.
What do YOU think is causing this issue?
If someone could post a link to the relevant info about the OMAP_flash then I will be happy to go forward with it.
Aside from all this I am shocked at the relative dismissal of this thread. I am seeking information from experienced members who have expertise on this device and while many are available I have gotten no replies as of yet. (this is not to discount those who have replied as I am very grateful for those suggestions as well) Please take two minutes and give me your thoughts. I don't believe this issue is similar to any other posts here and if you do believe it, kindly point me in that direction.
Click to expand...
Click to collapse
Jesus, will people stop talking about insurance fraud........
It's these kind of people that people in your country have to suffer higher insurance premiums, and the very same group of fraudsters are complaining about high insurance premiums..
Regarding OMAP flash:
1) Remove battery
2) Open device manager
3) Plug your phone to your PC/laptop
4) Right click on OMAP4460, go to properties
5) Drivers tab
6) Update drivers, direct to the OMAP flash folder
7) Run the .bat
8) Reflash a ROM just in case.
I don't think it going to do a reg reset for the camera by default..
This is from: Targets/Definitions/definitions_omap4.txt
CONTROL_CORE_PAD_CAM_GLOBALRESET 0x4A1000C0
It is pulled in and used by:
Targets/Configurations/configuration_omap4460_tuna_8g.txt
CONTROL_CORE_PAD_CAM_GLOBALRESET needs to set for the correct location -- I have not done any digging, so I don't know what the location is..
Just Found this -- https://github.com/omapconf/omapconf/wiki
omapconf can be used to read/write/modify any register from within Android..
Mach3.2 said:
Jesus, will people stop talking about insurance fraud........
It's these kind of people that people in your country have to suffer higher insurance premiums, and the very same group of fraudsters are complaining about high insurance premiums..
Regarding OMAP flash:
1) Remove battery
2) Open device manager
3) Plug your phone to your PC/laptop
4) Right click on OMAP4460, go to properties
5) Drivers tab
6) Update drivers, direct to the OMAP flash folder
7) Run the .bat
8) Reflash a ROM just in case.
Click to expand...
Click to collapse
Insurance fraud? Um get a life! That's not why their premiums are high you ass! They do it to make more money you jack knob. My company charges $65/yr with a $25 deductible with up to 5 claims a year! That's so much better than asurion. And they give you a piece of **** replacement. Is all about money not the customer...now please me nice. Great ideas come from working together not from being an asshat!
I've searched up & down the forums but haven't found any luck in regards to my problem. Long story short, my Camera front, back & LED light has completely stopped working. The camera app force closes as soon as I open the app. I've tried all the conventional remedies from resetting to default, flashing different Roms, different batteries, clearing the data from the gallery/camera app.. Everything! I have a feeling the camera may be fine, but something may have become disconnected somehow, because its obviously not getting power.
I can't seem to find a relatively easy teardown of the Nexus in order to replace it or at least get a look inside. This brings me to my question: Has anyone ever experienced a dead camera? Is it simple to replace? Is the front & back camera a one piece module? This has been lurking me for so long and this forum is my last resort before I toss it out the window. As crappy as the camera is, I need it for Google hangouts for conferencing for work. Help!
I almost forgot, has anyone had any experiences with sending their device to be fixed by Samsung? That's my true true last resort, but I'm a little hesitant.. I had a bad experience before.
So here is a teardown by ifixit. I have disassembled my Galaxy Nexus to replace the screen, and it is a bit of a pain to get into. If you are feeling brave, it is doable, but it certainly shouldnt be the first phone to tear into.
Linky to teardown
Thanks for the reply.. Now check this out, I just installed an alternative camera app (LGcamera) from the play store & it worked well for the most part, however it won't detect a front camera. I also noticed I have to ready phone after 40 minutes to get the camera app working again.
This is sooo odd. Like I mentioned before, whenever I open the original camera app, all I get is a force close - So maybe it is a software problem? Can you recommend any special way of re-installing gallery/camera app or someway to tweak the software to see if that's the problem?
The easiest thing I would say to narrow down the problem is (if you have cwm installed) make a nandroid backup, wipe everything, and install a different rom than the one you are using. Then you can have a completely fresh start, unrelated to any of your current software, and test the camera then. If it works, it was a software problem, if it doesn't work, it is most likely hardware.
Hi all,
Hopefully someone can shed some light on this and help a tortured soul. By no means am I an Android expert, but I definitely am not a noob. I had an S2 in the past and done plenty of flashing there, and now own a Bell SGH-I747M S3... my precious...
First off I tried a whole bunch of different ROMs, of all flavors (AOSP, AOKP, CM10, PARANOID, and some TW), and a lot of them are awesome. However, I found that after having done so much flashing and customizing using other people's work, it was now time for me and attempt to make my own ROM. I feel I now have the knowledge to do so. Don't get me wrong, I am far from a Dev, and I don't do much coding at all. I found this great suite called Android Kitchen, which pretty much guides you through the steps for making your own ROM, and it's great for learning.
In the end, I was able to come up with a final working version of my own ROM, built from scratch using the original official Bell JB 4.1.1 update file. and I have to say I am quite proud of it, as it has all the apps, features and theming that I want, and works quite well I might add. I get great results performance and battery wise (for my taste and needs) when using my ROM with KToonsez kernel.
BUT!!... as good as I think the ROM is, it is unfortunately not flawless. I do have an issue (the only one I could find so far after 2 weeks using it), and for me it is a BIG issue. Maps/Navigation does not seem to like the ROM/kernel combo on MY phone. I say MY phone because I have setup a friend with pretty much the same thing, and he is not experiencing the same issue.
Here is a description of the problem I get. Let's say I go to my contacts and select one with an address. I will touch the address, then Maps opens no problem, and finds the place, and I also get fast GPS lock, no issues there either. Then I will select Navigate to get a voice turn by turn description while driving. The Nav app starts OK as well and seems to work fine. Then after a few minutes (sometimes 2 sometimes 10), Navigation will shutdown, and I get a pop-up saying "Unfortunately Maps has stopped working...". When I OK that, after a few seconds, Navigation starts talking to me again, although not on screen. Also a Navigation icon will appear in the notification area, and if I hit that it resumes Nav, as if nothing had happened. Another few minutes like that, and then I get the same message again, but this time it crashes for good. ALWAYS!!
Troubleshooting:
- Flashed the ROM/Kernel 3 times now. Always wiping and formatting ALL!
- Cleared cache and data from Android Settings/Applications
- Cleared cache from Maps settings.
- Re-installed Maps
- Wiped phone cache, dalvik cache and fixed permissions from recovery.
- Changed kernel back to stock (that seems to work fine btw,, but I do not want stock kernel, plus the setup I want works well on my friend's S3, same as mine, which I setup myself for him (he's a total noob)).
- Changed kernel again from stock to KToonsez (that also works fine after that, however I get other things that start not working well... too many).
- I always wipe cache, dalvik cache and fix permissions after changing kernels.
I have been poking at this for about a week now, and I am tired! I was hoping someone would have a suggestion, maybe from past experience. The only thing I can think of that is different on his phone and mine is the apps that we restore after installing the ROM and kernel (Titanium Backup, user apps and data only, nothing related to system is touched). I am guessing one of my apps could cause a conflict, but pardon my laziness, but I really do not feel like testing / installing my apps one by one to hopefully without guarantee find a culprit... way too many apps for that So I am testing my luck here on XDA... there are a lot of smart people here
I appologize for the lenghty post, but this way, there is less chance I left anything out... PLEASE HELP!!!
Raz...
Sorry for the bump guys... I was really hoping someone can give some input here. Desperate for a solution here!!
Thanks
Some background info.
I bought my pixel XL from the Google store and I believe it came with the 63L build out of the box. I have since made it a point to completely wipe and fastboot flash the latest image Everytime an update is release, right now I am on the 26U build. The only thing I have done to my phone (and these bugs happen before and after) is bootloader unlock and root.
The bugs.
Every once in a while, my volume controls will quit working. I notice it happen more if I cast to my Chromecast and play a song or video (seperate) on my device. I'll hit the volume button and literally nothing will happen. To fix this I usually have to turn the display off, wait a few seconds, wake it back up, then the controls work fine again. I do not believe it is a hardware issue because i can fix it Everytime it happens.
The second bug, probably the most annoying, is that my nav bar will become completely unresponsive occasionally while in landscape orientation. Say I'm watching a video on YouTube in full screen, if I swipe to pull out my nav bar and hit the home/recent/back button, nothing will happen. I will see the animation however no vibration (feedback) or a action occurs.
This happens in games, YouTube, web browsers, doesn't matter as long as my phone is in landscape mode. Also note that when this happens, my device refuses to rotate back to portrait. This leaves my only solution (same as the volume bug) to turn off the display, wait a few seconds, and then I back on. Sometimes, however, this don't even work, and I'll have to jump straight to settings from my lockscreen to force the phone to portrait where the functionality of the nav bar returns.
I've contacted google, they run me through the typical steps "delete cache, have you tried a reset, update to the latest software", but nothing fixes it. They have told me repetitively it's not a common problem and it's not a problem that's worth rma'ing over.
I've been discovering my pixel has many small issues that no one else has. Such as the horrible transfer speed explain in my earlier thread, these bugs above, refusing to charge when the device is off, etc.
Has anyone had similar problems?
@noidea24,
I've had none of those issues. In fact, my Pixel XL has been flawless.
Not good. I guess I'm going to try and force a RMA.
noidea24 said:
I've contacted google, they run me through the typical steps "delete cache, have you tried a reset, update to the latest software", but nothing fixes it. They have told me repetitively it's not a common problem and it's not a problem that's worth rma'ing over.
Click to expand...
Click to collapse
Sorry to nit, but when I read the statement above I can't help but wonder if you actually did a factory reset. Reason I say that is you stated "have you tried a reset" and you didn't explicitly state that you did.
I kind of doubt the responsiveness stuff you're referring to is hardware related, it's probably software.
Whether or not a rogue app is affecting your device or a root app is impossible to determine without doing a factory reset and carefully adding one app/change at a time until the problem comes back. It's a PITA but that's what I'd do first to rule out hardware, and I'd simply run email and messaging apps unrooted for at least 24 hours to rule out hardware issues before I start loading up my favorite apps.
muzzy996 said:
Sorry to nit, but when I read the statement above I can't help but wonder if you actually did a factory reset. Reason I say that is you stated "have you tried a reset" and you didn't explicitly state that you did.
I kind of doubt the responsiveness stuff you're referring to is hardware related, it's probably software.
Whether or not a rogue app is affecting your device or a root app is impossible to determine without doing a factory reset and carefully adding one app/change at a time until the problem comes back. It's a PITA but that's what I'd do first to rule out hardware, and I'd simply run email and messaging apps unrooted for at least 24 hours to rule out hardware issues before I start loading up my favorite apps.
Click to expand...
Click to collapse
A factory reset is far from a pain in the ass, and yes, i have done it many times. the only things that makes it suck is when i have to transfer files back to my device because (as mentioned) i have terrible transfer speed from pc to device.
i have literally done everything i can to make this devices worth the price, and things are only getting worse. Since the post (later that night) i factory flashed once again, and re locked the bootloader. No root, No extra apps, hell, the only apps i had on my phone to begin with were facebook messenger, and that pixel car racer, i dont use anything else. ive had an even worse bug come in where my phone completely freezes when opening google camera and swiping to the video section. ill have to hold power until it force resets.
ive been with xda since my Motorola droid, Ive built roms for the community for my lg g2 and my nexus 6. hell, i even built kernels for my 5x (not public), so im a little past your average user complaining about some things that dont work due to user error. these are legitimate device flaws and malfunctions, and i was simply asking if anyone else has experienced them. and since it seems no one has, i have deemed my device faulty. now i have to come up with $600 for a service hold to get it replaced.
My experience with Googles first official flag ship has been pathetic, and im hoping that this replacement device i get (eventually) will persuade me not to go back to my 6p.
Well if that's the case then yeah I hope a replacement device will solve your issues. Sounds like it will.
Didn't mean to rile you up, just looking for clarity.
Good luck!
Hi there,
I have mentioned that issue partially in various other threads, now I'm asking for help for real, hoping someone can help me out.
Whenever I flash a new ROM to my 5X, the cameras work for like half an hour properly, beyond that it works somewhat for like two further reboot before cursing either just camera apps to crash or the entire phone to restart.
At first I thought it was because I replaced stock Oreo with MaruOS 0.6.6 and contacted the maintainer/developer about it but he couldn't think of much either.
So I switched to CrDroid expecting for better results but it's still the same.
Yesterday I went all back to stock Oreo 8.1 with Google's bootloader along the way.
My expectations were high given the cam worked a bit longer than on custom ROMs.
It crashed after a while but disabling HDR+ seemed to do the trick for some more minutes.
However, even doing so couldn't save my phone's cameras from not being properly detected.
Android returns the typical dialog for crashed apps, sometimes a toast pops up saying no connection could be established.
I tried CPU Info, sometimes I'm lucky and at least the cams get listed on the Hardware tab, for the most part they are absent though.
So is there anything I can do to about this issue or am I lost here?
Edit: I noticed this went to the wrong sub-board.
Maybe a moderator can move the thread to the Q&A/Troubleshooting section?