yashsingh1/xdaforums huggingface dataset:
[Moto X Android Development] riyosakura:
- BT problem is known problem, and there is no fix for it atm. And i doubt there will be one in the future, since Moto X is lack of devs.

- I have a working auto-connect WLAN in my phone. Someone has reported, it just happened for certain Wifi Router. It is a bug though, since it not working properly for any type of Wifi Router. So, I suggest to change your WLAN settings to make it work properly with Moto X LOS. Maybe somewhere around security (WPS settings)

- im not using any ecnrypted system, so i dont know about it.

im using LOS as my daily driver. for me, the only major problem with this ROM is, sound noise from recorded video. In that case, i rarely use the sound recorded by the phone. I just mute it and insert a music for it. :D

changing mic type on the build prop fix it. but in exchange you will unable to use loudspeaker while calling. Calling via WhatsApp or any other calling apps are working good though.
[Moto X Android Development] VitaTaf:
It's not required.
[Moto X Android Development] sharukins:
[MENTION=5573353]VitaTaf[/MENTION]: I've seen you did the rebranding in lineageOS and send the commits upstream.

Could you also add ghost to the lineage-build-targets file in LineageOS/hudson for weekly cm-13.0 branch?

Would be great to have official weeklies as soon as they start building. (That would probably save you the time to do the builds yourself.)
[Moto X Android Development] Ishaan Gupta:
I'm getting error 7 in TWRP when flashing this over the last build. The updater script looks the same in both the builds so I'm not sure what is going wrong.
[Moto X Android Development] VitaTaf:
Thanks for the instructions—I will look into it soon.

Is that the only error shown? Could you try using a different version of TWRP?
[Moto X Android Development] Ishaan Gupta:
I'm getting the same error even if I try to flash the 20/01 build over itself. It flashed fine a few days back from the same TWRP. I think I will have to clean flash this...
[Moto X Android Development] Faisi904:
How to root the latest build 01/19?
[Moto X Android Development] mringis:
I flash supersu zip and it do well
[Moto X Android Development] Faisi904:
For me it is causing bootloop 03feb build.
[Moto X Android Development] _cf:
do not disturbe quick setting

anyone having trouble with the do not disturbe feature? I used it a lot, and now it never disable automatically.. if I set it for an hour, it will be on until I turn it off, I really miss this, and I'm sure it is a silly and simples bug

great work! let's make it an official ROM soon :)
[Moto X Android Development] mringis:
Mine still build 20/1. I don't know about latest build. Maybe tonight i will try it

Updates: Flash 03/02 build + SuperSU no problem so far
[Moto X Android Development] 7bob:
Fix problems with encrypted user partition

I currently have the problem that I cannot decrypt my user partition (/data) because of the timeout in cryptfs. After entering the encryption password, the following log output appears, then the device hangs and does not continue booting:

02-06 18:07:09.361 186 212 D Cryptfs : unmounting /data succeeded
02-06 18:07:09.639 2039 2041 D BootAnimation: Use save memory method, maybe small fps in actual.
02-06 18:07:09.882 186 212 D Cryptfs : Just triggered post_fs_data
02-06 18:07:09.884 112 112 W kworker/0:2: type=1400 audit(0.0:33): avc: denied { net_admin } for capability=12 scontext=u:r:kernel:s0 tcontext=u:r:kernel:s0 tclass=capability permissive=0
02-06 18:07:09.884 112 112 W kworker/0:2: type=1400 audit(0.0:34): avc: denied { net_admin } for capability=12 scontext=u:r:kernel:s0 tcontext=u:r:kernel:s0 tclass=capability permissive=0
02-06 18:07:09.884 112 112 W kworker/0:2: type=1400 audit(0.0:35): avc: denied { net_admin } for capability=12 scontext=u:r:kernel:s0 tcontext=u:r:kernel:s0 tclass=capability permissive=0
02-06 18:07:09.884 112 112 W kworker/0:2: type=1400 audit(0.0:36): avc: denied { net_admin } for capability=12 scontext=u:r:kernel:s0 tcontext=u:r:kernel:s0 tclass=capability permissive=0
02-06 18:07:10.323 2056 2056 I recovery: Recovery image already installed
02-06 18:08:00.003 186 212 E Cryptfs : post_fs_data timed out!

This problem was already occasionally present on Cyanogen. However, it prevents me from booting at the moment.

I tried to change the timout and build a custom ROM myself, based on the latest LineageOS. However, the boot now hangs even before I can enter the encryption PIN when then phone says "Loading Apps".

[MENTION=5573353]VitaTaf[/MENTION], do you have any idea why the boot hangs there? ADB logcat cannot connect at this point of the boot process, so I don't have any log output.

