Database Develop

[Q] Help! Random Reboots on New Note

Hi,
Got a Note in the UK just last week, brand new, and within two days I flashed it to the German stock ICS update. I can't say that I noticed issues in the first few days, but that could be because I didn't get a lot of time with it.
Since then, however, now that it is all set up and configured, I'm noticing random spontaneous reboots during sleep on the device, anything between every 2 to 6 hours, no warning, just the phone suddenly flashing into life with the model splash screen, followed by startup animation.
Reading around I've followed all kinds of anecdotal cures... I've removed Apex Launcher and Widget Locker, and returned to TWLauncher and stock dialer. I've moved all my apps from external SD to phone internal and deleted App2SDpro. I've cancelled all automatic syncs. I'm not rooted and don't have any iffy software on it.
Does anyone please have any ideas on this?

No ideas?

Since the update mine does exactly the same thing. Sometimes it reboots after every hour or so but then sometimes it happens every 5 hours. Its completely random and has started happening since the ICS update.

Hmmm. I'm wondering if I should do another full install, or if this is a bug that will be absent in the official UK version of the new OS/firmware update.
I wonder if it is somehow specific to UK users?
It annoys the pants off me, because it will happen, then I'll delete a load of software and restart manually, then it will behave sometimes (like today) for 11-12 hours. And then it does it again. And again. I've had 12 hours between reboots from yesterday to today, and then today I've had three in four hours, including one after just an 11 minute interval, while the phone was on standby.
Is there anything that can be a 'variable' on an 'international' Note which might be an incompatibility in one territory but not another?
Sim? Network? Wifi?

I'm in UK, and was on German Ics official until today . Started experiencing fcs on random apps, from what I've read elsewhere that can be the start of a superbrick. I would highly recommend flashing back to stable GB immediately.
Sent from my GT-N7000 using xda premium

Well... We may be seeing an improvement.
When I installed German ICS on my UK Note I did it as an upgrade. So yesterday afternoon I put the note to sleep and then rebooted into hard reset. I got myself a nice clean system and after lots of restoring files and reinstalling apps, I now have a Note that spent all night charging and hasn't restarted itself since 6am. It still could... But hasn't yet.
Something else odd I noticed...
When I first installed ICS (without tweaks, messing, only on stock ROM) and came to install SwiftKeyX for Phone it refused, allowing me only to install the tablet version... This depressed me a little because the skin I use is nicer on the phone version than tablet. Oddly, this time, after the reinstall, the note would only install the phone version of SwiftKeyX, and not the tablet.
Not sure what changed and why, but I can only imagine that something was broke and is now fixed...
Time will tell. I think battery might be a little better now too. And I use JuiceDefender.
If I get a full 24 hours without reboots I might dare to try App2SD again and move some apps to card storage.
So far so good.

Arse. 19 hours later and the reformed Note spoiled itself with a random reboot during sleep.
Back to the drawing board.
So is this a hardware or software fault. Its so new that I could do with knowing... I can insist it be swapped. But am I going to get the same again? Has anyone been able to trap this erroneous reboot in logs or anything? Do we know what it is?
Are there just a few of us, or many? Former would suggest hardware, latter could be software.

I'm having this issue too. We need help here
Sent from my GT-N7000 using Tapatalk 2

Mine hasn't rebooted all night while on charge. I would also like to know if there are any logs that can pin point the issue
Sent from my GT-N7000 using xda premium

I would suggest turn it off (be sure, it is turned off)
Remove the battery
Leave it this way for an hour
Insert the battery
Perhaps it would be good idea to go back to your area GB also (following drKetan guides).
I had the same anectodal thing happening with my new note just when i purchased it. After 1..2 days it went grazy. Then it blacked totally out. But just by chance it woke up after resting without battery for a day.
Personally, I think, the cache should be cleaned - BUT i definitely will not recommend a wipe cache in LPY (though it worked with me - but then again, it COULD NOT work with you - and the loss... what a loss it would be). (worked with me - that means it did not brick my phone when i upgraded few days ago and that did not have anything to do with my troubles when I purchased the note (few months ago)).

