Develop Bugs

[DEV] AOSP Touchscreen dead.

Hi devs,
I was trying to compile the eclair AOSP with hero profile. Everything compiled correctly and it boots up on my hero but why does my touchscreen not work??
Anyone could give me a hand on why the touchscreen is not working on my hero? I am using godmode kernel.
Thanks in advance,

Use this kernel + wlan.ko:
http://github.com/loxK/android_device_htc_hero/blob/froyo/kernel
http://github.com/loxK/android_device_htc_hero/blob/froyo/wlan.ko

maxisma said:
Use this kernel + wlan.ko:
http://github.com/loxK/android_device_htc_hero/blob/froyo/kernel
http://github.com/loxK/android_device_htc_hero/blob/froyo/wlan.ko
Click to expand...
Click to collapse
Thanks Maxima!
But this is for Froyo or also working for eclair?
And another question is it a special kernel config that I need to enable for the touchscreen to work? As I did use a working .config from another 2.1 rom.
Giving those files a go anyhow

Argh! I recompiled the kernel with the config from the kernel you posted. But still touchscreen does not work..
Also the unlock (pincode) screen does not popup so I cant make any calls.
Can anyone please give me some hints on why this is happening?

In the kernel is a AOSP-version of the touchscreen driver and a Sense-version. Don't know why the difference is there, but if you look at your kernel source files you'll see a file in there with 'AOSP-fix' in the filename. Use that version of the .c file (overwrite the original or backup the original first) and compile your kernel. The touchscreen will work now.
Or (like the previous answers) use an already compiled kernel with this fix in it

dipje said:
In the kernel is a AOSP-version of the touchscreen driver and a Sense-version. Don't know why the difference is there, but if you look at your kernel source files you'll see a file in there with 'AOSP-fix' in the filename. Use that version of the .c file (overwrite the original or backup the original first) and compile your kernel. The touchscreen will work now.
Or (like the previous answers) use an already compiled kernel with this fix in it
Click to expand...
Click to collapse
Ah! Thanks. Recompiling
btw and what about the pincode popup issue? Why am I not getting that popup when starting the phone?

Works! Nice! Thanks. And my other Question? Pincode unlock is not poping up. I cant get a signal from my provider

Anyone has a clue?

I have tried to enable keyguard options to false/true 0/1 but still no joy.
Now checking settings it seems my build is not seeing the baseband versions. It says: Unknown.
Maybe this is something anyone has experience with?

Shakor said:
I have tried to enable keyguard options to false/true 0/1 but still no joy.
Now checking settings it seems my build is not seeing the baseband versions. It says: Unknown.
Maybe this is something anyone has experience with?
Click to expand...
Click to collapse
RIL-library..

maxisma said:
RIL-library..
Click to expand...
Click to collapse
Cool. Thanks checking this out.

Still no joy.. Argh

[Q] RIL Development sgh-t999

Hi everyone,
recently I have built and flashed on my sgh-t999 (galaxy S3 US tmobile version) CM11 Nightly. For my pro0ject however I need to modify two libraries of the Radio Interface Layer (RIL), libril.so and libreference-ril.so. I tried to modify the ones in the forlder /hardware/ril/ and build everything again with no results. Any change that I made to those files (such as ril.cpp in the folder libril) would not affect the functionality of the phone.
Finally yesterday I understood that when I build those libraries for the target cm-d2tmo-eng, those files that I have modified are not considered at all! When the libraries are built indeed, the system automatically takes the libril.so and libreference.so present in the vendor folder!
The problem is that those libraries in the vendor folder and already compiled and I cannot modify them. The question is:
Is there any way that I compile those libraries from the source code that I have modified?
Thanks,
brok85

Given that there is a unified D2LTE Build on CM, can you elaborate on what changes you wish to make to these libraries ?
To answer your question, You can do one of two things.
Grab the CM Source Code from the Device Tree of D2LTE. Make your relevant changes and check in the changes if they boot ok on your device. That way those changes will be included in future builds of CM and other Roms that use it.
If you do not wish to do so, then you will have to compile those libraries using C++ Compiler on a *NIX box and replace them in the Vendor folder.

Perseus71 said:
Given that there is a unified D2LTE Build on CM, can you elaborate on what changes you wish to make to these libraries ?
Click to expand...
Click to collapse
Well, as fisrt I just wanted to insert some log to be able to follow the code execution from the logcat or do something similar.
Perseus71 said:
To answer your question, You can do one of two things.
Grab the CM Source Code from the Device Tree of D2LTE. Make your relevant changes and check in the changes if they boot ok on your device. That way those changes will be included in future builds of CM and other Roms that use it.
Click to expand...
Click to collapse
Sorry but I am kind of new on this things. I have already downloaded the source code from the device tree and made my modifications in the files ril.cpp contained in [path-to-android-source]/hardware/ril/libril/ril.cpp. What I did was commenting the whole code within the function RIL_onUnsolicitedResponse() and listenCallback() such that in theory, the phone is not able to display incoming calls for example. However after flashing the re-built android I am still able to receve calls. How can I "check in the changes if they boot ok on my device"?
Perseus71 said:
If you do not wish to do so, then you will have to compile those libraries using C++ Compiler on a *NIX box and replace them in the Vendor folder.
Click to expand...
Click to collapse
I tried to remove the libril.so in the vendor folder and compile again using
# . build/envsetup.sh
# lunch (and select d2tmo)
# mmm [path-to-android-source]/hardware/ril/libril".
The problem is that when I indicate the target after lunch, the compiler looks for the vendor libraries and stop the build. What I am doing wrong?

Sounds like Compiler Dependacy path is set different from the code base. I will look further before commenting.
For when your changes are for the benefit of the community of users, you check in the changed code back to the Device Tree with detailed comments within the code and while checking in.

Perseus71 said:
Given that there is a unified D2LTE Build on CM, can you elaborate on what changes you wish to make to these libraries ?
To answer your question, You can do one of two things.
Grab the CM Source Code from the Device Tree of D2LTE. Make your relevant changes and check in the changes if they boot ok on your device. That way those changes will be included in future builds of CM and other Roms that use it.
If you do not wish to do so, then you will have to compile those libraries using C++ Compiler on a *NIX box and replace them in the Vendor folder.
Click to expand...
Click to collapse
Perseus71 said:
Sounds like Compiler Dependacy path is set different from the code base. I will look further before commenting.
For when your changes are for the benefit of the community of users, you check in the changed code back to the Device Tree with detailed comments within the code and while checking in.
Click to expand...
Click to collapse
Actually this is what I get after deleting
libril.so in vendor/samsung/d2tmo/proprietary/lib/
and after executing mmm /hardware/ril/libril :
No private recovery resources for TARGET_DEVICE d2tmo
make: *** No rule to make target `vendor/samsung/d2tmo/proprietary/lib/libril.so', needed by `/home/brok85/Documents/android/system/out/target/product/d2tmo/system/lib/libril.so'. Stop.
make: Leaving directory `/home/brok85/Documents/android/system'

If u want to build from source, delete the line that copies in vendor-blobs.mk
If u want to copy the blob instead of building it from source, keep the line
It'll be better if u provide us the device and vendor trees links

blackbeard said:
If u want to build from source, delete the line that copies in vendor-blobs.mk
If u want to copy the blob instead of building it from source, keep the line
It'll be better if u provide us the device and vendor trees links
Click to expand...
Click to collapse
I am not sure to understand what should I provide Sorry, as I said I'm kind of new here...
Also, I can not find vendor-blobs.mk...Where it should be?

brok85 said:
I am not sure to understand what should I provide Sorry, as I said I'm kind of new here...
Also, I can not find vendor-blobs.mk...Where it should be?
Click to expand...
Click to collapse
You said you built a cm11 for ur device. So for that you needed the device and the vendor trees. Give the link of those, if they are on the git
And vendor-blobs.mk would be present in the vendor folder under your device folder

blackbeard said:
You said you built a cm11 for ur device. So for that you needed the device and the vendor trees. Give the link of those, if they are on the git
Click to expand...
Click to collapse
Well I have followed the guide in the following page
http://wiki.cyanogenmod.org/w/Build_for_d2tmo
The link from where I have obtained the repository is
$ repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0
and then
$ breakfast d2tmo
blackbeard said:
And vendor-blobs.mk would be present in the vendor folder under your device folder
Click to expand...
Click to collapse
Actually now I think I was able to compile the library following your instructions. Unfortunatly, when I have built and flashed everything in the galaxy S3, I was not able to use the network. Probably some compatibility issue?
When I compiled libril.so, I have obtained it from the folder /hardware/ril/libril which should contain google source code, maybe not compatibale with my device...is it right?
thanks a lot for the help guys

brok85 said:
Actually now I think I was able to compile the library following your instructions. Unfortunatly, when I have built and flashed everything in the galaxy S3, I was not able to use the network. Probably some compatibility issue?
When I compiled libril.so, I have obtained it from the folder /hardware/ril/libril which should contain google source code, maybe not compatibale with my device...is it right?
Click to expand...
Click to collapse
You know, silly question. But just so we can rule out. Did you at any point compiled the CM11 code as is and flashed to the phone ? How did Network behave ? Was everything ok ?
Galaxy S3 is a very open platform with standard hardware and chipsets. So the Default google code should work out of box with it. If you have network issues, then just for kicks you can flash a custom Kernel on top of your compiled CM 11. See how that goes.

Perseus71 said:
You know, silly question. But just so we can rule out. Did you at any point compiled the CM11 code as is and flashed to the phone ? How did Network behave ? Was everything ok ?
Click to expand...
Click to collapse
No silly question at all
I have compiled CM11 as it is and worked perfectly. I could use the network.
Perseus71 said:
Galaxy S3 is a very open platform with standard hardware and chipsets. So the Default google code should work out of box with it. If you have network issues, then just for kicks you can flash a custom Kernel on top of your compiled CM 11. See how that goes.
Click to expand...
Click to collapse
The procedure I have followed is the following one:
1) Delete the llibril.so and libreference-ril.so from the vendor library. These are the pre-compiled vendor libraries that I need to modify.
2) commented the lines from the vendor-blobs.mk that were including those two precompiled libraries.
3) go to android/system/ and run "mmm /hardware/ril/libril" and "mmm /hardware/ril/reference-ril" to obtain the modified libril.so and libreference-ril.so respectively.
4) copied the new libraries just obtained in the vendor folder where the pre-compiled libraries were
5) re-include the lines commented in point 2).
6) run brunch d2tmo
7) flash the .zip obtained
Any mistake?

Perseus71 said:
You know, silly question. But just so we can rule out. Did you at any point compiled the CM11 code as is and flashed to the phone ? How did Network behave ? Was everything ok ?
Click to expand...
Click to collapse
No silly question at all. Yes I have built everything out of the box and worked perfectly. I could use the network.
Perseus71 said:
Galaxy S3 is a very open platform with standard hardware and chipsets. So the Default google code should work out of box with it. If you have network issues, then just for kicks you can flash a custom Kernel on top of your compiled CM 11. See how that goes.
Click to expand...
Click to collapse
I followed the following procedure to include my modified libraries:
1) Eliminate precompiled vendor libraries: libril.so and libreference-ril.so from the vendor folder
2) comment lines in the vendor-blobs.mk that included those two precompiled libraries
3) from /android/system/ executed command "mmm /hardware/ril/librail" and "mmm /hardware/ril/reference-ril" to obtain the modified libril.so and libreference-ril.so
4) copied the new libraries in the vendor folder in the same places were the precompiled libraries were positioned
5) re-include the two lines that were commented in point 2)
6) build everything again with brunch d2tmo
7) flash the .zip obtained
Any mistake?

Unless I am having a brain fart that process seems about right. I wonder if your RIL changes are related to the network
What kind of issues do you see ?

Perseus71 said:
Unless I am having a brain fart that process seems about right. I wonder if your RIL changes are related to the network
What kind of issues do you see ?
Click to expand...
Click to collapse
It cannot even find the network operators. It says that it is impossible to connect and to try later...
mine is the Tmobile version of S3. May this influence?

That would depend on the changes you made. But otherwise not really. The underlying Device tree is unified for all US S3 devices.

[KERNEL][Z1C] UNOFFICIAL CoCore-Z r27 [04/01]

This is an unofficial compiled from Xperia Z1 CoCore-Z Kernel sources. I like to share with you my modified version of CoCore-Z kernel r27. I'd like to credit @cocafe it wouldn't be possible without you. I'm not a developer so I cannot answer your question about any bugs for this kernel immediately.
If the kernel crashed (freezed and rebooted), please fetch last_kmsg file after the crash reboot and post in the thread. I will ask cocafe how to resolve bugs.
Code:
su -c cat /proc/last_kmsg > /sdcard/last_kmsg
2015/04/01
please visit http://forum.xda-developers.com/showpost.php?p=59827552&postcount=8 to see more information:
Changelog:
1.Compiled using Linaro GCC 4.9.3 2015.03 toolchain with Cortex-A15 optimizations
2.Ramdisk adjusted for the Z1C
3.Updated PhilZ Touch recovery v6.59.0 & CWM v6.0.5.0 & TWRP v2.8.5.0
Requirements:
1. Unlocked Bootloader
2. Stock Sony KK firmware .757/.108/.157 or any ROM based on it.
Features:
Visit the CoCore-Z Original thread in the Z1 forum, and make sure you read all the instructions and features.
http://forum.xda-developers.com/xperia-z1/orig-development/kernel-cocore-z-r12-t2892310
Download Links:
https://mega.co.nz/#F!ysRWkCQY!Hb9wssFCCpc9fCEhI4zFQQ
Kernel Source:
https://github.com/cocafe/c6902_kernel_CoCore-Z
Credits:
cocafe (for his kernel sources and letting me build this unofficial release)
[NUT] (for all recoveries & 14.4.A.0.157 kernel ramdisk & NDRUtils)
OmarEinea (for his great script of build tools letting me easy way to compile kernel)
Christopher83 (for Linaro cross compiler toolchains)
And for everyone who had a hand in making this kernel better

sharonliu said:
This is an unofficial compiled from Xperia Z1 CoCore-Z Kernel sources. I like to share with you my modified version of CoCore-Z kernel r25. I'd like to credit @cocafe it wouldn't be possible without you. I'm not a developer so I cannot answer your question about any bugs for this kernel immediately.
If the kernel crashed (freezed and rebooted), please fetch last_kmsg file after the crash reboot and post in the thread. I will ask cocafe how to resolve bugs.
Code:
su -c cat /proc/last_kmsg > /sdcard/last_kmsg
Changelog:
1.Compiled using Linaro GCC 4.9.3 2015.03 toolchain with Cortex-A15 optimizations
2.Ramdisk adjusted for the Z1C
3.Updated PhilZ Touch recovery v6.59.0 & CWM v6.0.5.0 & TWRP v2.8.5.0
Requirements:
1. Unlocked Bootloader
2. Stock Sony KK firmware .757/.108 or any ROM based on it
Features:
Visit the CoCore-Z Original thread in the Z1 forum, and make sure you read all the instructions and features.
http://forum.xda-developers.com/xperia-z1/orig-development/kernel-cocore-z-r12-t2892310
Download Links:
https://mega.co.nz/#F!ysRWkCQY!Hb9wssFCCpc9fCEhI4zFQQ
Kernel Source:
https://github.com/cocafe/c6902_kernel_CoCore-Z
Credits:
cocafe (for his kernel sources and letting me build this unofficial release)
[NUT] (for all recoveries & 14.4.A.0.157 kernel ramdisk & NDRUtils)
OmarEinea (for his great script of build tools letting me easy way to compile kernel)
Christopher83 (for Linaro cross compiler toolchains)
And for everyone who had a hand in making this kernel better
Click to expand...
Click to collapse
cocafe mentioned that the wifi modules has to be original from stock ROM, so i replaced them before flashing the kernel, but wifi does not turn on.

thank you for reporting this problem, it should be resolved next release.

Nice to see another stock based kernel around!
Only .108 or also .157?

Schlengge said:
Nice to see another stock based kernel around!
Only .108 or also .157?
Click to expand...
Click to collapse
from cocafe´s post:
ROM: Stock KitKat 4.4.4 14.4.A.0.108 +
Click to expand...
Click to collapse
so imho for .157 too

sharonliu said:
thank you for reporting this problem, it should be resolved next release.
Click to expand...
Click to collapse
i think this solves the problem: LINK

moonryder said:
i think this solves the problem: LINK
Click to expand...
Click to collapse
Thanks for the information. Just like DooMKernel, my goal is no need to compile wlan module. If I am not luck, I will build the wlan module in this weekend.

Changelog :
wlan is working
Download Links:
https://mega.co.nz/#F!ysRWkCQY!Hb9wssFCCpc9fCEhI4zFQQ
Insturaction:
If you want back to stock kernel, remember reboot to recovery and flash stock wife modules.

sharonliu said:
...flash stock wife modules.
Click to expand...
Click to collapse
funny...
btw will check this kernel
checked your stock wlan zip file, there is something wrong.
the wlan file is wrong named (the right name is pronto_wlan) and would be flashed into /system/lib/modules
but it has to be flashed into /system/lib/modules/pronto
p.s. i replaced all files in the zip with the original from my ROM

moonryder said:
funny...
btw will check this kernel
checked your stock wlan zip file, there is something wrong.
the wlan file is wrong named (the right name is pronto_wlan) and would be flashed into /system/lib/modules
but it has to be flashed into /system/lib/modules/pronto
p.s. i replaced all files in the zip with the original from my ROM
Click to expand...
Click to collapse
In CoCore-Z-r27-wlan-modul, pronto_wlan is not included in the zip file, only customize prima's wlan.ko. So my stock wlan zip file, no need to re-flash pronto_wlan. cocafe will try to port new pronto_wlan in the next time.

sharonliu said:
In CoCore-Z-r27-wlan-modul, pronto_wlan is not included in the zip file, only customize prima's wlan.ko. So my stock wlan zip file, no need to re-flash pronto_wlan. cocafe will try to port new pronto_wlan in the next time.
Click to expand...
Click to collapse
ok
btw flashed new build from today and wifi works like a charm.
thx

Thanks for this kernel
The only thing I noticed is that the notification light turns white when the battery is full
Normal it's green
Don't know if it's I bug but I noticed it

It's not a bug. Cocafe made it so the led will notify you of the real eoc. You can change the led color though here I believe "/sys/kernel/qpnp-charger/eoc_led"

i tried some scripts from cocafes original post HERE.
But none of the scripts work using SManager. Why?
always error: "No such file or directory ...."
but these files / directories are there (checked it with RootExporer) -DAMN
And if the scripts don´t work, there is no profit compared to DoomKernel...

moonryder said:
i tried some scripts from cocafes original post HERE.
But none of the scripts work using SManager. Why?
always error: "No such file or directory ...."
but these files / directories are there (checked it with RootExporer) -DAMN
And if the scripts don´t work, there is no profit compared to DoomKernel...
Click to expand...
Click to collapse
get terminal emulator from the play store and type it in there
or use adb shell
adb shell
su
Click to expand...
Click to collapse
it should work if you type these scripts. In my opinion, DoomKernel is the best custom kernel, bu nice to see another stock based kernel around.

sharonliu said:
...DoomKernel is the best custom kernel....
Click to expand...
Click to collapse
you are so right bro

I found this kernel seems not to support exFAT. May you fix that?
btw, thx for modifying this kernel for Z1C. It's amazing !!

a1b2c3901 said:
I found this kernel seems not to support exFAT. May you fix that?
btw, thx for modifying this kernel for Z1C. It's amazing !!
Click to expand...
Click to collapse
why do you use exFAT format?
Do you have files > 4GB in use?

moonryder said:
why do you use exFAT format?
Do you have files > 4GB in use?
Click to expand...
Click to collapse
Sometimes I will watch movie in the journeys, and that files may be oversize.

a1b2c3901 said:
Sometimes I will watch movie in the journeys, and that files may be oversize.
Click to expand...
Click to collapse
get "MLUSB Mounter" from the play store, you can use the USB hard drive (formatted NTFS, exFAT).

Tips for porting

When you found a bug when porting a ROM, you can try to fix using
this methods!
Just replace it from Stock ROM to your Custom ROMs.
Bootloop when porting:
/system/lib/libandroid_runtime.so
/system/lib/libandroid_servers.so
/system/lib/libmedia_jni.so
*Repack boot.image
Showing black screen after logo:
\system/lib/libMali.so
Sensors :
/system/bin/akmd*
/system/lib/libsensors.so
/system/lib/libms3c_yamaha.so
/system/etc/firmware(folder)
/system/bin/servicemanager
Bluetooth :
/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
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/etc/wifi (folder)
/system/etc/firmware (folder)
Camera :
system/lib/libfeatureio.so-cameranotworking
/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\libcameraprofile.so
\system\lib\libcameraservice.so
\system\lib\libmhal.so
\system\lib\libmhalcontent.so
\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-fixcamcoder
\system\lib\libfeatureo.so-fixcamfocus
#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
SD card/Memory:
/system/bin/vold
\system\etc\vold.fstab->edit file for swap internal and external
\system\etc\vold.fstab.nand
*Note:If not present leave this. from kitkat4.4.x this file has been moved into boot.img
Storage not mounting:
Decompile framework-res.apk using apk tool or apk multitool and
replace following file from STOCK framework-res.apk to PORT
framework-res.apk
/res/xml/storage_list.xml
GPS:
\system\xbin\libmnlp
/system/etc/gps.conf
Touch Screen (Haptic):
/system/usr
/system/usr\keylayout\Generic.kl->fixHomeKey
Sim1/2 (RIL):
\system\etc\firmware\modem.img
\system\etc\permission(RIL)
/system/bin/stmd
/system/bin/rild*
/system/etc/rril
Audio/Sound:
\system\lib\libaudio*.so
Ads:
/system/etc/hosts->replace with new files or use tweak.
Resolution problem:
open build.prop and add following line
ro.sf.lcd_density=240
[ex:240 but your dpi may be different]
Pixalation in video:
Replace following file from STOCK to PORT
system/lib/libvcodecdrv.so
Flipped touch screen:
Replace following files from STOCK to PORT
system/lib/libinput.so
LED not working:
Replace following files from STOCK to PORT
system/lib/libfeatureio.so
Fix Network / 3G Network:
/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
#Most of it works.

Need some guides
[email protected]!C said:
When you found a bug when porting a ROM, you can try to fix using
this methods!
Just replace it from Stock ROM to your Custom ROMs.
Bootloop when porting:
/system/lib/libandroid_runtime.so
/system/lib/libandroid_servers.so
/system/lib/libmedia_jni.so
*Repack boot.image
Showing black screen after logo:
\system/lib/libMali.so
Sensors :
/system/bin/akmd*
/system/lib/libsensors.so
/system/lib/libms3c_yamaha.so
/system/etc/firmware(folder)
/system/bin/servicemanager
Bluetooth :
/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
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/etc/wifi (folder)
/system/etc/firmware (folder)
Camera :
system/lib/libfeatureio.so-cameranotworking
/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\libcameraprofile.so
\system\lib\libcameraservice.so
\system\lib\libmhal.so
\system\lib\libmhalcontent.so
\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-fixcamcoder
\system\lib\libfeatureo.so-fixcamfocus
#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
SD card/Memory:
/system/bin/vold
\system\etc\vold.fstab->edit file for swap internal and external
\system\etc\vold.fstab.nand
*Note:If not present leave this. from kitkat4.4.x this file has been moved into boot.img
Storage not mounting:
Decompile framework-res.apk using apk tool or apk multitool and
replace following file from STOCK framework-res.apk to PORT
framework-res.apk
/res/xml/storage_list.xml
GPS:
\system\xbin\libmnlp
/system/etc/gps.conf
Touch Screen (Haptic):
/system/usr
/system/usr\keylayout\Generic.kl->fixHomeKey
Sim1/2 (RIL):
\system\etc\firmware\modem.img
\system\etc\permission(RIL)
/system/bin/stmd
/system/bin/rild*
/system/etc/rril
Audio/Sound:
\system\lib\libaudio*.so
Ads:
/system/etc/hosts->replace with new files or use tweak.
Resolution problem:
open build.prop and add following line
ro.sf.lcd_density=240
[ex:240 but your dpi may be different]
Pixalation in video:
Replace following file from STOCK to PORT
system/lib/libvcodecdrv.so
Flipped touch screen:
Replace following files from STOCK to PORT
system/lib/libinput.so
LED not working:
Replace following files from STOCK to PORT
system/lib/libfeatureio.so
Fix Network / 3G Network:
/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
#Most of it works.
Click to expand...
Click to collapse
Why don't you post some Rom Porting Guides.. I Know That There Are Lots Of Them Available Here On XDA But I Tried Them (Result : Stuck on bootanimation or bootloops).:silly:. i mean none of them worked.. if you are having experience with porting Please Put up some porting guides also..:good:

Yeah
mohit sethi said:
Why don't you post some Rom Porting Guides.. I Know That There Are Lots Of Them Available Here On XDA But I Tried Them (Result : Stuck on bootanimation or bootloops).:silly:. i mean none of them worked.. if you are having experience with porting Please Put up some porting guides also..:good:
Click to expand...
Click to collapse
First things first. Don't quote whole OP.
And the guide I use is this one http://forum.xda-developers.com/showthread.php?t=1908008

[email protected]!C said:
First things first. Don't quote whole OP.
And the guide I use is this one http://forum.xda-developers.com/showthread.php?t=1908008
Click to expand...
Click to collapse
oops sorry for that !
and thanx for guide

Error Loading

matrixex said:
Buddy let's try with some ROMs and this info is very useful I think I will try this with Stock ROM vs liquid smooth lollipop
And here is guide for porting ROM from another device by Rishab Raj
http://forum.xda-developers.com/showthread.php?t=1908008
Oops Someone is already posted this link no prob.
Click to expand...
Click to collapse
Liquid smooth is lollipop based rom......for porting CM13 rom to our jellybean we will need source codes + CM13 device tree and further compiling in ubuntu will give us CM 13 Rom....This method is insane :silly:
Try porting 4.4.x based or 4.1.2 based roms using this guide :good:

mohit sethi said:
Liquid smooth is lollipop based rom......for porting CM13 rom to our jellybean we will need source codes + CM13 device tree and further compiling in ubuntu will give us CM 13 Rom....This method is insane :silly:
Try porting 4.4.x based or 4.1.2 based roms using this guide :good:
Click to expand...
Click to collapse
END

matrixex said:
We already have liquid smooth lollipop by Ahmad hardy just try it.
Click to expand...
Click to collapse
it is the most buggy rom for X/XL

[email protected]!C said:
First things first. Don't quote whole OP.
And the guide I use is this one http://forum.xda-developers.com/showthread.php?t=1908008
Click to expand...
Click to collapse
First thanks for Tips, Let me add this, it'll be very helpful in porting
Nokia X Vendor Files https://github.com/NormandyLP/android_vendor_nokia_normandy
Nokia XL Vendor Files https://github.com/Nokia-xl-legacy/vendor_xl

Is their any way to test the ported rom other than flashing on device
Sent from my Nokia_XL using XDA Free mobile app

There is hissing noise that comes out of the speaker after playing media.
I replaced all audio libs, libcustom_nvram.so
How can i fix it?

zenowaren said:
There is hissing noise that comes out of the speaker after playing media.
I replaced all audio libs, libcustom_nvram.so
How can i fix it?
Click to expand...
Click to collapse
Well, i unpacked stock system.img and flashed via cwm without modifying any files, there is the same problem again. It is not related to port

How Can I Modify Nougat ROMs For The OnePlus 3T?

Hello.
Few days ago I tried to modify LineageOS 14.1 for my OnePlus 3T.
I managed to create a flashable zip that changes the UI to Blue.
Then I thought of implementing it into the ROM itself.
I tried many tools for system.new.dat & system.new.transferlist.
I was able to decompile the files, but I couldn't recompile it
Any help would be appreciated!

ViperXvenom8888 said:
Hello.
Few days ago I tried to modify LineageOS 14.1 for my OnePlus 3T.
I managed to create a flashable zip that changes the UI to Blue.
Then I thought of implementing it into the ROM itself.
I tried many tools for system.new.dat & system.new.transferlist.
I was able to decompile the files, but I couldn't recompile it
Any help would be appreciated!
Click to expand...
Click to collapse
Just build it from source then you wont have this issue.

zelendel said:
Just build it from source then you wont have this issue.
Click to expand...
Click to collapse
The thing is building it from the source takes a long time (Have to download about 20GB of data or so) I already have the ROM (.zip). I just want to modify the System UI color to Blue

ViperXvenom8888 said:
The thing is building it from the source takes a long time (Have to download about 20GB of data or so) I already have the ROM (.zip). I just want to modify the System UI color to Blue
Click to expand...
Click to collapse
Well then you will have o wait for apktool to fully support android O then. Yes it is alot but then again doing things the right way was never meant to be easy.

zelendel said:
Well then you will have o wait for apktool to fully support android O then. Yes it is alot but then again doing things the right way was never meant to be easy.
Click to expand...
Click to collapse
Android O? Why?? I want to modify LineageOS 14.1 (Android 7.1.2)

ViperXvenom8888 said:
Android O? Why?? I want to modify LineageOS 14.1 (Android 7.1.2)
Click to expand...
Click to collapse
I made that assumption due to your last post being in a CM thread that was an 8.0 thread.
Best bet is to pull a logcat while it bootloops and that will tell you the issue. I have not done modding in this way in many years since I learned the proper way to mod them.

zelendel said:
I made that assumption due to your last post being in a CM thread that was an 8.0 thread.
Best bet is to pull a logcat while it bootloops and that will tell you the issue. I have not done modding in this way in many years since I learned the proper way to mod them.
Click to expand...
Click to collapse
I don't know how to pull logcats.
I modified it few days ago using some Windows 10 Tool I found on XDA that converts patch & transferlist to the old file system (app, priv-app, etc...) And used another tool to convert file_context.bin to file_context (file type). Tried to recompile and it bootloops... I just want to know how other developers apply changes to their ROM.
Thanks

ViperXvenom8888 said:
I don't know how to pull logcats.
I modified it few days ago using some Windows 10 Tool I found on XDA that converts patch & transferlist to the old file system (app, priv-app, etc...) And used another tool to convert file_context.bin to file_context (file type). Tried to recompile and it bootloops... I just want to know how other developers apply changes to their ROM.
Thanks
Click to expand...
Click to collapse
They build from source and make their changes.
You should learn how to do a logcat. It is trouble shooting 101 which will happen.
I will give you a hint. You are way off of where you want to be. The color is in the framework res. You either pull the apks from the device or have to build it from source.

zelendel said:
They build from source and make their changes.
You should learn how to do a logcat. It is trouble shooting 101 which will happen.
I will give you a hint. You are way off of where you want to be. The color is in the framework res. You either pull the apks from the device or have to build it from source.
Click to expand...
Click to collapse
I already pulled the framework-res and modified it properly. As I said before, I made a flashable .zip and it worked but the problem is how do I implement the changes into the ROM itself?

ViperXvenom8888 said:
I already pulled the framework-res and modified it properly. As I said before, I made a flashable .zip and it worked but the problem is how do I implement the changes into the ROM itself?
Click to expand...
Click to collapse
You would have to build it. Trying to do it your way will not work as roms are encrypting the files so they can't be pulled and edited that way. It was done to prevent people from making minor color changes and then calling it theirs.
Just build from scratch. It is easier and less hacky. Mainly with roms using private keys to sign their roms.

zelendel said:
You would have to build it. Trying to do it your way will not work as roms are encrypting the files so they can't be pulled and edited that way. It was done to prevent people from making minor color changes and then calling it theirs.
Just build from scratch. It is easier and less hacky. Mainly with roms using private keys to sign their roms.
Click to expand...
Click to collapse
Thanks for this info!
From the information I've gathered, I've found out that I need the Device Tree, Vendor Tree & Kernel of the OnePlus 3T from GitHub. Any idea on where to find those?
Thanks!

ViperXvenom8888 said:
Thanks for this info!
From the information I've gathered, I've found out that I need the Device Tree, Vendor Tree & Kernel of the OnePlus 3T from GitHub. Any idea on where to find those?
Thanks!
Click to expand...
Click to collapse
The easiest thing to do is use an already set up project like DU or (shudders) Los. Then all you have to do is sync the source. Los has a page set up to show you how to build as does DU. I would use du but that is just me.

zelendel said:
The easiest thing to do is use an already set up project like DU or (shudders) Los. Then all you have to do is sync the source. Los has a page set up to show you how to build as does DU. I would use du but that is just me.
Click to expand...
Click to collapse
Alright. Thanks a lot for all the information you have provided me!