yashsingh1/xdaforums huggingface dataset:
[Google Pixel XL Questions & Answers] blanken_ship:
According to elementalx.org/devices/pixel/ the right elemental kernel is 1.15.

I've done this exact process too and ran into many issues, I would recommend as follows, I've had a lot of success with this. I got Magisk working under 14.2 , twrp 3.1.1-1 , and elemental 1.15. I could not get any of them working correctly with any other versions or in any other order - this worked for me.

reflash stock with flash_all and factory reset

fastboot boot twrp 3.1.1-1

check "never show" and swipe

adb sideload twrp-3.1.1-1.zip

adb sideload VerifiedBootSigner-v8.zip

reboot recovery

sideload again

adb sideload your new ROM here if you want that

adb sideload twrp-3.1.1-1 again, had to do this for PureNexus, cause recovery was overwritten

adb sideload VerifiedBootSigner-v8.zip again

reboot recovery

adb sideload ElementalX-P-1.15.zip

reboot recovery (might not be necessary)

adb sideload Magisk-v14.2(1420).zip - I got this from the Arise Aroma installer package in another thread

adb sideload VerifiedBootSigner-v8.zip again

reboot system, enable systemless hosts and magisk hide on google services framework and play store. magisk hide only works with a kernel that supports it so if your elemental is working you should be fine.

reboot again, then install busybox, I used stericsons from play store. I also installed the selinux switcher for permissive mode. I installed these to get Arise / Viper to work and I think they are required for xposed too.

Magisk modules should work from there, including the xposed installer, but xposed will cause safetynet to fail. I could not get magisk modules to work with 14.3, have not tested other versions, but 14.2 worked.

I did not let twrp install it's apk from recovery mode, or let magisk download it's update, I downloaded both APKs separately.

I remember having many issues with the order of install for magisk versus elemental. I'm pretty sure what worked for me is elemental, then magisk as I put here. but if you run into issues it might have to be magisk then elemental.
[Google Pixel XL Questions & Answers] smithilberry:
Thanks for the directions!

However, before I try this, I have one question... what is "VerifiedBootSigner-v8.zip"?

