yashsingh1/xdaforums huggingface dataset:
[One (M9) Original Android Development] Anjelikk:
Even though i dont have ui lag like he said, he's right, and i'm now curious if anyone else has seen this and if the problem can be fixed.. And at least for me, on cpu-z the gpu load is stuck on 0%, even though in developer options the statistics show the gpu working
[One (M9) Original Android Development] massatt212:
I did a Clean wipe cashe system internal data the cleanest

Flash new rom along with Gapps pico 8.1.0 ARM 64

when im doing a lil multi tasking while music in the background music will start to stutter or if apps updating stuttering

sometimes music player freezes completely and i have to reboot phone or hard shut down

The sound quality is almost the same until i go and adjust it in the audio FX app

The rom is pretty well

The stock camera is better well for me

Dont want to nit pick but Simple problems but i love the rom also AICP love it also

1 think ill Love to see is Huge Improvements on Vulkan API (3D Mark testing)

Sorry for bad english
[One (M9) Original Android Development] root-expert:
The GPU is supposed to be in 0% usage when you are just using the UI. SurfaceFlinger, the service which renders the UI elements, doesn't use the GPU when it want to renders the UI, because 1) the GPU is not optimized for that and 2) every time SurfaceFlinger uses the GPU, other apps are unable to use it to render their stuff.

That's why Hardware Composer (HWC) exists, to render the UI elements without bothering the GPU.

You'll see the GPU to spin up when you are running a game or another heavy task which GPU is supposed to handle it.

-Chris
[One (M9) Original Android Development] Anjelikk:
Ok, thanks for clearing it out for me!
[One (M9) Original Android Development] _mone:
[MENTION=8276284]Claymore1297[/MENTION] [MENTION=460472]eyosen[/MENTION] [MENTION=3082717]Flyhalf205[/MENTION]

First of all thanks a lot for the amazing work you have done on device tree and kernel.

Any reason why you are using 2 different trees for himaul and himawl? Even using same kernel and same blobs for both?

Can this be of interest? > android_device_htc_hima

If anyone is willing to test, here a build compiled using Claymore1297's sources apart from the repo linked above:

lineage-15.1-20180621-UNOFFICIAL-hima.zip

^ working just fine on my himauhl, no idea if it works for other variants too. This build

should

work for: himaul, himauhl, himaulatt and himawl.

Regards,

_mone
[One (M9) Original Android Development] boredherobrine13:
I tested to see if it would using benchmarks like AnTuTu and 3DMark. It never did, just sat at 180Mhz and the benchmarks lagged like crazy.

---------- Post added at 02:30 PM ---------- Previous post was at 02:28 PM ----------

I'll test it on my himaul. (It should work on all of them because I know for a fact that if you have S-OFF you can actually change which edition your phone is, I changed mine to himaul with CID) Edit: It does work fine, and it seems to have eliminated the GPU issue. Granted I did a clean flash rather than a dirty flash so that might have been the issue too.
[One (M9) Original Android Development] xhoi287:
There are some bugs within instagram camera it doesnt work everytime and the new feature of videocall in instragram doesnt work.
[One (M9) Original Android Development] haguilar91:
Audio Issues

Hi, I modified the zip and all is working on the Sprint M9, the biggest issue is audio lag and popping when playing media.
[One (M9) Original Android Development] The_Walking_Playground:
Hi [MENTION=8276284]Claymore1297[/MENTION],

I was able to encrypt my device, like the user above, on the latest version you posted. However, if I set a password/pattern/PIN on boot, and then change it, it keeps the initial one I chose, rather than updating to my current one. Also, if I choose a pattern larger than 3x3, or select one of the other size options and then select 3x3 again, the grid shrinks down to an unusable size, and I can't decrypt the device. Is there a way to fix this issue? Now that official TWRP supports decryption, I'd like to be able to use a larger pattern to secure the device. I'm also not sure if TWRP supports patterns larger than 3x3. I tried it once and it wouldn't decrypt (maybe the algorithm was changed, and TWRP needs to be updated?).

