yashsingh1/xdaforums huggingface dataset:
[HTC One S] Hauk92:
I have uploaded a current build. GPS, mp3 and mp4 playback works. I am not sure if this was an issue with cyanogenmod or only with moozons builds.

Download:

https://www.androidfilehost.com/?w=files&flid=77987 (no cherrypicks)

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

As said above GPS should work fine (tested between Hamburg and Bremen). 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

It seems like this 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

I have never answered here:

I do not think splitting the CM13 discussion would be wise. Additionally I am not uploading builds regularly.

In the first thread are two downloads, one with a full system dump and one with only firmware.
[HTC One S] The Setlaz:
New build 07/10 available here

#Tested

October security patch. Includes Flashlight fix.
[HTC One S] Hauk92:
Is the flashlight fix still necessary after http://review.cyanogenmod.org/#/c/161808/?
[HTC One S] The Setlaz:
Oh, good point!

Anyone who tried your build may be able to tell us?! :good:
[HTC One S] matu89:
I have an issue with the voice call , I can't hear the other person on the other side .

Any one else have this issue ?
[HTC One S] The Setlaz:
Voice works fine for me. :confused:
[HTC One S] chevydevil:
I tried that build and the flashlight did work.
[HTC One S] um.z:
Am still on the August 28 CM13 build posted in this thread, and everything is working fine for my purposes. Just curious: is there a good reason to flash a more recent build? For instance, are there any new features or fixes which significantly increase performance?
[HTC One S] The Setlaz:
Nope. Mostly Security Patch and Flashlight fix.

The rest is just minor fixes that (mostly) go unnoticed.
[HTC One S] chevydevil:
I can't use facebook with this rom. Installation failed 3 times. When it finally was installed it crashed on startup. Is it possible, that the device is running out of RAM and there is no swap?
[HTC One S] Bad.Fish:
Apps and storage share the the same space. No swap
[HTC One S] Hauk92:
I have updated my build environment and realized that I have been using old drm blobs in all my CM13 builds.

Then I checked [MENTION=4765686]moozon[/MENTION] and [MENTION=2268315]The Setlaz[/MENTION] builds and saw they were doing the same. (See the attached Oldblobs.png)

So I made a current build with the current blobs.

Download:

https://www.androidfilehost.com/?w=files&flid=77987 (no cherrypicks)

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

You can test if you are using the right blobs by installing https://play.google.com/store/apps/details?id=com.androidfung.drminfo. It should show that Widevine 1.0 with security level L3 is supported. (see the attached Widevine.png)

[MENTION=4765686]moozon[/MENTION] and [MENTION=2268315]The Setlaz[/MENTION]

To use the current blobs in a build you should add the TheMuppets repo to your local manifest.

nano .repo/local_manifests/roomservice.xml

and add:

<project name="TheMuppets/proprietary_vendor_htc" path="vendor/htc" remote="github" />

Edit

I just saw that [MENTION=7522961]htcones[/MENTION] already mentioned drm issues and I answered him then... wtf
[HTC One S] htcones:
Excellent work [MENTION=5094444]Hauk92[/MENTION], I didn't know what to do with that Muppet information back in June. Now you have told us how to include it in our builds. Thank you so much.
[HTC One S] matu89:
What its all mean ?

Right now cm13 is very good except battery life and random reboots

The above is solved in ur build [MENTION=5094444]Hauk92[/MENTION] ?
[HTC One S] Hauk92:
I did basically nothing. I was tipped off by the comments (and solution) here. So thanks to the people there, who do the actual work.

Who knows, maybe the causes for your reboots were fixed. Just try the build, there should be nothing new broken.
[HTC One S] sorewinner:
[MENTION=5094444]Hauk92[/MENTION] : Thanks a bunch for noticing the solution to DRM! It was annoying me for months. Every day I would clean out the tombstones that would accrue from drmserver crashing repeatedly in the background.
[HTC One S] pavel.bosco:
good point Hauk92, thanks,

