Related
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
905 stock rooted and I was having data drops like crazy last week. I have had a bionic since launch and have never had any data problems. Last week was terrible, couldn't hold a 4g connection (blue to white constantly). They sent me a new Sim card, it seemed to make it worse the first 2 days, so I asked for a replacement phone. Well after the first 2 days on the new sim, my bionic starting working flawlessly again. Now I have a replacement phone sitting here that I don't think I need. Should I send back the replacement? Or take the certified "like new"? Am I better off keeping my original? Help me decide, thanks!
I feel like it was a network error on Verizon's part, not an issue with my sim card but guess I'll never know.
y3llo said:
905 stock rooted and I was having data drops like crazy last week. I have had a bionic since launch and have never had any data problems. Last week was terrible, couldn't hold a 4g connection (blue to white constantly). They sent me a new Sim card, it seemed to make it worse the first 2 days, so I asked for a replacement phone. Well after the first 2 days on the new sim, my bionic starting working flawlessly again. Now I have a replacement phone sitting here that I don't think I need. Should I send back the replacement? Or take the certified "like new"? Am I better off keeping my original? Help me decide, thanks!
I feel like it was a network error on Verizon's part, not an issue with my sim card but guess I'll never know.
Click to expand...
Click to collapse
if it was me i would give it about a day or 2 and if the problem happens then switch phones you got 5 days to send it back (i did not send back my replacement phone for 2 weeks and never got billed or anything at all)
Mine replacement is on the way.
y3llo said:
905 stock rooted and I was having data drops like crazy last week. I have had a bionic since launch and have never had any data problems. Last week was terrible, couldn't hold a 4g connection (blue to white constantly). They sent me a new Sim card, it seemed to make it worse the first 2 days, so I asked for a replacement phone. Well after the first 2 days on the new sim, my bionic starting working flawlessly again. Now I have a replacement phone sitting here that I don't think I need. Should I send back the replacement? Or take the certified "like new"? Am I better off keeping my original? Help me decide, thanks!
I feel like it was a network error on Verizon's part, not an issue with my sim card but guess I'll never know.
Click to expand...
Click to collapse
I too am having the same connectivity issues. Blue/White strobe. They're sending me another Bionic. I fully expect the new one to have the same issues. Two of my friends have the same phone; both are having the same issue ever since the .905 upgrade.
Try this...
Power off pull the SD card. Power on fully. Power off. Reinsert the SD card and power on.
Don't ask! I read this somewhere and was willing to try anything and....oddly enough, it worked.
Thanks to the forgotten tipster.
D
I add the step of take out sim card,when removing the sd card, which i read at droidhive.com when it existed.
Sent from my DROID BIONIC using xda premium
I've got a Verizon N4. I have had it since *October 23rd*edit. I haven't had any issues with lag until two days ago. Yesterday it got to the point where I couldn't even turn on my screen or navigate anywhere. When I did a hard reset the phone would get stuck in the Verizon boot screen until I pulled the battery. The phone got catastrophic lag twice yesterday and locked in the boot screen twice. I took the phone into a Verizon store and they swapped it out for a new one no questions asked even though it was past the grace period. I was worried since it wasn't showing any issues at the store but that wasn't an issue. Hopefully this new one won't have any issues. Just wanted to give you guys a heads up in case there are more similar issues.
September?
Had a situation last night, wanted to know if anyone else had experienced it.
I had a Note 4 on Verizon, when I got my Nexus 6 I just cut the sim card and put it into my nexus 6, no problem. I haven't sold my Note 4 yet but plan on it, so last night I factory reset the Note 4 to sell it. As soon as the Note 4 factory reset/rebooted, my Verizon service stopped working. Couldn't make calls, send texts or use data (wifi worked fine). Nothing else changed, etc.
I had to put the sim card back in the Note 4, reactivate the Note 4 on Verizon.com then put it in the Nexus 6 to get the service to work back.
Was this some fluke or was it really because I factory reset my Note 4? When I factory reset my Note 4 the sim card was in the Nexus, but it's the only thing I could think of. Before I switched sim cards/reactivated I reboot the Nexus several times, even factory reset it and clean flashed Chroma/Francos to make sure it wasn't something with the rom/kernel.
If this is going to happen, how can i sell the Note 4 but keep my service from going out?
Thanks!
I'm not sure what occurred, but I doubt that is was because you FR'd the Note 4.
I'd believe something more nefarious with VZ's system than that. Plenty of people including yourself have moved an existing SIM to the N6 to work on the network.
Get it back on the N6 and see what you get.
RW-1 said:
I'm not sure what occurred, but I doubt that is was because you FR'd the Note 4.
I'd believe something more nefarious with VZ's system than that. Plenty of people including yourself have moved an existing SIM to the N6 to work on the network.
Get it back on the N6 and see what you get.
Click to expand...
Click to collapse
after i reactivated the sim card in the Note 4, i have put it back in the nexus 6 and it's working fine. I'll FR the Note 4 again tonight to see if it happens again, but I also thought it was pretty weird that it would've happened.
tmhiott said:
after i reactivated the sim card in the Note 4, i have put it back in the nexus 6 and it's working fine. I'll FR the Note 4 again tonight to see if it happens again, but I also thought it was pretty weird that it would've happened.
Click to expand...
Click to collapse
hit VZ's site now and see if the note 4 was replaced by a non-VZ device.
Turning on the 4 and FR really shouldn't affect the other at all at this point...
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?