UPDATED June 25, 2011
Bumblebee ROM 2.4
What's New
------ 6/25/2011 ------
Kernel source: bumblebee-kernel-r26-source.tgz
Code:
MD5 (bumblebee-kernel-r26-source.tgz) = 6fe10367094a0c609b76bc1694d3583a
------ 6/11/2011 ------
To upgrade from Bumblebee 2.3, wipe cache (and only cache) in recovery, then install the Bumblebee 2.4 zip (the install zip tries to wipe cache, but it is not always successful due to limitations in recovery, so it's best to manually wipe cache first then install). See below for more info if installing for the first time or coming from another ROM.
Kernel updates: accelerometer improvements (makes games using it more responsive), swap support, minor tweaks here and there. This is not the major new kernel which I've mentioned that I'm working on. That will be released when it's ready and completely stable, hopefully in a week or so (crossing fingers, but no guarantees).
ROM updates: Newly released update to Superuser (also with fixed signing key so it's upgradable via Market), No Frills CPU Control as a core app, updated core apps and system libraries.
------ 5/23/2011 ------
NOTE: Due to core changes in the system, I recommend a wipe for this update. A pain, I know; sorry about that. If you want to go a little crazy, you can try just wiping cache and dalvik-cache (first boot will still take a few minutes even with this shortcut). However, because the signing has changed on a few system apps, I cannot guarantee that this shortcut will work as the new keys may conflict with keys already stored in /data from a previous install. As always, if you have any issues, do a wipe. So, with that out of the way, on to what's new!
Shiny new Android boot animation (see below for an animated pic). Boot-up takes a few seconds longer, but it's so purdy you won't mind.
New built-in apps: GScript, Terminal emulator, and Text Editor.
Built-in settings updated to include Wifi AP Hotspot. Tether app, which was used to access the Hotspot settings before, is still installed as an easy way to create a desktop shortcut.
"ls" colors are now off by default, due to the Windows cmd.exe not being able to handle ANSI color codes properly when using adb. If you're on Linux, Mac, or another *nix environment, you can use the "lscolors" command to turn them on (it's sticky, you only need to do it once). In an adb shell, type "lscolors on" or "lscolors off" to turn them on or off permanently. You can also do this in the Terminal app on the phone, just be sure to "su" first.
Fixed a signing issue with some pre-installed upgradable apps (like Google Search and Voice Search) that made them non-upgradable. There should be no more issues with this now.
Updated ad-blocking /etc/hosts, and added a fix to the file for certain apps (like sl4a) that try to resolve localhost.
Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Boot Animation
Class 2 sdcard read speed increase
<-before ... after ->
Class 4 sdcard read speed increase
<-before ... after ->
Recommended install order:
Backup current apps and their data with Titanium Backup (available in the Market).
Do a nandroid backup in recovery before doing anything else below.
Required if installing BB 2.x for the first time: Wipe. Wipe it all. Data, cache, system, dalvik-cache, sd-ext if you've got it (might need to look under Advanced or Mounts in recovery to do the last two, and while you're there format /system). If upgrading from BB 2.3, wipe cache (and only cache) in recovery.
If not upgrading from 2.3, install Wiper zip (see below), just to be extra sure that all is wiped. Don't reboot yet.
Install ROM zip (see below).
Optional. If you need the non-overclocked kernel (see below), install it now before rebooting.
Boot into the ROM. w00t!
Download any desired gapps from the Market (Gmail, Maps, Street View, YouTube).
Restore apps with Titanium Backup (not necessary if upgrading, all apps should remain). Do not restore system settings, wifi settings, or anything else except user-installed apps and their data. If you have any issues after restoring apps, launchers and possibly other root or system-related apps may need to be uninstalled and re-installed.
ROM: update_bb_rom_2.4.zip
Code:
MD5 (update_bb_rom_2.4.zip) = b92900a5a095f41702ec2905e9453039
Wiper: update_wiper_1.3.zip
Code:
MD5 (update_wiper_1.3.zip) = 9a72c3b3d108eb8f033637d7b51af027
Recovery: xionia_cwma_12518.4_virgin.zip
Code:
MD5 (xionia_cwma_12518.4_virgin.zip) = 12481185d4234fe4b0af9d8265e86fb0
Kernel-only. Included in ROM. Linked here for the curious. Not guaranteed to work on any other ROM. Contains the two init.d scripts to enable dalvik-cache to /cache and the sdcard speed tweak.
Overclocked kernel:
update_bb_oc_kernel_1.26.zip
Code:
MD5 (update_bb_oc_kernel_1.26.zip) = 746453ee4e91ee1cac43d5429d62a460
Non-overclocked (by default) kernel, for those whose phones can't handle the default overclocking. Can still be overclocked with SetCPU to find the best setting.
update_bb_no-oc_kernel_1.26.zip
Code:
MD5 (update_bb_no-oc_kernel_1.26.zip) = 91251b7dd57c4bba57092642774b3437
I had an idea a little different than just putting up a "donate" button. I also happen to be a composer/pianist. So if you like neo-classical new age, instead of "buying me a beer" with a small donation, why not purchase a couple of tracks from my album Deep Blue Goodbye on Amazon or iTunes, and get something in return that might even last longer than your phone.
-------------------------------------------------
The Bumblebee ROM
-------------------------------------------------
Includes the Bumblebee Kernel (see below). Overclocked to 768 by default with the interactive governor (480 min, 768 max). No need for SetCPU or No Frills CPU Control, but you can use them to overclock even higher and/or set a different governor and range. If you get reboots, back off on the CPU settings, or install the non-overclocked kernel (see above) and gradually increase speed.
Froyo 2.2.1 with lots of tweaks.
TWS 50% bug fixed in Android Framework. This is not an "Airplane Mode Toggle" hack, this is the real deal -- a bug fix in the Android Froyo source. This also fixes the issue where 3G data connection would get stuck after making or receiving a call.
Sdcard Speed Tweak, increases sdcard read speeds by 20% or more.
Dalvik-cache to /cache for 170MB+ free internal memory after a clean install.
Reboot and Recovery options in power button dialog.
"Factory Data Reset" is removed from Settings (it's probably still accessible through an Anycut shortcut if you look for it, but if you're dumb enough to create a shortcut to that, I can't help you. ). Hopefully no more bricks from trying to wipe via the phone Settings. The factory reset was the only option under "Privacy", so you will no longer see "Privacy" on the main Settings screen.
Wifi AP Hotspot settings are available through the main settings screen under Wireless settings. It is fully functional, infrastructure mode. "Tether" app is included to create an easy desktop shortcut.
Extra-purdy boot animation.
AppWidgetPicker included to make choosing widgets easier by grouping them together in the selection menu. Similar to CM-style widget choice.
All Apps and Frameworks deodexed
These Google apps are removed because they are available on the Market: Gmail, Maps, Street View, and YouTube.
GScript, Terminal emulator, and Text Editor included.
Activate app is here, but all other bloatware apps are gone. The Activate app is included to help reset data connection problems for some people with wonky radios. It also happens to be handy for situations where your account lapses or gets canceled and you actually need to re-activate the phone.
Note: When doing a full-wipe install, the Activate app will appear by default on the desktop. If your phone is currently activated with Virgin Mobile, the app will automatically be removed after a second or two. If your phone isn't activated, it will stay until you remove it from the desktop yourself or until your phone is activated.
Removed to save space: Non-english language TTS files; long music ringtones and music alarms (notifications and short alarms are not removed); some internal LG diagnostic sound files. The removed larger-sized ringtones are here. You can put these on the sdcard to save system space. Unzip and install with "adb push media /sdcard/". (TIP: put any ringtones you download into the /sdcard/media/audio/ringtones folder to save memory.)
SuperUser pre-installed (be sure to check the Market for any updates)
Latest versions of TalkBack, KickBack, and SoundBack. TalkBack is available as a keyboard input method. Activate Accessibility->TalkBack, long-press in a text area, select TalkBack. Do the tutorial, it's pretty cool.)
toolbox and busybox (1.18.4)
etc/hosts from mvps.org for free generalized adblocking. This doesn't block admob or apps that use custom adds. Some in-app ads are blocked, e.g. the top banner ads in WeatherBug and a few others, including ads in some games. Most website ads are blocked. YMMV.
init.d support in kernel. Included are two init.d scripts to move dalvik-cache to /cache and an sdcard speed tweak, mentioned above.
e2fsprogs and libs for creatings, checking, and resizing ext2/3/4 partitions. ext2/3/4 support is compiled into the kernel, but these binaries are useful in init.d scripts.
Installing
Don't do a factory data reset from within the phone settings menu. This has caused all kinds of problems with every ROM out there, although it may be related to the recovery you're using. Better to be safe and just don't do it that way. It's been removed from Bumblebee, but it's probably still there in your current ROM. Stay away.
If coming from another ROM, I always recommend a complete wipe. In recovery, wipe data and cache. Then, under "mounts and storage" or "advanced" (depending on your recovery), format boot, system, data, and cache, and wipe Dalvik-Cache if you have that option as well. Lastly, use the Wiper update zip above, which includes it own wipe functionality to be extra wipy. Then install the ROM.
Recommended recovery
I use the Xionia CWMA 1.2518.4 Virgin recovery (note: this is a direct download to the recovery, with flash_image and a short how-to, because the original download in the forums was not working). I find it works fairly well, even though it suffers from incomplete wipes sometimes (they all do). I can't answer questions about installing Bumblebee with other recoveries, so if you have problems, first change to the Xionia CWMA .4 Virgin recovery and try again. (Note: the Xionia 1.2518.6 CWMA recovery in the Optimus S forums is not compiled for the V, only the one linked above is. Some people find .6 works, some don't. I can only say that .4_virgin works for me and .6 didn't.) I also plan on releasing my own recovery with the Bumblebee kernel soon, so stay tuned.
Wiper update zip
This update zip does a full wipe. (Well, technically, it doesn't wipe the sdcard, just /sdcard/.android_secure, and it only cleans up the sd-ext, if you've got one, without formatting it. But just about everything else is wiped pretty good.)
Download the "wiper" update zip listed at the top of the post, and flash with recovery.
Bumblebee ROM update zip
If you don't do a wipe and you have any issues, force closes, etc, do a wipe (again, not a reset from the phone settings menu) and re-install before you report the issue here. Or try the Wiper zip above then re-install.
Download the ROM update zip listed at the top of the post, and flash with recovery.
-------------------------------------------------
The Bumblebee kernel
-------------------------------------------------
Compiled from the official bug-fixed LGVM670_02 source with the following patches and modules:
init.d support. Init scripts should be placed in /system/etc/init.d and are executed in order (convention is to begin the script filename with a 2-digit number so they are executed in numerical order). Note that /sdcard is mounted by the Android init system after the rest of the system has loaded, so init scripts should not attempt to access /sdcard unless mounting it is included in the script.
If you install Link2SD and have created the /system/etc/init.d directory, that app will create a script named 11link2sd to mount the ext2/3 partition. If you don't have an init.d directory, Link2SD will create /system/etc/install-recovery.sh as a place to put it's mount code (not to worry, the install-recovery.sh file doesn't exist in Bumblebee, so it will be empty except for the Link2SD code).
Regardless of the method, if you use Link2SD and you find that it's not working, it may be because Link2SD didn't set permissions properly on the file it created. To fix this, "adb remount", then "adb shell chmod +x /system/etc/init.d/11link2sd" (or /system/etc/install-recovery.sh).
Built-in AP Hotspot enabled
Compiled-in support for ext2/3/4. e2fs binaries and libs included.
Networking modules: tcp congestion avoidance (bic, h-tcp, westwood) and tunneling (ipip and gre)
CPU governors: interactive, conservative, ondemand, userspace, powersave, and performance. Info on most of these is here: SetCPU Documentation
The interactive governor is newer than the SetCPU docs. It is a dynamic governor that scales (if needed) when coming out of idle, instead of polling.
Overclocked. Default on boot is 480-768/interactive, but this can be changed with SetCPU, or the built-in No Fills CPU Control, to any value (valid range is 122-864). Get SetCPU from the market (donate version), or see this thread to download it free for XDA forum members (posted by the dev):
SetCPU for Root Users
Stability at the high-end values depends entirely on individual batches of CPUs. A stable max value for the V can be anywhere from 787 to 824 or higher, it just depends on the unique qualities of the batch your individual CPU came from.
My personal settings are 600-806/interactive and I get great battery life. With the screen off and 3G/wifi set to always be on, I see about 1% drain per hour. There's lots of discussion on the V and S subforums about CPU frequencies and battery life and optimal settings; feel free to browse them for all the interesting findings and info.
What Works
Everything.
Installing
NOTE: If you are installing the ROM, you don't need to download the kernel, it's included. The kernel is here as a separate download for those wishing to just use the kernel with their current ROM.
Download the kernel update zip listed at the top of the post, copy it to your sdcard, and flash with recovery (you can rename it update.zip if your recovery doesn't give you the option of selecting a zip to install).
If you're using a Virgin-based rom, you should generally be fine. If the ROM has replaced any of stock Virgin dynamic-link (*.so) library system files to play happy with their kernel, there may be issues, but that's almost impossible to predict. There are a bunch of those *.so lib files, so to install them all really requires installing a new ROM (like Bumblebee), not just a kernel. However, I've included most of everything that is required for all the hardware to work properly on boot, and if your ROM is mostly stock (e.g. Xionia_VM, Aphrodite, RomidusROM) there shouldn't be any noticeable problems. If the ROM you use has a kernel-less update after you've installed this kernel, you may need to re-install the kernel if any issues crop up.
As-is, the kernel will not work with CM7. I have a kernel install zip that does work, but only 98% (some sensors work, some don't), so I'll release it when it all works 100%.
Note on Key Mapping
Most kernels in the past for the V have been built from the Optimus S source, which reverses the Home and Menu keys due to slight hardware differences. Many of these kernels, and ROMS that use them, have altered the key layout system file to reverse those two keys. The Bumblebee kernel, coming from official source for the Optimus V, has the buttons mapped correctly already. As part of the installation process, it overwrites the existing key layout file with the original key maps, so that people coming from kernels and ROMS that swapped the keys won't find themselves with the keys reversed again. If you use Button Remapper or a similar app to set up other custom key maps, you will need to re-map those keys after installation.
-------------------------------------------------
Themes
I don't believe in ROM themes, so you won't find any here. You can do just about any customization you want with the various launcher replacement apps available in the Market (I'm partial to GO Launcher EX, myself).
Stay tuned for Kernel and ROM updates!
Wonderful!
Sent from my VM670 using Tapatalk
Excellent work. Any plans to put your config and kernel on github? Would be nice to integrate some cyanogenmod settings from CM6 into this!
Sent from my VM670 using XDA Premium App
dammitman said:
Excellent work. Any plans to put your config and kernel on github? Would be nice to integrate some cyanogenmod settings from CM6 into this!
Sent from my VM670 using XDA Premium App
Click to expand...
Click to collapse
I have been thinking about it. My current plans are to try and integrate the latest kernel from the aosp (the VM670 kernel source is 2.6.32.9, the most recent branch in aosp is 2.6.35.7). When I do that, I will put everything up on github.
Excellent description of the build! Thank you very much for very nice work
Can I flash from out-of-the-box-stock? Rooted of course...
Anyone got a black bar ready for this ROM?
slow88lx said:
Can I flash from out-of-the-box-stock? Rooted of course...
Click to expand...
Click to collapse
Yep, you sure can, assuming you have a recovery installed. See the first post for a recommended recovery. For your first flash, I would do the "full-wipe" install, since it will remove the bloatware on your phone. After that you can do the "no wipe" installs to upgrade with new versions.
ok noob here, I followed instructions to the letter and my "v" gets stuck and the droid boot screen...... Any thoughts ? Has that happened to anyone else ?
Can you please use mediafire for files?
It doesn't have the annoying timer.
gringo8831 said:
ok noob here, I followed instructions to the letter and my "v" gets stuck and the droid boot screen...... Any thoughts ? Has that happened to anyone else ?
Click to expand...
Click to collapse
Did you wipe? Which recovery are you using? Did you try the "full wipe" install zip? Were you coming from another ROM, or were you just stock-rooted?
Give me some more info and I can help you figure it out.
ok scratch my last post. I figured it out. Didnt do the delvik wipe and that solved my issue. Hey thanks for for this ROM. Most of the others that are out have problems with the mms not being able to send pix.
How does this compare to CM7 for battery life, speed, and features?
Sent from my LG Optimus V
DustbinK said:
How does this compare to CM7 for battery life, speed, and features?
Sent from my LG Optimus V
Click to expand...
Click to collapse
Battery life is much better. I get less than 1% drain per hour with wifi always on (even when the screen is off) and between 1%-2% per hour with 3G, data and sync always enabled. With normal use, I get a good 18 hours battery life, including phone calls, texts, browsing, videos, etc. With light use, I get over 24 hours. With CM7 I get around 5%-6% drain per hour in complete idle. I got about 10-12 hours with normal use before needing a charge.
Speed is better as well, but this is getting more subjective. The Bumblebee kernel is overclocked out of the box, so that does help. And don't believe the Quadrant scores, they are not accurate at all for CM7 (inflated almost double, sometimes more). There's a thread somewhere about it. Try both ROMS, see which one feels snappier.
As for features, well CM7 is tweaked Gingerbread, and Bumblebee is (mostly) stock Froyo. Also, CM7 has some things like notification-bar power controls that even stock Gingerbread doesn't have. However, bluetooth doesn't work with CM7 for the V, which has always been a deal-breaker for me. If bluetooth is not a big deal, and you can live with the shorter battery life, there's no reason not to use CM7, it's very nice apart from those 2 issues.
Can I use this Kernel with asops? I just installed 2.3.3 with the gApps, and then did the OC Kernel but it wouldn't boot at all. Just hung on the LG logo.
I reflashed again using asops and it is working again, would really like to get this thing OCed though. Any help?
nootered said:
Can I use this Kernel with asops? I just installed 2.3.3 with the gApps, and then did the OC Kernel but it wouldn't boot at all. Just hung on the LG logo.
I reflashed again using asops and it is working again, would really like to get this thing OCed though. Any help?
Click to expand...
Click to collapse
No, the kernel install zip is only for Froyo-based ROMs. I do have a testing kernel install that works 99% with aospCMod, but sensors don't work. It sure feels snappier than the default aospCMod kernel, and I'd love to get it working 100%. If I can figure out the problem with the sensors (and it's not just the sensors.thunderc.so file, or any other .so file as far as I can tell) then I'll post it as an alternative kernel for aospCMod.
Something that is odd, I had your ROM installed with your Kernel as well, and then I installed asops ROM and gApps ROMs. But the OC is still there, and it works perfectly. I have it running at 245-806MHz.
am I able to have conversations with wired headphones, or does this have the same problem as CM7 and it treats ANYTHING in the headphone jack as handsfree
rubyiris said:
am I able to have conversations with wired headphones, or does this have the same problem as CM7 and it treats ANYTHING in the headphone jack as handsfree
Click to expand...
Click to collapse
Wired headphones (and BT) work fine, it does not have the same problems as CM7.
hmm might have to give this rom a try for a while. Not gonna lie I greatly prefer cm7 but I think it needs a lot more polish before it can become my everyday rom (using it right now but it leaves much to be desired).
obijohn said:
...And don't believe the Quadrant scores, they are not accurate at all for CM7 (inflated almost double, sometimes more)...
Click to expand...
Click to collapse
Couldn't agree with you more about Quad scores. It's just a number. I ran a some quads the other day with aospCMod. I was getting an average of about 1100, but I had one that came up 4000+. I know my phone isn't that fast when EVO Shift clocked at 1.8Ghz is getting 3300 on the average. Don't take quad scores as an indicator of speed. If the phone feels fast and is reponsive then that should be good enough. Judge the speed by how it feels, not the score some benchmark gives.
Related
android by polyrhythmic:
Eclair 2.1 for Kaiser/Vogue/Polaris -- polymod 2.1 Delta (Final Stable Version)[Based on OpenEclair 1.3.0.1 (XDA thread)]
Please see polyrhythmics thread for screenshots
BOTH themes have updated Desire settings icons and QVGA dialer:
NAND install:
This is an beta build! I am not responsible if you brick your phone or a tornado lands in your yard due to flashing to NAND!
How to flash a ROM for Kaiser
Questions? Don't forget to use the search!! Your question has probably been asked and answered before. Also, here's an Android on Kaiser FAQ
What works:
Normal Sleep/Suspend (not hacked!)
Calls/Txt
3G Data/MMS
Wifi
Full GPS with AGPS
Network (Cell-Tower-based) Location (fixed)
Hardware OpenGLES
Google Apps
Google Sync
Exchange Calendar
Facebook
YouTube
OpenEclair 1.3 Upgrades:
Newer AOSP 2.1r1 code
Gallery3D
More Messaging Options, like:
* White-Text-on-Black
More working LiveWallpapers:
* Polar Clock fully working
* Maps
* Spectrum
* VU Meter
* Waveform
* 'Many'
Improved stability & mem management
polymod Upgrades:
Updated RIL
Hacked Market Included
MarketEnabler Now Included
BT & Wifi Updates Included
Wifi Power Level now 'Medium' by default
* Wifi Power Level Updates still work
Fully PNG-optimized, including Phone and Framework
Latest Maps, Voice, and other apps updated
More available space for apps in /data partition
* No more data/app_s for us (not needed)
* Symlinked /system/etc/wifi/wlan.ko to /system/lib/modules for our kernel
Apps included in this build:
Live Wallpapers: Grass, Beziers, Bobs, Polar Clock, Visualizations
Taskiller Free 1.8.1 (no ads + CUSTOM THEMED TASKBAR WIDGET) [Free]
Facebook (full sync working)
Myspace
Car Home
Desk Clock [new!]
YouTube
Powerbar Widget
Genie Widget (a.k.a News and Weather app)
Nav Launcher [Free]
Tetherbot [Free]
GPS Test [Free]
extra terminal tools in bin/xbin: rwsystem, rosystem, nano & more
Voice Dial/Search/Keyboard
Speakerphone
YouTube HQ
'Reboot'
Skin information & credits:
* Light Tray Launcher from gChrome by Moonspoon (link)
* Dark Tray Launcher from Gloss by Moonspoon
* Dark Theme Colored Notification Icons from Zapote21's Zapmix 0.95
* Black Notification Bar and Notification Tray Handle from OpenEclair MetaMorph put together by JAguirre1231 (link)
* custom wallpaper, robot from (link)
* custom dark-themed taskiller bar
Thanks to Polyrhythmic for his support and permission to continue to provide this build. Polyrhythmic's Original thread, Thanks also to Kallt_Kaffe for the use of his custom kernel which I have included in the download.
Zenity's Changes:
Integrated Camera update : Camera often FC's in Haret installs due to excessive startup times
Integrated Cell tower location and pin verification
Added dark themed build
Removed the following expired apps;
Astro
maps
facebook
nav launcher
(all these apps are available in Market)
For Nand users, NBH is set for panel2, 320x428 @ 143 density, use rogue tools to change density, if you prefer another resolution or if you need a different panel type you will have to edit the nbh using Loserskaters NBH Editor, and reflash it.
For advanced users: You can edit the NBH to reduce the system partition using the NBH editor, I suggest 82Mb minimum for /system, this will give more space on /data.
Light Themed Version: http://rapidshare.com/files/414148706/Final.zip (MD5: 3A6F15C2AF27048A4DF7AFB95C951DAD) (3156)
Dark Themed Version: http://rapidshare.com/files/414221873/Final-dark.zip.html (1829)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Created another Romantically Apocalyptic themed Splash screen exclusively for Polymod, download, rename as kaisimg.nbh, put on SD, flash, enjoy : Polymod/Zenity Bootsplash (16)
Having been asked about Donations, I would like to request that anyone wishing to should donate to Polyrhythmic, it is his build, I am only maintaining it.
(Note: the numbers in brackets following the download links are an infrequently updated download count)
Installation instructions.
Nand:
You must have HardSPL installed, recommended minimum version 3.29.
Recommended Radio version 1.65 or above.
MicroSD card must be formatted Fat32.
Download whichever themed version you prefer.
Unzip the downloaded file to a suitable temporary folder, then copy everything to SD card root.
You will now have an SD card with one file on root,(KAISimg.nbh), and one folder,(andboot), place this SD in your device and flash the NBH using bootloader method, ( if you are unsure of how to do this please read through Dukenukemx's excellent guide: http://forum.xda-developers.com/showthread.php?t=680518).
Once you have flashed the device you must remove the battery, then replace it and power on, once you have the scrolling text press and hold the centre of the lcd screen until you get the install menu, ( you can also use dpad centre button, or volume up button ).
Once in the installer menu check that sys on nand, data on nand are starred, then choose option 1: install (yes, you know you will wipe your present system, yes, you want to clear data).
Once the installer finishes choose quit, and wait until the initial boot completes, ( this will take a little time, but once you see the boot animation everything is going well).
This next stage is important, please read carefully, or your system will likely be unstable.
Once you reach the welcome screen, press the android, skip the intro, skip the sign in, press next to both the following screens, and once this is complete, wait, for at least 15 minutes, with this build ,(as with most deodexed builds), it is important not to dive in and mess with things, the system needs time to copy the odex files to cache, if you interrupt this you could get a load of fc's, and most likely have to reinstall.
Once you have completed the waiting stage, you are usually best to power down, and reboot, your system should now be ready to begin using.
Initial setup:
This is common to both haret and nand installs, and is my usual procedure with most android roms, it should help with both battery life and speed.
In settings;
In Sound and Display, uncheck Orientation.
Set animations to Some. (you may wish to leave this at All).
Add google account.
In Spare Parts;
Set Window and Transition animations to Fast.
Check Home app in memory.
Advanced options: These may yield additional performance.
Use either Compcache or Swap, using both may actually slow the system down, you will require an SD card that has been partitioned with a 64Mb swap partition for swap.
Installation Instructions.
Haret/SD:
You must be using at least Windows Mobile 6.1
Recommended radio version is 1.65 or above
MicroSD card must be formatted Fat32 and be at least 2GB
Download whichever themed version you prefer.
Unzip to a temporary folder, then copy the files to SD.
You may delete KAISimg.nbh from SD, it is not required for Haret installs.
Fisrtly you must rename one of the default-device.txt files to default.txt, or alternatively edit the default-device.txt file and save as default.txt.
What you may need to edit/add;
board-htckaiser.panel_type=x, panel type may be 1,2,or 3, it should be apparent on boot is you are using the wrong panel type, the screen may be wrongly coloured, or have odd pixels, streaks etc, reset the device, change this option and run haret.exe again.
mddi.width=240 mddi.height=320 sets the screen resolution, default is 240 320, other common values are 320 428 and 320 480. (see lcd density).
lcd.density this also affects how the display looks, larger values make the everything on screen look smaller, default for 240x320 is 160, 320x428 is 144, 320x480 is 120,
board-kaiser-keypad.atttilt=x sets the keyboard map, 0 is querty US, 1 is at&t Tilt, 2 is Nordic, 3 is azerty, 4 is qwertz.
Once you have edited and saved the default.txt file it is time to install it to SD.
run Haret.exe, once you see the scrolling text, press and hold the lcd screen centre, ( you can also use dpad centre, or volume up keys), until you get into the Installer menu.
Once in installer menu choose option 1: install, and yes, this will wipe any system on SD card that you may have previously installed, it will not wipe WM.
Choose yes to wipe previous system, and data, wait until the installer has finished and returned to the main menu.
Choose quit, and android will continue to boot.
This next stage is important, please read carefully, or your system will likely be unstable.
Once you reach the welcome screen, press the android, skip the intro, skip the sign in, press next to both the following screens, and once this is complete, wait, for at least 15 minutes, with this build ,(as with most deodexed builds), it is important not to dive in and mess with things, the system needs time to copy the odex files to cache, if you interrupt this you could get a load of fc's, and most likely have to reinstall.
Once you have completed the waiting stage, you are usually best to power down, and reboot, your system should now be ready to begin using.
Initial setup:
This is common to both haret and nand installs, and is my usual procedure with most android roms, it should help with both battery life and speed.
In settings;
In Sound and Display, uncheck Orientation.
Set animations to Some. (you may wish to leave this at All).
Add google account.
In Spare Parts;
Set Window and Transition animations to Fast.
Check Home app in memory.
Advanced options: These may yield additional performance.
Use either Compcache or Swap, using both may actually slow the system down, you will require an SD card that has been partitioned with a 64Mb swap partition for swap.
Data ( 3G etc), under Haret: Notice that you may have to start a data connection in Windows Mobile before running Haret.exe, failing to start data May prevent 2/3G data from working correctly under Android.
Sounds like you've got some good things to add to Polymod that it's needed for a long time. Best wishes and have fun with the build!
Always had fun with your build poly, no matter what I tried, I always ended up re-installing it
I know you stated it in the other thread but what are all the changes you did to delta?
and is your download themed like the screenshots (those are gamma I think)...I loved the dark theme.
The first post is pretty much a placeholder at the moment, It will be evolving to reflect the status of 2.1D soon, I am working on the screenshots and changes at the moment and will update the first post as soon as possible.
Delta is now available in both light and dark themes, screenshots will follow soon
Absolutely top notch instruction and ROM.
Far more stable than my previous attempts with other ROM's. Ill be watching this closely.
Thanks a lot zenity.
Thanks, it has always been my favourite build, and just needed some updating to bring it back to life
I only received my Kaiser ( well, TytnII here) on monday. Ive gone through about half this subforum already Every other build I've tried managed to go fine until I put my sim in... then it went south from there....
Will see how it goes with this build once Ive tweaked as per your guide....
Notice your using radio 1.70, not sure about SA, but it is possible that you may get on better with 1.65 series, ( European users certainly do better on this radio), really depends what the actual issue is with the sim card?
Hmmm, maybe you're onto something. I'll give the 1.65 you are running a try...
Well if it's a lot of 'no service' problems, then that may sort it, did for me
Hi zenity!
What is wrong with installing Haret?
Once you select quit, and android continue to boot, system hangs and nothing happens!
Any ideas?
Hmm, I'll look into that, but remember running from haret is slower, and the initial boot does take quite some time, it will appear to hang even on nand for a few minutes before continuing to load, if it does not reach the bootanimation within 5 minutes, then something may be wrong with the haret files, I'll flash WM and check that.
ok
Just for your information - once pressed quit, I wait more than 10 minutes!
Just reflashed to WM, installed, it does take a lot longer than nand, quit, it does appear to hang, but finally went to bootanimation, and is running now, time is under 30 minutes, and that includes the WM reflash, so there are a few things to check.
WM version, must be 6.1 minimum, anything lower and you will get problems, guaranteed.
Try another SD card, remember for haret you need 2Gb minimum, it must be freshly formatted as Fat32, you really will need a lot of free space on the SD, (it is possible on a 1GB, but it will be really tight, and things may fail if there are bad blocks).
Remember if you are copying files to SD through activesync you must remove the usb cable safely, same goes for SD card adaptor, always use safe removal, as not doing this can leave data unwritten, ( safe removal writes any cached data before telling you it is safe to remove).
It is possible that the download is corrupt, you may want to redownload just to be certain, but try reinstalling everything from scratch first.
I have been having problems with anything downloaded from rapidshare lately. all the androidinstall.tgz are unable to open. giving this error...
Code:
gzip: stdin: invalid compressed data--crc error
tar: Child returned status 1
tar: Exiting with failure status due to previous errors
I though this was just my setup but if others are having install problems this may be
a file curruption issue. try re-downloading and see if you can open the androidinstall.tgz
this has been an issue with other builds as well as of lately.
please, make some screens
zenity said:
Well if it's a lot of 'no service' problems, then that may sort it, did for me
Click to expand...
Click to collapse
It wasn't no service, it was just plain locking up only while using the data connection. Wifi works 100% with no lockup. Will try it with the current radio then the new radio and give you soem feedback here.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3.2.1
This build is the exact copy of my RAFDROID HD EXT
the difference is that some parts of the system are "squashed" to give you the possibility to NOT USE any Ext partition for data.
I dont like squashedfs, but someone requested an hd build with some free space on nand (about 50mb) because some one not install a lot of apps and prefer to not use sd ext partition.
This build is mainly for EU HD2 (512mb) users.
If you are an HD 1024mb user really you dont need this, and you can use my main HD build
FEATURES
All the main features of RAFDROID HD EXT plus:
- odexed back to save dalvik cache space
- free user space after first boot: 101mb
- App2SD enabled if you use and SD with an EXT partition
CHANGELOG
Code:
3.2.1 - 3 MAR 11
Fixed Market FC
3.2- 3 MAR11
Some improvements and fixes to radio/audio driver,
this "should" fix phone freeze in some setups, also if I was not able to replicate the issues
Tweaked for more battery life on some sd cards usage
Updated hosts file with last one
3.1 - Initial release
=== INSTALL INSTRUCTIONS (CWR) - NEW USERS WITHOUT CWR INSTALLED OR WITH CWR BUT USING ANOTHER ROM ===
This process will erase everything on your nand. So, if you are already using a previous rom, backup everything!
Download PANASONIC SD FORMATTER and use it to format your card with FULL ERASE
You need to flash MAGDLR 1.13
You need to flash, via USB FLASHER magdlr option, this recovery partition layout, otherwise the build will not boot.
Download the FULL RAFDROID PACKAGE and copy the entire zip (not extracted!) on the SD CARD root.
Put the SD CARD in your phone and power it on and go in the MAGDLR menu (hold the power key while powering up)
Select BOOT AD RECOVERY
Click on INSTALL ZIP FROM SD CARD and then CHOOSE ZIP FROM SD CARD
Select the FULL_RAFDROID_HD*******.zip that you downloaded before.
Select "Yes - Install........" and wait for installation then Go back with power button and select REBOOT SYSTEM NOW
First boot can take up to 20 minutes. If you are stuck on white screen with HTC logo just wait. If you hear boot sound more than one time, you had a bootlop and something has gone wrong. Delete everything, reformat your SD card, read again the instructions and try again.
When you see the lockscreen, give at least 5 minutes to settle. Then do all your settings and then reboot again
Enjoy.
Remember: if you want to avoid Data Corruption always choose SHUT OFF and not reboot!
=== INSTALL INSTRUCTIONS (CWR) - UPGRADING FROM A PREVIOUS RAFDROID VERSION (2.2 or greater) WITH ALREADY CWR INSTALLED===
Since the data storage method is different, you cannot upgrade from a different RAFDROID HD version. You have to install fresh. Anyway you will keep your data and apps installed.
============ CONFIG.TXT ============Used some ideas and code bits from Dandiest's init script.
You can create a config.txt file on the root of your sdcard to configure some things at boot.
Actually you can configure the following options
gps_zone=[your country]
check http://www.pool.ntp.org/zone/@ for country codes (example: it for italy, us for usa.. and so on...)
ppp_mode=[1 or 0]
1 to enable PPP
0 to enable RMNET.
Default is 0
If wince=1 default ppp_mode will be 1
old_light_driver=[1 or 0]
0 to use the new light driver (working notification leds, button backlight control)
1 to use the old light driver (no notifications leds, buttons will go off after 10 seconds)
default is 0
auto_btn_backlight=[1 or 0]
1 to have the buttons backlight going off/on with the screen
0 to have the buttons backlight going off after 10 seconds from when the last button is pressed
default is 1
this work only if old_light_driver=0
wifi_mac_change=[1 or 0]
1 tells the system that you will need to change the wifi mac address to a custom one
0 tells the system that you will use the wifi mac address based on device hardware
custom_wifi_mac=yy:yy:yy:yy:yy:yy
here you have to write the wifi mac address you want.
This is needed, and will work, only if you specify wifi_mac_change=1
If you not write any mac address here, the default 00:11:22:33:44:55 will be used
Just an example on how a file could look:
Code:
gps_zone=it
ppp_mode=0
old_light_driver=0
auto_btn_backlight=1
The init script will also create an init.log file on your sd card at every boot. This will help you and me with debugging if something not works fine. If you have issues please always post your init.log file when reporting your problem.
============ KERNEL ============
You can refer to my kernel thread for updates, changelog, and comments
http://forum.xda-developers.com/showthread.php?t=940823
============ SQUASHED FILE SYSTEM ============
App, Framework and most of Lib folders, are squashed.
Anyway you can push or delete any file from those folder because any file is simlinked.
Example: if you want to use a different framework-res.apk, you can copy it in the /system/framework folder. At this point the simlink will be removed and your new file will be stored on nand, not in the squashed filesystem. This means that more "new files" you push in the squashed folders, less nand space you will have.
Anyway please note that I left only about 13mb free on "system". This means you will not able to push more then 13mb files. If you like to change a lot of things.. this build and squashfs is not for you.
============ DOWNLOADS ============
You need to flash, via USB FLASHER magdlr option, this recovery partition layout, otherwise the build will not boot.
Full Rafdroid HD 3.2 LIGHT SQ
http://hotfile.com/dl/108421743/5bfea5b/full_rafdroid_hd_3r2f1_light_sq.zip.html
MD5: 97018DD4D05FAAFBCC5F9329AEB03F28
SHA1: F6B6D67B90B96E02FCDA70D98836450B6FAE9917
CRC32: 150CCA2B
OLDER VERSIONS:
3.1 : http://www.multiupload.com/X8VBC6WKYV
============ DONATE ============
I made this version just for people that were asking, so if you think this helps you, a small donation for a coffe or a beer, is appreciated. Otherwise a click on the "thanks" button is appreciated too
============ CREDITS AND THANKS ============
Credit to all the people that made all this possible: Cotulla, DFT, darkstone, markinus, danijel, rajko and some one other I'm missing...
Big Thanks to Cass, ocm, darkstone, rajko, crawlingcity, atoore for their help in the last months and to be always available to help
Thanks to all the users who donated and helped me to keep going
Thanks to all the testers and users of my builds that with their reports helped me to solve bugs and issues.
Thanks also to Sergio76, imilka, cmylxgo for the nice talks and knowledge sharing
FAQ
Q: I have low quadrant score
A: This is normal. Nand is slower. Anyway during day usage you shold not notice big difference
Q: I have small freeze when installing apps
A: This happens with all Desire HD builds. I can't do nothing to avoid this
Q: I'm using App2SD but my internal memory keep decreasing at any app installed
A: Go in the application management and move the installed abb back in the phone. Some apps anyway keep some datas in internal mem.
Q: My phone sometimes freeze and I have to reboot.
A: Go in Settings -> Audio -> disable audible touch tones. this will solve the issue in most of the cases.
Q: Can you provide a different link or a mirror different from hotfile?
A: I'm sorry but the answer is "no". I pay hotfile every month and the downloads give me the possibility to pay it. I dont do this for money, but I also dont want to waste my money
Q: During/after boot a window appears with "System process not respoding". What I have to do?
A: This is caused from the new audio driver I used. The new audio driver has better phone stability and no robo voice. You have two choices: 1) Click on "wait" and all will be fine OR 2) download the "old_acdb_file.zip" and flash it via recovery. In this way you will not have the error anymore but you will start having robo voice on first call (you can avoid this disabling audible touch tones) and could happen that your phone freezes when receiving a call. It's your choiche. I preferred the "window error" one because for me is more important to have a working phone than an error window appearing at boot.
Q: I have robo voice when I make a call
A: To avoid this, disable "audible touch tones" from the "settings -> audio" menu. You will have no-more robo voice also if you reboot.
a) During the robo-voice call, enable the speaker, then disable it. You will have no more robo-voice until next reboot.
Q: I have very low audio during calls
A: During the call, enable the speaker, then disable it. You will have loud volume until next reboot.
Q: after boot I see only a white screen with a green htc logo
A: just wait. It can take fro 5 up to 20 minutes depending on your sd card. There are no issue. The build booted fine, it's just copying all the files to SD. This will happen only on first installation.
Q: I'm having high battery drain
A: Try reboot. Try disabling gps in location. As you can see from the screenshot I have 4mA with WIFI active! Also be careful. If during google account setup you choose to backup/restore all your data, the sync process will be dramatic heavy because it has to reinstall all your apps. It could need a couple of hours to settle. Also high battery drain could be caused by SD. try another one.
Q: It's really laggy!!!!
A: as all Desire HD builds this is BIG! This needs at least 10-15 minutes after boot to be usable. Then try to use it for 5-6 hours.. and do a couple of reboots.. you will see that the speed will improve. After 24 hours of use and 4-5 rebots this will be really fast.
Q: I have no GPS or the fix is really slow
A: Firs fixt can take up to 5 minutes. just wait.You can edit the config.txt gps_zone= to your country. See here for the right strings http://www.pool.ntp.org/zone/@ if this not solves, try use QuickGps from the market to download a-gps data.
Q: It not boots
A: partition again and format again your sd card. follow the guide linked in the first post. post your init.log. check that you flashed the custom recovery linked in the instructions.
Q: I have no data/3G/HSDPA
A: probably you have to set your apn manually. google it for tips on how to do and what settings are need for your carrier
Q: How do I remove BOOTSOUND / How do I change bootanim
A: bootsound and bootanim are located in /system/customize/resource
Just delete android_audio.mp3 if you dont want sound
Q: I have wake up lag
A: It's an issue that devs are trying to solve. It's not related to the build itself. In the Q&A Forum there is a thread about this problem.
Q: My screen stays off after call
a) Maybe this can help: http://forum.xda-developers.com/showthread.php?t=946012 ATM very few people have this issue, so I wonder is related to sd card.
Q: My contacts pictures are low res after sync!
A: this is a google problem, read here http://code.google.com/p/android/issues/detail?id=4147
Q: I have random reboots
A: Seems to be related to your phone, read here http://forum.xda-developers.com/showthread.php?t=941845 and here http://forum.xda-developers.com/showthread.php?t=898804
UPDATES:
Instructions:
1. Download your update and copy it to your sd card folder. Dont use MAGDLR mass storage mode because will corrupt your files. Use an sd card reader on your pc or usb mass storage mode in recovery menu
2. Boot into MAGDLR and choose BOOT AD RECOVERY
3. Make a backup! It will save your life if something goes wrong and you want to roll back! You are aware now!
4. Click on INSTALL ZIP FROM SD CARD
5. Click on CHOOSE ZIP FROM SD CARD
6. Select the update zip that you downloaded before
7. Select "Yes - Install........" and wait for installation
8. Go back with power button and select REBOOT SYSTEM NOW
Removed Apps for version 3.X -> http://www.multiupload.com/H5IPNFYBG4
old acdb file (read the faq if you dont know what this is) -> http://www.multiupload.com/AHV0UIKHZF
Stock Framework, only for version 3.X -> http://www.multiupload.com/TVDWWVDNL1
RAFDROID Framework, only for version 3.X -> http://www.multiupload.com/ZC4P6KSKWL
Replacing fonts with standard Desire HD one http://www.multiupload.com/N4VR74W8PK
Replacing fonts with Rafdroid one http://www.multiupload.com/E9UKQBEE4P
If you have issues with flash videos on website, you need an older flash version. Check this post. Thanks to Jayedamina http://forum.xda-developers.com/showpost.php?p=10584806&postcount=280
- maybe I need also this -
First! Nice!
waiting...
are there any advantages on HD2 TMOUS?
rafpigna said:
This build is mainly for EU HD2 (512mb) users.
If you are an HD 1024mb user really you dont need this, and you can use my main HD build
Click to expand...
Click to collapse
I gues not rizky_p
rizky_p said:
are there any advantages on HD2 TMOUS?
Click to expand...
Click to collapse
link is on-line
Thanks, will try
Going to try this tonight, looks good. Any one tried it yet?
Ston said:
Going to try this tonight, looks good. Any one tried it yet?
Click to expand...
Click to collapse
Yep, works a treat
Hello Raf thank you very much for giving us this opportunity, just wondering which files should we use to revert back to stock framework and standard fonts and how to install them.
Thanks again for all your efforts
I always had problem with data on ext partition due to easy file corruption, so I'm trying this...thanks!
thesniffer said:
Hello Raf thank you very much for giving us this opportunity, just wondering which files should we use to revert back to stock framework and standard fonts and how to install them.
Thanks again for all your efforts
Click to expand...
Click to collapse
You can use the update zips from my EXT build.
Very nice and smooth build
But one question: Has anyone tried to change the kernel to Rfp 1.6 or 1.5? I just tried and now the phone is stuck at "gogogo" ...
Intersting
rafpigna said:
You can use the update zips from my EXT build.
Click to expand...
Click to collapse
So via CWM Recovery as i supposed.
Thanks again for your kindness and keep up your valuable work
hi raf
i installed this one(only for proof of concept),works great and i think it is a little faster than the "normal" rafroid,i dont have any lag!!! but 101mb.....very poor...
back to rafroid HD "normal" with d2sd..... i love more space!!!
nice & good release
keep up the good work
cheers!
Hello everyone,
I've compiled a kernel which separates the NAND memory into 3 partitions (well more then that but anyway). These partitions are system, data and cache like a native Android phone (which also has recovery but we don't need that). Previously cache was linked to a directory on the data partition which was constantly becoming corrupt causing errors on start-up. Often clearing dalvik-cache would allow Android to boot but data was lost. There's nothing to say that this will solve the problem but i'm giving it a go so thought I would post it up for you to try also.
The cache partition is 20mb which means the data partition is only 90mb or so. If you like a million apps on your phone either put some on your SD card or don't use it
I haven't completely incorporated this partition into the initrd which means that currently it will only mount if data is also on NAND but this can be changed easily enough, but for testing purposes I want everything on the NAND chip anyway.
Downloads from market on all versions of Android, unless the init.rc directory is changed in Gingerbread, all go to the cache partition and are deleted on restart. What this means is that you can't download and install an app larger then 20mb (which isn't recommended anyway with the small amount of data space available). This is a drawback but for those that use data on SD it should be possible in the future to utilise more of the NAND memory for cache so you can install whatever you want. I don't know of many apps larger then 20mb anyway though.
I have included a modified version of ATools in the zip. The standard version will overwrite the partition values and the kernel won't work properly so if you need to modify the kernel use the version included. It is also important that you DO NOT change the system or data partition sizes in ATools as this hasn't been modified to account for the cache partition so will mess it all up.
I have also included an androidupdate.tar modules update for the kernel in case your wifi doesn't work after flashing the kernel.
I think that's it for now, let me know how it goes!
EDIT::
One last thing, you will need to wipe your DATA partition to use this kernel because some of your data may be positioned where the cache partition is now, so if you load this kernel and android is heavily corrupt you know what you have to do!
To check the kernel is working correctly you can type "df -h" into a terminal and it should show all of the current partitions including one called cache on mtdblock4.
Should now work with polaris, kaiser and vogue. There is a VOGUEIMG.NBH included for those who have trouble with ATools. It is completely untested on Vogue so sorry if it doesn't work.
EDIT
I have re-uploaded a modified kernel because there was some issues with data with the last one. If you have already applied the last one flash the new one and apply the module update again
testing will leave feedback
Ok, using your Scoot CyanogenMod 6.1.2 (RLS6) [16.03.2011], overclock via atools+roguetools to 529, gpu oc, battery units tweaked to suit my battery.
No SIM card yet, don't have one to put there, sync with google to get contacts.
Installed GoLauncher. Enabled JIT and Keep Launcher in memory.
Once in a while, Android is killing all apps, launcher included... strange...
Nevermind that, it was Cyanogen and the LongPress BackKey. LongPress on our Kaisers during lag can become short press
First couple of days of heavy use I've had in ages with no corruption. First day of my new job today so it's been on Google Navigation for 3 hours and used extensively during the day. Had to do a hard reset at one point and everything was fine. had a few soft reset's too. Don't get me wrong, i'd be surprised if this is a fix, but it's been a while since I've used my Kaiser this much and not had to wipe my data partition!
Update: CM is a bit slow, trying:
VaniljEclair RLS11 - A fast & stable CM 5.0.8 for Vogue/Kaiser/Polaris [2010-08-19]
And everyting seems good. I've pushed it a little, several normal reboots.
Had to reflash system (didn't reflash data). No errors, FC's, whatevar. Everything works, yet didn't try to make/receive calls. Its 1am here...
Now this particular version, has a god damn bug that is get the best of me. The Power Button and the red button won't make the phone go to standby. If i long press, i get the normal reboot/power off/airplane etc menu, on both keys. But single press is ignore... Any idea ?
scooter1556 , i have a question. It is not the purpose of the thread or kernel, but how difficult would it be to activate scalling of the cpu ?
Right now, the two 3 biggest issues with Android on the Kaiser are, IMHO, Data corruption, Battery life, performance.
Please share your thoughts
Using this kernel with Valentine 1.02. GPU overclocked and CPU @ 520mhz. Super fast and for the first time... no data corruption! Verry happy so far!
daedric said:
scooter1556 , i have a question. It is not the purpose of the thread or kernel, but how difficult would it be to activate scalling of the cpu ?
Right now, the two 3 biggest issues with Android on the Kaiser are, IMHO, Data corruption, Battery life, performance.
Please share your thoughts
Click to expand...
Click to collapse
Well in theory not too hard, there is a feature built into the linux kernel called cpufreq which is currently disabled in our kernel because our cpu and chipset code doesn't support it but krazy-killa has been working on getting it working in his kernels with a little success as far as i'm aware but i'm not that sure. I haven't personally looked into it but if I get some spare time I definitely will. I've started a new job now which i'm sure will keep me quite busy but I still intend to so some work on the Kaiser when I get time
Best of luck on your new job! I wish i had enough knowledge to continue the kernel development, but i'm quite a ignorant
Still, thank you, till now it's one of the best kernels i've used.
Hi Scoot!
I love your kernel. No data corruption so far (two days). did a few stylus resets and stuff.. Magical =D. Now IMO we only need better sleeping and autofocus to call kaiser a fully android device! Please Keep up the awesome job, scoot! thanx, danke, sposeeba, bedankt, aciu, dzenkuja!
Nice job scooter, I've been using Scoot CyanogenMod 7.0.2 RLS2 [28/04/11] @ 500MHz, and it seems fine so far.
I tried Fat Free Froyo before CyanogenMod, which also worked great for the few hours it was running. I'm not sure which one to stick with though.
Keep up the good work. I wish I could help with the development, but I have yet to learn programming (been ten years now ).
This kernel looks pretty stable, but just a few quick questions:
1) What filesystem is used for the cache? If YAFFS, could it get corrupted? If Yes, what would happend then?
2) Is it really needed to have 20MB for the cache? ATM it seems to be used only by a like 1-2MB on the cache partition, would not it be enough to have for example 10MB for the cache leaving more space for apps?
3) What is the difference using apps in the system and data partitions? If I would run off the space on the data partition, can I put some apps in the system apps folder to save the space without wandering about how it works?
Thanx for your great work, finally it seems to be fully usable for me and if you and Krazy-Killa would be able to work together to manage the power consumption, then it would be amazing, because I am going to get new phone (running some new extensive business and I can not afford to be not reachable when something happends on Kaiser) and give this lovely piece of HW to my son... And I really do not want him to have a WM machine But Android needs to be stable for him to use Well... he will get it for his 10th birthday at 6.9. so we still have some time to tweak it a bit more
if this works then it would be magical, your CM builds were so fast and awesome and if there's no data loss then... <3
Made 2 mistakes when building kernel (selected tilt instead of normal and forgot to OC to 480MHz), and running kingshui's 12/15/2010 build 2.2.1. seems ROCK solid and fast! I applaud your use of ramzswap for the extra 20mb, bravo!
I'm just hoping I can go back and rebuild the kernel with the correct settings without messing up the system/data/cache partitioning.
PoXFreak said:
Made 2 mistakes when building kernel (selected tilt instead of normal and forgot to OC to 480MHz), and running kingshui's 12/15/2010 build 2.2.1. seems ROCK solid and fast! I applaud your use of ramzswap for the extra 20mb, bravo!
I'm just hoping I can go back and rebuild the kernel with the correct settings without messing up the system/data/cache partitioning.
Click to expand...
Click to collapse
They aren't mistakes, those are the settings I need for my Kaiser. I included a modified version of ATools for you all to modify the kernel for your devices as I stated in the first post
a.s.j said:
1) What filesystem is used for the cache? If YAFFS, could it get corrupted? If Yes, what would happend then?
2) Is it really needed to have 20MB for the cache? ATM it seems to be used only by a like 1-2MB on the cache partition, would not it be enough to have for example 10MB for the cache leaving more space for apps?
3) What is the difference using apps in the system and data partitions? If I would run off the space on the data partition, can I put some apps in the system apps folder to save the space without wandering about how it works?
Click to expand...
Click to collapse
1) The cache partition is still using Yaffs2 because it is the easiest filesystem to configure at the minute, but the idea of making it a separate partition like on a native android device is that it can be changed to another filesystem in the initrd relatively easily. If it gets corrupted it will do what it used to I guess, but I haven't had any corruption as of yet so it's difficult to say. Hopefully if the cache partition get's corrupted it shouldn't affect data so you should just be able to wipe and format dalvik-cache in the install menu.
2) I made it 20mb because most android devices have 30mb or bigger and this is mainly because market app downloaded get downloaded here before being installed, so if you installed google maps for instance it would use up 6mb, plus the standard 1-2mb normally being used, but if you only had a 10mb cache for instance, you would only be able to install apps less then 8mb which is a little limiting really. I don't really care much about installing lots of apps in data or on the phone at all for that matter so having 95mb for data is more then enough for me.
3) You can put apps in the system partition in /system/app. The system partition is read only so all data for the app still goes to the data partition. You can still save a little data partition space though if you need it. Most installs of android are 80-95mb which should leave you 5mb or so to play with. Some all language builds pretty much use up all of the partition though so you need to look and see what space you have to play with before putting apps on the system partition. If you overload it you will probably end up corrupting it and having to reinstall. But to answer your last question, the system partition works in the same way as the data partition apart fro the fact that it is read-only and data is read/write.
I've modified my Kernel to use the NAND mtdblock3 (/data for everyone else) as the cache partition, since my NAND is pretty much shot to begin with, and have system and data on SD Card. So far it's made downloading Market Apps twice as fast, loading webpages pretty fast, and basically anything else that the cache is used for.
scooter1556 said:
They aren't mistakes, those are the settings I need for my Kaiser. I included a modified version of ATools for you all to modify the kernel for your devices as I stated in the first post
Click to expand...
Click to collapse
Scoot:
I understand that the settings built into the .nbh are for your device. What I was meaning was I needed to modify the CPU clock up to 480MHz, and for some odd reason my device swaps the "@" and "!" buttons if I set it to "tilt", among other buttons being set wrong.
Also, I am used to having the left and right softkeys set as "vol up" and "vol down" respectively. Is this something I need to make an androidupdate for, or do I have to write a new NBH?
PoXFreak said:
Scoot:
I understand that the settings built into the .nbh are for your device. What I was meaning was I needed to modify the CPU clock up to 480MHz, and for some odd reason my device swaps the "@" and "!" buttons if I set it to "tilt", among other buttons being set wrong.
Also, I am used to having the left and right softkeys set as "vol up" and "vol down" respectively. Is this something I need to make an androidupdate for, or do I have to write a new NBH?
Click to expand...
Click to collapse
Can you not do all of this using the ATools i provided in the attachment in the first post? You should be able to load the nbh into ATools and then set the CPU speed, change the keyboard type and remap the buttons and then save it before flashing. Just don't change the partition sizes as this will mess up the cache partition I added until I make it more permanent.
4EXT Recovery Classic v2.2.7 RC5 | STAY @EXT4 | Convert FS | Rom -> Backupname | ..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Quick note about themes:
Available themes as of Oct/18:
Themes by [URL="https://forum.xda-developers.com/member.php?u="]GuestK00388[/URL]
Themes by Apaquette420
Themes by Whiskey103
Themes by Amresh
Themes by Apaquette420
Themes by CWhitney24
Themes by DaMyth
Themes by Blindndumb
To uninstall any "flashed theme" and to revert to your own custom settings you had before flashing, just use this Theme Uninstaller in recovery.
It will clear any theme you might have flashed and revert to your own custom settings you had before flashing that theme!
THANKS:
All credits and my deepest respect go to Koush for his extremely great code!
Without him 4EXT Recovery wouldn't have been possible!
Biggest thanks possible go to Sebastiaan15 for his brilliant ideas and who spent whole weeks testing my buggy code with his Desire
Without you I could never have made it!!!
So BIG THANKS to SEBASTIAAN15 and KOUSH for his hard work with CWMR !!!
Many credits to the Desire S community ( especially to loveboatcaptain - LBC Mod Android Development and Marylandcookie ) for testing, very nice ideas, feature suggestions and helping to get the code running on the Desire S!
Special big thanks to RAVENNA from android-hilfe.de board for hours of testing for the Desire!
BIG Thanks to Hussainmushahid who helped me a lot spending much of time with solving a bug I could not reproduce on my device.
And many thanks to all users who reported and helped to identify problems ( can't any longer list all of you here since the list has grown too large )!
Even more thanks to people who 've bought me some beer YOU ROCK!! ZEEKIZ, A USER, PHILOS64, STEVEATHOME, PREACHER65, BEN_PYETT, ULTRA DROID, PTR_HAMILTON, BEANBEAN50, SEBASTIAAN15 and LOVEBOATCAPTAIN
v2.2.6 RC4 Released: Oct/01
Rare Superuser problem when tar backups were enabled (disabled by default) was fixed.
Converting partitions between ext3 and ext4 without data loss now correctly calculates the space needed to successfully complete the operation
New option: check and optionally repair the file system on your sdcard (fat32)
Removed duplicate format cache option inside the format menu (wipe cache does the same)
When formatting fat32 it will now save your 4ext.prop settings and restore them afterwards
Changed partitioning of the sdcard to not use LBA mode for new fat32 partitions as requested by Ghiki
Added new size option (128mb) to the partitioning menu per request
Parted is no longer used to format fat32 in the partition menu-> This solves a bug where sometimes the creation of the fat32 file system failed and produces better quality results
4EXT Recovery themes should now stay when formatting /system or flashing new roms
New option: format /sdcard fat32
New 4EXT Recovery Control API because I'm forced to drop "extendedcommand" (see App for the reason why)enables file names and directories to include spaces for installations
calculates needed space to complete a full or advanced backup at the beginning of the backup.
This ensures that you are not left with a non working backup.
Size for recovery greatly reduced
New 4EXT Recovery Control Features
Please see www.4ext.net for more.
Fix permissions
Calculate real values for the space needed to create a new full or advanced backup
Advanced Backups: While you are selecting / deselecting partitions, it will display and update the currently needed space to complete that custom backup set.
As an example, the following would be possible to do in just one session: Restore a backup, set to create a backup / advanced backup before the restore,
format all partitions with a file system of your choice before the restore process starts,
flash additional zip files afterwards, fix permissions and select to stay inside recovery or to reboot automatically once all actions are complete.
Features: Use 4EXT Recovery Control or Recovery Updater for complete Changelogs and Known issues!
not all features may be relevant for all devices
Displays additional information:
Identifies your current rom and displays its name
Current filesystems on your partitions
Free space remaining of all of your volumes
Current battery charge level
Backup | Restore:
Correctly calculates free space needed to complete a backup ( version > 2.2.6 RC4 )
Tar backups (can be switched on or off)
Complete CWMR5 compatibility
All Backups you create will be named after your currently installed Rom for easier identification.
Never unwillingly get "downgraded" to EXT3 again
Always restores backups using the file systems you HAD on your partitions at the time of creation!-> all partitions formatted with ext4 at that time, will be restored to ext4. The same is true for ext3.
You can manually change any existing Backup to ext4 or ext3-> so that after a restore, all partitions and up with the file system you wanted!
Advanced Backup: backup only a single partition
Convert any of your partitions to EXT4 or EXT3 without data loss.
Formatting:
When you wipe or format it will always use the same file system you currently have.-> but you can change that
When you format ext4 it will always create an aligned file system
Correctly identifies unformatted sd-ext partitions-> if it finds one it displays a warning and suggests you may format them by visiting the 4EXT menu
Filesystem check and repair option in advanced menu
Partitioning:
Alignment check of your partitions
Full support for up to 2 sd-ext partitions + swap (Backup/restore/format/convert, fsck, et.c.)
(RE-) Partition your sdcard for sd-ext without removing your fat32 partition.
All partitions created with 4EXTRecovery will be perfectly aligned to 4k
Installing:
Integrated md5sum checking option
Themes:
Customize all colours used throughout recovery
Use your own icons, background images, progress bars.. more to come.
Assign different backgrounds to different menu categories (version >= 2.1.2)
Create a flashable zip for others to flash your theme.
Menus:
Most popular menu items rearranged
Format menu
Power Menu + option to reboot into bootloader
Less "No's" in confirmation dialogues
Changed Advanced Restore: first select what you want to restore, then select the backup-> Useful for restoring from "Advanced Backups"
4ext.prop:
Configuration file on your sdcard where you can set options to be used by 4EXTRecovery
Change all settings conveniently with 4EXT Recovery Control
Many more options to come
Share your settings / themes by packing your config into a flashable theme
Other stuff:
USB Storage Autostart (must be switched on)
Mount usb storage exposes all partitions on your sdcard to the os (not just fat32)-> you could even partition your sdcard from your PC while connected via USB
Switch haptic feedback on/off
You don't need to reboot recovery if you transferred a file to show up in the install menu.-> This bug affected only some users with either CWMR or previous versions of 4EXT.
Button backlights (Desire S, Desire HD and Incredible S only)
Download:
All downloads are now available through 4EXT Recovery Updater. It's free, no ads, no tracking, no nothing, don't worry
.. and of course via 4EXT Recovery Control
This ensures that your downloads are ok by automatically verifying md5sums and that known issues and changelogs are easily accessible
It also notifies you when there are any new critical bugs found
Recovery images will be uploaded for download soon too, but they can also be acquired easily by using Updater or Control.
You can for example just download a recovery.zip containing the image. The download will be automatically verified for correct md5sums!
4EXT Recovery Control
Free version: Recovery Updater
Fully featured version: 4EXT Recovery Control
For a list of its many features, visit www.4ext.net
Some examples :
Flash as many zip files you want in one go
Automatically calculate and display the md5sums of all zip files you are going to flash
Check your backups' health to ensure they will restore later when you need them, by verifying their md5sums!
Optionally, but highly not recommended:If md5sums don't match but you REALLY NEED that backup BADLY, you might want to restore it anyway.
You can you this app to fix the md5sums of a given backup to "forcefully" restore it!
Calculate real values for the space needed to create a new full or advanced backup
Advanced Backups: While you are selecting / deselecting partitions, it will display and update the currently needed space to complete that custom backup set.
Identifies and adds your romname so you don't need to type so much when chosing a meaningful name for your backup
As an example, the following is possible to do in just one session: Restore a backup, set to create a backup / advanced backup before the restore,
format all partitions with a file system of your choice before the restore process starts,
flash additional zip files afterwards, fix permissions and select to stay inside recovery or to reboot automatically once all actions are complete.
Much, much more! See www.4ext.net
Recovery theming
Uninstall and Install themes with live preview and the option to change their colours without the need to reboot into recovery.
Change all colours with live preview and a nice colour picker.
Working great on my dinc2 this is the one thing i missed since switching from the inspire and now i have it back. Thanks max!
Sent from my Incredible 2 using xda premium
oxlong27 said:
Working great on my dinc2 this is the one thing i missed since switching from the inspire and now i have it back. Thanks max!
Sent from my Incredible 2 using xda premium
Click to expand...
Click to collapse
Thank you very much for that!
And for jumping into the cold water for me
If it booted up fine it's alright and I can remove the warning. Everything else is just like on the IS.
---------- Post added at 01:09 AM ---------- Previous post was at 12:48 AM ----------
Added 2.1.1 Final, but that version is really old.
I'd try the latest first. It has been extensively tested and issues if any should only be minor.
Yep everything i tried is working as it should. Havent tested the formatting yet but im sure its fine everything else works. And as far as trying something thats untested, well thats what xda is about, if you dont get a soft brick here and there your not having any fun. But yes this works fine thanks again
Sent from my Incredible 2 using xda premium
I gave it a go and seems to be working just as it should. Was jealous of this recovery on the Incredible S forums because it let you create EXT4 file structures and now its here. Thanks!
Quick question, what's the advantage with EXT 4? I have heard that it's faster, but then several others say it's a waste of time. I do like this layout a lot more aswell.. The backgrounds are an awesome idea! Great job with this
Sent from my Incredible 2 using XDA App
You should add this to ROM manager.
jonathon2011 said:
Quick question, what's the advantage with EXT 4? I have heard that it's faster, but then several others say it's a waste of time. I do like this layout a lot more aswell.. The backgrounds are an awesome idea! Great job with this
Sent from my Incredible 2 using XDA App
Click to expand...
Click to collapse
Thank you very much
Yes, theoretically it's faster.. depending on usage it can be much faster.
On a phone the difference is less than on a computer though.
Deleting larger files is definitely much faster, also formatting.
Most newer mobiles get shipped with ext4 file system instead of ext3.
It's difficult to answer your question
You should try it out and check if you feel the phone is faster
shoman24v said:
You should add this to ROM manager.
Click to expand...
Click to collapse
I really can't imagine that I had a chance or that it would be possible
Also obviously I would like ppl to use my app.. it was a lot of work.
And yeah, also if it is the free version!
It's a big advantage for me as the developer and I hope for the users too.
That way I can send you news about critical bugs found in a new release (which happened with rc1 for example), I can make sure you get to see at least the Changelog when you install a new version and since it's just a button press, the chance is greatly increased that you also take a look at any known issues.
There are times when I release many updates in a short time. This really comes in handy.
At the moment there is only the preview, but I will release the free version today or tomorrow
Downloaded this morning and gave it a run. I like this recovery a lot.
I ended up making a backup, and then converted my file system to Ext 4 on data and Cache (system already is.)
This is a very nicely done recovery, I like that it is easy to navigate, and has a few more options when doing wipes.
The app is nice to.
Thanks for sharing this!!
PacerguyDon said:
Downloaded this morning and gave it a run. I like this recovery a lot.
I ended up making a backup, and then converted my file system to Ext 4 on data and Cache (system already is.)
This is a very nicely done recovery, I like that it is easy to navigate, and has a few more options when doing wipes.
The app is nice to.
Thanks for sharing this!!
Click to expand...
Click to collapse
Thank you very much
BTW Free version of the app is finally up
madmaxx82 said:
Thank you very much
BTW Free version of the app is finally up
Click to expand...
Click to collapse
I went ahead and bought the market version. Excellent job, Ive been waiting for a recovery like this.
I would have to say I like this recovery a lot. I like having the partion information and battery level in recovery. Also the option to convert partions is a plus. Already tried it on a couple different roms and currently running them all as ext4.
Great job and keep up the good work
Sent from my Incredible 2 using XDA App
After converting everything to ext4 cant get wifi tether to work anyone else have this issue? Boots 100 times faster though on cm7
edit fixed by updating to the latest nightly
Great recovery, got the market version. Super smooth on a few roms here.
Anyone with a sense rom should go without saying but make sure the kernel supports ext4. Drellisdees kernel does well
This Recovery looks great, I'll try it soon. A couple questions...
1. It replaces Clockworkmod 5.0.2.0?
2. Has anyone actually done any benchmarks to see if Ext4 is faster than whatever is on the stock phone?
I use Ext4 on my Ubunutu Linux box and I understand it improves performance and adds journaling, but is it actually faster on a phone. It would be cool to see boot times, application install and launch times, task switching, etc. So often people say even minor updates to ROMs are "much faster" and it's nonsense.
Thank you all very much
regarding ext4: yes it will be faster, but how much depends on usage and it's really difficult to say on a phone. But certainly it won't be slower.
Also since newer phones seem to ship with ext4 it might indicate something
Yes, when you flash any other recovery it replaces the previously installed one.
ph1nn said:
This Recovery looks great, I'll try it soon. A couple questions...
1. It replaces Clockworkmod 5.0.2.0?
2. Has anyone actually done any benchmarks to see if Ext4 is faster than whatever is on the stock phone?
I use Ext4 on my Ubunutu Linux box and I understand it improves performance and adds journaling, but is it actually faster on a phone. It would be cool to see boot times, application install and launch times, task switching, etc. So often people say even minor updates to ROMs are "much faster" and it's nonsense.
Click to expand...
Click to collapse
Well as far as benchmarks I haven't dug in too deeply. Unfortunately with quadrant file systems tend to fool it anyway but I haven't gotten linpack or similar
The biggest advantage I see are the same things that we both likely saw when linux changed to ext4 (ubuntu fan here too ) that being, things involving large amounts of data being moved at once have the biggest improvement. Obviously there are more instances of that on a computer than a phone . Boot times, it knocked a few seconds off my boot time on cm7 which is not slow to boot by any means already. I think it would be even more drastic with something as big as a sense 3.0 rom..everything else I don't know that its particularly faster after everything settles down but is most definitely not slower and is just as snappy as before. It does seem to be a bit quicker in terms of settling down more quickly after a reboot (not laggy for as long) and everything getting precached etc.
Just want to tell everyone, that there is a new known issue with tar backups!
It can happen if you have enabled tar backups that superuser stops working after you restored a tar backup.
To anyone not familiar with this: it is disabled by default! So don't worry if you didn't enable that setting!
I have updated known issues and also sent a notice about that.
To work around this, you can flash your rom again (no wipe needed) and it will be ok.
Nonetheless please deactivate tar backups for now.
It doesn't happen for everyone and always.
Difficult to track it down and I couldn't reproduce it on my device yet.
It is or was also known to happen with CWMR5 which introduced tar backups.
Maybe it's solved in the newest version I don't know however I have seen a lot of posts regarding that.
I'm working on this.
If someone runs into this problem, please send me a pm or a report telling me which version of superuser and which rom he was running.
Thank you very much and sorry about that.
Anyone entering the app gets a one time notice about it.
I've been using the tar backups since installing 4EXT last week. No problems on my end, but since I really don't need the tar backups anymore, I'll go ahead and disable that option and go with the default format.
Thanks for letting us know Madmaxx. And thanks again for the great recovery!!
Thank you
New versions of recovery and 4EXT Recovery Control.
Big changes
Hello guys,
Introduction
Today is my first step in the android development world. And I'm starting with something very little. I've created this tool for myself but I thought I could share it, as it could be useful to you as well and you could help me to improve it.
Big announcements
1) Officially supported custom ROMs:
-OmniRom
-LiquidRemix
-Skydragon
-ArrowOS
-AEX
What can you expect from flashing my script?
I think my script is interesting because its utility is completely complementary with a custom ROM or kernel: what it does has nothing to do with the kernel, so it doesn't interfere at all. And it's concrete stuff, not some supposed-to-be optimization where you're not even sure it's going to do something. I'm usually not a huge fan of these apps / modules.
-You'll get more privacy: I've removed Qualcomm telemetry, OnePlus telemetry as well as some Google Telemetry (but you can't expect too much as long as you use gapps)
-You'll get better battery life: less apps running in the background, less wakelocks, less services communicating with servers to send telemetry.
-You'll get better performance: for the same reasons. Don't expect a huge difference as our phone is very smooth already.
-The feeling of having a clean device. And this has no price.
As a proof, see this (both screenshots were taken after a fresh boot):
Extreme script:
https://imgur.com/2O47su8
19 system apps running, for a total of of 31 services running. I'm not counting Google Play services as the number of services running keep changing.
No script:
https://imgur.com/E5cEr7P
36 apps running, for a total of 60 services running! I find the difference quite huge.
What does it do?
The point is to be very very basic. Obviously I don't intend to to share something as powerful and exhaustive as xXx. My objective is to only focus on bloatwares, not features.
Also, I wanted to make a script simple enough so anybody can use it, understand it and modify it depending on your needs.
I think I can call myself a flasholoic, as I flash ROMs quite often, even when I'm happy with the current one. There are many time consuming and boring tasks when it comes to clean flash a new ROM. However, for most of them, there's a solution. For example, Titanium Backup, to mention just one.
With this script, you'll be able to skip the very boring process of removing/freezing all the system apps you don't use.
You can use this script with no worries whenever you flash your new ROM.
Why don't i Freeze apps instead of removing them?
Ideally, I would prefer to only freeze apps so the setup can stick after an update or a dirty flash, however, I don't know how to do it from recovery. Freezing works with the command from package manager "pm disable {package_name}", however, it's only available when the phone is running.
What version should I install?
-Invisible script: Install it, enjoy. I basically removed only apps related to telemetry or that don't have any function. You should still have all the apps you're using and all the features you like.
-Light Script: Invisible + apps that I consider rarely use (because they're useless or because alternatives are much popular). It should fit to 80% people without any change to make.
-Extreme script: Invisible + light + a few Google Apps (most of them can be reinstalled) and features that are not absolutely necessary but useful for some people, like face unlock for example. I wouldn't recommend it to anyone who hasn't check the .txt file first. The light script is almost as good anyway.
How to Install?
Simply reboot to TWRP, flash the zip, reboot and enjoy.
If this doesn't work, you can try three different things:
-Try to use blu spark Recovery instead of other ones.
-Try to mount system in recovery before flashing my .zip.
-Try to install Magisk and this module: https://github.com/Magisk-Modules-Repo/busybox-ndk
-Try to install the script on both slots
At least one of these options should fix things for you.
Known incompatibilities
-If the script doesn't do anything, check installing instructions.
-If an app keeps force closing when you try to open it (for example the Google app, gmail, amazon, etc.), it's because you don't have any webview selected. You can select one in the developer settings and if you don't have any you can install one from the play store (Android System Webview).
-If some apps are remaining, it's because it's system apps you updated and they became user apps. You can just uninstall them like any other user apps and it will completely disappear.
-If an app that is included in the script freezes, but it's also available in the playstore, uninstall it with Titanium Backup, reboot and reinstall the app from play store.
-If you're using substratum, you must edit my script and remove this line: "/system/system/app/OpSkin",
-If your bank app doesn't work, you can try to add back Stk (sim toolkit), as the app helps for authentication.
-In general, search this thread if you want more details / understand why.
F.A.Q.
-I don't want to use this debloater anymore or it broke something I miss, how can I go back to normal?
=> Dirty flash your current setup (ROM, twrp, reboot to twrp, magisk, kernel, anything else you want)
-Does this script work for X or Y ROM? Can you make a debloater for X or Y ROM?
=> If you understand how my tool work, then you will understand that my scripts can potentially work on any ROMs, but each ROM has its specific apps so some bloatware won't be removed, most likely. I won't support any new ROM except if I end up trying it myself. I prefer to avoid to create new scripts blindly especially if I've never experienced the ROM.
-I flashed your deblaoter and now some apps keep force closing
=> "If an app keeps force closing when you try to open it (for example the Google app, gmail, amazon, etc.), it's because you don't have any webview selected. You can select one in the developer settings and if you don't have any you can install one from the play store (Android System Webview)."
Where can I get more info?
Check the .txt file in the download section. It lists all the apps included in the different scripts AND all the apps not included (so you can see what apps you want to potentially add, it's much easier to work like that)
How are the apps sorted in the .txt file?
-First, by categories (each category starting with #) (invisible, light, extreme, etc.)
-Then, they're sorted by their type (reserve / app / priv-app / other)
-Then, simply by alphabetic order.
-At the end of the document file, there are some explanations about some apps that can sound... mysterious about whether it's safe or not to delete them.
How to edit the script and make it work? (TUTORIAL)
Prerequisites
-Root (ideal but not mandatory)
-File manager (ideal but not mandatory, I recommend Amaze https://play.google.com/store/apps/details?id=com.amaze.filemanager&hl=en_AU )
-TWRP
Then you have two alternatives
a) Use your computer (Windows): you will need Zip Builder https://forum.xda-developers.com/an...g/tool-zip-builder-v4-2-1-build-sign-t3739556
b) Use your phone: then you will need MiXplorer ( https://forum.xda-developers.com/showthread.php?t=1523691 )
Steps to follow
1) Download my script.
2) Unzip it. Browse to META-INF\com\google\android and open "updater-script" in a notepad. (I'd recommend you notepad++ ( https://notepad-plus-plus.org/download/ )
3) Add some apps you want to delete, or remove the apps you want to keep. To see what apps are on your device, use a file manager that can use root and check the apps you have in /system/app and system/priv-app. The priv-app are usually more sensitive so be cautious with them.
4) Don't forget that on every line, you need a comma at the end, except for the last app of the list.
5) You don't need to touch any other lines, except if you want to have fun and change what TWRP will display: it's the lines with
Code:
ui_print("")
6) Save your file.
7) a) Windows alternative. Follow instructions to install properly Zip Builder. Then shift + right click on the parent folder of the META-INF folder and click on "Build Zip...". If Zip Builder is set up properly, you will see the option I just mentioned. You can also open the program and browse to the parent folder where META-INF is.
Copy the .zip to your phone and you're good to go!
7) b) Android alternative: Install MiXplorer. Long press on the META-INF folder. Confirm the creation of the archive, pick the name you want and make sure that "store" is selected, below "zip". Then select the newly created zip, and click on the "Sign" option. Choose Testkey. It will create yourzip-signed.zip. That's the file you need to flash in TWRP.
8) Flash in TWRP
Let me know if you need any help or if something is not clear to you.
Downloads, risks, credits, Information
Where to download?
Check the attachments!
What are the risks, or why is it actually pretty safe to use it?
1) If you use my scripts, as I've tried all builds, I can assure you in the worst scenario you will loose a few features you might have wanted to keep.
2) If you try to make your own script:
a) You misspell a system folder: (it's case sensitive, careful): well the script will just ignore it and try to remove a folder which doesn't exist, so no consequence at all, just a useless line in your script.
b) you mess up with how you're meant to write the script: for example, you forget a comma or you leave it on the line of the last app you want to delete. Well, no worries, TWRP will just not flash the script so nothing happens. Just check your code to find the mistake.
c) Your script is fine but delete a core app that the system needs. Again, no worries! You will bootloop. In this case, you need to dirty flash your current setup (for example, flash OOS, flash TWRP, reboot to recovery, flash Magisk, flash your favorite kernel, reboot). Then you can try to find the culprit in your code, remove it, and try again your script.
Just in case, you know the XDA saying: "flash at your own risk!"
Credits!
First of all, I'd like to credit @Primokorn for his tutorial which helped me a lot. Basically everything in my script I owe him. I've just made it even more simple and focused on only debloating. Also, and obviously, it's adapted for our OnePlus 6. Right now, it's optimized for OOS 9.0.3, but depending on how the project evolves and how popular it will get, I could make "special editions" for open betas as well as AOSP ROMs.
I would also like to thank @TKruzze for his amazing tool "Zip Builder", which makes me save a lot of time everytime I want to try / build a new script.
Thanks to @Zios01 for inspiring me about "optimizing" OOS.
Information
"Tomatot- Debloater"
Contributors
@Tomatot-
Source Code: everything is in the zip.
Created 2018-11-20
Last Updated 2019-12-23
Changelog
Tomatot Debloater 4.1 for OOS
-REMOVED FROM THE SCRIPT:
Light:
TeleService (necessary for some operators)
Extreme:
SdCardService (necessary for file managers)
ModuleMetadataGooglePrebuilt (necesary for permissions)
Tomatot Debloater 4.0 for OOS
REMOVED/CHANGED :
- All folders (and there are lots of them) that don't exist anymore (usually they got moved to another path)
ADDED
- "/data/india/india.img"; (let me know if it works)
- A few new apps that are most likely useless.
Previous updates:
Tomatot Debloater 3.3
-All apps in /reserve are now deleted in the invisible script. If new apps are added by OP, they'll be automatically deleted as I added the whole folder (you can check the script to understand). Thanks to @nirogu325 for the idea!
-Moved DiracManager to the light script since some people like using it.
-Added OPWidget, it seems to be a new app added by OP
-Added OPWallpaperResources to the extreme script as I'm not sure what it does
-Removed OPSimContacts since it breaks the OP phone app.
Tomatot Debloater 3.2
-Added amazon apps hidden in /vendor/etc/apps
-Removed Rftoolkit on the Omni script
Thanks to @bojiokia and @nirogu325 for pointing me out they existed and that they were on all devices.
Tomatot Debloater 3.1.1
Thanks to @nirogu325 for his help to figure out how to mount /vendor and how to remove Rftoolkit properly
Removed also a folder that doesn't exist (LiveWallpapers)
Tomatot Debloater 3.1
I have decided to only use " run_program("/sbin/mount", "/system"); " to mount system from now on. It seems to be the most reliable / universal way to do so.
The Omni update has no change except I switched to the new mounting way.
### New entries for Invisible Script
OPCommonLogTool
Traceur
Rftoolkit
### New entries for Light Script
ARCore_stub
CarrierDefaultApp
CtsShimPrebuilt
CtsShimPrivPrebuilt
### New entries for Extreme Script
LiveWallpapersPicker
LiveWallpapers
OPSafe
SdCardService
uimremoteclient
WAPPushManager
DocumentsUI
IFAAService
OnePlusGallery
VpnDialogs
Tomatot Debloater 3.0
-All main scripts that are up to date are now 3.0 for a purpose of clarity.
-Except the LiquidRemix script, no apps have been added/removed from the scripts.
-Omni/Liquid/Skydragon have a similar level of debloating.
-Since a lot of users reported issues of the script not working, I figured out it was because for some reasons some recoveries don't execute busybox commands properly. I switched to edify commands. The main benefit is that it should work for everyone 100% of the time. The disadvantage is that it won't work for other devices. It might be the same path for the 6T but I need people to check. For other devices it won't work 100%. What you can try however, is to mount system before flashing. It should make the script work.
OOS 2.5.2
-Removed DeskClock as it's the clock app that a lot of people need. I thought it was the widget, my bad.
OOS 2.5.1
-Removed WebViewStub from all scripts since it may affect the webview selecting setting.
OOS 2.5
-Added BluetoothMidiService to the extreme script because 99% people won't use it (check Google to check what it is)
-Added ProxyHandler for the same reason
-Added ManagedProvisioning for the same reason, in the light script. ( Work Profile Setup apk. It's useless for most people. Obviously don't delete it if your company gave you this phone, but then you shouldn't flash it in the first place! )
OOS 2.4
-Removed a few useless lines in the script.
-Cleaned up the .txt file, now all packages explained are sorted alphabetically.
-Moved CNEService to the extreme script as it breaks wifi calls.
-Moved HotwordEnrollmentXGoogleWCD9340 to the extreme script as it might break OK Google.
-Moved WebViewStub to the invisible script
-Added YouTube to the light script as it doesn't break YT Vanced.
-Added Chrome to the extreme script. Don't forget to have a working/activated webview!
OOS 2.3
HotwordEnrollmentXGoogleWCD9340 : moved to extreme as it breaks ok google
EmergencyInfo : moved to extreme as it could break double press power button to open camera
datastatusnotification : moved to extreme as it allows the system to cap data.
Added DeskClock to the light script
Added WebViewStub to the light script
OOS 2.2.1 / custom 1.2
-Unified numbers for all OOS sripts / all custom ROMs scripts so it's just easier to follow / maintain.
-OOS: moved OPBackup to the extreme script as it breaks system updates. It doesn't matter since if you have Magisk and TWRP you can't update via OTA but some people like having all settings working so... Now with the light script you shouldn't have any "broken" feature.
-Custom: removed DocumentsUI so it's possible to access external storage.
v2.2
-Removed Chrome from the script as it can break webview. There is not reliable fix as Android system struggles to properly select "Android System Webview". Feel free to freeze or uninstall Chrome as long as you update android system webview and make sure it's selected in developer settings.
-Put back Gmail2 in the script as now installing it as a user app shouldn't break the app anymore.
-Now the script should be completely bug free.
-if you had issues with gmail, dirty flash your current setup first.
v2.1
-Fixed a broken setting on ALL scripts, see this for more info: https://forum.xda-developers.com/showpost.php?p=78287566&postcount=103
-Added setup apps to the light script as I intended in the first place
-If you come from an older script, you should dirty flash your current setup again because otherwise the broken setting won't come back. Sorry for the mistake.
v2.0.2
-Fixed OPFilemanager on light and extreme scripts.
v2.0.1
-Fixed a few mistakes I wrote, extreme script will work now.
v2.0
-Completely resorted the apps so it makes more sense. I have a little more hindsight and for most apps I actually know what they do and if it's dangerous to remove them or not. Hence, the extreme script hasn't changed but the light is significantly different. It will remove more useless apps but not remove apps that most users use. A bit smarter I'd say.
-And I would like to introduce you the invisible script, the ones who really can't deal with making sure the script works for them, they just want to make their phone lighter. Easy peasy, hassle free.
-To see how I resorted apps, please check "List of systems apps SORTED & EXPLAINED v2.0.txt" or just have a look at the end of this post.
v1.8.1
-Removed Rftoolkit as it's a vendor app and I can't make it disappear for some reasons. I'd recommend you to freeze the app.
-Removed "datastatusnotification" as it's necessary to keep track on data usage.
v1.8
-Only the extreme script is updated
-Added a few more apps, including OPSes which sens telemetry I think. I couldn't find anything explaining exactly what it does but I've been running my script for some time now and 0 issue.
-Here is the list:
Code:
"/system/system/app/OPSesAuthentication",
"/system/system/app/SeempService",
"/system/vendor/app/Rftoolkit",
-Yes, changelogs are shorter and shorter
-However, 92 apps included now!
v1.7.2
-Added Music2 to both scripts.
v1.7.1
-Removed from the script OPAppCategoryProvider as it was breaking battery stats.
v1.7
-Only uploaded the extreme version as it's experimental and the light version would be the same
-I'm trying a few more apps that seem useles, but I need more feedback. Some telemetry from Qualcomm should be gone as well.
-Here are the new apps
Code:
"/system/system/priv-app/OnePlusWizard",
"/system/system/app/AutoRegistration",
"/system/system/app/datastatusnotification",
"/system/system/app/PlayAutoInstallConfig",
"/system/system/app/RFTuner",
"/system/system/priv-app/OPAppCategoryProvider",
v1.6
-Added more apps in both scripts
-Now the light script includes this category " #APPS THAT CAN BE FOUND ON PLAY STORE" as you can reinstall them very easily (and you won't even loose them if you updated them once).
-Expect more privacy as I've deleted more telemetry from both OP and Qualcomm.
-Documentation updated
-Here is the list
Code:
"/system/system/app/GoogleContactsSyncAdapter",
"/system/system/app/OpSkin",
"/system/system/app/HTMLViewer",
"/system/system/app/uimremoteclient",
"/system/system/priv-app/CallLogBackup",
"/system/system/priv-app/CNEService",
"/system/system/priv-app/OPAod",
"/system/system/priv-app/SharedStorageBackup",
v1.5
-Fixed a few entries as they were not written properly. So some apps that were already included will actually be removed this time. Thanks to @zyvex_14 for his help and support.
-I've added these apps that can be safely removed.
Code:
"/system/system/app/Account",
"/system/system/app/QdcmFF",
"/system/system/app/WapiCertManage",
"/system/system/priv-app/DiracAudioControlService",
"/system/system/priv-app/OPCellBroadcastReceiver",
-As always, I've updated the advanced documentation.
-You can now download a .txt file with all the documentation: all system apps are sorted and the shady ones are explained.
Now, Tomatot Debloater Extreme v1.5 removes 72 apps and your device still runs perfectly, if not better
Tomatot Debloater Light v1.5 42 apps and you basically don't loose any feature
v1.4
-Quite satisfying build: I feel like the script is almost final.
-Here are the new lines I added, to the different versions.
"/system/system/app/OPBackup",
Code:
"/system/system/priv-app/BackupRestoreConfirmation",
"/system/system/priv-app/Tag",
"/system/system/priv-app/OPFaceUnlock",
"/system/system/priv-app/EmergencyInfo",
"/system/system/priv-app/Turbo",
v1.3
I forgot to update the scripts when they're flashed so TWRP will display "v1.2 when it's actually v1.3, so no worries
-Merged with xXx all the apps where I was sure they could be removed without risks. Still some apps I need to sort out.
-Now I have 2 scripts
LIGHT = SAFE TO DELETE FOR ALMOST EVERYONE + APPS THAT CAN BE FOUND ON PLAY STORE (they will just become user apps if you updated them at least once)
EXTREME= SAFE TO DELETE FOR ALMOST EVERYONE + APPS THAT CAN BE FOUND ON PLAY STORE + SAFE TO DELETE IF YOU USE ALTERNATIVE APPS OR JUST DON'T NEED THE APP + EXPERIMENTAL STUFF SOMETIMES
To see their content, check advanced documentation.
v1.2
-Added OP user apps (that you can uninstall without root when to flash a new ROM). I didn't think of them at first because they're easy to remove and once you do, they don't come back after you reinstall the ROM. However, with the script, they will leave the system partition for good, which is cleaner. And it will be useful for people who didn't delete them already.
-Removed "usb_drivers.iso." it's what makes the windows explorer show the OP6 as a CDROM when you plug it to your computer. So you can have access to drivers. It's pretty useless except for the first time you plug your phone to your computer. And still, there are plenty other ways to install drivers.
-I've updated the list of the apps in the first post.
v1.1
-Fixed the "card" app.
v1
-Initial release
Works like a charm for me, many thanks.
I just had to edit your file for the "card" app, + few others lines I deleted to keep some apps I use, such as 'Duo'.
In your file, it is written "Card", but my app was named 'card' and apparently the C in capital letter makes it not work (for this app specifically).
zyvex_14 said:
Works like a charm for me, many thanks.
I just had to edit your file for the "card" app, + few others lines I deleted to keep some apps I use, such as 'Duo'.
In your file, it is written "Card", but my app was named 'card' and apparently the C in capital letter makes it not work (for this app specifically).
Click to expand...
Click to collapse
Wow, you're already a pro! Well done mate. I don't know if it was your experience with editing a script but if it is, I'm glad my my guide makes sense and that some users already benefit from it. And thank you for pointing out my mistake.
I'm uploading a 1.1 update with the fix.
Don't forget to flash again your script if you update your ROM.
First time I manipulated and edited this kind of file, so many thanks for your tuto, very helpful in my case.
Just one additionnal question, is there somewhere a list of all bloatwares that can be safely removed? Or is your list exhaustive for our OP6?
zyvex_14 said:
First time I manipulated and edited this kind of file, so many thanks for your tuto, very helpful in my case.
Just one additionnal question, is there somewhere a list of all bloatwares that can be safely removed? Or is your list exhaustive for our OP6?
Click to expand...
Click to collapse
Humm usually on different when you search for it on Google, you find threads that explain what services to disable, but 99% of the time they're also device specific.
I've never found a universal list with all the bloatware common to all Android phones. If you have a doubt about an app in particular, google it and you'll have your answer. However, what I've found out trying different scripts is that there are some apps i can freeze without any consequences, whereas if I try to delete them with my script, the phone will end up in a bootloop.
Unfortunately, this project is very recent for me and I didn't do any exhaustive testing so I don't know exactly what apps were breaking my script.
Ideally, i'd have to create another script that bring back the apps I remove so I can try one by one and see which apps are safe to remove. Because right now, everytime, flashing back OOS, rebooting to make sure it works, then going back, flashing my script, checking again, etc. it takes a lot of time so it will take some time before I can be more accurate.
At least right now I have a good base of what apps I'm sure I can remove.
Now when I'll have enough time I could try one by one to delete apps and see how it goes. I just to find a way to not have to reflash the whole system every time.
If anyone has a suggestion he's welcome!
I'd say that @Zios01 knows a lot about the topic since he probably tried himself what apps are safe to debloat.
You can read his script as well to see what apps he removes and you can assume it's safe to add them to my script.
I perfectly understand that you can't try one-by-one all of them, it gonna turn you crazy otherwise to flash-reboot-check and so on...
As you wrote, this is a good start and a good base, let's see also if someone has more experience with the others apps/bloatwares.
Anyway, thanks again for your answers and contact provided, I will try to find his script as well.
zyvex_14 said:
I perfectly understand that you can't try one-by-one all of them, it gonna turn you crazy otherwise to flash-reboot-check and so on...
As you wrote, this is a good start and a good base, let's see also if someone has more experience with the others apps/bloatwares.
Anyway, thanks again for your answers and contact provided, I will try to find his script as well.
Click to expand...
Click to collapse
Here it is.
I had to add the .txt extension to upload it. Also, I changed the name so it won't work. It's just for "science".
You will see he doesn't use the same "language" at all, and it's way more complicated than my script. However, it's not hard to spot the apps he's referring to.
Btw, as I already said, the good thing with this script is that it will ignore errors. So if you add a line to your current script, you can flash it and it will just remove the one app you added. You don't have to make an entire new file for your v2.
OK, so I added several lines based on XxX script.
I did a reboot and no bootloop, that is already a good point .
Now I am going to test my phone and if everything works ok and still flawless, I will share my file.
zyvex_14 said:
OK, so I added several lines based on XxX script.
I did a reboot and no bootloop, that is already a good point .
Now I am going to test my phone and if everything works ok and still flawless, I will share my file.
Click to expand...
Click to collapse
When I did my little experiments and I was deleting the wrong files, it was just not booting, stucking on OnePlus logo. Just once it booted, but shut down immediately and took me to recovery.
So you should be fine. But yeah maybe only after a week or something we'll find out that a tiny but sometimes useful feature doesn't work.
Thanks for your work! I would suggest using Magisk if possible as the changes aren't permanent. Except if you want to achieve that it's permanent
Tomatot- said:
When I did my little experiments and I was deleting the wrong files, it was just not booting, stucking on OnePlus logo. Just once it booted, but shut down immediately and took me to recovery.
So you should be fine. But yeah maybe only after a week or something we'll find out that a tiny but sometimes useful feature doesn't work.
Click to expand...
Click to collapse
Indded, that is what I worry about, that everything looks fine and finally after some days (maybe earlier :crying something doesn't work like it should be.
That is why I would like to test prior sharing my file.
Macusercom said:
Thanks for your work! I would suggest using Magisk if possible as the changes aren't permanent. Except if you want to achieve that it's permanent
Click to expand...
Click to collapse
It does sound like a good idea! I will investigate this possibility and let you know. I'm not sure I have enough knowledge and experience.
https://forum.xda-developers.com/apps/magisk/module-terminal-debloater-debloat-t3584163
So I've found this Magisk Module which seems quite impressive tbh. It seems quite easy to use and safe as well. It's honestly way more advanced than my script.
But at the same time, I feel like it doesn't do much more than a classic freeze with Titanium Backup.
You still have to go every time you install a ROM through all the apps you want to remove. You could write down numbers but it's risky, if you change ROM or even you update your ROM and numbers change, it could mess up everything. So I still think my solution had advantages compared to this Magisk Module.
However, I might use the module to see what apps break the device or not. Then I can improve my script a little. I will also think about making a Magisk Module out of it, but I'm not sure it will make things much better.
My ultimate goal is just to "flash it and forget about it until you flash a new ROM/update". So it wouldn't matter if you can remove it or not.
There are 2 possibilities when using my idea:
1) I (I isn't me, I speak for users in general) am happy with the script, I don't loose any features. So I don't need to touch it. Flashing it once in TWRP isn't a burden at all. Especially since it takes like 2 seconds to flash. Then it's the best solution since, once you have your script you like, you can always keep it.
2) I am happy with the script but I want a few apps back. Sure, having a Magisk module could make things easier as I could just remove the module (considering it has a restore feature), but I would need to edit the module or the script, and then apply it again. It one of the apps break the system and makes the device bootloop, even with a Magisk module, it will be hassle to fix it. It's just more simple to flash the ROM again like I'm doing now.
Now you need to ask yourself this:
1) Do you prefer to have more features at the cost of spending some time setting up your device every time you flash a ROM? Then use Titanium Backup or Terminal Debloater.
2) Do you prefer to take some time once to setup your script properly but then you won't have to care about it for, theoretically, until you get a new device? Then go with my script.
If my script gets some attention, I'm pretty sure within a few weeks I / we will be able to propose enough scripts to make (almost) everybody happy.
Like script 1 extreme debloating
Script 2 medium debloating
Script 3 light debloating
So 99% users are satisfied, and then the pickiest ones can always make their own script since it's very easy to edit my script.
Am I making a point?
What's with the .iso file and /system/reserve?
Tomatot- said:
https://forum.xda-developers.com/apps/magisk/module-terminal-debloater-debloat-t3584163
If my script gets some attention, I'm pretty sure within a few weeks I / we will be able to propose enough scripts to make (almost) everybody happy.
Like script 1 extreme debloating
Script 2 medium debloating
Script 3 light debloating
I think this will be a great way to debloat to each individual preference. Will be watching this thread for these updates:good:
Click to expand...
Click to collapse
Sh0X31 said:
What's with the .iso file and /system/reserve?
Click to expand...
Click to collapse
I didn't know about /system/reserve, thankj you for sharing. From what I understand, it's the apps that come pre installed but are removable. It seems like once you delete them they don't come.baxk after a dirty flash. However I can remove them so the script is useful after a clean flash. Thanks!
What are you referring to with the .iso though?
Tomatot- said:
I didn't know about /system/reserve, thankj you for sharing. From what I understand, it's the apps that come pre installed but are removable. It seems like once you delete them they don't come.baxk after a dirty flash. However I can remove them so the script is useful after a clean flash. Thanks!
What are you referring to with the .iso though?
Click to expand...
Click to collapse
I mean the usb_driver.iso
Sh0X31 said:
I mean the usb_driver.iso
Click to expand...
Click to collapse
What about it?
Sh0X31 said:
I mean the usb_driver.iso
Click to expand...
Click to collapse
Not sure what it is, but xXx has it available for debloat on his room as well