yashsingh1/xdaforums huggingface dataset:
[One (M9) Original Android Development] mmortal03:
Any idea why I'd be able to successfully flash the 17.1 ROM (lineage-17.1-20200921-UNOFFICIAL-hima.zip, along with open_gapps-arm64-10.0-nano-20210414.zip),

but it won't get past the LineageOS loading screen on the 18.1 ROM (lineage-18.1-20210314-UNOFFICIAL-hima.zip, along with open_gapps-arm64-11.0-nano-20200911-UNOFFICIAL.zip)?

I'm using TWRP 3.5.2_9-0. It's a 32GB 6735A (AT&T model).
[One (M9) Original Android Development] multiwirth:
Are you sure you've chosen the right gapps?

Open gapps for android 11 isn't officially avaiable for now.

According to the date of september last year, it probably is an old gapps build for android 10(?)

Try the latest beta release, it should work.

Wrong gapps can cause many weird issues.

OpenGApps - Browse /arm64/test/20210130 at SourceForge.net

OpenGApps daily releases

sourceforge.net
[One (M9) Original Android Development] mmortal03:
Thanks, yes, that more recent gapps fixes the problem!
[One (M9) Original Android Development] mmortal03:
Weird quirk, but I just tested making a TWRP backup of 17.1 (the most recent claymore1297 unofficial build, 20200921) of the boot, system, and data partitions, then did a regular TWRP wipe, then tried restoring that 17.1 backup, and it wouldn't load LOS, instead landing me at the white bootloader screen. Tried restarting the phone multiple times, and it would just land me back at the white bootloader. I've never had this happen in my experience restoring TWRP backups on other phones.

The workaround I found was installing the 17.1 ROM fresh first, and then restoring the backup on top of that without another wipe in-between, but I've never had to do that before.

To be sure, I tried repeating all of this with *another* freshly created backup of 17.1, and the same thing happened, so this confirms that I didn't mistakenly forget to backup some partition on the first go-around.

Anyway, then I repeated all of this with a freshly created 18.1 backup, and had *no* problems whatsoever. So, I guess I'll just stick with 18.1, but I thought I'd mention it here in case anyone knows why 17.1 might act differently with TWRP?
[One (M9) Original Android Development] Pfony:
Hello mmortal03,

what you described is what I experienced also with LOS 17.1 and I posted it here.

The only thing that helped me in this issue was this and I posted it to support others having this issue.

It is good to know that in LOS 18.1 the backup seems to be working flawlessly as you described because I didn't dare to do it yet.

So thank you for letting us know about that and it completes my impression/experience of LOS 18.1 is the most reliable and best working ROM ever for my m9.

Thanks again to claymore1297 for making this happen (y):cool:.

Additionally there are 3 things that I wonder if this is going to be fixed:

1. under settings/privacy/trust/SELinux it shows "disabled....if I remember correctly in LOS 17.1 it was "enabled" and the only warning I got at fresh boot was a notification about "Build signature" and now with LOS 18.1 I got 2 warnings: SELinux and Build signature

2. built-in camera app: is it intended to not being able to select where to store the taken pictures anymore (internal or sdcard); I think on LOS 17.x you could select that

3. phone's LED notification light in the upper speaker: under (I do not know) what conditions it happens or gets triggered, but when I e.g. receive a message or calendar event I will get notified by the LED and then confirming/swiping the message/event the LED does not always turn off again, so it keeps the light on. Sometimes it works (light turns off as intended/expected) and sometimes it does not.

So is anybody else experiencing this?
[One (M9) Original Android Development] mmortal03:
A bug I just noticed in lineage-18.1-20210314-UNOFFICIAL-hima.zip:

Go to Screen Cast -> Settings -> dot menu -> Enable wireless display.

Then try selecting a Roku or a Fire TV device to cast to them as a wireless display, and LineageOS will hard crash, restarting the OS.