After searching, I see a bunch of information on the May security patch, but nothing talking about the August security patch (which is what I'm on). That being said, does it still apply?
[Google Pixel XL Questions & Answers] kingbri:
You don't need Xposed, magisk has plenty of modules, but after rooting, flash the verified boot signer to allow for stock boot. It patches the boot image. Android 8 methods fixed this issue
[Google Pixel XL Questions & Answers] Mikkey81:
Here is how you flash a kernel with the stupid 2 slots LOL...

Rom installed and ALREADY BOOTED INTO the OS That rom.

Reboot to TWRP 3.2.1-0

Flash Kernel and Flash TWRP 3.2.1-0.ZIP followed by rebooting recovery (i usually hit reboot system hold volume down until i get to bootloader and then choose recovery (reboot recovery doesnt always work))

Flash Magisk 15.0 or 15.1 on Oreo and i believe 14.3 and down will work better for Nougat.

Reboot buddy!!! All is good in the world.
[Google Pixel XL Questions & Answers] Mikkey81:
WAAAAAAIIIIIT!!!! you need to be on Magisk 15.0 just failed multiple times and realized that was the last thing I Updated to 15.1..

Make sure you're flashing 15.0.
[Google Pixel XL Questions & Answers] dablitzkrieg:
Can we get Xposed yet on Oreo with Magisk? I see it says there are 4 different options available in the module section of Magisk. One is labeled "Xposed framework". All the others are labeled "Xposed Framework SDK 25" down to 19. Which one should be used for Oreo?
[Honor 9  Guides, News, & Discussion] ennbee:
Introduction

Since first getting the Honor 9 (STF-L09) all was well apart from the fact that there is clearly a volume limit on the UK/EU version of the phone, meaning that when walking through town, I couldn't hear my music properly. After a while searching the forums for a solution, I finally found motivation to tackle the problem myself and luckily have found a solution, not to the limiting, but to increase the headphone volume.

Credit

Credit to Demeth for the starter for ten when looking at this issue, who found the solution for the Honor 7

Requirements

You'll need a rooted Honor 9 and a Root Explorer to edit the files in question.

Tested on

I have tested this only on my own Honor 9 STF-L09 running build STF-L09C432B100 purchased in the UK.

This method may work on other versions, but you might have to trial and error the *.xml file located in /product/etc/audio/hi6403. I removed all mixer_volumes_STF-*.xml files. restarted and had no volume at all. I copied them back one by one, restarting after each until I had sound again, taking note of the last file copied; this is the one I ended up editing.

You may have to do this if the changes to mixer_volumes_STF-Oversea_ce.xml do not work for you.

Actions

Steps 1 and 2 look to remove the high volume warning limit, step 3 increases the headphone volume. I suggest carrying out all three steps.

1. Open Root Explorer and browse to /hw_oem/prop and open the local.prop file in read/write mode, edit the below line:

ro.config.hw.security_volume=14

To look like:

[B]#[/B]ro.config.hw.security_volume=14

Save the file, Root Explorer will create a backup (.bak) file of the original.

2. Browse to /product/hw_oem/STF-L09/prop and open the local.prop file in read/write mode, edit the below line:

ro.config.hw.security_volume=14

To look like:

[B]#[/B]ro.config.hw.security_volume=14

Save the file

3. Browse to /product/etc/audio/hi6403 and open the mixer_volumes_STF-Oversea_ce.xml file in read/write mode, edit the below line:

<path name="media-headphone" >
<ctl name="S1 IL PGA GAIN" value="252" />
<ctl name="S1 IR PGA GAIN" value="252" />
</path>

To look like:

<path name="media-headphone" >
<ctl name="S1 IL PGA GAIN" value="265" />
<ctl name="S1 IR PGA GAIN" value="265" />
</path>

Save the file.

4. Restart the phone and you should now have increased headphone volume and no complaint about high volume levels. The limit is still in place, but the maximum volume should now be increased.

Disclaimer

I am not responsible for any damage to your phone, headphones or ears, or any other alternative impact this change may or may not have.
[Honor 9  Guides, News, & Discussion] lordmogul:
Any ideas how high the values can be set?

255 or 256 would make sense as 8-bit variable, but 265 indicates that there can be more.
[Honor 9  Guides, News, & Discussion] robenzo420:
Finally solved my problem with low audio (atleast it seems so).

For anyone on Emui 8 who can't find files in step 3, try /odm/etc/audio.

Actually found this location after browsing many guides for different Honor phones and found that we have same location as a Huawei Mate 10 Pro.

Seems like location is changing with every emui update or with every phone. Confusing as hell.
[Honor 9  Guides, News, & Discussion] Aviiiciii:
Can you please help me i have Mate 10 Lite Oreo i tried everything nothing worked for me ?
[Honor 9  Guides, News, & Discussion] Pachanka:
I find the 3rd file in same place like you, but with this one, i can't modify it (no permissions :/)
[Honor 9  Guides, News, & Discussion] robenzo420:
Of course you need to be rooted and use 3rd party file explorer with root permissions. I used Solid Explorer.
[Honor 9  Guides, News, & Discussion] Pachanka:
I'm rooted and use Root Explorer with permission on this app....with no success :/
[Honor 9  Guides, News, & Discussion] edwardmlyte:
Perfect. This has bugged me for ages. Especially when you plug in the headphones initially and you can hear the full volume and it almost instantly quietened down.
[Honor 9  Guides, News, & Discussion] Haukore:
It works, thank you ^^

Inviato dal mio STF-L09 utilizzando Tapatalk
[Honor 9  Guides, News, & Discussion] Really_Rekt:
on later emui versions, its in the hi6403 subfolder
[Honor 9  Guides, News, & Discussion] packticho:
It would possible yo do this for audio bluetooth?
[General Questions and Answers] prostream:
Hi!

I would like to use Zattoo to run TV via FireTV Stick in background. Zattoo will run 8 hours a day.

The problem is that after 4 hours a message comes up "We've stopped the stream due to inactivity, please confirm to tune N-TV again.?"

Does anyone have any idea how to avoid this message? I have already decompiled the. apk file and found entries that point to the message. But I couldn't get a complete deactivation yet...

What i found out with decompiled .apk:

The stringname is: sleep_dialog_recover_message (Found in \res\values-de)

ID= 0x7f090294

Any ideas how to disable this annoying message?

Thanks in advance!
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] OneFlamingEye:
The last time I ever see my Tablet Gt N8000 (Made in Vietnam) :crying:

