yashsingh1/xdaforums huggingface dataset:
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] matthew_wetton:
appologies i have downloaded and it helmis rom claiming to be WM6 !! i think damn the con artists
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] matthew_wetton:
Also i have seen that T mobile users are being offered a WM6 ROM on their MDA III which is the BA isn't it?
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] matthew_wetton:
http://xdaforums.com/archive/index.php/t-309604.html

see there we go
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] Midget_1990:
thats an artemis lol
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] matthew_wetton:
ah i see i thought the MDA III was a BA
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] cyphol:
Waiting for a "...maybe it will be one for us. Hopefully"
[Sony Xperia M2] danhtho:
I has just update to android 5.1. It look good but icon size is too large. How can I resize it smaller ?
[Sony Xperia M2] Gaurav007:
Long tap on home screen>Home screen settings>icon size>small
[RAZR HD Q&A, Help & Troubleshooting] ddichiera:
Hi all, first post here.

I have a bricked XT925 which I'm trying to recover.

It will go into fastboot and I can access it with ADB/Fastboot/mFastbootv2/RazorHDToolkit5.0/RSD lite etc, but none of these will write a new recovery to flash.

I was able to unlock the bootloader using the Motorola website and the phone will talk to the PC software, but it's as though the internal flash memory is trashed.

In fact lots of commands to the flash result in a "fastboot max download size 30mb" error.

Can anyone help?
[RAZR HD Q&A, Help & Troubleshooting] Spott07:
I would start with obtaining a clean working flash of the official ROM, before trying to flash anything custom.

Just a guess, but if you went to the unlock website after the phone was soft-bricked, the bootloader may still be locked. I assume that the phone needs a full working OS to receive and implement the unlock signal from Motorola. Since it hasn't booted the OS since it was bricked, it hasn't had a chance to do so.
[RAZR HD Q&A, Help & Troubleshooting] ddichiera:
Would that I could. All the links I've found so far are dead.

I have another XT925 in working order, anyone know how to extract the image from it?

I think the Bootloader error messages are to be expected, everything I've since read suggests I should ignore them.
[RAZR HD Q&A, Help & Troubleshooting] palmbeach05:
I have one of the old Canadian leaked KK stock sbf (I was using it to see if I could bring anything to my AHD). I can post it to my GDrive and post the link this afternoon.
[RAZR HD Q&A, Help & Troubleshooting] ddichiera:
Any image would be welcome, GDrive is fine.
[RAZR HD Q&A, Help & Troubleshooting] palmbeach05:
https://drive.google.com/open?id=0B52pkPIFU2dRWFRXOU9UQlhHZ3c
[RAZR HD Q&A, Help & Troubleshooting] ddichiera:
Thanks for that, unfortunately my situation has become worse.

Whilst the phone was connected and in fastboot mode, I deleted the ADB driver in Device Manager and now the PC, or more specifically ADB and Fastboot wont talk to the phone. Grrrrr.

Oh, and the other handset has decided to die as well.

One thing at a time. Anyone know how to restore the driver/get-the-phone-talking-to-ADB/Fastboot again?
[X Style (Pure) Accessories] zrj9294:
Got the bumper and case on Moto.com

The case feels more solid and comfortable in hands because of the curve and thickness. But as you can see the case can easily catch fingerprints on it. Actually the case looks a lot better in reality than in this picture, my bad.

The bumper is a little loose on the left and right side and feels less premium than the case due to the material. But I do love the color and the design to show your finish.

Ps, I got these two with only $15, that's another story.:)
[X Style (Pure) Accessories] zrj9294:
Forgot one thing. The case can relative cause heating issue. I can feel a little warmer (not hot) with the case under the same usage.
[X Style (Pure) Accessories] thefunks67:
Still a naked phone for me but thanks for sharing.
[X Style (Pure) Accessories] chris23445:
What's the name of the full case? The one on the right? Also..how did you get them for $15??? I dig the clear case but if I remember correctly it is over $20 lol.
[X Style (Pure) Accessories] zrj9294:
It's Naked Tough Case for Moto X Pure Edition, you can find it both on Moto and case-mate's website.

Well I ordered the X Pure but my delivery was about one week late, so the rep of moto gave me a coupon of $25 to purchase any accessories on the website. Later I decided to get a bumper, which costs 20. I thought that the coupon of 25 can easily cover the whole price of the bumper (I just thought they will cut the price with maximum 25), but later I found that the coupon didn't work and I was fully charged. I called moto and they told me that I have to make my total purchase over 25 to be eligible to use the coupon. It's kinda sophisticated, let me make some examples:

