Related
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.
Realme 1 will be popular among developers for sure.XDA acknowledged it by opening a page for our device even before its sale has started.So all that is good.
Now coming to the problems,
We all know that mediatek is infamous for not releasing kernel sources.That makes it difficult for the developers to build custom ROMs.
On a more positive note since the realme one is based on 8.1 Oreo,I am guessing that its project treble compatible(somebody please confirm this) which makes the custom ROM development easier.
So the final question,
Will we get fully working custom ROMs of future android versions even if oppo and mediatek does not release kernel sources?Will project treble help in doing that??
You most probably will not. Snapdragon phones have better development, for example, the Redmi 4A did not have kernel source till recently, yet we had bugless Nougat ROMs, and now with source we have Oreo. It all depends on developer support, Oppo is not a brand that interests developers, on top of that it is a Mediatek phone, your custom ROM dreams may well be shattered. A few ported ROMs may be made if any developer decides to make it but will most likely be too buggy.
SouradeepB said:
You most probably will not. Snapdragon phones have better development, for example, the Redmi 4A did not have kernel source till recently, yet we had bugless Nougat ROMs, and now with source we have Oreo. It all depends on developer support, Oppo is not a brand that interests developers, on top of that it is a Mediatek phone, your custom ROM dreams may well be shattered. A few ported ROMs may be made if any developer decides to make it but will most likely be too buggy.
Click to expand...
Click to collapse
True.But oppo has never released a phone like this.
This phone has the same chipset(helio p60) of oppo f7 which is two times more costly than the realme 1.Therefore it offers immense value for money.And this will attract a lot of customers.Normally when a device has a huge customer base and if it is a value for money device, developers usually become interested in those devices.
Also I know know that both mediatek and oppo have violated GPL many times by not releasing the sources.But since this device is treble compatible,it should solve that problem to a certain extent right?
I am open to discussion...
gauthamkithu said:
Realme 1 will be popular among developers for sure.XDA acknowledged it by opening a page for our device even before its sale has started.So all that is good.
Now coming to the problems,
We all know that mediatek is infamous for not releasing kernel sources.That makes it difficult for the developers to build custom ROMs.
On a more positive note since the realme one is based on 8.1 Oreo,I am guessing that its project treble compatible(somebody please confirm this) which makes the custom ROM development easier.
So the final question,
Will we get fully working custom ROMs of future android versions even if oppo and mediatek does not release kernel sources?Will project treble help in doing that??
Click to expand...
Click to collapse
Yes it will help, as project treble is a initiative by Google to help developers create custom roms without approaching Vendor(Oppo) or the Manufacturer(Mediatek).
gauthamkithu said:
Realme 1 will be popular among developers for sure.XDA acknowledged it by opening a page for our device even before its sale has started.So all that is good.
Now coming to the problems,
We all know that mediatek is infamous for not releasing kernel sources.That makes it difficult for the developers to build custom ROMs.
On a more positive note since the realme one is based on 8.1 Oreo,I am guessing that its project treble compatible(somebody please confirm this) which makes the custom ROM development easier.
So the final question,
Will we get fully working custom ROMs of future android versions even if oppo and mediatek does not release kernel sources?Will project treble help in doing that??
Click to expand...
Click to collapse
Their response shown below,
We understand that you want to give root access to the device and we apologize for the inconvenience caused.
As per the policy, it is not suggestible to root the device. However, if you want to root the device, you can root it using any third party boot-loader on your risk. We won't be able to assist you with any information regarding the rooting of device.
nisanthu said:
Their response shown below,
We understand that you want to give root access to the device and we apologize for the inconvenience caused.
As per the policy, it is not suggestible to root the device. However, if you want to root the device, you can root it using any third party boot-loader on your risk. We won't be able to assist you with any information regarding the rooting of device.
Click to expand...
Click to collapse
I don't need root access, but there are issues with Color OS 5.
Like:
1. New notification pop appear for 3-4 seconds and you cannot swipe and close them, you need to wait to automatically close them, hampering your work. In other OS you can simply swipe left/right/both to close popup.
2. If you enable development option, then yellow notification will show constantly to close it, until you close mode. Why can't I use function like mock location, etc.
3. If you use app which use accessibility services (like Greenify) then it will constantly show notifcation bar sign to close, it means you cannot use Developer Mode or Accessibility Services Apps.
Hope Oppo will fixes these issues with Color OS in future updates.
""1. New notification pop appear for 3-4 seconds and you cannot swipe and close them, you need to wait to automatically close them, hampering your work. In other OS you can simply swipe left/right/both to close popup.""
HERE IS SOLUTION FOR YOU> SWIPE UP to CLOSE
Ayyshjaju said:
I don't need root access, but there are issues with Color OS 5.
Like:
1. New notification pop appear for 3-4 seconds and you cannot swipe and close them, you need to wait to automatically close them, hampering your work. In other OS you can simply swipe left/right/both to close popup.
2. If you enable development option, then yellow notification will show constantly to close it, until you close mode. Why can't I use function like mock location, etc.
3. If you use app which use accessibility services (like Greenify) then it will constantly show notifcation bar sign to close, it means you cannot use Developer Mode or Accessibility Services Apps.
Hope Oppo will fixes these issues with Color OS in future updates.
Click to expand...
Click to collapse
gauthamkithu said:
Realme 1 will be popular among developers for sure.XDA acknowledged it by opening a page for our device even before its sale has started.So all that is good.
Now coming to the problems,
We all know that mediatek is infamous for not releasing kernel sources.That makes it difficult for the developers to build custom ROMs.
On a more positive note since the realme one is based on 8.1 Oreo,I am guessing that its project treble compatible(somebody please confirm this) which makes the custom ROM development easier.
So the final question,
Will we get fully working custom ROMs of future android versions even if oppo and mediatek does not release kernel sources?Will project treble help in doing that??
Click to expand...
Click to collapse
It confirmed via email. The reply is given below:
"Thank you for writing to RealMe Customer Service regarding Project Treble inquiry.
We are delighted to inform you that your RealMe 1 device supports Project Treble. It is already enabled in your device."
But after some researchs i realised that even if it could support project treble, we still can't flash GSI rom with a locked bootloader. (Correct me if it is a wrong findings)
best customm rom
which is the best custom rom available for realme 1 ?
mygadgetreviewer said:
which is the best custom rom available for realme 1 ?
Click to expand...
Click to collapse
rightnow none..
root is not possible yet..
Any chances of custom roms that may pop up for realme 1
I am buying a new phone soon. I would like to know if realme 1 will get a custom rom? Please reply quick. Also when do you think the custom rom will be available?
custom rom
kindly worked custom rom,how can flash twrp?
Firmware
gauthamkithu said:
Realme 1 will be popular among developers for sure.XDA acknowledged it by opening a page for our device even before its sale has started.So all that is good.
Now coming to the problems,
We all know that mediatek is infamous for not releasing kernel sources.That makes it difficult for the developers to build custom ROMs.
On a more positive note since the realme one is based on 8.1 Oreo,I am guessing that its project treble compatible(somebody please confirm this) which makes the custom ROM development easier.
So the final question,
Will we get fully working custom ROMs of future android versions even if oppo and mediatek does not release kernel sources?Will project treble help in doing that??
Click to expand...
Click to collapse
Is realme 4gb version firmware available? Please provide the link of stock firmware.
Any update on bootloader unlock and rooting..?
Realme 1 support project terbel
:good:
gauthamkithu said:
Realme 1 will be popular among developers for sure.XDA acknowledged it by opening a page for our device even before its sale has started.So all that is good.
Now coming to the problems,
We all know that mediatek is infamous for not releasing kernel sources.That makes it difficult for the developers to build custom ROMs.
On a more positive note since the realme one is based on 8.1 Oreo,I am guessing that its project treble compatible(somebody please confirm this) which makes the custom ROM development easier.
So the final question,
Will we get fully working custom ROMs of future android versions even if oppo and mediatek does not release kernel sources?Will project treble help in doing that??
Click to expand...
Click to collapse
The realme 1 support project terbel I used the to check and it's shows that it support
confirmed the realme 1 and 2pro are getting bootloader unlock
Confirmed by realme CEO madhav Seth realme 1 and 2pro are getting bootloader unlock and kernel source code confirmed on twitter by him
Sailfish os
I want sailfish os for our realme device
Bootloader unlocked finally
Realme 1 has got bootloader unloccked when can we expect to get custom rom now
Imrans123 said:
Realme 1 has got bootloader unloccked when can we expect to get custom rom now
Click to expand...
Click to collapse
You need to wait for kernel sources to get released so devs can work on custom roms. If we get a TWRP recovery, you can try out the A/B GSI roms which are good but slightly buggy. If you want a bugfree rom, you need to wait a while, maybe a month or so.
Thanks bro when can we expect releases of kernel source another quarter
I few months/weeks back i read a new article on xda about xiaomi stating that they will now start releasing source codes faster.
Anyone else also read that?
Haven't xiaomi released the codes for KENZO yet ?
It should increase custom ROMs performance drastically, right?
Thankyou!
sssaini007 said:
I few months/weeks back i read a new article on xda about xiaomi stating that they will now start releasing source codes faster.
Anyone else also read that?
Haven't xiaomi released the codes for KENZO yet ?
It should increase custom ROMs performance drastically, right?
Thankyou!
Click to expand...
Click to collapse
Dude Source code released already. Source code is not like a raw material or fuel which is fed everyday to increase in performace of device.
Xiaomi dont care if source code is open to public. They would rather prefer to keep it closed source so that their userbase stick to the miui and not move to custom roms.
Only reason they give source code coz its based on qualcomm chip which is open source friendly. The reason u will see custom roms for xiaomi snapdragon devices.
Mediatek chip is based on closed source thats why no development or custom roms based on mediatek devices.
Xiaomi dont plan to give nougat or oreo to kenzo so why they will release new source code for new android version.
They only said it for new devices which are treble compliant. It will be easy for them to write the code based on treble standards. Hence they will push it faster. Not for kenzo.
So tc and Sweet dreams.
I am attempting to build an AOSP ROM for S8 and I'm not sure what is required nor where to acquire said requirements
So far I am assuming that the Proprietary binary/blobs are kept in /system/vendor, but I'm not sure about where to acquire the device tree for S8
If I need anything else to compile AOSP for S8 please let me know what I need and where/how I can find it
Also PLEASE let me know how I can do this safely so that this won't hard brick or damage my hardware
Note: I DO NOT care about compatibility at this stage, such as camera not working, finger print reader broken, and so on, as long as the os itself works, after I confirm the os can work successfully I will attempt to fix the incompatibilities
You could look at the lineage os thread
Awesomeslayerg said:
You could look at the lineage os thread
Click to expand...
Click to collapse
i would prefer if it is not based on an existing custom rom to avoid copyright/ownership issues, eg forking a custom rom and claiming it as my own is basically copyright, unless i am explicitly allowed by the developer of specified ROM
smallville7123 said:
i would prefer if it is not based on an existing custom rom to avoid copyright/ownership issues, eg forking a custom rom and claiming it as my own is basically copyright, unless i am explicitly allowed by the developer of specified ROM
Click to expand...
Click to collapse
You could always join the telegram group and ask
Awesomeslayerg said:
You could always join the telegram group and ask
Click to expand...
Click to collapse
plus https://forum.xda-developers.com/showpost.php?p=78970120&postcount=134
"
Quote:
Originally Posted by smallville7123
where can i find the source code for this so i can make my own modifications to the ROM, or perhaps a tutorial on making my own AOSP ROM for the S8 (with all required links) as so far i cannot seem to find the Device Tree for the S8 which is apparently required for compiling the AOSP
Yea that's what I asked couple of posts ago but the devs keep it secret and ignored my request .. Never saw that ppl keep device trees secret but here ..
Sent from my OnePlus 6T using XDA Labs"
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