My 32Gig TF201 is running AndroWook 2.3. I've spent quite a long time on stock (wth root when that was possible) and then tried AndroWook and Pac. One thing I've noticed all through the various ROM versions that I'd love to resolve (but could understand if it ain't) is that its behaviour when opening it when connected to the keyboard dock. Sometimes after a small and acceptable delay the screen comes on, at other times nothing happens until the power button is pressed and even then sometimes a rather long (a couple of second lag) occurs. Every so often while holding the power buttong with no effect the screen will come on with the power menu displayed.
Is there any way to make it come on more reliably, that the screen comes on after a consistent and short period of time when the lid opens and the power button is pressed?
iamroddo said:
My 32Gig TF201 is running AndroWook 2.3. I've spent quite a long time on stock (wth root when that was possible) and then tried AndroWook and Pac. One thing I've noticed all through the various ROM versions that I'd love to resolve (but could understand if it ain't) is that its behaviour when opening it when connected to the keyboard dock. Sometimes after a small and acceptable delay the screen comes on, at other times nothing happens until the power button is pressed and even then sometimes a rather long (a couple of second lag) occurs. Every so often while holding the power buttong with no effect the screen will come on with the power menu displayed.
Is there any way to make it come on more reliably, that the screen comes on after a consistent and short period of time when the lid opens and the power button is pressed?
Click to expand...
Click to collapse
Are you using hunds kernel with 2.3 ?
flumpster said:
Are you using hunds kernel with 2.3 ?
Click to expand...
Click to collapse
Yes, with data2SD, which I'm using now (wasn't with the other ROMs.
iamroddo said:
Yes, with data2SD, which I'm using now (wasn't with the other ROMs.
Click to expand...
Click to collapse
Can you grab the kernel installer from post 2 of the thread and install hunds with data2sd from that. It has a newer kernel in it that should fix that for you.
flumpster said:
Can you grab the kernel installer from post 2 of the thread and install hunds with data2sd from that. It has a newer kernel in it that should fix that for you.
Click to expand...
Click to collapse
It seems to have sorted the issue out. Thanks!
Related
Hi guys,
I finally installed Windows 7 bootcamp on my Mac, and went away on flashing kernel to XWKDD_insecure.tar, and rooting the S2 with S2 Root app. Everything went smoothly, and I now have TB Pro with a couple of apps frozen.
However, one very noticeable change after I flash and rooted was that my Applications button is very hard to activate. I thought I had imagined it, but when I unlock via Widgetlocker slider, and tap the Applications icon on the bottom right, nothing happens with the normal pressure I am used it. To activate it, I must push down with a little force for a second or two, let go, and it will go to the application folder. Also, I have also notice that when I wake the phone, the unlock widgetlocker slider is slightly unresponsive at first, I must also apply more force, hold it for a second, and slide for the slider to work. Before I rooted (6 hours ago), I can lightly tap the application icon, or light slide the unlock slider, and it would work.
Another weird thing is also buttons on the screen works fine thus far.
Anyone have this rather weird problem? I am slightly regretting rooting the phone, because the applications icon just wouldn't budge despite multiple taps... I've tried battery pulls, etc, but the problem persists, especially right after I unlock the phone.
Any input is much appreciated!
Thank you
Did you found a solution? I have the same problem, but I don't know if it's because rooting? This is really annoying.
Same here after CF-root.
and let me add that the return touch key (below the applications icon) isn't so responsive as before rooting!
I thought I was just imagining but I am "glad" you guys having the same problem.
Looking forward for a solution.
Maybe asking Chainfire ?
Well I just installed a stock rom, same thing.
My 'back' button is very un-responsive as well. it's like I really have to hit the spot for it to react.
Am having the same issue with the back key and i am still stock non rooted
cruzantis said:
Am having the same issue with the back key and i am still stock non rooted
Click to expand...
Click to collapse
Non rooted you say, interesting...
I thought it is because I rooted it.
gil80 said:
My 'back' button is very un-responsive as well. it's like I really have to hit the spot for it to react.
Click to expand...
Click to collapse
cruzantis said:
Am having the same issue with the back key and i am still stock non rooted
Click to expand...
Click to collapse
This is certainly not the first time I've heard about such complaints, infact a few friends also had this issue as well they had their phones replaced.
Hi guys
I have problem with my g tablet screen, 80% of time when screen goes off (regardless is it timeout of screen or by shot press on power button) it won't came back untill I restart device.
For example I am listening radio and screen timeout takes place, I am still getting sound but no meter what - screen is not coming back unless I press and hold power button and device restarts. I am running calkulin 1.1 rom.
Anyone......?
Known issue with most ROMs. Search for SOD.
erik077 said:
I have problem with my g tablet screen, 80% of time when screen goes off (regardless is it timeout of screen or by shot press on power button) it won't came back untill I restart device.
Click to expand...
Click to collapse
I, too, would've said that this was a SOD problem, but, then you said this:
For example I am listening radio and screen timeout takes place, I am still getting sound but no meter what - screen is not coming back unless I press and hold power button and device restarts. I am running calkulin 1.1 rom.
Click to expand...
Click to collapse
What happens if you play music using the standard Android music app and the screen times out while playing? Can you switch the screen on?
Suggestions:
On the current ROM, try a different kernel.
On the current ROM, if you install Jack Palevich's Android Terminal Emulator, you can "Take Wakelock" and then minimize the app to keep the tablet from going into suspend. Or, install one of the many apps from market designed to do the same thing.
On the custom GB ROMs, you can wake the device up by pressing the volume rocker after you enable Settings > VEGAn-TAB/CyanogenMod settings > Input > Volume rocker wake. Install a GB ROM.
Thanks. I read it somewhere that could be hardware issue and I unrooted device so I could maybe contact Viewsonic if 6 months is not too late. I will root it again and try this tonight.
I got permission denied for terminal emulator "Take Wakelock", tried with su not working either
I am running Calkulin 1.1 and not having BG options for sound
Most of other ROM's I tried for this dumb device are not working for me
rajeevvp said:
Suggestions:
On the current ROM, try a different kernel.
On the current ROM, if you install Jack Palevich's Android Terminal Emulator, you can "Take Wakelock" and then minimize the app to keep the tablet from going into suspend. Or, install one of the many apps from market designed to do the same thing.
On the custom GB ROMs, you can wake the device up by pressing the volume rocker after you enable Settings > VEGAn-TAB/CyanogenMod settings > Input > Volume rocker wake. Install a GB ROM.
Click to expand...
Click to collapse
erik077 said:
I got permission denied for terminal emulator "Take Wakelock", tried with su not working either
Click to expand...
Click to collapse
That's a very odd error. Uninstall, then reinstall the terminal emulator app and update to the latest version of the Superuser app.
It might be simpler to just install one of the wake lock holding apps from market, though.
Suggest
Ihad same problem with cm7. 2
I solve it with these steps
i set minimum cpu at 216
i set spare parts behavior go to sleep Option
iset auto brightness
and i disable any other on of option exept power button.
I install autokile memory optimizerr and set to advance different sleep i hope that help you
i have try it two days with no problem and i have on lock screen
with out sod problem
Thanks for any reply's in here. I sent tablet to Europe as gift (after applying those options, item was fine for 3-4 days).
I flashed fluxi kernel on CM9, then installed a newer CM9 build which replaced the kernel, and now the capacitive buttons don't light up when I touch them or the screen.
Any solution?
Under Settings>Advanced>Sensors "Enable keys backlight" is enabled?
Bye
itaijac said:
I flashed fluxi kernel on CM9, then installed a newer CM9 build which replaced the kernel, and now the capacitive buttons don't light up when I touch them or the screen.
Any solution?
Click to expand...
Click to collapse
Hold menu button for a few seconds and then let go.
Thanks. It is enabled and holding the menu button does nothing.
Sent from my GT-I9100 using XDA
Did you leave the phone on charger overnight? I did.
Now, most of the times, my capactiive keys do not respond. Sometimes they do.
When they are not working, they do not light up either no matter how many times they are touched. However, if i touch the screen area at that time, they light up according to duration (like 1.5 seconds). But still, touching them does not make them work.
I have tried the screen code *#2660# to update the fw of capacitive soft keys. Made no difference.
I've always been charging it overnight, the lights stopped working after flashing CM9 over CM9+fluxi kernel.
Also, the buttons work, the light behind them doesn't.
Well imo, you should flash stock kernel and start over i.e. root, then flash CM7 latest nightly. Stay with it for a few days.
I suppose full wipe should fix it, I was hoping for something else, like messing with the liblights file
Try siyah kernel. Using ext tweaks you can set a timeout for the capacitive button. It lights up when you touch the screen or the button not like the other kernels where you need to touch the button so that it would light up.
Edit: In case you try siyah kernel, make sure you download the one for sgs2 not sgs3.
Sent from my GT-I9100 using xda premium
Thanks but I might as well flash fluxi kernel. The problem started because I wanted to return to CM9 kernel (hence flashing CM9 over CM9+fluxi). I'm looking for a solution that will allow me to stay 100% CM9, without full wiping my phone.
itaijac said:
Thanks but I might as well flash fluxi kernel. The problem started because I wanted to return to CM9 kernel (hence flashing CM9 over CM9+fluxi). I'm looking for a solution that will allow me to stay 100% CM9, without full wiping my phone.
Click to expand...
Click to collapse
I think with cm9 kernel (for now maybe) you don't have the option to have a time out for the capacitive buttons or similar to what i have explained earlier (the one where when you touch the screen the capacitive button lights up blah blah). Either it is permanently on or it is permanently off (using the 2nd poster's advice).
Sent from my GT-I9100 using xda premium
"Enable keys backlight" is ticked. When I untick and then tick it again, the lights work only as long as I don't turn off the screen. If the screen is turned off and on again, no lights as usual, though the box remains ticked.
itaijac said:
"Enable keys backlight" is ticked. When I untick and then tick it again, the lights work only as long as I don't turn off the screen. If the screen is turned off and on again, no lights as usual, though the box remains ticked.
Click to expand...
Click to collapse
It's been a long time since i tried stock cm9 kernel. During that time the button lights are always on. I think i tried it one time and you're right. Well, siyah is working for great for me.
Sent from my GT-I9100 using xda premium
Update: problem solved by flashing build cm-9-20120709-EXPERIMENTAL-galaxys2-VOLUMEDROPFIX-LUXRANGE.zip
This ROM is working very well on my UK Rhod 100. Very stable & fast and since the latest update I have the correct HW keyboard layout. Battery life is limited but carrying a second battery is an easy solution.
The previous problems where the screen would not turn on after several pushes of the power button almost never occurs. However when the battery runs down to about 30% the screen always changes such that a red overlay occurs visible mainly on screens with a white background (see pics). Also when the screen changes ghost images remain from previous screens. Also at this point sometimes the screen will not turn on despite repeated use of the power button. Strangley, even though there is nothing visible on the screen I can unlock the phone by swiping in the expected area (and get haptic feedback) and long press the power button and turn off the device by pressing in the expected areas. Upon a reboot the screen will initially be back to normal but then if the battery is below 30% the problem will return. These issues never occur if the battery is above 30%. If I take screenshots with shootme the pics captured look normal when viewed after a reboot before the problem recurs. Not sure what the system does when the battery falls to this level but the screen is definitely affected. This problem also occurs with a fresh install with no apps installed.
If anyone has any ideas as to what could be the cause (and even better a solution) it would be most welcome. Thanks to all those behind this project.
Sorry you are having troubles. Unfortunately as noted in the first post for that thread we only have RHOD400s to test with. No one else has reported any similar issues. The 100s are known to be the problem children of the RHOD family. If you come up with a fix let us know, and we will try to include it in any future releases.
wizardknight said:
Sorry you are having troubles. Unfortunately as noted in the first post for that thread we only have RHOD400s to test with. No one else has reported any similar issues. The 100s are known to be the problem children of the RHOD family. If you come up with a fix let us know, and we will try to include it in any future releases.
Click to expand...
Click to collapse
Did you look at ACL's work on RE'ing that panel code...?
He said something about the panel power up/power down sequence on the 100's (the AUO panel specifically) to be quite a bit different.
arrrghhh said:
Did you look at ACL's work on RE'ing that panel code...?
He said something about the panel power up/power down sequence on the 100's (the AUO panel specifically) to be quite a bit different.
Click to expand...
Click to collapse
arrrghhh, I noted your post in the ROM development thread regarding the start up sequence in the OMGB kernel for the AUO panel. Perhaps this would solve my issue as well. If this change could be added to the next edition of this ROM my device would be virtually bug free.
As noted in the thread, we do not have any RHOD100s to test with. It is very unlikely that this will happen. If you would like to make your own kernel with these changes I can post it.
issue or not?
hi,
thanks a lot, first of all.
I've been trying to figure out how to get an Italian keyboard layout.
any suggestion?
-p.
paolora999 said:
hi,
thanks a lot, first of all.
I've been trying to figure out how to get an Italian keyboard layout.
any suggestion?
-p.
Click to expand...
Click to collapse
try using AItype Keyboard Plus which supports multiple languages and keyboard layouts
Sorry I didn't express myself properly. I meant the physical keyboard. In other thread I read something about a startup.txt file, I don't know if it applies to this ROM (and moreover I can't find it).
paolora999 said:
Sorry I didn't express myself properly. I meant the physical keyboard. In other thread I read something about a startup.txt file, I don't know if it applies to this ROM (and moreover I can't find it).
Click to expand...
Click to collapse
startup.txt files are only for the SD card versions of the android roms.
You would need to edit the keyboard map. Here is generic android keyboard map info.
There may be apps out there than can change your keyboard map, but I don't know any details about that.
Also in the future it would be best to start your own thread, rather than using an unrelated one. Better yet, post the questions about the rom you are working with in the thread for that rom.
i am having also a screen problem with that Rom and Kernel:
My screen is not calibrated. When i press it's being pressed on somewhere else on the screen.
P.S.
My RAM is not 100 +- this rom showing me 33 for usage on the device :S.
Can someone help me with those two ?
MTN_Cool said:
i am having also a screen problem with that Rom and Kernel:
My screen is not calibrated. When i press it's being pressed on somewhere else on the screen.
P.S.
My RAM is not 100 +- this rom showing me 33 for usage on the device :S.
Can someone help me with those two ?
Click to expand...
Click to collapse
Did you read the link that covered screen calibration listed under related goodies, or did you search for the threads that cover screen calibration under android? Tell us what you have tried, but didn't work.
No idea what you mean by the ram is not 100.
What the heck is going on here? Is this just the thread to jack?
Let's focus on the display issues please folks, as in your response should be related to the original post.
arrrghhh said:
What the heck is going on here? Is this just the thread to jack?
Let's focus on the display issues please folks, as in your response should be related to the original post.
Click to expand...
Click to collapse
idc if they will move my question the the original one...
but i can't fix my calebration points...every time i need to launch the HTC program :\
Problem resolved?
akk29 said:
This ROM is working very well on my UK Rhod 100. Very stable & fast and since the latest update I have the correct HW keyboard layout. Battery life is limited but carrying a second battery is an easy solution.
The previous problems where the screen would not turn on after several pushes of the power button almost never occurs. However when the battery runs down to about 30% the screen always changes such that a red overlay occurs visible mainly on screens with a white background (see pics). Also when the screen changes ghost images remain from previous screens. Also at this point sometimes the screen will not turn on despite repeated use of the power button. Strangley, even though there is nothing visible on the screen I can unlock the phone by swiping in the expected area (and get haptic feedback) and long press the power button and turn off the device by pressing in the expected areas. Upon a reboot the screen will initially be back to normal but then if the battery is below 30% the problem will return. These issues never occur if the battery is above 30%. If I take screenshots with shootme the pics captured look normal when viewed after a reboot before the problem recurs. Not sure what the system does when the battery falls to this level but the screen is definitely affected. This problem also occurs with a fresh install with no apps installed.
If anyone has any ideas as to what could be the cause (and even better a solution) it would be most welcome. Thanks to all those behind this project.
Click to expand...
Click to collapse
In an attempt to bring this thread back on topic I thought I'd report back that the original problem has not happened for a few weeks. My setup is essentially unchanged, the only change is that I have been using One Power Guard to try and improve battery life, which by the way seems to be effective. Managed 13hours with light use (few calls/occassional data for email web browsing)
Anyway it could be coincidence but it is possible that one of the tweaks performed by the app has sorted this issue. Since nobody else has reported the same problem I'm not sure how useful this info is but hopefully it may be of use to someone.
I have a minor niggle but wonder if it's due to something I'm doing wrong. I have full backup's of my TA partition and flash custom and stock rom's as and when I choose. I just have an annoying issue when i turn my screen back on it shows garbage pixels on the screen and slowly draws the screen til the bottom and then flashes to a properly drawn screen. Can I remove it or learn to live with it?
srdempster said:
I have a minor niggle but wonder if it's due to something I'm doing wrong. I have full backup's of my TA partition and flash custom and stock rom's as and when I choose. I just have an annoying issue when i turn my screen back on it shows garbage pixels on the screen and slowly draws the screen til the bottom and then flashes to a properly drawn screen. Can I remove it or learn to live with it?
Click to expand...
Click to collapse
My test device - that I picked up very cheep as it had been dropped and the SIM reader no longer works - displays the same issue, I had always assumed it was because of the fall it had.
Sorry if that doesn't help you
like this?
http://youtu.be/oyv5QmD5uQA
Exactly the same issue thanks
Same here but my phone is allways in case and i never dropped it. Oh and factory reset or flashing another ROM is not solution.
Any ideas?
I can only guess that either the RAM fills up with the screen off and once it starts to clear when the power button is pressed it suddenly can draw faster, or it's because the CPU and GPU clock down and slowly ramp up on wake. I'll change my performance settings see if that changes things?!
I've changed the settings in performance. So goto settings, performance, profile and select performance instead of balanced or power save. This seems to have sorted the re-draw issue on the lockscreen, any change I'll let you know. Now I just need to get a basic knowledge coding/cooking rom's and start delving further into android!!
srdempster said:
I've changed the settings in performance. So goto settings, performance, profile and select performance instead of balanced or power save. This seems to have sorted the re-draw issue on the lockscreen, any change I'll let you know. Now I just need to get a basic knowledge coding/cooking rom's and start delving further into android!!
Click to expand...
Click to collapse
So it's actually software problem right? Not damaged screen or something inside the phone.
Jecmenn said:
So it's actually software problem right? Not damaged screen or something inside the phone.
Click to expand...
Click to collapse
seems that way i now get it one in ten times I press the power button otherwise it just instantly appears with no redraw, just seems like lag
srdempster said:
seems that way i now get it one in ten times I press the power button otherwise it just instantly appears with no redraw, just seems like lag
Click to expand...
Click to collapse
mine is a hardware issue. you will see that it is currently on cm12 but it has done that on Stock, 4.4.x custom and 5.0 CM/AOSP as well. It will only do this if it hasn't be used for a few hours.