Develop Bugs

[Q] DHD camera dead

About 2 weeks ago, my camera simply stopped working. Any app that uses the camera simply opens to a black screen and then becomes unresponsive.
I've tried a full factory reset to no avail. Before sending the camera for repair, is there anything else I can try. I did check the forum and elsewhere to see if this was a known issue with the DHD or an individual firmware vesion, but nothing obvious.
I'm running 1.72.405.3
Thanks for any pointers
Daz

Hi Daz,
It does sound like your camera's sensor has failed. I had a similar issue with my HTC Hero when I got that many moons ago. This would be covered by the manufacturers warranty so you'd be entitled to a replacement or repair.

Did the camera only fail once the update had been applied? As i think and i'm not 100% but i think that the cam is one of the things which the update is for, maybe you could try a custom rom to see if the update has caused it, I can't see why but it could be.
My Hero's camera would not work with anything over 1.5, any custom rom or even the stock 2.1 update would cause my phone to reboot after every second usage of the phones camera, it was very annoying and because it was a persistent problem which was no fault of my own, i didn't pay for the replacement, so maybe look into it, it may save you a few bob getting it fixed, unless your getting it for free.
Just a thought.

To be honest it could well have been after an update, I just can't tie the two events together in my head.
The phone will be fixed for free as it's still under warrantee, I was just wondering if there was anything I could do to avoid having to send it away for what could be weeks. I do suspect it's a hardware issue so prob best just to let HTC deal with it and send me back a working phone.
Thanks all.
Daz

I also have this problem, any updates on the issue? I really don't want to be without my phone for weeks! The camera only stopped working after I flashed from Leedroid 1.2 to cyanogenmod 6.1.3 then flashed back to Leedroid

Hi,
I'm afraid I don't know just yet. I sent the phone away for repair and it's still being worked on. I'll let you know what they said when I get it back.
Daz

random reboots

Hello everybody,
I purchased my galaxy note 2 in late December, I kept the stock samsung ROM (android 4.1.1)and almost rooted it immediately after I had opened its box. Rapidly, I noticed it rebooted from time to time, it seems it happened randomly, i.e. not whilst performing a specific task on my phone. For instance, sometimes when I wanted to check my emails or texts, I picked it up from my pocket, and android was asking me to enter my SIM PIN. So basically my phone rebooted while sitting in my pocket. More rarely, it also suddenly rebooted while I was using it. (but to be honest, it spends more time in my pocket than it does in my hands, that's definitely why it did the latter far less frequently).
I saw that there was an update available, so I flashed the 4.1.2 stock ROM using kies, and rooted it again shortly after. But the reboots issue was still there, so in February I decided to give a try to a cyanogen mod 10.1 nightly build. For like a week or 10 days, it appeared to work properly, no more random reboots. However, after that delay, unfortunately it started to randomly reboot again.
I don't think that rooting the phone can cause such an abnormal behaviour, can it? I use several apps that require root privileges, that's why I did root it every time I flashed a new ROM.
Well the bottom line is that it's really pissing me off, so I'm considering to return it to samsung using a RMA procedure. But anyway, if you have any idea that could help me solve this problem, please feel to let me know, I'll gladly appreciate it. Also I'm wondering if anyone has an alike problem?
If need be, I'll return it for a repair or an exchange, if so, what do I need to do to reset it to factory defaults? I can re-flash the stock ROM, that should unroot it, but resetting the flash counter is also required, for that purpose I'll probably try the 'Triangle Away' app, hopefully it's gonna work. But AFAIK, when doing so on my former phone - a samsung galaxy S 2 - there was another counter, that counted how many times the first counter has been resetted, so one has to actually reset both of them in order for the mobile not to look having been tinkered with. Is anyone aware of a similar second counter on the galaxy note II? If you think of anything else I forgot to mention, please give me a shout.
Thanks for reading my post and helping me out.

Sadly it sounds like you might have a defective Note II. I have a stock (not rooted) Note II and, while I've only owned it for a month, it hasn't exhibited any problems with rebooting. Nor did I have anything like that with my S3 previously.
Probably not what you were hoping to read, sorry.

Thanks for your input muppetmania, well fortunately all galaxy note II don't have this problem
I just hope that if I return it, they'll be able to reproduce the annoying issue as they probably won't install as many apps as I did, or use it the same way, etc ...

My note 2 is the first android phone I've had that I have not rooted (yet). I've had it about a month now and it has randomly rebooted 3 times so far.
Every time it has happened it's been while I had 10+ tabs open in Chrome and was reloading several at once while also using other apps. For example one time I was composing an email and pulling excerpts from several sources on different web pages.. midway through composition and BAM, random reboot
In my opinion you did not cause this by rooting the phone

nebenezer said:
My note 2 is the first android phone I've had that I have not rooted (yet). I've had it about a month now and it has randomly rebooted 3 times so far.
Every time it has happened it's been while I had 10+ tabs open in Chrome and was reloading several at once while also using other apps. For example one time I was composing an email and pulling excerpts from several sources on different web pages.. midway through composition and BAM, random reboot
In my opinion you did not cause this by rooting the phone
Click to expand...
Click to collapse
If mine had only rebooted 3 times in a month then I'd be "happy" But for me it's more like 3 times a day. Well any random reboot is never a good thing, especially if you're are typing a text or writing an email. I'm scared it happens when I'm using my phone as a GPS on my motorbike, could be really pesky if I have to stop, wait for the mobile to reboot, get another GPS fix, and set my destination again ...
Just out of curiosity, you're also running the stock samsung ROM? Switching from it to cyanogen made virtually not difference for that matter.

I still have not rooted this device so yes... I'm running the stock Samsung rom
In case it may be relevant though, I do also use nova launcher and LOVE it. This new generation of TouchWiz is not bad at all not Nova is better, imo

I use the default launcher, both for the stock ROM and cyanogen Mod. I did not really like touchwizz, but I think the dual screen function and the stylus management were quite good though.

I gave a call to the after sales service, and they advised me to go to a Samsung store in order to get my phone repaired. Just to make sure it's going to be be alright (I mean that I don't want them to find out that I have rooted / installed a custom ROM on the mobile and use that as a pretext for refusing to fix it), can someone tell me exactly what do I need to do in order to revert the phone back precisely to its factory configuration?
So far, here is what I plan on doing:
- install the last official samsung ROM (which is currently the 4.1.2 version of android if i'm not wrong), that should unroot the phone altogether
- Use an app called "triangle away" to reset the flash counter
But I still wonder is there is anything else that would allow them to know that I flashed / rooted the phone. Is there anything like a second counter, that counts how many time the counter mentioned above has been resetted itself? Also I do remember that when I flashed my galaxy S II with an insecure kernel, a yellow triangle with an exclamation mark appeared during boot up (I know that "Triangle Away" should remove it), I don't currently have that on my GN 2, but I don't know whether Samsung still uses this method or if they have implemented something else?
Thank you.

[Q] Random Crashing?

So I have had the note 4 (retail version) for a few weeks now. It is quite nice being no root.
The only issue I have started to see is randomly when I unlock my phone there will be a crash report with just a picture of my lockscreen and nothing else. Today I attempted to go into my contacts and it crashed 4-5 times until I waited for a few seconds then finally got in. Has anyone else experienced these issues before?
I have not loaded any apps that are out of the norm, I am fairly tech savvy as I deal with technology for my job. I haven't yet had time to try a full factory reset on it as I also use this as my work phone (I own it though).

Yes I'm getting many crashes at this point and it's very aggravating. First it was Contacts, then other apps including Pandora, a music app, Gallery, and one other I can't remember at the moment. It happens many times per day now (probably about once per hour), though isn't fully predictable yet. Audio has also begun cutting out periodically when streaming music over Bluetooth. I've wiped cache and done a factory reset, but neither has produced a change.
Sent from my SM-N910V using XDA Premium HD app

Hmmm, anyone else having issues with this? Wondering if a few bad phones went through the line. I've had quite the busy weekend dealing with being in a accident and such so i haven't wiped my phone to see if that affects anything.

I've been getting the occasional Contacts crash, for reasons still unknown to me. I haven't had anything else really going on though. I've had my phone since December.
Though slightly related, I did have a strange behavior last night where the phone screen would not timeout and turn off on its own, even while on the lock screen. A reboot fixed that. I've never had that happen before.

veteranmina said:
So I have had the note 4 (retail version) for a few weeks now. It is quite nice being no root.
The only issue I have started to see is randomly when I unlock my phone there will be a crash report with just a picture of my lockscreen and nothing else. Today I attempted to go into my contacts and it crashed 4-5 times until I waited for a few seconds then finally got in. Has anyone else experienced these issues before?
I have not loaded any apps that are out of the norm, I am fairly tech savvy as I deal with technology for my job. I haven't yet had time to try a full factory reset on it as I also use this as my work phone (I own it though).
Click to expand...
Click to collapse
From what I have been reading in other forums, the " unfortunately contacts have stopped " has to do with google+. This issue just popped up recently and is happening on various devices and different carriers. So it's not just vzw Note 4. Disable or Uninstall updates seems to work. Hopefully the issue will get resolved with a Google+ update.

leroybrute said:
From what I have been reading in other forums, the " unfortunately contacts have stopped " has to do with google+. This issue just popped up recently and is happening on various devices and different carriers. So it's not just vzw Note 4. Disable or Uninstall updates seems to work. Hopefully the issue will get resolved with a Google+ update.
Click to expand...
Click to collapse
It's quite interesting how Google+ has been causing issues. I came from the Lg G3. Google+ and Verizon's app did not like each other and would crash constantly until google+ was disabled.

Random Reboots and Signal loss

I have random reboots and signal loss on my Nexus 5X.
I couldn't point my finger on what is causing it.
It started happening after the 6.0.1 update but since then I tried almost everything in the book:
* I was on stock with root, did wipe - didn't help
* I tried stock without root - didn't help
* I downgraded back to 6.0.0 without root and re-locked the bootloader - still didn't help but had a fewer reboots.
* I tried to check if it's one of my app causing this with no luck either. Video player played like an hour video without problem and afterwards it rebooted when I used chrome for couple of minutes.
* I had my screen replaced by private lab (I'm not living in the US where the phone bought originally) two weeks ago but the problems started to show up just yesterday.
I'm really frustrated because I'm not living in the US so I can't just RMA it and even if I had a way I dont know if Google will replace it for me because the screen replaced once and I unlocked bootloader and had couple of custom ROMS installed.
Has anyone else had this issue? any idea or advice on somthing that I didn't tried yet?
getting real frustrated here...
TIA,
Nitai

your problem remind me of the one I had after replacing myself the screen of the original nexus 5, except that mine was also hard-lagging before reboot itself. First thing I did was double check every connection, then flash the stock rom, but nothing did help. I still bet it was a power issue, either because of the battery (that I slightly forced to remove it), or because of some accidental damage to sopme power circuit.
If you won't be able to solve this in any way, as last chance you could try a battery replacement (I don't really know if it will work)

I also opened the back panel and reconnect every connection just to exclude that.
Didn't help either....
Sent from my Nexus 5X using Tapatalk

Anyone else experiencing something like this?
I found that it happened to a lot of Nexus 5 users after the Android 6.0 update: https://productforums.google.com/forum/#!topic/nexus/BodpKTSF-a8

#brickgate

Hi everyone, I had some strange behavior with my note 7 last night, it locked up for abou 10-15 seconds and then rebooted itself and got stuck in a bootloop, it looped through the first boot screen for around 10-15 cycles and eventually managed to boot up, I kept having random reboots and bootlooping for the next hour or so, I suspected it could be the stock browser as it seemed to be what I had open when most of the reboots occurred so I disabled it with EZ disabler, I haven't had any trouble since last night and I have re enabled the stock browser a day still don't seem to have any problems yet. I googled it and found that apparently a lot of people with the exynos variant are having similar issues, I read somewhere that it was the July date coded models that had the issue but mine is an August coded model, does anyone know anything about this?
Edit, its possible that downloading or updating apps might have something to do with it.

Mine does this and has been doing it since day 3 of my 10 days of having it.
What I'm gathered, any form of lag that corresponds with the vibration motor causes the reboot - so if you touch the back button one too many times or hitting the menu button; heck, sometimes it even just reboots when I'm scrolling in anything and there's some lag (both Chrome and stock browser as well as Whatsapp/Playstore).
I talked to my Telco and they said they'd replace as it's a clear defect but there's no stock unfortunately for an instant swap. I'm about to switch to the international XSA firmware (Currently on OPS Optus firmware) to see if that does anything since the XSA had a recent update relating to performance issues. If it is a defect it won't do anything and the best bet is to go into store and send it off while they order a new one.
Mine's begun to do it more frequently now. Sucks that this is the experience of a first time Note user :'(