yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] shpitz461:
One major issue I can report:

An incoming call, the whole screen answer window with the slider to drag to the green phone to answer, can't answer a call, I drag it multiple times to the right, it won't answer, phone keeps ringing...
[One (M7) Original Android Development] shpitz461:
More BT issues:

1. When music is playing and I place a call, music pauses, but call has no audio in or out. Tried toggling speaker/BT during the call to no avail. If I stop the music and then place a call, works fine

2. BT volume resets to MAX every time I hit play, so i play, lower the volume a bit, hit pause, then play again, volume resets to max

BTW, I dirty flashed 3/31 and did not flash SuperSU, looks like Magisk is providing SU, so it's all good.
[One (M7) Original Android Development] muthireddy:
Incoming call issue

After flashing 03/31 rom, Not able to answer incoming call. Slide to answer function is not working
[One (M7) Original Android Development] ljjehl:
Try out 3/30 and tell me what is broken there, maybe that telecomm commit wasn't a good option since it messed with incoming calls...
[One (M7) Original Android Development] shpitz461:
i thought 3/30 was broken as well, can't answer, but let me confirm.
[One (M7) Original Android Development] perfection76:
Handsfree not working?
[One (M7) Original Android Development] ljjehl:
This last post was why I was wondering about 3/30, I could simply remove stuff from 3/31 and go from there, depending on issues... :P
[One (M7) Original Android Development] piet8stevens:
On 0330, yesterday, I only received 1 incoming call but via my car and BT and no problem to answer (by using the car buttons to pick up the call). Sound was fine, too. Have not tried 0331 yet. Today, incoming call on the phone, I was able to pick up from a notification with an "Anwer" option. Also sound ok.

Over the last few releases, I sometimes do need to enter my pin code to unlock before I can pick up an incoming call.

Re. Magisk, It is hit and miss. Last night, after flashing v12, I had 3 green bars in Magisk manager (installed, supersu working and Safetynet check passed). I now rebooted and have a not rooted red bar in the middle. After another reboot, still red for supersu. Not sure what I changed to lose it or what I need to do to get it back.
[One (M7) Original Android Development] ★Michaelo★:
First of all, delete supersu as its not needed anymore. If you want to bring back the root than disable magisk hide and reboot your phone. It should be back
[One (M7) Original Android Development] piet8stevens:
Supersu and magisk

Thank you for the quick reply. I do not have a supersu. I installed 0330 and flashed magisk v12. At first, I could run apps such as TiBu that require root priviliges. Now I cannot. And magisk manager reports I am not rooted.

So, the question is why I lost root in magisk and how I can get it back.
[One (M7) Original Android Development] ★Michaelo★:
Read what I wrote up there again. It's a magisk v12 bug that people randomly lose root access. Also you don't need to flash magisk zip as its built in now
[One (M7) Original Android Development] ljjehl:
Magisk is built in, but still needed an update. It was still at v11.6, I believe. I had to update manually, also. Hopefully we have it updated in source already.
[One (M7) Original Android Development] piet8stevens:
Magisk & losing root

My root came back - do not ask me how - I rebooted for some other reason and it was back.

I have been browsing a bit on XDA and found this thread: Magisk and Magisk Hide installation and troubleshooting tips and tricks (v12) by Didgeridoohan

It says this:

a. on some ROMs, when you lose, root, it can usually be prevented by disabling busybox.

b. MagiskHide set to ON may lead to loss of root.

c. Tasker may have root issues with Magisk.

I am not sure what causes mine but have now switched busybox and MagiskHide to off. I will report back whether I still lose root or not.
[One (M7) Original Android Development] ljjehl:
Another Tidbit on Magisk :\ :

So you probably will have to run it in primary to have better success with Magisk on CTS.
[One (M7) Original Android Development] piet8stevens:
I am running in primary.
[One (M7) Original Android Development] JerseyChewi:
I just switched from plain LOS 14.1 to XenonHD 170331 and the only incoming call I've had so far suffered from the slide to answer issue. I thought I just had fat fingers until I saw this.

