yashsingh1/xdaforums huggingface dataset:
[X 2014 Android Development] JulesJam:
I have surfaceflinger, surfaceflinger_cflumen and surfaceflinger_shell all in /system/bin and libsurfaceflinger.so and libsurfaceflinger_ddmconnection.so in /system/lib. I am running 4.4.4 on my XT1060, not sure if that makes a difference compared to lollipop. Do you want them?

Also, I have not found bootloops to be worrisome. I simply get into bootloader mode and then recovery to wipe cache then back to bootloader mode and reflash using mofo.exe.
[X 2014 Android Development] ClydeDroid:
Alright, shoot me those files then. Giving it a shot can't hurt!
[X 2014 Android Development] mdmogren:
AirAudio works! $20 sent as promised. Thank you!
[X 2014 Android Development] JulesJam:
What do you use AirAudio for?

---------- Post added at 07:41 PM ---------- Previous post was at 07:31 PM ----------

https://mega.co.nz/#!V8dggRhY!_GEYI_U1Fn_hf2USuoZiHt4zvlFzdfBeBcdLGEQP8kk

MD5 = B2BBF7356759A785F9C962870C71DA4F
[X 2014 Android Development] mdmogren:
I use AirAudio to play music through my Airport Express which is output to my mixer then to my studio monitors. I've used an iPad and Macbook prior to this hack, but it's very nice to be able to use my phone now... I'm totally open to other non-apple options, but haven't found anything else that works as well...
[X 2014 Android Development] joshnat:
I've been getting google app crashes on 1.2. If I uninstall updates and clear data it's fine. As soon as I update the google app it crashes. Any ideas?
[X 2014 Android Development] redwings73:
Same issue here, too....although I had the FC's of the Google App Update to 4.6.10.19 before I went with TotalX1.2, so I don't think it's the image. I did find in Android Police and in the XDA Lolistat forum that using the Xposed module Lolistat will FC the 4.6.10.19 update and if you blacklist the app it will work properly, but I had no luck even after I did this....

I've been running 4.5.13.19 without FC's.
[X 2014 Android Development] joshnat:
Brilliant! Thank you! I would never have been able figure this out.

Edit: I was able to keep Lolistat on by blacklisting the Google app and GPE launcher.
[X 2014 Android Development] contesauce:
1.3 installed and running, everything running smooth so far. Installed airaudio, but haven't tested it yet, will test when I get home. Adaway, xposed, bb, all work with no issues. No google app force closes either.
[X 2014 Android Development] drwhitney:
I have a rooted Nexus 7 2012 running Lollipop 5.1.1; I can pull those files from it tonight if the files from JulesJam are problematic since they're 4.4.4. Worst case, I could also flash back to a 5.0 ROM and install CF.lumen there if the 5.1.1 files are also problematic. Thanks for all your work!
[X 2014 Android Development] joshnat:
Any possibility to get 1.3 with the stock lollipop animation? http://xdaforums.com/android/themes/bootanimation-android-l-60fps-v3-t2918168

Also, are we able to suppress the "Mobile Data is Unavailable" popup whenever on a call?

Awesome work, thanks!!
[X 2014 Android Development] redwings73:
I can't get anything above Google App 4.5 to not FC.... I've done all the wiping and Lolistat blacklisting, etc....I even uninstalled Lolistat.

Anyone have a clue what the issue could be?

I'm on TotalX 1.3.

UPDATE: I can only get 4.6.10.19 to work with the swipe right function of the Google Launcher....

SOLVED: I disabled all of my xposed modules and then, one by one, narrowed it down to the "force immersive mode" module....
[X 2014 Android Development] ClydeDroid:
That would be great, please send those files along!

If you'd like, I can make you an image of the next version with any bootanimation you send me. By stock, do you mean the original Moto X one, or the 5.1 animation I had in 1.0?

As far as that popup goes, I changed my preferred network mode to LTE/CDMA instead of global, and that seemed to make it come us less often, even though its still coming up. Still looking into it.

