Develop Bugs

[Q] Random reboots and frustrating boot loops

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.

[SOLVED in 2.3.6] Gingerbread 2.3.5 JQ3/JQ4 (soft) reboot issues (random + MicroSD)

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.

static phone calls and kernels not working

I hope someone can help me figure out what the problem is with my phone because I am out of ideas. I've been using the peoples ROM with stock kernel and occasionally my phone calls would be very staticy , but toggling speaker phone removed that issue. Now any ROM I use that doesn't use the stock kernel causes that same issue except I can't toggle it off anymore. Also many kernels I use besides stock causes apps to force close and system process to force close, unless the kernel came with the ROM. I've tried wiping my internal storage, formatting everything, installing any kernel I can find, fixing permissions, clear long cache 100's of times, flashing kernelcleaner, and I really don't know what to do next. Any advice? I really don't want to be stuck on 4.1.2.

Can I get any help on this?
Sent from my SPH-L710 using xda app-developers app

dokosatchii said:
Can I get any help on this?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Maybe try a clean install. You could always take a logcat to see if it is phone related. May also be a defective earpiece

lvpre said:
Maybe try a clean install. You could always take a logcat to see if it is phone related. May also be a defective earpiece
Click to expand...
Click to collapse
Do you mean wipe internal/system/factory reset and the install a ROM? I've done that but no improvements. I'll try a logcat but have no idea how to decipher it.
Normally I'd agree with you about it being a faulty earpiece, but the same issue pops up if I connect headphones or bluetooth headset during a phone call, still the same static noise. Could it cause all these issues?

I created a logcat but not sure what I should be looking for. I ran a logcat while making a phone call, does someone have a similar logcat so I can compare against? If it turns out the same I guess its just a hardware problem and that I should replace the earpiece? Any advice would be great.

dokosatchii said:
I created a logcat but not sure what I should be looking for. I ran a logcat while making a phone call, does someone have a similar logcat so I can compare against? If it turns out the same I guess its just a hardware problem and that I should replace the earpiece? Any advice would be great.
Click to expand...
Click to collapse
What rom are you using? Sometimes a logcat with have an /e or /f if a file or service is causing the issue. Start the logcat then try to make a call. If you are still having issues, use odin, unified toolkit, or something similar and make your phone completely stock again. Since you did a full wipe (system, data, caches, factory reset), maybe the rom you flashed has a custom kernel that has voltage settings not compatible with your phone. But try the stock rooted rom and then go back to completely unrooted, out-of-the-box stock if that doesn't work.

lvpre said:
What rom are you using? Sometimes a logcat with have an /e or /f if a file or service is causing the issue. Start the logcat then try to make a call. If you are still having issues, use odin, unified toolkit, or something similar and make your phone completely stock again. Since you did a full wipe (system, data, caches, factory reset), maybe the rom you flashed has a custom kernel that has voltage settings not compatible with your phone. But try the stock rooted rom and then go back to completely unrooted, out-of-the-box stock if that doesn't work.
Click to expand...
Click to collapse
I reset the phone to stock using odin, and I still get the issue(sometimes), but it goes away when I toggle speaker phone once. I am starting to think either the speaker is bad or my phone is just faulty.
I have tried every rom possible, MIUI, Paranoid Android, Slimbean, the only one that works is the rom that uses stock kernel like FreeGS3 and The Peoples Rom and even then I still have to toggle the speaker phone to get it working.(not all the time)
ASIDE: When I flash other kernels to test whether it'll work just as ktoonz, etc. the phone just goes through a bootloop or process start to fail, could be related?
EDIT: I created a logcat while placing a phone call while on stock and while using slimbean and I see the following discrepancies:
Stock: 4.1.2
--------------------------------------------------------------------------------------------
[ 08-21 09:50:38.359 170: 170 D/AudioHardwareALSA ]
setParameters() realcall=on
[ 08-21 09:50:38.359 170: 170 D/AudioHardwareALSA ]
>>>> realcall start!!!!
[ 08-21 09:50:38.369 170:13648 V/AudioPolicyManagerBase ]
setPhoneState() state 2
[ 08-21 09:50:38.369 170:13648 V/AudioPolicyManagerBase ]
Entering call in setPhoneState()
[ 08-21 09:50:38.369 170:13648 E/AudioPolicyManagerBase ]
unknown stream type
[ 08-21 09:50:38.369 170:13648 V/AudioPolicyManagerBase ]
getNewDevice() selected device 1
Slimbean ROM 4.3/4.2.2
--------------------------------------------------------------------------------------------
[ 08-21 10:07:52.803 343: 817 D/AudioHardwareInterface ]
setMode(IN_CALL)
[ 08-21 10:07:52.803 343: 817 E/AudioPolicyManagerALSA ]
unknown stream type
[ 08-21 10:07:52.803 343: 817 E/AudioPolicyManagerALSA ]
unknown stream type
[ 08-21 10:07:52.803 343: 817 E/AudioPolicyManagerALSA ]
unknown stream type
[ 08-21 10:07:52.803 343: 817 E/AudioPolicyManagerALSA ]
unknown stream type
Any idea's on how to get this AudioPolicyManager to run properly?
EDIT: After endless searching, guidance and effort, I am chalking this up to hardware problems. If anyone is experiencing this issue, I recommended returning the phone to sprint and getting it replaced.

