yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] shpitz461:
I had major phone app fc's, turns out to be the substratum theme I was using. Also, the BT on/off issues I've been having appear to also be related to the substratum theme.

Since I use the same theme for a few months now, I wonder if it's something within the latest Substratum that might cause these issues. I removed all theming and now BT toggle works, and phone app doesn't fc.

You did have a few builds in February where the theme didn't affect my phone like that.

---------- Post added at 10:30 ---------- Previous post was at 10:20 ----------

I can confirm what cadorna has found:

I dialed VM and got my messages, had the call on speaker.

Pressed the hang-up button.

Dialed VM again and got no audio.

I then placed another call, turned on speaker, then turned OFF speaker BEFORE I hung-up.

The next call is working fine!

I noticed that the handset call invokes DND, while when turning speaker on the DND mode is turned off. I suspect that when a call is ended while speaker is ON (DND is off), the code will toggle DND and this results in no audio. If the call is ended when speaker is OFF (DND is ON in statusbar), the next call is fine.

And I think this same behavior occurs when using BT as well, not just with speaker. Need to double-check if switching to BT call turns DND off.
[One (M7) Original Android Development] piet8stevens:
3/7 build

Did a dirty install of 0307 over 0207. Cleaned cache + dalvik cache. Did not test BT but tested just making a call. Sound quality is nice. However, I cannot stop the call after switching to another app. When I try to restart the calling app, it gives me a choice to connect another caller, or to go back to the actual call, but it does not do so. I have set my power button to not stop a call, and so I cannot stop it. The only way I have found to stop the call is to reboot my phone. I need my phone during the week so am going back to 0207.

Sorry, I cannot do more testing today or do a clean install. May be able to do that next weekend.
[One (M7) Original Android Development] ljjehl:
If you would flash MultiRom, you'll never have to worry about messing up your primary rom build....

https://xdaforums.com/htc-one/orig-development/mod-multirom-v32e-t3138965

:D
[One (M7) Original Android Development] shpitz461:
This morning woke up, BT would not turn on, had to reboot.

A few minutes ago, touchscreen stopped responding, only the hardware nav buttons were working.

Is there any chance you can revisit LP and add latest substratum to it? I'm starting to give up on N, and MM was just as bad... :(
[One (M7) Original Android Development] ★Michaelo★:
I guess Substratum won't work on android lower than 6.0. Also I never had a problem with touchscreen and Bluetooth is working fine for me
[One (M7) Original Android Development] ljjehl:
Doubt I could get substratum on LP, since it's really moved up to rootless now.

You must really use speakerphone a lot, as that seems to be the root of the BT issue in switcharounds between devices. It's not something I'm currently spending a lot of time troubleshooting at this time. I rarely make calls and spend more of my BT time streaming music on my phone to neckloop device. So far music streaming seems fine, but I assume speakerphone has issues if not manually shut off before ending a call
[One (M7) Original Android Development] ndshah2:
Updated lollipop version

Hello ljjehl, if possible, could you update your lollipop version with the latest security fixes?
[One (M7) Original Android Development] piet8stevens:
What version of the ROM are you on?
[One (M7) Original Android Development] ★Michaelo★:
Latest one with open gapps
[One (M7) Original Android Development] shpitz461:
I use speakerphone a lot cause the handset volume during calls is EXTREMELY low, even on max handset volume :(

There's also an issue with the interaction between BT audio streaming and phone calls, when I play music and a call comes in, the call has no audio, when i hangup and it goes back to music, the BT controls (next/previous track) stop working. Also, the volume keeps reset to max every time I either press play again or enter the car.

BT call controls also work sporadically (answer call or hangup).

My BT issues are consistent. The other things I reported (touchscreen and BT toggle) happen on very rare occasion. I've seen similar reports in other roms, so it's not something you're doing wrong or anything, it's just that the N-port to the M7 needs to be tweaked a little more.

I got my wife and my oldest new phones, but I'm sticking to my M7 till it dies...
[One (M7) Original Android Development] gitzolinick:
In this rom was done a great improvement since one month ago! Well done my boy, great work
[One (M7) Original Android Development] tinyturtles:
Is there any way to remove the wakelock blocker included in this ROM now? Ever since it was added, my phone has had crippling *awake*, *launch*, and Icing wakelocks (awake 1hr45min of 2hr10min)... My battery life has tanked to the point of draining battery while being on a charger, whereas it used to be 1.0% per hour drain when idle in the February builds.

Thanks and again awesome work on this ROM! :)
[One (M7) Original Android Development] ljjehl:
Thats the first I heard of it. How do you know it's the Wakelock Blocker and not something else?? Checking with others, as this is also being used with other device builds
[One (M7) Original Android Development] miinos:
Will this Rom get updates and fixes or it is abandoned like Lineage ?
[One (M7) Original Android Development] ljjehl:
The updates are global, we update the ROM, each device we support also gets the same update.
[One (M7) Original Android Development] miinos:
could we know what are the fixes to be included in the next update ? and how frequently the updates are pushed ?
[One (M7) Original Android Development] ljjehl:
You can see from the changelog in 2nd post
[One (M7) Original Android Development] tinyturtles:
I've had problems with this in the past when using Dirty Unicorns Marshmallow. When digging around then, I found some other threads that said it's related to the wakelock blocker, and true to that, I've never seen these excessive wakelocks on any ROM that doesn't have a wakelock blocker... Had no problems on this ROM until the Wakelock Blocker was included either.

