yashsingh1/xdaforums huggingface dataset:
[Huawei Mate 9 Guides, News, & Discussion] revjamescarver:
A/B partitions

Wrong, A/B partitions are used for "seamless" upgrades, that has absolutely nothing to do with project treble from Google. The mate 9 under Oreo is "fully" treble complaint. The vendor partition is always going to be upgraded from the vendor as this is where most of the closed source drivers and binaries live the Android system itself is just separate now from all that because of project treble, but don't expect that Google will be providing updates to any phones other than their own due to all the bloatware and ui stuff.
[Huawei Mate 9 Guides, News, & Discussion] Icetea:
[MENTION=4862365]revjamescarver[/MENTION]

as i wrote, "as i know"!

And how (or where) do you get your informations???
[Huawei Mate 9 Guides, News, & Discussion] revjamescarver:
Information

As far as treble requirements, straight from Google. Google does not "require" vendors to implement the a/b partitioning scheme, regarding the a/b partitioning scheme, straight from the vendors that implement it. There is tons of documentation on this and I'm not going to waste my time explaining it to you, go read it all yourself
[Huawei Mate 9 Guides, News, & Discussion] Icetea:
it looks like i had found my next candidate for my personal ignore list now.

btw: answers like yours are not very helpful to prevent spreading wrong facts!

and again: i have written "as i know" and not "you should know".

anyway, i will spend my time now also to more rewarding themes.
[Huawei Mate 9 Guides, News, & Discussion] kolembo:
...waste time?

Unhelpful.
[Sony Xperia X Accessories] lazl0brav0:
Im going to order Devilcase Luster Screen Protector but the only available is for XP, so my question is, do Xperia X and Xperia X Performance share the same screen size(the camera lens, speaker locations, sensor)?
[Sony Xperia X Accessories] non.verbal:
yes screen size is the same, x performance is only slightly thicker but from my experience most cases fit too
[Sony Xperia L] sahitha:
Hi all,

I was running LineageOS 14.1 Official Latest Build lineage-14.1-20180119 and I have updated the TWRP from 3.0.2-0 to 3.2.1-0. After flashing to boot from within recovery it does not reboot. Just nothing.

No Screen or LEDs. When pressing the power key it vibrates. No fastboot or Recovery mode.

Red LED flashes when connected to PC. That's it. Nothing else.

Please help!!!!!
[Sony Xperia L] OverBim:
I had this too. To recover:

- Download lineage-14.1-20180119.zip, unpack it and locate the file "boot.img".

- Download flashtool (I used v0.9.23.1).

- Boot into fastboot mode:

- Disconnnect the USB cable, Turn off phone and wait a bit.

- Hold volume+ and connect the USB cable.

- The phone should show a blue status light.

- Flash boot.img using FlashTool (press Flash icon, Flash kernel only).

- Reboot phone to system in FlashTool

This should bring your phone back up.

To install TWRP, I always use one of those procedures:

- Connect phone via USB and enable ADB

- Copy .img to some location on phone, eg. /storage/sdcard1

- Start ADB shell

- Run command via ADB:

su

dd if=/storage/sdcard1/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel

OR:

- Connect phone via USB and enable ADB

- Run on host computer:

adb root

adb wait-for-device

adb push "PATH_TO_TWRP_IMG_FILE" /tmp/twrp.img

adb shell dd if=/tmp/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel

If adb is complaining about "no premissions" for your device, try:

sudo adb kill-server

sudo adb start-server
[Sony Xperia L] sahitha:
Awesome!!

You are AWESOME!!! that actually worked!! Thank you very much [MENTION=5997283]OverBim[/MENTION]

I was very hopeless about recovering the phone. Thank you again.

And if you can, please tell me what did I do wrong or what happened to cause that.
[Xiaomi Mi A1 Questions & Answers] BloodRose:
I received this phone as a Christmas present and I'm generally happy with it except the Amazon Shopping app crawls. It takes ages to load and will often bring up a couple of crash warnings before finally loading and moving between pages seems to take forever. This seems to happen regardless of which data network I'm connected to at the time (WiFi or 4G). The phone also isn't running in power saving mode.

It's running the latest official ROM. Does anyone have any ideas?
[Xiaomi Mi A1 Questions & Answers] geekyzahed:
Same issue here on redmi 7

Were you able to resolve the issue? I am facing the same issue on my mobile
[Galaxy Tab S Q&A, Help & Troubleshooting] jack_ssl:
Hi Guys

Urgent Tab S Germany Firmware To Indian Firmware Possible .. CSC Code : DBT To CSC Code : INS .. Any Problem If I Change .. Flash Indian Firmware ?
[Galaxy Tab S2 Q&A, Help & Troubleshooting] jack_ssl:
Hi Guys

Urgent Tab S Germany Firmware To Indian Firmware Possible .. CSC Code : DBT To CSC Code : INS .. Any Problem If I Change .. Flash Indian Firmware ?
[One (M7) Q&A, Help & Troubleshooting] mkenbu:
HBOOT STATUS

m7cdtu relocked

cid htccn704(İ changed it years ago im not sure it is original)

hboot 2.49.0000

radio: u3.19.3509.4

opendsp-v35.120.274.0718

qsc-1237.29.35.0903

OS-7.17.401.6

Here is Device info

(bootloader) version: 0.5

(bootloader) version-bootloader: 2.49.0000

(bootloader) version-baseband: U3.19.3509.04

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 7.17.401.5

(bootloader) version-misc: PVT SHIP S-OFF

(bootloader) serialno: HC35KW907694

(bootloader) imei: 123583295771204

(bootloader) meid: 00000000000000

(bootloader) product: m7cdtu

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0780000

(bootloader) cidnum: HTCCN704

(bootloader) battery-status: good

(bootloader) battery-voltage: 3875mV

(bootloader) partition-layout: Generic

(bootloader) security: off

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: dirty-d0e3b226

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

all: Done!

I cant flash RUU, there is no recovery even if i can flash recovery my phone goes boot loop. entering recovery I really need to find the real problem guys ty.
[One (M7) Q&A, Help & Troubleshooting] alray:
Why? What's wrong when flashing the RUU?
[One (M7) Q&A, Help & Troubleshooting] mkenbu:
FAILED (remote: data length is too large) when i tried to flash fastboot gives me that message.

Can you send me a true RUU file ty.
[One (M7) Q&A, Help & Troubleshooting] lucyr03:
You need htc_fastboot.exe
[One (M7) Q&A, Help & Troubleshooting] alray:
7.17.401.5 ruu is available on androidfilehost.com

Flash it using htc_fastboot.exe or rename the zip PN071IMG, save the file at the root of a fat32 sdcard and reboot in bootloader mode with the sdcard in the phone and youll be able to flash the RUU without using fastboot
[One (M7) Q&A, Help & Troubleshooting] mkenbu:
okey guys here is the problem i have flashed the wrong RUU. My original OS name was 5.15.1403.32 Or something like that i dont know. I dont think my hboot, radio and os is right. Htc 802t is very problematic to find a RUU. I also tried htc boot exe and the PN07IMG method.
[One (M7) Q&A, Help & Troubleshooting] santod040:
http://d-h.st/8OH
[One (M7) Q&A, Help & Troubleshooting] mkenbu:
header error 32
[One (M7) Q&A, Help & Troubleshooting] mkenbu:
i get that message header error 32
[Xiaomi Mi A1 Questions & Answers] prasanna0007:
Hi all.

I m on latest official android 8.0 with January security update after January update my Bluetooth option get automatically on.too much battery drain takes place.

Any one facing same issue.????

Waiting for solution.

Thanks in advance.
[Xiaomi Mi A1 Questions & Answers] coremania:
No, works perfect, not much drain.
[Xiaomi Mi A1 Questions & Answers] _crAss_:
I have big battery drain as well when Bluetooth is activated at all times. When I turn it off manually the battery consumption is back at normal. I didn't have the problem with the first oreo update which had December's security update.
[Xiaomi Mi A1 Questions & Answers] YarpenZ:
Recently I am facing the same (or similar) issue.

Whenever I unlock the screen - the blutooth icon is ON and goes off after maximum of 1 - 1,5s (sometimes it is faster, a blink of an eye)

How can I identify the app/process turning it in? My battery consumption was very satisfactory up till now - now it is drained much faster :(
[Xiaomi Mi A1 Questions & Answers] surajnath:
Same problem with me. My bluetooth get turned ON automatically. I have to manually switch it off. However, it again turns ON after 5 mins. I play mobile legends and the game works damn slow when the bluetooth turns ON. I need to get this problem fixed ASAP so that I can play my game with out interruption!
[Huawei P9 Questions & Answers] clouds5:
Hi guys,

so as a musician recording stuff with my phone is quite important because, just like with cameras, the best recording device is the one you have with you when inspiration strikes.

Recording audio was always amazing with the P9. Very good and clear recordings. But since a recent update (i think it was b390 or b394) it distorts way too easily when the source has a certain volume. Making it impossible to record a band practice jam or something like that. And since I record stuff regularly this is definitely something new. So either my microphone is broken or the software has changed.

-->Normally the auto-gain is very good and automatically adjusts the input levels down, so that's what seems to be broken in my case. And that would mean it's just a software issue. Before I start flashing old ROMs I was wondering if you guys could do a little recording test with a loud stereo or something and report your findings (using the stock recording app or stock camera app, video recording with sound).

I'm running a P9 with:

-Bluewei 5.7 b397 (https://xdaforums.com/p9/development/bluewei-test-crossflash-to-l09-c432-t3608270)

but the issue was also present in the ROM i used before:

-moonlight 5.0 b394 (https://xdaforums.com/p9/development/p9-moonlight-rom-v1-0-b378-stock-t3567223)

So if you could tell me the software version you're using and how easily it distorts that would be greatly appreciated :):good:

cheers
[Huawei P9 Questions & Answers] clouds5:
Tested B390 and the problem persisted. So at this point I'm guessing it's either the custom ROMs that cause the issue (I don't have the time to test full stock atm) or my microphone is just broken.

Would be really great if anyone with anything B390 or higher could do a little test...
[Huawei P9 Questions & Answers] clouds5:
So just flashed the newest version of:

https://xdaforums.com/p9/development/p9-moonlight-rom-v1-0-b378-stock-t3567223

And the problem vanished. I guess it was a software issue after all.
[Xposed Framework Modules] C3C076:
Changelog 8.6.0 - 14/02/2021

- Added compatibility with EdXposed v0.5+ and LSPosed

- Added support for LSPosed module scope feature (auto-whitelist)

- Maintains backwards compatibility with EdXposed v0.4 and OG Xposed Framework

--- moving from old OG Xposed Framework to EdXposed/LSPosed is now strongly recommended, though!

- Does not require Xposed Resource Hooking support to be enabled anymore!

- Resource replacement:

--- redesigned for better compatibility and performance

--- implemented support for aliased resources pointing to Framework resources

--- Added support for resource overlays:

------ improves Advanced Tuning compatibility with systems using Theme overlays

------ fixes "Remove corner padding" option on Nokia (and other) devices

------ fixes hiding navigation bar by disabling "Enable navigation bar" option in Navbar tweaks

- StatusbarClock: respect time zone changes when showing seconds

- StatusbarClock: keep master switch for Clock tweaks off by default (thanks to aviraxp)

- Media: improved compatibility of More music volume steps feature

- Keys: improved reliability of Torch on power long-press

- ImagePicker: use dedicated library for cropping images instead of unreliable camera CROP intent

- About: added references to EdXposed and Riru

- Fixed XSharedPreferences Unexpected EOF errors showing in Xposed log

- Fixed layout/scaling of all GravityBox view elements affected by DPI change when screen resolution changes

IMPORTANT: Module settings are reset when framework is upgraded from EdXposed v0.4/OG Xposed to EdXposed v0.5.1+/LSPosed

due to changes in preferences storage location for modules in EdXposed v0.5/LSPosed

It is recommended to create a backup of GravityBox settings before upgrading the framework.

Developed and tested on:

- Nexus 5X running stock 8.0

- Nexus 5X running stock 8.1

- OnePlus 3T running stock OOS 5.0.1 and Beta

Download

Release 8.6.0 · GravityBox/GravityBox

Added compatibility with EdXposed v0.5+ and LSPosed Added support for LSPosed module scope feature (auto-whitelist) Maintains backwards compatibility with EdXposed v0.4 and OG Xposed Framework --- ...

github.com

EdXposed / LSPosed

Modules is compatible with EdXposed as well as LSPosed

Required whitelisted packages

- Android System (android)

- System UI (com.android.systemui)

- Call Management (com.android.server.telecom)

- Download Manager (com.android.providers.downloads)

- Phone (com.android.dialer or com.google.android.dialer)

- Phone (com.android.incallui) (OxygenOS only)
[Xposed Framework Modules] C3C076:
Important info about GravityBox and Oreo

Preferences and SeLinux

Although there is a limitation in current beta of Xposed Framework which prevents modules from reloading preferences within Android process,

GravityBox has been redesigned to overcome that limitation. This means enforced SeLinux is fully supported and thus it is not necessary to run Permissive.

Navigation bar tweaks on Pixel devices running proprietary Google SystemUI plugin

As I currently don't own any Pixel device I didn't have a chance to test nor adjust related features for such scenario.

I cannot tell how their plugin affects the way module works but let's wait for some feedback.

It is also possible that Navigation bar tweaks is not the only place where incompatibilities may show up.

Expanded Desktop in Oreo 8.1

Expanded Desktop is currently not fully supported in Oreo 8.1 (seems to be working fine in 8.0, though).

Despite there are almost no differences in related Android system parts between 8.0 and 8.1, I didn't manage to fix it, and I am currently not sure what's causing a differnt behavior.

There are only 2 modes available in 8.1 - Hide navigation bar and Semi-immersive (which is also temperamental)

Data activity indicator for Cellular icon

Due to changes in stock signal cluster layout type it is no longer possible to put activity indicators on top of a signal icon.

Therefore this feature has been redesigned to place narrov view containinig indicators right beside the signal icon.

WiFi is OK - there were no changes in layout type.

Notification drawer style in Oreo 8.1

Custom wallpaper/color for notification drawer is currently not supported in 8.1.

QuickSettings management

QS management has been massively redesigned for compatibility with stock SystemUI tuner back in Nougat and the same approach is taken for Oreo.

GB doesn't provide tile reordering functionality anymore. It only provides interface for enabling/disabling GB specific tiles and setting their protected mode (and other settings).

There are 2 checkboxes for each tile in the list - the first checkbox is for enabling/disabling tile, the second one is for protected mode.

There are also several stock tiles in the list with only the second checkbox - for setting protected mode (prevents using tile when device locked).

SystemUI tuner shows only those GB tiles that are enabled in GB QS management.

Use stock tile management to drag and drop GB tiles to desired slots.

Settings from Nougat

It should be possible to restore backup of the settings made in N version of GravityBox.

Full history of changes for transition from N to O

https://github.com/GravityBox/GravityBox/compare/v7.0.6_n...v8.0.0-beta-1_o
[Xposed Framework Modules] ntoetsoekarno:
Nice work!
[Xposed Framework Modules] Eazii:
Yeah Doe!!!!
[Xposed Framework Modules] firefds:
Looking forward to test this! Great job!
[Xposed Framework Modules] daddylonglegs:
I just tried this on my Google Pixel on Android 8.1 and I know you were asking this in the OP but all of the navigation bar tweaks I tried work perfectly! Every single tweak I tried works. If you would like me to test anything out for you on my Pixel, let me know.

Thank you so, so much for this. You have no idea how extruciating it was waiting for Xposed to get ported to Oreo and then GravityBox. It is my most-used mod and hoenstly the only thing keeping me using Android. You have no idea how much better of a phone experience I have with GravityBox.

You are amazing. Thank you again.
[Xposed Framework Modules] Johnny_B:
Absolutely fantastic work mate! So cool we can enjoy the great GB so soon!
[Xposed Framework Modules] emonkhan826:
Battery icon position not correct please fix this
[Xposed Framework Modules] sjamie:
I "finally" worked out all of the bugs with the N rom I am using on my OnePlus 5 and then you release this most awaited gem today... HALLELUJAH! :highfive:
[Xposed Framework Modules] omar2005:
nice work!
[Xposed Framework Modules] karige:
What a sight of relief!

Thanks
[Xposed Framework Modules] Prattham:
Make a full reboot after enabling the module
[Xposed Framework Modules] JRJ442:
[MENTION=5008415]C3C076[/MENTION] is there any way to get some type of extended SystemUI tuner function? Like how on stock you can get rid of certain status bar icons. Custom ROMs have all icons exposed so you can get rid of them. Like the VPN key for instance. Thanks so much for this. Definitely gonna be making a donation ?
[Xposed Framework Modules] Prattham:
My setup is same and it works fine
[Xposed Framework Modules] Sahib Pandotra:
What are the Tweaks under fingerprint launcher ? Do it enables fingerprint gestures ?

Nice work though :)
[Xposed Framework Modules] C3C076:
You can define action for each enrolled fingerprint independently. Thus you can use different fingers for different actions + one quick tap action.
[Xposed Framework Modules] hougga:
It's just my "must have" what a release! Thank you! :svetius:

Ps:working like a charm on S4 i9505 Oreo 8.1 AOSP JDCTeam.
[Xposed Framework Modules] B4oE:
I'm currently running Open Beta 21/Android 8.0 on my OnePlus 3T. The only bug I've found is on the Lockscreen Tweaks. The Hide Bottom Actions does not work. I've even rebooted after enabling the option but nothing happens. Please fix when you can.
[Xposed Framework Modules] Johnny_B:
Don't know if you're ready for some troubleshooting yet, but I'll give you my (rather small) issues:

- Lockscreen battery text is aligned left of all icons, while unlocked the text is in the right corner where it belongs

- Tap on clock action in QS pull down not responding

- Lockscreen bottom shortcuts cannot be hidden

All this on a Oneplus 5 with latest stock OOS.

Hope this helps!
[Xposed Framework Modules] renzo.olivares:
I actually was using this until I began to use an overlay that moves my clock to the left. With that overlay enabled lock clean no longer works for status bar . It would be great if this would be incorporated into GB or the ability to move the clock to the left.
[Xposed Framework Modules] ivicakc:
Guy's is anyone have carrier label?
[Xposed Framework Modules] C3C076:
Center clock is for status bar, not for notification shade. It's always been like that. Not sure about overlay. I don't use n5x often but so far I didn't notice anything weird about overlay. Maybe it's just subjective. Maybe one day I'll be looking into it closer.
[Xposed Framework Modules] kimikim0:
Work completely as it should on OnePlus 5, thank you, please enjoy your vacay, we can't wait [emoji8][emoji8]
[Xposed Framework Modules] 911jason:
Which overlay moves the clock to the left?
[Xposed Framework Modules] renzo.olivares:
Look for subtweaks in substratum it has many options.
[Xposed Framework Modules] :
Hi, first thanks for the update, everything works flawlessly!

However one small hiccup:

Before this version, I used the Xposed module "Ambient display enabler" on my OnePlus 5T to circumvent the OnePlus awful ambient display. It worked alongside GravityBox but I now guess that this was because lockscreen stuff was broken in GravityBox on OOS, right? Because now, the Ambient display doesn't work anymore, screen turns on when notifications arrive :(

Is there any chance to fix this or am I out of luck ?

Thanks

Edit: In fact after uninstalling the mentioned module, the stock OnePlus Ambient display seems to be broken too by GravityBox...
[Xposed Framework Modules] Dark_Eyes_:
[MENTION=5008415]C3C076[/MENTION] Many thanks for this great module. Everything I use is working flawlessly. I even got long press power button for flashlight to work consistently by removing battery optimization for gravitybox.

There is just an ever so small bug that I'd like to report. I don't think it has been reported yet. When changing the lockscreen bottom shortcuts, the new icons are showing when the always-on ambient display kicks in on the pixel 2 xl. Stock icons are hidden. Also, the popup Swipe from icon for... Isn't adjusted to fit the new shortcut. Still reads Swipe from icon for voice assist.

Other than that, very good job. A must have module!
[Xposed Framework Modules] GT500x:
Thanks for beta 2. Fixes lockscreen tweaks on OP5/OOS 5.0.2.
[Xposed Framework Modules] SourPower:
Amazing!!
[Xposed Framework Modules] C3C076:
Make sure you have active screen disabled in GravityBox ultimate notification control.
[Xposed Framework Modules] :
Yeah I already checked :(

I think I may have posted multiple times but my replies don't appear... weird
[Xposed Framework Modules] :
Yes I already checked, this setting sadly doesn't fix the problem :(
[Xposed Framework Modules] :
Tried Beta 1 on Samsung Oreo but i still get black screen after boot ?

Should i try beta 2 ?
[Xposed Framework Modules] Sytis:
Removing GravityBox from the "Doze list" fixed the flashlight issue for me as well, thanks :good:
[Xposed Framework Modules] firefds:
What device?

Both beta 1 and 2 work on my G950F
[Xposed Framework Modules] :
S8 with Minotaurus ROm... rooted with SuperSU.. latest xposed installer and framework is working.. also Xposed edge and some modules are working.. but if i enable Gravitybox..after boot i see only Black screen and i have to reboot with buttons and remove Gravitybox in Recovery..then devide will boot properly... how to find where can be problem ?

Can you write me your xposed installer and framework version... or you are using Magisk ?
[Xposed Framework Modules] DSA:
Minotaurus Rom is touchwiz
[Xposed Framework Modules] :
saw something else on S8 except Lineage OS ? ( which is not suitable for everyday use)
[Xposed Framework Modules] firefds:
I really dont know.

Im on latest beta with S8. No special rom. Stock beta.

Rooted with supersu and normal xposed. No magisk.

Can you try with just GB without any other module?

Also try with stock beta if you can
[Xposed Framework Modules] DSA:
Nope.

Gravitybox is for aosp roms, not touchwiz - thats all im stating (Its all in the first post)
[Xposed Framework Modules] firefds:
That hasn't been the case since Nougat. Some Touchwiz and OOP compability have been added.

I'm using GB on my Galaxy S8 for a few month now, both Nougat and Oreo
[Xposed Framework Modules] :
Can confirm... on Nougat :D now i have to figure out what is causing my problems on Oreo :o
[Xposed Framework Modules] Scarface1991:
Sorry for off topic but what font is this and where did you get it?
[Xposed Framework Modules] truelies1:
The mobile signal icon can't show signal strength after change color
[Xposed Framework Modules] MultiCulti:
did you get it work? have the same issue at the moment on OB3 5T
[Xposed Framework Modules] themachinist:
Everything running good on OnePlus 3 OOS OB31 except for the double tap action for home button under the navigation keys action which doesn't seem to work regardless what's assigned to it.
[Xposed Framework Modules] issasaurus:
Did you try in OOS settings to "hide the navigation bar"