Hey Guys,
First the relevant data
Galaxy S3 LTE I9305
ROM: Carbon Rom KK 4.4 (CARBON-KK-NIGHTLY-20140701-1234-i9305.zip)
Kernel: Standard Carbon Kernel
Problem Description:
The phone reboots itself sporadic and then gets stuck at bootlogo. It is completly sporadic so sometimes it is when i am using it heavyly sometimes just when i end a call or want to do something else not intensive.
The only solution then is to go to recovery, wipe cache and dalvik cache and the reboot. The phone the rebuilds the dalvik cache and crashes a few times while the process.
But there are some more strange things going on:
- Battery
The battery is almost fully charged, when the phone crashes and reboots a few times while rebuilding dalvik cache the battery show up empty suddenly! Phones turns off and only turns on when plugged to charger and then shows battery level 0% when running again. The charging process begins normally from there.
Sometimes the battery shows empty as described above but when i restart the phone again and rebuild dalvik cache it's on its old state (almost full).
- Kamera
When i take pictures, sometimes the camera shows some red stripes all over the stored picture or even in focus mode. Then the screen starts flickering and phone crashes as describes above.
- PIN
When crashed and running again after some tries to build dalvik cache, sometimes i enter PIN to unlock sim card and nothing happens. Then the screen starts flickering again and it crashes. Procedure start again then.
- Charger
When the phone crashes and i plug it to the charger before rebuilding dalvik cache, it runs through without any errors like it should.
What i tried so far:
- Other ROM (AOKP, CM, other Carbon Rom builds)
- wiped everything (really everything on internal storage) and clean install
- reflash after crash (dirty)
- reflash after crash (wipe)
- leave phone with just a few apps after clean install (thought it could be one of my apps)
- recording a logcat (aLocRec and logcat reader) but the problem here is as the logcat is stored in memory it's not accessible after crash (reboot).
What i want to try next:
- try getting a logcat via adb and hope it crashes while logging
- other kernel (don't want to try this, would be last option).
Does anyone have an idea?
Thanks!
Dark Smile
One idea may be a bad battery which may cause inconsistent power supply and all kind of strange errors. Especially because, as you write, with charger = stable voltage source things look good.
Cheers,
Axel
Thanks for the tip s3axel, i'll buy a new one when i get off work and try it.
I just ordered a original battery from here:
http://www.trade-shop-online.de/ori...galaxy_i9305_galaxy_i9305-p-29153.html?ref=20
I'll give feedback when arrived and tested.
Good luck
Unbelievable, it was the battery! No problems with the new battery. Thanks for your advice s3axel
Sent from my GT-I9305 using XDA Free mobile app
I was experiencing exactly EVERY one of those issues besides the battery jumping to zero. It would even crash when opening messaging, chrome, contacts, literally everything crashed it.
I tried everything that you tried, and was about to logcat from my computer too lol.
And without looking it up I had the idea, maybe its the battery and it just cant support the changes in power needs, maybe I should buy a new battery!
Thought, nahh... ill try some more things first. Then boom! Reading this post I felt like I wrote it!
This thread just blew my mind!!!
Related
I have had some recent problems with my Nexus and I think its seriously broke. I am hoping someone can help as I couldn't bare sending this back off to HTC or Google for repair because I'm living now at Saudi Arabia!
I.m using CM 7.1.0
my phone is nexus one with SLCD and never fall down I just bought it new from Amazon about 5 months ago
Main Problem
The camera is unresponsive.
Whenever I click on the camera app the live wallpaper in the background freezes, then the phone turns black and when I press the backup or home button the below error message comes up:
Sorry
Activity camera (in application Camera) is not responding
Force Close / Wait
Other problems (maybe related...)
-My camera flash will turn on randomly,
-My phone will turn off when i make calls the screen will go all black and not let me do anything unless i take off the battery
-The phone has been running with too much hot when this problem has started.
-Also, I have had what seems excessive batter useage i.e. fully charged overnight and unplugged at 7am, battery dead by 10 am.
Recent efforts
I have re-flashed the CM and did a data and cash wipe and tried a new cm build
I have factory reset the phone 3 times
I have removed the memory card
I have swapped and used a friends memory card
, but nothing!
so please help me ... if its a hardware problem please advice a site for me to buy new parts
First thing I would do is a full wipe of the phone. This includes manually wiping the /system partition and then performing a Factory Reset/Data Wipe. From there, reinstall CM and gapps and see if you problem is still there.
If you need to back up apps and app data, you can use a program like Titanium Backup.
Also, what is your radio/baseband version? You can find it in Settings -> About Phone.
I am getting the same problem.
I have a alogcat log output if it is helpful in working out what is causing this / fixing it
You can try and see if the logcat has any info that can help with it, but typically, they don't put out too much information that would help in diagnosing it. I would still recommend wiping the phone.
Have completed a full wipe as described above with no success.
Baseband version: 32.41.00.32U_5.08.00.04
andrewb_nz said:
Have completed a full wipe as described above with no success.
Baseband version: 32.41.00.32U_5.08.00.04
Click to expand...
Click to collapse
Is this after restoring your apps? Because a clean install with gapps typically yields a 1-2% battery drain (or less) per hour.
Did your camera just stopped working one day?
Sent from my Nexus One using xda premium
sorry I just get back from work trip
I wiped /system also and flashed the radio again which is 5.08.00.04
but no success
it just happened like that, my nexus one never fall down
What do you have your clock set to? My camera would FC also but its cause it was overclocked to high, i put it to MHz and now it runs smooth
I tried overclocked and underclocked but nothing
Idont know what happened, but everything seems that has been fixed by itself
No more battery and heat issues
No more drop calls
No more black screen
But the camera and flashlight problem still not fixed
Sent from my Nexus S using Tapatalk
Camera not working on Android 2.3.6
About 2-3 weeks ago the Android 2.3.6 update came over the air.
I have had a couple issues:
1. Camera does not work at all, no picture taking, no gallery
When I try to take a picture an error message pops up with 3 buttons:
Sorry!
Activity Camera (in application Camera) is not responding.
[Force Close] [ Wait ] [ Report ]
2. I just downloaded TripIt and it will not "stick" to the home screen when I try dragging it there.
Anybody with a solution?
I think you've flashed a wrong kernel. Non-working camera and fast battery drainage are common in kernel problem.
Hi,
My HTC one is running the android revolution rom for a couple months now, however recently I notice that at night my phone get super hot and the battery drains quick.
Has anyone else ran into this problem?
poisonsushi319 said:
Hi,
My HTC one is running the android revolution rom for a couple months now, however recently I notice that at night my phone get super hot and the battery drains quick.
Has anyone else ran into this problem?
Click to expand...
Click to collapse
weird you might want to flash the newest revolution rom, my guess is that there is an app running in the background. game perhaps? i would just recommend a fresh install with 4.2.2 =D
Sounds like you have some naughty apps or system processes misbehaving, you need to find out which ones they are, try installing the watchdog app and set it to monitor system processes as well.
Also a good one is wakelock detector.
John.
Verify the rom your flashings MD5 checksum.
To eliminate any apps that may be causing your phone to get hot, do the following.
Go to your internal memory and clean up anything that you do not need, so pics, music and videos i would keep, or copy them off, delete everything else that you don't need. *Make sure you leave a working ROM to flash on your memory* (I personally do a good clean up every third flash, so i delete every folder and just leave the ones i mentioned above and a flashable rom of course)
Reboot to recovery and perform a full wipe (Data, cache and dalvic cache)
Install your rom.
Don't install any extras at all
*Do not restore anything whatsoever*, no advanced restore and no titanium
Allow the phone to boot and don't install any apps, just sign into your Gmail and keep it like that for a day.
No overclocking / underclocking no undervolting / overvolting of any kind, keep it on stock kernel.
Turn off unwanted wireless connectivity when not in use, ie: GPS, NFC, WiFi, Mobile Data.
If your phone gets hot after that then I would say that it could be a problem with your handset.
When it's charging or your running an app the phone will get hot, thats a given but if you follow what i've written then your phone shouldn't get too hot.
Good luck m8
Use this app and see which apps getting energy
See your battery life result
https://play.google.com/store/apps/details?id=com.gsamlabs.bbm&hl=en
Sent from my GT-I9300 using xda premium
My theory is that it's bad install. It happened to me on few occasions.
Hi all,
I have a 32GB TP that has been doing fine (save for some battery issues) up until recently.
Now, at random, it flashes a full screen of blue lines. This lasts for about 1 - 2 seconds. Anything running appears to freeze while it happens, and if audio is playing, the TP will just BOOOOOOOOP while the blue lines appear.
Some times it will go an hour. Other times it does it every 20 seconds or so. Even just scrolling through the apps list. Does it both while plugged in and not.
I was running CM9 and thought that maybe it was a corrupt ROM or something. So, I did a full wipe (system, caches, etc) and installed CM10.x/4.2.2. Still doing it.
Anybody have ANY idea what might be causing this? Im guessing its a hardware issue now. Ive seen similar issue mentioned but never with any resolution.
Except for this issue and the occasional not wanting to turn on, the TP has been great. So...Im hoping its something fixable.
I'm not OC'd. Running pjsports CM build with non-system apps restored with TBU. Nothing funky (performance enhancing, monitoring, tweaking, av apps) installed.
Thanks.
Ahhk said:
Hi all,
I have a 32GB TP that has been doing fine (save for some battery issues) up until recently.
Now, at random, it flashes a full screen of blue lines. This lasts for about 1 - 2 seconds. Anything running appears to freeze while it happens, and if audio is playing, the TP will just BOOOOOOOOP while the blue lines appear.
Some times it will go an hour. Other times it does it every 20 seconds or so. Even just scrolling through the apps list. Does it both while plugged in and not.
I was running CM9 and thought that maybe it was a corrupt ROM or something. So, I did a full wipe (system, caches, etc) and installed CM10.x/4.2.2. Still doing it.
Anybody have ANY idea what might be causing this? Im guessing its a hardware issue now. Ive seen similar issue mentioned but never with any resolution.
Except for this issue and the occasional not wanting to turn on, the TP has been great. So...Im hoping its something fixable.
I'm not OC'd. Running pjsports CM build with non-system apps restored with TBU. Nothing funky (performance enhancing, monitoring, tweaking, av apps) installed.
Thanks.
Click to expand...
Click to collapse
I got this whenever I tried to change to a rom that was not supported with the current partition layout or needing an SE version or a data/media on a non data/media version....
I held home and power at same time till it re-booted and went into CWM recovery and re-flashed the original rom. (I bet you could use your NANDroid as well)
SteveoSupremo said:
I got this whenever I tried to change to a rom that was not supported with the current partition layout or needing an SE version or a data/media on a non data/media version....
I held home and power at same time till it re-booted and went into CWM recovery and re-flashed the original rom. (I bet you could use your NANDroid as well)
Click to expand...
Click to collapse
Thanks, but as I said, this was originally happening with the lastest stable build of CM9 (Sept '12?) - which was fine for about a year. So, since I had to reinstall to try and eliminate the issue, I went with the latest build 4.2.2 ROM that DIDNT require the new partition layout.
Since it seems Cyan has halted release of cyan 11 nightlies for the Atrix HD (indicative of what, I'm not sure), I figure it's worth solving this personal issue now; since it will most likely require another factory reset and I'd rather do it now.
Since day one of using custom ROMs, I've had the issue of my phone randomly crashing. Despite previously using only stable cyan releases, making sure to do clean resets (factory, dalvik, formatting system partitions,etc), letting the phone "stabilize" after installing (no clue what this means, but people seem to suggest just letting the phone sit about 10 min after flashing a new ROM, claiming a more stable experience), and even flashing a new kernel, I still see the same issue.
At this point, I've pretty much accepted that more likely than not, I'll have my phone randomly freeze and reset in my hands during basic use, calls, texting, internet use, listening to music, etc. Though clearing the Dalvik cache seems to quell the problem, it soon returns to the familiar behavior a day or two later. Any other basic solutions I might be overlooking? Suggestions, even obvious, very welcome.
CM11 switched to unified builds for the Moto 8960 family . http://www.cmxlog.com/11/moto_msm8960/
You can safely download a zip and dirty flash it over your current CM11 installation. At least that's what I did and I'm having possibly the smoothest experience so far on this phone/CM combo running Sat March 01 nightly.
About your crashes, do you get a phone freeze with signal loss before restarts? Do you always get a restart when the phone crashes?
Did you try enabling 2G only for a while? Do you crash while on WiFi?
You could also try another ROM such as Validus. I find the 4.3 release to be quite stable.
Thank you for the link to the new unified build. I've been busy with approaching midterm that I'd only heard of the new builds but didn't look into it personally.
As for the freezing. It's always been the same behavior: screen and all function buttons suddenly becoming unresponsive with no warning or change in signal (regardless of wifi or data use) remaining frozen for 10 to 30 sec, before returning to the unlocked bootload warning screen and the normal cyan reboot animation and normal lock screen after.
Everytime is has froze it will restart (i suspected a memory issue at one point, but after watching the memory usage long enough to see it randomly freeze but no change in mem, I doubt that it's directly the issue). I have not tried switching to 2g, so it would be worth a try. It will freeze regardless of whether wifi is off or on.
The only real "pattern" I could argue seeing is that it freezes most often during skype calls, while playing music (pandora and play music), and internet using browser; though it might only be because I'm actually paying attention to the phone while it is doing these tasks, I'm sure that it's probably freezing and resetting in my pocket thoughout the day. It will also randomly reset while looking through settings or non-data dependent tasks. Ironically, I've never had it reset on me while I was watching a youtube video. Go figure.
audit13 said:
You could also try another ROM such as Validus. I find the 4.3 release to be quite stable.
Click to expand...
Click to collapse
Any ROM, stable, nightly, cyan or other, with still see it start randomly freezing and rebooting an hour to a day after flashing.
-update*
After having switched to 2g signal instead of LTE, I haven't seen anymore randomly rebooting. I'm not sure if this was the issue but it's already been a day which is longest I've seen it remain stable.
1 Week later, back to the same behavior as before. Seems I might just screwed for having a stable modded phone.
Hi,
first of all sorry for my bad english and screenshots with german text .
The situation:
I have a total of two Tab S2 (T-813). The first is 4 years old, the second is less than 2 years old. The newer is now causing problems.
The reboots occur:
- When using the tablet. Definitely with a high load, but also sometimes with only light loads
- When it is charging
- completely random
Edit1: reboots are not related to the battery percentage
Edit2: never experienced a reboot while in TWRP.
I didn't really find anyone with the same problem on the Internet. It is not a boot loop. Sometimes you can use the tablet for hours/ days. Then again not at all, because it starts again after a minute. To narrow down the problem, I formatted both tablets and installed the same lineage version and firmware. Since it restarts, log files are unusable, right?
Is there any way to narrow down the error?
I suspect overheating, but I would like to know if I have any way to isolate the fault exactly. Maybe there is also another (hardware) forum, which can help better in this case, then I would also be grateful for a tip.
I would have no problem opening the tablet. I've already done this with my smartphones.
Thx for your time.
Solution:
It is an overheating problem if you have exactly the same problems as I had.
You can test it simply like this: fill a plastic bag with cold water and some icecubes. Use it like a pillow for your tablet so it can rest on the bag while you use it. I had no problems at all while doing this.
I send it to Samsung and they repaired it.
It's just as new now.
I actually have the same problem, just only when its at 15 or less battery
Hi.
Well, it sounds for me like a different problem, cause it's battery related. My battery is fine and I have reboots not related to battery status.
Have you tried anything (factory reset, newest lineage and firmware,...)?
Hi,
same here. A SM-T813 running LineageOS that started with random freezes and reboots about a week ago. Sometimes I can use it for about half an hour without problems, next time it reboots while rebooting ...
Seems to be completly random, only thing I noticed that it never reboots while in TWRP.
Cleared and reinstalled LineageOS, but didn't change anything. First time rebooted while still in the setup wizard, next time I could finish the wizard and install serveral apps before the next reboot.
Maybe a problem with the memory?
Yes, that is exactly the same.
I never experienced a reboot in TWRP. No problem with reinstalling lineage.
But while reinstalling Android, it reboots while configuring and while reinstalling apps.
The last days I could watch Amazon prime every evening. Now it reboots after a minute even without using it. I shut it off and hope it will work this evening again.
I have the same issue, sent it in for repair asked to flip battery and swap mainboard. Got it back. Worked a few days, then had random reboots again. I am 100% sure it is a battery issue, and when you get under a specific voltage, maybe when it gets under 30% or so, the chance for reboots rise dramatically, with high cpu or flash memory usage. It happens more often when doing a update in Google Play store for example. So totally have no idea, if Samsung flipped the battery or not, but this was my last Samsung product ever. I would assume there is an issue with too much current drain and then it reboots, and the battery used in them are not designed for the units properly.
same to me. i was on stock rom. never root or anything. and got random reboots most of them when i open google play or google chrome. now im on lineage and same. also i notice that the tablet didnt reboot until i install gapps. and the tablet never reboot on recovery or TWSR. reboots on high or low battery. and if it was overheating maybe the tablet will reboot on recovery. dont know its weird. i will try lineage with out gapps to see what happend.
just testing lineage without gapps no reboot. run browser and netflix with no problems. then i install youtube from aptoid store. and reboot start again. o unistall youtube and no reboot for now.
Same here. I have random reboots but also wifi disconnections (unable to reconnect until i reboot the device)...
Not evident cause...
Someone got a solution for this?
Have the same problem on my T813
You can find the solution for the problem I described at the end of the first post.