account arrowhead-down arrowhead-up mobile-menu search sm-bold-x x-skinny-rounded x-skinny arrowhead-right social-facebook social-googleplus social-instagram social-linkedin social-pinterest social-qzone social-renren social-tencent social-twitter social-vkontakt social-weibo social-youku social-youtube

Please help us improve our website

Take our customer survey to evaluate your visit.

It should only take a few minutes to answer five quick questions. Just click the Launch survey button at the end of your visit to begin.

cancel
Showing results for 
Search instead for 
Did you mean: 
Welcome to the Open Devices community!

This is where we discuss open source and development related questions on our Open Devices initiative.

Porting kernel to custom ROM

Talent
Message 11 of 29
2,800 Views
Message 11 of 29

Re: Porting kernel to custom ROM

I just tested flashing Omnirom package and unfortunately I get the same result as with DU package.

Big Sony logo appears (without xperia) and after that either bootloop or just a flashing blackscreen.

 

How do I proceed to debug boot up issue?

Also, what changes does the kernel need for it to be able to boot with a custom rom?

 

 

Developer World
Message 12 of 29
2,791 Views
Message 12 of 29

Re: Porting kernel to custom ROM

hi

 

since Sony kernel and binaryes provide AOSP compatibility you have to compile your custom rom with AOPS HALs instead of CAF ones

to debug you have to enable adb (build userdebug variant) and then you have access to command line

in comandline you can access logcat and dmesg each one providing good logs and information why your device bootloops

 

br

Alin

 

Talent
Message 13 of 29
2,786 Views
Message 13 of 29

Re: Porting kernel to custom ROM

Thank you

 

I guess that will work for DU, which has a separate branch for AOSP and CAF.

But, for omnirom there is only one branch (android-5.1)

How do I make sure I am using AOSP HALs and not CAF, since I am using AOSP trees there should not be referencing any CAFs?

 

I am building userdebug but adb logcat always hangs on 'waiting on device',

will try dmesg hopefully it works.

 

Thank you for your advice

Developer World
Message 14 of 29
2,778 Views
Message 14 of 29

Re: Porting kernel to custom ROM

hi

 

there should be some ifdefs

check your custom rom base

br

Alin

Message 15 of 29
2,767 Views
Message 15 of 29

Re: Porting kernel to custom ROM

Rancid, I will give a look to at it too. If you can tell me where the sources are I will help you.

 

Post the link of the sources(even if they are purely stock Sony sources) here so I can give a look. I am very interested into getting Xperia Z3 working properly with OmniRom, so if we are able you to get the build up and working(booting) it´ll we a giant step.

 

Keep on work!

Talent
Message 16 of 29
2,760 Views
Message 16 of 29

Re: Porting kernel to custom ROM

I compiled omnirom again deleting the hardware/qcom audio-caf media-caf and display-caf folders., (not exactly sure what the ifdefs refer to)

I have not tried it yet, will be trying it later and reporting.

 

Using Myself5 shinano and sirius repos as an example I have been able to compile omni-homemade packages:

 

I am also in the process of finishing downloading DU lollipop sources (not caf) and will try initial bring up to see if AOSP boots.

 

Using CM12 device and kernel trees I have been able to bring up DU lollipop-caf but it only boots with cm12 boot.img (compiled separately with cm12 sources) - for some reason it does not boot with compiled DU boot.img.

 

 

Adviser
Message 17 of 29
2,747 Views
Message 17 of 29

Re: Porting kernel to custom ROM

@hernan10alvarez, I already have a working Z3 Device tree for Omni Face with stuck-out Tongue Just check my git (still need to update with the newest changes made to the sirius tree)
@rancid, glad to hear it worked for you, let me know when you need any further help.

Regards
Talent
Message 18 of 29
2,729 Views
Message 18 of 29

Re: Porting kernel to custom ROM

 #Myself5

Working as in compiling.

