[ROM] [OFFICIAL- 8.1] [T813] OmniROM for Samsung Galaxy Tab S2

preference

Senior Member
May 3, 2017
987
553
93
Substratum

Latest weekly causes substratum to constantly crash, i cannot open it. My themes are still applied, so it's not a big deal, but I thought you would want to know about the error.

The error says "Substratum keeps stopping."

I don't know how to pull a log file, could you give me a quick set of instructions so I can help you out?

Current version: omni-7.1.2.20170604-gts210vewfi-WEEKLY
 

scanno

Senior Member
Mar 27, 2008
2,244
3,793
203
Arnhem
Latest weekly causes substratum to constantly crash, i cannot open it. My themes are still applied, so it's not a big deal, but I thought you would want to know about the error.

The error says "Substratum keeps stopping."

I don't know how to pull a log file, could you give me a quick set of instructions so I can help you out?

Current version: omni-7.1.2.20170604-gts210vewfi-WEEKLY
To all substratum users!
This is a heads-up if you update to the next official weekly built on 28.5.2017. If you have substratum app (version 731) already installed and running, then you will face the issue, where the substratum app will FC after booting and when starting the app.

The cause of that is the latest app update has introduced a new permission but the required changes in the framework for this to work correctly have been merged only this week into our code.

Due to the way android permissions work, this means that you will need to do a complete reinstall of the app, in order to avoid the crashes. Please make sure to apply any app settings you did before after the new install.

We’re sorry for the inconvenience caused by this, but due to substratum being its own entity, completely separate from OmniROM, there is very little we can do to avoid the problem.

 
  • Like
Reactions: VanoSM

preference

Senior Member
May 3, 2017
987
553
93
It worked

To all substratum users!
This is a heads-up if you update to the next official weekly built on 28.5.2017. If you have substratum app (version 731) already installed and running, then you will face the issue, where the substratum app will FC after booting and when starting the app.

The cause of that is the latest app update has introduced a new permission but the required changes in the framework for this to work correctly have been merged only this week into our code.

Due to the way android permissions work, this means that you will need to do a complete reinstall of the app, in order to avoid the crashes. Please make sure to apply any app settings you did before after the new install.

We’re sorry for the inconvenience caused by this, but due to substratum being its own entity, completely separate from OmniROM, there is very little we can do to avoid the problem.

Reinstall fixed the issue, thanks for your help (you are a very involved and dedicated developer)
 
  • Like
Reactions: cvelazquez

Lupin The Third

Retired Forum Moderator
Mar 26, 2011
3,947
5,019
263
Planet Earth
How's the fingerprint acting lately? Any update? Last time I used the rom, I often got a message on lock screen while trying to unlock. Something like, factory specific error.. The same happened with Lineage too... The only thing keeping me from using this rom... which makes me really sad!!!
 

scanno

Senior Member
Mar 27, 2008
2,244
3,793
203
Arnhem
How's the fingerprint acting lately? Any update? Last time I used the rom, I often got a message on lock screen while trying to unlock. Something like, factory specific error.. The same happened with Lineage too... The only thing keeping me from using this rom... which makes me really sad!!!
Hmmm. I can't remember seeing such errors. On the lockscreen or in the log?
 

Lupin The Third

Retired Forum Moderator
Mar 26, 2011
3,947
5,019
263
Planet Earth
Hmmm. I can't remember seeing such errors. On the lockscreen or in the log?
On the Lock Screen. In fact now that I remember better it is: Vendor Specific Message. Red letters at the bottom of the lock screen.

I might flash this again just to show you a screenshot or something... Don't know if it is in the logs too.
 

musashiken

Senior Member
Feb 22, 2010
1,354
152
93
On the Lock Screen. In fact now that I remember better it is: Vendor Specific Message. Red letters at the bottom of the lock screen.

I might flash this again just to show you a screenshot or something... Don't know if it is in the logs too.
Yup I have this error sometimes. I think it happens sometimes when the fingerprint sensor doesn't detect your finger properly.

How do you use the sensor? Do you first press the home button to wake the screen and then fingerprint unlock? I realize you can unlock the tablet from sleep by just using the fingerprint but that is quite rare.

So I usually wake screen first then unlock with fingerprint. Usually works 80% of the time. The other times finger moved too fast message or the vendor error message appears.
 

Lupin The Third

Retired Forum Moderator
Mar 26, 2011
3,947
5,019
263
Planet Earth
Decided to use omni exclusively for at least a month. I've been on stock most of the time.

Fingerprint failed only once since yesterday. Let's see how things go.

Everything else seems fine until now. :)
 

preference

Senior Member
May 3, 2017
987
553
93
Latest OTA broke the button lights. They light up when I reboot, but after using the tablet they eventually turn off. I'm talking about the two buttons around the home click button
 

scanno

Senior Member
Mar 27, 2008
2,244
3,793
203
Arnhem
Latest OTA broke the button lights. They light up when I reboot, but after using the tablet they eventually turn off. I'm talking about the two buttons around the home click button
Can you be more specific? The way you describe it, it seems to work as it should. Button lights go on and eventually turn off after a few seconds (see settings).

Verstuurd vanaf mijn SM-T813 met Tapatalk
 

preference

Senior Member
May 3, 2017
987
553
93
They turn off and never turn back on, even when I press the buttons. I have to reboot before they start again, but they eventually die and stop working, even if I press the buttons
 

preference

Senior Member
May 3, 2017
987
553
93
I did a full wipe, reinstalled omni + Open Gapps + magisk v13 and the installer wouldn't let me progress. It kept saying that the installer was closing unexpectedly. So basically I'm left with a useless device, because all I like to use is OMNI!

I'm going to attempt another install using Beans GAPPS right now. IF that doesn't work, I will use a differently weekly going back a few weeks.

Sorry, just wanted to let you know I am having difficulties with the latest ROM. I promise to keep trying different things until I can get it working.

---------- Post added at 01:40 AM ---------- Previous post was at 01:34 AM ----------

I did a full wipe, reinstalled omni + Open Gapps + magisk v13 and the installer wouldn't let me progress. It kept saying that the installer was closing unexpectedly. So basically I'm left with a useless device, because all I like to use is OMNI!

I'm going to attempt another install using Beans GAPPS right now. IF that doesn't work, I will use a differently weekly going back a few weeks.

Sorry, just wanted to let you know I am having difficulties with the latest ROM. I promise to keep trying different things until I can get it working.
I used dynamic gapps and it fixed my issue! thanks all

---------- Post added at 03:13 AM ---------- Previous post was at 02:40 AM ----------

Hmm. Don't have that problem here.

Verstuurd vanaf mijn SM-T813 met Tapatalk
I reinstalled and it fixed the lighting issue. Thanks for your help and devotion to support your users
 

preference

Senior Member
May 3, 2017
987
553
93
@preference so everything is OK now?

Verstuurd vanaf mijn SM-T813 met Tapatalk
No unfortunately. The lights worked at first, but once it kicked into night mode (amber screen), the button lights stopped working and stayed off. I checked again this morning when night light mode was turned off, and the buttons still are dead.

I can deal with it for now, but it kind of sucks. I don't know if my apps, substratum, or the rom is the issue. I wish I could send you some kind of log, but I don't know how to do that stuff.