Related
I think on every ICS ROM I have tried for the Galaxy Tab 10.1 there is a bug that sometimes occurs when you wake up the tablet and get the lock screen. You cannot unlock the tablet because the touch screen is not working. Sometimes if the tab goes back to sleep and you wake it up again, touch works. Other times, the tab will never go back to sleep and eventually ends up in a boot loop. This bug has been mentioned in a few topics as well.
What I'm wondering is, what causes this and is anyone working on a fix? I see lots of people who keep asking "does the camera work yet?!" but this particular bug is more annoying than a camera that does not work. I've been staying on top of the ICS development topics and I only see people reporting the problem, but no mention of a solution or that something is in the works.
So, does anyone know anything about this? It seems to affect all ICS ROMs (at least all CM9 based ROMs). I do not believe it is one kernel vs another as I have tried different kernels too. Any feedback is much appreciated.
yes happens to my 10.1 all the time as well. Not sure the root of the cause. Should probably pull up the logcat and see what the deal is.. Probably some sleep mode issue not letting it recover the touch driver or something.
+ 1 same issue
ganiman said:
I think on every ICS ROM I have tried for the Galaxy Tab 10.1 there is a bug that sometimes occurs when you wake up the tablet and get the lock screen. You cannot unlock the tablet because the touch screen is not working. Sometimes if the tab goes back to sleep and you wake it up again, touch works. Other times, the tab will never go back to sleep and eventually ends up in a boot loop. This bug has been mentioned in a few topics as well.
What I'm wondering is, what causes this and is anyone working on a fix? I see lots of people who keep asking "does the camera work yet?!" but this particular bug is more annoying than a camera that does not work. I've been staying on top of the ICS development topics and I only see people reporting the problem, but no mention of a solution or that something is in the works.
So, does anyone know anything about this? It seems to affect all ICS ROMs (at least all CM9 based ROMs). I do not believe it is one kernel vs another as I have tried different kernels too. Any feedback is much appreciated.
Click to expand...
Click to collapse
Oh wow! Did you make this yourself? Downloading and flashing now! Great work, dev!
Questions go in the Q&A section
Thank you for moving this to a place where topics go to die. This sort of question needs the attention of devs, not to be ignored in a forum hardly anyone looks in. Your system is broken.
ganiman said:
Thank you for moving this to a place where topics go to die. This sort of question needs the attention of devs, not to be ignored in a forum hardly anyone looks in. Your system is broken.
Click to expand...
Click to collapse
Welcome to XDA, new guy. XDA began as a dev-only forum; the general and Q+A subforums came later, and only to keep the important stuff uncluttered. You need to understand that if you're going to use these forums, you go by the rules; if you don't like it start your own forum. The rest of us like it that the dev forum enjoys special status.
BTW- if you want a dev to read your bug reports (and they'd be happy to do so), post in the ROM thread or IM them directly. The devs are friendly folk who do this for free; respect them and their forum and they'll respect you.
I just came here to mention the bug. It isnt the first time I experienced it, but it got to the point today where the tab wouldnt unlock at all after attempting for a good 3-5 mins of constant hitting the power button and trying to move the icon; and then trying the power button to power off the tab and the button on the screen wasnt working either for me.
flash latest cm9 nightly.
then flash this:
http://droidbasement.com/db-blog/?p=2591
observe if its better.
You want to talk about bugs in your lock screen heres a real bug problem that not even ics can fix http://forum.xda-developers.com/showthread.php?t=1641464
Just got my EVO LTE. I really like it but have always been used to having the 4 buttons at the bottom. The one I used a lot was holding down the search button to activate the voice command to Navigate to address, reply to a text.
Is there any quick shortcut that this phone has to get to that voice command. I did place the app on the homescreen but it launches then you need to press the microphone button again.
Can you reprogram the camera key to launch that instead?
Thanks.
U may find a dev to remap the buttons for u. But u will have to root at the least and get on the good side of a dev. Donations never hurt.
There are definitely options like this in the CM10 nightlies. That will require you to root the phone, and flash a different ROM though. If you plan on rooting and flashing a different ROM at some point, then I'd say no time like the present. But if you're not comfortable with that sort of thing, or would rather stick to the stock ROM, you'll have to find a different solution.
You're definitely asking in the right place, though. If it's possible on the stock ROM, someone here will know about it. And if it isn't, someone will know that, too.
Anyway, like I said, you can definitely do this in CM10. On other ROMs, I'm not certain, though it's quite likely some of them will let you do what you want. On stock, without root, it may be impossible to remap the buttons (and I have a feeling that's probably the case).
Talamor said:
There are definitely options like this in the CM10 nightlies. That will require you to root the phone, and flash a different ROM though. If you plan on rooting and flashing a different ROM at some point, then I'd say no time like the present. But if you're not comfortable with that sort of thing, or would rather stick to the stock ROM, you'll have to find a different solution.
You're definitely asking in the right place, though. If it's possible on the stock ROM, someone here will know about it. And if it isn't, someone will know that, too.
Anyway, like I said, you can definitely do this in CM10. On other ROMs, I'm not certain, though it's quite likely some of them will let you do what you want. On stock, without root, it may be impossible to remap the buttons (and I have a feeling that's probably the case).
Click to expand...
Click to collapse
Like I said, u will need to root to remap your buttons. But it is possible on sense roms, fairly easy to figure out as well. U will just need someone with more knowledge than random idiots to do it for you.
Out of nowhere, the bottom buttons stopped working today. I was on a Sense ROM (ICS Business) and I figured it was just software related. I tried 5 or 6 different ROMs, even went back to stock. Has anybody else had this issue before? If so, is it hardware or is there a way to get this working again?
For the interim, I just installed an AOKP Rom (Neo 1.5 Linaro) because it offers the software replacement navbar. Out of curiousity, does anybody know what other ROMs may offer the same software replacement?
I was going to look at Neo Rage (1.6 Linaro), but it's listed as AOSP and I'm not sure it offers them or not. I assume there are no Sense based ROMs that offer this?
Thanks!
-J
In any AOSP rom you can enable the soft keys. Some roms you have to manually edit XML files to get them though. In sense, you can't add them
Thanks. I'll poke around some other AOSP ROMs as well. I never really paid attention to them mainly cause I had no use for them heh. Now I really don't have much of a choice.
AshtonTS said:
In any AOSP rom you can enable the soft keys. Some roms you have to manually edit XML files to get them though. In sense, you can't add them
Click to expand...
Click to collapse
Please Ashton, do some fact checking.
xjacobx made softkey mods for early Sense ROMs (like back in January).
Edit:
And here's the thread
http://forum.xda-developers.com/showthread.php?t=1466143
nablicsu and
vgjunkie said:
Out of nowhere, the bottom buttons stopped working today. I was on a Sense ROM (ICS Business) and I figured it was just software related. I tried 5 or 6 different ROMs, even went back to stock. Has anybody else had this issue before? If so, is it hardware or is there a way to get this working again?
For the interim, I just installed an AOKP Rom (Neo 1.5 Linaro) because it offers the software replacement navbar. Out of curiousity, does anybody know what other ROMs may offer the same software replacement?
I was going to look at Neo Rage (1.6 Linaro), but it's listed as AOSP and I'm not sure it offers them or not. I assume there are no Sense based ROMs that offer this?
Thanks!
-J
Click to expand...
Click to collapse
Did you run any of the mods to dim the lights? I know I run a mod that scripts this change and I wonder if that's sticking and not playing nice with the other roms. Do you have anything for dimming the lights in:
/system/etc/init.d? if so maybe remove that
wlmeng11 said:
Please Ashton, do some fact checking.
xjacobx made softkey mods for early Sense ROMs (like back in January).
Edit:
And here's the thread
http://forum.xda-developers.com/showthread.php?t=1466143
Click to expand...
Click to collapse
ehh, I didn't know that thanks!
Ok, looks like I am not the only one, sorry to dig up this old thread, but my Capacitive Buttons stop working today.
I did not install any app, or made any changes and had been using the same (Niles Business 3.6) ROM since Jan.
I never have that dim Capacitive Buttons script.
I did not drop the phone recently either.
I am going to try INFECTION and see if it can tie me over until I get a new phone.
Oj, my guess here is something happened to the digitizer or digitizer ribbon cable. Have either of you had your phone disassembled anytime? If it's not the digitizer and software related, a hard reset or new ROM install should have fixed it no questions asked......
unless some other piece of hardware in this phone has taken a dump. .?
No, the phone had never been taken apart. The only thing that happens to the Rezound, was that I dropped in about 3 ft on asphalt, and it only had a few minor rash on the frame (the shiny part), and that happened many months before the capacitive buttons died.
I am added the info below to hopefully help others that have this issue.
Installed INFECTION, followed Neo's direction (below), and it has a usable phone again.
IAmTheOneTheyCallNeo said:
Add this to your build.prop, fix permissions, then reboot
qemu.hw.mainkeys=0
That will get you a navigation bar
Sent from my Rezound using xda premium
Click to expand...
Click to collapse
I recently flashed my Samsung Fascinate with PowerWashed Team's PWGB Version 2.0 (Beta 3). I'm terribly new to using custom ROMs, but I'm quite pleased with the results. I've only had one concern with this ROM regarding the back light on the soft keys. They light up every time I touch my screen or press a hard key.
I've attempted to find a setting for this in the OS and in CwM Voodoo Lagfix Recovery v2.5.1.x screen, but wasn't able to find such a setting (Again, I'm very green so it could be right under my nose and I simply don't know it.)
I also attempted to install myriad apps to keep the back light off on screen touch including:
Screen Filter (No effect)
Night Mode (No effect)
Light Flow Lite - LED Control (No effect)
Light Manager - LED Settings (This app actually stops the back light from coming on, however it's unpredictable and works >15% of the time)
I've also done a lot of searching on the matter. I've seen where others have stated the problem, but none where there was a solution or enough information for me to further investigate a way to fix this. It's also been complicated to find information due to a variety of search terms (soft keys, led, etc.) yielding results about the camera or other things that are unrelated to my issue coupled with my lack of direct knowledge on the matter.
I'd really appreciate any advice on either directly fixing this or a source of information so I may learn more from what is causing this behavior and fixing it myself. Thanks, everyone for all the time and effort you've put in for making things like this accessible to individuals like me. I can't tell you how much I appreciate it.
This behavior is a product of the kernel, and most people find it desirable. If you install the kernel control app nstools, you should see an option called cmled timeout, allowing you to set the led backlight timeout.
Posted from my Galaxy Tab with CM10
MultipleMonomials said:
This behavior is a product of the kernel, and most people find it desirable. If you install the kernel control app nstools, you should see an option called cmled timeout, allowing you to set the led backlight timeout.
Click to expand...
Click to collapse
Thanks for the information! Unfortunately, the ROM I flashed has a stock kernel and doesn't offer this option. So, I suppose that's the first thing I need to address, but now I know where the problem lies! Thank you so much for your time and input, I'll put it to good use.
Are you saying the back lights light up even if you just touch the screen? That's strange, they only have ever lit up for me when I actually touch a soft key or hit the power button to wake the phone up.
Well good luck, I'm not sure what kernel is best for GB as I started flashing custom roms during ICS and I'm now on Jelly Bean and never going backwards.
Crawshayi said:
Are you saying the back lights light up even if you just touch the screen?
Click to expand...
Click to collapse
Yes, exactly this. It is really odd and very bothersome when trying to read at night. Even if I use the volume rocker to turn the page the lights will come on. It's maddening. I'm currently looking at the kgb kernel, but I think the nstools led option isn't actually going to address this quirk. (Directly, I believe I will end up disabling the led altogether)
If you don't mind, what rom did you choose?(Ignore, I was on mobile and did not see your signature at the time)
How has the performance been? I'm interested in doing the same, but was afraid my fascinate wouldn't handle jb very well.
Well needless to say it's different for everybody when it comes to roms, sometimes your phone will have no problem running a certain rom where as someone else's might not even boot. As for myself I've been pretty fortunate and have been able to try any rom I've wanted to with success, and I'll give you a few of my thoughts on it.
If you're wondering about performance, well simply put JB blows everything else away and runs like a dream on the Fascinate. Once you spend a few days with it you'll never want to go back honestly. Even on our aging hardware, it runs amazingly fast, even without kernel performance tweaks.
Anyway, as far as roms go, if you're most concerned with stability and reliability then I would highly suggest CM10 (whatever the latest nightly version is). Of all the roms I've tried, it's by far the one that's given me the least hassle. That said, I'm quite fond of the tweaks offered in AOKP, mainly the voltage settings (for battery life) and the fact that it seems to vibe much better with Devil kernel than CM10 does. I've been running my current rom/kernel for a couple of weeks now, and I'm happy enough with how it's running to keep it as my daily driver for a while.
This isn't to say the GB roms aren't any good, because of course they are, but considering how nice JB roms run on our phone you'd be doing a disservice by not at least giving them a shot.
Crawshayi said:
If you're wondering about performance, well simply put JB blows everything else away and runs like a dream on the Fascinate. Once you spend a few days with it you'll never want to go back honestly. Even on our aging hardware, it runs amazingly fast, even without kernel performance tweaks.
Click to expand...
Click to collapse
You sold me on the idea of JB. Flashed it today, and I love it so far. Plus, my soft key lights aren't constantly on! Win-win.
Thank you so much for the guidance. Your input helped turn a satisfactory experience with ROMs into a trully positive one.
Glad to hear you liked it man, I was reluctant at first too due to (at the time) no 'official' releases, but I'm glad I made the jump. I'm quite enjoying AOKP M1 and will probably stay on it for a long time. Which rom did you end up trying?
Crawshayi said:
Glad to hear you liked it man, I was reluctant at first too due to (at the time) no 'official' releases, but I'm glad I made the jump. I'm quite enjoying AOKP M1 and will probably stay on it for a long time. Which rom did you end up trying?
Click to expand...
Click to collapse
I was really impressed with your review, so I chose to go with the same rom. It also seemed like the most stable option and easiest for me to understand the installation procedure (very important for me since this is my only device and more than just my daily driver, it's my life line). I had been extremely hesitant to go to JB for fear of junking my phone up, but I'm really glad I took the extra risk. I just needed an extra bit of encouragement. Thanks again for all your input!
If you managed to install AOKP smoothly you can pretty much install any rom the same way, basically meaning wipe data and cache/davlik then flash whatever you want to. Luckily this phone happens to be very hard to break, and you'd have to do something pretty extreme to brick it. I highly recommend Titanium backup pro so you can just backup the apps you want, and restore them in no time when you're trying different roms. Also, I've been using some voltage settings that make battery life insanely good, so if you're interested in doing that let me know and I'll post them.
olalaelaine said:
I was really impressed with your review, so I chose to go with the same rom. It also seemed like the most stable option and easiest for me to understand the installation procedure (very important for me since this is my only device and more than just my daily driver, it's my life line). I had been extremely hesitant to go to JB for fear of junking my phone up, but I'm really glad I took the extra risk. I just needed an extra bit of encouragement. Thanks again for all your input!
Click to expand...
Click to collapse
Regarding the key back light, since you are on aokp jellybean now if you still want to tweak the settings, goto settings and then device settings. There you can adjust the timeout on them
Crawshayi said:
If you managed to install AOKP smoothly you can pretty much install any rom the same way, basically meaning wipe data and cache/davlik then flash whatever you want to. Luckily this phone happens to be very hard to break, and you'd have to do something pretty extreme to brick it. I highly recommend Titanium backup pro so you can just backup the apps you want, and restore them in no time when you're trying different roms. Also, I've been using some voltage settings that make battery life insanely good, so if you're interested in doing that let me know and I'll post them.
Click to expand...
Click to collapse
just a little hint: NEVER RESTORE SYSTEM APPS WITH TITANIUM YOU WILL GET BOOTLOOP
Sent from my SCH-I500 using Tapatalk 2
I've restored Nova before that was a system backup with no problems but I agree about anything else. Not sure what system apps anyone would even want to backup really
Crawshayi said:
I've restored Nova before that was a system backup with no problems but I agree about anything else. Not sure what system apps anyone would even want to backup really
Click to expand...
Click to collapse
Dude I mean like system UI or settings lol
Sent from my SCH-I500 using Tapatalk 2
bbrad said:
Dude I mean like system UI or settings lol
Sent from my SCH-I500 using Tapatalk 2
Click to expand...
Click to collapse
I've actually done that before just to see what happened (system settings) and it didn't bootloop, it simply didn't restore anything. Not that I mind re-setting everything after a clean install, just figured I'd try to save a little time
Crawshayi said:
I've actually done that before just to see what happened (system settings) and it didn't bootloop, it simply didn't restore anything. Not that I mind re-setting everything after a clean install, just figured I'd try to save a little time
Click to expand...
Click to collapse
Are you trying too teach him too restore system apps lol?
Sent from my SCH-I500 using Tapatalk 2
Nope not at all, just chiming in on what happened when I tried it. It should be a no brainer to anyone flashing roms to not restore system apps, even if they're new to it honestly
Crawshayi said:
Nope not at all, just chiming in on what happened when I tried it. It should be a no brainer to anyone flashing roms to not restore system apps, even if they're new to it honestly
Click to expand...
Click to collapse
I know but it would surprise you I've had people complain because they flashed a i9000 ROM and it didn't work because the developer is stupid LOL
Sent from my SCH-I500 using Tapatalk 2
Nothing was the same after rooting my atrix.
-The HD games started to freeze, and on the worst cases crashing (e.g. GTA VC).
-Background apps (e.g. Gauge Battery Widget) rebooted very often (specially when browsing).
-When surfing multiple heavy pages, the browser tends to crash sometimes. Also when it crashes, it returns me to the start screen and if i have a live wallpaper running it stops and changes to a generic black screen.
-When trying to upload an image file on an image board, the browser refreshes the page.
-Overheats without reason from time to time. Seriously, its like a pocket heater.
-When the screen animations are activated, returning from landscape to vertical orientation turns the notification bar blurry and when i pull down the notifications tray it turns the screen blurry as well. Though it returns to normal when going back to landscape.
This is a major issue for me since if i turn off the screen animations, i can't tell if an app i opened is running (e.g. YouTube). And like i don't use the stock video player and use another player (e.g. MX player), when the animations are activated instantly crashes when opening a video.
Also before rooting, the battery only lasts me 5 hours without running apps and the problem persists ever since.
One thing. The first time i got the phone it came with stock FROYO 2.2.1 and i changed it right away to GINGERBREAD 2.3.6 skipping the 2.3.4, i unlocked the bootloader first and then rooted it.
Is there anything i can do to fix the problems previously mentioned?
I have a feeling you are an international user and did not flash the ramfix, search for it in development section, download to sd and flash.
jorno88 said:
I have a feeling you are an international user and did not flash the ramfix, search for it in development section, download to sd and flash.
Click to expand...
Click to collapse
Every tutorial i looked for didn't mentioned that, i'll give it a try.
But if i do that, does it mean i will have to do a hard reset?
It is surely mentioned in subsequent posts in the tutorial thread.
RAM fix has nothing to do with data so factory reset (or hard reset as you call it) is not needed.
ravilov said:
It is surely mentioned in subsequent posts in the tutorial thread.
RAM fix has nothing to do with data so factory reset (or hard reset as you call it) is not needed.
Click to expand...
Click to collapse
Not in the tutorials i've followed, they never mentioned it. FYI none of the tuts where from here.
Good to know i won't have to hard reset. So were does the zip go, internal or external?
always follow xda, it's the best
as for the zip, place it wherever you like and flash it with a custom recovery like cwm or twrp
Yeah I could never understand people who follow a tutorial on forum X then ask about it on forum Y... Makes no sense to me. Why are people on forum Y supposed to know anything about forum X or its contents?
Questions about a tutorial on some forum should be asked on that same forum.
And yeah, everything you need is on XDA, no need to go search for random sources.
Just to help the OP:
https://www.dropbox.com/sh/cu2bd61dh6ytzda/C-z3zfNBcr (just get the RAMfix.zip from this link)
http://www.youtube.com/watch?v=p5T9hJ4Yjek
Hope this helps OP. I have a At&t and I don't need to do the RAM fix. U can give this a shot. All the best.
5HoofedStallion said:
Not in the tutorials i've followed, they never mentioned it. FYI none of the tuts where from here.
Good to know i won't have to hard reset. So were does the zip go, internal or external?
Click to expand...
Click to collapse
Ramfix may not be mentioned in root tutorials because it's related with unlocking bootloader. Since you first unlocked, then rooted, you'll have to flash it anyway.
GH0ST DR0NE said:
Just to help the OP:
Hope this helps OP. I have a At&t and I don't need to do the RAM fix. U can give this a shot. All the best.
Click to expand...
Click to collapse
Off topic, but now that you brought the subject. I have seen this a while ago, and looks tempting but is it convenient for me to use the leaked ICS rom? Is there any bugs in it to be concerned about?
It's a shame that motorola decided to leave the atrix in the shadows with GB, they could at least made ICS the final and definitive update. I mean, the rom looks like it was 99% finished and ready to launch.
saldirai said:
Ramfix may not be mentioned in root tutorials because it's related with unlocking bootloader. Since you first unlocked, then rooted, you'll have to flash it anyway.
Click to expand...
Click to collapse
I followed both root and bootloader unlock tutorials and NONE brought that out. Since i'm LATAM, it made sense for me to seek in latin android forums instead here because of the firmwares, and boy they skip a lot of useful info in those forums.
Also, how do i exactly run the ramfix? Im eager to fix the buggy notification tray right away, that and fixing my battery not charging at 100%. I tried pulling the battery while charging and it turned worse, it went from 90% to 70%
I also need to know how to wipe the battery data from the CWM.
5HoofedStallion said:
... is it convenient for me to use the leaked ICS rom? Is there any bugs in it to be concerned about?
It's a shame that motorola decided to leave the atrix in the shadows with GB, they could at least made ICS the final and definitive update. I mean, the rom looks like it was 99% finished and ready to launch.
Click to expand...
Click to collapse
If it's running well for you, you should consider yourself very lucky. You should also read some of the threads concerning it and related ROMs (AtrICS etc) - the thing is so buggy very few people even wonder anymore how come it was never released.
Even if it's running so great for you as you say, I still wouldn't keep it if I were you. The ROM is a development build, it was never meant to be used as a daily driver. But that's just me.
5HoofedStallion said:
Off topic, but now that you brought the subject. I have seen this a while ago, and looks tempting but is it convenient for me to use the leaked ICS rom? Is there any bugs in it to be concerned about?
It's a shame that motorola decided to leave the atrix in the shadows with GB, they could at least made ICS the final and definitive update. I mean, the rom looks like it was 99% finished and ready to launch.
I followed both root and bootloader unlock tutorials and NONE brought that out. Since i'm LATAM, it made sense for me to seek in latin android forums instead here because of the firmwares, and boy they skip a lot of useful info in those forums.
Also, how do i exactly run the ramfix? Im eager to fix the buggy notification tray right away, that and fixing my battery not charging at 100%. I tried pulling the battery while charging and it turned worse, it went from 90% to 70%
I also need to know how to wipe the battery data from the CWM.
Click to expand...
Click to collapse
I agree with u. But Motorola is infamous for such antics. One if the reasons I don't have a RaZr anymore. But it is running good. I will b honest. Its OK. This phone isn't made for anything but GB in mind. I would pick a low end, second hand Windows Phone any day over this.
But this is as far as it goes for Atrix. Jelly Bean...naah.
Sent from my Π Σ Χ U S 4.
How am i supposed to run the ramfix?
Sent from my rooted & unlocked Motorola Atrix.
It's a flashable zip so just install it like gapps or a rom. Install from sd card
Which are the commands on the atrix?
Sent from my rooted & unlocked Motorola Atrix.
Use a custom recovery... You can manually adjust the cmdline but flashing the zip is much easier
You mean, with the RSD Lite?
Sent from my rooted & unlocked Motorola Atrix, using Tapatalk 2.
Don't ever touch RSD, RSDLite or any SBF (except pudding) unless you're at gunpoint.
Then how the hell do i run ramfix on clockwork!?!
Sent from my rooted & unlocked Motorola Atrix, using Tapatalk 2.
Would do you good if you could learn to search and read. It's all explained many times...
Hint: CWM = ClockWorkMod recovery
Another hint: How do you usually use a flashable zip?