Can someone explain why the compass of EVERY android phone I have ever owned has sucked? From a cheap HTC Aria to an uber-expensive S23U? Specifically, the compass seems to require re-calibration very frequently. For example, if you ask for walking directions in gmaps on an iPhone, the blue cone indicating the direction of motion is always correct and pointing in the appropriate direction. On every android phone I have owned it is frequently grossly off without calibration, sometimes by as much as 180 degrees. This affects the usability of the phone in augmented reality apps, whether it is hiking, figuring out where the sun is going to rise or set, where the milky way is going to be, etc. And even after the compass is calibrated it tends to drift for a few minutes after calibration, and cannot be trusted for critical use, for example "is the sun going to set between these two spires over there".
There may be regional magnetic anomalies.
blackhawk said:
There may be regional magnetic anomalies.
Click to expand...
Click to collapse
Why has my wife's iphone never suffered then?
GroovyGeek said:
Why has my wife's iphone never suffered then?
Click to expand...
Click to collapse
You probably shouldn't have swallowed those magnetic balls as a kid?
Borrow your wife's iPhone?
GroovyGeek said:
Why has my wife's iphone never suffered then?
Click to expand...
Click to collapse
Because different phones different problems? Report it on samsung members app with some proof
blackhawk said:
You probably shouldn't have swallowed those magnetic balls as a kid?
Borrow your wife's iPhone?
Click to expand...
Click to collapse
That could have been somewhat funny if it even peripherally addressed the question.
blackhawk said:
There may be regional magnetic anomalies.
Click to expand...
Click to collapse
OMG, do you mean Tycho Magnetic Anomaly 1?
My experience also. Have owned almost every iPhone model and the compass has always been flawless. Recently spent a week in Gran Canaria and used Google Maps on my S23 ultra for hours everyday. The compass was almost way off all the time. Calibration could help a minute and the it was off again.
The wife's and kids iPhones of course worked perfectly. I had to swallow my pride and ask them for direction a lot of times Love the phone but the compass is really a disaster most of the times
GroovyGeek said:
That could have been somewhat funny if it even peripherally addressed the question.
Click to expand...
Click to collapse
Couldn't resist
Using the phone is poor plan anyway if your navigation depends on it in remote areas.
Get a military compass; KISS.
blackhawk said:
Couldn't resist
Using the phone is poor plan anyway if your navigation depends on it in remote areas.
Get a military compass; KISS.
Click to expand...
Click to collapse
Fair. But what about walking in the city? Surely I should not have to carry a military compass in order to decide which way gmaps directions are sending me.
GroovyGeek said:
Fair. But what about walking in the city? Surely I should not have to carry a military compass in order to decide which way gmaps directions are sending me.
Click to expand...
Click to collapse
You can gauge NS/EW direction by streets, landmarks or the rising/setting sun. After a time it becomes second nature. Use anything at hand that works including distant sounds.
Or simply use gps plus maps. I navigated for decades using only maps and cross highways, roads, streets etc to determine my location and direction. Didn't use a compass; formed a rough idea of north using the map and/or visual clues. Today it's so simple to do many don't have basic map or navigation skills anymore. Getting lost means you get by the seat of your pants navigational training... try that in Boston
easycure197401 said:
My experience also. Have owned almost every iPhone model and the compass has always been flawless. Recently spent a week in Gran Canaria and used Google Maps on my S23 ultra for hours everyday. The compass was almost way off all the time. Calibration could help a minute and the it was off again.
The wife's and kids iPhones of course worked perfectly. I had to swallow my pride and ask them for direction a lot of times Love the phone but the compass is really a disaster most of the times
Click to expand...
Click to collapse
I am guessin it's not the S23U's fault since ALL Android phones do it. Suggests that the screwup is at the OS level
GroovyGeek said:
I am guessin it's not the S23U's fault since ALL Android phones do it. Suggests that the screwup is at the OS level
Click to expand...
Click to collapse
The compass works smooth and true on my N10+ except in the present of magnetic anomalies. Maybe iPhone is using GPS
GroovyGeek said:
Can someone explain why the compass of EVERY android phone I have ever owned has sucked? From a cheap HTC Aria to an uber-expensive S23U? Specifically, the compass seems to require re-calibration very frequently. For example, if you ask for walking directions in gmaps on an iPhone, the blue cone indicating the direction of motion is always correct and pointing in the appropriate direction. On every android phone I have owned it is frequently grossly off without calibration, sometimes by as much as 180 degrees. This affects the usability of the phone in augmented reality apps, whether it is hiking, figuring out where the sun is going to rise or set, where the milky way is going to be, etc. And even after the compass is calibrated it tends to drift for a few minutes after calibration, and cannot be trusted for critical use, for example "is the sun going to set between these two spires over there".
Click to expand...
Click to collapse
iPhones use a different sensor and calibration method that does not require the user to draw a figure-eight. Instead, the iPhone's calibration process is automatic and continuously adjusts the sensor's readings based on the phone's movement and orientation. Don't ask me why, in 2023, Samsung's flagship still requires drawing a figure-eight to recalibrate its sensor almost every single time, while my iPhone does it automatically. It's just ridiculous.
Wad12355 said:
iPhones use a different sensor and calibration method that does not require the user to draw a figure-eight. Instead, the iPhone's calibration process is automatic and continuously adjusts the sensor's readings based on the phone's movement and orientation. Don't ask me why, in 2023, Samsung's flagship still requires drawing a figure-eight to recalibrate its sensor almost every single time, while my iPhone does it automatically. It's just ridiculous.
Click to expand...
Click to collapse
That's not the magnetic compass. I normally don't need to calibrate that but I only have one game that uses those sensors (might be the orientation sensor, there are several). My Samsung is very well behaved and predictable... likely a 3rd party app that's mucking yours up.
DevChek is handy for seeing and checking sensors.
blackhawk said:
That's not the magnetic compass. I normally don't need to calibrate that but I only have one game that uses those sensors (might be the orientation sensor, there are several). My Samsung is very well behaved and predictable... likely a 3rd party app that's mucking yours up.
DevChek is handy for seeing and checking sensors.
Click to expand...
Click to collapse
Certainly not my experience. I have seen the compass on Android off by as much as 180 degrees, and without calibration is almost.alaays off by around 45 degrees. Calibrating it makes it true... till next. Time you shut off the screen after which the figure 8 song and dance needs to be repeated.
GroovyGeek said:
Certainly not my experience. I have seen the compass on Android off by as much as 180 degrees, and without calibration is almost.alaays off by around 45 degrees. Calibrating it makes it true... till next. Time you shut off the screen after which the figure 8 song and dance needs to be repeated.
Click to expand...
Click to collapse
Don't see that but I rarely use it. Not sure what the calibration suppose to do unless there's nearby ferrous metal.
I have to add... in a city with lots of tall metal buildings, I often have trouble getting the figure 8 to do anything anyway.
cjkimmel said:
I have to add... in a city with lots of tall metal buildings, I often have trouble getting the figure 8 to do anything anyway.
Click to expand...
Click to collapse
Yeah if bracketed by dense ferrous metal it will screw it up. It's pointless to calibrate in that case.
I can get pretty near to heavy trucks, in a large metal building and it's still fairly accurate.
However if I put in between two upright thick 8 inch C channels about 2 feet apart it goes way off by 45°.
Related
Long story short, new company doesn't allow cameras in their facilities and I'm having serious Thunderbolt withdrawals.
I was wondering if anybody had ever removed the cameras from their Thunderbolt and the phone still worked after the "surgery."
If you did, is there a specific procedure you would follow? I found this online: http://www.techrepublic.com/photos/...=47&tag=siu-container;photopaging#photopaging
But that guy is actually just tearing the phone apart. Is there a way to get to just the cameras without pulling the whole phone apart?
Sent from my ADR6400L using XDA Premium App
Go take a look at the FCC approval photos Adrynalyn posted... Not only will you be taking the phone apart, you'll be taking it apart to the BONE. I'm also pretty confident you'd destroy the phone in the process.
Curious... why would you even tell someone you've got the thing or show that it's got cameras on it, knowing the policy?
Jmc: I guarantee you're absolutely incorrect. There are many people who work in high security companies. There has to be at least one person who has done this.
loonatik78 said:
Go take a look at the FCC approval photos Adrynalyn posted... Not only will you be taking the phone apart, you'll be taking it apart to the BONE. I'm also pretty confident you'd destroy the phone in the process.
Curious... why would you even tell someone you've got the thing or show that it's got cameras on it, knowing the policy?
Click to expand...
Click to collapse
Why do you think I would destroy the phone?
As for your other question, sometimes security will sweep the entire building/staff, just in case. In those instances, if you're caught with a cameraphone, you're getting fired.
Sent from my ADR6400L using XDA App
infinite012 said:
Why do you think I would destroy the phone?
As for your other question, sometimes security will sweep the entire building/staff, just in case. In those instances, if you're caught with a cameraphone, you're getting fired.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
I think you'd destroy the phone because that camera isn't just a simple surface mount device like the power or volume micro-switches. It's an entire 8MP camera in a VERY tiny box. To kinda give you an idea how those things are mass produced, a solder paste is applied sort of like one might silk screen a shirt. Then the individual components are placed in their correct locations. Finally, the entire thing is baked in an oven to melt the soldier paste and adhere the components. If you want to see what I'm talking about, go to Qualcomm's website and look at the physical interface for the Snapdragon chip. Assuming the cameras is mounted in a remotely similar way, you're going to destroy the device removing them. Additionally, the FFC also functions as both a brightness and proximity sensor. Removing it would have consequences that would be difficult to predict.
infinite012 said:
Long story short, new company doesn't allow cameras in their facilities and I'm having serious Thunderbolt withdrawals.
I was wondering if anybody had ever removed the cameras from their Thunderbolt and the phone still worked after the "surgery."
If you did, is there a specific procedure you would follow? I found this online: http://www.techrepublic.com/photos/...=47&tag=siu-container;photopaging#photopaging
But that guy is actually just tearing the phone apart. Is there a way to get to just the cameras without pulling the whole phone apart?
Click to expand...
Click to collapse
Would filling over it with some sort of hard/opaque/sticky/permanent adhesive substance suffice? Something like putting epoxy or something over the lens so it renders it no longer useful.
yareally said:
Would filling over it with some sort of hard/opaque/sticky/permanent adhesive substance suffice? Something like putting epoxy or something over the lens so it renders it no longer useful.
Click to expand...
Click to collapse
That might work for the rear camera, but the FFC needs to function correctly to control screen brightness and proximity.
loonatik78 said:
That might work for the rear camera, but the FFC needs to function correctly to control screen brightness and proximity.
Click to expand...
Click to collapse
I dont know about that. Very few android phones have a front facing camera and they function just fine. Besides you can manually adjust brightness. The proximity sensor also has nothing to do with the camera. It's located under the speaker for receiving calls near the LED.
yareally said:
I dont know about that. Very few android phones have a front facing camera and they function just fine. Besides you can manually adjust brightness. The proximity sensor also has nothing to do with the camera. It's located under the speaker for receiving calls near the LED.
Click to expand...
Click to collapse
I was wrong. You're right about the prox sensor. Still, the devices that lack the FFC use a light sensor instead. I'd go nuts trying to adjust the screen all the time. If it were completely removed, there's still no promise the screen would even light up.
loonatik78 said:
I was wrong. You're right about the prox sensor. Still, the devices that lack the FFC use a light sensor instead. I'd go nuts trying to adjust the screen all the time. If it were completely removed, there's still no promise the screen would even light up.
Click to expand...
Click to collapse
Yeah that would be a pain, lol, but maybe he's desperate enough he doesn't care. He would obviously be addicted to his phone way more than I would be if so
yareally said:
Yeah that would be a pain, lol, but maybe he's desperate enough he doesn't care. He would obviously be addicted to his phone way more than I would be if so
Click to expand...
Click to collapse
Well, it's stuff like this that's the reason RIM still builds their top tier BlackBerrys with and without cameras.
Maybe this is too simple but how about just leave your phone in your car?
Sent from my Synergized Thunderbolt via XDA Premium App
Just a suggestion to the OP, there's been others that have asked the same question before. Might try looking through those http://www.google.com/search?client...ndroid+phone&sourceid=opera&ie=utf-8&oe=utf-8 for different solutions.
Yeah, I've been doing that (leaving phone in car), but I'm getting bored of the playlists on my ipod and would like to spice it up with Pandora.
Also, I would like to be able to receive emergency calls/texts from my family.
I have searched Google, which is how I got that first link with the teardown. If you guys think it's unwise to take out the cameras after looking at that, please say so. If you're making assumptions about the necessity of the cameras, take a look at the link.
infinite012 said:
Yeah, I've been doing that (leaving phone in car), but I'm getting bored of the playlists on my ipod and would like to spice it up with Pandora.
Also, I would like to be able to receive emergency calls/texts from my family.
I have searched Google, which is how I got that first link with the teardown. If you guys think it's unwise to take out the cameras after looking at that, please say so. If you're making assumptions about the necessity of the cameras, take a look at the link.
Click to expand...
Click to collapse
Functionality aside, simply how that big one on the rear is mounted would dissuade me.
infinite012 said:
Yeah, I've been doing that (leaving phone in car), but I'm getting bored of the playlists on my ipod and would like to spice it up with Pandora.
Also, I would like to be able to receive emergency calls/texts from my family.
I have searched Google, which is how I got that first link with the teardown. If you guys think it's unwise to take out the cameras after looking at that, please say so. If you're making assumptions about the necessity of the cameras, take a look at the link.
Click to expand...
Click to collapse
It's your phone, but I wouldn't mess with it unless I knew what I were doing with it.
Remove the camera apps, you can't take a picture with it if the application to take it has been removed. (i'm sure the company won't believe it, but it is a solution)
g00s3y said:
Remove the camera apps, you can't take a picture with it if the application to take it has been removed. (i'm sure the company won't believe it, but it is a solution)
Click to expand...
Click to collapse
If only it were that simple. I didn't believe it at first, but people get fired for having camera capable phones even if they don't have a battery in or near the phone. They're really strict on security.
Go to Wal-Mart & get a cheap Go Phone and some mins . If it has a camera , destroy that one .
I have noticed recently (perhaps related to the .21 update?) that Google sky was not tracking well with my movements... so I tried 2 compass applications to validate the e-compass performance.
The compass behavior is really squirrely and seems to have very little correlation to which direction the tablet is pointed.
It seems that the compass must have worked better in the past as Google Sky used to work great.
Can anyone else report if their compass is working properly? What app did you use to verify it? What orientation did you hold your TFP to get a good result?
Mine has never worked correctly, and I've been trying off and on since I first got it in December, before any official ICS update was even released. I always assumed it was related to the poor GPS performance.
nategodin said:
Mine has never worked correctly, and I've been trying off and on since I first got it in December, before any official ICS update was even released. I always assumed it was related to the poor GPS performance.
Click to expand...
Click to collapse
Exactly the same for me. And I have the (same) prime ever since December as well.
MNDaveC said:
I have noticed recently (perhaps related to the .21 update?) that Google sky was not tracking well with my movements...
Click to expand...
Click to collapse
No change (for better or worse) with .21 or ... ever
MNDaveC said:
It seems that the compass must have worked better in the past as Google Sky used to work great.
Click to expand...
Click to collapse
It never worked reliably. I'm sorry but I am skeptical about your statement "worked great". Search this forum for my posts mentioning the e-compass as almost unusable.
I once had fun watching the compass readings constantly revolve, making full 360 deg sweeps in just a little over a minute (sic!). A recalibration brought back the unreliable, miserable readings.
Yes this is a problem. But can be fixed by a simple step. Just move, rotate your tab in all directions (up down, left right and on its own AXIS)
This should fix the compass. In my case, thus would fix it but would revert back
Sent from my GT-I9100 using Tapatalk
I also confirm twitchy e-compass... no new news here though, it is all related to our known problems.
Sent from my Transformer Prime TF201 using Tapatalk
Make sure you do not have mock locations enabled in the developer settings....This throws off the compass
google skymap sucks for me too. I'll double check to see if mock locations is on, I don't think it is, I've fiddled with all the skymap settings with no results.
I have to calibrate my compass using GPS Status every time I want to use it. After that, it seems to work fine.
There seems to be a problem with keeping calibration settings for the compass after each reboot...
These e-compasses do not use the magnetic field to give direction. They totally rely on GPS. GPS accuracy requires movement. The compass gets 2 (or more) readings, and then caculates the location and direction from them.
Even a good GPS device like Garmin, will have difficulty. If you are stationary, the gps reading will vary. The best accuracy for consumers is about 10 ft. If you had a test app, and were stationary....you would see that the individual gps readings are grouped in about a 10 ft radius from your position, with a few being outside that.
robertg9 said:
These e-compasses do not use the magnetic field to give direction. They totally rely on GPS. GPS accuracy requires movement. The compass gets 2 (or more) readings, and then caculates the location and direction from them.
Click to expand...
Click to collapse
Please stop diffusing inaccurate information.
Prime is equipped with a physical magnetometer. PERIOD.
You can try to recalibrate the compass by moving the device in a large figure of eight in a horizontal plane, outside and away from any ferrous metal.
Also, beware of any magnetic devices, fastenings or closures in protective cases you might buy. Don't park your Prime on a convenient HiFi loudspeaker top!
FG
ForeignGadger said:
You can try to recalibrate the compass by moving the device in a large figure of eight in a horizontal plane, outside and away from any ferrous metal.
Also, beware of any magnetic devices, fastenings or closures in protective cases you might buy. Don't park your Prime on a convenient HiFi loudspeaker top!
FG
Click to expand...
Click to collapse
The Prime's keyboard itself has a magnet in it, and I'd imagine the Prime does as well to register that field so that the screen shuts off when you close it.
But yes! Keep your Primes off of awesome speakers lol, as well as all your other precious electronics
I haven't actually played with the compass all that much as I've fretted over WiFi/BT and GPS. I know that my accelerometer consistently feels off: until I actually run tests on it. I think many of our issues (outside of the aluminum body and bad choice in wireless module) really are drivers and apps' implementations of h/w as opposed to the h/w itself.
robertg9 said:
These e-compasses do not use the magnetic field to give direction. They totally rely on GPS. GPS accuracy requires movement. The compass gets 2 (or more) readings, and then caculates the location and direction from them.
Even a good GPS device like Garmin, will have difficulty. If you are stationary, the gps reading will vary. The best accuracy for consumers is about 10 ft. If you had a test app, and were stationary....you would see that the individual gps readings are grouped in about a 10 ft radius from your position, with a few being outside that.
Click to expand...
Click to collapse
I do not know why the hell you would post this. The meter does detect magnetic fields. Why do you think they call it an ecompass. Put a magnet close to it and open a compass app. Even your GPS explanation is horrible and incorrect.
sorry I just hate when people give out stupid info
Sent from my ADR6300 using xda premium
ForeignGadger said:
You can try to recalibrate the compass by moving the device in a large figure of eight in a horizontal plane, outside and away from any ferrous metal.
Also, beware of any magnetic devices, fastenings or closures in protective cases you might buy. Don't park your Prime on a convenient HiFi loudspeaker top!
FG
Click to expand...
Click to collapse
Okay I have read this and tried on an android phone with no success. Just to clear things up, do I keep the prime oriented the same way through the figure eights or point it through, kinda like a kid playing with a toy car driving in a figure eight. Also do I keep the prime horizontal as well? sorry to sound like a dolt, but I can see many ways to do a figure eight with the prime. Your Horizontal plane was a help.
As far as I know, just keep the device pointing the same way and horizontal.
If your compass does not respond to this, I suggest it might be stuffed.
FG
Its not perfect but after all the criticisms i have to say i like it
Sent from my TrueSmart using XDA Free mobile app
It's ok, I like mine too
What do you like about it though?
I'm getting another SIM to use in it and I think I'll like it more then, but the fact that the companion app is so poor means that the integration with bluetooth isn't an option really.
I'm quite happy with it too.
I have the 1/8 2100 version, and all seem to work well.
- It started up out of the box
- The cradles charge ( I got the extra one I ordered)
- the buttons don't fall off
- call quality is awesome
- screen sensitivity is good (sometimes a little too good, but hey)
- bluetooth, wifi and gps have a proper connection
- "back button" swipe left action works
And in general use:
- surprisingly easy to read on small screen
- even able to watch short video/tutorials on watch (very handy when needing both hands free)
- app installing/start up goes quick
- I use Minuum Keyboard now, and that is awesome, Frees up half the screen for reading conversations, perfect!
- with Minuum keyboard it's also easy to make small voice commands that turn to text, for me works even quicker than responding with the "normal phone" in the old days
by having the phone on the wrist it makes checking if you need to respond 10 times faster. Just a flick of the hand and a two finger swipe when you get a short vibrate or buzz from a message/email/update and you are ready. Where as the "normal phone" you have to get out of the pocket, check and put back.
The two biggest downside that I find, are not necessarily omate related but more smartwatch in general:
- by having the watch on your wrist, if you use it for typing, by default are using both arms. Where as a "normal phone" you can operate with one hand.
- I don't 100% like the reading angle: you have to hold your arm really parallel to the body to read without make strange neck moves. Having "landscape" mode is even worse.
I think about 35 degree angle of the arm would be a way better reading position. That maybe would be the biggest advantage of the round type smartwatches like the moto 360, the ability to adjust the screen orientation till it ergonomically fits you best.
Wiggz said:
What do you like about it though?
I'm getting another SIM to use in it and I think I'll like it more then, but the fact that the companion app is so poor means that the integration with bluetooth isn't an option really.
Click to expand...
Click to collapse
My experience is pretty much identical to timkey's. It does what its supposed to. Typing is obviously slower but its better than I thought. Screen is sharp. It's fast. And it's a phone on my wrist I think rooting it and putting on soft keys and a status bar are pretty essential though. I do find the touch screen goes a little haywire sometimes.
To help with the viewing angle, I wear it a little loose and then I can twist it slightly towards me.
Sent from my LG-V500 using XDA Free mobile app
I like it because it functions just how I wanted it to. Its quite simply an android phone on your wrist, which is pretty damn awesome. Calls work pretty good, texting on this is awesome (so handy being able to just look at your wrist), and it's pretty much taken every app and game I've thrown at it so far. I also like being able to throw a song on and have handsfree music, so I can cut rebar or something at work and have music. And to top it off, I get pretty great battery life out of it. It's always lasted at least a full day, if not two. Even after two days the lowest I've had it is 30%
So, despite the company itself acting like a total noob for supporting this, it does function quite well (after some necessary patching of course). Having proper sources and support with proper firmware updates and having more tweaks android is known for available, would all just be icing on the cake.
So would those who like it buy a TS2, or has the arrogance and sheer mismanagement of Omate put you off, even though you enjoy the product?
I enjoy mine, though I can rarely use it as intended due to water issues. I have a T-Mobile sim in it. I would not only not ever buy anything associated with Omate ever again, but also not Umeox and not MTK. Never Again.
Sent from my Nexus 5 using Tapatalk
It depends. I mean, the reality is I paid about £120 for a brand new android phone in watch form. If the TS2 was also a bargain, I'd probably get one. Hopefully they would learn some good lessons from this.
I am an engineer and did my degree in electronics, so I have some experience with product development. It was very clear to me that the timescales Omate were claiming were ridiculous and that made me question their competence. I'm still impressed they produced what they did as fast as they did. The testing problems people are experiencing are not acceptable but they are expected. Omate kinda painted themselves into an corner with their optimistic claims and high ambitions.
Now, all that said, I don't see what I would want from a TS2 that in don't get from this device. Its too small to do anything too intricate. It creates a WiFi hotspot and provides basic smartphone functionality well, which is all I need it for. Maybe if I got a 4G data plan, it might be good to have a watch that can make use of it but that's all I can think of.
Sent from my LG-V500 using XDA Free mobile app
The device has potential. I could maybe live with the HW shortcomings like IP rating, non-responsive buttons, add SD-card kills back seal etc as well as HW limitations like a little too heavy and too thick. The delays and communication failure from Omate is a separate story. I believe llepen believes what he says, he is still communicating still.
What I do not accept is the crappy firmware, that is HW specific. Noproper open source either. That kills BTLE, battery etc, as well as limits the adaptations required to get Android usable on a small device. I am not talking about limiting functionality like Android Wear, but an adapted Android experience w button actionssweep. Omate/Umeox mostly relies on MediaTek, and MediaTek seem to make good HW, but are both breaking GPL and incompetent in SW development.
I love my TS. I tried to have few expectations as to not be let down if it sucked, but I was happy to find that it was just about everything I could hope for in a smartwatch. It is solidly built, not too big, the screen is very sharp and sensitive, the camera is Good Enough(tm) (though the camera app really should rotate 90 degress left, which it does in the BlueTooth tether ROM, iirc).
My one major complaint is that Omate's version Android is awful. I work around it with third-party software (e.g. Nova Launcher, All in One Gestures), and with some effort, after-market ROMs can be ported. I'm very disappointed that no sources are available, but we all knew that would be the case.
That the notification bar is always hidden bugs the heck out of me, but the BlueTooth tether ROM fixes that.
Screen-on battery life is okay; not great, not awful, but it charges very quickly, so that's usually not a big deal. Screen-off life is fantastic.
I wish I could change the DPI for Ingress. It would be so cool to be able to play on my wrist.
Working with Omate is indeed like rolling a boulder uphill, and while I'll probably never buy anything from them again until they prove themselves reliable, I do believe Le Pen is trying. And I'm as disappointed with Omate as I am with those who continue to try to poison the TS community, making productive, open collaboration difficult.
timkey said:
I'm quite happy with it too.
Click to expand...
Click to collapse
I agree with just about everything you say. Anymore I use my phone only for long text conversations and more-than-casual web browsing. Everything else is done on my TS. Flesky is remarkably easy to use once you get used to it (although whoever decided to put backspace next to return needs a smack in the face). I'm especially happy that it's so easy to read text on the small screen as I read lots of RSS feeds on and off all day long.
The reading angle bothered me at first, but my arm just had to get used to being held in an unfamiliar position.
gerhardo said:
I could maybe live with the HW shortcomings like IP rating, non-responsive buttons, add SD-card kills back seal etc as well as HW limitations like a little too heavy and too thick.
Click to expand...
Click to collapse
The IP rating and back seal issues don't matter much to me, but I can see how that would be a disappointment to other users. The button responsiveness, weight, and thickness are fine for me. It did seem a bit heavy for the first day or two, but I quickly got used to it.
nicktastique said:
I wish I could change the DPI for Ingress. It would be so cool to be able to play on my wrist.
Working with Omate is indeed like rolling a boulder uphill, and while I'll probably never buy anything from them again until they prove themselves reliable, I do believe Le Pen is trying. And I'm as disappointed with Omate as I am with those who continue to try to poison the TS community, making productive, open collaboration difficult.
Click to expand...
Click to collapse
Xposed Framework
Xposed Per App Settings
I consider setting default dpi to something higher than 120, to see better and change dpi where needed
gerhardo said:
Xposed Framework
Xposed Per App Settings
I consider setting default dpi to something higher than 120, to see better and change dpi where needed
Click to expand...
Click to collapse
Yes, but it doesn't work, and others have confirmed. Is your experience different?
Smockingjacket said:
So would those who like it buy a TS2, or has the arrogance and sheer mismanagement of Omate put you off, even though you enjoy the product?
Click to expand...
Click to collapse
No.
While I like the watch itself, if I were to drop another $200-$300 on a new watch, it would be from a company that can support it's device a little more competently. I really doubt we'll ever see a firmware update.
Although as long as this watch doesn't **** the bed I should be using it for a good long time. It functions pretty much like I want it to, so I don't feel the need to upgrade anytime soon.
I like it as well. After changing launcher and installing a few apps I felt it was usable. I tried for a while to use it as phone replacement. It DOES work as that, but the upsides of having a watch (smaller / lighter than a phone, won't forget something strapped to your arm and so on) doesn't really outweigh the downsides (hard to type, sometimes hard to navigate menus, small screen causing readability and layout issues, battery is slightly worse than my phone, etc). The most annoying issue though is when the screen goes into over-sensitive mode and register button press all over the place. Someone said it gets a lot better with a screen protector on, I will try that.
However, it does work great in some areas. My main use is for exercise - RunKeeper (and similar apps) works great. I can take a run, track my progress, listen to music, and see notifications if someone is trying to reach me, without needing a much more cumbersome phone jumping around in my pocket.
It's also useful when I'm outdoors, say fishing or hiking. While it isn't waterproof, it does what I need (gps / maps, tell time, make calls if I need to, no risk of dropping it).
So overall, it's a nice device (even though software and such needs some urgent updates). Maybe not great for a phone replacement but for outdoor use and exercise it's really good imo.
nicktastique said:
Yes, but it doesn't work, and others have confirmed. Is your experience different?
Click to expand...
Click to collapse
Works fine for me, using it for SuperSU and Titanium.
Well, the TS is unavailable again: Screen is black, no response to buttons (except the feedback I added with Xposed Additions to get virtual physical button) and no adb. adb is a common issue, very seldom works. But I have my device for a couple of days, I have occasionally borrowed one for time to time though.
He means that changing the DPI to 90 for Ingress doesn't work, I think, gerhardo.
Actually, I play Ingress with my TrueSmart and the stock Ingress client (only) and it mostly does work. Hacking and firing work fine from the front screen long press menu and I was even able to deploy I found recently mainly by lucky pressing in the portal view on a crunched up set of buttons there. I had previously thought deploying impossible with stock and stock. Its still impractical.
What was reported no longer working was adjusting the DPI because of some change Niantic introduced into their code at some point a while back. I have not tried that anyway.
Sent from my Nexus 5 using Tapatalk
trent999 said:
He means that changing the DPI to 90 for Ingress doesn't work, I think, gerhardo.
Click to expand...
Click to collapse
Yes that's what I mean in particular. Ingress no longer honors density settings via App Settings. It doesn't even appear to honor ro.sf.lcd_density on the TS, though it does on my Note 2 (which is annoying since it's set to 280).
I like mine too (1/8 2100 Dev).
Straight from the box, no patch, no rom, no bootloader, no nothing. The apps tho aren't there but it's almost like when the new Xbox, Playstation or Nintendo come out - people don't introduce games until the hardware is in use. I figure the developers of apps are waiting, working and planning something awesome for all smartwatches (not just companions).
Omate, well, hopefully, lessons on their side have been learned and fingers crossed the TS2 (if there is one) will be better planned for.
Hats off to SWApp Link tho. The app is the best thing that's been introduced for me. I had my SIM in my phone originally, then the watch and now back to the phone (just to work out what is best for me - I take a lot of photos and use 4G too much so my Note 3 is where my SIM is needed most) but the app - Bluetooth aside - is absolutely wonderful.
I don't regret buying the TureSmart, nor regret using Kickstarter - I have backed many an idea over the months. My regret is that the technology in total isn't there, yet.
But thank you XDA for being here :good:
Hello, I purchased a v30 and would like to use the AOD. However, with all the burn in issues popping up all over the place, I'm a little worried about ruining my display. Does anyone know if the pixels shift to prevent burn in? Is there proof of this, such as a time lapse video or acknowledgement from lg? Thanks
tveith said:
Hello, I purchased a v30 and would like to use the AOD. However, with all the burn in issues popping up all over the place, I'm a little worried about ruining my display. Does anyone know if the pixels shift to prevent burn in? Is there proof of this, such as a time lapse video or acknowledgement from lg? Thanks
Click to expand...
Click to collapse
I don't have the phone myself but from what I understand yes the pixels do shift, try to use the AOD you should see that after a while it will appear slightly in a slightly different position
I had the same worry and was informed that AOD does move throughout the day. I can verify that this is true as I now leave it on with it scheduled to be off 12-5am when I should be asleep. Another tactic I've picked up to help make sure there's no burn in is to place the phone face down when I don't really need to be looking at it. (Such as now while I'm at a computer that will also show my notifications.) The proximity sensor turns off the AOD and it comes on pretty quickly when you pick it up, but not so quickly that you're wondering if it ever did turn off.
AOD does indeed move things around. Nothing seems to stay in the same place.
As for burn-in. I used mine as a sat-nav for 8 hours today and no visible burn-in on the screen.
CHH2 said:
I had the same worry and was informed that AOD does move throughout the day. I can verify that this is true as I now leave it on with it scheduled to be off 12-5am when I should be asleep. Another tactic I've picked up to help make sure there's no burn in is to place the phone face down when I don't really need to be looking at it. (Such as now while I'm at a computer that will also show my notifications.) The proximity sensor turns off the AOD and it comes on pretty quickly when you pick it up, but not so quickly that you're wondering if it ever did turn off.
Click to expand...
Click to collapse
use something like a piece of paper to cover the proximity sensor when phone is facing up will do the same trick.
debugger919 said:
use something like a piece of paper to cover the proximity sensor when phone is facing up will do the same trick.
Click to expand...
Click to collapse
I rarely have a piece of paper. Flipping over is always an option and pretty simple.
Hi. I didn't want to post a new thread.
AOD clock never changes position on my phone. Does anyone experince the same thing? It's on 8.0.0, june 1st 2018 and kernel 4.4.78.
CooLasFcuK said:
Hi. I didn't want to post a new thread.
AOD clock never changes position on my phone. Does anyone experince the same thing? It's on 8.0.0, june 1st 2018 and kernel 4.4.78.
Click to expand...
Click to collapse
I'm on 8.0 August 2018 and 4.4.78 and mine moves. I'm not sure what the dynamics are behind what makes it move (guessing time) but I know that mine does move eventually
How long have you monitored it?
KUSOsan said:
I'm on 8.0 August 2018 and 4.4.78 and mine moves. I'm not sure what the dynamics are behind what makes it move (guessing time) but I know that mine does move eventually
How long have you monitored it?
Click to expand...
Click to collapse
I've carefully placed a piece of paper over the screen to see if the clock moves and it didn't move in 10 minutes. Should I wait longer? I think it's a long time.
CooLasFcuK said:
I've carefully placed a piece of paper over the screen to see if the clock moves and it didn't move in 10 minutes. Should I wait longer? I think it's a long time.
Click to expand...
Click to collapse
I haven't done any testing but I'm pretty sure mine has taken longer than 10 minutes though I'm not sure how long to say.
KUSOsan said:
I haven't done any testing but I'm pretty sure mine has taken longer than 10 minutes though I'm not sure how long to say.
Click to expand...
Click to collapse
I've waited for 25 minutes and it didn't move. I really want to use this feature but without the risk of burn in.
CooLasFcuK said:
I've waited for 25 minutes and it didn't move. I really want to use this feature but without the risk of burn in.
Click to expand...
Click to collapse
No one in this forum has had burn in.
ChazzMatt said:
No one in this forum has had burn in.
Click to expand...
Click to collapse
Yes but they might have had if the clock stood still. I mean we are talking about hours. I think it will happen eventually.
CooLasFcuK said:
Yes but they might have had if the clock stood still. I mean we are talking about hours. I think it will happen eventually.
Click to expand...
Click to collapse
My understanding is the pixels move microscopically enough to prevent burn in. You may never see the clock move
ChazzMatt said:
My understanding is the pixels move microscopically enough to prevent burn in. You may never see the clock move
Click to expand...
Click to collapse
That makes sense but I've seen people on forums saying that they see the clock moving with their eyes. I don't know whether they are on Nougat or Oreo. I'd be glad if someone tried AOD for 30 minutes and see if the clock moves. I place a piece of paper where the clock ends and it is effective to see the movement or the lack of it.
Don't worry about it. It's also not in max brightness. I own it for a year and the screen is perfect.
I use the digital clock AOD. I notice it shifts between the top and middle of the screen throughout the day. I don't see it moving, but throughout the day I notice it's different positions.
ChazzMatt said:
My understanding is the pixels move microscopically enough to prevent burn in. You may never see the clock move
Click to expand...
Click to collapse
galr said:
Don't worry about it. It's also not in max brightness. I own it for a year and the screen is perfect.
Click to expand...
Click to collapse
These are the important points.
Burn-in happens when 1: pixels are at a high brightness and 2: they're holding a static image.
It's a common misconception that burn-in happens because of pixels getting partially "stuck". This doesn't apply to OLED displays; what happens is that each subpixel has a finite lifetime due to their organic elements, and will slowly use up that lifetime while on. Running at design voltage and no PWM (e.g. full brightness) will use that lifetime at almost the fastest rate possible, and images that have both dark and light areas will burn in the worst.
This is why store displays, that tend to be blasting at either 100% brightness or (if whoever set the firmware is particularly stupid) full-bright/outdoors mode with a short sequence of static advertisement screens, can burn up even the most durable OLED screen.
As I understand, AOD is fairly dim even on its "bright" setting. It probably achieves this brightness via both voltage and PWM, so the pixels are both only actually powered part of the time and at much lower than design voltage; even if only one of these is true, that means each subpixel is being run at far below design tolerances, with an increase in lifetime as the voltage decreases/flicker increases.
That, the changing time, and the slight shifting of the image means that it's pretty unlikely that you'll be able to get the clock to burn in within a meaningful timeframe. If you're really worried about it, use the dim setting.
Actually My wife's display had some discoloration issues LG replaced the panel is all good now. Me personally I don't use Always on display I like to save battery even if its two percent. Now my HP Touchpad that I use as a clock has major burn in LOL.
I just ordered a Pixel 6, which should be arriving in a couple of days. I want to do my best and locating any issues within the two week return policy.
From what I have read, most of the Pixel bugs have been fixed, and other issues some people have in other people don't.
Is there a way that I can run certain tests to see if those bugs are impacting my phone on the network that I'm on?
That is, for the fingerprint sensor, it's obvious how to test that.. For items such as connectivity, that seems a bit more complex.
As I have work and other obligations, as most people do, I can't sit in front of my phone all day for 14 days to figure out what issues exist.
Are there some recommendations on what /how to test, to see if things are any issues that are important to me?
Thanks
ScreenTest; check the display. It should be perfect. That's the first thing I check.
blackhawk said:
ScreenTest; check the display. It should be perfect. That's the first thing I check.
Click to expand...
Click to collapse
Thanks. That's great advice for phones in general. And recommendations for some burn-in type test would not be bad, altogether.
I was asking more specifically regarding issues which people have with the Pixel 6, even at this late date 9 months later. For example, related to network connectivity and overheating.
Thanks
dzr said:
Thanks. That's great advice for phones in general. And recommendations for some burn-in type test would not be bad, altogether.
I was asking more specifically regarding issues which people have with the Pixel 6, even at this late date 9 months later. For example, related to network connectivity and overheating.
Thanks
Click to expand...
Click to collapse
You're welcome. Sorry I can't give you more concise information.
Looking more for dead or wrong color pixels. Variations in color or greyscale, there should be none.
Test the cams. Test the phone, internet, bt and wifi. Test the sensors and fast charging.
Do the basics first as failure of these will cause a return for sure.
Fortunately you have the luxury of real users reviews now, months latter.
You don't have to dig too hard. Do searches on Google, use xda in search to pull up threads about easily on this site.
blackhawk said:
You're welcome. Sorry I can't give you more concise information.
Looking more for dead or wrong color pixels. Variations in color or greyscale, there should be none.
Test the cams. Test the phone, internet, bt and wifi. Test the sensors and fast charging.
Do the basics first as failure of these will cause a return for sure.
Fortunately you have the luxury of real users reviews now, months latter.
You don't have to dig too hard. Do searches on Google, use xda in search to pull up threads about easily on this site.
Click to expand...
Click to collapse
I also guess that you were talking about the more recently reported issues with dead pixels around the camera, not just a generic item.
dzr said:
I also guess that you were talking about the more recently reported issues with dead pixels around the camera, not just a generic item.
Click to expand...
Click to collapse
There have been more issues across the board with the variable refresh rate displays, not just dead pixels and not just Google. Personally I don't think the variable refresh rate displays are worth the trouble. They are extremely hard to accurately color calibrate as well; too many variables.
There been battery/heat issues too, but many other brands are having them as well. Android 11/12 are no gems. The scoped storage sucks extra CPU cycles/battery.
Take a picture of a blank wall and look for circle shaped spots. I didn't do that and now I have Casper the friendly ghost on every low detailed photo.
blackhawk said:
ScreenTest; check the display. It should be perfect. That's the first thing I check.
Click to expand...
Click to collapse
Is there a specific app that you recommend? They're quite a number of them called screentest.
Interestingly, I was expecting comments regarding network connectivity, overheating and the fingerprint reader.... Instead in hearing about camera and screen... Starting to think twice about this phone... I only ordered it after articles talked about bugs mostly fixed ..(and $100 off). I was waiting for the 6a (I have a 3a)
dzr said:
Is there a specific app that you recommend? They're quite a number of them called screentest.
Interestingly, I was expecting comments regarding network connectivity, overheating and the fingerprint reader.... Instead in hearing about camera and screen... Starting to think twice about this phone... I only ordered it after articles talked about bugs mostly fixed ..(and $100 off). I was waiting for the 6a (I have a 3a)
Click to expand...
Click to collapse
It's Screen Test, my bad.
This version will run on Android 9 and 10, not sure about 11/12.
Any tests for the networking issues?
blackhawk said:
There have been more issues across the board with the variable refresh rate displays, not just dead pixels and not just Google. Personally I don't think the variable refresh rate displays are worth the trouble. They are extremely hard to accurately color calibrate as well; too many variables.
There been battery/heat issues too, but many other brands are having them as well. Android 11/12 are no gems. The scoped storage sucks extra CPU cycles/battery.
Click to expand...
Click to collapse
So, I received the phone. That screen testing software, doesn't show anything around the camera, notification area. As such, the screen testing looked fine. But, I see a gradient in that portion of the screen. Is that expected?
At first I thought that I had massive networking issues ... But then I noticed that both the 3A and 6 have Network issues when they are on within a few feet of each other. Even if the other phone is in airplane mode. Once I turned one or the other off completely, the other phone worked fine.
I need to get used to the size of this.. hopefully I can. Right now my hand is cramping. Any suggestions? I'm really used to using a phone with one hand.
macaulay mcculkin said:
Take a picture of a blank wall and look for circle shaped spots. I didn't do that and now I have Casper the friendly ghost on every low detailed photo.
Click to expand...
Click to collapse
Thankfully, mine seems fine in this regard.
dzr said:
So, I received the phone. That screen testing software, doesn't show anything around the camera, notification area. As such, the screen testing looked fine. But, I see a gradient in that portion of the screen. Is that expected?
At first I thought that I had massive networking issues ... But then I noticed that both the 3A and 6 have Network issues when they are on within a few feet of each other. Even if the other phone is in airplane mode. Once I turned one or the other off completely, the other phone worked fine.
I need to get used to the size of this.. hopefully I can. Right now my hand is cramping. Any suggestions? I'm really used to using a phone with one hand.
Click to expand...
Click to collapse
Not sure. ScreenTest isn't working as expected.
It should cover the whole display.
Check to see if there's a newer version.
Get a good case and get use to using both hands. A case is needed to protect it. I use the Zizo Bolt but don't think they make cases for Pixels. The N10+ is not really one hand usable either but my eyes say the added screen acreage is worth it.
blackhawk said:
Not sure. ScreenTest isn't working as expected.
It should cover the whole display.
Check to see if there's a newer version.
Get a good case and get use to using both hands. A case is needed to protect it. I use the Zizo Bolt but don't think they make cases for Pixels. The N10+ is not really one hand usable either but my eyes say the added screen acreage is worth it.
Click to expand...
Click to collapse
I downloaded another screen test and the color is stable across the screen.
dzr said:
Interestingly, I was expecting comments regarding network connectivity, overheating and the fingerprint reader.... Instead in hearing about camera and screen...
Click to expand...
Click to collapse
I haven't had any problems with my P6, but from what I've read the problems will be easy to spot if you have them.
Stay off wifi for a while and make sure you have a stable mobile data connection (not constantly switching between 4G & 5G, being able to pull up websites, watch videos, etc.). See if the fingerprint scanner works at least 8/10 or 9/10 times. Does the phone heat up in normal use. Can you get at least a day out of the battery under normal use.
I don't think you need to stress out about locating issues. If you have them, you'll know.
Nidstang said:
I haven't had any problems with my P6, but from what I've read the problems will be easy to spot if you have them.
Stay off wifi for a while and make sure you have a stable mobile data connection (not constantly switching between 4G & 5G, being able to pull up websites, watch videos, etc.). See if the fingerprint scanner works at least 8/10 or 9/10 times. Does the phone heat up in normal use. Can you get at least a day out of the battery under normal use.
I don't think you need to stress out about locating issues. If you have them, you'll know.
Click to expand...
Click to collapse
Exactly, you do have a warranty if there happens to be issues. If theres a big hardware issue, they'd do a recall if not there'd be a class action like the N6P, the $400 we got was pretty cool.
I ended up having some audio issues with Bluetooth in my car and some siblilance (letter s) issues, on hd voice. I ended up returning the Pixel 6 and bought a 6A. I do not have this problems in the 6A. My current plan does not have 5G, so I can't test against it. I need to spend more time with 4G and see how that does. The fingerprint reader, I think they even be slightly slower than the pixel 6. The screen seems okay as well as the camera.