yashsingh1/xdaforums huggingface dataset:
[Moto Z Play Questions & Answers] jatinkhatri:
BTW.... Who has successfully locked bootloader on MZP ..?

Anyone !!!:laugh::laugh:

It's not possible to relock bootloader ...As there is no signed firmware available ......
[Moto Z Play Questions & Answers] Jimi Mack:
Yes they will know... I just put in for a warranty exchange last month after having issues with it. Yes it was unlocked and had a custom rom on it when I returned it. They had a New Play in my hands within 2 days. They knew the phone was unlocked, I documented it on my warranty claim and they still approved and sent out a replacement. Thank you Moto.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Imperium:
Hey i flashed my device with the battery at around 80%.

after the flash it was 100%...

so this means i just lost 20% of my capacity? how do i fix this?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Tec1106:
I don't believe you have lost capacity. It's only your gauge that's slightly altered. If you recharge your device fully(and about an extra 30min) you should have the regular capacity :)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] UnicornKaz:
How could going from 80% to 100% equate to a lost ??? :confused:

it's posible that you'd gained the extra charges while the flashing process was going on ( because it was plugged in ?? ) ... if it wasn't ... no idea why :cool:
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] shogunmark:
If i understand the post correctly they are equating am 80% to 100% a loss for 2 reasons:

1. because he would have lost charge while flashing due to the massive battery drain.

2. because now he is stating that his 100% is really only 80%

but i would probably just leave it charge overnight and you should be fine, the gauge just sounds to be off, it shouldnt be a true loss (unless the battery is bad)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] BUMP THAT:
Is there any other way to sync the battery with the device? I been trying a full discharge then charge.

I am using a mugen extended 3000mah battery and at 15% 10% and 1% it will stay there for some time before it starts to go down or turn off completely if it is reaches less than 1%.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jym04:
I don't think you've lost capacity.

I believe you just did a quick check before flashing (and it was already charging before you started right?), and the battery gauge wasn't updated. I had this a couple of times while recharging. I take a quick look and think "this is gonna take another half hour". Five minutes latter I check and the charge led is green again.

Sometimes the battery metter lags a bit, you have to check it again to be sure when charging.

At least it happens to me.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] shogunmark:
a few cycles of full charge and discharge should put the battery meter in check...
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] BUMP THAT:
Alrighty. I have done three so far. It has gotten better then the first time I got it. But its not perfect.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Imperium:
is it safe to discharge it to 0% so that it will shutdown? or what?
[Lenovo Phab 2 Questions & Answers] silvers01:
Does anyone know how to update the android version of our phab 2? I got mine with android 6 m. I tried the system update but it i dont know what did it update? Firmware? I thought it will update the android version from 6 to 7 ..wth

So does anyone here got their phab 2 an update for android 7?
[Lenovo Phab 2 Questions & Answers] martin2dn@gmail.com:
According to this site http://www.theandroidsoul.com/lenovo-android-7-0-nougat-update/ there´s no hardware support found for Nougat release. Can someone confirm this?
[Lenovo Phab 2 Questions & Answers] sushil888:
Lenovo officially said NO. So .,....
[Lenovo Phab 2 Questions & Answers] sodade21:
ARCore from google that it gonna replace tango will work on every phone above android 7... so that means,even if phab2 pro was ment to be the first AR Tango will left out of all these while it has extras on its hardware for exactly that reason. At least lenovo should put the kernel source and whatever else needed so some brave XDA dev can make some custom rom or bring somehow the nougat in the phab2 pro... at least Lenovo let XDA do your job!
[Lenovo Phab 2 Questions & Answers] Sendog2010:
I don't think these phones will update to 7. At least not yet. Operating speed is only 1.3 quad, personally I'm happy with its performance.
[Lenovo Phab 2 Questions & Answers] mysteryDave:
Disappointing these are stuck on Marshmallow and can't get Nougat or Oreo.
[Lenovo Phab 2 Questions & Answers] shinhosuck1973:
Any custom rooms for this device?
[Lenovo Phab 2 Questions & Answers] Reshan Kariyawasam:
Lineage OS 14.1 Lenovo Phab2 PB2-650M

Finally Lineage Os 14.1 ported for Lenovo Phab2 PB2-650M by ARRAKI.

