Hey all,
I've been having boot-loop problems for almost a month now. The phone just abruptly reboots and goes into a boot loop with just the HTC screen. The problem is fixed temporarily if I remove the battery for a while and then power it back up. If I start having too many things going on, such as several tabs in DolphinHD, downloading several updates, etc. [no gaming at all] it'll do the same thing and just reboot.
I was running Cyanogen 6 [stable] with Kingxkernel #2. I was not overclocked, but did have a few setcpu profiles active. I've tried everything imaginable since they began:
-Tried a different kernel [SNAP], didn't work
-Truned off setcpu, didn't work
Today, I got fed up with everything and then decided to flash a Sense ROM hoping that that would fix everything. I flashed the latest Fresh and after the install, even before I could skip all the set-up stuff, the phone started to reboot again.
As for the Fresh installation, I wiped fully including dalvik and cache all in RA.
I'm about to go crazy. I wan't my fully functioning phone back. Please help
EDIT: Also, I forgot to mention that around the same time the random reboots and bootloops began I got a new battery. It was the one from Best Buy made by Seido. Idk if that would affect anything seeing as I get the same problems with both batteries.
if i was you i would do all the following:
1. titanium backup all your apps...
2. flash clockwork recovery
3. nandroid backup everything
4. wipe /system
5. wipe /data
6. wipe /boot
7. wipe /cache
8. wipe /dalvik
9. install rom of your choice
10. run it for a few hours and push it as hard as you can to cause a reboot
- if it reboots -> plug into computer load up terminal/command prompt do adb logcat (copy and paste where and why it reboots)
- if it doesn't reboot -> start reinstalling your apps one at a time or in batches until you find the culprit (unlikely since most installed apps should only cause a force close rather than a reboot but still worth a shot)
11. post back with your findings... ?
fyi the nightly builds seem more stable than the stable build ever was... at least to me on my evo it was...
Thanks for the reply.
I'm going to try that to see what happens. I'll post asap.
Alright, I flashed Clockwork as you said and wiped/formatted everything you mentioned. After that, I flashed Fresh. Everything went well until it went through it's first routine reboot after flash; I didn't even get to pull down the lockscreen into activation before it randomly rebooted. I did a logcat on the first reboot. This is a little piece of the last part of that:
V/libgps ( 292): DeferredActionThread pthread_cond_wait returned
V/libgps ( 292): PA event: 0x00000040
V/libgps ( 292): PDSM_PA_EVENT_GPS_LOCK 0
D/dalvikvm( 292): GC_FOR_MALLOC freed 618 objects / 115992 bytes in 145ms
I/ActivityThread( 674): Publishing provider com.htc.dcs.provider.utility: com.htc.dcs.service.utility.UtilityProvider
D/dalvikvm( 292): GC_FOR_MALLOC freed 55 objects / 177104 bytes in 74ms
D/dalvikvm( 292): GC_FOR_MALLOC freed 296 objects / 253256 bytes in 86ms
I/ActivityThread( 674): Publishing provider com.htc.sync.provider.weather: com.htc.sync.provider.weather.Provider
D/ConnectivityService( 292): getMobileDataEnabled returning true
I/ActivityThread( 674): Publishing provider com.htc.socialnetwork.snprovider: com.htc.socialnetwork.provider.SocialNetworkProvider
horiveira:tools stgomez91$
Click to expand...
Click to collapse
It rebooted after the second to the last line. This is my first time using logcat, so I don't know too much about what any of that stuff is, except for the last line obviously.
Can anybody tell the reason why I get these problems by looking at that?
Here's a copy of the logcat file: http://www.sendspace.com/file/kt3lj1
I was hoping this would work, but alas...it did not. What do I do now??
Had the same problem.
For me the solution was to reset the GPS and after that all the random reboots stopped.
Dial : ##GPSCLRX#
Enter your MSL Code
let the phone reboot.
I hope this works for you.
How do you get your MSL code?
Gonna try that now, I hope it works...
How did you figure out it was the GPS?
EDIT: Just tried what you suggested. Didn't seem to work: after it rebooted and got past the Fresh screen, it rebooted without me touching it.
jthurs said:
How do you get your MSL code?
Click to expand...
Click to collapse
Use MSL reader, it's in the Market (and free).
Alright, after doing what aj74 mentioned and it not working, I left the battery out for a bit then powered it back on. That was at 3pm. At around 4, it had yet to reboot so I decided to restore all of my apps with Titanium Backup. I have yet to have a random reboot, though I highly doubt it's fixed.
I'm afraid to use my phone :-/
same problem. looks like this is becoming more and more frequent. i have tried unrooted, and a bunch of rooted roms. this is a problem that needs solving fast.
lo' and behold, as I was getting confident and rearranging things on the phone the loops began again.
I guess I feel better
Well, I feel better since it isn't just me. It has been working fine, then I took the phone on my first trip and as soon as I got off the plane on Wednesday, the random restarts started.
I'm guess some type of app update caused it, but god only knows which one. I did a factory reset, the gps reset, restored a nandroid backup from late september, and turned off all synching. Still get the reboot loop.
I seem to be able to make it stop for a little while by putting the phone in the freezer, but I can't believe we would all start having this problem at about the same thing if it was simply a overheating issue.
Update:
I was roaming when all of this happened, and now that I'm home, I haven't been able to get the phone to mess up. This will make it tough to take in for service. It still may be a heating issue, however, since it is not hot where I live, but it was hot where I was visiting.
Update 2:
I have now been able to get the problem to happen in my home area. The battery temp was > 100 F when it happened.
Related
Hi all,
I have Myns warm donut Nand flashed to my Kaiser.
This is the second time this has happened:
Turned phone back on, and it constantly displays android_power: wakeup (0->0) at *a load of numbers that change* (todays date eg 2010-06-07 15:28:29.666103333 UTC)
It does this every couple of seconds or so and keeps going on for forever.
Last time I reformatted my phone, but its a pain to keep losing my stuff and reflashing.
Any ideas anyone?
Thanks,
Take panel 2/3 ?
robuser007 said:
Take panel 2/3 ?
Click to expand...
Click to collapse
Hi, thanks for replying, im not sure if your asking which panel I have or to try a different one.
Ill answer both just to be sure, im on panel 3, i have tried all panels and all start up ok, other then graphics issues they all work.
As for trying a different panel, I dont think that will work as it was ok before, but I will try it if thats what your asking me?
Thanks again
There is a probable power wakeup difference between panels 2 and 3, which can cause wakeup issues even when the display seems perfectly fine.
However I'm not certain this is the problem here, I recall having a similar problem with warm donut which seemed to be related to the way it was powered down and restarted, I often had to do a battery pull before restarting, this stopped happening after an update when I fixed permissions and cleared the dalvik cache, perhaps worth a try?
XCougar said:
Turned phone back on, and it constantly displays android_power: wakeup (0->0) at *a load of numbers that change* (todays date eg 2010-06-07 15:28:29.666103333 UTC)
Click to expand...
Click to collapse
9 times out of 10 this error seems to be something corrupted in the system somewhere.
you can try the 'fix permissions' and 'clear dalvik cache'
you can even try 're-install app_s'
but most likely you will need to re-install the system.
you could re-install system without clearing data.
mnjm9b said:
9 times out of 10 this error seems to be something corrupted in the system somewhere.
you can try the 'fix permissions' and 'clear dalvik cache'
you can even try 're-install app_s'
but most likely you will need to re-install the system.
you could re-install system without clearing data.
Click to expand...
Click to collapse
I tried fix permissions, didnt work.
I was worried that clear dalvik cache would damage so I didnt do that before. This time I tried it, and it started!
Can anyone tell me what this does? Ive looked around and it seems to be something to do with a cache for applications? Is that right?
Thanks guys
Dalvik is the Virtual Machine that Android applications run on, the cache I believe stores application code to speed up execution time.
Clearing the cache will mean that the initial start up time will be longer, but any corrupt data will have been cleared, which is what I suspected was the problem when this happened to me.
XCougar said:
Hi all,
I have Myns warm donut Nand flashed to my Kaiser.
This is the second time this has happened:
Turned phone back on, and it constantly displays android_power: wakeup (0->0) at *a load of numbers that change* (todays date eg 2010-06-07 15:28:29.666103333 UTC)
It does this every couple of seconds or so and keeps going on for forever.
Last time I reformatted my phone, but its a pain to keep losing my stuff and reflashing.
Any ideas anyone?
Thanks,
Click to expand...
Click to collapse
also try kallt_kaffe's newest build (june 8), be sure to read the post at the end you will need to check the "Include ppp.nostart=0, and default clock and battery capacity settings" box
http://forum.xda-developers.com/showthread.php?t=660158
Ok, days of peace are finally over
Today after doing a simple reset of my kaiser (power off then back on)
I have noticed an endless loop in boot and that is the line,
set volume of 256 to 5
init: untracked pid 123 exited
Click to expand...
Click to collapse
The pid number increaments by 3 after every loop and the loop starts with
snd_set_device(1,1,1)
rpc_write(blablablabla)
blablablablabla
Click to expand...
Click to collapse
and the end of the loop is
set volume of 256 to 5
init: untracked pid 123 exited
Whats suddenly worng?
I really dont want to lose my contacts, rest of the apps/tweaks I dont care
dark_prince said:
Ok, days of peace are finally over
Today after doing a simple reset of my kaiser (power off then back on)
I have noticed an endless loop in boot and that is the line,
The pid number increaments by 3 after every loop and the loop starts with
and the end of the loop is
set volume of 256 to 5
init: untracked pid 123 exited
Whats suddenly worng?
I really dont want to lose my contacts, rest of the apps/tweaks I dont care
Click to expand...
Click to collapse
If u synced your phone with a google account there is no problem for contacts because they will pop up again if you reinstall android and you sync that account again.
Anyway, you can restore system as much as u want because when android start it is read only, so this means that no changes are done to it , simply reinstall android and say "no" when menu ask you to clear data.
I tried like this:
1st Try with Clear Dalvik Cache
2nd Try: Only system reinstall and no DATA wipeout
3rd Try: Reinstall like a hard reset
I change my fonts pretty often and what I think is a ttf was encoded wrong and I replaced that :/
pssshttt! I just rebooted my phone a second time (Power off then back on) and again this stupid error popped error popped up :/
One thing is for sure that its related to the font I am using :s
Endless loop
I have had this endless loop twice and both times I had to reinstall via the installer. I don't know if there is a fix so that you don't need to reinstall. It would be really nice if someone with a little insight could maybe find out what is going on.
I haven't been able to understand exactly what I did to make it loop like this.
I just make sure never to reboot and if so I just hope no looping accours.
There is something with the 3rd Party fonts I used, only one of them caused this, rest all of em were fine. I had to reboot my phone dozen times in order to see stability or corruption before releasing mine build
I think its related to some system related, and happens only when I install that specific cursed font lol
I will continue this topic. I'm using newest froyo on kaiser, newest kernel, and I also have an untracked pid allways, when I'm using my kaiser for longer time, or install something and reboot it. I have no idea what to do with that, and I don't want to go back to WM. Please, help
And sorry for my not good english
I have this problem too,but i didnt use custom fonts only installed opera and tried to move it to sd and installed igo which uses the sd to store files.And then it froze and gave me this piece o .... loop Is there a fix for this?
Reinstall, usually the error is caused by fs corruption.
Tried it but the problem still comes back when i try to install something or try to move something to the sd card.
I have figured out what causes this error and so far it occurs only in froyo ports. The init.rc gets corrupted. The bootup process goes into infinite loop in overwriting the init.rc
Best remedy is to CLEAR DALVIK CACHE and REBOOT. (You often lose your contacts and text msgs and google login details so keep a backup)
Its so much nuisance having this init.rc crashing atleast twice in a day and I am pretty much frustrated with WM either way. I am thinking for replacing my phone for a native android
I had this happen to me 3 times today, recovered all 3 times.
Running Liqid's kernel .32 using ATools and a deodexed version of "system froyo".
Fairly "stock" settings in ATools and only added 4 apps to original build.
I also got "low on space" notifications with each of these crashes. Checked memory after recovery and it was back to normal.
I really need to figure out how to make a sig...lol.
dark_prince said:
Its so much nuisance having this init.rc crashing atleast twice in a day and I am pretty much frustrated with WM either way. I am thinking for replacing my phone for a native android
Click to expand...
Click to collapse
Agreed. Almost there.
same thing happened to me
Hi all,
My phone is AT&T tilt.
Kernel : 2.6.25-dirty modified using Atools - Panel 2 type
Android 2.2.1 - Not So Super Froyo RLS 18 updated with latest androidupdate using the kernel menu to update.
all installed on NAND , using p2 for system and p3 for data and auto for swap
My problem and it seems that i am the only one or at least no one has reported it, is that the phone gets stuck 2 or 3 times a day with the backlight dimmed and the screen pixeled with grey and black random pixels.
If anyone tries to call me when this happened, my phone doesn't do anything and they have a normal ringing as if i am not answering. when i restart the phone there would be no log of what happens during the stuck phase. Sometimes it also gets stuck during the restart and i have to clear the Dalvik Cache, and all info , contacts gmail account . everything is gone and i have to resync.
Any help or pointing me to what i am doing wrong is highly appreciated.
Thanks to all in advance
Are you familiar with the Fn + Left Soft Key, wait 5 seconds, then Fn + Rt Soft Key?
Sounds like it's just stuck in VSync, which because the phone is not top of line, Android refreshes the screen faster than the phone can react, so there's a delay script in place that helps fix this, but this stuff still happens due to limited hardware.
Whenever you get the pixel snow, try that combination above too see if that helps. If not the only other thing that can be happening is data corruption, which has been around since Day 1. Try installing system on NAND and data on your SD Card and that should help with your data corruption issues as well.
Also, if you are installed completely on NAND, you could do backups of your /data partition on a daily basis (takes about 1 minute on replimenu). I do mine daily even though I have a fairly stable install. I have been having issues with the ribbon cable lately and the phone will lock in sleep mode and run the battery down a bit. Not sure if this is software or hardware related.
IMHO, if you download anything from the market, back up your /data partition as soon as you can to save all your info and newley downloaded apps or games.
Krazy-Killa said:
Are you familiar with the Fn + Left Soft Key, wait 5 seconds, then Fn + Rt Soft Key?
Sounds like it's just stuck in VSync, which because the phone is not top of line, Android refreshes the screen faster than the phone can react, so there's a delay script in place that helps fix this, but this stuff still happens due to limited hardware.
Whenever you get the pixel snow, try that combination above too see if that helps. If not the only other thing that can be happening is data corruption, which has been around since Day 1. Try installing system on NAND and data on your SD Card and that should help with your data corruption issues as well.
Click to expand...
Click to collapse
thanks a lot , no i am not familiar with this option and i will give it a try as soon as it happens , i also should try the data on SD .
PoXFreak said:
Also, if you are installed completely on NAND, you could do backups of your /data partition on a daily basis (takes about 1 minute on replimenu). I do mine daily even though I have a fairly stable install. I have been having issues with the ribbon cable lately and the phone will lock in sleep mode and run the battery down a bit. Not sure if this is software or hardware related.
IMHO, if you download anything from the market, back up your /data partition as soon as you can to save all your info and newley downloaded apps or games.
Click to expand...
Click to collapse
i tried the backup using the replimenu , but it is not working properly . it a long time , after that i restart the phone and the backup file size would be 0 KB.
that was on the old build that i used , i will try it with this build , thanks a lot
UPDATE: [SOLVED] Looks like the GingerBread 2.3.6 ROM fixed this issue.
When the MicroSD card is scanned at startup (i.e. the card is already inserted when the device starts), the MediaScanner / PackageManager analyses the card and this seems to generate a deadlock within the system_server process (.ServerThread), which results in a soft reboot. I don't know if this happens only when there are Apps2SD files (I didn't test this particular edge-case).
So, quite simply, I just insert the MicroSD card once the device is completely booted
UPDATE: sometimes the reboot occurs in this case too, so the deadlock is not completely unavoidable. However, if I long-press the search button, the system doesn't respond which generates a Force Close popup dialog for "Android System" => if I force-close this process, then the device starts responding again and everything works as normal!
Additional note: the MicroSD is perfectly stable when connected in USB transfer mode.
----------
Stock JQ3 has been rebooting randomly on my Tab (no obvious error message in logcat, disabled overclocking/undervolting, Koxudaxi or Overcome kernels, RFS or EXT4 filesystem)...sometimes I can use the Tab for days without problems, but today it keeps rebooting (with or without any interaction from my part).
UPDATE: confirmed with JQ4 too.
The logcat reveals that the watchdog detected a
system-process deadlock, and forced a full restart of the Android
runtime. Here's what [/data/anr/traces.txt] says for .ServerThread (system_server):
Code:
"android.server.ServerThread" prio=5 tid=10 SUSPENDED
| group="main" sCount=1 dsCount=0 obj=0x4050fc58 self=0x2f34a8
| sysTid=12309 nice=-2 sched=0/0 cgrp=default handle=3093984
at java.util.HashMap$HashIterator.hasNext(HashMap.java:~791)
at java.util.AbstractCollection.toArray(AbstractCollection.java:356)
at com.android.server.PackageManagerService.getInstalledPackages(PackageManagerService.java:2385)
at android.app.ContextImpl$ApplicationPackageManager.getInstalledPackages(ContextImpl.java:2186)
at com.android.server.BackupManagerService.allAgentPackages(BackupManagerService.java:966)
at com.android.server.BackupManagerService.addPackageParticipantsLocked(BackupManagerService.java:874)
at com.android.server.BackupManagerService$1.onReceive(BackupManagerService.java:836)
at android.app.LoadedApk$ReceiverDispatcher$Args.run(LoadedApk.java:709)
at android.os.Handler.handleCallback(Handler.java:587)
at android.os.Handler.dispatchMessage(Handler.java:92)
at android.os.Looper.loop(Looper.java:130)
at com.android.server.ServerThread.run(SystemServer.java:673)
"android.server.ServerThread" prio=5 tid=10 SUSPENDED
| group="main" sCount=1 dsCount=0 obj=0x4050fc58 self=0x2f34a8
| sysTid=12309 nice=-2 sched=0/0 cgrp=default handle=3093984
at java.lang.String.compareTo(String.java:~60)
at java.util.ComparableTimSort.mergeLo(ComparableTimSort.java:650)
at java.util.ComparableTimSort.mergeAt(ComparableTimSort.java:447)
at java.util.ComparableTimSort.mergeCollapse(ComparableTimSort.java:370)
at java.util.ComparableTimSort.sort(ComparableTimSort.java:178)
at java.util.ComparableTimSort.sort(ComparableTimSort.java:142)
at java.util.Arrays.sort(Arrays.java:1974)
at com.android.server.PackageManagerService.getInstalledPackages(PackageManagerService.java:2388)
at android.app.ContextImpl$ApplicationPackageManager.getInstalledPackages(ContextImpl.java:2186)
at com.android.server.BackupManagerService.allAgentPackages(BackupManagerService.java:966)
at com.android.server.BackupManagerService.addPackageParticipantsLocked(BackupManagerService.java:874)
at com.android.server.BackupManagerService$1.onReceive(BackupManagerService.java:836)
at android.app.LoadedApk$ReceiverDispatcher$Args.run(LoadedApk.java:709)
at android.os.Handler.handleCallback(Handler.java:587)
at android.os.Handler.dispatchMessage(Handler.java:92)
at android.os.Looper.loop(Looper.java:130)
at com.android.server.ServerThread.run(SystemServer.java:673)
More information here:
http://www.google.co.uk/search?q=reboot+Sending+signal+WATCHDOG+KILLING+SYSTEM+PROCESS
I got reboot whenever I enable wifi.
Hadn't test anything more than this.
Reverse back to dxjpj asian rom
Yes, I realized Wifi would potentially be the cause of the problem, so I am in "flight" mode with both wifi and cellular off.
This is clearly a "system_server" reboot (i.e. the adb connection via USB to my laptop remains alive), so I can capture the system logs even whilst the system is rebooting. Here's some info I found in a mailing list:
Code:
Runtime restarts are almost always for one of two reasons: either a
component running in the system_server process has crashed outright,
or something has caused the system_server's process primary looper
thread to deadlock. The deadlock case is announced by a line in the
logcat buffer reading something very like this:
04-04 14:06:16.888 885 1089 W Watchdog: *** WATCHDOG KILLING SYSTEM
PROCESS: null
I'm going to talk about the NON-deadlock cases first; they're simpler
to diagnose: just look in the logcat trace for the messages about the
system process crashing. There will be a Dalvik stack trace there to
the point at which the fatal exception was thrown, and you then know
where to go looking for the bug. As always, the event log and the
primary text log contain different information; both are useful for
reviewing the state and activity of the device leading up to a crash.
If the crash *was* due to a deadlock, things get a little interesting.
When the watchdog declares a deadlock and forcibly kills the system
process, it first captures the current stack trace of every
system_server process thread into the usual ANR stack trace file
(/data/anr/traces.txt on most devices). This file is automatically
included in a bugreport -- yet another reason to pull a full bugreport
rather than just logcat.
Look at the timestamp of where the watchdog declared a problem. In
the example line I gave above, it was 04-04 14:06:16.888. That tells
you which set of stack traces you're interested in within the "LAST
ANR" section of the bugreport. Find the system_server stack dumps
that were captured at the time of the watchdog's message. For
example, in the bugreport that my example came from, the "LAST ANR"
section was headed:
------ VM TRACES AT LAST ANR (/data/anr/traces.txt: 2011-04-04 14:06:14) ------
and the file holds *two* sets of system_process stacks. One of them
starts like this:
----- pid 885 at 2011-04-04 14:05:42 -----
Cmd line: system_server
and the second starts like this:
----- pid 885 at 2011-04-04 14:06:12 -----
Cmd line: system_server
Note that the first was taken 30 seconds before the second, and the
second was just a few seconds before the watchdog message about
killing the system process to restart the system. The watchdog takes
a thread snapshot after 30 seconds of the looper being unresponsive,
then another snapshot after a full minute of unresponsiveness; and
it's after that full minute that it declares the deadlock and restarts
everything. You probably want to start with the later thread stacks,
the ones that reflect the state of affairs when the watchdog finally
gave up.
In most Android applications the primary looper thread is called
"main", but this is *not* true of the system_process. The primary
system_process looper thread is titled "android.server.ServerThread".
Find that thread's stack trace that was taken at the time the watchdog
declared the deadlock, and you'll be off and running as far as
diagnosing what has caused that looper thread to be unresponsive for >
60 seconds.
At this point you've got the information you need to figure out what
locks are being contended for, what unapproved long-running operations
might be mistakenly being run on the system process's main looper,
etc. Dalvik's stack dump output is very useful, especially since it
tells you things like which other thread currently holds a lock being
requested.
Finally, so it's not my custom rom that cause random reboots to some users.
The strange thing is that not everyone get this issue, me for example, have not none a reboot since i've flashed it.
Daniel, did you have this problem in pure stock jq3?
Meant without overcome kernel installed.
Anyway, you should have this issue with jq4 too, since there are less differences between both versions.
daniel.weck said:
I'm not sure how to Heimdall-flash the JQ4 PDA tar over the ext4 partition? (since I installed Overcome, which aggressively converted /system and /data from RFS to EXT4 without any user-prompt).
Click to expand...
Click to collapse
Ok, that was simple: I flashed [factory.rfs] from JQ4 using Heimdall without repartition (and with the usual PIT file), and on reboot the Overcome kernel automatically converted to EXT4 once again (a short 2 minutes process, as my /data partition had already been converted before). The APKs are now being Odex'ed (Dalvik cache reset)...waiting...
I hope this will fix the reboot issue. UPDATE: no
af974 said:
Finally, so it's not my custom rom that cause random reboots to some users.
The strange thing is that not everyone get this issue, me for example, have not none a reboot since i've flashed it.
Daniel, did you have this problem in pure stock jq3?
Meant without overcome kernel installed.
Anyway, you should have this issue with jq4 too, since there are less differences between both versions.
Click to expand...
Click to collapse
As soon as I installed stock JQ3, I had a couple of reboots, however the ROM "became" stable rapidly and I enjoyed using the Tab for a number of days without any major issues. All this time, I was using Koxudaxi's build (overclocked, undervolted). Today, I updated some apps using the Market, I launched ezPDF and the system then entered this reboot frenzy! I went into flight mode to eliminate potential wifi/radio issues, I removed the overclocking/undervolting, and finally I switched to the Overcome kernel (just to try something different)...to no avail.
I have now flashed JQ4 [factory.rfs], but the system is rebooting again. Frustrating!!
I'm going through /data/anr/traces.txt again, hoping to find the culprit...
I was running stock froyo for the longest time, almost a year. I had huge problems with random reboots. Typically two-three days with frequent reboots followed by a week or two with few or no reboots.
I related the reboots mostly to two different things.
One was sim related and even though I had a new simcard I eventually had to get a new. I've also read about other tabowners with similar problems so maybe tabs are "simsensitive". With the new simcard, this problem went away.
The other problem was with wifi.
The easiest way to make my tab find my wireless quickly, was to put it into flightmode and back on again immediately. In 30-40 percent of the cases this would cause it to crash and reboot. After the reboot everything was fine again.
A month ago I finally dared to flash and I've been on the latest Overcome for a month now. I've had just a single random reboot in this time.
Just my two cents...
The issue appear indeed in the two versions of the ROM, the jq4 also have this issue and tweaking the build.prop does not change it, af974 I've try you're patch but still the issue remains, what is weird is that I spend the last 10 hours on wifi with no reboot and this morning, boom, reboots... the networks is not the same but still...
SOLVED.
UPDATE: [SOLVED] the reboots stop once the MicroSD card is removed from its slot. I have also tried to remove the SIM card. As soon as the SD card is inserted, the Apps2SD applications are analysed by the Nazca/Media Scanner and from this point onwards the Package Manager sub-system goes crazy. I will restore my apps on the device, and I will format the MicroSD, again... I doubt it is a problem with the Micro-SD hardware itself, more like a driver issue. It seems quite common with mobile phones, all brands concerned.
Nice one Daniel,
let us know how it goes after some test in the meantime i'll point my users to here.
daniel.weck said:
UPDATE: [SOLVED] the reboots stop once the MicroSD card is removed from its slot. I have also tried to remove the SIM card. As soon as the SD card is inserted, the Apps2SD applications are analysed by the Nazca/Media Scanner and from this point onwards the Package Manager sub-system goes crazy. I will restore my apps on the device, and I will format the MicroSD, again... I doubt it is a problem with the Micro-SD hardware itself, more like a driver issue. It seems quite common with mobile phones, all brands concerned.
Click to expand...
Click to collapse
Additional note: the MicroSD is perfectly stable when connected in USB transfer mode.
I made a selective backup of important stuff from [/sdcard/external_sd/] (whilst in USB data transfer mode with my laptop), making sure to copy all the [*.asec] App2SD files from [/sdcard/external_sd/.android-secure/]. Then I formatted the MicroSD card on my laptop, and formatted again from the tablet as it detected a corrupted/damaged card (I suppose the FAT driver on the tablet is picky). I then copied the [*.asec] files back to [/sdcard/external_sd/.android-secure/] (several megabytes which I am happy not to have to download again via the Market), and the Package Manager seems pretty stable so far. Win!
I haven't put the SIM card back in yet, first I am updating my Titanium backup!
Cheers, Dan
When the MicroSD card is scanned at startup (i.e. the card is already inserted when the device starts), the MediaScanner / PackageManager analyses the card and this seems to generate a deadlock within the system_server process (.ServerThread), which results in a soft reboot. I don't know if this happens only when there are Apps2SD files (I didn't test this particular edge-case).
So, quite simply, I just insert the MicroSD card once the device is completely booted
daniel.weck said:
When the MicroSD card is scanned at startup (i.e. the card is already inserted when the device starts), the MediaScanner / PackageManager analyses the card and this seems to generate a deadlock within the system_server process (.ServerThread), which results in a soft reboot. I don't know if this happens only when there are Apps2SD files (I didn't test this particular edge-case).
So, quite simply, I just insert the MicroSD card once the device is completely booted
Click to expand...
Click to collapse
I don't use App2sd so maybe that's why I don't have reboots with Gingerbread.
There are actually people who think that I with my SG Tab am jealous of their ipads. Moahaha!
What I did.....
What I did, when I first read this thread, I removed my SD-Card and formated it adapted to my PC (FAT32).
Next I reincerted it to my Tab. Til now (32 hours) it didn't reboot an single time:
I can check this, because of my Plantronics Discovery 975 BT headset that is permanently connected to the Tab.
Whenever in the past the Tab did a soft reboot (JQ3) it was hard work to get the headset reconnected.
PS: Used wifi for about two hours today. Seems to by stable for now. Will push some apps2sd and so on to see if it takes over rebooting.
Unfortunately I doubt this is the solution, the reboots remain even when I remove my sdcard...
CarpeNoctem said:
Unfortunately I doubt this is the solution, the reboots remain even when I remove my sdcard...
Click to expand...
Click to collapse
UPDATE: sometimes the reboot occurs even when I insert the MicroSD card after boot, so the deadlock is not completely unavoidable. However, if I long-press the search button, the system doesn't respond which generates a Force Close popup dialog for "Android System" => if I force-close this process, then the device starts responding again and everything works as normal!
daniel.weck said:
UPDATE: sometimes the reboot occurs even when I insert the MicroSD card after boot, so the deadlock is not completely unavoidable. However, if I long-press the search button, the system doesn't respond which generates a Force Close popup dialog for "Android System" => if I force-close this process, then the device starts responding again and everything works as normal!
Click to expand...
Click to collapse
Not really satisfying!
CarpeNoctem said:
Unfortunately I doubt this is the solution, the reboots remain even when I remove my sdcard...
Click to expand...
Click to collapse
Yes, same with me. Really annoying.
And by the way: android browser task often crashes, when trying to open an additional tab.
Oh damn, i really would like to have too this annoying bug.
In % , this happens in what situations? Browsing, wifi, any addictional info please.
Could someone with this bug post a logcat? Dowload alogcat from market, enable to view only errors and export the log, i don't have any reboots but my log show many errors regarding mtp, keyboard and sensor.
This will be a long post to explain my problem and I hope somebody could enlighten me on what's happening and if it's fixable
Sound Problem
Bought an used T-Mobile S4 (SGH-M919), came with stock 4.3 (MK2), not rooted, not KNOX warranty voided, everything working perfectly including sound, 2 days of constant use, then I wanted to upgrade to 4.4.4 (NK2), I tried through system update on Android and it only said "Failed to register" or something similar, however with Kies3 I was able to upgrade, then the nightmare started.
Being a stock firmware I thought, what could go wrong, update went smoothly, everything was working but after 10 minutes and here comes the important part, the SOUND GETS STUCK/DOESN'T RESUME/DIES AFTER THE SYSTEM GOES TO SLEEP, it always happens when I leave the screen turn off for like 5-10 minutes, the longer it stays off, less chances sound returns, not through ear piece, speaker or headphones, weird part it's that if I turn the phone off and on it works normally again until sleep, everything works normally, except for the part that if the screen goes off, hell begins, the longer it stays off, less chances sound resumes, and I say that because sometimes sound resumes but after like 5-15 seconds of waking, AND IT REPRODUCES EVERY SOUND IT SHOULD HAVE DONE WHEN IT WENT AWAKE (like button presses, volume change, sound systems, etc), like if something was stuck or in large queue, I can almost say it's 100% something related to software and not hardware since it reproduces the animation sound at the boot every time.
After the sound dies, weird stuff happens, Youtube videos get reproduced at like 0.5x speed, trying to play music with the default player says "Not supported" (varying mp3's from 128 to 320kbps), sometimes if I reboot from Android it gets stuck in a restart loop, not always, sound only seems to return again when it's restarted through shutdown/manually (that doesn't seem to happen with custom ROMs), sometimes Android gets weird, like laggy, no background on the home screen, stuck and with only the shutdown menu working, not even volume bar showing up or very laggy (this was something very rare in custom ROMs or it didn't happen at all).
I had to void the KNOX warranty to install a custom recovery (TWRP) and flash custom roms, I already tried stock 4.4.4 roms debloated/deodexed/rooted and even a 5.0.1 rom, tried 2 different kernels + stock, different modems varying from MK2 to NK2 again (flashed like 5 times each one), hell even I tried to flash the LTE modem (NON-HLOS.bin) from MK2, however I didn't get any sound (WiFi was working, weird) since I read that it has to match the bootloader version.
At this moment I'm downloading a 4.3 custom ROM to do another test and probably the last one, I'm running out of options.
Little Facts:
-Already went to complete stock through Kies3 and tried flashing the full firmware with Odin too.
-Volume bar changes normally, I really assured it wasn't muted in any way.
-I f*ckd up IMEI, too much wipes, kernel switches, rom flashing, I did an EFS backup just to find it was at 0 already, however problem started way before that, one problem at the time.
-Light/RGB sensor doesn't work, headphone jack do (I even dissassembled and reassembled without headphone jack to test, didn't work).
-Tried plugin headphones and removing them multiple times.
-Tried with and without a SD card/SIM/WiFi.
-No warranty.
Sorry for the long post, I can create a thread if the mods prefer.
I think I remember seeing something like this and I'm not sure on this but I think it was a third party app causing it. Have you factory reset and installed no apps to see if it still happened, or reboot into safe mode? If you have, can you upload bootloader and modem info using this app https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo when you say you flashed the LTE modem and got no sound, that shouldn't happen if you did indeed flash the matching LTE modem. Could be firmwares never got flashed correctly. Could also be why your imei is 0
I did multiple factory resets, and when I flashed the LTE modem I didn't get sound because the LTE modem was MK2 (just trying stuff) and bootloader NK2, however I reflashed the full stock firmware, I'm currently at NK2 modem, LTE and bootloader.
The only thing I haven't done is reboot in safe mode, will try later and post results.
Edit:
About the IMEI, I'm pretty sure that when I made the EFS backup with TWRP it wasn't 0, since I made it because I was going to try stuff that could go wrong and I wanted a backup, I still have the full system backup with EFS partition included, however, not even restoring the backup bring it back.
New info
-Safe-mode didn't work
-Did multiple full wipes and back to stock through Kies3/Odin, nothing
Trying to find more info found this through ' adb logcat *:E ' (Stock ROM, NK2, 4.4.4)
Code:
E/AudioStreamOutALSA( 300): Invalid argument! It could be standby to recover
E/ACDB-LOADER( 300): Error: ACDB AudProc vol returned = -8
E/alsa_pcm( 300): cannot prepare channel: errno =-22
If the sound was lost, as soon as I click the screen it produces those errors like 100 times, even if it's on vibration only.
Some other errors from *#7353# testing (SPEAKER TEST)
Code:
E/AudioSessionOutALSA( 300): PCM Prepare failed - playback err = 0
E/AudioSessionOutALSA( 300): Failed to open LPA/Tunnel Session
E/AudioTrack( 300): Could not get audio output for stream type 3
E/AudioSink( 300): Unable to create audio track
E/TunnelPlayer( 300): Opening a routing session failed
E/MediaPlayer( 8834): error (1, -19)
E/MediaPlayer( 8834): error (-19, 0)
E/MediaPlayer( 8834): Should have subtitle controller already set
E/MediaPlayer( 8834): Error (1,-19)
E/MediaPlayer( 8834): Error (-19,0)
And from MELODY TEST
Code:
E/MediaPlayer( 8834): stop called in state 0
E/MediaPlayer( 8834): error (-38, 0)
E/MediaPlayerService( 300): WFD client is not created
E/alsa_pcm( 300): cannot prepare channel: errno =-22
E/AudioStreamOutALSA( 300): Invalid argument! It could be standby to recover
E/alsa_pcm( 300): cannot prepare channel: errno =-22
E/AudioStreamOutALSA( 300): Invalid argument! It could be standby to recover
E/alsa_pcm( 300): cannot prepare channel: errno =-22
E/AudioStreamOutALSA( 300): Invalid argument! It could be standby to recover
E/alsa_pcm( 300): cannot prepare channel: errno =-22
And those 2 lines repeats themselves like 100 times
It could be an hardware problem, sadly, I hate that it works, but it stops working for no reason.
And found multiple threads about the same issue across different models:
http://forum.xda-developers.com/showthread.php?t=2333222
http://forum.xda-developers.com/showthread.php?t=2386070
http://forum.xda-developers.com/showthread.php?t=2333222
http://forum.xda-developers.com/showthread.php?t=2718326
http://forum.xda-developers.com/showthread.php?t=2612167&page=6 Post #51
My problem may be similar to yours. I have a completely stock S4. I have done no rooting to it. About a month ago I noticed the same sound problem you have. I noticed my phone would lose sound ability the longer it was on. Similar problems with YouTube playback slow, and I can't play media files like music or video (I get process errors).
I have factory reset a few times and the problems return. I'm getting tired of having to reset my phone every 1/2 hour. I've missed phone calls and alarms I've set.
I had this problem on an ATT S4. It was a hardware issue. Phone was under warranty and fixed by Samsung.
Sent from my SGH-M919 using Tapatalk
I guess I have to do a insurance claim. My current phone is my 1st replacement of my original GS4. The first phone was insurance replaced because it was passed the factory warranty and it stopped charging any battery put into it. Now my current one has started hanging at the T-mobile logo when resetting and just plain random resets.
My GS4 was reliable for a while. Maybe time for a Nexus 6.
I literally did the same thing last week with a refurbished phone from T-Mobile. Buyer be ware
Sent from my SGH-M919 using XDA Free mobile app