Could you point me which sources you're using to build your images?

Otherwise, could you maybe integrate the following patch into your next build? It increases the timeout for Cryptfs timeout from 50s to 250s:

project system/vold/
diff --git a/cryptfs.c b/cryptfs.c
index e0cc45f..0f9cf43 100644
--- a/cryptfs.c
+++ b/cryptfs.c
@@ -1778,7 +1778,7 @@ int wait_and_unmount(const char *mountpoint, bool kill)
return rc;
}

-#define DATA_PREP_TIMEOUT 1000
+#define DATA_PREP_TIMEOUT 5000
static int prep_data_fs(void)
{
int i;

Thank you!
[Moto X Android Development] VitaTaf:
Are you on the latest version of LineageOS (20170203) for ghost? They are built directly from Lineage source with no modifications. However, I could include your patch in the next build.

Could you flash this kernel in fastboot mode? I temporarily disabled SELinux (which may be causing the errors) and included a security fix. Let me know if you were able to decrypt your /data partition.
[Moto X Android Development] 7bob:
Thank you for your quick reply!

I repo synced the head of LineageOS-13 Branch, also for ghost.

I flashed your boot.img, but I'm still getting the "Cryptfs : post_fs_data timed out!" error. The system doesn't come up :crying:
[Moto X Android Development] VitaTaf:
Unfortunately, I am not sure what exactly is causing the problem. I will upload a new build with your patch within a week.
[Moto X Android Development] sharukins:
This doesn't sound like the timeout itself is the problem, but some access to the filesystem. 50s for operations on partitions should be more than enough..
[Moto X Android Development] 7bob:
So what would you suggest to get around this?
[Moto X Android Development] sharukins:
I'm not a developer and my knowledge of filesystems is rather small. Basically I have no idea what exactly causes this. I'm doing a build with a 250s timeout right now.

By the way, for me your code change looks wrong. The actual timeout is defined within the DATA_PREP_TIMEOUT 1000 function via:

usleep(5000)
[Moto X Android Development] 7bob:
Actually, it says

usleep(50000)

usleep() takes microseconds as an argument, that makes 0.05 seconds for the given argument of 50000. The loop goes around for a 1000 times in the original code, that makes 50 seconds in total. I extended the loop to 5000 times, which makes it wait for 250s.

What is wrong in your opinion?
[Moto X Android Development] sharukins:
I would personally extend the usleep by 5 times rather than calling the makro more often. But as I already said, I'm not a developer, especially not C and Java. Therefore I might be completely wrong.
[Moto X Android Development] sharukins:
you might want to try this build:

https://drive.google.com/open?id=0B1h5SCBkn-hVNTg4ZlVVeXBIaUE
[Moto X Android Development] 7bob:
Thank you so much, that image succeeded in decrypting (after around two minutes, so the timout was the problem indeed) and boots fine :)

I still wonder why the image I built myself doesn't boot. I strictly followed the steps in the LineageOS documentation, but it still hangs as described. Could you point me to the Repositories and Branches you used to get the sources? And where did you extract the proprietary blobs from (using ./extract-files.sh)?
[Moto X Android Development] sharukins:
Nice, you're welcome. I still wonder why it takes so long to decrypt...

It's a very hacky solution to change the timeout.

What happens if you flash back to a build without the timeout set higher?

For building I just synced the LineageOS repo from github using the cm-13.0 branch.

The extract-files.sh gave me some errors, I had to switch off confirmation of ADB actions in the developer options.

