For some reason my home button has started opening the desk app using evil fascination 3.5 and 3.6. I just odined back to DI01 and still no change. I figured going back to DI01 was a complete wipe back to stock. Any ideas what may be causing this?
Related
I just flashed double rainbow onto my android which was running sweet honey and now I get a looping startup, where its as follows
Samsung Vibrant Logo
Black (with some funny robotic sound)
A screen of broken images(like random lines )
reboots and repeat
Does anyone know how to remedy this problem? I just got my phone 3 days ago =(
The only way to fix this is to Obin back to stock. I always recommend to Obin to stock before flashing any ROM. This is just to make she you don't have any leftover pieces of the other ROM help with a clean install. Good Luck and you next flash
Sent from my SGH-T959 using XDA Premium App
Hey guys I did a quick search but couldn't find anything specific. Randomly, the Y, H, and B keys on my atrix have stopped working. When I hit them I sometimes get nothing, or sometimes it gets the key next to them. If I try and swype across them, it will stop right at that line that all these keys are on. Any ideas on what this might be and how to fix it? I have rebooted and cleaned the screen. I'm running Cognition beta rom (had to flash back from CM7 in an emergency using CWM).
I'm really hoping this isnt a fried digitizer...
After multiple fails with MTD based ROMs (sdcard issues), I've settled in to TSM resurrection 1.0 (EI20). One thing I can't find mentioned in the ROM thread is a problem I'm having where the screen will randomly turn itself on from sleep. Usually when this happens and I try to push the power button to turn the screen back off, it won't turn off, but instead takes a screenshot. Has anybody else encountered this issue or know what to do with it?
I'm running TSM resurrection with the base kernel from PWGB, no other mods (XIX, heap size, etc). I don't know if this is related, but my battery usage also shows that the email app has been awake for 18m. Could there be a problem with that app that is causing the screen on issues?
I had the exact same issue as you which sadly made me revert back to PWGB with GeeWiz kernel. The screen capture happened all the time for me (it was the worst in the car dock). From my troubleshooting I was not able to fix it (tried different kernels, task killers, etc.). The closest thing I could pin point was it had to do with the soft key back button. The phone thought I was holding down the back button and I would hit the lock button which would cause the screen shot. As far as the screen coming on, I have had that issue with multiple ROMs, but it never really caused problems for me. Hopefully this helps a little.
I'm not sure where off the top of my head, but there is a screenshot.apk you have to delete to stop the phone from taking screenshots. It's been discussed a few times on xda where. Maybe search for it?
"better to be safe than to be odining" -me
Odd. That was happening for awhile, but not since I wiped data, reflashed, and installed the most recent TKSGB kernel.
When it does happen, push the back button. It should stop the screenshots.
I have searched the forums and not found an answer so I am posting a question.
I flashed Aura ROM and been very happy for a very long time then suddenly the notification bar wont pull down.
The only thing I can think of is that I tried to use the Entertainment Dock and, although the phone went into entertainment mode, the TV remained blank, I unplugged and got on with my life.
I have since tried wipe (data/cache/dalvik), reflash Aura, wipe reflash Aura w/Bl, wipe reflash Home, flash update, flash theme, wipe...
After the above I went to restore a previous backup and got an MD5 Sums Mismatch. I repaired the backup and restored...still the problem persists.
Any ideas would be welcome. I am getting concerned that I have managed to ruin a fantastic phone.
I can confirm that there is no problem with the screen, that portion of the screen responds to swipes across and moves the desktop, just not the notification bar.
The really weird bit is that the buttons stop working, if I run my finger across from one side to the other then the screen responds (my home screen moves around).
If I go into landscape then the pull down works but the buttons are still shot and back to portrait doesn't help.
Standby and back seems to fix it (I do not have to power off).
Any help is greatly appreciated.
Thanks
Jez
Quick update (problem persists)
I used multitouch tester to see what was happening when I dragged down the notification bar. When functioning correctly it see's one finger as one. When going wrong it sees the finger at the top of the screen as two / three / four separate presses. When I drag the one finger down the extra points stay at the top. I guess this is why the notification bar doesn't go down.
Jez
Hardware Fault
I have decided that this is a hardware fault and so I am desperately trying to hide the "unlocked" text and return the device
...or brick it in the process
wish me luck...
jezarius said:
I have decided that this is a hardware fault and so I am desperately trying to hide the "unlocked" text and return the device
...or brick it in the process
wish me luck...
Click to expand...
Click to collapse
Just flash a GB SBF to remove the unlocked and you don't have to worry about bricks as long as you don't attempt to flash a froyo SBF. Don't worry if it doesn't boot after flashing the SBF. Just ssend it in. That's what I did.
Sent from my MB860 using xda premium
d3athsd00r said:
Just flash a GB SBF to remove the unlocked and you don't have to worry about bricks as long as you don't attempt to flash a froyo SBF. Don't worry if it doesn't boot after flashing the SBF. Just ssend it in. That's what I did.
Click to expand...
Click to collapse
I actually did the motorola update from their software update tool. It removed the "unlocked" text, put the T-Mobile startup animation back in and soft bricked it.
I have now sent it off for repair...three weeks
Thanks for the comment
I've rooted my phone and flashed it back to stock 4.4.2 (TWRP recovery) because I wanted more freedom than 5.01 gave me. Everything workeds fine until it did an OTA upgrade back to 5.01.
At this point the back button stopped responding (menu button was fine). When I pressed the menu button both of them lit up, but the back button still did not respond.
I put it back to 4.4.2 again and the buttons worked just as they should, but again after an OTA upgrade the back button stopped responding. Getting tired of this, I flashed various other ROMs from Stock 5.1 to CM12.1 and whichever one I choose the same problem occurs. Only when I put it back to 4.4.2 does everything work normally.
I know I'm not the only one who has experienced this and I'm told that Samsung is aware of it happening in a very few cases, but no cure has appeared and it is getting really frustrating. Today I flashed a really great-looking ROM, which is a port from the S6 for the S4. There are one or two little issues with it, but guess what? Yes, the back button is disabled again. I have switched on the accessibility menu option, which puts a floating icon on the screen which when pressed has a few options, one of which is to go back, but this is only a workaround kludge not a solution to the problem.
Is there an expert out there that can tell me what all the later ROMs have in common which disables the back key? There is nothing intrinsically wrong with the key mechanism, such as it is, because it works perfectly under 4.4.2. I have the feeling that since this only affects a relatively few S4's the problem will not be progressed.
Does anyone out there know what is going on and can anyone help me, please?
KC