yashsingh1/xdaforums huggingface dataset:
[Nexus S General] distortedloop:
It's a hold-over of the early DRM for Market apps. Marking it copy-protected kept you from copying the file to your sdcard, then refunding the app, then using the copy you got. It was lame and easily worked around once root and apps that took advantage of root to copy things came out. Seems pretty pointless other than to keep honest users honest.

It's not the developer that's keeping you from seeing it, it's on Google's server end. They haven't updated the Market server to recognize our phone's new build number, so it won't give us stuff that is copy protected to keep us from copying it.

Again, this is just stupid weak DRM, that doesn't stop pirates, and only serves to inconvenience non-pirates, because there's two ways around this if you don't want to wait for Google to fix the server (which might take a week, like the last update):

1) download the app on another phone if you have it, copy it with root explorer to your sdcard, then to your computer, then to the NS and install it manually.

2) edit your build.prop file to a version number that Google recognizes. (search for instructions there.
[Nexus S General] kramer987:
thanks for the explanations and workarounds. i use Titanium Backup Manager as well so have all my stuff backed up too. but its not like anything got deleted through the update process. not sure why copy protected apps should be a concern, especially since google will just update the marketplace in a week as was mentioned. but i guess to those that intend to uninstall their app in the next week they might want to redownload it. or maybe i just missed the point lol. anyway, thank you again.
[Nexus S General] distortedloop:
I have to say that Apple did a much better job of applying DRM to AppStore apps than Google has with the Market. They build a digital key into the app that ties it to your device/account and it just won't run on any other device unless you crack the DRM. Now, like any DRM, it's crackable, and not that difficult to do it, but it takes a jailbroken (rooted) phone and some binary hex editing. Just slightly more difficult than on Android.

All that said, I don't support pirating of apps. Devs deserve to be paid for their work if they want to be, and I encourage everyone to buy an app, or hit the donate button, or whatever to support the quality devs. ;)
[Nexus S General] nyijedi:
Turns out the problem was a result of using an old version of Clockwork Recovery. Once I updated it to the latest version, it worked fine. I then reapplied the superuser .apk before rebooting, rebooted, renamed the install-recovery.sh file again, and flashed Clockwork Recovery through ROM Manager. Everything is now working. Thanks!
[Nexus S General] rossiscatch:
Would the patched Mms.apk work on other phones? Would somebody who has updated pull the apk?

Thanks
[Nexus S General] dplate07:
OTA Updates

Hi all,

I live in Singapore and have imported the Nexus S. Currently running on 2.3.1.

My main issue is, will i get the OTA update to 2.3.2, if im outside the US/UK?
[Nexus S General] dnts:
Update fails.. AccountAndSyncSettings.apk fails

I tried to apply the update with CWM and stock recoveries only to face the same problem again and again - the patch check fails on AccountAndSyncSettings.apk for some reason. I even pushed a 12-22-2010 version of that to the /system/app but didn't help.

A little concerning that this apk is broken regardless of the update...

Any help (like sending me the 2.3.1 apk) will be much appreciated.

Nir
[Nexus S General] Darrien13:
wait so on the 2.3.1 firmware you can see protected apps but if I update to 2.3.2 I wont be able to see them?
[Nexus S General] distortedloop:
Apparently so. Same thing happened with the 2.3.1 update. It took Google a few days (maybe a week?) to fix the Market with that one.

Grab the ones you want before updating! :D
[Nexus S General] Darrien13:
I just won't be updating till they fix this is unbelievable
[Nexus S General] distortedloop:
LOL, unbelievable only because of all the noise about it when they did it with 2.3.1 less than a month ago! I guess Google doesn't learn from its mistakes.
[Nexus S General] windmill_81:
Hi, I can confirm that with this update the browser has become usable and doesn't lag anymore. Another issue that seems to have been fixed is the sensors freezing after using a series of programs. To have more info follow this discussion on Google's developer forum: http://www.google.com/support/forum...ad?fid=126dea2a5c8ec44300049a745efa455f&hl=en
[Nexus S General] zorak950:
I think it's a conspiracy by Google to make developers stop using copy protection so they can deprecate the feature more easily. :P
[Nexus S General] distortedloop:
Nah, they don't leave it broke long enough on updates to have any real leverage with the devs for that.

If they want to deprecate it, a good place to start would be just remove the ability from future app uploads to the Market.

Problem for them is they have to have some sort of DRM scheme in place to appease the developers.
[Nexus S General] distortedloop:
Looks like it doesn't, or at least isn't intended to.

Check out this comment from Google employee on the bug report site for the rebooting issue posted 18 hours ago, so about the time the update had already started showing up for people:
[Nexus S General] nyijedi:
Well, I updated to 2.3.2 this morning, and the phone just rebooted on a call. This is actually the first time it's ever happened to me. Oh well. Hopefully the next update to fix this will be coming out soon.
[Nexus S General] nielsvg:
I tried the checkin way but still nothing?
[Nexus S General] zorak950:
From what I hear, checkin usually doesn't work for grabbing updates. The fact that it worked for 2.3.1 was an anomaly.
[Nexus S General] AtomicPC:
Custom ringtone bug still going strong. Noticed that my text message tone randomly changes.
[Nexus S General] assassin504:
Still wating in the uk, comon google
[Nexus S General] kenvan19:
Why not just flash the update.zip? The link has been provided.
[Nexus S General] huy85:
Updated to 2.3.2 manually no issues here.
[Nexus S General] nyijedi:
So the 2.3.2 update seems to have fixed the browser lag on my phone, but I've had 2 reboots on phone calls since installing it - something that's never happened to me before. One problem fixed, and another one crops up. I love Android, but I'm really starting to get sick of this. I don't talk on the phone often, but I'd kind of like for my phone to be able to hold a call when I need to make one.
[Nexus S General] KULASSE:
Hello I always find that the sailor browser lag it is better but always not ca.
[Nexus S General] sir topas:
Thank you for reporting this. Has anyone else experienced this after upgrading (especially if you didn't have the random reboot issue before 2.3.2)? I'm hesitant to upgrade now for fear of "infecting" my Nexus S with this problem that I've thus far been spared.
[Nexus S General] distortedloop:
I have not had a reboot yet since the update, but it's not even been out 48 hours, and I only had it twice total anyways, so hard to say.

If you're rooted, use Clockwork to make a nandroid of your system, then go ahead and update. If the update is worse than the current setup, just restore your nandroid back to 2.3.1...
[Nexus S General] AllGamer:
took a while but finally got my notification
[Nexus S General] lf2k5:
Just received OTA... VodafoneUK.

All looks peachy, awaiting 2.3.3...:p
[Nexus S General] assassin504:
For some reason its not a satisfying lol :cool:
[Nexus S General] raeef:
Yup , I got it via EDGE just few hours ago. I live in Jordan.
[Nexus S General] Darrien13:
Come on Google update the market :(
[Nexus S General] rajesh78:
Stock Browser is fast

Just installed the update, immediately i realized the browser works very smoothly as few other earlier stated.

Also i noticed the screen/graphics/display looks much crisper. any takers for this??? :rolleyes:
[Nexus S General] gobbledygoo:
Received OTA update notice this afternoon... Am in Canada on Wind Mobile
[Nexus S General] terra_droid:
Just got the update OTA while I was having a coffee break. Nice. :)
[Nexus S General] Epiksol:
Whatcha mean? I've had the updated market UI for about 2+ weeks now. Does this mean that some people are still rocking the old school marketplace?
[Nexus S General] vapor311:
hey are we still having to rename the install-recovery.sh to install-recovery.sh.old if we want to retain things like the updated market apk?
[Nexus S General] B3arfruit:
Finally got my OTA....

Believers b3ar fruit with their Nexus S.....:)
[Nexus S General] vapor311:
you must have installed the apk or have a custom rom, the nexus s standard GB does not have the updated market.
[Nexus S General] SupaDupaFly24:
WRONG. The Nexus S got the updated market about 2 weeks ago, I got it and I am not on a custom rom and I didn't install it myself.
[Nexus S General] distortedloop:
Maybe he meant how Google's not yet updated the server end to recognize the new build number on our phone, which means we can't see protected apps (again)....argh!

Yep, I am stock, but rooted. Got the new Market app magically show up last week sometime.
[Nexus S General] sagech:
Yeah I got my new market about a week ago. It was automatically updated, no notifications whatsoever.
[Nexus S General] rocketragz:
new system update

Just got a new system update. 2.3.2

Any word what this is? Samsung fix?
[Nexus S General] kenvan19:
I'm not really sure what you mean, you got another system update notification however it did not change the build number?
[Nexus S General] rocketragz:
That is correct
[Nexus S General] distortedloop:
Samsung provides no fixes on the Nexus S.

2.3.2 is from Google, and it's primary purpose was to fix the infamous SMS bug where you'd send a text message to John, but the phone would actually send it to Jane.

This is already discussed in several threads here. ;)
[Nexus S General] rocketragz:
I'm not saying I just got 2.3.2. I got the 2.3.2 update a long time ago. I just got a new system update and I was commenting that the build number did not change.
[Nexus S General] rocketragz:
I also heard that sammy and google were working together to push out an update soon to fix bugs. That's why I mentioned a samsung update.
[Nexus S General] kenvan19:
I've not heard that but its possible its a hotfix for the browser lag?
[Nexus S General] distortedloop:
If it has the same build number, are you sure it's not the same update?

