Related
I am trying to build OMNI 4.4.4 for H60-L02. Right now I have managed to see the bootanimation of omni and then I have a bootloop. These are the logs for anyone who are willing to help
Logcat : http://pastebin.com/RT5x5EjJ
Dmesg : http://pastebin.com/PSzj9XJR
So, let's try to build roms for honor 6 !!! Any help is welcome ....
I don't have the skills but I'm willing to support the initiative as far as I can!
Sounds like the same issue i had, check google-cert folder that you have it and also build the files so that you edit default storage path. It was a few months ago i tried to build my own and i ended up with similair problem and it was related to missing cert and wrong storage path.
Im no expert, its just a hobby of mine so i might be wrong
Is Cyanogenmod avialable to Honor 6
Is Cm 11 available to Honor 6
Kanth's said:
Is Cm 11 available to Honor 6
Click to expand...
Click to collapse
No Cyanogenmod available yet, we all wait for.
HTC HD2 has CM12 already ^^
spanorg said:
I am trying to build OMNI 4.4.4 for H60-L02. Right now I have managed to see the bootanimation of omni and then I have a bootloop. These are the logs for anyone who are willing to help
Logcat : http://pastebin.com/RT5x5EjJ
Dmesg : http://pastebin.com/PSzj9XJR
So, let's try to build roms for honor 6 !!! Any help is welcome ....
Click to expand...
Click to collapse
@spanorg, what do you think of the information of codeworkx?
Daniel Hillenbrand a.k.a. codeworkx is a member of Team CM and TeamHacksung, is a legend
panamera2011 said:
@spanorg, what do you think of the information of codeworkx?
Click to expand...
Click to collapse
Go! go! go!
panamera2011 said:
@spanorg, what do you think of the information of codeworkx?
Daniel Hillenbrand a.k.a. codeworkx is a member of Team CM and TeamHacksung, is a legend
Click to expand...
Click to collapse
I have in my hands this info from the first hour I took the phone. I have built a whole device tree not only the partitions. Anyway, I appreciate any help. The big problem is that some sources of Huawei are not given. Especially for the kirin920 soc. That's why development is very difficult. Anyway, I am still trying for building... For any news, I will immediately tell you.
spanorg said:
I have in my hands this info from the first hour I took the phone. I have built a whole device tree not only the partitions. Anyway, I appreciate any help. The big problem is that some sources of Huawei are not given. Especially for the kirin920 soc. That's why development is very difficult. Anyway, I am still trying for building... For any news, I will immediately tell you.
Click to expand...
Click to collapse
Ok, thanks for try to build a CM :good:
Let's hope so!
spanorg said:
I have in my hands this info from the first hour I took the phone. I have built a whole device tree not only the partitions. Anyway, I appreciate any help. The big problem is that some sources of Huawei are not given. Especially for the kirin920 soc. That's why development is very difficult. Anyway, I am still trying for building... For any news, I will immediately tell you.
Click to expand...
Click to collapse
I've no doubt about this. @spanorg please help codeworkx (this IP the thread: http://forum.xda-developers.com/showthread.php?p=58283578).
He's searching for a tester whit competences. I think your help could be more precious now, you are a recognized developer and you can do more than a tester. you can collaborate whit him, and finally became our leader.
(we can ask for donations or other, if possible, to support your works)
Thanks.
spanorg said:
I have in my hands this info from the first hour I took the phone. I have built a whole device tree not only the partitions. Anyway, I appreciate any help. The big problem is that some sources of Huawei are not given. Especially for the kirin920 soc. That's why development is very difficult. Anyway, I am still trying for building... For any news, I will immediately tell you.
Click to expand...
Click to collapse
What do you need?
Here's a kernel for inline building:
https://github.com/codeworkx/android_kernel_huawei_h60
In original sources, have at look at drivers/vendor/hisi.
There are some "acore" folders with android userspace stuff. Doesn't belong there, but it's there.
I've seen some kirin stuff for bionic.
For everything else you have to use their libraries and make them working with aosp.
I assume this requires a ****load of bad hacks.
codeworkx said:
What do you need?
Here's a kernel for inline building:
https://github.com/codeworkx/android_kernel_huawei_h60
In original sources, have at look at drivers/vendor/hisi.
There are some "acore" folders with android userspace stuff. Doesn't belong there, but it's there.
I've seen some kirin stuff for bionic.
For everything else you have to use their libraries and make them working with aosp.
I assume this requires a ****load of bad hacks.
Click to expand...
Click to collapse
Hi codeworkx, I tried to compile cyanogenmod11 with your reposity, but I haven't not file local_manifests.xml .. you can send me right local_manifests.xml ?
Steve Giordano said:
Hi codeworkx, I tried to compile cyanogenmod11 with your reposity, but I haven't not file local_manifests.xml .. you can send me right local_manifests.xml ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/honor-6/orig-development/cyanogenmod-dev-thread-t3008138
please don't build if you don't know what you're doing.
This will not boot into android and requires a ton of work.
codeworkx said:
What do you need?
Here's a kernel for inline building:
https://github.com/codeworkx/android_kernel_huawei_h60
In original sources, have at look at drivers/vendor/hisi.
There are some "acore" folders with android userspace stuff. Doesn't belong there, but it's there.
I've seen some kirin stuff for bionic.
For everything else you have to use their libraries and make them working with aosp.
I assume this requires a ****load of bad hacks.
Click to expand...
Click to collapse
Do you have a link for the kirin stuff for bionic?
spanorg said:
Do you have a link for the kirin stuff for bionic?
Click to expand...
Click to collapse
sorry, my fault.
just stuff for the bootloader.
vendor/hisi/modem/drv/acore/bootable/bootloader/legacy/arch_balongv7r2
Is this project still active? Just curious.
Hey guys its devut again informing you that HOX's Device tree is nearlyready!!!
UPDATE: DEVICE TREE IS NOW COMPLETE
Nearly
Yes Nearly because libdgv1 is still taking time
libdgv1
http://dmitry.gr/index.php?r=06. Thoughts&proj=04. Android M on Grouper
Here it states that we get a lot of problem because
Code:
dlopen()
is a POSIX COMPLAINT:crying::crying:
So here it is nearly perfect Marshmallow device tree
https://github.com/DevUt/android_device_htc_endeavoru/tree/Marshmallow-begins-part-1
I also have not tested it for new layout
If you are a developer then please check it
[ Do not go for storage_list.xml (as it is deleted , go for fsatb)]
Another issue (damn it)
Proprietary-files.txt has a problem ! Will fix it soon
DevUt said:
Another issue (damn it)
Proprietary-files.txt has a problem ! Will fix it soon
Click to expand...
Click to collapse
*finger crossed*
bopung said:
*finger crossed*
Click to expand...
Click to collapse
I think it will take alot of time cause it is verrryyyy confusing
Added issue section in my github repo
1 issue added
you guys also help me by telling me the issues in code
Should i add wiki to my repo to guide other developer?
Or should leave them on their own to figure out how to make libnvos and other thing works ( cause just looking at the tree you wont be able to understand because the patches are also in proprietary files )?
And another great news the device tree wil be ready till Monday!! :laugh: :good: ????????????
Device tree complete now no monday
DevUt said:
And another great news the device tree wil be ready till Monday!! :laugh: :good:
Click to expand...
Click to collapse
(After this many ppl)
Critic : Monday ? What! You are so slow DevUt!
DevUt : Sorry , Thats the way im!
DevUt : But for other HOX DEVS
DEVICE TREE IS NOW COMPLETE
NOW NO MONDAY
DEV GET THEIR HANDS ON!
Awesome!I was planning to get an s4 but since the hox will actually get mm I will stick to it.Great work,you are awesome dude
MaRtYy01 said:
Awesome!I was planning to get an s4 but since the hox will actually get mm I will stick to it.Great work,you are awesome dude
Click to expand...
Click to collapse
My pleasure dude
I predict you will see mm till mid may cause my net is slow
Thanks for Patience and all your support
But if you wanna try to make a rom from this tree you can (please check the issue section if there are none then please proceed to building if there is even 1 Stop ; I will fix it )
Guys i just found out that we need to have a newer version of twrp to flash marshmallow on our hox. So here's my thought
First i will Fix the device tree ( yes i will be adding some more. Patch files which are on my local pc)
Then as we already have the kernel available for marshmallow.
And then i will build the new twrp and it all in a post
Guys fact of the matter : HOX doesn't runs well on newer roms! And yes thats the bitter truth for every Phone once its old it losses its powet
But why
Here's a logical answer : It is in the way the developer makes the newer roms!
What !
Yes ! Actually the devs just patch some existing files and add some new ones and release it !
And i dont blame the devs for it cause nobody will waste his/her time in writing everything from kernel , Device tree ,proprietary files they sum upto millions and millions of files
Thats causes the problem.
So whats the solution
The solution is nothing! But as a HOX lover i would love to take this whole summer for HOX
So whats your plan
My plan is after releasing marshmallow i would work to write the whole thing scratch (not exactly scratch) but i will make it the most stable rom for HOX
I know im making many promises but believe me i would make them true :highfive:
Thank you for your work, I'm looking forward to marshmallows for HOX.
I'm out of the station for 10 days will come and back to work ASAP
Is this a rom?
sagor1 said:
Is this a rom?
Click to expand...
Click to collapse
The ROM is nearly ready ! Source code has been downloaded tweaks have been made to the device tree ( necessary for ROM ) so you will see the ROM soon . This thread was made to keep updated my fellow friends with my status
Guys bad news my laptop screen has disturbed it is showing vertical lines I will send to soon for repairs and continue until then see my github progress ! You have surprise in both the kernel and my own profile
DevUt said:
The ROM is nearly ready ! Source code has been downloaded tweaks have been made to the device tree ( necessary for ROM ) so you will see the ROM soon . This thread was made to keep updated my fellow friends with my status
Click to expand...
Click to collapse
With sense or without sense?
sagor1 said:
With sense or without sense?
Click to expand...
Click to collapse
Without, its based on cm13
Sent from my Nexus 7 using XDA-Developers mobile app
Hi all,
I've created an issue on Motorola's kernel-msm repo that is a request for them to release the kernel sources for the G 5 Plus (Potter).
The post is here - https://github.com/MotorolaMobilityLLC/kernel-msm/issues/104
Please feel free to reply with similar requests so as to get Motorola moving on a proper GPL source release.
-Rob
bob2600 said:
Hi all,
I've created an issue on Motorola's kernel-msm repo that is a request for them to release the kernel sources for the G 5 Plus (Potter).
The post is here - https://github.com/MotorolaMobilityLLC/kernel-msm/issues/104
Please feel free to reply with similar requests so as to get Motorola moving on a proper GPL source release.
-Rob
Click to expand...
Click to collapse
https://github.com/MotorolaMobilityLLC/kernel-msm/blob/MMI-NPN25.137-15/arch/arm/configs/ext_config/mot8953-potter.config
:good:
The sources are already out....
Oh really? My bad... Can I just pull from that kernel-msm repo mentioned in the original post? Or is there a different repo just for Potter?
It looks like the source release for NPN25.137-15 is tagged here:
https://github.com/MotorolaMobilityLLC/kernel-msm/tree/MMI-NPN25.137-15/
It's a bit older than the version shipped with my phone but it could work. I'm going to see if I can compile it later.
bob2600 said:
It looks like the source release for NPN25.137-15 is tagged here:
https://github.com/MotorolaMobilityLLC/kernel-msm/tree/MMI-NPN25.137-15/
It's a bit older than the version shipped with my phone but it could work. I'm going to see if I can compile it later.
Click to expand...
Click to collapse
All the best. :good:
rayzen6 said:
All the best. :good:
Click to expand...
Click to collapse
Why'd you edit your post? I took a look at Alberto's repo and it looks like it would be compatible with our phones.
Seemed like a decent course of action to take. Did you try it yourself? Did it work? Don't just provide no reason, let's get hacking...
bob2600 said:
Why'd you edit your post? I took a look at Alberto's repo and it looks like it would be compatible with our phones.
Seemed like a decent course of action to take. Did you try it yourself? Did it work? Don't just provide no reason, let's get hacking...
Click to expand...
Click to collapse
Man yes let me mention the guy who successfully able to build with Alberto's sources. He is @i.snehal.kiran.
He has done this to compile but unfortunately for some reason he doesn't able to get the device to test. His msg is below
basically i have taken addison device tree ...just change the kernel path and defconfig name in boradconfig.mk ..makes it build boot.img
the source provided by motorola on github is full of errors..so use alberto's kernel for addison till you get official kernel from moto
https://github.com/Alberto97/android_kernel_motorola_msm8953
I edited the post bcz I thought u want to work with custom kernel for stock rom. And I thought this might not be useful.
bob2600 said:
Why'd you edit your post? I took a look at Alberto's repo and it looks like it would be compatible with our phones.
Seemed like a decent course of action to take. Did you try it yourself? Did it work? Don't just provide no reason, let's get hacking...
Click to expand...
Click to collapse
So what happened next? Did you tried something?
Edit:- btw one of the guy has replied positively on issue. :Good: I think we'll have a separate source soon.
rayzen6 said:
So what happened next? Did you tried something?
Edit:- btw one of the guy has replied positively on issue. :Good: I think we'll have a separate source soon.
Click to expand...
Click to collapse
I got as far as getting the LineageOS sources pulled for 14.1, had to do it twice since it was too big for my home directory so I had to create a new volume and run repo sync again. Took forever, but at least I have the OS sources downloaded. Now we're at the point of getting that kernel and setting up a device configuration for our device. Once we get that, then I can see if we can build and flash.
bob2600 said:
I got as far as getting the LineageOS sources pulled for 14.1, had to do it twice since it was too big for my home directory so I had to create a new volume and run repo sync again. Took forever, but at least I have the OS sources downloaded. Now we're at the point of getting that kernel and setting up a device configuration for our device. Once we get that, then I can see if we can build and flash.
Click to expand...
Click to collapse
Cool. Good work man. I'm in for testing.
Kernel sources are up
https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-NPN25.137-33
Hi,
this is the development thread for LineageOS development. The first release is out and this thread is for developer collaboration!
Everyone who knows C, Java and strace is welcome to participate. Please send git formatted patches!
HELP NEEDED
mixer_paths_tasha.xml and audio_platform_info.xml need tweaking
VoIP needs testing
WifiDisplay support
VoLTE (I can't test this)
Device Trees
https://github.com/cryptomilk/android_kernel_sony_msm8998
https://github.com/cryptomilk/android_device_sony_common-treble
https://github.com/cryptomilk/android_device_sony_yoshino
https://github.com/cryptomilk/android_device_sony_lilac
What about the bootloader?
blackknightavalon said:
What about the bootloader?
Click to expand...
Click to collapse
Just unlock it and have fun. Hopefully someone will be able to figure out a way to backup the DRM keys.
android_fury said:
Just unlock it and have fun. Hopefully someone will be able to figure out a way to backup the DRM keys.
Click to expand...
Click to collapse
And where, exactly, is the tutorial for that? It's not officially supported by Sony yet.
I think I read somewhere that you can select the XZ Premium on the list and follow the steps. Once a DRM backup is available, I may try doing that. By then, the actual XZ1C may already be on the list.
android_fury said:
I think I read somewhere that you can select the XZ Premium on the list and follow the steps. Once a DRM backup is available, I may try doing that. By then, the actual XZ1C may already be on the list.
Click to expand...
Click to collapse
I just checked a few minutes ago. XZ1C's not on there.
Good news ！
I've setup initial repositories, yoshino and lilac. yoshino is a common base shared between devices and I have a Kernel tree over the latest msm-4.0 kernel tree and already compiled it after fixing a log of build issues. I will create repositories in the next days and upload the sources once I have a recovery.
modpunk said:
I've setup initial repositories, yoshino and lilac. yoshino is a common base shared between devices and I have a Kernel tree over the latest msm-4.0 kernel tree and already compiled it after fixing a log of build issues. I will create repositories in the next days and upload the sources once I have a recovery.
Click to expand...
Click to collapse
Great news! Thank you so much for your efforts to bring us LOS for this really awesome compact beast.
Thank you so far, modpunk! Looking forward to it. The phone is great, but stock rom leaves some things to be desired...
Thanks bro, just do it!
Regarding unlocking: I selected X Compact and followed the instructions. Everything worked perfectly and I'm now running AOSP.
Code:
----- Made recovery image: recovery.img --------
#### make completed successfully (11:06 (mm:ss)) ####
modpunk said:
I've setup initial repositories, yoshino and lilac. yoshino is a common base shared between devices and I have a Kernel tree over the latest msm-4.0 kernel tree and already compiled it after fixing a log of build issues. I will create repositories in the next days and upload the sources once I have a recovery.
Click to expand...
Click to collapse
How much are you borrowing from Sony's AOSP repositories? They've been committing pretty heavily to their kernel in particular.
Gairtial said:
How much are you borrowing from Sony's AOSP repositories? They've been committing pretty heavily to their kernel in particular.
Click to expand...
Click to collapse
There was no Kernel release for msm8998 in kernel-copyleft, so I took the msm-4.4 Kernel tree and the tarball they dropped. I've fixed several bugs in the Kernel, I always wonder how the Smartphone manufacturers get their stuff compiled.
You can find the kernel source tree here: https://github.com/cryptomilk/android_kernel_sony_msm8998
I've also added exfat support already.
I've looked at the device repo for their AOSP trees, but started a yoshino and lilac device tree from scratch. I prefer clean repositories. I will push them in the next days, I did quite some cleanup today.
I haven't ordered the device yet. Need to wait till next week, I just came back from a long vacation
modpunk said:
There was no Kernel release for msm8998 in kernel-copyleft, so I took the msm-4.4 Kernel tree and the tarball they dropped. I've fixed several bugs in the Kernel, I always wonder how the Smartphone manufacturers get their stuff compiled.
You can find the kernel source tree here: https://github.com/cryptomilk/android_kernel_sony_msm8998
I've also added exfat support already.
I've looked at the device repo for their AOSP trees, but started a yoshino and lilac device tree from scratch. I prefer clean repositories. I will push them in the next days, I did quite some cleanup today.
I haven't ordered the device yet. Need to wait till next week, I just came back from a long vacation
Click to expand...
Click to collapse
Why the copyleft archive? It doesn't look like they've touched it since April while they touched the regular one 2 hours ago.
I had no issues compiling and running the kernel from https://github.com/sonyxperiadev/kernel, though that was integrated with their entire AOSP tree, which seems to package its own versions of gcc and clang. Perhaps LineageOS includes different prebuilt compilers and that's why you see issues.
Really curious to see how LOS runs though. AOSP has some annoying performance issues and crashes.
Gairtial said:
Why the copyleft archive? It doesn't look like they've touched it since April while they touched the regular one 2 hours ago.
I had no issues compiling and running the kernel from https://github.com/sonyxperiadev/kernel, though that was integrated with their entire AOSP tree, which seems to package its own versions of gcc and clang. Perhaps LineageOS includes different prebuilt compilers and that's why you see issues.
Really curious to see how LOS runs though. AOSP has some annoying performance issues and crashes.
Click to expand...
Click to collapse
I've just tried to build the aosp/LA.UM.5.7.r1 tree from the sony kernel repo. This one has a lot of compiler errors which need fixing first. However for me it looks like that the msm-4.4 tree is much cleaner in this regard so maybe also more advanced.
modpunk said:
I've just tried to build the aosp/LA.UM.5.7.r1 tree from the sony kernel repo. This one has a lot of compiler errors which need fixing first. However for me it looks like that the msm-4.4 tree is much cleaner in this regard so maybe also more advanced.
Click to expand...
Click to collapse
Also fellow LineageOS developers said that the sony 'kernel' repo is a Proof of Concept repo and not what they use in production. So I stick to the production release of MSM.
modpunk said:
I've just tried to build the aosp/LA.UM.5.7.r1 tree from the sony kernel repo. This one has a lot of compiler errors which need fixing first. However for me it looks like that the msm-4.4 tree is much cleaner in this regard so maybe also more advanced.
Click to expand...
Click to collapse
Huh, what kinds of errors are you seeing? I really suspect it must be something different between LOS and AOSP and I'm wondering what it is.
modpunk said:
Also fellow LineageOS developers said that the sony 'kernel' repo is a Proof of Concept repo and not what they use in production. So I stick to the production release of MSM.
Click to expand...
Click to collapse
This may be true but it's also the repo where the most work is done. We should at least pay attention to it in case they commit fixes that are useful.
Also probably getting ahead of myself but I wonder if we can merge EAS... It's in AOSP's common kernel, is it around in LOS anywhere yet?
Gairtial said:
Huh, what kinds of errors are you seeing? I really suspect it must be something different between LOS and AOSP and I'm wondering what it is.
This may be true but it's also the repo where the most work is done. We should at least pay attention to it in case they commit fixes that are useful.
Also probably getting ahead of myself but I wonder if we can merge EAS... It's in AOSP's common kernel, is it around in LOS anywhere yet?
Click to expand...
Click to collapse
You get the errors with -Wmaybe-uninitialized which is a relatively new gcc feature. The Sony 'kernel' repo is their Proof of Concept repository. Yes, sure they are working on it it makes totally sense to try things out there first!
I dunno what EAS is or means ...
(Dear Valued RedMagic Customer,
Thank you for your patience,
Please check the source code at https://github.com/ztemt. If you cannot access the connection, please refresh the interface and try again the next day. Thank you for your understanding.)
Edit :
It's already released.
Now I hope the developers start creating fantastic roms for this beast phone
salahomer said:
(Dear Valued RedMagic Customer,
Thank you for your patience,
Please check the source code at https://github.com/ztemt. If you cannot access the connection, please refresh the interface and try again the next day. Thank you for your understanding.)
Click to expand...
Click to collapse
Isn't our device NX729J? I don't see kernel source released for this... Sounds like they giving you the run around. They would sell a lot more phones if they did release. I almost didn't buy one due to this.. Hopefully they will release it soon.
Edit: Cool! It's finally released!
JWnSC said:
Isn't our device NX729J? I don't see kernel source released for this... Sounds like they giving you the run around. They would sell a lot more phones if they did release. I almost didn't buy one due to this.. Hopefully they will release it soon.
Click to expand...
Click to collapse
Very soon, not now...so let us wait a few more days or weeks
JWnSC said:
Isn't our device NX729J? I don't see kernel source released for this... Sounds like they giving you the run around. They would sell a lot more phones if they did release. I almost didn't buy one due to this.. Hopefully they will release it soon.
Click to expand...
Click to collapse
I see there are 7S and 6S kernels, but I don't see any custom ROMs for them, so idk if we will see any for this phone too.
The repo is now available, however, it's empty by the time of me posting this now. It took them two weeks just to create the repo, that's insane. Well, at least it finally happened. Waiting for sources to be uploaded, they probably have to use slow vpn or something to do that, so it might take quite a bit of time.
What can we do with the kernel source?
So it is here.
JWnSC said:
Isn't our device NX729J? I don't see kernel source released for this... Sounds like they giving you the run around. They would sell a lot more phones if they did release. I almost didn't buy one due to this.. Hopefully they will release it soon.
Click to expand...
Click to collapse
Edit :
It's already released, check again.
Now I hope the developers start creating a new fantastic roms for this beast phone
Well, apparently we'll have to write drivers for our device:
Code:
# nubia driver
drivers/nubia
arch/arm64/configs/vendor/nubia
arch/arm64/configs/vendor/NX729J_diff.config
arch/arm64/configs/vendor/NX729J-perf_diff.config
arch/arm64/configs/vendor/NX729J_driveronly.config
This is from .gitignore, so we can't build this kernel and run it i.e. on stock rom.
aaa.bbb111222 said:
Well, apparently we'll have to write drivers for our device:
Code:
# nubia driver
drivers/nubia
arch/arm64/configs/vendor/nubia
arch/arm64/configs/vendor/NX729J_diff.config
arch/arm64/configs/vendor/NX729J-perf_diff.config
arch/arm64/configs/vendor/NX729J_driveronly.config
This is from .gitignore, so we can't build this kernel and run it i.e. on stock rom.
Click to expand...
Click to collapse
So... What does that mean for new custom roms
gwenmillett said:
So... What does that mean for new custom roms
Click to expand...
Click to collapse
We're not gonna see them until someone writes these drivers or zte publishes them. Both are very unlikely, so...
Seems like they uploaded it again, on zips. I checked and it seems to contain several things inside the /drivers/nubia folder so we probably have now a full workable kernel source