Before it happend I was eating a Hamburger, I just use my camera and made a video...You know, some random videos like crappy stuff.

Then after I stop recording, It just hangs and reboot.

It just got stuck on Samsung Logo, I was not scared that time, I tried to use recovery like pressing Volume Up and Power Button,

you guys all said it was easy to use recovery, but NO, NOT FOR ME.

My tablet is so different that he wont let me use Recovery.

When I pressed the Power Button + Volume Up, It boots. I was waiting for the recovery screen but NO! Something bad happend It boots again.

Whenever I try to use recovery, it boots again like

I pressed the key to go to Recovery Mode

it says "Samsung Galaxy Note 10.1"

Then OFF then there goes again "Samsung Galaxy Note 10.1"

But it didnt go recovery mode, it goes to "Samaung Logo" now.

Its like denying my Recovery Command.

Then I have no choice but to use Odin and the Samsung N8000 Firmware.

I used Vietnam, go to odin then put the md5 then start.

THEN SOMETHING HAPPEND! It FAILED! I did it again, I unplugged and plugged the USB then FAILED! FAILED! FAILED! F*CKING FAILED!

F*CK THIS SH*TTY TABLET. :rolleyes::(:(

I try to find a way but no! Nothing. Only a Legend can solve this problem.

If you comment about more firmwares..No! Just No! I Tried It.

I Even USED 2 DIFFERENT FIRMWARES! ALL VIETNAM!

This is harder than you think.

R.I.P Samsung Galaxy Note 10.1 GT-N8000. :crying:
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] JJEgan:
Some information may help .

What firmware what fail error in Odin .

Or see multiple identical Odin / firmware fail posts .
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] immns:
Mine is made in viet too. Fortunately, i dont have any issue at all. I suggest to bring your tablet to your trusted phone repairer and tell them what's your problem. Because it's hard to predict(diagnose) what's going on whit your tablet. It may caused by emmc/camera sensor error, so you need to replace one/both of them. if you lucky enough, it well be just firmware failure.
[Samsung Galaxy J5 Guides, News, & Discussion] Cyterafle:
Only one J5 can get Oreo:J5 2017