Internal SDcard Busted, Can't Format or Write (Forever Locked as Read-only)

HI,
I used to be more active in this forum, but honestly nowadays I can't found any reason to since everything has been smooth sailing for me without any problems—until this day, at least. Somehow I got my internal sdcard busted, it was pretty spontaneous, all I can recall is suddenly the system starts to reboot itself. Nothing much, I thought to myself, problem is the system keeps rebooting, it doesn't even last a minute. Naturally when faced with this problem one would do the usual procedure, namely completely format the thing to stock the rule out any possibility on the user side of things, but then this is the part when it starts to get interesting...
The thing refused to be formatted, seriously, it baffles me at first but it does
Things I've tried:
Fastboot, it hangs at writing system, whether I was doing it line per line manually or via the flash_all.sh script, I haven't tried the toolkit but I think it's safe to assume that It'll do the same thing. Even if it does go on (which it did, once) it doesn't do any sort of changes whatsoever to the system.
ADB, nope, not this one either. And since the system reboots faster before I can do anything worthwhile it's pretty much out of the question.
Recovery, multiple times I've tried nuking everything via CWM, nada. I've tried TWRP too, I have to boot it from fastboot since it apparently doesn't allow me to flash a new recovery either, it reverts back to CWM every time. Also tried to flash a different ROM (CM), that didn't work, it spits out an error message regarding some failure in changing metadata, thought it was a corrupted file or something, so I re-downloaded it, that doesn't work. Still convinced that it's corrupted I tried 4 different version of it without any luck. Even the one I had successfully flashed before. Interestingly enough, flashing the exact same ROM I'm currently using (ShinyROM) works, not that it seems to do anything.
Built-in data format from settings, now this doesn't work because I assume that it needs the stock recovery to work, which I couldn't flash because it wouldn't let me—in a sense that it flashes just fine on the command line—fastboot doesn't show up any error or anything—but it defaults back to CWM as soon as I reboot it.
Manually via terminal emulator/file manager, still nothing, curiously enough, Terminal Emulator indicates that the whole system is read-only (I tried making a file with it, it shows that exact message).
Grit my teeth, clench my fist and screams out every curse word that I know of, this somewhat reduced my stress levels, but ultimately yields nothing.
Which led to be believe that either my phone was either a) Haunted or b) Has a serious hardware problem, I'm leaning on the latter. A few quick lookup with my limited amount of Google-fu and I've found several threads that described the exact same issue:
http://forums.androidcentral.com/go...-factory-settings-no-matter-method-i-try.html
http://forums.androidcentral.com/go...eset-nexus-7-2102-using-multiple-methods.html
Both of which hints at it being a hardware problem. Which was my biggest fear since I can't really revert the phone back to stock now can I? Locking the bootloader doesn't seem to work either (the 'fastboot oem lock' command works just fine but just like every single thing I've tried, reverts back to my previous setup as soon as I did a reboot), plus this means I have to send it back with my private data still on it, and I can't say I trust Samsung, Google (or anyone really) with my private data. Not to mention some of the stories I've heard/read about Samsung and their policy regarding rooted devices (much less ones with an unlocked bootloader).
In case it helps, here's a few more details:
What state the device is currently in:
It boots up just fine, but nor for long, apps starts to hang and ends up with a cold reboot (sorry if it's not the right jargon, but it starts right from the Google screen).
Everything that doesn't require you to access the filesystem works fine.
Apps doesn't seem to be able to write anything to the filesystem, I tried backing it up with Titanium Backup, much to my surprise the backup files weren't made (although TiBu seems to indicate that they were).
What the device is running:
Variant: Maguro 16GB
ROM: ShinyROM 4.4.2
Kernel: franco.Kernel r395
Baseband: XXLJ1
Bootloader: PRIMED04
Also I don't know if this will affect things but for the record I'm running the latest Ubuntu and Debian.
So this post is pretty much a shot in the dark, since I think I know what I'm dealing with already; if anyone had this problem before in the past, or has it now and somehow managed to fixed it, please do tell. Or if anyone has any experiences RMA-ing your device with a condition like this I'd love to know.

Yep your EMMC is fried. Sorry man.. But you can go to warranty. They *should* accept it since it is a developers phone but they could make a lot of hassle about it being rooted..
Sent from my Galaxy Nexus using XDA Premium HD app

Searched Hours Already, Help! Reboot after 25 Seconds

My N910A was stuck in a loop. It would load Andriod 6.0.1, but then after around 25 seconds, it would reset itself.... it would do this continually. I've noticed the top center section of my screen feels significantly warmer than the rest of the phone as this continues.
I tried using ODIN to reflash 6.0.1 and got stuck in a bootloop within the "Android App Optimization" It would make it to object 12 or 13, freeze, and then reboot.
I found the EPH5 Recovery Firmware and successfully flashed it onto the device, but that brought me back to square one of the rebooting after 25 seconds of loading.
The fact that the phone is getting warm leads me to believe something is screwy in the hardware, or something is locking up the processor on boot, and causing it to overheat.
I was able to get into the About Phone menu and noticed something odd - many of the objects had values of "unknown". My Phone Number, IMEI, IMEISV, IMS Reg (Not Registered), IP Address (Unavailable)
It's running a security patch from Aug 1, 2016 if that is needed for any diagnostics.
I don't know much about ODIN, but found a detailed write up what-is-odin-and-how-to-use-full-guide and chose to tick "Re Partition" when I flashed a firmware with a PIT file to ensure something wasn't corrupted in the file system.
I also read that when the IMEI shows unknown, it will wipe all settings files and create new, clean ones, so I ticked EFS clear.
Also, when I used a specific BL file to flash, I ticked "Phone BL Update" to clear out the old settings and reinitialize the new ones.
NOTHING I am doing is fixing this restarting issue though. I can barely make it through the About Phone menus to see the information.
I've literally searched for around 4 hours, downloaded about 16 different firmwares, and flashed a dozen times.... I've tried doing this on my own, and now I'm reaching out for an answer I'm sure is somewhere I haven't found yet.
Please help.

FWIW, I've also tried 3 different batteries as that seems to be a large suggestion for troubleshooting. All have the same result, so the issue is definitely with the phone.

Word for word
Started messing with this note 4 and word forword experienced the same issue you did. Did you notice though if you booted into recovery or download mode the phone will remain cool and run all day as long as you post pone the android os from booting? Then Samsung refuses to continue servicing this model? Sounds to me more like corporate greed rather than human error guys.
Ps seems like the oldest virus in the book. Continuously opening notepadbwindow after window until the hardware juat gives in and crashes. Or a kill system scriptbwith a random timer vatiable and overclock parameter. That's what i would do if i were them