Database Develop

Random Reboots.

I have been through 2 phones already, this one here is the worst yet. Within the 1st hour of use it had rebooted 3 times. Now it seems to happen at random.. the phone can be sitting idle on the table and it will randomly reboot.
Anyone else having issues this bad?

Chr0nicDreamz said:
I have been through 2 phones already, this one here is the worst yet. Within the 1st hour of use it had rebooted 3 times. Now it seems to happen at random.. the phone can be sitting idle on the table and it will randomly reboot.
Anyone else having issues this bad?
Click to expand...
Click to collapse
Mine's done it about 3 or 4 times in the month I've owned it... perfectly acceptable and better than my previous Android device... or my iPhone before that as a matter of fact.
I have to wonder if it is due to some piece of software you have installed.

The new phone was received today. I had only added my gmail account to it and not restored anything on it yet. it was bone stock with the exception of the account. and it rebooted now 5 times in the last 1.5 hours. The last 2 times were done AFTER a factory reset

Mine reboots maybe once or twice a week, which while annoying, I can live with.

<Removed>

Youssarian said:
That bad no, but mine had the occasional reboot as well and that was completely stock. It did it after resetting the vivid. The next logical thing was to back off the stock bloatware / spyware one at a time and of course the stock app uninstall is very limited, but I did what I could and it still did it. I blamed Carrier IQ, which may, or may not be true, but I blame it anyway. <G>
Click to expand...
Click to collapse
What I have come down to is returning it to amazon. After speaking to a very polite and helpful rep he had state they have been getting lots of returns for locked bootloaders as the main reason but also random reboots. So he gave me the skyrocket for free i just have to make sure that upon delivery I hand the vivid to UPS. I really Hate to leave HTC but this is something I cannot deal with as I need a phone that works since it is tied to my business.

I've had mine for a couple weeks now and it has done it once. Freaked me out though. It was just sitting on the car seat when I happened to look over, it shut off briefly and went to the splash. I thought about returning it at that momnet... and still am. If It wasn't so new, I probably wouldn't care.

Mine did this while charging and went away with new battery. I called HTC and they sent one out.

Bad batch of phones?
There is another, older thread on this same issue. I have experienced reboots three times in this first month, but not in the past week or so. Based on your experience, and some other issues in other threads, I think there must have been a bad batch of phones. It's too bad a replacement did not make things better.

I used to have random reebots, but for the past couple weeks it hasn't happened. Not worried about it anymore.

I don't really get random reboots anymore but it freezes sometimes while trying to lock/unlock the phone. Just emailed HTC to see if my device is faulty or if its a known issue.
Sent from my HTC PH39100 using XDA App

travisxcore said:
I don't really get random reboots anymore but it freezes sometimes while trying to lock/unlock the phone. Just emailed HTC to see if my device is faulty or if its a known issue.
Sent from my HTC PH39100 using XDA App
Click to expand...
Click to collapse
I just got a call from HTC regarding a failure to help resolve an issue and the bad review i gave them via their survey lol.

[Q] Should this phone be returned?

My o2x has a lot of bugs and hardware problems;
Display has bad light bleeding from 3 corners
Wifi sometimes does not show access points (fixable by reboot)
Memory card sometimes becomes read as 00 (not 0kb or anything just 00) when going into internal memory (has to be removed and re inserted for it to work, sometimes even reboot, happened with other cards of different brands)
Network data sometimes disconnects even with full reception bars
EXCESSIVE slowdowns, some games run at a good framerate and some other times are completely unplayable (even basic games such as angry birds) even when ram has been emptied.
I just returned it to the shop and they basically said this is normal with smart phones bla bla bla. I personally do not agree that these problems should be present in a phone that I paid 485euros for.
So my question is are these issues supposed to be enough grounds for the phone to be returned? I am on V20g non rooted

It'd you paid 485 euros, return it even if everything is working. At that price you get galaxy s3 these days.

this was early summer 2011

andrazz90 said:
this was early summer 2011
Click to expand...
Click to collapse
And your posting this now?
Sent from my Optimus 2X using xda app-developers app

I don't think these issues were there from day one ^^
@op: You could try cm7, cm9 or some other custom rom and see if the issues still exist (except for the bleeding, that seems like a hardware fault).
Else I'd try everything to get it swapped/return it. This definitely NOT normal and anyone telling you so is just a moron.

