Ok guys it started since I migrate to 5.1.1 ROM, flashed clean DN 0.3 note 5 port, and the phone would just go black at least once per day, nothing seems to work even a hard restart (volume up + power button for 20 sec) only a battery pull would restart the phone. So I figured it must be the ROM ( noone in DN 0.3 thread seems to have this problem) . So I flashed the original 5.1 firmware for my country, rooted it and used it for a day to find out it does the same! I'm really not sure what seems to be the culprit. I couldn't find a conclusive pattern on the bsod however last time I noticed it happened right before I was disconnected from public wifi, perhaps it is the modem? Maybe it's root and bootloader conflict with 5.1 firmwares? (the phone boots up, so it cannot be bootloader? Or I don't understand something about what bootloader does?) Any one has encountered the same problem? Any clues on how to fix it?
Just happened again while wifi connection was weak and I think it happens right before it got disconnected or switched to other connection mode or different wifi
Read around the forums that people are having bsod in combination with Tasker and secure settings to switch off secure keyguard, I never use this option, just use Tasker to automate sync processes, Uninstalled it nevertheless. Will see if it helps
Happened again... Noticed that the battery percentage drops quote significantly after the battery pool, here is the screenshot
{
"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"
}
Related
Hello you all peeps
I noticed some weired things happening to my phone. Sometimes when I want to use my phone I need to put in my PIN, never realised what it was.
10 minutes ago I received a text message, i read it and ploooops, my phone was rebooting out of nothing. After that my phone is working again, but watch this:
{
"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"
}
There's just a part gone, I know it was there before the reboot. Now i realize that i already had this issue a few times before.
Does anybody know where this strange thing come from?
Oh, I am running Litening rom with CF kernel, not sure if i had this issue before flashing the rom.
I had exactly the same thing on KE7. My phone rebooted itself at least once a day. I tried uninstalling and disabling all the apps I could think of but nothing resolved it.
Eventually, I performed a factory reset which has resolved the issue - it's now been running for 3 days without a reboot.
I had a spontaneous reboot only once - phone was overheating due to well, me messing around :-D
Check if heat is not a problem du to a runaway process
The heat is not a issue since it rebooted too when i didn't use the phone.
I deleted some Samsung bloatware too, perhaps that is the problem. Will do a factory reset, but not for now.
Good(?) to hear I'm not the only one with this problem
Same problem here, but i think it's related with the known bug of "suspend" and events/0 process and there is nothing to do but waiting for a fix :/
{
"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"
}
This one is 378MB and reportedly brings support for Wireless Internet Service Provider roaming (WISPr) and also includes a fix for RTT (Real Time Text) and the April Android security patch. I have no idea if this update will really improve much of anything for us, but I have reluctantly installed it hoping for better battery life.
Enjoy.
And introduced new bugs which prevent many widgets from updating or working properly...
Can some body post firmware or OTA here?
Many people with 6.0.1 cant update. Waiting for firmware.
Has anybody had charging issues since taking the update? Seems like fast charge won't work for me unless the screen is off. If I'm watching YouTube or streaming anything it won't charge the phone at all. Charging at 282 mA right now with screen on, and 2,561 mA when screen is off. And only when it's off.
Besides the kernel being slightly more efficient on battery, so far I'm not seeing any real benefit of this OTA either. In fact, this morning as I was wrapping up a BT business call, I pressed the headset's call button to end the call. Nothing happened, I then pressed end call in the phone app repeatedly and it wouldn't hang up. I had to shut off Bluetooth altogether from the quick toggles in order to hang up.
That was a discouraging experience to say the least...
Hi,
i got the following issue with my A5:
I accidentally dropped it in the sink on Friday, then turned off the device and let it dry.
Tried turning it on on Monday and it was unresponsive. Left it just like that and roughly 15-30 minutes later it did turn on just to turn itself off a while later. (Note: Tried to charge the device and it said the battery temperature is too low to allow it to charge)
It hasn't turned on since then, i can't boot it with any conceivable button combination. Not even Recovery Mode, the only mode that boots is the Download Mode. Screen looks fine, and it still turns on, great.
So i decided to take an eternity with my 384 kbit/s connection to grab some firmware and flash it.
Firmware in question is the following from Samsung-Firmware:
PDA Version: A510FXXU4CQH2
CSC Version: A510FOXA4CQH2
PHONE Version: A510FXXU4CQH2
Filename: A510FXXU4CQH2_A510FOXA4CQH2_A510FXXU4CQH2_HOME.tar.md5
Odin does recognize the device and flashed it with these messages and settings:
{
"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"
}
The problem now is that it still doesn't boot/restart, and still only goes into Download Mode and i am unsure how to get it to work at this stage since the hardware seems to be fine overall.
Any help would be appreciated.
Greets,
Frost
Bumping since i still haven't found a solution to the problem. Should also note that i typo'd on the thread title and meant Download Mode, not Recovery Mode.
So after i update my phone from nougat to oreo via wifi i get worst battery life on standby and sot. I check my firmware ( my lg its a unlocked lgus997 ) and it was the version us99720a i check on lg official webpage and it said that the last update for my phone was us99721b . i do not know why i didnt get that version when i updated it via wifi.
Long story short i download on my pc the us99721b kdz, then i factory reset the version i get first and put my phone on download mode and connected it to my pc. And using lgup i flashed it with the option "update" , when it was done i factory reset it again and stop home app to times because there its something wrong with that app that also drained my battery.
This are the results, i went to sleep for about 6 hours with all services turned off including wifi and battery saber turned on, after that i turned on wifi and turned off battery saver for 3 more hours on standby and didnt low any porcentage. So my phone last night was 100% and after 9 hours its exactly the same. Now i testing sot, while i was writing this post drop a few. Im on 95% right now
Im new on the forum. I do not know how to add my screencaptures xD
I added them on my drive but dont let me post externals urls :/
{
"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"
}
My ZE553KL (I use it as a home device control, small tablet) keep loading/reloading for 3 hours now. I CANNOT SHUT IT DOWN. everytime I have this vibrate boot, ITS SUPER ANNOYING.
It show the bootloader then reboot, then show the bootloader and so on. Buttons are unresponsive.
Only think I can do is press up and get to screen number 2 for exactly 6 second (my computer then recognize it).
I cannot remove battery (hello soldered battery). or shut it down, I guess at some point It will drain battery but.
I have no idea what is happening, please help?
{
"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"
}
Ouch
Play with it. Proper button sequence and timing is everything. It's easy to not hit the right button at the exact moment. Allowing the battery to auto shutdown may break the cycle. Don't attempt to solder the battery without a good iron and skillset. You need to be fast about it.
If the OS is pre Pie it's suspectable to rootkits that require a reflash to erraticate.
A hardware failure is also possible.
A bad coded 3rd party apk can also boot loop you. That's worse than a normal boot loop though.
It's definitely corrupted... hopefully someone here who has seen this before and/or knows more about that line of phones advanced troubleshooting can help you.