yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] Blu8:
GPS is fixed, at least it worked for me, but even on stock/Katana GPS is pretty unreliable for some reason, you're welcome to test it out for yourself though, look in the downloads section and the two files are what you need to have everything but video recording working. Again, just a heads up, its up to you if you flash or not.
[Miscellaneous Android Development] satva49721:
screen going blank

I keep experiencing a constant blank screen when screen shuts off. Only option from there is to reboot. I read a post about it being something to do with the new or old stylo and the 11-26 zip. I didn't see any other cm releases available nor do I know what styli I have. Regardless, can I easily fix this somehow or am I out of luck? Thanks
[Miscellaneous Android Development] bradym512:
Hey all! The 12/29 build is up, and includes permenant fixes for GPS, Camera, and disables LED. From a clean flash standpoint, with or without system wiped, LED is disabled from first boot and GPS works. Also, the stock camera app is present and ready to swing. From a dirty flash standpoint, it works fine and is the same as the 11/26 build with the bandaid zip, except it includes the December security patch. Dirty flash users will have to continue using the Google Camera app. As I was building, I realized I forgot to change the pixel density to 304 and forgot to implement the video recording fix commit. Expect to see those in the near future. These are all the major bugs I know of. If you notice a bug, feel free to post it here. If you can fix it, please do and PM me or put it in a post here and it'll be implemented into the sources for the next build. If the fixes keep flowin' the Stylo keeps growin'. Meanwhile, I'm going to begin work on CM13. Cheers!

EDIT: I'll be making a local_manifest.XML and uploading tomorrow. Also, this rom might be pulled from the [Beta] phase soon. We've come a long way, folks. Thank you for all your generous support along the way. The Stylo has potential, and 2016 will be a BIG year for the Stylo's AOSP life.
[Miscellaneous Android Development] dvkrane:
Where is the link to the updated ROM? Btw great job to everyone who's contributed!! I've been waiting patiently for this new build!!!
[Miscellaneous Android Development] bradym512:
It's in the DevDB downloads section.
[Miscellaneous Android Development] thereal_antiHackmasta:
Awesome work. Does this fix the issues with the kernal? Specifically the cpu settings being unable to change frequencies.
[Miscellaneous Android Development] bradym512:
Unfortunately, no. CM13 is going to be based off of the generic Cyanogen 8916 kernel. But I've been building with the sources mentioned so if anyone would like to make a commit to fix that I'll happily build again. I'm not very good with kernels.
[Miscellaneous Android Development] thereal_antiHackmasta:
Thanks for the reply. Forgive me but are you saying that CM13 will not have that problem and that CM12.1 is stuck like that unless we can get someone to fix it? Because that would be great and I'll try to do my research and fix the kernel and with your permission add it to the OP.
[Miscellaneous Android Development] bradym512:
That's what project maintainers are for. Yes please fork it and fix and if it works I'll start using your repo for 12.1 builds. And I'm not saying 13 won't have that issue. As soon as it boots it'll get a DevDB page labeled Alpha or Beta depending on how well it works. Since its a generic kernel it'll take a lot of work. All of you are on my contacts list for help.

IF ANYONE HERE IS GOOD WITH KERNELS PLEASE LET ME KNOW SO I CAN PM YOU IF I NEED HELP WITH IT. I suck at kernels.

Thanks to all who are willing to help me with 13. It's a big project but I'm sure it'll be worth it.
[Miscellaneous Android Development] dvkrane:
There's still a bug that doesn't let me wake up my device after putting it to sleep. The screen turns on but stays black.
[Miscellaneous Android Development] Blu8:
You really need to provide a log instead of just saying that it does that to you, doesn't seem to happen to the guy making the ROM and it doesn't happen to me but I know there's a few people reporting it, logs are needed though.
[Miscellaneous Android Development] dvkrane:
I'm sorry but I can't suppy a log because I switched back to stock for the time being. It's weird because I was on the 7/26 build from TeamRegular and all was fine. I flashed this new build to have all of the fixes incorporated already. I was just letting you all know that the bug is (still) an issue I thought would be fixed in this build.
[Miscellaneous Android Development] thereal_antiHackmasta:
I believe that its due to the stylo having different screens, but with out a log it's difficult to know for sure. I'm sure this will be sorted out soon.
[Miscellaneous Android Development] sirhc:
If anyone can flash this build and provide a log, that would be great. I understand the frustration but bugs can't always be pin pointed off the head. Logs give a better picture of where the bug is coming from so it can be squashed. If he flashed TeamRegulars build, then he has the original screen meaning it's less likely for the bug to exist in that area. Could be configuration for the hardware keys are bad.

