Database Users

Sailfish on N900

I would love to have it ported on N900. I might even try port it to N900 as soon as I can get hold of some sort of image... Anybody else still interested in giving their N900 new life?

U are joking? Sailfish will never work on n900,so do not even dream about it.
Wysyłane z mojego GT-I9100 za pomocą Tapatalk 2

daxanh said:
U are joking? Sailfish will never work on n900,so do not even dream about it.
Wysyłane z mojego GT-I9100 za pomocą Tapatalk 2
Click to expand...
Click to collapse
Why not. It can be ported there, since Mer and Nemo already were. But it doesn't mean that it'll work there smoothly, since N900 has quite a limited RAM. See https://identi.ca/conversation/97151426#notice-98031241

shmerl said:
Why not. It can be ported there, since Mer and Nemo already were. But it doesn't mean that it'll work there smoothly, since N900 has quite a limited RAM. See https://identi.ca/conversation/97151426#notice-98031241
Click to expand...
Click to collapse
Yes it is possible. Mer is already running on it so you just need the Sailfish UI. But it won't run smooth. It will be nearly unusable. So why should you really invest time to port it?

It would've been cool if it would run. I;ve tried running android on my n900 back in the day, but that was never smooth. I don't except jolla will either

N900 nitdroid-jolla
S4RSZ said:
It would've been cool if it would run. I;ve tried running android on my n900 back in the day, but that was never smooth. I don't except jolla will either
Click to expand...
Click to collapse
The N900 was a device i will never ever forget. My first step into Linux systems. for the record, I was able to install and fully use Nitdroid except for receiving and making calls. Back then also, developers on various android forums were promising a complete version. it even built an auto installer for android GB installation. unfortunately due to nokia/android restrictions, it did not reach final stages..
I did not check how jolla looks,.but i am sure it can be done. not a perfect working UI but perhaps like nitdroid.

maxed4901 said:
The N900 was a device i will never ever forget. My first step into Linux systems. for the record, I was able to install and fully use Nitdroid except for receiving and making calls. Back then also, developers on various android forums were promising a complete version. it even built an auto installer for android GB installation. unfortunately due to nokia/android restrictions, it did not reach final stages..
I did not check how jolla looks,.but i am sure it can be done. not a perfect working UI but perhaps like nitdroid.
Click to expand...
Click to collapse
good really good my girlfriend will be very happy :laugh::laugh:so can any one just give it a chance?:angel:
and sorry about my bad English.

.
ishan said:
I would love to have it ported on N900. I might even try port it to N900 as soon as I can get hold of some sort of image... Anybody else still interested in giving their N900 new life?
Click to expand...
Click to collapse
and you still asking?
Iam sleeping and seeing my reborned n900 on new OS
dont listen them, you doing right thing :good:

Even if you could get the drivers working (quite doubtful) and put one of the newer Android Kernels on it, performance would be disastrous. The Jolla (on hardware ~4x as powerful) is anything but a fast, smooth phone with Sailfish on board. The N900 would barely function, IMO.
Total waste of time.

Sorry for my ignorance,
So apps for Mer and sailfish are almost compatible?
Are they using QT libraries?
shmerl said:
Why not. It can be ported there, since Mer and Nemo already were. But it doesn't mean that it'll work there smoothly, since N900 has quite a limited RAM. See https://identi.ca/conversation/97151426#notice-98031241
Click to expand...
Click to collapse

Nokia
Hi Falks,
I was owning a n900, and now ordered a new one. I have looked back in Maemo , nothing really changed til left, just got some pain recently with closed doors on huawei and apple. And really want a physical keyboard and total freedom , and out of the box coming with terminal....
Do we have any alternative these days the last Linux phone which had keyboard was n900 (n950 prototypes also but discontinued). I can't beleive there were no devices made for geeks. And yeas more I use touch screen in last days more I miss the keyboard. So any devices newer ARM anfra more ram and physical keyboard??? Do we have like this, and device should come with only flasher bios/bootloader included , not with any chain, I am wondering if maemo as OS would continue that would be nice, but there are rly small people working things there, more or less DYI everything. I assume development for mobile devices are now much more easier SDK + IDE is basic. With proper OS libraries almost everything easy to port, except gui, but there we need strong libraries and guidences how to use them, or ultimately has a fallback library to the original source system UI with virtualization... There wasn't really easy to dev for eg maemo as ansi C was the main, then ok Pyton, and maybe they got a good C++ compiler, but all of above relies on SDK and OS libreries/refrences....
So any n900 like mobile these days, and I am asking for real items not for failed kickstarter stuff

[Q] Is it as simple as compiling cyanogenmod?

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.)

Sailfish on OnePlus One

If someone wants to port the system he can get an invite from me. :good:

from me too
thesimon said:
If someone wants to port the system he can get an invite from me. :good:
Click to expand...
Click to collapse
hey i will also send an invite to someone who ports sailfish os. i reaaaaaallly want it but i am not a developer or pc geek or something.
if jolaa would release offical roms i would even pay 10-20€

T-uzun said:
hey i will also send an invite to someone who ports sailfish os. i reaaaaaallly want it but i am not a developer or pc geek or something.
if jolaa would release offical roms i would even pay 10-20€
Click to expand...
Click to collapse
ugh i dont have any invites but i want to see it happen for sure!!!
i really want multirom and bcmon also on the oneplus one what else needs to get ported to the oneplus?

Sailfish/MultiROM for the OnePlus One
I'm familiar enough with the process of porting/building SailfishOS that I could probably get it running on the OnePlus One in less than a weekend. The hardware looks similar enough to the Nexus 5 - at least as far as the Qualcomm parts are concerned - that it should be a fairly simple port.
I've been trying to save up for a new phone for a while, but I haven't found one that I like enough to buy at unlocked-phone prices.
Call me cheap, but I felt like I overpaid for my Nexus 4 - which I probably did, because I traded a tablet for it.
I don't tend to develop low-level stuff like this for phones I don't own or at least plan to buy, but I have a long history of "porting" Linux distributions (mainly Debian and non-Unity, "desktop" Ubuntu) to Android phones by modifying the kernel to load the root filesystem from a microSD card, among other things.
Before you get too excited, remember that I may or may not be able to get everything working immediately - just look at how long camera support has been missing from Sailfish on the Nexus 4. On that note, the Sailfish camera HAL is in flux right now, but once it stabilizes, getting the cameras working should be easier.
By the time I get an invite and get around to buying a One, there's bound to be other people working on it, especially if this is as important as I think it is.
TL;DR: In a few weeks I should have money, in another few weeks I should have a device, and shortly after that there should be code.
I'm pretty confident that it should be relatively easy to get the port started, but don't expect miracle-speed progress towards getting all the hardware working.

thesimon said:
If someone wants to port the system he can get an invite from me. :good:
Click to expand...
Click to collapse
Hey,
Now we have released N5 I'm moving onto OnePlus, its booting into the Mer bootloader and switching root into SailfishOs rootfs at the moment but no UI yet due to gralloc issues.
Stay tuned.
BR
Martin

vgrade said:
Hey,
Now we have released N5 I'm moving onto OnePlus, its booting into the Mer bootloader and switching root into SailfishOs rootfs at the moment but no UI yet due to gralloc issues.
Stay tuned.
BR
Martin
Click to expand...
Click to collapse
LOL, where on earth did you get hold of all these devices!?

gTan64 said:
I'm familiar enough with the process of porting/building SailfishOS that I could probably get it running on the OnePlus One in less than a weekend. The hardware looks similar enough to the Nexus 5 - at least as far as the Qualcomm parts are concerned - that it should be a fairly simple port.
I've been trying to save up for a new phone for a while, but I haven't found one that I like enough to buy at unlocked-phone prices.
Call me cheap, but I felt like I overpaid for my Nexus 4 - which I probably did, because I traded a tablet for it.
I don't tend to develop low-level stuff like this for phones I don't own or at least plan to buy, but I have a long history of "porting" Linux distributions (mainly Debian and non-Unity, "desktop" Ubuntu) to Android phones by modifying the kernel to load the root filesystem from a microSD card, among other things.
Before you get too excited, remember that I may or may not be able to get everything working immediately - just look at how long camera support has been missing from Sailfish on the Nexus 4. On that note, the Sailfish camera HAL is in flux right now, but once it stabilizes, getting the cameras working should be easier.
By the time I get an invite and get around to buying a One, there's bound to be other people working on it, especially if this is as important as I think it is.
TL;DR: In a few weeks I should have money, in another few weeks I should have a device, and shortly after that there should be code.
I'm pretty confident that it should be relatively easy to get the port started, but don't expect miracle-speed progress towards getting all the hardware working.
Click to expand...
Click to collapse
hey man I have faith in you and i really want to encourage you to go out there and give it your best shot!
---------- Post added at 12:24 AM ---------- Previous post was at 12:16 AM ----------
rndmboyz3 said:
hey man I have faith in you and i really want to encourage you to go out there and give it your best shot!
Click to expand...
Click to collapse
will the mer bootloader have any conflicts with multirom? also now that I think about it multirom doesnt seem to have support for sailfish... multirom only mentions ubuntu touch and firefox os. I really hope sailfish os can be multibooted! but regardless sailfish os is a sexy beast and I want it even if it is the only rom I can run

