It is currently Thu Oct 19, 2017 9:57 pm Advanced search

Android 4.3 compatibility

here report bugs for TouchControl/PGM

Android 4.3 compatibility

Postby gafanhotz » Wed Jul 24, 2013 11:52 pm

Hello there, any plans to update the mod to be compatible with the new JB 4.3 kernel?

I still can't get any logs yet because i'm setting up my system, but I'd like just to inform that the mod isn't working. And if any users depends on it like me that have an broken power button, don't update to 4.3.
User avatar
gafanhotz
 
Posts: 10
Joined: Wed May 22, 2013 5:31 am
Location: Brazil


Re: Android 4.3 compatibility

Postby ponury » Thu Jul 25, 2013 7:24 am

I will compile kernel for 4.3 because the stock one doesn't have modules enabled.
User avatar
ponury
 
Posts: 1199
Joined: Fri Sep 23, 2011 11:19 pm
Location: Poland

Re: Android 4.3 compatibility

Postby gafanhotz » Thu Jul 25, 2013 9:35 am

Yep, thanks for the info. I was reading about that change in the android code, especifically just a commit that makes module loading impossible. Also in a few days Franco, Faux and a few others will update their kernels too. Hope to see your awesome work soon. It's the only thing that stopped me from using 4.3 and reverting back to 4.2.

And again, thanks.
User avatar
gafanhotz
 
Posts: 10
Joined: Wed May 22, 2013 5:31 am
Location: Brazil

Re: Android 4.3 compatibility

Postby gafanhotz » Thu Jul 25, 2013 3:29 pm

@ponury, take a look at your thread at the XDA Galaxy Nexus' forum, an user discovered the trouble with the 4.3 compatibility, the modules works fine on Stock (of course, he re-compiled it with the module loading activated), Faux and Franco's kernel, the problem is with the PGM app that isn't liking the new SuperSU. If you uninstall SuperSU but keep the SU binary, PGM works flawlessly.
User avatar
gafanhotz
 
Posts: 10
Joined: Wed May 22, 2013 5:31 am
Location: Brazil

Re: Android 4.3 compatibility

Postby ponury » Fri Jul 26, 2013 2:44 pm

gafanhotz wrote:@ponury, take a look at your thread at the XDA Galaxy Nexus' forum, an user discovered the trouble with the 4.3 compatibility, the modules works fine on Stock (of course, he re-compiled it with the module loading activated), Faux and Franco's kernel, the problem is with the PGM app that isn't liking the new SuperSU. If you uninstall SuperSU but keep the SU binary, PGM works flawlessly.


Actually it's not PGM problem. Same thing happened to me with bunch other root apps (busybox for example). I think something is wrong with supersu. I needed to flash supersu with TWRP and fix permissions in order for it to work.
User avatar
ponury
 
Posts: 1199
Joined: Fri Sep 23, 2011 11:19 pm
Location: Poland

Re: Android 4.3 compatibility

Postby gafanhotz » Fri Jul 26, 2013 5:14 pm

Well, the apps doesn't like each other. And apparently, activating the option "trust system user" on SuperSU, makes the PGM app able to load the modules properly for the first time, but I'm not sure.

Also, later we discovered that after you do the trick I said, and reinstalling SuperSU from play store, PGM still works even after reboots.

I hope all that info can help you in some way. :)
User avatar
gafanhotz
 
Posts: 10
Joined: Wed May 22, 2013 5:31 am
Location: Brazil

Re: Android 4.3 compatibility

Postby daryelv » Fri Jul 26, 2013 7:38 pm

This is from another forum I posted in regarding my Galaxy Nexus (4.3). A developer has compiled in PGM support to his kernel. Scrolling to the bottom it looks like it may be a signature issue...
.
.
. http://forum.xda-developers.com/showpost.php?p=43982450&postcount=2963
.

Still no-go on the modules loading. I see the toast that says PGM has been granted SuperUser Permissions for an interactive shell, but no gestures show up. There's something else causing the problem.. here's a portion of the logcat...

