Related
Hi everyone, this is my first post and I recently bought my first Android device (yes, yes, I'm a 100% noob). BTW, I also did the search (google and xda) for this problem, without results.
This is the story:
- I few weeks ago I bought my new Samsung Galaxy Tab wifi (p1010), with Android 2.2 Froyo, and it is not rooted or flashed with some rom.
- Search on the market for an official version of Skype, but no, at this time there was no one.
- Then, I find one on getjar, works ok, but only audio.
- A few days ago I uninstalled the getjar version an install another one, version 2.0.0.45-signed, from villanrom, announced with video support, but at the moment of accepted a video-call the application always fails and closed.
- After that, I uninstalled it, and wait for a new and better one.
- Here is the problem: I have tried with another versions (villanrom 2.0.0.47sig, xda-Froyo-droidrx, the first one from getjar, and others, even the "official one" 2.0.0.47 from the market) but always I got the same error "Out of space: Skype could not be installed. Free up space and try again"
- I can instal other apps (apk and market) without any problem.
- My Summary is: Program 438MB/1.87GB, Personal data 10.00MB/69.77MB, Internal memory 4.38GB/12.74GB", with NO External SD card.
Please, I need some help to resolve this problem, before doing anything drastic, like an hard-reset
Best regards and thanks
Jerome
[note. sorry for my regular english... ]
Please. I need some expert help with this problem.
Best regards
Jerome
You can try to run Titanium Backup, to see whether there still is some kind of skype installation on your tablet. If Titanium Backup can find something, then try to uninstall/wipe data/force remove app (all in Titanium Backup).
Another thing u could try is to use Root Explorer, and browse to data/app/ and see if there is still some skype in there (com.skype.raider-1.apk?). If there is, delete it. Also go to data/data/ and see if there is still something from skype there (perhaps com.skype.raider?). If there is, delete it.
Finally you could try to clear your dalvik cache. Usually that's done in clockworkmod, but as I'm not sure if you have that on your tablet, check here.
If none of that helps, I would backup some important stuff and then do a factory reset. Or better yet, put a nice new rom on there (either official or unofficial, no idea what's out there for the galaxy tab). At least go to gingerbread (android 2.3.x), or honeycomb (android 3.x) if that's available for your tab.
good luck!
PS; as for skype, i would recommend to use droidrx's mod. He's making great progress and most likely very soon there will be some kind of "final" and bug-free version.
Many many thanks.
My tab it´s not rooted yet (I think if I do that then lose guaranty)... I will try to do a factory reset or firmware update first... Only if that fail, then I will apply the root solution... BTW, wich one it is the better method/app for root a g-tab (with the un-root option included)??
Best regards
Jerome
Just did a 5 minute research, and apparently for some people there is already an official gingerbread update available. I would rather do that then a factory reset at this point. Gingerbread is a much better version of android than you have at the moment.
Rooting your galaxy tab is dead easy apparently, read here.
If you're thinking about installing a custom rom, see the Galaxy tab android development section.
Yep, but the update it's not available for everyone... I got installed the lastest version of Kies (2.0.1.11053_99), and it's shows "Current fw version = Latest = PDA:KB4 / CSC:KB4 (CHO)".. May be because my country (Chile).
SuperOnceClick looks fine, but with this issue
Note:
I have tried unrooting the device and rooting it again and this is not working. so this is to let you know that you will have to reflash the firmware to root the device if you unroot it again using this software and try to root until some one finds a solution
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=812367
Thanks again, I hope that's Gingerbread will be available soon for me.
Best regards
Jerome
Yea, that means that you can still get your tablet back to the factory state (including root), in case you wanna bring it back for warranty. Which is probably never going to happen anyway.
So my advice would be just to flash a gingerbread 2.3.4 rom, as i've noticed you don't even need to have root to do this. Who knows how long chile will wait with distributing a new android version?
no te preocupes!
EDIT: just be careful with one thing, i've noticed not all customs roms will work on your tablet since you have a wifi only tablet. keep that in mind when looking for a rom and make sure that the rom will be compatible.
Apparently I'm not the only one with this specific problem... It's look like some bad install/uninstall process with the "VillainRom" version on the GTab.
Google search:
villainrom Skype with Video Support for Various Devices... #55
(Sorry, but the system says that I'm too noob to publish external links.. )
Sadly, they have not released a solution yet
Best regards
Jerome
EDIT: Searching a little bit more, find this:
http://forum.xda-developers.com/showthread.php?t=857334
http://forum.xda-developers.com/showthread.php?t=1156569#15398287
OK, I´m not the first one with this specific problem, but some says even with root they can´t delete skype directory from system.
Jerome
Solution:
Run terminal and type:
"rm_-R_/data/data/ com.skype.raider" _ = space
i failed the oparation a few times until i got it..
After that i'v downloaded Skype again, but this time it installed successfully,
Im very disappointed with Skype team failing to fix the problem and having there paying customers to Root there devices !
Jerome,
I guess you are in the same boat i am.
I went to Chile in June and bought a P1010 at Falabella store. My FW is the same as yours and there's no ROM to upgrade (official or custom).
There's no development for it here. Also the video skype is for the GB not froyo.
The only tweaks i could do was the root (z4root) and the OCLF.
Sorry for this bad news... But at least i loved to visit your country. The Piscosawer, the "CONGRO" fish and the "Cafe con Piernas" 8))
{}s
CreativeBR
Jerome_xda said:
Yep, but the update it's not available for everyone... I got installed the lastest version of Kies (2.0.1.11053_99), and it's shows "Current fw version = Latest = PDA:KB4 / CSC:KB4 (CHO)".. May be because my country (Chile).
SuperOnceClick looks fine, but with this issue
http://forum.xda-developers.com/showthread.php?t=812367
Thanks again, I hope that's Gingerbread will be available soon for me.
Best regards
Jerome
Click to expand...
Click to collapse
Hello everybody, before all, I hope there isn't a thread already with this topic, if there is, my apologies.
I have an european (ww) stock rom Transformer on 3.1, I did the first update (3.0 to 3.1) manualy, it worked great, but now, its been since the 3rd of august (OTA 3.2 release date in France) that I've been waiting for my tranformer to receive the OTA, but it just won't.
I've tried to push the "search for update" button thousand times and reboot it almost everyday since then without result.
Do someone have had the same problem and solve it?
By the way, I don't have the keyboard dock yet; doest it play a role in my problem?
I bought my transformer 2 weeks ago i was in 3.1 and i had the update to 3.2 as soon my tab was connected on wifi. But i have the dock.
Are you sure that you never rooted your tab?
You can also ask asus france on their facebook page.
Yes I'm positive, unless the manual 3.0 to 3.1 update implied to root. But I'm quite sure it doesn't.
Apparently you are only offered the update once, if it fails it wont offer it again unless you delete a certain file
Not sure which one it is, but a factory reset should sort it if you can cope with wiping it
that's the odd thing, I wasn't offered it even once. I will search for the file you mentioned and in last ressort, go for a factory reset. But honestly I would prefer not to go that far. That's why I asked for other solutions.
Tried updated manually? ie downloading update from
http://support.asus.com/Download.aspx?SLanguage=en&m=Eee+Pad+Transformer+TF101&p=20&s=16
I've tried it too, I've followed the steps, I've put the "asus" folder on a micro sd card, put it in my transformer, but it did not detect the update, I've tried different ways to put the update folder on the sd card so that the tablet can find the update, but still, it didn't work. I just can't figure out why it doesn't want to update.
Thanks for your clues anyway, I will keep searching for a solution or a way to make this manual update...
If I find the thread with the location of the offending file, I`ll update this thread with it
Thanks, it will be very helpfull
seagle77 said:
Thanks, it will be very helpfull
Click to expand...
Click to collapse
You may already know about this forum, but Im beginning to wonder if the posts I am remembering are infact here
http://www.transformerforums.com
Great place either way
Yes great place indeed, i'll try to find it there
I had a similar issue. The tablet update section said 'There is an update available. Please check notifications'. The search for updates button was therefore greyed out. However, nothing ever appeared in the notifications.
I updated manually in the end. However, the update section remains the same: Telling me there is an update and not allowing me to check for any further updates. I'd really like to get this functionality working again.
OK can you please tell me wich folder did you put on the micro sd card for the tablet to detect the update?
Seagle77 go to settings/applications/manage applications/all and scroll down to DMClient click on it and hit clear data and clear catche if i remember right thats what i cleared when the ota failed to install for the first time, once you clear it u might have to restart but it should show you the ota notifiction after that, hope it helps.
V.
I tried it, but after the reboot, there is still no notification of the OTA and nothing more on the update menu.
Update.zip file you downloaded for manual update should go under /removable/microsd/update.zip try placing it there and seeing if u get the notification after a reset , if not then try booting into stock recovery and starting the update from there using update.zip
I've downloaded a file nammed "UpdateLauncher_WW_epaduser8659.zip" on asus website. Do I have to rename it before put it on the micro sd card, or leave it like this?
Ok, problem solved here, someone told me to check the update version on "transformerforum", and the origin of the bug was my first manual update, were I used the US update, istead of WW version.
Therefore, I just needed to update with the US 3.2 file and it worked perfectly.
Thanks for the help given here. Have a good one everybody
Enjoy 3.2 !
Today I got a message to install a new firmware for my transformer. However, if I do so, the installation aborts after one third of download, and I get a Android man, and a triangle with a yellow exclamation mark. The reason is probably that my system is rooted (running stock rom B80 with 8.6.6.19).
I do not really want this update. But how can I stop the update message? I can only delay the OTA for one day in the update activity.
And, does anyone have an information about the update? Is it worth going back to unrooted? And can I root again afterwards?
pretty sure it fixes the app backup hole that you got root with so i wouldn't update.
To prevent notification Freeze DMClient app with titanium backup
also there should be a .zip labled update or something like it in your /asus/ folder if you could post the number on the file name
I am not happy to admit that, but I messed around with build.prop until the system no longer reboots. I have to restore my backup. When I am back, I will report.
Back
OK, I am back.
Installed Titanium Backup, but did not find the option you are referring to. Can you explain, please? Thanks.
I found only one asus folder on /sdcard/asus, and this is for web storage. It is empty. Where do you want me to look for the file number?
You can use this app to temp un-root your device. If you read the subject, some transformer users used this tool for OTA updates.
http://forum.xda-developers.com/showthread.php?t=1241517
Looks too dangerous. I need a rooted device for Cisco VPN. And maybe that small update is not worth the trouble.
Things might be different, if OTA updates to Android 4. But by then, there will be ROMs available too.
can you upload your dlpkgfile? Also, which locale are you in?
Update
I' ve had the same information about update.
It's still 3.2.1.
Just to finish this discussion: I purchased Titanium Pro, and found an option to disable (it is not called "freeze") the update client. Thanks for the hint.
So I wasn't paying attention when I got the message from AT&T about the update being available, and I forgot that I had rooted my phone. I downloaded the update and it attempted to install, but I got the little android guy and the triangle with an exclamation point in it to let me know that there was no operating system installed. After a moment of panic, I was able to restore using CWM. But now I have this persistent notification at the top to let me know that the download is ready to install, and the clear notification button will not eliminate this particular notification. Any idea how to get rid of the nagging symbol or even delete the download altogether?
issues with att update.
kriswilliams03 said:
So I wasn't paying attention when I got the message from AT&T about the update being available, and I forgot that I had rooted my phone. I downloaded the update and it attempted to install, but I got the little android guy and the triangle with an exclamation point in it to let me know that there was no operating system installed. After a moment of panic, I was able to restore using CWM. But now I have this persistent notification at the top to let me know that the download is ready to install, and the clear notification button will not eliminate this particular notification. Any idea how to get rid of the nagging symbol or even delete the download altogether?
Click to expand...
Click to collapse
I had the same issue from att. I decided to get an ICS based rom. I decided on Virtuous infinity alpha2. was good but choppy and had a few small but annoying bugs. then i went for the alpha 3 rom with the inspire patch and everything works great. you do have to wipe phone and clear cachs. this did fix my issue as well i suggest getting ram manager pro. it helps the phone run much smoother. http://www.virtuousrom.com/ is their website. great site. Again Do Not forget the inspire patch. you can find both here http://rootzwiki.com/topic/30873-virtuous-infinity-v1330-alpha3-general/ the patch for camera fix is under the alpha 2 version.
Spaz84 said:
I had the same issue from att. I decided to get an ICS based rom. I decided on Virtuous infinity alpha2. was good but choppy and had a few small but annoying bugs. then i went for the alpha 3 rom with the inspire patch and everything works great. you do have to wipe phone and clear cachs. this did fix my issue as well i suggest getting ram manager pro. it helps the phone run much smoother. http://www.virtuousrom.com/ is their website. great site. Again Do Not forget the inspire patch. you can find both here http://rootzwiki.com/topic/30873-virtuous-infinity-v1330-alpha3-general/ the patch for camera fix is under the alpha 2 version.
Click to expand...
Click to collapse
i too had a brief lapse inn thinking and did the same thing, is there any way to get rid of the notification that anyone knows of, or how to update? (it's been a good bit since i've been on here and rooted my phone)
try this rom is...it might help you out
http://forum.xda-developers.com/showthread.php?t=1778202&page=811
I second this, this rom makes the phone live up to my expectations.
The Remedy said:
try this rom is...it might help you out
http://forum.xda-developers.com/showthread.php?t=1778202&page=811
Click to expand...
Click to collapse
Hi All,
Really sorry to post a new thread about this, but I am unable to add a post here: http://forum.xda-developers.com/showthread.php?t=1911437
So, followed Member - OPs guide to manually update my A701 to JB.
Simply put, the patch would not install (failed with a permissions error)
Put JB on anyway (just to see) and this won't let me get past the choice of language and location (Also, at this stage, SuperUser tells me system is requesting SuperUser access and whatever I do, it accepts)
So, used CWM to put the 4.0.4 build back, and that worked fine - though according to About Tablet I am actually on 4.1.1
I see improved UI speed and responsiveness, it's all looking great.
But Play Store won't run. Tried adding the latest version, still 'unfortunately stops' Also Nova refuses to run.
Has anyone run into any of these issues (Patch not installing, Play Store failing) and have any ideas what I can do to fix them?
Really sorry again for making a new thread in the wrong forum, I didn't see a choice (other than waiting!)
Thanks in advance,
Al
misteral1970 said:
Hi All,
Really sorry to post a new thread about this, but I am unable to add a post here: http://forum.xda-developers.com/showthread.php?t=1911437
So, followed Member - OPs guide to manually update my A701 to JB.
Simply put, the patch would not install (failed with a permissions error)
Put JB on anyway (just to see) and this won't let me get past the choice of language and location (Also, at this stage, SuperUser tells me system is requesting SuperUser access and whatever I do, it accepts)
So, used CWM to put the 4.0.4 build back, and that worked fine - though according to About Tablet I am actually on 4.1.1
I see improved UI speed and responsiveness, it's all looking great.
But Play Store won't run. Tried adding the latest version, still 'unfortunately stops' Also Nova refuses to run.
Has anyone run into any of these issues (Patch not installing, Play Store failing) and have any ideas what I can do to fix them?
Really sorry again for making a new thread in the wrong forum, I didn't see a choice (other than waiting!)
Thanks in advance,
Al
Click to expand...
Click to collapse
Mate, it doesn't sound good.
What I would do, at this point, is Fastboot the 4.1 image again.. And stay the heck out of CWM. If you Fastbooted the 4.0.4 image, and you still have it showing 4.1, then you have a serious issue. So boot to fastboot, and try it again. Clearly, whatever you did with CWM, didn't work,
Installing a rom from CWM, requires certain things to be done, either in the install script, or via CWM.
Most notably, Formatting User data, cache, dalvik, system, and data. If any of these do not get done, chances are, the rom install will not go good. The basic install script, generally only formats System and Flexrom. This is because Acer distributes a full rom with the understanding there is nothing on it. Most rom modders know this, which is why they give extra instructions via cwm.
The big thing, is when you boot your tablet, is if it says which bootloader you are on. So you have to look,. You want to be on the JB bootloader.
MD
Thanks for the response MD,
A tiny bit unsure how to proceed. I understand everything that you said (well, I think I understood correctly!)
I have in fact tried to fastboot the 4.1.1 image again, and again I am stuck on the language and location screen (did this last night before giving up for the day)
I have read and understood "Stay away from CWM" (and I know that it is in this case only - have used CWM on my Gnex without issue)
Please forgive me if what I am about to write is ridiculous - this is kind of where we'll see whether I understood correctly or not.
I'm thinking that if the various areas were not wiped, and that could be the reason for the snafu, then it would be worth going into CWM (which I have been warned to stay away from, and which I would stay away from except for this one thing) and formatting the user data, system, dalvik etc, then applying either the 4.1 or 4.0.4 to result in a working tablet.
Or possibly flashing the bootloader to make sure it is JB
Or going back to the weird 4.0.4/4.1.1 hybrid which works but doesn't allow Play Store and finding a way around that issue.
Mate, I'm not sure which way to go at this point!
Fastbooting 4.1 is a dead end at the moment (but could that be a bootloader issue....)
Fastbooting 4.0.4 gives me the hybrid (though I can check this again tonight)
BTW, the only CWM Rom work I have tried to do has been with the patched update (second downloadable file I think) - everything else has been done via ADB
So.....CWM to wipe/format caches? (I'm thinking 'NO! DID YOU NOT HEAR WHAT I SAID ABOUT STAYING AWAY FROM CWM????' but I'm asking anyway!)
Flash a new bootloader on? If so, any idea where I would find it (will obviously search here and Google)
Thanks anyway, and thanks in advance if you have any more advice. I really do appreciate the support!
Al
Well Al,
This is perplexing to say the least. Clearly fastbooting the 411 results in frozen at the wizard. My question, when you have the unlocked bootloader, does it say JBxxxxxxxx unlock mode when you boot the tab? Because it should. If it doesn't, then you're still on ICS bootloader. And will have to do the CWM thing to get JB installed. The 411 image flash, is to get a rooted version.
And this is the point. Personally, I do not trust the CWM's at this point. That's just me (already bricked 1 tab 3 months ago with a faulty CWM) I know the folks with ICS are using Pawitp's CWM, and haven't reported issues. But I don't know if they are doing wipes or not.
As with the 404 image, well, why playstore doesn't work is perplexing. You could try reinstalling the playstore via manual method (root required). Which is to delete the vending.apk, install a new vending.apk (making sure permissions are the same as the other files), then reboot. Go to settings, wipe the playstore cache's. Then try Playstore again. This was an old method we used with market issues in HC.
Personally, I feel the issue is with the wipes before running the patch. But I would hate you do the wipes and formats, then discover the emmc chip bricked. So it's 50/50.
But heck, you have warranty. Just install some update.zip, and it resets your bootloader so service doesn't complain
Wish I could give you a definitive answer, but these processes are too new.
MD
Keep warranty
Moscow Desire said:
But heck, you have warranty. Just install some update.zip, and it resets your bootloader so service doesn't complain
MD
Click to expand...
Click to collapse
Can you make a short tut how to replace the old unlocked Bootloader?
My Tab has some Problems with the Display so it need a service ...
witch cwm to use?
witch update.zip?
remove cwm and su if necessary
Android Version: 4.0.4
Baseband: 11.810.922.00
Kernal:2.6.39.4+
Image:ACER_AV043_A701_RV08RC02_EMEA_DE
Build: ACER_AV043_A701_1.017.00_EMEA_DE
Hi MD,
Thanks for such a speedy and useful response!
Warranty: nope! I'm in China, bought the tablet in Shanghai (now way down south in Shenzhen) and it was a dodgy deal to say the least. I suspect they were being lifted from the factory. No complaints from me about this, or about any difficulties caused by rooting/flashing/CWM. My choice of action all the way along and I am aware of the risks
Just flashed 404 again and it is fine so far, again very nice and smooth. Going to look at the Play Store and see how it behaves, see what I can do as far as vending.apk is concerned (although I'm lost when it comes to permissions. Obviously I know what permissions are in tech terms, but no idea where they would be set, how to change them, what to use as a reference) I figure this is the path of least resistance for right now.
Then I'm going to see if I can apply the standard A701 update to JB (which I won't be able to because of rooting/unlocking but I will fiddle around) and see if I have any joy.
Got my keen eyed gf to check the message on boot, you were right that with the 411 image applied it still had an ICS bootloader, so that's good to know if I want to try going back to the flashed JB image. However, I have no idea how to flash the JB bootloader/kernel, and the CWM process for the patched update fails each time (despite editing the first line of the necessary file in META-INF/Google/Android)
So, I will keep you up to date with progress. Fingers crossed!!!
Al
Quick update.
Play Store seemed fine for quite a long time (although I didn't download anything, I was able to browse no problem)
Went to install my back up of Nova, and of course had to tick 'Unknown Sources'
As soon as I did that, allowing installation of apps not downloaded from the play store, I got the 'Unfortunately Play Store has stopped working' message. Before I installed anything else, immediately I ticked that box.
Unticked it, but still not working - installed Nova, not working.
So....
misteral1970 said:
Quick update.
Play Store seemed fine for quite a long time (although I didn't download anything, I was able to browse no problem)
Went to install my back up of Nova, and of course had to tick 'Unknown Sources'
As soon as I did that, allowing installation of apps not downloaded from the play store, I got the 'Unfortunately Play Store has stopped working' message. Before I installed anything else, immediately I ticked that box.
Unticked it, but still not working - installed Nova, not working.
So....
Click to expand...
Click to collapse
Well, seems like Nova is the culprit. I assume you are talking about nova launcher? Or nova the game?
Hi MD
Yes, Nova launcher but no, it's not the culprit. At least I don't think so.
The play store stopped as soon as I ticked 'Install from unknown sources', before I installed Nova.
Very odd.
Quick questions:
1) Any advice/links/downloads for changing to JB bootloader if I apply the 4.1.1 again? Given that I cannot run the patched update/flash from CWM, I am guessing I would need to directly install/flash the bootloader from ADB...
2) Don't kill me for asking this. I know to stay away from CWM, I have seen you post it a good few times here, I heed the warning....BUT.....
Given that I have CWM installed and it's working ok (apart from failing to apply updates) - I have 6.0.1.4 - many of the guides to updating the 701 say it needs 6.0.1.1. Would the slightly more recent version of CWM make a difference in terms of success or failure of the update? Update is failing with a 'set_perm:some changes failed' very early in the update.
Seriously, I am being extremely wary of CWM, it's just that currently I have a slightly disabled tablet and it would be great to get this sorted.
Thanks, once again, for all your help,
Al
Update again, put 404 back on (after issue with play store and unknown sources)
Opened play store, downloaded Apex launcher - all good.
Ran Apex, all good....then suddenly Play Store stops, Apex stops, never to return.
With 404 img on, About Tablet still says 4.1.1
The saga continues!!
Aaaand that's the end of that!
Put 4.1.1 back on, pushed the boot.img from the official update.
Now no CWM, so it seems no recovery mode....if I try to get there by volume down and power on, it goes into update mode.
And of course neither the official update nor the 'patched' one will apply.
Can boot to the first start screen (language/location) but can't get any further.
Maybe I can find a service center here in Shenzhen who can sort it out.....as I said before, no harm no foul, I knew the risks!
Thanks one more time MD for all your support and advice )
Or is it......?
Didn't give up, didn't surrender. Found out how to get into fastboot using frantic waggling of the rotation lock.
Just flashed 404 on again, waiting for boot to finish. Might still have a semi-usable tablet! Then I just wait till a 100% working JB manual update surfaces!
misteral1970 said:
Or is it......?
Didn't give up, didn't surrender. Found out how to get into fastboot using frantic waggling of the rotation lock.
Just flashed 404 on again, waiting for boot to finish. Might still have a semi-usable tablet! Then I just wait till a 100% working JB manual update surfaces!
Click to expand...
Click to collapse
HA HA, you found the User Data wipe.... Yeah, a little known secret from the 500 forums.
MD
It's so strange....so now I'm back to having flashed 404 but the tablet thinks it's 411.
Play store was fine for about 40 minutes, I quickly got chrome, currents and BBC news.
I turned off the Acer ring and play store died...
But here I am, typing to you on the tablet and it's fine. And what a change in performance. It's most noticeable in currents..the increase in speed and smoothness when scrolling between pages makes it at least ten times better than before.
But the last flash was 404....weird....
I'll leave it like this for now. No market but at least it's not semi bricked!
Super Quick update - in lieu of finding a sparkly copy of vending.apk, I tried wiping data and uninstalling Play Store (reverting to factory)
It duly downloaded a new version, and worked fine.
Then I popped Apex on, the GPS got busy, and Apex and Play Store died.
The wipe/uninstall worked again for Play Store so to be honest, I am currently quite happy. Ok, it's not perfect, but if I can quickly reinstate Play any time it fouls up, I can still build up a decent amount of apps to make the thing useful.
And seriously, whatever changes are there (considering the weird 404/411 hybrid) the performance is incredibly enhanced. All the faffing has been worth it, it is finally the tablet that it should have been from the start.
misteral1970 said:
Super Quick update - in lieu of finding a sparkly copy of vending.apk, I tried wiping data and uninstalling Play Store (reverting to factory)
It duly downloaded a new version, and worked fine.
Then I popped Apex on, the GPS got busy, and Apex and Play Store died.
The wipe/uninstall worked again for Play Store so to be honest, I am currently quite happy. Ok, it's not perfect, but if I can quickly reinstate Play any time it fouls up, I can still build up a decent amount of apps to make the thing useful.
And seriously, whatever changes are there (considering the weird 404/411 hybrid) the performance is incredibly enhanced. All the faffing has been worth it, it is finally the tablet that it should have been from the start.
Click to expand...
Click to collapse
Well, good news then. I think it's an interesting set-up. Hybrid. Still not sure though, why it pulls 411 from the build.prop as it should have been changed when you flashed the 404image. But honestly, after reading the OP's steps, I believe he references going back to 404 via CWM, and not fastboot. This of course would mean installing a full 404 original rom. I'll have to look over my JB system dump and see where the other prop would be. Maybe something changed in JB.
So if you can live with it, it's probably better to leave it be till we come up with something more definitive.
MD
"So if you can live with it, it's probably better to leave it be till we come up with something more definitive"
Yeah, totally agree.
Mate, seriously, thanks for the support and advice on this. It makes a big difference. Even as I sat there last night with what seemed to be an unusable tablet, being able to chat to you about it meant that at least I didn't feel completely adrift!
Big big thanks