yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Mega] MegaHolic:
Hi Mr. Obsolet,

Could you let me know whether the new rom ( lineage jan. 31 ) has SelinuxState set to enforcing or to permissive ?

Thx 4 answering,
[Samsung Galaxy Mega] Silesh.Nair:
Permissive
[Samsung Galaxy Mega] MegaHolic:
Thx, Silesh :)

Any plans to change this into enforcing ?

I'd like to give Lineage a try but I'd like to have SelinuxState enforcing for reasons of security ...

and ... I wouldn't like to try a workaround by way of a third party app like SELinuxmodechanger available from f-droid.

Thx 4 your resonse 2 that :)
[Samsung Galaxy Mega] Tilagoon:
Downloaded and installed (dirty flash) latest build from OTA as well as latest TWRP : everything running smooth:good: fantastic job again :good::good:

First reboot after ROM flash was around 9-10 minutes !!
[Samsung Galaxy Mega] jajaxor:
Hi !

help me please. I have got a problem ! I think last update slwed that but no :(

I try to explain that ! since 2/3 update, when I receive a call my screen don't on for answer.

I desactivate option (in french sorry) "empêcher un éveil accidentel (check the proximity sensor prior to wake-ups triggered by gestures)" (in "screen" section). after that, when I receive a call my screen on ! :)

Bu when I answer this call, my screen off again. I must glide my thumb to the top on my mega for screen on !!

well then, option desactivate ? bug ? proximity sensor problem ?

I change my screen since one month and I don't remenber have got this problem before...

thanks for your help !
[Samsung Galaxy Mega] Silesh.Nair:
Themes wont apply if selinux is enforcing, atleast on this rom.
[Samsung Galaxy Mega] MegaHolic:
Ah, I see ... alright, I'll put my hopes onto RR instead of Lineage then :)
[Samsung Galaxy Mega] r1l_Alex_™:
Still running good here! Smooth and fast!

Rebuilt caches and some ka tuning... I've had it up on my daily doing all my normal stuff and haven't a single issue with anything...

The biggest improvement to note is IME latency tested considerably better than the previous CM builds.. I'm using a in-house board and its been a dream all day! Messaging and text input is super quick...

Gps locks on lineage are fast as **** too! I noticed that the 1221 cm build had some of the fastest locks I've noted since the AOSP based MM builds and lineage is just as fast...

Battery is good as well! SOT with 1350 low and 1728 high is improved too... Of coarse I finally was able to upgrade the battery on this one...

Of coarse I always make my changes and reflash! Just wanted to update you guys and let you know how it was going...

Will be testing further in the next days as well as running the RR oms testing.... As of right now its doing awesome!

Have a good night guys! :good:
[Samsung Galaxy Mega] Mr. Obsolet:
Sorry, MegaHolic, but my work sometimes needs my full attention and i was not able to answering your question.

Regarding new rom release: after 24hours no major or minor problems on my device.

Gesendet von meinem GT-I9205 mit Tapatalk
[Samsung Galaxy Mega] MegaHolic:
Hi Mr. Obsolet,

No problem at all ... thanks for coming back to my query ... :)

Have a good day :)
[Samsung Galaxy Mega] carlos974:
For me I have to create a directory "theme" in TWRP (internal storage).

I also put the file ui.zip.

But now with the latest twrp 3.0.3 the theme does not work.

He told me to use a stock theme...........one idea ? Thanks

Without this he works well.
[Samsung Galaxy Mega] carlos974:
Resolved !

Unzipped the file ui.zip

Edit in both splash.xml and ui.xml files the value in "themeversion"

Set the value 2 to 1

Enjoy !!! :good:
[Samsung Galaxy Mega] Saiful98:
[MENTION=4551757]Silesh.Nair[/MENTION]

Thanks a lot to you silesh..

Using 20170131 rom and never encountered any issue

Great battery life sot around 4-5 hours

Really love the pixel look

Thanks again for your contribution in this community sir:cowboy:
[Samsung Galaxy Mega] Silesh.Nair:
I miss my mega sometimes... :(
[Samsung Galaxy Mega] Mimisf:
Hi Silesh!

I encounter a problem that started from the last (or one build before last, can't remember) build of cm14 all the way to the 31/1/2017 lineage build.

When I am watching a video on YouTube, the video often stucks but the audio continues ( the video doesn't buffer, it just stops) and I have to go back or forward in the video 2-3 times to make it work again.

Is there anything wrong with the ROM or it's a YouTube problem?

Also

I have another bug when watching a video (not so often but it happens) the whole screen turns black but I can, for example, double tap the status bar to lock the phone.

To solve this I have to turn the screen off and on again.

Thanks in advance for all the work you do!

Both bugs happen with both dirty and clean installations.

Right now, I run clean installed lineage os 31/1/2017 build
[Samsung Galaxy Mega] Silesh.Nair:
[MENTION=7240824]Saiful98[/MENTION]
[Samsung Galaxy Mega] Saiful98:
I often watching YouTube too but never encountered that problem..

Also the video issue..no problem at all...btw im using mx player to watch videos
[Samsung Galaxy Mega] Mimisf:
Thanks for your time answering.

The black screen bug just happened again when I tapped the comments button on a post on Facebook so it doesn't have to do with video playback I guess...

It isn't a huge problem for me, but if you find anything on how to solve it, I will be pretty grateful.
[Samsung Galaxy Mega] Silesh.Nair:
Update available

Refresh your ota.

I will be taking some time off to concentrate on my sons studies. He is writing his 10th boards this year. Will probably pop up once in a week till March end. RR updates will be delivered on time.
[Samsung Galaxy Mega] r1l_Alex_™:
Awesome Silesh! I too have my daughter about to graduate early this year and have to make sure she stays high on her mathematics majors... I'm going to be busy as well..

Thank you for everything [MENTION=4551757]Silesh.Nair[/MENTION]
[Samsung Galaxy Mega] r1l_Alex_™:
[MENTION=4551757]Silesh.Nair[/MENTION]

Sim Card issue has returned... Booted after flash and com.android.phone fc's... no sim card detected... I didn't flash current picos.. Just the Rom... Went back wiped and clean flashed it, same thing.. Clean flashed one more time with current picos... No go...

Phones permissions and defaults are good....

I tried to pull logs and once again outputs blank.. I don't know what the deal is with that... I will keep trying...

If someone else has the issue please confirm.. Thanks!
[Samsung Galaxy Mega] Silesh.Nair:
Damn...

Try this one.

https://mega.nz/#!F5M1BS5K!mMsG0iftUxYsnkBHPjKY-N9ejpWbNeWKCC2bkIcJYls
[Samsung Galaxy Mega] r1l_Alex_™:
No go... Does the same thing... Ima try a few things to see if I can get it to fire..

If someone else flashes please confirm..
[Samsung Galaxy Mega] Sheist!:
"Full Substratum OMS theme support"?

Sim works fine for me, and on this update.

Substratum themes, however... don't change anything, despite showing to have disabled other themes/built and enabled without any errors. Rebooting changes nothing, and I manually ensured Substratum, the themes, and the masquerade have full/system/root perms.

Is the "Full Substratum OMS theme support" not yet baked?

I've wiped dalvik and cache, but have not tried blowing away the whole shebang and starting from scratch.
[Samsung Galaxy Mega] r1l_Alex_™:
Thanks for the update... Ill download the build again and flash it...

As far as substratum goes.. The shift of Selinux from Permissive to Enforcing may have been the cause as before...
[Samsung Galaxy Mega] MegaHolic:
• On my device, that rom worked in terms of sim card but failed to work along with Titanium Backup:

TB managed to let me know it recognized the ( correct ? ) number of user apps contained in the backup –

it showed a total number of apps ( user apps in backup together with system apps ) and it listed the user apps as the content of the backup folder ... however, TB didn't list any of these for restoring. So, restoring them wasn't possible for me.

• I am back to the latest RR which performs well.

• The latest TWRP does, at least on my device, fail to boot into recovery mode:

Upon choosing " recovery " ( after doing a full wipe ) as a boot destination, it tries to boot up the OS ( which is missing after full wipe ) like it does when selecting " system " as a boot destination.
[Samsung Galaxy Mega] Silesh.Nair:
Why would you reboot your phone to any mode without installing a ROM after a full wipe with no OS installed. Doesn't make sense.

The commit to make substratum work with sepolicy enforcing is added in this ROM. It works on the MotoG4 but if it doesn't on the Mega, I need logs.

Also need someone who has adb installed on their linux pc to connect phone and give me the output of the command below

adb shell su -c dmesg | grep denied | audit2allow -p out/target/product/board/root/sepolicy
[Samsung Galaxy Mega] r1l_Alex_™:
I clean flashed the 206-2 build again after re-downloading it today and I've clean flashed it on 2 devices and I haven't had any issue with either Sim nor Substratum / Masquarade... Selinux is enforcing!...

I apologize [MENTION=4551757]Silesh.Nair[/MENTION]...for some reason the file wasn't transfered correctly lastnight and I downloaded it twice... Anyways everything's good here...

CleanFlashed with 205 picos ...
[Samsung Galaxy Mega] Silesh.Nair:
No problem, Alex. **** happens sometimes....
[Samsung Galaxy Mega] Sheist!:
Substratum theme installs nothing*

Anyone able to get Substratum themes to ACTUALLY install changes? All I get is overlays/etc installed/enabled "with no errors", but nothing* actually changes. (ticked disable all other themes, build and enable, rooted, the whole 9 yards)

On latest 02/06 after full clean install.

Whomever actually has a Substratum theme successfully installed on this ROM, I'd like to know exactly how you did it.

I am not interested in anyone who just installed Substratum theme engine but did not actually try using it.

* NOTE: if I go to the wallpaper section in the engine and enable a wallpaper change there, it does change the wallpaper... but any rinky-dink app can change the wallpaper...

Thanky...
[Samsung Galaxy Mega] MegaHolic:
Hi Silesh,

doing so belongs to my collection of li'l habits with questionable benefits :) :

On the one hand, it doesn't take a significant amount of time ( if measured against the frame of time needed for clean flash and set up of rom ) –

on the other hand, it gives me the feeling that booting into recovery mode after completion of my manual full wipe might make the device remove any " traces of remains " that could be left otherwise.

My observation that the latest TWRP doesn't boot into recovery mode as intended by tapping " recovery " ( but, instead, tries to boot up the OS ) doesn't mean any problem to me – I reported on it simply because this " boot failure " doesn't belong to my experience made with previous versions of TWRP.

Feel free to call me crazy :), and

have a good day :)

Thank you for your comment included above, and ... of course ... for all your excellent work for the MEGA community.
[Samsung Galaxy Mega] r1l_Alex_™:
When you start Substratum for the first time does Masquarade ask for root? It should...
[Samsung Galaxy Mega] Sheist!:
No, it never has. Substratum asks for root at the beginning, but I do not see masquerade ask. I have gone in to Dev tools to root permission apps and given masquerade Approved from Ignored, but I have never seen it ask for permission.

Still makes no difference for me, re-applying everything again. It says all successfully built and applied, but nothing changes.

I even have to go into Apps and give Substratum permission to "modify system", as it has not asked me for that permission either.

Root is set for "apps only" in Dev tools.

---------- Post added at 07:10 PM ---------- Previous post was at 06:57 PM ----------

Does anything in this Rom or Substratum use the internal SD? It is the only thing I did not wipe when I reinstalled.

I suppose I can start over from scratch and put the install files on an external SD and wipe internal, and see what that gives me.
[Samsung Galaxy Mega] Silesh.Nair:
Themes won't apply if masquerade doesn't get root. Delete app data and try.
[Samsung Galaxy Mega] Tilagoon:
Hi,

Just done a dirty flash on top of previous version (file from OTA) : All OK , no SIM problem and installed theme still working :good: Great job again !

Just one small thing: I use the application "Power toggles" to easly swich LTE off/on as well as other functions (BT, Wifi, etc).

When I try to tooggle mobile data I get the following message:

Cannot toggle Mobile data. Is your device rooted ?

Error 2: Command "service" not found.

But the job is done and LTE switches on/off OK !!

The root is OK in developers options for "power toggles".

This didn't occur with previous build.:confused:
[Samsung Galaxy Mega] Silesh.Nair:
You don't need that. There is an option to activate toggle for Bluetooth/WiFi and data under settings-> additional features. Switch it on and use single click to toggle them on/off.
[Samsung Galaxy Mega] Tilagoon:
Thanks for the tip, I had missed it :)

But it looks strange:

Click on Bluetooth icon switches it off/on Ok

Click on Data icon goes to the setup screen for data but no activation

Click on Wifi icon toggles the Wifi Ok but tries also to toggle data and I get the same message as stated above.:confused:

I have frozen "Power toggles" with Titanium backup but still the same problem !

With power toggles you can do something like this:
[Samsung Galaxy Mega] r1l_Alex_™:
..............
[Samsung Galaxy Mega] MegaHolic:
Yesterday, I reported that my device didn' t " enjoy being fed " with the latest Lineage plus TitaniumBackup ....

Meanwhile, I could figure out the cause of this issue:

It was my wiping of data ( which in TWRP requires typing " yes " to specially confirm the intention to wipe ).

By it, something that TB needs ( for listing the apps to restore ) got lost.

After restoring RR by TWRP, rebooting RR, doing a full wipe without wipe of data then, and finally flashing the latest Lineage rom, TB did list the apps to restore :) ... and ... yes, its restoring of apps worked flawlessly.

I am now happy to try the Lineage with its SELinux set to enforcing.

Special thanks for that, Silesh :)
[Samsung Galaxy Mega] r1l_Alex_™:
Speaking of the new TWRP

Just as a side note... The new TWRP wont flash any Rom unless the device is a 9200/9500... I just found that out when trying to flash On a SGH Metro Vairant...

I have 2 9205s and A Metro Variant and TWRP errors and on the Metro Vairants aborts the flash... Of coarse I modify the builds for the metro variant before the flash so with that said Im able to do so... As the OP states and always has,the Roms are for the 92's...

If anyone tries to flash these builds on anything but the 9200s/9205s,,, using Silesh's TWRP 3.0.3.0 it will error... Use Silesh's TWRP 3.0.0.0 for that...

I've been getting PMs about the Metro Variants... This is what you need to do...

Thank you...
[Samsung Galaxy Mega] Silesh.Nair:
Gimme the model no's and name and I'll add it.
[Samsung Galaxy Mega] r1l_Alex_™:
Samsung Galaxy Mega 6.3

Model: SGH-M819

Thank You Silesh! That would save me a ton of time....
[Samsung Galaxy Mega] Silesh.Nair:
Do you haave the build.prop of a stock rom for this device by any chance?

Nevermind. Got it from here.

What does the output of the following commands say? meliuslteMetroPCS ?

getprop ro.product.device
getprop ro.build.product
[Samsung Galaxy Mega] r1l_Alex_™:
I apologize... left out some Information...

meliuslteMetroPCS

M819NUVUBNI5

SGH-M819N

Well you have it lol...
[Samsung Galaxy Mega] Silesh.Nair:
Output of

getprop ro.bootloader
[Samsung Galaxy Mega] r1l_Alex_™:
ro.product.model=SGH-M819N

ro.build.product=meliuslteMetroPCS

to.bootloader=M819NUVUBNI5

There... I apologize...
[Samsung Galaxy Mega] Silesh.Nair:
Get the twrp recovery flashable zip from here. You shouldn't have an issue from the next build.

Also get the ro.bootloader value from the guys who asked you and see of its different. It should usually say only M819N but yours is different. Don't know if it changes based on the build number.
[Samsung Galaxy Mega] r1l_Alex_™:
Done... Just flashed the recovery on the Metro Variant and all is good...

Just wanted to post getprop pulled from the recovery in case you need anymore information...

Thank you again [MENTION=4551757]Silesh.Nair[/MENTION]
[Samsung Galaxy Mega] PapkaOtec:
Will MIUI 8?
[Samsung Galaxy Mega] Silesh.Nair:
I think the developer has stopped working on it.
[Samsung Galaxy Mega] Bach_J:
I've just installed the last version of the ROM and it recognizes SIM Card.

But I still have this issue: when I use speakerphone during a call, the person I'm talking with hears my voice and the echo of his/her voice.

How could I solve?
[Samsung Galaxy Mega] r1l_Alex_™:
Did you ever figure out why your Substratums didn't apply? Or have you fixed it? Let me know...

---------- Post added at 04:13 AM ---------- Previous post was at 04:13 AM ----------

Did you flash up or clean flash?
[Samsung Galaxy Mega] Sheist!:
I have not yet discovered the cause of the problem, but not for a lack of trying everything available to me. It is clear that Masquerade never prompts me for root, never prompts for permission to storage, and makes no difference if I manually set permissions to storage for it. When Substratum asks for root, it states successful and error-free application, but does not.

I've wiped everything including data, system and internal storage and started from scratch, but still no-go.

At what point should Masquerade ask for root? With Substratum? Is there a specific Substratum I should be using, other than the one in Google Play?

In addition to starting off with a fully clean install of the phone, I've tried dumping data for Masquerade and reinstalling Substratum and the themes, but nothing changes it. It is as if Masquerade has decided to stay "asleep".

Should I try a specific previous version of Lineage, then dirty-flash the latest, instead of clean install of the latest rom? Other ideas?

Thanks.
[Samsung Galaxy Mega] r1l_Alex_™:
Back up your important data and ima send you something to try...

Pm sent... Keep it there....
[Samsung Galaxy Mega] Bach_J:
I wiped Dalvik/ART Cache, Data, System then I flashed ROM and pico opengapps. During the first boot, it blocked on the loading image so I forced restart by pressing Vol+ + Power button and it worked.
[Samsung Galaxy Mega] Hallahan:
I'm having troubles with the Bluetooth pairing with my Ford Mondeo Bluetooth hand free set: the phone doesn't remember the credentials entered. Everytime I have to enter them.

Any solution?
[Samsung Galaxy Mega] aku_baik:
I have the same issue with my smartwatch. I just unpair and pair it again, then it should be working normally :good:
[Samsung Galaxy Mega] r1l_Alex_™:
Here... I do this when the Bluetooth stack gets wacked out, or after a dirtyflash,If I have issues with pairing,file transfer,media streaming etc...

I do this via ADB but ill give you the RootBrowser version...

Depending on what root browser your using etc... I personally use RE...

Make sure bluetooth is off... Open RE or your RootBrowser..

Mount R/W and Navigate to:

/data/misc/bluedroid

Delete the files listed below...

bt_config.bak

bt_config.conf

Close it all up... Fire Bluetooth back up and Pair just like you normally would... You might have to redo the device names... This should fix it.... :good: If not a reboot maybe needed..
[Samsung Galaxy Mega] Hallahan:
I'll check it out later, thanks guys!
[Samsung Galaxy Mega] Axmed.92:
this room drain the battery sooo badly for my device idk why
[Samsung Galaxy Mega] r1l_Alex_™:
Not here.... Battery is real good! Considering Im set to have both cores up at all times and the low side clock freqs are 1674 and never fall...

Seems you have some applications running that eat up battery... Check gapp sync, this also too eats up battery... Shut wifi off when its not in use just to start...

I don't know what you have installed or running vs how the device was wiped, flashed and setup to accurately determine whats causing drain...
[Samsung Galaxy Mega] MegaHolic:
On my device, the latest Lineage rom doesn't cause such battery drain –

moreover, the roms' features that I use ( no bluetooth, no gps, no special themes ... just to name a few exceptions ) do work perfectly.
[Samsung Galaxy Mega] Bach_J:
Any solution?
[Samsung Galaxy Mega] _lo_ok_:
Wifi problem

There is a problem with Wi-Fi. I have two device the same problem on this version and the version of the one before it. Contact works about five minutes and then connect to the Internet ends so do I turn off the Wi-Fi and re-run it and then finished browsing. is there a solution .?
[Samsung Galaxy Mega] r1l_Alex_™:
I don't understand your question... Please be more specific...

This could be a gapps related issue? I'm not having issues with wifi...

Try this...

1. On your phone goto Wifi threw settings when connected and forget the network router your using and shut off wifi... Restart the phone... Let it boot and don't touch it...

2. Shut your router off to purge the clients IP table and release the network IP ISP and DNS will flush as well in normal circumstances ... Also make sure all devices that run on that network have wifi off aswell...

3. If your on a Win Box "Windows Computer" . Make sure wireless is off and or disconnect your Ethernet Cable before proceeding...Open a administrator command prompt by right clicking the command prompt icon and selecting run as administrator...

4. At the command prompt type the following commands.. Note: this is considering that the windows drive is labled c:\

Cd C:\ and hit enter...

Ipconfig /flushdns

5. Power your router back up and connect your Windows Box Via Ethernet Preferred so you can accsess its settings and view the clients table and up lease times etc...

6. Finally, take your phone and enable Wifi again... You will need to enter the network password again etc.. You would see it obtaining IP address and connected when done...

7. Test.... You can open settings and check the lease times as well just to make sure that that's not the issue... IP lease times can be modified...

Note: this method is for IP addresses that are chosen dynamically ... Static IP allocation is different...

Not saying this will fix it, as it could be a number of things causing it... Logs would be very helpful in a situation like this ...
[Samsung Galaxy Mega] Silesh.Nair:
Ambient display and deep sleep

Can anyone check using betterbatterystats app if device enters deep sleep with ambient display enabled. Wait for an hour after enabling ambient display before you check.

Will help rule out a source issue.
[Samsung Galaxy Mega] Bach_J:
As I wrote some days ago, when I use speakerphone during a call, the person I'm talking with hears my voice and the echo of his/her voice.

You asked me if I had done a clean flash and I answered: "I wiped Dalvik/ART Cache, Data, System then I flashed ROM and pico opengapps. During the first boot, it blocked on the loading image so I forced restart by pressing Vol+ + Power button and it worked."

I quoted you again because I thought you forgot my question :D

So, please, what should I do?
[Samsung Galaxy Mega] r1l_Alex_™:
On it! Give me a little bit and ill update... :good:
[Samsung Galaxy Mega] r1l_Alex_™:
QUOTE=Bach_J;71019022]As I wrote some days ago, when I use speakerphone during a call, the person I'm talking with hears my voice and the echo of his/her voice.

You asked me if I had done a clean flash and I answered: "I wiped Dalvik/ART Cache, Data, System then I flashed ROM and pico opengapps. During the first boot, it blocked on the loading image so I forced restart by pressing Vol+ + Power button and it worked."

I quoted you again because I thought you forgot my question :D

So, please, what should I do?[/QUOTE]

Do this...

https://xdaforums.com/galaxy-mega/o...urrection-remix-n-5-8-0-t3507216/post71007752

[MENTION=4551757]Silesh.Nair[/MENTION]

Still testing... So far with Ambient Display set on 3 devices, They do NOT fall into deep sleep... I've tested it repeatedly over the last few hours...

Tested with both BBS and Ka .... Ka screens show it clearly.... Current Lineage 0206 build..