yashsingh1/xdaforums huggingface dataset:
[T-Mobile Samsung Galaxy S 5] systemshock869:
I'm sorry, originally I put G900T in the title, thought I had specified that. I definitely don't want an AT&T phone unless I go with an active. Hoping to find out if the vanilla lollipop kernels for this phone are stock or not and if any/all custom roms are able to be used on Cricket with a simple SIM swap or if there is another procedure for it.
[T-Mobile Samsung Galaxy S 5] mabry:
Buy a T-mobile one, then you can run whatever you want. Make sure you get it SIM unlocked so your Cricket SIM will work. As for Carriers, there is no difference what SIM you have in there. It will still work.
[T-Mobile Samsung Galaxy S 5] talkingmonkeys:
I'll ask a mod to move this to the tmobile forum for you. I think they may be more helpful. We are strictly touchwiz here on the G900A whether we like it or not sadly.
[T-Mobile Samsung Galaxy S 5] Ragnar:
Thread moved to T-Mobile Q&A forum as this is what the OP is looking for.
[One (M7) Q&A, Help & Troubleshooting] D_Angelos:
Hello everybody!

i m using artmod's rom and i would like to install and use google dialer from santod040's rom. So i took the dialer.apk from the zip of santod's rom and copied it to system/priv-app in my phone and changed the permissions to -rw-r--r--. I can now use the dialer as an appa but it is not selected as default. I cleared default from settings fro stock dialer but still when i receive a phone sense dialer comes up.. Is there any way to change the dialer completely?

Thanks in advance
[One (M7) Q&A, Help & Troubleshooting] bdizzle1686:
The dialer that pops up when a phone call comes in is an app called telecomm I believe. If u go to santods port of iyapotas mod pack threads for the m7, download the mod pack , and extract EVERYTHING in the GPE folder , youll see whAt all you need for the full dialer experience. I believe theres dialer, contacts, telecomm, teleservice, and 1 other.
[Moto X General] JulesJam:
There is an Enable OEM Unlock option that is appearing in the Developer Options of the N6 and MX14 running 5.1 and if it is not checked, you cannot unlock your bootloader. If you unlocked via Sunshine or purchased a code for your device from the Chinese code seller, we do not know what is going to happen wrt this Enable OEM Unlock option for your phone if you upgrade to 5.1.

Until we do, it is safest to not upgrade and stay unlocked until 5.1 drops and the situation becomes clearer.
[Moto X General] fury683:
I don't think this is going to be an issue. People said in the N6 forums that they were able to unlock via fastboot without ever changing that setting in developer options. They hadn't even booted the phone into Android yet, just took it out of the box, put it in fastboot and unlocked.

I can't imagine the OTA would lock the bootloader, but who knows...
[Moto X General] JulesJam:
But others relocked after unlocking and didn't check the box then flashed something, ended up in a bootloop and were unable to unlock again to repair their phones.

Regardless, you cannot rely on what happens with a Nexus device. These MX13's were never intended to have unlockable bootloaders, whereas the Nexi were intended to have unlockable bootloaders.

I don't think it will relock the bootloader either. I am more concerned about those who relock then take the update not realizing that they will not be able to unlock again.
[Moto X General] fury683:
Except the Developer Edition units that are identical in every way to the retail versions, but the unlock code is obtainable.

Regardless, I will wait until the process is confirmed and use the same process that I did to update from 4.4.2 to 4.4.4. Reflash stock /recovery and a clean /system, take OTA, then reflash TWRP and flash SuperSU. I value my root to much to risk it.

Didn't intend to say you were wrong in my first post, just that people had the same thoughts when the N6 came out and it wasn't a problem. People freaked out when My Verizon updated a while back and it requested root permissions, too. It's an abundance of caution, I get it.
[Moto X General] JulesJam:
The GSM Dev Ed is not identical to the AT&T MX13. But still, so what? None of us know how this is going to be implemented in 5.1. We can speculate all we want but we will know for sure once it is released.

Rather than take the OTA, I would use Motorola Device Manager to upgrade - it leaves a copy of the fxz on your computer.
[Moto X General] JulesJam:
No, they could not have had the same thoughts as the N6 was always an unlockable device. You don't have to use Sunshine or purchase an unlock code to unlock the N6. So whatever thoughts anyone has had about the Enable OEM Unlock feature wrt how it would work with the N6 have nothing at all to do with this thread. The situations are totally different.

