yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] lotte67890:
Here we go... I grabbed the register_status file 3 times since it´s changing from time to time...

SMB34x Configuration Registers Detail

==================

Reg00h: 0x9c

Reg01h: 0x73

Reg02h: 0x93

Reg03h: 0xe3

Reg04h: 0x0e

Reg05h: 0x1e

Reg06h: 0x71

Reg07h: 0xe6

Reg08h: 0x08

Reg09h: 0x25

Reg0ah: 0xbe

Reg0bh: 0xa5

Reg0ch: 0x00

Reg0dh: 0x14

Reg0eh: 0xd5

Reg30h: 0x02

Reg31h: 0x00

Reg35h: 0x00

Reg36h: 0x01

Reg37h: 0x00

Reg38h: 0x50

Reg39h: 0x10

Reg3ah: 0x03

Reg3bh: 0xa3

Reg3ch: 0x3c

Reg3dh: 0x05

Reg3eh: 0x0a

Reg3fh: 0x91

==================

Reg00h: 0x9c

Reg01h: 0x76

Reg02h: 0x93

Reg03h: 0xe3

Reg04h: 0x0e

Reg05h: 0x1e

Reg06h: 0x71

Reg07h: 0xe6

Reg08h: 0x08

Reg09h: 0x25

Reg0ah: 0xbe

Reg0bh: 0xa5

Reg0ch: 0x00

Reg0dh: 0x14

Reg0eh: 0xd5

Reg30h: 0x02

Reg31h: 0x00

Reg35h: 0x00

Reg36h: 0x01

Reg37h: 0x00

Reg38h: 0x50

Reg39h: 0x10

Reg3ah: 0x01

Reg3bh: 0xa3

Reg3ch: 0x3c

Reg3dh: 0x05

Reg3eh: 0x0a

Reg3fh: 0x93

==================

Reg00h: 0x9c

Reg01h: 0x76

Reg02h: 0x93

Reg03h: 0xe3

Reg04h: 0x0e

Reg05h: 0x1e

Reg06h: 0x71

Reg07h: 0xe6

Reg08h: 0x08

Reg09h: 0x25

Reg0ah: 0xbe

Reg0bh: 0xa5

Reg0ch: 0x00

Reg0dh: 0x14

Reg0eh: 0xd5

Reg30h: 0x02

Reg31h: 0x00

Reg35h: 0x00

Reg36h: 0x01

Reg37h: 0x00

Reg38h: 0x50

Reg39h: 0x10

Reg3ah: 0x01

Reg3bh: 0xa3

Reg3ch: 0x3c

Reg3dh: 0x05

Reg3eh: 0x0a

Reg3fh: 0x90

The Nexus is charging with max ~830mA

Thanks for your effort!!!
[Nexus 7 Android Development] shaggyskunk:
k - Thanks that's why I was asking about sideloading - My brain isn't working properly today (some might say "ever" lol) Thanks AndDiSa??️
[Nexus 7 Android Development] OlliWi:
[MENTION=4943417]lotte67890[/MENTION]

I see two register values that might explain your charging issues but before we try to change those values, i want to know, which grouper board revision you have.

Reboot your nexus and then open a terminal and type

dmesg > /sdcard/download/dmesg.txt

Attach the created "dmesg.txt" file to your next posting.
[Nexus 7 Android Development] lotte67890:
Here it is, btw. it´s a Tilapia...
[Nexus 7 Android Development] OlliWi:
OK, found it. It´s the same as mine :good:

btw. the hardware-board is always called "grouper".

[ 4.359589] smb347_charger: [smb347_init] project_id=1, pcba_ver=1, dock_in_gpio=117

Now do the following:

a) disconnect your Nexus from USB/DOCK (battery should not be empty of course)

b) open a terminal and execute the following commands:

i2cset -f -y 4 0x6A 0x30 0x82

i2cset -f -y 4 0x6A 0x06 0x75

As always on your own risk!

Good luck!
[Nexus 7 Android Development] lotte67890:
I did as you suggested and I can see that the Nexus is now charging just below 900mA, which means it charges a little bit higer. Here is 2 times the reg_status, as I can see that there are changing values:

Reg00h: 0x9c

Reg01h: 0x76

Reg02h: 0x93

Reg03h: 0xe3

Reg04h: 0x0e

Reg05h: 0x1e

Reg06h: 0x75

Reg07h: 0xe6

Reg08h: 0x08

Reg09h: 0x25

Reg0ah: 0xbe

Reg0bh: 0xa5

Reg0ch: 0x00

Reg0dh: 0x14

Reg0eh: 0xd5

Reg30h: 0x02

Reg31h: 0x00

Reg35h: 0x00

Reg36h: 0x01

Reg37h: 0x00

Reg38h: 0x50

Reg39h: 0x10

Reg3ah: 0x01

Reg3bh: 0xa3

Reg3ch: 0x3c

Reg3dh: 0x05

Reg3eh: 0x0a

Reg3fh: 0x96

SMB34x Configuration Registers Detail

==================

Reg00h: 0x9c

Reg01h: 0x73

Reg02h: 0x93

Reg03h: 0xe3

Reg04h: 0x0e

Reg05h: 0x1e

Reg06h: 0x75

Reg07h: 0xe6

Reg08h: 0x08

Reg09h: 0x25

Reg0ah: 0xbe

Reg0bh: 0xa5

Reg0ch: 0x00

Reg0dh: 0x14

Reg0eh: 0xd5

Reg30h: 0x12

Reg31h: 0x00

Reg35h: 0x00

Reg36h: 0x01

Reg37h: 0x00

Reg38h: 0x50

Reg39h: 0x10

Reg3ah: 0x03

Reg3bh: 0xa3

Reg3ch: 0x3c

Reg3dh: 0x05

Reg3eh: 0x0e

Reg3fh: 0x93

May I mention that I´m not absolutely sure that the cable from the charger is in the best condition... I changed the USB micro port in the Nexus just some month ago, but I missed to also buy a new cable... and I´m using the original charger from 2012...
[Nexus 7 Android Development] OlliWi:
I´m still wondering why it switches back to 900 mA input current on the USB port (Reg01h=0x73/Reg3Fh=0x93) while ist starts with 1800 mA input current (0x76/0x96).

Do you have another charger and/or cable that you can try?

Why did you do that?
[Nexus 7 Android Development] radikyrick:
Thanks for keeping alive Nexus 7 [MENTION=2188693]AndDiSa[/MENTION].I need to re-flash magisk after every os update in my tilapia.Is it possible to keep magisk during updates?. Thankyou.
[Nexus 7 Android Development] Flounderist:
+1
[Nexus 7 Android Development] Sam Nakamura:
It's not even necessary to "adb push" the ROM, once you fastboot flashed TWRP and have booted it you can easily drag & drop the ROM file to your N7's internal storage while connected to the PC - MTP is usually working out of the box when booted into TWRP...

By the way, God must have have shared a brain for us 2 because mine usually doesn't work either... Haha :laugh:
[Nexus 7 Android Development] AndDiSa:
Taken from topjohnwu/Magisk:

any ideas to improve the update process are welcome ;)
[Nexus 7 Android Development] Flounderist:
It could be due to the build process. I am used to flash custom ROMs that are usually build as userdebug ones. You are building as OTA, hence addon.d could not be present (I might be wrong).
[Nexus 7 Android Development] CamoGeko:
Nope, due to the way Magisk applies root this isn't possible on any device at the moment. There's no other way but to reflash Magisk after every ROM flash.
[Nexus 7 Android Development] TureX:
Hi! This is last_kmsg , i get reboot in "idle" when is in charge
[Nexus 7 Android Development] AndDiSa:
Thank you very much for the log file. Here I can see an exception in interrupt. I'll have a look at it.
[Nexus 7 Android Development] mikefive:
Hi OlliWi,

as you suggested, i changed the register value to following values:

grouper:/storage/emulated/0 # i2cset -f -y 4 0x6A 0x30 0x80

grouper:/storage/emulated/0 # i2cset -f -y 4 0x6A 0x00 0x9C

still, theres no change in the charging speed:

grouper:/storage/emulated/0 # cat /proc/kmsg | grep current

<5>[10469.700323] bq27541_get_psp current_now = 339000 uA

<5>[10469.700961] bq27541_get_psp current = -339 mA

<5>[10472.327823] bq27541_get_psp current_now = 115000 uA

<5>[10472.328519] bq27541_get_psp current = 115 mA

<5>[10487.442880] bq27541_get_psp current_now = 183000 uA

<5>[10487.444065] bq27541_get_psp current = 183 mA

<5>[10492.206723] bq27541_get_psp current_now = 546000 uA

<5>[10492.207393] bq27541_get_psp current = 546 mA

Register setting now is:

SMB34x Configuration Registers Detail

==================

Reg00h: 0x9c

Reg01h: 0x76

Reg02h: 0x93

Reg03h: 0xe3

Reg04h: 0x0e

Reg05h: 0x1e

Reg06h: 0x71

Reg07h: 0xe6

Reg08h: 0x08

Reg09h: 0x25

Reg0ah: 0xbe

Reg0bh: 0xa5

Reg0ch: 0x00

Reg0dh: 0x14

Reg0eh: 0xd5

Reg30h: 0x00

Reg31h: 0x00

Reg35h: 0x00

Reg36h: 0x01

Reg37h: 0x0a

Reg38h: 0x50

Reg39h: 0x10

Reg3ah: 0x03

Reg3bh: 0xa3

Reg3ch: 0x3c

Reg3dh: 0x05

Reg3eh: 0x0a

Reg3fh: 0x92

tried different cables and chargers, result is still the same- did not come above 600-900mAh.
[Nexus 7 Android Development] OlliWi:
These two Register settings are the only one I identified as different from the ones of people (2, more feedback is welcome:() without charging issues.

Unfortunately without a documentation of the smb347 charger, it is nearly impossible to find out, what they mean.

Reg 05h controls the STAT pin of the charger, BIT (5) of this register seems to enable/diable the STAT pin.

Reg 06h controls the EN pin of the charger, BIT (2) of this register is referenced in some driver code as "charger_error" (#define CFG_PIN_EN_CHARGER_ERROR	BIT(2)).

Try the following:

Set Reg05h to 0x3e and Reg06h to 0x75:

i2cset -f -y 4 0x6A 0x30 0x80

i2cset -f -y 4 0x6A 0x05 0x3e

i2cset -f -y 4 0x6A 0x06 0x75

Good luck!

Attachment: part of circuit design of grouper ,smb347
[Nexus 7 Android Development] lotte67890:
Well, I replaced the USB port of the Nexus due to the charging issue... also I recognized that I got disconnects when connecting the Nexus to my PC... After the replacement the disconnects did not occur anymore.

I now tried another charger (2A) without any difference, still I can only reach 600~900mA. As soon as I got a new cable I will try that also.

Lotte

p.s. Does this help for identifying the meanings of the registers: https://docs.huihoo.com/doxygen/linux/kernel/3.7/smb347-charger_8c_source.html
[Nexus 7 Android Development] OlliWi:
OK, waiting for your feedback.

That´s one of the sources I use. :good:
[Nexus 7 Android Development] pincher65:
The battery controller is also involved in charging the battery. It is at his command that the charging current strength varies depending on the level of the discharge and, which is important, the battery temperature during charging.
[Nexus 7 Android Development] OlliWi:
That´s not how I think it works.

The battery fuel gauge chip bq27541 is just periodically (60s interval) calling the "smb347_config_thermal_charging(temp)" routine which does nothing else than compare the temperature value (temp) against the maximum allowed temperature (45 degrees) and then disables or enables the charger.

int smb347_config_thermal_charging(int temp)

{

struct i2c_client *client = charger->client;

int ret = 0, retval, setting = 0;

mdelay(150);

SMB_NOTICE("temp=%d\n", temp);

ret = smb347_volatile_writes(client, smb347_ENABLE_WRITE); // writing to register -> enable // not really needed here because no writing to a register is done!

if (ret < 0) {....	}

/*charger enable/disable*/

retval = smb347_read(client, smb347_PIN_CTRL); // read current status/content of Reg06h

if (retval < 0) {......	}

setting = retval & ENABLE_PIN_CTRL_MASK; // PIN_CTRL_MASK is 0x60 (0110|0000 binary) -> result for setting is either 0x60 (0110|0000) or 0x40 (0100|0000) 0r 0x20 (0010|0000) ox 0x00 (0000|0000)

if (temp > BAT_Hot_Limit) { // battery is too hot

if (setting != 0x40) {

SMB_NOTICE("Charger disable\n"); // we disable charger

smb347_charger_enable(false);

} else

SMB_NOTICE("Bypass charger disable\n");

} else { // battery temp is ok

if (setting != 0x60) {

SMB_NOTICE("Charger enable\n");

smb347_charger_enable(true); // we enable charger

} else

SMB_NOTICE("Bypass charger enable\n");

}

ret = smb347_volatile_writes(client, smb347_DISABLE_WRITE); // we disable writing to register again

if (ret < 0) {....	}

error:

return ret;

}

The smb347 does not need any external component to fulfil its function, it can operate stand-alone.

It knows the charging-end voltage (float voltage) of the battery (Reg03h) and then goes into taper-charging once those voltage has been reached.

Taper-charging reduces the current while mainting the battery on its float-voltage level.

The only thing, that the smb347 does not know, is the temperature of the battery. That´s where the bq27541 driver kicks in, calling above routine.
[Nexus 7 Android Development] kozmo2k4:
Flashed latest February version (dirty, over January release), with Pico Gapps and latest Magisk, over 48 hours ago.

All is running well and smooth.

Thank you [MENTION=2188693]AndDiSa[/MENTION]
[Nexus 7 Android Development] lotte67890:
Well,what can I say... you´re my hero! I now figured out that with the original charger and cable I can reach up to ~850mA, with the original charger and a new cable up to ~1150mA and with another 2.0A charger and the new cable ~1560mA :)

You made my day!

If you need further information please let me know

Thanks again!!!

L
[Nexus 7 Android Development] Witsche:
Hi, I'm looking for a rom (or even just the kernel) that supports mount namespace feature, in order to overcome SafetyNet with Magisk.

Does the kernel of this rom support this feature?

Thanks
[Nexus 7 Android Development] AndDiSa:
[MENTION=5756820]Witsche[/MENTION] yes, mount namespace is supported by the kernel (and the ROM, too).
[Nexus 7 Android Development] Witsche:
[MENTION=2188693]AndDiSa[/MENTION] can you confirm me that the safatynet test has passed?
[Nexus 7 Android Development] AndDiSa:
[MENTION=5756820]Witsche[/MENTION] yes
[Nexus 7 Android Development] Publicorderkeeper:
Thanks for the hard work. I installed 20190209 for grouper. There aren't any errors while install process - nice and easy). Pico gapps was installed without any problems as well. Only little problem is setup wizard - there wasn't way to go on without 'stop working' error, so I used a setup wizard fix for override that problem. I'd like to ask about kernel, is there any (but dc kernel) kernel to overclock CPU and GPU to higher speeds? P.s. DC kernel can be used to overclock CPU to 1500 MHz and GPU to 520(I'm afraid of increase it higher) but it has a major bug for me - memory leak(free ram decreases while using android and can't be reobtained in any way, only reboot can help with it).
[Nexus 7 Android Development] mikeataol:
Regarding Setup Wizard, I posted a few pages back that if you swipe down from the top in the notification area and enable Wi-Fi, then you can continue with setup. It may take a few tries but I've seen it on this and other ROMs. Perhaps it can be added to the installation notes on the 1st posts.
[Nexus 7 Android Development] AndDiSa:
I'll try to enable WiFi on initial boot, so hopefully no workaround will be needed any longer when setting up as a new device.
[Nexus 7 Android Development] spark001uk:
[MENTION=8559165]OlliWi[/MENTION]

Would you still like some more register settings for comparison?

I can try with a good cable and a poor one, see what changes. I acknowledge the main issue being in the driver, but cable quality can also contribute.

Also as a side note, I know a lot of people take charge current measurements using an inline usb meter. Whilst these can generally give a reasonable reading, the way in which they work - by measuring the voltage difference across a low value resistor (usually placed in its negative rail) - can add to the overall voltage drop across the cable, which doesn't help. In these cases where voltage drop is critical, I've made a small USB breakout adaptor with a current loop, and use it in conjunction with a DC clamp meter (hall effect) which reads down to 1mA resolution. This allows me to read actual current draw without interfering physically with the conductors.
[Nexus 7 Android Development] goran_s:
Yesterday I tried with 3 cables and 2 home chargers. According to Ampere I never manage to get over 800ma. As I primarily use my Nexus in my car, i have it on the car charger (2.4A) all the time. Maybe it's just a coincidence, but after the last update my nexus drains battery even on the charger, and charges with ~450mA in the car. Before battery was always 96-100% and I drained it every now and than to keep it in shape.

Best regards,

Goran
[Nexus 7 Android Development] OlliWi:
Thanks for your offer, but right now i do not need any more register values. I may come back to you offer at a later time.

I do power measurements at the AC-adapter´s input. As there is only a limited number of charging current stages (300, 500, 700, 900, 1200, 1500, 1800 mA), i can match those readings to the actual charging current.

But the behaviour of the smb347 is really strange.

After it worked well for about 10 days -

always charging at full speed

(never below 1200 mA - depending on AC charger), it is currently

always charging slow

with 900 mA max, most of the time only 500-700 mA with drops to 300 mA. Same chargers (i have 10 different chargers) and same cables (8 pieces) as before. And all of those chargers and cables work without any issues on 7 other android devices i have in my household.

The periods of quick charging and slow charging seems to alternate each couple of days. That´s weird.:eek::eek:

[MENTION=2188693]AndDiSa[/MENTION]

There are a couple of registers in smb347 that are not read-out by the driver - sysfs function static "ssize_t smb347_reg_show".

The adresses are 0x0f, 0x10, 0x11.

Please include it in next release. Especially 0x10h may be of interest because it probably contains the configuration of the input voltage detection circuit.

It is defined in our driver as #define smb347_IN_CLTG_DET	0x10 (note the scribal error, CLTG should be VLTG => voltage)
[Nexus 7 Android Development] dua89:
I cannot download (Build 20190209) Please help

I cannot download (Build 20190209)

Please help
[Nexus 7 Android Development] Portgas D. Ace:
First of all, welcome to XDA.

Second, your post doesn't contain enough information to help you properly. Did you try to download the latest build with another web browser?
[Nexus 7 Android Development] dua89:
I try download the latest build from "Install 7.1.2 Tilapia OTA-Package (Build 20190209) (md5: 8e4c0e1955ecc0bb65a51582bb01f779)"/

I do not understand what it means "with another web browser"?
[Nexus 7 Android Development] spark001uk:
Would it not be possible to just copy the relevant file(s)/settings from a stock N7 and incorporate them in this firmware? Or is it not as simple as that?
[Nexus 7 Android Development] AndDiSa:
Unfortunately the stock ROM has this issue, too. If you look back first people start complaining about slow charging rates in 2012 ...
[Nexus 7 Android Development] OlliWi:
It´s not as simple as that.

We have all the source code files from any ROM that´s ever been (officially) released for the Nexus. And a lot more source code from devices that utilise the same smb347 charger chip.

But unfortunately there is no datasheet anywhere on the internet that describes the functionality of the registers.

So we have to find out only by looking into the source codes, and hopefully there are some comments that indicate the register´s purpose.

But that still does not tell us how the smb347 works internally.

And finally we need to take into account that the chip itsself has some flaws, some hardware bugs we don´t know.

Or the PCB layout of the Nexus may not be properly designed, leading to some signal interference. You see, there can be a lot of causes for the issues we see. We´re working on it. Stay tuned.

[MENTION=2188693]AndDiSa[/MENTION]

I did a power on reset (POR) on my smb347 to force a reload of the non-volatile configuration registers into the volatile ones (in fact this is never done by the driver or anything else, neither a reboot of the Nexus or flashing a new ROM will ever reset the smb347 to its factory-programmed values). But that did not help either with the charging issue. Its still slow.

We should consider to do some register initialisation upon loading the driver after a reboot. Just like it is done in other smb347 drivers.
[Nexus 7 Android Development] spark001uk:
I'll see what I can find out on a datasheet/application notes, I'll put some feelers out (I am an electronics engineer so used to sourcing such documentation).

I can certainly desolder and replace the IC, as I can most surface mount components, but I don't know much about programming it unfortunately !
[Nexus 7 Android Development] Portgas D. Ace:
What browser did you use? For example, if you use Chrome, try Firefox ans check if the download issue still persist. I tried downloading the latest build and it works without any issue.
[Nexus 7 Android Development] TureX:
Hi ! Any update about random reboot?
[Nexus 7 Android Development] AndDiSa:
[MENTION=3777227]TureX[/MENTION] not really. I have random reboots, too, from time to time. I thought I found an explanation and a fix for it, unfortunately yesterday I had a reboot again :(
[Nexus 7 Android Development] TureX:
Thank you for Your hard work?
[Nexus 7 Android Development] OlliWi:
Hmm... i have no random reboots. System was up for 14 days (since the installation of the february ROM) without rebooting. Only the OOM is sometimes kicking in.

Then i rebooted the system manually to check if the smb347 registers are reset to its factory defaults. They are not.
[Nexus 7 Android Development] TureX:
Did you install magisk? And you [MENTION=2188693]AndDiSa[/MENTION]?
[Nexus 7 Android Development] AndDiSa:
Yes, Magisk 18.0 ...

Regarding reboots it's strange yesterday for example the device was laying around for some time, I woke it up, used it for a few minutes and sent it to sleep ... a few moments later I saw the device rebooting but I could not find the crash in last_kmsg so I am more and more thinking that it's not a kernel issue
[Nexus 7 Android Development] TureX:
Could be magisk?
[Nexus 7 Android Development] AndDiSa:
Even if chances are low I'll test it ... unfortunately those reboots are very rare.
[Nexus 7 Android Development] OlliWi:
Ich have Magisk 18.0 installed too. But no reboots.

/edit: Not sure if that instruction also applies for an update installation:

Do not install Magisk on initial setup as it might lead to issues. Start the ROM without having root access the first time and install Magisk in a second step.

Boot Recovery -> Flash ROM -> Boot recovery -> Flash Gapps -> Boot recovery -> Flash Magisk -> Reboot into system. That´s what i did IIRC.
[Nexus 7 Android Development] pincher65:
but there is no such thing on build 20190110. I returned to it due to the fact that my grouper just turned off if it was not used for a long time. Turned off even while on charge.

and it seemed to me SoT 20190209 became worse.

I have a magisk 18.1
[Nexus 7 Android Development] Publicorderkeeper:
I've been using newest build: no reboots, no problem with charging. I have magisk 18.1 and there's no problem with it either. My device is nexus 7 grouper.
[Nexus 7 Android Development] OlliWi:
It might help to investigate this issue if you only replace the kernel with the one from january. As there have been changes made to the kernel and the android system, it is not easy to find out whether this behaviour is caused by the kernel or android.
[Nexus 7 Android Development] AndDiSa:
In case of a kernel issue I would expect a crash dump in last_kmsg which in my case was not there ... (or battery power dropped completely and the device rebooted due to that ?)
[Nexus 7 Android Development] pincher65:
I would love to try, but unfortunately I did not save the January zip. if somebody shares it (or a kernel from it) I will definitely try.

I did not have reboots, it just turned off. and the magnetic trigger also began to work poorly (I use the smart cover), it was necessary to close and open the cover several times. I do not pay attention to the operation of the power button, since it initially does not work well on these tablets
[Nexus 7 Android Development] dua89:
I use Chrome and tried Firefox to download - not work. I opened site from mobile network, and download. I thinks it my provider block site. Thanks!
[Nexus 7 Android Development] rahimali:
Kernel from 20190110 build (for grouper) attached.

Sorry, I forgot to mention earlier this kernel is for grouper as that is the device I own....
[Nexus 7 Android Development] pincher65:
thanks, I'll try now

I flashed the January core for the February build. while the magnetic trigger works well. everything else I learn later (while on the charge).

after two days of work did not notice any problems. battery consumption also seems back to normal ~ 4 hours SoT in 4 days
[Nexus 7 Android Development] Yurchick:
Hello!

Build 20190209 (Tilapia) - works fine. The only thing that upsets is that OTG does not work.

Maybe you can somehow turn on OTG?
[Nexus 7 Android Development] OlliWi:
You´re the first with that issue. OTG works fine on my tilapia.:confused:
[Nexus 7 Android Development] Yurchick:
What a score.

OTG also worked fine for me on stock firmware (albeit after installing additional applications).

Now I tried various programs - devices (USB Flash) seem to see, but do not supply them with power.
[Nexus 7 Android Development] JoroBo:
Hi, I am reviving a grouper and was amazed to see that there is an actively supported ROM for it in 2019! A big thank you to the developer for his time and efforts!!!

I intend to flash it when I have some time and just want to ask if OMS support was added along the way and does anyone use substratum themes with the ROM? A quick search in the thread suggests that only substratum legacy functionality works and there was no OMS support so I wanted to know if there are any changes to this.

Thanks,