Hey guys,
So, I was running CM10.2 and wanted to get back to KitKat. I flashed Slimkat, and then the day after, Slim dropped their official, so I reflashed that, everything was fine, except I don't get notification sounds. Even if I go to settings, when I try and select a sound, it just doesn't play. I tried a few other roms, Pacman, Beanstalk, Going back to the non offical relase of slimkat, and still, everything is fine, except for no notification sounds.
Any ideas what could be causing this? Or how to fix?
I had this problem before, and was able to just use odin to flash a stock image and then reflash a custom rom, but I'd like to avoid that this time if possible.
Related
I lost my backup of my original factory ROM, I tried the RC ICS ROM and it did not work. I had cyanogenmod 7.1 alpha running but now it is very unstable. I have a series problem where the phone options screen keeps randomly popping up, without me pressing the top power button. I would now like to revert back to the stock Sense 3.0 ROM that shipped with the Sensation. If anyone can help me I would so grateful as this is a super annoying problem to deal with.
I have Revolution, Clockmod Recovery and have tried multiple ROM's and find they all have some sort of bug
Another thing, the battery life has deteriorated to the point that I can not even get more than a half day of standby with a quarter of usage.
Please explain how I can get the factory ROM back on the phone with no bugs or issues. Thanks.
have you tried any other ICS ROM? majority of them are stock with minor tweaks,
insertcoin 4.3.1 is pretty stable
Click Me!
I know you'll probably do so already, but make sure you do a full wipe before flashing the stock ROM
I tried the RCmix ICS but when I installed it, all that happened was it kept popping up a dialog box non stop and was unable to use it so I reverted back to the Cyanogenmod 7.1
Can you please let me know where I can get this ROM, I will give it a shot.
RUU Roms can be found in thread
ttp://forum.xda-developers.com/showthread.php?t=1074559
Hi everybody,
I decided to go back to Cyanogenmod, because i had some issues with the ROM I used before. First I flashed the CM 10.1.3 stable, everything worked fine, but I couldn't connect to any WiFi. So i tried flashing the nightly 10.2 10.2 2013111 over the Updates in the preferences. Still, i couldn't connect to any WiFi. I tried it two more times with full wipes and flashing the nightly over my Recovery, but couldn't make it work.
All these times i flashed the boot.img after flashing the nightly. I don't really know what to do anymore and thought anyone might have an idea for me?!
I didn't have any major issues until today, so i don't know what Information you might need to help me, so please tell me if I should say something more about the system or how I flashed it etc.
Thanks in Advance!
Edit: Same Problem with CM11...
Edit 2: Tried to flash the Bubba Kernel, because i read something about it...now i can't even turn the wifi on. -.-
So...I have had a captivate and SGS3 and have never had so much trouble with a phone. This infuse is frustrating and complicated to work with. I have blue CWM which was acquired by using Entropy's guide and the other numerous helpful tips out there. I had rootbox running which would eventually start FC'ing and acting dumb. I wiped everything the other day and flashed unofficial CM 10.2, it worked perfect then random reboots to stuck at samsung then cyanogen mod then back again. Sometimes it would randomly reboot in CWM, which has never happened to me on other phone. I feel like going back to stock and back again is the only answer, but it seems like a lot of work and I already did that and it was fine.
So, all you guys that understand whats going on behind that scenes, what do you think the issue is?
UPDATE: I found a video that may link this behavior to a hardware issue caused by poor design by Samsung having too many contacts that can get gunked up and causing issues.
Might be a problem with the version of the Gapps you're using. Consider changing and even going back to older versions. I found v 12/12 signed very stable on cm10.1.
If still stuck, consider Odin back to stock in download mode and flash cm9 and cm10.2 again!
Hello, do i have really weird problem.
My time just freeze and is different everywhere. Because of that my alarm doesnt even go off.
I thought i screw up something during flashing new FW, but now its doing on every ROM i flash, even STOCK !
Some exaple (clean and fresh flashed ROM, no apps installed, nothing, just clean)
http://imgur.com/a/YO3x9
Checked it hour later:
http://imgur.com/a/CTjFG
Stock:
http://imgur.com/a/uB4Qs
So what i did before it started.
I was running Paranoid Android 4.6 Beta 6, everything was good, i wanted to try lastest stock ROM, so i flashed 1.17 with FlashTool (i wanted to try camera, if its better) well, but i liked features from 4.4 kitkat, so i rooted with rootkit, via ADB flashed boot.img, installed back Paranoid and boom... clock sudenly freeze everytime, i have tried lolipop CM12 beta3, same thing, flashed to CM11 FXP349... same clock freezing, flashed paranoid 4.6 beta 6, same thing, so i flashed it back to 1.17, but hey, same clock freeze, so i flashed to 1.14, boom same freezing...
I have no idea what to do now, clock just freeze, alarm doesnt work because of that and iam clueless.
EasyCzT said:
Hello, do i have really weird problem.
My time just freeze and is different everywhere. Because of that my alarm doesnt even go off.
I thought i screw up something during flashing new FW, but now its doing on every ROM i flash, even STOCK !
Some exaple (clean and fresh flashed ROM, no apps installed, nothing, just clean)
http://imgur.com/a/YO3x9
Checked it hour later:
http://imgur.com/a/CTjFG
Stock:
http://imgur.com/a/uB4Qs
So what i did before it started.
I was running Paranoid Android 4.6 Beta 6, everything was good, i wanted to try lastest stock ROM, so i flashed 1.17 with FlashTool (i wanted to try camera, if its better) well, but i liked features from 4.4 kitkat, so i rooted with rootkit, via ADB flashed boot.img, installed back Paranoid and boom... clock sudenly freeze everytime, i have tried lolipop CM12 beta3, same thing, flashed to CM11 FXP349... same clock freezing, flashed paranoid 4.6 beta 6, same thing, so i flashed it back to 1.17, but hey, same clock freeze, so i flashed to 1.14, boom same freezing...
I have no idea what to do now, clock just freeze, alarm doesnt work because of that and iam clueless.
Click to expand...
Click to collapse
Just do a factory reset .Might work"-"
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