Code: Select all
I/ActivityManager(  392): Start proc net.ponury.pgm2 for activity net.ponury.pgm2/.PGM2: pid=6266 uid=10092 gids={50092, 1028}^M
D/paranoid.me_PGM2( 6266): [initialize:343] key=[kernel_version] value=[3.0.72.12-stable]^M
D/paranoid.me_PGM2( 6266): [add_gestures:225] Adding gestures, try #-1^M
D/dalvikvm( 6266): GC_CONCURRENT freed 136K, 2% free 9135K/9296K, paused 4ms+1ms, total 22ms^M
D/libEGL  ( 6266): loaded /vendor/lib/egl/libEGL_POWERVR_SGX540_120.so^M
D/libEGL  ( 6266): loaded /vendor/lib/egl/libGLESv1_CM_POWERVR_SGX540_120.so^M
D/libEGL  ( 6266): loaded /vendor/lib/egl/libGLESv2_POWERVR_SGX540_120.so^M
D/OpenGLRenderer( 6266): Enabling debug mode 0^M
D/paranoid.me_PGM2( 6266): [onCreateOptionsMenu:98] ^M
V/RenderScript( 6266): 0x57ca2bf0 Launching thread(s), CPUs 2^M
D/paranoid.me_PGM2$6( 6266): [onCheckedChanged:296] enabled = true^M
D/paranoid.me_PGMModule( 6266): [insmod:68] Insmodding module^M
D/dalvikvm( 6266): Trying to load lib /mnt/asec/net.ponury.pgm2-1/lib/libJNIExec.so 0x42343a28^M
D/dalvikvm( 6266): Added shared lib /mnt/asec/net.ponury.pgm2-1/lib/libJNIExec.so 0x42343a28^M
D/dalvikvm( 6266): No JNI_OnLoad found in /mnt/asec/net.ponury.pgm2-1/lib/libJNIExec.so 0x42343a28, skipping init^M
D/JNIExec ( 6266): exec_cmd: (insmod /data/data/net.ponury.pgm2/files/ponury.ko) start^M
D/JNIExec ( 6266): exec_cmd: [__RET__=255]^M
D/JNIExec ( 6266): exec_cmd: [RET=255]^M
D/paranoid.me_PGMModule( 6266): [insmod:73] Module loaded successfully^M
D/paranoid.me_PGM2( 6266): [load_module:357] Previously created module insmodded fine :)^M
D/paranoid.me_PGM2( 6266): [start_finish:446] Trying to enable the module^M
D/paranoid.me_PGM2( 6266): [start_finish:449] Module status file still not exists... try=9^M
D/paranoid.me_PGM2( 6266): [start_finish:449] Module status file still not exists... try=8^M
D/paranoid.me_PGM2( 6266): [start_finish:449] Module status file still not exists... try=7^M
D/paranoid.me_PGM2( 6266): [start_finish:449] Module status file still not exists... try=6^M
D/dalvikvm( 6266): GC_CONCURRENT freed 277K, 4% free 9252K/9556K, paused 8ms+2ms, total 32ms^M
D/paranoid.me_PGM2( 6266): [start_finish:449] Module status file still not exists... try=5^M
D/paranoid.me_PGM2( 6266): [start_finish:449] Module status file still not exists... try=4^M
D/paranoid.me_PGM2( 6266): [start_finish:449] Module status file still not exists... try=3^M
D/paranoid.me_PGM2( 6266): [start_finish:449] Module status file still not exists... try=2^M
D/paranoid.me_PGM2( 6266): [start_finish:449] Module status file still not exists... try=1^M
D/paranoid.me_PGM2( 6266): [start_finish:449] Module status file still not exists... try=0^M
W/System.err( 6266): java.io.FileNotFoundException: /proc/ponury/status: open failed: ENOENT (No such file or directory)^M
W/System.err( 6266):    at libcore.io.IoBridge.open(IoBridge.java:409)^M
W/System.err( 6266):    at java.io.FileOutputStream.<init>(FileOutputStream.java:88)^M
W/System.err( 6266):    at java.io.FileOutputStream.<init>(FileOutputStream.java:73)^M


Looks like a problem loading the module using insmod (exit code 255). Running directly...
Code: Select all
root@maguro:/proc # insmod /data/data/net.ponury.pgm2/files/ponury.ko         
insmod: init_module '/data/data/net.ponury.pgm2/files/ponury.ko' failed (Exec format error)


Here's what dmesg complains about...
Code: Select all
<3>[ 3407.182373] ponury_gm: version magic '3.0.72.12-stable SMP preempt mod_unload modversions ARMv7 ' should be '3.0.72.12-stable SMP preempt mod_unload ARMv7


This may be an issue to talk to the PGM developer about, unless you know why the insmod is failing.

-Daryel

[[ FIXED ]] - The problem was a SuperSU issue.
daryelv
 
Posts: 1
Joined: Fri Jul 26, 2013 7:36 pm

Re: Android 4.3 compatibility

Postby gafanhotz » Sat Jul 27, 2013 3:27 pm

Well, if you proceed doing this:

Go to SuperSU and select the option where it says "clean for re-install from play store" (not remove root completely!) and after that you activate PGM, it works very well, and after it you can easily reinstall SuperSU and PGM keeps working. It seems to be a SuperSU issue, but @bponury maybe just have to adapt the PGM app to work with it.

It just resumes to: Removing SuperSU and keeping the SU binary.
User avatar
gafanhotz
 
Posts: 10
Joined: Wed May 22, 2013 5:31 am
Location: Brazil

Re: Android 4.3 compatibility

Postby WizardBGR » Sat Jul 27, 2013 10:14 pm

Not working... SGN takju 4.3 stock, did all in previous post - no success :( Dev, pls fix this... :(
WizardBGR
 
Posts: 1
Joined: Sat Jul 27, 2013 10:08 pm

Re: Android 4.3 compatibility

Postby av8trdude » Wed Jul 31, 2013 2:48 pm

Updated to new SuperSU 1.51 and modules don't load, fail every time. Running stock 4.3. Originally had problem that modules load fine but no gestures appear (described above). Cleaned up SuperSU and reinstalled via Play Store, loaded binaries in recovery CWM, booted and granted root to PGM. From that point forward, modules fail each time. I'm a paid user as well.
av8trdude
 
Posts: 1
Joined: Wed Jul 31, 2013 2:36 pm

Next

Return to Bug reports



Who is online

Users browsing this forum: DarleuWag and 1 guest