yashsingh1/xdaforums huggingface dataset:
[One (M7) Android Development] evilcoleslaw:
Proximity works perfectly on the new build on my m7ul for the first call after boot and then subsequently I have to use dt2w. But I haven't had the screen totally stop responding from the proximity sensor so it's no biggie.
[One (M7) Android Development] icxj1:
Yup, its a pain in the butt! I will get it figured out soon.
[One (M7) Android Development] icxj1:
Here is a manifest.xml for anyone that wants to disable proximity until I have a fix. Boot recovery, Mount system, advanced/file manager, delete or move to storage system/vendor/manifest.xml then replace with this one. Screen will stay on during call.
[One (M7) Android Development] perfection76:
Thanks

---------- Post added at 06:53 AM ---------- Previous post was at 06:48 AM ----------

which gapps package you installed. You have solved the problem I want to explain.
[One (M7) Android Development] icxj1:
I normally just use nano, then install chrome & a few other apps after.
[One (M7) Android Development] evilcoleslaw:
Thanks for this. After a clean install proximity was now 100% borked for me. :silly:
[One (M7) Android Development] icxj1:
Hahaha! I know, I know!!! It is a bummer. I hope to get it straightened out soon.
[One (M7) Android Development] saturday_night:
Maybe you could just throw the device against the wall as hard as you can and see if that helps for proximity sensor ;p

Just kidding to bring some fun into this thread ;p
[One (M7) Android Development] icxj1:
Yes, haha! that would fix all of our problems at once. :good:
[One (M7) Android Development] alexxpotter458:
Apps like Instagram analytics can't be opened, it crashes every time... This problem is only in my device?
[One (M7) Android Development] corum3:
Having bluetooth switched on in the night seems to empty my battery really really fast, however I cannot see the battery stats so I dont know if its actually bluetooth doing the damage.

I connect to a bluetooth speaker for about 2 hours, using relaxio, after 2 hrs the app stops and the JBL go speaker switches off, but my phone is dead in the morning.

I realise this could be anything, but during the day I switch bluetooth off and the phone lasts all day.
[One (M7) Android Development] Rajeel911:
How are you able to last the tiny 2300 mah battery all day? Mine is able to last only for half a day..

What's your screen on time on a charge from 100% to about 15%?
[One (M7) Android Development] corum3:
ah yeah, i dont use the phone too much at all, so it pretty much lasts all day.

In the night I just it for relaxio and the bluetooth connection.

but I am in the middle of restoring to an earlier build, 0321 which seems to have much better battery life on BT connection. so I cant really say how long I get with the screen on, but its not too long.
[One (M7) Android Development] evilcoleslaw:
Yeah, combine the 2300mAh battery with battery age and I'm lucky if I can get through a workday. But on the plus side since the phone is so old you can find cheap accessories. I just ordered a Mophie Juice Pack for dirt cheap. I would've never paid $100 for one in 2013. ?
[One (M7) Android Development] corum3:
I just had to order a new screen replacement #2 which isnt bad considering it age. $18... I have replaced the screen once already, the main speaker & front cover, its all fun and games, but I like the feel of this phone.
[One (M7) Android Development] JerseyChewi:
First off, thanks for the awesome ROM. I didn't expect Oreo to be such a smooth ride. Sure, calling is flaky but that was true for my last ROM too.

So I tried this but unfortunately it made no difference here. I'd like to think I know what I'm doing. The following should prove that. I trust you'll have a proper fix before long.

$ diff -Naur /system/vendor/manifest.xml.orig /system/vendor/manifest.xml
--- /system/vendor/manifest.xml.orig
+++ /system/vendor/manifest.xml
@@ -198,7 +198,7 @@
</hal>
<hal format="hidl">
<name>android.hardware.sensors</name>
- <transport arch="32+64">passthrough</transport>
+ <transport>hwbinder</transport>
<version>1.0</version>
<interface>
<name>ISensors</name>

Aside from that, it may be my imagination but I think the battery is draining a little faster. Maybe it's not the main cause but Privacy Guard shows that NFC Service has woken the phone thousands of times even though I have NFC disabled. I've seen that other apps can cause NFC to become enabled again but I haven't seen any evidence of that here. I don't need it at all but you can't disable NFC Service. Anyone have any ideas?
[One (M7) Android Development] saentis:
Sounds like they charge it during the day, if draining battery at night is a problem.
[One (M7) Android Development] Rajeel911:
Just clean flashed this rom on M7 vzw.. (3rd April 2018 build)

The ROM has no issues and thankfully no reboots.

But when I try to call someone, I am not able to hear anything thing from the earpiece and once the screen goes off when I put the phone on my ear, the screen does turn on even after I press the power button after taking off my ear
[One (M7) Android Development] Rajeel911:
Edit: when I recieve a call, calling works absolutely fine. I am able tohear the other person and even the proximity sensor works.
[One (M7) Android Development] Rajeel911:
Edit 2: tried using Google phone dialer, calling works absolutely fine, but the proximity sensor problem still persists.
[One (M7) Android Development] Rajeel911:
Can I install magisk on this rom?
[One (M7) Android Development] kamikazedc:
Of course!
[One (M7) Android Development] Rajeel911:
Sometimes I have turning on Bluetooth..

I gets stuck on turning on

Rebooting solves the problem
[One (M7) Android Development] evilcoleslaw:
Been using the Mophie Juice Pack I just got for a few days. From like 7am to 11pm and I've got 50% battery left on the phone itself after using up the case's battery. Best $11 I've spent on eBay in a long time.
[One (M7) Android Development] icxj1:
Latest Vzw with April security patch along with source updates.

m7vzw += https://www.androidfilehost.com/?fid=818070582850506845

m7ul coming soon, need to check & update a few things first.
[One (M7) Android Development] saturday_night:
Great work, and Congratulations for your first thousand thanks ;p
[One (M7) Android Development] icxj1:
thanks guys! never thought i would ever see 500.

Here is m7ul, April 5 2018 security patch & updated source. there are some manifest changes so first boot may hang on dirty flash. give it about 5 minutes if it don't boot just force reboot. Proximity worked on first out call, so see what happens.

m7ul += https://www.androidfilehost.com/?fid=673956719939833856
[One (M7) Android Development] Rajeel911:
How do I install this update?

Will I also have to flash gapps again if I dirty flash it?
[One (M7) Android Development] samhhmobil:
I just made a dirty flash, wiping cache and dalvik, and it rebooted in 90seconds without any issue.

samhhmobil

---------- Post added at 02:19 PM ---------- Previous post was at 02:18 PM ----------

No. Leave it as it is.

samhhmobil
[One (M7) Android Development] Biggie_still:
System still crash on start up with this latest build?
[One (M7) Android Development] icxj1:
That's just a warning, select wait & rock on!
[One (M7) Android Development] Rajeel911:
This is literally the smoothest ROM I've experienced on M7 after the stock sense rom
[One (M7) Android Development] Rajeel911:
How can I use the updater app to install the update?
[One (M7) Android Development] icxj1:
Yup, few more bugs & we will be good to go.
[One (M7) Android Development] icxj1:
Top left corner, then select install & add zip.
[One (M7) Android Development] Rajeel911:
Ya, this rom is almost perfect now..

I had tested the 8march 2018 build..

It were too buggy for my daily driver.. Now installed the latest build and now it is a completely different story.. I really want to thank you for supporting such an old device for us..

I find no major bug in this rom

Thank you
[One (M7) Android Development] kamikazedc:
It's an unofficial build, OTA are not available.

But you can download the update manually, and go to "menu > install" within the update app and select the file.
[One (M7) Android Development] saentis:
I agree with how great it is to have this rom, thank you!

For me after dirty flashing to the newest version I still had the proximity problem. Clean flashing fixed it mostly.

Now on some calls it works, and on some the screen stays black after releasing the sensor. However in that case pressing the power button twice turns it back on (and from that moment on, in the same call, it works again). So I would say it's functional now. Thank you!
[One (M7) Android Development] icxj1:
It comes & goes, has a mind of it own. Sometimes it will work 3-4 times then stay black screen. It's in the aosp based dialer app bcuz sensor always test good. I think when screen stops working proximity still triggers & button backlight come on. Maybe someone can confirm the same? Google dialer is basically the same dialer app. I wish it had a dam on/off switch like the freaking speakerphone. :p

Sometimes I clear dialer app data & it works again for a few.
[One (M7) Android Development] saentis:
I also have it on skype calls.
[One (M7) Android Development] evilcoleslaw:
Clean install on m7ul. Proximity is still 100% borked for me after the first call. ? I know it has to be maddening.
[One (M7) Android Development] saturday_night:
Wow, nearly a full day without anyone reporting already known problems or new ones haha that must feel like easter birthday and xmas together ;p
[One (M7) Android Development] gehess:
Then again, maybe everyone's lost access to the internet on their device, so... :laugh:
[One (M7) Android Development] icxj1:
Hahaha! M7 either ate the battery or used up all their monthly data.
[One (M7) Android Development] evilcoleslaw:
My m7 sprang out these tubules into my other electronics and now they're all telling me that resistance is futile. Send help. ?
[One (M7) Android Development] hedeon76:
Hello [MENTION=7327102]icxj1[/MENTION],

i have tested the two new builds (20180409 and 20180410).

Unfortunately, there is no change regarding the bluetooth microphone problem.

Maybe someone else can test this.

The problem is not just when calling. You can also test it on a bluetooth recording app. There is the same problem.

Also, I noticed that in the last two builds no ambient display is available.

anyway, Thanks for your work.
[One (M7) Android Development] icxj1:
Yes, it is very Unfortunate. There should still be some ambient display options in AE lockscreen settings.
[One (M7) Android Development] hedeon76:
Yes, there are settings in AE lockscrenn settings, but the main switch under settings -> display is not there.

And the display will not turn on if i receive a message.
[One (M7) Android Development] icxj1:
Well when aicp brings it back in, then I will.
[One (M7) Android Development] hindydidou:
I know it's not very important, but I try to understand options in AICP Extra parameters, and mainly System Animations.

It's OK for Activity Close ans Open, but I don't understand what is Task Close and Open, Move To Front, and also Wallpaper Open, Close and Intra Open.

I tried all animations but I don't see any change.

Some example would be welcome.

And, of course many thanks for this great rom.

Alain.
[One (M7) Android Development] godll90:
It would be interesting add in the privacy guardian section, apps blocking.
[One (M7) Android Development] kamikazedc:
Hi all,

After clean install latest build, proximity sensor problem is still there for me too.

I've noticed it fails even when listening whatsapp voice notes in "call mode".

This can be a good method for quick testing...
[One (M7) Android Development] evilcoleslaw:
After another clean install and twiddling with Kernel Adiutor settings I finally got it at least usable with dt2w again. Which is good because it was a little frustrating having to force a reboot after nearly every outbound call. ?
[One (M7) Android Development] Rajeel911:
If I update using this method, will I loose my apps and the app data?
[One (M7) Android Development] saentis:
What also works is using the setting "power button ends call" in accessibility settings. Doesn't allow to turn the screen on during call. But at least you can end the call when the screen is off, and afterwards screen will turn on again.
[One (M7) Android Development] evilcoleslaw:
Ah. I was looking for that setting under Hardware Buttons. Used to use that on my Zenfone 2 when the proximity sensor died. ?
[One (M7) Android Development] Rajeel911:
Pls tell some1
[One (M7) Android Development] saturday_night:
No you dont lose anything
[One (M7) Android Development] markg546:
Any news on the SElinux switch?
[One (M7) Android Development] godll90:
The sprint version has an error when turning on the cell phone, it stays in the Htc logo and does not turn on. I have to connect it with the charger so that it turns on.
[One (M7) Android Development] Rajeel911:
It means your battery is at fault

Not the rom
[One (M7) Android Development] godll90:
I do not think so. I have tried different roms and only with this one happens.

By the way, which is the correct calibration. Because I've tried everything and nothing.
[One (M7) Android Development] Rajeel911:
Omg where is ambient display??

I really loved that feature

Note that i had updated the ROM to April 9 build using the aicp updater app
[One (M7) Android Development] icxj1:
It should return in next build.
[One (M7) Android Development] icxj1:
Hang sometimes on HTC splashscreen, charger has nothing to do with it. Wait 3-5 minutes if no boot, then force reboot. As for calibration, I don't know wtf you mean.
[One (M7) Android Development] Andrea224:
I was thinking for so long time: why the splashscreen takes so much time?
[One (M7) Android Development] icxj1:
Very doubtful, I have sepolicy straightened out in new build but I do not expect selinux switch to work yet. Especially from permissive to enforcing. I will run a build in enforcing mode & test that way.
[One (M7) Android Development] icxj1:
Just more symptoms of m7 noncompatible-broken hwbinder.
[One (M7) Android Development] markg546:
Any ETA for next build?
[One (M7) Android Development] icxj1:
It maybe 4-5 hours before I get back to PC & upload. You can test selinux switch anytime, just do not select persists across reboots. Bcuz if not working properly it will begin to reboot over & over. Then you will have to force into recovery to wipe system & reflash clean.
[One (M7) Android Development] markg546:
That's amazing

I maybe was a bit retarded and tried that with an app, it is one of the reasons I asked the ETA for next build
[One (M7) Android Development] markg546:
Hello there well ... I guess the estimation was wrong :P [MENTION=7327102]icxj1[/MENTION]
[One (M7) Android Development] Andrea224:
Oh I see, poor HTC M7...
[One (M7) Android Development] icxj1:
Hahaha! I forgotten you are the pushing little ****er! Lol! M7 & m7vzw are uploaded, just go to AH & grab it. I'll post all 3 when sprint is done. No go on Selinux switch yet but there are way less denials now. ambient has returned.
[One (M7) Android Development] icxj1:
Yup, if only there were a genius kernel dev out there that could work some magic for us.
[One (M7) Android Development] markg546:
Sadly the new build broke Bluetooth ... Calling and the most important I thought you fixed passwords ( can you please look into those?
[One (M7) Android Development] icxj1:
Good, no need to post build then. Sadly my BT & call are working fine. As for password, I don't use so couldn't tell you. I'll check it out, but not going to loose sleep over it. I've pretty much had an assful of bug reports with no logs and the pissing & moaning about what works on N that is not working on O. Me sharing builds for you all to just flash to decide if you want to drive it or not isn't getting anywhere with development. Testing & development was the original intention of this thread so that we could possibly have a verity of working O ROM's for m7. That means more then one dev working with source.
[One (M7) Android Development] gehess:
May I ask what happened to alial04?
[One (M7) Android Development] icxj1:
Haven't heard from him in a while. last I heard he start a new job that keeps him busy & development for Athene. I'm running out of time myself with summer months coming up I will be having to do overtime at work.
[One (M7) Android Development] gehess:
Fair enough.

... Don't suppose Athene has an M7? :laugh:
[One (M7) Android Development] icxj1:
No, I think Ali lost his m7 & is driving a Motorola Athene device now. He is building aicp for it.
[One (M7) Android Development] gehess:
Huh. Learned about 2 things called Athene today.

Sounds like a "luxury" version Toyota Camry. :D
[One (M7) Android Development] icxj1:
Haha, all the bells & whistles.
[One (M7) Android Development] Rajeel911:
I am not able to change the accent colour..

Whenever I choose a colour, it gets selected and then when I click on the back button I see no change.

(Vzw version)
[One (M7) Android Development] icxj1:
Go to AH & try the latest build.
[One (M7) Android Development] Rajeel911:
Ohhhh...

Is ambient display back on the 16 April build?

I am on April 9 build
[One (M7) Android Development] icxj1:
Yup, ambient is back.
[One (M7) Android Development] Rajeel911:
I have one small request.

Can you pls also add an option for always on display? I know that it will be really eating up the battery, but some people (including me) really like it.

I'll be the happiest person on the earth if you add that option:)
[One (M7) Android Development] icxj1:
Once again, source is not complete. aicp is still bringing in features & removing them & then bringing them back again. This has gone on for 8 months. When it is brought back by Los & Aicp then I will add it.
[One (M7) Android Development] icxj1:
Btw we are not the only device stuck on Selinux permissive, in fact there are only a few that are booting in enforcing mode. So no need to keep pushing on that topic.
[One (M7) Android Development] samhhmobil:
Yup.

But BTW, with build 0417 I (just only) tried to switch SElinux to "enforced/strict" and in that moment "Android-System" did request root permissions in Magisk (... and Magisk did refuse that by default).

Strange, oh???

Android-System should have its permissions by default, otherwise all system will behave strange...

samhhmobil
[One (M7) Android Development] evilcoleslaw:
Everything I use except the known issues is working as intended on 0417. Accent color is working for me as well. Anything specific that needs testing that isn't BT related? (I never use it)
[One (M7) Android Development] bbmaster123:
just want to report no build of this rom works for my old m7. NBD as not my main driver, but rom always starts to process system isn't responding, stays there frozen for about 20 seconds, finally lets me hit wait, stays on black screen forever, with minimal functionality. usb wont mount on pc, volume buttons do nothing, power button doesn't shut screen on/off, but home and back button will buzz, and holding power button brings up restart option, but does nothing if pressed. status bar will swipe down, but only first row, and wont let you interact with it. setup wizard never triggers, although at one point I did get into the homescreen by random chance I suppose, and played around for a few minutes and restarted, and then next boot was right back to the black screen. It seemed pretty nice and smooth while I was able to use it though. Strangely I didn't get the "system isnt responding" popup that time.

tried latest sense firmware, latest gpe firmware, and installing rom+gapps with and without a reboot in between, each attempt wiping everything for clean install. M7_UL, S-OFF, GPE, supercid

and of course thanks for all your hard work and time!

ps: I kinda thought the previous boot animation was pretty cool, pun intended? maybe? haha
[One (M7) Android Development] icxj1:
Not sure WTF you got going on. I can select wait as soon as process system isn't responding warning pops up, statusbar all working, usb adb-mtp working, setup wizard working, buttons working(maybe check & pick your hardware buttons). Never heard any buzz. Firmware doesn't matter anymore.
[One (M7) Android Development] hchanh:
Nice rom, i have not see any bugs.

But somehow i feel my phone abit lag and yeah, its hot (even turned off many connections). Does I need to reflash the rom or wait for new update?

Btw i love it so much alots of setting and its CLEAN.

Thank you guys.
[One (M7) Android Development] icxj1:
No lag or heat, reinstall. Make sure to uninstall any root you may have first & advanced wipe cache, dalvik/Art cache, data, & system. Flash ROM, gapps, & root.
[One (M7) Android Development] bbmaster123:
who knows, looks like most other people have it working. Can't really get a logcat at this stage anyways. hardware buttons are okay, tested with RR. By buzz, I really meant haptic feedback. I know, I just figured I'd try different firmwares anyway, was basically the last thing to try. That one time I did get it though everything was working normally, not sure why/how. Didn't trigger the setup though, just right to home screen.

oh and at one point the black screen turned into the lockscreen, where I could swipe up to just be back on the black screen, and if I swiped back down the lockscreen would fade back in :s
[One (M7) Android Development] sudowtf:
Is there a CPU limiter or overheat limiter option available/hidden in here somewhere? i was pushing it hard and had a couple reboots (separate times). maybe it overheated; i was using DJI Go 4 to fly a drone (bad time to to go black)
[One (M7) Android Development] evilcoleslaw:
Ran into a system UI crash well after boot. Froze up and then kicked me to a black screen for a bit then to the lock screen. This time I come bearing logs. (Logcat, Dmesg, Kmsg).
[One (M7) Android Development] icxj1:
Check KA thermal.
[One (M7) Android Development] gehess:
While I applaud the use of mobile devices with robotics, could I suggest maybe don't use an essentially experimental build of Oreo to control your drone. ;)
[One (M7) Android Development] icxj1:
Hahaha! Was thinking same thing, scary thought. Some of those are expensive. What goes up must come down. [MENTION=3755222]sudowtf[/MENTION] make sure to have a camera on it to capture footage of crash. :cyclops:
[One (M7) Android Development] icxj1:
I think they have a fix for you, I will include it in next build. Los just merged it today. Not sure why only you have reported issue on m7 so far, but it is apparently a known issue for other devices also. Reports are black screen with only statusbar & if enabled navbar with only back button. Has something to do with keygaurd profile not being properly dismissed on boot. I will post build when finished. I have a 20180418 build uploaded but that commit is not included in it.
[One (M7) Android Development] icxj1:
Guys, 20180418 m7ul & m7vzw are uploaded. It has more sepolicy then L, MM, & N ROM combined :laugh: there are some cherrypicks of fixes & improvements in fw/base, also hopefully a fully functional omniswicth.Working on 20180419 now. i will try to include m7spr build in this round.
[One (M7) Android Development] cyandaniel:
Hi, i installed this Rom last weekend and so far it is really great, I would like to thank you for all this work.

Alas I have one bug to report: golang (Google's programming language) makes some trouble. First I installed golang in termux and the system crashed every time I tried to run the compiler.

I don't need to compile on my smartphone, but I thought it would be fun.

Then I installed syncthing yesterday, which is also partly written in go and the system crashes again. Apparently golang and this rom don't work together. So in order to reproduce this, it should be sufficient to install syncthing from F-Droid and try to come past the welcome screen.