Gmail app keeps kicking out/closing - Fire Q&A, Help & Troubleshooting

I have a brand new kindle fire 7, just did the steps for installing Google play store, installed a few apps but the gmail app won't stay open and work.... What do I do now?

Same with me. I would love to find the answer to this. Thanks.

I'm having the same problem... Have tried most of the standard attempts to fix it. It did refresh the messages initially, but it still opens, then immediately closes. (Still shows it's running and have cleared that, rebooted, etc). Very frustrating! (Sorry.... probably the wrong thread, but's happening on my new Fire 8HD 2017 too)

Getting the same error here, so I did a logcat on it:
Code:
E/DatabaseUtils(15437): Writing exception to parcel
E/DatabaseUtils(15437): java.lang.SecurityException: Permission Denial: reading com.android.providers.downloads.DownloadProvider uri content://downloads/all_downloads/73 from pid=15497, uid=10016 requires android.permission.ACCESS_ALL_DOWNLOADS, or grantUriPermission()
E/DatabaseUtils(15437): at android.content.ContentProvider.enforceReadPermissionInner(ContentProvider.java:539)
E/DatabaseUtils(15437): at android.content.ContentProvider$Transport.enforceReadPermission(ContentProvider.java:452)
E/DatabaseUtils(15437): at android.content.ContentProvider$Transport.enforceFilePermission(ContentProvider.java:443)
E/DatabaseUtils(15437): at android.content.ContentProvider$Transport.openTypedAssetFile(ContentProvider.java:388)
E/DatabaseUtils(15437): at android.content.ContentProviderNative.onTransact(ContentProviderNative.java:313)
E/DatabaseUtils(15437): at android.os.Binder.execTransact(Binder.java:446)
W/GAV2 (15497): Thread[Background tasks,5,main]: dispatch call queued. Need to call GAServiceManager.getInstance().initialize().
--------- beginning of crash
E/AndroidRuntime(15497): FATAL EXCEPTION: Background tasks
E/AndroidRuntime(15497): Process: com.google.android.gm, PID: 15497
E/AndroidRuntime(15497): java.lang.SecurityException: Permission Denial: reading com.android.providers.downloads.DownloadProvider uri content://downloads/all_downloads/73 from pid=15497, uid=10016 requires android.permission.ACCESS_ALL_DOWNLOADS, or grantUriPermission()
E/AndroidRuntime(15497): at android.os.Parcel.readException(Parcel.java:1548)
E/AndroidRuntime(15497): at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:185)
E/AndroidRuntime(15497): at android.database.DatabaseUtils.readExceptionWithFileNotFoundExceptionFromParcel(DatabaseUtils.java:148)
E/AndroidRuntime(15497): at android.content.ContentProviderProxy.openTypedAssetFile(ContentProviderNative.java:691)
E/AndroidRuntime(15497): at android.content.ContentResolver.openTypedAssetFileDescriptor(ContentResolver.java:1080)
E/AndroidRuntime(15497): at android.content.ContentResolver.openAssetFileDescriptor(ContentResolver.java:921)
E/AndroidRuntime(15497): at android.content.ContentResolver.openFileDescriptor(ContentResolver.java:778)
E/AndroidRuntime(15497): at android.content.ContentResolver.openFileDescriptor(ContentResolver.java:733)
E/AndroidRuntime(15497): at android.app.DownloadManager.openDownloadedFile(DownloadManager.java:1040)
E/AndroidRuntime(15497): at ene.a(SourceFile:636)
E/AndroidRuntime(15497): at ene.a(SourceFile:439)
E/AndroidRuntime(15497): at com.google.android.gm.job.DownloadCompleteJob.a(SourceFile:40)
E/AndroidRuntime(15497): at eks.run(Unknown Source)
E/AndroidRuntime(15497): at android.os.Handler.handleCallback(Handler.java:739)
E/AndroidRuntime(15497): at android.os.Handler.dispatchMessage(Handler.java:95)
E/AndroidRuntime(15497): at android.os.Looper.loop(Looper.java:135)
E/AndroidRuntime(15497): at android.os.HandlerThread.run(HandlerThread.java:61)
It appears that com.google.android.gm doesn't have the permissions it needs (ACCESS_ALL_DOWNLOADS), so I tried to grant this permission with:
Code:
adb shell pm grant com.google.android.gm android.permission.ACCESS_ALL_DOWNLOADS
but I got:
Code:
Operation not allowed: java.lang.SecurityException: Package com.google.android.gm has not requested permission android.permission.ACCESS_ALL_DOWNLOADS

Anyone find a solution to this?

Try disabling "Download attachments" under Gmail's account settings while disconnected from WiFi.

Zeranoe said:
Try disabling "Download attachments" under Gmail's account settings while disconnected from WiFi.
Click to expand...
Click to collapse
Yes, I tried that...

Having the same issue. Can we downgrade the gmail app or something?

cduced said:
Having the same issue. Can we downgrade the gmail app or something?
Click to expand...
Click to collapse
Nope - characteristic if the underlying components that Gmail relies on. Can't downgrade those; will either fail or immediately self-updating to latest version. Look to another mail client (many fine options in Play Store) or use web interface.

gmail app quits
same problem - same with inbox spp. starts for few seconds then goes away. is still running but not in screen!
---------- Post added at 04:51 PM ---------- Previous post was at 04:38 PM ----------
just got off the phone with Amazon. needless to say they do not troubleshoot Google's apps! Nice guy, second tier informed him. so either Google fixes this or we are SOL! Maybe if we get a long enuf thread here! Anyone here work for Google?

carlscheider said:
same problem - same with inbox spp. starts for few seconds then goes away. is still running but not in screen!
---------- Post added at 04:51 PM ---------- Previous post was at 04:38 PM ----------
just got off the phone with Amazon. needless to say they do not troubleshoot Google's apps! Nice guy, second tier informed him. so either Google fixes this or we are SOL! Maybe if we get a long enuf thread here! Anyone here work for Google?
Click to expand...
Click to collapse
Unlikely either party will pursue a 'fix' as Amazon and Google don't pursue mutual business objectives or cross validate apps. Especially hacks. Best option IMO is to consider a different mail app (there are many fine alternatives in the Play Store) or use the Gmail web interface (spartan but serviceable).

thanks
that makes perfect sense. i do use an email app but prefer gmail direct.
i will hold out hope. Had the same problem with Amazon's washington post - it finally fixed itself! found i could sometimes get it to work by just shutting it off normally.
i used to be a cto - crappy code lives forever. no attention to zero defect.
appreciate the wisdom. saves a few frustrating calls.

carlscheider said:
that makes perfect sense. i do use an email app but prefer gmail direct.
i will hold out hope. Had the same problem with Amazon's washington post - it finally fixed itself! found i could sometimes get it to work by just shutting it off normally.
i used to be a cto - crappy code lives forever. no attention to zero defect.
appreciate the wisdom. saves a few frustrating calls.
Click to expand...
Click to collapse
I suspect (but have no direct evidence to support) a new dependency on a core Google component not included with the basic Play Store install for this device (FireOS v5 in general). Haven't peeled back the onion to identify root cause as I do not run FireOS on any of my devices. Do have temporary access to a 'stock' HD 8. Will take a look if time permits.
Could simply be a version mismatch on Android code shared between FireOS and Google components. That would be a tougher fix on unrooted devices.

Davey126 said:
I suspect (but have no direct evidence to support) a new dependency on a core Google component not included with the basic Play Store install for this device (FireOS v5 in general). Haven't peeled back the onion to identify root cause as I do not run FireOS on any of my devices. Do have temporary access to a 'stock' HD 8. Will take a look if time permits.
Could simply be a version mismatch on Android code shared between FireOS and Google components. That would be a tougher fix on unrooted devices.
Click to expand...
Click to collapse
I am a little surprised too. You can download it from the Play Store from the tablet so it's not to do with compatibility I don't think. I had the same problem earlier with Weather Underground and I downgraded a few versions and it worked. Could be an update Amazon snuck by us too. The tablet kicks you out right after you setup Gmail. It's like you can do everything else except read your Email. It even still sends you notifications. I thought it was working after my reset an hour ago because of the notifications. I tapped the icon, it went to setup and when it got to the inbox, it kicks me out. I'll reinstall it later using an older version and see if it works. I don't worry about auto update as I don't let my play store apps auto update.
EDIT: I recall when I had my Fire 7 working, you could go back a few versions of an app and update it from the play store to most recent and that fixed the issue. Perhaps try that?

Old version - good thinking
Didn't realize I could do that. I grew up coding assembly language on an IBM 50 - left when Smalltalk and C++ were all the rage.
I will stop auto updates and see about getting an older version.
I am kind of amazed that Amazon allows this "side loading" - it isn't really a root - just a sidestep.
Glad it works. The Fire 8 is a marvelous little gadget for the price. It will change EVERYTHING - like FIRE..
And it makes Jeff just a bit richer - like he needs it.
Many thanks.

cannot regress in Fire
carlscheider said:
Didn't realize I could do that. I grew up coding assembly language on an IBM 50 - left when Smalltalk and C++ were all the rage.
I will stop auto updates and see about getting an older version.
.
Click to expand...
Click to collapse
OK, after a bit of a search, I found a repository of older versions.
Is this reliable? https://gmail.en.uptodown.com/android/old
I am on 7.7.2 - I see there is even a newer one.
OK, 7.5.21 lasts a little longer - not much.
7.5.7 nope. 7.4.23 , 6.11.27, nope.
I am going to stop for now. I did find that it seems useful to delete the storage BEFORE uninstalling. It's like the next install picks up on the existing memory and just uses it. If you delete that, it starts fresh. Not that it is getting me anywhere. Thanks. Later.

carlscheider said:
OK, after a bit of a search, I found a repository of older versions.
Is this reliable? https://gmail.en.uptodown.com/android/old
I am on 7.7.2 - I see there is even a newer one.
OK, 7.5.21 lasts a little longer - not much.
7.5.7 nope. 7.4.23 , 6.11.27, nope.
I am going to stop for now. I did find that it seems useful to delete the storage BEFORE uninstalling. It's like the next install picks up on the existing memory and just uses it. If you delete that, it starts fresh. Not that it is getting me anywhere. Thanks. Later.
Click to expand...
Click to collapse
Older versions are also available on APKMirror. Not that it matters as it would seem an underlying dependency is missing. Becomes a cat-and-mouse game. Consider using a different mail app or the Gmail web interface.

Davey126 said:
Older versions are also available on APKMirror. Not that it matters as it would seem an underlying dependency is missing. Becomes a cat-and-mouse game. Consider using a different mail app or the Gmail web interface.
Click to expand...
Click to collapse
Damn shame no one these days has built in POP options anymore. I'd take a totally manual interface over an app any day.
---------- Post added at 10:45 AM ---------- Previous post was at 10:42 AM ----------
carlscheider said:
OK, after a bit of a search, I found a repository of older versions.
Is this reliable? https://gmail.en.uptodown.com/android/old
I am on 7.7.2 - I see there is even a newer one.
OK, 7.5.21 lasts a little longer - not much.
7.5.7 nope. 7.4.23 , 6.11.27, nope.
I am going to stop for now. I did find that it seems useful to delete the storage BEFORE uninstalling. It's like the next install picks up on the existing memory and just uses it. If you delete that, it starts fresh. Not that it is getting me anywhere. Thanks. Later.
Click to expand...
Click to collapse
Google is good about putting updates across all versions. If that is the case with Gmail, no older ones will work.
Gmail used to work. I did have it on the tablet a while back. Though I never reinstalled it after I did my first reset.

Davey126 said:
Look to another mail client (many fine options in Play Store) or use web interface.
Click to expand...
Click to collapse
You were right, there are other email apps that are fine... Thanks.

Would having root allow one to give the gmail app the proper permissions?

Related

Chromecast crashing system ui while casting

I have an lg gpad, and I keep getting the crash of system ui. The tablet is unusable until I do a restart of the device. It happens every time I cast either YouTube or other casting apps and I pull the notification panel down. That starts the crash right away. I've factory restored my Chromecast, factory reset tablet, with fresh install of all apps. I am stumped and getting really annoyed at this issue. Any help in a resolution would be greatly appreciated.
Make sure your apps and Google Play Services are updated. They work hand-in-hand.
bhiga said:
Make sure your apps and Google Play Services are updated. They work hand-in-hand.
Click to expand...
Click to collapse
Updating them did not help. There is a work around, at least for YouTube. Go find the APK for an app called OG YouTube and use the OLD version (4.x)
There's no cue, but you can Chromecast without crashing the entire planet.
I bought the Note Pro with the intent to Chromecast. I feel so ripped off right now, especially since it worked for a little while when I got it. Then an update came down and broke it all. I've read elsewhere that the devs don't seem to give a crap about it, claiming there is no report of the issue even though many many many users are online complaining about it.
hellomiakoda said:
I bought the Note Pro with the intent to Chromecast. I feel so ripped off right now, especially since it worked for a little while when I got it. Then an update came down and broke it all. I've read elsewhere that the devs don't seem to give a crap about it, claiming there is no report of the issue even though many many many users are online complaining about it.
Click to expand...
Click to collapse
That's a bit unfair to the devs, IMO. Chromecast is dependent on so many moving parts that things go haywire when major updates roll out. It's much like when Facebook does back-end updates, unfortunately.
The major moving parts are:
Cast SDK
Chromecast firmware (build number)
Google Play Services
App
Not to mention the individual devices running the Chromecast-enabled app(s).
Until they're all synced up with the correct version "set" things tend to be wacky, and because the Chromecast app whitelist is essentially "live" and I don't think Chromecast has a defined way to know the service or device properties...
tl;dr - give it a few days. Likely it will magically all start working - unless there's something else at fault in the configuration.
Being that it seems the prior version of YouTube works, it may simply be a bug introduced in the update.
Say hello to this bug affecting some LG and Samsung devices:
https://code.google.com/p/android/issues/detail?id=70783
bubbleguuum said:
Say hello to this bug affecting some LG and Samsung devices:
https://code.google.com/p/android/issues/detail?id=70783
Click to expand...
Click to collapse
Thanks Bubble... Argh, I just upgraded to 4.4.2, but this may explain why the recent Netflix update disabled hardware volume control even on 4.3

