yashsingh1/xdaforums huggingface dataset:
[HTC One S] Fear of Oneself:
I have had some issues with my device not reporting battery capacity very well once that battery gets low. At about 30%, the battery will remain reporting 30% until it dies completely. Not totally sure if that isn't an issue specific to my phone though, as the battery has got quite old. Furthermore, it takes about a week for a ROM to settle down on my device in terms of correctly reading battery when charge drops down low. Anyway, it's not critical and I've been using this as my daily, just thought I'd throw it out there to see if other people are seeing same thing. Going to try the newest build this weekend and post back my findings.

Again, OP thank you for continuing to post builds
[HTC One S] sorewinner:
Yes, I've noticed that, as well. Logcat shows battery errors:

BatteryStatsService( 1165)
no controller energy info supplied

&

BatteryStatsService( 1165)
modem info is invalid: ModemActivityInfo{ mTimestamp=0 mSleepTimeMs=0 mIdleTimeMs=0 mTxTimeMs[]=[0, 0, 0, 0] mRxTimeMs=0 mEnergyUsed=0}
[HTC One S] pavel.bosco:
in addition to listed in comments to

https://review.lineageos.org/#/c/155632/

there are also

01-29 06:07:42.932 183 183 E SELinux : avc: denied { find } for service=package pid=13693 uid=0 scontext=u:r:sudaemon:s0 tcontext=u:object_r:package_service:s0 tclass=service_manager permissive=1
01-29 06:57:19.716 183 183 E SELinux : avc: denied { find } for service=deviceidle pid=17391 uid=0 scontext=u:r:sudaemon:s0 tcontext=u:object_r:deviceidle_service:s0 tclass=service_manager permissive=1
01-29 09:15:10.383 183 183 E SELinux : avc: denied { find } for service=netd pid=13007 uid=1000 scontext=u:r:system_app:s0 tcontext=u:object_r:netd_service:s0 tclass=service_manager permissive=0
[HTC One S] pavel.bosco:
are you still on original battery?

I wonder what your adb shell "cat sys/class/power_supply/battery/uevent" shows to you.

on non-stock one I get

POWER_SUPPLY_=(null)

but this maybe unrelated.
[HTC One S] Flippy498:
I'm using the stock battery, as well. And I'm getting the same output: POWER_SUPPLY_=(null)
[HTC One S] pirlano:
For the netd it really seems one more entry on the *.te file is needed.

But what apps are running in sudaemon context? (pid 13693 and 17391). Are you using supersu or something similar?
[HTC One S] pavel.bosco:
I think it's greenify with root privs
[HTC One S] sorewinner:
Yes, a stock battery. As [MENTION=5872674]Flippy498[/MENTION] said, I get "POWER_SUPPLY_=(null)", as well.
[HTC One S] pirlano:
try to add this entry (to be superclean should be in system_app.te, but any existing te will do the job)

allow system_app { service_manager_type -netd_service }:service_manager find;

for the other 2 entries permissive=1, so it should be ok
[HTC One S] tmm68:
Weird behavior

I have totaly wipe my device and installed the system and gapps with the files from the first page.

The WLan is not working and mobile data works partialiy.

I did a factory reset and so on ....

The result is WLan without internet connectivity (little cross in the WLan symbol). Maybe the lastest rom only has this problem. There is nothing mentioned in the thread.

Regard

TMM
[HTC One S] pavel.bosco:
I see there is some sort of netd policies on global level, like

neverallow { domain -system_server -dumpstate } netd_service:service_manager find;

https://github.com/LineageOS/androi...c2af1630c15ba15f5ed38b23334e7957958b6/netd.te

so as I understand, only system_server and dumpstate domain are allowed, while system_app do not

but thank you for help, you inspired me to learn more
[HTC One S] pirlano:
exactly :good:

https://selinuxproject.org/page/AVCRules#neverallow

# Using the neverallow rule to state that no allow rule may ever

# grant mmap_zero permissions any type associated to the domain

# attribute except those associated to the mmap_low_domain_type

# attribute (as these have been excluded by the negative

# operator (-)):

