yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] FeelThePoveR:
He probably isn't though as my second hand M7 that currently is running on It's third battery (I damaged one when I was taking it out) and second motherboard don't have and didn't have any of the problems you mentioned.
[One (M7) Original Android Development] jabia:
Slow Battery Charging

Hello All. Installed this rom last week and I'm loving it. Works smooth and I don't have the battery issues reported by others. THe biggest problem I do have however is very slow charging. I've tried installing the alternate kernel and toggled the USB fast charge option, doesn't seem to work.

I don't write code so I can appreciate the amount of effort y'all put into our EOL device. I'd deeply appreciate any help I can get.

Thanks!

PS: I'm on the 20170601 Build, running this kernel

cc: [MENTION=7694084]mchowdhury[/MENTION] [MENTION=5944557]alial04[/MENTION] [MENTION=5694169]camambeou[/MENTION]
[One (M7) Original Android Development] miki4:
@ samhhmobil:

What about the firmware you use? The latest one? GPE or Sense?
[One (M7) Original Android Development] Technobeat:
I have exactly the same problem on non sense based roms.

The phone randomly shuts off at about 20-40% battery.

The bootloader and recovery seem to report correct battery stats while the ROM constantly stays out of sync.

Since i use my M7 as a secondary device the battery has been replaced by a freshly manufactured one and can be ruled out as the source of the problem.

I have several friends who face the exact same issue on non sense based ROMs, mostly in Germany.
[One (M7) Original Android Development] jbradshw:
I also have this EXACT same issue, and I thought it was a bad battery for sure, and it's also the reason I finally decided to upgrade to a new phone from this one, thinking it was pointless to upgrade the battery in this old phone.
[One (M7) Original Android Development] icxj1:
Fast charge is in the charger, has to be a 2.1 amp. With fast charge capabilities. Phone just activates it.
[One (M7) Original Android Development] camambeou:
The issue slow charge is solved after some of reboot, fast charge on kernel just raising up the current charging amper, not fast charge function from soc. Our m7 doesn't have that function. But for now, changing the current charging amper is solution for our device
[One (M7) Original Android Development] samhhmobil:
That's it. With both of my M7's.

Even I switched there and back between StockROM and 12.1/14.1 without any other influence, The bad battery behaviour is reproducable.

With StockROM Voltage is ~4.1xx V with 100%, going down to ~3.9xx V with 80%, and staying even with ~3.7xx V when 10% or less.

With 12.1/14.1 Voltage is even ~4.1xx V with 100%, but it goes down rapidly, 3.7V with 95%, 3.5V with 80%, only 3.2V or less with 60% or 50%. When using the AOSP-camera-app then, it immediately goes down to 2.9V or less, and then the system crashes. After that, the offline charging starts at 0%, 2% or in the best at 4%.

No other apps installed, just the clean freshly installed ROM.

There MUST be something wrong in the power handling. Sorry...

My both devices:

- the first I bought newly at normal high price in electronic market in Germany, Dec'13 (no branding, nothing special),

- the second one bought "used", second hand, it was branded for O2-Germany.

Both got the latest bootloader firmware from HTC (spring 2015, AFAIR), together with the latest stockrom.
[One (M7) Original Android Development] Technobeat:
I observed the same values with the exact same setup, not only on my device ( as mentioned) but also a second device which i borrowed yesterday for the sake of it.

My guesses are the following:

A: The power handling part of the kernel is broken and wrong voltage values are used to power the phone.

B: The power handling part of the kernel is working correctly for non sense ROMs, but kernel battery stat reporting algorithms are broken.

C: The power handling and battery stat reporting of the kernel are right, but the values are being misinterpreted by non sense ROMs (broken pipe), causing premature shutdowns.
[One (M7) Original Android Development] samhhmobil:
The latest Sense from 5.0.2 (as it is/was supported by HTC in Germany)...

*** UNLOCKED ***

M7_UL PVT SHIP S-OFF RH

CID-11111111

HBOOT-1.61.0000

RADIO-4T.35.120.274.0718

OS-7.19.401.30

eMMC-boot 2048MB

Aug 5 2015, 18:01:23.0

So... (please excuse me) does anybody know, which is the latest GPE firmware? Where to get? How to install (if possible without erasing data)?

I expect here in the forum, but...
[One (M7) Original Android Development] maciclazar:
Go to this thread, find 5.1 firmware section and download "Firmware without stock recovery & Boot IMG". Just flash it in recovery without wiping anyting and you will have latest GPE firmware installed.
[One (M7) Original Android Development] samhhmobil:
Just two stupid question more...

