Development [CLOSED][ABANDONED] [OFFICIAL] [Rosemary/Secret/Maltose] Project Kasumi 1.x for Redmi Note 10S

[Oxydeme]

Apparently the thx button doesn't work atm ,
First of all, gonna see for the latest available build i guess;
I noticed Google chrome and natural browser shiped in, keeps crashing after several times,
Sometimes it crashes every 3 mn sometimes every 15,
Yep indeed, you're right, it is fast charging!

Glad to hear you're working on v2, will look after it, be sure

for the cpu that's not a big deal actually, was just having fun {re}discovering things that were in the dev settings
And please, what about the Safety net fix, have you thinked a bit about it? would you -maybe-inculde it directly as op of it said it would be a better idea?

Thanks boot.brain.think.flash();

 

[Oxydeme]

Unfortunately no. Kasumi 1.x.x are all Android 11. Android 12 Kasumi will be possible only once our internal tests will be done and I finally finish working on Kasumi v2. Hundreds hyped, gradually widening audience, looking into the release of it. xD

Well, dudess

I did try installing directly the update via internal updater, it ended up i was still running previous build strangely

Excuse me, as I'm not an engeneer, a clear developper, or related to such stuffs in the first place, sometimes, I say sh*t or do sh*t Would better call myself an experiencer xD

Well, just flashed the actual latest build, will test this out

Edit: just flashed TWRP, included the rom, the bootfix and at the first try it booted!
Congratulations!

 

[Oxydeme]

And I did Bad things,
Yesterday I used to flash your update right?
Just booting it I realised I forget MTGapps,
So I tough I would just reflash correctly, no, everything went wrong I ended up with a freaking bootloop and no working correctly fastboot or recovery x)
Long story short, I battled hard with it as fastboot didn't recognized the phone, during 2-3hours lol
I ended up a 1:30 am restarting my computer several times and saw myself tweaking params to replace Android by Xiaomi composite device and finally could reflash stock using MiFlash, damn.

Will retry in the day, when will be less occupied, back soon for news

That's not the end, will be patiently waiting for Kasumi A12

And will restart to work with Backups I guess

Edit: ok, flashed successfully Kasumi latest build, actually running it at the time of writing, I just finished setting it up
Edit2: Chrome still crashing, RIL related? (Only annoying point ATM)
Edit3: Glas to see Gaming Mode popping up o/

 

[windowz414]

Apparently the thx button doesn't work atm ,
First of all, gonna see for the latest available build i guess;
I noticed Google chrome and natural browser shiped in, keeps crashing after several times,
Sometimes it crashes every 3 mn sometimes every 15,
Yep indeed, you're right, it is fast charging!

The crash issue is a platform-wide issue and will be resolved with the next release (When Lineage merges in August '22 patch on R, I merge them in within a day or two, Rosemary will take 4-5 days to receive new releases given we're using a single server to mass-build all devices). Apparently it was the `zlib` I'm using causing such crash. This has been the issue ever since 1.0 Staging and couldn't understand why until now.

Glad to hear you're working on v2, will look after it, be sure

Eh, it'll happen for Rosemary only when the other developer pushes his A12 trees. Seems to work much better than my 11 trees. ^^;

for the cpu that's not a big deal actually, was just having fun {re}discovering things that were in the dev settings
And please, what about the Safety net fix, have you thinked a bit about it? would you -maybe-inculde it directly as op of it said it would be a better idea?

I have done some more researches. And apparently SN passes only if you don't install Magisk. If you install Magisk, just make sure to enable Zygisk+Enforce Denylist, then add all processes of Play Services in Denylist, followed by a reboot. Of course you need to take care of apps finding out root status individually as well. I was able to use Turkish "ÖSYM Aday İşlemleri Sistemi" and my banking app just fine when I add both of them into denylist individually along with Play Services.

Thanks boot.brain.think.flash();

 

[windowz414]

