yashsingh1/xdaforums huggingface dataset:
[Moto X Android Development] hawkdown77:
Did you see the logs that i posted??
[Moto X Android Development] TeamMex:
YES

D/Error ( 818): ERR: exClass=android.os.StrictMode$StrictModeDiskReadViolation
D/Error ( 818): ERR: exMsg=policy=391 violation=2
D/Error ( 818): ERR: file=StrictMode.java
D/Error ( 818): ERR: class=android.os.StrictMode$AndroidBlockGuardPolicy
D/Error ( 818): ERR: method=onReadFromDisk line=1137
D/Error ( 818): ERR: stack=android.os.StrictMode$StrictModeDiskReadViolation: policy=391 violation=2
D/Error ( 818):	at android.os.StrictMode$AndroidBlockGuardPolicy.onReadFromDisk(StrictMode.java:1137)
D/Error ( 818):	at libcore.io.BlockGuardOs.stat(BlockGuardOs.java:292)
D/Error ( 818):	at java.io.File.lastModified(File.java:571)
D/Error ( 818):	at com.chelpus.XSupport.loadPrefs(XSupport.java:1220)
D/Error ( 818):	at com.chelpus.XSupport$14.beforeHookedMethod(XSupport.java:427)
D/Error ( 818):	at de.robv.android.xposed.XposedBridge.handleHookedMethod(XposedBridge.java:655)
D/Error ( 818):	at com.android.server.pm.PackageManagerService.queryIntentServices(<Xposed>)
D/Error ( 818):	at android.app.ApplicationPackageManager.queryIntentServicesAsUser(ApplicationPackageManager.java:645)
D/Error ( 818):	at com.android.server.accessibility.AccessibilityManagerService.readInstalledAccessibilityServiceLocked(AccessibilityManagerService.java:945)
D/Error ( 818):	at com.android.server.accessibility.AccessibilityManagerService.readConfigurationForUserStateLocked(AccessibilityManagerService.java:1441)

D/Error ( 818): ERR: exClass=android.os.StrictMode$StrictModeDiskWriteViolation
D/Error ( 818): ERR: exMsg=policy=391 violation=1

Xposed make many incompatibilities

The problems caused by Xposed not concern me, sorry

cheers
[Moto X Android Development] henrique.zanforlin:
I have a Ípega 9028 controller and i tested many ROMS, even in Stock Motorola ROM, the bluetooth loses connection all the time, but in your XPerience ROM xpe_9.1.1_r33-20160131-NIGHTLY, the bug is gone, fixed, however i updated to 20160204 and the bug is back.. Your ROM was the only one who could fix the problem.

I tested in many devices and the bug is only in moto x 2013, when connected, the wifi and bluetooth connection loses all the time, it's impossible to use the Ípega Controller ... :crying::(

