Hi,
Anyone here with a note 4 or edge who received the October Android Security update have input whether the glitches with soft reboots have been fixed?
Let me know.
Sent from my SM-N915W8 using XDA-Developers mobile app
Nope, the patch did not fix the soft reboot issue..
rodmc123 said:
Nope, the patch did not fix the soft reboot issue..
Click to expand...
Click to collapse
but why not? I don't like the soft reboots ? They are not fun
Sent from my SM-N915W8 using XDA-Developers mobile app
TheOneOleksiy said:
but why not? I don't like the soft reboots They are not fun
Sent from my SM-N915W8 using XDA-Developers mobile app
Click to expand...
Click to collapse
updated mine to dpj1, reboots still exist... really not funny at all.
Anyone know I was of downgrading to kitkat without voiding the warranty?
Sent from my SM-N915W8 using XDA-Developers mobile app
I wiped and reimaged and still have freezing and soft boots.
I got the November 1st security patch, does this fix all the reboots?
I don't know what reboots you guys are talking about. Haven't experienced this on my note edge. Whenever it does happen it's because of a custom kernel
TheOneOleksiy said:
I got the November 1st security patch, does this fix all the reboots?
Click to expand...
Click to collapse
Confirmed I keep receiving the soft reboots after the novemeber update
Darth-Kadd said:
I don't know what reboots you guys are talking about. Haven't experienced this on my note edge. Whenever it does happen it's because of a custom kernel
Click to expand...
Click to collapse
I don't have a custom kernel and it still happens. The ony thing that gets rod of it is having no screen security. It probably still reboots on its own without you just don't get prompted because the phone doesn't ask to put your password in. Some have said that if you give it to Samsung they will fix it? Can anyone confirm?
TheOneOleksiy said:
I don't have a custom kernel and it still happens. The ony thing that gets rod of it is having no screen security. It probably still reboots on its own without you just don't get prompted because the phone doesn't ask to put your password in. Some have said that if you give it to Samsung they will fix it? Can anyone confirm?
Click to expand...
Click to collapse
I get these soft reboots constantly... almost every time I lock the screen?
Genuinely flummoxed that no one has come up with a fix yet. ..
EDIT: I can confirm, there are no reboots, no password requests, and after some weeks now not even more battery drain , seems that this new firmware solved the problems.
So, finally I got rid of the random reboots and the lockscreen-problems.
I updated to the most recent version of MM 6.0.1 (see attached screenshot), and did it as follows:
first I made a backup of all my user files. I deleted all stored fingerprints, and disabled all lockscreens.
Then I updated via Samsung Kies (first time ever, did NOT use the OTA)
after finishing the update I booted into recovery and made a factory reset twice!
After reboot and initial setup I enabled fingerprint lockscreen and registered my fingerprints, then reinstalled all apps from app store, done.
After two weeks not a single reboot, no crash, fingerprint works flawless!
Finally !
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please register your request for a response from the Top software team at Samsung here....
https://us.community.samsung.com/t5...-Issue-Mods-Need-To-Escalate/m-p/50403#U50403
Related
Hello i have a q about this bug or what is it so after i charge my phone sometimes there are portions of the display that wont respond to touch
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
something like that ... It hapend twice first time i dont know how i fix it ...any ideas
Sent from my Nexus S using xda a ppm developers app
rdk00 said:
Hello i have a q about this bug or what is it so after i charge my phone sometimes there are portions of the display that wont respond to touch View attachment 2610705 something like that ... It hapend twice first time i dont know how i fix it ...any ideas
Sent from my Nexus S using xda a ppm developers app
Click to expand...
Click to collapse
have the same issue a bit lower on my screen(broken digitizer) and it can be fixed only with a new display
Screen Tile Not respondig
Having the same issue here, as described above , but it only happened like 2 weeks ago tops , like when i updated to latest Kitkat (slimKat stable 3 back then )...
Is this definitely a hardware issue or some broken code?
Been reinstalling some kitkat here, but the problem persists,...
I thought the problem was the firmware because of some post i spotted pointing at slimkat or something...
Did any of you get this problem AFTER installing slimkat or even latest TWRP (2.7.0.0) ? (i updated both kind of the same time)
I had that problem on 4.1/2/3 roms. Disappeared on kitkat, fyi.
Sent from my Nexus 5 using Tapatalk
ej8989 said:
I had that problem on 4.1/2/3 roms. Disappeared on kitkat, fyi.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
thnx for reply,
it emits hope... which i needed for this phone...
weird issue though...
Do you mind to share your last working configuration ...?
Rom+kernel+recovery ...
that would be tremendous help...
I also noticed you ve hardbricked your Nexus s ... though..
Ic3_C0ld said:
thnx for reply,
it emits hope... which i needed for this phone...
weird issue though...
Do you mind to share your last working configuration ...?
Rom+kernel+recovery ...
that would be tremendous help...
I also noticed you ve hardbricked your Nexus s ... though..
Click to expand...
Click to collapse
ROM: euroskank cm11
Kernel: default
Recovery: TWRP
My phone was bricked because of a design flaw somewhere in the exynos chip. Samsung wants me to pay $200 for board replacement.
Hello!
Eversince my stock N5 got the latest update (lmy48m) my phone havr started to slow down and close apps. This have happened before and then i waited it out for a new firmware to arrive, but now it's back
I started looking at how much ram the phone uses and this is where things started to scare me a bit
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When i saw this i restarted my phone and got this:
How is this possible? And is my phone still using too much memory? Chrome is still really laggy and some games still closes themself without warning, and it's pretty annoying..
Facebook and whatsapp killing your phone.
Sent from my Nexus 5 using Tapatalk
LMY48M problem memory again
This memory problem had been solved by Google in the previous update, but after that last update LMY48M the problem happen again, I'm waiting for a new fix Google.
Me too. After updated to LMY48M, it seems that memory leak problem is back. I have a nexus 6 updated too but it doesn't seen to have this problem.
ldubs said:
Facebook and whatsapp killing your phone.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Any fix for this?
carloscarosa said:
This memory problem had been solved by Google in the previous update, but after that last update LMY48M the problem happen again, I'm waiting for a new fix Google.
Click to expand...
Click to collapse
abc941121 said:
Me too. After updated to LMY48M, it seems that memory leak problem is back. I have a nexus 6 updated too but it doesn't seen to have this problem.
Click to expand...
Click to collapse
I guess there isn't anything i could do besides wait for a fix from Google?
Ive the same issue since I upgraded the phone. I dont understand how can happen this again. Until android 6.0 we will have the issue, I dont think google fix the problem.
Yup, here's another confirmation of this issue, from my side.
Does clearing partition cache help?
klappa said:
Does clearing partition cache help?
Click to expand...
Click to collapse
Was waiting for a few days of use before replying. This made quite a difference, but there were a couple times where a restart was needed - I don't know if it was from the same issue though. It's better now, anyway... no longer restarting 2-3 times a day.
blassster said:
Was waiting for a few days of use before replying. This made quite a difference, but there were a couple times where a restart was needed - I don't know if it was from the same issue though. It's better now, anyway... no longer restarting 2-3 times a day.
Click to expand...
Click to collapse
Yeah, a simple restart seem to do the trick for a day for me. Still have to restart once a day or every second day.
Sorry for irrelevant post I really need help about how to root N5 on this latest build LMY48M.I have tried all one click root apps but no luck plz help
Sent from my Nexus 5 using Tapatalk
Have you tried flashing supersu zip in recovery?
Had to restart twice today. At least M is around the corner... hopefully this is fixed.
Hi, this thing is trying to kill me for a long time since my Z3 was on 5.1.1.
Ok, in short.
I had this on 5.1.1 (any)
No problem at all on 6.0 (.570/.151)
The problem is back on N Preview (2/3) absolutely vanilla. No root or ad-blocker.
I have to restart my phone every time this happens. Clearing cache will not help at all. It has been said somewhere that this problem is not related to the rom. (Yeah, but I don't think so.)
So, whoever have this problem and fixed can help me out? Or is it the known problem which cannot be fixed?
Thanks in advance.
Ps.Image from Google.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
doresreturns said:
Hi, this thing is trying to kill me for a long time since my Z3 was on 5.1.1.
Ok, in short.
I had this on 5.1.1 (any)
No problem at all on 6.0 (.570/.151)
The problem is back on N Preview (2/3) absolutely vanilla. No root or ad-blocker.
I have to restart my phone every time this happens. Clearing cache will not help at all. It has been said somewhere that this problem is not related to the rom. (Yeah, but I don't think so.)
So, whoever have this problem and fixed can help me out? Or is it the known problem which cannot be fixed?
Thanks in advance.
Ps.Image from Google.
Click to expand...
Click to collapse
I assume that you unlocked your bootloader, right?
Same for me. On a locked bootloader and Android N preview 3.. But I do have to say that the problem occured after unlocking my bootloader..
Still, it is locked now, I have my DRM keys restored and it still gives me issues
I might know what's going on. It could be related to some DRM functions when unlocking bootloader. As far as I know downgrading to KK or upgrading to official MM fixes it. Othen then that ROM's like LP, N and MM concept has this problem. I think sony fixed this in official MM. Anyway for Lollipop and Concept you can try to use this fix, but you need root http://forum.xda-developers.com/showpost.php?p=64763489&postcount=4
It helped for me and it should help for you.
Cheers
Nojus33 said:
I assume that you unlocked your bootloader, right?
Click to expand...
Click to collapse
Me Gusta said:
Same for me. On a locked bootloader and Android N preview 3.. But I do have to say that the problem occured after unlocking my bootloader..
Still, it is locked now, I have my DRM keys restored and it still gives me issues
Click to expand...
Click to collapse
Well, this might be the cause. The weird thing is the problem was gone with MM. I'm confused now lol
Btw. I'm on locked right now but I had unlocked the bootloader before.
Nojus33 said:
I might know what's going on. It could be related to some DRM functions when unlocking bootloader. As far as I know downgrading to KK or upgrading to official MM fixes it. Othen then that ROM's like LP, N and MM concept has this problem. I think sony fixed this in official MM. Anyway for Lollipop and Concept you can try to use this fix, but you need root http://forum.xda-developers.com/showpost.php?p=64763489&postcount=4
It helped for me and it should help for you.
Cheers
Click to expand...
Click to collapse
Thank you so much. I'm on MM right now but if I can get root access on N, I will try and inform you back.
Edit: I completely forgot about that android N rooting thread. It has cool stuff right now so I'm going to unlock and try it right away.
Edit2: That method failed for me so I will try it later when I have time.
I got this problem too on android n preview 3, locked bootloader and not rooted. I noticed that whenever it happens, video recording fails as well, which might help resolve the issue. rebooting takes care of it momentarily though.
The long waiting update is here.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Boy do I feel stupid going through all the hassle to "softtware convert" it to a TA-1025 to get Oreo Beta a while back.
I bought into the rumors about not getting Oreo too hard.
Is this via an OTA? Have you done anything to the phone or is it just like you've taken it out of the box? I haven't received the update yet. Also what country are you in? I'm in Australia. Hopefully I get the update, even though nokia tech said I wouldnt out of the region
danielace said:
Is this via an OTA? Have you done anything to the phone or is it just like you've taken it out of the box? I haven't received the update yet. Also what country are you in? I'm in Australia. Hopefully I get the update, even though nokia tech said I wouldnt out of the region
Click to expand...
Click to collapse
It's via OTA. I'm in Taiwan and I haven't done anything to my phone yet. I did read on other forum that some people haven't received yet, maybe it just need a few days to receive.
Sent from my TA-1003 using XDA Labs
Wrong thread for my original post, sorry.
Yep I just checked and Android Oreo OTA is here! Woohooo
TA1000 got it too via OTA. Working fine, feels snappier. But the app to add more languages crashes (locale more pro) so I'm stuck with English for now which is not a big deal though.
5T33Z0 said:
TA1000 got it too via OTA. Working fine, feels snappier. But the app to add more languages crashes (locale more pro) so I'm stuck with English for now which is not a big deal though.
Click to expand...
Click to collapse
Try to clean data for this app (locale more pro) in apps admin. The best is to make a hard reset after the phone have been updated to Oreo.
I think the official Android 8.0 ota update killed my recovery. There simply just is a broken robot saying "no command" where the recovery used to be. GD Nokia bs phone.
5T33Z0 said:
I think the official Android 8.0 ota update killed my recovery. There simply just is a broken robot saying "no command" where the recovery used to be. GD Nokia bs phone.
Click to expand...
Click to collapse
When you see no command there in recovery
Hit power button and volume up button together, just hit, donot hold it
U will find the recovery mode
sltushar said:
When you see no command there in recovery
Hit power button and volume up button together, just hit, donot hold it
U will find the recovery mode
Click to expand...
Click to collapse
Thank you, I'll try it later.
Btw, after Oreo update you have problem with notifications? Gmail, Yahoo Mail, Whatsapp give me notification only after I open them.
Vivio said:
Btw, after Oreo update you have problem with notifications? Gmail, Yahoo Mail, Whatsapp give me notification only after I open them.
Click to expand...
Click to collapse
Goto bettery option
Background activity manager
Turn of all of them
Done
sltushar said:
Goto bettery option
Background activity manager
Turn of all of them
Done
Click to expand...
Click to collapse
At autoactivate or lock screen?
Vivio said:
At autoactivate or lock screen?
Click to expand...
Click to collapse
Setting then battery then background and other activities
Thank you, sltushar! It has helped a lot. Is not perfect, but it more manageable.
Has anyone got 8.1 yet
danielace said:
Has anyone got 8.1 yet
Click to expand...
Click to collapse
Me using 8.1
Hiya peeps. Id just like to ask you experts with a little help.
For the past week my phone suddenly started locking up and freezing and rebooting itself and ive had its for like 2 years. ok its always suffered from a little lag when like typing but i got used to it. I recently wiped its cache but nothing has changed. Its always had issues with the battery with random shut offs at from anything from 30% to even 50+% ive replaced the battery before and i guess its time to replace again.
Main question is my phone just literally just restarted itself now and has come to this screen which i will upload a photo.
I cant remember installing a custom rom since buying it. i did buy it 2nd hand though.
But what does this mean in the photo?.
last night i downloaded marshmallow 6.0.1 firmware because i wanted to see if re firmwaring my phone might later this evening will help in the mean time while i will buy a new battery.
.its been stuck on this screen for like 20 mins already and im scared to turn my phone off
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You need to install Odin on your PC and flash a stock rom.
devdawg8 said:
You need to install Odin on your PC and flash a stock rom.
Click to expand...
Click to collapse
So my phone isnt using stock rom already? So i presume the firmware i downloaded last night is also custom rom then.. Where do i get hold of an official firmware?
Thanks for replying btw
YumiStar said:
So my phone isnt using stock rom already? So i presume the firmware i downloaded last night is also custom rom then.. Where do i get hold of an official firmware?
Thanks for replying btw
Click to expand...
Click to collapse
It is using a stock rom, but it is in download mode. May I ask what device you have?
devdawg8 said:
It is using a stock rom, but it is in download mode. May I ask what device you have?
Click to expand...
Click to collapse
Ok after like 40 mins i did take the risk of taking out the battery as i'd assume my phone wouldn't be doing anything in its state. It rebooted again but still suffering from the issues i mentioned previously.
Im guessing this wouldnt be the last time this will happen and probably will see this screen again in future.
I own a Galaxy Note edge. Unlocked, Bought in england