dakoookie said:
And your posting this now?
Sent from my Optimus 2X using xda app-developers app
Click to expand...
Click to collapse
some of these issues were present, but always thinking they were random bugs, and they will be fixed with updates, which only one arrived on my UK o2x, the gingerbread release and no other update since then. But now i came to the realisation that this should not be happening, regardless waiting for updates. Now with regards to rooting it, i cant do that as it still is under warranty until july 2013

You can always NVflash a stock image before returning the phone, no permanent damage done to warranty.

Screw Up Stories?

I don't know if this will catch on or not, but I'd like to hear people's stories on how they screwed up or thought they screwed up their phone and fixed it? I think this could be an interesting thread with plenty of good stories and such

absoluterebirth said:
I don't know if this will catch on or not, but I'd like to hear people's stories on how they screwed up or thought they screwed up their phone and fixed it? I think this could be an interesting thread with plenty of good stories and such
Click to expand...
Click to collapse
I haven't screwed this phone up but I remember when I first started rooting phones I bricked my Vibrant (Galaxy S). I think I bricked it because I flashed the wrong radio or something. After that I have never bricked another phone. **Knock on wood**
Now I take extra caution and read extensively before rooting, flashing Roms, kernels etc.
sent from my neXus 5

Heres how i screwed my Nexus 5 on stock, I forgot to charge it and its now dead..
How i fixed it? I charged it :good:

I didn't because I actually read the stickies on the top of the general forum.
/Thread
Sent from my Nexus 5 using Tapatalk

Just took apart my Nexus 5 after it was unresponsive after a week of putting into rice/silica gels. No idea of what I am doing. I have never opened anything up in my life. Soaked motherboard into isopropyl and cleaned it with toothbrush, dropped it like 10 times, ripped a couple of cables. Should be all good though. Will post if it worked.

eastpac said:
Just took apart my Nexus 5 after it was unresponsive after a week of putting into rice/silica gels. No idea of what I am doing. I have never opened anything up in my life. Soaked motherboard into isopropyl and cleaned it with toothbrush, dropped it like 10 times, ripped a couple of cables. Should be all good though. Will post if it worked.
Click to expand...
Click to collapse
Yeah, ripping cables is probably not going to turn out "all good". Just my opinion

markdapimp said:
Heres how i screwed my Nexus 5 on stock, I forgot to charge it and its now dead..
How i fixed it? I charged it :good:
Click to expand...
Click to collapse
Please accept this Thanks as your post is very accurate and straight to the point.:good: Many of us have had that experience before whether it's forgetting to charge it over night by not plugging it into a charging source or it running out of battery power from heavy/extented usuage and not being able to charge it immediately after.:highfive:

DON`T USE TOOLKITS, these are related to most screwups Oh and get your rooting/flashing/adb skills up to par

FuMMoD said:
I didn't because I actually read the stickies on the top of the general forum.
/Thread
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Same!
Sent from my Nexus 5 using Tapatalk

I've only totally bricked one device, that was a sprint HTC evo (og evo). I got a replacement device via insurance and due to new firmware, I bricked it trying to root it/set s-off. No fix possible, only a new phone.
As far as nexi, nexus 5 specifically, I've soft bricked it a ton of times. But, one of the reasons I love the nexus brand, its never taken any more than a nandroid restore or only once a revert to stock. Unless you Dev test (and knowingly flash untested fw) or just start randomly picking zips and flash a modem or boot loader from a different device I've found it damn near impossible to make a nexus device unrecoverable.
I did initially flash the multi-boot mod w an incompatible ROM (beanstalk) and a kernel that really didn't like the multi-boot idea either (don't remember which ver of which kernel ATM). I was stuck on the "Google" boot loader screen for hours til I tried flashing a different ROM (which also changed the kernel) and trying again. Frustrated the hell out of me, kept phone unusable for almost a whole day, and wasted a ton of my time due to my laziness to read the whole thread.
Best advice ever given on XDA, whether you are a novice/learning/a noob or a android pro many years of experience or even a skilled developer.....
ALWAYS, ALWAYS, ALWAYS... did I say ALWAYS read the whole op or even better whole op and hopefully 90%+ of the thread before you try something you are unsure of.
Sent from my Nexus 5 using Xparent Skyblue Tapatalk 2

helioXverse said:
As far as nexi
Click to expand...
Click to collapse
Nexuses

Had the device perfectly set-up, with a few twrp backups as well and then for no reason...moved those backups from the device to the pc (probably in order to free some space). Then in a sequence of screw-ups, downloaded Flashify and wiped the cache and and dalvik cache from within the app (thinking it would be cool)...AND...bootloop! No backups...nothing! Booted to recovery...wiped cache/Dalvik the usual way, still nothing! Wiped data...nothing! Couldn't get ADB to work in the recovery. Finally -> Bootloader -> Fastboot Flash Stock ROM!
Did not stop though. in the next 5 minutes I was back with custom recovery, root and Titanium backup...ready to get back the device in shape (done and dusted as I type )

Reading the undervolting thread I decided to go -75 across the board. I succeeded but then tried to push it lower. Bootloops occurred. Backup copied back to SD card from PC failed to restore (said data failed. This was my first time restoring a ROM on the Nexus 5. If someone has insight as to why this happened it would be appreciated). Decided to go aosp and flash Rasta + trinity kernel but for some reason my mobile data wouldn't activate nor could I update PRL or profile by clicking on the usual option even after reboot and continuously clicking. Now I'm just getting my phone back to the original state it was in before I screwed up my UV values. Cataclysm + ElementalX #Life of a Phone Nerd
Sent from my Nexus 5 using XDA Premium 4 mobile app

gee2012 said:
DON`T USE TOOLKITS, these are related to most screwups Oh and get your rooting/flashing/adb skills up to par
Click to expand...
Click to collapse
I actually used a toolkit to return mine back to stock after i shipped it out to LG for repair after my son dropped. It was much easier for me than to write out the commands. took me about 10 minutes and that was because I locked the bootloader before flashing a zip. and i had to go back yada yada but worked out fine.

