yashsingh1/xdaforums huggingface dataset:
[8525, TyTN, MDA Vario II, JasJam ROM Development] khammo01:
The safest way when going between ROMs is reinstalling. I use a few techniques.

1. Install CAB files from SD card. Then you just install them one by one by tapping. Installing from Activesync can be problematic memorywise as the CAB will copy down to main memory and then be deleted after installation. This can be an issue if you have too many apps to install at once.

2. Unless the new ROM has the same device ID, email settings really have to be manually entered each time. I experimented with workarounds but they simply don't work.

3. After you install all your programs, import registry keys containing your common settings. Before erasing the previous setting, do a registry dump and then search for and find those registry keys that contain the settings. Most (but not all) are in HKEY Current User. Be careful. Don't import stuff that might break the new ROM.

4. Copy files or shortcuts from old ROM to new one. Careful though - if you are going to copy directories, use Total Commander or something. SPB Backup and WM File Explorer will REMOVE the old contents of a directory and replace it with only the stuff you have in your new copy of the directory! Total Commander only updates the new items.

5. Unfortunately, the only way to REMOVE files or registry keys (short of writing a DLL file or fancy XML?) is to manually search and delete them. I think you could probably use Mortscript to automate this but not worth the time probably unless you are flashing every day.

Between copying certain files and registries, many of my programs end up 'pre registered' on the new system. (SPB time, etc.)

Actually, I make a cab file with my preferred settings and files. I just click and go. This covers pretty much everything except email. Unfortunately the program I use cost 89$... but when I consider my billable hours, it's worth the saved time over the long run.

I can get all programs + settings in place in about 40 minutes now.
[8525, TyTN, MDA Vario II, JasJam ROM Development] crazyC:
Actually, I am using visual studio 2005 and making the adjustments to the emulator image, whilst watching the registry in the remote registry viewer. Once have identified the keys, I export them as reg files and then simply import them into cabmanager.

Depends on if you have access to VS2005.

I am sure there is a simpler way, (and am happy to learn it) but as I have occassional access to VS2005, this was how I decided to do it. Am using the WM6 SDK as well of course.

Because I keep updating the Phone Alarm beta, I actually modified the cab for the VisDaPhone skin to include my modified icons, and also to install the PA export file. Just running that cab after installing Phone alarm, and then importing the theme etc works for me. I did roll it all into one on an earlier version of PA, so it all started as per my settings, but then there was a new beta......
[8525, TyTN, MDA Vario II, JasJam ROM Development] crazyC:
I reckon (thanks to the exchange server) I can be back up in twenty!

If I can sort out the O2plus setup then I will reduce that as well.

I keep a word document on my sd card with a step by step guide for myself with serial numbers etc and settings.
[8525, TyTN, MDA Vario II, JasJam ROM Development] x-online:
do yo mind telling what's the program name/url that woul dbe?
[Galaxy S3 Neo Q&A, Help & Troubleshooting] DDX100:
So,i have a SGS3 - Neo GT-1901l and since i had it,it worked perfectly without issues.

A month ago (i think) i flashed via oding SuperSU and TWRP Recovery.After that i installed CM12 (Made a nandbackup though ofc)

It worked perfectly till i noticed that once the battery reaches 50/40 or 30%,it starts to drain VERY VERRRY fast and it also randomly starts to draw some white lines on my screen and then it shuts down even if the battery isnt at 1% yet.I can only reboot then if i plug in the charger.I installed my Nandbackup again to get my default rom again and to check if i still have the issue,and yes,i do still have this issue : C

I always have the phone on the lowest brightness setting,flymode enabled,no bluetooth and no GPS enabled. Can somebody please help me?

If you want informations about the kernel,the build number and etc,just say it in a comment,i will post a screen then.
[Galaxy S3 Neo Q&A, Help & Troubleshooting] koroveshi:
I have this too. I'm on stock 4.4.2 and mine starts to drain fast when it hits 15-20%
[Galaxy Note 4 Themes and Apps] CasTTeLLo:
Theme Name : Levis/Denim

Current themed Apps : framework, systemui, secsetting, touchwiz, calculator, more to come....

Themer : CasTTeLLo / Sab Twone

Release Date : Soon.....

Screenshoots :

View attachment 3218714

View attachment 3218717

View attachment 3218718

View attachment 3218719

View attachment 3218721

View attachment 3218722

View attachment 3218723
[Galaxy Note 4 Themes and Apps] CasTTeLLo:
Installation and Download links

Installation :

-Flash via custom recovery (its recommended to flash over x-note black theme)