http://lenovo-forums.ru/topic/24812-lineage-141/?page=1
[Lenovo Phab 2 Questions & Answers] tegmis:
but there's not link to dowload is broken. And have a issue with the band mobile. Do u know of some rom available to this phone. I cant find anything.
[One (M9) Q&A, Help & Troubleshooting] emjay911:
Hello

Since the Nougat update there has been a few noticeable and annoying issues.

So this issue has been bothering me since I have updated to Nougat thru system update a few months ago.

Suddenly the weather widget is not updating to current location and always shows "No Location Available"

I have to manually update the location but than again it goes back to showing "No Location Available"

Another issue is that

I am not receiving Gmail notifications at all and also some other apps I have noticed that their notifications either stopped all together or are very very delayed.

Has these issues not addressed by Google?

I am on Android version 7.0 software 4.28.401.3 -- which I got today only thru system update

Regards
[One (M9) Q&A, Help & Troubleshooting] shivadow:
Do you have location services disabled?.. Could be worth checking your google settings.

The weather widget "should" update if you get a location lock with full GPS enabled. If you think you might not be getting a gps lock then run google maps while outdoors (stand on you doorstep or go out to the garden) and wait for it to locate you then refresh the weather app.

Beamed in by telepathy.
[Lenovo Zuk Z2 Pro Questions & Answers] Alexiaomi:
Zuk Z2 Pro with MoKee 71.1 nightly OS gives bad error. There's no connection with the camera anymore. What should I do? Read on ZUI fans Europe that I should flash fastboot ZUI to fix it. But I want to use MoKee. Also want to try LineAge OS, but install did not succeed.

Any solution

Thanks,

Alex
[Lenovo Zuk Z2 Pro Questions & Answers] flyfire04:
The "no connection error with camera" error of the official mokee nightly is not the "ominous" camera bug. The error is shown bc the camera in this ROM (in every camera app) is not yet capable of shooting pictures with flash.. Just disable flash in camera settings. Reboot and it should work again.
[Lenovo Zuk Z2 Pro Questions & Answers] luxorjd:
If you update camera to 4.0.13 (or something like that) remote update, then camera works again!
[Lenovo Zuk Z2 Pro Questions & Answers] Alexiaomi:
Which camera app do you mean? ZUI app? I use Open Camera, but like flyfire04 says, no camera app works on MoKee rom.
[Lenovo Zuk Z2 Pro Questions & Answers] luxorjd:
Nearly all camera apps I tried worked in mokee.

But the camera from open gapps is updated via playstore and do not work after update. Remove update and it works again.
[Lenovo Zuk Z2 Pro Questions & Answers] Alexiaomi:
I will try that, thank you!
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] Necronomynus:
Hello xda-community!

First of all, thank you for your great material, guides and information you are offering here!

Now to the point:

I've flashed my Kindle Fire HDX 7" (Thor) with TWRP 3.0.3-1 with the LineageOS 14.1 and everything was great the first day.

After the night with my Kindle plugged in to AC charger I recognised my device turn off overnight. Was a little bit tricky to turn on (60s power-button reset) again.

No issues while using it in day-time. This time over night I didn't plug it in.

The next morning I saw the device rebooted and got stuck in the grey kindle fire bootloader screen. I reset then booted to Recovery TWRP showed me 14% battery left.

I've pluged it in AC charger and booted to Lineage. Lineage then showed me 100% battery charged. Even when I unplugged the kindle form power it remains 100 % charged and says its connected to AC power.

After this I let my Kindle run empty. The battery indicator in Lineage still remained 100%. The OS didn't shut down when power was low. In the end the screen was showing dark spots and was flashing 2 seconds to white and then the device was dead.

I've plugged it in again. Since this Lineage still shows 100% charged. If I boot to TWRP the battery indicator in the status bar disappeared mysteriously.

adb shell dumpsys battery brings up:

adb shell dumpsys
Current Battery Service state:
AC powered: true
USB powered: true
Wireless powered: false
Max charging current: 0
Max charging voltage: 0
status: 2
health: 2
present: true
level: 100
scale: 100
voltage: 0
temperature: 424
technology:

I've also flashed the LinageOS again and I've tried older versions of TWRP still the same (TWRP no battery indicator; Lineage 100%)

Also in CM13 it shows 100% charged. The kindle became very unstable and can only be run plugged in now. It seems the battery isn't chrarging at all any more.

