Database Develop

[DEV] Call to Arms!

I reedited this first post in order to update with further changelog in possible development that i make/work on, the most recent one is the LTX Kernel, logo down below, flashable zip soon, git link here if you want to cooperate/help.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The journey so far: (aka Kernel's changelog)
OC up to 1.9 Ghz added
Many governors like Smartass, Lionheart, InteractiveX, OndemandX.
Added SIO scheduler.
Added enormous amonts of changes because of compile errors, my bad most of them, soon the flashable will come
Click to expand...
Click to collapse
What to be expected? (aka future plans)
Upgrade Smartass to SmartassV2
Possible tweaks to battery
-Prepared for CM9-
Click to expand...
Click to collapse
Old thread head:
Hi, i'm new to this forum as i've recently bought this device from my friend as my beloved Streak has a nice wallpaper (smashed screen).
I'm not really able to see who is developing anymore and who doesn't, also, i have some dev-in skills so i can help to mobilise this forum as this device is great so let's get to work!
My ideea is to get in one place all the DEV's that are working on some ROM's and all the ones that are willing to test new things.
Just post everything to get to know things around here.
Click to expand...
Click to collapse
I would say that the best road for this device would be CM9 fully functional, CM10 fully functional and maybe, maybe an universal kernel.
I wait your suggestions and i hope i can help with something around here

+1 for IDEA

+ 1

I'm no developer but happy to be a test pilot.
Did quite a bit on the Desire and DHD.

I'll gladly be a tester as well, i can't wait to see CM10 running smoothly on my SXL

Unfortunately not a DEV but will be glad to test roms. Loving the idea mate.

I am a programmer(well familiar with C and linux, some basic knowledge about kernels), although my android dev skills are quite questionable, but if anyone can point me to good resources on porting ROMs with linux(I've only seen tutorials on doing stuff in windows) I would gladly help with anything I can, from development and research to testing. We have an awesome, and I believe utterly underrated, device. I would love to participate with anything I can!

kunev said:
I am a programmer(well familiar with C and linux, some basic knowledge about kernels), although my android dev skills are quite questionable, but if anyone can point me to good resources on porting ROMs with linux(I've only seen tutorials on doing stuff in windows) I would gladly help with anything I can, from development and research to testing. We have an awesome, and I believe utterly underrated, device. I would love to participate with anything I can!
Click to expand...
Click to collapse
I totally agree with you, this is another underrated device, like my other device i have (see signature), i'm just like you, well familiar with C and linux and same and maybe some good knowledge about scavanging ROM's and porting to other devices, so welcome to the club!
I recommend some tutorials for starters, found here, here and here.
Note that those tutorials are not written for our device, so differences will surely occur in places, but is a good place to start, also, Google is a good friend, they have nice tutorials about Android found here.
In my opinion, porting ROM's is more research and testing that research and development.

I totally agree, but porting roms to me is the easy part, it was a lot of trial and error and I got many many roms booting, but without the right kernel they were kinda not much use. So I then spent many hours trying to compile an AOSP kernel for this device, but as I am kinda new to the kernel thing, I wasn't very successful.
For anything to do with compiling you will need to get very used to using github.
I used to have a Dell Streak too and loved it

[vertigo] said:
I totally agree, but porting roms to me is the easy part, it was a lot of trial and error and I got many many roms booting, but without the right kernel they were kinda not much use. So I then spent many hours trying to compile an AOSP kernel for this device, but as I am kinda new to the kernel thing, I wasn't very successful.
For anything to do with compiling you will need to get very used to using github.
I used to have a Dell Streak too and loved it
Click to expand...
Click to collapse
Well, i'm hitting my head against the rock, trying to learn as much as possible about kernels, development, editting, in a sentence, all that involves linux kernel for android.
My adantage is that i'm experienced in C language (not Guru, experienced ).
Well, i'm kind of young (20 years old) so i think i can learn those things at a fast pace, but soon i'm going back to school (college), my main project now is to figure out all the kernel tweaks i can find, how can i model it to my liking, and how to make it as universal as possible (to support GB, ICS and maybe the future JB release if it will be ported ).
Untill then, no progress will be made by me as i like to start with the hard things first, also, JB in my opinion should be build up from source (many hours of compiling) to ensure maximum functionality.

Well my advice would be don't try to learn it all at once, because it will just get confusing, just try one thing at a time and once you've got that, everything else should start making a little more sense, well it did with me
To be honest if you're wanting full functionality from CM9 it would be better compiling it from source, because starting with ICS the kernel is built when you compile the rom, rather than working on a port of it.
As far as kernel development goes, I would suggest starting with this. Here is DutchDanny's github from his OC kernel for GB and you can then look and understand what has been changed and maybe try to port them over to ICS kernel, click on where it says branch and change it from master to BinDroid kernel. Then you will need to start learning on how to use 'git gui' and on how to add patches from one kernel to another.
Obviously you would need to download the original source files for the kernel and they can be found here https://github.com/htc-mirror/runnymede-ics-crc-3.0.16-c297c99.git
I would suggest looking at this thread http://forum.xda-developers.com/showthread.php?t=1039854 as it suggests the tools you would need for kernel compiling

[vertigo] said:
Well my advice would be don't try to learn it all at once, because it will just get confusing, just try one thing at a time and once you've got that, everything else should start making a little more sense, well it did with me
To be honest if you're wanting full functionality from CM9 it would be better compiling it from source, because starting with ICS the kernel is built when you compile the rom, rather than working on a port of it.
As far as kernel development goes, I would suggest starting with this. Here is DutchDanny's github from his OC kernel for GB and you can then look and understand what has been changed and maybe try to port them over to ICS kernel, click on where it says branch and change it from master to BinDroid kernel. Then you will need to start learning on how to use 'git gui' and on how to add patches from one kernel to another.
Obviously you would need to download the original source files for the kernel and they can be found here https://github.com/htc-mirror/runnymede-ics-crc-3.0.16-c297c99.git
I would suggest looking at this thread http://forum.xda-developers.com/showthread.php?t=1039854 as it suggests the tools you would need for kernel compiling
Click to expand...
Click to collapse
Thank you very much for the info, the source files are downloaded since i bought the phone , still looking through them, i downloaded them from the htcdev.com, i'm a little low on space on my laptop to try and compile from source a whole ROM so i'm starting with the kernel, and see what makes what and who does who, i'm planning to buy an external HDD soon enough. Honestly, the hardest part to me in all this dev-ing is to keep researching, as i'm a little lazy, but for now i can tell you that i''m addicted to ROM development, scavanging, tweaking, reading and things like that, i think the hot sun had some odd effects on me

Yeah you will need about 30gb for a full rom compile and anything up to about 90gb for a series of compiles lol. The initial repo sync is about 6gb....
Sent from my Galaxy Nexus using xda premium

[vertigo] said:
Yeah you will need about 30gb for a full rom compile and anything up to about 90gb for a series of compiles lol. The initial repo sync is about 6gb....
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
External HDD coming soon, compiling and experimenting coming soon
Since then, aquiring tools, looking around source codes, comparing kernels, right now i'm comparing source kernels and trying to figure out how the hardware really works
Hope to compile something worthile soon enough

New thing discovered today, if you hit the factory reset from S-OFF Hboot bootloader, the sd-card becomes corrupted, nice discovery, no nand recovery no nothing now
I was able to make it alive again by mounting via recovery and formatting from windows...
Hope this helps someone else out there...

Hey mate, just wondering how this development was going. We all appreciate your efforts and hopefully you are able to produce a good rom

nipsadinio said:
Hey mate, just wondering how this development was going. We all appreciate your efforts and hopefully you are able to produce a good rom
Click to expand...
Click to collapse
Hey, i've been trying to port a CM9 from different devices that has the same processor (ex. Xperia Arc) and trying to compile from source an AOSP ICS, nothing good right now, still have lots of things to learn to compile from source, and my flavour of CM9 doesn't boot, so not too good right now as i was a little busy as i returned to school and had to relocate.
Hope to get something worthwile soon enough... I will try to find someone who can help me here at the university campus for the development.
If anything new happens, it will be posted here

Sounds really good we all hope you never give up the fight
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium

No worries mate, always keep real life as a priority but great to know your still going at it. Cheers!

nipsadinio said:
No worries mate, always keep real life as a priority but great to know your still going at it. Cheers!
Click to expand...
Click to collapse
I think i found the right guy to help me at development, a good friend of mine said he is a guru in Android, i'm going to test that later this day if he is like my friend said, than the development will recieve a good and welcomed kick in the a*s

JB4.3 for p970

This topic is for other developers, not for users who are eagerly waiting for something that may never come
I know that upstream p970 development has stopped. However, I still find it a challenge to get JB4.3 running on the p970. Main reasons is that on the Samsung Galaxy Tab 10.1 (which has also been discontinued by CM-team due to the outdated tegra2 chipset) CM10.2 actually seems to run smoother than CM10.1 (possibly due to the code cleaning from JB4.2 -> JB4.3).
I have started by adding some missing variable to BoardConfig.mk and enabling SELinux in kernel, but already bumped into some compiling issues. Are there any others working on this, or interested in helping?!

Not going into technical part but I have heard and strongly believe that new version means not really a high-end hardware only. According to my knowledge KLP will run smoothly on a device having 512mb of RAM.

and how are you going to get 5.0 if you don't have the source code?! it will be just full of bugs, unusable

recl said:
and how are you going to get 5.0 if you don't have the source code?! it will be just full of bugs, unusable
Click to expand...
Click to collapse
????
JB is build based on pure android code from google. So that is the source code necessary...

Honestly,if I could choose from android 4.3 and android 5.0, I'll prefer to wait for android 5.0! Android 5.0 is designed to ensure the performance on old and low-end devices !
I am looking forward for developers to port android 5.0 into our device!!!

I'm willing to help in testing so ring me up anytime!
Sent from my LG-P970 using Tapatalk 4

kasper_h said:
This topic is for other developers, not for users who are eagerly waiting for something that may never come
Click to expand...
Click to collapse
What this mean for you guys?

It is booting already!
only running into some stagefright issues so the display isnt turning on, but i already get access to the logcat to debug.
our target is getting closer and closer

Nice job

What is the deal with the camera on Android 6

Hi,
I was hoping to get some clarification about what is going on with the camera on Android 6.
I think what from reading so far the camera needs some closed source blob, that is kind of like a driver for it, specifically for one version of the Android Kernel.
And this blob must exist for CAF/Qualcomm 3.4 Kernel used in the Stock rom and lately also Sony 3.10 Kernel used in the 5.1 AOSP build?
What I do not get is, why can none of the existing blobs not be used with the Kernel Android 6.0 AOSP requires.
And also: Is this just a matter of time until someone gets it working, or are we totally dependant on Sony to release the blob for the new kernel, or camera will never work.
Any insight would be nice

user822 said:
Hi,
I was hoping to get some clarification about what is going on with the camera on Android 6.
I think what from reading so far the camera needs some closed source blob, that is kind of like a driver for it, specifically for one version of the Android Kernel.
And this blob must exist for CAF/Qualcomm 3.4 Kernel used in the Stock rom and lately also Sony 3.10 Kernel used in the 5.1 AOSP build?
What I do not get is, why can none of the existing blobs not be used with the Kernel Android 6.0 AOSP requires.
And also: Is this just a matter of time until someone gets it working, or are we totally dependant on Sony to release the blob for the new kernel, or camera will never work.
Any insight would be nice
Click to expand...
Click to collapse
Hi,
first of all - sony released MM (6.0) blobs for 3.10 kernel on 2. February, so there are all things that developers need from sony. (including camera)
Existing blobs can't be used because all custom roms were using very old camera blob from 4.3 Jelly bean stock - newer blobs have some (DRM) protection on them so that they cannot be used. And unfortunately this old camera blob is not usable on MM, so CM team decided to wait for sony to release open source (they just call it open source, blobs are still closed source, but they are compatible with AOSP, unlike stock ones) one.
And why it still isn't working? Because there is still a lot of work ongoing on sonyxperiadev github, so I guess CM is waiting till the changes are complete.
Last thing I want to say - I'm not a developer, so I may be wrong. This is just how I understand the situation there.

SuperLamic said:
Hi,
first of all - sony released MM (6.0) blobs for 3.10 kernel on 2. February, so there are all things that developers need from sony. (including camera)
Existing blobs can't be used because all custom roms were using very old camera blob from 4.3 Jelly bean stock - newer blobs have some (DRM) protection on them so that they cannot be used. And unfortunately this old camera blob is not usable on MM, so CM team decided to wait for sony to release open source (they just call it open source, blobs are still closed source, but they are compatible with AOSP, unlike stock ones) one.
And why it still isn't working? Because there is still a lot of work ongoing on sonyxperiadev github, so I guess CM is waiting till the changes are complete.
Last thing I want to say - I'm not a developer, so I may be wrong. This is just how I understand the situation there.
Click to expand...
Click to collapse
I don't think that's entirely correct. Sony released blobs have never worked for AOSP camera. They have also not released anything for 3.10 kernel. I also don't think that jb blobs were used in up to LP5.1.1, as 4.3 camera never fully worked. If you look at CM gerrit, they say that they were able to have camera work once on MM with 3.4 kernel, but then they couldn't repeat it. Then, out of frustration and because they know Sonyxpdevs have abandoned 3.4 for good, CM have decided to switch to 3.10 kernel and wait for Sony to fix it. Good luck: Sonyxpdevs couldn't have camera work on ANY aosp rom...
So, the answer is, in my view: (i) potentially, we can have camera in MM with 3.4 kernel, but nobody is working on it in favor of 3.10; and (ii) not in our lifetime on 3.10. This is a pity and really has very little sense: Both 3.4 and 3.10 are hopelessly outdated (Linux is using 4.x already), so, why not to try to have it with 3.4, which worked fine up to MM? One of the reasons is that many developers just don't like CM (jealousy?), and CM isn't going to lift a finger for 2 devices (Z1 and Z1c), which they consider legacy devices. So, no luck. But in my view, M is crap (LP is crap too) LOL... Kitkat is still a lot more preferable...

optimumpro said:
I don't think that's entirely correct. Sony released blobs have never worked for AOSP camera. They have also not released anything for 3.10 kernel. I also don't think that jb blobs were used in up to LP5.1.1, as 4.3 camera never fully worked. If you look at CM gerrit, they say that they were able to have camera work once on MM with 3.4 kernel, but then they couldn't repeat it. Then, out of frustration and because they know Sonyxpdevs have abandoned 3.4 for good, CM have decided to switch to 3.10 kernel and wait for Sony to fix it. Good luck: Sonyxpdevs couldn't have camera work on ANY aosp rom...
So, the answer is, in my view: (i) potentially, we can have camera in MM with 3.4 kernel, but nobody is working on it in favor of 3.10; and (ii) not in our lifetime on 3.10. This is a pity and really has very little sense: Both 3.4 and 3.10 are hopelessly outdated (Linux is using 4.x already), so, why not to try to have it with 3.4, which worked fine up to MM? One of the reasons is that many developers just don't like CM (jealousy?), and CM isn't going to lift a finger for 2 devices (Z1 and Z1c), which they consider legacy devices. So, no luck. But in my view, M is crap (LP is crap too) LOL... Kitkat is still a lot more preferable...
Click to expand...
Click to collapse
well, you're not watching community here so much alviteri is woring on Z1 even he doesn't have the device and here you go.
And yes, they made camera working like two months ago on Lollipop on 3.10 kernel with aosp blobs and now - a few days ago even on marshmallow. It's only matter of time when it will work.
Check this: https://github.com/SonyAosp (there you have blobs and everything from alviteri)

SuperLamic said:
well, you're not watching community here so much alviteri is woring on Z1 even he doesn't have the device and here you go.
And yes, they made camera working like two months ago on Lollipop on 3.10 kernel with aosp blobs and now - a few days ago even on marshmallow. It's only matter of time when it will work.
Check this: https://github.com/SonyAosp (there you have blobs and everything from alviteri)
Click to expand...
Click to collapse
Well. As I said before, no one is working on making camera work with 3.4. Also, as far as blobs, according to davitery, "there is nothing to do" because of Sony: http://forum.xda-developers.com/showpost.php?p=64582482&postcount=33

optimumpro said:
Well. As I said before, no one is working on making camera work with 3.4. Also, as far as blobs, according to davitery, "there is nothing to do" because of Sony: http://forum.xda-developers.com/showpost.php?p=64582482&postcount=33
Click to expand...
Click to collapse
yes, this post was right on 31st December, but now is 6th February and the blobs ARE now available as I said before (and you can see screen with working camera in my previous post)
https://github.com/SonyAosp/platform_vendor_sony/commit/4f7409446779f371973035720935c36dbd09d7cc

SuperLamic said:
yes, this post was right on 31st December, but now is 6th February and the blobs ARE now available as I said before (and you can see screen with working camera in my previous post)
https://github.com/SonyAosp/platform_vendor_sony/commit/4f7409446779f371973035720935c36dbd09d7cc
Click to expand...
Click to collapse
I think the picture about camera is for Z3, which is not rhine. Also, if you look at the new blobs, there is nothing new for rhine devices; they just took out some older binaries, which are useless anyway. And this is consistent with Sony saying there won't be M for Z1. We will see, but I am not holding my breath.
Edit: I just downloaded the latest M blobs and everything in rhine and honami folders is dated August 2015. So, there is definitely nothing new for our device...

optimumpro said:
I think the picture about camera is for Z3, which is not rhine. Also, if you look at the new blobs, there is nothing new for rhine devices; they just took out some older binaries, which are useless anyway. And this is consistent with Sony saying there won't be M for Z1. We will see, but I am not holding my breath.
Edit: I just downloaded the latest M blobs and everything in rhine and honami folders is dated August 2015. So, there is definitely nothing new for our device...
Click to expand...
Click to collapse
Well, I didn't test it, so I don't know. But does it even make sense to release camera for Z3 and not for Z1 in the same package?
Anyway why do you think that they are useless? I tried that crdroid rom and it's not that bad (except for touchscreen driver and camera). And AOSP camera was definitely working on Lollipop (I personally tried it on build from erikcas), so it wouldn't make sense not to update it too when it requires only update their wrapper - and they can even use the one from Z3. (I don't really understand CM developers why they can't use Lollipop camera AOSP blob with simple wrapper to fit on Marshmallow, but I understand that it's more work and it's easier to wait)
I'm not that optimistic about Marshmallow officially, but I do think that they will release at least a bit usable blobs.

SuperLamic said:
Well, I didn't test it, so I don't know. But does it even make sense to release camera for Z3 and not for Z1 in the same package?
Anyway why do you think that they are useless? I tried that crdroid rom and it's not that bad (except for touchscreen driver and camera). And AOSP camera was definitely working on Lollipop (I personally tried it on build from erikcas), so it wouldn't make sense not to update it too when it requires only update their wrapper - and they can even use the one from Z3. (I don't really understand CM developers why they can't use Lollipop camera AOSP blob with simple wrapper to fit on Marshmallow, but I understand that it's more work and it's easier to wait)
I'm not that optimistic about Marshmallow officially, but I do think that they will release at least a bit usable blobs.
Click to expand...
Click to collapse
"make sense to release camera for Z3 and not for Z1 in the same package"
No, it doesn't, because Sony engineers do work on Z3 and NOT on rhine (Z1 and Z1c) devices.
You are confusing several things: the fact that camera worked with LP AOSP has nothing to do with M blobs, but rather the fact that Sony released a crippled AOSP camera for lollipop. This camera has nothing to do with M. And note, Sony released LP camera only after Android has moved to M.
Now, about M. The reason I think real blobs are not coming is that first Sony engineers must create stock M for rhine devices (and it ain't coming, because Sony said so). Then, they dumb stock down for custom roms. That's the usual way. But because M isn't coming to rhine devices, there is nothing to dumb down, unfortunately. And rhine is a different platform, as compared to Z3 and up. Not to mention that 3.10 kernel is the whole new deal on top of that. So, if there is a chance we could have a fully functional camera on M, it would rather be with 3.4, but no one seems to be working on 3.4 in favor of 3.10...

optimumpro said:
"make sense to release camera for Z3 and not for Z1 in the same package"
No, it doesn't, because Sony engineers do work on Z3 and NOT on rhine (Z1 and Z1c) devices.
You are confusing several things: the fact that camera worked with LP AOSP has nothing to do with M blobs, but rather the fact that Sony released a crippled AOSP camera for lollipop. This camera has nothing to do with M. And note, Sony released LP camera only after Android has moved to M.
Now, about M. The reason I think real blobs are not coming is that first Sony engineers must create stock M for rhine devices (and it ain't coming, because Sony said so). Then, they dumb stock down for custom roms. That's the usual way. But because M isn't coming to rhine devices, there is nothing to dumb down, unfortunately. And rhine is a different platform, as compared to Z3 and up. Not to mention that 3.10 kernel is the whole new deal on top of that. So, if there is a chance we could have a fully functional camera on M, it would rather be with 3.4, but no one seems to be working on 3.4 in favor of 3.10...
Click to expand...
Click to collapse
Ok I understand. But it's still android, isn't it? So camera API is not changed that much and there must be some way how to put another layer between the blob and kernel (the wrapper). Every time I see another device's tree updated to Marshmallow I see updated camera wrapper (only one or two lines changed). So I'm wondering why this isn't possible on our device, especially when CM was using a wrapper on stock blob.

SuperLamic said:
Ok I understand. But it's still android, isn't it? So camera API is not changed that much and there must be some way how to put another layer between the blob and kernel (the wrapper). Every time I see another device's tree updated to Marshmallow I see updated camera wrapper (only one or two lines changed). So I'm wondering why this isn't possible on our device, especially when CM was using a wrapper on stock blob.
Click to expand...
Click to collapse
Current stock blobs don't work on 3.10, and there is no stock for 3.10. So, there is nothing to wrap...
You should ask the devs why they prefer to bang their heads (in the dark) on a totally foreign to Sony 3.10, when they can work on adapting 3.4 to work with August M blobs.

optimumpro said:
Current stock blobs don't work on 3.10, and there is no stock for 3.10. So, there is nothing to wrap...
You should ask the devs why they prefer to bang their heads (in the dark) on a totally foreign to Sony 3.10, when they can work on adapting 3.4 to work with August M blobs.
Click to expand...
Click to collapse
so what's this? http://www.cas-online.nl/author/erikcas/
edit: my bad, I ment why is not possible to wrap aosp ones

SuperLamic said:
so what's this? http://www.cas-online.nl/author/erikcas/
edit: my bad, I ment why is not possible to wrap aosp ones
Click to expand...
Click to collapse
Sony has opened the entire camera (not just blobs) for Lollipop, so, because it is open and you know your "addresses", it will work with other kernels (like 3.10). This is different from having closed source blobs (with uknown addresses) wrap around for a particular kernel. When they release crippled camera for M, then it would be possible. But why would Sony release crippled camera for M if M isn't coming to Z1?

So, the answer is, in my view: (i) potentially, we can have camera in MM with 3.4 kernel, but nobody is working on it in favor of 3.10; and (ii) not in our lifetime on 3.10.
Click to expand...
Click to collapse
So anything AOSP 6.0 with working camera will never come to Z1 ?

Camera works, (of course with poor quality) in the latest cRDroid 6.0.1 build.

hey @optimumpro
have you seen this? https://github.com/SonyAosp/platform_vendor_sony/commit/43c92897de18e71d40aa4fe3da350ea19c5c7ba9
I can see there some new camera blobs for honami, what do you think?

SuperLamic said:
hey @optimumpro
have you seen this? https://github.com/SonyAosp/platform_vendor_sony/commit/43c92897de18e71d40aa4fe3da350ea19c5c7ba9
I can see there some new camera blobs for honami, what do you think?
Click to expand...
Click to collapse
@SuperLamic i hope it's have deal with kernel 3.10
from i read the discussion the old blobs can deal with 3.4 and not 3.10 but all favor 3.10
what do you think?

DectonX said:
@SuperLamic i hope it's have deal with kernel 3.10
from i read the discussion the old blobs can deal with 3.4 and not 3.10 but all favor 3.10
what do you think?
Click to expand...
Click to collapse
huh, I'm not really sure that I understand.
But - yes new blobs should not be compatible with old 3.4 kernel (though I didn't test it and I'm not planning on to)
so now all 6.0-MM roms use 3.10 kernel and new blobs. I don't think that it's that bad as optimumpro says. Many things improved, but it's true that we have to wait for it because of still ongoing development.

SuperLamic said:
huh, I'm not really sure that I understand.
But - yes new blobs should not be compatible with old 3.4 kernel (though I didn't test it and I'm not planning on to)
so now all 6.0-MM roms use 3.10 kernel and new blobs. I don't think that it's that bad as optimumpro says. Many things improved, but it's true that we have to wait for it because of still ongoing development.
Click to expand...
Click to collapse
Here is a fact: sonyxpdev team has NEVER had camera fully working on any aosp rom. So, what makes anyone think things are going to be different on MM? They won't. The only chance was to have it work with cm device trees and 3.4 kernel, but that ain't coming, because CM and everyone else switched to aosp trees and 3.10.
So, if you want MM, buy a new device.

[ROM][H60-L04][Cherry?][Unofficial] CM 14

~wrong devices kek

Cherry is Honor 4/4X - https://wiki.cyanogenmod.org/w/Cherry_Info
I think the Honor 6 codename was hwH60 or something like that.

Please delete the links or the entire thread as soon as possible, if people will start flashing this then we will likely have a lot of bricked devices. Venipa, this is horrible irresponsibility on your side to upload links to unknown stuff without even testing it yourself (even if you put a disclaimer)! And to all the guys thinking that we will magically get working CM one day, think again. You found a semi-official build of CM for some Huawei device and seriously thought it's a H60 build we didn't hear about before? If there is ever a proper CM release, it will take time to do it. But people posting stuff like "I've already posted the Full Source including Kernel Source and still no one wants to do it" will never understand how hard it is to make a ROM, or what exactly "full sources" mean...

MaRtYy01 said:
Cherry is Honor 4/4X -
I think the Honor 6 codename was hwH60 or something like that.
Click to expand...
Click to collapse
Honor 6 is mogolia​

sado1 said:
Please delete the links or the entire thread as soon as possible, if people will start flashing this then we will likely have a lot of bricked devices. Venipa, this is horrible irresponsibility on your side to upload links to unknown stuff without even testing it yourself (even if you put a disclaimer)! And to all the guys thinking that we will magically get working CM one day, think again. You found a semi-official build of CM for some Huawei device and seriously thought it's a H60 build we didn't hear about before? If there is ever a proper CM release, it will take time to do it. But people posting stuff like "I've already posted the Full Source including Kernel Source and still no one wants to do it" will never understand how hard it is to make a ROM, or what exactly "full sources" mean...
Click to expand...
Click to collapse
Can you tell me what exactly is missing from the source provided by Huawei?

Henrikx said:
Can you tell me what exactly is missing from the source provided by Huawei?
Click to expand...
Click to collapse
I'm not a developer so somebody else should be able to explain it better, but in general, the sources provided by Huawei are at most only useful enough to make a AOSP-style ROM based on the same Android version as the EMUI ROM the source is released for. So, no CM, no newer Androids than Marshmallow, etc.

nooo, got my hopes up (

sado1 said:
I'm not a developer so somebody else should be able to explain it better, but in general, the sources provided by Huawei are at most only useful enough to make a AOSP-style ROM based on the same Android version as the EMUI ROM the source is released for. So, no CM, no newer Androids than Marshmallow, etc.
Click to expand...
Click to collapse
Not true.Then why kirin based p8 lite has cm14?
http://forum.xda-developers.com/p8lite/general/cyanogenmod-14-t3458451
Its because we dont have devs and our device isnt that popular.Kirins arent the most rom friendly cpus,but they arent totally useless.

MaRtYy01 said:
Not true.Then why kirin based p8 lite has cm14?
http://forum.xda-developers.com/p8lite/general/cyanogenmod-14-t3458451
Its because we dont have devs and our device isnt that popular.Kirins arent the most rom friendly cpus,but they arent totally useless.
Click to expand...
Click to collapse
Okay, this proves me wrong. And obviously, I completely ignored the fact that our device already had a CM port, so indeed with a dedicated developer we'd have a chance to get something. What I probably should've said is that a potential developer has a lot of work ahead because of poor sources quality from Huawei, and absolutely no chance to make an official CM port for example. Of course, this all is based on random stuff I read on XDA about it, so you guys should wait until someone more knowledgeable responds to have a clear picture on the problems the development for this device is facing.

Heartbreak.

Thread closed as per OP's request

P10 & P10 Kernel Sources Now Available

As im sure some of you know Huawei have finally released the Kernel Sources for the P10 series enabling for much further development.
I would link the news source but apparently the XDA app does not want to lol.
Cheers

Here is http://consumer.huawei.com/en/opensource/detail/index.htm

Is it too difficult to build AOSP from this sources?

Its possible but not enough time ...

Because? The source relajease since June. I don't understand. It's very difficult built custom kernel and AOSP ROM?

Custom Kernel is not possible because there a bug that you cant took pictures with Huawei Stock camera.
AOSP for huawei is an unofficial build so you need to search all needed files from stock and that is not
easy if you dont do that every day
And testing with reading logfiles need a lot of time too. You can try if you want.

Blackball said:
Custom Kernel is not possible because there a bug that you cant took pictures with Huawei Stock camera.
AOSP for huawei is an unofficial build so you need to search all needed files from stock and that is not
easy if you dont do that every day
And testing with reading logfiles need a lot of time too. You can try if you want.
Click to expand...
Click to collapse
Thank you by your answer. I don't know compile AOSP ROM. SORRY

Blackball said:
Custom Kernel is not possible because there a bug that you cant took pictures with Huawei Stock camera.
AOSP for huawei is an unofficial build so you need to search all needed files from stock and that is not
easy if you dont do that every day
And testing with reading logfiles need a lot of time too. You can try if you want.
Click to expand...
Click to collapse
can you tell exactly what changes to the kernel makes the camera stop working ? Because i am trying to compile kernel and make a few small changes like adding new governors just to have some fun. Will adding governors and other small mods make the camera not work ?
I am going to use the custom kernel on stock rom so the camera should work right ?