yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] crashdjent:
[MENTION=921816]ljjehl[/MENTION], I just do not understand why there is no support Doze for my m7? And it seems to be just me ... No support for the sensor. Any idea of ​​what could be wrong? m7_u, htc-a48, 7.19.401.151.

But in the bootloader is not displayed. The OS is empty. But about 3 months ago, I flashed that RUU

UPD. After comand fastboot getvar all line version-main: also empty. maybe because of this doze is not working?
[One (M7) Original Android Development] shpitz461:
I'm on GPE firmware. BT this morning did not want to turn on. I had to reboot twice for it to be functional again.

Woke up, tried to turn BT on, the quick setting button would not do anything. In BT settings, was not able to toggle on/off, it would stay stuck in ON position.

Reboot 1st time, BT showed being OFF, could not toggle in quick settings nor in BT settings. The toggle in settings did move from OFF to ON, but BT was off showing the text message in the settings window.

Reboot 2nd time, BT was OFF but was able to toggle with quick settings, and BT in the car connected and worked fine.

---------- Post added at 09:47 ---------- Previous post was at 09:43 ----------

I use GPE firmware and no random reboots, only BT is flaky.

Firmware line in getvar is blank, doesn't make any difference. I think that's cause we're not stock anymore...

Which app did you use to determine if doze works or not?
[One (M7) Original Android Development] gitzolinick:
I had the same problems: sometimes it doesn't want ON, not very smooth experience (actually quite laggy)