-Flash at your own risk...make a nandroid backup 1st for security reason

Download :

- I will uploaded by part/app at the moment

1. Calculator V1

2. TouchWiz V1

3. Setting V1

4. Home Wallpaper

5. Lock Wallpaper

6. Dropdown Wallpaper

7. Statusbar Wallpaper

8. Framework V1

9. SystemUi V1

10. twframework - in progress

11. incallui - in progress

12. contact note - in progress

13. Themechooser apk
[Galaxy Note 4 Themes and Apps] CasTTeLLo:
Gold premium version
[Galaxy Note 4 Themes and Apps] markusyeremya:
çok güzel sabırsızlıkla bekliyoruz...
[Galaxy Note 4 Themes and Apps] CasTTeLLo:
Installation and Download links

Op updated - post 2
[Galaxy Note 4 Themes and Apps] malybru:
Mod Edit

May I remind you of the XDA RULES # 4

4. Use the English language.

We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator. You're free to include your original message in your own language, below the English translation. (This rule covers your posts, profile entries and signature).

malybru

Forum Moderator
[Galaxy Note 4 Themes and Apps] CasTTeLLo:
Contact note
[Galaxy Note 4 Themes and Apps] CasTTeLLo:
Which one is better? Red or blue?
[Galaxy Note 4 Themes and Apps] sphinxjv:
Blue looks much better in my opinion ;)
[Galaxy Note 4 Themes and Apps] CasTTeLLo:
same as me....love the blue one....thanks....
[Galaxy Note 3 Accessories] ReeX:
So there it is. The majority of the headphones are made for Apple. No fully functional remote control with Samsung phones. Thanks to Apple, again.

Is there a well known list of quality in ear monitors with 100% Samsung (Note 3) compatibility?
[Galaxy Note 3 Accessories] tsabrakar:
I'm using Sony Ericsson MW-600 for few years now. I've used them on my galaxy S2 then S3 and now on my note 3.

They feature:

One of the best quality audio performance

Microphone and call answer key

Multipoint Bluetooth and A2DP for wireless music streaming

Compatible with Sony Ericsson handsets and other bluetooth-enabled handsets

3.5mm jack to swap headphone

I hope I helped.
[Galaxy Note 3 Accessories] ReeX:
Do they work using the jack pin or only in bluetooth mode?
[Galaxy Note 3 Accessories] tsabrakar:
Bluetooth only.
[Galaxy Note 3 Accessories] ShadowLea:
AKG Y23U.

- ultra small and light

- brilliant sound (5.8mm drivers)

- remote button with microphone for call answering, pauze/resume, and double click for next/triple click for previous track. Also works as shutterbutton if an app has the setting.

- clear microphone sound

- 3.5mm audio jack pin.

http://eu.akg.com/akg-product-detail_eu/y23u-black.html
[Galaxy Note 3 Accessories] ocujos:
Xiaomi Piston 2.1

Fully compatible with Note 3. Sound is AMAZING! Google the reviews.
[Nexus 6  General] stas333:
We are having 3 official versions of the android 5.1 showing up. LMY47D, LMY47E, LMY47I. Some say they are carrier specific, some say they are not, and others have no idea what is going on. So, let’s discuss all the versions here and why some may or may not think that each one is carrier specific.

My main questions to those that say they are carrier specific is, I though Nexus 6 was not carrier locked and can work on all 4 carriers just by swapping the sim card. If that is the case, the how can we have carrier specific updates? I guess in theory it can be related to the sim that we have in our phones, so then by changing the sim from one carrier to another we will need to/offered the other software version?
[Nexus 6  General] mgerbasio:
There was a thread pointing to a twitter from someone at T-Mobile that explained this. As I understand it, Google changed the way it handles the minor network tweaking carriers need to make for their network and SIMs. Any OS would work with any phone but the carrier specific version will work slightly better. They can't make any changes to apps or the OS, just some network parameters. I'm oversimplifying but that's what I got out of it.
[Nexus 6  General] stas333:
hmm, i need to find that.
[Nexus 6  General] jbdan:
I'll assume because of the N6's "all carrier compatibility" they have released carrier specific optimizations in their different builds. Unfortunately, and in my opinion, Google caved with the N6 to get better sales. It is what it is and I'm just thankful I have a phone that I can still do as I please with it. It would be nice, and thoughtful, if the Goog would release official information on what the heck they are doing with these different builds.... is that so hard?! :p
[Nexus 6  General] crypt0kiddie:
So does anyone know which one matches which carrier?
[Nexus 6  General] stas333:
if its carrier specific, D is sprint, E is verizon, M is t- mobile.

edit, since canada is getting version D right now, D must be just general. Who knows. lol
[Nexus 6  General] crypt0kiddie:
So nothing specific to AT&T yet? Just curious to try a carrier specific one and see if data is faster.
[Nexus 6  General] 02840:
Try these...

http://xdaforums.com/showpost.php?p=59535507&postcount=90

http://xdaforums.com/showpost.php?p=59535608&postcount=92
[Nexus 6  General] sykopompos:
Not so much. 47e brought in new camera proprietary binaries too so it isn't just carrier specific
[Nexus 6  General] westers035:
Can't be carrier specific, I am on 3 Uk and have the D variant.
[Nexus 6  General] RW-1:
I would weigh in and say that if a carrier makes a change needing a new build, it gets submitted to Google, tested and the changes only affect those with that carrier, likely due to SIM detection.

The fact that the phone has radios for all the carriers means that this can be possible, tweaks to a radio or band your phone may not use won't affect you ... and at the same time Google can toss in some tweaks across the board for all of us. I suppose that what makes it confusing is that while any of them can be flashed, they'll only push out the one to a carrier specific imei set, like E to Verizon.

For the normal user, they get an update that makes their specific network functionality better, and the others are not pushed for that, but may get the overall tweaks in the next update to their phone in general, or if before that there is a carrier requested tweak for them that requires a build release.

But we here, see all of this because we have that "wanting to have the latest build" mentality, the questions arise.
[Nexus 6  General] mikkelwe:
What was suggested was that every build would work but a specific variant would be slightly better. For example m would be better for t mobile but any variant would work. For carriers other than sprint, verizon and t mobile I don't know if there'd be any real difference.
[Nexus 6  General] mhseraph:
Has anyone on ATT received a 5.1 OTA?

If so, which one?
[Nexus 6  General] DebianDog:
I knew something seemed different about the camera. Photos in low light looked better to me.

Sent from my Nexus 6
[Nexus 6  General] buschris:
Exactly. But some will never admit it
[Nexus 6  General] phoenixus:
The real question is this:

Can someone on T-mobile who is on 47D or 47E see if they get an OTA update to 47M?

If the builds are carrier specific, would google push them based off the the SIM or the IEMI? It would have to be the SIM right? For people that purchased a phone through Google/Motorola and are using it on Verizon. Or switch networks, whatever the case may be.
[Nexus 6  General] knitler:
Admit what? If it it carrier specific then explain why E has Camera updates that D does not? What does that have to do with the carrier?

If everything was the same except for the Radio.img then I'd buy the carrier only thing, but there are more that's changed.
[Nexus 6  General] stas333:
i edited my post. D is not Sprint. It must be general version since Canada is getting it right now.
[Nexus 6  General] gee2012:
Because its not true, then why did i get the 47D version in the Netherlands Europe. Btw i also have Sprint and Verizon files in my firmware, so that tells me they are universal roms that contain specific (network) optimisations that will be triggered when using a specific carrier.
[Nexus 6  General] ak47nerd:
According to the T-Mobile Support page, the requirements to upgrade to 47M is that your current build must be LRX22C, so I'm guessing that those with 47D or 47E won't be able to get an OTA update to 47M.

I'm on T-Mobile with 47D, and I didn't receive any OTA update as of now.
[Nexus 6  General] stas333:
Wow
[Nexus 6  General] pauleandro:
Changelog

http://www.androidpolice.com/2015/0...0_r3-lmy47i-mostly-small-fixes-for-sim-cards/
[Nexus 6  General] patmw123:
Anyone know if the LMY47I boot.img is any different?
[Nexus 6  General] Intub8:
These google weekly's are starting to get confusing. I just switched back to build E on ATT today. Does anyone have anything to report on L yet?
[Nexus 6  General] xdatastic:
FYI - It's an i not an L.

;)
[Nexus 6  General] Intub8:
thats how confused I am. :D
[Nexus 6  General] stas333:
LOL
[Nexus 6  General] Smallsmx3:
Is I newer than M? Does I have everything M has? I know Google said they would be unifying the builds at some point. On T-Mobile and M seems to be working well.
[Nexus 6  General] patmw123:
Supposedly LMY47I has some SIM card compatibility changes/optimizations. I think that may be it - I'm still waiting to see what all has actually changed aside from that.
[Nexus 6  General] :
It will be interesting to see if anyone on LMY47D/E/M gets an OTA to LMY47I.
[Nexus 6  General] xdatastic:
M is newer than I. M hasn't been pushed to AOSP yet so we don't know what changes there are.

