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
Related
Cyanogen has released for our belived phone wt19i...codename coconut...cm 7.2.0...2.3.7...nightly build...the question is,have anybody ever try it?
Sent from my WT19i using xda premium
CyanogenMod haven't released CM7 on their website yet for Live
yes neroyoung is right CM yet not available for WT19.
Waiting eagerly
Please update this tread when support is available.
On the cyanogenmod forums are 13 nightly builds posted...
How much time does normally pass between a first nightly build and a stable release?
Anyone got any idea how stable this build is?
cm_coconut_full-13.zip
any news on that?
Its out
I have used aka tested it. Its cool fast.
Problem
The dual speaker is not working which can be fixed using a flash file
http://forum.xda-developers.com/showthread.php?t=1600762&page=4 check here for the file
The brightness is too much I think 100% I think it will spoil the display.
No hepatic feedback on soft keys.
Battery back up I have not tried
Anyone can comment on battery..?
Go to Development section, there are 2 topics, CyanogenMod 7.2 and CyanogenMod 9 for 2011 Xperia series, including Live with Walkman.
These are the CM ROMs, that are also on the official webpage. FreeXperia Team is responsible for building these to 2011 Xperia phones. You can find more info in these topics.
Cm9 stable
Yes! I've tried the new rom. It's smooth and fast. NO doubt. But comes with few bugs which can be resolved easily.
1. Wifi doesn't work.
2. Accelerometer lag
3. Stereo Speakers working but no xLoud ( Only for sony live with walkman).
I've fixed all these bugs and create d a backup image. Contact me and i'll send you the link.[/FONT]
This rom is effectively the CM7.2 version of FXP140. I don't believe any changes have been committed to the es209ra sources since FXP130, but it does include the all the latest 7.2 commits made in the 2 months or so since FXP130 was released.
Background:
The USSD exploit was published last week and the Cyanogen dialer is vulnerable. I don't know if there's a USSD factory reset code for the X10 but frankly, I don't want to find out.
The exploit was patched in the CM sources recently and since FXP is no longer releasing 7.2 builds I thought I'd try and build the latest CM version from source for use on my X10 (rather than install some extra app just as a work around)
I was most surprised to get it compiled correctly first time, and I've been running it on my phone today without problems. I figured there are people here who don't have the time or inclination to compile the sources and might find this rom useful.
Installation
It's exactly the same as FXP 7.2 roms, so just follow this.
Colossus FXP install guide
You'll need the standard FXP 130 kernel, or a kernel that's compatible with FXP 130. The Kernel.sin file is included in the rom and you can make an FTF from that with Flashtool if you don't already have a suitable kernel to install.
Download link
http://www.mediafire.com/?6zkni41daaaieq7
Disclaimer: I'm not a developer and haven't made any changes, this is just a clean build of the very latest latest CM7.2 sources from Github: https://github.com/CyanogenMod/
will test.
REPOSTED!
Me test, too.
And I did, idk what kernel should I use, so it's a bit laggy for me. and Play store with Gmail isn't working. but everything else works good.
Sent from my SO-01C using xda app-developers app
will try it
working ok. if i could add the camera from cm7 M&M.. would be better. A lot of free ram, good 3d performance with Cosmic Kernel Mod.
I'm not sure which camera app M&M use, the APK should work as long as it's not the semc one (since M&M is based on stock rom/zmod).
what's USSD ?
USSD codes are special dialling codes that can be used to make a phone perform special functions (e.g. show the IMEI, access the secret menu on a sony stock rom).
See the link I posted originally for more details on the bug:
http://dylanreeve.posterous.com/remote-ussd-attack
It's most serious on Samsung phones as they have a USSD code that performs a factory reset without prompting.
Hi,
i use in my Roms CM-cam.apk
Greets maik
Gesendet von meinem GT-I9100 mit Tapatalk 2
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'm sorry to post this on general forum, because I don't have permission to write on dev forum.
I think is pretty old, because there is new android version 4.2.1, but anyway
as you know, you cannot use ICS libril.so with JB, because of network searching problem.
Well known solution is compiling new libril.so with JB source code.
But if you really want to use ICS ril, because of ril specific function that is implemented on ril by device vendor, you will face big challenge.
So I made mod for JB (4.1.2).
I just compared ril.cpp file with two version (JB and ICS), and add new features from JB ril.cpp to ICS RIL.java.
So, unsupported requests will proceed by RIL.java not libril.so.
this is works for me.
mine is HTC's 4.0.3 ICS libril.so, ril version 6.
I'm not sure this will works for all of your libril.so, I hope this is helpful.
GIthub link is here. (sorry, I dont have link permssion.)
github.com/hounjini/JB_ICS_ril_support
Happy new year!
Hello people and devs un particular ,
For the purpose of fixing the html5 and some other bugs in webbrowser on jb roms ( cm10 also cm10.1 and cm10.2 ) , I figured out that all the problems are from graphic drivers witch was not well compatible with our devices , and its the same reason in addition to the html5 playing issue , that panorama and last google maps app have graphic "glithces" issue also !
Because I'm lacking knowledge and possibilities like a linux or powerfull computer , I request, as in the title, from expert devs in lib files and drivers to make the needed changes in jb ( cm10 or cm10.1 or cm10.2 ) source according to stock drivers from .587 fw source or if possible port them to jb roms and compile a fully compatible graphic drivers files and upload them for users as cwm flashable zip, and then I would like to thank anyone who will help in this problem
CM10 is no longer under development and FXP team who were developing it are now focusing on newer devices. Better check active LegacyXperia Project.
Gesendet von meinem Xperia Neo V mit Tapatalk 2
ReznorNInchNails said:
CM10 is no longer under development and FXP team who were developing it are now focusing on newer devices. Better check active LegacyXperia Project.
Gesendet von meinem Xperia Neo V mit Tapatalk 2
Click to expand...
Click to collapse
I know man , but because it's the most stable jelly bean rom it has just few bugs left thats why I'm asking this right here looking for any dev who can fix the source code problem of the lib file and compile it so then we can get a fully working browser .
Every developer builds a ROM for fun. And when a version of Android is still alive (doesn't reach EOL), developer will work on it and will try to fix issues. For example, some bugs/not working issues like FM radio remains in the CM10.2 build because there are no new releases, so what is done is done.
CM10 was really buggy, even almost everything was working, it wasn't fluid. For example, few days ago I flashed old 4.1.2 PolishBlood AOSP (which is same version as CM10, and I used most recent kernel for it - PAC kernel)
Wifi was dropping every few seconds. On Mike's build no drops at all.
I don't think any developer will contact you because he is not interested in project anymore (neither I am) so try to contact FXP by message and ask your question.
Gesendet von meinem Xperia Neo V mit Tapatalk 2
now the case has changed , its not the libwebcore.so file , but its graphic problem ( openGL ) , can anyone try to fix it , its also present in cm10.1 and cm10.2 roms , but cm11 doesn't have the bug as i had tested it !