And I did Bad things,
Yesterday I used to flash your update right?
Just booting it I realised I forget MTGapps,
So I tough I would just reflash correctly, no, everything went wrong I ended up with a freaking bootloop and no working correctly fastboot or recovery x)
Long story short, I battled hard with it as fastboot didn't recognized the phone, during 2-3hours lol
I ended up a 1:30 am restarting my computer several times and saw myself tweaking params to replace Android by Xiaomi composite device and finally could reflash stock using MiFlash, damn.

The bootloop on the latest build is just some missing priv-app permissions for Lawnchair, for why I also pushed a `kasumi13bootfix.zip` in the downloads as well. All it does is copying over proper permissions XML into `/system/system_ext/etc/permissions/` for permissions to be granted properly. Ah and yes, you need to format data afterwards because all permissions are already written into data and formatting data is the only solution to get rid of it.

EDIT: For GApps, we only support MindTheGApps. And I don't really recommend anything other than flashing GApps builds given that we're at dynamic partitions and I'm not entirely sure if GApps ZIPs can resize those...

That's not the end, will be patiently waiting for Kasumi A12

Well, if you have a POCO X3 Pro actually, I can slowly give some test builds on Telegram to you if you're willing to see what am I working on and help me get it up until Rosemary gets it. Just remembered to say this now that you mentioned it for the second time.

Edit: ok, flashed successfully Kasumi latest build, actually running it at the time of writing, I just finished setting it up
Edit2: Chrome still crashing, RIL related? (Only annoying point ATM)

As stated in the previous post, it's just different `zlib` causing problems. Switching to AOSP one fixes it, but brings another issue: The boot animation is s l o w .

Edit3: Glas to see Gaming Mode popping up o/

Gamur spotted. xD

 

[windowz414]

Well, dudess

Forgot to reply this one.

I did try installing directly the update via internal updater, it ended up i was still running previous build strangely

A/B talent. When boot fails, your device switches slots and boots from the other slot. LineageOS Updater installs new updates into the inactive slot, and your next reboot is to that slot. Just in case, the old slot is still kept intact so you're thrown into old version because you booted into the same slot in the end of the day.

Excuse me, as I'm not an engeneer, a clear developper, or related to such stuffs in the first place, sometimes, I say sh*t or do sh*t Would better call myself an experiencer xD

Don't worry, that way of yours sometimes reminds me of my old Android One 2nd Gen times, in which I was just an MVP tester.

Well, just flashed the actual latest build, will test this out

Edit: just flashed TWRP, included the rom, the bootfix and at the first try it booted!
Congratulations!

Glad to hear! Enjoy!

 

[Oxydeme]

Forgot to reply this one.


A/B talent. When boot fails, your device switches slots and boots from the other slot. LineageOS Updater installs new updates into the inactive slot, and your next reboot is to that slot. Just in case, the old slot is still kept intact so you're thrown into old version because you booted into the same slot in the end of the day.


Don't worry, that way of yours sometimes reminds me of my old Android One 2nd Gen times, in which I was just an MVP tester.


Glad to hear! Enjoy!

Answering the whole thing would be actually a bit difficult, would answer quoting a part of it

Will stay tuned for the next release
Glad you found from where the problem was starting from,
No, I don't use magisk, in fact, by the past only thing i used to use.. Was chainfire su
The bootloop i'm talking about was due to clearly m'y mistakes in the end, cause as told, last bootfix and so on were working as expected, i just f*cked my install process,
Not at all, only Rosemary actually x)
Was just testing my app, i saw it poping up
OK so, cause of A/B, must use only TWRP, but, how does Xiaomi itself Handke it? If you find out, you may have a path
So far, your build works pretty well i must say

Edit : Oopsy, seems that bluetooth doesn't work properly

@windowz414
Edit2: During a call, using the speakers isn't a problem, but getting back to classic call use, made the microphone to shut down, without pressing the button if fact.
Was speaking with my wife, didn't clearly heard so i used the speakers, once i turn the speakers iff the mic turn off as well and once i re turn the speakers on, she started hearing me back; strange