I was built on 4th March 2015

M was built on 7th March 2015
[Nexus 6  General] Candy[MAN]:
What has been posted are the AOSP general changes. No device specific changes have been posted. I am more curious about that. They have updated both the Nexus 5 and 6 and I am curious to what device specific changes were done.
[Nexus 6  General] ZPaul2Fresh8:
LMY47D without EVER inserting a Sim.
[Nexus 6  General] NastyNeil:
Unify! Lol
[Nexus 6  General] PunishedSnake:
Same radio as D?
[Nexus 6  General] twatts723:
So if I OTA from 5.0.1 to 5.1 M, do I bypass whatever BS is being fixed from D-I? (what a confusing bunch of letters lol):eek:
[Nexus 6  General] TwelfthMan:
Null
[Nexus 6  General] buschris:
Just take what updates to your phone over OTA upgrade.
[Nexus 6  General] PunishedSnake:
I'd say get on M if you have tmobile otherwise d or I unless on vz then you are on e
[Nexus 6  General] twatts723:
Yeah I have T-Mobile. I was on D, then I downgraded to 5.0.1, and as soon as i went through the setup screen, OTA update popped up, so I figured that'd be the safest way to get on M (which was my goal to begin with). But that was last night. Its been downloading for like 8 hours and its only about halfway done so.... Waiting
[Nexus 6  General] Bgbird68:
USCC D version on my Nexus 6
[Nexus 6  General] discstu37:
This is all making my head spin, and to make it worse, I *think* I am seeing a battery life decrease since going from D back to 5.0.1 to M (I am on T-Mobile). 26% battery loss in 3 hours and 15 minutes with only 26 minutes screen on time. Now, I didn't wipe anything when I did all these flashes, so I am wondering if the downgrade to 5.0.1 might be the culprit. But I don't want to wipe and restore until I know what the *final* 5.1 build is going to be.

Side note, does a factory reset impact my device ID that is reported to Google for subscriptions, such as Google Music?
[Nexus 6  General] mgerbasio:
You can factory reset the device and you're subscriptions will be there when you reactivate the phone. as long as you add the correct google account.
[Nexus 6  General] thafngame24:
So i am a Nexus 6 user on AT&T... which of these 5.1 builds would be best for AT&T? Thanks
[Nexus 6  General] jbdan:
No one really knows. Other than you trying them to see what fits you best. The general consensus would probably be to run 47D
[Nexus 6  General] Intub8:
I just finished flashing I but its way too soon for results. Everything seems fine though.
[Nexus 6  General] Candy[MAN]:
I would go with the 47I. Reason is because they are calling the "I" release as 5.1_r3.

5.1_r1 = 47D

5.1_r2 = changelog was never released but I will assume it was 47E as the factory files exist on their website

5.1_r3 = 47I

I have a suspicion that there will be an OTA update for all 47D users to 47I.
[Nexus 6  General] Sydman:
I flashed 'I' last night as well, I am on At&t, and have seen no issues yet. Actually seems to run a little better than 'E'.
[Nexus 6  General] dodgebizkit:
Is there any way to go from D to a newer build without wiping/unlocking boot loader yet?(ie via OTA?)

Cheers

-----------------------<SiG>-------------------

My house phone is better than your iPhone.
[Nexus 6  General] manup456:
I posted this in the other thread flashed LMY47I last night and did some speed test at work today and this is the best I got out of all the 5.1 releases and I'm also on at&t.
[Nexus 6  General] manup456:
Just got this while standing outside so the single is super strong for me.
[Nexus 6  General] hanano17:
Your wifi is active on that one....the previous ones were cell though. Just saying.
[Nexus 6  General] manup456:
Well prob didn't go off fast enough but my last before that was 44+ so I'm pretty sure outside I can get a 46+ easy.
[Nexus 6  General] TheLoverMan:
battery issues here too, discharges way to fast
[Nexus 6  General] PunishedSnake:
Is that why I cant lock onto b12
[Nexus 6  General] Pecata:
Yep, it looks like we have to be on the LRX22C in order to get the 47M OTA...I am running the 47E and haven't gotten OTA yet either...
[Nexus 6  General] phoenixus:
Well I think that settles the discussion guys. We have carrier specific builds. 47D came first. Then 47E with a new radio/other stuff. Now 47M with the same radio as 47D. And T-Mobile says you HAVE to be on the 5.0.1 build to get the OTA.
[Nexus 6  General] gee2012:
I`am sure it will be posted on the Google dev. site. You can flash it manualy in fastboot then, or the OTA will be posted to be flashed in sideload.
[Nexus 6  General] knitler:
I find that annoying as I get great reception on T-Mobile with both 95R and 98R radios.

I'll wait til we find out what the break down in changes are So far we know

E has newer Radio and newer Camera binaries than D.

We know M has the same Radio as D.

I'd love to see what other changes we find in E and M against D
[Nexus 6  General] wschamps42:
I'm on the LRX22C build ( just downgraded) didnt get the OTA yet
[Nexus 6  General] TonikJDK:
I am sad. This is not the promise of the Nexus brand. The different camera is very telling, we are going to fragment now. Badly.
[Nexus 6  General] Xplicit84:
The end is near, let it be known

[IMG="deadcar"]http://i.imgur.com/SVICXRq.png[/IMG]
[Nexus 6  General] gee2012:
Not so grim guys, these firmwares are all posted on the dev. site. Its yours for the taking and flashing ;) I`am sure 47M will be posted too within the next day(s).
[Nexus 6  General] Pecata:
Scratch that actually it has been confirmed that we on the 47E build will also get the OTA. I sure hope Google also posts a factory image.

