yashsingh1/xdaforums huggingface dataset:
[Motorola Droid X2] Citizen_Snips:
No. The best thing I can seem to do is post a question on "google groups" / Google Mobile Help Forum....

I don't have time to sit here and write an essay, so I'll ask you guys to do it for me. Let's all come up with a well thought out, well rounded informative post for them to read. Save the questions for the conclusion.

I also think we should all post these questions, email them, just plain old flood them with a ridiculous amount of bootloader unlock requests. Let them know we want to be on the same level of development that samsung and htc owners are on. They have to give in sooner or later, don't they? We should probably also pass this info around to other motorola forums and get them in on the fun. A small group of users from one specific model probably won't convince them to budge
[Motorola Droid X2] ztotherad:
the bootloader is part of the hardware, so petitioning google isnt going to do anything, you guys need to keep up with moto-rizon, not google
[Motorola Droid X2] Citizen_Snips:
Call Moto then. The rep told me they had nothing do with unlocking them. I asked him specifically to repeat himself after he told me Motorola "couldn't unlock bootloaders if they wanted to"

I told him it was the coding of the phones partitions that were made by Motorola. He told me I was mistaken and Google would have to unlock the bootloader. It's up to Google, not Motorola. He made that more than clear. I'll try calling back later & record the call for you to hear.
[Motorola Droid X2] ztotherad:
google is all for unlocked bootloaders & development from 3rd party, so imho moto is feeding you bull****, bro
[Motorola Droid X2] Citizen_Snips:
No need to get that way, thanks.

Respectfully, how do you know that? What are your sources? I'd like to be informed as possible on the subject, so please, enlighten me.

Edit: Motorola was recently acquired by Google, so... wouldn't they have a say? At the very least...
[Motorola Droid X2] ztotherad:
bro, no disrespect and sorry if I made it seem that way. Google has acquired Motorola, but they're keeping their noses out of that. they just purchased Motorola for their patents.

and sorry I don't really have any sources right now, but let me see if I can look up some after work or in the next few days.

Hopefully someone'll come in here and see that and then back me up or you, I could be totally wrong, but this is what I read from other members in this forum, also I've read it on twitter through the major android forums and such.
[Motorola Droid X2] Maximinus I:
Google doesn't control bootloaders its that simple. Bootloader is controlled by the manufacturer and or provider. Samsung and HTC have allowed unlocked bootloaders for various devices this should disprove the moto rep. You should look outside this forum for info and should never listen to a phone jockey who gets paid to make moto look good.
[Motorola Droid X2] Stuckinabox:
It's great that their techs are so informed.

