yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] saady002000:
Hello, RobZen,

sorry for late reply,

yes The Realtek chip needs to be removed first, then solder the new chipset.

better to take it a professional soldering person to do it for you, because it is very tinny and looks like micro soldering.

I made the soldering at computer maintenance shop I guided the guy how to do it only and he did it for me.

that was much safe.

and nothing covered with varnish.

good luck
[FYT Android Head Units] RobZen77:
Thank you,

Problem is that I live in Germany, not easy to find someone to do it for you, when I would find someone, probably I would pay for that almost as much as I paid for the whole unit. I also have experience in soldering, probably I will try to do it myself.
[FYT Android Head Units] Astralech:
I have a soldering iron with various T12 tips and soldering with 0.5 or 0.7 mm tin was very difficult to connect both fields and I was afraid of overheating. I thought I'd try the paste and it turned out great. First, I precisely positioned the module and connected the ground fields with a soldering iron.
[FYT Android Head Units] Astralech:
On your board you had galvanized 360 module fields. Look at the photo of the RobZen77 board and see what the soldering pads of the 360 module and soldered elements and tinned pads without components look like.
[FYT Android Head Units] RobZen77:
Unfortunately it looks like it is an abandoned project, I was about to install the screen in the car ( for now without the 360 chip) and before put it in place, I dropped the screen and the display came apart from plate , all ribbon cables came off. I tried put all back, but now the screen lights up but no image. I don't know if the ribbon cables are damaged, or something on the board. To bad, it is a good board.
[FYT Android Head Units] daneag:
Has anyone see black and white camera feeds, after installing the 360 chip? In-addition, looks like the picture has been cut up and messed around (I'm assuming due to not able to read the signal from the camera) I'm assuming this is a software issue hopeful, it been annoying if this was hardware (my soldiers joints might need to be redone though, but connectivity test seemed fine)

I'm assuming AHD camera 1280x720 was fine with it as if I change from 360 input to backup camera input I have fully color and working camera there. (Note: In the process of getting new firmware to see if that will work)
[FYT Android Head Units] RobZen77:
Happened to me, when I was connecting the cameras to the display, what was originally for Audi. It was a 8259 base, but the problem was the wiring pinout was incorrect. As soon as I resoldered the wires in right way, everything was fine.
[FYT Android Head Units] daneag:
How were you able to test the wires were in the right spot, as they just go to an header on the head-unit? (8259 base?) Measure voltage? (I'm assuming your talking about camera wires to the header on the headunit)
[FYT Android Head Units] RobZen77:
I was measuring resistance according to the colour codes and pinout
[FYT Android Head Units] daneag:
So tried it out, but couldn't make heads to tails of anything wrong with it, had 75 ohms to the camera feed to gnd (which make sense), the 4 camera voltage lines look like voltage lines. So it seems like my header was the correct way
[FYT Android Head Units] RobZen77:
All I can think of is that the 8259 unit did not need trigger wire for every camera. It was only one trigger wire from reverse attaching to the wiring and the cameras needed only the ground-video- 3.3v in completely other order attached. Also could you play with canbus types too.
[OnePlus 6 & 6T Cross Device Development] Evon88:
thank you boss, thx for this hard work 💜
[OnePlus 6 & 6T Cross Device Development] syamkumar.tpl:
crDroidAndroid-12.1-20220709-enchilada-v8.6.zip

is it Beta version..?
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
Yay we're finally official! Come 'n' get it kids!
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
Nope, I just PR'd last night to go official and it was accepted. :)

crDroid 8.x has stricter requirements for device maintainers with Android 12 releases, so until now I've only been able to classify the 8.x builds I've been working on for the last several months as betas, and honestly I haven't had the time until now to set up all of the XDA pages, so they've just been linked in the Telegram chat group.
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
(also, please don't link to the sourceforge files directly -- having people go through the crdroid.net website and have ads displayed helps fund the ROM dev team's server costs. Unless you don't WANT the ROM to keep getting developed, of course...)
[OnePlus 6 & 6T Cross Device Development] tomasz-c:
Thank you for your work!

I just updated on my OnePlus 6 crDroid from version 7.19 to 8.6. For a quick check what I checked is working fine, all data is preserved.

Thanks!
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
Oh holy crap, it worked?! That's... kind of amazing. I didn't expect it to work, ngl. Thanks for the report, and enjoy!

___

If you don't mind me asking; what GApps (if any) did you have before & which package did you flash as part of the update, what recovery or with built-in updater in Settings > System > Updater, etc etc.?
[OnePlus 6 & 6T Cross Device Development] tomasz-c:
Yes, it worked :) And could you explain why it surprised you? Looks like it was more risky than I thought :) but I made copies beforehand, of course.

All the apps I checked work without any problem. Contacts, SMS, call history, photos and other data on storage and data of other apps are preserved.

I didn't remove the encryption before the update and my pin (sign) works fine.

In the previous post I forgot to add an important piece of information: I don't use GApps so I didn't test it.

At first I uploaded boot.img to both slots (because I forgot that in the description for the update it said to upload to one) but I guess it doesn't matter. I uploaded crDroidAndroid-12.1-20220709-enchilada-v8.6.zip to slot B, rebooted it booted after a long while (probably updating something) Android 12.1, when I saw that it worked I rebooted to recovery and uploaded it to slot A as well.
[OnePlus 6 & 6T Cross Device Development] tomasz-c:
I only now saw the questions in the second part of your post.

Basically, I did it as you stated in the instructions: "First time installation:" only without the "Factory reset / Wipe data" step and without installing GApps, because I don't use them.

To begin with, I updated to the latest version of crDroid 7.x (7.19)

Reboot phone to bootloader

fastboot flash boot_a crDroidAndroid-12.1-20220709-enchilada-v8.6_boot.img
fastboot flash boot_b crDroidAndroid-12.1-20220709-enchilada-v8.6_boot.img

Reboot phone to bootloader.

Use vol +/- keys to select recovery mode & press power button to enter recovery.

On phone, in red menu recovery choose "Apply update" > "Apply from ADB" > "ADB sideload" & then from computer,

adb sideload crDroidAndroid-12.1-20220709-enchilada-v8.6.zip

Reboot to system

When I saw that everything worked I rebooted to recovery and uploaded the zip image to the second slot via ADB Sideload.

I didn't have GApps before and didn't install them afterwards because I don't use them.
[OnePlus 6 & 6T Cross Device Development] tomasz-c:
I noticed that on the keyboard AOSP in Polish:

- swiping does not work,

- spell check does not work,

- word prompting does not work,

All these things worked on crDroid 7.19. Now they also work but in other popular languages, such as German or English.

I've tried deleting all AOSP keyboard app data and reconfiguring it from scratch, but that doesn't help.

Could I ask someone who has a clean installation to check this? Because without confirming it, it's unlikely to report the error.
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
8.7 testing releases available in the OP 6/6T TG channel if anyone is feeling adventurous!
[OnePlus 6 & 6T Cross Device Development] runtosafety:
Thanks for your hard work.

ROM runs pretty well, although there are some minor yet annoying issues (don't know if they have been mentioned in the Telegram group but I'll list them here anyway).

Sometimes the notification shade noticeably lags.

Text selection menu (cut, copy, etc) doesn't appear after selecting, I have to long tap the selection again for it to appear. It happens for both input fields and usual text (e.g. on a web page)

Gboard doesn't always save the buffer content into the clipboard manager. Same applies for the paste suggestions. Maybe I should install it as a system app? (I'm pretty sure I used it as a user app on crDroid 7 though)

