I recently upgraded to ICS Passion v8 from Froyo 2.2, but I have two issues:
1. I don't get any sound at all from any media or games; music plays but there's no sound, and games will play but there is no sound from them either (I'm not in silent mode). Is there anyway to fix this issue?
2. I continually get a android.media.process has stopped error, which seems to drain batter, as well as preventing me from using both my camera and gallery (I don't really care about video recording, but I would like to take pictures).
Side Note: This is more of an aesthetic, but my network provider appears as a number instead of the name it appeared as in Froyo 2.2, is there a way to fix this? As well, the home and back button have reversed roles, is this normal?
I am using: ICS Passion v8 Build 3
Hardware:
Samsung Galaxy S Vibrant
Handset Provider: T-mobile
Network Provider: Telus Mobility
Solved, fixed permissions, then a format, wipe, clean flash. No more media issues. Thanks to anyone who looked at the thread.
Was running in to very similar problems, with many process errors just after I flashed in to ICS Passion v11. Did exactly as the OP, and fixed my problems too.
Thanks for following up on your post, unfortunately all too common to run in to someone who has your same problem, but they never bother to post what fixed it for them.
Related
I've been playing around with the rooted 2.1 far a few weeks now and I've noticed that after using the camera a couple of times, the phone "kind of" crashes. I mean kind of because some of the applications behave normally, but there is no audio from the phone, no video from the camera, volume up/down lags. No force close warnings. I've read some of the bluetooth audio issue threads and they sound similar. Has anyone experienced anything like this? I've tried other builds (eris21official-root) and the same problem.
Phone details:
ROM: VanillaDroidV1
Firmware: 2.1
Baseband ver: 2.40.00.01.22
Kernal ver. 2.6.29-564a4a15
Anyone with either of the two ROMs, could you please give it a try? I just need to know if it is the phone or the ROM.
Thanks
are you doing a data wipe and a davlik wipe before each flash there?
Ive used both of those and have had none of the issues you mention.
Im going back and forth between root ota and Sensable 2.0.
I am doing both of the erase you mentioned. I experience the issues within the hour after using the camera to shoot a few pictures. I can tell the phone is acting up because, I won't get any audio when I call or receive a call from someone. Thanks for the suggestion. Not sure what else to do.
I just bought a new car recently and when I try to pair my Fascinate with the car bluetooth, my phone slows down considerably, won't successfully complete calls, and eventually locks up, forcing me to do a hard reset. My car's bluetooth program locks up as well. One time I got an error message on my phone saying services.exe had to force close. At first I thought the problem was with the car, but my dad's Droid Incredible works beautifully on it.
My phone is rooted w/o lagfix, and has launcher pro. It's also been de-binged and has other basic bloatware removed. I don't use taskillers either. Any help or advice would be greatly appreciated, thanks!
I have been having this issue for a while now. I'm currently on stock ED01 and it is almost consistently happening when I end a call. After the call is over and I hang up, the phone does a silent FC with bluetooth being the cause (silent FC = 1 vibrate followed by 2 short vibrates).
When using the stock kernel, the FC is hit or miss. I can maybe get a FC after a 2nd call. When using ANY of the custom kernels built by the devs here, bluetooth will consistently crash after a call is over.
Just like the OP said, the phone will crash and will become very unresponsive. If the phone is responsive and I manage to turn bluetooth off then on again, it MIGHT connect back to the car.
It seems like no one else is experiencing this? Or maybe not a lot of people use bluetooth calling with their Fascinate? I went back to stock just to see if it was a kernel or ROM issue and while it works a bit better, it's still not 100% working. I'm hoping there is someone out there who has working bluetooth calling with their car. I had the T-Mobile G2x for a week and that phone worked perfectly (as far as bluetooth was concerned).
Anybody?
Bluetooth Crash After 1st Call is Ended
DeezNotes said:
I have been having this issue for a while now. I'm currently on stock ED01 and it is almost consistently happening when I end a call. After the call is over and I hang up, the phone does a silent FC with bluetooth being the cause (silent FC = 1 vibrate followed by 2 short vibrates).
When using the stock kernel, the FC is hit or miss. I can maybe get a FC after a 2nd call. When using ANY of the custom kernels built by the devs here, bluetooth will consistently crash after a call is over.
Just like the OP said, the phone will crash and will become very unresponsive. If the phone is responsive and I manage to turn bluetooth off then on again, it MIGHT connect back to the car.
It seems like no one else is experiencing this? Or maybe not a lot of people use bluetooth calling with their Fascinate? I went back to stock just to see if it was a kernel or ROM issue and while it works a bit better, it's still not 100% working. I'm hoping there is someone out there who has working bluetooth calling with their car. I had the T-Mobile G2x for a week and that phone worked perfectly (as far as bluetooth was concerned).
Anybody?
Click to expand...
Click to collapse
I'm also having this same problem with my Bluetooth crashing after my first call ends when using following:
ROM ComRom 1.3
Kernel TW with Voodoo Sound+BLN+UV+Misc tweaks 4/15 by jt1134
Radio ED04
2011 VW Jetta SEL (just purchased a few weeks ago)
I'm thinking to go back to stock as well but would prefer some kind of fix or even a workaround over doing that.
Yesterday I was able to make 3 calls with no crashes at all for the first time ever.
MIUIwiz 1.1
OTB kernel 1.6 - no mods in voltage control
ED04 modem
(No Longer Resolved) The ROM was the Problem with Bluetooth
DeezNotes said:
Yesterday I was able to make 3 calls with no crashes at all for the first time ever.
MIUIwiz 1.1
OTB kernel 1.6 - no mods in voltage control
ED04 modem
Click to expand...
Click to collapse
Excellent!!! Thank you for this! I already had the ED04 modem so that wasn't the problem. Last night I updated my kernel and this morning I tried again with no success so the kernel wasn't the problem. Later this morning, I loaded up the MIUIwiz 1.1 ROM and on the way home from work, I tested 4 calls and viola SUCCESS!!! ComRom 1.3 was the culprit and even though MIUIwiz is based on ComRom, somewhere along the line Bluetooth in the ROM was fixed.
Thanks again DeezNotes!
Edit: My problem is back as well now. Any ideas? Problem started last night when I attempted to make a second call while connected via bluetooth. I was able to make two calls this morning then upon ending the second call, I received the one long vibrate followed by two short indicating something crashed and then the phone would no longer connect.
On the same setup, the problem is back. Its actually a lot worse than before. I actually noticed crashes from Pandora when hanging up a call and Pandora wasn't even running (for days). Even after uninstalling Pandora, still get plenty of consistent crashes after hanging up a call. Interestingly enough, this is with an Audi, so hearing the issue is with a VW isn't far off from what I'm seeing since those cars are typically very identical.
I'm trying out a different phone on a different carrier [again] later this week. If all goes well, I'm going to chalk it up to Samsung and their lack of QC. I would say it's an Audi/VW issue, but I've successfully used the same features with a Blackberry and an LG G2x. Later this week I'll try the HTC Sensation and see how things go. Based on my experiences so far, this might be the last Samsung smart phone I'll ever get.
Bluetooth drivers issue - causing crashes.
Hello. found this thread whilst searching the internet for a related problem, just thought I'd add my experience on the matter.
The issue you are all experiencing is due to a bug in Broadcoms bluetooth stack. More specifically anything to do with listening for a bluetooth service then opening and closing a RFCOMM SPP connection to anything else (maybe a bluetooth OBD2 adapter) will cause either the BTLD process to consume 100% cpu (and make the device run slowly) or cause a kernel panic and reboot.
This is also related, but a slightly different bug (again Broadcoms drivers at fault):
http://code.google.com/p/android/is...rs&colspec=ID Type Status Owner Summary Stars
piemmmm said:
Hello. found this thread whilst searching the internet for a related problem, just thought I'd add my experience on the matter.
The issue you are all experiencing is due to a bug in Broadcoms bluetooth stack. More specifically anything to do with listening for a bluetooth service then opening and closing a RFCOMM SPP connection to anything else (maybe a bluetooth OBD2 adapter) will cause either the BTLD process to consume 100% cpu (and make the device run slowly) or cause a kernel panic and reboot.
This is also related, but a slightly different bug (again Broadcoms drivers at fault):
http://code.google.com/p/android/is...rs&colspec=ID Type Status Owner Summary Stars
Click to expand...
Click to collapse
that sounds really really technical. any ideas on what we can do to fix it?
Handsfree Bluetooth Problem is Back
My problem is back as well now. Any ideas? Problem started last night when I attempted to make a second call while connected via bluetooth. I was able to make two calls this morning then upon ending the second call, I received the one long vibrate followed by two short indicating something crashed and then the phone would no longer connect.
I have the same issue with ED05 de-bloated, stock kernel.
Has anybody found a solution?
Hello,
I'm going to describe the dialer lag bug and a possible clue how to fix it. In short the phone hangs when you try to dial (call) a number for up to 10 seconds (at least on my phone) and then the dialing begins.
As far as I've researched it is present in other phones as well. I'm running the latest CyanogenMod nighty (update-cm-9-20120511), but the same bug appears in all previous nighties and in the latest official Samsung 4.0.3 ROM I tried (XXLP7 I think). The logcat logs are from CM9, but I believe the reason is the same in the official Samsung ROM.
Full wipe (+sdcard if that matters), absolutely stock. Logged in Google account. Direct call shortcut on the main screen. WiFi should be turned off (very important). If the WiFi was turned on, restart the phone first for reliable reproduction. Leaving WiFi turned on for a longer period sometimes masks the bug.
1. Screen off
2. Wait 10 seconds, screen on, unlock
3. Tap on the direct dial shortcut
The phone hangs for ~ 10 seconds and then begins dialing. Exactly the same procedure with WiFi turned on results in no lag. The number is dialed immediately.
I suppose this bug is present in all ROMs, based on Samsung 4.0.3 XXLPQ+ (possibly previous ones as well).
I've attached logcat logs from point 1 (screen off) until the phone begins to dial and I hang up.
No WiFi (hangs): http://pastebin.com/GC01G2FR
WiFi (doesn't hang): http://pastebin.com/eJS9N6sz
Subtracting the noise, the last identical line between two versions is:
Code:
D/PhoneUtils( 2207): checkAndCopyPhoneProviderExtras: some or all extras are missing.
This is the line which appears when I start dialing the number. After that the difference are those lines, present only in No WiFi (hangs) version:
Code:
W/ActivityManager( 1985): Timeout of broadcast BroadcastRecord{410f0a90 android.intent.action.SCREEN_ON} - [email protected]40f159d0, started 10000ms ago
W/ActivityManager( 1985): Receiver during timeout: BroadcastFilter{40f15bd8 ReceiverList{40f15b60 1985 system/1000 local:40f159d0}}
I'm a developer outside of the Android ecosystem, but as far as I understand an intent broadcast SCREEN_ON is issued and its intent receiver timeouts in 10000ms (those 10 seconds during which the dialer hangs). Supposedly Android is waiting for some intent receiver to handle its onReceive() and during this period nothing happens.
Please note that in the log there is another timeout before this one with the same consequences, but with timeout for intent SCREEN_OFF, issued seconds earlier when I turned the display off. That's why I skipped it.
Interestingly with WiFi on this doesn't happen.
I searched many forums and some people report (but can't describe) the problem. Other don't have it. I suppose there are other variables I can't isolate. Can you please try to reproduce it and point me to the right direction (tools, approach) how to debug it? This is a showstopper bug IMHO.
This post is mirrored here: http://forum.cyanogenmod.com/topic/50279-dialing-lag-after-screen-on-with-logcatanalysis/
May I ask the administrators to transfer this thread in the section "Galaxy S II Original Android Development"? I think it will be more appropriate.
It happens to me only on stock ROM. cm9 never had that issue.
It actually started after I flashed the xwlp9 xen ROM, after that it haunted me for some time, until I went back to GB, deleted my contacts from gmail and resynced all again.
Wifi thing is interesting but I can't reproduce as it only happens once in a while. and doesn't reoccur the next time.
I'm on dxlp9 now and it happened just once in 4 days.
Yes, it is really frustrating. I didn't have the issue several days after I migrated to CM9. Now it happens even after full wipe. It is so annoying! This is basic functionality and I see people with Galaxy Nexus suffering the same issue. I think that I have enough knowledge to find the root cause, but I need somebody with a little Android debugging experience to help me start!
I have been having this problem as well with the stock (rooted) rom, and i recently flashed the Resurection Remix ICS rom (v2.0) just a few days ago and i still have this problem, almost without exception (ie easy to reproduce). I hadn't noticed the wifi part, for me it is about a 10sec lag with or w/o wifi, and actually i am now noticing a lag when turning on/off wifi... sigh.
I never got past "hello world" in perl so effectively have zero developer experince but if you have managed to figure out a fix for this I would love to hear it!
-Gaiko
After no one expressed any interest in this bug and I tried hard for a week, I gave up. Unfortunately IMHO Android 4.0.x is way unstable yet (I've experienced many issues with both stock and CM9 nighties). I reverted back to CM7 (currently 7.2.0RC3). It is Android 2.3.7 based, but I don't really miss anything from 4.0.x and I'm more than happy.
Thx for the reply. Its unforunate that its been so unstable, on my phone it seems like the longer i run it the less stable it is. I am going to try a newer stock rom and if that still gives me probs i will just go back to an older kernel and see if that does the trick.
Cheers,
-Gaiko
It's the first time I run into this issue and I had many stock and custom 403 and 404s.
For me, the delay is 5 sec and it ocurs randomly with or without wifi.
Now I run stock 4.0.3 xwlpg, jkay's fw, latest siyah kernel, go launcher.
I had this setup in the past and it didn't happened. Strange, ain't it?
Actually I don't care about this bug anymore. No one did anything to help and in Android 4.1 it is fixed. As I'm running on the latest nighties of CM10/4.1.2, I don't experience it anymore. Sometimes it's funny how fast technology goes forward.
I have this bug in android 4.2.1. Never used to have it, now I randomly do. Strangely, it cropped up at the same time as the multiple duplicate sms bug... I think they may be related. Any ideas?
Hi,
The problem with my LwW is the lack of sound. Basically, at some point neither the speakers nor the microphone don't work. The problem most frequently occurs when trying to dial a number or make a phone call, whereas the phone stops working, and a message saying that com.android.phone process stopped, shows up on the screen. The sounds seem to appear sometimes, after multiple reboots (the pleasure, though, doesn't last for long). However, that is not an adequate solution for this issue, you'd agree.
What I did notice is a characteristic snapping sound, crackling, that comes from both the front and rear speakers, but also from the earbugs when attached, which makes me think it's rather a software issue, not a hardware one. Perhaps it's something wrong with the phone app? Currently LWW is running Real ICS 6 custom ROM, I had reflashed to Gingerbread and tried stock ICS, but the problem presisted. Bootloader is locked, so I cant install any custom kernel. I attached the phone to ADK and tried to read warnings from LogCat when playing music but it doesn't show any particular problem except few android.phone warnings. I dont know which type of messages I should be looking for.
If anyone had this issue (or a similar one) please feel free to post your suggestion
Thanks
Hi Folks,
This was the closet forum I could find for my phone. I actually have the GS2 HD LTE (i757) from Bell Mobility in Canada. Monday I finally received my Jelly Bean Update (4.1.2) I wish I could say I an excited however it has caused me so much stress, Ever since I installed it my phone has been terrible laggy. ICS gave me no troubles but after seeing the huge performance boost in my Wife's i9100m last month when it was available to hers I did not hesitate to update mine. Below I will list my symptoms, as well as the steps I have done to resolve this. I have search everywhere for an answer and have come up with nothing. Also to note, my Friend in the office has a Galaxy Note with a different provider (Telus) who received the update the same day, we can put our phones side by side and we both experience the exact same issue.
Setup:
i757 (S2 HD LTE)
Not Rooted
Symptoms:
Swiping to unlock is choppy
Opening Messaging to text takes three part (Loads the body, loads previous message and then keyboard loads in the middle of the screen and works its way down.
30-45 second pause to open the dialer
when clicking the power button to get to the lock screen it shows the desktop for a second, then god to my lock screen wallpaper then my lock screen icons appear. After this I can swipe.
loading apps
at startup RAM is 558MB/737MB. I hit clear memory right away it goes to 394MB/737MB. But open any app I am back up to to 550MB-600MB
Things I have tried:
Install install was Down with Kies as a regular update with all my Apps still installed.
I Wiped Cache and down a Factory Reset
Reloaded the Stock ROM with Odin3 v1.85
In developer options I disabled animation for Window, Transition and Animator
I disabled ripple effect for lock screen
I disabled Google Now
Tried to Wipe Cache then resume use without reloading OS
Tried Disabling GPS, Bluetooth, WiFi and sync.
Installed Android assistant to clean up startup
Did another Factory Reset/Cache Wipe then install OS from MSD
None of these options have made a difference. The phone worked flawlessly on ICS, I don't know what else I can do. Has anyone experienced this issue? and if so have they fixed it?
At this point I will try anything before I take out the hammer and fix it for good. Any assistance would be greatly appreciated.
- Boots!
Also my Current status is Factory Reset/Wipe Cache OS Installed from SD Card nothing install.
* * * COULD MOD PLEASE MOVE TO APPROPRIATE FORUM I MUST HAVE OVER LOOKED THE i757 FORUM * * *
Moved
Hi,
I have the exact same symptoms on my SGH-i757m.
The phone is brand new! I got it for the job, in replacement of my s2-i9100. As soon as I got it, I had the official ICS, then JB done to it...and it is an absolute disaster up to now.
Sometimes I can't even take an incoming call because the ''incoming call screen'' (with the green and red phones logo) freezes, giving me the ''com.android.phone has stopped'' error.
I'll be looking out for solutions, but I might just take it back to ICS soon...
windex23 said:
Hi,
I have the exact same symptoms on my SGH-i757m.
The phone is brand new! I got it for the job, in replacement of my s2-i9100. As soon as I got it, I had the official ICS, then JB done to it...and it is an absolute disaster up to now.
Sometimes I can't even take an incoming call because the ''incoming call screen'' (with the green and red phones logo) freezes, giving me the ''com.android.phone has stopped'' error.
I'll be looking out for solutions, but I might just take it back to ICS soon...
Click to expand...
Click to collapse
windex.
Please keep this thread in mind, Anything I can find I will post it here. If you could do that same that would be great. My S2-i9100 was amazing with the Official JB release also. I am surprised more people are not complain online about this as I know my friend with the Note on Telus is having same issue (Update was released the same time for him) I also called Bell and their Tech support said they were receiving alot of the same issues since the May JB update..
Damn Lag has got my phone!
AH! damn update lag has got my phone and my girlfriends too! We both have the samsung galaxy HD LTE I757M phone and have exactly the issues all of you guys have. From extremely slow response to flickering and its just a pain in the ass. My girlfriend tried a factory reset which worked for about a week with no lag or anything but then just started the same lag issues we all have. A lot of people apparently are reporting that a factory reset does the charm but its only a matter of time before the issues creep back to your phone. Right now I am going to try a custom rom for our phones and hope that it works. If it does Ill post the results for you guys to hopefully benefit from.
sean
I was having the same problem with my I757M. This phone is fine on ICS 4.0.4.
I don't know the real solution but, the phone is fine (for now)
Used Forever Gone app
Did a factory reset before upgrading to JB 4.2.1 (Maybe?)
Removed Ripple effect on Screen lock
Set the transitions to 0.5x
Power savings enabled (Screen only)
Disabled these system apps
100% HD Games
AllShare Play
Asphalt 6
Google Play Magazine
Google Play Movies
Google Play Music
Google+
GPS navigator
Let's Golf 3
Self-Service
Update software
Google Play Books (or Play Books)
Social Network
Ringtones and Applications
Sympatico.ca
Talk
Talkback
TV mobile (bell)
Y! Finance
Yahoo! Finance Daemon
Yahoo! News
I installed JB 4.1.2 today, saw some improvements, hope it is fixed for good !
The ram usage on boot (369MB / 737MB)
Sorry to post again !!
Okay, it started to lag as described by others. So I went back to 4.0.4... The battery life is better on Jelly Bean because it can reduce the screen's power (not just brightness)
I did this today, my last attempt with JB...
In Dial :: *2767*3855# (it formats everything, even sdcard, so backup your things before doing this !!!)
I configured ICS from the welcome screen (no gmail configuration, etc.)
Installed JB 4.1.2 from Kies.
I disabled the programs mentionned at my previous post...
There was still a lag when unlocking the phone. Tried Holo Locker and didn't do anything... still lags.
Then, I searched on the net :
http://forum.xda-developers.com/showthread.php?t=2224906
It seems TouchWiz has problems rendering Widgets on homescreen, so, I installed Nova Launcher to replace it.
For now, when receiving a SMS, after unlocking, the wallpaper can become black, but there is no lag like before. :good:
Same situation
My wife‘s i757m has the same situation. I wiped to factory and uninstall like "let's golf", google play music. Then it turned much better for about 1week and then be back lag lag lag again.
I have no idea why it is so ridiculous , cause my friend's I727(GS2HD rogers) is very good after he updated his in March.
Please help me SGH-1757M
I have the same Issues.
After upgrading the Phone to 4.1.2 bellow issues identified.
1) When Incoming call comes the Phone Frezes and Green and Red button on the screen does not work
2) Some times it works but when I get any call the Phone rings with black screen and after some time it comes with number and then caller id and then answer button
3) Every time when I went to Messaging it loads the messages with number and next updates the Caller ID and then body of the messages and text editor
4) Morning when alarm rings phone Freezes and does not allow me to stop the alaram and force restart the Phone.
I am having so amny problems like this .
Please suggest what we can do here to resolve these issues.