Database Develop

BeyondPod for Android Beta 1 is out

BeyondPod for Android is the Android version of the popular RSS feed reader and podcast manager for Windows Mobile.
Short YouTube demo and the Beta are available at http://www.beyondpod.mobi/android

Awesome. Doggcatcher is too buggy. Can't wait to give this a shot. Thanks for the heads up.

BeyondPod Beta 2 is now available
BeyondPod BETA 2 was released today.
If you are using Beta 1, here is what is new in BETA 2:
* Added Update Scheduling. You can now create separate update schedules for each category. (Press and hold over the category in the Category View to set the schedule)
* Added Support for streaming and playing Videos and static Images
* Added a global setting to automatically update the feeds every time they are open in the content view
* Added a global setting to Toggle WiFi During update (WiFi On -> Update -> WiFi Off)
* Added a global setting that prevents BeyondPod of using the cellular connection for updates. (Useful if your cellular data plans charge for traffic)
* Added a global setting to disable the automatic download of feed images in the browser.
* Reduced the timeout when the remote server is unavailable
* Removed Accelerometer screen rotation
BETA 2 is available from http://www.beyondpod.mobi/android/beta

SWEEEEEET!... Yeh dog catcher is cool, but gets hung up easily and doesn't play everything... Downloading now...

interesting. gonna have to try it. right now im using itunes to download the podcasts, then i have a script that copies them to my phone. would be nice if this does it automatically.
grr, already had it lock up on me.
im getting the requested file was not found.
java.lang.Integer when trying to view the NPR Top Stories

Killan,
Can you post the feed URL you are having problems with. Are you having problems opening the feed or downloading the podcast?

I use to use this with my WM phone. But with the g1, I use greed because its linked with my Google reader feeds. Its all about unity with Android.

BeyondPod 1.0.28 BETA is available
Here is what is new in this release:
* Fixed the issue where BeyondPod would show "java.lang.integer" error
in the feed content view or crash on opening the settings screen.
* Fixed an issue with scheduling where BeyondPod would stop the update
schedule after a device reboot
* Fixed an issue where the feed progress bar remains visible after
switching from the Feed Content view to the feeds view.
* Added more graceful handling of storage card removal and insertion
while BeyondPod is running. This also affects the case when you mount/
dismount the storage card using the USB connection
* Fixed an issue that sometimes would cause a crash in the Feed
Content View
You can download the latest beta from: http://www.beyondpod.mobi/android/BETA

TimSykes said:
I use to use this with my WM phone. But with the g1, I use greed because its linked with my Google reader feeds. Its all about unity with Android.
Click to expand...
Click to collapse
It's the beauty of Android! That alone will keep me buying android phones for years.
Greed is a great app... almost looks like Google made it. And the "free but donations always welcome" makes me <3 the dev.

BeyondPod for Android 1.0.29 Beta is available
This is what is new in this beta
* Fixed a bug in Google Reader integration where Shared items were not synchronized correctly
* Feed parsing engine was enhanced to handle wider variety of feeds including support for Cyrillic and other languages
* Added several improvements to the Feed Content view, including wider spacing between controls and fixes to scrolling when items are marked as read
Short YouTube demo and the latest beta can be downloaded from http://www.beyondpod.mobi/android

no login/pass support :<

If you are referring to password protected feeds, that feature will be in the next beta.

great, cheers.

BeyondPod 1.0.30 Beta is out
What is new in this build:
* Added a menu for Clearing the WebView Cache (stored in /data/data/mobi.beyondpod/cache/webviewCache) and the Feed Cache (stored in /sdcard/BeyondPod/RssCache). The option is located in Menu > More > Clear Caches
* Added support for password protected feeds. Now you can add user name/password in the feed properties.
* There is an option to change the color of the item titles in the feed Content view (used to be Orange). The option is located in the global settings.
* Fixed an issue with the Scheduling where it did not set correctly the start time of the schedule if the repeat interval was set to hours
Beta can be downloaded from http://www.beyondpod.mobi/android

Can anyone give me some insight on how to incorporate google reader? I'be got all my feeds there and would like to just use those.

[RHBROMS][WIP][Guide] Mobile Application Testing [Manual Testing/Automation Testing]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Presents
Mobile Application Testing
This will be a Full Tutorial on Mobile Application Testing.
I will be updating this thread as I get time. SO NO ETA's.
Click to expand...
Click to collapse
If anybody wants to use / copy this tutorial to their Website or Blog please feel free to contact me at my personal email id: [email protected]
or at our official Website: www.rhbroms.com
Click to expand...
Click to collapse
Please Click on Thanks button if this tutorial by me had helped you for some extent !!!
Click to expand...
Click to collapse
Manual Testing
Contents:
1. What is Mobile Application Testing?
2. Difference Between Mobile Testing and Mobile Application Testing.
3. Mobile Application Extensions and Small intro about Android Platform.
4. How to Test a Mobile Application?
Automation Testing
Click on the below Topics to Lean Automation Testing..
It will take only 2-3 days to learn If you are good at Java
Contents:
1. Robotium for Android Application Testing.
2. Monkeyrunner for Android Application Testing.​
Credits,
My Parents - For the best support.
@Swaroop Bandagadde - For the best support.
Renas Reda(Founder of Robotium Test Automation Tool) - For liking my tutorial and for the best support. :good:
jutikorn (My friend) - For the best support.

Mobile Application Testing
1. What is Mobile Application Testing?​
It is somewhat similar to software testing but the testing will be performed on a mobile device instead of performing on a system.
Types of Mobile application Testing are:
1. Installation testing.
2. Functional Testing.
3. Memory Leakage Testing.
4. Interrupt Testing.
5. Usability testing.
6. Certification Testing.
7. Performance Testing.
8. Integration Testing.
9. System Testing.
10. Accessibility Testing.
11. Adhoc(Monkey) Testing.
The all above points will be discussed on "How to Test Mobile application?" Chapter.
2. Difference Between Mobile Testing and Mobile Application Testing.​
Mobile Testing
- Mobile Testing is testing of Mobile Handsets or Devices.
- Here we mainly concentrate on Native applications(Blot wares).
- Testing all the core like SMS, Voice calls, Connectivity(Bluetooth), Battery(Charging), Signal receiving, Network are working correctly.
- Testing is conducted on both hardware and software.
Mobile Application Testing
- Mobile Application Testing is the testing of mobile applications which we are making as third party for the targeted mobile handset.
- Some core feature of the mobile are tested just to see that your application has not created any side effects on the device functionality.

Mobile Application Extensions and Small intro about Android Platform
3. Mobile Application Extensions and Small intro about Android Platform.​
Below are some Mobile Platforms given with respective File Extensions
1. Android - .apk (Android application package file)
2. Iphone - .ipa (iOS application archive file)
3. Symbian - .sis (Software Installation Script)
4. J2ME - .jad and .jar (Java Application Descriptor and Java ARchive)
5. RIM - .alx and .cod
6. Windows Mobile - .cab
7. Bada - .jad and .jar (Java Application Descriptor and Java ARchive)
Android Platform
Testing Purpose we should have to know about the android architecture as well as about Android Versions. Details On this discussed below:
Architecture of Android:
Android operating system is a stack of software components which is roughly divided into five sections and four main layers as shown below in the architecture diagram:
Linux kernel
At the bottom of the layers is Linux - Linux 2.6 with approximately 115 patches. This provides basic system functionality like process management, memory management, device management like camera, keypad, display etc. Also, the kernel handles all the things that Linux is really good at such as networking and a vast array of device drivers, which take the pain out of interfacing to peripheral hardware.
Libraries
On top of Linux kernel there is a set of libraries including open-source Web browser engine WebKit, well known library libc, SQLite database which is a useful repository for storage and sharing of application data, libraries to play and record audio and video, SSL libraries responsible for Internet security etc.
Android Runtime
This is the third section of the architecture and available on the second layer from the bottom. This section provides a key component called Dalvik Virtual Machine which is a kind of Java Virtual Machine specially designed and optimized for Android.
The Dalvik VM makes use of Linux core features like memory management and multi-threading, which is intrinsic in the Java language. The Dalvik VM enables every Android application to run in its own process, with its own instance of the Dalvik virtual machine.
The Android runtime also provides a set of core libraries which enable Android application developers to write Android applications using standard Java programming language.
Application Framework
The Application Framework layer provides many higher-level services to applications in the form of Java classes. Application developers are allowed to make use of these services in their applications.
Applications
You will find all the Android application at the top layer. You will write your application to be installed on this layer only. Examples of such applications are Contacts Books, Browser, Games etc.
Android Application Activity Lifecycle
The life cycle of an activity with main methods as shown below:
onCreate() This is the first callback and called when the activity is first created.
onStart() This callback is called when the activity becomes visible to the user.
onResume() This is called when the user starts interacting with the application.
onPause() The paused activity does not receive user input and cannot execute any code and called when the current activity is being paused and the previous activity is being resumed.
onStop() This callback is called when the activity is no longer visible.
onDestroy() This callback is called before the activity is destroyed by the system.
onRestart() This callback is called when the activity restarts after stopping it.
If you know this much it is enough to Go ahead with Mobile application testing in Android platform.