rndmboyz3 said:
hey man I have faith in you and i really want to encourage you to go out there and give it your best shot!
---------- Post added at 12:24 AM ---------- Previous post was at 12:16 AM ----------
will the mer bootloader have any conflicts with multirom? also now that I think about it multirom doesnt seem to have support for sailfish... multirom only mentions ubuntu touch and firefox os. I really hope sailfish os can be multibooted! but regardless sailfish os is a sexy beast and I want it even if it is the only rom I can run
Click to expand...
Click to collapse
Multi Rom Supported for Nexus 5
https://wiki.merproject.org/wiki/Adaptations/libhybris/Install_SailfishOS_for_hammerhead

aironeous said:
Multi Rom Supported for Nexus 5
https://wiki.merproject.org/wiki/Adaptations/libhybris/Install_SailfishOS_for_hammerhead
Click to expand...
Click to collapse
perfect and porting from nexus 5 shouldnt be too bad as OPO has simillar specs but better

rndmboyz3 said:
perfect and porting from nexus 5 shouldnt be too bad as OPO has simillar specs but better
Click to expand...
Click to collapse
Here is the list of the devices being ported and what is and is not working right now
https://wiki.merproject.org/wiki/Adaptations/libhybris
Here is the list of who is porting it to what device
https://wiki.merproject.org/wiki/Adaptations/libhybris/porters
Here is the log for #sailfishos-porters at webchat.freenode.net so you can read them working out the details for each device
http://www.merproject.org/logs/#sailfishos-porters/#sailfishos-porters.2014-08-18.log.html

aironeous said:
Here is the list of the devices being ported and what is and is not working right now
https://wiki.merproject.org/wiki/Adaptations/libhybris
Here is the list of who is porting it to what device
https://wiki.merproject.org/wiki/Adaptations/libhybris/porters
Here is the log for #sailfishos-porters at webchat.freenode.net so you can read them working out the details for each device
http://www.merproject.org/logs/#sailfishos-porters/#sailfishos-porters.2014-08-18.log.html
Click to expand...
Click to collapse
thanks for the resources!!! vgrade is a god

rndmboyz3 said:
thanks for the resources!!! vgrade is a god
Click to expand...
Click to collapse
sorry rndmboyz3 just flesh and blood and part of a great team
Pop into #sailfishos-porters and say hello
vgrade

Any news on the sailfish port?
Would really like to try it.

I need an invite from someone to get in ..

carepack said:
I need an invite from someone to get in ..
Click to expand...
Click to collapse
They will be removing the invite system from October, unless they delay it.

well i have an OPO now and my friend has a Jolla,
how we both wish we have the other's os ported to our device just for cool geeks thing.
anyways awaiting for some magic on this one.
imagine what a 2.5 pro and 3gb lpddr3 could do to the performance of sailfish, just would be awesome
drooolllllll...
regards

strategist99 said:
well i have an OPO now and my friend has a Jolla,
how we both wish we have the other's os ported to our device just for cool geeks thing.
anyways awaiting for some magic on this one.
imagine what a 2.5 pro and 3gb lpddr3 could do to the performance of sailfish, just would be awesome
drooolllllll...
regards
Click to expand...
Click to collapse
I hope I can try and port, but I am just a tech savvy noob.

aaron007 said:
I hope I can try and port, but I am just a tech savvy noob.
Click to expand...
Click to collapse
multirom supports sailfish do i need just a image for oneplus one now! someone has one??

T-uzun said:
multirom supports sailfish do i need just a image for oneplus one now! someone has one??
Click to expand...
Click to collapse
MULTIROM for the Oneplus is a port, the Sailfish support is a reflection of this. You'll need a working image of Sailfish .. AFAIK no-one has made one yet for the Oneplus.