I'm discouraged that there are either so few people suffering this that we're simply 'on our own' with it, or so many people who have it but have learned to accept it.
It seems preposterous to not have attention to such a big fault.
And I realised that I've seen this before, and have the sneaky feeling that it is a dirty little secret of Android....
I bought an ASUS Transformer last June. It had this issue from day one on Honeycomb. Random reboots at unpredictable times, at least two per day. Over the last 9 months it went back to ASUS three times and each time they 'fixed' something totally unrelated to the problem before eventually telling me that they had no replacement units to give me and were authorising a full buy back - a refund.
I had anecdotal indications that it only occurred when I had an SD card installed. That was my growing suspicion, but I now no longer have a unit to test it.
Other Galaxy range users have been reporting random or looped reboots, and have pinned blame on using an sd card, especially in conjunction with App2SD.
I have an HTC Flyer with an SD card installed, running App2SD, and have no random reboot problems. Its as solid as a rock on stock Honeycomb.
Similarly, though, some users have reported that their Galaxy phone model has random reboots relating to having a sim card installed...
You see where this is going. Its getting to the place where we're accepting that the only way our expensive device works is if we disable key functionality and surrender our expectations of its advertised features doing the job they were intended to.
It is scandalous that this device should malfunction as a result of using the advertised features, and that no fix would be found nor explanation offered.
I now have an SD in the unit, but have not moved apps with App2SD. I have established that the reboots occur with all three of my SD cards of varying sizes, soit is not caused by a corrupt or faulty SD... If it is caused by an SD at all, it is 'all' SD's. Since so many users have the Note with SD's installed, and they run perfectly, I can't believe there is an issue with SD cards, although I did wonder if the manufacturers are now phasing out SD slots in their devices because 'cloud computing' is all the rage, or rather because this volatility caused by SD in the now unfixable evolving Android code means that they are minimising their embarrassment by simply dispensing with the faulty variable.
I have also begun setting static IP's for all my stored wlan's in case this is a DHCP issue caused during momentary wakes from sleep for polling or sync. If only we had an app that could store, like a seismograph, a persistent record of device events which trigger the reboot and then capture the reboot events also. Closest I've found uses ram to store the events log and then blanks the log on reboot starting from the reboot instead of maintaining the record prior to the reboot.
Getting close to wits end with this, and now deeply regretting my purchase.
Nothing like this on my Xperia Arc S.
Even an iPhone is better than this!

opsakas said:
I would suggest turn it off (be sure, it is turned off)
Remove the battery
Leave it this way for an hour
Insert the battery
Perhaps it would be good idea to go back to your area GB also (following drKetan guides).
I had the same anectodal thing happening with my new note just when i purchased it. After 1..2 days it went grazy. Then it blacked totally out. But just by chance it woke up after resting without battery for a day.
Personally, I think, the cache should be cleaned - BUT i definitely will not recommend a wipe cache in LPY (though it worked with me - but then again, it COULD NOT work with you - and the loss... what a loss it would be). (worked with me - that means it did not brick my phone when i upgraded few days ago and that did not have anything to do with my troubles when I purchased the note (few months ago)).
Click to expand...
Click to collapse
Can you direct me to that guide?
And is it likely that it is the DE ICS release that just doesn't like UK devices? Why would that be so?

Looks like i'm going to get stuck with this problem until I move on to a next phone. What a waste
Sent from my GT-N7000 using Tapatalk 2

Maybe you should have waited for a stable release built using the UK or wwe equivalent rom? You didn't even give the stock more than a couple of days, what was the rush?!
Sent from my GT-N7000 using xda premium

Maybe, yes.
Naivete, perhaps.
I'll tell you exactly why.
I had an Xperia Arc S on ICS which I loved. I was tempted by the Note. I bought one expecting a Samsung flavored ICS experience, and got tossed back to GB. I basically had 7 days to return the Note or learn to like it, and during that period DE f/w was released and I had to know...
Note was rebooted using static ip's and is nowraring to go...
So far so good @ 18 hours

BashyUK said:
Maybe you should have waited for a stable release built using the UK or wwe equivalent rom? You didn't even give the stock more than a couple of days, what was the rush?!
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Did you even read my other posts? Problem started when i was still in gb.
Sent from my GT-N7000 using Tapatalk 2

Still going... No reboots. And excellent battery performance to boot.

l0rd_almighty said:
Did you even read my other posts? Problem started when i was still in gb.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
But if that was when your phone was still new why didn't you just return it for a replacement rather than root and flash a phone that wasn't stable in the first place? For all you know it may be a hardware issue and likely so as I've not heard any apart from you and the op mention it.
Anyway, your phone, your call what you do with it but it makes no sense to me to blame the manufacturer and model when you've not even followed basic steps to deal with an issue.
Sent from my GT-N7000 using xda premium

The first note I had in December 2011 rebooted at random. It was a hardware issue. It only started after owning it for 3 weeks, stock GB. Not roiled or modified in anyway. I had it replaced.
G
Sent from my GT-N7000 using Tapatalk 2

BashyUK said:
But if that was when your phone was still new why didn't you just return it for a replacement rather than root and flash a phone that wasn't stable in the first place? For all you know it may be a hardware issue and likely so as I've not heard any apart from you and the op mention it.
Anyway, your phone, your call what you do with it but it makes no sense to me to blame the manufacturer and model when you've not even followed basic steps to deal with an issue.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Basic steps i didn't follow? Enlighten me... I never mentioned that this happened when my phone was new. I said this started when i was still in GB. Notice the difference? If you can't help us figure out what's causing this just go troll on somebody else's thread.
Sent from my GT-N7000 using Tapatalk 2

Phantom screen input

Hi everyone,
Long time lurker so first off thanks to everyone for all the useful assistance over quite a prolonged period.
I did a search before posting this, and whilst other screen issues have been raised in the past I could see no reference to this one. Basically in the last 48hrs my N7 has started to interpret touch screen input despite me not actually interfacing with the screen. It has got so bad in the last day I'm probably going to have to send it back as I assume its a hardware issue. I've had the N7 about 6 weeks.
Not sure if anyone else has seen such a thing and its actually software related? I'd rather fix it myself if possible rather than send it away. Even if not, I thought it would be useful to provide a record of the issue.
Edit - as a new user I can't post the YouTube link. My username is stenard1000 and the video title is "Nexus 7 screen issue - phantom input". I double checked and its easy enough to locate.
Ignore the Paradise Cove gameplay in the background. The issue mainly occurs in the top right corner. The only screen input by me in the video is the back button or pressing no in the middle of the screen. I've enabled the touch screen logging in the developer options to help track the phantom inputs more easily.
Also, for the record, turning the screen off and back on again does stop the issue temporarily, so its not a permanent hardware fault.

All you can do is a full wipe and format of everything, and flash back to completely stock. If that doesn't fix it then its a hardware issue and you're powerless,; time to send it back.
One thing that you could try first is popping the back off, and disconnecting the battery for ten minutes or so to give it a proper cold boot. That's the best advice i can give...
Sent from my Nexus 7 using Tapatalk

I've recently started getting this as well, my n7 was picked up last August so its odd that its suddenly started to be haunted.

spvnexus said:
I've recently started getting this as well, my n7 was picked up last August so its odd that its suddenly started to be haunted.
Click to expand...
Click to collapse
There's been a # of posts & discussions on this lately - hardware issues are being pointed at - as simple as a loosely assembled battery connector (that's lousy QC on the production line at the factory = poor QI) and/or hardware failure with the thin & delicate electronics.
At least we can mostly conclude that neither our own government's CIA/NSA and/or UK's MI5, etc. are tuning in to spy on our devices, or some hackers deep out in cyberspace has managed to remotely launch spyware on the N7 - I would hate to think what my friends behind the China's firewalled garden are handling these freaking incidents with the ghosty keypad inputting strokes on its own, LOL.

I had this issue straight out the box and after i flashed smoothrom also (i called them ghost strokes). After flashing CleanRom all that disappeared. Can't say for sure that CleanROM fixed it, buti haven't had that issue since then.
Sent from my CleanROM N7 using XDA Premium App

BDR456 said:
I had this issue straight out the box and after i flashed smoothrom also (i called them ghost strokes). After flashing CleanRom all that disappeared. Can't say for sure that CleanROM fixed it, buti haven't had that issue since then.
Sent from my CleanROM N7 using XDA Premium App
Click to expand...
Click to collapse
I just flashed SmoothROM last night and had this problem as well. I didn't happen with the stock ROM though. I just bought mine two weeks ago.

Does anyone know if it's software or hardware yet? D=

Hardware problem?

Hello all! I've had this device since September and am very satisfied with it thus far. Finally got root a week ago. But I was just wondering if by chance any here might know what's going on on my phone.
If you look closely at the attached pic, you'll notice a little white sliver of pixels hanging out at the top of every screen, regardless if I'm in stock or custom ROM.
Is this AMOLED problem or touchscreen??? Motorola forums tendered no solutions or answers...
sent from Joker 1.0 on MotoAHD

Looks like you've got some dead/stuck pixels in the display. Nothing you can really do except replace the screen or attempt a warranty replacement.

Thanks for the input. I was afraid of that. I was hoping it was somehow a software glitch, but since rooting and flashing a test ROM, I noticed it's still there.. :banghead:
sent from my **rooted** MotoAHD

[Q] blacks on my screen are not true black; why?

so black screens on my phone look like LCD blacks and glow in the darkness. it's extremely noticeable (i'll get some pics soon) and it happens everywhere, not just in android -- the galaxy note 4 splash screen on boot shows the same bright blacks, as do the backgrounds of twrp and download mode. i'm completely perplexed, i could see some kind of android mis-configuration affecting colors in the OS but i cannot understand why it would be happening outside of android at all.
my rom is cmremix 3.3 with 4/22 slim gapps, i've done a full wipe+reinstall to no avail. all screen-related settings in color control and kernel adiutor are set to default.
any ideas??

developing said:
so black screens on my phone look like LCD blacks and glow in the darkness. it's extremely noticeable (i'll get some pics soon) and it happens everywhere, not just in android -- the galaxy note 4 splash screen on boot shows the same bright blacks, as do the backgrounds of twrp and download mode. i'm completely perplexed, i could see some kind of android mis-configuration affecting colors in the OS but i cannot understand why it would be happening outside of android at all.
my rom is cmremix 3.3 with 4/22 slim gapps, i've done a full wipe+reinstall to no avail. all screen-related settings in color control and kernel adiutor are set to default.
any ideas??
Click to expand...
Click to collapse
Flash a few rom and see if it the same. My blacks are black so it might be what the devs used in the rom. Ask the dev what color code he used and see the color wheel what it looks like in other phones if u enter the color code.
BAD ASS NOTE 4

the problem is persistent across ROMs as well. i tried a lollipop touchwiz rom and then a stock firmware through odin, no change.

Bad phone/screen
BAD ASS NOTE 4

Is your phone a clone? Most clones come with LCD screens instead of AMOLED.

for real? i got my phone from a t-mobile store and it's been working fine since december. two days ago the screen **** the bed sometime after i clean flashed cmremix 3.3 from 3.1. also, please tell me what kind of fake phone runs custom roms for the original phone.

developing said:
for real? i got my phone from a t-mobile store and it's been working fine since december. two days ago the screen **** the bed sometime after i clean flashed cmremix 3.3 from 3.1. also, please tell me what kind of fake phone runs custom roms for the original phone.
Click to expand...
Click to collapse
If you say the phone is an original from the T-Mobile store then my question would be have you ever replaced the screen because of a crack?
My dad cracked his Note 3's screen once and bought a replacement screen from eBay. Little did he know the replacement screen wasn't an OEM replacement. It was a cheap knockoff which caused the screen to look a bit washed out. He never noticed it until I told him.

My first thought is also that you got a clone or a unit with an aftermarket screen, but since you say N4 roms install & run fine, your screen may have just somehow gone bad.
Try odining back to bone stock & see if the issue persists. If it does- warranty exchange.

OuncE718 said:
If you say the phone is an original from the T-Mobile store then my question would be have you ever replaced the screen because of a crack?
My dad cracked his Note 3's screen once and bought a replacement screen from eBay. Little did he know the replacement screen wasn't an OEM replacement. It was a cheap knockoff which caused the screen to look a bit washed out. He never noticed it until I told him.
Click to expand...
Click to collapse
nope, i replaced the housing but didn't mess with the screen or mobo. this problem didn't arise until weeks after the housing replacement as well so i'm loathe to blame it; i would have to agree with the other posters in this thread who suggested the screen is simply broken. i'll try to contact samsung/t-mobile and then decide if i want to replace it or not.