I switched to escape the random (daily?) reboots that many on LOS complain about. I was under the impression that this ROM did not have that issue but sadly I just observed a reboot while the phone was just sat in front of me doing nothing. It's still a nice ROM though so thanks. I'll be sticking with it!
[One (M7) Original Android Development] ljjehl:
Please revert to the 3/30 version and and give me an input on your testing, please. I'm already going to remove 3/31 due to issues with that last commit I made.

Unfortunately, I can't make any more improvements until I get more info regarding 3/30 build. I had some positive responses, but need more info regarding bluetooth transitions with other profiles (speaker/earpiece, etc)
[One (M7) Original Android Development] piet8stevens:
Am on 0330 and can confirm I can take incoming call by swiping to the right. Sometimes via notification, sometimes swipe, not sure when. Have the impression notification when locked, swipe when unlocked.
[One (M7) Original Android Development] ljjehl:
How about any other issues not resolved yet? May have something for the random reboots, but thats still tentative at this time. I never liked the fact that I can't hear ringing when initiating a call while in bluetooth mode (maybe a fix here). Anything else??
[One (M7) Original Android Development] piet8stevens:
Only other thing I have found is substratum problem with phone app, but that may be due to dirty flash. For my utilization of the phone, 0330 is just about perfect (if I do not lose root with magisk). I have so far not had any random reboots, but it is too soon to really know about that. And BT just keeps on working - I have now switched it on and off many times and it re-pairs with my car without a hitch.

Notes re. magisk:

1) with busybox off and magichide off, I have not lost root. I have now switched MagiskHide to on to see whether that then generates the problem.

2) when I "lose root", I do not just lose root but also the menus in Magisk Manager become seriously simplified, such as no more MagiskHide button etc... .
[One (M7) Original Android Development] JerseyChewi:
3/30 seems okay. I can't comment on Bluetooth at the moment.
[One (M7) Original Android Development] ljjehl:
Update!

Updated to 4/02. Magisk is v12 as well as some kernel updates, hopefully eliminates the random reboot issues.
[One (M7) Original Android Development] shpitz461:
Any chance you can tackle the BT volume issue? every time I pause music and hit play volume jumps to max, scared the **** out of the wife the other day... lol
[One (M7) Original Android Development] ljjehl:
Been trying to. You need to tell me the scenario from start and finish. Are you saying it kicks out of BT and runs in main speaker audio? With the proper scenario, I might be able to find the solution. Need to know if that scenario was supposed to stay in BT or not. I was hoping I got the answer in the previous commit with volume management. Also let me know which version rom you are running in.
[One (M7) Original Android Development] shpitz461:
Easy:

1. Have BT connect to the car

2. Play music

3. Reduce volume to 1/2 let's say

4. Pause music

5. Press Play to continue playing

Volume will reset to max every time you resume playing.
[One (M7) Original Android Development] ljjehl:
and everything is heard in BT connection? How did wife get startled? She had BT and you not? I was wondering if there was a profile disconnect and it went from BT to main speaker.
[One (M7) Original Android Development] shpitz461:
Yes, everything goes through BT when BT is connected (Maps voice prompts, notification sounds, etc...)

I stopped for gas, turned off the engine, fueled, started the car and as soon as BT connected to the car the BT audio streaming volume reset itself to max, blasting the song and she jumped.

I flashed 4/2 last night, going to do more testing throughout the day.

Were you able to replace SlimLauncher with v1.2?
[One (M7) Original Android Development] ljjehl:
Haven't had the chance...too many personal things happened last night to think about it now. Maybe next version, once I secure a copy of it to push to the github. Now I understand, you're streaming from phone to car speakers...??
[One (M7) Original Android Development] shpitz461:
Yes, streaming through BT to car stereo.
[One (M7) Original Android Development] An3skmbi:
[MENTION=921816]ljjehl[/MENTION] Just flashed 1402 and in the installer logs I see that Magisk flashes the boot img. Does this work even for S-ON? Usually I manually flash the boot.img in fastboot after flashing the rom.
[One (M7) Original Android Development] ★Michaelo★:
Don't need to flash boot.img even if you are S-ON
[One (M7) Original Android Development] An3skmbi:
Are you kidding me? I've been doing that since forever. I thought you had to do it on S-ON... :crying: but thanks, now I know :highfive:
[One (M7) Original Android Development] ljjehl:
I guess if you are actually rooted and your Bootloader is unlocked, Magisk is setup to flash it for you. If I remember right (OneX-endeavoru days), I used to be able to download an app from Gplay that allowed me to do the same without Fastboot (Flashify)
[One (M7) Original Android Development] ★Michaelo★:
Actually its possible to flash boot.img in TWRP also so fastboot isn't really needed
[One (M7) Original Android Development] dream79:
the current build runs great for me so far, thank you guys
[One (M7) Original Android Development] xaadilhx:
I've clean flashed on my m7 170402 & so far it seems functional without the random reboots, at least in the last 24 hours. Fingers crossed, I don't want to go back to lg's lollipop.

