hello.
i have a 32 gb hp touchpad overclocked.
when i turn it on i have sound working good.
but after very quicly, it have no more sound at all (even when i push the sound + or soung - button, i see the sound logo going up and down but no sound)
and if i turn it off and on the sound come back.
do you know what can be the problem ?
Thank you
Happens to me ALL THE TIME. I just chalk it up to WebOS being completely unfinished. But then again it could be some of the patches I have installed, since I spent all of about 3 minutes without them.
Me too, I read that Making a call in skype will bring sound back.
Apparently it helps to disable system sound, keyboard and vibrate.
Happened to me twice more today. So annoying.
Happens to mine pretty much daily. I don't see a whole lot of *****ing in general about it though, mostly here and Precentral, which leads me to believe it's mostly "modified" touchpads with this problem. I'm thinking it's a patch or kernal problem.
It's most likely a problem with a kernel or patch. I have 3 16GB's, two stock, one modded, and none of them exhibit this behavior. Since all of you have modded yours, I suggest removing patches/kernels and see if the problem persists.
parisien99 said:
hello.
i have a 32 gb hp touchpad overclocked.
when i turn it on i have sound working good.
but after very quicly, it have no more sound at all (even when i push the sound + or soung - button, i see the sound logo going up and down but no sound)
and if i turn it off and on the sound come back.
do you know what can be the problem ?
Thank you
Click to expand...
Click to collapse
te)
Install the Preware Linux App > Increase TouchPad Volume ( Lite)............
See if it makes a difference
I haven't figured out what causes it for me, but a simple solution to fix it without having to restart is to run a couple commands in xterm..
stop pulseaudio
start pulseaudio
Sound goes off (ANNOYING)
Why does the sound go off all of a sudden, I hate it, I can't even hear youtube videos, it requires a restart
Sent from my SCH-I510 using XDA App
Finally , I had to disable the email audible notification (left the vibrate only). Now it has been OK for more than 1 week, before it will lose sound in a few hours.
Hope HP get's this resolved.
Thanks
trialdoer said:
I haven't figured out what causes it for me, but a simple solution to fix it without having to restart is to run a couple commands in xterm..
stop pulseaudio
start pulseaudio
Click to expand...
Click to collapse
If you install the "Advanced Reset Options" patch, you can use it to restore your sound...
Just hold the power switch until the buttons show up, then tap "Cancel".
Hi,
Advanced Reset option does not fix the issue for me (unless I select Reset).
Sound fails even if the only App I have opened since a full reboot is the email App.
Maybe one of the installed Logging patches is causing the sound to drop out? Maybe we should enable logging to see if the logs give any indication around what is causing the sound issue?
this issue was happening to me everything my touchpad would go idle for longer than an hour (super annoying) however I gave all the suggestions here a try and finally had luck with robrob777's suggestion! Turning my email notification sounds to vibrate has seemed to fix my issue hasn't happened in 2 days. Just wanted to say thanks robrob777!
gburt said:
Advanced Reset option does not fix the issue for me (unless I select Reset).
Sound fails even if the only App I have opened since a full reboot is the email App.
Click to expand...
Click to collapse
There's an article over on precentral about fixing the problem, though it really isn't a fix, but rather a way of getting your sound back without a reboot. See it at:
www
precentral.net
/
fix-your-touchpad-s-lost-audio
Sorry about the format of the link, but forum rules for newbies prvented me from posting it properly. Since it obviously isn't spam, I am hoping I won't be in trouble for it.
It's complicated, and you might find a reboot easier, but perhaps some developer who's into patches will spot it and come up with a more permanent fix, either to fix the problem itself, or at the very least, to have the stop/start fix applied when the volume control button reaches max and is pressed again once or twice.
Update: It just became a little easier to apply the start/stop "fix". XServer, Xterm, and Xecutah just became available on webos-internals (.org). Just use Preware, select Applications, All, and the new stuff will show at the top of the page. Just download Xecutah and the other two packages will download with it if you allow it.
Update 2: Even easier...
After installing the X stuff, start Xecutah and create a shell script in the default directory you land in with Xecutah. I just used cat and typed it in.
cat >fixaudio
Here's what I put in it...
#!/bin/sh
stop pulseaudio
start pulseaudio
Then, fix up permissions...
chmod 070 fixaudio
(It's been a while since I used Unix/Linx, but I'm sure someone will correct my permissions choice if it's not right).
Then, when your sound goes away, start Xecutah and type fixaudio.
Even better... Use Preware to find an app called PulseAudio Restarter. Works well.
Related
Ok, I'm hoping someone may have some idea why this error is plaguing me.
After a hard-reset, the following behavior is observed on the T-mobile 3.14 rom.
1. Set Ringer (or leave at default) to anything.
2. Hit Ok.
3. Change volume to either Off or Vibrate.
4. Go back to phone options - ringer is now set to "BellDitty".
Odd thing is that when volume is restored, the phone doesn't play anything when an incomming call is received - not even the listed "BellDitty".
Anyone know what the problem is? How to work around it? Is the ringer just set in the registry? If it is, then it could just be a case of writing a program to restore the ringer ever 2 sec. or so.
Hope you guys can help - a phone that fails to ring is a misbehaving in my book.
Thanks.
Fixed!!!
After doing some hunting, here is what I found. If you guys have some spare time, try doing this to your phones and see if you have the same oddball results. From what I found:
When the Pocket PC is put into Mute, a key in the registry (HKCU\ControlPanel\Sounds\RingTone0) named Sound is set to *none* or *vibrate* depending on what you mute to. There is another key in that branch named “SavedSound”, which has the ringer you setup in Phone options. Now, as long as you don’t go into Phone options and hit “Ok” while the phone is muted, the registry keys work just fine – as soon as you unmute, the value of “Sound” gets set to whatever “SavedSound” is. HOWEVER – if you do go into phone options and hit OK, it confuses PPC 2002. It writes the new sound to the “Sound” key, however it never cleans up after itself in the same way it would if you unmated. Now when you unmute, it looks to the Sound key to see if it says *none* or *vibrate* so it knows to re-enable the ringtone. When it finds the saved value from the phone applet (that you hit “OK” to) it assumes that the phone was unmuted, even though it wasn’t.
Re: Fixed!!!
dadarkmcse said:
After doing some hunting, here is what I found. [...]
Click to expand...
Click to collapse
Well researched !
[ I've had this thought more often: do we have a Microsoft representative in the room here? If not, I guess we need to have some protocol for reporting issues from our collective brain back to the developers. (But ofcourse MS really needs to be here and read the forum if they're serious about making this a real phone.) ]
My audio randomly drops out and requires a reboot to clear. All audio is silenced. For example, pressing the volume buttons do not beep. It happens randomly, but most often after a reboot.
Tonight I was able to reproduce the problem fairly consistently so I was able to get a logcat (attached) of the issue. I was using Rockplayer v1.5.5 with hardware decoding. I don't think Rockplayer is the issue because the problem has happened with other programs, like Angry Birds.
I am not an expert but I see lines like "[FONT="]W/AudioTrack( 927): obtainBuffer timed out (is the CPU pegged?) 0x21a528 user=00033b2a," [/FONT]when the issue occurs. When everything is working normally, these entries are not there. I trimmed the log file to meet the size limitations. I have the whole file if needed. Please help!!![FONT="]
[/FONT]
Moved to general
I will try and post a logcat the next time mine does it.
I'm having the same problem. I can hear sound whenever i startup the tablet, but after a while (sometimes it can be less than 1 min sometimes after 5 hours) the sound stops and i only get static noise or no sound at all. Whenever that happens, in the android log appears the following lines repeatedly (with a frequency of 1 sec):
W/AudioTrack( ####): obtainBuffer timed out (is the CPU pegged?) 0x##### user=00######, server=00######
I've tried changing ROMs without success in solving this problem, now i'm using TNTL v4.4.0.
The bug triggers while i'm using sound (games/watching videos on youtube/playng music on winamp/ pressing the battery button on the status bar, triggering that "click" noise).
When this bug is triggered, i get FC from some apps that use sound (Youtube / Winamp / some games)...
Rebooting the tablet fixes the problem untill it triggers again
i've been using adb logcat several times with this problem and the only correlation between the logs is the line described above, i've tried searching on google, but the results i get are for cellphones or pre 2.2 devices... in one of them, they interpret it as a kernel problem (http://forum.xda-developers.com/showthread.php?p=6280968)...
Any help is appreciated.
Same thing here on one of the woot tablets running Vegan 5.1. 1. Usually happens after coming back from sleep. I asked for a replacement and the new tablet will be here tomorrow.
I really hope this is a hardware problem and not caused by a rom or app. Still interested in finding out what causes this, so I won't have this happen again with my new tab. Did anyone have this issue with the stock rom? Are these all recently bought tablets? I didn't spend enough time with stock to encounter sound problems.
I've been toying around with my tablet to see what is causing the problem, so i started by Flashing all over to stock to find out if at some point the sound problem stops... well... here are my results untill now:
Started at TNTL 4.4.0, Many apps installed and the sound problem appears constantly and is triggered easily. Before starting I backed up everything using Titanium Backup xD.
Part 1: Format + NVFlash to "belkit 1105" + Factory Reset: Problem Still Arround, took me about 3 reboots and 7 minutes to reproduce it by playing a song and randomly click on the battery/wifi/notification buttons with the sound of those buttons turned on.
Part 2: Updated to "stock 3588" (couldn't do it through OTA because it sayed that my tablet was up to date... so I downloaded the update from the NVFlash guide and installed using this guide from the internal SD. It didn't work, it took me about 5 minutes to reproduce the error, no rebooting .
Part 3: Settings > Security > Factory Reset: ... still haven't been able to reproduce the error, i've rebooted it about 7 times and listened music for 3 hours, eventually clicking on the notification/battery/wifi buttons and it seems to work fine... at least this is a checkpoint for me
It would be great if someone with the same problem could confirm that this works, i'm going to leave my tablet playing music during the night just to be sure :9.
Oh, JIC I bought my tablet on 27 Feb from J&R Electronics Inc through Amazon.
I'm having the same problem with mine in fact I have the tablet sitting next to me and the thing just went all static and freaked the cat out and woke my wife up not exactly cool when your in bed! I may have to look into exchanging or return it! I would hate to be at work or somewhere else and have it freak out like that! It's annoying!
I'm having the same problem, I lost all sound once I upgraded to Vegan Tab Ginger. Downgrading, or any changes doesn't do anything
I have a similar issue. I installed Cyanogenmod 7.0.3 and my sound mysteriously goes away. I can easily repeat it by putting the table to sleep and then waking it up. Sometimes, you can hear some static before it goes out.
I discussed this with Gojimi long time ago, but, I dont remember, I think the issue got lost with time. Still happens though
I'm new to this forum, and android too - but I've been using Linux of some sort on my desktop for years so I took a stab at installing cm7 on my Player 5.0 (US). As I'm not I can't post to the dev forum, so I figured I'd share my experience here.
Rooting the device was pretty pretty simple. I found a bash script online somewhere that used the zergkode exploit, and walked through the script manually via adb.
I wanted to watch the root process myself and interact with it in case something went wrong. It worked fine. I had more trouble finding an amd64 version of the adb binary than I did anything else actually.
Next I tried updating the kernel to the entropy's daily. I think the most recent I could find was for last month, but it worked just fine. I briefly considered firing up winxp in a virtualbox to try and get odin working - but considering the problems I've heard others have with kies and drivers - I just bypassed it and looked around for a linux rom flashing solution. Heimdall was easy to find
Checked out the lasted sources out at git://github.com/ambrice/Heimdall.git, compiled, and flashed the kernel with it. I think the command was something like
Code:
heimdall flash --kernel zImage --verbose
Reboot, make a backup of device with the recovery manager. Reboot, copy update-cm-7.2.0-RC1-YP_G70_USA-KANG-signed.zip and gapps-gb-20110828-signed.zip to /mnt/sdcard/external_sd where my microsd card lives. Reboot back into recoverymode.
By the way. I couldn't seem to get the hang of the keypress to kick in the recovery mode or download mode. I'd usually try various combinations of power and upvol until at some point in the boot process it'd kick in. Do you hold the volume key down while depressing power, then releasing it, then volume or is it some other combination? In any case, I rebooted enough times to eventually stumble into recovery mode.
After that, install worked pretty much like what I expected it to. Did a Wipe Data/Factory Reset, install from zip. Installed gapps from zip. Reboot.
CM7 fired up fine, and I thought the bootsplash is nifty. Heck, the whole thing is very pretty and has nice effects. I noticed right away that Google apps didn't take, so I rebooted (again and again) until eventually I manged to find recovery and re-applied the zip. Worked this time.
Fired up Titanium Backup and began restoring apps. Took me an hour or two to get it all working. Some apps didn't want to restore and would freeze Titanium. Especially anything samsung related like the FM Player, which I still don't have installed. In fact, I don't think I have *ANY* samsung apps installed, which I kinda like.
Impressions/Bugs/Annoyances:
* Headphones do not work at all unless you use the stock earbuds that shipped with the player are used. Took me about a halfhour to figure that one out. I imagine that the stock earbuds with their inline mute have some different wiring, and regular earbuds/headphones just aren't seen the same and cm7 doesn't like em. Dunno. Annoying.
* Wifi doesn't work unless you go into airplane mode and enable wifi. I imagine this has something to do with disabling the software that handles the non-existant phone hardware? Is there a way to do this without going into airplane mode?
* Wifi seems flakey, drops connections after 10/15 minutes. Comes back usually, but it's annoying. This is on an open network too. In my experience (with linux), things can become all sorts of extra fun when you start adding wpa/wep to the mix. So I'm not hoping for better behavior when I try on an encrypted net.
* Camera works, but I can't figure out how to use the small one facing me. No big deal, but ... ugh.
* On initial (cold) boot, it seems to reboot as soon as it startes the "scanning media" phase... Once. Subsequent reboots seem to act fine.
* Not a fan of adwlauncher, so replaced it with launcherpro. On first startup, It shows a black screen, sliding to the left or right to another "page" fixes the big black space on the screen. Not sure of this is launcherpro problem or a cm7 one. A little bit annoying, but not a big deal.
* CM7 seems to eat up a lot of space. I have a few gig free on /mnt/sdcard and on /emmc, so I assume the warnings I get when trying to install new apps refers to the root directory. I think I saw some options about where to install new apps somewhere in the settings, which would solve that problem. I could also use Titanium to move system apps back to userspace (terminology right?) I think.
Other than that - everything seems to be running fine. I have other third party software that I used to take care of setting power/cpu profiles which I notice CM can handle on it's own - so I'll probably need to spend some time figuring out how all of that works.
I'm happy for the most part at this point. The earbuds thing and the wifi flake-out are the most annoying bugs, which I can live with for a while I suppose. I never use the FM Radio anyway.
Anyway, thanks to all the folks out there working on the CM project for the Galaxy Player. It's amazing that it works as well as it does at this point. Keep up the good work! I might even try CM9 at some point, but I'll wait until the camera is reported working first.
xterminus said:
I'm new to this forum, and android too - but I've been using Linux of some sort on my desktop for years so I took a stab at installing cm7 on my Player 5.0 (US). As I'm not I can't post to the dev forum, so I figured I'd share my experience here.
Rooting the device was pretty pretty simple. I found a bash script online somewhere that used the zergkode exploit, and walked through the script manually via adb.
I wanted to watch the root process myself and interact with it in case something went wrong. It worked fine. I had more trouble finding an amd64 version of the adb binary than I did anything else actually.
Next I tried updating the kernel to the entropy's daily. I think the most recent I could find was for last month, but it worked just fine. I briefly considered firing up winxp in a virtualbox to try and get odin working - but considering the problems I've heard others have with kies and drivers - I just bypassed it and looked around for a linux rom flashing solution. Heimdall was easy to find
Checked out the lasted sources out at git://github.com/ambrice/Heimdall.git, compiled, and flashed the kernel with it. I think the command was something like
Code:
heimdall flash --kernel zImage --verbose
Reboot, make a backup of device with the recovery manager. Reboot, copy update-cm-7.2.0-RC1-YP_G70_USA-KANG-signed.zip and gapps-gb-20110828-signed.zip to /mnt/sdcard/external_sd where my microsd card lives. Reboot back into recoverymode.
By the way. I couldn't seem to get the hang of the keypress to kick in the recovery mode or download mode. I'd usually try various combinations of power and upvol until at some point in the boot process it'd kick in. Do you hold the volume key down while depressing power, then releasing it, then volume or is it some other combination? In any case, I rebooted enough times to eventually stumble into recovery mode.
After that, install worked pretty much like what I expected it to. Did a Wipe Data/Factory Reset, install from zip. Installed gapps from zip. Reboot.
CM7 fired up fine, and I thought the bootsplash is nifty. Heck, the whole thing is very pretty and has nice effects. I noticed right away that Google apps didn't take, so I rebooted (again and again) until eventually I manged to find recovery and re-applied the zip. Worked this time.
Fired up Titanium Backup and began restoring apps. Took me an hour or two to get it all working. Some apps didn't want to restore and would freeze Titanium. Especially anything samsung related like the FM Player, which I still don't have installed. In fact, I don't think I have *ANY* samsung apps installed, which I kinda like.
Impressions/Bugs/Annoyances:
* Headphones do not work at all unless you use the stock earbuds that shipped with the player are used. Took me about a halfhour to figure that one out. I imagine that the stock earbuds with their inline mute have some different wiring, and regular earbuds/headphones just aren't seen the same and cm7 doesn't like em. Dunno. Annoying.
* Wifi doesn't work unless you go into airplane mode and enable wifi. I imagine this has something to do with disabling the software that handles the non-existant phone hardware? Is there a way to do this without going into airplane mode?
* Wifi seems flakey, drops connections after 10/15 minutes. Comes back usually, but it's annoying. This is on an open network too. In my experience (with linux), things can become all sorts of extra fun when you start adding wpa/wep to the mix. So I'm not hoping for better behavior when I try on an encrypted net.
* Camera works, but I can't figure out how to use the small one facing me. No big deal, but ... ugh.
* On initial (cold) boot, it seems to reboot as soon as it startes the "scanning media" phase... Once. Subsequent reboots seem to act fine.
* Not a fan of adwlauncher, so replaced it with launcherpro. On first startup, It shows a black screen, sliding to the left or right to another "page" fixes the big black space on the screen. Not sure of this is launcherpro problem or a cm7 one. A little bit annoying, but not a big deal.
* CM7 seems to eat up a lot of space. I have a few gig free on /mnt/sdcard and on /emmc, so I assume the warnings I get when trying to install new apps refers to the root directory. I think I saw some options about where to install new apps somewhere in the settings, which would solve that problem. I could also use Titanium to move system apps back to userspace (terminology right?) I think.
Other than that - everything seems to be running fine. I have other third party software that I used to take care of setting power/cpu profiles which I notice CM can handle on it's own - so I'll probably need to spend some time figuring out how all of that works.
I'm happy for the most part at this point. The earbuds thing and the wifi flake-out are the most annoying bugs, which I can live with for a while I suppose. I never use the FM Radio anyway.
Anyway, thanks to all the folks out there working on the CM project for the Galaxy Player. It's amazing that it works as well as it does at this point. Keep up the good work! I might even try CM9 at some point, but I'll wait until the camera is reported working first.
Click to expand...
Click to collapse
Cool... welcome...
I am not a CM7 user as I use CM9, but I wanted to give you clear directions on the Download and Recovery mode key combos.
Download Mode = Power + Vol Down (-) - Hold this key combo from a full power down state. Hold them until you see the Yellow Triangle logo. It should be about 5-8 seconds
Recovery Mode = Power + Vol Up (+) - Same as Download Mode... Hold them until you see the CWM menu.
I usually hold them until I see these menus... I think holding them for about 5 secs or so and letting go of the power button still gets you in those modes.
followup
cvcduty said:
Cool... welcome...
I am not a CM7 user as I use CM9, but I wanted to give you clear directions on the Download and Recovery mode key combos.
Download Mode = Power + Vol Down (-) - Hold this key combo from a full power down state. Hold them until you see the Yellow Triangle logo. It should be about 5-8 seconds
Recovery Mode = Power + Vol Up (+) - Same as Download Mode... Hold them until you see the CWM menu.
I usually hold them until I see these menus... I think holding them for about 5 secs or so and letting go of the power button still gets you in those modes.
Click to expand...
Click to collapse
Thanks, I think the trick is ONLY hold the power button down long enough to get it to boot. Pressing it beyond that point doesn't do anything good. Thanks
Some followup notes on CM7 I didn't cover in my first post:
* By swapping out wpa_supplicant (in /system/bin) for a newer version seems to help with wifi stability quite a bit. There is a link to a rar in the CM7 thread with a few alternative binaries. In any case, I don't have to fool with airplane mode anymore. Wifi just seems to "work" now.
* I've noticed that CM7 seems to suck a lot more juice when "sleeping", or idling with the screen off. I've noticed some mentions of a failure in the kernel to go into deep-sleep, which I suppose makes sense.
* Touching anything bluetooth related (turning it on, scanning, etc) often but not always results in an crash and instant reboot. I don't use bluetooth much, but I can see it's a problem. Disabling all bluetooth settings has helped stability quite a bit.
* The "black screen" I noticed in launcherpro went away when I disabled scrolling widgets.
* I've tried manually installing the FM Radio app (copying apk directly in with appropriate metadata files.) Still not working although it shows up. I suppose in order to get it working I'll have to restore all the samsung apps too. I'll get it working eventually I'm sure. I tried a third party Fm Radio app (Spirit Radio Free), and it didn't work at all either. At least it installed.
* In the calling preferences, where you can select googlevoice as your voicemail provider results in a crash of the google voice app. I also can't get the phone to properly register with a SIP provider with the stock CM7 settings either. I disabled that configuration and restored the Groove-IP app until I can figure out what's going on. I have a proper gv/sip gateway I can use (besides grooveip) - but the phone doesn't seem to want to work with it.
* For this particular ROM, it'd probably simplify everyone's lives if it were possible to remove any reference to most of the phone settings. For example, the Player doesn't have to deal with "Mobile Networks" (under settings/wireless & network settings). Removing the option to enable mobile data makes sense too I suppose. I'm not sure *how* to do it, but I thought I'd mention it.
That's it for now.
Okay, I would have liked to post this in development but apparently I dont have enough posts. What is th deal with the phone dropping out on CM10 when the screen goes black from the sensor, then coming back when the call is dropped by the other person. Does anyone have a fix for this, the CM10 thread gets so diluted with different issues you'd think people would start making other topics regarding issues rather than discussing them throughout a 30 page thread.
Are you talking about the screen shutting off and not being able to use the dialer or any onscreen buttons?
tallyforeman said:
Are you talking about the screen shutting off and not being able to use the dialer or any onscreen buttons?
Click to expand...
Click to collapse
Yeah but it also drops the phone call when that happens.
Thanks really strange. Try getting a fresh download with the gapps and flash it again.
It's a good thing you didn't post this in the development because it would have been moved here. You can always PM me with questions and I try my best to respond to everyone in a timely manner.
Anyhoo. I'm not quite sure as to why this isn't working yet. I've called my family, friends, girlfriend, whomever a few times already and haven't ran into the problem yet. With this being said, no one is giving any real details on what leads up to the problem or how to really reproduce it. The best I've received so far is "I make a call, the screen goes off and won't go back on." What I need is someone to get me the logs of this happening. As weird as this may seem it's the only way I can help anyone with it. Apparently from what I hear the phone is still "working" but with the screen just not turning back on. If this is the case, anyone should be able to plug their phone into their computer and get me a logcat of what is going on (this doesn't require any screen interaction if the phone is setup properly). If you have any questions on how to get one, search the forums. It's been posted in just about every development forum for every phone including ours.
My phone did that last night. People in the CM10 thread have been blaming it on the bluesleep fix but who knows. I had that flashed at the time too. When it happened, I was on a call and the call dropped a few minutes into the conversation, the screen stayed black and didnt come back on. I had to pull the battery and restart. I called the person back and it happened again. Long story short, due to my own error, one thing led to another and I ended up SBF'ing. Since last night, I made one call and it didnt happen. I need to make more calls to see if it persists. The problem is, I dont call people very much. lol
Just want to add that I was having this issue also. I only noticed it after I installed the bluesleep fix... I SBF'd and installed clean with no bsfix and have not had this issue since... Maybe it has nothing to do with bluesleep but thats some really strange timing if it doesnt.
If it happens to me again I'll get a log for you DZK but seeing as I don't plan on flashing the bluesleep fix back I don't think it will happen.
Well I sent a message to you DZK cause i'd really rather avoid SBF if I could. But if I have to I will because most people are linking it to the bluesleepfix which I did indeed install. In any case, the phone just hangs when the screen shuts off until the other person hangs up the phone then the call is ended and the screen comes back, but until then voice is dropped the call is droped and the screen remains off as that person tries to talk to me but isnt disconnected until they end the call.
[Tutorial] How To Logcat
Logcat or it never happened.
download adb
place it in folder I use
Code:
c:/root
open command prompt
Code:
cd/
Code:
cd c:root
Code:
adb logcat *:E > oh_nos_it_crashed.txt
should work
oh_nos_it_crashed.txt will be in root folder can name it
Code:
adb logcat *:E > dropped_call.txt
if you want
I'm having similar issues. The phone locks up on a call and can't be unlocked. I just have to pull the battery. The call continues for me, so at least I can finish the call, but to hang up - pull the battery.
I currently have the CM10 ROM, gapps v5, and bluesleep fix applied.
So, how does one get rid of the bluesleep fix? Can I delete is somehow using a root browser, adb, or... ? If not, can I just reflash the ROM and gapps files (without the bluesleep fix) without a factory reset, etc.? Or am I in for a complete refresh of the phone and reflash of the ROM and gapps?
TIA
no way to remove bluesleep that i remember
just restore nandroid of rom other than cm10, then reflash cm10
This started happening to me tonight.
I haven't installed the Bluesheep fix... unless that's the MX2 wifi patch.. if that's the case then I have that too.
My current workaround is using headphones, which disables the proximity sensor.. I also put my phone to stay cycle a little longer.
I just flashed my phone with CM10a3 Wednesday and ran into this issue with the first call I tried to make. I'm still new to rooting and flashing ROMs (my first time lol) so I don't have too much useful information, I will try and gather some logs next time it happens. Unfortunately it is not something that seems to happen every call. My current work around is to use bluetooth or speaker phone as the issue does not happen then.
I'm using
CyanogenMod 10-20130113-Daytona Alpha 3
gapps-jb-20121011-signed
I'm also running into issues with the mount locations and losing settings upon restart, however I still need to do more research on those items first.
I was able to get some logs around the phone call issue. However, it appears the behavior has changed for me now. When the screen goes to sleep, the call audio cuts out, and then about 10-15 seconds later I get notified that the call was dropped. I do now however have control of my screen during this whole time.
Unfortunately by speakerphone workaround does not work for this new behavior, so I have to carry around a wired or bluetooth headset in order to take calls.
Since the behavior is no longer identical to the original poster, I'll post my log in a new thread once I clean up some of the noise in the log.
licwid said:
I was able to get some logs around the phone call issue. However, it appears the behavior has changed for me now. When the screen goes to sleep, the call audio cuts out, and then about 10-15 seconds later I get notified that the call was dropped. I do now however have control of my screen during this whole time.
Unfortunately by speakerphone workaround does not work for this new behavior, so I have to carry around a wired or bluetooth headset in order to take calls.
Since the behavior is no longer identical to the original poster, I'll post my log in a new thread once I clean up some of the noise in the log.
Click to expand...
Click to collapse
lol carrying headphones around? that sounds a bit overkill.
Hi Guys,
Always loved loading custom roms on my androids. Never had a problem I had to ask for help with until now. Please bear with me; I'm trying not to be noob-ish.
I'm running Resurrection Remix 4.4.2 on my Galaxy S2 GT-9100. I installed it last night. Had a big problem (after rebooting into recovery and then wipingdata/factory reset) - I couldn't mount my sdcard1 (externalSD) in CWMrecovery > hence I couldn't install the rom.zip from my SD card. I ended up using adb sideload to push the rom and GAPPS onto phone.
ROM working great so far, loving it! Suddenly; I can't adjust the audio slider for my main audio. The ring-volume and alarm volume can both be adjusted - and the speaker works when either of these two are used. My music/audio volume however won't lift up off zero. The speaker has the line through it to say it's muted completely.
I've tried using my hardware buttons, and the touchscreen to adjust it. I've searched Google & XDA. I've looking through all the settings on my phone. No luck. I've tried restarting phone. Can't think of any settings I've adjusted that could cause this. I was playing with contacts all afternoon, syncing FB images & organising Google contacts.
Please can somebody give me a hand - I've got my wedding coming up in 3 weeks and I don't have millions of hours to troubleshoot this alone.
Thanks in advance, let me know if there is anything I can do to help.
****This is strange. Just restarted my phone and it works again. Not sure then what is triggering the issue. Could be something to do with Open Mic for Google Now (it listens actively for "Ok Google"). Could be something to do with USB cable being plugged in and it thinks it is docked? Not sure any more. Working for now.****
****Now lost audio again! Was simply using my phone, using Google now to test the commands etc. Audio level dropped to zero, and I can't lift it up. Why! Perhaps it happened after phone went into standby?**** I've just checked and my WiFi doesn't go to sleep when phone is standby - it's already set to stay on.