Apps seem to unload from RAM more aggressively than on crDroid 7.

I guess they were removed in crDroid 8, but there used to be settings for weather on lock screen and smart charging (auto-disabling charging at XX%).

In quick settings, when I tap mobile data, it takes very long for the animation to switch on/off while Wi-Fi is on (only the animation). Sometimes it will get stuck at on or off until I reopen the notification shade. Also if you quickly reopen the shade, the animation will change instantly without any lag. (All this is true regardless of the Mobile data always active developer setting)
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
So, dirty little not-so-secret: I'm not really sure what I'm doing most of the time. There are a lot of things that seem to be regressions in Android 12, and I believe I've set up overlays correctly to configure crDroid-specific features. But... There are plenty of things where I don't know where to begin, and just assume that it's something that one of the actual core ROM dev team for crDroid (I am a device maintainer, not part of the core dev team) will eventually deal with, or it's just an issue with our specific device, or ... Whatever. Occasionally it's a thing that maybe I can dig up bug reports and logs and reproduce and figure out what's up and fix it.

Most of the things you mention are entirely beyond my control.

1. I believe you. Dunno what to do there; this will probably be an upstream ROM thing that needs to get fixed, but possibly relies on an overlay I need to fix. Usually things like this, I try and try to get to the bottom of it and pull my hair out and waste hours & hours and then it's something that was in the frameworks anyway and I don't know enough Java or Kotlin or C/C++ to have possibly been able to fix it, and then someone else fixes it and I could've just waited and it would've been fine in a month or two.