Google Account Settings issue

** UPDATE **
To be more specific, I'm not having issue with Android Device Manager, I'm having issue with the message "You don't have any devices" in Google Play Store.
I've looked it up in lots of places but seems like no one has a concrete answer.
Any further direction would be appreciated!
******
Hello,
I've installed all of the required apps to run Google Play store and have installed apps without issue. I'm having a couple of issues:
1) When I tap on Google Account Settings, it doesn't load anything, just closes the app
2) When I log in to Google Play on my browser, it says that I have no devices connected to the account, even thought I'm downloading apps just fine with that very same account in Google Play app. I'd like to remotely add and delete apps from my tablets as they are for the kids and I don't always have the tablets by my side to install / delete things.
Please help, thanks!
dymlu said:
Hello,
I've installed all of the required apps to run Google Play store and have installed apps without issue. I'm having a couple of issues:
1) When I tap on Google Account Settings, it doesn't load anything, just closes the app
2) When I log in to Google Play on my browser, it says that I have no devices connected to the account, even thought I'm downloading apps just fine with that very same account in Google Play app. I'd like to remotely add and delete apps from my tablets as they are for the kids and I don't always have the tablets by my side to install / delete things.
Please help, thanks!
Click to expand...
Click to collapse
Sometimes takes a few days for everything to sync up on Google's end.
Davey126 said:
Sometimes takes a few days for everything to sync up on Google's end.
Click to expand...
Click to collapse
It's been like this since I got everything set up 3 weeks ago. It's never recognized that the tablet is associated to the account.
dymlu said:
It's been like this since I got everything set up 3 weeks ago. It's never recognized that the tablet is associated to the account.
Click to expand...
Click to collapse
Another poster (perhaps a few) described a similar situation along with the steps taken to remediate. If I stumble across that I will repost here. As I recall it involved deleting and readding Google account(s) on the device side (reboot between) plus a tweak or two from the web version of Android Device Manager.
Davey126 said:
Another poster (perhaps a few) described a similar situation along with the steps taken to remediate. If I stumble across that I will repost here. As I recall it involved deleting and readding Google account(s) on the device side (reboot between) plus a tweak or two from the web version of Android Device Manager.
Click to expand...
Click to collapse
That would be awesome, thanks a million in advance!
Davey126 said:
Another poster (perhaps a few) described a similar situation along with the steps taken to remediate. If I stumble across that I will repost here. As I recall it involved deleting and readding Google account(s) on the device side (reboot between) plus a tweak or two from the web version of Android Device Manager.
Click to expand...
Click to collapse
dymlu said:
That would be awesome, thanks a million in advance!
Click to expand...
Click to collapse
Problem appears to be widespread with no generic solution. See (one of many similar posts):
http://www.androidpolice.com/2015/0...android-device-manager-googles-working-on-it/
Might be something you just have to live with.
Davey126 said:
Problem appears to be widespread with no generic solution. See (one of many similar posts):
http://www.androidpolice.com/2015/0...android-device-manager-googles-working-on-it/
Might be something you just have to live with.
Click to expand...
Click to collapse
Rats, I want to remotely install and delete apps on my kids tablets, any ideas on remote device management tools for Android tablets?
dymlu said:
Rats, I want to remotely install and delete apps on my kids tablets, any ideas on remote device management tools for Android tablets?
Click to expand...
Click to collapse
While there are quite a few you might want to start with AirDroid. Generally well regarded albeit sometimes a bit schizophrenic. You should be able to accomplish basic app/device management with the free version. Can also look at some of the more focused tools once you decide which features are most important.
Davey126 said:
While there are quite a few you might want to start with AirDroid. Generally well regarded albeit sometimes a bit schizophrenic. You should be able to accomplish basic app/device management with the free version. Can also look at some of the more focused tools once you decide which features are most important.
Click to expand...
Click to collapse
I was looking for something that I can use while I'm at work and the kids are at home?
dymlu said:
I was looking for something that I can use while I'm at work and the kids are at home?
Click to expand...
Click to collapse
Yes - did you look at AirDroid? Claims to have that capability. Also note there are various workarounds (eg: create a second account) for the original issue you reported. None work 100% which is why I didn't elaborate. You are going to have to do a little research to get what you want.
Davey126 said:
Yes - did you look at AirDroid? Claims to have that capability. Also note there are various workarounds (eg: create a second account) for the original issue you reported. None work 100% which is why I didn't elaborate. You are going to have to do a little research to get what you want.
Click to expand...
Click to collapse
AirDroid doesn't allow me access to install apps, just delete I'll have to keep researching, thanks for the advices.
Davey126 said:
Yes - did you look at AirDroid? Claims to have that capability. Also note there are various workarounds (eg: create a second account) for the original issue you reported. None work 100% which is why I didn't elaborate. You are going to have to do a little research to get what you want.
Click to expand...
Click to collapse
To be more specific, I'm not having issue with Android Device Manager, I'm having issue with the message "You don't have any devices" in Google Play Store.
I've looked it up in lots of places but haven't found anything concrete for solution. Is it because I'm using a Fire Tablet and it's not supported on Google Play?
dymlu said:
AirDroid doesn't allow me access to install apps, just delete I'll have to keep researching, thanks for the advices.
Click to expand...
Click to collapse
dymlu said:
To be more specific, I'm not having issue with Android Device Manager, I'm having issue with the message "You don't have any devices" in Google Play Store.
I've looked it up in lots of places but haven't found anything concrete for solution. Is it because I'm using a Fire Tablet and it's not supported on Google Play?
Click to expand...
Click to collapse
Answered the last question in a previous post (below). As for remote install a tool like AirDroid can get the job done but you will need to get creative with the approach. In the end it may not be worth the effort, especially if the target devices are physically accessible albeit with a little inconvenience wrestling it away from the kid.
http://forum.xda-developers.com/amazon-fire/help/google-account-settings-issue-t3441323/post68240076

