Hi there gents.
I just bought a new razr d1 xt918.
And im having issues with the navigation apps while driving a car, such as google maps navigation, and waze app.
I've already did that tutorial using the phone tester to unlock the X axis for the compass. But mine 3 axis were moving okay already.
The issue that im having is that when im using such apps to navigate with the car moving around the gps system seems to take too long to lock or respond, or finnaly "load", so i've already moved from a position and the gps app screen is still far behind where i was before.
In a way that the navigation apps with routes and maps can only be used as a google maps for consulting a frame of a map. But you cannot use it for real time driving. im not having a real time movement in any car navigation app, because the gps does not respond soon enough.
With the phone tester app, i can go @Sensor status and there i see three boxes showing: Accelerometer / Proximity Sensor / Light Sensor.
All three boxes seems to be responding okay.
But when I hit the ! (exclamation point) on the top right of the screen i get this message:
Your phone doesn't have :
Compass
Magnetic field sensor
Temperature sensor
Gyroscope
Pressure Sensor
Humidity Sensor
Okay. i think i don't need things like humidity sensor.
But the other sensors like magnetic field, gyroscope, compass and the rest. Isn't those sensors needed to have a good enough hardware to perform a real time gps navigation inside an app ?
Are these RAZR's phone model missing some hardwares devices in the gps system?
Or is it the Jelly Bean 4.1.2 bugged in a way that cannot have these sensors working correclty.
Searching for answers i've already find a lot of complains about the gps issue, or compass issue wich in my case the axis were working fine.
But there are a lot of complains about it. Even because in the Gingerbread builds, older one, the navigations app could work pretty good.
Why the new phones cannot ?
And another this is that there are a lot of people complaing and sharing tutorials. but no official axplanation about it. not at all. Or from google, or motorola, or verizon, or nothing.
I saw that another guy have recieved a messahe from the support telling that his phone does not have the compass devices and point. stop trying to use it. haha.
I think that the support guys were oriented to tell the customer that he does not have a compass and force him to give up the problem.
Please. How i do to have a real time navigation with this phone ?
razr d1 XT918
Andorid version 4.1.2
Flex
XT918_retail_brazil_20130227-[2_330_395_1346]
Band base
MAUI.11AMD.w12.22.SP.V21.F3.P.2013/09/2012 10:15
Kernel version
3.4.0
#1 PREEMPT thu oct 3 17:55:15 CST 2013
Version number
2_330_2009
thanks.
Related
Hi there!
First time I need to make a topic, as I don't find the answer anywhere..
Had my Touchpad since about two weeks.
However the accelerometer has not functioned at all since I got it.
First thing to check is the auto rotation lock -> it's turned off
Second thing I did was download a sensor visualizer app -> Seismograph.. This shows very weird results for the x-axis (see attached file), fyi, the Y and Z-axis functioned as expected..
Then the third thing I tried, Need For Speed Hot Persuit... A game that uses the X-axis accelerometer (right!?)
This works brilliant!
Other things I have done to troubleshoot this:
Restart the device.
Full reset the device.
Run HP doctor.
All have failed in resolving my problem.
As I've bought the touchpad from a french webstore (fnac.com), HP Netherlands (where I'm from) tells me I need to get back to them for a solution, as they don't offer worldwide repair (unlike ASUS for example).
Fnac.com has not answered to my request to exchange the product (2 days after I got it). And actually I just want to solve it myself if possible, bought it for fun anyways (and reading of course xD)
Any ideas how I can make the OS recognize the accelerometer?
Last thing, the auto rotation functions in the following way: Tablet is stuck in landscape, I turn to portrait, screen turns as well, but within the second the tablet is back in landscape. This behavior can be read from the seismograph screenshot.
Thanks!
Hello
I just started a new thread for a different accelerometer problem (it is just dead)
http://forum.xda-developers.com/showthread.php?t=1284760
Was wondering how you ended up fixing your problem.
thanks
Just wanted to ask you the same question...
I still have the same problem. Need to contact Fnac.fr, but my french sucks and my time is scarce. So have been postponing this. My unit actually came DOA.. however Fnac didn't respond to my request, and has now asked me to call them.. sucky service
You have no solution I guess?
Well this is odd..
Out of nothing the auto rotate function is working since today.. I noticed it while reading a PDF in Android. Booting back to WebOS didn't make a difference, the sensor is working again
I've got no clue what did the trick.. I have not updated the kernel or something like that lately.
I wonder if the sensor was kicked back into action by brute force (for instance my cat jumping on the tablet..)
Anyway, problem soved for now =D
Hey Mongoose,
First of all, great job with the ROM. Installed both Alpha 2 and 3 and you are making fantastic progress!
Thanks also to all of the Eris DEVs (and all DEVs for that matter) out there, my first little Android has held its own for a few years now
A quick comment:
The keyboard consistently opens ALMOST all the way up. For me, it's been stopping in the middle of the last row - still able to use - but not fully visible.
I was in the Messaging app and I did something that made it jump up to fully visible, but now (of course) I can't replicate what I did.
Thanks again, looking forward to future iterations!!
Wanted to comment on what I've tested and is WORKING for me:
touchscreen (not having any of the reported issues)
physical & soft buttons
data
calls (sending and receiving, no mic)
earpiece audio
sms (sending and receiving)
vibration / haptic feedback
proximity sensor
google sync
root access
NOT WORKING:
microphone
speaker audio
wifi (scans fine, can enter text to connect, says it's connecting, then authenticates, then loops on connecting/authenticating)
gps
camera
bluetooth
trackball
light sensor
orientation sensor
accelerometer (downloaded an app that has opengl 3D using the accelerometer and it rebooted the phone when I tried to view the 3D model)
magnetic field sensor
sdcard
mms (when I choose attach a picture it says "No external storage available.")
Also, installation was a piece of cake!
Wiped data and dalvik and then let it boot. Obviously no boot animation, but first the screen illuminated, then the soft buttons lit, then the haptic feedback shook, and then I was at the Start screen.
Again, fantastic job!!
Hello all,
Just to clarify (since some people in the Dev forums are still having issues that I have not had with Alpha 3) my Eris model number is PB00100.
I believe this is the 2nd model number of Eris from Verizon (not 100% sure about this)? I did have my original Eris replaced after I was losing calls like crazy.
Hope this helps!
Thanks for the detailed feedback! With another post you'll be allowed to post in the section. Look forward to seeing you over there
No problem! Last night I was following the dev thread in the Hero forum talking about the audio issues. Looks like jaybob413, Shelnutt2, shed, you, and a couple others are very close to working that issue out.
Once this build has a working mic, I will be using it more extensively.
I have a really strange problem with the touchscreen. When i touch it with one finger and hold my finger in the same location without moving it on the screen for 20-50sec, my touch is not recognized anymore at this location. Around this location my touch is "seen" by the screen, but not at the specific location. After a few seconds trying to touch the screen at the dead location, it "repairs" itself and everything works fine again.
That is a real problem when you want to play a game like reckless racing 2. There you need to hold the finger at the accelerate-button the whole time and after a few seconds it doesnt work anymore. Has someone experienced the same issue? The best way testing it is with a multitouch tester app .
I would be very thankful if someone could test it. Maybe i have a faulty device.
Im using a german razr with the latest android 2.3.6 firmware.
You can see a video of the problem here at vimeo.com/37909738
Something like this? http://forum.xda-developers.com/showthread.php?t=1467696
Thanks for the link. This really looks like the problem i have. This seems to be a feature? A feature which makes playing some games on the razr almost impossible .
I have this issue with my S3, that is infuriating! Whenever I get a call and answer it, my screen turns off after a short while and during the call I can't turn it back on. The power and home buttons do nothing, and the proximity sensor isn't working either, so I can't turn off a call.
Anyone know how I can fix this? I have Lollipop, CyanogenMod 12.1 custom ROM installed.
Thank you for your time.
This bug partially exists in stock roms too. It's just magnified in custom roms.
You should be able to set it to keep the screen on during calls. It's the only way i know of.
I fixed this problem by opening up the phone, unplugging the proximity sensor, and throwing it in the bin. (the trash to you Americans)
Screen stays on during calls now, but I've not had problems with accidentally ending calls with my face, so I'm happy.
You also lose your front camera because it's part of the same tiny PCB. But I've never used the front camera on a phone in my life. So my solution is perfect for me, but maybe not for you.
The other option is a software fix. There's an app, or a method that you can do yourself to disable the proximity sensor, but I had problems with it, so did it my way.
Edit: I forgot to mention that the reason my proximity sensor wasn't working was because whoever had this phone before me did a screen repair and had half severed the ribbon cable for the proximity sensor by accident. Not just because of the bug that sometimes exists.
Sent from my GT-I9300 using Tapatalk
Proximity sensor problem. Manually calibrating it solved the issue for me.
http://forum.xda-developers.com/showthread.php?t=2569141
Go to that thread and follow instructions. The code for sensors might be different for s3, Google it.
sashankps said:
Proximity sensor problem. Manually calibrating it solved the issue for me.
http://forum.xda-developers.com/showthread.php?t=2569141
Go to that thread and follow instructions. The code for sensors might be different for s3, Google it.
Click to expand...
Click to collapse
Bah, that's the boring way to fix it.
(didn't work for me. maybe work for OP though)
Sent from my GT-I9300 using Tapatalk
I remember that I saw a MOD or xposed module to keep screen on during call.
It's better than throwing the sensor to the bin (trash ) .
hi,
the compass on my phone seems to have issues.
i have calibrated many times, in general, the compass seems to work fine. but it oscillates fast within about 3°
apps like peakfinder or peaklens are almost useless when the camera is enabled. the peak names are jumping left and right like mad.
is this a known issue on that phone type or is it just mine?
thanks for answering.