2. Yeah, I've had that too; seems to depend on app. Can you send me a log after it happens?

3. I'm using GBoard as a user app myself, although that's with MinMicroG, and haven't had problems with it. But I believe you. What GApps are you using?

4. Yeah, I noticed that too. There's work to do tuning things, but I'm not sure where to begin. I'm in a little over my head trying to keep the best of both worlds between just running with the Qualcomm QTI perfd kernel driver, and cutting over to using Google's libperfmgr with power hinting, and their corresponding low memory killer drivers (the "EdwinMoq" commits you may have heard mention of). It feels like I'm getting better performance/battery life right now, with trying to just use some of the "clean up and do some tuning without dropping QTI perfd" commits as an approach, but it might be overkill. If I remove all those things, then we basically end up functioning just like vanilla LineageOS on stock kernel for battery life/performance/smoothness. I'm open to suggestions there.

5. Yes, they were removed. Lock screen was reworked a lot in Android 12, as well as background services, and running the OmniJAWS service (which was intended for older Android versions anyway) apparently broke. Smart charging functionality can be brought back by using the Advanced Charging Control (acc) Magisk module. Best results seem to be by installing the last release of AccA (the graphical front-end), and then manually setting it to use acc module v2022.2.22.1 (newer "android 12 compatible" ones actually kinda fail to work), and then check for a charging switch that supports "battery idle mode" (and toggle on "prioritize battery idle mode").

6. Quick Settings and data handling in Android 12 is... man I don't even know. See point #1. It's not just our device though, from what I've seen scroll by in the crDroid maintainer chat.
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
Status update (11 August):

There's a lot of stuff I'd like to work on fine-tuning, because I might not be a pro AOSP dev, but I like having things feel polished.

LineageOS has been working on merging the August ASB, maybe they're done by now; and I know Neobuddy89 has been working on merging that into crDroid sources (it wasn't ready to build/test as of a few days ago, but probably fine now).

We finally hit summer weather here and it's been too hot for me to work in the back room where my build computer (and monitor setup) lives, and my wife took the summer off teaching and I've been busy working... And working on real life household projects, cleaning, repairs, dealing with the aftermath of my cousin-in-law passing away, taking care of the kids since school is out; lots of things.

I want to fine-tune things of course, but I'll have to save that for the August security patch or later.

I'll just throw 7.20 (whatever test version) and 8.7 test 2 out to OTA for now as the official releases, because "real artists ship"... And I can't sync crDroid sources now to keep working on July ASB releases because it would probably end up pulling in August changes anyway.

Definitely seems like they've been good enough to release for weeks, I've been daily driving and haven't run into regressions, and I can't let "it's not perfect yet!" prevent people from getting updates.
[OnePlus 6 & 6T Cross Device Development] runtosafety:
Just updated, I'll see if 8.7 has fixed that.

See the spoiler below for logs.

NikGApps Basic. Yeah, I only noticed it's not a recommended option after installing (although that's what I used on crDroid 7 where I didn't have that issue).

Spoiler content hidden.
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
Everything blew up this summer in real life.

I finally pushed the 8.7 test 2 that I've been using as a daily driver personally and everyone in Telegram seems to have been more than happy with to OTA as the official July 2022 ASB release, sorry it's like a month late.

