Hello Friends,
Just want to share another GUIDE/MOD this time for NON-ROOT users - ENABLING Apps for PEN Window without Root.
Without root, the only way to add more apps for Pen Window is modifying the app yourself or getting developers to add pen window support to their apps. But it involves a bit of knowledge in decompiling, editing, recompiling and resigning apps with apktool, jarsigner or some similar tool like Apk Manager, Apk Multitool and a lot others. I won't go into a tutorial about decompilation. I was a noob once and I did my best to search and learn about this stuff so if you are interested then a few google or xda search would give you tons of links on how to decompile/recompile apk files.
TOOLS:
1. Knowledge of modding apk files
2. ApkManager or other similar tools
3. Notepad++ or something similar
GUIDE:
1. Decompile apk file using ApkManager or your tool of choice.
2. Open the AndroidManifest.xml file of the decompiled apk file using Notepad++ or your editor of choice. Below is a sample AndroidManifest.xml file.
Code:
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="mobi.xperiacle.PenWindowTest"
android:versionCode="1"
android:versionName="1.0" >
<uses-sdk
android:minSdkVersion="16"
android:targetSdkVersion="17" />
<application
android:allowBackup="true"
android:icon="@drawable/ic_launcher"
android:label="@string/app_name"
android:theme="@style/AppTheme" >
<activity
android:name="mobi.xperiacle.PenWindowTest.MainActivity"
android:label="@string/app_name" >
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
</activity>
</application>
</manifest>
3. Look for the acivity which has "<category android:name="android.intent.category.LAUNCHER" />"
and add "<category android:name="com.samsung.android.intent.category.PENWINDOW_LAUNCHER" />" below it.
Below is the same AndroidManifest.xml above with the change highlighted in RED.
Code:
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="mobi.xperiacle.PenWindowTest"
android:versionCode="1"
android:versionName="1.0" >
<uses-sdk
android:minSdkVersion="16"
android:targetSdkVersion="17" />
<application
android:allowBackup="true"
android:icon="@drawable/ic_launcher"
android:label="@string/app_name"
android:theme="@style/AppTheme" >
<activity
android:name="mobi.xperiacle.PenWindowTest.MainActivity"
android:label="@string/app_name" >
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
[COLOR="Red"]<category android:name="com.samsung.android.intent.category.PENWINDOW_LAUNCHER" />[/COLOR]
</intent-filter>
</activity>
</application>
</manifest>
4. Look for "</application>" which is the closing tag of the <application...> node. Then add
"<meta-data android:name="com.samsung.android.sdk.multiwindow.penwindow.enable" android:value="true" />" above it. Below is the same AndroidManifest.xml file above with the all changes in RED.
Code:
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="mobi.xperiacle.PenWindowTest"
android:versionCode="1"
android:versionName="1.0" >
<uses-sdk
android:minSdkVersion="16"
android:targetSdkVersion="17" />
<application
android:allowBackup="true"
android:icon="@drawable/ic_launcher"
android:label="@string/app_name"
android:theme="@style/AppTheme" >
<activity
android:name="mobi.xperiacle.PenWindowTest.MainActivity"
android:label="@string/app_name" >
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
[COLOR="Red"]<category android:name="com.samsung.android.intent.category.PENWINDOW_LAUNCHER" />[/COLOR]
</intent-filter>
</activity>
[COLOR="Red"]<meta-data android:name="com.samsung.android.sdk.multiwindow.penwindow.enable" android:value="true" />[/COLOR]
</application>
</manifest>
5. Recompile and Resign apk file and push to your phone. If you are using ApkManager that is all done in one go with option 14 while phone is connected.
6. Have FUN! A COFFEE would be Nice. he he
THANKS to @soloilmeglio for testing and making sure it works before I write and share this guide.
Great news for all non-rooted gn3 eh eh.... great work as always
Inviato dal mio SM-N9005 utilizzando Tapatalk
So is it possible for you to do an app that automaticly does the magic?
Like some drag and drop .apk to make it work on penwindow (and why not in multiwindow too?)
Thanks, it works
I got it work only in one app (tried for ~5 apps)
Dunno if the problem is using APK Multi-Tool instead of ApkManager? And I believe problem is in .apk or tool.. Not in your guide
And why I can't find those lines already in app that has multiwindow, pen window or both already? How those are made then?
But thanks anyway very useful guide
ps. Didn't try to only add pen window, but multiwindow too at same time
Sent from my SM-N9005 using XDA Premium HD app
Oh man this is such great news..... if I knew how to decompile and recompile apks.
I've downloaded the tool but it's way above my knowledge.
Will wait to see if some-one can design an app to do it automatically as I'm NOT rooting my N3....
Amdathlonuk said:
Oh man this is such great news..... if I knew how to decompile and recompile apks.
I've downloaded the tool but it's way above my knowledge.
Will wait to see if some-one can design an app to do it automatically as I'm NOT rooting my N3....
Click to expand...
Click to collapse
It's not that hard really, it took a while for me but even I managed to make it work
If you got Java JDK and ADB installed (Google how to install if not)
Google APK Multi-Tool, you'll find a link to some topic on XDA where is download link (and instructions how to use it)
When you got all ready and multi tool running, type 24 and enter, choose your apk file (if you have that apk on computer and moved to Multi-Tool apk edit folder) and enter again. Then type 9 and enter to decompile, go to projects folder and edit AndroidManifest.xml. Then delete that app from your phone if already installed, connect your phone to pc using USB cable and then type 15 in Multi-Tool and hit enter. Now it should compile, sign and install that app to your phone, if everything went right.
Sorry for messy message but I'm at work. Ask if somethings not clear to you
Sent from my SM-N9005 using XDA Premium HD app
Add the red string under penwindow tweak and you unlock Multiwindows too
<category android:name="com.samsung.android.intent.category.PENWINDOW_LAUNCHER" />
<category android:name="android.intent.category.MULTIWINDOW_LAUNCHER" />
Click to expand...
Click to collapse
<meta-data android:name="com.samsung.android.sdk.multiwindow.penwindow.enable" android:value="true" />
<uses-library required="false" name="com.sec.android.app.multiwindow" />
<meta-data android:name="com.sec.android.support.multiwindow" android:value="true" />
<meta-data android:name="com.sec.android.multiwindow.DEFAULT_SIZE_W" android:value="632.0dip" />
<meta-data android:name="com.sec.android.multiwindow.DEFAULT_SIZE_H" android:value="598.0dip" />
<meta-data android:name="com.sec.android.multiwindow.MINIMUM_SIZE_W" android:value="632.0dip" />
<meta-data android:name="com.sec.android.multiwindow.MINIMUM_SIZE_H" android:value="598.0dip" />
Click to expand...
Click to collapse
---------- Post added at 01:43 AM ---------- Previous post was at 01:42 AM ----------
Add the red string under penwindow tweak and you unlock Multiwindows too
<category android:name="com.samsung.android.intent.category.PENWINDOW_LAUNCHER" />
<category android:name="android.intent.category.MULTIWINDOW_LAUNCHER" />
Click to expand...
Click to collapse
<meta-data android:name="com.samsung.android.sdk.multiwindow.penwindow.enable" android:value="true" />
<uses-library required="false" name="com.sec.android.app.multiwindow" />
<meta-data android:name="com.sec.android.support.multiwindow" android:value="true" />
<meta-data android:name="com.sec.android.multiwindow.DEFAULT_SIZE_W" android:value="632.0dip" />
<meta-data android:name="com.sec.android.multiwindow.DEFAULT_SIZE_H" android:value="598.0dip" />
<meta-data android:name="com.sec.android.multiwindow.MINIMUM_SIZE_W" android:value="632.0dip" />
<meta-data android:name="com.sec.android.multiwindow.MINIMUM_SIZE_H" android:value="598.0dip" />
Click to expand...
Click to collapse
erlos said:
Add the red string under penwindow tweak and you unlock Multiwindows too
---------- Post added at 01:43 AM ---------- Previous post was at 01:42 AM ----------
Add the red string under penwindow tweak and you unlock Multiwindows too
Click to expand...
Click to collapse
would anything of this work with Waze?
valtersboze said:
would anything of this work with Waze?
Click to expand...
Click to collapse
?????
I did Not understand...
This is OLD tips on note 1
Inviato dal mio SM-N9005 utilizzando Tapatalk
erlos said:
?????
I did Not understand...
This is OLD tips on note 1
Click to expand...
Click to collapse
before i spend hours trying to figure out the apk tool - i wanted to ask if anyone has applied the penwindow/multiwindow tags to Waze apk and if it works. In city driving waze is critical to be open but it is waste of screen real estate to see just waze. i would like whatsapp or music apps open and visible too.
I Will be try later!
Inviato dal mio SM-N9005 utilizzando Tapatalk
nice work...
itworks thanks
What apps have you all tested this on? I'd like to try it on a confirmed app. I did this with one app already and the app runs normally but it is not showing up in my pen window list when I bring it up. I also tried setting it up for multiwindows but I don't know how to test that feature. Is there a way to bring up multiwindows without having to do it automatically? For example if I'm browsing on chrome and I want to pull up a dictionary app in the second window, is that possible and if so how?
Dewdropkorn said:
What apps have you all tested this on? I'd like to try it on a confirmed app. I did this with one app already and the app runs normally but it is not showing up in my pen window list when I bring it up. I also tried setting it up for multiwindows but I don't know how to test that feature. Is there a way to bring up multiwindows without having to do it automatically? For example if I'm browsing on chrome and I want to pull up a dictionary app in the second window, is that possible and if so how?
Click to expand...
Click to collapse
Allright..
If you made it right, app should show in penwindow menu and for multiwindow in the list when you open "multiwindow bar"
What program you used for editing .apk?
I did it this way (some apps still didn't work, but not sure why is that)
I downloaded APK Multi-Tool from bottom of first post http://forum.xda-developers.com/showthread.php?t=695701
Then: Enter 24 (Set current project) --> 9 (Decompile apk) --> Then I deleted the app from my phone --> Edited the AndroidManifest.xml --> 15 (compile apk / sign apk / install apk)
Now it install the app to phone
Okay then, there is typos in all post in this topic that should enable penwindow (at least didn't work for me before I corrected them)
If you watch close to (example those at first post) they got SPACE between "." and "P" --> "...category.(SPACE HERE)PENWINDOW..."
Same for another line "...multiwindow.(SPACE HERE)penwindow.enable"
APK Multi-Tool gave error to log and app didn't work before those SPACEs were removed.
Hmm.. When I was writing this post, I noticed that SPACE came there in post preview even it really wasn't in post?
It did same when I tried to put those lines in quote tags, so why is that?
Only way to get that one "automatic space" away from line was to put it in code tags
So try copying these to AndroidManifest.xml to enable both Penwindow and Multiwindow
Code:
<category android:name="com.samsung.android.intent.category.PENWINDOW_LAUNCHER" />
<category android:name="android.intent.category.MULTIWINDOW_LAUNCHER" />
Code:
<meta-data android:name="com.samsung.android.sdk.multiwindow.penwindow.enable" android:value="true" />
<uses-library required="false" name="com.sec.android.app.multiwindow" />
<meta-data android:name="com.sec.android.support.multiwindow" android:value="true" />
<meta-data android:name="com.sec.android.multiwindow.DEFAULT_ SIZE_W" android:value="632.0dip" />
<meta-data android:name="com.sec.android.multiwindow.DEFAULT_ SIZE_H" android:value="598.0dip" />
<meta-data android:name="com.sec.android.multiwindow.MINIMUM_ SIZE_W" android:value="632.0dip" />
<meta-data android:name="com.sec.android.multiwindow.MINIMUM_ SIZE_H" android:value="598.0dip" />
Spere said:
Allright..
If you made it right, app should show in penwindow menu and for multiwindow in the list when you open "multiwindow bar"
What program you used for editing .apk?
I did it this way (some apps still didn't work, but not sure why is that)
I downloaded APK Multi-Tool from bottom of first post http://forum.xda-developers.com/showthread.php?t=695701
Then: Enter 24 (Set current project) --> 9 (Decompile apk) --> Then I deleted the app from my phone --> Edited the AndroidManifest.xml --> 15 (compile apk / sign apk / install apk)
Now it install the app to phone
Okay then, there is typos in all post in this topic that should enable penwindow (at least didn't work for me before I corrected them)
If you watch close to (example those at first post) they got SPACE between "." and "P" --> "...category.(SPACE HERE)PENWINDOW..."
Same for another line "...multiwindow.(SPACE HERE)penwindow.enable"
APK Multi-Tool gave error to log and app didn't work before those SPACEs were removed.
Hmm.. When I was writing this post, I noticed that SPACE came there in post preview even it really wasn't in post?
It did same when I tried to put those lines in quote tags, so why is that?
Only way to get that one "automatic space" away from line was to put it in code tags
So try copying these to AndroidManifest.xml to enable both Penwindow and Multiwindow
Code:
<category android:name="com.samsung.android.intent.category.PENWINDOW_LAUNCHER" />
<category android:name="android.intent.category.MULTIWINDOW_LAUNCHER" />
Code:
<meta-data android:name="com.samsung.android.sdk.multiwindow.penwindow.enable" android:value="true" />
<uses-library required="false" name="com.sec.android.app.multiwindow" />
<meta-data android:name="com.sec.android.support.multiwindow" android:value="true" />
<meta-data android:name="com.sec.android.multiwindow.DEFAULT_ SIZE_W" android:value="632.0dip" />
<meta-data android:name="com.sec.android.multiwindow.DEFAULT_ SIZE_H" android:value="598.0dip" />
<meta-data android:name="com.sec.android.multiwindow.MINIMUM_ SIZE_W" android:value="632.0dip" />
<meta-data android:name="com.sec.android.multiwindow.MINIMUM_ SIZE_H" android:value="598.0dip" />
Click to expand...
Click to collapse
That's exactly what my problem was. Fixing the spaces caused the app to show up for both my Penwindow and my multiwindow. Thank you so much. I don't have the luxury of rooting and this was exactly what I needed for doing what I need for this phone for.:good:
Thanks
Sent from my SM-N900 using XDA Premium 4 mobile app
Dewdropkorn said:
That's exactly what my problem was. Fixing the spaces caused the app to show up for both my Penwindow and my multiwindow. Thank you so much. I don't have the luxury of rooting and this was exactly what I needed for doing what I need for this phone for.:good:
Click to expand...
Click to collapse
Nice to hear it works
Sent from my SM-N9005 using XDA Premium HD app
Has anyone done this with Spotify? I've successfully modded about 6 apps now but the .apk I recompiled and signed for Spotify has "parsing" errors when I try to installing it. Anyone else with better luck?
Related
This recovery is CWM for the One SV. It is fully working and has no problems. All variants are supported below
K2_CL (Boost Mobile) -> Boost Download
K2_PLC_CL (Cricket) -> Cricket Download
K2_UL (EU LTE) -> EU LTE Download
K2_U (EU NON-LTE) -> EU Non-LTE Download
Sources:
Boost Mobile Source
Cricket Source
EU LTE Source
EU Non-LTE Source
To build these recoveries on your own, simply follow the directions below:
Clone the CyanogenMod repo. See their wiki at http://wiki.cyanogenmod.org
create a local_manifests file by issuing the command `mkdir -p .repo/local_manifests/` then `gedit .repo/local_manifests/k2.xml`
inside this new document place the following lines
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="device/htc/msm8960-common" name="CyanogenMod/android_device_htc_msm8960-common" />
<project path="device/htc/s4-common" name="CyanogenMod/android_device_htc_s4-common" />
<project path="device/htc/k2_cl" name="SimonSickle/android_device_htc_k2_cl" revision="cwm" />
<project path="vendor/htc/k2_cl" name="SimonSickle/android_vendor_htc_k2_cl" revision="jellybean" />
<project path="device/htc/k2_plc_cl" name="SimonSickle/android_device_htc_k2_plc_cl" revision="cwm" />
<project path="vendor/htc/k2_plc_cl" name="SimonSickle/android_vendor_htc_k2_plc_cl" revision="jellybean" />
<project path="device/htc/k2_ul" name="SimonSickle/android_device_htc_k2_ul" revision="cwm" />
<project path="vendor/htc/k2_ul" name="SimonSickle/android_vendor_htc_k2_ul" revision="jellybean" />
<project path="device/htc/k2_u" name="SimonSickle/android_device_htc_k2_u" revision="cwm" />
<project path="vendor/htc/k2_u" name="SimonSickle/android_vendor_htc_k2_u" revision="jellybean" />
<project path="kernel/htc/k2" name="SickleKernels/android_kernel_htc_k2" revision="htc_3.4" />
</manifest>
now run `repo sync` and wait for this to finish. It will take a long time
With any luck, you now have the source. Your computer should already be set up to build so just do the following commands
. build/envsetup.sh
now you will want to lunch the right device (see the download section as a guide)
lunch cm_k2_cl-userdebug
and finally the make command is as follows
make -j5 recoveryimage
at the end you will see a welcoming path to your new recovery. Flash it in fastboot or with dd and enjoy!
simonsimons34 said:
This recovery is CWM for the One SV. It is fully working and has no weird glitchy screen like it had before.
Download for BOOST MOBILE here -> http://downloads.codefi.re/simon/k2cl/CWMrecovery.img
Source at http://github.com/SimonSickle/android_device_htc_k2_cl/tree/cwm
I have applied for official status with Koush. Until he accepts it, enjoy this perfect build
Click to expand...
Click to collapse
Works great Simon! Thanks.
simonsimons34 said:
This recovery is CWM for the One SV. It is fully working and has no weird glitchy screen like it had before.
Download for BOOST MOBILE here -> http://downloads.codefi.re/simon/k2cl/CWMrecovery.img
Source at http://github.com/SimonSickle/android_device_htc_k2_cl/tree/cwm
I have applied for official status with Koush. Until he accepts it, enjoy this perfect build
Click to expand...
Click to collapse
Hi;
The recovery file is not there. Can you reload it?
Sorry Simon, recovery doesn't boot.
Neither the k2u nor the k2ul.
k2u -> boots constantly into android, not recovery.
k2ul -> hangs on splash screen.
bkcokota's cwm works totally fine, but it has the framework bug.
This bug fixed and we have a stable CWM. But i know, devs do not work on others build.
I am going to do twrp then. Once those are confirmed booting ill use the TWRP folder and remove anything non twrp from them
PS- The issue with his build is a lack of source (problem one), the partitions are different (two), the devices have different code names which messes with the flashing of source built roms (problem three) and its not ready for 4.3 (4)
Updated 9/21/13
Sent from my C525c using Tapatalk 4
All of the links are dead. Where else can I get info for the Boost c525c?
1. Download Settings Files.zip
2. Decompile your Settings.apk
3. Extract custombanner.xml of Settings Files.zip and place it in res/layout in decompiled Settings.apk
4. Open /res/xml/device_info_settings.xml
You'll see several <Preference android:title tags
5.Add this just a line above the first Preference tag:
Code:
<PreferenceCategory android:layout="@layout/custombanner" android:title="" />
6. Save the file and exit
7. Now make a .png banner for your ROM or find one on the internet. It has to be a .png
Resize your banner to 480x300 and rename it to custombanner.png
8. Place the custombanner.png in res/drawable
9. Recompile Settings.apk and Replace the settings.apk in your ROM
10. Enjoy :good:
Reserved for Screenshots
Screenshots
Hi ...... Can you add theme option in settings ?????
nathanjp said:
1. Download Settings Files.zip
2. Decompile your Settings.apk
3. Extract custombanner.xml of Settings Files.zip and place it in res/layout in decompiled Settings.apk
4. Open /res/xml/device_info_settings.xml
You'll see several <Preference android:title tags
5.Add this just a line above the first Preference tag:
Code:
Code:
<PreferenceCategory android:layout="@layout/myawesomerom" android:title="" />
6. Save the file and exit
7. Now make a .png banner for your ROM or find one on the internet. It has to be a .png
Resize your banner to 480x300 and rename it to custombanner.png
8. Place the custombanner.png in res/drawable
9. Recompile Settings.apk and Replace the settings.apk in your ROM
10. Enjoy :good:
Click to expand...
Click to collapse
Thanks bro... it works on my Samsung Galaxy Mega GT-I9152, but I Think there's only one mistake with your guide bro... in step number 5 :
Code:
<PreferenceCategory android:layout="@layout/myawesomerom" android:title="" />
it should be
Code:
<PreferenceCategory android:layout="@layout/custombanner" android:title="" />
Please correct me if I was wrong...Thanks...
sitifire said:
Thanks bro... it works on my Samsung Galaxy Mega GT-I9152, but I Think there's only one mistake with your guide bro... in step number 5 :
Code:
<PreferenceCategory android:layout="@layout/myawesomerom" android:title="" />
it should be
Code:
<PreferenceCategory android:layout="@layout/custombanner" android:title="" />
Please correct me if I was wrong...Thanks...
Click to expand...
Click to collapse
Thanks for pointing that when i war writing the xml file i thought of using myawesomerom but instead i used custombanner. Thats why i made a mistake will correct it immediately. Thanks for letting me know
It works perfect!!!!!
G.M.L._V2_IcSmoothness
http://pasakalis.blogspot.gr
Ended up in error in recompiling Any help?
Works perfect on sprint Galaxy Note 3 running stock deodexed lollipop rom. Thanks for this. It's awesome!!
great..thanks..I just try
Hey!
I am trying to port AOSP-B to my LG G4. I added the following to my manifext.xml follow and synced
Code:
<remote name="mups" fetch="https://www.github.com/themuppets" revision="cm-13.0" />
<remote name="cm"
fetch="https://github.com/cyanogenmod"
revision="cm-13.0" />
<project path="device/lge/h811" name="android_device_lge_h811" remote="cm" />
<project path="device/lge/g4-common" name="android_device_lge_g4-common" remote="cm" />
<project path="kernel/lge/msm8992" name="android_kernel_lge_msm8992" remote="cm" />
<project path="vendor/lge" name="proprietary_vendor_lge" remote="mups" />
and synced up. Everything I added was there. Perfect!
I run "./build/envsetup.sh" and everything goes fine.
I type "lunch" and see my device
Code:
8. cm_h811-userdebug
I hit "8" and get this:
Code:
build/core/product_config.mk:234: *** Can not locate config makefile for product "cm_h811". Stop.
Device h811 not found. Attempting to retrieve device repository from AOSPB Github (http://github.com/AOSPB).
Repository for h811 not found in the AOSPB Github repository list.
If this is in error, you may need to manually add it to your .repo/local_manifests/aospb_manifest.xml
build/core/product_config.mk:234: *** Can not locate config makefile for product "cm_h811". Stop.
** Don't have a product spec for: 'cm_h811'
** Do you have the right repo manifest?
Where could I go wrong? I know since I'm building AOSP that it's probably missing something from CM. What would I need to add? I've already reached out to a dev that ported this AOSPB to the G3 with no response yet.
I did not modify anything I downloaded. Just sync and build.
Any ideas?
bradym512 said:
Hey!
I am trying to port AOSP-B to my LG G4. I added the following to my manifext.xml follow and synced
Code:
<remote name="mups" fetch="https://www.github.com/themuppets" revision="cm-13.0" />
<remote name="cm"
fetch="https://github.com/cyanogenmod"
revision="cm-13.0" />
<project path="device/lge/h811" name="android_device_lge_h811" remote="cm" />
<project path="device/lge/g4-common" name="android_device_lge_g4-common" remote="cm" />
<project path="kernel/lge/msm8992" name="android_kernel_lge_msm8992" remote="cm" />
<project path="vendor/lge" name="proprietary_vendor_lge" remote="mups" />
and synced up. Everything I added was there. Perfect!
I run "./build/envsetup.sh" and everything goes fine.
I type "lunch" and see my device
Code:
8. cm_h811-userdebug
I hit "8" and get this:
Code:
build/core/product_config.mk:234: *** Can not locate config makefile for product "cm_h811". Stop.
Device h811 not found. Attempting to retrieve device repository from AOSPB Github (http://github.com/AOSPB).
Repository for h811 not found in the AOSPB Github repository list.
If this is in error, you may need to manually add it to your .repo/local_manifests/aospb_manifest.xml
build/core/product_config.mk:234: *** Can not locate config makefile for product "cm_h811". Stop.
** Don't have a product spec for: 'cm_h811'
** Do you have the right repo manifest?
Where could I go wrong? I know since I'm building AOSP that it's probably missing something from CM. What would I need to add? I've already reached out to a dev that ported this AOSPB to the G3 with no response yet.
I did not modify anything I downloaded. Just sync and build.
Any ideas?
Click to expand...
Click to collapse
Greetings,
Please read the sticky threads for XDA Assist.
This is not a help desk. XDA Assist is a place for new members to get help finding their way. Our purpose is to provide a link to where they should post and get the help they seek. As a Senior member, you are expected to be able to use the search feature and ask in the correct forum yourself.
Thanks.
Thread closed.
Hello, I'm trying to build cm 13 caf rom myself (i have never done it before) and I'm following this guide. I have done everything to the step "download the source code" from https://github.com/CyanogenMod/android.git. Now I should "Prepare the device-specific code", but the guide is for hammerhead CM (non-caf) and, if I'm right, I should add some local_manifests but I have no idea of how to do this. (in fact if I type $ breakfast hammerheadcaf it starts downloading and then it says
** Don't have a product spec for: 'cm_hammerheadcaf'
** Do you have the right repo manifest?)
Can anyone explain it to me, please?
Hello apon97!
You can search the CAF thread a bit - a lot of question regarding building CyanogenMod for hammerheadcaf have been already covered there. However, the thread is huge and searching it is a pain in the b*tt sometimes so I'll try to help you here.
You have to know the following:
Downloading the source code will 'only' download the default projects. This usually takes a few hours to download depending on your internet connection. However, to build for a specific device (hammerheadcaf in this case) you also have to get two more things: It's dependencies (device- and kernel-tree) and the vendor proprietary files - usually simplified as 'blobs'.
So after you've downloaded the source code you don't have any local manifests. A simple 'breakfast hammerheadcaf' will look for cm.dependencies in the device-tree and automagically add these to your default local manifest (called 'roomservice.xml').
The proprietary stuff has to be manually added to the local manifest. Just open up /SOURCE/.repo/local_manifests.xml and you should see that the kernel and device tree is already there (because you breakfasted...). Now add another line for the blobs. These can be found on TheMuppets: github.com/TheMuppets/proprietary_vendor_lge
So your local manifest 'roomservice.xml' should look something similar to this:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_lge_hammerheadcaf" path="device/lge/hammerheadcaf" remote="github" />
<project name="CyanogenMod/android_kernel_lge_hammerhead" path="kernel/lge/hammerhead" remote="github" revision="cm-13.0-caf" />
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" />
<project name="TheMuppets/proprietary_vendor_lge" path="vendor/lge" remote="github" />
</manifest>
PS: myfluxi updated the proprietary files for hammerheadcaf on his personal GitHub. You're free to use this project instead if you want to be up-to-date. However, he says that we don't need necessarily up-to-date blobs. Then the last project would look like this:
Code:
<project name="myfluxi/proprietary_vendor_lge" path="vendor/lge" remote="github" />
Now you have everything set up and ready to build CM13 CAF for the Nexus 5!
You don't have to go through this everytime you want to build. Next time just use
'repo sync'
'source build/envsetup.sh'
Optionally 'make clean' or 'make clobber' <- This will delete stuff from previous builds. Doing a clean build will take longer...
and finally...
'brunch hammerheadcaf'
Much fun building!
Everything looks clear. Yes, I have searched your thread but couldn't find the answer (maybe I could have tried a little more). I hope I will not have to bother you anymore
Thank for such a complete answer and for everything you do for our Nexus 5
Yeah I know, the thread is a bit messy but I can't do anything about it
Don't hesitate to ask if you need a bit more help
Whatsapp Enable Dark Mode for rooted device only.
This is for information only. Do it on your own risk.
Make sure you have a file explorer that supports root. If you don’t have much idea about this, suggest you download the*Solid Explorer File Manager*from Play Store. Now when you open the app, grant it root access by tapping Allow in the Magisk pop-up that appears.*
Open File Manager and head over to the root partition.*
Then go to*Data*>*Data*and navigate to the*com.whatsapp*folder.
Go to the*shared_prefs*folder and search for the*com.whatsapp_preferences.xml*file.
Now add the below lines to that xml file, anywhere inside the*<map>*and*</map>*tags. This one line of code is, in fact, responsible for enabling Dark Mode on WhatsApp on rooted Android devices.
<boolean name="dark_mode" value="true" />
Next, tap on the floppy icon to save the file. Now just force close WhatsApp and re-open it.
Finally, head over to*Settings. You could now see the*Theme*option, just beneath Account. Tap on it and select*Dark.
That’s it.
Tested in android 9 and 10.
Example how i added that line
<boolean name="move_media_folder_from_sister_app" value="true" />
<int name="web_service_delay" value="120" />
<boolean name="search_in_storage_usage" value="true" />
<boolean name="third_party_sticker_caching" value="true" />
<boolean name="auth_fingerprint_enabled" value="true" />
<boolean name="dark_mode" value="true" />
</map>
I hv added in last line...
For example
There's already a thread for this here:
https://forum.xda-developers.com/general/general/enable-dark-mode-whatsapp-root-twrp-t4017667
Please search before posting to avoid creating duplicate topics.
Thread closed.