Has anyone tinkered with the guts of the moto mod gamepad? I'm having an odd issue with the analog sticks. In apps with high sensitivity to stick position, I don't get the full range of motion in certain directions. This is almost certainly a factory calibration problem... on a PC I could just calibrate the device directly or find a workaround, but I don't know enough about android accessories/devices. Short of ripping it open and futzing with what I assume are hall sensors, is there a way to initiate some sort of device re-calibration, or change the values for 0 to max in Android?
I've sent a similar question to Lenovomoto, but I'm not hopeful.
Edit: I'm too green to upload images here, but gamepad tester output shows a 'flat tire' response from 11-oclock to 1 oclock.
I rock the stratus steelseries XL for Android gaming. It has never let me down....and paired with the projector mod is an epic combo... I would just return it get the controller and hold out for your promo..unless you already have it..then ur set...
Mr_Shakes said:
Has anyone tinkered with the guts of the moto mod gamepad? I'm having an odd issue with the analog sticks. In apps with high sensitivity to stick position, I don't get the full range of motion in certain directions. This is almost certainly a factory calibration problem... on a PC I could just calibrate the device directly or find a workaround, but I don't know enough about android accessories/devices. Short of ripping it open and futzing with what I assume are hall sensors, is there a way to initiate some sort of device re-calibration, or change the values for 0 to max in Android?
I've sent a similar question to Lenovomoto, but I'm not hopeful.
Edit: I'm too green to upload images here, but gamepad tester output shows a 'flat tire' response from 11-oclock to 1 oclock.
Click to expand...
Click to collapse
It sounds like a DOA gamepad. Out of the box mine hasn't had to be calibrated and has a natural controller feel. The only thing I notices is the D-Pad required firm pressure at times.
my gamepad doesn't seem to have any of those type issues:
https://youtu.be/8zndTsQgKf0
have you checked for a software update?
No updates yet, though I do suspect it could be corrected in software, so here's hoping. In the meantime, it looks like in-game sensitivity adjustments provide a suitable workaround for most games and emulators. (just boost the sensitivity to the point where all directions register) I'll just have to wait patiently - despite providing raw output data, Moto customer service doesn't regard this as a defect.
I have had the same issue with my original gamepad mod and the replacement. I've deducted mine to trigger slop. No teardowns I've found yet. And I called Lenovo about it and they said no calibration tools available. Make sure your forward directions are not sloppy. On both analogs I get .8 travel out of 1 in all forward directions on both sticks. Trying to figure out how to fix lenovos poor design and crappy plastic parts myself. Glhf.
I Solved this problem on my gamepad
My way is a bit tryhard, but... I found this teardown from a guy who was replacing the membrane from the D-Pad, I can't post links cause I'm a new user, but if you search for "moto gamepad disassembly" in google, click the third link that says "Moto GamePad Mod - better buttons! : Moto_Z - Reddit" and then go to the link at the bottom of the thread (thanks very much to that hero).
So... following those steps I removed the stick and used sandpaper to expand the radius of the circle that limits the movement of the stick. When you are getting close to the grey ring, you are done. At that point the stick can reach from -1 to 1 values on every direction you point it.
If you want to do it, I have a couple of tips... In the second step of the teardown you have to use a bit of strength to separate the shell on the top and bottom corners that point to the center of the gamepad. And I recommend to use a hard sandpaper at the start and when you are close to the grey ring use a soft one.
Sorry if I don't write very well, I don't speak much english.
Related
Now i love my desire... Its fantastic but it isnt without some issues...
One ive noticed that could be a problem esp when your working with reality overlay apps...
The compass doesn’t seem to work that well...
Its slow to respond to movement and even when it does move its horridly inaccurate. north seems to have a room for error of 60-90 degrees.
Has anyone else noticed this? Is it the same for most digital compasses? or do i have a faulty module?
Hi Nutsy,
I've also noticed these issues with the compass in the Desire. I've worked with magnetic compass chips before and I think it's all to blame on the way these compasses work:
To sense the earth's magnetic field they use a two- or three axis magnetometer. Although it's a very accurate way to sense the earth's weak magnetic field, it's also very sensitive to any other magnetic field. That means that the presence of ferromagnetic materials (like iron) or electrical currents in the vicinity might really screw up your compass reading.
So electrical wires, iron piping, laundry machines (almost anything that you would find indoors that runs on electricity or contains iron), will interfere with your compass.
a good alternative would be to use a gyroscopic compass like they do on submarines, but I don't think these fairly expensive devices aren't used in mobile equipment yet. So the only thing to do is to stay away from anything that might interfere.
The slow response to movement might be caused by internal filtering. These analog sensors produce quite an amount of measurement noise. In order to cancel this, they probably use some sort of filtering algorithm like this one:
step 1 -> Take a new sensor reading.
step 2 -> Add it to a buffer that contains the last 25 readings.
step 3 -> Calculate the mean value of all measurements in this buffer. This will be the compass heading that is sent to Android OS or your application.
step 4 -> Repeat this cycle every 25 milliseconds.
Hope this answers your questions. Of course if you compass readings never make any sense under any circumstances, the thing might just be broken...
Friendly regards,
Joost
Ps.
There's an App in the market called "Metal detector" that actually uses the interference "problem" with the compass to detect ferromagnetic metals.
Wow Thanks for the really detailed reply...
Im glad its not just me then... Didnt really want to RMA it over a dodgy compass unit.
And thanks for letting me know about that app... sounds usful... I guess it could be used to detect wireing in plaster as well?
You're welcome.
In theory you could use it to detect metal or wires in a plaster wall. I've just tried it, and it works quite well. On the other hand, I really don't want to risk electrocution by trusting a telephone to find electrical wires...
My compass is shocking. Actually points closer to South whenever I open Compass or a programme which uses the compass like G-sky. I have to calibrate it every single time.
Thing that annoys me, is if I calibrate, then exit the programme and immediately re-open the programme, it doesn't remember the calibration, it reverts to pointing in a ridiculous direction.
I want to hit it with my fist.
Addtitionally, think it's broken?
jimmymagix said:
My compass is shocking. Actually points closer to South whenever I open Compass or a programme which uses the compass like G-sky. I have to calibrate it every single time.
Thing that annoys me, is if I calibrate, then exit the programme and immediately re-open the programme, it doesn't remember the calibration, it reverts to pointing in a ridiculous direction.
I want to hit it with my fist.
Addtitionally, think it's broken?
Click to expand...
Click to collapse
Yesterday I found out the same thing... Sometimes I cant even get it working after calibration. I was beginning to think that this happened because I dropped it once pretty hard. What should we do next? Can this be solved by replacement with warranty or something?
Smauglys said:
Yesterday I found out the same thing... Sometimes I cant even get it working after calibration. I was beginning to think that this happened because I dropped it once pretty hard. What should we do next? Can this be solved by replacement with warranty or something?
Click to expand...
Click to collapse
Make sure your phone isn't in a case which uses magnets to keep it closed, as they affect the compass. If you're affected, take your phone out of the case and try again. Also, try out in the open, away from structures which may contain a lot of ferrous metal.
In my case the problem is due to powered-on wi-fi module. Turning off wifi, compass works fine. Could Anyone elserepeat my experience?
poldie said:
Make sure your phone isn't in a case which uses magnets to keep it closed, as they affect the compass. If you're affected, take your phone out of the case and try again. Also, try out in the open, away from structures which may contain a lot of ferrous metal.
Click to expand...
Click to collapse
Yes I know that. Tried out doors, and wheres no metal... When I had the G1, the compass worked normally.
In my case the problem is due to powered-on wi-fi module. Turning off wifi, compass works fine. Could Anyone elserepeat my experience?
Click to expand...
Click to collapse
Just tried what you said. It did not help for me. I turned it of completely.
Smauglys said:
Yes I know that. Tried out doors, and wheres no metal... When I had the G1, the compass worked normally.
Just tried what you said. It did not help for me. I turned it of completely.
Click to expand...
Click to collapse
Just went outside to test it again. And I think I found how to get it working. If i launch the compass application, and try to turn the phone in the flat position (on its back), then the arrow moves in random directions. But if i lift the phone that it is facing straight to my face, and then turn left and right a few times, like a steering wheel, the compass "calibrates" as I can see. And then when I lay it down again flat, it starts to work normally. Can anyone try this, if you understood my instructions?
A more accurate way of calibrating the compass is by rotating the phone twice around each axis, ideally you should do this away from anything metallic or any interfering magnetic fields preferably outside.
Er......
Where is the compass?
I dont seem to have a compass! In my list of apps there just isnt one called compass...
The Analogue Compass app is very buggy for me so I use the Compass app -> http://www.androlib.com/android.application.com-apksoftware-compass-qAC.aspx
When taking readings, I;
Always have to recalibrate on startup as far too many objects cause large interferences within the sensor making it go astray, even the charging cable causes it to go berzerk. The known working routine is to calibrate by fast twisting and turning the phone [I do it after running the built-in figure 8 calibration routine]
Keep it mid-upper body height with no metals nearby (jewellery/belt/metallic objects minimum >5ft away), holding still and level across the x-axis
Point the upper-end of the phone in the direction I want the bearing of (this depends on the type you use though, I use the digital type)
I spin the phone around and then retake 2 more readings for a total of 3 readings - averaging them out for a final mean reading
I only have 2 directions calibrated through professional consultation when this room extension was built a few years back and know the rough directions all sides this property faces, but in particular, I'm 100% sure of the exact degree reading one wall faces. This app using the built-in compass sensor reads that bearing spot on everytime after calibration (fluctuation is 1-2 degree max).
Some friends in a Lithuanian Android forum, suggested to do this, like it is shown in the video. Works perfectly every time. And I thought that something was wrong, because I never had to do anything like this on my G1.
Youtube video ID, because I cant add link because of spam protection http://www.youtube.com/watch?v=sP3d00Hr14o
I was playing with my GF's Nook the other day and thinking about what a nice size it is for e-Reading. Now, I realize it has a higher screen resolution that WP7 doesn't support, so I wasn't thinking of going that far.
But I did get to thinking: is there a 7", 800x480 capacitive screen on the market that could be made to simply "plug in" via the same type of connector as the focus uses, and just work? In that case it wouldn't be *too* difficult to transplant the rest of the focus' guts into a bigger chassis (maybe adding a bigger battery since the extra space would be there anyway). Anybody thought about this or have some idea what one would look for?
Thanks!
So I'm guessing nobody has any idea or interest in exploring said idea?
The chances of that working are pretty darn slim. I'm not really into the hardwaret thingy, but I'm pretty sure you would need to know what interface to the display is used on both devices. They need to be the same, or you'll need to find a way to convert the signals, which means a lot of work and room for error I guess.
I would say it's possible, if you find a device with the right resolution and display interface/controller.
The display itself should work, since a display is just a display... It only receives data what to display. But dunno if the touchscreen would work out of the box, maybe different systems use different protocols in sending/receiving/processing data from the touch panel... But then again, I don't have my diploma yet
The displays must have the same controller. Or using the controller from the Focus - but don't forget, that it is AMOLED, so it might work totally different.
I don't think it is possible without too much effort. You should get some x86 tablet and run WP7 emulator on it . Or make an app for the W7 that looks like WP7.
Basically you would need to have two drivers, or make the other side compatible with existing drivers.
The screen and the touch panel.
I don't know what type of touch panel you have, but WP7 uses capacitive screens, this is a big requirement because you won't work around it easily.
The way the positioning data is transfered matters allot, because this can kill the accuracy at the least.
Next, the screen needs to know how to display the data received from your device, I assume the connector won't fit out of the box so thats the first challenge. Then you need to make sure it's receiving the correct data over the correct lines. It is not the same as plugging in a D-SUB/DVI cable.
So, if you have knowledge of some hardware modifications (electro) then you will stand a chance, otherwise you'll probably end up wasting two devices.
If you can spare both, I would say go for it. Otherwise I would think twice if I were you.
Yeah, I'm way too lazy (well, too busy with school) for all that . I was just randomly thinking about it the other day, how nice it'd be to have WP7 on a decent sized screen for an ereader, given that the Kindle app works great on the device. I guess I was hoping that there might exist, essentially, an "embiggened" version of the exact same screen, with the same connector, to simply be driven off the Focus' existing controller and hardware. Capacitive, obviously--WP7 on Resistive would lick all kinds of donkey balls, I'm sure.
Hello xda! , i have just bought i nexus 7 (2013) last wednesday and today i have noticed that there is a certain area of the screen where if i swipe my finger from another location it terminates the touch and starts another one, i enabled developer options and turned on the pointer location to see what was happening and it shows the line when im close to the "spot" but when i strike through it it starts another line after that "spot" but if i tap its okay i discovered this while playing draw something and when i go through that location it just start a new brush line or whatever and its a little annoying, the thing is that i bought it at RadioShack but didn't add the warranty but still have the 31 day warranty.
Hope you understand what im saying
1. Is this a reason to replace my tablet?
2. Will they replace it or what?
1. Yes
2. No reason why not, you're within a week.
(if you used a CC you've got even more leverage)
Now that you know what to look for you can test before you even leave with it. :thumbup:
Yeah I Think i'll keep it for a few days (15 or 20) if google launches a patch i'll keep it if not i'll try to replace if the same issue is present on the replacement i'll ask my money back
Sent from my Nexus 7
I don't think that a dead spot that's repeatable is software, but, what the heck. They're pushing out an update right now that's supposed to fix the touch issue, so you'll know soon enough...
Hello Guys, i just updated my tablet to JSS15Q and the multitouch issue has been corrected but my problem with the vertical dead spot i mentioned is still there today i'll back up everything that i can and tomorrow will take it to RadioShack for replacement. Thanks
Sent from my Nexus 7
danvee said:
I don't think that a dead spot that's repeatable is software, but, what the heck. They're pushing out an update right now that's supposed to fix the touch issue, so you'll know soon enough...
Click to expand...
Click to collapse
It usually isn't a true dead spot in the sense that there is no voltage drop or current going through that area. It is usually that for that area they need to use a different threshold to trigger detection. I saw in the firmware changes they can fine tune even edge responses, so I assume they can have some sort of matrix where the thresholds are specified for different parts of the screen. The problem might arise that if they make some area more sensitive, displays that are already more sensitive in that area might start having undesirable behavior.
I have seen areas where the screen won't register taps but will register swipes. I've also seen areas that won't register taps or swipes, but when you hold the unit it starts to register them, so clearly the wiring is there for the input to be registered, but the thresholds to determine noise vs input may need to be tuned.
It does seem there is a lot of variance on these touchscreens which appears to be making it hard for them to come up with one firmware that fixes everything.
They may need to add some user tunable functionality to account for the different variances.
Is that even possible?
Interesting, but it's not a constant in my case.
The upper ⅓ in portrait becomes decreasingly sensitive toward the top, but only periodically. Maybe 2-3X/day.
Can't reproduce it at will, or by introducing any series of events (at least consciously).
It just happens.....
The occasional freezing happens, maybe once/day, and again, not reproduce able at will.
One plus is that any spontaneous rebooting has been while it's 'sleeping', hasn't done it during use.
My question is based on that, the back of our Moto Z Play will be adapted certain mod, s including this extra battery and a version of this, it has been adapted to turn wireless charging, so he proposed me that together we get on very, very little money.
With that premise, the first thing we have to be aware that every touch point is that back.
I have numbered the contacts so that each is its function without possible error, I have not yet started to take electrical measurements of each and every one of them even the bar for me has all the earmarks of being earth ( -).
I guess somewhere you could see that information even officially and keeping that already fixed, the rest would take a wireless receiver of those in Ebay or Amazon, etc etc tec. and with them even performance testing and that, considering the original back cover cover the whole shebang given thickness having the receiving plates is about 1 millimeter or 1 with a tenth desmereciera I do not think the whole.
That is, to work and I hope that with this idea, collaborate to launch even more this thread.
Deputy graphic including numbering.
Conflicting reports in regards to NFC on the higher-end Deluxe models. GSM Arena reports it's available, PDAdb, which i believe is more reliable doesn't even mention 'NFC'.
I believe this VERY common feature has been 'avoided' in this phone, absolutely foolish by ASUS as it's keeping me away from this phone. Can someone please confirm? Anyone know why this decision was made despite the fact they have the 5.5", 5.7" deluxe variants and the ULTRA, which isn't much better?
Thanks
RoOSTA
It is available BUT it is in the very top of the phone.
Most phones use the battery and have NFC centered around the middle of the back. The ASUS Zenfone 3 deluxe, and the ZTE Axon 7, have it at the top of the phone, around where the speaker is located.
I don't know WHY it was put there but I eventually found it with a bit of hair pulling...
Somethings need to be the top part of the back but you can also use the very top of the phone too. A little annoying as this isn't very well explained...
NFC sensor is on the front near the top of the screen.
Yes, it have NFC, in te top of the phone near the call's speaker
I used it all days with some nfc tags.
An awkward location to put the NFC. You cannot see the screen when it is contacting the other device.
ultramag69 said:
It is available BUT it is in the very top of the phone.
Most phones use the battery and have NFC centered around the middle of the back. The ASUS Zenfone 3 deluxe, and the ZTE Axon 7, have it at the top of the phone, around where the speaker is located.
I don't know WHY it was put there but I eventually found it with a bit of hair pulling...
Somethings need to be the top part of the back but you can also use the very top of the phone too. A little annoying as this isn't very well explained...
Click to expand...
Click to collapse
@wshek @jonasiesta
Thanks guys. Can you show me a quick NFC tag scan in a short video please?
roosta said:
@[email protected]
Thanks guys. Can you show me a quick NFC tag scan in a short video please?
Click to expand...
Click to collapse
Hey, so I sometimes get the NFC to work (unlike my zenfone 2) bit when I tap to send / beam a picture it goes to Google play and tries to install the gallery app. Anyone know how to send the picture instead?
jmoricone said:
Hey, so I sometimes get the NFC to work (unlike my zenfone 2) bit when I tap to send / beam a picture it goes to Google play and tries to install the gallery app. Anyone know how to send the picture instead?
Click to expand...
Click to collapse
You "sometimes get it to work" ? Pretty crap phone if it doesn't work as intended...
roosta said:
You "sometimes get it to work" ? Pretty crap phone if it doesn't work as intended...
Click to expand...
Click to collapse
Senior member of High School
I get NCF to work.. Did not realize the chip was in a different location than model 2. Model 2 is rooted and can send pics via beam with no problem. Version 3 when I try to beam tries to install the app. Don't need wise ass comments. Joined XDA for "real" advice. If I need bull**** comments, remarks, etc I would have just posted on ****ty websites. Real question for real answers. If you have nothing else to do shut the **** up
The NFC is located at the top of the phone. You could "image" it's using the 3.5mm jack as the center of antenna. (Although it's actually there..)
I use the NFC function almost daily for payment (for convenience store purchase as well as subway ride) and it works 100% of time. (never second time touch) The way I use it is screen facing me, only the very top of phone (basically where the 3.5mm jack is located) is touching the payment terminal reception pad.
Most of the payment terminal will even accept the phone lying flat, LCD up as long as the 3.5mm jack is located near center of the payment terminal's reception pad.
The reason why NFC is located at top of phone is that the back of this phone is made by one piece of metal. NFC signal will have trouble pass this metal barrier. Beside, I found it's easier to use as NFC is at top since can hold the phone 45 degrees (LCD facing me) instead stick the back of the phone flat to the payment terminal when making payment.
Also, the screen is not needed to be on when making payment (YMMV, may depend on APP). The sensitivity of NFC is even better then my cashless credit card. (I tested both at same terminal).
lssong99 said:
The NFC is located at the top of the phone. You could "image" it's using the 3.5mm jack as the center of antenna. (Although it's actually there..)
I use the NFC function almost daily for payment (for convenience store purchase as well as subway ride) and it works 100% of time. (never second time touch) The way I use it is screen facing me, only the very top of phone (basically where the 3.5mm jack is located) is touching the payment terminal reception pad.
Most of the payment terminal will even accept the phone lying flat, LCD up as long as the 3.5mm jack is located near center of the payment terminal's reception pad.
The reason why NFC is located at top of phone is that the back of this phone is made by one piece of metal. NFC signal will have trouble pass this metal barrier. Beside, I found it's easier to use as NFC is at top since can hold the phone 45 degrees (LCD facing me) instead stick the back of the phone flat to the payment terminal when making payment.
Also, the screen is not needed to be on when making payment (YMMV, may depend on APP). The sensitivity of NFC is even better then my cashless credit card. (I tested both at same terminal).
Click to expand...
Click to collapse
Thanks for the info. One of the downsides of the body design I guess... Good to see its working for you and there's a way around it. I would've gone for this phone had root been available on it by now. Lack of IR is something I don't use all the time, but still find it important and am using on my V20...
RoOSTA