What actually happens is Motorola gets a copy of Android, loads it up with terrible code, then slaps it on the phone.
[Motorola Droid X2] ultravioletnanokitty:
That's a bunch of bulls***. Google may continue the overall development of the Android platform, but each device-specific build is entirely the responsibility of the manufacturer. The bootloader isn't even a part of Android! All you got from that talk was Motorola trying to get you to quit bothering them. Verizon and Motorola are the two parties we need to talk to.
[Motorola Droid X2] Triscuit:
Seriously, why the hell are "they" putting up such a fight!!!! We are completely aware that we fully void our warranty when we do stuff like this. Just give us the damn unlock code and send it out with an agreement that we acknowledge what we are doing with our phones. They will make many many happy people and maybe even keep us as Motorola consumers. But as many others have said...this will more than likely be my LAST Motorola device.
[Motorola Droid X2] Stuckinabox:
It's likely that it has more to do with forcing people to use the moto/verizon software. Don't listen to any of the reasons they give.
[Motorola Droid X2] Triscuit:
Gross
[Motorola Droid X2] CadenH:
Moto can unlock bootloaders. Don't believe their garbage. Google has absolutely nothing to do with this. You either spoke to a misinformed employee who really shouldn't be spreading false information or they just don't want to be bothered with the bootloader thing. I've stated before in other threads that moto has a terrible business ethic, all I've heard from them are lies if you even hear from them at all. I won't be supporting their company in the future by purchasing moto products. I've had a very disappointing experience with this phone and the lack of support that moto and Verizon have given. I've had this phone for a year now and I'm still stuck with it until February. Frankly, that's depressing to think about. It's unfortunate that moto deals with their customers this way. If it weren't for the consumer buying their products their company obviously wouldn't exist. Why wouldn't they listen to customer concerns instead of acting like a two year old and ignoring every one of is. I guess what I'm getting at is that given the information we need to make a decision about whether or not this company is worth supporting or even worth the time petitioning when they won't budge for customer interest.
[Motorola Droid X2] jsgraphicart:
Google doesnt control all the software for all devices. Theres a reason why Motorola has blur, HTC has sense and Samsung has touchwiz. Each company takes the open source software made by Google and makes it their own. Just like how all our ROMs are built. Developers take whats already made and tweak it. The only Android Software that is all Google is the phone they first release with the latest software on it, which has been the nexus series. Google doesnt control how the phones are made or how the software is developed for it. The locked bootloader is all motorola and verizons fault.
[Motorola Droid X2] ztotherad:
double gross-ocidity
[Motorola Droid X2] litetaker:
It is a blame game dude... I tried the lot Refer to one of my old threads in this section, about filing a BBB complaint against Moto. I called Verizon, and they said that they have nothing to do with the software and that it is something Motorola has to deal with. Then, I called Motorola, and they said that they have no intentions of doing any unlocking and I think they also put blame on the carrier, saying that if carrier permits, they will do so... And I believe I was answered by the Motorola Corporate Office and so what I was told must be authoritative... If not, then Moto is a ****ty AND shady company that you would rather not do business with...

And as far as I know and can tell, Google has nothing to do with anything here... It is either Motorola OR Verizon's fault. And I believe they are just making you run around like nuts... My advice (sadly) is to man up, ditch the Motorola phone as soon as you can, financially AND then flip 'em off for satisfaction (may be email customer support, or they call center and rant saying how they lost another customer) and never look behind. I AM NOT joking... This is possibly the fastest and best way you can move on to a better phone. There is no point trying to do anything with Motorola as of now...

One of the XDA members told me something that made the most sense... Moto manufactures their phones with the bootloader locked, and so no service provider will willfully ask them to remove said "protection" and so, the whole unlocking conversation never occurs and so the bootloader remains locked. Moto also obviously doesn't push for it... I don't remember the whole argument, but it made sense then. I'll update this when I find that post or recollect the argument... Bottom line, you are going to waste a lot of time, just like I did... :rolleyes:
[Motorola Droid X2] densetsu86:
I only disagree with one thing here. And that is with what you said Google has nothing to do here.

IMO Google is the main culprit. They don't enforce with carriers and manufacturers what can and can't be done. And they hide behind the opensource stance of android, saying basically its open source so they can do what ever they want. Yet for us it becomes closed source being screwed over. Locked and encrypted bootloaders should not be allowed.

So I'm more annoyed with Google than both moto and Verizon. Google has a really poor business model with android.

Now don't get me wrong out of the three major os for phones android is by far the best but they have by far the worst business strategy.

They are responsible for what the carriers and manufacturers are doing, they are to blame. As long as they are the primary owner of android even though its source code is opensource they are the ones behind the wheel not caring about what their passengers (carriers and manufacturers ) are thowing out the window.
[Motorola Droid X2] Maximinus I:
That's the thing Google doesn't own android. So it isn't like they can tell moto to unlock their bootloader or else. Android is free and open that's how we have cm and aokp. Blaming Google for bootloaders is pointless unless your talking about an android experiance device. Those are the only ones they may control. My point here is this.. blaming Google is pointless this issue is not Google's fault and there isn't anything Google can do about it for most device. Unless they make it closed :rolleyes: killing the whole point of android.
[Motorola Droid X2] litetaker:
I absolutely agree with you there. I too feel google should do way more (something like what MS did with WP7 and hardware standardization and prompt OS updates across phones) to defragment the Android ecosystem... But as others have pointed out, I really don't know what they can do, given that Android is technically open source so anyone is free to tweak and install it on whatever device they make...
[Motorola Droid X2] Maximinus I:
I really wish some people would actually learn about things before creating and responding to these threads. Half the people here don't even know what a bootloader does. They just know that they can't flash xyz rom because its locked. Learn a little bit and this situation explains why its moto's fault and no one else's.
[Motorola Droid X2] nicko6113:
only throwing this out there because i haven't seen a mention of it.

