[App][Rooted]KPPD Control[4.4+][Oreo Compatible now!] - G4 Themes and Apps

KPPD Control
Hey everyone! I know many of you are a big fan of @savoca 's KCal daemon KPPD. It is KCal for select chip sets on rooted phones that do not have KCal built into the kernel, or for phones that the KCal only partly supports.
KCal is a tool for adjusting the color, saturation, contrast, etc., of your screen, post processed. That means it happens after the image is drawn, and only affects what you visually see, so a screenshot is not affected by this. this helps you make your display show true black, and all sorts of cool color effects!
You can read more about KCal here:
https://forum.xda-developers.com/showthread.php?t=3165247
And a couple of quotes from savoca:
Hello all! If you're familiar with*KCAL*and suffer from symptoms such as a locked bootloader or non-loadable kernel modules then you may be interested in KCAL Post-Processing Daemon, or KPPD - the all-in-one display tuning tool that you can use to customize your color calibration on the fly!
This does NOT require an unlocked bootloader, custom kernel, or even a kernel that supports module loading, just run the daemon and you're good to go!
A once *very* device dependent feature now made available for the following chipsets:
Quote:
8x10
8974 v1.0
8x26 v1.0
8x26 v2.0, 8926 v1.0
8926 v2.0
8974 v2.0
8974 v3.0 (Pro)
8084 v1.0
8084 v1.1
8994 v1.0
8916 v1.0
8939 v1.0
8092 v1.0
Click to expand...
Click to collapse
However, the LG G4 has an 8992 chip, and it works too. So you could always try it if you have a Qualcomm chip. Be sure to let us know the results!
All the credit for KPPD goes to savoca. Using his tools used to require installation at the terminal or with ADB. Then, to make changes required hand editing a text file. But praise God, not anymore! now you can just use this app to handle everything from installation to making adjustments!
Feel free to give it a try! I made this app under the Apache 2.0 license, so fell free to borrow anything you need!
After install, you must give the app permission to read/write to the phone.
Go to:
Settings --> apps --> kppd --> permissions
And turn on storage.
Note: If you turned on storage permissions, but it still says "error, check permissions" then go to your sdcard, and create a folder called "documents" (if it doesn't exist) and in that folder, create an empty file called "kppd.conf". Then try the app again. This happens on some ROMs, and I'm not sure why.
Google Play Store:
https://play.google.com/store/apps/details?id=com.alaskalinuxuser.kppdcontrol
GitHub: (The app folder has a copy of the apk as well, if you don't use the play store.)
https://github.com/alaskalinuxuser/app_kppdcontrol
I have only tested this on a T-Mobile LG G4, but it should work on any KPPD/KCal compatible (mdp5) device.
Enjoy! And feel free to comment!
{
"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"
}
Sent from my LG-H811 using XDA-Developers Legacy app

AlaskaLinuxUser said:
KPPD Control
Hey everyone! I know many of you are a big fan of @savoca 's KCal daemon KPPD. It is KCal for select chip sets on rooted phones that do not have KCal built into the kernel, or for phones that the KCal only partly supports.
KCal is a tool for adjusting the color, saturation, contrast, etc., of your screen, post processed. That means it happens after the image is drawn, and only affects what you visually see, so a screenshot is not affected by this. this helps you make your display show true black, and all sorts of cool color effects!
You can read more about KCal here:
https://forum.xda-developers.com/showthread.php?t=3165247
All the credit for KPPD goes to savoca. Using his tools used to require installation at the terminal or with ADB. Then, to make changes required hand editing a text file. But praise God, not anymore! now you can just use this app to handle everything from installation to making adjustments!
Feel free to give it a try! I made this app under the Apache 2.0 license, so fell free to borrow anything you need!
Google Play Store:
https://play.google.com/store/apps/details?id=com.alaskalinuxuser.kppdcontrol
GitHub: (The app folder has a copy of the apk as well, if you don't use the play store.)
https://github.com/alaskalinuxuser/app_kppdcontrol
I have only tested this on a T-Mobile LG G4, but it should work on any KPPD/KCal compatible (mdp5) device.
Enjoy! And feel free to comment!
Click to expand...
Click to collapse
Thanks sir
This is what i wanted
To change values everytime editing the file was very messy
Thanks sir
And also to savoca

addy692 said:
Thanks sir
This is what i wanted
To change values everytime editing the file was very messy
Thanks sir
And also to savoca
Click to expand...
Click to collapse
Thank you, I'm glad you like the app!
Sent from my LG-H811 using XDA-Developers Legacy app

@AlaskaLinuxUser thank you so much for this.
i used to use kcal on my sony xperia z2 on stock marshmallow rom with compiled kcal module but now i am on resurrection remix android 7.1.2 (aosp base), i installed the app but i can only adjust RGB same like the built in feature live display but i can't adjust anything else like contrast saturation,values...etc, from what i readed i should be able to adjust everything same like kcal even without custom kernel ! or should the kernel supports kcal to be able to adjust everything ?
thanks again for the app .

rocker00 said:
@AlaskaLinuxUser thank you so much for this.
i used to use kcal on my sony xperia z2 on stock marshmallow rom with compiled kcal module but now i am on resurrection remix android 7.1.2 (aosp base), i installed the app but i can only adjust RGB same like the built in feature live display but i can't adjust anything else like contrast saturation,values...etc, from what i readed i should be able to adjust everything same like kcal even without custom kernel ! or should the kernel supports kcal to be able to adjust everything ?
thanks again for the app .
Click to expand...
Click to collapse
rocker00,
Thanks for the kind words.
Two thoughts:
#1. Could you open the /sdcard/documents/kppd.conf file, and manually edit it to pa version 1 instead of 2? Then try editing (manually) the file values and press save. Does that work? Be sure before hand to open the app and enable once to get the kppd running. This will see if you have pa version 1 or 2. My app is only set up for version 2, but I may need to make a settings page for version 1 or 2.
#2. If you manually install per savoca's kppd thread (link in op) does it work? If not, then it is a problem with the kppd, not my app.
I am not trying to duck the problem. Just trying to isolate if it is my app or kppd itself. I didn't make kppd, and kppd may need to be specifically edited and compiled for your phone, I'm not sure. Was there ever a working kppd (not KCal, which is in the kernel) for your phone?
Also, for grins, can you send me a log cat when it fails to work?
Thanks!
Sent from my LG-H811 using XDA-Developers Legacy app

AlaskaLinuxUser said:
rocker00,
Thanks for the kind words.
Two thoughts:
#1. Could you open the /sdcard/documents/kppd.conf file, and manually edit it to pa version 1 instead of 2? Then try editing (manually) the file values and press save. Does that work? Be sure before hand to open the app and enable once to get the kppd running. This will see if you have pa version 1 or 2. My app is only set up for version 2, but I may need to make a settings page for version 1 or 2.
#2. If you manually install per savoca's kppd thread (link in op) does it work? If not, then it is a problem with the kppd, not my app.
Edit: @AlaskaLinuxUser tried to install manually without you app, same result ! can't adjust anything except RGB ! also tried your idea to change pa from 2 to 1 but also the same result ! so the problem is not the app, the problem is kppd itself or something in the rom ! thank you so much for the app and for trying to help and also lets wait for feedback for other users.
best regards
I am not trying to duck the problem. Just trying to isolate if it is my app or kppd itself. I didn't make kppd, and kppd may need to be specifically edited and compiled for your phone, I'm not sure. Was there ever a working kppd (not KCal, which is in the kernel) for your phone?
Also, for grins, can you send me a log cat when it fails to work?
Thanks!
Sent from my LG-H811 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Thanks for trying to help and yeah sure i understand you are just trying to figure out where is the problem !
i will do what you said and i will let you know the result.
Thanks.
Edit: @AlaskaLinuxUser tried both ideas, changing pa form 2 to 1 & installing manually without your app but still the same result ! only able to adjust RGB ! so, obviously the problem is not the app itself but in kppd or something in the rom !
anyway thank you so much for the app and for trying to help and also lets wait for feedback from the other users !
best regards .

rocker00 said:
Thanks for trying to help and yeah sure i understand you are just trying to figure out where is the problem !
i will do what you said and i will let you know the result.
Thanks.
Edit: @AlaskaLinuxUser tried both ideas, changing pa form 2 to 1 & installing manually without your app but still the same result ! only able to adjust RGB ! so, obviously the problem is not the app itself but in kppd or something in the rom !
anyway thank you so much for the app and for trying to help and also lets wait for feedback from the other users !
best regards .
Click to expand...
Click to collapse
Do you have a link to the threads with the compiled kcal module? savoca made kppd open source, so if the thread has any clue to the girth commits to make it work on your phone, perhaps there is something we can do. Perhaps, no promises, and it's a long shot....
Sent from my LG-H811 using XDA-Developers Legacy app

AlaskaLinuxUser said:
Do you have a link to the threads with the compiled kcal module? savoca made kppd open source, so if the thread has any clue to the girth commits to make it work on your phone, perhaps there is something we can do. Perhaps, no promises, and it's a long shot....
Sent from my LG-H811 using XDA-Developers Legacy app
Click to expand...
Click to collapse
here is the thread for the module https://forum.xda-developers.com/crossdevice-dev/sony/5-x-kcal-module-flashable-t3159869 , the rom which i am using right now supposed to use 3.10 kernel but it uses 3.4 kernel to have a fully working camera due to the lack of camera blobs source from sony, since i am not linux user unfortunately i don't know anything about compiling but i also feel that it's a little bit complicated in this case !
Thank you so much

I'm assuming that because this deals with modifying the kernel that you have to have an unlocked boot loader. Which means this won't work for a Verizon LG G4?

Spookymyo said:
I'm assuming that because this deals with modifying the kernel that you have to have an unlocked boot loader. Which means this won't work for a Verizon LG G4?
Click to expand...
Click to collapse
This actually does not require an unlocked boot loader. The KPPD daemon runs in user space, but root is required. I have only tested on the T-Mobile G4, but it should work on any rooted G4.
I would appreciate hearing your results if you have time to test it.
Sent from my LG-H811 using XDA-Developers Legacy app

Does not work on LG G5

obol2 said:
Does not work on LG G5
Click to expand...
Click to collapse
Thanks for testing it!
Question: did it not work at all? Did the r g b multipliers work, or just not at all?
Sorry, just read up on the LG G5, it has an 8996 chip, which savoca did not list as applicable. Then again, neither is the G4's chip, the 8992, but it works on the G4 anyways. Sorry that it does not work on the G5.
Also, if you have time did savoca's original kppd work? Sorry for all all the questions. Thanks for taking the time to test it!
Forgive my ignorance, too, but is the G5 chose on the list of chips in the OP (just updated, was not there before now)?
If so, which version? Notice in the text file there is a "pa" version. You may need to change to 1, 2, or 3 depending on your version. If that is the case (and them editing the text file works) I could add a settings for version number also.
Sent from my LG-H811 using XDA-Developers Legacy app

Hi there!
Would this tool work on a Nexus 6P running Pure Nexus with ElementalX kernel? I had been using savoca's Color Control app but it doesn't work anymore on Nougat.
Thanks!
Sent from my Nexus 6P

Works on msm8953 chip?

Ghisy said:
Hi there!
Would this tool work on a Nexus 6P running Pure Nexus with ElementalX kernel? I had been using savoca's Color Control app but it doesn't work anymore on Nougat.
Thanks!
Sent from my Nexus 6P
Click to expand...
Click to collapse
Great question!
Yes, it should work.
On the original kppd thread (link in OP) a 6P was using it. They did mention a specific 6P glitch, though, that if you had the screen off when kppd applied, the colors would look funny. So give it a try, but keep that glitch in mind, you may not want the set on boot.
Sent from my LG-H811 using XDA-Developers Legacy app

suvam69 said:
Works on msm8953 chip?
Click to expand...
Click to collapse
I don't see that on savoca's list of approved chips, but neither was the G4's 8992, so feel free to give it a shot. I'd like to hear how it turns out. If it works, we can add it to the list.
Sent from my LG-H811 using XDA-Developers Legacy app

Thanks for the awesome job! This app makes KPPD so much easier to use
Btw, does anybody have a display-calibrating tool to find the right values to have the G4 calibrated to sRGB colorspace?
I'm asking because most of the internet content is sRGB so it would be amazing to achieve a better calibration on our G4 (which has horrible factory calibration).
Thanks in advance

Hello!
Im using a RN4x with snapdragon 625. I can't get that app to be working :/ i gave it already root permissions and to memory, but it still says "Error: Please check permissions". What's wrong?

ReDuXX528 said:
Hello!
Im using a RN4x with snapdragon 625. I can't get that app to be working :/ i gave it already root permissions and to memory, but it still says "Error: Please check permissions". What's wrong?
Click to expand...
Click to collapse
Cheers,
reporting the same issue on latest Xiaomi.eu Beta-7.7.20 and working Magisk 13.3 on a Xiaomi Redmi Note 4 Global Edition.
Logcat reports the following for the application using
Code:
adb logcat *:W
Code:
07-27 16:48:37.904 9538 9538 W System.err: java.io.FileNotFoundException: /storage/emulated/0/kppd (Permission denied)
07-27 16:48:37.905 9538 9538 W System.err: at java.io.FileOutputStream.open(Native Method)
07-27 16:48:37.905 9538 9538 W System.err: at java.io.FileOutputStream.<init>(FileOutputStream.java:221)
07-27 16:48:37.905 9538 9538 W System.err: at java.io.FileOutputStream.<init>(FileOutputStream.java:108)
07-27 16:48:37.905 9538 9538 W System.err: at com.alaskalinuxuser.kppdcontrol.InstallActivity.installKPPD(InstallActivity.java:84)
07-27 16:48:37.905 9538 9538 W System.err: at java.lang.reflect.Method.invoke(Native Method)
07-27 16:48:37.905 9538 9538 W System.err: at android.support.v7.app.AppCompatViewInflater$DeclaredOnClickListener.onClick(AppCompatViewInflater.java:288)
07-27 16:48:37.905 9538 9538 W System.err: at android.view.View.performClick(View.java)
07-27 16:48:37.905 9538 9538 W System.err: at android.view.View$PerformClick.run(View.java)
07-27 16:48:37.905 9538 9538 W System.err: at android.os.Handler.handleCallback(Handler.java)
07-27 16:48:37.905 9538 9538 W System.err: at android.os.Handler.dispatchMessage(Handler.java)
07-27 16:48:37.905 9538 9538 W System.err: at android.os.Looper.loop(Looper.java)
07-27 16:48:37.905 9538 9538 W System.err: at android.app.ActivityThread.main(ActivityThread.java)
07-27 16:48:37.905 9538 9538 W System.err: at java.lang.reflect.Method.invoke(Native Method)
07-27 16:48:37.905 9538 9538 W System.err: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java)
07-27 16:48:37.905 9538 9538 W System.err: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java)
This is the output when not searching for warnings and above:
Code:
07-27 16:50:57.920 9538 9538 W System.err: java.io.FileNotFoundException: /storage/emulated/0/kppd (Permission denied)
07-27 16:50:57.920 9538 9538 W System.err: at java.io.FileOutputStream.open(Native Method)
07-27 16:50:57.920 9538 9538 W System.err: at java.io.FileOutputStream.<init>(FileOutputStream.java:221)
07-27 16:50:57.920 9538 9538 W System.err: at java.io.FileOutputStream.<init>(FileOutputStream.java:108)
07-27 16:50:57.920 9538 9538 W System.err: at com.alaskalinuxuser.kppdcontrol.InstallActivity.installKPPD(InstallActivity.java:84)
07-27 16:50:57.920 9538 9538 W System.err: at java.lang.reflect.Method.invoke(Native Method)
07-27 16:50:57.920 9538 9538 W System.err: at android.support.v7.app.AppCompatViewInflater$DeclaredOnClickListener.onClick(AppCompatViewInflater.java:288)
07-27 16:50:57.921 9538 9538 W System.err: at android.view.View.performClick(View.java)
07-27 16:50:57.921 9538 9538 W System.err: at android.view.View$PerformClick.run(View.java)
07-27 16:50:57.921 9538 9538 W System.err: at android.os.Handler.handleCallback(Handler.java)
07-27 16:50:57.921 9538 9538 W System.err: at android.os.Handler.dispatchMessage(Handler.java)
07-27 16:50:57.921 9538 9538 W System.err: at android.os.Looper.loop(Looper.java)
07-27 16:50:57.921 9538 9538 W System.err: at android.app.ActivityThread.main(ActivityThread.java)
07-27 16:50:57.921 9538 9538 W System.err: at java.lang.reflect.Method.invoke(Native Method)
07-27 16:50:57.921 9538 9538 W System.err: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java)
07-27 16:50:57.921 9538 9538 W System.err: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java)

AlaskaLinuxUser said:
This actually does not require an unlocked boot loader. The KPPD daemon runs in user space, but root is required. I have only tested on the T-Mobile G4, but it should work on any rooted G4.
I would appreciate hearing your results if you have time to test it.
Click to expand...
Click to collapse
I gave it a try. No luck. Doesn't work for rooted Verizon LG G4. When I open the app it prompts me for root which I grant. Then I click the install button and the phone restarts. I open the app again and there is no control panel it only shows the install button again. Tried it a few times with the same results.

Related

force closing widget

Hello I'm running sacs moar s5 v5 port with the sleep kernel but I have tried going back to stock I have flashed to the stockfish 4.4.4 ROM I've tried different nc5 ROMs and this one widget force closes I wrote the developer but they said there's nothing wrong that should be making the widget force close my wife has the same phone running stockish 4.4.4 and the widget works fine and it used to work fine on mine the problem started when I first flashed sacs moar ROM s5 port v1 with the v1 fixes and now no matter what I do it want work and the app to me is a must have here's a logcat if anybody can explain what's going on and maybe how to fix it I would thank you so much all the widget name is Alabama live clock widget made by smartphone technologies
https://www.dropbox.com/s/z9a0tk4hvwjlobh/Log_2014-10-30_23-10-43.txt?dl=0
Any help is good help
Here's a link to the app https://play.google.com/store/apps/details?id=com.smartPhones.clockwidget.ncaa.live.alabama_AND
I've also formatted my phone and reflashed still force close its like its not seeing that I paid or something
uknow said:
Any help is good help
Here's a link to the app https://play.google.com/store/apps/details?id=com.smartPhones.clockwidget.ncaa.live.alabama_AND
I've also formatted my phone and reflashed still force close its like its not seeing that I paid or something
Click to expand...
Click to collapse
I'm no expert at reading logcats, nor do I know anything about the app that you installed, but from what I can tell, the app sets up an XML file that says which widgets you have bought. It appears that the widget is having a tough time reading from that XML file.
Code:
10-30 22:58:20.588 3252 3252 W System.err: java.text.ParseException: Unparseable date: "0" (at offset 1)
10-30 22:58:20.588 3252 3252 W System.err: at java.text.DateFormat.parse(DateFormat.java:555)
10-30 22:58:20.588 3252 3252 W System.err: at com.college.ClockPro.MainActivity.readPurchaseXML(MainActivity.java:486)
10-30 22:58:20.588 3252 3252 W System.err: at com.college.ClockPro.MainActivity.checkPurchase(MainActivity.java:451)
10-30 22:58:20.588 3252 3252 W System.err: at com.college.ClockPro.MainActivity.onCreate(MainActivity.java:267)
It's possible that even though you wiped your phone, that there were leftover files on the device which the app is continuing to try to use. Can you go through these steps ans see if it helps?
Install your favorite ROOT file explorer. I personally use ES File Explorer, but you can choose any that has root access.
Uninstall the Alabama Live Clock App
Find the following folders and delete them (if they exist):
/InternalStorage/Android/data/com.smartPhones.clockwidget.ncaa.live.alabama_AND
/ExternalStorage/Android/data/com.smartPhones.clockwidget.ncaa.live.alabama_AND
Reinstall the Live Clock App.

[GUIDE][ULTIMATE][Noobs-friendly]How to fix bugs and bootloop on a ported roms

I Think this Guide going to help u lot
With this guide i think u will make a stable rom
So lets Start
1.)For fixing Bootloop when porting rom
Replace :
Code:
/system/lib/libandroid_runtime.so
/system/lib/libandroid_servers.so
/system/lib/libmedia_jni.so
*Repack boot.image
2.)Showing black screen after boot
Replace:
Code:
/system/lib/libMali.so
3.)Fixing Sensors
Replace:
Code:
/system/bin/akmd*
/system/lib/libsensors.so
/system/lib/libms3c_yamaha.so
/system/etc/firmware (folder)
/system/bin/servicemanager
4.)Fixing Bluetooth\Wifi not turning On\Off
Replace:
Code:
/system\lib\module\mtk_stp_wmt
5.) Fixing RadioFM
Replace:
Code:
\system\bin\fmradio
\system\etc\firmware\mt6620_patch_e3_hdr.bin
\system\etc\firmware\mt6620_patch_e6_hdr.bin
\system\etc\firmware\WMT.CFG
\system\lib\modules\mtk_fm_drv.ko
\system\lib\libfmcust.so
6.) Fixing Bluetooth
Replace:
Code:
/system/bin/bd_prov
/system/bin/uim*
/system/bin/hcid
/system/bin/bluetooth*
/system/bin/hciattach
/system/bin/sdptool
/system/xbin/hciconfig
/system/bin/brcm_patchram_plus
/system/lib/libbluetooth_mtk.so
/system/lib/libbluetoothem_mtk.so
7.) Fixing Wifi
Replace:
Code:
Wifi :
/system/bin/netcfg
/system/bin/dhcpcd
/system/bin/ifconfig
/system/bin/hostap
/system/bin/hostapd
/system/bin/hostapd_bin
/system/bin/pcscd
/system/bin/wlan*
/system/bin/wpa*
/system/bin/netd -> Fix wifi hotspot
/system/lib/libhardwarelegacy.so -> Fix wifi /system/lib/modules/mtk_stp_wmt.ko/system/lib/modules/mtk_wmt_wifi.ko
/system/etc/wifi (folder)
/system/etc/firmware (folder)
8.) Fixing Camera
Replace :
Code:
system/lib/libfeatureio.so - camera not working
/system/etc/media_profiles.xml
/system/lib/libcamera.so
/system/lib/liboemcamera.so
\system\lib\hw\camera.default.so
\system\lib\libcamera_client.so
\system\lib\libcameracustom.so
\system\lib\libcamer aprofile.so
\system\lib\libcameraservice.so
\system\lib\libmhal.so
\system\lib\libmhalcontent.s o
\system\lib\libmhaldrv.so
\system\lib\libmhalmdp.so
\system\lib\libmhalpipe.so
\system\lib\libmhalscenario.so
\system\lib\libmhalutility.so
\system\etc\permission\android.hardware.camera.front.xml
\system\lib\libOmx*.so -fix camcoder
\system\lib\libfeatureo.so -fix cam focus
# camera not working or force close or any other problem
copy all libs starting with /libcam*.so
#Camera showing wrong model in pic property?
Change model in build.prop
Still not working? Replace following file from STOCK to PORT
system/lib/libexif.so
9.)Fixing SD card/memory
Replace:
Code:
/system/bin/vold
\system\etc\vold.fstab -> edit file for swap internal and external
\system\etc\vold.fstab.nand
10.)Fixing Storage Not mounting
Replace:
Code:
Decompile framework-res.apk using apktool or apk multitool and replace following file from STOCK framework-res.apk to PORT framework-res.apk
/res/xml/storage_list.xml
11.) Fixing GPS
Replace:
Code:
\system\xbin\libmnlp
/system/etc/gps.conf
12.) Fixing Touch Screen(Haptic)
Replace :
Code:
/system/usr
/system/usr\keylayout\Generic.kl ->fix HomeKey
13.) Fixing Sim1/2 (RIL)
Replace:
Code:
\system\etc\firmware\modem.img
\system\etc\permission (RIL)
/system/bin/stmd
/system/bin/rild*
/system/etc/rril
14.) Fixing Audio/Sound
Relace:
Code:
\system\lib\libaudio* .so
15.) Fixing Network / 3G Network
Replace:
Code:
/ system / etc / agps_profiles_conf
/ system / etc / APNs-conf
/ system / etc / epo-conf
/ system / etc / spn-conf
/ system / etc / virtual-spn-conf-by-efspn
/ system / etc / virtual-spn-conf-by-IMSI
16.)Fixing Pixalation in video
Replace:
Code:
Replace following file from STOCK to PORT or Port to ur Ported rom
system/lib/libvcodecdrv.so
---------------------------------------------------------------
Note Some file will not be there so dont worry jst skip it
And last thing Dont forget to Press Thanks If this helped .......................:good:​
Reserved
Thank you @adityaupreti ... i need this badly.... I will try to fix the bugs in my port ROM using this guide bro.....whenever i hav time......Thanks A lot bro
Please elaborate for bootloop.
as you said replace these files from port system folder & repack your boot image.
what changes it will make to boot image ?
will this work for 32 bit or 64 bit ?
---------- Post added at 09:48 AM ---------- Previous post was at 09:07 AM ----------
what if stuck at boot animation ?
rajlko said:
Please elaborate for bootloop.
as you said replace these files from port system folder & repack your boot image.
what changes it will make to boot image ?
will this work for 32 bit or 64 bit ?
---------- Post added at 09:48 AM ---------- Previous post was at 09:07 AM ----------
what if stuck at boot animation ?
Click to expand...
Click to collapse
rajlko said:
Please elaborate for bootloop.
as you said replace these files from port system folder & repack your boot image.
what changes it will make to boot image ?
will this work for 32 bit or 64 bit ?
---------- Post added at 09:48 AM ---------- Previous post was at 09:07 AM ----------
what if stuck at boot animation ?
Click to expand...
Click to collapse
whats ur phone model and what is the model of phone ur porting?
brownstyle said:
whats ur phone model and what is the model of phone ur porting?
Click to expand...
Click to collapse
ze550kl, 5.0.2 ( https://www.asus.com/in/Phone/ZenFone-2-Laser-ZE550KL/HelpDesk_Download/ 1.16.40.763) & YU Lettuce 12.0 version. (https://download.cyanogenmod.org/get/jenkins/124086/cm-12-20150901-SNAPSHOT-YNG4NAO254-lettuce.zip)
adityaupreti said:
Click to expand...
Click to collapse
Dear,
Please provide a solution, your solution does not work & it s still in bootloop, you have replied with
rajlko said:
ze550kl, 5.0.2 ( https://www.asus.com/in/Phone/ZenFone-2-Laser-ZE550KL/HelpDesk_Download/ 1.16.40.763) & YU Lettuce 12.0 version. (https://download.cyanogenmod.org/get/jenkins/124086/cm-12-20150901-SNAPSHOT-YNG4NAO254-lettuce.zip)
Click to expand...
Click to collapse
i think huawei honor 4x is a better option
brownstyle said:
i think huawei honor 4x is a better option
Click to expand...
Click to collapse
4x have 5.1 but base rom is 5.0.2.
rajlko said:
Dear,
Please provide a solution, your solution does not work & it s still in bootloop, you have replied with
Click to expand...
Click to collapse
It will not work coz ur porting a marshmallow or lollipop based ROM
Use any other guide of porting and then come to my threadto fix bugs
rajlko said:
ze550kl, 5.0.2 ( https://www.asus.com/in/Phone/ZenFone-2-Laser-ZE550KL/HelpDesk_Download/ 1.16.40.763) & YU Lettuce 12.0 version. (https://download.cyanogenmod.org/get/jenkins/124086/cm-12-20150901-SNAPSHOT-YNG4NAO254-lettuce.zip)
Click to expand...
Click to collapse
thanx for providing this link but when i try to flash it says E:footer is wrong installation aborted.we have the same device asus ze550kl..wat could have been the problem?
brownstyle said:
thanx for providing this link but when i try to flash it says E:footer is wrong installation aborted.we have the same device asus ze550kl..wat could have been the problem?
Click to expand...
Click to collapse
asus signature verification process is totally different. , I have provided both link so that any one may try to port it.
both having same version android, same cpu, same gpu.
rajlko said:
asus signature verification process is totally different. , I have provided both link so that any one may try to port it.
both having same version android, same cpu, same gpu.
Click to expand...
Click to collapse
is there any way to bypass that verification process?any other workaround?
what are the lib files for bluetooth in Marshmallow for Qualcomm devices ? I have found libbluetooth_jni.so but replacing it didn't fix the issue. What other files do I have to replace?
Great Work
Thanks for this guide
ROBERT CM said:
Great Work
Thanks for this guide
Click to expand...
Click to collapse
Ur welcome
Hi adi bro.
I have cm 12.1 ROM but in camera video recording is not working can u tell me how to fix it??
Man trying get wifi on this port to the s6 i found some files which i moved then bingo wifi turned on scanning put password in now its saying Failed to obtain IP address any tips some the files just arnt there. I got 920p S6
Jimmy1life said:
Man trying get wifi on this port to the s6 i found some files which i moved then bingo wifi turned on scanning put password in now its saying Failed to obtain IP address any tips some the files just arnt there. I got 920p S6
Click to expand...
Click to collapse
Always when i had that problem, i had to go to system/etc/dhcpcd and change the permission of dhcpcd-run-hooks so that "Owner", "Group" and "Others" can execute. Also in build.prop you can change ro.secure.storage=true to false (if it's not already). This is usaly for not saving the password but worth a try.
And by the way if someone has more knowledgement than me:
I'm on the Note Edge and therefor does no exist a CM 13 version. I have read somewhere you can do it also with a sammy rom as base. So i took a S7 edge rom and a Note edge rom, both 6.0.1. I get it to flash and boot but endless boot. I pulled the prev_dump.log to get the errors but all i can see is this
Code:
01-01 00:11:15.899 17542 17542 I boot_progress_system_run: 680900
01-01 00:11:15.999 17542 17542 W SystemConfig: [COLOR="red"]Got exception parsing permissions[/COLOR].
01-01 00:11:15.999 17542 17542 W SystemConfig: [COLOR="red"]org.xmlpull.v1.XmlPullParserException: No start tag found[/COLOR]
01-01 00:11:15.999 17542 17542 W SystemConfig: at com.android.server.SystemConfig.readPermissionsFromXml(SystemConfig.java:275)
01-01 00:11:15.999 17542 17542 W SystemConfig: at com.android.server.SystemConfig.readPermissions(SystemConfig.java:197)
01-01 00:11:15.999 17542 17542 W SystemConfig: at com.android.server.SystemConfig.(SystemConfig.java:157)
01-01 00:11:15.999 17542 17542 W SystemConfig: at com.android.server.SystemConfig.getInstance(SystemConfig.java:110)
01-01 00:11:15.999 17542 17542 W SystemConfig: at com.android.server.pm.PackagePrefetcher.prefetchPermissions(PackagePrefetcher.java:251)
01-01 00:11:15.999 17542 17542 W SystemConfig: at com.android.server.SystemServer.run(SystemServer.java:420)
01-01 00:11:15.999 17542 17542 W SystemConfig: at com.android.server.SystemServer.main(SystemServer.java:363)
01-01 00:11:15.999 17542 17542 W SystemConfig: at java.lang.reflect.Method.invoke(Native Method)
01-01 00:11:15.999 17542 17542 W SystemConfig: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1230)
01-01 00:11:15.999 17542 17542 W SystemConfig: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1120)
01-01 00:11:16.059 17542 17630 W ResourceType: Failure getting entry for 0x7f020020 (t=1 e=32) (error -75)
01-01 00:11:16.059 17542 17630 D PackagePrefetcher: put: /system/app/ANTRadioService
01-01 00:11:16.089 702 866 E BootAnimationLoader: [email protected] : ####Clear Cover is closed####
01-01 00:11:16.099 17542 17542 D AndroidRuntime: Shutting down VM
01-01 00:11:16.099 17542 17542 E AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: main
01-01 00:11:16.099 17542 17542 E AndroidRuntime:[COLOR="red"] java.lang.UnsatisfiedLinkError: dlopen failed: cannot locate symbol "TZ_CCM_register_default" referenced by "/system/lib/libandroid_servers.so"...[/COLOR]
01-01 00:11:16.099 17542 17542 E AndroidRuntime: at java.lang.Runtime.loadLibrary(Runtime.java:372)
01-01 00:11:16.099 17542 17542 E AndroidRuntime: at java.lang.System.loadLibrary(System.java:1076)
01-01 00:11:16.099 17542 17542 E AndroidRuntime: at com.android.server.SystemServer.run(SystemServer.java:463)
01-01 00:11:16.099 17542 17542 E AndroidRuntime: at com.android.server.SystemServer.main(SystemServer.java:363)
01-01 00:11:16.099 17542 17542 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
01-01 00:11:16.099 17542 17542 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1230)
01-01 00:11:16.099 17542 17542 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1120)
01-01 00:11:16.119 17542 17629 D PackagePrefetcher: put: /system/app/AllShareCastPlayer
01-01 00:11:16.149 17542 17542 E android.os.Debug: ro.product_ship = true
01-01 00:11:16.149 17542 17542 E android.os.Debug: ro.debug_level = 0x4f4c
01-01 00:11:16.149 17542 17542 E android.os.Debug: sys.mobilecare.preload = false
01-01 00:11:16.149 17542 17542 E AndroidRuntime: Error reporting crash
01-01 00:11:16.149 17542 17542 E AndroidRuntime: java.lang.NullPointerException: Attempt to invoke interface method 'void android.app.IActivityManager.handleApplicationCrash(android.os.IBinder, android.app.ApplicationErrorReport$CrashInfo)' on a null object reference
01-01 00:11:16.149 17542 17542 E AndroidRuntime: at com.android.internal.os.RuntimeInit$UncaughtHandler.uncaughtException(RuntimeInit.java:96)
01-01 00:11:16.149 17542 17542 E AndroidRuntime: at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:693)
01-01 00:11:16.149 17542 17542 E AndroidRuntime: at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:690)
01-01 00:11:16.149 17542 17542 I Process : Sending signal. PID: 17542 SIG: 9
01-01 00:11:16.179 702 866 E BootAnimationLoader: [email protected] : ####Clear Cover is closed####
01-01 00:11:16.209 16339 16339 [COLOR="Red"]E Zygote : Exit zygote because system server (17542) has terminated[/COLOR]
But i don't know how to solve it.
Or is it kernel related because of selinux (i use stock Note edge)?
Code:
[ 537.872906] init: Warning! Service gatekeeperd needs a SELinux domain defined; please fix!
[ 537.873485] init: Warning! Service gpu_snapshotd needs a SELinux domain defined; please fix!
[ 537.873938] init: Warning! Service thermal-engine needs a SELinux domain defined; please fix!
[ 537.874395] init: Warning! Service imsqmidaemon needs a SELinux domain defined; please fix!
[ 537.874892] init: Warning! Service mdm_helper needs a SELinux domain defined; please fix!
[ 537.875353] init: Warning! Service mdm_helper_proxy needs a SELinux domain defined; please fix!
[ 537.886664] init: cannot execve('/system/bin/mdm_helper_proxy'): Permission denied
[ 537.887518] init: cannot execve('/system/bin/mdm_helper'): Permission denied
[ 537.887717] init: property_set("ro.service.mdm_helper_restarted", "true") failed
[ 537.888674] init: setgid failed: Invalid argument
[ 537.890330] init: cannot execve('/system/vendor/bin/thermal-engine'): Permission denied
[ 537.891130] init: cannot execve('/system/bin/gpu_snapshotd'): Permission denied
[ 537.891871] init: cannot execve('/system/bin/gatekeeperd'): Permission denied
Or is it completly nonsens?
Thank you.
prev_dump.log

[ROM][MONTANA][UNOFFICIAL] LineageOS 14.1

LineageOS 14.1
{
"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"
}
​
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Prerequisites
Bootloader unlock > HERE
Recovery twrp > squid2 or sevenmaxs
What works
RIL (dual sim, volte)
WIFI
Tethering
Camera
Bluetooth
Sensors
MTP
Sound
Fingerprint
NFC
MotoActions
- - SELinux: enforcing
Todo
Fix "Enable on-screen nav-bar" toggling option.
Download
https://www.androidfilehost.com/?w=files&flid=251047 AFH LOS7 Files
https://opengapps.org/ OpenGApps - Choose ARM/7.1/PICO or NANO
Source
Device: https://github.com/kayesk/android_device_motorola_montana
Vendor: https://github.com/kayesk/android_vendor_motorola_montana
Branch: cm-14.1
How to install the rom ?
Copy the rom to your G5S.
Restart in recovery (squid or Sevenmaxs)
Take a backup of existing ROM.
Wipe clean (Cache, Data, Dalvik/ART, System)
Install ROM.
Make a wipe cache.
Reboot System.
Initial load would take time.
Contributions :
@GoldeneyeS2 for fixing OEM bloatware, NFC and releasetools script.
THANKS TO :
@squid2 for twrp
@SevenMaxs for twrp
All other users who provided support, valuable suggestions and productive comments.
Report bugs with proper logcat details.
Device is unrooted. Root using Magisk works.
Thanks
KS
Nice,happy new year!
customs on g5s incomming
Thanks, HAPPY NEW YEAR
good job my friend and thank you for your work
Happy new year .
Video recording - FIXED
FIXED another issue with MTP.
NFC selinux rules are added - SOMEONE PLEASE VERIFY IF IT WORKS.
NEW BUILD: lineage-14.1-20171231_060004-UNOFFICIAL-montana.zip
Link: Same as in topic.
Thanks
KS
Awesome work! Works fine, no bugs until right now, BUT
one thing about the moto devices that i love, is the moto actions and the moto display, how to keep them?
Have some flashable lib from stock? Can you Add or teach how to use it? I need one hand navigation on the fingerprint sensor.
Thx
Great work...i was trying for this but failed...now u can expect Oreo ROMs too
kalyansundhar said:
Video recording - FIXED
FIXED another issue with MTP.
NFC selinux rules are added - SOMEONE PLEASE VERIFY IF IT WORKS.
NEW BUILD: lineage-14.1-20171231_060004-UNOFFICIAL-montana.zip
Link: Same as in topic.
Thanks
KS
Click to expand...
Click to collapse
can u please push kernel sources...i can help fixing moto acions
Happy new year.
NFC is not working. I don't see it in the settings.
Tomorrow more time....
Anyone drop screenshots
govind1233 said:
Anyone drop screenshots
Click to expand...
Click to collapse
Tomorrow I will do. But its just lineage 14.1.
The ROM is based on the stock version. Some services are still from Motorola.
Following bug I found:
The first time you watch a full screen video. You will get a message about it. Portrait modes there is no problem but in landscape you will see a weird thing happening with the message and the video.
Thanks so much for developping a rom for this device, because not a lot a developper make something for this device contrary to the dev arround the moto g5s plus. And happy new year.
govind1233 said:
Anyone drop screenshots
Click to expand...
Click to collapse
Done.
GoldeneyeS2 said:
Tomorrow I will do. But its just lineage 14.1.
The ROM is based on the stock version. Some services are still from Motorola.
Following bug I found:
The first time you watch a full screen video. You will get a message about it. Portrait modes there is no problem but in landscape you will see a weird thing happening with the message and the video.
Click to expand...
Click to collapse
Thank you very much for making a rom for the Moto G5S. Are you aware of the bug in the developer options and Moto Actios does not work? Sorry for any mistake in English.
Doug.97 said:
Thank you very much for making a rom for the Moto G5S. Are you aware of the bug in the developer options and Moto Actios does not work? Sorry for any mistake in English.
Click to expand...
Click to collapse
Yes. I am aware of the issues you mentioned.
@govind1233, I have published kernel code as well https://github.com/kayesk/android_kernel_motorola_msm8937.
Can someone confirm NFC support in this device? Mine is XT1795 (India) and I don't see NFC support.
Also I have one confusion. If I add MotoActions apk to code, will it interfere with CMActions?
Thanks
KS
Please release kernel sources
kalyansundhar said:
Can someone confirm NFC support in this device? Mine is XT1795 (India) and I don't see NFC support.
KS
Click to expand...
Click to collapse
I have the XT1794 with NFC. I dont see the nfc in settings.
I also try to get it working.
Maybe its something with settings.apk??? Did you also copy that from the G5???
@kalyansundhar
Are now working building or still copying and pasting? you can better upload your system.img and boot.img to github(extract).
kalyansundhar said:
Yes. I am aware of the issues you mentioned.
@govind1233, I have published kernel code as well https://github.com/kayesk/android_kernel_motorola_msm8937.
Can someone confirm NFC support in this device? Mine is XT1795 (India) and I don't see NFC support.
Also I have one confusion. If I add MotoActions apk to code, will it interfere with CMActions?
Thanks
KS
Click to expand...
Click to collapse
Thanks bro
---------- Post added at 04:35 PM ---------- Previous post was at 03:35 PM ----------
kalyansundhar said:
Yes. I am aware of the issues you mentioned.
@govind1233, I have published kernel code as well https://github.com/kayesk/android_kernel_motorola_msm8937.
Can someone confirm NFC support in this device? Mine is XT1795 (India) and I don't see NFC support.
Also I have one confusion. If I add MotoActions apk to code, will it interfere with CMActions?
Thanks
KS
Click to expand...
Click to collapse
For Moto actions to work u need proper commits for cmactions
GoldeneyeS2 said:
I have the XT1794 with NFC. I dont see the nfc in settings.
I also try to get it working.
Maybe its something with settings.apk??? Did you also copy that from the G5???
@kalyansundhar
Are now working building or still copying and pasting? you can better upload your system.img and boot.img to github(extract).
Click to expand...
Click to collapse
Well, I am doing little bit here and there with whatever limited experience I have.
My main concern now is my lack of understanding on how everything fits in the big picture. And without knowing it if I make some change that shouldn't be screwing up something which works fine.
I think it is better for me to stop here, so that good developers could take it further. Anyway the repositories are public.
I cannot push system.img to github because of file size limitation. File size is 900MB and allowed limit is 100MB.
I would share it in my onedrive account and publish the link.
Bugs so far:
1) Developer options - Getting selinux permission issue which is blocked by global rule. I don't know how to override a global rule.
2) Moto Actions - Not working.
3) NFC - Getting zygote error related to seapp_context.
Code:
01-02 21:32:58.857 1534 1593 E ActivityManager: android.util.Log$TerribleFailure: Removing process that hasn't been killed: ProcessRecord{ffc4c99 8487:com.android.nfc/1027}
01-02 21:32:58.857 1534 1593 E ActivityManager: at android.util.Log.wtf(Log.java:295)
01-02 21:32:58.857 1534 1593 E ActivityManager: at android.util.Slog.wtfStack(Slog.java:98)
01-02 21:32:58.857 1534 1593 E ActivityManager: at com.android.server.am.ActivityManagerService.removeLruProcessLocked(ActivityManagerService.java:3419)
01-02 21:32:58.857 1534 1593 E ActivityManager: at com.android.server.am.ActivityManagerService.processStartTimedOutLocked(ActivityManagerService.java:6611)
01-02 21:32:58.857 1534 1593 E ActivityManager: at com.android.server.am.ActivityManagerService.-wrap13(ActivityManagerService.java)
01-02 21:32:58.857 1534 1593 E ActivityManager: at com.android.server.am.ActivityManagerService$MainHandler.handleMessage(ActivityManagerService.java:1895)
01-02 21:32:58.857 1534 1593 E ActivityManager: at android.os.Handler.dispatchMessage(Handler.java:102)
01-02 21:32:58.857 1534 1593 E ActivityManager: at android.os.Looper.loop(Looper.java:154)
01-02 21:32:58.857 1534 1593 E ActivityManager: at android.os.HandlerThread.run(HandlerThread.java:61)
01-02 21:32:58.857 1534 1593 E ActivityManager: at com.android.server.ServiceThread.run(ServiceThread.java:46)
01-02 21:32:58.872 8500 8500 E SELinux : seapp_context_lookup: No match for app with uid 1027, seinfo default, name com.android.nfc
01-02 21:32:58.873 8500 8500 E SELinux : selinux_android_setcontext: Error setting context for app with uid 1027, seinfo default: No such file or directory
01-02 21:32:58.873 8500 8500 E Zygote : selinux_android_setcontext(1027, 0, "default", "com.android.nfc") failed
01-02 21:32:58.873 8500 8500 F art : art/runtime/jni_internal.cc:492] JNI FatalError called: frameworks/base/core/jni/com_android_internal_os_Zygote.cpp:631: selinux_android_setcontext failed
01-02 21:32:58.905 8500 8500 F art : art/runtime/runtime.cc:422] Runtime aborting...
01-02 21:32:58.905 8500 8500 F art : art/runtime/runtime.cc:422] Aborting thread:
01-02 21:32:58.905 8500 8500 F art : art/runtime/runtime.cc:422] "main" prio=5 tid=1 Native
01-02 21:32:58.905 8500 8500 F art : art/runtime/runtime.cc:422] | group="" sCount=0 dsCount=0 obj=0x73784268 self=0xa5a05400
01-02 21:32:58.905 8500 8500 F art : art/runtime/runtime.cc:422] | sysTid=555 nice=0 cgrp=default sched=0/0 handle=0xa86de534
01-02 21:32:58.905 8500 8500 F art : art/runtime/runtime.cc:422] | state=? schedstat=( 0 0 0 ) utm=0 stm=0 core=0 HZ=100
01-02 21:32:58.905 8500 8500 F art : art/runtime/runtime.cc:422] | stack=0xbe70f000-0xbe711000 stackSize=8MB
01-02 21:32:58.905 8500 8500 F art : art/runtime/runtime.cc:422] | held mutexes= "abort lock"
01-02 21:32:58.905 8500 8500 F art : art/runtime/runtime.cc:422] kernel: (couldn't read /proc/self/task/555/stack)
01-02 21:32:58.905 8500 8500 F art : art/runtime/runtime.cc:422] native: (backtrace::Unwind failed for thread 555: Thread doesn't exist)
01-02 21:32:58.905 8500 8500 F art : art/runtime/runtime.cc:422] at com.android.internal.os.Zygote.nativeForkAndSpecialize(Native method)
01-02 21:32:58.905 8500 8500 F art : art/runtime/runtime.cc:422] at com.android.internal.os.Zygote.forkAndSpecialize(Zygote.java:95)
01-02 21:32:58.905 8500 8500 F art : art/runtime/runtime.cc:422] at com.android.internal.os.ZygoteConnection.runOnce(ZygoteConnection.java:225)
01-02 21:32:58.905 8500 8500 F art : art/runtime/runtime.cc:422] at com.android.internal.os.ZygoteInit.runSelectLoop(ZygoteInit.java:853)
01-02 21:32:58.905 8500 8500 F art : art/runtime/runtime.cc:422] at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:775)
Looks like all 3 issues boils down to selinux, file contexts, uevent permissions.
Thanks,
KS
GoldeneyeS2 said:
I have the XT1794 with NFC. I dont see the nfc in settings.
I also try to get it working.
Maybe its something with settings.apk??? Did you also copy that from the G5???
@kalyansundhar
Are now working building or still copying and pasting? you can better upload your system.img and boot.img to github(extract).
Click to expand...
Click to collapse
Uploaded boot-20180102.img and system-20180102.img to onedrive. https://1drv.ms/f/s!Ahq68S0B7zYZjmVhmIHwvYGoz3gq. Please find it within build_images subdirectory.
Thanks
KS

Porting XOSP on Lineage device trees?

Hello!
I have compiled Lineage for x2. Now I'm wondering if it would be hard to port new ROM (let's say XOSP) based on trees for other one. I heard, that it's hard to port CAF-based ROM (like XOSP is) on CM trees.
AFAIR @shivatejapeddi already tried to port XOSP to x2.
Can somebody tell me if it's possible to port ROM without deeper knowledge of AOSP guts? Or, maybe, where should I begin learning AOSP build process, if it's too hard for someone inexperienced?
Thanks!
remixn said:
Hello!
I have compiled Lineage for x2. Now I'm wondering if it would be hard to port new ROM (let's say XOSP) based on trees for other one. I heard, that it's hard to port CAF-based ROM (like XOSP is) on CM trees.
AFAIR @shivatejapeddi already tried to port XOSP to x2.
Can somebody tell me if it's possible to port ROM without deeper knowledge of AOSP guts? Or, maybe, where should I begin learning AOSP build process, if it's too hard for someone inexperienced?
Thanks!
Click to expand...
Click to collapse
if you compiled los from source then there is also source for xosp ( https://github.com/XOSP-Project/manifest ) anyway there is build of xosp ( https://androidfilehost.com/?w=files&flid=185291 ) anyway when i flashed it screen was blinking and i wasnt able even use phone.
kihope12 said:
if you compiled los from source then there is also source for xosp ( [ur l]h ttps : //gi thub.com/ XOSP-Project/m anifest[/ur l] ) anyway there is build of xosp ( [ur l]h tt ps :// an droidfilehost. com/? w=files&flid=185291[/u rl] ) anyway when i flashed it screen was blinking and i wasnt able even use phone.
Click to expand...
Click to collapse
Thank you for reply!
I already know that there is a build on AFH. I also know that there are sources for XOSP. In fact, I tried to compile XOSP using several slightly modified device trees (without success). When I was lurking across @shivatejapeddi's sources on GH, I saw that there is a modified display driver. That's one of things that make me curious.
Heyyo, eh tbh from what I've seen? It's not overly too hard. Please take a look at andr68rus dirty unicorns or his Paranoid Android which are both CAF based.
There's a chance that ROM might have a different CAF display than a different ROM (prevalent right meow in 8.1 custom ROMs such as LineageOS having a lot of changes whilst OmniROM is more of a minimal approach)
OK. Just compiled the ROM.
I'm surprised, that build process took only 20 minutes on old CPU.
Now, to the point. Flashed the ROM. Doesn't boot at all. Just freezes at bootloader screen (LeEco…). Make hasn't errored at all.
So, I have no idea, what should I do now…
UPDATE:
A kind of problem with RIL, I guess?
Hmm have you tried building with -eng build instead of userdebug or user to see if you can get ADB logcat via a PC and USB cable?
If you suspect it's RIL then yeah you could always try to swap it to CAF variant and delete the device specific variant or check what other devices on xosp use
remixn said:
OK. Just compiled the ROM.
I'm surprised, that build process took only 20 minutes on old CPU.
Now, to the point. Flashed the ROM. Doesn't boot at all. Just freezes at bootloader screen (LeEco…). Make hasn't errored at all.
So, I have no idea, what should I do now…
UPDATE:
A kind of problem with RIL, I guess?
Click to expand...
Click to collapse
only 20 minut? that is wierd, and RIL as i know (maybe i am wrong) is about singnal and sim, i dont think it can couse no boot, and you didnt event pass oem logo, you should try re-compile it maybe.
kihope12 said:
only 20 minut? that is wierd, and RIL as i know (maybe i am wrong) is about singnal and sim, i dont think it can couse no boot, and you didnt event pass oem logo, you should try re-compile it maybe.
Click to expand...
Click to collapse
Eh from my experiences with ROMs anything can cause issues. I've gotten bootloops from sensors and Bluetooth lol
kihope12 said:
only 20 minut? that is wierd, and RIL as i know (maybe i am wrong) is about singnal and sim, i dont think it can couse no boot, and you didnt event pass oem logo, you should try re-compile it maybe.
Click to expand...
Click to collapse
After recompiling it took ~40 mins. Still stuck on OEM logo :/
remixn said:
After recompiling it took ~40 mins. Still stuck on OEM logo :/
Click to expand...
Click to collapse
what edits of device tree you did?
kihope12 said:
what edits of device tree you did?
Click to expand...
Click to collapse
This is modified device tree: attps://github.com/remi6397/android_device_leeco_x2/tree/xosp-n-rebase
This is modified kernel: attps://github.com/remi6397/android_kernel_leeco_msm8996/tree/xosp-n-rebase
Modified LeEco vendor files are here: attps://github.com/remi6397/proprietary_vendor_leeco_x2/tree/xosp-n-rebase
Thank you!
remixn said:
This is modified device tree: attps://github.com/remi6397/android_device_leeco_x2/tree/xosp-n-rebase
This is modified kernel: attps://github.com/remi6397/android_kernel_leeco_msm8996/tree/xosp-n-rebase
Modified LeEco vendor files are here: attps://github.com/remi6397/proprietary_vendor_leeco_x2/tree/xosp-n-rebase
Thank you!
Click to expand...
Click to collapse
Man i am not dev, i just know very basic i can atleas give you xda thread where is how build rom from source
kihope12 said:
Man i am not dev, i just know very basic i can atleas give you xda thread where is how build rom from source
Click to expand...
Click to collapse
I've read several threads already. Also, I've changed only several makefiles. Nothing directly related to programming. Anyway, I'll try to fix something, then compile it again, and again…
remixn said:
This is modified device tree: attps://github.com/remi6397/android_device_leeco_x2/tree/xosp-n-rebase
This is modified kernel: attps://github.com/remi6397/android_kernel_leeco_msm8996/tree/xosp-n-rebase
Modified LeEco vendor files are here: attps://github.com/remi6397/proprietary_vendor_leeco_x2/tree/xosp-n-rebase
Thank you!
Click to expand...
Click to collapse
Heyyo, it's the kernel. That's the AOSPA Le Pro3 kernel that is made by GalaticStryder that isn't ported to the Le Max2 yet. I tried but ran out of personal time... It would require quite a bit of work to get functional for the Le Max2. Boot DTS files, firmware, missing drivers and so on.
Also, andr68rus based ROMs are not EAS compatible just in case that's something you really want.
I'd recommend using this kernel instead:
https://github.com/1nfrag/android_kernel_leeco_msm8996/tree/bsi?files=1
Or if you want EAS based kernel I'd recommend checking out SlimRoms For EAS compatible device tree, kernel and vendor blobs.
https://github.com/slim-x2
Sorry I should have been a little more specific with my information on that first post. My bad.
Ok… I've got several errors on boot, mainly from surfaceflinger.
Log: https://pastebin.com/sXDB1u0Y
Vendor: attps://github.com/slim-x2/proprietary_vendor_leeco-2
Device tree: attps://github.com/slim-x2/android_device_leeco_x2-old
----
Now I'm trying with device: attps://github.com/slim-x2/android_device_leeco_x2 + attps://github.com/slim-x2/device_leeco_msm8996-common
I've got a compile error:
Code:
ninja: error: '/home/remi/android-buildenv/xosp/out/target/product/x2/obj_arm/SHARED_LIBRARIES/libsrsprocessing_intermediates/export_includes', needed by '/home/remi/android-buildenv/xosp/out/target/product/x2/obj_arm/SHARED_LIBRARIES/libaudioflinger_intermediates/import_includes', missing and no known rule to make it
or without SRS_TRUEMEDIA:
Code:
ninja: error: 'vendor/leeco/x2/proprietary/vendor/etc/audio_output_policy_letv.conf', needed by '/home/remi/android-buildenv/xosp/out/target/product/x2/system/vendor/etc/audio_output_policy_letv.conf', missing and no known rule to make it
Heyyo, @moto999999 can you please give him some directions as to which branches he should be using?
I better play it safe and ask him directly just to help things along
Ok. Now it boots… and almost works (it even makes a sound ). System dies leaving a huge amount of logs behind itself:
Here is an important part (IMO):
Code:
--------- beginning of crash
06-20 13:41:46.873 1629 1629 E AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: main
06-20 13:41:46.873 1629 1629 E AndroidRuntime: java.lang.UnsatisfiedLinkError: dlopen failed: library "libgnsspps.so" not found
06-20 13:41:46.873 1629 1629 E AndroidRuntime: at java.lang.Runtime.loadLibrary0(Runtime.java:989)
06-20 13:41:46.873 1629 1629 E AndroidRuntime: at java.lang.System.loadLibrary(System.java:1562)
06-20 13:41:46.873 1629 1629 E AndroidRuntime: at com.qualcomm.location.izatserviceprovider.service.IzatServiceBase.<clinit>(IzatServiceBase.java:199)
06-20 13:41:46.873 1629 1629 E AndroidRuntime: at java.lang.Class.newInstance(Native Method)
06-20 13:41:46.873 1629 1629 E AndroidRuntime: at android.app.ActivityThread.handleCreateService(ActivityThread.java:3198)
06-20 13:41:46.873 1629 1629 E AndroidRuntime: at android.app.ActivityThread.-wrap5(ActivityThread.java)
06-20 13:41:46.873 1629 1629 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1586)
06-20 13:41:46.873 1629 1629 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:102)
06-20 13:41:46.873 1629 1629 E AndroidRuntime: at android.os.Looper.loop(Looper.java:154)
06-20 13:41:46.873 1629 1629 E AndroidRuntime: at com.android.server.SystemServer.run(SystemServer.java:378)
06-20 13:41:46.873 1629 1629 E AndroidRuntime: at com.android.server.SystemServer.main(SystemServer.java:232)
06-20 13:41:46.873 1629 1629 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
06-20 13:41:46.873 1629 1629 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:889)
06-20 13:41:46.873 1629 1629 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:779)
So… There is a missing GPS blob (GLONASS?). I will try stealing that from some other device.
ThE_MarD said:
Heyyo, @moto999999 can you please give him some directions as to which branches he should be using?
I better play it safe and ask him directly just to help things along
Click to expand...
Click to collapse
Sure, always happy to help
remixn said:
Ok. Now it boots… and almost works (it even makes a sound ). System dies leaving a huge amount of logs behind itself:
Here is an important part (IMO):
So… There is a missing GPS blob (GLONASS?). I will try stealing that from some other device.
Click to expand...
Click to collapse
Are you trying to build nougat or oreo?
moto999999 said:
Are you trying to build nougat or oreo?
Click to expand...
Click to collapse
Nougat.
Now compiled with your slim device tree forked from LineageOS. It was a huge amount of work (never tried something like that before ) Everything I've tested so far works fine. I need to make some more tests, but maybe tomorrow.
PS: Thank you for your contributions to this device tree.
remixn said:
Nougat.
Now compiled with your slim device tree forked from LineageOS. It was a huge amount of work (never tried something like that before ) Everything I've tested so far works fine. I need to make some more tests, but maybe tomorrow.
PS: Thank you for your contributions to this device tree.
Click to expand...
Click to collapse
You should use this tree https://github.com/slim-x2/android_device_leeco_x2-old
Kernel https://github.com/moto999999/kernel_leeco_msm8996 (nougat branch)
Vendor https://github.com/slim-x2/proprietary_vendor_leeco
I don't recommend that you use my tree forked from lineage, it isn't the one I use. The forked one was just for testing

Question Official miui camera app

I've installed Lineage OS on the Mi MIX 4 and I cannot be happier after getting rid of MIUI, but now I'm left without a proper camera app. I installed GCAM but not everything works at the moment.
I would like to try to install the official MIUI camera app and see if by any chance it works, but I forgot to extract the apk before flashing Lineage OS.
Can someone who has MIUI installed upload the apk in this thread, or know where I can get it? For example using an extractor like this one:
Apk Extractor - Apps on Google Play
Extracts installed applications on your device and places them on your SD card.
play.google.com
Thanks a lot!
You can find the Xiaomi Camera apk on apkmirror.
Let us know if this works!
Aleksanderbjorn said:
You can find the Xiaomi Camera apk on apkmirror.
Let us know if this works!
Click to expand...
Click to collapse
Thanks for the suggestion! Unfortunately, it crashes on launch (I installed this one).
Stacktrace:
Spoiler: Stacktrace
Code:
2022-03-17 08:03:05.314 31800-31800/? D/MiCameraAlgo: init: E
2022-03-17 08:03:05.314 31800-31800/? D/MiCameraAlgo: init: application file path to algorithm lib: /data/user/0/com.android.camera/files
2022-03-17 08:03:05.314 31800-31800/? E/MiCamAlgoInterfaceJNI: start loading camera_algoup_jni.xiaomi
2022-03-17 08:03:05.316 31800-31800/? E/MiCamAlgoInterfaceJNI: can not load library:camera_algoup_jni.xiaomi : java.lang.UnsatisfiedLinkError: dlopen failed: library "libcamera_algoup_jni.xiaomi.so" not found
at java.lang.Runtime.loadLibrary0(Runtime.java:1087)
at java.lang.Runtime.loadLibrary0(Runtime.java:1008)
at java.lang.System.loadLibrary(System.java:1664)
at com.xiaomi.engine.MiCamAlgoInterfaceJNI.<clinit>(MiCamAlgoInterfaceJNI.java:3)
at com.xiaomi.engine.MiCamAlgoInterfaceJNI.init(Native Method)
at com.xiaomi.engine.MiCameraAlgo.init(MiCameraAlgo.java:4)
at com.android.camera.LocalParallelService$LocalBinder.initMiviEngine(LocalParallelService.java:4)
at com.android.camera.LocalParallelService$LocalBinder.<init>(LocalParallelService.java:9)
at com.android.camera.LocalParallelService.onCreate(LocalParallelService.java:5)
at android.app.ActivityThread.handleCreateService(ActivityThread.java:4186)
at android.app.ActivityThread.access$1500(ActivityThread.java:237)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1932)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:223)
at android.app.ActivityThread.main(ActivityThread.java:7664)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
2022-03-17 08:03:05.316 31800-31800/? E/.android.camer: No implementation found for int com.xiaomi.engine.MiCamAlgoInterfaceJNI.init(java.lang.String) (tried Java_com_xiaomi_engine_MiCamAlgoInterfaceJNI_init and Java_com_xiaomi_engine_MiCamAlgoInterfaceJNI_init__Ljava_lang_String_2)
2022-03-17 08:03:05.316 31800-31800/? D/AndroidRuntime: Shutting down VM
2022-03-17 08:03:05.316 813-31855/? E/CamX: [ERROR][SENSOR ] camximagesensordata.cpp:1635 GetI2CCmdSizeForEarlySetting() EarlySettingFunc total size = 536
2022-03-17 08:03:05.316 31800-31800/? E/AndroidRuntime: FATAL EXCEPTION: main
Process: com.android.camera, PID: 31800
java.lang.UnsatisfiedLinkError: No implementation found for int com.xiaomi.engine.MiCamAlgoInterfaceJNI.init(java.lang.String) (tried Java_com_xiaomi_engine_MiCamAlgoInterfaceJNI_init and Java_com_xiaomi_engine_MiCamAlgoInterfaceJNI_init__Ljava_lang_String_2)
at com.xiaomi.engine.MiCamAlgoInterfaceJNI.init(Native Method)
at com.xiaomi.engine.MiCameraAlgo.init(MiCameraAlgo.java:4)
at com.android.camera.LocalParallelService$LocalBinder.initMiviEngine(LocalParallelService.java:4)
at com.android.camera.LocalParallelService$LocalBinder.<init>(LocalParallelService.java:9)
at com.android.camera.LocalParallelService.onCreate(LocalParallelService.java:5)
at android.app.ActivityThread.handleCreateService(ActivityThread.java:4186)
at android.app.ActivityThread.access$1500(ActivityThread.java:237)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1932)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:223)
at android.app.ActivityThread.main(ActivityThread.java:7664)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
2022-03-17 08:03:05.317 31800-31800/? E/CAM_CameraFCHandler: Camera FC, @Module = 163 And @CameraId = 0
2022-03-17 08:03:05.317 31800-31800/? E/CAM_MqsHelper: [K_PROCESS]: Error occur the reason is that CameraApp Mode:Photo[163] CameraId:0 Error:Java Crash
2022-03-17 08:03:05.318 31800-31800/? D/CAM_AfterSales: aftersales record not enable in this device
2022-03-17 08:03:05.318 31800-31800/? E/CAM_CameraFCHandler: Camera FC, msg=No implementation found for int com.xiaomi.engine.MiCamAlgoInterfaceJNI.init(java.lang.String) (tried Java_com_xiaomi_engine_MiCamAlgoInterfaceJNI_init and Java_com_xiaomi_engine_MiCamAlgoInterfaceJNI_init__Ljava_lang_String_2)
java.lang.UnsatisfiedLinkError: No implementation found for int com.xiaomi.engine.MiCamAlgoInterfaceJNI.init(java.lang.String) (tried Java_com_xiaomi_engine_MiCamAlgoInterfaceJNI_init and Java_com_xiaomi_engine_MiCamAlgoInterfaceJNI_init__Ljava_lang_String_2)
at com.xiaomi.engine.MiCamAlgoInterfaceJNI.init(Native Method)
at com.xiaomi.engine.MiCameraAlgo.init(MiCameraAlgo.java:4)
at com.android.camera.LocalParallelService$LocalBinder.initMiviEngine(LocalParallelService.java:4)
at com.android.camera.LocalParallelService$LocalBinder.<init>(LocalParallelService.java:9)
at com.android.camera.LocalParallelService.onCreate(LocalParallelService.java:5)
at android.app.ActivityThread.handleCreateService(ActivityThread.java:4186)
at android.app.ActivityThread.access$1500(ActivityThread.java:237)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1932)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:223)
at android.app.ActivityThread.main(ActivityThread.java:7664)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
Looks like the apk only works on MIUI... Try ANXCamera, must be installed through Magisk or TWRP.
Aleksanderbjorn said:
Looks like the apk only works on MIUI... Try ANXCamera, must be installed through Magisk or TWRP.
Click to expand...
Click to collapse
Nice suggestion, thanks again.
I've tried the different builds for Android 11 via TWRP and all of them hang during installation, the phone is also not yet listed as officially supported.
If I manage to make it work somehow I will post it in this thread (also if I find any other good alternative).
At the moment only GCAM works, but not fully.
xatok said:
Nice suggestion, thanks again.
I've tried the different builds for Android 11 via TWRP and all of them hang during installation, the phone is also not yet listed as officially supported.
If I manage to make it work somehow I will post it in this thread (also if I find any other good alternative).
At the moment only GCAM works, but not fully.
Click to expand...
Click to collapse
I have also tried with multiple ANXCamera combinations - none work :/ It installs OK but the camera view is black

Categories

Resources