Screwed up 2 Galaxy S2's, first one because I didn't pay close enough attention to the brickbug, second one because it just died... Due to the brickbug. Other than those I've never killed a phone. I thought I had broken my friends Nexus 5 though, I unlocked it and went to root it for him but TWRP/CWM couldn't mount any partitions because it's "encrypted". Got it fixed though.
I've killed xbox's, PSP's, everything. It's all part of the learning process.

...When I first got my Nexus 5 in MTP on my Windows PC I had my phone hooked up to, on Internal Memory I saw a folder called sdcard that was not there before that was supposedly empty according to MTP. Deleted it. Turns out it was a symlink screwup in MTP, and it deleted my entire SD card including photos, luckily the important ones were already uploaded to Facebook and such. Now I backup my phone almost daily just in case.
I bricked my Archos Home Connect 35 once. Kinda my fault. I had set the bootloader to boot SDE firmware for it defaultly on boot. (Dev edition firmware from Google that was rootable). I updated from .82 firmware to .83 firmware, forgot to change that. It took the SDE firmware out, normally youd have to reinstall it, and since it was set to boot from that in Archos. mess of a firmware and bootloader, it would just bootloop because the SDE firmware wasnt there. No way to get out of it. RMA'd it and got a new one from Archos though. Never again, will always just manually select the SDE Dev Edition firmware when/if i ever reboot it. (Its just a Alarm clock mostly that plays Pandora occasionally. it last went 300 days without a reboot until it hard locked and I had to reboot. )
Never had a unrecoverable problem with my Galaxy S4, or my Nexus 5.Worst case with the S4 I Odin'd back to stock firmware. Nexus 5 got a corrupt data or cache partition once, i could have ran fsck but I flashed stock images instead.

I was having an issue having my phone seen on my PC. This is after I've rooted... Transferred music and pics from PC to phone, so I knew my drivers were installed. So I tried going back to stock. I downloaded the stock image and tried fastboot flashing. My download was corrupted. It got froze sending the radio. Froze for 30 min... Just kept saying sending. So I finally unplugged and rebooted to bootloader as everything else has been wiped. Tried again and it froze again at sending the boot loader. Froze for 30 min. I unplugged and tried rebooting. It never turned back on. No charging indication or anything. Officially bricked. I had tmo send me a new one and I'm returning the old one today. Wish me luck
First brick of my life and I've been rooting and modding since the OG Nex1
Sent from my Nexus 5 using Tapatalk

My GPS was working intermittently so I applied the cardboard fix and now its great. But in the process I damaged my back cover and now NFC and wireless charging don't work.
Really wishing I just RMA'd it.
Sent from my Nexus 5 using XDA Premium 4 mobile app

Had anyone successfully returned their Note 4 due to Lag/Sluggish Performance?

I was just curious if anyone has successfully done this. Did they give you and trouble? Did you do it at the T-Mobile store? Did you have yo pay anything? Mine doesn't really lag, i would more so call it stuttering. For example, when i scroll using tapatalk it isn't smooth, it stutters a lot. Once in a while exploring it different apps or system there is some noticeable stuttering. Again, it is for a long period of time.. just slightly. I have tried several of the tips posted in here and it still happens. I am not asking for help, i just want to know if anyone has returned it and how it went. I am on day 10, and want to see if it is worth going in the store before 14 days is up. Thank you!

bigmase23 said:
I was just curious if anyone has successfully done this. Did they give you and trouble? Did you do it at the T-Mobile store? Did you have yo pay anything? Mine doesn't really lag, i would more so call it stuttering. For example, when i scroll using tapatalk it isn't smooth, it stutters a lot. Once in a while exploring it different apps or system there is some noticeable stuttering. Again, it is for a long period of time.. just slightly. I have tried several of the tips posted in here and it still happens. I am not asking for help, i just want to know if anyone has returned it and how it went. I am on day 10, and want to see if it is worth going in the store before 14 days is up. Thank you!
Click to expand...
Click to collapse
They'll charge you a $50 restocking fee as the return will fall under "buyer's remorse." You don't need to give a specific reason other than you don't want it. There's no way of avoiding the restocking fee on a return that leads to a full refund, even if it's defective.

Hmm and if i pay $50 for a new device there is no guarantee the problem will be solved. Interesting. .

I didnt have to pay cause it was under 14 days for store and on 21 days if u do online.You could get another phone or same different color I didn't pay any fee. If u pass that time I would do a warranty exchange if u have jump it is $5 processing fee

raw2000j said:
I didnt have to pay cause it was under 14 days for store and on 21 days if u do online.You could get another phone or same different color I didn't pay any fee. If u pass that time I would do a warranty exchange if u have jump it is $5 processing fee
Click to expand...
Click to collapse
Don't know how Tmobile works in other states but here even switching to a different color is considered another handset purchase and you'll still be charged the restocking fee.
Sent from my Nexus 5 using XDA Free mobile app

They called it a preference exchange and said i didnt have to pay cause it was under the 21 days i did it over phone

raw2000j said:
They called it a preference exchange and said i didnt have to pay cause it was under the 21 days i did it over phone
Click to expand...
Click to collapse
Interesting. Our stores here in Oregon will NOT let you switch colors without paying the restocking fee. I guess you could always ask for a managers override
Sent from my Nexus 5 using XDA Free mobile app

I di over phone so maybe atores r different thats y i dont deal with them lol

UPDATE:
Well, as i was using Odin and going back to stock I tested again and to my surprise the lag/stutter was gone. I tested everything where I was experiencing this. All gone. Then I rerooted and added custom recovery and still good to go. Weird.. maybe Samsung had a bad "flash" when building my Note 4.
With that being said, to whomever is having the same experiences I was, this is what I recommend! BTW, T-Mobile was going to do a free exchange due to buyers remorse. I called them back and said I would not be coming in

Were you using Wanam Xposed?

I haven't but I will. I already tried using other ROMs, factory resetting, everything. Absolutely love the phone, but TouchWiz kills the phone for me. It slows the phone down a lot (in my case at least) and it stutters. So, I'll be returning it and getting a Nexus 6.

bigmase23 said:
UPDATE:
Well, as i was using Odin and going back to stock I tested again and to my surprise the lag/stutter was gone. I tested everything where I was experiencing this. All gone. Then I rerooted and added custom recovery and still good to go. Weird.. maybe Samsung had a bad "flash" when building my Note 4.
With that being said, to whomever is having the same experiences I was, this is what I recommend! BTW, T-Mobile was going to do a free exchange due to buyers remorse. I called them back and said I would not be coming in
Click to expand...
Click to collapse
The note 4 is a monster. The stock rom is the issue. Now that we have custom roms all is well. I'm on firekat. .....this phone is beast. I'm running about 10 xposed mods,over clocked to 2.9ghz, battery life is 50% better than stock even with all that jazz going on and I just added this SD adapter now I'm noting just over 1tb of space with rw speeds around 60. Font return the device I was having the same issues til yesterday
Sent from my SM-N910T using Tapatalk

I haven't experienced any lag ... I'm currently running Custom Stock ROM ... And deleted everything that I didn't had to use ....

