hey now that the bada zone is finally open i just wanted to know if there is any chance to port android to the wave i mean bada runs on linux so there must be a way.
i just want to know it for a friend that hate hes phone now coz of bada haha
i mean i have lgp500 with droid so i am happy if somebody got anynews please do report thx.
If you had some devs, who were ready to work on that project and if they found possibilities to have an breaktrough in to the Bada/Wave system, it would be possible to port Android to the Wave. But it still needs a lot of time and work to have an usable Android port. Some tried it some already resigned.
At the moment there are no big plans or progresses in this way.
By the way many smartphones/tablet OS runs on a Linux kernel. But it doesn't mean that they are similar to each other or that Bada is similar to Android.
Not to mention that the current bada phones don't use Linux for a kernel, but NucleusRTOS (as part of SHP). There is nothing in common with today's Android phones!
The JetDroid project is much closer.
There is already a thread open discussing this matter *HERE* so please post there as 2 threads talking about the exact same thing isnt productive to your goal.
Thread closed.
Mark.
Fellow xda members,
I've been lurking/browsing this section of xda for quite some time now, and I made a post on together.jolla.com with the same title as this...
Anyway, I am a CS student, and I'm curious to try Sailfish, the only thing is, the only android phone I have is a very powerful and potential-filled Xperia Z3C that is not going anywhere on its current OS (Lollipop 5.0.2), and since being a previous user of BB10, I love gesture-based OS'...
With that being said, I have read the Sailfish HADK enough times that I am thinking about trying to port Sailfish to my Z3C once and for all, I just don't know exactly where/how to start. I've also been following the mer wiki, and it appears that someone successfully ported SF to an Xperia Z. I don't know if there are any hardware changes between the Xperia Z and Z3 that would warrant a brand new/different build, or if I could potentially use the image that already exists for the Xperia Z and just debug/test/update with the most current build of SF that was recently launched (I think it's 1.17 or something...) and keep that going until SF officially releases a downloadable image (which, from reading their blogs, and chatting with some people on freenode, doesn't seem like they will anytime soon).
It also appears that CyanogenMod 11 is available for the Z3C (I think?) -- and this is one of the prereqs for unlocking the bootloader etc...
I am looking for guidance/tips, and anyone that is willing to help me along the way, so I can bring this amazing OS to an awesome piece of Sony hardware, that should not be brushed under the carpet. I am new to porting/mobile dev, but I am willing to learn, so any help will be greatly appreciated!
Thanks!
apollus said:
Fellow xda members,
I've been lurking/browsing this section of xda for quite some time now, and I made a post on together.jolla.com with the same title as this...
Anyway, I am a CS student, and I'm curious to try Sailfish, the only thing is, the only android phone I have is a very powerful and potential-filled Xperia Z3C that is not going anywhere on its current OS (Lollipop 5.0.2), and since being a previous user of BB10, I love gesture-based OS'...
With that being said, I have read the Sailfish HADK enough times that I am thinking about trying to port Sailfish to my Z3C once and for all, I just don't know exactly where/how to start. I've also been following the mer wiki, and it appears that someone successfully ported SF to an Xperia Z. I don't know if there are any hardware changes between the Xperia Z and Z3 that would warrant a brand new/different build, or if I could potentially use the image that already exists for the Xperia Z and just debug/test/update with the most current build of SF that was recently launched (I think it's 1.17 or something...) and keep that going until SF officially releases a downloadable image (which, from reading their blogs, and chatting with some people on freenode, doesn't seem like they will anytime soon).
It also appears that CyanogenMod 11 is available for the Z3C (I think?) -- and this is one of the prereqs for unlocking the bootloader etc...
I am looking for guidance/tips, and anyone that is willing to help me along the way, so I can bring this amazing OS to an awesome piece of Sony hardware, that should not be brushed under the carpet. I am new to porting/mobile dev, but I am willing to learn, so any help will be greatly appreciated!
Thanks!
Click to expand...
Click to collapse
Greetings
I was curious about getting Sailfish to Xperia Z3C, but after reading HADK I realized that I do not have the knowledge nor time to actually port Sailfish for the device. Though I'm not a Linux/Android developer, here are just some things I would like to just point out:
HAIK lists in it's PREREQUISITES section that it requires CyanogenMod 10.1.x. Using CyanogenMod 11.x.x might cause some unpredictable issues
Z3C hardware is completely different from Z1 hardware, so you will be forced to create a new build. You might also noticed that Z1 is compatible with libhybris and Z1C is not. There's also a chance that libhybris won't be compatible with Z3C.
You pretty much need to have a great knowledge of Linux, without that knowledge, you will end up looking up your issue on the internet very often
When you run into an issue that you can't solve on your own, just ask for help on the Sailfish Freenode IRC channel, I'm sure that they will help you.
Only thing I could offer you is to host the compiled builds on my server.
Thundery Steak said:
Greetings
I was curious about getting Sailfish to Xperia Z3C, but after reading HADK I realized that I do not have the knowledge nor time to actually port Sailfish for the device. Though I'm not a Linux/Android developer, here are just some things I would like to just point out:
HAIK lists in it's PREREQUISITES section that it requires CyanogenMod 10.1.x. Using CyanogenMod 11.x.x might cause some unpredictable issues
Z3C hardware is completely different from Z1 hardware, so you will be forced to create a new build. You might also noticed that Z1 is compatible with libhybris and Z1C is not. There's also a chance that libhybris won't be compatible with Z3C.
You pretty much need to have a great knowledge of Linux, without that knowledge, you will end up looking up your issue on the internet very often
When you run into an issue that you can't solve on your own, just ask for help on the Sailfish Freenode IRC channel, I'm sure that they will help you.
Only thing I could offer you is to host the compiled builds on my server.
Click to expand...
Click to collapse
Thanks for the tip. The bit about hardware changes is exactly what I was worried about, as I know the newer Z series have the 800 SoC chips and other possible differences, but I did read somewhere that Sony was supposedly making their bootloader universal among Z series (correct me if I am understanding this wrong). -- As for Linux, I have no experience with Linux, and was going to do this all on my OSX machine (I believe it is doable with homebrew and some bash scripting).
I'm staying tuned to see if anyone else chimes in on this. Thanks again!
apollus said:
Thanks for the tip. The bit about hardware changes is exactly what I was worried about, as I know the newer Z series have the 800 SoC chips and other possible differences, but I did read somewhere that Sony was supposedly making their bootloader universal among Z series (correct me if I am understanding this wrong). -- As for Linux, I have no experience with Linux, and was going to do this all on my OSX machine (I believe it is doable with homebrew and some bash scripting).
I'm staying tuned to see if anyone else chimes in on this. Thanks again!
Click to expand...
Click to collapse
I would really try not to do it on OS X. You need a proper Linux distribution to use, seeing as you're going to be following HADK very closely. It's not doable on OS X system and will never be. You require a Linux system to build another Linux system. If you went through HADK multiple times, you would know this.
I see why you think that OSX and Linux are alike, but they're really not, even when they are both UNIX systems. OS X is bastardized UNIX system and doesn't contain the GNU toolchain and the only thing it shares with Linux is the UNIX core.
Thundery Steak said:
I was curious about getting Sailfish to Xperia Z3C, but after reading HADK I realized that I do not have the knowledge nor time to actually port Sailfish for the device. Though I'm not a Linux/Android developer, here are just some things I would like to just point out:
HAIK lists in it's PREREQUISITES section that it requires CyanogenMod 10.1.x. Using CyanogenMod 11.x.x might cause some unpredictable issues
Z3C hardware is completely different from Z1 hardware, so you will be forced to create a new build. You might also noticed that Z1 is compatible with libhybris and Z1C is not. There's also a chance that libhybris won't be compatible with Z3C.
When you run into an issue that you can't solve on your own, just ask for help on the Sailfish Freenode IRC channel, I'm sure that they will help you..
Click to expand...
Click to collapse
Actually CyanogenMod 11.0 is currently the preferred version to be used as a base for Sailfish porting, no new ports should be made with 10.1 unless 11.0 is not available. Missing information in the supported devices table does not really tell whether a device can have support or not, it just means that nobody has done it yet. The difficulty of porting varies a lot from device to device but for quite many of the most common problems solutions already exists and #sailfishos-porters at Freenode will help with all problems encountered during porting.
mal- said:
Actually CyanogenMod 11.0 is currently the preferred version to be used as a base for Sailfish porting, no new ports should be made with 10.1 unless 11.0 is not available. Missing information in the supported devices table does not really tell whether a device can have support or not, it just means that nobody has done it yet. The difficulty of porting varies a lot from device to device but for quite many of the most common problems solutions already exists and #sailfishos-porters at Freenode will help with all problems encountered during porting.
Click to expand...
Click to collapse
mal-, how is your port of sailfish for the xperia pro working out?
mal- said:
Actually CyanogenMod 11.0 is currently the preferred version to be used as a base for Sailfish porting, no new ports should be made with 10.1 unless 11.0 is not available. Missing information in the supported devices table does not really tell whether a device can have support or not, it just means that nobody has done it yet. The difficulty of porting varies a lot from device to device but for quite many of the most common problems solutions already exists and #sailfishos-porters at Freenode will help with all problems encountered during porting.
Click to expand...
Click to collapse
HADK still mentions 10.1.xx so there's that. Though, I don't know if I should wait for SailfishOS 2.0 and gain some Linux knowledge by reading RFS or dive right in into porting when I will have some time.
Thundery Steak said:
HADK still mentions 10.1.xx so there's that. Though, I don't know if I should wait for SailfishOS 2.0 and gain some Linux knowledge by reading RFS or dive right in into porting when I will have some time.
Click to expand...
Click to collapse
HADK does indeed still talk only about 10.1 but the 11.0 based build can done using the same HADK by replacing in chapter 5.1 the hybris-10.1 in repo init command with hybris-11.0. A new version of HADK will be published hopefully quite soon with a lot of restructuring of the content to make it simpler for users. Also there has already been work done on porting Sailfish to Z3C on #sailfishos-porters and just today there was talk about continuing that.
---------- Post added at 12:43 AM ---------- Previous post was at 12:37 AM ----------
apollus said:
mal-, how is your port of sailfish for the xperia pro working out?
Click to expand...
Click to collapse
Just a day ago I published the first image of the port but haven't yet posted about it here because I need to do a few more posts to be able to include links to my posts. The link to the image and installation instructions can be found through the adaptation status table at Mer-project wiki.
mal- said:
HADK does indeed still talk only about 10.1 but the 11.0 based build can done using the same HADK by replacing in chapter 5.1 the hybris-10.1 in repo init command with hybris-11.0. A new version of HADK will be published hopefully quite soon with a lot of restructuring of the content to make it simpler for users. Also there has already been work done on porting Sailfish to Z3C on #sailfishos-porters and just today there was talk about continuing that.
---------- Post added at 12:43 AM ---------- Previous post was at 12:37 AM ----------
Just a day ago I published the first image of the port but haven't yet posted about it here because I need to do a few more posts to be able to include links to my posts. The link to the image and installation instructions can be found through the adaptation status table at Mer-project wiki.
Click to expand...
Click to collapse
Why isn't the Z3C added to the wiki page then? at least the device, so that people (like myself) know...
I'm probably gonna end up putting fedora on this machine and start trying to learn to use linux (to port). Will be taking a UNIX/Linux intro class soon anyway, so that will come handy.
I am really sick and tired of boring old android and I think the effort to get Sailfish is well worth it... Gonna keep checking into freenode to see if people mention the Z3C.
Mal, thanks for your posts.
apollus said:
Why isn't the Z3C added to the wiki page then? at least the device, so that people (like myself) know.
Click to expand...
Click to collapse
It depends on the person doing the porting at how early stage they add the information to the wiki page. Some do it very early some wait until it's reasonably usable. Of course it would be nice to have information about all ongoing porting activity.
Guys, OS development fever for our device doesn't seem to end soon,it seems. As One Plus Team is reportedly working on Ubuntu OS for our device. Check out this link for more. Fingers crossed.
http://www.knowyourhandheld.com/blo...-ubuntu-os-rom-oneplus-x-version-coming-soon/
Sweet. I would still prefer a fully working SailfishOS but still...
They sure have a buils for OPO.
But nothing was said about the OPX, is that a valid source for news?
Calvin2394 said:
They sure have a buils for OPO.
But nothing was said about the OPX, is that a valid source for news?
Click to expand...
Click to collapse
I know. On the OP Forums one of the mods announced that they needed help porting it, and I would help, but there isn't a repository where I can contribute.
I would love to habe the option. After i saw that demo lately i m hyped .
RJDTWO said:
I know. On the OP Forums one of the mods announced that they needed help porting it, and I would help, but there isn't a repository where I can contribute.
Click to expand...
Click to collapse
https://devices.ubports.com/#/
seems to be forwarding the porting efforts though their github doesnt have the repo.
@mariogrip @h2o64
might be able to explain better.
Dark Passenger said:
https://devices.ubports.com/#/
seems to be forwarding the porting efforts though their github doesnt have the repo.
@mariogrip @h2o64
might be able to explain better.
Click to expand...
Click to collapse
I won't contribute to Ubuntu Touch ever anymore for ethical private reasons.
h2o64 said:
I won't contribute to Ubuntu Touch ever anymore for ethical private reasons.
Click to expand...
Click to collapse
"ethical reasons" if you could clarify(non private ones )
Also I quoted you because your associated with the ubports project so could explain the best way to contribute to the same or to ubuntu touch.
Dark Passenger said:
"ethical reasons" if you could clarify(non private ones )
Also I quoted you because your associated with the ubports project so could explain the best way to contribute to the same or to ubuntu touch.
Click to expand...
Click to collapse
Because what began as a open source innovating project become a commercial thing half abandonned that relies on hype (I won't develop).
First thing, Ubuntu Touch is AOSP based. CM and Oxygen (Hydrogen) are CAF based. You can't use one resources on the other (trees,...)
Second thing, Canonical have WIP branches based on lollipop and I highly recommend waiting for those.
I'm out of this thing but I follow everything
h2o64 said:
Because what began as a open source innovating project become a commercial thing half abandonned that relies on hype (I won't develop).
First thing, Ubuntu Touch is AOSP based. CM and Oxygen (Hydrogen) are CAF based. You can't use one resources on the other (trees,...)
Second thing, Canonical have WIP branches based on lollipop and I highly recommend waiting for those.
I'm out of this thing but I follow everything
Click to expand...
Click to collapse
thanks.
h2o64 said:
Because what began as a open source innovating project become a commercial thing half abandonned that relies on hype (I won't develop).
First thing, Ubuntu Touch is AOSP based. CM and Oxygen (Hydrogen) are CAF based. You can't use one resources on the other (trees,...)
Second thing, Canonical have WIP branches based on lollipop and I highly recommend waiting for those.
I'm out of this thing but I follow everything
Click to expand...
Click to collapse
I can agree with you there. I used to use LM a little over a year back because j enjoyed the simplicity of the Ubuntu base, but then Canonical... Changed I guess would be the right way to put it. They started to make a distro that was commercialized and screwed everyone like myself over. I couldn't use a distro that made so many bad choices and gave Linux a bad face so I switched to OpenSUSE. They seem to respect user freedom at the very least.
That said, Ubuntu Touch serves as a base for another project.. Plasma Mobile. And as much as I don't care for Touch, I do like the looks of Plasma so I will try to contribute at the very least.
Hola
I am not a developer, but like those with a little time and technical know how, I can compile my own ROM from sources. This was extremely popular when I had the OnePlus 1 device and CM was still around.
The question is what does it take to create custom ROMs? ...especially given that OnePlus has traditionally been developer friendly with releasing not only kernel but firmware sources rather quickly compared to other OEMs. I understand that the OnePlus 3 / 3T sub-forum on XDA even outrival's the Pixel devices from Google. Maybe my inquiry is best suited in the general Android sub-forum on XDA.
That aside, I am surprised we haven't heard much from some developers who run and maintain well known custom ROMs such as LOS, RR, Mokee, DU, AICP, AOSP, etc. regarding support for this OnePlus 5. Am I missing something or it rather just a matter of time
Lastly, and more importantly, my greatest appreciation to all developers, cooks, maintainers, and others who help keep the community alive and well. Without these folks we would just be regular consumers being forced to use what crappy software we are provided with. Thanks to you :highfive:
I'm googling while compiling this post but I just lack too much knowledge about aosp so I'm asking for some eli5 or just a link to an article where there is a well organized explanation on open source android development closely related to what I want to know here. (I prefer public sharing but PM would work too)
So, @tissot-dev (who is this? Xiaomi engineers?) published open source code for Tissot. (is this only for mi a1, who named it, when and why, what is it made from, is it build on aosp, if so in how many iterations to get to "Tissot").
What did @ghpranav do to become the standard? (What from his background contributed to his knowledge on this topic if known?)
Why can't we get a stable Oreo tree? How do we get to it?
Are unofficial builds contributing in any way and how are those built to be stable enough?
Why are officials running away from mi a1? (Few of them built a stable nougat but stopped, some even ditched doing simple fixes to make it fully functional)
Edit: Where does the Android one project come to play?
I want to learn a lot more and contribute if enough of these concepts get cleared in my head, so it's a bit technical, but I made this post to help myself and hopefully others with a compiled list of errors my brain is generating and if someone is kind enough, eli5 please, or just share a link or two, I need a bit of guidance at least to help my brain generate some good kw args for googling.