- Is it flashable via "fastboot" too?

- Is the GPE firmware even running on "Europe"-GSM-Versions of the M7? (or am I in danger to brick the device?)
[One (M7) Original Android Development] maciclazar:
I don't know if you can flash it via fastboot. It is made to be flashed in recovery. Just make sure you are using official TWRP. You can freely flash it on your phone. It won't break your device.
[One (M7) Original Android Development] samhhmobil:
I'm sorry, didn't work.

I flashed the M7 cleanly and newly with TWRP 3.0.2-0 Recovery, and LOS 14.1 Custom ROM. I copied the file "6.04.1700.13_NoBoot_NoRecovery_firmware.zip" into internal storage, and... TWRP-install crashes!

What -- the hell -- am I doing wrong?
[One (M7) Original Android Development] Syntr@nic:
I flashed this firmware via CWM to 2 german O2-devices. Works great, no battery drain with 12.1 - not testet on 14.1.
[One (M7) Original Android Development] samhhmobil:
OK, folks, I got it! :) :good:

I made it via fastboot.

Booting into the bootloader, switching to FASTBOOT, connecting the USBcable ==> "FASTBOOT USB"

then on the PC-side:

htc_fastboot.exe oem rebootRUU <enter>

htc_fastboot.exe flash zip 6.04.1700.13_NoBoot_NoRecovery_firmware.zip <enter>

htc_fastboot.exe reboot-bootloader <enter>

and ... ... (tadaaaa) ... ... it works!

(but HBOOT is now back to 1.54, it was from european StockROM 5.0.2 on level 1.61)

Now we'll see, if THIS has influence to the power handling of 12.1/14.1.
[One (M7) Original Android Development] maciclazar:
I was wrong. Firmware should be flashed via fastboot and not in recovery :silly: Long time passed since I flashed it on my phone.

Anyway good thing is that you succeeded.

That 1.54 GPE Hboot is actually newer than 1.61 sense because Google updated our device longer than HTC did.
[One (M7) Original Android Development] miki4:
I cannot say that I don't have that problem because I have it, too. But until now I was pretty sure that it had to be the battery. My battery was replaced by HTC 25 months ago and about half a year ago the phone began to suddenly shutdown when you put some load at it when the charge level was at about 30% or less. Particularly when trying to take a photo. I was on stock-based ARHD 91 back then and it worked without trouble before. After setting up LOS14.1 about a month ago, the behaviour is still the same. adb getvar tells me my battery was "good" btw. Maybe on stock-based I had a problem which could be solved by a data wipe and now under LOS I'm having that obvious bug?

I'm located in Germany and also running latest WWE sense-based firmware (7.19.401.51).
[One (M7) Original Android Development] Technobeat:
Glad you made it, I'm excited for the results. The premature shutdowns on 14.1 have been driving me insane. Especially because the one m7 makes a great secondary phone.
[One (M7) Original Android Development] mchowdhury:
Hi Everyone, new builds are up!

M7 - https://www.androidfilehost.com/?fid=961840155545575724

M7vzw - https://www.androidfilehost.com/?fid=817550096634779985

Changelog:

- Latest LOS source

- More CVE Kernel Patches

Please report any bugs or issues. Also can I get confirmation if the speakerphone bug and the slow battery charging bug are present in these builds?
[One (M7) Original Android Development] samhhmobil:
My first impression looks good... after 14hours (with some work, not only idle) 52% and 3.8V (AOSP-camera works correct, no voltage breakdown). So let's wait for the next 14 hours...

It seems, that LOS 14.1 works good with GPE firmware and VERY bad with european HTC sense firmware from the latest stockrom.
[One (M7) Original Android Development] saturday_night:
Sure like postet nearly half a year ago ;) Edited that thread and addded battery problems.
[One (M7) Original Android Development] saturday_night:
Clean install and speakerphone bug is still the same.
[One (M7) Original Android Development] mchowdhury:
Are you on the GPE firmware? Also are you experiencing the battery bug that others have reported?
[One (M7) Original Android Development] haykweb:
What about bluetooth

Fm radio

Camera 60 fps recording ?
[One (M7) Original Android Development] miki4:
The firmware in that thread is 6.04.1700.13 and is not the latest one. Also it is only the OTA package and not a full firmware. You would need to flash a full firmware package or RUU to be completely GPE if you come from a sense-based firmware. Then update to latest OTA to be up-to-date.

The latest GPE RUU was 5.11.1700.3 (Android 5.0.1).