What can I do to use the battery normal? Should I replace the battery?
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] Necronomynus:
I've also saw that the folder /sys/class/power_supply/ only contains 3 subfolders:

smb349_ac
smb349_usb
usb

I'm not sure but it seems to me that the folder for my battery is missing. Anybody have an idea?
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] Necronomynus:
Can please someone post the "normal" view of this class? Thank you
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] Necronomynus:
OK folks, seems my battery has found its way back to life.

The class now looks like this:

bq27x41
smb349_ac
smb349_usb
usb

And the bq27x41 subclass contains all the info of my battery I could wish for. Charging and discharging behaviour seems pretty normal at the moment.

adb shell dumpsys battery now brings up:

ads su shell dumpsys
Current Battery Service state:
AC powered: false
USB powered: false
Wireless powered: false
Max charging current: 0
Max charging voltage: 0
Charge counter: 0
status: 3
health: 2
present: true
level: 86
scale: 100
voltage: 4105
temperature: 358
technology: Li-ion

Don't ask me what how I've exactly repaired my device. That's what I did:

flash kindle fire OS recovery system data boot with TWRP

flash vunarable bootloader and unlock it

flash TWRP 3.0.2-2 again

wipe everything also format data

flash CM13 and GAPPS

reboot/reset

let device in TWRP turned on and connected to AC power for 24h

wipe and flash Linage14. 1 and GAPPS

used my device normal while plugged in all the time for 3 days. When I'm not using it, I shutdown OS and unplugged my device. Then I've always powered it on again while connected to the AC-charger

after OS was running 2h I've unplugged my device from AC and now the battery is working again
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] Necronomynus:
Damn. I've booted to TWRP to see if the battery indicator is back but it was not. So no I've the same status again like in the OP.... No battery indicator in Lineage14. 1, too. I don't get it what happened.

Can someone please explain how and when this class is initialised by Android and when the objects (power_supply/bq27x41) are created. How can I trigger this?
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] fhh2626:
Met the same problem... I ran out of the battary and charged. After I rebooted, the battery indicator never worked again.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] fhh2626:
Have you finally solved the problem? I reflashed Lineage and also tried CM13, but the problem remained. I plan to try the official OS to see if it works.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] DB126:
Thoughts:

- downgrade TWRP to 3.0.0-1 (yes, this seems unrelated; eliminating variables)

- try Fire Nexus (KitKat build) which shares the largest common base w/stock

- be sure to wipe system and data partitions prior to each attempt

Obviously Nexus is not a permanent solution; just trying to drive to root cause)
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] fhh2626:
I tried Nexus..doesn't help. thanks anyway
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] Necronomynus:
no I have not found a solution yet. Still facing the same problem sometimes it works for some hours or days in LineOS and the suddenly the battery status is not updated anymore (e.x. at 55% battery doesn't change even when I plug in) after reboot it shows imediateley 100 % for some days) Then even while operating LineOS and without need of a reboot the indicator suddenly is working again.

It would be really helpful to know which event and which command the kernel issues to refresh/rebuild battery information from the smb349 (battery power-management IC) via i2cget command.

While using the Kindle without working battery indicator (I can still use it normally, even unplugged now) I just have to remember myself how long I've used it unplugged not to run out of battery unexpected.

While the working battery indicator days I've run "Accu Battery 1.1.7c" App which reports good health status and about 93% of the design capacity (4550 mAh) of my battery left

I always power it off and unplug it in phases I'm not using it for longer time (e.x. overnight). This improved the stability a lot.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] DB126:
Curious - which build of TWRP do you have installed? Obscure long shot but updgrading/downgrading might yield some insights. Does battery status show correctly from the recovery UI?

Another (albeit riskier) option is to reflash the vulnerable bootloader.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] Necronomynus:
Thank you Davey for trying to help us.

I'm using TWRP 3.1.0.0. At the periods the indicator works in LineageOS it also works in TWRP and vice versa if not then both not.

I've also tried TWRP 3.0.2-2 which shows the same behaviour.

I've upgraded to the LOS 02. May release today. Maybe the indicator works better now. I will let you know.

In the Folder /sys/class/power_supply/

The bq27x41 is a link to the object:

/sys/devices/f9967000.i2c/i2c-0/0-0055/power_supply/bq27x41