But when it boots after the Sony logo appears it stops booting and there is a flashing black screen.

 

What changes are needed for Omnirom to not include cafs (jerpelea mentioned ifdefs).

I removed the qcom caf projects, but it seems that that is not enough.

What other changes are needed?

 

Than you for your help

Also,

I tried dmesg, (adb logcat did not work):

[382978.660355] usb 3-2: new high-speed USB device number 114 using xhci_hcd
[382978.678156] usb 3-2: New USB device found, idVendor=0fce, idProduct=51bb
[382978.678165] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[382978.678170] usb 3-2: Product: Xperia Z3C
[382978.678174] usb 3-2: Manufacturer: Sony
[382978.678178] usb 3-2: SerialNumber: xxxxxxxxxx
[384650.408623] usb 3-2: USB disconnect, device number 114
[384845.566870] usb 3-2: new high-speed USB device number 115 using xhci_hcd
[384845.589986] usb 3-2: New USB device found, idVendor=18d1, idProduct=4ee2
[384845.589994] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[384845.590000] usb 3-2: Product: Xperia Z3C
[384845.590004] usb 3-2: Manufacturer: Sony
[384845.590008] usb 3-2: SerialNumber:xxxxxxxxxx
[384905.744870] usb 3-2: reset high-speed USB device number 115 using xhci_hcd
[384905.767093] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88014f74d4c0
[384905.767102] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88014f74d480
[384905.767108] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800c8ae0a80
[384905.767112] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88014f74d500
[384905.767116] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800c8ae0ac0
[384912.724993] usb 3-2: USB disconnect, device number 115
[384996.898366] usb 3-2: new high-speed USB device number 116 using xhci_hcd
[384996.922291] usb 3-2: New USB device found, idVendor=0fce, idProduct=0dde
[384996.922300] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[384996.922305] usb 3-2: Product: S1Boot Fastboot
[384996.922309] usb 3-2: Manufacturer: Sony Mobile Communications AB
[384996.922313] usb 3-2: SerialNumber: xxxxxxxxxx
[385045.509274] usb 3-2: USB disconnect, device number 116
[385062.977288] usb 3-2: new high-speed USB device number 117 using xhci_hcd
[385063.000352] usb 3-2: New USB device found, idVendor=18d1, idProduct=4ee2
[385063.000361] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[385063.000367] usb 3-2: Product: Xperia Z3C
[385063.000371] usb 3-2: Manufacturer: Sony
[385063.000375] usb 3-2: SerialNumber: xxxxxxxxxx
[385123.131316] usb 3-2: reset high-speed USB device number 117 using xhci_hcd
[385123.153603] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8803e18b0d00
[385123.153612] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8803e18b0cc0
[385123.153617] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800c8ae0e00
[385123.153622] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8803e18b0d40
[385123.153626] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800c8ae0e40

[387673.851531] usb 3-2: new high-speed USB device number 119 using xhci_hcd
[387678.845681] xhci_hcd 0000:00:14.0: Timeout while waiting for address device command

Not sure what to make of it, though.

Talent
Message 19 of 29
2,707 Views
Message 19 of 29

Re: Porting kernel to custom ROM

I got DU to compile, too.

 

But I have the same issue.

When I flash zip package, after the sony logo I get a flashing blackscreen.

DU has a separate branch for caf and lollipop, so am not sure why this is the case.

 

When I used fastboot to flash boot, system, userdata

it got stuck in Sony logo and logcat connected to device - http://pastebin.com/4NZtPdVR

Any ideas what is going on?

Highlighted
Developer World
Message 20 of 29
2,704 Views
Message 20 of 29

Re: Porting kernel to custom ROM

I/DEBUG   (  272): pid: 709, tid: 709, name: surfaceflinger  >>> /system/bin/surfaceflinger <<<
I/DEBUG   (  272): signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
I/DEBUG   (  272): Abort message: 'couldn't find an OpenGL ES implementation'