I've created an app for dual booting automatically to Android or WM6. V2.3.2 can boot multiple version of Android on a single SD card and can be customized for text content and language. See post #2 for documentation and screenshots.
The "lite" version is a replacement for using a file explorer to run CLRCAD then HaRET, allowing Android to be started with a single tap on an icon. To install the lite version, simply un-RAR the contents to your Android folder then use a file explorer to create a Start Menu shortcut.
Please leave feedback and suggestions/questions.
French translation:http://forum.xda-developers.com/showpost.php?p=13123392&postcount=151
Documentation and Screenshots
RunDroid app v2.3.2 for HTC HD2 by Pop45398 (@ XDA Developers)
This app can start Android on an SD card automatically on boot-up or with a single tap, thus allowing for an easy dual boot to Android or Windows Mobile, and should be compatible with all versions run with CLRCAD/HaRET. It features a setup menu which allows for user customization including setting the timeout before the default OS is started, thus allowing time to access the setup menu or select a non-default OS. It is actually a MortScript and corresponding MortRunner with a custom icon. It may work on other WM6 devices.
CHANGES:
Version 2.3.2 added a new subroutine to rename the Android folder back to its original name when “Enable Builds” is selected if RunDroid had renamed the folder to Android. This eliminates the folder being renamed to Android[1]. (Thanks to crazycranky!)
Version 2.3.1 features language/text customization. By editing RunDroid.ini with a text editor the user can now change all text for desired content and language (with exception of button text, i.e. Ok/Cancel, Yes/No). There is no longer a need to edit the script for non-English ROMs where the SD card is not called “Storage Card”, a directory tree will appear for the user to locate the SD card’s root.
Version 2.2.1 features some minor changes over v2.1.1. A StartUp shortcut is no longer used for auto-launching at boot-up, instead it is launched during the init process before StartUp programs, hence the elimination of creating and deleting shortcuts from the Setup Menu. A new option to Enable Sense has been added so that Sense can be easily re-enabled if somehow not properly re-enabled during script execution. A setup.dll is now used to run Install and Uninstall scripts.
Version 2.1.1 represents a major overhaul from version 1 and features the ability to boot to a basically unlimited number of Android builds and a guided setup that walks through the setup process on initial running. It will scan all folders in the SD card's root for Android builds, indicated by the presence of HaRET.exe. It asks whether to use each build then asks if it requires renaming the folder to Android in order to run (some builds don't require being in the Android folder). A .cab file is used for installation which is now in the RunDroid folder in the root of the device. The folder name is used for displaying the build's name in RunDroid, with one caveat: if there is more than one build and one of them is named Android, that folder will be renamed to Android[1] so that the selected build folder can be renamed to Android (which is renamed back to original when another build is selected), hence descriptive folder names should be used.
INSTALLATION:
Simply copy the .cab file to the SD card and run it with a file explorer to install. Version 2.3.1 MUST be installed to the device due to hard coded addresses required for auto-launching. This also eliminates the occasional possibility of the SD card not being initialized before RunDroid is started during boot-up. If during installation the SD card is not found by the default name “Storage Card” (usually due to a non-English ROM) a directory tree will appear for choosing the correct SD card root, not Android folder (see screenshots below for an example).
OPERATION:
Start RunDroid with the Start Menu icon. On initial running, a guided setup will walk through the settings. Menus are self-explanatory (see screenshots). Selection is done by double-tapping an entry or tapping once then tapping OK. Only the main (Boot Selection) menu is timed for auto-selecting. If auto-running at boot-up is NOT desired, select “Disable AutoStart” during initial setup or later from the Setup Menu. The Timeout Delay may be adjusted to suit the user and system (see ISSUES section below). Whenever another build is added or deleted, one is no longer desired to be run, or a folder name changed, Enable Builds must be selected from the setup menu which will once again walk through the setup of builds and default OS selection (but not other settings). Builds are displayed in alphabetical order and can only be rearranged by renaming folders, like by adding a number at the beginning of folder names.
ISSUES:
Startup programs, including HTC Sense and Notifications, etc, can briefly interfere with the ability to make selections, causing the default OS to be started before menu selections can be made. To combat this, if enabled and not already started, Sense is disabled then re-enabled on app exit. The Timeout can be adjusted to help with this. If the Timeout is set too low and selecting the Setup Menu or Boot to Windows is not possible, simply re-install the .cab. If unable to boot to Windows because Android starts before the menu appears, power off the device, remove the SD card, then power on the device; if not already at the menu, start RunDroid and go to the Setup Menu and adjust the Timeout to allow more time to access the menu, then power down and re-insert the SD card.
CUSTOMIZATION:
The user interface can be customized for text size, font type, language, and size of menu selection entries by editing RunDroid.ini with a (pure text) editor such as Notepad. Once RunDroid is installed, locate the .ini file in the RunDroid folder in the root of the device (not SD card) and open or copy to PC then open.
The following variables control the font and size of menu entries:
FontSize=23
EntryScale=1.3
FontType=Tahoma
Increase or decrease FontSize to make menu selection text larger or smaller. EntryScale controls the size of menu selections, larger size makes selections easier to make. The scale is in percentage of the font size, i.e. 1.3 equals 130% of the font size. To use a different FontType than Tahoma, the desired font must be installed on the device.
In addition to descriptive variable names, to make RunDroid.ini easier for editing text content and language certain conventions are used:
Variables containing “Sel” are for menu selection entries.
......WMsystemSel=Windows Mobile
Variables Containing “Hint” are for the text that appears in the upper portion. Note that “Setup Menu” is preceded by a period and several spaces. The spaces are to center the text; the period is required because leading spaces will otherwise be ignored and the text will begin on the left instead of centered.
......SetupMenuHint=. Setup Menu
Variables containing “Txt” are for messages and questions which pop-up in new windows.
......NoBuildsMessTxt=There were no Android builds using HaRET.exe found on this SD card.
Do not change the actual variable names, for example “TimeoutMessHint=”, only the text following the “=” sign as these names are hard coded into the script and the new text will not appear.
Editing prior to completing the initial setup is preferred. Once editing is complete, copy the modified file to \RunDroid, overwriting the original. A copy of the modified RunDroid.ini file should be saved somewhere besides \RunDroid because if RunDroid is reinstalled or a newer version installed the entire folder will be deleted along with the modified file. Once reinstalled, copy the modified file to \RunDroid before completing the initial setup.
Let me try.
Works Great!
Thanks
shadowburt said:
Works Great!
Thanks
Click to expand...
Click to collapse
78 downloads (and another dozen in another thread) and finally some feedback, was beginning to wonder if it only works for me. Am glad it works for you.
My original intent was just to make a script that runs CLRCAD then HaRET by simply tapping an icon on the Start Menu instead of using a file explorer to run them separately like the chefs all say. That is what the "lite" version does. I then remembered I had routines in other scripts I'd written a few years ago that could be used to spice it up.
Hi, I´m gonna try it i a minute - sounds goode - thank you!!!
pronor
Is there interest in RunDroid having the ability to select different Android builds from the same SD card? If enough interest I can do this but because most builds require being located in the Android folder a small .ini file will be required in each build folder so that folders can be renamed then renamed back when a different build is selected. Sorry, I can't edit the original post to make it a poll so you will have to post your interest in this mod.
Pop45398 said:
Is there interest in RunDroid having the ability to select different Android builds from the same SD card? If enough interest I can do this but because most builds require being located in the Android folder a small .ini file will be required in each build folder so that folders can be renamed then renamed back when a different build is selected. Sorry, I can't edit the original post to make it a poll so you will have to post your interest in this mod.
Click to expand...
Click to collapse
Hooo man i want this +1
Pop45398 said:
Is there interest in RunDroid having the ability to select different Android builds from the same SD card? If enough interest I can do this but because most builds require being located in the Android folder a small .ini file will be required in each build folder so that folders can be renamed then renamed back when a different build is selected. Sorry, I can't edit the original post to make it a poll so you will have to post your interest in this mod.
Click to expand...
Click to collapse
That would be awsome!!!
New version
yesucan said:
Hooo man i want this +1
Click to expand...
Click to collapse
palmbluetooth said:
That would be awsome!!!
Click to expand...
Click to collapse
I've PMd y'all a download link for v2.01. The new version represents a major overhaul from v1.02 and features the ability to boot to an unlimited number of Android builds and a guided setup that walks through the process on initial running. It will scan all folders in the SD card's root for Android builds, indicated by the presence of HaRET.exe, then ask whether to use that build, then ask if it requires renaming the folder to Android to run (some builds don't require being in the Android folder). A .cab file is used for installation which is now in the RunDroid folder (when installing, be sure to select Storage Card) . The folder name is used for displaying the build's name in RunDroid, with one caveat: if there is more than one build and one of them is named Android, that folder will be renamed to Android[1] so that the selected build folder can be renamed to Android (which is renamed back to original when another build is selected). Whenever another build is added/deleted, one no longer desired to run, or folder named changed (in this case the Droid.ini file in that folder should be deleted), Enable Builds must be selected from the setup menu which will once again walk through the initial setup of builds (but not other settings).
I've tried every combination I could think of and the folder renaming process seems to work fine. Please post if you find any issues.
PS> Order of build appearance is by alphabetical order and can only be rearranged by renaming folders, for example by placing a number at the beginning of the folder name; however, more than 1-9 will screw that up because 10 will appear before 2, etc.
Pop45398 said:
I've PMd y'all a download link for v2.01. The new version represents a major overhaul from v1.02 and features the ability to boot to an unlimited number of Android builds and a guided setup that walks through the process on initial running. It will scan all folders in the SD card's root for Android builds, indicated by the presence of HaRET.exe, then ask whether to use that build, then ask if it requires renaming the folder to Android to run (some builds don't require being in the Android folder). A .cab file is used for installation which is now in the RunDroid folder (when installing, be sure to select Storage Card) . The folder name is used for displaying the build's name in RunDroid, with one caveat: if there is more than one build and one of them is named Android, that folder will be renamed to Android[1] so that the selected build folder can be renamed to Android (which is renamed back to original when another build is selected). Whenever another build is added/deleted, one no longer desired to run, or folder named changed (in this case the Droid.ini file in that folder should be deleted), Enable Builds must be selected from the setup menu which will once again walk through the initial setup of builds (but not other settings).
I've tried every combination I could think of and the folder renaming process seems to work fine. Please post if you find any issues.
PS> Order of build appearance is by alphabetical order and can only be rearranged by renaming folders, for example by placing a number at the beginning of the folder name; however, more than 1-9 will screw that up because 10 will appear before 2, etc.
Click to expand...
Click to collapse
Thanks man . will try it out ..
Hello,
Is it possible to have the link to download the latest release?
Thank you
tristano said:
Hello,
Is it possible to have the link to download the latest release?
Thank you
Click to expand...
Click to collapse
Sent you a PM.
Thank you.
Downloading.
Gonna try it
Pop45398 said:
Sent you a PM.
Click to expand...
Click to collapse
Can you please post the download link for v2.01? Thanks.
would like to try it out mate....
thanks
Could I have the link also pls ) to the latest version
Thanks)
I got problem when i install the 2.0.1 version follow the instruction . After doing set up press yes to all folder but i don't see the Android folder in the main screen only window . Reinstall delete RUNDROID folder still the some . thanks.
yesucan said:
I got problem when i install the 2.0.1 version follow the instruction . After doing set up press yes to all folder but i don't see the Android folder in the main screen only window . Reinstall delete RUNDROID folder still the some . thanks.
Click to expand...
Click to collapse
After install was there a RunDroid folder in the root of your SD card? When running the .cab file you must select to install to Storage Card, not to the Device which is the default when installing cabs. It's best if you don't have an Android folder to start with. Each build should have a meaningful name which will be renamed to Android if required, however the original name will appear in the menu, not Android. I found a problem when reinstalling because of the Droid.ini files that were created on the first install but don't think that is your problem. I have now fixed v2.02 to delete all Droid.ini files whenever a setup of builds is done, whether on initial setup or when Enable builds is selected from the setup menu. Sent PM with new link.
Pop45398 said:
After install was there a RunDroid folder in the root of your SD card? When running the .cab file you must select to install to Storage Card, not to the Device which is the default when installing cabs. It's best if you don't have an Android folder to start with. Each build should have a meaningful name which will be renamed to Android if required, however the original name will appear in the menu, not Android. I found a problem when reinstalling because of the Droid.ini files that were created on the first install but don't think that is your problem. I have now fixed v2.02 to delete all Droid.ini files whenever a setup of builds is done, whether on initial setup or when Enable builds is selected from the setup menu. Sent PM with new link.
Click to expand...
Click to collapse
Thanks man ,will try out now .And give feedback . Will hit the thanks button tomorrow. Finish used already .
Edit: It works ! thanks .
Hi,
I've got problem with the multiwindow mod from bala_gamer ( http://forum.xda-developers.com/showthread.php?t=1995697&page=56 )
I'm on 4.1.2, MA2, so I choose the last file (multi v10.zip), and I flash it with CWM.
But after reboot, I didn't have any changes.. There are the same app in the multi-window menu..
What could probably be wrong in my way to do ?
Busybox is installed, my GS3 is rooted with a stock ROM.
Thanks in advance to my saver
Here is how you can add apps into the multi window tray;
-search for the multi window control app in your app drawer.
-open the app.
-click on the "add applications" tab.
-click on "add an application" at the top of the menu that appears. A list of all the apps installed then appears after which you can click on the app you want to add to the multiwindow.
-repeat step 4 for all apps you want added to the multiwindow.
-Press the back button once you are done adding your preferred apps. A pop up stating that settings for the multiwindow bar have changed comes up. click on kill it!
-Now open the multiwindow bar and click on edit. You will find all your added apps on the right side.
-to customize the bar, press and hold an app and drag and drop it into the tray.
-Enjoy.
Hey gesbon!
Thanks for your rapid answer !
I remember seeing an app for the multi-window function... but I didn't find it anymore..
How can this be possible ?
The flash of the multi10.zip may be the cause ?
I finally found !
I had to delete the FlashBarService.odex file in the /system/app/ folder, because I'm not on a deodexed ROM !
So it's working !
...but bad: I've got a lot of applications and I can only add the first one (on the first page, before scrolling) to the flashbar.
If i want an app on the next page, I have to add the first application then remove them (they go to the bottom of the list of apps)...
Q&A for BLU 23... Hike OS for BLU Studio 5.3ii
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for BLU 23... Hike OS for BLU Studio 5.3ii. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Updated HikeOS 4.2 for BLU Sudio 5.3.ii
kevinoliva113 said:
Standard Disclaimer: It's your phone.. If you brick your phone, or it becomes self aware and takes over the world, I am not responsible.
THIS IS HikeOS 4.2 PORTED FOR BLU Studio 5.3.ii
This is the most dynamic looking ROM I have seen for MT devices. The screen looks like it is HD.
I used HikeOS from SuperDragonPT.. Please visit him here http://forum.xda-developers.com/showthread.php?t=2617363 and give him a thanks.
Features
Deodexed
Setup menu
build.prop tweaks (ring and 3g speed improvements)
SuperDragonPT Features
Aroma installer
Gravity Box
Additional build.prop speed tweaks
Known Issues
GPS is spotty.. (but so is the stock blu rom)
Beauty setting on camera causes fc. So does video. ( You can download cameraMX for video) Or any other recorder you like.
DO NOT ATTEMPT TO USE QUICK SETTINGS THROUGH GRAVITY BOX. YOU WILL JUST BOOTLOOP ON REBOOT.
I will tell you how to enable through phone
Download Link: https://drive.google.com/file/d/0BzpfAdALNa_gbEJ4a29TYnJDQmc/edit?usp=sharing
Installation Instructions:
ALWAYS DO A BACKUP PRIOR TO FLASHING THIS, OR ANYTHING ELSE
1)wipe data/factory reset
2)wipe cache partition
3) Flash will begin Aroma. Go through Aroma. Will automatically Reboot upon completion.
If you want Quick settings:
Open Gravity box> Status bar tweaks> QuickSettings management> Turn off.
Then pull down status bar> shortcut menu(bottom right)>More>Quick pulldown.
Select which side you want then reboot.
Enjoy!!
Click to expand...
Click to collapse
Kevin, Many thanks for providing not just one custom ROM for this phone but three!
I have choosen your HikeOS 4.2 as my favorite and here are some changes I have made:
1. I have added Email.apk, GalleryGoogle.apk and libcameracustom.so to get Email and working AutoFocus and non-crashing camera from a similar phone custom rom: HikeOS_JY-G3_Android_4.2.1_V3
2. Added Barcode Scanner from market to demonstate working AutoFocus.
3. Replaced bootanimation.zip with one that I like.
4. Removed GPS Status. The YGPS system apk that is designed for this phone gives faster locks. To get easy access to YGPS I have included QuickShortcutMaker and xShortcut free from market. First create a shortcut for YGPS with QuickShortcutMaker then create another shortcut for YGPS with xShortcut free with its Capture Shortcut mode. The xShortcut allows the YGPS run in back ground mode to work.
5. Added MT GPS from market to manually download EPO files every couple of weeks. I use the GPS EPO assistance mode for faster first time locks. I disable A-GPS mode to not use my mobile data.
6. I have modified SunBeam.apk to a Lockscreen wallpaper I like. To use launch Hike Themes and select Themes Style on the left with the Clock and apply.
7. For changable Lockscreen wallpaper I have moved theme SunBeam.apk from sytem to data/app directory to allow easy updating with APK editor that I have included from market. With APK editor "Select Apk from App" and scroll all the way to the bottom and select com.hike.them.SunBeam. Select "Resource". Select "drawable-hdpi" and scroll all the way to the bottom and select lock_wallpaper.png and replace with any 540 x 960 png or jpg file you want. Select Save then exit app. Your installable apk is in ApkEditor directory on your SD card. No need to reapply the Theme your change will take effect after installing.
Here is the link to the altered ROM:
https://docs.google.com/file/d/0B4DmlgCfG8vLdldNT3laT195VDA/edit
tswisher said:
Kevin, Many thanks for providing not just one custom ROM for this phone but three!
I have choosen your HikeOS 4.2 as my favorite and here are some changes I have made:
1. I have added Email.apk, GalleryGoogle.apk and libcameracustom.so to get Email and working AutoFocus and non-crashing camera from a similar phone custom rom: HikeOS_JY-G3_Android_4.2.1_V3
2. Added Barcode Scanner from market to demonstate working AutoFocus.
3. Replaced bootanimation.zip with one that I like.
4. Removed GPS Status. The YGPS system apk that is designed for this phone gives faster locks. To get easy access to YGPS I have included QuickShortcutMaker and xShortcut free from market. First create a shortcut for YGPS with QuickShortcutMaker then create another shortcut for YGPS with xShortcut free with its Capture Shortcut mode. The xShortcut allows the YGPS run in back ground mode to work.
5. Added MT GPS from market to manually download EPO files every couple of weeks. I use the GPS EPO assistance mode for faster first time locks. I disable A-GPS mode to not use my mobile data.
6. I have modified SunBeam.apk to a Lockscreen wallpaper I like. To use launch Hike Themes and select Themes Style on the left with the Clock and apply.
7. For changable Lockscreen wallpaper I have moved theme SunBeam.apk from sytem to data/app directory to allow easy updating with APK editor that I have included from market. With APK editor "Select Apk from App" and scroll all the way to the bottom and select com.hike.them.SunBeam. Select "Resource". Select "drawable-hdpi" and scroll all the way to the bottom and select lock_wallpaper.png and replace with any 540 x 960 png or jpg file you want. Select Save then exit app. Your installable apk is in ApkEditor directory on your SD card. No need to reapply the Theme your change will take effect after installing.
Here is the link to the altered ROM:
https://docs.google.com/file/d/0B4DmlgCfG8vLdldNT3laT195VDA/edit
Click to expand...
Click to collapse
Wow!!! You put a lot of work into that. Great job.
Sent from my SM-N910P using XDA Free mobile app
Additional info
kevinoliva113 said:
Wow!!! You put a lot of work into that. Great job.
Sent from my SM-N910P using XDA Free mobile app
Click to expand...
Click to collapse
Thanks.
The YGPS shortcuts and MT GPS should work for any MediaTek MT6577 phone.
The LockScreen wallpaper method should work for any HikeOS that has the same BootLoop issue or that has disabled the custom wallpapers for the lockscreen.
The libcameracustom.so is a recommended AutoFocus fix for any MediaTek custom rom when the auto focus is not working.
I've seen a few people asking about this and decided to play at doing it. After some messing around I've found the following method to work.
First off, you must be rooted. I don't know away around this.
Secondly you will need to download the two files I have linked in this thread and place them in folders of the same name (DO NOT INSTALL THE ACTUAL APKS).
Third, navigate to system > app folder and copy the two folders called "Weather2017" and "WeatherWidget2017" and move them somewhere else.
After moving the 2017 folders replace them with the 2016 folders and reboot
Once you have rebooted navigate back to system > app folder, remove 2016 folders and place the 2017 folders back as they were and reboot again.
When your phone boots back up now you should have access to place the default S8/S8+ weather widget on your screen while using your launcher of choice (I've tested it using Nova but I think it should work with others).
If this helps you please feel free to leave a like!
Eh im not rooted and i can set the default weather widget just fine in nova launcher ?
This is a Pixel Launcher mod. An ADB Installer until TWRP is ready. Nothing fancy, just a few simple options. You can change app drawer background-text color (separately for light mode and dark mode), remove weather (at a glance) from Launcher. Change the number of hot seat icons on home page (and size) as well as change the number of columns-rows in the app drawer.
Root required
Instructions.
1. Unzip ADB Mods Installer Files.zip on your PC
2. ADB debugging Enabled
3. Run TulsadiverModsInstaller.bat (Give ADB Root Permissions)
4. Flash one of the Bases First. They provide the necessary smali files and public ID's for everything to work. Low-medium-high refer to how high the hotseat icons reside on the home page.
5. Go through the other options selecting what all mods you want. It is generally best to start at the top and work your way down.
6. Once finished with selections, run "Complete Installation" at the bottom. This will generate your mymagisklauncher.zip module in a folder called "ozop" on your sdcard.
Android 11 uploaded 6-13-21
NexusLauncherReleaseADBPixel4XL.zip | by Tulsadiver for Pixel
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
-------------------------------------------------
If I helped, hit the Thanks Button!
Feeling generous, send me a beer!
--------------------------------------------------
Tulsadiver said:
This is a Pixel Launcher mod. An ADB Installer until TWRP is ready. Nothing fancy, just a few simple options. You can change app drawer background-text color (separately for light mode and dark mode), remove weather (at a glance) from Launcher. Change the number of hot seat icons on home page (and size) as well as change the number of columns-rows in the app drawer.
Root required
Instructions.
1. Unzip ADB Mods Installer Files.zip on your PC
2. ADB debugging Enabled
3. Run TulsadiverModsInstaller.bat (Give ADB Root Permissions)
4. Flash one of the Bases First. They provide the necessary smali files and public ID's for everything to work. Low-medium-high refer to how high the hotseat icons reside on the home page.
5. Go through the other options selecting what all mods you want. It is generally best to start at the top and work your way down.
6. Once finished with selecti, run "Complete Installation" at the bottom. This will generate your mymagisklauncher.zip module in a folder called "ozop" on your sdcard.
Android 11 uploaded 9-16-20
https://www.androidfilehost.com/?fid=8889791610682936558
Click to expand...
Click to collapse
EDIT NVM
Tulsadiver said:
This is a Pixel Launcher mod. An ADB Installer until TWRP is ready. Nothing fancy, just a few simple options. You can change app drawer background-text color (separately for light mode and dark mode), remove weather (at a glance) from Launcher. Change the number of hot seat icons on home page (and size) as well as change the number of columns-rows in the app drawer.
Root required
Instructions.
1. Unzip ADB Mods Installer Files.zip on your PC
2. ADB debugging Enabled
3. Run TulsadiverModsInstaller.bat (Give ADB Root Permissions)
4. Flash one of the Bases First. They provide the necessary smali files and public ID's for everything to work. Low-medium-high refer to how high the hotseat icons reside on the home page.
5. Go through the other options selecting what all mods you want. It is generally best to start at the top and work your way down.
6. Once finished with selections, run "Complete Installation" at the bottom. This will generate your mymagisklauncher.zip module in a folder called "ozop" on your sdcard.
Android 11 uploaded 9-16-20
https://www.androidfilehost.com/?fid=8889791610682936558
Click to expand...
Click to collapse
Do you know if it would be possible to mod the launcher to change the default homescreen. Like to be able to swipe left to other pages. Thanks!
jojo1419 said:
Do you know if it would be possible to mod the launcher to change the default homescreen. Like to be able to swipe left to other pages. Thanks!
Click to expand...
Click to collapse
Not possible by me.
Tulsadiver said:
This is a Pixel Launcher mod. An ADB Installer until TWRP is ready. Nothing fancy, just a few simple options. You can change app drawer background-text color (separately for light mode and dark mode), remove weather (at a glance) from Launcher. Change the number of hot seat icons on home page (and size) as well as change the number of columns-rows in the app drawer.
Root required
Instructions.
1. Unzip ADB Mods Installer Files.zip on your PC
2. ADB debugging Enabled
3. Run TulsadiverModsInstaller.bat (Give ADB Root Permissions)
4. Flash one of the Bases First. They provide the necessary smali files and public ID's for everything to work. Low-medium-high refer to how high the hotseat icons reside on the home page.
5. Go through the other options selecting what all mods you want. It is generally best to start at the top and work your way down.
6. Once finished with selections, run "Complete Installation" at the bottom. This will generate your mymagisklauncher.zip module in a folder called "ozop" on your sdcard.
Android 11 uploaded 9-16-20
https://www.androidfilehost.com/?fid=8889791610682936558
-------------------------------------------------
If I helped, hit the Thanks Button!
Feeling generous, send me a beer!
--------------------------------------------------
Click to expand...
Click to collapse
Thanks for the mod...
Getting permission denied....
How to give root permissions on step 3?..
cultofluna said:
Thanks for the mod...
Getting permission denied....
How to give root permissions on step 3?..
Click to expand...
Click to collapse
Check in magisk app and make sure adb shell has root permission. Then start over but unless you are on an old version of android, use this one. If it is just saying something like system not mounted, ignore it.
Tulsadiver said:
Check in magisk app and make sure adb shell has root permission. Then start over but unless you are on an old version of android, use this one. If it is just saying something like system not mounted, ignore it.
Click to expand...
Click to collapse
Im trying this on a12..lol...
But...its working ..thanks
June update has been uploaded.
can we edit app names in app drawer using this?