[CM10] Auto-rotate screen work only with keyboard open - Eee Pad Transformer Q&A, Help & Troubleshooting

I run official CyanogenMod 10 on my SL101 who is a TF101 with a integrated keyboard sliding under the screen.
The auto-rotate screen function does not work when the keyboard is under the screen.
Is there a solution or a trick to make it work correctly without an app ?
PS:The only roms who work normaly are the Asus-TF101/SL101 based roms like Revolver 4 but who are not JellyBean.

We Slider owners just have to stick with the few ICS ROMs for now. Devs are still concentrating on fixing the bugs for the TF101 on ICS ROMs.

There is so few SL101 users next to TF101, that I am afraid that we will never have update.
By the way, changing some properties of the build.prop CM10 by Asus-ICS do nothing better.

Related

JB bug list?

I dont see one started yet.. has anyone seen any posts with bugs/issues with the JB update (i mean once its running)
ive seen two posts about different bugs but no overall list of everything combined together yet.
was wondering since ive had an odd quirk where flipping between screens it suddenly gets the screen frozen with a random pattern over top (random as in machine random not as in chosen pre made pattern)
I'm still on ICS (and I'm starting to be happy with it), but from what I've read there are issues regarding the alarm clock, the HDMI output and status bar overlapping the notification panel. Could be more, I hope that the guys with JB hop in and confirm or find new issues. Asus seemed a little bit in a hurry to launch the JB upgrade and didn't test everything extensively.
Trimis de pe ASUS Transformer Pad TF300T

[Q] Galaxy Tab 2 7.0 Navigation Bar on CM10

Hi guys,
i just installed the newest nightly CM10 (18.09.2012) on my galaxy tab 3110.
first i noticed that in navigation bar the back and multitask buttons are replaced.
second i noticed these buttons are smaller than bevor with nightly build 14.09.2012.
i figuered out how to replace the buttons again and saved the settings.
my problem is as followed:
since the new nightly update my navigation bar is not specific. everytime i have to touch the buttons a bit left and they work.
if i touch them in the center or a bit right there is no action and the buttons are not responding.
only the home-screen button is working well so far.
has anyone noticed this problem? can i solve it?
does this problem depend on the smaller navigation-bar buttons?
i hope you can help me.
thanks
Just try aokp rom it has a full control of navigation buttons (like cm10 but more customizable) and based also in jelly bean
Sent from Galaxy S2 or Galaxy Tab2
thanks for reply.
i dont want to change my rom. before the new nightly everything was ok and the navigation-bar was not customizable, so nothing was wrong and everytime i touched the buttons they responded 100%
does anybody have the same problems like me when touching the navigation-buttons they cant be touched in the center or a little bit to the right of them?
EDIT:
So it seems the problem is known by other users as well.
I would like to downgrade to an older nightly build. is this possible? can anybody tell me how to do it?
can i just put the older nightly .zip on internal sd-card and flash it like all the other "updates"?
thanks
EDIT:
So it seems the problem is known by other users as well.
I would like to downgrade to an older nightly build. is this possible? can anybody tell me how to do it?
can i just put the older nightly .zip on internal sd-card and flash it like all the other "updates"?
thanks

[Q] Screen issue on 4.2 roms

Ok so i installed CM10.1 and i noticed that there is someting like an invsible line 1cm above the buttons..... it can be really annoying. I can only see it in games or when i scroll up/down in portrait mode.looks like it would reload everytinhg scrolling through there, dont even know how to explain. I tried to enable the 3 options for screen tearing("disable hw overlays , force gpu rendering etc) but it doesent slove anything. Same goes for AOKP 4.2.2. With 4.1 roms everyting is fine.Anyone knows what the problem could be ?
You might wanna make a backup of CM10.1 and flash another ROM to see if the problem persists. I've ran about 6 different 4.2 ROMs and haven't seen this.
Worst case scenario is that it's your screen...
AW: [Q] Screen issue on 4.2 roms
Have the same issue with baked black bean 8 (4.2.2). Hope it will be fixed soon, but actiually I can live with that.
sent from my baked One S
Black Bean 8? Mind telling me where you found that? Been searching for days for it.

Multitouch Problem

I've found something that affects multitouch in the galaxy tab 2 7.0. When I put two or more fingers on the screen in apps that needs multitouch(dead trigger,maps,chrome) and move them (this is hard to explain in words) the app will have 'jittery' movement and sometimes the multitouch will 'break'(pinch to zoom will stop midway). I also tested this with the 'show pointer location' in developer options and it seems that the pointer trail has gaps in it. This cannot be a hardware issue because I haven't dropped the tablet and it only happened recently. It's probably software related as the issue dissapears for a while if I restart. I'm using stock rom 4.0.3 non-rooted with no custom kernels. Does this also happen in other ics and jb stock roms?

[Q] CM10.1 question - wondering if you're seeing this

TF700T unlocked, rooted, and CM10.1 Stable loaded and I have the Asus keyboard dock.
Liking it so far but one issue that I have is that when you wake the device and go to put in the PIN for unlocking, the keyboard will not work on that PIN screen and only on the PIN screen. The keyboard works perfectly in all of the other apps and circumstances that I've played with so far...
anyone else running this setup and have the same experience or tips?

Categories

Resources