yashsingh1/xdaforums huggingface dataset:
[One (M7) Android Development] houston_:
Right now I am using a few days old gapps bundle (opengapps).

I will see if any reboots occur ...

Well just did one. I will try NanoDroid with Magisk. (I hope I can use Google Calendar Sync?)

Tried it first without any "Gapps"

Just flashed AICP without anything else -> reboots (maybe only after entering the SIM pin?)

Now I try disabling the sensors.

For that I install Magisk 16 on the clean AICP.

Incl. dalvik wipe.
[One (M7) Android Development] Mastacheata:
On each new reboot I get the "The app system has hung up and isn't reacting, wait or close" thingy (sorry, this is roughly translated from the german words on my phone as I have no idea what the english android error messages look like)

Neither action seems to have any effect on the phone, as it appears to be perfectly stable until the next unexpected reboot. (which apparently is delayed the longer you keep the phone connected to the computer or maybe a charger, haven't tried that, but there was at least one reboot every 20 mins when disconnected whereas it now happily survives 3-4 hours without unexpected reboot)

What is really bothering me, though, is the fact that as soon as I try to set up any kind of display lock, the phone hangs up. I've tried both the pattern lock and the password lock so far and they both hang up as soon as you finish the confirmation step. After that the phone is impossible to use. I've tried waiting for 2 hours to no avail and have given up now.

The big problem is that apparently it tries to set up the encryption as soon as you enter a display lock and fails at that step.

I force shutdowned the phone after 1 hour at the first attempt and gave it a full second hour at the second try. Both times it ended up with asking for a password on reboot and even if the password was entered it only told me that the encryption was broken since the password matched but it couldn't access the decrypted data either way.

Has anyone ever run across a similar issue?
[One (M7) Android Development] icxj1:
Flash the 2-28-18 build first please, I need someone to confirm if no reboots for them on that build. I've been stable for 7 days, & it started from that build.
[One (M7) Android Development] icxj1:
Copy kmesg & post if you can please , I will take a look at it.
[One (M7) Android Development] houston_:
Since I am having troubles finding the right nanodroid package for magisk...

That is a good way to avoid nanodroid :)

I will flash it right away.
[One (M7) Android Development] Mastacheata:
Is kmesg in accidental mixup of the dmesg command and the /proc/kmsg mount?

I can provide the dmesg output for the startup error message about system not responding and force closing.

Here's the dmesg output for the timespan of 30-60 seconds after boot (to get even earlier messages, this would've to be coded into the system startup itself and I've got no idea how to do that on android. ADB only starts after about 50 seconds into the boot process and earlier messages are already overwritten at that point)

View attachment 4439625

If you need any more info or have a better idea how to get at the earlier kernel messages, please let me know.
[One (M7) Android Development] icxj1:
You should win a prize for sending first log. :silly:

Thanks.

And that may be the reason for message is bcuz of late start & what is waiting for did not response in time. ? Just a theory.
[One (M7) Android Development] houston_:
Just curious... What is the kmsg (kernel messages?) and the dmesg?

I am just a user that is stumbling everytime trying to take a catlog thats not contains everything :)

At another rom, desire hd, I hat a random reboot and tried to provide a catlog, but that was completely useless, because the reboot was not throwing anything. (if I remember correctly)

If any log can help getting deeper into knowing why the reboots appear, please let me know, I will try my best to provide these logs ;)
[One (M7) Android Development] icxj1:
Yup Kmesg is kernel, dmesg is device
[One (M7) Android Development] Mastacheata:
Kmsg is a log file where Linux kernel writes messages, but the file is a round robin (each line appended on the end removes one line at the top)

No idea what it waits for. I ran this

adb wait-for-device shell "su - c dmesg > /sdcard/dmesg.log"

That should execute the command as soon as adb is loaded on the device.

I've got no idea about the autoload process of android, do they still have a classic init or did they switch to systemd as well?

One could probably write an init script to run the dmesg even before adb is available.
[One (M7) Android Development] houston_:
Just tried the 2-28-18 build.

Without anything else it works without restart. (waited about 30 min screen off)

Now pushing gapps on it.

Edit:

After installing gapps nano, I get reboots.

Now I could try nanodroid instead.

Or can I somehow deliver a log to you?
[One (M7) Android Development] icxj1:
See, they are still buged & so are we. That's not a good combination. Lol! I'm still running an older unofficial gapps. Could very well be why I'm not getting and reboots. Try some of the suggestions in thread for microG or something different.
[One (M7) Android Development] houston_:
Talking about nanodroid or gapps or both?

Well if there is nothing I can do right now, I return to a nougat rom.

Once my other device returns, I can try to provide more feedback.

THanks for your work anyway! :)
[One (M7) Android Development] gehess:
AFAIK, NanoDroid (of which microG is a part of) is not buggy. Their thread page says it works in Oreo (SDK 26 & 27), as well as all versions of Android going back to KitKat.
[One (M7) Android Development] peter1120:
After dirty flash 6 March from 3 March. The title live display in quick setting didn't work and notification settings in AICP EXTRA force close only these two things. Other s works great and by the way very nice boot animation from 6 March version.
[One (M7) Android Development] samhhmobil:
I cannot confirm this.

Display lock works well, tried with PIN, with password and with pattern, and even faceunlock (gapps nano 03-06-2018, opengapps.org) works well, as it should.

samhhmobil
[One (M7) Android Development] Rajeel911:
Way too many random reboots on the Verizon variant..

I have the 6 March 2018 version, and it randomly reboots a lot . While the device is idle and is not charging, it reboots a lot. Once in about every 15 minutes. While charging (and the device is idle) it doesn't reboot ( randomly). I didn't face any random reboots while using +both when not charging as well as while charging.

Pls fix this issue. The tiny 2300 mah battery drains too quickly with the reboots. And no I don't have even a single app that requires root. There is something with the ROM. Pls fix it ASAP as this is causing a lot of problem.

(Verizon variant)

---------- Post added at 11:06 AM ---------- Previous post was at 11:05 AM ----------

The ROM seems smooth otherwise.

---------- Post added at 11:07 AM ---------- Previous post was at 11:06 AM ----------

And no, I just have the gapps (full) installed, no other zips flashed (eg nandroid and other stuff)
[One (M7) Android Development] Deltafox79:
I can confirm this on my m7UL variant fw 7.19.402.2 HBoot 1.61 whit AICP release of 6 March..

Please fix this randomly reboots it's a great rom but with these continuous reboots it's almost impossible to use it ..

I have full wipe/Format data, system cache etc after this I have install the AICP release of 06 mars + magisk + gapps 8.1 stock of 06 mars..

Best Regards
[One (M7) Android Development] RoM4uK94:
I want to thank the developer for this work, he will succeed!!!

Thank you :)
[One (M7) Android Development] grishaiozhig:
No bug except proximity sensors, as fur as i feel. Using since first publication

Upd: Also no LTE in Ukraine, with none of 3 operators. Flashed both spr and ul versions of phone to and old LOS and to stock - both are running LTE+... But for AICP its H+ and no more, which is a great pity
[One (M7) Android Development] jinx11:
Is not working IRDA
[One (M7) Android Development] icxj1:
What app? Grab log.
[One (M7) Android Development] jinx11:
Smart IR Remote - AnyMote v4.6.8
[One (M7) Android Development] grishaiozhig:
But...theres no IRDA in M7... AFAIK

Upd: damn, there is... 2019, i discovered something new about my 2013 phone
[One (M7) Android Development] kamikazedc:
[Facepalm] :fingers-crossed:

---------- Post added at 08:10 PM ---------- Previous post was at 08:08 PM ----------

I use this one. It's simple, clean, and works well:

https://play.google.com/store/apps/details?id=org.twinone.irremote
[One (M7) Android Development] cannonleo:
I can ignore the battery life issues without bother but the proximity sensor issue is the best thing that can happen if fixed.

Am just frustrated being stuck at lollipop and viper rom cos thats the only satble rom that works for me
[One (M7) Android Development] jinx11:
kamikazedc thank you very much
[One (M7) Android Development] kamikazedc:
You're welcome!
[One (M7) Android Development] gehess:
Well, I flashed your "fastboot flash recovery twrp-3.2.3-0-m7.img" and can't access recovery.

But I then did "fastboot flash recovery twrp-3.2.3-0-m7univ.img" from dl.twrp.me/m7univ/ and it works fine.
[One (M7) Android Development] icxj1:
Yup it still needs work. Mine boots to recovery just fine. Problem is, when I want to power down it goes into recovery. I will run more tests later, as device tree improves.
[One (M7) Android Development] gehess:
Fair enough. If it's any consolation, any other recoveries I've flashed (other than ones from dl.twrp.me/m7univ/) haven't worked either.
[One (M7) Android Development] samhhmobil:
Yes, that's it.

And thanks for the hint of "m7univ", this even works for me on all m7ul devices.

samhhmobil
[One (M7) Android Development] Jalava:
Let's try this rom!
[One (M7) Android Development] mva113:
Hello! When using video calls WhatsApp Green bars on this screen, as it was before when viewing YouTube. Is this a known problem or just me?
[One (M7) Android Development] violentia:
ı falsh twrp-3.2.3-0-m7univ.img then rom and magisk flash but still not opening system always boot screen logo why ?
[One (M7) Android Development] samhhmobil:
A brand new install of the latest build did need more than 30 minutes but less than 60 minutes on my M7ul, this time you see only the boot animation.

So please be patient.

samhhmobil
[One (M7) Android Development] violentia:
thanks , I gave up the installation
[One (M7) Android Development] goodguy217:
Problem with booting

Hello!

I have a problem with the htc one m7 getting stuck on the freezing logo and it wont boot even after 40 minutes. I've tried reflashing, i've flashed it multiple times, i've reflashed the twrp. I've tried everything i could think of. Any clues on what it could be?

Thenks!

edit:

got the answer,(i think) sorry :)

Re edit:

Still need help, its been booting for about one and a half hours.
[One (M7) Android Development] icxj1:
Should not take that long. Go back to twrp 3.2.1-0 &Try an older version of magisk, 17.1 maybe. 3.2.3-0 has su removed & that seems to be part of the issue.
[One (M7) Android Development] icxj1:
Anyhow, To Hell with oreo! I will release a new build soon, still working on the pure source build + some tricks i have learn from android 9 along the way. Now it is time to move on towards better things, Maybe even eat a little piece of PIE :p. I have it! of coarse it is bugged, that is part of the fun. Soon as i fix wifi then i will start thread & let you guys play to :laugh:

View attachment 4716839
[One (M7) Android Development] goodguy217:
Thanks for the help! :) I will let you know how it goes!

Update: It worked, thanks! :)
[One (M7) Android Development] samhhmobil:
Cool! It looks great, thanks for your "fun"...

samhhmobil
[One (M7) Android Development] mva113:
look forward to!
[One (M7) Android Development] cannonleo:
Beautiful bro, blessings to you for your patience and perserverance

---------- Post added at 07:18 PM ---------- Previous post was at 07:13 PM ----------

After everything i finally decide to embrace reality and leave viper 9.0.0 finally to this rom as a daily driver, so to those using the latest build of this rom i ask

1. Is there a finally solution for the proximity sensor issue

2. If there is a work around can someone just place it step by step for me as a noob, i really didnt understand the xml manifest workaround placed before

3. can someone point me to the build that can be tagged, most stable to use si i can download it

(The only one i used and downloaded was the 18/12/2018 build

Please someone should just help me answer this question calmly and help a noob on the way

Thanks you icx
[One (M7) Android Development] gehess:
Just in case it helps, twrp 3.2.3 and magisk 18.1 work fine with Nougat 7.1.2
[One (M7) Android Development] samhhmobil:
Yes, this is correct!

samhhmobil
[One (M7) Android Development] Settler11:
Mm, I get stuck with the booting animation.

I'm on the latest available twrp, did wipe cache, data and system and tried it with and without gapps (8.1) Any idea's? Do I need a custom kernel for it or am I missing a part?
[One (M7) Android Development] samhhmobil:
Wait approx. 60 minutes, and system will start.

samhhmobil
[One (M7) Android Development] Settler11:
Damn, an hour. Better have that charger plugged in haha.
[One (M7) Android Development] Vlad_Jonson:
I have booot screen,and system not starting,I wait all night,use charge ( I want install Android 9 help me give link and say what works )
[One (M7) Android Development] grishaiozhig:
Just did a fresh install, with latest pico gapps and magisk. Works flawlessly, waiting for Pie
[One (M7) Android Development] Settler11:
Mm, it reboots after a long while and then it goes back to the flashing loading screen.

Edit: Ok, so now it's working after many waiting! I assume the trick is to add gapps AND magisk to it while flashing, untick the 'reboot after flashing' and wipe both caching. Then plug in the charger and wait to load..
[One (M7) Android Development] dudeperfect878:
hey first thanks alot for supporting m7 i know its tricky to maintain some device but not every one had vps or descent pc xD

may i ask what bugs on pie and we should have some chat group like in telegram for example for m7 community this will draw more forum members and review m7 community
[One (M7) Android Development] cannonleo:
A link to the nougat rom and is it stable (eg proximity sensor issue)
[One (M7) Android Development] samhhmobil:
Search in this forum!!!! :eek:

Look under M7 for topic [ROM][7.1.1] Lineage OS 14.1

It's UNOFFICIAL and stable. No proximity issue.

The dev is .:B:. and the download link is in his signature.

The latest build includes security level of 02/2019.

samhhmobil
[One (M7) Android Development] Vlad_Jonson:
Official aicp have discord Chanel for this...

Maybe worth creating too,for HTC one m7
[One (M7) Android Development] grishaiozhig:
Vote for 2 Telegram channels as WoA (Windows on Arm project) where there's a public channel for news about software (icxj1 will post updates, sneak peeks, announcements and WIP there) and a telegram chat where noobs and geeks will communicate, try to solve each other problems and suggest what icxj1 should implement in future builds.

VOTE! VOTE! VOTE!
[One (M7) Android Development] mva113:
icxj1, Do you know about this?:D:D:D
[One (M7) Android Development] icxj1:
? There is m7 chat on telegram created by [MENTION=5944557]alial04[/MENTION] when we were running official N ROM. Seems most have moved on. I do not know of any other devs working on Android 8 or 9 for m7. Things move very slow when it is a one man operation. 9 is coming soon, the kernel is coming along good. I have sdcardfs working for the first time since Android 6, that is gr8! Right now there is no WiFi or camera. Ril works but needs more work. Not sure about GPS because I have only ran vzw builds so far. I will release a build soon for testing & logs, but I would at least like to have WiFi working first.
[One (M7) Android Development] mva113:
Sorry for my english this is google translator! Not exactly conveys thoughts.
[One (M7) Android Development] icxj1:
No problems
[One (M7) Android Development] grishaiozhig:
That was a suggestion
[One (M7) Android Development] icxj1:
Good news!!! WiFi is officially working on Android 9
[One (M7) Android Development] plebdroid:
I lose connection (data/phone) constantly and get "com.android.phone has stopped" error on this ROM (have to restore through recovery to fix the com.android.phone has stopped error).

I'm using Ting and the sprint version of the ROM anyone have an idea of what could be wrong?
[One (M7) Android Development] icxj1:
Take a radio log in aicp extras. I do not have a sprint model to test myself.
[One (M7) Android Development] crownvn:
Dear all,

I dont lucky when my devise was broken 2 days ago and cant not use anny more thought I tried to repair it . now i cant try this Rom . I say good bye M7

for me : M7 is a wonderful and legendary mobile. with developer group . up to now. it has been spent 5 ys android 4 but now it still can run androi O and P.

thanks for Wonderful develop group who work hardly and creative

.Although I cant use M7 however I will follow this with you.

good luck to everybody
[One (M7) Android Development] grishaiozhig:
When will we be able to take a test?)
[One (M7) Android Development] icxj1:
Upload keeps dropping out, I will try again after work.
[One (M7) Android Development] plebdroid:
I uploaded a log to pastebin QgZszaNX

