Related
http://pocketnow.com/android/sony-xperia-play-neo-and-arch-getting-cyanogenmod-custom-rom
i dont belong to this forum... but i bring some happy news
if its repetitive topic.. delete it pls
so hopefully u all guys will have cyanogen , miui soon
good news indeed!
this and freexperia rom and also miui
choices are now coming for the patient common users, good!
from the bottom of my heart, I wish they agree.
CyanogenMod seems like great stuff for phones without 2.3.3. Wonder what will it have to offer that is better than SE stock ROM or stock+rooted?
For my Motorola Defy it was awesome. Yet what SE offers is quite enticing. Without functioning camera and video recording no ROM is worthy having, but I guess it's harder to program into ROM than anything else.
Well, best wishes nonetheless.
Am I missing something We already have CyanogenMod Custom ROM in Development section. Why does CyanogenMod Team have to make another one
ShyamSasi said:
Am I missing something We already have CyanogenMod Custom ROM in Development section. Why does CyanogenMod Team have to make another one
Click to expand...
Click to collapse
It will be a more complete, and supported release.
I believe the current rom is not official.
Feel free to correct me, I never got into the x10 version. It never seemed quite finished to me.
Sent from my LT15i using XDA App
This is not another one. This is the same work, we've been fixing lots of issues (graphics, automating recovery build, etc) for the past weeks with the goal of getting all of FreeXperia work merged into official cm.
This is great news. I hope it gets approved. Hopefully this convinces Sony Ericsson to give their camera drivers to you, so we can have a fully operational CM7 on our Xperia arc.
Great work. Looking forward to trying it on my Neo. Let's just hope SE comes to the table on Camera drivers.
Cyanogen Mod would sense for devices not getting the latest Android version from the producers. As the current Xperia range was 2.3.3, it's rather pointless to have it instead of a thoroughly tested with proper drivers firmware made by the producers.
Darth Glacious said:
Cyanogen Mod would sense for devices not getting the latest Android version from the producers. As the current Xperia range was 2.3.3, it's rather pointless to have it instead of a thoroughly tested with proper drivers firmware made by the producers.
Click to expand...
Click to collapse
Many people prefer a stock Android over SE's firmware. Stock 3.0.1 was fine, very little background apps, but 4.0 added some new 'bloat'. It's always nice to have the choice, and it's good to get started on Cyanogen early to make sure it'll stay compatible as we move to Ice Cream Sandwich.
Currently our beloved xperia play is running the old gingerbread kernel, and development from FXP is about to come to an end for this device. So I made this thread to give our phone the chance to fully support Jellybean. So please anyone who can help is welcome on board. Here are some helpful links to get us started: http://source.android.com http://www.kernel.org http://forum.xda-developers.com/showthread.php?t=1423009. The last link is an example of what to do to find the UART debugging if needed to build the kernel. May the games begin!
Sent from my Transformer Pad TF300T
https://github.com/kamarush/CAF_android-msm-3.0
it is not booting yet, but most things are done.
see todo list
edit: also zeus board isn't supported yet, need to be fixed too
iiri soft is more active on it now than kamarush, and I plan to port it to Zeus. For now he's doing interim updates like 2.6.32.60 which I have also ported to the Play (but has same issues as he does).
Sent from Xperia Play (R800a) with Tapatalk
Okay guys nice progress I would help if my computer didn't suck
Sent from my Xperia Play using Tapatalk 2
LOL I have a core i3 with 4GB RAM, patiently working on AOSP JB
Sent from Xperia Play (R800a) with Tapatalk
I have an Intel celeron @ 2ghz, 2gbs of ram, and a 250gb hard drive. Lol
Sent from my Xperia Play using Tapatalk 2
Even my laptop is Intel i7 2.5GHz, 8GB RAM, 750GB HDD.
nickholtus said:
https://github.com/kamarush/CAF_android-msm-3.0
it is not booting yet, but most things are done.
see todo list
edit: also zeus board isn't supported yet, need to be fixed too
Click to expand...
Click to collapse
How long has this been worked on
Sent from my Xperia Play using Tapatalk 2
jeffbud98 said:
How long has this been worked on
Sent from my Xperia Play using Tapatalk 2
Click to expand...
Click to collapse
Ha, looks like kamarush has deleted it. He's mad.
As I said before though, irii-soft and ExPeacer have continueed work on it. See https://github.com/irii-soft/CAF_android-msm-3.0/
You can see how long/active it is by looking at the commit log. It's not going to come any time soon, if at all. There is still a LOT of work to do. 2.6.32.60 is only *just* working after a lot of his work, because he is removing/refactoring the strange stuff Sony adds in to make it more generic (i.e. his other kernel work will contribute to knowledge of porting 3.x kernel).
just a question:
are You guys working on a new kernel software for the xperia play to make jb functions working etc. ???
Spatinator said:
just a question:
are You guys working on a new kernel software for the xperia play to make jb functions working etc. ???
Click to expand...
Click to collapse
No. What JB functions aren't working?
CosmicDan said:
No. What JB functions aren't working?
Click to expand...
Click to collapse
Well camera jusf works with a hack, but panorama is broken and touchpad is very buggy.
somethijg that very annoys me is the crash when watching videos.
and what about upcoming android versions...
jb is the last android version, that the fxp team will support on our xperia play, because its really hard work to make jb with our old gb kernels compatible
Spatinator said:
Well camera jusf works with a hack, but panorama is broken and touchpad is very buggy.
somethijg that very annoys me is the crash when watching videos.
and what about upcoming android versions...
jb is the last android version, that the fxp team will support on our xperia play, because its really hard work to make jb with our old gb kernels compatible
Click to expand...
Click to collapse
CM10.0
- latest cm 10.0
- sensors update (all 2011)
- youtube final fix (all 2011)
so youtube will work ok again.
we will get 4.2 (fxp just comfirmed it)
touchpad can be kernel related, but mostly project butter isn't fully working
nickholtus said:
CM10.0
- latest cm 10.0
- sensors update (all 2011)
- youtube final fix (all 2011)
so youtube will work ok again.
we will get 4.2 (fxp just comfirmed it)
touchpad can be kernel related, but mostly project butter isn't fully working
Click to expand...
Click to collapse
-android 4.2 is jb so is said nothing wrong
-youtube: its not just watching videos on youtube i mean watching videos at all
- and i forgot wifi hotspot
o man project butter really doesnt work??
Spatinator said:
-android 4.2 is jb so is said nothing wrong
-youtube: its not just watching videos on youtube i mean watching videos at all
- and i forgot wifi hotspot
o man project butter really doesnt work??
Click to expand...
Click to collapse
Nope I believe the play is too old to allow project butter to run (Afaik) so it's not on any JB ROMS for the play
kamarush said he has got it working.
but because of people complaining at him he stopped developing for sony Phone like me (i also stopped since today)
Ok Nick proved me wrong xD
it's a real shame all you guys are getting such abuse it's not on and I don't blame you for jumping ship but again it's a real shame
actually really sad...
nickholtus said:
kamarush said he has got it working.
but because of people complaining at him he stopped developing for sony Phone like me (i also stopped since today)
Click to expand...
Click to collapse
Good choice this was my first and soon to be last Sony phone. I dont know why sony was OEM of the year their new phones done even come with jellybean and that's been out for 6 months already
Sent from my Transformer Pad TF300T
jeffbud98 said:
Good choice this was my first and soon to be last Sony phone. I dont know why sony was OEM of the year their new phones done even come with jellybean and that's been out for 6 months already
Sent from my Transformer Pad TF300T
Click to expand...
Click to collapse
Because they are much more "open" than other major OEM's. I'd like to see you name one other recent phone from a major OEM that came preinstalled with Jellybean.
And he didn't say he stopped working on Sony because he didn't like them, but because the users are always complaining. And I know what they mean, it's annoying that people are so obsessed with having kernel 3.x and/or full working native jellybean on their phones that are nearly two years old. If they were really that dedicated and wanting of it, they'd learn something and try to help. Or simply give up on the Sony devices and leave us alone.
What are the differences between AOSP and GPe ROMs (that are noticeable). I know that the GPe is based off of the TW framework, but they look very similar otherwise. I'm trying to decide if I want to switch over to the 4.3 AOSP ROM posted a few days ago.
Thanks guys :beer:
Cheater912 said:
What are the differences between AOSP and GPe ROMs (that are noticeable). I know that the GPe is based off of the TW framework, but they look very similar otherwise. I'm trying to decide if I want to switch over to the 4.3 AOSP ROM posted a few days ago.
Thanks guys :beer:
Click to expand...
Click to collapse
I saw this on the Verizon forum for the 4.3 AOSP ROM
@Elvis_Marmaduke -
For those who are still having trouble getting it. GE is made by Samsung and is a Samsung"ROM" if you will. It's like touchwiz without all the bloat and custom menus and features. AOSP is from Google. Not specialized per phone nor do they have the closed Qualcomm drivers so you may not get as high benchmarks and stuff. But most real world performance they will be pretty similar.
Click to expand...
Click to collapse
@Dubbsy -
I thought I said it elsewhere. But anyway GoogleEdition is not AOSP. And AOSP is not GoogleEdition. I was following Brood's progress on a REAL aosp project. When be posted works in progress and his source I decided to play with it.
This is not meant to replace Google Edition 4.3. I'm still working on my Google Edition 4.3 port. It hasn't been friendly at all. B-d from Sprint has been having the same issues I am. Every time I have a "clearly this is the problem" moment... It's not the problem. At least not the main problem.
Comparing GE's 4.2.2 to 4.3 update and the effects to real AOSP it's like comparing cacti and puppies. Besides that, GE's 4.3 is older than this 4.3. JSS builds I've been reading have wake lock issues but while running it I've gotten nothing but amazing battery life
Click to expand...
Click to collapse
@Cruiserdude -
This is NOT Google Play Edition, this is actual AOSP. But yes, 4.2.2 GPe is heavily TW based, while 4.3 GPe is AOSP based with some TW on top. Dubbsy will have to fill you in on the specifics.
My guess is that the decision to offer a "stock" experience S4 happened fairly late in the development process, possibly to silence those rumors of a Google/Samsung rift that were going around a few months ago. Samsung would have already had access to early 4.3 code, so they wouldn't have wanted to build a new 4.2.2 rom from the ground up. So they likely just used an engineering build they had, that had all of the lower level TW stuff but without any of the actual features or themeing built in. Which is presumably what they'd use to develop their TW builds, so they can test features individually with the base they need, but not have so many variables as they track down bugs. Either way, they probably already had something like this laying around, that only needed minor tweaking to become the GPe software. That way they didn't waste effort on software that they'd be replacing after only a month or so, anyway.
That way they could focus right in on developing the 4.3 GPe software so it'd be ready for a prompt release. Which would explain why it's much more heavily based on AOSP, though still with enough TW built in for a few things like the Smart Cover to work. Not to mention it'll likely take them awhile to have a solid 4.3 TW base.
Note that all the above is pure speculation on my part, with the exception of the actual distinctions between versions that I mentioned.
Click to expand...
Click to collapse
I hope that helps!
I'd hold off on the 4.3 aosp until I get all the framework edits done if you need it to be a complete ROM. You'll have data but voice is messed up. telephony isn't setup properly for CDMA handoffs. Didn't notice it until someone pointed it out.
It's one heck of a smooth build though :good: Brood's doing a great job
Would it be as simple as compiling cyanogenmod for a new phone? We have official builds for my phone (lg Optimus g), and various other AOSP based projects. The main reason I am asking is I have compiled cyanogenmod night lies before, and this looks very interesting so I want to try to get it working on my phone.
evodev said:
Would it be as simple as compiling cyanogenmod for a new phone? We have official builds for my phone (lg Optimus g), and various other AOSP based projects. The main reason I am asking is I have compiled cyanogenmod night lies before, and this looks very interesting so I want to try to get it working on my phone.
Click to expand...
Click to collapse
It is
XpLoDWilD said:
It is
Click to expand...
Click to collapse
Just a quick question,will it support mediatek devices?
s.sawrav said:
Just a quick question,will it support mediatek devices?
Click to expand...
Click to collapse
Yes.
We have early support for the r819.
I hope OmniROM is also meant for devices with low specs like for my Xperia U. I am interested to try it as a user.
Mayank7795 said:
I hope OmniROM is also meant for devices with low specs like for my Xperia U. I am interested to try it as a user.
Click to expand...
Click to collapse
If you have a working AOSP, it should be available without problems.
@XpLoDWilD
Would it be worth me attempting to build this for the tf700, or do you guys have plans for it?
Cheers
What about devices that have CM10 only?
lozohcum said:
What about devices that have CM10 only?
Click to expand...
Click to collapse
You need at least an unofficial CM 10.2 / AOSP 4.3.
JoinTheRealms said:
@XpLoDWilD
Would it be worth me attempting to build this for the tf700, or do you guys have plans for it?
Cheers
Click to expand...
Click to collapse
Building is always worth an attempt...
I used to build my own CM, i'm gonna try to build my own omni too but i'm struggling. I must be doing something wrong with the repo init but I can't seem to find what... I'm gonna update my buildbot first because it's been awhile, and maybe try again tomorrow.
As always everyone forget about non-highended devices and lower android versions. Everytime new android version appers, all devs greedily jump on in and start making roms only for it. Nexus 7, Xperia Z/Z1... I vomit. And of course experienced devs are not willing to share their's knowledge about device maintenance
lozohcum said:
As always everyone forget about non-highended devices and lower android versions. Everytime new android version appers, all devs greedily jump on in and start making roms only for it. Nexus 7, Xperia Z/Z1... I vomit. And of course experienced devs are not willing to share their's knowledge about device maintenance
Click to expand...
Click to collapse
That's why its worth scrawling through XDA, going through guides and learning to dev. Nothing wrong with a dev who decides to leave an older version for a newer version. They're doing it for fun and free.
lozohcum said:
As always everyone forget about non-highended devices and lower android versions. Everytime new android version appers, all devs greedily jump on in and start making roms only for it. Nexus 7, Xperia Z/Z1... I vomit. And of course experienced devs are not willing to share their's knowledge about device maintenance
Click to expand...
Click to collapse
I actually have a plan about getting legacy devices involved in the form of a "legacy branch" complete with legacy maintainers. It's tricky to get started off, but might prove useful for anyone wanting to get longer community support for their devices.
pulser_g2 said:
I actually have a plan about getting legacy devices involved in the form of a "legacy branch" complete with legacy maintainers. It's tricky to get started off, but might prove useful for anyone wanting to get longer community support for their devices.
Click to expand...
Click to collapse
As long as there is no hard reason to stop supporting a device and we have someone who is taking care of that device we will try
On the other side - there is constant evolution which sometimes will make it necessary to leave a device "behind" if the effort will become too large
Sent from my Find 5 using xda app-developers app
XpLoDWilD said:
It is
Click to expand...
Click to collapse
Not quite yet... Not until we have roomservice up and running.
(For those that didn't understand what I said - roomservice is the part of CM's repo management system that will automatically sync a device tree and all dependencies. roomservice is HEAVILY dependent on github's APIs, so we couldn't even start work on that particular piece of infrastructure until the project went public.)
lozohcum said:
As always everyone forget about non-highended devices and lower android versions. Everytime new android version appers, all devs greedily jump on in and start making roms only for it. Nexus 7, Xperia Z/Z1... I vomit. And of course experienced devs are not willing to share their's knowledge about device maintenance
Click to expand...
Click to collapse
The reason for the Nexus/Xperia Z support is because the vendors have AOSP source for pretty much the entire device readily available. The Xperia Z series (Z, Z Tab, Z1) have source widely available for (IIRC) pretty much everything bar the radio. Heck - sony had uploaded AOSP 4.3 sources before CM had 10.2 nightlies running, from memory.
Anything beyond that boils down to porting existing patches, or people bringing up other devices. This will generally happen for more widely used devices first simply because there's more likely to be someone available with the skills to do it. By the sounds of Omni is working, you could have pretty much any obscure old phone but if you're happy to do the bringup then it'll get added
M.
mattman83 said:
The reason for the Nexus/Xperia Z support is because the vendors have AOSP source for pretty much the entire device readily available. The Xperia Z series (Z, Z Tab, Z1) have source widely available for (IIRC) pretty much everything bar the radio. Heck - sony had uploaded AOSP 4.3 sources before CM had 10.2 nightlies running, from memory.
Anything beyond that boils down to porting existing patches, or people bringing up other devices. This will generally happen for more widely used devices first simply because there's more likely to be someone available with the skills to do it. By the sounds of Omni is working, you could have pretty much any obscure old phone but if you're happy to do the bringup then it'll get added
M.
Click to expand...
Click to collapse
Someone should write a definitive guide about converting CM10 device tree to AOSP JB device tree, so more people can work on devices maintenance
pulser_g2 said:
I actually have a plan about getting legacy devices involved in the form of a "legacy branch" complete with legacy maintainers. It's tricky to get started off, but might prove useful for anyone wanting to get longer community support for their devices.
Click to expand...
Click to collapse
I hope the Acer IconiaTAB A5000 will get supported.
Please, support for RAZR i (x86)
lozohcum said:
Someone should write a definitive guide about converting CM10 device tree to AOSP JB device tree, so more people can work on devices maintenance
Click to expand...
Click to collapse
Problem is, every device has its own pitfalls. Some are harder to overcome than others.
For example, the lack of NEON in tegra2 combined with the dependency of newer gapps on NEON really screws tegra2 devices, and there isn't much that can be done about it.
Also, in some cases, the things needed to get a device working aren't in the tree, but are in the frameworks to handle OEM-specific oddities (RIL hacking in opt/telephony, which I admit I'm not too familiar with...) or platform support. Sometimes, old devices get left behind simply because their platform overall is a ***** to support beyond a certain point. (See how MSM8660 devices have been lagging lately, due to Qualcomm pretty much sunsetting that chipset.)
Hi to everyone, got my phone yesterday, rooted unlocked and started off.
I come from some experience in the field (my first phone was an xperia)
and my stats show that I put effort and time into this community and am looking forward to start working on some projects.
(i am merely a builder not a developer)
Would anyone be so kind and nice to give me a picture of current development status?
Are there major bugs being worked on from cm incompatibility?
How come there is only one cm based kernel?
What are the most common problems that have been mostly encountered?
Thanks for your replies, happy to be here, take care
Rudjgaard said:
Hi to everyone, got my phone yesterday, rooted unlocked and started off.
I come from some experience in the field (my first phone was an xperia)
and my stats show that I put effort and time into this community and am looking forward to start working on some projects.
(i am merely a builder not a developer)
Click to expand...
Click to collapse
Welcome to this forum and I hope you'll enjoy working with the community here
Would anyone be so kind and nice to give me a picture of current development status?
Are there major bugs being worked on from cm incompatibility?
Click to expand...
Click to collapse
AFAIK, there aren't any CM bug now, there was a camera lag at start up weeks ago, but now it's solved,
the only thing left is that camera quality on AOSP-Based ROM is not as good as it is on stock Sony FW,
The great thing going on now is that we're gonna have official AOSP support from Sony soon (all thanks to @jerpelea)
check these:
Unified kernel for msm8974 devices
Xperia AOSP Project
these are still new and their early stages, and hopefully we'll start using them soon:good:
How come there is only one cm based kernel?
Click to expand...
Click to collapse
To be honest, there aren't many devs how own or work for this device, even the cm-based kernel we have is ported from Z1 !
also I'm working on a brand new one with the latest features, but I think it'll take some time
What are the most common problems that have been mostly encountered?
Thanks for your replies, happy to be here, take care
Click to expand...
Click to collapse
Well as I mentioned, we don't have any major problems, as this device can get whatever Z1 can get, and Z1 is popular
except for one thing! the double tap to wake feature can't be ported from Z1 to our device as the two devices don't share the same touchscreen!
That's all I can remember right now
if you need any help, I'm always available,
and I'm looking forward to seeing your work
Best Regards,
Omar.
Thank you very much for your long and exhaustive answer.
I did see a camera workaround in the cm system.
Has anyone tried porting stock camera to cm? (Is it the actual camera hal responsible for qualiy or Sony proprietary rendering sw on album(are pics better/worse in fact when viewed on PC or from the phone's album? We did that on the lg with great results..
What about device blobs for the kernel are they closed source or do we have support from Sony?
Thanks again for all the info
Cheers