It makes no sense to me why FXP134 cm10 Nozomi image is released. I thought 133 was put on hold due to missing Camera libraries. The lib files are not released yet by Sony, so I assume there still is no working camera in FXP 134
Related
Anyone else tried cm's release candidate for LWW? I don't have the time to flash it yet but http://download.cyanogenmod.com/?device=coconut
And here's the changelog https://github.com/CyanogenMod/android_vendor_cyanogen/blob/gingerbread/CHANGELOG.mkdn
I do not know yet if the dual speakers are fixed (haven't found it on the log) but seeing that it is a release candidate maybe it was fixed.
So now that JB is official from ASUS will the lead to a more stable version of CM10? I'm still sitting on CM9 due to the HDMI audio issues but I'm thinking of going to CM10 if its built off this official ASUS JB version. Any ideas?
CM10 is different from branded firmwares. They can eventually grab the kernel drivers that will be released by Asus as soon as update process is finished, and also all hardware specific sources that are not present in AOSP tree. For the core system, CM10 already uses Jelly Bean sources from Google.
Wait for a bit... once we get the kernel source (Asus has yet to release it), it will soon be merged into CM10 along with the new JB proprietary files and drivers...
craigacgomez said:
Wait for a bit... once we get the kernel source (Asus has yet to release it), it will soon be merged into CM10 along with the new JB proprietary files and drivers...
Click to expand...
Click to collapse
Will you post in the Dev section when this occurs?
hello O1 Developers, I found this thread in the android general forum:
http://forum.xda-developers.com/showthread.php?t=1960117
Ganster41 found a way to modify the stagefright architecture, configuring it to use GB or Froyo OMX libs in ICS... he is working on ICS for ZTE blade... In the comments, zeubea said that it was implemented on a ics build for the HTC legend using Froyo OMX libs. He could play about 30 min youtube videos on HQ with official app without lags but there's still a bug with embedded video plugins on the web. If that is the case, videos with resolutions lower than WVGA could be played without lags, rigth? (it's just a theory)
my question is: is there a way to use this patch/hack on your ICS/JB builds?
PD: i'm not a developer, i ask this question with great respect to you guys :good:
PD2: Sorry for my bad english :silly:
Its already being implemented. Check out the ifs these here. You'll see that hephappy already got it working. I'm running it now and its smooth!
People already know about that. Nobody has it working on jelly bean, but hephappy has an ice cream sandwich build with working omx available here: http://www17.zippyshare.com/v/54828584/file.html Unless you're a dev, there's no way to just patch a rom with gangster41's hack.
Yes, all of us has started the work on this same patch since the first day of its release by Ganster41 on 28 Oct
Bytecode is working on PA with this patch
Rashed97 & Adfad666 are working on CM10 with this patch
WilliamCharles is working on AOKP with this patch
popdog is working on Oxygen with this patch
&
Hephappy and me are working on CM9 with this patch
Hope this clears out for you.
thanks
thank yoy guys.the only thing that keepsme away from ICS was the video lag (even vga videorecording bug)... installing hephappy's ICS rom right now... hope JB will have this path soon
All are waiting for fully working ICS and JB :thumbup:
Sent from my LG-P500 using xda premium
Originally Posted by CYANOGENMOD
in facebook
CM 10.1 Status Update
So we continue to work through the merger of 4.2 code and our CM enhancements. A branch in our github repos called mr1-staging has been created to facilitate the merger and is the target for core CM items (not features).
mr1-staging is not meant to be compile-able, its only purpose is to be a staging grounds for our core work. Chances are, it is useless for independent builders.
CM 10.0 (4.1.2) code is in jellybean-stable, if you are working on a bug-fix for the last stable release, patches should be submitted against that branch. If/when we do another 4.1.2 release (ie CM 10.0.x), it will originate from code in this branch.
Once staging is done in mr1-staging, we will push all that code to a 'CM10.1' branch, and eventually back to our primary 'jellybean' branch. This process is in place to make sure that we effectively move forward from CM 10.0 code, instead of starting over as was seen with the jump from Gingerbread to ICS. Patches from gerrit will be accepted towards CM 10.1, but for now, please have patience while we work through mr1-staging.
While the 4.2 updates are on a smaller scale, they do present some changes that will need to be considered and will effect our implementation of features. Just to name them briefly: Telephony Split, Multi-User, Quick Settings, and Lock-Screen Widgets. These items will be a strong focus when the initial CM10.1 branch is created.
On the feature front, David van Tonder (dvtonder) decided to make his weekend productive, and has already worked on the code for the majority of our MMS enhancements: Emoji support, sms split, gestures and templates, quick messaging. Notably MMS auto retrieve is not being forward ported as Google fixed that themselves. As stated above, patches will hit gerrit review after this staging process is completed.
As always, a timeline isn't and won't be available. We will continue to provide updates as we have them.
Click to expand...
Click to collapse
Let's wait for further announcements
thanks but no CM10.1 for Neo and Neo V
mido_fedo said:
thanks but no CM10.1 for Neo and Neo V
Click to expand...
Click to collapse
CM 10 is available for Neo/Neov ..but its not the stable release ..they are close to making a stable release .. So I guess we might get 10.1 too
Abhiheart said:
CM 10 is available for Neo/Neov ..but its not the stable release ..they are close to making a stable release .. So I guess we might get 10.1 too
Click to expand...
Click to collapse
Even if we get a stable Cm 10 ,it would be worth it and I think Fxp would do that!
As for Cm 10.1,it's been answered already ,it's not just worth the efforts n hassles!
Sent from my MT11i using xda premium
---------- Post added at 09:42 AM ---------- Previous post was at 09:41 AM ----------
FXP said:
HY All
We said it already several pages back CM10 is last release for 2011 devices
Those devices use an old kernel (2.6.32) and old blobs for camera (ICS)
So even making those work with cm10 (jellybean) was an real pain
To update kernel to 3.0 we will require 6+ months (not worth for an 2 year old SOC) limited in hardware and memory
Even if we take this effort this device will not be able to handle next version of android after 4.2 because it simply lacks RAM
Even for Jellybean we had to use legacy camera to be able to use camera in an proper way (with broken panorama)
What's the benefit of having latest android if your device is not able to use new features?
We will continue fixing cm10 and releasing weekly updates with latest JB progress
Jerpelea
FreeXperiaTeam
Click to expand...
Click to collapse
Sent from my MT11i using xda premium
i have one question,what would happen if i replace camera libs on stock ics with the ones from gingerbread?
no i don't think it's that easy if you replace the libs camera won't work it'll just crash and i think these libs from gingerbread will be difficult to port due to different sources