Related
I have a problem with assigned ringtones as they keep resetting to stock settings or removing themselves after every reboot, planned or not, or sporadically, and have to reassign them practically a couple of times a day and its becoming a pain. Im rooted & on stock rom. I had a nexus 1 prior and never had problems stock, with miui, or cm7. I just got my phone like 2 days ago and am really contemplating returning it as I have also had a lot of reboots, freezes, and severe lag. Yes, I have ringtones on internal sd, and also tried them from external sd and same thing happens. Can someone please help me?
I have searched and found no answer. And I'm sorry if I somehow missed it.
Sent from my LG G2x
Okay.. I know. This is my first post, but don't use that to determine the validity of the information.
I've been on here for months, just didn't have anything useful to contribute until now.
Switched from rooted Gingerbread MT3G to G2x - was pretty excited till the bluetooth issues set in.
Didn't have the random reboots like everyone else. I think that happened once in my pocket... not thing to write home about there. This damn bluetooth was killing me though. Like a bad toothache badly in need of a root canal. Every time I picked up the phone I was reminded how beautiful but flawed this is.
So my search began. Poured over LG forums, T-Mobile and Google searches, compiling information. It became clear that this didn't seem like a hardware issue. The crappy Andriod 2.2 shipped with the phone was the issue. To me it seemed like this wasn't fully tested before shipping. Has sold tens of thousands of these phones and were largely unaware of the issue - the techs were surprised when the reports came in - mainly from US based customers on T-Mobile. In my quest I stumbled across an app that reported to fix a similar issue on a few other phones and gave it a shot, and it worked. So real simple here you go:
1. Root your phone, if you haven't already done so. I did with a heavy heart. Was waiting to do so but this issue was driving me nuts.. I used these scripts to Mac and Linux (I'm a unix guy):
http://forum.xda-developers.com/showthread.php?t=1048309
2. Download, from the market, and run, the following app:
>>>> Bluetooth Fix Repair <<<<
That's it!!
Here's what I did to test:
a. Left headset on, power cycled phone
b. Left phone on, power cycled headset
c. Out of range disconnect on head set, then moved back in range - successfully placed call.
d. Received call from a fresh connect, force range disconnect, then reconnect - successfully received call.
e. Disconnected headset from phone menu, then reconnected, placed call successfully.
f. Left headset and phone on for hours, multiple disconnect/reconnect - successfully placed calls.
I'm using a Blueant Q1, with the Blueant app from the market - BTW.
All seems to be well so far.. Give it a shot
fix the a2dp on gb and i'll give you your first donation.
What were the issues you had? My bluetooth seems to work fine, except the volume seems low and of course it helps to drain the already short battery life -- sorry, don't mean to be adding another battery rant!
donbeth said:
What were the issues you had? My bluetooth seems to work fine, except the volume seems low and of course it helps to drain the already short battery life -- sorry, don't mean to be adding another battery rant!
Click to expand...
Click to collapse
My battery life is fine. Lasts the whole day and then some. Check the running apps and kill the unnecessary tmobile apps and anything else that you don't need. Another way to save battery is to drop the data rate down to 2G. Settings --> Wireless & Networks ---> Mobile Nets --> Use 2G. I know, defeats purpose of having 4g, but it works fine for email and IM.
Bluetooth issue:
Bluetooth disconnects and doesn't reconnect. Only way to resolve is to power cycle phone. Sometimes it would indicate that it was connected where it wasn't. Multiple folks have the same issue. Doesn't seem to matter whether it's a headset or car bluetooth.. same issue.
crazythunder said:
fix the a2dp on gb and i'll give you your first donation.
Click to expand...
Click to collapse
Wish I had the time to get into the ROMs. Don't know how you guys do it..
Returned the original G2x today and got another. Well, bluetooth is jacked on this one also. You know, I shouldn't have to be messing with this damn thing I paid $300 for. It should work.. The right thing for T-Mobile to do is recall the G2x and replace it the new dual core nexus for affected users. This phone is a piece of shyte.
The BT fix was short lived My bluetooth must have disconnected half a dozen times today. Very frustrating.
jlevy73 said:
The BT fix was short lived My bluetooth must have disconnected half a dozen times today. Very frustrating.
Click to expand...
Click to collapse
I have a Blueant Q2 that collects dust because it is useless trying reconnect it every time it disconnects (far too often) while I'm driving, what's the point? Bluetooth is a fail on the G2X.
So the damn bt issue is still not resolved.
Sent from my Sensation using xda premium
ICS fixes the BT issue... but how? And can it be done for previous versions too?
I have tried the ICS CM9 and it seems to fix this BT issue. Not sure how it happens. Can one of the developers comment and maybe implement the fix in their ROM as well?
crazythunder said:
fix the a2dp on gb and i'll give you your first donation.
Click to expand...
Click to collapse
It works in the SK ICS builds.
I know it is an old thread but would like to share my experience here.
My only desire was to have the bluetooth not disconnect without announcing the disconnect. I saw this issue in GB 2.3.3 and below and saw it fixed on 2.3.4 and above, only to see another issue (no mute via bluetooth) crop up.
I have, however, by sheer luck and burning hours at it managed to fix it for 2.3.3. Haven't tried to see if it fixes the mute problem yet. I am satisfied with Weapon G2x 3.0 R1 .
Here is the link to my post. http://forum.xda-developers.com/showthread.php?t=1590523. Note that you will loose everything in the internal SD card so be prepared. It seems that the disconnect problem has its root in another partition (other than /data, /system and /cache). I have been problem free for almost 3 weeks now.
Will try with 2.3.4 and above later to see if the mute issue gets fixed too .
Try at your own risk and post results as you find. The reference thread in the post can be used to create an out of the box G2x with T-Mobile ROM so no chance of bricking (I believe this phone is unbrickable ).
mansa_noob said:
I know it is an old thread but would like to share my experience here.
My only desire was to have the bluetooth not disconnect without announcing the disconnect. I saw this issue in GB 2.3.3 and below and saw it fixed on 2.3.4 and above, only to see another issue (no mute via bluetooth) crop up.
I have, however, by sheer luck and burning hours at it managed to fix it for 2.3.3. Haven't tried to see if it fixes the mute problem yet. I am satisfied with Weapon G2x 3.0 R1 .
Here is the link to my post. http://forum.xda-developers.com/showthread.php?t=1590523. Note that you will loose everything in the internal SD card so be prepared. It seems that the disconnect problem has its root in another partition (other than /data, /system and /cache). I have been problem free for almost 3 weeks now.
Will try with 2.3.4 and above later to see if the mute issue gets fixed too .
Try at your own risk and post results as you find. The reference thread in the post can be used to create an out of the box G2x with T-Mobile ROM so no chance of bricking (I believe this phone is unbrickable ).
Click to expand...
Click to collapse
Wow you dug up deep for this. I believe this is the time we didn't have a2dp on cm roms
Sent from my LG-P999 using xda premium
All these new roms are amzing however, Hellfire Sandwitch and Pheonix both have this damn Bluetooth issue. I go to make a call and no sound comes to the bluetooth except some static and then it goes away. I hear nothing. I switch to speaker phone and I hear the dialtone on that. What the heck is going on with the bluetooth on these roms? Both ICS and GB share the same problem. I'm using that fix posted on the forums that makes any rom work with the new march 2012 BB update.
SovereignKnight said:
All these new roms are amzing however, Hellfire Sandwitch and Pheonix both have this damn Bluetooth issue. I go to make a call and no sound comes to the bluetooth except some static and then it goes away. I hear nothing. I switch to speaker phone and I hear the dialtone on that. What the heck is going on with the bluetooth on these roms? Both ICS and GB share the same problem. I'm using that fix posted on the forums that makes any rom work with the new march 2012 BB update.
Click to expand...
Click to collapse
check the irl too?
No haven't done that. Not sure how you mess with the irl. I know it has something to do with baseband. But I don't think it has anything to do with Bluetooth?
Been contemplating for a while whether to post this as it will come off as rather trollish. Had my Infuse for over a year now. When I first got it I noticed there were some "issues". I remained patient hoping or thinking maybe when GB was released it would improve. It did not. Later I needed to root this phone and came here, found a ROM that had all the AT&T junk stripped out. Phone worked better, but still had these issues.
I got to the point that I knew I would never again purchase either a Samsung phone or Android. Did not know what the culprit was. Just recently I had the chance to really take a look at an HTC EVO, and I realized that Samsung is the problem, not Android.
Number one issue is that this phone is sluggish, and sometimes unresponsive. I will touch whatever button and get that vibrating acknowledgement, but nothing happens. I will be in the app menu and wish to exist and the home button just does not respond.
Yesterday I missed a call because the bloody phone just did not respond, even though I touched the answer button. Other times I just can not make a call. I dial number, and the phone just sits there doing nothing. Eventually I just pull out the battery and restart the phone to make a simple bloody call. I had a HTC WinMo phone for years and never once experienced this. No matter how farked the OS could get with some app or whatever, the phone function always worked.
I do not run a lot of apps, and recently have experienced these issues with almost literally no apps installed. I will then add something like GO taskmanger just to confirm that the unresponsive behavior is not due to some app taking up memory/CPU etc..
Sorry for the long post, but I am at my wits end with this bloody phone. The fact that I miss calls when the **** phone is right in my hand is unacceptable. So before placing this phone in a box filled with C4 and shooting this to the moon, hoping that maybe a solution is out there.
p.s. I have 2 Infuse in use, both have the same issue.
What firmware are you running?
Is it the same firmware on both phones?
What is the launcher?
Have you tried a different modem?
Are you using a battery saver like juice defender?
Are you using an ad blocker?
Are you using a specific kernel? Oc? Uv?
Need for specific info
ssa2204 said:
Been contemplating for a while whether to post this as it will come off as rather trollish. Had my Infuse for over a year now. When I first got it I noticed there were some "issues". I remained patient hoping or thinking maybe when GB was released it would improve. It did not. Later I needed to root this phone and came here, found a ROM that had all the AT&T junk stripped out. Phone worked better, but still had these issues.
I got to the point that I knew I would never again purchase either a Samsung phone or Android. Did not know what the culprit was. Just recently I had the chance to really take a look at an HTC EVO, and I realized that Samsung is the problem, not Android.
Number one issue is that this phone is sluggish, and sometimes unresponsive. I will touch whatever button and get that vibrating acknowledgement, but nothing happens. I will be in the app menu and wish to exist and the home button just does not respond.
Yesterday I missed a call because the bloody phone just did not respond, even though I touched the answer button. Other times I just can not make a call. I dial number, and the phone just sits there doing nothing. Eventually I just pull out the battery and restart the phone to make a simple bloody call. I had a HTC WinMo phone for years and never once experienced this. No matter how farked the OS could get with some app or whatever, the phone function always worked.
I do not run a lot of apps, and recently have experienced these issues with almost literally no apps installed. I will then add something like GO taskmanger just to confirm that the unresponsive behavior is not due to some app taking up memory/CPU etc..
Sorry for the long post, but I am at my wits end with this bloody phone. The fact that I miss calls when the **** phone is right in my hand is unacceptable. So before placing this phone in a box filled with C4 and shooting this to the moon, hoping that maybe a solution is out there.
p.s. I have 2 Infuse in use, both have the same issue.
Click to expand...
Click to collapse
You know, for the rather lengthy post, you really have not explained any detail about your issue.. You have a generic 'I have an issue, the Infuse sucks' post and its not going to help anyone resolve your issue. I find it EXTREMELY hard to believe that you have 2 infuses having the SAME EXACT ISSUE. Yes, there will be times when you get a defective phone or it isnt working up to your standards, but to have 2 defective phones with the same defect? You need to play the lottery. Also, i suggest you send the phones back. It sounds like youve already made your mind up and have pretty much bashed the samsung infuse in that entire post. The same samsung infuse that myself, and plenty of other people live with day to day and have absolutely 0 complaints.
I will give you $20.00 a piece for them!!!!
ssa2204 said:
Been contemplating for a while whether to post this as it will come off as rather trollish. Had my Infuse for over a year now. When I first got it I noticed there were some "issues". I remained patient hoping or thinking maybe when GB was released it would improve. It did not. Later I needed to root this phone and came here, found a ROM that had all the AT&T junk stripped out. Phone worked better, but still had these issues.
I got to the point that I knew I would never again purchase either a Samsung phone or Android. Did not know what the culprit was. Just recently I had the chance to really take a look at an HTC EVO, and I realized that Samsung is the problem, not Android.
Number one issue is that this phone is sluggish, and sometimes unresponsive. I will touch whatever button and get that vibrating acknowledgement, but nothing happens. I will be in the app menu and wish to exist and the home button just does not respond.
Yesterday I missed a call because the bloody phone just did not respond, even though I touched the answer button. Other times I just can not make a call. I dial number, and the phone just sits there doing nothing. Eventually I just pull out the battery and restart the phone to make a simple bloody call. I had a HTC WinMo phone for years and never once experienced this. No matter how farked the OS could get with some app or whatever, the phone function always worked.
I do not run a lot of apps, and recently have experienced these issues with almost literally no apps installed. I will then add something like GO taskmanger just to confirm that the unresponsive behavior is not due to some app taking up memory/CPU etc..
Sorry for the long post, but I am at my wits end with this bloody phone. The fact that I miss calls when the **** phone is right in my hand is unacceptable. So before placing this phone in a box filled with C4 and shooting this to the moon, hoping that maybe a solution is out there.
p.s. I have 2 Infuse in use, both have the same issue.
Click to expand...
Click to collapse
Simple . Hack it and put cm7 on it if you really need speed. Maybe its your screen protecter. Wipe the screen off. Cm9 can be sluggish, for speed go to miui on gingerbread or cm7
Id be willing to buy one of the infuses
Trust me...sounds like you got two defective units...which like Scott, I find hard to believe...but hey its possible-idk when you got hem.but if it hasn't been a year then put them back to stock with gtgs unbrick and file a warranty claim with Samsung...the infuse is a great phone and I never had the problem you described...I do have a question though...did you get them both at the same time? Cause I don't see why you would get a second if your first was having problems
Anyways...if you wanna sell one hmu...I may buy one depending on the price and if I can get the money (I think I already may have one lined up for $170 just need to get the money)
Sent from my HTC PH39100 using xda app-developers app
Never really had any problems with samsungs beside the only issue I have ever had with ALL Samsung phones .. They have the worst RF signal/strength out of any company! I miss the days of my old Nokia RF ..
Sent from my SAMSUNG-SGH-I997 using xda app-developers app
Android Law #1: Costum ROMs are ALWAYS 10x better than stock.
Wow an i cant find one issue. Always great signal never inresponsive u sure u have an infuse
Sent from my SGH-I997 using xda premium
Prometh1216 said:
Wow an i cant find one issue. Always great signal never inresponsive u sure u have an infuse
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
Hehehe, what ROM u running?
Sent from my SAMSUNG-SGH-I997 using xda premium
qkster said:
What firmware are you running?
Click to expand...
Click to collapse
One is using the GB posted by jscott30 here, the other is the plain official Samsung GB via Kies. Mine is then UCLB3
qkster said:
Is it the same firmware on both phones?
Click to expand...
Click to collapse
No
qkster said:
What is the launcher?
Click to expand...
Click to collapse
Both stock
qkster said:
Have you tried a different modem?
Click to expand...
Click to collapse
No, thought never occurred to me that I should look at this as a solution.
qkster said:
Are you using a battery saver like juice defender?
Click to expand...
Click to collapse
Neither.
qkster said:
Are you using an ad blocker?
Click to expand...
Click to collapse
Nope
qkster said:
Are you using a specific kernel? Oc? Uv?
Click to expand...
Click to collapse
2.6.35.7-I997RUXK53-CL366622 for mine (GB rooted ROM) the other would be whatever came with the official Samsung GB release.
qkster said:
Need for specific info
Click to expand...
Click to collapse
Again this has been a recurring problem since purchase, and during this time I have had stock Froyo, rooted Froyo ROM, GB update, and for one now a the GB rooted ROM.
When the slow to unresponsiveness occurs there does not appear to be any specific cause. Prior to updating to the rooted GB I had used GO Taskmanager, and long before that some other app I long since forgot the name of. Point was that they had shown that neither CPU was excessive, or memory was used up. Both phones have data services disabled and are strictly Wifi only. There are no tasks or extra programs run in the background (though did install Connectbot today). I no longer use any Live wallpaper. After updating to the rooted GB I left the phone in that state (no software installed) for a week or so, and the problem still occured.
This occurs when calling or answering calls, but as previously posted occurs sometimes just opening the Applications menu as an example. So it is not a specific task or program that is slow or unresponsive. Earlier this evening I got a call, slide the bar across to answer and the screen just hung there for a few moments. This time it was at least not long enough that I missed the call. When the call was done I looked and there simply was nothing running on the phone. No apps, no web browser or mail, in fact I was not even connected to the wifi (I have data 3G/4G service disabled on the phone).
are you completely wiping before every flash youve done? have you tried a complete wipe and start from fresh?
ssa2204 said:
One is using the GB posted by jscott30 here, the other is the plain official Samsung GB via Kies. Mine is then UCLB3
No
Both stock
No, thought never occurred to me that I should look at this as a solution.
Neither.
Nope
2.6.35.7-I997RUXK53-CL366622 for mine (GB rooted ROM) the other would be whatever came with the official Samsung GB release.
Again this has been a recurring problem since purchase, and during this time I have had stock Froyo, rooted Froyo ROM, GB update, and for one now a the GB rooted ROM.
When the slow to unresponsiveness occurs there does not appear to be any specific cause. Prior to updating to the rooted GB I had used GO Taskmanager, and long before that some other app I long since forgot the name of. Point was that they had shown that neither CPU was excessive, or memory was used up. Both phones have data services disabled and are strictly Wifi only. There are no tasks or extra programs run in the background (though did install Connectbot today). I no longer use any Live wallpaper. After updating to the rooted GB I left the phone in that state (no software installed) for a week or so, and the problem still occured.
This occurs when calling or answering calls, but as previously posted occurs sometimes just opening the Applications menu as an example. So it is not a specific task or program that is slow or unresponsive. Earlier this evening I got a call, slide the bar across to answer and the screen just hung there for a few moments. This time it was at least not long enough that I missed the call. When the call was done I looked and there simply was nothing running on the phone. No apps, no web browser or mail, in fact I was not even connected to the wifi (I have data 3G/4G service disabled on the phone).
Click to expand...
Click to collapse
Task manager is NOT the best app to tell you what is running in the background.
Maps and other location apps may not be listed but will consume resourse that can be the cause of your lag.
The fact that stopping wallpaper or live wall paper off alleviate the condition may suggest that the phone is running at max capacity. Steps to reduce the load improves it. Live wp, facebook, maps, stock email and other device manager from stock att was one of the first @#$% I took out on any rom I run.
Having a large amount of apps installed can also cause this lag. The OS may only be able to handle so many.
Have a poor signal at the time of the call may also be an issue, especially if both of your phones have this issue occasionally but not consistently.
Lock screen can also be a factor. Some sleep setting may also cause the phone to wake up poorly. I get around this by turning off my lock screen. On the call settings, you can also change the answering options so that it will override others and make it easy to answer.
On any firmware - stock or modded, after you have the phone running for an extended period of time without a reboot, you may start to see some lags. This may be across all devices. You may need to reboot it occasionally or boot into recovery and wipe the cache.
These issues may or not go away once you have a device with more power or resources..ex: dual or quad core, 1gb or 2gb ram etc..my guess is when a device has more power, programmers will come up with more resourse intensive apps that may hinder the phone as well.
Lastly, pay attention to your battery meter. As the power dips below 30%, there are steps taken by the OS to conserve the battery. This may give you lags as well..possibly one of the reason why it seems random also.
If you wanted to test out the lag issue due to background apps, go to settings/account and sync. turn off background data. You will retain the (radio) phone and text but there will be no email/facebook, weather, widgets/market/amazon etc updates unless you manually update them. If this runs smoothly but lags when you turn it back on, you can start the process of narrowing down your culprit.
gl
****************UPDATE AGAIN
My phone number only seems to switch when I'm under "NV" for my CDMA subscription. It appears to be randomly switching back to NV periodically. If I put it in airplane and switch it back, it will correct my phone number and allow some messages to be sent. Any info on what settings should be there how to keep that from switching or any other info regarding this?
My phone number is currently showing up as 000-000-3720
My MIN is currently showing up as 0000003720
I do have a IMEI and MEID
Hello,
I have had two issues with the galaxy s3 since I got it. I never had any problems with my gnex but gs3 is killing me.
1. When I download AOSP roms like liquid smooth and mrom, the phone randomly will not send text messages and will frequently go into roaming. Even if it says I have 4g, it will still not always send text messages. Then it will randomly be fine for about 45 minutes and then go back into crap mode.
2. When I download touchwiz roms, everything appears to look normal and I have no problems with my phone calls or messages not sending, BUT my phone likes to randomly reboot when opening apps and especially with sending messages. I can reproduce the problem several times over by sending a text message.
Both seem to be sms related. But in many ways seem completely unrelated. Any ideas on what is going on?
Thanks
Bryan
boconnor341 said:
Hello,
I have had two issues with the galaxy s3 since I got it. I never had any problems with my gnex but gs3 is killing me.
1. When I download AOSP roms like liquid smooth and mrom, the phone randomly will not send text messages and will frequently go into roaming. Even if it says I have 4g, it will still not always send text messages. Then it will randomly be fine for about 45 minutes and then go back into crap mode.
2. When I download touchwiz roms, everything appears to look normal and I have no problems with my phone calls or messages not sending, BUT my phone likes to randomly reboot when opening apps and especially with sending messages. I can reproduce the problem several times over by sending a text message.
Both seem to be sms related. But in many ways seem completely unrelated. Any ideas on what is going on?
Thanks
Bryan
Click to expand...
Click to collapse
Try turning off vibrate for notifications - it works in one older JB build.
jefmoody1 said:
Try turning off vibrate for notifications - it works in one older JB build.
Click to expand...
Click to collapse
Ill try that when the issue starts back up again. Right now I'm asymptomatic.
Anyone have this issue or possible solutions to either of the above or a reason why this might be occurring?
Thanks
jefmoody1 said:
Try turning off vibrate for notifications - it works in one older JB build.
Click to expand...
Click to collapse
I tried to do it when it started up again. Its going into roaming again.
****************UPDATE
My phone number is currently showing up as 000-000-3720
My MIN is currently showing up as 0000003720
I do have a IMEI and MEID
boconnor341 said:
Hello,
I have had two issues with the galaxy s3 since I got it. I never had any problems with my gnex but gs3 is killing me.
1. When I download AOSP roms like liquid smooth and mrom, the phone randomly will not send text messages and will frequently go into roaming. Even if it says I have 4g, it will still not always send text messages. Then it will randomly be fine for about 45 minutes and then go back into crap mode.
2. When I download touchwiz roms, everything appears to look normal and I have no problems with my phone calls or messages not sending, BUT my phone likes to randomly reboot when opening apps and especially with sending messages. I can reproduce the problem several times over by sending a text message.
Both seem to be sms related. But in many ways seem completely unrelated. Any ideas on what is going on?
Thanks
Bryan
Click to expand...
Click to collapse
I feel for you. I ruined my first S3 by downloading CM10.1. Never had issues with Galaxy Nexus. S3 is wonky when it comes to AOSP based roms (i.e, speakerphone echo, may lose MEI when flashing, AOKP ms 1 has occasional issues with sudden failed bluetooth connection issues in car, all Jellybean 4.2.1 AOSP based roms seems to have issues with cutting off streaming when traveling in your car via using iHeartRadio). I never had any of these issues with my Galaxy Nexus. When a better phone comes out, I will ditch this S3 fast for a phone that works better with custom AOSP roms. I sometimes long for my old Galaxy Nexus.
sghrush said:
I feel for you. I ruined my first S3 by downloading CM10.1. Never had issues with Galaxy Nexus. S3 is wonky when it comes to AOSP based roms (i.e, speakerphone echo, may lose MEI when flashing, AOKP ms 1 has occasional issues with sudden failed bluetooth connection issues in car, all Jellybean 4.2.1 AOSP based roms seems to have issues with cutting off streaming when traveling in your car via using iHeartRadio). I never had any of these issues with my Galaxy Nexus. When a better phone comes out, I will ditch this S3 fast for a phone that works better with custom AOSP roms. I sometimes long for my old Galaxy Nexus.
Click to expand...
Click to collapse
There are certainly positives and negatives, but at this point the phone is unusable at times and I almost feel like it was a waste "upgrading". .
The issue exists with Touchwiz roms as well in that it reboots rather than go into roaming or fail to exchange data/txts.. Nobody has had this issue? I find it hard to believe I'm the only known case of this. Anyone have something similar or any options?
Could I benefit from starting completely over from stock? Anyone with knowledge pertaining to this would be greatly helpful.
Thanks
boconnor341 said:
There are certainly positives and negatives, but at this point the phone is unusable at times and I almost feel like it was a waste "upgrading". .
The issue exists with Touchwiz roms as well in that it reboots rather than go into roaming or fail to exchange data/txts.. Nobody has had this issue? I find it hard to believe I'm the only known case of this. Anyone have something similar or any options?
Could I benefit from starting completely over from stock? Anyone with knowledge pertaining to this would be greatly helpful.
Thanks
Click to expand...
Click to collapse
updated again
Dear All.
My samsung galaxy s2 skyrocket had been working with ParanoidAndorid (v 2.55) for 2 months without problems, but since a week ago I couldn't place regular calls. I can dial the numbers and receive calls, but in neither case I can hear any sound. The rest of the functions work just fine (youtube, chrome, etc). After checking for sound configurations, such as noise reduction, the problem persisted. I have to say that the problem goes away after rebooting the system, but is happens again at random times. I've change to Cyanogenmod 10, but the situation holds.
I noted that two apps seems to be producing this problem: Viber and Line. Immediately after I receive a Viber/Line call the problem arises. This is strange as I've been using Viber from the beginning, but the problem has been happening only from last week.
I would appreciate any suggestions. Thanks in advance
Contact the app DEV and provide him some logs. It's not the phone from what you're describing.
hechoen said:
Contact the app DEV and provide him some logs. It's not the phone from what you're describing.
Click to expand...
Click to collapse
I'll try using the phone without Viber/Line for a couples of days just to be sure that is a app-driven problem. Given the popularity of these apps, I would be surprised if this is only happening to me.
Did the app update recently? I'd unistall it then clear caches and reboot. If the problem goes away it's the app.
Hi @MarceloR -
I am a rep. of Viber here on XDA.
Thanks for sharing the details of the problem.
First, please note that Viber does not officially support your device, s2 skyrocket (here is the full list of fully compatible devices: http://bit.ly/Hm5k9p). Furthermore, we (Viber) don't claim to fully support devices with Custom ROMs, since it is impossible for us to adapt our app with all of the Custom ROMs out there.
Both these issues may be the sorurce of the problem you're experiencing. Have you tested this issue on Stock ROM on your device? (though it's not fully supported).
Having said that, the problem still sounds odd - Viber should not affect your ability to use your phone for regular calls.
Same problem, different software
I'm having the same issue - no mic, no sound on phone calls. I do not have either of the above-mentioned apps installed. I'm running CM10.1, though (Rogers). Tried installing the CLI3 modem, and the stock Rogers modems to see if that might help.
I did notice that the ear speaker was getting quite hot when I tried to use the phone, and the phone app itself is performing tremendously slow.
If anyone has thoughts / suggestions about how to fix this, I'd really appreciate it.
It's a common issue and has nothing to do with Viber, i've never used it personally.
This has happened to me on all kinds of roms stock, custom and AOSP.
Usually, when it happens, it happens after or while i am running an app that uses audio. Like any video / audio player and games.
It's not that big of a bother since it doesn't happen too often, but just embarassing.. when you've payed some $300+ for a phone and it doesn't even make phone calls lol. Might as well have bought one for $20 that does.
My point is i want to know a reason or explanation for this if someone can offer one.
Update: pulled SIM card, battery. Reboot, shut down, insert SIM card. Everything works again. Using the same 3/3 nightly. No other changes.
lingowistico said:
It's a common issue and has nothing to do with Viber, i've never used it personally.
This has happened to me on all kinds of roms stock, custom and AOSP.
Usually, when it happens, it happens after or while i am running an app that uses audio. Like any video / audio player and games.
It's not that big of a bother since it doesn't happen too often, but just embarassing.. when you've payed some $300+ for a phone and it doesn't even make phone calls lol. Might as well have bought one for $20 that does.
My point is i want to know a reason or explanation for this if someone can offer one.
Click to expand...
Click to collapse
Common for whom I don't have these issues. I swear how do you guys have all of these crazy problems.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Common for some..
http://forum.xda-developers.com/showthread.php?t=2168656
http://forum.xda-developers.com/showthread.php?p=39678817
@lingowistico -
Thank you for sharing this valuable information, that will help us aide our users as well.
If you have any news in this matter, please do let us know
lingowistico said:
Common for some..
http://forum.xda-developers.com/showthread.php?t=2168656
Click to expand...
Click to collapse
I circumvented this problem by installing an old version of viber (one from Dec 2012). I found the old version here: http://www.androiddrawer.com/
So far, no problems. Everything seems to be back to normal.