Anyone know if this is being developed?
I would love to see sailfish on the oneplus one. Does anyone know if this is being currently worked on or if there a compatible version out there on the net?

Welcome to the Exodus

Hello Guys,
welcome to the world of Team-Exodus.
What is Team-Exodus ?
We are a small group of entusiasts that like to learn more about Android and the Android-ROM developement.
We aren't exactly beginners But there is still room to learn more (you never end learning).
What is Exodus-Rom ?
Maybe, we better should start, what Exodus-Rom isn't: It isn't a (semi)professional mainstream ROM like CyanogenMod,AOKP or similar Roms. We don't focus on buzzword features, nor are we into "bling bling" options. We don't need a "change clock color" option, just because we can do it. These are "low hanging fruits", something nearly everybody can do, who has a computer to compile Android.
So what is Exodus-Rom, what is our focus on ?
We mainly focus on learning how things can be done. We are more into "quality over quantity". We prefer to have 4 or 5 real good and stable working features and not 20-30 features that work... somehow... sometimes...
We want performance, a fast, smooth fluid UI, a real good user experience, not a overbloated kang rom.
For instant that's the main reason why we currently don't have a Marshmallow Rom online, but I will give you a little more information regarding Exodus-6.0 (marshmallow) later.
But before that, who are we, who is "Team-Exodus" ?
The core team of "Team-Exodus" consists of the following guys:
@PrimeDirective - Dave, a very talented developer from the US, founder and Team Leader of Team-Exodus, specialist in App developement (for instant our Exodus Updater or the Drop Wallpaper App) and also our specialist for in deep functionalities of the Android Rom (like a complete rewritten Navbar customization). He currently uses bacon (Oneplus One) and Flounder (Nexus 9) for developenemt
 @Raja.M - Raja, a real nice guy from India, he is our java specialist, he started Android developement something link 6 month ago but his knowledge is fast growing. He developes on the bacon (Oneplus One)
 @TheCrazyLex - Alex, a kernel specialist from germany, he joined Team-Exodus like 3 month ago, mainly responsible to optimize and unify our kernels where possible. He also uses the Bacon (Oneplus One) as developement device.
 @usmcamgrimm - Adrian, our graphics and theme specialist. Beside his amazing wallpapers, he is also responsible for all our LGE G3 devices. He mainly developes on the VS985.
 @Martin_Ro - myself, Martin, also from germany, mostly responsible for the server with the build system, gerrit and download page. I'm also developing here and there if I find some time as I'm a married guy with to young boys. I'm developing on shamu (Nexus 6).
