Progress.. :) #1
Comments
|
Hi there, the build works, but the device won't boot to android due to some GPU issues that I am trying to fix. Feel free to contribute, some help would be awesome! |
|
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. |
|
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. |
|
Well, first I am trying to get working pure Android, whenever that's done, I'll start with Cm. |
|
@powerpaul17 The kernel gets compiled from source, I am pushing that commit right now. |
|
@powerpaul17 I'd love to see your logcat output, mine is this Is surfaceflinger also crashing on your end? |
|
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. |
|
I think I've reached a major milestone :P |
|
Nice.. :) So is it booting? Did you manage to compile the kernel? I am still trying.. |
|
@powerpaul17 It's almost booting. What's that kernel issue? Are you using Linaro toolchain? |
|
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? |
|
@powerpaul17 zygote is crashing, at least surfaceflinger loads properly, it looks like I'll need to change some libs. |
|
Any progress ? thx in advance. |
|
@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! |
|
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. |
|
Good luck with the problems :) I'm very glad you won't surrender. We need a rom for our Little P8 |
|
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 |
|
I'm very excited to hear that. Those warning's can't be worse than EMUI :) Let those pics come :) |
|
There are lots of bugs (as expected), but there's the proof! |
|
wow, congrats, so it was libs issue? |
|
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. |
|
@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 ;) |
|
@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. |
|
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... |
|
@Hak86 Yes, I copied them from the original ramdisk, it's not updated here because I am building everything again from scratch. |
|
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! |
|
Well, it looks like it wasn't as easy as just switching sources, now it doesn't even boot. |
|
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 |
|
Well, you can copy them by hand in order to check if it works @Hak86 Mine copied that files just fine. |
|
@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? |
|
@VenityZ It's stock Huawei Framework Android 5.1.1. EMUI 3.1 |
|
@muhammadfahadbaig I don't know if it changes something. But you were using B008 I guess theres a newer 5.1.1. I think the frameworks are different need update pakage? |
|
@VenityZ Actually, we don't need any EMUI framework patches. We only need how hwframework invokes and manages RIL. You may compare all RIL classes in my uploaded version to any other Android 5.1.1 EMUI version. I think it would be the same. |
|
@muhammadfahadbaig Nice job! Let me play around with it, and let's see if I can understand it. |
|
i manage to got worked boot.img with adb too compiled under cm-12.1, and also i have an idea want to apply after see first boot to get worked ril without patches, keep in touch 👍 |
|
@Hak86 @XePeleato All fighting for one common cause.... to free everyone from the horribly designed (although with many great features and addons) EMUI. |
|
@muhammadfahadbaig sure bro, our device will be faster with a stable rom i think :) |
|
@olrak2 So were you able to get it to boot? |
|
@XePeleato About the RIL issue, I was able to find RIL libraries for HiKey boards. And HiKey Board is compatible with AOSP. Any chance they might work? |
|
@muhammadfahadbaig No idea, where did you find them? I could try. |
|
@XePeleato Here is the link for complete AOSP ROM for HiKey: https://builds.96boards.org/snapshots/hikey/linaro/aosp/218/ . Download system.img.tar.xz. Also for a list of libs and other files included in this distribution, see installed-files.txt |
|
@XePeleato I built from your sources. Unfortunately, my device is stuck on Huawei logo. It doesn't even goes to bootscreen. Any idea why? (using the boot.img compiled from sources) |
|
@olrak2 @XePeleato I confirm the bug faced by @olrak2 . Stuck at Net.d starting.... |
|
@muhammadfahadbaig, after looking in the system.img from @XePeleato , you need to copy the entire bin, etc, lib, lib64 dir's to the out directory of your build. You need to put it all in the system folder. After copying the dir's you can build your rom. Tomorrow i post a scrypt that you can put in your Android.mk file. |
|
@olrak2 Yeah, I figured that out. The reason of Net.d is crashing was either because of init.rc in ramdisk or because of the Android Runtime crashing. The latter is caused because of incompatible libraries being used in the ROM which are not compatible with AOSP. |
|
It's not a good idea to copy the whole folders, I'll upload it this afternoon |
|
@XePeleato Right about that! I'm using Android 5.1.1 r37 and I would not like to face some major crashes. Also, it's good you uploaded the 5.1.1 system.img on XDA. I'll extract the libs from that and then I'll create a repository here on github. |
|
@XePeleato @olrak2 Here are the vendor files :) https://github.com/muhammadfahadbaig/vendor_device_hi6210sft |
|
Development is officially resumed! |
|
@XePeleato Good news If you need something, just call. My working tree for omnirom 5.1 is on my github. (https://github.com/olrak2/android_device_huawei_alice) |
|
How's everything going? And what about the RIL? |
|
There's still work to be done, the RIL stack won't work until I patch the framework. |
|
and also does required patches to boot the rom? my own aosp still stuck due netd is failing to work.. |
|
@Hak86 Are We talking about Lollipop or Marshmallow? |
|
at the moment lollipop, mm downloads, in progress. |
|
@Hak86 Not really, I didn't even touched the framework at Lollipop |
|
so with a correct blobs will boot and this drivers like gatekeeper.hi6210sft.so was use on emui 4.0, right? i am trying your tree right now, once booted will try my modified ril .java and see if will work. |
|
@Hak86 My tree can be useful as a start point but You'll have to tweak it a little bit |
|
@XePeleato yep i see, there was some libs are missed, i am sure it's not a problem with ramdisk, my own ramdisk is complete and worked with omni, in just 4 files. will report if got moved (still building). |
|
Some progress? |
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
The text was updated successfully, but these errors were encountered: