yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] dadi11:
Hello [MENTION=6936389]tinyturtles[/MENTION].

I just thought if removing wakelock blocker doesn't increase battery life, but only removes few wakelocks that (from what you write) also doesn't cause any battery drain had any sense? Do you have any test or proves that can show that it is really a culprit of some issues? For example comparsion between a build with and without wakelock blocker battery life or wakelocks. Personally I think that if removing it didn't improve battery life noticeably it is better to bring it back and give a chance to block other battery-draining wakelocks with it
[One (M7) Original Android Development] tinyturtles:
Hi!

I don't really have any evidence other than my own phone. After a day or two on the build, my battery life has calmed back down (from 1.5% per hour while idle to 1% or less). I definitely agree with you that it's a good option to have; for me, personally, all the ROMs I have used with the wakelock blocker kept my phone awake longer. BetterBatteryStats also usually shows my CPU speeds as different - much more 384 MHz and much less Deep Sleep. As I said in my previous post, I did a dirty flash, not clean. Since then, I've wiped my cache again through TWRP (dalvik too) and the ROM has started behaving better. In my daily usage, the only problem I have now is random reboots (1-5 times a day, usually closer to 1 or 2).
[One (M7) Original Android Development] ljjehl:
It's hard to catch a random reboot, but you can possibly grab a logcat of it by using CatLog (from GPlay) and set it up to record. I can bet it may take a bit to grab that reboot, unless you can push it by doing something specific.
[One (M7) Original Android Development] ljjehl:
Update!

Well, added another update with a commit that may have lessened the speakerphone switch issue. I noticed that after a speaker hangup I lose call audio, but if I toggle bluetooth off and back on, I seem to get it back. It seems to be a routing issue between bluetooth and speaker, so hopefully I can look at the code and make a manual edit.

Substratum has also been updated.
[One (M7) Original Android Development] shpitz461:
Yeah, that's what I experienced with speaker/bt modes and how i temporarily fix it.
[One (M7) Original Android Development] tinyturtles:
On it! I will try. Thank you :)
[One (M7) Original Android Development] ajcsessz:
After installing the last update, SuperSU wanted to update itself, I let it, now the phone doesn't start. the logo spins for hours, nothing happens.

Please advise.
[One (M7) Original Android Development] An3skmbi:
For anyone using substratum themes, above issue (system ui fc) is caused by substratum after dirty flash. After a minute or two, substratum disables the theme and you can actually use your phone. Then simply enable your theme again and all is well. Seems I was just impatient first time round :p
[One (M7) Original Android Development] shin06:
thnx for rom, can you fix please, whe calling DND icon appear on status bar, srry for my poor english
[One (M7) Original Android Development] ★Michaelo★:
I guess that one of the nougat features and you can't change it
[One (M7) Original Android Development] tinyturtles:
Instead of letting SuperSu update its own binary, flash the zip file through TWRP. That's how I've been getting SR3-SuperSU-v2.79-SR3-20170114223742 to work.
[One (M7) Original Android Development] Krysadio:
I dont know whats happened but my nfc dont work anymore.
[One (M7) Original Android Development] fouineur74:
Hi everybody,

I'm come to lineage (see my signature).

Installation -> Ok

But, i have a little problem...

where is E-Mail application as i had under lineage ???

I don't like gmail (i have 6 emails addresses, and E-mail is very easy to manage them )

Thank you in advance
[One (M7) Original Android Development] ★Michaelo★:
Just use different app for mail
[One (M7) Original Android Development] dream79:
@ the devs,

super, just installed the new Version and bluetooth semms to be switchin on and off just fine.

Had a littel other issue today regarding bluetooth, I will se tomorrow if that is also fixed.

You guys are good.
[One (M7) Original Android Development] n0j0e:
Did you using LiveDisplay on automatic mode?

[size=-1]Send with much love & Android.[/size]
[One (M7) Original Android Development] shpitz461:
ljjehl, i'm wondering how good/reliable is flashing a new build after wiping cache/dalvik and system, leaving data untouched?
[One (M7) Original Android Development] ljjehl:
If its the same ROM and version, most times its fine. I usually only wipe cache and dalvik, but not all the time.
[One (M7) Original Android Development] shpitz461:
Yeah, only with same rom and android version. Cool, i'll give the new build a shot.