TWP
[One (M9) Original Android Development] Claymore1297:
can you please name me your exact device-version and firmware, you are using.

Only one of my himaul(s) (a himaulatt) are able to encrypt by using hw-encryption.

Due you issue ... can you provide a log when you are changing the pin/pattern?
[One (M9) Original Android Development] The_Walking_Playground:
Hi,

Here's the output of fastboot getvar all for my device:

(bootloader) kernel: lk
(bootloader) product: htc_himaulatt
(bootloader) version: 1.0
(bootloader) current-slot:
(bootloader) version-main: 4.30.617.12
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440971_103.00.61018G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA11000
(bootloader) cid: BS_US001

Attached is a logcat from when I'm changing the pattern to a PIN on the device. When asked if I want to do "Secure start-up" I choose Yes. The weird thing is, after a reboot, I have to unlock the device with the original pattern, and then unlock the lock screen with the PIN I just chose. Please let me know if you need anything else!
[One (M9) Original Android Development] Claymore1297:
I expected this ... same device and firmware as mine ...

Hm, I see some SELinux denials, will try to get around them and include in the next build ...
[One (M9) Original Android Development] lebo97:
Excuse me, [MENTION=8276284]Claymore1297[/MENTION]. Can you add "Soft reboot" in Advance restart??? Like future ones in Xposed Manager. (NOT "reboot system UI"). Thank you... THANK YOU VERY MUCH for your support for this rom.
[One (M9) Original Android Development] Claymore1297:
#### New build is up!! ####

himaul:

https://www.androidfilehost.com/?fid=5862345805528044692

himawl:

https://www.androidfilehost.com/?fid=5862345805528044735

the builds are containing mainly the following:

-july-ASB's

-whatsapp video-playback/videocall-bug solved

-camera on apps like snapchat work properly

Enjoy!
[One (M9) Original Android Development] xlayn:
Thank you very much for the effort you and all the community has put on this rom!!!!
[One (M9) Original Android Development] Simon94:
Are you working on encryption? I get a M9 these days and could assist with testing that stuff, although i'm not very skilled in those android-internals. Flashing and crashing is what i could offer :)

Best

Simon
[One (M9) Original Android Development] Claymore1297:
I was - together with [MENTION=9159293]nimbius[/MENTION] - I'm currently busy with some other improvements. Maybe it is a firmware-related issue ... as you can see in thread, it works on a himaulatt with latest firmware...

I will try to test some more things in the near future and let you know :)
[One (M9) Original Android Development] Crackfreak:
Definitly reccomended as daily driver

this rom gave new life to my M9.

haven't seen any bugs or noticeable issues. I've installed stock HTC camera from play store and it's amazing.

Thank you so much for your work.

btw can I dirty flash the latest update?
[One (M9) Original Android Development] phpbb3:
Dirty flashing should not cause any issues, however take a backup first, and be sure to clean flash if you have issues.
[One (M9) Original Android Development] Cường Hồ:
What is the mode on the go? thank you

Gửi từ SM-G610F của tôi bằng cách sử dụng Tapatalk
[One (M9) Original Android Development] chayxe:
google assistant

How do I summon Google Assistant.

Pressing and holding the home button turns the screen off
[One (M9) Original Android Development] Claymore1297:
I use this setting, so I set it on my ROM as default ;)

You can change this very easily in settings->system->buttons->Home long press action
[One (M9) Original Android Development] comolik:
Thanks [MENTION=8276284]Claymore1297[/MENTION] for working on bringing LineageOS 15.1 to himaul. Did you consider to make it official anytime soon? Seems like [MENTION=3082717]Flyhalf205[/MENTION] went MIA and won't continue the work. Would be awesome to finally have an official LineageOS build for himaul again. Especially since a lot of people still run the outdated 14.1 builds that stopped being supported with a lot of security issues in them.
[One (M9) Original Android Development] Flyhalf205:
I also wonder this question? :)

and second question...Does encryption work?
[One (M9) Original Android Development] phpbb3:
There is this for your second question:

And as far as I understand, LOS will not re-add support for himaul, however AICP is under active development, and Claymore is 1 of the maintainers!
[One (M9) Original Android Development] comolik:
Why do you think that LineageOS will not re-add support for himaul? To my understanding it needs nothing more than a developer (or better: two) taking the responsibility. Since [MENTION=8276284]Claymore1297[/MENTION] already does the work and publishs it here on XDA, I'd like to encourage him to make it an official LineageOS port (again) :)

[MENTION=3082717]Flyhalf205[/MENTION]: So is it correct that you won't continue working on the LineageOS himaul port? In any case: thanks a lot for your past work on it, it is really appreciated!
[One (M9) Original Android Development] phpbb3:
I could well be wrong, thus saying "as far as I understand", but I believe encryption is not yet up-to-par for los, and may never be. LineageOS has much more stringent requirements to be an official device compared to aicp and other ROMs.
[One (M9) Original Android Development] woodman:
Hello,

[MENTION=8276284]Claymore1297[/MENTION] is now the OP of this thread :)

Regards,

Wood Man

Senior Moderator
[One (M9) Original Android Development] phpbb3:
But there is also this:

https://jira.lineageos.org/plugins/servlet/mobile#issue/BUGBASH-457

The last few comments show I may well be quite wrong ;)
[One (M9) Original Android Development] Crackfreak:
Thanks for the news :D

People would love an official build based on this rom and it's already my daily driver.

I have nothing but respect and gratitude and github stars for the developers. :cool:
[One (M9) Original Android Development] Claymore1297:
#### New build is up!! ####

the builds are containing mainly the following:

-audio-issue which causes random reboots solved

-panorama-mode in snap work properly

-Kernel is patched to the highest patchlevel (EOL=End of Life) on 3.10, which is v3.10.108

*due the audio-issue:

this issue causes random reboots, while playing music with a player like the buildin eleven.

This should be the same issue as the random reboots on bluetooth-connections

I've updated the OP and you can find my builds in the AFH-Link.

I've also updated the build instruction for the selfbuilders out there :)

OK folks, lets talk about officials...

LineageOS has a new charter, which should garantee several level of quality:

https://github.com/LineageOS/charter/blob/master/device-support-requirements.md

So, curently we are hitting this by 2 cases:

1. hardware encryption:

Yes, as reported below, hw-encryption works on this ROM, when the device is a himaulatt and has got the latest firmware (4.30.617.12). [MENTION=9159293]nimbius[/MENTION]: can you confirm this, or have you got an other firmware-version.

I could not test this forther, because I was busy to solve the remaining issues on this ROM, to make it stable for everyone.

If you want to help. you can try to encrypt and report here or PM me directly which device and firmareversion you are using and if it's working.

We are not finished with this, and will try to solve this issue...

2. video-recording/camcorder:

the current solution of camcorder is not mergable and so this would be an other point we are hitting the charter. [MENTION=6052895]root-expert[/MENTION] (Maintainer of HTC One M8S) and I will try to find a better solution, but I can't say, if we will get success.

So our current state is, that we can't get official, as long we can't solve the issues mentioned above.

In my opinion the only difference to a official supported ROM is the following:

- the ROM is not build on LineageOS-jenkins

- ROM-files aren't signed

- Updater don't work

But I can ensure you ,I'll be here and support hima - because it's also my daily driver! So you don't have to worry about this!

I'll be providing minimum 1 build in a month, so you get the latest ASB's.

If it is important for you to have an official ROM, you have to switch to AICP - on which I'm one of the maintainers, and I can assure you

the device codebase is 99% the same!

So there is absolute no need for it.

And just to clarify, when this would be an official ROM, the only one who would solve bugs on it or something like that, would be me (or the corresponding maintainer,

as [MENTION=3082717]Flyhalf205[/MENTION] did the last years) - exact as I do it right now!

Enjoy!
[One (M9) Original Android Development] kunalxda:
Hi dev can you add dts eagle latest caf by lazerlord in kernel for both linageos and aicp https://github.com/lazerl0rd/dts_project thanks in advance
[One (M9) Original Android Development] Claymore1297:
one of my next tasks...
[One (M9) Original Android Development] Evengard:
Thank you a lot for this new build! I will test it extensively. Was waiting for it this morning, as was having theese damn reboots and bluetooth disconnects =) I hope it will go away now.

I will write you back with some other problems I'm having, but nothing critical. Still, some of them may also hit the device-support-requirements...

Anyway, big thanks for your work!
[One (M9) Original Android Development] annascott:
Thank you [MENTION=8276284]Claymore1297[/MENTION] and everyone else who's involved in the development!!! I flashed this morning, and the bluetooth connection seems to be working perfectly! I will update if I run into any problems.

Also, is anyone still having problems with the led indicator for charging? It seems to be a hit and miss on my phone. Is there anything I can do about it other than a clean install?
[One (M9) Original Android Development] root-expert:
Hey, can you specify what:s your problem with led indicator?
[One (M9) Original Android Development] annascott:
[MENTION=6052895]root-expert[/MENTION] it won't turn on to indicate it's charging. It's a hit and miss, sometimes it does, sometimes it doesn't.
[One (M9) Original Android Development] root-expert:
When the led doesn't turn on do you have a notification? If yes then that's the problem.
[One (M9) Original Android Development] annascott:
[MENTION=6052895]root-expert[/MENTION] nope, when it works and I have a notification it just switches between colours, when I don't have a notification and it doesn't work, the led isn't on at all.

I had the same problem in 14.1 official, no problems in stock.
[One (M9) Original Android Development] phpbb3:
I can confirm this as a problem in every AOSP-based ROM I've used with this device. It does seem to be totally sporadic.
[One (M9) Original Android Development] 1234What:
Hello everyone, :)

Does anyone here using the Expanded desktop feature in the Display settings? I got a weird case where phone screen doesn't turn on after minutes of turning off the screen.

I'm using the latest build - lineage-15.1-20180717-UNOFFICIAL-himaul-

Does anyone experienced this one or I am the only one?

Thank you :)
[One (M9) Original Android Development] DonJDelago:
Installed the AICP Build last night on himaul. Works nicely! You guys may consider to give it a try at http://aicp-rom.com and donate a few bucks to keep the servers alive...

Thx [MENTION=8276284]Claymore1297[/MENTION] and cheers from Frankfurt am Main ;)
[One (M9) Original Android Development] shimbob:
Installed 15.1 on my himaul, clean flash. I'm unable to send text messages, it reports: "cant send message with CARD 1, error 96"

It was able to send text out before and it just stopped working.

Here's the logcat output that shows up between the moment I tell it to retry sending and it fails.

07-20 08:22:15.097 775 904 E LightsService: Light requested not available on this device. 2
07-20 08:22:15.279 4111 21820 I MessagingAppDataModel: ResendMessageAction: Resending message 31; changed timestamp from 1532100087082 to 1532100135279
07-20 08:22:15.296 4111 21820 I MessagingAppDataModel: ProcessPendingMessagesAction: Scheduling pending messages
07-20 08:22:15.315 4111 21820 I MessagingAppDataModel: ProcessPendingMessagesAction: Queueing message 31 for sending
07-20 08:22:15.392 4111 21824 I MessagingAppDataModel: SendMessageAction: Sending SMS message 31 in conversation 11
07-20 08:22:20.494 775 897 E LightsService: Light requested not available on this device. 2
07-20 08:22:20.606 2878 3534 I Icing : IndexChimeraService.getServiceInterface callingPackage=com.google.android.gms componentName=null serviceId=36
07-20 08:22:20.634 2722 3123 I vev : 19-GetFileDescriptorAndDelete -- metadata{ service_id: 0 }
07-20 08:22:20.669 2878 29084 I Icing : Usage reports ok 0, Failed Usage reports 0, indexed 0, rejected 0, imm upload false
07-20 08:22:21.682 2878 2050 I Icing : Indexing FE98E561F6797F4ED5CC2B4411F3F7522CFCDD36 from com.google.android.gms
07-20 08:22:21.730 2878 2050 I Icing : Indexing done FE98E561F6797F4ED5CC2B4411F3F7522CFCDD36
07-20 08:22:33.681 1891 1891 D MmsService: getAutoPersisting
07-20 08:22:33.696 4111 4111 E MessagingApp: SmsSender: failure in sending message part. requestId=content://sms/18 partId=0 resultCode=1 errorCode=96
07-20 08:22:33.719 4111 21824 E MessagingApp: MmsUtils: SMS permanent failure
07-20 08:22:33.888 4111 21944 I MessagingAppDataModel: ProcessSentMessageAction: Done sending SMS message 31 in conversation 11; status is MANUAL_RETRY
07-20 08:22:33.889 4111 21944 I MessagingAppDataModel: ProcessPendingMessagesAction: Scheduling pending messages(message failed)
07-20 08:22:33.955 775 796 I zygote64: Background concurrent copying GC freed 17502(1072KB) AllocSpace objects, 2(104KB) LOS objects, 42% free, 12MB/21MB, paused 285us total 152.889ms

Hmm, well I rebooted my phone before posting this, and now it is sending out text just fine. Hope this error doesn't make a habit of cropping up.
[One (M9) Original Android Development] supachris:
Hi all,

I come from Galaxy S4 and installed LOS 15.1 on the One M9.

I cannot find the Inactivity Display option. Is this only enabled for OLED devices?

Reat ROM, many thanks!
[One (M9) Original Android Development] Claymore1297:
If you are talking about the burn-in protection, yes only for oled devices.
[One (M9) Original Android Development] supachris:
No. I googled the correct English description, I mean "Ambient Display". Sorry, in German this is Inaktivität Display, so I was wrong.

Can the ambient display be enabled here?
[One (M9) Original Android Development] Claymore1297:
I have this enabled in AICP and it seems to work, so I can enable ever here.

Maybe not a bad idea, due the fact we seem to have some issues with notification lights.
[One (M9) Original Android Development] supachris:
Oh, great. This would be very helpful, as due to the stupid hardware design, the notification LED is quite useless. Thanks a lot in advance.
[One (M9) Original Android Development] Anjelikk:
Does everything that works now on this rom also work on the latest version of AICP (e.g. camera)?
[One (M9) Original Android Development] DonJDelago:
I tried to shot a panorama with the standard app in AICP yesterday but wasnt lucky.
[One (M9) Original Android Development] supachris:
Can it be, the device encryption prevents the phone from going into deepsleep? I have the phone encrypted and the battery is down from 100 to 78 percent over night. Wakelock detector says, no deep sleep and kernel triggers 3h memaccess and gcrypto1de, gcrypto2fde...

Thanks.
[One (M9) Original Android Development] shimbob:
This has now happened a second time, reboot cleared it again. I guess I'm the only one experiencing these?
[One (M9) Original Android Development] Claymore1297:
encryption, eh?

Are you using hw or sw encryption?
[One (M9) Original Android Development] Claymore1297:
as I mentioned before LOS and AICP has the same functionality, but please don't mix things up.

This is a LOS-thread. For AICP questions, please use the AICP-thread.
[One (M9) Original Android Development] supachris:
I'm not sure, but I think HW encryption.