On the contrary - it has been quite a problem for a lot of people with N6's who relocked their bootloaders. That is well documented on the N6 forum.
[Moto X General] superkeest:
Why would I relock my bootloader to take the OTA? Why would I relock for any purpose?
[Moto X General] Saythis:
Running the soak test of Android 5.1 and there is no Enable OEM Unlock option on it..
[Moto X General] athulele:
The option only appears when you update to 5.1 with your bootloader locked.
[Moto X General] KidJoe:
Most would expect that for those Moto freely gives away the bootloader unlock code for (on their web site), should be ok and not impacted. At least that is what we hope, otherwise Moto could have a bunch (maybe a small bunch) of angry users on their hand

But the thought about a warning or caution was directed toward those with ATT, Republic Wireless, or Verizon (non-dev) units who either purchased their bootloader unlock code from the China seller (or middle man) when it was available, or used Sunshine in order to bootloader unlock... since those devices were not ever intended to be bootloader unlocked.... There is uncertainty over this new "check box" in the rom. Moto could leave it out for those models (especially since ATT and RW use their own roms, VZW could be a little trickier since all XT1060's, dev and non-dev use the same rom), and if so, how does that impact any user who had a code and didn't use it yet, or unlocked, and might later want to relock for some reason.

For Sunshine, the concern would be due to changes in the phone's bootloader, TZ, or other parts that might be included in the update which might close that exploited vulnerability down. Think back to how some of the early Root/WPDisable processes were said to be "permanent" only to find they were NOT when the next OTA came out and "un-did" the hack.

So yeah, as you said...
[Moto X General] JulesJam:
Some people relock b/c they think it is more secure if they lose their phone or it gets stolen.
[Moto X General] sseuorosal:
it leaves a copy of the fxz on your computer.
[Moto X General] JulesJam:
Motorola Device Manager does, yes if you upgrade using MDM, you will have a copy of the fxz on your computer.
[Moto X General] Icon000:
Any Updates on this situation?

It's almost been a month. Has anything new been discovered? I'd like to know if I can update to 5.1.
[Moto X General] rjcrystal199:
dont know about 5.1 but when i flashed 4.4.4 removing cm 12.1 on my att moto x it didnt relock my bootloader hope this stays same with 5.1 i used sunshine to unlock.
[Moto X General] KidJoe:
The 5.1 OTA for ATT, Republic Wireless and Verizon hasn't been available yet, so I doubt anyone has tried it.

The only ones upgrading to 5.1 right now are those with a bootloader that is unlockable via code from Moto's web site.

I haven't seen Jcase, Beaups, or anyone related to Sunshine make any comments.
[Moto X General] KidJoe:
Further... I asked in the Sunshine thread...

See JCASE's response -> http://xdaforums.com/showpost.php?p=61503326&postcount=3529
[Moto X General] breakthestatic:
I have an XT1060 (VZW), unlocked via Sunshine. I recently switched to T-Mo, and although the VZW build worked fine, I wanted Lollipop, so I flashed the stock T-Mo 4.4.4 build, and then sideloaded the 5.1 update. I am still unlocked and everything is working fine. I'm not sure if this totally mimics your situation, but I can say that the 5.1 update rolling out to T-Mobile doesn't affect the bootloader status for Sunshine unlocked devices.
[Moto X General] -Maverick-:
Exactly what I've done, converted my mother's Sunshine unlocked BL Verizon Moto X into a T-Mobile one. I'm waiting for the OTA instead of sideloading to see how things go. I'm guessing by your experience she shouldn't have any problems taking the OTA update to 5.1.
[Moto X General] ryusufu:
How did you convert it, I'm considering converting my att moto x to retail version. Btw its bootloader is unlocked
[Moto X General] -Maverick-:
Boot your phone into fastboot mode and manually flash the T-Mobile 4.4.4 update, TMO_RETAIL_XT1053_4.4.4_213.44.1.ghost_row.Retail.en.US_MR4_CFC. You'll need mfastboot to flash the system.img. Do a Google search for mFastboot-442.zip, that's what I used.

fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
[Moto X General] ryusufu:
Ok, after flashing the tmobile firmware, will my ota come from tmobile or att. I'm just curious
[Moto X General] -Maverick-:
I think Motorola is pushing the OTA updates for the XT1053, so you likely won't need to worry which carrier you're on, but I'm not 100% sure on this, so someone might correct me on this. Either way, it should be soon. :good:
[Moto X General] ryusufu:
Ok, thanks
[Moto X General] KidJoe:
Keep in mind the XT053 and XT1058 roms/radios are setup to support different frequencies.... With the XT1053 missing support for LTE band 5 and 7, which ATT uses in some areas.

Flashing the ATT XT1058 with XT1053 you should expect loss of support for those two bands. In areas where ATT is using those frequencies, you likely wont get LTE. In areas where ATT has rolled out LTE on multiple frequencies (for capacity issues), you might see decreased performance/coverage.

And because of GPT/Motoboot issues you might run into issues should you want to go back to the ATT rom.
[Moto X General] ryusufu:
Noted, thanks
[Moto X General] cicatriz63:
Now that the AT&T update is rolling out has anyone had any issues upgrading?
[Moto X General] ryusufu:
I don't have any issues, btw i unlock my att moto x bootloader using sunshine.
[Moto X General] rjcrystal199:
Everyone can relax now. lollipop update is not locking bootloader i have updated using sideloading OTA .zip not sure about mdm i dont think that the process would affect locking of bootloader. so everyone who bought sunshine can relax now and update to lollipop and root and other awesome things we do.
[Moto X General] Vivjen:
Band 7 still be working fine on 1053 FW outside the USA. Tested today (and many times earlier) in EU
[Motorola Droid 4] Careless_:
so I installed the latest CM12 Droid 4, and for some reason it's telling me I'm not rooted.

I was rooted in 4.1.2 using the razr utility for the XT894.

I first flashed original firmware

then did step 3 (root)

then installed safestrap using a 3.75 download link.

booted into recovery, installed latest CM12 nightly...

... but i can't get root access?

How do I restore root access now that I'm on 5.0.x?

Yes, I ENABLED root access in developer options. Still won't give root access.

Root Checker says:

Root access: no access

Su Found: system/xbin, system/bin
[Motorola Droid 4] moodroid:
Hi,

After flashing CM12.1 you need to flash SuperSU:

http://xdaforums.com/showthread.php?t=1538053
[Motorola Droid 4] Careless_:
Actually, I didn't have to do that. I just started over again. I did try flashing SuperSU by downloading the APK they have linked on the playstore page, through SafeStrap Install ZIP function, but it didn't work.

I went with the Razr Utility and installed 4.1 with wipe. then reinstalled root. then I went and installed safestrap 3.75, followed by lollipop.

all is well now.

I think the cable extension i was using was causing packet loss issues of somesort, as i can touch the cable end and it cuts in and out. But the root process said it was completed successfully. I think it just didn't go through the cleaning process and left files over that caused a root loss of some sort.

It seems to be fine now.
[Motorola Droid 4] sd_shadow:
Cm12 has it's own root, and is different from stock rom.

When device is in twrp recovery, it doesn't matter if Rom is Rooted or not.

Guessing it was a bad cm12 install, you didn't need to reflash firmware, just reboot to twrp, reinstall the Rom.

May need to redownload the Rom, and verify the md5 checksum.

To root Rom in twrp use

SuperSu flashable zip (UPDATE-SuperSU-v2.45.zip - 28 Jan 2015)
[Motorola Droid 4] Careless_:
if you look at my second post, I said I tried to install the SuperSU binary using recovery, and it did not do anything.

I just reinstalled the rom after wiping the partition to avoid any issues.
[8525, TyTN, MDA Vario II, JasJam ROM Development] kltye:
Just want to confirm that Black Shadow uses the "new" A2DP implementation (as mentioned here: http://www.pocketpcmag.com/blogs/in...t_bluetooth_a2dp_stereo&more=1&c=1&tb=1&pb=1). Ah, no more aliasing-like noise at the 1-3KHz frequencies...
[8525, TyTN, MDA Vario II, JasJam ROM Development] rgelfand:
Are you saying there is no more hissing noise?

How does it compare to black dymond 3.5 or faria's ?

Thanks in advance
[8525, TyTN, MDA Vario II, JasJam ROM Development] kltye:
Correct. I haven't used Black 3.5 or faria's ROMs, but compared to the modified LVSW and black 2.5 it definitely sounds better.
[8525, TyTN, MDA Vario II, JasJam ROM Development] Dishe:
Yeah, the official WM6 release has vastly improved A2DP drivers.

The older ROMs based on the beta and pre-release had very poor a2dp, worse even than WM5 AKU 3.

the new cooked roms are finally including the updated drivers.

For more information, read this thread:

http://xdaforums.com/showthread.php?t=310438
[8525, TyTN, MDA Vario II, JasJam ROM Development] hardcore:
This is not exclusive to Black Shadow. The good sounding A2DP has been around in the other newer WM6 ROMs as well.

Check out this thread:

http://xdaforums.com/showthread.php?t=308752
[XDA Assist] sam.nair:
I have a canvas gold a300. I want to create a custom rom for it ans hence i downloaded the stock rom. But i cannot find the meta inf file. What do i do and how should i proceed. Please help
[XDA Assist] jd1639:
Hi, thank you for using XDA Assist. There are a number of threads on XDA than can help you. Here are a few:

http://xdaforums.com/showthread.php?t=2195858

http://xda-university.com/as-a-developer/introduction-how-an-android-rom-is-built

http://xda-university.com/as-a-developer/getting-started-building-android-from-source

http://xdaforums.com/showthread.php?t=1798056
[Galaxy S II Q&A, Help & Troubleshooting] zb007:
Installed CM12.1 with gapps 5.1 on my samsung galaxy s2 I9100 but the play store does not work, please can you help me?

Does CM12.1 is too much for my phone?

If so, what the most advisable and later that is running at 100%?

If you can show me where I can download the necessary files and newer thank.

thank you
[Galaxy S II Q&A, Help & Troubleshooting] noppy22:
You probably ran out of /system space. Which gapps did you install? On stock partitions, you need a small gapps package to make it work properly. If you want a rom "running at 100%" you might be better off with a stable rom 4.4.4 or earlier as the newer lollipop roms are not yet stable(they still have bugs and/or missing features). Maybe not yet mature is a better way of explaining.

For gapps I would recommend CM GApps

For the rom I would suggest the 05/08 build as explained in the dev thread(if you want LP)

If you want a more stable rom I would try Slimsaber 4.4.4 by [MENTION=1228651]fusionjack[/MENTION]. It's awesome, but most of the major roms from kitkat and earlier are nice and stable and worth a look depending on what you want

Oh, and if you decide to go with slimsaber or another kitkat rom I use Minimal Edition GApps, but you can use any 4.4.x gapps you like
[Galaxy S II Q&A, Help & Troubleshooting] zb007:
Thank you noppy22

I appreciate the help, I will try with the minimum version 5.1. if not solve I will try with the second alternative presented me.

If possible and as I am new to do these things, I would like him to explain the steps to be as follows:

How have the full version of gapps and want to install the version that aconselhor me the CM GApps what I have to do?

How do I remove the version I have already installed?

If after not work how do I delete the android version 5.1 and gapps I have to install the 4.4.4 you advise me? The kernel that I serve?

My android presents these data at this point where only the play store does not.

Cyanogen the 12.1 s v.1.0-i9100

android 5.1

3.0.64 kernel-cm g7e7a10d

21/04/15

compilation date

21/04/15

compilation number

cm-i9100-userdebug 5.1 LMY470

c2e395cca3 test-keys

What changes should I make?
[Galaxy S II Q&A, Help & Troubleshooting] noppy22:
I'm not sure what you mean by full gapps. The smaller the gapps package, the better. The gapps are installed to your /system, so any other apps you want, you can install from play store(this is what I would recommend). If you want a bigger gapps package with apps like youtube or others you will need to repartition your phone, as you won't have enough room in your /system partition otherwise.

Here are two threads that will give you information if you want to do that. HERE and HERE. Just read carefully so you understand perfectly before you do anything.

To remove the gapps I would format /system. There may be other ways of just wiping gapps, not sure; you could try just flashing a new one over the old one, but I wouldn't recommend this. The only downside to formatting /system is you will wipe your rom as well. But you can just reflash it.

To go back to 4.4.4, just do a full wipe as you would to go to 5.1, using the recovery that came with cm.

Do you mean it works except for play store? Once you install the rom and small gapps you should be able to use play store
[Galaxy S II Q&A, Help & Troubleshooting] zb007:
Thanks again

I will do what you say.

Yes only the play store dont work.
[Galaxy S II Q&A, Help & Troubleshooting] zb007:
E: signature verification failed

Thanks for the help, as I could and was working well.

Now I have another of my milher equal and tried to do the same, put the 3 files on sd card

CWM

Cyenogen 12.1

Gapps minimal

That worked perfectly on the other.

This when trying to root with the CWM file that I used the other gives the error

E: signature verification failed
[G3 Q&A, Help & Troubleshooting] QA Bot:
Q&A for finally custom rom for lg g3 d858hk

Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.

Before posting, please use the forum search and read through the discussion thread for finally custom rom for lg g3 d858hk. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.

Thanks for understanding and for helping to keep XDA neat and tidy! :)
[G3 Q&A, Help & Troubleshooting] TommyBRSL:
Gracias, como hago para descargarla?, funciona mejor que la stock?
[G3 Q&A, Help & Troubleshooting] Hussien H-F:
network problems

I have this phone its good mobile ,but not all network band working here in my country

How can i open or unlock all network band in this phone ?? :confused:
[Optimus One, P500, V Q&A, Help & Troubleshooting] flaming homer:
I'm interested in reviving my T-Mobile branded Optimus T as an in-car wifi hotspot after inserting a data-SIM into it. Ideally I like to have it powered on and off with the car, meaning I would want to run it without battery.

Can someone suggest a custom firmware that does NOT support "offline charging" ? I'm hoping this would mean as soon as the car is powered on the phone will boot up - and I can use some kind of tasking program to automatically start wifi tethering

TIA
[Galaxy Tab Pro 12.2, 10.1, 8.4 Q&A, Help & Trouble] carltonbp:
TL:DR Anyone willing to see if their tab pro drains battery when fully powered off. Like overnight when you're sleeping or at work. Thanks

Hi,

I got a 10.1 tabpro back at the end of Jan. I thought it would be a massive step up from my Nook HD+ (rooted) but it's not. Not only is it slower than expected the battery life is atrocious. Samsung advertises over 2500 standby hours for their 10.1 tablet, I get 200. Also I get about 6 hour video, mp4 files, not 10 and I don't like a bright screen, I know companies exaggerate but this is daft. But it's the standby that's a problem, having to charge it every few days in case I want to use it is a big step down from my Nook.

It's been into Samsung repair 4 times now and I'm currently at a dead end.

Problem

It loses 0.5% an hour on standby even with wifi, gps, updates off etc

It loses 0.5% an hour fully powered off. Fully powered down. OFF, not on standby. Just to be clear ;)