J5 prime has 7570 the SOC supports Marshmallow and Nougat (J3 2017 too can't get O)

And J5 2016 has Snapdragon 410
[Samsung Galaxy J5 Guides, News, & Discussion] ClaudiuXDEV:
Well... Moto G4 Play and Redmi 2 have the same chipset as j5 16 and some people have succesfully ported the Oreo for those phones....
[Samsung Galaxy J5 Guides, News, & Discussion] Cyterafle:
Moto G4 doesn't has official update
[Samsung Galaxy J5 Guides, News, & Discussion] BlackAxiom:
Your post has serious grammatical error. Your argument is invalid!
[Samsung Galaxy J5 Guides, News, & Discussion] Cyterafle:
For Samsung is an argument and Sorry for gramatical error,I'm french
[Samsung Galaxy J5 Guides, News, & Discussion] Tisenoiazei100:
MSM8916 is pretty much dead now on official support

Its predecessor MSM8226 ended with MM so i think its the same with the 8916....

But hey you have MIUI9, LOS15"Broken", TW-NN and many more ROMS to enjoy

Also J5 2017 is an Exynos 7870 phone :b(Its a J5 series phone only)
[Samsung Galaxy J5 Guides, News, & Discussion] Cyterafle:
MSM8916 support stop with Nougat

If the support has stopped with MM If not J5 2016 and Moto G4 couldn't have Nougat
[Samsung Galaxy J5 Guides, News, & Discussion] Tisenoiazei100:
And? J5 2016 has much lower lifespan than the 2015 model and also Samsung has never EVER fixed bugs or wrote any code in their sources by themselves(Samsung hasnt even created Touchwiz :b). They are taking Nougat patches from Qualcomm and if Exynos from partners and if Qualcomm kills oreo support for MSM8994/8996 then they wont really get their time porting it for J5 2016/2015
[Samsung Galaxy J5 Guides, News, & Discussion] Cyterafle:
If support is stopped we can port Lineage (J5 2015 has already LineageOS 15)
[Samsung Galaxy J5 Guides, News, & Discussion] JosephDM:
MSM-8916 development is stronger than ever, you clearly don't know what you're talking about. And LOS 15 is not ported is built from source like 14.1. For J5 (2015) we have great devs.
[Samsung Galaxy J5 Guides, News, & Discussion] Cyterafle:
I know what I'm talking about but Today,There's a MSM8916 devices who can get official Oreo ?
[Samsung Galaxy J5 Guides, News, & Discussion] Tisenoiazei100:
Unofficialy yes

Z9 Max for example: https://xdaforums.com/android/development/rom-lineageos-15-0-nubia-nx512j-t3672528

Officialy no
[Samsung Galaxy J5 Guides, News, & Discussion] Cyterafle:
Support is stopped officially
[Samsung Galaxy J5 Guides, News, & Discussion] ClaudiuXDEV:
Oreo can be ported for J5 2016 but is not that easy to fix the bugs because you don't have the right libs to use, not all the libs from N are compatible with O and there are so many missing. An example could be the RIL bug (sim bug), you need to replace the new main RIL lib but you can't find it in any other N rom... If you try to replace it or any other RIL file you will get a bootloop...
[Samsung Galaxy J5 Guides, News, & Discussion] Mubeen1:
I like your question.

I think all Samsung brands should be accepted it.
[Samsung Galaxy J5 Guides, News, & Discussion] Cyterafle:
I know this because Qualcomm has stopped support on their MSM8916 (Snapdragon 410)
[Galaxy Note 10.1 Android Development] pappschlumpf:
Three bugs,

soft keyboard not showing up, governor pegasusq faulty, settings fc once after boot. Same bugs as Lineage. Please switch governor to ondemand. Well, working on it. If i've time i'll fix these issues.
[Galaxy Note 10.1 Android Development] jika23:
Great work nice to see our old but awesome device been update.

Just a question and a corretion.

First should we use the 2.8.7.0 TWRP Recovery from Lirakoa or the last one from DesTroy

The gapps aren't 64 just arm 7.1.2
[Galaxy Note 10.1 Android Development] pappschlumpf:
I don't think that the TWRP version is important. I've used 2.8.7.0 to flash it. Anyway, use newest will work for sure too. Gapps to flash are for sure just ARM, not ARM64.

Gesendet von meinem SM-N950FD mit Tapatalk
[Galaxy Note 10.1 Android Development] jika23:
I will flash it tonight, once I get home from work.

Nice job.
[Galaxy Note 10.1 Android Development] svicenty:
Will definitely flash tonight and will let you know what's going on
[Galaxy Note 10.1 Android Development] Aramir_:
Then fix opengapps link in your post.
[Galaxy Note 10.1 Android Development] pappschlumpf:
Oh, thx, that's a copy of my Xiaomi Mi Mix OP. Changing the link now.

Gesendet von meinem SM-N950FD mit Tapatalk
[Galaxy Note 10.1 Android Development] OwenW71:
Followed the flash instructions, stuck in a bootloop and cannot get to Recovery again. Hrmmm.

Edit:

Got to Recovery, re-wiped, re-flashed, just watching the boot animation over and over.
[Galaxy Note 10.1 Android Development] svicenty:
Very nice rom you definitely put a lot of work into this the auto-rotate is not working though it stays in land mode other than that is a real good rom keep up the good work this would definitely be one of the best rom for this tablet

---------- Post added at 03:00 AM ---------- Previous post was at 02:53 AM ----------

The pixels go a little crazy when you go to recents
[Galaxy Note 10.1 Android Development] jika23:
Was about to report this same bugs. For now the only I've found.
[Galaxy Note 10.1 Android Development] pappschlumpf:
Give OmniSwitch a go ;)
[Galaxy Note 10.1 Android Development] svicenty:
Tried the OmniSwitch still it goes a little crazy the pixel now I'm noticing it's not only happening with the recents but other places as well so far looks like and you can clean up the pixel could be a a nice rum really nice work
[Galaxy Note 10.1 Android Development] sanangel:
No one has said anything and it just happens to me, but I can not change the brightness of the screen.
[Galaxy Note 10.1 Android Development] svicenty:
Nice rom just needs to be cleaned up, tweaked
[Galaxy Note 10.1 Android Development] dude73:
Its not just you,same thing happens to me
[Galaxy Note 10.1 Android Development] pappschlumpf:
I'll check with my N8013. OC kernel is on the list too. But it'll need some time, many things to at work atm.

Gesendet von meinem SM-N950FD mit Tapatalk
[Galaxy Note 10.1 Android Development] jyofre1973:
GAPPS installation problem in a gt-n8010.

Hi. Thanks for this ROM. I have a gt-n8010 and I've installed the ROM first successfully. I started for a first time the system and changed the keyboard settings. After that, I went back to recovery to install the gapps (arm 7.1 nano and micro). When the gapps package is being installed TWRP reboots and it doesn't finish the installation.

I have a problem right now because the boot animation is eternally looping without starting.

I have used 2.8.7.0 TWRP Recovery and I have performed a complete wipe (except for the MicroSD) of the system.

Is it possible that the problem is that I'm doing it with a n8010 and not a n8013. I think it's not the issue because the ROM installation seems to work fine. The gapps installation is the issue.

Any help, please?
[Galaxy Note 10.1 Android Development] svicenty:
Yea in the intro it says N8013
[Galaxy Note 10.1 Android Development] pappschlumpf:
No idea, i have the N8013. But well, what's about a size issue? Maybe a gapps package that is to large? Stock or full for example. I've used Mini.

Edit:

But if it boots without gapps, ROM is working. Looks to be a TWRP issue.

Gesendet von meinem SM-N950FD mit Tapatalk
[Galaxy Note 10.1 Android Development] dude73:
Mine is a n8010 and it flashed ok but I flashed ROM & gapps together . I also used the same recovery as you & arm 7.1 gapps nano
[Galaxy Note 10.1 Android Development] retiredtab:
The first post says "Based On Latest Google Android 7.1.2" and I would like to know if this includes the latest patches for Krack (wifi, wpa2 vulnerabilities).

The release notes for 5.8.5 at

https://github.com/ResurrectionRemix/android_vendor_resurrection/blob/nougat/CHANGELOG.mkdn

suggest no Krack fixes.

Can someone who has loaded this rom please post what the Android security patch level is in the "about device" screen?

Thank you.
[Galaxy Note 10.1 Android Development] pappschlumpf:
Krack is a kernel fix i have not included. But well, any other ROM around here having it? No. I'll update the kernel too, but for sure no ETA. My time, especially for working on N8013, is limited.

Gesendet von meinem SM-N950FD mit Tapatalk
[Galaxy Note 10.1 Android Development] xblosa:
Currently there is CWM 6.0.1.1 and Android Revolution HD21 (Android 4.4.2) installed on my N8010. Can I flash TWRP from CWM and then RR.?
[Galaxy Note 10.1 Android Development] retiredtab:
Hi Pappaschlumpf,

I appreciate your time and effort in this rom. I completely understand you are busy with work and holidays so any effort you can put into this is greatly appreciated.

I will not be bothering you for an ETA. I just hope to be happily surprised someday.

Thank you.
[Galaxy Note 10.1 Android Development] :
You have to flash TWRP from Odin I believe. But did you try flashing RR on CWM?
[Galaxy Note 10.1 Android Development] xblosa:
Meanwhile I flashed TWRP using heimdall (more or less the ODIN way). Did not update the ROM until now, need some time.....
[Galaxy Note 10.1 Android Development] lasbrujazz:
so far, the only bug i found is brightness. everything works perfectly well.
[Galaxy Note 10.1 Android Development] juniorhxcx:
Firstly thank you for more is ROM!

Could you port the N8000 model as well? Please!
[Galaxy Note 10.1 Android Development] Oceansoul91:
hi [MENTION=3910111]pappschlumpf[/MENTION] what should I change to flash it on n8000? build.prop, boot.img... ? (I don't need for porting phone part)
[Galaxy Note 10.1 Android Development] mohameddeela:
It is easy by deleting the first line of (updater-script) in META-INF\com\google\android and save it.
[Galaxy Note 10.1 Android Development] Oceansoul91:
Thank you :good:
[Galaxy Note 10.1 Android Development] zonedgold:
Wow great rom , great dev, love it. Thank you <3
[Galaxy Note 10.1 Android Development] DJDoom1:
Hello, can anyone download the version for n8000, I have a error when i changing file in meta- u.scprit
[Galaxy Note 10.1 Android Development] Oceansoul91:
I have this error too
[Galaxy Note 10.1 Android Development] mohameddeela:
delete the first line of (updater-script) in META-INF\com\google\android and do not leave the space .I did this step and it worked with me .
[Galaxy Note 10.1 Android Development] Oceansoul91:
Thanks again mate, I solved using notepad++ for editing the file, with other default editors didnt work, thanks! :highfive:
[Galaxy Note 10.1 Android Development] DJDoom1:
Can you share rom?)
[Galaxy Note 10.1 Android Development] radtech777:
Got everything up and going, except Bluetooth is not working for me. Anyone got a fix for that or some ideas?
[Galaxy Note 10.1 Android Development] Oceansoul91:
I'm uploading it on my gdrive, it's a bit slow and i'm going to play with my band :p I upload also the "updater-script" file to replace in in META-INF\com\google\android inside the original zip file. it's easy, just copy and paste it. I'll share the rom link later if You have any problems after replace. sorry for my english :silly:

updater-script link:

https://drive.google.com/file/d/194tFiMr7IYPK1luR9oN5tsktEoyBQP9c/view?usp=sharing

rom link (hope I have the permission):

https://drive.google.com/open?id=131MRZ-AOi0jNdOaQFxwJledUhexy8YgH

I can't test bluetooth now, till now I noticed only the glitch when lock screen or recent panel, btw this rom didn't give new life to my device, it's really pretty slow (not rom fault), maybe just too old.
[Galaxy Note 10.1 Android Development] zonedgold:
Amazing ROM but the brightness bug made me have to go back to my other ROM. Is there a work around for this bug?
[Galaxy Note 10.1 Android Development] svicenty:
Will definitely download again when the bugs gets fixed great rom
[Galaxy Note 10.1 Android Development] DJDoom1:
Thanks)
[Galaxy Note 10.1 Android Development] BlackCrow13:
any?

Awesome Rom just as my Note 3's. All the work greatly appreciated!

Have anyone been able to find a workaround for the Bluetooth or Auo-rotate? Seems to be the only 2 things missing from it:fingers-crossed:
[Galaxy Note 10.1 Android Development] indianninja:
is there some way to get any sort of soft keyboard?

Is there some way to get any sort of soft keyboard? This is the only thing stopping me from getting this awesome rom:(
[Galaxy Note 10.1 Android Development] pappschlumpf:
yes, sure, please read my installation instructions in the op. Install without gapps for first boot ;)

Gesendet von meinem SM-N950FD mit Tapatalk
[Galaxy Note 10.1 Android Development] indianninja:
You mean to say after all is over I can actually get back a soft keyboard? Cause I do not see attaching an actual hardware keyboard all the time I use it. I can sure do for once for making all okay....sorry if I sound a bit stupid since I am new to post anything in this forum. I appreciate very much the quick reply you have given and the prospect of actuallu being able to use this gives me hope......Indianninja