the rest is basically just upstream LOS, besides of two changes in bluetooth configuration which I wanted to test. (Or basically search someone to test, because I don't have any bluetooth devices where the known bug occurs.)
[Moto X Android Development] 7bob:
Well, that problem existed for some time with other CyanogenMod images, so maybe the Moto X is too slow for the encryption of newer Android releases?

So you extracted the files from a Moto X? Which ROM did it have running?

What exactly did you want to test on the ROM? Maybe I can help.
[Moto X Android Development] sharukins:
One of the LOS devs said that encryption was working on the Moto X at least for CM-12.1

Maybe the timeout has changed in later releases..

I used my Moto X with the last official CM-13.0 installed.

There was this bluetooth bug when using audio devices over bluetooth and getting calls. I don't remember the exact scenario and need to look it up in the CM-13.0 thread.

Edit: okay the bug is when connected to a bluetooth audio device receiving a call will result in a complete freeze of the phone, maybe someone can test if this happens with the build I uploaded as well.
[Moto X Android Development] zeroena:
I am being unable to call or answer calls in this ROM (latest 13.0-20170203). Cause immediate reboot. Could this be a general issue or it is just mine?

Best regards.
[Moto X Android Development] Ishaan Gupta:
Have you set any dialer app as default? Do so. If you have flashed any opengapps package with Google dialer, it needs to get set as default app as the zip removes the AOSP dialer.
[Moto X Android Development] zeroena:
Thank you, that did the trick! I didn't think permission settings was giving such kind of trouble!

Best regards!
[Moto X Android Development] krishn:
Hey,

Can anyone provide me with SuperSu that is working. Seems like I'm running into a bootloop.
[Moto X Android Development] goodorbadash:
This is amazing.
[Moto X Android Development] rydebaas:
using last build 03/02 and tried flashed SuperSu 2.79, everything is work very well in here
[Moto X Android Development] mringis:
Hello [MENTION=5573353]VitaTaf[/MENTION]

I found kernel in AHF from 07/02?

It is kernel update?

Whats the different with kernel in 03/02?
[Moto X Android Development] sharukins:
Just so everyone knows: ghost has just been added to the official LineageOS 13.0 Weeklies roster. Thanks [MENTION=5573353]VitaTaf[/MENTION]
[Moto X Android Development] thewraith420:
Will the official builds be posted here or a new thread?
[Moto X Android Development] riyosakura:
but im not seeing it yet on los download page.

only moto g 2013, moto x 2014 and up. but no moto x 2013. :(

or maybe it will need sometime before it officially release on los download page.

Thanks btw.
[Moto X Android Development] sharukins:
there are no official 13.0 builds at all at the moment. they will arrive at a later stage
[Moto X Android Development] shrayek10:
Hey guys, I have a problem and was looking for some help.

I clean flashed this rom with Opengapps nano and phh's superuser.zip. After it boot up, it got stuck on the setup wizard (LineageOS logo with options for emergency call and next). The touch was not working, though the hw buttons responded, upon touching the screen nothing happened. As of now I have restored my backup, but could anyone guide me on what went wrong?

Thanks
[Moto X Android Development] omxx:
;)Well,I was crying at the closed CM
[Moto X Android Development] BR/user:
GPS

Greetings, sirs.

I would like to know how to solve the GPS bug.
[Moto X Android Development] abacate123:
[MENTION=5573353]VitaTaf[/MENTION]

Ghost has been added to the official lineageOS 13 (MM) download (will be published once the build is finished obviously)

http://lineageos.org/Last-Week-in-LineageOS/
[Moto X Android Development] renanbs:
Is bluetooth working fine for receiving/making calls? And 4G/LTE?

Thanks
[Moto X Android Development] VitaTaf:
That is a debugging kernel with SELinux disabled.

Enter these commands in fastboot mode:

fastboot erase modemst1
fastboot erase modemst2

Indeed, thanks to [MENTION=4136182]sharukins[/MENTION]'s suggestion.
[Moto X Android Development] krishn:
Do you think we might have it this week?
[Moto X Android Development] sharukins:
depends solely on when 13.0 builds are triggered by the team.
[Moto X Android Development] Palauro:
battery

hi people, i seen in the post before that some bugs are old, i dont know if my are (new on xda and stuffs about ROMs). the last update rom installed of lineage and i have 2 problems about battery, the charging and the 95%. the charging is the low entrance of mah, starts with 1000 mah (ok for me) and after 20 minutes begins to decay until the level of kind of 200 mah. i flashed again lineage and nothing, install the hybrid kernel and i thing it's the same situation, i look on google but no good search. Took about 3h or more to 100%. the other issue is when i disconnect and the status of battery drop really fast to 95%, i already made the battery calibration, manual mode and with app but not happens. If anyone has a solution, appreciate. (by the way when the status Comes close to 30~25% drop fast until 10~5%)

thanks with the excellent marshmallow on moto x 2013
[Moto X Android Development] jf.navica:
Currently on 20170203, when receiving a call while using bluetooth headset, the phone keeps vibrating but it is impossible to answer the call. It'll keep vibrating until you turn off bluetooth, then it'll show the option to answer the call.
[Moto X Android Development] CsR0501:
Common issue... Search and read bro'!

Enviado desde mi Moto X mediante Tapatalk
[Moto X Android Development] Jhoanchb:
Tycoo kernel

It is recommended to use the tycoo kernel with this ROM?

I mean there's a big difference between that and the stock (LOS) one?

Can someone please share his experience with the tycoo kernel?
[Moto X Android Development] jf.navica:
Yeah, I've seen others have had similar issues but I don't see a fix. If you do know about a fix, posting hints about it would have been more useful than to tell me to search and read.
[Moto X Android Development] abacate123:
There's no fix
[Moto X Android Development] WOrld1:
The news about official LOS support is good, just hoping we have the same support for 14.1 version (7.1.1 as now) in future.
[Moto X Android Development] jb789:
I have not yet upgraded to MM and probably won't have time to anytime soon, but here's some info that might serve as a bluetooth workaround:

https://xdaforums.com/showpost.php?p=68731402&postcount=1754

https://xdaforums.com/showpost.php?p=67019813&postcount=2350

So, based on my limited understanding, a possible workaround is to re-route media audio to the headset profile. I guess you'd lose stereo & probably a bit of audio quality, but if the workaround is viable, at least you'd be able to enjoy both media & calls. There's probably many other combinations of apps that would function the same as the two mentioned in the above links. Here's some that might be worth a try:

A2DP Volume- I'd try this for the automation part since it can also read texts & notifications, and is still being developed. There's currently a newer version on F-Droid.

Dynamic Media BT Mono Router- This one might do it all in one app, but could probably also work in conjunction with the A2DP Volume app. Also recently updated.

Let us know if this works! :)
[Moto X Android Development] jf.navica:
Thanks a lot, this explained the problem. Haven't tested the apps since I didn't want to lose music quality. Disabling phone audio in bluetooth pairing worked for me.
[Moto X Android Development] jb789:
So what happens if you get a call in that configuration? Does the phone just behave normally, ignoring the active bluetooth connection & any attached BT device, allowing you to answer & converse on the phone itself?
[Moto X Android Development] jf.navica:
Phone behaves normally, bluetooth music stops (at least with Spotify) and you can answer the call on the phone. Music starts when the call ends.
[Moto X Android Development] jb789:
Good to know, thanks for the report.