Did experience BT not connecting when I went to the car to drive home, had to reboot for BT to work again.
[One (M7) Original Android Development] ljjehl:
I guess I'll have to checkout that CarKit issue. I know my vehicle was trying to connect to my device before in the past, drove me nuts when my bluetooth was on :D
[One (M7) Original Android Development] c3mfux:
Hey guys I've been experiencing an issue with lockscreen date text with the latest 2 builds(0323&0321). I don't know what triggers this so far I sometimes unlock the device to find it so.

Soft reboot doesn't change it back to normal, only rebooting does. Have a go at the screenshots attached.

edit: also after checking out the screenshots, the carrier text also seems to move closer to the center a bit.

Has anybody had this or any advice or sth. cheers.
[One (M7) Original Android Development] ★Michaelo★:
Try both and decided which one is better for you
[One (M7) Original Android Development] shpitz461:
This is how mine looks like
[One (M7) Original Android Development] gitzolinick:
If you write here xenon is better, if you write in aicp thread aicp it's better. The best thing is to install both all together by flashing aicp on xenon before, and after flashing sense rom. Be careful to don't clean cache.

The goal is the mixing of features (it will be like a tomato, Nutella and ananas pizza:so good)
[One (M7) Original Android Development] tinyturtles:
No, I turned it off altogether.
[One (M7) Original Android Development] dream79:
ok, I've been to fast in writing tta bluetooth is is now well switchin on and off.

Could not get it started this morning again, so still only after a reboot.
[One (M7) Original Android Development] ljjehl:
Probably after you messed with speakerphone
[One (M7) Original Android Development] An3skmbi:
Unfortunately not. I also had to reboot yesterday to fix bluetooth, and did not use speakerphone. Bluetooth stopped syncing somewhere during the day. Switched it off, had to reboot to get it back on.
[One (M7) Original Android Development] dream79:
I didn't use the phoe as phone at all since the last update :D so, no speaker phone, which I anyway never use
[One (M7) Original Android Development] piet8stevens:
Multirom

That did the trick. I am now the proud owner of an HTC M7 with multirom and patched to March 5, 2017!! I now have one rom on 0207 and one (dirty) on 0323. Am also terribly low on storage space so will need to move one rom to OTG.

Did not have a chance to test BT in my car, but was able to switch it on and off a few times. Phone app crashed once, but worked for the rest.

Thank you! Will keep you updated on BT.
[One (M7) Original Android Development] ms31:
I had similar issue with date & time. It fixed itself after phone reboot, but start moving again. I was thinking to post a comment as well. Then, I finally did a clean install of a ROM, after wiping data. For nearly 2 days there is no issue with date & time.
[One (M7) Original Android Development] gehess:
This may seem like a silly question, but are Android security patches always released on the 5th of each month?
[One (M7) Original Android Development] saturday_night:
Not allways, there are some on 2. or 3. but usualy there are two and the latest one is allways from 5. of a month.
[One (M7) Original Android Development] dream79:
Just a quick update on the blue tooth issue.

Today I was able to turn it off and on a few times manually, that seems to be fine.

I will test with system profiles again.

During the weekend the device lost all known blue tooth pairings though.

But no issue to pair again, so no Problem.
[One (M7) Original Android Development] ljjehl:
There may be an issue that the system is not sufficiently terminating the connection fast enough, so it needs some wait time.

I have another untested build with a commit that addresses an issue like the above scenario. I have not been able to test this yet, so I wonder who all wants to test this one?? :P

Pushed to mirrors for all that want to try out the BT addition. Hope it works :D
[One (M7) Original Android Development] shpitz461:
This morning BT wouldn't turn on again, showed as turned on, but no devices could connect. Turned it off and rebooted, when it came back it wouldn't turn on still, had to do another reboot. 3rd time was the charm.

Never experienced BT pairings disappear myself...

Sure, I'll test the new build. Is wiping dalvik/cache sufficient? should I also wipe system?
[One (M7) Original Android Development] ljjehl:
dalvik and cache should be enough, as the only things changing is Bluetooth areas and maybe a few apk updates. I'm still looking into another one that reduces the timeout of the connection attempts for GATT services. Not 100% sure of that relation to HFP and A2DP profiles, but here's a link to brush up on what you may not know :

https://en.wikipedia.org/wiki/List_of_Bluetooth_profiles

:laugh: :good:
[One (M7) Original Android Development] piet8stevens:
I can test. I am on 0323 now with multirom (dirty flash as mentioned before). Tested BT - still needed to reboot to get connection in my car. But overall, 0323 seems to be very fluid, nice. Sound quality during phone via BT is fine.

