Related
Attention, new stable rom for our legends!
From a Spanish cheff, SuperFroyo MVZ Legend 8
The thread is in Spanish, but you can download the rom from the link "Descarga" in red.
The thread: http://www.movilzona.es/foro/topic2567.html
Thanks to superatmel for his hard work, we finally have an alternative with Froyo in our machines.
EDIT: The rom is working FINE finally right now. Download and test!!
Enjoy this rom from Superatmel
EDIT2: Translation of the first post of the SuperFroyo ROM:
SuperFroyo MVZ 8 for HTC Legend, MovilZona edition
It´s installed from the recovery, as every time you install a ROM. Don't worry if takes a long time to get the first splash. It´s absolutely normal because it executes the config files in the first boot.
Added by manudas: It really reboots twice, the first time for the overlay filesystem, for having read/write access to the system partition.
You must have the Legend rooted. If you don´t know how to do, please search in this forum before asking.
I strongly recommend a full formatting to the SDCARD with three partitions EXT3 512MB / LinuxSwap 64MB and the rest in FAT32. You can do it from the recovery, but remember to save your data before (pics, music, etc…). This is because some directories are created in the sdcard (Android) in which records data I found to negatively affect the rom. PROVEN!
-------------------
WARNING!
This rom autoinstalls itself, and also restarts twice after installation. Ie, reconfigures itself.
WIPE is recommend before the installation, because it has many changes. After installing the rom leave it alone for at least 4 minutes, not touching the screen, because this is the time it takes to finish of installing everything. Then you can setup the rom, but I recommend that you skip the google config, pressing skip button, and once in the launcher you can configure the rom as you like. This is because otherwise the phone will autoconnect to the market, and begin to automatically download all the applications you had installed. Al this can saturate the terminal because it does everything at once. Besides, if the phone connects to the market, background image that you had prior to the rom flashing will be there again, and then you will ask how is possible that after a wipe the bottom appears as you had before.
If you follow my instructions you will do a clean install. Then you should enter the market and install a free application to refresh the applications you have installed in the terminal and to see if everything went well you should go into "Downloads" and see if appears at least an update of SupSetup I'll post this afternoon to check .
Very attentive to you who do restorations of any kind against the rom cause you can have problems. (I mean backups, including their own SupSetup least in the application section). Special attention to restore configuration data of any kind. Under doubt, the best it´s not doing it.
Remember that the installation is at your own risk.
- Added Apps2sd in SupSetup. Now even allows the deactivation of this without having to WIPE. NEW! Do not be alarmed if you reboot, read the posts !!!!! (Better don´t use the applications move feature of Froyo)
Don´t activate Apps2sd without at least once you have restarted
Improvements in this version.
All versions are the same for all terminals
In 8
- SupSetup with integration to Legend
- Implementation of the base for HTC Legend
- Bug fixed Chamber
- HTC Legend Custom Kernel (2.6.29.6 reissued)
- Deactivated perflock for changing CPU frequencies (Only Legend)
- Implemented Swap Legend, not Compcache
- New edition of Framework for all bases (Nexus, Magic, Dream, Legend, Galaxy S)
- Preparation for FM (But not yet available)
In 6.6.4
- On base Froyo FRG83 2.2.1
- Kernel 2.6.35.6 (Nexus One, Magic & Dream)
- Digital retouching (the Chinese muiu)
- More stable Camara
- Google Apps updates
- Etc. ..
In 6.6.2
- New Gmail upgradeable
- New upgradeable Street View
- New way of setting up the internal processes with better results
- New SupSetup V12 14.06
- Edited the rill for a better and stable 3G HSDPA coverage
- Various internal improvements
In 6.6
- New management of the post installation Rom
- New way of SupSetup for disabling applications of the rom (Attention!! Disable is not uninstall)
- New very optimized kernel and removed processes that do not use the Nexus
- New SupSetup V12 v14.00
- New Launcher Pro if activated from the SupSetup configured for higher performance.
- Appear new SupSetup's with more applications to disable!!
- Now install themselves the voices for the GPS
- And more internal improvements for a brutal stability. That if it´s installed with a generous WIPE!
- Adding the Control of energy, I recommend activating the cells that are in the last captures for battery consumption settings, because for example when you turn on wifi automatically pass to 2g for lower battery consumption or you change the data will change also to 2g, or if the wifi is enabled then will activate the sync automatically, etc ...
In 6.4
-Added new option in SupSetup with the direct integration against the system (Optimize the system)
- New setup for the Launcher Pro: to activate it from the SupSetup, go to applications! Important if the Launcher Pro is enabled, for activating the future updates of the market you have to execute the option Optimize system!
- New Shazam
- Rescheduled framework for the implementation of the new option of SupSetup
- Kernel settings
- Adding the Control of energy, I recommend activating the cells that are in the last catch for battery consumption settings.
- Etc ...
In 6.2
- Fix Shazam
- Recompiled the framework to eliminate obsolete processes
- A small graphic touch
- Added black and white bar from the jrosmetamorh. (You must enter the program and select the folder jrosmetamorh / SuperFroyoBNegra or SuperFroyoBBlanca, wait to finish installing and reboot).
- Set some xml framework
- New icon of the battery.
- Various internal improvements
- This rom is very stable.
In 6.1
- All Cyano improvements
- Fix for flash player to install without Wipe (Nexus only)
- Improved 3D Gallery
- New ADWLauncher 1.1.5
- SupSetup V12 12.94
- Updated all apps
- Added icon headphones
- New kernel 2.6.34.5
- And as always own improvements
In 6.0
- Fixed a bug in the CPU frequency
- Fixed issue with FlashPlayer, if it does not work, apply "the force be with you" from the SupSetup, and wait to restart. (Solo Nexus)
- Fixed problem with Speech Sinthesis.
- Edited the battery again to display up to 100% load
- Revert SoundRecorder
- Added Series for Android
- Optimized Kernel for lower consumption. (Removed unused drivers)
- And besides of my optimizations, all from Cyanogen too
In 4.4
- Added restart in normal mode, recovery and bootloader
- Enabled again hsdpa
- Fixed bug in the battery icon
- New Wallpaper.apk
- New sounds and notifications in addition to integrating the lock & unlock from Iphone
- Many of internal improvements in the libraries
- Camera with manual focus touching the screen.
- Added Launcher Pro activating it from the SupSetup (applications menu)
- Added File Explorer activating it from the SupSetup (applications menu)
- ADWLauncher updated to version 1.1.4 (thanks AnderWeb)
General
- New option in the SupSetup Applications
- Added Development (Disabled from SupSetup)
- Added STK sim provider (Disabled from SupSetup)
- Added File Explorer from the SupSetup (Disabled from SupSetup)
- Terminal (Available from SupSetup)
- Added news and weather
- Implemented Flash Player 10.1 (only Nexus)
- Added Google Chrome to Phone. Allows you to launch pages from pc to mobile with one click, after installing the plugin on Google Chrome on your pc.
- Now you can customize the toolbars notifications from the Spare Parts.
- New application for viewing videos.
- Control the music in the lockscreen activated from the Spare Parts
- Many and funny improvements in Spare Parts for the control of the rom.
- You can modify all the colors of the rom including notification bar (text notifications, time and date)
- Now SupSetup applies directly the changing of CPU frequency
- Modified the management of "the force be with you", with better results of suffering sporadic FC's.
- Fixed the problem of always-on Bluetooth from SupSetup
- Implemented LinuxSwap and CompCache, but warning, you can only enable one of the two. If you enable one the other will be disabled automatically (Thanks Tole)
- And many small modifications to control the system.
- Optimized all the apk's png
- Take a look at the new Spare Parts integrated settings.
- Improved management of root
- New Market Management
- Now enabling APNs from SupSetup automatically applies
- Development is disabled from SupSetup
- New options in the Spare Parts that can even choose which applications are installed if not activated Apps2sd (better do not use)
- Wake Unlock & Wake up
- Sound Recorder can record conversations
- Updated Spanish translations
- Added Speech Synthesis (To the voices of the GPS)
- Added provider SIM STK
- Now you can activate and deactivate the JIT from the Spare Parts
- Spare Parts and SupSetup integrated into the rom settings
- Bug fixed contacts and translations
- Redesign of the images of the framework
Applications
- Audio Manager
- Google Apps integrated default
- Maps with GPS 4.5.0
- New Gmail
- Shazam
- AndroidVNC
- Ebuddy
- Facebook
- SupSetup V12
- Twitter
- Wireless Manager
- Wifi status
@superatmel is great, very great. Can't wait.
Sent from my Legend using XDA App
Can I ask why I would want this over say the Cyanogen Mod froyo ROM?
not hating, just asking.
Also is it in English?
I think that is multilingual. This rom includes optimizations from cyanogen, as its author says, and many other of their own. You should try it and if you like it you stay, if not you can restore the previous. Furthermore, this will activate the FM radio in future versions.
wow great news! Finaly something fresh on legend scene! More chefs should work on froyo roms
Good!
thank you I'll try this one as soon as it's available.
PS: GPS does not work in Cyanogen for me, so I hope it's fixed in this one.
hoping that rom is multi language that avail english!
Anyway I think it would not be difficult to add some language support in case that have not english
manudas said:
Furthermore, this will activate the FM radio in future versions.
Click to expand...
Click to collapse
I laughed a lot on this one.
Not that it's impossible and I really wish the devs good luck on btips and that proprietary mess HTC created.
ali ba said:
I laughed a lot on this one.
Not that it's impossible and I really wish the devs good luck on btips and that proprietary mess HTC created.
Click to expand...
Click to collapse
I laugh because he laughed.
Rom is on servers, ready to download!
its huge 85mb... now downloading... after download flashing!!!
How is it?
I can not wait to try it. I'll download it now. Someone who has tried can give us the first impressions and tell us if in addition to Spanish it has English?
Well tried it but all i got was boot loop. It starts but at enter pin the phone reboots.
Same here.
Boot loops on pin code entering.
Did u wipe before flashing? I wanted to flash this rom to, but my SD card started to f*** with me AGAIN. Now trying to backup data and format it, if it would help.
Yes, I did.
same here wiped everything, but no go.
Wiped twice, reboots at the first screen (touch the android logo)...
Google Translate doesn't help much:
This rom installs itself alone, that is completely reconfigures.
WIPE recommend because it has many changes, after installing the rom to let her leave without touching recovery 4 minutes or more exactly because of that time will finish installing everything. Then you can already configure but I recommend you salteis the account settings to skip giving google and once in the launcher and set podreis rom to your liking. This is because otherwise the phone will Autoconnect the market and begin to automatically download all the applications you had installed and it saturates the terminal because it does hit, besides putting the background image that you had prior to the rom and then you ask me that as it is possible that if I install the rom to wipe the bottom appears to me that I had before. In this way you will do a clean install. Then you enter the market and instalais a free application to refresh anyone that you have installed in the terminal and to know that everything went well when you go into shock must appear at least an update of SupSetup I'll post this afternoon to check .
Very attentive to you to do restorations of any kind against the rom or program that you can have problems. (I mean backups, including their own SupSetup least in the section on applications), special attention to restore configuration data of any kind. Under the best not to doubt.
Remember that the installation is at your own risk.
- Added Apps2sd in SupSetup now even allows the deactivation of this without having to WIPE. NEW! Do not be alarmed if you reboot, read the posters !!!!! (Better not use the applications move Froyo)
Apps2sd not activate without at least once you have restarted
Hi, I tried to apply ext4 lagfix via CF ext4 Manager (CF-Root-ext4-v1.3-Addon.apk) , data was converted successfuly, system was not converted due not enough free space, which is normal as Chainfire said.
Please note that when first using the tool to convert, you will probably notice /system is not converted. If this happens, it is because /system does not have enough free space for the extra space overhead of ext4. You will need to free up some space on /system before the conversion will succeed.
Click to expand...
Click to collapse
Running 2.3.4 JVQ stock firmware with CF root.
But after reboot ext4 app have all choices grayed, so I cannot convert system or any other partion to ext4 or back.
It show "No rfs/ext4 partions found" and "unknow ,0.0MB, 0.0MB total"
Any tips appreciated. Thanks in advance
Roman
Which kernel are you running? Try changing kernel eg: Semaphore or galaxian. Then do a wipe cache and dalvik cache
Runnig CF-Root-XX_UNK_JVQ-v3.7-CWM3RFS on stock JVQ without other changes.
Thanks for advice
Problem is, that many kernels have logging disabled, I need logcat, ddms for developing
EDIT: Flashed semaphore, there is greenscreen while lock/unlock screen(minor issue),but other things seems fine, thanks!
semaphore has logging enable script
Quote :
"In order to control voodoo sound and BLN you have to download Voodoo Control and BLN control applications respectively from android market.
The max CPU frequency is by default 1Ghz.
You may use applications like Voltage Control or Pimp my CPU to control OC/UV.
In order to load various modules of the kernel copy the respective script from /res/scripts to /system/etc/init.d directory and give the script executable permissions. This is optional. It is needed only if you want to use this functionality. The scripts:
- enable_conservative (load conservative governor module)
- enable_cifs (load cifs module)
- enable_netfilter (load netfilter modules for firewall or WiFi, USB tethering)
- enable_tun (load tun module)
- enable_deadline (load the deadline I/O scheduler module)
- enable_binfmt_misc
- S05_enable_oc replaces enable_ocuv since 1.6.0 (enable overclocking)
Other scripts:
- enable_sm_cold script for SpeedMod cold preset
- enable_sm_warm script for SpeedMod warm preset
- enable_sm_neutral script for SpeedMod neutral preset (please note that this is enabled by default)
To enable logcat run the enable_logger script in res/scritps and reboot your phone."
Here is the link
Hope this helps.
NEW EASY INSTALLER, RECOVERY ZIP
Total overhaul of code.
*HELP WANTED, PM FOR RELEVANT DETAILS*
This software package was originally just made for my personal use to rectify the issue of my phone not entering deep sleep when idle and me not having access to a charger for the majority of the day while also improving multitasking because being my phone is also my build environment/office environment, I am frequently jumping around various apps that I'd prefer to keep open.
Things this package accomplishes on your phone (very simple and brief summary):
*Forces entry into deep sleep as soon as the screen is off (if enabled, on by default). It also has audio detection so you can listen to music with the screen off without unwanted deep sleep entry.
*Improves multitasking, no more apps having to reload/redraw when you switch back to them.
*Automatic odexing of all apps, including new installs (if enabled, pre-lollipop ROM's).
*Easy management of swap.
*CPU management. You can set your own values to be locked (no other app can change them) or let its device manager automatically set CPU frequencies and the governor you specify.
*Dynamic Max CPU Freq: When enabled (on by default) it will automatically scale the max CPU frequency value depending on the CPU load. This can help with governors that favor the high end of the frequency table too much by allowing you to save battery but have the CPU power available when needed, without having to adjust anything manually whenever you go from doing something processor demanding to having your phone sit idle.
*Fixes issues with several kernels where the touch screen is unresponsive after waking the device. No more inconvenient force reboots.
*Enables all idle and suspend states available (they are disabled by default quite often) and can help get your device into the lower C-States.
*Fixes broken links to firmware files caused by buggy init scripts on some ROM's.
New/Other features:
*New recovery flashable installer
*Force system wide GPU rendering and faster framerate.
*Fixes Dt2w and Sw2w lock screen freeze bug.
*Now compatible with KSM.
*Faster app loading and responsiveness. Key android services are given priority status for I/O and CPU resources.
*Multitask over 20+ apps simultaneously without any redraws and low-latency app switching (provided you have the swap space)
Tip: I use the large amount of unused space on /system to increase the size of that MaxOpt managed swapfile.
*Fixed the crash on boot issue between MaxOpt and some kernels.
Default MaxOpt config:
•Swap on, default MaxOpt generated swapfile size is 64 MB, with one made on /data, one on /cache, and one on /system if mounted rw.
•Auto-odexing off.
•Hotplugging compatibility on.
•User CPU settings off, auto-device manager on.
•Deep Sleep immediately on screen off enabled.
•KSM off (you must have a kernel that supports it to enable this option and have it work).
•Kernel settings on.
•Everything is forced to be drawn by the GPU.
All of the above listed features are user optional/tuneable.
For those who wish to only use MaxOpt for fixing the lock screen freeze bug associated with some kernels/DT2W/S2W use the following link: http://forum.xda-developers.com/showthread.php?t=3061589
If you would like to just use individual components or adjust program settings from a terminal app, here is an example usage and description of their individual functions as well as other useful documentation (VERY OLD DOC, NEEDS LOTS OF UPDATES):https://docs.google.com/file/d/0B_hgNZE_j5sVbEN4ZUtkS2p0bW8/edit?usp=docslist_api
Terminal Emulator is what I would recommend for use with managing MaxOpts' settings.
System Requirements (not entirely sure due to lack of public testing):
Busybox
A terminal app
A kernel that can best be utilized by these programs.
Please make a nandroid backup before using.
And here is the MaxOpt installer ( R2 1.0.6 ):
* https://drive.google.com/file/d/0B_hgNZE_j5sVaGdxV0FfODdxbVU/view?usp=docslist_api
Changelog:
R2 v1.0.6- Adjustments to write buffering and multitasking memory performance.
R2 v1.0.5a- Fixed a bug present in both this project and MaxLife where data wasn't validated thoroughly enough before using it.
R2 v1.0.5- Added a new completely experimental new user tuneable (on/off, default off) that changes runtime memory allocation values. Only activate it if you have a large amount of swap.
R2 v1.0.0- Totally rebuilt the project, installable with a recovery flashable zip now, kernel image installer is no longer compatible and is scrapped.
For those still getting crashes:
The issue still appears to be related to the device radio when it happens, so, after a crash could you please force reboot your device and try to disable mobile data when it boots before it crashes again and please post a copy of /proc/last_kmesg. Thank you.
Screenshots of battery screen showing time spent in sleep:
https://docs.google.com/file/d/0B_hgNZE_j5sVSjRUU0ZlX0UwUWc/edit?usp=docslist_api
https://docs.google.com/file/d/0B_hgNZE_j5sVSmNjYThkUzAtNGM/edit?usp=docslist_api
https://docs.google.com/file/d/0B_hgNZE_j5sVcWxJd0JyV09nMDA/edit?usp=docslist_api
Please thank if my software has helped you and please leave logs and descriptions of problems if my software did not work for you.
Wow, this looks amazing. Very nice work.
I Will be playing with this for the next few days.
Sent from my Moto G using Tapatalk
Damn this looks complicated as hell haha. Good job OP
Very nice job
Thank you very much everyone. Glad for the positive feedback, this is my first public software release. I daylight in a machine shop, so this was far from my field of expertise and a long learning experience for me
I tried it on faux kernel 014m.
But my phone bootlooped
I have faux clock app.
Is it causing the problem?
Thanks
One possible problem could be the boot image it made was over 10 MB depending on the size of the input one. If that wasn't the issue, did you disable signature checking? Also this is currently not ART compatible. It is also important that you run the installer from a partition that supports octal permissions, so the emulated sdcard is a no go.
Edit: it may be worth trying disabling the faux clock app too. I don't have that kernel or app to try for myself but this mod does affect CPU settings so it could be a conflict. If none of those work, I may have to look into updating my installer with an alternate method for incompatible kernels.
elrod16 said:
One possible problem could be the boot image it made was over 10 MB depending on the size of the input one. If that wasn't the issue, did you disable signature checking? Also this is currently not ART compatible. It is also important that you run the installer from a partition that supports octal permissions, so the emulated sdcard is a no go.
Edit: it may be worth trying disabling the faux clock app too. I don't have that kernel or app to try for myself but this mod does affect CPU settings so it could be a conflict. If none of those work, I may have to look into updating my installer with an alternate method for incompatible kernels.
Click to expand...
Click to collapse
I followed steps as below:
I put that 2 files in the data partition.
Then boot.img of faux.
I set permission 755 for both files and boot.img
Then from terminal I executed the command.
I got new_image.img
I repack the zip using this new boot image and flashed it in recovery.
Then I reboot.
Phone booted and stuck on "optimizing apps 1 of 98"
Then again same.
Also I had 700mb of free memory when I tried this.
When I again booted using faux kernel I had 450mb of free memory.
Can you guess what's going wrong?
Did you disable APK signature checking?
elrod16 said:
Did you disable APK signature checking?
Click to expand...
Click to collapse
Sorry I forgot that.
Where exactly should I put those 2 files.
Was I doing right to put them in data partition?
And after first boot can I enable signature verification?
Do I need to disable it before every boot?
Unfortunately for now it needs to be off whenever an app is upgraded or added, but can be enabled after the reboot that that happens on, and yeah, /data works
Even after disabling signature verification it doesn't work on faux boot.img
Am I doing right?
For whatever reason it sounds like the dexy binary isn't playing well with your phone, I'll make a new installer with the option of disabling it for incompatible setups for the time being, but the other ones should still work. I'll keep ya posted.
My rom is stock 4.4.4
I will try again with disabled optimization.
kedar512 said:
My rom is stock 4.4.4
I will try again with disabled optimization.
Click to expand...
Click to collapse
OK, hopefully that should be the only part of this package not working for ya. Keep me posted, I'll continue trying to figure this out if it persists.
elrod16 said:
OK, hopefully that should be the only part of this package not working for ya. Keep me posted, I'll continue trying to figure this out if it persists.
Click to expand...
Click to collapse
No luck bro
Same problem.Stuck at optimization.
Should I try it on Xperience kernel?
Its not working with faux.
kedar512 said:
No luck bro
Same problem.Stuck at optimization.
Should I try it on Xperience kernel?
Its not working with faux.
Click to expand...
Click to collapse
I would say yeah, try it with it and see if it makes a difference
Also did you try the new build with a clean restore? (Before any of the failed install attempts) Try not wiping the cache/dalvik-cache after install and flash.
I tried again but this time booted upto lock screen and rebooted.
I tried with new build.
after placing ./maxopt boot.img appears running with dexy enabled.
That means it's already working? If yes, have to do anything else?
Every time you turn the meter will have to repeat the procedure?
Sorry my bad english
hennymcc:
Important notice:
- You flash this image at your own responsibility. I am not responsible for any damage that might be caused by flashing this image (bricked device, lost data, ...)
- Flashing this kernel image will trigger the KNOX counter, so your warranty will be void.
- The image is only for S5 Mini SM-G800F (Exynos)
- The kernel is not tested well. It might be instable, crash your device, drain your battery, or even might damage your smartphone (e.g. if an OTG device drains too much power)
- Backup your data before flashing and check if the original firmware is present (e.g. at SamMobile)
Click to expand...
Click to collapse
Side note: Tripping KNOX counter might break some Samsung applications even after a factory reset. This might be due to secure storage(which is fixable), but for now be cautious if you depend on these features! This image will likley damage the Qualcomm variant of the S5 Mini, do not flash if you have a G800H!
Hello! :laugh:
I've been working on a custom kernel for a while for personal use but I thought some of you might like it.
Current feature list:
Patched to Linux 3.4.113
Fading LED notification (default disabled)
Added row I/O Scheduler
Added zzmoove CPU Governor(with temperature export)
Added PIE network scheduler(supposed to reduce latency, default disabled)
DriveDroid support
Universal Control Interface[UCI] (use the Synapse app to configure)
USB OTG
Boeffla sound engine (Only configurable via Synapse! default disabled)
Powersuspend with LCD panel hooks
1.5GHZ clock speed on processors with revision 2 and above
Double Tap 2 Wake
Voltage Control
MDNIE Hijack
F2FS Support
Haptic Feedback for soft keys
Compiled with Self built Linaro 5.3 toolchain
This kernel is currently only designed to work with the corresponding TouchWiz ROM and likely won't be able to boot custom ROMs. KitKat/Lollipop TouchWiz is also not supported!
If you have any questions about the included features (how to enable, what they do) you may ask in the Q&A until I update the thread.
About 1.5GHZ clock speed
So, as it turns out, Samsung had already done the work to push the 3470 to 1.5GHZ. The frequency tables were already there and all that needed to be done was to remove a soft limit set on it and voila! 1.5GHZ! The catch is that these tables only applied to the second revision of the SoC and above.
Possible reasons why Samsung set the limit:
The S5 mini comes out with both the older and newer revisions of the 3470 and Samsung wanted to avoid getting in legal trouble for selling a higher clocked phone as the same product
The higher clock speeds legitimately can damage the phone
As I don't have multiple S5 Mini's at hand I can't prove the first point, but the second point is more likely true. If you don't feel comfortable with the higher clock speeds you may lower the maximum to 1.4GHZ via Synapse, but the default clock is always 1.5GHZ due to the way in which the frequency controller works.
Current status : BETA
Credits:
andip71(Boeffla sound), faux123(Powersuspend), FrozenCow(DriveDroid support), ZaneZam(zzmoove), Linux Foundation(kernel patches), AndreiLux(Voltage patches for INT and MIF bus), Yank(MDNIE hijack), Samsung(F2FS)
On-board BusyBox by meefik https://play.google.com/store/apps/details?id=ru.meefik.busybox&hl=en
The authors are not responsible for the way in which their features have been implemented in this kernel. Do not post bug reports to them!
Flashing procedure will be the same as with this kernel.
Download current image here:http://forum.xda-developers.com/devdb/project/?id=10241#downloads
Chaneglog:
Code:
1.0
-Initial Release
1.1
-ZZMoove Update to 1.0 Beta 8
- Linux Update to 3.4.108
- Toolchain update
- 1.5ghz unlock for higher revision SoC's
1.2
- Ramdisk update
- Double Tap 2 Wake!
- UCI update
- USB OTG now permanently enabled
1.3
- Voltage Control (CPU, GPU, bus)
- Fixes for DT2W
- Linux Update to 3.4.109
1.4
- Intelliactive Removed
- Linux Update to 3.4.110
- MDNIE Hijack
1.4_L
- Lollipop Variant Now Live
1.4_L2
- Second Lollipop release
- Fixed OTG
- System partition can be remounted again
- Removed Frandom (Does not work so well in Lollipop)
1.5
- KitKat support terminated
- Fix annoying bootloader warning ("KERNEL IS NOT SEANDROID ENFORCING")
- F2FS Drivers updated and F2FS support improved (/data and /cache)
- Patch to Linux 3.4.111
- UKSM removed due to stability concerns
- SELinux policy support update (Latest SuperSU betas might need this)
- Switch to self built linaro toolchain
1.6
- Update to Linux 3.4.112
- F2FS drivers updated
1.7
- F2FS drivers update
- NTFS support enabled (eg. for reading USB HDDs)
- Kernel side haptic feedback on soft keys added (see second post)
1.8
- patch to 3.4.113
1.9
- Switchable OTG
2.0
- Updated to MM
- No longer need to install BusyBox manually to use Synapse
XDA:DevDB Information
G800F Custom Kernel, Kernel for the Samsung Galaxy S5 Mini
Contributors
CurtisMJ
Source Code: https://github.com/CurtisMJ/g800f_custom_kernel
Kernel Special Features: Boeffla Sound, Fading LED, Linux 3.4.113, row I/O Scheduler, zzmoove CPU governor, PIE netsched, DriveDroid support, UCI, USB OTG, DT2W, Voltage Control, MDNIE Hijack, F2FS, Haptic feedback
YOU MAY NEED TO REFLASH SUPERSU AFTER FLASHING THE KERNEL!
Version Information
Status: Beta EOL
Current Beta Version: 2.0
Beta Release Date: 2017-03-07
Created 2015-06-08
Last Updated 2017-03-07
Reserved
OTG switching
Credit to tobigun for the original code (I actually attempted it at some point but failed miserably).
Execute the commands in a terminal:
Turn on OTG
Code:
su -c echo OTG > /sys/class/sec/switch/otg_cable_type
Turn off OTG
Code:
su -c echo USB > /sys/class/sec/switch/otg_cable_type
(Haven't touched Synapse in forever, cannot make sense of it anymore, so no Synapse switch soz)
Synapse Issues
I had some trouble with colour choosers crashing Synapse under specific conditions. If Synapse keeps crashing when picking colours for MDNIE, please try the custom build available in the downloads section of this project.
IF THE DEVICE IS CRASHING WHEN USING SYNAPSE, THEN YOU HAVE LIKELY SET UNSTABLE SETTINGS! SYNAPSE WILL NOT PREVENT THIS, SO PLEASE BE CAREFUL WHEN CHANGING SETTINGS!
There are two ways to recover:
- Use your recovery to delete Synapse's data folder
- Factory Reset your device (Only in extreme cases)
Using PIE netsched:(likely not working with Android at this point in time)
Run following in root terminal or as init.d script
Code:
tc qdisc replace dev wlan0 root pie
tc qdisc replace dev p2p0 root pie
tc qdisc replace dev rmnet0 root pie
ZZMoove and profiles:
The zzmoove governor is highly recommended. It can be set to various profiles to mimic the benefits of various other governors. It'll even ensure the device doesn't overheat!
The profile can be set by setting the "profile number" tunable in Synapse to one of the number values mentioned here. Setting it will change a bunch of other tunables. You'll need to restart Synapse after setting it and save the changes for future application.
Notes on DVFS
Samsung's DVFS feature in their TouchWiz ROMs seems to get a bit shouty when anything other than the "interactive" CPU governor is active. It could also be the cause of rare kernel panics relating to CPU frequency tables(frequency controller expects something from the governor, governor doesn't deliver, panic). Since it also seems to cause a couple other unrelated issues, I'd recommended simply disabling it altogether(the easiest way being via Xposed)
Double Tap 2 Wake
This feature allows you to wake the device by double tapping on the screen while it is off. NOTE:Deep sleep is near totally inhibited while this feature is active, this means extra battery may be consumed. On a tweaked ROM you'll get 2-3%/hr on full standby, on non tweaked you'll get about 4-5%/hr, please keep this in mind while using the feature! Android OS suspension should be unaffected. The feature disables itself when a Samsung branded flip cover is closed, including S-View covers(no double tapping on the window). The feature makes use of the light and proximity sensors in order to detect whether the device is in a dark enclosed place (eg. A pocket) and disables itself in these situations as well in order to prevent accidental wakes (though that may still happen...)
MDNIE Hijack Example
Profile based of iPhone 6+ screen:
R: FF 00 00 - G: 12 FC 12 - Bu: 00 00 FF - C: 12 FF FF
M: FF 00 FF - Y: FF FF 00 - W: FF FF FF - Bl: 00 00 00
Feel free to post any other nice looking profiles you find
Init.d in Lollipop
I did not add Init.d support when building the Lollipop variant's ramdisk. Instead, /su/su.d should be used to run boot scripts. The functionality is exactly the same as the old Init.d.
Haptic feedback on soft keys
In order to avoid conflict with ROM side solutions, haptic feedback is disabled by default. It can be enabled via the following command which can be run as a boot script (eg. in /su/su.d). Command must run as root.
Code:
echo 1 > /sys/class/misc/abov_touckey/vibrate
NOTE: Above "touchkey" was misspelled in code. It should be fixed in a future update. Sorry for any inconvenience
still not fixed lol
Extra Compatibility Notes:
[url]http://forum.xda-developers.com/showpost.php?p=62226500&postcount=2[/URL]
Awesome, thanks !
Installed it and testing now
After a few days of testing !!! All I can say is, Great Kernel :good:
Good performance, great battery life
No issues so far.:highfive:
Working fine on G800FXXU1AOE3
And works great on G800FXXU1AOG2 too.
Again big Thanks Curtis ! :angel:
kernel is damn good.
Games running very fast for me with the new updated kernel
The 1.5Ghz CPU overclock is .. awesome
For additional gaming performance you can lock the GPU Frequency like this:
Shell command:
cd sys/module/mali/parameters
echo 533 > mali_dvfs_control
thats it, gpu locked to 533 mhz. Thanks to hennymcc for this commands
for example:
GTA San Andreas running now with maximum resolution+visibility graphical settings
Solid 30+ FPS :cyclops:
Sorry for noob question - can someone show me the exact syntax to enter in Terminal (or procedure) to activate OTG ? I don't seem to figure it out .
seaman5705 said:
Sorry for noob question - can someone show me the exact syntax to enter in Terminal (or procedure) to activate OTG ? I don't seem to figure it out .
Click to expand...
Click to collapse
To turn on:
Code:
su -t echo 1 > /sys/devices/virtual/sec/switch/otg
And off:
Code:
su -t echo 0 > /sys/devices/virtual/sec/switch/otg
Will ask for root.
EDIT: Enter exact commands in terminal emulator or adb shell
Thanks Curtis , but something is wrong in my case . It doesn't work and I don't understand why . After running the script , I granted the root access
, everything seemed to be ok , but nothing happens when I connect and USB key which is recognized in my S4 phone .
seaman5705 said:
Thanks Curtis , but something is wrong in my case . It doesn't work and I don't understand why . After running the script , I granted the root access
, everything seemed to be ok , but nothing happens when I connect and USB key which is recognized in my S4 phone .
Click to expand...
Click to collapse
Does anything else work? OTG also gets reset on boot, maybe it needs to be in an init.d script. I'll admit, I don't have an OTG cable to test, perhaps I should get hold of one, but the code definitely creates the right behavior (exactly the same as the other OTG kernel around here actually). Maybe switchable isn't the right way to go about it and OTG must be enabled permanently. I'll have to look into this, but in the meantime could you perhaps test with the other OTG kernel and see if it works? Also, the stick maybe might not be automatically mounting. Run "mount" in a terminal and see if it pops up. Apologies for the inconvenience.
CurtisMJ said:
Does anything else work? OTG also gets reset on boot, maybe it needs to be in an init.d script. I'll admit, I don't have an OTG cable to test, perhaps I should get hold of one, but the code definitely creates the right behavior (exactly the same as the other OTG kernel around here actually). Maybe switchable isn't the right way to go about it and OTG must be enabled permanently. I'll have to look into this, but in the meantime could you perhaps test with the other OTG kernel and see if it works? Also, the stick maybe might not be automatically mounting. Run "mount" in a terminal and see if it pops up. Apologies for the inconvenience.
Click to expand...
Click to collapse
No, it will not mount . I tested and OTG works with henny's kernel . Otherwise you made a great kernel - thanks for your work and your advices !
seaman5705 said:
No, it will not mount . I tested and OTG works with henny's kernel . Otherwise you made a great kernel - thanks for your work and your advices !
Click to expand...
Click to collapse
Attached is a build of the kernel with OTG enabled on a permanent basis. If you would not mind, could you test to see if it works? If so it will be done this way in future release, if not I will have to have a good look at any related code...
(P.S, sorry for the wait, my dual-boot was giving me issues)
CurtisMJ said:
Attached is a build of the kernel with OTG enabled on a permanent basis. If you would not mind, could you test to see if it works? If so it will be done this way in future release, if not I will have to have a good look at any related code...
(P.S, sorry for the wait, my dual-boot was giving me issues)
Click to expand...
Click to collapse
Yes , OTG works with this kernel . Great !
Note that after flashing, another reboot is needed to have the usb key properly mounting and poping up the file explorer with the key's content on connection .
Thanks !
New Version!
New version of my custom kernel released. Now includes Double Tap 2 Wake.
Is it possible to add voltage control to your kernel ? thanks .
CPU Voltage control is now implemented. Will work on a Synapse interface and the int and mif buses later today.
New Version!
Voltage control, Linux patches and fixes for DT2W waking up the screen while a call is in progress(sorry 'bout that)
Working great - I achieved good undervolting . Thanks
Hope to see a modified kernel for Lollipop too .
Battery Life Extender
Code:
###### JayminSuthar @ xda-developers
###### Copyright (c) 2018 Jaymin Suthar. All rights reserved.
## Legal
* This file is a part of "Battery Life Extender (blex)".
* blex is released under the terms of GNU GPL v3 as published
by the Free Software Foundation, and you hereby are allowed
to use, modify or redistribute it, either pieces of it or
entirely under v3 or any later version of the GPL.
* blex is developed in a hope of being useful, but neither
warranty nor support are promised with it, not even fitness
for the particular purpose. See the GPLv3 for details.
* A copy of GPLv3 (COPYING) is placed in the root folder of
blex, see <https://www.gnu.org/licenses/> for more.
## Links
* [Git Repository](https://github.com/Magisk-Modules-Repo/blex)
* [Support Thread](https://forum.xda-developers.com/apps/magisk/mcs-charging-controller-t3739371)
* [Telegram Group](https://t.me/joinchat/IiBDkxCpljv5TH994qtv6Q)
## Introduction
* blex helps in extending/maintaining lithium batteries' life
by controlling when charging is enabled or disabled.
## Details
* blex is a tool that lets you enable or disable charging in
programmatic manner so to extend/maintain batteries' life,
it is reliable and also fully automated.
* Automation provided includes two features which are 'Auto
Switch' and 'Auto Power'. Auto Switch is a feature which
disables charging when a disable threshold has been hit and
enables charging back as soon as the battery level hits an
enable threshold, whereas Auto Power is a feature which'll
power the device OFF as soon as level has reached a power
threshold.
* The purpose behind Auto Switch is to make the battery lie
inside our specified limits so that a constant charge cycle
can be maintained that's a basic requirement when you wish
to extend the batteries' life. It helps to increase maximum
charge cycles the battery can have and that without losing
anything.
* And the purpose behind Auto Power is to never let the cells
lose voltages too low that it might harm bring the battery
back to the life. This helps to prevent some weirdities like
unexpected battery levels shown.
* blex also provides you to enable/disable charging manually
on demand, and that introduces manual methods. You can use
manual methods to fulfill the need based on either level or
time, refer to the 'CUI' section for more.
* The 'CUI' section provides details on each flag and option
that you can use to setup Automation, configure blex, launch
the daemon, reset battery statistics and more...
## Requirements
* A modern arm-based chipset.
* Basic terminal knowledge.
* (if Magisk install...) Magisk 14.6+.
* (...or else) Any root solution,
* (...or else) Init.d support.
## Installation
* blex supports both the Magisk systemless install and the
standard /system modifying install, just make sure all the
requirements are met for that specific install mode and do
flash the zip from either custom recovery or Magisk Manager
and blex will detect install mode and install accordingly.
* NOTE: Modifying /system might make your device unbootable.
* NOTE: If Magisk is detected, you can't do standard install.
* NOTE: If Magisk is older than required, it'll automatically
install in standard /system modifying mode.
## Setup
* After installing, blex requires you to configure itself by
running 'blex --configure', if you don't do that, blex will
be of no use to you. This step is required only once after
installing/upgrading.
* I also recommend you to toggle ON/OFF Automation features
and set their thresholds to your needs for a set-and-forget
concept.
* NOTE: Enforcing thresholds outside blex' recommended limits
is against the purpose of extending batteries' life and thus
is strongly discouraged. That flag is included just for some
users who wish to use blex to control charging rather than
to extend/maintain batteries' life.
## Usage
* blex provides a nice, user-friendly and easy to use CUI to
the user. This CUI can be used to configure or setup blex or
to run a manual method, etc... All you need is a terminal
emulator (like Termux). So, in steps...
* ...launch the terminal,
* write 'su' to have a root shell,
* and call blex by running 'blex [flags] [options] args'.
* NOTE: If you have multiple blex processes running, they may
interfere with each other, please avoid such conditions.
* NOTE: Most things in CUI are checked and defaulted to some
action if an argument is not provided.
## CUI
* Flags
[--detach]
Detach from the terminal and run as a background process.
[--skip-logs]
Skip dumping logs to the logfile (to improve performance).
[--enforce]
Enforce any value between 1-99 as a valid threshold and
do not perform mathematics on arguments given.
NOTE: Flags must be in order [--detach] > [--skip-logs] > [--enforce]
or else blex will misinterpret them as options.
* Options
[--update] [switch/power] [disable/power] [enable]
Update Automation thresholds. The feature that provides
the thresholds is the first argument and new values of
thresholds are arguments following that.
If the feature is Auto Power, second argument is power
threshold, and if the feature is Auto Switch, second and
third arguments are disable and enable thresholds as in
order.
If enable threshold is not given, it will figure that out,
and if no threshold is given, it'll revert thresholds of
the feature to their defaults, and finally, if the feature
is not given, it will revert every threshold.
[--toggle] [switch/power] [ON/OFF]
Toggle Automation feature ON or OFF. The feature to toggle
is the first argument and the state to toggle to is the
second.
If state is not given, it'll invert the feature state like
ON -> OFF and vice versa, and if the feature is not given,
both features will be reverted to their default state.
[--manual] [enable/disable/stop] [level/time]
Enable or disable charging, or stop every manual method
running. The action to perform is the first argument and
the format string for the action (if not stop) is second
argument.
If the action is stop, it will stop every manual method
currently running, and if enable or disable, then charging
state will be {action}d based on the format specified by
the format string.
The format string will be '{level}%' if {action}ing until
the 'level' is hit, or '{time}s', '{time}m' or '{time}h'
to {action} charging until 'time' seconds, 'time' minutes
or 'time' hours have passed respectively.
[--mkdaemon] [start/stop]
Start or stop the blex daemon manually. It will start or
stop the daemon as per the first argument.
If an argument is not given, it will start the daemon.
[--configure]
Configure blex' kernel communication interface.
[--restat]
Reset battery statistics on demand. Useful in recalibraing
the battery, should only be used once a month.
[--info]
Print information about current battery state, settings of
blex and whether the daemon is running or not.
[--help]
Print this HELP page and exit.
## Examples
* blex --enforce --update switch 99
* blex --detach --manual disable 1%
* blex --skip-logs --configure
* blex --update switch 80 60
* blex --update switch 85
* blex --update power 15
* blex --update switch
* blex --update
* blex --toggle switch ON
* blex --toggle power OFF
* blex --toggle switch
* blex --toggle
* blex --manual enable 1h
* blex --manual disable 30m
* blex --manual enable 90%
* blex --mkdaemon start
* blex --mkdaemon stop
* blex --mkdaemon
* blex --configure
* blex --restat
* blex --info
* blex --help
## Support
* ISSUE: Device spontaneously reboots while configuring.
* SOLUTION: Configure blex again after the device rebooted.
* ISSUE: blex stops working after flashing some kernel.
* SOLUTION: Reconfigure blex using 'blex --configure'.
* NOTE: Resetting batterystats might not work for all devices.
* If you experience any issue while installing, please share
about that in either the 'Support Thread' (see 'Links') or
'Telegram Group' (again, 'Links') and remember to attach
the '/dev/blex_install.log' logfile.
* If you experience any issue with the daemon or CUI, write
about that in the thread or group and please attach logfiles
placed in the folder '/sbin/.core/img/blex/log' if Magisk
install, or in '/data/adb/blex/log' for standard install.
* All the bug reports should be widely described and must have
required (and relevant) logs.
* If you're a developer willing to contribute, please do so
by creating PRs at my personal GitHub fork of blex.
* I'm a college first-year student who does it all as a hobby
to help others, so if I helped you, kindly use the 'Thanks'
button on the XDA Support Thread.
## Credits
* @topjohnwu for Magisk.
* @osm0sis for his BusyBox binary.
* Every blex/mcc beta tester :)
XDA:DevDB Information
Battery Life Extender, Tool/Utility for the XDA Community Apps
Contributors
JayminSuthar
Source Code: https://github.com/Magisk-Modules-Repo/blex
Version Information
Status: Stable
Current Stable Version: 0.3
Stable Release Date: 2018-10-16
Created 2018-01-23
Last Updated 2018-10-16
Changelog
Code:
#### 0.3
* Fix default PATH for daemon startup.
* Fix for kernels not responding node changes.
* Limit checking for current to just once.
* Minor UI change.
* Documentations update.
#### 0.2
* Add examples for supported actions.
* Symlink BusyBox applets instead of hardlinking.
* Revert manual methods regardless of Auto Switch.
* Check control file content before writing.
* Filter out Changelog from [--help] output.
* Update to osm0sis' BusyBox 1.29.3.
* Update documentation.
#### 0.1.4
* Limit charging state changes to only two.
* Fix unwanted output when checking for daemon.
#### 0.1.3.3
* Minor README fix.
#### 0.1.3.2
* Fix daemon not running issues.
#### 0.1.3.1
* Fix daemon detections.
#### 0.1.2.1
* Fix the daemon can not be launched.
#### 0.1.2
* Fix CLI not recognizing the daemon.
* Fix [--mkdaemon] always starting daemon.
* Update strings.
#### 0.1.1
* blex is no longer in beta stage!
* Fix configuring for lazy kernel events.
* Fix detecting running processes.
* Fix daemon checking in [--mkdaemon].
* Fix manual methods detection.
* Fix stopping multiple methods.
* Prevent running multiple daemons.
* Minor UI update.
#### 0.1.beta
* Please remove any version of mcc before installing this.
* Rework as 'Battery Life Extender (blex)'.
#### Redefined 1.1.3
* Fix [--help] page output.
#### Redefined 1.1.2
* Fix unzipping error.
* Update strings.
#### Redefined 1.1.1
* I'm currently porting this project Shell -> native "C". No
feature builds, will be released for the shell version of
it. Only bugfixes! Keep reporting please.
* In case you're interested, porting to "C" will allow it to
function even without a root solution, though requiring a
custom recovery. Also executions will be hell-lot-of fast
and much less resource heavy (current: 7MB).
* Fix the daemon incorrectly reverting the switch.
* Fix boot script not launching the daemon.
* Fix Install script aborting in recovery.
* Fix A/B slot detection for some devices.
* Fix permissions for generated files.
* Fix read-only filesystem errors.
* Fix lost BusyBox applet links.
* Fix other bugs I discovered.
* Automatically implement skip_root workaround.
* Improvements (logging, daemon, algorithms).
* Remove Magisk versionCode checking.
* Remove separate error log_files.
* Remove lock file feature.
* Update BusyBox to 1.29.2.
* Update documentation.
* Update arguments.
* Update UI.
#### Redefined 1.1
* Fix incorrect daemon status in [--info].
* Fix control references identification.
* Fix mounting issues for some devices.
* Fix 'internal error' for system mode.
* Fix racial condition with [--reset].
* Fix boot scripts error logging.
* Fix BusyBox aborting setup.
* Fix other minor bugs.
* Remove unnecessary x86 BusyBox.
* Remove unnecessary img resizal.
* Remove late_start boot script.
* Remove the wrapper around su.
* Install mcc to xbin for system mode.
* Use BusyBox for mcc Install script.
* Add logging to the Install script.
* Update the behaviour of lock_file.
* Update strings.
* Update README.
#### Redefined 1.0.2
* Fix the daemon not writing control nodes.
* Internal code improvements.
* Update README.
#### Redefined 1.0.1
* Fix daemon not launching with beta Magisk.
* Fix control reference nodes never identified.
-> This should fix daemon not working and always reconfiguring.
* Fix safe boundaries for [--switch/--power].
* Fix some algotithmic flaws.
* Update BusyBox to 1.29.1.
* Update strings.
##### Redefined 1.0.MR
* Fix a few bugs with BusyBox and UI.
* Update README for public release.
##### Redefined 1.0
* Initial redefined release.
##### 2.0.MR
* Hello people, This build is a fix for when a [-s/--switch]
call doesn't act like it should. Actually, the code while
having the down threshold and the code for when not, were
placed alternatively. So if you run... say 'mcc -s 85 70'
it would run as the '70' was not given and as mcc I wrote
to be intelligent, it would set 85 and ' 85 - 10 = 75'.
##### 2.0
* This version is re-written from scratch, so please perform
a CLEAN INSTALLATION.
##### 1.5.1.MR
* Hi users,
* This build is to fix two major bugs which I identified just
now. First is the well-known, conflict of the mcc Installer
and the mcc daemon, and the second is the daemon misbehaves
if refs are not set or the lock file is created. Both of em
have been fixed. While the first prevents mccs installtion,
the second causes unwanted reboots for cases while the user
has misused the lock file feature or have modified the conf
file. After this fixations, I can proudly say that mcc does
not have no bugs now...
* Another thing is that mcc now patches the Main before Magic
mounting has happened, so in theory, there will not be need
to make any modifications if Magisk changes its mount point
again, just enjoy!!! Regarding boot scripts, they log their
errors now too as well as commands executed.
* And also while some advanced users did directly run the mcc
daemon, I have also prevented the daemon from running, only
mcc internals can fork it, and that should be when required
by mcc. This blocking also helps the initial daemon call on
the boot a great algorithmic space, so is great.
##### 1.5
* Hi users,
* The final build by me is here, as I will be prepping for my
college admissions. If someone is willing to develop it, PM
me at XDA or open an issue at GitHub and I'd give you write
access to the Repo.
* This build is nothing other than previous build, but having
fixed the Magisk mountpoint, BusyBox setup, and other minor
issues.
* A quick tip: If Magisk changes its mountpoint again, simply
edit LINE 45 in /system/{x,}bin/mcc, NOTHING else.
* Quick tip 2: All the core logic is documented, nothing else
is there, I think logic builds program, not coding skills.
* Wish me luck and Goodbye.....
##### 1.4.3
* Hi users,
* A small + sensitive release is here, which is aimed on some
minor code errors, and a better way of eliminating failures
due to interference with the daemon.
* All the bugs fixed are reported by users at XDA, and I will
not detail them here, but "Please toggle auto switch OFF if
compatibility check fails upgrading".
* What I am gonna detail is a new feature of the daemon. From
this version on, mcc daemon can be paused with a lock file.
Users, or anyone else, can create the file CACHE_DIR/lock_d
and the daemon will go sleep until it exists. This is to be
used by Installer, but not limited. So changelog reads...
* ...Fix 'Permission denied' while running mcc
* ...Fix daemon not launching for some devices
* ...Fix bad compatibility check failures
* ...Bring back initial 120 seconds delay
* ...Add a lock file to pause the daemon
##### 1.4.2
* Hi users,
* This is another lil bug fix release, which is to fix a very
serious bug, which makes auto switch non-functional, thanks
to @pat357 for pointing the buggy thing out and providing a
quick fix
##### 1.4.1.MR
* Workaround Magisk bundled BusyBox missing poweroff applet
##### 1.4.1
* Hi users,
* This is a small bug fix release, which is aimed to fix some
little, but very serious bugs, so changelog reads as
* --> Fix mod_dir not being set by the service
--> Fix unwanted reboots while installing
--> Fix installations for Pixel 2 XL
--> Fix switch not being written
* And the last twos are thankfull contributions from @chuckr2
##### 1.4
* Hi users,
* As always it calls for an apology that you all had to manually
set references even after succeeding the compatibility check from the
mcc Installer, it was a misspelled variable in the Installer, which
has now been fixed, for which I want to thank @pat357 for his pull
request
* Another critical bug was false positive compatibility successions, this
bug appears when the device did not even have a recognized battery
device / module, and so much funnier, the reason was just a single
misplaced variable, that was used to detect if the check succeeded,
this bug has also been fixed
* @RSDamasceno at XDA reported having soft reboots and device warm-ups
with mcc, which I suspect a bug with kernel not handling switch writes
correctly, but as mcc is entirely written in Shell, I have added some
code that will detect the current switch status and write to it only if
the status is different, so the issue is supposed to be fixed
* It fixes another issue when the user has given an invalid argument for
manually enabling charging, issue appeared something like, mcc will
first disable charging, then abort due to unrecognized argument, so
charging will be disabled as opposed to be enabled, which has also
been fixed
* With any older mcc build, the first execution of command always took
some seconds, some people reported 2, some 5 and some even 8 seconds,
which happened due to mcc's Magisk mount point finding and BusyBox
setup, which I implemented just to make sure mcc can work with all the
present and possibly any future Magisk version, but the logic has now
been shifted to service, which on boot, will do it all once for the
entire boot session
* The boot daemon launcher will now attempt 5 times to launch the daemon,
which whether succeeded / failed will be logged in Magisk logs, so
that users can check if the daemon was launched at boot time
* And now as Android P DP1 is out, which removes make_ext4fs, I have put
a fallback for that to mke2fs, just as same with Magisk
* Also all the strings in the Installer and the Main have been re-written
and some faulty code has been cleaned up and organized as always
* So, the complete changelog is
--> Fix the Installer not setting references by @pat357
--> Fix false positives with compatibility check
--> Fix a bug with with kernels not handling switch changes correctly
--> Fix a bug with manually enabling charging
--> Fix image creation for Android P DP1
--> Fast as hell first time execution
--> A better boot daemon launcher
--> Re-write all the strings
--> Cleanup some code
##### 1.3
* Hi users,
* Firstly, I'm sorry for the sucking 'No references set' bug,
I forgot to split out the switch file which resulted in as an
unrecognized switch by mcc, So, whenever mcc was ran, it did not
detect switches and so the bug happened, this bug has been fixed now
* And now, so mcc provides manual run option, and which takes time as an
argument, for which, mcc will fork a session which will keep sleeping
for the given time, and mcc will check for that process every second,
but it gave false positives when another shell process was also sleeping
for the same time as mcc ( child ) did, that bug has also been fixed
* I also recently intoduced a new feature said 'Revert Magic Mount'
live from booted Android, but I realized that with A / B devices,
it is completely different, which made it unusable for such devices,
but now, the feature is working completely on A / B devices now, for which
mcc requires Magisk >= 1410 from now ( would not matter for most users )
* I have also put in a hell lot of efforts in making mcc rock stable,
I started from the top of every single component and kept analyzing, and
analyzing, and analyzing, and analyzing, and analyzing, and analyzing,
and Finally, I'm glad to declare most unless all bugs are flushed out
* I also have effingly strived harder to workaround many non-mcc flaws which I found
* So, the complete changelog is
--> Fix the 'No references set' bug
--> Fix false positives for time-based run
--> Fix 'Revert Magic Mount' for A / B devices
--> Re-analyze and re-write the entire project
--> Workaround many non-mcc flaws
--> Require Magisk >= 1410
##### 1.2.4
* Fix compatibility check ( Installer / mcc ) for some devices
--> add support for some weird devices I saw ( mostly Honor )
* Fix some faulty BusyBox setup code
* Fix image sizes for resizing
--> mcc never shrinks them, so expand only to needs
* Fix regression opened by @pat357
* Free Magisk daemon child after mcc daemon is launched
* Abort installation for Magisk < 1400
* Update README ( and indirectly [ --help ] )
##### 1.2.2
* Fix daemon not being launched at boot ( was my bad )
* Fix some faulty image resizing code in mcc Installer
* Fix unwanted power-offs for when no references are set
* Fix regression opened by @pat357
--> show daemon status ( runnning or what ) in [ --info ]
* Add perms handling for non Stock / near Stock kernels
* Increase checking intervals from 10ms to 100ms
--> which is likely to fix some compatibility check failures
* Add double checking for uevent file
--> which is likely to fix some compatibility issues
* Flash again to uninstall feature now performs a complete uninstall
--> 1) remove files 2) kill mcc processes and 3) revert Magic Mount
--> it will revert Magic Mount live from booted Android!!!
--> the last one is available only for Magisk >= 1410,
as topjohnwu has changed the Magic Mount algorithms many times
##### 1.2.1
* All previous versions are considered incompatible
* Fix installations for Magisk Manager 5.6.0+
* Fix some faulty busybox setup code
* Correct some terminology ( see 'Arguments can be' )
* Improve the [ --re-daemon ] option
* Change defaults to 80 70 ( it be optimal )
* Rewrite README ( which directly means [ --help ] )
* Add messages to UI for some tasks
* Reduce checking intervals to 10ms
* Reduce max switches to two from four
* Add error handling for new code
* Port commit from Magisk to mcc Installer
--> 'Round sizes to nearest integer', also repair image first if found
* Put errors to a separate logfile
* Rebase some tests on common observations
* Remove and re-write some pieces of code
* For developers
--> Revert the source mcc feature, to keep the code clean
Downloads are here.
blex-0.3-201810161-stable-signed.zip
blex-0.2-201810061-stable-signed.zip
blex-0.1.4-201809231-stable-signed.zip
blex-0.1.3.3-201809222-stable-signed.zip
blex-0.1.3.2-201809221-stable-signed.zip
blex-0.1.3.1-201809182-stable-signed.zip
blex-0.1.2.1-201809171-stable-signed.zip
blex-0.1.2-201809111-stable-signed.zip
blex-0.1.beta-201809081-beta-signed.zip
mcc-Redefined 1.1.3-201808101-stable-signed
mcc-Redefined 1.1.2-201808092-stable-signed
mcc-Redefined 1.1.1-201808091-stable-signed
mcc-Redefined.1.1-201808011-stable-signed
mcc-Redefined_1.0.MR-201807231-signed
mcc-2.0.MR-201804181-stable-signed
mcc-1.5.1.MR-201804102-stable-signed
If you face any issues with the Installer, please provide /dev/blex_install.log log file.
If you face any issues after installing, please provide log files in $blex_dir/log folder,
where $blex_dir is /sbin/.core/img/blex for Magisk install, otherwise /data/adb/blex.
Thank you for this module !
It's seems to be working as advertised.
The only thing that I didn't test yet is the shutoff at 15%.
What's the difference between this module and the one from VR25 ?
pat357 said:
Thank you for this module !
It's seems to be working as advertised.
The only thing that I didn't test yet is the shutoff at 15%.
What's the difference between this module and the one from VR25 ?
Click to expand...
Click to collapse
Thanks, i'm glad it helps you
There are so many differences, but the most important ones are
- Error handling
- Logic
- Coding style
BTW, which device, ROM and kernel you're using ??
Sent from my Le Max 2 using XDA Labs
Have a look at my sig !
I have installed the zip through magisk but I can not find the app to configure. Where should I look?
Ali.G said:
I have installed the zip through magisk but I can not find the app to configure. Where should I look?
Click to expand...
Click to collapse
You should interact with it via any Terminal Emulator, all the available commands are listed in the README, or run "mcc --help" fromTerminal to see all of them
Sent from my Le Max 2 using XDA Labs
MCMotherEffin' said:
You should interact with it via any Terminal Emulator, all the available commands are listed in the README, or run "mcc --help" fromTerminal to see all of them
Sent from my Le Max 2 using XDA Labs
Click to expand...
Click to collapse
Ok thank you. I have enabled to 90% and disable to 55% will it get charged till 90 then stop till it reaches 55 and again?
Sent from my ONEPLUS A3003 using Tapatalk
Ali.G said:
Ok thank you. I have enabled to 90% and disable to 55% will it get charged till 90 then stop till it reaches 55 and again?
Click to expand...
Click to collapse
Yes, you're right...
Sent from my Le Max 2 using XDA Labs
Hi,
I am trying to install this module, but I get this error:
Error:- Could not find Magisk internal busybox
Abort:- Please install Magisk v14.0+
I am running Magisk v15.3
What could be the problem?
Best Regards
cheveguerra said:
Hi,
I am trying to install this module, but I get this error:
Error:- Could not find Magisk internal busybox
Abort:- Please install Magisk v14.0+
I am running Magisk v15.3
What could be the problem?
Best Regards
Click to expand...
Click to collapse
Hi, Can you tell me the output of "find /data -type f -name busybox" ???
Sent from my Le Max 2 using XDA Labs
MCMotherEffin' said:
Hi, Can you tell me the output of "find /data -type f -name busybox" ???
Sent from my Le Max 2 using XDA Labs
Click to expand...
Click to collapse
Hi MCMotherEffin,
Sure, here it is:
a5y17lte:/ # find /data -type f -name busybox
/data/data/com.keramidas.TitaniumBackup/files/busybox
/data/data/._cwm_restore/data/adb/magisk/busybox
/data/data/._cwm_restore/data/data/com.keramidas.TitaniumBackup/files/busybox
/data/data/._cwm_restore/data/data/com.paget96.lspeed/files/binary/busybox
/data/data/com.paget96.lspeed/files/binary/busybox
/data/adb/magisk/busybox
Regards
cheveguerra said:
Hi MCMotherEffin,
Sure, here it is:
a5y17lte:/ # find /data -type f -name busybox
/data/data/com.keramidas.TitaniumBackup/files/busybox
/data/data/._cwm_restore/data/adb/magisk/busybox
/data/data/._cwm_restore/data/data/com.keramidas.TitaniumBackup/files/busybox
/data/data/._cwm_restore/data/data/com.paget96.lspeed/files/binary/busybox
/data/data/com.paget96.lspeed/files/binary/busybox
/data/adb/magisk/busybox
Regards
Click to expand...
Click to collapse
Fixed with the next update
Sent from my Le Max 2 using XDA Labs
MCMotherEffin' said:
Fixed with the next update
Sent from my Le Max 2 using XDA Labs
Click to expand...
Click to collapse
Thanks a lot!!
MCMotherEffin' said:
Fixed with the next update
Sent from my Le Max 2 using XDA Labs
Click to expand...
Click to collapse
Hi again,
Tried the updated version, but got this error log:
- Copying zip to temp directory
- Installing MCs_Charging_Controller-Gulab_Jamoon.zip
losetup: /dev/block/loop1: No such device or address
losetup: /dev/block/loop2: No such device or address
losetup: /dev/block/loop3: No such device or address
losetup: /dev/block/loop4: No such device or address
losetup: /dev/block/loop5: No such device or address
losetup: /dev/block/loop6: No such device or address
losetup: /dev/block/loop7: No such device or address
- Abort :- Could not find Magisk mount point
Failed!
! Installation failed
Best regards
cheveguerra said:
Hi again,
Tried the updated version, but got this error log:
- Copying zip to temp directory
- Installing MCs_Charging_Controller-Gulab_Jamoon.zip
losetup: /dev/block/loop1: No such device or address
losetup: /dev/block/loop2: No such device or address
losetup: /dev/block/loop3: No such device or address
losetup: /dev/block/loop4: No such device or address
losetup: /dev/block/loop5: No such device or address
losetup: /dev/block/loop6: No such device or address
losetup: /dev/block/loop7: No such device or address
- Abort :- Could not find Magisk mount point
Failed!
! Installation failed
Best regards
Click to expand...
Click to collapse
Do you have a "hidelist" file at /sbin/.core/img/.core ?? If so, what do it contain ??
Sent from my Le Max 2 using XDA Labs
MCMotherEffin' said:
Do you have a "hidelist" file at /sbin/.core/img/.core ?? If so, what do it contain ??
Sent from my Le Max 2 using XDA Labs
Click to expand...
Click to collapse
Hi,
Yes, that file exists, here is the text it contains:
com.google.android.gms.unstable
Regards
cheveguerra said:
Hi,
Yes, that file exists, here is the text it contains:
com.google.android.gms.unstable
Regards
Click to expand...
Click to collapse
Can you capture output of
Code:
grep '/dev/block/loop0 ' /proc/mounts
??
BTW, which device, ROM, and Android version are you using ???
Sent from my Le Max 2 using XDA Labs