I'm developing an app that is supposed to measure vertical accelerations, and in the process I've discovered that the accelerometer seems to be uncalibrated. When the phone is lying perfectly horizontal, the Z axis acceleration should be 9.81, but it is about 8.81 (X and Y being roughly 0.0). I can of course offset the error from within the app by letting the user "calibrate" the app while the phone is lying still. But it seems odd that there is no method within Android to do this - sometimes Google Maps prompts me to calibrate the compass by moving the phone in figure eights - but I have not seen any way to calibrate other sensors... is it possible? A further problem is that if I turn the phone so the top is facing straight up (up/down in line with the direction of gravity), the offset of the axis' are different from what is expected, and different from the offsets I get when the screen is facing up. This all seems to indicate that the accelerometer is not as accurate as one might think, and when adding rotation to the mix the results get even more skewed...

The"compass" in Android seems to be a projection of the 3D magnetic field measured by a magnetometer : Having read https://electronics.stackexchange.com/a/22271/282833 I still have three questions: 1. Assuming the compass has been calibrated while quality testing before shipping, why is it needed to calibrate the compass again? Or in other words: Assuming that the magnetic sensor is placed the same with high precision on each device of the same series, why can't a "golden sample" be calibrated and the data set to all of the similar devices? 2. Assuming you calibrated the compass and you use it in more or less the same area (meaning: I know that the compass may need re-calibration when moving a significant distance, like a few hundred km), but same area means less than 50km), what are the reasons you must re-calibrate the sensor after some time? 3. Is the compass calibration global to all apps, or do individual apps require separate compass calibration? It seems some apps suggest re-calibrating the compass frequently, while others don't. Background for the question is that even after calibrating the compass, it started to "go mad", meaning north was almost 180° off.

Good day. Installed a new NOHON BN59 5000mAh battery in Xiaomi PocoF3 phone (original battery 4520mAh). According to the Aida64 application, the battery charges up to 100% (4400-4500mAh) and continues to charge the battery to approximately 4900mAh and more... However, as soon as the charging current drops indicating the end of the charge, the remaining capacity readings reset to the standard value of 4250mAh. I can't understand why the phone doesn't want to recognize the full capacity of the new battery. After all, earlier, when the phone was new, the same Aida64 saw the capacity of the original battery not as 4520mAh, but as 4700mAh and even slightly more... Well, such things happen with new batteries, when the capacity is slightly higher than typical. And now, with a new battery, it doesn't even want to recognize anything above 4600mAh. It charges to nearly full capacity and that's what it shows, but as soon as the current drops to 0.5mAh, the battery value displayed is 4535-4550mAh. Editing the Framework in the offer folder doesn't help solve this issue. I'm using the native Miui14 Android 13. Could the operating system eventually understand that there is already a 5000mAh battery in the phone? Do I need to do something? Maybe reflash the phone? I've changed MIUI kernels, but it doesn't help.

I have a Nexus 5X and was in a bit of a hurry when I followed the setup steps. There was a calibrate compass wizard, which I skipped because I wanted to do this later. However, I've not figured out yet how to launch the compass calibration wizard again. I found this question on Android.SE telling about the general process, as well as this Google support article , but I couldn't figure out how to launch that wizard again. Any ideas?

My phone (Pixel 5a) went from 100% battery to off quite quickly, and it had been doing so. When it died from 100%, I turned it back on. It turned on, showed 0%, and died within a minute. I plugged it in (via USB-C, not wireless). While off but charging (without interruption), I checked and found it steadily increasing toward 100%. I saw it at 93%, then 97%, but then it went to 96%, 95%, and 93%. Hours later, it's still plugged in but showing 92%. Is the battery discovering that its maximum charge is much higher than it had been? Or, despite a charging animation on the "off but charging" screen, is the phone discharging? I'm not sure about the version, but it is the latest standard/stable OS and security version as of today (2023.10.23).