Will try 0327 tomorrow or Wed.

Thx for all the work. I am very happy with 0323.
[One (M7) Original Android Development] shpitz461:
Cool, tnx!

Any chance you can replace SlimLauncher with the version I recommended? v1.2

Thanks
[One (M7) Original Android Development] piet8stevens:
ROMCleaner can do that for you - remove the "wrong" one and add the right one (for you)
[One (M7) Original Android Development] ljjehl:
Haven't figured yet what you said was not working or missing in Slimlauncher vs 1.2
[One (M7) Original Android Development] shpitz461:
Tons of features, if you look @ the settings screen in both version you'll see it right away.

Here's what I see in v1.2.
[One (M7) Original Android Development] An3skmbi:
Hey guys, looks like we have joy. Dirty flashed 27/03, turned BT on, success, turn BT off, wait a couple of seconds, turn on again, success! :D

However I still have those wakelocks keeping my phone awake while BT is on (only about 30% deep sleep when completely idle for 30 mins).

- msm_serial_hs_brcm_rx

- msm_serial_hs_brcm_tx

- msm_serial_hs_dma

- msm_serial_hs_rx

Edit: [MENTION=921816]ljjehl[/MENTION] maybe check this out https://xdaforums.com/showthread.php?t=1786981
[One (M7) Original Android Development] piet8stevens:
Multirom & 0327

Tried to create an additional rom on a usb stick via OTG from an android backup (for dirty flash of 0327 over 0323). First trial went through many steps from Installing ROM through to Restoring System to then end with a red error "extractTarFork() process ended with ERROR: 255".

I then reformatted my usb (tried fat32 and exfat), but now, it cannot even mount: red error "E: failed to mount location "/dev/block/sda1 (vfat)".

Any ideas?

One other question - maybe obvious, but just to be sure: when I make a nandroid backup, that is of the primary rom, right?

Thank you.
[One (M7) Original Android Development] genseng:
Nandroid will restore the system as well. You need to use an app like Titanium Backup Root to keep app data between ROM changes. You can often keep your data between updates of the same ROM (called a dirty flash) although this can sometimes cause problems.
[One (M7) Original Android Development] liam_davenport:
A nandroid is a full rom backup, you can use titanium backup to backup apps/data
[One (M7) Original Android Development] daduy:
Got to say i am really happy with the latest beta, havent experience any bug for 24 hours. Thanks Dev!
[One (M7) Original Android Development] macross7ra:
This is the only smooth custom rom for Android 5.X, at least no lag no hang for 5 days, but IR buster not working...
[One (M7) Original Android Development] ljjehl:
It works great with IR remote. Not sure yet why some like Peel do not work.
[One (M7) Original Android Development] umarmasroor:
Can someone please pullout messaging.apk for me please

thanks
[One (M7) Original Android Development] aviranzerioniac:
Here you go.
[One (M7) Original Android Development] umarmasroor:
I am getting parse error... How can i solve it?
[One (M7) Original Android Development] aviranzerioniac:
Here is the apk. If this doesn't work, go to apkmirror.com and download the Google messaging application, ditto from play store. That should be the same application. If not, it is even there in the flashable zip of the rom. The location is /system/priv-app/Mms/
[One (M7) Original Android Development] umarmasroor:
My bad luck again getting parse error...

The app on play store is not the same as in the rom..
[One (M7) Original Android Development] umarmasroor:
Gapps link for this rom...
[One (M7) Original Android Development] ziaulh.ch:
How is the battery on this rom guys? If compared to Sense or GPE? And btw, have anyone been able to use CM12 themes on this AOSP?

Thanks in advanced!

---------- Post added at 01:49 PM ---------- Previous post was at 01:17 PM ----------

Slim Gapps would work I think. http://xdaforums.com/slimroms/general/gapps-official-slim-gapps-trds-slimkat-t2792842
[One (M7) Original Android Development] neptune_:
Are there any random reboot issues or problems with camera (reboot using flash, etc.)?

Is it safe to restore apps from Titanium Backup, coming from CM 5.1.1 rom?
[One (M7) Original Android Development] ljjehl:
Build 5 Update!!

Finally have a new update!! Posts 1-3 have been updated. Enjoy!!
[One (M7) Original Android Development] neptune_:
This ROM is really wonderful! One of my favs

