So I really don't know what's going on and what's happening behind the stage.
Obviously alonsoj636 decided to discontinue and abandon his greatly admired LineageOS builds from the past months.
I haven't found any notes or statements as to why he finally has decided to do so and I was not able to reach him on xda because he blocked PMs. If you read this, maybe you want to be so kind and give us some hints what's happened!
Anyway...
we, as the RM10 LineageOS community, have to face reality and that means: currently there is no LineageOS rom build and maintained by anybody. That either means sticking with old versions, changing ROMs/GSI or switching the phone completely.
While alonsoj636's versions are still working very well, they eventually become outdated sometime.
This thread should be used to coordinate discussions about future LineageOS development (if there is enough interest and people).
You have 3 options.
Wait for another builder to pick it up
Build it yourself
Run Lineage GSI from AndyYan (guide here)
One more thing. Building a ROM for a device is never considered a development. What you're referring to, is maintenance. Lineage's development will never stop.
Alright, so the cat is out of the bag on this one:
While I'm really happy that Alonso kept maintaining the ROM for a while, the reality is that he wasn't interested to go official anytime soon and kept being vague about it.
As for me, I'm building up the courage to do MPK99 recommendation and go with GSI. Apparently GSI works like old ROMs, and it doesn't nuke TWRP, so that seems nice.
Try GSI. It's perfect.
MPK99 said:
You have 3 options.
Wait for another builder to pick it up
Build it yourself
Run Lineage GSI from AndyYan (guide here)
One more thing. Building a ROM for a device is never considered a development. What you're referring to, is maintenance. Lineage's development will never stop.
Click to expand...
Click to collapse
I'm pretty aware of that, however all new ROMs are tagged as development on this xda forum so I used this wording.
I think all 3 mentioned options are valid.
I could build it myself, however the time is the problem. Finding someone else building lineage in the future seems to be difficult. The past showed there aren't as many people interested and even less have the time and skill to build it.
GSI sounds like a wonder bag to me. while it's great to always have the latest updates, it might lack of the features LineageOS had for years. (i think of things like os-level online permission per app (wifi/cell), permission center, etc.). you can workaround that with 3rd party tools maybe, but it's cumbersome again.
Also GSi still sounds like a bit of an unpolished OS for this specific phone, with some kind of bugs and lack of features (compared to LOS). it's everybodys own decision to put priority on either that or on latest updates, though.
I might as well give it a try sometime, but I'll need enough spare time for experiments, so it won't happen soon.
my hopes are low, but maybe someone will step up and also build new LOS roms in the future.
Zirila said:
however all new ROMs are tagged as development on this xda forum
Click to expand...
Click to collapse
They're all namesake
Zirila said:
it might lack of the features LineageOS had for years
Click to expand...
Click to collapse
Lineage is lineage whether it's a gsi or a cusrom
Zirila said:
still sounds like a bit of an unpolished OS
Click to expand...
Click to collapse
Those are false claims. You need to use it before committing on it.
Zirila said:
I'll need enough spare time for experiments, so it won't happen soon
Click to expand...
Click to collapse
There's nothing to experiment, as user's experiments are logged on my thread. You can follow them. I'm myself a gsi user for an year long btw. As for the time, it'll take not more than 10 minutes. And I've laid out post configuration & fixes on the thread which'll be another 5 minutes.
well what I meaned with unpolished is what I've red in your thread about bugs like -don't touch screen while booting- etc. I haven't installed it so I solely say that by reading these posts.
and experimenting is synonymous with taking time to clean flash and reinstall everything again while learning and fixing problems with new OS/roms/GSIs.
I'll have a look sometime and I'm grateful there is progress.
Atleast I was transparent about the bugs on it.
Zirila said:
bugs like -don't touch screen while booting
Click to expand...
Click to collapse
Not touching the screen 'while booting' is an easy fix & you won't often reboot your device while work in the first place.
Zirila said:
learning and fixing problems with new OS/roms/GSIs
Click to expand...
Click to collapse
Just the procedure would be new. Rest of it would be your same old preferred AOSP derivative (lineage).
you did well. nothing to complain.
the more I dip into the topic the more I think it might be worth a try. don't count the time till I can focus on it, it'll take a while. but it sounds more and more promissing and the overall experience might as well get even better with time.
regardless of the GSI option, let's still have this thread and discussion opened for the case of some future LineageOS-CustomROM progress.
I'm very sorry for my abrupt decision to kill Lineage.
some personal and family problems made me think that I couldn't continue with this (nothing too big, don't worry... typical family fights)
after some messages I decided to get back to the action.
I will upload a new build with improvements once I unlock my bootloader (not very soon) as my RN10 is my only source of internet and I can't use the Mi Unlock Tool.
Thread will remain locked until the new build is done.
Thank you for your understanding and sorry for my bad steps ....
Regards
Thanks for the informational update
no worry, we are all human. as software engineer and project maintainer in troubled times it's often better to just keep calm, step back for a while, let the projects delay or freeze, that won't really hurt anyone. and then check back later to make a judgement if the project(s) really have to end.
It wasn't that bad for us either, in the meanwhile some of us learned a bit more of the GSI option which might also be a viable way to run LOS in the future. But everything has up- and downsides.
I'm glad we get to see a few more updates for the LOS custom rom.
lineage is alive again
new update is up ... waiting for shadowstep to open the thread again
Changelog
* Switch to SkiaGL Threaded
* Optimize package manager dexopt properties
* Kernel upstreamed to v4.14.295
* Kernel built with Clang 15.0.2
* Enable config_avoidGfxAccel
* wifi: Disable TDLS offchannel
* Disable few debug services
* Don't enable iostats
these are only for LineageOS 19.1
No changes for 18.1
Lineage OS for Mojito - Browse /Lineage at SourceForge.net
LineageOS for Redmi Note 10 (mojito/sunny)
sourceforge.net
Deleted.
Related
So Android P rolled out, and I was wondering, we've been blessed with devs work and got every great update and tons of rom for this device. And was wondering is there by any chance getting Android P based roms in future. Also I was specially wondering about RR, because I like that a rom alot.
Well will we be getting android P, or I shouldn't get my hopes up?
Just wait patiently. The sources are available, just wait until a dev cooks a build for kenzo. Or when proper GSIs will be available.
Sure thing buddy, by any chance you also want VoLTE and 10 hours SOT?
Nobody maintains Kenzo for income, just because they feel like sparing time, for crying out loud it was just formally announced today, so if you want P go ahead and build it on your own.
Just stop this kind of threads, they are just spam.
BusterBg_18 said:
Sure thing buddy, by any chance you also want VoLTE and 10 hours SOT?
Nobody maintains Kenzo for income, just because they feel like sparing time, for crying out loud it was just formally announced today, so if you want P go ahead and build it on your own.
Just stop this kind of threads, they are just spam.
Click to expand...
Click to collapse
Could like please take your hate and get the hell out of this thread.
Like seriously, I'm just genuinely asking a question, so its not a spam, and I asked BECAUSE P came out today. If you don't wanna answer just ignore this, not a hard thing to do.
-shashankpatel- said:
Could like please take your hate and get the hell out of this thread.
Like seriously, I'm just genuinely asking a question, so its not a spam, and I asked BECAUSE P came out today. If you don't wanna answer just ignore this, not a hard thing to do.
Click to expand...
Click to collapse
Sorry, the devs need income and now the devs like @rocknegi have started p**n for ₹50/day or ₹200/month cause the users aren't donating enough money.
If they get enough income from p**n selling, they will develop Android P for you.
Daruwalla said:
Sorry, the devs need income and now the devs like @rocknegi have started p**n for ₹50/day or ₹200/month cause the users aren't donating enough money.
If they get enough income from p**n selling, they will develop Android P for you.
Click to expand...
Click to collapse
Yeah I saw that as well. Look I just wanted to know of there was a possibility of kenzo getting a p, coz yk, this is pretty old device.
-shashankpatel- said:
Yeah I saw that as well. Look I just wanted to know of there was a possibility of kenzo getting a p, coz yk, this is pretty old device.
Click to expand...
Click to collapse
I know but just use some sense? We are not devs, we are normal users like you. How do we all users know if a dev can develop Android P. Plus, do you think a dev will announce 'Hey Niggas, I'll develop Android P rom for you all niggas asking for it, wait for few hours:. No?
The dev need to look into the source, need time to see what all bugs needs to be fixed, else users like you will come here and say it's buggy, that doesn't work, this doesn't work right?
Another sensible answer: Android P sources are just released. It's not like magic to develop rom directly from the source. Needs a lot of hack, back port blobs and things we don't even understand.
Summary: it's a redundant question as of now. Please wait, if there's a Android P rom, you will see it here. Till than, enjoy other roms.
Daruwalla said:
Sorry, the devs need income and now the devs like @rocknegi have started p**n for ₹50/day or ₹200/month cause the users aren't donating enough money.
If they get enough income from p**n selling, they will develop Android P for you.
Click to expand...
Click to collapse
Disaster! Time to join negi ?
Nick_gunale said:
Disaster! Time to join negi
Click to expand...
Click to collapse
Free p**n sites aren't enough for you? ?
Daruwalla said:
Free p**n sites aren't enough for you?
Click to expand...
Click to collapse
need income lol
As a user of redmi note 3 . i just hope dev make android p for this device.
As one of the lineage 15.1 maker for Redmi Note 3, yep, we will do bringup after 9.0 source code release, and should be easier than Oreo, as Pie impacted a lot of backport comparable, please don't ask lots of annoying OTA, follow XDA rule, P will be coming to Kenzo/Kate after sometimes, but for Treble is more harder as blobs are old, we need to wait hydrogen and suzu devices etc updates for new blobs, for more Treble working, and even CAF for msm8952 board not impacted treble, unlike msm8953 board, so treble now is experimental and don't expect stable treble in a short time.
---------- Post added at 03:58 PM ---------- Previous post was at 03:56 PM ----------
And for my lineage 15.1 long time no updates because I teams with @Carlos Arriaga, and he is back in July so I and other team members need to do some updates, my 15.1 new build will release soon
LokManSiu said:
As one of the lineage 15.1 maker for Redmi Note 3, yep, we will do bringup after 9.0 source code release, and should be easier than Oreo, as Pie impacted a lot of backport comparable, please don't ask lots of annoying OTA, follow XDA rule, P will be coming to Kenzo/Kate after sometimes, but for Treble is more harder as blobs are old, we need to wait hydrogen and suzu devices etc updates for new blobs, for more Treble working, and even CAF for msm8952 board not impacted treble, unlike msm8953 board, so treble now is experimental and don't expect stable treble in a short time.
Click to expand...
Click to collapse
Thanks for this reply. Won't be asking for annoying updates, just wanted to know that is all.
Well, speaking of Android Pie development, I've found a Pixel Experience ROM that is based on Android Pie through a Telegram channel
Known broken features:
• Bluetooth
• VoLTE
• Stock camera app, but the camera works for stills and video (Open Camera)
(link: http://t.me/TheStrechh) t.me/TheStrechh (the author)
(link: http://t.me/KenzoRoms_News) t.me/KenzoRoms_News
(link: http://t.me/kenzoromnews) t.me/kenzoromnews
NOTA BENE: Try it at your own risk, as it is not developed by me, but if you want to download it and try it, here's the link: https://drive.google.com/open?id=1KqyUEdUgtW5coyoTlHuuN0Y2Jt1aKnn-
Yep. I've been using the Pixel Experience 9.0 from @thestrechh as my daily driver for a couple days now.
It's usable if you can get by without VoLTE and Bluetooth.
Gcam works, but can't change the settings and it crashes a lot. Front and back camera stills and video all working.
The rom feels pretty buggy and a bit sluggish to me. CPU operations seem to take an unusually long time. Maybe all the cores are not being utilized optimally. (Don't know. I haven't actually tested.)
I'm sure this rom will continue to get better and better in the coming days. I'm anxious to dirty flash the coming updates.
Excellent work by @thestrechh.
kazekiri said:
Yep. I've been using the Pixel Experience 9.0 from @thestrechh as my daily driver for a couple days now.
It's usable if you can get by without VoLTE and Bluetooth.
Gcam works, but can't change the settings and it crashes a lot. Front and back camera stills and video all working.
The rom feels pretty buggy and a bit sluggish to me. CPU operations seem to take an unusually long time. Maybe all the cores are not being utilized optimally. (Don't know. I haven't actually tested.)
I'm sure this rom will continue to get better and better in the coming days. I'm anxious to dirty flash the coming updates.
Excellent work by @thestrechh.
Click to expand...
Click to collapse
I've not noticed sluggish performance here, but I have noticed bugs here and there, which is par for the course, considering the infantile state of Android Pie development.
Still though, for an early release, it works almost excellently
aha360 said:
I've not noticed sluggish performance here, but I have noticed bugs here and there, which is par for the course, considering the infantile state of Android Pie development.
Still though, for an early release, it works almost excellently
Click to expand...
Click to collapse
I decided to do a benchmark with antutu. The score seems fine. Guess I must be mistaken.
kazekiri said:
I decided to do a benchmark with antutu. The score seems fine. Guess I must be mistaken.
Click to expand...
Click to collapse
It happens. Either way though, the coming weeks will be interesting in terms of Android Pie ROM development
The bug of battery drain in standby (mobile network) apear in Android PIE like Oreo?
Can you share battery stats?
Thanks
aha360 said:
I've not noticed slugogish performance here, but I have noticed bugs here and there, which is par for the course, considering the infantile state of Android Pie development.
Still though, for an early release, it works almost excellently
Click to expand...
Click to collapse
did you have the Pixel Setup crashing after flashing this rom? if you do, what's the solution?
Wear 24 DevelopmentContributors: @JaredTamana, @davwheat
Current Status: ActiveCurrent Kernel Status: Building, NFC driver working but still potentially WIPSystem ROM Status: Still WIP. Current task: collecting/compiling files, modifying .jarsTHIS ROM IS NOT YET AVAILABLE TO DOWNLOAD AS AN END-USER ROM
This project has a few goals:
- Bringing NFC/Google Pay support to Wear24 [Feasible, main goal]
- Bringing system updates to the Wear24, ie System H [Probably doable, second goal]
- Adding/fixing functionality in the Wear24 (such as new radio bands, no cloud icon, etc) [Maybe possible but needs more research, low on the list)
- Other projects are being considered for the Wear24, but no news on them at this time.
Links
Social
Wear24Dev Blog, periodic updates on this project: http://wear24dev.blogspot.com
Wear24 NFC Discord, open chat so users can see us develop in real-time! Also, tech support. https://discord.gg/8XyTeUC
Development
Wear24-NFC-Kernel GitHub, this is our source for building the kernel. Instructions for building it yourself are in the README. https://github.com/davwheat/Wear24-NFC-Kernel
Travis-CI Build Logs for Kernel: https://travis-ci.org/davwheat/Wear24-NFC-Kernel
Wear24-NFC-ROM GitHub, will soon contain the files needed to make an image/zip, depending on how we decide to distribute. https://github.com/davwheat/Wear24-NFC-ROM
JaredTamana's GDrive dorado folder, may contain files you need: https://drive.google.com/drive/folders/1h6gz-oLMPZ90nwt7BLhWVgHii1DRCW5c
davwheat's GDrive dorado folder, may contain files you need: https://drive.google.com/drive/fold...droid-msm-dorado-3.18-nougat-mr1-wear-release
tetra release for enabling NFC: https://forum.xda-developers.com/sm...ony-smartwatch-3-nfc-support-package-t3219713
NXP Setup Guidelines: https://github.com/NXPNFCProject/NF...r/AN11762-Android_NXP_NFC_Setup_Guideline.pdf
Special Thanks
janjan: Dev guidance
@bensdeals: Donor, help
@yochanmarquos, u/lerxi: Development help.
-- RESERVED -- Because you never know
Someone should have a TWRP backup handy with the images you are looking for. Correct me if I'm wrong, but all the images you require are inside a TWRP backup image.
Anyone remember that Sony SW3 port thread? I'm not sure what happened to the project, but dev seems quiet and the device tree repos are gone. Was hoping to use those as a resource and it wasn't crawled by archive.org. Wonder if external forces got involved, which makes me a bit worried. If anyone has a clone of that repo, it might be really useful.
Please. I beg you to make this happen. Thanks for even trying
I'm definitely interested in this. If I knew I could get Google Pay working on this device, I would definitely buy one. I'll happily throw a few dollars your way too, if you can release something that works.
Hoping I found it
JaredTamana said:
Anyone remember that Sony SW3 port thread? I'm not sure what happened to the project, but dev seems quiet and the device tree repos are gone. Was hoping to use those as a resource and it wasn't crawled by archive.org. Wonder if external forces got involved, which makes me a bit worried. If anyone has a clone of that repo, it might be really useful.
Click to expand...
Click to collapse
Is this what you're looking for? (Sorry, I'm not allowed to post url yet so just remove space before .com)
github .com/FlorentRevest/android_device_sony_tetra
My Wear24 just came in from eBay . It's a really good looking device. I might be able to help you test at some stage. Also willing to donate ducats if you get far enough. Good Luck :good:
I got my wear24 a few months ago, and was slightly disappointed to find out about the lack of root, customization, etc. I'm still not a huge fan of opening it up, but I'm up for helping any other way I can!
YTSec said:
I got my wear24 a few months ago, and was slightly disappointed to find out about the lack of root, customization, etc. I'm still not a huge fan of opening it up, but I'm up for helping any other way I can!
Click to expand...
Click to collapse
I appreciate the thought, but doing anything in the vein of system modification will require opening the watch. Luckily, the pinout is right under the back cover, so chances of damaging the watch are minimal. If you change your mind, let me know.
** NEWS **
Semi-daily updates will be going on this Blogger Page so I don't clog up the thread
http://wear24dev.blogspot.com
Hi, can i flash this rom to zte quartz 2017?
Hi, can i flash this rom to zte quartz 2017?
Eshal said:
Hi, can i flash this rom to zte quartz 2017?
Click to expand...
Click to collapse
Eshal, this ROM hasn't even been built yet. I cannot guarantee compatibility with your device because I'm not building for your device. You can try flashing whatever you like, but I'm not liable for your device.
This ROM is still in its first steps and I quite literally have nothing to release yet. I've just finished bringing backups over to my PC.
JaredTamana said:
I appreciate the thought, but doing anything in the vein of system modification will require opening the watch. Luckily, the pinout is right under the back cover, so chances of damaging the watch are minimal. If you change your mind, let me know.
Click to expand...
Click to collapse
I took a look, it's not as bad as I thought. Its probably worth unlocking the bootloader anyway! I'll let you know tomorrow if I do.
YTSec said:
I took a look, it's not as bad as I thought. Its probably worth unlocking the bootloader anyway! I'll let you know tomorrow if I do.
Click to expand...
Click to collapse
Glad to hear it! Make sure to read the main thread as to tips on how to do it. Use lots of heat, and don't forget the Y000 (0.6) screwdriver.
Kernel builds are now passing, and I've begun debugging the boot process. More info on the Blogspot
Sorry for the late reply, I'm just waiting on a toolkit that works on it, then I'll start ripping it apart to help out! Also, I got that new UI which is great.
How goes the testing? I've noticed that there haven't been any new posts on the blog or on this thread. Hope everything is well
@JaredTamana Have you seen this? BLOCKS announces Project OpenWatch: an Android Oreo-based OS for smartwatches in collaboration with CarbonROM and LineageOS
Here's their GitHub.
VlitalityX said:
How goes the testing? I've noticed that there haven't been any new posts on the blog or on this thread. Hope everything is well
Click to expand...
Click to collapse
Hiya! Sorry for the lack of updates. I've hit a wall with that Binder error. All documentation online seems to be about x86 machines and ranges from IO errors to SELinux errors. I've already tried compiling without SELinux in a few different ways to no avail. I've tried contacting development channels on IRC, but no one seems to have the answers I need (most times I don't even get a reply...)
I'm still brainstorming. I took a look at the kmsg from the stock build and there's a LOT being sent to logs there that isn't from my kernel. I'm not sure where to go next, and I don't want to go knocking on the door of every single developer that might know the answer. The problem is the Binder errors are so vague about what's causing the failed transaction that I can't even start to understand what's wrong.
yochananmarqos said:
@JaredTamana Have you seen this? BLOCKS announces Project OpenWatch: an Android Oreo-based OS for smartwatches in collaboration with CarbonROM and LineageOS
Here's their GitHub.
Click to expand...
Click to collapse
Thanks! I do remember seeing this. Problem is, if I can't even build a stock kernel, nothing else can be done. I need the device booting first before I can move to system changes.
MOD EDIT: Prepayment type fundraisers are not allowed on this site
Just donated, would love to see this rom!
Funding update, Since a lot of people in group have shown interest in paypal info instead of going thru funding site Ill provide info and ammount collected in this post
as of right now we are sitting at 500/550 euros
(Actually even closer as ill add my money and try to find cheapest available device (Going for s10 as it has all of the features that might show up to be messier to implement than on s10e))
Paypal you can use to donate is <Mod Removed>
If you donated and want a refund feel free to conact me in PM, This post will be updated few times per day to reflect new ammount collected
As a little background i worked on exynos devices since 2014 starting with note 2, As of right now I'm maintaining s7 and s8 series of devices, I am also a member of LineageOS so once everything works as expected it shouldnt take too long for device to recieve official builds.
if you have any questions feel free to ask me either here in telegram or via PM
Once moeny is collected donation links will be removed
Why? FYI the s10 can run lineage already. simply install the Univeral system image build
The S10 is fully compatible with treble 2, literally just install any GSI Rom, including Google's official Android Q Beta for GSI
Be aware the camera is total crap though, its like taking pictures from messenger / whatsapp.
This is a thing since the S9.
https://developer.android.com/preview/gsi-release-notes
https://forum.xda-developers.com/pr...i-lineageos-16-0-gsi-arm64-ab-how-to-t3908029
The phone is treble ready.
Unless you are starting from scratch I don't see this require.
TheUndertaker21 said:
The phone is treble ready.
Unless you are starting from scratch I don't see this require.
Click to expand...
Click to collapse
Even though it is Treble ready, I doubt it will be daily driver ready, some form of development is required.
Really looking forward to getting LOS, I am starting to get bored with my S10e
opssemnik said:
Why? FYI the s10 can run lineage already. simply install the Univeral system image build
The S10 is fully compatible with treble 2, literally just install any GSI Rom, including Google's official Android Q Beta for GSI
Be aware the camera is total crap though, its like taking pictures from messenger / whatsapp.
This is a thing since the S9.
https://developer.android.com/preview/gsi-release-notes
https://forum.xda-developers.com/pr...i-lineageos-16-0-gsi-arm64-ab-how-to-t3908029
Click to expand...
Click to collapse
What magical GSI are you talking about? Have you even tried GSIs on S10? It doesn't work any good. Lots of major bugs. That won't magically fix itself. If Ivan can help if people donate device, and people want to donate, let this be.
opssemnik said:
Why? FYI the s10 can run lineage already. simply install the Univeral system image build
The S10 is fully compatible with treble 2, literally just install any GSI Rom, including Google's official Android Q Beta for GSI
Be aware the camera is total crap though, its like taking pictures from messenger / whatsapp.
This is a thing since the S9.
https://developer.android.com/preview/gsi-release-notes
https://forum.xda-developers.com/pr...i-lineageos-16-0-gsi-arm64-ab-how-to-t3908029
Click to expand...
Click to collapse
The current state of gsis is not daily driver ready
Bugs: MTP, Proximity sensor, Signal bars, Bluetooth, NFC, HWC, deep sleep, Fingerprint, brightness range, auto brightness
Having a device specific rom is always better
Still no luck in booting Q gsi - any advices?
you can get some s10 on swappa for cheap unless you really want new
TheUndertaker21 said:
you can get some s10 on swappa for cheap unless you really want new
Click to expand...
Click to collapse
Swappa doesnt even work in EEA and those are used prices in most of eu, actually cheapest we've found
Hope something can be done with snapdragon as well
malinathani said:
The current state of gsis is not daily driver ready
Bugs: MTP, Proximity sensor, Signal bars, Bluetooth, NFC, HWC, deep sleep, Fingerprint, brightness range, auto brightness
Having a device specific rom is always better
Click to expand...
Click to collapse
Those bugs were probably due to the specific rom you were using, as HWC in aosp gsi is literally mandatory for google to certify the device. Its on the list of treble requirements even
https://android.googlesource.com/pl...6d53f727d53d232dca503bbbc6d6f7854d8/README.md
Dont get me wrong, i still appreciate decice specific roms(mostly for kernel), just wanted to make people aware really
Good luck
opssemnik said:
Those bugs were probably due to the specific rom you were using, as HWC in aosp gsi is literally mandatory for google to certify the device. Its on the list of treble requirements even
https://android.googlesource.com/pl...6d53f727d53d232dca503bbbc6d6f7854d8/README.md
Dont get me wrong, i still appreciate decice specific roms(mostly for kernel), just wanted to make people aware really
Good luck
Click to expand...
Click to collapse
Can you show us that it actually works on our devices? I have heard the same as others and am curious.
kevkid said:
Can you show us that it actually works on our devices? I have heard the same as others and am curious.
Click to expand...
Click to collapse
it doesn't work, it didn't work properly since pie on s9 either sure it will show up as working in logs (dumpsys SurfaceFlinger) but anyone who tried using it will notice graphical glitches in transition animations, due to samsungs messed up implementation of dealing with fences in hwc2 (they treat it same way as hwc1 fences) but i guess some people would rather be stubborn than do some research, furthermore he should know big oems get exempt from some tests sometimes, take for example a fact previously samsung had completely different fingerprint enrolling percentage calculation so fingerprint couldn't be enrolled by default you either had to use custom hal (like we did at lineage) or hack up system like phh did
opssemnik said:
Those bugs were probably due to the specific rom you were using, as HWC in aosp gsi is literally mandatory for google to certify the device. Its on the list of treble requirements even
https://android.googlesource.com/pl...6d53f727d53d232dca503bbbc6d6f7854d8/README.md
Dont get me wrong, i still appreciate decice specific roms(mostly for kernel), just wanted to make people aware really
Good luck
Click to expand...
Click to collapse
I've tried 3 gsis till now and i can confirm its not a rom specific bug.
And Samsung doesn't fully follow the rules set by google
I would really suggest you to try a gsi yourself if you're thinking it's something usable in its current state.
Was there ever a stable build for the S8? Last I remember a lot was still broken. (It's been awhile)
---------- Post added at 03:56 PM ---------- Previous post was at 03:40 PM ----------
FlatOutRU said:
Hope something can be done with snapdragon as well
Click to expand...
Click to collapse
Yeah, i'd contribute if they had 97x0 support.
Fznwolf said:
Was there ever a stable build for the S8? Last I remember a lot was still broken. (It's been awhile)
---------- Post added at 03:56 PM ---------- Previous post was at 03:40 PM ----------
Yeah, i'd contribute if they had 97x0 support.
Click to expand...
Click to collapse
Yeah s8 has stable lineage right now, Well next update will bring even more things to it, Previous maintainer didnt do much, Also i personaly dont have plans of working on qcom variants as stated previously as i enjoy working on exynos more and have a lot of experience with it so i would leave qcom to someone else as it should also be way easier
san_099 said:
Even though it is Treble ready, I doubt it will be daily driver ready, some form of development is required.
Really looking forward to getting LOS, I am starting to get bored with my S10e
Click to expand...
Click to collapse
How could you be bored of oneui and the themeing and all the other things you have on stock... i think your just curious to have linage os running on your phone you mean because all youll find is poor battery and performance and a poor camera and over heating issues then youll be back to stock in no time....then ull get curious again when something else comes up and youll do it all over again then keep repeating lol...past experience for me haha thats y i dont even root now days...was talking about myself in that rant btw.
Thread closed
Apologies but no prepayment fundraisers are allowed on XDA
We barely tolerate Bounty threads and they have VERY strict guidelines
Thank you all for your understanding
OnePlus has numerous models (like my Nord N10) that are still waiting for Android 11. Other models have beta versions of Android 12, but OnePlus has wholly and completely botched their rollout of Android 11.
I'm sure that THOUSANDS of OnePlus users would gladly pay for a stable ROM.
Would love to see Pixel Experience or Lineage take the lead on this!
mkeaton1967 said:
OnePlus has numerous models (like my Nord N10) that are still waiting for Android 11. Other models have beta versions of Android 12, but OnePlus has wholly and completely botched their rollout of Android 11.
I'm sure that THOUSANDS of OnePlus users would gladly pay for a stable ROM.
Would love to see Pixel Experience or Lineage take the lead on this!
Click to expand...
Click to collapse
No doubt mate, I would definitely pay for a Lineage ROM...
I mean, I even contacted the OP support team showing them how pissed and disappointed I am due to the lack of OxygenOS support for the N10, but they answered with a completely generic and useless email...
However, there's already a Pixel Experience ROM for OP N10: https://download.pixelexperience.org/billie
But I dunno, isn't Pixel Experience way more Google-dependent than OxygenOS? I usually avoid Google stuff.
EDIT: Well yea, I just noticed that ROM was discontinued, my bad.
lbsilva said:
No doubt mate, I would definitely pay for a Lineage ROM...
I mean, I even contacted the OP support team showing them how pissed and disappointed I am due to the lack of OxygenOS support for the N10, but they answered with a completely generic and useless email...
However, there's already a Pixel Experience ROM for OP N10: https://download.pixelexperience.org/billie
But I dunno, isn't Pixel Experience way more Google-dependent than OxygenOS? I usually avoid Google stuff.
EDIT: Well yea, I just noticed that ROM was discontinued, my bad.
Click to expand...
Click to collapse
Appreciate your feedback. It’s a chicken or the egg conundrum.
I’ve shared feedback directly with both Lineage and Pixel Exp that there is an opportunity here. Some twerp moderating the Lineage forum (not a developer) sent me a grumpy reply saying “read the forum rules you can’t ask for a ROM for your phone”. I explained to the dummy that I’m not talking about just my phone, rather it is a huge opportunity for nearly every model of OnePlus phones.
We need to help folks at Lineage or Pixel Exp understand that yes these custom ROM projects are things they work on for fun — but that they are also supported thru DONATIONS. So, consider developing ROMs for models where there are known customer dissatisfaction issues. Maybe even require a minimum donation of $15 or $25 if you have published a stable ROM that you are committed to for ongoing support.
mkeaton1967 said:
Appreciate your feedback. It’s a chicken or the egg conundrum.
I’ve shared feedback directly with both Lineage and Pixel Exp that there is an opportunity here. Some twerp moderating the Lineage forum (not a developer) sent me a grumpy reply saying “read the forum rules you can’t ask for a ROM for your phone”. I explained to the dummy that I’m not talking about just my phone, rather it is a huge opportunity for nearly every model of OnePlus phones.
We need to help folks at Lineage or Pixel Exp understand that yes these custom ROM projects are things they work on for fun — but that they are also supported thru DONATIONS. So, consider developing ROMs for models where there are known customer dissatisfaction issues. Maybe even require a minimum donation of $15 or $25 if you have published a stable ROM that you are committed to for ongoing support.
Click to expand...
Click to collapse
I think many developers build and develop custom ROMs in order to practice or just to have fun, not for money. What I think you're proposing is turning what is a fun hobby for many of the developers into a sort of job, which I think is a little unreasonable. This is probably the point where most developers would stop having fun and cease development altogether. I think letting developers pick whatever devices they want to develop for would be for the best. The only thing we can do is wait or send a device their way in hopes that they pick up development. Also, there are already Pixel Experience and LineageOS ROMs for the N10(I'm using Pixel Experience right now and it's pretty stable). If you're feeling extra adventurous, there is a guide to flash GSIs from the GitHub Wiki here.
Generic123. said:
I think many developers build and develop custom ROMs in order to practice or just to have fun, not for money. What I think you're proposing is turning what is a fun hobby for many of the developers into a sort of job, which I think is a little unreasonable. This is probably the point where most developers would stop having fun and cease development altogether. I think letting developers pick whatever devices they want to develop for would be for the best. The only thing we can do is wait or send a device their way in hopes that they pick up development. Also, there are already Pixel Experience and LineageOS ROMs for the N10(I'm using Pixel Experience right now and it's pretty stable). If you're feeling extra adventurous, there is a guide to flash GSIs from the GitHub Wiki here.
Click to expand...
Click to collapse
Thanks for sharing your point of view. Agreed 100% that these are volunteers who don’t do it for money. Just pointing out that there’s an opportunity for both because of how OnePlus has handled the rollout of Android 11. The OnePlus 9 is part of the Android 12 Beta, but the N10 and other models are still waiting for Android 11.
My goal is just to create awareness of an issue. Given that most custom ROM developers focus on a couple of phone models, they might not be aware of the issues that OnePlus has had. Someone can still be a custom ROM developer on the side for the fun of it, but at the same time pick devices where there is a need. It might increase donations — a way to subsidize the fun.
I held off on installing Pixel or Lineage on my N10 because both mention issues with adaptive brightness — didn’t know if that meant that brightness was randomly changing or if that means it just doesn’t adapt and stays at whatever you have it set on.
mkeaton1967 said:
Thanks for sharing your point of view. Agreed 100% that these are volunteers who don’t do it for money. Just pointing out that there’s an opportunity for both because of how OnePlus has handled the rollout of Android 11. The OnePlus 9 is part of the Android 12 Beta, but the N10 and other models are still waiting for Android 11.
My goal is just to create awareness of an issue. Given that most custom ROM developers focus on a couple of phone models, they might not be aware of the issues that OnePlus has had. Someone can still be a custom ROM developer on the side for the fun of it, but at the same time pick devices where there is a need. It might increase donations — a way to subsidize the fun.
I held off on installing Pixel or Lineage on my N10 because both mention issues with adaptive brightness — didn’t know if that meant that brightness was randomly changing or if that means it just doesn’t adapt and stays at whatever you have it set on.
Click to expand...
Click to collapse
Thanks for the calm discussion. From your perspective, I can see how looking at all of these OnePlus devices and their lack of recent updates has created a huge void that could be easily filled with custom ROMs. The N10 is no exception; only 1 major android update and that's it, which is obviously a big bummer. I think some developers are aware, but might just be waiting for the "promised" updates to actually occur, slow as they are. I personally think the slow deveopment progress of the N10 relative to other OnePlus devices is most likely because this phone is on the more boring side, and most people have marked it off as budget garbage. Concerning Pixel and Lineage: auto brightness just doesn't work at all, and other than DT2W , both are pretty stable(as indicated by my last post).
I love you both
Hi,
I am wondering if there is a common way on this forum to express support for the development of a specific custom ROM for a phone? Is there a commonly accepted way to do this? (Came here to see if I could +1 a LineageOs thread for the Zenfone 9)
Rik
bump
rainyskye said:
bump
Click to expand...
Click to collapse
haha is this a +1 of my wish to be able to give a +1 ?
Hey mate,
I was thinking to contact developers and pay them to build lineage OS and make it official!
Or the other alternative is Learn how to build it and submit it for review on LOS website..
If you have any suggestions?
cool, no idea how to go about that, but I would be happy to contribute as well. I'm sure others would be too - I am on a forum where there are multiple threads dedicated to finding a good small deGoogled phone (community.e.foundation). There must be a place where people can put up amounts for a development like this, right? Sort of like a Kickstarter for a bit of development? I will ask on the other forum too
Rik44444 said:
cool, no idea how to go about that, but I would be happy to contribute as well. I'm sure others would be too - I am on a forum where there are multiple threads dedicated to finding a good small deGoogled phone (community.e.foundation). There must be a place where people can put up amounts for a development like this, right? Sort of like a Kickstarter for a bit of development? I will ask on the other forum too
Click to expand...
Click to collapse
The problem with LineageOS is that when there is no more maintainer for a specific model the phone just goes to rubbish, no more security patch... same for the other custom rom... eOS depends on LOS repositories and even if lineage stop supporting a specific device eOS will keep updating their all supported devices... That's why I really like eOS. It doesn't matter if some features are unavailable... a phone is supposed to be used for call, text. Nowadays, everything seems to be sophisticated however it doesn't need to be... I'll start asking some recognised developers if they are willing to work on a LOS build for the zf9 for some money participation... maybe start a crowdfunding of an alternative without fraud!!
Bump
Hi bro,
Sorry got no time at the moment I ended up using a one plus 6 with eOS... I haven't started anything yet. I might need some help to organise something about crowdfunding..
Good luck and let us know if you have some ideas. Thank's