One thing I noticed after this crash happens, the Flashlight in the dropdown doesn't work and says the camera is in use. You have to restart the OS again to fix this. After the crash, the LineageOS Camera app icon also disappeared from my home screen and the app drawer, as well, even though it still showed up as installed under App settings. It has since reappeared after a restart or two.
[One (M9) Original Android Development] Refayatul:
Is there any rom for htc one m9plus?
[One (M9) Original Android Development] ace779:
When I update to 18.1 it renders my mic useless, I have himaul.

edit. was my fault mic works now
[One (M9) Original Android Development] mmortal03:
I see number 1 and number 2. It's not my primary phone, so I haven't seen number 3 happen yet.

Regarding number 2, it looks like it was a thing in 17.1 starting in November:

https://www.reddit.com/r/LineageOS/comments/k18b7z
[One (M9) Original Android Development] lymon66:
I am having a weird issue and it seems to point to Media Storage.

I can't clear/reset Media Storage data and/or cache through settings...it is all greyed out.

I can clear it using adb though (eg. by using the "pm clear" command)

Is this an Android 11 "feature" or a bug in this ROM ?

Also when trying to backup or restore media storage using Titanium Backup it hangs and even after force closing TB, the phone starts to behave weird.

it seems all access to internal storage (/storage/emulated/0/) is locked to everything and the phone needs to be restarted to be able to use it again.
[One (M9) Original Android Development] tombbb:
I just flashed 0513 build, so far so smooth and stable.
[One (M9) Original Android Development] Pfony:
the built-in updater does not offer the new built:

View attachment 5312799
[One (M9) Original Android Development] tombbb:
I downloaded it from link in op.
[One (M9) Original Android Development] mmortal03:
Same here, and I'm not familiar enough with hima yet, but I've seen this same issue on other phone builds. Just as a workaround, the Updater is simply downloading the .zip file to /data/lineageos_updates, so you can always manually download the .zip file and install it yourself with the recovery that you use.
[One (M9) Original Android Development] Pfony:
OK, I just downloaded and updated (unfortunately) "manually" and now the standard camera app is not listed in the apps anymore... But I still can activate the camera by double press on power button. Any idea how to get the camera app back again???

PS: does anybody know the changelog from this May update?
[One (M9) Original Android Development] mmortal03:
Try restarting the phone a few times. I had the camera app disappear on me, too, but it eventually came back.
[One (M9) Original Android Development] Pfony:
I already tried a few times...no success camera app icon still missing. But now (by chance??? or on purpose???) you can select again where to store the pictures (internal or sdcard):

View attachment 5316957
[One (M9) Original Android Development] m_abbas25:
I am facing a problem that I can't able to install big games like asphalt 9 via play store. Which requires obb file.

Manually you can install by placing file in Android obb folder using root access but play store refuses to install. I think this problem is for all lineage os 18. Can any one help me in this.
[One (M9) Original Android Development] Julian_B:
I think this "feature" is due to new scoped storage restrictions since Android 11. It has to be a general Android 11 issue.
[One (M9) Original Android Development] mmortal03:
Thanks! So far, it is working. :)
[One (M9) Original Android Development] Pfony:
Hi there,

great news, really. Is there any chance to get the update via the built-in updater working again? The "manual" way is so much time consuming o_O;).

Any news about "SElinux not enforcing" issue? 😇

Would be so great, thank you.
[One (M9) Original Android Development] Claymore1297:
Selinux will be enforcing next build
[One (M9) Original Android Development] multiwirth:
Well first, it's not recommended to use titanium backup.

It may work fine, but it could cause weird issues.

About the internal storage issue, i experienced it aswell.

It's a bug

Always had to reboot.

I'm usually building the roms myself and my last build from 2021.07.07 doesn't have this issue.

You should upgrade to the latest build avaiable from claymore, should be fine i guess
[One (M9) Original Android Development] lymon66:
Never had any issues with TB and it works/backups/restores fine for me.

I installed the latest build (20210710) and media storage bug is still there unfortunately
[One (M9) Original Android Development] platinumthis:
You mean this bug that you sometime cant see folders in Filebrowser?