1, You bought an item under 25, even 24.95, not work. You pay full price.

2, You bought a single item over 25, let's say 29.95, you pay 4.95+shipping.

3, You bought two items with total over 25, maybe one 20 and one 15, you get the 20 free and pay 15+shipping.

See? That's really complex and They did NOT mention this kind of thing anywhere. While after discussion they decided to cancel my original order and send a free bumper, and I can still use that coupon to buy other staff, while I went with the case. That's the whole story, to be frankly, compared with the ending, I would rather they ship my phone on time at the beginning.
[X Style (Pure) Accessories] rushless:
The heat is why I would rather use a bumper case. This device IMO gets too hot to have a case on it for my medium to heavy use. Any app that uses the GPU much gets this device hot and a case only helps keep the heat in.

As far as the bumper case, the tube trim seems like it could come off after some wear. Does it seem that way to you? It looks like a blue tube that has been glued to the bumper frame.
[X Style (Pure) Accessories] zregnier:
I got mine this morning. Really liking it so far. Don't feel like I'm going going to drop the phone any more. I got the grey/black and it goes well with my white front and dark ash wood back.
[X Style (Pure) Accessories] rushless:
Does the tube trimming look like it will come off after some wear?
[X Style (Pure) Accessories] zregnier:
Hard to say. It looks perfectly flush so I'm thinking it's good for at least a year unless you're really rough on phones. My main worry is dust/grit collection and scuffing up the edges of the phone. I'll make sure to clean it out weekly.
[X Style (Pure) Accessories] Corduroy-21:
Just wondering if you think the bumper alone can offer protection. The phone is huge and I'd like to avoid any case, but I don't know if that's wise.
[X Style (Pure) Accessories] tyronekramsey:
Actually it's no complicated. They give a 25$ coupon essentially. It's not a 25$ giftcard where you use it and you have money left over it's a one time coupon to use and you have to use it all
[X Style (Pure) Accessories] Bootup:
mine is already lose around the buttons area. There is very noticeable slack and looseness on the right side of the phone now. It started tight and flush but not so much now and its only been a week and I've only taken it off once.
[X Style (Pure) Accessories] rushless:
Based on the design this is what I expected, but a few months later than now. It would be better off with a harder frame and coated rubber glued around the frame.

I will use the plastic two parter for a while longer I guess. I was going to drill holes in the back, but can see the plastic crack. Need to think about it....

The bumper case it came with was too fragile and broke around the button area. Plastic is too thin. These hard cases though only seem good for scratch protection and keeping the heat in for GPU heavy app use. The latter is not a good thing.
[X Style (Pure) Accessories] zrj9294:
I think it can protect in a certain level, but clearly it's not the best option compared with other cases.
[X Style (Pure) Accessories] rushless:
Seems though it will protect better than the hard cases, since all hard cases do is transfer energy to the device itself when dropped. About the only good a hard case provides is scratch and scuff protection.
[G3 Q&A, Help & Troubleshooting] chichibud31:
Keep getting popup saying "Currently unable to download, please try again later." Factory reset done and still I get the popup occasionally. Would appreciate some help as to how to fix this problem?
[G3 Q&A, Help & Troubleshooting] itsbighead:
Might be a issue related to your storage deice

Are you saving to sd card or internal storage?
[Moto X Q&A] blueblur1986:
This has been happening the last few days, at least once if not twice daily, but I will unlock my phone to find out the Google Voice Keyboard is frozen with no way to force close it and block the bottom half of my screen on EVERY screen. The only way to get it to go away is to power off the phone and power it back on. This is getting very annoying since it happens so often.

Sometimes it appears out of nowhere, sometimes it is after I use voice typing. I have used voiced typing in between and it opens and closes fine. It seems very random.

Any thoughts to get it to stop?
[G2 Android Development] casual_kikoo:
When I see how many projects are done for the G2, I really think I should give a try... Anyway, !gg mate, I'll try this recovery ;).
[G2 Android Development] blastagator:
What did you change? Or did you just build my repos and post a new thread?
[G2 Android Development] Lawlrus:
[MENTION=2096805]dr4stic[/MENTION]