In fact, once you use the speakers during a call you need to stay with it, otherwise people won't hear you

 

[windowz414]

Answering the whole thing would be actually a bit difficult, would answer quoting a part of it

Will stay tuned for the next release
Glad you found from where the problem was starting from,
No, I don't use magisk, in fact, by the past only thing i used to use.. Was chainfire su
The bootloop i'm talking about was due to clearly m'y mistakes in the end, cause as told, last bootfix and so on were working as expected, i just f*cked my install process,
Not at all, only Rosemary actually x)
Was just testing my app, i saw it poping up
OK so, cause of A/B, must use only TWRP, but, how does Xiaomi itself Handke it? If you find out, you may have a path

Well, Xiaomi handles the update installations exactly the same way as Lineage updater does; just under a bit fancier installer. You can still use LineageOS recovery and it will work about the same as Xiaomi recovery, only difference is you can actually sideload stuff and choose to clear just cache and several more stuff like that.

So far, your build works pretty well i must say

Edit : Oopsy, seems that bluetooth doesn't work properly

I've been actively using my Bluetooth earphones and they were all fine.

@windowz414
Edit2: During a call, using the speakers isn't a problem, but getting back to classic call use, made the microphone to shut down, without pressing the button if fact.
Was speaking with my wife, didn't clearly heard so i used the speakers, once i turn the speakers iff the mic turn off as well and once i re turn the speakers on, she started hearing me back; strange

In fact, once you use the speakers during a call you need to stay with it, otherwise people won't hear you

So this is what the issue actually was.

Thank you, I'll see what can I do about it.

 

[Oxydeme]

Well, Xiaomi handles the update installations exactly the same way as Lineage updater does; just under a bit fancier installer. You can still use LineageOS recovery and it will work about the same as Xiaomi recovery, only difference is you can actually sideload stuff and choose to clear just cache and several more stuff like that.

I've been actively using my Bluetooth earphones and they were all fine.


So this is what the issue actually was.

Thank you, I'll see what can I do about it.

Thanks you,

For the bluetooth, i assume you are right,
But tried to send a file from my computer to my phone, ans i couldn't, failed all the way.

Yep ans this one seems really annoying

 

[Oxydeme]

Battery holds goodly
Normal usage, no charging from after flash, will charge it tonight i think
No fast drain, clearly well balanced

 

[killer_v41]

Is this an official rom? Also does it retain l1 certificate and can it be daily driven?
Edit: what are the options for custom recovery since twrp is not available for Redmi note 10 s

 

[Oxydeme]

Is this an official rom? Also does it retain l1 certificate and can it be daily driven?
Edit: what are the options for custom recovery since twrp is not available for Redmi note 10 s

As suggested by title per OP, it is.
I use it actually as my daily driver, it contains several bugs actually such as chrome or native browser crashing from times to times and, l1 certificate should be present, see scsht below,
Also unnoficial TWRP for A11 by Woomymy or OrangeFox recovery are available at the moment.

Just be sure to be running global rom before proceeding anything.

That said, you must :
-Have an unlocked BL (procedure av. Here and there),
-Running Android 11, Miui 12.5.16 Global ROM,
-Install the recovery of your choice,
-Switch to slot B,
-Follow OP procedure in the end,

Optionnal: MindTheGapps/Magisk, beware, if you boot you ROM once before flashing any of those 2, you're good to reflash everything as it won't get flashed, i did the test

 

[averagexiaomiuser]

I have no idea if this is a dumb thing to ask, would this be safe to run on EEA, my phone is eea and would it affect anything if i flashed global? Or is eea supported

 

[Oxydeme]

I have no idea if this is a dumb thing to ask, would this be safe to run on EEA, my phone is eea and would it affect anything if i flashed global? Or is eea supported

Hey there, I've been running EEA as a base on my RN10S, it's a requirement to be running Global before making any kind of step

 

