• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

port cm roms to p875

skfl

Member
Hi guys, we got true working recovery now. I try to port some roms as expiriments of learning custom roms building when I am free. To start with, I found that we can port from devices that share similar specs. Examples are: Sony Xperia V (Tsubasa), Moto Droid Razr M (xt905,xt925), Lg Optimus Vu2 and Optimus F7 (fx1s) and more.
 
Here are what I came up with. CM10 is quite light and similar to aosp
 

Attachments

  • Screenshot_2020-01-18-10-48-12.png
    Screenshot_2020-01-18-10-48-12.png
    352.2 KB · Views: 235
  • Screenshot_2020-01-18-10-52-15 phone status.png
    Screenshot_2020-01-18-10-52-15 phone status.png
    281.5 KB · Views: 251
  • Screenshot_2020-01-17-23-35-04.png
    Screenshot_2020-01-17-23-35-04.png
    250.1 KB · Views: 222
  • Screenshot_2020-01-18-10-08-52 3g data.png
    Screenshot_2020-01-18-10-08-52 3g data.png
    289.1 KB · Views: 242
No, I havn't yet tried lineage os. Afa I know Xperia V and Razr M got lineage and other os like rr. It would be difficult to port as lineage os is android 7.x. We need to build a new kernel from scratch
 
Here are what I came up with. CM10 is quite light and similar to aosp
The phone seems to run faster on cm10 than stock rom lol. I found that it is not fully working. Camera, wifi & nfc do not work though
 
Last edited:
The phone seems to run faster on cm10 than stock rom lol. I found that it is not fully working. Camera, wifi, nfc & proximity sensor do not work though

I had an Galaxy S3 and a Note 3 on CM and both ran much faster than stock. Bluetooth issues are common occurrences with cm and LineageOs, although some less than others.
 
No, I havn't yet tried lineage os. Afa I know Xperia V and Razr M got lineage and other os like rr. It would be difficult to port as lineage os is android 7.x. We need to build a new kernel from scratch

Yes, I also agree
 
Actually I tried to use camera libs (libchromatix, camera.msm8960 at /lib/hw) from my base stock rom in cm10 in order to get camera working. The camera app dialong box "cannot connect to camera" disappers, however the camera screen is in dark blank.
 
Last edited:
  • Extract the ROM you need to port and you will have these main things:
    META-INF
    System
    boot.img.
  • If you have them then you are ready for the next step.
  • Open /system folder of stock and rom to port.

Good to know but I think CM roms
Actually I tried to use camera libs (libchromatix, camera.msm8960 at /lib/hw) from my base stock rom at cm10 in order to get camera working, however it didn't help

I had a similar issue with flashing a N7 camra mod to my N4. I was experimenting with what I thought might be compatible with my device. The first few times I flashed the mod the stock camera would FC. I couldn't get it to work. At one point, I needed to take a picture and just downloaded a user app. I have no idea why the user app worked but yet my system camera didn't. Makes no sense but there it was.
On another occasion , I accidentally deleted syatem camera app. Downloading a usrr cera app , FC's.
 
I think the system apps mod usually fc caz they are designed to be used in a particular os (like each oems hv a camera app and so on)
 
Hi, I checked the build.prop of cm10 and it said the wifi chip vendor is broadcom. But that in my stock jb is qcom, the model is wcnss. It is normal to hv different wlan chip in the same soc?
 
And uptil now wifi, nfc & cam not working after changing /system/lib. Also, the sys time will reset to 1970 jan even I enabled time service in build.prop (persist.timed.enable=true)
 
And uptil now wifi, nfc & cam not working after changing /system/lib. Also, the sys time will reset to 1970 jan even I enabled time service in build.prop (persist.timed.enable=true)

Did youvsetbthe proper permissions (lib)?
 

Attachments

  • Screenshot_2020-01-29-02-30-10.png
    Screenshot_2020-01-29-02-30-10.png
    563.8 KB · Views: 175
  • Screenshot_2020-01-29-02-30-10.png
    Screenshot_2020-01-29-02-30-10.png
    563.8 KB · Views: 189
Just a thought but changing you buildprop. to mimic the device that cm was intended for might be worth a try. I wouldn't get my hopes up but you never know.
 
Yes, I used the updater script from the port rom. I hv tried to change wifi section of my cm build.prop but with no luck
 
Hi, after all, I noticed the wifi unusable problem is due to wpa-supplicant has not initialized shown in the testing menu. (dial *#*#4636#*#* in phone) Any ideas?
 
Last edited:
The phone seems to run faster on cm10 than stock rom lol. I found that it is not fully working. Camera, wifi, nfc & proximity sensor do not work though

Yes, Im having similar issues running a Marshmallow bootloader and modem with a lollipop custom rom. No wifi, no hot spot and the camera is extremely blurred.
I
Btw, are your samsung phones use snapdragon soc?

Yes at least mine does, however I'm not sure if that applies to all Samsung snapdragons, especially when it comes to new models.
 
Btw, are your samsung phones use snapdragon soc?

Some older U.S. Samsungs model have an Exynos chipset, for instance. The Note 5 and the S6. The newer models are all snapdragon and come with locked Bootliloaders. There exception but I am not aware of.
 
I had the same issues with Wifi on LP with a MM bootloader and modem. I found some information on this with mixed results. None of which were specific to my device.
I also had an idea of returning to a stock rooted rom and coping all the wifi related folders and porting them but a few were in my EFS partition and fear the possibility of a DM-verity and/or DRK error.
 
I'll post a link for a possible Wifi fix on AOSP roms if I can find it. I'm pretty sure I PM it to a fellow member of XDA. The result were mixed but maybe this is what your looking for.
 
Back
Top Bottom