yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] adrynalyne:
There are multiple licenses at stake here.

One is for use, which Google has.

One is for redistribution, which Google could not obtain. For some reason it was fine for Gingerbread, but not for ICS. For some reason, ICS throws in a wrench in the process.
[Samsung Galaxy Nexus] tannor:
adrynalyne,

mind if I ask, i am still new to compiling and have done it a few times, but just so I understand better. Are these the cdma proprietary files that we are talking about:

/device/samsung/toro/extract-files.sh

and that adb copies to

/vendor/samsung/toro/proprietary

I noticed when I tried to compile 4.0.3 I was not able to get those from google even before the changes, I had to first install a custom 4.0.3 rom, and then run that script to pull it from the working 4.0.3 rom to get them.

What I am curious about is if I had to pull them myself, where did others get them to begin with? was it a leak? Is that the main concern that we will not be able to get these for future updates? say when 4.1 comes out unless we can get a hold of these proprietary files somewhere we are going to have to deal with hacked prop files and hope it works?

Thanks
[Samsung Galaxy Nexus] adrynalyne:
Yes. The files they are discussing are pulled by extract-files.sh. That said, you aren't 'legally' allowed to do that per license either. So Google can't come out and say, "just use extract-files.sh".

There was a 4.0.3 leak a while back that a bunch of tards hoarded to themselves (for CDMA anyway). You can tell who the tards are by checking their Google Apps. Those 4.0.3 Google Apps that have xhdpi resources in them did not come from the Nexus S.

Anyway, that leak also ended up releasing proprietaries to the wild. Then it kind of spread. Now mind you, you don't "need" to use 4.0.3 proprietaries except the ones for Graphics, which Google did provide, (but may not anymore).

You bring up a good point. At some time, we will need updated proprietaries that we don't have. We will have to hack crap up, or have to wait for the appropriate OTA/leak with the right versions. As for GPU, we are set. A few mk mods, and we can use GSM ones.
[Samsung Galaxy Nexus] k.electron:
well... yes..

i guess what i meant was that as long as the basic device stays the same, the highly capable devs here and elsewhere will be able to churn out roms.
[Samsung Galaxy Nexus] adrynalyne:
Until there comes a time where the code doesn't work right because its no longer being tested for CDMA before it hits AOSP.
[Samsung Galaxy Nexus] bplewis24:
Man, I pray to Tebow that they will eventually be able to work out a redistribution licensing deal. I just want this headache to go away.

Brandon
[Samsung Galaxy Nexus] AllGamer:
just a piece of advice, for those with a CDMA model sell before it's too late ;)

no official 4.0.x upgrades in the horizon

and next year when AOSP 5.0 Jelly or whatever they are going to call it arrives, there will be no sources, and you'll only get a ported version from the GSM that might or might not work, that's assuming there's still DEV willing to stick with the CDMA model and Deving for it
[Samsung Galaxy Nexus] Rem3Dy:
The only thing that has changed is the documentation. You can still build aosp roms, and ota updates will continue to come. It may not be as simple as before but it is possible. If anything, Samsung will host the files on their site just like Motorola does for the Xoom.
[Samsung Galaxy Nexus] Baguett:
I'd not be surprised if the SGS2 would get an newer android version than us when samsung is finished putting TouchWiz in there...

Amateurish launch and seems like bad cooperation between Google and Samsung..
[Samsung Galaxy Nexus] silver03wrx:
Google says updates for the cdma galaxy nexus will still come directly from them. So lets hope it stays that way.
[Samsung Galaxy Nexus] miketoasty:
I'm guessing this is just all sarcasm.
[Samsung Galaxy Nexus] adrynalyne:
Fool.

LTE and CDMA telephony support is native to android as of ics. Nothing will change past what has already happened.

Stupid rumor mongers.
[Samsung Galaxy Nexus] Rem3Dy:
But he is a moderator with 500+ apps installed on his phone.
[Samsung Galaxy Nexus] edgeicator:
Pretty sure he's being sarcastic as this whole issue has been largely overblown.
[Samsung Galaxy Nexus] adrynalyne:
Read his post history. I think you will change your mind.
[Samsung Galaxy Nexus] AllGamer:
the sources codes for the CDMA model has been pulled from the build tree, you can verify that yourself for those that don't believe

here's an easy to follow guide on how to setup an ICS build, or use the virtual machine http://xdaforums.com/showthread.php?t=1386615