And many randoom reboots.
[One (M7) Original Android Development] ljjehl:
May have pushed the latest update too fast. Gained security update for Substratum and also pocket detection for DT2W, but killed videocam for snap for some reason. :(
[One (M7) Original Android Development] saturday_night:
Thanks anyhow, pocket protection doesnt work, the switch doesnt have any effect like the one for enable or disable dt2w.
[One (M7) Original Android Development] crashdjent:
anyone can share a log after entering command dumpstate in terminal emulator?
[One (M7) Original Android Development] ljjehl:
It does prevent you from waking up from screen by DT2W with proximity sensor covered. That in itself should do the job to prevent accidental wakeup by you "Pocket Pool" players :D

I see that switch, I guess that's a result of a global setup. I'll see what I need to do to get that up to par.

As for the VideoCam not working, I thought it was due to enforcing mode. (Due to M8 having same issue). I think I also need to update the selinux stuff, so watch out for an updated version soon (hopefully today)
[One (M7) Original Android Development] saturday_night:
I know what pocket protection does and on TeslaOS (same Android Version) it is working perfect, in the Moment the sensor is covered you cant activate the screen by a double tap, on latest Release of XeHD you can activate The screen by a double tap even if The sensor is covered.
[One (M7) Original Android Development] ljjehl:
Is this a dirty or clean flash?? I have it working with clean flash.
[One (M7) Original Android Development] piet8stevens:
Bluetooth

After working really well for over 1 week, I had a glitch on bluetooth: could not switch it on to connect to car. Soft reboot did not help. Hard reboot did. (170113 version).
[One (M7) Original Android Development] saturday_night:
Oh, i made a dirty flash
[One (M7) Original Android Development] crashdjent:
[MENTION=921816]ljjehl[/MENTION], In the folder / sys / class / I do not have sub-folders / htc_g_sensor / Perhaps this reason is not working Doze?

And in MySensors app show info vendor Invensense for bma250, not BOSCH.
[One (M7) Original Android Development] ljjehl:
Looks like I have more work to do :\
[One (M7) Original Android Development] cadorna:
Thanks. You were right. Now I'm on 6.04.1700.13 and phone didn't hang up and reboot while talking but calls are dropped after 10 seconds of duration. Could you confirm me if yours incoming calls works fine all the time please?

Enviado desde mi One mediante Tapatalk
[One (M7) Original Android Development] shpitz461:
Yes, i have no issues with calls.
[One (M7) Original Android Development] Maxim Power:
GPS not work

No way, gps also does not work with the 17.01.24 version. Is s normal to come at the Flash two command unknown error?
[One (M7) Original Android Development] saturday_night:
Made a clean flash today and still can activate the display with a double tap while the sensors are covered. I will stay with teslaOS cause of that battery drain without pocket protection. Maybe just undo all changes that you made regarding to dt2w and pocket protection and start over again with it, on MM you have done that so nice but on N there must something went the wrong way. And i think it is easier to implement the settings into apps like kernel adiutor or exkernel manager than direkt into the system settings itself. Here is a link to a working kernel for m7 android N with perfect working dt2w and pocket protection, settings in kernel adiutor. It´s made by tathanhlam66 for teslaOS and he made the same Kernel for CM14.1 and it´s same way perfect. As he is not the most cumulative person, i think he will help you with the url´s he used if you ask him by pm or so. I hope you´ll get it to work without too much work, it would be my long-term favorite choice as a daily driver.
[One (M7) Original Android Development] crashdjent:
17.01.24 build. GPS
[One (M7) Original Android Development] FeelThePoveR:
It is normal if you use the old TWRP.

You can get the newest one in here https://android.cmphys.com/lineageos-m7/

It's still beta though and these two errors are harmless so you can continue to use yours.
[One (M7) Original Android Development] Maxim Power:
Thx! Will test it tonight. Have version 3.0.2 of the twrp. Will test 3.0.nobeta2
[One (M7) Original Android Development] shpitz461:
Interesting, it says in the TWRP description that it fixes the blank OS version in the bootloader... Thanks for the link!

---------- Post added at 08:38 ---------- Previous post was at 08:36 ----------

ljjehl, I also noticed that when placing a call, DND automatically turns on for the duration of the call. Never seen that before in any rom and in any android version...
[One (M7) Original Android Development] cadorna:
Thanks. Do you have the exact same configuration like me showed on the picture ? (except for the firmware version like talked of course.... ) Do you have an AT&T or international M7 version? I'm trying to know what is the difference to correct it and re test.

Enviado desde mi One mediante Tapatalk
[One (M7) Original Android Development] ★Michaelo★:
It seems to be a new feature or something cuz I saw that in other roms too.
[One (M7) Original Android Development] shpitz461:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.36.3218.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.04.1700.19
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4272mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0ddc65a3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.125s

This is the T-Mobile US version of the phone, PN07130
[One (M7) Original Android Development] ★Michaelo★:
It seems I found a thing that causes some of the reboots. Kernel Auditor cause them. Idk which option, but I tried KA on some other Nougat roms and had same problems. Phone just reboots after clicking the power button. After deleting it everything seems to be fine. Will try it also on Xenon when I will flash it again
[One (M7) Original Android Development] shpitz461:
That's odd, cause i'm using Kernel Adiutor to set a few things on startup, and I don't experience any reboots.

Only thing I do experience is touchscreen not responsive, it happens on rare occasions, and not sure if there is a pattern to it not working. I just hold the power button until the phone reboots. The screen turns on when I press the power button, I just can't touch/swipe/click anything.
[One (M7) Original Android Development] ★Michaelo★:
What are you changing in the KA?
[One (M7) Original Android Development] shpitz461:
Battery > Fast charge

Misc > Vibration Strength

Misc > Host Name

That's it.
[One (M7) Original Android Development] ★Michaelo★:
Well, I'm underclocking CPU (to 1566Mhz), changing read-ahead and I/O scheduler. Maybe that's because my phone reboots after that
[One (M7) Original Android Development] specione:
If I use speaker , in the next call I make I cannot hear anything is there a fix? Ty
[One (M7) Original Android Development] Krysadio:
Hi, what version of opengapps I should download? I download ARM 7.1 NANO and when i open Play Store it keeps "checking info" and then error pops up.

Another thing is that I turn off double-tap wake up and its still possible.
[One (M7) Original Android Development] crashdjent:
Pico
[One (M7) Original Android Development] ljjehl:
I use micro for mine, so not sure why you have problems with nano
[One (M7) Original Android Development] shpitz461:
i use nano, ARM/7.1/Nano on http://opengapps.org/

---------- Post added at 18:05 ---------- Previous post was at 18:04 ----------

Try to clear cache on Google Play Services/Store.
[One (M7) Original Android Development] Krysadio:
Ok, I solved the problem. I can't be connected to wifi if I want to add google account. I changed to cellular data and it works for me.

But what about dobule-tap wakeup? If I disable it in settings its still works.
[One (M7) Original Android Development] crashdjent:
It's known bug
[One (M7) Original Android Development] tnakir:
I haven't had any restarts for days now. The rom is very stable, fast, and the battery life is great. Thank you.
[One (M7) Original Android Development] ★Michaelo★:
GPS works for me also on latest build
[One (M7) Original Android Development] ljjehl:
Just pushed another update. This includes working ambient display and thumbnail preview (WIP) in camcorder.
[One (M7) Original Android Development] piet8stevens:
Bluetooth

Still on Jan 13 version - bluetooth still unreliable - had to do hard reboot both this morning and tonight to get the phone to connect to the car. Are there any known workarounds? Are the later versions better in this respect?
[One (M7) Original Android Development] ljjehl:
probably not. I haven't changed anything yet in BT lately. I hear that it's a global issue with older devices. I've been hearing complaints about it in the XE maintainers group.
[One (M7) Original Android Development] Maxim Power:
GPS not work

Unfortunately, the GPS does not work despite the new Rome. I have unfortunately no idea what I should still try. Latest twrp version tried. Before and after the installation tried new kernel from Tesla. Older versions of xhd installed on new per dirty update. All data is completely deleted and the latest version installed. With Android 5.0.2 of nanuseven it works without problems.
[One (M7) Original Android Development] shpitz461:
Did you try an actual app that uses GPS? GPS Info is not working for me again, but navigation apps work fine.
[One (M7) Original Android Development] Krysadio:
Hi I see new problem and its BIG PROBLEM FOR ME. I want to share internet connection from my phone to computer by USB connection but I can only do it when cerrelar data is OFF same as HOTSPOT WIFI.

1. So if I use Cerrelar Data I cant share internet by USB or HOTSPOT

2. Double-tap wake up still works after disable this option in settings
[One (M7) Original Android Development] gitzolinick:
KEEP CALM!!!!!
[One (M7) Original Android Development] ★Michaelo★:
Can I dirty flash new build from the previous one? Or clean flash is recommended
[One (M7) Original Android Development] ljjehl:
Since half the update is in frameworks, its usually recommended to flash clean. I never hold people back from flashing dirty, but if it doesnt work as expected, then you know what you need to do.
[One (M7) Original Android Development] ljjehl:
Hotspot is another one I'm looking into fixing. Not sure how long it will take me, as I have little time to spare before Sunday. Thanks for your patience.
[One (M7) Original Android Development] ljjehl:
Just pushed another round. Hotspot is now working. Have fun!!
[One (M7) Original Android Development] rahimskala:
\m/ =D>
[One (M7) Original Android Development] shpitz461:
Camera is crashing for me after flashing the build from earlier today, when I switch to Video.

Attached is log.
[One (M7) Original Android Development] shpitz461:
I just flashed the latest build and the Camera crashes when switching to Video still. Tried clearing cache to no avail.
[One (M7) Original Android Development] Stehlnix:
There are two camera apps in this Rom, in one of them Video is working, hope that helps temporarily

On another note, I apreciate the updates, but why did you take out pocket detection? :(
[One (M7) Original Android Development] ljjehl:
probably a result of a quick (dirty) build. I just built a clean version, hopefully nothing broke this time. I will test before I post, though
[One (M7) Original Android Development] Stehlnix:
Very much appreciated ^^
[One (M7) Original Android Development] shpitz461:
Yeah, the other camera sucks, you need to swipe the left edge to select video/photo, i prefer the one we had a build before.

Snap is much better than the camera2 app.

It's odd, maybe a glitch in the build that there are 2 cameras, one is snap, the other is camera2, both v2.0.002...
[One (M7) Original Android Development] Stehlnix:
Maybe its my gapps package but the other builds also had two camera apps ?
[One (M7) Original Android Development] ljjehl:
New Build pushed.

Fixes are:

Bluetooth

Snap records with preview thumbnail

Edit: a small caveat. May have broke sim for the moment. wtf... :crying:

All good now. I pushed another that should get the above as well as SIM working
[One (M7) Original Android Development] shpitz461:
Many thanks, do you see any problem dirty-flashing or do you recommend a clean install?

Also, as for Slim Launcher, you're not going to try and include it? pretty please :)
[One (M7) Original Android Development] ljjehl:
I'm not going to give up on Nova, but it's possible to let Slim Launcher co-habit with the other launchers.

As for Bluetooth, the issue with turning on/off has been fixed. Call audio is working fine, but media audio might not be. You'll have to tell me.

Currently file transfers via bluetooth is still broken, has been for all N devices as far as I know.
[One (M7) Original Android Development] shpitz461:
That would be great, if you could include both launchers, just like you included 2 camera apps :)

i'll give BT a thorough check tomorrow on the way to work.

Never used file xfer with BT, and probably never will...
[One (M7) Original Android Development] piet8stevens:
[MENTION=921816]ljjehl[/MENTION] Great news re. BT. I will flash & test & let you know how it goes. Thanks a lot for all the work.
[One (M7) Original Android Development] ljjehl:
Ok, done. SlimLauncher is now provided as well as Nova on this rom
[One (M7) Original Android Development] shpitz461:
Many thanks. Is there a way to unpack the system.new.dat and extract files from the image?

There is an extractor but it only works up to MM afaik.
[One (M7) Original Android Development] ljjehl:
Never dealt with it. I just recompile a new rom as I see fit and need
[One (M7) Original Android Development] cadorna:
Is it OTA working? I'm on 170113 and checking updates manually to read that there is no new updates!

Enviado desde mi One mediante Tapatalk
[One (M7) Original Android Development] ljjehl:
Thanks for letting me know. Guess it might not be working for the moment
[One (M7) Original Android Development] Stehlnix:
Normally it works, used it to update from 170113 to 170127

But now it tells me to check if xenonhd is supporting my device, im still on the 27 build, gonna download new build manually now but wanted to let you know
[One (M7) Original Android Development] shpitz461:
So far so good, music streaming was working fine, will test more tomorrow.

My video issue with Whatsapp seems to be resolved, must be related to the snap video crashing, not sure...
[One (M7) Original Android Development] Stehlnix:
I won't demand anything because I know that this isn't your job but more of a hobby, but could you please put pocket detection back in or at least fix dt2w so that it can be turned off?
[One (M7) Original Android Development] ljjehl:
Fixing pocket detection would be easier than having a switch for DT2W. I would have to redo all the T2W code, which would take time to do.
[One (M7) Original Android Development] Stehlnix:
Either way I'd appreciate if my phone wouldn't turn on in my pocket all the time xD

Like I said before, your work is much appreciated, this ROM is perfect for me if it weren't for the dt2w/lack of pocket detection

And no, I don't play pocket pool, its just that most of my pants got very thin cloth for the pockets so the digitizer reacts to my leg

---------- Post added at 05:20 AM ---------- Previous post was at 05:10 AM ----------

I edited the /sys/android_touch/tap2wake file to turn it off, is it safe or could this cause problems?

Never messed with init.d and only looked it up for this case so I don't know if its safe
[One (M7) Original Android Development] ljjehl:
That's one way to turn it off. Its fine and won't cause issues.
[One (M7) Original Android Development] tnakir:
Naaah... I had 4 random reboots in the last 2 days...

When its stable, its stable and it works fine for days, when it doesn't, its a ****storm!
[One (M7) Original Android Development] shpitz461:
I was too quick to state my video issue with Whatsapp was fixed. It took longer to occur, but it still does.

Hangouts video works great. Must be an issue with Whatsapp and this rom.

Had no issues with BT streaming.

Another odd this is, since the 1/29 build, Dolby Atmos is crashing when I run the app, never had that with any other build.

Another thing that is happening lately is when I dirty-flash the rom, then flash dolby atmos and reboot, the phone reboots a few seconds after the launcher appears. This is happening in a loop.

Only way to get out of this boot-loop is to clear cache/dalvik in recovery, then the phone is fine.

I'll provide logs tonight.
[One (M7) Original Android Development] piet8stevens:
Disabling tap2wake

I never knew that is how it works. I prefer to not have tap2wake and this is really an easy way to switch it off. Just change the 1 to 0. Thank you!

Note: so far, on the 0128 version, bluetooth seems to work! No issues switching off and back on. Hope it will continue like this.
[One (M7) Original Android Development] shpitz461:
Booted into recovery, did a backup, then rebooted.

It would boot-loop after I see the launcher for a few seconds.

Something is up, going to try a clean flash to see if this and the Atmos issue go away.

---------- Post added at 18:37 ---------- Previous post was at 17:49 ----------

Ok, this is happening every time I boot from recovery, launcher will show for a few seconds then phone reboots, in a loop.

Attached is the last_kmsg.

---------- Post added at 18:51 ---------- Previous post was at 18:37 ----------

ok, I wiped everything but sdcard, then flashed rom and Atmos.

After boot, Atmos is opening w/o crashing.

Going to do a clean flash of rom, gapps, teamblackout themeready apps, then atmos. Going to start clean.
[One (M7) Original Android Development] ljjehl:
May be the combination of gapps and such, as the rom works just fine for me

I use Micro version of openGapps.. BTW, never saw a kmesg link
[One (M7) Original Android Development] shpitz461:
Odd, I swear I uploaded the log...
[One (M7) Original Android Development] shpitz461:
Ok, started fresh with a clean flash, everything seems to be working great!

Only beef is with BT, when making VOIP calls BT controls still operate in audio-streaming mode.

Dolby Atmos works great.

Had a few quirks with the volume still stuck in audio mode instead of ring mode, and I could not turn it down all the way to vibrate, had to reboot.

Also, in the morning, data would not connect (4-5 bars were showing) until I rebooted.

I'll report more as I use the phone more, many thanks ljjehl!!!
[One (M7) Original Android Development] tinyturtles:
I've been using this ROM as a daily driver for quite a while now, and it's absolutely solid. Other than the occasional random reboot, it's been fantastic.

However, on the most recent build, I've been having some issues. I am doing a dirty flash from 13 Jan build. For root, I use SuperSu so I am opening the app and updating the binary (either through the "normal" button or through TWRP 3.0.2.0). Doing this causes me to, upon restart, be permanently stuck at the Xenon HD boot animation. Is this happening for anyone else? Does anyone know how I can fix it without needing to resort to a clean flash?

Thanks!
[One (M7) Original Android Development] shpitz461:
SuperSU is built-in, no need to do anything. It is part of Privacy...

I was also dirty-flashing between builds, but had many issues coming up over time. I did a full clean flash last night and all is well...
[One (M7) Original Android Development] tinyturtles:
Either way, my problem is when SuperSU binary updates with the most recent build. Just wanting to see if there's anything else I can do before the clean wipe!
[One (M7) Original Android Development] shpitz461:
Not sure why you would need a binary update? I don't have supersu installed and root works great...
[One (M7) Original Android Development] tinyturtles:
Just used to SuperSU because it was on my previous phones too. It was working fine on a previous build so I don't know why I'm not able to get it running now.
[One (M7) Original Android Development] shpitz461:
I've used SuperSU in many other roms as well, but Xenon N doesn't need it, it's built-in into Privacy. Donno what to tell you...
[One (M7) Original Android Development] Maxim Power:
GPS does not work

Hi community,

Have again the latest rom XenonHD-170129-experimental-m7 installed.

Unfortunately the gps does not work.

GPS Status, AndroiTS GPS, G Maps and Waze do not find satellites.

In appendix are some screenshot and my GPS.conf original and modified both do not work :(

Has anyone else an idea

THX

UPDATE:

I have fixed my GPS problem!

I had left the GPS enabled "high accuracy" and then first flashed on XenonHD.

Now GPS works perfectly.
[One (M7) Original Android Development] shpitz461:
GPS Status app shows 19 in view, 0 in use. ljjehl, something is amiss in this regard, as this was working in a prior build (forgot which), and the status apps work fine in other roms.

But Google Maps and Waze work fine. Did you give them permission to use GPS? there should be a popup asking you when you launch the apps...
[One (M7) Original Android Development] Maxim Power:
Yes all permissions on allowed
[One (M7) Original Android Development] cadorna:
If you want to mount system partition like rw , then you need super su, with the included root you can't. Also some apps that require root access didn't work fine for for me until super su was installed. Total commander for example.

Enviado desde mi One mediante Tapatalk
[One (M7) Original Android Development] shpitz461:
I'm using Mixplorer and writing to /system works fine...