Hi guys! I'm posting here because I'm a little bit lost. I got a new software update today on my A505F (A505FDDU2ASJ2 - it's the 2nd update for October, the phone was already on Oct. 1st security level before this update) and I installed it right away.
Now the problem is albeit the phone does feel significantly smoother after this update, the charging algorithm is a complete mess (it was already buggy enough after the August update, which claimed it "improved the charging algorithm") and it's even worse after this update, it's now causing weird issues:
- The flashlight doesn't work anymore unless the phone is plugged and charging, what a weird bug!. If I try to turn on the flashlight without the charger plugged in, it simply doesn't turn on (Google Assistant can't turn it on either). The camera seems to be able to turn on the LED flash but it's completely bugged out, the flash keeps turning on and off and sometimes even stays on after leaving the camera (phone unplugged from the charger).
- The phone keeps throwing error messages telling me to "check the cable connection" when it's plugged in.
- The phone also takes more than 10 seconds to detect the charger (and keeps saying it's charging more than 15 seconds after unplugging the charger).
- The fast charging toggle on the Device Care\Battery Settings simply does not work, the phone will keep using fast charging even if the toggle is set to disable.
- If I turn off the phone, it keeps showing a battery with an exclamation mark and It's hard to get it to turn on, I have to find the right timing after the battery icon disappears to turn it on.
- My PC does not detect the phone anymore (it still charges it, though).
As you can see, there's something really wrong with that charging algorithm or whatever piece of software is in charge of the charging.
-PS: It's the 128 GB storage / 6 GB RAM version of the A505F.
-PS2: My friend's A50 exhibits the same behavior after the update while my brother's doesn't, any idea?
-PS3: I can't afford to soft-reset the phone right now, I really can't!
Thank you for reading, some feedback would be really appreciated if you do install this update.
EDIT: A soft reset didn't fix the issue. Bummers -_-
I have same version of phone as you and all problems after last update. Is there any official Samsung forum so we can report these bugs?
same as my mother's galaxy a50 after 2 updates(the first one is 400mb and the second is 200mb) when we connect the charge it doesn't charge. The error prompt is "connect charger" even it is connected.
We try to charge the phone while its off but there is battery icon with exclamation point.
We cannot charge the phone until now. pls help
yuansmart said:
same as my mother's galaxy a50 after 2 updates(the first one is 400mb and the second is 200mb) when we connect the charge it doesn't charge. The error prompt is "connect charger" even it is connected.
We try to charge the phone while its off but there is battery icon with exclamation point.
We cannot charge the phone until now. pls help
Click to expand...
Click to collapse
I have managed to charge it like 35% in 6hours, only samsung can help us now. You can report bug in Samsung members app.
I am so relieved to hear that the issue is more widespread than I thought, it might mean that Samsung will have to take it seriously, I hope they'll publish an update soon
Also, a soft-reset (from the phone settings) + a factory reset (from recovery mode) did not fix the issue, don't bother trying if you were thinking about it.
I rolled back to August patch with Odin same thing happens i guess its hardware related...:crying:
Detangler said:
I rolled back to August patch with Odin same thing happens i guess its hardware related...:crying:
Click to expand...
Click to collapse
I think there's more to it, It's really weird that it happens after an update and on different phones :|
Detangler said:
I rolled back to August patch with Odin same thing happens i guess its hardware related...:crying:
Click to expand...
Click to collapse
I think there's more to it, It's really weird that it happens after an update and on two different phones :|
NVTesla said:
I think there's more to it, It's really weird that it happens after an update and on two different phones :|
Click to expand...
Click to collapse
I rly dont know man i guess we need to w8. Some one posted same thing happened to them in August and they replaced motherboard after that it was okey. But its rly weird everything else works fine just flashlight and stupid charging
Rolled back all the way to May update and my phone now works just fine.
Detangler said:
Rolled back all the way to May update and my phone now works just fine.
Click to expand...
Click to collapse
Nice! So that means that it's a software issue?
NVTesla said:
Nice! So that means that it's a software issue?
Click to expand...
Click to collapse
Yes!
Detangler said:
Yes!
Click to expand...
Click to collapse
Glad to hear that, I'll try to get in touch with Sammobile, they might help us raise this issue to Samsung. Thank you for confirming, It would be really nice if we could get other people with this issue to show up in this thread
I also can't charge properly which is a pain. Was working 100% before I updated the firmware
No idea if they gonna fix this soon, there is a way to roll back with Odin. It's safe I didn't had any problems.
I have a same issue with this weird update. I want to roll back the updates but how and where to download the previous updates manually. :'(
You can see instructions on sammobile or here on XDA.
According to a user on Reddit, he/she can't find the update (said they were still on A505FDDU2ASJ1, and the culprit update is A505FDDU2ASJ2), it appears that Samsung has pulled it out from the servers, this must mean that they're aware that it's causing issues!
That's nice to hear
---------- Post added at 12:11 PM ---------- Previous post was at 11:18 AM ----------
Updated it again still doesn't work, gonna w8 for Android 10 haha
Detangler said:
That's nice to hear
---------- Post added at 12:11 PM ---------- Previous post was at 11:18 AM ----------
Updated it again still doesn't work, gonna w8 for Android 10 haha
Click to expand...
Click to collapse
Did you try the November update? It's out in the US and Europe but I still haven't gotten it on my A50 (MENA Zone)
Related
Hey as everyone knows there are some people having LOS and it will remain that way until after a reboot. First I'm rooted but not with a custom kernel. I'm on the stock kernel(just flashed CWM and then root.zip) So I have had LOS a few times since I got my phone. Just a few minutes ago I got LOS after a phone call and it remained that way. AbsolutZeroGI on IRC wanted me to try something whlile I had LOS before I rebooted. I went into the task manager, selected the ram tab and then pressed the clear button. That didnt bring service back but after I did that I did get the roaming notification(but still had LOS) so I plugged my phone into my PC(not to try to fix it but to boot into recovery) and then I noticed my signal came back without a reboot as soon as I plugged in the cable. Now I'm not really sure if/why plugging in the USB would correct this or if it was just a coincidence or if it fixed it. Although I know the other times I had LOS it didnt come back until a reboot no matter how long I waited.. So I would like to run a test..
The next time you get LOS go into the taskmanager, select the ram tab and then click clear, then plug your phone into your PC (Edit: While your screen is off). Did your signal come back or do you still have LOS?
EDIT:
I just got home, was sending a few text messages had a signal, put my phone down, came back and turned on the screen and I had no service. So I came back to my PC to test this out again. When I came back to the PC I had a PM from AbsolutZeroGI. He told me he just got the LOS and the steps didnt work. And so far I've been the only one to get it to come back without a reboot. So I tried again.. I plugged it in and unplugged it multiple times... nothing.. still no service, I tried to remember the exact steps I did the first time and I thought "when I plugged it in and it worked was my screen on or off" So I tried one more time. I turned the screen off, waited a few minutes, had the usb cable plugged into the pc then plugged in the phone. I waited a few more seconds, turned the screen on and boom, I had almost all the bars but no 3G icon and a few seconds later the 3g icon came back on.
So here is my theory: When the screen goes off maybe there is a bug in the sleep process that somehow causes the LOS. When you wake it, whatever it is that disabled it, doesnt re-enable it so it "thinks" it's still sleeping, until it's back in sleep mode and something like plugging in the usb wakes it for usb debugging. So I think it somehow goes into a deep sleep and doesnt fully wake up when the screen goes on, but something like plugging it in fires another separate process that does fully wake it.
Thank you in advance for everyone who tests this out for us. If we can find a real method that works every time we can start working on a temporary fix until Sammy gives us a firmware update so LOS won't be so bothersome.
i have not experienced the los, but have experienced very poor signal when trying to connect to the net. but when i rebooted the signal did get better
Although I know some people stated that they had this issue on unrooted phones as well as rooted, I myself had the issue with my first Epic Touch after I rooted. Before I rooted, I never experienced the issue.
I exchanged my phone Thursday because there was no way to return to stock at the time and I haven't experienced the LOS of service at all.
plmiller0905 said:
Although I know some people stated that they had this issue on unrooted phones as well as rooted, I myself had the issue with my first Epic Touch after I rooted. Before I rooted, I never experienced the issue.
I exchanged my phone Thursday because there was no way to return to stock at the time and I haven't experienced the LOS of service at all.
Click to expand...
Click to collapse
Hmm maybe I'll install the stock kernel and see of that fixes it. I only had my phone since yesterday and it was rooted after an hour or so of having it and since I've had at least 5 Los. :-( but I have read the same that people claim its happening to them as well without ever rooting
Sent from my SPH-D710 using XDA App
I'll definitely try in a few when my los kicks in. Had my first touch for three days and no los occurrences but my new one has had them 5 times in two days.
Sent from my SPH-D710 using xda premium
I've had my phone since launch day. I didn't root until the 20th. I had no LOS in that time I was completely stock. Right after I installed bubby's CWM and root the problems started. I mean the same night. It had happened several times until I went back to the stock kernel. I have since had the LOS for literally 5 seconds while it switched from Sprint to roaming and service was right back. Not a problem since. I'm not saying these other kernels are the complete problem and that the phone is not without bugs. I just think that maybe the other kernels make the problem (if any) worse.
---------- Post added at 07:58 PM ---------- Previous post was at 07:56 PM ----------
jirafabo said:
I'll definitely try in a few when my los kicks in. Had my first touch for three days and no los occurrences but my new one has had them 5 times in two days.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
The other night I had 5 times in two hours. Literally!!
I'm completely stock and picked up my phone on Launch day. I had several LOS during the first few days. I updated my PRL, Profile, Firmware etc. and it hasn't been an issue since.
I do have an issue roaming, as in my phone wont.
Ok guys, I'm going to update the OP but here is a new development.
I just got home, was sending a few text messages had a signal, put my phone down, came back and turned on the screen and I had no service. So I came back to my PC to test this out again. When I came back to the PC I had a PM from AbsolutZeroGI. He told me he just got the LOS and the steps didnt work. And so far I've been the only one to get it to come back without a reboot. So I tried again.. I plugged it in and unplugged it multiple times... nothing.. still no service, I tried to remember the exact steps I did the first time and I thought "when I plugged it in and it worked was my screen on or off" So I tried one more time. I turned the screen off, waited a few minutes, had the usb cable plugged into the pc then plugged in the phone. I waited a few more seconds, turned the screen on and boom, I had almost all the bars but no 3G icon and a few seconds later the 3g icon came back on.
So here is my theory: When the screen goes off maybe there is a bug in the sleep process that somehow causes the LOS. When you wake it, whatever it is that disabled it, doesnt re-enable it so it "thinks" it's still sleeping, until it's back in sleep mode and something like plugging in the usb wakes it for usb debugging. So I think it somehow goes into a deep sleep and doesnt fully wake up when the screen goes on, but something like plugging it in fires another separate process that does fully wake it.
graffixnyc said:
So here is my theory: When the screen goes off maybe there is a bug in the sleep process that somehow causes the LOS. When you wake it, whatever it is that disabled it, doesnt re-enable it so it "thinks" it's still sleeping, until it's back in sleep mode and something like plugging in the usb wakes it for usb debugging. So I think it somehow goes into a deep sleep and doesnt fully wake up when the screen goes on, but something like plugging it in fires another separate process that does fully wake it.
Click to expand...
Click to collapse
I saw that theory from someone else around here as well. Definitely seems like something is going to sleep and not coming back on and the modified kernels seem to exacerbate the issue for some reason. (Maybe the source Samsung released is older than what the phone shipped with and the issue was improved between the two versions?)
Nothing against the devs or anything like that, but this LOS issue is why I havent rerooted my current Epic Touch.
As much as I want to flash that new
midnight roms, I'm holding back just for that reason.
This message was developed and sent from my SGSII-EPIC 4G TOUCH!
graffixnyc said:
So here is my theory: When the screen goes off maybe there is a bug in the sleep process that somehow causes the LOS. When you wake it, whatever it is that disabled it, doesnt re-enable it so it "thinks" it's still sleeping, until it's back in sleep mode and something like plugging in the usb wakes it for usb debugging. So I think it somehow goes into a deep sleep and doesnt fully wake up when the screen goes on, but something like plugging it in fires another separate process that does fully wake it.
Click to expand...
Click to collapse
That wouldn't work, because in reality, the phone checks cell towers for new calls something like every 5-10 seconds. No sleep for the wicked radio.
No. It is definitely something that disables the radio entirely.
---------- Post added at 10:56 PM ---------- Previous post was at 10:53 PM ----------
plmiller0905 said:
Nothing against the devs or anything like that, but this LOS issue is why I havent rerooted my current Epic Touch.
As much as I want to flash that new
midnight roms, I'm holding back just for that reason.
This message was developed and sent from my SGSII-EPIC 4G TOUCH!
Click to expand...
Click to collapse
There's no reason not to root the phone now AT ALL.
The current root method of:
1) Install custom recovery+kernel,
2) Flash su binary,
3) Flash stock recovery+kernel
---
The current root method does nothing but add files to /system partition -
you change nothing else in the operation of the phone but add root privileges.
Flashing roms while they are in beta though, that's just asking for trouble, unless you are testing for the rom builder.
I have the LOS icon at this very moment, yet I just received a call? Also, I plugged it into my computer, but nothing changed.
Hi all. I just had LOS and tried to use my car charger instead of my computer. It didn't fix the issue but I did notice that the charging led wouldn't illuminate. after reboot the phone gets signal and the led is working fine. I don't know if that is significant but wanted to mention it.
Sent from my SPH-D710 using XDA App
Interesting thread. Ive had mine for 3 days now and havent experienced this at all.
Sent from my SPH-D710 using Tapatalk
about 5 times a day when i try to place a call the call get stuck in "dialing" mode and never connects. if I try to end it it is still stuck in the task bar and there is no way to make another call unless I reboot. The signal bars look normal. is this the LOS?
I bought two E4GT's on launch day and I told the lady to just activate them and I would do the rest of the setup. She was messing around with them for awhile and I asked her what was going on, and she said they were doing a system update.
That makes me think that the factory firmware had the bug, but they already had an update at launch. If that is the case, I think there's a good chance the source code released was for the original firmware, which reintroduced the bug into all the custom kernels.
This could also explain why some unrooted users have the los - maybe their Sprint store was too lazy to do the update for them (although they should have got a notice for the ota update by now).
FWIW, neither of our phones have this issue and both are still stock. Baseband version is EG30.
Sent from my SPH-D710 using xda premium
leond said:
about 5 times a day when i try to place a call the call get stuck in "dialing" mode and never connects. if I try to end it it is still stuck in the task bar and there is no way to make another call unless I reboot. The signal bars look normal. is this the LOS?
Click to expand...
Click to collapse
No, but that is major suckage, happens to me once a day. Makes me want to punch babies.
los, which I get too, is when you get the no smoking signal instead of a cdma signal.
I went to root+stock kernel and the problem is gone and LOS is gone to
txmikester said:
I bought two E4GT's on launch day and I told the lady to just activate them and I would do the rest of the setup. She was messing around with them for awhile and I asked her what was going on, and she said they were doing a system update.
That makes me think that the factory firmware had the bug, but they already had an update at launch. If that is the case, I think there's a good chance the source code released was for the original firmware, which reintroduced the bug into all the custom kernels.
This could also explain why some unrooted users have the los - maybe their Sprint store was too lazy to do the update for them (although they should have got a notice for the ota update by now).
FWIW, neither of our phones have this issue and both are still stock. Baseband version is EG30.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
There was no update when these phones were released. If she was activating the phone then she was 9/10 referring to a profile update and prl update which each phone does when being activated.
Sent from my SPH-D710 using xda premium
So here's the story ; I bought the phone worked normal , nodo installed , security update installed , i then register a developer account , installed mango beta 1 , then beta 2 , after that the leaked rtm mango, random restarts.I thought its normal since the drivers aren't updated for mango. Reverted back to nodo today so i can get the mango through official channel with the normal driver. I keep checking no mango , i then tried a disconnect trick a discovered on the forums. version 7401 was installed and then random restarts much often than usual. After disconnecting the phone on step 9 and removing battery couple of times phone booted up and stayed on. After that the Zune prompted me to install Mango. After doing everything zune said Step 8 of 9 Restarting your phone. Phone was stucked on HTC logo disconnected phone removed battery like i did before... but now i can't start it up , no logo no nothing , Power + Volume down does nothing... warranty is still valid though , should i send it for repair? Thanks for any reply
If it's a Verizon trophy, look at the leaked HTC roms, they are the same thing.... (version for version they are exactly the same as you get from the Zune download).
Flash that rom and you'll be on Mango final with all the features that you want.
DavidinCT said:
If it's a Verizon trophy, look at the leaked HTC roms, they are the same thing.... (version for version they are exactly the same as you get from the Zune download).
Flash that rom and you'll be on Mango final with all the features that you want.
Click to expand...
Click to collapse
Its an unbraded open market htc trophy , the problem is i can't boot it up...
spyridonas said:
Its an unbraded open market htc trophy , the problem is i can't boot it up...
Click to expand...
Click to collapse
Check in the HTC Trophy area on this site... there is a bunch of roms, find a NODO rom and put your phone in boot flash, flash it, it should get you back to a working phone.
I know about the CDMA version of the phone and you have the GSM, so I can't help you with the exact rom you need but, I am sure you can find it.
DavidinCT said:
Check in the HTC Trophy area on this site... there is a bunch of roms, find a NODO rom and put your phone in boot flash, flash it, it should get you back to a working phone.
I know about the CDMA version of the phone and you have the GSM, so I can't help you with the exact rom you need but, I am sure you can find it.
Click to expand...
Click to collapse
The phone won't power up , no flash boot no nothing...i do have my own backup of nodo rom no need to find another one , the problem is i can't boot it up !!!!
If it won't boot up, and no trick to make it boot up works, then get it swapped. No reason to ask here when no one here works for HTC or whoever you bought the phone through.
From the random reboots you mention, you might have had a semi defective unit from the start as it shouldn't be rebooting that much on you if at all.
Exactly the same problem here. Going to contact htc sav :/ to fix that.
spyridonas said:
After doing everything zune said Step 8 of 9 Restarting your phone. Phone was stucked on HTC logo disconnected phone removed battery like i did before...
Click to expand...
Click to collapse
This was the issue; how long did you wait?
I remember when I last upgraded, the phone ages to reboot. You have to be patient!
Same problem here.
HTC Trophy. Was on NoDo (7392 or something like that) and never installed any pre-release Mango. Phone is not developer unlocked or unbranded (it's VF).
Did the disconnect trick last night to get the update. It installs 2 updates and the first went fine but the second (which I think was the HTC firmware update) took quite a long time and eventually got to step 8 of 9 (restarting phone) but stayed there for at least an hour with the HTC logo on screen.
I left it and went to sleep. Woke up this morning with Zune still saying step 8 of 9 and phone blank.
Phone is completely dead. Whether it's unplugged, connected to PC or connected to the charger it won't power on. It doesn't even show the red or green power light. Camera + Vol Up + Power also does nothing. Checked battery with multi-meter and it has power so it's not a charging issue.
It looks almost like a hardware failure (by the fact that there's no activity at all). Maybe the firmware update taking so long overheated something in the phone.
try with power+down vol+camera = usb mode host
maraver said:
try with power+down vol+camera = usb mode host
Click to expand...
Click to collapse
Tried that too. Still nothing. :-(
Nothing. The Telephone act like there's no battery in it...
---------- Post added at 02:23 PM ---------- Previous post was at 01:54 PM ----------
Nothing. The Telephone act like there's no battery in it...
I have the similar problem while updating to Mango. But my current state is a little bit different (may be a bit better then other people). It is stuck in the HTC logo screen.
I have can get into bootloader, but the official bootloader doesn't allow me to do anything.
dears
i have same problem with my trophy
first step: if your trophy can't enter boot mode you have to go to profisnal tool like Riff Box or ORT Box thay used JTAC method and you have to open your phone to connect JTAC cable then repir Boot area and no way to repir this area without this solution
after repir now you can enter boot mode
sec step : flash your phone with Correct flash files
but my Q is what kind of flash can be correct i try many but still hang on HTC logo
we need some one give us correct info about :
all flash file Brand or unbranded and what the true one
are we need to repir RSPL Or HSPL
These sound like factory faults to me. I've been playing around with different ROMs ever since I got my phone,no problem. The only things I wish I had were usb storage and tethering, I wish they were possible without going through an encyclopaedia of instructions,that's a sure way to brickville.
Sent from my 7 Trophy using XDA Windows Phone 7 App
spyridonas said:
The phone won't power up , no flash boot no nothing...i do have my own backup of nodo rom no need to find another one , the problem is i can't boot it up !!!!
Click to expand...
Click to collapse
IM0001 said:
If it won't boot up, and no trick to make it boot up works, then get it swapped. No reason to ask here when no one here works for HTC or whoever you bought the phone through.
From the random reboots you mention, you might have had a semi defective unit from the start as it shouldn't be rebooting that much on you if at all.
Click to expand...
Click to collapse
suzukube said:
Nothing. The Telephone act like there's no battery in it...
Nothing. The Telephone act like there's no battery in it...
Click to expand...
Click to collapse
Leave the phone to wall charger for at least 30 min and then it will boot up
colossus_r said:
Leave the phone to wall charger for at least 30 min and then it will boot up
Click to expand...
Click to collapse
I tried that a few times. In fact I left it plugged into the wall charger overnight. Still nothing.
I ended up getting a replacement phone from my carrier. Interestingly the battery was completely flat when I put it into the replacement phone. They only replace the main shell (refurb), not battery, charger cable or back cover. I had to leave it plugged into the charger for a minute before it turned on.
The difference between the dead phone and the replacement is that the replacement would charge (immediately showed red light when plugged in) but the bricked phone didn't charge or even seem to recognise that a charger was connected.
I do wonder what would have happened if I had charged the battery some other way and then put it back into the phone. I'll never know because the courier took my phone away when they dropped of the replacement.
The worst part was being without my phone for 4 days (over a weekend) and then having to reconfigure and reinstall everything on the new phone (because stupid Zune does not have any way to restore a backup to a different phone). I think the only thing I really lost was my text messages in the end.
---------- Post added at 06:15 PM ---------- Previous post was at 06:02 PM ----------
Vukile said:
These sound like factory faults to me. I've been playing around with different ROMs ever since I got my phone,no problem. The only things I wish I had were usb storage and tethering, I wish they were possible without going through an encyclopaedia of instructions,that's a sure way to brickville.
Click to expand...
Click to collapse
Well I've had my phone for 7 months without any issues, including the couple of updates we've had since February. I think what caused the problem here was that the Mango update included firmware updates from the manufacturers. It actually applies one update, restarts the phone and then applies a second update which is the HTC Firmware update. That's the one that doesn't complete properly. Looking around online there seems to be a few HTC (Trophy and HD7) users experiencing the same thing.
I applied the Mango update to my replacement phone (also a Trophy 7) without any problems so maybe it only affects certain Trophy phones.
And I agree with you on the tethering - that's one of the main features I seriously miss from my previous phone!
Nomad1011 said:
And I agree with you on the tethering - that's one of the main features I seriously miss from my previous phone!
Click to expand...
Click to collapse
+3 or 4 or 10,000
I miss this so much... (I keep a spare 6.5 phone around to do tethering when I need it, just wish I could do it with my trophy)
most likely its a faulty usb port or some problem with yr pc when transferring the update which bricked yr phone
Magpir said:
most likely its a faulty usb port or some problem with yr pc when transferring the update which bricked yr phone
Click to expand...
Click to collapse
Then a lot of people must have the same problem with their PC or USB port (including 3 people on this thread alone). I can't post links yet but if you do a Google search for "mango bricked HTC windows phone" there are quite a few links, each with multiple people having the exact same problem (completely dead phone, no power or lights at all). I wouldn't call it "widespread" yet but there's definitely an issue affecting certain HTC phones when updating to Mango.
I had done previous updates on that phone (using the same PC, cable, etc) without issues and the first part of this update worked fine (including the restart). Replacement phone (exact same model) updated fine on the same PC with same cable (including the HTC Firmware update).
Hi All
Few weeks back, my note 2 used to hang once in about two days and I thought it is normal. Lately, it is giving a lot of problems as it hangs as many as 40 times in a day, that too for no reason at all.
To make it work, I have to restart it by taking out battery or long pressing the power key, and sometimes doing so even 10 times doesn't solves the hanging issue. I am on stock rom 4.1.2 (India) fully updated and never rooted.
Do you think maybe RAM or the Processor is at fault. Is there anyway or app to test these for defects.
Although it is painstaking but I am planning to reset the phone, do you guys think it will help?
Any chance my phone is heading towards SUDDEN DEATH, are these the symptoms?
I am so fed up of rebooting it again and again and in the process missing important calls.
Help me deal with this situation guys..
No sds is sudden and india has the latest sds fixed roms available. Yeah you can start with a factory reset
Sent from my GT-N7100
UtkarshGupta said:
No sds is sudden and india has the latest sds fixed roms available. Yeah you can start with a factory reset
Sent from my GT-N7100
Click to expand...
Click to collapse
Resetting was the last thing on my mind, but I guess you are right. Will start with factory reset and post further development.
Have ame problem here.
Don't know yet seems to be sds problem?
Is posible to replacement new unit?
Sent from my GT-N7100 using Tapatalk 2
It is usually because of the bad update or the high usage of the storage (keep in mind when you used the first time and compare it to now, there is a diference) the best that you can do is to do full wipe as they said but if this doesnt work try to update using emergency firmware (or something similar) via Kies it must be enough.
If it doesnt help then is a problem of the device itself or maybe the official update if more than one is having the same issue
Hope it helps to you, bests
Sent from my GT-N7100 using xda app-developers app
Factory reset solved my problem for now but overall the phone seems to lag a bit, but not a cause for concern. I guess the hangs were largely due to number of messages stored, call logs and maybe some applications.
Though there was one weird thing, when I connected my phone to kies for backing up, the firmware section displayed that my firmware version is not allowed to update via kies.
Absolutely same issue , in my case even factory reset hasnt worked. Have tried unmounting the externl sd and kept very basic vanilla apps. It hangs every time i interact with the screen and the only wy out is to hard boot it.
PLs help if someone has the same issue.
Had the same problem with rebooting only was 2-3 times a day. Changing to a different firmware fixed it. Download a newer firmware wipe cache, dalvick and factory reset then flash new firmware. Hopefully will fix your issues guys.
sahiltyagi said:
Absolutely same issue , in my case even factory reset hasnt worked. Have tried unmounting the externl sd and kept very basic vanilla apps. It hangs every time i interact with the screen and the only wy out is to hard boot it.
PLs help if someone has the same issue.
Click to expand...
Click to collapse
Yep, It doesn't work in my case too. rebooting into recovery and deleting the cache folder helps a while, and then it comes back.. will go to a service center tomorrow if it's still happening
iqbalbaskara said:
Yep, It doesn't work in my case too. rebooting into recovery and deleting the cache folder helps a while, and then it comes back.. will go to a service center tomorrow if it's still happening
Click to expand...
Click to collapse
I had the same problem
1: Did a factory reset
a: didnt install anything...the moment i went to set up the email it hung.
2: Took to the service centre
a: He reinstalled the stock ROM. After rebooting and while setting up the device it hung again.
b: Tomorrow they will either changes the PCB or the screen depending on what the tech feels is the issue.
Regarding memory... after a reset it shouldnt have hung. + have tried it without the 32gb card also.
Will let you know what comes out.
But yes it was working fine and all of a sudden it started hanging last few days.
the strangest thing is that sometimes the screen doesnt respond to touch EXCEPT the notification bar, it goes alright in that area, I can even toggle the buttons and swipe away the notifications, but if i close the notification bar, open it again, ANY action (swiping notifs, clicking button, etc) would instantly hung the phone. strange eh?
i had the same problem, and i checked my emmc and it was the one that has the bug. Just finally got the SDS today.
guys, if you haven't already, check this thread: http://forum.xda-developers.com/showthread.php?t=2093599&highlight=sds my phone has that chip. I think I'm going to have to take it to the service center tomorrow
---------- Post added at 08:59 PM ---------- Previous post was at 08:58 PM ----------
xryousukex said:
i had the same problem, and i checked my emmc and it was the one that has the bug. Just finally got the SDS today.
Click to expand...
Click to collapse
thanks for sharing, have you take it to the service center? how long will they need to fix it?
iqbalbaskara said:
guys, if you haven't already, check this thread: http://forum.xda-developers.com/showthread.php?t=2093599&highlight=sds my phone has that chip. I think I'm going to have to take it to the service center tomorrow
---------- Post added at 08:59 PM ---------- Previous post was at 08:58 PM ----------
thanks for sharing, have you take it to the service center? how long will they need to fix it?
Click to expand...
Click to collapse
I'm in the U.S. and we don't have a service center since these phones are only for International. Samsung USA says they won't fix it, and EU says we aren't EU residents. I have the same chip.
The only place i found so far is http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-note-ii-emmc-chip-repair-replacement/ and they charge $150. They have a facebook that mentioned that were able to get the emmc chips this past week and have now started to do repairs.
They are located in Texas so I'll be sending my phone to them this upcoming Monday. We'll see how long it takes and the turn around time. If anyone else has tried them, please let us know how long it took.
xryousukex said:
I'm in the U.S. and we don't have a service center since these phones are only for International. Samsung USA says they won't fix it, and EU says we aren't EU residents. I have the same chip.
The only place i found so far is http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-note-ii-emmc-chip-repair-replacement/ and they charge $150. They have a facebook that mentioned that were able to get the emmc chips this past week and have now started to do repairs.
They are located in Texas so I'll be sending my phone to them this upcoming Monday. We'll see how long it takes and the turn around time. If anyone else has tried them, please let us know how long it took.
Click to expand...
Click to collapse
Send your device to wherefrom you bought it. As long as you have your invoice, they have to fix it.
went to the service center and they say they'll replace the circuit board on monday, no questions asked
Hello!
I'm glad (unfortunately for us) to see that some people have the same issue. I bought the phone on November and I have the "hangs" since 1 week. Hard reset didn't solve the problem for me, even without restoring my backups or apps. I tried to remove the SD card, and the problem persist.
I think the SDS problem is not exactly this one, but It may be related.
Today, I'll go to the seller and I'll see what I can do...
Thank you for the information! I'll post with the updates of my case
Hi, my phone suffered from bootloop and according to the tremendous posts about this problem the answer was always laying in buying a new original battery, which i did but still the bootloop continues, may open for a few hours then bootlop again,
if anyone could help that would be appreciated because i'm giving on the phone now
mines doing the same thing with the original battery..
interested in the answer before i outlay for a v20.
---------- Post added at 11:24 PM ---------- Previous post was at 10:33 PM ----------
I had a bit of a hunt around and i noted that the phone has an issue with the WiFi.. so i disabled the WiFi and Bluetooth in the settings
as a precaution i ran some tape over the NFC and Qi battery charging connectors, blocking these connections.
if this solves the problems.. ill be outlaying for a new phone soon.. ill wait for the G6 to come out before considering the v20
ill post back in a week if i experience the same issues.
looks like this did not fix the issue.. i will try a custom ROM tonight to see if it fixes the issue..
i am wondering if the battery is the key here, it is possible that the software is seeing the battery voltage and when it drops below a certain volt the OS automatically shuts down the phone to protect itself..
as i only see the boot loop when i am launching particular heavy load apps. and i don't see this happening when the battery is at 100%
---------- Post added at 03:36 PM ---------- Previous post was at 03:21 PM ----------
https://forum.xda-developers.com/lg-g3/general/random-shutdowns-reboots-t3553374
some interesting points here.
Do you have a reboot (phone restart) or a bootloop (phone try to restart but it never pass the boot screen)?
Have you noticed temperature issues?
If you have already tried return to stock and the problem continue it probably is a hardware failure.
Regards
Sent from my phone
ypsmav said:
Do you have a reboot (phone restart) or a bootloop (phone try to restart but it never pass the boot screen)?
Have you noticed temperature issues?
If you have already tried return to stock and the problem continue it probably is a hardware failure.
Regards
Sent from my phone
Click to expand...
Click to collapse
before with the old battery it started to freeze and restart then it got worse, it closes and bunch of bootloops then open then 2 minutes and bootloop again, until it permanently bootlooped ,so i bought new original battery from lg store and the phone opened first time then 5 mins later it restarted then bootlooped once again, thing is, by the new battery it opens sits for an half an hour or less then bootloop, with the old battery it never passes the lg logo.
mrpea said:
looks like this did not fix the issue.. i will try a custom ROM tonight to see if it fixes the issue..
i am wondering if the battery is the key here, it is possible that the software is seeing the battery voltage and when it drops below a certain volt the OS automatically shuts down the phone to protect itself..
as i only see the boot loop when i am launching particular heavy load apps. and i don't see this happening when the battery is at 100%
---------- Post added at 03:36 PM ---------- Previous post was at 03:21 PM ----------
https://forum.xda-developers.com/lg-g3/general/random-shutdowns-reboots-t3553374
some interesting points here.
Click to expand...
Click to collapse
thanks for the share , tell me if you tried anything and whether it works or not.
Farius said:
thanks for the share , tell me if you tried anything and whether it works or not.
Click to expand...
Click to collapse
Hi , I have the exact same problem and i thought changing battery is the solution but i got my new battery today and everything was fine at the begining but later when the phone tried to update some apps again it turned off .
I had this issue suddenly few days ago after install some apps or some updates .. I am hoping it is because of software issues and can be fixed after factory reset.
(phone able to start when it is colder , so i tried to put it 2 min in freezer and it started but just tried one time , i dont know just coincidence )
I tried to update my firmware to 6.0 MM , so nothing change.
Looks like nobody able to solve this problem. Now my phone is just garbage
1sin1 said:
Hi , I have the exact same problem and i thought changing battery is the solution but i got my new battery today and everything was fine at the begining but later when the phone tried to update some apps again it turned off .
I had this issue suddenly few days ago after install some apps or some updates .. I am hoping it is because of software issues and can be fixed after factory reset.
(phone able to start when it is colder , so i tried to put it 2 min in freezer and it started but just tried one time , i dont know just coincidence )
Click to expand...
Click to collapse
I noticed the same thing, it works fine when it's cold or normal then lag and restart when it's hot (38C+), today i tried to disable heating lag and the thermal mitigation thing but still doing the same..
Farius said:
before with the old battery it started to freeze and restart then it got worse, it closes and bunch of bootloops then open then 2 minutes and bootloop again, until it permanently bootlooped ,so i bought new original battery from lg store and the phone opened first time then 5 mins later it restarted then bootlooped once again, thing is, by the new battery it opens sits for an half an hour or less then bootloop, with the old battery it never passes the lg logo.
Click to expand...
Click to collapse
It seems the problem is related to hardware.
Sent from my LG-D855 using Tapatalk
After so many tries finally "kind of" stable solution i found.
Rooted phone and use No-frill Cpu app to block my cpu speed on 1 ghz .. so far no loop or restart ... we will see
1sin1 said:
After so many tries finally "kind of" stable solution i found.
Rooted phone and use No-frill Cpu app to block my cpu speed on 1 ghz .. so far no loop or restart ... we will see
Click to expand...
Click to collapse
what about now ?
Farius said:
what about now ?
Click to expand...
Click to collapse
It is even better now because I opened up my phone and heatsinked the cpu .. I am still using lower cpu freq but even works without cpu adjustment after heat sink .. Now using 1.5 ghz just for incase.
(Still sometimes turning off itself when charging) Would be even better with heat sink pad i guess
I had heard that adding a 0.5mm thermal pad to the SOC makes its run a little cooler, but i do seem to think the battery is the main culprit, the main problem with getting a replacement battery which operates within the same tolerances.
downclocking the cpu to 2.0-2.2ghz with a fresh battery and adding a thermal pad on the SOC seems like the best solution..
I have since upgraded to a v20.. so hopefully it doesn't happen with that phone..
Some old original baterries have an issue that swollen a bit and the phone starts rebooting itself. But I don't remember from which year the good ones are manufactured.
Try testing with a generic battery (as I do) to see if that's the issue.
If you still have the battery's warranty, claim it.
I got a new battery, then charged it fully, then added an empty SD card to back up the data. Connected to a fast charger., otherwise it is not enough power to keep it on, causing a bootloop. The phone must be cool, not powered on for some time (overnight, in my situation).
I was able to back up the data., my main goal. I have heard others being able to fix it, and it works for some time, but soon enough this trick no longer works.
I have the K8 Note phone with Android 8 and security path level : 5 March 2019
My phone is switching off unexpectedly and when I switch it on, it boots up to the lock screen and then switch off immediately. This is repeating at different times for different actions and I cant identify a pattern to replicate it. If I keep the phone connected to the charger then this issue doesn't happen. When I remove it from the charger it will switch off when I try to open some app or sometimes when receiving calls or making calls. It also happens when I open the app drawer. I have done a factory reset and also booted to safe mode,but still the issue is there. All these switch offs happened when the phone was not connected to the charger and the battery charge is more the 50%. I am not sure if the phone is showing the correct battery levels. Also I am not sure if any of the google apps is causing this issue. Can someone help me solve this issue?
So nobody has this problem ? or no one wants to reply?
i also have this problem & many users too after the last oreo update
i try every thing to solve it hard rest , downgrade & custom roms and every thing but does not work !
Kareem walaa said:
i also have this problem & many users too after the last oreo update
i try every thing to solve it hard rest , downgrade & custom roms and every thing but does not work !
Click to expand...
Click to collapse
I didnt try any custom rom. I cannot find any official response from Lenovo about this issue. I will never buy Lenovo products again, and actively discourage people from buying.
sreeju1 said:
I didnt try any custom rom. I cannot find any official response from Lenovo about this issue. I will never buy Lenovo products again, and actively discourage people from buying.
Click to expand...
Click to collapse
I had exact same issue. Replacing the battery solved the issue. If you go to Lenovo Service Center, they will tell you that, it is a motherboard issue. But in reality it is a battery issue.
sreeju1 said:
I have the K8 Note phone with Android 8 and security path level : 5 March 2019
My phone is switching off unexpectedly and when I switch it on, it boots up to the lock screen and then switch off immediately. This is repeating at different times for different actions and I cant identify a pattern to replicate it. If I keep the phone connected to the charger then this issue doesn't happen. When I remove it from the charger it will switch off when I try to open some app or sometimes when receiving calls or making calls. It also happens when I open the app drawer. I have done a factory reset and also booted to safe mode,but still the issue is there. All these switch offs happened when the phone was not connected to the charger and the battery charge is more the 50%. I am not sure if the phone is showing the correct battery levels. Also I am not sure if any of the google apps is causing this issue. Can someone help me solve this issue?
Click to expand...
Click to collapse
i have lenovo k8 note device one of them was date 1 month ago and another had same issue bootloop kinda since yesterday, i had manage to flash rom but after that same boot loop issue, i dont know waht to do
Can replacing battery solve the issue
Please tell me my k8 note switch off problem solve with new battery?
---------- Post added at 06:06 AM ---------- Previous post was at 06:03 AM ----------
kk9999gada said:
I had exact same issue. Replacing the battery solved the issue. If you go to Lenovo Service Center, they will tell you that, it is a motherboard issue. But in reality it is a battery issue.
Click to expand...
Click to collapse
Can it solve switch off issue please tell
sauravsaka said:
Please tell me my k8 note switch off problem solve with new battery?
---------- Post added at 06:06 AM ---------- Previous post was at 06:03 AM ----------
Can it solve switch off issue please tell
Click to expand...
Click to collapse
Yes, if your phone doesn't switch off when connected to charger and switches off suddenly as soon as you unplug or after a few minutes. Then probably the battery is at fault and needs to be replaced.