New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Doesn't seem to work on Fire OS 6.3 #23

Closed
SilverK98 opened this Issue Nov 16, 2018 · 123 comments

Comments

Projects
None yet
@SilverK98

SilverK98 commented Nov 16, 2018

Title. Downloaded it inside my Fire HD 8, however when i click on it the screen flashes and the app doesn't open

@sturgeo1

This comment has been minimized.

sturgeo1 commented Nov 20, 2018

I have the same issue. Downloaded it to two brand new Fire HD 8 tablets and the app does not function. It works perfectly on my Fire 7. Any suggestions or workarounds?

@drizzt09

This comment has been minimized.

drizzt09 commented Nov 23, 2018

v2.1 appears to work on the Fire HD 8 though

@friedl

This comment has been minimized.

friedl commented Nov 23, 2018

I can confirm V3 does not work on a Fire HD8 with Fire OS 6.3.0.1.

v2.1 appears to work on the Fire HD 8 though

Also on the newest Fire OS?

@drizzt09

This comment has been minimized.

drizzt09 commented Nov 23, 2018

Yes I have brand new out of box yesterday 8HD that upgraded to 6.3.0.1

@BaronKiko

This comment has been minimized.

Owner

BaronKiko commented Nov 23, 2018

Sadly I don't own one of the new hd 8's so I honestly have no idea. If some of you could send the crash log from the app opening then I can at least have a guess what's going wrong. It may be easy to fix or hard to fix I just don't know without more info. If it's a hard fix then there really isn't much chance I could fix it as I can't test any changes I have made.

@drizzt09

This comment has been minimized.

drizzt09 commented Nov 23, 2018

I can plug into logcat this weekend and grab logs.
Have to do it when kids aren't around as it's an xmas present. Opened to set it up last night so it's ready to go on unwrap

@davidfi01

This comment has been minimized.

davidfi01 commented Nov 24, 2018

V3.0 works on HD8 2018 if you enable "allow display over other apps". However, a side effect is that when you open task switcher, and try to jump to another task, it jumps you back to the home page only.

Another overlay shows in YouTube. The control overlay with the pause, forward and back buttons does not disappear when playing videos.

@friedl

This comment has been minimized.

friedl commented Nov 25, 2018

V3.0 works on HD8 2018 if you enable "allow display over other apps". However, a side effect is that when you open task switcher, and try to jump to another task, it jumps you back to the home page only.

Awesome. That worked. I can live with the task switcher not working, because closing tasks still works.

@drizzt09

This comment has been minimized.

drizzt09 commented Nov 25, 2018

HiJack3Crash.txt
ok this is the fatal when trying to launch v3:
I/ActivityManager(569): Start proc 11833:com.baronkiko.launcherhijack/u0a178 for service com.baronkiko.launcherhijack/.HomeButtonService 11-25 15:32:24.997: D/VendorDisplayManagerGlobalCallback(11833): callGetInstance: nil 11-25 15:32:25.003: W/ActivityThread(11833): Application com.baronkiko.launcherhijack can be debugged on port 8100... 11-25 15:32:25.009: W/System(11833): ClassLoader referenced unknown path: /data/app/com.baronkiko.launcherhijack-1/lib/arm 11-25 15:32:25.051: D/AndroidRuntime(11833): Shutting down VM 11-25 15:32:25.052: E/AndroidRuntime(11833): FATAL EXCEPTION: main 11-25 15:32:25.052: E/AndroidRuntime(11833): Process: com.baronkiko.launcherhijack, PID: 11833 11-25 15:32:25.052: E/AndroidRuntime(11833): java.lang.RuntimeException: Unable to create service com.baronkiko.launcherhijack.HomeButtonService: android.view.WindowManager$BadTokenException: Unable to add window android.view.ViewRootImpl$W@7867e5 -- permission denied for window type 2006 11-25 15:32:25.052: E/AndroidRuntime(11833): at android.app.ActivityThread.handleCreateService(ActivityThread.java:3223) 11-25 15:32:25.052: E/AndroidRuntime(11833): at android.app.ActivityThread.-wrap5(ActivityThread.java) 11-25 15:32:25.052: E/AndroidRuntime(11833): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1578) 11-25 15:32:25.052: E/AndroidRuntime(11833): at android.os.Handler.dispatchMessage(Handler.java:102) 11-25 15:32:25.052: E/AndroidRuntime(11833): at android.os.Looper.loop(Looper.java:154) 11-25 15:32:25.052: E/AndroidRuntime(11833): at android.app.ActivityThread.main(ActivityThread.java:6188) 11-25 15:32:25.052: E/AndroidRuntime(11833): at java.lang.reflect.Method.invoke(Native Method) 11-25 15:32:25.052: E/AndroidRuntime(11833): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:911) 11-25 15:32:25.052: E/AndroidRuntime(11833): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:801) 11-25 15:32:25.052: E/AndroidRuntime(11833): Caused by: android.view.WindowManager$BadTokenException: Unable to add window android.view.ViewRootImpl$W@7867e5 -- permission denied for window type 2006 11-25 15:32:25.052: E/AndroidRuntime(11833): at android.view.ViewRootImpl.setView(ViewRootImpl.java:705) 11-25 15:32:25.052: E/AndroidRuntime(11833): at android.view.WindowManagerGlobal.addView(WindowManagerGlobal.java:342) 11-25 15:32:25.052: E/AndroidRuntime(11833): at android.view.WindowManagerImpl.addView(WindowManagerImpl.java:95) 11-25 15:32:25.052: E/AndroidRuntime(11833): at com.baronkiko.launcherhijack.HomeButtonService.onCreate(HomeButtonService.java:52) 11-25 15:32:25.052: E/AndroidRuntime(11833): at android.app.ActivityThread.handleCreateService(ActivityThread.java:3213) 11-25 15:32:25.052: E/AndroidRuntime(11833): ... 8 more

@drizzt09

This comment has been minimized.

drizzt09 commented Nov 25, 2018

after following steps above to allow draw over other apps i was too able to open without crash. I also experienced the issue of not be able to use task switcher and captured those logs. Those ones are a little harder to pinpoint the issue so here is the full log for the test.
HiJack3.txt

@BaronKiko

This comment has been minimized.

Owner

BaronKiko commented Nov 25, 2018

Ah that's part of the same issue that hit fire TV. It's due to new security restrictions added to android.
You can probably just run:
adb shell pm grant com.baronkiko.launcherhijack android.permission.SYSTEM_ALERT_WINDOW

That allows the app to create it's alert window.

Can you still enable accessibility services on the new hd 8? If not there is another command I can look up for you to set that.

But do let me know how that command changes things.
I am still yet to look at the longer log yet. Need my pc for that as mobile formatting is broken

@davidfi01

This comment has been minimized.

davidfi01 commented Nov 25, 2018

Can you do it by using app permission settings or only through adb?

@drizzt09

This comment has been minimized.

drizzt09 commented Nov 25, 2018

accessibility detect home is there and able to enable.
Maybe we need the other one in the code to set the permission(s).

Running the shell command does not help with the task switcher. However it seems to have messed with the home button being pressed.
1/3 times pressing home chooses my Apex Launcher. 2/3 selects Amazon Home
HiJack3home.txt

Update, the home button consistency issue was fixed after device reboot. Task switcher issue still persists

@BaronKiko

This comment has been minimized.

Owner

BaronKiko commented Nov 26, 2018

Ah forgot you need a reboot for the perm to fully take effect. You need to set it via adb on more recent android versions because it was used for viruses and other nasty things. Not sure if the latest fireos falls in this category.
It doesn't look like I can get around the switcher stuff without some code. If any of you are budding Devs you can check out the firetv branch and may be able to get it going (it works in a totally different way) but it's not nice code so it's probably too much of a time sync for most.

@drizzt09

This comment has been minimized.

drizzt09 commented Nov 26, 2018

What's different in 2.1 that it doesn't happen with?

@BaronKiko

This comment has been minimized.

Owner

BaronKiko commented Nov 26, 2018

It works differently, simply put v2 waits till it sees the home screen open and then opens your desired launcher.
V3 directly intercepts the home button press so the default launcher never opens meaning it's much quicker.
The fire TV version works differently again to achieve the same effect as v3 but within the new security restrictions and while I got it working on the TV with 100% success rate it broke the settings menu and long press menu severely limiting the usability of the app. Those issues shouldn't be present on the tablet hence why I said you could probably get that version working.

Not sure all that is 100% accurate as I wrote it a long time ago now but it's more or less the story.

@Somethingweirdhere

This comment has been minimized.

Somethingweirdhere commented Nov 27, 2018

Thanks for the app @BaronKiko. The home-button works perfectly, but the task switcher always defaults back to the home page (just like @drizzt09 said. Is there anything that can be done about this?

@BaronKiko

This comment has been minimized.

Owner

BaronKiko commented Nov 27, 2018

As I have said previously the firetv version may fix it as it works differently but it's still in development. Unfortunately I have been busy with getting a real job so it's been on hold for 3-4 months now and shouldn't be used on a device without fixing up.
I can try make a build at some point with the extra firetv stuff removed if I get a spare evening or 2 but please don't hold me to it as getting that time isn't so easy.

@dwaal

This comment has been minimized.

dwaal commented Nov 27, 2018

I have Hijack running on my FireHD 10 (2017). Works perfect.

I just installed it on my new FireHD 8 (2018) and tested it with various launchers. Sometimes it works, sometimes it does not. Very strange.

Shouldn't it work all the time or not at all? It's more like 50:50

@Somethingweirdhere

This comment has been minimized.

Somethingweirdhere commented Nov 27, 2018

@BaronKiko I tried the 2.1 one. It sometimes flashes the old screen, but it works just fine for me :) The only thing that is weird are widgets, but I don't think it's possible to fix this.

That said, take your time. Real life is more important than this, so get everything working there before you worry about this :) and good luck with the Job Search!

@dwaal

This comment has been minimized.

dwaal commented Nov 27, 2018

I tried 2.1 from scratch on my FireHD 8.

What I did:
Installed Apex 3.3.3 and LawnchairLauncher2.2
Installed LauncherHijack v2.1

Started LauncherHijack and selected one of the new launchers
Went to "Settings -> Accessibility -> To detect home button press". The problem here is, when I click on it, it does show me an empty screen.
Unlike with my FireHD 10, where there is a ON/OFF toggle button to set "detect home button press".

Is this only me or is the option "To detect home button press" permanently "OFF" and there is no way to change it for the new "Fire HD 8 (2018)" ???

Can somebody confirm this?

@splitbrain

This comment has been minimized.

splitbrain commented Nov 27, 2018

@dwaal I needed to upgrade FireOS to 6.3.0.1 before the accessibility options worked on my 8th gen Fire HD 8. Before I also had the empty screen. I'm using Launcher Hijack v3.

@drizzt09

This comment has been minimized.

drizzt09 commented Nov 27, 2018

I concur accessibility is broken in 6.3.0.0. had to upgrade to 6.3.0.1
It also doesn't just affect this app. It was same with my parental controls app. Was also missing the on off toggle and needed the OS update

@BaronKiko

This comment has been minimized.

Owner

BaronKiko commented Nov 27, 2018

Accessibility is not broken in the os, the menu was removed for security reasons. The new tablets as I am led to believe (don't own one so can't confirm) are using a newer fireos version that the firetv cube and stick have been using for a while now. This new version is based on a later android base version.
In fairness it's Google that have made the decision to hide it as it is a really bad security flaw allowing mostly full access to an unrooted device.
Amazon may have added the option back and that would be handy to know but you can still enable accessibility services via adb.

The command is in the next post and works for any service you wish to enable. This means you can't accidentally enable it but it is kind of a pain.

Hopefully that clears things up as the same issue has been posted on various threads a couple times now. Either that or people aren't reading this stuff -_-

Somebody mentioned widgets, in amazons infinite wisdom they block widgets on all 3rd party launchers. There are some adb commands that enabled widgets on any launcher of your choosing (can't remember what they are but some googling should bring it up). I never use them because Google being the top dogs have some kinda backdoor in fireos/android that allows their launcher, Google now which seems to be getting killed off :( , to use widgets on the device out of the box so I suggest you just use that. It's a solid launcher anyhow.

@BaronKiko

This comment has been minimized.

Owner

BaronKiko commented Nov 27, 2018

THESE COMMANDS ARE WRONG, USE THE ONES FURTHER DOWN THE PAGE!!!

Turns out the command was on another issue so here is it:
You can enable the service via adb with:

adb shell settings get enabled_accessibility_services
Copy the output from the above command and paste it into the command below

adb shell settings put enabled_accessibility_services (PASTE_HERE):com.baronkiko.launcherhijack/com.baronkiko.launcherhijack.AccServ
Hope that helps,

@drizzt09

This comment has been minimized.

drizzt09 commented Nov 27, 2018

The accessibility settings are there on fireOS 5 (android 5) and in FireOS6 (android 7) with the patch update.
It's also on my android phone (android 8.1) and my old phone (Android 6). It's needed for many apps such as parental controls. It was also on my galaxy tablet when it was android 5, 6 and 7. I have never not seen it there.(except fireOS 6.3.0.0)

@BaronKiko

This comment has been minimized.

Owner

BaronKiko commented Nov 27, 2018

I can't remember the details but the menu to enable them is defiantly missing on the firetv someone donated to me. Hence the need for the command.
It's a smart thing to do honestly, as I mentioned earlier it's really just a great way for hackers to install a virus onto your phone. You get to intercept all button presses, read what's on the screen in the currently loaded app etc. Basically you can lock someones device up, go through all their apps 1 by 1 and take any data that shows up on the screen. So take all your contacts, read your facebook, instagram, twitter and all that good stuff. All while the owner gets to watch his phone flicking through apps unable to do anything as you can't remove a battery in modern devices. Worse yet they can just silently watch everything you do.

Nasty stuff but it's pretty much the only way to do what this app does. Frankly if I didn't write the code I would be hesitant to install it myself.

@BaronKiko

This comment has been minimized.

Owner

BaronKiko commented Nov 27, 2018

Oops, command above are wrong though it doesn't seem they are needed. Correct one to get should be:
adb shell settings get secure enabled_accessibility_services
Set should be:
adb shell settings put secure enabled_accessibility_services (PASTE_HERE):com.baronkiko.launcherhijack/com.baronkiko.launcherhijack.AccServ

And as you know you also have to use:
pm grant com.baronkiko.launcherhijack android.permission.SYSTEM_ALERT_WINDOW

@dwaal

This comment has been minimized.

dwaal commented Nov 27, 2018

Thanks. Works now with a little more jitter compared to v3.

The warning message emitted by the "to detect home button press" toggle sounds quite a little bit less scary: it can read text you type (except passwords). Is it text you type or any data showing on the screen?
Btw, why lump into one permission to ability to detect home button press and reading text you type?

Is every app able to "detect home button press" when you turn this on?

This all sounds a bit scary. Maybe I stick with my temporary workaround and just use the Amazon launcher. Once you put ALL the garbage apps from Amazon into a single "app folder" you are basically just left with the stuff you installed yourself from the PlayStore.
Also you obviously don't have to turn on "home button detection" ;)

@BaronKiko

This comment has been minimized.

Owner

BaronKiko commented Nov 28, 2018

It's not quite all 1 permission, there are multiple sub perms for each service mostly to reduce the noise an app would have to deal with, but it's easier to just enable it all as android perms are a pain. This app specifically intercepts home button presses and listens to the default fire launcher opening and the device booting. I.e. it's not spying or anything like that and if you don't trust me all the code is there to read :P
It also creates an invisible overlay window that isn't part of the accessibility services (that's what the other command enables). That also intercepts home button presses.

It is possible that other services will spy but assuming you trust the source you should be fine. Just like how any company that makes drivers for windows could be doing malicious things but you wouldn't worry about installing an nVidia driver for example.

My point was that it makes you think about what you are installing. Most people when told to enable a service in the settings will just do it, similar to how most people just never read the permissions page that comes up when installing an app.
Most people that have the know how to install adb, enable dev options and run the required commands know what they are doing and are aware of the risks. Very few can do all that yet not understand the dangers.
On top of all that Google's basic rule of thumb is if you break your device through the normal OS it's a security issue and therefore Googles fault (at least in part). If you break it through adb, well you are a dev so that's on you. Not to say they won't help recover your device but it's not a bug for them to fix.

In short the rule is: only install services from developers you trust. Same goes for regular apps but it's far less likely to break the device if you ignore the rule.

Finally if you can get v3 working it should be better, You will need to re-run the commands every time you install, update or reinstall the app.

@thechanch

This comment has been minimized.

thechanch commented Dec 5, 2018

@drizzt09

This comment has been minimized.

drizzt09 commented Dec 5, 2018

@andrewcianci what happens if you press the home button without crashing the 2 two?
just open recents and press home button

@BaronKiko

This comment has been minimized.

Owner

BaronKiko commented Dec 5, 2018

I'm going to assume that's just the style choice Amazon has chosen for the dialog boxes. I apply no styling and they look different on every device I know of. As long as the buttons work I choose not to worry about it.
Launcher Hijack should appear in the recents as it's just an app and doesn't need to be open for the service to work. Your chosen launcher however shouldn't but after watching that video that's the least of your concerns.
As has been discovered frequently throughout this thread rebooting after setting up fixes a lot of issues. And clearly make sure the accessibility service is enabled. Assuming you have already done that or doing that makes no difference I need those logs

@thechanch

This comment has been minimized.

thechanch commented Dec 5, 2018

unable to grab logs right now, i'll try tonight. accessibility service is enabled and rebooted a handful of times.
@drizzt09 for reference, pressing home drops me to the stock launcher, and then hitting home again flashes screen back into evie.

@drizzt09

This comment has been minimized.

drizzt09 commented Dec 5, 2018

if you go into recents and swipe away everything. it should auto return to home... and if working properly should be eevie. although i found eevie didnt work well on fire tablet 7. which is why i switched to using Apex. I have not tested Eevie on Fire tab 8 since Apex worked so well on FT7 i stuck with it

@BaronKiko

This comment has been minimized.

Owner

BaronKiko commented Dec 5, 2018

Oh something to note, the button doesn't override while the recents menu is open. Somebody in this thread (don't want to read it all again to find out) reported issues regarding it so I disabled it in that case. You can go into the new settings menu in launcher hijack and change it but you probably wont be able to switch apps without it.

It does look like the service isn't running, I had the issue where the service wouldn't start regardless of the settings but thought it was just development. If that's the case you have to:

  1. Do a complete uninstall for all user as I mentioned earlier
  2. Do a full reboot so shutdown wait a couple seconds then boot again
  3. Reinstall and all the usual

I think it's due to not changing the version number.
If all that doesn't help then it's really about those logs. I'm not planning on doing any more dev today, spent a good 10 hours so there is no need to rush.

@thechanch

This comment has been minimized.

thechanch commented Dec 5, 2018

👍 will test @BaronKiko suggestions and test Apex and Nova to see if Evie is the culprit. thanks all

@thechanch

This comment has been minimized.

thechanch commented Dec 5, 2018

complete uninstall + reboot + reinstall with Apex and im having no issues.
can't pinpoint Evie at this point but i'm content with the outcome, thanks everyone

@BaronKiko

This comment has been minimized.

Owner

BaronKiko commented Dec 5, 2018

Great, need to add those instructions to the troubleshooting section. Evie should work, it's the launcher I use. Don't see why it would be different for the new Fire OS.
Least there isn't yet another bug I need to fix :)

@drizzt09

This comment has been minimized.

drizzt09 commented Dec 7, 2018

do we have an official release then now?
Are you releasing it any stores?
Aptoide is good as it has a normal version and a TV version so you can release to both and have your version for Fire TV available too

@BaronKiko

This comment has been minimized.

Owner

BaronKiko commented Dec 7, 2018

There are still a couple things I need to finish literature wise. Got busy, hopefully I can get something out tomorrow but we will see :)

@davidfi01

This comment has been minimized.

davidfi01 commented Dec 8, 2018

I can't get V4 to work on HD8 2018 regardless of resets/rebbots/settings.

Once I replace 3.x with 4, remains at native launcher.

D

@BaronKiko

This comment has been minimized.

Owner

BaronKiko commented Dec 8, 2018

Not even posted about it outside github and already bugs :(
When you close the app in the app switcher and open it again does it say the service isn't running?

@BaronKiko

This comment has been minimized.

Owner

BaronKiko commented Dec 8, 2018

Well I have rechecked and it works for my devices.
Anybody running any of the debug builds I suggest you uninstall the old one for all users then reboot before installing the new version. Would like to know it works before advertising.

@davidfi01

This comment has been minimized.

davidfi01 commented Dec 8, 2018

Checking now on another device.

  1. remove 3x debug
    2)reboot, install 4
  2. activate accessibility setting
    4lreboot, activate Google now
  3. reboot
    Will post results
@davidfi01

This comment has been minimized.

