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
Related
If I use the latest jachero rom will apps2sd be done for me? If not then can anyone explain to me what I need to do.
JACHero roms automatically do apps to sd on boot up/reboot
Yes it does, but c'mon, was this thread really necessary?!
JACHero 2.7.3
-Rosie.apk modifications to fix open folder view in Rosie
-Reverted Boot Graphics untill I can get the .gif looking better
JACHero 2.7.2
-I borked the boot graphics on this one haha!
JACHero 2.7.1
-Maps.apk replaced with GoogleMaps due to GPS
-WorldClock.apk reverted due to Alarm issues
-Status Bar pull down modified to fill corners
JACHero 2.7
* 2.6.29 Modifed Kernel
* Enhanced ramdisk with auto EXT2/EXT3 mount
* Cyanogens Apps2SD with a2sd ran before user runtime starts
* Includes E2FSProgs for checking and converting Ext filesystems (Thanks Cyanogen!)
* Apps2SD is automatic. All you need is a second partition.
* Supports ext2/ext3 for Apps2SD
* Linux-Swap is automatic! All you need is a linux-swap partition (32MB~)
* fsck at boot (should stop FS corruption)
* Tweaked frequency scaling options to be more responsive (Thanks Cyanogen!)
* Maximum CPU scaling frequency set to 384MHz
* TCP buffer changes
* PATH variable updates
* Calls to /data/init.rc /system/init.rc
-Working Audio/Modified for better speaker/mic clarity
-Auto backlight turned off by default in build.prop
-rwsystem, rosystem for easy remount from terminal (Thanks Soulife!)
-RIL optimizations
-lucid already in /system/bin
-EN_US (Thanks db.hates.you)
-DalvikVM optimized
-Framework optimized
-png's optimized with optipng
-Multi-Touch
-Stock Rosie.apk (modifieds are not needed)
-Launcher included
-Linux-swap support
-Flash 9
Click to expand...
Click to collapse
Its his first post... surprised? Noobs, just because you're new here, doesn't mean ask questions without looking first, especially in the most obvious of places. This forum is not meant as a replacement for the search button, but as the next step if you really really can't find your problem, if we get more of these threads, the pros won't know who to help with all these easily searched up problems...
I came across this application on the dream forums:
http://forum.xda-developers.com/showthread.php?t=558108
Haven't managed to get it working yet as I need to load a rom with busybox support (will be doing so shortly).
Been trying to get this to work, but it's crashing on connect at the moment for me, seems like it is for some other people too, judging by the thread.
i got some errors too , i think this is due to the modified busybox that enable color in ls like this
Code:
D:\ANDROID\RECOVERY>adb shell
# ls
ls
←[1;34mcache←[0m ←[1;32minit.goldfish.rc←[0m ←[1;34msbin←[0m
←[1;34mdata←[0m ←[1;32minit.hero.rc←[0m ←[1;34msdcard←[0m
←[0;0mdefault.prop←[0m ←[1;32minit.rc←[0m ←[1;34msqlite_stmt_journals←[0m
←[1;34mdev←[0m ←[0;0mlogo.rle←[0m ←[1;34msys←[0m
←[1;36metc←[0m ←[1;34mproc←[0m ←[1;34msystem←[0m
←[1;32minit←[0m ←[1;34mroot←[0m
#
i managed to disable the color by doing a new alias for ls
Code:
alias ls="ls --color=never"
but if you close the shell and reopen a new one , it doesnt save this setting.
may be it can be fixed by enabling a .profile file , but i havent got time to check
I haven't looked into it at any great depth yet, but mine is doing the same. Looks like an awesome app!
they are working on a correction
http://de.codeplex.com/Thread/View.aspx?ThreadId=66743
I rebuild the sofware from source , this build fix the freeze crash at startup due to the LS bug ( some roms use a new version of busiybox , that enabled color sheme by default , and adds strange caracter in some terminal)
Code:
so i change the ListDirectoryCommand option
Resources.resx in DroidExplorer.Core/Properites and change: ls -lF {0} to busybox ls -lF {0} --color=never
here is the zip file , just copy it to the installation dir
soory the rar files didnt attached
EDIT: not everything seems to work , like process explorer , ....
noescape said:
I rebuild the sofware from source , this build fix the freeze crash at startup due to the LS bug ( some roms use a new version of busiybox , that enabled color sheme by default , and adds strange caracter in some terminal)
Code:
so i change the ListDirectoryCommand option
Resources.resx in DroidExplorer.Core/Properites and change: ls -lF {0} to busybox ls -lF {0} --color=never
here is the zip file , just copy it to the installation dir
Click to expand...
Click to collapse
Thanks. Will give it a try tonight!
Nice work noescape - no longer crashes!
Thanks
PS. Screencast is awesome!
official new realsed
Change log 0.7.4.0
* Changed the SdkInstallDialog to use a WebRequest instead of the WebClient. Hopefully this will help some peoples issues...
* Window settings are now saved and reloaded.
* Remembers the folder view state (large icon, details, etc)
* added --color=never to directory listing command. this should fix the issue people with Heros are having
* moved the options dialog tree config to its own file, as it really isnt configured by the user.
* added batch installer plugin (alpha) that can install/uninstall multiple apk's at one time.
* added logging info for droid explorer. (saved in %USERAPPDATA%\DroidExplorer\logs)
* it should also handle "unhandled" errors better
* wired up Tools menu items
* Added property to indicate if a plugin can be ran by the Runner
* Jumplist items added for runnable plugins
Android Open Source Project 6.0
Marshmallow
for
Samsung Galaxy Tab 10.1
(P7510, P7500, SGH-T859)
(p4wifi, p4, p4tmo)
Customizations:
busybox
init.d scripts
CMFileManager
Kernel features:
CPU overclock (1.2Ghz - 1.6Ghz)
CPU voltage control
CPU temperature readings
GPU overclock (400Mhz)
L2 cache optimization
F2FS
SELinux
Voodoo Sound
USB Charging
Updated WIFI driver
ZRAM backports
sdcardfs
Working:
Video
Audio
WIFI
Cellular
GPS
Bluetooth
- Audio playback: working
- File transfer: working
Encryption
Not working / buggy / needs testing:
Camera
- Pictures: working
- Video recording: (not working)
Dock audio
Keyboard dock (untested)
- Likely the same status as Lollipop
Tethering
- USB tethering: working with WIFI
- Bluetooth tethering: (not working)
- WIFI tethering: (untested)
Wireless Display / Miracast
- No compatibility with the outdated video blobs
Installation:
Backup all data
Install TWRP 2.8.7.0 or newer
Wipe cache, dalvik cache, system, data
Install the ROM
Optional step:
- Install gapps pico
- Install Supersu 2.52
Boot the ROM
Enable on screen keyboard by toggling "Show input method"
Downloads:
p4wifi (GT-P7510): WIFI only tablet.
aosp-6.0-p4wifi-20160806.zip
p4 (GT-P7500): Cellular / 3G tablet.
aosp-6.0-p4-20160809.zip
p4tmo (SGH-T859): T-Mobile tablet.
p4wifi and p4 users do NOT install this.
aosp-6.0-p4tmo-20160809.zip
mirror: AndroidFileHost
GApps
http://opengapps.org/
root: SuperSU
BETA SuperSU v.2.52
Mirrors:
Android File Host
Changelog
Code:
August 9, 2016
decatf/android_kernel_samsung_p4
e602201 defconfig: Fix typo while enabling CONFIGFS_FS
August 6, 2016
Update to android-6.0.1_r59
decatf/android_kernel_samsung_p4
2c421f2 fuse: O_DIRECT support for files
3bb1d41 fuse: remove the second argument of k[un]map_atomic()
acf44b5 fuse: verify all ioctl retry iov elements
1b17d75 fuse: postpone end_page_writeback() in fuse_writepage_locked()
d88af9d fuse: break infinite loop in fuse_fill_write_pages()
33c337c fuse: support ioctl on directories
37bb785 FUSE: Notifying the kernel of deletion.
f7c8478 fuse: Add support for shortcircuited read/write for files
d5c6ade Revert "fuse: Add support for shortcircuited read/write for files"
04ed83b fuse: Add support for shortcircuited read/write for files
ab0b217 fs: fuse: Ensure update of fuse inode attributes in shortcircuit
b653a54 fuse: Use iocb->ki_pos instead of pos for shortcircuit writes
b79cfba fuse: Use BUG_ON to check pos validity in fuse_aio_write
786913d fs: fuse: Disable shortcircuit when mmap is called on a file
bfc19a7 vfs: add d_canonical_path for stacked filesystem support
fb6bb3e inotify: Fix erroneous update of bit count
8bae312 Initial port of sdcardfs
568217e get rid of kern_path_parent()
7233db3 sdcardfs: Port to 3.4
a5d5845 sdcardfs: Port to 3.1.10
4cede1c sdcardfs: Changed type-cast in packagelist management
3f69353 sdcardfs: Bring up to date with Android M permissions:
dfc2ff3 sdcardfs: Add support for d_canonicalize
1f80a89 sdcardfs: remove effectless config option
dd5eccf sdcardfs: Remove unused code
1b8979a sdcardfs: remove unneeded __init and __exit
1c16f89 sdcardfs: Truncate packages_gid.list on overflow
560043c ANDROID: sdcardfs: fix itnull.cocci warnings
d3e1021 vfs: change d_canonical_path to take two paths
e587970 fuse: Add support for d_canonical_path
434e90b defconfig: Enable sdcardfs
e7b5ee2 BACKPORT: perf tools: Document the perf sysctls
90bd458 FROMLIST: security,perf: Allow further restriction of perf_event_open
1ccaa78 defconfig: restrict access to perf events
android_device_samsung_p4-common
8404df3 p4-common: Enable sdcardfs
913957d p4-common: Disable EGL_WORKAROUND_BUG_10194508
5f67070 p4-common: sepolicy: Allow kernel to rw wifi efs file
android_vendor_decatf
6bbd9c6 sepolicy: remove BOARD_SEPOLICY_UNION
91f8dc2 sepolicy: Add rule to allow sdcardfs to read package list
8209b59 sepolicy: Fix MTP for sdcardfs
android_bionic
546aae2 bionic: Sort and cache hosts file data for fast lookup
platform_frameworks_base
0454407 mountservice: Shut down volumes before restarting framework
9baa27d mountservice: Don't nuke all volumes when decrypting
android_frameworks_opt_net_wifi
d21014b Revert "Revert "wifi: Set the mode at native layer""
platform_system_core
a052e68 sdcard : Use the fuse shortcircuit option
86faebc sdcard: Allow fuse shortcircuit for all platforms
e06eb06 sdcard: Add support for sdcardfs!
d3a24ca sdcard: Fix sdcardFS check
6ff0e73 sdcard: Pass the umask to sdcardfs correctly
android_external_sepolicy
5d57d80 sepolicy: Add policy for sdcardfs and configfs
July 8, 2016
Update to android-6.0.1_r50
Restore previous WIFI driver
June 15, 2016
TRIM is now merged into this ROM. You don't need to install the TRIM kernel from the other thread.
Update to android-6.0.1_r46
74f7de9 p4-common: TCP buffer settings
93ca209 p4-common: Wifi is no longer built as a module
2133d24 p4-common: Enable dlmalloc
b6808c6 p4-common: Remove unused flags
4692beb tcp: drop SYN+FIN messages
cf415a5 misc: uidstat: avoid create_stat() race and blockage.
3f791c1 usb: gadget: f_fs: Fix enumeration in fullspeed mode
0469e56 usb: gadget: accessory: Fix section mismatch (again)
30fbe2f USB: remove duplicate out endpoint creation in MTP mode
c607c37 pipe: limit the per-user amount of pages allocated in pipes
8e01cbe power: max17042: Reduce logspam
5565950 Revert "Staging: android: binder: Allow using highmem for binder buffers"
bf9b28a Reduce logger size
9c3a8ec mmc: fix integer assignments to pointer
d7bfd4c mmc: sdio: Workaround for dev with broken CMD53
74032a4 mmc: sdio: Fix to support any block size optimally
3f9da59 mmc: sdio: Use multiple scatter/gather list
ed4849d genirq: Always force thread affinity
b1bb34f genirq: Avoid deadlock in spurious handling
c4cb3ae genirq: Fix can_request_irq() for IRQs without an action
aeaeb4de mmc: Restore MMC_CAP_ERASE
fd6a17d mmc: Add sdio_ctrl_power
8bd4f0d arm: tegra: p4: Allocate static dhd info buffer (section 7)
ec9b234 arm: tegra: p4: Built-in wifi
cfb0ab2 arm: tegra: p4: Set wifi chip id to 0x4330
ce80b1b arm: tegra: Conditionalize builtin wifi
2477c3b Revert "net: wireless: Sync with grouper android-5.1.0_r0.4"
e32e74d arm: tegra: p4: Fix build when not builtin wifi
a0d37af net: wireless: Import CFG80211_REG_NOT_UPDATED from klte kernel
62151e1 defconfig: disable loadable modules
a5cf304 net: Backport wireless stack from Galaxy S5 kernel
88d16a6 net: Fix net/wireless backport for 3.1.10
7dbf92b bcmdhd: G900FXXU1CPD7
abf9e8c bcmdhd: fixup for p4
e3c843a bcmdhd: Restore tegra specific irq wake
aa99d0d defconfig: bcmdhd builtin
716bd9c defconfig: Enable CONFIG_CFG80211_ALLOW_RECONNECT
946d13f mmc: tegra: Don't set MMC_PM_KEEP_POWER by default
9a40b65 mmc: host: sdhci: abort suspend if host suspend fails.
8d5d16f mmc: host: sdhci: Don't set MMC_PM_KEEP_POWER when suspending
6f689f2 mmc: Remove Samsung WIFI hacks
April 28, 2016
Fix headphone detection
April 14, 2016
Update to android-6.0.1_r30
March 26, 2016
project art/
20c3c84 Revert "Optimize double/float immediate loading on arm."
8037a8d Re-enable VFPv3-D16 register definitions
d53de19 Disable clang for art compiler on target
project device/samsung/p4-common/
f19dec3 p4-common: Use dalvik.vm.dex2oat-flags to specify backend
0cc66dc p4-common: Remove unused flag
84f022f p4-common: Tweak ksm settings
project frameworks/av/
111a9b9 Revert "mediaplayer: remove use-awesomeplayer developer option"
project frameworks/native/
f1b88cd Configure tablet dalvik heap for 1GB mdpi device
project kernel/samsung/p4/
2b12c4b pipe: iovec: Fix memory corruption when retrying atomic copy as non-atomic
16a60d8 Squash revert Android timerfd support
24bcc61 Android alarm-dev from android-3.4
f519a62 defconfig: enable android-3.4 alarm-dev
4ab42f7 p4_battery: Fix timer slack
7dbdfb5 ARM: 7006/1: Migrate to asm-generic wrapper support
f2b70ff ARM: 7493/1: use generic unaligned.h
33e4372 asm-generic: allow generic unaligned access if the arch supports it
a998f78 Revert "Revert "video: tegra: remove free memory check""
project packages/apps/Settings/
98144ac Revert "developer settings: remove "Use deprecated AwesomePlayer" settings"
project system/core/
6b5492a healthd: increase healthd fast timer to 10mins instead of 1min
March 14, 2016
Fix WIFI driver
March 10, 2016
Update to android-6.0.1_r17
ca6770d Align machine_kexec restart sequence with soft_restart()
b4c0a36 ARM: 7476/1: vfp: only clear vfp state for current cpu in vfp_pm_suspend
f847946 cfq-iosched: fix the setting of IOPS mode on SSDs
a74f780 arm: tegra: Restore tegra2 core/cpu voltage relationship
868ba34 Revert "bound cpu cores to same speed"
c4877ab include/linux/poison.h: fix LIST_POISON{1,2} offset
9c3f030 pagemap: do not leak physical addresses to non-privileged userspace
February 7, 2016
Update to android-6.0.1_r10
February 1, 2016
Add init.modem.rc for p4 and p4tmo
January 31, 2016
hwrotation for Galaxy Tab 8.9
January 28, 2016
Update to android-6.0.1r7
Switch to ICS audio wrapper HAL
Update to latest f2fs-stable
Frequently Asked Questions and Other notes:
Can I upgrade / dirty-flash from Lollipop to Marshmallow?
- You cannot. It must be a clean install.
Can I dirty flash over a previous Marshmallow build?
- Yes.
I thought you said Marshmallow wouldn't work.
- The problem with ART is not solved. The Optimizing compiler backend is producing binaries that crash on the Tegra 2. The Optimizing backend is the new default dex2oat compiler in Marshmallow. The Quick compiler is default backend in Lollipop. It is still in the Marshmallow source so this ROM is using the Quick compiler backend.
SELinux enforcing mode
- The default SELinux mode is permissive mode. The Set_SELinux_enforcing.zip will not work with Marshmallow. That script was setting a system property to toggle SELinux early on in boot. Google has removed the use of this system prop so that method won't work anymore.
- For now you can find some app on F-Droid to set the SELinux mode after boot. It's not ideal but it will do until some better solution arises.
Doze
- This device does not meet the hardware requirement to support Doze.
Themes
- Marshmallow supports RRO (Layers) themes. I will not add CM-12 themes, CM-13 themes, or any other theme engine.
HD video playback issues and Camera issues.
- The video and camera stack are proprietary NVidia software. This means there is no chance of fixing bugs within.
Browser crash when downloading files
- Settings > Apps > Browser > Permissions > Enable Storage permission
Google App force close
- Install GApps Pico.
- Google App now uses the NEON instruction set which the CPU on this device does not support. The pico package does not include the parts of GApps which use the NEON instruction set.
- reference post
Non-NEON Google Apps
Chrome 49.0.x
Donate:
Via Paypal
XDA:DevDB Information
Android 6.0 Marshmallow, ROM for the Samsung Galaxy Tab 10.1
Contributors
decatf
Source Code: https://github.com/decatf
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.1.x
Based On: AOSP
Version Information
Status: Alpha
Created 2015-12-08
Last Updated 2016-12-19
Problem reporting steps:
Got an error? Is something not working for you?
I cannot see what your problem is from here. Save and upload the system logs from your device so that I can see what happening on your device.
How to save system logs:
Root the device by installing SuperSU.
Install SysLog.
Reboot the system.
Reproduce the problem.
Open Syslog app and save the Kernel Log and Main Log.
Send me the log files stored in /sdcard/Syslog.
Share the files on Dropbox or another similar site.
Then PM me a link to the files. Please describe exactly what the issue is.
Some comments to start off.
The ICS audio HAL is not working right in Marshmallow and I think I'd rather try another run at getting the rest of the stuff in the open souce HAL working rather than keep trying to find hacks to keep the old blob alive. Recall that only voice calls and dock audio are not working with the open source audio HAL.
- Voice calls are just passing off audio to the Samsung cellular blobs so I don't think it's that much of a stretch to get working. But this will have to wait until cellular stuff is working in the first place.
- I found some patch for Samsung dock audio. It looks like it might apply to this device as well seeing as it seems to have a similar dock implementation. The patch is in the ROM already so that needs testing.
Cellular probably won't work for at least the first few builds. Other devices on M with a similar cellular radio needed a few new patches to get it working on M. I have put in the patches from L but we will have to trial and error what is needed for M based on other devices as a reference.
Thank you!
I know it's early on, but do you have any expectations as to how well it will run compared to previous Android version?
I appreciate all you've done, but mine never ran that great on the newest roms. It is passable and I appreciate it though.
Sent from my XT1094 using XDA Free mobile app
thank you very much for betting on this tablet , and download and I'll try ... I'm sure you will be able to tune it as we did with lp...
sflesch said:
I know it's early on, but do you have any expectations as to how well it will run compared to previous Android version?
I appreciate all you've done, but mine never ran that great on the newest roms. It is passable and I appreciate it though.
Sent from my XT1094 using XDA Free mobile app
Click to expand...
Click to collapse
The OS appears to perform the same as Lollipop. It's a four year old device. There is nothing that will make it run as well as a modern Android device. You could try setting animation times to zero and set ro.config.low_ram=true.
For Marshmallow I have added L2 cache improvements in the kernel that improves RAM speed benchmarks. That's around 1k score in Antutu.
I understand that. And again I appreciate it. I was just curious what the performance level was. I expected at best it might be similar, but more likely it would, as is typical, use more resources.
I never expected much from my Tab. Finding your ROM was an unexpected surprise. I will try those tweaks. From all of the posts I read, I got the impression that many other tablets ran better than mine. I know fully well that each tablet is different and I don't blame you or the ROM, just my tablet.
Sent from my XT1094 using XDA Free mobile app
decatf said:
The OS appears to perform the same as Lollipop. It's a four year old device. There is nothing that will make it run as well as a modern Android device. You could try setting animation times to zero and set ro.config.low_ram=true.
For Marshmallow I have added L2 cache improvements in the kernel that improves RAM speed benchmarks. That's around 1k score in Antutu.
Click to expand...
Click to collapse
Thank you for keeping this Mastodont alive. I will be doing the switch soon enough... I have been following and installing your Lollipop releases for quite a while now and appreciate very much all the time and effort you have put into these projects...
Sent from my p4wifi using XDA Free mobile app
Definitely wasn't expecting this tbh. You're doing a damn great job at keeping this tab alive decatf. Thank you for that.
Mmmh, I just did the following steps (coming from your version of 5.1.1) :
1) Installed TWRP-2710 from previously installed TWRP-2610
2) Rebooted into 2710 Recovery
3) Full Wipe
4) Install Android 6.0 ROM
5) Install OpenGapps (nano)
6) Install SuperSU 2.52
7) Reboot
Now the P4 is stuck at the Samsung boot logo, so it does not boot up.
Any ideas what I did wrong?
Regards, mistersixt.
mistersixt said:
Mmmh, I just did the following steps (coming from your version of 5.1.1) :
1) Installed TWRP-2710 from previously installed TWRP-2610
2) Rebooted into 2710 Recovery
3) Full Wipe
4) Install Android 6.0 ROM
5) Install OpenGapps (nano)
6) Install SuperSU 2.52
7) Reboot
Now the P4 is stuck at the Samsung boot logo, so it does not boot up.
Any ideas what I did wrong?
Regards, mistersixt.
Click to expand...
Click to collapse
Me too, ive installed twrp 2.8.7.0. Full wipe, install android 6 rom (P4) and use openGapps (pico), install superSU beta 2.52.
My P4 is stuck at samsung boot logo
Anyone able to install the rom successfully?
Anyways thanks decatf for all u have done for our device!
maybe don't use OpenGapps Pico?
on different devices, had issues with OpenGapps Pico versions;
especially on 5.1 and 6.0, pico may be -too- light?
I've had success with slim gapps zero on different devices;
size is similar to OpenGapps nano.
- maybe try WITHOUT any gapps?
- assuming it works, try Open nano, or slim zero?
i'll try myself and report later if I can
cheers
---------- Post added at 10:45 AM ---------- Previous post was at 10:37 AM ----------
I haven't read -too- thoroughly,
but in addition to the 'regular' supersu beta (currently 2.52),
chainfire has a separate "WIP" thread where, at least check,
2.61.. for Marshmallow+.. systemless?.. discussion is still in the 2.52 / beta thread
a) link to the WIP thread: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
b) that said, maybe for our system , 2.52 may be more appropriate?
can anyone compare?
c) hmm.. more reading.. may want to stick with 2.52 for now,
until 2.62 is ready (currently 2.61, but with planned features/fixes for 2.62)
cheer
Same thing, just did another full wipe and installed the p4 ROM only (no gapps, no supersu), and it is still stuck at the Samsung boot logo.
Regards, mistersixt.
spamam1 said:
on different devices, had issues with OpenGapps Pico versions;
especially on 5.1 and 6.0, pico may be -too- light?
I've had success with slim gapps zero on different devices;
size is similar to OpenGapps nano.
- maybe try WITHOUT any gapps?
- assuming it works, try Open nano, or slim zero?
i'll try myself and report later if I can
cheers
---------- Post added at 10:45 AM ---------- Previous post was at 10:37 AM ----------
I haven't read -too- thoroughly,
but in addition to the 'regular' supersu beta (currently 2.52),
chainfire has a separate "WIP" thread where, at least check,
2.61.. for Marshmallow+.. systemless?.. discussion is still in the 2.52 / beta thread
a) link to the WIP thread: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
b) that said, maybe for our system , 2.52 may be more appropriate?
can anyone compare?
c) hmm.. more reading.. may want to stick with 2.52 for now,
until 2.62 is ready (currently 2.61, but with planned features/fixes for 2.62)
cheer
Click to expand...
Click to collapse
It works on my p4wifi. Somebody with an actual p4 needs to try booting it then reboot directly into TWRP and grab the last_kmsg.
Code:
adb pull /proc/last_kmsg
Or
Go to Advanced > File Manager > Go to /proc/ > Tap last_kmsg > Copy File to /sdcard/
P4: wrong updater binary?
hi,
on TWRP 2.8.7.0.. try to install on P4,
but getting error:
E:Error executing updater binary in zip '/sdcard/Android/aosp-6.0-p4-20151207.zip'
maybe the binary is from p4wifi?
anyone on P4 having issues?
I checked the MD5, and it matches.
cheers
---------- Post added at 11:06 AM ---------- Previous post was at 11:04 AM ----------
spamam1 said:
hi,
on TWRP 2.8.7.0.. try to install on P4,
but getting error:
E:Error executing updater binary in zip '/sdcard/Android/aosp-6.0-p4-20151207.zip'
maybe the binary is from p4wifi?
anyone on P4 having issues?
I checked the MD5, and it matches.
cheers
Click to expand...
Click to collapse
hmm. .. donjuan10 on P4 was able to at least flash the files.
what am i doing wrong?
Hope I grabbed the right file:
http://144.76.203.117/tmp/last_kmsg
regards, mistersixt.
decatf said:
It works on my p4wifi. Somebody with an actual p4 needs to try booting it then reboot directly into TWRP and grab the last_kmsg.
Code:
adb pull /proc/last_kmsg
Or
Go to Advanced > File Manager > Go to /proc/ > Tap last_kmsg > Copy File to /sdcard/
Click to expand...
Click to collapse
spamam1 said:
hi,
on TWRP 2.8.7.0.. try to install on P4,
but getting error:
E:Error executing updater binary in zip '/sdcard/Android/aosp-6.0-p4-20151207.zip'
maybe the binary is from p4wifi?
anyone on P4 having issues?
I checked the MD5, and it matches.
cheers
---------- Post added at 11:06 AM ---------- Previous post was at 11:04 AM ----------
hmm. .. donjuan10 on P4 was able to at least flash the files.
what am i doing wrong?
Click to expand...
Click to collapse
more info..
before the error message (in red), a message about mount/symlink:
mount: failed to mount /dev/block/platform/sdhci-tegra.3/by-num/p4 at /system: Device or resource busy
symlink: some symlinks failed
?
It might just be some kernel cmdline options I missed. The reason it boots on my p4wifi is because I'm testing it on multirom which passes off some cmdline options from the host ROM so the problem was not apparent due to that.
Just install the ROM then the kernel. And the rest of the stuff as usual.
p4-kernel-aosp-6.0-20151209.zip
p4tmo-kernel-aosp-6.0-20151209.zip
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.
ShellHide
Code:
###### Copyright (c) 2018-2019 Jaymin Suthar. All rights reserved.
## Links
* [Git Repository](https://github.com/Magisk-Modules-Repo/sh-hide)
* [Super Git Repo](https://github.com/sjayminsgithub/ShellHide)
* [Support Thread](https://forum.xda-developers.com/apps/magisk/magisk-shellhide-t3855616)
## Introduction
* A shell script based alternative to MagiskHide.
* ShellHide ports MagiskHide into Shell scripts, it's intended for users who
cannot get native MagiskHide to work reliably on their devices.
* ShellHide is not a prop editor or a fingerprint mask, it's the Shell version
of MagiskHide. It will help you to pass basicIntegrity, but not ctsProfile.
* SafetyNet is added by default into hidelist, this will make sure you can use
most banking apps, games, etc...
## Details
* Features implemented: Hiding dangerous props, SELinux state, Magisk props and
non-standard mounts (Magic Mounts, /sbin overlay, loop mounts, etc...).
* How it works: Well, this question is much complex, so I'd keep it simple here.
I analyzed control flow and algorithms of MagiskHide, converted them to their
Shell equivalents that resulted into ShellHide.
* ShellHide can't be used alongside MagiskHide, if you have working MagiskHide,
I'd recommend you to stick with that.
* ShellHide features its own hidelist implementation and a commandline interface
(similar to MagiskHide), find more info about commandline usage below.
## Installation
* ShellHide requires Magisk v15.0+, mount namespace support and a reliable Shell
interpreter to work well. Once you have all these met, simply flash it either
from a custom recovery or Magisk Manager.
## Usage
Usage: sh-hide [option [argument]]
Options:
--enable Enable ShellHide
--disable Disable ShellHide
--launch Launch ShellHide daemon
--add PROCESS Add PROCESS to hidelist
--remove PROCESS Remove PROCESS from hidelist
--list Print current hidelist
## SafetyNet
* ShellHide helps to pass basicIntegrity, but to pass ctsProfile, I recommend
'MagiskHide Props Config' module by @Didgeridoohan.
## Support
* If you have any issues, reports, requests or queries, feel free to post about
it in official 'Support Thread'.
* Please always be detailed and include relevant logs, I won't be able to help
you without any missing logs.
* ShellHide dumps all logs into MOUNTPATH/sh-hide/log folder where MOUNTPATH is
magisk.img mountpoint, always include them.
## Thanks to
* @topjohnwu for their open source spirit.
* @Didgeridoohan for featuring my module.
## License
* I have kept just the same open source spirit as of original MagiskHide, see
[this parent repo](https://github.com/sjayminsgithub/ShellHide) for details.
XDA:DevDB Information
ShellHide, Tool/Utility for the XDA Community Apps
Contributors
JayminSuthar
Source Code: https://github.com/sjaymin1001/ShellHide
Version Information
Status: Stable
Current Stable Version: 1.7
Stable Release Date: 2019-02-11
Created 2018-10-18
Last Updated 2019-02-18
Changelog
Code:
#### 1.7
* Fix most known bugs, including logcat parsing issue.
* Rework scripting style to make it more standardized.
#### 1.6
* This is a major release containing many bugfixes and improvements.
* Fix process name identification and PID parsing from logcat.
* Use name of hidden processes' for their separate logfiles.
* Clone MagiskHide's nature when initializing hidelist (kill).
* Fix incorrect "Please disable MagiskHide first" messages.
* Fix mountpoints parsing regex' when in process' namespace.
#### 1.5
* Fix an issue where ShellHide daemon will not launch.
* Fix errors with add/removing processes from hidelist.
* Log ShellHide daemon errors as well as progress.
* Add separate logfiles for each hidden process.
* Add debugging info to documentation.
#### 1.4
* Add logging support to allow debugging.
* Fix logcat output not parsed correctly.
#### 1.3.1
* This is a bugfix release, please update ASAP.
* Fix incorrect path to config file.
* Fix MagiskHide status detection.
#### 1.3
* Support newer /sbin/.magisk/img path.
* Make reforking the daemon better.
#### 1.2
* Beautify user interface.
* Move core files to ShellHide folder.
* Improve daemon forking logic.
* Internal code reorganization.
* Make boot script POSIX compliant.
* Fix incorrect commandline messages.
#### 1.1.3
* One more critical bugfix, please update.
* Fix incorrect paths for mount namespaces.
#### 1.1.2
* Another bugfix release, but just too quick.
* Fix daemon exiting when logcat is EOF.
* Fix commandline usage output.
#### 1.1.1
* Fix Magisk public releases identified as Canary builds.
#### 1.1
* This is a minor release focused on performance and bugs.
* Speed up logcat parsing.
* Ensure mount namespaces support.
* Fix daemon lacking BusyBox.
* Speed up general test commands.
#### 1.0
* This is major release focusing on performance and features.
* Add ability to manage ShellHide via commandline interface.
* Add various tweaks and upstream changes to improve speed.
* Add our own hidelist apart from MagiskHides' provided one.
* Fix many possible bugs that might affect non-standard setups.
#### 0.3
* Remove hiding "/" feature.
* Fix unmounting failing (no umountexp()).
* Fix unmounting failing (no $PID).
* Update documentation.
#### 0.2
* Fix mounts not actually unmounting.
* Terminate processes instead of killing them.
* Update documentations.
#### 0.1
* Initial beta release.
Downloads are here.
sh_hide-1.7-201902111-stable-signed.zip
sh_hide-1.6-201812251-stable-signed.zip
sh_hide-1.5-201812221-stable-signed.zip
sh_hide-1.4-201812171-stable-signed.zip
sh_hide-1.3.1-201812131-stable-signed.zip
sh_hide-1.3-201812121-stable-signed.zip
sh_hide-1.2-201811141-stable-signed.zip
sh_hide-1.1.3-201811133-stable-signed.zip
sh_hide-1.1.2-201811132-stable-signed.zip
sh_hide-1.1.1-201811131-stable-signed.zip
sh_hide-1.1-201811071-stable-signed.zip
sh_hide-1.0-201811061-stable-signed.zip
sh_hide-0.3-201810271-stable-signed.zip
sh_hide-0.2-201810181-stable-signed.zip
sh_hide-0.1-201810141-stable-signed.zip
ShellHide will help you to pass basicIntegrity, but if you can't pass ctsProfile, I recommend MagiskHide Props Config module by @Didgeridoohan.
If you have any issues, reports, requests or queries, feel free to post about it in official 'Support Thread'.
Please always be detailed and include relevant logs, I won't be able to help you without any missing logs.
ShellHide dumps all its logfiles into MOUNTPATH/sh-hide/log folder where MOUNTPATH is magisk.img mountpoint.
Always include these logs to help diagnose the issue properly.
Reserved #4
Reserved #5
Well done.
I'm unsure about your hideroot function. What does it attempt to do?
Magisk missing
So i flashed your .zip as instructed, but now the Magisk Manager is not recognizing Magisk at all. It says it is not installed and I can't use any modules.
Edit: Lucky I had a TWRP Backup ready, but it seems that something really went wrong with the installation of the script
RoundtripShadow said:
So i flashed your .zip as instructed, but now the Magisk Manager is not recognizing Magisk at all. It says it is not installed and I can't use any modules.
Click to expand...
Click to collapse
Probably because of this:
Fif_ said:
Well done.
I'm unsure about your hideroot function. What does it attempt to do?
Click to expand...
Click to collapse
I haven't installed the module, just read the code.
The hideroot function has a bug I think (or maybe it's just plainly malicious where a hard link to a directory is attempted between /sbin and /root, followed by a wipe of Magisk binaries in /sbin. I didn't follow the logic, and I asked the author, who has been quiet so far.
That may be how you lost Magisk. I haven't seen anything else obviously bad in the script, so hopefully it's just a serious bug.
In the meantime, I'd strongly advise to avoid this module or at least make a backup before trying it out (which is good practise anyways).
kernel without namespaces
I have kernel 3.4.0-606 on galaxy s4.
This kernel doesn't support name spaces so I can use magisk but I can not use Magisk Hide.
Ther is not possible to check (set up) checkboxes at all.
Does Sh-hide need namespaces?
Is it possible to other method than list of apps in MagicHide?
YanecXDA said:
I have kernel 3.4.0-606 on galaxy s4.
This kernel doesn't support name spaces so I can use magisk but I can not use Magisk Hide.
Ther is not possible to check (set up) checkboxes at all.
Does Sh-hide need namespaces?
Is it possible to other method than list of apps in MagicHide?
Click to expand...
Click to collapse
Like the real MagiskHide, this module depends on name space separation support.
There are other problems with the module anyways, please read the posts before yours.
Fif_ said:
Probably because of this:
I haven't installed the module, just read the code.
The hideroot function has a bug I think (or maybe it's just plainly malicious where a hard link to a directory is attempted between /sbin and /root, followed by a wipe of Magisk binaries in /sbin. I didn't follow the logic, and I asked the author, who has been quiet so far.
That may be how you lost Magisk. I haven't seen anything else obviously bad in the script, so hopefully it's just a serious bug.
In the meantime, I'd strongly advise to avoid this module or at least make a backup before trying it out (which is good practise anyways).
Click to expand...
Click to collapse
Can confirm, installing this wiped out my Magisk install. To fix, had to reinstall Magisk from step one.
Magisk wiping bug has been fixed, I'm sincerely sorry for inconvenience brought by this and encourage you to try out version 0.3.
Coolhaus said:
Can confirm, installing this wiped out my Magisk install. To fix, had to reinstall Magisk from step one.
Click to expand...
Click to collapse
How to fix this if I don't have a backup ?
IDAHEX said:
How to fix this if I don't have a backup ?
Click to expand...
Click to collapse
Sorry for the inconvenience, you will have to start all over. Or you could simply disable the module in recovery and Magisk would have been back!
Great module! fixed safteynet not passing on my blackview a20 running treble pie, thanks! been going crazy with this issue
@JayminSuthar When I used magisk hide Basic integrity was working and I disable magisk hide and install this module both CTS Profile and Basic integrity are failing
kullurumanoj said:
@JayminSuthar When I used magisk hide Basic integrity was working and I disable magisk hide and install this module both CTS Profile and Basic integrity are failing
Click to expand...
Click to collapse
Can you provide logcats with both MagiskHide and ShellHide ??
Can't flash this module on my j7 2016 getting error [
Fixed installation
I can not install the modulator as the problem
magisk install log
- Copying zip to temp directory
- Installing sh_hide-1.1-201811071-stable-signed.zip
- Mounting /system, /vendor
Archive: /data/user/0/com.topjohnwu.magisk/cache/install.zip
inflating: common/post-fs-data.sh
inflating: config.sh
inflating: module.prop
*******************************
Please install Magisk v15.0+!
*******************************
Canary builds are unsupported
*******************************
! Installation failed