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!
Related
http://www.engadget.com/2009/11/23/google-maps-navigation-officially-comes-to-android-1-6/
When trying to download onto my phone from the Market, I get an error message 'Package file was not signed correctly.'
I'm running Cyanogen 4.2.5 on my Rogers Magic 32A.
Doesn't work for me in denmark
I think this is only US.
It's been released for the Market on all devices, but I think it has something to do with our devices using test-keys and not release-keys...
Thoughts?
Same problem in Belgium with 32A using CyanogenMod 4.2.5 with Kernel 2.6.29bfs.
Very sad
working fantastic on my MT3G running Dwang 1.13. Didn't get an 'update available' notification, but installing it from the market worked flawlessly. I gotta say, navigation with google layers is freakin' awesome
cursordroid said:
When trying to download onto my phone from the Market, I get an error message 'Package file was not signed correctly.'
I'm running Cyanogen 4.2.5 on my Rogers Magic 32A.
Click to expand...
Click to collapse
I have the same phone and ROM version and it updated just fine from the Market. However, I did push the software to my phone, following the instructions here. Not sure if that's why it works without issue.
So i guess its confirmed that this is still US only. BAH
"Some features of Android 2.0 are not available on Android 1.6, for example, the ability to use the "navigate to" voice command as shown in our demo video. However, you can still create a shortcut that will allow you to launch Navigation and start getting directions to a specific place from your current location with just a single touch from your home screen."
Source: http://googlemobile.blogspot.com/2009/11/happy-thanksgiving-travels-google-maps.html
ugh...
If it is US only, why did they not restrict it to the US on the market ? Or maybe that's technically not possible with the current market configuration ?
Neejay said:
"Some features of Android 2.0 are not available on Android 1.6, for example, the ability to use the "navigate to" voice command as shown in our demo video. However, you can still create a shortcut that will allow you to launch Navigation and start getting directions to a specific place from your current location with just a single touch from your home screen."
Source: http://googlemobile.blogspot.com/2009/11/happy-thanksgiving-travels-google-maps.html
ugh...
Click to expand...
Click to collapse
Or you can search the Market for 'Nav Launcher' and it will enable these features through an external application. Works fine for me.
Same issue on a Mytouch 3G (32B,) in the US and also running Cyanogen 4.2.5.
This is a fresh install of cyanogen as well (literally nothing more than the 1.6 base image and then the cyanogen update.)
I'm also getting the "package not signed" error. Not sure what the problem is. Running CyanogenMod Android 1.6, but I honestly don't remember what version of Cyanogen it is.
This official update no different than the 1.6 hacked Maps w/Navigation that was pulled from the Droid dump.
Even if you can get it installed, you still need to use either Directions shortcuts or the Nav Launcher to get it working outside the US.
I keep getting errors cannont remove / no such file or directory
on cyan 4.2.5 seams like nothing different from 2.0 droid nav
I sure do wish that people stop giving apps 1 start because it doesn't work on cyanogenmod..... these are precisely the people that bring down heat on developers with their crying. God forbid they have to do a search on the net... and, dare I say, read 3 lines of text.
People need to realize we are not flashing official software here, and so we have no right to b*tch if something that's made for official software doesn't work on our hacked ones. There is not one dev here that I can remember who doesn't clearly say that if you break your phone it's your responsibility, not his, or the manufacturers. That's why we have this community here, if you're having problems most members here will help you out however they can because that's what this place is about tweaking our equipment as much as possible and fixing it when we mess up. I would say most people here enjoy helping others out with tech related stuff, I know I do in whatever way possible, but I have no sympathy for those that can't be a$$ed to read a few lines and just want to flash their phones with total disregard of what could happen.
How do you think google feels everytime they see a one star rating on one of their apps, or any other app, that works perfectly fine on official images when the person comments "DIS SUXXORS, IT B NOT WORKING ON C.M 4.2.5"? It's a miracle they didn't crack down on cyanogen much sooner than they did. PLEASE, PLEASE PRETTY PLEASE if you have issues with something you downloaded from XDA or any other site on the net that deals with this kind of stuff, don't go complaining to your mobile carrier, or whoever developed your mobile's official software; come here and ask for help... besides 99% of the time I'm fairly sure that we'll do a much better job of helping than anybody you can contact from your mobile carrier, or official developers. Also, if you brick you're phone be responsible for you're mistake; don't try to be sly and send it in because it's not working to your dev because again this only attracts unnecessary attention to this site. I'm fairly sure that cease & desist that xda received from MS a few years back was due to precisely this.
I've customized windows mobile, palm, symbian, android phones, plus ps1, ps2, ps3, psp, wii, and so far I've never brick anything, or at least not to the point I can't bring it back, so does this mean I'm super lucky? or super smart? Not really, it's quite simple really my secret is this: READ, Read like your equipment depended on it because quite frankly IT DOES.
Sorry for the rant guys, it's not directed at any one of you, but maybe just maybe one of these "people" will find it and correct themselves. I'd actually wish the mods would post something on the main page, but then again who am I kidding the problem originally arises from them not reading in the first place.
I agree.
Also not working on my phone (32a Magic). Currently looking for a work around.
I have searched for:
Google
Google Maps
Google Maps Navigation
Navigation
Etc, Etc, Etc...
and can NOT find this version in the market???
I updated to the latest "Google Maps" from the market, but it does not have the NAV Features.
AHA!
Redownloaded and now get the "Package Not Signed" error as well.
CyanogenMod-4.2.5
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.
OK, I'm frustrated.
I have been trying to add my gtab to my devices on the new Market site, and have so far been unable to do so. Actually, that is not exactly true. I can get it to show up partially.
I have a Droid phone, and I see the phone when I go to my Market Account, Settings, My Devices. I enter the new nickname for my tablet.. [tablet, gtablet, Viewsonic G-Tablet, Malata ... all tried separately], I check the "show in menus" option. Press the Update button on the right. And nothing happens. The Maker, Model, Carrier columns for the tablet are empty, with only a hyphen. I cannot enter information directly into these columns, and whenever I try to download something, only the phone shows up. When I click on the little black triangle to expand the devices, I DO see the GTablet there. But it is grayed out with a question mark beside it. It says it is not compatible with this device. Every single app is not compatible with my tablet?
What am I missing?
Full Market fix
You need to change the build.prop file. Use steps 1-5 here:
http://forum.xda-developers.com/showthread.php?t=861044
Ya funny thing is, I think mine showed up (and someone will correct me I bet) as VS GTablet Advent Vegan 5.1.
Something like that but I thought oh they even know I am running the VEGAn ROM. Interesting indeed.
i'm runing vega5.1 and i had to do nothing... he just appeared..
but yesterday i had to do the market fix again and it disappeared.. LOL
weird
tysonkam said:
You need to change the build.prop file. Use steps 1-5 here:
http://forum.xda-developers.com/showthread.php?t=861044
Click to expand...
Click to collapse
my build.prop is correct and does not appear on market...
like i said before, it appeared then after fixing market again it does not
Same. I had to do the market fix again, and then my device disappeared. It was showing the TNT-Lite version beforehand, but now - nada.
tedlogan42 said:
Same. I had to do the market fix again, and then my device disappeared. It was showing the TNT-Lite version beforehand, but now - nada.
Click to expand...
Click to collapse
I had the EXACT same thing happen to me. It was there as a malata gtab running tnt lite, and I had to do market fix again. Now its like it was never there. Is there anyone we can talk to at google about this? Like a customer support type?
Sent from my GTablet-TnT-Lite using Tapatalk
Maybe it is just the simple fact that this tablet is not supposed to be on the market at all. So calling Google to ask why your tablet with the hacked market doesn't work probably won't get you very far.
What is the big deal with this web market anyway? I have no problem using the market app on the tablet.
Agree
Sprdtyf350 said:
Maybe it is just the simple fact that this tablet is not supposed to be on the market at all. So calling Google to ask why your tablet with the hacked market doesn't work probably won't get you very far.
What is the big deal with this web market anyway? I have no problem using the market app on the tablet.
Click to expand...
Click to collapse
+1 I just use the market on the tablet.... My device(for now) is showing in web market.
My G-Tab running Vegan 5.1 is working in the new market with no changes or modifications except editing the nickname. I installed an app to it via the new market already. Since I have a Droid also, I kinda like the ability to install on either or both devices. YMMV, apparently...
Nvidia VEGAn-TAB-v1.0.0B5.1
My tablet showed up under the web-based market as: "Nvidia VEGAn-TAB-v1.0.0B5.1 ". I added a nickname and downloaded some applications. Since I wasn't connected to the internet at the time it was held in abeyance. Once I got a wifi connection, boom down they came. So I can now peruse the market at work or as I monitor these forums, find an application, purchase it (or not) while I am still thinking about it and have it update the tablet the next time it connects. Not bad functionality for someone like me whose work environment is wifi restricted.
I still have one issue I would like to see Google fix. I purchased a application under one gmail account but after reflashing from tnt-lite to Vegan Tab I put my other account on the device first. Now I can't update that application without some tricky effort. Not sure I want to go through that effort or pay the $5 again
While that was me being stupid, I proposed to Google that I could envision the case where I might want to purchase an application with my work credit card and put that on their tablet and also purchase an application with my personal credit card. Their current schema doesn't allow for that. I can see where with telephones it might be a little more personal but tablets may start becoming shared devices say within a family.
What they seem to have for that situation is the ability to use more than one CC with the account. In that case you could use your work CC for some and personal for others.
Not a help for your situation, but it does address the situation you proposed.
Sprdtyf350 said:
Maybe it is just the simple fact that this tablet is not supposed to be on the market at all. So calling Google to ask why your tablet with the hacked market doesn't work probably won't get you very far.
What is the big deal with this web market anyway? I have no problem using the market app on the tablet.
Click to expand...
Click to collapse
The point was that there is no reason for Google to not support the g tab with ANY Rom. They support the galaxy tab, the. Streak too. Why is it ok for those devices? Is it because they are tied to a service and not just WiFi?
Sent from my HTC Liberty using XDA App
Frrrrrrunkis said:
The point was that there is no reason for Google to not support the g tab with ANY Rom. They support the galaxy tab, the. Streak too. Why is it ok for those devices? Is it because they are tied to a service and not just WiFi?
Sent from my HTC Liberty using XDA App
Click to expand...
Click to collapse
Google has prerequisites that must be met for a device to have official and supported Market. GPS and cellular radio are on that list if I'm not mistaken.
Sent from my Viewsonic G Tablet running TnT Lite 4.2.1 w/ Clemsyn's Kernel using Tapatalk Pro
anjenaire said:
My tablet showed up under the web-based market as: "Nvidia VEGAn-TAB-v1.0.0B5.1 ". I added a nickname and downloaded some applications.
Click to expand...
Click to collapse
I'm getting the same showing up in my market access, but where we differ, is I have yet to have an application actually download to my tablet. I've gone through 5-6 different apps that did show the G-Tablet as a compatible device, and these were not installed on my tablet before going to the web market...
The big difference now is I am seeing lots more apps using the legacy Market app on the tablet.
I figured the first week or so would be pounding the web market, and things seem to be settling down, if just a small bit.
Frrrrrrunkis said:
The point was that there is no reason for Google to not support the g tab with ANY Rom. They support the galaxy tab, the. Streak too. Why is it ok for those devices? Is it because they are tied to a service and not just WiFi?
Sent from my HTC Liberty using XDA App
Click to expand...
Click to collapse
I think that they are not trying to give us a hard time as much as they are just trying to have some sort of way to keep things manageable. I mean, they set certain guidelines that devices need to follow to get market access so hopefully most of the apps will work. GPS, and cell type data connection are a couple requirements. Why? I don't know. Guess they had to start somewhere.
I think it is also done so developers can build apps that hopefully work for the types of devices that do qualify. Imagine how hard it would be to make apps that worked on every variation of Android out there. How often do we have issues with apps that don't work on one rom, but work on a different rom.
Maybe it was just to try and keep the market from being like the wild wild west...
Apple has it pretty easy. There are only a couple of hardware platforms they need to worry about. How about Android? There are probably a 1000 different hardware variants out there.
I really won't be surprised if they come up with a way to keep all non qualified devices off the market. Not that big of a deal really if they do though.
So far my tablet is showing on the new market and allows me to download apps to it. I'm running vegan tab 5.1 if that helps anyone...
Sprdtyf350 said:
I think that they are not trying to give us a hard time as much as they are just trying to have some sort of way to keep things manageable. I mean, they set certain guidelines that devices need to follow to get market access so hopefully most of the apps will work. GPS, and cell type data connection are a couple requirements. Why? I don't know. Guess they had to start somewhere.
I think it is also done so developers can build apps that hopefully work for the types of devices that do qualify. Imagine how hard it would be to make apps that worked on every variation of Android out there. How often do we have issues with apps that don't work on one rom, but work on a different rom.
Maybe it was just to try and keep the market from being like the wild wild west...
Apple has it pretty easy. There are only a couple of hardware platforms they need to worry about. How about Android? There are probably a 1000 different hardware variants out there.
I really won't be surprised if they come up with a way to keep all non qualified devices off the market. Not that big of a deal really if they do though.
Click to expand...
Click to collapse
You are probably right, i tend to lean towards everything being based on how these companies can make the most money. Like if what i said is true, maybe then google gets a bigger kick back from the carriers, or phone manufacterers. Its ATT 's fault really, lmao, since everything they do is based on getting more money from me as a subscriber. it seems loke they try to make evry feature, an extra charge, without lowering the standard monthly fees. (i know i am most likely wrong, it just seems this way to me). I am not askin for free stuff, it just seems like they keep the services i want out of my pockets' reach.
Sent from my GTablet-TnT-Lite using Tapatalk
Web market woes
I can confirm web market was working running TNT Lite... stopped working after redoing market fix. Web market working again... after flashing Vegan and wiping data.
For the people with working web based market: did you change your android id? if you did, did you change it to a different devices id or did you use one from an emulator?
Another one bites the dust.
It took awhile for Wunderground's API to actually die, but it finally did and I used my last data point yesterday. None of the other APIs in the app (OpenWeatherMap, Norwegian MET, Yahoo) have worked for awhile. I tried the obvious with OWM and N-MET, getting new API strings, decompiling the app, replacing the APIs and stitching it all back together. But no joy. The data structures in the new APIs are probably different and that's way beyond me. The jiggered app ran, but it was unable to gather data from anywhere (other than what my location is).
Too bad. Nothing left like it, AFAIK.
Yeah, I'm bummed. Weather Ace was one of the few apps that had nice widgets appropriate for the eInk screen.
scotte9999 said:
Yeah, I'm bummed. Weather Ace was one of the few apps that had nice widgets appropriate for the eInk screen.
Click to expand...
Click to collapse
I came across this: https://f-droid.org/en/packages/org.jsharkey.sky/
It works, which is rare for something so old, but the widgets are butt-ugly on the NST
Looks like I'll be researching changing colors, etc. So far it looks like the icons could be easily replaced, but the most offensive part is the widget background which is a 9-patch png (of course...).
The WeatherACE developer is a nice fellow but it would be ridiculous to contact him over this. So we move on.
nmyshkin said:
I came across this: https://f-droid.org/en/packages/org.jsharkey.sky/
So we move on.
Click to expand...
Click to collapse
Indeed. I spent some time yesterday exploring web-based widgets, thinking we could just point the browser at a URL, but most widgets use HTTPS and Javascript, neither of which are the strong suit of the NST, even with Opera Classic instead of the native browser.
Did this work?
disTrck33 said:
Did this work?
Click to expand...
Click to collapse
Depends on what "this" is.
I eventually wrote my own weather widget app for the NST/G: https://forum.xda-developers.com/nook-touch/themes-apps/app-nst-weather-widget-t3946270
This works.
nmyshkin said:
I came across this: https://f-droid.org/en/packages/org.jsharkey.sky/
It works, which is rare for something so old, but the widgets are butt-ugly on the NST
Looks like I'll be researching changing colors, etc. So far it looks like the icons could be easily replaced, but the most offensive part is the widget background which is a 9-patch png (of course...).
The WeatherACE developer is a nice fellow but it would be ridiculous to contact him over this. So we move on.
Click to expand...
Click to collapse
Link said USA only . There is a weather app that can be used for Europe which uses yr.no site for data. It runs on my tablet and should work with Android 1.5+. Nothing special but good enough. Might require some customization to e-ink display though. That needs to be checked.
SJT75 said:
Link said USA only . There is a weather app that can be used for Europe which uses yr.no site for data. It runs on my tablet and should work with Android 1.5+. Nothing special but good enough. Might require some customization to e-ink display though. That needs to be checked.
Click to expand...
Click to collapse
Didn't remember the US restriction, but all of the potential apps I looked at back then looked terrible on the NST or required network location. That is why (shameless promotion...) I eventually worked up my own Weather widget/app just for the NST. It lacks many bells and whistles but will work for any locale that OWM has stations. And, if I say so myself, looks pretty good on the NST.
nmyshkin said:
Another one bites the dust.
It took awhile for Wunderground's API to actually die, but it finally did and I used my last data point yesterday. None of the other APIs in the app (OpenWeatherMap, Norwegian MET, Yahoo) have worked for awhile. I tried the obvious with OWM and N-MET, getting new API strings, decompiling the app, replacing the APIs and stitching it all back together. But no joy. The data structures in the new APIs are probably different and that's way beyond me. The jiggered app ran, but it was unable to gather data from anywhere (other than what my location is).
Too bad. Nothing left like it, AFAIK.
Click to expand...
Click to collapse
The app is not dead.
I working on adding more weather sources. Atm, the app has 5 weather sources worked correctly - NOAA (USA only), OpenWeatherMap, Norwegian MET (yes, its back to work again, I switched WeatherACE to the their new API), Weatherbit.IO (new weather sources that added to WeatherACE in last build 1.12.30) and Forecast.IO (they are not provide new keys atm). Currently I working on 2 more weather source.
As for Wunderground, they were bought by IBM. The lowest price for weather data from IBM is around of $10000 per year, for a limited set of data. They also provide some weather API for people that provide them data from personal weather stations, but its just current and few days weather and no hourly data forecasts...
So, please check the app again.
mycodefab said:
The app is not dead.
I working on adding more weather sources. Atm, the app has 5 weather sources worked correctly - NOAA (USA only), OpenWeatherMap, Norwegian MET (yes, its back to work again, I switched WeatherACE to the their new API), Weatherbit.IO (new weather sources that added to WeatherACE in last build 1.12.30) and Forecast.IO (they are not provide new keys atm). Currently I working on 2 more weather source.
As for Wunderground, they were bought by IBM. The lowest price for weather data from IBM is around of $10000 per year, for a limited set of data. They also provide some weather API for people that provide them data from personal weather stations, but its just current and few days weather and no hourly data forecasts...
So, please check the app again.
Click to expand...
Click to collapse
No, it's not dead. In fact, I run it on most of my devices. I really appreciate the clean-looking widgets and I would recommend it to anyone looking for a good weather app with widgets.
Sadly, in the context of this forum, it is "as good as" dead since the old version that would still run on Android 2.1 can't connect to any of the weather services any longer
I'm sorry if Google-bots picked up this posting and are making it seem like the app is non-functional. I've edited the post title so that maybe in the future that will be corrected.
nmyshkin said:
No, it's not dead. In fact, I run it on most of my devices. I really appreciate the clean-looking widgets and I would recommend it to anyone looking for a good weather app with widgets.
Sadly, in the context of this forum, it is "as good as" dead since the old version that would still run on Android 2.1 can't connect to any of the weather services any longer
I'm sorry if Google-bots picked up this posting and are making it seem like the app is non-functional. I've edited the post title so that maybe in the future that will be corrected.
Click to expand...
Click to collapse
Hmm... What version of WeatherACE you use on the old device? Its too bad that I didnt used VCS (version control system) in the time (like I do it now). But I still have backups of source code of some really old versions of the app. The oldest is 1.6.2, then 1.7.4, 1.80, etc.
Not sure if Google will allows me to make it (uploading to Google Play will not be possible for sure), but I could try at least. If everything depended on me, the application would continue to support android 2.1 (or 2.3 was in the very first version, I don't remember exactly). Unfortunately, Google constantly demands to gradually raise the minimum API, and with it, support for older devices decreases.
mycodefab said:
Hmm... What version of WeatherACE you use on the old device? Its too bad that I didnt used VCS (version control system) in the time (like I do it now). But I still have backups of source code of some really old versions of the app. The oldest is 1.6.2, then 1.7.4, 1.80, etc.
Not sure if Google will allows me to make it (uploading to Google Play will not be possible for sure), but I could try at least. If everything depended on me, the application would continue to support android 2.1 (or 2.3 was in the very first version, I don't remember exactly). Unfortunately, Google constantly demands to gradually raise the minimum API, and with it, support for older devices decreases.
Click to expand...
Click to collapse
And I completely understand that. It's why I said in post #3 that it would be silly to contact you about this. I still remember how promptly and helpfully you responded to a question I had about more recent versions of the app I was running on my tablet. But restructuring an app that, in Android terms, is nearly an archaeological artifact, is not, I'm sure, a simple matter.
In any case, it looks like this version (1.4.4) is earlier than anything you may still have source code for.
nmyshkin said:
And I completely understand that. It's why I said in post #3 that it would be silly to contact you about this. I still remember how promptly and helpfully you responded to a question I had about more recent versions of the app I was running on my tablet. But restructuring an app that, in Android terms, is nearly an archaeological artifact, is not, I'm sure, a simple matter.
In any case, it looks like this version (1.4.4) is earlier than anything you may still have source code for.
Click to expand...
Click to collapse
Seems like the last version that support Android 2.1 and 2.2 is version 1.7.4 and I have sources for it. The changes log for 1.7.4 has mention about such fixes "Hotfixed crash on devices with android 2.1 - 2.3.X for weather alerts"." The version support WeatherACE API for external apps/widgets/early verions of tasker plugin, weather alerts and Forecast.IO source.
Luckily, there is a place where you can get almost any version of this app https://4pda.ru/forum/index.php?showtopic=511055&st=0 The last spoiler in the start post has links to my posts with most of the versions of WeatherACE. So, if you will have time, please try 1.7.4 from the post https://4pda.ru/forum/index.php?s=&showtopic=511055&view=findpost&p=32402422
If 1.7.4 will work for you. I could try to build it from the sources I have. In case it will build correctly, it will not be so hard to update support for OpenWeatherMap and Norwegian MET.NO weather sources. Probably I also could add support for Weatherbit.IO.
mycodefab said:
Seems like the last version that support Android 2.1 and 2.2 is version 1.7.4 and I have sources for it. The changes log for 1.7.4 has mention about such fixes "Hotfixed crash on devices with android 2.1 - 2.3.X for weather alerts"." The version support WeatherACE API for external apps/widgets/early verions of tasker plugin, weather alerts and Forecast.IO source.
Luckily, there is a place where you can get almost any version of this app https://4pda.ru/forum/index.php?showtopic=511055&st=0 The last spoiler in the start post has links to my posts with most of the versions of WeatherACE. So, if you will have time, please try 1.7.4 from the post https://4pda.ru/forum/index.php?s=&showtopic=511055&view=findpost&p=32402422
If 1.7.4 will work for you. I could try to build it from the sources I have. In case it will build correctly, it will not be so hard to update support for OpenWeatherMap and Norwegian MET.NO weather sources. Probably I also could add support for Weatherbit.IO.
Click to expand...
Click to collapse
That would be amazing. Unfortunately I get a 404 error when I try to download the app. I always get the error on that site. Not sure if you have to be logged in or what. I'll keep searching for the correct version.
nmyshkin said:
That would be amazing. Unfortunately I get a 404 error when I try to download the app. I always get the error on that site. Not sure if you have to be logged in or what. I'll keep searching for the correct version.
Click to expand...
Click to collapse
Please try http://mycodefab.com/files/WeatherACEv1v7v4.apk
mycodefab said:
Please try http://mycodefab.com/files/WeatherACEv1v7v4.apk
Click to expand...
Click to collapse
Thanks so much. I tried this version on two NSTs, one with Network Location enabled and the other without. It works on both to the extent I can judge without any weather data being fetched. No sudden crashes or odd behavior. The map at the initial setup is blank, but that was the case in 1.4.4 (something to do with e-ink and the assumptions for default themes, I guess). Anyway, the map does not matter if you can type in your own geocoordinates which is what I did on the device without Network Location.
So this looks like a good candidate.
nmyshkin said:
Thanks so much. I tried this version on two NSTs, one with Network Location enabled and the other without. It works on both to the extent I can judge without any weather data being fetched. No sudden crashes or odd behavior. The map at the initial setup is blank, but that was the case in 1.4.4 (something to do with e-ink and the assumptions for default themes, I guess). Anyway, the map does not matter if you can type in your own geocoordinates which is what I did on the device without Network Location.
So this looks like a good candidate.
Click to expand...
Click to collapse
OK, thanks. In case you have DarkSky API key (the app know it as Forecase.IO, it was an old name of the DarkSky API) please use it with the version 1.7.4, the app version support the weather source. Once purchased by Apple, DarkSky (Forecast.IO) no longer give out free keys. But any old keys continue to work atm, as far as I know.
Building a new version with updated support for weather sources will take some time. As usual, most problems in the case are not related with app itself, but with other libraries. For example, a library that provided map does not support Android 2.1 anymore, so probably I will need to completely remove map from the app. Google libraries related with analytics and ads - also does not support old android versions anymore. I will work on it this weekend.
nmyshkin said:
Anyway, the map does not matter if you can type in your own geocoordinates which is what I did on the device without Network Location.
Click to expand...
Click to collapse
You need GPS.
nmyshkin said:
So this looks like a good candidate.
Click to expand...
Click to collapse
OK, seems like its done http://mycodefab.com/files/WeatherACEv1v7v4v2.apk Hope it will work, because I dont have Android 2.1 devices to test. In case of problems, I will try to find something.
The version support 2 weather sources - OWM (open weather map) and Norwegian MET.NO.
Limitations:
1. Removed weather map and adding locations via map. I cant find any android weather libraries that support Android 2.1 devices.
2. Removed ads for same reason.
3. Weather icons limited to the small set of icons inside the app + 1 custom icon set.
As for custom icon set, its mostly same as for latest versions of WeatherACE, just a bit different directory for images. Directory is "Android/data/mycodefab.aleph.weather/files/custom/icons/". It use same format as for the latest versions. So, for example, for "clear sky in day" condition it will use "d_100.png" file, "clear sky in night" will look for "n_100.png" file, "overcast" will use "d_104.png", etc.
In case the version of the appt will start, but not show the weather after weather info update, please get to Menu->Settings->Advanced->Weather Sources. Here you could see Active weather sources on the top. Tap on it. Uncheck OpenWeatherMap and Norwegian MET, tap OK. Enter Active weather sources again. Set check OpenWeatherMap and Norwegian MET, tap OK. It will recheck availability of sources for existing locations and will update the weather info.
mycodefab said:
OK, seems like its done http://mycodefab.com/files/WeatherACEv1v7v4v2.apk Hope it will work, because I dont have Android 2.1 devices to test. In case of problems, I will try to find something.
Click to expand...
Click to collapse
I tried the app on both devices (with and without Network Location). Unfortunately it does not want to run
There is immediate funny business as the package shows in the file manager as a generic "package" icon rather than the app icon. Also, the package name (and generic package icon) are displayed in the launcher rather than the app icon and name.
I've attached a section of a logcat for trying to open the app. I don't know whether it has information that is helpful.
It may or may not have any bearing on what you have done, but as you're already going way beyond any expectations, I would suggest that leaving the app alone except for fixing the weather sources would be more than enough. I can understand your desire to have things "right". I have that same problem , and I do appreciate it, but maybe without so many changes there would be a better chance of the app still working, which is what it did even now, except for the access to weather sources. Of course, it's probably not that simple.
Thanks for your efforts.
Two apps that I use on my NST (glowlight) are AlReader and RelaunchX, for which there are still relatively recent apk's to be found. I haven't seen them mentioned here a lot, so here's the link to the latest Alreader that still works on Android 2.1 (hard to find if you don't speak Russian):
http://4pda.ru/pages/go/?u=http://a...340035&usg=ALkJrhhH03h-JtOUNtSq7Dy0YRE5zt-deQ
And here's ReLaunchX, a fork of ReLaunch:
https://f-droid.org/en/packages/com.gacode.relaunchx/
I just fixed my Nook after it stopped working with the 1.2.2 update that I hadn't installed yet, so I'm updating it with some recent apps that still work on it.
Sent from my BLA-L09 using Tapatalk
STEELBAS said:
Two apps that I use on my NST (glowlight) are AlReader and RelaunchX, for which there are still relatively recent apk's to be found. I haven't seen them mentioned here a lot, so here's the link to the latest Alreader that still works on Android 2.1 (hard to find if you don't speak Russian):
http://4pda.ru/pages/go/?u=http://a...340035&usg=ALkJrhhH03h-JtOUNtSq7Dy0YRE5zt-deQ
And here's ReLaunchX, a fork of ReLaunch:
https://f-droid.org/en/packages/com.gacode.relaunchx/
I just fixed my Nook after it stopped working with the 1.2.2 update that I hadn't installed yet, so I'm updating it with some recent apps that still work on it.
Sent from my BLA-L09 using Tapatalk
Click to expand...
Click to collapse
There is also an English version of the Alreader website with app downloads: http://www.alreader.com/?lang=en
nmyshkin said:
There is also an English version of the Alreader website with app downloads: http://www.alreader.com/?lang=en
Click to expand...
Click to collapse
That's true, but despite what it says there, the version up for download there is not actually compatible with Android 2.1. I had to use Google translate on their support forum to find the above version.
Sent from my BLA-L09 using Tapatalk
STEELBAS said:
That's true, but despite what it says there, the version up for download there is not actually compatible with Android 2.1. I had to use Google translate on their support forum to find the above version.
Click to expand...
Click to collapse
Yes, you are correct. I've been trying out v. 1.7.7, which is that same as in your link.
I like it a lot except for two minor issues: the TTS does not work (a very minor issue) on the NST, although if you install the app on another device with native audio support it does work properly, and (more significantly for me), there is no way to address the Library directly. Unlike the author of FBReader, this author has made all of the various activities private so there is no way of accessing them from outside the app. I've been looking at the Android Manifest in the decompiled app, trying to decide if this can be "fixed". I've seen references to dealing with this issue before but now when I want then I can't locate them
nmyshkin said:
Yes, you are correct. I've been trying out v. 1.7.7, which is that same as in your link.
I like it a lot except for two minor issues: the TTS does not work (a very minor issue) on the NST, although if you install the app on another device with native audio support it does work properly, and (more significantly for me), there is no way to address the Library directly. Unlike the author of FBReader, this author has made all of the various activities private so there is no way of accessing them from outside the app. I've been looking at the Android Manifest in the decompiled app, trying to decide if this can be "fixed". I've seen references to dealing with this issue before but now when I want then I can't locate them
Click to expand...
Click to collapse
Ah, yes... Well, I would never use the NST for TTS, so that's no problem for me. As for the library... I take it you mean in the underlying code? Out of interest: what would you use it for? I basically use ReLaunchX to locate the book I want (in my own directory-based library) and open it with Alreader.
The one thing I wish Alreader would provide, myself, is a cover image of the current book to use as a screensaver on the Nook. But that's a minor issue.
STEELBAS said:
Ah, yes... Well, I would never use the NST for TTS, so that's no problem for me. As for the library... I take it you mean in the underlying code? Out of interest: what would you use it for? I basically use ReLaunchX to locate the book I want (in my own directory-based library) and open it with Alreader.
Click to expand...
Click to collapse
I have to confess that I hate Relaunch. I use a more traditional Android structure, including ES File Explorer, but that's not a nice way to browse for books. On two devices I have the B&N system and on one for experimentation I have removed all that and am trying out different readers. I miss the Library.
The one thing I wish Alreader would provide, myself, is a cover image of the current book to use as a screensaver on the Nook. But that's a minor issue.
Click to expand...
Click to collapse
Ah, but it does! Take a look in /media/screensavers and you will discover that it has created a new folder and there is a cover image there for the book you are currently reading. All you need to do is select that folder from the NST Settings app.
nmyshkin said:
I have to confess that I hate Relaunch. I use a more traditional Android structure, including ES File Explorer, but that's not a nice way to browse for books. On two devices I have the B&N system and on one for experimentation I have removed all that and am trying out different readers. I miss the Library.
Ah, but it does! Take a look in /media/screensavers and you will discover that it has created a new folder and there is a cover image there for the book you are currently reading. All you need to do is select that folder from the NST Settings app.
Click to expand...
Click to collapse
Aaaaah. Here I was looking all over for that folder, but for the place where you'd expect it. Well. Great, then.
I never really used the B&N Library app in the first place, I always immediately rooted my Nook and browsed for books in the directory structure, so that helps... Also my meta-data is always a mess so using a real library app wouldn't really work well for me, anyway.
STEELBAS said:
Two apps that I use on my NST (glowlight) are AlReader and RelaunchX.
Click to expand...
Click to collapse
You probably have more experience with AlReader than I do so I thought I'd pose a question which I have not been able to answer.
Is there a way to center the page number in the status bar? I don't have any of the other stuff showing in the status bar but I do want to see the page number, even in full screen. What I don't like is to see it floating at some small indentation from the left margin. You can center the title/author in the Header (which I do not have visible in full screen), but why not the page number? I think the answer is perhaps that the developer wanted to cram in all the other possibilities in the status bar and so each has a certain space allotted to it. I hope not.
I've pored through the settings xml file for AlReader but I can't make sense of much of it. Too many obscure abbreviations. I can't even find the line for centering the title/author in the Header.
Any ideas?
Edit: I made a tiny bit of headway, identifying variables in the xml file that control some aspects of the header and footer. However, as sometimes happens with these files, when you make a change and save the file, the values have reverted back if you return for another look. I'm assuming that the master data must be held in a database so I'll look at that tomorrow.
Edit-Edit: Nope, nope and nope. The databases are all about books. So the values are hidden in the app itself (library files or jars perhaps, who knows?). I spent way too much time squinting at the smali files from the decompiled app but it's just all so much mush to me. Not even a hint that resembles English as to how items are positioned. It's a pity that one of the choices in the Header was not "page". If that were true I'd switch the Header with the Status bar and the problem would be solved. The "page number/chapter" I find useless. Oh well....nothing is perfect.
External library app
I have a ton of bookmarks for NST/G stuff that I was reorganizing this morning and in the process came across this app: https://forum.xda-developers.com/nook-touch/themes-apps/library-app-t2823169
I haven't put it through the wringer yet, so to speak, but it looks reasonably good and books open in whatever the default reader is. If it's reliably functional it may serve as a general library app for whatever reader one chooses. Perhaps worth a look.
I'm trying to install v1.77 on NSTG 1.2.2 but I got error: Parse Error
try the
mrhamed said:
I'm trying to install v1.77 on NSTG 1.2.2 but I got error: Parse Error
Click to expand...
Click to collapse
Try the attached. It works for me.