More & more places near me are banning anything but hands-free BT calls while driving, so I'd probably opt for the media-audio-redirect-to-headset hack. That is, presuming it actually works!
[Moto X Android Development] renanbs:
I've tried the Dynamic Media BT Mono Router and it did not work. The Phone app just stops working... :(

I will try the other methods.

PS.: This Bluetooth problem is a kernel issue or a profile issue? I would like to help fix this.
[Moto X Android Development] jb789:
Did you try both the dynamic & static redirection options in the Dynamic Media BT Mono Router app? The dev goes into more detail on his github page.

Unfortunately, I'm not smart enough to answer your second question. [MENTION=4136182]sharukins[/MENTION] made a build to test BT fixes:

I'd say give it a try & maybe together you two can find the fundamental BT issue. :)
[Moto X Android Development] sharukins:
Would be nice if you try, if it works I would send the change upstream. But I'm not a developer, so I'm not able to really debug BT if it's an actual bug. I just tried a different BT configuration for the build I posted
[Moto X Android Development] renanbs:
I will try your build in the morning... I can test it only in my car...

I'm downloading it now... :)

What exactly have you changed? can you post here the git diff?

Thanks
[Moto X Android Development] renanbs:
Just tried. Don't know if playing music was working before, I haven't tested. But today I could listen to Spotify on my car. :)

About calling, the phone app stopped working and when I tried to close it the phone restarted. I tested it twice.

Is there any log I can get to help track what happened?

Renan
[Moto X Android Development] sharukins:
I just took the BT configuration from huashan, but that doesn't seem to change anything, therefore we will need a real dev to fix the issue. Sorry but this is beyond my capabilities.
[Moto X Android Development] kathsfernan:
Any help? I tried flashing ROM again and i cant get root permission
[Moto X Android Development] riyosakura:
Hei there.

I want to know, is there a built in root on the latest los 13?

Im using 20170119 version and i lost built in root which is available on the previous rom i used, official cm 13.

Or is there any way to get root. I read somewhere on the thread that we need to flash Supersu for the root. Does it work? I need someone to confirmed it.
[Moto X Android Development] mringis:
Flash SuperSu work for me. I use 20170119 build
[Moto X Android Development] kathsfernan:
Which Supersu version?? I flashed the latest and get stuck in Lineage screen. Same wiping dalvik cache/cache
[Moto X Android Development] jb789:
Just out of curiosity, why huashan? Does it share any hardware/chips with our ghost, or does that even matter? Seriously, I have no clue, just looking to learn. ;)
[Moto X Android Development] muham47:
what are the current bugs?
[Moto X Android Development] renanbs:
Does anyone knows what is the bluetooth proc in the xt1058? I will take a look at the kernel :), no promisses
[Moto X Android Development] jb789:
This Moto X teardown says it's a Qualcomm WCN3680 combo Wi-Fi/Bluetooth/FM chip. It also mentions some EPCOS 7959 Wireless LAN/Bluetooth Filters, but I don't think that's relevant. Presumably, this stuff is the same across all Moto X models. Hope this helps!
[Moto X Android Development] mringis:
2.79 SR3 (build 20170114 i think). No need to ckear cache/dalvik