This object and all it's sub objects are these

/power/autosuspend_delay_ms
/power/control
/power/runtime_active_time
/power/runtime_status
/power/runtime_suspended_time
capacity
charge_full
charge_full_design
charge_now
charge_now_design
current_now
device.lnk
energy_avg
health
manufacturer
status
subsystem.lnk
technology
temp
type
uevent
voltage_now
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] Necronomynus:
The problem still the same in the LOS 14.1 May release. But overall performance getting better now only approx 25% of usage time of the device my battery indicator doesn't work.

What is the risk with flashing the vulnerable boot loader? Do I have to unlock it again?
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] DB126:
I find it interesting the battery indicator also does not work when booted into a custom recovery (TWRP) which operates independently from whatever lives in the system partition (eg: LinOS).

A refreshed bootloader would likely need to be unlocked; depends where keys are held (above my wage grade). Risks include potential result data loss and/or bricking the device should the flash goes bad; a twiddled bit can yield a very bad day at the office. I view the last two as unlikly but would be remiss in not mentioning the possibility.

[MENTION=5828306]draxie[/MENTION] - thoughts?
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] draxie:
genie in the battery...

Independent is a relative term in this case, I'd posit.

Based on my quick read of this thread, that battery

appears to enter some weird state from time to time,

gets stuck there for a while, only to get "unstuck" for

no obvious reason after some random period in limbo.

The only firm conclusion I could make is that neither

LineageOS nor TWRP have the chops to systematically

pull the battery out of limbo. In other words, when it's

stuck, it simply doesn't show up in either... (Now, why

LineageOS decides to show a missing battery as fully

charged is beyond me, but that's beside the point.)

To me, that implies a strong dependence in how each

'partition' will behave, since that appears to be fully

determined by the state of the battery.

The more interesting question is what triggers the limbo.

Based on the first few posts, I had the theory that Lineage

was clearly to blame (as I haven't found any mention of

the "good state" going bad while in TWRP), but then post#5

made me less sure, as it gave the impression that booting

into TWRP _when_everything_worked_ in Lineage caused

the battery to go missing again...

BTW, what I find *most* curious is that 'dumpsys battery'

output in post#4. If that was really generated from 'adb'

(as opposed to a terminal emulator on the device itself),

'USB powered: false' is decidedly not what I would expect.

Here's the output of the same command on my test Thor:

[B]root@thor:/ # dumpsys battery [/B]
Current Battery Service state:
AC powered: false
USB powered: true
Wireless powered: false
status: 2
health: 2
present: true
level: 87
scale: 100
voltage: 4175
current now: 606000
temperature: 256
technology: Li-ion

I attribute the fact that the fields are different to me running FireOS,

but it may also be indicative of different drivers/device definitions.

Also the discrepancy in the temperature readings (256 vs 358) may be

a cause for alarm (depending on the ambient temperature there at the

time; I don't have a thermometer, but I'd guess it's around 23-25C here).

If you mean flashing the very same vulnerable bootloader to the aboot

partition anew by a "refreshed bootloader", then you wouldn't need to

unlock again (i.e. the device "stays unlocked"), unless you flash another

version in between. On the other hand, I'm not quite sure what you

expect to gain from flashing a bit for bit identical image... (if it wasn't

the device wouldn't even boot; the bootloader is also signed).

Instead, I'd suggest to test running with FireOS for a few days (there's

no way to get closer to stock, if you can stand it) and see if the battery

still behaves erratically. If so, you should probably consider swapping it

(although, the root cause could easily be a _related_ HW component

and not the battery itself). I have a hard time seeing this as a pure SW

issue in LineageOS, since we should have seen plenty more reports (or,

at least, more meetoos on this thread). I've tested Lineage briefly on

this test Thor and haven't seen anything similar.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] Necronomynus:
Thank you draxie for you're precise analysis and help.

I'm still operating LinageOS. It's very stable now.

I don't know what sends the battery object to limbo but it seems like I found a solution to get it out there:

I've found out after the battery indicator stayed in limbo for approx. 10 days.

I've always used a USB-Charger with only 500mA through out this period.

But recently I have incidentally used another power source (Anker 28W Wall-Charger) with a original Kindle USB-Cable. After booting (because battery run totally empty before) it started with 5% battery indicator and its behaviour normal.

In the beginning (of this thread) I often changed chargers and cables (1 A Apple charger, USB-charging via Laptop, 2 A "China-noname" charger, 1.5 A Sony Charger) so it would explain the random behaviour.

So I have the theory it all depends on the charger and USB-cable to cause this issue with my device.

However I will try with the weak 500 mA charger if I can send the battery indicator to limbo with it. After this I hope I can confirm you that the strong charger and original cable can recover the battery indicator.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] draxie:
Thanks for the info!