You've already applied it?

Any chance you ran a logcat to get the url for the rest of us? We could compare to the original 2.3.2.
[Nexus S General] DKYang:
2.3.2 is the Android Version. The build number is GRH78C (for android version 2.3.2 on CM7). You're telling us the android version, not the build number.
[Nexus S General] onthecouchagain:
After 2.3.2, my gallery is a mess. When trying to open one picture, it actually opens another. Nice Google... nice. And the Gingerbread woes continue...
[Nexus S General] rocketragz:
Oops you're right. Yes obv I mean android version..
[Nexus S General] kenvan19:
That'd be my fault, I'm the one who mistakenly referred to it as the build number.
[Nexus S General] rocketragz:
Yes I already ran the update. I'm positive it's not the same update. I'm the one who broke the 2.3.2 update on xda month or two ago lol. And sorry I didn't get the url
[Nexus S General] NexusDro:
I'm confused. So what's your build number?
[Nexus S General] kenvan19:
2.3.2 just came out a few days ago. 2.3.1 came out a month ago. Sounds to me like you just got 2.3.2.
[Nexus S General] rocketragz:
Dammit you're right. Lol long day...

I guess this is old news?

Sorry for the confusion everyone!
[Nexus S General] kenvan19:
Yup, don't worry about it man.
[Nexus S General] rocketragz:
Ok yeah I see the thread 2.3.2 below my thread. Lol dammit I'm one of those guys now lol

