Related
So I updated to FroYo manually thanks to the methods posted here. I've nearly reinstalled all my apps with the exclusion of one; Square. I cannot find it in the market and thought maybe the dev pulled it, but it shows up in 2.1 and web-based market browsers, just not in 2.2. Anyone else experiencing this? Can I just force the apk onto the phone somehow?
icanhazxda said:
So I updated to FroYo manually thanks to the methods posted here. I've nearly reinstalled all my apps with the exclusion of one; Square. I cannot find it in the market and thought maybe the dev pulled it, but it shows up in 2.1 and web-based market browsers, just not in 2.2. Anyone else experiencing this? Can I just force the apk onto the phone somehow?
Click to expand...
Click to collapse
Same here.. seems like the copy protected apps are having problems.
This is not root or something else regarded - everyone has these issues.
Regards
Great to hear I'm not alone, but being an early adopter can sometimes blow (in the BAD way) =\
Is this being discussed in another thread? I did a search prior to posting and came up empty
EDIT: Mods, thanks for moving this to the appropriate forum. I've seen mention of this issue appear in various threads, though no thread of it's own. Will wait for devs to catch up with 2.2
I reported the same problem on modaco last night... I'm sure google will enable de protected apps this week, just a slight oversight on their side.
i had same problem, just put them apk on your sd card and install it. if it is being a stubborn app like a certain few just copy/paste or move them to data/private-app and install from in there. should take care of it 4 u.
Same problem here (Tapatalk Pro and Extended Controls missing).
when you create an app you can set a max api level to support, or not.
applications that have that set won't show on newer devices.
exzeus, square, and a few others seem to have done it...
give them about a month or so and you should see them come around.
icanhazxda said:
Will wait for devs to catch up with 2.2
Click to expand...
Click to collapse
reporting in for the same problem!
My App ICE Donate wasn't found either.. I removed the copy protection until Froyo is officially listed - it can be found and downloaded again
I'm missing cachemate, I only see the free version and I've check the box for all sources for apps. astro will not install from my backups
-------------------------------------
Sent via the XDA Tapatalk App
found out if you sign in via wifi (as I've been doing - maybe even if you skip update at the beginning) things don't work right with the market...since my account is suspended I eventualyl signed in with my cousins sim and yea, it all works fine now...
AbsoluteDesignz said:
found out if you sign in via wifi (as I've been doing - maybe even if you skip update at the beginning) things don't work right with the market...since my account is suspended I eventualyl signed in with my cousins sim and yea, it all works fine now...
Click to expand...
Click to collapse
This cant be the reason. i did only do signin via edge!
Having the same issue here. Wife's N1 can't find WeatherBug Elite, or the Helix Launcher in the market. Even after reboot.
Same. Paul actually fixes it in his roms by changing the Rom fingerprint. Some of the unofficial nexus updates he integrated did the same thing to protected apps. Once fingerprint was changed, it seemed to have done the magic. I'm guessing that he will do the same next week for froyo.
Same here my paid app wont show up which means I may be losing sales so I'm pissed right now
Yeah, so no MLB app at the moment... which makes me unhappy.
Any word on an official response from Google yet on this issue?
theres a fix in this thread:
http://forum.xda-developers.com/showthread.php?p=6572697#post6572697
punk4bc said:
theres a fix in this thread:
http://forum.xda-developers.com/showthread.php?p=6572697#post6572697
Click to expand...
Click to collapse
Good looking out. Google needs to address this fast though for the non tech people (and potential app customers)
t0mmy said:
Good looking out. Google needs to address this fast though for the non tech people (and potential app customers)
Click to expand...
Click to collapse
the non tech people you speak of won't be running Froyo
Just an FYI, I installed it and a bunch of stuff I couldn't find in the market before is there. ( I doubt it though )
http://www.megaupload.com/?d=P3SVF3IE
https://sites.google.com/site/droidlife24/home/Vending_2_2_11.apk?attredirects=0&d=1
Let me know what you think, I've had problems, so use at your own risk ( I should have put this earlier, I hope it didn't hurt anyone, as always back up first )
* I have been having wifi issues since this update. When it comes out of sleep the wifi wont connect automatically
might be jumping the gun trying market fix.
sixvoltsystem said:
might be jumping the gun trying market fix.
Click to expand...
Click to collapse
What do you mean? Did it not work?
Jim
sixvoltsystem said:
Just an FYI, I installed it and a bunch of stuff I couldn't find in the market before is there.
http://www.megaupload.com/?d=P3SVF3IE
https://sites.google.com/site/droidlife24/home/Vending_2_2_11.apk?attredirects=0&d=1
Let me know what you think
Click to expand...
Click to collapse
Cool.. Just loaded it on vegan beta 5.1. Seems to work just fine. Don't know if I see any more stuff, but never really had a problem finding things with the other ones.
I do notice that the appearance seems crisper. Like maybe they are using a higher quality. Or, maybe not.
Still the same for me. Stars still truncated. Missing apps still missing.
The new apk is about 600 MBA larger than earlier one.
Jim
Just for fun I went ahead and did the market fix again. Didn't need to but I saw the earlier post and was curious. I never could get it to open after the first reboot. Had to reboot again. Then once it started working I have noticed more of the "android.process.acore" errors, and server errors then with the older one. I will be rolling back to a previous version myself since this doesn't seem to really make anything better.
I wonder if there should be an updated GoogleServicesFramework with this?
Jim
jimcpl said:
I wonder if there should be an updated GoogleServicesFramework with this?
Jim
Click to expand...
Click to collapse
Kind of wonder that myself. Did you notice any difference in the look? Like a higher res look for the fonts? Or was I just seeing things? That would sort of make sense for the size difference of the file I guess..
And I thought I was doing good. LoL dag nabbit
Sent from my VEGAn-TAB-v1.0.0B5.1 using Tapatalk
sixvoltsystem said:
And I thought I was doing good. LoL dag nabbit
Sent from my VEGAn-TAB-v1.0.0B5.1 using Tapatalk
Click to expand...
Click to collapse
You did fine! Never know if it is cool or not until you try....
Sprdtyf350 said:
Kind of wonder that myself. Did you notice any difference in the look? Like a higher res look for the fonts? Or was I just seeing things? That would sort of make sense for the size difference of the file I guess..
Click to expand...
Click to collapse
It might be, but it's really hard to discern.
Jim
P.s. I went back also.
Sprdtyf350 said:
You did fine! Never know if it is cool or not until you try....
Click to expand...
Click to collapse
Ditto...
Jim
Works for me
I'm running vegan 5.1 with pershoots latest kernel and here are my findings thus far. I backed up market with titanium and installed the update, immediately opened market. Everything looks to be there, I searched for a few things and installed one or two. I looked for adw and couldn't find it, I did see its themes but not the app. Rebooted, loaded up market no fc's, until I tried to roll back to previous version to look for adw because I am almost certain it was there before. Interestingly I did see appbrain which I've never been able to get before. Never tried market fix, and did not notice any image improvement. Anyone know for certain what to look for to see if it actually improves previous market? I'm going to try and fix my market now and will report back if anyone's interested.
I installed via the apk (there is also an update.zip available) and all working well. No reboot or clearing Google Services Framework required.
I had previously preformed the well documented market fixes but could never quite get the entire market. Everything appears to show up now.
I'm not sure it is complete I can't find a few things. But then again I found a bunch of things I couldn't find before either. Catch 22 yet again.
anyone else having a problem with 'Media Volume' not working after this update? The rocker doesn't work, I tried to go in the settings (I had to unmute and turn the system sound back up - no dice), I even tried to play a video and turn up the sound using the software controls within that program....nothing works.
How do I revert back? Where is the old .apk located?
....also had to turn my wi-fi on with each reboot, which is new.
Running Vegan5.1
I think it would be most helpful if you guys actually listed the names of the titles of the apps that you either DO or DO NOT see once you have tried this. Just might help in the troubleshooting aspect. For what its worth.
ckelly,
search xda for market or vending.apk and you will find many versions to play with
Volume corrected on reboot #2.
Wi-Fi still needs to be manually connected..
@sixvolt
Since this appears to not improve things, you must have had even less apps show up than we did and this update brought you to par with the rest of us. Everything is relative
After reading some positive reviews and seeing a video showing it working on a TouchPad running Android, I decided to buy DeadSpace. I made the purchase through market.android.com, but I can't download it because the Market app says it's not compatible with my device. Does anyone have a recommendation for how to download this game now that I've bought it? Can I change the device ID or something to make the market think my TouchPad is something that is compatible?
Thanks!
try changing your build.prop info to the same as the SG-i9100
In the build.prop change the following lines from:
ro.product.model=Touchpad
ro.product.brand=HP
to
ro.product.model=GT-i9100
ro.product.brand=samsung
rogabean said:
try changing your build.prop info to the same as the SG-i9100
In the build.prop change the following lines from:
ro.product.model=Touchpad
ro.product.brand=HP
to
ro.product.model=GT-i9100
ro.product.brand=samsung
Click to expand...
Click to collapse
u didn't change manufacturer on purpose?
Wasn't needed.
By the way I tested and this didn't make this particular game show up. Will look into some more when I get a chance.
Sent from my GT-i9100 using Tapatalk
Actually this did work for me and I was able to download the game. I did have to clear cache on Market and clear data on Google Services Framework, then reboot, but once I did, it showed up. I had to perform these steps on my Nook Color back in the day as well...
So now that it's installed, the game starts and says it needs to download 300+MB. I tell it to do so and it immediately shows an empty dialog with only an "Exit" button, after which it exits. I can't get past that. Any ideas?
Also, I installed Chainfire3D and the Nvidia plugin. Is that necessary? Is that correct for the TouchPad? Is there any other configuration that I should do for this to work well?
Thanks much for the help!
You could try the other plugins powervr or qualcomm
Glad you were able to get it downloaded. Not sure on the download issue though.
If you have another supported device you could try downloading the files on it and moving them over - or see if someone has posted the sdcard files somewhere.
Have the exact same issue with Dead Space. Asphalt 6 HD works like a charm though. I'm looking for answers but I get the same response.... wash, rinse, repeat (wipe, clear cache, repeat thrice...)
Haven't tried doing the 3-peat yet. If anyone else has and has achieved success after having the same issue with this game, let us know!
Sent from my HTC Pyramid using Tapatalk
Success! Took a while though.....
So I updated my build.prop to the Pyramid device... (sorry, no link where I found that, but GT-i9100 should do fine too). Then I side loaded the main apk like suggested in previous threads. Then I copied the root folder from my Evo where I already had it installed to my PC and transferred the folder to my TP like it was already fully installed.
From there it still said my device wasn't supported, so I installed the powervr plugin for chainfire3d, used in-app settings through chainfire.
Here's where it got weird: I kept getting the same error over and over of my device not being supported. Then my wifi connected and when I ran the game, it immediately searched for an update. Apparently it found one! Suddenly I'm up and running, smooth as silk.
Now gonna try Real Racing 2!
Sent from my HTC Pyramid using Tapatalk
SCWells72 said:
Actually this did work for me and I was able to download the game. I did have to clear cache on Market and clear data on Google Services Framework, then reboot, but once I did, it showed up. I had to perform these steps on my Nook Color back in the day as well...
So now that it's installed, the game starts and says it needs to download 300+MB. I tell it to do so and it immediately shows an empty dialog with only an "Exit" button, after which it exits. I can't get past that. Any ideas?
Also, I installed Chainfire3D and the Nvidia plugin. Is that necessary? Is that correct for the TouchPad? Is there any other configuration that I should do for this to work well?
Thanks much for the help!
Click to expand...
Click to collapse
Anyone know a solution for this? I'm getting the same issue. I'm running Jensen 2.8 lite with the buildprop changes and also installed chainfire3d with all the pluggins. No go
Okay, I used my Nook Color to download the data, transferred that back to the TouchPad, and launched it successfully. When it starts rendering 3D, though, it's all white with no textures. What Chainfire3D settings are folks using on the TouchPad that work?
I have read somewhere to use the following option for chainfire 3D as this is the GPU-manufacturer:
qualcomm
it may be worth a try.
justfor4 said:
I have read somewhere to use the following option for chainfire 3D as this is the GPU-manufacturer:
qualcomm
it may be worth a try.
Click to expand...
Click to collapse
Yeah, I've tried all three plugins with the various options enabled and disabled. No go. Has anyone gotten this going with A3.5? Between this and the lockups in Currents and other Webkit apps, I'm strongly considering going back to the previous alpha.
Okay, I finally got this working. I moved back to A2.1 which didn't actually fix anything (though it does seem to have resolved the lockups in Webkit-based apps like Google Reader and Currents, though they're not as smooth when they're working), but then I purchased the full version of Chainfire 3D and launched Dead Space using per-app settings. Suddenly it worked perfectly! I don't know why that would make a difference...perhaps I just didn't know how to use the free version. Either way, $4 is a small price to pay for the added flexibility of the full version of Chainfire 3D, and of course now I have a working, silky smooth Dead Space! Woohoo!
UPDATE: Okay, I know the magic incantation now. This works under A3.5 (and therefore presumably XRON) just fine if you use the PowerVR plugin in ChainFire 3D. I didn't have to reduce texture quality or anything else, just set the plug-in to PowerVR. I hope this helps others get this really nice looking game going on their TouchPads!
Hi ya, i think i had 5.3.2.0 and rooted it via rootjunky's tool (kingroot then supersu) and flashed back to 5.3.1. blocked OTA updates and went for the custom Nexus ROM, kept coming up with google errors so dumped that and tried CM12.1 and still got various other errors so read on one of rootjunkys feeds that someone just gave up and kept 5.3.1. and just removed the "crap" as he called it so i have come to the conclusion i'm going to do that as well.
So as i stand right now i am at 5.3.1. rooted blocked OTA updates and kingroot has gone and supersu is in, playstore is due to go on via the 5thGenSuperTool and change the stock launcher to Nova, that is as far as i can go on my own, been hunting around on here for threads that help remove the unwanted Amazon which to be honest is all of them i think but i'd like to keep Calender/Calc/clock/camera app but even some of these need you to register the tablet before i can go any further, so as it stands right now what is best for me should i register the tablet or not, if yes should it be in real name or moody name?
Also i see mention of lock screen and adverts, sorry for the next question the lock screen is that the screen you come to first where you have to swipe upwards to see icons? And why have i not seen any adverts yet, is it because i have not registered the tablet yet?
Also can you suggest any other threads for me to look at regarding getting rid of the rubbish or bloatware just stuff i don't need, i have come across the following but just wondering if i have missed anything you can think will help me in my case.
https://forum.xda-developers.com/amazon-fire/general/removing-lock-screen-ads-root-t3218946
https://forum.xda-developers.com/amazon-fire/general/adb-shell-pm-hide-bloat-amazon-t3221466
https://forum.xda-developers.com/amazon-fire/general/amazon-fire-2015-tips-tricks-t3214544
https://forum.xda-developers.com/amazon-fire/general/safe-to-remove-5-0-1-bloatware-2015-t3239582
Now i'll be the first to admit i have not read all of these threads yet, that is my plan next but i just wanted to see if i'm missing anything special that you think i should know before i go any further and also unsure what registering the tablet will do.
All1
Allonewordinuk said:
Hi ya, i think i had 5.3.2.0 and rooted it via rootjunky's tool (kingroot then supersu) and flashed back to 5.3.1. blocked OTA updates and went for the custom Nexus ROM, kept coming up with google errors so dumped that and tried CM12.1 and still got various other errors so read on one of rootjunkys feeds that someone just gave up and kept 5.3.1. and just removed the "crap" as he called it so i have come to the conclusion i'm going to do that as well.
So as i stand right now i am at 5.3.1. rooted blocked OTA updates and kingroot has gone and supersu is in, playstore is due to go on via the 5thGenSuperTool and change the stock launcher to Nova, that is as far as i can go on my own, been hunting around on here for threads that help remove the unwanted Amazon which to be honest is all of them i think but i'd like to keep Calender/Calc/clock/camera app but even some of these need you to register the tablet before i can go any further, so as it stands right now what is best for me should i register the tablet or not, if yes should it be in real name or moody name?
Also i see mention of lock screen and adverts, sorry for the next question the lock screen is that the screen you come to first where you have to swipe upwards to see icons? And why have i not seen any adverts yet, is it because i have not registered the tablet yet?
Also can you suggest any other threads for me to look at regarding getting rid of the rubbish or bloatware just stuff i don't need, i have come across the following but just wondering if i have missed anything you can think will help me in my case.
https://forum.xda-developers.com/amazon-fire/general/removing-lock-screen-ads-root-t3218946
https://forum.xda-developers.com/amazon-fire/general/adb-shell-pm-hide-bloat-amazon-t3221466
https://forum.xda-developers.com/amazon-fire/general/amazon-fire-2015-tips-tricks-t3214544
https://forum.xda-developers.com/amazon-fire/general/safe-to-remove-5-0-1-bloatware-2015-t3239582
Now i'll be the first to admit i have not read all of these threads yet, that is my plan next but i just wanted to see if i'm missing anything special that you think i should know before i go any further and also unsure what registering the tablet will do.
All1
Click to expand...
Click to collapse
Hum - not aware of any persistent errors on CM 12.1. Stable, responsive ROM.
Davey126 said:
Hum - not aware of any persistent errors on CM 12.1. Stable, responsive ROM.
Click to expand...
Click to collapse
Yea i did get a couple but forgot to take not of what they were, i'll give CM 12.1 another go tonight and post back just for your info on what errors i got .
All1
Allonewordinuk said:
Yea i did get a couple but forgot to take not of what they were, i'll give CM 12.1 another go tonight and post back just for your info on what errors i got .
Click to expand...
Click to collapse
No ROM is perfect - custom or stock. Installation errors/omissions are a leading contributor to less than satisfactory outcomes. Post your experiences w/supporting detail; someone will try to help.
Davey126 said:
No ROM is perfect - custom or stock. Installation errors/omissions are a leading contributor to less than satisfactory outcomes. Post your experiences w/supporting detail; someone will try to help.
Click to expand...
Click to collapse
I'm having no issues with the ROM itself SuperSu has been a nightmare to update, i tried TWRP but for the life of me every thread i try to use (here and elsewhere) it fails to works and just lease a blank screen, if i remember last time my problems came with gapps and wondering what version of gapps i should use i have seen pico spoke about but can't even get that far, had the damm thing since black friday and to be honest i'm getting fed up with it
All1
Supersu has been updated and for the life of me i have no idea why but i don't care it's done, now to look at gapps
Well just to close this down, i have it working now my major problem was trying to install gapps v6 on it but once i had worked out my error she is fine, i just want to say thanks to everyone who has helped me get it sorted once and for all.
All1
Hey everyone,
So I've been trying to "modernize" my phone, since I'm under the impression that I can get another 2-3 years out of it. So far I have:
-Running 7.1.1 stock rooted w/Franco kernel
-Hacked to include Pixel launcher (works great)
-Hacked to include Assistant (works great)
-Hacked to run Daydream (works great(ish)) -These tutorials are all available online and are pretty simple if you kinda know what you're doing
I bought a Daydream headset and have been playing with the apps. Some seem to work fine, and some won't run, some won't install. This seems like pretty fresh territory, so I haven't found much help online.
I know our phone supposedly doesn't meet the intended hardware specs (thermal characteristics, and GPU speed?), but it sure seems capable enough to me.
-Home screen and remote - works no problem.
-Playstore - works no problem.
-Netflix VR - works no problem.
-Arts & Culture - works no problem.
-Asteroids - This is pretty awesome. It's a demo of an animated episode (not the old game). It has 3D sound, which I wasn't expecting since the Netflix VR app didn't have it.
-Youtube VR - won't install (sideload). A little research, and it sounds like this app won't run on our phone's architecture. As far as I know, I can't force it to run. I'm very interested in getting this to work though.
-NextVR - Launches to blank screen.
-Hello Mars - works no problem. Lacking content it seems.
-JauntVR - works no problem.
-Littlestar - opens to non-side-by-side screen.
-InceptionVR - opens to non-side-by-side screen.
-Etc.. haven't tried very many yet.
For some of these, I wonder... I have my phone "posing" as a Pixel XL. I wonder if it would make a difference if I changed it to Pixel regular instead.
Anyhow, there must be others out there who are interested in exploring Daydream on our Nexus 6. Please share your experiences/expertise or point to relevant threads I may have missed!
Unfortunately I am in the same situation as you are, but I am just as interested in getting it resolved. The Daydream UI and the apps that are working actually work very well. What I found is the apps that are opening single screen are doing so because of our device info. I can go into the build.prop and edit the ro.product.device to marlin instead of shamu the app will open in a side by side screen. The only problem is that my phone reboots after running for a few minutes (even if I am not in daydream). I emailed the app developer of "AFFECTED:The Manor" and he said they will adjust the app requirements in their next update, but we can't expect everyone to be so helpful. We need to come up with a way to edit the build.prop info without causing rebooting. Keep me posted and I will do the same ...
Very cool, glad I'm not alone here.
I did notice that Netflix seemed to have picked out that my device was a Shamu, but luckily at least that app doesn't care.
FYI it looks like a bunch more apps just got added to the in-Daydream app-store. Going to try a few of those, and also trying to get google photos working.
Having trouble with Google Pictures in daydream. I get a message saying there is no daydream content for this app. I tried the same build.prop mod you mentioned, and it did not help with that app. I can confirm it did fix the others which didn't previously work. It threw off my kernel though, so I set it back to Shamu. I didn't experience reboots, but I had it set that way for about 10 minutes only.
Guys remember that there is a reason the nexus 6 didnt make the cut. One of the main reasons being that it wont be getting the vulcan drivers that daydream will need. By forcing it you could damage your device beyond repair. Its a high risk for something that will most likely die out over the next few years.
zelendel said:
Guys remember that there is a reason the nexus 6 didnt make the cut. One of the main reasons being that it wont be getting the vulcan drivers that daydream will need. By forcing it you could damage your device beyond repair. Its a high risk for something that will most likely die out over the next few years.
Click to expand...
Click to collapse
Yes good point. I personally am prepared for the worst, but yeah, disclaimer to others...
I was able to get it to work in safe mode.. But after rebooting I was still logged in but it's like the touch screen is dead and when I move my phone the picture jitters
needleyepoke said:
I was able to get it to work in safe mode.. But after rebooting I was still logged in but it's like the touch screen is dead and when I move my phone the picture jitters
Click to expand...
Click to collapse
Get what to work?
stev067 said:
Get what to work?
Click to expand...
Click to collapse
The daydream app... Isn't that what this forum is about?
needleyepoke said:
The daydream app... Isn't that what this forum is about?
Click to expand...
Click to collapse
We had just been talking about getting specific apps running, so I didn't know if you were referring to a certain app or just Daydream in general. I didn't have any trouble following the guide to get Daydream up and running. You sure you did it right?
stev067 said:
We had just been talking about getting specific apps running, so I didn't know if you were referring to a certain app or just Daydream in general. I didn't have any trouble following the guide to get Daydream up and running. You sure you did it right?
Click to expand...
Click to collapse
I'll go back and check my steps.. Thanks
stev067 said:
Having trouble with Google Pictures in daydream. I get a message saying there is no daydream content for this app. I tried the same build.prop mod you mentioned, and it did not help with that app. I can confirm it did fix the others which didn't previously work. It threw off my kernel though, so I set it back to Shamu. I didn't experience reboots, but I had it set that way for about 10 minutes only.
Click to expand...
Click to collapse
That is going to be the key to getting those apps working, it is pulling info from the build.prop to verify it should run in the dual screen mode. I just can't figure out how to make the edit and have my device run correctly. I noticed when I changed shamu to marlin even some of my apps updated (like camera) to the pixel camera, but it is supposed to run on 64 bit system so it crashed. I think the change will have to take place on the app side, which is unfortunate.
adbFreedom said:
That is going to be the key to getting those apps working, it is pulling info from the build.prop to verify it should run in the dual screen mode. I just can't figure out how to make the edit and have my device run correctly. I noticed when I changed shamu to marlin even some of my apps updated (like camera) to the pixel camera, but it is supposed to run on 64 bit system so it crashed. I think the change will have to take place on the app side, which is unfortunate.
Click to expand...
Click to collapse
Check this article out: http://apcmag.com/how-to-fake-an-android-device.htm/
It's kinda old, but it sounds like there's more lines that may need to be changed besides [ro.product.device].
stev067 said:
Check this article out: http://apcmag.com/how-to-fake-an-android-device.htm/
It's kinda old, but it sounds like there's more lines that may need to be changed besides [ro.product.device].
Click to expand...
Click to collapse
Yea, I had tried all combinations one at a time and all at once and my device would always reboot. I found during the trial and error that only the ro.product.device was what the app was reading, but could not stop the rebooting.