Sent from my XT1526 running Cypher 6.0.1 BETA 3
[Miscellaneous Android Development] thereal_antiHackmasta:
I have the old stylo and the newer build has never worked the team regular did. I'll try to flash later this week and give you a log. I would do it sooner but I need my phone for work and I don't have the time to ew install everything.

Rather the new build works but once the screen turns off it doesn't turn back on.
[Miscellaneous Android Development] A Christian Guy:
I been saying that
[Miscellaneous Android Development] Blu8:
And people keep saying they're willing to look into it but they can't guess around at how to fix it without knowing what exactly is wrong. Get a log of it doing that.
[Miscellaneous Android Development] T-Macgnolia:
I can get CM 13 to build using the current repos(screenshot provided as proof) but it does not even give a boot animation so I can not pull a log to try and go further. I am really thinking the issue is in the init scripts but that is the obvious starting point. I have been trying to use the msm8916-common CM has but can not seem to get past the current error I am getting. I have tried using the generic kernel you are talking about and to be honest with you I do not think it will even work if you do manage to get it to build, and I do mean if you get it to build cause it seems like never ending errors with it. You can hit me up if you want when you start trying to build CM 13. I have a record of what I did to get past the 4 errors you will get.

​
[Miscellaneous Android Development] A Christian Guy:
Next time I flash the Rom I get you the log rigth now I'm back on stock rom
[Miscellaneous Android Development] thejoker954:
awesome, just got a pcs stylo a couple days ago, glad to see a cm build. I plan on installing this tomorrow and I can't wait. now if we can just get a pacman rom I'll be in heaven : )
[Miscellaneous Android Development] bradym512:
Been a quiet thread lately. I don't really know where to go now. We're practically bug-free with a rom more than usable as a daily driver. I'm moving onto Resurrection Remix Lollipop and AFAIK TMac is working on 13. I'm starting to have my doubts about a stock MM upgrade to this phone. The only things I can notice off the top of my head are that sometimes when the device is plugged in, color calibration screws up. If there are any bored devs out there looking to get another pull request in their name, you can try to tackle color calibration. The next build might just be the January security patch, but I'll try to work video in there, too.
[Miscellaneous Android Development] MrObvious:
I need to flash this and get you that boot log because my phone will not wake up. Is it just an adb log cat?
[Miscellaneous Android Development] Blu8:
Good battery life? I think yes....
[Miscellaneous Android Development] bradym512:
Definitely yes. What cm theme are you using?
[Miscellaneous Android Development] Blu8:
Just found Swift Dark and it's pretty great. https://play.google.com/store/apps/details?id=com.brit.swiftdark
[Miscellaneous Android Development] sirhc:
Can't wait to port this over to the stylo for Brady's new builds. Errhumm excuse the dialog it's optimized to only work for the moto E for now (Sensor config and integration) but once I port it over it will be a Stylo "Exclusive" ?
[Miscellaneous Android Development] bradym512:
Yaaaas! I'm really excited for cypher. However, mm isn't coming smoothly to this phone. Tmac is working on it rn and says its hell to port.
[Miscellaneous Android Development] sirhc:
Im excited for it to. It will look so much better on the Stylo imo. Yea after speaking to some Devs in the moto threads they even admit that it's not easy. Most of them are full on Teams and they still have a hard time keeping stable builds without breaking things. Same with me and my builds.

Sent from my XT1526 running Cypher 1.5
[Miscellaneous Android Development] bradym512:
Wow. I thought it was just tmac working on it. I'm currently working on porting stock 6.0.1 from the sprint update to the tmo device. Hopefully by the time it's stable 13 will be working and I can start work on MM Resurrection or something.
[Miscellaneous Android Development] sirhc:
Wait... Marshmallow got released for the sprint stylo? Wow I didn't know that

Sent from my XT1526 running Cypher 1.5
[Miscellaneous Android Development] bradym512:
Haha yeah it did. The ls770 got mm. So I'll put all the tmo bloat on it etc and modify it to work with the Stylo and use the Return2Stock updater script.
[Miscellaneous Android Development] sirhc:
Sounds good. LG didn't release a kernel source? If they did, you guys could've used that for MM

Sent from my XT1526 running Cypher 1.5
[Miscellaneous Android Development] bradym512:
I think they did. Go to the open source LG website and search ls770 and see what they got.
[Miscellaneous Android Development] sirhc:
Yup it's right here http://opensource.lge.com/osSch/list?types=NAME&search=Ls770 go to the far right and you'll see the source tab where you can download as well as license information