if there are any further updates it'll be from Verizon / Sprint themselves
[Samsung Galaxy Nexus] lrs421:
Aren't the build tree and ota's two separate things? Google has stated that the CDMA Nexus is still a Nexus and they will continue to provide ota's.
[Samsung Galaxy Nexus] adrynalyne:
Spreading fud again.

The only changes to the source tree so far was the removal of a lunch command. The device repos are still there. You can also view this on merged changes via Gerritt.

When something is removed from a repo, a git rm removes it from the catalog, as well as the source itself. This was not done.

PS--I have verified for myself with syncing my source with Google. Apparently you have not.

https://android.googlesource.com/device/samsung/toro
[Samsung Galaxy Nexus] imnuts:
You obviously haven't repo sync'd lately. device/samsung/toro still exists when you repo sync, and last I checked, that is the VZW Nexus...
[Samsung Galaxy Nexus] jcase:
I had no problem syncing & building for CDMA this morning.
[Samsung Galaxy Nexus] Rem3Dy:
You really have no clue what you are talking about :(
[Samsung Galaxy Nexus] AllGamer:
here is what i was talking about

http://www.talkandroid.com/87964-go...provide-direct-software-support/#.TzWL8ZUWVak

so, again any further updates will most likely be through the carrier rather than Google, while Google will still support the phone as a consumer product it will not longer be a Development Device

Even if you can still get existing sources, it wont guarantee next major release.
[Samsung Galaxy Nexus] mutelight:
You post an article from a week ago and paraphrase what everyone is already aware of to try to make a point?
[Samsung Galaxy Nexus] lrs421:
I think you should just let this go. Google has already stated that they will continue to support this device via ota's.
[Samsung Galaxy Nexus] eman3316@optonline.net:
This is the most confusing thread ever and I do not know what to believe.
[Samsung Galaxy Nexus] lrs421:
Believe the devs.
[Samsung Galaxy Nexus] imnuts:
All that article says is that it won't be fully supported via AOSP anymore. That means absolutely nothing about where the updates are going to come from, or the status of the phone. They have stated that it is still a development device, as there is more to development than just AOSP, like applications and accessories.
[Samsung Galaxy Nexus] lowandbehold:
What do you think it means for the future of Nexus devices on Verizon?
[Samsung Galaxy Nexus] mwalt2:
The same thing it means for future devices on Sprint. The Nexus S 4G has been out and supported by google for 9 or 10 months now if I remember correctly. Sprint is also getting the Galaxy Nexus as well.
[Samsung Galaxy Nexus] Rem3Dy:
nexus devices will continue. They will still get updates directly from Google, still get updates first and still ship with unlocked bootloaders.

Put your tin foil hats to rest.
[Samsung Galaxy Nexus] imnuts:
With all the major carriers going the LTE, which is a GSM standard, it should just make it easier in the future to get Nexus devices, only hopefully with full AOSP support once CDMA can finally be dropped.
[Samsung Galaxy Nexus] roymontante77:
I really don't see the big issue here? Why do some of you have so much hatred for the cdma version? This is by far the best phone I've ever had. I get excellent 4g reception everywhere... and do mean just about anywhere. Haven't had any bugs with this phone .. no data drops.. believe it or not great battery life.. no dropped calls.. hands down the best device I've ever owned
[Samsung Galaxy Nexus] gnarlyc:
So, I'm trying to get a good solid summary of how the situation is and how it most likely will be going forward. Tell me what, if anything, I have wrong here.

1) Not much has really changed for the near term. We still have fairly recent factory images. We are still getting OTAs. And building from source is ever so slightly more difficult than it was a few weeks ago, but it's barely worth mentioning.

2) Going forward...

a) We will get OTAs from somewhere. (I have no idea where this info is coming from though. I have not read it from Google, but I might have missed it. I'm just going by what people are saying here.)

b) We might get factory images, if Google is able to provide those. They plan to get them to us, where they can. (#1 below)

c) Building AOSP will probably stop working and no one at Google will try to make it work. Please correct me if I'm reading that wrong. (#1 below)

So, yes, the near term has not changed. It's the future that still bothers me. The plan for the future has changed. There's no doubt about that. If 2a is really correct, then we still have a supported phone going forward. That's great. That's helpful. I'm sure that some really smart folks will work out the whole building from source thing and keep it going as long as possible. That's not why I personally bought this phone though. I'm tired of building CM from source. I really wanted to build pure, Google AOSP. I really wanted to be able to build a basically stock ROM from source. So, I can still do that now. That's great. I'm more concerned about the changes to the plan.

I'm also concerned that we have few details about what happened and who to bug about it. I have seen nothing from Google that says something like -- "We were unable to come to an agreement with Qualcomm about licensing issues." OR whatever. Who can I call/email/send a letter to? I don't want to do it because I think it will help. It probably won't. Think of it as therapy for me. You might not understand. It might not make sense to you. That's fine. We are all different. We all have a different focus. My focus is what I've said here. Not how easy is still is to build from source. Or that someone somewhere says there will still be OTAs. I learned years ago that some very intelligent people disagree with me and believe things that make no sense to me. Just because someone disagrees with you does not make them stupid. But thinking that makes you arrogant. (In my opinion. I might be wrong.)

Sorry. I started with trying to get a summary and went off on a rant... I'd still like to get the summary right. :)

Citations:

#1 https://groups.google.com/group/android-platform/browse_thread/thread/10c8db7b1c893e1e?pli=1
[Samsung Galaxy Nexus] adrynalyne:
"c" sounds bad but its expected. Remember, aosp code starts out life as normal android code before closed source modules are stripped and it is pushed to multiple public gits. As long as CDMA and LTE work in retail, it should be fine in AOSP. I say fine, because Google isn't going to guarantee they didn't screw something up on CDMA/LTE code and if they did, it will not be fixed on AOSP's end.

For further explanations of this mess:

https://groups.google.com/forum/#!topic/android-platform/EMjbexyJPh4

It becomes quite clear that a documentation change was not the only change, but it is not as severe as we thought it would be (the sky hasn't fallen yet).
[Samsung Galaxy Nexus] gnarlyc:
So, you are saying that they take the proprietaries and make the code work with them to make an OTA for 'retail' and/or factory image, and then they strip the props and publish the source. As long as someone continues to ship a retail build, we should be fine. On previous devices that I've had... As soon as the official builds stop coming, it's been iffy on whether newer Android versions would work. We've been really lucky to have the CM folks and others who have worked around this. But these aren't pure, Google AOSP, not matter how many people insist on calling them AOSP.

You linked to the same post I did, which you actually pointed out to me in IRC a few days ago. :) (I probably need to read it a few more times anyway.)

As always, thanks adrynalyne. You have a deeper understanding of this stuff than I do, and I appreciate you explaining things in a public forum instead of just in PMs on IRC like some folks do.

Now, if you can tell me who to start bugging...
[Samsung Galaxy Nexus] adrynalyne:
Well, stripping out props is relative I guess, because they probably just don't use a retail vendor when it goes to AOSP so there was nothing to strip anyway. However, they do strip other closed source modules, as well that we have to contend with. Of course, GSM does too.

For people to "bug" about more info, it would likely be JBQ, because he has a deep understanding of the issue.
[Samsung Galaxy Nexus] twiztidninja:
ohh well verizon is still the best carrier
[Samsung Galaxy Nexus] 3devious:
Being the tallest midget in the room ain't all it's cracked up to be. ;)
[Motorola Atrix 2] Manases13:
I need help with the update, when you restart to begin the upgrade process I get the following error:

Finding update package...

Opening update package...

Installing update...

Verifying update...

