Related
I've been collecting free apps from Amazon on my rooted NC for awhile now. At the time I got each of these apps, they were listed as "compatible" with my device.
Now suddenly a lot of them are not, and I am unable to go back and re-install the ones that I had removed.
Even worse, pretty much everything I've tried so far today to grab has come up as incompatible. Even really simple stuff that should have no problem running.
Oddly, at some point early on, Amazon listed my device as simply "Nook Color". Most of the apps are still showing as compatible with that device. Unfortunately, that's not what Amazon thinks my NC is anymore! I now have a second device on my list called "BarnesAndNoble NOOKcolor", which almost nothing is compatible with.
So then I wanted to check to see if Amazon was behind this, maybe to screw B&N fans. But nope! The Android Marketplace lists every game I've checked so far today as incompatible with my NC!!!
That's certainly news to me, considering some of the games I checked are currently installed on my NC and work perfectly.
I'm not sure what's going on here, but it's sort of scaring me. Who's locking down my rooted NC? If the official android marketplace says everything is incompatible... there aren't a lot of options for getting apps.
Do search with "Market" keyword, you will see about 10 threads with many responses and instructions how to fix this.
votinh said:
Do search with "Market" keyword, you will see about 10 threads with many responses and instructions how to fix this.
Click to expand...
Click to collapse
There are quite a few threads found that way, but none of the ones I read helped. I did the "stop/restart Framework/Google and reload" and nothing changed. Most of the others seem to be related to problems with the new market, which was working perfectly for me up until today, or problems run into right after rooting. I've been rooted for about 5 months with no market problems of any kind, and I haven't changed anything on my NC for over a month.
I also tried clearing the settings for the Amazon market and also deregistered the device from my amazon account, forcing it to re-register. Still no luck.
Anyone else seeing this, or have another suggestion?
My old market and new market were working fine too, just like yours, until a few days ago. If you try the 160 dpi/reboot/clear-data-from-market procedure below and that doesn't work, then you may have a totally unique problem that just happens to have the same variety of symptoms everyone else is having. (I'm doubtful.) This procedure seems to be fixing the problem for almost everyone else. Did you try it? It fixed mine.
1) set dpi to 160 in build.prop
2) reboot
3) clear market app data (force close first may help?)
4) restart market, accept terms, let it rebuild data at 160 dpi
5) profit
the above we all seem to agree on now. Next steps are more speculative
6) set dpi back to 161 (or whatever you had)
7) reboot
8) profit indefinitely (unknown how long this lasts; I rebooted >5 times including flashing a nightly w/o issue)
9) do NOT clear data again as this rebuilds data at the wrong dpi again.
Click to expand...
Click to collapse
Thanks, I had tried the first half, but not the second. I used manual nooter, so my dpi entries originally looked like:
ro.sf.lcd_density.xdpi=169.3333
ro.sf.lcd_density.ydpi=169.3333
I don't know if that makes a difference.
Anyway, I just tried the second half of the above process but I'm still showing as incompatible. I wonder if I need to re-noot.
Everyone trying to be helpful here seems to miss the poster's dilemma. He is talking about the Amazon Market, not the Android Market. Hopefully someone familiar with the workings of the Amazon Market will chime in with some suggestions.
My original problem was with Amazon's market, but it looks like that's just a symptom of the bigger problem that I noticed first because I use it every day, as opposed to much less frequent use of the android market.
But the Android market suffers the same problem and from what I've read online it sounds like the problem was started with changes by Google that Amazon also adopted.
Interestingly I noticed this for the first time last night on the Android market and this morning with the Amazon market. Ebook downloads presently are unaffected to my rooted NC. Amazon recognizes my device as an Android but when I tried to make an app purchase this morning it suddenly tried to download it to a BN Nook. Amazon emailed me this morning saying that unless I have their market preloaded by the manufacturer they do not support it. Collusion?
I got the "not compatible" message after installing the most recent update from the Amazon App Store. Fortunately, I have the very first app store apk. I uninstalled the updated app store, then installed the old apk, logged in and then updated it and for some reason that worked for me. You might try not updating also to see if that works. I am not using CM7 though and I'm not manualnootered. I'm minirooted meaning I can side load apps and have superuser access, but no Android Market access and some other things.
I have attached the apk I used. I hope it works for you.
unibroker said:
Interestingly I noticed this for the first time last night on the Android market and this morning with the Amazon market. Ebook downloads presently are unaffected to my rooted NC. Amazon recognizes my device as an Android but when I tried to make an app purchase this morning it suddenly tried to download it to a BN Nook. Amazon emailed me this morning saying that unless I have their market preloaded by the manufacturer they do not support it. Collusion?
Click to expand...
Click to collapse
A better question would be is Amazon trying to bork the Nook Color with their app?
Anyone else have a suggestion for getting the Android Market working again for me?
thanks for the APK, I'll try it when I have a chance... But since the Android market from Google doesn't work either I'm hoping for a fix to that.
If you make the change in your build.prop “ro.product.manufacturer=BarnesAndNoble” to “ro.product.manufacturer=samsung” then reboot the device. This seems to fix most of the device compatibility problems in the Amazon appstore. I went down the top 100 paid and free app list, and the only apps that came up with the compatibility problems after doing this are,
Soundhound
Peggle
Thumb keyboard
Trainz simulator THD
Chuzzle
Talking Tom Cat
flexT9
GrooVe IP
Ultra Voice Changer
TV.com
Compass
Also attached is the amazon appstore v.1.14, it has the double click buying fix, but does not give all the compatibility issues. With installing this version does fix the compatibility problem, but you will be constantly hounded with the update reminder.
I don't use Facebook, but I was able to find, install and open the Facebook app with the new market. Do the density change using 240. Its more stable than 160 for whatever reason.
GMPOWER said:
If you make the change in your build.prop “ro.product.manufacturer=BarnesAndNoble” to “ro.product.manufacturer=samsung” then reboot the device. This seems to fix most of the device compatibility problems in the Amazon appstore.
Click to expand...
Click to collapse
Thanks for the suggestion. Unfortunately it had no effect. The first four apps i tried not on your list all came up incompatible, as did stuff on the google market.
I'll try your attachment to see if it helps. Thx!
kayak and tripit does not install
Running MN4.5 on NC. Kayak and Tripit are visible in Market and downloads - but I get a window that just says "error".
Any suggestions?
GMPOWER said:
Also attached is the amazon appstore v.1.14, it has the double click buying fix, but does not give all the compatibility issues. With installing this version does fix the compatibility problem, but you will be constantly hounded with the update reminder.
Click to expand...
Click to collapse
The old version of the market is working! I was able to install a number of apps that didn't previously work.
Now if I could just get the Google market to work!
Thanks for that link!
I was having the same problem with the AMAZON appstore (but not the android marketplace, for some reason) but I couldn't find the old amazon appstore apk. Going back to it totally fixed the problem. But you're right, the constant reminders to update the apk are a pain in the whatsus.
Also try going into application management and goto market and tap uninstall updates. Also use titanium backup or similar program to freeze market updater.
By what I read, I bet amazon is trying to block the competition because they are fixing to come out with their own tablets and by horning something like the nook you might be enticed to buy their tablet.
I voided my warranty and your mum.
My markets all seem to do whatever the f*ck they want the moment i need an application that was perfectly available minutes before. What i've done to get around the issue if neither the market or the amazon store have what i'm looking for is: (i know its tedious but hey it works)
1) install astro
2) using your android phone assuming you have one, download the applications you want regardless of them being compatible with the nook color according to the android market.
3) once your files are installed on your phone use astro to create a backup of the .apk files you want (open astro > menu > tools > application manager/backup)
4) i then take my sd card out of my phone and pop it into my nook color and install my apps through w.e file manager it is i have on the nook color
all the games that i cant normally download onto my nook through the official methods i've been able to install and play through the method i've been using. not ALL apps will allow you to back them up though =/
So I had no problem installing or physically using the market app. The problem comes when I search for apps in the market. Every time I see a thread about must have apps I search for said apps and only find half or less. Real racing 2, Gta 3, even Google f'in maps all come up with nothing. I have tried every version of the market I can find to no avail. I figure there must be some other problem, and I just don't have the intelligence to figure it out. Is it possible the market checks for device compatability? Regardless, you guys are smarter than I can ever hope to be and seem helpful for the most part.
I would tell you what I rooted with and what market version I am using but it all got lost when my last laptop crashed. Yes, I know, longest post with no info ever. My bad.
UPDATE
I no longer have a computer and did not get any further in my quest to get the full market before my computer died. I probably could have just edited this post instead of posting a reply (third post) but I don't use forums much. So if you know of a way to get the full market without a computer it would be most appreciated.
Check out this thread.
Now, that developer has stated that he will not support stock, so I would not use his build.prop if you're using stock. What I did was to modify my own build.prop. Comment out (put a pound symbol: "#" at the very start of the line) any lines in your build.prop that start with either ro.build or ro.product, and add any line starting with those strings from the linked build.prop.
Now, realistically, I would expect that the linked build.prop to work on stock, but the developer has explicitly said you're on your own if you try. You can mess up your device by playing with build.prop, but the ro.build & ro.product lines should be relatively safe to change. Plus I have my own tweaks I prefer, so that's all I took from his version.
Check out the first post in this thread. I found this as a work around for the not compatible crap.
You have to follow it to a T
I just installed Real Racing 2 on my KF running CM7 Short version... Pay attention to browser vs market....
You may need to go to market.android.com in your browser first and log out if you are already logged in. (cookies)
1. Using browser google the app name.
2. Scroll until you see the link to the app on market.android.com.
3. Click that link in browser.
4. If you get a pop-up that asks to use browser or market, select browser.
5. A pop up will ask you to sign in. Sign in.
6. It will then ask you what to use to complete action, browser or market. Select market.
7. There will be an install button on the left of the page that describes the app, reviews, etc. Select install and then accept permissions.
8. It will download, but there will be an exclamation point at the top saying it is not compatible with your device, but if you look in your status bar, it will show that the app downloaded by the little check box inside a square icon.
9. Click that and finish the process. When I clicked the link in status bar, it then prompted me for the full 600 meg additional download for the game.
It finished the download and installed. I am now looking at the "Player Settings" screen and music from the game is playing on the KF.
The link posted above was for installing magiclocker main which, if you go through the normal process using the market app, is not available and doesn't come up in search . But if you do it as described, it will work.
(now to uninstall Real Racing 2 'cause I'm not a gamer)
Yes I am bringing this back from the dead because I have made no progress. It is only my fault though. Long story short, my fire is my only connection to the Internet now. I have no computer and did not get to flash a new Rom or update my build.prop before it died. Same general question as before about the market, but with a new more difficult situation. I figure I am screwed but I don't like to give up easily. Thanks again.
I got around this by using the GR6 rom (MoDaCo)... It has changes to it to make the market think it is a Galaxy Tab...
http://forum.xda-developers.com/showthread.php?t=1439916
I see that version 7 is out now... have not tried it... might flash it today.
o Based on the 6.2.2 release
o Heavily optimised and compressed to take as little space as possible and perform as fast as possible!
o Includes Google Services Framework and Google Play Store, masquerading as Galaxy Tab for maximum app availability
o Optional Google Books / Music
o Network location support (for Maps etc.)
o Rooted with Superuser
o Insecure boot image (for 'adb remount' etc.)
o init.d support
o TweakDeck Twitter client Kindle Fire version (can be uninstalled)
I've just tried an app from a website out of stupidity and it totally took over my phone. It just kept loading a webpage over and over until I killed the app. I'm just concerned about my Nexus and my data.
Has anyone heard of http://leviathansecurity.com and the nopermissions.apk?
Stock and unrooted.
I haven't heard of that website but I think you should uninstall that app rather than just closing it.
I downloaded a bad app as well last week but it deleted all my SD content, photos and music etc
Now I only install Apks from here on XDA and play store of course
here's link about that apk,
leviathansecurity.com/blog/archives/17-Zero-Permission-Android-Applications.html
3 functions
reads sd data,
reads what apps install and access their data
device information
then sends info via url by opening webpage to send data
its just to show how easy it is to give access to your information for apps that abuse permissions or even given none like this apk, this one is intentional to show the loop holes
I didn't realise how easy it was, rooted is evem worse
GMonkey said:
I've just tried an app from a website out of stupidity and it totally took over my phone. It just kept loading a webpage over and over until I killed the app. I'm just concerned about my Nexus and my data.
Has anyone heard of http://leviathansecurity.com and the nopermissions.apk?
Stock and unrooted.
Click to expand...
Click to collapse
DELETE that app, make sure the apk is gone too.
When you approved side loading of apks, your good phone warned you to be careful with what you ok to install, no?
Install Lookout as well and let it do a full scan, you never know..
Leviathan security, and the no permissions app, is a test application to show how zero permission apps can still read and steal data from your phone without permissions. AFAIK it isn't malicious, just a test app to show how easy it is for 0 permission apps to steal your data. Just uninstall the APK. More info here: http://leviathansecurity.com/blog/archives/17-Zero-Permission-Android-Applications.html
Thanks Peeps, It did seem legit on the site before I installed it. It's just the fact it took over my browser for a bit. The app was removed but, would there be a need to hard reset or anything like that? I'm normally rooted and have a data firewall to block anything outgoing on certain apps but, with the N4 being so good as it is I've put it off until I can no longer resist the urge.
This thread should be kept relatively clean & free of posts or comments not directly related to getting all Gapps working. Logcats & other reps via terminal or adb should only be posted if you know what you are looking at & for, or if a Dev asks you specifically for something. If you have a specific thought or idea, please feel free to participate, but also, please keep this easy to browse & search through for the folks working on getting everything working.
I have so far been able to get almost all Google apps working, including G+, Hangouts, Chrome, Gmail, Play Books, Movies, Music, Newsstand, Play Services (100%, all sub-menus), Google Now/Search, Voice, Maps & even YouTube. I can post pics when I get to a laptop & have a minute, but they'll just show that all these are working for the most part.
Play Store is a conundrum. It will work with some changes that effectively kill the Amazon service most of us bought the tablet for & use most, but I'm still hopeful that integration will be possible as dual boot does not interest me.
So far, I have been able to determine that there is an Apps 1.0 apk, which is an intent proxy (MarketIntentProxy_1010.apk) which intercepts market calls & attempts to pass them to Amazon's Market. I have also determined that some Gapps sync issues cannot be fixed without seriously modifying (adding functions) to the new Fire OS settings apk. Package/intent calls to this service via adb causes an immediate reboot, as the account/sync settings just are not there. You can backdoor into the account & sync Google app from ICS, but attempting to add or set sync for accounts also causes a reboot.
I need to pull a logcat using the standard host ip, while trying to open the Play Store to see what is intercepting the call & forcing Play Store to close.
Sent from my Nexus 7 using XDA Premium HD app
Here is the basic logcat output showing what is going on while Play Store is opening & being forced closed by the tablet. I have not had a chance to pour through it yet, but I thought I'd post it in case one of the HD greats, (like @Hashcode ) had a chance to stop by. I have a final design review this morning, so I'll be tied up most of the day.
Also, I have noticed some specific google app restrictions in place. There are a few things you can very quickly see in the various text/xml files throughout /data/system/ that are probably interfering with the market connection.
Looks like someone may need to modify com.amazon.dcp to get this working 100% alongside the Amazon features. Also, as I mentioned, looks like some mods need to be made to a few /data/system/* & /data/system/user/* files.
Slowly working through it as I find time. Anyone else?????
Code:
I/ActivityManager(20089): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 pkg=com.android.vending cmp=com.android.vending/.AssetBrowserActivity} from pid 20302
V/DoNotDisturb(20089): Top component: com.android.vending/com.android.vending.AssetBrowserActivity
W/PackageManager(20089): Launching com.android.vending (32107) with AMZ_APP_GID
I/ActivityManager(20089): Start proc com.android.vending for activity com.android.vending/.AssetBrowserActivity: pid=29195 uid=32107 gids={72107, 3003, 1015, 1028, 9001}
D/ActivityManager(20089): reply from CABL: Success
D/ActivityManager(20089): ?Ç?Ç?Ç?Ç?Ç?Ç?Ç?Ç?Ç?Ç?Ç?Ç?Ç?Ç?Ç?Ç?Ç?Ç?Ç?Ç?Ç?Ç?Ç?Ç
I/AmazonPhoneWindowManager(20089): repositioning status bar
D/WindowManager(20089): openingActivityName = com.android.vending.AssetBrowserActivity, animAttr = 8
V/DoNotDisturb(20089): Top component: com.android.vending/com.android.vending.AssetBrowserActivity
D/QcConnectivityService(20089): reportNetworkCondition(1, 0)
D/QcConnectivityService(20089): Actual State: DefaultConnectivityState, Current State: DefaultConnectivityState.processMessage what=104
D/QcConnectivityService(20089): Actual State: DefaultConnectivityState, Current State: DefaultConnectivityState.processMessage what=5006
D/QcConnectivityService(20089): handleInetConditionChange: net=1, condition=0,mActiveDefaultNetwork=1
D/QcConnectivityService(20089): handleInetConditionChange: starting a change hold
I/ActivityManager(20089): Displayed com.android.vending/.AssetBrowserActivity: +323ms
I/installd( 340): free_cache(1375058) avail 52834697216
D/Resolver(20215): icon resource drawable 2130837581
D/Resolver(20215): icon resource drawable 2130837611
D/Resolver(20215): icon resource drawable 2130837611
D/Resolver(20215): icon resource drawable 2130837581
E/AndroidRuntime(29195): FATAL EXCEPTION: download-manager-thread
E/AndroidRuntime(29195): java.lang.NullPointerException
E/AndroidRuntime(29195): at android.os.Parcel.readException(Parcel.java:1431)
E/AndroidRuntime(29195): at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:185)
E/AndroidRuntime(29195): at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:137)
E/AndroidRuntime(29195): at android.content.ContentProviderProxy.insert(ContentProviderNative.java:420)
E/AndroidRuntime(29195): at android.content.ContentResolver.insert(ContentResolver.java:867)
E/AndroidRuntime(29195): at com.google.android.finsky.download.DownloadManagerImpl$1.run(DownloadManagerImpl.java:43)
E/AndroidRuntime(29195): at android.os.Handler.handleCallback(Handler.java:747)
E/AndroidRuntime(29195): at android.os.Handler.dispatchMessage(Handler.java:92)
E/AndroidRuntime(29195): at android.os.Looper.loop(Looper.java:151)
E/AndroidRuntime(29195): at android.os.HandlerThread.run(HandlerThread.java:60)
W/ActivityManager(20089): Force finishing activity com.android.vending/.AssetBrowserActivity
D/ActivityManager(20089): reply from CABL: Success
D/ActivityManager(20089): ?Ç?Ç?Ç?Ç?Ç?Ç?Ç?Ç?Ç?Ç?Ç?Ç?Ç?Ç?Ç?Ç?Ç?Ç?Ç?Ç?Ç?Ç?Ç?Ç
D/WindowManager(20089): openingActivityName = com.amazon.kindle.otter.Launcher, animAttr = 4
W/InputDispatcher(20089): channel '41d66268 com.android.vending/com.android.vending.AssetBrowserActivity (server)' ~ Consumer closed input channel or an error occurred. events=0x9
E/InputDispatcher(20089): channel '41d66268 com.android.vending/com.android.vending.AssetBrowserActivity (server)' ~ Channel is unrecoverably broken and will be disposed!
W/InputDispatcher(20089): Attempted to unregister already unregistered input channel '41d66268 com.android.vending/com.android.vending.AssetBrowserActivity (server)'
I/AmazonPhoneWindowManager(20089): repositioning status bar
I/WindowState(20089): WIN DEATH: Window{41d66268 u0 com.android.vending/com.android.vending.AssetBrowserActivity}
I/ActivityManager(20089): Process com.android.vending (pid 29195) has died.
V/DoNotDisturb(20089): Top component: com.amazon.kindle.otter/com.amazon.kindle.otter.Launcher
D/Resolver(20215): icon resource drawable 2130837581
D/Resolver(20215): icon resource drawable 2130837605
D/Resolver(20215): icon resource drawable 2130837611
D/Resolver(20215): icon resource drawable 2130837611
D/Resolver(20215): icon resource drawable 2130837605
D/Resolver(20215): icon resource drawable 2130837581
W/InputMethodManagerService(20089): Got RemoteException sending setActive(false) notification to pid 29195 uid 32107
D/QcConnectivityService(20089): Actual State: DefaultConnectivityState, Current State: DefaultConnectivityState.processMessage what=105
D/QcConnectivityService(20089): Actual State: DefaultConnectivityState, Current State: DefaultConnectivityState.processMessage what=5007
D/QcConnectivityService(20089): sendStickyBroadcast: action=android.net.conn.INET_CONDITION_ACTION
D/QcConnectivityService(20089): handleInetConditionHoldEnd: net=1, condition=0, published condition=100
E/ChargeProtectionService(20089): Read failed, /sys/class/power_supply/smb347_usb/device/charge_input not exist!
Last one?
Maybe not.
GSLEON3 said:
This thread should be kept relatively clean & free of posts or comments not directly related to getting all Gapps working. Logcats & other reps via terminal or adb should only be posted if you know what you are looking at & for, or if a Dev asks you specifically for something. If you have a specific thought or idea, please feel free to participate, but also, please keep this easy to browse & search through for the folks working on getting everything working.
I have so far been able to get almost all Google apps working, including G+, Hangouts, Chrome, Gmail, Play Books, Movies, Music, Newsstand, Play Services (100%, all sub-menus), Google Now/Search, Voice, Maps & even YouTube. I can post pics when I get to a laptop & have a minute, but they'll just show that all these are working for the most part.
Play Store is a conundrum. It will work with some changes that effectively kill the Amazon service most of us bought the tablet for & use most, but I'm still hopeful that integration will be possible as dual boot does not interest me.
So far, I have been able to determine that there is an Apps 1.0 apk, which is an intent proxy (MarketIntentProxy_1010.apk) which intercepts market calls & attempts to pass them to Amazon's Market. I have also determined that some Gapps sync issues cannot be fixed without seriously modifying (adding functions) to the new Fire OS settings apk. Package/intent calls to this service via adb causes an immediate reboot, as the account/sync settings just are not there. You can backdoor into the account & sync Google app from ICS, but attempting to add or set sync for accounts also causes a reboot.
I need to pull a logcat using the standard host ip, while trying to open the Play Store to see what is intercepting the call & forcing Play Store to close.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
How did you get hangouts to work? What changes does Play Store need to work? Maybe xposed framework is the solution...
I'm rooted 7 hdx and tried android cowboys tutorial on putting Google play on kindle HD. I applied vending.apk within systems folder .able to read write with es3 . I'm sure you will figure it out..let me know if I could help..
Sent from my DROID RAZR HD using Tapatalk
Here is the log file from when I try to launch the Play store.
View attachment Log_2013-11-26_22-28-25.txt
How about posting the steps to get it working while killing the Amazon stuff? not every wants the Amazon app store and prime. I don't have a prime account for starters and no credit card on file with Amazon so I am unable to use their all store so I don't care if they stop working. I was thing you could put those steps out now for those of us who don't care about the Amazon stuff while you guy try and figure out how to get them playing nice together.
kholdstare said:
Here is the log file from when I try to launch the Play store.
View attachment 2417337
Click to expand...
Click to collapse
What version of framework, GMS & market are you using? You are getting a whole ton more errors thrown than I am.
Montisaquadeis said:
How about posting the steps to get it working while killing the Amazon stuff? not every wants the Amazon app store and prime. I don't have a prime account for starters and no credit card on file with Amazon so I am unable to use their all store so I don't care if they stop working. I was thing you could put those steps out now for those of us who don't care about the Amazon stuff while you guy try and figure out how to get them playing nice together.
Click to expand...
Click to collapse
When I get the chance, I will try to put everything back together the way I did the first time I got it to work, but It was using older framework & apps with a host change & some intent proxy changes to stop AMZ market from intercepting. To be honest, once I realized it broke everything, I pretty much moved on, since I am a prime member & there are no roms anyway. I've had a dozen or more resets & restores since then & I never thought there'd be anyone buying an HDX that didn't care about Amazon services. I still have the files (albeit unseperated), but I'll have to go back & try to hit the steps again, because they only worked when installed & booted in a specific order.
It will be a while before I get back to anything HDX related though, I am at work, trying to get everything billed out as this is our month end & I will be traveling for Thanksgiving tonight, back on Monday. I'll try to slip away to play, but it pisses the wifey off, so...
EDIT: One last thing, it will not install extra data for apps that require it, like MC4, Asphalt, Madden, etc. & it will only show a fraction of the apps as compatible, which may be because of DPI settings, maybe because of model id or fingerprint, IDK, like I said, I moved on because it broke what I most care about, preserving Amazon Service.
GSLEON3 said:
I've had a dozen or more resets & restores since then & I never thought there'd be anyone buying an HDX that didn't care about Amazon services.
Click to expand...
Click to collapse
Lots of people here would it seems, myself included. I only bought the tablet once I knew we would be able to use root to get rid of all Amazon stuff and use the Google store and services.
Using Prime after rooting
I would like to know if I root a Kindle Fire HDX7", will i still be able to use prime? e.g. get games and gmail from play store and still use the functionality of prime e.g. free books etc..
Sorry for the stupid question.
EniGmA1987 said:
Lots of people here would it sI boughyself included. I only bought the tablet once I knew we would be able to use root to get rid of all Amazon stuff and use the Google store and services.
Click to expand...
Click to collapse
Count me in, too. I don't give sh*t about amazon stuffs. I bought the tablet for its hardware only.
Does anyone know if there is a way to make the Google apps I added look HD in the carousel?
Newerabs said:
Does anyone know if there is a way to make the Google apps I added look HD in the carousel?
Click to expand...
Click to collapse
No. Sideloaded apps will have lower quality icons in the carousel. I tried Unicon to do a system wide icon replacement but that didn't work. If someone finds a way to do it, I'd be interested to know as well.
Seems download service have some compatible problem with Play Store?
Bebobwolf said:
I would like to know if I root a Kindle Fire HDX7", will i still be able to use prime? e.g. get games and gmail from play store and still use the functionality of prime e.g. free books etc..
Sorry for the stupid question.
Click to expand...
Click to collapse
Root won't affect any amazon functionality
Sent from my DROID RAZR HD using Tapatalk
Thank you GSLEON3 for this initiative. I am OK with not having access to the play store itself as long as most of the important Google apps work with no issues.
sm_x said:
Thank you GSLEON3 for this initiative. I am OK with not having access to the play store itself as long as most of the important Google apps work with no issues.
Click to expand...
Click to collapse
+1
I think the android download provider is open source ? Did someone think to compile it with some debug code around ?
Sent from my Nexus 7 using xda app-developers app
I had high hopes (very high!) that I could get tasker to run on the ouya, unfortunately I have not had any luck as of yet.
Maps was installed, as was a few files that needed to be manually installed in /system, but unfortunately neither seemed to work.
Has anybody had any luck? Please let me know if you did, I had big plans for this little system and tasker was a key piece to it.
Thanks.
Well, apparently I'm batting 1000 tonight on threads.
A reboot allowed instillation of the tasker trial version.
It looks like everything works, or as much as you would expect for the ouya. I did two test tasks. First was just a screen popup, which obviously worked great. The other was a reboot to test root access, and this also worked perfect (say hello to automated weekly reboots!).
Now, to see if autoremote can be made to work, and then on to autovoice or utter! and the inherently difficult prospect that will be.
Snoman002 said:
Well, apparently I'm batting 1000 tonight on threads.
A reboot allowed instillation of the tasker trial version.
It looks like everything works, or as much as you would expect for the ouya. I did two test tasks. First was just a screen popup, which obviously worked great. The other was a reboot to test root access, and this also worked perfect (say hello to automated weekly reboots!).
Now, to see if autoremote can be made to work, and then on to autovoice or utter! and the inherently difficult prospect that will be.
Click to expand...
Click to collapse
Please periodically update this thread with your progress? Curious to follow suit, though don't have the time to help in the investigations
A few issues with tasker itself, such as I can't download from Google play, it won't recognize my original order #, i can't find 'my' .apk, basically can't get my purchased version working and am stuck on the 7 day trial version. As for functionality it works great.
Current main task is to start XBMC if Autoremote received a certain message, as well as sending a message when xbmc is open and a different one when it closes.
On my tablet when I fire up the Yatse app, Tasker checks to see if XBMC is running, if not it displays a popup asking if I want to start xbmc. If I say yes it sends a command through autoremote which is what triggers tasker to start xbmc.
OK, a few things I have found.
Originally I could not download Tasker through the Play Store as the Ouya showed up as 'incompatible', however after a Play Store crash that removed it from my system, and subsequent reinstall, I can now download it from Google Play. I don't know why this was, but when I first did the play store mod I didn't have busybox installed, I did for the reinstall. I don't need the play version however as I was able to get the 'Trial' version validated, which is good as the direct download has added functionality (that I will never use). To validate the trial version you need to find the 15 digit order number (not the 16 digit Google provides in the email). This is best accomplished by using the 'Contact Crafty Apps' link in the email, and then finding Tasker, the 15 digit order number should then be visible. This only works if you bought Tasker before March 2013 though, otherwise you will need the Play store version (thanks Google :/)
To get Tasker to run you need to be Rooted and move two Google files to the proper location on the Ouya. Tasker will not run without the Google maps framework and oddly enough installing Google maps doesn't install the full framework. You can get these files by flashing the gapps package with CWM, or just install the two files themselves. To get the files unzip the gapps package, I think in the 'framework' folder. You need to move com.Google.android.maps.XML to /system/etc/permissions, and move com.Google.android.maps.jar to /system/framework. This WILL require you to remount /system as writeable. ES File Explorer worked for me (download an old version, 3.0.4 maybe, as the newest Play store version crashes), it was the only free root access file manager to work for me. Remount /system back to the way it was. BTW, I did all of this without adb, it was all done on the system itself with some help from dropbox (unzipped on my nexus, it was easier).
Tasker itself works great and I currently have it sending messages through autoremote to update variables on my other devices, this triggers a popup that asks if I want to start XBMC when I start my XBMC remote app (only if XBMC isn't running). If I select yes then it sends an Autoremote message that triggers a Tasker profile that starts XBMC. I also have Utter! setup to trigger the 'Start XBMC' Auto remote message on my Nexus
My next two tasks will be for an automatic nightly reboot, and a task that sends the Ouya into sleep mode when I start my alarm clock app on my nexus. I'm still trying to think of good ideas to implement. I hope to get a microphone working to use voice commands directly on the Ouya, and my dream is for an IR blaster to work so the Ouya could turn on my TV with voice commands (old TV)
Snoman002 said:
OK, a few things I have found.
Click to expand...
Click to collapse
Wow! I really commend you for your perseverance and willingness to share your experience and findings...people don't realize how much this helps others.
Scenes Working
Hey Snoman002,
I have my Ouya rooted and found a Tasker that can be used to mount and unmount NFS mounts. I have the two google maps files installed and have version 4.2 of Tasker installed. When i try to open the scene or even create a new one Tasker closes and goes back to the Make Menu. Have you seen a similar thing with the version you have been using ?
Thanks
Techhhead33
Techhead33 said:
Hey Snoman002,
I have my Ouya rooted and found a Tasker that can be used to mount and unmount NFS mounts. I have the two google maps files installed and have version 4.2 of Tasker installed. When i try to open the scene or even create a new one Tasker closes and goes back to the Make Menu. Have you seen a similar thing with the version you have been using ?
Thanks
Techhhead33
Click to expand...
Click to collapse
Sadly, other than getting it running initially I have done nothing more with Tasked on my ouya.
Your trying to make a scene in tasked? Scenes are really only for overlays and custom menus (drastic oversimplification I know). I fail to see the need for the complication of a scene just for mounting and unmounting. Perhaps you could change the tasker task to a simple popup menu (which now that I think about it may be a scene...). Popups worked for me, but that's all I can say about it.
Sorry, I'm not here much anymore as my ouya just runs xbmc now. I will try and check in more often.