yashsingh1/xdaforums huggingface dataset:
[Windows Mobile Development and Hacking General] itsallwright:
Fuze

A friend of mine with a Fuze let me check it out and I determined why it does not work.

The dialer on the Fuze has Mute/Unmute buttons on the screen, but the buttons do not have text (I suspect it uses seperate Mute/Unmute images instead). That being said, MobileMute determines the Mute State of a call based on the text value of the Mute/Unmute buttons. Therefore, it does not know what command to send.

I am trying to figure out a way to work around this, but in the meantime, I am sorry to say the Fuze is unsupported.

Just as a fyi... the Mute/Unmute button IDs for the Fuze are the same as the Kaiser (21408/21409)

I'll keep you posted on my progress with supporting this device.

-Jay
[Windows Mobile Development and Hacking General] jhw549:
Trying to use this app on my Mogul/Titan without success. I set it up on the button that would normally be conn mgr, went into cfg and set it to \windows\connmgr.exe

When I go to use the button I get a wait icon, the program launches and hides (still visible in Task Mgr). Opening manually works equally well (not at all).

The tools in the 2nd post don't work ("Class not registered" error).

While in a call the application launches (with a massive delay I might add) then performs its functino properly and mutes the call, no delays after initial launch.

There is no error log in the program's folder.

Help?
[Windows Mobile Development and Hacking General] itsallwright:
The initial start of MobileMute does have a delay. That is the reason I created v2 that will stay running. If MobileMute shows in task manager after you run it, then it found the hardware button you have it assigned to and is listening for future presses of that button. Since it does Mute/Unmute the calls, the program is functioning as designed.

As for running "\windows\connmgr.exe". I also cannot run that program (even manually). I don't think it is an app to be used that way. Are you sure you don't actually want to run "\windows\CommManager.exe"?

-Jay
[Windows Mobile Development and Hacking General] jhw549:
Heh.... umm... oops >.<

That's rather embarassing lol... You're completely right, I picked the wrong exe. It works 100% perfectly now.

I just wish it would hide completely and not show up in my tasks list... I have a tendancy to hit that kill all button rather than pick them out one by one.
[Windows Mobile Development and Hacking General] nir36:
thanks. this is a good idea... i'll be using it.
[Windows Mobile Development and Hacking General] itsallwright:
v2.1 with Fuze support

Well, it turns out that the Fuze isn't the only device with that dialer. I recently found a ROM (Phoenix v2) that has touch flo and a similar dialer to the Fuze. I put that ROM on my Kaiser to reproduce this issue on my own.

After quite a bit of research and learning, I found a way to detect the Mute state of a call via TAPI. The Mute/Unmute button text is no longer needed.

I have no way to test with an actual Fuze, but I am pretty confident it will work now. I have added the new version to the original post.

-Jay
[Windows Mobile Development and Hacking General] jpn621:
I've got v2.1 loaded. Detection on Fuze works, the registry shows mute/unmute id's 21408/21409. I'm using the short_PTT.lnk method. When I press PTT, I can see the titlebar flash 'MoblieMute' text.... but the mic does not mute.
[Windows Mobile Development and Hacking General] itsallwright:
When you are not in a call, does it open the configured program (BubbleBreaker by default). Also, if you look in task manager, is MobileMute listed?

-Jay
[Windows Mobile Development and Hacking General] jpn621:
Yes on both counts, although I quickly disabled the configured program. MobileMute remains in my task manager unless I manually kill it.
[Windows Mobile Development and Hacking General] itsallwright:
OK, when you are in a call, does it appear to do nothing? Or does it still open the configured program?

This will tell us whether or not it knows you are in a call. If it does nothing, then it probably detected the call and is sending the wrong command to mute it (which is most likely a button ID issue). What device and ROM are you using?

-Jay
[Windows Mobile Development and Hacking General] jpn621:
During a call, the PTT key flashes the MobileMute title to the right of my Start button; it does not play sounds (I've set PTT_chirp) and it does not show BubbleBreaker (configured and enabled). Mute key is configured as 21408, unmute as 21409. I used the configuration program to set sounds and examine key codes, then verified the settings in the registry.

Repeating the test -

After verifying settings, I soft-reset the device. Then called my desk phone to test it (with headset to observe whether mute succeeded). The first press did nothing other than flash the title bar. A second press had the same result. The third press shut the mic off. Unmute using the button failed (6 or 7 attempts). I left a 5 sec span between keypress tests.

I tested again, without the soft reset. The button was not able to mute my mic. I noticed that when the title flashed, so did the keyboard icon (centered between the lower softkeys). Flash lasts roughly .5 sec.

Device: ATT Fuze (HTC-P4600)

ROM: 1.95.502.5 WWE

ROM Date: 10/25/08
[Windows Mobile Development and Hacking General] itsallwright:
This is interesting, the program usually works or it doesn't. This half working sometimes scenario your having is troublesome.

Just as a test, kill the program from task manager and try to unmap the program from any hardware button and run it manually (I know this isn't the desired end result, but could provide useful info). When not in a call, it should open BubbleBreaker and then exit (leaving BubbleBreaker open). When in a call, it should toggle the mute function and exit. Let me know these results.

Is your ROM, the default ROM that came from ATT? Have you completely disabled the ATT PTT function by removing the PTT registry keys?

-Jay
[Windows Mobile Development and Hacking General] jpn621:
It is the default ROM. I disabled the PTT registry keys and have had the PTT button mapped to other functions. Recently conf calls have raised my need to gracefully mute the mic, and I've found that the lack of a dedicated MUTE button is a HUGE oversight by HTC and ATT. I will test more on Saturday morning and report my result. If you have a version that writes to a logfile, I'd be willing to run it to help the debug effort.
[Windows Mobile Development and Hacking General] jpn621:
After removing keymaps and soft-reboot, it behaves as you described. Muting worked during a call when I ran it from file explorer during a call.

I re-mapped PTT to a lnk to the exe, it launched MobileMute_v2.exe, but the exe did not exit and muting did not work. Very odd.
[Windows Mobile Development and Hacking General] itsallwright:
Did you disable the PTT function by deleting the entire PTT registry key from HKEY_LOCAL_MACHINE\Services?

-Jay
[Windows Mobile Development and Hacking General] jpn621:
Yes.

- deleted HKLM\Services\PTT

- renamed \Windows\short_PTT.lnk

- renamed \Windows\PTT

- created empty dir \Windows\PTT set to ReadOnly/System

- in Buttons I set it to <None>

- HKLM\Software\Microsoft\Shell\Keys\40C7 set Default and ResetCmd values to empty strings

When disabled,the PTT did absolutely nothing.
[Windows Mobile Development and Hacking General] itsallwright:
Nicely done, sorry I doubted you. The symptoms just seem to point at PTT since it works when ran manually. I created a new build that logs (a lot), so we can get some more info on what's going on under the hood.

Create a new DWORD registry value named LogLevel under HKLM\Software\itsallwright\MobileMute\Config. Give it a value of 5.

Then replace the 2 files in Program Files\itsallwright\MobileMute with the ones in the attched zip file.

Just as a heads up, with the excessive logging, the program will take 15-30 seconds each time it is launched. So, when you run it, make sure to give it plently time to finish. The log will be in the program directory, post the results here and I will take a look.

Note: The log may contain the name and number of the connected call, so replace those values with something else for your privacy.

-Jay
[Windows Mobile Development and Hacking General] jpn621:
PTT Configuration:

- PTT Services entries do not exist

- HKLM\Software\Microsoft\Shell\Keys\40C7\Default="\Program Files\itsallwright\MobileMute\MobileMute_v2.exe"

- HKLM\Software\Microsoft\Shell\Keys\40C7\ResetCmd="\Program Files\itsallwright\MobileMute\MobileMute_v2.exe"

- Short_PTT.lnk is a shortcut to MobileMute_v2.exe

Scenario 1: not in a call

- BubbleBreaker launched

- Manually closed BubbleBreaker

- TaskManager showed that MobileMute remained resident

- Manually closed MobileMute via TaskManager

(forgot to save log before scenario 2)

Scenario 2: in a call

- MobileMute title flashed in title bar

- Mic did not mute

- TaskManager showed that MobileMute remained resident

- Manually closed MobileMute via TaskManager

copied text file from phone after connecting sync cable.

Should MobileMute remain resident, or exit after a button press?

Scenario 3: In a call, (disabled the SpB Phone Suite today-screen plugin)

- MobileMute title flashed

- Mic MUTED !!!!!!!!

- TaskManager showed that MobileMute remained resident

- Manually closed MobileMute via TaskManager
[Windows Mobile Development and Hacking General] itsallwright:
I see this in DebugLog2.txt

The program did not see the button press event. All the log indicates is that the program received focus (which you see as a flash on the title bar).

It should remain resident, but only if it determines what hardware button it is mapped to. In your case, it figured it out according to both logs you provided.

This log looks normal, with the exception that it starts by detecting the call is already muted (I assume you manually muted before pressing the button and MobileMute unmuted the call).

So, are you saying that it works properly after you disabled SpB Phone Suite today-screen plugin?

-Jay
[Windows Mobile Development and Hacking General] jpn621:
My statement regarding SpB Phone Suite was premature. It does not matter whether SpB Phone Suite is enabled, behavior is the same:

When in a call:

- First press gains focus, mutes mic, remains resident

- second press gains focus briefly, remains resident, mic remains muted.

- additional presses duplicate the second press

While in a call, I pressed my home key and used task manager to kill MobileMute

- PTT press gains focus, unmutes call, remains resident

- second press gains focus briefly, remains resident, mic remains enabled

- additional presses duplicate the second press

In all cases, the log shows a tone getting played but there is no sound.
[Windows Mobile Development and Hacking General] itsallwright:
One thing that is bothering me in the logs is that you have MobileMute configured on 2 buttons (C6 & C7).

Hardware button '40C7' found
Program assigned to button is \Program Files\itsallwright\MobileMute\MobileMute_v2.exe
Hardware button '40C6' found
Program assigned to button is \Windows\PTT\MobileMute_v2.lnk
MobileMute appears to be mapped to hardware button with ID 199

It is only configured to listen to 1 button press (I never thought anyone would want it mapped to multiple buttons). According to the logs, it picked C7 to listen to. On my Tilt/Kaiser, C7 is the PTT press and hold button and C6 is the PTT press once button.

Try to remove the extra mapping or press and hold PTT to see if that works in this case.

-Jay
[Windows Mobile Development and Hacking General] jpn621:
Removed C7 and it works as-designed. I have no idea why I configured it twice. It's a bit slow (non-debug) but it works.

Thanks much, greatly appreciated.
[Windows Mobile Development and Hacking General] itsallwright:
Great! I am glad it is working.

The only difference in the debug version is the addition of logging. You can set the LogLevel value to 0 to disable it.

I have noticed a slight delay too, but only on the first press. Subsequent presses seem to be as fast as if I pressed the button on the screen.

-Jay
[Redmi Note 11 (spes/spesn)] Love XDA Developers:
Hi

Last night I purchased this Beautiful phone with amazing blue color

I want to have these in my phone :

Call Blocker : https://apkpure.com/tr/root-call-blocker/fahrbot.apps.rootcallblocker.beta

Call Recorder : https://play.google.com/store/apps/details?id=com.nll.acr&hl=en&gl=US

Or something similar to theme ,

Now there is no app works on this phone and have no Idea how fix that

Please help me in this case

Thanks all of you and XDA forums
[Redmi Note 11 (spes/spesn)] Cisuwek:
Install xiaomi.eu rom for call recording. You can find few apps in play store to block calls. Call recording doesn't work good as I know on miui os, even on rooted devices. If you really want these apps, flash custom rom based clean android
[Redmi Note 11 (spes/spesn)] Love XDA Developers:
Thanks for reply

Would you please tell me where I can find stable and secure custom rom ?
[Redmi Note 11 (spes/spesn)] MHaseebpk:
Just unlock bootloader

Flash Indonesian rom with mi flash tool.

You will get mi dialer with call recording instead of google dialer.
[Redmi Note 11 (spes/spesn)] Love XDA Developers:
Hi

Thanks for reply

Where can I found that Indonesian rom ? is it official or custom rom?
[Redmi Note 11 (spes/spesn)] MHaseebpk:
Indonesian roms are official.

Download fastboot rom from here.

XM Firmware Updater

The ultimate script that provides firmware packages for Xiaomi devices.

xiaomifirmwareupdater.com
[Android General] lucfortunato:
Mainline it to the main Linux repo

Use mobian END or

If you want android Get the upgraded LOS port to your device and port it to AOSP using the android mainline kernel (now with the last Linux you can use any android version you want), with mainline drivers like freedreno etc... (You can use drm-hwcomposer) END or

If you want your stock rom like OxygenOS extract the GSI of the newer model of your phone, decompile apks, edit files etc... To match your hardware and reenable lost features or disable feature with hardware requirements. To make sure everything is working fork LOS and call it, merge it with the prebuilt GSI and modify it to work lawless with stuff like enforced selinux.

I'm doing this with my OnePlus 6T, my hope is to have the last OxygenOS that work flawlessly on mainline kernel and upgrade it until the hardware is not good enough, then I'll just use mobian or buy a new phone.
[Android General] GalaxyA325G:
Given that Android is comprised of multiple disjoint components, about two dozen of which are encompassed in Project Mainline/Treble/Google Play system updates/etc., now mostly simply referred to as "Google System updates"...

I have asked this key pertinent question of everyone I can ever since project Mainline/Treble had been announced way back for Android 10 and have yet to get _any_ answer whatsoever that has any basis in published facts from Google.

The question...

For the two dozen core modules covered in project Mainline, for how long does Google update them over Google Play Update services on Android 10+ phones?

The answer...

Is it finite?

Is it forever?

Is it arbitrarily finite?

For how long are the two dozen core modules updated over Google Play for any given Android X+ device?
[Android General] lucfortunato:
The "project mainline" is misleading. Here when I tak about mainlining I'm talking about running android with a generic Linux kernel instead of the fork. So you can basically update the kernel to infinity and so port every android version you like.
[Android General] lucfortunato:
So basically now I'm porting the OnePlus 6t to aosp using android-mainline as kernel with drm-hwcomposer. So anything forked or something.
[OnePlus 10 Pro] Compassvale542:
I am an app developer. From our Firebase Crashlytics logs, some issue is happening on NE2215 but I didn't see NE2210.

I can only find NE2210 in my country.

What is the difference between NE2210 and NE2215?

Seems NE2210 is China version and NE2215 is US or global version.

Is it only the ROM difference? Can I flash a NE2210 with a NE2215 ROM?

Thanks
[OnePlus 10 Pro] g96818:
NE2210 is a POS model that does not work well outside of china
[OnePlus 10 Pro] Compassvale542:
Thanks.

Would it be possible to change it to NE2215 by flashing the global ROM?
[OnePlus 10 Pro] maddler:
Yes, there are a few threads about that in the forum, just have a look.
[OnePlus 10 Pro] g96818:
Won't matter if you can't unlock the LTE bands for use outside of China.
[OnePlus 10 Pro] Oneplusit:
As there are a lot threads about this, are able post one that may work. So far I think 8pro was better, I only got it when I was in China early year this at launch. But now home I miss the hey Google
[Android Q&A, Help & Troubleshooting] Raja Mastory:
Hey Guy's let's help me how I can root my Samsung Galaxy A03s and how i can find the image of twrp in my phone.
[Android Q&A, Help & Troubleshooting] Airic12345:
Download Platform ADB & Fastboot.

Download The Latest Odin tool.

Download 7-Zip

Download "Bifrost" on your phone.

Download The Stock ROM of your SM-A037F using the Bifrost (make sure to know your device's Model & Region-Specific CSC).

Backup User Data (as your Phone will have to be reset... Multiple times)

... Now...

Step1: Decrypt the Stock ROM you downloaded with Bifrost in the Decrypt section of Bifrost.

Step2 : Move the firmware to your PC, keep two copies.

(p.s.: leave only the "AP" file on your phone.)

One copy will be the stock firmware backup incase of any mishaps.

The second copy of the firmware; Change the file extensions of all the extracted files to ".tar" with 7-Zip.

Step3 : On your phone, Using The latest Magisk APK, patch the entire "AP" file (should be about 5GB give it some time to work.). It will now be renamed by Magisk to something else.

Step4 : Move the patched "AP" to your PC. Then lauch Odin and input all the files in the following order;

BL. - Stock BL.

AP. - MAGISK-Patched AP.

CP. - Stock CP.

CSC. - Stock CSC. (DO NOT USE "HOME CSC").

Go to "Option" tab and Untick "Auto Reboot".

Step5 : Go to "Developer Settings" on your phone and enable OEM Unlocking.

Step6 : Plug-In your phone to your PC

Step7 : Power off;

Long-press: Volume Up + Volume Down Simultaneously.

Step8 : Wait till you see a prompt to disable Device Bootloader by Holding Volume Up; Proceed with holding on Volume Up to unlock the device Bootloader.

Step9 : It will Rest your device's, so quickly Setup your phone, turn on your data connection or WiFi.

Head to the "Developer Settings" to confirm the status of your bootloader.

Repeat Step6 & Step7.

Step10 : Tap once on Volume Up to enter Download Mode and Click Start On the Odin tool on your PC to flash the Rooted Firmware on your Galaxy A037F.

Step11 : Wait for it to finish its Download and then hold Volume down and power button.

Step12 : After Booting up, Power Off and Long Press Volume Up and Power Button to enter Recovery Mode.

Step13 : Perform a Factory Reset. And Reboot

Step14 : Install Latest Magisk APK and

Done!
[Android Q&A, Help & Troubleshooting] Galaxyjunky:
I need help too

on a Galaxy a03s sm-a037u the system is as follows.

Android 11 / R / API 30

Baseband Version: A037USQS2AVD3

Linux Kernel Version: 4.19.127-23960189

Http User Agent: Dalvik/2.1.0 (Linux; U; Android 11; SM-A037U Build/RP1A.200720.012) hardware model MT6765V/CB

Needing to unlock bootloader, Enabled developer options and no oem unlock toggle,ran adb commands got,

( ro.oem_unlock_supported "1")

( sys.oem_unlock_ allowed "0")

( ro.boot.flash.locked "1")

( ro.boot.vbmeta.device_state "locked")

( ro.boot.verifiedbootstate "green")

( ro.boot.verifymode "enforcing")

Tried running Flashboot command

Flashboot unlock oem,returned error code remote unknown command. Dies anyone know who to unlock bootloader and root this device?
[Android Q&A, Help & Troubleshooting] Zillion:
This is a33 forum device not a03s.
[Android Q&A, Help & Troubleshooting] Galaxyjunky:
Yea that's obvious was just hoping some one could help
[Android Q&A, Help & Troubleshooting] Goosemidtn:
Actually its the a03 thread. Read the title up top D!ck
[Android Q&A, Help & Troubleshooting] Zillion:
Some moderator moved it to "Android Q&A, Help & Troubleshooting", try to be nice with people.
[Mogul, XV6800 ROM Development] AndyMan386:
Are there any tweaks that can be made to get better signal/range on wifi, or any external accessorie that can boost the signal?

Thanks!
[Mogul, XV6800 ROM Development] ve7gvs:
you could get a repeater, or load dd-wrt onto a router and use it as a repeater.
[Mogul, XV6800 ROM Development] Scott:
Not that I know of.
[Mogul, XV6800 ROM Development] worwig:
I added one of these to my router. I was right on the edge of a good signal on my porch. This improved it enough to make it reliable.

http://www.freeantennas.com/projects/template2/index.html
[Mogul, XV6800 ROM Development] dcd1182:
or continue using it as a gateway and increase the output power. you could also use channels higher than 12, they should be enabled in my ROM as well. (FCC has a problem with that)
[Mogul, XV6800 ROM Development] AndyMan386:
reason I ask is I sub teach at a school that has a few different wireless signals in the building. They wont give computer accounts to subs, but the wireless isnt password protected. So depending where I am in the building, sometimes I can get a signal, sometimes I cant. So I was hoping if there was anything to boost the searching signal on my end, I might be able to connect.. probably what I need is a laptop! haha