The latest GPE OTA and firmware is 6.04.1700.19.

The OTA from 5.11.1700.3 to 6.04.1700.06 firmware-wisely only included radio.img (modem firmware) and hboot_signedbyaa.img (bootloader). The rest are system files and boot.img which are rom-specific (you know what I mean, kernel and so, no real "firmware") and recovery.img which we usually don't want anyway. Every following OTA up to the latest one only included hboot for firmware.

So, what you exactly need to do is flash the 5.11.1700.3 RUU or correspondent firmware package with

every

relevant firmware file, then flash 6.04.1700.06 OTA to get the latest GPE radio.img and then flash 6.04.1700.19 to get the latest hboot. This way every part of the firmware will be updated to the latest GPE version. Maybe someone could build an all-in-one package which includes all the firmware parts in their latest version.

What I noticed is that even though it is a RUU the GPE 5.11.1700.3 RUU does not include firmware parts like touchpad or infrared firmware. However, I guess they are the same as in the sense firmware so no real issue.

Cheers

EDIT:

This guy offers a full 6.04.1700.19 firmware package. I'll check that.

https://xdaforums.com/showpost.php?p=67457491&postcount=10666
[One (M7) Original Android Development] saturday_night:
Yes GPE FW and i dont use this as my daily driver just tested your latest build for a few minutes so cant say something to the battery problem.
[One (M7) Original Android Development] miki4:
Just checked the latest GPE 6.04.1700.19 firmware package from the link in my post above.

radio.img is the latest GPE one (from OTA 6.04.1700.06)

hboot_signedbyaa.img is the latest GPE one (from OTA 6.04.1700.19)

adsp.img is the latest GPE one (from RUU 5.11.1700.3)

sbl*.img are the latest GPE ones (from RUU 5.11.1700.3)

splash1.nb0 is the splash screen. sp1.img in RUU 5.11.1700.3 is another format but probably the same.

tz.img is the latest GPE one (from RUU 5.11.1700.3)

--rpm.img which contains i.a. voltage tables is NOT the same as the one in RUU 5.11.1700.3. It actually derives from the GPE 3.62.1700.1 RUU (Android 4.4.2) and should be replaced with the rpm.img from RUU 5.11.1700.3 so you get the latest one.--

Correction: rpm.img IS the latest GPE one (from RUU 5.11.1700.3). I made a mistake previously. I compared the files to a non official RUU which included an older rpm.img.

--Besides the firmware package contains cir.img (infrared), tp_SYN3202.img (Synaptics touchpad) and rcdata.img which are neither contained in the latest GPE RUU nor in the following OTAs.--

Correction: They are all included in the official RUU 5.11.1700.3.

Comparing the package with the latest WWE Sense 7.19.401.51 firmware you find out that:

cir.img and tp_SYN3202.img are the same in both packages. rcdata.img is different. You can open it with notepad and see some radio config data. EDIT: If someone has reception issues it could be worth a shot to delete rcdata.img from the package or replace it with the rcdata.img from WWE Sense 7.19.401.51 firmware before flashing it to the phone as it could make a difference in different networks or places (HSDPACat=24 instead of HSDPACat=14 as an example). Don't brick your phone though, I'm not responsible.

Every other file is different between the GPE and Sense package. Additionally the Sense package contains a pg2fs_spcustom.img and another touchpad firmware tp_HMX852XD.img.

Here you can find some infos on the different partitions on HTC phones: https://docs.google.com/spreadsheets/d/1wsL4zfECK8nWQnuS8uoQttajkQB9vYYIlpJGnUu99I0/edit#gid=0

--I will build a custom firmware package with a combination of the latest firmware parts.--

Correction: Not neccessary as there is everything up2date in Slim Jim Guy's package.
[One (M7) Original Android Development] maciclazar:
Thanks for the info. I'll check this tomorrow. If you make custom firmware please share it here.
[One (M7) Original Android Development] mchowdhury:
What's the issue with Bluetooth and Camera 60fps recording? Are you on the GPE firmware?

The FM radio issue is a known issue that we have been unable to fix. If you or someone has knowledge on how to help fix the FM issue, please refer them to us.

---------- Post added at 06:41 AM ---------- Previous post was at 06:32 AM ----------

Thanks for all this info. Is there anyway that you can also build a firmware package derived from the GPE that will also work on the M7vzw? (remember the M7vzw was never a GPE device) This would be immensely helpful because the GPE firmware fixes a lot of issues with Android 6+ ROMs.

