Hi Folks,
Interesting behaviour...
Docked TF701T - Kitkat 4.4.2 (stock, not rooted)
Chrome - 46.0.2490.76It appears that running the above version of Chrome will cause my keyboard dock touchpad mouse, and any USB attached mouse, to get disabled. Indeed, writing this makes me think that the dock has nowt to do with it, but the mouse interrupt handling area of Android is being messed with by Chrome.
Has anyone else seen this?
The behaviour appears to be that everything works fine for a brief moment while Chrome loads up, but after an undetermined amount of time (of the order of a few seconds), the mouse interrupts (I'm guessing) no longer get handled. The mouse stops responding to input, and, eventually, the mouse pointer disappears, never to reappear again (the pointer disappearing isn't directly a symptom - it's simply disappearing as expected in the absense of any mouse input).
Toggling the enable/disable touchpad key has no effect. However, undocking the keyboard, then re-docking brings the mouse back again for a brief period before the interrupts get ignored/blocked after a few moments.
Disabling Chrome seems to prevent this issue from arising (writing this using the stock Browser instead) and the mouse pointer is still happy...
I've not tried the dev or beta versions of Chrome yet.
[Update] Looks like the USB mouse dies, not because of mouse interrupts, but the USB port is getting powered down - as discovered when plugging in a USB hub or memory stick - no LED activity).
[deleted]
From your description it may be more likely to be dock hardware related.
Sent from Galaxy S-III with shoe on head
Problem found...
I had a look at logcat, to see what was going on, and it looks like there was some corruption in the sqllite database (possibly due to some catastrphic crashes previously while testing a broken dock). I decided to factory reset the tablet, and, so far, the problem seems to have disappeared...
Not sure why Chrome seemed to trigger the symptons, but hitting reset has resolved it.
bruisah said:
Problem found...
I had a look at logcat, to see what was going on, and it looks like there was some corruption in the sqllite database (possibly due to some catastrphic crashes previously while testing a broken dock). I decided to factory reset the tablet, and, so far, the problem seems to have disappeared...
Not sure why Chrome seemed to trigger the symptons, but hitting reset has resolved it.
Click to expand...
Click to collapse
Very good. I happy the issue was software related. I sometimes hesitate in reseting factory settings because I fear I will loose something, but it is absolutely the way to go before pulling out the soldering iron.
Sent from Galaxy S-III with shoe on head
Related
So I have the stock, froyo 2.2.2, non-rooted, wifi only version of the DS7. I have been having some real issues with the stock browser (only browser on device so far). I notice it mostly when I try to access the xda website (compact view) from the device (which is almost daily now). The browser will freeze, then I get an error message saying it has stopped responding and it asks to force quit or wait. I have good to excellent signal strength when this occurs. Tonight it happened again, and I quit it. Then tried to reopen multiple times only to get a white screen. It is acting very buggy at this point. White screens and non-responsiveness. I cleared the cache (1 Tap cache cleaner) and tried again only to get the same white screen. If the only fix is to get another browser from the market that is fine, however, if after I do that can the stock browser be deleted? I like the stock browser if it will work correctly. Sorry for all the issues. I'm starting to wonder if its me or if Dell has released an inferior product. This theory is only reinforced by the fact that none of the tech stores carry the device nor any accessories for it, but that is just a theory. Any ideas on browser issue? Thanks in advance!
The stock browser is made by Google, and it has always been inferior. I personally don't use it and I don't know of many who use it. Try Opera, its what I use.
::UPDATE::
After last nights little episode, as I said earlier, I turned it off and charged it. Right before I went to bed I turned it back on and everything was ok. I turned the wifi off, left the device on standby or sleep, and it had a full battery. Now this morning when I woke up, it wont turn on. When I plug it into the charger, I get no lights, no indication that it has even been plugged in. And it WONT TURN ON! HELP!!
UrbanAlkemist said:
After last nights little episode, as I said earlier, I turned it off and charged it. Right before I went to bed I turned it back on and everything was ok. I turned the wifi off, left the device on standby or sleep, and it had a full battery. Now this morning when I woke up, it wont turn on. When I plug it into the charger, I get no lights, no indication that it has even been plugged in. And it WONT TURN ON! HELP!!
Click to expand...
Click to collapse
Try the pinhole reset, then see if it turns on or charges.
As for the browser, I love the stock one. Dolphin HD is another good choice (a few others out there, such as Opera). Personally, I always end up back on the stock browser. This is not a browser issue (at base), so something else is going on; even if it's an issue of a corrupted browser apk. Try another browser and see if that fixes it (if you can get your S7 on).
Doesn't that reset the device as in restoring to factory settings? Won't that erase everything I have done so far?
UrbanAlkemist said:
Doesn't that reset the device as in restoring to factory settings? Won't that erase everything I have done so far?
Click to expand...
Click to collapse
No, it forces a restart like the reset button on your computer.
Thanks. Got it done.
Glad you're up and running; now go root that sucker! Just on principle . . .
Try Dolphin HD
I would HIGHLY recommend trying dolphin hd browser. The biggest benefits, for me anyway, is it's xmarks plugin and lastpass plugin.
I have an inspire 4G android phone, dell streak tab, work desktop, travel laptop and wives pink netbook all running those 2 plugins and it works GREAT!
Xmarks syncs all your devices bookmarks between ALL the machines you use. Every computer i turn on is identical. If you change or add a bookmark on one device, all the others are updated instantly. The other nice thing is it's "open tabs" screen. You can see what tabs are open on another computer and open that same page directly on your tablet or smartphone. Theres a lot more, just read up on it.
Lastpass, if your not familiar will sync all your passwords across all your devices, including the DS7 when using Dolphin browser. It really comes in handy when you just cant remember that login password that your office computer remembers. With last pass, it will automatically enter it from any of the supported devices you use.
There are lots of other plugins for it too. I used to use opera, but setup this way dolphin is the BEST!!!
UrbanAlkemist said:
So I have the stock, froyo 2.2.2, non-rooted, wifi only version of the DS7. I have been having some real issues with the stock browser (only browser on device so far). I notice it mostly when I try to access the xda website (compact view) from the device (which is almost daily now). The browser will freeze, then I get an error message saying it has stopped responding and it asks to force quit or wait. I have good to excellent signal strength when this occurs. Tonight it happened again, and I quit it. Then tried to reopen multiple times only to get a white screen. It is acting very buggy at this point. White screens and non-responsiveness. I cleared the cache (1 Tap cache cleaner) and tried again only to get the same white screen. If the only fix is to get another browser from the market that is fine, however, if after I do that can the stock browser be deleted? I like the stock browser if it will work correctly. Sorry for all the issues. I'm starting to wonder if its me or if Dell has released an inferior product. This theory is only reinforced by the fact that none of the tech stores carry the device nor any accessories for it, but that is just a theory. Any ideas on browser issue? Thanks in advance!
Click to expand...
Click to collapse
I use skyfire for browsing, and the custom XDA application for working here on XDA.
http://www.phonejoy.us/
It works with our phones but I did notice a half a second delay from an action to a reaction (Super mario world - I press a button, it takes half a second before mario jumps). So platforming may be off the list until the controls become more tight.
A heads up for anyone trying to configure the controller. You have to the keyboard FIRST to PhoneJoy IME running BEFORE you can connect your gamepad, which disables you're ability to enter numbers. So have 1234 copied from a test message and then you can paste the numbers in AFTER during the pairing process.
Also the controllers feels exactly like the PS3 controllers with the one exception of being lighter. (probably because the rumble motors & weights are missing).
*** I no longer advise purchasing this device ***
Glitch04 said:
http://www.phonejoy.us/
It works with our phones but I did notice a half a second delay from an action to a reaction (Super mario world - I press a button, it takes half a second before mario jumps). So platforming may be off the list until the controls become more tight.
A heads up for anyone trying to configure the controller. You have to the keyboard FIRST to PhoneJoy IME running BEFORE you can connect your gamepad, which disables you're ability to enter numbers. So have 1234 copied from a test message and then you can paste the numbers in AFTER during the pairing process.
Also the controllers feels exactly like the PS3 controllers with the one exception of being lighter. (probably because the rumble motors & weights are missing).
Click to expand...
Click to collapse
Hello, did you find so far a solution for the delay thing? I have 2 phonejoy and i got some issues with it:
=>I have always some error message popup from Bluez IME that are saying something like:
"disconnect, error"...
=>With suerGNES i have an issue with mario kart rom, sometimes during a race the controler is not responding during some seconds, and suddently it will respond again. So far i didnt see the same thing into another game, i'll see.
=>I noticed this input lag issue with another one TV set, maybe it's coming from the TV+Mhl cable, i'm not sure.
See u
int0x13 said:
Hello, did you find so far a solution for the delay thing? I have 2 phonejoy and i got some issues with it:
=>I have always some error message popup from Bluez IME that are saying something like:
"disconnect, error"...
=>With suerGNES i have an issue with mario kart rom, sometimes during a race the controler is not responding during some seconds, and suddently it will respond again. So far i didnt see the same thing into another game, i'll see.
=>I noticed this input lag issue with another one TV set, maybe it's coming from the TV+Mhl cable, i'm not sure.
See u
Click to expand...
Click to collapse
Yes I have tried several phones, and even the bluetooth pc options, the lag persists. It seems no matter what system I have used it on, there will always be a half a second lag at least. I regret my purchase now, and have moved on to PS3 controllers that (when compatible) have a better response time.
I don't recommend this device anymore unless you are navigating options menus like XBMC or a music player remotely.
Glitch04 said:
Yes I have tried several phones, and even the bluetooth pc options, the lag persists. It seems no matter what system I have used it on, there will always be a half a second lag at least. I regret my purchase now, and have moved on to PS3 controllers that (when compatible) have a better response time.
I don't recommend this device anymore unless you are navigating options menus like XBMC or a music player remotely.
Click to expand...
Click to collapse
Did you try on another TV? Did you try to set your tv picture settings into "Game mode"?
What about my questions, any clue?
Okay, I've got several Samsung Keyboard issues, so bear with me as I explain as it may be a bit long.
First and foremost, my keyboard keeps crashing. At first, I assumed this was just a general issue that a reboot was necessary in order to fix. This is entirely not the case, as it even happens directly after a reboot at times. Also, they keyboard crashing happens in several different ways. This normally happens while using Kik messenger, but it does happen at times while using normal text messaging as well, so I'm assuming Kik isn't the problem.
1)Normal keyboard crash, where it gives an error and the phone tells me it has stopped working.
2)Keyboard entirely disappears, yet I can still type by touching the black area where the keyboard would normally be.
3)Keyboard doesn't disappear, but text entered doesn't appear inside the text box until after closing the keyboard.
4)Keyboard crashes normally, causing either (2) or (3) to happen.
I'm unsure what's going on. I am running a rooted system, so I'm guessing it may be some issue with the root combined with something I've installed, but I'm unsure what it could be. Keyboard was (and has been) working fine for months and months, and I haven't installed anything new since the day I rooted.
I'm rooted with Rooted Community Rom. I've not had any problems with this root since I've installed it, so I don't know what the Hell is going on. Any input would be wonderful, especially if someone could tell me what's causing this to happen, or if others have this issue.
BobScramit said:
1)Normal keyboard crash, where it gives an error and the phone tells me it has stopped working.
2)Keyboard entirely disappears, yet I can still type by touching the black area where the keyboard would normally be.
3)Keyboard doesn't disappear, but text entered doesn't appear inside the text box until after closing the keyboard.
4)Keyboard crashes normally, causing either (2) or (3) to happen.
Click to expand...
Click to collapse
I'm thinking 1) is due to Low Memory causing Force Close (due to many running apps) or the Keyboard App data somehow got corrupted and 2) and 3) are happening due to GPU not being able to draw the Keyboard and letters when called upon; can't entirely be sure unfortunately.
I can think of two solutions to try however:
Clear Data and Cache of Keyboard App
Go to Settings -> Apps -> ALL -> Keyboard
Select Clear data and Clear cache
Reboot or start a messaging app and start typing again
Try another Keyboard App
Many options available, try: AOSP Keyboard, Google Keyboard, Swype
Hope that helps!
Clearing it and letting it reload does fix all of the issues, but it just happens again shortly after. I don't have very many apps, and normally still have around 100MB RAM free at all times. I don't use social media or anything on the phone at all, and most everything else is just Google things, Kik messenger, and stuff pre-installed on the phone(Like the normal sms app, phone app, etc) Reboot, clearing memory, etc, all have the same result. Fixes the problem, only for it to happen again shortly afterward. Sometimes, in the case of the keyboard going blank, clearing memory doesn't fix the issue. It re-loads with a blank keypad. Doesn't happen very often, but it did once or twice today.
I've tried using Swype since it's already pre-installed, but it's not really the same size as the standard keypad and it's difficult to adjust to typing on it :\ I suppose I'll have to make due with using it for now, because that keypad doesn't seem to freeze or crash at all as I've used it (wasn't for very long, but the normal keypad tends to crash at least twice within the span of an hour if it's used regularly).
It wouldn't even be a problem if it wasn't happening so damned often. I'm used to things crashing at random, because having a load of apps (before) caused it to make things crash sometimes. But this is definitely not a "sometimes" issue. It's a "Please God, make it stop" issue lol
BobScramit said:
It wouldn't even be a problem if it wasn't happening so damned often. I'm used to things crashing at random, because having a load of apps (before) caused it to make things crash sometimes. But this is definitely not a "sometimes" issue. It's a "Please God, make it stop" issue lol
Click to expand...
Click to collapse
I know how that feels. I remember experiencing those keyboard symptoms you mentioned in the past. Frankly, I couldn't leave the stock ROM fast enough.
You should try AOSP or Google Keyboard, the keys are bigger and appear less confusing than Swype.
Anyone else with this phone using Android Auto? I've been having issues with my Kenwood DDX9207S head unit where it sometimes doesn't initialize AA properly, is more often than not very laggy, etc. Sometimes it runs smoothly, as I would expect for a phone of this class with these specs, but it's getting pretty frustrating. I've tried clearing Android Auto's data/cache and uninstalling and reinstalling it, but nothing seems to help. I'm not sure if it's an AA issue, phone issue, or possibly the head unit (very doubtful, but the screen sometimes stays stuck on AA after disconnecting the phone). I can sometimes resolve the issue simply by unplugging and replugging the phone in, sometimes I have to kill all app processes, and sometimes I have to flat out reboot the phone.
EDIT:
Did some testing last night and this morning during my commute (I sit in a lot of traffic, don't worry) and found a possible culprit: Settings. I looked at the memory usage for apps, and without fail, everything was using very little memory except Settings, which was eating 100-300mbs. Killing the process instantly made AA responsive again, but within 5-10 minutes, I was seeing lag again, and Settings was building up memory usage. I'm going to perform a factory reset on the phone today to see if that alleviates the issue.
EDIT II:
After factory resetting the phone, I'm not seeing issues, SO FAR, with AA. The settings thing wasn't the right target. I still get high RAM numbers with it regardless, and I see the same thing on my Tab S2, so that's obviously not what was causing the issue. The difference *might* be that I disabled a lot of AT&T bloatware before, and in doing so might have messed something up. I'm leaving everything enabled right now, so we'll see how this goes. I only have one car ride under my belt so far, so it's not a very scientific comparison.
EDIT III:
Ran into the exact same issues earlier this afternoon. Plugged the phone in, got the "Accept" screen on my head unit, and then blank. I looked at my phone and realized that AA didn't actually launch, so I unplugged it and plugged it back in. It launched that time, but the lag was there. I can take up to 10 seconds for AA to register a touch, and Maps freezes up constantly for 10 seconds or so before trying to catch up (it usually doesn't catch all the way up before it freezes again). This makes AA more or less unusable for me. I can't find anyone else out there that has had these issues with AA and this phone, so I'm unsure of what the issue actually is. The only difference between last night and today is that last night I was listening to podcasts through Pocket Casts, and today I used Audible. I'll do a bit more testing with/without Audible to see if that's the culprit; I know AA support is relatively new on Audible (though it was in the beta for a while). Again, I haven't seen anyone complain of poor AA performance while using Audible, so I don't know if that's the issue. I wish I had a Nexus to test this against to see if its the phone...
Having the same issue it does not connect all the time
I recently started getting a lot of AA disconnects from my Samsung phone and my AA stereos - I have an Android Chinese unit as well as a Kenwood Excelon in my second car. Thought the cable might be the issue but that didn't seem like it.
I went in to the apps menu and found that under system apps, there are 2 more AA related apps. Proceeded to turn off battery optimizations for all 3 and now it seems to be running stable.
The apps are:
Android Auto (DUH!)
android.auto_generated_rro_product__
android.auto_generated_rro_vendor__
You're the f'ing man! I could kiss you.
Didn't work for me.. only fix I have found is tap the usb options [while plugged in] on phone and tell the phone that the plugged in device manages connection.. unfortunately this setting does not remain set after use.