Hi I have been using the 4.4.4 final Omnirom for tf300t on a tf201. It works fine.
Today I tried the 5.1.1 20151214 on the same device (after complete wipe). I'm seeing a white ring on the touch screen that I have to drag over to any point I'd like to touch before the touch is acked. This looks a bit like some confusion about detecting the dock (still happens if the dock is connected but the ring follows the pointer then).
Now I realize that I'm using a tf201, but given the 4.4.4 rom works perfectly I'm wondering if this is a glitch in the 5.1.1 build?
I have twrp 2.8.7.2 kang for recovery.
reflashed recovery to vanilla twrp 2.8.7.0 in case that was a factor (is not). Come on chaps, lets have some ideas!
No clue, I'm shocked cross-flashing a device works at all.
Our TF300 maintainers hang out in IRC - warning, many of us idle for extended periods so you might have to wait a while. I strongly recommend a real client and NOT using the web interface.
(We routinely have conversations with multi-hour gaps in them...)
Thanks will do.
Re - cross flashing - the tf201 and tf300 share almost all of their hardware (camera is different - interestingly that *works* on the 4.4.4 rom...it didn't with cyanogenmod - well done).
Related
I have just bought Acer Iconia A500 and when I play Words WF the tray tiles keep shuffling until I place one, running Honeycomb 3.1, is this a problem with the tablet or software ? I have tried turning the rotation off any ideas please
I play the game myself on my tablet and do not have this problem.. Are you running the Tablet version of the app of the phone version? I have no issues at all witht he tablet version.
I expect the tablet version I downloaded from market with the tablet I did not need to specify so believe should be right I have got the ap on an Optus Tablet works fine, thanks for your reply ????????????
If you got it through the market as opposed to installing an APK manually then you should have the right version. I am at a loss as to why you are experiencing the problem you describe though. Not experiencing this issue at all myself.
try to uninstall, then reinstall, may be a bad apk u installed
Hi. Your accelerometer is what's causing the issue. It's reporting the Z axis to be 0 to + 18 instead of -9.6 to +9.6.
I have the exact same issue. It's not a bad install or APK. You'll have the same problems in games like ATilt 3D Labyrinth, and anything else that relies on Z-axis. Have been looking for a fix or an update that fixes this but so far nothing.
I've tried multiple roms so far. My next attempt is going to revert back to stock (unrooted) 3.0 and try the OTA updates.
Update: Just reverted back to stock rom, issue is present in words with friends and also ATilt 3D Labybrinth. However, it's not present in Labyrinth Lite. Odd. updating now to stock 3.1
Update: Just updated to stock 3.1 via OTA. Words with friends now working/not constantly changing tiles.
I had the same problem. Constant shuffling in WWF. Updated to 3.1 and seems to be gone. They should've put a way to turn off shake-to-shuffle (which is what causes the problem). Honestly who would shake their tablet (or phone) to shuffle when there is a button right there?
Hi thanks for your really detailed reply you obviously know your stuff but as I am very new to tablets I have no idea what or how to update etc. Tablet tells me 3.01, Kernel 2.6.36.3 and build 1.016.04.
What is rooted etc, sorry if I seem a bit thick but struggling with the terminology and process, I therefore probably am a bit thick....LOL thanks for your assistance, Phil
I am not sure how many owners of the SM-G730A are mobile gamers at all, but maybe some of you have noticed this...
Since the update to Android KitKat 4.4.2 the touchscreen behaves erratically in certain games, primarily FPS shooters. I know it is not an issue with my particular device, goto Google Play and look up Dead Trigger 2. View the reviews for this device model only, you will see numerous complaints beginning after the date the OTA was released (8/27/14) complaining about the touchscreen controls.
I have downloaded the kernel source code from Samsung for both 4.2.2 and 4.4.2. Upon examining the kernel source, the Atmel touchscreen driver has been updated in 4.4.2. I believe this to be what is causing the problem. I am not sure if it is configured incorrectly or if it is just a poor driver. The Jelly Bean driver gave NO issues what so ever. I would revert back to 4.2.2 Jelly Bean if I could. I also compiled a kernel for KitKat which includes the Jelly Bean Atmel driver, however due to the locked bootloader, it does me no good.
What happens is this, you will have two fingers on the screen. Suddenly it is as though you lifted one, even if you are still touching the screen. Touches are erratic for a few seconds after this happens, then touch returns to normal temporarily until it happens again (usually only a few seconds later). This makes using the device for gaming extremely annoying, and difficult. This issue does not occur in normal use, only gaming, where there is rapidly changing multitouch inputs.
If any of you have noticed this, maybe you can contact Samsung/ATT complaining of the issue, if we're lucky maybe a patch will be released. Or it will be fixed in a future firmware update. I already wrote to both, ATT says they will forward the complaint to their management, Samsung has yet to reply.
http://www.samsung.com/us/support/contact / [email protected]
Also, this is a video I created demonstrating the problem. The video includes annotations describing the issue that can only be viewed from PC YouTube.
https://www.youtube.com/watch?v=3FMEPB51Y-4
Thanks for reading.
Has anybody with this device tried a multi-touch test? I'm starting to wonder if it's related to my screen protector. The issue only started after the KitKat update though, immediately after. I do a good amount of mobile gaming or I'd never have noticed it still to this day. Never presents itself outside of fps games.
Best way to check (within multi-touch test app):
Touch screen with two fingers.
Keep one stationary and rapidly slide the other around for a few seconds then stop and lift that finger only.
The stationary touch will act as though you lifted even though you didn't.
Sometimes touches will be erratic for a while if the test is repeated several times.
If anyone tries this please let me know if you have a screen protector or not and how it behaved. Thanks.
Nobody with this device on KitKat is willing to do a multitouch test for me?
All you have to do is turn the phone sideways so the app is in landscape mode, touch with two fingers, one on each side of the screen.
Keep one still, move the other rapidly for a little while then stop, but keep touching the screen.
Does the app show that you lifted the other finger even though you didn't?
I'd appreciate it, trying to narrow it down to a kernel driver issue, or screen protector issue.
https://play.google.com/store/apps/details?id=com.rn.yamtt
quakeaz said:
Nobody with this device on KitKat is willing to do a multitouch test for me?
All you have to do is turn the phone sideways so the app is in landscape mode, touch with two fingers, one on each side of the screen.
Keep one still, move the other rapidly for a little while then stop, but keep touching the screen.
Does the app show that you lifted the other finger even though you didn't?
I'd appreciate it, trying to narrow it down to a kernel driver issue, or screen protector issue.
https://play.google.com/store/apps/details?id=com.rn.yamtt
Click to expand...
Click to collapse
Its the phone mine does these same. Might just be a cheap screen make
Deonta23 said:
Its the phone mine does these same. Might just be a cheap screen make
Click to expand...
Click to collapse
Thanks for verifying. It's not the screen itself from what I can tell. I tried this on Jelly Bean with no issues. I did go through the kernel source for KitKat and believe it is the KitKat kernel touch driver. I am hoping for ATT/Samsung to release a kernel patch. The multitouch was perfect in JB.
Hi All,
I'm wondering if anyone else has encountered this problem?
Basically, I was having wifi issues connecting to an enterprise WLAN with PEAP/MSCHAPV2, so I (stupidly) upgraded to the OTA 4.4.2 ROM, which would have been fine if it didn't kill battery life and randomly restart. I wasn't on this version long enough to know if it had the same issue that I will describe below.
So I threw caution and my warranty to the wind and went with the 4.4.4 Pacman ROM, which was great, but whenever I had a phone call, the phone screen freezes and won't wake up to allow me to hang up a call. The same thing would occur if I called someone and had to use their automated system - I'd put the screen on loudspeaker, open up the dialpad, and when I want to hit the numbers - nothing. Locked up. Can't hang up either.
I had the same issue on the 4.4.4 Cyanhacker ROM, so I believe that it is fully related to some sort of incompatibility between KitKat and the i9505, and not the ROMs themselves.
At this point I was successful in switching to the Darthstalker 4.3 ROM, which is running beautifully and I'm really liking it so far. It's also nice having the old phone and contacts apps back, because I really hated the Kitkat one anyway...
I'm looking to use my Asus Nexus 7 WiFi as a car stereo unit soon.
Would like to start checking out the various Car ROM's.
What is everyone using these days that is up to date on security patches, etc?
Anyone?
I can't get a 2013 N7 yet. So I'm stuck with my 2012 N7 for a while longer.
I am unable to download Timur's ROM/kernel because it's no longer available.
http://rootzwiki.com/topic/37755-timurs-kernel-usb-rom-most-popular-thread-on-rootzwiki/page-479
Currently on an AOSP ROM that's not working well with things I need it to do.
Really need a kernel that works well with fixed car stereo applications.
EDIT: I did locate Timur's 4.2.2 ROM, the last produced for N7 2012.
The filename is:
cm-10.1-20130817-USBROM-grouper.zip
It's hosted at a couple different places. Just google the filename.
Would still really like a newer Lollypop/Marshmallow ROM & kernel though if anyone has suggestions.
Otherwise, I'm still in my beginning stages of Googling everything about anything.
I don't know what you mean by car ROM, but I've been using CM13 for a while now and it's quite reliable
I'm using Autodroid 1.2 with oxydo-revamped kernel. It's Kitkat 4.4.4 which is by no means new but still newer than Timur. I'm overall very satisfied. I have a slight but annoying compatibility issue between Sygic navigation app and Slimrom nature of Autodroid (traffic cameras are not displayed correctly on navigation screen). The same problem I face on my phone, which also runs a Slimrom based ROM.
Thank you. I had heard of Autodroid but thought it was only for the 2013 N7.
And I do love me some SlimROM!
I'll Google it up at some point this afternoon.
I really still enjoy using this table and LineageOS 14.1 breathed new life into it from the stock Andriod ROM of KitKat. If not does anyone suggest anything other than LineageOS to run on my tablet that would perform any better than LineageOS.
Thanks,
Lime
Hmm nobody has any thoughts?
Resurrection Remix is a very good and stable ROM. But you leave curious...
What is lacking in Lineage that leaves you wanting?
wellersl said:
Resurrection Remix is a very good and stable ROM. But you leave curious...
What is lacking in Lineage that leaves you wanting?
Click to expand...
Click to collapse
It looks like they may not be going forward with any new releases of lineageos for the SM-T520.
LOS14 Issues
I have 3 issues with LOS14 on my SM-T520 wifi which I didn't have with a former CM Rom:
- I like to hold my Tab in different orientations and android rotates the screen likewhise. But the unlock-screen is not rotated and allways shows same orientation no matter how i hold the tab.
- I play some games on my tab with ad videos. In some games those videos are played in full volume for a fraction of a second even though my volume is low or off. This makes an irritating noise whenever one of the video starts.
- In some games android seems to overload the cpu regularly for some milliseconds and the game hangs (graphic and sound) but only when the tab had been running for a longer time. When I then restart the tab everything works fine.
I had a CM on my tab before and I didn`t have any of these issues there. But CM is no longer supported or updated so I switched to LOS14. Appart from these issues LOS14 runs very good on the SM-T520. But like limeman35 said there seem no progress in developement. At least there are nightly builds from time to time with service releases from android.
I am a newbie when it comes to rooting. I've never tried it but I have a Samsung t525 an I check all the time for system updates for this tablet but there never have one. I've even called into Samson an they told me you cant download any updates at all. That is hard for me to ac Sept. There has to be something I can to to utilise my tablet. Will you please explain how to root my tablet? Ty Pawneehappygamer