"Motorola Mobility, Inc. is an American telecommunications equipment corporation owned by Google"
[Motorola Droid X2] Maximinus I:
I agree with you it shows the benefit of a closed os. But at the same time that means no custom roms and you can bet all wp7 phones have locked bootloaders. With freedom there's trade offs. Android itself is free and open. You can for the most part get around some manufacturer's restraints and you have an open os. That's why you can jailbreak an iPhone but there's no roms. Ios is closed therefore short of debloating your stuck on stock ios. At least on android you can create another version. Its a battle really closed will always run better but not be customizable. Open can be customized but will never be optimized for every device. Of course the manufacturer is going to pick closed on android that means locked bootloader because then they can optimize android for the device. I've said it before and I will say it again we are a minority. 9/10 of android owners will never root or change roms. Therefore openness is not an issue for the big manufacturer. They will still make money.
[Motorola Droid X2] densetsu86:
But with moto we're more like ios a closed os because of the encrypted bootloader. And most of our roms are just debloats and rethemed. All but 3 and the 3 that have no blur are unstable, and incomplete. So our dx2 is more of a jailbroken ios then android.

Google has the copywrite for android so yeah they own it. Its there baby, they made it to be opensource but it is still theirs. Case and point if they truly don't then why in the hell does apple take them to court? Why is Google trying to buy patents to protect it? Its theirs. They allow people and companies to do with what they please but its still theirs.

They should have laid some ground rules though. Like not allowing companies to interfere with opensource ie not locked or encrypted bootloaders, can't block Google updates to it. Can't put on nonremoveable skins/bloatware.

Other then that anything goes. Opensource for people and companies have not been violated. Moto is violating opensource and Google just doesn't care. And now fir better or worse Google owns moto. It may be separate but its still apart of Google and Google still owns them.

Google is responsible for the action of its employees and companies. So yeah the blame is on Google for me. What moto does Google has allowed. A crime of omission is still a crime. Google may say we have nothing to do with them but they still turn a blind eye to moto's action who they own so its like Google saying "yeah to bad you're stuck with it" instead of restructuring the company and sending out unlocks for its customers.

They're trying to run it like Sony does with its companies bur what they don t realize is that Sony still pays attention to scea , Sony bravia, etc and still controls them and steps in when needed.

Google does not realize they are at the part where they need to step in and fix things. This business as usual should not he aloud to continue on it only reflects Google's stance on not giving a damn.
[Motorola Droid X2] Maximinus I:
Your still missing the point. WE DONT MATTER!! If we get pissed Google /Verizon/moto loose maybe a tiny percent of money. We are a small group of people on the fringe of the smartphone market. There is a reason these things are locked. Mostly idiot people would break there phones.
[Motorola Droid X2] densetsu86:
Trust me I know we don't matter. That is why I don't waste my time with moto or Verizon or Google petitions stuff. I know it falls on deaf ears. I'm just giving my stance, outlook, opinion on the matter and what I think it should be.
[Motorola Droid X2] Maximinus I:
I guess then I still don't know why your upset at Google for something they have no control of? I'm all for being mad at those responsible. To me this is no different than being mad at a dev for releasing a rom you didn't like. Google brought android to the world and the manufacturers are screwing it up. I guess we will just see things different.
[Motorola Droid X2] CadenH:
I don't think Google has absolutely anything to do with this. Keeping android open source means manufacturers can do absolutely anything they want (including lock the bootloaders) and Google can't really do anything about it. They create the os and that's it.