I had this too, a backup and restore can maybe fix that, it usally happens when i restore /data sometimes from TWRP. If you guys mean this bug what i mention.
[One (M9) Original Android Development] lymon66:
Since installation of build 20210710 I have a new issue: in some cases I get no sound during call: the one calling me can hear me, but I can't hear the caller ... if I switch to speaker it works and I can hear the caller.

When this issue happens and I call back or call another number, I get the same thing...I can see on the display the call is active (counter is running), but I don't hear anything unless I put the call on speaker.

Restarting the phone *sometimes* fixes the issue, but not always.

edit: never mind...found the issue. it's a faulty earpiece. If I press hard on the casing where the earpiece sits, it works again for a few seconds.
[One (M9) Original Android Development] lymon66:
No, the bug refers to media storage (in system apps) , you can't clear it's cache or storage (eg. to rebuild the ringtone/notification sounds database).

You can't make a backup of this database either without (indirectly) crashing the phone
[One (M9) Original Android Development] Pfony:
Hi everybody,

there is still the (built-in) camera-app-icon missing so I have to start the camera by double press on power button (also latest built from july). (No, even dozens of restarts didn't help).

Two issues unfortunately still annoying in camera app:

1. start up time is very long from double press on power button till actual camera app is ready (some spontaneous photos got never been shot 😭)

2. if HDR is enabled before taking pictures the camera app sometimes crashes saying something like "media server died, could not connect" or "could not connect to media server" something like this. If I already have camera app started then go to standby and some times after I want to take a picture the app crashes more frequently so that I have to "force stop" the app and open it again. But this behavior is also experienced without HDR enabled.

Concerning the "Location" functionality: I still wonder if this is a (wanted) feature to not beeing able anymore to select what kind of location type you want. In the past LOSs (I think 16.x, 15.x, ...) you could chose between "device only" and 2 other methods. Now since there is only "on/off" my navigation app (osmand~) takes a very long time to determine the current position (it downloads some map material !?).

Any ideas on that?

ps: will the OTA updater work again for next built ? 🙂🙃😉
[One (M9) Original Android Development] lymon66:
I had similar issues with the standard camera app crashing for no reason.

Since then I installed "Open camera" from the play store as my default camera app and it has been working fine (it also has a lot more options).

NB: make sure you enable opencamera as the default camera app, otherwise the stock camera app will still interfere.
[One (M9) Original Android Development] multiwirth:
You could try to wipe the app data and cache from camera.

Maybe something got messed up during updates idk.

I have 3 m9 and none of them have an issue with the default camera 🤔
[One (M9) Original Android Development] iamleobn:
Is there a reason why not a single custom ROM for this phone has working FM radio?
[One (M9) Original Android Development] multiwirth:
Well all custom roms use more or less the same or a forked version of the same device tree.

Which means all bugs are the same across all roms.

And since Claymore is maintaining almost all current avaiable ROMs, he´s using the same sources for all roms.

Unless he or someone else finds a fix for fm radio, none of the avaiable ROMs will have working fm radio.

And to be honest, i doubt this will ever get fixed as most people simply don´t care about fm anyways 🤔
[One (M9) Original Android Development] platinumthis:
This is not true, Ice rom or Revoltion rom has FMradio (sense roms)

Also iam trying to get FMradio to work but for now i was not abel to, some time will pass and then it work.
[One (M9) Original Android Development] multiwirth:
As you already said, those are stock sense based roms so no surprise fm radio is working there.

But this is not an AOSP based custom rom, it´s a modded stock rom 😉
[One (M9) Original Android Development] iamleobn:
Is there any way I can help? I've never developed anything for Android, but I am a software developer and I happen to have a spare M9 lying around. Do you have any idea where I would even start?
[One (M9) Original Android Development] multiwirth:
Well if you're familiar with linux, it would be a good start to get a rom built from source first.

I could send you my manifest and some instructions via dm or telegram.

But i'm not a developer myself, i'm just building from time to time and help testing stuff so i can't give you exact instructions but maybe some hints where to start.

First you'll need to enable fm radio apk for build routines since you cannot simply install the apk later (i tried that).

Unfortunately idk how to do so atm but maybe i can find some documentation about which values have to be changed in configs

Then you could try troubleshooting the issue by grabbing a logcat.
[One (M9) Original Android Development] multiwirth:
So i did some research and i looked at some stuff from M8 and i successfully built a rom including the fm radio app (FM2)

I don't know if it's the right one though, since as far as i remember there were two packages avaiable depending on what fits better to the device.

Check out this commit:

add FM2 package to device.mk to build fmradio app · multiwirth/android_device_htc_hima@57f748c

Change-Id: I2af9c35daa8711826b05ba64c8a1e33222a25dda

github.com

However, as expected fm radio doesn't work.

I also uploaded my build including FM if anyone is interested in troubleshooting:

Downloads for : HTC One M9 | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.

Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.

www.androidfilehost.com
[One (M9) Original Android Development] janeku:
Hi guys,

Maybe it is not a proper place to ask, but despite 18.0 is a good ROM, I had to back to my stock ROM .

In boot section it says :

HTC HIMAUHL

Radio 01.01_U14401011_117.00.61117G_2

Open DSP 20.7.3.00535.8994_1012

OS 4.23.710.1

Where I can find this stock rom ? I tried almost everything there was only one ROM that was accepted by my phone and this ROM has encrypted my phone when I installed so I had to re-install LOS in orther to get back my phone.

Thanks in advance.
[One (M9) Original Android Development] Julian_B:
You could also go with a stock based ROM like ViperOneM9 instead.
[One (M9) Original Android Development] janeku:
I know but main reason is of technical problem: wifi is not working (mechanical-electronic issue) so repair man ask for original rom to be installed in order to be able detect it properly and replace wifi module with new one (that is what he says). Else I will have to put it in recycle bin forewer (that is what I do not want).
[One (M9) Original Android Development] janeku:
I tried and now it says my phone is encrypted. It asked for pass and when I try enter pass, it says it is ok but phone is encrypted and needed to restart. When I tryi to go back to twrp it start it, but it run some script and I can't get to twrp and it takes me back to encryption info page.
[One (M9) Original Android Development] Julian_B:
Did you wiped everything in TWRP before the install?
[One (M9) Original Android Development] Ibrahim924k:
guys i just installed this rom but i am facing a problem. whenever the device boots up fully into the system it just hot reboots after a coupkle of seconds and it just keeps going on. i have installed the rom two times but still have the same problem.
[One (M9) Original Android Development] WizzTech:
I have just installed it too. No probs.

Did you install latest version?

Did you wipe data?

Edit: Spoke too soon. Although I can boot into the rom (takes a bit), I now can't boot to recovery anymore.

Not sure where I went wrong.

Trying to install SKD now to try and install TWRP via ADB. Massive PITA. xD

Another issue is my win10 Machine doesn't seem to recognize the M9 when plugged in.

Machine at work was recognizing it and machine at home recognizes the tablet. :S

Shoulda stuck with AICP 15. xD ahahah

Edit 2: Finally able to flash TWRP again, had to disable driver signature on win10, install naked drivers for the device to finally be recognized in Download mode.
[One (M9) Original Android Development] Ibrahim924k:
the reason why u werent able to boot into twrp was because in the setup process they ask u to update the lieage recovery alogside the os. that option actually corrupts twrp. ad i have tried everything but i am still facing the same problem. I boot into the software without any problem but as soon as i boot up my device hot reboots. still not sure what is the issue.
[One (M9) Original Android Development] Ibrahim924k:
another problem is that i cant setup my screen lock.
[One (M9) Original Android Development] Ibrahim924k:
ok i think i f***ed up because my device is himawhl and if i am correct this build is only for al and wl but still my device manages to boot up and i only face the hot reboot problem if i try to setup a screen lock

edit: if i stay away from screen lock settings my device works like a charm and i can do anything on it like use it normally.

edit 2: i was wondering if i can install the elemental x kernel because it was oficially supported on the sense rom or if there is any kernel available for this particular build.
[One (M9) Original Android Development] WizzTech:
Didn't think I selected that but you might've been right.

Yesterday I had some stability issues (SD card related - formatting as internal storage).

Formatting the sd card as ext storage and today the device ran all day very stable.

Unfortunately tonight I attempted to replace the battery, in doing so I slightly damaged one of the zifs, and now after putting the device back together, I'm not getting any signs of life.

It vibrated a bit when pressing power at first, but no image on screen whatsoever (plugged to mains obvs), and now no sign at all.

I guess this is goodbye. Thanks for everything and good luck M9ers.

Ps: the computer detects it still.
[One (M9) Original Android Development] Claymore1297:
#### New build is up!! ####

the build is containing mainly the following:

-august ASB's

-SELinux enforcing

-last Lineage fixes

Enjoy!
[One (M9) Original Android Development] danjde:
Hi Friends,

does support this release encrytion data partition, twrp side too?

Thanks!

David
[One (M9) Original Android Development] Salbingu:
I did everything like in the tutorial. the phone gets stuck on the logo HTC.

Help
[One (M9) Original Android Development] Salbingu:
Hi. I did everything as on tutorial but i can not boot. Stuck on htc logo.

Help please
[One (M9) Original Android Development] Pfony:
Thanks a lot for the new build and keeping my favorite phone truly up to date !!!

I especially appreciate the SELinux enforcing being back.

Just for your information my whishes for future builds 😇:

1. Camera app (built-in) (already reported here)

1a) camera app icon still missing; start up time (by double press on power button as the only way) is still veeery slow >7sec (I just compared with a friend's AICP 13.1 (20190228) installation (on excact same phone model) which is superfast almost 1sec; in current build app also crashing a lot and it seems that there are 2 different instances of camera app started (lockscreen vs. unlocked condition) so these 2 instances possibly interfere and lead to a program crash?!!?🧐🤨

2. Sound issue on signal-messenger: when playing a received voice message and setting the speed to 2x the sound is very "cracky". Also compared this to AICP 13.1 (20190228) installation (on excact same phone model) and there is crystal clear sound playback on 2x speed.

3. built-in updater was not showing the new update for august update (already reported here); can't confirm nor deny for august built since there is obviously no newer built right now ☺️

Anybody experienced similar behaviour in august build?

Nevertheless: GREAT WORK on this rom. Please keep up the amazing work.

ps:

Could you give a brief preview on what's planned to fix/implement for next build 😇?
[One (M9) Original Android Development] :
Yes
[One (M9) Original Android Development] :
Flash latest TWRP version (twrp-3.5.2_9-0-hima.img)

In TWRP select - Wipe - Format Data - YES

Reboot in TWRP & select Wipe - Advanced Wipe - Select ¨ Dalvik, Cache, System, Data, Internal Storage¨

Flash the ROM

Reboot

(If u need Gapps flash it now, after flashing ROM and reboot)

Flash Magisk
[One (M9) Original Android Development] :
1 - only occurs after flashing Magisk, after re-downloading another Magisk.zip from official site never occurred again

2- don't use Signal! It's not secure lol (Telegram / Antox / Wire are way better)

3 - Have you tried a clean install? Sometimes some bugs occur when dirty flashing
[One (M9) Original Android Development] mtotheax:
Hi

everything was working fine. then I decided to encrypt the phone and now its in a Bootloop.

If I try to enter recoverymode, It goes back into the bootloop. Downloadmode is working but I can`t find it with adb devices like before. the Computermanager (win10) finds it but I cant do things with it. got sombody any ideas ? or is the device dead? ITs ok it was a " fun Projekt", I just dont want throw away a device thats savable.
[One (M9) Original Android Development] Jupp Pütta:
Do you have any source that suggests why Telegram should be better than Signal? Don’t want to discuss this here, as it is off topic, but a simple link would be nice, as it is opposod to everyting I know. Thanks.