Currently unable to post outside links.

I had to removed a few thousand lines of

03-12 10:29:27.720 9251 9251 W CarrierConfigManager: Error getting config for subId -1 ICarrierConfigLoader is null
03-12 10:29:27.974 9344 9344 I chatty : uid=1001(radio) com.android.phone expire 57 lines
03-12 10:29:28.173 347 9395 I chatty : uid=1001(radio) /vendor/bin/hw/rild expire 2 lines

to get by the 512kb limit.
[One (M7) Android Development] icxj1:
Try this. Place these in internal storage, boot into recovery. mount system & go to system/etc find the original .xml's delete them & replace with the new. wipe ccache & reboot. Provide feedback please.

View attachment 4722434

View attachment 4722435
[One (M7) Android Development] plebdroid:
Thanks, I'll let you know in a week!

---------- Post added at 05:46 AM ---------- Previous post was at 05:22 AM ----------

Just did it, still getting the error.
[One (M7) Android Development] grishaiozhig:
No luck?
[One (M7) Android Development] cannonleo:
https://xdaforums.com/htc-one/orig-development/rom-lineage-os-14-1-t3531331/page4

Found it but no downloaf links
[One (M7) Android Development] cannonleo:
So we are not getting a final oreo builf with proximity sensor fix at all
[One (M7) Android Development] samhhmobil:
If course it is there! In the "signature"(!!) of the dev.

samhhmobil

PS

His builds are really stable for daily use, but only for M7 international version, no SPR, no VZW!
[One (M7) Android Development] icxj1:
Ok, next test will be a new build. Bad thing is it may be a week or so before it is ready.
[One (M7) Android Development] icxj1:
Here is the link to the Pie thread for test builds. Right now it is for m7 only. For testing, as i am sure it has plenty of bugs. Please post the logs on the AICP 14.0 thread.

https://xdaforums.com/htc-one/general/m7-m7vzw-m7spr-aicp-14-0-p9-0-t3910161
[One (M7) Android Development] plebdroid:
All good, thanks!
[One (M7) Android Development] violentia:
I've been waiting for 1 hour but the Aıcp logo is stuck
[One (M7) Android Development] ab123pro:
boot to twrp and flash magisk
[One (M7) Android Development] daywalk3r666:
did you flash magisk?without magisk it won't boot
[One (M7) Android Development] violentia:
yes rom magisk and gapps firsst rom second magisk and gapps
[One (M7) Android Development] grishaiozhig:
Try ROM gapps magisk, had the same issue yesterday and it helped to change the order of installation
[One (M7) Android Development] cannonleo:
I use wlv
[One (M7) Android Development] AsrielDash:
The audio has huge latency with this ROM,please fix
[One (M7) Android Development] inggit kurniawan:
awesome rom...great...thanks to Dev..
[One (M7) Android Development] violentia:
https://i.hizliresim.com/y6rAZa.jpg

