{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PixelExperience for OnePlus8T[kebab]
What is this?
PixelExperience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, boot animation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 12.1
Whats working?
Wi-Fi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
FM radio
Fingerprint reader
Face unlock
NFC
Lights
Sound/vibration
Known issues
You tell me
DON'T FLASH GAPPS, THEY'RE ALREADY INCLUDED
Download from PixelExperience website
Donate
[*]UPI-ID:- [email protected]
[*]Paypal:- paypal.me/KakatkarAkshay
Translation
Help with project translation
Stay tuned
Our Telegram channel
Device Specified Telegram Group
Our blog
Android OS version: 12.1.0_r2
Security patch level: March 2022
Build author/Device Maintainer: Rohan Hasabe
Device Source code: https://github.com/PixelExperience-Devices
Kernel Source code: https://github.com/PixelExperience-Devices/kernel_oneplus_sm8250
Source code: https://github.com/PixelExperience
ROM Developer: jhenrique09
Reserved
Reserved
With the abomination that OOS12 is, I am now eager to switch to a custom ROM more than I was before. I will be definitely giving this ROM a try. Perfect timing! Will flash this week.
I can't se the latest build on website
Does Google Now Playing work?
So I haven't installed a custom rom in ages, I used the pixel experience instructions and everything seemed to go well, I tried to relock the device, but it wouldn't boot after it just keep taking back to the bootloader after telling me I had installed a rom (I don't recall exactly what it said), so I unlocked it again and it booted fine, I just assumed it was because I'm using a tmobile 8T+. the only issue I have at the moment is that it's forcing me to setup face unlock, I have absolutely no desire to do that, is there a way around this? it looks like I'll have to set it up to get passed the initial setup and I'm very unpleased about that, but it is what it is.
I'm going to go through with it, but I'm curious if there is a way to, not have to do it in the first place.
If anyone knows, I'd appreciate any tips or advice. thanks!
Edit: Ok, I've tried several ways to setup my phone and all of the force the use of facial unlock and it won't recognize my face so I'm going to try something else. It also told me that my phone was a pixel 6 pro, so that wasn't what I was expecting, I was under the impression from everything i've read that this rom was more of a AOSP made pixel and now I'm thinking it's a pixel rom made AOSPish.
I appriciate the effort, unfortunately it's not for me.
pro_granade said:
Does Google Now Playing work?
Click to expand...
Click to collapse
It doesn't, that's the only true "pixel only" feature
houstontaxi said:
I can't se the latest build on website
Click to expand...
Click to collapse
It's up right now
bookofjoshua said:
So I haven't installed a custom rom in ages, I used the pixel experience instructions and everything seemed to go well, I tried to relock the device, but it wouldn't boot after it just keep taking back to the bootloader after telling me I had installed a rom (I don't recall exactly what it said), so I unlocked it again and it booted fine, I just assumed it was because I'm using a tmobile 8T+. the only issue I have at the moment is that it's forcing me to setup face unlock, I have absolutely no desire to do that, is there a way around this? it looks like I'll have to set it up to get passed the initial setup and I'm very unpleased about that, but it is what it is.
I'm going to go through with it, but I'm curious if there is a way to, not have to do it in the first place.
If anyone knows, I'd appreciate any tips or advice. thanks!
Edit: Ok, I've tried several ways to setup my phone and all of the force the use of facial unlock and it won't recognize my face so I'm going to try something else. It also told me that my phone was a pixel 6 pro, so that wasn't what I was expecting, I was under the impression from everything i've read that this rom was more of a AOSP made pixel and now I'm thinking it's a pixel rom made AOSPish.
I appriciate the effort, unfortunately it's not for me.
Click to expand...
Click to collapse
It's a standard setup procedure even on stock Pixel phones.. You could just ignore any security input during setup, and then just add fingerprint in the settings after the system boot....
Has anyone already determined whether this OS based on A12.1 also has an increased power consumption when using the device?
I first noticed this with the pixel blaster and then with project zepyurus. The device is always warm and the battery is drained properly. However, it only loses 3-5% during overnight standby.
I flashed this rom today!
So far feels very good. I love it.
Question: If there is an new update, can i update inside the rom or must i reflash the new update?
nitroax said:
It's a standard setup procedure even on stock Pixel phones.. You could just ignore any security input during setup, and then just add fingerprint in the settings after the system boot....
Click to expand...
Click to collapse
there wasn't any option to bypass it, it only showed "try again" and "cancel". my last pixel was a 2xl and it didn't force me to add any security. this one forced me to add a pin and then went directly into the face id. I couldn't find any way get arround it, I tried copy from old phone, and setup as a new device and it was the same every time.
bookofjoshua said:
there wasn't any option to bypass it, it only showed "try again" and "cancel". my last pixel was a 2xl and it didn't force me to add any security. this one forced me to add a pin and then went directly into the face id. I couldn't find any way get arround it, I tried copy from old phone, and setup as a new device and it was the same every time.
Click to expand...
Click to collapse
hmm that's odd because i flashed feb build (that had faceunlock) and when it asked me for pin first, i just ignored it and got direct to system.
Is this build online? I think it got removed smh
Seems not online, when I click on the link it says error no file found, anyway if it's ready for download the dev will post the link, so we have to wait patiently
Yeah, the link went down, not sure why. I've asked @RohanHasabe8 on Telegram about an issue which I'm experiencing when trying to open network tab (WiFi/LTE) in the settings app (the app is crashing), but I haven't received a response.
Another issue that I've experienced on a new 12.1 build is that battery consumption is much higher than on a build from February.
To be fair with 12 build I had only one issue - with automatic brightness, it wasn't working perfectly - especially when I was using dark mode mainly and the app which had a white theme was opened at night and a screen went full brightness.
nitroax said:
hmm that's odd because i flashed feb build (that had faceunlock) and when it asked me for pin first, i just ignored it and got direct to system.
Click to expand...
Click to collapse
I'll try again to be sure. I started setup and I set the wifi, then agreed to the location etc, and the it aaked to set up backup (not sure if it did that when I set it up as a new device) then it went straight to set a PIN and there wasn't anything except the key pad, no option to skip, if I hit ->| button with out putting in a PIN it just sat there. No 2ay past it.
bookofjoshua said:
I'll try again to be sure. I started setup and I set the wifi, then agreed to the location etc, and the it aaked to set up backup (not sure if it did that when I set it up as a new device) then it went straight to set a PIN and there wasn't anything except the key pad, no option to skip, if I hit ->| button with out putting in a PIN it just sat there. No 2ay past it.
Click to expand...
Click to collapse
I mean this ,right after backup restore
nitroax said:
View attachment 5573927
I mean this ,right after backup restore
Click to expand...
Click to collapse
As I said there wasn't a skip option. I looked for it. But I'll try again.
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 10 (Q), which is designed to increase performance and reliability over stock Android for your device. LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github Repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
Screenshots here
Flashing Instructions:
Pre-installation & other downloads:
OrangeFox R11.0 (it's MANDATORY) - Download from here
Repartition script - Download from here
GApps: ARM64 > 10 > Pico - Download from here
Magisk 21.4 or newer for root - Download from here
Installation:
Enter to recovery mode and make a backup of your EFS & Modem (recommend).
Go to the Files tab and flash "LOS17.1-Repartitioner-exynos7870.zip". The recovery will auto-reboot.
Now, go to the Trash Bin and then go to the "Format data" tab, type "yes" and the tick to format data.
Go to the Wipe tab, select SYSTEM, CACHE, DALVIK, VENDOR, DATA and INTERNAL STORAGE, then swipe the bar.
Install the lineage-17.1-xx-UNOFFICIAL-j7xelte.zip
Install the GApps zip
Install Magisk (optional)
Reboot and wait. Without GApps, it boot in 15s. With Pico GApps, it boot on 1min 5s.
Done!
Download:
ROM: https://www.androidfilehost.com/?fid=17248734326145727245
Known issues:
- Frontal camera stretched for some apps (Instagram, Snapchat & Whatsapp don't have this problem). See second post for more info.
- LineageOS LiveDisplay
- Frontal Flash
- Bluetooth Calls
- VoLTE
Sources:
Kernel: github.com/samsungexynos7870/android_kernel_samsung_exynos7870/
ROM OS Version: Android 10
ROM Kernel: Linux 3.18
IMPORTANT, PLEASE READ THIS
This is a ROM built from source and not a GSI!
Fix Camera stretch & force close for some camera apps
You can do it editing /vendor/build.prop file using MiXplorer (you’ll need ROOT).
Search for the line “vendor.camera.hal1.packagelist”
After the = are the name of different apps. Delete one of these and put the package name of the app that you want to fix. For example, com.facebook.orca is the Facebook package name.
Per default, the ROM comes with Whatsapp, ZOOM, Snapchat and Instagram added. Maximum 4 Apps are allowed in this line and must be separated by comma ",".
If you don’t understand, open this link to see visual steps.
Fix Camera stuck
Sometimes, the camera can get inaccessible if an app has crashed. If it happen, follow this:
Install this app. Open it and tap "Kill camera", then give it ROOT permissions. Done! Camera is working again.
Take in mind that if the camera is broken and you didn't do this, the audio in calls maybe not work.
GCam
This ROM can run GCam. Download a modded version for Exynos HERE. Thanks to Leonardo Estacio for his mod.
Games: this ROM works so good for gaming and can run ARM64 apps/games. If you feel lags, go to Settings > Battery > Battery Saver and performance > Performance Profile and set it to High Performance.
For close, i want to give a huge thanks to @Astrako - Without him this ROM haven't be possible <3
Changelog
===== 02-02-2021 =====
- Initial build
Good ROM , stable. Just sometimes the launcher takes time to load after lock screen
Camera ta stretched
Hi, Thanks a lot for your work!
Just installed, looks very good and fast. I'll report eventual bugs I'd see.
Presently I have to warn to change point five of installation, as it's
for J7:
GonicTEAM said:
Install the lineage-17.1-xx-UNOFFICIAL-j7xelte.zip
Click to expand...
Click to collapse
with "install lineage-17.1-20210202-UNOFFICIAL-j5y17lte.zip".
Another known problem on LOS17.1 is the wrong behaviour of the proximity sensor during calls, that permanently darkens screen, and solves disabling sensors on calls or using headphones.
I know that isn't an issue of your port but instead an internal LOS17, and maybe AOSP bug: I also have the same on an Ananjaser port for Note4, anyway I signal it, in the hope that someone can fix it.
Are you also planning to port LOS18 on J5/2017?
Kind regards
BT no Audio
WiFi keep disconnecting and wifi mac address keep changing after reboot
00:12:34:xx:xx:xx
and wifi mac is not match in
Settings>About and Network details>Advance
All in all rom works great
Hi.good rom. Microphone on call not work. And speaker on call echo sound
I use sim2 slut
Very beautiful! It's very quick and feels light. Unfortunately, the SIM card is not recognized, making the Rom unusable. You are the king if you can make sure that the SIM card is recognized. I carried out the installation according to your instructions. My device is the SM-J530F (J5Y17LTE)
Internet navigation appears to be possible only through WiFi.
With a SIM inserted LTE band appears to be blocked, LTE indicator has a superimposed x.
Pointing the browser to a site gives back "unable to load page"
net::ERR_NAME_NOT_RESOLVED.
Please fix it
Edit: I have reinstalled from scratch after some day, and now it's all OK.
justforlineage said:
Very beautiful! It's very quick and feels light. Unfortunately, the SIM card is not recognized, making the Rom unusable. You are the king if you can make sure that the SIM card is recognized. I carried out the installation according to your instructions. My device is the SM-J530F (J5Y17LTE)
Click to expand...
Click to collapse
I also have the same model, and can see my SIM.
But I cannot navigate (pls see my latter post).
The fact that calls don't work is an old problem in LOS, maybe coming from AOSP. It's due to malfunction of the front sensor, that should turn off screen and touch when the phone is close to cheek. A quick and dirty workaround is to put headphones on, or to disable sensors (Settings ->System ->Advanced ->developer options ->quick settings developer tiles -> Sensors off). Of course, while sensors are disabled, rotation, gps, and all apks needing a sensor output cannot work and possibly crash. At that point the phone app blue screen stays on, and one can tick loudspeaker, call end or launch some other app while on call.
Alvin50 said:
I also have the same model, and can see my SIM.
But I cannot navigate (pls see my latter post).
The fact that calls don't work is an old problem in LOS, maybe coming from AOSP. It's due to malfunction of the front sensor, that should turn off screen and touch when the phone is close to cheek. A quick and dirty workaround is to put headphones on, or to disable sensors (Settings ->System ->Advanced ->developer options ->quick settings developer tiles -> Sensors off). Of course, while sensors are disabled, rotation, gps, and all apks needing a sensor output cannot work and possibly crash. At that point the phone app blue screen stays on, and one can tick loudspeaker, call end or launch some other app while on call.
Click to expand...
Click to collapse
Hey,
On this LOS version i can use SIM ( SMS, Calls, Mobile Data ) ->
lineage-15.1-20180510-UNOFFICIAL-j5y17lte.zip
Hey,
On this LOS version i can use SIM ( SMS, Calls, Mobile Data ) ->
lineage-15.1-20180510-UNOFFICIAL-j5y17lte.zip
Click to expand...
Click to collapse
Ok, but it's an old version.
For newer versions I'm just triying a LOS 18.1 treble from AndY Yan, that looks promising and seems to have solved the previous issue.
Just updated yesterday, but presently may have some erratic reboot, I'm investigating whether it's a problem of mine or not. Minor problem, the signal strength triangle always stays empty.
Alvin50 said:
Ok, but it's an old version.
For newer versions I'm just triying a LOS 18.1 treble from AndY Yan, that looks promising and seems to have solved the previous issue.
Just updated yesterday, but presently may have some erratic reboot, I'm investigating whether it's a problem of mine or not. Minor problem, the signal strength triangle always stays empty.
Click to expand...
Click to collapse
Hey,
does the LOS 18.1 version recognize the SIM card? Are there any more problems besides the regular restarts? If not could you give me the link to the post?
I am currently using LOS 15.1 lineage-15.1-20180510-UNOFFICIAL-j5y17lte.zip but don't dare to root it because I fear that the rooting has led to regular reboots and the subsequent deletion of all data.
justforlineage said:
Hey,
does the LOS 18.1 version recognize the SIM card? Are there any more problems besides the regular restarts? If not could you give me the link to the post?
I am currently using LOS 15.1 lineage-15.1-20180510-UNOFFICIAL-j5y17lte.zip but don't dare to root it because I fear that the rooting has led to regular reboots and the subsequent deletion of all data.
Click to expand...
Click to collapse
Yes, SIM cards are recognized. Making and receiving calls works well, only rings on incoming call aren't working. the bug I claim is a reboot every 24 mins, that in any case doesn't affect the system.
Alvin50 said:
Yes, SIM cards are recognized. Making and receiving calls works well, only rings on incoming call aren't working. the bug I claim is a reboot every 24 mins, that in any case doesn't affect the system.
Click to expand...
Click to collapse
It's a shame that these mistakes exist ... With these mistakes, the rom is no good as a daily companion. I'll keep my fingers crossed that you will get the problem solved or that there will be an update.
Alvin50 said:
Yes, SIM cards are recognized. Making and receiving calls works well, only rings on incoming call aren't working. the bug I claim is a reboot every 24 mins, that in any case doesn't affect the system.
Click to expand...
Click to collapse
Did you root the rome? Have you ever tried booting into Safe Mode to see the rom reboot every 24 minutes? Downloaded another phone app to see if there is a sound on incoming calls? These possibilities just came through my head.
justforlineage said:
Did you root the rome? Have you ever tried booting into Safe Mode to see the rom reboot every 24 minutes? Downloaded another phone app to see if there is a sound on incoming calls? These possibilities just came through my head.
Click to expand...
Click to collapse
This ROM comes pre-rooted, anyway I'm used to Magisk, so I installed it too.
Don't blame at the developer: having some bug on an unofficial, out-of-the-box vanilla release is rather normal. Our job is to collaborate with developers, feeding them with our bug findings, possibly correlated with some log. Such ROMs aren't for daily use, it's well advertised in the first posts, already until the joined efforts of testers and developers achieve a reasonable reliability and stability level.
IMHO, this one is pretty usable, a temporized reset is a minor bug. There are other worse bugs, but with patience and constance they also can be overcomed.
Edit:
I just realized we are in the wrong thread. My latter posts are related to AndyYan's GSI LOS18.1. Better if we move our discussion there.
Kind regards
ROM IS VERY FAST AND VERY CLEAN!ALL WORKS FOR ME EXCEPT SIM CARD CONTACTS i cant see it even with 3RD party app
Edit:anyone know how to push apps into system?Link2sd and similar apps fails.If i push it from recovery phone doesnt boots!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Google Pixel
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 18.1 thread for the Google Pixel.
Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.
Official builds:
sailfish
Unofficial - built once a month by me, includes GApps and Pixel goodies:
sailfish
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
Sound Trigger (Screen-off "Hey Google" detection) is nonfunctional due to incompatibilities with older proprietary binaries, and lack of system space for needed Google Apps.
Find any? Report them according to this guide.
Notes:
Firmware is shipped in the ROM package for this device, so no need to worry about updating it on your own!
The only supported GApps package at the moment is OpenGApps pico, linked on our Wiki page about gapps.
Kernel Source: https://github.com/LineageOS/android_kernel_google_marlin
npjohnson said:
Google Pixel
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the unofficial Lineage OS 18.1 thread for the Google Pixel.
Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.
sailfish
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
IMS (VoLTE/ViLTE/WFC) is nonfunctional due to incompatibilities with older proprietary binaries
Sound Trigger (Screen-off "Hey Google" detection) is nonfunctional due to incompatibilities with older proprietary binaries.
Find any? Report them on this thread, and make sure to include logcat/dmesg as applicable.
Notes:
GApps are baked in, alongside other Pixel goodies - No, I will not be building without GApps included for this device. These builds are built, packaged, and signed by me, and not affiliated with LineageOS whatsoever.
This will likely never be official. At minimum, IMS would need to be fixed, and I haven't cracked it (yet). If you can get IMS working, please contact me, and we can work together!
Firmware is shipped in the ROM package for this device, so no need to worry about updating it on your own!
Kernel Source: https://github.com/npjohnson/android_kernel_google_marlin
Click to expand...
Click to collapse
Thank you so much
Thanks, good work !
Thank you for great work!
Bugs:
- WiFi MAC randomization toggle in Developer Options is not working, but AFAIK MAC randomization isn't even supported by original Pixel devices
- sRGB toggle in Developer Options not working
- Brightness/dimming acts funky and sometimes reduces brightness to 0 by itself, then the screen becomes unresponsive for a short time
DirtyAngelicaSecured said:
Thank you for great work!
Bugs:
- WiFi MAC randomization toggle in Developer Options is not working, but AFAIK MAC randomization isn't even supported by original Pixel devices
- sRGB toggle in Developer Options not working
- Brightness/dimming acts funky and sometimes reduces brightness to 0 by itself, then the screen becomes unresponsive for a short time
Click to expand...
Click to collapse
1. Expected, I disabled the function, it's broken, but there's no easy way to hide it.
2. Yeah, but color profiles through LiveDisplay should work in it's place?
3. I've hit this on stock a few times, wondered if it was my device or what - maybe a hardware digitizer bug?
npjohnson said:
1. Expected, I disabled the function, it's broken, but there's no easy way to hide it.
2. Yeah, but color profiles through LiveDisplay should work in it's place?
3. I've hit this on stock a few times, wondered if it was my device or what - maybe a hardware digitizer bug?
Click to expand...
Click to collapse
Thank you so much for the Sailfish July 2021 update
Edit: what computer 🖥 and OS do you use to compile your Rom's? Would you be so kind to make a guide with the commands you use to compile? I can't get the one from the LOS website to work :/ ty
spiral777 said:
Thank you so much for the Sailfish July 2021 update
Edit: what computer 🖥 and OS do you use to compile your Rom's? Would you be so kind to make a guide with the commands you use to compile? I can't get the one from the LOS website to work :/ ty
Click to expand...
Click to collapse
I use the same one's detailed on the Lineage wiki.
They work.
My personal PC specs: https://pcpartpicker.com/user/npjohnson/saved/#view=dr268d
Does this work with unlimited Google Photos storage? If so, I'm instantly installing it. Thanks in advance.
Edit: It does!!
Thanks for the August update dude! You're one humble dude for not posting that here.
npjohnson said:
1. Expected, I disabled the function, it's broken, but there's no easy way to hide it.
2. Yeah, but color profiles through LiveDisplay should work in it's place?
3. I've hit this on stock a few times, wondered if it was my device or what - maybe a hardware digitizer bug?
Click to expand...
Click to collapse
August 2021 unofficial update for Sailfish is working great ty
My experience these first weeks: the phone is very fast and responsive, battery lasting longer than last official stock firmware (Android 10). The following are the only issues I've found:
Automatic brightness going too low in the dark: This was present at least in the past two releases.
Android Auto not working in the car ("Test App" appears on screen when connecting to car USB). There's a workaround in the forums where you need to copy the .apk to a system folder here, or re-flashing gapps. This was also present in the last releases.
Great job!
I've found issues that the settings app seems to crash if you enter the permission screen on some (all?) apps. Just go into Facebook or Messenger or whatever and try to disable the microphone and there's a good chance for a crash
Also, I've definitely noticed what was mentioned above. This ROM seems to have 0% screen brightness as an option. The official LineageOS 16.1 does not.
rinaldimj said:
My experience these first weeks: the phone is very fast and responsive, battery lasting longer than last official stock firmware (Android 10). The following are the only issues I've found:
Automatic brightness going too low in the dark: This was present at least in the past two releases.
Android Auto not working in the car ("Test App" appears on screen when connecting to car USB). There's a workaround in the forums where you need to copy the .apk to a system folder here, or re-flashing gapps. This was also present in the last releases.
Great job!
Click to expand...
Click to collapse
1. I can take a look into this. Nothing has changed in auto-brightness since 18.0's initial push, so it must be device specific. Does it just go black?
2. Yeah, we can't fit full GMS - AA is one of the things I sacrificed to get GMS to fit.
Melionix said:
I've found issues that the settings app seems to crash if you enter the permission screen on some (all?) apps. Just go into Facebook or Messenger or whatever and try to disable the microphone and there's a good chance for a crash
Also, I've definitely noticed what was mentioned above. This ROM seems to have 0% screen brightness as an option. The official LineageOS 16.1 does not.
Click to expand...
Click to collapse
Permissions: Doesn't happen for me - do you have Magisk or something?
npjohnson said:
1. I can take a look into this. Nothing has changed in auto-brightness since 18.0's initial push, so it must be device specific. Does it just go black?
Click to expand...
Click to collapse
Not absolutely black, but so low the screen is unreadable. The firsts times it happened I thought adaptative brightness will correct it according to my selection, but it doesn't - at least for the lower end. The very next step in the scale is perfect for a minimum.
2. Yeah, we can't fit full GMS - AA is one of the things I sacrificed to get GMS to fit.
Click to expand...
Click to collapse
I undestand. I though this wouldn't be the case when I noticed that the required system app for Android Auto is very small (~3MB), but the truth is our devices really suffer the low storage.
Again, thank you very much, amazing job!
Has auto-brightness been fixed? It really did set itself to 0% last time I tried this ROM. Was there some way to get it back up? What about MAC address randomization and sRGB toggle?
MAC Randomization should be controllable by the OS itself, not hardware.
Your signature says "Lineage OS Developer Relations Manager". Does that mean that you know whether there is a plan to officially bring Lineage OS 18.1 to Pixel Sailfish in the future?
rinaldimj said:
Not absolutely black, but so low the screen is unreadable. The firsts times it happened I thought adaptative brightness will correct it according to my selection, but it doesn't - at least for the lower end. The very next step in the scale is perfect for a minimum.
I undestand. I though this wouldn't be the case when I noticed that the required system app for Android Auto is very small (~3MB), but the truth is our devices really suffer the low storage.
Again, thank you very much, amazing job!
Click to expand...
Click to collapse
I have sailfish, and took it in a pitch dark room, sure it got dark but I could still read it?
Maybe it's panel degradation? Do you see this problem on stock?
And yeah, it's not the devices fault really, LineageOS has grown like 50 mb in the last few weeks.
DirtyAngelicaSecured said:
Has auto-brightness been fixed? It really did set itself to 0% last time I tried this ROM. Was there some way to get it back up? What about MAC address randomization and sRGB toggle?
MAC Randomization should be controllable by the OS itself, not hardware.
Your signature says "Lineage OS Developer Relations Manager". Does that mean that you know whether there is a plan to officially bring Lineage OS 18.1 to Pixel Sailfish in the future?
Click to expand...
Click to collapse
1. See above, I can't recreate.
2. I hid it, LIveDisplay offers an alternative that actually works.
3. MAC Randomization - nah, it's more complicated than that - the controller and firmware have to play nicely - and they don't - so I disabled it.
And lastly, there's a note in the OP about why this won't (likely ever) be official.
Thank you for a prompt response! I never had auto-brightness issue with any ROM's, be they official stock images or Lineage OS official images. This ROM was the only one with that issue.
I hope you don't mind me asking, but why is it necessary for IMS to work? VoLTE doesn't work for some devices with official Lineage releases, but it doesn't get in the way of such releases either.
DirtyAngelicaSecured said:
Thank you for a prompt response! I never had auto-brightness issue with any ROM's, be they official stock images or Lineage OS official images. This ROM was the only one with that issue.
I hope you don't mind me asking, but why is it necessary for IMS to work? VoLTE doesn't work for some devices with official Lineage releases, but it doesn't get in the way of such releases either.
Click to expand...
Click to collapse
Given that the pixel is a US centric phone, and the US is shutting down everything except for voice over LTE this year, we don't want to ship something that's not going to work as an "upgrade".
Thank you for this ROM, it's fast and smooth.
Hii everyone
Thanks for this rom
Working nicely on sailfish
just one problem
a particular app is not working ( banking app )
i have attached the logs
kindly assist
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction
LineageOS, an open-source Android distribution, is available for several devices,
with more being continuously added thanks to the biggest, yet ever growing, Android open-source community.
Join us and breathe new life in your device, be it old or new.
Click to expand...
Click to collapse
If you don't know LineageOS and would like to read about it before installing it you can take a look at the official Website.
Features
Individuality
Customization is paramount to productivity.
That’s why LineageOS promises to push for user personalization and preference.
Everyone is unique and your device should be too.
Click to expand...
Click to collapse
Security
Your data, your rules. With powerful tools such as Privacy Guard, you are in control of what your apps can do whenever you want.
Trust will help you understand the security of your device and warn you about possible threats.
We take security very seriously: that’s why we deliver security updates every month to all our supported devices.
And to make your device more secure, lock everything behind an enhanced lock screen.
Click to expand...
Click to collapse
Longevity
LineageOS extends the functionality and lifespan of mobile devices from more than 20 different manufacturers thanks to our open-source community of contributors from all around the world.
Click to expand...
Click to collapse
Installation:
If you are on stock OS, you need a custom recovery first. You can get the recommended recovery in the official installation instructions link below.
If you are coming from stock or other ROMs, you need to make a factory reset.
As always, make sure to backup before installing this ROM.
More detailed instructions at:
Install LineageOS on onyx.
Downloads
Download LineageOS 18.1 for OnePlus X
Download TWRP Recovery for OnePlus X
Recommended Google Apps package: Open GApps (Choose the arm pico package - NOT arm64)
Source code
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
The device specific source code can be found in the LineageOS Github repo.
OnePlus X device tree
OnePlus X kernel
Changelog:
Initial
Bug reports:
Please submit bugs and other errors in this thread
Donate to support development:
Donate via PayPal to vware
Donate via PayPal to LineageOS
Contributors
Georg Veichtlbauer
ROM OS Version: Android 11
ROM Kernel: Linux 3.4.x
Version Information
Status: Experimental
Created 2022-06-12
Last Updated 2023-05-05
(reserved)
Thank you so much, I''ll be installing it tomorrow and will be active here if I found some bugs will report with logs once again thank you so much, much appreciated your work
The in call volume is very high even at the lowest volume level and screen doesn't go off when answering a call or dialing a call
let me know that do I need to post logs for this issue
thanks for trying it! i will be playing a bit trying to reintegrate into upstream lineage, if that does not work, i will continue down this path.
should have some news pretty soon, though it's summer
qsnc said:
The device specific source code can be found in the LineageOS Github repo.
OnePlus X device tree
OnePlus X kernel
Click to expand...
Click to collapse
Hmmm... But these are sources for tree 15.1, not for 18.1.
as ive said in the other thread, this is pretty much just built on top of the trees of Yume. you can find the sources there, or on my github (linked in my profile).
however, also, just a post above, ive stated i am working on re-upstreaming the whole thing, i am not done yet. and its summer ;P once ive got news, i'll update the thread.
new release. beware: quite a lot of changes, mostly bringing configs back to stock (original maintainers didnt understand the usage of i2s in the sound config apparently). however: this may cause unexpected problems, so please let me know if anything new goes wrong here
also, current source links are updated
just quick update
clean Installed it and so far it's fine. in call volume is perfect and screen also goes of now
I'll test it and see if I find any other bugs.. hopefully not
1 update: when it boots up it says signed with public keys
Random reboots keeps happening. Mainly when I try to switch between more than two apps or it could be something else. I've attached logs if it helps
niravnn said:
Random reboots keeps happening. Mainly when I try to switch between more than two apps or it could be something else. I've attached logs if it helps
Click to expand...
Click to collapse
Same here it crashes a lot and also the download manager seems to disappear.
I can confirm that it often crashes and just restarts for no reason
sadface. did the other build crash for you guys too?
qsnc said:
sadface. did the other build crash for you guys too?
Click to expand...
Click to collapse
no other build was fine it wasn't rebooting like your latest build. but the in call volume was so high at the lowest volume that it was unsable as daily driver and also screen wasn't turning off when receiving a call or dialing a call so it was also creating issue. so I only used your other build for like 30 minutes but not a single reboot at that time.
but with your latest build, it rebooted every 5 minutes. so it's completely unusable..
The version of the lineage-18.1-20220612-UNOFFICIAL-onyx.zip runs so far well with me no restart without reasons present.
Unfortunately, the display does not go off when making calls with the version lineage-18.1-20220612-UNOFFICIAL-onyx.zip when the phone is at the ear.
For me, the volume was ok, but not perfect either, I felt it was more quiet than loud.
It could be a bit louder.
Their new version lineage-18.1-20220623 I tested only briefly and then went back to the old one because of the constant reboots.
EDITED: pretty sure zram was the culprit in the new build, so please download from the first post again and try it, works okay on my device.
AFTER you have downloaded it, please let me know if volume issues still persist, it's been back and forth a bit
Sorry I noticed something else
So for one the proximity sensor still doesn't work and the display doesn't turn off while on the phone and just stays on when the phone is at your ear.
What also does not work is the interactivity display.
My settings are set to: Wave On, Pick Up On and Pocket On.
however nothing happens so I guess the sensor is not working because the phone just stays dark when in standby.
new build is up, quite a lot of changes. proximity sensor works fine for me, in call and also during inactivity display. unless i make some progress on my "internal" goals, this will be the one to get for some time, as it works for everything i need it to.
Great respect good work thank you it runs as far as I can tell now everything.
Good work for this old Phone!! And we have nothing to pay...! One Question ist there an Option to customize the Navbar (center Clock, change Battery Icon, etc.)? I can't find anything.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Moto Edge 20 Pro
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 19.1 thread for the Moto Edge 20 Pro.
Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.
pstar - Official builds
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
None.
Find any? Report them according to this guide.
Notes:
The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.
Kernel Source: https://github.com/LineageOS/android_kernel_motorola_sm8250
Is there still a problem with the black screen of death?
wangyi666 said:
Is there still a problem with the black screen of death?
Click to expand...
Click to collapse
It shouldn't no
Will you add the fingerprint variations?
I can't use fingerprint to unlock my phone after install los, even no options in system settings. ls it normal situation?Did los doesn't support fingerprint?
x-new said:
I can't use fingerprint to unlock my phone after install los, even no options in system settings. ls it normal situation?Did los doesn't support fingerprint?
Click to expand...
Click to collapse
We are working on it, some devices use goodix fp, it is not supported right now
Thanks for this, this ROM fixes so many problems that the stock ROM from Motorola has. It's so nice now being able to call fine, use WiFI calling, being able to turn wifi on and off without it crashing and rebooting etc etc! All issues on the stock ROM for myself and others!
And it's amazing to have double tap to wake that works and a screen brightness that lowers like it should .
Only issues noticed are the fingerprint sensor issue as above, which I know you're looking into Elctimon (big thanks!) and one I seem to be getting with third party launchers sometimes which is when returning to the home screen and tapping an app icon, it interacts with the previous app instead. It's fine if you just wait longer...
I've logged a bug report for both following the instructions in the original post.
The only feature I miss from stock is the ability to set refresh rate for games to 120 or 140hz sometimes, otherwise I like my phone to be at 60hz for power savings. I turn off all animations anyway. The dynamic refresh rates sadly don't work below 70% brightness (same as stock ROM behaviour)
I tried to flash the Moto games apk which did this but unfortunately I get a missing library error : "Package com.motorola.gamemode requires unavailable shared library moto-core_services; failing!".
Perhaps a quick toggle setting could be added for refresh rates?
P.S Always on Google listening hotword detection doesn't work if you follow the instructions and install the mindthegapps package linked, it seems that it doesn't install enough packages. It needs the Google app to be installed before the OS first boots it seems? Make sure the gapps you are flashing includes Google app if you care about this.
is dc (anti flicker) works well？ i have flashed los a few month ago but the dc stoping working after lock screen
Thank you Electimon, the black screen issue has resolved for me with the latest releases.
Do you think that merging the Goodix (GF3626 fingerprint sensor) related files from the Berlin (edge 20) LineageOS build would resolve the Goodix fingerprint not working issue?
The files: https://github.com/LineageOS/android_device_motorola_berlin/search?q=goodix
I made a branch of it with the files copied over but I wasn't sure about these two files, if anyone could help me with getting these created for our device that'd be awesome!
android_device_motorola_berlin/rootdir/etc/init/hw/init.mmi.overlay.rc at 136fd799ec84e4d6ed008ab2641cac3e2d5aef3c · LineageOS/android_device_motorola_berlin
Contribute to LineageOS/android_device_motorola_berlin development by creating an account on GitHub.
github.com
android_device_motorola_berlin/modules.load at 71457c4f0467182bf7ae7834efe6dbeffa129cb7 · LineageOS/android_device_motorola_berlin
Contribute to LineageOS/android_device_motorola_berlin development by creating an account on GitHub.
github.com
https://github.com/LaurenceGough/android_device_motorola_pstar (if it helps at all) pull requests were not allowed
Thanks!
Hello Electimon. Thanks for the ROM, it's great to have something different for this underdeveloped device.
I came to Lineage to try to solve a problem with Bluetooth, but it didn't work. The problem remains exactly the same, Bluettoh only works from time to time, most of the time it doesn't even turn on. Still, I'm going to stay in this ROM, because I think it's better than the stock one.
If you have any suggestions of what I can do please enlighten me.
I don't understand how this can happen to some people and Motorola doesn't recognize it and make a fix available. I don't know what else to try, but my problem is the exact one demonstrated by this guy on Reddit:
https://www.reddit.com/r/motorola/comments/ym02hj
Hi guys,
What's up with the random reboots in this ROM? I used to have that problem on the previous Lineage as well as on the latest LMODroid build.
I need the original camera to take 108mb
thomashastings said:
Hi guys,
What's up with the random reboots in this ROM? I used to have that problem on the previous Lineage as well as on the latest LMODroid build.
Click to expand...
Click to collapse
I'm at 71 hrs uptime now, this was not achievable on any previous ROMs for this device. I'm truly thankful for this release, it's just excellent.
thomashastings said:
Hi guys,
What's up with the random reboots in this ROM? I used to have that problem on the previous Lineage as well as on the latest LMODroid build.
Click to expand...
Click to collapse
Ive never had a random reboot on this ROM, well apart for one time which I'm 99% sure was to do with an OTA update.
I've run this ROM for many weeks too.
The only downside is no fingerprint reader for my Edge 20 pro phone and that's it.
It fixes a load of issues with the stock motorola ROM!
rambo2405 said:
I need the original camera to take 108mb
Click to expand...
Click to collapse
It's just pixel binned anyway like all modern phones the 108mp is kinda a waste of time I feel. Look into gcam for our phone that's worth installing.
Well, since the last update (March 28), Bluetooth is working normally. It's still too early to know if it's fixed, but it hasn't worked this well for a while.
Bothrops said:
Well, since the last update (March 28), Bluetooth is working normally. It's still too early to know if it's fixed, but it hasn't worked this well for a while.
Click to expand...
Click to collapse
Is that with the stock ROM?
I wondered if Motorola have also fixed the outgoing call issues that all the edge 20 and 30 phones are getting? Where you cannot make a call unless you reboot or turn off WiFi, which usually causes a reboot.
And when you turn WiFi off and on it reboots the phone...
Factory resetting does not resolve the issue but installing LineageOS does fix the issue. Sadly banks require so many workarounds now to work, and my fingerprint sensor still doesn't work but I know one of the Devs are working on it.
Sadly call quality for me is really bad on this ROM, next to unusable for me. I think it needs some kind of voice technology that's on the stock ROM but is missing from this ROM. But it's better than no calls so I'm running it for now.
Also I'm noticing very high WiFi latency spikes and packet loss jssues that was also an issue on the stock ROM. It uses the same drivers as the stock ROM so I guess that's expected. All other non Motorola devices are fine.
I take back what I wrote. After a few days working normally, Bluetooth became unstable again. For me Lineage has the same problem as the stock ROM. In my case, Wifi works perfectly both on stock and Lineage. But Bluetooth doesn't work properly on either of the 2.
Motorola drivers may not work for all Wifi and Bluetooth modules, as there may be hardware differences between devices. Anyway, it's a serious failure, due to complaints on websites, youtube, Telegram groups, etc... and the worst thing is that I haven't seen the problem acknowledged anywhere.
I do not recommend LineageOS for this device, WiFi/Bluetooth didn't get fixed and are features that is not fully workable as in stock rom. Also, Motorola has rollout the Android 13 stock rom and if you remove some bloatwares, I fully recommend it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Pixel Experience GSI for Surface DuoHello everyone, after a long tease, finally I have a build of Pixel Experience with some modifications to run on Surface Duo.
The experience is still very preliminary, with almost no UI customization. The only work done is to react to posture changes.
As such, I would suggest this build to be installed using DSU Sideloader instead of directly flashed onto device, so you can try out the experience and get back to a more stable, stock Microsoft Duo OS experience.
Download Link:
duo_PE_system.img.gz
GZ File
1drv.ms
Features:- Pixel Experience ROM
- Screen and touch react to posture changes
- Sleep/Wake based on posture
Bugs:- You tell me (sorry, I have always wanted to type that)
- Posture sometimes become buggy. Workaround is to unfold device to get back to dual screen and go back into the posture you want.
- I have noticed some funny behavior with screen timeout and waking, but haven't tested it properly yet
- The split screen handle is actually smaller than the hinge, so you lose some pixels from apps in split screen mode
- UI is not modified for dual screen, so you will have UI elements under the hinge.
Installation Guide (DSU)Prerequisite:
- Unlocked bootloader
- Have at least 32Gb of storage left
1. Download and install DSU Sideloader from https://github.com/VegaBobo/DSU-Sideloader
2. Download Pixel Experience GSI for Surface Duo from https://1drv.ms/u/s!An829WhOFDfUoLgiauVbeMFQYJ6lWg?e=gbDWdY
3. Follow instruction in DSU Sideloader to install the build. I recommend changing the userdata partition size to be 16Gb at least, but can be larger if you want to use it more substantially.
Installing using DSU Sideloader will mean whenever I release a new build, you will need to sideload it again, losing all userdata of the build in the process. This is expected, as I don't think the build is necessarily ready to be daily driven.
Installation Guide (fastboot)If you are well acquainted with ROM flashing and are not afraid of messing around with fastboot and recovery images, this is for you. The upside is that you can update whenever I release new builds without losing data. I will write out the general steps here. If you cannot figure out how to do this from the steps, this is not for you yet.
1. Unlock bootloader
2. Reboot into fastbootd
3. Delete system_ext and product partition, alternatively delete the inactive system_a/b slot.
4. Flash the system.img onto system partition
5. Reboot
6. ??
7. Profit
Photos:
Huge thanks for your work! Glad you got it stable enough for a release. Will test it once I am home
I gave it a try as DSU Sideload and it runs very well. Thank you.
Will use it for the next days.
Amazing work! Flashing when I get home for sure
Already flashed amazing work !!!
My sim card going back from my pixel 7 to my duo again
works great, much better than the microsoft original rom. You have save this device, thanks
Works very well, thank you for your work, do you plan to make updates to fix the middle of the screens?
Looks great understand its early days but will you be moving towards the standard pixel experience installation method in the future?
Even though I've been banned from Twitter I have been following you for at least a month now. I'm so glad to see you had released a working copy.
I swear I was just moments away from closing that tab thinking you had lost interest in the Surface Duo.
THANK YOU! You are my hero.
From the video I saw, the apps open as spanned by default then?
Amazing, installed it last night, noticed a few wonky things like:
1) When opening /unlocking only 1 screen turns on, after a second or two both come on.
2) Thinks there's no bezel and is one big screen, probably the hardest part to figure out how to get it to behave with a gap offset or like the OG Microsoft rom
3) Pin to screen is not as nice as in the original rom
Where do you want us to report this, here or in your github repo?
Does this work on the Duo 2?
Bugreport:
I installed it yesterday via fastboot. I figured out that the most Microsoft Apps are not working. They start but close immediatly (MS Outlook, MS365)
MS Edge Canary is working
rmb32 said:
Bugreport:
I installed it yesterday via fastboot. I figured out that the most Microsoft Apps are not working. They start but close immediatly (MS Outlook, MS365)
MS Edge Canary is working
Click to expand...
Click to collapse
I can second this, a lot of apps which may have had duo optimisations (Kindle, TikTok, Microsoft Outlook & Teams) seem to crash on startup/opening. I wonder if they're looking for frameworks or features that would be present on the stock ROM.
I'm trying right now using dsu. Amazing work!!
I really like the way multitasking (using both screens) is done here. Haven't tried phone calling and aside from one time the ui hanging while messing with the split screen options, everything seems very smooth and stable. Really looking forward to what comes next!
Nice work! I will definitely be flashing this on my next day off. Thanks for your work on this and look forward to more updates!
Justice™ said:
I can second this, a lot of apps which may have had duo optimisations (Kindle, TikTok, Microsoft Outlook & Teams) seem to crash on startup/opening. I wonder if they're looking for frameworks or features that would be present on the stock ROM.
Click to expand...
Click to collapse
I can confirm this as well. I tried to use Outlook but it crashes on startup. A possible solution would be to fake the device identity as a Pixel? I guess these apps check if the device is a Surface Duo and then they expect the duo sdk/framework
Pinguin2001 said:
I can confirm this as well. I tried to use Outlook but it crashes on startup. A possible solution would be to fake the device identity as a Pixel? I guess these apps check if the device is a Surface Duo and then they expect the duo sdk/framework
Click to expand...
Click to collapse
Can confirm as well. Flashed via fastboot and OneNote, onedrive, and ms365 are all crashing.
I havent logged in xda for the longest time but I just wanted to say thank you for working on this. I have been switching back and forth between my v60 and the duo because the v60 has been far more responsive and stable. But the duo form factor is better. I have been dailying the duo for a week and have been considering switching back to the v60 again but after installing this, you have given me hope because of the increased responsiveness.
Screen orientation is excellent and fast.
I'm on the fence on the flipping over the screens on phone mode. There are times it gets confused which screen should be on but I cant say how else dictate which screen should be on. Situation where person is looking down on the screen (standing up) VS person is looking up on the screen (lying down with the phone above the persons head.) , the phone can kind of be tricked into turning the other screen by quickly rotating the phone and back to the position desired.
Can confirm tiktok crashing.
Thai I hope you can continue working on this. You've already done a great job vs an entire company to make give life to the duo again. Is there a way where we can help support you in your work on the duo?
Thanks again!