I recently got the s3 and installed the GalaxyMod R12 on it, but every so often, when my screen times-out, I will hit the home or power button to turn the screen back on, and the phone is frozen. It has happened in several apps, built in messaging app, games, email, browser, and the common theme is that the phone is frozen and the app is in landscape mode (whether I was in portrait or landscape mode before the screen timing-out has no effect). It doesn't happen often, but it is very annoying because I have to remove the back and the battery.
Does anyone have any idea as to what could be causing this? Everything else works better than I could imagine, it's just this one thing .
Note: this also happened with the R11 version of the galaxy mod.
What kernel did you choose on the install? Try flashing a stock kernel or another custom kernel and see if the issue goes away.
I installed imoseyon's kernel (because I didn't quite want to overclock yet.
Either disable everything in the lock screen settings except AOSP Lockscreen or do this method taken straight from the Galaxy Mod OP...
PureMotive said:
Q: The phone keeps freezing when I go into landscape mode.
A: This has been covered many times in the thread, but to reiterate: If you are using the AOSP lockscreen you must disable "Ripple Effect" in Settings -> Lock Screen -> Lock Screen Options
Click to expand...
Click to collapse
Related
Figured perhaps a bug thread for the Rogers 2.2 update may be in order?
Not sure if this is a bug or not, but it does seem a bit odd. The lock screen usually has the text "swipe screen to unlock" or something to that nature (the part with the <<< and >>>) - mine had it to begin with in 2.2, however now it has dissapeared and I just see the little lock icon saying the phone is locked. Is there any way to get it back or is this a 2.2 "feature" so you see more of your background?
The 2nd problem I noticed I have already started a thread on (and no replies ) - it deals with contact linking and Facebook. Seems something is whacky there too possibly. The thread: http://forum.xda-developers.com/showthread.php?t=907088
j.smith said:
Figured perhaps a bug thread for the Rogers 2.2 update may be in order?
Not sure if this is a bug or not, but it does seem a bit odd. The lock screen usually has the text "swipe screen to unlock" or something to that nature (the part with the <<< and >>>) - mine had it to begin with in 2.2, however now it has dissapeared and I just see the little lock icon saying the phone is locked. Is there any way to get it back or is this a 2.2 "feature" so you see more of your background?
The 2nd problem I noticed I have already started a thread on (and no replies ) - it deals with contact linking and Facebook. Seems something is whacky there too possibly. The thread: http://forum.xda-developers.com/showthread.php?t=907088
Click to expand...
Click to collapse
Definitely a feature. I love the clearer lock screen.
Bug: Haptic feedback vibration is very low system wide (not including soft keys).
Bug: Voice Dialer (Voice Dialler) is misspelled in the App Drawer.
Bug: Going to Settings > Display > Font Style causes a crash.
All I remember so far but there has been several.
Enhanced said:
Definitely a feature. I love the clearer lock screen.
Click to expand...
Click to collapse
Confirmed feature of Froyo, or is this a Rogers/Samsung specific feature? Just wondering because it WAS showing up for a few lock screens right after the upgrade, then eventually stopped showing up - reboot/battery reset didn't get it back... haven't tried a factory reset yet to see if that fixes it (if it's broke).
Enhanced said:
Bug: Going to Settings > Display > Font Style causes a crash.
Click to expand...
Click to collapse
No problems here - did you have it set to a custom/non default font when upgrading? I had mine on default (I prefer that to any other font) and have no issues changing fonts.
I've had some issues with wifi losing it's internet / market connection after wake up sometimes. shows still connected, but no network access. i have to turn wifi off, then back on occasionally.
rnewton01 said:
I've had some issues with wifi losing it's internet / market connection after wake up sometimes. shows still connected, but no network access. i have to turn wifi off, then back on occasionally.
Click to expand...
Click to collapse
Go to Settings -> Wireless and network -> Wi-Fi settings. From this screen, hit your menu key and select Advanced and try changing your Wi-Fi sleep policy to Never... perhaps it's set to "When screen turns off" causing you to lose Wi-Fi whenever you lock your phone?
Oh, another bug possibly...
Go to Camera app and open Settings. Open the wrench tab and go to the 2nd page. Click the Update button beside Firmware update. Either of the next two menu choices ("Check version by network" or "Firmware update") seem to freeze the phone (power off required). Doesn't seem to happen all the time, but my first time trying to get the update to do something caused the phone to lock up in to camera mode.
Also, the "It will occur additional fee." message is quite fun... no idea what fees I will incur, or for what reason (and I won't even get in to the grammar issues).
j.smith said:
Confirmed feature of Froyo, or is this a Rogers/Samsung specific feature? Just wondering because it WAS showing up for a few lock screens right after the upgrade, then eventually stopped showing up - reboot/battery reset didn't get it back... haven't tried a factory reset yet to see if that fixes it (if it's broke).
Click to expand...
Click to collapse
Well it can't be a Froyo feature because no other manufactures use the same lock screen as they do. So it's a Samsung feature brought on by Froyo. Simply, it can't be a bug.
No problems here - did you have it set to a custom/non default font when upgrading? I had mine on default (I prefer that to any other font) and have no issues changing fonts.
Click to expand...
Click to collapse
Yeah, I had to it some other font besides the default font...guess I'm screwed now? Bugs like these make me more anxious to get real Froyo.
Enhanced said:
W..guess I'm screwed now? Bugs like these make me more anxious to get real Froyo.
Click to expand...
Click to collapse
This is real Froyo from Rogers.
Anyone noticing that it's very glitchy and not smooth?
sirknattar said:
Anyone noticing that it's very glitchy and not smooth?
Click to expand...
Click to collapse
Its much faster and smoother than 2.1 stock was for me. Did you set it up fresh? Older settings can cause issues.
you guys have this issue? you may not even know it until you try to use mass storage mode. I use iSyncr (lets me use smart playlists based on ratings) so I need mass storage mode.
http://forum.xda-developers.com/showthread.php?t=907854
My wife and I (each have a Captivate) have had none of the bugs you guys have mentioned.
All we have experienced is a faster phone and WAY better battery life.
The only thing that upset me is that the update deleted my Ocean Wave livewallpaper, but I just redownloaded it.
Did some of you guys experiencing bugs ever run a custom ROM? I am thinking maybe these issues might be because you did...
Re: Haptic Feedback.
I've noticed it too, it's much weaker than before.
I could have sworn that I saw the option to turn up the intensity before, but can't find it now.
I want to update, but all these bugs are not very comforting
Jeffu said:
I want to update, but all these bugs are not very comforting
Click to expand...
Click to collapse
Go for it..I installed it and so far the improvements have been great over 2.1
Battery life is much improved, its faster than stock 2.1 (and after applying Ryan's OCLF...its incredibly responsive)
If you do have a lagfix installed prior to upgrading you should uninstall that first. Thats what I did and didn't have much problems. my one issue with Swype was fixed by clearing the cache.
shawn122 said:
Go for it..I installed it and so far the improvements have been great over 2.1
Battery life is much improved, its faster than stock 2.1 (and after applying Ryan's OCLF...its incredibly responsive)
If you do have a lagfix installed prior to upgrading you should uninstall that first. Thats what I did and didn't have much problems. my one issue with Swype was fixed by clearing the cache.
Click to expand...
Click to collapse
I gave it a go on your recommendation. Updated with no issues, now to actually try using it...
Has anyone rooted after applying 2.2? If so, what did you use?
I've been having issues turning on WiFi on my phone ever since I installed the update.
I accidentally clicked Airplane mode on my phone this morning, now my phone has been trying to turn the WiFi back on for about 5 mins....
As for battery life, my phone the first few days after installing Froyo seemed great, but now it doesn't really seem as good? No idea why....
And I've noticed a bit of lag at times while navigating on my phone.
Using LauncherPro Plus as my home screen, haven't rooted or installed any roms or anything.
I have noticed that when you turn the phone on from when it is off, if you don't wait for the wallpaper to display before swiping your phone on, the phone will stall. Mine stalled for about 5 minutes before it responded again.
I'm having a couple of small issues:
1) I can't get the GPS to look position. It just displays "Waiting for Location" and sits there.
2) OCLG - I got about 1000 on quadrant score. It doesn't seem laggy but I wanted to apply this lagfix to see if it can be better. I tried runnig the first option in the menu (z4 rooting), and it tries to launch either a page or the market (not sure which) but says "Page Not Found", but when you close it and press back, it says the root was successful, but all the other options are still "unavailable" so I can't apply the lagfix. There's a second method in the menu to do a root and that one fails as well, so I'm not sure how to get this working.
3) Camera - I got the same problem as a previous poster for the firmware update where it says "fees will occur" then when I click "yes", it tries to launch a page/market (again not sure) and says "Page Not Found".
4) Rooting - not sure how to root because the previous method of putting my update.zip and doing it through the recovery menu fails.
Any help is appreciated.
I was running rooted lagfixed stock Rogers 2.1 before. Removed lagfix first and did a factory reset before updating to 2.2 through Kies.
After updating to 2.2 I re-rooted and lagfixed with no issue.
Things bugs I have noticed on my phone:
- Camera a few times had started up with a black screen only with usual camera options but it's as if it does not see anything from the lens (had done camera fw update on it. You can download it from Samsung Apps app)
- When viewing "Contacts" can't press Back button to exit it so I just press Home button. Small bug
- can't set up smtp outbound email settings on stock email app. Keep getting it can't connect with server even when manually inputting correct settings.
- Battery undetermined as i've been playing with GPS a lot testing it so it drains pretty quick.
- GPS - Had no problems with 2.1 (using GPS + "Use wireless networks") but it's been horrible on 2.2. Locks ok when stationary, fluctuating between 5-9 satellite locks (used lbstestmode to check) but when you are moving or when using it for Navigation, it will be ok for a short bit then would eventually start bouncing all over the place or start getting weak/lost locks. Was using it on the hwy one time and it would suddenly tell me to do a u-turn because it thought I was on a side road. (condition was clear and phone was by windshield).
What it did fix for me:
- Opening Gallery before would sometimes lock up the phone requiring battery pull in 2.1. Fixed for me with 2.2
- Running latest updated Maps would sometimes lock up the phone requiring battery pull in 2.1. Fixed for me with 2.2 but still somewhat useless because of issue mentioned previously.
I can live with all the bugs except for the abismal gps.
So, I've been having issues with my TF101 for a while now. At first I thought it was ROM related, but I've seen this issue across a couple different ROMs, including the stock ICS update. The issue is that frequently, the launcher will crash and restart when swiping off the main homescreen. Other times, the UI overlay will crash. That is to say, the icons and everything will vanish, but the background will still be there. Sometimes a widget might be frozen on the screen (it's visible regardless of swiping, and you can't interact with it). I can still swipe, the background is still visible scrolling, and if you know where something should be, you can even tap it and it will open. Has anyone else experienced this? I've noticed the issue in the stock ICS launcher, Apex, or Trebuchet. When it happens, I either have to restart or at least re-apply the system them. Even the lock screen UI vanishes.
FWIW, my TF101 is a B60 unit, rooted, running RaymanFX's CM10 (4.1.2) ROM, and TWRP.
So no one's seen this kind of issue before?
I have a similar problem. Hitting the "home" button (it never disappears) solves the problem, no need for other apps or reboot or anything. I just plain hit the home button and everything reappears.
TheQuicksilver said:
So no one's seen this kind of issue before?
Click to expand...
Click to collapse
Sometimes, my UI vanishes, but if I wait about 10 seconds or so, it comes back. I guess the launcher crashes, but is automatically restarted by the kernel. I use the K.A.T kernel, maybe that is better with the re-launch when it crashes?
Hi guys. Apologies if this has been asked before, but I couldn't find anything that was exactly this issue.
Galaxy S3 running Alliance rom v22 with (though I had the same issue with v21).
Using Nova Launcher 2.3 or TW Launcher (haven't tried any other launchers)
When closing an app or the app drawer using the home button, many times the screen just goes black. I have to hit the power button to turn the display off, then again to turn it on to get anything to show on the display. I thought it may have been something with the Nova Launcher, so I tried TW, and had the same issue. I have done multiple clean wipes and installs with this and the v21 Alliance rom. Not sure it matters, but I am currently using the Beans Stock kernel, but saw the same issues with the Lean kernel.
This happens at least 10 times a day and is getting very aggravating, to the point where I went back to the 4.1.3 Jelly Beans rom after trying v21. I came back when v22 was released hoping something may have changed. Does anyone have any ideas of settings I might change or something like that that could fix this? Thanks!
I currently have an N5 which is running PA (4.5 beta2) and Franco (R59) and i seem to come across this issue no matter what version (or combination of versions) i end up using.
The issue - After installing the rom and kernel it will work fine for a week or so and then after that period it will have this issue whereby I press the power button and nothing will happen to the screen, it just stays black but i know the phone is still on because the LED will flash. From this point onwards i usually just reset the phone and then it will work fine for the first maybe 20 mins and then it ends up doing the same thing again.
I know it isnt a problem with the power button itself cause it works totally fine after the phone resets (and im still able to reset the phone using the power button), sometimes the screen will actually power up when i press the button and it shows me my home screen but then fade to a black screen and it just does that over and over again (during that period you cant actually do anything, tried touching screen, volume up+down etc and there is just no response) unless you reset the phone.
any help would be appreciated
It could be one of a few things. Generally it will be an app or a kernel setting. I would recommend ruling out kernel first by flashing ROM without the kernel.
Sent from my Nexus 5 using Tapatalk
Yeah that definitely seems like a kernel issue. Try just flashing the rim by itself as mentioned above. Also what apps do you have install that deal with display stuff, ex. Lock screen notifications, led light etc.?
nym27jrey said:
...Try just flashing the rim...
Click to expand...
Click to collapse
Not sure you want to do that
hi guys, im pretty sure i have found the source of the problem now. I normally have the 'Twilight' app (nothing to do with teenage vampires + werewolves) in the background which softens the colours and dims the screen to a level which is more pleasant for the eyes at night. After uninstalling this it seems as though the problem has gone.
I think the app itself projects an overlay on top of the launcher to dim the screen but sometimes when the app is running and the screen is dimmed it seems to block out (unable to tick) some of the pop-up boxes which some programs throw up. Too bad, i really liked the app too, might just have to email the developer and let him know.
Now on to my next problem, anybody know of another app which does similar? lol
ticketseriously said:
Now on to my next problem, anybody know of another app which does similar? lol
Click to expand...
Click to collapse
Chainfire's C.F. Lumen
OK I was wrong. After uninstalling all the apps which have an effect on my display as well as reinstalling the ROM without the Franco kernel its still having the same issue.
I left a music app running this time and then left the phone till it put itself into sleep/lock mode. The app continued to run and I could change the volume with the side buttons but when i Pressed to get the screen on it just stays black now but it seems as though everything is still running in the background. Anybody had this type of issue with PA before? Thanks
One last question on the kernel, do you have any tweak apps running?
Sent from my Nexus 5 using Tapatalk
ticketseriously said:
OK I was wrong. After uninstalling all the apps which have an effect on my display as well as reinstalling the ROM without the Franco kernel its still having the same issue.
I left a music app running this time and then left the phone till it put itself into sleep/lock mode. The app continued to run and I could change the volume with the side buttons but when i Pressed to get the screen on it just stays black now but it seems as though everything is still running in the background. Anybody had this type of issue with PA before? Thanks
Click to expand...
Click to collapse
its sod, sleep of death. its not really known what causes it on the n5, but it happens. raising your voltages might help you, as it helps a few, but not all. if it happens that often, id see about an rma after flaahing the factory img to test.
Running beta software, custom kernel... Seems you're in for more that what you've bargained for.
Just do as simms22 says and flash latest factory image.
Anyone else having this issue? Basically, if my phone has been asleep for any amount of time (more than 10-15 mins), when I first wake it, the screen is unresponsive. I can usually put it back to sleep and wake it again to use the screen but sometimes it'll take multiple attempts for it to work. I have this issue regardless of how I wake the phone (finger scanner, power button, double tap) and the only way I can use the screen is to put it back to sleep and wake it again.
I have an unlocked bootloader, root, ElementalX kernel, tether hack in build.prop, maybe other mods that I can't remember. I'm not saying that this isn't something that I've caused and I feel sure a clean install would help but since TWRP is still buggy (backup/restore function not working properly) I've been hesitant to flash any roms or reset my Pixel. I will wipe and reinstall if absolutely necessary but I prefer to isolate the issue and fix it if anyone knows what's causing it. I have a Verizon variant on Android 7.1.1 NMF260.
Sent from my Pixel using Tapatalk
joshw0000 said:
Anyone else having this issue? Basically, if my phone has been asleep for any amount of time (more than 10-15 mins), when I first wake it, the screen is unresponsive. I can usually put it back to sleep and wake it again to use the screen but sometimes it'll take multiple attempts for it to work. I have this issue regardless of how I wake the phone (finger scanner, power button, double tap) and the only way I can use the screen is to put it back to sleep and wake it again.
I have an unlocked bootloader, root, ElementalX kernel, tether hack in build.prop, maybe other mods that I can't remember. I'm not saying that this isn't something that I've caused and I feel sure a clean install would help but since TWRP is still buggy (backup/restore function not working properly) I've been hesitant to flash any roms or reset my Pixel. I will wipe and reinstall if absolutely necessary but I prefer to isolate the issue and fix it if anyone knows what's causing it. I have a Verizon variant on Android 7.1.1 NMF260.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
If you use ElementalX, did you disable the stock moves? You should enable either gestures from EX, or stock, not both.
quangtran1 said:
If you use ElementalX, did you disable the stock moves? You should enable either gestures from EX, or stock, not both.
Click to expand...
Click to collapse
I have moves enabled in the kernel and I've tried enabling and disabling them in the stock features, which hasn't made a difference. I'm going to re-flash the kernel and disable it at the kernel level to see if that helps. The only thing I'll leave on is swipe to sleep.
Sent from my Pixel using Tapatalk