yashsingh1/xdaforums huggingface dataset:
[One (M9) Original Android Development] bubba1601:
Sense home 9.14 works fine on my M9 running LOS 15.1

Never crashed once or force closed.

The HTC oneM9 is an ARM64 device (arm8v) so why have you installed the ARM7V version of sense home on your device??? :eek:

Do you not know the difference between ARM64 and ARM7v?

ARM7v apps will not work on an ARM64 device as THEY ARE NOT DESIGNED TO WORK on a device with different processor architecture:eek:

Also, Lineage OS 15.1 doesn't have an aroma installer.

FYI

I'm using the ported HTC Sense apps by [MENTION=753984]xpirit[/MENTION] available from his thread here on XDA, and im using the ARM64 version of sense home from APK MIRROR.

(Remember the HTC One M9 is an ARM64 device, and not an ARM7v device)

Perhaps if you installed the correct sense home version for your device (ARM64/ARM 8V) your sense home would not keep crashing :eek:

If you are really not sure what processor architecture your device is, download droid info from play store, and it will tell you your device architecture but most HTC One M9s are ARM64, not ARM7v.
[One (M9) Original Android Development] HTCCM11/2:
**** and very mistake. I mistook the ROM with CRD (Aroma) installing different ROMs and just got mixed up with the version.

okay . on issues Sense Home - does not work any of the official installed from HTC (unmodified) version - crash. 9.14 I installed because it is the last before updating from htc changing the versions and layout of the screen application panel. The new version 9.60 can not be used - it is too close -5x6.

ARM v7. I am currently using the tel from the very beginning and it works like deflut apk htc, so I thought about transferring this version to Lineage 15.1 hoping for implementation and operation. The difference between v7 and v8 is obvious but I did not think there would be problems, the Arm64 version is from the beginning and only such applications are in the system.

What does the camera issue look like in Lineage 15.1.

I have not seen any module in this system, no application has even been installed.

Link to sense home

Link to Lineage 15.1 M9
[One (M9) Original Android Development] An3skmbi:
Please read the OP. It clearly states camera not working. Also has download links.
[One (M9) Original Android Development] HTCCM11/2:
Thanks , when it possible to get camera in lineage
[One (M9) Original Android Development] baddevil2:
Is there any progress on this?
[One (M9) Original Android Development] thisisapoorusernamechoice:
Any time I've tried to build since February began it breaks between 11-14%, always when the build starts on the kernel. I'll try again tomorrow so I can share the actual error message. (I'm replacing Ubuntu with Arch on my build machine but it's my first time so I have some kinks with setting up users). The last time I was able to build successfully was 26 January; I've used that build for several weeks now.

I can't really speak to what work needs to be done in the code. I'm pretty nooby when it comes to coding and I work 2 jobs so I never have as much time as I want to really go over the device tree in depth.
[One (M9) Original Android Development] ZVNexus:
Do

not

build

on

Arch.

Trust me. Its a pain to set up, way easier just to use 16.04 Ubuntu or 18.04.
[One (M9) Original Android Development] phpbb3:
I build aicp on arch without any issues, AUR even has metas/groups for building android. There is excellent information available on the arch wiki if you're having trouble getting started.
[One (M9) Original Android Development] ZVNexus:
How did you set it up? I just used AOSP Devel from the AUR. It builds until the end where it will segfault and corrupt.
[One (M9) Original Android Development] phpbb3:
Sounds like maybe its trying to use the wrong version of python, although I'd have to see the full error to know for sure.

Make sure you're using a virtualenv2 to ensure your bash session is using python2. Refer to this doc for details under "setting up a build environment"

https://wiki.archlinux.org/index.php/android
[One (M9) Original Android Development] ZVNexus:
That was my first problem when I initially tried to build. I got that problem fixed, Python 2.7.something, but now its just segfaults, due to the Ryzen segfault bug. It only happens on Arch based distros for some reason though.
[One (M9) Original Android Development] phpbb3:
Sorry, I'm not familiar with any of AMDs CPUs
[One (M9) Original Android Development] ZVNexus:
Yeah I wasn't either until I got one, in theory it is a way better performer than my old 3770K, but in practice it is extremely unstable.
[One (M9) Original Android Development] crnkoj:
Sir, you have to rma it. I had the same issue with a ryzen 1700, kept segfaulting in gentoo, couldn't even update system. After several "debugging" steps that were asked from amd and didn't fix the issue, they arranged for a free pick up and return of a new cpu, which never segfaults, even so when oced to 3900mhz on 1.275v and ram at 2933 2x16gb (sadly micron, not samsung b die).
[One (M9) Original Android Development] SunEater:
Any chances of getting official lineage 15.1????
[One (M9) Original Android Development] Claymore1297:
not in the moment, our device is also affected by the HAL1-problem (non working camcorder), which is mentioned in the announcement...
[One (M9) Original Android Development] Cường Hồ:
m9 has no new version

