http://developer.sonymobile.com/2012/11/08/sony-takes-lead-on-aosp-on-xperia-s-project-video/
Haha. I love the Android version lol.
Sent from my iPad using Tapatalk HD
pepporony said:
Haha. I love the Android version lol.
Sent from my iPad using Tapatalk HD
Click to expand...
Click to collapse
Only SONY have that android version...
Lolz 4.1.2.3.4....
Sent from my LT26i using xda premium
I want unlockable bootloader now!
Sent from the outer space, delivered by an android
Nice, just in time I announced I was going to upgrade my rom to Jellybean and then this pops up
Sent from my LT26i using xda app-developers app
Release AOSP means all drivers and proprietary binaries will be open source?
If that so we could try modifying camera drivers to get less compression on photos. It's funny how 12MPx camera makes 1.5-2.5MB photos, just like my old 5MPx nonOS phone :]
Thread moved to Xperia S General section.
I would request the section mods to close it if it's a duplicate. Thanks.
Nice, does anyone reckons this will get a release for everyone with an unlocked bootloader to use? This would stop me buying a Nexus 4.
MrBelter said:
Nice, does anyone reckons this will get a release for everyone with an unlocked bootloader to use? This would stop me buying a Nexus 4.
Click to expand...
Click to collapse
me to
kistigun said:
me to
Click to expand...
Click to collapse
Me tooo
Gesendet von meinem LT26i mit Tapatalk 2
JoHnNy08PL said:
Release AOSP means all drivers and proprietary binaries will be open source?
If that so we could try modifying camera drivers to get less compression on photos. It's funny how 12MPx camera makes 1.5-2.5MB photos, just like my old 5MPx nonOS phone :]
Click to expand...
Click to collapse
Just read the article on Sony's blog. The AOSP project do not longer in the hand of JB Queru. Sony dumped the folder on their gitHub.
They also say that they can't release some proprietary binaries, but they work on it.
Technical status of the project
As for the current status and progress of the AOSP on Xperia™ S project, we actually have a lot of things working now. With the code we’re now making available on GitHub, AOSP now boots up, and we have the SD-card, Wi-Fi® and sensors working. And as you can see in the video above, internally we also have audio and the modem running. However, these functions require proprietary binaries that we cannot publish at the time being.
Going forward, the next steps are to replace some of the previously published binaries with source code, and to get Android 4.2 working on Xperia™ S. This can be used as a development platform, and as a base for the work of opening up source code for more modules. For the latest technical status, check out the project on GitHub.
Click to expand...
Click to collapse
is this available to do something with it, or it's just a preview of it?...
For now the Xperia S is the closest thing to a Nexperia.
Peanutboy said:
is this available to do something with it, or it's just a preview of it?...
Click to expand...
Click to collapse
I think it is available, but you need to compile the rom yourself. It's explained on the git page, but still need some skill if you don't know what you're doing.
Could someone please put up a link to their github?
So what does this mean for us, the end users? Getting Jelly Bean sooner? Easier for FXP to finish their CM10?
revan17 said:
So what does this mean for us, the end users? Getting Jelly Bean sooner? Easier for FXP to finish their CM10?
Click to expand...
Click to collapse
Basically yes, where do you think FXP got camera libs for CM to work? Leaked JB from Sony.
hi.i cant unlock my bootloader!thats (( not allowed))!!!
my phone,not support??? or this rom will come for locked bootloader??
Sent from my LT26i using Tapatalk 2
Not really a good news... Sony is counting on the community to make this evolve... they'll never release the needed binaries for modem, sound,...
This project is already dead
Related
Yes, you read that right. The Xperia S tree will become an experimental playground to investigate possibilities to add more devices to AOSP. This doesn't mean we'll have a fully working build any time soon, but the work is starting on lower levels. This also means Xperia S becomes the first non-Nexus device supported in AOSP.
https://groups.google.com/forum/m/?fromgroups#!msg/android-building/zji_sQGN9Oo/MoaS0xidmRMJ
More info here. Way to go Sony and JBQ and Bin4ry.
Very nice news
Tapatalk 2-vel küldve az én LT26i-ről
Good news, the Xperia S deserves some love for sure.
Just what we needed
Sent from my Xperia S
I wouldn't necessarily say supported, but it will be the first non-nexus to be merged into AOSP - and because of that maybe we might get a fee more devs here.
Sent from my ST25i using Tapatalk 2
KeiranFTW said:
I wouldn't necessarily say supported, but it will be the first non-nexus to be merged into AOSP - and because of that maybe we might get a fee more devs here.
Sent from my ST25i using Tapatalk 2
Click to expand...
Click to collapse
TBH I intentionally made it sound like this, for people who think there is no development.
I like this news
So - Sony have actively been involved in this? That's cool
Sent from my Xperia S using xda app-developers app
Thanks for the great news.
The best news I have heard since...EVER!
KeiranFTW said:
I wouldn't necessarily say supported, but it will be the first non-nexus to be merged into AOSP - and because of that maybe we might get a fee more devs here.
Sent from my ST25i using Tapatalk 2
Click to expand...
Click to collapse
I hope for that
Sent from my Xperia S
Jean-Baptiste Queru is an official google developer?
EDIT: ok, yes:
Jean-Baptiste M. "JBQ" Queru
Technical Lead, Android Open Source Project, Google.
here is the current progress:
https://android.googlesource.com/device/sony/lt26/+/master
What does this mean for users of the XPS that arn't devs or techically minded?
How is this different from what FXP are doing with CM9, or devs doing their own ROMS?
AOSP is the Original android proyect by google. We can have a pure Android device
Ah, I see. So like the Nexus devices then? No skinning/mods at all included?
Sounds good!
This is great news! Looking forward to the development!
Sendt fra min LT26i med Tapatalk2
AOSP = Android Open Source Project.
It's the one by google.
JBQ wanted ot start this as an experiment, so we (FXP Team) thought we want to support this step and are currently building an AOSP tree for XPS which is mergeable Of course we have some experience on this device which helps us to get this straight forward Hopefully it will be good for other interested developers too!
So hopefully we can see Sony in official AOSP soon, this will be the first NON NEXUS device included to AOSP tree
You can read the google groups postings if you are interested in current process.
For now, its just a start nothing finished here.
Regards
Bin4ry said:
AOSP = Android Open Source Project.
It's the one by google.
JBQ wanted ot start this as an experiment, so we (FXP Team) thought we want to support this step and are currently building an AOSP tree for XPS which is mergeable Of course we have some experience on this device which helps us to get this straight forward Hopefully it will be good for other interested developers too!
So hopefully we can see Sony in official AOSP soon, this will be the first NON NEXUS device included to AOSP tree
You can read the google groups postings if you are interested in current process.
For now, its just a start nothing finished here.
Regards
Click to expand...
Click to collapse
Too bad I can't help. Good luck to you all
Isn't the Motorolla Xoom a pure google device which isn't Nexus?
When can i GEDify my XS? :cyclops:
www.youtube.com/watch?v=gT5XOWU8u-o
This is awesome. The PA guys released it just recently and it would be awesome on our Defy
Sent from my MB526 using xda premium
swapnil360 said:
www.youtube.com/watch?v=gT5XOWU8u-o
This is awesome. The PA guys released it just recently and it would be awesome on our Defy
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
That's neat. Probably really hard to port since it relies on the closed source PAPreferences.apk and some of the open source PA modifications.
PIE is on PA 2.99 based on JB 10.1. As far as I know, our 10.1 isn't ready for daily use just yet (that might change with all the changes I saw on Quarx's github a while ago ). When it is, I plan on getting back to PA. I'm also willing to help anyone who'd like to try kanging it all together in the mean time.
In the mean time I'm working an ICS rom. Gonna include ICS PA, Salad Bar, and ICS Blur from the Atrix HD. Didn't plan on going full Blur, but some Blur services are required to get Smart Actions fully working (everything works except for location based triggers, requires Blur services framework). Figured if I was gonna have to use some Blue, might as well use it all .
Still have a ways to go, but its progressing.
it does not rely on paprefs. in fact nothing we ever did does. paprefs writes and reads name=value pairs to a textfile, nothing more. you dont need the app for hybrid engine or pie. having said that, pie is still under heavy development. we always build first and release later, we never release unfinished source, much like google does with the aosp.
molesarecoming said:
it does not rely on paprefs. in fact nothing we ever did does. paprefs writes and reads name=value pairs to a textfile, nothing more. you dont need the app for hybrid engine or pie. having said that, pie is still under heavy development. we always build first and release later, we never release unfinished source, much like google does with the aosp.
Click to expand...
Click to collapse
I assumed PAPrefs was a requirement for PIE since I've seen it bundled with framework-res.apk and systemui.apk for other devices to try it out. Since that's not the case, cool beans. Sorry about the misinformation.
/Yep, I assumed. We all know what that makes me
@molesarecoming: I wonder how you find this post to answer. xD I still can't forget the help you and Darkenesys provided when I first started to port the ICS PA for Defy.
About the Pie, its one of the coolest thing happened to Android. You guyz are getting bigger and bigger, even the big OEMs will try to copy you soon so get ready to be more famous.
@Skeevy: good luck mate.
Cmx has Pie too xD
http://www.youtube.com/watch?v=wXCBRmheXc4
squadzone said:
http://www.youtube.com/watch?v=wXCBRmheXc4
Click to expand...
Click to collapse
Is that a Defy in that video?
Sent from my MB526 using xda premium
swapnil360 said:
Is that a Defy in that video?
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
No, it isn't a Defy.
AW: [REQ] Paranoid Android PIE port for Defy
Pls delete
MB525 red lense
It's possible for you see android 4.4 on xperia play?
Inviato dal mio R800i con Tapatalk 2
Arbiterandrea said:
It's possible for you see android 4.4 on xperia play?
Inviato dal mio R800i con Tapatalk 2
Click to expand...
Click to collapse
If we someday get 3.4 kernel working on our phone than maybe. But for now it looks like we will never get anything higher than 4.1.2.
the 3.4 kernel is already done.. so why cant we ??
saqibkhan said:
the 3.4 kernel is already done.. so why cant we ??
Click to expand...
Click to collapse
It's "done" except for the touchscreen, recovery, charging doesn't work, and probably hundreds of other bugs.
Sent from my R800i using xda app-developers app
good
waiting for ur news
Sent from my GT-I9220 using xda app-developers app
korrectmethod said:
It's "done" except for the touchscreen, recovery, charging doesn't work, and probably hundreds of other bugs.
Sent from my R800i using xda app-developers app
Click to expand...
Click to collapse
Up until now there wasn't so much of an incentive though, seeing that at best JB would have been a laggy novelty rom that was too heavy to be a daily driver. It's not so much the case now that 4.4 seems to be optimised especially for devices like ours! Maybe devs will be more eager to sink a few weeks more into it!
I'm trying to get GoogleNow home launcher to run on SuperJellyBean (4.1.2), but it won't work, Velvet.apk keeps crashing. Not sure what its missing, but working fine on my MK808 android stick with 4.2.2.
eksasol said:
I'm trying to get GoogleNow home launcher to run on SuperJellyBean (4.1.2), but it won't work, Velvet.apk keeps crashing. Not sure what its missing, but working fine on my MK808 android stick with 4.2.2.
Click to expand...
Click to collapse
It has mixed results with 4.1.2 roms, it's mainly 4.2.2+
Sent from my R800i using xda app-developers app
awkXda said:
Up until now there wasn't so much of an incentive though, seeing that at best JB would have been a laggy novelty rom that was too heavy to be a daily driver. It's not so much the case now that 4.4 seems to be optimised especially for devices like ours! Maybe devs will be more eager to sink a few weeks more into it!
Click to expand...
Click to collapse
I am no expert or a dev but i think it is highly unlikely that 4.4 grants that much of a performance boost over 4.1+ on the Play
Tlailaxu said:
I am no expert or a dev but i think it is highly unlikely that 4.4 grants that much of a performance boost over 4.1+ on the Play
Click to expand...
Click to collapse
I've done practically nothing except read about KitKat since it was introduced, and I can promise you that performance of this OS will be much higher than any Jelly Bean roms.
The memory footprint required by apps and services has been trimmed by a large amount. Games on the PLAY will no longer run out of ram. There's plenty of documentation on the web right now explaining why this OS would be perfect for devices like the Xperia Play.
Anyway it would be very hard as you would have to make a kernel designed for it which will take some time and you would need to get the touchpads working and edit the build prop
Sent from my LT30p using XDA Premium 4 mobile app
Visa Declined said:
There's plenty of documentation on the web right now explaining why this OS would be perfect for devices like the Xperia Play.
Click to expand...
Click to collapse
That sounds great.Excuse my ignorance but what exactly is stopping people from creating a ROM based on KitKat for the Play?
Tlailaxu said:
That sounds great.Excuse my ignorance but what exactly is stopping people from creating a ROM based on KitKat for the Play?
Click to expand...
Click to collapse
No current kernel is working. Like it won't boot up properly or whatever.
G.I. Jew said:
No current kernel is working. Like it won't boot up properly or whatever.
Click to expand...
Click to collapse
so, its been like 6 months, is there any kernel for the xPlay?
Joanse said:
so, its been like 6 months, is there any kernel for the xPlay?
Click to expand...
Click to collapse
[WIP][Thinktank][DEV]Kernel 3.4.x
The Kernel is in Page 11(Post #105), and the ROM is in Page 10(Post #95),
any of you have a CDMA xperia play?
even the defy i had now have a cm11 build(pretty good even! they have 250+ ram free most stuff works)
and we dont get it on a great device such as out hox?
what is the status of trying and running the 4.4?
is the devices status that bad when it comes to new versions?(the defy dont even have an open bootloader, at all!)
yossi2010 said:
even the defy i had now have a cm11 build(pretty good even! they have 250+ ram free most stuff works)
and we dont get it on a great device such as out hox?
what is the status of trying and running the 4.4?
is the devices status that bad when it comes to new versions?(the defy dont even have an open bootloader, at all!)
Click to expand...
Click to collapse
Well... Its been said a thousand times read through the general threads
Sent from my EndeavorU using Tapatalk 4
What always worried me about HoX development is that the hardware is very similar to the 3G nexus 7 2012 which gets its source code released,
i know there must be different things, different brand ram, the nexus 7 has a slower version of the Tegra 3, not sure if the radio, bluetooth and sensor chips are the same,
and the screen controller is clearly different.
Even the evita now has a cynaogenmod 11 build out
Sent from my HTC One X using xda app-developers app
Tegra . Tegra......
Envoyé de mon HTC One X en utilisant Tapatalk
xeloni said:
Tegra . Tegra......
Envoyé de mon HTC One X en utilisant Tapatalk
Click to expand...
Click to collapse
... Amazing really. A couple posts above someone mentioned the nexus 7 has 4.4. Now suddenly the tegra chipset is the problem again. It is htc not releasing sources for **** sake people. Its no wonder we dont achieve anything as a whole.
We have thomy a great dev but his hands are tied without sources. We would be rockin cm11 for sure by now
Sent from my EndeavorU using Tapatalk 4
2011 Sony Ericsson Xperia Devices Taste Android 4.4 KitKat
Also xperia devices not have code from sony but the developers have only complicated by the codes and are 4.4 ///I'm with 3.8.0 kernel jb !!!
It not just kernel source I think...because it seem LG optimus 4x hd where have same chipset as us already have kit kat. Please let our dev focus on bringing stable 4.3 first.
Sent from my EndeavorU using Tapatalk
audahadi said:
It not just kernel source I think...because it seem LG optimus 4x hd where have same chipset as us already have kit kat. Please let our dev focus on bringing stable 4.3 first.
Sent from my EndeavorU using Tapatalk
Click to expand...
Click to collapse
We don't need 4.3 the changes between 4.2.2.and 4.3 is to small we need the new 4.4 directly
One X seem be dead. Miui discontinued support for porting HOX on official site of Miui
Why not make a petition to get HTC releasing the kernel source code? I've already tell them on twitter to stop violating GPL
Or we will go with the old kernels if we want cm11. This could also happen
Sent from my EndeavorU using Tapatalk 4
Yeah, you're right, but this doesn't make any sense.
HTC have to release the source so the dev can work on it!
Damn you HTC, I'm glad you're failing.
and313 said:
... Amazing really. A couple posts above someone mentioned the nexus 7 has 4.4. Now suddenly the tegra chipset is the problem again. It is htc not releasing sources for **** sake people. Its no wonder we dont achieve anything as a whole.
We have thomy a great dev but his hands are tied without sources. We would be rockin cm11 for sure by now
Sent from my EndeavorU using Tapatalk 4
Click to expand...
Click to collapse
Have you done ROM development on a new android release for a device?
Sent from my Nexus 5 using Tapatalk
Lloir said:
Have you done ROM development on a new android release for a device?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
No. Im just saying what the devs said. Waiting for sources
Sent from my EndeavorU using Tapatalk 4
and313 said:
No. Im just saying what the devs said. Waiting for sources
Sent from my EndeavorU using Tapatalk 4
Click to expand...
Click to collapse
The Motorola defy doesn't even have an open bootloader they use a software trick called 2ndinit to boot into a custom recovery.
I bet they don't have kernel source either yet they have come from 2.1 until 4.4 with a mere gingerbread base.
How comes can't we do the same trick?
yossi2010 said:
The Motorola defy doesn't even have an open bootloader they use a software trick called 2ndinit to boot into a custom recovery.
I bet they don't have kernel source either yet they have come from 2.1 until 4.4 with a mere gingerbread base.
How comes can't we do the same trick?
Click to expand...
Click to collapse
Because as said devs are waiting for sources which means they want to use the new one because they are more updated as the old ones which means more customization. Something in that way. Nothing stays in the way using a old kernel though. But when new sources are released they need to port it again. Something in that way again
So nobody wants to work for free double time... Which is normal i guess
Sent from my EndeavorU using Tapatalk 4
Some time ago I read that HTC got no other choice besides releasing kernel source because of some legal stuff.
Is this true? If it is it's just a matter of time and we will definitely get the new kernel source and 4.4
Also we could use this argument to force HTC to release the source faster.
We have passed the land of arguments very long ago and now we are in the land of get a lawyer and a looot of money or forget about it
Sent from my EndeavorU using Tapatalk 4
Maybe you guys should flood HTC's social media channels with kernel source requests.
It's really rediculous they haven't release 4.2.2 kernel sources yet.
I know OEM's really dislike negative attention via social media so that's probably the best way.
Can devs port the L images of either N5 or N7 and make a ROM out of it or can devs do something with the system dump of the L ?
Porting from a N5 or 7 is next to impossible. It might be possible to build it from source. But kitkat was tricky too. I have faith in the awesome devs here so lets see when they manage to get it booting.
Sent from my Galaxy Nexus using XDA Free mobile app
mrgnex said:
Porting from a N5 or 7 is next to impossible. It might be possible to build it from source. But kitkat was tricky too. I have faith in the awesome devs here so lets see when they manage to get it booting.
Sent from my Galaxy Nexus using XDA Free mobile app
Click to expand...
Click to collapse
We can't build from source as L isn't merged in AOSP yet.
^and it won't be until the "fall"
Some rom for GNeX uses ART?
If is posible port ART to GNeX, Android L is posible in GNeX, the only hard work is on new drivers device.
dpunx said:
Some rom for GNeX uses ART?
If is posible port ART to GNeX, Android L is posible in GNeX, the only hard work is on new drivers device.
Click to expand...
Click to collapse
ART Came with KitKat as a Developer option for testing the new Run Time and allowing app developers to optomize their apps.
As mentioned above Android "L" needs to be merged with AOSP before we can build it from source. Some say that may happen in fall. I think personally Google should merge the preview so Developers can prepare for other devices instead of just Allowing Nexus 5 and Nexus 7(2013) users get to work on it.
Allowing it to be merged early would allow better feedback and preparing App Dev's for the new API's
Android "L" Preview has been released.
https://developer.android.com/preview/setup-sdk.html#top
I'm already downloading to start pulling APK's.
blmvxer said:
Android "L" Preview has been released.
https://developer.android.com/preview/setup-sdk.html#top
I'm already downloading to start pulling APK's.
Click to expand...
Click to collapse
If you can get your hands on that new keyboard that'd be awesome
Castro27 said:
If you can get your hands on that new keyboard that'd be awesome
Click to expand...
Click to collapse
It requires the new API, I already tried it.
blmvxer said:
It requires the new API, I already tried it.
Click to expand...
Click to collapse
Ahhh crap. Thanks though
Edit: Is there anything we can use?
Castro27 said:
Ahhh crap. Thanks though
Edit: Is there anything we can use?
Click to expand...
Click to collapse
I'm not good at decompiling APK's and backporting them. Hopefully some dev's from other devices and with our device will be able to backport some of the newer applications.
http://forum.xda-developers.com/showthread.php?t=2796129
That was fast
Castro27 said:
http://forum.xda-developers.com/showthread.php?t=2796129
That was fast
Click to expand...
Click to collapse
:good:
galaxy nexus survies to android l
it is soo good read care fully before installing
here is the link
http://forum.xda-developers.com/galaxy-nexus/development/rom-fml-fork-life-06-05-2014-v2-t2764064
and think twice before you talk
enjoy android 5.0
Android L
Thanks to @MWisBest ... His work ... really good .. we can run android L really smooth ... just need abit improvement/fix ... http://forum.xda-developers.com/galaxy-nexus/development/rom-fml-fork-life-06-05-2014-v2-t2764064