yashsingh1/xdaforums huggingface dataset:
[HTC One S] pavel.bosco:
in attepmt to make device less laggy if lots of apps installed, I tried to apply patches from other kernel to zram

it's always hard to tell if this really helps, because it's first required to install new rom to try new kernel, and installing new rom itself makes phone faster and stable for some first days/months.

patch also deal with some race condition, not sure if someone faces exactly it or something else. I usually get my phone crashed at the underground metro, where signal is unstable, and also a lot of switches between mobile data and wifi, while I also pushed to see lots of ads videos, to get logging in into wifi, so it's kinda stressful for the phone, especially since I use chrome, which like to eat memory and cpu a lot.

anyway, here is the kernel. and atleast it boots up and works.

it adds the peak statistic

/sys/block/zram0/mem_used_max

which can be read to understand how much is taken by zram.

my guess is since original rom doesn't limit zram, it then can make system low on phisical memory.

so I always tend avoid to use "rich" apps, like aliexpress/viber/navigator installed all at the same time.

it also adds the limit to zram, but by default it's turned off (=0)

/sys/block/zram0/mem_limit

probably this is interesting for one who found out "one s" is quite limited in ram for modern apps.

keep in mind this is a test build.
[HTC One S] robgni:
there seems to be a problem with the voice detection. "OK Google" detection doesn't respond when phone is listening...
[HTC One S] ChristianFS1:
I may be slightly off-topic, but I just have to know:

Does anyone have any knowledge on battery life with this rom in conjunction with fresh and/or bigger batteries?

The phone needs to at least last through a single day, currently it won't last even close to that long with its original battery (used since may, 2012). While it would be nice to be able to last longer than that, it would be preferred for everything to just work out without any issues.

Do the One X and One X+ batteries last any longer than the stock 1650mAh unit on this particular rom (factoring in Project Volta, etc)?

Currently, X and X+ batteries are actually cheaper to get than One S batteries, so I'm kinda torn on what to do.
[HTC One S] KoMaSo:
I have One S with fresh batterys. All is fine it runs nere two days...

Matthias
[HTC One S] ChristianFS1:
Is it a 1650mAh battery or is it some higher capacity unit?
[HTC One S] freshmike:
Works better for me with this Kernel.
[HTC One S] KoMaSo:
It's an standard battery. I think 1650mAh.
[HTC One S] The Setlaz:
Hi guys,

New build with January 5 security patch. Download available on AFH

#Tested
[HTC One S] ChristianFS1:
Can confirm it's working, but it broke root access for apps (the only accessible options are "ADB only" and "disabled". What would you suggest?
[HTC One S] The Setlaz:
Have you tried reflashing superSU?
[HTC One S] ChristianFS1:
Will do. :good:
[HTC One S] transmetea:
hi

camera says " insert SD card to use camera"

folder explorer cant find nothing

but storage shows correct size
[HTC One S] Nomeji:
Thanks a lot for keeping updates on!

Does this build include the new kernel with zram tuning?
[HTC One S] Mbuuqw:
Just flashed this morning and it runs like a dream! Breath of life into this phone.
[HTC One S] DAOMAN:
And how to install this core?
[HTC One S] sorewinner:
[MENTION=2268315]The Setlaz[/MENTION], [MENTION=6095106]pavel.bosco[/MENTION] : Even with this phone's poor performance on Nougat, are there any plans to try & build Lineage 15.1?
[HTC One S] The Setlaz:
WTF are you talking about!?! :silly:

I'm afraid not... Just check how much trouble it is to bring manufacturer supported phone to LOS/PF... :eek:
[HTC One S] sorewinner:
Thanks for responding. Perhaps it's unfair to say "poor". Mediocre, then, due to its performance with a lot of apps installed. As to the second response, that's unfortunate. Thanks for the update, and for your regular builds.
[HTC One S] The Setlaz:
No problem!

Yes it's struggling with many apps, but now I just use mine as a backup phone with minimum things on it, and it behaves amazingly!

I'll put a new build up over the weekend with March security patch!
[HTC One S] freshmike:
Are there any LOS upstream patches included or only Android Security Patches?
[HTC One S] pavel.bosco:
Me too disagree about bad performance. It really hardware, which is not enough to run all the apps, 800mb is nothing today. this is main problem with phone performance - RAM size.

Also lot of today application bring services with them, which run always in background even you don't use them in foreground and don't even started youself.

I don't dive deep into new version releases, ie LOS 15, so mb I'm not fully correct, but afaik, google pushes too much into security and minimum required kernel version. Our kernel a bit outdated, it was stopped to support almost immidiately after HTC release.

