yashsingh1/xdaforums huggingface dataset:
[HTC One S] pavel.bosco:
yes, I'm also sorry, since it might be seemed as not ROM related, but actually, I think it is.

Maybe we need to start another topic, I am not sure. Thanks for sharing charging information. It will be also interesting to see is there any difference while charging phone turned ON, I suppose the difference could happen.

Back to ROM: I found the battery profiles for HTC One S original battery and for 2300 mAh. They are actually sit in the same git repo:

ville: https://github.com/CyanogenMod/andr...2b3/arch/arm/mach-msm/htc/ville/board-ville.c

m7: https://github.com/CyanogenMod/andr...6cf1db2b3/arch/arm/mach-msm/htc/m7/board-m7.c

search for .capacity

from that I learned last days, battery monitoring system chip (bms) which is 8921 of qualcomm uses not only voltage for charging, but also temperature and impedance tables of the battery in different states, since battery works on chemical reaction, and impedance and temperature changes during charge process and normal discharge.

anyway, all this tables are included in config for m7 board above. the only trick to do now, is to merge code from second file to the first one, and build the kernel.

the only challenge here is that battery selection are made internally by id_raw value, depending the range it fall to. id_raw is determined from battery, you can find it in /sys/class/power_supply/battery/batt_attr_text on a device. it is not a constant, it changes. Mine now is ID_RAW(uV): 275278; Kernel will transform it to 275.

The ranges are 261-510 & 50-260 for 2300mAh battry and 0-330 & 331-540 for default 1650mAh, so they are interchanged. The function used for select is "htc_battery_cell_find_and_set_id_auto" from htc_battery_cell.c

We can alter battery select from board-ville.c using "hint" function htc_battery_cell_set_cur_cell, then this value (battery) will be "selected" irregardless to the raw_id value.
[HTC One S] Bad.Fish:
That was ROM related?
[HTC One S] Morans:
This isn't THIS ROM specifically related. But I think that the non-stock battery management could be a strong plus for roms cooked for a 4 years old phone. How many of us have non-original battery? Anyway if it isn't appreciated, probably it's better to open a new thread on the battery issue. In conclusion, I've made another test; this time with the phone on. I measured the electrical absorption from 0% to 100% and it was only 1798mAh. I turned off the phone and it displayed the battery was still at 100%. Something doesn't work in rom battery management, whereas in the previous test the phone switched off recognise the correct battery capacity. Pictures attached.

Morans
[HTC One S] Bad.Fish:
OK well then start the thread bro
[HTC One S] Hauk92:
New build with December security updates. I cherrypicked 142377 like last time and added 175831 and 175832 because I expect them to be merged soon.

Download:

Android File Host (142377, 175831 and 175832 cherrypicked)

Changelog:

Notable new features: https://github.com/CyanogenMod/android_vendor_cm/blob/cm-13.0/CHANGELOG.mkdn

I would recommend looking at cmxlog for the m7, ignoring all the m7 specific commits (this covers general and msm8960 changes) and at GitHub for the device specific changes.

cmxlog

ville

s4-common

Fixes:

FM Radio workaround:

http://xdaforums.com/showpost.php?p=65085653&postcount=264

Wi-Fi turning off

It seems like Wi-Fi turning off is an aosp problem. I have found various "fixes":

1. In Settings - Wifi - Advanced - Keep Wi-Fi on during sleep > Change the setting to Never

After turning Wifi Off/On change back to Always.

Source: https://forum.cyanogenmod.org/topic/120233-cm13-wifi-dropping/?page=2

2. Another solution that seems to work is to roll back to the Lollipop DHCP Client. Settings-> Developer Options-> Use legacy DHCP client.

Source: https://productforums.google.com/forum/#!topic/nexus/gkPdghmnj_o

3. Install an app: https://play.google.com/store/apps/details?id=com.roy.wifimonitor&hl=en

Possibly faster GPS fix:

GPS should work fine. But if you still have problems you could try to add a supl server in /system/etc/gps.conf:

SUPL_HOST=supl.google.com

SUPL_PORT=7276

Looks like someone is back at posting one liners and telling people to open new threads :-p
[HTC One S] Bad.Fish:
Yup
[HTC One S] pavel.bosco:
Am I right in assuming that building by this instruction: https://wiki.cyanogenmod.org/w/Build_for_ville only produces HBOOT 2.15 version of the ROM?

what should be done in addition to build for HBOOT 2.16?

I understand there are some howto in the forum, but they talk about CM11-CM12, and obsolete, afaik,

could you point me in right direction?

pleeeease
[HTC One S] Hauk92:
You do not need to do anything for CM13. The relevant commit is already merged in the official repo. CM13 is always only for hboot 2.16.

For all versions before CM13 you need to cherrypick a commit from here: https://review.cyanogenmod.org/#/q/...droid_device_htc_ville+use+FUSE+sdcard+daemon.
[HTC One S] pavel.bosco:
thanks bro..

this THING works on right out of the box, not counting week for preparation and downloading and 3 hours of compiling.

i'm crying like brandon fraser

started it just now
[HTC One S] moozon:
New build CM13 from 2017/01/09

Changelog for ville

Changelog for msm8960

Changelog for s4-common

#Tested
[HTC One S] NamenIos:
Can you use an app to measure the voltage of the battery at <5% and at 100%? If the voltages are at 4.1V+ at 100% the battery is at least 90% full probably more, I don't know the <5% voltage, but it should be around 3.5V to be at 10% or less. Probably your battery is just labelled wrong, this happens very often with batteries that are not original.
[HTC One S] Morans:
I use a tester between the charger and the phone. Offline charge is correct (my tester measured 2300mAh), when the phone is on it charge only 1650mAh. pavel.bosco and me are trying to make it work, take a look at this thread https://xdaforums.com/htc-one-s/development/ville-cm13-2300-mah-battery-t3519679
[HTC One S] NamenIos:
This hardly means anything. If the voltages are in the range I gave you, your battery is just mislabelled. Charging a battery is never 100% efficiency, especially with 5V. I really recommend it to you, that you check the real capacity of your battery first before you destroy something.
[HTC One S] Morans:
I know that is never 100% efficiency, but there are no possibilities to destroy anything. Throughout the charge the important value is voltage, which never exceeds 4200mV in the kernel built for my battery. You can set any mAh value, but the Power Management Module PMM8920 (Qualcomm battery manager for the Snapdragon S4) ends the charge when the max voltage value is reached. Even if you raise this value, there's a max voltage limit of 4,5V and the module checks if the temperature of the battery increases too much. Anyway, thank you for your interest :good:
[HTC One S] pavel.bosco:
we were asked to create separate thread for battery discussion, and did it:

https://xdaforums.com/htc-one-s/development/ville-cm13-2300-mah-battery-t3519679

you are welcome to continue in there

as per your note, my view is that you would unable to measure by phone internal sensor, actual state of charge of the battery using only voltage. you need current. as long as battery reach full charge, current drops to ~zero.

and per voltage, it is actually just a guess, you can for instance put 4100 mV as full state of the battery, or you can put 4200. same applies to 5% of charge.

it is more different story with higher voltage. here you may be correct, and as long as battery labeled as 4350 max charge voltage, could only show 4200mV in full charged state, this means it probably not 4350, and instead only 4200, so it's kind of mislabeled, as far as I can understand.

but still there is a probability, that this is just some component inside the phone (either sw or hw) which prevents the battery from being charged to more than 4200mV and so the battery could be labeled correct.

at least the specification of pm8921 charger chip, states it could charge battery with such a high voltage as 4350, and even board-ville.c - source of CM ROM for ville contains a reference to such battery charging voltage, althrough it is not used:

https://github.com/CyanogenMod/andr...ch/arm/mach-msm/htc/ville/board-ville.c#L3111
[HTC One S] EssCee:
Hi folks.

Coming from CM12.1/HBOOT2.16.

Phone has TWRP 3.0.2

Regarding 'Startingpoint: CustomROM' tutorial:

'5. Wipe everything and format partition to F2FS

Boot to TWRP and wipe/format

If you do not format, you may encounter "Unable to mount /cache" error'

What partition do I format, and how can I check the current format of the partitions on the phone?

Any chance I can dirtyflash CM13 over CM12.1?

Cheers.
[HTC One S] The Setlaz:
Still haven't encountered any issue and bettery life has been better than CM12.1 for me and camera doesn't crash either so for me it's good for a daily driver!

By the way, anyone is having very slow start time of Viber app?

I mean 1st time you open the app, I get about 5s black screen and then it appears (once it's in memory, it's fine). I wonder if it's CM13 or F2FS or just my install...
[HTC One S] moozon:
New build CM13 from 2016/05/22. Only for Hboot 2.16 Changelog
[HTC One S] The Setlaz:
Many kernel patches to comes on next build: ALSA fixes, F2FS update, netfilter, ril command, usb...

Courtesy of Matt Mower :good:
[HTC One S] htc-2016:
Exciting!!! :laugh::silly::victory:

Any news or improvements regarding the

encryption

of the phone? Right now it's reported not functional. Can it be related to the f2fs partition?

And another question: Is it possible to flash a newer version of the rom without loosing apps/data/settings etc.? For example from build "cm-13_2016-05-17" to build "cm-13_2016-05-22"

Thank's for the create work... Looking forward to have this great created rom on my phone :D
[HTC One S] The Setlaz:
Just dirty flash:

1. Wipe cache and dalvik only.

2. Flash the ROM
[HTC One S] moozon:
New unofficial build CM13 from 2016/05/25. Only for Hboot 2.16 Changelog
[HTC One S] garleest:
Some observations with CM13 installed on my device. Fresh install and no gapps.

2016/05/11 Camera works with no issues

2016/05/20 Camera works with no issues

2016/05/22 Camera's flash goes off when button is pushed then the camera crashes

2016/05/25 Camera instantly crashes when button is pushed

2016/05/22 and 2016/05/25 Lockscreen will lose wallpaper function (black screen)if any app is pushed to system app or priv-app

Any build - Stock browser will crash on various websites. Reuters, Nascar, etc
[HTC One S] vp1407:
I confirm both the camera and lock screen issue in the latest builds. Don't use the stock browser so can't say anything about that.

I also noticed that the battery percentage icon in the statusbar seems a little bit offset since the 2016/05/22 build.

Furthermore, my device seems to become way hotter than with other ROMs, even though performance and battery are fine. Anyone else having this problem?
[HTC One S] htc-2016:
I can't mange to get SuperCID

tried it already two times. There is no errors :( :confused:

htc-2016@Ubuntu # adb devices
List of devices attached
HT23LW400932	device

htc-2016@Ubuntu # adb shell
shell@ville:/ $ su

root@ville:/ # dd if=/dev/block/mmcblk0p4 of=/sdcard/mmcblk0p4
2+0 records in
2+0 records out
1024 bytes transferred in 0.002 secs (512000 bytes/sec)

root@ville:/ # exit
shell@ville:/ $ exit

htc-2016@Ubuntu # adb pull /sdcard/mmcblk0p4
166 KB/s (1024 bytes in 0.006s)

-> HERE I HEX'ED T-MOB101 to 11111111 (Filesize is identical!)

htc-2016@Ubuntu # adb push mmcblk0p4MOD /sdcard/mmcblk0p4MOD
14 KB/s (1024 bytes in 0.067s)

htc-2016@Ubuntu # adb shell
shell@ville:/ $ su

root@ville:/ # dd if=/sdcard/mmcblk0p4MOD of=/dev/block/mmcblk0p4
2+0 records in
2+0 records out
1024 bytes transferred in 0.007 secs (146285 bytes/sec)

root@ville:/ # exit
shell@ville:/ $ exit

htc-2016@Ubuntu # adb reboot bootloader

htc-2016@Ubuntu # fastboot oem readcid
...
(bootloader) cid: T-MOB101
OKAY [ 0.009s]
finished. total time: 0.009s

Any ideas?

Thanks in advanced!
[HTC One S] The Setlaz:
Camera also stopped working for me but Open Camera is working fine, so that should get fixed by CM soon. Didn't notice phone running hotter though.

Battery icon has changed indeed: spacing is different and battery percentage font is smaller.
[HTC One S] jja2000:
Gain root using the htcdev unlock and twrp. Then use http://rumrunner.us to s-off.
[HTC One S] htc-2016:
Tried that also: unocked Bootloader, installed TWRP, flashed CM11.

Now when I wanted to use rumrunner it doesn't pass. I meeting all requirements just the custom Rom is not officially supported.

Tried to get the stock rom back. Even thoug my restored backup from twrp doesn't start and now my internal storage/sdcard is gone?? In Twrp and via MTP at the computer.... oh dammit... :(

I get a lot's of errors in twrp when doing a factory reset:

E:Unable to mount '/sdcard'
E:Unable to recreate and-sec folder.
E:Unable to mount '/sdcard'
E:Unable to mount '/sdcard'
Updating partition details...
E:Unable to mount '/sdcard'
...done
E:Unable to mount storage
E:Unable to mount /sdcard during GUI startup
Full SELinux support is present.
E:Unable to mount /sdacrd/TWRP/.twrps when trying to read settings file.
E:Unable to mount '/sdcard'
MTP Enabled
E:Unable to mount '/sdcard'
E:Unable to mount '/sdcard'
E:Unable to mount '/sdcard'
E:Unable to mount '/sdcard'
E:Unable to mount '/sdcard'
E:Unable to mount '/sdcard'
E:Unable to mount '/sdcard'
E:Unable to mount '/sdcard'
E:Unable to mount '/sdcard'
E:Unable to mount '/sdcard'
E:Unable to mount '/sdcard'
E:Unable to mount '/sdcard'
E:Unable to mount '/sdcard'
...
Updating partition details...
E:Unable to mount '/sdcard'
...done
E:Unable to mount storage.
E:Unable to mount '/sdcard'
Formatting Cache using make_ext4fs function.
Formatting Data using make_ext4fs function.
E:Unable to mount '/sdcard'
Updating partition details...
E:Unable to mount '/sdcard'
...done
E:Unable to mount storage.

What a morning :(
[HTC One S] jja2000:
You need to format your device using the wipe menu, I had the same problem when I booted into twrp for the first time (it was only cache though).

So format your sdcard and you'll be fine.

Also, try to get stock running again, rumrunner worked for me as long as you gain root using supersu and twrp
[HTC One S] htc-2016:
Thanks for your reply.

Sadly it still doesn't work. I have 0MB of internal storage and no way to wipe or format the internal storage=sdcard.

When I use the file manager within twrp I can see a folder sdcard with a folder twrp. But this is not a partition.

Is there any .zip file for flashing the stock rom via fastboot or adb?
[HTC One S] jja2000:
You need to flash the ruu via fastboot, there should be enough tutorials around these forums.
[HTC One S] htc-2016:
Nice! That gives me hope!

One more dump question and I'm off ;)

There is two possible fitting RUUs, because of the CID -> T-Mobile DE

RUU_Ville_U_ICS_40_S_TMO_DE_2.38.111.10_Radio_1.09es.50.02.07_2_10.09d.50.04L_ver2_release_287723_signed.exe

RUU_Ville_U_TMO_DE_1.77.111.5_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_259421_signed.exe

Probably both of them will work, I guess?

Any idea how to handle the ".exe" File in Linux? I don't flash this via fastboot.. I need to unpack or run an installer, right?

Thank's for help :highfive:
[HTC One S] Flippy498:
With S-On you can only use RUUs with the same or a higher firmware version than the one that is currently installed on your phone. You can check the current version with "fastboot getvar all". It's the "version-main".

For extracting files from RUUs you should take a look at this thread: http://xdaforums.com/chef-central/android/tool-universal-htc-ruu-rom-decryption-t3382928
[HTC One S] htc-2016:
Thank's for the information! Great people with great knowledge here!

If have

version-main: 3.16.111.11

So both versions I posted are lower than mine, right? And probably I'm locked to the one from TMD because my CID is still T-MOB101.

Can I use this one without TMD?

RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4.exe
[HTC One S] Bad.Fish:
Just changed to hboot 2.16 to try this ROM. I'm actually impressed with how smooth it runs. Not happy with camera but other camera apps work good so no biggy

sent from my HTC One S on Marshmallow biyatch
[HTC One S] htc-2016:
I decrypted the RUU:

RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4.exe

and have a boot.img and system.img now.

Is it wise to flash these ones via twrp? And does it give me back my internal-storage/sdcard or does it make things worse? :eek:
[HTC One S] Bad.Fish:
If you are already on 2.16 there is no special wiping. Just full wipe and clean flash
[HTC One S] derkleinebroicher:
IIRC you can restore your data from a 12.1 backup to a clean Cm13 installation. To check the format of your partitions, i recommend diskinfo .
[HTC One S] EssCee:
Ok, thanks folks.

Installed, and so far, so good.

However, I do seem to be missing the Torch app - is this supposed to be there?
[HTC One S] derkleinebroicher:
There is a toggle for the Torch in the quick settings. But there is no app in the app drawer.
[HTC One S] pavel.bosco:
trying to build lineage 14.1

but it stops as it missed

'vendor/htc/s4-common/proprietary/etc/firmware/widevine.b00'

and this file is not extracted from the phone, seems it's not there

is it some lineage for ville inconsistency, or some additional steps need to be done from my side?

I've included Muppets project, but I'm not sure on which steps it load binaries, and should I omit using 'extract-files.sh' with Muppets included

UPD: actually found that I used Moozon fork, and it's just NOT updated by recent changes of widevine is s4-common part
[HTC One S] EssCee:
Ok, I've found it now :good:

Have found something strange:

Settings -> Lock Screen -> Screen Lock

When I tried to set a PIN for the screen lock, it would always fail at the second entry - just stop and proceed no further.

This happened multiple times.

When I came fully out of settings, and tried again, the screen lock function first asks for the PIN code - and does not accept it.

When the phone is locked, it will accept the PIN code to unlock.

So the PIN code has been set - but now cannot be unset or changed.
[HTC One S] moozon:
New build CM13 from 2017/01/31

Changelog for CyanogenMod common

Changelog for ville

Changelog for msm8960

Changelog for s4-common

#Not Tested

New build LA14.1 from 2017/02/05

Changelog for LineageOS common

Changelog for ville

Changelog for msm8960

Changelog for s4-common

#Tested
[HTC One S] Bad.Fish:
I get an access denied page from android file host regarding your 14.1 build.... (Fixed) well its your link. I found a workaround. I accessed it through your profile on AFH
[HTC One S] rickq_:
Hi,

try to use the link for downloading CM13 but change flid=149533 in the url (sorry for not posting the exact url, I have just registered here and I am not allowed to).
[HTC One S] Bad.Fish:
Look above to my post I found a workaround
[HTC One S] rickq_:
Thanks a lot.

But CM13 seems to be very laggy since the build cm-13.0-20161109-UNOFFICIAL-ville.zip.
[HTC One S] Bad.Fish:
I am on the 14.1 build. It took a while to boot up but after that works super quick. Only issues are 1: no access to play store. The app icon is there but does nothing. 2. I can't find where to add my Google account 3. No root access offered to apps
[HTC One S] Bad.Fish:
OK I switched the gapps and got access to play store and Google account.... But syncing is messed up for gmail. And still no access to root for apps just adb root access
[HTC One S] htcones:
I assume this comment is related to the Lineage 14.1 build. To get root baked in you must build with WITH_SU=true set in your environment. I too am stuck with Play Store not connecting,which GAPPS are you using as I downloaded the nano arm 7.1 version from today and had no luck.
[HTC One S] Bad.Fish:
https://xdaforums.com/android/general/gapps-gapps-7-0-nougat-minimal-t3474980/page5 here's the gapps. Use the version 2.1 not 3.0.
[HTC One S] htcones:
Still the same result for me, logcat is showing some kind of SSL issue, so I am suspecting my build. is the issue. Not sure if my CM 13.0 and Lineage OS 14.1 are sharing the same build cache, so I might clean that out and do the build again and see if that improves the situation for me.

Finsky : error:100003fc:SSL routines:eek:PENSSL_internal:SSLV3_ALERT_BAD_RECORD_MAC (external/boringssl/src/ssl/s3_pkt.c:610 0x9a7b7a40:0x00000001)
[HTC One S] Bad.Fish:
I triple swipe clean before I flash a new ROM to ensure everything runs smoothly
[HTC One S] htcones:
I have even tried moozon's build with the exact same issue, so it has to be the way I am prepping my device.

What exactly do you mean by triple swipe clean? I am using TWRP 3.0.0-M5 and I do an advanced wipe selecting everything except Internal Storage and OTG.
[HTC One S] Bad.Fish:
I do have the same twrp and do the same advanced wipe you do. But after that I back out and just do the regular full wipe swipe twice.then flash the lineage 14.1 and the agapps v.2.1 arm. Make sure you are NOT using agapps v.3.0 arm64. Then reboot. When phone boots up let set for 5- 10 minutes then reboot again. When it boots back up give a few minutes then you can set it up
[HTC One S] htcones:
Sadly, the same end result :crying:

I have posted in the development group to see if anyone has any suggestions,

https://xdaforums.com/showpost.php?p=70883112&postcount=5724
[HTC One S] moozon:
Update links
[HTC One S] Bad.Fish:
For those that want root access. Flash this in recovery
[HTC One S] Bad.Fish:
https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools here is a recovery mode update for twrp. I used the app in the link above to flash it. DO NOT FLASH THIS ZIP IN RECOVERY. UNZIP USING ANDROZIP AND FLASH THE .IMG USING THE APP IN THE LINK ABOVE
[HTC One S] Bad.Fish:
Just updated to the latest build. So far so good except the gmail sync is still acting up. Everything else syncs better except that.
[HTC One S] Roomianfar:
Bluetooth hands free Crash

Tank you for posting this great and useful rom ;) :o, everything works :fingers-crossed: except calling by Bluetooth hands free, It goes to crash and reboot automatically.
[HTC One S] Bad.Fish:
Hola just wondering if you are working on anymore lineage builds? Not asking for an ETA. I tried someone else's build and it messed up my ville. I trust moozon builds
[HTC One S] Strikerr:
cm-13.0-20170131-UNOFFICIAL-ville

Microphone not working on speakerphone mode.

Plz check.
[HTC One S] moozon:
New build LA14.1 from 14.03.2017. Hboot 2.16.

Changelog for LineageOS common

Changelog for ville

Changelog for msm8960

Changelog for s4-common

#Tested

New build CM13 from 14.03.2017. Hboot 2.16.

Changelog for CyanogenMod common

Changelog for ville.

Changelog for msm8960

Changelog for s4-common

#Not Tested.
[HTC One S] mali_zeeko:
Build CM13 from 14.03.2017. works fine for now.

Android security patch level is set to December 1, 2016. Is this correct?