But beside this core team, there are a lot more ppl that help us making the Exodus Rom as amazing as possible, I will add some more of them step by step
So, now, back to Marshmallow and why it takes so much more time to bring an Exodus-6.0 to you guys:
For this to understand, you need to know more about where we come from.
On late 2014 we (Dave and Me) parted from VanirAOSP (that wasn't really AOSP but also used CM as base at that time btw) because we feeled like it started to get more and more into that mainstream "feature count is everything".
With 5.1 we started to directly use CyanogenMod (cm-12.1) as base, but was somewhat annoyed by upcomming issues because they used their open source branch as testfield for unfinished stuff, so for 6.0 we decided to go as near as possible back to strict AOSP.
But a matter of fact is: With strict AOSP you aren't able to support every device, and not as many devices as we want to support. So we have had to make some decisions and try some stuff. In the end we started developing Exodus-6.0 with a Mixture of strict AOSP and CAF as base, with the really amazing wide support of CyanogenMod regarding devices.
But with this, we got back to one of our main concerns: CyanogenMod is doing a fantastic job regarding device support (nobody can beat them in that department) but they are cluttering their stuff more and more. In the past few month, they started to create their own SDK, their own framework. And their SDK started to grow like a octupus, sticking his arms into every aspect of android. But we don't want to use their sdk, so we needed to remove it from everywhere.
And that was, what took so long. We wanted the device-tree and their hardware layer, but not their feature, and for sure not their SDK. And removing that stuff from everywhere inside the device-trees and Hardware layer.
Also we needed to use some of their code stuff in various places to make the connection between our AOSP/CAF based ROM and their hardware/device stuff.
So that took us nearly a month to finish up, but now we have first working experimental builds for bacon, shamu and VS985 so we can go into the real developing stuff.
There is still a lot to do (bring back all the features we want to, make the rom that fluid that you might be used to from EXODUS-5.1 etc.) But the real hard part is done now and we are way neared to a first public beta. Depending on the time Dave can find for Exodus (he is really really busy currently because of a new job), we expect to have a public beta by the end of the month...
So stay tuned and be patient

Made sticky

Hello! I enjoyed the 1/2 of the core team's and the new teams work since JB VanirAOSP to Exodus .
Just wondering, it would be cool to say what you do to seperate you guys from the rest. I know you guys build with jdk8 instead of jdk7 for the lollipop builds and use Linaro with some optimization flags.
I'd like to know if you do more than that and also I am wondering how JDK8 especially helps with optimization.

If you need a tester for bacon. I'm here very big fan of 5.1.

Nice to hear the updates... waiting patiently...

Sounds like the beta will become a christmas present.
Gesendet von meinem Nexus 5 mit Tapatalk

big fan/user of Exodus 5.1 on falcon. out of all the LP ROMs i've tried this has to be one of the most stable and lean ROMs out there. love the amount of essential customization catered here and skipping of cliche features that no one bothers to use (atleast me).
big thanks to @sachoosaini for introducing me to the ROM.

Well here it goes on
@PrimeDirective always a great human and great developer who supported Falcon despite the fact that i can never able to contribute the device to you. I find a best buddy out there who will always be my friend... Now @koshikas thanks Dave for supporting this phone, i never did anything for exodus.. But i am committed for future. If Dave continues the journey for exodus i will be with him in all way... Well what he told me around 6-7 months back is now coming to the real world. Now they support falcon or not. But I am honored by Dave for being there with all the silly questions people ask in community, falcon has great life indeed now its upto the team they develope for it not. I will donating device as soon as I am getting my salary which i am for sure going to get soon..... Wish Luck to exodus....6.0 is on the horizon

If you need a tester...
Hey, if you guys need an experienced tester for bacon, look no further. :good:

AndroidPr0 said:
Hey, if you guys need an experienced tester for bacon, look no further. :good:
Click to expand...
Click to collapse
I'm with this guy

Where do I go to look at the rims ?....dir a HTC m8 Sprint
With S-on

Coolkid90 said:
Where do I go to look at the rims ?....dir a HTC m8 Sprint
With S-on
Click to expand...
Click to collapse
Hm, ok, might be, because english is not my mother language, but for me this sound like "too much drugs and not enough sleep"....

Oh, and by the way:
we just prepared the open source manifest so you can start contribute
I will write a short Facts thread for Exodus-6.0 so you know how to build, and what we changed regarding device-support...

Excelente

Looking real forward to Exodus MM!

sir I am with you here.
AndroidPr0 said:
Hey, if you guys need an experienced tester for bacon, look no further. :good:
Click to expand...
Click to collapse
I m new here and wish to get some knowledge from senior member.

Thanks for this great rom

Exodus seems cool... hyped for MM release!

delete : found it
"err on the side of kindness"

Hi guys
Only to keep you informed: We started publishing official release builds for Exodus-6.0.
Look into your devide Android Developement sections for more information or on our g+ community: https://plus.google.com/communities/106801227383087889476

XZ1 Nougat

Hello dear developers,
I think some of you know, that the XZ3 is in the Android preview program for Nougat. https://developer.sony.com/develop/smartphones-and-tablets/android-n-developer-preview/
As far as I can see in wikipedia the hardware of Z1 and Z3 are very similar. The Z3 is the last of the Z series with very similar hardware.
Because there are so many Xperia devices, the community of developers is very thinned out. There is not even one MarshMallow release which is running without problems until now and Google is already short before releasing Nougat.
Sadlly I am no developer on my own. I already fail at creating the necessary Linux environment. But there are many great developers and skilled people here on the forum. Wouldn't it be a great idea that you bundle your skills, skip the MM release and create the maybe last ROM update for our beloved XZ1? A release of stock based N.
It is just an idea, but it would be great if some of you would capture the idea :fingers-crossed:

wrong forum, xperia z1 won't have a stable MM ROM........................

->--- said:
Hello dear developers,
I think some of you know, that the XZ3 is in the Android preview program for Nougat. https://developer.sony.com/develop/smartphones-and-tablets/android-n-developer-preview/
As far as I can see in wikipedia the hardware of Z1 and Z3 are very similar. The Z3 is the last of the Z series with very similar hardware.
Because there are so many Xperia devices, the community of developers is very thinned out. There is not even one MarshMallow release which is running without problems until now and Google is already short before releasing Nougat.
Sadlly I am no developer on my own. I already fail at creating the necessary Linux environment. But there are many great developers and skilled people here on the forum. Wouldn't it be a great idea that you bundle your skills, jump over the MM release and create the maybe last ROM update for our beloved XZ1? A release of N.
It is just an idea, but it would be great if some of you would capture the idea :fingers-crossed:
Click to expand...
Click to collapse
None of Xperias will have stable custom roms above LP 5.1.1, because everyone has switched to AOSP trees. Sony blobs are protected by DRM, so, they won't work with camera wrappers and Sony's blobs for AOSP have always and will continue to be crap. Sony doesn't want you to have custom roms. So, think of developer friendlier manufacturers. This crap about Sony being friendly to open source is just that. Their open source developers are just PR people. Sony AOSP has never had a stable rom: not for JB, not for Kitkat and not for LP...

optimumpro said:
None of Xperias will have stable custom roms above LP 5.1.1, because everyone has switched to AOSP trees. Sony blobs are protected by DRM, so, they won't work with camera wrappers and Sony's blobs for AOSP have always and will continue to be crap. Sony doesn't want you to have custom roms. So, think of developer friendlier manufacturers. This crap about Sony being friendly to open source is just that. Their open source developers are just PR people. Sony AOSP has never had a stable rom: not for JB, not for Kitkat and not for LP...
Click to expand...
Click to collapse
I've wondered for a long time now: you talk crap about Sony's software, complain about their blobs being 'crap', and claim Sony isn't friendly to OSS, yet you continue to develop and deploy custom ROMs for the Z1. If it's such a hurdle to develop, why not move to a developer friendly platform/device like the Nexus 6P? I appreciate your work for the Z1, but I think you're beating the dead horse at this point.

kentexcitebot said:
I've wondered for a long time now: you talk crap about Sony's software, complain about their blobs being 'crap', and claim Sony isn't friendly to OSS, yet you continue to develop and deploy custom ROMs for the Z1. If it's such a hurdle to develop, why not move to a developer friendly platform/device like the Nexus 6P? I appreciate your work, but I think you're beating the dead horse at this point.
Click to expand...
Click to collapse
LP 5.1 is pretty good. It is better than stock. Today I replaced the rear camera module (the old one stopped focusing) and camera is superb. No bugs in LP.
I may move to Nexus, but the phone I buy has to be metal or glass, plus Z1 has enough life ahead of it. I don't care about M or N. From my point of view, Google changes SDK, so that prior features won't work, and in exchange gives us a few different icons and slightly different interface.
Security updates are coming and lp will be supported for a long while. Normal users don't care about versions either. They want a stable device and they get it in LP...

optimumpro said:
I may move to Nexus, but the phone I buy has to be metal or glass, plus Z1 has enough life ahead of it.
Click to expand...
Click to collapse
The OnePlus 3 is the next best developer-friendly platform after the Nexus devices. Warranty doesn't go bad if you root or unlock bootloader. It even got CM 13 before launch! It also happens to have a metal back, 16MP shooter with OIS, and everybody's favorite 'Dark Mode'. I don't mean to advertise, but for $399, I'd say that's a great bargain. Don't get me wrong, the Z1 still works beautifully when all is OK, but it's really starting to show it's age: your device's rear camera module stopped focusing until you replaced it, several user's battery in the Z1 (not just on XDA) is going bad, and my Z1's touch digitizer has issues on tap (probably from abuse, but people reported self-cracking screens with their touchscreens completely broken). Not too many people want to go through the trouble of sending it in (to China?!) or fixing it themselves.
I don't care about M or N. From my point of view, Google changes SDK, so that prior features won't work, and in exchange gives us a few different icons and slightly different interface.
...
Normal users don't care about versions either.
Click to expand...
Click to collapse
Um, what? According to many tech sources, that's the highlight issue with Android: fragmentation. If you wanted to know Android's biggest problem, this is it. In fact, people (including some casuals) blast Android because of this. Maybe you don't care about Android versions, but if you stick with LP or an older platform, you're contributing to the problem.
Security updates are coming and lp will be supported for a long while. They want a stable device and they get it in LP...
Click to expand...
Click to collapse
As you can probably tell, I've already switched to a different device: a OnePlus 3. Oxygen OS 3.1.3 (6.0.1 Marshmallow), from experience, is quite stable and is developed by the team behind Paranoid Android. Sure, LP's code is more stable because it's been out longer and has more revisions, but it really depends of how you interpret the term (because I've experienced no crashes or FCs so far on MM). I'm fine if you continue holding the torch for Z1's AOSP/CM ROM community and keep LP more secure/stable for them, but I find it a bit redundant as most users have already moved away from this device and transitioned to MM (and even N DP4).

