I will be updating my website over the next few days, so hang in there with me as there will be some format issues and picture issues until complete.
For many wearing hearing aids is not an option, this is the case for my wife. The problem is she hates them. The primary reason she hates them is because she can create a custom setting on the Phonak App and then it defaults back to Autosense or the prescription setting. If you Google this issue, you will find that many are having the same problem and if you go to Phonak’s forums you will discover they appear to be clueless. After looking into my wife’s remote app, I not only discovered the fix, but the cause of the problem. Continue reading to discover the problem and the solution. However, do not drop to the solution for the quick fix, without understanding the why; you may not like the solution.
First the PROBLEM:
As a person needing hearing aids, like my wife yours may have cost over $6,000.00. At first you are excited, you can create custom settings on the Phonak app for just about any situation and by wearing them all the time, your brain will adjust to the background noise and in time you will adjust. But then you quickly discover that once you have created a custom setting on the Phonak remote app, it reverts back to Autosense and sometimes this is so unexpected that it causes hearing pain. The Phonak Company has identified the issue. Every time ANY sound is created on the phone, this includes keyboard sounds, ANY notification from any app, any audio sound made, the remote app defaults back to Autosense. On the Phonak website the suggested “fix” is to turn off ALL notifications, this even includes text, social media, and it would even include severe weather related notifications. This is simply NOT an option. Phonak’s expectation is the every sound and audio made on the phone is to be played through the hearing aids. However if you take them out at night and it is dangerous weather you need to hear notifications. The expectation is that you will go through the advanced settings on your phone EVERY time to turn notification on and off. This is not practical. The solution provided on Phonak’s website is not realistic.
So what is happening that is causing the Phonak Remote App to default to Autosense every time any audio sound is made on the phone? I will explain using Android, but the same applies to iPhone. In Android if you go to SETTINGS>CONNECTIONS>BLUETOOTH you will see your Phonak connection like in the image displayed.
Tap the TOP setting. The next image shows what you should see. PHONE and AUDIO, one or both sliders may be in the ON position. This is where the POF (Point of Failure) is. The point of the AUDIO slider is to allow ALL audio sounds made by the phone to be played through the hearing aids. This includes all notifications, all of them. People use thousands of different sounds, voices and beeps as notifications. Such a large scale of audio sounds is the POF. The hearing aids are not able to sort out such a large ongoing different amount of audio sounds, so the solution that hearing aids will do is to default to the prescription setting or Autosense. This is something that Phonak can’t fix because Android and iPhone will not allow any developer to access the internal settings of the system notifications or the code of another app. So in order for Phonak to overcome this issue with their code they would need to add code that would be able to sort through all these audio sounds and Android and Apple will not allow that. Each developer of each app is given a “key” to code their app only. So Phonak can’t create code for their app to sort through all the audio sounds.
Sadly the only solution is to turn the sliders for Phone and Audio to the off position. Let’s look at this image. Here you see 3 Phonak settings under Bluetooth. The BOTTOM 2 please leave them on. These are for the remote settings to control the volume and custom settings that you will create on the remote app. The BOTTOM 2 are only for SETTINGS from the Phonak remote app to the hearing aids. However the TOP setting, if you tap on it will take you to the sliders for Phone and Audio. These settings allow AUDIO to be transmitted through Bluetooth to the hearing aids. Although you set the controls on the remote app, the changes occur in the hearing aids. As one tech taught me, each hearing aid is a tiny computer. So you control the hearing aids through the Phonak Remote app. With the 2 sliders in the on position for Phone and Audio all sounds made on the cellphone are transmitted to the hearing aids and some of those sounds are forcing the hearing aids to default to Autosense. So the only solution that I have found is to turn both sliders to the off position. This will of course not allow the user to answer calls or play music through the hearing aids.
So a choice has to be made.
#Phonak #Deaf #Hearingloss #Hearingaids #signlanguage
[Gregory Watts has 5 IT degrees including a CompTIA A+ certification. He got his start in the IT field in 1983 writing computer code.]
The more technically explanation involves describing permissions, interrupt request, obtaining permissions from Android and iPhone and more. When writing this I kept in mind those who would be using the feature and not techs.
Microsoft does not want users to install Windows 11 on older systems, I personally do not believe it has anything to do with Microsoft wanting people to buy a new system, but with security. However many of us have older systems and may want Windows 11. I have Windows 11 installed on my Surface Pro 3 with a 4th Gen Intel, I have a 10th Gen Acer desktop with Windows 11 and I wanted Windows 11 on my Dell Latitude. After much trial and frustration I managed to succeed. My issue turned out to be, the different steps required were posted on different sites. There was no start to finish anywhere. Part of the reason is there are 2 different ways to do it and instead of posting that, only bits and pieces are here and there. I will now post a start to finish for BOTH methods.
So both methods have similar steps and I will simply repost the steps for each method.
Use the Windows 11 Media Creation Tool to created a USB Drive Boot. Download here
Method #1 a Clean Install.
Step 1: Back up your system, off the system. Back up to an external hard drive or USB drive.
Step 2: Enter the BIOS. On the Dell Latitude restart the system or from a cold start, press the F12 key before for the Dell logo or at the latest when you see the Dell logo. You will see a message that says you are entering ONE TIME BOOT MENU.
Step 3: Once in the BIOS look first for SETTINGS>GENERAL>BOOT SEQUENCE then Enable UEFI (After you do this you WILL NOT be able to boot back into Windows 10, but do not worry. Remember you created a USB key Windows 11 install from the Media Creation Tool before you got this far.
Step 4: VERY IMPORTANT, no matter what you read elsewhere DO NOT ENABLE SECURE BOOT, if you do you can't boot from the USB drive you made.
Step 5: We now need to enable TPM 1.2. The Dell Latitude does not have TPM 2.0, but Microsoft will allow users to install on systems with TPM 1.2. You simply have to agree to a warning message that also says you may not get updates, but you do get updates.
As above DO NOT enable SECURE BOOT.
Step 6: In the image below enable Lagacy Option ROMs to boot from. This will allow the BIOS to load the option to boot from the USB key you created.
Step 7: This is a 2 screen process in the BIOS but I did not take a shot of the first screen. So find SECURITY>TPM SECURITY the first screen will explain what TPM is and sounds a bit scary but click the box, you can close your eyes if it helps. After you click the box the BIOS will put this screen up (below) leave the 2 boxes checked and only click ACTIVATE. That is it. You are set now set to install Windows 11 on this old Dell.
Step 8: Now before restarting take that USB Drive that you made. Remember you used the Windows 11 Media Creation tool, you faithfully followed the instructions and put the Windows 11 install files on that USB Drive? So take that USB Drive you made and plug it into a USB port.
Step 9: Now click EXIT in the BIOS and if asked to SAVE say YES.
The Laptop restarts.
Again press the F12 key at the Dell Logo. It will again enter the ONE TIME BOOT OPTION.
But this time DO NOT enter the BIOS, you will see the option under Legacy Boot to boot to the USB Drive. It may have a different or odd name, but USB will be in the name. Choose that.
Follow the instructions and choose to do a fresh or clean install.
About 1 hour later you are running Windows 11.
Windows 11 Install on Dell Latitude Option 2
This method is longer and follows much of the same steps above but has extra methods involved. So why post it? Well some people are very scared of messing up their system or may want to go back to Windows 10.
First download the Windows 10 Media Creation Tool and create a Windows 10 USB Install Drive. So choose to save the Windows 10 install files to the USB Drive.
Then follow the steps above, exactly including backing up your laptop. Follow Step 8 above but this time you are reinstalling Windows 10. So why can't you just boot back into Windows 10? When you change the option in BIOS from Legacy boot to UEFI the "file" pointing to the MBR on the Hard Drive has altered. So what was in Legacy BIOS to look for the Windows 10 boot files has been altered, so reinstalling Windows 10 created a new Boot record for UEFI.
Now once Windows 10 is installed there is a great deal of work from here.
Go to SETTINGS>WINDOWS UPDATE and download ALL Windows 10 updates until you see the update 21H2 installed.
Now we get to edit the registry. Here is the source for the following information >CLICK HERE<
Press Windows key + R and type in REGEDIT
Then look for and create the following
The above registry key change tells the Windows 11 install process to ignore the TPM security check.
You will now need to download the Windows 11 ISO files, they are huge, over 5GB. Click >THIS LINK< to download them.
If you updated to Windows 10 21H2 then you can install from the ISO file from within Windows.
After it has downloaded Double click the ISO file then Double Click SETUP, follow the instructions, it may take more than an hour.
The original article can be found >HERE< I am going to copy and paste it here but the author is By Mayank Parmar October 24, 2021.
Android Subsystem for Windows 11 is one of the biggest new features that was originally supposed to come on October 5. It turns out that Microsoft needs more time to test the subsystem and it has started rolling out the feature to Insiders, but a simple trick now lets you sideload Android apps on Windows 11 without joining the beta channel.
Microsoft has confirmed that testers in the United States can download and install Android apps from the Amazon AppStore on Windows 11. However, Android Subsystem for Windows 11 is rolling out in stages, so the Amazon AppStore may not download when the Store app is not updated.
Windows 11’s Android Subsystem is available on eligible devices with Intel, AMD, and Qualcomm processors. Additionally, a minimum of 8GB of RAM is required to sideload Android APKs on Windows 11, while 16GB of RAM is recommended for the best experience on supported devices.
Sideloading APKs on Windows 11Thanks to WSA, we can sideload Android apps on Windows 11 without Google Play Store. It also lets you install and use mobile apps that you can’t find through app stores like Amazon, Google or Samsung.
What’s great about the Android Subsystem for Windows is that it lets you install nearly all Android apps without making changes to device settings. The process is similar to sideloading apps on your phone, but you should be familiar with Command Prompt.
In this guide, we’ll talk about the simplest ways of sideloading apps on Windows 11 using Command Prompt. The method is easy to follow, so let’s take a look at how it works.
How to sideload apps on Windows 11 using Command PromptIf you know the basics of Command Prompt and ADB (Android Debug Bridge), sideloading APKs on your Windows 11 PC can be a piece of cake.
Before getting started, make sure you’ve downloaded APKs for apps you want to install on your device. For this article, we chose to install the Brave browser downloaded from APKMirror.
To sideload Android APKs on Windows 11 using WSA without joining the beta channel, follow these steps:
4. Head to Google’s website and download the Android SDK Platform-Tools.
5, Extract Android SDK Platform-Tools to a folder of your choice.
6. Open Windows Search and type “Windows Subsystem for Android“, and click on it.
7. Inside “Windows Subsystem for Android”, scroll down and turn on “Developer mode”.
8. Click on “Files” to get the IP address. This step is required when the IP address is unavailable on the settings page.
9. If you still do not see the IP address, click Refresh or reopen the settings.
10. Once done, open Command Prompt.
11. Use cd command to navigate to the folder of Android SDK Platform-Tools. For example, if you extracted the tools in the Downloads folder, you would need to type cd c:\users\username\downloads\platform-tools and press enter.
12. In the Command Prompt, enter adb connect ipaddress that you copied earlier.
13. To install the APK, use adb install appname.apk. In this case, we’re using brave.apk (brave browser), so we entered the following command: adb install brave.apk
14. If you followed the steps correctly, a success message will appear in the Command Prompt.
You will find the app listed in your Start menu and these Android apps can be uninstalled like other apps.
Microsoft has gone to amazing lengths on the security to protect Windows 11. In fact that is the reason the systems requirements are so strict, an attempt to prevent hackers from getting any access to the OS or the computer. However I have come across 2 articles thus far where a user pr company has defeated or hacked a form of the Windows 11 security. I will update this article as I discover more. If you have one you would like to submit please reach out to me on About>Contact Us page.
The first "hack" was done by Mozilla Firefox. Microsoft has made setting anything but their apps as default difficult and deep. Mozilla wanted to be able to just allow the user to set the default browser from within the browser. Microsoft has claimed by making it difficult to alter the default apps it prevents hijacking and bad actors from hijacking existing apps or installing their own. So did Mozilla defeat this in Windows 11 before it was released. Read the full store. >https://www.theverge.com/2021/9/13/22671182/mozilla-default-browser-windows-protections-firefox<
Installing Windows 11 Without an Account
Windows 11 Home requires users to use an Internet connection and a Microsoft Account to install. However one user has already defeated this.
"Neowin forum member warwagon has created a video illustrating how Windows 11 Home users can still create a local account at startup without being forced to use a Microsoft email. When you see the “Let’s connect you to a network” screen, hit Shift-F10, type “taskmgr” in the command prompt window, and kill the process called “Network connection flow.” According to the video, this will allow the OS to install normally after you insert a user login and password. You can also kill the application directly from the command line if you like, using the command “taskkill /F /IM oobenetworkconnectionflow.exe”
You are on your Windows device, you go to the App Store and tap/click an app then tap/click "GET" and nothing. No error message, no warning, no install, no nothing. This is been a curse since Windows 10 and it also happens in Windows 11. There are hundreds of forums offering suggestions and nothing works.
After I installed Windows 11 on my Surface Pro 3 I did exactly that. I went to the App Store, tapped GET and nothing. I once more searched the Internet, nothing that worked. Then I figured it out. Like Android Microsoft limits the number of registered devices to a Microsoft or Windows account. The maximum number of devices according to Microsoft is 10, however in may case it tops out at 5, a 6th device can't make use of the store. I logged into my Windows account using a browser and navigated to my devices and removed the redundant ones, the App Store worked fine.
This has long been a curse of the Windows App Store and not even Microsoft is fully aware of the problem and the fix, they have never posted it and if you go to their forums you will not find this suggestion from Microsoft at the time of this post.
In reply to another reader I emailed Maximum PC magazine with the fix and they published it in the August 2021 issue. I have posted a shot of it as well. I know that many will now start to post this fix in self help forums and many will also take credit. However the article is published and dated. So please when posting the fix be honest where it came from.
A project that I have been working on for a while is "Life in Jesus Day" collecting real everyday archaeology finds and posting them with captions. I think it is interesting how many items are the same today as they were then. Be sure to bookmark the new page as I will update if often, visit it here Everyday Life in the Time of Jesus - Still With Eyes Closed (dewaynewatts.com)
DeWayne Watts: I started out writing short stories and poetry. Some of which was published in the 1980's. I have parts of 5 novels written and have completed 2 novels. I have been married over 25 years and raised 2 wonderful sons who have been a great addition to the human family.
Follow me on GOODREADS
The 3 Novels/Books Written By DeWayne Watts
Click Title to Buy the Book.
"The Boy in The Wood"
Click Title To Buy The Book.