Anyway, new version will not make this phone faster, or looks better, so why spend time on it?
[HTC One S] freshmike:
I don't think it's the RAM size as the Moto G3 has also 1 GB of RAM and people report good performance with Beta Orea ROMs on XDA better than with Nougat. I believe the CPU is just old not up the the task, the RAM type & MHz is probably also not the same as 1 GB on recent phones performance wise.
[HTC One S] sorewinner:
Ah, kernel is too old. That makes sense. Your last sentence, though, doesn't really compute. This forum is about tweaking and customizing software for devices. To say "why spend time" to put current OS on a device... Otherwise, device is dead.
[HTC One S] magur0:
The king is dead! Long live the king! :fingers-crossed:

Now as Resurrection Remix 5.8.5 Nougat for HTC One S stopped development (due to the upstream RR Team stopped working on nougat completely) it's the time of LineageOS to take over the future of this device! Long live the king! :laugh:
[HTC One S] kelleci:
Hi,

I have a request from developer if possible. Could you add wireguard vpn support to kernel?Or point me out how to compile it by myself?

Best regards.
[HTC One S] pavel.bosco:
new build

lineage-14.1-20180414-UNOFFICIAL-ville.zip

security as of Apr 5 2018
[HTC One S] freshmike:
U R a star Sir!
[HTC One S] NamenIos:
In case anyone is in the mood for something highly experimental: I have rebased most of the relevant parts from the Sony mint (Xperia T) in order to have a better maintainability, fixes for the CVEs of the last year or so and a better base for going forward to O. AdrianDC is very active and mint is an officially supported device. Kernel source I am using fastboot boot boot.img for now, boot.img download. You can check under about if the Kernel is compiled on the 16th. I would be very happy about bugreports with dmesg. For now not much should have changed on the outside, I still need to activate thinks like per process reclaim in the device tree and change the zram values etc. in addition to the todos in the commit message. The device tree is from March 21st, I would assume it is compatible with the latest version in this thread.

And sorry for the messy squashed commit, doing it right would take ten times the amount of work.
[HTC One S] KoMaSo:
Hi,

i have an selfcompiled Los.. from github without changes.

...only with the property PRODUCT_PROPERTY_OVERRIDES += "ro.config.low_ram=true from https://source.android.com/devices/tech/perf/low-ram" for Low RAM Devices...

If You set this many GApps runs very quicker... playstore starts in seconds and so on...

It feels better than your ZRAM for GApps.

Matthias
[HTC One S] NamenIos:
On Nougat and lower this is the same as using AdrianDCs low ram property patcher. You can use both, ZRAM and the low ram config and I would recommend both.
[HTC One S] NamenIos:
Latest state of my rebased Kernel: https://www.androidfilehost.com/?fid=890129502657599947

The source is on github as before (WIP part 4) with this commit cherrypicked: https://github.com/LineageOS/androi...mmit/4fad55ecee29cdb47596bbf09d97f6153438d436 For now it's 26hours uptime on one core, I will switch to both cores later to see if dual core is "stable" too. Per process reclaim and bigger zram activted in the ramdisk too. edit: and /proc/last_kmsg is working again.

edit: Two cores seem stable too (40 hours, the vmpressure restarts are gone). Testing is appreciated.
[HTC One S] freshmike:
Tried the low mem patcher, but had to disable as the phone kept crashing. But the initial mem was indeed around 400-500MB.
[HTC One S] KoMaSo:
hI, the only to do is edit the system.prop in /android/lineage/device/htc/ville folder an add the following one line at the end.

ro.config.lo_ram=true

Then build the ROM.

It is also possible to edit the build.prop in an installed rom to check...
[HTC One S] NamenIos:
In case someone wants to try the current state of my experiments: https://www.androidfilehost.com/?fid=962339331458990485 it's of course all on github, except I used the fusion3 gpu driver update from TheMuppets/sony/blue-common. low_ram is enabled by default and I would recommend a full wipe. Reboot to recovery doesn't work (it did before right?), last_kmsg and reboot to bootloader works.
[HTC One S] ginfreak:
i have my old htc ville c2 is there any way i can use this rom , im on hboot 3 and sense 5.. hope i can make this phone usable again thanks
[HTC One S] Flippy498:
[MENTION=6389186]ginfreak[/MENTION]:

Please read the warning that is stickied in this development section. For files that are compatible with your phone you should take a look at the development section that is dedicated to the C2 version of the One S.
[HTC One S] magur0:
Updates, any?

[MENTION=2928758]namenlos[/MENTION] how is your work progressing?
[HTC One S] Typhoon_Master:
my phone worked for 1 month with this rom fine.