neverallow { domain -mmap_low_domain_type } self:memprotect mmap_zero;
[HTC One S] pavel.bosco:
#uploaded new version

lineage-14.1-20170201-UNOFFICIAL-ville.zip

Changelog for ville

Changelog for msm8960

Changelog for s4-common

there are some notable changes in power-profile.xml, and fix for some background phone activity if phone is in GSM network.

all other changes up-to-date are included, only merged commits.
[HTC One S] F-L-Y-E-R:
So this means LineageOS will have official support for Ville? :eek:

Strange and amazing at the same time because there was no MM
[HTC One S] Fear of Oneself:
That would be amazing if true. I looked for a list of supported devices, but couldn't find one
[HTC One S] pavel.bosco:
unfortunately I'm a not connected to official sources. All I know there are some list of "officially supported" devices over different www sites, and they contain HTC One S.

some of them even have a link to download Lineage 13 (it was a surprise to me)

#deleted the question about youtube.

seems that youtube works fine in chrome. as well as in youtube app. this is just chromium which fails.
[HTC One S] KuGeSch:
Great ROM!

Thanks to all contributors. This is the very best ROM ever for our device!!
[HTC One S] Vavun:
setup wizard apk crash at first boot after clean install (not update)

build lineage-14.1-20170201-UNOFFICIAL-ville.zip
[HTC One S] Flippy498:
I didn't face that problem after a clean install. Did you verifiy the MD5 checksum of the rom after the download was completed?
[HTC One S] Vavun:
no actually, just checked - md5 is OK

tried to wipe all caches and data - setup wizard still crash

---------- Post added at 05:40 PM ---------- Previous post was at 05:36 PM ----------

I will try to download and install it again just in case

---------- Post added at 05:57 PM ---------- Previous post was at 05:40 PM ----------

1) downloaded zipped rom again - done

2) checked md5 after download - OK

3) Wiped everything except internal memory and usb otg

4) installed freshly downloaded rom again

5) setup wizard crash again =(
[HTC One S] TheEndHK:
long time no see pirlano .... I think you already forgot me... hehe :D

---------- Post added at 02:11 AM ---------- Previous post was at 02:09 AM ----------

yup, it's good to hear One S received 7.1 and on going development even after five years.
[HTC One S] Dooxed:
I have got exactly the same issue: Setup wizard crashing after clean install. Tried multiple times, with various variations on formatting the partitions to F2FS or not.

I did htc unlock, ran the unofficial RUU to get to HBOOT 2.16&radio 1.20, installed TWRP 3.0M5, wipe all, formatted partitions, installed lineage-14.1-20170201-UNOFFICIAL-ville.zip through mount and also tried via sideload. Starts fine, takes a couple of minutes to get through the splashscreen, then starts with continuously crashing setup wizard. I am able to operate the sound buttons just fine, that's it. Any thoughts on how to debug?
[HTC One S] Fear of Oneself:
What gapps are you using?

When flashing I do the following: (in TWRP)

Nandroid backup

Complete Wip

Flash ROM

Complete Wipe

Flash OpenGapps pico

Complete Wipe

Reboot
[HTC One S] Dooxed:
I did not flash any Gapps. Might that cause this?
[HTC One S] Fear of Oneself:
Indeed. In my opinion, Gapps are bloated these days, I would recommend the pico http://opengapps.org/
[HTC One S] pavel.bosco:
did you install gapps?

try previous Lineage build. See downloads section.

I'm not sure, it maybe my setup missed something, or I checked out sources between of two commits, or maybe just some commit was wrong at the particular moment of my build.

I tried to install todays build (not published), noticed some browser crash while setup, and also it finished kind of unexpectedly near the end of setup on some misc page, but everything works after that.

I also noticed there are a lot of changes in the wizard, comparing the my first setup, most of them are about import existing data. Most likely work is still in progress.
[HTC One S] Dooxed:
:good: With lineage-14.1-20170127-UNOFFICIAL-ville.zip no problems at all, works very smoothly. Again no Gapps / Opengapps whatsoverever installed. Thanks for the fast responses!
[HTC One S] Fear of Oneself:
I tried flashing the February build today with OpenGapps, and I get "setup has stopped" in a loop upon first boot. This is a clean flash too. Same issue as him. What gapps to you use?

This build is my daily driver too
[HTC One S] Flippy498:
Open GAPPs pico for arm/7.1 from the 2nd February are working fine with the rom build from the 1st February.
[HTC One S] Wel1973:
Fantastic LinageOS Rom!. I installed 02/01 on Wednesday and no problem since them. At first I didn´t have root access but I repaired it post-first with a flasheable.zip. Therefore, no reboots, no problems. Very smooth and stable. . for dalily use no doubt. This terminal is in a second life. . Or maybe a third;)