Gửi từ GT-N5100 của tôi bằng cách sử dụng Tapatalk
[One (M9) Original Android Development] ZVNexus:
I did RMA it. This is the second CPU I have gotten from an RMA, and both were after the 25th week. My current one is manufactured sometime in October. While this one segfaults way less, it still happens from time to time.
[One (M9) Original Android Development] annascott:
Other than that, are there any other issues that prevent the upgrade? What about the encryption problem, that got 14.1 pulled?
[One (M9) Original Android Development] Claymore1297:
Yes, the encryption problem is still present. I have no knowledge about any other problems, but I havn't checked the new LOS-charter in detail.

I think [MENTION=3082717]Flyhalf205[/MENTION] could giver here a better assessment...
[One (M9) Original Android Development] annascott:
Can anyone explain what's wrong with the encryption to someone who doesn't code?
[One (M9) Original Android Development] Claymore1297:
in simply words... hardware encryption ist broken on our device in LOS.

Here you can see the JIRA-Issue:

https://jira.lineageos.org/browse/BUGBASH-457
[One (M9) Original Android Development] baddevil2:
Is someone able to build this rom against latest sources?
[One (M9) Original Android Development] Claymore1297:
Yes, almost every day ...
[One (M9) Original Android Development] baddevil2:
Do you upload your builds or can give me a mirror? :)

Is camera still broken, as mentioned in first post? :)
[One (M9) Original Android Development] Eran baruch:
So that's it? RIP M9? No hope for LO 15.1?
[One (M9) Original Android Development] Claymore1297:
No, you are wrong! be patient young jedi! :)
[One (M9) Original Android Development] thisisapoorusernamechoice:
Did you ever hear the tragedy of Darth CyanogenMod the Wise? No. I thought not, it's not a story the Developers would tell you
[One (M9) Original Android Development] Anjelikk:
" Developers :)" - so does that mean official LOS 15.1 development is not gonna happen or what
[One (M9) Original Android Development] Vahid91:
Is it possible to port with HTC ONE 10 and fix the camera. ht___tps://yescrowd.optus.com.au/t5/Blog/Android-Software-Updates-21-02-2018/ba-p/390908
[One (M9) Original Android Development] xz123:
Building from source with the recent sources works, following the suggestions in the starting post (although I had to skip change 206531). The Android N signature spoofing patch could be applied as well, only one hunk failed which could easily be applied by hand. Runs rather nice, except for the camera and, which is a bit of a show-stopper: No sound, neither ringing nor in-call sound or anywhere else, lots of errors in the logs – none of which I can make much sense of, for I am rather new to all this.

Not sure if I just screwed up somewhere or if I should open a bug report; especially as m9-work seems to be somewhat stalled anyway.

/edit

Oh, btw: device encryption seems to have worked as well, although TWRP can't decrypt – but it boots cleanly into the ROM after requesting the password/pin/pattern.
[One (M9) Original Android Development] Saad Saleem:
EOL :(

Seems to be m9 isnt listed anymore for oreo on optus website
[One (M9) Original Android Development] Claymore1297:
You can take instead of 206531 this commit: https://github.com/Claymore1297/and...mmit/5abd4f2859f167cd4acc3fb8909e0a29ae59c49d

The sound is broken, because of various changes in our audio-hal.

You can integrate this commit to get audio working:

https://github.com/Claymore1297/and...mmit/24efeb135f2285883388574af4b150054010552e

The shim-mechanism has been changed in LOS, so it could be useful to pick also this commit https://review.lineageos.org/#/c/207174

EDIT: the encryption-fact is interesting, because HW-encryption is activated ... I'll check this later on...
[One (M9) Original Android Development] xz123:
That worked quite well, thanks!

Will your work be upstreamed someday, or should I focus on your fork as "where the development happens"?
[One (M9) Original Android Development] Claymore1297:
good to hear :)

Well more or less both. But the lead and main development on hima is on Flyhalf, but he seems to be quite busy these days...
[One (M9) Original Android Development] abbas_392003:
Hello friends

What should we do to work on this camera rom?
[One (M9) Original Android Development] danny2a:
Install today and it's works perfectly ! It's beautiful ! BUT, without the camera, I'm obliged to do a back machine, it's too important for me.
[One (M9) Original Android Development] UltraM8:
llabtoofer said that was a typo, they never meant to release oreo for m9
[One (M9) Original Android Development] xz123:
Honestly, I don't know. I'm still a bit in the dark about actually verifying/understanding the FDE-process of Android. I'm not even sure if everything is encrypted as it should be - I wish there was something like