The "normal way" : Settings - Security and privacy - encryption and credentials - encrypt phone. With pre boot pattern entry and also decryption in TWRP.

Is this a known bug? I read something about that, but seems to fixed...?
[One (M9) Original Android Development] Claymore1297:
OK, then it is hw-encryption.

Can you please tell me which exact hima-device you are using and which HTC-firmware it running?
[One (M9) Original Android Development] supachris:
OK, here the infos from the download mode screen:

htc_himauhl PVT S-ON

LK-1.0.0.0000

RADIO-01.01_U114401011_117.00.61117G_2

OS-4.18.111.2

Mar 9 2017

Before installing LOS, I checked for HTC OTA updates, but obviously it was the newest.
[One (M9) Original Android Development] bahha:
Great Rom Thank you, came form AICP Rom . the battery is better with Lineage os. at first I thought it was draining fast in AICP because it's relatively old.

but when I switch to LOS it became better. so far no bugs . except the protected app crashes , no big deal tho .
[One (M9) Original Android Development] Claymore1297:
oh ... so hw-encryption is also working on a himauhl ... great!

Which build are you using?

Are there any others, which get the device encrypted with this ROM?
[One (M9) Original Android Development] supachris:
I use your latest build: lineage-15.1-20180717-UNOFFICIAL-himaul.zip

Yes, in principle it works, but seems to prevent the phone from going to deep sleep. I formatted data to remove the encryption, and now the phone is in deep sleep while not using and battery drain is much less.
[One (M9) Original Android Development] freed_de:
How to build

Hey,

Thank you for your fantastic work. :))

I've just tried your "how to build" as described in the first post, and I have a question about the first cherry-pick:

I do:

cd <build LOS-root-dir>

cd frameworks/av

git fetch https://github.com/Claymore1297/android_frameworks_av lineage-15.1

git cherry-pick 1b0bb4377d1163233b96b1ca55b0814d778f52569

And I get:

fatal: bad revision '1b0bb4377d1163233b96b1ca55b0814d778f52569'

Thank you very much for a hint.

Best regards!
[One (M9) Original Android Development] Claymore1297:
Info in OP is now correct, please try again!
[One (M9) Original Android Development] freed_de:
Thanks, syncing works fine now. :)

Build is running, ROM is installed and works. :)
[One (M9) Original Android Development] jongreeny:
So I have hardware encryption working on your earlier build (15.1-20180613-UNOFFICIAL-himaul). Pattern check comes up on boot and showing as encrypted in settings.

However I've run into problems with TWRP (ver 3.2.1.0 hima) Whenever booting into recovery it doesn't accept my pattern passcode and refuses to mount internal storage making it impossible to update to your latest build. I'm not sure how to get round this. I've read there's problems with TWRP and lineage os 15.1 encryption. There is an update to TWRP recovery 3.2.2.0 though it doesn't appear to show fixes for encryption in change log and I can't install via internal storage while the decryption isn't working.
[One (M9) Original Android Development] Claymore1297:
can you please name your device-type and HTC-firmware?

The TWRP-issue is fixed in 3.2.2, so update please your TWRP.
[One (M9) Original Android Development] jongreeny:
Great thanks. Stupid question but how do I install the update to twrp if I can't mount storage because of the encryption problem. Is it possible to sideload it via a PC?

DOWNLOAD MODE DEVICE INFO:

htc_himauhl PVT S-ON

LK-1.0.0.0000

RADIO-01.01_U114401011_117.00.61117G_2

OpenDSP-20.7.3.00535.8994_1012

OS-4.28.401.3

Mar 8 2017,11:55:08(869604)
[One (M9) Original Android Development] Claymore1297:
Thanks for the info & the good news! :)

1. Boot into Download-mode.

2. fastboot flash recovery twrp-x.x.x-x-himaul.img

3. enjoy!