First off, this was a replacement handset, as soon as I got it I upgraded it to 2.3.6 rooted it and unlocked the bootloader. I then installed RomRacer's CWM. At this time I wiped phone through CWM and proceeded to install Aura (ROM) http://forum.xda-developers.com/showthread.php?t=1186990 everything went well and the phone booted up and that was that. I left the phone out all night and when I woke up I saw that the phone was asleep and wouldn't wake. No backups were restored so it isn't a corrupt backup. Phone kept doing it randomly and so I wiped it again and again to see if it would help but every time it would do the same. To cut the story short, I then completely wiped the rom off of the phone and installed nottachtix 1.2.9b..... and the same thing is still happening! I've tried different batteries just in case and nothing. What could be wrong here?
i had the same problem with neutrino 2.5...had to pull the battery to wake it up...have you tried any other roms like red pill or dark side? i am using neutrino 1.4-s with no wake issues...
Today it happened for the first time ever on my phone using cm7 weekly feb 20. I think I'm going to try out some other roms.
I just applied the wake with volume keys hack... so let's see what happens. I've only tried aura and nottachtix, but trying 2 different ROMS and having the same issue is making me think it might not be the ROMS
Sent from my MB865 using xda premium
i never had the wake issue on miui either...could also be ghosts in the machine
i'm having this problem too. both on stock rom and custom rom (mrom) so i'm thinking its not the rom it has to be something else
I'm getting the same thing using the newest CM 10.1 build by epinter, released today.
If I play music, and then put the screen to sleep, the music keeps playing, but I cannot wake up the screen using the power or volume keys. I have to pull the battery to reboot.
I disabled all volume mods I could find (wake on vol, skip tracks, etc), but same result in two different music players (apollo, mixzing), can't wake while music playing.
I don't think I had that issue on other roms (beanstalk, avatar) but i think those use an older kernel (2.X), whereas CM 10.1 uses the alpha 3.1 kernel. Using beanstalk was almost perfect, but for some reason Mixzing on beanstalk couldn't contact its servers to build playlists (and ads), which I really need.
d'ohhh, 2 steps forward, one step back
EDIT: looks like it might have been bad installs, all above mentioned issues now working in the various roms.
Related
Last night I updated my g tablet to the most recent VEGAn ROM 5.1. I wiped all the data from my device via clockwork, wiped the Dalvik cache and repartitioned the internal memory as well. The install went smooth and everything is running great except for the fact that I now have no audio coming from my speakers. Turning the volume all the way up does nothing. I tried reinstalling the ROM but the issue repeats itself. Anyone have the same problem? Or, anyone have an idea how to fix this? Thanks.
Sound works fine here. I did have to take it out of silent mode.
bartonhen said:
Last night I updated my g tablet to the most recent VEGAn ROM 5.1. I wiped all the data from my device via clockwork, wiped the Dalvik cache and repartitioned the internal memory as well. The install went smooth and everything is running great except for the fact that I now have no audio coming from my speakers. Turning the volume all the way up does nothing. I tried reinstalling the ROM but the issue repeats itself. Anyone have the same problem? Or, anyone have an idea how to fix this? Thanks.
Click to expand...
Click to collapse
Sound fine here too. Volume rocker ONLY sets Media Volume in this ROM. Go to Settings->Sound->Volume and manually set volumes up, see if it fixes.
Thanks for the responses guys(or girls...one never knows). Silent mode is definitely turned off and I have also tried to address the issue by going into the volume settings. I have turned everything all the way up but I still get nothing. I'm gonna restore it to beta 4 and see what's up and then try and reflash 5 again. Wish I knew what was going on but thanks for the input.
Just reflashed to beta 4 and audio worked perfectly. I then reinstalled beta 5.1 and the audio disappeared again. Am I the only one?
bartonhen said:
Just reflashed to beta 4 and audio worked perfectly. I then reinstalled beta 5.1 and the audio disappeared again. Am I the only one?
Click to expand...
Click to collapse
I am actually still using beta 5, not beta 5.1, so not sure if something changed when Gojimi updated it this morning?
A quick suggestion - can you try first backing up everything in Clockwork Mod, then wiping user data and see if it makes a difference (i.e. if audio is still screwed up on a fresh install of beta 5.1).
Sound is fine for me in 5.1. All he changed was the G sensor stuff...
Backed it up, wiped user data, did a fresh install and still nothing. Maybe it is specific to my device(although I could not understand for the life of me why). Sad...I am loving VEGAn especially this newest update. I guess I will just wait for the next release to see what happens.
bartonhen said:
Backed it up, wiped user data, did a fresh install and still nothing. Maybe it is specific to my device(although I could not understand for the life of me why). Sad...I am loving VEGAn especially this newest update. I guess I will just wait for the next release to see what happens.
Click to expand...
Click to collapse
If it works in Beta 4, but not 5 maybe download the file again. Besides the G sensor stuff in 5.1 I think Gojimi also uploaded a new file to fix some boot.img size problem. Can't hurt to try the latest if you haven't already...
Did you try the headphone trick? (insert headphone plug into port, then unplug) That was an early issue that was resolved, but maybe it's making a reappearance.
I'm not on 5.1 yet, working on that today.
(btw, when I first read the title, I thought you were trying to do surround sound off your GTab!)
Brilliant! I've spent hours flashing and reflashing trying to get this thing to work and all I needed to do was plug in some headphones and then unplug them! I wish I would have found this out sooner so I wouldn't have wasted everyone's time. Thank You!
P.S.- Yeah I could see how there could be some confusion about title to this post...ha, I'll have to clarify more next time.
bartonhen said:
Brilliant! I've spent hours flashing and reflashing trying to get this thing to work and all I needed to do was plug in some headphones and then unplug them! I wish I would have found this out sooner so I wouldn't have wasted everyone's time. Thank You!
P.S.- Yeah I could see how there could be some confusion about title to this post...ha, I'll have to clarify more next time.
Click to expand...
Click to collapse
Only thing is you should not have to do that anymore. I bet you still have fragments of old roms hanging out. I do not have to do the headphone trick anymore and I am using 5.1. Haven't had to use that trick for a while now.
Whenever I flash something new I always do a factory reset, and a cache wipe. Every now and then I will use Nvflash to restore all the way back to brand new out of the box status. Too much of the old is getting mixed up with the new in a lot of cases causing lots of people to have weird issues that really don't exist.
Makes it hard for a developer to really know what is working and what is broken..
I just installed beta 5.1 and no audio issues, yet. Did you do a data wipe? Maybe there's something in /data causing the issue, that's my only guess.
Data wipes between mods and major updates is always recommended. I know it's a PITN but it can reduce the number of weird issues. I use Titanium Backup religiously.
I have never had to do it before with any older ROMS. I have only been using VEGAn ROMS since beta 3 came out. I also have been doing factory resets, wiping the cache, and repartitioning the sdcard consistently between installs. I might need to use Nvflash just to be safe and install a totally clean version.
bartonhen said:
I have never had to do it before with any older ROMS. I have only been using VEGAn ROMS since beta 3 came out. I also have been doing factory resets, wiping the cache, and repartitioning the sdcard consistently between installs. I might need to use Nvflash just to be safe and get it to stock.
Click to expand...
Click to collapse
I think the framework changed between beta 4 and beta 5. Different stuff. Maybe that's why you have been fortunate until now...
I got No sound too. Plugging in headset makes sound work On headet but when unplugged my sound is gone again. was working perfect on Beta 4.
Just flashed to Vegan Beta5 2 hours ago. My audio is working fine. Playing "Hall of the Mountain King" atm from speakers.
I update Vegan-tab 5.1 and the sound was working, i watched couple of movies, and today evening no sound, tried in setup and no sound.
I was turning sound off/on from the screen unlock, window, by swipe down the speaker icon. Now i have no sound.
I don't know what i did to make the sound goaway.
Update: now i got the sound back, don't know how i got back since i did all the tricks said in this forum.
1. did the settings->volume-> changed all 3 volume increase.
2. reboot may times.
don;t remember the order. so don't know which one cleared it.
So far I have not run into the no sound problem with b5.1. I sure hope it doesn't crop up because I leave today for a week long trip.
Last night i had installed FRING and Yahoo Instant Messenger, with the Voice/video add-on. And my media volume was muted, couldn't get it to go up. Even when going into setting, and increasing it, it wouldn't increase. I uninstalled those programs and it started working again after a reboot. Running VEGAN 5.2.
Does anyone else experience this with the new leaked 2.3.4 HKTW build? Or is it just my Atrix?
Yeah I exp. It as well but I notice my screen becomes in responsive and so do the touch keys. Only the power button and volume rocker work.
I've only experienced this while on a phone call though to be honest. Like when I'm on hold and I'm.checking Facebook or I'm looking something up on the web while on a call. But I definitely think it's a bug in hktw build 2.3.4 cause I beverage had a problem before with it.
I tried looking through the forums and haven't seen any other complaints untilled this one so maybe its just a few of us. Can any one else confirm this or is there a fix some where?
Sent from my unlocked//rooted ATRIX
mine works fine...
Happens to mine all the time. Fixes itself after turning the screen off.
d3athsd00r said:
Happens to mine all the time. Fixes itself after turning the screen off.
Click to expand...
Click to collapse
when mine freezes even locking phone with the power button and waiting a few seconds to turn it back on doesn't help it still stays un-responsive at the lock screen. I'm actually noticing it happening more and more frequent. or I'm just multi tasking more and more frequent lol idk cant wait for a USA build as apposed to this HKTW build but hey i got to say its definitely pulling me through this month of waiting for it ;P
Mine happened a few times a few days ago...then once the day after, and not since. Been like 4 days now.
i've a cyanogen 7 in my wildfire, and start happens and i dont know why, i've this rom from 3 months and never heard such a thing, hope some one can help fix this.
I've have done a hard reset and nothing
Mine did that already in 2.2 , back then the fix was to lock and unlock the screen. That would always fix the issue, at least until next time. Now in 2.3.4, it still happens, but if I wait 15-20 seconds it usually fixes itself. Looks like Motorola applied some fixes but didn't fix the issue completely.
Bell ATRIX Gobstopper 2.3.4
well guys, i solve the problem for now....
solution:
1º make sure that you have a backup prior to the problem (original stock or other thing), if not you might have to install the room from set one.
2º retrieve you sd card, make a backup of some things that you dont want to lose (like pictures, ring tones, mp3 etc) and leave a folder with a backup that you have, next format sd card in fat32 and put the things that you save (note, dont do all the backup of sd card, like the folders with .com... and android folders etc)
3º go to clockworkmod recovery, by restarting to recovery, wipe all data, like the firs time you install the custom rom, now go to backup and restore and do restore to your backup.
4º Restart and voila, that works for me...i figure that was some app that might cause the problem,(thinking on ndrive 11) im going to test now, but it works.
cheers and post something that might help some one
Gingerbread Problem
I am the same problem everything was fine with Froyo once I updated to Gingerbread I had these issues. Also the droid and nexus folks are reporting those just google up gingerbread phone freeze. I have not found a fix yet. Thanks
My US Galaxy Player 5:
Model: YP-G70
ROM: Eryigit Rom 3.0 USA
Firmware: 2.3.6 Gingerbread
Launcher: ADW
Rooted: Yes
Sorry if this question has already been answered elsewhere, but I have scoured the forums and have seen no other people with an experience similar to mine.
I bought a refurbished galaxy player 5.0 US version on amazon about 6 months ago. Since about a week or two after I bought it, I have had nothing but problems with it:
-The player will randomly say the SD card has become unmounted (never on for more than 2 hours without the SD card being unmounted,) and the only way for it to recognize the SD card is a reboot
-The player will freeze when I am trying to open an app, and I am forced to hard reboot
-Occasionally starts randomly playing songs at full volume through the speakers, even though the player is on silent and is not being used (and there is no alarm on.)
I was originally using the stock ROM, and these problems gradually became worse and worse. After the freezing became so bad that I was literally forced to reboot (sometimes multiple times) any time I wanted to switch between apps, I decided to try using Cyanogen instead of Stock Gingerbread.
I loaded version CM7.2.0, and all of these problems completely disappeared (except for the SD card unmounting problem, but even this was way less frequent.) I used CM7 for a few weeks, and ran into the problem where flight mode was stuck on and I couldn't use my WIFI.
I tried to factory reset a few times, but still couldn't get it to work, so I tried flashing the Stock Gingerbread 2.3.6 back on, but got the boot loop error. I ignored the boot loop and used CWM to put CM7.2 back onto my player. I eventually got the WIFI to work through a third party app, and was able to use my player with no errors for about a week, until it went completely haywire and started crashing any time I tried to use any apps that WERE NOT third party apps. Also, none of the features like WIFI, bluetooth, camera, etc. were working. My app I use to study Chinese was still working, so I waited a few weeks before I tried to recover the player in case doing so made it unusable. I tried a hard reset, and this time I got a boot loop for Cyanogen as well. After a few weeks and about 40+ hours of flashing different ROMs onto the player and using different strategies to do so, I finally got past the a boot loop using Eryigit Rom 3.0 USA.
I was very happy to have use of my player back, but only a few days after flashing the stock ROM, the problems that plagued my player initially have returned.
Sorry for the novel, but I wanted to make sure I included a detailed history of my problems in case any lend some insight in to what is wrong with the device. Does anyone have any advice on what to do moving forward to fix any of these problems? Thanks in advanced.
Also, this probably isn't related, but I would like to note that my player stayed on without being charged for 10 straight days (with intermittent use over the period) when I had CM7 flashed and it was messed up. Wanted to point that out in case it signified that some specific critical process was not running, which led to buggy usage, but super long battery life.
Did you wipe the data partition and dalvik cache when you installed each new rom? If you didn't, I suspect that's causing a lot of your problems right there. To fix it, you'll need to use the "reset to factory" and 'wipe dalvik cache" options in CWM.
A couple of your problems are standard behavior. Specifically, the lack of bluetooth, camera, and hw acceleration are normal with CM9 or later on this device. Also bootloops will happen if you reboot your device while it's connected to a computer.
One possible solution for your sd-card issue is to unmount the drive (in the settings/control panel) then physically eject the card and reinsert it (making sure to push it in all the way, you'll feel it latch). That's what I did when I had a similar problem with my player and the sdcard.
Could be you did not wipe when you install rooms .. also try some 4.1 rom offcourse with wipe
Sent from my Galaxy Nexus using xda app-developers app
My tab (P4wifi model) does not seem to recognize the current volume level when I start playing any app with sound (Youtube, Netflix etc.).
The moment I adjust the volume up or down (physical button or on screen), volume comes back up and from there it acts normally.
For example, if the volume level by default is 80% and if I start playing something on Netflix, it plays in very low volume and then if I reduce/increase the volume even just by 1, then sound comes back up to the actual level as if it never knew the volume was 80%.
I have tried many Roms like cyanogen, SGT7, Omni 4.4, Nameless 4.4 and now I'm on SlimSaber 4.3.1. As far as I can remember, it used to work fine in stock ROM and somehow broke somewhere along the way.
I am not able to figure out what I did wrong and not able to figure out an exact match for the problem even after searching posts here. I know this tab generally lacks volume and also about multiple apps to boost (ViperFx etc) this. But, I am fine with how loud this tablet is. But not the way it behaves when starting up an app with sound.
If this is a hardware problem, I don't know how everything works normal when I adjust the volume even by a little bit. Any help is appreciated.
You could try to go all the way back to stock to see if it fixes it. If it does, then flash back to your current ROM and test again. Like you said, something may have broke along the way and flashing back to stock may fix it.
Thank you. I will try that tonight and see what happens.
Okay so, I went back to Stock 4.0.4 and tested YouTube volume. No problems there. Couldn't test Netflix as it wasn't showing up on play store.
Now, I switched back to SlimSaber 4.3.1 by restoring a nandroid back up with TWRP. Same original issue with volume still exist.
One thing I noticed during the first boot to SlimSaber ROM was the media volume setting was always showing lowest (silent) and wasn't saving the setting even after changing it multiple times. But, this problem got sorted out on its own after a reboot.
I had tried flashing the ROM before restoring backup like you said in your reply. But, at that time ROM did not boot due to some issue. It was stuck at SlimSaber logo. I'm going to try this couple of more times during the weekend and will flash the ROM instead of restoring nandroid to see if that makes any difference.
Try not to use the backup unless you got yourself in trouble. A clean flash is better if you're trying to fix things. And also remember to make a full wipe before flashing. I've been on SlimSaber and I can confirm that I don't have the issue.
After switching to LineageOS 14.1, my Samsung S3 i9300 randomly turns off. Not a proper shutdown, screen just goes black.
Happened 7 times in 2 days so far, first time while I was tinkering with the settings, second time while I was swiping to another page in Nova Launcher, third time while I was asleep last night, woke up and discovered my phone was off. The other shutdowns happened while the phone was locked.
The device does not shut down completely. I can see the Samsung Led flashing for the message notifications. Just the display turns off. I have to go into recovery mode and reboot the system from there to get the display working again.
I came from the stock ROM. It started immediately after flashing Lineage.
If this happens on a stock rom, it is probably a hardware issue.
audit13 said:
If this happens on a stock rom, it is probably a hardware issue.
Click to expand...
Click to collapse
Thank you for your reply, but this does not happen on the stock rom.
It's definitely good that this doesn't happen in stock.
Sounds like a incompatibility between the phone and rom. Have you tried earlier or later versions of lineage?
All custom roms are considered beta. You will encounter issues. The issues should be in a list on the website/dev forum for the developers.
Beamed in by telepathy
I can also confirm this on the latest lineageos nightly update to date. It's as if phone is on standby/sleep and no way to wake it up without rebooting the phone by holding down the power button until phone restarts. I don't need to go into recovery like OP. Anyone else?
Are we the only ones experiencing this issue? Any help would be appreciated.
Gizmotech said:
Are we the only ones experiencing this issue? Any help would be appreciated.
Click to expand...
Click to collapse
You got a reply in the other thread where you posted about it:
minealex2244 said:
I'm feeling bad for you guys. Everyone should get the same beautiful LOS experience.
Thank you @Gizmotech for the last_kmsg. I think that you removed the battery to be able to reboot your phone. If you received a notification (sometimes you will receive it but it will freeze before letting you know that you got a notification) then the kernel will freeze. If the kernel is freezing it's because of root or a failed attempt to remove root (even if it said that it was a successful removal). It's very simple: you get a notification and it freezes. Maybe it will give a sound and the LED light maybe not. What's sure is that the kernel will freeze. Lastest SuperSU has this issue fixed. If you want it working then dirty flash latest build again. Tell me if the issue was fixed and avoid root until that time. After you'll tell me the results you can flash latest SuperSU and tell me again what happened. Do not remove root. This is always a dangerous thing.
Click to expand...
Click to collapse
kgndrn said:
After switching to LineageOS 14.1, my Samsung S3 i9300 randomly turns off. Not a proper shutdown, screen just goes black.
Happened 7 times in 2 days so far, first time while I was tinkering with the settings, second time while I was swiping to another page in Nova Launcher, third time while I was asleep last night, woke up and discovered my phone was off. The other shutdowns happened while the phone was locked.
The device does not shut down completely. I can see the Samsung Led flashing for the message notifications. Just the display turns off. I have to go into recovery mode and reboot the system from there to get the display working again.
I came from the stock ROM. It started immediately after flashing Lineage.
Click to expand...
Click to collapse
Providing the last_kmsg will help Simon to find a solution. If you only complain about this issue then it won't be solved. Next time make sure to include last_kmsg.
---------- Post added at 19:49 ---------- Previous post was at 19:45 ----------
shivadow said:
All custom roms are considered beta. You will encounter issues. The issues should be in a list on the website/dev forum for the developers.
Beamed in by telepathy
Click to expand...
Click to collapse
Really? Do you know what beta means? I'm sure that you don't. Beta means that it is not really stable (80% or less of the things are working) while stable means that 95% of the things are working. This explains why LOS 14.1 for S6 was considered stable: because everything was working. Also that issues are already listed in the forums.
kgndrn said:
After switching to LineageOS 14.1, my Samsung S3 i9300 randomly turns off. Not a proper shutdown, screen just goes black.
Happened 7 times in 2 days so far, first time while I was tinkering with the settings, second time while I was swiping to another page in Nova Launcher, third time while I was asleep last night, woke up and discovered my phone was off. The other shutdowns happened while the phone was locked.
The device does not shut down completely. I can see the Samsung Led flashing for the message notifications. st the display turns off. I have to go into recovery mode and reboot the system from there to get the display working again.
I came from the stock ROM. It started immediately after flashing Lineage.
Click to expand...
Click to collapse
Same problem with last lineage version. Are you found solution ?
Any news on this? g9305 boots just fine but reboots after a few seconds / minutes.
cRaZy-bisCuiT said:
Any news on this? g9305 boots just fine but reboots after a few seconds / minutes.
Click to expand...
Click to collapse
The problem is the rom or kernel. It happens to all custom roms and kernels on the s3. No-one has found the source of the problem.
Everything custom is beta even if it is considered stable. Beta means "not final". Unless you see a rom with "final" on it then you'll encounter issues at some point.
The only truly final product if you want root is stock rom rooted. If you flash a kernel you'll get the same problem.