How to Test a Mobile Application?
4. How to Test a Mobile Application?​
1. Installation testing:
To Verify application can be installed successfully.
Different ways of Installing an application to Android Device:
1(a). OTA(Over The Air) : We can install our application by using android play store app on the mobile or else by browsing into Google playstore website. This can be done using WiFi as well as by using GPRS connection.
1(b). Sideloading From Your PC : To do this we need ADB(Android Debug Bridge). This is a very simplest way to install any 3rd party app to your device, most of the time we test engineers prefer this way only.
Just download and Install Android SDK to your system and follow the below steps:
1. Download the application (APK) file to a folder of your choice on your computer.
2. Connect the phone to the computer through the USB port.
3. Enable installation of non-market applications on your phone:
a. On your phone, open the Applications menu (i.e., the tab in the bottom center of the
phone’s home screen) and click on the Settings application, then select Applications
from the Settings menu.
b. Make sure that the first selection, Unknown Sources, is checked so that you can install
an APK file from a location other than the Android Market. A warning message about
the phone being vulnerable to attack will be displayed. Select OK to continue if you
trust the APK file you are about to download. You can change this setting back after the
current installation is complete.
4. Turn on “USB debugging” on your phone: open the Applications menu and select Development,
then enable USB debugging.
5. Open a command/terminal window:
• On Windows, select Start > Run> then type ‘cmd’.
• On Mac OS X, open the Applications folder, select Utilities, then Terminal.
• On Linux, select Applications > Accessories > Terminal.
6. In the command/terminal window, enter the following command:
Code:
adb install <APK_FILE_PATH><APK_FILE>
2. Functional Testing:
Testing the functionality of the application with respect to given requirements of the application.
2(a). Application LOGO Test: Testing the logo of the application to check whether the app which is under test have used the proper logo as per the requirement specification or not.
2(b). Application Splash Screen Test: To verify that when user selects application logo in application manager splash is displayed.
Note that Splash do not remain for more than 3 seconds.
2(c). Application Background Image Test: To test whether the application under test is using the proper Background image as per given requirement specification or not.
2(d). Font style / size / color: Testing the Font size/style/color as per requirement specification.
2(e). Layout: Testing the layouts with respect to given requirement specification.
2(f). Back Key: Verify that back key should navigate the user to previous screen or should close the application with proper exit popup dialog(Again it depends on Requirement specification).
2(g). Application Start/Restart:
i. Find the application icon and select it
ii. Observe the application launch In the timeline defined.
iii. Application must not take more than 25s to start
2(h). Exit Application: Verify that user is able to exit from application with every form of exit modes like Flip, Slider, End Key or Exit option in application and from any point.
3. Memory Leakage Testing
Memory leakage happens when a computer program or application is unable to manage the memory it is allocated resulting in poor performance of the application and the overall slowdown of the system. As mobile devices have significant constraints of available memory, memory leakage testing is crucial for the proper functioning of an application.
4. Interrupt Testing
An application while functioning may face several interruptions like incoming calls or network coverage outage and recovery. The different types of interruptions are:
Incoming and Outgoing SMS and MMS.
Incoming and Outgoing calls.
Incoming Notifications.
Battery Removal.
Cable Insertion and Removal for data transfer.
Network outage and recovery.
Media Player on/off.
Device Power cycle.
An application should be able to handle these interruptions by going into a suspended state and resuming afterwards.
5. Usability testing
Checking the user-friendliness of the application is known as Usability testing.
We have to verify if the application is achieving its goals and getting a favorable response from users. The application should have to give the results in very few steps or in few clicks.
The best example for this is: If you are booking a movie ticket by using some application, user should get the ticket booked in a very short amount of time / only by using 3-4 activities maximum!!
6. Certification Testing
Use this command : (Jarsigner is in your Java bin folder goto java->jdk->bin path in cmd prompt)
Code:
$ jarsigner -verify -verbose -certs my_application.apk
If you see "CN=Android Debug", this means the .apk was signed with the debug key generated by the Android SDK (means it is unsigned), else u will find something for CN. for more details http://developer.android.com/guide/publishing/app-signing.html
How do developer signs their apps:
He/She creates a keystore file by using the below cmd:
Code:
$ keytool -genkey -v -keystore my-release-key.keystore
-alias alias_name -keyalg RSA -keysize 2048 -validity 10000
To show you how it works I have given a screen shot of creating one below:
After generating key we have to follow the following steps:
Right click on project > Android Tools > Export Signed Application Package
The Export Android Application wizard appears.
Select the project I want to export, click Next.
The Keystore Selection screen appears.
Select the keystore and enter the password.
After this just give the path of the .apk file that has to be released.
7. Performance Testing
This testing process is undertaken to check the performance and behavior of the application under certain conditions such as low battery, bad network coverage, low available memory, simultaneous access to application’s server by several users and other conditions. Performance of an application can be affected from two sides: application’s server side and client’s side. Performance testing is carried out to check both.
This is done by performance test engineers. They use specific tools for this, for example: LoadRunner, Apache JMeter etc...
8. Integration Testing
Testing the data flow between two modules(activities) is called to be as Integration Testing.
This is done after finishing of Functional Testing.
The reason why we do Integration Testing is to make sure that all the activities are connected together properly or not.
9. System Testing
It is a end to end testing of the application where in Testing Environment is similar to production.
Here we test the data flow from the beginning to the end, If something is broken we have to report it as a bug.
We perform system testing after finishing of Integration Testing.
We perform system testing to make sure that end to end scenarios of the application is working properly or not.
10. Accessibility Testing
Accessibility testing is a subset of usability testing where the users under consideration have disabilities that affect how they use the application. The end goal, in both usability and accessibility, is to discover how easily people can use application and feed that information back into improving future designs and implementations.
This testing is done after completion of system testing.
11. Adhoc Testing(Monkey Testing)
Testing the application in a random way is called to be as Adhoc or Monkey Testing.
Monkey Testing is done after completion of full software testing and reporting of all the bugs is done. And also when the product is almost stable.
The reason why we perform this testing is,
To some how brake the product.
To find more number of bugs.
To make the software more stable.
to be continued...

It's very massive info, which you have shared with us.
I just want to know what's the meaning of Defect Detailed Report ?

[Android 4.1+] HeadUnit Reloaded for Android Auto with Wifi

