Related
hello, i got the cifs module to work, but when i try to add the xpad.ko in the terminal it says read only. then when i do insmod it says can not find directory. i placed the xpad.ko where i placed the cifs.ko . the cifs works fine. i have cm7 with pershots 2.6.32.41 kernel. everything is placed in /system/lib/modules/2.6.32.41-cyanogenmod/.... what am i doing wrong ??
It would help if you gave us the exact command you used and the exact error message you got back.
this is what i did. placed xpad.ko in /system/lib/modules/2.6.32.41-cyanogenmod/ , then in terminal chmod 644 /system/lib/modules/2.6.32.41-cyanogenmod/xpad.ko , terminal replys chmod 644 /system/lib/modules/2.6.32.41-cyanogenmod/xpad.ko: Read-only file system ... then in terminal insmod /system/lib/modules/2.6.32.41-cyanogenmod/xpad.ko , reply from terminal, insmod: init_module '/system/lib/modules/2.6.32,41-cyanogenmod/xpad.ko' failed (no such file or directory) ....i followed pershots directions from droid basement. i had no problems installing the cifs module, that works fine.
Save yourself a lot of trouble:
Don't copy the xpad.ko file (or any other kernel module file for that matter) into /system--just leave it on the SD card.
You can also skip the chmod command. Since the insmod command needs to be run as superuser, permissions for the kernel module files don't matter.
All you have to do is specify the correct path to the .ko file when giving the insmod command which you must run as root--loading modules into a running kernel is a privileged operation, and normal users cannot do it.
Assuming your xpad.ko file is in /mnt/sdcard/tmp/, do:
Code:
$ su [I]# become superuser[/I]
# insmod /mnt/sdcard/tmp/xpad.ko
thank you for your help... tried doing it like you wrote , but it keeps telling me no such file or directory . i don't get it , why does it work for the cifs module and not the xpad module ?? if i can set up the cifs correctly, i should be able to do the xpad , it's all the same commands you just add in the module ko. , right? thanks for your time.. tired of messing with trying to get a game pad to work. i give up on this . at least i got the cifs to work..... thanks
The xpad.ko module needs another module to be loaded first, before it can be loaded. Otherwise you get this error:
Code:
$ su
# insmod /mnt/sdcard/tmp/xpad.ko
insmod: can't insert 'xpad.ko': unknown symbol in module or invalid parameter
I ran modinfo (on a Linux machine) on the xpad.ko file and it told me that xpad.ko depends on a ff-memless module. So load that module first (this module is also available in lib-2632.41_gb.tar.gz):
Code:
$ su
# insmod /mnt/sdcard/tmp/ff-memless.ko
# insmod /mnt/sdcard/tmp/xpad.ko
# dmesg | tail -n5
[79594.956918] CPU1 attaching NULL sched-domain.
[79595.074521] CPU0 attaching NULL sched-domain.
[79595.075957] CPU1: clean shutdown
[79608.912964] usbcore: registered new interface driver xpad
[79608.918576] xpad: X-Box pad driver
Looks like the drivers loaded successfully.
thank you, thank you, thank you, that worked....this is a really easy way to load in the modules , so much faster... just have to set up gscript lite now to do the work for me. thank you so much for your time ... thanks
Forgive my ignorance but in Pershoot's kernel would that xpad.ko file have to be compiled for the Android flavor you have? For instance on his blog he has both the Froyo and GB kernels, but I have seen his latest kernel on a few Honeycomb roms. Just wondering because I've tried to load the xpad.ko file in terminal with admin rights on a few and can't get them to work. Again, forgive my ignorance I'm trying to learn. Feel free to smack me about.
sixvoltsystem said:
Just wondering because I've tried to load the xpad.ko file in terminal with admin rights on a few and can't get them to work.
Click to expand...
Click to collapse
Did you load the ff-memless.ko module before loading xpad.ko as per post #6 in this thread?
rajeevvp said:
Did you load the ff-memless.ko module before loading xpad.ko as per post #6 in this thread?
Click to expand...
Click to collapse
Yes sir. Running Flashback Alpha 5.4 Rom. I can't get either one to run. My ff-memless.ko module is located in:
/system/lib/modules/2.6.32.42-cyanogenmod/kernel/drivers/input/ff-memless.ko
My Xpad.ko file is located in:
/system/lib/modules/2.6.32.42-cyanogenmod/kernel/drivers/input/joystick/xpad.ko
I get this:
Permission Denied even though I have "Needs SU" checked in Gscript
Thank you for the help I'm a bit of an idiot so I appreciate the look see
sixvoltsystem said:
I get this:
Permission Denied even though I have "Needs SU" checked in Gscript
Click to expand...
Click to collapse
Send me the output of these commands. Open the Terminal app on the gTablet and then type:
Code:
gTablet$ [B]su[/B]
gTablet# [B]find / -name ff-memless*[/B]
gTablet# [B]find / -name xpad.ko[/B]
EDIT: Just ran these exact commands in the terminal and the modules appear to have loaded just fine on my gTab (I'm running GtabComb beta 3.1):
Code:
gTablet$ [B]su[/B]
gTablet# [B]insmod /system/lib/modules/2.6.32.42-cyanogenmod/kernel/drivers/input/ff-memless.ko[/B]
gTablet# [B]insmod /system/lib/modules/2.6.32.42-cyanogenmod/kernel/drivers/input/joystick/xpad.ko[/B]
gTablet# [B]dmesg | tail -n 5[/B]
[ 1073.826181] CPU1 attaching NULL sched-domain.
[ 1073.942055] CPU0 attaching NULL sched-domain.
[ 1073.945705] CPU1: clean shutdown
[ 1283.649241] usbcore: registered new interface driver xpad
[ 1283.654886] xpad: X-Box pad driver
/system/lib/modules/2.6.32.42-cyanogenmod/kernel/drivers/input/ff-memless.ko
Then if I try running it in terminal it says failed ( File exists )
both the ff-memless.ko & xpad.ko files are located in the same place yours are. Should I format and start over? Odd
By the way much appreciated for the help
sixvoltsystem said:
Then if I try running it in terminal it says failed ( File exists )
Click to expand...
Click to collapse
That means that the modules are already loaded. Check using the dmesg command I gave previously, and also check using lsmod like this:
Code:
gTablet$ [B]su[/B]
gTablet# [B]lsmod[/B]
Module Size Used by Tainted: G
xpad 8315 0
ff_memless 4200 1 xpad
dhd 201288 0
tun 10899 0
nls_utf8 1143 0
ntfs 207149 0
cifs 235684 0
As you can see, both xpad.ko and ff_memless.ko are loaded and xpad.ko is using ff_memless.ko as it should. You should be good to go at this point.
rajeevvp said:
That means that the modules are already loaded. Check using the dmesg command I gave previously, and also check using lsmod like this:
Code:
gTablet$ [B]su[/B]
gTablet# [B]lsmod[/B]
Module Size Used by Tainted: G
xpad 8315 0
ff_memless 4200 1 xpad
dhd 201288 0
tun 10899 0
nls_utf8 1143 0
ntfs 207149 0
cifs 235684 0
As you can see, both xpad.ko and ff_memless.ko are loaded and xpad.ko is using ff_memless.ko as it should. You should be good to go at this point.
Click to expand...
Click to collapse
dmesg command gave this:
nvrm_notifier_show: blocking
CPU0 attaching NULL sched-domain.
CPU1 attaching NULL sched-domain.
CPU0 attaching NULL sched-domain.
CPU1: clean shutdown
lsmod command shows:
xpad 8315 0 - Live 0xbf043000
ff_memless 4200 1 xpad, Live oxbf03c000
dhd 201288 0 - Live 0xbf000000
You sir are awesome for helping me, it works! Wired Xbox 360 controller is working perfectly!! I thanked you in every post here.
sixvoltsystem said:
dmesg command gave this:
nvrm_notifier_show: blocking
CPU0 attaching NULL sched-domain.
CPU1 attaching NULL sched-domain.
CPU0 attaching NULL sched-domain.
CPU1: clean shutdown
Click to expand...
Click to collapse
You were too late with that dmesg command. It should've been executed right after the insmod stuff. Or, just plain dmesg without the tail and then look through its output.
Wired Xbox 360 controller is working perfectly!! I thanked you in every post here.
Click to expand...
Click to collapse
Oh, boy! And I don't even own an Xbox. Of any variety.
Really, you should be thanking the guy(s) who wrote the code.
rajeevvp said:
You were too late with that dmesg command. It should've been executed right after the insmod stuff. Or, just plain dmesg without the tail and then look through its output.
Oh, boy! And I don't even own an Xbox. Of any variety.
Really, you should be thanking the guy(s) who wrote the code.
Click to expand...
Click to collapse
No problem, I will thank them. Thank you for helping me understand it a bit more. You were very helpful and patient. We have an xbox, but it is my son's, I'd rather play some Atari or 8-bit Nintendo....which is what I'll do now that this works
Hello all of you, maybe anyone can help with this...
Im trying to use a generic usb gamepad with the gtab but only work the buttons and not the direction pad. Anyone have any idea? I dont have any wired xbox controller...
Thanks a lot!
first off, a million thank yous to rajeevp and everyone else on this thread. I'm not all that knowledgeable with this stuff but after coming across these posts I was able to install xpad.ko, using terminal emulator that I got of the android market and now I can use the xbox wireless gaming adapter and xbox360 wireless controller on my rooted gtablet. I'm using gtabcomb 3.3 bootloader 1.1 and I play nest, snes, n64, Sega roms and emulators that I got free from 4shared.com,. I was cracking my head trying to get the 360 controller to work with the usb adapter and now it all works. The thank god I found this thread!! You hackers and developers out there are awesome!!!
after the drivers loaded. Whats next
rajeevvp said:
The xpad.ko module needs another module to be loaded first, before it can be loaded. Otherwise you get this error:
Code:
$ su
# insmod /mnt/sdcard/tmp/xpad.ko
insmod: can't insert 'xpad.ko': unknown symbol in module or invalid parameter
I ran modinfo (on a Linux machine) on the xpad.ko file and it told me that xpad.ko depends on a ff-memless module. So load that module first (this module is also available in lib-2632.41_gb.tar.gz):
Code:
$ su
# insmod /mnt/sdcard/tmp/ff-memless.ko
# insmod /mnt/sdcard/tmp/xpad.ko
# dmesg | tail -n5
[79594.956918] CPU1 attaching NULL sched-domain.
[79595.074521] CPU0 attaching NULL sched-domain.
[79595.075957] CPU1: clean shutdown
[79608.912964] usbcore: registered new interface driver xpad
[79608.918576] xpad: X-Box pad driver
Looks like the drivers loaded successfully.
Click to expand...
Click to collapse
So what would the next step be after the ff-memless.ko and xpad.ko drivers have been installed????
--- This is not made by me. This is an repost to XDA. ---
This is 32-bit, so you can use offical TWRP.
Made by hacker12455 and Lukapanio
Bugs:
Camera and minor bugs
Installation:
(Requires ADB + Fastboot, Linux on the PC and Git)
1. Format the data partition with ext4 (Format != Wipe)
2. Download the latest halium-boot.img from https://sourceforge.net/projects/ubports-cedric/files
3. Run
Code:
fastboot flash boot halium-boot.img
4. Download the latest ubports-touch.rootfs-xenial-armhf.tar.gz from https://ci.ubports.com/job/xenial-rootfs-armhf/
5. Download the latest system.img from https://sourceforge.net/projects/ubports-cedric/files
6. Clone https://gitlab.com/JBBgameich/halium-install git repository and go into that folder
7. Run
Code:
./halium-install -v -p ut path/to/ubports-touch.rootfs-xenial-armhf.tar.gz path/to/system.img
8. Reboot your phone.
9. Run
Code:
dmesg -w
and look for an GNU/Linux device.
10. Connect your computer to the RNDIS network that appeared when you rebooted your phone. (If not already happened.)
11. SSH onto the device:
Code:
ssh [email protected]
12. Follow that guide: http://docs.ubports.com/en/latest/porting/running-ut.html
You made it!
Source: https://github.com/ubports-on-cedric
Download: http://ubports-cedric.sf.net
Fail, ignore
Screenshots!
Note: Visual glitch already fixed, old screenshots.
About this device is coming soon.
Nice, i will try it tomorrow
[censored because imei leak, looking for new screenshot]
@nift4 the broken things are fixable?
lucki1000 said:
@nift4 the broken things are fixable?
Click to expand...
Click to collapse
Sound yes
Why authors are redacted?
nift4 said:
Why authors are redacted?
Click to expand...
Click to collapse
Follow the xda rules - telegram is not allowed on xda nor is the promotion of any other social media
XDA is a place for discussion and building of android projects - if everyone went to telegram the forums would be empty
I'd advise you remove all references to telegram
Done
EDIT: I did not want to break the rules I simply did not made it
Ok, I:
- Flashed the boot image from fastboot mode
- Booted into TWRP because the halium-install script tried to use ADB (there's no ADB in fastboot mode!)
- image flashed, i rebooted and the RNDIS appeared with
Code:
sudo dmesg -w
but ssh connection is refused on port 22, and when I connected with telnet the commands from the last guide (had to use the Wayback Machine, since the actual page doesn't exist anymore) but
Code:
/ # cat /var/lib/lxc/android/rootfs/ueventd*.rc|grep ^/dev|sed -e 's/^\/dev\///'|awk '{
printf "ACTION==\"add\", KERNEL==\"%s\", OWNER=\"%s\", GROUP=\"%s\", MODE=\"%s\"\n",$1,
$3,$4,$2}' | sed -e 's/\r//' >/usr/lib/lxc-android-config/70-cedric.rules
cat: can't open '/var/lib/lxc/android/rootfs/ueventd*.rc': No such file or directory
/bin/sh: can't create /usr/lib/lxc-android-config/70-cedric.rules: nonexistent directory
/ #
So, what am I doing wrong? Is there a more recent version?
prove:
I give a zip file.download and extract it.you can find a video watch it as the prove of this post
You can test GSi ROM without any data loss.....
Requirements:
1.Need a laptop with Linux (window also can do...but Linux is batter for CMD line)
2.Unrooted phone.(magisk patch boot not boot gsi for my case try it if it work or not)
3.vbmeta.img(flash it via 'fastboot flash vbmeta vbmeta.img')
3.java installed in your machine...
4.Working brain to solve Errors.:fingers-crossed::fingers-crossed:
Step 1:
Go to the link and download any official gsi arm64-ab version (I can not boot unofficial gsi..Descendant X....any room which it not boot remember you cannot boot it even fastbood method )
https://www.google.com/url?sa=t&sou...FjAAegQIARAB&usg=AOvVaw0IRaTTGUOyl04z17LCE96H
Step 2:
Extract and rename file as 'system.img'...
Step 3:
Now open CMD terminal from where your system.img located and paste this cmd...
simg2img system.img system_raw.img
Error and slove...
You need to install simg2img on Linux...
After install and run this CMD you found error like about header file magic or like something...do not worry... that's mean your system.img file already a raw file and do not need to convert it..just rename this file as 'system_raw.img'
Step 4:
Now open CMD terminal from where your system_raw.img located paste this cmd...
gzip -c system_raw.img > system_raw.gz
Wait for finish..
Step 5:
Now connect your phone with via cable and in developers options turn on usb debugging mood and run this CMA...
adb push system_raw.gz /storage/emulated/0/Download/
Wait for finish........
Step 6:
Now run this CMD..
adb shell setprop persist.sys.fflag.override.settings_dynamic_system true
Step 7:
Now run this CMD...
adb shell am start-activity \
-n com.android.dynsystem/com.android.dynsystem.VerificationActivity \
-a android.os.image.action.START_INSTALL \
-d file:///storage/emulated/0/Download/system_raw.gz \
--el KEY_SYSTEM_SIZE $(du -b system_raw.img|cut -f1) \
--el KEY_USERDATA_SIZE 8589934592
You need to varying your identity by fingerprints or parttern if your device has lock function on...after varify you will notice a notification like this...
Dynamic system update
That's mean you can successfully do my instructions....:cyclops::cyclops:..
Wait for finish....
Now you have two option restart or discard....
Tap restart to go to your gsi or discard to destroy gsi install....
On gsi you can do what you want..
If your work or discover finis then reboot the phone with power button option.
After reboot you are now miui and yes no data lost...
After some moments you can again get two options (Restart or discard)...
This process go untill you discard gsi...
If you stay gsi after reboot then run the CMD....
adb shell gsi_tool enable
Now you can stay gsi after reboot how many time you want...
Disable this feature now type this CMD ...
adb shell gsi_tool disable
If you face some problems....tell me want is your problem......
If you can dual boot your device the thanks is free...
Go throw below link for more information...
https://developer.android.com/topic/dsu
Redmi note 9 merlin doesn't support seamless system update. Is it possible to do this?
Halloul said:
Redmi note 9 merlin doesn't support seamless system update. Is it possible to do this?
Click to expand...
Click to collapse
I think it's better to provide your questions in Redmi note 9 fourms in Xda.
Check it :https://forum.xda-developers.com/redmi-note-9
Halloul said:
Redmi note 9 merlin doesn't support seamless system update. Is it possible to do this?
Click to expand...
Click to collapse
Redmi note 9 supporting dynamic storage if it come with android 10 out of box..if you hava fastboot rom then go to image folder on it and find super.img.
If super.img found that's mean your are good to go...
Or if you find system.img and vendor.img then sorry
1st time its works great
Then i want to check another gsi but not showing in the notification menu
Mantipallykrishna said:
1st time its works great
Then i want to check another gsi but not showing in the notification menu
Click to expand...
Click to collapse
If you use two GSI. That's mean you install a a dynamic GSI over a GSI then the problem will happen. Because all GSI can not capable with it. If you flash dynamic GSI over MIui Rom then the problem not happened.when you in MIui then restart to go dynamic GSI.when you are in dynamic GSI then do not reboot your device just power off and then power on your device to go MIui.then you find the dynamic GSI restart option again.even if you can not find the notification then go to your device recovery option and reboot device from recovery mood.
Even if your problem not solve then you can activate GSI from adb cmd
adb shell gsi_tool enable
Then you can go GSI and when you reboot you can not go back MIui but it is good option to use GSI without data loss.to deactivate just run this adb cmd
adb shell gsi_tool disable
Now reboot and then you can back MIui again..
But remember to check if your dynamic GSI can connect you PC via adb.
This method work for me.I also face the same problem like you.hope you can solve your problem.and remember one thing that if you use magisk patched boot.img then you can not boot your dynamic GSI.I think it is a bug hopefully it will solve soon
the first time worked fine, then i tried the command: adb shell gsi_tool enable, for some reason i wasn't able to connect to gsi with adb to turn it off: adb shell gsi_tool disable
i flashed miui with miflash, but now the installation won't start again
just found out that when a micro sd card ist in the phone, for some reason dsu won't show up, i removed the micro sd card, restarted the phone, and now dsu shows in the notification bar
Shas45558 said:
prove:
I give a zip file.download and extract it.you can find a video watch it as the prove of this post
You can test GSi ROM without any data loss.....
Requirements:
1.Need a laptop with Linux (window also can do...but Linux is batter for CMD line)
2.Unrooted phone.(magisk patch boot not boot gsi for my case try it if it work or not)
3.vbmeta.img(flash it via 'fastboot flash vbmeta vbmeta.img')
3.java installed in your machine...
4.Working brain to solve Errors.:fingers-crossed::fingers-crossed:
Step 1:
Go to the link and download any official gsi arm64-ab version (I can not boot unofficial gsi..Descendant X....any room which it not boot remember you cannot boot it even fastbood method )
https://www.google.com/url?sa=t&source=web&rct=j&url=https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-%28GSI%29-list&ved=2ahUKEwj04pKZwfnrAhVLfXAKHV8FAFcQFjAAegQIARAB&usg=AOvVaw0IRaTTGUOyl04z17LCE96H
Step 2:
Extract and rename file as 'system.img'...
Step 3:
Now open CMD terminal from where your system.img located and paste this cmd...
simg2img system.img system_raw.img
Error and slove...
You need to install simg2img on Linux...
After install and run this CMD you found error like about header file magic or like something...do not worry... that's mean your system.img file already a raw file and do not need to convert it..just rename this file as 'system_raw.img'
Step 4:
Now open CMD terminal from where your system_raw.img located paste this cmd...
gzip -c system_raw.img > system_raw.gz
Wait for finish..
Step 5:
Now connect your phone with via cable and in developers options turn on usb debugging mood and run this CMA...
adb push system_raw.gz /storage/emulated/0/Download/
Wait for finish........
Step 6:
Now run this CMD..
adb shell setprop persist.sys.fflag.override.settings_dynamic_system true
Step 7:
Now run this CMD...
adb shell am start-activity \
-n com.android.dynsystem/com.android.dynsystem.VerificationActivity \
-a android.os.image.action.START_INSTALL \
-d file:///storage/emulated/0/Download/system_raw.gz \
--el KEY_SYSTEM_SIZE $(du -b system_raw.img|cut -f1) \
--el KEY_USERDATA_SIZE 8589934592
You need to varying your identity by fingerprints or parttern if your device has lock function on...after varify you will notice a notification like this...
Dynamic system update
That's mean you can successfully do my instructions....:cyclops::cyclops:..
Wait for finish....
Now you have two option restart or discard....
Tap restart to go to your gsi or discard to destroy gsi install....
On gsi you can do what you want..
If your work or discover finis then reboot the phone with power button option.
After reboot you are now miui and yes no data lost...
After some moments you can again get two options (Restart or discard)...
This process go untill you discard gsi...
If you stay gsi after reboot then run the CMD....
adb shell gsi_tool enable
Now you can stay gsi after reboot how many time you want...
Disable this feature now type this CMD ...
adb shell gsi_tool disable
If you face some problems....tell me want is your problem......
If you can dual boot your device the thanks is free...
Go throw below link for more information...
https://developer.android.com/topic/dsu
Click to expand...
Click to collapse
its give me proble when in start activity at the end.
===========================================================
adb shell am start-activity \
-n com.android.dynsystem/com.android.dynsystem.VerificationActivity \
-a android.os.image.action.START_INSTALL \
-d file:///storage/emulated/0/Download/system_raw.gz \
--el KEY_SYSTEM_SIZE $(du -b system_raw.img|cut -f1) \
--el KEY_USERDATA_SIZE 8589934592
Exception occurred while executing 'start-activity':
java.lang.IllegalArgumentException: No intent supplied
at android.content.Intent.parseCommandArgs(Intent.java:7790)
at com.android.server.am.ActivityManagerShellCommand.makeIntent(ActivityManagerShellCommand.java:341)
at com.android.server.am.ActivityManagerShellCommand.runStartActivity(ActivityManagerShellCommand.java:438)
at com.android.server.am.ActivityManagerShellCommand.onCommand(ActivityManagerShellCommand.java:189)
at android.os.BasicShellCommandHandler.exec(BasicShellCommandHandler.java:98)
at android.os.ShellCommand.exec(ShellCommand.java:44)
at com.android.server.am.ActivityManagerService.onShellCommand(ActivityManagerService.java:11390)
at android.os.Binder.shellCommand(Binder.java:936)
at android.os.Binder.onTransact(Binder.java:820)
at android.app.IActivityManager$Stub.onTransact(IActivityManager.java:5216)
at com.android.server.am.ActivityManagerService.onTransact(ActivityManagerService.java:3162)
at com.android.server.am.OppoActivityManagerService.onTransact(OppoActivityManagerService.java:169)
at android.os.Binder.execTransactInternal(Binder.java:1166)
at android.os.Binder.execTransact(Binder.java:1130)
=========================================================
Here Is the error code. Im on A11. Realme C3. But when Im use Dsu and download and install from dsu it works im confused ??
fire7ly said:
its give me proble when in start activity at the end.
===========================================================
adb shell am start-activity \
-n com.android.dynsystem/com.android.dynsystem.VerificationActivity \
-a android.os.image.action.START_INSTALL \
-d file:///storage/emulated/0/Download/system_raw.gz \
--el KEY_SYSTEM_SIZE $(du -b system_raw.img|cut -f1) \
--el KEY_USERDATA_SIZE 8589934592
Exception occurred while executing 'start-activity':
java.lang.IllegalArgumentException: No intent supplied
at android.content.Intent.parseCommandArgs(Intent.java:7790)
at com.android.server.am.ActivityManagerShellCommand.makeIntent(ActivityManagerShellCommand.java:341)
at com.android.server.am.ActivityManagerShellCommand.runStartActivity(ActivityManagerShellCommand.java:438)
at com.android.server.am.ActivityManagerShellCommand.onCommand(ActivityManagerShellCommand.java:189)
at android.os.BasicShellCommandHandler.exec(BasicShellCommandHandler.java:98)
at android.os.ShellCommand.exec(ShellCommand.java:44)
at com.android.server.am.ActivityManagerService.onShellCommand(ActivityManagerService.java:11390)
at android.os.Binder.shellCommand(Binder.java:936)
at android.os.Binder.onTransact(Binder.java:820)
at android.app.IActivityManager$Stub.onTransact(IActivityManager.java:5216)
at com.android.server.am.ActivityManagerService.onTransact(ActivityManagerService.java:3162)
at com.android.server.am.OppoActivityManagerService.onTransact(OppoActivityManagerService.java:169)
at android.os.Binder.execTransactInternal(Binder.java:1166)
at android.os.Binder.execTransact(Binder.java:1130)
=========================================================
Here Is the error code. Im on A11. Realme C3. But when Im use Dsu and download and install from dsu it works im confused ??
Click to expand...
Click to collapse
Use dsu..it is easy method
Shas45558 said:
Use dsu..it is easy method
Click to expand...
Click to collapse
Yeah You Are Right ! . But Dsu gives Only Aosp Gsis. Which Is not So Great. If Any Ways I use Pixel Gsis it Would Be Great.
fire7ly said:
Yeah You Are Right ! . But Dsu gives Only Aosp Gsis. Which Is not So Great. If Any Ways I use Pixel Gsis it Would Be Great.
Click to expand...
Click to collapse
Hmm...thats is the point...use linux and when you input any cmd you must open cmd pannel from where you kept the rom which you try to installed...
Shas45558 said:
Hmm...thats is the point...use linux and when you input any cmd you must open cmd pannel from where you kept the rom which you try to installed...
Click to expand...
Click to collapse
you mean same directory where gsi present.
fire7ly said:
you mean same directory where gsi present.
Click to expand...
Click to collapse
Yes..
work in poco m3?
how about redmi note 9 pro sir? can you give me a link for the tut?
Hello! After many years without development, today I'm sharing a new kernel with ZRAM and swap support for this device.
The kernel is based upon weritos' Cyanogenmod 13 kernel source code and should work on both rev. 1 and rev. 2 devices.
Installation procedure is as follows:
1. Download the latest TWRP, kernel build and modules.
2. Install the kernel and TWRP from ADB shell (the device must be booted into Android) or a terminal app:
Bash:
su (from a terminal app; not required from ADB shell)
cat </path/to/TWRP_image> > /dev/block/mmcblk0p13
cat </path/to/kernel_image> > /dev/block/mmcblk0p8
reboot recovery
3. Install the kernel modules:
Bash:
mount /dev/block/mmcblk0p21 /system
unzip -o </path/to/modules.zip> -d /system/lib/modules
4. Done! Reboot into Android.
NOTE: The < and > symbols should never be issued within the commands!
Version Information
Status: Beta (Bluetooth, camera recording and screen recording do not work.)
Created: 2021-05-11
Last Updated: 2021-05-12 (Import and enable Ultra KSM driver.)
I still have this device, will this kernel with twrp installed fix the crashing problems in cm 13, thanks for your effort
@Krush206 it's saying can't open zip file on the last step, how to fix??
SerjSX said:
@Krush206 it's saying can't open zip file on the last step, how to fix??
Click to expand...
Click to collapse
fixed it, I was supposed to write:
Code:
unzip -o /sdcard/modules.zip -d /system/lib/modules
instead of:
Code:
unzip -o /storage/emulated/0/modules.zip -d /system/lib/modules
in TWRP terminal.
However, how do I know if it successfully worked?? My phone booted up normally but no sign that shows if it worked 100% or not. @Krush206
not working
Turkish developers said:
I still have this device, will this kernel with twrp installed fix the crashing problems in cm 13, thanks for your effort
Click to expand...
Click to collapse
This is the reason I exported the ZRAM driver to the kernel. However, I have noticed it breaks Wi-Fi, so I will have to fix it for proper testing.
SerjSX said:
However, how do I know if it successfully worked?? My phone booted up normally but no sign that shows if it worked 100% or not.
Click to expand...
Click to collapse
Either install Termux (or a terminal app of your choice) or use ADB and issue the free -m command.
Krush206 said:
This is the reason I exported the ZRAM driver to the kernel. However, I have noticed it breaks Wi-Fi, so I will have to fix it for proper testing.
Either install Termux (or a terminal app of your choice) or use ADB and issue the free -m command.
Click to expand...
Click to collapse
Hi, thanks for your response. Just did i and looks like it worked, 59 total swap, used 58, and free 541.
Are you sure you checked the correct line? The total should be 255 (256), not 59.
can you compile a kernel for overclocking in stock room or cm 11 please our quttro needs it now
overclock kernel pls
Sorry for the delay. The battery of my device has swollen, so I cannot really check whether overclocking is possible or not.
However, though overclocking may be possible, it may cause system instability and crashes.
I could probably have a look at the code and see how to get it done, but I cannot post results and would not recommend overclocking.
The battery in my device was swollen, I found a battery and the best software for this device is 4.1.2. I want to try overclocking for this version. Bide 4.1.2 also does not play hd videos in the original software. Is there a code or a mod for this?
1.5 Ghz overclock pls
any update?
If you two, @Fever070720, @Turkish developers, are still looking into overclocking, please, send the output of the following command:
Code:
cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq
Hello!
My Nord 2 will be plugged in 24/7 because I use it for E2E testing. I need to optimize battery so it wont swell up.
Is there any working solutions for doing it? Or is there a way to put battery charging to idle so main power will be drawn from usb.
I tried Magisk ACC plugin, but it seems it is not running. Shell has supperuser power on magisk
ADB shell:
"acc
/system/bin/sh: <stdin>[2]: acc: inaccessible or not found
accd,
/system/bin/sh: <stdin>[3]: accd,: inaccessible or not found"
Also same error in ACC app, magisk have given supperuser access for that app:
"/system/bin/sh: <stdin>[3544]: acc: inaccessible or not found"
when i execut acc.sh in /data/adb/vr25/acc/ folder then i cant get ACCD running there. Well it runs for a minut then turns off
"
Advanced Charging Controller v2021.8.31 (202108310)
Copyright 2017-2021, VR25
GPLv3+
(i) accd is not running
1) Language
2) All commands
3) Documentation
4) Start/restart daemon
5) Stop daemon
6) Export logs
7) Charge once to #%
8) Uninstall
9) Edit config.txt
a) Reset battery stats
b) Test charging switches
c) Check for update
d) Flash zips
e) Battery info
f) Exit
#? b
(!) Charger must be plugged to continue...
(i) Alright, this may take a minute or so...
(!) [/proc/mtk_battery_cmd/current_cmd 0::0 0::1 /proc/mtk_battery_cmd/en_power_path 1 0] won't work
(i) Press any key to continue..."
Hi, I'm the developer of acc.
Have you tried a slow charger or USB charging?
Refer to README > Troubleshooting.
This is a kernel/adapter issue.
Edit
Just noticed that you're not using the latest acc release.
Since you're facing issues, upgrading is a must.
Regardless, don't skip the documentation.
I am using PC USB connection for charging. Should ACC daemon allways run? It works for a minute and then stop. Do you mean oneplus nord 2 battery charging management have same kernel issue as you mentioned in ACC thread?
I have tested different versions to be sure. v2021.8.31 came from Magisk for first.
AccA is latest 1.0.35 Daemon/API 202109200
New ver.:
Advanced Charging Controller v2021.9.20 (202109200)
Copyright 2017-2021, VR25
GPLv3+
(i) accd is not running (PID 12046)
1) Language
2) All commands
3) Documentation
4) Start/restart daemon
5) Stop daemon
6) Export logs
7) Charge once to #%
8) Uninstall
9) Edit config.txt
a) Reset battery stats
b) Test charging switches
c) Check for update
d) Flash zips
e) Battery info
f) Undo upgrade
g) Exit
#? b
(!) Charger must be plugged to continue...
(i) Alright, this may take a minute or so...
(!) [/proc/mtk_battery_cmd/current_cmd 0::0 0::1 /proc/mtk_battery_cmd/en_power_path 1 0] won't work
This is usually a kernel and/or power adapter issue.
The daemon should be running to control charging.
The #1 reason for it to stop is total charging switch failure.
That is, all charging switches fail to respond.
In that case, it finds no reason to keep running.
Share a log archive (acc -le) and the output of acc -p.
Where can i get those logs? From /data/adb/vr25/acc-data/logs/ ? Might it be acc-logs-OP515BL1.tar.gz file?
Somehow "pull" and "cp" are not working on me with adb shell. Is there any better tools for pulling files and logs? There is many tools witch are not working with my phones and cant find root folders, google is to big.
@VR25 Hi! I attached all logs from ACC-data logs folder. Will it help?
CapnRene said:
@VR25 Hi! I attached all logs from ACC-data logs folder. Will it help?
Click to expand...
Click to collapse
Perfect!
I found potential charging switches.
Test the following commands one by one and report the ones that work:
su -c acc -t /sys/devices/virtual/oplus_chg/battery/mmi_charging_enable 1 0
su -c acc -t /sys/devices/platform/charger/enable_sc 0 1
su -c acc -t /sys/devices/platform/charger/enable_sc 1 0
su -c acc -t /sys/devices/virtual/oplus_chg/battery/stop_charging_enable 0 1
su -c acc -t /sys/firmware/devicetree/base/charger/usb_charger_current_suspend 0 1
Note
One/some of the commands may trigger a reboot.
That's not a big deal. Just move to the next on the list.
First line got response:
OP515BL1:/ # su -c acc -t /sys/devices/virtual/oplus_chg/battery/mmi_charging_enable 1 0
(!) Charger must be plugged to continue...
(i) Alright, this may take a minute or so...
(i) [/sys/devices/virtual/oplus_chg/battery/mmi_charging_enable 1 0] works
- battIdleMode=true
As i understand i need to change switch now to get it working?
su -c acc -s s="/sys/devices/virtual/oplus_chg/battery/mmi_charging_enable 1 0"
You should be all set after running that.
The next release will include the new switch.
Edit
Since the device will be plugged in 24/7, you may want to run `acc 3920` to set it up.
Essentially, this will keep the battery voltage between 3870-3920 millivolts.
3920 is said to be the sweet spot for longevity.
Not 100% sure did it work, need to test it a litte to be sure. It seems it updated log
OP515BL1:/ # su -c acc -s s="/sys/devices/virtual/oplus_chg/battery/mmi_charging_enable 1 0"
/system/bin/acc[580]: export: 1: is not an identifier
(i) Alright, this may take a minute or so...
(i) /data/adb/vr25/acc-data/logs/acc-logs-OP515BL1.tar.gz
My bad
It should have been
su
acc -s s="/sys/devices/virtual/oplus_chg/battery/mmi_charging_enable 1 0"
VR25 said:
My bad
It should have been
su
acc -s s="/sys/devices/virtual/oplus_chg/battery/mmi_charging_enable 1 0"
Click to expand...
Click to collapse
It worked! Ty! I set my swich to turn on 59% and off 60% for optimal ressult.
It seems that those are not working or maybe i have made some mistake somewhere:
shutdown capacity
charge current
charge voltage
CapnRene said:
It worked! Ty! I set my swich to turn on 59% and off 60% for optimal ressult.
It seems that those are not working or maybe i have made some mistake somewhere:
shutdown capacity
charge current
charge voltage
Click to expand...
Click to collapse
From the documentation:
# shutdown_capacity (sc) #
# When the battery is discharging and its capacity/voltage_now_millivolts <= sc and phone has been running for 15 minutes or more, acc daemon turns the phone off to reduce the discharge rate and protect the battery from potential damage induced by voltage below the operating range.
# sc=-1 disables it.
# [Beta] if the file /data/adb/vr25/acc-data/warn exists, accd posts Android shutdown warning notifications at sc + 5% or sc + 200 mV.
The last two features are not supported by all devices.
I'm yet to see a MediaTek device that supports at least one of the those.
Please ask further questions in the actual forum, so that other users can help you whenever I'm unavailable.