yashsingh1/xdaforums huggingface dataset:
[EVO 4G General] supericexu:
My phone is HTC G7, and I use data2sd to get 1.5G rom space, now there is still about 1.2G left, but I also met the "invalid package file" problem. I can't find any *.apk in /cache, (root, with "ls -a"). But if I uninstall some apps, I could install or update other apps successfully. I could not use Link2sd for I already have data2sd and I guess it's not a problem of insufficient space, because I still have enough rom space.

Do you have any new solutions?
[EVO 4G General] sw99:
The problem is not the apps, its the /cache running out of space. I suspect that the app you are using cannot move the dalvik-cache files (and is really just a shortcut to android's app2sd - which is not the same as darktremor or link2sd).

in terminal us df -k to see how much space you have on each mount to confirm that there is little space in cache.

If you really have that much space in your apps mount, then I would suggest moving the dalvik-cache back to its original location (search for instructions, as the only way I know how to do it is by installing darktremor's app2sd). If you are still having problems, you really are limited to either partitioning your SD card and using apps2sd or link2sd or removing apps.

hope this helps.
[EVO 4G General] leebo:
I have been having this issue for a couple of months now - with a bit of a twist. After wiping my dalvik-cache, my apps began to sucsessfully update - except for Google apps.

I have no idea why just those apps, but going into settings/Applications/Manage applications, and selecting each app, then clearing that apps cache, allowed those apps to sucessfully update also.

I am thankful I did not have to resort to the above fix.
[EVO 4G General] dsample:
Any solution if not rooted?

I've just started to get this error when trying to update the Google+ app. The error is only happening with Google+, every other app I update/install works fine.

I haven't rooted my device, and I'm hoping there's a way to fix the issue without rooting?

Device: Nexus One

Rom: Stock Android

Version: 2.3.4

Although I couldn't see anything in the cache directories, I checked in /system/app and couldn't find any package that looked like it would be Google+.
[EVO 4G General] kf2m:
Uninstall Google+ then reinstall from the Market. Customized apps will do that.
[EVO 4G General] JCroese:
Thanks that fixed it for me to !, I am running MIU XJ (D2W) Rom on my HTC Desire. and just a week or two ago I started to get these invalid package file errors when I tried to instal or update an app (with the exeption that some app didn't give the error and just updated) after clear my dalvik cach throuh CW recovery all apps update and new apps install again. (even the google one's)
[EVO 4G General] pranks1989:
To add to what OP said in the first post:

There is a script 09dalvik in init.d which moves dalvik cache to cache and vaccum the DBs. Deleting that will of course help coz that is the one responsible for copying dalvik to /cache! do a dalvik-cache wipe after removing that init.d script..

PS: I tried everything and at last this method helped! Before my /cache was full and now it is 0.4MB/200MB
[EVO 4G General] khan.orak:
Okay now this is interesting.

I got a stock Nexus 7. Unboxed it and I had got the Play Store App updates for GApps only.

When I tried to update them, I got this notorious error "Package File is Invalid" in the middle of download.

Clearing cache/data didn't help.

Then I configured VPN profile and got connected to server. To my surprise, the download went without any error.

Maybe some problem with GApps in my country.
[EVO 4G General] RinCEWinG:
Refloating this post, because after 3 or 4 months with this issue "Package file invalid"....after flashing different Kernels and roms...maybe 10 times..... after clearing cache, dalvik,...... I FOUND THAT THE SOLUTION WAS IN THIS POST.

THANKS A LOT!

What I have realised is that in my DATA/DALVIK-CACHE folder was full of very old files. I deleted all of them (:silly::silly::silly:) and ForceCloses start. Reboot the phone, and everything is ok, and I was able to install more apps without getting "invalid package file" message!!!
[Droid X General] hoola20055:
Is there a way to get powerbar on my notification bar like I've seen a mod for on htc sense?
[Droid X General] lilpeezy23:
Try power control plus. Works well until a rom comes out with them
[Droid X General] strikeir13:
This should be on the second version of Obsidian, 2.0.2, that should be coming out sometime soon.
[Droid X General] hoola20055:
Power control plus is EXACTLY what I wanted. Best 2$ spent on market. Thank you so much. For real.
[Droid X General] ljbaumer:
Will be out with my release of my rom swag squad, that should be out in the next week or so for the droid2.
[Nexus S Q&A, Help & Troubleshooting] mcp2009:
Just got my nexus s and whenever I choose bill my t-mobile on the market it asks me to enter my name and address. It never did that on my nexus one, g2, galaxy tab, and etc. I don't mind entering my info but when I do it always says invalid address, I've tried entering my address multiple ways but it will not work. I'm running CM7 right now can anyone else try and see what it does for them?
[Nexus S Q&A, Help & Troubleshooting] Smokexz:
Same here! I never got it to work, I am going to wait til I get the new market to try it again.

Sent from my Nexus S
[Nexus S Q&A, Help & Troubleshooting] mcp2009:
Lol I googled it and saw your post on android central. Which ROM are you running?
[Vibrant General] mattyfatty182:
Hey!

I'm a tinker'er' by nature and wanted to try out a few different ROM's. I followed guides and installed ClockWorkRecovery, etc. Made a Nandroid backup and started flashing away.

Tried Nero and Auxura and decided that neither was for me. Great work, BTW. I know both of those ROM's use Voodoo and the stock ROM does NOT - I was careful to follow instructions when flashing between the two and disabled Voodoo before trying to go back to stock.

I booted into CWR and went to "restore" and did a restore based off of my Stock ROM...which seemingly went fine . Phone goes through the T-Mobile splash screen and is booted up now, but I cannot get the screen to unlock. It goes off, comes back on and is stuck on the lock screen no matter how many times I attempt to "Sweep screen to unlock".

I've booted into CWR successfully and did a "Factory Wipe" and then another Nandroid restore and same problem. Do I need to give this thing more time, or what? It keeps waking up, vibrating and then going back to sleep.

Any help? I kinda need my phone to work (partly why I'm going back to stock :)) Should I be following this guide: http://xdaforums.com/showthread.php?t=848737?

EDIT: Used the guide posted in this exact post worked great - thanks guys, I did read the Bible and that's what lead me to a correct "unbrick"
[Vibrant General] offdutyninja808:
If your nand backup is from stock 2.1, then that's your problem. You need to flash a 2.1 kernel.
[Vibrant General] oka1:
Disable voodoo (if you haven't) Then reflash with Odin Eugene's Froyo that does not brick, then flash (Odin) back to stock. That should get you back ok. Please look at the bible and stickys they have all the needed instructions there

Good luck
[Nexus S General] Menace II Society:
Source Link

WOW if this is true.. I will be highly upset..
[Nexus S General] phonex1:
I was excited until i read the AWS part. Was so hoping it mentioned ATT compatible bands. Sigh..
[Nexus S General] Menace II Society:
Well.. I feel your pain, Phonex1.

But as a T-Mobile Nexus S user.. I'm highly upset because of this. Even though it might be speculation on Engadget's part, I usually trust their word. And even the idea that Samsung would do this is upsetting as well.
[Nexus S General] ap3604:
Soooo...

Samsung has held back 2.3 from the Nexus One to help sales of the Nexus S

Samsung is holding back 2.2 from the Vibrant to help with sales of the Vibrant Plus

Samsung now going to hold back 2.4 from the Nexus S to help sales of the Nexus S Plus?

History indicates yes :(
[Nexus S General] diversificationied:
Hmm...looks like I may be returning a phone.

edit: This may just be the SLCD version of the phone. Even if it's not coming to the US they still run it through FCC approval.

I just noticed in that video, that nexus s looks mighty thick when he turns it slightly.....Nexus S w/keyboard anyone?
[Nexus S General] Menace II Society:
I won't lie.. I am really upset right now. I feel like throwing this phone and screaming out Samsung in a dramatic way. It's so frustrating I wanna laugh too.. lol.
[Nexus S General] distortedloop:
Seems to fit right in line with this link: http://androidspin.com/2011/01/12/b...samsung-is-holding-the-android-world-hostage/
[Nexus S General] Darrien13:
If this happens I will cry.
[Nexus S General] phonex1:
Hopefully Google will learn and broker a partnership with another company (preferably HTC) instead of Samsung. They already confirmed the random reboot issue with the NS; such refreshing news after SGS complaints lol.
[Nexus S General] onthecouchagain:
Remember that "slap in the face" many said Samsung/Google would never commit by releasing some sort of refreshed Nexus S2 or Nexus S+? ... Well, my face is getting ready.
[Nexus S General] Menace II Society:
Man.. if it's the Vibrant 4G I wouldn't care.. (No offense to any Vibrant owners)..

But this phone just came out a month ago.. Come on man.. What kind of **** is this? lol
[Nexus S General] irishrally:
I don't see what people are getting upset about. Who cares if there is a different color Nexus S coming out, and there is no mention that there will anything added to this version over what we have. If the only change is color and maybe SLCD screen then who cares? Wait, don't the euro NS already have SLCD? Either way, I highly doubt Google will be releasing a new Nexus phone before the end of the summer, especially with just an incremental update to 2.4. Even if they added HSPA+ that would not be enough to release a Nexus S Plus.
[Nexus S General] Menace II Society:
LOL

Definitely.. I don't know if I want to risk it and get a refund and wait to see what happens.. I still got my G2.. Ahh.. I got a couple days to think about this.. Hopefully some more information develops.
[Nexus S General] diversificationied:
I minor change doesn't require a new fcc filling....
[Nexus S General] Menace II Society:
Well.. it says possibly HSPA+ and 2.4

Basically.. sounds like Samsung is saying "oops.. we forgot this and that.. alright guys.. here is the phone with tis and that.. sorry you bought the other one.. now buy this one!"

I don't know.. it's just a slap in the face to me. It might not matter to you.. but it does to some of us.
[Nexus S General] irishrally:
It's probably just a Nexus S variant then that adds nothing new, like the Desire was for the Nexus One. Either way, I don't think google will be releasing this phone, Samsung will. I'll stick with my Google "dev phone".
[Nexus S General] phonex1:
Samsung seems to be trying to showoff as the biggest evil in cellular industry now. Stopping firmware updates (even on devices thought to be immune from this) and releasing similar devices. I bet by the end of the year Samsung haters >>>>>>>>>>>>>>> Apple haters :mad:
[Nexus S General] diversificationied:
So if it adds the HSPA+ radio, you're not gonna be upset?
[Nexus S General] irishrally:
I'd still prefer this Google Nexus S without HSPA+ (all speculation) over a Samsung Nexus S variant and tmobile printed all over it and slow updates. The networks can not handle a full 21Mbps or even half of that yet. My buddies download speeds on his g2 are barely better than mine. Once the network can achieve more I'll be perfectly happy maxing out my 7Mbps, and by then I'll probably own the Nexus dual core with HSPA+ anyway.
[Nexus S General] theinternot:
Hopefully some concrete info will come out soon... got till Feb 1. before my 30 days are up.
[Nexus S General] Androyed:
He's right though. If people here always do as they do now when the type number of a new phone is released, they must be sad all the time.
[Nexus S General] XPLANE9:
And you are surprised why? Look at sammys past android history, galaxy to galaxy spica, galaxy support dropped. Now, vibrant to vibrant plus, vibrant pushed to curb. Nexus s?
[Nexus S General] leerobson99:
For crying out loud, the nexus s is going to be supported by google. Samsung provided HARDWARE, they can't possibly **** this phone over like galaxy s. Why can't u ppl get it into your thick skulls. i9023 is a different variant of the nexus s. A color change, a different radio etc.

If this phone is shipping with 2.4, then that could also b a reason for the variation in model number.

Don't fret our phone WILL also get 2.4 as soon as it is available.

Patience guys.
[Nexus S General] ap3604:
You know I used to think the same thing about my Nexus One ;)

"Google will always make sure my Nexus phone will have the latest software"...

But now its already been over a month and Google seems to have dropped support from the Nexus One in favor of their new toy, the Nexus S. I wonder if the same thing is going to happen to the Nexus S next year when an even newer Nexus phone comes out? :rolleyes:
[Nexus S General] chaval:
Clearly they rushed GB in the NS for launch. Which has a lot of serious bugs.

If they dont have two separate teams woking with NS/N1 I wont expect a N1 update untill a the bugs on the NS are fixed.

Strange though, The GB roms for the N1 are nearly perfect, maybe they are implementing something else.

Funny, those GB roms for the N1 dont have the same issues as the NS, either crappy HW or poor NS specific dev(kernel, drivers, radio)
[Nexus S General] slowz3r:
Some things promised in GB didnt make it in so there may be truth to that
[Nexus S General] :
That's because GB was coded with the N1.

The NS was a clobbered port at the last minute.
[Nexus S General] Rusty!:
Next year?

This year without a doubt. Wouldn't be surprised if it was within 6 months really, given the NS is from the wrong generation.
[Nexus S General] chaval:
Interesting, any source on that?
[Nexus S General] laurentbon:
Interesting thread everyone but I am none the wiser. 4 days ago, I was about to buy a Nexus S from the Carphonewarehouse (I live in the UK) and now, I don't know what to do. Wait and see what happens and what the i9023? If yes, until when? Frustrating..

L
[Nexus S General] Androyed:
You have got to be kidding ME.

Oh, come on!

First of all, the Nexus S is supported by Google. Samsung doesn't have a **** to say about whether it will get updates or not. So comparing this with how it went with the Vibrant, is absolutely nonsense.

Second, that the Nexus One doesn't have Gingerbread now, doesn't mean it will get it later. The Nexus S is a reference model (don't know if that's the right word) for Gingerbread. How could it possibly be that when another phone comes with Gingerbread at the same time? Besides, the Nexus S isn't even released yet in a lot of countries. The United States is not the whole world. If the Nexus One would get Gingerbread now, it would be ahead of the Nexus S in most of the countries.

Third, @Rusty!, where have you read that? That there are dual-core phones coming in 6 months, doesn't mean they have to cut all updates for the Nexus S. There is no reason that that would happen. Do you think they are stupid? Of course they knew that there were going to be dual-core phones.

And last, as I already mentioned, this phone will probably just be the European version of the Nexus S. Why i9203 and not i9020, you ask. Because Europe will get a Super Clear LCD version. Maybe it will get some minor hardware bug fixes, and maybe a colour change, but that's about it.

First people were whining about notification-LED's and dual-cores (which is perfectly OK, but just buy another phone if you don't like the Nexus S. You don't have to buy it, and it doesn't have to be perfect because it's a Nexus, and because the Nexus One, in your opinion, was perfect), and know they are whining about a slightly different type number...
[Nexus S General] ap3604:
I would def wait to see how Google treats the Nexus One (original Nexus phone)

Google right now is acting like a**holes and withholding the gingerbread update from the N1 the same way that people HATE Samsung for withholding Froyo from the Galaxy S phones :mad:

The whole reason to buy a Nexus phone was to get updates ON TIME and not get dicked around by carriers withholding software updates but now you can't even have faith that Google isn't going to leave a Nexus phone for dead like they did with the Nexus One.

If they do this to the Nexus One then they are going to do this to the Nexus S as well. Right now Apple seems like a more trustworthy company than Google for software updates, and thats saying alot :(
[Nexus S General] jlevy73:
Not sure I entirely agree with what you said. The Nexus One will surely be the next phone google releases Gingerbread for. Around Christmas, one of the Google devs stated on Twitter that they are still writing the code and it would come in the next couple of weeks. At least for the next year (or whenever Google drops another phone) the NS will be first the first to get everything. Take a look at the "silent" market update that was pushed. The NS got the first and the rest of the people around the interwebs got via someone pulling the apk from their phone and posting it.

But as far the Nexus One getting screwed, I just don't see this happening. For GB to get pushed to any other device requires intensive carrier processing, crapware bloating, etc. The Nexus will get an OTA as soon as it's properly coded for it. Just my two cents on this.
[Nexus S General] ap3604:
I remember the Google tweet coming out on December 6th saying that the Nexus One won't get Gingerbread but it wasn't because they were still writing code. That'll be 6 weeks without even hearing a peep and probably 2 months or longer before Nexus owners get an actual update!

The whole argument of "Google needs time to write code" doesn't really hold water in my opinion since Apple has different phones with different parts and still makes sure that EVERYONE can get the update on time. It's not like they say "Oh lets make sure iPhone 4's get the updates first since they are the newer version and f#ck the iPhone 3gs owners!" the way that Google is doing this to Nexus One owners :mad:

No.

Apple makes sure that everyone can update all different phones at the same time REGARDLESS if there are different phone versions and different processors and parts used. Apple doesn't use the excuse "Oh we need time to code iPhone 3gs owners, wait 2 months and you might hear from us" and neither should Google. :mad:

Google is currently giving Nexus One owners the finger and will probably do the same thing to Nexus S owners as soon as a newer Nexus phone comes out next year...

(btw jlevy I respect you alot and this heat isn't directed at a great guy like you... only google)
[Nexus S General] meetagrawal:
Apple > Google in updates. It's absolutely ridiculous that they haven't updated for Nexus One. I have no reason to believe it will be different with the Nexus S in a year.
[Nexus S General] Naths:
surely this phone is the rest of the world version,the i9020 is for the UK and the US the 2 biggest markets,the i9023 is for the rest of the world with the slcd screen,the i9023 isnt fully available yet and as the nexus s is supposed to be the first worldwide phone with gingerbread thats more than likely why the nexus 1 hasnt had the upgrade,as soon as the nexus s is avaiable worldwide the nexus1 will be updated,probally the same will happen when the next nexus is released,but im sure most nexus s owners now will change to the new version when its released....
[Nexus S General] robstunner:
Except for the fact that apple restricts older phones from certain updates. Look at where the 3g is. Its thrown away and at&t was still selling them a few months back. Its not even getting 4.3 at this point with tons of newer and cooler things on the newer phones (3gs and 4). The 3gs didnt even get hdr camera update after a year in the market.
[Nexus S General] theimpaler747:
Please keep it friendly in here, thank you.
[Nexus S General] robstunner:
Apologies. Didn't mean for it.
[Nexus S General] RogerPodacter:
For everyone saying the nexus one is getting screwed, is there any proof of that? Has anyone actually looked at github repository source code and seen no activity for the nexus one ROM? I'd bet money that daily commits are being made to the nexus one source code directly by Google just like always . Has nobody checked that?
[Nexus S General] xanos01:
I back you up 100% I say the same dude its a European version check it on the FCC site it says European common. So relax guys.
[Nexus S General] meetagrawal:
The 3g was supported by updates for 2 years. Considering that's the length of contracts people are signing for those phones, what would be the problem with that? I want support for at least a year and a half.
[Nexus S General] Androyed:
Glad to see that there are some smart guys here. There is really nothing to worry, and that the Nexus One didn't get the update yet, is just because Gingerbread is a Nexus S exclusive for a while. The Nexus S is released only in two countries. Besides, Apple make the software and hardware themselves, and that's why they update faster. If Google releases Gingerbread for the Nexus S, doesn't mean it works right away on the Nexus One.
[Nexus S General] Anderdroid:
Geez guys. Geez.

First off. (Vibrant -> Vibrant+) != (Nexus One -> Nexus S) != (iPhone -> iPhone 4)

The Vibrant+ is a new Vibrant. It IS the SAME hardware with new software. The Nexus S is NOT even the same manufacture as the Nexus One. The iPhones are ALL Apple and ALL very very similar.

Complaining like the Vibrant users can complain is absurd.

The Nexus One is a last generation phone. Google will not leave it to die, however, they have no incentive to prioritize it as highly. They are working on Honeycomb. Why would they send their engineers to support old hardware and upgrade it to Gingerbread, when Honeycomb needs to debut as fast as possible. Also, the code isn't so easily interchangeable. The Nexus One is completely different hardware from the Nexus S. Not to mention... They're trying to sell the Nexus S!

As for Apple. They do things however they do things. Different phones DO have different features. The iPhone 4 DOES have more software features than the older iPhones. Apple chooses to update all iPhones at the same time, so in all honesty, the iPhone 4 users should be complaining because they would be getting their updates faster. Apple holds the updates from the iPhone 4 so it can release all the updates.

In the end, no one will be happy. I recommend getting rid of your smartphone and switching to an old camera flip phone if you would like to retain happiness, if you cannot find it in a smart phone.
[Nexus S General] ykphuah:
If its not European version it might be this:

http://www.samsunghub.com/2011/01/17/skt-will-launch-the-nexus-s-in-south-korea-in-feb/

Dunno why the phone that I am already using is still "under testing".
[Nexus S General] Rusty!:
Other way round, it was originally developed on the Nexus One, there were pictures of it long before anyone knew about the Nexus S.

Which might explain why it doesn't work right on the NS yet (the publicly acknowledged reboot problem for example).
[Nexus S General] mythamp:
I think Rusty is spot on with this, Gingerbread was developed before Nexus S phone was selected. Check out the interview of Matias Duarte @ engadget, They must have developed it in line with N1 till that time. They are allowing Samsung to milk some money before they release it for the N1 which would also mean that there are chances of less bugs.

I am just hoping that i9023 is an identical phone to the NS but with touchWiz.

Unfortunately I think the buzz surrounding the NS is also taking a nosedive like it had with N1, thus sales will also fall.
[Nexus S General] bergqvistjl:
If this is the case, why is the version of the phone we can legally and officialy purchase in the UK (i.e. not importing the US one), the i9020?