https://twitter.com/askdes/status/578658061914615810
[Nexus 6  General] trailblazerz11:
My guess is that they are not carrier-specific in that only E works for VZW or M only for Tmo. They are

carrrier-requested

incremental updates to address their different networks.

Internally, Google updates builds all the time. Verizon probably requested to M build to include network specific changes, as did Tmo for VoLTE on their network.

The updated blobs were just part of Google's incremental changes, but a new build is not enough to justify updating everyone D->E not on VZW, same for M.

These are different builds of the same version, only 5.1.1 with more incremental builds and fixes would require OTA for everyone.

This just points to the lack of synchronization over the release. Carriers wanted to make changes specific to their network at the last minute, so now we have different builds. Tmo was probably testing VoLTE with the older radio while VZW wanted to make radio changes for E which explains the radio difference.

TLDR: The changes from build to build are either minimal or specific to networks and eventually they'll get their crap together and we should have a single build for all on the next OTA
[Nexus 6  General] Xplicit84:
I'm just joking. Some people take this factory image stuff way to seriously
[Nexus 6  General] gee2012:
The problem is that nobody knows anything for sure, statements, hunches and speculations are flying all over the boards and Google doesn`t provide clarity. If however a firmware is posted on the Google dev. site we can all flash it.
[Nexus 6  General] wind784:
US carriers, scourge of the world? Discuss...
[Nexus 6  General] cougs:
Anyone received the update on att.
[Nexus 6  General] R4INS:
I called google phone support number. Asked about the whole builds thing. After much confusion on their end and waiting the only info I got from them was "the E build is newer". Then luckily got some more info which is kinda common knowledge that E includes a new radio which has fixes for cell radio, Bluetooth, wifi, and connectability. No info on the M update. Googles own employees seem to be as confused as us. For now, we should all run E I think haha.

In my opinion we should all run the newest build regardless. Say Verizon put their fixes in X build, then T-Mobile puts their fixes in M build. We all still benefit since its a multi carrier device. So Verizon's tweaks should also be present in the M build and so on until it all sorts itself out.
[Nexus 6  General] aa_chow:
I just go with the newest build on Google's factory image page, which right now is the E build. Seems to me the most "universal".
[Nexus 6  General] R4INS:
I would. Even if I'm not T-Mobile I'll probably flash M as well.

Just consider these build letter increases as fixes for different carriers. Doesn't hurt to run it, and it may run better for you carrier. I'm assuming everything in D is in E and everything in D and E will be in M and its all universal. ATT may release their FU build next if at all.

And if you think about it say the E build has Verizon tweaks they won't push M or any other build that doesn't pertain to them. So I'll just keep flashing system images as they show up regardless and may or may not benefit from the tweaks.
[Nexus 6  General] kingsway8605:
This. Google needs to clarify which build to use. There are legit people and companies buying nexus phones to develop kernels, images, and apps. Google needs to clarify.
[Nexus 6  General] david279:
Just use the latest factory images or whatever ota gets pushed to your phone.
[Nexus 6  General] Golf c:
Everybody should get ready for the Google nightlies!

Sent from my Nexus 6
[Nexus 6  General] PunishedSnake:
What do those camera updates do?
[Nexus 6  General] andrewhahalee:
GSM FTW
[Nexus 6  General] knitler:
Someone mentioned a bit better low light.