There's no "thermal support" official twrp uses their kernel, which blasts all cores on max freq, generating needless amounts of heat.

From the sounds of it, you're using the stock cm12.1 kernel, so there should be no heat issues. If the CPU gets hot, it will throttle as it is supposed to.

So that's what his twrp means when it says thermal support. It uses our phones kernel so it operates like it would on a ROM.
[G2 Android Development] dr4stic:
[MENTION=5559940]Lawlrus[/MENTION], thank you for the explanation! After I investigated I assumed that's what was going on, but I didn't want to assume and then tell people something I wasn't sure about. I noticed that mine gets a slight toastier than blastagator's, but not a significant difference. I attributed it more to kernel tuning with the finalized CM kernel than anything else.
[G2 Android Development] blastagator:
Nah man, I'm not upset. I made it so easy (or tried to make it easy, at least) to build my source so other people could muck with it. My curiosity stems from wanting to add any improvements in to my build. :)

I briefly messed with cm12 device trees but didn't have luck the first go around so I didn't bother going down that road. Will definitely keep an eye on this thread.

My builds are built with the Omni 4.4 Source, and these changes:

https://github.com/blastagator/cm_device_lge_g2-common/blob/cm-11.0/blastagator_g2-common.xml

The device trees are actually based on cm-11, not 12.

As for SELinux, issues probably stem from this: https://github.com/blastagator/aicp...mmit/85953d0cf8dd3d33406ad8a745ced99e5039f766. When I committed it I thought it set SELinux to permissive. However, it actually completely disables SELinux, so the kernel won't automatically preserve contexts, etc. This seems like the most likely culprit for your issue. I will run a test build and revert that commit, if you'd like it to test.

As to cm-12, in general: I'm certainly interested in moving up, I just never really had a reason to spend any time on it.
[G2 Android Development] dr4stic:
PM me with your email. I'll shoot you the diff I made. The only reason I haven't posted it to github is that I wanna show the changes piecemeal instead of in one big diff. If you can call it big... it's really just 4 changes :)

Honestly, I'm not sure why they recommend against building on CM. Despite their documentation being utter crap, the build itself was easy once I figured out where the pieces were all supposed to go.

And yeah... CM 12.1 at the time you built things was an absolute mess. But the stuff in the official repo's is really rock solid now. Well, maybe not tonight, it seems there were a bunch of g2 changes and one in particular is gonna break the build for tonight :)
[G2 Android Development] jacoghi:
Tried the d800. Device went into fastboot mode, doesn't boot into recovery. Back to blastagators.
[G2 Android Development] sandys1:
Github makes tracking all of this better. My suggestion is that you first create a "fork" of blastgator's repo on Github, and then "clone" the repo on your local machine. Apply your diffs to it. Commit and Push (to your fork). Then issue a pull request to Blastgator.
[G2 Android Development] dr4stic:
Thanks for your suggestion. I'm already talking to blastagator. The problem is that his current build isn't actually based on CM-12, we are working from different sources.
[G2 Android Development] dr4stic:
I have a few d800's, it's the device I use. Which bootloader are you on? JB? KK? LP?
[G2 Android Development] jacoghi:
I have the hybrid LP bootstack, from blastagator, which includes the KK aboot. Blastagator's twrp works without hitches
[G2 Android Development] dr4stic:
Just a few things...

Are you talking about the "Bump LP" bootstack on this page?

Are you sure you downloaded the d800 recovery?

If you did, could you verify the md5 of the file you downloaded against the one I list in the OP?

Thanks.
[G2 Android Development] jacoghi:
Yep to all of them. I flashed your image using blastagators twrp and got the fastboot mode. Let me know should you need any extra info. Thanks
[G2 Android Development] dr4stic:
Do you use cm-12.1? Which ROM do you use (and version) if you don't mind me asking.
[G2 Android Development] jacoghi:
I'm using cloudy 3.3 right now with xceeds kernel. After I got the fastboot mode, I could boot my system normally, if that helps. Rebooted again, got fastboot once more. Then booted system up again and installed autorec, which corrected the problem.
[G2 Android Development] teamacc:
Well, messed around with this for a bit, decided to format /data to f2fs.

Dont do that. Not on this recovery. Formatting to f2fs takes forever (probably hangs entirely as i waited at least 10 minutes before rebooting)

Then noticed my /data wouldnt mount on reboot, causing my rom to bootloop and, even worse, the recovery to bootloop.

Due to a (probably unrelated) bug the lg flash tool didnt work either, so had to open up the device to boot in qhsusb mode and manually format /data to ext4.

This is the closest I've been to a complete brick on this phone since I got it.

Please update the OP to warn people about f2fs.

Nice work on the kernel update, but I personally am going to avoid this recovery until the above issue is solved
[G2 Android Development] abc001:
My problem is that it would not reboot nor power off while in this recovery. But it works by pressing power button.
[G2 Android Development] abc001:
It is ok now by removing the theme file ui.zip.
[G2 Android Development] dr4stic:
Thanks for letting me know, I'm updating the OP appropriately.
[G2 Android Development] dr4stic:
Alright folks. I've updated the OP with a new version.

Anyone using the previous version should consider upgrading. One of the changes is by way of a recommendation by [MENTION=5031300]blastagator[/MENTION] regarding the location of the data / media partition. He suggested that without those changes, one could have issues. So, upgrade, because safer.

Also, There's a whole new theme (which I cherrypicked at the behest of [MENTION=4662457]Rashed97[/MENTION]). I'll get around to posting screenshots of it later. I need to rework the OP (I really should've reserved the second post, but whatevs). Whether it looks better or not is up to you, but I will say it seems to provide better access to options and what not.

Finally... There are two issues that I'll get around to testing/fixing (if I can) once I get my test phone back (in about a week and a half or so). My d800 is my daily driver and I am not in the position at the moment to test changes to make f2fs work.

Enjoy!
[G2 Android Development] obvious:
Nice logo/theme :)
[G2 Android Development] daniel.stuart14:
[MENTION=2096805]dr4stic[/MENTION] , where can I found your device source? Community could help you with bugs if you post it on the 1# post.

Also, about the f2fs bug, it should fix: http://review.cyanogenmod.org/#/c/110402/

EDIT:

Also, AROMA packages are making phone to restart here. It isn't happening with blastagator's version.
[G2 Android Development] teamacc:
You can test wether f2fs will work by formatting cache to f2fs, this will not break your device, just requires you to reboot and reformat.

Formatting data however will break your recovery into a bootloop (if f2fs is still broken) - maybe its a good idea to change the default behaviour of [/data not mountable] into [dont auto-exit/reboot recovery]
[G2 Android Development] TheUnladenSwallow:
Hey [MENTION=2096805]dr4stic[/MENTION], any chance you'll consider a mirror other than dev host? XDA no longer recommends them and for good reason, when I clicked it a new window popped up AND there were fake download buttons on multiple ads.

EDIT: wtf, the dev host download gave me a .ace with the file's name that opens up to an exe, I'd already deleted it but then my antivirus detected it... Seriously bro, take down the dev host links.

EDIT 2: Found a link to the actual img hidden in the multitude of download buttons :P

EDIT 3: Also it appears the material theme doesn't work on vs980.
[G2 Android Development] dr4stic:
I have an ad blocker, I guess that's why I don't see those things. Got any suggestions?

EDIT 3: define "doesn't work" ... I'm fairly sure everything was replaced, so either I uploaded the wrong recovery, or... well, I don't know. But I don't think it's a switch so much as a replacement.
[G2 Android Development] TheUnladenSwallow:
As for hosting this article lists good alternatives http://www.xda-developers.com/xda-devhost/ androidfilehost has always been good for me. As for the theme it just shows normal twrp and from what I can tell there's no theme folder in the twrp folder.
[G2 Android Development] dr4stic:
I'd been planning to update my OP with this information, I just haven't gotten around to it:

https://github.com/dr4stic/twrp_device_lge_g2-common ... Thanks for the link to the f2fs bug, I'll look into it soon. Building is a pain when you don't have a server farm ;)

Also, what are the AROMA packages? Link?
[G2 Android Development] dr4stic:
Thanks for the list. I'm not wild about exposing my drives (whatever the protections may be). And Dropbox scolded me once for much larger downloads... so Android File Host it is. I signed up for dev access, I just have to wait for them to approve me.

