Related
there were a lot of posts (including one of mine) where people complained that when data network mode was activated and they tried to answer / make a call, they couldn't. and if they did try to, it wouldn't answer and the network bars would become grey (that is, no bars) and it would take a couple of minutes for network to come back (or until you restart, whichever comes first).
anyway, i had some issues with my phone and i gave to the service center. i told them of it and they flashed the stock ROM + kernel. i had some other issues as well, so they said they'll keep the phone for two days.
so i'm getting my phone back tomorrow. now i want to know if flashing the stock firmware did in fact solve anyone's issues. if it did, i'll continue with the stock rom / kernel (please tell me which was causing you the problems). if not, i'll flash a custom ROM / kernel again. please let me know.
also, does anyone know why this happens? is some app causing these problems? because after flashing a new custom ROM (without any user apps installed) i can call / receive properly without deactivating the data network mode.
but, no user apps (and no google account sync either) = no internet traffic.
i'd request the expert devs (ROM makers, kernel developers, testers etc) to please leave their opinion as i'm not the only one who faces this issue. a few of us do and this is one of the few unsolved issues on this forum.
thank you.
Mohit12 said:
there were a lot of posts (including one of mine) where people complained that when data network mode was activated and they tried to answer / make a call, they couldn't. and if they did try to, it wouldn't answer and the network bars would become grey (that is, no bars) and it would take a couple of minutes for network to come back (or until you restart, whichever comes first).
anyway, i had some issues with my phone and i gave to the service center. i told them of it and they flashed the stock ROM + kernel. i had some other issues as well, so they said they'll keep the phone for two days.
so i'm getting my phone back tomorrow. now i want to know if flashing the stock firmware did in fact solve anyone's issues. if it did, i'll continue with the stock rom / kernel (please tell me which was causing you the problems). if not, i'll flash a custom ROM / kernel again. please let me know.
also, does anyone know why this happens? is some app causing these problems? because after flashing a new custom ROM (without any user apps installed) i can call / receive properly without deactivating the data network mode.
but, no user apps (and no google account sync either) = no internet traffic.
i'd request the expert devs (ROM makers, kernel developers, testers etc) to please leave their opinion as i'm not the only one who faces this issue. a few of us do and this is one of the few unsolved issues on this forum.
thank you.
Click to expand...
Click to collapse
ur last custom rom??? wer u using 3g turbocharger??
frankly i don't know what 3g turbocharger is :/
i was using kyrillos' ROM 8.0 (updated to 8.1) and i did run the supercharger script, but i don't think that's what you're talking about. i wasn't using the 3g network.
i've been facing this issue for a LONG time now. i've changed a few ROMs but same effect in all of them. maybe it's something to do with the european firmware (i live in mumbai, india) or something, i'm not sure. are you on vodafone? where in india do you stay?
Well even i am facing this strange network problem but only indoors!!
Outdoors the range is full!!
Since we all flash custom roms that are based on european base, i thought that the problem is related to the modem.bin AKA baseband!!
So i was thinking of just flashing the modem.bin again from any asian firmware.
But before doing that i flashed the old ddjg6 (eclair) rom just to see if baseband flashing is worth it.
Well the network problem was still there!! so the conclusion was that baseband/modem.bin flashing wont affect anything!!
stay happy!!
I cant remember if kyr8 had 3g turbocharger tweaks on build.prop.. But yes with 3g turbocharger on , I hav sum issues with data connection...
-tapatalked by RnB
Btw did u get phone.apk force close while happenin this??
-tapatalked by RnB
phone.apk force closed often. but never because of the weird data connection. i think it just generally force closed.
and i have been facing this problem since kyrillos' 6.0 or 7.0. one of the two. can't remember. also, please look for my "a request for a custom lock screen?" thread in galaxy 3 general and let me know if you can help. thanks!
also, people who are facing such issues please leave your name and "symptoms" here.
yes i also face the same problem of network,no solutions found yet.but i am not sure whether this prob happens to all the network or just VODAFONE,as i am using VODAFONE only.
okay please visit this thread :
http://forum.xda-developers.com/showthread.php?t=1229423&highlight=data+network+mode&page=2
also, here's a bit of my network story if it helps anyone understand this issue :
i bought the phone when it was running Eclair. it worked fine for a few days then i started to face the issue. when i tried sliding the green answering thing to the right, it just wouldn't answer. it would go back in it's place. when people called me, it said it was unavailable. my network used to restart, and calls would randomly get cut and i couldn't call back immediately. i had to wait for 10-15 seconds before i could make / receive any call again. within this time, the calls would dial, but not connect.
so i upgraded to froyo (JP2) from the samsung gallery. my phone worked PERFECTLY for two months or so. no call drops, no nothing. then all of the above started happening again.
i tried flashing different ROMs, kernels etc but nothing helps.
and neo, i face this problem everywhere. indoors and outdoors.
okay so i'm getting my phone back tomorrow. does anyone have any tips for me? something that i should or should not do? like flash a european ROM or just the kernel or not to install a specific app or something?
i do have the same situation. it worked very good by me, till marcellusbe released his cm7 alpha4 i think. i installed it, and since then i have got that network problem, during calls f. example i lose the communication. i dont hear amything, it freezes, and turns back to menu after a few seconds. then i notice that its in the flight mode automatically. and this just happens me when i have got the data connections on. if i deactivate it i dont face any problems like that. i also noticed since i once installed cm7 alpha4 , i have got a strange battery drain. i charg the phone till its fully cjarged, after 3 hours i do not have any battery any more.. help me in that ... PLEASE
i really become frustated the whole time when this happens to me, pls find a solution!! ....
Sent from my GT-I5800 using the XDA mobile application powered by Tapatalk
Try fixin permissions from cwm recovery..
Btw do u use adfree ??
-tapatalked by RnB
Mohit12 said:
okay please visit this thread :
http://forum.xda-developers.com/showthread.php?t=1229423&highlight=data+network+mode&page=2
also, here's a bit of my network story if it helps anyone understand this issue :
i bought the phone when it was running Eclair. it worked fine for a few days then i started to face the issue. when i tried sliding the green answering thing to the right, it just wouldn't answer. it would go back in it's place. when people called me, it said it was unavailable. my network used to restart, and calls would randomly get cut and i couldn't call back immediately. i had to wait for 10-15 seconds before i could make / receive any call again. within this time, the calls would dial, but not connect.
so i upgraded to froyo (JP2) from the samsung gallery. my phone worked PERFECTLY for two months or so. no call drops, no nothing. then all of the above started happening again.
i tried flashing different ROMs, kernels etc but nothing helps.
and neo, i face this problem everywhere. indoors and outdoors.
okay so i'm getting my phone back tomorrow. does anyone have any tips for me? something that i should or should not do? like flash a european ROM or just the kernel or not to install a specific app or something?
Click to expand...
Click to collapse
Well if flashing customs roms and kernels is not helping, you need to try only flashing the stock modem.bin!! I really dont know how to do that safely but people do it!! If you can update the OP like "Please help in flashing just modem.bin" then maybe someone makes and give you an update.zip or a tar containing just modem.bin.
If that too fails to solve your problem, then you must demand a replacement of the handset from samsung! Thats all i can say man!!
Well, the same is happening with me. Even i have vodafone and i live in pune, india. I didnt use eclair for alot of of time so I don't know whether it is a froyo-eclair prob.
The problem that happens with me is that, when i go to my classes (which are in a damn closed area) i dont get any signal. Even though the network bars are zero i still get messeages and phone calls. but when i call someone or message it does not reach. It only happens in some places like my classes and school, but not at my house.
I found a way (not quite conventional but works). I have found that when i flash a rom; irrespective of whether stock or custom; the signal catching is quite stong. But after a month or two it is becomes laggy again. So i flash another rom and again it's good. I dont know whether it is a correct method but works for me.
ak700 said:
Well, the same is happening with me. Even i have vodafone and i live in pune, india. I didnt use eclair for alot of of time so I don't know whether it is a froyo-eclair prob.
The problem that happens with me is that, when i go to my classes (which are in a damn closed area) i dont get any signal. Even though the network bars are zero i still get messeages and phone calls. but when i call someone or message it does not reach. It only happens in some places like my classes and school, but not at my house.
I found a way (not quite conventional but works). I have found that when i flash a rom; irrespective of whether stock or custom; the signal catching is quite stong. But after a month or two it is becomes laggy again. So i flash another rom and again it's good. I dont know whether it is a correct method but works for me.
Click to expand...
Click to collapse
Same place!! Pune!! But i get the problem only in some areas!!!
okay so i've been using the stock firmware for two-three days now. and i've been facing absolutely no network problem as such.
when i press *#1234# here are my results :
PDA : i5801DDJP2
phone : i5801DDJP2
CSC : i5801DDJP2
build info : 2011, 04
now can someone interpret this for me? i mean tell me what exactly this means. which of those is my ROM build, my kernel build, or baseband or whatever.
tell me if there are any custom ROMs / kernels built on these builds (or updated ones, but still indian updates) so that i can test if those work for me?
thanks.
Mohit12 said:
okay so i've been using the stock firmware for two-three days now. and i've been facing absolutely no network problem as such.
when i press *#1234# here are my results :
PDA : i5801DDJP2
phone : i5801DDJP2
CSC : i5801DDJP2
build info : 2011, 04
now can someone interpret this for me? i mean tell me what exactly this means. which of those is my ROM build, my kernel build, or baseband or whatever.
tell me if there are any custom ROMs / kernels built on these builds (or updated ones, but still indian updates) so that i can test if those work for me?
thanks.
Click to expand...
Click to collapse
There is no custom rom build on this build as this build is lot buggy than the other european firmwares.
And that phone is the baseband responsible for the network and all!!
Some people face network problems some dont!!
Here is the phone of i5801ddjp3 firmware
http://www.mediafire.com/?34yrw4b7fe63tri
If you unzip this file, you get the modem.bin
Now there has to be a way to flash this modem.bin over custom firmwares!!
here is the sgs version of it!! This thread contains of all modem.bin of stock firmware to be flashed over custom rom to get better baseband for samsung galaxy s!
Even I used to face similar problem but only on custom rom's not on stock ones.. but using the stock rom's is too boring so now I have flashed with purungrit's rom v.1.0, kernel G3 mod 2.0, and its working fine, no network issues. The theme is good with extended power menu and 5 lockscreen.. u can try this. we can flash custom rom's based on Indian firmwares and face no network problems, problem is only with European or other countries firmwares..
Sent from my GT-I5801 using XDA App
pavankadam said:
Even I used to face similar problem but only on custom rom's not on stock ones.. but using the stock rom's is too boring so now I have flashed with purungrit's rom v.1.0, kernel G3 mod 2.0, and its working fine, no network issues. The theme is good with extended power menu and 5 lockscreen.. u can try this. we can flash custom rom's based on Indian firmwares and face no network problems, problem is only with European or other countries firmwares..
Sent from my GT-I5801 using XDA App
Click to expand...
Click to collapse
But the problem is that indian firmwares are a bit inferior as compared to european firmwares.. If you compare any indian firmware with jpq or jpu you will feel the difference..
I really want someone to try that modem.bin method
Tapatalked from my awesome G3 aka apollo
Ask some of the devs that whether this method can be used n is it safe.. than we can go for it.
Sent from my GT-I5801 using XDA App
pavankadam said:
Ask some of the devs that whether this method can be used n is it safe.. than we can go for it.
Sent from my GT-I5801 using XDA App
Click to expand...
Click to collapse
Yup!! right now i am fighting my exams!!
If somebody can do it!! ;-)
Hi !
(First of all, I apologize for my english)
I just tried to install the last NovaHD's release on my Optimus 2X P990 device (http://forum.xda-developers.com/showthread.php?t=1508492) but my touchscreen now doesn't respond at all, when I have to unlock my SIM.
I tried also to format and re-install CM7 and a other kernel, but the problem stay the same.
I have no idea of where it comes from, do you have a idea of how fix it ?
It is mostly likely a faulty rom. No way of fixing this unless you contact the developer.
So you've installed multiple roms and the problem still persists? You sure its not your digitizer?
How the screen is drivered ? By kernel or ROM, or anything else ?
It can't be a fautely ROM, I tried also to go back on my previous CM, which always have been working.
I don't know where it can come from. I format and wipe everything, but it stays desperately locked.
It seems others users had the problem on the first version of the ROM (http://forum.xda-developers.com/showpost.php?p=23061913&postcount=420); but normally, it doesn't affect the users of the curent version.
Does the kernel's affected by the format, or it is stocked on anything else ?
PakAttack1994 > That would be a great coincidence... I don't think it's dead.
EDIT 28/03 > I try to install a stock ROM.
EDIT > Returned to LG.
I have had Bean's Jelly 'Beans' ROM installed on my GS3 since I first got the phone in October. Verizon had to replace my phone this past week, and once I received the new one, I did the customary procedure of rooting it and installing a custom ROM. However, after I install a ROM, the Camera always breaks (I get the message "Camera Failed" and the camera screen is black when I open the stock camera app).
I have already researched the issue, and it seems there is a history of some S3's coming out of the box with a broken camera, but it is important to note that the camera works fine as long as I revert back to the stock (and rooted) rom. When installing the Jelly 'Beans' ROM, I have selected 4 different kernel options(Beans custom stock, imoseyon lean kernel, ktoonsez, and faux kernel), thinking that may be the issue, but each one still leaves a broken camera. I have also tried installing an aftermarket camera app, in case the S3 camera apk is somehow broken, and have flashed the Photosphere Camera. Nothing will get the camera to work (and yes, my battery is fully charged).
Not being able to install a custom ROM is a pretty big deal to me, and not having a working camera is a deal breaker. Unfortunately, I won't be able to get Verizon to replace the phone again since it all works on the stock ROM. Does anyone have any ideas? I have tried several things I have read in the forums, but nothing has worked so far. Thank you all in advance for your help!
tfc87 said:
I have had Bean's Jelly 'Beans' ROM installed on my GS3 since I first got the phone in October. Verizon had to replace my phone this past week, and once I received the new one, I did the customary procedure of rooting it and installing a custom ROM. However, after I install a ROM, the Camera always breaks (I get the message "Camera Failed" and the camera screen is black when I open the stock camera app).
I have already researched the issue, and it seems there is a history of some S3's coming out of the box with a broken camera, but it is important to note that the camera works fine as long as I revert back to the stock (and rooted) rom. When installing the Jelly 'Beans' ROM, I have selected 4 different kernel options(Beans custom stock, imoseyon lean kernel, ktoonsez, and faux kernel), thinking that may be the issue, but each one still leaves a broken camera. I have also tried installing an aftermarket camera app, in case the S3 camera apk is somehow broken, and have flashed the Photosphere Camera. Nothing will get the camera to work (and yes, my battery is fully charged).
Not being able to install a custom ROM is a pretty big deal to me, and not having a working camera is a deal breaker. Unfortunately, I won't be able to get Verizon to replace the phone again since it all works on the stock ROM. Does anyone have any ideas? I have tried several things I have read in the forums, but nothing has worked so far. Thank you all in advance for your help!
Click to expand...
Click to collapse
I'm going to go ahead and help myself out and respond to my own question. Upon even further research (yes, I know everyone says people don't look hard enough), I believe the issue relates to the Firmware version. Supposedly the newest firmware breaks the camera unless it's on the stock rom. There are modified firmwares out there that change the part that breaks the camera, but I believe I am going to downgrade the modem and all from what was pre-installed and see if it works.
tfc87 said:
I'm going to go ahead and help myself out and respond to my own question. Upon even further research (yes, I know everyone says people don't look hard enough), I believe the issue relates to the Firmware version. Supposedly the newest firmware breaks the camera unless it's on the stock rom. There are modified firmwares out there that change the part that breaks the camera, but I believe I am going to downgrade the modem and all from what was pre-installed and see if it works.
Click to expand...
Click to collapse
if its a custom Rom (Stock but maby some extras such as overclocking or somethin) they are Sometimes Broken They will try to fix it sometimes, upgrading to a higher android version it is sometimes is Quite hard to Fix everything.
Trozzul said:
if its a custom Rom (Stock but maby some extras such as overclocking or somethin) they are Sometimes Broken They will try to fix it sometimes, upgrading to a higher android version it is sometimes is Quite hard to Fix everything.
Click to expand...
Click to collapse
I downgraded the firmware to VRBMB1 and went back to that custom rom and the camera works flawlessly. I read in the firmware forum that the new firmware is doing this to a lot of people...I just happened to have one of the phones that came with it pre-installed. Problem solved and hopefully this post will help someone out...if not...it helped myself out at least.
tfc87 said:
I downgraded the firmware to VRBMB1 and went back to that custom rom and the camera works flawlessly. I read in the firmware forum that the new firmware is doing this to a lot of people...I just happened to have one of the phones that came with it pre-installed. Problem solved and hopefully this post will help someone out...if not...it helped myself out at least.
Click to expand...
Click to collapse
maby just wait till next firmware and they will fix it?
Trozzul said:
maby just wait till next firmware and they will fix it?
Click to expand...
Click to collapse
Yeah I'm sure it will be fixed. Either way, I don't recommend that newest firmware...signal seems to be the worst out of all of the ones I've tried...for me at least. Seems to be a lot of complaints out there with it anyways.
Similiar issue?
I am having a similiar issue with my US Cell GS3. I bought the donor version of mskip's Samsung Galaxy S3 Unified Toolkit and rooted my device yesterday now my camera is doing the same thing...fires up to a black screen, hangs a few seconds then says camera failed. I'm running Android 4.1.2, build R530UVXAMD4. I've read in a few places that I may have to either downgrade my kernel or flash with some sort of alternate firmware.
Any assistance provided is greatly appreciated!
Sterling8356 said:
I am having a similiar issue with my US Cell GS3. I bought the donor version of mskip's Samsung Galaxy S3 Unified Toolkit and rooted my device yesterday now my camera is doing the same thing...fires up to a black screen, hangs a few seconds then says camera failed. I'm running Android 4.1.2, build R530UVXAMD4. I've read in a few places that I may have to either downgrade my kernel or flash with some sort of alternate firmware.
Any assistance provided is greatly appreciated!
Click to expand...
Click to collapse
did you figure this out?
im having same problem
I had the same problem while flashing one of my friend's S3...i just did the whole process once again..and everything works fine
Sent from my Galaxy Note II using xda premium
tfc87 said:
I have had Bean's Jelly 'Beans' ROM installed on my GS3 since I first got the phone in October. Verizon had to replace my phone this past week, and once I received the new one, I did the customary procedure of rooting it and installing a custom ROM. However, after I install a ROM, the Camera always breaks (I get the message "Camera Failed" and the camera screen is black when I open the stock camera app).
I have already researched the issue, and it seems there is a history of some S3's coming out of the box with a broken camera, but it is important to note that the camera works fine as long as I revert back to the stock (and rooted) rom. When installing the Jelly 'Beans' ROM, I have selected 4 different kernel options(Beans custom stock, imoseyon lean kernel, ktoonsez, and faux kernel), thinking that may be the issue, but each one still leaves a broken camera. I have also tried installing an aftermarket camera app, in case the S3 camera apk is somehow broken, and have flashed the Photosphere Camera. Nothing will get the camera to work (and yes, my battery is fully charged).
Not being able to install a custom ROM is a pretty big deal to me, and not having a working camera is a deal breaker. Unfortunately, I won't be able to get Verizon to replace the phone again since it all works on the stock ROM. Does anyone have any ideas? I have tried several things I have read in the forums, but nothing has worked so far. Thank you all in advance for your help!
Click to expand...
Click to collapse
I have had the same problem when I installed a certain custom rom (can't remember the name ) on my s3. But later I found that during installation of the rom, there was an option to choose one of four kernels, and if I chose Boeffla kernel (included in the options) my camera wouldn't work. So I just reverted back to the stock kernel and walah! My camera works again.
Hi all,
I've just bought a new SII Skyrocket to replace my Motorola Bravo -- the bravo was terrible purchase and though the Skyrocket is a two year-old phone I consider this a big step up.
I bought the phone on eBay and it was advertised as new. It arrived in its original packaging with the security seal intact, so I have no reason to doubt this. The phone is running ICS (4.0.4 build IMM76D.UFCLF6).
The phone arrived yesterday and I really like it, but I've encountered a weird issue. If I reboot the phone then it is no longer able to make any sound. Any action that requires sound -- incoming calls, outgoing calls, choosing a ringtone, playing music, taking a picture -- causes the phone to freeze for a minute or more and then become very slow. Rebooting again makes no difference. The only solution I've found is to reboot into recovery and factory reset, though this may only work after several tries.
- Has anyone heard of this issue before?
- Is it likely to be fixed by upgrading to Jelly Bean (I'll install a custom ROM if I can be sure that the phone is working properly) or is this more likely a hardware issue?
Apologies if this question has been answered before. I've searched the forums here and elsewhere, but I haven't found any mentions of similar issues.
Thanks for your help!
Try flashing a stock UCMC1 ROM and doing a factory reset after your flash finished successfully and Odin rebooted your phone.
3 things you need:
1- skyrocket windows drivers from Samsung website
2-Odin
3-stock ucmc1 tar ball.
Refer to this page:
http://forum.xda-developers.com/showthread.php?t=2228247
Good luck.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
sjbonner said:
Hi all,
I've just bought a new SII Skyrocket to replace my Motorola Bravo -- the bravo was terrible purchase and though the Skyrocket is a two year-old phone I consider this a big step up.
I bought the phone on eBay and it was advertised as new. It arrived in its original packaging with the security seal intact, so I have no reason to doubt this. The phone is running ICS (4.0.4 build IMM76D.UFCLF6).
The phone arrived yesterday and I really like it, but I've encountered a weird issue. If I reboot the phone then it is no longer able to make any sound. Any action that requires sound -- incoming calls, outgoing calls, choosing a ringtone, playing music, taking a picture -- causes the phone to freeze for a minute or more and then become very slow. Rebooting again makes no difference. The only solution I've found is to reboot into recovery and factory reset, though this may only work after several tries.
- Has anyone heard of this issue before?
- Is it likely to be fixed by upgrading to Jelly Bean (I'll install a custom ROM if I can be sure that the phone is working properly) or is this more likely a hardware issue?
Apologies if this question has been answered before. I've searched the forums here and elsewhere, but I haven't found any mentions of similar issues.
Thanks for your help!
Click to expand...
Click to collapse
You don't need to install a custom rom. Try updating to official jellybean with kies, if that doesn't work then try C64's advice above with either UCMC1 or UXUMA7 (uxuma7 is less bloated).
The issue you're having is odd and I haven't encountered it before..
lingowistico said:
You don't need to install a custom rom. Try updating to official jellybean with kies, if that doesn't work then try C64's advice above with either UCMC1 or UXUMA7 (uxuma7 is less bloated).
The issue you're having is odd and I haven't encountered it before..
Click to expand...
Click to collapse
Thanks for the suggestions, C64 and lingowistico. Upgrading to JB was going to be my next move, but I wanted to know if anybody had seen this behavior first. I don't want to mess with the phone too much in case the seller will take it back (I may be on a loser there). I'll try the official upgrade and let you know.
Custom ROM not necessary -- true, but I've been running CM on my bravo for a couple of years and can't go back to a stock ROM. I'll try the de-bloated version of the official JB release, but I'd like something I can have more control over.
Cheers...
sjbonner said:
Thanks for the suggestions, C64 and lingowistico. Upgrading to JB was going to be my next move, but I wanted to know if anybody had seen this behavior first. I don't want to mess with the phone too much in case the seller will take it back (I may be on a loser there). I'll try the official upgrade and let you know.
Custom ROM not necessary -- true, but I've been running CM on my bravo for a couple of years and can't go back to a stock ROM. I'll try the de-bloated version of the official JB release, but I'd like something I can have more control over.
Cheers...
Click to expand...
Click to collapse
when phone is doing odd things the best way to ts is a complete wipe, formatting/removing sdcards then returning to stock w/odin, but you could try the debloated rom 1st just to test it out, if its resolved then its prob not hw related, just make a backup of ur current rom if planning on returning it but since you install an official stock it should also be returnable
vincom said:
when phone is doing odd things the best way to ts is a complete wipe, formatting/removing sdcards then returning to stock w/odin, but you could try the debloated rom 1st just to test it out, if its resolved then its prob not hw related, just make a backup of ur current rom if planning on returning it but since you install an official stock it should also be returnable
Click to expand...
Click to collapse
Thanks Vincom. I don't have access to a Windows machine at the moment so haven't been able to try the upgrade.
One question -- how is it possible to make a backup of the current ROM without first rooting and installing a custom recovery? I suppose that I could install the custom ROM and create a nandroid backup. Then if I needed to restore I could restore the nandroid and reinstall the stock recovery. Is there an easier way?
Apologies, I just saw that you have information on reinstalling the stock recovery on your Newb Guide.
BTW, I want to say thanks for your work on the Newb Guide. One of the things that sold me on this phone was the support that it has here. Amazing to have all of the information on installing the custom recovery, rooting, etc. all in one place.
sjbonner said:
Hi all,
I've just bought a new SII Skyrocket to replace my Motorola Bravo -- the bravo was terrible purchase and though the Skyrocket is a two year-old phone I consider this a big step up.
I bought the phone on eBay and it was advertised as new. It arrived in its original packaging with the security seal intact, so I have no reason to doubt this. The phone is running ICS (4.0.4 build IMM76D.UFCLF6).
The phone arrived yesterday and I really like it, but I've encountered a weird issue. If I reboot the phone then it is no longer able to make any sound. Any action that requires sound -- incoming calls, outgoing calls, choosing a ringtone, playing music, taking a picture -- causes the phone to freeze for a minute or more and then become very slow. Rebooting again makes no difference. The only solution I've found is to reboot into recovery and factory reset, though this may only work after several tries.
- Has anyone heard of this issue before?
- Is it likely to be fixed by upgrading to Jelly Bean (I'll install a custom ROM if I can be sure that the phone is working properly) or is this more likely a hardware issue?
Apologies if this question has been answered before. I've searched the forums here and elsewhere, but I haven't found any mentions of similar issues.
Thanks for your help!
Click to expand...
Click to collapse
I believe I had this kinda issue once before, it was when I flashed CM10 or something. No incoming sound, sound did not work whatsoever, but installed a different kernel solved the issue, or flashing a new different rom.
econan1214 said:
I believe I had this kinda issue once before, it was when I flashed CM10 or something. No incoming sound, sound did not work whatsoever, but installed a different kernel solved the issue, or flashing a new different rom.
Click to expand...
Click to collapse
UPDATE:
So, I managed to upgrade to the official JB 4.1.2 this evening. Had to do it twice.
First time the boot got stuck at the AT&T logo and PC wouldn't detect the device. I followed the directions in another post http://forum.xda-developers.com/showpost.php?p=34682377&postcount=9 to repeat the upgrade and the same thing happened.
On a whim I decided to try rebooting a few times to see what would happen -- and it worked! Sort of...
I'm repeatedly rebooting the phone and sometimes it will start without problem. However, most of the time it gets stuck when the AT&T logo appears exactly where it should play the start up sound, except it freezes and the sound never plays.
I'm guessing that wiping the data before had nothing to do with fixing the problem and I was simply getting lucky on reboot.
I realize that this is a hard question without having the phone in hand -- but does this sound like a hardware issue?
Thanks again to everyone for their help.
Boot into recovery and factory reset from there. That should clear up the boot loop issue.
theesotericone said:
Boot into recovery and factory reset from there. That should clear up the boot loop issue.
Click to expand...
Click to collapse
Just a quick note to let you know how this was resolved. I returned the phone to the seller who provided a full refund.
Thanks again to those who respondend.:highfive:
crazy touchscreen problem
After flashing a ROM my touchscreen x axis seems to have inverted itself, so right is left on the screen.
This problem happens during the recovery screen also
I have tried changing recovery's,Kernals,flashed ROM's that I know work
I have even returned the phone back to stock nothing fixed it.
I have even went as far as removing the motherboard and installing one out of a working phone and guess what it does the same thing.
So i ask all you knowledgeable people WTF wold cause this and how can I fix it ?
these are the last two ROM's I was trying out when all this happened
they both ran without a problem I just didn't like them
MokeeOS 44.2 24/12/2013 [UNOFFICIAL],
UNOFFICIAL AOKP][4.4.2] [S4] [12/26/13]
I'm in no way blaming the ROM developers for this issue I just need a little help
Strange problem. I think you should flash firmware, it is worth to try i guess
Sent from my One S using xda app-developers app
mines actually doing the same, and from what i've been reading, i believe it has to do with your hboot version and ics not being compatible with it. try flashing your original ruu if you can. that's what i'm trying to do as we speak. if i ever get my problem figured out, i'll let you know if it works.
HomieOneKinobi said:
mines actually doing the same, and from what i've been reading, i believe it has to do with your hboot version and ics not being compatible with it. try flashing your original ruu if you can. that's what i'm trying to do as we speak. if i ever get my problem figured out, i'll let you know if it works.
Click to expand...
Click to collapse
This was my test phone I had flashed just about everything you can think of before I would install it on the phone I use every day
I guess my luck ran out
I ended up flashing the phone back to the original firmware and OS version using the factory RUU without a problem
If I try to install anything over 4.04 it goes right back to the same crap
I tried different firmware, kernels, roms with sense/ no sense doesn't matter.
the phone is being sold as I type this and I'm leaving my other two One S phones alone for now on
Nobody should have to go through this much bull for newer OS version so I'm saving for a Nexus 5
Thank you for the suggestion