Sent from my XT1526 running Cypher 1.5
[Miscellaneous Android Development] bradym512:
Well then... That'll be useful in MM Resurrection.
[Miscellaneous Android Development] sirhc:
Yup, just use their kernel which you'll mostly likely have to modify a little bit. I know the LG Tribute community was waiting for LG to release MM and their source so they could get a MM ROM but they haven't had any luck. Stylo users are very fortunate. This makes building MM much easier

Sent from my XT1526 running Cypher 1.5
[Miscellaneous Android Development] bradym512:
Yes definitely. I'll look into it.
[Miscellaneous Android Development] MrObvious:
brady,

See attached. It seems to start around the line

E/WifiStateMachine( 2236): cancelDelayedScan -> 19

E/WifiStateMachine( 2236): WifiStateMachine L2Connected CMD_START_SCAN source -2 18, 19 -> obsolete

I/PowerManagerService( 2236): Waking up from sleep (uid 1000)...

I/DisplayPowerController( 2236): Blocking screen on until initial contents have been drawn.

I/QCOM PowerHAL( 2236): Got set_interactive hint

D/SurfaceFlinger( 275): Set power mode=2, type=0 flinger=0xb8ad85e0

D/qdhwcomposer( 275): hwc_setPowerMode: Setting mode 2 on display: 0

E/qdutils ( 275): int qdutils::getHDMINode(): Failed to open fb node 2

E/qdutils ( 275): int qdutils::getHDMINode(): Failed to find HDMI node

I/DisplayManagerService( 2236): Display device changed: DisplayDeviceInfo{"Built-in Screen": uniqueId="local:0", 720 x 1280, 60.0 fps, supportedRefreshRates [60.0], density 320, 257.577 x 258.031 dpi, appVsyncOff 0, presDeadline 17666667, touch INTERNAL, rotation 0, type BUILT_IN, state ON, FLAG_DEFAULT_DISPLAY, FLAG_ROTATES_WITH_CONTENT, FLAG_SECURE, FLAG_SUPPORTS_PROTECTED_BUFFERS}
[Miscellaneous Android Development] MrObvious:
Wowsa, it's something in the Kernel. I flashed the boot.img in TWRP from the 7/12/15 build and it worked.
[Miscellaneous Android Development] sirhc:
Those are kernel commands so yea I was just getting ready to tell you that

Sent from my XT1526 running Cypher 1.5
[Miscellaneous Android Development] MrObvious:
I wonder if it will break anything else though? I guess I'll find out.

How hard would it be to compare the kernel differences and find what might be broken?
[Miscellaneous Android Development] sirhc:
It shouldn't break anything. I don't think any kernel specific changes where made yet and just take a log like before

Sent from my XT1526 running Cypher 1.5
[Miscellaneous Android Development] thereal_antiHackmasta:
So your using noobs kernal with brady's build and the screen doesn't lock up?
[Miscellaneous Android Development] ardaz87:
Ardaz87

Ardaz87

https://play.google.com/store/apps/details?id=com.frozenvolcano.android.cinema4kk

I downloaded that app, and video recording works. ... App crashed after I pressed stop but it saved the video and played normally when reopend

Yesterday at 11:23 AM
[Miscellaneous Android Development] MrObvious:
Yes that's what I did. However video recording doesn't work. It says "cannot connect to camera".
[Miscellaneous Android Development] ardaz87:
https://youtu.be/vUpDLlcBOxE

Recorded my phone using it.
[Miscellaneous Android Development] Blu8:
Yeah that definitely works
[Miscellaneous Android Development] ardaz87:
How though? .. App crashes after a setting changes but the change sticks when reopened.
[Miscellaneous Android Development] bradym512:
Hey guys I just built the kernel from v10j stock to text how it works with cm12.1 and it gave me a zImage file. Is there any way I can get into fastboot to flash this or make it into a boot.img file?
[Miscellaneous Android Development] sirhc:
It's alot of work http://androidforums.com/threads/how-to-build-kernel-zimage-into-boot-img.824521/