Great job here!:good:
[HTC One S] NH3:
What about this HBOOT version?
[HTC One S] pavel.bosco:
it's another device, CPU s3
[HTC One S] KuGeSch:
hboot 2.16

I followed this instruction and it worked...

https://xdaforums.com/htc-one-s/general/guide-how-to-install-hboot-2-16-time-t2898605
[HTC One S] htcones:
My life does not appear to be so straight-forward., posting this for the benefit of others.

First I tried building my own ROM and Lineage installs and runs fine, It was the nano Gapps that never worked. I tried OpenGapps nano & micro and A GAPPS minimal 2.1 suggested by [MENTION=4645918]Bad.Fish[/MENTION] but I always ended up with the same result,

02-06 12:20:39.926 2026 6139 E GCoreUlr: Caused by: javax.net.ssl.SSLProtocolException: Read error: ssl=0x97c6d400: Failure in SSL library, usually a protocol error

02-06 12:20:39.926 2026 6139 E GCoreUlr: error:100003fc:SSL routines:eek:PENSSL_internal:SSLV3_ALERT_BAD_RECORD_MAC (external/boringssl/src/ssl/s3_pkt.c:610 0xb4274b60:0x00000001)

GCoreUlr is not the only component with the same BAD_RECORD_MAC TLS alert

So I thought maybe my build environment was bad, so not knowing this thread existed yet I tried the build by [MENTION=4765686]moozon[/MENTION], same exact result.

Then I figured it was so long ago that I did my hboot 2.16 update that maybe I missed something, so I redid that. Same result :crying:

Finally I posted a question in The Android Rom Development forum, https://xdaforums.com/showpost.php?p=70883112&postcount=5724, and the only suggestion was to use an older Gapps release.

I had started with 20170203, then I tried 20170126 which has setup wizard issues. I then pulled yesterday's OpenGapps and it works better but still not fully functional. Play Store at least connect now, but any donwloads and just pending and logcats still shos BAD_RECORD_MAC TLS alerts.

So can anyone give me a bonafide date for OpenGapps that works?
[HTC One S] The Setlaz:
I used OpenGapps micro 20170119 successfully.

But your problem seems rather odd... Have you done a full firmware upgrade or just HB2.16?

What is your radio version?
[HTC One S] htcones:
Today I redid the hboot firmware zip using the zip from the quote of you in the OP. The output during the HB update looked like it was doing the full set.
[HTC One S] The Setlaz:
Give that a go: LOS14.1 04/02/2017 + Gapps 20170119

I didn't go through the Setup with this build but it is working fine for me.
[HTC One S] Fear of Oneself:
OR!

Settings>tap on the 'build number' 7 times>Developer settings>enable Root

You can do:

Apps only

ADB only

Both

I also flashed the latest build, with a fresh download of GAPPS and it worked without a problem. The issue wasn't the rom, it was my GAPPS not copying properly. It was ~100MB on my PC, and ~75MB on the phone. I cleared up some space on the phone's SD card, and that fixed the issue. In all: user error. Testing the new build as of today
[HTC One S] Bad.Fish:
It only shows adb only. LineageOS didn't has app access. That's what the zip is for
[HTC One S] Fear of Oneself:
Right after a fresh install
[HTC One S] htcones:
Sadly the same result. I don't understand why 14.1/Gapps does not work on my device. CM 13.1 is working fine.

You would think that the SSL/TLS implementation would be entirely dependent on the ROM build.

Looks like I am not alone in my misery, https://jira.lineageos.org/browse/BUGBASH-21
[HTC One S] pavel.bosco:
just double check that Setlaz said, your radio module version (settings->about the phone) should be 1.20...

if not, then probably you didn't a fully upgraded to HBOO2.16, some internal upgrade steps are missed, like reformat partitions, radio fw upgrade.

what was your "last known working good configuration" before you started to uprate to lineage?

last gapps 20170204 are working for me. I searched for javax.net.ssl.SSLProtocolException through all my last logs (logcat, dmesg), nothing found.
[HTC One S] htcones:
I updated my previous post with a link to a Jira opened for another device that has the exact same issue.

My radio is 1.20 and has been for a while. I redid the firmware update today just to make sure I had not missed anything previously. I have restored back to my CM 13.1 build for now which is working fine. Just don't understand what makes my configuration so special that I have this issue and few others do.

Here is the getvar from immediately after the update.

(bootloader) version: 0.5
(bootloader) version-bootloader: 2.16.0000
(bootloader) version-baseband: 1.20.50.05.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.05.401.1
(bootloader) version-misc: PVT SHIP S-OFF
[HTC One S] wildboarhog0:
Any plans for this Lineage 14.1 rom for HTC One XL?

if so I will be a tester.
[HTC One S] The Setlaz:
There has been activity on the Evita device. Just follow this: https://review.lineageos.org/#/q/project:LineageOS/android_device_htc_evita+branch:cm-14.1

Maybe you can try to build?
[HTC One S] wildboarhog0:
Man I do wish I knew how to build :crying: ..... Im a Mechanical Engineer

not a Software Engineer :)
[HTC One S] Dooxed:
Just for my better understanding, on what information do you base this? Because there is activity specifically for Ville in the LineageOS repository?
[HTC One S] F-L-Y-E-R:
Yes, not just some activity but a lot of activity even CM13 didn't have that much. On the other hand that probably doesn't mean they will officially release it because anyone can contribute right?
[HTC One S] discomega:
I just wanna hammer that thanks button! Cheers mate!
[HTC One S] pavel.bosco:
#uploaded new version

lineage-14.1-20170212-UNOFFICIAL-ville.zip

Changelog for ville

Changelog for msm8960

Changelog for s4-common

Changelog for frameworks_base

not too much changes at ville specific level.

I hope next version will include changes from next AOSP release android-7.1.1_r21

probably much more fixes/enhancements, currently not merged yet https://review.lineageos.org/#/c/160504/

bug resolved: then you open battery stats several times from drop down quick tiles panel, it wouldn't crash any more.

I updated the recovery info in OP with latest version information, prepared/built by MDMower.
[HTC One S] Bad.Fish:
Does this build have gmail sync issues? I'm using Moozons 14.1 build at the moment but if gmail sync works on your I will switch
[HTC One S] pavel.bosco:
I didn't see specific change for gmail. What kind of issue you mean? Is it reproducible? Any steps to reproduce?
[HTC One S] derkleinebroicher:
Could anyone share his experience with formatting one or more partitions to F2FS? Advantages / disadvantages, which partitions might be changed or not? Or is it better to stay completely on ext4?
[HTC One S] Bad.Fish:
Download link not working
[HTC One S] 44alphabeT:
You are not alone. My phone Play Store connect but pending download and failed after a while. Tested with lastest gapps pico 20170213 and micro-20170119 with no connection at all.
[HTC One S] pavel.bosco:
guys, I believe your messages without logcat attached, are of no help.

there are simply too many things which could go wrong, to guess any certain one.

upd: but I see someone attached logcat to https://jira.lineageos.org/browse/BUGBASH-21

so maybe it will be solved.
[HTC One S] Fear of Oneself:
I have had no issues with the download link, try it again.

Thanks OP, running the newest build as my daily, no issues thus far. Also figured out my crashing when the battery was low. It was actually my pedometer application which would crash, if the phone's physical temperature was cold. (Walking outside in the Canadian Winter)

EDIT: OP, could you post a link to the .zip that you need to flash which will enable root (assuming you haven't installed GAPPS)? Just experimenting on not using GAPPS on my device, using fdroid and titanium backup with the applications that I need. However root doesn't work properly for titanium backup if you don't install gapps initially. Thank you!
[HTC One S] htcones:
Yeah, I attached my logs. to that ticket after sanitizing my personal info from it. Not optimistic at the moment though as I have had zero feedback.
[HTC One S] pavel.bosco:
I checked quite briefly, found only one difference so far with my own log:

02-10 22:50:38.847 2296 5091 I PeopleSync: Sync start: cannotHavePeople=true isPageExistenceCheckOnly=false

in my log it says cannotHavePeople=false

not sure does it make sence, nor I can tell what it is suited for

nevermind. it's a consequence, probably.

more interesting is

02-10 22:50:38.821 3581 3581 I Finsky : [1] com.google.android.finsky.utils.bl.a_(1247): Server requests device config token

googling gives me that it means you have creadit card attached to your account.

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

I'm defenetely not.

so mb try to detach it, and resync
[HTC One S] Bad.Fish:
When I push download link
[HTC One S] The Setlaz:
I don't have credit card attached either and don't run into those issue. Coincidence?
[HTC One S] htcones:
I do not have any cards associated with my Google account. So unfortunately that cannot be the issue.
[HTC One S] ninjamirage:
Hi. Thanks for this rom :)

I had a problem when using bluetooth and wifi at the same time. Wifi would not connect when bluetooth is on. I haven't changed the kernel or anything. Will try a clean install again. I did try to set se-linux permissive but it didn't solve the problem. I have an Htc ville s4 with 2.16 bootloader. Thanks.
[HTC One S] pavel.bosco:
uploaded new build

lineage-14.1-20170218-UNOFFICIAL-ville.zip

included all up-to-date merged changes

and on top of them some cherry-picked:

https://review.lineageos.org/#/c/162367/

https://review.lineageos.org/#/c/162368/

https://review.lineageos.org/#/c/162374/
[HTC One S] derkleinebroicher:
You're sure, you linked the latest build? This one seems to be from January.
[HTC One S] htcones:
I have had this problem for years. Have just learned to live with it.
[HTC One S] pavel.bosco:
another evidence to not to do big deals right before the sleep, thanks, fixed.
[HTC One S] KuGeSch:
bootloop

after a dirty flash over the last version (lineage-14.1-20170212-UNOFFICIAL-ville.zip) I ended up in a bootloop,

did a dirty reflash of the previous version and that works...
[HTC One S] derkleinebroicher:
Same here. Phone won't boot after dirty flashing latest release.
[HTC One S] pavel.bosco:
hmm..just to let you know I run it for almost 20 hours already w/o problem.

which latest release you use? the previous commenter mentioned of 2017.2.12, which is not indeed latest. <- oops, I get it wrong, sorry

are you clean the cache&dalvik before dirty flash? I recommend to do so, as they actually merged a lot of things, I can't even say exactly how much.

and you can collect /proc/last_kmsg after any unsuccessful boot from terminal in recovery, just copy it to /sdcard in recovery -> terminal emulator
[HTC One S] KuGeSch:
bootloop

I flashed 2017.2.18 over 2017.2.12. I'm not quite sure if I wiped cache&dalvik. Will try again and keep you posted

---------- Post added at 05:09 PM ---------- Previous post was at 04:31 PM ----------

Wiped cache&dalvik, flashed 2017.2.18 over 2017.2.12. Bootprocess is running since 25', have ADB connection, will wait for another 10', suppose it's bootloop.

Maybe I should wipe system as well?
[HTC One S] pavel.bosco:
I don't think it's necessary. just to be sure, are you using gapps? which one? did you update them to the latest? did you reflash them too after flashing rom?

it actually take a long time to boot after clearing cache, but I don't think it's longer that 10 minutes, mb 5, but I never counted, probably depends on gapps variant you choose.

I use the open gapps pico of 12-02-2017
[HTC One S] KuGeSch:
update bootloop

wiped cache&dalvik

flashed 2017.2.18

flashed open gapps pico of 12-02-2017

-> bootloop

wiped cache&dalvik

flashed 2017.2.12

flashed open gapps micro of 19-02-2017

-> works fine
[HTC One S] pavel.bosco:
if this is due to some of cherry-picks, we definetely need /proc/last_kmsg from you after bootloop (can be copied to /sdcard from recovery - terminal)
[HTC One S] KuGeSch:
Here I have some lines out of the file last_kmsg, but I'm not quite sure if it covers the bootloop

[ 403.233694] err: rc = 0x80000002. Failed: ddl_device_init

[ 403.237356] vcd_open returned error: 4294967277

[ 403.337738]

[ 403.337738] VIDC: vidc_freq = 200000000, req_perf_lvl = 244800, set_perf_lvl = 244800

[ 403.342408] pil_get failed

[ 403.342408] ddl_dev_init:fw_init_failed

[ 403.342438] Invalid params

[ 403.342438]

[ 403.342438] err: rc = 0x80000002. Failed: ddl_device_init

[ 403.354402] vcd_open returned error: 4294967277

[ 403.454814]

[ 403.454814] VIDC: vidc_freq = 200000000, req_perf_lvl = 244800, set_perf_lvl = 244800

[ 403.461498] pil_get failed

[ 403.461498] ddl_dev_init:fw_init_failed

[ 403.461529] Invalid params

[ 403.461529]

[ 403.461529] err: rc = 0x80000002. Failed: ddl_device_init

[ 403.466381] vcd_open returned error: 4294967277

[ 403.566793]

[ 403.566793] VIDC: vidc_freq = 200000000, req_perf_lvl = 244800, set_perf_lvl = 244800

[ 403.573325] pil_get failed

[ 403.573325] ddl_dev_init:fw_init_failed

[ 403.573355] Invalid params

[ 403.573355]

[ 403.573355] err: rc = 0x80000002. Failed: ddl_device_init

[ 403.580161] vcd_open returned error: 4294967277

[ 403.680512]

[ 403.680512] VIDC: vidc_freq = 200000000, req_perf_lvl = 244800, set_perf_lvl = 244800

[ 403.685579] pil_get failed

[ 403.685579] ddl_dev_init:fw_init_failed

[ 403.685640] Invalid params

[ 403.685640]

[ 403.685640] err: rc = 0x80000002. Failed: ddl_device_init

[ 403.692415] vcd_open returned error: 4294967277

The whole file is too long to post it here. If you want, I can send it to you as attachment...
[HTC One S] pavel.bosco:
yes, I would like to look to it, mb pastebin or something. will try to resolve.

these lines are ok, they been there before, it is something else.

btw in my log they finish complaining at 310 second of boot, while in yours they do it till 403 sec.
[HTC One S] KuGeSch:
Attached please find the file. -> I removed it
[HTC One S] pavel.bosco:
look trough it briefly, I see bootanim process finished ~416 second of boot, so I believe at this point you should be able to see boot process finished.

then there are unusually lot of selinux denials - not good.

I asked more experienced man to look into it.

thanks for reporting ;)

PS: also, there was an update for TWRP, see OP header links. did you managed to install it? which TWRP you currently use?

mine is on N1, but I see there is even more fresh one - N2 (twrp)
[HTC One S] KuGeSch:
You're welcome ;) Thank you for the ROM!

I'm using TWRP 3.0.N1-0
[HTC One S] pavel.bosco:
so, looks like the file you attached is of start of version 2017.02.12, this is stated in line #3,

Matt Mower suggests to make experiment: try to rollback to TWRP M5 and reinstall the latest build, he said current TWRP version might need some improvement (or might not)
[HTC One S] KuGeSch:
status 2017.2.18

Experiment with TWRP M5 was not successful, neither was the attempt with TWRP N2

Cannot retrieve "last_kmsg" accordingly

Now I'm on TWRP N2 and 2017.2.12
[HTC One S] pavel.bosco:
at the early betas of this ROM I get last_kmsg from bootloops by booting to recovery right after such unsuccessful boot, and then copying /proc/last_kmsg by starting terminal (in recovery) and then execing

cp /proc/last_kmsg /sdcard

then you can mount it by MTP mode and upload to PC