10.2" Secain Chinese head unit touch screen only works with a usb mouse.Since I reinstalled and updated the iGo navigation app last year, I noted that touch sensitivity reduced and eventually became nonexistent. I notice that the touch screen calibration option has dissapeared from settings and every effort including 'Factory Reset' failed to recover the menu option or to get the touch reactivated. Further confusion with trying to update the Android version due to the unit showing that it is 'V 5.0.1' and a test app identifying it as 'V 4.4.2 KitKat'. I would very much appreciate any guidance as to any action that I should take to get the touch working again and maybe recover the menu option. [![Unit specs[![\]\[1\]]]]

I have an Orange pi 2g-IoT board with a 3.97 in TFT touch screen (the whole thing is a set) One of the provided OS images for this board is stock Android 4.4 (at least this is what it claims, the UI does look like it is probably based on 4.4, but I am not sure whether/what kind of specific modifications the manufacturer has made) The LCD touch detection is very flaky (sometimes works and sometimes doesn't, works consistently on some GUI components but doesn't on others, etc, see stackoverflow question about it here ) The user manual that comes with the board doesn't say anything about calibration, but I think some kind of calibration is needed. I had similar problems with the touch screen of a raspberry pi board that I had previously worked on, and it worked perfectly after calibrating the screen using the provided software, so I'm assuming that's what I need to do here as well. The board manufacturer is not very helpful with software support, I'm on my own regarding making this work Is there anything like a generic LCD calibration app for android? I see that there are lots of apps claiming to calibrate the screen if I do a quick playstore search (never used any such app myself). So is that a real thing? How do such apps handle different phone models? I can't use google playstore on this board but I can connect to it using ADB and it has root, so I am ok with installing an apk through ADB. After some random poking around I was able to get a preinstalled app to run on the board which shows LCD screen parameters. Here's part of what this app shows: Is there any way to calibrate this touch screen, or any way to make my own calibration app? I can try and get more screenshots from this app pictured above, if it will be helpful.

I have an Android mobile which seems to be of Samsung, or at least a clone thereof. I got it for my wife as a present, so I don't really know which one. Under the battery pack it says "Model: 19502" when I look through the menus there are absolutely no identifications as to which it is and the settings only allow rather high level stuff, like setting background images, and similar, but nothing system relevant. When I play games I noticed that the tilt is not correct, so I installed "App Sensor Box" which allows me to test the sensors. It shows a board with a ball on it, and I can see that the ball rolls off when I keep it balanced. Unfortunately this app doesn't allow me to calibrate it, so I wanted to know if such an app exists, or what I can do to calibrate it, because there are not setting to trigger this. The apps I found on Play Store all seem to just read, but don't change it.

I recently obtained a new galaxy tab A and have been noticing that touching small buttons in certain places is particularly hard (specifically the "read more" button in youtube comments). After doing some experimenting with the developer options that show touch information, I found that the touch screen didn't want to register touches in vertical lines all across the screen. In particular, when swiping diagonally the registered line meanders to avoid moving horizontally then jumps across to follow my finger, like I'm pulling it across a washboard. Two lines in particular at dx 331.7/332.7 and dx 943.2/944.2 seem to catch the pointer like a cliff. **Is this a software/firmware issue?** Or is this digitizer screwy despite being new? Can this be fixed with a factory reset, or not installing a recent patch, or updating firmware? I've seen this behavior in an older tablet (Memo pad 8) but much worse, so much so that tapping on one of these lines would register a tap on either side of the vertical line, and scrolling would often create double taps. That issue manifested while playing a rhythm game, so I assumed some hardware cracked.

My Samsung Galaxy S6 indicates constantly the wrong direction in Maps, compass apps, etc. as it shows the North always towards the left side of the phone. (This might be a long-term effect of the magnetic phone case.) Compass calibration is reported as "very good" and re-calibrating the compass by moving the phone in a 8-figure pattern doesn't have any effect. Is it possible to somehow reset the compass calibration to factory settings?

I've watched videos and referred some random sites. But I'm not sure if these steps are correct. I used battery calibration app but that doesn't help. I'm using Asus Zenfone Max Pro M2. Running on stable pie. So how to calibrate battery accurately?

My original battery is bloated and is dying quickly after a full charge so I now bought a replacement. Do I need to calibrate this new battery using a calibration app?