Sent from my XT1526 running Cypher 1.5
[Miscellaneous Android Development] MrObvious:
I think there is already a compiled boot.img in the 10j download flashable zip.
[Miscellaneous Android Development] thereal_antiHackmasta:
Link?
[Miscellaneous Android Development] MrObvious:
Nevermind. Just flashed it and it rebooted straight back to TWRP. I can't find it though, but just had a stale cache copy. If anyone wants it I can upload it, but it's not working.
[Miscellaneous Android Development] thereal_antiHackmasta:
Yeah I did a little research and it won't work.
[Miscellaneous Android Development] bradym512:
What won't? Using that boot.img or using the stock kernel altogether?
[Miscellaneous Android Development] thereal_antiHackmasta:
[/COLOR]

Using stock kernel won't work on cm to many differences between roms. Boot.img contains the kernel along with boot header and ramdisk.
[Miscellaneous Android Development] bradym512:
Yeah but the one I'm using for builds is modded and I'd rather redevelop it from stock. Really soon I'm going to try building AOSP 6.0.1 with the LS770 MM kernel. I'm having a hard time deciding what project to tackle next. I was going to do the stock 6.0 thing but now that ik there's a promising method for porting mm that hasn't been tried idk. I'll just try building tonight.
[Miscellaneous Android Development] thereal_antiHackmasta:
Apps 6.0.1 would be awesome. I'm sure that T-Mobile and metro are gonna get an update for mm stock soon so I wouldn't waste time on that but most importantly do what is fun for you.
[Miscellaneous Android Development] bradym512:
Yeah. Thanks. I just downloaded the 6.0.1 r41 source... to my home directory. This'll be fun to clean up. I moved the .repo directory to my intended workdir and repo synced so it's extracting. I won't be home for another 2 hours then I'll sync everything and put the stock kernel in kernel/lge/msm8916 and start fixing le errors.
[Miscellaneous Android Development] thereal_antiHackmasta:
Your da man! I just flashed the team regular boot.img onto your latest build of cm and it's booting I had the issue of the screen turning off and not turning back on because I have the older stylo. You have the newer one right? I was told that it is a kernel issue so if this work that would confirm that.
[Miscellaneous Android Development] bradym512:
Yeah I've got the newer one. I always knew it was a kernel discrepancy I just didn't know where. I don't physically have an old stylo so even when people are pulling logcats for you its still hard to work with.
[Miscellaneous Android Development] sirhc:
I was gonna say stock boot.imgs don't work with CM. CM is CAF, stock isn't. Brady is simply using the stock kernel and making it work with CAF CM.
[Miscellaneous Android Development] bradym512:
Haha I feel stupid now. What's caf?
[Miscellaneous Android Development] sirhc:
Can't really explain in detail right now, but in shorter terms, it's well optimized with Qualcomm chips and is better at performing.
[Miscellaneous Android Development] thereal_antiHackmasta:
So after 20 mins of testing I can confirm that flashing TR's boot.img over your build works for the older stylo's. Also I think someone say that they got a zImage when trying to build kernel well I found some info to make it into a boot.img. Let me know if you need help there.
[Miscellaneous Android Development] AgainstTheFlow:
Where can I find TR's boot image? I am having the same issue with my Stylo
[Miscellaneous Android Development] thereal_antiHackmasta:
So here is what I did.

1.Flash TR's CM

2.Make backup of boot only.

3.Flash brady's CM

4.Restore boot only reboot and should work fine.

Still some random reboots and a little laggy compared to Katana but CM is much better. Also the battery life is better than the TR build even though the CPU doesn't throttle down.
[Miscellaneous Android Development] Blu8:
Guys quick question, what's the biggest package you've flashed from opengapps?
[Miscellaneous Android Development] sirhc:
Pico
[Miscellaneous Android Development] kcarden:
Iirc if you unpack the kdz and the dz you should get a boot_(partition size).img
[Miscellaneous Android Development] thereal_antiHackmasta:
Yeah but stock kernel does not work.
[Miscellaneous Android Development] A Christian Guy:
Nop no luck only reboot keep booting to recovery
[Moto G Q&A, Help & Troubleshooting] Hurriname:
I want to install TWRP on my Moto G but i am not 100% sure if or how it could brick my phone. I want to install this > http://teamw.in/devices/motorolamotog2013.html <. Can you tell me if it could cause a hard brick or could i repair it with in fastboot if something goes wrong?

I am using the XT1032 with Android 5.1, Bootloader unlocked and phone's rooted.
[Moto G Q&A, Help & Troubleshooting] lost101:
It's best to use the version of TWRP in Development section: http://xdaforums.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621

You cannot brick your phone; even if you flashed a recovery.img for a totally different phone. The fastboot command is:

fastboot flash recovery recovery.img​
[Moto G Q&A, Help & Troubleshooting] Hurriname:
I just tried the link you gave me and it worked perfectly. Thanks alot :)
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] dpmeeks:
Is there simple instructions on how to root and install a rom for the latest lollipop update on the sprint s4 ? Ive been able to use kingroot and it worked but ive read you have to use supersu to be able to install custom rom so I deleted everything and its basically back to stock again. I'm just wondering if there is simple step by step instructions without bouncing all over the place to get it done ?
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] EngineManShawn:
Took me a while. I used twrp and it wanted a su binary update. Couldn't figure it out so I installed kingroot and it somehow gave me the su binary that I needed and I acquired root. Now the backup (recovery) that was a whole different story. Go to the Thread on everything for your specific device. It has complete instructions on rooting S4 mine was Sph-l720t. I takes patients you can figure it out. The good news is you can always reflash your firmware if all fails.

---------- Post added at 08:05 PM ---------- Previous post was at 08:03 PM ----------

Odin and cf-autoroot is the easiest. Was for me. Has super su in the zip file.
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] dpmeeks:
thanks engine... I can never get supersu to work with lollipop so I can get it rooted is my problem.
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] K94U:
Kingroot works but THEN you need to use super_sume from the play store. I used an older version of super_sume in my full 2 part video of the entire process... https://www.youtube.com/watch?v=IWnYFDQ1Vio

To install a custom ROM, you need a custom recovery OR you can try Flashfire without a custom recovery...
[X 2014 Q&A, Help & Troubleshooting] Qwerty1208:
I have decided to sell my Moto X and so I decided that I would restore it to stock firmware before I let anyone else take it over.

Everything on it (Pictures etc) is already transferred to my computer and deleted from the phone, so no worries about that.

To start with I had the bootloader unlocked, was rooted and running Nexus Experience.

I downloaded a factory image (VICTARA_RETEU_XT1092_5.1_LPE23.32-25.1_cid7_CFC.xml) I found here on XDA,

and flashed it manually as follows:

mfastboot flash partition gpt.bin

mfastboot flash motoboot motoboot.img

mfastboot flash logo logo.bin

mfastboot flash boot boot.img

mfastboot flash recovery recovery.img

mfastboot flash system system.img_sparsechunk.0

mfastboot flash system system.img_sparsechunk.1

mfastboot flash system system.img_sparsechunk.2

mfastboot flash system system.img_sparsechunk.3

mfastboot flash system system.img_sparsechunk.4

mfastboot flash system system.img_sparsechunk.5

mfastboot flash system system.img_sparsechunk.6

mfastboot flash system system.img_sparsechunk.7

mfastboot flash modem NON-HLOS.bin

mfastboot erase modemst1

mfastboot erase modemst2

mfastboot flash fsg fsg.mbn

mfastboot erase cache

mfastboot erase userdata

mfastboot erase customize

mfastboot erase clogo

mfastboot reboot

Then I get the warning that the bootloader has been unlocked. At first it got stuck there, but after forcing it to

shut down and trying again it gets past it and instead it starts flashing the android figure laying on it's back with a lid open

and a red hazard sign above it, telling me "No command". This appears for about 0.1 seconds every fourth second.

So here I am now, the phone is still flashing this message and it seems I can't really turn it off. I can (Sometimes, with a little

luck) reach fastboot mode, but whatever I choose from there takes me to the bootloader warning and the "No command" message.

Is there anyone that can guide me through this so I can get it up and running again and hopefully back to stock firmware?
[X 2014 Q&A, Help & Troubleshooting] moreadon:
I'm guessing you missed

mfastboot flash system system.img_sparsechunk.5

mfastboot flash system system.img_sparsechunk.6

mfastboot flash system system.img_sparsechunk.7

Did the same thing the other day.

Re flash with all sparsechunk files. I'm on 1095 so there was 7 for me. Not sure about 1092.

I still had the error after. I rebooted into bootloader then selected factory and it worked.

Good luck

---------- Post added at 12:22 AM ---------- Previous post was at 12:19 AM ----------

I also didn't use these comands

mfastboot flash partition gpt.bin

mfastboot erase customize

mfastboot erase clogo

and after

mfastboot flash motoboot motoboot.img

I used

mfastboot reboot bootloader

I'm not sure if those commands are needed. Just wasn't in the tutorial I followed
[X 2014 Q&A, Help & Troubleshooting] Qwerty1208:
I did miss those, but only when I wrote this thread. Fixed that now.

I'm gonna give your method a try in just a minute!