As I wrote the message with the phone sitting next to me it rebooted :( then I switched Wi-Fi network afterwards & again, otherwise I enjoyed the day without reboots, particularly no pocket reboots like with resurrection.
[One (M7) Original Android Development] MegaHTC:
Hi there!

got problems with bluetooth. After hang up a voip call (softphone) bt still remains on and all audio (notifications, music etc.) comes out of the headset until i disconnect it.

turning on and off the speakers while having a voip call kills the audio and the phone will crash soon. will this bug ever be a fixed (using vendors driver instead qualcomm's)? i wonder when ppl saying everything is working when a simple phonecall lead into a crash. also teamspeak and possibly all other apps that output to "voice call" will crash the phone. i own a m7 and t6 (one max). both international versions and both suffer from this bug.

apart from that almost everything is looking good. even the ir transmitter is working (but not the receiver, tested with "Smart IR Remote for HTC One".
[One (M7) Original Android Development] shpitz461:
BT streaming audio volume seems to be fixed, thanks!!!

Still major issues with switching BT profiles, HFP doesn't kick-in many times while music is playing, the music pauses and call initiates, but no audio in or out, and BT car controls do not work in HFP mode, they work in AVRCP mode to control music(even though the music is paused and not playing at the moment).

Music pauses and resumes fine when a call is placed once music is streaming.
[One (M7) Original Android Development] accesspc:
Hi all,

First of all, very nice ROM, I was on latest LineageOS until it got cancelled, and I admit, it was never this good as XenonHD ;)

I'm currently on 170402 and there is only one thing that bugs me - while phone is on sleep, hardware touch keys (back and home) are always active, I can feel the phone vibrate, at in some cases it wakes the phone and launches something, like Camera. Tried to search this thread but couldn't find anything. Is it something wrong with ROM itself, or I just missed some settings.

P.S. I did a clean flash after LineageOS and configured everything from scratch (no backup restores). Went through all settings (I think) and didn't find anything related to active keys while asleep...
[One (M7) Original Android Development] piet8stevens:
So far, 0402 seems to be working really well.

Question: does anyone have experience using microG on XenonHD?

Note: shortly after writing this, did have 1 random reboot. Was not even touching the phone and it rebooted.
[One (M7) Original Android Development] ljjehl:
I think this one is related to the home wake key option. I've had the same feel, but it can be turned off by turning off the tap2wake keys in display, I think
[One (M7) Original Android Development] piet8stevens:
MicroG and signature spoofing

[MENTION=921816]ljjehl[/MENTION]: I would like to try microG with XenonHD, but need signature spoofing for that.

Couple of questions came up:

a. Is this ROM deodexed? If so, I can patch myself.

b. could you include the signature spoofing patch in future releases? (no idea whether this is complicated or not): https://github.com/microg/android_packages_apps_GmsCore/wiki/Signature-Spoofing

Thx,

Piet
[One (M7) Original Android Development] shpitz461:
Interesting... I always turn vibrate off for the buttons so never realized that, but they are active while sleeping...

I guess maybe this is dt2w being active also activates the buttons and not just the screen? donno...
[One (M7) Original Android Development] tinyturtles:
I may be blind but I don't see this option under Display or even by searching​ for it in Settings...
[One (M7) Original Android Development] ljjehl:
I did have an app for it before, but you can turn off DT2W and its Hardkey button vibrate issue in the wake portion of Kernel Aduitor
[One (M7) Original Android Development] dream79:
Ou, I had two reboots again today, but I think I know now when it happenes.

It seems to be happening when the phone has no cell service for some time.
[One (M7) Original Android Development] daedric:
Mine also does that, usually with a persistent beep, until self-reboot...
[One (M7) Original Android Development] ljjehl:
So both you guys have cellular issues when a reboot happens??
[One (M7) Original Android Development] dream79:
Yes, I know for sure, yesterday with the two reboots in short succession I had noc cell coverage in the room that I was in.

With the 2 or 3 reboots that I had in the past week it might be that the phone had noc coverage, as it can be sometimes spotty in my house.

as per the vibration issue, mentioned by a few guys above, mine vibrates in the pocket sometimes for no obviouse reason, might be also buttom related.

Otherwise, working fine.

:fingers-crossed:
[One (M7) Original Android Development] saturday_night:
I made a clean flash of XeHD yesterday ver. 170402. No problems with calls or random reboots so far, can confirm the button vibration while screen is off.

But there is a small bug in the recents screen, not allways all runing apps are shown in the recents screen. I often close apps i dont want to close just because i open recents and swipe the last used app out there, but very often it doesnt show the last used apps only the first opend, so i accidentialy close this app and have to re open it. After a little bit playing around i found out that close the recents and open it again brings back all opend apps. But thats very anoying because i just dont think of it all the time haha

Another problem is, when the device goes into doze mode, it disconnect the wifi connection, no matter if in wifi settings i choose "allways on". If i activate the display after that, it takes just a second to reconnnect to wifi but thats really bad because its using mobile data when not connected to a wifi network. I just found this wifi bug while i was configuring something on my router and was wondering why my phone wasnt shown under connected devices.

Edit: just experienced a bug related to sound. When i play a voicemail in whatsapp, the speaker is working fine (loud speaker) but if i cover the sensor (that it should switch to usual sound when the phone is on my ear) it just stops playing the voicemail for a second and start again with full speaker sound as if the sensor isnt covered. Tested the Speaker bug which was in previous builds present, and it is still in there. If i end a call with speaker active, from there on there is no more in call sound, not with speaker and not the usuall sound.
[One (M7) Original Android Development] gdbouchon49:
problem gps

problem gps

Hi why my gps does not work under rom marsmallow and nougat while in lollipop it works super well.

Thank you for your answer.
[One (M7) Original Android Development] accesspc:
Yey! This did fix the problem. I'm guessing this Kernel Aduitor and enabled this "feature"...
[One (M7) Original Android Development] ljjehl:
Need more info here. What app are you using?
[One (M7) Original Android Development] ljjehl:
I'll try to remember this issue, but not sure why this happens, yet...

another add to TODO list, lol

I think this Whatsapp issue would be something that proximity speaker would come in handy for, its was a global issue back in LP. I doubt I would bring back prox speaker for this one, though.

This speaker issue in calls may or may not be resolved in this Android version. It might be possible to setup a tasker to close Speaker on your side, but the code is pretty messed up somehow by Laos in comparison to GS code. I can't fault them for this, as Google loves to twist stuff up so much that we have our work to do in getting it compatible for the non-native (not Nexus/Pixel) devices
[One (M7) Original Android Development] ljjehl:
Doubt I'll integrate this, with the possible problems with security interactions with Google updates. I'll keep it in mind for now, already have enough on my plate atm.
[One (M7) Original Android Development] piet8stevens:
Deodexed?

I understand - I am grateful for the rom as is (especially since 0402, it works really well). But is the rom deodexed? And if not, can I deodex myself?
[One (M7) Original Android Development] shpitz461:
Wow, can't place or receive any calls, as soon as I try to dial, or accept a call, the phone reboots.

Even tried downloading google dialer from the store, same thing.

It must be an update that came in the past day or so to cause this, it was calling fine yesterday or the day before.

EDIT: I dirty flashed 4/2 again, same thing, as soon as I try to dial voicemail, the phone reboots.
[One (M7) Original Android Development] maciclazar:
Did you set google phone as default phone app in settings? That may be the problem. I've never had those reboots as you. I only get one random reboot once a week :)
[One (M7) Original Android Development] shpitz461:
It was not set, it showed 'none' under Phone App, so I set it, but still reboot as soon as trying to place or receive a call.

going to try and get a log and kmsg.

EDIT: Attached logs.
[One (M7) Original Android Development] ljjehl:
Dirty flashing can cause issues.....But maybe you can try uninstalling any app updates related to telephony in settings
[One (M7) Original Android Development] shpitz461:
Yeah, but it got to a point that I had to have calls working as I was expecting some technicians at the house today.

I flashed ArtMod v10, and had/made a few calls, audio was AMAZING, so clear and good volume.

Were you able to re-do SlimLauncher?

I'm trying to install v1.2 on ArtMod (android 5.0.2 SENSE-7), but getting this error:

C:\Download\APK>adb install "SlimLauncher v1.2.apk"

[100%] /data/local/tmp/SlimLauncher v1.2.apk

pkg: /data/local/tmp/SlimLauncher v1.2.apk

Failure [INSTALL_FAILED_OLDER_SDK]

Any chance you can make a build that will work on it?
[One (M7) Original Android Development] sempi601:
Hello!

I'm using this ROM now for a few days now so cannot give any long-term feedback, but so far it is very much suitable for daily-driver. I haven't found any big issues only two minor ones:

-When double tapping screen to wake, sometimes the camera launches. I didn't find any setting for this. I know there's a double

tap power to launch, that works without a problem.

-When connected to bluetooth headset I usually lower the volume on the phone before starting playback. But when I start the music it jumps to a higher volume so I have to turn it down again. In both cases I'm modifying the bluetooth volume as the little icon says. Seems like there are two volume profiles for bluetooth.

Anyways I could live with these, just a minor notice. Keep up the great work!
[One (M7) Original Android Development] gdbouchon49:
problem gps

Hi I use google map, via michelin as well as runstatic for none gps worked under diferentes rommal marss or nougats.

I have used Andoit gps but never any satellites of localized ....

thank you
[One (M7) Original Android Development] sempi601:
Maybe my second issue is not a bug. I just noticed that with Nougat I can control the phone volume from the bluetooth headphones. This is new to me, previously (when I was on Lollipop Sense) I could control the headphone and phone volume separately.

Also now I see the battery level of the bluetooth device. Nice :)
[One (M7) Original Android Development] ljjehl:
First one may not be a bug either, as the camera by default is on the right corner of lockscreen. If you double tap, you may also be playing "thumb pool" in that area... ;)
[One (M7) Original Android Development] tinyturtles:
Do you have the "press power button twice for camera" setting on? I had the same issue and it was because I would double tap and the screen wouldn't register, so I would double tap again and the phone registered all four taps (two power button presses) and went to camera.
[One (M7) Original Android Development] shpitz461:
Did you enable High Accuracy under Settings > Location?
[One (M7) Original Android Development] sempi601:
Yes I have that turned on. I will try turning it off to see if it happens any more.