I've gotten my force closes to stop completely. Here's what I did: uninstall updates for Google Play Store, then from Google Play services. Reboot, and then reinstall the updates found here: Play Store and Play Services
[X 2014 Android Development] joshnat:
Thank you! The animation I mean is the GPE Lollipop one and can be found here: http://xdaforums.com/android/themes/bootanimation-android-l-60fps-v3-t2918168

I'l try changing my radio settings and see if that helps with the popup.
[X 2014 Android Development] redwings73:
I've gotten my force closes to stop completely. Here's what I did: uninstall updates for Google Play Store, then from Google Play services. Reboot, and then reinstall the updates found here: Play Store and Play Services[/QUOTE]

I disabled all of my xposed modules and then, one by one, narrowed it down to the "force immersive mode" module....
[X 2014 Android Development] fakieskr8333:
I would love for one with the GPE boot animation (the one with the moving colored dots, like on android wear). The 5.1 moto one was cool for a while but it so bright! Thanks and I look forward to the next version.
[X 2014 Android Development] drwhitney:
These are the same five surfaceflinger files that [MENTION=5983610]JulesJam[/MENTION] posted, from my Nexus 7 2012 running Lollipop 5.1.1.

https://mega.co.nz/#!apN2BIwR!RU1oTIyEWKNOrhO4hNQ7Z3G_j1rM_SHTyCjcPnLFVQo

MD5: dd5ee408762a2a1af22680bfa969236f
[X 2014 Android Development] hotpass105:
Here is the million dollar question, will 5.1.1 be supported when it is released? Also, ClydeDroid, this is excellent work. There isn't much I can do to repay you, but I will mirror your images if you would like.

Montreal Canada

TotalX-1.3.rar

Atlanta mirror also available if you are interested.
[X 2014 Android Development] JulesJam:
I am sure that 5.1 bootloader will not have closed the exploit that mofo uses. However, the images will have to be remade if you want to run rooted 5.1 on the XT1096 and as a starting point we need the 5.1 fxz. Then we would need someone with knowledge and time to mod the 5.1 system.img.

I myself am going to wait to upgrade until Motorola Device Manager can flash the full files b/c when you use MDM to upgrade, it leaves a copy of the fxz on your computer. What is happening with the Brazil XT1097 and PE XT1095 is that the OTA is dropping but MDM is not yet updating devices. So there appears to be a delay b/t when the OTA drops and when the full files are available using MDM.

I have frozen MotorolaOTA so that it won't update me by accident.

Also, we will need redownload mofo.exe b/c AIUI, our version only will flash modified 4.4.4 and 5.0 system images. Somehow maiko1 configures each copy of mofo.exe to work only for the specific device and the specific versions of the OS that have been verified to work so maiko1 will need to do something on his end to free up mofo.exe for use with 5.1 on the XT1096. I would be willing to test again but like I said, first step is to get the 5.1 system.img and the only way I know how to get it is by using MDM to update.

FYI - looks like we are getting an update soon to fix a problem with dialing 911 if your phone is encrypted and you use a PIN. I am not sure if the fixes are in the system or modems/basebands but if they are changes to system.img, then if you want these fixes on your phone, the images would have to be remade. Again, the first step is capturing the fxz using MDM. AIUI, there is not an issue unless you encrypt your phone and use a PIN.

http://www.phonearena.com/news/Spec...-serious-problem-with-emergency-calls_id69001
[X 2014 Android Development] ClydeDroid:
[MENTION=5983610]JulesJam[/MENTION] and [MENTION=3543659]drwhitney[/MENTION] - Can you look at the files you sent me on your devices using root explorer and tell me the permissions, owners and context on each file? I'm actually able to pull the files from my own device using the normal installation method through the app using adb right before it reboots, so I just need to know what to set the files to in the image, and then it should be good to go.
[X 2014 Android Development] JulesJam:
All of the ones in /system/bin have the same properties:

surfaceflinger: rwx r-x r-x, owner root, group shell

surfaceflinger_cflumen: rwx r-x r-x, owner root, group shell

surfaceflinger_shell: rwx r-x r-x, owner root, group shell

And all of the ones in /system/lib have these properties:

libsurfaceflinger.so: rw- r-- r--, owner root, group root

libsurfaceflinger_ddmconnection.so: rw- r-- r--, owner root, group root
[X 2014 Android Development] drwhitney:
system/bin/

surfaceflinger -rwxr-xr-x

surfaceflinger_cflumen -rwxr-xr-x

surfaceflinger_shell -rwxr-xr-x

system/lib/

libsurfaceflinger_ddmconnection.so -rw-r--r--

libsurfaceflinger.so -rw-r--r--

Edit: JulesJam beat me to it. Same owner and group permissions as posted above.
[X 2014 Android Development] ClydeDroid:
Welp, I added the files to the image, flashed, and my phone is stuck on the first boot screen before the bootanimation. So I'm not sure what else to try at this point. If only [MENTION=631273]Chainfire[/MENTION] could help...
[X 2014 Android Development] ClydeDroid:
Is mfastboot a special fastboot specific to Motorola? I am unfamiliar with it. Also, I had looked at the update-binary, but I didn't notice 99-cflumen.sh before. I can try adding that as well.
[X 2014 Android Development] drwhitney:
[MENTION=2821926]ClydeDroid[/MENTION] If you need the 99-cflumen.sh, here it is:

https://mega.co.nz/#!L1VDXbgR!BADzuuWVhF4cF_QZXqa5q4Av_U79ylTu4xYBNp-042w

MD5: 71f47a0f054bb22fc1330b8f2be28e88
[X 2014 Android Development] JulesJam:
Yes, it is motorola's fastboot and it allows you to flash the system.img as a single file rather than the sparsechunks. I don't think it is necessary for logo.bin though. I am just used to using it, but fastboot should work fine to flash logo.bin.

---------- Post added at 09:32 PM ---------- Previous post was at 09:25 PM ----------

can't find it on my XT1060 and then there is this in the update-binary script:

if [ -f /system/addon.d/99-cflumen.sh ]

then

rm /system/addon.d/99-cflumen.sh

fi
[X 2014 Android Development] drwhitney:
I found this: http://xdaforums.com/xposed/addon-d-script-xposed-to-survive-cm12-t3036886. It looks like anything in the system/addon.d/ is for backing up system apps so they can survive reflashing of a ROM. Which we can't do without write access, so it's moot for our devices.
[X 2014 Android Development] JulesJam:
I suspect the easiest thing to do would be along the lines of [MENTION=2278321]btdownloads7[/MENTION]'s method to obtain root - modify the update-binary and then install it through TWRP on a bootloader unlocked device. He had to modify the update-binary for Chainfire's SuperSU so it is likely that this update-binary needs to be similarly modified.

http://xdaforums.com/showpost.php?p=60389310&postcount=177

When I have a chance, I will try using my XT1060 to install CF Lumen using the method above, but if it doesn't work, then the update-binary needs to be modified.
[X 2014 Android Development] G4 Man2:
Considering my cf.lumen convo is happening in the AT&T thread, I figured I'd shoot up a post in this one. I believe that the only way to get it working is getting those surfaceflinger files from a Moto X 2014 variant running on lollipop. If anyone has a working install of cf.lumen running on a Moto X 2014, please pull those files and post them.
[X 2014 Android Development] JulesJam:
The people who are going to have those are going to be the Pure Edition XT1095 owners and I am sure they aren't reading this thread. I would create a separate post on the Q&A forum specifically asking for a PE XT1095 owner running CF Lumen to pull those files and upload them.
[X 2014 Android Development] JulesJam:
I used btdownloads7's method to install chainfire using TWRP on my XT1060 and got a Failed message.

I noticed that CF lumen puts a copy of surfaceflinger in /cache/recovery - So I will try again by putting that in the same directory.
[X 2014 Android Development] JulesJam:
This is what is in 99-cflumen.sh

#!/sbin/sh

. /tmp/backuptool.functions

case "$1" in

backup)

backup_file $S/lib/libcflumen.so

backup_file $S/lib64/libcflumen.so

if [ -f $S/bin/surfaceflinger_cflumen ]; then

backup_file $S/bin/surfaceflinger

rm $S/bin/surfaceflinger

mv $S/bin/surfaceflinger_cflumen $S/bin/surfaceflinger

fi

backup_file $S/bin/surfaceflinger_shell

;;

restore)

restore_file $S/lib/libcflumen.so

restore_file $S/lib64/libcflumen.so

if [ -f $C/system/bin/surfaceflinger ]; then

mv /system/bin/surfaceflinger /system/bin/surfaceflinger_cflumen

restore_file $S/bin/surfaceflinger

fi

restore_file $S/bin/surfaceflinger_shell

chcon u:object_r:system_file:s0 /system/lib/libcflumen.so

chcon u:object_r:system_file:s0 /system/lib64/libcflumen.so

chcon u:object_r:surfaceflinger_exec:s0 /system/bin/surfaceflinger

chcon u:object_r:system_file:s0 /system/bin/surfaceflinger_shell

;;

pre-backup)

# Stub

;;

post-backup)

# Stub

;;

pre-restore)

# Stub

;;

post-restore)

# Stub

;;

esac
[X 2014 Android Development] JulesJam:
On the system partition of my XT1060 there is also libcflumen.so in /system/lib
[X 2014 Android Development] JulesJam:
[MENTION=2821926]ClydeDroid[/MENTION] [MENTION=4049305]G4 Man2[/MENTION] - [MENTION=3273468]Red_81[/MENTION] kindly posted the CF Lumen files.

http://xdaforums.com/showpost.php?p=61098563&postcount=5

he couldn't find surfaceflinger_cflumen on this device though. Not sure why not.
[X 2014 Android Development] hotpass105:
Hey, I have managed to break something. I flashed 1.3 and installed xposed in that order. I was not particularly shocked to find that exposed was not working and I proceeded to uninstall and reinstall xposed. After doing so I reflashed 1.3. This did not fix the issue, so I next flashed 1.1 then 1.3 and this has not fixed the issue either. It says that the framework is unavailable. Instillation is only possible manually via recovery. Will update if I can get a log puppy.

Log:
[X 2014 Android Development] JulesJam:
Did you delete the 2 folders in /data/dalvik-cache? If not, you need to do that.

You can't break anything - /system partition is write protected so nothing you do will affect the /system partition. What I would do is boot into recovery and wipe cache. Then boot back into system. Depending on what you have done, you may need to wipe the /data partition, too idk.
[X 2014 Android Development] hotpass105:
I've attached the xposed log. I flashed the stock image and followed the steps exactly. The cache was cleared and those directories have also been removed.
[X 2014 Android Development] JulesJam:
I would just flash back to stock, then do a factory reset in recovery, then reflash the image.
[X 2014 Android Development] hotpass105:
I used a file manager to navigate to "/data/data/de.robv.android.xposed.installer/conf/" and added the modules.list file with the proper permissions. This fixed the issue. Also, I had previously tried that method to no avail. I'm not sure if this is a new issue for those flashing from STOCK > 1.3; however, it did not occur when I flashed from STOCK > 1.1. Thanks again, XDA!
[X 2014 Android Development] firewater88:
delete
[X 2014 Android Development] d33dvb:
Anything you could do to get some of the network tools like droidsniff zanti sslstrip network spoofer? I think they need access to some files that dont exist, but i have no idea what, it seems like the iptables commands, is it possible to symlink all of the iptables / network /wifi configs as well?