(Sorry, I'm used the Google Translator to help me)
[Moto X Android Development] hawkdown77:
You are talking about the painel volume bug? Cause before i was using mokee ROM and i had no such error
[Moto X Android Development] NiEb:
i lost my original mac adress :(

[53.096261,0] wlan: Invalid MAC addresses in NV, autogenerated 00:0a:f5:b2:50:38
<36>
[Moto X Android Development] tycoo:
I am using xposed too + some modules to customize the rom some more. And i dont have this prob. Most likely you messed up something on your own.

I dont understand what you are talking about exactly. Regarding to this commit your phones mac address should always be the same

https://github.com/tycoo/moto_x_kernel/commit/66a8d45aefb80b6ba20818ed40084381ed220b9c

---------- Post added at 09:30 PM ---------- Previous post was at 08:44 PM ----------

[MENTION=4403780]TeamMex[/MENTION]

The roms is running very well at all. There are only some minor probs or suggestions left i like to tell:

- the Xperience Kernel Tweaker force closes when selecting "minimum available memory" (I dont know the exact description in english).

- a switch to disable the root hash in the notification bar would be great. Since i am using afwall+ with root permission the hash is always visible.

- an option to setup the duration appearance of the lockscreen when receiving messages or just looking for the time would be great too.

- i have seen you merged the PiecControl3.0 into Xperience 10 already. Would be very nice if you could implement it into Xperience 9 too, until we have a working marshmallow port for our phone (hopefully there will be one someday). The moto x amoled display suffers from "Burn-In" over time. To prevent a visible difference between the default navigation bar, the pie control is the ultimate choice in my opinion. Atm i applied it via GravityBox, but this one is not as configurable as the Pie 3.0.

- there would be some more on my "wishlist" but thats enugh for now. ;) Thx for you work!

regards
[Moto X Android Development] henrique.zanforlin:
Bugreport to the bluetooth problem. Even in Stock 5.1 it happens :( any help? :crying:
[Moto X Android Development] Megatron007:
bluetooth can u be more specific ...is it bluetooth audio ?
[Moto X Android Development] henrique.zanforlin:
I Explained detailed in the post # 61, the bug it happens using an Ípega 9028 Controller.
[Moto X Android Development] hawkdown77:
Can we install cm13 themes in this ROM?
[Moto X Android Development] MiyamuraNEET:
Copilacion for xperia M dual please!
[Moto X Android Development] tycoo:
wow, three times fail. 1. quoting the op 2. demanding a rom 3. wrong device forum :rolleyes:
[Moto X Android Development] rafatosta:
Update for android MM?

The XPerience will be updated to version 10?

There is already a summer of CM 13 for the ghost and soon rom RR already have a version with MM.

http://xdaforums.com/moto-x/development/rom-cyanogenmod-13-moto-x-t3313427
[Moto X Android Development] TeamMex:
I have a unstable version of XPerience 10 since some day's a go

Until it is something stable, I will release the first version,

some screens of XPE 10

https://plus.google.com/u/0/+klozzjesus/posts/6wyP7CjnHrk

cheers.
[Moto X Android Development] hawkdown77:
when we silenced the device and open any app to update the status of the phone increases the volume alone.
[Moto X Android Development] NiEb:
it continues here ? :)
[Moto X Android Development] UrielGT-X:
¿Habrá una nueva actualización?

Ningun bug en esta ROM!

La mejor!

Otra cosa:

¿Recomiendas instalar el kernel de tycoo para CM12.1?
[Moto X Android Development] TeamMex:
I never tested my rom with tycoo kernel I hope it works

Nunca he usado mi rom con ese kernel espero que funcione no se si trae su propia ramdisk

saludos

I will update this version soon, for now i working on Marshmallow
[Moto X Android Development] UrielGT-X:
Waiting for the last stable build of LP...

:(

I think MM still is not for daily use...
[Moto X Android Development] lavero.burgos:
Did you install latest build posted in OP? Is it stable? Were you able to install tycoo kernel?.

I've been using stock but I'm getting tired of it mostly because i cant use xposed + gravity box, it gets unstable.

Looking for a stable custom ROM without bugs with decent features and battery friendly. Only reason of using stock is because data speed seemed faster.

Sent from my Moto XT1053 powered by Tapatalk
[Moto X Android Development] Ignaciodnb:
Waiting for a new build :P
[Moto X Android Development] lavero.burgos:
Yeah would be nice to have a stable build of this ROM.

I really don't get the rush for MM I rather have a fully functional phone but properly optimized to the best devs can to get the best out of this phone.

Enviado desde mi Moto X mediante Tapatalk
[Moto X Android Development] TeamMex:
Maybe tomorrow (if I have some free time) update the source to 5.1.1_r35

cheers.
[Moto X Android Development] pankaj.jajoria:
I'm unable to flash with twrp..

I already edit the updater script bt it still shows updater script error... Wat to do guys ?
[Moto X Android Development] lavero.burgos:
What TWRP version?

Do the wipes , when done reboot to recovery and immediately flash the rom

Enviado desde mi Moto X mediante Tapatalk
[Moto X Android Development] lavero.burgos:
So i just installed this ROM with The method above with TWRP 2.8.7.0 Official and it worked.

Question for [MENTION=4403780]TeamMex[/MENTION] , i installed as per OP instructions to The letter but when i started flashing The ROM TWRP showed patching system and then file system went back to ext4 from f2fs. I wanted to try this ROM exactly for that feature to test if indeed The phones performance increased as sometimes phone will lag no matter what ROM or what kernel, and as this is The only ROM i found that mentioned Support of f2fs file system for both system and cache i decided to give it a try.

T.I.A
[Moto X Android Development] TeamMex:
This don't support F2FS System only cache and data.

Android source can't build a F2FS image I tried

cheers
[Moto X Android Development] hawkdown77:
Cast chromecast doesnt work
[Moto X Android Development] UrielGT-X:
Alguna actualización?

is there a update?
[Moto X Android Development] TeamMex:
I updating source maybe in the night I upload new build

cheers.
[Moto X Android Development] UrielGT-X:
Nada aun? :rolleyes:
[Moto X Android Development] riyosakura:
Does this rom have theme manager?
[Moto X Android Development] wizardknight:
It is listed as a feature in the op.
[Moto X Android Development] TeamMex:
esp:

No viejo enferme de dengue y estuve encamado xD mañana termino de actualizar el source y fixear los problemas que genere el nuevo merge

eng:

No brother, sick with dengue and was bedridden xD

Tomorrow I finish updating the source code and repair the problems generated by the new merge

cheers.
[Moto X Android Development] UrielGT-X:
¡Oh! ¡Que mal!. Pase por lo mismo. :(

Ok, a esperar entonces. :highfive:
[Moto X Android Development] TeamMex:
ROM UPDATED :)

changelog in scond post
[Moto X Android Development] UrielGT-X:
Instale la ROM pero al momento de instalar las gapps aparecio un problema... (imagen abajo) No si si sea problema de las gapps o de la rom...

Despues reinicie y al momento de ingresar alguna red wifi el sistema se reiniciaba, paso unas 3 veces, despues de eso inicio normal.

Fuera de esos problemas todo bien! Excelente trabajo. Gracias!

Por cierto uso la ultima version de twrp.
[Moto X Android Development] CsR0501:
This ROM is Lollipop (5.1.1) source and you flash MM gapps (6.0.1)... [emoji29]

Enviado desde mi Moto X mediante Tapatalk
[Moto X Android Development] UrielGT-X:
No, I downloaded the correct package (open_gapps-arm-5.1-mini-20160512)

It seems that the OS is 6.0.1 :eek:

I'll try again with the new version of 20160513
[Moto X Android Development] TeamMex:
dham lol xD I tested it 2 days and I never had problems D: download the last 5.1.1 Gapps from opengapps

if still continue the wifi bug send a logcat :)

take bug report from xperience center (OTA)

cheers
[Moto X Android Development] UrielGT-X:
Los mismo otra vez... volvi a descargar la rom y las gapps y los mismo errores solo que ahora ya no me deja pasar de la pantalla de conexiones wifi, se reinicia una y otra vez. :(
[Moto X Android Development] TeamMex:
weird wipe data and cache format system then flash the rom
[Moto X Android Development] UrielGT-X:
INFO:

Gapps: open_gapps-arm-5.1-mini-20160513.zip (mini)

ROM: xpe_9.1.1_r37-20160511-NIGHTLY-ghost.zip

TWRP: TWPR-3.0.2-0-GHOST-FIXED-NIGHTLY-UNOFFICIAL.img

format system and format cache with F2FS

Now my phone is in hard brick, I couldn't do anything. I tried reinstalling the firmware but system cannot be installed.

Creo que lo llevare a garantia. :/
[Moto X Android Development] TeamMex:
solo entra al recovery copia todo y haz un fastboot erase userdata luego reformatea la cache a ext4
[Moto X Android Development] NiEb:
thx, this rom is great.

Bluetooth calling works... :) fine
[Moto X Android Development] UrielGT-X:
Creo que solucione por mi cuenta mi hard brick.

Soy yo o hay un problema en reproducir musica mediante chromecast? He probado con vario reproductores pero no funcionan, con youtube y los navegadores si, pero con los reproductores de musica no.

Gracias....!

It's me or chromecast didn't works?

I connected mi moto x for listen music but didn't works with others sound yeah but with the music players no.

Trate de traducir xD
[Moto X Android Development] TeamMex:
con eso no te puedo ayudar no tengo chromecast sorry

With that I can't help you, I haven't chromecast sorry

cheers-
[Moto X Android Development] UrielGT-X:
Hello!.

I have a problem. Why the system partition changes from f2fs to ext4 automatically?

Before I change system to f2fs and after flashing the ROM again changed to ext4.

It's normal? It's me or the ROM?

He probado otras ROMs pero esta es la mejor :)
[Moto X Android Development] CreasingMass Dev:
/system is meant to be ext4 always as it's read-only most of the time, so there's no reason to format it to f2fs.

