yashsingh1/xdaforums huggingface dataset:
[Moto Maxx General] calsurferpunk:
I updated the binder by reverting the commit that undid the Motorola changes (just leaving the new commit additions need for Oreo by Shamu now). Afterwards I went through and fixed the code to work properly (fixed a few function calls, added the appropriate debug lines, and removed the unused code per what the compiler demanded).

First I ran it with the original f2fs data partition and got the first attached log.

Next I ran it after making sure all partitions were ext4 and got the next attached log.

Neither booted beyond the starting boot logo (not in the operating system loading screen), but the logs did change a little bit. Towards the end of the f2fs boot it complained of the partition type being invalid, but the ext4 only boot had some less errors around that point.

Happen to notice anything else I might have messed up on? For convenience again, device: https://github.com/calsurferpunk/device_motorola_quark, kernel: https://github.com/calsurferpunk/kernel_motorola_apq8084.
[Moto Maxx General] fgl27:
try this branch

https://github.com/bhb27/kernel_apq8084/commits/f2fs_sdcard/

you need to update the binder driver and anything related to defconfig that is O only and maybe something that is not related to f2fs and sdcardsfs, because those things I already update plus some others (those that don't conflict with N or M) and they may be causing boot problems so there may be a improve on using that branch...

to update binder you may need to revert N binder changes I did... try with and without in case they don't cause conflicts...

https://github.com/bhb27/kernel_apq8084/commits/f2fs_sdcard/drivers/staging/android/binder.c

also undo this

https://github.com/calsurferpunk/device_motorola_quark/blob/lineage-15.0/BoardConfig.mk#L141-L144

you need those rules even on permissive there is somethings that need to exist, fix sepolicy build error by deleting or comente out the lines that cause problem on the it sepolicy file of device tree or qcom/sepolicy

and set this to ro.sys.sdcardfs=false

https://github.com/calsurferpunk/device_motorola_quark/blob/lineage-15.0/system.prop#L116

and check latest changes for shamu as they update the device and kernel, but the kernel seems to be only Linux updates on top of sdcardsfs and binder changes...
[Moto Maxx General] digolg:
oreo for maxx is dead?
[Moto Maxx General] fgl27:
something that never born can't die :silly:
[Moto Maxx General] ChazzMatt:
Read this post carefully. Post #4 of this thread.

https://xdaforums.com/showpost.php?p=73521810&postcount=4

It all depends on [MENTION=5747496]bhb27[/MENTION] and the kernel. No ROMs will come before that. He only has ONE phone, which he has to use daily with stable Nougat, then also use it for testing on it for Oreo. I'm sure he has a regular job, regular life. If he had two Quarks -- one for testing, one for daily use -- he could probably work faster. ;) Also, LOS 15 still isn't really stable, yet.

It'll be ready when it's ready.
[Moto Maxx General] digolg:
Everyone knows, I referred to the project, I thought a word to the wise is sufficient
[Moto Maxx General] PILLMUZIK3600:
I look forward to it. My daily is a zplay Droid but I fire up my turbo from time to time..
[Moto Maxx General] Hlcpereira:
[MENTION=6069596]calsurferpunk[/MENTION] try update tools and change init_quark.cpp on tree like link below to see if it works.

https://github.com/Oreo-quarks/device_motorola_quark/blob/Oreo/init/init_quark.cpp

Seems "SetProperty" on init cause in some devices no boot. And tools because have some people that doing that install successfully the builds.

But no boot can be a kernel issue also, but it doesn't hurt to try.
[Moto Maxx General] guyz_ahead:
Its never happening is it? Shall i lose hope or shouldn't i. [MENTION=5747496]bhb27[/MENTION] u are my rom god. Its my dream to learn making kernels and you are the one I take inspiration from. If you give up, we will be heart broken. If you want any help please let me know.
[Moto Maxx General] Kevanness:
He's working on it, here is his github page for Oreo: https://github.com/bhb27/device_motorola_quark/tree/O

If you look at last Saturday he put in a lot of work, I don't know how close it is to being bootable or stable though. The Nexus 6 is pretty close to having a stable build and once it does it'll make getting the Moto Maxx a stable build easier.
[Moto Maxx General] guyz_ahead:
​

Wow. Well thanks for keeping me updated. Thanks bhb
[Moto Maxx General] ChazzMatt:
You can read the latest update in this post, as well as see a screenshot of Quark Oreo 8.1 [MENTION=5747496]bhb27[/MENTION] posted.

https://xdaforums.com/showpost.php?p=75679058&postcount=4
[Moto Maxx General] guyz_ahead:
Any update on Oreo? :( [MENTION=3250376]ChazzMatt[/MENTION] [MENTION=5747496]bhb27[/MENTION]
[Moto Maxx General] ChazzMatt:
5 days ago:

So the XDA rule still applies. Don't ask for ETA. Sorry.
[Moto Maxx General] lat94084:
Android Oreo is coming soon without a defined release date:

https://github.com/bhb27?tab=repositories

[MENTION=5747496]bhb27[/MENTION] is updating the kernel, device and proprietary source trees, Want Android Oreo now? Build using the O branch, but some things may not working
[Moto Maxx General] calsurferpunk:
Thanks for the update. I didn't know he had any time to work on it lately. I was able to get a build of Lineage OS 15.1 to boot with it after some minor changes. Wifi and mobile data appear to be working so far, but bluetooth and some other things aren't yet (like you suggested). It's promising to see there is still work being done since I had been stuck on getting it to boot a long time ago. As soon as more is working and he gives the okay, I'll be sure to release builds as well :).
[Moto Maxx General] lat94084:
[MENTION=5747496]bhb27[/MENTION] some hours ago published more changes to source trees, but is not finished yet. And, How you built LineageOS 15.1? It would be interesting to have the instructions to build LineageOS for this device.
[Moto Maxx General] ChazzMatt:
Resurrection Remix Oreo:

https://xdaforums.com/moto-maxx/development/rom-resurrection-remix-t3811195

That means there is an Oreo compatible kernel by [MENTION=5747496]bhb27[/MENTION]. Now everybody and his brother can make QUARK Oreo ROMs.

Just remember who's the man. [MENTION=5747496]bhb27[/MENTION].

---------- Post added at 03:29 AM ---------- Previous post was at 03:24 AM ----------

Don't worry about it.

[MENTION=6069596]calsurferpunk[/MENTION] will make your Lineage ROM. ;)

He's probably working on it right now. He's the guy who kept Quark CM/Lineage ROM going the past couple of years.
[Moto Maxx General] ChazzMatt:
Here's Lineage ROM:

[ROM][All Quarks][8.1][LOS 15.1 Unofficial][2018-07-04]

https://xdaforums.com/moto-maxx/development/rom-t3812506

"Unofficial" on purpose, so it's better. Read the thread.
[Nexus 6P General] ThaHaloMilitia:
Join the conversation on Hangouts: https://hangouts.google.com/group/mXRpImw34fL9sqAF2
[LG G6 Questions and Answers] Android Oreo:
Hi guys

i have a h870 G6, today i have unlocked Bootloader for Rooting my device

i Followed this thread

[GUIDE] Official LG G6 Bootloader Unlock (Currently supported: EU H870, USA US997)

but i can't pass the 9th stage :(

i flashed the phone with twrp.img and Reboot the phone in recovery mode, i can see the Factory Reset screen, i have clicked on the first and second YES, the data is erased ( no problem i have a backup ) but i dont know what doing after this stage :( the phone is rebooted to the normale mode now.

please help me to rooting my device please. :(
[LG G6 Questions and Answers] Killua96:
After flashing the TWRP you need to reboot in recovery with the combination explained in that thread, if you don't reach the reset you'll have to flash the TWRP again.
[LG G6 Questions and Answers] Android Oreo:
thanks for you reply

after flashing with twrp, i rebooted my phone in recovery mode and i get the white screen ( have only YES or No for erase data ) and i don't know what do after that.
[LG G6 Questions and Answers] Killua96:
If the phone didn't reboot once between the flash of TWRP and the boot trough combination in recovery you have to confirm yes two times and you'll enter in TWRP
[LG G6 Questions and Answers] Android Oreo:
Thanks bro

after 2 Yes the phone reboot on recovery mode and i installed SuperSu, and DONE :D

another question ! How delete the first screen ( g.co/abh ) if you know Sir ! and thanks for your help
[LG G6 Questions and Answers] Killua96:
It's not possible to remove It ;)
[Sony Xperia XA Themes, Apps, and Mods] capaficionado:
Hey guys, I have an old Xperia XA living around, and I'm planning to root it soon and use substratum themes with Sony's ROM, but I'm confused if it's even substratum compatible or not.

Please let me know, thanks.
[Sony Xperia XA Themes, Apps, and Mods] levone1:
I don't think so. I don't know exactly how it works. I don't think it's quite like Xposed, where there needs to be a special framework in place, (since many Substratum themes do work on Los14, which is not officially supported), but I think there does need to be a compatible environment, similar to or based on AOSP. I think Xperia has it's own version of theming framework. For example, many of the files that control the UI on an Xperia are named 'somc_(something)'. Those files are specific to Sony phones, so a different theme engine wouldn't by default have any references to them.

However, I've never tried...
[Sony Xperia XA Themes, Apps, and Mods] jimxperia9:
what theme you use??thanks
[Sony Xperia XA Themes, Apps, and Mods] jimxperia9:
hello again...can you give me the link of the theme you use ?? (Grace UX)I can not find it :( thanks

also i test many themes on substratum theme engine and nothing happend.
[Android Studio] maja_ldm:
The option to merge unrelated histories on a Github account used to be a checkbox in the Push interface of the Git menu of Android Studio, but in the newer versions it disappeared from there and I can't find it anymore.

How can I set the option to allow unrelated histories with Android 2.3?
[Nexus 5X Q&A, Help & Troubleshooting] Z0l:
I updated to Oreo by signing up to the beta program and installed the full upgrade (~1GB) earlier today. It worked flawlessly for several hours and then the phone froze; I was unable to boot it up after that. I booted into recovery, performed a cache wipe, but since that, it still won't boot and now I can't go to recovery either (just get a blank screen after the Google logo). My device is locked, so I can't do a fastboot flashing unlock :(

Do you have any ideas what to do next? I can still go to fastboot and issue fastboot commands and the phone charges if I connect a charger in a powered-off state, but that's it.
[Xiaomi Redmi Note 3 Questions & Answers] Unipo:
Hey guys! I was wondering why can't we encrypt /sdcard as we do for /data?... In my opinion my files/documents/photos are sensitive information as my data partition is...
[Xiaomi Redmi Note 3 Questions & Answers] Unipo:
Up?
[HTC 10 Questions & Answers] thunder2132:
Hi everyone,

I've been having issues with receiving calls and based on another thread for the HTC 10 decided to wipe modemst1 and modemst2 to try to figure it out. After wiping them my phone no longer detected the sim card. I ran a RUU which didn't resolve the issue. I'm using a Sprint HTC 10, unlocked bootloader, S-off. So far my process has been:

1. S-off.

2. fastboot erase modemst1 and 2 from bootloader.

3. Reboot to Viper, no SIM detected.

4. Factory reset Viper, no SIM detected.

5. RUU with latest Sprint RUU, reboot, no SIM detected.

Any thoughts on my next steps? If it matters I'm running the RUU with the zip on my SD card.
[HTC 10 Questions & Answers] thunder2132:
I'm not sure how to mark this as resolved, but I got past this part. I flashed to LeeDroid, it popped up and told me simlock was enabled. Apparently in what I was doing I lost my sim unlock. I re-performed the NV method of sim unlock and have signal again. It still hasn't resolved my issue with not receiving phone calls, but at least I'm back to where I started.
[8525, TyTN, MDA Vario II, JasJam ROM Development] wpl11972:
Where in the world is vp3g. Is he in the kitchen cooking.
[8525, TyTN, MDA Vario II, JasJam ROM Development] sd619:
I've been missing his cooking, too. We haven't heard from him in months. I hope everything is well with him and he soon finds the time to cook for us again.
[Android Q&A, Help & Troubleshooting] Unipo:
Hey guys! I was wondering why can't we encrypt /sdcard as we do for /data?... In my opinion my files/documents/photos are sensitive information as my data partition is...
[Android Q&A, Help & Troubleshooting] Unipo:
Up?
[Android Q&A, Help & Troubleshooting] Unipo:
Seriously, no one?
[Android Q&A, Help & Troubleshooting] two_handed:
Little late... Anyways, I too am wondering all the time why encryption seems to be relevant for only a really small number of users.

Since you can only encrypt your SD Card with LOS when formatting it as internal storage via assistant, I chose to go this way:

https://guardianproject.info/2011/02/02/create-an-encrypted-file-system-on-android-w-luks/

Did you find another solution?
[Android Q&A, Help & Troubleshooting] Unipo:
[MENTION=4382927]two_handed[/MENTION]

Sorry I moved to CopperheadOs, my Mi5 was only pure lineage with F-Droid as system app.

I noticed that you don't have access to /data on you encrypted lineageOs phone which means apps data, pictures, music, etc... But you still have access to everything else (/system included) through adb/fastboot.

I wanted a secure phone without google crap, only FLOSS apps, and CopperheadOs is one of the few allowing you (more like forcing you) to relock you bootloader to activate boot secure and prevents anyone to use fastboot/adb shell if your phone gets stollen.

Concerning your question, maybe this http://sovworks.com/eds/ ? Sort of veracrypt for android, also working with veracrypt containers.
[Moto G5 Plus Questions & Answers] SirPeriwinkle:
Hi everyone, I'm a huge fan of rooting and installing custom roms, but the way motorola makes you void your warranty scares me. I'm normally very careful with my devices but I always like to have the option to flash back to stock and send it in if I have to. That being said, I was thinking of switching over to Resurrection Remix, and I was wondering everybody's thoughts on whether its worth voiding the warranty as the stock software is pretty good as is.
[Moto G5 Plus Questions & Answers] divvykev:
I am newly over from being a long time Nexus user so have flashed a fair few Roms in my time. But, even on the Nexus I was getting to the point that Stock was doing the job and was only rooting to install adaway. Then I found dns66 and so went back to stock.

Since getting my G5Plus all I have done is updated to the latest version and am purely stock. Personally I dont see the benefit of rooting at the moment.
[Moto G5 Plus Questions & Answers] Jrhotrod:
Resurrection Remix is so heavily modified it's basically a skin. I would recommend Lineage; you won't know how you lived with stock after you get it. Plus, it'll take Lenovorola months to roll out Oreo, and custom ROMs will have it sooner.
[Moto G5 Plus Questions & Answers] SirPeriwinkle:
I've tried lineage before on a Samsung Galaxy Tab 3 8.0, and it was great(the tablet was super slow though). My main reason for wanting to go with RR is because of the customization as well as the fact the G5+ build contains all of the moto-exclusive features so i'm not giving anything up except my warranty.
[Moto G5 Plus Questions & Answers] BubuXP:
I'm in your same situation. Just like user divvykev I don't need root after discovering DNS66, but my brain want to hack every device I get in my hands...

Very occasionally my G5+ lags for some seconds, almost freezes. I don't know what's the cause, but now I have to try another ROM to check if the problem persists.

And I want more customization than the stock ROM can offer.

And thinking that we're on Android 7.0 when there is 7.1.2 available won't let me sleep at night :)

And consider also the security updates, that are almost real-time in some custom ROM, while on stock we're still on May 2017 (at least me with "reteu").

And I don't know when Lenovo will deploy Android 8 for G5+, but with a custom ROM we can do it by ourselves in a month or so.

And I miss so much the LED notification...

My first smartphone was Moto G 2013. I unlocked the bootloader and rooted after a week and I didn't regret it for a single second (it's still alive and working fine thanks to custom ROM's developers). The G5+ is already two weeks old and still it's on stock ROM, but it's only a matter of days for bootloader unlocking.

And the warranty? I'm in Europe and many people say that here unlocking the bootloader won't void the warranty, despite what the manufacturers say.

I still haven't had the pleasure to find if that's true, and I hope to continue like this.
[Moto G5 Plus Questions & Answers] Jrhotrod:
So does Lineage
[Moto G5 Plus Questions & Answers] vee.vardhan:
Official Lineage?

I know there is no official support for G5 Plus (Potter) yet, and there is one unofficial build, in fact I am running it right now! But, I wanted to know if there will be official support to it or the unofficial one will get updates.

Thanks!
[Moto G5 Plus Questions & Answers] Sahilsinghlodhi:
Camera quality? Is there some ROM with stock like camera quality? Have tried 3-4 ROMs just to get back to stock everytime.
[Moto G5 Plus Questions & Answers] Jrhotrod:
Pretty much every ROM, in my experience, has camera quality just as good as stock. If you really want the full potential make sure to change the aspect ratio to 4:3 and 12.2 megapixels.
[Moto G5 Plus Questions & Answers] eleazar6:
Since when does Motorola void warranty for bootloader unlocked devices? My 2014 Moto X and 1st gen Moto X both had warranty repair with an unlocked bootloader.
[Moto G5 Plus Questions & Answers] SirPeriwinkle:
To unlock the bootloader you have to got onto motoroals website and get a code. When you do so they give you all these warnings and make you accept a terms of service that'll make you unable to submit warranty claims
[Moto G5 Plus Questions & Answers] Azphreal:
Most OEMs state that unlocking the bootloader voids warranty. Every ROM on XDA also says the same thing. More importantly, Motorola makes you go through a signup/generate unique key for your unlock, which means they have the fact that you unlocked your bootloader on record.

From section 5 of Motorola's legal agreement when you go through their unlocking process:
[Moto G5 Plus Questions & Answers] eleazar6:
Looks like if you mess up your software, it's not covered. But if it's a hardware issue, it will be. My issue was hardware related, so I was covered.

https://forums.lenovo.com/t5/Moto-X...-re-Warranty-for-Pure-Style/m-p/3202233#M5570
[Moto G5 Plus Questions & Answers] SirPeriwinkle:
So I just got off of chatting with a Motorola support rep. I showed them the link and they said to call the support telephone number to clarify further
[Samsung Gear S3] coolhandz:
Just flashed stock Android O to my pixel xl then rooted. Samsung pay doesn't seem to even start whereas before with root it would start but then say it doesn't work on a rooted device. This would leave me to believe that SPay didn't work yet on Android O. Can anyone offer input on this? Thanks
[Samsung Gear S3] benrees21:
Was just about to come and ask the same question. I know it was not working at all on the Beta of Android Oreo but I thought it would on the official build but nope, looks like we gotta wait for Samsung to update something...the Spay app or the gear app...dunno.
[Samsung Gear S3] uodii:
Is your gear S3 actually working on Android O? When I was on DP4 on my Pixel I could not even connect it to my phone and the gear app wasn't compatible via the play store either
[Samsung Gear S3] coolhandz:
Mine is working on O. I get all my notifications and everything like before, just SPay won't even start.
[Samsung Gear S3] bootsie99:
Same Here cant get Samsung Pay to install on Pixel running Oreo then obviously cant setup on my Frontier
[Samsung Gear S3] Liquidarmz:
Same here with my Nexus 6P, everything except Spay seems to be working fine.
[Samsung Gear S3] MrMediaGuy:
Joined the Android Beta program last week in order to get the 8.0 OTA on my Pixel without waiting. As others have noted, everything else works fine (mostly) but Samsung Pay doesn't open and delivers a crash dialog when opening the Gear app. Also visiting the Play Store no longer shows the Pay app at all, and going to the Play Store on my PC while logged into my Google account lets me get to the Pay app page, but it's marked "This app is incompatible with your device." So, no way to reinstall. (Also, the Pay app is no longer in the launcher or in the Gear applications list.)

I assumed I was out of luck probably until Samsung releases Oreo on their phones, when I'd expect an 8.0-compatible version of the Gear and Pay apps to be available. HOWEVER, in scrolling through my running apps today on my Pixel, what should I see in the list? SAMSUNG PAY. Running in the background. Well, I thought, what if I just access the Storage page and clear the cache and data and restart it? VOILA! I used my watch (not the phone!) to launch Pay, and it immediately opened the setup dialog on my phone. I was able to sign back into my Samsung Pay account and re-add all my credit cards without any problem, and everything is now working fine.

EXCEPT -- the Pay app still doesn't appear in the Launcher or in the Gear apps list, so I guess it's running in some weird stealth mode. But it's running, which is all I care about. So if SPay isn't working for you after updating to Oreo, try Settings > Apps, find the app in the list, go to Storage, and delete data and cache. Launch Pay from the watch and see if it works.

(Note that I am on the OTA install, which means my phone wasn't wiped to install Oreo and the Pay app was still on the phone. If you flashed from the bootloader and you are installing from scratch I think you're out of luck since there's no way to reinstall Pay just yet.)
[Samsung Gear S3] daddylonglegs:
I accidentally uninstalled Samsung Gear trying to fix this issue. How can I get the Samsung Gear apk again? Is there any way you can pull the APK (AirDroid makes this very easy) and you can upload it?
[Samsung Gear S3] coolhandz:
Found a solution on Pixel XL using Oreo (OPR6) which is rooted using SuperSU and has SU Hide.

1. Download Samsung Pay for Android Wear

2. Download Samsung Pay framework

3. Install both

4. Hide both in SU Hide (tap each app once)

5. Turn off AdGuard (probably just me) to connect to server

6. add cards and let the cashiers be wowed by the magic of the gear S3

*Edit*- I will add that Samsung Pay doesn't show up in the Samsung Gear app or in the apps listed on the watch (shows SPAY version 0.0.1), but SPAY will open when you use the watch.
[Samsung Gear S3] daddylonglegs:
Thanks so much but is there any way you can upload the Samsung Gear app itself? The main one? The one for non-Samsung phones? It absolutely refuses to show up in the Google Play Store because I am on 8.0 :(
[Samsung Gear S3] coolhandz:
Here is the link for the full Samsung Gear app.

Edit: read your post wrong. Here is the link for the gear app not the SPay app.
[Samsung Gear S3] MrMediaGuy:
That's really strange -- I'm on 8.0 and never had any problem seeing the Gear app in the Play Store, only the SPay app. Have you tried accessing the Play Store from your PC while logged into your Google Account? When you do that, the Gear app will always show up -- it will just tell you if it's able to be installed on your device or if your device is incompatible. What does it say?
[Samsung Gear S3] daddylonglegs:
It says my device is incompatible. Does not matter if I am doing it on the phone or on the PC! What could be wrong?