According to Mozilla's roadmap Firefox OS 2.0 finished the Code Complete phase on September 1 of this year (2014, if you're not already aware ). "After this phase, the code is released to our Partners and OEMs, who perform modifications on the source code, certification tests, and device-specific optimizations."
Does this mean that Firefox OS 2.0 is now the most up to date stable version available?
(I am very excited to run a stable version of 2.0 on my ZTE Open C)
KUPOinyourWINDOW said:
According to Mozilla's roadmap Firefox OS 2.0 finished the Code Complete phase on September 1 of this year (2014, if you're not already aware ). "After this phase, the code is released to our Partners and OEMs, who perform modifications on the source code, certification tests, and device-specific optimizations."
Does this mean that Firefox OS 2.0 is now the most up to date stable version available?
(I am very excited to run a stable version of 2.0 on my ZTE Open C)
Click to expand...
Click to collapse
I am not sure but you could always ask b2g developers in their IRC channel. They are very friendly and helpful.
darkowlzz said:
I am not sure but you could always ask b2g developers in their IRC channel. They are very friendly and helpful.
Click to expand...
Click to collapse
I wish I was skilled with the Terminal then I could just make my own builds
KUPOinyourWINDOW said:
I wish I was skilled with the Terminal then I could just make my own builds
Click to expand...
Click to collapse
Well, it's not really difficult. ZTE's support site has some recent downloads with manual on how to install the updates. Maybe you would like to read the manual, try it out and improve your terminal skills :good:
darkowlzz said:
Well, it's not really difficult. ZTE's support site has some recent downloads with manual on how to install the updates. Maybe you would like to read the manual, try it out and improve your terminal skills :good:
Click to expand...
Click to collapse
Those manuals tell you how to install updates, not how to build your own.
Related
hi guys, did HTC ever release the source code for the 2.1 update?
No. htc are bell-ends and don't even release driver source code, let alone code for their "superior" gui. Hence why it takes a while to port newer versions of android to the hero. Developers have to implement loads of dirty hacks and backports using kernel binary blobs they manage to extract from the 2.1 upgrade.
TheReverend210 said:
No. htc are bell-ends and don't even release driver source code, let alone code for their "superior" gui. Hence why it takes a while to port newer versions of android to the hero. Developers have to implement loads of dirty hacks and backports using kernel binary blobs they manage to extract from the 2.1 upgrade.
Click to expand...
Click to collapse
well thats just bad news!!
but they did afaik release source code for the kernel for many of their phones didn't they, what i would like to know is what does this mean to developers, what can they do with the kernel source?
The kernel is just a modified linux kernel, which has been open source since the early 90's.
Developers can do quite a bit with the kernel, is is basically the bridge between hardware and software.
However, despite running Debian since Etch was the latest stable release, my knowledge of the linux kernel is limited, so you would have to ask a developer for specifics.
TheReverend210 said:
The kernel is just a modified linux kernel, which has been open source since the early 90's.
Developers can do quite a bit with the kernel, is is basically the bridge between hardware and software.
However, despite running Debian since Etch was the latest stable release, my knowledge of the linux kernel is limited, so you would have to ask a developer for specifics.
Click to expand...
Click to collapse
thanks for your help
info on webkit source please..
i was at HTC's Developer Center and i noticed that HTC released the "webkit source code" for several "Sense UI" models, including the HTC Droid Eris, which very much shares our beloved Hero's specs...
i was wondering is this webkit compatible with our GSM Hero, and why didn't HTC release the webkit source for the GSM version?
the reason i'm asking is because i want to take out libwebcore.so alone and patch it, and replace the one in Hero...
Hi all,
Now that CM is dead (RIP) and official Lineage OS for the Wileyfox Swift 2 has not yet happened, i've been looking into other alternative OS's that are compatible with the Wileyfox Swift 2 [marmite].
However i'm not seeing any that are compatible for this device (Resurrection Remix, Dirty Unicorn, LineageOS (yet) and wondered if anyone has had any experience with any other custom OS's that they know are compatible?
Thanks
There are none because there is no source code for this device. You must be patient and wait until Wileyfox releases (Before the end of this month?!) the promised Android 7.1 update, and hope they also release the source code with it.
I did several modifications to stock CyanogenOS 13.1 version for myself, but I found not worth it sharing that, since we're going to receive the new update really really soon. If the update is a disaster, or they do a OnePlus (release the update on the 31st, late in the night before the end of the month, and full of bugs), I'll consider sharing it. But until then, just wait for it.
Thanks for the update. :good::good:
linuxct said:
since we're going to receive the new update really really soon.
Click to expand...
Click to collapse
I live in hope. :fingers-crossed:
linuxct said:
There are none because there is no source code for this device. You must be patient and wait until Wileyfox releases (Before the end of this month?!) the promised Android 7.1 update, and hope they also release the source code with it.
I did several modifications to stock CyanogenOS 13.1 version for myself, but I found not worth it sharing that, since we're going to receive the new update really really soon. If the update is a disaster, or they do a OnePlus (release the update on the 31st, late in the night before the end of the month, and full of bugs), I'll consider sharing it. But until then, just wait for it.
Click to expand...
Click to collapse
Thats not true there is maybe not a source code but the chips inside the device (and drivers) are also used in other devices wich are so you can make roms for this device.
There are no roms because this phone isn't used by many peaple yet or the community isnt big at the moment for this device but we can port roms from the xiaomi redmi 3s for instance
draakwars said:
Thats not true there is maybe not a source code but the chips inside the device (and drivers) are also used in other devices wich are so you can make roms for this device.
There are no roms because this phone isn't used by many peaple yet or the community isnt big at the moment for this device but we can port roms from the xiaomi redmi 3s for instance
Click to expand...
Click to collapse
WTF? Do you think that by having same CPU means we should have the very same source code? I know there's source code for the SD430 in codeaurora, and that Xiaomi released sources for land, but that doesn't mean anything. It'd require a lot of dirty and unnecessary stuff to get it working here (it's not only about the CPU, right?), and since Wileyfox is REQUIRED to release the source code (all OEMs are) we can avoid it by just waiting patiently. From there, building Lineage will be easier, but hey, if anyone wants to do the hard job, use land-m source code and try to port it, is free to do so! :laugh:
linuxct said:
Wileyfox is REQUIRED to release the source code
Click to expand...
Click to collapse
Manufacturers need to release kernel source as it's under a GPL license, but Android itself is under the Apache License 2.0 and manufacturers are not required to release any source code. In fact the vast majority of manufacturers do not release any of their internal Android code.
And having kernel source does not magically allow you to make custom ROMs. In fact you shouldn't even need the manufacturers kernel source unless they are using some obscure hardware.
flibblesan said:
Manufacturers need to release kernel source as it's under a GPL license, but Android itself is under the Apache License 2.0 and manufacturers are not required to release any source code. In fact the vast majority of manufacturers do not release any of their internal Android code.
And having kernel source does not magically allow you to make custom ROMs. In fact you shouldn't even need the manufacturers kernel source unless they are using some obscure hardware.
Click to expand...
Click to collapse
I know, but it's better having and working with it, isn't it? I know we will need to bring up a device tree, and that it's not that easy, but starting out of a good base is better than mixing sources from other phones, at least that's my opinion.
The kernel sources are already available for a long time (slowpokes?): https://bitbucket.org/wileyfox/kernel-wileyfox-msm8937
BeYkeRYkt said:
The kernel sources are already available for a long time (slowpokes?): https://bitbucket.org/wileyfox/kernel-wileyfox-msm8937
Click to expand...
Click to collapse
Oops. You made my day man. I swear I wasn't able to find that, I had no idea they published it already, they didn't mention it on social media, and whenever I asked them on the support chat they were like "Sorry, we don't have that".
linuxct said:
Oops. You made my day man. I swear I wasn't able to find that, I had no idea they published it already, they didn't mention it on social media, and whenever I asked them on the support chat they were like "Sorry, we don't have that".
Click to expand...
Click to collapse
Because I do not think that the public (where most users are not geeks, probably) will be interested in the post that the developers have released the source code of the kernel. Or someone beforehand, before closing Cyanogen Inc, released the source code for the kernel. And support is usually not answered to such questions, because they do not have such information.
But in any case you need the information you need to find in all available ways.
Lenovo is the only company to have released an Android Nougat update for an Intel Atom Cherry Trail SoC powered device.
If Lenovo releases the kernel sources for the Android N version created for its Lenovo Yoga Book (Lenovo YB1-X90F/L), developers can start working on Android N upgrades for other devices powered by the Intel Atom Cherry Trail SoCs.
Lenovo has previously released the Android Marshmallow kernel sources for the Yoga Book (https://pcsupport.lenovo.com/us/en/products/tablets/yoga-series/yoga-book/downloads/ds118515 Thus it shouldn't be a problem abiding by the General Public License v2 (GPLv2), which requires Android device makers to publish the kernel source code.
Please consider signing here: https://www.change.org/p/lenovo-kernel-sources-for-lenovo-yoga-book-android-n-7-1-1 . Thank you
True, we really Need to make Lenovo release the source Code, i hope you could edit your Petition by adding that also we Need Infos about how to use the source Code.
Greetings
I'm not sure that it would make a difference, but has anyone tried posting on their support forums or contacting them directly?
It might help our case to note that the device (the Android version, anyway) has been discontinued. I doubt we'll see any further official updates from Lenovo.
Take a look , Hope this will work for you:
https://forum.xda-developers.com/yoga-book/development/sources-yoga-book-nougat-source-code-t3765211
beltani said:
I'm not sure that it would make a difference, but has anyone tried posting on their support forums or contacting them directly?
It might help our case to note that the device (the Android version, anyway) has been discontinued. I doubt we'll see any further official updates from Lenovo.
Click to expand...
Click to collapse
Only via Facebook. Got this answer:
"Thanks for reaching out. Currently, this the only open source http://lnv.gy/2DMoObI we have for Yoga Book. You can keep an eye on the support website as it will be updated if a new open source will be released. Let us know if you have other inquiries."
Feel free to post the link to the petition on the Lenovo forums or even ask them via Facebook/scoial media. The more attention, the greater the chances.
Palm Trees said:
Lenovo is the only company to have released an Android Nougat update for an Intel Atom Cherry Trail SoC powered device.
If Lenovo releases the kernel sources for the Android N version created for its Lenovo Yoga Book (Lenovo YB1-X90F/L), developers can start working on Android N upgrades for other devices powered by the Intel Atom Cherry Trail SoCs.
Lenovo has previously released the Android Marshmallow kernel sources for the Yoga Book (https://pcsupport.lenovo.com/us/en/products/tablets/yoga-series/yoga-book/downloads/ds118515 Thus it shouldn't be a problem abiding by the General Public License v2 (GPLv2), which requires Android device makers to publish the kernel source code.
Please consider signing here: https://www.change.org/p/lenovo-kernel-sources-for-lenovo-yoga-book-android-n-7-1-1 . Thank you
Click to expand...
Click to collapse
THEY UPDATED IT AFTER I CONTACT THEM
CHECK IT OUT https://pcsupport.lenovo.com/us/en/products/tablets/yoga-series/yoga-book/downloads/ds118515
THE MAXIMUM POWER said:
THEY UPDATED IT AFTER I CONTACT THEM
CHECK IT OUT https://pcsupport.lenovo.com/us/en/products/tablets/yoga-series/yoga-book/downloads/ds118515
Click to expand...
Click to collapse
WOW! I've passed this information along. Thanks a lot, this hopefully opens some doors
What did you do exactly?
UPDATE: It's another Marshmallow kernel source code. We need the Android Nougat kernel source code!
Palm Trees said:
WOW! I've passed this information along. Thanks a lot, this hopefully opens some doors
What did you do exactly?
UPDATE: It's another Marshmallow kernel source code. We need the Android Nougat kernel source code!
Click to expand...
Click to collapse
True, i open it and it was another MM sources, i will rewrite to them again, however, i figure it out how to use it, for example specially for yoga Book Windows owners, i tried to install Android distro (Phoenixos, blissos,......) but some Drivers were missing i mean no Sound, no Bluetooth,....... but today i understood how it work, in lib/Firmware we Can add this files in any Android distro to get some or all Drivers work, but im trying to figure out how to copy-paste them inside System.sfs under Windows enviroment :fingers-crossed:
THE MAXIMUM POWER said:
True, i open it and it was another MM sources, i will rewrite to them again, however, i figure it out how to use it, for example specially for yoga Book Windows owners, i tried to install Android distro (Phoenixos, blissos,......) but some Drivers were missing i mean no Sound, no Bluetooth,....... but today i understood how it work, in lib/Firmware we Can add this files in any Android distro to get some or all Drivers work, but im trying to figure out how to copy-paste them inside System.sfs under Windows enviroment :fingers-crossed:
Click to expand...
Click to collapse
Thanks! Hopefully Lenovo releases them - let me know
Get in touch with KonstaT from http://www.modaco.com/forums/forum/445-other-devices/ if you need help with the Android side.
Palm Trees said:
Thanks! Hopefully Lenovo releases them - let me know
Get in touch with KonstaT from http://www.modaco.com/forums/forum/445-other-devices/ if you need help with the Android side.
Click to expand...
Click to collapse
Thanks, i will try to contact him:good:
hi peeps. thank u for stopping by
i want to get into android development and make personal touches and changes to my phone. i quite like oxygenOS so i would like to stick with this and modify that slowly. but i cant figure out how to begin specifically with oxygenos? it doesnt appear as if they release their source code anymore. could anyone please point me in the right direction? thank you
kieran_buffet said:
hi peeps. thank u for stopping by
i want to get into android development and make personal touches and changes to my phone. i quite like oxygenOS so i would like to stick with this and modify that slowly. but i cant figure out how to begin specifically with oxygenos? it doesnt appear as if they release their source code anymore. could anyone please point me in the right direction? thank you
Click to expand...
Click to collapse
Hi,
First of all, OnePlus do release their source code. But if you want to modify your phone and keep OxygenOS, you don't look it the right place.
With root you can have a lot more possibilities for customization, so I'll advice you to check Magisk (a root manager/ customization tool with which you can install modules).
If you want to theme your device you can use Substratum, and install themes from the Play Store.
Search about them and give them a try if you want to
Raiz said:
Hi,
First of all, OnePlus do release their source code. But if you want to modify your phone and keep OxygenOS, you don't look it the right place.
With root you can have a lot more possibilities for customization, so I'll advice you to check Magisk (a root manager/ customization tool with which you can install modules).
If you want to theme your device you can use Substratum, and install themes from the Play Store.
Search about them and give them a try if you want to
Click to expand...
Click to collapse
thank u for getting back to me! i took a look at their github page but it said they stopped releasing the source code because it can be found elsewhere, and i cant find where exactly that is. i dont want to modify the OS as is (root it and customise that way), i mean getting the source code, changing, removing and adding things and then flash my own custom flavour of oxygenOS onto my phone. i figure going with what comes with my phone is best when getting into android development so that there are as few compatibility issues as possible. would you be able to point me exactly how i might obtain the source code? it would be very cool my dude
kieran_buffet said:
thank u for getting back to me! i took a look at their github page but it said they stopped releasing the source code because it can be found elsewhere, and i cant find where exactly that is. i dont want to modify the OS as is (root it and customise that way), i mean getting the source code, changing, removing and adding things and then flash my own custom flavour of oxygenOS onto my phone. i figure going with what comes with my phone is best when getting into android development so that there are as few compatibility issues as possible. would you be able to point me exactly how i might obtain the source code? it would be very cool my dude
Click to expand...
Click to collapse
I hope you're familiar with git. I believe this is what you're looking for. https://github.com/OnePlusOSS
Spaceminer said:
I hope you're familiar with git. I believe this is what you're looking for.
Click to expand...
Click to collapse
i am indeed familiar with git, but i dont exactly understand what i am wanting from that page. i want the full source code to oxygenos and the kernal/binary specific packages for my phone. i previously found this site before but to my knowledge what is on there doesnt get me the source code. am i missing something? thank you for your helps
kieran_buffet said:
i am indeed familiar with git, but i dont exactly understand what i am wanting from that page. i want the full source code to oxygenos and the kernal/binary specific packages for my phone. i previously found this site before but to my knowledge what is on there doesnt get me the source code. am i missing something? thank you for your helps
Click to expand...
Click to collapse
Check under the Android section on that page. Which specific OnePlus device do you have? There are many of them. I can help you find it if I know your model.
Spaceminer said:
Check under the Android section on that page. Which specific OnePlus device do you have? There are many of them. I can help you find it if I know your model.
Click to expand...
Click to collapse
i see where you mean. but it seems like they stopped doing these releases. on their latest release (11 months ago) they said; "based on conversations we had with our dev community and the fact that we have only made few changes on AOSP(Qualcomm BSP) device tree, we will not be releasing AOSP device trees for future devices, the community can get the baseline from our device and get the source code from Qualcomm."
"the community can get the baseline from our device and get the source code from Qualcomm." i have no idea where to get what they are talking about.
i have the oneplus 8 pro
kieran_buffet said:
i see where you mean. but it seems like they stopped doing these releases. on their latest release (11 months ago) they said; "based on conversations we had with our dev community and the fact that we have only made few changes on AOSP(Qualcomm BSP) device tree, we will not be releasing AOSP device trees for future devices, the community can get the baseline from our device and get the source code from Qualcomm."
"the community can get the baseline from our device and get the source code from Qualcomm." i have no idea where to get what they are talking about.
i have the oneplus 8 pro
Click to expand...
Click to collapse
They're probably referring to CAF sources for the Qualcomm bit. The baseline part is probably a reference to the script that's in the Android section. This is the closest thing to what you're after that I can find.
https://github.com/AndroidBlobs/device_oneplus_OnePlus8Pro
https://github.com/AndroidBlobs/vendor_oneplus_OnePlus8Pro
https://github.com/codeauroraforum (CAF)
Spaceminer said:
They're probably referring to CAF sources for the Qualcomm bit. The baseline part is probably a reference to the script that's in the Android section. This is the closest thing to what you're after that I can find.
https://github.com/AndroidBlobs/device_oneplus_OnePlus8Pro
https://github.com/AndroidBlobs/vendor_oneplus_OnePlus8Pro
https://github.com/codeauroraforum (CAF)
Click to expand...
Click to collapse
ah yes. my brain has clicked with the baseline part, i would plug my phone in and it would use adb to extract the "baseline"? i understand this process. is what i am asking for difficult? perhaps i am better off taking the kernal files for my phone and integrating it with stock android that i would build and practicing with that? i really appreciate your effort but this "android blobs" is apparantly for reference only, i have no idea what android blobs is. i went into this knowing oneplus isnt extremely AOSP friendly compared to Sony for example, but i am going to push on. do you have any advice? this doesnt appear to be a friendly introduction into existing OS modification by sticking with OxygenOS
We are happy to announce that we now have launched AOSP build instructions for Android 13!
The Xperia Open Source Project (Xperia Open Devices) is an initiative created to guide the developers step-by-step on how to build AOSP for their unlocked Xperia devices. Our instructions will show you how to prepare your environment, how to download all the necessary tools, and how to download and configure the code before you can build AOSP images and flash them on your own device.
New AOSP build instructions for Android 13 - Sony Developer World
developer.sony.com
The one downside is Ubuntu...I would be down to start building roms...but the problem is I'm on windows 11...and prefer it...
Ainz_Ooal_Gown said:
The one downside is Ubuntu...I would be down to start building roms...but the problem is I'm on windows 11...and prefer it...
Click to expand...
Click to collapse
WSL?
unicastbg said:
WSL?
Click to expand...
Click to collapse
WSL??
What is Windows Subsystem for Linux
Learn about the Windows Subsystem for Linux, including the different versions and ways you can use them.
docs.microsoft.com
Code:
sudo apt-get purge ...
The instructions aren't off to a good start.
kevinmcmurtrie said:
Code:
sudo apt-get purge ...
The instructions aren't off to a good start.
Click to expand...
Click to collapse
To be blunt as a rock, you should be doing this on a clean install or inside a container anyways. I'm surprised Sony is not providing us with one.
UsernameNotRecognized said:
To be blunt as a rock, you should be doing this on a clean install or inside a container anyways. I'm surprised Sony is not providing us with one.
Click to expand...
Click to collapse
That's clear from step 1, but not necessary if Sony had created the build correctly. Modern build environments may coexist without issues.
Even apt-get is rather outdated.
kevinmcmurtrie said:
That's clear from step 1, but not necessary if Sony had created the build correctly. Modern build environments may coexist without issues.
Even apt-get is rather outdated.
Click to expand...
Click to collapse
The Guides are copy-paste since quite a time now. You basically just need to change the Tag each time You want to sync the Code. Anyways, sudo apt install works well on Ubuntu while some Parts cant be installed and need to be corrected like zlib1g-dev:i386 which is zlib1g-dev. WSL2 works fine on My W11 install. Just give this a go:
GitHub - bostrot/wsl2-distro-manager: A GUI to quickly manage your WSL2 instances
A GUI to quickly manage your WSL2 instances. Contribute to bostrot/wsl2-distro-manager development by creating an account on GitHub.
github.com
You will like it if You want to keep Windows...
what is the use of all these instructions if there are no developers who have made and supported at least a normal firmware based on android 12
Sakuma_Eitarou said:
what is the use of all these instructions if there are no developers who have made and supported at least a normal firmware based on android 12
Click to expand...
Click to collapse
There are many people involved working on it. It takes times and they need help with logs and testing since there are many supported devices. I am working myself on it with A13 and its a pain in the a** right now... Many small issues and missing stuff here and there. We are also talking about bugs like no Mobile Data + No Wifi and non working Cameras and such... It's a great Project but lacks Users and support...
Miustone said:
There are many people involved working on it. It takes times and they need help with logs and testing since there are many supported devices. I am working myself on it with A13 and its a pain in the a** right now... Many small issues and missing stuff here and there. We are also talking about bugs like no Mobile Data + No Wifi and non working Cameras and such... It's a great Project but lacks Users and support...
Click to expand...
Click to collapse
certainly lacks people and support because the community is too small due to the high cost and unpopularity of the phone. To begin with, I would like to see a completely completed firmware like this https://sourceforge.net/projects/ancientrom/files/gsi/V6.4/ and only then firmware based on a13
maybe one day there will be one fully working ROM with a fully programmable assistant button and a working Sony camera. as well as all the advantages of custom ROM
Sakuma_Eitarou said:
maybe one day there will be one fully working ROM with a fully programmable assistant button and a working Sony camera. as well as all the advantages of custom ROM
Click to expand...
Click to collapse
I can surely tease, there is Something comming this Year. Android 13 2019-2022 Xperias
Miustone said:
I can surely tease, there is Something comming this Year. Android 13 2019-2022 Xperias
Click to expand...
Click to collapse
in general, it doesn't matter, because official Google builds are 5 years behind amateur builds like crdroid and other teams. In my opinion, Android 12-13 looks gray, boring, not beautiful, sad, no transparency effects, colored notification icons. It feels like there are some idiots at Google who can't come up with anything worthwhile, or at least standardize what is already available in custom ROM. For example, it annoys me that the usual aosp assembly is empty, there you can't even adjust the height of swipes of control gestures
Miustone said:
The Guides are copy-paste since quite a time now. You basically just need to change the Tag each time You want to sync the Code. Anyways, sudo apt install works well on Ubuntu while some Parts cant be installed and need to be corrected like zlib1g-dev:i386 which is zlib1g-dev. WSL2 works fine on My W11 install. Just give this a go:
GitHub - bostrot/wsl2-distro-manager: A GUI to quickly manage your WSL2 instances
A GUI to quickly manage your WSL2 instances. Contribute to bostrot/wsl2-distro-manager development by creating an account on GitHub.
github.com
You will like it if You want to keep Windows...
Click to expand...
Click to collapse
would you want to update the aosp build guide as a how to do for xda?
i would certainly be interested in stock aosp build.
"Now you are ready to build AOSP images that can be flashed to a device. To do this, you have to point out your specific device and then start building the images."
this my current blocker. how would i point out the specific device? as i understand the command in the given step ( step5 ) it requires a source. that source is not specified in the builöd instructions or i didn't find them