I have never experienced these crazy lags. It does stutters sometime, but all computers stutter sometime... You should see my ipad3. I'm on stock and not rooted just yet.

If you're within the 14 or 21 days they have to exchange it if something is wrong with the phone. It's not buyer's remorse.
Unless of course you want a different color then that's different.
I think I might return mine because I've had lag almost everywhere from home screens to apps, Internet and even videos.
I'm still completely stock, never had this type of issues with my Note 3. ****, even disappearing icons, look at the bottom messaging app.
Icon gone after a reboot, had to reboot again.
I was wondering, for those that have exchanged it.
Did the replacement work out better for you??
I'm debating whether returning it or just rooting it and slapping a rom on. But I don't want to keep it if it's the actual phone.....
---------- Post added at 01:46 PM ---------- Previous post was at 01:44 PM ----------
Nvm couldn't attached the pic to show you the missing icon.

rambo8987 said:
The note 4 is a monster. The stock rom is the issue. Now that we have custom roms all is well. I'm on firekat. .....this phone is beast. I'm running about 10 xposed mods,over clocked to 2.9ghz, battery life is 50% better than stock even with all that jazz going on and I just added this SD adapter now I'm noting just over 1tb of space with rw speeds around 60. Font return the device I was having the same issues til yesterday
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
which xposed mods are you running. How did you overclock, Did you flash a different kernel?

eduardmc said:
which xposed mods are you running. How did you overclock, Did you flash a different kernel?
Click to expand...
Click to collapse
Wan man, root cloak ig and vine Downloader obb files to SD card etc. I used cpu controller on market I'm ok firekat rom
Sent from my SM-N910T using Tapatalk

For all the people claiming there is no lag, THERE IS LAG. But only if you root it and if you don't properly fix the S health issue.
I thought all those people were crazy for claiming there is lag until I experienced it myself. Do the clear data/reboot method on s health and then go back on wanam and check the option to fix s health. That removed my lag
And also there is a lag on the recent apps hard key, it's pretty slow just like on my S5. On my S5 I enabled soft keys/on screen keys and that lag was gone but the lag was still there for the hard keys on my S5.
I tried enabling soft keys on the Note 4 but it keeps crashing "system UI" every 2 seconds, I am able to put soft keys on my s3-s5/htc m7 but how come not on the note4?

*UPDATE
So I contacted Tmo today just so they can note what's going on so I have no issues exchanging it.
The rep recommended to take out my SD card and try it without. And if I wanted to, to do a reset.
I had used the same SD card since my S2 Days so I didn't think nothing of it when I started using with my Note 4.
Anyways, long story short. SD card is out, factory reset it and now my lag is practically all gone. I've been using for about 5 hrs now.
So it was the SD card causing all if not most of the problem.
I'm going to format my SD card with this phone and hopefully I won't need a new SD card lol.
Anyways, something for you also having lag to try it out in case you have a similar situation as me.

ThC23 said:
*UPDATE
So I contacted Tmo today just so they can note what's going on so I have no issues exchanging it.
The rep recommended to take out my SD card and try it without. And if I wanted to, to do a reset.
I had used the same SD card since my S2 Days so I didn't think nothing of it when I started using with my Note 4.
Anyways, long story short. SD card is out, factory reset it and now my lag is practically all gone. I've been using for about 5 hrs now.
So it was the SD card causing all if not most of the problem.
I'm going to format my SD card with this phone and hopefully I won't need a new SD card lol.
Anyways, something for you also having lag to try it out in case you have a similar situation as me.
Click to expand...
Click to collapse
I did sane took out sd card played wirh it lag gone pyt sd card in again lag still gone

Galaxy S6 AT&T 64GB Dies instantly, Deepsleep or hardware problem?