cryptsetup luksDump

:D

I just built a ROM from the Lineage-Sources a few days back, tried the encryption option, rebooted and now Android as well as TWRP ask for a passphrase.

Unusual observations: TWRP can't successfully decrypt, and I can't change the decryption-passphrase independently from the screen unlock as I was used to (with tools like SnooperStopper): Both claim the phrase is not correct, while system boot works.

Interestingly, the system still boots with the most recent sources from your repo(s).

So, I'm sorry about not being much help at all :D

I'm up for some hints which parts of a logcat might shed light on this mystery, or how/where I might be able to check if/how/what actually is encrypted (maybe some

vdc cryptfs ...

-magic?)
[One (M9) Original Android Development] Claymore1297:
if your BoardConfigCommon.mk contains this line:

TARGET_HW_DISK_ENCRYPTION := true

you are on hardware-encryption.

run this command to get encryption-state:

adb shell getprop ro.crypto.state
[One (M9) Original Android Development] king786:
Hi does support the substratum theme engine

Thanks
[One (M9) Original Android Development] abdol haque:
Oreo
[One (M9) Original Android Development] nguyen4514:
I'm hoping someone can point me in the right direction. Since the M9 is not my daily device anymore, I have decided to get into building. I haven't attempted to do anything different from the build guide itself. I've tried to follow the guide in the original post, but I'm getting this error when running brunch himaul:

Starting build with ninja

ninja: Entering directory `.'

ninja: error: '/home/dennis/android/lineage/out/target/product/himaul/obj_arm/SHARED_LIBRARIES/libtime_genoff_intermediates/export_includes', needed by '/home/dennis/android/lineage/out/target/product/himaul/obj_arm/SHARED_LIBRARIES/libandroid_servers_intermediates/import_includes', missing and no known rule to make it

build/core/ninja.mk:151: recipe for target 'ninja_wrapper' failed

make: *** [ninja_wrapper] Error 1

make: Leaving directory '/home/dennis/android/lineage'
[One (M9) Original Android Development] Claymore1297:
on which OS you are building?

Your roomservice.xml is like in the OP and unser correct location?
[One (M9) Original Android Development] thisisapoorusernamechoice:
Don't run ./extract-files.sh that's what usually causes this problem for me
[One (M9) Original Android Development] Sabbir_Khan:
Was the 14th January version the last released...???
[One (M9) Original Android Development] thisisapoorusernamechoice:
PM if you want to try a new build, unsupported, at your own risk
[One (M9) Original Android Development] Anjelikk:
The m9 himaul and himawl builds are pulled from the official lineageos download page now apparently
[One (M9) Original Android Development] ZVNexus:
Yep its a difficult device to support, especially for the lack of users. Somehow the Droid Bionic from 2010-2011 still has Lineage 14.1 support with latest security patches lmao.
[One (M9) Original Android Development] StraightDroid:
It seems to be that the proprietary-files.txt isn't really up to date. I Installed yesterday the current cdma virzon rom. Extract the system (Firstline the lib, #part of - changes )

--------------------------------------------------------------

- /system/vendor/lib/libaptX_encoder.so

# Bluetooth

#removed???

------------------------------------------------------------

-------------------------------------------------------------

- /system/vendor/lib/libhwdaphal.so

# Audio libraries

# removed???

--------------------------------------------------------

--------------------------------------------------------

- /system/vendor/lib/hw/sound_trigger.primary.msm8994.so

# Listen

/lib/hw/audio.primary.msm8994.so:vendor/lib/hw/audio.primary.msm8994.so

/lib64/hw/audio.primary.msm8994.so:vendor/lib64/hw/audio.primary.msm8994.so

----------------------------------------------------

-------------------------------------------------

- /system/vendor/lib/hw/vulkan.msm8994.so

- /system/vendor/lib64/hw/vulkan.msm8994.so

# Graphics

# can this be right?

/lib/libvulkan.so

/lib64/libvulkan.so

#this replaced by android??

/lib64/hw/copybit.msm8994.so

/lib64/hw/hwcomposer.msm8994.so

# removed ?

- /system/vendor/lib/libllvm-qgl.so

- /system/vendor/lib64/libllvm-qgl.so

----------------------------------------------

- /system/vendor/lib64/librilqmiservices.so

# Radio

/lib/librilqmiservices.so

/lib64/librilqmiservices.so

---------------------------------------------

---------------------------------------------

- /system/vendor/lib64/libuiblur.so

# Graphics

# removed ?

--------------------------------------------

---------------------------------------------------

- /system/vendor/lib64/libprotobuf-cpp-fulm.so

- /system/vendor/lib64/libprotobuf-cpp-litm.so

# Protobuf

/lib/libprotobuf-cpp-full.so

/lib64/libprotobuf-cpp-full.so

/lib/libprotobuf-cpp-lite.so

/lib64/libprotobuf-cpp-lite.so

-----------------------------------------------------

---------------------------------------------------

- /system/vendor/lib64/mediadrm/libwvdrmengine.so

- /system/vendor/lib/libdrmdecrypt.so

# removed ???

# Widevine

---------------------------------------------------

Before this isn't fixed, we can not realy build any kind of stable rom. I'm right?

Forgotten to say - repo sync from today

ROM Version

"0PJAIMG_HIMA_WL_N70_SENSE80_VZW_MR_VERIZON_WWE_4.49.605.16_Radio_2.15.C1144077@70710_CNV_1.26_002_release_520623_combined_signed_2_4.zip"
[One (M9) Original Android Development] Claymore1297:
yes you are right ... the file isn't up to date...

Just add the muppet repo in you roomservice.xml (acording the OP) ... then you don't need the stuff you mentioned :)
[One (M9) Original Android Development] thisisapoorusernamechoice:
I didn't check my messages before posting so sorry I'm an idiot. Ugh I feel so stupid, please forgive me Claymore
[One (M9) Original Android Development] Cường Hồ:
Link , please, thanks

Gửi từ SM-J730GM của tôi bằng cách sử dụng Tapatalk

---------- Post added at 02:36 AM ---------- Previous post was at 02:16 AM ----------

Yesterday I installed lineage 15.1 11 03, double tap does not work [emoji23][emoji23][emoji23]

Gửi từ SM-J730GM của tôi bằng cách sử dụng Tapatalk
[One (M9) Original Android Development] rognlorie:
So....are we giving up here? I see there is no longer a dl link. I wish I could help but I'm ignorant of the language.
[One (M9) Original Android Development] Claymore1297:
Yes, thats right! On my builds camera is working...

Due the fact, that Flyhalf205 seems to be busy these days and the last build was uploaded 3 month ago, I will upload a build today later on...

I will delete this build as soon as Flyhalf steps in...

... I hope I don't get a bann for this...
[One (M9) Original Android Development] Claymore1297:
here are the download-links for my builds:

himaul:

https://drive.google.com/open?id=1xV8QVcMDEIwuXt9kXnZM6_vQDcEXd2vw

md5sum: 4a483d4cc231d3e16b1deee9b153e7fa

himawl:

https://drive.google.com/open?id=1ZuUq_yQ_NceonneXXaKYrANkvTqtPdwe

md5sum: dfbe02c65a3237ef1220dcf4ac664f95

The following is not working/ are known bugs:

1. video recording, due the hal1-problem. But there is a workaround use Footej Camera-App https://play.google.com/store/apps/details?id=com.footej.camera for video recording

2. sometimes Whatsapp-Videos can't played. The workaround here is, to kill the app, then videos can be played

3. last but not least device decryption is broken

4. ... and Updater-App only works in my WLAN ;)

This build supports (or should support) exfat, but I couln't test it yet.

As mentioned before, this builds will be deleted immediately, as soon Flyhalf205 steps in.

And I hope that I have not violated any XDA guidelines now...
[One (M9) Original Android Development] shaqman89:
Could you please share some pictures taken with this ROM?

Do you think it's the same as with sense rom is most cases?
[One (M9) Original Android Development] rognlorie:
I'm going to try this today! :good:
[One (M9) Original Android Development] xhoi287:
Hi

The rom that Claymore shared for himawl doesn't flash at all it gives error.
[One (M9) Original Android Development] Claymore1297:
can this anybody confirm?

Which error?

I have no himawl, so I couldn't test it ...
[One (M9) Original Android Development] xhoi287:
I dont remember what its says but as i remember was a warning and didnt extracted the zip files after skiping md5 and the flash got aborted.
[One (M9) Original Android Development] FlanFlinger:
I had the usual error 7 when installing but clearing the cache cured that, I get stuck on the very first setup screen, it keeps crashing. I did a clean install after a factory reset and it still does it.
[One (M9) Original Android Development] mariuszm22:
I'm testing ..... a big problem with Google play services (application stopped). The battery drastically falls down. The phone warms up very much.

Sorry for my English
[One (M9) Original Android Development] Claymore1297:
Ensure, that you make a clean flash, install gapps and then boot.

According to:

https://wiki.lineageos.org/gapps.html

I've test my builds on 3 devices (himaul), and no problems at all... :confused:
[One (M9) Original Android Development] Claymore1297:
so I tested the following:

Downloaded the himawl-ROM and edited the updater-script, so I could install the ROM on my himaul.

Did a factory reset (Wipe cache,data+dalvic) and installed the ROM.

It booted and I could pass the LOS-setup-wizard.

Can someone take a logcat?
[One (M9) Original Android Development] thisisapoorusernamechoice:
If you use magisk, try the Oreo version of this module: https://xdaforums.com/apps/magisk/module-enable-doze-google-play-services-t3608783

And as Claymore1297 already said, definitely clean flash when first installing the rom and gapps
[One (M9) Original Android Development] mariuszm22:
Thank you for answer. I have himaul. Wiped Dalvik / Art, System, Cache and Data. Installation without a problem. I installed pico gapps from 15/03 (108MB) and of course Magisk. I need root to restore TB applications. But I installed gapps after starting the system. I will try before.
[One (M9) Original Android Development] cel04:
[MENTION=274059]Clay[/MENTION],

the rome is top, everything is with me somehow, the battery runs almost 2 days,

so far. Camera and video recordings run top.

mfg cel

sorry google english
[One (M9) Original Android Development] mariuszm22:
The second installation ..... OS, then gapps ( nano) and the last Magisk ... and everything looks OK :)
[One (M9) Original Android Development] FlanFlinger:
That could be why it didn't install properly, I hadn't installed gapps, I was going to do that once it had booted.

Editerooo

All working now! :good:
[One (M9) Original Android Development] xz123:
Both are set, but from what I understood the latter is merely a flag that's getting set, not necessary a way to actually confirm encryption.

Even though everything still seems encrypted, things are still off somewhat: cryptfs checkpw or changepw still fail, and the logs during startup ( https://hastebin.com/otuyuwitir.hs ) or during any cryptfs changepw/checkpw-action ( https://hastebin.com/useyahiriz.hs ) seem to indicate trouble. Seems more like the device thinks encryption took place, but it didn't.
[One (M9) Original Android Development] Claymore1297:
are the himawl-builds working now?
[One (M9) Original Android Development] xhoi287:
Well i don't know i will wait for anyone with himawl to know if the rom will flash.
[One (M9) Original Android Development] rognlorie:
Room works good except you have to turn off 4g to receive phone calls so I deleted it but it is great
[One (M9) Original Android Development] FlanFlinger:
Working really well for a Beta :good:

Observations so far

Something funky with either gps or Google Fit, just been for a 4 mile walk and it's only showing just over a mile covered, but the steps count is high enough to reflect more than that distance covered.

Notification light stays on for some reason, but can't determine what's triggering it.

Notification sounds and ringtones are a bit jangly like they are in 14.1 (kinda fixed by unlinking them in the settings and adjusting individually)

Not noticed any issue with calls when in a 4g signal mostly because hardly anyone calls me :o
[One (M9) Original Android Development] xhoi287:
So flashing the rom in himawl doesn't have problem?
[One (M9) Original Android Development] FlanFlinger:
Sorry, I'm a himaul
[One (M9) Original Android Development] mazin mr:
I would like to install this rom

But i want to confirm somethings before installing

1. Is Fast battery charging (Quick Charge 2.0) supported in this rom

2.is the gestures "double tap to wake and sleep" is available in this rom
[One (M9) Original Android Development] Claymore1297:
1.) not sure

2.) yes
[One (M9) Original Android Development] schinge:
Do you know if your build supports VoLTE in the o2-de network? Or is this impossible on the himaul? As you surely know, on the stock ROM only the Vodafone branding supports VoLTE here in Germany.
[One (M9) Original Android Development] Claymore1297:
I'm not sure... I think, I've read that it's not possible, but I've never dealt with this, so maybe you have to try it, and share your experience here ...
[One (M9) Original Android Development] szaj:
I'm using this Rom three day in a row and I'm shocked.

Man this is probably the best build which was ever created on this phone. Animation are so smooth and sexy. Multitasking is perfect. There is no bad feelings inside of this. Camera working flawlessly, and in my opinion quality of photos is way much better thanbstock . Music quality is fantastic as well.

Bluetooth is working.

NFC is working.

I haven't saw nothing what is not work properly.

Thank you very much for this rom. This phone is fantastic once again.

Photos below

---------- Post added at 09:28 PM ---------- Previous post was at 09:21 PM ----------

https://imgur.com/a/ekNtU