Related
Any developers out there having HTC desire v and interested in building roms for our device, post here.. I have been helping in development of galaxy mini, and a member of team jellaxy as well..
I am currently not having free time so cannot build one! If anyone else interested post in this thread, I will try out when I have free time in a couple of weeks
Sent from my HTC Desire V using xda app-developers app
i create this thread http://forum.xda-developers.com/showthread.php?t=2007243 this is my first ROM, but i wont to build for our Desire V CM10 or AOSP
AKA_noodle said:
i create this thread http://forum.xda-developers.com/showthread.php?t=2007243 this is my first ROM, but i wont to build for our Desire V CM10 or AOSP
Click to expand...
Click to collapse
That's great @AKA_Noodle. I used to own the Galaxy i9003 and have experience in testing ROMs, customizing, boat ware removal etc. for 10 months. I have just bought a Desire V yesterday and this is my first HTC. I am getting to know the difference.
I have followed your post and am going to ROOT the phone in a couple of days. I am giving my stock 7 days for the just in case hardware issues with my handset. Post that I will unlock the bootloader and free my device. I am ready for testing and development.
And by the way,
Congratulations to all. We finally have a dedicated thread for our phone.
Thanks @AKA_Noodle, i use the European Rom, great
Guys,
I don't own this device, but I'm interested in developing for it.
I believe I could try to port a ROM or two from the desire X to this device, if anyone would test it.
The only thing I need to know is: do you guys have android 4.0.4 or 4.0.3?
Sent from my awesome fridge
4.0.3
Rew64 said:
4.0.3
Click to expand...
Click to collapse
Thanks. I hope that little difference doesn't affect the ROM.
I don't have time in this week, but I'll try to get you guys a ROM next week.
Sent from my awesome fridge
I'm interested with HTC Desire V Rom Development. And I will first make CM10, then MIUI, etc. I'm following the tutorials at XDA.
Finally i have device tree ready for HTC DESIRE V The next task is to download sources for CM9 ( takes a hell lot of time :/ ) and start working on it, hopefully with community's help, it will be completed
i will be uploading the device tree soon, so anyone can help me building it..
I'm waiting for that CM9, because all other ROMs I tried are disappointing. I posted here earlier a version for Baidu ROM but turns out that was also buggish.
So, please someone make a Cyanogenmod for this phone.
yeah... please develop a CM9/10 version for this dual sim phone ///
Until today, i still can't find an easy way to root my device. LOL!
carliv said:
I'm waiting for that CM9, because all other ROMs I tried are disappointing. I posted here earlier a version for Baidu ROM but turns out that was also buggish.
So, please someone make a Cyanogenmod for this phone.
Click to expand...
Click to collapse
I did some snooping - it turns out that it's buggish because we are using the nightly builds version of the Baidu . The official version is V4:
http://translate.google.com/transla...m.php?mod=viewthread&tid=62590&extra=page%3D1
charmainelooi said:
I did some snooping - it turns out that it's buggish because we are using the nightly builds version of the Baidu . The official version is V4:
Click to expand...
Click to collapse
I know, but my version was from that stable one, which is based on version 27. Still it had some "things" because for Baidu stable not means final, it's a project in developement. I guess, if no one develop a CM for our device we'll have to wait for some final Baidu.
One other thing is that they develop Baidu to integrate with their service (let's not forget that Baidu is Google for China), and it will be more suitable to users from China .
Too bad that HTC couldn't release a ROM without bugs. Baidu, even in beta, didn't restart my phone randomly like HTC rom did (stock version too), and I have a friend with Wildfire stock, unrooted, untouched which do the same. Maybe it is something with HTC rom platform, I don't know.
I don't think it is hardware, because if it was, Baidu would restart too.
For developement
I just finished to try every single open source of android to make a new build for this phone and my conclusion is not good.
HTC announced that this phone will not get JellyBean - understandable 1 single core processor, 512 MB Ram, not enough.
That will be a huge obstacle in order to get Paranoid, PAC or Slimbean to this phone - they mentain those sources now only for jellybean. Or for jellybean, we need a new kernel to support that. And even so, we can not know if it will work - poor phone specs.
Cyanogenmod doesn't support DualSim, and I bought this phone for that function only.
MIUI doesn't support DualSim either - I know there are a lot of dualsim phones with MIUI, but these are ported not compiled from source - and MIUI source isn't public (what they have on github is a patch tool, wich doesn't work very well, especially with HTC phones which are more difficult).
LewaOS has a source open on github, but is only for Gingerbread - if they upgrade this it will be our best alternative, because LewaOS is a very stable, fast and reliable ROM, and works well even in low specs phones. Baidu ROM seems to be at the begining some port of LewaOS (I still found some mediatek references in baidu, and mediatek is the main processor for Lewa).
So, we're stuck with Sense...
Desire V Rom Development
rohan007 said:
Finally i have device tree ready for HTC DESIRE V The next task is to download sources for CM9 ( takes a hell lot of time :/ ) and start working on it, hopefully with community's help, it will be completed
i will be uploading the device tree soon, so anyone can help me building it..
Click to expand...
Click to collapse
Hi Rohan,
I am interested In developing Android Rom for HTC desire V, so i required few things, can you suggest where i get the device identity (Device Tree, Vendor) details.
carliv said:
Too bad that HTC couldn't release a ROM without bugs. Baidu, even in beta, didn't restart my phone randomly like HTC rom did (stock version too), and I have a friend with Wildfire stock, unrooted, untouched which do the same. Maybe it is something with HTC rom platform, I don't know.
I don't think it is hardware, because if it was, Baidu would restart too.
Click to expand...
Click to collapse
I have the same problem with my htc desire V, can you please link the rom that solved your problem?
ManthanRB said:
I have the same problem with my htc desire V, can you please link the rom that solved your problem?
Click to expand...
Click to collapse
None, it's a hardware issue. I took it to a service shop and then I sold it and never bought a HTC again.
Hello.
I am very keen in getting the Ubuntu Touch ported to my Xperia Z2 phone. Obviously, I'll need all the help and guidance possible.
What I currently have? developer.ubuntu.com/en/start/ubuntu-for-devices/porting-new-device/
I'm using the official porting guide as checklist. Below are what I have accomplished so far with the guide
Setup my Development Environment
Have built for Nexus with success to see if my environment is up and running (the building threw no errors, so I assume it "works", since I have no means of testing because I don't have a nexus handset)
I have added repos regarding under how to enable a new device.
I have done the first part of the Device specific changes using the check-config script, the _defconfig file in the kernel (this is Sony Xperia Z2 kernel: CyanogenMod/android_kernel_sony_msm8974 , right?)
When I did the build ( just to test so far what I've done ) I got the error that, its using the pre-compiled kernel, or something like that.
Now my questions:
How do I tell it which kernel to use, and where?
Where is the pre-compiled kernel and which is the precompiled: the one from the vendor/ (which I got from extracted binary from sony official) OR the /kernel/sony/msm8974 ?
I've gone looking around to see if I could perhaps follow the pattern used in the porting to the Xperia Z, since they're in the same series. Yet, I hardly could follow what exactly the 'porter' did. I was interested in finding answers to the 'What?', and 'Where?' of the porting done, but couldn't get solid answers.
I ask this here with the hope that, a developer who's been through the porting process will be able to offer assistance. I've been in touch with Mamenyaka, and along the lines, he'll be assisting too. But since he isn't available all the time, I ask this here.
Concerning the above list of questions, please, any assistance will be appreciated.
Its understandable, yet unfortunate, that the official ubuntu porting guide has been made to be so broad and so generic its hard to streamline what it says with a specific device. With this thread, I hope to get very specific instructions precisely tailored to the Xperia Z2 and to accommodate being extensive, instructions for the Z line series.
thanks
EDIT: my error log so far pastebin.com/Wax18UFK
seanmavley said:
Hello.
I am very keen in getting the Ubuntu Touch ported to my Xperia Z2 phone. Obviously, I'll need all the help and guidance possible.
What I currently have? developer.ubuntu.com/en/start/ubuntu-for-devices/porting-new-device/
I'm using the official porting guide as checklist. Below are what I have accomplished so far with the guide
Setup my Development Environment
Have built for Nexus with success to see if my environment is up and running (the building threw no errors, so I assume it "works", since I have no means of testing because I don't have a nexus handset)
I have added repos regarding under how to enable a new device.
I have done the first part of the Device specific changes using the check-config script, the _defconfig file in the kernel (this is Sony Xperia Z2 kernel: CyanogenMod/android_kernel_sony_msm8974 , right?)
When I did the build ( just to test so far what I've done ) I got the error that, its using the pre-compiled kernel, or something like that.
Now my questions:
How do I tell it which kernel to use, and where?
Where is the pre-compiled kernel and which is the precompiled: the one from the vendor/ (which I got from extracted binary from sony official) OR the /kernel/sony/msm8974 ?
I've gone looking around to see if I could perhaps follow the pattern used in the porting to the Xperia Z, since they're in the same series. Yet, I hardly could follow what exactly the 'porter' did. I was interested in finding answers to the 'What?', and 'Where?' of the porting done, but couldn't get solid answers.
I ask this here with the hope that, a developer who's been through the porting process will be able to offer assistance. I've been in touch with Mamenyaka, and along the lines, he'll be assisting too. But since he isn't available all the time, I ask this here.
Concerning the above list of questions, please, any assistance will be appreciated.
Its understandable, yet unfortunate, that the official ubuntu porting guide has been made to be so broad and so generic its hard to streamline what it says with a specific device. With this thread, I hope to get very specific instructions precisely tailored to the Xperia Z2 and to accommodate being extensive, instructions for the Z line series.
thanks
EDIT: my error log so far pastebin.com/Wax18UFK
Click to expand...
Click to collapse
Hello,
if you are still working on this project:
Your Problem was not that you used the prebuilt kernel, your problem was that the script doesnt use mkabootimg correctly. For sony device you have to use another command.
Friend i would love to see ubuntu on my z2
share a link which may be helpful
https://wiki.ubuntu.com/Touch/Devices/minato
Hello people.
I just came to the forums and since nothing is happening here visibly, i was wondering to do CyanogenMod bringup for the device
Dont forget the poll above
If there are people here, willing to help us out a bit, it would be good to do something here.
Post your hangouts here, if you are interested in what we are wanting to do.
We can use all the help available. Testing, dev-ing, etc! Just pool in everything we got and lets get rolling
br
s
I hope cm comes to this device I see ATM there's not a lot happening in the way of custom ROMs suppose its early days [emoji3]
Yeah, although CM would be good at some point in the future, I don't know how useful it is at the moment since the phone is running pretty much stock android anyway with just minimal Sony skinning on top however it'd still be nice to see it as an option
+1
(As soon as I will be able to buy it this week. )
+1 ! Would be awesome
cant wait for a better rom for M4!
+1
But now how can M4 Aqua ROOT ? , many root tools not support yet ?
[email protected] said:
+1
But now how can M4 Aqua ROOT ? , many root tools not support yet ?
Click to expand...
Click to collapse
have you tried kingroot? it works on z3 lollipop
Today I bought E2303.
[email protected]
None of the rooting methods are working.
Cyanogen would be nice . .
Cyanogenmod would be soooo nice to see on our phones! HW is great, but sony's software is crippling it...
Sent from my E2303 using XDA Free mobile app
who can root it???
Can't wait for CM. There is so much bloat in this phone
Maybe in a few months
Have Sony released device/kernel sources? I'm planning to buy this phone and I can compile roms if it has open sources
dadi11 said:
Have Sony released device/kernel sources? I'm planning to buy this phone and I can compile roms if it has open sources
Click to expand...
Click to collapse
Nothing yet.
No BL unlock/root yet.
"Thread closed until there is something to do.
Before to start flashing
This is an UNOFFICIAL version of CM12.1, so this means that have bugs that i hope to fix soon. So use it carefully at your own risk. The most important thing to say, after flash this ROM,is ....
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
Installation Guideline
Install the lastest version of TWRP (it's in uploading state and have an important update in fstab file)
Power down your phone and go in recovery mode.
Copy the ROM file in your sdcard
Make a wipe data/factory reset
Install the zip you copied
Wipe cache
Reboot
What works
First Boot
Audio
RIL
SDCARD
Tethering
LEDS
Touchpad now works
Bluetooth (partial: pairing not works)
Some else i'm testing
Light and proximity sensors, Accelerometer, Gyroscope and Magnetic sensors
What not works
Camera
GPS
NFC
SMS
Anything else i will find and fix
Screenshots and Video
In the top of the pace, section Screenshots.
Download
M4 Aqua ProjectMarshmallow Official Site
Uploading in this moment. You will see a post on my site!
Installation
Be sure to have my TWRP installed on your device. If you don't have it go to my site and download it (see download section).
Download and copy the ROM and GAPPS in the root of your SD
Boot in TWRP
Wipe your data (wipe data/factory reset in TWRP)
Install the ROM (Install... in TWRP)
Install GAPPS (see more information in the following GAPPS Section)
Reboot
GAPPS
You can download your GAPPS here. Be sure to download the ARM64 version for 5.1. The pico version is the minimal one (save more space).
Bug Channel
Please report any bug and issues here!
http://projectmarshmallow.altervista.org/bug-channel/
Both the ROM and the new RECOVERY will be uploaded on my site. Stay in touch!
XDA:DevDB Information
CyanogenMod 12.1, ROM for the Sony Xperia M4 Aqua
Contributors
tonystark88
Source Code: https://github.com/projectmarshmallow
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
Version Information
Status: Alpha
Created 2015-12-12
Last Updated 2016-04-30
Thanks for the rom, but where is the download? All I see is the download page for TWRP
Still uploading. I will advice you when finishs. Anyway its a testing ROM...not for daily use.
Does this has any problem with battery draining more than the stock rom? because this problem existed in my old ? z1 and i can't find anything related to the camera, so am asking if is it working? and any chance of porting z4 camera framework so we can use superior auto in this rom? Thanks in advance
I think is a bit premature make these kind of discussions now. When i'll make this rome stable (now it's a test build, have some reboot problems probaby lrelated to thermanager config) we can face more problems. But don't worry, any problem/idea will be faced at right time.
Awesome! Thank for your work!
Thanks for excellent work! Hope some major bugs could be fixed asap [emoji481]
Sent from my E2312 using Tapatalk
put more SS please...
WiFi not working???About Sound too??
And This is Android M or Android LP???
CyanogenMod 12 is based on android 5.x so that means this rom is lollipop
I'm waiting for the upload because the rom boot loops for a thermanager problem. Anyway i have fixed also sensors. I'm not able at this moment to offer more infos because rom boot loops. When i fix the thermanager config and rom will be stable i could be more detailed. I'm sure that RIL and 3g connection works. Wifi powers on but not reveal available Wi-Fi but i think is a configuration problem too.
Let me work guys, we are so close
Great news. Thanks God for You.Good Luck and we will wait for results
Wysłane z mojego E2303 przy użyciu Tapatalka
tonystark88 said:
I'm waiting for the upload because the rom boot loops for a thermanager problem. Anyway i have fixed also sensors. I'm not able at this moment to offer more infos because rom boot loops. When i fix the thermanager config and rom will be stable i could be more detailed. I'm sure that RIL and 3g connection works. Wifi powers on but not reveal available Wi-Fi but i think is a configuration problem too.
Let me work guys, we are so close
Click to expand...
Click to collapse
If you can force enable adb and upload the rom I'm sure that we can send you logcats to find the problems. Also, could you upload the new TWRP that is mentioned in the OP?
@tonystark88
Hi, under GPL v2 license you are required to link a copy of the kernel you used, otherwise, would be in violation of the license. Thank you.
I have taken a look at your source, would it be possible if u rebuild it with Sony's Unified Kernel? Thanks!
boylush said:
@tonystark88
Hi, under GPL v2 license you are required to link a copy of the kernel you used, otherwise, would be in violation of the license. Thank you.
I have taken a look at your source, would it be possible if u rebuild it with Sony's Unified Kernel? Thanks!
Click to expand...
Click to collapse
I'm not violating anything, i'm not reselling or forcing someone else. I don't understand all this pressure, you have all the informations you want now, you saw my sources. The kernel is the same published from sonyxperiadev. I have to fork it to my page to be in rule with GPLv2? I don't think, i think is useless.
If you want that i publish my sources (already unstable) on the first page, i don't see the problem, i will do it.
Also, i see this discussion only a waste of time that i subtract to my work.
tonystark88 said:
I'm not violating anything, i'm not reselling or forcing someone else. I don't understand all this pressure, you have all the informations you want now, you saw my sources. The kernel is the same published from sonyxperiadev. I have to fork it to my page to be in rule with GPLv2? I don't think, i think is useless.
If you want that i publish my sources (already unstable) on the first page, i don't see the problem, i will do it.
Also, i see this discussion only a waste of time that i subtract to my work.
Click to expand...
Click to collapse
It's not out of nothing, cos ur sources must be able to build. You changed one of the defconfigs to cyanogenmod_blablabla so you have to fork and make the changes on ur end as well. Hope u understand
boylush said:
It's not out of nothing, cos ur sources must be able to build. You changed one of the defconfigs to cyanogenmod_blablabla so you have to fork and make the changes on ur end as well. Hope u understand
Click to expand...
Click to collapse
It's the temp .config file generated when u build the kernel. I renamed it and used because differently from the asp defconfig is formatted well.
boylush said:
It's not out of nothing, cos ur sources must be able to build. You changed one of the defconfigs to cyanogenmod_blablabla so you have to fork and make the changes on ur end as well. Hope u understand
Click to expand...
Click to collapse
I see no problem here especially since Sony hasn't exactly released the kernel code. There is no reason to be so distrustful. Heck he hasn't even released the rom yet so what are you complaining about. Please don't take offense. He is just trying to further this community
boylush said:
It's not out of nothing, cos ur sources must be able to build. You changed one of the defconfigs to cyanogenmod_blablabla so you have to fork and make the changes on ur end as well. Hope u understand
Click to expand...
Click to collapse
Supports developers, do not lock their work
I don't understand this mentality of 'Let the dev work and do his thing' and saying that he should be given space to himself to work and build CM12 for The M4 Aqua. As it stands, you all don't know what Open Source Means. The M4 Aqua is in a state where much dev work is needed and all you guys do is hamper the speed at which developers can build ROMs for you. Without Kernel Source code and all LOCAL modifications uploaded, other devs can't jump in and help out to build for the M4 Aqua. I work mainly in the Xperia SP Forums and when the Xperia SP got released, it barely had any source code given by SONY but now we're at CM13. CM13!!!! From a 2012 device to 2015 we have gotten CM13 while YOUR M4 Aqua is stuck at even building CM12! All the Xperia SP had going for it is the AMAZING DEV support with SO MUCH OPEN SOURCE CODE that we all learnt to share. We keep the credits individual to commits and we all gave credits which were due in every rom we built.
If I can't build the ROM with what you say uses the original sony kernel source code, then this ROM is violating GPL code. I will be back soon to test the results and see if it does indeed build and churns out the exact bugs reported. If you are unable to handle even a small request that Boylush has said and say that you're already stressed out due to ONE MEASLY request then there seems to be something wrong.
Those of you who have absolutely no developer experience I would advise you to refrain from trying to defend your individual parties and let this be easily settled by simple building on my end.
I don't like these kinds of reasoning about me and about my work only because in two months other people aren't been able to boot nothing, also a recovery. This is the last time i will respond to you because this is a DEV topic, and here will be DEV things.
Furrydaus said:
The M4 Aqua is in a state where much dev work is needed and all you guys do is hamper the speed at which developers can build ROMs for you. Without Kernel Source code and all LOCAL modifications uploaded, other devs can't jump in and help out to build for the M4 Aqua.
Click to expand...
Click to collapse
I repeat this thing again, all my sources are public. Just see the first page of this topic. And also, all sources are open on sonyxperiadev and are a intellectual property of Sony. All the LOCAL modifications are on my github page, in the commit area. Just click and see.
Furrydaus said:
I work mainly in the Xperia SP Forums and when the Xperia SP got released, it barely had any source code given by SONY but now we're at CM13. CM13!!!! From a 2012 device to 2015 we have gotten CM13 while YOUR M4 Aqua is stuck at even building CM12! All the Xperia SP had going for it is the AMAZING DEV support with SO MUCH OPEN SOURCE CODE that we all learnt to share. We keep the credits individual to commits and we all gave credits which were due in every rom we built.
Click to expand...
Click to collapse
And i'm happy for the Sony XPERIA SP, this means people work together. In the case of Sony M4 Aqua i just saw topics that bumps out after i started to develop, also if only the recovery, for this device. No one sent me a message for say, "Tony let's work together".
Furrydaus said:
If I can't build the ROM with what you say uses the original sony kernel source code, then this ROM is violating GPL code. I will be back soon to test the results and see if it does indeed build and churns out the exact bugs reported. If you are unable to handle even a small request that Boylush has said and say that you're already stressed out due to ONE MEASLY request then there seems to be something wrong.
Click to expand...
Click to collapse
I'm not stressed, i feel great thanks And again no one ROM violates the GPL license. Simply because there isn't yet on the site and will not be until will complete boot correctly. And about the request, i responded yet. I have to repeat that i used the same kernel published by sonyxperiadev site WITHOUT MODIFICATIONS ?
Furrydaus said:
Those of you who have absolutely no developer experience I would advise you to refrain from trying to defend your individual parties and let this be easily settled by simple building on my end.
Click to expand...
Click to collapse
Probably in the ROMS world this sentence is true. But i'm a graduated ICT Engeneer and i worked in past in Android. Maybe i know a little bit of devel things, and i say "a little bit" because i know i can do it, and i not let you and others to offend me without know who i am.
CONCLUSION
Without me, the unexperienced, this device today has a working recovery and i hope for ALL THIS COMMUNITY a working CM12.1 . And i repeat again this thing: THE SOURCES ARE PUBLIC ON MY GITHUB AND ON THE SONYXPERIADEV GITHUB. I'm not blocking the work of anyone and i will be happy if someone else will make the rom work better and efficiently than mine. I will learn where i failed from the other devs commits, like i always did.
I hope is more clear my point of view now to avoid future noisy discussions.
Hi everyone, who still browses these threads.
It's pretty obvious that development for our devices is practically dead. But as I noticed pretty recently - devices like Xperia T or S III mini are one of the first to get Lineage OS. I believe someone spoke about starting new development for Xperia P and I'm interested in any news. Also, I have two Xperia U devices laying around so I'd be willing to help out. Tell me, what you think. Can we push P, U, Sola or Go any further? It seems like a fun challenge to me...
The sony devices with novathor chipset i almoast dead duo to the low chip power an some developers have left this phones ... but are some developer like hakx20 is still working on cm12.1 and lineage 13 for xperia p and kebabra10 a rusian developer is trying to build lineage 14 for xperia p ... i hope to get a bugles lineage 13 on my phone
@HiR3x thanks for mentioning me but well kadabra10 gave up already and well im working on Oreo which is almost done just need to get working boot.img. But well yeah this is just for Xperia P and well once i got it booting i will release all the device tree sources so other devs can use them.
---------- Post added at 06:17 PM ---------- Previous post was at 05:58 PM ----------
thedeermaster said:
Hi everyone, who still browses these threads.
It's pretty obvious that development for our devices is practically dead. But as I noticed pretty recently - devices like Xperia T or S III mini are one of the first to get Lineage OS. I believe someone spoke about starting new development for Xperia P and I'm interested in any news. Also, I have two Xperia U devices laying around so I'd be willing to help out. Tell me, what you think. Can we push P, U, Sola or Go any further? It seems like a fun challenge to me...
Click to expand...
Click to collapse
If you have 2 Xperia U you could be a tester if you want but well still need to finish oreo then we can test
And to answer the second question then yes we can push our devices a lot more then LP yeah sure we didnt get MM or N but well with help of @ChronoMonochrome i pushed the device a lot and well i got an zip file of Oreo that will 90% work but well i still didnt get working boot.img which im working on i had a holiday for few days because Christmas and all that stuff but well i need to start working on it again.
So Plan is like this:
1. Working boot.img with disabled SElinux
2. Test the zip
3.5. If it doesnt boot find a fix.
4. Fix bugs
The problem is that i needed to delete entire SEpolicy stuff in device tree to get it compile because it wasnt updated from LP and well MM changed a lot of SElinux stuff so the first thing to do is to disable SElinux totally in kernel if that boots up then we can move on and start to create SEpolicy again from scratch (I could use some help on creating the SEpolicy).
And once thats done fix the bugs that were introduced in Oreo bringup.
Also i know 8.0 is not up to date but well once i get this booted up i will surely download LineageOS15.1 sources and build them.
So what i can say at the end is that its not 100% sure that we will get Oreo running but well its 90% possible that we will get it booted up.
So just wait its gonna take some time since im the only dev doing the work.