Related
The ICS update finally appeared in France for stock Note.
It appears the update was pulled shortly after because a lot of users bricked their Notes in the process.
Moral of the story: don't update as soon as you see an update, but wait...
Samsung really sucks at software development.
Sent from my GT-N7000 using xda app-developers app
as tu une source s'il te plait merci
Samsung france facebook page for the source.
SFR update and XEF for the short time i spent there.
i'm in the same case except that i'm booted and running( for me was a FOTA update, wich installed nicely except with a "failed " message after the fist boot), but the phone cannot be mounted by any ways under windows now ( even with drivers reinstalled ).
But some seems to be blocked in bootloop
Epic fail on this one, especially just before a week-end.
I'm one of the lucky few that got it to boot - sigh come on Samsung!
Managed to upgrade to ICS with 'failed to upgrade firmware' warning.
Missing S Note application, not sure whatelse it might be missing.
You can manually install S Note app by looking up apk file.
Search 'S Note app xda' from google if anyone having similar problem.
Kies 2.0 is recognizing phone as well. I can link screenshot if anyone need for w/e reason if it may help them.
Also, battery drainage problem still there i believe.
Tried the infamous aeroplane mode method, not so sure if it helped:
1. Turn off touch sound and screen lock sound from setting->setting
2. Turn on aeroplane mode
3. Switch off phone
4. Take out battery for 10sec
5. Boot and wait till everything loads
6. Turn off aeroplane mode
App called 'Play Movies' was installed along with ICS, but it gives 404 connection error for 'movie rental' section.
Other than that, Note is running really smooth with ICS.
Firmware version shows up as PDA:LQ3 / PHONE:LPT / CSC:LP1 (XEF)
Wasted time trying to download this so-called update
Sent from my GT-N7000 using xda app-developers app
When I see that, I'm happy to install safe custom roms...
It's a shame for such a company to provide such crappy roms...
Well I am one of those who got stuck on the infamous Samsung logo...
Stock Note, purchased in November, never rooted, 2 GB updates via OTA since November, CSC XEF.
Yesterday morning I got the upgrade notice, did it OTA and on rebooting stuck on Samsung screen...
As an idiot I had been waiting for the "official" ICS ROM.
Thanks Samsung, lesson learned.
Many phone manufacturers will tell you to stay away from custom roms to avoid bricking your phone but to brick your device when updating on an OFFICIAL stock rom after receiving a notification is definitely UNBELIEVABLE !!!!! What is Samsung doing to this expensive device - after the EMMC Bug episode where many people have bricked their Note, now we have another update problem!
Samsung's reputation will take a hard punch with these things if the press writes about this. I think most people who bricked their Note will be fed up and avoid Samsung's phones in the futur.....
For those who want to follow this :
http://www.facebook.com/SamsungMobileFrance
Final5k said:
Many phone manufacturers will tell you to stay away from custom roms to avoid bricking your phone but to brick your device when updating on an OFFICIAL stock rom after receiving a notification is definitely UNBELIEVABLE !!!!! What is Samsung doing to this expensive device - after the EMMC Bug episode where many people have bricked their Note, now we have another update problem!
Samsung's reputation will take a hard punch with these things if the press writes about this. I think most people who bricked their Note will be fed up and avoid Samsung's phones in the futur.....
For those who want to follow this :
http://www.facebook.com/SamsungMobileFrance
Click to expand...
Click to collapse
totally agree... it would have been good for them if they silently provide fix for the emmc bug... staying on GB has become the best solution to all this crap..
I have to say that I'm glad to hear of this. At least it's not just me!!!
My French note got the update yesterday and although it's not hung up or bricked, it certainly has huge issues. Running so hot and battery discharging even when connected to PC by usb. Using wall charger is barely keeping up with the drain even when not using phone.
Have done battery pull and cache wipe twice. No change. Factory reset, nothing either.
Swype not working. Premium suite totally missing. Really disappointing.
Probably not worth waiting for them to figure it out. Downloading UK version now.
I left my note on overnight under the following condition.
Wifi off
Bluetooth off
Data off
Auto rotation off
Gps off
Silent mode on
Power saving off
Between 1am and 10am battery % changed from 81% to 79%.
Quite satisfied with standby drainage.
I just did aeroplane methid as i mentioned on page 1.
Not using any battery save apps.
However when using apps such as dolphin browser, s note, s memo, there seem to be heavy battery drainage issue.
Charged fully then used the browser for approx. 30min and it was on 90%.
Hello all,
I just bought an S3 and updated it to 4.1.1 stock. I like this device but I am very disapointed by how buggy is the stock 4.1.1 ...
I currently own a Xoom running the stock 4.1.2 and never found a single bug using it for months.
I only use my S3 with stock 4.1.1 and already met multiple annoying bugs !
- if I set the Wifi to auto-disable when the S3 goes to the lock screen, then, when Wifi does re-enable, it connects well to the router but I cannot acess to internet. This bug does not exist on the S3 mini running stock 4.1.1.
- the S3 randomly reboot, it rebooted 3 times in about 12 hours.
- the email application has a display problem : the screen flashes black when I scroll an email.
- some apps crash with no reason : stock web browser, stock camera app ...
- the stock browser bookmarks preview is not available : all bookmarks are displayed with a grey icon instead of the web page preview.
- some features in the parameters menu has no effect, they just don't work even when activated : the feature which disables the screen when you're not watching it for exemple, there are some others which did not work but I can't remember which ones.
And as I am only using it for 24 hours I am afraid of discovering some more bugs soon ...
Am i the only one to meet these bugs ?
Is CM10 for S3 less buggy ?
Does anyone know when stock 4.2 should be available for the S3 ?
Thanks
i have 0 problems you mentioned.. try a reset and see if it solve. or just install a custom rom ( you can always return to stock in case of warranty's necessity)
Yes, I already tried to power off the S3. I don't want to use a custom ROM for now, I think for such a high level device I shouldn't have to. I can't understand why so many bugs could be found in less than 24 hours on a stock ROM, this is not serious from Samsung : they waited several months before releasing Jelly Bean for the S3 and finally the ROM is as buggy as an early custom ROM ...
This is a big dispointment for me.
no power off, but a wipe at factory reset
try it!
Settings---> backup and restore--->factory reset ( is the last in list, don't know how is written as i'm using italian language)
Suggest you have a problem and you return the phone either for exchange or refund .
- the S3 randomly reboot, it rebooted 3 times in about 12 hours.
>>> That suggests problem with the phone or an app its not normal behavior .
some apps crash with no reason : stock web browser, stock camera app
>> As above .
Twelve hours and you updated
OTA or Kies update or a self update ????
.. Any of those going wrong could give above symptoms .
Does anyone know when 4.2.1 should be available for the S3 ?
>>> No known date .
jje
I am using the stock 4.1.1 release so I just did the OTA update, everything went fine during the upgrade.
If I am the only one to meet these problems it may be due to hardware issues ... Too bad ...
Not seen any of those bugs at all on ICS nor on JB.
You need to do a complete factory reset.
I don't understand why I would need to do a factory reset : I am just using it for less than 24 hours ...
That's crazy if I already need to do this ... Loosing data and reinstalling everything ... Please, not yet !
I am more an more thinking of installing CM10 ROM, but it seems to have too many issues for now.
I wonder if I just shouldn't get my money back ...
I also suspect you got bad luck and received the only faulty device in store.
Been using mine constantly for 10 days on stock rom without any problems.
Earlier today, I could not wait for 4.1.2 any longer and flashed this one:
http://forum.xda-developers.com/showthread.php?t=1944035
Been using it also without any problems.
No such problems for me, I expect there was a slight issue when you updated. I would just reflash via Odin and see if that fixes your problems.
rekenaar00 said:
I also suspect you got bad luck and received the only faulty device in store.
Been using mine constantly for 10 days on stock rom without any problems.
Earlier today, I could not wait for 4.1.2 any longer and flashed this one:
http://forum.xda-developers.com/showthread.php?t=1944035
Been using it also without any problems.
Click to expand...
Click to collapse
because,maybe, in OTA process something is gone wrong ( like some datas of application not compatible or corrupted during the process)
Might want an exchange as you may have a faulty device..
Considering you're having that many problems in such a short period of time, I think you should return the phone and get a replacement. It's clearly a faulty device. If I were you, I wouldn't bother trying to reflash firmware for it or anything, I'd just go straight to wherever I bought it and demand a new one. Good luck with whatever you end up doing.
Never had a random reboot on my s3 running stock. It has happened running custom kernels but that's a different kettle of fish entirely.
Sent from my Nexus 7 using Tapatalk 2
erto90 said:
no power off, but a wipe at factory reset
try it!
Settings---> backup and restore--->factory reset ( is the last in list, don't know how is written as i'm using italian language)
Click to expand...
Click to collapse
So I finally decided to do a factory reset. All my reboots / Wifi problems are gone now. But I still need a more time to judge this as my problems came after a few hours of use. Thanks to all of you for your advices !
Still, the feature wich uses the front camera to power off the display if you don't watch it does not work at all ...
Dude, return it asap. Mine also did that the first week before totally failing and getting stuck in the inicial samsung logo without possible recovery. Very high chances of happening the same to yours. Plenty of "omfg my phone's totally dead" threads around to confirm this, don't be another one.
dizzy33 said:
So I finally decided to do a factory reset. All my reboots / Wifi problems are gone now. But I still need a more time to judge this as my problems came after a few hours of use. Thanks to all of you for your advices !
Still, the feature wich uses the front camera to power off the display if you don't watch it does not work at all ...
Click to expand...
Click to collapse
You mean smart stay. Yes, smart stay suffered a regression in JB. It was much better in ICS. Slightly better in XXELKC Poland official stock 4.1.2. You could try that out.
Sent from my GT-I9300 using xda app-developers app
prabhjots said:
You mean smart stay. Yes, smart stay suffered a regression in JB. It was much better in ICS. Slightly better in XXELKC Poland official stock 4.1.2. You could try that out.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
OK, so this one is a real bug. Not a big deal as I don't want to use it anyway (I was just curious to try it) because I guess leaving the front camera working may decrease battery life and performances.
kaynpayn said:
Dude, return it asap. Mine also did that the first week before totally failing and getting stuck in the inicial samsung logo without possible recovery. Very high chances of happening the same to yours. Plenty of "omfg my phone's totally dead" threads around to confirm this, don't be another one.
Click to expand...
Click to collapse
For now, since I did a factory reset, I did not experience any reboot. So I'll keep it.
dizzy33 said:
I don't understand why I would need to do a factory reset : I am just using it for less than 24 hours ...
That's crazy if I already need to do this ... Loosing data and reinstalling everything ... Please, not yet !
I am more an more thinking of installing CM10 ROM, but it seems to have too many issues for now.
I wonder if I just shouldn't get my money back ...
Click to expand...
Click to collapse
No problems here, Factory reset (power off the phone, push the volume up + home + power button continuously)
Choose factory reset and you should be okay.
EDIT: Sorry, just noticed your latest comment.
Good to know it solved it.
EDIT2: Smartstay works here, wait for the next official update in our region (JB 4.1.2).
Hey guys..
I've owned all the Samsung Galaxy phones from the S+ right up to the S4 and I've flashed firmwares over all of them with generally no problems at all.
But lately I have a constant issue that has been plaguing my Galaxy S 4 (i9505) phone since I flashed the 4.3 i9505G (GE Edition) ROM over my phone.. (have since moved to OMEGA v12)
The phone just randomly reboots whenever it seems to feel like it.
It could be whilst taking a picture, it could be whilst using google maps, it could be whilst installing an app from the app store or just scrolling across the screen. It's basically rebooted through anything and everything and I've tried pinning it down to something but every time I think that I've got it sorted out. It crashes again whilst doing something else.
1 thing however has got me stumped. The phone has NEVER crashed whilst plugged in. If I keep the phone plugged in, it's never ever just rebooted on its own for me. Which got me thinking that it could be a faulty battery or some sort of voltage issue.
Coming from the 4.3 GE Edition ROM there are other people experiencing random reboots. But now I've just flashed over OMEGA v12 and right after flashing (I did a full wipe of course first) the phone rebooted whilst typing in my Wifi access key. After the reboot I was able to set my phone up and I did a reboot myself, then I went to the app store to add an account and the phone crashed AGAIN.
I'm totally over this issue with my phone. I paid a small fortune for it and I cannot rely on it at all. So I absolutely need it to work. I've had issues on 4.3 GE getting Mobile Data to work. I've had issues with it crashing and I'm just done with all of this.
Do you think that my phone is already broken? (It's barely 3 months old) Do I need to get it replaced under warranty? Can I even get it replaced under warranty, is there a way to even get my warranty back or reset the flash counter etc?
I'm just so confused guys I thought maybe it was my battery, and that my battery was faulty because I had battery percentages dropping and jumping around like mad. For example 15% battery left would actually have the phone turn off... and reboot at 0%. Then the light wouldn't go green for 'Fully charged' and the phone would sit on 99% or 100% but still not say 'charged'. In addition I could swear I had lost more than 10% of my charge in the blink of an eye etc.
I just bought 2 new batteries but they will take a week to get here.. and if the phone is still rebooting (and it isn't a voltage/cut out issue with the battery) then should I assume it's a hardware issue and that the phone needs replacing? Or could it just be a bad flash or something? The phone has at least a 2 year warranty. I don't want to replace it after just 3 months when I haven't even so much as dropped it once.
My recovery is PhilZ 5 Touch 6.0.4.0
I always check MD5 sums before flashing and do a full wipe:
- Wipe Data/Factory Reset
- Clean to Install a New ROM
- Yes
- Then Flash the new .zip file etc.
What on earth could be wrong with my phone?
I'll happily provide any more information, as I honestly cannot handle this happening and I have no idea what my problem is...
Thanks incredibly much for any help at all, what-so-ever.
leijonasisu said:
Hey guys..
I've owned all the Samsung Galaxy phones from the S+ right up to the S4 and I've flashed firmwares over all of them with generally no problems at all.
But lately I have a constant issue that has been plaguing my Galaxy S 4 (i9505) phone since I flashed the 4.3 i9505G (GE Edition) ROM over my phone.. (have since moved to OMEGA v12)
The phone just randomly reboots whenever it seems to feel like it.
It could be whilst taking a picture, it could be whilst using google maps, it could be whilst installing an app from the app store or just scrolling across the screen. It's basically rebooted through anything and everything and I've tried pinning it down to something but every time I think that I've got it sorted out. It crashes again whilst doing something else.
1 thing however has got me stumped. The phone has NEVER crashed whilst plugged in. If I keep the phone plugged in, it's never ever just rebooted on its own for me. Which got me thinking that it could be a faulty battery or some sort of voltage issue.
Coming from the 4.3 GE Edition ROM there are other people experiencing random reboots. But now I've just flashed over OMEGA v12 and right after flashing (I did a full wipe of course first) the phone rebooted whilst typing in my Wifi access key. After the reboot I was able to set my phone up and I did a reboot myself, then I went to the app store to add an account and the phone crashed AGAIN.
I'm totally over this issue with my phone. I paid a small fortune for it and I cannot rely on it at all. So I absolutely need it to work. I've had issues on 4.3 GE getting Mobile Data to work. I've had issues with it crashing and I'm just done with all of this.
Do you think that my phone is already broken? (It's barely 3 months old) Do I need to get it replaced under warranty? Can I even get it replaced under warranty, is there a way to even get my warranty back or reset the flash counter etc?
I'm just so confused guys I thought maybe it was my battery, and that my battery was faulty because I had battery percentages dropping and jumping around like mad. For example 15% battery left would actually have the phone turn off... and reboot at 0%. Then the light wouldn't go green for 'Fully charged' and the phone would sit on 99% or 100% but still not say 'charged'. In addition I could swear I had lost more than 10% of my charge in the blink of an eye etc.
I just bought 2 new batteries but they will take a week to get here.. and if the phone is still rebooting (and it isn't a voltage/cut out issue with the battery) then should I assume it's a hardware issue and that the phone needs replacing? Or could it just be a bad flash or something? The phone has at least a 2 year warranty. I don't want to replace it after just 3 months when I haven't even so much as dropped it once.
My recovery is PhilZ 5 Touch 6.0.4.0
I always check MD5 sums before flashing and do a full wipe:
- Wipe Data/Factory Reset
- Clean to Install a New ROM
- Yes
- Then Flash the new .zip file etc.
What on earth could be wrong with my phone?
I'll happily provide any more information, as I honestly cannot handle this happening and I have no idea what my problem is...
Thanks incredibly much for any help at all, what-so-ever.
Click to expand...
Click to collapse
I can only give you advice on some of the smaller issues that you mentioned. I haven't had a problem with reboots at all (i've flashed all manners of ROMs too, including the GE), so I'm guessing it is hardware related. You should get it replaced (if it still is messing up with the new batteries).
As for warranty, yes you can claim it back on warranty. To be doubly safe, restore it to stock: http://forum.xda-developers.com/showthread.php?t=2265477
Use Triangle Away: http://forum.xda-developers.com/showthread.php?t=1494114
Also FYI, rooting does not void warranty: http://matija.suklje.name/rooting-and-flashing-your-device-does-not-void-the-warranty-in-eu (assuming you are in the EU, not sure about other countries) (gosh i've posted this a lot today).
Thanks a lot buddy I am in the EU definitely and the phone is purchased from the EU. I am actually about to flash it right back to stock now to see if it stops the rebooting issue. I will just have to live without custom roms for awhile and such. If it still keeps crashing I will wait for the new batteries. If it still keeps crashing again after I get those. I guess all that is left to do is render myself without a phone for a week or two and have it repaired...
I wouldn't worry mate it sounds to me like a definite battery issue
Sent from my GT-I9505
similar problem
leijonasisu said:
Thanks a lot buddy I am in the EU definitely and the phone is purchased from the EU. I am actually about to flash it right back to stock now to see if it stops the rebooting issue. I will just have to live without custom roms for awhile and such. If it still keeps crashing I will wait for the new batteries. If it still keeps crashing again after I get those. I guess all that is left to do is render myself without a phone for a week or two and have it repaired...
Click to expand...
Click to collapse
Hi leijonasisu,
I've stumbled across your post after having experienced more or less the same issues as you. After trying many custom ROMs in the last few weeks, the phone has barely been useable for more than a few minutes until it randomly reboots. At which time, I must start over with the whole flashing process. My question is, did getting a new battery resolve your issue? Or did you just trade the device back in?
many thanks
kingzain900 said:
I can only give you advice on some of the smaller issues that you mentioned. I haven't had a problem with reboots at all (i've flashed all manners of ROMs too, including the GE), so I'm guessing it is hardware related. You should get it replaced (if it still is messing up with the new batteries).
As for warranty, yes you can claim it back on warranty. To be doubly safe, restore it to stock: http://forum.xda-developers.com/showthread.php?t=2265477
Use Triangle Away: http://forum.xda-developers.com/showthread.php?t=1494114
Also FYI, rooting does not void warranty: http://matija.suklje.name/rooting-and-flashing-your-device-does-not-void-the-warranty-in-eu (assuming you are in the EU, not sure about other countries) (gosh i've posted this a lot today).
Click to expand...
Click to collapse
Looks like it's better to restore to Samsung stock firmware first then start again from there,
But this will upgrade the the Knox bootloader also.
Stock firmware can be downloaded here, www.sammobile.com/firmwares
I fixed this ages ago. It was a battery issue, I'd bit my bottom dollar that it would be a battery issue for anyone else too, I've read a lot of stuff online about people who have gotten bad batteries with theirs. Swapped to 2 third-party and apparently larger batteries and never had an issue and never looked back.
Sorry for not replying back much sooner but I forgot about the thread.
Try another battery and if within a day or two you get no reboots then toss the bad battery and enjoy your phone! The thing is the battery (due to voltage issues) can make it look like it's the OSes fault when in actual fact it's just a faulty battery and voltage issues.
same problem here.. s4 randomly reboot..
I got the same problem.
The phone reboots every few minutes on me when i want to take it out of standby.
Sometimes it works for a few hours and sometimes it just reboots itself every few minutes or it reboots when i want to do something.
So ur all saying that a new battery could solve my problems ??
Opuske said:
I got the same problem.
The phone reboots every few minutes on me when i want to take it out of standby.
Sometimes it works for a few hours and sometimes it just reboots itself every few minutes or it reboots when i want to do something.
So ur all saying that a new battery could solve my problems ??
Click to expand...
Click to collapse
Hi, the OLD problem WAS caused by the faulty batteries batch (easy to recognize - the battery serial no was beginning with BD code).
Now, more frequently it is resulting from KNOX related issues.
spamtrash said:
Hi, the OLD problem WAS caused by the faulty batteries batch (easy to recognize - the battery serial no was beginning with BD code).
Now, more frequently it is resulting from KNOX related issues.
Click to expand...
Click to collapse
hi thx for the answer.
Could infact be knox issue as i am now back on stock rom without root or anything and im not having any issues now.
But i would like to have a custom rom and root again .
So how would i go from here to there without having random crashes / reboots on custom rom ?
Opuske said:
So how would i go from here to there without having random crashes / reboots on custom rom ?
Click to expand...
Click to collapse
Only one option then: read the ROM-specific threads, loo for feedback posts. If ROM would cause random reboots, you can be certain that it will be written there.
Same issue with gt i9505, random reboot, earlier i had gt i9500 that was flawless with all rom n root n with everything, but i bought gt i9505 and its random reboot like in every 30 to 20 mints, im totally pissed n disappointed ? plzz help....
adilabdi110 said:
Same issue with gt i9505, random reboot, earlier i had gt i9500 that was flawless with all rom n root n with everything, but i bought gt i9505 and its random reboot like in every 30 to 20 mints, im totally pissed n disappointed ? plzz help....
Click to expand...
Click to collapse
Have you disabled everything related to knox and deknoxified your phone?
Do press thanks if my posts are helpful
Sent from my Stock Deodexed i9500 :')
adilabdi110 said:
Same issue with gt i9505, random reboot, earlier i had gt i9500 that was flawless with all rom n root n with everything, but i bought gt i9505 and its random reboot like in every 30 to 20 mints, im totally pissed n disappointed ? plzz help....
Click to expand...
Click to collapse
Uninstall everything realiting to Knox with Titanium backup and be Happy
Sent from my Galaxy S4 using Tapatalk
i9505 S4 sussed out the randomsoft rebooting
i9505 Kitkat random rebooting with UGNG8
UK - BTU
2014 November
I9505XXUGNG8
I9505YXYGNH2
I9505XXUGNG8
4.4.2
For me kitkat UGNG8 with random soft rebooting, tried everything with that firmware I could, reset to default and it was still randomly rebooting when ever it liked. Usually after swiping the screen out of wake lock most of the time. I even re-odin GNG8 3 times.
Cured by Odin with this one, below, which I thought I couldn't, because of the backward compatibility of the dates, but it went in ok. No reboots for weeks. Cured my i9505 S4
2014 July UK - BTU
I9505XXUFNB9
I9505BTUFNE1
I9505XXUFNB9
4.4.2
Link http://www.sammobile.com/firmwares/download/31852/I9505XXUFNB9_I9505BTUFNE1_BTU.zip/
So if you pulling you`re hair out with the S4, or trying to get rid, Odin this firmware first.
satelliteone said:
i9505 Kitkat random rebooting with UGNG8
UK - BTU
2014 November
I9505XXUGNG8
I9505YXYGNH2
I9505XXUGNG8
4.4.2
For me kitkat UGNG8 with random soft rebooting, tried everything with that firmware I could, reset to default and it was still randomly rebooting when ever it liked. Usually after swiping the screen out of wake lock most of the time. I even re-odin GNG8 3 times.
Cured by Odin with this one, below, which I thought I couldn't, because of the backward compatibility of the dates, but it went in ok. No reboots for weeks. Cured my i9505 S4
2014 July UK - BTU
I9505XXUFNB9
I9505BTUFNE1
I9505XXUFNB9
4.4.2
Link http://www.sammobile.com/firmwares/download/31852/I9505XXUFNB9_I9505BTUFNE1_BTU.zip/
So if you pulling you`re hair out with the S4, or trying to get rid, Odin this firmware first.
Click to expand...
Click to collapse
Interesting will have to give this a go, also the battery option.
For months I was running on Lollipop custom ROM, the developer did an upgrade and then the SIM card removed error started. I went back to the old version was keep getting the SIM Card removed error. A few days ago went back to Original ROM for NZ 4.4.2 and I still get the SIM Card error and now the phone just reboots randomly.
Hi
My S4 (UK sim free) is about 4 months old now and has been running pretty reliably until last week, when I received a message on the screen to tell me that there was a software update to be applied ( 4.3 ). I followed the instructions as I have done in the past with my previous S2 and the OTA update began. The process seemed to involved several reboots and eventually it got stuck in a cycle of reboots - which commenced as soon as the illuminated menu and return off screen buttons lit, flickered briefly and then rebooted., until I connected the phone to the samsung power supply at which point the boot proceeded normally and the upgrade appeared to have completed.
Firstly, let me say that the battery was fully charged before I began the update - I have done a number of them in the past with playing with different roms on my S2 so I was aware how important it is to start with a charged battery.
I thought nothing more of it until later that evening, the phone rebooted when i finished a call and took the headset away from my head. Again, I was unable to get the phone to boot correctly until I connected the charger. It has happened several times since - once when i was using the Maps app with GPS switched on. The reboots appear to be completely random. The phone was completely fine before the upgrade so to me it HAS to be the latest version that has caused the problem. I have searched high and low for a solution online, but the only one appears to be to factory reset the phone which I have done, but to no avail.
I can't see an official way to "downgrade" back to my previous version of android until kitkat comes out for the S4.
Can anyone offer any other solutions, as the phone is virtually unusable as it stands ?
Other info : Android 4.3. Baseband I9505XXUEMKF Kernel : 3.4.0-2082040 BUILD : JSS15J.I9505XXUEMKF
Thanks
Geoff
BTW I also wiped and reformatted the cache partition. Also noticed that my WiFi has started acting up - it keeps telling me that its disabled because the signal is poor - of course it isn't - it worked fine before the update and all my other wi-fi devices are fine too.
HartleyHare said:
Hi
My S4 (UK sim free) is about 4 months old now and has been running pretty reliably until last week, when I received a message on the screen to tell me that there was a software update to be applied ( 4.3 ). I followed the instructions as I have done in the past with my previous S2 and the OTA update began. The process seemed to involved several reboots and eventually it got stuck in a cycle of reboots - which commenced as soon as the illuminated menu and return off screen buttons lit, flickered briefly and then rebooted., until I connected the phone to the samsung power supply at which point the boot proceeded normally and the upgrade appeared to have completed.
Firstly, let me say that the battery was fully charged before I began the update - I have done a number of them in the past with playing with different roms on my S2 so I was aware how important it is to start with a charged battery.
I thought nothing more of it until later that evening, the phone rebooted when i finished a call and took the headset away from my head. Again, I was unable to get the phone to boot correctly until I connected the charger. It has happened several times since - once when i was using the Maps app with GPS switched on. The reboots appear to be completely random. The phone was completely fine before the upgrade so to me it HAS to be the latest version that has caused the problem. I have searched high and low for a solution online, but the only one appears to be to factory reset the phone which I have done, but to no avail.
I can't see an official way to "downgrade" back to my previous version of android until kitkat comes out for the S4.
Can anyone offer any other solutions, as the phone is virtually unusable as it stands ?
Other info : Android 4.3. Baseband I9505XXUEMKF Kernel : 3.4.0-2082040 BUILD : JSS15J.I9505XXUEMKF
Thanks
Geoff
Click to expand...
Click to collapse
Has your battery a serial number starting by DD or DB? If has, buy a new one or change your battery in a service center; if hasn't, no, you can't downgrade your firmware from 4.3. You should reflash same firmware by odin from your pc and surely your issue will disappear (sometimes ota updates fail). But before to do this, check your battery, it is a usual problem with that batteries serial numbers...
jaswinky said:
Has your battery a serial number starting by DD or DB? If has, buy a new one or change your battery in a service center; if hasn't, no, you can't downgrade your firmware from 4.3. You should reflash same firmware by odin from your pc and surely your issue will disappear (sometimes ota updates fail). But before to do this, check your battery, it is a usual problem with that batteries serial numbers...
Click to expand...
Click to collapse
Thanks for the quick reply. My battery serial is BD1D609JS/2-B, So it seems that isn't the problem, besides everything was fine before the update. It seems that there are quite a number of people out there with similar problems over the last couple of days, so it does point to a flaky release...
HartleyHare said:
Thanks for the quick reply. My battery serial is BD1D609JS/2-B, So it seems that isn't the problem, besides everything was fine before the update. It seems that there are quite a number of people out there with similar problems over the last couple of days, so it does point to a flaky release...
Click to expand...
Click to collapse
Sorry, i mistaked, i meant BD instead DB. You have the defective Samsung recognized battery. Maybe updating has walked up your battery issue (consider that the bug is not in the electrical part of the battery, but in the electrical part). Before trying more fixes, change your battery (also consider it can damage your device).
Enviado desde mi GT-I9500 usando Tapatalk 2
jaswinky said:
Sorry, i mistaked, i meant BD instead DB. You have the defective Samsung recognized battery. Maybe updating has walked up your battery issue (consider that the bug is not in the electrical part of the battery, but in the electrical part). Before trying more fixes, change your battery (also consider it can damage your device).
Enviado desde mi GT-I9500 usando Tapatalk 2
Click to expand...
Click to collapse
Ok I'll contact Samsung to get a replacement - thanks for bringing that to my attention...
Gracias mi amigo !
Hey guys
recently i bought a Bluetooth speaker and connected it to my A3 (300FU), but now when i check the battery stats to see what is eating my battery it only shows Bluetooth (not even screen, wifi etc) [ see screenshots]
i deleted dumpstat/logcat and also wiped cache partition but it didn't help.... is there an obvious solution or am i missing something here?
*running stock Marshmellow ROM
Any help would be appreciated
i think a few users have it confirmed, Bluetooth seems to be a major drain in MM for A3FU.
i can only advise to update to a newer build. what build are you btw? do a screenshot of About in Settings
i didn't have a problem until recently, when i paired my device with the bluetooth speaker.
should i reset network settings?
I've attached the screenshot.
all users who reported BT issues came from first BT pairing, just like you. and they were all on PH3.
It's a rom bug that you can only hope they notice and fix, and then it's up to you to try the new builds and see if there is any change.
But is this a bug only in the battery stats or is bluetooth actually draining the battery even if its turned off ?
Bffn45 said:
But is this a bug only in the battery stats or is bluetooth actually draining the battery even if its turned off ?
Click to expand...
Click to collapse
Quite sure bluetooth is being the idiot here.
I do not own this device but I had this issue on my other A series device and it's because of the Nearby Device Scanning in Other Connection Settings.
This feature is included after updating to Mashmallow and it causes your Bluetooth to be always ON if the feature is ON(By default its ON so go and turn it off).
BTW, how did you get the battery graph on Mashmallow? Didn't Samsung removed it since Lollipop? I can't access it on my device, my sister's J7 and my mom's S7 edge
conanDO98 said:
I do not own this device but I had this issue on my other A series device and it's because of the Nearby Device Scanning in Other Connection Settings.
This feature is included after updating to Mashmallow and it causes your Bluetooth to be always ON if the feature is ON(By default its ON so go and turn it off).
BTW, how did you get the battery graph on Mashmallow? Didn't Samsung removed it since Lollipop? I can't access it on my device, my sister's J7 and my mom's S7 edge
Click to expand...
Click to collapse
Nearby device scanning is turned to off, should i reset network settings? maybe that way it will correct the readings
For the Battery stats --> Settings -->at the System section search for Battery--> Battery usage, or maybe just use S finder
I've got the same issue. Untill I switch Bluetooth on, normal battery stats, as soon as I do, everything is reported as Bluetooth - no screen use, now Android System use. "Nearby Device scanning " option seems to have no effect.
I also had this issue when I upgraded to MM (build CPI1)... even tried factory reset, but problem persisted.
I think it's a bug in the Samsung ROM, no way to get rid of it without a software upgrade.
Same "bug" with my A300FU.
Tried everything...
Installed earlier firmware (rom) with odin (in which I did not have the exaggerated Bluetooth usage)
Installed latest firmware again
Full wipe
Install latest firmware
After installing each rim I have the high Bluetooth usage from the start without installing any app
My colleague with identical A300FU did have the same with the previous 6.0.1 rom, bit after OTA update it dissappeared on his device
So it has to do something with my setup....
According to the battery gauge Bluetooth is using approx 4mAh PER SECOND
Also explored the option to modify the power profile.xml in the framework-res.apk but to no avail (keep getting bootloop)
*frustrated*
Anyone an idea?
Flashing cm12 or cm13 and then reverting to stock 6.0.1 is also not a solution to this issue......
My Wife's Galaxy A5 (2015) also has this bug. All 6.0 firmwares - even latest from January. So stupid - I can't belive that they can't see this bug. There is no battery drain - only bad statistics. But its very anoying because You cant check how long screen was used etc. Scaning of near devices is disabled too - didnt help. Dammed.
Have You find any solution?
I never looked at that screen before, but I recently noticed this too and it freaked me out at first. After testing it tho, I was gonna post and ask other peoples' experience, but then I found this thread.
What I get is that initially my batterystats are recorded normally, but then when i turn on bluetooth, even if it's for 1 second, all stats disappear and bluetooth appears in that list with what appears to be a huge (and impossible) drain.
Bffn45 said:
But is this a bug only in the battery stats or is bluetooth actually draining the battery even if its turned off ?
Click to expand...
Click to collapse
PlutoDelic said:
Quite sure bluetooth is being the idiot here.
Click to expand...
Click to collapse
I normally have bluetooth on, and I don't actually notice my battery draining any faster than when it's off. Also, if the computed battery usage on this was accurate on my phone, I would run out of power in a matter of seconds. So it's definately a bug in the battery stats.
aerogenes said:
After installing each rim I have the high Bluetooth usage from the start without installing any app
My colleague with identical A300FU did have the same with the previous 6.0.1 rom, bit after OTA update it dissappeared on his device
So it has to do something with my setup....
Click to expand...
Click to collapse
I beg to differ! I flashed lollypop and the problem disappears then, but it's there on both marshmallow builds for our country, even when starting fresh after a data wipe.
Which roms have you tried? And what rom is your colleague on after the OTA that fixed it? Buildnumbers would really help
For me: U1CPH3 and S1CPL1 both have this issue
It seems, for me at least, that after the December OTA security update the bug dissappear and i am now getting normal battery readings.
Bffn45 said:
It seems, for me at least, that after the December OTA security update the bug dissappear and i am now getting normal battery readings.
Click to expand...
Click to collapse
Al right, thanks! Latest rom/update for my country is from december too, but i still have it.
So i'll try downloading a jan 2017 rom for a different country and see what happens
Update:
Installed the S1CQA2 firmware, which should be the latest, and the bug is still there. Just with less unbelievable numbers and it takes a little while longer for it to make all other stats disappear.
Update2:
Looked into the powerprofiles.xml too, but the marshmallow one (which has this issue) is identical to the lollipop one (that doesn't have this issue). Also all there is to edit in there is the amperage usage for actual A2DP, but according to this https://source.android.com/devices/tech/power/values.html a lot of battery usage is just pushed to the batterystats service by the controller.
Now wondering what files are associated to the bluetooth controller. Simply replacing the bluetooth.apk from a different rom where this is working does not solve it either.
After some more digging, and succesfully porting the S5 bluetooth files to my phone, i found out that the samsung S5 suffers from this issue as well andthus the issue was still not fixed
Also, judging from other posts in other forums it appears the Note 4 has it too.
Therefore I think it is a touchwiz bug, and I am clueless on what to try anymore.
This is my third post in this thread in a row but editing my previous posts here might make the new info go unnoticed...
So this is just a heads up that the italian A300FU1CQC2 firmware has finally fixed this bug for me! :victory:
I have had bluetooth on (idle) all day now and it doesn't show up in battery stats at all.
great effort mate, really love it when people monitor the release stream .
Carpe-Dimi said:
So this is just a heads up that the italian A300FU1CQC2 firmware has finally fixed this bug for me! :victory:
I have had bluetooth on (idle) all day now and it doesn't show up in battery stats at all.
Click to expand...
Click to collapse
Thanks for the heads up... I've just flashed the update, and I can confirm that also for me this new firmware solves the BT issue. :good: