[ROM][WIP/Experimental][AOSP][4.3.1] Google Edition for SGS4A (int'l) v0.8 - Galaxy S 4 Active Original Android Development

What?
work in progress build of AOSP, using LeJay's CM kernel sources and device files, modified to play ball with AOSP
some stuff copied from CM, to make build happen (bionic, assorted libs and stuff in external and system)
build makefiles modified, using CM files where possible
some small code modifications
for I9295 international only
stuff is broken, for how long i do not know. I'm still learning this stuff
DISCLAIMER: You take responsibility of your phone and what you flash into it, not me. You are warned
How?
grab the file: https://drive.google.com/folderview?id=0BzJzDM42pkRvcUVyZDRVSERzdlk&usp=sharing
if coming from another rom: factory reset + system format
upgrading previous version shouldn't need factory reset or system format
flash in CWM (yes, CWM or similar needed)
flash gapps
report bugs if new one found
help with development if possible
Credits
Google for Android (and Google search, boy this wouldn't have happened without it )
CyanogenMod for stuff i'm using to make this happen
SlimRom guys
LeJay for jactivelte kernel sources and other stuff
ohwarumbloss for testing CM builds and donations
Chainfire for root
other donators and testers
Changes v0.8
Video preview fixed
sub-1080p video recording fixed
Audio volume settings copied from SlimRom jf-common, more volume
Changes v0.7.1
Only kernel changes
Newer Broadcom wireless drivers from S4 CM 10.2 kernel
EXT4 and JBD2 drivers from S4 CM 10.2 kernel
MSM-8960 related stuff from S4 CM 10.2 kernel
Assorted stuff from S4 CM 10.2 kernel, check the commits in https://github.com/spegelius/android_kernel_samsung_jactivelte if interested (and if something seems wrong, please tell me
Changes v0.7
dualboot version available
network location working
backup to google account working. For those flashing cleanly, the setting should be on. For those dirtyflashing, you need to check this out: http://jftr.de/2014/01/fairphone-and-android-backups-to-the-google-cloud/
Changes v0.6
dualboot version available
some merges from S4 kernel, no changes in functionality
cwm update script doesn't format system anymore
libbt-vendor natively built instead copy from CM build. No change in functionality
Changes v0.5
Sdcard should now work (FAT32 at least, report exfat)
Sports Tracker doesn't crash UI when 'network' location provider isn't found
Changes v0.3 & 0.4
[*]Receiving calls fixed
Hanging up the call fixed
NFC doesn't crash on the background anymore, cannot test though
Bluetooth fixed, using lib from CM build
Changes v0.2
WiFi dhcp fixed
SuperSu included
init.d support
bash included
Bluetooth updates, but no full fix yet
Bugs v0.8
Whoa, are there any?
Bugs v0.7.1
Camera: 720p recording produces crappy videos
Camera: during video recording the preview is very low resolution
Bugs v0.6
Some problems with locations, network locaion isn't really enabled
Camera: 720p recording produces crappy videos
Camera: during video recording the preview is very low resolution
Backup account set to debug-only private cache for some users
Bugs v0.5
Some problems with locations
Camera: 720p recording produces crappy videos
Camera: during video recording the preview is very low resolution
Fixed Bugs
Sdcard doesn't mount
Cannot receive calls
Cannot hang up a call
WiFi connects, but doesn't get IP address
Bluetooth service fails at start, bluetooth doesn't work
NFC seems to be crashing on the background
no root as of yet
Source code
https://github.com/spegelius
Will be updating manifests and other stuff there when i figure a good way to get my changes there.
Oh and mods, if this fits the regular development section better, feel free to move it

A little incentive. Confirmation number: 1D974208B4414071D
I'll test and report. I'm on the GDE 4.2.2 port from Darkman now.

Downloading
Thank you very much for your efforts Mate!
Going to install this and report back soon!
Sent from my GT-I9295 using xda app-developers app
Edit1
Ok, here I come.
- Installation worked fine
- Bluetooth crashed on start as mentioned
- Mobile Data works (at least Edge, thats what I have here)
- WiFi get stuck in "Authenfication" when using standard settings
- WiFi connects when using "static IP" in advanced settings
- been to lazy to config Router for nonDHCP but I think it should work
- All SU Files (chainfire) I tried didn´t work (google search, no success, yet)
- No external SD, but that´s normal in AOSP I think (need 3rd Party app for this)
So, I started to compare this build with CM (cm-10.2-20131227-UNOFFICIAL-jactiveltexx) and there are several Files missing but there are so many..
@spegelius, if only I knew which ones are candidates for Problems...
Edit 2:
These Files may be interesting/important (Don´t laugh if this is totally wrong)
Missing Files in AOSP Build :
Code:
/system/app
- BluetoothExt.apk
Code:
/system/lib
- libbluedroid.so
- libcurve25519.so
- libimscamera_jni.so
- libjackpal-androidterm4.so
- liblzo.so
- libncurses.so
- libpci.so
- libssh.so
- libvt_jni.so
Code:
/system/lib/hw :
- nfc_nci.msm8960.so
- power.msm8960.so
Code:
/system/xbin
- bash
- htop
- Isof
- nano
- openvpn
- powertop
- rsync
- vim
There is no /system/etc/init.d (may be the/a problem of SU as there is also no "50selinuxrelabel" script)
There is no /system/etc/ssh (may be familar to the WiFi as it contains a script "sshd_config", inside this there is a lot of IP-Forwarding bla bla.. but all with a "#" in front)
I hope that helped a little or at all...I don´t have time for more investigations/testing for the rest of today, sorry..
Greetings
Thomas

ohwarumbloss said:
Downloading
Thank you very much for your efforts Mate!
Going to install this and report back soon!
Sent from my GT-I9295 using xda app-developers app
Edit1
Ok, here I come.
- Installation worked fine
- Bluetooth crashed on start as mentioned
- Mobile Data works (at least Edge, thats what I have here)
- WiFi get stuck in "Authenfication" when using standard settings
- WiFi connects when using "static IP" in advanced settings
- been to lazy to config Router for nonDHCP but I think it should work
- All SU Files (chainfire) I tried didn´t work (google search, no success, yet)
- No external SD, but that´s normal in AOSP I think (need 3rd Party app for this)
So, I started to compare this build with CM (cm-10.2-20131227-UNOFFICIAL-jactiveltexx) and there are several Files missing but there are so many..
@spegelius, if only I knew which ones are candidates for Problems...
Edit 2:
These Files may be interesting/important (Don´t laugh if this is totally wrong)
Missing Files in AOSP Build :
Code:
/system/app
- BluetoothExt.apk
Code:
/system/lib
- libbluedroid.so
- libcurve25519.so
- libimscamera_jni.so
- libjackpal-androidterm4.so
- liblzo.so
- libncurses.so
- libpci.so
- libssh.so
- libvt_jni.so
Code:
/system/lib/hw :
- nfc_nci.msm8960.so
- power.msm8960.so
Code:
/system/xbin
- bash
- htop
- Isof
- nano
- openvpn
- powertop
- rsync
- vim
There is no /system/etc/init.d (may be the/a problem of SU as there is also no "50selinuxrelabel" script)
There is no /system/etc/ssh (may be familar to the WiFi as it contains a script "sshd_config", inside this there is a lot of IP-Forwarding bla bla.. but all with a "#" in front)
I hope that helped a little or at all...I don´t have time for more investigations/testing for the rest of today, sorry..
Greetings
Thomas
Click to expand...
Click to collapse
Thanks for digging this stuff out. Some of those might be needed, i'l be adding them from CM repos one by one and testing how it works. I did another build, now adding Superuser to makefiles but still no go. Superuser does pop up after boot, telling su binary neds updating... Also added some init.rc scripts which are in CM build, but still no luck. After some digging, it seems that with 4.3, Google has made rooting bit more difficult. Root is my nr. 1 prio now, i'll need it to restore Titanium backups...
I've been using the rom few days now and it seems to work very well all in all. I had a camera hang yesterday, and after killing camera app it said Cannot connect to camera. Could get a logcat...

Yes, root is a problem, indeed..
Tried 3 hours yesterday in the evening, pushing all kind of different Versions and ended up with the binary update..
Also searched in CM Rom but it seems to be somewhere I can't find it, that little devil
ADB is working fine, also the shell with full root access, pushing and deleting Files, chown, all good. But no luck with the Superuser.apk.
Ended in frustration and restoring Stock..
Now, I hope you're getting it, somehow!
Did you get DHCP running somehow?
There are 3 PC and 4 Smartphones here using Wlan and I'm not really up to set them all up to static IP
Greetings
Thomas
Sent from my GT-I9295 using xda app-developers app

ohwarumbloss said:
Yes, root is a problem, indeed..
Tried 3 hours yesterday in the evening, pushing all kind of different Versions and ended up with the binary update..
Also searched in CM Rom but it seems to be somewhere I can't find it, that little devil
ADB is working fine, also the shell with full root access, pushing and deleting Files, chown, all good. But no luck with the Superuser.apk.
Ended in frustration and restoring Stock..
Now, I hope you're getting it, somehow!
Did you get DHCP running somehow?
There are 3 PC and 4 Smartphones here using Wlan and I'm not really up to set them all up to static IP
Greetings
Thomas
Sent from my GT-I9295 using xda app-developers app
Click to expand...
Click to collapse
Well i have the Superuser app as embedded in the rom and when starting TB, logcat shows that su binary tries to start, but fails with error:
D/su ( 2213): su invoked.
D/su ( 2214): starting daemon client 10062 10062
E/su ( 2215): connect failed with 2: No such file or directory
E/o.gZ ( 1909): Root shell has terminated unexpectedly.
Did a search of the error and it seems that it's related to root setting in developer options. The problem is, there's no setting for root in there. Gonna have to do some diffing between CM and AOSP settings.
Haven't looked into the dhcp yet.

To get root working:
install SuperSu: http://forum.xda-developers.com/showthread.php?t=1538053
Run in adb shell:
Code:
mount -o remount,rw /system
echo persist.sys.root_access=1 >> /system/build.prop
reboot
I'm trying to get supersu integrated, but latest from github doesn't like to play ball. Maybe i'll just use the above release and integrate it... Koush's Superuser doesn't display the dialog for root access when using CM's version and latest from github didn't find some symbols.
Edit: use value 3 if you want to give root access to apps and adb

Ok, some progress, even though i even lost root for a while. Damn i was losing my mind over it, but the it turned out to be a matter of su daemon not starting during boot. Added init.d support and proper init script for the daemon.
- wifi dhcp should work now. It was a matter of file permissions in /system/etc/dhcpd, run-hooks could not be executed. Noticed this when running dhcpd on adb shell. The cmw install script simply didn't set the perms...
- included SuperSu to rom, root should work out of the box
Bluetooth is still buggy; it doesn't fc on boot, but now it fails after a little while, this time the problem is that there's no /dev/ttyO1 for some reason and bt libs cannot connect to it.
Ver 0.2 is uploading, test away

spegelius said:
Ok, some progress, even though i even lost root for a while. Damn i was losing my mind over it, but the it turned out to be a matter of su daemon not starting during boot. Added init.d support and proper init script for the daemon.
- wifi dhcp should work now. It was a matter of file permissions in /system/etc/dhcpd, run-hooks could not be executed. Noticed this when running dhcpd on adb shell. The cmw install script simply didn't set the perms...
- included SuperSu to rom, root should work out of the box
Bluetooth is still buggy; it doesn't fc on boot, but now it fails after a little while, this time the problem is that there's no /dev/ttyO1 for some reason and bt libs cannot connect to it.
Ver 0.2 is uploading, test away
Click to expand...
Click to collapse
nice to here this , for bt issue are the ttyO1 file in ramdisk of boot.img?

mythi said:
nice to here this , for bt issue are the ttyO1 file in ramdisk of boot.img?
Click to expand...
Click to collapse
Hmm, haven't checked. I'll check that after work. I assume the vendor module is built properly as qcom's libs define ttyO1 and libbt_vendor.so exists. But shouldn't the ttyO1 ceated if the module is built?

spegelius said:
Hmm, haven't checked. I'll check that after work. I assume the vendor module is built properly as qcom's libs define ttyO1 and libbt_vendor.so exists. But shouldn't the ttyO1 ceated if the module is built?
Click to expand...
Click to collapse
Hmm... maybe tty01 is a qcom propriety so it couldnt be created without pulling it from a working device and place it in dev folder of ramdisk , I thought like this because the kernel extracts ramdisk files and folders in the "/" folder ..

mythi said:
Hmm... maybe tty01 is a qcom propriety so it couldnt be created without pulling it from a working device and place it in dev folder of ramdisk , I thought like this because the kernel extracts ramdisk files and folders in the "/" folder ..
Click to expand...
Click to collapse
Ok, could be. Don't know how ramdisk is created during build, have to look into it.
Also, found a quite major bug: cannot receive phone calls, at least i can't. That's kinda big problem, considering this is a phone still

Use dsixda kitchen to exreact the boot.img and view/edit its contents

mythi said:
Use dsixda kitchen to exreact the boot.img and view/edit its contents
Click to expand...
Click to collapse
Extracted boot.img, contents:
Code:
./zImage
./ramdisk
./ramdisk/init.trace.rc
./ramdisk/init.qcom.rc
./ramdisk/init.qcom.usb.sh
./ramdisk/system
./ramdisk/init.qcom.lpm_boot.sh
./ramdisk/sepolicy
./ramdisk/file_contexts
./ramdisk/seapp_contexts
./ramdisk/sbin
./ramdisk/sbin/ueventd
./ramdisk/sbin/adbd
./ramdisk/sbin/watchdogd
./ramdisk/init.cm.rc
./ramdisk/init.recovery.qcom.rc
./ramdisk/default.prop
./ramdisk/dev
./ramdisk/res
./ramdisk/res/images
./ramdisk/res/images/charger
./ramdisk/res/images/charger/battery_charge.png
./ramdisk/res/images/charger/battery_0.png
./ramdisk/res/images/charger/battery_fail.png
./ramdisk/res/images/charger/battery_5.png
./ramdisk/res/images/charger/battery_3.png
./ramdisk/res/images/charger/battery_4.png
./ramdisk/res/images/charger/battery_1.png
./ramdisk/res/images/charger/battery_2.png
./ramdisk/init.qcom.syspart_fixup.sh
./ramdisk/ueventd.qcom.rc
./ramdisk/charger
./ramdisk/sys
./ramdisk/init.qcom.class_main.sh
./ramdisk/init.usb.rc
./ramdisk/init.qcom.sh
./ramdisk/init.carrier.rc
./ramdisk/init.qcom.early_boot.sh
./ramdisk/ueventd.rc
./ramdisk/init.target.rc
./ramdisk/init.rc
./ramdisk/data
./ramdisk/init.qcom.class_core.sh
./ramdisk/init.qcom.usb.rc
./ramdisk/proc
./ramdisk/lpm.rc
./ramdisk/init
./ramdisk/property_contexts
./ramdisk/fstab.qcom
./ramdisk.cpio.gz
Nothing in /dev. Apparently those files are created by kernel/something else?
I'm feeling out of ideas currently, don't know where to start looking... i mean everything compiles ok, no errors. Logcat says:
Code:
I/bt_userial_vendor( 1515): userial vendor open: opening /dev/ttyO1
E/bt_userial_vendor( 1515): userial vendor open: unable to open /dev/ttyO1
E/bt_userial( 1515): userial_open: wrong numbers of open fd in vendor lib [0]!
E/bt_userial( 1515): userial_open: HCI UART expects only one open fd
From what i looked at bluedroid code, the tty opening should happen in vendor bt lib... meh. Same libs work with CM, i'm already using system/bluetooth and external/bluetooth from CM, along with qcom libs of course.
And about the phone, i can't seem to get apns to show, even though i copied proper apns list from CM. Even did a factory reset just to eliminate possibility about bad datas etc.

spegelius said:
Extracted boot.img, contents:
Code:
./zImage
./ramdisk
./ramdisk/init.trace.rc
./ramdisk/init.qcom.rc
./ramdisk/init.qcom.usb.sh
./ramdisk/system
./ramdisk/init.qcom.lpm_boot.sh
./ramdisk/sepolicy
./ramdisk/file_contexts
./ramdisk/seapp_contexts
./ramdisk/sbin
./ramdisk/sbin/ueventd
./ramdisk/sbin/adbd
./ramdisk/sbin/watchdogd
./ramdisk/init.cm.rc
./ramdisk/init.recovery.qcom.rc
./ramdisk/default.prop
./ramdisk/dev
./ramdisk/res
./ramdisk/res/images
./ramdisk/res/images/charger
./ramdisk/res/images/charger/battery_charge.png
./ramdisk/res/images/charger/battery_0.png
./ramdisk/res/images/charger/battery_fail.png
./ramdisk/res/images/charger/battery_5.png
./ramdisk/res/images/charger/battery_3.png
./ramdisk/res/images/charger/battery_4.png
./ramdisk/res/images/charger/battery_1.png
./ramdisk/res/images/charger/battery_2.png
./ramdisk/init.qcom.syspart_fixup.sh
./ramdisk/ueventd.qcom.rc
./ramdisk/charger
./ramdisk/sys
./ramdisk/init.qcom.class_main.sh
./ramdisk/init.usb.rc
./ramdisk/init.qcom.sh
./ramdisk/init.carrier.rc
./ramdisk/init.qcom.early_boot.sh
./ramdisk/ueventd.rc
./ramdisk/init.target.rc
./ramdisk/init.rc
./ramdisk/data
./ramdisk/init.qcom.class_core.sh
./ramdisk/init.qcom.usb.rc
./ramdisk/proc
./ramdisk/lpm.rc
./ramdisk/init
./ramdisk/property_contexts
./ramdisk/fstab.qcom
./ramdisk.cpio.gz
Nothing in /dev. Apparently those files are created by kernel/something else?
I'm feeling out of ideas currently, don't know where to start looking... i mean everything compiles ok, no errors. Logcat says:
Code:
I/bt_userial_vendor( 1515): userial vendor open: opening /dev/ttyO1
E/bt_userial_vendor( 1515): userial vendor open: unable to open /dev/ttyO1
E/bt_userial( 1515): userial_open: wrong numbers of open fd in vendor lib [0]!
E/bt_userial( 1515): userial_open: HCI UART expects only one open fd
From what i looked at bluedroid code, the tty opening should happen in vendor bt lib... meh. Same libs work with CM, i'm already using system/bluetooth and external/bluetooth from CM, along with qcom libs of course.
And about the phone, i can't seem to get apns to show, even though i copied proper apns list from CM. Even did a factory reset just to eliminate possibility about bad datas etc.
Click to expand...
Click to collapse
Hmmm.. Something is wrong lets reference to the stock kernel maybe we get answeres
:silly:
edit: Even stock kernel doesnt have have guess issue is different
---------- Post added at 09:50 PM ---------- Previous post was at 09:27 PM ----------
Looking at the logcat and staring at it for 20 minutes i think Logcats says
There is permission issue in the /system/vendor folder , missing bluetooth libs :cyclops: or simply permission issue

mythi said:
Hmmm.. Something is wrong lets reference to the stock kernel maybe we get answeres
:silly:
edit: Even stock kernel doesnt have have guess issue is different
---------- Post added at 09:50 PM ---------- Previous post was at 09:27 PM ----------
Looking at the logcat and staring at it for 20 minutes i think Logcats says
There is permission issue in the /system/vendor folder , missing bluetooth libs :cyclops: or simply permission issue
Click to expand...
Click to collapse
Heh, yes it might a permission issue, i've tried to match my updater-script perms to CM's, but not sure if they should be the same or something else. Suggestions welcome.
Edit: perms system:
Code:
drwxr-xr-x root root 2014-01-29 22:11 app
drwxr-xr-x root shell 2014-01-29 22:12 bin
-rw-r--r-- root root 3405 2008-08-01 15:00 build.prop
drwxr-xr-x root root 2014-01-29 22:11 cameradata
drwxr-xr-x root root 2014-01-29 22:11 etc
drwxr-xr-x root root 2014-01-29 22:11 fonts
drwxr-xr-x root root 2014-01-29 22:11 framework
drwxr-xr-x root root 2014-01-29 22:11 lib
drwxr-xr-x root root 1970-01-01 02:00 lost+found
drwxr-xr-x root root 2014-01-29 22:11 media
drwxr-xr-x root root 2014-01-29 22:11 tts
drwxr-xr-x root root 2014-01-29 22:11 usr
drwxr-xr-x root shell 2014-01-29 22:11 vendor
drwxr-xr-x root shell 2014-01-29 22:12 xbin
perms /system/vendor:
Code:
drwxr-xr-x root shell 2014-01-29 22:11 firmware
drwxr-xr-x root shell 2014-01-29 22:11 lib
perms /system/vendor/lib:
Code:
-rw-r--r-- root root 13880 2008-08-01 15:00 libbt-vendor.so
perms /system/vendor/firmware:
Code:
-rw-r--r-- root root 9432 2008-08-01 15:00 bcm2079xB4_firmware.ncd
-rw-r--r-- root root 783 2008-08-01 15:00 bcm2079xB4_pre_firmware.ncd
-rw-r--r-- root root 47921 2008-08-01 15:00 bcm4335.hcd
-rw-r--r-- root root 28862 2008-08-01 15:00 bcm4335_A0.hcd
-rw-r--r-- root root 47921 2008-08-01 15:00 bcm4335_murata.hcd
-rw-r--r-- root root 70 2008-08-01 15:00 bcm4335_prepatch.hcd
-rw-r--r-- root root 47921 2008-08-01 15:00 bcm4335_semco.hcd
Maybe i'll need to set them root:shell in vendor?

spegelius said:
Heh, yes it might a permission issue, i've tried to match my updater-script perms to CM's, but not sure if they should be the same or something else. Suggestions welcome.
Edit: perms system:
Code:
drwxr-xr-x root root 2014-01-29 22:11 app
drwxr-xr-x root shell 2014-01-29 22:12 bin
-rw-r--r-- root root 3405 2008-08-01 15:00 build.prop
drwxr-xr-x root root 2014-01-29 22:11 cameradata
drwxr-xr-x root root 2014-01-29 22:11 etc
drwxr-xr-x root root 2014-01-29 22:11 fonts
drwxr-xr-x root root 2014-01-29 22:11 framework
drwxr-xr-x root root 2014-01-29 22:11 lib
drwxr-xr-x root root 1970-01-01 02:00 lost+found
drwxr-xr-x root root 2014-01-29 22:11 media
drwxr-xr-x root root 2014-01-29 22:11 tts
drwxr-xr-x root root 2014-01-29 22:11 usr
drwxr-xr-x root shell 2014-01-29 22:11 vendor
drwxr-xr-x root shell 2014-01-29 22:12 xbin
perms /system/vendor:
Code:
drwxr-xr-x root shell 2014-01-29 22:11 firmware
drwxr-xr-x root shell 2014-01-29 22:11 lib
perms /system/vendor/lib:
Code:
-rw-r--r-- root root 13880 2008-08-01 15:00 libbt-vendor.so
perms /system/vendor/firmware:
Code:
-rw-r--r-- root root 9432 2008-08-01 15:00 bcm2079xB4_firmware.ncd
-rw-r--r-- root root 783 2008-08-01 15:00 bcm2079xB4_pre_firmware.ncd
-rw-r--r-- root root 47921 2008-08-01 15:00 bcm4335.hcd
-rw-r--r-- root root 28862 2008-08-01 15:00 bcm4335_A0.hcd
-rw-r--r-- root root 47921 2008-08-01 15:00 bcm4335_murata.hcd
-rw-r--r-- root root 70 2008-08-01 15:00 bcm4335_prepatch.hcd
-rw-r--r-- root root 47921 2008-08-01 15:00 bcm4335_semco.hcd
Maybe i'll need to set them root:shell in vendor?
Click to expand...
Click to collapse
try making perms in vendor as root excute user and group (i think in other words it is root:shell) this will inusre if we have perm issue

mythi said:
try making perms in vendor as root excute user and group (i think in other words it is root:shell) this will inusre if we have perm issue
Click to expand...
Click to collapse
No go with relaxed permissions, even set the x bit on... also noticed that /system/etc/bluetooth had some strange permissions, but no change.
I noticed that there are some bluetooth related devices in /dev, like ttyHS0 so it isn't fully dead. The problem is to find out why the damn ttyO1 won't start... actuallu i'm not liking the current state where i use most of the Bluetooth implemntation from CM. What i'd like is to have as close to AOSP as possible. Maybe i'll need to start cherrypicking parts of the bluetooth code and take only needed stuff to support qcom chips. But that'll take a while to get working.
Oh and stumbled upon some telephony code in framework/opt/telephony. Saw some files like SamungQualcom in CM sources, which indicates that to get phone working, checking through that code is needed. Quick compare showed some 100 files are different, so there;s work there too...

spegelius said:
No go with relaxed permissions, even set the x bit on... also noticed that /system/etc/bluetooth had some strange permissions, but no change.
I noticed that there are some bluetooth related devices in /dev, like ttyHS0 so it isn't fully dead. The problem is to find out why the damn ttyO1 won't start... actuallu i'm not liking the current state where i use most of the Bluetooth implemntation from CM. What i'd like is to have as close to AOSP as possible. Maybe i'll need to start cherrypicking parts of the bluetooth code and take only needed stuff to support qcom chips. But that'll take a while to get working.
Oh and stumbled upon some telephony code in framework/opt/telephony. Saw some files like SamungQualcom in CM sources, which indicates that to get phone working, checking through that code is needed. Quick compare showed some 100 files are different, so there;s work there too...
Click to expand...
Click to collapse
Why dont we cherry pick from gs4 snapdragon version qcom things since they share the same board , just cherry pick the diver files from an aosp rom for that device I am quite sure it will work .
Sent from my GT-I9295 using Tapatalk

Don't give up!
Let me know if there's something I can do!
Saturday 95℅ free time if the weather doesn't turn to warm (bike is calling)
Sent from my GT-I9295 using xda app-developers app

Related

[9 Nov 11][Fix]GPS only works once after reboot / RUNNYMEDE 1.05.401.4 - dungphp

Hi all,
i noticed that GPS only works once after a reboot on this ROM.
Please note - This fix may work on any ROM, which uses tytung's GPS Libraries:
[26.Aug.2011][Dev] GPS Libraries v2.1 with AGPS support for HD2 Gingerbread
So even if your don't use dungphp RUNNYMEDE 1.05.401.4 - Android 2.3.5 - Sense 3.5 - it's worth a try to fix it this way.
You can fix it by modifying your gps.conf file from /system/etc/.
Note!
When modifying the file via ADB pull, its nessecary to set correct file permissions when pushed back to device by ADB.
Please note the original file permissions of gps.conf and ensure it has this permission settings when finshed editing the file.
There are alots of guides how to check/change file permissions on XDA/Google, so please read on this if your are not familiar to work on this.
e.g.:
Google: get set file permissions ADB
Google: get set file permissions ES Explorer
Pull your gps.conf file or edit it on device.
Your file should contain the parameter GPS1_CLEANUP_ENABLED=1 which it set to 1 by default.
If this parameter is missing in your file - add it.
Set the parameter to 0 (zero/off) .
It should look like this:
Code:
NTP_SERVER=yourCountryCode.pool.ntp.org
XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra.bin
XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra.bin
SUPL_HOST=supl.google.com
SUPL_PORT=7276
###########################################
# Enable/disable automatic (periodic) #
# download requests of gpsOneXTRA #
# assistance data to client #
# Range: 0 to 1 #
# Default: 0 (Disabled) #
###########################################
GPS1_XTRA_AUTO_DOWNLOAD_ENABLED=1
###########################################
# Time (in hours) between automatic #
# download requests of gpsOneXTRA #
# assistance data to client #
# Range: 1 to 168 (168 = hr in a week) #
# Default: 24 hr #
###########################################
GPS1_XTRA_DOWNLOAD_INTERVAL=24
###########################################
# Enable/disable to shutdown the gpsOne #
# engine properly on GPS off #
# Range: 0 to 1 #
# Default: 1 (Enabled) #
###########################################
[COLOR="Red"]GPS1_CLEANUP_ENABLED=0[/COLOR]
###########################################
# Time (in seconds) between invoking #
# pdsm_get_position() #
# Range: 2 to 120 #
# Default: 2 seconds #
###########################################
GPS1_SESSION_TIMEOUT=2
Save your file or push it back to device and boot into CWM.
Don't forget to set the correct file permissions!
Thats it - reboot now.
GPS should work now everytime you need it.
Yours, Stephan
Is this just a bug with RUNNYMEDE? Because GPS works fine on HyperDroid with that enabled.
OCedHrt said:
Is this just a bug with RUNNYMEDE? Because GPS works fine on HyperDroid with that enabled.
Click to expand...
Click to collapse
Hi mate,
i tried it on 2 EU HD2 with this ROM - both showed the same behaviour - GPS didn't worked more than once before the fix and after fixing all was fine
I don't know if it's a problem on other ROMS, but it's worth a try when the ROM comes up with this particular symptom.
Greetz, Stephan
Nice man ! Thank you very much...
dungphp said:
Nice man ! Thank you very much...
Click to expand...
Click to collapse
Hi dungphp,
you are welcome
We have to thank you for your hard work on the ROMs!
Yours, Stephan
brush2 said:
Hi all,
i noticed that GPS only works once after a reboot on this ROM.
You can fix it by modifying your gps.conf file from /system/etc/.
Pull your gps.conf file or edit it on device.
Your file should contain the parameter GPS1_CLEANUP_ENABLED=1 which it set to 1 by default.
If this parameter is missing in your file - add it.
Set the parameter to 0 (zero/off) .
It should look like this:
Code:
NTP_SERVER=yourCountryCode.pool.ntp.org
XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra.bin
XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra.bin
SUPL_HOST=supl.google.com
SUPL_PORT=7276
###########################################
# Enable/disable automatic (periodic) #
# download requests of gpsOneXTRA #
# assistance data to client #
# Range: 0 to 1 #
# Default: 0 (Disabled) #
###########################################
GPS1_XTRA_AUTO_DOWNLOAD_ENABLED=1
###########################################
# Time (in hours) between automatic #
# download requests of gpsOneXTRA #
# assistance data to client #
# Range: 1 to 168 (168 = hr in a week) #
# Default: 24 hr #
###########################################
GPS1_XTRA_DOWNLOAD_INTERVAL=24
###########################################
# Enable/disable to shutdown the gpsOne #
# engine properly on GPS off #
# Range: 0 to 1 #
# Default: 1 (Enabled) #
###########################################
[COLOR="Red"]GPS1_CLEANUP_ENABLED=0[/COLOR]
###########################################
# Time (in seconds) between invoking #
# pdsm_get_position() #
# Range: 2 to 120 #
# Default: 2 seconds #
###########################################
GPS1_SESSION_TIMEOUT=2
Save your file or push it back to device and boot into CWM.
Use the option menu Advanced then option Fix Permissions.
Thats it - reboot now.
GPS should work now everytime you need it.
Yours, Stephan
Click to expand...
Click to collapse
do we add ALL the text here you've written or just GPS1_CLEANUP_ENABLED=1,so sorry for the noob question lol
Ty5982 said:
do we add ALL the text here you've written or just GPS1_CLEANUP_ENABLED=1,so sorry for the noob question lol
Click to expand...
Click to collapse
LOL - hey mate,
of course only the parameter and it's value is required:
GPS1_CLEANUP_ENABLED=0
Btw: You wrote the parameter set to 1, this is the default value and is the reason for GPS failure.
This value must be set to 0 to get it to work!
I pasted the whole modified file here to show how it could/should look in the end.
Now we can see - even posting the whole file did not help in your case
Just kidding - have a nice day.
Greetz, Stephan
brush2 said:
LOL - hey mate,
of course only the parameter and it's value is required:
GPS1_CLEANUP_ENABLED=0
Btw: You wrote the parameter set to 1, this is the default value and is the reason for GPS failure.
This value must be set to 0 to get it to work!
I pasted the whole modified file here to show how it could/should look in the end.
Now we can see - even posting the whole file did not help in your case
Just kidding - have a nice day.
Greetz, Stephan
Click to expand...
Click to collapse
must apologise lol,early mornin here,not fully awake yet lol,was just curious as ive flashed loadsa fixes,even a gps fix apk floating around here and also faster fix that comes pre-installed,i've even edited my build prop,but nothing ever seems to work lol,but i've tried your solution,will use gps test from the market to see if anythings happening
EDIT: after this i get 9 sattelites in view 8 used,as before i didn't get any or if my phone was in a good mood i'd get 1 lol..........SO IT WORKS
Ty5982 said:
must apologise lol,early mornin here,not fully awake yet lol,was just curious as ive flashed loadsa fixes,even a gps fix apk floating around here,i've even edited my build prop,but nothing ever seems to work lol,but i've tried your solution,will use gps test from the market to see if anythings happening
Click to expand...
Click to collapse
Ok mate - good luck.
I hope i didn't promised too much
Would be nice to get some feedback from you - your info may help others!
Greetz, Stephan
brush2 said:
Ok mate - good luck.
I hope i didn't promised too much
Would be nice to get some feedback from you - your info may help others!
Greetz, Stephan
Click to expand...
Click to collapse
IT WORKS,IT WORKS,IT WORKS,IT WORKS,IT WORKS,IT WORKS,IT WORKS....................CAN'T SAY THANK YOU ENOUGH,i've got 4 bars signal as to the usual none and i aint even outside lol,will see when i take my little girl school in 15 min..........will tell u more then,feels like christmas has come early lol
Ty5982 said:
IT WORKS,IT WORKS,IT WORKS,IT WORKS,IT WORKS,IT WORKS,IT WORKS....................CAN'T SAY THANK YOU ENOUGH,i've got 4 bars signal as to the usual none and i aint even outside lol,will see when i take my little girl school in 15 min..........will tell u more then,feels like christmas has come early lol
Click to expand...
Click to collapse
Hugs from germany
Yours, Stephan
So using Dansta's Runnymede rom does that line get pasted at the end of the gps.conf info? Like the last line I mean.
chrisrj28 said:
So using Dansta's Runnymede rom does that line get pasted at the end of the gps.conf info? Like the last line I mean.
Click to expand...
Click to collapse
Hi mate,
maybe; - maybe means of course only if it does not exists upwards. I am not sure how it reacts if the parameter occurs twice with two different values - but i think the last occurence of this parameter in file should "win"
Greetz, Stephan
brush2 said:
Hugs from germany
Yours, Stephan
Click to expand...
Click to collapse
the english aren't suppose to like the germans lol,but u can be an exception lol.........my results using gps test from the market not GPS STATUS & TOOLBOX AS ITS NOT AS ACCURATE........
satellites in view 17
satellites used 15
accuracy(feet) 14.9
speed(mph) 0
NOT TO SURE HOW GOOD THESE RESULTS ARE,BUT THEY ARE 1000% BETTER THAN WHAT I USED TO GET
1 thing i did notice and is VERY IMPORTANT is if you have previously done a fix permissions for anything else,DELETE THE LOG SAVED ON YOUR SD CARD 1ST,add file to gps.config,save,reboot,then clickon fix permissions
Ty5982 said:
the english aren't suppose to like the germans lol,but u can be an exception lol.........my results using gps test from the market not GPS STATUS & TOOLBOX AS ITS NOT AS ACCURATE........
satellites in view 17
satellites used 15
accuracy(feet) 14.9
speed(mph) 0
NOT TO SURE HOW GOOD THESE RESULTS ARE,BUT THEY ARE 1000% BETTER THAN WHAT I USED TO GET
1 thing i did notice and is VERY IMPORTANT is if you have previously done a fix permissions for anything else,DELETE THE LOG SAVED ON YOUR SD CARD 1ST,add file to gps.config,save,reboot,then clickon fix permissions
Click to expand...
Click to collapse
Regarding "love between brits and germans" - i don't understand this is really a topic - damn; ain't there bigger problems in life?
The fix should not touch/change anything about accuracy. It only forces GPS to work as it should - .. more than once after a reboot...
Regarding deleting of fix permission log file - i don't think it has to be deleted to get the fix to work. But fixing the permissions is important to set the correct permissions for gps.conf file after modifying it.
Greetz, Stephan
brush2 said:
Regarding "love between brits and germans" - i don't understand this is really a topic - damn; ain't there bigger problems in life?
The fix should not touch/change anything about accuracy. It only forces GPS to work as it should - .. more than once after a reboot...
Regarding deleting of fix permission log file - i don't think it has to be deleted to get the fix to work. But fixing the permissions is important to set the correct permissions for gps.conf file after modifying it.
Greetz, Stephan
Click to expand...
Click to collapse
it works and that's all that matters
Why bother with CWR fix permissions as it can cause other issues (such as losing contact pictures in Messaging) - why not just edit the file with Root Explorer or ES Explorer, save and then longpress on the file and select properties and set all the permissions there? The file needs all nine boxes ticked for permissions. Also to make sure the file saves if you are using ES Explorer (not sure with Root Explorer) before you edit the file you need to go into settings and make sure you tick 'Mount system as writeable' otherwise it won't save.
Dunc001 said:
Why bother with CWR fix permissions as it can cause other issues (such as losing contact pictures in Messaging) - why not just edit the file with Root Explorer or ES Explorer, save and then longpress on the file and select properties and set all the permissions there? The file needs all nine boxes ticked for permissions. Also to make sure the file saves if you are using ES Explorer (not sure with Root Explorer) before you edit the file you need to go into settings and make sure you tick 'Mount system as writeable' otherwise it won't save.
Click to expand...
Click to collapse
Hi there,
You're right - it's more save only touching the permissions of gps.conf file. I will leave a note in the intial post to ensure people keep this in mind.
Thanks and Greetz, Stephan
OCedHrt said:
Is this just a bug with RUNNYMEDE? Because GPS works fine on HyperDroid with that enabled.
Click to expand...
Click to collapse
Look at the known issues #3 in my GPS thread for the reasons. It's there long time ago.
Some ROMs suffer from the "GPS off-and-on" bug.
Those ROMs can shutdown the gpsOne engine properly when turning off GPS setting using gps_cleanup(), but they cannot restart the gpsOne engine again because gps_init() is never called when turning GPS setting on after turning it off.
It's a Gingerbread bug which is fixed by applying this commit from the source code.
If you cannot modify the source code, the workaround is to set/add GPS1_CLEANUP_ENABLED=0 into gps.conf to avoid doing full cleanup.
Click to expand...
Click to collapse
tytung said:
Look at the known issues #3 in my GPS thread for the reasons. It's there long time ago.
Click to expand...
Click to collapse
I vaguely remember reading that But thanks always for your work.

[TOOL][v1.2.0] Batch Deodexing Tools using Android Device

[Tool/Utility][v1.2.0]Apktool Mobile Batch Deodexing - Run Batch Deodex Jobs Using Your Android Device!
*** Disclamer
Your device is shipped without root for a reason. Modifying system files that are normally off limits carries the risk of being caught in a situation where you will be unable to fix the damage unless you plan ahead.
It is wise to not proceed unless you have a means of restoring your device in the event of a catastrophic event and that you are confident in your ability to restore any issues you create.
I am not and will not be responsible for any harm that may come to your device or to your sanity as a result of **** up.
For more on what's expected, new members should help themselves to the video below.
Description
A toolset for performing batch deodexing straight from your device. Comes installable as a flashable zip and can easily be modified by advanced users to suit their needs. Just drop all your odex and corresponding archives into a folder and run one simple terminal command (or use Linux Script Handler within your File Manager) and deodezed versions will be outputted to a separate folder.
I wrote this because Apktool Mobile lacks any batch features.
COMPATIBLE FOR ALL ANDROID DEVICES RUNNING ICS OR LATER!
Project is just listed here because I had to choose a location specific to a certain device when creating the project. Mods, feel free to move if desired.
Learn more about deodexing and the differences between an odexed system and deodexed system
Installed Files/Directories:
/sdcard/bdt - Directory with our smali and baksmali jars as well as directories to place batch jobs in as well as output folders. There is a readme in each folder describing it's function.
/data/misc/bdt - Directory which contains the Java Runtime Environment as well as all dependent libraries.
/system/bin - Two scripts are installed here. The first is "bdt" and contains all path variables in case you need to edit a path (ex. you download newer smali/baksmali versions to use, or change the name of the bdt directory on your /sdcard). This also contains wrapper functions athat do all the work. The second file is "batch-deodex" and once you have placed your odex (and corresponding apk/jar) files into the /sdcard/bdt/files-to-deodex folder open a command prompt and run this script to deodex all the odex files into dex files and then insert into the corresponding archive.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Installation Instructions and Usage
Download the latest version from one of the hosts in the downloads section and simply flash it in recovery. You could always manually extract the contents but then you'd also have to chmod quite a bit to set the permissions.
To uninstall, flash the uninstall zip that's also in the downloads section, or manually delete /system/bin/bdt, /system/bin/batch-deodex, /data/misc/bdt folder, and /sdcard/bdt folder.
Batch baksmali/smali
To run a batch decompile, move your odex (or deodexed apk or jars) files into /sdcard/bdt/files-to-deodex and fire a command prompt up and type:
Code:
su
. /system/bin/bdt # Import paths and functions
batch-baksmali
The source folders will be outputted to /sdcard/bdt/smali-source.
To compile a batch of deodexed source folders we just do essentially the same thing. Open up a command prompt and type:
Code:
su
. /system/bin/bdt
bbdth-smali
Doing so will create a dex file for each source folder and this will be outputted to /sdcard/bdt/dex-out.
Batch deodexing
Performing a batch deodex works much the same way. Copy all the odex files and their corresponding apk or jar into /sdcard/bdt/files-to-deodex then open a command prompt up and type:
Code:
su
# no need to import anything for this
batch-deodex
Just that easy. The script may take a while depending on how many files you're deodexing just as with the other scripts so if running a lot be patient.
The deodex script moves all odex files to ../files-to-baksmali and then calls batch-backsmali. Then the script calls batch-smali to create the dex files. After that's done it enumerates through the dex files and finds each one's corresponding archive and once it does it uses the
Code:
zip -jq {archive} classes.dex
to insert classes.dex into the archive without extracting anything or changing any compression settings, etc.
Once complete you'll have your deodexed archives and the script cleans up all other directories. The other two scripts don't do this.
Known Issues
-- Discovered that some ROMs are telling me that my scripts don't exists when they very well do, so of you are seeing a "sh: {scriptname}: The file or directory cannot be found" then just run by using the Linux Script Handler within your File Manager until I figure this out or until the ROM dev gets in touch.
-- I just discovered this error while preparing these test screenshots. It didn't effect the deodexing process though but I'll look into fixing this tomorrow. UPDATE: Haven't looked into this yet as it has no effect on the outcome. I think it's occurring because on the final loop when running a batch and when all is finished it still runs one last time, thinking it's looking for a jar file. Once I get these other minor details done I'll publish on github. Actually there is published code there now, but ir needs to be removed and updated.
Downloads
Batch Deodex Tools 1.2.0 - Box
Batch Deodex Tools 1.2.0 - Dropbox
Uninstall ZIP for 1.1.0
Changelog
Code:
1.2.0 Released: -- 08/21/14
-- fixed an issue causing the /sdcard/BDT folder to not be properly flashed
-- some editing made to the scripts in preparation for uploading to github
1.1.0 Released: -- 06/26/14
-- turned into a stand alone project
-- optimized the scripts
-- flashable in recovery
-- also created flashable zip to uninstall
1.0.1 Released: -- 06/21/14
-- initial release
TO DO
-- Migrate the JRE off /data/... to prepare for Android L. Was going to move to /data/app-lib where it probably should have been to begin but no point now, so will remain in /data/misc/bdt for the time. Rwas more in the Addendum in second post
-- Add Box, Dropbop, and Mega hosts as well. Well having just a Drive and Box host should accommodate the demand. If the demand increases I'll adjust accordingly.
-- Publish code to github.
-- Scratched making this into an APK... Having it as is makes it easier for advanced users to make modifications (use custom files, etc) on the fly
Thanks To/Credits
Code:
* Brut.all for giving us apktool and much more
*
XDA:DevDB Information
Batch Deodex Tools - Android, Tool/Utility for the LG G2
Contributors
MidnightHarvester
Version Information
Status: Stable
Current Stable Version: 1.2.0
Stable Release Date: 2014-08-21
Created 2014-06-22
Last Updated 2014-08-21
Reserved
APPENDUM
Consider this a diary. Dates are when the thoughts or discoveries hit me, not release dates
Aug 15 - After modifying the tookset so it"s Android L ready by moving the JRE to /system/{wherever}, after flashing now the BDT directory doesn't get flashed to the sdcard. I'll need to do a little fiddling with the updater script, then release it once it's working. Granted you can just manually extract and copy that directory over easily but I'd prefer a fully working flaahable..
Aug 19 - Noticed there has been updated smali and baksmali jars, so either an incremental update and most likely just a patch will be worked I n and releaaed. Because of the update I'm also looking at any other files that may have been updated.
Aug 20 - I've discovered that on some devices (specifcally, CloudyG3 1.3), that t
here arr some issues running the scripts via terminal as apparently ... they don't exist. Executing them via Linux Script Handler within a File Manager should work until I figure this out)
Aug 20 - Releases will be migrated over time to my Box account, probably Dropbox account, as well as Mega. Archived releases will also be uploaded, and the OP will be updated as each is moved.
Aug 21 - Fixed a bug preventing the /sdcard/bdt directory from being installed on flash. Also made a few revisions to the code, nothing spectacular. Also uploaded to Box and Dropbox and ditched the Drive host. Incremental update to 1.2 0.
Good job buddy. Keep it up. Will give a try it soon.
Sent from my GT-I9100 using Tapatalk 2
Thanks! I'll be publishing an update in a day or so. I'm creating a stand alone project that won't require root. Right now root is required because the scripts need to access the JRE bin that's located in the data directory of apktool. I'm moving JRE lib (and Java binary) and smali and baksmali jars into a flashable zip.
It'll also be a lot easier to maintain this way. I completely killed my phone yesterday while cleaning up the scripts. After doing a batch deodex as it is now it will clean up the working directories and delete
everything except the deodexed archives.
I modified the paths hoping to create less work in the long run and after testing the modified script by phone rebooted back up and I got "unable to find setup" message and a blank screen. I must have left a "/" off of a path and ended up wiping everything in /sdcard/ ?
The error on boot was caused by the fact I always delete the LG setup app as I never anticipate deleting my SD card. So I was stuck at a black screen with nothing to restore since I wiped the SD card.
Eventually I realized I could pull the notification bar down still, and make it into settings by long pressing a quick toggle. Once I discovered I could open Google Now after enabling it in search settings I was in my way since I could use that to open Chrome and Root Explorer, etc.
I ended up restoring my system back and just wiped /data as well since I already wiped my SD card. Then spent the rest of the day restoring my device and luckily I had most everything backed up onto Drive.
Needless to say no changes were published in yesterday. I can imagine the backlash I would have gotten if I did lol. If I had a penny for each time I've mucked my device up while working on something I'd have, well maybe a dollar but still that's a lot
It shouldn't take long to get the standalone build out. I don't plan on turning the standalone build into an apk though as its easy enough to run via terminal emulator or file manager and take up far less space.
Sent from my VS980 4G using Tapatalk
I'll find another host to upload the install zip to as well as the Drive host in the OP. The zip is too large to attach here. I hope this simplification over installation appeals to more ?
Version 1.1.0 is now live. Installation boils down to just flashing the install zip in recovery. Read OP for additional information on how to use it.
Dang man! You beat me to it hahaha! I had started on this as a personal project for myself earlier today. However, I am wanting to just implement the process strictly through the recovery and by locating/finding all .odex files in my system to later deodex and place back accordingly all without me touching a thing but just running the script. I'm currently digging through your work right now to see if anything may be helpful for what I am aiming to do. Nevertheless, greatly appreciate you sharing this project.
How do you make an odexed apk into am installable apk? I wanna take the LG QVoice apk from an odexed rom and be able to install it like a normal app without having to add it to /system/app or /system/priv-app. Would just deodexing the apk do that?
Skizzy034 said:
How do you make an odexed apk into am installable apk? I wanna take the LG QVoice apk from an odexed rom and be able to install it like a normal app without having to add it to /system/app or /system/priv-app. Would just deodexing the apk do that?
Click to expand...
Click to collapse
You would most likely need to deodex that app and then install it via /data/app.
Make sure that system app you are referring to doesn't use any lib files or other dependencies. Some system apps do and it would be needed to port them over to your device for them to work (and possibly some work on the app itself once decompiled).
Sent from my C525c using Tapatalk
Modding.MyMind said:
You would most likely need to deodex that app and then install it via /data/app.
Make sure that system app you are referring to doesn't use any lib files or other dependencies. Some system apps do and it would be needed to port them over to your device for them to work (and possibly some work on the app itself once decompiled).
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
Yea I didn't think of lib files for that app. It makes sense it would need it. Thanks.
Modding.MyMind said:
Dang man! You beat me to it hahaha! I had started on this as a personal project for myself earlier today. However, I am wanting to just implement the process strictly through the recovery and by locating/finding all .odex files in my system to later deodex and place back accordingly all without me touching a thing but just running the script. I'm currently digging through your work right now to see if anything may be helpful for what I am aiming to do. Nevertheless, greatly appreciate you sharing this project.
Click to expand...
Click to collapse
That's an awesome idea bro. You'd need the jre in /data/misc/jdr somewhere. You may be able to run it off the scars in recovery since you can set permissions to the /sdcard mount there but not sure.
Create a script that 'finds' all odex files system wide and corresponding archive files and use the run_program edify script command to run the script so that you can deodex everything from recovery with one slide of a button.
There's not too much that would have to be changed in the script other than changing some of working directory variables as you go. Be careful in the batch-deodex script if borrowing from that as that deletes all odex, apk, and jar files in the /BDT/*/ except for the readme files.
Edit: If you need any advice or help on that project hit me up, as I could probably get it working by the end of the day. Well sooner not this day as my son is here but tomorrow.. Sorry I didn't comment the script that much but there wasn't really much to comment, so I mainly just commented the paths.
MidnightHarvester said:
That's an awesome idea bro. You'd need the jre in /data/misc/jdr somewhere. You may be able to run it off the scars in recovery since you can set permissions to the /sdcard mount there but not sure.
Create a script that 'finds' all odex files system wide and corresponding archive files and use the run_program edify script command to run the script so that you can deodex everything from recovery with one slide of a button.
There's not too much that would have to be changed in the script other than changing some of working directory variables as you go. Be careful in the batch-deodex script if borrowing from that as that deletes all odex, apk, and jar files in the /BDT/*/ except for the readme files.
Click to expand...
Click to collapse
Thanks. I had already set up my project folder along with my deodex script before I came across this thread (what were the odds lol). Was having issues getting the script to work at all until I looked at yours and notice you were exporting the LD_LIBRARY path. I implemented that idea in my script and now I'm getting a few failures for linking executables based on certain commands such as grep for example.
The script is a combination of premade works from different people which I have put together as followed. Currently, the script is a bit rough on what I am aiming to do but my goal for now is to get it to successfully find and deodex all necessary files. Once accomplished, I will proceed forward.
Script:
PHP:
#!/sbin/sh
cd $(dirname "$0")
DEODEXED_APK="/data/DEODEXED.log"
if [ ! -f $DEODEXED_APK ]; then
busybox touch $DEODEXED_APK;
fi;
prop="/system"
smalibaksmali_dir="/data/local/tmp/smali"
java_dir="/data/local/tmp/jvm/java-7-openjdk-armhf/jre/bin/java"
#tmp="$(dirname "$1")"
export LD_LIBRARY_PATH="/data/local/tmp/jvm/java-7-openjdk-armhf"
# Deodexes every .odex file
DEODEX() {
local API="$(busybox grep "ro.build.version.sdk" "$prop/build.prop" | busybox cut -d'=' -f2)"
echo "Detected API level $API" >> $DEODEXED_APK
busybox find "$prop" -type f -iname "*.odex" | while read line; do
local FILE="$(basename "$line")"
local FILEDIR="$(dirname "$line")"
echo "Deodexing $FILE" >> $DEODEXED_APK
echo "Disassembling $FILE..." >> $DEODEXED_APK
$java_dir -Xmx512m -jar $smalibacksmali_dir/baksmali-2.0.2.jar -a "$API" -d "$prop/framework" -x "$FILEDIR/$FILE"
if [[ $? -ne 0 ]]; then
echo "ERROR DEODEXING $FILE, ABORTING!" >> $DEODEXED_APK
rm -rf out
return 1
fi
echo "Assembling into classes.dex..."
$java_dir -Xmx512m -jar $smalibacksmali_dir/smali-2.0.2.jar -a "$API" -o classes.dex out
if [[ ! -e classes.dex ]]; then
echo "ERROR DEODEXING $FILE, ABORTING!" >> $DEODEXED_APK
rm -rf out
return 1
fi
FILE="$(busybox echo "$FILE" | busybox rev | busybox cut -d'.' -f2- | busybox rev)"
local FOUND=0
for EXTENSION in "jar" "apk"; do
if [[ -e "$FILEDIR/$FILE.$EXTENSION" ]]; then
echo "Packing back into $FILE.$EXTENSION..."
zip -rq "$FILEDIR/$FILE.$EXTENSION" classes.dex
rm -f classes.dex
FOUND=1
break
fi
done
if [[ "$FOUND" -eq 0 ]]; then
echo "ERROR, No output found?!"
rm -rf out
rm -f classes.dex
return 1
fi
rm -f "$line"
rm -rf out
done
echo "Deodexing finished"
}
# Start Processing Here
DEODEX
Sent from my C525c using Tapatalk
Saved while I read script after kid stops jumping on me lol
LD_LIBRARY_PATH threw me off to. Somewhere in java or bad small or small expects it to point to the data/data/per.pqy.apktool/lix files.
MidnightHarvester said:
Exporting LD_LIBRARY_PATH and pointing that to wherever you have the lib files stored which in apktool are in /data/data/per.pqy.apktool/lix is key cause either java or baksmali or small reference that Android environment variable.
That took me a while too until I realized what I needed to do. You can cut down on size quite a bit and copy the lib files in /data/misc/bdt in my project as those are the only ones needed for smali and baksmali. With that figured out you'll have it done in no time. You could always flash these tools and then make a script like
Code:
# import my 'bdt' script
. /system/bin/bdt
# copy all odex, apks, and jars into files-to-deodex - could
# use lath variables instead of full pathnames
cp /system/app/. *odex /sdcard/BDT/files-to-deeodex
cp /system/app/. *apk /sdcard/BDT/files-to-deeodex
cp /system/priv-app/. *odex /sdcard/BDT/files-to-deeodex
cp /system/priv-app/. *apk /sdcard/BDT/files-to-deeodex
cp /system/framework/. *odex /sdcard/BDT/files-to-deeodex
cp /system/framework. *apk /sdcard/BDT/files-to-deeodex
# call batch-deodex function
batch-deodex
Then make sure all the deoxed archives are in the deodexed-out directory and if check a few make sure classes. dex are in them lol. Then if running from recovery, copy the new deodexed archives into appropriate places and set permissions (recursively unless you're insane ).
Sounds a lot like what you're doing though. Also gives me an idea for version 2 which also gives the option to deoxed the entire system and then create a flushable zip with all the deodexed archives inside. Will probably work on that tomorrow after my son is gone. Keep me posted ed on the progress on your work though as I haven't had much in out back regarding this.
Click to expand...
Click to collapse
I like your idea about making a flashable zip once it is done. I have it working now.
I made a small typo which resolved my earlier problem.
I used "smalibaksmali_dir" as my variable which pointed to the smali directory.
However, later in my script I spelled 'bak' with a 'c' - smalibacksmali_dir.
I will keep you posted man. I was shocked when i found your thread because prior to I had spoken with a relative about my project and how it appeared no one had done this. Then I found you lol. Kudos for your work bro.
Sent from my C525c using Tapatalk
---------- Post added at 07:54 PM ---------- Previous post was at 06:58 PM ----------
Here is a screenshot with my personal script/project running.
Sent from my C525c using Tapatalk
@MidnightHarvester, my script is working great now. However, I noticed that this bogs down the device greatly. To deodex the Rom from the device will take WAY TOO LONG then if you were to do so using a descent computer. However, if merely deodexing an app here or an app there then it's fine and tolerable but not for all *.odex files at once lol.
There has to be some way to make this move along faster. Otherwise, the wait begins for phones with better processors and more ram.
Sent from my C525c using Tapatalk
Modding.MyMind said:
@MidnightHarvester, my script is working great now. However, I noticed that this bogs down the device greatly. To deodex the Rom from the device will take WAY TOO LONG then if you were to do so using a descent computer. However, if merely deodexing an app here or an app there then it's fine and tolerable but not for all *.odex files at once lol.
There has to be some way to make this move along faster. Otherwise, the wait begins for phones with better processors and more ram.
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
I'm pretty sure that the scripts are only utilizing one thread (unless I'm mistaken). Is there a way in bash to start a new thread or at least call on a binary and pass over a callback function? I'll have to look into it.
When I deodexing my /system/priv-app folder I just let it run overnight. There isn't anything really in the script I can do to speed things up much as the majority of the work is being used during the baksmali and smali calls.
That's one reason I didn't echo any output like your script did which I really wanted to but I've found that things tend to run faster without output being sent to stdout. Might not be a huge hit but...
Maybe if I an get it to deodex in recovery nobody would be competing for resources? Definitely keep updated on the thread as this isn't anywhere near done yet.
I'm glad I found somebody else working on this. For a while I thought no one was that interested since there has been PC tools to do this for ages. Problem is for some (like myself) is that THIS is my PC .
I'm trying to think on how to speed things up and drawing a blank. There aren't enough odex files in all of /system for there to be issued with looping. I think the baksmaling and smaling just take time. Take a look at Matt's old Privacy Blocker app (same Matt that developed xUltimate deodex tools on PC). It takes ages to baksmali and smali there as well.
My first early version though was even worse. I actually was decompiling resources as well in the archive and creating a smali folder and moving the decompiler source as well into there and recompiling the entire apk/jar lol. Don't ask me why.
I need to borrow an idea from you as well and let the user set API level. Normally omitting it should be fine (defaults to latest doesn't it?) but having the choices might help of anyone comes across a picky app.
In the meantime if deodexing am entire folder I'd recommend just doing it at night while you sleep. If you can, use a tool to enable all four cores and set all cores to performance mode and leave the Ax plugged in. *shrugs* I have AIDE installed so if I can get into the baksmali/smali source code maybe I can at least have a look.
Edit: I'm running a multithreading test now. You can run a command in another thread by placing '&' after the command. If it works I'll update.
@MidnightHarvester, I too use my device as it were my own computer which is why I make up the things which I do lol. Seems we have much in common. I actually learned about the idea of using multithreads with '&' just the other night as I was researching for ways to optimize my script. Another method is to use 'wait' which will put any future commands on hold until the current one is finished. That should out less stress on the cpu. Another idea is to limit the use of pipes. The more pipes being implemented the more usage the cpu has to dish out.
I believe flashing and running this in the recovery may speed this up as you mentioned that it would required less resources being used during operations, but the question is how much would the improvement be lol.
Keep me updated with using multithreads and feel free to take away whatever you find to be useful from my deodex script.
Expect many future changes to it to optimize it as much as possible.
In addition, using 'while read line' can increase the performance on speed if the following commands afterwards are not causing an overhaul.
Sent from my C525c using Tapatalk
---------- Post added at 03:10 PM ---------- Previous post was at 03:04 PM ----------
I will be pushing my project to my github later on today. Will be easier to keep up with any changes I make. Will take note in README.md that the project is still in development and to use with GRAVE caution lol.
Sent from my C525c using Tapatalk
---------- Post added at 03:13 PM ---------- Previous post was at 03:10 PM ----------
It's ashame I don't currently have any way to build the smali/baksmali sources from my phone.
Need to look in to it and see if any flags could optimize the final build to produce a more proficient workload in performance.
Sent from my C525c using Tapatalk
So, I am working on getting my project to work in the recovery. Looks like some troubleshooting is in store.
From my recovery.log:
Code:
about to run program [/tmp/deodex.sh] with 1 args
CANNOT LINK EXECUTABLE: could not load library "libc.so" needed by "busybox"; caused by library "libc.so" not found
CANNOT LINK EXECUTABLE: could not load library "libc.so" needed by "busybox"; caused by library "libc.so" not found
CANNOT LINK EXECUTABLE: could not load library "libc.so" needed by "busybox"; caused by library "libc.so" not found
Detected API level
CANNOT LINK EXECUTABLE: could not load library "libc.so" needed by "busybox"; caused by library "libc.so" not found
CANNOT LINK EXECUTABLE: could not load library "libc.so" needed by "sort"; caused by library "libc.so" not found
Deodexing finished
CANNOT LINK EXECUTABLE: could not load library "libc.so" needed by "busybox"; caused by library "libc.so" not found
run_program: child exited with status 1
Sent from my C525c using Tapatalk
---------- Post added at 05:33 PM ---------- Previous post was at 05:00 PM ----------
Resolved my problem. Export path for sbin was being overwritten by the script so it prevented busybox from being used. To resolve it you just need to insure that sbin is included to the path as well.
Edit: this was tested with TWRP
PHP:
export LD_LIBRARY_PATH="/sbin":"/tmp/jvm/java-7-openjdk-armhf"
Sent from my C525c using Tapatalk
:cyclop
Modding.MyMind said:
I like your idea about making a flashable zip once it is done. I have it working now.
I made a small typo which resolved my earlier problem.
I used "smalibaksmali_dir" as my variable which pointed to the smali directory.
However, later in my script I spelled 'bak' with a 'c' - smalibacksmali_dir.
I will keep you posted man. I was shocked when i found your thread because prior to I had spoken with a relative about my project and how it appeared no one had done this. Then I found you lol. Kudos for your work bro.
Sent from my C525c using Tapatalk
---------- Post added at 07:54 PM ---------- Previous post was at 06:58 PM ----------
Here is a screenshot with my personal script/project running.
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
No probs cyclops. Between family I don't get a chance to get on hereuch but that's all changing here Very soon. I really glad you're taking off where i left off. I saw that there's a GUI out now I haven't read the thread yet so not sure if it's your work or not, but I'm glad others are running with it. Beauty of open source. I rewrote a lot and published to github under GPL but unfortunately during the rewriting I broke something and haven't been back to fox it yet.
I need to as yje code is streamlined as well as being on github open where all can see and make commits. I would get on that but it seems the GUI version has taken off and this is more for legacy but who knows
I also noticed someone else had a btch deodex script published on github though no as robust but I should have borrowed off him instead of reinventing the wheel. Too bad I didn't see that until later.
Inteied my luck at multithreading the shell commands but that would require a LOT of counters keeping track of example which processes are still decompiling and which are recompiling to avoid collisions, so I lwdr it be for now. And now that the GUI is out maybe ibcan lend a hand there if needed.
Is the GUI just a command line GUI or an actual app?I'll look when done reading. If it's an actual app multithreading would be much easier and i wouldn't mind helping out on the team. If its a shell GUI like old Windows apktool versions I commend you. Takes patience to mundnely write out the interface
Either way glas there's interest and happy others with more time to devote can carry on.
@MidnightHarvester
Hello sir,
I'm trying to decompile settings.apk with apktool for android. It won't do it correctly, and I'm wondering if it's because it should be deodexed first. The only 2 I've been able to recompile are htc-resources.apk and framework-res.apk on HTC Evo 3D 4.0.3ics
That's first question, will be able to recompile settings after deodex?
I don't understand this command,
. /system/bin/bdt
bbdth-smali
Are these on one line, separate?
I'm fairly new to modding, will you help me please?
The commands listed, when pasted into terminal, errors a lot. Using SManager to run works, but what is got from it isn't a deodexed app.-
When running batch-deodex(I'm using bdt from v.1.1.0 because it throws out several errors with bdt from v.1.2.0, I haven't looked through it, so I'm not sure if it's just not echo ing them), well, first I put the settings.apk in files-to-deodex folder, create odex of it in apktool(is this right thing to do?) Settings.odex is created in same folder, then ran batch-deodex.
The exact same settings.odex is placed into files-to-baksmali. And same settings.apk is placed in deodexed-out. In the dex-out folder are same 2 files called classes.dex and Settings.dex. and in the smali-source is Settings folder with a boat load of smalis.
After it's done:
exec sh '/system/bin/batch-deodex'
in/batch-deodex' <
rm failed for -rf, No such file or directory
rm failed for -f, No such file or directory
cp: can't stat '/sdcard/BDT/files-to-deodex/*.jar': No such file or directory
rm failed for -f, No such file or directory
rm failed for -f, No such file or directory
rm failed for -f, No such file or directory
rm failed for -f, No such file or directory
rm failed for -f, No such file or directory
And here's the log
Error occured while loading boot class path files. Aborting. org.jf.util.ExceptionWithContext: Cannot locate boot class path file /system/framework/conscrypt.odex at org.jf.dexlib2.analysis.ClassPath.loadClassPathEntry(ClassPat h.java:217) at org.jf.dexlib2.analysis.ClassPath.fromClassPath(ClassPath.jav a:161) at org.jf.baksmali.baksmali.disassembleDexFile(baksmali.java:59) at org.jf.baksmali.main.main(main.java:274)
What am I doing wrong?
How do I get to having deodexed app?
Sent from above using xparent tapatalk blue

[KERNEL] [March 21] ElementalX G4/G4 Plus 3.01 (Oreo)

ElementalX Kernel
for Moto G4 and G4 Plus
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ElementalX is designed for maximum stability. It is made for people who depend on their phone every day.
Features
Easy installation and setup with Aroma installer
Fingerprint sensor as home button
Sweep2sleep
Block wakelocks
Rootable
Sound control
Overclock or underclock CPU
NTFS r/w support
Option to disable fsync
advanced color control
performance and power optimizations
upstream ZRAM with lz4 compression
KSM enabled
brighter HBM
adjust or disable vibration
FIOPS i/o scheduler
Does not modify system partition
Does not overwrite modules
Compatible with systemless root
Installation
1. Flash in recovery
For maximum compatibility with all ROMs, ElementalX uses your existing ramdisk.
Notes
This works on both the G4 and the G4 Plus but NOT the G4 Play.
Flashing this does not modify your system partition, only the boot.img. Back up your stock boot.img in recovery or with an app and you can easily restore it if you want to return to stock or install OTAs.
EX Kernel Manager can be used to configure settings and install or update the kernel.
You can also use my free app Button Mapper to customize the actions of the fingerprint sensor if you have the G4 Plus
Google+ Community
Download
Stock Android 8.1.0 Oreo
ElementalX-G4-3.01
Stock Android 7.0
ElementalX-G4-2.01
LineageOS-based Android 7..1.1/7.1.2
ElementalX-G4-1.11-LOS
Stock Android 6.0.1
ElementalX-G4-0.07
CM-based Android 6.0.1
ElementalX-G4-0.07-cm
Source code
https://github.com/flar2/kernel-msm
_____________________________________
XDA:DevDB Information
ElementalX-G4, Kernel for the Moto G4 Plus
Contributors
flar2
Source Code: https://github.com/flar2/kernel-msm
Kernel Special Features:
Version Information
Status: Stable
Created 2016-07-24
Last Updated 2019-03-21
Reserved
0.02:
-build optimizations (linaro 4.9 -O2)
-headphone gain control
0.01:
-Fingerprint sensor as home button
-Sweep2sleep
-Overclock or underclock CPU
-NTFS r/w support
-Option to disable fsync
-advanced color control
-performance and power optimizations
-upstream ZRAM with lz4 compression
-KSM enabled
-brighter HBM
-adjust or disable vibration
-FIOPS i/o scheduler
Reserved
Hi, I have not worked WiFi.
wizard-dima said:
Hi, I have not worked WiFi.
Click to expand...
Click to collapse
Please tell me your model number and build number from the about phone page in settings.
flar2 said:
Please tell me your model number and build number from the about phone page in settings.
Click to expand...
Click to collapse
G4 plus XT1642
build number - MPJ24.139-48
You can add doubletap2wake?
Sweep2sleep only works right to left.
Although I chose to either side.
wizard-dima said:
G4 plus XT1642
build number - MPJ24.139-48
You can add doubletap2wake?
Sweep2sleep only works right to left.
Although I chose to either side.
Click to expand...
Click to collapse
I would also like to see the output of
Code:
lsmod
from adb shell or terminal.
WiFi working and no issues so far
Moto G4
XT1625
BUILD- MPJ24.139-49
LSMOD OUTPUT
Module Size Used by
wlan 4215738 0
core_ctl 20182 0
qdrbg_module 30626 0
qcrypto_module 145880 0
flar2 said:
I would also like to see the output of
Code:
lsmod
from adb shell or terminal.
Click to expand...
Click to collapse
You kernel:
Module Size Used by
qdrbg_module 30626 0
qcrypto_module 145880 0
Stock kernel:
Module Size Used by
core_ctl 20182 0
wlan 4215738 0
qdrbg_module 30626 0
qcrypto_module 145880 2
zanoli99 said:
WiFi working and no issues so far
Moto G4
XT1625
BUILD- MPJ24.139-49
LSMOD OUTPUT
Module Size Used by
wlan 4215738 0
core_ctl 20182 0
qdrbg_module 30626 0
qcrypto_module 145880 0
Click to expand...
Click to collapse
perfect, thanks!
wizard-dima said:
Module Size Used by
qdrbg_module 30626 0
qcrypto_module 145880 0
Click to expand...
Click to collapse
One more question:
Can you show me the output of these commands:
Code:
ls -la /system/lib/modules/
Code:
su -c insmod /system/lib/modules/wlan.ko
flar2 said:
One more question:
Can you show me the output of these commands:
Code:
ls -la /system/lib/modules/
D:\ADB>adb shell ls -la /system/lib/modules/
-rw-r--r-- root root 9404 2009-01-01 09:00 ansi_cprng.ko
-rw-r--r-- root root 128788 2009-01-01 09:00 core_ctl.ko
-rw-r--r-- root root 8736 2009-01-01 09:00 dma_test.ko
-rw-r--r-- root root 6400 2009-01-01 09:00 evbug.ko
-rw-r--r-- root root 6592 2009-01-01 09:00 gpio_axis.ko
-rw-r--r-- root root 7216 2009-01-01 09:00 gpio_event.ko
-rw-r--r-- root root 9712 2009-01-01 09:00 gpio_input.ko
-rw-r--r-- root root 10648 2009-01-01 09:00 gpio_matrix.ko
-rw-r--r-- root root 4200 2009-01-01 09:00 gpio_output.ko
-rw-r--r-- root root 228528 2009-01-01 09:00 isdbt.ko
-rw-r--r-- root root 43304 2009-01-01 09:00 mcDrvModule.ko
-rw-r--r-- root root 20608 2009-01-01 09:00 mcKernelApi.ko
-rw-r--r-- root root 47104 2009-01-01 09:00 mmc_block_test.ko
-rw-r--r-- root root 36916 2009-01-01 09:00 mmc_test.ko
-rw-r--r-- root root 44852 2009-01-01 09:00 oprofile.ko
drwxr-xr-x root root 2009-01-01 09:00 pronto
-rw-r--r-- root root 18088 2009-01-01 09:00 spidev.ko
-rw-r--r-- root root 28816 2009-01-01 09:00 test-iosched.ko
lrw-r--r-- root root 2009-01-01 09:00 wlan.ko -> /system/lib/mo
dules/pronto/pronto_wlan.ko
Code:
su -c insmod /system/lib/modules/wlan.ko
Click to expand...
Click to collapse
D:\ADB>adb shell su -c insmod /system/lib/modules/wlan.ko
insmod: failed to load /system/lib/modules/wlan.ko: File exists
wizard-dima said:
D:\ADB>adb shell su -c insmod /system/lib/modules/wlan.ko
insmod: failed to load /system/lib/modules/wlan.ko: File exists
Click to expand...
Click to collapse
I should have mentioned this, I need that output withe ElementalX installed.
flar2 said:
I should have mentioned this, I need that output withe ElementalX installed.
Click to expand...
Click to collapse
Sorry, WiFi works.
The problem was that during the first installation I did not have root access.
For the team of your su needed the right, so that's posleh their installation, with no WiFi key problems.
I think it is necessary to specify in the instructions, and a large red font)
wizard-dima said:
Sorry, WiFi works.
The problem was that during the first installation I did not have root access.
For the team of your su needed the right, so that's posleh their installation, with no WiFi key problems.
I think it is necessary to specify in the instructions, and a large red font)
Click to expand...
Click to collapse
Thanks for the head's up.
So without root, no wifi.
I'll see if I can fix that.
on the standard firmware, the phone spends too much charge in sleep mode. You can it somehow fix it?
I don't think I can get the wifi module to load without root.
The problem is I need to mount an image at /system/lib/modules but selinux won't allow it. It is only possible with SuperSu installed unless somebody knows how to modify sepolicy without SuperSU.
wizard-dima said:
on the standard firmware, the phone spends too much charge in sleep mode. You can it somehow fix it?
Click to expand...
Click to collapse
I'm not sure what you mean?
flar2 said:
I'm not sure what you mean?
Click to expand...
Click to collapse
You can add doubletap2wake?
wizard-dima said:
You can add doubletap2wake?
Click to expand...
Click to collapse
I don't know. I think it might cause battery drain on this device. There also isn't a big need for it since the fingerprint sensor is on the front and wakes up the device (at least on the G4 Plus)
working perfectly..thanks bro.
WiFi working ..now i can able to use finger print sensor as home button..thank very much bro..
Moto G4 plus
XT1643
BUILD- MPJ24.139-23.1
LSMOD OUTPUT
Module Size Used by
wlan 4215738 0
core_ctl 20182 0
qdrbg_module 30626 0
qcrypto_module 145880 0

Teamviewer Quicksupport on LineageOS?

How do I get Teamviewer Quicksupport to run on LineageOS, so that I can remote control the device from a PC?
With Samsung and original OS it is no problem, but I would like to know if it is also possible on Lineage.
Thank you in advance
Nexxus23 said:
How do I get Teamviewer Quicksupport to run on LineageOS, so that I can remote control the device from a PC?
With Samsung and original OS it is no problem, but I would like to know if it is also possible on Lineage.
Thank you in advance
Click to expand...
Click to collapse
Yes
ok, and how?
where do I get the matching Teamviewer Quicksupport Add-on .apk ?
anybody?
unfortunately the QS Add-on does not work on LOS.
https://community.teamviewer.com/t5...d-add-on-app-quot-Out-of-space-quot/td-p/3161
in this case the issue is certainly that you're running on LineageOS, which, as mentioned above, is not supported at all for the Add-Ons.
The Add-Ons are only supported on the official, unrooted, stock firmware of the respective mobile device.
Click to expand...
Click to collapse
I Am Running (Lineage 14) Resurrection Remix 5.8.5 [Unofficial] [Flash Kernel] on One Plus 5.
After A Bit Of Digging Around The Net, I Found A Fix, Which Works.
**USE ROOT EXPLORER OR ES FILE EXPLORER [Any File Manager Capable Of Setting Folder & File Permissions]**
1. After TeamViewer downloads the QS Addon APK, retrieve it from Internal Storage/Android/data/com.teamviewer.host.market/files/Download/TeamViewerQSAddon.apk
2. Create a folder in /system/app/ or /system/priv-app/ named TeamViewerQSAddon with "rwx r-x r-x" [OCTAL - 0755] [I Created BOTH]
3. Put the APK in the folder(s) and change its permissions to "rw- r-- r--" [OCTAL - 0644]
4. Reboot Phone
[NOTE: In case Of Using ROOT Explorer, There May Be A Case Where It Wont Allow The Creation Of The Folder Inside /system/app/ OR /system/priv-app, In This case, Just Create The Folder Elsewhere and Copy It There, After The Copy, Change The Permission]
Thanks To "le-isis" Who Originally Posted The FIX.
Original REDDIT Link : https://www.reddit.com/r/teamviewer...oid_app_not_installed_when_trying_to_install/
Hmmm, on my device Teamviewer doesn't download the Quicksupport but sends me to the Playstore instead. So there is no Internal Storage/Android/data/com.teamviewer.host.market/files/Download/TeamViewerQSAddon.apk afterwards.
What can I do?
tosho1 said:
Hmmm, on my device Teamviewer doesn't download the Quicksupport but sends me to the Playstore instead. So there is no Internal Storage/Android/data/com.teamviewer.host.market/files/Download/TeamViewerQSAddon.apk afterwards.
What can I do?
Click to expand...
Click to collapse
Try downloading the APK directly from the Teamviewer website (personally I haven't test it): https://download.teamviewer.com/download/TeamViewerQS.apk
Thanks.
I'll try that when I've got some time.
tosho1 said:
Thanks.
I'll try that when I've got some time.
Click to expand...
Click to collapse
Sorry, that doesn't work for me.
I copied the folder to /system/app and /system/priv-app.
Still Teamviewer sends me to the playstore for the QS app and when it starts there's still this finger and I cannot do anything except pointing to things with that finger.
Maybe they have changed how things work...
Thanks [email protected]
The solution works on Samsung Galaxy J3 SM-J320FN with Lineage 14.1.
I've set permissions:
for directory -> drwxr-xr-x 755, Owner: 0: root, Group: 0: root
for file -> -rw-r - r-- 644, Owner: 0: root, Group: 0: root
After restarting the phone, the permissions changed to:
for directory -> drwxr-xr-x 755, Owner: 0: root, Group: 0: root
for file -> -rw-r - r-- 644, Owner: 10069: app_69, Group: 1015: sdcard_rw
In the /Android/data/com.teamviewer.host.market/files/Download/ directory you can delete all downloaded duplicate APK files.
TeamViewr Host is working properly.
Works on Fire HD 10 2017 with lineage OS 12.1
Thank you
jaco777 said:
Thanks [email protected]
The solution works on Samsung Galaxy J3 SM-J320FN with Lineage 14.1.
I've set permissions:
for directory -> drwxr-xr-x 755, Owner: 0: root, Group: 0: root
for file -> -rw-r - r-- 644, Owner: 0: root, Group: 0: root
After restarting the phone, the permissions changed to:
for directory -> drwxr-xr-x 755, Owner: 0: root, Group: 0: root
for file -> -rw-r - r-- 644, Owner: 10069: app_69, Group: 1015: sdcard_rw
In the /Android/data/com.teamviewer.host.market/files/Download/ directory you can delete all downloaded duplicate APK files.
TeamViewr Host is working properly.
Click to expand...
Click to collapse
Hi, I cannot get this to work although I created the system folder, copied the latest QuickSupport-APK into it and changed the rights with Total Commander. It start, I can get access to the phone via QS, but only get the "screenshot" option which is useless, but not remote control. Any other app would be helpful as well which allows remote control. Thanks for any help.

Themes / Apps / Mods [MOD/magisk/root] GoogleWiz - my magical Magisk module (for devs/sharing !!!)

I'm posting this here for the benefit of the (developer) community.
Attached is my personal "magical" Magisk module for P6P.
I strongly suggest that you DO NOT INSTALL this ... first read below ... If you don't understand what is written below, stop reading and go back playing with your phone ;-)
What is this module doing:
- it "hides" a lot (> 80) of system APKs which I do not use (e.g. NFC, Pixel Tips, Security Hub, MusicFX, ...) - so these literally "disappear" from your phone (Magisk hiding); this works by "bind-mounting" an empty directory over the APKs' file system
- it has a bash shell for "su"
- ad blocking (hosts file, mounted as /etc/hosts)
- it has a series of init.d (mounted as /etc/init.d) and service.d (mounted as /etc/services.d) scripts that do various things (e.g. kernel tuning, disable various debugging, disable swap, run sqlite optimizer, charling limit, ext4 tweaks ...), some things will NOT be relevant to you (e.g. there are scripts that install obf maps for OSMAND)
- a number of binaries (e.g. bash, busybox, xmlstarlet, find, (g)parted, ...)
- a number of scripts (mounted in /system/bin) for my personal usage (e.g. a script to make all my settings "stick")
- enables VoLTE (check properties in system.prop file)
So, you need to unzip this module and check the stuff inside, modify as per your liking !!!
This module is a (long lived) decendent from an old (2018) Magisk based ROM on Galaxy S8 (https://forum.xda-developers.com/t/...iz-pixelize-your-s8-end-of-life-crj5.3750641/). That ROM was quite popular as it turned the Galaxy S8 into a Pixel like phone. For me personally it was a journey to learn how to develop Magisk modules and gradually became bigger and bigger ...
You CAN install it ... but it may NOT be to your liking (!!!) ... then just uninstall it from Magisk ... no harm done (except that you will have my settings) - check out the script LS99execonce to understand this
Devs: feel free to (re)use for whatever purpose ... sharing for the benefit of the community ... if you do use it, no need to mention me (but you can of course) ;-)
Most of the code is "sh" scripting (and a few "bash" scripts).
If you do run it, there will be logging info in /data/googlewiz, just do:
Code:
> adb shell
$ su
# cat /data/googlewiz/*
... and
# cat /data/LS00* (init.d scripts logging)
# cat /data/LS99* (services.d scripts logging)
Hopefully some of this can help you in developing your own magisk module.
Which file in your module lists which app get disabled/hidden?
I would prefer to go through them manually first
Unzip the module, then check all the directories which have an ".replace" file, e.g. on linux do:
Code:
> cd mydir
> unzip googlewiz.zip
> find . -name '.replace'
That wil show you the paths of the APKs which are hidden.
Sorry, I'm not a Windows guy ...
This is the list:
Code:
./system/product/app/YouTubeMusicPrebuilt/.replace
./system/product/app/SoundAmplifierPrebuilt/.replace
./system/product/app/VoiceAccessPrebuilt/.replace
./system/product/app/SafetyRegulatoryInfo/.replace
./system/product/app/PixelWallpapers2021/.replace
./system/product/app/talkback/.replace
./system/product/app/Videos/.replace
./system/product/app/VZWAPNLib/.replace
./system/product/app/DiagnosticsToolPrebuilt/.replace
./system/product/app/LocationHistoryPrebuilt/.replace
./system/product/app/MicropaperPrebuilt/.replace
./system/product/overlay/DisplayCutoutEmulationCorner/.replace
./system/product/overlay/CellBroadcastServiceOverlay/.replace
./system/product/overlay/CellBroadcastReceiverOverlay/.replace
./system/product/overlay/NavigationBarModeGesturalExtraWideBack/.replace
./system/product/overlay/DisplayCutoutAvoidAppsInCutout/.replace
./system/product/overlay/DisplayCutoutNoCutout/.replace
./system/product/overlay/FontNotoSerifSource/.replace
./system/product/overlay/NavigationBarModeGesturalNarrowBack/.replace
./system/product/overlay/OneHandedModeGestural/.replace
./system/product/overlay/NavigationBarModeGesturalWideBack/.replace
./system/product/overlay/NavigationBarMode3Button/.replace
./system/product/overlay/DisplayCutoutEmulationDouble/.replace
./system/product/overlay/DisplayCutoutEmulationWaterfall/.replace
./system/product/overlay/DisplayCutoutEmulationTall/.replace
./system/product/overlay/DisplayCutoutEmulationHole/.replace
./system/product/priv-app/Showcase/.replace
./system/product/priv-app/HotwordEnrollmentXGoogleFUSION/.replace
./system/product/priv-app/ScribePrebuilt/.replace
./system/product/priv-app/OTAConfigNoZeroTouchPrebuilt/.replace
./system/product/priv-app/OemDmTrigger/.replace
./system/product/priv-app/BetterBug/.replace
./system/product/priv-app/PartnerSetupPrebuilt/.replace
./system/product/priv-app/PixelLiveWallpaperPrebuilt/.replace
./system/product/priv-app/HelpRtcPrebuilt/.replace
./system/product/priv-app/DCMO/.replace
./system/product/priv-app/TipsPrebuilt/.replace
./system/product/priv-app/DreamlinerPrebuilt/.replace
./system/product/priv-app/AppDirectedSMSService/.replace
./system/product/priv-app/ConnMO/.replace
./system/product/priv-app/SafetyHubPrebuilt/.replace
./system/product/priv-app/CbrsNetworkMonitor/.replace
./system/product/priv-app/WellbeingPrebuilt/.replace
./system/product/priv-app/MaestroPrebuilt/.replace
./system/product/priv-app/CarrierMetrics/.replace
./system/product/priv-app/DiagMon/.replace
./system/product/priv-app/DreamlinerUpdater/.replace
./system/product/priv-app/DMService/.replace
./system/product/priv-app/HotwordEnrollmentOKGoogleFUSION/.replace
./system/app/GooglePrintRecommendationService/.replace
./system/app/PacProcessor/.replace
./system/app/BasicDreams/.replace
./system/app/NfcNci/.replace
./system/app/EasterEgg/.replace
./system/app/PartnerBookmarksProvider/.replace
./system/app/BookmarkProvider/.replace
./system/app/WallpaperBackup/.replace
./system/app/LiveWallpapersPicker/.replace
./system/app/BluetoothMidiService/.replace
./system/app/HTMLViewer/.replace
./system/system_ext/app/EmergencyInfoGoogleNoUi/.replace
./system/system_ext/priv-app/GoogleFeedback/.replace
./system/system_ext/priv-app/QuickAccessWallet/.replace
./system/system_ext/priv-app/MyVerizonServices/.replace
./system/system_ext/priv-app/obdm_stub/.replace
./system/system_ext/priv-app/StorageManagerGoogle/.replace
./system/system_ext/priv-app/WallpaperPickerGoogleRelease/.replace
./system/system_ext/priv-app/OBDM_Permissions/.replace
./system/system_ext/priv-app/LLKAgent/.replace
./system/system_ext/priv-app/PixelNfc/.replace
./system/priv-app/BuiltInPrintService/.replace
./system/priv-app/Traceur/.replace
./system/priv-app/LocalTransport/.replace
./system/priv-app/ManagedProvisioning/.replace
./system/priv-app/AppDirectedSMSService/.replace
./system/priv-app/TagGoogle/.replace
./system/priv-app/CellBroadcastLegacyApp/.replace
./system/priv-app/CallLogBackup/.replace
./system/priv-app/SharedStorageBackup/.replace
./system/priv-app/MmsService/.replace
./system/priv-app/MusicFX/.replace
./system/priv-app/BackupRestoreConfirmation/.replace
foobar66 said:
Unzip the module, then check all the directories which have an ".replace" file, e.g. on linux do:
Code:
> cd mydir
> unzip googlewiz.zip
> find . -name '.replace'
That wil show you the paths of the APKs which are hidden.
Sorry, I'm not a Windows guy ...
This is the list:
Code:
./system/product/app/YouTubeMusicPrebuilt/.replace
./system/product/app/SoundAmplifierPrebuilt/.replace
./system/product/app/VoiceAccessPrebuilt/.replace
./system/product/app/SafetyRegulatoryInfo/.replace
./system/product/app/PixelWallpapers2021/.replace
./system/product/app/talkback/.replace
./system/product/app/Videos/.replace
./system/product/app/VZWAPNLib/.replace
./system/product/app/DiagnosticsToolPrebuilt/.replace
./system/product/app/LocationHistoryPrebuilt/.replace
./system/product/app/MicropaperPrebuilt/.replace
./system/product/overlay/DisplayCutoutEmulationCorner/.replace
./system/product/overlay/CellBroadcastServiceOverlay/.replace
./system/product/overlay/CellBroadcastReceiverOverlay/.replace
./system/product/overlay/NavigationBarModeGesturalExtraWideBack/.replace
./system/product/overlay/DisplayCutoutAvoidAppsInCutout/.replace
./system/product/overlay/DisplayCutoutNoCutout/.replace
./system/product/overlay/FontNotoSerifSource/.replace
./system/product/overlay/NavigationBarModeGesturalNarrowBack/.replace
./system/product/overlay/OneHandedModeGestural/.replace
./system/product/overlay/NavigationBarModeGesturalWideBack/.replace
./system/product/overlay/NavigationBarMode3Button/.replace
./system/product/overlay/DisplayCutoutEmulationDouble/.replace
./system/product/overlay/DisplayCutoutEmulationWaterfall/.replace
./system/product/overlay/DisplayCutoutEmulationTall/.replace
./system/product/overlay/DisplayCutoutEmulationHole/.replace
./system/product/priv-app/Showcase/.replace
./system/product/priv-app/HotwordEnrollmentXGoogleFUSION/.replace
./system/product/priv-app/ScribePrebuilt/.replace
./system/product/priv-app/OTAConfigNoZeroTouchPrebuilt/.replace
./system/product/priv-app/OemDmTrigger/.replace
./system/product/priv-app/BetterBug/.replace
./system/product/priv-app/PartnerSetupPrebuilt/.replace
./system/product/priv-app/PixelLiveWallpaperPrebuilt/.replace
./system/product/priv-app/HelpRtcPrebuilt/.replace
./system/product/priv-app/DCMO/.replace
./system/product/priv-app/TipsPrebuilt/.replace
./system/product/priv-app/DreamlinerPrebuilt/.replace
./system/product/priv-app/AppDirectedSMSService/.replace
./system/product/priv-app/ConnMO/.replace
./system/product/priv-app/SafetyHubPrebuilt/.replace
./system/product/priv-app/CbrsNetworkMonitor/.replace
./system/product/priv-app/WellbeingPrebuilt/.replace
./system/product/priv-app/MaestroPrebuilt/.replace
./system/product/priv-app/CarrierMetrics/.replace
./system/product/priv-app/DiagMon/.replace
./system/product/priv-app/DreamlinerUpdater/.replace
./system/product/priv-app/DMService/.replace
./system/product/priv-app/HotwordEnrollmentOKGoogleFUSION/.replace
./system/app/GooglePrintRecommendationService/.replace
./system/app/PacProcessor/.replace
./system/app/BasicDreams/.replace
./system/app/NfcNci/.replace
./system/app/EasterEgg/.replace
./system/app/PartnerBookmarksProvider/.replace
./system/app/BookmarkProvider/.replace
./system/app/WallpaperBackup/.replace
./system/app/LiveWallpapersPicker/.replace
./system/app/BluetoothMidiService/.replace
./system/app/HTMLViewer/.replace
./system/system_ext/app/EmergencyInfoGoogleNoUi/.replace
./system/system_ext/priv-app/GoogleFeedback/.replace
./system/system_ext/priv-app/QuickAccessWallet/.replace
./system/system_ext/priv-app/MyVerizonServices/.replace
./system/system_ext/priv-app/obdm_stub/.replace
./system/system_ext/priv-app/StorageManagerGoogle/.replace
./system/system_ext/priv-app/WallpaperPickerGoogleRelease/.replace
./system/system_ext/priv-app/OBDM_Permissions/.replace
./system/system_ext/priv-app/LLKAgent/.replace
./system/system_ext/priv-app/PixelNfc/.replace
./system/priv-app/BuiltInPrintService/.replace
./system/priv-app/Traceur/.replace
./system/priv-app/LocalTransport/.replace
./system/priv-app/ManagedProvisioning/.replace
./system/priv-app/AppDirectedSMSService/.replace
./system/priv-app/TagGoogle/.replace
./system/priv-app/CellBroadcastLegacyApp/.replace
./system/priv-app/CallLogBackup/.replace
./system/priv-app/SharedStorageBackup/.replace
./system/priv-app/MmsService/.replace
./system/priv-app/MusicFX/.replace
./system/priv-app/BackupRestoreConfirmation/.replace
Click to expand...
Click to collapse
Np, I am a Linux user too
And you are sure that you can safely disable all that stuff?
I see several packages that I had disabled in AFWall+ and I noticed that some things got broken.
Utini said:
Np, I am a Linux user too
And you are sure that you can safely disable all that stuff?
I see several packages that I had disabled in AFWall+ and I noticed that some things got broken.
Click to expand...
Click to collapse
I don't have broken things. But I don't use certain things either, e.g. NFC, one handed mode, pixel tips, live wallpapers, eSIM ... all of these (and more) I have disabled ... but you have to judge for yourself!!!
I probably won't be using this, but this is awesome. I've done similar for one of my very old LG phones and tablets. More of the traditional bloatware, that is.
Like you, I've been disabling all of those same apks, pretty much every one you disabled except for NFC for the rare time I actually use it. I've done that probably for the last ten years on all my devices. You do see a slight speed increase and maybe some better battery life by disabling all of those. On my S21 Ultra I think I had about 135 apk's disabled. Great module.
Hello from Germany...
One of these settings prevents the correct display for some apps.
Here is an example from SwiftKey.
Do you know which one it could be?
In the first picture googlewiz is switched off.
The second one shows the different colors on the same keyboard.
In the third picture you can no longer see the enter button.
It seems to be something about black and white.
If I switch off dark mode with googlewiz switched on, it works without any problems.
greetz
V-Ripper said:
Here is an example from SwiftKey.
Click to expand...
Click to collapse
Hmmm ... could either be the (a) force dark setting or (b) the gesture pill removal (overlay).
Try the following:
Code:
> adb shell
$ su
# cmd overlay disable com.android.shell:NavBarFrameHeightOverlay
Then check SwiftKey again. Please report if OK or not.
I've been using this for a couple of days now & seems to be working brilliantly, thanks @foobar66!
I have highly modified the package to fit my usage - I have removed: adblocking (as I use adaway), your personal settings, the charge limit, some binaries & I have unfrozen some system apks, etc.
The module still is freezing 37 system apks & is also still running: block dev tweaks, ext4 tweaks, kernel tweaks, scheduling tweaks, swap off script, no log script, stop daemon script & swapiness script.
Everything seems to be running very well! I especially love the green "[email protected]" instead of "raven" when using shell
DanielF50 said:
Everything seems to be running very well! I especially love the green "[email protected]" instead of "raven" when using shell
Click to expand...
Click to collapse
Simple bash prompt ;-);-)
Actually, the hosts file in the magisk module is an (old) version of the AdAway one ...
Below is my most recent list of 'hidden' APKs (stuff that I don't use) ... but please check for yourself.
Code:
/system/app/BasicDreams/BasicDreams.apk
/system/app/BluetoothMidiService/BluetoothMidiService.apk
/system/app/BookmarkProvider/BookmarkProvider.apk
/system/app/CompanionDeviceManager/CompanionDeviceManager.apk
/system/app/EasterEgg/EasterEgg.apk
/system/app/GooglePrintRecommendationService/GooglePrintRecommendationService.apk
/system/app/HTMLViewer/HTMLViewer.apk
/system/app/LiveWallpapersPicker/LiveWallpapersPicker.apk
/system/app/NfcNci/NfcNci.apk
/system/app/PacProcessor/PacProcessor.apk
/system/app/PartnerBookmarksProvider/PartnerBookmarksProvider.apk
/system/app/SimAppDialog/SimAppDialog.apk
/system/app/Stk/Stk.apk
/system/app/WallpaperBackup/WallpaperBackup.apk
/system/priv-app/BackupRestoreConfirmation/BackupRestoreConfirmation.apk
/system/priv-app/BuiltInPrintService/BuiltInPrintService.apk
/system/priv-app/CallLogBackup/CallLogBackup.apk
/system/priv-app/CellBroadcastLegacyApp/CellBroadcastLegacyApp.apk
/system/priv-app/InputDevices/InputDevices.apk
/system/priv-app/LocalTransport/LocalTransport.apk
/system/priv-app/ManagedProvisioning/ManagedProvisioning.apk
/system/priv-app/MmsService/MmsService.apk
/system/priv-app/MtpService/MtpService.apk
/system/priv-app/MusicFX/MusicFX.apk
/system/priv-app/SharedStorageBackup/SharedStorageBackup.apk
/system/priv-app/TagGoogle/TagGoogle.apk
/system/priv-app/Traceur/Traceur.apk
/product/app/DiagnosticsToolPrebuilt/DiagnosticsToolPrebuilt.apk
/product/app/DevicePolicyPrebuilt/DevicePolicyPrebuilt.apk
/product/app/LocationHistoryPrebuilt/LocationHistoryPrebuilt.apk
/product/app/MicropaperPrebuilt/MicropaperPrebuilt.apk
/product/app/PixelWallpapers2021/PixelWallpapers2021.apk
/product/app/SafetyRegulatoryInfo/SafetyRegulatoryInfo.apk
/product/app/SoundAmplifierPrebuilt/SoundAmplifierPrebuilt.apk
/product/app/SSRestartDetector/SSRestartDetector.apk
/product/app/talkback/talkback.apk
/product/app/Videos/Videos.apk
/product/app/VZWAPNLib/VZWAPNLib.apk
/product/app/VoiceAccessPrebuilt/VoiceAccessPrebuilt.apk
/product/app/YouTubeMusicPrebuilt/YouTubeMusicPrebuilt.apk
/product/priv-app/AppDirectedSMSService/AppDirectedSMSService.apk
/product/priv-app/BetterBug/BetterBug.apk
/product/priv-app/CarrierMetrics/CarrierMetrics.apk
/product/priv-app/CarrierWifi/CarrierWifi.apk
/product/priv-app/CbrsNetworkMonitor/CbrsNetworkMonitor.apk
/product/priv-app/ConnMO/ConnMO.apk
/product/priv-app/DCMO/DCMO.apk
/product/priv-app/DiagMon/DiagMon.apk
/product/priv-app/DMService/DMService.apk
/product/priv-app/DreamlinerPrebuilt/DreamlinerPrebuilt.apk
/product/priv-app/DreamlinerUpdater/DreamlinerUpdater.apk
/product/priv-app/EuiccGoogle/EuiccGoogle.apk
/product/priv-app/GoogleOneTimeInitializer/GoogleOneTimeInitializer.apk
/product/priv-app/GoogleRestorePrebuilt/GoogleRestorePrebuilt.apk
/product/priv-app/HelpRtcPrebuilt/HelpRtcPrebuilt.apk
/product/priv-app/HotwordEnrollmentOKGoogleFUSION/HotwordEnrollmentOKGoogleFUSION.apk
/product/priv-app/HotwordEnrollmentXGoogleFUSION/HotwordEnrollmentXGoogleFUSION.apk
/product/priv-app/Iwlan/Iwlan.apk
/product/priv-app/MaestroPrebuilt/MaestroPrebuilt.apk
/product/priv-app/OemDmTrigger/OemDmTrigger.apk
/product/priv-app/OTAConfigNoZeroTouchPrebuilt/OTAConfigNoZeroTouchPrebuilt.apk
/product/priv-app/PartnerSetupPrebuilt/PartnerSetupPrebuilt.apk
/product/priv-app/PixelLiveWallpaperPrebuilt/PixelLiveWallpaperPrebuilt.apk
/product/priv-app/SafetyHubPrebuilt/SafetyHubPrebuilt.apk
/product/priv-app/SCONE/SCONE.apk
/product/priv-app/ScribePrebuilt/ScribePrebuilt.apk
/product/priv-app/SetupWizardPrebuilt/SetupWizardPrebuilt.apk
/product/priv-app/Showcase/Showcase.apk
/product/priv-app/TipsPrebuilt/TipsPrebuilt.apk
/product/priv-app/WellbeingPrebuilt/WellbeingPrebuilt.apk
/product/overlay/CellBroadcastReceiverOverlay/CellBroadcastReceiverOverlay.apk
/product/overlay/CellBroadcastServiceOverlay/CellBroadcastServiceOverlay.apk
/product/overlay/DisplayCutoutAvoidAppsInCutout/AvoidAppsInCutoutOverlay.apk
/product/overlay/DisplayCutoutEmulationCorner/DisplayCutoutEmulationCornerOverlay.apk
/product/overlay/DisplayCutoutEmulationDouble/DisplayCutoutEmulationDoubleOverlay.apk
/product/overlay/DisplayCutoutEmulationHole/DisplayCutoutEmulationHoleOverlay.apk
/product/overlay/DisplayCutoutEmulationTall/DisplayCutoutEmulationTallOverlay.apk
/product/overlay/DisplayCutoutEmulationWaterfall/DisplayCutoutEmulationWaterfallOverlay.apk
/product/overlay/DisplayCutoutNoCutout/NoCutoutOverlay.apk
/product/overlay/FontNotoSerifSource/FontNotoSerifSourceOverlay.apk
/product/overlay/NavigationBarMode3Button/NavigationBarMode3ButtonOverlay.apk
/product/overlay/NavigationBarModeGesturalExtraWideBack/NavigationBarModeGesturalOverlayExtraWideBack.apk
/product/overlay/NavigationBarModeGesturalNarrowBack/NavigationBarModeGesturalOverlayNarrowBack.apk
/product/overlay/NavigationBarModeGesturalWideBack/NavigationBarModeGesturalOverlayWideBack.apk
/product/overlay/OneHandedModeGestural/OneHandedModeGesturalOverlay.apk
/product/overlay/BuiltInPrintService__auto_generated_rro_product.apk
/product/overlay/NfcNci__auto_generated_rro_product.apk
/product/overlay/Traceur__auto_generated_rro_product.apk
/product/overlay/SafetyRegulatoryInfo__auto_generated_rro_product.apk
/product/overlay/ManagedProvisioningPixelOverlay.apk
/product/overlay/SettingsOverlayGLU0G.apk
/product/overlay/PixelSetupWizardOverlay.apk
/product/overlay/PixelSetupWizardOverlay2019.apk
/product/overlay/PixelSetupWizard__auto_generated_rro_product.apk
/product/overlay/SimAppDialog__auto_generated_rro_product.apk
/system_ext/app/EmergencyInfoGoogleNoUi/EmergencyInfoGoogleNoUi.apk
/system_ext/priv-app/EuiccSupportPixel/EuiccSupportPixel.apk
/system_ext/priv-app/EuiccSupportPixelPermissions/EuiccSupportPixelPermissions.apk
/system_ext/priv-app/GoogleFeedback/GoogleFeedback.apk
/system_ext/priv-app/LLKAgent/LLKAgent.apk
/system_ext/priv-app/MyVerizonServices/MyVerizonServices.apk
/system_ext/priv-app/OBDM_Permissions/OBDM_Permissions.apk
/system_ext/priv-app/obdm_stub/obdm_stub.apk
/system_ext/priv-app/PixelNfc/PixelNfc.apk
/system_ext/priv-app/PixelSetupWizard/PixelSetupWizard.apk
/system_ext/priv-app/QuickAccessWallet/QuickAccessWallet.apk
/system_ext/priv-app/ShannonRcs/ShannonRcs.apk
/system_ext/priv-app/StorageManagerGoogle/StorageManagerGoogle.apk
/system_ext/priv-app/UwbService/UwbService.apk
/system_ext/priv-app/WallpaperPickerGoogleRelease/WallpaperPickerGoogleRelease.apk
/vendor/overlay/NfcNci__auto_generated_rro_vendor.apk
/vendor/overlay/Traceur__auto_generated_rro_vendor.apk
DanielF50 said:
I've been using this for a couple of days now & seems to be working brilliantly, thanks @foobar66!
I have highly modified the package to fit my usage - I have removed: adblocking (as I use adaway), your personal settings, the charge limit, some binaries & I have unfrozen some system apks, etc.
The module still is freezing 37 system apks & is also still running: block dev tweaks, ext4 tweaks, kernel tweaks, scheduling tweaks, swap off script, no log script, stop daemon script & swapiness script.
Everything seems to be running very well! I especially love the green "[email protected]" instead of "raven" when using shell
Click to expand...
Click to collapse
Bye the way, if you do:
Code:
> adb shell
$ su
# gset mysettings
You will have a txt file /sdcard/mysettings ... if reflects your settings in {global/system/secure} namespace. If you ever need to reinstall your pone you can just command line 'source' that file to restore your settings.
Code:
> adb shell
$ su
# source /sdcard/mysettings
But please note that not all settings form the Settings app are stored in those namespaces! So it's not a 100% restore.
And ... bye the way ... you can check log files from the 2 main Magisk scripts (post-fs-data.sh and service.sh):
Code:
> adb shell
$ su
# data /data/googlewiz/*
The log files for the /etc/init.d/ scripts:
Code:
# cat /data/LS00*
And the log files for the /etc/services.d/ scripts:
Code:
# cat /data/LS99*
Wait, EXT4 tweaks? I thought we only had F2FS?
Nope ... mostly system/ro file systems on ext4/
I have not checked lately how relevant the ext4 tweaks still are ... come from a long history since the Galaxy S4 (lol).
Anyway ...
Code:
# ls -l /sys/fs/ext4/
# ls -l /sys/fs/f2fs/
F2FS for /data (of couse) since there is writing there.
And check /etc/vendor/fstab.*
Code:
system /system ext4 ro,barrier=1 wait,slotselect,avb=vbmeta_system,logical,first_st
age_mount,readahead_size_kb=128
system_ext /system_ext ext4 ro,barrier=1 wait,slotselect,avb=vbmeta_system,logical,first_st
age_mount
product /product ext4 ro,barrier=1 wait,slotselect,avb=vbmeta_system,logical,first_st
age_mount
vendor /vendor ext4 ro,barrier=1 wait,slotselect,avb=vbmeta_vendor,logical,first_st
age_mount
vendor_dlkm /vendor_dlkm ext4 ro,barrier=1 wait,slotselect,avb=vbmeta,logical,first_stage_mou
nt
/dev/block/platform/14700000.ufs/by-name/boot /boot emmc defaults slotselect,avb=boot,first_stage_mount
/dev/block/platform/14700000.ufs/by-name/efs /mnt/vendor/efs ext4 defaults,noatime,rw wait,check,formattable
/dev/block/platform/14700000.ufs/by-name/efs_backup /mnt/vendor/efs_backup ext4 defaults,noatime,rw wait,check,formattable
/dev/block/platform/14700000.ufs/by-name/modem_userdata /mnt/vendor/modem_userdata ext4 defaults,noatime,rw wait,check,formattable
/dev/block/platform/14700000.ufs/by-name/modem /mnt/vendor/modem_img ext4 ro,defaults,context=u:object_r:modem_img_file:s0,barrier=1 wait,slotsele
ct
/dev/block/platform/14700000.ufs/by-name/misc /misc emmc defaults wait
/dev/block/platform/14700000.ufs/by-name/metadata /metadata ext4 noatime,nosuid,nodev,data=journal,commit=1 wait,check,formattable,first_
stage_mount,metadata_csum
/dev/block/platform/14700000.ufs/by-name/pvmfw /pvmfw emmc defaults wait,slotselect,avb=pvmfw,first_stage_mount
/dev/block/platform/14700000.ufs/by-name/userdata /data f2fs noatime,nosuid,nodev,discard,reserve_root=32768,resgid=1065,fsync_mode=noba
rrier,inlinecrypt,compress_extension=apk,compress_extension=apex,compress_extension=so,atgc,checkpoint_merge latemount,wait,check,quota,formattable,sysfs_path=/dev/s
ys/block/bootdevice,checkpoint=fs,reservedsize=128M,fileencryption=::inlinecrypt_optimized+wrappedkey_v0,metadata_encryption=:wrappedkey_v0,keydirectory=/metadata/vold/
metadata_encryption,fscompress,readahead_size_kb=128
/dev/block/platform/14700000.ufs/by-name/vbmeta /vbmeta emmc defaults slotselect,first_stage_mount
/dev/block/zram0 none swap defaults zramsize=3221225472,max_comp_streams=8,zram_backin
gdev_size=512M
/devices/platform/11110000.usb* auto vfat defaults voldmanaged=usb:auto
foobar66 said:
Simple bash prompt ;-);-)
Actually, the hosts file in the magisk module is an (old) version of the AdAway one ...
Click to expand...
Click to collapse
Ah yes, the app just gets new updated everyday so I use that to keep up-to-date
foobar66 said:
Bye the way, if you do:
But please note that not all settings form the Settings app are stored in those namespaces! So it's not a 100% restore.
Click to expand...
Click to collapse
Great info, thanks!
foobar66 said:
And ... bye the way ... you can check log files from the 2 main Magisk scripts (post-fs-data.sh and service.sh):
Click to expand...
Click to collapse
Yes, I used these commands to confirm which parts I was running
foobar66 said:
Hmmm ... could either be the (a) force dark setting or (b) the gesture pill removal (overlay).
Try the following:
Code:
> adb shell
$ su
# cmd overlay disable com.android.shell:NavBarFrameHeightOverlay
Then check SwiftKey again. Please report if OK or not.
Click to expand...
Click to collapse
Hello.
I'll try this tomorrow.
Should googlewiz be activated when trying?
V-Ripper said:
Hello.
I'll try this tomorrow.
Should googlewiz be activated when trying?
Click to expand...
Click to collapse
No because you are just disabling an overlay which is already there.
just a suggestion/feedback as someone who has self created modules that do some of the same things, plus over 30 years in IT:
way too many things in ONE script...personally i separate mine out, not least because you can identify points of failure far easier....
i know it seems a good idea to "everything at once", but it rarely is, and its an even worse idea when you choose to share it, its like trying to herd cats when trying to sort out user issues....
also golden rule of android #1:
never apply something which one person says works 100% and magically for them to your own device
case in point ive just left my S20+ 5G for pixel life again, and previously i had a debloat list (for use with a friends officially listed debloat magisk module) that had 169 package son it. For years i declined to give anyone my personal debloat list, because even with the disclaimer "this works for me, as i dont use any Samsung apps and replace them with Google ones, and never use device function you might" i just know some kiddie will blanket use it and then come crying when it all goes wrong, and i personally dont need that level of drama in my life. I did give my list to the 2 devs i respect and know will treat it carefully, but i would never give it to an end user...i wont even tell end users which packages i hide in magisk or other apps like Hide My Applist, because people just wont make the mental leap to consider things rationally and think for even 30 seconds, "this may be personal to him and wont work for me". Sad but true

Categories

Resources