Related
I have been on the fence for this ever since it has been out. I have been to bestbuy and verizon to test out the demo units multiple times and both units seem to have the same issue.
When I open some apps, say dolphin hd for example, I can see screen artifacts for a second. Like colored dashes of varying lengths, and this seems to happen often.
Second, when I am trying to pinch and zoom or scroll in Dolphin, it jerky and spastic, there was one other app that did this as well but I can remember which one. The scrolling on the stock browser seems ok but not the best.
Anyway, do any of you see this? More than likely a software fix, but hey, you never know.
And a rant, who on earth thought of that flimsy power adapter, good grief, they were both broken and the two stores when I first went to look but have since been replaced. And the power button? I have to turn it over to find it.....
Rant off and hoping to fall of the fence.....
Matt
The power button is actually placed well I think. It's not in the way and not hard to get to. I rarely have my device on a table cause of the viewing so it's not a hassle. Also I have not experienced that with dolphin HD on my device.
It's a Dolphin HD problem.
The stock browser rocks.
I haven't noticed any screen artifacts on my display whatsoever. For the most part I disregard demo displays in any store, as you have thousands of people with their hands all over it and the mentality of "Its not mine, what do I care?". God only knows what was done to the demo units.
I have not used Dolphin HD browser at all, so I can't comment on that, i'll try and download it today and give you another reply. The android browser pinch to zoom works damn near flawlessly for me.
As for the power cable, yes I was a little weary of it and the size. But since the battery lasts for quite awhile on this thing, I just plug it in on my nightstand and it lasts me through the day.
My typical uses through the day are music, browsing the internet on breaks, work e-mail, picture management, and work e-mail (exchange push). I start work at about 8 o cloak and am usually done around 6. During this time theres constant use of e-mail and music, and when the day is finished I am around 35%-50% on battery depending on how the day has gone. When I am home, its light browsing and maybe a game for awhile.
The power adapter could become an issue if you plan on having it travel with you constantly, but in a fixed location for charging and nothing disturbing it, its not so much of an issue.
Are you seeing the artifacts? It is like a blip and then the app starts.
I know what you're talking about... but it only occurs for me with Dolphin. I used to use that as my main browser and pinch/zoom when it would try to reload the text/images it would be very jittery.
Again though it's the apps issue not the tablet or honeycomb.
I just had to change the default browser to load as a desktop and not as a mobile device.
i know this probably a common excuse, but HD Dolphin isnt made for honeycomb. Dolphin is making a tablet specific browser and hopefully it'll be release soon. i have both installed just to keep my browser option open.
as for the power button, i think it's the best place. what you dont release from the demo unit is that when actually have in your hands, it's completely different. if the power button was along the side anywhere, it could be easily hit. especially laying down it on it side or even having it in a tablet stand. i even have some issues with the volume button when i place it in my tablet stand.
besides all that, i contact Quickoffice and asked about whether they're developing a Honeycomb specific Quickoffice with editing and making new documents. they said yes
I use the stock browser with no problems.I don't see why they had Dolphin browser on the Xoom anyway because its not designed for honeycomb & furthermore those demo units are no way to judge the Xoom anyway.People push everything in sight on them & mess them up anyway.
I'm surprised they don't perform a reset every once in a while to clear up the device of any hangups.
Though I guess it makes for a pretty good stress test to see if it can handle anything that is thrown at it.
Mooem7 said:
I'm surprised they don't perform a reset every once in a while to clear up the device of any hangups.
Though I guess it makes for a pretty good stress test to see if it can handle anything that is thrown at it.
Click to expand...
Click to collapse
yeah I put all kind of stuff on there testing stuff I read here.
Launcherpro
dolphin
spareparts
asee ( app i use for my home dvr)
The verizon store also had an ipad right next to it, and I do have an ipad now, but love my Droidx.
the other thing I seem to notice is that the colors are a little washed out on the xoom compared to the ipad and the ipad is much brighter, but that always is best especially late at night in the bed. The ipad is to brit on tne dimmest setting.
Man i just cant decide to drop the dough....
OK, so here's my problem. I recently returned my nexus 7 for a newer production date build because I had a horrible touch screen. I updated the new one and had missed touches/sticky keys but when I unlocked it to apply sfhub's fix it wiped everything and the problem is gone (maybe a bad upgrade install?) Every once in awhile it feels like it's still missing a touch. Like once every couple hours. I've noticed that the touch screen is very sensitive and if I move my finger a little bit while touching it registers as a swipe I guess. Is there a way to see if it's really not seeing the touch or registering as something different? There are no sticky keys whatsoever and multi-touch seems to work fine in a case or out. Does anyone else see this with theirs?
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
Enable developer options and see the touches
You can test/verify the touches by enabling the developer options on the Nexus.
To do this, go to settings, go down to "About tablet", and then down again to the build number. Tap the build number information ca. 5 times (5 to 10? after a few taps you will see an info sign about how many times you still have to tap), this enables the developer mode.
In the settings menu there should be now a new item, Developer options (just before the About tablet). In the developer options check the box named "Pointer location".
Now when you touch the screen, with one or more fingers, you can see a screen overlay with coordinates and axles showing where the device sees your touches.
I have the touchscreen problem with missing and sticky touches and pinch and twist problems, the whole menu. For example, using google maps or writing emails is a pain in the ass because of these touchscreen issues.
On my device once I enable the "show the pointer location" -feature, I can clearly see that the device registers the touches right, but it behaves differently from the touches.
According to this I see, at least on my device, this more as a software than a hardware problem, and it looks that the problem is maybe even on a higher API level, which is IMO a good thing, because it _might_ be fixed with a firmware update. The question is, why Google hasn't done this yet, as the issue has been there around the world for a while, and there have already been a couple of updates (Q & R, or even more?) which haven't fixed the problems.
It would be interesting to hear reports of other devices. Test and report!
May82 said:
OK, so here's my problem. I recently returned my nexus 7 for a newer production date build because I had a horrible touch screen. I updated the new one and had missed touches/sticky keys but when I unlocked it to apply sfhub's fix it wiped everything and the problem is gone (maybe a bad upgrade install?) Every once in awhile it feels like it's still missing a touch. Like once every couple hours. I've noticed that the touch screen is very sensitive and if I move my finger a little bit while touching it registers as a swipe I guess. Is there a way to see if it's really not seeing the touch or registering as something different? There are no sticky keys whatsoever and multi-touch seems to work fine in a case or out. Does anyone else see this with theirs?
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Try playing some heavy multitouch games. I'm playing Terraria. Requires fine motion. You'll notice anything in that game.
Sent from my Nexus 7 using XDA Premium 4 mobile app
kotivalo said:
You can test/verify the touches by enabling the developer options on the Nexus.
To do this, go to settings, go down to "About tablet", and then down again to the build number. Tap the build number information ca. 5 times (5 to 10? after a few taps you will see an info sign about how many times you still have to tap), this enables the developer mode.
In the settings menu there should be now a new item, Developer options (just before the About tablet). In the developer options check the box named "Pointer location".
Now when you touch the screen, with one or more fingers, you can see a screen overlay with coordinates and axles showing where the device sees your touches.
I have the touchscreen problem with missing and sticky touches and pinch and twist problems, the whole menu. For example, using google maps or writing emails is a pain in the ass because of these touchscreen issues.
On my device once I enable the "show the pointer location" -feature, I can clearly see that the device registers the touches right, but it behaves differently from the touches.
According to this I see, at least on my device, this more as a software than a hardware problem, and it looks that the problem is maybe even on a higher API level, which is IMO a good thing, because it _might_ be fixed with a firmware update. The question is, why Google hasn't done this yet, as the issue has been there around the world for a while, and there have already been a couple of updates (Q & R, or even more?) which haven't fixed the problems.
It would be interesting to hear reports of other devices. Test and report!
Click to expand...
Click to collapse
Yeah i feel the same too. I think the problem is software/drivers related than hardware and i dunno if there is a "perfect" device out there at all. I feel many casual users are simply not experiencing it. What i find odd is that, it always feels better after a reboot and things start to deteriorate from there. Almost like memory is not being released properly and there's some stucked process being stacked etc etc. Personally i find that eliminating the use of Chrome entirely has worked better for me. Am using only Dolphin now and it's been going very well so far.
The latest touchmark results shows there is a high latency in the Nexus 7 2013 model. It also indicates that it could be due to frequency of CPU polling for touches with a combination of other things in GPU too. IMO i think the high DPI on the screen and the handling of the quadcore processor might require some tweaking to get it perfect. There seems to be too much latencies and perhaps the missed touches / stuck touches are due to a combination of problems in the code with regards to touch events handling. Oh well, regardless i think they need a taskforce behind it to resolve it.
http://appglimpse.com/blog/touchmarks-ii-touchscreen-latencies-in-flagship-tablets/
lomonic said:
http://appglimpse.com/blog/touchmarks-ii-touchscreen-latencies-in-flagship-tablets/
Click to expand...
Click to collapse
Interesting!
lomonic said:
Yeah i feel the same too. I think the problem is software/drivers related than hardware and i dunno if there is a "perfect" device out there at all. I feel many casual users are simply not experiencing it. What i find odd is that, it always feels better after a reboot and things start to deteriorate from there. Almost like memory is not being released properly and there's some stucked process being stacked etc etc. Personally i find that eliminating the use of Chrome entirely has worked better for me. Am using only Dolphin now and it's been going very well so far.
The latest touchmark results shows there is a high latency in the Nexus 7 2013 model. It also indicates that it could be due to frequency of CPU polling for touches with a combination of other things in GPU too. IMO i think the high DPI on the screen and the handling of the quadcore processor might require some tweaking to get it perfect. There seems to be too much latencies and perhaps the missed touches / stuck touches are due to a combination of problems in the code with regards to touch events handling. Oh well, regardless i think they need a taskforce behind it to resolve it.
Click to expand...
Click to collapse
Thanks lomonic, an interesting link.
I had the former/original Nexus 7 (until my oldest daughter accidentally dropped it in May), and it had no touchscreen issues, at least nothing as bad compared to my new Nexus 7 (2013 model). Yes, it lagged sometimes, as does also my Nexus 4 (mostly noticeable when you slide down the notification menu or open the open applications list), but it had no similar problems with the precision of the touchscreen of the new Nexus 7.
I just tried to reboot the device and also noticed the touchscreen performing a bit better. Though, the problem came back in no time, and after a couple of minutes using Google Maps was the same mess as before. Twisting/rotating the map with two fingers results to pinching/zooming and the map centers somewhere else you want it to. Also in Chrome zooming and scrolling doesn't work as expected, and selecting text is also problematic. Using the keyboard might get you a sticky backspace, which is somewhat annoying. I can only imagine how it would be to try to play touchscreen intensive games, which demand fast and precise touches.
On my Nexus 4 I've also noticed that Chrome seems to slow the whole device, and for this reason I've also been using Dolphin for a while now (but I've yet not deleted Chrome, I just don't use it). Maybe I should dump the whole app from my phone. Also using Clean Master to clean up the memory from apps/processes helps for a while, but only for a while.
Google (or Asus) could verify if there's a sw patch on the way. I'm not a gamer, I mostly use the tablet for surfing and reading, but also these task are not a pleasure with the touchscreen issue. If this problem still persist after a month or so, I really think about returning the device (I bought it just a week ago).
Chrome is super slow.
I don't know why but the stock Android Browser is super fast and awesome. I've been using Next Browser since it is based on Stock Android Browser but the past 2 recent updates have really screwed it up where it is beyond usable. Once it gets resolved, Next is really awesome. It is like Stock on Steroids.
However, regarding touchscreen issues, DON'T GO LOOKING FOR PROBLEMS. If you aren't having issues, then just relax and enjoy your tablet. If your tablet was plagued with a quirky touchscreen driver, then you would notice it. If you can't notice any issues, then you don't have any issues.
Sure there are tests you can run but why bother? It is a software problem and will be fixed eventually. This is not the first Nexus with quirky touchscreen drivers. In fact almost all of my Nexus devices had quirky touchscreen issues out of the box. All were corrected within a few updates. Even the Nexus One had a physical hardware problem with crossing axis that was alleviated using some Google Magic.
May,
I have the exact same issue--but my missed touches are once every 5 minutes--quite annoying when typing an email or typing a password. I haven't unlocked the tablet yet to apply sfhub's fixes--will let you know how it goes.
player911 said:
Chrome is super slow.
I don't know why but the stock Android Browser is super fast and awesome. I've been using Next Browser since it is based on Stock Android Browser but the past 2 recent updates have really screwed it up where it is beyond usable. Once it gets resolved, Next is really awesome. It is like Stock on Steroids.
However, regarding touchscreen issues, DON'T GO LOOKING FOR PROBLEMS. If you aren't having issues, then just relax and enjoy your tablet. If your tablet was plagued with a quirky touchscreen driver, then you would notice it. If you can't notice any issues, then you don't have any issues.
Sure there are tests you can run but why bother? It is a software problem and will be fixed eventually. This is not the first Nexus with quirky touchscreen drivers. In fact almost all of my Nexus devices had quirky touchscreen issues out of the box. All were corrected within a few updates. Even the Nexus One had a physical hardware problem with crossing axis that was alleviated using some Google Magic.
Click to expand...
Click to collapse
Stock android is fast but how do you get it with stock rom? chrome replaces it in 4.3 isnt it? OR are you on a custom?
I think the reality is that many are having problems but do not know about it. They may just dismiss it as not being accurate with their own touches. Also for some users, it could likely be their first touch devices and have no prior experiences to compare with. When i've gotten this device, it was working well and all, but it just feels like typing aint that smooth and slowly over time, the problems starts to be more frequent.
There was an incident i had when after a few days of usage, i tried using it with it lying on the bed and it was going crazy - which never happened before. I picked it up (attempt to earth it) and lay it back down again but the results are the same. So i did a reboot with the system on the bed, and all the problems went away. So i'm not sure it has to do with the earthing factor which many are citing.
I think it is a combination of GPU/CPU/memory and touch related event handling factors that causes the problems to occur more frequently after extensive usage. There should be no reason for hardware to perform perfectly after a reboot only to fail over time.
Oh well, only time will tell when these problems would eventually be addressed.
lomonic said:
Stock android is fast but how do you get it with stock rom? chrome replaces it in 4.3 isnt it? OR are you on a custom?
Click to expand...
Click to collapse
I guess you mean the stock android browser. It may not be available as an app but it's still there as a WebView component available to developers. I guess Dolphin and many other 3rd party browsers are based on the WebView component or on the source code of it.
The problem with the so called stock browser and WebView is that is uses some legacy HTML and JS engine that has not been updated since 2010 or so. That is another crappy developer "feature" from Google that for 3rd party developers there's no "web browser" component that is based on some up to date rendering engine like Chrome's.
In the Themes and Apps thread, there is a method to allow you to install the stock Browser on a stock rom without being rooted.
Also using Sfhub ts10 gave me a 90% fix but it would still spaz out occasionally and would miss touches or click weird stuff. ts20 really fixed me up right. I can play games now and type with no errors.
ts10 is a really good fix, but ts20 really hit it home.
Wow, talk about a terrible experience. The MOJO is absolutely NOT ready for production. I was able to find maybe 10 games that were even compatible with it, and only ONE game that actually used the controller as advertised. NOVA 3 almost worked but even then there were some functions that didn't work (like swapping weapons, sorta important). The list of compatible games is misleading; many of those games will load, but they will not function with the controller (meaning: not at all).
Madcatz claims that the TegraZone games will work with the MOJO - that is a lie. Only a handful of them actually work. A gaming console that only works with a handful of games is pretty useless.
I updated the firmware exactly as instructed, and after rebooting the wifi did not work at all (it did before the update). An Android console without functional wifi is a paperweight.
I am going to return this unit and try to get a Nvidia Shield instead. I got the MOJO for my kid for Christmass. Talk about a disappointment. Luckily he also got a PS4, so it wasn't a total disaster.
The MOJO is an interesting concept, and if they ever get it working right it might - *might* - be worth the money. But as of now, no, not even close. Stay FAR away from this thing for now. You've been warned.
I'm starting to agree....Out of the 372 apps I've purchased, only five were compatible and able to download. I've sideloaded a couple, but cannot map the controller properly.
I'll give it a few more days and some tinkering.
I wished to read this before I buy it back to ouya without developer MOJO = 0 with all respect
ExtremeRyno said:
I'm starting to agree....Out of the 372 apps I've purchased, only five were compatible and able to download. I've sideloaded a couple, but cannot map the controller properly.
I'll give it a few more days and some tinkering.
Click to expand...
Click to collapse
Interested in selling it?
Not just yet..I've been sideloading apps all day. Watching some streaming movies on it right now. It's a very capable machine, but fairly annoying having to sideload anything useful.
Well so far little disappointed but I like it just waiting until root which hopefully we can mod the build prop to show apps in store. Don't side load much using a aptoide. . From what I understand the tegra 4 still pretty new so I'm guessing that's why some of these games not playing. Patience it will get better
Yeah...Updated the firmware and now the Wifi is dead. Unable to "Turn On." WTF....
Yea the way I've mostly gotten over the No apps work issue is by sideloading. Its annoying though because if there's feature updates you have to backup from my other devices, transfer and install again to get the updates. The power is nice though. Nova 3 and Dead trigger look good even though their not a very good games its still a good showing of what the Mojo can do. And if you're into emulators most of them out there work great with the controller and have no trouble doing kool stuff. Unfortunately at the moment the mojo is mostly making me excited for a Minix device with equivalent specs as Minix devices don't have the same app store issue.
What are you using for your backups? I tried AppMonster, but haven't had a chance to sideload the backups to the MOJO yet.
Titanium Backup on a rooted device. It just backs apks to a zip file. If there's extra data I just move the obb files over manually via an sd card.
ExtremeRyno said:
Yeah...Updated the firmware and now the Wifi is dead. Unable to "Turn On." WTF....
Click to expand...
Click to collapse
This. When this happened, that's when I decided to return it. It's a paperweight without wifi.
fisterkev said:
This. When this happened, that's when I decided to return it. It's a paperweight without wifi.
Click to expand...
Click to collapse
Yea that really sux. That's the kind of stuff that you never want to see happen.
To be honest this feels more like a developer/beta release. The hardware is there and is for the most part great, could use an off/off button and an otg port. But the way it interacts with the ecosystem that currently exists is much too, I hate to say it, fragmented. There are more apps coming to the play store and I've seen a few pop in the last couple of days but its still hasn't hit anywhere near that critical mass point where its useable for anyone without some android nerdery. Which begs the question why didn't Mad Catz support that nerdery with things like an otg port, pre root/root tools at launch etc. Though the pre-bootloader unlock is a good start.
Its also clear google really has no interest in this kind of product YET by the way that the play store is currently laid out and hides paid apps from the main frontend, you have to search for paid apps specifically or by type. Its really going to be a rough year of slow apps incoming and building up momentum about this time next year I think it might start to be a valid for some main stream gamers. I'm worried that Mad Catz might feel that's too long to support and update this new market product. Luckily the markets going to grow either way but I'd like to see this product along for the ride.
All that being said I use this product every day, really like it, and whenever I'm home its on and being used in some way. Be that gaming, local movies, streaming video, or music but I took a path to set it up that very very few will and most I fear will have the same experience with '**** don't work then I updated It and less **** works. Return'. And that really sux.
So, I purchased from Amazon on 26th Dec. (Note, I'm REALLY trying to like this device because I really like the hardware). As an update to the OP info, mine came with firmware 0110 and NOVA 3's weapon change works fine, but the buttons are mapped really stupid - the trigger is not the fire button, the shoulder button is. Trigger changes weapons.
NFS MW installed from backed-up APK, and it detects controller and says you can set it up in the config menu, but you cannot get to the config menu with either controller, keyboard, or mouse, so it is unplayable.
I got a Real Racing 3 APK from a bad place and it does not seem to support controllers at all, and also does not seem to recognize the Tegra, so it is terrible looking and unplayable.
Shadowgun works great and you can assign all functions to buttons on the controller. This was also a backed-up APK. You cannot install the THD version; even if you could get the APK on there it won't let you dl the THD data.
Overall, my experience has been terrible. Yay! I'm so excited!
defectivedonkey said:
So, I purchased from Amazon on 26th Dec. (Note, I'm REALLY trying to like this device because I really like the hardware). As an update to the OP info, mine came with firmware 0110 and NOVA 3's weapon change works fine, but the buttons are mapped really stupid - the trigger is not the fire button, the shoulder button is. Trigger changes weapons.
NFS MW installed from backed-up APK, and it detects controller and says you can set it up in the config menu, but you cannot get to the config menu with either controller, keyboard, or mouse, so it is unplayable.
I got a Real Racing 3 APK from a bad place and it does not seem to support controllers at all, and also does not seem to recognize the Tegra, so it is terrible looking and unplayable.
Shadowgun works great and you can assign all functions to buttons on the controller. This was also a backed-up APK. You cannot install the THD version; even if you could get the APK on there it won't let you dl the THD data.
Overall, my experience has been terrible. Yay! I'm so excited!
Click to expand...
Click to collapse
I find the controller works better if I switch it do mouse mode or PC mode, depending on the game.
It's the game developers who must designate that a controller can be used for their game. If they don't, then no dice. Can't blame them tho, how could they have seen devices like these coming. I'm willing to bet almost EVERY new game becomes controller compatible. Hang in.. Still brand new device. Developers will adapt. And besides, unlike a ps2, it won't become outdated as fast. Games will just continue to improve!
Mojorising said:
I find the controller works better if I switch it do mouse mode or PC mode, depending on the game.
It's the game developers who must designate that a controller can be used for their game. If they don't, then no dice. Can't blame them tho, how could they have seen devices like these coming. I'm willing to bet almost EVERY new game becomes controller compatible. Hang in.. Still brand new device. Developers will adapt. And besides, unlike a ps2, it won't become outdated as fast. Games will just continue to improve!
Click to expand...
Click to collapse
Aww, we can blame the developers a little bit. I mean, come on, ANDROID developers? They often hang out on this very site where people have been hacking their butts off for years adding controller support to games. It might be a big deal to add controller support to a finished game if it wasn't developed with that in mind but I'm with you, it will be expected in the future.
In the mean time I would really like it if we could install one of those apps that lets you map buttons to touchscreen presses. That would help a lot!
defectivedonkey said:
Aww, we can blame the developers a little bit. I mean, come on, ANDROID developers? They often hang out on this very site where people have been hacking their butts off for years adding controller support to games. It might be a big deal to add controller support to a finished game if it wasn't developed with that in mind but I'm with you, it will be expected in the future.
In the mean time I would really like it if we could install one of those apps that lets you map buttons to touchscreen presses. That would help a lot!
Click to expand...
Click to collapse
Yes, but developers have been working on gamepad support. The MOGA supposedly has 230 games which work with their controllers, which happens to be a great feat because often developers are not likely to upgrade their older stuff (gameloft is notorious for this where their old games are "not compatible" with newer devices, even if the resolution is the same and the hardware more powerful.
solsearch said:
Yes, but developers have been working on gamepad support. The MOGA supposedly has 230 games which work with their controllers, which happens to be a great feat because often developers are not likely to upgrade their older stuff (gameloft is notorious for this where their old games are "not compatible" with newer devices, even if the resolution is the same and the hardware more powerful.
Click to expand...
Click to collapse
I think I got distracted writing the post you replied to. When I was talking about "controller support" I really meant to say something like button mapping. You know? Essentially, you let android handle the input device, and just have a method to map input signals to your calls. Like, how the emulators let you map each button press of a controller to an action in the emulator. By abstracting away the interface to the actual controller, ANY android supported device could be mapped. You would never have to worry about someone building a new controller that you have to write non-reusable code for. This MOGA nonsense just seems dirty, but then again, I'm not an Android dev, so there may be something more to it than I realize. I just can't put together in my head how I'd even write something that didn't abstract the input -- what if I wanted to change it later? I don't know....I hate the idea of "Support the MOGA!" "Support the CNTRLR!" No -- support everything! It SHOULD be easier!
defectivedonkey said:
I think I got distracted writing the post you replied to. When I was talking about "controller support" I really meant to say something like button mapping. You know? Essentially, you let android handle the input device, and just have a method to map input signals to your calls. Like, how the emulators let you map each button press of a controller to an action in the emulator. By abstracting away the interface to the actual controller, ANY android supported device could be mapped. You would never have to worry about someone building a new controller that you have to write non-reusable code for. This MOGA nonsense just seems dirty, but then again, I'm not an Android dev, so there may be something more to it than I realize. I just can't put together in my head how I'd even write something that didn't abstract the input -- what if I wanted to change it later? I don't know....I hate the idea of "Support the MOGA!" "Support the CNTRLR!" No -- support everything! It SHOULD be easier!
Click to expand...
Click to collapse
You mentioned the mapping but as an app. And I wasn't talking about MOGA versus CNTRL either. I was thinking more along the lines like with Windows PCs they have generic controller recognition (sure, you can install apps and drivers for better compatibility) where you normally get at least basic functionality. But yeah, one could avoid those problems if they had the same functionality of emulators where they map functionality based on the readings when buttons are pressed. It would make things quite a bit easier in general for them (a little but more work for us but only when playing a game for the first time).
The next app I'm gonna rip from my tablet is the Sixaxis app that allows you to map the buttons for the PS3 controller. I use it on my tablet for any possible game. You can assign buttons swipe actions, too. Very handy. There are a few other apps out there that do this with generic BT controllers, so we might just have to start trying them out. MadCatz surely should have created one for the MOJO before it was ever released. This was a big stupid on their part.
Hello All,
This is Nathan from Mad Catz. Our apologies for the inconveniences you've been facing. I unfortunately could not replicate your wifi problem. One note is that most MOJOs that have been made available should have already been on "MO0110-WW", so this step could be skipped if you don't need it.
Before any update, you can also go into your google account settings, choose your account, and then choose "Sync now" from the menu in the top right. If wifi is not working, you can use a wired ethernet connection to at least do this step. If you're forced to do the "factory reset" option to fix the wifi, when you do the initial setup again, choose to "restore" from your google account. Outside of apps that have been sideloaded, this should start downloads of everything that was downloaded from the google play store shortly after the initial setup is finished. You can check which ones are being re-downloaded by going into the Play Store and then checking your "My apps".
So I am loving the Mojo more than ever now that it has the Remix OS but I am still stuck with one annoying gripe. I cant seem to get my emulators to work without controller lag. The regular games seem to be fine but every emulator, no matter which ones I try, all seem to have the same input lag problem. Its not incredibly bad in fact some people might not even notice it but to me it annoys the crap out of me and makes games like Mario unplayable.
Does anyone else have this problem and if you do did you find a fix for it? Any help would be greatly appreciated!
Drakey83
Yes. I have significant input lag as well. I have been meaning to test it on a computer monitor to ensure that it isn't just my TV. However, I'm in the same boat as you because normal Android games do not have lag, whereas, emulators do. I think it might be an issue with the emulator itself, but you wouldn't know for sure unless you tested it on an Android smartphone with comparable specs.
TwistyTravster said:
Yes. I have significant input lag as well. I have been meaning to test it on a computer monitor to ensure that it isn't just my TV. However, I'm in the same boat as you because normal Android games do not have lag, whereas, emulators do. I think it might be an issue with the emulator itself, but you wouldn't know for sure unless you tested it on an Android smartphone with comparable specs.
Click to expand...
Click to collapse
When you running the emulator, default mode is windows mode. After running emulator, try put your mouse point on emulator icon on task bar and press mouse right button(or controller's button 2) and choose full screen mode. I think still there is input lag, but much better than window mode.
Hello all,
I just wanted to let all who are interested know that the MyGica A681 USB stick works 100%. I have it hooked up to one of those flat window mount antennas and it receives full HD signal that I view through the PadTV app found on Play Store. The PadTV app lacks in a lot of ways, it would be cool if someone around here was able to come up with something better. A few of the channels have a major A/V delay but it may be due to reception and not the tuner stick or app. Overall, it was a very worthwhile purchase for me, if anyone has any questions let me know.
Hopefully this is useful information for a cord-cutter somewhere. I'm not in any way affiliated with MyGica, just a fellow MOJO owner who couldn't find any info on a TV Tuner stick that would work with our boxes so I took the dive on my own.
Thanks buddy, this is a great discovery!
AndroidSupaFan said:
Thanks buddy, this is a great discovery!
Click to expand...
Click to collapse
No problem. I've pretty much been doing a lot of my own discovering what works since there's not much documentation for our devices. Like I said in my first post, it would be awesome if someone around here was able to come up with something better for a channel surfing app. PadTV gets the job done, but it's certainly not the prettiest. I forgot to mention that it also does DVR, but one of my issues is that it will only save to internal storage and not something like an external drive or an SD card. The channel info/current episode descriptions are several hours behind. If theres a button on my remote for Channel +/-, I haven't found it. You have to use your mouse to bring up and scroll through channels. Again, it gets the job done, I can watch 39 or so OTA channels, and quite a few of which are HD. It's just not the most MOJO friendly UI, since it was intended for phones.
Some other things I use daily that work 100%: Ouya controller (as 2nd controller), Plugables brand 7x USB 3.0 hub, & a Rii Mini i8 keyboard. Obviously stuff like my Logitech Bluetooth receiver that I run to my stereo also works to receive audio from MOJO. My USB wired Logitech PC game controller works great as well.
Just trying to help fellow XDA'ers and Googlers not worry about compatibility before they order something like I did. That said, most if not all of my worries were completely unfounded because everything I've thrown at the MOJO so far works like a charm!
Would a wired XBox 360 controller work?
psxfa said:
Would a wired XBox 360 controller work?
Click to expand...
Click to collapse
I don't have one to test but I'm 99% sure it would.
I'd just like to clarify a point: it may sound like nitpicking, but it's not the PadTV app that works; it's the PadTV-HD app. The standard PadTV just says it can't find a device.
That being said, the little MyGica is a little giant. I live in a fringe reception area, for decent reception I need a huge rooftop antenna, but this little thumb-drive-sized receiver still picks up a round dozen stations on the 10-cm piece of coat hanger wire it comes with. Yes, the weaker stations have audio lag problems; I hope a better antenna fixes that. It also costs about half what other similar units do, and most of them work on windows only.
I tried a few of the other TV apps on Play Store but the PadTV-HD was the only one that recognized the A681. I didn't find it all that bad an interface, except that the sidebars won't stay in place longer than a couple seconds, and I couldn't find a setting for that. It also lacks a volume control, as the MOJO itself does, so you must hope you have some control somewhere else. And there is no info in the EPG (electronic program guide) even though it appears to have that function. But I was able to find and watch several different channels without any real problems; except, of course, that TV programming in general sucks. Unless you're a sports fan.
So thanks, @tideee88, for the heads-up here!
kevinthefixer said:
I'd just like to clarify a point: it may sound like nitpicking, but it's not the PadTV app that works; it's the PadTV-HD app. The standard PadTV just says it can't find a device.
That being said, the little MyGica is a little giant. I live in a fringe reception area, for decent reception I need a huge rooftop antenna, but this little thumb-drive-sized receiver still picks up a round dozen stations on the 10-cm piece of coat hanger wire it comes with. Yes, the weaker stations have audio lag problems; I hope a better antenna fixes that. It also costs about half what other similar units do, and most of them work on windows only.
I tried a few of the other TV apps on Play Store but the PadTV-HD was the only one that recognized the A681. I didn't find it all that bad an interface, except that the sidebars won't stay in place longer than a couple seconds, and I couldn't find a setting for that. It also lacks a volume control, as the MOJO itself does, so you must hope you have some control somewhere else. And there is no info in the EPG (electronic program guide) even though it appears to have that function. But I was able to find and watch several different channels without any real problems; except, of course, that TV programming in general sucks. Unless you're a sports fan.
So thanks, @tideee88, for the heads-up here!
Click to expand...
Click to collapse
Yes, thank you for mentioning that it is in fact the PadTV HD app. Hope I didn't cause anyone any confusion. I also had no luck trying other tuner apps and I tried literally every one available on Play Store (including non-ATSC ones) and even tried sideloading a few because I dislike PadTV HD so much.
I agree that the MyGica stick is a great little device. I'm really impressed with it when it's able to do it's thing properly. I never tried the dinky little antenna it came with, I ordered a 25-mile distance flat window-mount antenna and it gets me about 39 channels here in Pittsburgh, PA. Lots of them are HD, and look and sound great. However, many of the Play Store reviews for PadTV HD seem to indicate that the slow motion, lag, and stuttering are a result of the app not taking advantage of hardware acceleration and thus is trying to encode 1080p on the fly via software rendering or something to that effect. Other than the mild inconveniences of things like not having a dedicated button for CH +/- and as you noted, the channel info being totally useless, it's a real bummer that I can't even get the channels I could be getting if it weren't for a poorly written app that is unfortunately our only option at the moment. I feel as though this is a real hole that could be filled with the rate at which Android set top boxes are becoming popular.
I mostly purchased this because the only time I ever need to watch broadcast TV is when my Steelers are on and hence have no use to pay for cable. I'm really hoping we have a new app sorted out before football season because FOX is one of the channels that currently comes in very laggy and out of sync for me at the moment.
Your MOJO doesn't have volume control, though? It certainly should. Do the hardkeys not work on your C.T.R.L.R.? Android system volume works perfect for me in all apps. Failing that, I've found you can change the volume in Pad TV HD by clicking somewhere in the video frame and dragging your mouse up or down, like a swipe if it were touch. Hopefully that helps!
tideee88 said:
Yes, thank you for mentioning that it is in fact the PadTV HD app. Hope I didn't cause anyone any confusion. I also had no luck trying other tuner apps and I tried literally every one available on Play Store (including non-ATSC ones) and even tried sideloading a few because I dislike PadTV HD so much.
I agree that the MyGica stick is a great little device. I'm really impressed with it when it's able to do it's thing properly. I never tried the dinky little antenna it came with, I ordered a 25-mile distance flat window-mount antenna and it gets me about 39 channels here in Pittsburgh, PA. Lots of them are HD, and look and sound great. However, many of the Play Store reviews for PadTV HD seem to indicate that the slow motion, lag, and stuttering are a result of the app not taking advantage of hardware acceleration and thus is trying to encode 1080p on the fly via software rendering or something to that effect. Other than the mild inconveniences of things like not having a dedicated button for CH +/- and as you noted, the channel info being totally useless, it's a real bummer that I can't even get the channels I could be getting if it weren't for a poorly written app that is unfortunately our only option at the moment. I feel as though this is a real hole that could be filled with the rate at which Android set top boxes are becoming popular.
I mostly purchased this because the only time I ever need to watch broadcast TV is when my Steelers are on and hence have no use to pay for cable. I'm really hoping we have a new app sorted out before football season because FOX is one of the channels that currently comes in very laggy and out of sync for me at the moment.
Your MOJO doesn't have volume control, though? It certainly should. Do the hardkeys not work on your C.T.R.L.R.? Android system volume works perfect for me in all apps. Failing that, I've found you can change the volume in Pad TV HD by clicking somewhere in the video frame and dragging your mouse up or down, like a swipe if it were touch. Hopefully that helps!
Click to expand...
Click to collapse
I'll try the volume control thing. I'm using CM12.1 and maybe it has a volume control somewhere but I haven't found it yet, I'm used to hardware switches. I'm not using the CTRLR either, just a keyboard & mouse. I'm still working on display resolution problems, as I don't really have the right display hardware for the MOJO, and it's picky that way. I'm about to give up entirely on the powered HDMI-2-VGA adapter to the 1280x1024 computer monitor, too unreliable even just in Android. Neither it nor the HDMI-2-DVI cable to the old Dell monitor will display at all in recovery, for that I have to commandeer the living room and the only true HDMI display in the house, which is a projector--not the best setup for tweaking a device. Still doing my homework on tweaking TWRP to 720P which I hope will solve that problem.
kevinthefixer said:
I'll try the volume control thing. I'm using CM12.1 and maybe it has a volume control somewhere but I haven't found it yet, I'm used to hardware switches. I'm not using the CTRLR either, just a keyboard & mouse. I'm still working on display resolution problems, as I don't really have the right display hardware for the MOJO, and it's picky that way. I'm about to give up entirely on the powered HDMI-2-VGA adapter to the 1280x1024 computer monitor, too unreliable even just in Android. Neither it nor the HDMI-2-DVI cable to the old Dell monitor will display at all in recovery, for that I have to commandeer the living room and the only true HDMI display in the house, which is a projector--not the best setup for tweaking a device. Still doing my homework on tweaking TWRP to 720P which I hope will solve that problem.
Click to expand...
Click to collapse
I'm running a rooted stock rom via HDMI so I'm not sure about your display issues as I haven't had any. But I use a bluetooth keyboard/mouse most of the time and the volume hardkeys work on that as well. If your keyboard has volume hardkeys and they don't work, it may be some sort of issue with your rom. AFAIK, my keyboard's drivers are just generic Windows ones.
tideee88 said:
I'm running a rooted stock rom via HDMI so I'm not sure about your display issues as I haven't had any. But I use a bluetooth keyboard/mouse most of the time and the volume hardkeys work on that as well. If your keyboard has volume hardkeys and they don't work, it may be some sort of issue with your rom. AFAIK, my keyboard's drivers are just generic Windows ones.
Click to expand...
Click to collapse
Same display issues regardless of ROM. AFAIK there are only four, and I tried them all. (This is a very rare instance of me following my own advice: try all the different flavors before deciding on a favorite.) Several people have reported similar issues while in system but I think I'm unique in the recovery problem. Changing the resolution by editing the build.prop improved my display in system but did nothing in recovery; I will just have to carry the MOJO into the living room whenever I need to use recovery, which shouldn't be that often. The bright side is that I learned to unpack and repack recovery images.
My keyboard is a wired mini with no extra room for media keys, but it does have a third control key (FN) to emulate them. But I can't see the blue-on-black icons to use them unless the room is brightly lit! Volume control is not a biggie for me though, I run the audio through a seventies-vintage amp and speakers. I pity those who grew up with "modern" surround sound, satellite speakers and a single subwoofer. My setups often fool both myself and the dogs, we can't tell if the noise is outside the open door or inside the TV.
BTW Windows keyboard drivers won't work on Android, but it's such a low-level thing they are just included in the kernel. Somewhere in the ROM is a keyboard map that can be edited (with root of course), but I misremember where. I never had to remap a keyboard.
PadTV HD app no longer works for me as of the latest update. For anyone considering purchasing a tuner, I recommend against it. Flushed $40 down the toilet.
If you'd like I'll send you the old version, I'll just need to save it then upload it. You'd just have to uninstall the newer version then sideload the old one and not allow it to update. Just PM me.
kevinthefixer said:
If you'd like I'll send you the old version, I'll just need to save it then upload it. You'd just have to uninstall the newer version then sideload the old one and not allow it to update. Just PM me.
Click to expand...
Click to collapse
Can you please send me the version that works?