kentexcitebot said:
The OnePlus 3 is the next best developer-friendly platform after the Nexus devices. Warranty doesn't go bad if you root or unlock bootloader. It even got CM 13 before launch! It also happens to have a metal back, 16MP shooter with OIS, and everybody's favorite 'Dark Mode'. I don't mean to advertise, but for $399, I'd say that's a great bargain. Don't get me wrong, the Z1 still works beautifully when all is OK, but it's really starting to show it's age: your device's rear camera module stopped focusing until you replaced it, several user's battery in the Z1 (not just on XDA) is going bad, and my Z1's touch digitizer has issues on tap (probably from abuse, but people reported self-cracking screens with their touchscreens completely broken). Not too many people want to go through the trouble of sending it in (to China?!) or fixing it themselves.
Um, what? According to many tech sources, that's the highlight issue with Android: fragmentation. If you wanted to know Android's biggest problem, this is it. In fact, people (including some casuals) blast Android because of this. Maybe you don't care about Android versions, but if you stick with LP or an older platform, you're contributing to the problem.
As you can probably tell, I've already switched to a different device: a OnePlus 3. Oxygen OS 3.1.3 (6.0.1 Marshmallow), from experience, is quite stable and is developed by the team behind Paranoid Android. Sure, LP's code is more stable because it's been out longer and has more revisions, but it really depends of how you interpret the term (because I've experienced no crashes or FCs so far on MM). I'm fine if you continue holding the torch for Z1's AOSP/CM ROM community and keep LP more secure/stable for them, but I find it a bit redundant as most users have already moved away from this device and transitioned to MM (and even N DP4).
Click to expand...
Click to collapse
Fragmentation has nothing to do with Android versions. Neither Android version has done anything to reduce fragmentation as compared to the previous one. It is the fact that there are hundreds of different devices with varieties of hardware. However, different hardware does not create fragmentation. Unlike Apple, Windows and Linux work on many devices. The problem for Android is that manufacturers don't want to provide hardware addresses (to make open source drivers) or blobs to work with hardware. The question is: why manufacturers provide the necessary info for Windows and Linux, but refuse the same with Android and mobile devices. And I am yet to hear an answer to this...

