Related
The official Facebook app for Android is now available in the market. Looks a pretty solid release. Loving the widget.
A lot of people, at least in Sweden is reporting it to crash at startup. I'm running latest MoDaCo ROM.
How come application is released by katana-something. How do one actually know this application is an officially one?
bear78 said:
A lot of people, at least in Sweden is reporting it to crash at startup. I'm running latest MoDaCo ROM.
How come application is released by katana-something. How do one actually know this application is an officially one?
Click to expand...
Click to collapse
crach here to. Modaco 2.0
Crash here on HTC Generic 2.73.405.5 with radio 63.18.55.06EU_6.35.06.18
Doesn't look like an official application to me, no matter what it says in the description.
According to the application link
http://www.facebook.com/apps/application.php?id=74769995908
On the left hand side in the information box
This application was not developed by Facebook.
Click to expand...
Click to collapse
Okay chanced language for the os from danish to english and now it works just fine
seems slow and laggy and has less options than a mobile site :/
Developers email: [email protected]
About as official as a 419 scammer purporting to be from the IMF with an email address like [email protected], with an offer of a share of a few million quid!
Regards,
Dave
Alright... Somebody should change the thread title
Yes and no. It IS the "official" Facebook app, and most certainly must have been developed WITH Facebook. Actually, even the iPhone app development page said it was not developed by Facebook up until v. 3 (I think). --And it definitely was. They just gave credit initially to the FB employee who had done the coding. The story behind this app is that Google "lent" FB an Android dev to create this app.
The Palm, Blackberry, and other "official" FB apps also say they were not made by Facebook. Click "mobile" on your computer at the bottom of the screen and check them all out. FB does this for some reason. Also, any previous apps that have been developed have been forced to remove the word "Facebook" from their names. Bloo was originally called something different, and he was forced to change the name. This is why we have "Babbler", "Bloo", "Fbook", etc. You know every one of those devs would have preferred to name their apps "Facebook". I have no doubt this app is developed officially in conjunction with Facebook.
http://androidcommunity.com/facebook-for-android-hits-market-20090908/
Works fine for me! No crash on modaco 2.0
Yeh, as Switchbitch said, it IS the official Facebook app, but it was NOT created by Facebook, but rather, in association with Facebook.
And in regards to crashing - working perfectly fine here on MCR 2.1e.
MCR 2.2 Here. No crashing, and every bit as cool as the iPhone app from what I can tell.
iPhone version is obviously going to be a lot more feature-filled and stable (seeing as they're already at version 3.x) but I can picture the Android one improving over time.
The app is the same one shown in the leaked images a few weeks back and when installed and used the 1st time you must accept the facebook terms and conditions.
Does not crash for me at all, is pretty fast however i have noticed that i seem to get notifications from babbler way before this app notifies me about anything.
From reading about the app previously you would have known that it wasnt going to be as advanced as the iPhone app and wouldnt have access to items such as your inbox.
This app is based entirely on the new stream system that facebook usues.
On a side note, does anyone know how to skin the widget and the notification icons?
which one is the "official" one?
i can see quite a few out there like facebook lite, mobile facebook etc etc
This is rubbish. You can see people's walls and your own, but no access to your inbox for private messaging...?
And how do you update your status rather than just post to your... "wall". I think the problem is that Facebook has changed since i used it last and I don't understand it!
They released a version this morning that didn`t work. Force quit during startup.
Around lunchtime they released an update. Now everything is work as it should. Pure joy!
So, it seems status updates now go straight to the wall rather than being seperate. and are archived to your wall. Then the news feed gets everyones comments and status updates. You can also post on someones wall if you wish, as well as commenting directly on thier status. I get it. I think
Well, it's missing friend search, and messaging.
Battery life
Has anyone else noticed this chewing through the battery? Since installing this I've been watching the percent left drop on a frequent basis. I've got it set to update every hour.
EDIT
Forget that, it was just me being paranoid. Fully charged the phone last night, unhooked it from the mains this morning at 7am and currently power is sitting at a very respectable 99%.
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.
Really TICKED OFF that the MMS is dead. Read everything I can find on other Forums and nothing has worked. Going to start a new thread here because this seems to be the only place on the web where device specific discussion, especially for these this device, happens.
I am being offered a HUGH OTA update but it doesn't say what it is.
I am in the USA and the device actually came from India.
Anyone in the USA know if this is the 6.0.1 update and does the device retain full phone capability??
10/25/16
OK going to answer my own question.
Yes it is the update to 6.0.1
Did a lot of research before moving on with the download.
It will complete the download and then give you some instructions.
It will also list the Versions and build numbers. Looked those up to find out what reagion they were for and that told me I was getting a version for Australia so I was sure I was going to get to keep the phone function. I Did.
The research I did gave a bunch of instructions and cautions about backing up all your data and apps. WAS NOT NECESSARY. Every APP I had was reloaded and all of my screens were restored just like before. It even saved my APN DATA for the phone. The only oddity was that it put some shortcuts on the home screen to some of my Drive files and to my voicemail quick dialer.
General observations:
I HATE the SMS APP now. Lost a lot of control over the background and bubble appearance.
Not real enthused about the new drop down menu background and icon definition either.
The problem is both cases is that the backgrounds are white/light grey and the icons/bubbles are medium blue. Not a lot of contrast so they will be hard to see in bright light.
The new MEMO APP is going to take some getting used to but, I think I will like it.
Cut Right Sharpening said:
Really TICKED OFF that the MMS is dead. Read everything I can find on other Forums and nothing has worked. Going to start a new thread here because this seems to be the only place on the web where device specific discussion, especially for these this device, happens.
I am being offered a HUGH OTA update but it doesn't say what it is.
I am in the USA and the device actually came from India.
Anyone in the USA know if this is the 6.0.1 update and does the device retain full phone capability??
10/25/16
OK going to answer my own question.
Yes it is the update to 6.0.1
Did a lot of research before moving on with the download.
It will complete the download and then give you some instructions.
It will also list the Versions and build numbers. Looked those up to find out what reagion they were for and that told me I was getting a version for Australia so I was sure I was going to get to keep the phone function. I Did.
The research I did gave a bunch of instructions and cautions about backing up all your data and apps. WAS NOT NECESSARY. Every APP I had was reloaded and all of my screens were restored just like before. It even saved my APN DATA for the phone. The only oddity was that it put some shortcuts on the home screen to some of my Drive files and to my voicemail quick dialer.
General observations:
I HATE the SMS APP now. Lost a lot of control over the background and bubble appearance.
Not real enthused about the new drop down menu background and icon definition either.
The problem is both cases is that the backgrounds are white/light grey and the icons/bubbles are medium blue. Not a lot of contrast so they will be hard to see in bright light.
The new MEMO APP is going to take some getting used to but, I think I will like it.
Click to expand...
Click to collapse
What was wrong with the 815Y stock messaging sms app? Compared to the 815?
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!
So in what appears to be yet more anti-consumer behavior, by trying foist yet more online-required services upon us into thier ROM's. In this instance it appears Samsung has replaced a local app/function that worked just fine (in thise case number blocking) with an online component.
Rant aside I am fairly sure and thought I had not removed any app that did local number blocking (isnt this part of the phone app), however I do remember seeing a number blocking service (which is an online service) - which of course I have no f-ing interest in using due security/privacy concerns.
So in order for me to try and troubleshoot and narrow down what app the the phone and messages app are trying to open when I want to block a number, can someone remind me what the blocking serevice app was called? I think its might be ' com.hiya.starcom.hiya.star ' (thats the online service I was referring to earlier)
a timely response of yes that's it from me lol
hah better late than never, but already figured it out. And I had already forcebly removed it from the rom and its causing the phone/contacts app to FC. So I have 2 choices atm, reflash the stock rom again and then just hide the ' com.hiya.starcom.hiya.star ' serivce and thats assuming it will hide.
or
Just wait for the custom rom thats being worked on atm to be released and then just flash that from twrp.
can you just find and push the apk ?