This Threader is a Spin-off of the original: [Android 4.1+] Headunit for Android Auto - 160117 - Self Mode+ other fixes, x86, 720p by the late :crying: @mikereidis.
App links: https://www.b3itlabs.com/prod.php?id=1
PlayStore: https://play.google.com/store/apps/details?id=gb.xxy.hr
Previous XDA Lab purchases can be downloaded using: https://www.b3itlabs.com/download.php
Last edited: 20/04/2023
Version 7.X Released
- It has braking changes for WiFi, this is mainly due to recent Android SDK limits, like toggling WiFi, BT, getting Mac address and others. Therefore WiFi connection now does need a helper app on the phone.
- Dropped GLES20 as too many issues reported by different bad implementations
- Resolution is now automatically detected based on the cars screen.
- SelfMode (running on phone screen) works without the need of activating developer options in Android Auto.
Last edited: 07/02/2021
Version 6.3 Beta 1 released
- Re-wrote whole rendering process to use GLES20, in simple terms video render should use GPU
- Much better scaling approach
- Added support for native AA Wireless. This will only work on the units where the BT is accessible from the Android, as many of those android powered Chinese units, have a separate BT board. For devices which supports this, no headunit server or no WiFi Launcher is needed.
- Changed key mapping, user can now define their own buttons as they wish.
Last edited: 21/06/2020
Version 5.2 released
- Removed WiFi Direct
- Improved menu UI CREDIT and THANKS TO @sebaw
- Updated margin setting
- Added option to record audio using BT mic (motorcycle helmets)
- Added button to reconnect WiFi connection ( phone and unit depended won't work on all units, please read app forum for how to connect)
- Option to disable touchscreen
- Removed brightness adjustment (some users experienced problems adjusting brightness after using previous version, sadly they need to do a factory reset of the unit, and update to current version)
Version 5 released
- New UI CREDIT and THANKS TO @sebaw
- New over-scan approach allowing any resolution units to work properly (including portrait mode)
- New mic source (should help with speech recognition)
- Added option to keep status bar (user request)
- Added welcome setup
- Added possibility to use old USB driver (android built in one) in case you cannot get it connected with the new version
- Added option for Gain control on mic
- Added option to keep Wifi off (for USB use)
- Changed Wifi Direct implementation (you will need to install the Wifi Launcher for HUR on the phone to use Wifi Direct)
- Removed option to stretch full screen as this is not needed any more (it will always be full screen)
- Fixed Incoming mode not setting password for some devices
- Fixed app crash when Wifi toggled during app running
- Fixed night icon colors for devices running 4.x
- Fixed app freeze if permissions denied
- Fixed app crash after device unplugged when using native android USB driver.
- Fixed day/night calculation if share GPS turned off
- Code cleanup
- Other bug fixes.
Also a big THANK YOU to @ppietak for helping with code cleanup and bug fixes!
Version 4.5 released
- Fixes for USB shuttering
- New USB driver
- Fixes for reverse camera not resuming on some units
- Added support for incoming connection listener (automating Wifi) - Experimental, read below how to connect
Version 4.4 Released
Change log
Fixed broken touchscreen
Changes on WideScreen mode and HD
Fixes for Rotary
Potential fix for black screen for second connection over Wifi
Left/Right hand driving position option (for widescreen)
Buffer setting for mic (could help when Assistant does not hear what you're saying)
Enjoy XDA Ad Free and check out:
Version 4.3 Released
Change log
Fixed double skip on Spotify when using SWC
No more decoder workaround needed (updated code for video playback)
Added support for rotary (arrow keys can be used for non-touch input)
Enhanced mic input (mic sampling rate can be adjusted in settings for better compatibility)
Added intent: "gb.xxy.hr.WifiP2P" for Wifi-Direct start
Added app color scheme (dark menu for night)
Mapped Key N to open Maps (N=Navigation)
Mapped Key L to open Multimedia (L = Listen)
Changed USB code, hoping to help those who suffered for USB disconnection problems
Fixed a serious bug in share GPS code
For some rooted android headunits the app can now disable the default call screen being overlayed when HUR is running (only if HUR is set as the navigation app!) This will require ROOT
Version 4.1 Released
Change log
Removed Google Play Services dependencies
Honda compatibility fixes
Some other small bug fixes
Version 4.0 Released
How to use the app?
USB Mode
Plug in the USB to your device (in case of tablet use an OTG cable), when prompted make sure you allow HUR to be the default app for the action and you check the always box.
If you are running the app on a device with Android 7.0 or higher, you might need to pull down the notification bar and select the connected USB device before the app starts (this is device dependent)
If the app does not start automatically when you plug in your phone, you can always open HUR, tap the USB button and select the phone from the list.
Wifi Mode
READ SECOND POST​
Self Mode (when Android Auto and HUR are running on the same device)
Open HUR and press the self mode button. (you need to make sure Android Auto, Google Play Service, Google maps, Google Text To Speech is also installed on the device and it's up to date)
FAQ / Troubleshoot
All I get is a black screen
- If you are using an Android powered headunit (Joying, Xtrons, etc) look for a setting on your device which allows Video Playback during drive
- Try changing HUR settings and enable Software decoding
What does the "Share GPS" do?
- Share GPS actually forwards the GPS data of your device to the phone, so phone will need to do less work, comes really handy if you have an Android powered headunit, with external GPS antenna, however, if you using a tablet which is built into the dashboard, it's possible that you want to turn off this feature, because your phone will have a more accurate GPS fix.
What is the Sink Audio
- This option enabled HUR to work as a speaker for your phone. If you disable this option, all the sounds will be outputted on your phone speaker (or if your phone is connected to a Bluetooth device, then they will be played back on that)
My carrier doesn't provide data allowance for Wifi, what can I do?
Wifi data used between phone and tablet is classed as intranet not internet so it won't count against your data usage, but do be careful if you have auto-updates enabled on the device running HUR those updates will be downloaded over the phone's Wifi hotspot and that will incur data costs.
I have audio-sink enabled but phone calls are coming from the phone speaker. Why?
Android Auto is designed to sink all the audio over USB (Wifi) except phone calls where it will ALWAYS use a Bluetooth headset, if none is connected it will just flip the phone to speaker mode.
Are any hardware keys supported?
Volume Up
Volume Down
Media Next
Media Prev
Media Play
Media Stop
Media Rewind
Phone answer key (In case of incoming call it will answer the call, in case of not being on a call it will take you to the dial pad
F key - Same as Phone Key
M Key - Mic
H Key - Takes you to home screen
What about intents?
gb.xxy.hr.playpause Same as pressing the Play/Pause media button.
gb.xxy.hr.next Same as pressing the Next media button.
gb.xxy.hr.prev Same as pressing the Prev media button.
gb.xxy.hr.mic Triggers microphone input.
gb.xxy.hr.phone Same as pressing the dial key (answer phone call when ringing, takes you to dialer screen otherwise).
gb.xxy.hr.day Enables day theme.
gb.xxy.hr.night Enables night theme.
gb.xxy.hr.togglenight Switches between day and night theme.
I need more help.
- Feel free to ask a question on this thread, or you can always drop me an email to [email protected]
How do I collect a bug report / logcat
1. Enabling Developer Mode
1. Open Settings > About phone.
2. Scroll down to the Build number.
3. Tap the Build number 7 times in quick succession until "You're now a developer" appears.
4. Return to the Settings menu and select Developer options.
5. At the top of the screen, make sure 'Developer options' is set to On (green).
6. Scroll down to Debugging and enable both USB debugging and Bug Report Shortcut on (green).
7. Tab on Logger buffer sizes: Default setting is 256K. Select 16M to help capture more information for debugging. Of note, it can affect the apps performance especially with lower spec phone, so change it back after you have finished submitting bug reports.
2. Capturing a Bug Report
It's very important to do this right after you experience the issue again, so your device can log at least one occurrence of the issue.
1. Hold the Power button down until the menu appears.
2. Select Take bug report. and wait for the device to capture the bug report.
3. Tap the 'Bug report captured' notification when it appears.
4. Share the bug report. (I recommend to email it to yourself.)
5. Download the bug report to your computer.
6. Send the bug report by email to [email protected]
IF YOU UPGRADED TO ANDROID AUTO 2.X
Dial Pad is broken - Workaround available:
- Open AA -> About -> 3 dot menu -> Developer settings -> Application mode -> change to developer. This will bring back the Dial screen.
Version 3.0 Released
Changelog:
​
- Move USB functions from C to Java
- USB popup numbers limited to 2 and they should remain saved
- App will only start on a phone manufacturer vendor
- App is now running in multi-thread for better performance
- Much enhanced Wifi speed
- Better USB stability
- Should work on RK3188 units as well
- App runs as service so can be run in the background as well
- While running in background supports notification control for media
- While running in background on units running 5.0+ and above you will enjoy Heads-Up notifications for navigation
- Ability to rename the "Headunit" to your own prefered string.
- Fixed Wifi-Direct so can connect over Wifi-Direct as well, but not all devices seems to work
- Moved string to XML so translation to other languages should be implemented in the future
- Fixes some memory leaks
- Supports custom hardware keys
Version 2.5a Released
- Fix for USB close bug in 2.5
Version 2.5 Released - Attention contain BUG
- Left/Right button goes into endless loop
- Added support for ARM64
- Changed car name from Emil to Headunit
- Added mirror output support for HUD display.
Version 2.4 Released
- Improved performance (Wifi should be on par with USB now, even with Audio transport enabled)
- Improved touch sync (no accidental long touches and other strange occasional bugs)
- Option to share the GPS with the phone (reduce battery usage footprint on phone)
- Final fixes for Day/Night calculation and theme switching
- Auto volume adjust fixes (on supported ROM, the volume adjuster is hidden from the user)
- Software decoding works with Audio as well.
Version 2.3 Released
- Improvements and fixes for auto volume adjust
- Improvements and fixes for hardware key input
- Wifi speed improvements (should be able to run smoothly even with transport sound enabled)
- Tweaks for SelfMode (home and recent app button can be used to gracefully exit the app)
And the biggest change:
- Unlimited Browsing support - This is experimental and hacky it's possible that Google will close the loophole at some point but for the time being it works.
Version 2.2 Released - With some major changes
- Fixes for Communication Error 2 received with Play Service 10.X
- New Self mode
- Corrected channels order
- Unlimited browsing working when car is parked (only for Android Auto 1.6)
- Totally changed the Day/Night toggle logic, now the calculations are done inside the headunit app and updated each 10 minutes, so if you're driving all day the sunset/sunrise should be correct. even if you are 500 miles more to the north or west or whatever.
- Added Auto adjust volume option (works for bluetooth audio as well).
- Changed all the key mapping, and using real keys instead of simulated touches:
Supported hardware keys:
Volume Up
Volume Down
Media Next
Media Prev
Media Play
Media Stop
Media Rewind
Phone answer key (In case of incoming call it will answer the call, in case of not being on a call it will take you to the dial pad
F key - Same as Phone Key
D key - Changes to Day theme
N Key - Changes to Night theme
M Key - Mic
H Key - Takes you to home screen
The following keys are still usable but they are based on simulated touches:
Up Arrow = Scroll Up
Down Arrow = Scroll Down
Left Arrow = Moves to next Left tab
Right Arrow - Moves to next right tab
Version 2.0 Released
Changelog:
- Fixed calculated night mode
- Added support for Software decoding (should work now with any device) - If you have problems running HUR, go to settings and enable Software decoding. Do not use software decoding with audio transport, the audio playback will suffer a lot, consider streaming the audio from the phone to a A2DP directly or using a cable to connect the phone Jack to the stereo AUX, or if your phone is rooted you might want to consider Wifi Audio streaming app, it's too much to ask from the Software decoder to do both Audio and Video, unless you have a very strong CPU, but if that is the case I'm pretty confident that the Hardware decoding will work on the device.
- Added option for letterbox display (prevent distortion of stretch)
- Added option to start the app when connected to Wifi
Software Decoding
- Based on the feedback although it works, I'm not recommending this app for those with Joying or any other Rockchip (RK3188, RK3066) powered headunit. Feel free to use the trial and decide yourself, but it appears to be painfully slow on those devices.
Version 1.5 Released - Key features
- Stable Wifi connection
- Added support for Android 7.0 (Self mode as well)
- Self mode running in stable and usable way
- Connecting USB cable will start app automatically (even if phone is running Android 6.0 or 7.0)
- Supports keyboard shortcuts:
M = Start the Mic
N = Navigation Tab
P = Phone Tab
H = Home Tab
E = Entertainment Tab
UP Arrow = Scroll Up
Down Arrow = Scroll Down
Left Arrow = Moves to next Left tab
Right Arrow - Moves to next right tab
S = Play/Pause button (only works in Entertainment tab)
F = Next track (only works in Entertainment tab)
R = Prev Track (only works in Entertainment tab)
- Uses light sensor (if available) for toggling Day/Night theme.
If you are updating from version older than 1.2 please read:
You won't be able to install it over the old one (Key signature changed!), so please uninstall the previous version before updating, HOWEVER if you were upgraded for free from Mike's version, please follow this steps:
1) On XDA Labs, click the download Stable
2) When prompted to install select Cancel
3) Open a file explorer and go to Storage -> Android -> com.xda.labs -> files
4) Locate the newly download APK and copy it somewhere else.
5) Uninstall the old version
6) Install the APK which you just copied.
If you miss any of the steps, just reinstall the old version you received from me by email and try again, let me know if you are stuck.
App requirements:
- Android 4.1 or higher
- H264 Hardware decoding!
How to use the app: (Please read this steps before asking for help)
1) USB OTG
- Plug in the OTG cable to your tablet, connect your phone, done!
2) Self mode (for AA 2.0) - See Video
- Start Android Auto, Go to About, if you are not a developer yet press the "Android Auto" header 10 times, from the 3 dotted menu select "Start Head Unit Serve"
- Exit Android Auto
- Start HUR and select Self
3) Wifi
- From the phone create a Wifi hotspot
- Start Android Auto, Go to About, if you are not a developer yet press the "Android Auto" header 10 times, from the 3 dotted menu select "Start Head Unit Serve"
- Connect your tablet to the newly created Wifi hotspot
- Start the Headunit Reloaded app
- HTC ATTENTION! If your phone is a HTC, please change the default IP address to: 192.168.1.1
- Select Wifi
4) Wifi Direct (not supported by all phones/tables)
- Start Headunit Reloaded on the tablet
- Select Wifi Direct
- On the phone go to Settings -> Wifi -> Advanced -> Wifi Direct, join the group. (Do not try to connect as to a normal Wifi it will not work!)
- On the phone start Android Auto, Go to About, if you are not a developer yet press the "Android Auto" header 10 times, from the 3 dotted menu select "Start Head Unit Serve"
Other important notes:
Software Decoding
- Based on the feedback although it works, I'm not recommending this app for those with Joying or any other Rockchip (RK3188, RK3066) powered headunit. Feel free to use the trial and decide yourself, but it appears to be painfully slow on those devices.
To exit the app
If you are connected with USB, just unplug the USB cable, DO NOT use the exit from the menu. If you are running Wifi, Wifi Direct or Self mode, ALWAYS use the exit button from the left drawer menu!
Audio transport option
Will forward (sink) all the audio from the phone to the tablet if enabled, EXCEPT phone call audio, that will go trough the phone speakers or Bluetooth Handsfree if connected. If you wish to stream all the audio from the phone directly to your A2DP bluetooth, then simply disable the Transport Audio option.
Day/Night toggle
The device running the Headunit Reloaded app will be responsible for changing the theme. You can chose between using the light sensor of the device to toggle between day and night mode, or you can use calculated sunset sunrise mode, or even force it to one theme only. If you have previously installed AA Helper to your phone, please uninstall it!
Auto Start on Wifi
This option will launch HUR whenever you are connected to a Wifi (specific Wifi can be named)
Auto increase volume on speed
The logic behind is a very simple approach, every time the speed increases it will send a vol + key to the phone and every time the speed decrease it will send a vol - to the phone. This requires the device running HUR to have a GPS receiver.
OLD STUFF:
Version 1.3 (Wishlist version) - Released
- Added option for easy car mode toggling. (Car mode can be disabled if not using Self mode - avoid conflict with other Car apps)
- Auto Hide status + action bar while running the app no need to use the Hide option from menu
- App will automatically close when Wifi connection is lost
Version 1.2b - Released
- Buffer overflow protection - Special Thanks to invis-zz from GitHub (https://github.com/invisi-zz) - This should random crashes while using the app.
- Removed Send Log feature (it was classed as backdoor/trojan and Google was blocking the app on playstore)
- Updated OpenSSL library to 1.0.1t (used OpenSSL contained vulnerabilities and Play store blocked the app)
- Managed to get the app on PlayStore (wonder if it will stay...) - https://play.google.com/store/apps/details?id=gb.xxy.hr
Signature Key changed!!!!
I had to update the APK signature key (I'm trying my luck with Play Store), this means if you try to install the new version you won't be able to install it over the old one, so please uninstall the previous version before updating, HOWEVER if you were upgraded for free from Mike's version, please follow this steps:
1) On XDA Labs, click the download Stable
2) When prompted to install select Cancel
3) Open a file explorer and go to Storage -> Android -> com.xda.labs -> files
4) Locate the newly download APK and copy it somewhere else.
5) Uninstall the old version
6) Install the APK which you just copied.
If you miss any of the steps, just reinstall the old version you received from me by email and try again, let me know if you are stuck.
Version 1.1 Stable - Released
Jumping the version number due to significant amount of changes:
Removed Day/Night/Auto mode (see bottom of this post for a better solution.)
Added new setting for 720p Video - Fully working now (even on Wifi)
Changed Self mode start sequence (if the phone is rooted it will start automatically and then go back to HU), if your device is not rooted, please use the following sequence to start Self mode:
Start HU app
Select Self mode
When AA opens select Start Developer Server
Added support for hardware keys (simulating touches), so if your tablet is integrated with the car remote you can control AA from the remote.
Hardware keys as follow:
M = Start the Mic
N = Navigation Tab
P = Phone Tab
H = Home Tab
E = Entertainment Tab
UP Arrow = Scroll Up
Down Arrow = Scroll Down
Left Arrow = Moves to next Left tab
Right Arrow - Moves to next right tab
S = Play/Pause button (only works in Entertainment tab)
F = Next track (only works in Entertainment tab)
R = Prev Track (only works in Entertainment tab)
Some other minor tweaks, to improve stability and make Self mode connect 9 out of 10 times.
Fully integrated x86 native binaries
Declared app as CAR HOME, for those using SelfMode it is crucial, that when you get prompted which should be the default CAR HOME app (Android Auto or HU) you select HU!!! - This is needed to be able to bring back the HU on top after a successful connection is established. AA is trying to override everything..... and to block the user out of his phone as soon as it's connected to the car.
Transport Audio option will affect USB connections as well (You can keep the audio on your phone/bluetooth, when connected with the OTG cable)
Version 1.03b released - Beta
- You will find it in XDA Labs (under the Beta version)
- Fixes Wifi/Self mode for some devices which didn't connect before
- Increased stream buffer size to match the DesktopHeadUnit app (128Kb vs 64Kb)
Version 1.02 release
- Fixed wifi not connecting on some device only after numerous attempts (see explanation below if interested)
The issue looks to be related to the timing, on some occasions and on some devices the phone either sends the SSL data too soon, either too late, either to slow and because the TCP socket is set to non-blocking mode, it can end up in a missed packet in the initial Handshake. I have tweaked this now, so the TCP socket will connect in non-blocking mode, but will switch to blocking mode and wait for full message after a successful connection and once the SSL Handshake is out of the way it will revert back to non-blocking mode, uhhh event reading this makes me dizzy
This however could make the initial startup slightly slower than it was.
- Corrected AutoStart option (Working properly now)
- Fixed USB device overlapping Settings text on the drawer menu
- Added "Send Log" function to be used if there are problems for easier debugging.
Version 1.01 released
- Potential Wifi disconnect fix (see: http://forum.xda-developers.com/showpost.php?p=68078605&postcount=16 for details)
- AutoStart option added to the menu
Very sadly Mike passed away this year and his software stopped working after a Google Update, he left us a slightly outdated GPLv3 version of the software at: https://github.com/mikereidis/headunit which I have used to rebuild (or ty to) rebuild up to his latest build with some additional small modifications as well as fixing the issue caused by Google.
The forked version can be found on: https://github.com/borconi/headunit if anybody is intersted.
Since the app released by him isn't working any longer I have created the new version of it and slightly re-name it just to avoid any confusion.
I take almost no credit in this app, except for some minor changes, and finding the fix for what Google have broke (changed), which was a painful task.
I'm not a developer as such, and this app would never have existed if it wasn't for @mikereidis, however I have spent now several weeks studying the app and understanding how it's working and I plan to continue with the maintenance/development of the app.
I have published the app on XDA Labs under the new name: "Headunit Reloaded Android Auto" and it is now available for purchase. As I have stated previously I'm intending to support all of Mike's customers, so if you have purchased Mike's application before, please email me a proof of purchase to [email protected] and you can have a free copy of the spin-off app.
How to use (Self / Wifi ) ?
1) Self mode.
See instructions in version 1.1
2) Wifi Mode
Start AA on your phone, tap the header 20 times till you become a developer, once that is completed from the menu select Start Head Unit server. Now start tethering on the phone, connect the tablet to the newly created wifi hotspot, start HU on your tablet and select Wifi. This will make the HU app try to connect to the default Android gateway (192.168.43.1), if you need to change this, use the Settings menu from the HU option list. If HU doesn't start on first, do try a few more times, first setup sometimes proves tricky. If this is the first time you connect your phone to the a HU, please make sure you answer all the questions on the phone.
3) Wifi p2p
This is not supported by all devices and might not work for your device, plus sometimes it can be slightly buggy. Start WifiP2p on the tablet from the HU. On the phone go to Wifi Direct (this is usually found in Advanced Wifi settings settings - DON'T TRY TO CONNECT LIKE TO A NORMAL WIFI and look for a new available connection. If you can see one tap to join. Once you joined the network, give it about 30 seconds or so, then open the AA on the phone and start the head unit developer server (same as describe it above). If you're lucky it will work instantly, if not you might need to play around with it.
Other Options:
Possibility to toggle the Audio mirroring when using a Wifi connection. By disabling the Audio mirroring, you will keep all the audio on your phone rather than on the tablet (or on the handsfree) if the phone is connected to the handsfree. This will improve the performance greatly, since audio will use up a significant quantity of Wifi bandwidth when communicating between the 2 device.
USB OTG connection.
Have remained unchanged and it will work same way it did till now, see original threader for details.
I will monitor both Threads and will do my best to help and support everybody.

Well done! Thanks so much for your hard work Emil.

*Purchased
Also cloned and starting to build it as am having issues with my Joying head unit showing black screen after connecting (Test shows a black screen also).
looking forward to getting this running.

Syphe said:
*Purchased
Also cloned and starting to build it as am having issues with my Joying head unit showing black screen after connecting (Test shows a black screen also).
looking forward to getting this running.
Click to expand...
Click to collapse
What version of Android is your unit running? I haven't heard of any with less than lollipop being able to run this so far, h.264 decoding is absent or poorly implemented.
Edit....see the bottom of this post
http://forum.xda-developers.com/showpost.php?p=68010519&postcount=1449

Wifi Mode - Starting with HUR 7.X
Braking changes with version 7.X
Only for phones running Android 9 or higher, if you still use Android 8 phone, you won't be able to connect over WiFi. Device running HUR, can have any version of Android.
Phone Setup:
Install Wifi Launcher for HUR on the phone ( https://play.google.com/store/apps/details?id=com.borconi.emil.wifilauncherforhur&hl=en_US )
Make sure you give the app all the permissions, including draw over other apps, otherwise it cannot start Android Auto from the background!
Open the app and select the car's BT adaptor from the list (make sure phone is NOT connected to the car's BT, but BT is enabled!)
If you want your phone to create the hotspot, turn on the option to Enable hotspot (this will probably not work if you are on Version in the USA due to carrier limitations!), likewise if you want your car to create the hotspot or you want to use an incar wifi module, leave this option turned off.
Only turn on the legacy option if HUR specifically instruct you so.
Car/Headunit setup:
Connect to the phones hotspot or if you are using an incar WiFi connect to that network. Alternatively if you want HUR to create the hotspot and connect your phone to it, enable the option in HUR settings.
Open HUR
As soon as the 2 devices are on the same network, HUR will fire up on your car screen.

Emil Borconi said:
Hi Syphe.
The core of the app is the same as the original, and the app does require a hardware H264 decoding supported by the OS. Till now we are not aware of any chinese HU which support this. Please contact me by email and I'll refund your purchase.
Click to expand...
Click to collapse
You might want to post a "demo" version with just Mike's test mode that plays an H.264 screencap of AAuto running. Would be a good requirement-diagnostic app to have on hand, wouldn't take much time to bake - and it wouldn't have to track source either...
Just be sure to have it display a message popup saying that this is only a requirement check app, not an interactive demo. Something that informs users that its sole purpose is to make sure the decoders work. Maybe call it "Headunit Decoder Requirement Check.apk"

Christopher Price said:
You might want to post a "demo" version with just Mike's test mode that plays an H.264 screencap of AAuto running. Would be a good requirement-diagnostic app to have on hand, wouldn't take much time to bake - and it wouldn't have to track source either...
Just be sure to have it display a message popup saying that this is only a requirement check app, not an interactive demo. Something that informs users that its sole purpose is to make sure the decoders work. Maybe call it "Headunit Decoder Requirement Check.apk"
Click to expand...
Click to collapse
Yeah I thought about that myself.... will probably create a small check app in the near future (just need to catch up with all my other work now, which has been pushed behind to get this done)

bugger, thought it was quite promising when everything started to connect itself
I've been building my own app to do simple notification mirroring over a wifi tether, but this would have been much easier haha.

Does anyone know if there is a problem with xda labs on marshmallow or something? I've been trying to download this head unit app for the past week (was trying the old one and now this new one) and every time I click the pay now button for PayPal it just hangs there saying "Contacting PayPal". Is there maybe some other way to purchase the app? Any help would be appreciated, I really want to try this app out!

kevster0522 said:
Does anyone know if there is a problem with xda labs on marshmallow or something? I've been trying to download this head unit app for the past week (was trying the old one and now this new one) and every time I click the pay now button for PayPal it just hangs there saying "Contacting PayPal". Is there maybe some other way to purchase the app? Any help would be appreciated, I really want to try this app out!
Click to expand...
Click to collapse
Hi.
Yeah the XDA labs app can sometimes play funny, if your having any kind of issues feel free to contact me directly be email, on [email protected]

Hi Emil,
I had a chance to play with your new version. I got it to work, however it was not simple and I have a few issues.
I'm using it in WiFi mode. My Android TV stick(5.1.1) runs HeadUnit app and is connecting to my phone (Samsung Galaxy S7 Edge) that runs WiFi hotspot option.
The problem is that I need to click WiFi (in the menu of HU) many times for it to connect to my phone. It can take 5 to 15 clicks on Wifi option in HU for the phone to connect.
Is it the same for you? Any idea what can be the problem?
Also, I'd like to automate it somehow. I'm not using USB, so I'd like the HU app to be always ready for WiFi connection. Is it possible?
Thank you!
P.S.: I have some other issues/comments as well, but I'll keep them for later

fmark said:
Hi Emil,
I had a chance to play with your new version. I got it to work, however it was not simple and I have a few issues.
I'm using it in WiFi mode. My Android TV stick(5.1.1) runs HeadUnit app and is connecting to my phone (Samsung Galaxy S7 Edge) that runs WiFi hotspot option.
The problem is that I need to click WiFi (in the menu of HU) many times for it to connect to my phone. It can take 5 to 15 clicks on Wifi option in HU for the phone to connect.
Is it the same for you? Any idea what can be the problem?
Also, I'd like to automate it somehow. I'm not using USB, so I'd like the HU app to be always ready for WiFi connection. Is it possible?
Thank you!
P.S.: I have some other issues/comments as well, but I'll keep them for later
Click to expand...
Click to collapse
Hi Mark.
No it's connecting usually on the first attempt (sometimes on the second) but most of the cases it's first one. Yes I do plan to add a setting for Auto-Start mode in the settings which will make the app start in (Self / Wifi / wifip2p) as selected.
Does your phone have 3g/4g connection while tethering? The change which broke everything im Google Play service 9.2 is actually running a certificate check against google server, so without an internet connection to it won't start.
I had once or twice problem with the wifi myself (I got a debug message saying no route to the ip, meaning the Routing table on the tablet (stick in your case) got something wrong) a simple restarted did cleared the problem.
Please do report back if the problem persist and I'll send you a debug enabled app so I can get an understanding of what is going on, however probably that won't happen before Wednesday, looking forward to a long weekend.... of field work that is..

Emil Borconi said:
Hi Mark.
No it's connecting usually on the first attempt (sometimes on the second) but most of the cases it's first one. Yes I do plan to add a setting for Auto-Start mode in the settings which will make the app start in (Self / Wifi / wifip2p) as selected.
Does your phone have 3g/4g connection while tethering? The change which broke everything im Google Play service 9.2 is actually running a certificate check against google server, so without an internet connection to it won't start.
I had once or twice problem with the wifi myself (I got a debug message saying no route to the ip, meaning the Routing table on the tablet (stick in your case) got something wrong) a simple restarted did cleared the problem.
Please do report back if the problem persist and I'll send you a debug enabled app so I can get an understanding of what is going on, however probably that won't happen before Wednesday, looking forward to a long weekend.... of field work that is..
Click to expand...
Click to collapse
Yes, my phone has 4G connection while tethering.
Lets try the debug output. Could you please send me the .apk with debug messaging? I'm curious to see what is going on when it fails to connect.
Thank you!

Im interested too because isnt working on my s4 and nexus7 2012

wpostma said:
Im interested too because isnt working on my s4 and nexus7 2012
Click to expand...
Click to collapse
Need much more information to help. What S4 firmware, carrier, and Android version are you running? What Nexus 7 firmware? Are you trying to connect over Wi-Fi or USB?

Christopher Price said:
Need much more information to help. What S4 firmware, carrier, and Android version are you running? What Nexus 7 firmware? Are you trying to connect over Wi-Fi or USB?
Click to expand...
Click to collapse
It might be about the Wifi connection, I had some connectivity issues over Wifi myself the last day, but they were fully random, at a first look they point to the TCP socket.... I'm investigating this.
I got some Wifi disconnected myself but it is very random, it can occur after 1-2 minutes or after 3-4 hours... so testing potential FIX for the issue isn't going to be easily. At the first investigation it looks to be something related with the pooling/keeping connection alive. I have tweaked this and made a new build, currently running for about 20 mins and looks OK, but as said the disconnect can occur randomly at any point.
The worst part is that the logs do not give any hint on what could be the cause of this, neither on the HU part, neither on the AA side, they only mention a broken PIPE bu no hint on what can be the cause...

I'm guessing you've already tried, but running a 0 byte ping in the background every few seconds to keep the pipe open?

Christopher Price said:
I'm guessing you've already tried, but running a 0 byte ping in the background every few seconds to keep the pipe open?
Click to expand...
Click to collapse
setting socket to keppalive looks to sort the problem, I'm trying to figure out failing handshake at the moment. On TCP sometimes the handshake fails, trying a few more times passes..., handshake over usb always passes....
Looking at the code and notes Mike seems to struggle with it as well in the past...

When trying wifip2p, I can see the wifi connection from the tablet on my phone but when I try to connect to it, it wants a password. How do I know what this is?

skitty said:
When trying wifip2p, I can see the wifi connection from the tablet on my phone but when I try to connect to it, it wants a password. How do I know what this is?
Click to expand...
Click to collapse
Emil Helped me with this problem. You don't actually connect through your wifi networks menu, use Wi-Fi Direct instead. Found here: wifi networks menu > 3-dot menu > Advanced > Wi-Fi Direct

Mac FAQs: Your guide to common macOS terms

The popularity of Windows easily surpasses that of macOS because of its four-times-larger share in the PC market. Despite this differentiation, macOS still ranks as the second most used desktop operating system in the world owing to the lack of other popular options. Apple spares no chance to boast about the excellent and tasteful user experience offered by macOS — and users and fans echo it. At XDA however, we've focused more on Windows in the past and have only started attending to Mac recently. We recently published a Beginner's Guide to macOS for those switching from a Windows PC to a Mac. Next up is a glossary of terms that you can use to sound smart when talking about macOS.
In this article, we'll tell you about some of the most common terms relevant to macOS that every macOS user must know.
Glossary of standard macOS terms​iCloud​Apple's online cloud storage service is called iCloud and is linked to your Apple ID used to sign into your Apple devices. It automatically backs up your files stored in the Desktop and Documents folder. You get 5GB of free iCloud storage with each Apple ID, but you can also buy iCloud storage for a monthly payment if you need more.
In addition to cloud storage, you get features such as:
Find My that can be used to track the geographical location of all your Apple devices as long as they're connected to the internet.
Continuity, which synchronizes tasks on different Apple devices.
A universal clipboard.
At WWDC 2021, Apple announced iCloud+, which extends the utility of iCloud by adding features such as a VPN and unlimited storage for footage from Homekit-compatible security cameras.
Finder​[caption id="attachment_447827" align="aligncenter" width="900"]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Desktop folder in Finder[/caption]
Finder in macOS is where you'll find all your files, similar to File Explorer on Windows. Besides saving files in folders such as Downloads, Documents, and Desktop, Finder also lets Mac users view the apps installed on their computers in the Applications folder.
Dock​
The Dock is a floating row of apps traditionally placed at the bottom of the display. It can also be placed at the bottom, left, or right side of your Mac's screen based on your preference. Since macOS lacks a Taskbar, apps minimize into the Dock.
System Preferences​
System Preferences is the settings hub for everything on macOS. It's denoted by the gear icon on the Dock.
Control Center​[caption id="attachment_447877" align="aligncenter" width="487"]
Control Center on macOS[/caption]
Control Center, added to macOS with Big Sur, is an assortment of quick settings for essential features such as Wi-Fi, Bluetooth, AirDrop, and display and keyboard brightness on MacBooks. The Control Center is inspired by the feature on iOS and iPadOS and can be accessed by clicking on the icon to the left of the date and time on the Menu bar.
Spotlight Search​[caption id="attachment_447835" align="aligncenter" width="900"]
Spotlight Search on macOS[/caption]
Spotlight is a system-wide Search feature on macOS. It can be used to search files and folders, apps, and sub-menus in Preferences. Besides documents or apps stored on the Mac, Spotlight can also be used to preview web results based on the suggestions from your default web browser.
You can launch Spotlight search by pressing Command + Space on the keyboard.
Launchpad​[caption id="attachment_447881" align="aligncenter" width="900"]
Launchpad on macOS[/caption]
Launchpad is like an app drawer where you find all of the applications installed on your Mac. You can open Launchpad either by clicking on its icon (
) in the Dock or by pinching inwards on the trackpad with three fingers and a thumb.
Mission Control​
Mission Control is a powerful multitasking tool on macOS. It can be used to reveal all active apps on each desktop so you can switch between those apps seamlessly. It can also be used to arrange different maximized apps on different desktops.
You can also use Mission Control to merge two apps into a single desktop so you can use them side-by-side. To learn why you would want to do that, we have a good explainer on Why & How to Split your Screen on a Mac.
Stacks​Stacks can be used to organize items on the desktop. Using Stacks, you can arrange similar files in a single heap of files that can be expanded when you click on them. It is like a folder, but one less click away. Files can be arranged in Stacks based on the kind of file, the date it was created, added, modified, or last opened, or based on tags attributed to the file.
Continuity​Continuity is a suite of features used by Apple to facilitate an easy transition between your Mac and your iPhone, iPad, or other Mac, provided they are connected to the same iCloud account and the same network. Using Continuity, you can:
receive messages or calls from your iPhone on your Mac.
use your iPhone's data connection as a personal hotspot if your Mac cannot recognize any other Wi-Fi network.
copy on your iPhone and paste on Mac — or vice-versa — using a universal Clipboard.
take photos or scan documents on your iPhone and view them on your Mac.
perform tasks like view webpages, draft emails, or mark up media on your iPhone or iPad, and continue on your Mac.
Photo Booth​
If you've tried searching for "Camera" and couldn't find one on your MacBook, it's because Apple calls the app "Photo Booth" instead. You can use Photo Booth on your Mac to capture photos and videos. In addition, you can also try a myriad of comical and bizarre effects to make your pictures or videos enjoyable.
Sidecar​Sidecar lets you use an iPad as the secondary screen for your Mac. It's beneficial for creators who use an Apple Pencil for taking notes, graphics designing, or creating illustrations on their iPad. With Sidecar, these tasks can be accomplished directly on a Mac using apps like Adobe Illustrator. You can also use Sidecar to add a touchscreen to your Mac or use a secondary screen for apps that don't need to stay on your primary desktop. To use Sidecar, your iPad needs to run at least iPadOS 13 or higher.
Here are the minimum system requirements for your Mac to run Sidecar. You need to have a new model (listed on the link) of Mac, or else the feature might not work.
With the next version of macOS, i.e. Monterey, Apple will also allow seamless drag-and-drop between a Mac and an iPad without turning it into a secondary display.
Time Machine​As the name suggests, Time Machine is a backup utility in macOS, and it allows you to create timely backups of your Mac. You can create an entire backup of your Mac, including all files and folders, installed applications, saved IDs, and even preferences. You can assign a disk for an automatic backup of your Mac or create one manually every time you want. If something goes wrong and your Mac starts malfunctioning, you can reinstall macOS and use the latest Time Machine to completely restore your Mac as if nothing happened.
The vital clue here is to take regular backups, and the next item in this list can help you manage that.
Disk Utility​Disk Utility is a tool used to manage internal and external disks connected to your Mac. You can check disks for errors, create partitions, or erase external disks and partitions using Disk Utility. We also have an explainer that answers What is Disk Utility on Mac and what can it do?
Terminal​The Terminal is an application that lets you control and troubleshoot your Mac using a command-line interface. Like the Command Prompt — or Terminal Preview — on Windows, it can manage files or run commands and scripts.
Activity Monitor​
Activity Monitor lets you manage the activities running on your Mac and see the RAM, CPU power, storage, or network used by them. You can also terminate apps that are not responding and consuming too much of any of these resources listed above.
That's about it. If you can think of anything else that we didn't mention in our macOS glossary, let us know!

Xperia All in one Debloat Tool

PLEASE READ BEFORE USE OR ASK. ​IMPORTANT WARNING: ​DO NOT DOWNLOAD THIS SOFTWARE FROM ANY SOURCE OTHER THAN THIS THREAD/FORUM. IT IS XDA EXCLUSIVE AND I WILL NOT RELEASE IT ON ANY OTHER FORUM. ANY FORUM THAT USES MY NAME OR REPOSTS IT IS NOT ME OR APPROVED BY ME. DOWNLOADING FROM ANYWHERE ELSE COULD RESULT IN TAMPERED OR MALWARE-INFECTED SOFTWARE.​I AM NOT RESPONSIBLE FOR ANY VIRUSES OBTAINED BY DOWNLOADING THIS SOFTWARE FROM AN UNAUTHORIZED SOURCE. YOU HAVE BEEN WARNED!.​
IDEA BEHIND THIS SOFTWARE​As a long-time secondhand Xperia user, I have always preferred the Japanese version due to its lower price and Grade A quality. It is widely agreed upon that the Japanese version of the Xperia has slightly different hardware and software, and is often full of bloatware and dead services, especially for releases prior to the Xperia 1.
I have been developing this script for a long time for my own personal use, but I noticed that there are many people on the internet asking how to convert the Japanese version to the global version. This inspired me to create the Xperia All In One Debloat (XAIOD) tool, which allows users to easily remove bloatware with a single click. This tool is made with love for the Sony and XDA communities.
Official Demo Video
Community Demo video
Spoiler: Before
Docomo Variant
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Spoiler: After
Docomo Variant
KDDI AU Variant
Feature​-All in one EXE
No need to download ADB separately. Simply download and run XAIOD.exe anywhere, with its own built-in ADB (note: Xperia driver may need to be installed manually for some devices).
-Simple as click and wait
While advanced users can use the manual mode to select specific settings, this software is designed for simplicity. Just click and select what you want to remove, from vendor/operator apps only to full bloatware and dead/Japan-specific software, with just two clicks. Wait for the process to complete (note: depending on your PC hardware and phone vendor, it may take a long time, but it is easily cancelable with the escape key if it gets stuck).
-Almost foolproof
There is almost no way to break your phone with this software. It has triple fool protection (no joke - I really don't want to be blamed if someone uses this in a very stupid way) and has been tested on two real Xperia devices (Xperia XZs and XZ1 with Android 8 and 9) to the extreme, with no harm done to either device. However, someone may eventually find a way to use this in the most "unhuman" way possible, so please use with caution.(For the average user, this is 99.99% harmless, even if unplugged/rebooted during the process.)
-Completely offline
For those who may be wondering or concerned, this software works fully offline. There is no need to enable a firewall or make any changes to your antivirus software. If you prefer, you can simply disconnect from the internet and the software will continue to function like a charm (With the exception of external links like xpricheck.com, which I have included for reference, because let's face it, even I can't write out the entire database of Sony smartphone information that this software is indexing. But don't worry, it won't affect anything on your end. Unless, of course, you're dying to know what SOV35 or S0-5k stands for. In that case, just double click on any of the devices under Supported Models menu)
-Provided by me, maintained by us
This software could have been made in just two days, but I am taking it one step further by adding all future features now for easy updates. While it took longer to create, it will be easy to update and I am now finished with my work. It is now up to the community to provide me with app lists. So, while the native device list is currently small, the compatible list and community list will grow over time, thanks to you - those who help test by using it, adding more devices by giving/donating your vendor app names, and confirming whether things work or not by commenting.
How to use​
Download this Software + download Xperia driver (if needed only).
Enable USB Debugging by going to:
Settings > System > About phone > Tap build number (Android 8/9/10)
Settings > About phone > Tap build number (Android 11/12) Then:
Settings > System > Developer option > USB debugging tap to on (Android 12)
Settings > System > Advanced > Developer option > USB debugging tap to on (Android 9)
Settings > System > Developer option > USB debugging tap to on (Android 8) (Enabling "stay awake" is recommended if your display turns off in less than 5 minutes)
Plug your phone into your PC with a data cable (no more than 1 device)
Run the software.
Wait until the software recognizes the device. If the software is not detecting anything, check your phone and allow USB debugging on this PC.
Check if your device's status is native/compatible or not supported.
If native/compatible, hit auto mode and select the apps you want to debloat (more info below).
There will be a progress bar in the middle of the screen. Wait and please do not touch your phone or computer (finishing the process may take longer than other steps, so please be patient).
After it finishes, you will be sent back to the main menu. At this point, all is done.
DEVICES LIST​Native: App list is created and tested with real devices
Compatible: No app list yet, but similar lists from other native phones can be used
Not Supported: This device is detected as Sony, but there is no app list that can be used with it (auto mode not available, use Manual with caution)
Not recognizable: ADB debugging may not be enabled or the device you have plugged in is not a Sony or has been modified. Features are disabled to prevent harm to your device.
​Native Models:​
AU: SOV36, SOV39, SOV40
Docomo: SO-03J
Softbank: N/A
Global: G8341
Compatible Models:​
AU: SOV35, SOV34, SOV33, SOV37, SOV38
Docomo: SO-02J, SO-04J, SO-01J, SO-04H, SO-02K, SO-05K, SO-03K, SO-04K, SO-01L
Softbank: N/A
Global: G8342, H8416, H9493, H9436, J8170, J9110
Community Models:​
Docomo: SO-01K
Differences between modes in Auto.​Operator only:
This will only remove specific apps from specific vendors (Docomo/AU/Softbank) without removing other bloatware.
Operator + third party:
This will do the same as operator only, plus removing generic bloatware (Facebook, antivirus, etc.).
Third party only:
This will only remove generic bloatware without removing vendor apps.
Full Debloat:
This will remove all bloatware, both vendor and generic, and remove all Japanese-specific apps or Sony dead services.
How to Help this software grow:​There are three ways in which you can help this software grow:
The easiest and most effortless way is by upvoting, sharing, liking, or following me on XDA, YouTube, or Instagram. One single like already makes my day!
Using an APK analyzer is another way to help. With this app, you can see package names, which are the most important thing in this software. To do this, download the app, take a screenshot of all the app list on your phone (cropping, removing, or painting over any private apps if you wish), and send it to me (don't forget to include your phone variant, model, and operator).
If you are an advanced user, simply comment with your whole phone's package names that you have dumped with ADB shell.
if you play roblox. i do open donation inside "donate me". and maybe consider pay to add custom feature? or new custom Easter egg?. or if you that damn rich. why dont buy full source code XD
Any help counts, and for the first user who provides package names, their username will be written next to the device model in the Supported model menu.
Next Update:​Next Big version : Currently Slowly Working on it,
Next Update Plan:
Add More devices
Fix window size not correct on low resolution devices -Skipped for next update
Code improvement/optimization - Skipped for next update
Allow unofficial list/Third party to be loaded and run by anyone without update the program
Known bug/issue:​
possible to make program not responding by hotswaping while processing
on some model. sony software update accidentally included as bloatware, where it not suppose to, it most of model are docomo. please be advice if you using modern devices that still get software update to check if you devices effected or not. for end of support devices this does not effect everyday use except setting can crash if some app redirect user to see software update(e.g security update under lock screen and security)
android 7 or lower may have problem keyboard now showing if using replace feature. please try restart your devices and manually change keyboard settings(unfixable)
If you encounter any other bugs, please let me know.

Changelog History
Spoiler: Changelog Release 1.0.1.1B(20/05/2023
Fix Wrong Resolution / Fix Missing "about me" button
(If you already use 1.0.1.1 there no point donwload 1.0.1.1B, it same software, with 1 bug fix)
Spoiler: Changelog Release 1.0.1.1(30/04/2023)
Added new features and functionalities that are part of the upcoming update.
Addressed few typographical errors.
Tweaked menu and text names for improved clarity with the upcoming update
Added Official Community support for SO-01K (thanks to chacha lee for clear demonstration)
Spoiler: Changelog Release 1.0.1.0(22/01/2023)
Addressed various typographical errors.
Added 5 optional argrument(e.g. --N | --NOPROTECTION to Bypass Foolproof core protection(only for advance user only. does not disable entire foolproof system))
some argument now can be exported via cmd(e.g. XAIOD --VERSION>>name.txt)
Updated the foolproof system to address issues related to "hotswap devices."
Fixed an issue where the window could be resized while it was not supposed to be.
Fixed a bug where debug code was running outside of debug mode.
Resolved an issue where the program would not respond or crash if devices were disconnected while processing (though this may still occur in rare cases).
Removed unused variables.
slightly optimize performance.
Add EasterEgg
Spoiler: Changelog Release 1.0.0.1(12/01/2023)
Added Modern Method for Final processes(Legacy method still in use if Modern method fail)
Fixed Duplicate list
Optimized code for Improved Performance
Spoiler: Changelog Release 1.0.0.0(05/01/2023)
Added the ability to change or remove the SwiftKey keyboard
Changed from "Loading..." to "Press ESC to Abort" for clearer instructions
Enabled manual mode for advanced users
Fixed a bug that allowed users to remove operator apps on global models
Fixed model detection issues with global models being detected as Docomo or Softbank
Fixed a bug that caused the scroll button to not work properly
Fixed model detection issues with some Docomo models being detected as AU
Fixed a bug that caused some global models to try to remove "imaginary" vendor apps during full debloat
Optimized code for improved performance
Updated the list of Docomo apps
Improved Sony Detection Logic
Spoiler: Changelog Pre-release V2
Fix Minor bug
Fix Software Using Wrong Adb
small optimization
Spoiler: Changelog Pre-Release V1
Initial Pre-Release

thanks, it is useful but some very few bloatware remain in xz1 s0-01k, how can we add them to the debloat list

Your welcome. Well currently im busy with other project. But If you send the app list from your phone or app name or link to apkmirror if any. I can update it right now and probably available tomorrow. But remember the current list is base from real devices and tested. The app you might want to remove may connected to system or effect stability. If this the case then i am not add that. But still feel free do provided the app list to this post

Support So-53b please!

WOLF33B said:
Your welcome. Well currently im busy with other project. But If you send the app list from your phone or app name or link to apkmirror if any. I can update it right now and probably available tomorrow. But remember the current list is base from real devices and tested. The app you might want to remove may connected to system or effect stability. If this the case then i am not add that. But still feel free do provided the app list to this post
Click to expand...
Click to collapse
These are the apps that remain
I unistalled the 2 japanese apps on the last page of home screen

chacha lee said:
These are the apps that remain
I unistalled the 2 japanese apps on the last page of home screen
Click to expand...
Click to collapse
Thank you for clear demonstration, but could you send the app name? It would greatly help the progress. Other than that i guess i will update it this monday or later, as current im not home until sunday

com.nttdocomo.android.mydocomo
jp.co.lawson.android

chacha lee said:
View attachment 5897633
com.nttdocomo.android.mydocomo
jp.co.lawson.android
Click to expand...
Click to collapse
Thank you. I will update it ASAP

WOLF33B said:
Thank you. I will update it ASAP
Click to expand...
Click to collapse
ok

WOLF33B said:
Thank you. I will update it ASAP
Click to expand...
Click to collapse
Found another one, which one should i provide you the name ?

chacha lee said:
ok, just for more clarification i installed third party app (attached in sceenshot) to extract the names, i hope i did it correctly
Click to expand...
Click to collapse
chacha lee said:
Found another one, which one should i provide you the name ?
View attachment 5897639
View attachment 5897641
View attachment 5897651
Click to expand...
Click to collapse
No osaifu keitai is nfc relates to sony nfc type f. I tried but removing this also make nfc relate functions unstable that why i dont add it. You can remove the launcher/osaifu-keitai app manually you want but i dont recommended

thx a lot man

"Compatible: No app list yet" means that a list of all apps could be possible and then uninstall whatever we want ?

JIJOK said:
"Compatible: No app list yet" means that a list of all apps could be possible and then uninstall whatever we want ?
Click to expand...
Click to collapse
If you mean selecting something specific or similar, then no, it's not possible yet. However, if you mean uninstall using other similar model then yes. it all app that same as list get uninstall(but not whatever you want though), I am currently working to allow external list / custom list that can be made by anyone for anyone at anytime. whoever due to busy with other thing,due to being busy with other things, the development of this feature has slowed down. Nevertheless, I am already working on it. for now as long it sony,(and not softbank as I don't own it and cannot find a trusted app list for that model) you could try remove it manually via manual mode. it not perfect as same app but on newer phone change slightly the naming. but probaly remove at least 70% of the bloatware, as the hidden one normaly doesn't change the name On the other hand, if you are using SoftBank, unless you send me the app list for SoftBank, there is no list available at all.