The July patch took a long time to merge, and August even longer, but it'll take me a while to release August unless I just skip working on my backlog of bugfix notes entirely.
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
Okay, I took a mental health day to work on Android stuff. :D

First test builds of 8.8 will be going up tonight in the Telegram group if anyone wants to join & try them out!

Had to drop Camera2 (the basic AOSP camera) since that little 5MB makes the difference between MindTheGapps 12.1 arm64 & Magisk both being able to install and updater able to correctly process addon.d scripts when installing the zip, and a bootloop because it couldn't quiiiiite finish copying over the privapp permission XMLs to system/product/. Stupid tiny system partition...

No device-specific bugfixes yet in my trees, just testing with the most recent lineage changes & crDroid 8.8 sources.
[OnePlus 6 & 6T Cross Device Development] 3dawg:
Appreciate the work you're putting in.
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
Hey folks, I'm having trouble with the 8.8 update test builds.

The "system" partition is getting too full with 8.8 for some reason, and it seems to be causing bootloops for some people when they try to update to it (either with Settings > System > Updater while booted into system, or while adb sideload flashing from recovery).

I've run into this on my testing fajita when trying to flash or update the ROM, MindTheGapps (12.1-arm64-20220605_112439 build), and Magisk (25203 canary build). Unfortunately, until we switch to retrofitting dynamic partitions, this means that just about the only way to reliably cut down on the used space in the system partition is to do something about the included OnePlusCamera apks (Camera, CameraService, and Gallery specifically).

There are two good ways to do that, and I've tested them both. Either...

Ship an older version of the OnePlusCamera app, which is about 40MB smaller, but then would require manually re-installing the apk file to remain at the current version, or...

Remove all three prebuilt apks from the ROM zip, and provide a magisk module instead for those who actually use them, since Google Camera is better in almost every way except for 60fps video recording.

Option 1 (ship older version of the OPCam app):

Pros:

Easier to keep things mostly the same for people who don't read release notes or documentation

Cons:

Doesn't save as much space in the system partition

Older version of camera app probably has even worse image quality

Requires downloading & reinstalling an apk file just to remain at the current version

Option 2 (drop apps from ROM zip and use Magisk module to overlay them back into system_ext/priv-app/):

Pros:

Saves more space in system partition, which is the goal

Stays on latest versions of apps

No more useless OP camera/gallery apps for those that hate them

Cons:

Just updating the ROM without reading release notes/instructions will result in reduced functionality

Requires manually downloading/copying three apks to your phone & in-place update installation if you don't install the module before the 8.8 ROM update in order to make Android happy again & prevent FCing

I guess I can't brag about shipping fully-functional OnePlusCamera built-in any longer... although using the module, it still retains the same 100% functionality as in 8.6 & 8.7 versions

Other