kabuk1 said:
My first thought is also that you got a clone or a unit with an aftermarket screen, but since you say N4 roms install & run fine, your screen may have just somehow gone bad.
Try odining back to bone stock & see if the issue persists. If it does- warranty exchange.
Click to expand...
Click to collapse
will a warranty exchange work if i've tripped the knox flag? i restored the stock firmware+recovery through odin last night and still it hasn't gone away.

developing said:
will a warranty exchange work if i've tripped the knox flag? i restored the stock firmware+recovery through odin last night and still it hasn't gone away.
Click to expand...
Click to collapse
From what I've heard they don't care 99.5% of the time.

developing said:
will a warranty exchange work if i've tripped the knox flag? i restored the stock firmware+recovery through odin last night and still it hasn't gone away.
Click to expand...
Click to collapse
I had to exchange mine for a funky screen too and they didn't say a word about knox. I've never had any trouble getting exchanges on tripped devices, ever. You should be fine, just odin back to stock before you send it back.

Delay in opening Air Command menu

Hi All,
So I got my Note 5 a couple of days everything works fine except for the annoying delay in opening of Air command menu once the Spen is pulled out.
The issue doesn't always happen and I noticed that its slow to open up only when the device has been on sleep mode for a while.There is no perceptible delay when I have been using the device and take out the Spen.
Was wondering if that's how it is or is there something up with my device.
Any pointers would be of great help.
Thanks.

I just got my note 5 and I have the same exact issue. There is a long delay after I pull the pen out and then once it finally comes on, the delay is gone. But when the pen is not used for a while and I try to use it again the delay is back.

gso78 said:
I just got my note 5 and I have the same exact issue. There is a long delay after I pull the pen out and then once it finally comes on, the delay is gone. But when the pen is not used for a while and I try to use it again the delay is back.
Click to expand...
Click to collapse
Thanks Gso78 for the confirmation.
Mine is an Indian version N920G ,Since the issue is not widespread wondering if it has got to do with the variant.
Did you find any solution to it.Anybody else facing the same issue?
Regards.

I have the same issue since the time I bought it.

I also experience this. I don't use the pen much, but find it interesting that, like the OP, the issue happens only after the pen is left in for an amount of time. Then subsequent times in near time to the first, there is no/little delay. Suggests it's a software issue and in that case I'd expect most folks to experience this, barring some hardware revision or variances by carrier version.
Mine is a Verizon U.S. model for the record.
Curious if anyone has found the source of this issue, or how wide spread it is (seems not very wide spread considering how few people responded to this thread).

Just wanted to add my name to this list, I have the Indian N920G running Dr.Ketan ROM L8

Yes. I too have same problem. Indian version

Anyone got this resolved? I'm facing the same issue too.

dedee89 said:
Yes. I too have same problem. Indian version
Click to expand...
Click to collapse
Factory reset didn't solve the issue!

gaugan said:
Factory reset didn't solve the issue!
Click to expand...
Click to collapse
No. I tried many times even after getting two updates. I have given to service center and calling them daily two times. One week over. They admit that the manufacturer didnt install a part. I think they called it "black tape" if i heard it correctly. MADE IN INDIA.

dedee89 said:
No. I tried many times even after getting two updates. I have given to service center and calling them daily two times. One week over. They admit that the manufacturer didnt install a part. I think they called it "black tape" if i heard it correctly. MADE IN INDIA.
Click to expand...
Click to collapse
Ohhh.... I'm planning to visit the service station tomorrow! I hope its not a painful experience.

dedee89 said:
No. I tried many times even after getting two updates. I have given to service center and calling them daily two times. One week over. They admit that the manufacturer didnt install a part. I think they called it "black tape" if i heard it correctly. MADE IN INDIA.
Click to expand...
Click to collapse
Motherboard fault they said. Replaced my piece with a Brand New One!

I have no delay, it comes up right when the pen is completely out of the phone. N920P here

They Repaired my phone (not replaced) but they broke back cover. So another 3 days of delay and frustration. And finally got my phone back working fine. Hope not to go service center anytime in future and i to switch to apple.