I don't have any issues with build 31.08.2016, everything I need works fine. especially I glad to not to have any issues with call volume decreased, or with browser performance totally degraded to zero.

I also saw messages of drm crashing, maybe this influence on battery drawing a bit faster, then expected, so we need a new build to try.

still the build 31.08 is good. I flashed it with factory reset and also did a battery reset by deleting battery stat.

just write it there as a note
[HTC One S] moozon:
New build CM13 from 2016/10/24 Changelog for ville

# Updated Htc proprietary files(Thanks [MENTION=5094444]Hauk92[/MENTION])

# Tested

P/s

I created a new repository on Github with proprietary files for ville only. https://github.com/moozon/proprietary_vendor_htc_ville

Add to local manifest(roomservice.xml):

<project name="moozon/proprietary_vendor_htc_ville" path="vendor/htc" remote="github" revision="cm-13.0" />
[HTC One S] The Setlaz:
New build 25/10 available here

#Tested

Includes working DRM from TheMuppets repo (thanks to Hawk92 for that!), reverted previous flashlight fix (thanks to Hawk92 again!), and latest kernel commit pushed today (courtesy of Matt Mower):

# KEYS: Fix short sprintf buffer in /proc/keys show function (android_kernel_htc_msm8960)
# tcp: fix use after free in tcp_xmit_retransmit_queue() (android_kernel_htc_msm8960)
# mm: remove gup_flags FOLL_WRITE games from __get_user_pages() (android_kernel_htc_msm8960)
# fix infoleak in rtnetlink (android_kernel_htc_msm8960)
# Replace %p with %pK to prevent leaking kernel address (android_kernel_htc_msm8960)
# fs: ext4: disable support for fallocate FALLOC_FL_PUNCH_HOLE (android_kernel_htc_msm8960)
# binder: prevent kptr leak by using %pK format specifier (android_kernel_htc_msm8960)
# net: Fix use after free in the recvmmsg exit path (android_kernel_htc_msm8960)
# perf: duplicate deletion of perf event (android_kernel_htc_msm8960)
# ASoC: msm: audio-effects: misc fixes in h/w accelerated effect (android_kernel_htc_msm8960)
# msm: perf: Do not allocate new hw_event if event is duplicate. (android_kernel_htc_msm8960)
# UPSTREAM: netfilter: x_tables: validate e->target_offset early (android_kernel_htc_msm8960)
# msm8960-common: libril: Replace variable-length arrays on stack with malloc. (android_device_htc_msm8960-common)

Haven't included [MENTION=4765686]moozon[/MENTION] proprietary files though :(

EDIT: Link pointing to new upload ZIP file
[HTC One S] sorewinner:
Thanks for your build [MENTION=2268315]The Setlaz[/MENTION] , but I think that either your source file, or your upload, was corrupt. I've d/l it, MD5-verified, to multiple hard drives, via multiple servers. 7z can open it, but with multiple errors. Phone will not flash it >> corrupt zip.
[HTC One S] The Setlaz:
Thanks for the heads-up!

It may well be the upload. My phone is running on this one, so it was clean on my own drive. I will upload again soon!
[HTC One S] matu89:
Any improve in battery life?
[HTC One S] The Setlaz:
On par with previous version... Unplugged my phone at 9am this morning, it's 7pm now and I'm at 72% left... (with very little usage / SOT though)
[HTC One S] The Setlaz:
I've just re-uploaded it, it should be fine. Can you give it a try here?

The downloaded version opens fine on my desktop (LM18 with file-roller archive manager)

Thanks!
[HTC One S] sorewinner:
Good to go, [MENTION=2268315]The Setlaz[/MENTION] ! I assumed it was one of those rare upload corruptions. Thanks, again :)
[HTC One S] ilbarone87:
Hi guys, I'm trying to install this rom on my device but after changed to 2.16, the external storage is not recognized, anyone knows any fix for this issue?
[HTC One S] matu89:
Hey,

In twrp format the SD card to ext4 file system and then it will recognize ur SD card storage.
[HTC One S] ilbarone87:
Fixed, thank you.
[HTC One S] aurel33:
What is the best version:

Moozon of 24/10/16 or The Setlaz of 25/10/16?
[HTC One S] The Setlaz:
They are the same. Mine just includes latest Kernel commits merged on 25/10 evening.
[HTC One S] pavel.bosco:
any news on CM14 ? what should be done to make it happen? is it possible at all?
[HTC One S] aurel33:
Moozon said: Updated Htc proprietary files (Thanks @ Hauk92)

The Setlaz said: Have not included [MENTION=4765686]moozon[/MENTION] proprietary files though

This difference does not change?
[HTC One S] The Setlaz:
[MENTION=4765686]moozon[/MENTION] created its own repository. I used TheMuppets repository.

I don't know if he introduced any changes compared to TheMuppets, from what I saw, they are the same files.
[HTC One S] derkleinebroicher:
Just tried both latest versions and found out, that the home button won't open the app drawer. Is this normal? The other options (long press and double press) seem to work fine.
[HTC One S] razor26:
Hi, I'm currently using the 20160727 version. If I want to update to the latest version, can I just dirty flash? I also flashed cyanogen apps. Will it be affected? Thanks in advanced!
[HTC One S] Bad.Fish:
I wouldn't. Its too much of a gap between updates
[HTC One S] Hauk92:
I always wipe system and cache, then reinstall all zips (CM, GApps, Xposed, FM Radio). I would only wipe data if there are any unforeseen problems or if the phone is particularly slow.
[HTC One S] aurel33:
I had the bluetooth bug and since he works for the media but no longer works for the phone.

There t there a way to run it again?
[HTC One S] razor26:
Thanks for the reply! I'm thinking of updating because I'm experiencing significant lag whenever I just turn on my wifi and receive status bar notifications. Now, I limit the notifications to emails only but it still lags the same. I uninstalled facebook and messenger because using them practically makes the phone unusable. Does anyone have this problem as well? Otherwise, my phone runs smooth especially when wifi is turned off.
[HTC One S] aurel33:
My phone works well even with wifi on the latest version
[HTC One S] htcones:
Lags like that are usually caused by specific apps. When I had that problem it was caused by the BBC news app using most of the CPU for a couple of minutes after turning on WiFi. I used OS Monitor to identify the issue. Problem stopped after turning off usage stats and background updating. So you might have something else doing the same.
[HTC One S] razor26:
Thanks! Will try to do what you suggested the next time I encounter this problem again. For now, I flashed the latest version after wiping everything except sdcard and it's working smoothly now!
[HTC One S] moozon:
New build CM13 from 2016/11/09

Changelog for ville

Changelog for msm8960

Changelog for s4-common

#Tested
[HTC One S] The Setlaz:
Also built it yesterday 2016/11/10, available here

November 5 security patch

#Tested
[HTC One S] Olli1277:
the ROM works well and fast for me. Only FM radio and rSAP App isn't working .
[HTC One S] fax11:
I've read many threads and I can'y explain why on my One S rom is very slow and there are many lags. I reinstalled the entire hboot 2.16, I did clean install...

If you know a solution

Thanks
[HTC One S] The Setlaz:
Even after clean install? (i.e: no apps, just Pico Gapps package)
[HTC One S] Bad.Fish:
Dirty flashed the setlaz new build... My lag is completely gone
[HTC One S] fax11:
I did another clean install, this time I wiped system AND data, that I didn't do last time. It's more responsive, some lags but better :)
[HTC One S] Morans:
Hi! First of all, thank you for the ROM; it’s fast, stable and on my phone everything works! My problem is that I replaced the stock battery with a 2300mAh. The phone recognized it as 1650mAh, so I unzipped the rom archive, unpacked system.new.dat, opened framework-res.apk and changed battery capacity value from 1650 to 2300 in power_profile.xml. Then I signed framework-res.apk, repacked system.new.dat, zipped the rom and signed the rom archive. I tried to install it on my phone and all went right. Then I tried to install gapps but it failed and I noticed that my system partition was only 500mb. I think that something went wrong repacking system.new.dat because the program that I used (Marshmallow system extractor by matrix) asked me the size of system folder before repacking it and I inserted 500mb (the size of system folder). I tried also to force a size of 1600mb (the original size of my system partition) but the program failed. What I’m doing wrong? Do you have any idea?

Morans
[HTC One S] pavel.bosco:
that is an interesting point, I did recently inserted 2800 mAh battery, without doing anything, and miss 'the effect', so it works a bit longer, but not dramatically. I even didn't know that I should change something in framework-res.apk.

edit: just tried

root@ville:/ # cat /sys/class/power_supply/battery/full_bat
cat /sys/class/power_supply/battery/full_bat
1650

and get 1650 mah, so looks like I really need to change something..

while in "capacity" it seems show only percentage value of 100

root@ville:/ # cat /sys/class/power_supply/battery/capacity
cat /sys/class/power_supply/battery/capacity
100

I did tried to rewrite existed framework-res.apk under /system/framework, using mount -o remount,rw, file changed successfully, stays after reboot, but, if I do cat /sys/class/power_supply/battery/full_bat it shows same 1650 as before.

so I'm not sure if I get that desired

latest lines from dmesg states that full_bat=1650:

[ 3958.422798] [BATT] batt_worker: total_time since last batt update = 60160 ms. at 3958400442096 (2016-11-28 14:43:16.091370679 UTC)
[ 3958.428719] [BATT][BMS] FCC=1640000,UC=0,RC=1640000,CC=-3,CC_reset=0,RUC=1640003,SOC=101,SOC_R=300,start_percent=-22,end_percent=-22,OCV=4179539,OCV_raw=4179539,rbatt=128,rbatt_sf=0,batt_temp=303,soc_rbatt=0,last_rbatt=-22,V_unusable_uv=3000000,pc_unusable=0,rc_pc=100,scalefactor=100,no_ocv_update_ms=0,consistent=0
[ 3958.429512] [BATT][BMS] pm8921_bms_get_batt_soc: state_of_charge=100, store_soc_ui=100, last_good_ocv_uv=4179539, raw.cc=-768, stored_cc_uv:-768, currtime_ms=2875446266
[ 3958.430367] [BATT] prev_chg_src=7, prev_chg_en=7, chg_dis_reason/control/active=0x0/0x0/0x0, chg_limit_reason/active=0x0/0x3, pwrsrc_dis_reason=0x0, prev_pwrsrc_enabled=1, context_state=0x0, pre_screen/cur_screen=0/0, htc_extension=0x1, sw_stimer_counter=0
[ 3958.442453] [BATT][CHG] V=4190 mV, I=0 mA, T=30 C, SoC=100%, FCC=1640000, id=275 mV, H=1, P=1, CHG=1, S=4, FSM=1, AC=0, USB=1, DC=0, WLC=0 iusb_ma=500, usb_target_ma=0, OVP=0, UVP=0, TM=0, eoc_count/by_curr=0/0, vbatdet_low=0, is_ac_ST=0, batfet_dis=0x1, pwrsrc_dis=0x0, is_full=1, temp_fault=0, is_bat_warm/cool=0/0, btm_warm/cool=0/0, ichg=4858 uA, vph_pwr=4192503 uV, usbin=5103884 uV, dcin=43422 uV, pwrsrc_under_rating=0, usbin_critical_low_cnt=0, disable_reverse_boost_check=0, flag=0000, hsml_target_ma=0, vin_min=4400, pj_exist=0
[ 3958.443948] [BATT] ID=1,level=100,level_raw=100,vol=4190,temp=303,current=0,chg_src=7,chg_en=7,pj_src=0,pj_level=0,full_bat=1650,over_vchg=0,batt_state=1,overload=0,ui_chg_full=1 at 3958421836877 (2016-11-28 14:43:16.112521296 UTC)
[ 3958.444986] [BATT] batt_worker: done

maybe the problem is that I didn't signed back this .apk
[HTC One S] bakmanhans:
Can't you just open the file in vi or vim in "adb shell"? Make your change and save/close the file. And reboot.

Verstuurd met Tapatalk
[HTC One S] pavel.bosco:
I found out thet the capacity is hardcoded to be 1650 in anyway, there:

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

search for string "htc_battery_cell htc_battery_cells" without quotes

but as in my case, battery detected as Unknown, which is 3d choise, which doesn't have id_raw_min id_raw_max limits, whatever it means.

so the question is, do we need to do something special if we insert more powerful battery inside the phone, or it is smart enough to manage new battery itself?
[HTC One S] Hauk92:
I have uploaded a new build. Lots of WiFi changes this time (see changelog). I additionally cherrypicked 142377.

Download:

Android File Host (142377 cherrypicked)

Changelog:

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

It makes more sense to change this to

<project name="TheMuppets/proprietary_vendor_htc" path="vendor/htc" remote="github" />

I edited this in my original post.

I do not think this makes much sense. You would be more prone to outdated files in the future (or in other revisions of CM)
[HTC One S] Morans:
So there's no way to change the value? I tried the method found on this webpage http : // www . htcmania . com / showthread . php ? t = 755503 (sorry for spaces in this link, but otherwise I can't post it), but without success. I don't know if it's smart enough to manage different battery capacity, but I doubt it. In my experience battery life hasn't changed as expected.
[HTC One S] um.z:
Will there be CM14 for the One S?
[HTC One S] Bad.Fish:
Someone will eventually try and make an unofficial build from source.
[HTC One S] Vavun:
Have the same problem :(
[HTC One S] pavel.bosco:
after some reading, I found out that this question was rised on the forum at some 2014ies, with some people telling it makes no sence to insert more capacity battery, and others to disagree.

that I found myself as an outcoume of all my reading and some code analisys, that actually "capacity" value is hardcoded to 1650 in code, but it makes no sence. the value that makes sence is minimal and maximum voltage of the battery. this is the points there phone treat battery as fully charged and discharged. and minumum are obviously are more or less equal for all battery, independed of their capacity. this is also maybe misleading, since it is not voltage it is current (ampere) which should make sence.

But from practice I believe you can get a full from your battery not changing any config file or piece of code. Just dischage it almost fully, then clear the statistic (there is bucket icon on battery menu in settings for that), and then phone will turned off, charge it to green light.

My phone lifetime expanded almost twice with with new battery, like 2 days in normal conditions and 1 in hard use, so new battery makes sence.
[HTC One S] Flippy498:
But from your findings it looks like there is no benefit in using a bigger one. As far as I can tell you just could have used a 1650 one. When I bought the One S back in 2012 it's battery lasted for two and sometimes even for two and a half days although it only has the standard battery.

I can't prove that since at that time I wasn't tinkering as much as I'm now and therefore didn't bother looking at battery statistics, etc. However from your experience and the whole discussion from 2014 I personally come to the conclusion that although it's a good idea to change the battery after some years it's not worth paying more for a bigger one.
[HTC One S] pavel.bosco:
well, you are right, I can't prove anything too. it is just a general conclusion, that there isn't such thing as constant capacity for the battery, so even cap for capactity wouldn't make more sense than just a general information from software perspective.

also I forget to mention, that I did found that values for bigger battery i.e. 2000mAh have same numbers in max_voltage, min_voltage, and the only difference is capacity.

Your message force me to investigate more. I will comeback if I will find anything more useful. For now I feel I could end up with full setup for building ROMs myself for experiments, but I'm too lazy for that.
[HTC One S] Bad.Fish:
So this is the battery forum now?
[HTC One S] Morans:
You're right, but i thought that many of us that changed their battery, could have the same problem; so I looked for the solution, and eventually I found it! It's impossible to measure battery drain, so I bought an USB tester and I measured the battery charging from 0% to 100%. My battery is 2300mAh and the tester measured 2344mAh (picture attached). So battery management infers residual % capacity from battery voltage (as written by pavel.bosco) not from mAh and the hardcoded max capacity value (1650) isn't used. The case is closed; I'm sorry, if I bothered someone.

Morans