Related
At first, I am not liable for any harm or damage that may happen to your device!
If you have su and didn't trigger knox, I CANNOT guarantee that running this script won't cause 0x1!
Requirements:
1) P905/viennalte/Qualcomm based model ONLY (won't work on Exynos devices. MIGHT work on other Qualcomm LTE deices from Note Pro and Tab Pro series - feel free to repost but give credits!) running 4.4.2 stock;
2) root access with SuperSU (using cf-root - credits to chainfire);
3) busybox installed (I do recommend this paid installer: https://play.google.com/store/apps/details?id=stericson.busybox.donate , MOST PROBABLY free version will be more than enough, too, but I haven't tested it as I have license...)
4) Android Terminal Emulator installed ( free at: https://play.google.com/store/apps/details?id=jackpal.androidterm )
Installation:
1) download file init.d_qcom.sh using below link and put it in the root of internal memory (so it will be placed in: /sdcard/init.d_qcom.sh)
2) run Android Terminal Emulator
3) at command line, type:
Code:
su -c /sdcard/init.d_qcom.sh
(give it an access if requested)
4) voila.
Additional info for advanced users:
1) scripts in /system/etc/init.d shall be root:root 755 (and NOT 777 as stated in A LOT of sources, thou has to be a heavy idiot to give write access for system files to "world"...)
2) init.d is handled from one of the /system/etc qualcomm additional scripts as it refused to work using regular install-recovery.sh method...
3) scripts are triggered paralelly but I am using different method (find/nohup/su combination...), as this damn rom refused to simply execute "run-parts" applet...
4) init.d permission helper script included (just put your scripts in init.d and they'll receive proper permissions on reboot)
Download:
http://www12.zippyshare.com/v/32009778/file.html
Nice to see some developement for this tab!
Anyway to port it to exynos? :fingers-crossed:
prohackerbro said:
Nice to see some developement for this tab!
Anyway to port it to exynos? :fingers-crossed:
Click to expand...
Click to collapse
+1
sent from my amazing NotePro 12.2 via Tapatalk
Criminal23 said:
+1
sent from my amazing NotePro 12.2 via Tapatalk
Click to expand...
Click to collapse
I might try, however I do not own the device and the file structure is completely different.. Can you first enter via Android Terminal:
Code:
su
ls -l / >/sdcard/content.txt
ls -l /system/etc >>/sdcard/content.txt
And post the /sdcard/content.txt file which will be created (or its contents only)?
Also, i would be glad if you copy every *.rc file from root of filesystem to a dir , compress it to one file and post it too
esgie said:
I might try, however I do not own the device and the file structure is completely different.. Can you first enter via Android Terminal:
Code:
su
ls -l / >/sdcard/content.txt
ls -l /system/etc >>/sdcard/content.txt
And post the /sdcard/content.txt file which will be created (or its contents only)?
Also, i would be glad if you copy every *.rc file from root of filesystem to a dir , compress it to one file and post it too
Click to expand...
Click to collapse
Here you are
Criminal23
Criminal23 said:
Here you are
Criminal23
Click to expand...
Click to collapse
Criminal23 said:
Here you are
Criminal23
Click to expand...
Click to collapse
After looking into sent (and posted) files, I have to say that the init process in our devices are ABSOLUTELY different.
Qualcomm version triggers about 7-8 scripts lying in /system, which are provided by Qualcomm, which are pointed in configuring all the hardware provided with their chipset - in addition to init.???.rc files from the kernel. The clue was to add init.d execution command at the very end of one of those scripts (and that is done automatically with script attached in the first post).
Exynos version does not launch (almost - see below) ANY external script during the boot. Whole process seems to be performed by rc files lying in root of the filesystem, which are embedded in kernel's ramdisk and any edits won't preserve the reboot, so it cannot be done without repacking the kernel and that is something far more troublesome to perform without device in hand, without the firmware on disk and without a plenty of time.
BUT
it still runs /system/etc/install-recovery.sh which is an Android standard and which genuine purpose was to reflash recovery back to stock if a custom one was detected. Now, it is sometimes utlized to run somehing at boot, especially: it is used by SuperSu (in addition with other methods) to run its daemon. The problem is that kitkat introduced enforcing SELinux, that Samsung SELinux policy adds special security context for this file, that install-recovery.sh won't be launched if the file has no proper security label - and that while installing SuperSu, the context is set in a different way and in final, install-recovery.sh isn't launched, until we restore /system context, and restoring context to the system ends with... non working su, so we have to flash it again, breaking install-recovery.sh context... Did you get it? - it's a loop as fixing one thing breaks the second, and fix to the second breaks the first That is why on my qualcomm device i have chosen another script file to run the init.d - and as you don't have any other script except install-recovery.sh, I don't know where it might be put...
BUT also I cannot guarantee that the behavior above is not qualcomm-exclusive and it is possible that on exynos device everything will work without problem!
That's why you may want to try standard method for all the devices (term init - uses install-recovery.sh method described above):
http://forum.xda-developers.com/showthread.php?t=1933849
and if it won't work then you have to wait for - at least - repacked kernel with init.d support embedded into init.rc files or run your script by an external app, ie SManager. Just be aware that even if term init work, it may stop working every time you flash SuperSu, so remember to run the script again then.
Sorry for not being too helpful.
The latest versions of Adblock Plus don't work with the Nook. Although they can be installed, they will force-close upon initial start-up (silently if looking just at the UI but with a lot of stuff going on behind the curtains if you read the logcat). I've just reported it as a bug, and it got assigned the nice number #2000 but I expect it will be resolved by marking the APK as unsuitable for the Eclair API level.
So, if you want to use Adblock Plus, the last working version seems to be Adblock Plus 1.1.4.287. It's a development build, as I couldn't find an archive of old stable releases. Download it and install with:
Code:
adb install adblockplusandroid-1.1.4.287.apk
To make Adblock Plus work with the Nook, you need to set a HTTP proxy to address 127.0.0.1 (localhost) port 2020. There are two ways to do it:
This will open a dialog where you can input the above data:
Code:
adb shell am start -n com.android.settings/com.android.settings.ProxySelector
This is totally automatic but a reboot might be required:
Code:
adb shell sqlite3 /data/data/com.android.providers.settings/databases/settings.db "INSERT INTO secure (name, value) VALUES('http_proxy', '127.0.0.1:2020');"
Adblock Plus does an even better job in conjuction with AdAway, available here. In this case, the last version appears to work just fine.
Please note that you don't have to use ADB, you can also do all this directly from your Nook if you have Terminal Emulator installed.
Steps for installing directly from your Nook:
1. Install Adblock Plus by tapping on it in a file explorer, tapping "Install" and tapping "Done".
2. Set an HTTP proxy to localhost 127.0.0.1 and port 2020 by opening up Terminal Emulator and executing this:
Code:
su
am start -n com.android.settings/.ProxySelector
Then, in the "Hostname" text box, enter 127.0.0.1, and in the "Port" text box, enter "2020". Then tap "Save".
Done! ABP will now work properly.
Is it possible to hide notification message or icon?
kazikas said:
Is it possible to hide notification message or icon?
Click to expand...
Click to collapse
Somewhat OT, but yes, you can do that by making the notifications .png files in framework-res.apk plain black.
PM me for detailed instructions.
ROM Information
ROM Target Device: Samsung Galaxy Grand Prime SM-G530W | SM-G530T | SM-G530T1 | SM-G530FZ
ROM Status: Stable
ROM OS: CyanogenMod 12.1
Maintainers: [ vince2678 ]
[*] Project GitHub Repositories: https://github.com/vince2678
Build Tracking & Download
CyanogenMod (CM-12.1): http://grandprime.ddns.net/jenkins/job/CM_Builds/
TWRP Builds:: http://grandprime.ddns.net/jenkins/job/TWRP_Builds/
You can track builds via RSS: http://grandprime.ddns.net/jenkins/job/CM_Builds/rssLatest
All the builds from above are testing builds, and as such, are likely to be extremely unstable or
unusable.
Nightly and Stable Builds: http://grandprime.ddns.net/builds/
Instructions
To flash an the ROM, you can either:
Download a zip archive from above and flash it from recovery by sideloading the zip (using adb sideload) or by
just copying it to the device (using adb push or MTP file transfer) and installing it. Instructions are below under
Zip Instructions.
Download a tar.md5.xz archive which can be flashed via ODIN. Instructions are below at ODIN Instructions.
After CM-12.1 is installed, flash either the GApps package linked above, or download openGApps, but only
the micro version, otherwise there will be app conflicts between the CM apps and the GApps.
After flashing an image successfully, simply check for updates from System->About to update thereafter.
Device Names
Verify your device codename before downloading any firmwares or recovery images!
SM-G530W - gprimeltecan
SM-G530T - gprimeltetmo
SM-G530T1 - gprimeltemtr
SM-G530FZ - gprimeltexx
Note
Do NOT ask for help/post issues if you:
Code:
[LIST]
[*] Have flashed mods (Xposed, etc);
[*] Didn't read the OP;
[*] Didn't follow intructions to the word.
[/LIST]
And most of all, I'm not taking feature or device requests.
Disclaimer
I'm not willing to help anyone who damages their device because they didn't take the time to read any instructions I may have written
up, and I'm not willing to do any hand-holding when it comes to flashing custom firmwares. I assume beforehand that you know what terms
such as "Odin" and "recovery" mean in this context and the basics of flashing firmwares using Odin and custom recoveries.
These packages are distributed in the hope that they will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
I'm not responsible for any bricked devices, etc, etc, as a result of flashing these images. It is assumed that by downloading one of
these images you possess the prerequisite knowledge required to flash such firmware image.
Zip Instructions
[*] Download and install a TWRP recovery file for your device if you are on stock recovery. You will have to flash the recovery
.tar file for your device using ODIN (see ODIN Install below) or by using one of several applications from the Play Store such as
Rashr (will require a rooted phone).
[*] Download a recent .zip file from the links above for your device.
[*] Reboot into recovery mode [Press Power+Volume Up+Home].
[*] Wipe your data and cache partition (equivalent to doing a Factory Reset) if you are coming from a stock ROM.
[*] Either: Plug in your phone into your computer, copy the zip file to a location on your Internal or External Storage on a
device, click Install on TWRP on your phone and locate the zip file in the phone, or:
[*] Plug in your phone into your computer, and open Advanced->ADB Sideload on TWRP on your phone and swipe the slider to enter
sideload mode. Then open a command prompt/terminal on your computer in the folder you put the file by Shift-Clicking (Shift+Right
Click) and selecting "Open Command Prompt/Terminal Here" (you will need to have adb installed) and type:
Code:
adb sideload name_of_zip.zip
to sideload the file. Replace name_of_zip.zip with the name of the file. If you are running Linux you may need to type
adb kill-server and use sudo adb sideload if you get an `Insufficient Permissions` error.
[*] Download and flash GApps in the same way (optional).
ODIN Instructions
The flashable images are hosted at the link above.
The directory contains tar.md5.xz archives. The tar.md5.xz archives are named according to the date the image was built, e.g
cm_gprimeltecan-ddmmyyyy.tar.md5.xz and can be uncompressed to yield the flashable .tar.md5 archive.
Each ODIN flashable .tar.md5 contains the boot image, recovery image, and system image for flashing.
Installation
[*] Enable Developer Mode on your phone and unlock the bootloader from the settings, if not done already.
[*] Download a recent compressed flashable image above.
[*] Reboot into Download Mode [Press Power+Volume Down+Home].
[*] Extract the tar.md5.xz archive with 7zip or `xz -d cm_gprimeltecan-ddmmyyyy.tar.md5.xz` if under Linux or Cygwin to get a flashable
tar.md5 file.
[*] Flash the tar.md5 archive using ODIN by clicking AP and selecting the .tar.md5 file you just
extracted. If the file was corrupted during download, the installation will fail. You will need to redownload the file in this
case.
[*] You will need to wipe your data and cache partitions afterwards (equivalent to a Factory Reset) if you are coming from a
stock ROM, which can be done by rebooting into recovery [Power+Volume Up+Home].
[*]
Download and flash GApps (optional).
TL;DR: https://www.youtube.com/watch?v=fbabglAX5Ho
Changelog
01/11/2016
* [ fixed ] NFC is now working.
* [ note ] This batch will be the last build(s) for CM-12.1.
30/10/2016
* [ G530FZ ] Changed kernel source
* [ G530FZ ] Rear and front camera should be working as @kentone said.
12/09/2016
* [ G530FZ ] Enabled LTE
* [ G530FZ ] InputDisabler should now be working fine.
* [ G530FZ ] Fixed up camera code in kernel. If rear camera still does not work, then this is an issue in
the proprietary files.
08/09/2016
* Added a few more frequencies to the cpufreq kernel table (overclock to 1209MHz, and addition of 1152MHz).
Please don't request for me to add anything higher; the CPU is rated maximum for 1209MHz (even with nitrogen cooling, and so on), so it is
impossible to go past this.
* Added the "Particle" charging animation from the stock ROM. Off-mode charging should be working proper as well.
* Fixed Viper4Android (module was not named properly when copied to system).
* Updated InputDisabler code (the software that turns your touch screen off when you call).
* Tuned Kernel Samepage Merging to be less agressive with memory page merging. This should fix the responsiveness issues that popped up
in the last builds.
* ZRAM is available for all devices (fixed at 512MB), but only enabled by default for the G530FZ. There's a post somewhere on how to
enable it in the thread.
* Patched the update zips from today's builds with an old updater binary (zip updates should work again). I removed the zips from
Jenkins so they're only available from the /builds/ directory on the root of the web server.
* Added a few more screenshots.
* Any other changes in the log are more concerned with refactoring of code in the device trees, etc.
05/09/2016
* Added new build server [Bilbo]
* Added Viper4Android as the default equaliser.
* In-call audio now working.
* TWRP is now the default recovery [in the ODIN images]
* [ G530FZ ] Fixed zram properties, added other low-memory tweaks
* Enabled dex pre-optimisation [= Faster app startup, lower memory usage, quicker boots]
* I dunno what else, you check and see.
01/09/2016
* [ G530W ] The sleep of death issue should be gone on the latest successful build, and the device should be
going into deep sleep properly. I have yet to resolve this for the other devices (probably in a few days).
31/08/2016
* Fixed InputDisabler
* Added qcom powerHAL (might hopefully fix sleep issue)
+ Various other fixes ( file access permissions, kernel tweaks)
29/08/2016
* Initial work on cpu undervolting.
28/08/2016
* Fixed MTP support in TWRP (if you use TWRP, reinstall it).
* TWRP now shows proper disk free space information.
* adb sideload now works in TWRP (may need to kill adb server and start as root to do so).
* Added new device (SM-G530T1).
* Added VoLTE support to SM-G530FZ (Still no in-call audio ).
* Added darkness cpufreq driver (from Mokee kernel) to kernel.
* Enabled ZRAM by default in SM-G530FZ.
* Trebuchet and System UI should be working properly now (ostensibly it requires hardware rendering,
which is disabled on low-ram devices by default).
+ There may be other minor fixes I missed here.
25/08/2016
* MTP is now working (properly)
25/08/2016
* MTP is kinda working (I'm investigating)
* Modem is now fully working on G530FZ (calling, audio, data).
* All sensors (gyro, magnetic, proximity) working on G530FZ.
19/08/2016
* Fixed WiFi tethering
* Fixed issue with WiFi and bluetooth MAC addresses (were not set properly at boot).
* Added Samsung Doze app
+ Several other minor fixes and tweaks
14/08/2016
* Kernel is now built entirely from source
* WiFi should be working again on all builds
12/08/2016
* TWRP recovery is now available (I will not bother servicing any issues regarding this if it doesn't work for you, it is included here
purely for the purpose of providing a different recovery to those that want one.)
* There do not seem to be any more sleep-of-death issues (this seems to have ended the last build).
* Over-The-Air updates are now possible, simply check for updates from System->About (after flashing this image).
03/08/2016
* Recents button is now working (thanks @Has.007 !).
* I'm not going to be uploading any new images because I'm currently working on getting the kernel to build from
source, and (I'm occupied with exams and schoolwork in general), so no new images are going to be pushed until this works properly (I had
to cobble this one together from a failed build on the custom kernel).
31/07/2016
* Added a few tweaks concerning CPU frequency scaling so there should be power savings from that as well as lowered device temperatures.
* Kernel Adiutor frequency scaling now works properly.
30/07/2016
* The previous update was buggy and kept crashing, I pulled that one and uploaded a new one which should hopefully fix that.
29/07/2016
* Minor tweaks
25/07/2016
* Both front and rear camera work as expected now.
* Trebuchet now displays the lock screen image properly.
* Trebuchet now displays full windows in the Recent Apps switcher.
* GPS is working
24/07/2016
* WIP - I had uploaded an image but I pulled it because filesystem mounting was broken in this build.
* I have pushed a new image, but something broke in the build which is preventing the sdcard from being mounted at boot by Vold (an
explicit entry had to be put in the fstab). I will be reverting changes and looking for a fix so there might be no build for the next few
days.
* Mobile data is now working in this build, but phone calls can still neither be placed nor received.
* System detects SIM card properly.
* GPS is not working.
* Rear camera works properly with the default camera app, however the front camera does not work with the default application and trying
to switch to it will cause the app to crash and refuse to open.
* Recents button is still not working (I had thought I fixed it but apparently it isn't working).
23/07/2016
* Limited mobile connectivity [ sending/receiving texts ].
- Calls can be received or made but there is no audio (speaker or microphone).
- Mobile data is not working.
- Currently the system does not show the mobile connection as active, but texts can still be sent and received.
* Screen brightness controls working
22/07/2016
* Limited mobile connectivity [ sending/receiving texts ].
Currently the system does not show the mobile connection as
active, but texts can still be sent and received.
* Fixed troublesome cgroups problem, meaning:
Apps can now be installed on the device; and
Apps no longer crash.
* Minimal camera capability - camera image is distorted, and only back camera works.
21/07/2016
* Wifi connectivity now available. [module has to be manually loaded - use adb shell su modprobe wlan ]
* Bluetooth is now working.
* GPS is working.
* Audio is working (microphone, speaker)
* Multimedia playback working
* Sensors are working (magnetic, rotation/gyro,proximity)
21/07/2016
* Initial image created.
Known Issues
======================================================================================================================================================================================
All devices
Format: [PRIORITY] Issue.
[LOW] FM Radio app is not working
======================================================================================================================================================================================
Click to expand...
Click to collapse
Issue Reporting
You can report issues with the ROM here on this forum.
Contribute
If you are familiar with Makefiles and the Linux shell, (optionally Java, C, C++) you can contribute directly to the
project by collaborating on working on the device and vendor trees.
You can also just download the ROM and report any issues and submit logcats.
Kudos
@Xenotoad for the extra build server [Bilbo].
ViPER520 and zhuhang for the awesome equaliser (Viper4Android).
@zim555 for the audio fix, and various other bits from his device sources.
@baran0119 who did some work on the G530FZ and on whose work the source is based on.
Screenshots
Here's the logcat for the kernel adiutor frequency issue. Let me know if there's anything else you need.
i'm new here but..
yesterday I installed this rom on my SM-G530W and I'm so happy with it. The front camera on default camera app is working perfectly fine. All that I desperately want fixed soon is data and calling :crying:
joe_5579 said:
yesterday I installed this rom on my SM-G530W and I'm so happy with it. The front camera on default camera app is working perfectly fine. All that I desperately want fixed soon is data and calling :crying:
Click to expand...
Click to collapse
Hi Joe,
The mobile data should be working on this build, did you try enabling it and checking?
vince2678 said:
Hi Joe,
The mobile data should be working on this build, did you try enabling it and checking?
Click to expand...
Click to collapse
It's working now glad its working. Thank you btw for this rom once again. Question: If you were to fix an issue, would i have to just update my cyanogenmod to get the issue fixed?
joe_5579 said:
It's working now glad its working. Thank you btw for this rom once again. Question: If you were to fix an issue, would i have to just update my cyanogenmod to get the issue fixed?
Click to expand...
Click to collapse
You mean update via the System Settings? This ROM is not officially supported by Cyanogenmod, so there are no Over-The-Air updates, but you can just come here and check to see if I have fixed anything else, and download the ROM and flash it. That would indeed fix the issue.
vince2678 said:
You mean update via the System Settings? This ROM is not officially supported by Cyanogenmod, so there are no Over-The-Air updates, but you can just come here and check to see if I have fixed anything else, and download the ROM and flash it. That would indeed fix the issue.
Click to expand...
Click to collapse
Thanks
vince2678 said:
Hi Joe,
The mobile data should be working on this build, did you try enabling it and checking?
Click to expand...
Click to collapse
Hey @vince2678
I'm getting hot to flash this! Does this mean phone calling is working as well? Does sms messaging work as well?
I'm keeping an eye on your issue log but don't see (or recognize) an entry for this issue.
And I have been watching your repos and see that you have been busy!
Also, I've tried to build your ROM and I'm getting the error below. Is this as simple as adding another remove-project entry in the manifest?
+ make otapackage
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=5.1.1
CM_VERSION=
TARGET_PRODUCT=full
TARGET_BUILD_VARIANT=eng
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a
TARGET_CPU_VARIANT=generic
TARGET_2ND_ARCH=
TARGET_2ND_ARCH_VARIANT=
TARGET_2ND_CPU_VARIANT=
HOST_ARCH=x86_64
HOST_OS=linux
HOST_OS_EXTRA=Linux-4.6.4-301.fc24.x86_64-x86_64-with-fedora-24-Twenty_Four
HOST_BUILD_TYPE=release
BUILD_ID=LMY49J
OUT_DIR=/home/android/out
============================================
Checking build tools versions...
"ebtables is disabled on this build"
find: ‘dummy’: No such file or directory
build/core/base_rules.mk:154: *** platform_testing/tests/jank/webview: MODULE.TARGET.APPS.UbWebViewJankTests already defined by frameworks/webview/chromium/tests/UbWebViewJankTests. Stop.
Zippy Dufus said:
Hey @vince2678
I'm getting hot to flash this! Does this mean phone calling is working as well? Does sms messaging work as well?
Click to expand...
Click to collapse
Hey @Zippy Dufus, SMS messaging has been working for a while, and mobile data has been working since the last two uploaded builds as well. Right now, the only troublesome aspect on the radio is the telephony, which isn't working as expected, but I am investigating the issue, and I *might* have a fix by tomorrow or the end of the weekend.
[/QUOTE]
I'm keeping an eye on your issue log but don't see (or recognize) an entry for this issue.
Click to expand...
Click to collapse
All issues RIL or telephony related on the Issues page are concerning this, so don't worry, I'm definitely looking into it.
One major problem in getting things to work is that most of the proprietary binaries or libraries on the stock ROM from qcom or Samsung are simply undocumented and as such it is difficult to understand what exactly needs to be fixed to get the telephony aspect of RIL to work fully.
And I have been watching your repos and see that you have been busy!
Also, I've tried to build your ROM and I'm getting the error below. Is this as simple as adding another remove-project entry in the manifest?
+ make otapackage
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=5.1.1
CM_VERSION=
TARGET_PRODUCT=full
TARGET_BUILD_VARIANT=eng
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a
TARGET_CPU_VARIANT=generic
TARGET_2ND_ARCH=
TARGET_2ND_ARCH_VARIANT=
TARGET_2ND_CPU_VARIANT=
HOST_ARCH=x86_64
HOST_OS=linux
HOST_OS_EXTRA=Linux-4.6.4-301.fc24.x86_64-x86_64-with-fedora-24-Twenty_Four
HOST_BUILD_TYPE=release
BUILD_ID=LMY49J
OUT_DIR=/home/android/out
============================================
Checking build tools versions...
"ebtables is disabled on this build"
find: ‘dummy’: No such file or directory
build/core/base_rules.mk:154: *** platform_testing/tests/jank/webview: MODULE.TARGET.APPS.UbWebViewJankTests already defined by frameworks/webview/chromium/tests/UbWebViewJankTests. Stop.
Click to expand...
Click to collapse
I don't get this issue under my build. It looks like you have duplicate declarations for some tests in your build directory, could you try erasing all the code in your build directory and re-initialising it as follows:
Code:
cd /path/to/build/directory
rm ./*
repo -j sync
Making sure not to erase the .repo hidden directory in the build directory.
PS: I hadn't noticed this before, but it looks like you might have forgotten to do a . build/envsetup.sh && lunch cm_gprimeltecan_userdebug before running make -j otapackage, try that first, and if it doesn't work, then try resetting your build directory.
Is camera have bug with manual focus with flash or not?
snthe said:
Is camera have bug with manual focus with flash or not?
Click to expand...
Click to collapse
Hi snthe,
The cameras seem to be working correctly, if you have any issues, could you detail them more fully so that I can understand the problem?
Thanks.
vince2678 said:
Hi snthe,
The cameras seem to be working correctly, if you have any issues, could you detail them more fully so that I can understand the problem?
Thanks.
Click to expand...
Click to collapse
thx for your reply bro,but i not use your variant. I use 530H.
I ask that to u because on our cm12.1 camera when set to 8mp and use flash screen flickering.. This is the thread http://forum.xda-developers.com/gra...ailybuild-cm12-1-galaxy-grand-prime-t3345897/
Maybe u can help us to fix that if u not encountered that bug on yours
snthe said:
thx for your reply bro,but i not use your variant. I use 530H.
I ask that to u because on our cm12.1 camera when set to 8mp and use flash screen flickering.. This is the thread http://forum.xda-developers.com/gra...ailybuild-cm12-1-galaxy-grand-prime-t3345897/
Maybe u can help us to fix that if u not encountered that bug on yours
Click to expand...
Click to collapse
Hi,
Sorry, I don't think I can help, to fix such an issue I'd have to have the device to work with. You should ask one of the devs on the ROM to look for a solution to that.
settings>buttons>home button>double tap for recently used apps (until recents button is fixed)
Please try flashing this nd see if the Recent Key works.
I warn you to take a full backup before flashing.
Hello guys i've got a FZ Too and i'll help you to test this rom ! Thanks for porting this cyanorom on our grand prime !
This ROM is correct for daily usage ? :/
Okay so, i wanna dial *611 to top up my plan, but calls cannot be placed (i'm aware of the problem already) help?
MiQuenDroid said:
This ROM is correct for daily usage ? :/
Click to expand...
Click to collapse
Not quite, or rather, that depends on what and how you use it daily.
But, the short answer: Not yet (almost? ).
joe_5579 said:
Okay so, i wanna dial *611 to top up my plan, but calls cannot be placed (i'm aware of the problem already) help?
Click to expand...
Click to collapse
As of the image(s) from 03/08/2016, calls can now be made and received, BUT *audio* calls cannot be placed or received because the audio is not being routed correctly for some reason. Dialling USSR codes should still work fine.
This mod has since been discontinued in favor of Adaway. Read on for information on how to use Unified Hosts with Adaway
What are Unified Host Files?
Unified host files combine many reputable sources into a single hosts file (with duplicates removed). Some examples include adaway, mvps, yoyo.org, and malware domain list (see Steven Black's page here for a complete list).
Adaway Installation for Magisk:
Adaway version 4.x now works properly with magisk systemless hosts. To enable it, just install the latest version from here (the main xda thread for it hasn't been updated for it yet). Then go to Preferences -> Enable systemless mode. This automatically enables the Systemless hosts option in magisk manager so no need to bother with that. Then use the app as normal.
How to Add Unified Hosts to Adaway:
In the adaway app, go to Preferences -> Redirection IP (NOT Allow Redirects). Change the value to 0.0.0.0. Read the readme on Steven Black's GitHub linked above for why.
Then go to Hosts Sources. Then add the url of the unified hosts you want (ONLY CHOOSE 1):
Master: https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
Master+FakeNews: https://raw.githubusercontent.com/StevenBlack/hosts/master/alternates/fakenews/hosts
Master+Gambling: https://raw.githubusercontent.com/StevenBlack/hosts/master/alternates/gambling/hosts
Master+Porn: https://raw.githubusercontent.com/StevenBlack/hosts/master/alternates/porn/hosts
Master+Social: https://raw.githubusercontent.com/StevenBlack/hosts/master/alternates/social/hosts
Master+FakeNews+Gambling: https://raw.githubusercontent.com/StevenBlack/hosts/master/alternates/fakenews-gambling/hosts
Master+FakeNews+Porn: https://raw.githubusercontent.com/StevenBlack/hosts/master/alternates/fakenews-porn/hosts
Master+FakeNews+Social: https://raw.githubusercontent.com/StevenBlack/hosts/master/alternates/fakenews-social/hosts
Master+Gambling+Porn: https://raw.githubusercontent.com/StevenBlack/hosts/master/alternates/gambling-porn/hosts
Master+Gambling+Social https://raw.githubusercontent.com/StevenBlack/hosts/master/alternates/gambling-social/hosts
Master+Porn+Social: https://raw.githubusercontent.com/StevenBlack/hosts/master/alternates/porn-social/hosts
Master+Fakenews+Gambling+Porn (This is the one I use): https://raw.githubusercontent.com/StevenBlack/hosts/master/alternates/fakenews-gambling-porn/hosts
Master+Fakenews+Gambling+Social: https://raw.githubusercontent.com/StevenBlack/hosts/master/alternates/fakenews-gambling-social/hosts
Master+Fakenews+Porn+Social: https://raw.githubusercontent.com/StevenBlack/hosts/master/alternates/fakenews-porn-social/hosts
Master+Gambling+Porn+Social: https://raw.githubusercontent.com/StevenBlack/hosts/master/alternates/gambling-porn-social/hosts
Master+Fakenews+Gambling+Porn+social: https://raw.githubusercontent.com/S...lternates/fakenews-gambling-porn-social/hosts
You can then uncheck the host sources already added by default to adaway since they're included in unified hosts sources already
**Note that the 'Social' filter does exactly what you think: blocks social networks. So if you use any kind of social networking, DO NOT CHOOSE THIS ANY SOURCE WITH THIS IN IT**
Using a APN that uses a proxy server or a subsidiary provider and unable to get adblocking working? See here for a fix
Original Mod Information:
Description
Blocks ads by using Steven Black's Unified Hosts
Comes with a small utility based off of LarappsOfDongle's RP modular host module that allows you to choose which kind of host file you want (adware/malware, fakenews, gambling, porn, social, or any combination)
Installation
Go to Settings in Magisk Manager and enable 'Systemless Hosts'
Flash module
Open terminal and type:
Code:
su
hosts
Then follow the prompts to install the host file of your choice.
OR
- Open terminal and type:
Code:
su -c hosts arg1 arg2 arg3
- The script will apply your arguments all at once and close. Useful for automation purposes
- For example: `su -c hosts m wr b`
- Script will apply the master filter, then your regex whitelist, then your blacklist
Updating Hosts:
Just run the hosts file again in terminal and it'll overwrite the old one
Note: The script will now notify you to say if you need to update or not at the top of it
Disabling Host Mod:
Just toggle the enable systemless hosts option in magisk manager
Whitelist Instructions:
Create an empty file on sdcard card called "whitelist"
Either add exact lines you want remove to it -> Run hosts script and choose whitelist option
For example:
Code:
0.0.0.0 facebook.com
Will unblock facebook.com
Or add regex for lines you want removed -> Run hosts script and choose whitelist regex option
For example:
Code:
.*facebook.*
Will unblock all domains with "facebook" in them
Blacklist Instructions:
Create an empty file on sdcard card called "blacklist"
Add exact lines you want to remove it (do not include the 0.0.0.0 -> so for example: "facebook.com")
Run hosts script and choose blacklist option
For example:
Code:
google-analytics.com
Will block the google-analytics.com domain (it will add the entry "0.0.0.0 google-analytics.com" to the hosts file - note the lack of the 0's here. The script takes care of it automatically for the blacklist feature)
To Remove Whitelist:
Just run hosts script and reinstall host file of choice
Latest Magisk Version Compatibility:
15.x
Source
Can't Boot?
Try rebooting into the bootloader, then boot into system. Thanks @rignfool for the tip
Bonus!
I made a quick automate flow to update the hosts file. Just import it, add a shortcut to your home screen, and you can update it in one click
Just change the 2nd block to whatever options you want
@Didgeridoohan made a tasker profile here for any who use tasker: https://forum.xda-developers.com/showpost.php?p=73369050&postcount=451
Download
How does this differ from AdAway?
serubin323 said:
How does this differ from AdAway?
Click to expand...
Click to collapse
The unified hosts file combine many sources including AdAway, mvps, malware domains, and more. Check out steve black's page in the op for a full list.
Also, for some reason, adaway wouldn't detect the systemless hosts file for me so i had to set a custom path and symlink it
Updated module for latest magisk manager update (required changes to the readme). Doesn't change the functionality of the module at all so if you're in 1.1, there's no need to upgrade since these readme changes will only be reflected in magisk manager once this module is approved into the repo.
Damnit... Wrong thread...
OK...
Syntax...
su -c hosts ______
Please fill in the blank...
rignfool said:
Damnit... Wrong thread...
OK...
Syntax...
su -c hosts ______
Please fill in the blank...
Click to expand...
Click to collapse
Code:
su
Give root permissions
Code:
hosts
Program will prompt for input. For example, if you want malware/adware (master) + fakenews + gambling, you're input would be:
Code:
fg
The reason for not including the master (adware/malware) in the arguments is that it's already included by default in each host file. So the fakenews host file is actually master + fakenews. It's how steven set it up so I have no control over it (and who wouldn't want the malware block anyways)
Found a typo in the directions for the host file. Once again doesn't effect functionality at all but does eliminate confusion so uploaded fixed version (sorry)
Zackptg5 said:
Give root permissions
Program will prompt for input. For example, if you want malware/adware (master) + fakenews + gambling, you're input would be:
Click to expand...
Click to collapse
I'm looking to execute as a one line shell command with tasker...
So I'm using 'su -c' cuz SU detection in tasker with magisksu is broken...
Then hosts... But I want to run with an argument so I don't need to interact with the script... Just have it update the hosts file...
rignfool said:
I'm looking to execute as a one line shell command with tasker...
So I'm using 'su -c' cuz SU detection in tasker with magisksu is broken...
Then hosts... But I want to run with an argument so I don't need to interact with the script... Just have it update the hosts file...
Click to expand...
Click to collapse
I've never used tasker (use automate instead). Perhaps
su -c; hosts; sleep 1; fgps; sleep 2; q
Not sure if the sleep command works for tasker (linux thing) but if there's a way to have it wait a half a second or so before inputting the next command, and then waiting 2 seconds or so to quit after the hosts is applied (not sure on the time, just guessing).
Edit, just saw you didn't want to deal with the script. The 'hosts' command is the script. If you look my source for the hosts script, it lists each url for the file and what it does. So all of the terminal code for fgps would be:
Code:
su -c
cd /magisk/.core
wget -O hosts --no-check-certificate https://raw.githubusercontent.com/StevenBlack/hosts/master/alternates/fakenews-gambling-porn-social/hosts
This will replace the systemless hosts file with the one you want. Note you will at least need the wget portion of the module (system/bin) since it's not included in most roms
v1.3 update: Noticed that the disable option was broken so I removed it since it's not needed (see OP for disable instructions)
Using ze551ml, after rebooting, module disappeared. I can't find hosts command anywhere.
danzel said:
Using ze551ml, after rebooting, module disappeared. I can't find hosts command anywhere.
Click to expand...
Click to collapse
Does magisk manager say root is enabled? There's been an ongoing issue where root will disappear and so all modules will disappear as well. This isn't a module issue but a magisk issue
Automating hosts update?
Hi Zack!
Love your module, thank you!
Is there a way I can update with FG running a shell command from Tasker?
When I try
Code:
echo fg|hosts
it does download the fg file, but then it infinitely loops and never quits, until I send a CTRL-C to the terminal.
Could you please make it so hosts accepts arguments from the command line, instead of a menu?
Thank you!
Yom said:
Hi Zack!
Love your module, thank you!
Is there a way I can update with FG running a shell command from Tasker?
When I try
Code:
echo fg|hosts
it does download the fg file, but then it infinitely loops and never quits, until I send a CTRL-C to the terminal.
Could you please make it so hosts accepts arguments from the command line, instead of a menu?
Thank you!
Click to expand...
Click to collapse
The menu is part of the command line. I don't have tasker however, maybe this post will help: https://forum.xda-developers.com/showpost.php?p=71117156&postcount=9
You can circumvent running the script completely and just wget your host of choice. In that post, I have a link to the source for the hosts file with all of the urls. For fg for example, it would be: https://raw.githubusercontent.com/StevenBlack/hosts/master/alternates/fakenews-gambling/hosts
Yom said:
Hi Zack!
Love your module, thank you!
Is there a way I can update with FG running a shell command from Tasker?
When I try
Code:
echo fg|hosts
it does download the fg file, but then it infinitely loops and never quits, until I send a CTRL-C to the terminal.
Could you please make it so hosts accepts arguments from the command line, instead of a menu?
Thank you!
Click to expand...
Click to collapse
As @Zackptg5 says, to automate with Tasker it's easier to just circumvent the script altogether...
I have a Tasker profile set up to fetch the hosts file directly from Steven Blacks GitHub and save it to /magisk/.core/hosts. I couldn't get wget to work properly with Taskers Run Shell, so I used the HTTP Get instead to fetch it to /sdcard and then Run Shell to move it to /magisk/.core/hosts (and to remove it from /sdcard afterwards).
Is there a possibility of whitelists?
ChronoReverse said:
Is there a possibility of whitelists?
Click to expand...
Click to collapse
In theory, you shouldn't need a white list with these hosts files. I chose them because they are gone over with a fine tooth comb so you shouldn't have any issues. However, when I get on spring break, I could attempt to add a whitelist option to the script. I was thinking the easiest way to do this would be to read a text file (would be a blank one in the module folder by default but is editable the uses to add whatever) and remove any matches from the host file. Have any better ideas to implement this? I have no experience with GUI development and that would add unnecessary overhead anyways
Does this module work currently? I disabled adaway and enabled this but it's not blocking ads that adaway blocks.
Testcase: root check by Jrummy
Adaway blocks the in app ads. This module does not
EDIT: apparently I can't read... Lol. Followed the Op and now it works great!
Neat module. It's working great! Thanks for sharing it!
Yom said:
Hi Zack!
Love your module, thank you!
Is there a way I can update with FG running a shell command from Tasker?
When I try
Code:
echo fg|hosts
it does download the fg file, but then it infinitely loops and never quits, until I send a CTRL-C to the terminal.
Could you please make it so hosts accepts arguments from the command line, instead of a menu?
Thank you!
Click to expand...
Click to collapse
I have a profile set up to do this every 12 hours. If you still need it, I updated it to use your preferred settings and exported it. All you need to do is import it in Tasker (long-press Profiles header) and turn it on.
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