I have a Sharepoint site so I can create collaboration sites super duper easy.
I'm not sure if we have an app list yet....but here's one.
http://sp.texultant.apps4rent.info/MoSo/NC/Lists/App List/AllItems.aspx
It's wide open, anybody can anonymously add and edit posts....so be nice....If it gets abused I'll have to lock it down and require logins....you don't want that hassle do you?
Perhaps it may be a good idea to include the most recent version number tested of each app?
HLOsHubby said:
Perhaps it may be a good idea to include the most recent version number tested of each app?
Click to expand...
Click to collapse
Done ... AppVersion
Thanks for the site. Great idea!
Other Apps
Could someone check whether USA today, NY Times, Twitter, Facebook and GV apks work on a rooted nook color. Planning on ordering one and rooting.
Yes, I know it wont make phone calls, but want to see if it will notify of texts.
Also, I see people installing Google Maps. Can it be used to find your location?
Thanks in advance.
Search through this thread to see if anyone has gotten them to work. Its over in the Nook Color Android Development forum.
http://forum.xda-developers.com/showthread.php?t=857434
I'm sorry if this has already been debated elsewhere. I did search and try to locate threads on this already, but didn't come up with anything which (seemed) relevant to this problem.
If anyone has a link handy for another thread which already discusses this, I'll close the thread if that is wanted.
With that said... Here's my issue.
As stated elsewhere, one of the main things which excited me about Gingerbread was the ability to do native SIP dialing. About time, I say! Now I've flashed Gingerbread on my SGS and so far the results has been below underwhelming.
From what I can tell this is how you get SIP/VoIP/Internet calling on your phone using Gingerbread:
1. Sign up for Google Voice.
2. Install Google Voice and sign in.
3. Voila. Your Gingerbread Android-device now has a bunch of SIP settings and options.
This is ofcourse, unless your manufacturer has somehow crippled your phone's software.
That might be the case with Samsung's firmware, but I wouldn't know because the steps outlined above is absolutely impossible for anyone outside the US. You cannot sign up for Google Voice anywhere else. End of story.
So. Is this for real? Did Google release a smartphone OS for worldwide consumption, touting "native SIP", native internet calling as feature and then implement it in a way which means it will only work in one country, all else be damned?
I seriously find this very hard to believe. There has to be a way to get this functionality up and running otherwise. Seriously? The internet maestros at Google implements a core OS-level function tied to (one) geo-location? Is third-party solutions ala Sipdroid the solution for everyone else?
So... Please tell me I am completely mistaken and that there are steps for getting SIP running on my phone, despite me not have an adress of residency ending in "US".
Any hints or links in any direction so that I can actually get to try this out would be über appreciated.
Bump.
I realize posting this while Europa were getting ready for sleep and only US-people were around might have been bad timing.
Just bumping this again to see if there's any more response. I can't seriously be the only one wondering about this.
If bumping is severely against forum policies, let me know and I'll make a note of it and wont do it again.
http://forum.xda-developers.com/showthread.php?t=1043016
Use this zip as an update from CWM recovery, enables the menu "Internet call settings" under "Call settings".
Works on odex and deodex ROMS [I have the same JVB as the OP]
Problem solved
Thanks Vinnie.
Since I already have some framework-res.apk dependent mods, I just pushed the permissions-file as mentioned in that thread, and now I have "Internet calling options" available.
Yes, I realize this will only work while on wifi and SIP over 3G will be disabled, but at least it gives me something to experiment with so that later I will know if handing over my other mods for 3G VoIP/SIP will be worth it.
Thanks for the response and handy link. Now if XDA had better search, I might not have needed to pollute the forums with duplicates like this
Edit: Checked the entire thread and saw that there is an update.zip with eyecandy as well. Will try it out later.
Hey guys, I'm relatively new to the android programming scene and I'm trying out a simple app idea I have. My app idea is to be a way for people to make posts to facebook and that's it. I've got the code working but what really bugs me is how the logging in system works and how the posting system works. The way I have done it, the app does not handle the authentication flow nor the posts, but rather a pop-up comes up and asks them to sign in or make a post - similar to using the browser. This does not work with the design of the rest of the app along with slowing it down. I need help. I want my app to authorize the user, similar to how the official Facebook android app logs people in; there are no pop-ups and everything is handled by the app (same to be done with making posts). If you guys could help me out by blatantly telling me what to do, sending me any articles that explain how to do it, or any other help I would appreciate it. Thanks!
NOTE: I have glanced around the Facebook developer site and I'm completely confused by their documentation. I know there's something about fragments, but I'm not sure if I understand it completely.
Okay guys, I found this thread at Stack Overflow and found the answer. In case anyone else had a similar question. http://stackoverflow.com/questions/...x-send-to-the-users-wall-with-facebooks-andro
I have the Amazon version of the G7 Plus. On my home network, I am running Pi-Hole as a DNS server. When reviewing the logs on Pi-Hole, the most active device on the network is my phone. Among the requests it send out, it is trying to send requests to 'web.facebook.com', 'graph.facebook.com' and connect.facebook.net'
I have never had Facebook installed on this phone. I don't use a web browser to access it either. I have closed all my apps and disable background data on all installed apps. It is still trying to talk to Facebook.
Is there a way I can identify what app is making these requests? In a 24-hour period, it has made nearly 500 requests. That boil down to a request every 3 min 30 seconds. If I can identify the app, I can decide if it's worth keeping.
mrschwarz said:
I have the Amazon version of the G7 Plus. On my home network, I am running Pi-Hole as a DNS server. When reviewing the logs on Pi-Hole, the most active device on the network is my phone. Among the requests it send out, it is trying to send requests to 'web.facebook.com', 'graph.facebook.com' and connect.facebook.net'
I have never had Facebook installed on this phone. I don't use a web browser to access it either. I have closed all my apps and disable background data on all installed apps. It is still trying to talk to Facebook.
Is there a way I can identify what app is making these requests? In a 24-hour period, it has made nearly 500 requests. That boil down to a request every 3 min 30 seconds. If I can identify the app, I can decide if it's worth keeping.
Click to expand...
Click to collapse
There is a factory facebook installer app trying to do its job...so its got all your radios looking for a download its not getting or the illuminati planning a dark plot against society.... Moto is probably the last phone to still have that and probably the first...lol... if you are rooted with magisk I would install the terminal debloater mod and follow the directions...super easy and is something I wish I had back in the day....i just reflashed stock on mine and flashed back twrp and magisk...ill put the specific apk info shortly
My phone is pure stock. Not rooted. I thought we vanquished the Illuminati. Sneaky bast*rds.
[/COLOR]
KtownJeff said:
3 apps that facebook uses to mess with life /system/app/facebook -appmanager
/system/priv-app/facebook-installer
/system/priv-app/facebook-services
If you are stock it can be defeated by using adb pull commands .... I can walk through it if you havent done it before but this thread will cover it all just follow step by step and I believe after OTA you will have to do it again.. nope new info i just obtained states that u wont have to do it again and you can debloat the Amazon stuff too
https://www.xda-developers.com/uninstall-carrier-oem-bloatware-without-root-access/
Click to expand...
Click to collapse
:good::good:
So...I followed the instructions for adb. Since this was an unlocked phone that I bought from Amazon and since I am using a prepaid MVNO, I wasn't sure what to put in the 'OEM' or 'Carrier' variables. I downloaded and installed the App Inspector app. I scrolled through every entry on the list and could not find any that had anything resembling Facebook in it.
Anything else I can try? Thanks for all your help.
mrschwarz said:
So...I followed the instructions for adb. Since this was an unlocked phone that I bought from Amazon and since I am using a prepaid MVNO, I wasn't sure what to put in the 'OEM' or 'Carrier' variables. I downloaded and installed the App Inspector app. I scrolled through every entry on the list and could not find any that had anything resembling Facebook in it.
Anything else I can try? Thanks for all your help.
Click to expand...
Click to collapse
I did a little more research and found out that its other apps reporting to facebook.... they share data and facebook plugs it into an ad algorithm....hmmmm.... read these articles https://www.cnbc.com/2020/01/29/fac...-you-from-other-web-sites-how-to-stop-it.html
https://gist.github.com/imcodingideas/f07be3889411b323e5f8051899b9d9cc
KtownJeff said:
I did a little more research and found out that its other apps reporting to facebook.... they share data and facebook plugs it into an ad algorithm....hmmmm.... read these articles https://www.cnbc.com/2020/01/29/fac...-you-from-other-web-sites-how-to-stop-it.html
https://gist.github.com/imcodingideas/f07be3889411b323e5f8051899b9d9cc
Click to expand...
Click to collapse
Since years this service is a part of almost every app for Android.
WoKoschekk said:
Since years this service is a part of almost every app for Android.
Click to expand...
Click to collapse
I just got the memo...lol....Ive only been at it two years so Im still learning all the time
8-31-21: My report on the death of this app for the NST is a little premature. See post #5, etc., for a "fix". It worked for the poster and it worked for me. It might work for you.
Don't shoot the messenger...
Sometime in late 2020 or early 2021 it became impossible to negotiate an initial login with the Kindle app (yes, even with the OTP they email you). I've checked the security certificates and they are fine. I've tried installing the app on newer devices, going all the way to Oreo. Same behavior. A logcat on the NST shows a failed SSL negotiation so it looks like the server just won't talk to the old app any longer--at least for an initial authorization. That's the very bad news.
There is a tiny bit of good news for those who already have the Kindle app installed and authorized. At least on my three devices it continues to function completely. You can still check out Overdrive Kindle books and send them to your device and the same book on different devices appears to sync. You can also sideload .mobi books and read those. The clock is, however, probably ticking.
I mention this as a warning for anyone who has a legacy Kindle installation and is thinking of doing major work on their device. If you uninstall or wipe out the Kindle app, it's gone for good. It may be possible to use something like Titanium Backup to restore the app. I was able to find all this out after a reset and then restore my NookManager backup and the app worked fine.
Edit: I have done a little experimenting and the app authorization token appears to include a lot about the device and system. So it's not possible to use Titanium Backup. I tried this on a FW 1.2.1 installation with a working copy of Kindle. Then I updated and rooted FW 1.2.2, installed the Kindle app and then restored a Titanium backup from the same device (but with FW 1.2.1). It failed to initialize, asking to register again. I've had success only in restoring a NookManager backup from the same device with the same FW, etc., and in cloning a device from a NookManager backup. This is not something I would necessarily recommend, but you might have your reasons. However, when I tried to correct the MAC address, this threw off the Kindle app token and it reverted to asking for registration again. So there's very little wiggle room for preserving a working installation if you have to do any significant changing.
I have seen your report in the thread where you were trying to help another forum member to overcome the issues he had with his device. This strengths my beliefs that for resolving the SSL issue work on kernel(s) must be done. Question is where exactly? In Linux kernel or somewhere in Android? What SSL is used on NST if the snag is in Linux - OpenSSL or LibreSSL?
In the defense of the NST I must say that recently saw on YouTube video someone put Alpine Linux on Kindle PW3. What am I trying to say is that older generation of this kind of devices suffer from same illness regardless of brand manufacturer pushing people to just abandon the legacy software on them and create their own custom made one tailored for their devices and their intended way of use.
If the SSL layer is somewhere in Android oh boy that might be harder cookie to bake from my point of view.
SJT75 said:
I have seen your report in the thread where you were trying to help another forum member to overcome the issues he had with his device. This strengths my beliefs that for resolving the SSL issue work on kernel(s) must be done. Question is where exactly? In Linux kernel or somewhere in Android? What SSL is used on NST if the snag is in Linux - OpenSSL or LibreSSL?
In the defense of the NST I must say that recently saw on YouTube video someone put Alpine Linux on Kindle PW3. What am I trying to say is that older generation of this kind of devices suffer from same illness regardless of brand manufacturer pushing people to just abandon the legacy software on them and create their own custom made one tailored for their devices and their intended way of use.
I
Click to expand...
Click to collapse
SJT75 said:
I have seen your report in the thread where you were trying to help another forum member to overcome the issues he had with his device. This strengths my beliefs that for resolving the SSL issue work on kernel(s) must be done. Question is where exactly? In Linux kernel or somewhere in Android? What SSL is used on NST if the snag is in Linux - OpenSSL or LibreSSL?
Click to expand...
Click to collapse
My understanding of the issues is very limited. I once happened into a discussion where it was stated that apps which need to communicate with external servers contain their own SSL certificate which has an expiration date. If so, apps like that just die a "natural" death.
It's actually amazing that there are some apps requiring logins that still work on the NST. Two that come to mind are ancient versions of Pandora and TuneIn Radio. I use both and they still perform flawlessly. For now.
Until today I didn't know what Pandora is but I am familiar with TuneIn radio app. Good to know that some of those apps is still working. Well it just had to be complicated with SSL/TLS hidden somewhere in Android layer. I totally understand why people like Android user friendly UI and apps availability. Still gamble with Java seems that didn't paid of regarding promised platform crossing ability.
So either porting to a new Android version which probably will not be very new (low RAM) or making custom Linux which is anything but user friendly?
Edit: Scratch that question about Linux and the app OP mentioned! I just realize that there is no Linux Kindle app. It could be used through Wine and such witchcraft but that is stupid way of doing things on this device. Better option is to use it on PC and then pass it on to NST using Calibre IMHO. SSL/TLS although remains as weak spot for the time being. Oh well... If that issue with certificates get somehow fixed maybe Kindle cloud reader from browser could reclaim at least part of functions of dedicated Kindle app.
For what its worth I recently got a NST and managed to get the kindle app running this morning. I upgraded to FW 1.2.2, rooted with Nook Manager, and installed the app with adb. The sticking point for me was that I had to go into my Amazon account and disable two-factor authentication. When I tried to log in with the app it still gave the bad password error, and Amazon still sent a text message with an OTP, and that let me log in. This same process DID NOT work if I had two-factor auth turned on in my Amazon account.
I don't understand why they still sent an OTP when two-factor auth is turned off, but they did, and it worked.
wrexroad said:
For what its worth I recently got a NST and managed to get the kindle app running this morning. I upgraded to FW 1.2.2, rooted with Nook Manager, and installed the app with adb. The sticking point for me was that I had to go into my Amazon account and disable two-factor authentication. When I tried to log in with the app it still gave the bad password error, and Amazon still sent a text message with an OTP, and that let me log in. This same process DID NOT work if I had two-factor auth turned on in my Amazon account.
I don't understand why they still sent an OTP when two-factor auth is turned off, but they did, and it worked.
Click to expand...
Click to collapse
Wow! This is very good news. I'll give it a try tomorrow on a fresh system and see if I can get it to work.
Did you by any chance go back and turn on the two-factor login and see if the app still connected after first initializing it?
nmyshkin said:
Wow! This is very good news. I'll give it a try tomorrow on a fresh system and see if I can get it to work.
Did you by any chance go back and turn on the two-factor login and see if the app still connected after first initializing it?
Click to expand...
Click to collapse
Yes, I should have mentioned that. I re-enabled two-factor and downloaded a book to test, everything worked fine. I'm currently using this (https://forum.xda-developers.com/t/app-eink-friendly-amazon-kindle-3-2-0-35.2024062/) version of the app, but I don't think it should matter much.
wrexroad said:
Yes, I should have mentioned that. I re-enabled two-factor and downloaded a book to test, everything worked fine. I'm currently using this (https://forum.xda-developers.com/t/app-eink-friendly-amazon-kindle-3-2-0-35.2024062/) version of the app, but I don't think it should matter much.
Click to expand...
Click to collapse
Excellent. As I expected based on legacy installs continuing to work, once the credentials are on the device, you're good to go whether you use single or two factor login after.
I had a password issue with Amazon awhile back and I'll bet that's where the problem originated. When I changed my password, authentication must have gone to two-factor. I need to check that, but I'm pretty sure that's it. What great news! Back to seamless library book checkout and download, all on the device!
BTW, the version of the app you mention is the only one that works (again!) on the NST.
Something is weird on the Amazon side right now. Even though two factor was turned off, they still sent the OTP. The only difference is that it actually worked when two-factor was disabled, but didn't work when it was enabled. Very strange.
wrexroad said:
Something is weird on the Amazon side right now. Even though two factor was turned off, they still sent the OTP. The only difference is that it actually worked when two-factor was disabled, but didn't work when it was enabled. Very strange.
Click to expand...
Click to collapse
Mmm... I'm glad you posted this before I started testing. I have two NSTs with working Kindle apps right now and I don't want to trash those while tracking down the "solution". I need to think about how I'm going to approach this.
OK, I think my last message was a little unclear.
What I meant was that with two-factor enabled you are supposed to be able to log in with a legacy device, have it give you a password error, receive an OTP via text or email, then use the OTP to actually log in. However, this does not work when two-factor is enabled.
What does work is first disabling two-factor auth, then trying to log in. You will still get a password error, they will still send you an OTP and the OTP will now let you log in and register the device.
This is what I meant when I said something was weird, when two-factor is disabled they shouldn't even be sending you an OTP. It's like disabling two-factor makes it work correctly, rather than turning it off.
To be absolutely clear, once I registered the app, I was able to download a book when two-factor was either on or off. The only thing that was affected was the ability to do the initial sign in.
wrexroad said:
OK, I think my last message was a little unclear.
What I meant was that with two-factor enabled you are supposed to be able to log in with a legacy device, have it give you a password error, receive an OTP via text or email, then use the OTP to actually log in. However, this does not work when two-factor is enabled.
What does work is first disabling two-factor auth, then trying to log in. You will still get a password error, they will still send you an OTP and the OTP will now let you log in and register the device.
This is what I meant when I said something was weird, when two-factor is disabled they shouldn't even be sending you an OTP. It's like disabling two-factor makes it work correctly, rather than turning it off.
To be absolutely clear, once I registered the app, I was able to download a book when two-factor was either on or off. The only thing that was affected was the ability to do the initial sign in.
Click to expand...
Click to collapse
OK, that's what I had hoped for and expected since my two working installs were made before my auth. got changed to two-factor. With really old apps you never quite know how server negotiation is going to evolve.
I hope to give it a try later today.
wrexroad said:
To be absolutely clear, once I registered the app, I was able to download a book when two-factor was either on or off. The only thing that was affected was the ability to do the initial sign in.
Click to expand...
Click to collapse
When I went to my Amazon account it seemed like 2SV was not enabled, by which I mean that clicking on "edit" for the settings generated an email which contained a link that took me to a page with a button that said "Get Started".
I didn't pursue this. I didn't see anything about turning it off--or should I have gone farther along?
That's odd, it does sound like it's not turned on... If you didn't have other devices that you were worried about I would say that you should just turn it on then try to log in. If that doesn't work, turn it off and try again. I think the risk is minimal, but clearly there is something different about your account, so it's up to you.
wrexroad said:
That's odd, it does sound like it's not turned on... If you didn't have other devices that you were worried about I would say that you should just turn it on then try to log in. If that doesn't work, turn it off and try again. I think the risk is minimal, but clearly there is something different about your account, so it's up to you.
Click to expand...
Click to collapse
Yeah, this is not working for me. I looked at the 2SV stuff again this morning and thought, "well, I'll just set it up and then disable it". Except I don't own a mobile phone (no, truly, just an emergency ancient (non-text message) device I keep in my glove compartment), and the QR thingy woud do me no good with the NST. So I'm cooked.
Despite apparently not having 2SV set up, now I can't even generate an OTP email when I try to login with the Kindle app. But my two working installations continue to function. Puzzlement.
Edit: I had a friend with a mobile phone help me out. So I finally got to where I could "disable" 2SV. But it made no difference. Still can't log in or even generate an OTP email by trying to log in. I'm glad this worked for you and I'd like to think it might work for others, but alas my account appears to be "special".
Edit-Edit: Yeehaw! It took a lot of fumbling for me with the unwieldy password I had to recreate in the near past, but by clearing the dalvik cache and making sure that 2SV was actually listed as "disabled" at Amazon, I was finally able to log in a new installation!!! Now I don't have to run a "clone" of another device on this particular NST. Thank you, @wrexroad, for taking the time to look into this and communicate your findings. One big step back from the brink for the Kindle app
That's awesome, I'm glad you got it running! In the future, if you need to get a password via text, you can use a temporary number here: https://sms24.me/en/countries/us/
Hey folks,
I just stumbled into this NST world and want to share my experience with the Kindle app. I'm on FW 1.2.2, and used NookManager to root. I replaced the certs file as recommended in another thread. Once I was ready to login, I enabled 2fa on my Amazon account in a browser. The instructions there clarified that I would need to use PASSWORD+OTP when registering my device. Previously I had tried only the OTP, or only my normal passwrord, but those failed. Appending the OTP to my password, I was able to login.
Hope that helps anyone else who has reached this point.