But it seems that I don't have it now, or at least very rarely.
[One (M7) Original Android Development] piet8stevens:
On 0402, had an outgoing sound problem during a call. No BT involved, just a regular incoming call. I accepted the call without a problem, everything worked and then, the phone vibrated and I could still hear the other side, but they could no longer hear me. I stopped the call, reconnected but still no outgoing sound. Phone returned to normal after reboot. Not sure what caused the vibration and then stopping of outgoing sound.
[One (M7) Original Android Development] An3skmbi:
I always have problems after accepting a call from overhead popup while phone is active. When screen is off/locked and I answer incoming call (by swiping) everything is fine. But when phone is in use and I answer from the popup, after the call the phone is super slow for about 10 secs and then reboots. Had it twice this weekend.
[One (M7) Original Android Development] sempi601:
I tried to increase vibration strength in kernel adiutor and also setting the dt2w to fullscreen instead of half. However, it seems that the settings won't stick and I'm always back to the default settings. Is there a way to change these settings?

Other thing I had several random reboots lately. How can I find out what might have caused it?
[One (M7) Original Android Development] shpitz461:
What did you set the delay in Adiutor to? I think the default is 10 seconds after boot, change it to immediate and see if it helps.
[One (M7) Original Android Development] ljjehl:
Update!!

I've added some kernel updates that hopefully will help with the random boots some of you have been having. A few more updates also, maybe fixing issues in Telephony. Let me know whats improved (or not) :D
[One (M7) Original Android Development] sempi601:
Hello ljjehl!

Thank you for the update I will try it in the evening. Do you have any idea why the settings in kernel adiutor not saving? I changed the delay to imnediate as suggested before but didn't help.