Related
Is there any workaround...?
Whats the problem ?
All the apps i have ever bought / downloaded, via the market work fine.
I believe this is what he's talking about
http://www.google.com/support/forum/p/Android+Market/thread?tid=107185eea74e4005&hl=en
http://androinica.com/2009/02/23/some-paid-apps-unavailable-on-unlocked-phones/
It appears that as of February, Google made it so whenever a developer selects the "Copy Protected" option when listing their application on the marketplace, that application will not appear for any rooted phone or developer phone. Basically it seems they did this because a rooted or developer phone can extract the APK file after purchasing an app, and then return it while still keeping the application.
I recently became aware of this today as I was working with a developer to determine why his application would not appear in the market. It's a shame - the majority of the root community is not out there to STEAL apps, we support our developers, I was trying to find his application on the market so I could BUY it. I really wanted to purchase the application and now I have no way to do it, simply because I wanted to use my phone to it's full extent instead of being stuck on the stock firmware.
rabeatz said:
http://www.google.com/support/forum/p/Android+Market/thread?tid=107185eea74e4005&hl=en
http://androinica.com/2009/02/23/some-paid-apps-unavailable-on-unlocked-phones/
It appears that as of February, Google made it so whenever a developer selects the "Copy Protected" option when listing their application on the marketplace, that application will not appear for any rooted phone or developer phone. Basically it seems they did this because a rooted or developer phone can extract the APK file after purchasing an app, and then return it while still keeping the application.
I recently became aware of this today as I was working with a developer to determine why his application would not appear in the market. It's a shame - the majority of the root community is not out there to STEAL apps, we support our developers, I was trying to find his application on the market so I could BUY it. I really wanted to purchase the application and now I have no way to do it, simply because I wanted to use my phone to it's full extent instead of being stuck on the stock firmware.
Click to expand...
Click to collapse
Any example of apps not showing up on the market for us?
Gilliland12 said:
Any example of apps not showing up on the market for us?
Click to expand...
Click to collapse
Search for the application Accudial on the market. It's copy protected. I get 0 results. Thats the one Example I am aware of but it also could be related to the fact that I'm on a 2.0.1 ROM instead of the older ones, switching back to test again. It's kind of hard to determine whether or not there are apps being hidden from us, if we don't know the app exists how are we gonna know it's hidden from our results?
It's because your on a Eclair rom..just searched on the WG 10 (Donut) and got AccuDial and AccuDial Free
Yeah I'm switching back to the latest CM ROM right now. But when I was running 2.0.1/Eclair, I was trying to download an application designed for 2.0 and it did not appear in the market - the developer said the only requirement he placed on it was that the phone be 2.0 or higher, so we came to the conclusion that it was the copy protection blocking the app.
But regardless of that - what about those links in my first post? Google Employees reply in those articles openly admitting that access to copy protected apps have been blocked from rooted and dev phones. Did Google quietly "undo" this between now and then? I can't find anything that says they did.
rabeatz said:
Yeah I'm switching back to the latest CM ROM right now. But when I was running 2.0.1/Eclair, I was trying to download an application designed for 2.0 and it did not appear in the market - the developer said the only requirement he placed on it was that the phone be 2.0 or higher, so we came to the conclusion that it was the copy protection blocking the app.
But regardless of that - what about those links in my first post? Google Employees reply in those articles openly admitting that access to copy protected apps have been blocked from rooted and dev phones. Did Google quietly "undo" this between now and then? I can't find anything that says they did.
Click to expand...
Click to collapse
I can find all of those apps they mention.
Dunno.
rabeatz said:
Yeah I'm switching back to the latest CM ROM right now. But when I was running 2.0.1/Eclair, I was trying to download an application designed for 2.0 and it did not appear in the market - the developer said the only requirement he placed on it was that the phone be 2.0 or higher, so we came to the conclusion that it was the copy protection blocking the app.
But regardless of that - what about those links in my first post? Google Employees reply in those articles openly admitting that access to copy protected apps have been blocked from rooted and dev phones. Did Google quietly "undo" this between now and then? I can't find anything that says they did.
Click to expand...
Click to collapse
They did lift the "block", I know of at least 2 protected apps that I can use, Nesoid and Mobile Defense (not protected anymore but it ised to be)
Right now, I can only find Accudial Free but not Accudial. I'm on Cyan 4.2.9.1.
Maybe that's because I'm not in the US??? Or that I don't have a Google Checkout account???
Thanks!
rabeatz said:
Yeah I'm switching back to the latest CM ROM right now. But when I was running 2.0.1/Eclair, I was trying to download an application designed for 2.0 and it did not appear in the market - the developer said the only requirement he placed on it was that the phone be 2.0 or higher, so we came to the conclusion that it was the copy protection blocking the app.
But regardless of that - what about those links in my first post? Google Employees reply in those articles openly admitting that access to copy protected apps have been blocked from rooted and dev phones. Did Google quietly "undo" this between now and then? I can't find anything that says they did.
Click to expand...
Click to collapse
That was a long time ago.
supremeteam256 said:
That was a long time ago.
Click to expand...
Click to collapse
The fair labor standards act was passed in 1938. Still in effect today. Just because Google made the change 10 months ago doesn't mean it suddenly was removed.. Whenever I search on the topic all I can find is info that says that access to copy protected apps been disallowed, can't find any article that mentions them removing the block.
I'm not saying it hasn't been removed, but it's kind of hard for me to know whether or not i'm being blocked from applications, I don't know what ones are copy protected and what ones aren't, or if theyre being blocked from me, because they simply wouldn't show up and I wouldn't even know they exist.
If the block has in fact been removed, it'd be nice to see if anyone could find an article that mentions it. Everything online talks about the block being placed
rabeatz said:
The fair labor standards act was passed in 1938. Still in effect today. Just because Google made the change 10 months ago doesn't mean it suddenly was removed.. Whenever I search on the topic all I can find is info that says that access to copy protected apps been disallowed, can't find any article that mentions them removing the block.
I'm not saying it hasn't been removed, but it's kind of hard for me to know whether or not i'm being blocked from applications, I don't know what ones are copy protected and what ones aren't, or if theyre being blocked from me, because they simply wouldn't show up and I wouldn't even know they exist.
If the block has in fact been removed, it'd be nice to see if anyone could find an article that mentions it. Everything online talks about the block being placed
Click to expand...
Click to collapse
Search Nesoid, that is a protected app. If you see the paid version then they lifted the block
Have you ran market enabler?
supremeteam256 said:
Have you ran market enabler?
Click to expand...
Click to collapse
What's that...?
Edit: Got it... http://code.google.com/p/market-enabler/ And it works... Thanks for the tip...!
Edit 2: Market Enabler works by mimicking certain APNs, be sure to backup your current APN first and restore it after getting the apps (it can be done within Market Enabler).
Cheers.
I had some issues with the ADB commands for preparing my rooted Nook Color for on-device app install (primarily due to microcrap's 64-bit Vista) so I found a very easy method.
In the Market, there's an app called "Sqlite Editor" from the folks who make "Root Explorer" - it's about $3.07 US$ but I bought it anyway.
With this [AFTER A BACKUP!] I was able to directly edit the settings.db (sub category SECURE) and change the following:
'install_non_market_apps' from the default value of 0 to 1 and following a SAVE and REBOOT I can now install directly from my SD Card.
While I was doing this, I find a large number of additional entries including (are you ready for this???) bluetooth_on!
Dare I do this???
I also posted this in Mobileread's excellent Nook Color Forum and I was thinking that may we should also acknowledge them as a great forum for our beloved Nooks!
docfreed said:
While I was doing this, I find a large number of additional entries including (are you ready for this???) bluetooth_on!
Dare I do this???
Click to expand...
Click to collapse
LOL...If only it were this easy.
I had no issue with installing apps from the sd card after rooting/installing mkt and gapps.
Depends on How You Rooted..
I'm not certain but some rooting methods have market/gapps built-in, some don't. I used Autonooter (after upgrading to 1.01) and market & Gmail just appeared - I never had to install anything else.
If you used Autonooter then you wouldn't have to do anything to be able to install non market apps. Maybe just toggle the setting in Nook Tools if anything.
docfreed said:
While I was doing this, I find a large number of additional entries including (are you ready for this???) bluetooth_on!
Click to expand...
Click to collapse
Its NOT that simple, its been turned on in the kernel & custom ones built for it with nothing.
If you see the "salting nook" posts so much as been done trying to get it to work, most expect something ground breaking to come from actually looking at the pins on the chip it self an connection through the MoBo.
Amd sold faulty quad cores as triples so it could be that the chip/Mobo cant do it. Could be a easy hardware mod but TBH so much deep thought an attempts have been seen in IRC i dont see a "virtual fix" anytime soon.
But that said im an idiot so could be 475% wrong
Yeah, I tried toggling Nook Color Tools per the instructions - never seemed to work for me. Anyway, it appears to be just a one-shot adjustment any way it's done (at least till we get FroYo) so I'm happy.
Merry XMAS everyone
docfreed
sqlite not working for me
Purchased Sqlite, when trying to install, exits without loading apps. Any suggestions? Rooted with older booker and then re-rooted with pre 1.01 autonooker. Thanks. -
I have a kernel and u-boot that enables the bluetooth portion of the module and sets up an rfkill device. hciattach will detect it as a TI Bluetooth module and will load one of the TI bluetooth firmware scripts, but then complains about a missing socket or something. It sounds like a software error more than anything that might be wrong with the hardware.
What this means is that the Bluetooth part of the WiFi module isn't just left disconnected and the link to the CPU is working. But we don't know if the antenna is set up to share between wifi and Bluetooth or if the hardware is otherwise missing something that would keep it from working.
If you have experience with getting TI WiLink Bluetooth working in Android or Linux, or know someone who does, PM me or join us on Freenode channel #nookie. We're really close!
Hello XDA'rs,
I work for the developer Loud Crow Interactive Inc. and we build book apps for kids.
We've recently launched into the Android Market and are having trouble with our app being installed on rooted nook colors. The issues appear to be on the licensing side.
Does anyone have any thoughts on what this could be? Also, what does a rooted nook register as (device) on the Android Market place,
Thanks in advance,
Tom
What's the error, logcat ?, what's the app?
dude u gotta give some info if need a solution.
There could be a million things that could cause problems like that.
x2002dude said:
Hello XDA'rs,
I work for the developer Loud Crow Interactive Inc. and we build book apps for kids.
We've recently launched into the Android Market and are having trouble with our app being installed on rooted nook colors. The issues appear to be on the licensing side.
Does anyone have any thoughts on what this could be? Also, what does a rooted nook register as (device) on the Android Market place,
Thanks in advance,
Tom
Click to expand...
Click to collapse
We are all waiting for an answer. I have an outstanding request in with Google that I have had to update several times as they seem to be dancing around the question. When and if I hear I will post a response.
The App is "The Going to Bed Book" or "PopOut! The Tale of Peter Rabbit" - Our users are getting a "Invalid License" error. We're going to root one of our nooks soon to do some testing, but until then we were thinking we might be able to get something from the forums. Both users who reported the issue were running CM7, which I also run on my HTC IS, and runs our apps fine. Thus we're thinking it could have something to do with the device ID running against the licenses?
As we set up restrictions by device, We were curious what a rooted NC running CM7 would show as in terms of a device on the Android Market place?
Thanks for the help guys, and thanks for the patience. I'm not the actual Android developer on the team. He's out of the office for the week,
Cheers,
Tom
I think he means he is having trouble getting the application to install from the market in general. I looked up the applications and the NC was not a supported device.
I don't want to pay the money to download it to my phone and sideload it (I'm at work anyways). I don't know much about applications and how devices are determined to be compatible other than maybe their permissions. However, these applications (there are two on the market), don't require anything other than SD access.
As we set up restrictions by device....
Click to expand...
Click to collapse
That might be part of some of this. I was not aware developers were setting restrictions by device. Is this new?
model name -NookColor
product name -encore
And there is really no way to find out the problem, without looking at the logcat.
patruns said:
That might be part of some of this. I was not aware developers were setting restrictions by device. Is this new?
Click to expand...
Click to collapse
No, this feature is available to every developer since a long time. but there are 600 or so devices so not a lot of people bother with it.
rigy73 said:
model name -NookColor
product name -encore
And there is really no way to find out the problem, without looking at the logcat.
Click to expand...
Click to collapse
Actually, questions to the market run against your account and the email info and log the following device details:
> IIILanguage: en
> IssueType: market_website
> Language: en
> android_app_name: Facebook
> android_os: gingerbread
> android_os_other:
> device_manufacturer: other
> device_manufacturer_other: Barnes & Noble
> hidden_country: US
> website_issue_select: grayed_device
device_manufacturer= bn
If u want to know more take a look at build.prop, people have uploaded it in netflix thread, which reminds me that a lot of users usually change their device and fake it to run different apps.
rigy73 said:
device_manufacturer= bn
If u want to know more take a look at build.prop, people have uploaded it in netflix thread, which reminds me that a lot of users usually change their device and fake it to run different apps.
Click to expand...
Click to collapse
Those were direct quotes from what Google's filters picked up when I sent an email while logged in to the market.
Thanks guys, this will be a good start. If and when we resolve the issue I'll be sure to post an update with the details. I really wish Android Market supported promo codes; we'd love to be able to throw out some free copies for you guys to have a look at and test for these one off issues.
Thanks Again!
I assume if you sideload the .apk it will install fine?
Just want to contribute that I have the Going to Bed Book installed and running fine on my Nook. I am still running CM7 7.1RC, and have my build.prop spoofed for Netflix (no longer required, but I never changed it back and haven't flashed a new CM7 in a while). The only change I made in build.prop was setting the manufacturer to HTC.
The book runs great and is my son's new favorite app.
You may have an issue using get.DeviceID()... have one of your users use my IMEI generator and see if it fixes their problem. They can also spoof Manufacture, Device and Model with the newest version.
IMEI Generator Thread.
I have it on my CM7 (7.0.3 to lazy to update, running off sd no changes to build.prop) Nook and it works fine. My daughter loves it.
Some of the pages are kind of hard to register a turn, and it always starts upsidedown then flips itself over. But both of those things are the same on my incredible 2 as well.
Sent from my ADR6350 using XDA App
When the HD comes out, could somebody rip the Amazon Instant Video app apk and post it on xda?
The reason: Old app only works on Gingerbread. The new one should work on ICS and JB because the new Kindle Fire's OS is based on ICS.
Was just about to post a thread over here, we has one going on the old KF forums. ES File Explorer is on the Amazon market and should be able to read the /system/app directory without root. Really hoping this apk works on other ICS/JB devices.
An update bin file was posted and I grabbed the apk file from that. So far no luck, it FCs on my Touchpad with CM9. I tried installing as a regular app making sure Voodoo had me unrooted. I also tried as a system apk and rebooted, still FCs. It refuses to install on GB so I imagine its using API Level 15.
Hopefully it just needs another apk installed, Ill play around with it and see if I can get it working.
EDIT: I installed aLogcat to see if I could narrow down what is causing the FC. Its looking for the class "amazon.unifiedsettings.UnifiedSettingsHelper" which doesn't exist. Later in the log the FC is caused by a fatal exception with the class "amazon/unifiedsettings/UnidifedSettingsHelper" not being found. Is this a lib file or a system apk it wants?
EDIT2: I gave up on it for now. I tried some lib files, tried installing as many apks as I could (didn't try replacing system apks). It still FCs with the same error log and I can't find any files that reference unified settings. I also downloaded the Kindle Fire 2 update file (the updated original fire) and its using the same APK. LCD Density for the HD is 240 and 160 for the regular Fire 2. I use 160 on my Touchpad so that shouldn't be the issue.
How does one get apks out of Amazon's .bins?
com.amazon.dcp.apk
MyAccount-unsigned.apk
AccountAndSyncSettings.apk
These are the three extra apks (in addition to video apk itself) I needed to get it running on my Nook Tablet back in the day. I noticed back then that it seemed to work a little different for everyone. Some folks didn't need any of those while others of us experienced all manner of crashing without some of them. Sadly, one also forced my NT to appear as a KF in the Amazon app store, which made some of my purchased apps incompatible. Caveat emptor.
Would love to see those posted though if someone gets around to it. Would also love to see Amazon get their rear in gear and release a prime streaming app for android that didn't require all the fuss.
The bin files open for me in WinRAR, I think they are just zip files. AccountAndSyncSettings.apk is gone from the new Kindle Fires, the other two files are still there. I remember using those 3 files before allowed you to add an Amazon account and then open the app and you would already be logged in. With the new 2 files, it FCs in settings when I try to add an Amazon account. I didn't try using the old GB apks, it may be worth a try as they allowed an Amazon account to be added even on ICS.
I'll upload them, there is only 2 now, because you may have a different outcome than me on a different device.
No luck on a simple side load to an Acer A700 or an Acer A100 both stock and unrooted running ICS. I am reluctant to try the other apk's because I also had my a100 appear as a kindle fire and had to restore it to get use of my apps that were not kindle compatible.
I was messing around on my Touchpad with CWM so I always have the option to restore a nandroid if I were to screw something up. But I played around with it a lot this morning and didn't do any damage, everything was FCing.
No luck on Nexus 7. Tried after installing all three apk.
Sent from my Nexus 7 using Tapatalk 2
I too am looking to stream amazon on my cm9_tp but did not see anyone mention the fact it works perfectly on WebOs.
rfauconn said:
I too am looking to stream amazon on my cm9_tp but did not see anyone mention the fact it works perfectly on WebOs.
Click to expand...
Click to collapse
I will work through a flash capable browser with a desktop user agent in Android as well, but its not optimized very well for mobile devices. The app is much nicer when it works. At this point we may be better off trying to get the GB version working in ICS since it will at least open and let you browse.
In addition to a better UI in the app, I've also experienced intermittent, albeit minor, audio sync issues with mobile flash that I never had in the app. I hate that.
can someone with a kindle fire hd open up the app and then post the log? Wouldn't we be able to see where the unifiedsettingshelper file was with the log of it opening successfully?
Any update on this?
Sent from my Transformer Prime TF201 using Tapatalk 2
We need a Fire HD user or somebody with more knowledge of how things work to figure out where we can get "amazon.unifiedsettings.UnifiedSettingsHelper" from. This is the missing service it crashes on. I can't find any lib files or apks from the ROM that fix this issue. Also even if we get past this crash error another one may appear. At this point I'm thinking we may be better off trying to get the old GB app working since it seems to have fewer issues. It allows you to open and browse to videos on ICS, also allows you to add your Amazon account to the device, but crashes when you go to play a video. Its having a database issue according to the crash log posted over in the GB thread:
http://forum.xda-developers.com/showpost.php?p=31633773&postcount=193
spunker88 said:
We need a Fire HD user or somebody with more knowledge of how things work to figure out where we can get "amazon.unifiedsettings.UnifiedSettingsHelper" from. This is the missing service it crashes on. I can't find any lib files or apks from the ROM that fix this issue. Also even if we get past this crash error another one may appear. At this point I'm thinking we may be better off trying to get the old GB app working since it seems to have fewer issues. It allows you to open and browse to videos on ICS, also allows you to add your Amazon account to the device, but crashes when you go to play a video. Its having a database issue according to the crash log posted over in the GB thread:
http://forum.xda-developers.com/showpost.php?p=31633773&postcount=193
Click to expand...
Click to collapse
could amazon.unifiedsettings.UnifiedSettingsHelper be part of one of the odex files in system/app ?
It will be fantastic once this can be resolved. I hate that they are allowing this on iOS but not on other android devices.
Yes, it is absurd that iPad has access and general android devices are SOL. We purchased our content...and can't watch it reliably (app access). I would encourage everyone to let amazon know this is unacceptable - and I'm hopeful the good people here find a fix for us in the mean time.
Gonzorito said:
Yes, it is absurd that iPad has access and general android devices are SOL. We purchased our content...and can't watch it reliably (app access). I would encourage everyone to let amazon know this is unacceptable - and I'm hopeful the good people here find a fix for us in the mean time.
Click to expand...
Click to collapse
I tried giving Amazon some feedback on supporting other Android devices - they didn't seem to care much. I guess they want to sell more Fires, but if they're selling them at a loss wouldn't they make more profit by supporting their app on other devices?
Our how about, I purchased my kindle to read, purchased a tablet before the fire was a gleam in their eye.
I purchase video content and have limited access to it, so i won't purchase future content with amazon as a result.
No I won't buy a fire and I am encouraged to buy my future content through Google play on top of that!
Loss, loss, and more loss for Amazon. Doesn't make sense.
Sorry for side tracking the thread, I will end the QQ
Gonzorito said:
I would encourage everyone to let amazon know this is unacceptable - and I'm hopeful the good people here find a fix for us in the mean time.
Click to expand...
Click to collapse
Yup. Of course they aren't going to listen to any one complaint, but Amazon is a pretty responsive company on the whole. Squeak enough and they'll grease the wheels. There's no indication they want to make this fire-only, given how many other devices its on, it's just a question of priority. You can bet the apple people whined more than the android people, so if you want them to get it in gear get on their contact page and make the request. I've done it repeatedly, but we need more people to get noticed.
So the last (?) PlayStore access app for Android 2.1 bites the dust, apparently. The Search function died sometime last month and now log-in is impossible. The most recent version, 0.46, was done at the beginning of 2019. Word has it that the developer has abandoned the project.
Is there an alternative?
---------- Post added at 10:58 PM ---------- Previous post was at 10:40 PM ----------
nmyshkin said:
So the last (?) PlayStore access app for Android 2.1 bites the dust, apparently. The Search function died sometime last month and now log-in is impossible. The most recent version, 0.46, was done at the beginning of 2019. Word has it that the developer has abandoned the project.
Click to expand...
Click to collapse
I just installed Yalp Store fork from F-Droid.
Even ist says it's. Not compatible with my device, the app works perfect with yalp store built-in credentials.
XtraWater said:
Is there an alternative?
---------- Post added at 10:58 PM ---------- Previous post was at 10:40 PM ----------
I just installed Yalp Store fork from F-Droid.
Even ist says it's. Not compatible with my device, the app works perfect with yalp store built-in credentials.
Click to expand...
Click to collapse
Assuming this is what you are referring to: https://f-droid.org/en/packages/com.github.kiliakin.yalpstore/
I cannot at this time confirm your experience. I have been unable to successfully log in with this new forked version.
nmyshkin said:
Assuming this is what you are referring to: https://f-droid.org/en/packages/com.github.kiliakin.yalpstore/
I cannot at this time confirm your experience. I have been unable to successfully log in with this new forked version.
Click to expand...
Click to collapse
Choose another device.
XtraWater said:
Choose another device.
Click to expand...
Click to collapse
Mmm...you might have saved me some time by telling me which one worked for you. I eventually found that choosing HTC Desire would allow a log-in, but this raises other issues. Originally the Yalp Store would filter out apps that were not for Eclair (or at least list them as "incompatible"). This does not happen if you are spoofing another device that is running who knows what version of Android.
Also, Search is broken. It reverts to a search of the device (Library and Shops) rather than the PlayStore. Not helpful.
Finally, although you can use the "category" option to look at apps (with no idea which might actually be compatible...), you cannot download anything. At least I couldn't. I got an error each time I tried.
So....a lot of work for the new developer to make this functional for the NST. For a lark I installed the last version of the original Yalp Store on my Tablet running 8.1 and was surprised to see that it actually worked without any funny business. So whatever happened to it seems to have affected legacy devices, but not more current OSes.
nmyshkin said:
Mmm...you might have saved me some time by telling me which one worked for you. I eventually found that choosing HTC Desire would allow a log-in, but this raises other issues. Originally the Yalp Store would filter out apps that were not for Eclair (or at least list them as "incompatible"). This does not happen if you are spoofing another device that is running who knows what version of Android.
Also, Search is broken. It reverts to a search of the device (Library and Shops) rather than the PlayStore. Not helpful.
Finally, although you can use the "category" option to look at apps (with no idea which might actually be compatible...), you cannot download anything. At least I couldn't. I got an error each time I tried.
So....a lot of work for the new developer to make this functional for the NST. For a lark I installed the last version of the original Yalp Store on my Tablet running 8.1 and was surprised to see that it actually worked without any funny business. So whatever happened to it seems to have affected legacy devices, but not more current OSes.
Click to expand...
Click to collapse
I used galaxy 7 edge. However, can't login anymore today at all.
Including Aurora store not able to log in.
I guess this is a war against Huawei that might eventually lead to the death of aosp at least for gapps people. Imagine gapps flashing on top of clean aosp becoming useless as none of these apps would not be able to log in etc
darfri said:
Including Aurora store not able to log in.
I guess this is a war against Huawei that might eventually lead to the death of aosp at least for gapps people. Imagine gapps flashing on top of clean aosp becoming useless as none of these apps would not be able to log in etc
Click to expand...
Click to collapse
I don't want to speak out of turn because I could not do the sort of programming required for these efforts. However, I do run the 8 gb version of the Nook Tablet using the microG project components. It works very well including maps, and uses so few resources you can even use the actual Playstore app instead of one of the other apps which seem to be either abandoned or in need of repair. Unfortunately, KitKat is the lower limit for microG, but it sure makes a difference, especially on a device struggling with memory issues.
At least F-droid have in descriptions of application requirements that state minimal version of Android it can be run from on my tablet it is so. I hope that is also the case with f-droid run from NST. If I had to choose device name for spoofing purposes on that YALP application my bet would be some of the phones running Eclair. Last were some Motorola phones from 2015 as far as I recall. Since on my NST social and even shop stopped working properly I am more and more leaning to go through the road taken by many and ditch original software and start tweaking and tinkering with the device. Eclair is so old that I do not know is there many application left to work with but in case this thread escaped attention I will leave link here. https://forum.xda-developers.com/showthread.php?t=698851
SJT75 said:
At least F-droid have in descriptions of application requirements that state minimal version of Android it can be run from on my tablet it is so. I hope that is also the case with f-droid run from NST. If I had to choose device name for spoofing purposes on that YALP application my bet would be some of the phones running Eclair. Last were some Motorola phones from 2015 as far as I recall. Since on my NST social and even shop stopped working properly I am more and more leaning to go through the road taken by many and ditch original software and start tweaking and tinkering with the device. Eclair is so old that I do not know is there many application left to work with but in case this thread escaped attention I will leave link here. https://forum.xda-developers.com/showthread.php?t=698851
Click to expand...
Click to collapse
"Run" and "work" are not always the same thing. The original Yalp Store stopped working in the mid 0.4x series. It could not log in, even with your Google account, probably due to SSL issues. The fork of the Yalp Store can log in but search is broken and download does not work. Search defaults to a device search rather than a search of the PlayStore and attempts to download an app from the Categories results in a crash. I've sent results to the developer but there does not seem to be a lot of change going on there (the app does work on the NST CM 11 ROM). It's pretty moot as there is not a lot in the Market any longer that will work on the NST. It's "easier" in the long run to do your homework and then search for the app you think will work using Apkpure or similar.
If Social and Shop have stopped working on your device you probably have not updated to 1.2.2.
nmyshkin said:
"Run" and "work" are not always the same thing. The original Yalp Store stopped working in the mid 0.4x series. It could not log in, even with your Google account, probably due to SSL issues. The fork of the Yalp Store can log in but search is broken and download does not work. Search defaults to a device search rather than a search of the PlayStore and attempts to download an app from the Categories results in a crash. I've sent results to the developer but there does not seem to be a lot of change going on there (the app does work on the NST CM 11 ROM). It's pretty moot as there is not a lot in the Market any longer that will work on the NST. It's "easier" in the long run to do your homework and then search for the app you think will work using Apkpure or similar.
If Social and Shop have stopped working on your device you probably have not updated to 1.2.2.
Click to expand...
Click to collapse
True about that. Should and will are two different verbs meaning. Interesting info about that app is still working but under different ROM. Just for the sake of making things clear all custom made things here on the forum are still based on Eclair and there were not any Android upgrades through custom ROM to preserve compatibility with B&N software?
About your Nook page say that I have version 1.2.2 of software. Remember that I have NST in untouched never modified condition that has active over the air active update as designed by B&N. So it might be that something gone wrong during update and I need to do it again manually from SD card or through computer. Shop behaves odd. It allows me to search for a book but does not allow me to download. Social do not connect at all.
I am just sifting through different apps looking for those that might be possible to use on NST. I have seen in F-droid repository two YALP stores. One from the original author that is not updated for over a year and second one labeled fork which is not updated for over nine months period. To add to confusion OP mentioned version 0.46 which is not the latest version original author placed in repository (his latest version is 0.45). Still forked version with that number exist sort of labeled 0.46-legacy IIRC. So what is exactly version up used that stopped working? Even an info about non-working app is good sometime to avoid loosing time on very much likely fruitless effort.
SJT75 said:
I am just sifting through different apps looking for those that might be possible to use on NST. I have seen in F-droid repository two YALP stores. One from the original author that is not updated for over a year and second one labeled fork which is not updated for over nine months period. To add to confusion OP mentioned version 0.46 which is not the latest version original author placed in repository (his latest version is 0.45). Still forked version with that number exist sort of labeled 0.46-legacy IIRC. So what is exactly version up used that stopped working? Even an info about non-working app is good sometime to avoid loosing time on very much likely fruitless effort.
Click to expand...
Click to collapse
Yeah, it's a mess over there. You have to go to the github to access older versions of the original Yalp Store. So you can see there that the developer of the "fork" just picked up with version 0.45 and carried on. The "legacy" refers to a simpler UI such as can run on Android 2.1, for example, as even the original developer started branching out, eventually releasing two versions of the app each time. Actually it was after the app tried to become a little more fancy that it began to have trouble on the NST (surprise). It's been quite awhile since I ran the app on the NST but I suppose somewhere in my original post about the Yalp Store the version is mentioned (probably started with 0.39, if memory serves, and then moved along as login failed when Google changed things; at one time I think I got as far as 0.43)
One issue with the "fork" (besides the fact that "fork" is in the screen display name...) on the NST is that Search is broken. It defaults to a device search rather than a PlayStore search. Not sure if this was ever a problem with the original. I'll have to download a few versions and see. Also, even if you wade through the categories and select an app that way, it crashes when you try to download.
All that said, those are definitely NST issues since the most recent version of the "fork" runs fine on the CM 11 sdcard-ROM for the NST (including Search and download)
nmyshkin said:
Yeah, it's a mess over there. You have to go to the github to access older versions of the original Yalp Store. So you can see there that the developer of the "fork" just picked up with version 0.45 and carried on. The "legacy" refers to a simpler UI such as can run on Android 2.1, for example, as even the original developer started branching out, eventually releasing two versions of the app each time. Actually it was after the app tried to become a little more fancy that it began to have trouble on the NST (surprise). It's been quite awhile since I ran the app on the NST but I suppose somewhere in my original post about the Yalp Store the version is mentioned (probably started with 0.39, if memory serves, and then moved along as login failed when Google changed things; at one time I think I got as far as 0.43)
One issue with the "fork" (besides the fact that "fork" is in the screen display name...) on the NST is that Search is broken. It defaults to a device search rather than a PlayStore search. Not sure if this was ever a problem with the original. I'll have to download a few versions and see. Also, even if you wade through the categories and select an app that way, it crashes when you try to download.
All that said, those are definitely NST issues since the most recent version of the "fork" runs fine on the CM 11 sdcard-ROM for the NST (including Search and download)
Click to expand...
Click to collapse
Thanks for reply with all quality info there! Does github work on NST or have done cloning/compiling elsewhere and sideload app to NST? Interesting issue with search on NST. It looks to me like B&N manage to pull another fast one on us like they did with "nonexistent" browser. I believe that somehow they screwed search through basically invoking any search attempt to link to their search library/shop application instead. Probably author in early versions used his search function but later decided to exploit some inbuilt Android/Google option that B&N screwed with. That might be the reason why on running the app through CM11 ROM from flashcard everything works as author intended/expected to work had NST be ordinary Android device. Now question remains...is that search function still there on NST but "hidden" and can it be somehow re-enabled or some heavier work lies on that road?
SJT75 said:
Thanks for reply with all quality info there! Does github work on NST or have done cloning/compiling elsewhere and sideload app to NST? Interesting issue with search on NST. It looks to me like B&N manage to pull another fast one on us like they did with "nonexistent" browser. I believe that somehow they screwed search through basically invoking any search attempt to link to their search library/shop application instead. Probably author in early versions used his search function but later decided to exploit some inbuilt Android/Google option that B&N screwed with. That might be the reason why on running the app through CM11 ROM from flashcard everything works as author intended/expected to work had NST be ordinary Android device. Now question remains...is that search function still there on NST but "hidden" and can it be somehow re-enabled or some heavier work lies on that road?
Click to expand...
Click to collapse
So here's a run-down of what still "works" on the stock NST:
Only one version of the original Yalp Store passes every test but one. Version 0.35 succeeds in log-in (with your own Google account--no version successfully logs in with a generic Yalp Store account), Categories successfully brings up lists of apps and you can download/install from these lists. Search shows in light grey within the field "applications" and an initial search string brings up a number of more specific items, but no matter which you select it always returns "no apps".
As to the "fork", you can log in with a Google account, but Categories is blank, and Search shows in light grey within the field "Search NOOK(R)" and will dutifully check the Library, Shops, Social, etc. Totally useless.
So it seems the most nearly working is 0.35 of the original app series. Presumably the API for getting search information from the PlayStore is no longer correct. However, it may be possible for someone clever (more clever than I) to reverse engineer or cross engineer versions. Since we know the "fork" versions work on a non-NST ROM, it seems the API or whatever for Search is currently valid in them. Why they default to device search remains a mystery.
I should add that I did not try device spoofing in any of my tests. Too many variables for my brain. It may be that changing the apparent device ID would bring up apps in Categories which is otherwise blank. But using Categories to select apps is painful. A working Search is essential or the app is pretty useless.
nmyshkin said:
So here's a run-down of what still "works" on the stock NST:
Only one version of the original Yalp Store passes every test but one. Version 0.35 succeeds in log-in (with your own Google account--no version successfully logs in with a generic Yalp Store account), Categories successfully brings up lists of apps and you can download/install from these lists. Search shows in light grey within the field "applications" and an initial search string brings up a number of more specific items, but no matter which you select it always returns "no apps".
As to the "fork", you can log in with a Google account, but Categories is blank, and Search shows in light grey within the field "Search NOOK(R)" and will dutifully check the Library, Shops, Social, etc. Totally useless.
So it seems the most nearly working is 0.35 of the original app series. Presumably the API for getting search information from the PlayStore is no longer correct. However, it may be possible for someone clever (more clever than I) to reverse engineer or cross engineer versions. Since we know the "fork" versions work on a non-NST ROM, it seems the API or whatever for Search is currently valid in them. Why they default to device search remains a mystery.
I should add that I did not try device spoofing in any of my tests. Too many variables for my brain. It may be that changing the apparent device ID would bring up apps in Categories which is otherwise blank. But using Categories to select apps is painful. A working Search is essential or the app is pretty useless.
Click to expand...
Click to collapse
Hmmm...well nice to know what is working. Interesting that YALP spoofing does not work but you can login using your credentials. I was under impression that nothing in the line of Gapps works now on NST due to changes implemented by big G..gle. Since other methods like G-droid, Aurora store etc.are out of option due to their android version incompatibility it seems that sideloading through SD card and PC is only option left viable. That present another problem of search for a right app on web through PC but it seems like a topic for another thread. I believe that we also opened here another rabbit hole of messed up search on NST which is if I remember well been observed in several situation/application. On my side I think that two things I found. First apparently working search in B&N Shop does not have to mean anything as it seems that it simply goes through internally downloaded DB of their Shop. My request for download never delivers anything and it seems that internet connection to B&N servers is down. Interestingly later I received e-mail from B&N claiming that my books are ready for delivery. I will investigate this and report back about outcome but it seems that there is someone on the other end of my request sending listening and filing the intent but from some reason unbeknownst to me they do not send the requested file. Maybe they opted for another method of delivery in case of such outdated devices due to possible security problem/flaw? We will see.
While researching about Opera browser something came to my attention and I have to ask about it and this look as good place as any. I remember that people here managed to use Amazon app to download applications to NST that I have no information is it still working. However I stumbled upon an info about something called Opera store. Since Opera is still working on NST if the ancient version allows using Opera Store that might be interesting option? Has someone checked that out?
SJT75 said:
While researching about Opera browser something came to my attention and I have to ask about it and this look as good place as any. I remember that people here managed to use Amazon app to download applications to NST that I have no information is it still working. However I stumbled upon an info about something called Opera store. Since Opera is still working on NST if the ancient version allows using Opera Store that might be interesting option? Has someone checked that out?
Click to expand...
Click to collapse
I had always thought the Opera Store was for Opera extensions and addons, but you made me take a look.
Supposedly the URL is apps.opera.com, but this redirects to something called the "Bemobi Mobile Store" (using the Opera logo). The site loads fine in Opera Mini on the NST, probably Opera Mobile as well, although I did not try.
I looked at a few apps just to see what would happen. There didn't seem to be any check on the Android version. In each case I tried, tapping on the "Download" button took me to the Android Market agreement (i.e., the PlayStore entry) so whatever is going on there, it doesn't seem to be an actual "store" as much as a listing of apps with referral to the PlayStore (where, of course, the NST cannot go). There may be exceptions. Obviously I didn't try everything.
In the long run, there is very little point in some kind of Market access for the NST. If you want to try something you need to track it down. There are all kinds of sites like Apkpure, etc., that can be sources for old versions of apps. The other day I came across a huge listing of Android 2.1 apps (by an XDA member, as it happens) and most of them had dead PlayStore links. But with a version number and a little searching I had little trouble finding the few that sounded interesting.
I had hope that Opera tried to make their version of store like Amazon did or at least manage to make their online browser based version of Aurora which considering what they do with Opera Mobile wouldn't be that hard to achieve. Nevermind sideloading for the win it is!