Compare this to my nook with a smaller battery capacity which loses less than 1% a day. I've tried turning off other android devices (mobiles & tablets) and none lose battery over 12 or 24 hours when powered off.

Current situation

It's been in 4 times, it has been returned with a squeaky corner which they've failed to repair and the retail box is torn and tatty like they played football with it.

I've now been told

This doesn't address that wifi, gps, updates etc is turned off and drain whilst it's powered off. I responded 2 weeks ago but there has been no reply.

Feedback please

1. I've been all over the internet. I've tried greenify, I've tried battery calibration, there's a ridiculous amount of bloatware that I can't delete but I've reduced apps running as much as I can. Does anyone have any other ideas?

2. What's your tablet like, does it lose battery life when powered off? I've seen people posting on here about their 8.4 inch tabpro and they've put screen shots showing better standby battery life than my 10.1 with a much better battery capacity.

I've attached some screen shots, less than 3 days and it lost 33% doing nothing on standby.

I would really appreciate if anyone could feedback on battery life when switched off, is someone able to test theirs for me?

Many thanks,

Anna
[Galaxy Tab Pro 12.2, 10.1, 8.4 Q&A, Help & Trouble] carltonbp:
Is someone willing to see if their tab pro loses battery even when powered off?

Thanks
[Galaxy Tab Pro 12.2, 10.1, 8.4 Q&A, Help & Trouble] wellersl:
Uh-oh. I hope this is unusual and anomalous. I'm actively seeking a replacement for my HD+. I want to love it. I *SO* want to love it but it infuriates me that the browser crashes so often. Yours? Which ROM?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Q&A, Help & Trouble] carltonbp:
Nook is fine, It's the Samsung that's utter pants. Nook battery loses less than 1% a day on standby and screen is good. Surprisingly I thought the octo core samsung wouldn't be laggy but it is, it's not that much better than the Nook.

I have cyanogenmod 11 I think. Yes the browser crashes but that's partly because many sites are badly designed and web 2.0 is badly implemented and I use Dolphin because I like the format however it's a terrible browser for crashing. The new Guardian site I struggle with on tablets and mobiles no matter what browser for example.

Anyone willing to test their tabpro for me????
[Galaxy Tab Pro 12.2, 10.1, 8.4 Q&A, Help & Trouble] cloud71:
I'm actually on my 3rd day with my 8.4 it's 10:35 pm and I still have 35% left