Related
First question does Osprey's hardware support Android O ?
Prob does but we'll prob not be able to have some features
Osprey's hardware didn't supported android N too but we got it with custom rom... I think this will happened with android O too
Our device is in list to get los 15 ie. android O
androidbaba said:
Our device is in list to get los 15 ie. android O
Click to expand...
Click to collapse
Well that's a pleasant news. And considering the awesome dev support our device has, I'm pretty sure we'll be getting plenty of Android O ROMs to try out.
adityak1303 said:
Well that's a pleasant news. And considering the awesome dev support our device has, I'm pretty sure we'll be getting plenty of Android O ROMs to try out.
Click to expand...
Click to collapse
Just for fyi, lineageosdownloads.com is not the official site (download links are redirected to actual linageos.org (org, not com)). So information they give cannot be verified unless the official linageos blog posts something about it.
It's still a long way. Source code hasn't been out yet. After AOSP code is pushed, linageos team will work on it, but considering the limited resources (unlike CyanogenMod), it can take a while. After the base is ready, then devs will focus on building device specific images and fix bugs. Only then android o will be roaster ready. Other derivative ROMs will take more time obviously.
We can't be sure if 8.0 will be fully compatible with our device. We don't have official Nougat kernel sources and proprietary blobs (AFAIK), also from what I've observed so far, the farther apart the last official firmware and target firmware are, the harder it is to keep a ROM unmodified and yet stable & functional.
Our device shouldn't die that easy though, as newer Moto devices with similar hardware as osprey and Merlin have been released.
Broadcasted from Zeta Reticuli
Just like i say earlier our device it wasn't supported android N but we got it thanks to our awesome developers. I think they won't let us down with android O too.. it maybe take a little time but i think we will have android O for our moto g 2015
sorry for my bad english
Hopefully we get O, and hopefully O comes default with the pixel nav because redacting that would take effort thats not worth it now that nexus is dead .
Nikos dima said:
Just like i say earlier our device it wasn't supported android N but we got it thanks to our awesome developers. I think they won't let us down with android O too.. it maybe take a little time but i think we will have android O for our moto g 2015
sorry for my bad english
Click to expand...
Click to collapse
Our device does support Nougat, it is evident by the presence of custom ROMs (and even a stock port). The only reason we didn't get a OTA was because the company didn't provide us. The Moto ROM and these custom ROMs all are based on AOSP code.( Technically, if the company released the full source of their ROM and features, then we could build stock ROMs too)
And yes, you are right, it may take a little while but eventually we should see the ROMs coming
But the absence of latest device specific proprietary stuff and official kernel sources forces devs to look for other branches to fill the gaps and get newer thingies working. In some places it's not possible to implement a certain feature and an older feature is modded to make it work, for example before the official marshmallow OTA was out, we already got marshmallow ROMs but it had some hacky workarounds for radio (I don't know if it was updated after that), same goes for early Nougat when camera was becoming a problem. The camera is still not perfect (check linageos thread), working correctly on some apps and glitching on others. Newer software, newer challenges.
But codes are not exactly like food though, mixture of old and new ones is not always bad. But the blobs and drivers sometime give headache
Broadcasted from Zeta Reticuli
Have faith on our awsome developer we will surely have android O
Well, Android Oreo is out. I really hope that Osprey will get it soon.
https://source.android.com/devices/architecture/treble
according to this website,
"With Treble, a new stable vendor interface provides access to the hardware-specific parts of Android, enabling device makers to deliver new Android releases simply by updating the Android OS framework—without any additional work required from the silicon manufacturers"
Does this mean if someone gets Lineage OS 15 or OTA of Stock Android 8.0, they will receive all the updates from google from security patch to new Android versions (If the hardware is capable of running that version obviously!)?
---------- Post added at 09:47 AM ---------- Previous post was at 09:46 AM ----------
If that so, Manufacturers can just update all the devices which theoretically can run android O , it will be a onetime work, after that it'll be easy to update the devices
That would be amazing. Let's wait for a developer opinion.
I managed to build AOSP 8.0_r4 for osprey with SELinux disabled and tons of warnings, using cm14.1's files with some edits. Though for some reason the kernel doesn't seem to boot (I tried with linage os and squid kernel)
I attached the boot.img it built if someone more expert wants to look at it (I didn't manage to find anything wrong)
Flashing the file results in fastboot "Error: failed to load the kernel"
android1111 said:
I managed to build AOSP 8.0_r4 for osprey with SELinux disabled and tons of warnings, using cm14.1's files with some edits. Though for some reason the kernel doesn't seem to boot (I tried with linage os and squid kernel)
I attached the boot.img it built if someone more expert wants to look at it (I didn't manage to find anything wrong)
Flashing the file results in fastboot "Error: failed to load the kernel"
Click to expand...
Click to collapse
Hi, Alberto97 (the official maintainer of lineageOS for osprey) has successfully booted android O on osprey. If you can get in contact with him, he might help you.
PS. Don't bug him about ETAs. He'll release when he feels its ready.
adityak1303 said:
Hi, Alberto97 (the official maintainer of lineageOS for osprey) has successfully booted android O on osprey. If you can get in contact with him, he might help you.
PS. Don't bug him about ETAs. He'll release when he feels its ready.
Click to expand...
Click to collapse
Wow.. nice to hear this.. dude how do you know about this
rahul9999 said:
Wow.. nice to hear this.. dude how do you know about this
Click to expand...
Click to collapse
I follow him on G+. He posted the good news there.
https://plus.google.com/+AlbertoPedron/posts/Av6Knfnsja2
adityak1303 said:
I follow him on G+. He posted the good news there.
https://plus.google.com/+AlbertoPedron/posts/Av6Knfnsja2
Click to expand...
Click to collapse
Thanks For the information
I want to know about Merlin.. is it gonna get Android O? And if yes , when?
Abhishek17599 said:
I want to know about Merlin.. is it gonna get Android O? And if yes , when?
Click to expand...
Click to collapse
Hello,
There is no confirmation yet about this from official maintainer
Yes it should be get as Osprey already successfully booted it.. but don't ask for ETA
If you have a JDI display (what you can verify on MIUI via *#*#6484#*#* and on AOSP via "su [click enter] cat /proc/cmdline" command), you currently get a touch lag (limit) on every Oreo/Pie-based ROM (MIUI too). If you move your finger ultra slowly, the touch pointer stays until you move 2-3mm in distance, then it simply jumps. I really don't want to explain why it feels like crap, but even a single millimeter isn't a small unit on miniaturized computers which often need to be operated in detail (UI sliders, graphic editors, scrolling clickable elements).
So, if you happen to understand that and to already be pissed off, here you go: I built a kernel with the touchscreen firmware extracted by Luca Stefani https://review.lineageos.org/c/LineageOS/android_kernel_xiaomi_msm8996/+/197860 long ago, when Xiaomi still had it fixed. Sadly, the scorpio-o-oss source code drop (which is used on every AOSP Pie ROM) and any of the official Oreo MIUI builds no longer contain it.
Then here we go: so far, only one tester booted it for me and it was on Syberia ROM, while the image I link is made on top of LOS 16 trees. I want to test with few people before committing. Maybe it's too much of a hassle, but at least nobody will tell me it's dangerous or irrelevant.
Your mission is:
- test it
- don't be dumb to ask about anything explained in the thread
https://transfer.sh/12rbtB/lineage-16.0-20190725-UNOFFICIAL-capricorn.zip
For moderators: even if it's kernel, it's more of a mod and nothing with plans to be further maintained. If you really decide to move it, it's up to you, but to me, it wouldn't make sense.
It works! Thanks a lot!
Jdi
Current state: need to figure out why fp gets broken, as it turns out it is :| If I won't come up with any solution, I'll just build the kernel sometimes, for the people who hate this lag and couldn't use any ROM with it (like me). But I hope I'll fix it up.
Edit: Pie trees may be unfinished or requiring something special, because fp works properly with 15.1 build.
https://transfer.sh/7fHND/lineage-15.1-20181224-UNOFFICIAL-capricorn.zip
Build made on the current sources
https://transfer.sh/12rbtB/lineage-16.0-20190725-UNOFFICIAL-capricorn.zip
Would you make flashable file for twrp, so we could use it with other ROMs .. For example, I`m on Pixel 8.1 Final now ..
Regards
bmasgone said:
Would you make flashable file for twrp, so we could use it with other ROMs .. For example, I`m on Pixel 8.1 Final now ..
Regards
Click to expand...
Click to collapse
First test this build and then I'll link the commit sent to LOS gerrit.
j1505243 said:
First test this build and then I'll link the commit sent to LOS gerrit.
Click to expand...
Click to collapse
I'm not willing to flash a whole rom but curious to try - Could you provide your kernel patch (preferred) or a compiled kernel?
Did you get fingerprint working on Pie?
jamesd__ said:
I'm not willing to flash a whole rom but curious to try - Could you provide your kernel patch (preferred) or a compiled kernel?
Did you get fingerprint working on Pie?
Click to expand...
Click to collapse
Nobody tested the existing build yet, that's the only reason why I'm not pushing it to gerrit.
The source commit is here https://review.lineageos.org/c/LineageOS/android_kernel_xiaomi_msm8996/+/197860
sorry i dont know how to flash it, can u teach me to use it? jdi work on my phone and the touch lag is too bad.
sorry my english is poor
Hey,
over the last few weeks I've used my Christmas vacation to start working on the Z18 again. However since work is coming up again soon, I won't have that much time (and nerves) for working on this properly until the end of summer probably.
That's why I want to share my codebase with you, so maybe someone can pick up where I left off (and really, it's nothing big I did. I merely set up the device tree and made it compile more or less. It doesn't boot because of avb and I'm not aware of any way around that)
The device tree can be found here. It's still using a prebuilt kernel but I'll work on fixing the kernel source to a compileable state next.
If anyone wants to get involved, help or pick this up, feel free to do so. The community and I are always happy for help.
Explanations of what the next steps would be can be found below.
Again, do not install this unless you want to softbrick! It's not useable at all and will currently fail at boot verification!!
So what's next?
Fixing avb2.0: This isn't an easy task. How I understand, it either needs the official keys or I failed at signing the build with test keys from LineageOS. Either way this is the first step and top priority so the device boots again at least
EDIT: It seems that https://github.com/rockchip-linux/tools/tree/master/linux/Linux_SecurityAVB might be of some use (given that youyim123, the guy who also did the TWRP for Z18 starred this project). However I don't speak Chinese and putting my device in the hands of Google Translate is risky.. so anyone willing to translate, I'm open for DMs or anything
EDIT2: avb is working, so we can move on to breaking our system now (yay)
Hi, Its a long time i am waiting for a suitable rom to be installed in my Nubia Z18. Can you tell me when this rom can get out? Your effort is highly appreciated.
Zahidul Hasan said:
Hi, Its a long time i am waiting for a suitable rom to be installed in my Nubia Z18. Can you tell me when this rom can get out? Your effort is highly appreciated.
Click to expand...
Click to collapse
Sorry but I can't give you any ETA on this. I'm working on it in my little free time and I'm not even sure what I'm really doing with this. The source is all on the GitHub repo I linked in the OP though, so if you're hesitant and want to get a working ROM, just get involved. It's really not that hard, all it requires is time, patience and lots of googling for weird error messages and further features you want to implement.
You can mostly follow the guide here https://wiki.lineageos.org/devices/bacon/build just replace the bacon command with nx606j-eng and you're good to go and build this yourself. Maybe you can figure out avb since I can't do it by myself, so any help is appreciated.
Dear Sir, Thank you so much for your reply. Last day i tried to push a TWRP from here TWRP installed, but failed to install any gaapps. although process said success.
curtisy said:
Sorry but I can't give you any ETA on this. I'm working on it in my little free time and I'm not even sure what I'm really doing with this. The source is all on the GitHub repo I linked in the OP though, so if you're hesitant and want to get a working ROM, just get involved. It's really not that hard, all it requires is time, patience and lots of googling for weird error messages and further features you want to implement.
You can mostly follow the guide here https://wiki.lineageos.org/devices/bacon/build just replace the bacon command with nx606j-eng and you're good to go and build this yourself. Maybe you can figure out avb since I can't do it by myself, so any help is appreciated.
Click to expand...
Click to collapse
Zahidul Hasan said:
Dear Sir, Thank you so much for your reply. Last day i tried to push a TWRP from here TWRP installed, but failed to install any gaapps. although process said success.
Click to expand...
Click to collapse
Yeah, that thread, if most of the development threads on the Z18 so far, was made by me. I also mentioned in post #3 that flashing Gapps doesn't seem to be working and I was trying to ask the GApps team for help. I never got an answer though, so I stopped looking into this and instead focused my effort on providing a working Lineage build for everyone. The result of that is this thread here
Hey curtisy, are u building lineage OS forZ18 right now?
im chinese and can help to test this rom if need tester, I've a Z18 on hand rite now and still finding a solution to solve the "GAPP" problem
try to flash GAPP package but no luck!
hope the Lineage can release soon for testing~tks!
sky104hk said:
Hey curtisy, are u building lineage OS forZ18 right now?
im chinese and can help to test this rom if need tester, I've a Z18 on hand rite now and still finding a solution to solve the "GAPP" problem
try to flash GAPP package but no luck!
hope the Lineage can release soon for testing~tks!
Click to expand...
Click to collapse
I'm not building it right now. As I said, the project is pretty much on standby for anyone to take it where I left it but I'm still working on it sometimes and try to get it to work. The big issue is that the Z18 uses avb2 which I'm not sure how to bypass and which is also why the Lineage I built will not boot correctly. I don't want to seem rude saying this over and over again, but rather than testing, it would help if I had some more people to get involved. Just download the source and follow the instructions I mentioned in post#4. Progress will be much faster if there was a team behind this and not only one guy who doesn't know what he's doing most of the time. Also getting support in the Lineage IRC is tedious because I can't be online 24/7, so having some more people nag about avb2 there would also be of huge help.
And when there finally is something to test, not only will you be satisfied by your own achievement, but you can also be the initial tester since you built the ROM yourself.
PS: The Gapps issue is probably because of avb2 as well, however I'm not too sure about that
curtisy said:
I'm not building it right now. As I said, the project is pretty much on standby for anyone to take it where I left it but I'm still working on it sometimes and try to get it to work. The big issue is that the Z18 uses avb2 which I'm not sure how to bypass and which is also why the Lineage I built will not boot correctly. I don't want to seem rude saying this over and over again, but rather than testing, it would help if I had some more people to get involved. Just download the source and follow the instructions I mentioned in post#4. Progress will be much faster if there was a team behind this and not only one guy who doesn't know what he's doing most of the time. Also getting support in the Lineage IRC is tedious because I can't be online 24/7, so having some more people nag about avb2 there would also be of huge help.
And when there finally is something to test, not only will you be satisfied by your own achievement, but you can also be the initial tester since you built the ROM yourself.
PS: The Gapps issue is probably because of avb2 as well, however I'm not too sure about that
Click to expand...
Click to collapse
OK I understand your situation, probably not as many ppl own this phone at all...there are many ppl doing developement in Oneplus 6 which I actually own that phone, the Z18 is actually my fd, therefore I cannot keep the phone long...just wonder if there have more ppl involve to this...the "avb2" I'll check to see if anyone on the net doing this, haha! the only solution is more developer involve to this phone!
sky104hk said:
OK I understand your situation, probably not as many ppl own this phone at all...there are many ppl doing developement in Oneplus 6 which I actually own that phone, the Z18 is actually my fd, therefore I cannot keep the phone long...just wonder if there have more ppl involve to this...the "avb2" I'll check to see if anyone on the net doing this, haha! the only solution is more developer involve to this phone!
Click to expand...
Click to collapse
As a quick update for everyone here as well because the discussion has somewhat shifted to the TWRP thread I worked around avb now. I also have a system.img but it's not working as of yet. If you want to get stuck in a boot loop, feel free to ask here and I'll attach the files in the OP for you to try and modify. Without building from source, there's probably not that much you can do though.
Hint: try booting phh-treble GSI first.
j1505243 said:
Hint: try booting phh-treble GSI first.
Click to expand...
Click to collapse
Thanks! Going to try that later but out of curiosity, isn't the reason this phone doesn't have google services out of the box that it wasn't certified by google? If so it's not treble compatible either right? Or am I missing something?
curtisy said:
Thanks! Going to try that later but out of curiosity, isn't the reason this phone doesn't have google services out of the box that it wasn't certified by google? If so it's not treble compatible either right? Or am I missing something?
Click to expand...
Click to collapse
An uncertified device can be freely Treble compatible, so it's really worth to try. Remember to join the Telegram chat of phh-treble if you happen to need some quicker response.
j1505243 said:
An uncertified device can be freely Treble compatible, so it's really worth to try. Remember to join the Telegram chat of phh-treble if you happen to need some quicker response.
Click to expand...
Click to collapse
Awesome. Thank you for the heads up! Might be worth to invest some time in this again then.
j1505243 said:
Hint: try booting phh-treble GSI first.
Click to expand...
Click to collapse
Alright, I tried and I don't think it's working. I get stuck in a bootloop again which repeats every few seconds.
Since I got Lineage compiled, wouldn't it be a better idea to just get that working and be done with it?
Any help is much appreciated!
Hello curtisy, I wish you good luck with your work on the Nubia Z18. I'd love to help you, but unfortunately I have no skills at android developing. Anyway... in case you will get LineageOS to run, I'd be very happy to post an instruction for the installation on my website chinahandys.net. Liebe Grüße, Joscha
curtisy said:
Alright, I tried and I don't think it's working. I get stuck in a bootloop again which repeats every few seconds.
Since I got Lineage compiled, wouldn't it be a better idea to just get that working and be done with it?
Any help is much appreciated!
Click to expand...
Click to collapse
Booting non-GSI will only be tougher :/ Capture deep level logs and inspect that. If you need help, join a phh-treble chat somewhere.
j1505243 said:
Booting non-GSI will only be tougher :/ Capture deep level logs and inspect that. If you need help, join a phh-treble chat somewhere.
Click to expand...
Click to collapse
Yeah that's actually the same point I stopped at with Lineage. Got it to boot to the Nubia logo, captured logs and I can see some weird errors. But getting replies on IRC is a pain, especially if I can only be online for 2hrs a day. That's why I had hoped someone would pick this up but to no avail. Guess I'll have to look into it again and experiment.
Thanks for your help so far! If there's any more tips you want to share, I'm always open for them
furiousjay said:
Hello curtisy, I wish you good luck with your work on the Nubia Z18. I'd love to help you, but unfortunately I have no skills at android developing. Anyway... in case you will get LineageOS to run, I'd be very happy to post an instruction for the installation on my website chinahandys.net. Liebe Grüße, Joscha
Click to expand...
Click to collapse
Hey, sure thing I actually know the site well and got the idea of getting a Z18 from your site. In case you know anyone that might be able to help with logs or anything, I'm always open for suggestions and help.
As a general rule of thumb, so far the process isn't exactly easy because it requires proprietary software. The issue is with boot verification, so to get around that, I rooted my phone with some Chinese Windows application (still trying to reverse that to get the actual keys..) then I could start flashing. The process is tedious though as every failure means reflashing the original rom as well as running the root tool again. I'll try to make it simpler and cross platform once the rom actually works. But it's still a long way to that point.
curtisy said:
Hey, sure thing I actually know the site well and got the idea of getting a Z18 from your site. In case you know anyone that might be able to help with logs or anything, I'm always open for suggestions and help.
As a general rule of thumb, so far the process isn't exactly easy because it requires proprietary software. The issue is with boot verification, so to get around that, I rooted my phone with some Chinese Windows application (still trying to reverse that to get the actual keys..) then I could start flashing. The process is tedious though as every failure means reflashing the original rom as well as running the root tool again. I'll try to make it simpler and cross platform once the rom actually works. But it's still a long way to that point.
Click to expand...
Click to collapse
Unfortunately I personally don't know somebody who has the skills to support you. I have included a call for support for your project in our review.
Welcome to Android Open Source Mutation for the OnePlus 7T
(previously Xtended-Mutate)
Code:
**DISCLAIMER**
We bear absolutely no responsibility for any damages to your device,
from following any instructions or flashing anything we provide.
All software is 'as-is' and no warranty is implied or stated and will not be honored.
As always flash at your own risk.
Everything you could want in a ROM.... and more
ROM originally derived from MSM-Xtended
Features list:
- Android R notification headers
- Substratum support
- Theming (accents, gradients, dark mode)
- FOD icon customizer
- Fully customizable animations
- Different fonts included
- Full sounds customization
- Power menu customization
- Full MD2 support
- Signature spoofing
- Remove ADB notification
- Aggressive battery
- Sensor block per package
- OmniStyle and OmniJaws for headers and weather
- Ambient display and Always-On Display
And even more!
TODO:
- Rebase on Lineage sources
- Finish rebranding
- Add all the features, ALL OF THEM.
- Ok maybe not all.
What works:
- FOD works
- Alert slider works
- DC dimming works
- 60/90/Auto refresh rate
Bugs:
- Auto brightness may have issues
- The carrier Visible is known not working on latest builds.
- ??? This is where you tell us
Install instructions
* Always make sure to flash latest OxygenOS to each slot before installing this ROM!
* Flashing via fastbootd is recommended for now. Although a TWRP is available, it is closed source and therefore in violation of the TWRP GPLv3 license and we therefore cannot link to it here. OTA zips and fastbootd zips will be provided.
1. Set up adb and fastboot on your computer with the latest zip from google. Get them here
2. Ensure your device is upgraded to the latest OxygenOS. We recommend flashing latest to both slots before proceeding.
3. Reboot to bootloader
Code:
adb reboot bootloader
4. Ensure your bootloader is unlocked. This can be done with
Code:
fastboot oem unlock
You'll need to confirm on device. T-Mobile users have to obtain the unlock from T-Mobile first.
5. Now this is the different part with Android 10. If you choose to use the non-official TWRP, you may flash the OTA zip as usual. Otherwise assuming the ROM fastbootd zip is in the same location as your prompt:
Code:
fastboot update -w <file>.zip
6. Reboot and enjoy! Never flash magisk on first reboot as this can cause issues. Always boot at least once.
Updates
* Recommended method is via fastbootd
1. With adb set up and enabled:
Code:
adb reboot bootloader
2. In bootloader mode:
Code:
fastboot update <name>.zip
Reporting bugs:
- To report a bug, clean flash is MANDATORY.
- We provide no support to (Ed)Xposed users, or custom kernels (some custom kernels are known to break FOD, DC dimming, etc). Bugs should be reported with magisk in safe mode or with no modules enabled. We also provide no support for any users of AIO "tweakers" (eg, FDE.AI, LSpeed, NFS, etc), the reason being those are well known to cause instability.
- A good bug report should contain:
Code:
- Device:
- ROM version (eg date ROM was built):
- Magisk used?:
- Tried a clean flash?:
- Concise description (eg, no "fingerprint not working plzzz help"):
- Logcat or dmesg (for boot issues, try the Magisk Module LogCatcher, logcat's I recommend Logcat Reader. Reports without logs WILL BE IGNORED):
Support:
-Telegram: https://t.me/joinchat/KNY93ke5jYFhTFYpwyR3Lw
-XDA: this thread (duh)
Downloads:
{Mod edit}
Device sources:
Kernel: https://github.com/Xtended-Mutate/kernel_oneplus_sm8150
Device: https://github.com/Xtended-Mutate/device_oneplus_hotdogb
Many thanks to:
@linuxandria
jacks84
@Abalam
Creators of MSM-Xtended
AOSiP for some device related things
BlissROMs for a handful of features
Everyone else we probably forgot to mention
We request all discussion to be courteous, on topic, and adding to the discussion. Any hateful or off-topic will be promptly be delt with. Moderators, do what you have to. Thank you.
XDA:DevDB Information
[ROM] [10] [Official] Android Open Source Mutation - hotdogb, ROM for the OnePlus 7T
Contributors
linuxandria, Abalam, jacks84
Source Code: https://github.com/Xtended-Mutate
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: OxygenOS 10.0.9 or newer
Based On: MSM-Xtended
Version Information
Status: Stable
Current Stable Version: 2.0
Stable Release Date: 2020-05-12
Created 2020-05-14
Last Updated 2020-05-17
Thanks for release !
Looks like a cool rom.
So,
fastboot update -w <file>.zip
Click to expand...
Click to collapse
Will be all thats needed to flash?
No need to unzip and flash each file manually , as we do with other ROMs for our OnePlus 7t?
hightech316 said:
Thanks for release !
Looks like a cool rom.
So,
Will be all thats needed to flash?
No need to unzip and flash each file manually , as we do with other ROMs for our OnePlus 7t?
Click to expand...
Click to collapse
No need to unzip no
linuxandria said:
No need to unzip no
Click to expand...
Click to collapse
Awesome.
Is it Ok coming from MSM-Xtended ,or should we flash back to lastest OxygenOS first, then flash your rom?
Thanks for a new room! This looks pretty dope
hightech316 said:
Awesome.
Is it Ok coming from MSM-Xtended ,or should we flash back to lastest OxygenOS first, then flash your rom?
Click to expand...
Click to collapse
I always recommend clean flashing, as we have some serious changes
Can some one upload some screenshot of this ROM, please?
First, THANK YOU VERY MUCH!!!
Next:
Does it have face unlock? I work at the post office and have to use gloves. Face unlock is a must have for me.
Also, does Google pay work?
Congratulations you guys for getting all together now on XDA. Jack: Lets get you back on XDA so you can get some XDA points
Been using this for a day now and just wanted to say this rom is amazing! The customization and the performance is perfect. Thanks again!
Kanging entire project without permission, isn't what we promote on xda
aer0zer0 said:
Congratulations you guys for getting all together now on XDA. Jack: Lets get you back on XDA so you can get some XDA points
Click to expand...
Click to collapse
And luckily, for doing that he decided to use MSM-Xtended with just logo changes and nothing further, no addition, no fixes, just nothing.
Going through the commit history was showing further more. I mean, I have heard many devs saying cherry-picking is the easiest, still people don't want to ?
Moderators, the entire of our work has been used without any notice or permission or anything. Here I mean entire of the work of Team Xtended and we object to it.
Kindly let us know the process to take down this thread.
Regards
BOND
SuperDroidBond said:
And luckily, for doing that he decided to use MSM-Xtended with just logo changes and nothing further, no addition, no fixes, just nothing.
Going through the commit history was showing further more. I mean, I have heard many devs saying cherry-picking is the easiest, still people don't want to ?
Moderators, the entire of our work has been used without any notice or permission or anything. Here I mean entire of the work of Team Xtended and we object to it.
Kindly let us know the process to take down this thread.
Regards
BOND
Click to expand...
Click to collapse
I sort of knew this was going to happen when I saw this thread but yea he basically just cloned y'all entire work without any changes hell I'm surprised it took this long tho for anyone to notice lol.
Unfortunately due to recent feedback and discussions, this thread will be locked until further notice! The project will be undergoing some serious reworking and reevaluation!
@MikeChannon if you could lock this thread we'd be grateful
SuperDroidBond said:
And luckily, for doing that he decided to use MSM-Xtended with just logo changes and nothing further, no addition, no fixes, just nothing.
Going through the commit history was showing further more. I mean, I have heard many devs saying cherry-picking is the easiest, still people don't want to ?
Moderators, the entire of our work has been used without any notice or permission or anything. Here I mean entire of the work of Team Xtended and we object to it.
Kindly let us know the process to take down this thread.
Regards
BOND
Click to expand...
Click to collapse
You have absolutely no right to say this. We have violated no license, and have given all proper authorship and credits. In addition, while it is most certainly true we have based our rom on MSM-Xtended (and have never once denied it!), we have added a smattering of new features and unbroken things they have broken on our supported devices.
Kindly do not make exaggerated accusations, and if you have something to say, let's discuss it in private, not taking to public forums to complain about someone using your work. Personally if someone based off my work, I'd be complimented
If you want to discuss anything in a constructive manner, my telegram username is linuxandria, otherwise do not further pollute our chatrooms and threads with any more of this nonsense, thanks.
And I'll kindly remind everyone that you have kanged the entire work of either AOSP or LOS and you don't see them coming into your xda threads complaining about using their works without violating any licenses and maintaining proper authorship.
Regards
In before the lock! Lol
linuxandria said:
And I'll kindly remind everyone that you have kanged the entire work of either AOSP or LOS and you don't see them coming into your xda threads complaining about using their works without violating any licenses and maintaining proper authorship.
Regards
Click to expand...
Click to collapse
And let's not forget gzosp, either. There was no MSM without GZOSP.
linuxandria said:
Unfortunately due to recent feedback and discussions, this thread will be locked until further notice! The project will be undergoing some serious reworking and reevaluation!
@MikeChannon if you could lock this thread we'd be grateful
Click to expand...
Click to collapse
THREAD CLOSED!
Please advise the moderators' team to re-open the thread when re-working and re-evaluation has been finished but especially when ready to provide a workable link to kernel source.
Request to everybody: If moderator's assistance is required, please do not simply state this in a post! XDA currently has more than 35.5M threads and we cannot and do not scan every single thread and post. For timely actions please use the report function!
LineageOS is a free, community built, aftermarket firmware distribution of android, which is designed to increase performance and reliability over stock android for your device.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit LineageOS Wiki.
Disclaimer: This is the first time I post a ROM, and I'm not able to even test it myself at the moment. It may not even boot, kill your cat or make you lose your stimulus check. I'm putting it out here because there is no lineage OS for 7t (but there is for 7t pro). This is based on the device tree of the 7t pro, I know the pro ROM boots fine on regular 7t, but due to motorized camera setup on the pro, the camera is completely broken on regular. This is the (only) thing I was trying to solve.
ROM: <link removed as not working (yet)>
lineage recovery: https://drive.google.com/uc?export=download&id=1O63wABMA-el8iiYOPkHhhc_zFvUiuJfV
device sources: https://github.com/joske/android_device_oneplus_hotdogb
kernel sources: https://github.com/LineageOS/android_kernel_oneplus_sm8150
Credits:
LineageOS team
StatiXOS (for reference to their hotdogb device tree)
Update:
What works:
ROM boots
wifi works
Lineage Camera works!
audio/video playback
fingerprint
What doesn't work:
GSM/4G does not work, device crashes hard when you try to use the dialer
GCam crashes
So clearly this is pre-alpha and you should not flash it ;-). Will try to fix.
reserved
Has anyone tried this yet?
KashMiester said:
Has anyone tried this yet?
Click to expand...
Click to collapse
Tonight as work blocks downloads
Wow gotta try this out tonight
don't flash, it's not working. I've updated the OP. I'm rebuilding with muppets vendor blobs. Will report back (probably tomorrow as build takes hours and it's already late).
josdehaes said:
don't flash, it's not working. I've updated the OP. I'm rebuilding with muppets vendor blobs. Will report back (probably tomorrow as build takes hours and it's already late).
Click to expand...
Click to collapse
Thanks for the update
It booted but then powers off during setup (right past WIFI password). Seemed fast though
good
Sorry guys, I'm struggling with this. I guess I created this thread (way) too early.
Or it doesn't boot, or it boots, but no GSM and crashes quickly. I continue to learn, hopefully in another 100 attempts I'll have something usable . Are there any people here wanting to help out by testing (most probably broken ) builds? It's difficult for me to keep flashing my only phone (I need it to be working).
I'm now trying with 18.1. Lineage OS does not have a kernel or blobs tree for android 11 for sm8150, but yaap does. Maybe it's a stupid idea, but trying anyway
josdehaes said:
Sorry guys, I'm struggling with this. I guess I created this thread (way) too early.
Or it doesn't boot, or it boots, but no GSM and crashes quickly. I continue to learn, hopefully in another 100 attempts I'll have something usable . Are there any people here wanting to help out by testing (most probably broken ) builds? It's difficult for me to keep flashing my only phone (I need it to be working).
I'm now trying with 18.1. Lineage OS does not have a kernel or blobs tree for android 11 for sm8150, but yaap does. Maybe it's a stupid idea, but trying anyway
Click to expand...
Click to collapse
THREAD CLOSED as placeholders (i.e. threads without a download possibility) are not accepted!
Please advise the moderators team (best via the report function) to re-open your thread when ready to provide a download link.
Please refer to this section of the "Device Forum Rules (Read before posting)":
ROMs, Kernels, Recoveries, & Other Development Section
This section is fexclusively reserved for ROMS, Kernels, Recoveries etc. if they are own development
Try to keep the device forum CLEAN! No offtopic posting and no questions posted in this section/sub-forum.
Use the report button in the lower left corner of an offending post or PM/conversation to let us mods know we need to take action. Don't take matters into your own hands!!!
Sources need to be posted for all kernels!!! Also for all ROMS where license demands it. Refer to post no. 2 above.
You need to use TAGS like [ROM] or [KERNEL] and so on as used in all dev forums throughout XDA (see post no. 4 below).
Any disputes between developers should be handled by PM; try to solve the issue amicably via PM. No public posting in a any thread regarding these matters.
Rom issues should be discussed within their respective threads.
Thread titles should ALWAYS coincide with ROMS ALREADY AVAILABLE FOR DOWNLOAD!!! No advance notification of incoming ROM through thread title. A changelog for the yet unreleased Rom can be included in the OP or in another post CLEARLY MARKED as EXPECTED CHANGELOG.
All threads posted in this section/sub-forum and that are NOT about own ROMS, Kernels, Recoveries etc., or R&D in general will be closed or deleted. Posters that will choose to disregard the previous guidelines will be infracted.
Click to expand...
Click to collapse
I wish you success in getting your ROM running without issues soon. Happy developing.
Stay safe and stay healthy!
Regards
Oswald Boelcke
Forum Moderator