Related
THIS TOOL HAS BEEN DISCONTINUED. IF YOU REALLY NEED A LAGFIX, USE VOODOO. HOWEVER, WITH LATEST ROMS I DONT PERSONALLY FEEL A LAGFIX IS STILL NEEDED, THUS I DON'T USE ONE, AND WILL NOT CONTINUE DEVELOPING ONE
About
Here it is, yet another LagFix tool. It's certainly not the first, but it does offer some things others do not (at the time of this writing).
This patch uses the ext2/ext3 image in /data method.
IMPORTANT NOTICE FOR FROYO USERS
(1) Use ext2. ext3 is NOT supported on Froyo, only Eclair
(2) The installation will fail if you apps installed to SD. Go to Settings -> Applications -> Manage -> On SD card. Click each app and click "Move to phone". In the end, the "On SD card" list should be empty. Reboot. Install CFLagFix. When the fix is installed, you can move apps back to the SD card if you wish.
Features
- Lots of checks to make sure the fix is possible
- This is not just based on a script, but a lot of commands are performed and their results rigorously checked to be what is expected
- You can select (from a set of presets) which folders you want to lagfix
- You can select how big the image should be (between 128mb and all the free space in /data minus 250mb, to prevent low storage space warnings)
- The actual moving of data from RFS to the image is done in a boot loop, while the files are not in use. This minimizes the chance of corruption during move (settings being lost, etc)
- Comes with e2fsprogs, and e2fsck is performed each boot to fix a corrupted image
- Comes with it's own busybox, so no need to install it, and no chance for conflicts
- If an ext2 image is used, it is tuned to not reserve any blocks
- If an ext3 image is used, it is tuned to not reserve any blocks and use journalling
- Also moves databases (safely)
- Uninstall option
- Resize option, resize your partition whenever you want, to whatever (possible) size you want
- "Full automatic" option, this will max out the image size while still preventing the low storage space warning, and will also reclaim the space from the backup folders and automatically resize the image to max again after that space is reclaimed. This generally results in an image of about 1.5 GB. It'll also leave some space in case the system still needs to write in /data but not in the image.
- Progress monitor ("educated guess" about progress, not exact, but pretty close, usually!)
A fair number of these seem to be unique at the time of this writing.
Notes
- e2fsck result is stored in /data/cflf/e2fsck_result.txt
- list of mounted directories is stored in /data/cflf/mountlist.txt
- if ext3 is used /data/cflf/imageisext3 file will be present
- my own test rom is JM2+root-with-update.zip+ClockworkMod
Known issues
- In case the image is heavily corrupted, e2fsck may take longer to fix it than the rest of the boot process. Theoretically this could result in data loss
- ext3 does not seem to be supported on Froyo ROMs JP1/JP2/JP3
Credits
- mimocan, ykk_five, RyanZA, and all others who have chipped in for various lagfixes
- cynogen, e2fsprogs built for ARM
- kalpik, busybox APK
- ofcourse the original authors of those tools as well
- myself, this is all based on ADB Magic code
Donations
Please feel free to donate: http://www.jongma.org/dx.php
Requirements
- Windows
- Microsoft .Net 3.5 framework
- Phone in USB debugging mode
- SuperUser
Before using ...
I strongly recommend using ClockWorkMod and making a backup of your ROM. Just in case Also, during any operation, I advise having your phone hooked up so I can draw power from the computer.
Usage
- Unzip the attached file somewhere
- Make sure your phone is connected in USB debugging mode
- Make sure you have SuperUser installed
- Run CFLagFix.exe
There are three tabs:
Install LagFix
This tab allows you to install the LagFix, and lets you configure some options.
I recommand leaving the "Full automatic" option turned on, if you do, just press "Install !" and everything will be arranged for you. If you turn this option off, you can configure some settings manually, but note that using this does not reclaim wasted space of the backup files.
Note that you can still select to use ext3 instead of ext2, even if in "Full automatic" mode.
When you press "Install !", the program will be finished quickly, but your phone may continue working for 30 minutes or so, and keep rebooting very often. If you have a lot of data installed, it may take even longer.
Do NOT even touch your phone until Android boots up again!
A lot of things are checked before the install will start. You will need about 50% free in /data for the operation to work, but it will check this before making any modifications on your phone.
Resize Partition
This tab allows you to change the current ext2/ext3 partition size. The slider will only let you select values that are actually possible, i.e., bigger than your current data usage and smaller than the total space that could be occupied by the image.
Clicking "Resize !" will reboot your phone and resize the partition. Again, this can take an awfully long time! Don't panic, just wait it out.
Uninstall LagFix
This will uninstall the LagFix. It will completely remove it. Before removing it, however, it will move all files out of the image and back into the normal filesystem again, so no data is lost.
Clicking "Uninstall !" will reboot your phone and perform the uninstallation. Again, this can take an awfully long time! Don't panic, just wait it out.
Note that uninstallation will only work if you are using less than 50% of the device's capacity, but again the program will check this before making any modifications on your phone.
You can only uninstall installations of CFLagFix 1.20 and newer !!
BETA
This is very beta, use at your own risk!
WARNING
This patch is NOT compatible with ANY other lagfix tools. Either undo those completely, or just don't use this. If you were using one of those, I'd personally recommend a complete reflash of the firmware before using this patch.
WARNING #2
Before trying 1.80, please see this post.
Download
<< 1.70: 632
Changelogs
1.80, 15-08-10
- Redone some crucial parts of the patching procedure (for all install, resize and uninstall). Should fix all remaining issues!
1.70, 13-08-10
- Added /data/app-private/ folder
- Added progress monitor (estimates.... not exact)
- Moved /dbdata/databases to it's own partition, much faster for smaller read/writes
1.60, 12-08-10
- Updated codebase to ADB Magic 0.9, fixes issues with some weird pre-existing installations of busybox
1.50, 12-08-10
- Added "full auto" mode, "one click" solution for beginners
- Added ext3 support
- Added resize support
- Added uninstall support
- Fixed some issues
- Update scripts
1.20, 11-08-10
- Everything has been moved to /data/cflf/ , this - amongst other things - fixes issues with JP3
1.01, 11-08-10
- Adusted a permission error which could cause the system to be unable to create any new databases
Fix for 1.00 users: there isn't any yet. This is *beep* to fix manually. I would advise this "unpatch" method posted here: http://forum.xda-developers.com/showpost.php?p=7616676&postcount=29, then repatch with the latest version.
CFLagFix.exe doesn't even run for me.
"The application failed to initialize properly (0xc0000135). Click OK to termiate the application."
lyno said:
CFLagFix.exe doesn't even run for me.
"The application failed to initialize properly (0xc0000135). Click OK to termiate the application."
Click to expand...
Click to collapse
You sure you have MS .Net 3.5 framework installed ?
http://www.microsoft.com/downloads/...fd-ae52-4e35-b531-508d977d32a6&displaylang=en
The error message is a DLL initialization error... as CFLagFix doesn't explicitly use any DLLs, my guess would be the .Net framework.
Chainfire said:
You sure you have MS .Net 3.5 framework installed ?
http://www.microsoft.com/downloads/...fd-ae52-4e35-b531-508d977d32a6&displaylang=en
The error message is a DLL initialization error... as CFLagFix doesn't explicitly use any DLLs, my guess would be the .Net framework.
Click to expand...
Click to collapse
Ah yes! I removed all .net frameworks on this works laptop to be able to install some old COM files. Will re-install and test.
This looks so awesome! Thank you!
Any chance for open sourcing this?
installing now
Well im gonna give this a shot, have just installed the african jg8 and rooted,am doing this fix now.
Then ill try the 1.2 overclock on top, ill post a score shortly .
Not bad though i see one problem... it's windows only ^^
select which folders you want to lagfix
Click to expand...
Click to collapse
Sorry, bit of a noob here - what exactly do you mean by this? Why would we only want to 'lagfix' certain folders and not the whole thing?
just tried out your tool on my stock DXJF4 (with apps in it, not clean condition). With default size as well (around 1200 mb)
Actually I used mimocan's fix before but everything was wiped by mistake and everything went to default condition.
After the process finished, the Android displayed information about damaged internal SD, but everything was working. Is that expectable?
Now I got 2260 using Quadrant, leap from 1700 with mimocan's fix.
Nice job Chainfire!!
Can't wait to use JM2 / DDJG4
btw, can I post this on my blog?
:update :
whenever I open gallery, it always says no sdcard detected... do you know how to fix this? -> it doesn't recognize both my internal & external sd, but i can browse them properly in Estrongs/astro
veenone said:
After the process finished, the Android displayed information about damaged internal SD, but everything was working.?
Click to expand...
Click to collapse
That sounds scary, think I'll wait a while before trying!
RyanZA said:
This looks so awesome! Thank you!
Any chance for open sourcing this?
Click to expand...
Click to collapse
Not at the moment, but maybe in the future
Tayutama said:
Not bad though i see one problem... it's windows only ^^
Click to expand...
Click to collapse
Can't be helped. Not going to release a non-Windows versions. Perhaps wine/mono will make it work, though I doubt it
danamoult said:
Sorry, bit of a noob here - what exactly do you mean by this? Why would we only want to 'lagfix' certain folders and not the whole thing?
Click to expand...
Click to collapse
You can't really lagfix all folders, as the process where the image is mounted is run asynchronously with the rest of the boot process. There will be havoc if the system can't load certain files because the image is not mounted yet. This is why you can't just lagfix the entire system, but only certain parts.
In the presets I have only added those folders that I feel are mostly safe to lagfix AND would actually benefit the speed of the phone.
Also, for some folders there is some discussion to whether or not it is beneficial to have them in the image, like /dbdata/databases. I personally feel it should be lagfixed, but not everyone agrees.
veenone said:
just tried out your tool on my stock DXJF4 (with apps in it, not clean condition). With default size as well (around 1200 mb)
Actually I used mimocan's fix before but everything was wiped by mistake and everything went to default condition.
After the process finished, the Android displayed information about damaged internal SD, but everything was working. Is that expectable?
Now I got 2260 using Quadrant, leap from 1700 with mimocan's fix.
Nice job Chainfire!!
Can't wait to use JM2 / DDJG4
btw, can I post this on my blog?
Click to expand...
Click to collapse
I have not seen the "damaged internal SD" message before in any of my tests. It might be ROM specific (I'm personally using JM2). I would recommend rebooting (using the "hold power button + press power off" method) and see if the message still comes up. Let me know what happens.
And yes, feel free to post about it in your blog.
veenone said:
just tried out your tool on my stock DXJF4 (with apps in it, not clean condition). With default size as well (around 1200 mb)
Actually I used mimocan's fix before but everything was wiped by mistake and everything went to default condition.
After the process finished, the Android displayed information about damaged internal SD, but everything was working. Is that expectable?
Now I got 2260 using Quadrant, leap from 1700 with mimocan's fix.
Nice job Chainfire!!
Can't wait to use JM2 / DDJG4
btw, can I post this on my blog?
:update :
whenever I open gallery, it always says no sdcard detected... do you know how to fix this?
Click to expand...
Click to collapse
Replying to the same message again, hehe.
Now that I'm thinking about, how exactly did your device got wiped ? Anything less than an actual firmware flash does not completely remove mimocan's fix, AFAIK. To completely undo it you'd have to completely reflash (and get stock kernel back), and possibly remove the ext partition from your SD. In other words, if you "wiped" from recovery, this is not a removal of mimocan (AFAIK).
Gallery is working fine for me, by the way, and as stated above, I have not seen that message in my tests with JM2 (neither with a lot of apps installed nor a clean flash).
(Then again, this is the first release, so there might be issues )
Is it possible to do this onto an external SD card (provided one has one that is fast enough) so we do not risk any possible further damage to the internal card due to excessive IO.
I believe it would be quite difficult to replace the internal SD card, and in order to load custom roms (with update.zip) it must be mounted to the internal SD.
I'd much rather replace external SD cards if I had to choose between the internal and an external.
well everything was restored to factory state when I went to CSC menu. I think mimocan's fix also removed since I got 800 in quadrant score.
Update: after I rebooted the sgs for a couple times, now it recognize both sd cards.. weird.. But that's fine since the issue is solved now!
Daemos said:
Is it possible to do this onto an external SD card (provided one has one that is fast enough) so we do not risk any possible further damage to the internal card due to excessive IO.
I believe it would be quite difficult to replace the internal SD card, and in order to load custom roms (with update.zip) it must be mounted to the internal SD.
I'd much rather replace external SD cards if I had to choose between the internal and an external.
Click to expand...
Click to collapse
This fix is using exactly same space that is already reserved for user data and programs. And it is on the internal SD. So I really can't think how this fix could cause any damage at all. Thoughts?
I selected maximum Space, and now i have low internal memory. How to remove this fix or change the Space?
Daemos said:
Is it possible to do this onto an external SD card (provided one has one that is fast enough) so we do not risk any possible further damage to the internal card due to excessive IO.
I believe it would be quite difficult to replace the internal SD card, and in order to load custom roms (with update.zip) it must be mounted to the internal SD.
I'd much rather replace external SD cards if I had to choose between the internal and an external.
Click to expand...
Click to collapse
Use mimocan's fix if you want to use external SD - it is especially made for that! His thread is a sticky (at the top) in this forum.
veenone said:
well everything was restored to factory state when I went to CSC menu. I think mimocan's fix also removed since I got 800 in quadrant score.
Update: after I rebooted the sgs for a couple times, now it recognize both sd cards.. weird.. But that's fine since the issue is solved now!
Click to expand...
Click to collapse
Mimocan's fix uses Odin. Like update.zip's, a "factory reset" does not remove patches made in this way, only a real flash does.
Either way, happy to see your problem is solved
I think the problem was the system didn't mount sd cards properly after several boots from CFLagFix. So it needs more reboots to mount the sdcard with structure change properly...
Chainfire said:
Not at the moment, but maybe in the future
Can't be helped. Not going to release a non-Windows versions. Perhaps wine/mono will make it work, though I doubt it
Click to expand...
Click to collapse
It's a shame you can't open source this.
Personally, there is no way I'm going to run something like this without source - I believe you are just trying to help us out, but there is always the chance that you could be doing something damaging by mistake, or even installing a trojan on purpose.
I'll be following release though, looks awesome and hopefully you'll be able to open source this soon!
[size=+2]This version is now deprecated in favor of the 2.0 APK version. Please see this link: http://forum.xda-developers.com/showthread.php?t=784691[/size]
This version is not recommended for use any longer.
Details about what this fix does:
Creates a VIRTUAL EXT2 filesystem inside the stock RFS filesystem on the internal SD card, with a 4KB block size. This means that this lag fix creates a buffer between the real filesystem and the android system. This buffer should reduce the amount of disk I/O required for all operations by utilizing EXT2 buffering, as well as not writing file access times to disk, etc.
Folders that are currently supported:
/data/data
/data/system
/data/dalvik-cache
/data/app
/data/app-private as a symlink to /data/app/app-private
/dbdata/databases is not supported. It appears to be ROM backed, and can cause problems if overwritten.
Benefits over version 1
1.5GB of application data available, with no data loss.
e2fsck of the EXT2 partition on each boot.
Correct busybox version included! YES!
/app and /app-private directory included in the fix for faster application installs.
/dbdata/databases included in the fix, expected to give a big performance boost for apps that use it.
Mounts instead of symlinks for extra performance as OS does less work (about 100 or so more quadrant).
Benefits over other lag fixes
Open source, with full comments and ease of editing.
Works on any and all firmware versions, including any yet unreleased froyo versions (that don't change file structure).
Credits
Big thanks to mimocan for putting us all on the right track in how to sort out lag problems!
Big thanks to ykk_five for showing us all how well loopback filesystem mounting works!
Big thanks to cyanogen mod for e2fsck
Requirements for One Click Lag Fix 2.0
Rooted phone - http://www.addictivetips.com/mobile...t-samsung-galaxy-s-i9000-with-a-single-click/
Windows computer with SGS Drivers (Samsung Kies), or the ability to read through the batch file and run it yourself.
(Beta Release) The ability to reflash your device if something goes wrong.
No other lag fix installed. If you installed One Click Lag Fix 1.0, then use the uninstall function which came with that lag fix before running this lag fix. (Untested but assumed to be working, please help out here.)
1.5GB of freespace on Internal SD Card for swap files while the fix is working (/sdcard).
"Internal phone storage" in Settings->SD Card must read greater than 500mb (0.5GB) of free space.
How to run One Click Lag Fix 2.0
Place your phone into USB debugging mode: Settings->Applications->Development
Attach your device to your computer. Do not mount the drives.
Download the attached ZIP file.
Unzip to a folder of your choice.
Double click "lagfixme.bat".
Don't double click "unlagfixme.bat".
Wait for it to complete.
You will need your phone to be unlocked when it runs the script, so that you can accept the permissions request that will appear on your device.
How to remove One Click Lag Fix 2.0
Double click "unlagfixme.bat"
Wait for it to complete.
Known Issues For All Versions
Some custom firmwares use up all available space in /system. This fix requires some libraries to be placed in /system/lib. These libraries are used to create the filesystem properly, and to check it for errors on every boot.
If your firmware does not have the available space (around 1mb) in /system, do not use this fix! Your phone will not boot and will have to be restored from backup / reflashed.
Current known firmwares with this issue: None yet. Please provide the firmware version+mods if you encounter this issue. It will show up as an out of space error in the log, under 'Copying libraries'.
Known Issues 2-1, 2-2
Paid apps from the market have issues.
Google maps and other pre-installed ROM-backed applications have issues.
2-3 Changes from 2-2
/dbdata has been removed. This fixes maps issues.
/app-private is now a symlink to /app/app-private. This fixes paid apps issues.
Alternate installation methods for similar fixes
Tayutama has made an update.zip version that is easy to install - http://forum.xda-developers.com/showpost.php?p=7632258&postcount=208
Chainfire has a .NET version of this fix with some nice features - http://forum.xda-developers.com/showthread.php?t=751513
Frequently Asked Questions
Q: My apps are force closing while this fix is running, and I can't use my phone!
A: By design. The script has backed up/copied your apps over to the internal SD card (remember the requirement about 1.5GB of free space on the SD card?). It is now overwriting them with a 1.5GB file. As the file overwrites an app that is trying to do something, it will probably force close. This is normal.
Closing all running apps, and removing widgets before running this fix can make the process much smoother, though.
Q: The script can't transfer files to my phone / The script can't run / Help help I'm dieing!
A: Read the first post again.
Q: My paid apps from the market don't show up.
A: I will hopefully have a fix for this sooner or later. Hold tight! It's in the known issues. I don't have access to paid apps, so I can't test this.
Q: Does this need busybox?
A: No, busybox is included.
Q: I only have 200mb of free space now! What gives?
A: The lag fix has made a 1.5GB file, and is storing all of the data inside there. The side effect is that the free space meter is now incorrect. Sorry, this can't be helped.
You can check real free space by using ADB like this:
Code:
adb shell
su
busybox df -h
Q: When I use a backup tool, the backup is now 1.5GB big! It's taking forever!
A: The backup tool isn't designed to work with this fix. It will work, it just won't work well. Hopefully this fix will be short lived, and either Samsung will give us a new update, or someone will give us a good custom firmware that can natively mount what we need, where we need it. Or someone might come out with a better backup manager. Until then, we suffer.
Q: Will a reflash wipe this fix?
A: Yes, a reflash will wipe everything this fix did.
Q: Can this brick my phone?
A: If you know how to get to the download mode from power off (hint: volumedown+home+power), then almost nothing short of throwing your phone off a tall building can actually brick it. If you can't do this though, or don't know someone who can, then you're better off waiting for samsung to release a fix. Anything that moves files around on your device has the potential to break things, and this fix has no QA department.
Q: Why is /dbdata not included in your fix, but other people have included it?
A: Other people have included it in the same way my 2-2 fix includes it. However, /dbdata is ROM backed. This means that the real files are on ROM, and only the changes appear in the /dbdata folder. When copying or moving files from this folder, you would need to specify each folder by exact name to ensure that it was copied across, and each firmware can have their own names. (This is because RFS wildcard will not catch an unused ROM backed file.) In some cases, you can get lucky and have this work perfectly because you have already used all the files in /dbdata. There is no fail safe method to do this though, and /dbdata does not make a big difference to performance. (It is already on NAND flash.) If you want to try your luck, v2-2 is still available.
Q: Why does this lag fix work? Is it slowly destroying my phone?
A: Let's say an application counts from 1 to 10, and writes the value each time to disk.
Stock:
1 -> App tells RFS to write 1 to disk -> RFS writes 1 to disk -> RFS writes journal saying to changed the value on the disk.
2 -> App tells RFS to write 2 to disk -> RFS writes 2 to disk -> RFS writes journal saying to changed the value on the disk.
..
9 -> App tells RFS to write 9 to disk -> RFS writes 9 to disk -> RFS writes journal saying to changed the value on the disk.
10 -> App tells RFS to write 10 to disk -> RFS writes 10 to disk -> RFS writes journal saying it changed the value on the disk.
Total physical disk writes: 20. Speed: SLOW! Wear and tear on disk: HIGH!
Lag Fix:
1 -> App tells EXT2 to write 1 to disk -> EXT2 stores 1 in RAM.
2 -> App tells EXT2 to write 2 to disk -> EXT2 stores 2 in RAM.
..
9 -> App tells EXT2 to write 9 to disk -> EXT2 stores 9 in RAM.
10 -> App tells EXT2 to write 10 to disk -> EXT2 stores 10 in RAM.
..
EXT2 tells RFS to write 10 to disk -> RFS writes 10 to disk -> RFS writes journal saying it changed the value on the disk.
Total physical disk writes: 2. Speed: FAST! Wear and tear on disk: LOW!
This isn't exactly what is happening, but it gives you the general idea.
Q: Can this mod work on other Android devices? Would we see a performance boost on them as well? If not why is it limited to the Galaxy S?
A: SGS has very very good hardware, but it has some parts of it's hardware poorly implemented. The filesystem that samsung chose to use is custom-built using FAT32 as a base, RFS. It has a lot of the problems that FAT32 has, and should have been left back in the 90s, or even the 80s.
One of the big issues with it is how it handles multiple requests - it blocks. It blocks everything. When your mail app wants to read the mail you just tried to view, but your twitter app is busy writing a new tweat it just received, your mail app is forced to wait.
This is bad, but it could be worse! And it is... your twitter app didn't just get one tweat, it got 50 tweaks. It is busy writing the tweats one by one to the filesystem. This would be fine, since all modern filesystems will buffer writes, so instead of writing each one at a time, they will batch them together and write it as a big chunk. Uh oh - RFS does no buffering at all! After each write, it will also write an update to the grafted-on journal system. Guess what happened to your mail you were trying to view while all this happened? It 'lagged' and you got a black screen for half a second, before the mail popped into view.
Luckily the hardware on the device is so good that you usually don't even notice the problem until you have a lot of apps running, all writing their updates when you unlock the phone.
This is mostly speculation based on experiments done on RFS -- RFS is closed source, and we have no idea if the problems are just badly set settings (such as a block size that is too small), coding bugs in the implementation, or if RFS is just really that badly designed.
This fix just grafts a buffer on top of the RFS filesystem, using a very very simple and fast filesystem, EXT2. It fixes most of the issues by writing to RFS as seldom as possible.
So no, this fix won't fix other devices, since they're already running quite close to maximum speed. The SGS at stock is running nowhere near maximum speed, and this lag fix takes it a bit closer. You could probably speed up other devices by tweaking the filesystem settings to give them a big buffer or similar, but it isn't really needed. (I haven't actually tried to put an EXT2 onto any other Android phone, as I don't have any other Android phone, so this is just speculation.)
Q: My phone is fast now!
A: Yeah.
Oh, awesome. I managed to post this in the wrong forum. Doh!
Could a moderator please move this to Android Dev sub forum?
haha looks awesome dude but you are correct, wrong section im gonna try it now, will report in 5 mins!
A few people in the other thread said they had the first lag fix working on the captivate. Anything that might change that with this release? I came to download the old one, and here a new one is
abra-cadabra...
*POOF*
Done!
E_man5112 said:
A few people in the other thread said they had the first lag fix working on the captivate. Anything that might change that with this release? I came to download the old one, and here a new one is
Click to expand...
Click to collapse
The old one is still here. Nothing has changed that should stop it working on the captivate though, but it is completely untested. Use the 1.0 (which has had a lot of testing) until this one has been put through the paces.
sirphunkee said:
abra-cadabra...
*POOF*
Done!
Click to expand...
Click to collapse
Thanks.
RyanZA said:
The old one is still here. Nothing has changed that should stop it working on the captivate though, but it is completely untested. Use the 1.0 (which has had a lot of testing) until this one has been put through the paces.
Click to expand...
Click to collapse
E_man5112 said:
A few people in the other thread said they had the first lag fix working on the captivate. Anything that might change that with this release? I came to download the old one, and here a new one is
Click to expand...
Click to collapse
I'm running the manual ext2 fix with Q scores 2000+. I'll try 2.0 Util tonight and post feedback....
Someone got some benchmarks?
Maybe for xxjp3? I only reach 1900 in quadrant.. /:
Sent from my GT-I9000 using Tapatalk
gonna test report in 5minutes
RyanZA said:
The old one is still here. Nothing has changed that should stop it working on the captivate though, but it is completely untested. Use the 1.0 (which has had a lot of testing) until this one has been put through the paces.
Click to expand...
Click to collapse
I'm in the process of flashing back to stock on my Captivate so I can give this a legit test. I'll report back here and let you know how it goes. Assuming my Captivate doesn't melt I'll update my OP from the thread about the original fix in the Captivate section!
About what lag is this?
Sent from my HTC Desire using XDA App
Dominik06 said:
Someone got some benchmarks?
Maybe for xxjp3? I only reach 1900 in quadrant.. /:
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
Benchmarks are roughly the same as 1.0. You can expect about 100 points more on average though, at least on my phone.
I just removed the V1 version and finished the V2.
It finally finished and rebooted the phone. now it tells me my internal memory storage is full. None of my Widgets will load.
Looking i see only 14MB free in internal storage.
thoughts?
Zilch25 said:
I'm in the process of flashing back to stock on my Captivate so I can give this a legit test. I'll report back here and let you know how it goes. Assuming my Captivate doesn't melt I'll update my OP from the thread about the original fix in the Captivate section!
Click to expand...
Click to collapse
Just as long as you point out that this fix isn't heavily tested yet!
RyanZA said:
Just as long as you point out that this fix isn't heavily tested yet!
Click to expand...
Click to collapse
Oh I know, I'm going to emphasize that heavily, lord knows I don't want to get stuck on tech support all night
clubtech said:
I just removed the V1 version and finished the V2.
It finally finished and rebooted the phone. now it tells me my internal memory storage is full. None of my Widgets will load.
Looking i see only 14MB free in internal storage.
thoughts?
Click to expand...
Click to collapse
Thoughts? That's bad.
You should be seeing roughly 215mb free. Did you see any errors in the log at all?
Everything is working fine for me. First reboot after lagfix had some problems with downloading apps from market, but after a second reboot it got fixed.
"Biggest" problem now, is just the phone stating that my internal phone storage is too low, with an icon on notification bar that I cannot remove. Already deleted some .bak from /data folder, any more tips what I can delete to get rid from this message?
Regarding the fix. apps are indeed much more snappier, no lag on the system when installing apps from market, and overall if the phone would continue like this for the next 48 hours, lag fix form me is solved. I had some problems after some 24h, with some lag, even with the previous version of the lag fix.
clubtech said:
I just removed the V1 version and finished the V2.
It finally finished and rebooted the phone. now it tells me my internal memory storage is full. None of my Widgets will load.
Looking i see only 14MB free in internal storage.
thoughts?
Click to expand...
Click to collapse
Looking through my old V1 remove script, I believe I was leaving behind the .bak files! Nastyyy... I'll update V2 to remove those if they're there on install. Will hopefully clear up any problems.
This was the kernel thread but it is so full of question that it was renamed to Question and answer!
before ask search in the forum.
Guide to install:
http://sourceforge.net/apps/trac/androidhtc/wiki/HowToInstallWithAtoolsNand (Flash the phone)
http://sourceforge.net/apps/trac/androidhtc/wiki/HowToInstallWithAtoolsHaret (Dual system windows/android)
If you have "install module error" please install the android update on sourceforge. Read more here:
http://forum.xda-developers.com/showthread.php?t=848921
Awesome job on this l1q1d, i finally got around to getting the git set up on my computer yesterday so in can modify and compile so i'll try and get coding when i have some free time Thanks for all your efforts.
I have some memory issues with both 3-10-2010 and 4-10-2010 kernels. The memory usage is really high and my launcher(launcher pro) keeps getting closed/restarted all the time even without opening any other apps.
Here for testing...
Glad to see this thread started!! Thought dev for Kaiser had seen its end. I'm no coder but can help with testing.
Hey L1q1d, this isn't by any means vital but i find it annoying and don't know if any other kaiser users have found this. If i turn the phone on and don't unlock it before pressing the power button again (i.e. just to check the time), there is a relatively long delay before the screen turns off. If i unlock the phone and then press the power button it turns off instantly. I have attached the logcat from when the phone is turned on and then turned off, i have also indicated where it locks before turning off the screen. I'm looking into it but if you have any pointers or don't experience this with your device let me know please
-Arturo- said:
I have some memory issues with both 3-10-2010 and 4-10-2010 kernels. The memory usage is really high and my launcher(launcher pro) keeps getting closed/restarted all the time even without opening any other apps.
Click to expand...
Click to collapse
Ok scratch that looks like the problem has been caused by having data on ext2 partition.
The kernel 2.6.32 runs way better than previous, but i have a persistent fail that knocks out the screen, at start i can see a message saying "msm_i2c.0: Bus still busy, status 2100m intf 100" and another more saying "msm_i2c.0: Error waiting for notbusy". ¿It is a common fail or it's only mine?
Hi
the problem is I do not belong here
I tried several variants android
the Caller ID does not work
basic configuration of network settings, but it is not good
if you want to set up an error message is incorrect sim, and it is no longer a network
something that is not a solution?
L1q1d, good work. Some of the changes you have made, such as nand, affect all of the related phone types. So, you might want to at least mention them on the vogue kernel thread. On the other hand, the keypad and battery code is not used by vogue. As you know, Polaris uses the same battery code as Kaiser.
I'm thinking two changes for battery code:
a) going back to max voltage and current instead of average, to work better with poor batteries. My old battery sometimes has deep dips in its reported voltage, causing a recalibration to 5% capacity when it really has more like 40%.
b) the recommended capacity calculations at high and low calibration points should be "recommended = battery_capacity - (new - old)" instead of "recommended -= (new - old)". As things are, the recommended value is pretty close on the first calibration, but any subsequent calibrations apply the same correction over and over again, making the recommended value go negative or insanely positive. Of course I cannot remember the names of the variables.
@L1q1d
This is a nice idea to make this thread for kaiser users.
Today I tried the latest kernel 4-10-2010 with fresh froyo 2.2.1 (nand installation). First the system works well. But after installing the ADW.Launcher from the market and after a reboot I got always chrashes from this launcher and I never had this before with any other kernel and the launcher version has not been changed. So maybe I have the same issues then Arturo. Then I tried the app task killer but it chrashes after starting it (same problem). I think these problems could be memory issues in the latest kernel version.
Keep going on your nice work for kaiser
l1q1d I have just got a framework exception and as usual 90% of apps don't work anymore. It occured using the latest kernel.
Also I still keep getting those launcher pro redraws It didn't happen while using the 2.6.25 kernel. Has the memory management been changed in the new kernel?
Do you use compcache? Like wlan, compcache uses kernel drivers that have to match the kernel version. I use compcache with backing store on 4th partition of sdcard.
Sent from my Full Android on Vogue using XDA App
n2rjt said:
Do you use compcache? Like wlan, compcache uses kernel drivers that have to match the kernel version. I use compcache with backing store on 4th partition of sdcard.
Sent from my Full Android on Vogue using XDA App
Click to expand...
Click to collapse
Yes I do. I ripped the compcache.sh file from latest dzo's fresh froyo build.(I remember reading Kalt Kaffe's post about getting compcache to work with the newest kernel a while ago so I assumed that it has been sorted out and we can enable compcache with new kernel) I'm on NAND at the moment with both system and data. I've tried system on nand and data on ext2 partition but the launcher redraws were killing me, every time I opened opera mini and then closed it the launcher was closed and I had to wait for it to load into memory again.
I'm back to system and data on nand at the moment with new kernel and it's much much better but still it happens from time to time. I've never experienced launcher redraws with the old kernel so I don't really now what;s wrong.
About the 4th partition....you mean swap, right?
When I was on nand +sd card I had 3 partitions 1) fat 32 then 2) ext2 about 30 mb(I don't know what for is the first ext2 partition but i remember that i couldn't install data to sd card with only one ext2 partition) and finally 3) second ext2 partition for data about 300mb. So by creating the third ext2 partition I would activate swap in compcache? I've never tried as I heard that it might used up the sd card faster. also I only have two sd cards 6gb(class 4) and 12 GB (class 2) so I think i would probably need class 6 for swap file?
The compcache-required modules are included in the 2.6.32 modules attached to my first post of this thread. Those files should work with any recent 2.6.32 kernel. I would suggest that we should be able to get modules the same place we get zImage and NBH files.
I wouldn't recommend backing store for everybody. It works for me, with my 8GB card, but I'm not sure it ever even writes anything to the swap partition. And, yes, my fourth partition is a swap partition. Kallt-kaffe's latest compcache.sh script should work fine.
An easy way to find out of your compcache is working: use the "free" command from the command prompt. If swap is shown as zero, compcache is not working. You can also see failures in the dmesg log.
n2rjt said:
The compcache-required modules are included in the 2.6.32 modules attached to my first post of this thread. Those files should work with any recent 2.6.32 kernel. I would suggest that we should be able to get modules the same place we get zImage and NBH files.
I wouldn't recommend backing store for everybody. It works for me, with my 8GB card, but I'm not sure it ever even writes anything to the swap partition. And, yes, my fourth partition is a swap partition. Kallt-kaffe's latest compcache.sh script should work fine.
An easy way to find out of your compcache is working: use the "free" command from the command prompt. If swap is shown as zero, compcache is not working. You can also see failures in the dmesg log.
Click to expand...
Click to collapse
Excellent N2rjt i think you just found the cause of my issues. I updated my system with the modules you have linked enabled compcache again and then i entered the "FREE" command and swap shows zero. So the compcache is not working this must be the reason for constant launcher redraws. Now what could be the cause of "broken" compcache?
Sent from my Full Android on Vogue using XDA App
lzo modules are now included in the kernel, you need only ramswap. probably compcache script have some problem with it.
Ok, guys I got a compcache.sh file from the latest dzo's froyo and compcache is finally enabled. I will be testing the device to see whether the issues are gone. Thanks for your help.
Bug: white screen, Android still alive
How I got a white screen:
AT&T Tilt-flavored Kaiser, latest kernel and dzo's Fresh Froyo, both built from current git code.
I was typing on the hardware keyboard, actually entering a message for xda-developers. I wanted to say "dmesg | grep ds2746", but couldn't find the "|" symbol. I remembered that the hardware keys for the soft keys (between R-T and between I-O) have some symbols mapped to them, so I was trying different Fn- and Symbol combinations of those keys.
Eventually I hit Fn-(Left soft key), and got a text screen with dmesg logs.
Okay, how to get back to a graphical screen? I tried a few keys that didn't take me back, then had a brilliant idea, hit the red hangup key.
That blanked the screen, but when I hit other keys to wake up, I had a white screen. Yet, adb logcat verifies that the phone is still running Android, and it is even responding to my touches, just I can't see anything except white.
Edit: can recover by using Fn- keypad right soft key.
Battery issues?
If anyone has battery issues, please open a terminal, and type this:
> dmesg | grep ds2746 > /sdcard/dmesg.log
and send the dmesg.log file.
Thanks!
I am super-curious if & how anyone here is using Link2SD successfully with CM11 (on the Epic 4G, specifically).
I've tried scouring these forums, and the Internet in general, to figure out the best way to get this to work...
But everything that I've tried, it all seems to be working great, only up until the first time that the phone reboots, then it all goes to hell.
I am wondering if there are any extra steps to follow, specifically for the Epic 4G, or any particular pitfalls known to avoid?
That's why I wanted to ask here, specifically to Epic 4G users...
If you are getting Link2SD to work well with CM11, then please chime in here, and can you explain how you got it all set up and working well?
(I feel like this is the one last thing that if I could conquer it, then I could really continue to get a lot of life out of this phone... as it stands, it seems too risky to put much faith in Link2SD, because if the phone happens to spontaneously reboot while I'm out running around, then I'm screwed because so many apps just disappear, and then it's a pain to re-download, re-install, and re-setup each of them...)
Thanks in advance for any help,
AS
I am using Link2SD on my Epic 4G with CM11 with some success. I just did a reboot, and as usual lost any icons that had links created in Link2SD, so I go to the app locker & re-add them to my home screen. This is typical of what happens on a reboot for me. One thing I did notice is that it takes a minute or so for the deleted app icons to show up in the app locker again, so if you are reinstalling them, it may be a matter of waiting for them to show back up. Also on occasion(not this time), Link2SD will prompt me about a problem with the links and then prompt me to reinitiate the partition or something to that affect. Once I do that and it reboots, the app icons are still gone, so I just re-add them. Anyway, I know its not a perfect solution, but with this device its better than running out of RAM. One last thing, needless to say, I only create links for enough apps to free up enough RAM to keep my Epic working properly.
I've finally got a system going that seems to work for me, and so I thought I'd share some things.
I'm on CM11 (as of today, cm-11-20140602-NIGHTLY-epicmtd.zip) and I'm using Link2SD.
HERE'S A "GOTCHA" THAT HAD ME PULLING MY HAIR OUT FOR AT LEAST A DAY OR TWO:
Link2SD was having problems mounting the 2nd partition - it would just say "Mount script cannot be created." or something like that (not a very helpful error message), no matter how many times I rebooted and tried again. What I *finally* figured out (somehow), was that this error was being caused by /system being completely full. When I went and deleted a few things from /system (such as goofy wallpapers or that 'Apollo' app that I never use), then Link2SD was able to successfully create the script, and then I'd reboot and could use the 2nd partition successfully.
It's still a little aggravating that any reboot of the phone will cause all of my "Linked" apps to disappear - I've played with this until I am blue in the face, and have resigned myself to accepting that this is just "how it is" (?) - but I'm now using Titanium Backup as my workaround.
STEPS I TAKE WHEN THE PHONE REBOOTS:
1) Go into Link2Sd and make sure the 2nd partition is usable, otherwise recreate mount scripts (deleting wallpapers/Apollo if necessary)
2) Under Link2SD's "More" menu, perform the following:
a) Clean up the 2nd partition
b) Clean up the dalvik-cache
c) Clear all app caches
3) Restore apps from Titanium Backup
a) starting with Facebook app (the biggest hog) and then immediately go and make Facebook a "Linked" app again
b) restore a few more apps (to internal/phone), then go and shuffle those over to "Linked" apps via Link2SD
c) (repeat step 'b' until all apps are restored and "Linked" via Link2SD
^ This is the only way I've been able to get this to work for me... but now I can put about as many apps on the phone as I'll ever possibly need, and I have to say everything is running pretty smoothly now - but if anyone can see a better way, or how to improve what I'm doing, then I'm all ears... please let me (us) know.
Thanks!
Apex launcher doesn't lose the icons. I can free about 66MB of system space by swapping the launcher, deleting CM wallpapers, live wallpaper and Google keyboard.
I verified link2SD plus was not working properly but free link2SD works as advertised. For me, just installing the plus version will break the working functions of the free version. The free version scripts, links and launcher icons survive reboots. The plus version continually lost mount and wouldn't properly clean up the second partition and was not copying the lib files and placing them in the second partition.
Edit: per the developer's request, after verifying free link2SD was setup and surviving reboots, I added plus link2SD and rebooted: OK so far. Next I linked a file with plus version; OK until reboot. The application was not found except in directories. Dalvik cache cleanup finds the dex link and file in second partition as unneeded files. Had to manually delete all the files and links for the broken application and reinstall it. Also had to uninstall plus link2SD to properly link again. Sent the results back to developer.
Sent from my SPH-D700 using Tapatalk
Edit: 6/20/2014; link2SD 3.4.8 fixed the reboot issue for the link2SD Plus version for me. Sent email to developer to thank him for the fix.
See post #8.
Update on my last entry:
I emailed the link2SD developer and got a reply asking me to check the plus version again. In my reply back I linked him to this thread.
Another tip to add for nightly flashers that use link2SD and modify the zip prior to flashing: pull the mount script, 11link2SD, found at /system/etc/init.d and move it same location on zip before flashing. If retaining data, ie: dirty flashing; the mount securely retains your apps after flashing new nightly. Just checked with free version of link2SD: works.
Sent from my SPH-D700 using Tapatalk
Arson Smith said:
I am super-curious if & how anyone here is using Link2SD successfully with CM11 (on the Epic 4G, specifically).
I've tried scouring these forums, and the Internet in general, to figure out the best way to get this to work...
But everything that I've tried, it all seems to be working great, only up until the first time that the phone reboots, then it all goes to hell.
I am wondering if there are any extra steps to follow, specifically for the Epic 4G, or any particular pitfalls known to avoid?
That's why I wanted to ask here, specifically to Epic 4G users...
If you are getting Link2SD to work well with CM11, then please chime in here, and can you explain how you got it all set up and working well?
(I feel like this is the one last thing that if I could conquer it, then I could really continue to get a lot of life out of this phone... as it stands, it seems too risky to put much faith in Link2SD, because if the phone happens to spontaneously reboot while I'm out running around, then I'm screwed because so many apps just disappear, and then it's a pain to re-download, re-install, and re-setup each of them...)
Thanks in advance for any help,
AS
Click to expand...
Click to collapse
I'm using link2SD for all minus 16gb internal android device. Here is what i do in epic 4g, currently on CM11 20140523, use 20131209 gapps. I just write the part involved link2sd :
1. Buy atleast 16gb microSD and class 10 is a must, make 2nd partition (usually about 4gb - 6gb) as ext2 - ext4 (depends on the OS).
2. Device rooted, install titanium backup & root explorer 3.1.3 (make sure the root explorer working). Uninstall system apk (one of the launcher, whisper push, terminal emulator (I prefer use better terminal emulator, install as user app), CM filemanager, etc - still more that can be uninstalled for more space in system.
3. install link2SD, pick ext2 - ext4 (depends), dont restart yet. go to setting, uncheck everything then restart.
4. After back to launcher, open root explorer, go to root/data/, check app & dalvik-cache folder, press copy. Go to sdext2 folder, delete lost&found folder (usually there), and paste. So the app & dalvik-cache folder is there now (you could copy data/data folder too if you really want maximum extra space in internal, but in epic 4g i didn't copy data folder because it's enough space).
5. At the sdext2 folder, long press app folder, select "link to this folder", go to root/data/, press "create link" - "yes". Then go to sdext2 folder again, long press dalvik-cache folder, select "link to this folder", go to root/data/, press "create link" - "yes". Do the same if you copy data/data folder to sdext2 folder.
6. Reboot. Done. Then installing others app or restore with titanium backup.
I hope this is useful. Some Screenshot attached.
Hello
Thanks for that solution.
I`m searching for this solution since 1-2 weeks.
I had the same Problem on xcover 2 Link2SD.
Now it`s clear i have installt Link2SD and works perfect for just 3-4 days then i upgrade to Link2SD plus and then it happend like the Threat above.
I`m wondering that Lin2SD works perfectly on CM11 and if you go to Link2SD plus for money and this don`t work.
Free works perfectly and paid work not.
I have go back and everything its fine.
I hope the autor will fix the problem then i go back to plus.
Thank Thanks Thanks works fine!
regards marle.m
Good news! It appears the link2SD version 3.4.8 released today has a bug fix to survive reboots for linked apps when linking with link2SD plus version.
So far, I've only linked one app with plus version enabled and it survived one reboot. Then Ⓘ linked the data folder and rebooted again which also survived the reboot.
Looks like plus version is fully functional; I'll update if it fails some time later.
Sent from my SPH-D700 using Tapatalk
Finally had a chance to sit down and mess with this...
Yeah! Success! Freeing up space in /system worked.
Next question...Will I have to remove the bloat prior to flashing from now on? ie no more CyanDelta easy flashing
Anyone have any Scripting-Fu to come up with an automated method of stripping out said bloat?
thx sno
Snoshrk said:
Finally had a chance to sit down and mess with this...
Yeah! Success! Freeing up space in /system worked.
Next question...Will I have to remove the bloat prior to flashing from now on? ie no more CyanDelta easy flashing
Anyone have any Scripting-Fu to come up with an automated method of stripping out said bloat?
thx sno
Click to expand...
Click to collapse
I was thinking the gapps could be modified at the updater-script to remove some system bloat. Then remove some bloat from that as well. Most remove their own bloat choices so maybe a diy tut would be more useful?
I agree, the script would make the nightly flashing easier.
Sent from my SPH-D700 using Tapatalk
Just realized that if using Link2SD Plus to multi link all folders of an app to sdext2 after a clean install is still broken, if using intended method. Apps linked this way are missing after reboot.
Working on a safer suggested method that focuses more on removing apps from Gapps but also removing some other system apps after flashing a nightly that requires no modification of the nightly zip on a computer. Have to focus on linking only a minimum amount of apps with free Link2SD considered less risky to move, like larger stand alone apps, not needed tools.
I've got a working script and method that works but the risks to be avoided need to be detailed along with the tut to script and tool your own modified Gapps that minimizes the flash to flashing the nightly as-is and then flashing a custom Gapps that includes preferred launcher and restore methods.
Removing CMWallpapers, Apollo music and Trebuchet launcher. Substituting blacked out Google play. Replacing removed apps with Apex beta test launcher for test group, blacked out Pandora (these will be installed at /data partition where they can be easily uninstalled or updated) I use my own borrowed wallpaper.
Along with the removed bloat from Gapps, this frees a bit more than 40 MB of system space.
Sent from my SPH-D700 using Tapatalk
UPDATE: the latest version of Link2SD (3.5.2) has "fixed the bug that causes linked apps disappear on reboot when internal data is linked".
So... if you've also ponied up the buck or two for Link2SD Plus (as I have), then this finally works again like you'd always hoped it would.
I just loaded a bazillion apps back on the phone, and have been able to reboot multiple times without losing them.
The only time I "lost" them for a moment was after flashing to the latest CM11 nightly, but then doing the "Recreate mount scripts" and reboot brought them right back, with no other shenanigans necessary.
(Just wanted to let people know, because this is such a relief to me now....)
HURRAY!
OK I'm trying this again. Reboots are fine as long as I don't select quick or soft reboots; I lose mount, linked apps not installed.
Now need to try the clean install of nightly.
Snoshrk said:
Finally had a chance to sit down and mess with this...
Yeah! Success! Freeing up space in /system worked.
Next question...Will I have to remove the bloat prior to flashing from now on? ie no more CyanDelta easy flashing
Anyone have any Scripting-Fu to come up with an automated method of stripping out said bloat?
thx sno
Click to expand...
Click to collapse
One possible solution:
more scripts to limit steps
Another possible solution (click link)
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