developer options are not available for this user - Essential Phone Questions & Answers

HI,
I just OTA updated to Android Q Beta 3 on my PH-1 (rooted). However, I'm experiencing a very interesting problem. When I go to developer options. Instead of a long list of options, I get a message of "developer options not available for this user". Moreover, the notifications pull down is no longer working anymore.
I have done tons of research and did try the following solutions
1) Using the widgets in Nova Launcher to create activities of "Essential SetupWizard Welcome Screen"
2) adb shell am start -n com.google.android.setupwizard/.SetupWizardTestActivity
3) using terminal to create new user
Unfortunately, none of the solutions works for me....would anyone able to give me a hand please?????

Related

[Q] Help enabling Multi-User on latest AOKP

First I love AOKP, and it has defined android for me for a while. I need some help getting multi-user support on the aokp nightly. Apologies, if this is against any rules.
I am running the latest 10/15 nightly, although a majority of my attempts were done on the 10/10 nightly.
My setup post freset:
twrp to install nightly, gapps 08/13, photosphere, lte zip.
boot rom, no google sign in
adb push titanium backup, restore android device id, reboot, restore all apps with data
restore nova settings and lte apn settings
Click to expand...
Click to collapse
So this is where I'm starting from.
ATTEMPT 1
I use terminal for the following
adb shell
su
pm get-max-users (should show 1)
setprop fw.max_users 8
pm create-user Guest
Click to expand...
Click to collapse
This brings up the users tab in settings where I can see the Guest user I just created. I go to set it up and it soft reboots to the welcome to android setup screen. Great. but every gapps start crashing. basically fail fail fail. no keyboard means I cant set up the profile. Even then there's no way to get to terminal to softboot back to my original. so from here I nandroid restore in twrp.
ATTEMPT 2
My next option was to start from a clean install and download/install the xposed framework. That allowed me to use the Modaco Toolkit module that list the following as a feature.
Google Nexus (all): Enable multi-user support if unsupported on stock (e.g. Nexus 4).
Click to expand...
Click to collapse
This actually worked well. I saw the users option in settings, I was able to create different users, and the phone soft rebooted to set up the new user. Great, but still every gapps stoppes working as soon as the welcome screen pops up. Although with this option I can long press the power button and go back to my original user.
So can anyone provide some insight as to how to install the gapps in the emulated /1 folder for a second user?
Since multiuser on phone is a Microsoft Nokia patent, Google can't enable it by default.
I don't know how to edit the buildprop to do it, but I use this app to enable it: https://play.google.com/store/apps/details?id=org.sferadev.multipleuser
The problem is your DPI have to be below a certain number for the multiuser switching to show up on your lockscreen, 192 or something. But then everything on the screen looks very small so its not worth it anymore unless you have a 6" device maybe.
I know that Paranoid Android have multiuser feature so it's the only solution I know of. I'm just not willing to let go of AOKP either.

[Q] Tasker

Hi,
I've got a problem with the app tasker.
I am rooted without using SuperSU over cm12.1.
Tasker won't detect my root access.
What should I do?
Secure setting plugin is installed...
I've tried to manage the mobile data via secure settings plugin but it doesn't do the trick neither...
any suggestions?
Go into Settings > About and tap the build number several times, until you get a notification saying "You are now a developer!"
Then go back to the main settings screen and look for Developer options. Go into developer options and look for Root acces. Tap on that and set it to Apps. Or set it to apps and adb. Done. Otherwise just install SuperSU from the playstore
GDReaper said:
Go into Settings > About and tap the build number several times, until you get a notification saying "You are now a developer!"
Then go back to the main settings screen and look for Developer options. Go into developer options and look for Root acces. Tap on that and set it to Apps. Or set it to apps and adb. Done. Otherwise just install SuperSU from the playstore
Click to expand...
Click to collapse
I've already enabled root access via CM.
That wasn't the problem.
I found a solution if anyone stumbles on that thread:
http://forum.xda-developers.com/showpost.php?p=60300161&postcount=2371