I tried but failed to be able to find through the logcat what was going wrong.
[X 2014 Android Development] tacosrdelicioso:
Can you do aosp signal icons with LTE indicator [MENTION=1262312]cycle[/MENTION]droid? Would be eternally happy for them
[X 2014 Android Development] sonic1675:
Guys remember if you have any questions there is a thread for it. I don't believe op is going to answer them here.
[X 2014 Android Development] joshnat:
What thread?
[X 2014 Android Development] sonic1675:
http://xdaforums.com/showthread.php?t=3102219
[X 2014 Android Development] joshnat:
Ah, got it, thanks. Didn't see that one when I looked in Q&A.
[X 2014 Android Development] GatorsUF:
I posted this in the Q&A thread, but for fear of it no being seen since that thread seems to drop to page 2 or 3 often times...I'll post it here:

I get the theory of a "Q&A" thread when a ROM has a lot of traffic and questions are flying everywhere. However since the development on these ROMs has slowed considerably (with good reason) I think it would be ok to keep questions and new information in one thread so people can get the answers to their questions without having to search 2 threads....JMO

I also posted a question in there...
[X 2014 Android Development] hotpass105:
This is a critical bug alert. Version 1.3 of this rom will not connect 911 calls!
[X 2014 Android Development] hotpass105:
Can someone verify that this is an issue?
[X 2014 Android Development] catawalks:
Is it just me or does the lockscreen come up during an incoming call instead of the dialer incoming call screen?

---------- Post added at 10:10 AM ---------- Previous post was at 10:08 AM ----------

I can confirm this. Dialing 911 just closes the dialer keypad without placing the call.
[X 2014 Android Development] redwings73:
Holy crap. Same here.... Dialing 911 just closes the dialpad without call placement.
[X 2014 Android Development] hotpass105:
Lockscreen does come up for incoming calls. I think the stock dialer may be needed if this implementation cannot be sorted.
[X 2014 Android Development] contesauce:
I also confirm the 911 bug, have to switch back to one of the other images without Gdialer, can't have something happen and no access to emergency services.

Gonna flash back to [MENTION=5849464]mikeoswego[/MENTION] root-tether-BusyBox-SQLite3-Xposed image.
[X 2014 Android Development] tacosrdelicioso:
Omg I'm so happy nothing happened while I was running this!!!!! I switched back to stock last week
[X 2014 Android Development] rhpot1991:
Has anyone verified if the 911 issue exists in the other versions? I'm still running the initial one and I was going to update but I'll hold off for now.
[X 2014 Android Development] tacosrdelicioso:
Try it dude and find out for yourself?...
[X 2014 Android Development] rhpot1991:
Illegal to call 911 without an emergency I thought.
[X 2014 Android Development] mdmogren:
Can confirm 911 bug. Tried another dialer too, same result.
[X 2014 Android Development] mdmogren:
Workaround for anyone using this image - You can still call 911 from the lock screen emergency dialer.
[X 2014 Android Development] RashaMatt:
I flashed TotalX 1.3 as instructed.

Everything seems to be working, EXCEPT Recovery mode is broken.

When I boot into recovery I get the "dead android" image with the red icon.

Anyone else run into this?
[X 2014 Android Development] JulesJam:
Everyone runs into this. That is normal. I cover that in my Noob Guide.

http://xdaforums.com/moto-x-2014/general/noob-guide-rooting-verizon-moto-x-2014-t3097375

When you see the dead Android, you press and hold the power button and then tap and release the volume up button to get into the recovery menu.

Also, if you want to upgrade to a 5.1 image, read mikeoswego's thread in this forum.
[X 2014 Android Development] RashaMatt:
Awesome noob guide - I don't know how I missed that.