Hay guys,
Edited: on 07/07/2016: Problems First; My AT&T Galaxy S6, reboots randomly, dies instantly and some times freezes, doesn't matter what app i am on. The full story is here if interested, please read below;
I bought a used AT&T Galaxy S 6, 64 GB Black sapphire, Now running 6.0.1 (i sideloaded it) and it has a problem which you guys call it deep sleep problem (I call it, dying phone with no reason) when i bought it, it was running 5.1.1 then (probably BOJ7), and the second day i noticed that it was dead, (i remember i was taking some selfies, pictures, i locked it and after more or less 15 or 20 minutes i wanted to take some more pics, i saw it was not waking up). And to my surprise, I have checked it, when i call the number which is in that phone, the call goes and i can listen on my other phone that the bill is ringing but actually my device doesn't ring at all (while dead) (I have also seen once that the notification LED was blinking Blue, yet the phone was off, itself)
So, story short when i saw the device was unexpectedly off i tried to switch it on by the following methods;
i pressed all the button many times but it didn't respond until, i pressed and kept holding recovery boot combination i.e. volume down + volume up + Power buttons and it booted.
Later on it was good, after two days, it did it again.
Now my concern was rising about Galaxy S6's sudden deaths, (I still don't know whether i should call it a deep sleep and awake problem or it is something related to hardware) so, i thought lets find a way and upgrade it to MM. I searched the xda and found this
Updating to Android 6.0.1 G920AUCU3CPD6 Step by Step {http://forum.xda-developers.com/att-galaxy-s6/general/updating-to-android-6-0-1-g920aucu3cpd6-t3371884}
I upgraded my phone and thought it's fine now, but to my surprise, the phone went off while it was in my pocket with almost 70% battery charged. I was shocked, yet started it with the buttons combo, and yesterday when i left it charging while the battery was about 87% charged, I thought let it go to 100% but when i picked it up after 15 minutes and pushed the home button to see the status the phone was dead again with a RED LED light on while the screen was off, when i pressed the home OR power button the screen showed a big green battery with 100 % Charge (which was indicating as i powered it off and kept charging)
Now my question is that " What the hell is going on?"
If it was a rooting problem? Then, I did an odin flash of BOJ7 with all four files AP, CP, CSC and his child. which should have removed the rooting, and to confirm it whether my device is rooted or the KNOX tripped or not, i have checked the knox it is 00000 which means the KNOX is not tripped.
Please help me guys, this was my dream phone, i can't buy a new one with warranty, and i can't loose it or live it with this problem, my days suck.
please help me,

And today I've seen a new thing may be it's the real problem but I really got it today. I was surfing the net and twitter my AT&T Galaxy S6 suddenly went off and I had to force start it.
Hay guys, i need your help, am i missing you all?

Hay guys, Talvigi back,
As far as no body is interested in my post and may be no one has faced such problem before, so, i am back with some updated information;
Day before Last night, I was very much worried about my phone's behaviour, even i was thinking to show it's way out. But when i was a bit asleep yet awaken i thought way not try to factory reset the device from recovery, formate system devlock and cache partitions?
And i did it while i was half asleep and let the device update it's builtin softwares and WOLLA, it's second day my beloved AT&T specific Galaxy S6 hadn't misbehaved yet, (till now, may be it will make me lying just now)
Edit: (Third Day):
Third Day guys its third day and still my phone has not misbehaved after the above mentioned factory reset, and i hope this will continue to work like that.
Edit: Fifth day:
Sorry Sammy boy but you are a sucking OEM, after two good days my AT&T Galaxy S6 is again misbehaving with me, it again deep slept, just after seconds when i was surfing the facebook and i got lock my device for some seconds. As soon as i wanted to unlock it again i saw that the device was once again not waking up hence i had to push both volume and power buttons to start it.
And it did the same thing while it was kept on my table for a couple of hours.
It's now making me crazy to sell it again and go for a galaxy S5, it least i haven't seen this problem, i actually haven't listened this kinda problem in them from any where.
Edit; Now after a lot of days of sudden deaths and instant restarts, it has started to freeze now, I have not seen this before. I mean when I am using facebook it freezes but doesn't restart as far as I have seen it twice with freeze problem. Now I can say that it is indeed a software problem may be we can suggest it to be a kernel related problem.
So is it because I might have used a 32 GB specific ROM on a 64 GB device?
Is there a real difference between 64 GB and 32 GB ROM.
Hell with the AT&T Galaxy S6.

talvigi said:
Hay guys, Talvigi back,
As far as no body is interested in my post and may be no one has faced such problem before, so, i am back with some updated information;
Day before Last night, I was very much worried about my phone's behaviour, even i was thinking to show it's way out. But when i was a bit asleep yet awaken i thought way not try to factory reset the device from recovery, formate system devlock and cache partitions?
And i did it while i was half asleep and let the device update it's builtin softwares and WOLLA, it's second day my beloved AT&T specific Galaxy S6 hadn't misbehaved yet, (till now, may be it will make me lying just now)
Edit: (Third Day):
Third Day guys its third day and still my phone has not misbehaved after the above mentioned factory reset, and i hope this will continue to work like that.
Edit: Fifth day:
Sorry Sammy boy but you are a sucking OEM, after two good days my AT&T Galaxy S6 is again misbehaving with me, it again deep slept, just after seconds when i was surfing the facebook and i got lock my device for some seconds. As soon as i wanted to unlock it again i saw that the device was once again not waking up hence i had to push both volume and power buttons to start it.
And it did the same thing while it was kept on my table for a couple of hours.
It's now making me crazy to sell it again and go for a galaxy S5, it least i haven't seen this problem, i actually haven't listened this kinda problem in them from any where.
Hell with the AT&T Galaxy S6.
Click to expand...
Click to collapse
May I ask, Why am I tagged in this?

hyelton said:
May I ask, Why am I tagged in this?
Click to expand...
Click to collapse
Sorry man, @hyelton: but you are the great hero for me,
You have been so much helpful to me as well as to many others i have seen,
And to tell the truth, i didn't tag you to help me specifically on this problem,
but i knew you will be the only one to notice me in this crap.
And i believe you have read my problem and have at least thought once, about my situation, haven't you?
And i also know you can off course guide me, or lead me a way through.
Please don't be rude, i beg your kind honour to please suggest me a way out there, any way out! :crying::fingers-crossed::crying::fingers-crossed:
Because there are many people in this forum but you can see no one, no one even noticed my problem.

Hello, I was tagged in your threads and received the notification while I was sleeping. First of all my Galaxy S6 was bought by me on May 6 2015 at an Official AT&T Store, the same Store were, nine years ago, I open a contract account for mobile service. Before Android phones I was a Blackberry user. Never root a phone, never side loaded a Google Platform Upgrade, never bought a used phone. The only time I bought a phone outside an Official AT&T Store was when I bought a brand NEW Google Nexus 5 at Amazon and God knows that my former Nexus 5 was the best phone I ever owned. I always owned the top of the line Blackberry, the Bold series. And all my formers Android phones bought at AT&T were Flagships phones at the moment I bought them. OK now, I read all your threads and when you applied a Factory Data Reset you do, in my humble opinion, the right thing . Unfortunately the problem at your phone is beyond a Factory Data Reset. My advise is that you must go to an AT&T Official Store and ask for a new Nano Sim Card. If that's not work go to an Official Samsung Repair Store or Center. If that's not work, then my friend, take out the Nano Sim Card of your Galaxy S6 and bought a NEW Google Nexus 6p directly from Google or Amazon and push the Nano Sim Card in. You are going to have peace on earth running a Google Nexus phone at AT&T. Remember my fried, NEVER AGAIN buy an used phone and by the way don't side loaded Google Platform Upgrade. Just wait for the OTA regarding Platform Upgrade. I'm really sorry for the bad experience with your Galaxy S6.
Sent from my SAMSUNG-SM-G920A using XDA-Developers mobile app

emilioaponte said:
Hello, I was tagged in your threads and received the notification while I was sleeping. First of all my Galaxy S6 was bought by me on May 6 2015 at an Official AT&T Store, the same Store were, nine years ago, I open a contract account for mobile service. Before Android phones I was a Blackberry user. Never root a phone, never side loaded a Google Platform Upgrade, never bought a used phone. The only time I bought a phone outside an Official AT&T Store was when I bought a brand NEW Google Nexus 5 at Amazon and God knows that my former Nexus 5 was the best phone I ever owned. I always owned the top of the line Blackberry, the Bold series. And all my formers Android phones bought at AT&T were Flagships phones at the moment I bought them. OK now, I read all your threads and when you applied a Factory Data Reset you do, in my humble opinion, the right thing . Unfortunately the problem at your phone is beyond a Factory Data Reset. My advise is that you must go to an AT&T Official Store and ask for a new Nano Sim Card. If that's not work go to an Official Samsung Repair Store or Center. If that's not work, then my friend, take out the Nano Sim Card of your Galaxy S6 and bought a NEW Google Nexus 6p directly from Google or Amazon and push the Nano Sim Card in. You are going to have peace on earth running a Google Nexus phone at AT&T. Remember my fried, NEVER AGAIN buy an used phone and by the way don't side loaded Google Platform Upgrade. Just wait for the OTA regarding Platform Upgrade. I'm really sorry for the bad experience with your Galaxy S6.
Sent from my SAMSUNG-SM-G920A using XDA-Developers mobile app
Click to expand...
Click to collapse
Thank You sir for such a detailed reply, my bad luck with S6 is that I love it so much but when it comes to your life you will better lose your eyes. I think I will somehow sell it back and will not buy any second hand phone again.
Sent from my SAMSUNG-SM-G920A using Tapatalk

talvigi said:
Thank You sir for such a detailed reply, my bad luck with S6 is that I love it so much but when it comes to your life you will better lose your eyes. I think I will somehow sell it back and will not buy any second hand phone again.
Sent from my SAMSUNG-SM-G920A using Tapatalk
Click to expand...
Click to collapse
My friend please don't lose your eye and work hard so you can buy a brand new Samsung Flagship, Galaxy S7 or a Note 6. Don't forget, far beyond the Manufacturers Flagships, far beyond your worst nightmare is the Google Nexus Phone .
Sent from my SAMSUNG-SM-G920A using XDA-Developers mobile app

Well thanks for the suggestion but do you know, I will have to work 8 hours a day for five month and save 50% of that earnings, if I want to buy a brand new Galaxy S7, and for you my dear, that would be not more then 15 days half earning or 8 days full. So, to buy a flagship, in my dreams! Yet I will try to manage on a Huawei X5 or oppo F1
Sent from my SAMSUNG-SM-G920A using Tapatalk

emilioaponte said:
My friend please don't lose your eye and work hard so you can buy a brand new Samsung Flagship, Galaxy S7 or a Note 6. Don't forget, far beyond the Manufacturers Flagships, far beyond your worst nightmare is the Google Nexus Phone .
Sent from my SAMSUNG-SM-G920A using XDA-Developers mobile app
Click to expand...
Click to collapse
talvigi said:
well thanks for the sugg estion but do you know I will have to work 8 hours a day for five month and save 50% of that earnings, if I want to buy a brand new Galaxy S7, and for you my dear that would be not more then 15 days half earning or 8 days full. So, to buy a flagship, in my dreams! Yet I will try to manage on a Huawei X5 or oppo F1
Sent from my SAMSUNG-SM-G920A using Tapatalk
Click to expand...
Click to collapse
Sent from my SAMSUNG-SM-G920A using Tapatalk

talvigi said:
Well thanks for the suggestion but do you know, I will have to work 8 hours a day for five month and save 50% of that earnings, if I want to buy a brand new Galaxy S7, and for you my dear, that would be not more then 15 days half earning or 8 days full. So, to buy a flagship, in my dreams! Yet I will try to manage on a Huawei X5 or oppo F1
Sent from my SAMSUNG-SM-G920A using Tapatalk
Click to expand...
Click to collapse
My dear friend at 16 years old I left my parents house and work hard and studied hard. Now I'm 60 years old and still work hard. That's the way life goes, don't fight it. You are a good person , work hard and enjoy your life and all the Android phones you are going to have.
Sent from my SAMSUNG-SM-G920A using Tapatalk

Somebody, help me, please. My system is really unsustainable and doesn't tell me when to stop working and when to restart.

Edit; Now after a lot of days of sudden deaths and instant restarts, it has started to freeze now, I have not seen this before. I mean when I am using facebook it freezes but doesn't restart as far as I have seen it twice with freeze problem. Now I can say that it is indeed a software problem may be we can suggest it to be a kernel related problem.
So is it because I might have used a 32 GB specific ROM on a 64 GB device?
Is there a real difference between 64 GB and 32 GB ROM.
Sent from my LG-V410 using Tapatalk

Well, guys i somehow have been able to maintain my device to keep away from all those misbehavings which it had to do all the time. But i don't want to exaggeratedly lie that they are gone now, they are here, and they also sometimes show there faces but rarely, very rarely indeed. It all could happen after a couple of factory resets and keeping the device away from auto updates mostly from googleplaystore.

Well I have ODIN back and now i'm back on 5.1.1 BOJ7. And surprisingly the reboots are still here, I think, will have to kill my wish of being on Galaxy S6 for some more months and I will have to go back to the market and buy a LG G4 or Galaxy S5 may be?
People say their experience with Marshmallow has not been good but i would mine was the worst with S 6.
I think this device has a factory fault, but as far as i have bought it in used condition and the device is an AT&T device, that too out of the US, so samsung would surely won't help me, neither i have any warranty here.
I hat you Samsung/AT&T for making such a piece of crap.

Any body in this world has the same kind of problem with the Galaxy S6 AT&T 64 GB, or I am alone?