Hi everyone, I flashed my viewsonic gtab with tnt lite 4.4, and everything seems to be working fine, except that the android market thinks i'm using Malata GTablet-TnT-Lite...is there any way to fix this?
Thanks
Quicksilvr530 said:
Hi everyone, I flashed my viewsonic gtab with tnt lite 4.4, and everything seems to be working fine, except that the android market thinks i'm using Malata GTablet-TnT-Lite...is there any way to fix this?
Thanks
Click to expand...
Click to collapse
Actually, it is seeing it correctly, just not the way you want it to be seen. Your gTablet OEM is actually Malata. With the new version of Market, Google has attempted to tighten non-authorized device access. It gets device info from the build.prop file (/system/build.prop). If you are not having problems with limited app selection or downloading, you can leave as is.
If you are having limited app access/download problems then do a search for "market fix". You will probalby find various edits for the build.prop file to trick market into giving you increased access. When I was on stock 4349 (way back when), I edited mine by adding the following line "ro.build.fingerprint=google/passion/passion/mahimahi:2.2/FRF91/43546:user/release-keys". I also remember seeing one that recommended changing "ro.product.device=" to "olympus'. To edit build.prop you will need to use rootexplorer or a similar app. As always it would be best to do a backup with CWM before editing system files.
Al
Related
I installed vegantab and followed the directions to get the full marketplace on my gtab. However when i search for certain app they do not show up. At first i just thought they were apps that weren't compatible with android tablets but this does not seem to be the case. A couple of the apps are facebook and twitdroid. I know facebook came preinstalled on tap n tap so it should not be a compatability issue. Can someone please tell me what may be causing this?
Thanks in advance
Have you tried this post? It worked for me when I thought I had the full market.
http://forum.xda-developers.com/showthread.php?t=865245
This happened to me too. Even after I did the market fix as described in the ROM install thread. The previous poster has pointed you in the right direction, but more specifically these are the exact steps that fixed me. I take no credit for this other than finding it and passing it along.
Step 4.
Go into Settings - Applications - Manage Applications - Market - Clear CACHE - Force Stop
(For TnT/TnT Lite... Settings - Applications - System Applications)
Step 5.
Press back once - Google Services Framework - Clear DATA - Force Stop
Step 6.
Go back to your home screen and open up the market. You should get an error. If not, redo steps 4 and 5 until you do.
Step 7.
Reboot your device. After it starts back up let it sit for a minute or two to let things in the operating system normalize. Open the Market. Reboot your device.
Step 8.
Open the market again and enjoy. You should now have Flash and the Android Market.
I've always thought that "Full Market" didn't mean everything available in the market, but everything that the market believes it can install on your device. I've always double-checked by going to the web market and trying to "push" the app to my device to see if it is compatible.
Or is there something on the device that identifies itself on the market as to what it can have installed?
I wish there was a tablet market separate from phones. It would make things much easier.
MechAniX.one said:
I wish there was a tablet market separate from phones. It would make things much easier.
Click to expand...
Click to collapse
but then you wouldn't be able to see the phone apps that work well on tablets. I would assume that most widgets are cross compatible. Even when going to iTunes from an iPad, they have the 'iphone apps available for you.
in the infancy of android tablets, if we could ONLY see tablet only apps, we'd all be limited to about 50-100 apps, most of which not all of us would have a purpose for.
I'm having a similar problem, even after following the steps outlined in the Clockwork/ROM thread. Not sure if it varies with the rom as I was able to get Zeam Launcher with the Adam rom, but not with TNT lite.
Following along to see if there are other suggestions...
So I had followed the steps when I originally flashed Vegan 5.1.1 and the Market didn't show up Apps, like Facebook for example.
For the heck of it I tried it again just now, after I've been using my tablet for a while, and now the Market works fully! I still can't see tablet Apps like the CNN one, but now I have access to lots of Apps I didn't before.
Another resource you could check would be 4shared.com. Search for cnn.apk or just .apk and you will see lots of other apps, not sure if they will all work, but its worth a shot.
FWIW... I ran the steps again last night (for the second time since flashing TNT lite) and got access to more apps. I was able to find zeam, but I still can't find ADW. Might try it again tonight just to see what happens.
Seems odd, but that's been my experience so far.
jacksonpt said:
FWIW... I ran the steps again last night (for the second time since flashing TNT lite) and got access to more apps. I was able to find zeam, but I still can't find ADW. Might try it again tonight just to see what happens.
Seems odd, but that's been my experience so far.
Click to expand...
Click to collapse
From my experience with three/four different ROMs is that it shows up for certain ROMs(like VeganGinger and not for others like VeganTab)
couchmonkey said:
From my experience with three/four different ROMs is that it shows up for certain ROMs(like VeganGinger and not for others like VeganTab)
Click to expand...
Click to collapse
I'm noticing that as well as I flip back and forth between adam and TNT lite.
Is there any setting that can be changed without switching ROMs that will fool the market into thinking the device is compatible with more applications?
sedrikk said:
Is there any setting that can be changed without switching ROMs that will fool the market into thinking the device is compatible with more applications?
Click to expand...
Click to collapse
If you have Root Explorer you can alter your build.prop file to set your device as olympus and that gives you a full market, or at least the fullest I've seen. The following apps show up with this change:
firefox, adw, facebook, cnn, zeam, launcher pro, dolphin hd, flash 10.2, samurai vengeance, etc.
This has worked on Vegan 5.1.1, TNT Lite 4.4, G-Harmony 2.3.3, CM7, & Calkulin's v1.1 for me.
http://forum.xda-developers.com/showthread.php?t=1020130
I used astro file manager to change that file and then reapply the market fix. Still no apps like google docs on the market. Would this be an immediate fix or will it take some time for the market to register the change?
nvm: astro didnt actually save the modified file after editing it
Using root explorer now i guess the correct procedures would be
1) change the mount to r/w from r/o
2) modify the permissions of the build.prop to allow write access
3) modify build.prop
4) restore original permisions
5) change mount back to r/o from r/w
6) rerun market fix
Am i missing anything?
Read through the linked thread a bit more and seems that is all that is needed. Thanks for the point in the right direction.
This is what I do. Using Root Explorer I change the mount from R/W to R/O then alter the build.prop from Vega to olympus on that one line & then switch back to R/W. I don't change permissions. Then I go to settings>applications>market to clear market cache & then force stop. Next I go to settings>applications>google services framework to clear data & then force stop. Reboot. Then have full market. Always works for me.
Hi,
I've got an Archos 43 IT with dual boot UrukDroid 1.5 and the stock fw. I had the latest version of the market running there (+market fix, installed by arctools) and all worked just fine. But since a few days ago the market only shows very few apps (like 2-3 each section) in both (stock and ud). When I try to install apps over the official market-homepage, I get the message like this (translated): "This App isn't compatible to your Archos A43-Device."
What can I do here? Does anyone have the same problem?
A few days ago in another post I read about a pro here, who managed to replace the file which told the market, that it is an A43 by an other one (i think, it was a samsung galaxy), but I can't find the thread/post anymore. I guess this should solve my problem, but I don't know which file it was, anymore.
Does anyone know, which post this was (link)/which file?
Ma-Shell
You can change the setting at content filtering to show all app.
For market app, you may reinstall it from arctools.
Hi,
thanks for your reply.
deliverywong said:
You can change the setting at content filtering to show all app.
Click to expand...
Click to collapse
Do you mean in the settings-menu under "select level"? All the checkboxes are activated with me.
deliverywong said:
For market app, you may reinstall it from arctools.
Click to expand...
Click to collapse
I tried but it's the same as before.
ma-shell
EDIT:
I even tried applying the fix again but it didn't work
EDIT 2:
I now managed to find the post I mentioned in my first post. It was here:
http://forum.xda-developers.com/showpost.php?p=11113696&postcount=3
But when I tried modifying my /system/build.prop, I was very surprised to see, it already had the galaxy-footprint, the line containing Archos was only put as a comment (Does this come by UrukDroid as default?). So this doesn't seem to work either...
I am still having the same problem I've tried everything i can think of fix unfix un reinstall edit build.prop and i think posted on the other thread you mentioned. And I'm having the same problem on my stock installation too. Anyone else have any ideas.
Sent from my A32 using Tapatalk
I now managed to get the fingerprint of a Motorola somewhat... (ro.build.fingerprint=verizon/voles/sholes/sholes:2.2/FRG01B/45394:user/release-keys)
Doesn't seem to do any change... Do I have to do anything to apply the changes in the build.prop? I tried reboot, clearing cache and data of the market and the google-services-framework. Anything else I have to do?
So, I got all the apps back . What I did was the following:
First I switched my fingerprint back to the Galaxy one. After that I rebooted my device and went to (the menu-points are translated by me, so it might not be the exact name) Settings -> Applications -> manage Applications -> Market -> Clear Cache, Clear Data, Force Stop.
Does this work for you as well, jared?
ma-shell
Just talked the wife into getting one. She loves her android phone and will be using the market to install apps.
Major issue for me now. I am running into an issue where almost all the apps are saying "not compatible with your device" I know this is not true because it works on her optimus S phone.
Tried the market fix 6 times now and stll everything says incompatible. Is there a build.prop fix I can use to make the market see the device as compatible?
If not what is a stable functional Rom I can go to?
Thanks for any helpful suggestions.
Yea for me to. Simple apps that we KNOW works on the GTab. I ran into like...14 of em. For me..i downloaded all onto my PC...from various sites...then hooked my GTab to the PC and put it into the Internal storage...then download from there. All of em worked. Even Flash 10.3.
Just download Vegan tab 7.1 I did and that fixed my problem.
You need to change the LCD_denstiy in the build prop to 160 then do the market fix. With the old market setting the density to 161 fixed a problem, but with the new market it is not needed.
That did it markmac.
used root explorer to make a copy of the original to a folder on my SD card for backup. THen copied another one to the root of the SD card. Edited the build.prop on the root of the SD card. then mounted system as r/o and cut and pasted the build.prop from the root back to the system folder. REbooted and did the Market fix. boom everything is updating and able to be installed now.
Again THanks
here is situation:
1. I had rooted 1.4.2 with not blocked OTA and my NT updated to 1.4.3.
2. It is obvious that root and some apps stopped working and some of them even disappeared from the device (like WinAmp for example).
3. I rooted 1.4.3 with SDcard method and it looked like things are fine until I started to get my apps back.
4. I used FIREFOX as a main browser with 1.4.2 update and after registering at Play store on rooted 1.4.3 I read that FIREFOX is incompatible with my device!!! What the hell?
5. Also, my NT registered at Play as NEW device, not the old one as I had - so it seems my serial changed or something has changed in the build.prop or somewhere else in the identification part of device.
6. Besides, after root, i started installing apps and it seems Notification bar has some sort of glitches - it does not clear all the messages and keeps the last downloaded file in the list...
Can anyone point me how to fix incompatibility issue?
---------------
Now, second situation:
7. I reverted back to 1.4.2 with the img file from this post: http://forum.xda-developers.com/showthread.php?t=1663836
8. But the thing is that I want to try 1.4.3 again
9. I downloaded official update from B&N and put it onto the SDCard
10. It boots and progress bar starts to move but at some point (25% of bar) it shows me exclamation icon with '!' and says "Please restart your device and try again..."
What is this issue and how it can be fixed?
Thanks in advance.
Honestly, I have had similar issues with the play store and my Nook on 1.4.3 but if you want to block OTA updates more effectively, I have been told that the updater cannot run if you have CWM flashed rather than the stock recovery image. When I screwed my Tablet up I found that I couldn't get it to load the acclaim_update.zip or any update files until I reflashed the stock recovery image rather than CWM.
titanshadow said:
Honestly, I have had similar issues with the play store and my Nook on 1.4.3 but if you want to block OTA updates more effectively, I have been told that the updater cannot run if you have CWM flashed rather than the stock recovery image. When I screwed my Tablet up I found that I couldn't get it to load the acclaim_update.zip or any update files until I reflashed the stock recovery image rather than CWM.
Click to expand...
Click to collapse
Can you share the links or files that get your nook back to normal state?
I've been reading and reading a lot the forum but still miss something important. Step-by-step guide would be much appreciated, if possible.
I have found the same problem. When I run CM7 on the NT from an SD card, I have no app compatibility issues. But when I run from rooted stock 1.4.3, I get the app compatibility error. I even tried pasting the build.prop file from CM7 into 1.4.3 but that did not correct the problem. The same apps are coming up as not compatible. What else is the Market looking at to determine compatibility?
Nook Color
Eustace2 said:
I have found the same problem. When I run CM7 on the NT from an SD card, I have no app compatibility issues. But when I run from rooted stock 1.4.3, I get the app compatibility error. I even tried pasting the build.prop file from CM7 into 1.4.3 but that did not correct the problem. The same apps are coming up as not compatible. What else is the Market looking at to determine compatibility?
Click to expand...
Click to collapse
This was actually a fix for Nook Color... to modify the build.prop. If you copy/pasted the entire build.prop I would think it would work.
One other thing to do is
1.) manage google play
2.) clear data
3.) uninstall updates
4.) manage google market
5.) clear data
6.) manage google services framework
7.) clear data
8.) reboot
This didn't always work and I had to do this a couple time. Not sure if which step made a difference or what order but it eventually worked. And I could see as many apps as my Captivate (Galaxy I).
Anyway, again, this worked for Nook COLOR and not Tablet. Or at least I havent figured Table yet. If you figure it out. Let me know.
My recent attempt was to copy the build.prop from Nexus and I got black screen after start up. Now I had to unbrick my device and I'm back to square one.
Good luck.. Keep me posted!!!!
@rtabasco - Good plan, but it didn't work. Even when I uninstalled the update and just used the Market app. Looks like 1.4.3 may have changed something other than the build.prop file. I'll keep poking around. It would help if the Play Store would provide a little more detail about the compatibility issue.
This just gets even more strange...
Restored with 1.4.2 image from http://forum.xda-developers.com/showthread.php?t=1663836 and Google Play (after root with sdcard method) says "FIREFOX is incompatible..."
Also tried to restore with NT_stock_1.4.2_Ribbon_Root_B&N.zip from http://forum.xda-developers.com/showthread.php?t=1494367 and Google Play still says "FIREFOX is incompatible..." Besides 'Go Weather EX' is incompatible too - this is ridiculous.
Anyone has idea how to overcome this?
PepeladZ said:
This just gets even more strange...
Restored with 1.4.2 image from http://forum.xda-developers.com/showthread.php?t=1663836 and Google Play (after root with sdcard method) says "FIREFOX is incompatible..."
Also tried to restore with NT_stock_1.4.2_Ribbon_Root_B&N.zip from http://forum.xda-developers.com/showthread.php?t=1494367 and Google Play still says "FIREFOX is incompatible..." Besides 'Go Weather EX' is incompatible too - this is ridiculous.
Anyone has idea how to overcome this?
Click to expand...
Click to collapse
What is your DPI ? Do you have an easy ( free ) way to try 160 ? . The market is your friend.
old_fart said:
What is your DPI ? Do you have an easy ( free ) way to try 160 ? . The market is your friend.
Click to expand...
Click to collapse
I am set at 160 dpi and that didn't help.
old_fart said:
What is your DPI ? Do you have an easy ( free ) way to try 160 ?. The market is your friend.
Click to expand...
Click to collapse
You mean - can I access 'build.prop' and change DPI there to 160? I probably can, but why exactly 160?
Why not default "169.33333"? As I understand CM7 has '160'?
it took me less than a minute to find this one... please do more searching and reading... thank you !
http://www.youtube.com/watch?v=uKlO9gkmsKk
PepeladZ said:
You mean - can I access 'build.prop' and change DPI there to 160? I probably can, but why exactly 160?
Why not default "169.33333"? As I understand CM7 has '160'?
Click to expand...
Click to collapse
Apart from the issue we are discussing in this thread that we can't figure out, a lot of compatibility issues with a rooted NT could be eliminated by changing the screen DPI to 160 in the build.prop file. My guess is that most of the apps were written for phones with 800x480 displays (or other dimensions that are easy multiples of 800x480). Making that change had worked for me to get access to most apps I wanted until this most recent problem that has been caused by changes in 1.4.3 or in the Play Store, or both working together.
Eustace2 said:
Apart from the issue we are discussing in this thread that we can't figure out, a lot of compatibility issues with a rooted NT could be eliminated by changing the screen DPI to 160 in the build.prop file. My guess is that most of the apps were written for phones with 800x480 displays (or other dimensions that are easy multiples of 800x480). Making that change had worked for me to get access to most apps I wanted until this most recent problem that has been caused by changes in 1.4.3 or in the Play Store, or both working together.
Click to expand...
Click to collapse
Thanks for explanation. I looked in build.prop from CW7 and DPI there is set to 160. I will try and report if this solved at least firefox problem.
old_fart said:
it took me less than a minute to find this one... please do more searching and reading... thank you !
http://www.youtube.com/watch?v=uKlO9gkmsKk
Click to expand...
Click to collapse
Thank you for video, but I was not asking how to edit text document, but rather what this change will give me.
Well, BNs build.prop has separate settings for X and Y dimensions. Following the logic, it does not matter if DPI is set via one command or via two... Anyway, simply changing to 160 DPI and rebooting did not help me with firefox compatibility in play store as well as other apps that were noted to show incompatible.
Any other suggestions and ideas would be very much welcome!
Hi everyone,
im having problems updating the build in Tunein 5.1 to the latest 7.1.
It works doing it via market oder apk but after a restart 5.1 is installed again by the system.
How the hell can i fix it...the old 5.1 must be somewhere & getting restored after every single restart...
bloodgnome said:
Hi everyone,
im having problems updating the build in Tunein 5.1 to the latest 7.1.
It works doing it via market oder apk but after a restart 5.1 is installed again by the system.
How the hell can i fix it...the old 5.1 must be somewhere & getting restored after every single restart...
Click to expand...
Click to collapse
I got a reply from archos support.
" our tech team is aware of the problem and is working on a solution"
Given how old is the problem I guess they are not really working on it. Can one of our dev champion look at it? Maybe it is as simple as a file set as readonly somewhere.
It looks like the newer tunein from either applibs 6.4 or from the market 7.1 is installed but it does not overwrite the original app. I guess archos did not install it at the right place. The solution would be to modify the shortcut on the dashboard and also in the clock application to the new apps. Or another solution move original apps to where the market apps is installed. I am not a tech so I'd do not know how .
Papagaiou said:
I got a reply from archos support.
" our tech team is aware of the problem and is working on a solution"
Given how old is the problem I guess they are not really working on it. Can one of our dev champion look at it? Maybe it is as simple as a file set as readonly somewhere.
It looks like the newer tunein from either applibs 6.4 or from the market 7.1 is installed but it does not overwrite the original app. I guess archos did not install it at the right place. The solution would be to modify the shortcut on the dashboard and also in the clock application to the new apps. Or another solution move original apps to where the market apps is installed. I am not a tech so I'd do not know how .
Click to expand...
Click to collapse
Via "Apk share" I shared TuneIn Pro to my Archos Connect from Galaxy S2, it's installed and works.
No I've tried to do the same with new version of TuneIn Pro 7.3, it's not working. It's installed, run, but still 7.1 not 7.3.
So after fighting a long time with this crap device here is the solution for tunein:
Rename the new (7.4) Tunein to tunein.apk and copy it via Root Explorer (Or anoter Root-Filemanager) to /data/app.
After that change the permissions of tunein.apk so that there no write is possible (untick the write options in permissions after holding your finger on tunein.apk a long time).
With this it is impossible for this stupid Archos device to overwrite the tunein with the crappy old 5.1 Version.
Downside: You cant log into your tunein account. But at least you have a good working Tunein.