Please delete this thread
[Nexus S General] shata:
Ya mine just got pushed the update 5min ago.
[Nexus S General] vapor311:
Well the new market is the slowest roll out in history then....
[Nexus S General] nyijedi:
I had this happen to me once before the 2.3.2 update. You have to delete the thumbnails from your phone and it will fix it. Unfortunately, I don't remember exactly where they're stored in Gingerbread. Perhaps someone else remembers, or you can do a search.
[Nexus S General] shrivelfig:
/sdcard/DCIM/.thumbnails
[Nexus S General] jivemaster:
I noticed the gallery problem too. Deleting from that folder doesn't fix it, neither does clear data under the app. Maybe I need to reboot.

Edit: yep, reboot fixed it.
[Nexus S General] vapor311:
Anything?
[Nexus S General] distortedloop:
Happens to all of us once in a while! At least now you see why we all reacted so oddly. ;)
[Nexus S General] knytphal:
Wasn't slow enough for me - I miss my old market app. ;)

I like my stuff compartmentalized and miss my tabs. :)
[Nexus S General] nicholasbgr:
I also got the notification today but I'm afraid to get the reboot issue as well like some people reported.
[Nexus S General] catchsomezz:
i'm new to android and the phone tweaking area, so forgive me if i use the wrong vocab.

i had 2.3.1, rooted, installed ROM manager. through ROM manager, installed CWM.

downloaded 2.3.2 update from google, renamed to update.zip, placed in root folder

started bootloader mode-->recovery. ROM manager (orange text) came up, installed update, reboot.

now im still rooted (weird? setcpu still works, just backed up everything with titanium backup) and everything seems to be working. ...what happened? was expecting to lose root.
[Nexus S General] supermartin73:
Ok,

So I followed and got build number:

bionix ns v1 (grh78) @ team whiskey

But still 2.3.1, whats wrong with this?
[Nexus S General] distortedloop:
You usually can't (or at least shouldn't) apply an OTA to a custom ROM unless the ROM author has specifically said you can. Generally the author will apply the updates as appropriate and issue a new ROM release.

Could that be your problem? I don't really follow the Bionix thread.
[Nexus S General] supermartin73:
The update as pushed through....then stalled (for an hour +) so I restarted the phone and it was back to normal.

