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:
Related
my GF has a SGS I9000...i updated her via Kies to the latest firmware because it was performing like crap. The update fixed that but every now and again it stops responding and the screen goes black...lights are still working on the buttons.
You can't power it off with the power button and the only way to fix it is to remove the battery. I've just updated her the the latest ROM from XDA for the SGS from http://forum.xda-developers.com/showthread.php?t=1102881 XWJVZ/XXJVT/OXXJV9/Sbl (MultiCSC) but it still does it...any ideas??
I've seen a few posts but no fixes..any ideas...HW vs. SW..was fine before the updates.
tia
First thing to do is isolate the problem as a hardware or software one. Simple task: flash stock, and see if it happens. If it does, you know it's hardware.
If it isn't, ask the developer (if it's a custom rom), or post under the appropriate phone of the forum. Chances are, if it is software, someone else with the same device has had it before.
NType3 said:
First thing to do is isolate the problem as a hardware or software one. Simple task: flash stock, and see if it happens. If it does, you know it's hardware.
If it isn't, ask the developer (if it's a custom rom), or post under the appropriate phone of the forum. Chances are, if it is software, someone else with the same device has had it before.
Click to expand...
Click to collapse
Tried a stock ROM straight from the Telco, now flashed to a stock ROM from XDA. Happening on 2 phones, both SG2 i9000. Both have different ROMS from different Telco's both were fine before the latest ROM updates.
One appears better with the latest official stock ROM from XDA but just monitoring it at the moment...just wanted to know if it was a know issue before spending too much time on it
ta
I just installed UCLD2 Smooth ICE 5.0 followed his instructions and I like the Rom, but I have an issue. My home button and search button do not work at all. I've gone into the settings to see if there is anything to change what the buttons do, but I've found nothing.
Does anyone know what could be causing this? Or what I can do to fix it.
I had the same issue with flashing sky is. I did a nandroid recovery, then reflashed the whole thing and allowed the system to settle longer than the suggested 5 minutes. It works great now. Buttons are fine.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Well as it turns out that was only one of a myriad of problems, I may or may not have permanantly bricked my phone. I let the system settle, but now the screen isn't very responsive when I try to do anything on it. I also tried returning to stock, and have had the same problems.
I don't have any idea what happened, but it seems to be like a kernel problem.
CrazyLineman777 said:
Well as it turns out that was only one of a myriad of problems, I may or may not have permanantly bricked my phone. I let the system settle, but now the screen isn't very responsive when I try to do anything on it. I also tried returning to stock, and have had the same problems.
I don't have any idea what happened, but it seems to be like a kernel problem.
Click to expand...
Click to collapse
If it turns on then its far from bricked. What was your method of returning to stock?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
There's been way too much of this nonsense recently. You don't even know what a brick is. All the new guys need to stop flashing everything they can get their hands on. Stop and read before you do this stuff to your phone. I read for almost a whole month, everything I could find before doing anything. Before I even flashed anything, I had everything needed to fix and return to stock, and made sure I completely understood what I was doing. Read and understand before you break stuff so you can fix it!
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
I...I....I give up Congrats noobs not just op you have killed my faith in humanity you all have won and destroyed my spirits
Sent from my SGH-T989 using Tapatalk 2
When most of us first installed the leak the fix was to install it again with the 1 click or factory reset.... Are you coming from stock gb or stock ics leak?
Edit: nrm and dx you guys crack me up
CM9 Skyrocket
I didn't flash whatever I could get my hands on thank you. I flashed NexusMod 4.3 Nexus UI first about a week and a half ago. Then I wanted to try and get something a little more like stock, but still ICS so after READING ALL THE INFORMATION on the post for ICS Smoothie v2 I flashed it after wiping data, cache, and dalvik and following the instructions regarding an ICS radio which I had not followed previously with Nexus Mod when I flashed it. Then the problems started.
There is no lockscreen even when the phone decides to work. When I start up the phone. Process.google.acore force closes as does process.google.gapps
Also when I unlock the phone the screen will respond to 1 maybe 2 swipes to find a homescreen then it'll hang.
I used ODIN to return to stock following the instructions on the Stickied post about doing so in the Development section. Also I'm sorry if some of what I said comes off rude I've just been trying to fix this for about 4 days with no luck and I really need some help.
Also I would've responded sooner, but it's finals week at my college so I've only got so much time.
Also I apologize for calling it a brick even though it was not. I do know what a brick is. It's when your device is unresponsive and will not turn on or do anything. It'a a paperweight or a brick.
I was freaking out my bad. I am sort of seasoned I was rooting my HTC Inspire when I got it almost a year ago, and I put ICS on it when the first leaks started coming out. I'm sorry I'm new to this phone. I will be getting better trust me. I just need some time to get used to the different quirks involved in this phone compared to my last one.
CrazyLineman777 said:
Also I apologize for calling it a brick even though it was not. I do know what a brick is. It's when your device is unresponsive and will not turn on or do anything. It'a a paperweight or a brick.
I was freaking out my bad. I am sort of seasoned I was rooting my HTC Inspire when I got it almost a year ago, and I put ICS on it when the first leaks started coming out. I'm sorry I'm new to this phone. I will be getting better trust me. I just need some time to get used to the different quirks involved in this phone compared to my last one.
Click to expand...
Click to collapse
My suggestion still stands use the ics leak 1 click then root see how you like stock ics twiz if you want a more custom rom then goto cwm and wipe cache , factory reset, then in mounts wipe sys, wipe cache and wipe data do all of these 3 times before installing rom and kernel always let.it sit a few minutes to settle....
CM9 Skyrocket
Ok I'm sorry for causing all of these issues I think I found a solution. In the General section and since I can't post links it is entitled:
[FIX] No Power Menu, No Lockscreen, Corrupt Efs FIX! Skyrocket and T989
Sorry I didn't look in General before posting this in Q&A the General section in the HTC Inspire forum wasn't usually gonna have fixes in it maybe root methods, but not fixes for stuff like this.
CrazyLineman777 said:
Ok I'm sorry for causing all of these issues I think I found a solution. In the General section and since I can't post links it is entitled:
[FIX] No Power Menu, No Lockscreen, Corrupt Efs FIX! Skyrocket and T989
Sorry I didn't look in General before posting this in Q&A the General section in the HTC Inspire forum wasn't usually gonna have fixes in it maybe root methods, but not fixes for stuff like this.
Click to expand...
Click to collapse
What radio did you flash?
I did realize I had done it wrong I flashed this: ATT-GALAXY-NOTE UCLC5 radio
but it was the one located in the post for Embryo 2.2 and I didn't flash the embryo rom, so the radio file which Mohan made specifically for his rom didn't go over well with the rom I flashed.
I did get back to stock eventually. It just took a few tries and the efs fix. I'm now putting CWM touch back on my phone and flashing a Gingerbread Rom because ICS on our phone is still a little too iffy for my likeing. I'll probably just wait till Samsung releases source for the kernel and cook my own rom.
CrazyLineman777 said:
I did realize I had done it wrong I flashed this: ATT-GALAXY-NOTE UCLC5 radio
but it was the one located in the post for Embryo 2.2 and I didn't flash the embryo rom, so the radio file which Mohan made specifically for his rom didn't go over well with the rom I flashed.
I did get back to stock eventually. It just took a few tries and the efs fix. I'm now putting CWM touch back on my phone and flashing a Gingerbread Rom because ICS on our phone is still a little too iffy for my likeing. I'll probably just wait till Samsung releases source for the kernel and cook my own rom.
Click to expand...
Click to collapse
I see, the note modem corrupts the efs partition. Glad you read some things and got it fixed!
So I originally rooted my S3 using odin and a stock verizon software followed by using ez bootload unlock, ez recovery, and clockwork mod. I used the custom rom cyanogen mod, and eventually continued to update those roms when they rolled out the OTA updates. When the latest update came out on the 18th I noticed an issue with my contacts. Due to this I reverted to the 16th rom, but something went terribly wrong. At this time I tried re-rooting, tried different types of rooting and got my device working along with my contacts back, but it rendered my sim card useless. I tried everything I could find on the internet. I finally covered my tracks and took it to the verizon store. They replace the sim card, but it still didn't work. They replaced my device, and me being dumb I rooted it again. Same original rooting that worked the first time. It worked at first, but then the same issue occurred. I'm not sure what to do, I can't go back to verizon again. They will expect something this time. It makes no sense. The hardware is not an issue, there is some data error somewhere. PLEASE HELP!!!
TLDR; Crazy weird data issue maybe? Whoever can solve this will be the House of Android rooting.
a.p.mahaney said:
So I originally rooted my S3 using odin and a stock verizon software followed by using ez bootload unlock, ez recovery, and clockwork mod. I used the custom rom cyanogen mod, and eventually continued to update those roms when they rolled out the OTA updates. When the latest update came out on the 18th I noticed an issue with my contacts. Due to this I reverted to the 16th rom, but something went terribly wrong. At this time I tried re-rooting, tried different types of rooting and got my device working along with my contacts back, but it rendered my sim card useless. I tried everything I could find on the internet. I finally covered my tracks and took it to the verizon store. They replace the sim card, but it still didn't work. They replaced my device, and me being dumb I rooted it again. Same original rooting that worked the first time. It worked at first, but then the same issue occurred. I'm not sure what to do, I can't go back to verizon again. They will expect something this time. It makes no sense. The hardware is not an issue, there is some data error somewhere. PLEASE HELP!!!
TLDR; Crazy weird data issue maybe? Whoever can solve this will be the House of Android rooting.
Click to expand...
Click to collapse
Why don't you try to Odin a pre-rooted Verizon stock can be found here http://forum.xda-developers.com/showthread.php?t=1984436 to see if it addressed both our your issues?
I just had some major issues with this as well. There is something wrong with the nightly versions of CM 10.1.
Like you - I flashed CM 10.1 12/18 and found that my data was not working. I then searched this forum and found that other users were having the no data issue as well. I decided that I would do the same and flash back to an earlier CM 10 release from December, but the update did not go as expected. Due to going 10.1 to 10 I had to wipe data/cache/dalvik. At this point I got CM 10 reinstalled, but the phone came up with NO cell coverage. I went to System Settings -> About -> Status and found that the phone was no longer registering my cellular network (Verizon) or phone number. My IMEI data was dead.
Luckily in my case I had already made backups of my IMEI data per this post: http://forum.xda-developers.com/showthread.php?t=1852255
I restored my IMEI and reflashed CM 10 12/16. Everything is now working as expected. Your issue sounds identical to mine - I just spent half the day fighting with the exact same issue. I definitely learned my lesson about staying so current with the NIGHTLY builds for day-to-day non-dev use. I knew it before, it just never bit me like this.
Anyways, I hope this information helps you somewhat. Good luck!
a.p.mahaney said:
So I originally rooted my S3 using odin and a stock verizon software followed by using ez bootload unlock, ez recovery, and clockwork mod. I used the custom rom cyanogen mod, and eventually continued to update those roms when they rolled out the OTA updates. When the latest update came out on the 18th I noticed an issue with my contacts. Due to this I reverted to the 16th rom, but something went terribly wrong. At this time I tried re-rooting, tried different types of rooting and got my device working along with my contacts back, but it rendered my sim card useless. I tried everything I could find on the internet. I finally covered my tracks and took it to the verizon store. They replace the sim card, but it still didn't work. They replaced my device, and me being dumb I rooted it again. Same original rooting that worked the first time. It worked at first, but then the same issue occurred. I'm not sure what to do, I can't go back to verizon again. They will expect something this time. It makes no sense. The hardware is not an issue, there is some data error somewhere. PLEASE HELP!!!
TLDR; Crazy weird data issue maybe? Whoever can solve this will be the House of Android rooting.
Click to expand...
Click to collapse
You most likely lost you imei/min or something, you can check in settings>about phone>status. Easy way to correct it is to flash a older stock ICS image and use the reprovision code. Flash this in odin then type this in the dialer *2767*3855# and that should fix ya back up. Flashing anything carries a risk of dropping your imei but it happens much more on AOSP roms.
So after doing a wipe to my phone (was becoming slow) my phone randomly restarts itself for no reason as if it just crashes. I am running the latest version of the beanstalk rom. http://forum.xda-developers.com/showthread.php?t=2091900 I don't have the greatest understanding of flashing, roms, blah blah blah, but managed to get kit kat working for the last year or so, I don't understand why this is happening now, did I choose a bad rom or something? Everything else on the phone works but obviously constant restarts get to be very annoying.
Any help would be appreciated,
thank you!
Infused4life said:
So after doing a wipe to my phone (was becoming slow) my phone randomly restarts itself for no reason as if it just crashes. I am running the latest version of the beanstalk rom. http://forum.xda-developers.com/showthread.php?t=2091900 I don't have the greatest understanding of flashing, roms, blah blah blah, but managed to get kit kat working for the last year or so, I don't understand why this is happening now, did I choose a bad rom or something? Everything else on the phone works but obviously constant restarts get to be very annoying.
Any help would be appreciated,
thank you!
Click to expand...
Click to collapse
Try leaving it turned on in recovery mode (CWM). If it still reboots, then you have a hardware issue. If it stays stable, I would blame the ROM and try a different version or a different distro.
Sent from my MyTouch 4G Slide
joel.maxuel said:
Try leaving it turned on in recovery mode (CWM). If it still reboots, then you have a hardware issue. If it stays stable, I would blame the ROM and try a different version or a different distro.
Sent from my MyTouch 4G Slide
Click to expand...
Click to collapse
Thanks for the reply,
I don't think it is a hardware issue as it never did this when I had Jelly Bean or even the last time I had Kit Kat, never know though! Also, I will try to leave it in recovery and see if it does it but a few questions:
-What is "distro" (does it has to do with the OS of the phone?)
-Is there some ROM you could recommend to me for this phone that is stable.. When I install the beanstalk ROM there are like 10 to choose from, I'm guessing they are all older/newer versions!?
-Finally something I was wondering for the longest time but wasn't sure of is can I go back to say, Jelly Bean? Or is it "irreversible"?
Thanks again, glad there's people out there who can help the noobs like me!
Infused4life said:
Thanks for the reply,
I don't think it is a hardware issue as it never did this when I had Jelly Bean or even the last time I had Kit Kat, never know though! Also, I will try to leave it in recovery and see if it does it but a few questions:
-What is "distro" (does it has to do with the OS of the phone?)
-Is there some ROM you could recommend to me for this phone that is stable.. When I install the beanstalk ROM there are like 10 to choose from, I'm guessing they are all older/newer versions!?
-Finally something I was wondering for the longest time but wasn't sure of is can I go back to say, Jelly Bean? Or is it "irreversible"?
Thanks again, glad there's people out there who can help the noobs like me!
Click to expand...
Click to collapse
Methinks it is the specific ROM. I call the different types of OM out there distributions (or "distros" - in light of what is commonly used in the Linux world), but there may be a better term. It could be the version of Beanstalk you are using, it could be any version of BeanStalk with your phone. Hard to say.
In light of above, I would try CarbonROM. I tried it out briefly, and haven;t had a problem with it (and have heard no issues form the guy I sold the phone to with it installed).
But if you want to go back to JellyBean, there is still a version of 4.2 kicking around (CM 10.1) in the development threads. You can downgrade, at worst you may have to ODIN back to stock. But try to flash in CWM first. I was quite satisfied with that version. My biggest gripe is that the mobile data quick setting didn't work fully (but the long way around did). There is CM 10.2 as well, but I could never get that one installed on my phone (installer would break). Between the two, I would try 10.1 (and if you cannot find a copy, I can dropbox it to you).
5529
joel.maxuel said:
Methinks it is the specific ROM. I call the different types of OM out there distributions (or "distros" - in light of what is commonly used in the Linux world), but there may be a better term. It could be the version of Beanstalk you are using, it could be any version of BeanStalk with your phone. Hard to say.
In light of above, I would try CarbonROM. I tried it out briefly, and haven;t had a problem with it (and have heard no issues form the guy I sold the phone to with it installed).
But if you want to go back to JellyBean, there is still a version of 4.2 kicking around (CM 10.1) in the development threads. You can downgrade, at worst you may have to ODIN back to stock. But try to flash in CWM first. I was quite satisfied with that version. My biggest gripe is that the mobile data quick setting didn't work fully (but the long way around did). There is CM 10.2 as well, but I could never get that one installed on my phone (installer would break). Between the two, I would try 10.1 (and if you cannot find a copy, I can dropbox it to you).
Click to expand...
Click to collapse
YES!
So, after I left the phone in CWM for 25 minutes or so and it being fine I decided to get Carbon as I seen in your "signature" that you had that ROM on your Infuse, it has been good for 2 hours+, looking good! I guess it was the Beanstalk ROM after all.
Thanks for the downgrading information as well, wasn't sure if you could downgrade or what would happen!
Finally, what is flashing? (I could google it but since your here, could you give me a noob friendly definition!?)
Thanks for all your help
Infused4life said:
YES!
So, after I left the phone in CWM for 25 minutes or so and it being fine I decided to get Carbon as I seen in your "signature" that you had that ROM on your Infuse, it has been good for 2 hours+, looking good! I guess it was the Beanstalk ROM after all.
Thanks for the downgrading information as well, wasn't sure if you could downgrade or what would happen!
Finally, what is flashing? (I could google it but since your here, could you give me a noob friendly definition!?)
Thanks for all your help
Click to expand...
Click to collapse
Went to reply about the camera issue and notice it was no longer in the post. Glad you got it sorted.
So flashing, as I understand it, is just another term for installing something via recovery. Not sure of the origin, maybe have something to do with installing to flash memory.
joel.maxuel said:
Went to reply about the camera issue and notice it was no longer in the post. Glad you got it sorted.
So flashing, as I understand it, is just another term for installing something via recovery. Not sure of the origin, maybe have something to do with installing to flash memory.
Click to expand...
Click to collapse
Ah ok, so it's essentially as I thought it was. I thought I was doing something wrong in terms of "flashing" but guess not! Sounds like it should just be called "Installing custom ROM".. !
Yeah, in terms of the camera thing, I'm an idiot and had USB storage turned on *facepalm*, So it wouldn't let me open the camera app!
Infused4life said:
Ah ok, so it's essentially as I thought it was. I thought I was doing something wrong in terms of "flashing" but guess not! Sounds like it should just be called "Installing custom ROM".. !
Yeah, in terms of the camera thing, I'm an idiot and had USB storage turned on *facepalm*, So it wouldn't let me open the camera app!
Click to expand...
Click to collapse
I am not sure if you are still facing the same issue but if you are facing reboots, then considering doing a fresh install after cleaning your internal storage as well since the remnants of the apps from previous installs have caused me problems. Ever since I started doing a fresh install (Factory reset, wiping the cache, wiping the dalvik cache and even the cache partition along with the wiping of the internal storage), there have been no reboot issues.
Hey guys, I can't seem to get this figured out, so I have resorted to coming to the forum for help. On every single ROM I have ran lately EXCEPT the old LiquidSmooth 4.4.4(most recent version), I have had issues playing music through AUX. WHenever I would plug in my aux cable, play a song, then turn off my screen, the music would start lagging and there would be lots of static. but if I waked the device it would be fine. Turn the screen back off, same thing. It started happening after flashing this GPE ROM found here http://forum.xda-developers.com/htc-one-m8/development/rom-m8-gpe-01232015-t3010825
Now it does it on Viper, any GPE or AOSP other than LiquidSmooth 4.4.4. I flashed Fluent ROM in the Verizon Dev thread last night and same thing. It will also do it on all versions of Viper(4.4.4 and 5.0.1). Is anyone else experiencing this? BTW I have not tested Bluetooth, so I don't know if it does it there too. I have tested the actual speakers on the phone, and it does not do it there, just on aux. kinda making me think it may be my cable, but I'm just looking to see if anyone else is having these issues.
Thanks in advance guys!
blkhrt13 said:
Hey guys, I can't seem to get this figured out, so I have resorted to coming to the forum for help. On every single ROM I have ran lately EXCEPT the old LiquidSmooth 4.4.4(most recent version), I have had issues playing music through AUX. WHenever I would plug in my aux cable, play a song, then turn off my screen, the music would start lagging and there would be lots of static. but if I waked the device it would be fine. Turn the screen back off, same thing. It started happening after flashing this GPE ROM found here http://forum.xda-developers.com/htc-one-m8/development/rom-m8-gpe-01232015-t3010825
Now it does it on Viper, any GPE or AOSP other than LiquidSmooth 4.4.4. I flashed Fluent ROM in the Verizon Dev thread last night and same thing. It will also do it on all versions of Viper(4.4.4 and 5.0.1). Is anyone else experiencing this? BTW I have not tested Bluetooth, so I don't know if it does it there too. I have tested the actual speakers on the phone, and it does not do it there, just on aux. kinda making me think it may be my cable, but I'm just looking to see if anyone else is having these issues.
Thanks in advance guys!
Click to expand...
Click to collapse
Did you flash any audio mods or new firmware?
loonatik78 said:
Did you flash any audio mods or new firmware?
Click to expand...
Click to collapse
I have not flashed either. However, as we speak, I am updating my firmware to the new 5.0.1 firmware found here...http://forum.xda-developers.com/showthread.php?t=2723159...and I downloaded the version for TWRP users, and I have the latest TWRP 2.8.5.0 installed. So maybe that will make a difference?
blkhrt13 said:
I have not flashed either. However, as we speak, I am updating my firmware to the new 5.0.1 firmware found here...http://forum.xda-developers.com/showthread.php?t=2723159...and I downloaded the version for TWRP users, and I have the latest TWRP 2.8.5.0 installed. So maybe that will make a difference?
Click to expand...
Click to collapse
Possibly, but I doubt it. There's something telling the kernel to sleep which is why it happens when you turn your screen off. I'd try wiping /system before flashing a ROM. There might be something from liquid being left behind. Factory resets don't wipe /system. If you're ROM requires an intact /system such as Adrenaline, flash a stock rooted ROM first, then the custom ROM. That's what I'd try. Someone else might have a better idea.
loonatik78 said:
Possibly, but I doubt it. There's something telling the kernel to sleep which is why it happens when you turn your screen off. I'd try wiping /system before flashing a ROM. There might be something from liquid being left behind. Factory resets don't wipe /system. If you're ROM requires an intact /system such as Adrenaline, flash a stock rooted ROM first, then the custom ROM. That's what I'd try. Someone else might have a better idea.
Click to expand...
Click to collapse
Actually every single time I flash a new rom, I go into advanced wipe and wipe system, data, cache and dalvik cache 3 times. Every Time. But I flagged that new firmware and was rubbing digital high rom from the Verizon thread and did not have the music issue. I'm running fluent rom sense 7 from the Verizon thread now but have not tested the music yet But will update you guys in the morning. Thanks for all your replies