asser failed: apply_path_check("/system/build.pro"

"423fc04f00baf98b985c9f8981c22496b5e4d213", "5f6cc954

c01cd27baa275c058bf621bf2711103a")

E:Error in /cache/Blur_Version.55.11.16.MB865.ATT.en.U

S.zip

(Status 7)

Installation aborted.

please help
[Motorola Atrix 2] cogeary:
Have you modded your phone at all? It seems like you tweaked your build.prop file.

Of you don't have a backup you'll have to flash the fxz.
[Motorola Atrix 2] Manases13:
ok, then I can flash with?:

Android 2.3.5 ---- Blur_Version.55.11.16.MB865.ATT.en.US

InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID28 5.zip

http://xdaforums.com/show....php?t=1396650
[Motorola Atrix 2] Moverf16:
RichLocation

I'm posting this here since I'm getting a similar error, except mine is with the update for RichLocation.odex

I originally rooted for the sole intent of deleting social location that was draining my battery. Before doing so, I backed up using Titanium Backup.

I've tried to restore it using Titanium Backup, but it just hangs up.

I found a XT860 stock files post with the Odex and Location, and reinstalled RichLocation, but it says it found an unexpected result.

Does anyone have RichLocation.Odex and RichLocation.apk they could send me?

I don't want to flash back to stock because I can't get RSD Lite to even recognize my phone, and I think if I put these two files (compatible with this phone) in the system/apps/ folder, the update will work fine.

Thanks in advance.
[Motorola Atrix 2] farshad525hou:
Yes, as long as you haven't updated to 2.3.6 flashing that should work fine.
[Motorola Atrix 2] jimbridgman:
This is why you ONLY freeze apps that are from the stock load...

If you can't get RSD lite working, you can't restore the FXZ.

You really need to, make sure you are on windows 7 ONLY..... It does not work well well with vista or XP, some have gotten XP to work, but not well. You also need to make sure you have the right drivers.

All of this stuff is in the n00b thread:

http://xdaforums.com/showthread.php?t=1396650
[Motorola Atrix 2] Manases13:
Thanks, I could upgrade to 2.3.6 after making falsh

I have it in 2.3.6 and Root:D:D:D
[Desire Q&A, Help & Troubleshooting] TKG26:
Im using Acesmod v41 rom on my phone and it works just great. ITs my daily driver.. But it seems recently when ever a go to try other roms i cannot get text messaging to work 100%. Typically the first thing i do with a new rom is text my own number to verify it works. Well it seems my message cannot do the round trip and i get un able to deliver message.. I can receive messages from my wife it seems so it does work. I texted using telus website to my phone and that works.

I have texted my self in the past as a test and it works. Any ideas why i cannot send my self a text anymore? Now when i go back to ACESmod v41 i cannot text myself anymore like i used to..

here are my settings:

Name: TELUS SP

APN: sp.telus.com

Proxy: 74.49.0.18

Port: 80

Username: <Not set>

Password: <Not set

Server: <Not set>

MMSC: http://aliasredirect.net/proxy/mmsc

MMS Proxy: 74.49.0.18

MMS Port: 80

MMS Protocol: WAP 2.0

MCC: 302

MNC: 220

APN type: default,mms
[Desire Q&A, Help & Troubleshooting] twisted_forever:
Check ur service center number in the sms settings.

MMS APN has nothing to do with texting failure.:D
[Desire Q&A, Help & Troubleshooting] TKG26:
Looks like i have the correct number

+16475800172
[Desire Q&A, Help & Troubleshooting] twisted_forever:
Why do u wanna text to urself?:confused: is texting to someone doing OK with ur rom? if u want to be sure of the sms is recieved, u have to turn on the delivery report. did u do that?
[Desire Q&A, Help & Troubleshooting] TKG26:
I have no friends... so i text myself...

LOL

Seriously i text myself anytime i flash a new rom, i also call my self as well. To make sure both are working sending or receiving... From time to time it seems my ability to send and receive texts is not 100%

So today i cannot send any texts to my self. But i have been receiving some from my wife and she has been getting some of mine.. But not all of the texts i have sent her.

So i text my self to make sure everything is working... in my case its not working.

I did not turn on that confirmation option. i will. but that is why is text myself. i know i sent it and would know i received it quit easily...
[Desire Q&A, Help & Troubleshooting] TKG26:
Any ideaS?
[Desire Q&A, Help & Troubleshooting] TKG26:
WEll just to complete the story, i have done nothing and it seemed to work its self out. All settings as i said where correct..

For what ever reason i can text myself again and have confirmed many to and from texts...

Why this seems to come up when ever i decided to flash different roms i have no idea. Im on an ICS rom now and life is good...
[Desire HD Q&A, Help & Troubleshooting] nigsy116:
Hi all,

I'm running the Absolution rom (V3.7) on my HD and can't get the speech recognition in Evi app to work.

All the other voice inputs app work (recorder, voice dialer etc) but Evi is the one I use!!

On the keyboard I can see the mic button but when pressed it comes up with a mic icon with a red line through it.

Any ideas?

(would post in dev forum, but need 10 posts!)
[myTouch 4G Q&A, Help & Troubleshooting] Hhwr1917:
For those who made new Box account last month using edited build.prop to gain 50GB upgrade is anyone else having problem logging on? Seems like it started today and no way am I able to logon via Box (v1.5.1.2) from MT4G even when logon credentials are valid and works via web browser from device and PC but not the app itself.

I clear the cache, didn't work. I uninstalled app and reinstalled, didn't work. I am guessing they are flagging the accounts same way they granted the upgrade as by reading device and manufacture string. Post here if anyone else is having issue or is it just me, which is very unlikely.
[myTouch 4G Q&A, Help & Troubleshooting] tw39515:
i didnt edit the build prop but had a friend sign me up on his touch pad. the app is working fine for me today on my mytouch 4g, not much help sorry.
[myTouch 4G Q&A, Help & Troubleshooting] sckboy78:
No problem on my end. I edited my build prop
[myTouch 4G Q&A, Help & Troubleshooting] Hhwr1917:
Well I still don't see any reason for me to not able to logon as data connection is enabled and active while password is valid. Only thing I can think of other than that is if it was disabled by Box admins

Storage: 19.7MB of 50.0GB (6 files)

Bandwidth: 22.7MB of 10.0GB (72 downloads)

Now I am not using their service excessively as you can see from stats above. Nor am I sharing any files that would violate their TOS as nothing is media related that would be any ways remotely considered copyright infringement. Matter of fact its all for XDA folks which is under GPL. I am sure I am flagged ATM by them as it won't allow me to logon via device even from another account and another device. Maybe they cross linked it and blacklisted the device IMEI when device manufacture/device didn't match. Thus flagging the account from logging in but who knows. All I know is I have no access which is kind of shaddy if you ask me.

Sent from MT4G-Glacier powered by HKM's GB2.3.X Enhancement Package v1.2
[myTouch 4G Q&A, Help & Troubleshooting] tw39515:
can you login via browser or on computer?
[myTouch 4G Q&A, Help & Troubleshooting] Hhwr1917:
Look below as its stated in first post.

Hmmm still no access via mobile app Box (v1.5.1.2) but before I couldn't even logon. So I synced with local /data/data/com.box.android/ and linked /SDCard/Box/ to it and its able to get passed All Files/Update but it won't update due to auth issue. As it shows offline status with valid connection, POS Box why disable me.

Sent from MT4G-Glacier powered by HKM's GB2.3.X Enhancement Package v1.2
[myTouch 4G Q&A, Help & Troubleshooting] tw39515:
oh well use something else, good luck unsuscribed.
[myTouch 4G Q&A, Help & Troubleshooting] ext1rpate:
I got a 50MB account by editing the build.prop as well and I was able to log in without problems. You might want to contact Box.com, they might be able to help you out as to why you're having problems logging in.
[myTouch 4G Q&A, Help & Troubleshooting] Amathgirl:
Problem=SOLVED

HKM here, so I contacted Box support and they didn't even respond to the ticket. So I took matters in my own hand and found the issue and even fixed it. So if anyone else having this same issue on XDA then let this be a reference.

Problem: Unable to login Box.

Symptoms: Offline and unable to sync.

Cause: Entries in hosts file.

Effect: Rx/Tx queries blocked.

Diagnosis: Finding manually and physically removing the entries.

Keep in mind this will save you alot of time if you do this on PC. But it can also be done from the device physically.

1) Go locate the file by following its absolute path below.

PATH: /data/data/hosts

SYM1: /system/etc/hosts

SYM2: /etc/hosts

2) You can adb pull the file to PC and view it in text editor or from File Manager in the device open it with its text viewer/editor.

3) In text editor search for entries listed below.

.box.

box.net

box.com

4) The intruding entries would look something like below.

127.0.0.1 box.net

5) Once you find it then just simply remove the line and search again for multiple entries if present.

6) When its all done just save the file by replacing it and restart the device to take effect.

Sent from MT4G-Glacier powered by HKM's GB2.3.X Enhancement Package v1.2
[Asus  Eee Pad Transformer Prime] Techie2012:
OK So I've been told that the "Official ASUS Thread - Users with BT/WiFi Fallout Issues" is ONLY for BT + WiFi issues.

We need an official thread to address the weak WiFi issues! After tons of threads, posts, complaints and returns, will ASUS ever going to admit there IS an issue and have it fixed? I'm receiving my 3rd Prime this week. I'll continue returning until I get one that works.

***NOTE*** IF YOU THINK YOUR WIFI IS "FINE" PLEASE DO NOT POST ON THIS THREAD. LET US USERS WITH WIFI ISSUES DISCUSS OUR PROBLEMS. THANKS!!!