I totally appreciate the effort you spent into development, and maybe I can't thank you enough for that. I know how tough it is to get things going, I've been there and done that. Look for AdyScorpius roms and you'll know.Hello everyone,
At this point just a few words regarding etiquette and the progress on the project:
The project is a Beta and marked as WIP. It is known to us that not everything works, and maybe not even everything as advertised with each release (full or OTA).
We are very sorry for stuff like that the OTA ZIP installer is broken, but you've to to cut us some slack, really, with functionality on the ROM.
First of all without starting a flamewar, the CM12 build is just mostly built from CM sources while we actively work on AOSP code. Regarding that the progress we made from the initial release on the 16th up to now, or even the progress krabappel2548 made before making an initial release is quite considerable.
Regardless, this here is not a daily driver and it will not be so until we flag it as such. You can not magically expect everything to work just because we push a new update. Some things will work, some will not.
There might be regressions (i.e. stuff that used to work doesn't again), and some things that work for some people don't work for others. Such is life and development on AOSP.
At this current point we do not guarantee any functionality (and neither do we for bricking your device, as always).
If you spend half of the night installing the OTA and then it doesn't work like Sony's ROM that will be released at some point in 2015, well, we can't really help you there. They have the magic sauce (i.e. secret source code, blobs) and additional resources.
But you are always welcome to help us. Anytime. We're hiring.
CM source in terms of framework is different. You can use the device trees across all aosp, which is why its easy to port all aosp based roms once CM is ported.Somewhere in the OP it says "calling might only work with headset" but generally audio routing is fixed! Before the OTA, the device didn't even recognize a plugged in headset. Those are two not completely related issue.
As for not duplicating work, no one is really doing that here. We can't really apply CM source code 1:1 to AOSP. I mean, otherwise it would be just AOSP (or CM), right? Not because we have some kind of difference in our political stance or whatever, but because you can't really swap source code like lemonade from one jar to another. There are reasons why CM is CM and AOSP is AOSP. You should know that.
Having said that I will, once I get the time, definitely look at what the CM people have done, and see if we can in some way transfer the changes into our ROM (and add some kind of thanks or, whatever in that direction, of course).
I'm sitting here right now and am testing some patches from commits to Google's AOSP to fix the voice audio.
I'm not sure what I can do more, irrespectibly of the fact that I'm even doing this in my free time that I don't even really have. My girlfriend is waiting for me right now because she wants to go outside with me.
Which I'll probably do.
I had the same issue on the C6603 (Xperia Z) - your kernel is probably missing uid-based routing: The missing support freaks out netd and causes incomplete routing tables.
This should do it:
..and this to avoid kernel-panic-funtimes:
(cherrypicked from the google-msm kernel)
If you need any help with the device bringup feel free to PM me: I got everything working on the C6603 (http://www.blinkenlights.ch/ccms/android/yuga-l.html) and the hardware of the Z2 is almost the same anyway.
OK thanks for the info. I should perhaps add that this is the first time I work with the AOSP source itself at this level (I work as Android app developer at daytime).
The source code will be online when we get around to it, it WILL be online at some point in any case. I managed to get the non-CAF msm8974 audio hal working without any CM code, believe it or not.
And even if we did use CM code, what would be the point in trying to hide that?
I'm not understand how to flash system.img and boot.img. Can u guide me any idea.
I'm just useing command,
fastboot flash system system.img
fastboot flash boot boot.img
but yet not working, looping in logo.
other way i have to use command
fastboot flash system system.img
fastboot flash system boot.img
not working too.
Pls, guide me how can I do.
[QUOTE][B]== Beta v3 (via OTA 1)==[/B] - Mobile Data working (RIL working, routing to modem device fixed) - Calls and Texts working - Sound routing/headphone jack detection working - Wifi stability improvements [/QUOTE] [B]== Beta v2 ==[/B] - Sensors are fixed - first Z1 compact, Z2, Z3 and Z3 compact release - Latest 22.214.171.124 kernel - Mic is working while calling???? - Auto-brightness fixed - Rotation is working [B]== Beta v1.1 ==[/B] - Wifi is a lot more stable - Updated kernel - charging-LED is working now - Rom is more stable and supersmooth [B]== Beta v1.0 ==[/B] - Bluetooth - Wifi - LED - Texting - Calling - Sound - Brightness Slider (autobrightness doesn't work yet, turn it off to make slider working) - Vibration - Screen/Touch