Here's a link to the current M7vzw sense firmware: https://xdaforums.com/showpost.php?p=46506621&postcount=2
[One (M7) Original Android Development] Slim Jim Guy:
All files in the firmware package are the latest ones, so check again the rpm.img in the signed 5.11.1700.3 RUU and compare it with the latest package, because it's the same.

The RUU contains the IR, TP, etc. images, so you probably used a RUU created by someone else, but I have the necessary files from original sources, so it should be okay in every aspect.

You can find everything on my AFH account.

Complete firmware (without boot.img and recovery.img): M7_UL_GPE_Firmware_6.04.1700.19.zip

Signed 5.11.1700.3 GPE RUU: PN07IMG_M7_UL_L50_STOCK_UI_MR_Google_WWE_5.11.1700.3_LRX22C.H3_Radio_4T.30.3218.21_10.33I.1718.01L_release_403339_signed.zip
[One (M7) Original Android Development] miki4:
Not neccessary anymore. Slim Jim Guy's firmware package from the link in my post and his post is up2date! :)

I'm sorry, I cannot do this. It is possible to mix the individual firmware parts in a .zip but to create a GPE-firmware for M7vzw you would need to disassemble the individual firmware parts which differ from M7_UL, compare and rebuild them with the neccessary changes. Way easier said then done.

Thank you much, you are right. I had a tampered RUU which I thought was original. I wondered why the date stamp of rpm.img in the tampered RUU was older than the one in the foregoing RUU and my conclusion was that they must have reverted to the previously used rpm.img in the latest RUU. But thats crap. Everything clear now. ;):good:
[One (M7) Original Android Development] maciclazar:
Ok, thanks. I upgraded to this firmware and for now everything is good.
[One (M7) Original Android Development] n0j0e:
This is the right one for my m7_ul S-On?

https://xdaforums.com/showpost.php?p=67457487&postcount=4921

Send with much love & Android.
[One (M7) Original Android Development] plazma247:
I would also like to know if this is correct, im currently running a converted s-on phone which has got the 1.61 htc hboot and the original htc 4T.35.3218.16_10.33Q.171801L radio...

From my understanding to flash hboot and rru (radio) you need to have s-off (if someone can confirm this is the case for both).

Also am i right in understanding that its the hboot and radio thats important from the GPE to make it stable for later roms 6.x and above.
[One (M7) Original Android Development] FeelThePoveR:
Radio can be flashed separately through TWRP, for HBOOT and firmware you need to be S-OFF, if you want to flash versions from different CID. HBOOT also cannot be downgraded when S-ON.
[One (M7) Original Android Development] plazma247:
Thanks for replying, so to answer my other question is it the Radio or Hboot or both thats essential to be flashed to make later roms stable?
[One (M7) Original Android Development] FeelThePoveR:
[MENTION=511296]plazma247[/MENTION]

Radio could potentially help, HBOOT version doesn't matter much, firmware is the most important.

---------- Post added at 06:14 PM ---------- Previous post was at 05:56 PM ----------

You can't flash GPE firmware on Sense version of the phone with S-ON (as CID numbers don't match and it won't let you flash it). You also can't flash unsigned files with S-ON, so it probably won't work.
[One (M7) Original Android Development] plazma247:
Again thanks for replying, i will flash up the Rom n0j0e suggested here:

https://xdaforums.com/showpost.php?p=67457487&postcount=4921

As the radio is later than i currently have and then flash up to this, really happy if i can still avoid having to pay the s-off tax :)
[One (M7) Original Android Development] FeelThePoveR:
Don't flash that, as it probably won't work. I will attach TWRP flashable radio in a moment.

EDIT: http://www12.zippyshare.com/v/Dpfqx1IO/file.html
[One (M7) Original Android Development] plazma247:
[MENTION=5078473]FeelThePoveR[/MENTION] Thats awsome thanks, your radio flashed fine thankyou :)

I then flashed over the top: https://www.androidfilehost.com/?fid=24591023225176888

From here: https://xdaforums.com/htc-one/development/rom-google-play-edition-lollipop-v1-00-t2963927

Which flashed and does not appear to have a radio, but was also a GPE-5.1_LMY47O.H19 build (which was later than mine) and i guess a good idea to also do first?

Just letting it boot so i can take a nandroid backup just in case and then i will flash upto Lineage OS 14.1 :) thanks again for your help man.