Also, blocking said wakelocks causes CMwakelock to go out of control, and then blocking that causes yet other wakelocks to keep my phone awake for 5+ hours.
[One (M7) Original Android Development] gitzolinick:
Hello Ljjehl,

I have problems wjth poweramp (it crashes when i open it) and it happens only in xenon rom not others i tried before ? can i sebd you the log??
[One (M7) Original Android Development] cadorna:
It's working fine here

Enviado desde mi One mediante Tapatalk
[One (M7) Original Android Development] ★Michaelo★:
Were working for me also
[One (M7) Original Android Development] gitzolinick:
Actually i am experiencing random reboots.. :rolleyes: someone know if dolby atmos has incompatibility? It is the only mod i have installed
[One (M7) Original Android Development] gitzolinick:
ROM it's unstable, please care more about stability
[One (M7) Original Android Development] miinos:
it reboots at least 5 times a day ! :(
[One (M7) Original Android Development] gitzolinick:
Yes, exactly. I am on AICP ROM now and it is very stable
[One (M7) Original Android Development] ★Michaelo★:
No problems for me (only one 1 reboot after week of testing)
[One (M7) Original Android Development] tinyturtles:
I can second the Poweramp issues. It crashes for me when I go to any view except Now Playing.

I had a lot of random reboots since updating to the most recent build too. Wiping cache helps sometimes. The ROM will be stable for a week or so after clean flash, then go crazy with reboots, then calm down a bit again.
[One (M7) Original Android Development] ndshah2:
Link to Lollipop version

Could someone post the link to the lollipop version of this rom. I screwed up my phone with multirom and need to reflash. Being the idiot I am I didn't do a nandroid : (
[One (M7) Original Android Development] ★Michaelo★:
Link
[One (M7) Original Android Development] gitzolinick:
I am on AICP ROM. No reboots and full compatibility with poweramp. If you want use poweramp install AICP :svetius:
[One (M7) Original Android Development] miinos:
what about battery life in AICP ?
[One (M7) Original Android Development] ljjehl:
Only thing i can think of:

Is it dirty or clean build?

What mods do you have added?

If you have Poweramp added and it clashes with another app we have built in, then you'll have the issue. AICP may not have the same built in app that we have. We use audiofx, which may be what's interfering with Poweramp. I'm not sure though, depends on your setup
[One (M7) Original Android Development] gitzolinick:
No
[One (M7) Original Android Development] tinyturtles:
Clean build, and I don't add any mods... I have whatever the ROM comes with by default (but never have used it). The only things I flash in recovery with the ROM are gapps and SuperSU.

I can work around not being able to use PowerAmp but these wakelocks are killing me.. lost 30% of my battery today to them in 3 hours.
[One (M7) Original Android Development] ljjehl:
I believe the next build should have them gone. It was a global device move, not all devices benefitted from it
[One (M7) Original Android Development] ljjehl:
Update!!

Here goes nothing, Wakelock blocker out, suspend actions in. A few other additions and smaller footprint. Hopefully all for the better....
[One (M7) Original Android Development] gitzolinick:
Sorry did you noticed here is a xenon thread!???
[One (M7) Original Android Development] ljjehl:
And I appreciate it if you quit talking about other builds like a commercial. I might have some issues with mine that needs working with, but thats what happens when you have to deal with imperfections from other sources. Every build has it's ups and downs. That's why this is a development thread, for you guys to help me improve upon it. I spend more time developing for the m7 than my m8.

Last I heard, I don't get paid to do this. Its supposed to be fun. But if I hear about this all the time, then just maybe I should just move on and sell my m7.
[One (M7) Original Android Development] gitzolinick:
Sorry man you are right, it was unrespectful. I apologize to have offended you and your work.
[One (M7) Original Android Development] An3skmbi:
Hey guys,

Thanks [MENTION=921816]ljjehl[/MENTION] for keeping our m7 alive!! 4 years down the line and still on the latest version, that's amazing, so thanks for your hard work!

I just dirty-flashed the latest build over the previous one, now after reboot just get black screen and system ui force close. Will do clean flash later, just wondering if someone has an idea why this happens? I flashed xenon, then gapps, wipe cache/dalvik, flashed boot.img (I'm S-ON), reboot. Then I just get a black screen, with a popup every now and then saying system ui fc'd.
[One (M7) Original Android Development] ljjehl:
I actually dirty flashed this latest over 3/06 build myself for kicks. After I dirty flashed, I promptly wiped cache and dalvik cache. The build currently works fine after a bit of settling in. Since I have gapps backup built-in, I never needed to re-flash the Gapps. That may be your issue, as you needed to have Gapps flashed already, as you can't re-flash Gapps over a dirty build, it has to be clean.
[One (M7) Original Android Development] piet8stevens:
Big thank you to lijehl. I do appreciate all your work. Will flash your new rom and multi-rom as per your suggestion.
[One (M7) Original Android Development] shpitz461:
The ignore-list is an awesome feature... :)
[One (M7) Original Android Development] gitzolinick:
Ahahahah lol! You have such a great sense of humor!!! ?
[One (M7) Original Android Development] tinyturtles:
Dirty flashed the new build before going to bed last night... Removal of wakelocks blocker has removed all of my large wakelocks! My battery didn't drain any slower than it was in the previous build with all those wakelocks, but currently I'm going to chalk it up to the new flash. Thank you!!!
[One (M7) Original Android Development] gitzolinick:
Come on, i apologized :highfive: it was a joke, stupid joke i admit it. Now if you want blame me because of this forever it's up to you. I said what i think: the rom is not stable.

I was at Opera last week, my phone suddenly beep like a crazy electronic diapason.... I Almost was killed. I hated you that moment Ljjehl, i hated you so much especially because i was so proud to show my new Nougat rom to anyone just 30 minutes before.

Don't be depressed now for my bad joke, we are young, brilliant and fullbof humor...so we can bypass all bad moments.

With all my respectful regards,

Gitzolinick
[One (M7) Original Android Development] tinyturtles:
For what it's worth, this is the best ROM I have used since Lollipop. You are amazing for keeping this going! Thank you for all your hard work. :)

---------- Post added at 07:52 PM ---------- Previous post was at 07:41 PM ----------

I just checked this by removing Audiofx then trying to play around with PowerAmp. My crashes still occur. Not that it matters a whole lot since I don't NEED PowerAmp, but this is my result at least!

Also, I noticed that even though I set SELinux to Permissive, it automatically becomes enforcing again upon reboot. Is this because I am S-On? If I grant root permissions to Settings, it always occurs on reboot. If I do not give Settings root permissions, then it will remain permissive. Is there an advantage to either one? Or is there a fix to this?

Thank you!!!!!
[One (M7) Original Android Development] ljjehl:
Let me know if you have issues installing MR. It's easy, to be honest. This no-kexec option makes it sooo easy to flash multiple m7 roms without screwing up your primary. That's how I survive....
[One (M7) Original Android Development] ljjehl:
Since a few of you guys seem to like Poweramp so much, I'll do a test later an see what's up with the issues you have been experiencing. Will probably also have a build later, also!! ?
[One (M7) Original Android Development] shpitz461:
And while you're at it, can you please use SlimLauncher v1.2? The newer ones have tons of features missing for some reason...

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

From this thread: https://xdaforums.com/android/apps-games/app-slimlauncher-1-1-t3216971

It's a pain for me to keep removing the build you included, reboot, then restore 1.2 :)

My favorite music player is HTC Music, works great, no issues with using it with Dolby Atmos, which can be found here: https://xdaforums.com/showpost.php?p=61738087&postcount=4
[One (M7) Original Android Development] saturday_night:
After flashing the rom, in twrp choose mount, mount system, go back go to advanced , choose file manager and delete the app before you restart the device. I allways debloat roms this way, positive thing the first boot is much faster ;)
[One (M7) Original Android Development] shpitz461:
Great tip, thanks!

Even better would be to prevent the problem in the 1st place :)
[One (M7) Original Android Development] gehess:
I have noticed that ljjehl is one of the few rom devs that takes the time to respond to people's problems and questions. :good:

That's worth something, especially for a device that has no official support.
[One (M7) Original Android Development] ljjehl:
Well, if I set my device as permissive, I get Thememanager root permissions (pass), then I reboot and keep permissive status. I haven't seen a revert of what I did yet. :\ Why do you need permissive status? Doubt being S-On has anything to do with it, since you have an unlocked bootloader.
[One (M7) Original Android Development] shpitz461:
I'm sad to report all BT calls issues still exist, did a clean flash.

1st call after flash had no audio, had to toggle speaker/BT for it to work.

After that, several calls were ok, some were not, all on BT.

I also figured out the BT call controls: if the speaker fiasco is in affect, BT control is treated as audio streaming, so it tries to change the track, even though there is no music playing. Once I toggle speaker and then back to BT, BT call control is working fine and I'm able to end the call with the car control.
[One (M7) Original Android Development] ljjehl:
I haven't really been researching the issue as of late. I do have this build I have done but not tested yet. I probably should test first before push, as most of you don't have MultiRom setup yet. It's no fun to flash something and find out it's crap and no backup to fall back on, lol....
[One (M7) Original Android Development] shpitz461:
there's always a back with nandroid :)

And i've pretty much stopped doing a full restore after a clean flash to test a new build, I just test a few basic things to make sure it's all good, so I don't waste too much time or effort.
[One (M7) Original Android Development] tinyturtles:
No need! I was just wondering if this is occurring as intended (switching back to enforcing upon reboot) or not and if anything relies upon SeLinux being set as permissive. It seems that this is not intended, which means I will need to figure out why the device switches back to enforcing upon boot.

Second this. Fantastic dev!
[One (M7) Original Android Development] ljjehl:
We needed permissive in the beginning due to code still in the beginning stages of development. Now since it's been mostly figured out, enforcement keeps crap out. Nothing is foolproof though...
[One (M7) Original Android Development] gehess:
Have you tried SELinuxModeChanger, which you can download via F-Droid?

After boot, it should keep whichever mode you set.
[One (M7) Original Android Development] tinyturtles:
Settings takes root access AFTER this app does, so it switches to enforcing even if I use this app.
[One (M7) Original Android Development] gehess:
Otherwise I've had success in the past with this (use a terminal emulator or ADB to type these commands):

su

mount -o remount,rw /system

mkdir /system/su.d

echo "#!/system/bin/sh" > /system/su.d/permissive.sh

echo "setenforce 0" > /system/su.d/permissive.sh

echo "0" > /sys/fs/selinux/enforce

chmod 755 /system/su.d/permissive.sh

Each line needs to be entered separately by pressing enter after each line. Then reboot. The SELinux policy should be set to permissive and stay like that after any reboots.
[One (M7) Original Android Development] gitzolinick:
You don't need it i think, it is included in the rom. Go to Dev Options
[One (M7) Original Android Development] ljjehl:
It's in configurations, and works in a lower level than an app you can install after-the-fact. I still have my device set as permissive even after repeated reboots. I just reset as enforced and still all good.

Update! BTW, I pushed a minor update that might have something that may work with you carkit users. I'm not that optimistic, though, as I haven't tested that one yet. :\
[One (M7) Original Android Development] piet8stevens:
Multirom

Thank you for the tip. Installed it, enabled no kexec. Cloned a nandroid backup from 0207 (I want to create a clean 0321 and a dirty flashed 0207 to see whether there is any difference), but then get stuck installing 0321. Get error 7 when flashing the zip. Not sure what I did wrong. Had not checked the checksum and will do so and report back. Multirom is fascinating. When trying a clean 0321, I also get error 7.
[One (M7) Original Android Development] ljjehl:
error 7 is usually a md5 error. I installed on mine with no issues. In case you (or other new users) don't know, MultiRom is accessed in upper right of recovery (3 vertical lines). I remember having that issue in the beginning, as the MR dev went more discreet in designing the MR recovery designs.
[One (M7) Original Android Development] shpitz461:
I experienced error 7 as well with another build. Only way I got it to work was by cleaning cache using fastboot, then wiping all partitions in recovery.
[One (M7) Original Android Development] piet8stevens:
Multirom error 7 - Cleaning cache?

I wiped dalvik cache & cache in recovery. When you say "cleaning cache using fastboot", do you mean "erase"? It is strange as usually, cache etc... only comes into play when you start up the ROM, if I am not mistaken. Do you erase before you install the zip?

I verified the checksum and that is not the problem. Checksum matches the .md5sum file.

Thx for any help.
[One (M7) Original Android Development] ljjehl:
Are both of you using MR?? Which version if so??
[One (M7) Original Android Development] shpitz461:
Nope, never had and most likely never will... :)

I'm a 1-ROM kinda guy :)
[One (M7) Original Android Development] piet8stevens:
Multi-rom version

20160409. Installed via the app. TWRP_3.0.2-0-multirom.
[One (M7) Original Android Development] nsanzumuhire:
What if I want to replace xenonHD with lineageOS ?? I have lineage as primary and viperone9 as second??
[One (M7) Original Android Development] dream79:
Hello,

I have an issue with controling bluetooth, after a reboot I can enable bluetooth once or maybe twice, after that I can not enable bluetooth any more once it is turned off.

I'm using XenonHD-170321-experimental-m7 flashed with twrp.

I had the same issue with the latest lineage os also.

The device is a non branded european M7 with 32gb.

I'm using custom roms on this device only since last weekend (Lineage Os)
[One (M7) Original Android Development] shpitz461:
Happened to me as well, went to the car to drive home, BT connected, but after a reboot it would not connect even if it showed as turned on.

The solution dream79 is to turn BT off, then reboot, then turn it on.

A reboot while BT is toggled ON would not work.
[One (M7) Original Android Development] An3skmbi:
I can confirm the bluetooth issue [MENTION=769624]dream79[/MENTION] and workaround suggested by [MENTION=583152]shpitz461[/MENTION]. Also having bluetooth wakelock issue in latest (21/03) build after clean flash. My bluetooth is always on to sync with my fitbit, never had these wakelocks so high before (used to be ~5%). See attached screenshots. Anyone know how to get rid of these?
[One (M7) Original Android Development] shpitz461:
My BT is on all the time to avoid some of the issues, but I'm not experiencing any of the wakelocks you do...

I was on a whatsapp video call, that's why the drain is so high.
[One (M7) Original Android Development] ziomek666:
Dat lucky patcher message tho :)

(when you install lucky patcher and reboot a message will apear which will force you to confirm that you are a thief)

Too bad it's not true (Name 1 app that failed due to piracy and not being a bad app)

I'm appreciating that it's only a warning and not any kind of lock :)
[One (M7) Original Android Development] Allenoic:
Quick Q

What Kernel can I install for this ROM which I can overclocking the CPU?
[One (M7) Original Android Development] ljjehl:
wiping cache and dalvik helps with the kernel. When I dirty flash over another Xenonhd rom, I wipe cache and dalvik in recovery. It helps make sure you don't end up in a bootloop with incompatible kernels.
[One (M7) Original Android Development] ljjehl:
this one is newer:

https://www.androidfilehost.com/?w=files&flid=129510
[One (M7) Original Android Development] ★Michaelo★:
None. Overclocking isn't really needed. Just use the stock kernel provided in this rom
[One (M7) Original Android Development] ljjehl:
Was trying to figure out why I ended up back to the issue with bluetooth not turning off, found out that my commit that worked was not in there this time. Added it and currently building. Hopefully this works this time round.
[One (M7) Original Android Development] Allenoic:
Okay thank you