[FireOS 5.x + ROOT] Quickly switch to Amazon UI and back:

Update2: Updated and tested under Lollipop (Sept 2015 FireOS 5.0.1 version for Fire HD 7 2014 [5.2.2u2], and should work with Fire 7 2015)
Given that a Fire tablet with Amazon experience is a terrible thing to waste, these are scripts to switch from and to Amazon launcher both under FireOS 4.5.x and Lollipop. Along with the launcher this disables a lot of battery sucking Amazon apps (the enabling script revives all of this goodness back).
The key stuff in scripts is the launcher block/unblock. I block other apps too because some of them seem to wake up a lot ("Wakelock detector" tells me this), so why not make them less obnoxious when you are not running Amazon experience ...
Naturally, you do need ROOT (how to root FireOS is a subject of other guides).
I assume you have Nova Launcher or free Google Now Launcher (on Lollipop installed as a system app in order to have Widgets working). If your Amazon launcher apk file is renamed, rename it back (verify that you do have the proper /system/priv-app/com.amazon.firelauncher/com.amazon.firelauncher.apk ). Do make sure that you have an alternative launcher (besides the stock Amazon one !!!). Also, make sure that your adb is authorized in order to enable you to unblock the Amazon launcher in case you get the permanent Fire logo.
Go ahead install Gscript ( https://bitbucket.org/Equidamoid/gscript/downloads ). Copy either fire_on_off.zip (for FireOS 4.5.x), or fire_on_off_511b.zip (for FireOS 5.x - Lollipop) to /sdcard/gscript, and unzip scripts right in there. In "Gscript", tap the 3 dots at the bottom right corner, tap "Add script", tap "Load File", tap root required, first choose the disabling script, then repeat for the enabling script. All set.
In Nova, long tap on an empty area, it'll offer to create Shortcut. Choose Gscript/"Kindle block". Repeat for "Kindle unblock".
Then in "Nova", tap "Kindle unblock". It'll get you into Kindle Launcher, at which point you have 100% Amazon experience. Once you do your thing, and want to go back, launch/switch to "Nova", and tap "Kindle block". At this point you are back to more stock like Android.
To give proper credit, this approach was proposed by DoLooper ( http://forum.xda-developers.com/showpost.php?p=61089153&postcount=29 , and some good suggestions in a reply to this post) .
bibikalka said:
So why not switch quickly to and away from stock Amazon UI ?
Click to expand...
Click to collapse
Thanks for the post and the scripts! The shortcut makes it so easy to switch between launchers, and blocking the other packages is a great idea.
In case it's not obvious to casual reader, this lets you run any adb shell command(s) from a homescreen shortcut (and scripts that do other things, too, of course). Here are a few related tips:
Launcher: This works with any launcher that allows shortcuts on the homescreen
Gscript: I suggest using this Gscript app instead of getting it from play store. Play store version is older and less stable, and I don't think it closes after running the shortcut.
Adding the scripts (alternate method): Create a folder named "gscript" in sdcard and put bibikalka's scripts in there. Then in Gscript app, tap (3-dot) menu button, "Add script," "Load file" and the scripts will be listed.
Edit scripts from Gscript: Long press on the script name and choose Edit.
People using Freetime should edit the scripts and delete lines for amazon.kindle.kso and Tahoe. Blocking these causes bootloop.
I'm on 4.5.3 root with Google play, does it Worth upgrading ?
This works with any Fire OS; don't need 4.5.4, just have to be rooted. If you use the Amazon launcher occasionally, try this.
DoLooper said:
This works with any Fire OS; don't need 4.5.4, just have to be rooted. If you use the Amazon launcher occasionally, try this.
Click to expand...
Click to collapse
Has anyone made a version of this for Lollipop ???
bibikalka said:
Has anyone made a version of this for Lollipop ???
Click to expand...
Click to collapse
Not I. (Kinda puts the lie to that old post, eh?)
Commands for developers preview:
pm disable com.android.launcher
pm enable com.android.launcher
am start -n com.android.launcher/com.android.launcher2.Launcher
5.2.2u2 enable/disable = pm disable com.amazon.firelauncher
I can guess start is:
am start -n com.amazon.firelauncher/com.amazon.firelauncher.Launcher
. . . but I can't test cuz I don't have a custom launcher right now. Maybe someone else can test this ??? If not, I'll figure it out in next few days. (You're still on 4.5.5?!)
DoLooper said:
Not I. (Kinda puts the lie to that old post, eh?)
Commands for developers preview:
pm disable com.android.launcher
pm enable com.android.launcher
am start -n com.android.launcher/com.android.launcher2.Launcher
5.2.2u2 enable/disable = pm disable com.amazon.firelauncher
I can guess start is:
am start -n com.amazon.firelauncher/com.amazon.firelauncher.Launcher
. . . but I can't test cuz I don't have a custom launcher right now. Maybe someone else can test this ??? If not, I'll figure it out in next few days. (You're still on 4.5.5?!)
Click to expand...
Click to collapse
OK, thanks! I just got a 5th gen Fire 7 for a present, and will play with it to see how this blocking works on Lollipop.
bibikalka said:
OK, thanks! I just got a 5th gen Fire 7 for a present, and will play with it to see how this blocking works on Lollipop.
Click to expand...
Click to collapse
It works "interestingly." Played with it today to update the block sys app post. Start command:
am start -n com.amazon.firelauncher/.Launcher
Couple interesting (to me) things:
Disable:
- If you only have one alternate launcher, disabling firelauncher immediately takes you to alternate. (But maybe it did this before. I've always had multi alt launchers.)
Enable:
- You stay on alt launcher, but tapping Home icon takes you to Fire launcher (even with multi alt launchers installed).
- Enable and switch = same as before: run enable and then run start
Updated and tested for Lollipop. Thanks to DoLooper for the suggestions!
bibikalka said:
Updated and tested for Lollipop. Thanks to DoLooper for the suggestions!
Click to expand...
Click to collapse
I want to give this a try on my Fire HD7 and have only been using the Amazon launcher to this point. What is the preferred Android launcher most of you use and do you go with the free launcher or purchase a particular one? I see a couple varieties of Nova at the Play Store and have to assume the purchased one does not have ads, so thought I would ask your preferences before giving it a try. Thanks in advance for any advice you provide...
I enjoy the Nova Prime(paid app) no ads lots to customize
phfoneman said:
I want to give this a try on my Fire HD7 and have only been using the Amazon launcher to this point. What is the preferred Android launcher most of you use and do you go with the free launcher or purchase a particular one? I see a couple varieties of Nova at the Play Store and have to assume the purchased one does not have ads, so thought I would ask your preferences before giving it a try. Thanks in advance for any advice you provide...
Click to expand...
Click to collapse
What don't you try the free Google Now launcher ? Once you see how this works, perhaps you'll try Nova.
In case you overdo launcher switching and end up with no working launcher, just remember you can always save the day with these commands in adb (as long as keep the amazon launcher intact, and just block it via "pm disable" as the script above does it):
pm enable com.amazon.firelauncher
am start -n com.amazon.firelauncher/com.amazon.firelauncher.Launcher
Hi all, I have run kindle_block_5_1.sh and then reboot device. I am stack with "Fire" logo at the boot. I have access to ADB, but could not receive root access in adb shell. Can anyone advice me? How can I revert changes after that script back?
Thanks in advance
Yevgen.A said:
Hi all, I have run kindle_block_5_1.sh and then reboot device. I am stack with "Fire" logo at the boot. I have access to ADB, but could not receive root access in adb shell. Can anyone advice me? How can I revert changes after that script back?
Thanks in advance
Click to expand...
Click to collapse
No need to answer, easily fixed my problem by factory reset in recovery
Yevgen.A said:
Hi all, I have run kindle_block_5_1.sh and then reboot device. I am stack with "Fire" logo at the boot. I have access to ADB, but could not receive root access in adb shell. Can anyone advice me? How can I revert changes after that script back?
Thanks in advance
Click to expand...
Click to collapse
Yevgen.A said:
No need to answer, easily fixed my problem by factory reset in recovery
Click to expand...
Click to collapse
Rookie mistake No launcher present, no adb authorized ! But I've added some messages to the original post to mention this issue.
I can't get Nova to create a Gscript shortcut at all. I press the Gscript disable option and it dumps me back to the Amazon launcher.

Disable OTA - Keep SDCard Write Access and Use a Different Launcher *READ BEFORE BOOT

Since root has been obtained and an alternative launcher can be installed, as has been mentioned there is really no need to stay on 5.0.0 anymore. I would recommend updating to 5.0.1. However, this procedure can still be applied to 5.0.1 and hopefully it'll prevent any future updates. (As of writing it 5.0.1 is the latest).
The steps are basically as follows:
Enable ADB by going to Settings> Device Options. Keep tapping on the Serial Number field until the Developer options field appears.
Under Developer options Enable ADB
Hook the Fire up to your computer and do the following commands:
adb shell pm hide com.amazon.otaverifier
adb shell pm hide com.amazon.device.software.ota
adb shell pm hide com.amazon.settings.systemupdates
I don't know which of three is the magic one, But you can not longer go to device options > system update. It also never appears to pull down the update in the background.
Rivethread23 - good work and many thanks for this
I know that you have the original Fire 7 with no system update but I wanted to see if any of your commands will work on 5.01. My device is on 5.01 has been in aeroplane mode since purchase, I have been using OTG Ethernet for connectivity and I have not signed into Amazon. Google Play is installed - basically a standalone device on 5.01 with no association with Amazon.
After running the commands and the ADB shell gave a [True State] after each command. Rebooted the device:
System Updates now gives the following error message: [The requested action is not permitted. Check Parental controls settings and try again]. As my device is not associated with Amazon parental controls have not been configured - so I browsed to a few proxy sites and such to confirm no filtering on web browsing etc
I've tried various launchers from Play store and every time the default Fire Launcher kicks back in again.
SD Card issue is still there.
When you tried the System Update button did you get the same error message as me? If so, I wonder if the Adb Shell command to disable OTA works on 5.01 as well?
Update 1: [adb shell pm hide com.amazon.firelauncher] disables the default Amazon launcher. I picked another launcher at random from Google Play. Halo installed and it worked with the default launcher hidden, however using the minimise middle button on the device forces the Parental Control Popup to appear.
So it is possible to hide the default launcher on 5.01 using ADB but it is causing issues. We need a better work around.
Unfortunately this only blocks the update from occurring. I ran into another issue on the 5.0.0 tablet in that I can't get Google play store working. It just says cannot connect. So I don't know if one of the above things broke it. It was getting late so I went to bed. I'll keep plugging at it and see what I can do.
I might finally take both of mine out of the box today, can more people confirm this is working? @Rivethread23, did you get the play store sorted out?
Couldn't wait, dove in. On an out-of-box Fire, running 5.0.0, these do in-fact keep the OTA updates from firing. I have been online, installing apps and customizing the tablet for over an hour with many reboots, no prompts or attempts of an update.
With this, and ads disabled, and the play store turned on we have a usable tablet!
F-Droid works as well, just sideload their APK to get access to lots of software:
https://f-droid.org/repo/org.fdroid.fdroid_96150.apk
Still stuck on Play Store in 5.0.0 *not working* for now.....same problem as OP
I can confirm that the Google Play Services, Login Services, and Framework are (at least partly) working, even though the Play Store is not. I sideloaded Gmail, and it automatically had my info, and downloaded my email.
Wait, I'm confused. In 1 post you say play store is on and working, then you're saying it's not...
Aside from the play store, it sounds like everything else is working fine! Is that correct. I'm asking because I'm thinking about buying a 2nd one of these, only if I can have it working 100% the way I have it now with my tablet, just with the ability to use a different launcher.
With the original 5.0.0 firmware, if you prevented the OTA update to 5.0.1:
+Can change launcher
+Can write to SD from apps
-Can't get Play Store to work (so far, but can manually side-load GApps (Gmail, Hangouts, etc))
In the other thread, people that have gone to 5.0.1:
-Locked to amazon Launcher when using HOME button
-Manual SD writing is disabled
+Google Play Store can be installed and 90% of the GApps work
--------
The key to take away is that if you get another one, and you do the fix in this thread to prevent OTA updates, you can simply wait til everyone gets things fixed and figured out. You can safely use it and not worry about getting pushed to a firmware that might be even more locked down.
On the other hand, if you're not worried about OTA updates breaking stuff, and want a working store, go to 5.0.1 and follow SD_Shadow's instructions in his thread on that subject.
Hopefully root comes soon and we can fix all these problems properly, but until then it's kinda hit and miss depending on what version you got.
Hope that helps.
Thanks Tufkal was going to post something along those lines but you beat me to it.
Essentially you can prevent updates from further locking down the tablet. Who knows what future updates bring? I'll wait and update as thing warrant.
I have two one on 5.0.0 and another on 5.0.1. While I like being able to use the launcher of my choosing on 5.0.0, the working google store and updated amazon store and apps have me using the 5.0.1 one. I am keeping the other on 5.0.0 until development starts then I'll try my hand at making a ROM.
Your device that is on 5.0.0 Firmware have you signed into Amazon and associated your device? Or is it standalone like mine?
Was on Amazon for a day. Factory reset it and am using it sans Amazon. Mostly using the 5.0.1 one myself.
Yep same here. 5.01 with no amazon sign in.
I've been playing around with the launcher again. Tried changing the hardcoded buttons and also with ADB Shell am force-stop pm disable on com.amazon.firelauncher to stop dependent services, ie hard buttons. All to no avail.
root definitely needed for this
I figured out a way to access some hidden functions within the OS last night. Seeing where this leads after work today Apparently I can cast the screen and access the home function disabled in 5.0.1. Problem is the home function doesn't override the hard coding.
Most interesting is something called Prod and Devo Switch that give "Access Denied" when I try to activate it. Hmmmm........
Here's what I have discovered. It's easier done on 5.0.0 but can be done on 5.0.1. You'll need another launcher like Nova installed. Installed "Anycut" from the google store. It'll let you put a shortcut on the desktop for any "activity". There are alot of items there not normally accessible. You can cast to a Chromcast for example (it works). The reason you need another launcher is the Amazon launcher doesn't support shortcuts I guess as they don't appear. They appear on Nova's desktop when created.
Most interesting is a shortcut called "Prod and Devo Switch" which if you look at the info refers to the "Amazon Device Settings" app.. ( com.amazon.device.settings?). It's separate from the user settings. If you try to access it it will say "Access Denied" on 5.0.1. Or "Permission denied" on 5.0.0. Makes me wonder if what needs to happen the app needs some additional permissions to be run. I was looking through the list of permissions via ADB and there are a number of permission groups that are android.xxxxx. However there are only a few permission groups that are amazon.xxxxx one of which is amazon.permission-group.settings. Listing the settings in the group shows a large list. Maybe using ADB pm grant com.amazon.device.settings the correct permissions could unlock this? Thoughts?
Here's what I got from a logcat when I click on the shortcut in novalauncher:
I/ActivityManager( 454): START u0 {act=android.intent.action.VIEW flg=0x1000000
0 cmp=com.amazon.device.settings/.DevoProdConfigActivity bnds=[300,168][400,310]
} from uid 10017 on display 0
W/ActivityManager( 454): Permission Denial: starting Intent { act=android.inten
t.action.VIEW flg=0x10000000 cmp=com.amazon.device.settings/.DevoProdConfigActiv
ity bnds=[300,168][400,310] } from ProcessRecord{9460965 1138:com.teslacoilsw.la
uncher/u0a17} (pid=1138, uid=10017) requires com.amazon.dcp.permission.DISPLAY_D
EBUG_UI
E/Launcher( 1138): Launcher does not have the permission to launch Intent { act=
android.intent.action.VIEW flg=0x10000000 cmp=com.amazon.device.settings/.DevoPr
odConfigActivity bnds=[300,168][400,310] }. Make sure to create a MAIN intent-fi
lter for the corresponding activity or use the exported attribute for this activ
ity. tag=ShortcutInfo(title=Prod and Devo Switch intent=#Intent;launchFlags=0x10
000000;component=com.amazon.device.settings/.DevoProdConfigActivity;sourceBounds
=300%20168%20400%20310;end id=15 type=Shortcut container=-100 screen=1 rank=-1 c
ellX=3.0 cellY=1.0 spanX=1.0 spanY=1.0 dropPos=null user=UserHandle{0} modelGene
ration=-1) intent=Intent { act=android.intent.action.VIEW flg=0x10000000 cmp=com
.amazon.device.settings/.DevoProdConfigActivity bnds=[300,168][400,310] }
E/Launcher( 1138): java.lang.SecurityException: Permission Denial: starting Inte
nt { act=android.intent.action.VIEW flg=0x10000000 cmp=com.amazon.device.setting
s/.DevoProdConfigActivity bnds=[300,168][400,310] } from ProcessRecord{9460965 1
138:com.teslacoilsw.launcher/u0a17} (pid=1138, uid=10017) requires com.amazon.dc
p.permission.DISPLAY_DEBUG_UI
Tried granting that specific permission to Nova launcher or the Fire launcher but both do the same thing:
com.amazon.firelauncher com.amazon.dcp.permission.DISPLAY_DEBUG_UI <
Operation not allowed: java.lang.SecurityException: Package com.amazon.firelaunc
her has not requested permission com.amazon.dcp.permission.DISPLAY_DEBUG_UI
Maybe someone with more knowledge than I create a program with that permission that calls the intent in question?
Again good work on this
I picked up another new device yesterday morning. OTA updates disabled, Fire OS 5.0, no association to Amazon and connectivity via WiFi. Just like you I got Gmail, YouTube and other Google associated apps to work with the exception of the Play store. It finally let me sign in but comes up every time with the [Connection Retry] error.
I followed your instructions and installed AnyCut - and I have been playing around as I thought it might be possible by using shortcuts to load my Google account onto the device.
Shortcut [Add an account] - and the "Couldn't sign in - google server error" came back so not working for now.
Shortcut [Testing] - allows us to pull up more info on the Fire 7 with the 4 below options
Tablet Information - not working
Battery Information - working
Usage Statistics - working
WiFi Information - working
Shortcut [IP Settings] - gives us advanced WiFi options
A lot of the options try to load or there is a visible presence of starting to load and you can clearly see the device stopping them from loading. Basically we are trying to load Android Apps that are locked down by Fire OS which sits on top of Android.
Other apps with Permission Denied
[Log Manager]
[Crash Manager]
[Metrics Debug UI]
Looks like Amazon do not want us to have access to their inbuilt log files on their device
As I do not have access to Google store I have been using F-Droid for my apps. I have installed APK Extractor and it lists all the current APK's on the Fire 7. What is interesting about this is that there are APK's that where not findable using [AnyCut] but show up in APK Extractor.
Will update more in a bit
Here's an interesting note..... I'm on 5.0.0 and trying to get the Play Store working (I believe that 5.0.0 w/ Play Store is a better avenue to attack than trying to fix the launcher in 5.0.1)
For testing reasons I'm on an older version of the Play Store where the search icon is visible.
On the play store screen where it says no connection with the retry button, I hit the search icon and start typing "clas" It autofilled in clash of clans. Then i did "hang" and I see hangouts dialer. The play store app is communicating it would seem.....
tufkal said:
Here's an interesting note..... I'm on 5.0.0 and trying to get the Play Store working (I believe that 5.0.0 w/ Play Store is a better avenue to attack than trying to fix the launcher in 5.0.1)
For testing reasons I'm on an older version of the Play Store where the search icon is visible.
On the play store screen where it says no connection with the retry button, I hit the search icon and start typing "clas" It autofilled in clash of clans. Then i did "hang" and I see hangouts dialer. The play store app is communicating it would seem.....
Click to expand...
Click to collapse
What is the version of your Play APK please? As I have the latest version with no search - but still on 5.0.0
k3ll0gs said:
What is the version of your Play APK please? As I have the latest version with no search - but still on 5.0.0
Click to expand...
Click to collapse
I'm trying all kinds, the one i was using for that test I got here:
https://onedrive.live.com/redir?res...4&authkey=!AIVXLFXAOWDeM0Q&ithint=folder,.apk
I'm with you I tried some work arounds on the 5.0.1 tablet but if we can get the play store working on 5.0.0 it seems to offer more opportunities.
Yep same here - it makes more sense to get Play store to work.
I think I might know what the issue is causing and I believe it is down to the Google Service Framework (GSF) on 5.0 not installing correctly and causing the sync issue when trying to connect. I installed [Device ID] app on 5.0 and there is no serial listed for GSF at all - on my 5.1 tablet GSF would load up on the screen and you could view settings but on 5.0 it does not.
When trying to open the Google Play some I found the following error in Logcat [.onClick: b/5160617: Reinitialize account] this relates to the GSF serial not being present. Logs also show permissions and api errors as well. The only
Looking into a GSF workaround if possible. It might be on the wrong track but I am going to see what else I can find out.
I thought I had found a back door into Google signin. Using an App calling [Applications Info] which I used to pull up the GoogleServiceFframework apk. From there I started to play around with the launch options for the applicable services.
Selecting launch on [Legal Services] takes you to Google Sign In - keyboard was not working for this so I had to adb shell input text of my gmail & password. Unfortunately the same old Google error was appearing even after I cleared the cache and re-installed Gapps.
The last screengrab shows that the System Updates on installed Google Service Framework is corrupt and not working properly. I have also launched other Gapps dependent activities from the services in [App Info] and again they either fail to load of abundance of errors. So installation issues for all of the Gapps in one way or another on Fire 5.0
Obviously there is a difference between the 5.0 Rom + 5.01 Rom that is stopping Gapps from working. Due to the amount of errors in Logcat and in Application Info and dependent services not working. My gut is saying that when we have root on 5.0 we have a better chance of getting Gapps working as we will have the ability to play around with not only System files but System commands too.
If anyone has any ideas or what else we could try please chip in.
rivethead23 said:
Hook the Fire up to your computer and do the following commands:
adb shell pm hide com.amazon.otaverifier
adb shell pm hide com.amazon.device.software.ota
adb shell pm hide com.amazon.settings.systemupdates
Click to expand...
Click to collapse
running those commands will prevent any future update?
Right now I have 5.0.1 and I'm happy with it, I would like to avoid any bad surprises.
redst said:
running those commands will prevent any future update?
Right now I have 5.0.1 and I'm happy with it, I would like to avoid any bad surprises.
Click to expand...
Click to collapse
yes updates would be blocked until you run the unhide commands.
Sent from my KFFOWI using Tapatalk

Update Check, Settings app Crash

After the latest update, I believe its the 3 or 4th on 5.1.1, When go through the usual Settings >> About Device >> Software Update, the settings app force closes with the message "Unfortunately Settings has stopped".
Now my questions are :
1) Will I still receive updates OTA (i.e. Marshmallow)?
2) Have a terminal app on my device, can I check for updates via that?
3) Can check for updates via ADB in Mac terminal?
4) Is it possible to force Smart Switch to check for update rather that have it as an automated check?
Sorry for all the questions.
Any/All help greatly appreciated
ok, a little update.. Im still having the same issue (very very frustrating).
So, I use Nova Launcher and had a dig through the Activities, specifically the Settings activities, I found only 1 pertaining to updates. SO I made a widget with this activities the result was an "access denied" message.
Please, I need to fix this.
issue has been solved by OTA update to 6.0.1.. can a Mod please close this thread. thanks

Categories

Resources