As you can read for yourself on this link here: https://motorola-global-portal.cust...2LzEvdGltZS8xMzQ1MjUzMDMzL3NpZC9KM21ITFkzbA==
Motorola explains 2 things needed to unlock.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[*]First is whether the device ships with a bootloader that is capable of being unlocked or re-locked.
This has been easily proven by running a strings.txt on the bootloader on the Atrix HD and that the commands
Code:
fastboot oem unlock
Code:
fastboot oem get_unlock_data
and
Code:
fastboot oem lock
are all enabled and work perfectly fine on the Motorola Atrix HD.
[*]Second is whether the wireless carrier that sells the device allows the bootloader to be unlocked, as each of our operator partners has their own policy.
This is where we are failing evidently. Straight from Motorola's site, the wireless carrier that sells the Motorola Atrix HD (AT&T Wireless) is the reason behind the Motorola Atrix HD not being unlocked via the "Unlock My Device" webkit.
Personally, I do not use AT&T and have not been in contact with them or used their stores to get my Motorola Atrix HD. There is absolutely no reason by the AT&T company should control a device that has nothing to do with them. This kind of thing is why I stopped going with Verizon Wireless, the locking of bootloaders. If I buy a device I should be able to do with it whatever I want, including voiding the warranty. A separate company that has nothing to do with me and my use of the Motorola Atrix HD (AT&T) has no right to tell me I cannot void the warranty on my device. I hope Motorola realizes this.
What can we do about it?
Nothing but sit back and complain via the internet. It's not like you can take back your purchase of this device. Feel free to contact Motorola on their bootloaders forums via http://www.motodev.com/ , their twitter page http://www.twitter.com/Motorola , or their facebook page http://www.facebook.com/Motorola
Thanks very much AT&Terrible!
I bet AT&T doesn't want to deal with the hassle of having Atrix HDs that have voided warranties and angry customers who don't get why they're not under warranty anymore because their BL is unlocked and they chose to ignore Motorola's warnings.
If some of these other boards are any indication, I can see why a carrier wouldn't want any bootloaders unlocked. Some people ruin their phones and expect their carrier and the OEM to take responsibility for their screw ups.
Sent from my MB886 using Tapatalk 2
sliderocket22 said:
I bet AT&T doesn't want to deal with the hassle of having Atrix HDs that have voided warranties and angry customers who don't get why they're not under warranty anymore because their BL is unlocked and they chose to ignore Motorola's warnings.
If some of these other boards are any indication, I can see why a carrier wouldn't want any bootloaders unlocked. Some people ruin their phones and expect their carrier and the OEM to take responsibility for their screw ups.
Sent from my MB886 using Tapatalk 2
Click to expand...
Click to collapse
+1
Sent from my HTC One X using xda premium
I will accept the idea of ATT not unlocking the devices in order to protect themselves
...if they get a move on it and push for some official vanilla updates
This ROM is pretty close to AOSP. In fact, it has some features I would like to see on AOSP. We're lucky that this isn't TouchWiz or Sense or LG's crap.
Sure Jelly Bean features like Google Now and enhanced notifications would be nice, but they should come as an update.
The issues I see are no toggles in the notification shade, touch screen sensitivity (registering taps vs scrolling), camera (though it's more than passable).
The circles widget and pop up, quasi widget functions of the phone, SMS, calendar apps are really value adds.
If you really want pure AOSP, get a Nexus or heavily supported CM device.
Sent from my MB886 using xda app-developers app
amccue said:
I will accept the idea of ATT not unlocking the devices in order to protect themselves
...if they get a move on it and push for some official vanilla updates
Click to expand...
Click to collapse
I think timely updates fall more with the OEMs rather than the carriers. Look at the Galaxy Note. It took Samsung a long time to release ICS for it; the AT&T version came shortly after. Carriers aren't sitting there making their own custom builds of software, but it'd be really nice if they did and could sidestep the OEMs completely.
dnorthington said:
This ROM is pretty close to AOSP. In fact, it has some features I would like to see on AOSP. We're lucky that this isn't TouchWiz or Sense or LG's crap.
Sure Jelly Bean features like Google Now and enhanced notifications would be nice, but they should come as an update.
The issues I see are no toggles in the notification shade, touch screen sensitivity (registering taps vs scrolling), camera (though it's more than passable).
The circles widget and pop up, quasi widget functions of the phone, SMS, calendar apps are really value adds.
If you really want pure AOSP, get a Nexus or heavily supported CM device.
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
I fully agree. With the cluster that was MotoBlur, this skin is a pleasant surprise. Not that I dislike Sense or Touchwiz, but those feel like their own operating systems. I think people wouldn't be so confused with Android if OEMs kept it somewhat similar across the board. As it stands now, unless you correct them, some people would think an Atrix HD, an S3, and a One X are all running different operating systems and I blame that mostly on Google for not setting better guidelines.
Sent from my MB886 using Tapatalk 2
Related
Good day to all,
Does anybody here think that the root access method found by djrbliss in thread http://forum.xda-developers.com/showthread.php?t=1234510 would work on Bell's Motorola XT860 4G ?
I'm pretty sure that, to the core, it is the same hardware with a different radio chipset... nothing like what the original DROID was compared to the Milestone in terms of hardware.
I currently own one that I unlocked and use on TELUS, and I must say that it is a very nice upgrade from the Milestone... it just needs root access so I can restore all those Titanium backups !!!
Share your thoughts.
EDIT : Used the following method, worked flawlessly on my XT860. http://rootzwiki.com/showthread.php?t=3714
Enjoy !
I'm interested in this too, as I'll probably be getting the XT860 for usage in europe
As per Team Black Hat, all current Motorolas running Gingerbread are vulnerable to this exploit. XT860 isn't an exception. I will likely root mine shortly (busy right now).
leobg said:
As per Team Black Hat, all current Motorolas running Gingerbread are vulnerable to this exploit. XT860 isn't an exception. I will likely root mine shortly (busy right now).
Click to expand...
Click to collapse
Welllll.... not that i'm scared to do it or anything, but let us know how it goes, if you ever get to that task on your ToDo list !
I just ran the root program on my XT860 from rootzwiki forums, and the process went through with no problems. Not sure if it actually worked, checking it out now.
Edit: Confirmed the root is working for the XT860. Yayyyyy.
Wow
There's no word to describe how awesome this new is.
XT860 owners, REJOICE!
SX86 said:
There's no word to describe how awesome this new is.
XT860 owners, REJOICE!
Click to expand...
Click to collapse
Does this allow for unlocking as well?
Yes, it worked, as expected. Glad we have root now. But be careful - without SBF, we have no secure way out of screw ups, plus altering stuff in /system will prevent us from getting updates. And with the totally broken camera I expect Motorola very soon to come up with one. They will likely break the vulnerability we use too. CWM is the next thing to look on now, as it will be the only way to update preserving root.
Lack of SBF is bothering me...
leobg said:
Yes, it worked, as expected. Glad we have root now. But be careful - without SBF, we have no secure way out of screw ups, plus altering stuff in /system will prevent us from getting updates. And with the totally broken camera I expect Motorola very soon to come up with one. They will likely break the vulnerability we use too. CWM is the next thing to look on now, as it will be the only way to update preserving root.
Lack of SBF is bothering me...
Click to expand...
Click to collapse
The lack of SBF is what's keeping me or making me hesitate to root my XT860...
On another subject, what's wrong with your camera ?
Most Droid 3 cameras look blueish. I've heard a few people complain about how slow/buggy the app is (crashes).
I personally haven't had a problem with it...
Raa_1 said:
Most Droid 3 cameras look blueish. I've heard a few people complain about how slow/buggy the app is (crashes).
I personally haven't had a problem with it...
Click to expand...
Click to collapse
Are you trying to say your's not taking blueish pics?? It is not only D3, but the Canadian XT860 is doing exactly the same thing. Unless I use 3rd party camera software that allows adjusting the white balance, everything comes out saturated with blue.
Also - how's the location tag working on yours - everyone so far confirmed pictures are stored with wrong location tag. Your's snaps normal pics and proper location tags? Maybe you run newer software?
I've not taken a "lot" of pics, but mine haven't been overly bluish, i'll admit.
I don't have location tags or services turned on whatsoever. I prefer to remain... anonymous? *chuckle*
It is a personal matter more. Here is a small example where differences can be seen:
1) Motorola XT860 with Moto camera:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2) Motorola Droid 2 Global (my old phone, which has far from perfect camera, but colors reproduction is not as bad):
The two shots have been taken seconds one after other - same lighting conditions.
Geo-tagging for those who use it is broken on the D3
Sorry for going off-topic - lets get back on topic - I have no doubt Motorola will be releasing an update, rather soon, that addresses the camera issues and given the root power, it is not difficult to mess up the phone and not being able to update it, given the fact there is no easy way back (SBF).
So - bottom line - be careful with the "new power"
Here a video taken from my XT860. I uploaded it from my phone and I hope it kept its original format.
http://www.youtube.com/watch?v=RPiAUKpfPn0&feature=youtube_gdata_player
You can clearly see the cool blue tint. In my opinion there should be some white balance option in the camera app but there is none.
Sent from my XT860 using XDA App
SX86 said:
The lack of SBF is what's keeping me or making me hesitate to root my XT860...
On another subject, what's wrong with your camera ?
Click to expand...
Click to collapse
I can also confirm that the exploit works flawlessly on the XT860, and can reaffirm the caution for playing around too much. I've messed up my contacts and can't recover it, since I relied on Titanium for backing up my system apps (oops).
On motorola upgrade page (https://supportforums.motorola.com/community/manager/softwareupgrades)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Looks like we might not get official ICS. Let's go CM9!
Further evidence that the D3 was released so they could use Droid 4(g)... so retarded. Thanks for the shaft, moto.
Sent from my DROID3 using xda premium
How does this prove there will be no ics for the D3?
Sent from my DROID3 using XDA App
I honestly wouldn't mind if they just unlocked our bootloader or gave us a better kernal
Sent from my DROID3 using XDA App
force1stiptopped said:
How does this prove there will be no ics for the D3?
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
Because it is a list of current phones that will be upgraded. The D3 is a current phone that is not listed, which means it will most likely not be getting an upgrade. However, no one knows for sure
I'm not sure it indicates anything. The D3 isn't listed in the list below either where all of the other phones are.
Hashcode said:
I'm not sure it indicates anything. The D3 isn't listed in the list below either where all of the other phones are.
Click to expand...
Click to collapse
This was my thought.. that top banner of text seems as more of a teaser for those who just purchased their bionic and razr to silence the people worried if their recently purchased phone is going to receive android 4.0.
The Droid 3 isn't listed on the page at all and obviously it exists.. so I don't think that upgrade page means a thing. I would assume those would just be the first to get it then other phones that are capable would have 4.0 implemented. Since the D3 is so similar, I doubt the bionic will receive 4.0 without the D3 being considered..
http://phandroid.com/2011/10/24/mot...-release-beginning-with-razr-bionic-and-xoom/
A few sites(check google) say that these lists are just motorola confirming which phones will get ics over the next few weels starting with the razr, bionic and xoom.
phandroid.com said:
Click to expand...
Click to collapse
Has anyone noticed that only verizon moto phones are listed? That cannot be a complete list, what about the photon? The atrix 2? I highly doubt this is a complete list of devices that can be upgraded. This is just for hype, companies like to do this so people buy their phones for the upgrade. If this is the complete list, our beloved Droid 3 has booted ICS already so there is no need to worry.
I'm probably going to thoroughly ***** a verizon rep out. I'm not big on ICS to be honest but the fact that they dropped this, then like 10 other phones in the few months following is terrible business practicing. My phone shouldn't be obsolete in 2 weeks.
I may just drop Verizon and goto Sprint while it's still got unlimited data. Tho that would probably leave me with $600 in termination fees. Good thing I got credit growing from things bigger than Verizon?
Page obviously needs an update on all the new phones, looks like it's 6+ months out of date so it has no real relevant information for new phones at all.
We will more then likely get ICS.
-smc
That's technology. You don't wanna be outdated get an iPhone. With the overclocks, custom ROMs, Hash working on ICS, and everything, why wouldn't our phone keep up? I mean it's got the hardware to be current for a while minus 4G.
Hey all.
Basically i just want to hear all your thoughts on your current devices, and what you think of the next device in that product family.
My thoughts.
My first android device was the Motorola defy which really sold android for me, the fact i could treat a phone horribly by accident and it not care was a really solid selling point. The developer community for it was really quite strong too, it even receiving CM10 before my current S2.
The original transformer isn't the prettiest, lightest and fastest tablet anymore (not that it was ever lightest SO MUCH GLASS) but it was and is my first tablet and still works amazingly today. Good job Asus.
My current phone is the Samsung Galaxy S 2 which i bought outright after everyone that had one giving raving reviews and a quick view of the forum showed a very active community. Little did i know the issues the developers faced to get the aosp roms working properly, it is not pretty and it is entirely the fault of Samsung and their hardware partners (I am looking at you, yamaha). I know this and love the developers for supporting my S2 so well, especially codeworkx whom has been moving devices lately.
I love the idea of getting the S3, but i would only be going for the larger screen and if all i want is the larger screen why not go even larger and get the Note 2? Especially after its drop test video. It is a tank of a phone.
The One X+ Kind of interests me with unlocked bootloaders etc. But the fact i have to flash the kernel separately to the ROM every time (or at least that is my understanding) would really annoy me.
After the defy i would rush to a unlocked bootloader on a Motorola. That and screen size were the only issues i had with my defy.
But my current plan runs out in December which is only a few months away and i would love some ideas on devices coming into Christmas season.
Currently i am thinking Note 2, but i don't want to have half baked aosp roms because of hardware support. Ideas?
And yes doing a BYO 6 month plan with my local carrier is an option.
How bout this one?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
orangekid said:
How bout this one?
Click to expand...
Click to collapse
Although super durable i am not sure it would have all the features i am after. And look at that screen, tiny!
HTC 100% of the time.
There are some really cool devs and contributors who have written apps and scripts that enable you to flash everything all at once, kernel included.
Sent from my EVO using Tapatalk 2
I have the SGSIII and the One X. In the case of the One X (not the One X+ but it's basically a refresh of the One X) yes, you do have to extract and flash the boot.img via your pc using fastboot and the flash the modules via recovery...not as bad as it sounds. It's a great phone.
The SGSIII not only has a bigger screen but a higher resolution than the SGSII. There are many ROMs for it and in the case of the US variants I've flashed ROMs made for the AT&T variant on my T-Mobile one. (The international version also has great development.)
Sent from my SGH-T999 using Tapatalk 2
tommytomatoe said:
HTC 100% of the time.
There are some really cool devs and contributors who have written apps and scripts that enable you to flash everything all at once, kernel included.
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Hey Tommy thanks for the reply, i take it your experience is from the EVO?
Thanks Babydoll one of my friends has the one x which i rooted/cm10ed for him the other day, it was an interesting look into HTC custom roms and i must say it is not overly difficult or anything. And i did see the scripts Tommy was talking about, they would be nice in easing the transition. How do you find the one x build quality? I heard it was hit and miss between users.
yay101 said:
Hey Tommy thanks for the reply, i take it your experience is from the EVO?
Thanks Babydoll one of my friends has the one x which i rooted/cm10ed for him the other day, it was an interesting look into HTC custom roms and i must say it is not overly difficult or anything. And i did see the scripts Tommy was talking about, they would be nice in easing the transition. How do you find the one x build quality? I heard it was hit and miss between users.
Click to expand...
Click to collapse
I have a HT23 which is one of the earlier batches and I have no issues. No Wi-Fi attenuation, no screen flicker, nothing wrong at all with my device.
Sent from my SGH-T999 using Tapatalk 2
Evo og and Evo LTE. Also had an Evo 3d for a brief time.
Sent from my EVO using Tapatalk 2
I also had the (original) Samsung Galaxy Note. I really loved that phone. I only sold it because the eMMC brick bug got on my nerves.
I still miss that phone. I am getting the Note II.
Sent from my SGH-T999 using Tapatalk 2
Babydoll25 said:
I also had the (original) Samsung Galaxy Note. I really loved that phone. I only sold it because the eMMC brick bug got on my nerves.
I still miss that phone. I am getting the Note II.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
That's the reason why you sold it? You could have flashed a safe kernel. Done.
Hi All,
I understand the differences between the Moto X sold by VZW and the Dev Edition in that the latter has an unlockable bootloader and more storage space but I have a few more in-depth questions about the device. I've called and asked Moto, but sadly I trust you guys to give me more accurate answers.
1. Will Android updated come directly from Motorola or will they have to pass through Big Red first?
2. Will VZW bloatware be on the DevEd?
3. Ay other interesting differences between the devices?
I don't really have any interest in rooting my device (tried to get some custom firmware on my PSP100 back in the day and bricked it), and want to (feel forced to) buy a phone on full retail to keep my UL data with promo pricing. Would this be my best choice? Thanks in advance for the help.
1. Will Android updated come directly from Motorola or will they have to pass through Big Red first?
I think future Android OS updates will more than likely be made available OTA by Verizon, unfortunately, despite it being a developer device. I've not heard nor read anything otherwise.
2. Will VZW bloatware be on the DevEd?
Not sure about this question, but I wouldn't be surprised if I saw bloatware.
3. Ay other interesting differences between the devices?
Other than the obvious unlockable bootloader, color scheme, higher storage capacity, there's nothing else that I know of to differentiate the developer edition from the regular consumer edition.
erik7970 said:
Other than the obvious unlockable bootloader, color scheme, higher storage capacity, there's nothing else that I know of to differentiate the developer edition from the regular consumer edition.
Click to expand...
Click to collapse
we get a cool inscription
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can you confirm the absence (or presence, hopefully not) of Verizon bloat? If I'm paying 650 for a phone I don't have any interest in tinkering with, I'd like to not have to worry about useless apps sucking up the system resources.
Also, on a slightly unrelated note, I've noticed that the Verizon demo units are a little sluggish compared to the ATT demos. I'm assuming it's either a fluke or the demo app VZW loaded on it. Can any Verizon users confirm the phone is just as fast as the others?
just root and then freeze or delete the bloatware with titanium backup
alex94kumar said:
we get a cool inscription
Click to expand...
Click to collapse
How could I possibly forget the most important feature of all?
---------- Post added at 12:17 PM ---------- Previous post was at 12:13 PM ----------
tkdftw said:
Can you confirm the absence (or presence, hopefully not) of Verizon bloat? If I'm paying 650 for a phone I don't have any interest in tinkering with, I'd like to not have to worry about useless apps sucking up the system resources.
Also, on a slightly unrelated note, I've noticed that the Verizon demo units are a little sluggish compared to the ATT demos. I'm assuming it's either a fluke or the demo app VZW loaded on it. Can any Verizon users confirm the phone is just as fast as the others?
Click to expand...
Click to collapse
I don't think we'll know for sure if Verizon apps come pre-installed until someone actually receives their dev edition unit and lets us know. I personally wouldn't have wanted to deal with bloatware either, but since this model in particular does have an unlockable bootloader, rooting and removing these apps shouldn't be too much of a problem.
alex94kumar said:
just root and then freeze or delete the bloatware with titanium backup
Click to expand...
Click to collapse
You don't even have to do that. Just go into Apps and disable it. It disappears from the app drawer.
icase81 said:
You don't even have to do that. Just go into Apps and disable it. It disappears from the app drawer.
Click to expand...
Click to collapse
Are you finally allowed to do so even with bloatware apps? I think I vaguely recall not being able to accomplish this with certain Verizon apps on my Galaxy Nexus.
erik7970 said:
Are you finally allowed to do so even with bloatware apps? I think I vaguely recall not being able to accomplish this with certain Verizon apps on my Galaxy Nexus.
Click to expand...
Click to collapse
Yup. Everything disappears.
Sent from my Nexus 7 using Tapatalk 4
icase81 said:
Yup. Everything disappears.
Click to expand...
Click to collapse
That's great news. Maybe I won't need to root this device after all once getting...
UCU2AOA1 4.4.4 Fail!
First off Android 4.4.4 has been out since June of 2014 (thanks for the speedy update AT&T) wouldn't you think this would have been an update that fixes any previous issues and possibly improved upon? 8 Months later... UCU2AOA1 4.4.4
The camera does not make an audible noise and does not turn green anymore when in focus.
The gallery app has text overflowing if the album has long characters.
App drawer lags every time you scroll a page.
*Bloatware*
Mail - ATT Mail
AT&T Live
Uber
Remote Support GTFO out of my phone!
Also have a look at your application manager under all, you will see a lot of new things that were never there before and it's not just for the Android 4.4.4 update. Be sure to check out the one that looks like a white pacman ghost (Sorry forgot the name of it) NSA?
487MB of pure garbage!
Thanks AT&T for more bloatware and bugs when Lollipop has been out since November 2014 .
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm so sick of this crap that this is the last subsidised phone I'll bother with. Sadly, AT&Ts network is the best for me as far as service goes. There's no point in taking their phones, though. The meager savings are not worth the hassle.
I can't change from Dalvik to ART now. Anyone else have this issue?
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
aaronkemp172460 said:
I can't change from Dalvik to ART now. Anyone else have this issue?
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
Click to expand...
Click to collapse
Do you have xposed rinning? Of so, you can't do art with that.
No. I don't think I do. I looked in the application manager and there is nothing named xposed.
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
I shot myself in the foot when the rep convinced me to switch to an AT&T next plan. Now i'm paying full price for the S5 & the software is garbage.
morphfxf said:
I shot myself in the foot when the rep convinced me to switch to an AT&T next plan. Now i'm paying full price for the S5 & the software is garbage.
Click to expand...
Click to collapse
fwiw, if you didn't buy one outright before, you probably ended paying more than full retail for it over the lifetime of a 2 yr contract. probably.
and yes, locked BL is a PITA for those who want to play. it's nothing new though, and att apparently has a history.
C0derbear said:
fwiw, if you didn't buy one outright before, you probably ended paying more than full retail for it over the lifetime of a 2 yr contract. probably.
and yes, locked BL is a PITA for those who want to play. it's nothing new though, and att apparently has a history.
Click to expand...
Click to collapse
I think it should be illegal, they are infringing on owners of their phones. Not to their software and at their will. I made the sad sad mistake of picking up an unlocked att s5 and I'm on T-Mobile service since att phones work and I had an s3 running on 5.0.2 for months and loved it so I got this phone with intentions of running a custom ROM because that is what android is all about and after purchasing the hardware I should legally be able to use any software I'd like, not the previous service provider. Does that sound unreasonable?
Depends on the agreement made when buying the phone. Its all very on the second hand market because I'm not sure what the original contract states ... I would not be surprised to find very restrictive verbiage in the AT&T contract, whether enforceable or not.
The true solution is to look to the vendors selling open devices from the beginning and stay with them. Unfortunately this will almost always rule out true leading hardware devices as the prime carriers will lock them up.
Sent from my Nexus 7 using Tapatalk