Huh... that's odd. Really odd. I ran the builds successively and alphabetically, and I didn't update my repo between any of the builds (which would've wiped the cherry pick), and the files are still all there. Are you sure you installed the right one? I gotta do something about the versioning to make diagnosing this easier, but I don't wanna artificially bump the patch level when I'm not actually modifying twrp itself.
[G2 Android Development] daniel.stuart14:
Droidth 30f, you can found it here.

You can upload the images to github as a release.
[G2 Android Development] dr4stic:
FYI

I've repackaged the 20151015 builds as zip files. I have been made aware by [MENTION=4662457]my personal sous chef[/MENTION] that if I just distribute images then devices with the JDI panels will get the white lines if they are ever timeout the display and then get woken up again. Therefore a zip file is necessary to package a script to modify the recovery for the proper panel during the flash procedure. If you flashed the img file and have had no ill effects, then don't worry, you're fine. If you'd feel more comfortable re-flashing, then by all means do that.

Additionally, on the advice of [MENTION=5377343]TheUnladenSwallow[/MENTION] I have moved the downloads from dev-host to Android File Host.

I will be packaging and moving the 20151003 release soon enough.
[G2 Android Development] dr4stic:
Just to re-touch on this.

What's restarting? Does your device restart when you flash the zip? eg... is the recovery crashing? Or do you mean the phone reboots when you flash an aroma package and then reboot the system.... eg the ROM goes into a bootloop.

If the twrp produces some sort of error, can you screenshot the onscreen log for me pls? Thanks.
[G2 Android Development] :
On the last version before the latest builds with zips, I had data and cache formatted with blastagator's twrp. When wiping cache on this recovery or on cm recovery it takes like 5 minutes, more or less, to format. Just though I post this as a note, because on blastagator's it takes seconds. Anyways , awesome theme and thanks for this recovery.
[G2 Android Development] MB525:
Hi dr4stic,

i confirm reboots with aroma scripts. Just tested with Nevax Boot Changer, it immediately reboots into system. No chance for a log.

I was using the Play theme before and that still functions well.
[G2 Android Development] TheUnladenSwallow:
Hey there, just wanted to say thanks for the new builds, the material theme now works and the new host works. Also I can confirm that f2fs doesn't work/is too slow to be practical.
[G2 Android Development] PYCON:
Tried, nice theme and thx for the hard job :)

But wipe dalvik & cache on my D802 takes 3 or 4 mins :eek:I've to go back to 2.8.7.1 by Blasta :silly:
[G2 Android Development] dr4stic:
Folks, I'm closing up this thread and packing up development. Blastagator's 2.8.7.3 release fixes the sepolicy issues that started my project. Also, TWRP doesn't like to be based on CM directly. Or maybe CM doesn't like to accomodate TWRP. Who knows, either way it created more problems than I had time, inclination, or expertise to solve. Thank you all for trying this and for your support. Consider this project abandoned (for now, and possibly ever).
[G2 Android Development] fendaris:
Thanks for all the work you've done.
[General Accessories] asafb24:
Thanka for the review.

I would like to know howmuch mah does they really have?

For example xiaomi 16000 mah powerbank has 10000 mah (the rest get lost at the conversion.
[Verizon LG G2] blunk2000:
So first. I was trying to flash TWRP with AutoRec and when I rebooted I got a message saying fastboot mode started. I couldn't access anything else. I read around and managed to get download mode back but I cannot flash the kdz with the flash tool because the phone is not detected by the computer while in download mode. This is the Verizon variant g2 (vs980).
[T-Mobile LG G3] singmokjai:
Can anyone please help me with this problem? I recently started to get this error message and it pops up every time I unlock and access my phone. I never had this problem before. I think it happened after I updated the 'Google' app but not sure if that is the cause. Also accessed hangouts for first time on mobile but didn't actually use it. Please see attached document for error message. Any help much appreciated, thanks.
[T-Mobile LG G3] singmokjai:
anyone can help please?
[T-Mobile LG G3] redduc900:
If you think the error started appearing after updating the Google app, then try force stopping the app, then uninstalling updates. Or you could try clearing the Google app cache.... both options of which are located under Settings--> General--> Apps--> All.
[T-Mobile LG G3] singmokjai:
I've tried that but the message still keeps popping up. Maybe it's a different app? I haven't updated to lollipop but I don't think that is relevant. Is there like a list of all Google associated apps so I can try clearing cache or force stop? Not sure what else to do :(
[T-Mobile LG G3] singmokjai:
anyone else got other ideas? Help much appreciated thanks.
[T-Mobile LG G3] CarvedArt:
Google Services Framework
[Sprint Samsung Galaxy Note5] keebler125:
Has there been any advance on correcting the KNOX trip that rooting the device trips?

thank you