davidfi01 commented Dec 8, 2018

Does not work on second device either. Also, does not seem like settings are taking. I enable setting to display over other apps, and then check apps settings for lh4 after reboot, and app settings (system app settings) does not show display overlay is on. Also when lh4 setting to hide in task switcher is checked, it still shows in task switcher.

@BaronKiko

This comment has been minimized.

Owner

BaronKiko commented Dec 8, 2018

The overlay window is disable by default on the new devices as it's not needed. You can reenable it in the newly added settings menu but I don't recommend it.
So the question is, is the Accessibility Service running. When you open the app it will alert you if it's not running with a default modal dialog. Rotate your device on the launcher select menu and it will recheck. If you don't get that then all should be ok. Saying that I would be far more worried if you aren't getting that dialog because then you have an actual bug and I don't like them :(

@davidfi01

This comment has been minimized.

davidfi01 commented Dec 8, 2018

Not getting modal dialog. Was able to get Google now to show once by toggling accessibility setting couple of times. The launcher reverted upon a restart. Have not been able to get Google now to work again.

@BaronKiko

This comment has been minimized.

Owner

BaronKiko commented Dec 8, 2018

Maybe try another launcher? Google now is known to be a pain. Once set up shouldn't be an issue. Also note that the first time you press home after a reboot or launcher change it can be quite slow to open as it has to start the launcher up. After that it should be quick.

@BaronKiko

This comment has been minimized.

Owner

BaronKiko commented Dec 8, 2018

I can't replicate this issue. I have noticed that you need to disable then enable the service after a reboot and there has been 2 more issues spotted so v4 is no good. Would be helpful if others are getting the same issue so I can better narrow it down.

@BaronKiko

This comment has been minimized.

Owner

BaronKiko commented Dec 8, 2018

New release, it doesn't directly fix your issue as I am unable to replicate but I am hoping that it is encompassed by the other bugs I squashed.
Also other peoples experiences would be appreciated.

Edit: As I mentioned earlier I suggest you uninstall the old one for all users and reboot before installing the new version.

@davidfi01

This comment has been minimized.

davidfi01 commented Dec 8, 2018

So 4.01 loads Google now on boot. However, loses it with home button press. It costs and then reverts to Amazon launcher. If I switch to task switcher, and return, it relaunches Google now.

@BaronKiko

This comment has been minimized.

Owner

BaronKiko commented Dec 8, 2018

Hmm, maybe you should just not have issues. It would stop making me sad.
Will have another look later. Am hungry so having some dinner.

@BaronKiko

This comment has been minimized.

Owner

BaronKiko commented Dec 8, 2018

Final release of the night. Hopefully 4.0.2 works.

@davidfi01

This comment has been minimized.

davidfi01 commented Dec 9, 2018

4.02 working on fire hd8 2018. Thanks! Great effort.

@BaronKiko

This comment has been minimized.

Owner

BaronKiko commented Dec 9, 2018

Thank the lords, before I do the final write up later today anybody else able to test. I like at least 2 confirmations from each device and the new tablet is the only device yet to meet this.

@drizzt09

This comment has been minimized.

drizzt09 commented Dec 9, 2018

Where's the download for 402. I'll give it a test
NM found. Testing.....standby

@drizzt09

This comment has been minimized.

drizzt09 commented Dec 9, 2018

Ok cleared data and uninstalled v2.1. installed v4.02. no reboots.
Launching prompted for accessibility. Clicking on it returned to ftv home. I manually launched accessibility settings and turned on home detect.
Selecting apps in recent task switcher works. Awesome.
I do see apex home as an app option and if I swipe it away it takes an extra second but loads.
I can see a slight flicker when pressing home but you have to be looking for it to see it. It's so fast you don't see ftv home at all.
After reboot all working the same.
Very nice build. Great job. Now to install it on my other daughter's tab7. :)

@BaronKiko

This comment has been minimized.

Owner

BaronKiko commented Dec 9, 2018

Awesome, I'm taking 4.0.2 out of pre-release and marking this issue resolved. Thanks for all your testing to everybody in the thread.
Fyi If all goes well I will be putting Launcher Hijack up on f-driod and aptoide so look out for that if you are interested in a more streamlined updating situation, otherwise enjoy.

@BaronKiko BaronKiko closed this Dec 9, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment