Progress.. :)

[powerpaul17]

Hello! Sorry for starting this as an issue but I can't find a way to write messages to users on Github (maybe it doesn't exist..)

I found your repository for the P8 Lite yesterday and since I am also trying to compile a AOKP ROM for this device I wanted to ask if your device configuration is working. I also saw that you already included the Mali libraries, is this working too. So far I couldn't get my phone to boot correctly..

Thanks and maybe we can combine our efforts..?

Greetings, Paul

[XePeleato]

Hi there, the build works, but the device won't boot to android due to some GPU issues that I am trying to fix. As far as I can tell, the device configuration is fine, the current issue is with the Mali GPU, but the libs get loaded by the device.

Feel free to contribute, some help would be awesome!

[concept0]

Hello! I am very glad that you are working on CM for alel21. Can the USB Host / OTG support for him? Unfortunately I'm still a noob and cant do it myself. Sincerely, Alexander.

[powerpaul17]

Hey, thanks for the reply. I also have the same problem with the GPU, it seems to boot but the graphics do not get initialized.

Did you use a stock kernel? Maybe it has something to do with this, I am currently trying to compile the kernel too. I also wrote to someone on xda-developers who seems to have accomplished to compile the kernel.

[XePeleato]

Well, first I am trying to get working pure Android, whenever that's done, I'll start with Cm.

[XePeleato]

@powerpaul17 The kernel gets compiled from source, I am pushing that commit right now.

[XePeleato]

@powerpaul17 I'd love to see your logcat output, mine is this

http://pastebin.com/iRMw1SBS

Is surfaceflinger also crashing on your end?

[powerpaul17]

sorry, I haven't saved the logcat, but it looks pretty much the same.. it also crashed at the same point with the same stacktrace. I also tried to use the surfaceflinger binary from the stock rom but then it doesn't even get started.

I start to believe it might have something to do with the kernel. Maybe the stock kernel is not compatible with AOSP, I am trying to compile the kernel from the sources but I still got some issues.

[XePeleato]

I think I've reached a major milestone :P

[powerpaul17]

Nice.. :) So is it booting? Did you manage to compile the kernel? I am still trying..

[XePeleato]

@powerpaul17 It's almost booting. What's that kernel issue? Are you using Linaro toolchain?

[powerpaul17]

I am using the toolchain which gets compiled or prepared from the "repo" system (just started with Android development.. ;) ). The kernel finished compiling now using the sources from Huawei but I haven't tested yet. What are your boot issues?

[XePeleato]

@powerpaul17 zygote is crashing, at least surfaceflinger loads properly, it looks like I'll need to change some libs.

[olrak2]

Any progress ?

thx in advance.

[XePeleato]

@olrak2 Well, I have compiled the kernel succesfully, and now the "rom" itself is my obejctive, if there's any major progress I'll post it here or wherever I find it convenient.

Have a nice day!

[XePeleato]

Just a quick update for those of you who are waiting, I have spent all of the weekend working on this, I have compiled more than 40 images so far just in the weekend, I have solved some issues but the rom is not finished yet. Now I am not stuck with the graphics system anymore, but there are more issues to fix, I won't surrender.

[olrak2]

Good luck with the problems :) I'm very glad you won't surrender. We need a rom for our Little P8

[XePeleato]

Alright, got it, the rom boots to android, I am not too excited about it since some services crash and the rom is not functional, since you are spammed with "service XXX stopped working" warnings, but at least, it boots :) I'll upload some pics later

[olrak2]

I'm very excited to hear that. Those warning's can't be worse than EMUI :) Let those pics come :)

[XePeleato]

There are lots of bugs (as expected), but there's the proof!

[ghost]

wow, congrats, so it was libs issue?

[XePeleato]

Kind of @hak86 I also disabled selinux and modified the ramdisk, I'll submit a pull request in the afternoon to your tree, since I have spotted something weird.

[ghost]

@XePeleato i think you need to remove everything used by emui, second we should make a ril.java file to let it works, we can try with honor 6 one, it's use kirin920 if not wrong but i'm not sure ;)

[XePeleato]

@hak86 True, since the phone doesn't even ask me to unlock the SIM card. I didn't had much luck following the Honor 6 config. I removed every Huawei file inside 'framework', so there's no trace of Huawei code (just the libs used to get the camera/wifi/bluetooth/display..) working.

[ghost]

one question, does get in the out like root/res? needed for the charger? @XePeleato because my own boot won't boot without them....pretty weird...

[XePeleato]

@hak86 Yes, I copied them from the original ramdisk, it's not updated here because I am building everything again from scratch.

[XePeleato]

UPDATE: I am switching from AOSP to CM, because AOSP doesn't let me configure some things that CM does, and at the moment, I don't have the time to figure out how to do them on my own, so the Build machine is now compiling, allow some hours for a new update.

Have a nice weekend!

[XePeleato]

Well, it looks like it wasn't as easy as just switching sources, now it doesn't even boot.

[ghost]

i fix copying blobs into build and now should copy them with any rom, for the boot.img i still don't understand why in the out/target/product/hi6210sft/root, give me only sbin and res, should be folder like data, dev, system and many other..bah.. @XePeleato

[XePeleato]

Well, you can copy them by hand in order to check if it works @hak86 Mine copied that files just fine.

[olrak2]

@XePeleato Can you update your source? I also want to test aosp and try to boot up my P8 lite. One thing i find weird. How does it come your build number is the same as the original stock build number? It should be a total different number than the stock one, no?

[XePeleato]

@olrak2 It doesn't work that way, the build number is written into a file, I uses the file that came with the device, so it isn't so surprising

[olrak2]

Good to know :) I don't know anything about building. Still learning. Is your tree up to date so i can test on it?

[XePeleato]

@olrak2 Kind of, however you can download it and test it, but let me remind you that it isn't even finished, and you'll need to use my kernel in order to get it working, also, folders "vendor" and "etc" are not copied, since I am doing it by hand because I am testing those files at the moment, However you can still copy them yourself

[XePeleato]

I'm getting closer :)

[ghost]

nice, i just finish a build too, let's see :+1:

[XePeleato]

Update.

I have been talking to codeworkx and it looks like the whole RIL stack isn't compatible with the AOSP framework. As I see it, We have three options.

1. We can decompile Huawei's framework
2. We can develop a hack
3. We can beg Huawei

Any Java developer is up to a challenge?

[ghost]

did you try to call the command like adb shell > rild to see if drivers are missed?

[XePeleato]

Yes, however it worked. 'adb logcat - b radio' was more explicit

[muhammadfahadbaig]

@XePeleato Remove the third option. 3. We can beg Huawei I have done that already and too much...

[muhammadfahadbaig]

@XePeleato which sources you used to compile RIL

[XePeleato]

The RIL daemon is the original one, and the libs are also from Huawei. If you mean the Java class, it's just used to fix signal strength and some other minor bugs.

[muhammadfahadbaig]

@XePeleato Talking about codeworks, he did compiled CM 11 for Honor 6. Any tip from him? I am seriously not good in Java (even I am below moderate in C/C#). You mentioned, decompiling Huawei Framework. Any idea from where to start? I know someone who may take a look.

[olrak2]

@XePeleato Why not try omnirom or cyanogenmod again?

Probably also a good idea is to update your source tree so everybody can build from your source.

I gave tried to build but could not boot to android.

There were a couple of weird things in your tree that i needed to fix before i could build:

• BoardConfig.mk line 90 needted to remove: TW_THEME := hdpi_portrait
• BoardConfig.mk TARGET_KERNEL_PREBUILT does not exist it's : TARGET_PREBUILT_KERNEL
• You import in aosp_hi6210sft.mk as well in device.mk your ramdisk (only needed once)

Could you please also upload your vendor files so we can use them. I have seen a dir /vendor/huawei/p8litekirin/ and a dir /vendor. Where did you place the vendor files?

Here was my catlog file from my bootup: http://pastebin.com/raw/F1744gqG

Many thanks for the work that you already done. :smiley:

[XePeleato]

The tree is updated, I'll upload the vendor files in the evening. Thanks!

[olrak2]

No, thank you @XePeleato

[sgspluss]

@XePeleato would it be helpfull to take a look into huawei p6? They fix ril problems, maybe this will helps you to fix it to. Just search "huawei p6 ril fix" in google.

[XePeleato]

@sgspluss Since it doesn't support Lollipop, I don't think it'll work.

However thank you for your suggestion!

[sgspluss]

I know it didnt has lollipop but maybe it will be helpful anyway @XePeleato, hope you can fix it finger-cross

[sgspluss]

@XePeleato, just search a bit around and found following things, all for CM12.1...

https://github.com/ShevT/vendor_huawei_U9500/commit/0de7be416167dab5ac53677cfdbff1044347e4be

https://github.com/ShevT/device_huawei_U9500/commit/625ed001a380605584de526c3cd006cdc90c737d#

http://forum.xda-developers.com/showpost.php?p=62770987&postcount=7

The last link sounds that the ril fix for CM11 should work bur just for single sim, dual sim have problems. Well however hope that links can help to find the problem for our device...

[muhammadfahadbaig]

@sgspluss It still will be difficult. Apart from the RIL blobs, the QMI blobs won't work for our device. QMI is a protocol developed by Qualcomn and is only available on Qualcomn Chipsets. Our best bet would be to,

1. Patch the Modem Images to make them compatible.
2. Switch to CM base.
3. Or maybe give that QMI fix a try :) Atleast nothing bad would happen.