My dock (I'm from the UK so dock and tablet come together as one package) only seems to fully work about 25% of the time. Most of the time when I connect it I don't get a mouse pointer and I can't use it to type :-( The tablet recognises the dock being connected as in the notification area it says "You can now use the keyboard to type" and the tablet charges from the dock. However, only the top row of the keys do anything - so I can lock it, mute the sound, turn off wifi etc fine, but none of the other keys work. The other 25% of the time when I connect it the mouse pointer instantly appears and I can type fine. The bar always goes to the lock position, so I'm assuming I am connecting it correctly.
Apart from this the tablet works fine - no dust or dead pixels, good wifi, minimal light bleed, so I'd rather not return it and get another one with other issues. maybe a loose connection on the dock?
Anyone else with the same issue, or who can help?
I had some problems with the dock functioning, but it seems to have gone away after plugging/unplugging a few times. Now it seems fine.
I am also from the UK and have the same problem I have tried to remove the dock a few times and sometimes it works. It never worked first time. The table is perfect with Bluetooth and GPS working. My main problem is that it takes ages to boot up compared to my 101, about 4 times as long. I will wait a couple of weeks see if an update sorted it then return the thing back to Comet.
No problems here. Did you guys get the firmware update? I am using MobileDock version TF201-DOCK-0206, that got pushed to me the first time I docked my TFP.
Bimboy said:
No problems here. Did you guys get the firmware update? I am using MobileDock version TF201-DOCK-0206, that got pushed to me the first time I docked my TFP.
Click to expand...
Click to collapse
Bimboy
Yes I have the same version TF201-DOCK-0206 thanks for the reply
I'm from Austria, but got the package with tab and dock too, i think thats regular in EU. I have no problems with my dock. Maybe you've pressed the "disable mousepointer" button? it's next to the bluetooth button on the dock
theSpawnAT said:
I'm from Austria, but got the package with tab and dock too, i think thats regular in EU. I have no problems with my dock. Maybe you've pressed the "disable mousepointer" button? it's next to the bluetooth button on the dock
Click to expand...
Click to collapse
Thanks, Hadn't noticed that button. If the dock isn't working (which is about 75% of the time) and you press that button to disable the mouse pointer and then press it again to reenable it, the mouse pointer will work for a short time, but the keyboard still won't work in this scenario. If you leave the mouse pointer to disappear you can't get it back again until you press that button twice again.
So its still not working properly but there can't be much wrong with it if you can press a button to get the pointer on again. Maybe it will be fixed by the ics update on thursday?
Mine has a little issue where after not using it all night the dock will not funtion. There is no mouse pointer at all. Once I pull it off the dock and put it back on it works just fine the rest of the day. Anyone else have this issue?
Got it working again by rebooting and then re-docking a couple of times (typing from it now). Been working for 30 mins - scared to leave to go into sleep mode in case it fails again ;-)
Closing and opening the hinge seems to help, but probably best wait for todays update before worrying too much!
Got this from ASUS support today;
Could you please await the firmware update that is due to be released this comming thursday?
If the firmware update has failed, please back up all your data and try the recovery back to factory settings as per instructions below:
1. Press and hold the power button and choose <Ok> to shut down.
2. Remove any SD cards from the Eee Pad.
3. Press and hold the <Volume Down> button, then press and hold the <Power> button. Keep pressing them both until you see white writing on the screen. You may then release them.
4. Wait five seconds until you see an icon in the middle of the screen labeled "Data Wipe".
5. Use the <Volume down> button to highlight "Data Wipe"
4. Press the <Volume up> button to execute the process.
6. After the "Wipe Data" process finished, it will automatically reboot and start normally.
Didn't do a wipe, but I'm still seeing this occasionally after updating to ICS 9.4.2.7. Open/Close seems to persuade it to work.
Select Asus keyboard as input and the keyboard will work. EOT
Changing the keyboard setting doesn't always work. Sometimes the special/shifted keys get mapped wrong too. It's all related, but some point in the process seems unreliable.
Mine does the same thing. I have to reboot the tablet while off the dock and then plug it in at times for it to work.
Same here. Bought from PC World in UK.
Is this a software issue? If not, I'll get it swapped.
I have the same problem with the dock, i tried everything. Hardreset , factory reset, reboots with and without dock on prime but nothing changed at all, the dock is working about 10% of the time and that is completely random.
There doesnt't seem to be a loose contact between dock and prime, because I tried to move around the dock and the prime in every direction while they were connected and the keyboard was working at that time without problems and without losing connection or an error message.
As soon as I'm working with the dock for a few minutes or when the Prime (while connected to the dock) is turned back on from sleep mode, either the dock's keyboard or the touchpad or sometimes both stop working.
I'm using the DE version of Android 3.2.1 as firmware,
ankhazam said:
Select Asus keyboard as input and the keyboard will work. EOT
Click to expand...
Click to collapse
Nope! ASUS keyboard is already selected - I've tried every combination of keyboard it makes no difference to the functionality of the dock. full keyboard only works 10% of the time, mouse pointer only works about 25% of the time, the top row of keys works 75% of the time, and dock charges the tablet 75% of the time.
On the odd occasion when all the keys do work, they only work for up to 30mins or so, or until it sleeps :-(
A user on transformerprimeforums.com as tried a different a second tablet with his dock - and it worked fine. Which assumes his tablet is the issue? Which is a bit weird as I would have assumed an issue with the dock. Anyway, mine is going back (both tablet and dock as it's one package in the UK) and I'm going to try a second one. Any issues with the second one and I'll give up and get a refund :-(
Problem persists for me on TF201-DOCK-0206 .
Although sometimes irratic and difficult to replicate, I've found a way that normally works.
When booted undocked, then docked after lock screen displayed, MobileDock works.
When booted docked, MobileDock still charges, but isn't fully functional.
I've installed all firmware updates so far. No change.
I also have the same problems with my TF201-DOCK-0206 as mentioned in this thread. Was hoping for the last update to solve it, but it didn't.
What I found out is when the keyboard works, keep the Caps Lock light burning if you don't use the keyboard.
I'm not sure if it is a soft or hard issue, but I don't think it has something to do with bad connections/connectors. More like a component goes into sleep mode and won't wake up the normal way.
Related
After upgrade to XXKG2 firmware 2 days ago, the voice command launches randomly. Exactly like you press twice the home button. So, I been suspicious about home button or accidental push. But this occurs also on the table, without anything near to it. But I got more worried about this, when this issue comes, sometimes the battery icon show up the charging icon
Also detected randomly "wake ups", with the screen dimmed... without any touch
Yes, I could freeze or remove the car dock app or the voice command app, but this will not fix the source.
Anyone having similar issue or figure out some fix?
EDITED: Problem fixed ... my results here, in other thread:
http://forum.xda-developers.com/showpost.php?p=16418825&postcount=25
The accelerometer on my Razr Maxx works promptly and perfectly except under two conditions. The first -- if I'm lying down, say on a couch or in bed, and holding the device over my head facing down. In this position the device will almost immediately shut off over and over. It won't reboot, just shut down. I can always restart it the same way I would from any "sleep". I can get the device to stay on merely by rotating it to face "up" no matter whether I change position or location or run or do not run any particular application. Is this common? Is it by design for some reason? The second -- if I have Button Savior installed, the Maxx accelerometer will work but there will be a significant delay in responding. Like 15-30 seconds delay! No Button Savior - no delay. Install Button Savior - delay. Uninstall Button Savior again - no delay. This troubles me as I really like Button Savior even on devices that have "hard" buttons. Having these controls right under my thumb is the fastest way to navigate, for me. Button Savior (updated) works perfectly for me on other Android phones, on my rooted Nook Color (CM7), even on my rooted Nook Touch. Any cures for either ill?
Hi
The accelerometer issue... does this happens from the first day you bought it? I trying searching similar issues, could not find anything. I am almost sure it is physical defect of some kind, you should probably take it back for replacement.
I don't know if the accelerometer issue related to Button Savior began when I first installed the app (as opposed to coming from a particular app update, for instance) as it took a long process of elimination to find the connection. As to the "upside down" issue I believe it has always done that. However -- it only does it if I TURN ON the device while it is upside down. If I start using it facing up, say watching a video, and then turn it upside down the video continues to play flawlessly. Bizarre!
I know there is an option to use the light sensor to detect when your phone is in your pocket, and turn off. Maybe it's on on your phone, and it's detecting lower light when you flip it over and shutting the screen off?
ok, so i misunderstood the issue, i thought the phone turns off completely...
if it only goes into "silent" or "lock" mode... maybe you installed some kind of app that does that when you flip? or maybe your player has one of those settings? like... say you are in a meeting, with your phone on the table, it rings... you just flip it and it goes silent.... some android build have that as a default setting already...
here, check this so u understand better what i mean :
http://www.appbrain.com/app/flip4silence/org.failedprojects.flip4silence
hope this helps!
tried updating yet? i had the same problems prior to the 65.1.40 update
Upgraded to CM11, but had this on 10.2 as well. Back and home buttons are rendered inoperable depending on how NT is positioned (rotated). Really annoying and I know they aren't shorted because BACK works in one position but not the other, same issue with HOME. Anyone know of a fix?
Anybody?
you're talking about the onscreen buttons in android, right? i've never had any issues
that happen to me
I had that same problem when I change the dpi from 160 to 265 and that when it happen to me. It took me a day or two before I realized what causes It but when I change the dpi back to 160 my buttons started to work just as they did before.I hope this helps you with your fix.good luck
Well I don't know if it's your case, but this happened to me as well, and I found that I had dead zones in touchscreen exactly where on screen home and back buttons are, the only way I could use home and back buttons again was rotating the screen to upside down portrait (I could not pull down controls menu in this position since that part of screen was dead) or in landscape.
How I found out: download this app. from Google Play https://play.google.com/store/apps/details?id=com.rn.yamtt, turn your tablet to landscape so on screen buttons will change positions. Open the app. and select paint tester and move your finger on the part of the screen where the on screen buttons wasn't working in portrait mode.
If you have dead zones like me, the app. won't paint the area where you are moving your finger because the touchscreen is dead in that area.
Also, my nook developed another problem after this, it won't charge, and when I plug the power cord, tablet crashes and reboots and stay in a bootloop unless I remove the cable. I'm 100% sure the cable and charger are ok, my nook suddenly started to show a lot of problems, I'll miss my nook =/
so what did you do to fix it?
F. Gacrux said:
Well I don't know if it's your case, but this happened to me as well, and I found that I had dead zones in touchscreen exactly where on screen home and back buttons are, the only way I could use home and back buttons again was rotating the screen to upside down portrait (I could not pull down controls menu in this position since that part of screen was dead) or in landscape.
How I found out: download this app. from Google Play https://play.google.com/store/apps/details?id=com.rn.yamtt, turn your tablet to landscape so on screen buttons will change positions. Open the app. and select paint tester and move your finger on the part of the screen where the on screen buttons wasn't working in portrait mode.
If you have dead zones like me, the app. won't paint the area where you are moving your finger because the touchscreen is dead in that area.
Also, my nook developed another problem after this, it won't charge, and when I plug the power cord, tablet crashes and reboots and stay in a bootloop unless I remove the cable. I'm 100% sure the cable and charger are ok, my nook suddenly started to show a lot of problems, I'll miss my nook =/
Click to expand...
Click to collapse
wedmiston said:
so what did you do to fix it?
Click to expand...
Click to collapse
Nothing since this has no fixes, part of the touchscreen is simply dead, unless a miracle happens, I even tried to restore stock nook rom, opened my tablet to check if there is a loose cable or something.
Is this happened to you in the same day you opened this thread? If your answer is yes, this sounds funny, because it's exactly the day when this small part on left bottom of the touchscreen died in my nook.
Also, somewhat my tablet started to charge again, but very slow, like USB charging, but I'm happy my nook returned to life.
No this happened many weeks before the thread. All of a sudden both home and back touches no longer worked in portrait position, but DO work in Landscape. Annoying.
F. Gacrux said:
Nothing since this has no fixes, part of the touchscreen is simply dead, unless a miracle happens, I even tried to restore stock nook rom, opened my tablet to check if there is a loose cable or something.
Is this happened to you in the same day you opened this thread? If your answer is yes, this sounds funny, because it's exactly the day when this small part on left bottom of the touchscreen died in my nook.
Also, somewhat my tablet started to charge again, but very slow, like USB charging, but I'm happy my nook returned to life.
Click to expand...
Click to collapse
wedmiston said:
No this happened many weeks before the thread. All of a sudden both home and back touches no longer worked in portrait position, but DO work in Landscape. Annoying.
Click to expand...
Click to collapse
Did you made the check I mentioned before? Does the back and home buttons works if put your tablet in upside down position so portrait mode will move soft buttons to the top edge?
Yes - all three DO work when I flip it upside down in portrait. Is this my workaround?
F. Gacrux said:
Did you made the check I mentioned before? Does the back and home buttons works if put your tablet in upside down position so portrait mode will move soft buttons to the top edge?
Click to expand...
Click to collapse
wedmiston said:
Yes - all three DO work when I flip it upside down in portrait. Is this my workaround?
Click to expand...
Click to collapse
Unfortunately, you have the same problem as me - dead zone in touchscreen. Flip the tablet upside down in portrait or use in landscape are the only workaround afaik. I thought in moving the on screen buttons more to the right in a zone where the touchscreen is working, but I didn't find a way to do this, I managed to move them a little bit by adding more buttons in the bar in system settings, but the back button would still stay in the dead zone, them I switched home and back buttons positions (so home stays in the dead zone) since you can still use the tablet N button to use home function.
Hello people,
I've noticed a weird problem with my Samsung S2 running Gingerbread 2.3.5 (yes, I know, it's old... but the last time I've upgraded to anything more recent, the battery lasted less than one day. I'll happily receive any advices on newer versions tho).
let me tell the story:
the phone is "quiet", with the screen black.
...a message arrives! (doesn't really matter if it's an SMS, Telegram, WhatsApp or anything else. Even notes will be affected, everything needing a keyboard input)
I press the power button, the phone "wakes up" and shows me the lock screen - I've set a static image with the time in the upper area.
so the phone starts running and I go to the desired application (sms/telegram/notes/etc...)
the keyboard (swype keyboard, but is the same also with my other 2 keyboards) shows up.
I try to input letters, words, but nothing gets written. If I press longer to get to the special character selection, I can't select any of them, all I can do is touching the Back button and return to the keyboard.
I usually press a key from time to time to see when the keyboard starts working.
After a delay of ~15 seconds it starts working, but I have to be careful not to let the phone going back to sleep or I will have to endure the delay again (this usually happens during a chat and it's quite annoying).
so, I suspect there is some application that gets stuck after waking up from the lock screen, but does anyone have experienced this? Any ideas on what it could be?
Thanks!
Best Regards
Max
Today I got my phone in. I was on the first set up page and it wouldn't respond to any of my touches. The buttons would glow like I was touching them but it wouldn't type or input. I soft reset it. It worked when I used assist touch. I hard reset it, wiped cache and factory reset. It fixed and I installed all my apps and when I plugged it into the charger it stopped working again. I can open the camera by double pressing the home button to unlock my phone but i can't open anything. It will glow like I'm pressing it but it won't open. I can pull down my notifications bar but none of my toggles or setting icon will work, again, they will glow just not open. I came back to my room and randomly it was working again, after 5 mins it stopped again.
Thank you for your attention.
ATT 64 GB
Galaxy S6 (not edge)
I don't know if this is the cause/solution to your problem, but I know S Voice can cause lag issues. By default, double pressing the home button (when device is unlocked) opens the S Voice. Frankly, it's redundant and pointless, as it's a mediocre attempt at Google Now. Open it, then go into the settings, and disable it. It causes lag because it's waiting to see if you're going to press it again or not.
But if that doesn't fix it, and it's doing that stuff before you've even set it up, I'd tend to think you've got a faulty unit. The capacitive buttons are part of the screen/digitizer, so maybe you've got a bum one.