Greetings,
I have been tinkering with my GF's 850f with the hopes that she will forget about those damn expensive Iphones and embrace the Android way... but so far the Alpha has been acting up. I will explain the issue:
Sometimes, seemingly at random, the phone will get stuck and get really slow. I think I managed to isolate the issue because it seems to happen after using an app that uses the microphone (Duolingo, Whatsapp). After she uses the microphone, the phone will remain stuck. You can get out of the app and close it, but it won't open again and the phone gets slow. Everything goes back to normal after I reboot the phone, but it invariably happens at least once a day. It doesn't happen everytime she uses microphone.
Things I've tried:
Upgraded to official Lollipop using the France image (Clean flash)
Installed custom recovery (First 2.8.0 and then 2.8.6)
Flashed Ozcan ROM (Clean flash again)
It didn't happen on KitKat, it actually began after flashing the Lollipop upgrade, but I'm iffy about downgrading from Lollipop. Anyone knows a way to debug, single out or fix something like this?
Thanks in advance!
Related
Hello,
at start I have to apologize for my worse english; haven`t written and spoken it for years.
I have an Z2 and rooted it a few weeks ago; after that I installed Cyanogenmod Recovery.
I`ve tried a few Custom Roms but the problem is always the same: It crashes after some time, when I am trying to start an App.
Mostly Ingress and Google Maps. Often they work fine, like 4-6 times, they start without any issues.
But one time it crashes.
It restarts instantly and often tells me I dont have a simcard or it disables the Bluetooth-Connection.
The only possibility is to restart it and after that it works fine... for a few hours till I try to restart an app.
Sometimes it hangs itself up in a boot loop and i have to use Power + Vol Down to get into Cyanogenmod Recovery, but after that the restart takes up to 15 minutes because he calibrates all the apps.
It seems that the problem doesn`t happen when I am using Wlan.
Everything else works fine, no problems, but it is really annoying.
Any ideas?
Please? I have no clue and its really annoying. :crying:
-WTF- said:
Please? I have no clue and its really annoying. :crying:
Click to expand...
Click to collapse
1. cyanogenmod recovery is sh*tty
2. install a pre-rooted stock rom or a modified one like eXistenZ Premium, MoonWalker epidemic or PureX
never had such issues with these roms
Yeah, i know its ****ty, but i cant enter the bootloader anymore; it always starts the recovery. So i cant remove it.
The other problem is, that i tried 4 different roms and the problem seems to appear in every rom.
So it seems to depend on something else.
I'm having the same exact issue except that I don't get into bootloops
Mohaned98 said:
I'm having the same exact issue except that I don't get into bootloops
Click to expand...
Click to collapse
The bootloops seems to appear only under Ressurection Remix; i've installed CM again and they didnt happen anymore.
But the problem, that it crashes and after a restart often didnt find my SIM, is still there...
I don't know about RR rom as I haven't tried it but I'm getting the reboots on CM
So, since the past few days my i9300 keeps randomly rebooting. At first it was not that much of an issue but today it started to go into a boot loop.
Sometimes it finishes booting but before I can go into the settings to factory reset it, it crashes.
I also tried to get into TWRP but as soon as the logo shows up, it crashes.
I can't even use the download mode because, guess what happens: it crashes.
I really don't know what to do right now. I still have a spare motherboard but I'm not able to access it for another week. It would be a shame to throw away a perfectly fine motherboard if it is just a software thing.
Currently it is running the last version of SlimKAT that was released, I don't know which version of TWRP it is running, but I updated it just a few weeks ago. It is not using the original battery fom Samsung but one from Anker which should be fine.
If anyone needs more or specific information, I'm more than happy to provide it.
Hi,
just want to ask, you're stuck in bootloop at the "samsung" Logo or where?
Because I am having bootloops, too since 2 days. Phone kept restarting one or 2 times since last 3 days and when i got home on 1. november i put my phone to the charger and got back 20min later and saw it was rebooting.
Mine is stuck in optimizing apps or if i wait long time then it is at starting android: starting apps and i see when the color temperature of the phone changes (i think of the light sensor) it gets stuck and reboots.
just for docu (even if its not the same problem):
i have a 2nd spare s3 for testing here and to test ag. hardware issue i made a twrp backup and both are dying. after facory reset and installing apps i recognized that it is dying at the installation of telegram app and after that its going to the same bootloop on both phones. i checked telegram and seems to fit in, they updated their app at 1. november. and date code of last changes before the bootloop: telegram was modified. so for my problem it seems to be caused by telegram.
I am using bliss rom 6.1 (Andoid 6 Marshmallow, CM13 based) at i9300
sorry for maybe not beeing a help. I now found out that it happens to other app installations, too. so seems to be a problem deeper in android/interfering with this specific rom - maybe its play store . So far since it happens on 2 identical s3 with this rom I will have to change the rom now. :crying: (was stable >1year)
It is stuck on the Samsung Logo. I've been testing multiple ROMs for stabillity because after some time it will randomly crash (most of the time after 2 - 3 weeks of usage) but it was never this bad. I thought it was due to the fact that newer versions of Android need stronger Hardware, so I switched back to KitKat.
But Telegram could be a reason for this. I too use it and if you say they updated it, the timeframe would match.
I know that my spare motherboard is fully functional, with stock rom, not rooted or anything. I will swap it out as soon as I can and will install Telegram to try to confirm that this could be the reason.
Niggyminator said:
It is stuck on the Samsung Logo. I've been testing multiple ROMs for stabillity because after some time it will randomly crash (most of the time after 2 - 3 weeks of usage) but it was never this bad. I thought it was due to the fact that newer versions of Android need stronger Hardware, so I switched back to KitKat.
But Telegram could be a reason for this. I too use it and if you say they updated it, the timeframe would match.
I know that my spare motherboard is fully functional, with stock rom, not rooted or anything. I will swap it out as soon as I can and will install Telegram to try to confirm that this could be the reason.
Click to expand...
Click to collapse
good luck!
But if you'r stuck at the samsung logo, sounds even worse than mine. if your having a new board could at least be an option to check if its really not a hardware issue (you mentioned that its getting again unstable after some time)
for my problem I managed to backup most things out of the nandroid image and moved to ressurection remix with android nougat. the new rom is running fast and so far without any problem - hope it stays like that .
I have a Galaxy S III GT-I9300 I bought in 2014. After three years, I downloaded a custom ROM from xda-developers (android 4.3 is all I remember about it) and installed it successfully. It worked alright until one day when I wanted to sell the phone and a customer wanted to buy it on short notice, and I rushed to delete my files from the phone, but I destroyed the Android... I connected it to my laptop and shift-deleted some system files.... since then, the phone is delaying when trying to unlock (if i lock it now and try to unlock it a few times, it opens harder and harder), when I'm using apps it continously shows that some .com processess stopped working, and if I try to turn on the bluetooth, the phone instantly freezes and restarts itself.
I tried reinstalling two original ROMs, (version 4.1.2) successfully, but the data on the phone&the system problems remain the same.
I'd like to know how can I make a hard reset, meaning in deleting all the files&settings as it was brand new, just to clear everything, like clearing CMOS. I also think the recovery mode is damaged and I'd like to fix it somehow (if this is possible). The installation process I did for installing the custom ROM from XDA-devs was long and complicated, I had to do a lot of things... and I just want to get the phone fixed and restore to default (or even to fix bugs on this android version) its android, kernel & everything could be ,,reflashed''.
I'm willing to pay if someone helps me fix the problems and it really works. Thank you!
I have a Galaxy S III GT-I9300 I bought in 2014. After three years, I downloaded a custom ROM from xda-developers (android 4.3 is all I remember about it) and installed it successfully. It worked alright until one day when I wanted to sell the phone and a customer wanted to buy it on short notice, and I rushed to delete my files from the phone, but I destroyed the Android... I connected it to my laptop and shift-deleted some system files.... since then, the phone is delaying when trying to unlock (if i lock it now and try to unlock it a few times, it opens harder and harder), when I'm using apps it continously shows that some .com processess stopped working, and if I try to turn on the bluetooth, the phone instantly freezes and restarts itself.
I tried reinstalling two original ROMs, (version 4.1.2) successfully, but the data on the phone&the system problems remain the same.
I'd like to know how can I make a hard reset, meaning in deleting all the files&settings as it was brand new, just to clear everything, like clearing CMOS. I also think the recovery mode is damaged and I'd like to fix it somehow (if this is possible). The installation process I did for installing the custom ROM from XDA-devs was long and complicated, I had to do a lot of things... and I just want to get the phone fixed and restore to default (or even to fix bugs on this android version) its android, kernel & everything could be ,,reflashed''.
I'm willing to pay if someone helps me fix the problems and it really works. Thank you!
Hello, when using (D855) stock rom and stock based rom (Fulmics 8), the phone freezes extremely after the account and apps are installed, I can't take any action, The system is not responding, the home screen is not responding errors, also the phone is unavailable when I put a screen lock it becomes, the password cannot be entered (I don't think it's hardware related as it works very well when using Lineage OS) Used when Nova Launcher is installed (no screen lock), but when you open the notification panel, vibrate the phone, the phone becomes unusable when the settings are in overview. This only happens when using stock and stock-based rom (Fulmics 8). Is there a solution?
Solution
First, boot to recovery and factory reset your phone.
Second, boot back to os, than SET THE DATE TO 2014, and about the date when lg g3 released.
Do not connect the phone to the internet or do not let the phone knows the current time and date.
Third, please root and install a custom rom ASAP, like lineageOs, NOT stock rom based.
What is planned obsolescence? And why it's related to the these problems?
Planned Obsolescence is extremely prevalent in smartphones. Phone companies such as LG, wanted their customers to stop using their phones after warranties, and buy a new phone so they can earn more interest. Therefore they embed software "time bomb" in android phones(usually embed in the stock ROM)These were counting down to the right time after few weeks of warranty, then your phone would start doing "suicide"(causing problems and damaging themselves) resulting lag, freezes, random reboot, bootloops, and even bricked at last.
In the the solution, it intercepted that "time bomb", so it will thinks the phone is still in warranty and stop causing problems to your phone.
This solution can also WORK ON OTHER devices.
Before, my stock rom android 4.4 LG G3 F400S had constant reboot, so I reset it, set date to 2014/9/12 and installed lineage os 18.1 on it. Everything works again, or even better.
Please share this to everyone, I bet this can help many people and most of them don't know it. Thx