Quantcast
Jump to content


Samsung Galaxy Z Fold 4 release date just leaked


BGR

Recommended Posts

Samsung Galaxy Z Fold3

After the Galaxy S22 series’ semi-disastrous launch, Samsung probably can’t wait to unveil its next flagship phones. These will be foldable devices, however. They’re the successors of last year’s Galaxy Z Fold 3 and Flip 3. The Fold 4 and Flip 4 have appeared in several leaks already, and we know what to expect from the handsets’ designs and specs sheets. And a leaker just revealed the purported launch, preorder, and release dates for the Galaxy Z Fold 4 and Flip 4.

 

The Fold 4 and Flip 4 will look like their predecessors, but fans of foldable handsets can expect several significant design changes.

Samsung’s Galaxy Z Fold 4 design is the more exciting of the two devices. The phone will be shorter and wider than the Fold 3. It’ll still have a massive internal foldable display. But it should be more comfortable to use the handset when folded because the external display will have a better aspect ratio.

The Fold 4 is also going to be lighter and thinner than its predecessor. Samsung will supposedly use a new hinge mechanism to reduce the phone’s weight.

100% accurate
Galaxy Z Fold4
7.6" QXGA+ AMOLED, 120Hz
6.2" HD+ AMOLED, 120Hz
Snapdragon 8+ Gen 1
12GB RAM
256/512GB storage
Rear Cam:
50MP + 12MP (UW) + 10MP (3x)
Inner Cam: 4MP 2.0μm (UDC)
Outer Cam: 10MP
Android 12, OneUI 4.1.1
4400mAh battery, 25W

— Ice universe (@UniverseIce) May 30, 2022

The same leaker who provided most of the aforementioned Galaxy Z Fold 4 details also listed the handset’s main specs. The main takeaway is that the Fold 4 will feature a brand new chip, the Snapdragon 8 Plus Gen 1 that Qualcomm just unveiled.

This implies that all the Fold 4 models will pack the same System-on-Chip (SoC), which is good news for fans. Poor Exynos 2200 performance hurt the Galaxy S22 this year, and many people think Samsung should drop its latest SoC as soon as possible.

Ice Universe has provided plenty of tidbits about the Fold 4 and Flip 4 in the past. But he never revealed the launch and release date details for the two Galaxy Z phones.

Thankfully, we now have that information from a different prominent leaker, YouTuber Jon Prosser.

Galaxy Z Fold 4 release date

The YouTuber took to Twitter to discuss several unreleased Samsung products, including the new foldables. Prosser revealed launch, preorder, and release dates in a series of tweets. He mentioned the Galaxy Z Fold 4, Flip 4, a Lavander version of the Galaxy S22, as well as upcoming Galaxy Watch 5 and Watch 5 Pro wearables.

If Prosser’s sources are correct, Samsung will hold its Galaxy Z Fold 4 launch event on August 10th. That’s when the company should unveil the Flip 4 and its new 2022 wearable generation. Preorders for all these products should start on the same day.

Then, the Galaxy Z Fold 4 and the rest of these new devices will apparently get the same release date: August 26th.

(2/2)

Watch 5 (40mm)
Phantom Black, Silver, Pink Gold

Watch 5 (44mm)
Phantom Black, Silver, Sapphire (blueish color)

Watch 5 Pro (46mm)
Phantom Black, Silver

Announcement / pre-orders Aug 10
Launch Aug 26

— Jon Prosser (@jon_prosser) June 8, 2022

The leaker said that the Galaxy Z Fold 4 will come in Phantom Black, Green, and Beige. The Flip 4 will be available in colorway options at launch, including Graphite, Bora Purple, Pink Gold, and Blue.

The Galaxy Watch 5 will come in 40mm and 44mm sizes, which sound familiar. Both models are said to be available in Phantom Black or Silver. The smaller model will get a Pink option, while the 44mm will get a Sapphire (blueish) colorway. The Watch 5 Pro will also reportedly come in Phantom Black and Silver, but it’ll be slightly larger at 46mm.

Prosser did not provide pricing information for any of these devices, but at least we have an apparent release date. However, considering that Samsung went out of its way to make last year’s foldables more affordable, we’d expect a similar strategy for the Galaxy Z Fold 4 and Flip 4.

The prices should leak as we get closer to the launch event.

The post Samsung Galaxy Z Fold 4 release date just leaked appeared first on BGR.

View the full article

Link to comment
Share on other sites



  • Replies 0
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
  • Similar Topics

    • By Samsung Newsroom
      Samsung Galaxy Fold devices have taken the mobile industry by storm, offering users a revolutionary way to interact with their applications. One of their key features is the rear display mode that enables users to continue their tasks seamlessly on the cover display while the main display remains turned off. Jetpack WindowManager has introduced APIs to enable this mode programmatically, and starting from One UI 6.0, developers can now utilize these APIs to integrate rear display mode into their applications, enhancing usability and maximizing the potential of foldable devices.
      In this blog post, we dive deeper into implementing Jetpack WindowManager's rear display mode in a camera application. By leveraging this mode, users can take selfies with superior image quality using the rear camera instead of the front camera. Join us as we explore the exciting possibilities of foldable technology and uncover how to optimize your applications for the Samsung Galaxy Fold.
      You can download the sample camera application here.
      CameraXApp.zip (623.3 KB) Sep 26, 2024 Step 1: Add the WindowManager library into the project
      WindowManager, a Jetpack library introduced by Google, supports rear display mode starting from version 1.2.0-beta03. To add the WindowManager library, go to Gradle Scripts > build.gradle (Module: app) and enter the following to the dependencies block:
      implementation "androidx.window:window:1.3.0" Step 2: Implement the WindowAreaSessionCallback interface in MainActivity.kt
      The WindowAreaSessionCallback interface updates an Activity about when the WindowAreaSession is started and ended. Using the onSessionStarted method, this interface provides the current WindowAreaSession as soon as a new window session is started.
      class MainActivity : AppCompatActivity() , WindowAreaSessionCallback { … override fun onSessionEnded(t: Throwable?) { if(t != null) { println("Something was broken: ${t.message}") } } override fun onSessionStarted(session: WindowAreaSession) { } } Step 3: Declare variables
      The WindowAreaController provides information about the moving windows between the cover display and the main display of the Galaxy Fold device.
      The WindowAreaSession interface provides an active window session in the onSessionStarted method.
      WindowAreaInfo represents the current state of a window area. It provides a token which is used later to activate rear display mode.
      WindowAreaCapability.Status represents the availability and capability status of the window area defined by the WindowAreaInfo object. We utilize this status to change the UI of our application. The status of the Galaxy Fold device can be one of the following:
      WINDOW_AREA_STATUS_ACTIVE: if the cover display is currently active.
      WINDOW_AREA_STATUS_AVAILABLE: if the cover display is available to be enabled.
      WINDOW_AREA_STATUS_UNAVAILABLE: if the cover display is currently not available to be enabled.
      WINDOW_AREA_STATUS_UNSUPPORTED: if the Galaxy Fold device is running on Android 13 or lower.
      private lateinit var windowAreaController: WindowAreaController private var windowAreaSession: WindowAreaSession? = null private var windowAreaInfo: WindowAreaInfo? = null private var capabilityStatus: WindowAreaCapability.Status = WindowAreaCapability.Status.WINDOW_AREA_STATUS_UNSUPPORTED private val operation = WindowAreaCapability.Operation.OPERATION_TRANSFER_ACTIVITY_TO_AREA Step 4: Create an instance of WindowAreaController in the onCreate method
      windowAreaController = WindowAreaController.getOrCreate() Step 5: Set up a flow to get information from WindowAreaController
      In the onCreate() method, add a lifecycle-aware coroutine to query the list of available WindowAreaInfo objects and their status. The coroutine executes each time the lifecycle starts.
      lifecycleScope.launch(Dispatchers.Main) { lifecycle.repeatOnLifecycle(Lifecycle.State.STARTED) { windowAreaController.windowAreaInfos .map { info -> info.firstOrNull { it.type == WindowAreaInfo.Type.TYPE_REAR_FACING } } .onEach { info -> windowAreaInfo = info } .map { it?.getCapability(operation)?.status ?: WindowAreaCapability.Status.WINDOW_AREA_STATUS_UNSUPPORTED } .distinctUntilChanged() .collect { capabilityStatus = it updateUI() } } } Step 6: Update the UI according to the device's WindowAreaCapability.Status
      private fun updateUI() { if(windowAreaSession != null) { viewBinding.switchScreenButton.isEnabled = true } else { when(capabilityStatus) { WindowAreaCapability.Status.WINDOW_AREA_STATUS_UNSUPPORTED -> { viewBinding.switchScreenButton.isEnabled = false Toast.makeText(baseContext, "RearDisplay is not supported on this device", Toast.LENGTH_SHORT).show() } WindowAreaCapability.Status.WINDOW_AREA_STATUS_UNAVAILABLE -> { viewBinding.switchScreenButton.isEnabled = false Toast.makeText(baseContext, "RearDisplay is not currently available", Toast.LENGTH_SHORT).show() } WindowAreaCapability.Status.WINDOW_AREA_STATUS_AVAILABLE -> { viewBinding.switchScreenButton.isEnabled = true } WindowAreaCapability.Status.WINDOW_AREA_STATUS_ACTIVE -> { viewBinding.switchScreenButton.isEnabled = true Toast.makeText(baseContext, "RearDisplay is currently active", Toast.LENGTH_SHORT).show() } else -> { viewBinding.switchScreenButton.isEnabled = false Toast.makeText(baseContext, "RearDisplay status is unknown", Toast.LENGTH_SHORT).show() } } } } Step 7: Toggle to rear display mode with WindowAreaController
      Close the session if it is already active, otherwise start a transfer session to move the MainActivity to the window area identified by the token.
      While activating rear display mode, the system creates a dialog to request the user’s permission to allow the application to switch screens. This dialog is not customizable.
      private fun toggleRearDisplayMode() { if(capabilityStatus == WindowAreaCapability.Status.WINDOW_AREA_STATUS_ACTIVE) { if(windowAreaSession == null) { windowAreaSession = windowAreaInfo?.getActiveSession( operation ) } windowAreaSession?.close() } else { windowAreaInfo?.token?.let { token -> windowAreaController.transferActivityToWindowArea( token = token, activity = this, executor = displayExecutor, windowAreaSessionCallback = this ) } } } Step 8: Start the camera preview
      Call startCamera() when onSessionStarted is triggered by the WindowAreaSessionCallback interface.
      override fun onSessionStarted(session: WindowAreaSession) { startCamera() } Step 9: Add a button and set a listener to it for activating rear display mode
      <Button android:id="@+id/switch_screen_button" android:layout_width="110dp" android:layout_height="110dp" android:layout_marginStart="50dp" android:elevation="2dp" android:text="@string/switch_screen" app:layout_constraintBottom_toBottomOf="parent" app:layout_constraintBottom_toTopOf="@+id/horizontal_baseline" app:layout_constraintStart_toEndOf="@id/vertical_centerline" /> viewBinding.switchScreenButton.setOnClickListener{ updateUI() toggleRearDisplayMode() } Incorporating rear display mode into your application can significantly enhance user experience by providing more intuitive control and greater flexibility. By following the outlined steps, you can create a more dynamic and user-friendly interface. As technology continues to evolve, staying ahead with features like rear display mode can set your application apart and offer users a seamless, professional-quality experience. To learn more about developing applications for Galaxy Foldable devices, visit: developer.samsung.com/galaxy-z.
      View the full blog at its source
    • By Samsung Newsroom
      A sensor's maximum and minimum values are crucial for calibration, data interpretation, threshold setting, user interface, error handling, sensor selection, and performance optimization.
      Understanding the expected range of values helps identify and handle sensor errors or anomalies, and selecting the right sensor for the intended use case is essential. Efficient use of sensor data, especially in resource-constrained environments like mobile devices, can optimize data processing algorithms.
      The maximum and minimum values of sensors play a crucial role in the accurate and efficient functioning of sensor-based applications across various domains. In this tutorial, a wearable application is developed to collect the maximum and minimum ranges of sensors from a Galaxy Watch running Wear OS powered by Samsung. This tutorial shows how to retrieve all sensor ranges together, as well as from one specific sensor separately.
      Environment
      Android Studio IDE is used for developing the Wear OS application. In this tutorial, Java is used, but Kotlin can also be used.
      Let’s get started
      The SensorManager library is used here to collect sensor data from a Galaxy Watch running Wear OS powered by Samsung.
      Retrieve the maximum range of a sensor
      To get access and retrieve the maximum ranges from the sensor:
      In Android Studio, create a wearable application project by selecting New Project > Wear OS > Blank Activity > Finish. To access the sensor, add the body sensor in the application’s “manifests” file.
      <uses-permission android:name="android.permission.BODY_SENSORS" /> To run the application on devices with Android version 6 (API level 23) or later, you need runtime permission from the user to use the BODY_SENSORS APIs.
      Add the following code snippet to the onCreate() method before calling any sensor operations:
      if (checkSelfPermission(Manifest.permission.BODY_SENSORS) != PackageManager.PERMISSION_GRANTED) { requestPermissions(new String[]{Manifest.permission.BODY_SENSORS}, 1); } else { Log.d("TAG___", "ALREADY GRANTED"); } After this code executes, a pop-up window appears and requests permission from the user. The sensor APIs return values only if the user grants permission. The application asks for permission only the first time it is run. Once the user grants permission, the application can access the sensors.
      Figure 1: Permission screen
      More details about runtime permissions can be found here.
      Create an instance of the SensorManager library before using it in the code.
      private SensorManager sensorManager; sensorManager = (SensorManager)getSystemService(Context.SENSOR_SERVICE); To retrieve the maximum range of all sensors, create a sensor list using API Sensor.TYPE_ALL.
      List<Sensor> sensors = sensorManager.getSensorList(Sensor.TYPE_ALL); ArrayList<String> arrayList = new ArrayList<String>(); for (Sensor sensor : sensors) { if (sensor != null) { arrayList.add(sensor.getName()); arrayList.add(sensor.getMaximumRange() + ""); arrayList.add(sensor.getResolution() + ""); } } arrayList.forEach((n) -> System.*out*.println(n)); The above code shows the sensor name, maximum range, and resolution. You can get all the available data from the sensors, such as type, vendor, version, resolution, maximum range, and power consumption, by applying this same approach.
      Remember, sensor information may vary from device to device.
      Additionally, not every sensor that appears in the logcat view is accessible. Third-party applications are still not allowed to access Samsung's private sensors using the Android SensorManager. You get a “null” value if you try to access the private sensors.
      Moreover, there are no plans to make these sensors available to the public in the near future.
      You can check my blog Check Which Sensor You Can Use in Galaxy Watch Running Wear OS Powered by Samsung to find out which sensors are accessible on your Galaxy Watch and which are not.
      Retrieve the minimum range of a sensor
      The minimum range is the complement of maximum range.
      If the maximum range is x, then the minimum range can be calculated like this: x*(-1) = -x.
      If a specific sensor value should always be absolute, then the minimum range is zero (0).
      There is no direct API available to retrieve the minimum range of sensors from Galaxy Watch.
      Get a specific sensor value
      To get specific sensor values from a Galaxy Watch, you can filter the sensor list or use the getDefaultSensor() method. Here is an example that demonstrates how to do this. Add the necessary permission in the “manifests” file for the accelerometer sensor:
      <uses-feature android:name="android.hardware.sensor.accelerometer" /> Use the following code in your Activity or Fragment to retrieve the accelerometer data:
      sensor = sensorManager.getDefaultSensor(Sensor.TYPE_ACCELEROMETER); if (sensor != null) { textView_maxV.setText(textView_maxV.getText() + "" + sensor.getMaximumRange() + ""); textView_resolution.setText(textView_resolution.getText() + "" + sensor.getResolution() + ""); } Ensure you have added the TextView element to your XML file. Output of the above code:
      Figure 2: Maximum range and resolution of the accelerometer
      Remember, sensor ranges may vary from device to device. You may get different values for different Galaxy Watch models.
      Download the example from this blog:
      SensorMinxMax (313.2KB) Sep 10, 2024 Summary
      This article demonstrates how you can retrieve the maximum and minimum ranges of sensors from your Galaxy Watch running Wear OS powered by Samsung. You can also use the above approaches to get other necessary available information from the watch that can be used for the precise and effective operation of sensor-based applications in a variety of fields.
      If you have any questions about or need help with the information in this article, you can reach out to us on the Samsung Developers Forum or contact us through Developer Support.
      View the full blog at its source
    • By BGR
      The Galaxy S22 has been a big success for Samsung so far, but the new flagship series isn’t without problems or controversies. The latest issue concerns the Galaxy S22 Ultra, as Samsung’s new Note model seems unable to hold a GPS connection.
      That’s the kind of problem that would impact any app that relies on location data. You’ll need GPS for Google Maps and other navigation apps. And you’ll also be using it whenever you want to share your location with someone else.
      Don't Miss: Wednesday’s deals: $50 Echo Buds, secret Fire TV deal, Oral-B sale, Samsung monitors, more The current controversies
      Before we get to the GPS issues, let’s look at the Galaxy S22’s other problems.
      I’ve recently highlighted four reasons not to buy the Galaxy S22, even when better price deals arrive. One of those concerns the Galaxy S22’s ability to survive drops, but it’s immediately fixable. The Galaxy S22 Ultra seems especially fragile in such accidents. You can reduce the risk by getting protective accessories from the first day.
      We then have Samsung misleading buyers regarding the Galaxy S22 and Galaxy S22 Plus display efficiency. Similarly, the 45W fast charging support available on the Plus and the Galaxy S22 Ultra seems to be a marketing gimmick.
      The most important issue concerns the phone’s performance. The throttling issue that was widely covered in the past few weeks might be hiding a more significant problem with Samsung’s flagships. It might be a chip a cooling issue. Samsung said in an explanation to shareholders that it hasn’t been cutting costs, however.
      That’s to say that the Galaxy S22 series is already drawing attention for the kind of faults you wouldn’t expect from a flagship. The GPS signal loss problem falls in the same category.
      Samsung Galaxy S22 Ultra in white, with stylus. Image source: Samsung The Galaxy S22 Ultra GPS problems
      Addressing camera quality issues, leaker Ice Universe also observed on Twitter that the Galaxy S22 is the best-selling Samsung flagship in years. But also the one suffering from the most problems. The leaker previously criticized Samsung for the throttling issue.
      The GPS connectivity complaints come from elsewhere, however. Android World detailed the problem, explaining that Galaxy S22 Ultra users would encounter GPS issues from the first boot. The problem can persist even after updates, and the GPS won’t work.
      A post on a Samsung Community forum in Europe has some 202 replies showing that some Galaxy S22 Ultra buyers have experienced the GPS problem. But the issue doesn’t appear to be widespread at the moment.
      There’s no fix for it either. The blog notes that resetting the APN settings might work. You can also consider resetting network settings. Whatever it is, it might be a problem with the phone rather than apps that need location data to work.
      If you’ve experienced any Galaxy S22 Ultra GPS issues, you can consider reaching out to Samsung for help.
      The post Some Galaxy S22 Ultra units might have a GPS connectivity issue appeared first on BGR.
      View the full article





×
×
  • Create New...