Evr since I flashed the latest 2.3.4 my back button doesn't work sometimes. I'm not sure what it is if anyone has an idea thanks?
Related
Hi there!
I'm new to this whole thing, however I managed, with some help from a friendly guy on the IRC channel to get my device rooted. First thing was to downgrade my firmware as it was too high (1.84) to 1.34, I think. After this downgrade I noticed that the keyboard has become buggy and the WiFi not working.
I then flashed a new ROM (wiping first etc) built on firmware 1.85. The problem with the _Keyboard_ persisted, the WiFi issue was now fixed. Then I installed CM 7.0.3 (wiping first etc) and it works wonderful, however the keyboard issue still persist...
What I mean when I say the keyboard is buggy:
It's only a few letters to the right of the keyboard, and I think the keys are, I, K, M, L, O and P. Sometimes it will not react when pressing the key other times it will print out the letter TWICE. The problem persists in caps lock mode, but IS NOT an issue when being in FN / ALT mode (Special-characters-mode)
I did not drop the phone or anything, and have never-ever experienced it like this before. But I felt this bug like 5 minutes after downgrading...
I really do not hope this is a hardware issue.
Regards
Hey guys,
Just wondering if anyone else on the Rogers Galaxy S3 is experiencing this same issue after updating to Rogers Jelly Bean 4.1 update, or loaded the rooted JB 4.1 software. I've factory reseted my phone 3 times now. Same issue. I'm on rooted JB 4.1
I've called both Rogers and Samsung, they say theyve never heard of this. Told me to Factory Reset. I've done this 3 times now
Phone has NEVER been dropped.
Weird thing that happened last night with the official update. And has never happened before. When the screen is completely off, we usually wake it up by pressing the home button. Well its happened a few times where I pressed the home button (not super hard) but screen doesnt turn on. Press it again a few secs later same amount of force, and screen turns on. This never happened on ICS stock Rogers.
I'm not sure if its my phone or something with JB.. I'll try to take battery out and place it back in and see if it does this same thing again
Another member on a different forum has replied that this was an issue on the Cyanogenmod10 ROM as it was ported from the Jelly Bean 4.1 ROM:
FWIW the home button not consistently waking up the phone is a prevalent issue on CyanogenMod 10 (which is based on Android 4.1). I had the issue on CM10 but I haven't experienced it since switching to AOKP.I've called both Rogers and Samsung, they say theyve never heard of this. Told me to Factory Reset. I've done this 3 times now
Click to expand...
Click to collapse
Any CM10 issues are not related to TouchWiz. They are two different worlds. CM10/AOKP are based on AOSP which is vanilla Android, there is no Samsung code in there at all.
Have you loaded ICS back on to see if the issue still exists? Are you able to warranty your device in case it might be a hardware issue?
There is something called "Power" button... it was made for unlocking the screen beside powering function....
Download Rogers stock ROM and flash, it should fix.
Tony_YYZ said:
Any CM10 issues are not related to TouchWiz. They are two different worlds. CM10/AOKP are based on AOSP which is vanilla Android, there is no Samsung code in there at all.
Have you loaded ICS back on to see if the issue still exists? Are you able to warranty your device in case it might be a hardware issue?
Click to expand...
Click to collapse
The thing is I've never dropped this phone since getting it in Nov. So I dont think its hardware issue. Then again I'm not a phone tech. Is it possible to load back on Stock Rogers ICS through Odin again? Same process as rooting? I have stock recovery and not clockwordmod
Thanks for the input
yulet said:
There is something called "Power" button... it was made for unlocking the screen beside powering function....
Download Rogers stock ROM and flash, it should fix.
Click to expand...
Click to collapse
Yes I realize I can wake the phone up from pressing power button. May'be I'll just do this from now on. I'm guessing most ppl wake their phones up by pressing power button as well?
I'll load back on the Rogers stock ROM ICS and see if the issue is still there.
Thanks for the input
If you bump up the min cpu speed from 386 to 486, either through the ROM settings or an app like SetCPU, this seems to resolve the problem.
BenW23 said:
The thing is I've never dropped this phone since getting it in Nov. So I dont think its hardware issue. Then again I'm not a phone tech. Is it possible to load back on Stock Rogers ICS through Odin again? Same process as rooting? I have stock recovery and not clockwordmod
Thanks for the input
Yes I realize I can wake the phone up from pressing power button. May'be I'll just do this from now on. I'm guessing most ppl wake their phones up by pressing power button as well?
I'll load back on the Rogers stock ROM ICS and see if the issue is still there.
Thanks for the input
Click to expand...
Click to collapse
Go here: http://forum.xda-developers.com/showthread.php?t=1739426
Follow those instructions on how to flash a stock ROM. You can find the ICS factory software at www.sammobile.com Or use the rooted versions provided by MrRobinson
---------- Post added at 03:00 PM ---------- Previous post was at 02:54 PM ----------
goodtimes50 said:
If you bump up the min cpu speed from 386 to 486, either through the ROM settings or an app like SetCPU, this seems to resolve the problem.
Click to expand...
Click to collapse
OP is running TouchWiz and therefore cannot alter these settings. Those apply to the CM10/AOKP home button issue. Although what OP is describing is similar it is not the same....unless OP has CM10 or AOKP installed prior to installing the official JB update and didn't mention it in his first post.
Tony_YYZ said:
Go here: http://forum.xda-developers.com/showthread.php?t=1739426
Follow those instructions on how to flash a stock ROM. You can find the ICS factory software at www.sammobile.com Or use the rooted versions provided by MrRobinson
---------- Post added at 03:00 PM ---------- Previous post was at 02:54 PM ----------
OP is running TouchWiz and therefore cannot alter these settings. Those apply to the CM10/AOKP home button issue. Although what OP is describing is similar it is not the same....unless OP has CM10 or AOKP installed prior to installing the official JB update and didn't mention it in his first post.
Click to expand...
Click to collapse
I was running stock Rogers ICS 4.0.4 then updated to JB 4.1 via Kies. Then rooted with a stock Rogers JB 4.1 ROM
Never had any custom ROM's. I will load up the stock Rogers ICS and see if the problem still persist. Will report back
Thanks again for the help guys :good:
This happens on my AT&T GS3 since the Jelly bean update, but I think it is due to the root. It's no big issue, I never use the home button anyways to unlock the screen.
Bump
I took the time yesterday to load back on the stock Rogers ICS 4.0.4 ROM and played with the home button for several hrs (4hrs) at random times pressing the home button to wakeup the phone. Everytime I pressed the home button it would wake the phone up without issues. I can conclude that ICS had no issues with waking the phone up via home button.
I then reloaded back my JB 4.1 w/root and the home button glitch reappeared again.. Its a minor inconvenience. But I now use my power button to wake the phone up anyways.
goodtimes50 said:
If you bump up the min cpu speed from 386 to 486, either through the ROM settings or an app like SetCPU, this seems to resolve the problem.
Click to expand...
Click to collapse
REALLLLLLY? thats interesting will be testing this now...
JWC59382 said:
This happens on my AT&T GS3 since the Jelly bean update, but I think it is due to the root. It's no big issue, I never use the home button anyways to unlock the screen.
Click to expand...
Click to collapse
This has definitely been happening to me on my AT&T SG3 too. Will be testing the above suggestion with my MIUI.US ROM.
Hello guys,
Long time reader/user, first post...
Here is the story... On a concert last week, my GF's Galaxy S3 fell into one big beer glass... it was an accident, nothing to do about it.
After we cleaned all we can in site and let it dry for 24 hours, we turned it on and found the screen was damaged... damn... ok, I got a working screen from a friend and replaced the original... At first everything was OK, but after some 8-10 hours, the screen started to go blank on random events (pressing the apps button, opening an SMS, pressing the power button to lock, and several other actions)...
We did a factory reset, it worked for a while and then failed again... removed the battery and put it back on... worked for some time and then it happened again...
As it was recently upgraded to 4.3 (TCE) software, and it stops happening from time to time, I thought it was a software issue, so then I reinstalled the stock firmware using Odin... it worked for 8-9 hours and then it happened again.
Then, I rooted the device and installed CM 10.2 ... Worked fine again for a while and then it got even worse.
Tried to install Stock ICS (4.1.1) firmware downloaded from sammobile.com, but the install failed and the phone was soft-bricked.
Used Odin again to install 4.3 stock firmware again and it worked... for some hours again...
Tried using a different battery... same issue... removed the SDCARD... same issue...
I still think the stock ICS 4.1.1 (TCE) firmware may work, but unfortunately I cannot find it to download... all the sites (including posts here on XDA) direct to a link on "Hotfile", that unfortunately was taken down by the goverment for piracy issues.
I'm out of ideas now, so, if you guys have this firmware, please help me sharing it, or if you have other ideas to troubleshoot this issue, it will be greatly appreciated... my GF has only one month with this phone and is very frustrated.
Thanks in advace. Kind regards,
--
Bureizu (Xperia S LT26i - LB - JellySlim_FullPower)
[BUMP 25/12/2013]
Hey guys.
No response yet? Help please.
Ok, cleaned all the apps installed by Google Play from the computer... flashed back stock JB... and we're installing apps one by one... problem reappeared but less frequently...
I'm thinking memory issue... not really sure...
If anyone has some advice, it will be greatly welcome...
Is anyone else having issues wirh the home button not working? Occasionally the recents too. Its driving me bananas, i have had this tablet for over a year and use the crap out of it. Now i have to restart all the time which usually doesnt solve anything. Is this googles way to make me have to buy a new tablet??
How did you install 5.0.1? Flash or OTA? If you flashed it using TWRP, make sure you're using TWRP ver. 2.8.2.2. I heard this solves your problem.
OTA, i did a factory reset and it seems to have solved the issue so far. Thanks!
Looking for suggestions....
My home button doesn't do anything ever since I did and flashed to Ironrom
Have rebooted
My mic also stopped working but that started a while back when I switched to cyanogenmod 12.1
Anything I can try?
Details:
Sm-t800
Ironrom 2.4
Why us the problem rooting when you've stated it's happened since you changed roms?
Iirc there is a setting to disable the home button. Check that.