And as far as Google owning Motorola, that doeant really matter either. They only did it for patents, they could care less what Motorola does business wise, they keep the companies separate. This separation is necessary anyway to keep the manufacturers of android devices competitive instead of Google ending up like apple or Microsoft.
[Motorola Droid X2] zeb carter:
I've got an idea - everytime there's a story about a bootloader unlock, regardless of device or carrier, email the link to the folks at Motorola and Verizon. Ditto for info from Team Cyanogen Mod. CM seems to be the universal link to all devices. It doesn't matter if it's from XDA or other forums, just send it to them.

Just my $0.02 US.
[Motorola Droid X2] h_10:
agreed. the bootloader has nothing to do with android. android source codes do not have anything about bootloaders. bootloaders are part of the hardware.

google has stated that they are treating motorola mobility as a separate autonomous entity. but i don't buy that google doesn't have a say on unlocking moto bootloaders. if google wanted to unlock it, they would. at this point, they have no desire to. the carriers want moto to stay locked. google already has a line of unlocked, pure google devices.

it's really this simple. if you want an unlocked device, get a nexus. after the frustrations with this very issue on my X2, i got a galaxy nexus and am NEVER looking back. nexus devices from now on. i'm never going to be at the mercy of oems or carriers on os updates. and the dev support for the galaxy nexus is lights out. i will never buy moto again, period.

while other devices are struggling to get ics, i just loaded jelly bean yesterday. it's glorious.

f moto.
[Motorola Droid X2] freakboy13:
You can add htc to that list as well.

Though not as bad as moto still this whole attitude these carriers and cell makers have about this is just asinine.
[Motorola Droid X2] dragonzkiller:
Honestly most of this thread is just a bunch of things that we already know. This is the correct answer. Despite whatever you may have heard or believe, it is MOTOROLA who controls the unlocking of the bootloaders (with major input from Verizon). Motorola has unlocked versions of every phone they ever made so that they can develop for them. In fact they also have the unlocked SBFs and such for them also so that they can fix them.
[Motorola Droid X2] tech.kyle:
In an attempt to clear up a little confusion, the bootloader fires up first, takes inventory of the attached hardware, then hands off to the Android OS.

This is similar to the BIOS in your computer.

The way this works in a Motorola phone, when the phone first gets power, the bootloader starts up, sees an encrypted boot partition, and starts checking it to make sure it's valid (aka: not modified). It then decrypts the partitions and boots the kernel and the Android OS. All of that locked and encrypted stuff happens before your phone even THINKS about touching Android. For all the bootloader knows, it might be Windows Phone 7 that's on the encrypted partitions. It doesn't know! (Don't blame Google.)

When Motorola makes the software for their phones, they take the stock Android OS from Google, modify it to run MOTOBLUR (a set of so-called tweaks and "enhancements" designed by Motorola), compile it from source, then encrypt it with their key. When we flash it to our phones, the bootloader checks the key to see if it's valid. If it isn't, the flash fails. All the community wants is for Moto to either give us the key or to update the bootloader to not require that key. Many of us would happy void our warranties if it meant we could run a proper version of CyanogenMod on our phones.

Motorola has designed their bootloader to deny anything that isn't encrypted with their special key. They have released the source code for the Droid X2's Kernel, but the catch is that we can't DO anything with it without the key to encrypt it. Without the correct key to encrypt it, the bootloader won't accept it as a valid partition (and inherently will refuse to flash and/or won't boot).

The locked bootloader on our X2 exists

because Motorola put it there

. No one else. Motorola can unlock bootloaders on their phones if they want to.

The reason why the person on the phone told you they can't is because either:

He doesn't know how it works, so he fed you some BS to get you off his back

He doesn't care about you (the customer), so he fed you some BS to get you off his back

His supervisor told him to point the finger at Google to keep angry customers off Motorola's back.

All of the above

If you want to blame someone else too, blame nVidia. Their drivers for Tegra 2 are closed-source. That doesn't mean we can't make our own roms, it just means we're forced to use their un-tweakable proprietary drivers.

This is all Motorola's doing.

Never

listen to the salesman.
[Motorola Droid X2] Shpoople:
If you google unlock Motorola bootloader and look for the site change [dot] org there is a petition that has 11k signatures i havent looked at the others yet this may help get them unlocked
[Motorola Droid X2] zeb carter:
Verizon pulls a Motorola

I come to XDA several times a day and this morning there is a story about Verizon locking down their variant of the Galaxy S III. You'd think that Verizon and Motorola would learn their lesson.

Here's the link to the story if you missed it:

http://www.xda-developers.com/android/no-root-for-verizon-galaxy-s-iii-petition-started/
[Motorola Droid X2] uberjon:
I seen that earlier.. if page plus worked properly with LTE devices I would have bought an s3.. first month with x2 put directly on PP..

I suspect the s3 will have a larger audience by far complaining about it...
[HTC One X] shantusingh:
** Talking about this issue, on everything being stock (not even unlocked bootloader or rooted) **

I bought two days ago hox, and its gr8 but its speaker volume is average and playing some music videos like "rain over me", etc video songs it gives crackling/stuttering sounds at some places keeping sound enhancer on. And if sound enhancer is off then video songs volume gets low, feels kinda trapped :p . I really didn't expected this though... Wish someone forwards this issue to get fine in next update like sound enhancer gets corrected according to speaker and make speaker more louder and crackling goes away from every where or if anyone has any solution already??!

I have seen this issue with xperia u awell that its software is advanced because being sony, but the speaker is off low quality so a mix match gives crackling sound on loud speaker on many songs and videos because of its xloud feature being on, though its a lot cheaper than hox. I had xperia arc s it never gave any crackling sound and is too louder then hox. So Any helping answers please??

I just also want to ask another thing that the USB cable I got with phone does not charges my phone though shows charging.. but I get a pop when battery is low that "ur phone is giving more current than ur charger and the bettery level still drains.. I plugged my xperia u's USB cable to HTC's adapter and it connects tightly to phone's USB pin and charges my phone to full without giving any problem... So still is it fine if I keep charging this way as main is the adapter that gives correct current through the USB cable to phone right??

Would highly appreciate answers on these main things as for now please!!
[HTC One X] shantusingh:
No one

No one can Help?! :(
[HTC One X] andyl66:
Yes this is known, the next update should fix it (i hope). Mine crackles on some videos and I haven't found a way to stop it.

Oh and as for charging, just use the xperia one if it works. I use my hd7 charger on everything, my one x, my hd7, my iPhone, my Sony e reader. I haven't even unwrapped the official charger and cable :)
[HTC One X] shantusingh:
Oh wow thank you so very much.!!
[HTC One X] Crabitpig:
yip

Mine is fine soundwise.coredroid 3.5
[Galaxy S I9000 General] cezaralboiu:
Hi.i heard that samsung galaxy s has an ICS tw4 launcher,so i tried to install the mod on samsung galaxy s plus and it wored!

Download the attachment and install it from recovery!;)

[UPDATE] try the new update of TW4.5 fully working without lag.i tested it coulpe of weeks and it's working perfect! ;)
[Galaxy S I9000 General] KoKoOo^^:
Yep, it works but ot my CM9 it's lit bit laggy when scrolling the home pages in the app drawer it's Ok.
[Galaxy S I9000 General] gizmoichitzo:
The last time I used the TW4 Mod, I can't have 182DPI on my screen, and this is the reason for which I uninstall it.

and now, can we change the DPI of the screen without lose somethings?
[Galaxy S I9000 General] Dreiundachzig:
Do you have some screenshots?
[Samsung Epic 4G Touch] noobtoob:
I need someone else to take a look at this, please. I am not on a team, and a novice at best. I just finished cooking my first rom. Everything worked with exception of Contacts (and phone since they are connected). I need an experienced devs help.
[Samsung Epic 4G Touch] FrameCityJackal:
What did you take out/add to the rom for you to get FC?
[Samsung Epic 4G Touch] noobtoob:
see thread here, just took out a variance of these. Added AOSP email and exchange.

http://xdaforums.com/showthread.php?t=1386846&highlight=+info+removeable+system+apps

I am trying different variants, like re-adding the stock email and exchange, but not even a boot after i do this...
[Samsung Epic 4G Touch] locoboi187:
All AOSP system apps won't work with TW