The Launcher3 fork known as "Rootless Pixel Launcher"
The developer of this repository has not created any items for sale yet. Need a bug fixed? Help with integration? A different license? Create a request here:
By Amir Zaidi
Play Store release: https://play.google.com/store/apps/details?id=amirz.rootless.nexuslauncher
Photos and videos: https://photos.app.goo.gl/qdcAcLOdiu8Kl1Bh1
APK Downloads: https://github.com/amirzaidi/launcher3/releases
Rootless Pixel Bridge: https://github.com/amirzaidi/AIDLBridge/releases
Magisk version (only for Pixel users): https://github.com/amirzaidi/launcher3magisk/releases
My launcher is a close to AOSP launcher that only changes the necessary code to allow for small extensions and backporting to older Android versions. If you want a more feature packed launcher use Nova, Action or Lawnchair. It is focused on simplicity and rock solid stability. Bug reports go above all else, and almost every feature request will be denied.
This launcher supports adaptive icon packs. I made an example pack called Google Icons, which replaces OEM icons with the Google variant: https://github.com/amirzaidi/GoogleIcons/releases
There is also a module for Pixel users if they grew bored of the default launcher and want to try out my launcher.
Disable this launcher and switch to different launcher before enabling or disabling the module. Not doing so could result in a “0.0dip has stopped working" bug. If you do encounter this bug, try installing the real Pixel Launcher from the app store.
Before I talk about the things I used for the creation, I want to put a disclaimer that I did not simply copy and paste what the developers did. I looked at their code to spare myself time in researching the places where changes are necessary for a feature, and then made my own implementation. Still, I want to credit these developers for the hard work they have done upon which others like me could build.
Till is the founder of Lawnchair, the Pixel Launcher with many customization features. Initially I did not want to implement icon packs because I feared it would break too many things, but then I took a look at his old implementation to see how much work it really was. And to my surprise it could be done without changing any AOSP Java code. Instead, I could specify a custom icon loader through XML and then focus on writing that icon loader code. The icon loader could load an icon pack app’s icon list and save that list in memory.
Samsung users were facing stylistic issues, saying they were seeing blue folders and a blue app drawer. They also had this problem in the real Pixel Launcher, but Paphonb had fixed it according to them. So I decompiled Paphonb’s Pixel Launcher and compared it with the real APK to see what he changed. From his I figured out what was necessary to override Samsung’s changes and incorporated them in my styles.
This commit, used by Flick Launcher, was what gave me the idea of a simple most-clicked counter for app predictions. I extended the code with the idea of “decay” where new apps can eventually catch up with the older apps and the old apps aren’t stuck forever at a high click count.
This member of Paranoid Android, who is also known as TheCrazySkull, was the first person that got the Google Now feed to work and release sources for it on GitHub. Thanks to him, the entire chain of “Rootless” Google Now feeds has been set in motion. I first tried implementing it on the Custom ROM called VertexOS, and wanted to find a way to debug what I was doing. I managed to get the launcher to compile in Android Studio, and to my surprise it worked after simply installing it as an apk! I hadn’t seen anyone else release a launcher that supported this (except for Google, obviously) so I continued working on it until it became the first version of “Rootless Pixel Launcher” (after a lot of decompilation with trial and error).
The Nova Launcher developer was kind enough to e-mail me the details of WHY the Google Now feed was working on my launcher. He explained that the Google App used to have two ways of showing the Google Now feed: either the Google app was installed as a debug variant app, or the launcher was installed as a system app (which requires root). A few months ago Google changed this condition, so it also shows when the Launcher is installed as a debug app. This is why my debug variant launcher APKs are working, and the apps on the Play Store (which requires a release variant app) need a “companion” that runs as a debug app to get the Now feed. I think I still haven’t replied to this e-mail, so if you are reading this Kevin, I’m sorry..
This Substratum developer taught me how to make a Magisk module this week. I wanted to release it on his name, but he said it’s so simple I didn’t have to do it. So instead I will credit him here.
I kanged the translations for the terms “Icon pack” and “Applying” from their launcher. Sorry (not really).
For making the real Pixel Launcher in the first place. I also got some translations using Google Translate.
Working on this launcher took a long time, and I would like to thank all the testers across different Android versions and OEMs for making sure the launcher has rock solid stability. You reported bugs to me at an incredible pace which is necessary for a project of this scope. Without you I wouldn’t have been able to come this far!
Enjarify, Procyon and Jadx do 75% of the decompilation work, but you have to manually fix up the decompiled sources before you can even think about compiling in Android Studio. I want to thank the creators of these decompilation tools for the impressive work they have done.
If it requires an additional settings entry, no. I stand for simplicity and perfection out of the box, and having a lot of customization does not fit in that vision. Use Nova, Action or Lawnchair if you want features, I probably won’t add it.
I tried my best to backport as much as possible all the way to Lollipop. Some features like app shortcuts are simply too difficult for me to do properly and without bugs at this moment. The light theme could work on Marshmallow, but is broken on some OEM Stock Marshmallow ROMs so I decided to just disable it for Marshmallow.
Disable the weather card in Google Now, or use a lower DPI. Changing your DPI can be done from Android 6 onwards, and it can be done through the settings app from Android 7. It’s called “smallest width” in the developer options.
This is based on your DPI/smallest width. For Marshmallow you will have to Google how to change it with ADB. On Nougat and Oreo you can change it using the “smallest width” setting in developer options.
Update the Google App to the latest version, set my launcher as the default launcher, then reboot the phone. If you are on a tablet, I’m afraid the Google App doesn’t support it.
Google likes giving everyone a different experience with 10+ A/B testing flags. This is beyond my control and all handled by the Google App.
This is dependent on your Google App and can break for many reasons. Make sure your location is on the High Accuracy setting, Google Now shows a card for your weather, you have an up to date Google App, and the new feed is working.
These only work with Google Calendar. Like the weather, everything is handled by the Google App, so it is hard for me to debug.
These only work on Marshmallow on newer, so Lollipop will never show them. If you are at least on Marshmallow make sure the app has permissions to read notifications. You can check this in the settings. If they still don’t work, reboot your device.
Google uses a massive library for prediction based on the time of day and location. I have tried decompiling this in the past, but getting everything to work flawlessly is an extremely difficult task. Therefore I decided to leave it out starting with version 2.0, and continue that trend with this 3.0 release.
Only official LineageOS and official Paranoid Android. Anything else can have unexpected bugs that I cannot account for. Make sure you are on either of those ROMs or your device’s stock ROM if you want to do a bug report.
Use the “Calming Coastline” Live Wallpaper. You can find a port of the new Pixel 2 Live Wallpapers here: https://forum.xda-developers.com/showpost.php?p=74142755&postcount=608
They are two completely different projects. I started with AOSP Launcher3 in Android Studio, he started with the real Pixel Launcher APK where everything was already working. I focused on implementing all the functionality in Java, he modified the APK to work better on older Android versions. The disadvantage to my method is that some features like Google’s App Suggestions are too hard to add. The advantage to my method is that I could add anything I wanted at any time, like Icon Pack support. So, it is an initial effort vs down the line feature implementation effort trade-off.
Ironically, the “Rootless Pixel Launcher” requires root for Pixel users. The reason for this is that it uses the same name as the real Pixel Launcher. The real one cannot be removed or overwritten without root. Changing the name would break the Smartspace features, because Google hardcoded the Google App to only provide the features to the “real” Pixel Launcher.
Launcher3 is the name that the default AOSP launcher uses. If you compile AOSP from sources directly, that is what you will get. My GitHub project is called Launcher3 because I forked from AOSP and did not change the name. Changing the GitHub project name now is possible, but unnecessary.
First use another launcher like Nova as your default. Then delete any other Pixel Launcher you have on your phone. If you can't do this because you are on a Pixel or custom ROM, use the Magisk module (needs Magisk).
Change your DPI, like with the Smartspace getting cut off FAQ entry.
Blame Google, they decided this was better.
Set a very dark wallpaper. The threshold is an average brightness of 25% and there shouldn't be many bright spots.
Set my launcher as the default launcher first. They only work on Android 7.1 and higher.
Remove it from any other launcher you have on your phone first
Select another launcher as your default, then you can uninstall it from your phone's settings app.
Go to the APK Downloads link, and click the top most "Launcher3-aosp-debug.apk". After it is downloaded, click the notification and press install.
Custom ROM users have to disable the "RR dynamic navbar" feature. Samsung and LG users might have to enable the fullscreen mode for this app in their device's settings.
Unfortunately this is a Samsung specific problem and would require a lot of hacking around to fix. If you are desperate to make them white, consider using a substratum theme.
Seems to be a Google App problem, every launcher with the new feed is suffering from it, including the real Pixel Launcher. Make sure you are not using a Google App Beta.
For a reason I can’t diagnose because I don’t have a Huawei device, recent Huawei phones seem to crash on launch when the user hasn’t given the launcher storage permissions. If this happens to you go into your system settings and grant the storage permission manually.