yashsingh1/xdaforums huggingface dataset:
[Android Apps and Games] alecot18:
VolumeP allows users to disable the default popup to change volume media on the top of the screen in favor of a side popup.

VolumeP uses the minimal possible Accessibility Service configuration to listen to volume keys to launch the side popup and does not observe any user action or text that they type; however this privilege is mandatory for all accessibility services, but VolumeP disregards any events the system does send, except for those mentioned that anyway are not recorded.

Also VolumeP uses the performGlobalAction() Accessibility service feature to perform default usage of hardware key like menu, home and back, to restore the user experience otherwise compromised from the same Accessibility service.

Download it for free:

https://play.google.com/store/apps/details?id=com.alecot.volumep

XDA:DevDB Information

VolumeP, App for all devices (see above for details)

Contributors

alecot18

Version Information

Status: Testing

Created 2018-03-13

Last Updated 2018-03-13
[Android Apps and Games] rignfool:
Not sure if it's fixable...

Volume changes require individual presses... Meaning you can't hold the button down to have to move
[Android Apps and Games] bejunk:
Great Idea! But please add a dark theme, so it fits the rest of my system :) (Android P switches it too, if using dark wallpaper) Also like mentioned above, when holding the volume button continuesly, it should adjust the volume continuesly... Last thing, if i enable dnd mode via your Volume overlay, it dont gives me any option no more in quicksettings (like until alarm, for few hours, etc.)

But its a great Idea and thank you for the app! :D

✌
[Android Apps and Games] rignfool:
Also...

I cannot change the volume of a phone call while in call... It is stuck on media volume only...

Might I suggest... Since you're running an accessibility service already... Allowing for per app ignoring... Or changing the default stream based on foregeound app...
[Android Apps and Games] Agi Maulana:
Verry nice app.

when i have given all permissions volume pop up work properly but recent app button doesn't work, i revoked all permission and recent button want to work. Please fix this bug. Nice work.

Samsung J320G

Resurrection Remix 5.8.5 (Android 7.1.2)
[Android Apps and Games] andymedina2588:
Link for github,.volumep pro please!
[Android Apps and Games] charackthe:
Volume keys control media volume but there should be a slider to set it to control ringtone volume. I don't know if its possible. My keys supposed to control ringtone volume but instead they control media.

Also the panel updates a little late while pressing the button once. I don't know if its something that could be worked around.
[Xiaomi Mi A1 Questions & Answers] hemanth_gunasekaran:
Hi all,

I've installed GCam 5.1.018.177470874 recently. Front cam works perfectly at portrait mode. It gives that blur effect.

But the rear camera just zooms in takes the picture. There is no depth and blur effect. Is it normal on all GCam or should I be installing a different version? Please suggest me.
[Xiaomi Mi A1 Questions & Answers] stup0r:
Only blurs for human subjects.
[Xiaomi Mi A1 Questions & Answers] hemanth_gunasekaran:
Thanks a lot.
[Honor 9  Questions & Answers] miffeltoffel:
EDIT: My solution was to have an exFAT formatted SD card with update.app, I had previously only tried on an ext4 formatted card.

Hi everyone!

I've been looking for days for a way to get my Honor 9 working again to no avail.

It started with me trying to install a custom ROM on my EMUI 5.1 Honor9, but when the touch buttons didn't work I decided to go back to stock. This is where the problems started.

FRP and bootloader was unlocked before doing this.

After many different firmware tries I managed to get into stock rom (B130), and apparently it locked FRP again, but since the touch buttons still didn't work I decided to rebrand with B120. Bad idea.

Now my phone has FRP locked, so I can't flash images from fastboot anymore (command not allowed), and no working OS.

I do however have TWRP installed as recovery2/e-recovery, so I can still adb push images and install them via TWRP.

I've looked through every thread on this forum and tried every possible solution I could find (extracting images from update.app, copying update.app to /dload on external sd, different firmware versions etc)

If there is there anyone here that is more experienced than me that can give me any pointers in the right direction, I'd be incredibly grateful!
[Honor 9  Questions & Answers] oslo83:
As far i know there only 3 service repair firmwares publicly available which works the dload way. There nougat and are meant to use from nougat.
[Honor 9  Questions & Answers] miffeltoffel:
Alright, so they won't work for me no matter how hard I try?

What alternatives are left to me?
[Honor 9  Questions & Answers] oslo83:
What's your region and version firmware actually ?

You stated you rebranded ?

What region region service repair firmware did you used ?
[Honor 9  Questions & Answers] miffeltoffel:
Region is EU, I'm not really sure what my original firmware is, but i suspect around B130? I know, I'm an idiot for not checking before I wiped it..

I tried at least, to install the B120 in order to get the capacitive buttons to work, but I'm pretty sure I didn't succeed.

I've been using EU firmware to try and get the phone up and runnin. A few different versions.
[Honor 9  Questions & Answers] angelobiz:
have you tried to flash again B130 whit 3 fingers mode?

mmmhhh but maybe you have need stock recevery....
[Honor 9  Questions & Answers] miffeltoffel:
With 3-finger mode you mean stock recovery? (Not twrp or stock eRecovery)

How would I flash this using stock recovery, via update.app method?

When flashing stock recovery to recovery partition it boots straight to twrp (flashed to recovery2) regardless of what buttons I hold. :/

If i flash twrp to recovery and stock eRecovery to recovery2 partition and restart holding vol+ and pwr, I get a screen similar to fastboot screen with "error 2 - could not load"

I'm afraid that if i flash stock both recovery and eRecovery, I have no way of flashing images or restore twrp due to FRP being locked...

Thank you everyone for taking the time to respond, really appreciate it!
[Honor 9  Questions & Answers] angelobiz:
not undestrand...

now you have TWRP installed or Stock recovery? phone turn on in system or have a loop? what it is the problem? only FRP blocked?

how you can falsh twrp and stock e-recovery if you have frp blocked?

what is happen when you turn on phone holding Volume + and Power Button WHITOUT ANY USB CABLE CONNECTED?

this is three fingers way:

1) download "stock service B130" from:

https://xdaforums.com/hon...stock-t3696892

2) copy UPDATE.APP and update_STF-L09_hw_eu.app to external SDCARD into /dload folder

turn on the phone holding Volume + and volume - and power ( three fingers way)

if all is good, phone restart in stock recovery and update firmware....

you will have again bootloader and frp blocked after new firmware will be flashed

if you have a twrp installed you can try this method.... but i dont know if it work whit frp locked:

1) download "stock service B130" from:

https://xdaforums.com/hon...stock-t3696892

2) download those 2 file from

https://mega.nz/#F!Y59nFYbJ!fb1f4UpEdgABZ4NhOfu1JQ

3) put all files in HWOTA7 directory on external SD

4)In TWRP find the folder HWOTA7 on the phone SD and from it flash the file "hwota7_update.zip"

he phone will reboot itself into the stock recovery and it will install the firmware.

++++++ Important ! ! ! ++++++

After have installed the firmware, you need to boot into the recovery and make a full Wipe

if all ok, b130 firmware will be flashed.

let me know if you try
[Honor 9  Questions & Answers] miffeltoffel:
First of all, thanks a lot for trying to help me! :)

I will try this method. I downloaded the HWOTA script, however in the bash script contained in this file, it says:

#!/sbin/sh

dd if=/external_sd/HWOTA7/STF_RECOVERY_NoCheck.img of=/dev/block/mmcblk0p37

dd if=/external_sd/HWOTA7/STF_RECOVERY_NoCheck.img of=/dev/block/mmcblk0p34

echo --update_package=/sdcard/HWOTA7/update.zip > /cache/recovery/command

echo --update_package=/sdcard/HWOTA7/update_data_public.zip >> /cache/recovery/command

echo --update_package=/sdcard/HWOTA7/update_all_hw.zip >> /cache/recovery/command

reboot recovery

Which means that I should have 3 zip files present on the phone in /sdcard/ called update, update_data_public and update_all_hw.

These zip files do not exist in the B130 firmware you linked. What files should I use for this?
[Honor 9  Questions & Answers] miffeltoffel:
I tried running it anyway and got into recovery, however it says "Software install failed! The update package does not exist. Please download the package again."
[Honor 9  Questions & Answers] miffeltoffel:
Alright, that may have thoroughly f**d me. Now TWRP is replaced with stock eRecovery.

I suppose I can put files on the SD card by using my laptop, but then I'd need the correct files. Anyone? :)
[Honor 9  Questions & Answers] oslo83:
Now you should be able to flash with b130 service Repair files:

http://androidhost.ru/v5

Instructions inside, you will need an sdcard formated to extfat.
[Honor 9  Questions & Answers] miffeltoffel:
I've tried SO many times trying to get this update method to work, but always stuck at 5%, until now!

Seems like exFAT is the key! When formatting the SD card on my laptop with linux, it became formatted as ext4, which was fine to read and write to in twrp, but however stock recovery seems to demand an exFAT partition.

Today I went out and bought an USB SD card reader and formatted with exFAT on my windows machine and lo and behold the update was installed!

I don't know if I'm an idiot for missing this fact or if it is not iterated enough. This solved my issue though!

Thanks a lot, Oslo83 and Angelobiz
[Honor 9  Questions & Answers] angelobiz:
yes... you have right...i missed somethings:

update.zip same same

update_STF-L09_hw_eu.app have to rename in update_all_hw.zip

update_data_public.zip dont need for restore....

happy that you have solved.

which files have you used?
[Honor 9  Questions & Answers] miffeltoffel:
I used the stock B130 files in the thread that you posted, worked like a charm. As stated, the issue seems to have been that Linux cannot format in exFAT, and stock recovery can only read exFAT. :)
[G4] R3PUBL1K:
My friends phone (i sold him a year ago) is having this issue, even after hard-reset. So I am going to try update the radio rom and OS too.

Apparently I can now use HARD_SPL (see HERE) on this G4.

as the FTP is down is there any other download links i could use for the files i need.

any ROM and Radio

Thanks in advance
[Lenovo Zuk Z2 Pro Questions & Answers] suchit23:
Kindly help please
[Huawei P9 Questions & Answers] FabianGER:
Hello,

I want to root my Huawei P9.

Information about the handy:

EMUI 5.0.1

EVA-L09

B397

CPU: Kirin 955

Bootloader is unlocked.

I tested a lot of things but it still dont work.

I hope, I got help here.

For help to finish, I want to pay a little bit as a bonus :)
[Huawei P9 Questions & Answers] Sorinn88:
https://theunlockr.com/2016/12/06/root-huawei-p9-p9-plus/ have you tried this?
[Huawei P9 Questions & Answers] zgfg:
You have omitted important part, your cust, is it c432 or what. I.e. full name of your build as it shows in About Phone, like EVA-L09c432b397 or what.

Forget advices about rooting P9 Plus (?!), you can easily brick your phone

There is search on XDA, you can find excellent topics about rooting (this one is for SuperSU, there are others for Magisk)

https://xdaforums.com/p9/development/root-supersu-2-81-emui-5-t3612258

Read the guide at the beginning and posts from last e.g. month at the end (up to date with the latest builds like yours). There is search and you can search through the topic, to find details applicable for your build, apps you need the root for, etc

And post your further questions there - e.g. that topic has 570+ posts, probably tens of experienced hackers who are watching - to the other side topics like this one get opened 5-10 new every day, and chance that somebody who is knowledagbe will spot it and dare to answer (every day sinilar questions are repeted by new users, who will answer to each and every of them, every day) are negligable ;(

PS: The guide above covers only the last part, flashing the correct ZIP for rooting. Before that you need to unlock bootloader and install TWRP for EMUI 5.x - search on XDA to find the guides about
[Huawei P9 Questions & Answers] FabianGER:
Thank you, it still works now :)
[Huawei P10 Lite Questions & Answers] punkrockfan:
stock ROM, installed viper4android both ways:

standard apk for nougat from viper homepage

zip guitarhero modified through twrp

both ends in driver install loop at every startup

google says linux should be set to permissive (due to writing rights?) and then modify an audio effects file in vendor...dev...tree with root explorer

even after trying to change linux to permissive with selinux chnager app, the discontinued one, i never get that entry audio effects in vendor dev etc somewhat

so whenever i reboot the phone, restart viper4android it wants to install the driver, says success, re same thing.

never had these problems on custom but on stock ROM, how to solve the issue please on p10 lite?

thanks ;D
[Huawei P10 Lite Questions & Answers] Minecrafted:
Did you find a fix?
[Other SmartWatches] kapsubm:
Has anyone seen this behavior with a pedometer on a Feature watch? (self counting stepmeter - while the watch is laying on the desk).

Funny thing is, if i try the Firmware on my other mtk6261D "Y1" watch-

the pedometer just works as it should

(Display on "working" watch2 inversed due to LCD rather then IPS -.-).

"auto step:" https://www.youtube.com/watch?v=9Vgx-r5haLQ

"normal behavior:" https://www.youtube.com/watch?v=v699Hextg1c

(display inversed due to LCD rather then IPS display, but for the rest Firmware is working just normally)
[Verizon Motorola Droid Turbo General] droid_ulti:
lets face it, droid turbo community is dead , nexus 5 with SD 800 have android O !

while our much powerful OG droid stuck on MM or N, and i am not talking about 25$ , it's just xda is the place were you get stuff for free , that's just sad seeing a good device feed away.
[Verizon Motorola Droid Turbo General] ChazzMatt:
I'm sorry that you failed to include that in your purchase price . That's your fault.

If Bootloader unlock is that important to you you would've researched and known the cost.

Blame Verizon -- they are the ones that locked down the Bootloader on the droid turbo. The other Quarks have free Bootloader unlock, courtesy of Motorola. Sunshine devs gave Droid Turbo bootloader unlock, so they could join the party. Without them, Droid Turbo would still not have bootloader unlock -- like the Droid Turbo 2.

The XT1250 is identical to the Droid Turbo, with all the Verizon bands, and runs on Verizon just fine. The XT1225 has more LTE and HSPA bands than the Droid Turbo XT1254.

You didn't research before buying.

Quark will also get Oreo, so I don't understand your point there. All LOS-based Quark ROMs are compatible with all Quarks.

Maybe you don't don't about the OTHER Quark forum on XDA? All the dev work is over there. And it's also for the Droid Turbo.

Sent via open market LG US998 V30/V30+
[Verizon Motorola Droid Turbo General] droid_ulti:
lol man , you missing the point , i don't have issue with paying 25$ in fact my droid is boot-loader unlocked right now using sunshine , the point is community is dead we don't have a variety of roms like the same era phones such as htc m8 and smasung s5 and z2/z3 nexus 5/6 etc , even my 2012 lg l3 have more roms droid turbo, the unlocking boot-loaeder and sunshine was obstacles against all this wonderful hacking and moding things we could do.
[Verizon Motorola Droid Turbo General] ChazzMatt:
You missed my point. Droid Turbo XT1254 is only one Quark of three, all of which use the exact same LOS-based ROMs.

It would be like LG G3 was divided up into three different model names. The internal name was Quark, but the global consumer name for this device was Moto Maxx -- even for the U.S. model, but Verizon demanded an "exclusive", so theirs was named "Droid Turbo". But the XT1254 exactly the same phone as the XT1250 -- just has a locked down bootloader. It wasn't exclusive in any way. Other carriers in the U.S. sold the Moto Max XT1250, which has the same FCC ID as the the Droid Turbo XT1254.

Then the XT1225 Moto Maxx was renamed Moto Turbo for India, but it's the exact same FCC ID device as the XT1225 Moto Maxx.

Droid Turbo is the only one with locked down bootloader. The others are not. So, nothing is preventing development unless you INSIST on buying the only Quark with locked down bootloader, and didn't research before buying.

That's why all the development for Quarks, including the Droid Turbo is posted in the OTHER QUARK forum. Like TWRP, custom kernels, most of the ROMs.

Your whole premise is flawed. You think people HAVE to buy Droid Turbo or nothing. No, they can buy one of the other Quarks and have free bootloader unlock.

* With XT1225 they can have more LTE and HSPA bands.

* With XT1250 they can have all the Verizon CDMA and Verizon LTE bands.

The Droid Turbo XT1254 is the least desirable of all the Quarks... But if you buy it, be sure to factor in $25 for bootloader unlock. The others have free bootloader unlock.

Sent via open market LG US998 V30/V30+
[Verizon Motorola Droid Turbo General] droid_ulti:
people buy the Verizon droid turbo over the other Quarks because the price and availability , being said that i think most Quark users are using xt1254 plus it is compatible with CDMA and GSM that's why the user go for xt1254 which is the most desirable,

any the phone is three years old can't people around the globe who are using xt1254 get a free unlock !
[Verizon Motorola Droid Turbo General] ChazzMatt:
Again, you have it wrong.

Why do you think the Droid Turbo is cheaper? Because you have to factor in extra $25 into the purchase price for bootloader unlock. The REAL price is $25 MORE than you paid. People who buy it have to do that -- if bootloader unlocked and root is important to them. Thus, Droid Turbo SEEMS cheaper...

If there was "free bootloader unlock", Droid Turbos would then become more expensive as the price would rise. Just like 2015 Kinzie -- Verizon Droid Turbo 2 are much cheaper because they don't have bootloader unlock, but sibling Moto X Force is more expensive because it's BETTER -- it has free bootloader unlock from Motorola.

Why do you think the other Quarks (XT1250/XT1225) are more expensive? Because they are better. Free bootloader unlock from Motorola.

Outside the U.S. CDMA is mostly useless. Most of the world detests CDMA and doesn't use it. The XT1225 has more LTE and HSPA bands than the XT1254/XT1250 and doesn't have useless CDMA.. It has 64GB storage and FREE bootloader unlock, whereas most XT1254 have 32GB storage (yes, some have 64GB but not many) and you have to pay $25 for bootloader unlock and it's sometimes not easy to do. So XT1225 is worth more money.

____

Sunshine team publicly released the vulnerability they use. Anyone that wants can code free bootloader unlock. Nothing is stopping anyone from coding and releasing it.

But you seem to be blaming the devs who are offering a solution. If there was no Sunshine, you would HAVE to buy XT1250 or XT1225 -- or another phone altogether.

The Verizon Droid Turbo 2 (Kinzie) never got bootloader unlock, so people HAVE to buy the free bootloader unlock Moto X Force (Kinzie) if they want root and custom ROMs. Tons of people would LOVE the opportunity to pay $25 to unlock their Droid Turbo 2! ;)

Sent via open market LG US998 V30/V30+
[Verizon Motorola Droid Turbo General] ChazzMatt:
Here's news about Oreo ROMs for Quark, and the current list of Nougat ROMs. Since you're new, you may have missed this.

https://xdaforums.com/showpost.php?p=75679114&postcount=94
[Verizon Motorola Droid Turbo General] lem22:
Oreo needs at least Kernel 4.4. To prevent false hopes, it still should be called Resurrection Remix.

It's a bit like installing Vista themes on Windows XP back in the days... :)
[Verizon Motorola Droid Turbo General] ChazzMatt:
SUMMARY: you're never going to have a kernel for a device which was not first released by the OEM, in this case Motorola.

________

Call the kernel Resurrection Remix? It seems you are confusing kernels with specific ROM names? Maybe you are making a joke, I'm not sure.

Once we have a compatible kernel in the LOS tree to that will run on Oreo, any ROM maintainer can package and release a ROM. [MENTION=5747496]bhb27[/MENTION], our kernel developer also maintains Resurrection Remix ROM. But there's also LOS, crDroid, etc. All the current ROMs will probably follow to Oreo. We may even attract some new ones.

An Oreo compatible kernel is the FOUNDATION for any Oreo ROM. You need that first. But you can't just create a kernel out of thin air. You need to adapt the kernel sources the OEM (in this case Motorola) has released publicly.

_________

Here's the problem with the kernel -- and I'm not an expert on kernels, but I'll explain it the best I can.

When our former official CM dev [MENTION=2228410]Skrilax_CZ[/MENTION] started this work back in early 2015, he had to take Motorola KitKat kernel sources and adapt it to work with Lollipop CM 12.0 (March 2015) and then CM12.1 (April 2015). We had Lollipop CM custom ROM BEFORE Motorola gave us Lollipop. :rolleyes:

Motorola did release official Lollipop, but didn't release Lollipop kernel sources until like July 2015. At that point our CM dev [MENTION=2228410]Skrilax_CZ[/MENTION] then updated the CM kernel to "Lollipop" kernel. Until then for many months, we had Lollipop ROMs running on Kitkat kernel.

WHY? Because you can't just create a kernel that will run on a phone from scratch. You have to adapt the kernel the OEM has made for it.

Then, same thing happened with Marshmallow. For awhile, we had Marshmallow ROMs running on "Lollipop" kernel. Then Motorola released Marshmallow kernel sources and now we have "Marshmallow" kernel. During this time frame (Marshmallow to Nougat) was when [MENTION=5747496]bhb27[/MENTION] took over kernel coding duties.

Well, guess what? Marshmallow was the last firmware Motorola ever released for Quark.

Yet, we have Nougat ROMs -- running on Marshmallow kernel. (Thanks to [MENTION=5747496]bhb27[/MENTION])

If we ever get Oreo -- it will be Oreo running on Marshmallow kernel. (Thanks to [MENTION=5747496]bhb27[/MENTION]).

So, no I'd pretty much bet you will never get Linux Kernel 4.4 running on any Quark. If you want that, you would need official OEM kernel coding -- with stock official Oreo ROM -- which is only available with currently supported hardware. XDA devs with skill give life to older devices like these 2014 phones, but there's limits to what they can do.

I have Linux kernel 4.4.63 on my LG V30 US998, but it's a new phone. LG codes that kernel. Three years from now if I still have this phone, any ROMs in running will have to be using kernel sources from LG.

Just like any Quark will need kernel sources from Motorola -- and the last available is Marshmallow kernel, circa 2016.
[Verizon Motorola Droid Turbo General] TheSt33v:
Not true. See link for LOS 15.1 for Nexus 4, Linux kernel 3.4: https://xdaforums.com/nexus-4/development/rom-lineageos-15-1-t3758779