Also all rom's updater-script automatically format /system to ext4 before actually flashing the rom.
[Moto X Android Development] UrielGT-X:
Oh ok.! Thanks! :good:
[Moto X Android Development] TeamMex:
Android is not ready to build the system image in f2fs

cheers
[Moto X Android Development] SevenFactors:
[MENTION=4403780]TeamMex[/MENTION] Is there a reputable place where one can download 9.1.1_r37-20160707-ghost-FINAL? All download link are broken.

Also, why will there be no more updates? New project?

Thanks
[Moto X Android Development] TeamMex:
For now not more updates, I working on nougat.

I will compile the rom again and I'll upload to another host, for now basketbuild is out of service.

cheers.
[Moto X Android Development] SevenFactors:
Out of service & just when I found out about Xperience. Mi suerte lol

Gracias por responder :)
[Moto X Android Development] natsousa:
Anywhere I can find a download link for this ROM?
[Moto X Android Development] TeamMex:
ouh, idk why this was removed from basketbuild :S
[Moto X Android Development] natsousa:
If you could find some way of sharing it with me I would be grateful.

Also, the Verizon Developer Edition is usually cheaper on ebay and it has an unlocked bootloader. I don't know if that would work.

I just love the small size of the phone. I can't understand how people use these big phones as the don't fit well in my hand or pocket. As long as mine lasts, I will keep using it, especially with great ROMS like yours
[Moto X Android Development] natsousa:
Can I ask again for you to re-upload this ROM?
[Moto X Android Development] revampmybrain:
I second this, could you please reupload the final to another site? My S8 bricked recently and I'm using my moto as the backup, wanted to use this rom specifically [MENTION=4403780]TeamMex[/MENTION]
[Galaxy Note 4 Q&A, Help & Troubleshooting] jonitfcfan:
Hi,