since today i stuck in a bootloop. any suggestions?
[HTC One S] NamenIos:
Sorry for the late response, you tagged the wrong guy, it's a capital i in the middle not an L.

I stopped, I have had no feedback at all and I hit a block on vmpressure_prio crashes. But since a few days a user on another phone with an S4 quad reported the same problems. I got some clues what might be needed to fix that. Once that is fixed I'll see on how this progresses.
[HTC One S] magur0:
Thank's for the feedback [MENTION=3233991]NamenIos[/MENTION] ;)

I tried your latest release in a quick run but couldn't get it running properly (suffered from bootloops if I recall correctly)...

Let's see how thing's involve! Always nice to get new bits and bytes for the old phones abandoned by there manufactures years ago!
[HTC One S] kzaneo:
Hello,

I have a problem with Lineage 14.1 :

- My HTC Ville is unlock with HBOOT 2.16, S-OFF and CID-11111111.

- I have Wipe System, Data, Cache, Dalvik Cache and same Internal Storage

- I install this ROM

- I have a bootloop

- Same if it's S-OFF, i have flash boot.img, bootloop

Have you an explication and resolution please ?

Thanks
[HTC One S] sorewinner:
[MENTION=2268315]The Setlaz[/MENTION] [MENTION=6095106]pavel.bosco[/MENTION] : Any chance for a build? :)
[HTC One S] pavel.bosco:
hi, I can compile, but

see last commit from Dan Pasanen, of Dec 2017, I believe there are no much news since then

https://review.lineageos.org/#/q/status:merged+project:LineageOS/android+branch:cm-14.1

I don't think compiling it now will bring anything

upd:

uploaded

lineage-14.1-20180820-UNOFFICIAL-ville.zip

as I said, don't expect something "new"
[HTC One S] freshmike:
Andriod security updates?
[HTC One S] pavel.bosco:
yes, of Aug 05

https://review.lineageos.org/#/c/LineageOS/android_build/+/223007/
[HTC One S] freshmike:
Thanks for the effort!
[HTC One S] c19932:
does anyone know if streaming to chromecast work with this rom? Thank you very much!
[HTC One S] htc2019:
Would it be possible to compile a new release with the newest android security updates? :cyclops: :victory:
[HTC One S] KoMaSo:
Hi I have compiled an actual ROM from github (https://github.com/LineageOS/android_device_htc_ville) without any changes by myself . There are no changes since 2017 in the repository - only securityupdates from google. But I cant upload this. There are limitations in size in this forum for me.
[HTC One S] htc2019:
You could upload to an external service like mega or google and drop us the link here :fingers-crossed:

---

xda is just killing itself :silly:
[HTC One S] KoMaSo:
Here is an link with my final build for HTS One S. It contains securitypatches from dec 2018 and some memory optimisations in the "system.prop".

My additional entrys in the "system.prop" was

------"system.prop"------

# Sets Android Go recommended default values for propreties.

# Set lowram options

PRODUCT_PROPERTY_OVERRIDES += \

ro.config.low_ram=true \

ro.lmk.critical_upgrade=true \

ro.lmk.upgrade_pressure=40 \

ro.lmk.downgrade_pressure=60 \

ro.lmk.kill_heaviest_task=false \

ro.statsd.enable=false

----

I have submitted the device and therefore will not create new builds.

https://www.androidfilehost.com/?w=files&flid=288132
[HTC One S] htc2019:
Thank's a lot for your build! Would it be possible to get a updated (with newer android security patches) and compatible (dirty flashable) rom when taking the source from here https://github.com/LineageOS/android_device_htc_ville and adding your system.prop settings?

Looks like I need to learn how to build android roms :silly:
[HTC One S] KoMaSo:
The securityupdate is the last from 2018. I dont build an new rom because I have no device.

I have done this using the wiki for HTC M8 (https://wiki.lineageos.org/devices/m8/build) and change only the name M8 to ville in the commands breakfast und brunch.

breakfast m8 --> breakfast ville and brunch m8 --> brunch ville.

Think about to have an running device with running adb th get the drivers (blob) from the device. .... described in the wiki.

---------- Post added at 03:29 PM ---------- Previous post was at 03:28 PM ----------

oh, the rom ist clean and dirty flashable. I have tested both. there are no changes about this.
[HTC One S] freshmike:
Anyone actually tested this?
[HTC One S] KoMaSo:
I have tested this.

21 downloads until today, but no responses.
[HTC One S] htc2019:
Is someone skilled to make a new release from this base (dirty flashable) with the most recent security patches (may 2019) included? :confused:
[HTC One S] gappsfreeandhappy:
Soon it will be Christmas and I ask myself if somebody will gift us with new release (after one year of pause). No new features, just security updates (lineageoslog.com/14.1) to use this device many more ears :silly:

I don't know if their a still active people around [MENTION=9590461]htc2019[/MENTION] [MENTION=8264785]KoMaSo[/MENTION] @freshmike [MENTION=6095106]pavel.bosco[/MENTION] [MENTION=2268315]The Setlaz[/MENTION] @Flippy498 [MENTION=3233991]NamenIos[/MENTION] ? If so, scream out loud! :laugh:

Meanwhile the no link to the latest (one year old) rom for our beloved one s:
[HTC One S] Wingman2K:
Patchlevel 2020-04-05 is good enough

still have 2 of these, little bit short of Ram, buildprop modifyed as in upper post, no support ;)

lineage-14.1-20200523-UNOFFICIAL-ville.zip

have fun
[HTC One S] gappsfreeandhappy:
Wicked! You are the man! :victory: Thank's a lot! :good:

Looking forward to the build lineage-14.1-20210523-UNOFFICIAL-ville.zip :silly:
[HTC One S] freshmike:
Is still have one of these in storage, if anyone from the UK wants it for further testing and development I'm happy to donate it. got a new spare battery, never used too.
[HTC One S] cannondale0815:
Still works great today -- thank you!
[HTC One S] nogapps:
Dang! 2023 and this ROM/device combo still going strong!

If someone could drop a final android 7 release would be still great ;)
[HTC One S] whatagarbage:
It works! Awesome! The ROM is stable AND snappy 🏆