I then went through the links on this thread to manually update, (I think the links are on page 4) followed the instructions and then the Build # as above was in place, the version is still 2.3.1

I assumed that follwing these steps would get me to 2.3.2, but instead its still 2.3.1 with a custom ROM?

This is following advice in this thread from posts 28-30,
[Nexus S General] distortedloop:
I don't know what changes Bionix makes the Google Apps in the /system partition. If they've deodexed and optimized like custom ROMs tend to do, then the patches in the OTA should fail because the files to mod don't pass the check before the patch is made.

We're seeing this with people who have pushed a single modded file to their system like maybe Google Maps or Gmail app. The update fails on them, though I think they're getting error messages.

I'm not sure you had a successful update applied, even if your screen told you it was. That's why (I'm assuming) your build number and version aren't changing.

Have you asked in the Bionix thread for advice on the update?
[Nexus S General] kenvan19:
The rom is built on 2.3.1 and therefore it is 2.3.1. You can't update a rom with an update from Google. For example, on my stock rom NANDroid I have 2.3.2 however, when I restore my backup for CM7rc15 (which I flashed after applying 2.3.2) it goes back to 2.3.1.
[Nexus S General] supermartin73:
Ok, thanks.

I was under the impression that it would update to 2.3.2 as per the thread, not do this 2.3.1 business....as I already have that!

Advice on flashing back to factory OS please?
[Nexus S General] kenvan19:
There is a thread over in development that has a stock rom NANDroid.
[Nexus S General] rahlquist:
Is anyone on stock noticing anything odd after this update. Specifically my wifes Nexus S the screen seems to be much brighter despite being on auto and also today for the first time ever her battery dropped to 24%. She normally uses about 50% from 7 am to 9pm. The only major change is she installed the update last night when she was prompted.
[Nexus S General] Random Select:
Just received my update via OTA.
[Nexus S General] kenvan19:
Everything went off without error?
[Nexus S General] terra_droid:
Mine did without nary a peep.
[Nexus S General] n1ggyn1ce:
well swype stopped swyping after the update.
[Nexus S General] Random Select:
The update went with no error. So far my phone is running fine with no problems.

I don't use Swype but I'm sure those who do would have to wait for a newer version or have to completely uninstall it and then re-install it for it to work. I know I had to do that with my Nexus One.
[Nexus S General] kenvan19:
Awesome, grats man. Enjoy not having to worry about having your SMS messages go to the wrong person hehe
[Nexus S General] Bspence415:
I just got my Nexus s today and its 2.3 how can I get the update by the way its Google special edition
[Nexus S General] distortedloop:
Read the whole thread...instructions on how to install it manually are in the first few pages of this thread, and there's another thread in this section that's got 2.3.2 update url in the title and it also has instructions.
[Nexus S General] cosimoss:
Does anyone know what bugs apart from SMS were fixed in this update?
[Nexus S General] Riyanweb:
I had to wipe data/factory reset my phone because after updating to 2.3.2 superuser stop working properly...
[Nexus S General] distortedloop:
Oh, no!

All you needed to do was reflash the su rooting zip...
[Nexus S General] xanadu.dm:
Having installed the update manually for 4 days now and everything keeps running smoothly. Browsing seems to have improved a bit, stability is just fine.

No dropped phone calls here although I haven't been calling very long lately.
[General Questions and Answers] dave79:
Hi there, if I hypothetically have 2 unreleased superphones at home for testing purposes available (Android 2.2).

I don't wanna go public of which model but it's runs on a tegra2 dual core, you do the guess work.

Now, I've had one of the phones for quite some time, but this week a new phone came along with FedEx. I'd like to make a copy of ROM/software unto the older phone. Are there any possiblities to do that? The hardware is identical.

I've successfully rooted both phones.

//Dave
[Trophy General] bartkozik:
Hi,

Is it possible to install WM6.5 onto the Tropy instead of the present version 7?

My company does not support its email exchange software for WM7 and I do not want to get the "outdated" HTC HD2. (Android or Symbian are also not supported :( ) Do you think it is possible to install WM6.5 until support for the new windows will be available?
[Trophy General] Avandor:
Not possible... get the HD2.
[Droid Incredible Q&A, Help & Troubleshooting] brandon2x:
Can anyone tell me the best rom that comes with an overclocked kernal built in? Looking for a kernal that has killer battery life also. I've been looking but i'm new to the dinc and am not sure what the best one is. I tried to install a custom ziggy kernal with incredibly re-engineered installed but it started rebooting every time it started up... Any help is appreciated. Thanks.
[Droid Incredible Q&A, Help & Troubleshooting] Hellzya:
Did you read everything before flashing ziggy's kernel? this is quoted from his site. did you have setcpu installed before you flashed?

NOTE1: If you’re having problems, please uninstall/disable SetCPU and any init scripts first. A lot of the issues are OC related. If everything works fine after doing that, slowly start over-clocking, if not, please post. Once the problem speed is found, report it, but most likely, it’s a voltage issue, not all phones/processors are equal. Since these kernels have snq-’s VDD sysfs interface, you can modify the VDD levels yourself. If there are any Java developers that would like to tackle the task of writing a program to assist, please do, I’ll help as much as I can
[Droid Incredible Q&A, Help & Troubleshooting] Hellzya:
oh and make sure you dl the right kernel its the bottom 2 on his page. i made that mistake earlier today. tryed loading a bravo kernel and my phone got stuck in the splash screen
[Droid Incredible Q&A, Help & Troubleshooting] unreal2k:
Incredibly re-engineered comes with Lou's #8 kernel, which is my understanding that it already has pre-configured screen off speeds, governor etc. It could be as simple as a wipe cache/dalvik that would solve your problem.

Other than that, i'm curious as to why you are looking into OC when you want killer battery? Those don't go together :confused:
[Droid Incredible Q&A, Help & Troubleshooting] brandon2x:
Ok. I missed the setcpu statement. Ill try that... and I want to oc because this inc wont play the only game I play worth a crap compared to my old x... homerun battle 3d... im hoping that will help...
[Droid Incredible Q&A, Help & Troubleshooting] unreal2k:
hmmm homerun battle 3d plays fine on my end. Check my sig for my rom and kernel, stock speeds.
[Droid Incredible Q&A, Help & Troubleshooting] pete_kowalski83:
chads incredikernel is probably the best for gaming, its oc-able..i actually run it some days on 1075 mhz performance, and get great batt life
[HD2 Windows Phone 7 Q&A, Help & Troubleshooting an] varunverma:
post the list of steps u took.

may b u r not following some of the instructions..

i got my hd2 unlocked in 1st attempt. its a fairly straight forward method..

jus' relax n try again...
[HD2 Windows Phone 7 Q&A, Help & Troubleshooting an] brianb2:
i just posted the steps i took and also i eve just tried hese steps (and still nothing )

1. Have Winphone developer tools installed. Download it for yourself

2. Connect Phone via USB

3. Wait till zune starts and sync completes

4. Verify that zune is not in a guest relationship

5. open a command prompt, type netstat -a to confirm that port 443 is not being used

6. open an admin command prompt, navigate to c:\windows\system32\drivers\etc\ then type notepad hosts and delete any references to windowsphone developer services

7. go to the settings on the phone and turn airplane mode on (so that the phone is forced to use internet via zune)

8. While the phone is still on the settings page, run Chevron with admin privileges
[HD2 Windows Phone 7 Q&A, Help & Troubleshooting an] Ra_Han:
my way:

1-restart computer safe mode and login

2-restart again and login normaly

3-plug the phone-start zune-start ChevronWP7.cer and try unlock...

ı don't know why but its works for me:)

sorry for english
[HD2 Windows Phone 7 Q&A, Help & Troubleshooting an] wholly1:
if u use skype shut it down, also turn temporary of all antiviruses and firewales...

it worked for me :)
[HD2 Windows Phone 7 Q&A, Help & Troubleshooting an] MilRash:
I have been experiencing the same problem. What I have discovered is that after several attempts I have just left the chevron in the background without closing it after the last fail for around 10 minutes. After that I have just thought that it is worthed to give it a try and then suddenly was saying that the phone is unlocked and instead UNLOCK button there was just RELOCK button. Hope that this will help you. The only thing that I have shutdown was skype and the chevron was run with administrative rights.
[HD2 Windows Phone 7 Q&A, Help & Troubleshooting an] miduman:
I'm in the same trouble, the first time that i installed all work fine at 1st attemp, then the device was blocking itself and never more i can unlock again, i tried all method explained here an in other sites i reflashed the phone again, but nothing it seems that my phone is in a black list or something.