Small question, i see that lineage have recently (i think read a lot of posts yesterday) started to provide the rom without root, is this the same for the builds here, or do i need to flash super su after? I guess the best thing to do is to boot and find out...
[One (M7) Original Android Development] maciclazar:
Rom is not rooted by default. You can flash lineage superuser from lineage official site (ARM version), magisk superuser or supersu. I personaly prefer supersu.

Note: everytime you flash new build you will need to reflash superuser again or you will lose root.
[One (M7) Original Android Development] plazma247:
Ok so no root, so i just flashed over super su :)

One question, i sorta miss the beats audio for speaker play back, is there an option for that anything similar that would be compatible with the rom? (viper maybe?)
[One (M7) Original Android Development] FeelThePoveR:
GPE-5.1_LMY47O.H19 is just a rom without firmware so flashing LineageOS will overwrite it. Unfortunately currently it seems there is no way to change firmware from Sense to GPE without S-OFF.

---------- Post added at 09:01 PM ---------- Previous post was at 08:58 PM ----------

Here's viper:

https://xdaforums.com/apps/magisk/module-viper4android-fx-2-5-0-5-t3577058

You can also check other ahrion modules out.

I'm currently using AINUR Sauron + ViPER FX 2.5.0.5 + AM3D for audio (although I don't recommend AM3D for speaker playback).

AM3D may need permissive SELinux (with Magisk 12 it didn't need it, but with Magisk 13 it's kinda wonky as it still wasn't updated for it)
[One (M7) Original Android Development] plazma247:
[MENTION=5078473]FeelThePoveR[/MENTION] - AINUR SAURON Looks pretty awesome, so tried that first, installed on its own, but i cant hear any difference what so ever with my old ears, so i removed and tried viper1.4 from your post, Also tried the version from the main site : http://vipersaudio.com/blog/?page_id=48 But but tell me i have to install the driver over and over again i can see that audio_effects.conf gets moved to .bak however it never works..

I also tried the version from here: https://xdaforums.com/android/general/guide-how-to-install-viper4android-t3485827 same thing. Ive seen some places suggest that busybox is required, however if this was the case how would it manage to create the bak file?

On the GPE, my device is S-ON and ive been running a GPE rom for many months now since i got the phone, i forget which one exactly, as i remember i just unlocked it with htcdev, flashed twrp and wiped the system partition and flashed a GPE rom, so the only thing ive not been able to do was flash hboot or (i though radio, but you proved this was possible earlier) and to supercid, however unlock codes are stupid cheap should i need to bumb it to another provider its not worth it... cheaper than paying s-off tax.

Question the GPE rom i had before had a neat feature that would allow you to double tap the screen to wake, currently ive set the volume rocker to also wake, as the screens amoled its possible, not sure if it impacts the battery life tho... i guess i should go a day first and see what the power life is like without out it, i guess i could get use to pressing buttons again.
[One (M7) Original Android Development] miki4:
I'm not sure on this. It would make sense but the file [MENTION=8300892]samhhmobil[/MENTION] flashed to his phone in this post only contained the GPE hboot and that seems to have cured the problems for him although coming from a sense-firmware so the hboot is actually the only GPE firmware part on his phone now.
[One (M7) Original Android Development] FeelThePoveR:
It didn't only contain HBOOT, even in the GPE topic it is written above the link that this was firmware (OS line in fastboot) HBOOT is just the bootloader - it makes our phones boot, but the firmware part is what makes it work properly.

Besides look at the getvar all he posted and the screenshot of the fastboot later - OS changed from 7.19.401.30 to 6.04.1700.13 (which is actually newer)
[One (M7) Original Android Development] plazma247:
[MENTION=4740462]miki4[/MENTION] and [MENTION=5078473]FeelThePoveR[/MENTION] im s-on, so unless i fork out for s-off im stuck on hboot 1.61, but like FeelThePoveR its just the bootloader, surely the important stuff is whats in /system and the radio?

Ok just checked on FastBoot and it says os 7.18.206.51
[One (M7) Original Android Development] FeelThePoveR:
The really important stuff is on locked-out partitions that you wont be able access normally.

And...

Here's a kernel with DT2W option (it needs to be enabled on kernel adiutor)

https://xdaforums.com/htc-one/development/kernel-current-kernel-s2w-dt2w-l2m-l2w-t3568353

As for the Viper4Android unfortunately I can't help you as I switched from SuperSU long timer ago to Magisk. But basically there are lots od "methods" that supposedly fixed Viper install, but most od them didn't work for me. When I was still using SuperSU I remember that I used guitaredhero version that was posted somewhere in the main Viper4Android topic (it was also on his afh do you may try to google that).