Wondering if there's a way to get sound panel to show at bottom of power menu? Normally in other ROMs, there are icons for silent, vibrate, sound, etc. horizontally just below the power menu options (reboot, shutdown, etc.).

Thanks
[One (M7) Original Android Development] ljjehl:
Probably not. We already have that option setup with vol +/-, it can be accessed in both lockscreen and normally.
[One (M7) Original Android Development] neptune_:
Ok fair enough. Is there a quick tile for sound toggles?
[One (M7) Original Android Development] Stephen:
Moderator Information,

Thread has been cleaned. Please try to give as much information as possible and provide log cats were possible as well.
[One (M7) Original Android Development] Heisenberg:
Thread cleaned, again.

If you're going to provide feedback, do so

constructively

, provide logs, provide detailed information. Without all that, and while using the term "disgusting' to describe the ROM, it's nothing but a smear campaign. This is the final warning on this matter.
[One (M7) Original Android Development] paulbearry:
Is there any way to shut off the music visualizer on the lockscreen?
[One (M7) Original Android Development] ljjehl:
Now you're going to make me try this out. I've used it maybe once before. I never bothered, as using SDcard takes much longer to setup and I never had that patience, lol

If you backup normally, yes. TWRP works separately from MR. You kindof already have a backup of MR on sdcard. /Internal Storage/multirom/roms/ is the location. If you want an actual backup of your internal rom to MR, you can also use "Swap ROMs" and copy primary rom to secondaries.
[One (M7) Original Android Development] piet8stevens:
I am having some weird problems copying files from my m7 to my PC via usb. Some files just won't copy. I am trying to just backup roms to my laptop, but for some reason, the file boot.emmc.win won't copy. I then tried to copy it in amaze from its original location to a new one on the phone, and that also failed. Any ideas? Thx.
[One (M7) Original Android Development] ljjehl:
Just copy the whole folder. I did and everything transferred over
[One (M7) Original Android Development] shpitz461:
Went to drive home from work after a whole day @ the office, BT was ON but would not connect. Had to reboot to get it to connect to the car. Donno what gives...

I'm running HTC firmware, not GPE, not sure if that would make a difference.
[One (M7) Original Android Development] piet8stevens:
Copying

Did that. It only created an empty folder. Then I manually added the files to it. It is really weird - never had this before. It only happens from my phone. It also happens on the phone when I try and copy the whole folder in Amaze for example. Mounting problem?
[One (M7) Original Android Development] ljjehl:
Could be the cable itself. Or maybe you need to set the folder as r/w.
[One (M7) Original Android Development] piet8stevens:
I am running 0327 with dirty flash but get an error from substratum:

Phone keeps stopping...
All enabled overlays for this app have been disabled.

I did have some issue accepting a phone call - needed to enter the security code before I was able to pick up the incoming call.

Later tonight or tomorrow, I will try to do a clean flash and report back.
[One (M7) Original Android Development] dream79:
so, I'm on the latest build now, so far no issues with blue tooth but the phone rebootet twice in the last 24 houres.

On the bright side, it runs better than an Iphone 6+ :D

Thanks guys
[One (M7) Original Android Development] ljjehl:
Rootless Substratum does have some sort of error toast for themes that may not be compatible for it. This may be what it does. So far I havent seen that type of error, though I havent tested for substratum issues at this time.

I currently am testing a new route with Magisk (XenonHD global direction) I'll go ahead and push this version for y'all to try out. So far it looks good. I still see issues with speakerphone causing audio issues unless bluetooth is toggled (like before) but bluetooth seems more robust in toggling so far. (due to a commit I added) We'll see how this one goes, lol.
[One (M7) Original Android Development] shpitz461:
lol, cool, thanks!
[One (M7) Original Android Development] An3skmbi:
I got this message this morning with youtube. It kept crashing, then got the substratum message that youtube keeps closing and all overlays for youtube has been disabled, then youtube was fine...? Also get it for system ui after dirty flashing. Might be related only to specific themes. I'm running Swift Dark.

Yay :D
[One (M7) Original Android Development] Sn1cket:
I switched from LineageOS to XenonHD and would like to know how the update process works. In LineageOS I just tap update and the new version is installed in system. In XenonHD do I have to update via recovery mode or am I missing something?
[One (M7) Original Android Development] ljjehl:
Update!!

pushed another build with another commit :