[GUIDE] Stop Google Play Services Wakelocks (AppMeasurement, net_scheduler, etc.)

Update 09.12.17: The methods below may not fully work on the latest OS versions. There is an ongoing discussion in the last pages so I hope it gets cleared out eventually, sadly I've been busy with my studies and haven't touched my phone since initially making this thread (it's on OOS 4.0.2). I write this just to make sure I don't waste your time accidentally, so please check the latest replies if you're on newer OS versions.
Hello everybody,
*the undermentioned methods and app(s) require root*
I have asked you guys in the AKT thread if you would like to see a small tutorial on how to stop the constant "com.google.android.gms/.measurement.PackageMeasurementService" and "net_scheduler" wakelocks that might or might not be responsible for the device waiting longer than it should before dozing off.
Please keep in mind that this method does work for me, and might or might not work for you, as everybody uses different things/apps so in case you see unwanted behavior, just revert back and sigh that the method has failed you.
I am not responsible for any hardware-/software damage that may occur upon using these settings.
So, now that we've got all the generic stuff out of the way, first few words about why this might bother you:
1) You don't like your device doing stuff you didn't make it do.
2) You want to minimize wakelocks
3) You're here because you just saw the two beforementioned wakelocks and already decided you want to get rid of them.
So, regarding the first one, all I can say is I got the method from this reddit post , which briefly explains which services are doing the waking and what they are. Starting with "At the heart of Firebase is Firebase Analytics, a free and unlimited analytics solution. .." got me raising an eyebrow, as I don't like handling control of my device to other people, without me even knowing.
UPDATE: I have merged the two approaches into just using one app and making the changes on a global level, so you can just do them in like 5 minutes and forget about it, but in case you have problems with disabling package measurement you can also check the hidden text just below for instructions using another app, which was basically "the old way".
So to get rid of the "snooping", as already described in that post, you need to download MyAndroidTools.
Disclaimer: Disabling some services/receivers may "crash" the app. I found it is normal, just go back to where you were and check if you managed to disable the thing you wanted, if yes, then it was successful.
1. Open the app
2. Click on the top left to open the panel, click on Broadcast Receiver.
3. On the menu that opens go to the right column named System. Click search on the top right, type "Play" and choose the Google Play Services option.
4. In the search bar there type at least "ana" and disable the two found results with the names "AnalyticsReceiver" and "AnalyticsSamplerReceiver"
5. Hit x and search again for at least "meas". You will see three results with the names "AppMeasurementInstallReferrerReceiver", "AppMeasurementReceiver" and "PackageMeasurementReceiver*". Disable all three.
****Update 15.02.17*** Apparently this one resets every once in a while, I blame this again on Google's efforts to have their spying on, but anyways. Go to services->system->Google Play Services->search "meas"->disable both "AppMeasurementService" and "MeasurementBrokerService". The third one (PackageMeasurementService) will restart too so don't bother. This should do the trick though.
6. There was discussion about "Campaign Tracking" . I only found it in the same System menu, in Android Pay, by searching at least "cam" you get the result "CampaignTrackingReceiver". Disable it if you feel you want to. I don't use Android Pay and cannot say if it breaks something there, but otherwise have it disabled and haven't noticed any problems so far.
7. Search for Google Play Store in System. In that option, search for at least "app" and disable "AppMeasurementReceiver". Hit x and search for at least "fir", then disable the two results with names "FirebaseInstanceIdInternalReceiver" and "FirebaseInstanceIdReceiver"
8. Done. All the setttings are now global for any sort of app measurements, as far as I know.
This is the "old way" of dealing with app measurement. If you have done the steps above just ignore (hide) this part and continue with disabling net_scheduler below.
So to get rid of the "snooping", as already described in that post, you need to download Root Package Disabler or equivalent alternative.
ATTENTION: As per the last version of the app, I see there might be a bug which reverts some settings when you use the search bar, so please try and find the services by hand in stead of searching, as it is more reliable.
1. Open the app
2. Start with the left-most pane, e.g. "Installed". There you can see all your installed apps
3. Click on the first app on the list, it will display a small menu. Apps that use services will have the bottom-left option named "SERVICES" available, click there. This will take you to the services list that this app uses.
4. Click on the searching icon on the top-right in order to filter the services we need disabling.
5. Write at least "appm" . If the AppMeasurementService is used by this app, it will now be displayed.
6. Tick that off (the switch will turn gray)
7. Hit x, and search again for at least "fireb". This will display all services that use the Firebase SDK. You may also check under the name of the service and see the word is contained in the "executable name", so it might not always have "an official" name that states Firebase, but still use one of their "executables" (sorry for lack of detail)
7.1 Check for any other services that have "analytics" in their description, although I haven't checked if this stops something useful, but I doubt it.
8. When you're done with the current app, it will no longer call these services and cause wakelocks as long as the services remain stopped. To my experience the settings stay after reboot, it's just the above mentioned bug you have to keep in mind since it happened to me now while making the guide, and I know it came with the latest update.
9. Go back to the installed pane and maybe tick on the star next to the app in question. It will be added to the "favourite" list where you can have all those apps and don't bother to search them again if needed.
10. Repeat from step 1 for the next app and go through all your apps. If not you will still get calls to this service from the apps that still have these services on. Also a reminder here, you have to remember and check every new app you install, as most apps do have the service enabled.
11. After you're done with all apps in "Installed", check out bloatware (I think I haven't found anything there, but it's worth checking).
12. "System" apps that I know have some of those services: Calendar, (probably) Chrome (I have that disabled so dunno), Drive, Duo, Gboard, Google Play Services, Google Play Store, Google VR Services.
Here are two pictures how an app's services list looks like, and one with some of the services disabled:
all services on
some services off
After doing these steps, you should charge your battery to 90% to reset the battery statistics and you should see that the "com.google.android.gms/.measurement.PackageMeasurementService" wakelock no longer occurs (or stays really, really low, and not thousands like before). If you still have it after all this, then you probably have an app you haven't disabled the services for.
The second approach will get rid of the "net_scheduler" wakelock. Thanks to @denon480 for the idea, it's post #34 in this thread It involves installing (again) MyAndroidTools or equivalent alternative.
1. Open the app
2. Click on the top left corner to open the menu panel.
3. Click on Broadcast Receiver
4. Navigate to the System pane
5. Click on search on the top right. Search for Google Play Services. Click on them when they show up
6. In the search top right, write at least "sche" and you will see the two receivers responsible for the "net_scheduler" wakelock, "SchedulerInternalReceiver" and "SchedulerReceiver" . Here's a picture how it looks
7. Switch the first one off. The app will quit, don't worry.
8. Go back to where you were (steps 1 to 6) . You will see that you indeed managed to swtich that receiver off.
9. Switch the second one off. The app will quit, again no worries.
10. Check if you managed to switch the second one as well. After that you're done!
I hope I could help you guys out. I know there is nothing fancy in these methods but felt a thread might be useful as I saw a good number of requests when I mentioned it in the AKT thread.
Also sorry for misleading the guys I already told it was going to be a short guide, I honestly thought it would take way less words than it did. But I think it is for the better.
Have fun.
* Reserved *
Going through this guide, I was able to get the services disabled through root package disabler, bit my android tools kept force closing for some reason.
*edit* uninstalled, rebooted, reinstalled, and was able to get the app to stay open, and got them disabled. I'm curious to see what my wake locks are going to look like tomorrow. This is pretty much the nougat answer to amplify, huh? =)
MeggaMortY said:
* Reserved *
Click to expand...
Click to collapse
I think Everything is fine or?
tzbigworm said:
Going through this guide, I was able to get the services disabled through root package disabler, bit my android tools kept force closing for some reason.
*edit* uninstalled, rebooted, reinstalled, and was able to get the app to stay open, and got them disabled. I'm curious to see what my wake locks are going to look like tomorrow. This is pretty much the nougat answer to amplify, huh? =)
Click to expand...
Click to collapse
Hope it gets rid of those for you too. If I remember correctly I noticed the problem since Nougat, but then again I've been on Android since only a few months, coming from a big pause. Last time I was around we were rocking the HTC HD2 and had to deal with very different problems.
1+3_FA said:
I think Everything is fine or?
Click to expand...
Click to collapse
Yup looks great.
MeggaMortY said:
Hope it gets rid of those for you too. If I remember correctly I noticed the problem since Nougat, but then again I've been on Android since only a few months, coming from a big pause. Last time I was around we were rocking the HTC HD2 and had to deal with very different problems.
Click to expand...
Click to collapse
Crazy how much of a beast that phone was. People forget it's actually a windows phone, Android was put on it so much lol!
Thanks for the tips. Works great!
Thank you for your awesome work!
I have two more questions:
1. What about CampaignTrackingService? Could we disable this one as well?
2. In MyAndroidTools under Broadcast Receiver there are lots of receivers like AppMeasurementReceiver or FirebaseInstanceIdReceiver. They also need to be disabled or disabling the corresponding service is sufficient?
Thank you very much
youknownothing said:
Thank you for your awesome work!
I have two more questions:
1. What about CampaignTrackingService? Could we disable this one as well?
2. In MyAndroidTools under Broadcast Receiver there are lots of receivers like AppMeasurementReceiver or FirebaseInstanceIdReceiver. They also need to be disabled or disabling the corresponding service is sufficient?
Thank you very much
Click to expand...
Click to collapse
1. I initally disabled that in a few apps and didn't have problems System-wide or with the apps. So you can give it a go and in case of apps not functioning you can revert those back.
2. No for now it's okay to just use the Package Disabler for that. Like I said both apps have similiar functionality, there's probably a way to find the right service/receiver and disable it globally from MyAndroidTools, then we won't need the Package Disabler. But since it did work for me and I don't install new apps more than like once a week, I just didn't bother figuring it out. I can only say that disabling certain services/activities in MyAndroidTools can brake functionality or even bootloop your device, so be very careful in case you wanna find out if it's possible.
MeggaMortY said:
1. I initally disabled that in a few apps and didn't have problems System-wide or with the apps. So you can give it a go and in case of apps not functioning you can revert those back.
2. No for now it's okay to just use the Package Disabler for that. Like I said both apps have similiar functionality, there's probably a way to find the right service/receiver and disable it globally from MyAndroidTools, then we won't need the Package Disabler. But since it did work for me and I don't install new apps more than like once a week, I just didn't bother figuring it out. I can only say that disabling certain services/activities in MyAndroidTools can brake functionality or even bootloop your device, so be very careful in case you wanna find out if it's possible.
Click to expand...
Click to collapse
Thank you for your quick response. I'll give it a try, if anything goes wrong I'll let you know.
Is there any difference between Package Disabler and Disable Service app? I've tried the former, but it was really buggy. Scrolling was so glitchy and with lots of stutters that I've accidentally disabled few services. So I've used Disable Service with success. Now I only wonder whether both apps have the same functionality. Do you happen to know that?
Thanks in advance
youknownothing said:
Thank you for your quick response. I'll give it a try, if anything goes wrong I'll let you know.
Is there any difference between Package Disabler and Disable Service app? I've tried the former, but it was really buggy. Scrolling was so glitchy and with lots of stutters that I've accidentally disabled few services. So I've used Disable Service with success. Now I only wonder whether both apps have the same functionality. Do you happen to know that?
Thanks in advance
Click to expand...
Click to collapse
Assuming you're disabling services, which we are lol (should've been more obvious for me too I guess), I'd say you should be fine, and even say maybe the same goes for just using MyAndroidTools, just scroll through the Service menu in Table Third-Party and you'll see the same settings you applied with the other app/Package Disabler. I guess I was lazy to realize that since I liked I can favourite the apps I need to keep an eye on in the Package Disabler.
So all in all you should be okay, but even better you may try and just use MyAndroidTools for both. I have some exams coming so I won't be able to test those things but will make sure to update the tutorial if indeed that turns out to be right (for the app you suggested or even just MyAndroidTools).
Give a shout in case you find out something more. And thanks for the info
Followed the guide, thanks for this like said before kind of amplify for nougat. But as I was disabling net.schedule I noticed "my android tool" can do the fire base and app activity. Under service activity and press <...>
I suppose that this two methods doesn't compromise any function of the device right? For example loosing notifications or similar
Sent from my OnePlus 3
Mr.Jay said:
I suppose that this two methods doesn't compromise any function of the device right? For example loosing notifications or similar
Sent from my OnePlus 3
Click to expand...
Click to collapse
Like mentioned, it works fine for me, and probably depends on personal usage. I don't use Google Pay for example, and Chrome, and Google Music.... but besides those I haven't had problems anyway.
Disabled everything that is said to do in this thread and it worked great while I was at home while on wifi. I had drain of .5% an hour at times. However today while at work and on LTE, drain went up to 2.6% an hour, plus wakelocks from play services was waking up the device on average over 3 times a minute. When I looked into it further there was one service under play services where all the alarms were coming from. I do have a screenshot of this. Anyone have any insight to this? For the record, I do keep location off on my device.
Edit: I wonder f it comes from moving around a lot, as I'm always on the move as I manage a restaurant. Its not really a major drain, but still makes me wonder.
NJGSII said:
Disabled everything that is said to do in this thread and it worked great while I was at home while on wifi. I had drain of .5% an hour at times. However today while at work and on LTE, drain went up to 2.6% an hour, plus wakelocks from play services was waking up the device on average over 3 times a minute. When I looked into it further there was one service under play services where all the alarms were coming from. I do have a screenshot of this. Anyone have any insight to this? For the record, I do keep location off on my device.
Edit: I wonder f it comes from moving around a lot, as I'm always on the move as I manage a restaurant. Its not really a major drain, but still makes me wonder.
Click to expand...
Click to collapse
Have you disabled location history in the Google App? The problem is this guide fixes only one concrete aspect of the whole "Google stalking experience" shenanigans. Please check for the thing I mentioned and also in Settings -> Backup & Reset, make sure Back up my data is off if you haven't logged in an account and intend to use that - these two things were also draining battery for me when I was on the go as far as I can remember.
LMcR92 said:
Followed the guide, thanks for this like said before kind of amplify for nougat. But as I was disabling net.schedule I noticed "my android tool" can do the fire base and app activity. Under service activity and press <...>
Click to expand...
Click to collapse
I did some checking on that list and am currently testing a way to only use MyAndroidTools for the whole aproach. If it turns out to be working the whole guide would get reduced to like 10 clicks, since the settings are global. I'll post more info after a day or so to make sure it is working, but as for now I see promising results.
Anyone used Franco's Servicely app to do this?
Up, I have updated the guide to just using MyAndroidTools and disabling the receivers on a global scale. So now you just have to do it once and (hopefully) forget about it.
MeggaMortY said:
Up, I have updated the guide to just using MyAndroidTools and disabling the receivers on a global scale. So now you just have to do it once and (hopefully) forget about it.
Click to expand...
Click to collapse
Will Doing like #1 post notifications from Gmail?
techusthad said:
Will Doing like #1 post notifications from Gmail?
Click to expand...
Click to collapse
Don't know what you mean by #1 - disabling the AppMeasurement stuff, e.g. first set of instructions? I haven't had problems with Gmail and I use it with two accounts on there.

R.I.P. Yalp Store

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!

[SOLVED][NST/G] R.I.P. Amazon Kindle app (NOT!)

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.

Categories

Resources