Thanks.
[Sprint HTC One (M7)] dtracycar@yahoo.com:
I have a Sprint HTC One (M7) that I rooted a while ago. On the first screen you get when you boot into recovery, it says Unlocked and S-Off. I'm using TWRP Recovery v2.8.3.0. I also use ROM Manager, and have installed a few different ROMs until I found one I liked, with no problems. My current ROM is CyanogenMod 5.0.2. I have superuse v3.1.3 (46). When I try to access Titanium Backup I get an error message that says "Sorry, I could not acquire root priveleges. This application will *not* work! Please verify that your ROM is rooted, and try again. This attempt was made using the "/system/bin/su" command. I cant' figure out what the problem is. Can anyone help?
[Moto G Q&A, Help & Troubleshooting] Brian D:
I had downloaded and installed Firefox and suddenly, two icons appeared on my screenlock. I deleted Firefox and they went away, but I really would like to use Firefox. They are the camera icon int he lower right, and an uparrow in the lower center.

Now, I downloaded and installed Tasker. The icons have reappeared but I do not want to uninstall Tasker.

Anyone know how I can get rid of these icons? I search wide and far and could not find an answer. I am not interested in loading a third party app to remove these icons. Just would like them gone.

Thanks
[Moto G Q&A, Help & Troubleshooting] CJMom:
I always had these Icons in my device, I think it's a problem they don't appear.

Why do you want to remove them? they don't take too much space and doesn't bother at all.
[Moto G Q&A, Help & Troubleshooting] Brian D:
I find them to be annoying. If I wanted my phone to control me, I would buy an iPhone. I know it sounds ridiculous, but I like to have my phone's esthetics the way I would like them to be. For a long time they were not there. And now they show up and I cannot get rid of them. Call me crazy.
[Sony Xperia Miro, Tipo (Dual), J, E] pintudada:
Guys pls pls help me out:'(
[Galaxy S6 Accessories] Sauveur:
I received this case for my Galaxy S6 at an 85% discount in order to provide an honest review. Before I begin, it is important to note that I am not the type of person who would find a wallet case useful. I do not always carry my wallet with me on my person in the first place, and as I am often in the gym, I need a case that can stand up to sweat and dirt. That being said, I am reviewing this case as a wallet case. I'll assume that if you're interested in buying this, you have already made the decision that you are a wallet case kind of person. Finally, note that I did not use this case for more than a couple days. I cannot attest as to its long term durability.

My very first thought upon receiving the product was that it was packaged nicely. My second thought was that the included lanyard, which you need to loop into the case yourself, was extremely annoying. I removed it almost immediately after installing it.

The case has a distinct, leathery smell. The smell also rubs off on your fingers the first few days and can cause some minor alarm until you realize that it's from the case. It otherwise feels and looks premium.

My biggest gripe with the case is that it is not useful to someone with more than a few credit cards. There are 4 slots for cards, and one of the slots has a clear plastic cover, ideal for placing an ID for quick viewing. In my usage I found that each slot couldn't take more than 1 or 2 cards before the case was unable to close and began to warp. In total, if you have more than 6 cards, you're going to have to leave some behind. For me, this meant I could only fit my driver's license, my school ID, two credit cards, and two debit cards. And that's not including cash, which seems like a pain to put in and out.

As far as the phone's functionality goes, the case has a plastic frame that snugly fits around the phone. The buttons are accessible through openings in the case and are easy to press. If you need to take a phone call, it seems like you'd have to fold the wallet portion of the case around the back. Again, I'm not a wallet case person. I imagine this is the case with all similar products.

Overall, it's a nice product for what it's meant to do. My real problem was not being able to carry more than 6 cards. This made the case impractical for me. But if this is the type of case you want, it will do nicely.

EDIT: I added pictures and the Amazon link (http://www.amazon.com/Samsung-Artec...ywords=archetype+21+leather+samsung+galaxy+s6)
[Galaxy S6 Accessories] Artech21-Offical:
If you do not like that kind of case , you should give the opportunity to other who might use it for real

We are really down for this
[Galaxy S6 Accessories] Sauveur:
Well I certainly like the case enough to keep it. I will probably use it while I am traveling, so I can consolidate cards and phone into one case, and since I will be traveling internationally I won't need some of my debit cards.