[video] [Guide] enable WhatsApp calling feature.. any device (4.4+) - Android General

video link https://www.youtube.com/watch?v=8RlIxhEJEOw
STEPS:-Install the latest apk (Of course)
Open any root explorer (es file explorer preferred )
and navigate to /data/data/com.whatsapp/shared_prefs/com.whatsapp_preferences.xml
Add these 2 lines anywhere in the file but within the <map></map> and save
<boolean name="call" value="true" /> <string name="call_allowed">all</string>
now force stop WhatsApp and open it again .... and you are done
Not able to post kink but video id = 8RlIxhEJEOw
Edit if any one can post link then plz add that video...thanks

Seems no one interested

Seems like not working.
I got the call tab, but anyone I'm trying calling to, it's just getting disconnect immediately.
(all the people I tried have the updated version)

Related

[Q] Lock Screen xml?

Hope this isn't a double post.... I would like to change the lockscreen image to something other than the background of the phone. Maybe through editing the .xml file on the phone? etc. Anyone know of how to do this?
PS... PLEASSEEEEE don't reply with anything about widgetlocker. I know it exists I know it can do this but and I am not trying to nor do I want to use it for various reasons ...
Thanks in Advance.
-Adam
Here your are
had a little trouble with this, but here's a full guide that worked for me "tools used apk manager 4.9"
using the apk manager
1. pull /system/framework/framework-res.apk (option 0)
2. Decompile apk (option 9)
3. add your pic to drawable-mdpi (must be a .png) eg. lockscreen_background.png
4. open the file res\layout\keyguard_screen_tab_unlock.xml with notepad, and find the line
<RelativeLayout android:gravity="center_horizontal" android:id="@id/root" android:background="#70000000" android:layout_width="fill_parent" android:layout_height="fill_parent"
change to
<RelativeLayout android:gravity="center_horizontal" android:id="@id/root" android:background="@drawable/lockscreen_background" android:layout_width="fill_parent" android:layout_height="fill_parent"
5. compile the apk (option 9)
(when recompile do)
5.1. Hit yes to "system app".
5.2. Hit yes to restoring the files:
6. -Open the "keep" folder and delete resources.arsc and res\layout\keyguard_screen_tab_unlock.xml
7. when done rename unsignedframework-res.apk to framework-res.apk and put it back to /system/framework/ again (i did this in recovery)
Done
Awesome... Thanks.. Did you try this on the Droid X?
or can you change the lockscreen background to a dedicated image through ninjamorph? anyone have a quick tut on how to do this with a droid x?

[TIP] How to join more than 5 Contacts

Good day my dear friends,
There were a lot of questions about this matter, yet the only solution I found here apply for Galaxy SIII
So, for all of you who still didn't manage to have this feature, I come today with the solution.
I applied it in my Galaxy Grand Duos and it worked.
First, your device needs to be rooted.
Then, follow these steps:
1. Use root explorer (as R/W) to go to /system/csc/ and look for a file called features.xml. If you didn’t find it (I didn’t) then look for a file called others.xml.
2. You'll find The following code:
Code:
<?xml version="1.0" encoding="UTF-8" ?>
<SamsungMobileFeauture>
<FeatureSet>
</FeatureSet>
</SamsungMobileFeauture>
You might find some <CscFeature...> tags… just keep them.
3. Now right before the last two lines (before “</FeatureSet>“) add the following line:
Code:
<CscFeature_Contact_SetLinkCountMaxAs>[COLOR="red"]30[/COLOR]</CscFeature_Contact_SetLinkCountMaxAs>
Replace (30) with the number you want as a limit.
4. Save the file and restart.
Note: if you selected a different country other than USA, you'll have to go to the folder that represent your country inside /system/csc/ and repeat the steps 2-4 to the file feature.xml or others.xml inside it.
In my case, I'm from Saudi Arabia so I needed to go to /system/csc/KSA/system/csc and applied the changes to others.xml and it worked.
Thanks to l0uy blog
Thank you. It works, but...changing the number to anything bigger then 5 removes the contact's network icons (google, skype, facebook, etc)
Any solution for this?
Thanks.
Samsung Galaxy Note 2 with stock 4.1.2

GN3 Ac3 support mod by pako7 - update : found & working !

Hi everbody,
pako777 of 4pda.ru (pako7 on xda) was kind enough to send me his patch.
The original patch (as in this topic http://4pda.ru/forum/index.php?showtopic=503233&st=120#entry25623750) is attached to this thread.
As i found too many difference between my original media_codecs.xml and the one in the archive i've juste added these lines to /etc/media_codecs.xml (tagged by <!-- added AC3 support -->, other lines are fyi)
HTML:
<MediaCodec name="OMX.SEC.flac.dec" type="audio/flac" >
<Quirk name="needs-flush-before-disable" />
<Quirk name="decoder-ignores-streamcorrupt-error" />
</MediaCodec>
<!-- added AC3 support -->
<MediaCodec name="OMX.SEC.ac3.dec" type="audio/ac3" >
<Quirk name="needs-flush-before-disable" />
<Quirk name="decoder-ignores-streamcorrupt-error" />
</MediaCodec>
<!-- added AC3 support -->
<MediaCodec name="OMX.SEC.wma.dec" type="audio/x-ms-wma" >
<Quirk name="needs-flush-before-disable" />
<Quirk name="decoder-ignores-streamcorrupt-error" />
</MediaCodec>
Also copied the to .so files to /system/lib
I'm on rooted stock 4.4.2 XXUENB1
Cheers !
So this will add AC3 support to Note 3? got it!
Just a reminder, if you use ES file explorer (not sure about other file managers, don't use anything else), you need to change back file permissions for xml file and both lib files and reboot the phone for it to work.
pete4k said:
Just a reminder, if you use ES file explorer (not sure about other file managers, don't use anything else), you need to change back file permissions for xml file and both lib files and reboot the phone for it to work.
Click to expand...
Click to collapse
I just have to copy and paste these lines <MediaCodec name="OMX.SEC.ac3.dec" type="audio/ac3" > <Quirk name="needs-flush-before-disable" /> <Quirk name="decoder-ignores-streamcorrupt-error" /> </MediaCodec> bc all the other ones are already there so I just want to make sure.
copy the lines between "added AC3 Support" to mediacodecs.xml, copy 2 files to /system/lib, fix permissions for all 3 files, reboot
pete4k said:
copy the lines between "added AC3 Support" to mediacodecs.xml, copy 2 files to /system/lib, fix permissions for all 3 files, reboot
Click to expand...
Click to collapse
OK that's what I did but I didn't have to fix the permissions I had use rom toolbox with browser within that app. It works I didn't reboot but after I did that all is well.
I did this fix and now my youtube, watchESPN soundcloud, netflix, hangouts apps force close. The AC3 audio does work though. Any thoughts?
Factory reset did not fix the issue and AC3 audio is still playing. I guess the reset didn't undo the 'fix' .
AppleJuice3 said:
I did this fix and now my youtube, watchESPN soundcloud, netflix, hangouts apps force close. The AC3 audio does work though. Any thoughts?
Factory reset did not fix the issue and AC3 audio is still playing. I guess the reset didn't undo the 'fix' .
Click to expand...
Click to collapse
Youtube works fine on mine, I don't use other programs,
Double check permissions on the files you accessed, verify you didn't accidentally change anything else in xml file, restore original xml file, if all fails reload original firmware, after factory reset it shouldn't be that much more work.
I fixed it by reflashing. Didn't have the time to really get into it. Might experiment more this weekend.
I guess getting AC3 codecs working on their Note 3s isn't something that's important to a lot of people...sorry for bumping this thread, but I just wanted to let people know that it didn't work for me, but it didn't do anything bad either. I set the octet to 644 (I assume that's what you all meant by fix permissions, but let me know if I am wrong!) and put the three files in the right locations, but Plex, with AC3 turned on in the advanced options, still says "this device cannot play AC3"
So, it seems it isn't working, but it doesn't cause any apps to horse close/crash for me.
Hi could this work on any device?
Who are you asking ?? last post 2015 OP 2014 .
I thought someone was answering me. Since I was interested in my android box. I searched the forum is the only thing I found

Samsung S6 FACTORY Bootloader Unlocker apk and source

Got a hold of the Samsung CROM Service apk that unlocks the S6 SM-G9250 bootloader and I've decompiled it, I'll be honest, it's been years since I've looked at this stuff. The file is distributed by Samsung for the Chinese market It's been verified to install on American Devices but force closes immediately. I figure it's failing a version check or something along those lines.
I can pass it along if anyone wants to take a crack at it. I'll be muddling along on my end but my primary interest is in the results - not the credit.
Anyone interested?
Edit: I have TWO versions of the file,version 1.04 android:versionCode="20150408" and
version 1.01 android:versionCode="20141126", which I've attached below.
-----
Contents of S6 CROM Android Manifest xml file:
<?xml version="1.0" encoding="utf-8"?>
<manifest android:sharedUserId="android.uid.system" android:versionCode="20150408" android:versionName="1.0.4" package="com.sec.android.app.kwb"
xmlns:android="http://schemas.android.com/apk/res/android">
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.READ_PHONE_STATE" />
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" /> />
<uses-library android:name="kwb" />
<application android:theme="@style/SettingsTheme" android:label="@string/app_name" android:icon="@drawable/custom_rom" android:allowBackup="true">
<activity android:theme="@style/SettingsTheme" android:label="@string/app_name" android:name="com.sec.android.app.kwb.KwbLaunchActivity" android:configChanges="keyboardHidden|orientation">
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
</activity>
<meta-data android:name="SPDE.build.signature" android:value="424919/737923/release" />
<meta-data android:name="SPDE.env.version" android:value="0.12.2/19.1.8/19.2.12" />
</application>
</manifest>
The.Jericho.Initiative said:
Got a hold of the Samsung CROM Service apk that unlocks the S6 SM-G9250 bootloader and I've decompiled it, I'll be honest, it's been years since I've looked at this stuff. The file is distributed by Samsung for the Chinese market It's been verified to install on American Devices but force closes immediately. I figure it's failing a version check or something along those lines.
I can pass it along if anyone wants to take a crack at it. I'll be muddling along on my end but my primary interest is in the results - not the credit.
Anyone interested?
Edit:
-----
Contents of Android Manifest xml file:
<?xml version="1.0" encoding="utf-8"?>
<manifest android:sharedUserId="android.uid.system" android:versionCode="20150408" android:versionName="1.0.4" package="com.sec.android.app.kwb"
xmlns:android="http://schemas.android.com/apk/res/android">
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.READ_PHONE_STATE" />
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" /> />
<uses-library android:name="kwb" />
<application android:theme="@style/SettingsTheme" android:label="@string/app_name" android:icon="@drawable/custom_rom" android:allowBackup="true">
<activity android:theme="@style/SettingsTheme" android:label="@string/app_name" android:name="com.sec.android.app.kwb.KwbLaunchActivity" android:configChanges="keyboardHidden|orientation">
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
</activity>
<meta-data android:name="SPDE.build.signature" android:value="424919/737923/release" />
<meta-data android:name="SPDE.env.version" android:value="0.12.2/19.1.8/19.2.12" />
</application>
</manifest>
Click to expand...
Click to collapse
You can post the apk and wait for anyone crack it, you will receive the proper credit
Redundant post. Copied file into OP...
Redundant post. Copied file into OP...
The.Jericho.Initiative said:
Interestingly I came across a second version. The manifest of the first I posted said version 1.04 android:versionCode="20150408"
The manifest of the second reads version 1.01 android:versionCode="20141126" I've attached the second apk to this message
Click to expand...
Click to collapse
odd. on my galaxy tab s 10.5 (T807v) it opens up to the message that talks about unlocking device then fcs.. on my vzw s6 edge it fcs right away
Sent from my SM-G925V using XDA Free mobile app
---------- Post added at 06:57 PM ---------- Previous post was at 06:51 PM ----------
elliwigy said:
odd. on my galaxy tab s 10.5 (T807v) it opens up to the message that talks about unlocking device then fcs.. on my vzw s6 edge it fcs right away
Sent from my SM-G925V using XDA Free mobile app
Click to expand...
Click to collapse
also, the second apk has a lib file.. libkwb.so
Sent from my SM-G925V using XDA Free mobile app
heres where i get on my tablet...
Sent from my SM-T807V using XDA Free mobile app
s6-CROM.apk is missing /libs/libkwb.so
Code:
04-20 10:40:09.461: I/LoadedApk(19562): getClassLoader :dalvik.system.PathClassLoader[DexPathList[[zip file "/data/app/com.sec.android.app.kwb-1/base.apk"],nativeLibraryDirectories=[/vendor/lib64, /system/lib64]]]
04-20 10:40:09.461: I/LoadedApk(19562): getClassLoader :dalvik.system.PathClassLoader[DexPathList[[zip file "/data/app/com.sec.android.app.kwb-1/base.apk"],nativeLibraryDirectories=[/vendor/lib64, /system/lib64]]]
04-20 10:40:09.471: D/Activity(19562): performCreate Call Injection manager
04-20 10:40:09.481: I/InjectionManager(19562): dispatchOnViewCreated > Target : com.sec.android.app.kwb.KwbLaunchActivity isFragment :false
04-20 10:40:09.481: D/KwbLaunchActivity(19562): onResume called
04-20 10:40:09.481: D/LibKwb(19562): WARNING: Could not load /libs/libkwb.so
04-20 10:40:09.481: D/LibKwb(19562): java.lang.UnsatisfiedLinkError: dalvik.system.PathClassLoader[DexPathList[[zip file "/data/app/com.sec.android.app.kwb-1/base.apk"],nativeLibraryDirectories=[/vendor/lib64, /system/lib64]]] couldn't find "libkwb.so"
04-20 10:40:09.481: E/art(19562): No implementation found for int com.sec.android.lib.kwb.LibKwb.getCustomBinStatusFlag() (tried Java_com_sec_android_lib_kwb_LibKwb_getCustomBinStatusFlag and Java_com_sec_android_lib_kwb_LibKwb_getCustomBinStatusFlag__)
edit:
Added the that in, now it has unmet dependencies
Code:
04-20 11:32:14.231: E/art(24783): dlopen("/data/app/com.sec.android.app.kwb-1/lib/arm/libkwb.so", RTLD_LAZY) failed: dlopen failed: could not load library "libQSEEComAPI.so" needed by "libkwb.so"; caused by library "libQSEEComAPI.so" not found
edit:
Added in libQSEEComAPI.so and the app fires up and you can get thru all of the prompts, but then it crashes because I had to remove the shareduser so it would install, basically it has no permissions. We need to be able to load the two dependencies without modifying the apk because we can't resign the apk with the same signing key that it was originally signed with.
If someone could test this on an S6 that has root and load the two .so files we could do some more testing.
designgears said:
s6-CROM.apk is missing /libs/libkwb.so
Code:
04-20 10:40:09.461: I/LoadedApk(19562): getClassLoader :dalvik.system.PathClassLoader[DexPathList[[zip file "/data/app/com.sec.android.app.kwb-1/base.apk"],nativeLibraryDirectories=[/vendor/lib64, /system/lib64]]]
04-20 10:40:09.461: I/LoadedApk(19562): getClassLoader :dalvik.system.PathClassLoader[DexPathList[[zip file "/data/app/com.sec.android.app.kwb-1/base.apk"],nativeLibraryDirectories=[/vendor/lib64, /system/lib64]]]
04-20 10:40:09.471: D/Activity(19562): performCreate Call Injection manager
04-20 10:40:09.481: I/InjectionManager(19562): dispatchOnViewCreated > Target : com.sec.android.app.kwb.KwbLaunchActivity isFragment :false
04-20 10:40:09.481: D/KwbLaunchActivity(19562): onResume called
04-20 10:40:09.481: D/LibKwb(19562): WARNING: Could not load /libs/libkwb.so
04-20 10:40:09.481: D/LibKwb(19562): java.lang.UnsatisfiedLinkError: dalvik.system.PathClassLoader[DexPathList[[zip file "/data/app/com.sec.android.app.kwb-1/base.apk"],nativeLibraryDirectories=[/vendor/lib64, /system/lib64]]] couldn't find "libkwb.so"
04-20 10:40:09.481: E/art(19562): No implementation found for int com.sec.android.lib.kwb.LibKwb.getCustomBinStatusFlag() (tried Java_com_sec_android_lib_kwb_LibKwb_getCustomBinStatusFlag and Java_com_sec_android_lib_kwb_LibKwb_getCustomBinStatusFlag__)
edit:
Added the that in, now it has unmet dependencies
Code:
04-20 11:32:14.231: E/art(24783): dlopen("/data/app/com.sec.android.app.kwb-1/lib/arm/libkwb.so", RTLD_LAZY) failed: dlopen failed: could not load library "libQSEEComAPI.so" needed by "libkwb.so"; caused by library "libQSEEComAPI.so" not found
edit:
Added in libQSEEComAPI.so and the app fires up and you can get thru all of the prompts, but then it crashes because I had to remove the shareduser so it would install, basically it has no permissions. We need to be able to load the two dependencies without modifying the apk because we can't resign the apk with the same signing key that it was originally signed with.
If someone could test this on an S6 that has root and load the two .so files we could do some more testing.
Click to expand...
Click to collapse
do you have the two files? i am not sure where to locate the libqsee file.. i know it doesnt work but i am trying to learn and would like to see what you did lol
Sent from my SM-T807V using XDA Free mobile app
designgears said:
s6-CROM.apk is missing /libs/libkwb.so
Code:
04-20 10:40:09.461: I/LoadedApk(19562): getClassLoader :dalvik.system.PathClassLoader[DexPathList[[zip file "/data/app/com.sec.android.app.kwb-1/base.apk"],nativeLibraryDirectories=[/vendor/lib64, /system/lib64]]]
04-20 10:40:09.461: I/LoadedApk(19562): getClassLoader :dalvik.system.PathClassLoader[DexPathList[[zip file "/data/app/com.sec.android.app.kwb-1/base.apk"],nativeLibraryDirectories=[/vendor/lib64, /system/lib64]]]
04-20 10:40:09.471: D/Activity(19562): performCreate Call Injection manager
04-20 10:40:09.481: I/InjectionManager(19562): dispatchOnViewCreated > Target : com.sec.android.app.kwb.KwbLaunchActivity isFragment :false
04-20 10:40:09.481: D/KwbLaunchActivity(19562): onResume called
04-20 10:40:09.481: D/LibKwb(19562): WARNING: Could not load /libs/libkwb.so
04-20 10:40:09.481: D/LibKwb(19562): java.lang.UnsatisfiedLinkError: dalvik.system.PathClassLoader[DexPathList[[zip file "/data/app/com.sec.android.app.kwb-1/base.apk"],nativeLibraryDirectories=[/vendor/lib64, /system/lib64]]] couldn't find "libkwb.so"
04-20 10:40:09.481: E/art(19562): No implementation found for int com.sec.android.lib.kwb.LibKwb.getCustomBinStatusFlag() (tried Java_com_sec_android_lib_kwb_LibKwb_getCustomBinStatusFlag and Java_com_sec_android_lib_kwb_LibKwb_getCustomBinStatusFlag__)
edit:
Added the that in, now it has unmet dependencies
Code:
04-20 11:32:14.231: E/art(24783): dlopen("/data/app/com.sec.android.app.kwb-1/lib/arm/libkwb.so", RTLD_LAZY) failed: dlopen failed: could not load library "libQSEEComAPI.so" needed by "libkwb.so"; caused by library "libQSEEComAPI.so" not found
edit:
Added in libQSEEComAPI.so and the app fires up and you can get thru all of the prompts, but then it crashes because I had to remove the shareduser so it would install, basically it has no permissions. We need to be able to load the two dependencies without modifying the apk because we can't resign the apk with the same signing key that it was originally signed with.
If someone could test this on an S6 that has root and load the two .so files we could do some more testing.
Click to expand...
Click to collapse
I know CROM Service does have the library, what results, if any, did you see running that app?
The.Jericho.Initiative said:
I know CROM Service does have the library, what results, if any, did you see running that app?
Click to expand...
Click to collapse
i was not able to locate the libqseecomapi.so within the apk once i decompiled it.. when i tried to add it and recompile with original signature it failed to install as he stated due to signature..
i would assume if a rooted device was able to load the lib files to the right area, the apk would not need the original signature to function..
i have no idea if thats what he meant bcuz he is beyond my skill ha!
maybe we can get someone with root to help us out.
Sent from my SM-G925V using XDA Free mobile app
Post the libs and ill put them together tomorrow at the office. Will also be posting docs on how to deodex Android 5.0+ apks tomorrow as well
BMc08GT said:
Post the libs and ill put them together tomorrow at the office. Will also be posting docs on how to deodex Android 5.0+ apks tomorrow as well
Click to expand...
Click to collapse
Would that mean this thing might actually work?
Sent from my SAMSUNG-SM-G925A using Tapatalk
elliwigy said:
i was not able to locate the libqseecomapi.so within the apk once i decompiled it.. when i tried to add it and recompile with original signature it failed to install as he stated due to signature..
i would assume if a rooted device was able to load the lib files to the right area, the apk would not need the original signature to function..
i have no idea if thats what he meant bcuz he is beyond my skill ha!
maybe we can get someone with root to help us out.
Sent from my SM-G925V using XDA Free mobile app
Click to expand...
Click to collapse
If you can load the 2 files into the lib folder of the device there is no need to modify the apk and lose the signature and permissions. Even then the app checks the CID, IMEI, and serial which it then sends to a server to validate that you are using an unlockable device, which the AT&T variant isn't.
The only chance I see of this working is if we get root we could modify the app to have root permissions which would make modifying it not a problem. Might be possible to spoof the info being sent to the server but then there is a pretty good chance what it returned wouldn't work anyways because it doesn't match the phone.
Might be worth checking out, but I am pretty sure it's a dead end.
designgears said:
If you can load the 2 files into the lib folder of the device there is no need to modify the apk and lose the signature and permissions. Even then the app checks the CID, IMEI, and serial which it then sends to a server to validate that you are using an unlockable device, which the AT&T variant isn't.
The only chance I see of this working is if we get root we could modify the app to have root permissions which would make modifying it not a problem. Might be possible to spoof the info being sent to the server but then there is a pretty good chance what it returns wouldn't work anyways because it doesn't match the phone.
Might be worth checking out, but I am pretty sure it's a dead end.
Click to expand...
Click to collapse
Thanks for the clarification! so we need root in order to manually push the apk/libs as well as try to modify it so it will work on other devices..
i knew it wasnt that easy! thanks for looking into it! hopefully it can provide insight at a bl unlock later down the road if and when root is attained.
Thanks again!
Sent from my SM-G925V using XDA Free mobile app
So this is basically a dead end for AT&T/Verizion users?
Wiseor said:
So this is basically a dead end for AT&T/Verizion users?
Click to expand...
Click to collapse
This apk is a dead end. Hopefully chainf ire will get root.
Sent from my SM-G925V using XDA Premium HD app
Chain fire has nothing to do with getting root on locked phones... He doesn't do exploits
Att has root. Time to revive this thread?
Sent from My Samsung Galaxy S6 "Pure" Black
Is there any hope for this at all because I feal like we have the tool we just need to get past the checks
Wiseor said:
Is there any hope for this at all because I feal like we have the tool we just need to get past the checks
Click to expand...
Click to collapse
you need to manually push the libqseecom and libkwn files if you can find them then need to spoof device so it thinks its an unlockable variant when it contacts the server in order to have a chance at it working..
i am unable to locate the necessary files and when i installed both versions of the apk (also tried manually pushing and setting perms) they just fcd immediately.. i think this is due to me not having the required libs
Sent from my SM-G925V using XDA Free mobile app

Removing Android 11 Notification Headers: status_bar_notification_section_header.xml

Hi,
What's a clean way to apply changes made to SystemUI.apk in an Android 11 ROM (and have those changes take effect) that I don't maintain? Direct overwriting is fine, but I need the changes applied/running. I'm fine with breaking things, have root, and have resolved boot breakages via ADB etc. I'm trying to get rid of the annoying notification section headers (Conversation, Silent, etc..) that waste screen real estate. I overwrite the XML file in the APK (status_bar_notification_section_header.xml) with 0 padding, and re-sign that APK with LuckyPatcher (its test key). What's a good way to apply my patched APK so that it works like the original, but with my changes? pm install patched_file.apk isn't perfect - APK is internal. And there's ODEX/VDEX files generated for the original APK (/system_ext/priv-app/SystemUI/ .... SystemUI.apk, oat/arm/*.odex, *.vdex). I had to do a pm grant to reading contacts when I applied a revised SystemUI.apk. Assume I don't have Android Studio and just want to work on the mobile.
What I'm attempting:
packages/SystemUI/res/layout/status_bar_notification_section_header.xml - platform/frameworks/base - Git at Google
status_bar_notification_section_header.xml:
<com.android.systemui.statusbar.notification.stack.SectionHeaderView
xmlns:android="http://schemas.android.com/apk/res/android"
android:layout_width="match_parent"
android:layout_height="@dimen/notification_section_header_height"
androidaddingStart="0dp"
androidaddingEnd="0dp"
android:focusable="true"
android:clickable="true"
>

Categories

Resources