optimumpro said:
None of Xperias will have stable custom roms above LP 5.1.1, because everyone has switched to AOSP trees. Sony blobs are protected by DRM, so, they won't work with camera wrappers and Sony's blobs for AOSP have always and will continue to be crap. Sony doesn't want you to have custom roms. So, think of developer friendlier manufacturers. This crap about Sony being friendly to open source is just that. Their open source developers are just PR people. Sony AOSP has never had a stable rom: not for JB, not for Kitkat and not for LP...
Click to expand...
Click to collapse
Actually, they have been doing a lot of work and are very friendly about AOSP. MM already has a working camera if you use 1.2.2 kernel. The only issue there is zoom focus and application restarts when switching between front and back camera, but apart from that everything works well. Sony is being very developer friendly and you can't take that away from them.

olokos said:
Actually, they have been doing a lot of work and are very friendly about AOSP. MM already has a working camera if you use 1.2.2 kernel. The only issue there is zoom focus and application restarts when switching between front and back camera, but apart from that everything works well. Sony is being very developer friendly and you can't take that away from them.
Click to expand...
Click to collapse
Would you have any test build that could be tried out? I'd love to test it out...

olokos said:
Actually, they have been doing a lot of work and are very friendly about AOSP. MM already has a working camera if you use 1.2.2 kernel. The only issue there is zoom focus and application restarts when switching between front and back camera, but apart from that everything works well. Sony is being very developer friendly and you can't take that away from them.
Click to expand...
Click to collapse
Doing "a lot of work" and having stable releases, which they have never had on any android version, are 2 different things. Aren't they? Camera aside, how about random reboots, blank screen issues, failure to wake up, battery drain, slow charging, overheating: what more do you need? And by the way, you think camera focus is the only issue? I bet a lot of users would disagree.
We are almost in August. Last year this time LP 5.1.1 was pretty stable. No chance for MM and N is already here...
Edit: My opinions about MM and Sony shouldn't be taken as criticism of Sony open source developers (who work their butts off) or any other devs (myself included) who contribute to the code, but rather Sony Corporation itself. Sony doesn't want you to have custom roms.
If I am to blame community developers, then it would be for abandoning stable releases like LP 5.1.1 in favor of undercooked new ones like MM. That's double stupidity, because in addition to starting from ZERO, they are following (instead of leading) teenage users who would rather have a slightly changed "cool" user interface, as opposed to a rock solid stable release...