The first boot after flashing SuperSU taking a while as i remember
[Moto X Android Development] gowtham3834:
simply cm13 bugs are still there rest,see it in description
[Moto X Android Development] renanbs:
Thanks
[Moto X Android Development] dieKatze88:
I read the entire thread and thanks for the GPS fix, that's awesome to have everything up and running again.

Just a few minor things.

Is there a fix for Bluetooth being off at boot? Mine is always off at boot.

Is there a way to permanently change the USB Connection type to MTP? I only plug my phone into stuff I trust anyway so I'm not worried about it getting owned by some rogue box.
[Moto X Android Development] Faisi904:
Official build is out guys.
[Moto X Android Development] senseii:
Get it while it's hot :good:

https://download.lineageos.org/ghost
[Moto X Android Development] gowtham3834:
what are the bugs and the features included in this build
[Moto X Android Development] abacate123:
LineageOS = CyanogenMod with some other details, so, don't expect much different.
[Moto X Android Development] jb789:
From the OP: https://www.cmxlog.com/13/ghost/

or here: https://download.lineageos.org/ghost/changes/1487904129/

Lots of stuff over my head & several security patches/fixes.
[Moto X Android Development] abacate123:
[MENTION=5573353]VitaTaf[/MENTION] it's official now, you can rename/update the thread if possible (when possible) :)
[Moto X Android Development] Rahh1112:
Just a reminder

OFFICIAL LINEAGE OS 13 ISN'T COMPATIBLE WITH THE UNNOFFICIAL ONE, YOU NEED TO BACKUP YOUR DATA AND CLEAN FLASH!
[Moto X Android Development] Couchy:
Ugh, rootless...

The official build doesn't include su (apparently you're supposed to flash it separately now) but the extras page only has versions for 14.1, which doesn't work.
[OnePlus 3T Questions & Answers] flammenwurfer:
I guess I wasn't paying close enough attention and I tried installing the 7.0 update from this thread.

I can now only get to TWRP recovery and fastboot. When I'm in TWRP my internal storage says 0MB and it won't let me mount the data partition. Flashing anything fails.
[OnePlus 3T Questions & Answers] viper2097:
Fastboot format userdata
[OnePlus 3T Questions & Answers] neinfricatu:
Flash the stock recovery through fastboot. You can use the toolkit found here on xda forums.
[OnePlus 3T Questions & Answers] Eremitus:
Also you can format data in TWRP and then it should work, but you lose everything in internal storage, pics, music, all your own stuff.
[OnePlus 3T Questions & Answers] flammenwurfer:
Thanks guys. I got the stock recovery installed and it wiped everything, which was fine. I already backed up important stuff. It seems the update went through because I have Nougat now. But I'm having trouble installing any other roms. It wants to decrypt but it doesn't work. I read on the TWRP post that you can set a boot password and it would update the crypto key type or something and it should work after that. Well I did that, but twrp still won't accept my password and let me flash anything.
[OnePlus 3T Questions & Answers] kinfam:
I had the same problem. I used the 3T toolkit to force decrypt (Option 14). This worked for me.
[OnePlus 3T Questions & Answers] Nobody121:
I just did this and it worked in TWRP: I was able to create a backup (which is not possbible in password-bugged state) and then I noticed I still was not able to mount the USB partition and thought I had to boot in to OOS once, so I did it, set up the bare minimum and then checked back at TWRP and voilà: Locked again.

The OOS said "encrypted" as well after I booted it.

I was (am) running 7.0, TWRP, non rooted (because I freaking can't)

Anynone can help here?
[OnePlus 3T Questions & Answers] kinfam:
Did you flash SuperSU before booting into OOS? Not sure what to tell you :( I did the Force Decrypt then went into TWRP and immediately flashed SuperSU.
[OnePlus 3T Questions & Answers] Nobody121:
I wanted to do so but was not able to because I was not able to mount the relevant partition, nvm though I think I`ll wait a day or two to see if TW releases a new build. Thanks anyways:good:
[OnePlus 3T Questions & Answers] cultofluna:
,Using the toolkit take the option 14....To push decryption..,

DONT boot to your ROM...With the toolkit push the SuperSU and then flash it...

Now you can boot to your ROM....

If you boot without SuperSU will reenforse encryption.....