Any one is able to include recent patches by any chance?
[HTC One S] Flippy498:
[MENTION=6095106]pavel.bosco[/MENTION]: Be aware that this is only allowed if you give credits to the original author. ;)
[HTC One S] Fear of Oneself:
Is there a way to tell what firmware you have? I upgraded to Hboot 2.16 a couple of years ago, and I can't remember how I did it at all. All I remember was the complete wipe of my SD card. (And that it wasn't just a flashable zip)
[HTC One S] modal11:
This is a bit confusing to me too.

This gives you the Build number:

adb shell getprop ro.build.version.release

This gives you the build description which I suspect may be the firmware they are referring to:

adb shell getprop ro.build.description

The following will give you the baseband version:

adb shell getprop gsm.version.baseband

which should help you locate the correct RUU/OTA file for your phone.
[HTC One S] Flippy498:
Normally you would find it out by booting to bootloader and using fastboot getvar all. The firmware is stated in the line with version-main at the beginning. However, my fastboot getvar output is empty at that position since I flashed a TWRP version which was a bit broken and therefore deleted that entry, some years ago. (If I remember correctly it was one of the 2.6.x versions.) In addition that entry always changes, as well, whenever you flash a single firmware file instead of a whole firmware pack. This way the output may state version 4.x although you only flashed the hboot and not the whole firmware. That's why it's always better to flash the whole firmware and instead of only single files. Otherwise you can't find out the real firmware if you didn't write it down somewhere before you started tinkering.

The build.prop file only contains the information that got inserted by the rom cook. Therefore using build.prop entries for finding out the current firmware version is more than unreliable. A simple example: The current international firmware for the One M9 is 3.35.401.32. However, the latest ViperOne M9 rom states that firmware version 1.95.401.4 is used. That version doesn't even exist for the M9. It's a firmware version of the HTC 10 and since the rom is based on a HTC 10 port you'll get that "false" information whenever you look at the build.prop.

My advice to everyone who isn't sure which firmware he or she is currently using is starting from scratch. That means either re-flashing the unofficial firmware pack* that got distributed by Llabtoofer (version 4.06.401.1) or this unofficial RUU (version 4.05.401.1). It doesn't matter which one you use since both are compatible with every rom that got created for "hboot 2.16".

* It's located inside the "Install Package.rar". The firmware pack is actually nothing more than an unofficial RUU which lacks a system/rom and that fancy *.exe installer. Instructions for flashing can be found in the hboot 2.16 installataion guide that got linked on page 1.

Edit: And since I think we hijacked this thread more than enough with all this firmware off-topic I won't answer further firmware questions in this thread. If anyone still has any questions you can feel free to create a thread in the Q&A section and mention me ([MENTION=5872674]Flippy498[/MENTION]) there.
[HTC One S] The Setlaz:
I can see the proximity sensor being active when I'm on the lockscreen.

Is it the case as well for you guys ?
[HTC One S] Flippy498:
Yes, I can confirm that. And it doesn't seem to matter whether you place a thumb on it or not. I can unlock the phone in both cases.
[HTC One S] pavel.bosco:
I see this too,

btw Matt says the denials I see in dmesg are not critical, as long as nothing realy broken, likely the proximity problem is not critical too
[HTC One S] Fear of Oneself:
Thank you for the info! I ended up just following your advice and flashing again, just to be sure. I followed the guide in the OP, and made backups of my files. Not a huge deal, and now I know it's got a clean 2.16 and the associated firmware. Plus it's nice to clean out your SD card every once in a while. Rom flash after Rom flash, mixing AOSP and Sense scattered things up a bit. Thanks to both
[HTC One S] NH3:
Faster than 5.1.1 ?
[HTC One S] pavel.bosco:
it probably depends on how you are using it, and since there is no change in RAM and CPU, any performance changes in general are not so dramatic.

but it's smooth and responsive. and overall battery life is good, as they introduced 'deep sleep' back in 6.0.

for me it just a way to feel myself connected to recent technologies, w/o need to throw away more money

and latest branches of development have better support, so less buggy (in general) and probably more safe

#uploaded new version

lineage-14.1-20170123-UNOFFICIAL-ville.zip

Changelog for ville

Changelog for msm8960

Changelog for s4-common
[HTC One S] Fear of Oneself:
It's much appreciated. Running the new build right now.
[HTC One S] sorewinner:
Thanks so much for building N for our HTC One S! I'm having one issue, though. I clean-flashed coming from CM13.1 unofficial. Cache & data are F2FS, but system is not, since CM13 isn't compatible with that, & re-formats as EXT4, anyway. One error on completion about log. Flashed GAPPS. Booted. Everything seems to work, but audio isn't. Logcat shows:

audio_hw_primary( 699)
start_output_stream: cannot open device '/dev/snd/pcmC0D15p': No such file or directory
[HTC One S] pavel.bosco:
interesting. I didn't reformat, leave it as is, and the sound works in general.

do you mean you don't hear sound at all, or just in some particular use case? there might be problems with audio, code was changed, but I personally didn't see any problem with it

upd: checked mine setup, mine cache and /data are ext4. I can say I didn't loss my data between CM13 and LineageOS14.1, so looks like I was on CM13 with ext4.

upd2: I do see same error message in logcat
[HTC One S] sorewinner:
So, it's not that there is no sound. Ringtone, notification, & alarm sounds work, but any sounds that are located in "other sounds" do not. Meaning, lock sounds, phone key tones, etc. I clean flashed again to test, and even checked the partitions. It's weird, though. When the phone is first booted, if you quickly go into settings > sound, ringtones, notification, & alarms are completely empty. It just says "none" for all three.

EDIT: It shows "none" for sounds at first boot, because, from memory, logcat had showed that all OGG files (sounds) were considered invalid because the build type (or number) had changed, and a reindex was being scheduled. I really don't want to clean-flash again, just to determine if the word was "type" or "number", and the module that reported it.
[HTC One S] The Setlaz:
Actually I have the same problem. Strangely enough, it doesn't affect the "charging sounds"

All my partition are F2FS.
[HTC One S] pavel.bosco:
yeah, I confirm this happen. wasn't even notice this before, as I usually turn all of this 'other sounds/vibro' off right after first boot.

looks like sound config problems.

I reported the problem, hopefully it will be fixed quite soon.
[HTC One S] pavel.bosco:
you can try to made a changes described in

https://review.lineageos.org/#/c/158758/1

by hand, changing /system/build.prop and /etc/audio_policy.conf files

then 'other sounds' will come back
[HTC One S] sorewinner:
Yes, that fixes it. I added the one line to build.prop, and replaced audio_policy.conf. That fixed it.

Unfortunately, one more issue.

Videos are working, but youtube is not. I've tested with multiple browsers. Logcat shows:

chromium( 16631)
[ERROR: texture_definition.cc(177)] eglCreateImageHDR for cross-thread sharing failed: 0x300c

So, it's now a video config error.
[HTC One S] pavel.bosco:
yes, confirm.

but it works in youtube app.

I'll try to build latest sources, and try to see if it still there. Matt merged sound patches, unfortunately device is not supporting low_latency audio

upd

#uploaded new version

lineage-14.1-20170127-UNOFFICIAL-ville.zip

Changelog for ville

Changelog for msm8960

Changelog for s4-common

'other sounds' fixed

youtube video don't work in browser, but do work fine in youtube app.

btw a lot of debug settings were turned off by this commit: https://review.lineageos.org/#/c/157585/
[HTC One S] pirlano:
what kind of permission denials?