optimumpro said:
Doing "a lot of work" and having stable releases, which they have never had on any android version, are 2 different things. Aren't they? Camera aside, how about random reboots, blank screen issues, failure to wake up, battery drain, slow charging, overheating: what more do you need? And by the way, you think camera focus is the only issue? I bet a lot of users would disagree.
We are almost in August. Last year this time LP 5.1.1 was pretty stable. No chance for MM and N is already here...
Edit: My opinions about MM and Sony shouldn't be taken as criticism of Sony open source developers (who work their butts off) or any other devs (myself included) who contribute to the code, but rather Sony Corporation itself. Sony doesn't want you to have custom roms.
If I am to blame community developers, then it would be for abandoning stable releases like LP 5.1.1 in favor of undercooked new ones like MM. That's double stupidity, because in addition to starting from ZERO, they are following (instead of leading) teenage users who would rather have a slightly changed "cool" user interface, as opposed to a rock solid stable release...
Click to expand...
Click to collapse
but, like you said, lollipop are stable, why still develop for it?

brickhayabusa said:
but, like you said, lollipop are stable, why still develop for it?
Click to expand...
Click to collapse
Because stable and maintained are different things. Stable becomes outdated if not further developed. For example, all abandoned LPs are now outdated and shouldn't be used...

optimumpro said:
Because stable and maintained are different things. Stable becomes outdated if not further developed. For example, all abandoned LPs are now outdated and shouldn't be used...
Click to expand...
Click to collapse
Then why xperia M is really awesome, they have a official cm13 nightly still updte every day, n now they're will building for awaken the Nougat, already tested n booted with Alpha release now,
it all by they devs is superior or factor xperia M devices are supported?
Will realy glad if Honami can like them..

Snp Mania2 said:
Then why xperia M is really awesome, they have a official cm13 nightly still updte every day, n now they're will building for awaken the Nougat, already tested n booted with Alpha release now,
it all by they devs is superior or factor xperia M devices are supported?
Will realy glad if Honami can like them..
Click to expand...
Click to collapse
Because they are probably using 3.4 kernel together with older camera blobs. In case of honami, they have decided to move to 3.10 kernel and the newer good blobs are drm protected. And they are waiting for Sony aosp to improve 3.10 blobs, which should happen in the next 50-100 years. Because of this, CM is not working on honami. That's why there is not even one nightly MM for Z1. And since other "big" guys can only cut and paste from CM, there is nothing for Z1.

optimumpro said:
Because they are probably using 3.4 kernel together with older camera blobs. In case of honami, they have decided to move to 3.10 kernel and the newer good blobs are drm protected. And they are waiting for Sony aosp to improve 3.10 blobs, which should happen in the next 50-100 years. Because of this, CM is not working on honami. That's why there is not even one nightly MM for Z1. And since other "big" guys can only cut and paste from CM, there is nothing for Z1.
Click to expand...
Click to collapse
Sorry for this one sir,
This screenshoot i take from xda fecebook via someone of member z1 indonesia FB group, but i dont OP like u so i not understanding it, pls help for read that post at this link...
http://developer.sonymobile.com/build-aosp-nougat-7-0/
EDIT: looks like z1 never to be the Nougat :crying:
from here: http://www.xda-developers.com/sony-...g-aosp-7-0-nougat-for-its-xperia-smartphones/

looki looki!!!!
http://uploaded.net/f/ikvebh

santeria27 said:
looki looki!!!!
http://uploaded.net/f/ikvebh
Click to expand...
Click to collapse
U have try that rom?

No tested!!!
Sent from my Xperia Z1 using XDA-Developers mobile app

santeria27 said:
No tested!!!
Click to expand...
Click to collapse
Haha . Even i cant download that .

Spent 2 hours for downloading this.
Mirror: https://drive.google.com/open?id=0B5NqkvihftQXSDI5Vl9Na2h6ak0