[Oxydeme]

Download & instructions:

• Install MIUI 12.5.16.0 Global if you haven't already. (**NO, NONE ELSE WILL WORK!**)
• Fully install custom recovery of your choice.
• Switch to slot B (Reboot > Slot B), and reboot to recovery.
• Flash the ROM. You can also sideload it with ADB if you want to.
• !!! If you'll flash Magisk, you'll need to enable "Reflash (recovery) after installing a ROM" after choosing the ZIP as well !!!
• After flashing, reboot to recovery.
• Format data.
• Flash Magisk if you want to.
• Reboot to system and enjoy!

@averagexiaomiuser

 

[windowz414]

ROM has been discontinued and all downloads have been taken down.

 

[Oxydeme]

That's fair

 

[shenoayad]

View attachment 5664591

#include <std_disclaimer.h>
/*
* Your warranty is... still valid?
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/

Another weebified custom ROM aiming to be a home for weebs - Based on Project Materium, an optimized LineageOS-based Android aftermarket firmware with extra features, developed by people all over the world.
Quoting the LineageOS description:

We offer vanilla, GApps and AuroraOSS variants. If you install a vanilla variant, the only supported GApps package is MindTheGapps (GApps/AuroraOSS builds are not available for a few devices due to space issues).

Download & instructions:

• Install MIUI 12.5 if you have updated to anything Android 12.
• Fully install custom recovery of your choice.
• Flash the ROM. You can also sideload it with ADB if you want to.
• !!! If you'll flash Magisk, you'll need to enable "Reflash (recovery) after installing a ROM" after choosing the ZIP as well !!!
• After flashing, reboot to recovery.
• Format data.
• Flash Magisk if you want to.
• Reboot to system and enjoy!

Download (Taken down due to discontinuation)

IMPORTANT: If you are coming from another ROM, you need to format data (TWRP > Wipe > Format Data > *type "yes"*).
IMPORTANT: If you want to keep Magisk after each OTA, you need to make it flash to inactive slot **right before rebooting** (Magisk > Install (In "Magisk" card) > Install to inactive slot)

About:
Features:

• Latest security patches merged from LineageOS
• SafetyNet passing unconditionally without Magisk/with kdrag0n's SafetyNet fix
• Many optimizations coming from Stellar OS/Project Materium/droid-ng
• New wallpapers & bootanimation
• QS customization (tint, rows customizer, data usage)
• Status bar customization (4G/LTE toggle, new NFC & VoLTE icons)
• Kill app from notification
• Notification pulse
• KitKat-style notification ticker
• Screenshot sound toggle
• Per-app volume
• WiFi & Bluetooth timeout
• Smart Charging & Cutoff
• Sensor, Wakelock and Alarm blocker
• Battery info on lockscreen
• Improved microG support (signature spoofing, location support)
• ...and more! (We accept suggestions!)

What's working:

• Almost everything

Bugs:

• Microphone doesn't work when speaker is enabled during calls.
• You tell me.

Sources are available at https://github.com/ProjectKasumi and https://github.com/Kasumi-Devices

Full list of device sources used;

• Device tree
• Linux kernel tree used
• Vendor tree for proprietary blobs

ROM Founded By: Yuki (AITEx64)
ROM Developed By: Beru Hinode
ROM Designed By: Ayuko, Qirkl and UsiF.
ROM OS Version: 1.3 "PoPiPa" R2
ROM Kernel: Customized Linux 4.14.186 from MiCode
ROM Firmware Required: MIUI 12.5.16.0.RKLMIXM (Global)
Based On: Project Materium 1.0 (LineageOS 18.1)

Version Information
Status: Discontinued
Last Stable Version: 1.4 "PoPiPa"
SELinux Status: Permissive
Initial Release Date: July 20, 2022

Good

 

[Oswald Boelcke]

ROM has been discontinued and all downloads have been taken down.

Thread has been closed!