Hi,
my battery gets killed by those wakelocks (qpnp-vm-bms). At the moment it is laying on my table and I dont use it. Just online and waiting for calls (see attachment -> 43 seconds screen on). It is a XIAOMI REDMI 3 PRO with global ROM. I found several users who have this problem with a MI BAND attached, BT on and various ROMs. I dont have this band and BT is switched off. My other phone, wich I use daily and has a smaller battery (3000 inspite of 4000), lasts longer than this "akku-monster".
Anyone here has any idea or any solution to get rid o this?
Thanks a lot ....
Walhalla
Same problem on freshly installed lineageos rom. I've had issues with a sensor (accelerometer akm)
I also have this problem on Lineageos. Did you happen to find any source of this issue?
Related
Hello all,
I have faced issues with the Wifi on my OPO since the day I got it. I researched a lot about it and found out that it's a problem faced my a lot of OPO users. Just to summarize the problem: The Wifi connects but after a few minutes (in sleep and sometimes even when the phone is in use) the data transmission stops. The Wifi icon shows that it is connected but you can't access the internet.
I had this problem on the 11s and when I read 12s had solved the problem I moved to 12s. But the problem still persists. Here are the things I have already done:
Wifi in sleep - Always
Restored factory settings
Installed app WifiKeepAlive
Installed 12s (15th Aug build)
I have seen a lot of posts but haven't seen a resolution in them. Appreciate if someone could help out.
I used to have a similair problem on my old One until it broke due to water damage. My new one doesn't have this however.
Perhaps a kernel issue? Try flashing a different one and see if the problems persist.
For some time now I own a Honor View 10. Back when I got it I paired my Sony Smartwatch 3 with the phone. I experienced that the watch sometimes loses connection to the phone and I had to restart the watch. That was not necessary with my old OnePlus 3. I thought it was the watch going bad because it had some other problems, too.
However, I recently got a Huawei Watch 2 and paired it to my Honor View 10. With the new watch, the problem still exists. Sometimes it loses connection to the phone without showing it. Sleep tracking with Sleep as Android does not get recorded or the watch app does not get the information my alarm is dismissed, notifications are still shown on the watch despite being already swiped away on the phone, new notifications do not get shown on the watch. It can only be resolved by turning off bluetooth on my Honor View 10 and turning it back on then. Sometimes I even need to reboot my watch.
Has anyone else experienced same problems on his or her Honor View 10 or has a smartwatch paired without any problems? For me it seems like the Bluetooth stack went bad on my Honor View 10.
I have exactly the same issue. My phone was fine on stock b130 but went wrong on subsequent updates. I believe the issue is a shared WiFi and Bluetooth stack. I installed Carbon ROM which works and doesn't suffer from this issue - the only problem i have is that I can't play my music collection from the external SD card with the stock music player or my normal one - have to use Poweramp or Rocket etc or copy files to the internal for system.
Sent from my AOSP on dragon using Tapatalk
I have similar issue.
My main concern is that my sleep tracker on the Smartwatch doesn't work when the phone goes to sleep.
So the sleep tracking is useless.
Did anyone else have this problem and now importantly a solution?
Sent from my BKL-L09 using Tapatalk
I have a FitBit... before i git used to doing it, I had the same issues with it.
wjhat i found was the battery manager was killing off the connection, set it to manual management and no issues since
I got problems pairing my Honor Band3 with my Honor V10 (AICP13.1) After 2 hours of trying i could suddenly pair my device with the tracker. For me i didnt succed to pair this device also with a Huawei AH100 (body fat scale)... Anybody an idea? I have de(installed) the Huawei Health app, deleted Bluetooth cache and data, no success. With an Axon 7 (also running AICP13.1) and a Huawei P10 (AICP13.1 also) i got connection within seconds... No problems to connect the View 10 to an Anker soundbox or an Samsung bluetooth keyboard....
borisku said:
I got problems pairing my Honor Band3 with my Honor V10 (AICP13.1) After 2 hours of trying i could suddenly pair my device with the tracker. For me i didnt succed to pair this device also with a Huawei AH100 (body fat scale)... Anybody an idea? I have de(installed) the Huawei Health app, deleted Bluetooth cache and data, no success. With an Axon 7 (also running AICP13.1) and a Huawei P10 (AICP13.1 also) i got connection within seconds... No problems to connect the View 10 to an Anker soundbox or an Samsung bluetooth keyboard....
Click to expand...
Click to collapse
I think it's issue with custom ROM rather than the watch.
May be you can capture logs and send it to the developer.
I would think that, too, but the joke is, that its exactly the same Rom on the Huawei P10 as on the Honor v10: I flashed the same romfile (for the beverley aka V10) onto the Huawei p10 (where the Huawei Body AH100 is definetly recognized by the health-app and runnig correctly) without any error (exept the ota app that leads to an error like this: "the ota app has stopped running") so i tried in the developer options ("networking") with setting different bluetooth AVRCP- Versions (1.3 -1.6) ...
borisku said:
I would think that, too, but the joke is, that its exactly the same Rom on the Huawei P10 as on the Honor v10: I flashed the same romfile (for the beverley aka V10) onto the Huawei p10 (where the Huawei Body AH100 is definetly recognized by the health-app and runnig correctly) without any error (exept the ota app that leads to an error like this: "the ota app has stopped running") so i tried in the developer options ("networking") with setting different bluetooth AVRCP- Versions (1.3 -1.6) ...
Click to expand...
Click to collapse
ROM is same but hardware is different hence there is a possibility of software compatibility issues.
But it would be very strange, that the hardware for that the ROM ist made (HonorV10) does not work, while the not really fitting hardware (Huawei p10) will work. Dont you agree?
borisku said:
But it would be very strange, that the hardware for that the ROM ist made (HonorV10) does not work, while the not really fitting hardware (Huawei p10) will work. Dont you agree?
Click to expand...
Click to collapse
P10 is Kirin 960 where as hv10 is Kirin 970 and Bluetooth versions are different hv10 has different and updated Bluetooth version than p10 hence it doesn't look strange to me.
Hi all,
Some users are reporting faults in the proximity sensor (it works when it wants ... sometimes during calls, sometimes during audios on Whatsapp/Telegram ...), there are cases in which they have changed the device and it continues to fail so we think it is more software failure than hardware, on the contrary also there are people who don't give any fault.
Does it happen to anyone?
Yes it's annoying but i think in the future will be patched out with updates it came out only on 5 November so they need time to push out some fixing updates.
Yes, we just have to wait for updates, I have the hope that this will be fixed
alvaroadlf said:
Yes, we just have to wait for updates, I have the hope that this will be fixed
Click to expand...
Click to collapse
They will because i think it's their first phone trying to reach best image quality and they focused everything on it but if more and more person reports this problem they will updated it because android 10 it will come to this device too??
Do you have this phone? with the same problem? ? Yes this device is quite new ...
Same wih my new Mi Note 10. It's quite annoying to make sure not to touch the display while calling. Although, during one in 10 calls, the proximity sensor works properly...Also I'd like to listen to voice messages though the call speaker, which does not work at all right now.
also fail for me... also fail on secret menu on telephon dealer ----> *#*#6484#*#* /14 --> proximity sensor test ---> FAIL.
With the last update (11.0.11.0 EEA) it no longer gives me problems, it has been working fine for a few weeks ????
i flash a global Rom on my CC9 Pro china and the Proximity Sensor never work i try it on call and try the Proximity Sensor test app its not work i think its because Google dialer on the global Rom so i back to china Rom with Mi Dialer
alvaroadlf said:
With the last update (11.0.11.0 EEA) it no longer gives me problems, it has been working fine for a few weeks
Click to expand...
Click to collapse
Just updated to that version, still not working.
Here is the solution!
Just disable the 'Raise To Wake' feature and problem will be solved. Simple.
Problem randomly solved (maybe with latest update), even with Raise to wake turned on.
With my Note 10 Lite latest global firmware is 11.0.8.0 and the problem is still present
+1 ! Also on a Mi Note 10 Lite ...
Very annoying!
+1 Mi Note 10 Lite... Dealbreaker for me, whats the worth of a phone if you cant use it for calls reliably!
For my diabetes I use the Freestyle Libre system to measure my glucose levels. It works using NFC, it should work using NFC. Sadly it only works a few times out of every 10 times I try. Sometimes the Oppo reads my glucose levels with no problem but usually it is just a miss and miss scenario.
Sometimes turning NFC off and on resolves the issue, sometimes powering the Oppo off completely resolves the issue, but several times the seemingly only option was to do a factory reset , reinstalling everything again, whereafter it works a few days, when the same problem reappears again.
As you can imagine, not something that makes me happy. Anyone out here who recognizes these NFC problems, and has a solution, or a way to make it work more reliable. Every other NFC operations seem to work okay, but this one is really bugging me, especially as it is important with regards to my wellbeing. i am using a fully updated Oppo Find X2 Pro.
On my previous phone, a Samsung S9+, i had no issues at all.
I'm so glad someone else also has this issue!
I was about to start a similar thread.
I have a lot of issues scanning my libre and it hardly ever works!
Can anyone help locate the exact location of the NFC sensor. I have watched Jerry rigs everything teardown but he did not mention where exactly it is located.
If someone could give me the exact grid number from this grid I've created I'd be very grateful!
CheopsChefren said:
For my diabetes I use the Freestyle Libre system to measure my glucose levels. It works using NFC, it should work using NFC. Sadly it only works a few times out of every 10 times I try. Sometimes the Oppo reads my glucose levels with no problem but usually it is just a miss and miss scenario.
Sometimes turning NFC off and on resolves the issue, sometimes powering the Oppo off completely resolves the issue, but several times the seemingly only option was to do a factory reset , reinstalling everything again, whereafter it works a few days, when the same problem reappears again.
As you can imagine, not something that makes me happy. Anyone out here who recognizes these NFC problems, and has a solution, or a way to make it work more reliable. Every other NFC operations seem to work okay, but this one is really bugging me, especially as it is important with regards to my wellbeing. i am using a fully updated Oppo Find X2 Pro.
On my previous phone, a Samsung S9+, i had no issues at all.
Click to expand...
Click to collapse
Is this issue still present on Android 11 for you? My issue still persists even on a factory reset
Have you found solution. I have the Same problem with OPPO reno 4 z
I have bought an Oppo Find X3 Lite this weekend. Same issue. Anybody has a solution already for the above? I imagined only NFC would be enough but why is it that the Oppo phone does not connect with the scanner? Any idea anybody?
I got the Android 11 update for Oppo Reno 10x Zoom, and my Freestyle Libre 2 Sensors stopped working with the phone. When I try to scan, the NFC service hangs and NFC will not work anymore untill phone restart.
Oppo told me it is a known problem and they will try to fix it in a new firmware update. God knows when.
THANX A LOT, OPPO! Now I have to carry around the ****ty Freestyle reader all the time!
Hi Everyone. I had this issue and called ABBOT. Got a fix which now works. In your phone settings go to the libre link app and clear the cache data. Restart your phone and voila it works!
I was testing aosp roms for my xiaomi poco x3 nfc and I found an error that apparently only I have, when it comes to playing online games with the wifi it goes with micro lag, only with the wifi with mobile data it works well
Does anyone have an idea why it will be? (I don't have that problem in emui roms)