some facebook video green with this rom :(
[One (M7) Android Development] samhhmobil:
==> 403 Forbidden

:(

samhhmobil
[One (M7) Android Development] violentia:
http://i.hizliresim.com/y6rAZa.jpg
[One (M7) Android Development] AsrielDash:
I got this problem too
[One (M7) Android Development] inggit kurniawan:
first ,,thanks to dev for this great rom...i am using htc m7_ul hbot 1.61 unlock bootloader..S ON...i am flast the last build this rom flash gapps and magis too..for the first booting,,i have 1 hours ...i am using this rom until now is 4 days and i dont have any bug..maybe later...thanks...and i am sorry for my bad english...i am from indonesia
[One (M7) Android Development] burntfacethom:
Heya! I've been using this rom for 3 Month now after SlimRoms stopped integrating security updates. Love it lots, so my dearest thanks icxj1!!

Since yesterday my phone is on bootloop, although i neither installed anything new, nor have i fooled around with any flashing stuff. I guess it is because i agreed to an update from the magisk manager, which randomly popped up the day before. :( (I'm not even sure if it was just the app or a new magisk version.)

So i have tried uninstalling magisk through TWRP and reinstalling the magsik version, which worked for me before (18.0). No luck there. Before i wipe everything and start anew, i thought i'd ask if maybe some1 already had the same problem and a solution for me?

Edit: i also waited for approx 90 minutes if the bootloop would end... alas it did not...

Edit 2: after wiping Data, cache, and DALVIK and (kind of) dirty flashing everything (order: ROM, gapps, Magisk 18.1) it now works again. Probably something blew away gapps? I have no clue about the issue or what exactly resolved it, but its working so i wont complain. Hopefully someone with a similar problem can profit off of that.

Regards
[One (M7) Android Development] grishaiozhig:
Same here, I got about 5-7 updates of magisk manager in 30 minutes, and updated it every time until ended up bootlooping.. Thx I had a a Twrp backed-up rom
[One (M7) Android Development] ab123pro:
did you try booting in to twrp and flashing Magisk uninstaller - View attachment 4735175 wiping dalvik/art cache then reflashing Magisk ?
[One (M7) Android Development] grishaiozhig:
No, I just recovered a backup. Magisk guys seem to have tried an April fools joke, but one thing they did is bricking a few devices...
[One (M7) Android Development] ab123pro:
well that's the reason i keep the uninstaller in my Download folder you never know when a mod might loop your device.

btw thank you icxj1 for this amazing rom smooth af sometimes smoother then my mi5 running pie :good:
[One (M7) Android Development] burntfacethom:
I tried that and when i tried installing magisk in TWRP after that, it just said the partition could not be mounted. The uninstaller from February worked though (as in i could install magisk afterwards), but did not resolve the bootloop issue.

Not really sure what caused that and what step exactly resolved the issue for me.
[One (M7) Android Development] ab123pro:
without magisk it will bootloop try rebooting in to twrp mount system and flash magisk 18.1 again
[One (M7) Android Development] tarkzim:
for lockscreen issues:

https://github.com/TARKZiM/android_device_htc_t6-common/blob/rr-oreo/t6-common.mk#L135

and

https://github.com/TARKZiM/android_device_htc_t6-common/blob/rr-oreo/manifest.xml#L115

don't set QSEE related flags in BoardConfig, that's it.

EDIT: also kernel changes:

https://github.com/TARKZiM/android_...mmit/f84b7e3276f567c1263c88d208acf909fe56d47e
[One (M7) Android Development] tarkzim:
for data usage / sim settings fc issues:

https://github.com/TARKZiM/android_kernel_htc_msm8960/commit/ac1d3c4963e4dbf5dd733b9aa4e6dd799197e023

https://github.com/TARKZiM/android_kernel_htc_msm8960/commit/6c59c34f972283fbcf5c26b211b08188e7f4bda2

https://github.com/TARKZiM/android_kernel_htc_msm8960/commit/366ac062e12133283e58bd6d32140d9f73dc6cf6