I have an HTC 10 running stock Oreo with Sense, not rooted and S-ON. I bought this second hand and don't know whether the issue came up as the phone was upgraded to Oreo, or whether it had always been an issue (which would solve my case). The issue is that the battery seems to work fine, although mobile network standby appears to take an uncomfortably large amount of power, however when it gets to a lower percentage, it shuts off unexpectedly then bootloops when you try to turn it on again. When you plug it in, it shows that the battery is at about 1%, but in a matter of minutes, it charges up to around 40% - this is on a 1mA 5V charger - and then proceeds to charge normally. I can temporarily solve the issue by calibrating my battery, and that makes the mobile network standby drop back to normal, and my battery works fine, and the phone shuts down as expected when it reaches 0%. The problem is that the next time I charge the battery, no matter whether I charge it from nothing to 100% or from 65% to 85%, the problem gradually comes back, and I have to once again drain my battery to calibrate it properly, then wait for it to charge up to 100%. I've heard online that many other HTC 10 owners have experienced similar issues with their device, but the fixes only work for some people sometimes, so this could easily be a software issue or a problem with the battery itself. Which is it?

I heard that charging li-ion batteries to less voltage value *heavily* increases number of (charge-discharge) cycles, while decreasing phone work time(energy return from charge) only for *a little*. Charging only a half of capacity increases number of charges 3x, so there is 1.5x outcome in energy that i could get from battery for its life. I have 5000 mAh battery, and a huge power bank. It is very big capacity, and i am ready to sacrifice some working time to prolong battery life for years as much as possible. So for now it could charge to 4.2V to 100%, and i want to "reconfigure" or "recalibrate" BMS. It should "think" for example that 3.9V is 100% charge and stop charging it, and 3.6V is a 0% and is a device shutdown voltage. How to set this in Android?

I am having an issue with my GS4 's compass. It turns in the opposite direction, i.e., if I turn right, it turns right with me when actually it should turn left w.r.t the screen. I tried calibrating it but the problem persists. Does anyone have any clue about what might be wrong ?

I am wondering how compass calibration works / why e.g. drawing an 8 or rotating the phone to all 3 axis works (or at least shall work) - I mean I would understand the calibration process, if an application would say me: Point to north, then press that button down there, but you can start at basically zero knowledge for the app, just by rotating your phone! How is that done? Also, do I need to enter a special calibration mode or can I draw these figures (like the 8) directly in Google Maps? How does Google Maps know that I am not just really moving the phone but want to calibrate the compass? Thanks for any hint!

My Android Phone Fell from my Hand and it's screen is partially Broken. Don't have much of a difference after breaking the screen but I need to Re-Calibrate my Android Device's Display. Is there any way I can do that? With or without Root? I prefer Without Root.

I am using redmi 2 for about 3 year and it's battery is dead. It was using 2200 mAH battery. So I went to local vendor and bought a copy battery with the rating of 2000 mAH. Now the new battery has less capacity of 200 mAH. But my smartphone is calibrated for 2200 mAH battery. So my smartphone will charge the new battery 200 mAH more. This will deteoriorate the newer battery. So I need way to calibrate the smartphone manually to 2000 mAH so to prevent overcharge of the newer battery. Is there any way to do this with using application and without rooting.

There are several posts on how to calibrate android batteries but none describe its working. How is it that the system can determine at what voltage the battery is considered to be charged (100% or say 4200mV) and what voltage is considered to be discharged (0% or 3400mV)? "Android stops the battery from charging when reaching 100%" but if it is calibrated wrong, how come it wont stop charging at another voltage (say 4100mV) or even continue discharging at a voltage below its normal operation (say 3200mV)? Expected answer: - The actual technical insight on how android determines the current battery level **Edit 1:** I am stressing that my question has nothing to do with battery statistics and how much battery apps have used but solely on the procedure involved with determining the battery % *This is my first question please excuse any conventions I may have missed*

Just got a KBTEL battery that's 3800 mAh compared to the original 2300 mAh nexus battery. I charged it dead overnight, and now its been running for more than 7 hours and the capacity shows below 5% for an hour now but its not dying. How do i get the battery meter to show the actual range? The system still detects a 2300 mAh battery.