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
Hi,
Im just curious how to track down the reason for reboots with stock ROM and stock kernel, not rooted. I had one random reboot yesterday (when watching trailers in the IMDB app) after almost a week I own N7. I know that one reboot in a week is nothing, but its my new toy and Id like to know how to track down the reason for that in case it happens again.
I found out some threads about this and generally it says I should use LogCat - but I dont know how to use it. So I please ask for help! For now, I started Stability Test (CPU+GPU) and wait ...
Happy New Year, Y'all !!!
EDIT: Ghardashyan a bit lower mentioned hes been having reboots when watching youtube videos. Anybody else having this kind of behavior? Also, I had my reboot when watching trailers in the IMDB app - its playing via youtube, right?
The ONLY reboot I have ever seen, is when the default lockscreen widget gets updated by the marketplace. It's guaranteed to reboot on 4.2. It does it every time on both my Nexus 4 and my Nexus 7.
You will only ever see it, if you remove the default android 4.2 lockscreen time widget and put something else there from the marketplace, and only when that widget gets a marketplace file update.
Perhaps you are seeing this? Do you have auto-update apps enabled???
CrazyPeter said:
The ONLY reboot I have ever seen, is when the default lockscreen widget gets updated by the marketplace. It's guaranteed to reboot on 4.2. It does it every time on both my Nexus 4 and my Nexus 7.
You will only ever see it, if you remove the default android 4.2 lockscreen time widget and put something else there from the marketplace, and only when that widget gets a marketplace file update.
Perhaps you are seeing this? Do you have auto-update apps enabled???
Click to expand...
Click to collapse
I dont have auto-update enabled. I added another time/weather widget to the lockscreen but I dont think it got updated yesterday ... I will remove it and hope it wont reboot again. I sure think it was some app as the stability test goes for 2 hours without problem.
michalurban said:
I dont have auto-update enabled. I added another time/weather widget to the lockscreen but I dont think it got updated yesterday ... I will remove it and hope it wont reboot again. I sure think it was some app as the stability test goes for 2 hours without problem.
Click to expand...
Click to collapse
Its to do with location based services, HD Widgets is a major culprit and stated they were talking to Google to try and resolve the issue, it is also as stated before mainly because of the new lockscreen widgets, which HD Widgets also provide, so the stock widget could also cause the same issue?
Mine have pretty much stopped with the last update of HD Widgets, but it does still occur.
Wilks3y said:
Its to do with location based services, HD Widgets is a major culprit and stated they were talking to Google to try and resolve the issue, it is also as stated before mainly because of the new lockscreen widgets, which HD Widgets also provide, so the stock widget could also cause the same issue?
Mine have pretty much stopped with the last update of HD Widgets, but it does still occur.
Click to expand...
Click to collapse
Just for your information, I dont use HD Widgets
Since you're on stock rom and kernel, I think the best way would be to reset your device and keep track of what applications are installed, one at a time.
My guess is that one of the installed apps are causing it..
Sent from my Nexus 7 using Tapatalk HD
ajhn said:
Since you're on stock rom and kernel, I think the best way would be to reset your device and keep track of what applications are installed, one at a time.
My guess is that one of the installed apps are causing it..
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
I know that, but as it was one reboot only in less than a week, it could take months to track the app down ... :laugh: Im about to restart the device myself and then use alogrec to continually record stuff.
EDIT: Alogrec is not recording a thing, so I rooted my phone. In case of restart, I believe it should be enough to save last_kmsg. Am I right?
michalurban said:
Hi,
Im just curious how to track down the reason for reboots with stock ROM and stock kernel, not rooted. I had one random reboot yesterday (when watching trailers in the IMDB app) after almost a week I own N7. I know that one reboot in a week is nothing, but its my new toy and Id like to know how to track down the reason for that in case it happens again.
I found out some threads about this and generally it says I should use LogCat - but I dont know how to use it. So I please ask for help! For now, I started Stability Test (CPU+GPU) and wait ...
Happy New Year, Y'all !!!
Click to expand...
Click to collapse
I get some occasional reboot when watching Youtube videos... Leaved the stability test for 2 hours, no reboots.
ghardashyan said:
I get some occasional reboot when watching Youtube videos... Leaved the stability test for 2 hours, no reboots.
Click to expand...
Click to collapse
I had my reboot when watching IMDB trailers - which also are on youtube, am I right??
BTW Is your problem repeatable? Eg. is there any time watching youtube that quarantees reboot? Id like to check that ... And are you using the youtube app?
REALLY?
Check out the thread 4.2 Random reboots instead of making new threads.
Sent from my GT-I9100
Correlation does not equal causation and it seems some are eager to go barking up the wrong tree. As has been stated here, as well as confirmed by Google, it is a bug at the OS level. It has nothing to do, per say, with HD Widgets, YouTube, or any individual app. It affects all products running 4.2 and 4.2.1.
Until Google fixes the issue, there are only two guaranteed workarounds- disable location services or downgrade to 4.1.2.
Sent from my Nexus 7 using Tapatalk HD
najaboy said:
Correlation does not equal causation and it seems some are eager to go barking up the wrong tree. As has been stated here, as well as confirmed by Google, it is a bug at the OS level. It has nothing to do, per say, with HD Widgets, YouTube, or any individual app. It affects all products running 4.2 and 4.2.1.
Until Google fixes the issue, there are only two guaranteed workarounds- disable location services or downgrade to 4.1.2.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Thanks, never heard of that. How do I disable Location Services? Should I just turn off the Location access menu? Or is it a service under running services? In that case, which one?
michalurban said:
Thanks, never heard of that. How do I disable Location Services? Should I just turn off the Location access menu? Or is it a service under running services? In that case, which one?
Click to expand...
Click to collapse
Settings › Location. Bear in mind that the tradeoff is that, among other things, Google Now will no longer be functional.
For me, the reboots haven't been annoying enough to warrant disabling it on mine just yet.
Sent from my Nexus 7 using Tapatalk HD
najaboy said:
Settings › Location. Bear in mind that the tradeoff is that, among other things, Google Now will no longer be functional.
For me, the reboots haven't been annoying enough to warrant disabling it on mine just yet.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Great, thanks. :good: I disabled that for now and will turn it on only when I need navigation. I dont use Google Now anyway.
BTW, when Google finds a solution for this, should I expect a full system upgrade?
Just experienced my first random reboot while streaming a flash video on Firefox Beta..
Random reboots are annoying me as well with my stock unrooted n7
Mostly though its during wifi/network activity not just in one app, have had reboots while in youtube, ebay, chrome etc. I have also seen it reboot while in standby
All started from 4.2
Would be interested to know if these reboots are reported back to google?
Sent from my Nexus 7 using xda premium
My Nexus 7 has 38 days uptime, only thing "special" I've done is I've disabled lockscreen widgets:
https://play.google.com/store/apps/details?id=com.wordpress.chislonchow.deviceadminkeyguard
Stock 4.2.1, rooted.
Not sure if this has been questioned already, I'm having a mess around with a few ROMs on my HTC One, if I install a ROM with Sense/HTC ROM on the phone it all works perfectly fine and flawlessly, as soon as I install a Google Edition ROM or CM etc it wont let me download any apps giving me the Error 403 on the Play Store. I've tried all the solutions and none work, wondering if anyone shares the problem or knows a fix.
Thanks, Dan.
Seems like you're out of luck if you've tried "all the solutions".
Sarcasm aside, list what you have done so people know what you've done, how you did it and then maybe they can offer some assistance.
Sent from my HTC One using Tapatalk
bbinder said:
Seems like you're out of luck if you've tried "all the solutions".
Sarcasm aside, list what you have done so people know what you've done, how you did it and then maybe they can offer some assistance.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Well by all the solutions I mean I've literally spent hours doing all the obvious ones, clearing proxies, clearing Google Play Services, Play Store and the Download Managers caches, datas etc. Removed my account, rebooted whilst doing all this. Signed in with a different Google Account, I literally cannot find another solution anywhere, sorry for being vague.
It must be a problem on Google's side. The same thing occurs with my Xperia Z, and I've tried all the fix suggestions on both stock and PA 4.0
Drummerjed said:
It must be a problem on Google's side. The same thing occurs with my Xperia Z, and I've tried all the fix suggestions on both stock and PA 4.0
Click to expand...
Click to collapse
I have just read another thread, and many HTC One's and LG's, even a Nexus 5 and 7 have had the same issue! Lets hope it's fixed soon!
Verified no proxy in APN?
Does it work on home WiFi?
sent from my mobile device
ivehaddan said:
Not sure if this has been questioned already, I'm having a mess around with a few ROMs on my HTC One, if I install a ROM with Sense/HTC ROM on the phone it all works perfectly fine and flawlessly, as soon as I install a Google Edition ROM or CM etc it wont let me download any apps giving me the Error 403 on the Play Store. I've tried all the solutions and none work, wondering if anyone shares the problem or knows a fix.
Thanks, Dan.
Click to expand...
Click to collapse
Maybe it can help:
FEB 11, 2014
Google Play Store is experiencing yet another partial downtime and is bringing up the dreaded 403 error message for a good number of Android users.
Actually this error has come up once in a while, often randomly and without any explanation given afterwards. It's not exactly a fatal error but it does prevent users from downloading or updating apps. It can be an annoyance and an inconvenience at worst.
Unfortunately for users, there isn't really anything they can do about it, other than wait, and maybe complain.
Click to expand...
Click to collapse
i have the same problem before
Chrome fails to load sites regularly. It seems to load, the status bar completes but the page remains blank. The fix is easy enough, switching to a new tab and retrying the webpage/Google search loads the page properly. It's annoying though. Has anyone else experienced this and/or know how to fix it permanently?
Thanks
For me fails to load at first then refresh and works fine. Are you tried uninstall/clear cache/reinstall?
Joseluize said:
For me fails to load at first then refresh and works fine. Are you tried uninstall/clear cache/reinstall?
Click to expand...
Click to collapse
Yeah I have thanks, and refresh continues to fall to load it.
Just my opinion.. Chrome is a terrible browser. There's many superior ones on the play store.
Tho it could be the sites themselves as well.
KJ said:
Just my opinion.. Chrome is a terrible browser. There's many superior ones on the play store.
Tho it could be the sites themselves as well.
Click to expand...
Click to collapse
That was weird I check this thread an instant before I got the email about a reply and there wasn't one. Anyway...
Thanks for the reply, you're probably right. Unfortunately I like the passwords and bookmarks syncing too much.
It's a Chrome bug for sure though. I think something similar used to happen with my Nexus 7 (2013). I don't even really no why I posted it here, it really should be posted on Google's Product Forums.
EvanVanVan said:
That was weird I check this thread an instant before I got the email about a reply and there wasn't one. Anyway...
Thanks for the reply, you're probably right. Unfortunately I like the passwords and bookmarks syncing too much.
It's a Chrome bug for sure though. I think something similar used to happen with my Nexus 7 (2013). I don't even really no why I posted it here, it really should be posted on Google's Product Forums.
Click to expand...
Click to collapse
Chrome is on my debloat list immediately after any ROM flash. Lol
I use dolphin and boat browser.
EvanVanVan said:
Chrome fails to load sites regularly. It seems to load, the status bar completes but the page remains blank. The fix is easy enough, switching to a new tab and retrying the webpage/Google search loads the page properly. It's annoying though. Has anyone else experienced this and/or know how to fix it permanently?
Thanks
Click to expand...
Click to collapse
I haven't had this issue on my VZW Dev X. I'm stock but rooted (via twrp/supersu), no other modifications.
Are you running any mods on your phone?
KidJoe said:
I haven't had this issue on my VZW Dev X. I'm stock but rooted (via twrp/supersu), no other modifications.
Are you running any mods on your phone?
Click to expand...
Click to collapse
I am running the 4.4.2 GPE Rom (http://forum.xda-developers.com/moto-x/development/fxz-xt1053-xt1060-google-play-edition-4-t2715488) on my VZW Dev X. I've got Xposed with Gravity Box installed as well. Similar stuff used to happen with my Nexus 7 like I said, although I also have GB [KK] installed on that too. And it hasn't been a problem on the N7 recently.
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.