Requires Magisk (I guess this is a con if you don't want to install Magisk; I always use it anyway for hostfile-based ad blocking, but some people are strange and dislike the idea)

So! Who wants the "ship older version" option? React with a "Haha" 🤣. Prefer the Magisk module approach? React with a "Love" 😍

Feel free to reply & discuss, or hop in the TG group.
[OnePlus 6 & 6T Cross Device Development] kmr168401:
:love:
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
Welp, I accidentally made it work installing them to /vendor/priv-app/ so... I guess we go with door number three.
[OnePlus 6 & 6T Cross Device Development] truquete:
Just finished upgrading from crDroid 7 by following the instructions and a clean install. Used Swiftbackup and so far everything very very smooth. I will report after testing for a few days. Thanks Jordan for your huge effort. This is epic.
[OnePlus 6 & 6T Cross Device Development] truquete:
After a week of usage, everything rock solid. I have noticed a daily message offering an update to Android 13, what probably is an issue with upstream crdroid. Other than that, everything running smoothly.

I am surprised how few people are paying attention to this thread. Thing is, you hardly find this thread in xda when searching for rooms. Even searching in Google for "xda crdroid oneplus 6" will point you to less relevant threads. I usually have to find it through crdroid page, which I guess is not how people should find one of the best ROMS for enchilada out there. Any way to improve the exposure?
[OnePlus 6 & 6T Cross Device Development] ravidevani:
Will move to this ROM once we get A13 builds.. No point in clean flashing again.. crDroid 9 should arrive soon according to their website... right now I am on EvoX A13
[OnePlus 6 & 6T Cross Device Development] cobrax2:
hi guys

any way to make wifi cast/miracast and nfc/bt work correctly?

thanks
[OnePlus 6 & 6T Cross Device Development] nostri:
Nfc payment work for me
[OnePlus 6 & 6T Cross Device Development] HannibalLecter:
does this ROM have Unlimited google photos storage?????
[OnePlus 6 & 6T Cross Device Development] cobrax2:
in known bugs it says that there are issues. i'm more interested in bt file sharing and audio than nfc payments though. also wireless display
[OnePlus 6 & 6T Cross Device Development] truquete:
According to Google photos "this Pixel can backup unlimited photos and videos at no charge." I haven't tried it and wouldn't like to try it personally, since in my opinion this is an abuse of Google's policies, plus you never know if they could figure it out at some point and end up losing access to your memories.
[OnePlus 6 & 6T Cross Device Development] truquete:
No. It says there are some issues when reading data through nfc, but not when sending. It is explicitly stated that Google pay should work. The country where I live doesn't use it though, so I cannot confirm.
[OnePlus 6 & 6T Cross Device Development] truquete:
Even if crdroid 9 arrives soon, this doesn't mean that it will arrive soon for oneplus 6. For this to happen, you probably also need a lineageOS port, and a volunteer able to do the port to crdroid. Jordan does he's best but I would hold my breath on this happening anytime soon.
[OnePlus 6 & 6T Cross Device Development] crisontur:
Hello,

this rom has safetynet passed by default and without root banking apps working?

thanks
[OnePlus 6 & 6T Cross Device Development] jmno c:
Hello, I don't understand a bit, i.e. the camera oneplus with 60 fps works on crdroid?
[OnePlus 6 & 6T Cross Device Development] sebcio2804:
yes
[OnePlus 6 & 6T Cross Device Development] Bananikus:
Bro, the only reason i switched to this ROM is because you made one plus camera working. I don't get what you mean that Google camera is better in any way, it was absolutely unstable for me, slow and with worse picture quality, with most important features not working, like 60 fps video recording (bro, that's like the most important feature ever and i don't want to say a word more, i was dreaming of it before that was even a thing) portrait mode, slo-mo (that's seem to be still broken?) I would rather go to stock, if this haven't been solved. So thank you for bringing that and believe me, for me it means a lot, thanks to this i am not thinking about changing the phone again.
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
Okay, hi everyone! So I'll probably edit this post later once I've got more time, but quick status update:

- Still busy AF in real life

- 8.8 will be out soon, and moves OnePlus Camera & Gallery to vendor partition so there should be room for larger GApps installs (for clean install).

- I'll make a "OP Camera" troubleshooting post here for what to do if it's behaving funky for you after updating, but short version is to clear app storage & cache for OP Camera & OP Gallery, and possibly download the apks directly and do an "update this app" install using the same version, and then it'll get its head on straight and work properly.

- I know 8.9 is already out for other devices, I've just been way too busy and want to push 8.8 official. It's been release-worthy for a long time and I've been daily driving it, it just takes time to go through the checklist and especially write proper release notes/make sure everything's still current in the first posts of the thread.

- I did a test build of crDroid 9.0 (Android 13), and it 1) compiled eventually, 2) booted, and 3) no network access for any apps. That wasa a month ago. It's probably all fixed in upstream sources now, and I'll be shifting attention to that soon. But let's get Android 12 updates that are already ready pushed to official, hey?
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
I know 60fps video recording doesn't work correctly in any of the GCam mods I've played with, but if you want just about everything else working better (especially with HDR+ enabled), and both frame rates for slow-mo functioning WITH sound out-of-the-box, try out the old DMGC v4.5 based on GCam 7.3; it works pretty darn well.

Or even MJL Minilux (7.3-based) with Juan-All XML (no postprocessing) for photography, video be damned.