Use Audio HAL3.0 API for routing and volume management

Hopefully this helps, as I just tested that bluetooth toggles fine so far. Let me know!!
[One (M7) Original Android Development] shpitz461:
Downloading now...

With all the latest builds I'm experiencing extremely low call volume...
[One (M7) Original Android Development] piet8stevens:
Rootless substratum

I removed magisk and returned to just standard supersu in /system as getting my setup with magisk to work took me too much time. So, I would think that that is not the reason. In the mean-time, it has stabilized, so may just have been startup issues from dirty flash. Not sure. Thanks anyway.

---------- Post added at 04:01 AM ---------- Previous post was at 03:30 AM ----------

Wow, I cannot keep up with the updates. I had just dirty flashed 0329 and now there is already a 0330. Should I upgrade again?
[One (M7) Original Android Development] ljjehl:
Up to you. I made this build last night before I went to sleep, it completed with no errors, but had no time to test the Bluetooth intensively for quality. I was not able to test the phone portion yet before I went to work.
[One (M7) Original Android Development] ljjehl:
Anything I need to know from the users today?? Would be nice to see where we stand regarding Bluetooth and volume management.
[One (M7) Original Android Development] ljjehl:
Still another update, v 3/31. Trying to get the carkit option to work well with the rest of the options (switching between bluetooth devices)

I haven't tested the above option, but I do know calling works (with exception of speakerphone option still causing issues requiring switching BT off and on again.)
[One (M7) Original Android Development] RobeStar:
Hi ljjehl, would be possible to flash LMY47O.H19-stock_062416 Firmware without stock recovery & Boot IMG? I'm S-ON and wish chance to flash last firmware version...

Regards,

Robe
[One (M7) Original Android Development] ★Michaelo★:
No you can't. You need to be S-OFF to do it
[One (M7) Original Android Development] RobeStar:
Ok, thanks for your reply Michaelo
[One (M7) Original Android Development] shpitz461:
I received one call yesterday on build 3/30, volume was great, so was the audio quality! I think the last update was tremendous!

I will do more testing when i drive back home at the end of the day.

Music streaming was working well, as it always did, didn't get a chance to test the interaction between the BT profiles...

Going to dirty flash 3/31

---------- Post added at 08:23 ---------- Previous post was at 08:23 ----------

Do we still need SuperSU now that you've added Magisk?
[One (M7) Original Android Development] piet8stevens:
Hail, hail - BT fixed!

Hail, hail to the great Ljjiehl,

he who could slay,

the bad, bawdy BT bugaboo

through a great many updates

despite some nasty forum jibes

Hail, hail to the great Ljjiehl

May he never fail

I am on 0330 and was able to switch BT on and off and pair with the car at least 5 times today, without one single reboot being needed! A big thank you! Calling sound was fine, too.

One question: I do not have supersu any more. Are we supposed to add that ourselves with Magisk? - Question solved: I upgraded to Magisk v12 and I can again grant su rights. Not sure what was wrong before but I could no longer run TiBu and some of my tasker tasks failed because they could not get the right permissions.
[One (M7) Original Android Development] ljjehl:
LMFAOOO!! Thats a funny poem!!

Magisk is SU, though I am still a bit a little noob on this one, also. It was a global move by the XenonHD team. Seems that we do have more than one option, depending on what works best for everyone. v12 did come out, yes. I guess that was the problem, so the reason why Magisk updated. **shrugs**
[One (M7) Original Android Development] ljjehl:
I would say no, but not sure how well Magisk v12 works at this time (as said on previous post)
[One (M7) Original Android Development] shpitz461:
My magisk 12 fails Safetynet check, CTS profile something...
[One (M7) Original Android Development] ljjehl:
It does, a known issue right now. Don't know if it makes it for the other su methods though... Other maintainers had successes, but don't currently know the combination to have it pass CTS yet
[One (M7) Original Android Development] shpitz461:
question is: do we care...? lol

I flashed supersu out of a habbit, so maybe i'll redo my flashing by wiping system as well and redo it all except leaving /data alone.
[One (M7) Original Android Development] saturday_night:
Magisk v11.6 had a bug where it sometimes hide the su from itself. Dont know if that is solve with v12, but if you sometimes dont have root after a reboot, just go into magisk settings and uncheck Magisk Hide and reboot, root will be back. For passing Saftey Net Check, you need to enable Magisk Hide, but as said before there was a bug in v11 with this option.