Chargers having a short-term effect sounds plausible to me.

And, so does the propensity of aging batteries to act erratically.

I guess we could be looking at the combination of both....

How often do you need to charge your Kindle?

My 4-year-old Apollo is having trouble keeping up with my

usage patterns. Some days I have to charge twice.

And, the battery indicator does behave _somewhat_ odd,

when charge is around 10% (it can jump back up to 25%, when

going from idle to heavy use [why?!?], or it can drop dead

from 7%; but sometimes it's still ticking with 0% ;)).

Recently, it has also started to complain about the stock

charger that came with it as being "low power"...
[ZTE Axon 7 Questions & Answers] n1234d:
After the nougat update, taking a screenshot is no longer instant like it was on 6.0.1 You need to press and hold power down for a second before the action is triggered. I happen to take a lot of screenshots, and find it annoying/inconvenient. Does anyone else share the same?

Is any dev here able to port the screenshot utility from 6.0 to 7.1.1?

[MENTION=3044858]DrakenFX[/MENTION] [MENTION=4911249]Unjustified Dev[/MENTION] any inputs? If any files are needed, I'm still on 6.0.1 and can help you with those.

Others feel free to chime in as well!

Thanks.
[ZTE Axon 7 Questions & Answers] aLexzkter:
It's not lag. Now it required to press and hold both buttons.

I have no idea why they changed this but on LineageOS it's the same.
[ZTE Axon 7 Questions & Answers] n1234d:
I know that it's not lag. On 6.0.1, it was modified by ZTE to not require to press and hold. Just a short press of both the buttons would trigger a screenshot, which made it extremely convenient. I want to have the same functionality on 7.1.1. I don't think it'll be a big task to change that, but I don't really know how to
[ZTE Axon 7 Questions & Answers] gpz1100:
Just enable the 3 finger pinch setting in settings/gestures.
[ZTE Axon 7 Questions & Answers] n1234d:
It isn't convenient. Power+volume down is a perfect one-handed gesture.
[ZTE Axon 7 Questions & Answers] n1234d:
Is it not possible at all to change the long-press delay for screenshots? It has really been bugging me, after the convenience on 6.0.1
[ZTE Axon 7 Questions & Answers] xzolteu:
Its all good with B02 7.1.1.
[ZTE Axon 7 Questions & Answers] n1234d:
A2017G?

Interesting. I'm on the A2017U
[ZTE Axon 7 Questions & Answers] brian88:
I cant find the setting you said. Could you please more details?
[ZTE Axon 7 Questions & Answers] strifej:
It looks like they removed the pinch to screenshot gesture from U Nougat??
[ZTE Axon 7 Questions & Answers] Aj-jss:
I've still got it on 7.1.1(MiFavor4.2) A2017.

Also I just need to press both buttons to take a screenshot not holding them.
[ZTE Axon 7 Questions & Answers] strifej:
I'm also running 7.1.1, MiFavor 4.2.15. But 3 finger pinch doesn't do anything.

In Marshmallow they used to have a Settings menu for the pinch to screenshot feature. That has been removed entirely. Searching for screenshot has no results in the settings search.
[ZTE Axon 7 Questions & Answers] Aj-jss:
Searching doesn't work. You should go to Settings/Features/Gestures and Motions/three-finger pinch
[MX Player] Thirumalai.K:
MX Player team is very happy to announce that we are now adding “AC-3” audio support in our latest version of the app (i.e. MX Player v1.8.17 & MX Player Pro v1.8.16) in most of the regions.

If you have video files with “AC-3” audio, you can now play it without using any third-party / unofficial custom codecs…!

There are no extra efforts required on your end. Just relaunch the app again with working internet. Once, MX Player configuration is updated on your device, it will automatically start working again…!
[MX Player] P€πtex4869:
Thank you very much
[MX Player] andgtr08:
Great News! Thank You! :)