My N910F has recently been acting weirdly. It either randomly reboots itself, or just freezes for several seconds when switching screens or scrolling/tapping buttons. This started a couple of weeks ago on stock 5.0.1 (this version, I think) running Emotion kernel. This was running fine for a while; I didn't flash any new mods during this time, although I did switch between AEL kernel and Emotion once or twice without much success.

Thinking it was just one of those situations that called for a clean slate; I backed up my important stuff, booted into TWRP to wipe all partitions, then flashed stock 5.1.1 via Odin (this version, which I'm currently running). But even before I rooted it once again the phone was displaying the same aforementioned symptoms, both during and after going through the built-in setup wizard. This behaviour continued after flashing TWRP and AEL kernel v8.2, which I'm currently on at the moment. If it makes any difference I've also noticed that the lower my battery level, the more often it reboots itself. The battery level also "yo-yos" sometimes, usually at lower levels.

I've uploaded the relevant logs as advised elsewhere for anyone who can decipher them, as I otherwise don't know what to look for. This includes my last three kmsg dumpstate logs (just in case it's a slightly different cause each time), as well as my logcat and dmesg files (whatever they are lol) which I got using the SysLog app.

Any help would be appreciated, and if you need any more info please let me know.

Thanks :).
[Galaxy Note 4 Q&A, Help & Troubleshooting] jonitfcfan:
*bump*
[Galaxy Note 4 Q&A, Help & Troubleshooting] acnoai:
I have the same problem. Help would be highly appreciated. : )
[Galaxy Note 4 Q&A, Help & Troubleshooting] jonitfcfan:
*bump*

[UPDATE]: Once or twice when it's crashed as above, it would try and boot again but then reboot into download mode with the following text at the top of the screen above all the other info:

Could not do normal boot.
ddi: mmc_read failed

If I then pull the battery and turn it on again, it boots up as normal (at least until the next crash). Is this something that can be fixed with a fresh flash in Odin (or some other method), or is my phone on the way to its death?
[Galaxy Note 4 Q&A, Help & Troubleshooting] mikkelrev69:
Got the same issue + loses Wifi password after random reboot. Sent the phone back to the operator I bought it from 1 week ago and they did a repair. They replaced the USB-flex, did a firmware upgrade(?? ..was already updated to latest) and sent it back. I got it this morning and at first the phone now works fine and no more "mmc_read fail". But after some time the random reboots started again. Not so often now but still 4 times over the day and twice the wifi-password is lost and I had to retype it. Now I'm on the fence and just waiting for the first mmc_read fail" to happen before I complain and send it back for a second repair. I can not imagine this beeing beeing other than a hardware fail coming from a weak spot on the phone. I got the impression many people has the same issue and it really comes to life after upgrading to 5.1.1.

I also think the problem at the service shop ist that they just do a quick system test on a clean wiped phone and can't find the issue and think the phone is fine. After reinstalling my 200 apps and setting up my phone all over again, the workload causes the issue to reappear and I now have to ask the service shop for a deeper check. They accepted this as a warranty fix all though my phone has a knox trip (0-1)x4...
[Galaxy Note 4 Q&A, Help & Troubleshooting] l3o4nn:
I've also faced random reboots on Lollipop. How i solved that? Simple. I downgraded to Kitkat. Lollipop still having lots of battery drains and bugs even on 5.1.1
[Galaxy Note 4 Q&A, Help & Troubleshooting] jonitfcfan:
[UPDATE]

I've decided to go through my network provider to get a replacement sent out to me, which they were happy to do after going through their line of questioning over the phone ("have you tried turning it off and on again", "did you try taking out your memory card and see if that helped", "did you try doing a factory reset", etc). They say it will get here tomorrow so fingers crossed for the replacement. :)
[Galaxy Note 4 Q&A, Help & Troubleshooting] mikkelrev69:
The ddi mmc_read fail has not reappeared yet..

It's strange.. Lately the random reboots are not wiping my wifi passwords anymore, but now after every random reboot the multiwindow is enabled and I've got to untick it in quick settings..

Latest: It seems that the random reboot may come from heavy account sync workload. I did have 5 Google accounts syncing on my phone + 6 excange accounts and when i disabled syncing alltogether the phone ran a lot smoother and the reboots stoped. So i deleted all Google accounts except my main account and for now thing seems to be fairly stable. I've also uninstalled all for me unimportant 3'rd party apps, reducing 3'rd party app count from aprx 200 to 150..

If things develop further I'll come back with more

Sent from my ****in' phone!
[Galaxy Note 4 Q&A, Help & Troubleshooting] j_svas:
Thanks fot starting this thread Jointfcfan...i am using 910P and have same issue of your post 1 and 4!!!!

Loosing hope on Samsung, it is really frustrating...

Tried cleaning cash, dalvic, reboots, on latest 5.1.1 k version...frozen all not neede games and apps ...only 1 google and 1 exchange account no auto sync

At next stage while rebooting it sometime going an error stating kernel panic and i have to pull battery to restart
[Galaxy Note 4 Q&A, Help & Troubleshooting] mikkelrev69:
Replacing USB-flex board at service shop has cured the "ddi. mmc_read fail" boot issue for good.

So to me it seems that when many people experiences this, the USB-flex board may have a built in design flaw making it a weak spot on the Note 4.

Also I found that the phone works A LOT smoother if using Nova launcher instead of TW. Random reboot count is way down and phone works almost normally. Still some lag, mostly when unlocking screen, but reboots happens only 2-3 times a day now. Still random rebooting enables "multi window" option every time..

I've also rooted the phone now using CF-autoroot. I've flashed Philz CWM recovery and using it to install Wanam Xposed. So now I can run Greenify properly in Xposed mode and automaticly hibernate apps including system apps..

NB! Be aware, flashing root and custom recovery trips Knox counter 0x1 permanently and MAY void warranty

I have also mailed my operator asking them to take in the phone a second time for check/repair, alt. replacing the phone. I guess when they did system check 1st. time without issues after replacing the USB-flex, it was done when phone was reset to factory and under no significant workload.

Sent from my ****in' phone!
[P3300, MDA Compact III ROM Development] NikMel:
Hello all,

I just extracted this P800w_SEA_ENG_WM6_Upgrade_20070713 ROM and made a clean one.

This one includes:

Radio Version : 02.97.90 (from http://xdaforums.com/showthread.php?t=326639)

Protocol: 4.1.13.46

NOTE: YOU MUST FOLLOW THE STEPS FROM http://xdaforums.com/showthread.php?t=311403#1

Download it here :=> http://rapidshare.com/files/55212551/RUU_Signed.nbh

This one uses HyperCore from here http://xdaforums.com/showthread.php?t=310076

How to flash:

1. Extract the HyperCore

2. Copy RUU_Signed.nbh to %HYPERCORE%\Tools\RUU folder

3. Run BiuldOS from %HYPERCORE%\Panel\Build

4. Go for [4] - Flash
[P3300, MDA Compact III ROM Development] dannyoneill:
Thanks, what version is the OS in the about screenand the other numbers in the system info?

Also, is this newer than the version available to download from HTC asia?

Thanks
[Moto G 2015 General] Aftcomet:
Just got Android 6.0... the "use SD Card as internal Storage" feature seems pointless

This was a highly touted feature. Especially with our Moto G's that have only 8GB of storage. In Lollipop, we could store all of our media (pictures, videos, files), on the SD Card. Some apps also supported being moved to the SD card. Microsoft Groove, for example doesn't support SD card storage at all. Meaning, if you wanted to download any music, everything would be stored on your internal partition. Obviously, Android M seemed very promising because it looked like we could combine out storages to overcome this.

Fast forward to it now. You can set your SD card as internal storage and it will show up as internal storage. HOWEVER, some apps still cannot be moved there (any app that couldn't be moved before, still can't be moved). Microsoft Groove still resides completely on the primary partition. So if I download too many songs, the 8GB eMMC fills up and I get warnings that I'm out of storage and can't receive messages or have other functions....

I don't get it. What is so special about this? My SD card functions exactly the way that it did under Lollipop. My storage still shows up as 8GB + 32GB SD Card, the way it did before. It's not 40GB internal combined the way it was advertised to be.

Very disappointing.
[Moto G 2015 General] EP2008:
From what I can see, it encrypts the card so it can only be used by your device.

It told me during setup that it would automatically move apps, data (saved me 155mb), but I haven't tried to move stuff manually.
[Moto G 2015 General] bobby0724:
Other thing I notice is that lets say you move 1 app to the sd card, when that app gets updated it moves back to internal then you need to go and move it manually , and sometimes it doesn't want to move need to reinstall :(
[Moto G 2015 General] Aftcomet:
Yup! This exact problem existed in Lollipop. I decided to just leave them in internal instead of the hassle of trying to save a few hundred megs all the time.

This feature showed so much promise. For me it was going to be a killer feature. Take an 8GB ROM phone and turn it into a true 40GB ROM phone.