Search results

December Eleven update is up. Check on the website for further changelog and info. Also, I'd like so much to thank everyone for those 2 years developing for dipper, for all the support and everything else. It was certainly an era for me that I'll never forget. The device will be maintained now...

1 - Plus Edition thing 2 - No 3 - No, on Plus there's DT2L on the Status bar, but on the Pixel Launcher it's impossible.

1 - That seems too much relative, I'm not having any fast drain, and some other people have been reporting that battery actually improved. 2 - Youtube videos aren't freezing in here, Instragram may be because of the fact that it's a facebook app (the same happened in the start of Q development)...

1 - Noted, but I unfortunately don't have how to test in here, as no where in my city Google Pay is supported. 2 - Will come back soon 3, 4, 5 & 7 - Those are plus edition features only. Plus Edition builds based on R just going to happen only next year (And no, not around January or February)...

As long as TWRP doesn't fixed the encryption support and decryption point for properly flash on it (that includes not only TWRP but also others such as OFox, PitchBlack and etc.) with Android 11 the override will still be happening.

That's actually more confusing. The issue that I mentioned was: Whenever, if you have navigation gestures on, the recognition area on the bottom will move along with the same amount that you'll have of the status bar "moving", being lower (hide the notch), or higher (returning to a visible notch...

All those feature you requested are from Plus Edition builds which are coming just next year. About the home screen grid: We didn't touch anything from the launcher app, so as far as we know, it came like that from Google itself. Wait does the bottom gesture nav area is not working, or just...

It's planned indeed.

Read the build changelog space on the website, the warnings are there for a reason, and even one regarding this point. Not happening in here. Logs are welcome. If you read the second post I did in here about the first Android 11 build, you should've noticed that is already known, and even...

The only known bug is: Whenever you hide the notch and vice-versa the gesture nav area in the bottom moves along with it, it's unknown why yet, but rotating the screen to landscape and back to normal fixes it. Rest everything is working. Happy flashing

I've just released an Android 11 build. Be aware that as of now I won't create a thread due the instabilities XDA is going through due the migration from the old website to the new one. Feel free to report and send logs in here.

Ok, this is can be kind of annoying/repetitive, BUT as no search option on thread is available... On some threads I noticed that some pages are a no-go (dunno if the migration still happening, but still I'll let it in here), also noticed that some posts are completely out of order too. Also...

Ok, despite XDA fucking up the migration and messing up some posts (won't put all the blame on them, but still... F), about A11: It will come until this weekend for sure, just looking to fix a minor bug related to the gestures whenever hiding the notch and/or vice-versa.

Just pushed it.

If you mean without any CAF stuff, no, that'll mean just more work, as the HALs are completely different from CAF ones, and that'll mean more stuff broken while in the process of Aospfying the device. All ROMs that are called AOSP have the same bit from CAF as Lineage, and basically all apart...

Well, sadly those can't simply be deleted, as back with the displayfeature. Those need to be there. The sfp_execption I fixed using a fix that a friend of mine did over violet and it worked perfectly (I haven't upload the changes yet), the GraphicBuffer error I did the shim and it worked but...

No OTA from Q to R. I think the same from Pie to Q. Some people didn't wip anything at all and it was all fine. Still a clean install (which means just the wipes, no format data) is recommended If you mean a separated thread here on XDA, then yes.

Yeah. I'm trying to understand what happened, because I did that back on Q bringup for Dipper and it worked just fine. I don't know if it's trying to get from a different path or what, anyway, I'll put the lib patched on ghidra later on to see what is happening on it.

Ok, I read the logcat and I can see that other than those that you wrote down it has a lot of dlopen errors too, which are killing the camera service HAL, whether cause of missing blobs or missing symbols.

If you mean a custom kernel project, I had one until some time ago but stopped after sometime. Either way for MIUI custom ROMs it would be a problem without a Q based kernel release.

1 - Wrong, they have a similar sensor but not exatcly the same 2 - They are using prebuilt vendor and kernel, while I'm building custom vendor and using a cleanup kernel without Xiaomi ricing or bs. (No I won't go down this path although I have a vendorless and prebuilt kernel tree on my tucana...

Welp, that just confirms even more my theory that unless Xiaomi do a proper kernel code release getting tucana back cameras to work won't be possible at all with the camera Q blobs at least. I may try again the Pie blobs again, so let's see (And I really hope this time I don't end up looping...

FYI there won't be an update this month. Why? The October security patch is just a change of the security patch date string (literally that's all that came from Google). Also there isn't any new device side fixes so as per that September updates are fine to use. November might be the start of...

I'll be updating Q until the R sources are ready

Just a fact that the only thing remaining to work on is on camera kernel drivers. I'm doing this right now taking advantage of holidays tommorow (Monday Oct, 12th)

No. I've had enough of people complaining about the GCam pre-shipped with the ROM to be completely honest.

MIdo has a completely different screen technology to start with, not to mention that as per that it'll have completely different screen configurations. Dipper has an Samsung AMOLED EA8074 only, while mido has an tianma lcd, and other two IIRC but that I don't remember their names right now.

You're having both oversaturated and washed colors? Wow das crazy. Jokes apart, if you you guys mean all the interface getting washed colors after running an HDR video or during it run, that's normal. It's being like that since Pie.

That's not going to happen. Unfortunately that means more buggy than as it is right now. Don't forget that Xiaomi might have done hacks into the display HAL over stock and many more software parts that over AOSP custom ROMs just causes bugs, such as the screen being stuck in the weird...

As yourself said, no, it's not and by this time right now never for sure. The device was launched with A-Only partition schema, and to be completely honest, there's no such need for we to convert from A-Only to A/B. As for the custom ROM that changes nothing or will only cause more headaches for...

Search tool is a thing and literally answered that on the previous page, oof Sent from my MI 8 using XDA Labs

About HDR: Whether was that or a too much saturated behavior, due some change that Xiaomi did over display configs to make an HDR profile that wasn't an actual HDR mode. To avoid the screen get to much saturated due the false HDR that Xiaomi did over the display configs I simply let the display...

That's Play System Updates Security Patch. I have the same behaviour in here for some reason. 1 - I have auto rotate in here, works fine 2 - Did a bunch of calls yesterday for transfer of address of some stuff, the screen is getting touch locked during calls is just working fine in here too.

I may have a new lead over camera issue, but I'm moving to another place so I'm busy with the moving rather working on the device. Once the moving is done I'll return working on the device more often again.

If you format data yes, if you wipe /data partition, just the system-wide data will be wiped. nothing related to the internal storage files will be removed.

ROM Update! Clean Install is recommended! Download link Changelog Standard/Plus Edition: PixelExperience: - September security patch (backported from A11) - Improved the face unlock - General Bug fix Device specific: - Kernel upstream (4.9.236) - Some fixes here and there WARNINGS: -...

Regarding the touch issue: I have that sometimes even on twrp, same as th.marci situation, whenever I plug in the charger. Regarding the September Update: Today later on. Regarding a PE 11 Update: Dipper will receive for sure, however, neither anyone in the ROM team is rushing to do the...

Those are already enabled on the defconfig and merged into kernel drivers. The only things I haven't tried yet: Try pie blobs, or try make everything on kernel drivers inline with tucana-p-oss/phoenix-q-oss

Yes and yes, although the boot.img will be reflashed, so root/su will be lost while at it.

Yes, go to dev options if on standard edition builds and look for the cutout option there. If using a Plus Edition build go to display settings and look for the same settings.

I recommend install firmware 20.8.3 CN, but I don think it's going to be any problems if you're using a global fw already. I'll put the minimum fw limitation once the camera is fully fixed.

Well, for it work you'll need to clone/download android_vendor_lineage repo to a folder vendor/lineage and trees must be on device/xiaomi/{tucana/sm6150-common} for extract-files.sh to work. Then just do a bash extract-files.sh on the one in the tucana specific tree. For the actual binaries to...

Extract-files.sh comes in hand XD. If you mean the proprietary-files list that was a script tool that another dev did and I just went for it. Then I did just the organization and gave it a try (if you check a few pages back you'll see a major ****up with displayfeature, which was involved in...

https://sourceforge.net/projects/tucana-lineageos/files/ There ya go. Use at your own risk. Known Issues: - Back cameras - NFC - Proximity Sensor I won't make a thread for the time being. Will create one once back cameras are working. If anyone wants to collaborate on fixing the current...

MGC_7.3.020_RPII_v0f_tuning.apk by marlin-ku. I did some little tweaks, but I lost the modified apk.

As said in the changelog, it was removed the GCam and switched to SnapCamera, which is a source-built app made by Qualcomm. It's also the default app for LineageOS. Sent from my MI 8 using XDA Labs

Not actually. Take it as the WiFi interface that Pixel devices use, however with the addition of the VPN feature for the public wifi connection where it's supported and so on. The WiFi interface previously there before the WiFi-ext is back there now.

SnapCamera is the same as the one over LineageOS. It should be the same way as on LOS.

People kept complaining about "Can't use the GCam that I like" and stuff like that, so shipped with Snap so then they can freely choose about that. And wifi-ext was removed due complains from some maintainers, and therefore Silva decided to remove it entirely from the ROM source.

ROM Update! Clean Install is recommended! Download link Changelog Standard/Plus Edition: PixelExperience: - August Security Patch (android-10.0.0_r41). - Wifi-Ext is gone. - Imported new translations - Others fixes Device Specific: - Kernel upstreamed to 4.9.234. - Removed GCam, and...