yashsingh1/xdaforums huggingface dataset:
[Xiaomi Mi Mix 3 ROMs, Kernels, Recoveries, & Other] maikduarte:
Good afternoon people.

I've been using it for two days and despite having crashed twice so far and for it to come back it was necessary to restart the device... the ROM is very pleasant to use...

I will continue with it and look forward to the project continuing.

Congratulations on the work.
[Xiaomi Mi Mix 3 ROMs, Kernels, Recoveries, & Other] blacky2198:
It's good to see Paranoid Android back.

Just flashed it, so far it booted. Thank you and looking forward for the project future. Congratulations!
[Xiaomi Mi Mix 3 ROMs, Kernels, Recoveries, & Other] Until_You_:
The ROM is very smooth, I have been using it for two days and I like it very much, but there seems to be a random restart, and there seems to be a problem with the system's deep sleep, and it loses 30% of power in one night.thanks for your great job,Hope the next update will fix it
[Xiaomi Mi Mix 3 ROMs, Kernels, Recoveries, & Other] Epyon@1991:
hello I consult... the links are damaged of this rom... any possibility that someone has the files and passes them to me... thanks
[Xiaomi Mi Mix 3 ROMs, Kernels, Recoveries, & Other] denypher:
Rom is Good and very smooth. I think everything is fine, but I have one problem:

my led indicator is constantly blinking whether there are notifications or not. How can I fix it?
[MTCD Android Head Units General] Bertkeuter:
Does anybody know where to buy MTCD/E motherboards? I need one that accepts the PX6 RK3399 Chipset, and has WIFI and BT onboard.
[MTCD Android Head Units General] Bob_Sanders:
https://www.aliexpress.com/item/1005003292234331.html
[Windows Mobile Development and Hacking General] garthus:
Hi All,

I have an app that based on certain conditions will add a new contact to the Contact db (Pocket Outlook). I can programatically add a new user without a problem however i'd like to use pocket outlooks Add/Edit contact dialog to do it so i don't have to duplicate that functionality.

I'm developing in C/C++.

Thanks for any help.
[Windows Mobile Development and Hacking General] mjg7876:
the easiest way I can think of would be to use POOM (google 'POOM API'). add a contact would be something like this:

if ( SUCCEEDED(m_pPOOMApp->CreateItem(olContactItem,
(IDispatch**)&pContact)) )
{
hr = pContact->Display();
if ( S_OK == hr )
pContact->Save();
}

More info here:

http://www.developer.com/ws/pc/article.php/10947_3519721_1

Hope this helps
[Windows Mobile Development and Hacking General] garthus:
It worked

Thanks that did it with some tweaking. If you want the user to give the option to edit you can't add any values to the pContact until after the call to pContact->Display
[General Questions and Answers] FailSafeNow:
I need some help unlocking the bootloader on my Samsung A01. The instructions say to enable developer mode — basic stuff — and then enable USB debugging and OEM Unlocking. You guessed it: the OEM Unlock option just ain't there. I tried the trick with chaging the date and checking for updates, but it didn't help. Please, can anyone give me some help that will actually fix the problem? I just want to root this damn thing.
[General Questions and Answers] xXx yYy:
To root phone's Android unlocking phone's bootloader is NOT required.
[General Questions and Answers] FailSafeNow:
Ok then. How do I do it? All the other guides tell me I have to. And how would I install TWRP, which I definitely want to do?

Every guide I look at tells me I have to unlock the bootloader first.
[General Questions and Answers] xXx yYy:
You do NOT need to root your phone's Android to install TWRP - a custom recovery, but you will need to unlock the bootloader. Take note that Android OS has nothing to do with phone's bootloader, that Android OS gets launched by bootloader if device didn't get tampered.
[General Questions and Answers] FailSafeNow:
Ok, how do I just root for now? I want Magisk. I'm trying to install it with ADB, but I'm getting Error 21.

Furthermore, how do I unlock the bootloader when the system doesn't want to give me the OEM Unlocking option?
[General Questions and Answers] xXx yYy:
You do NOT need to root your phone's Android before to install Magisk: you typically root Android OS by means of Magisk.

You install Magisk via TWRP what requires an unlocked bootloader. You unlock a phone's bootloader via FASTBOOT tool what requires OEM Unlock option got activated before applying the bootloader-unlock.
[General Questions and Answers] FailSafeNow:
So basically until I can use the OEM Unlock option, I can't do a darn thing, can I?

So how do I get it?
[General Questions and Answers] FailSafeNow:
I'm going to ask for help on this again. I've been around the forum, I've looked for anything I could find, and I'm still no closer to getting this thing solved.
[Samsung Galaxy S21 Ultra] mattybuk1:
Has anyone actually been able to order an S22 Ultra on Samsung Upgrade? It just tells me they have Technical Difficulties or the loan agreement number is wrong (it isn't)...

Would be interesting to see what people have tried to get through or if anyone else has this same issue?
[Samsung Galaxy S21 Ultra] highlightshadow:
I ordered last night .... site was struggling and under a lot of load ...

I cancelled the order this morning .... I was going to give Exynos the benefit of the doubt but no, i cannot justify that anymore .... more benchmarks came out last night showing Exynos 2200 is barely still matching 888 let alone 8G1
[Samsung Galaxy Watch 4] mahmoudgamaljemmy:
Hello all,

I have a problem if anyone can help me 😢

I felt like my galaxy s10 plus had a battery drain so i cleared the storage of the play services in am attempt to fix it. After that my watch could not connect to my phone. I made a factory reset so it was able to connect but it can not copy the google account no matter how many times i try. I tried to make another factory reset, and to uninstall and reinstall the galaxy wearable app but no luck
[Samsung Galaxy Watch 4] berni502:
uninstall galaxy werable and galaxy plugin than format watch
[Samsung Galaxy Watch 4] Darbar1701:
That doesn't work anymore
[Samsung Galaxy Watch 4] berni502:
anymore? like after yestarday update? becouse i just did it like 2 days ago : p
[Samsung Galaxy Watch 4] Darbar1701:
After the new update
[Samsung Galaxy Watch 4] berni502:
omg nice
[Samsung Galaxy Watch 4] mahmoudgamaljemmy:
Just tried and it did not work, both phome amd watch are on one ui 4.0
[Samsung Galaxy Watch 4] mahmoudgamaljemmy:
I solved the issue! By clearing the storage of google play services again! The watch got diconnected again and had to make a reset for the watch to connect but this time the account got copied with no problems.
[Samsung Galaxy Watch 4] Marcelocohenarg:
Hi, when you say clearing the storage, do you mean clearing cache or everything? I can't sync my google account in the watch; never could, and I'm looking for solutions. My phone is a Xiaomi Mi 9. Thanks.
[Samsung Galaxy Watch 4] crosshelder:
I'm on the same problem with oneplus 9 pro. Can't find a way to add google account to the watch. It was working perfect but after update stop connecting with the galaxy wear app, so i did a reset to the watch. Now stuck on this problem
[Samsung Galaxy Watch 4] mahmoudgamaljemmy:
Everything! Not only cache, it didn't harm me in anyway. No account was logged out or anything
[Samsung Galaxy Watch 4] alfiter:
I have tried but on my xiaomi 9t it still does not work
[Samsung Gear S3] parasetam0l:
DEVELOPER NOTES :

Soldering USB and Odin USB mode: Done

Install Combination firmware (COMBINATION-FT30_R760XXU2CQL1): Done

Root Access (Combination firmware is pre rooted): Done

Build Tizen Kernel: Done

Upstream Tizen Kernel to latest (from 3.18.14 to 3.18.140): Done

Enable Android configs and disable some Samsung stuff on kernel: Done

Kernel cmdline patch for booting from mmc: Done

TWRP device tree: Done

Build TWRP: Done

MM (memory management) and FB (framebuffer) patch for IOMMU error: Done

PMIC patch for enabling USB: Done

Created fstab file: Done

Update Android Binder kernel driver: Done

Android Boots with ADB support: Done

USB Charging: Done

Mali T720 GPU Driver Update: Done

Decon Framebuffer: Done

S6E36W2X01 LCD Panel: Done

Compile AOSP9: Done

WearOS2 Port: Done

Broadcom 43102 Wifi and Bluetooth SDIO: Done

Palm to suspend: Done

Audio: Partially Fixed (Low sound level and quality)

HFP (Handsfree Protocol): Partially Fixed (Mic works, speaker distorted sound)

Brightness: Done

Vibration: Done

LSM6DSL Accelometer and Gyroscope Sensor: Done

TSL2584 Light Sensor: Done

PPS960 Heart Rate Sensor: Done

SSP Sensor Hub: Partially

Tap to Wake: Done

Always on display: Done

Bezel: Done

THINGS TO DO:

GPS

NFC

Offline charging

Step Counter

Power Optimizations (power.exynos5)

Audio and HFP (mixer_paths.xml)

SSP Sensor Hub

...

...

...

WearOS 3
[Samsung Gear S3] parasetam0l:
ls -l /dev/disk/by-partlabel

lrwxrwxrwx 1 root root 15 Jan 20 23:11 boot -> ../../mmcblk0p8
lrwxrwxrwx 1 root root 15 Jan 20 23:11 cm -> ../../mmcblk0p7
lrwxrwxrwx 1 root root 15 Jan 20 23:11 cpnvcore -> ../../mmcblk0p3
lrwxrwxrwx 1 root root 15 Jan 20 23:11 csa -> ../../mmcblk0p2
lrwxrwxrwx 1 root root 16 Jan 20 23:11 csc -> ../../mmcblk0p11
lrwxrwxrwx 1 root root 16 Jan 20 23:11 module -> ../../mmcblk0p10
lrwxrwxrwx 1 root root 15 Jan 20 23:12 param -> ../../mmcblk0p6
lrwxrwxrwx 1 root root 15 Jan 20 23:11 ramdisk1 -> ../../mmcblk0p5
lrwxrwxrwx 1 root root 15 Jan 20 23:11 ramdisk2 -> ../../mmcblk0p4
lrwxrwxrwx 1 root root 15 Jan 20 23:11 recovery -> ../../mmcblk0p9
lrwxrwxrwx 1 root root 16 Jan 20 23:11 rootfs -> ../../mmcblk0p14
lrwxrwxrwx 1 root root 16 Jan 20 23:11 steady -> ../../mmcblk0p15
lrwxrwxrwx 1 root root 16 Jan 20 23:11 system-data -> ../../mmcblk0p12
lrwxrwxrwx 1 root root 15 Jan 20 23:11 tup -> ../../mmcblk0p1
lrwxrwxrwx 1 root root 16 Jan 20 23:11 user -> ../../mmcblk0p13

(parted) print
print
Model: MMC FJX7AA (sd/mmc)
Disk /dev/block/mmcblk0: 3909MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number Start End Size File system Name Flags
1 4194kB 37.7MB 33.6MB tup
2 37.7MB 46.1MB 8389kB ext4 csa
3 46.1MB 48.2MB 2097kB cpnvcore
4 48.2MB 69.2MB 21.0MB ext2 ramdisk2
5 69.2MB 77.6MB 8389kB ext2 ramdisk1
6 77.6MB 86.0MB 8389kB param
7 86.0MB 89.1MB 3146kB cm
8 89.1MB 106MB 16.8MB boot
9 106MB 123MB 16.8MB recovery
10 123MB 139MB 16.8MB ext4 module
11 139MB 339MB 199MB ext4 csc
12 339MB 504MB 166MB ext4 system-data
13 504MB 2538MB 2033MB ext4 user
14 2538MB 3907MB 1369MB ext4 rootfs
15 3907MB 3907MB 262kB steady

I will use

system-data -> /recovery

csc -> /cache

user -> / (system as root)

rootfs -> /data
[Samsung Gear S3] parasetam0l:
UPDATE:

I am using

SM-R870_samsung-freshbl-freshbl-11-RWD1.210503.001-R870XXU1BUH9-user-release-keys.tar.gz

which is referenced from this post. It is Android 11 based WearOS 3. You can also find this file if you search on the internet. This is not a full firmware. Many files are missing. I think they dumped this from a factory device while it is running or they removed some files intentionally.

but I completed missing files for minimal booting. I also fixed Android's binder driver. Now device is booting to Android with working ADB. I can get logs from logcat. Very good!

Next thing is graphics driver. GW4 firmware does not include a surfaceflinger binary. So I built my own surfaceflinger with some modifications. Solis has Mali T720 MP1. I got this from ADB.

01-23 02:54:06.980 4377 4377 E mali : file /dev/mali0 is not of a compatible version (user 10.6, kernel 10.2)
01-23 02:54:06.986 4377 4377 E mali : ERROR: The DDK is not compatible with any of the Mali GPUs on the system.
01-23 02:54:06.986 4377 4377 E mali : The DDK was built for 0x720 r1p1 status range [0..15], but none of the GPUs matched:
01-23 02:54:06.989 4377 4377 E mali : file /dev/mali0 is not of a compatible version (user 10.6, kernel 10.2)
01-23 02:54:06.989 4377 4377 W libEGL : eglInitialize(0xf3b010a0) failed (EGL_NOT_INITIALIZED)
01-23 02:54:06.990 4377 4377 E libEGL : call to OpenGL ES API with no current context (logged once per thread)
01-23 02:54:06.990 4377 4377 F RenderEngine: eglQueryStringImplementationANDROID(EGL_VERSION) failed
01-23 02:54:06.991 4377 4377 F libc : Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 4377 (surfaceflinger), pid 4377 (surfaceflinger)

Things to check:

libGLES_mali.so (This is main driver library with many other files)
Mali T72x Kernel driver
[Samsung Gear S3] parasetam0l:
UPDATE:

I fixed USB charging and added ambient capabilities to kernel (which is needed for surfaceflinger and in general android).

So this error is gone:

capabilities requested but the kernel does not support ambient capabilities

I also updated tizen_arm MALI kernel drivers from r12p0 to arm r29p0. With proper libGLES_mali.so, DDK error is gone.

I tried to use Exynos 7570 hardware composer from several roms. Now I am facing a problem with lcd panel. LCD panel gives this error.

01-01 00:00:10.094 222 222 E HWComposer: getAttribute: getDisplayAttribute failed for display 0: BadParameter (4)
01-01 00:00:10.094 222 222 E HWComposer: getDisplayConnectionType: getDisplayConnectionType failed for display 0: Unsupported (8)

Because of this problems, I stopped porting WearOS and started building LineageOS from stratch. Before building process, I have to prepare a device tree. This repos are helpful for preparing device tree.

https://github.com/LineageOS/android_hardware_samsung
https://github.com/LineageOS/android_hardware_samsung_slsi_exynos5
https://github.com/LineageOS/android_hardware_samsung_slsi_exynos
https://github.com/LineageOS/android_hardware_samsung_slsi_exynos7580
https://github.com/LineageOS/android_hardware_samsung_slsi_libbt
https://github.com/LineageOS/android_kernel_samsung_universal7580
https://github.com/LineageOS/android_hardware_samsung_slsi_openmax
https://github.com/TO21Consortium/SGSWPlatform
[Samsung Gear S3] vazee00Buda:
Nice work, just keep going! Many of us are looking forward to this, perseverance!
[Samsung Gear S3] zswielder:
I've been following "the other thread" for years. I really like yours and the way you show progress and steps very clearly. I hope you'll succeed!
[Samsung Gear S3] ardonhs:
Great work!
[Samsung Gear S3] parasetam0l:
GOOOD NEWS AND BAD NEWS:

I successfully built a Lineage 18.1 rom. But due to massive HAL changes, framebuffer and hardware composer incompability, display was never worked. So I decided start from earlier Android version that we hope HWC is working. With the big help of this repository, I prepared an AOSP M build environment with custom surfaceflinger, samsung hardware, and solis device tree (with small changes on smdk7270 device tree). I also worked on kernel. Downgraded binder and mali drivers for Android M. Patched decon framebuffer, lcd and backlight. Built AOSP on Ubuntu 14. Time for good news.

GOOD NEWS: Hello Android on Gear S3 :)

View attachment 5555171

BAD NEWS: Nothing is working except display (touchscreen is also working) and USB. We have a lot of work to do. Now it is time to build and upgrade Android version by version.

I noticed that BEZEL is also working! I think it is working like a middle scroll button of a computer mouse. I did not tested too much. When you rotate bezel, A black mouse pointer comes to screen and page scrolls.
[Samsung Gear S3] adfree:
Not sure if you allready find something usefull inside AKI Source...

https://xdaforums.com/t/gear-s3-roo...ear-port-thread.3584588/page-39#post-79816730

SEC_Android_Independent_EVT0.0_E7270_BSP_KERNEL.tar.zip

SEC_Android_Independent_EVT0.0_E7270_BSP_u-boot.tar.zip

GitHub - naverlabs/aki: AKI open source repository

AKI open source repository. Contribute to naverlabs/aki development by creating an account on GitHub.

github.com

Only as info...

Best Regards
[Samsung Gear S3] lavasbey:
Hey, good work! I want to thank you @parasetam0l and @adfree for your hard work, just for a smartwatch that has begun to be forgotten.

I have a bit of experience in coding myself and I'll be ready for helping you in whatever testing you need. (After the soldering part is done and all the installation can be done without any -possible- physical damage)

I can't wait to use Wear OS in my watch, I've been reading and waiting for this to happen for sooo long :D
[Samsung Gear S3] Cryen:
Is there any significant difference in source code of the SM-R760 and SM-R770?

Only the first one was uploaded by Samsung and I have the second one.

If I'm not mistaken they are the frontier and classic models so they might be identical in firmware.
[Samsung Gear S3] parasetam0l:
Hello all,

I am trying to keep this topic as up to date as possible. Due to my job, I haven't been able to have enough time for this project for the last few weeks. But I am doing little things day by day.

@adfree

I looked at this repository. Only kernel and UBOOT source. It is also based AOSP 7. Nothing for Exynos 7270 specific device files. For now, no work needed for kernel side and we have combination SBOOT which allows booting Android. Thank you for your help.

@lavasbey

At this time no testing needed because of nothing to test :) I am heavily editing gpu and lcd drivers. When they are done, it will be impossible to physically damage to watch. With USB we can always flash our device even it is dead. For wireless download mode I can not promise anything :) If some testing needed, I will contact you. Thank you for your good wishes and wanting to help.

I will try to explain what I am doing and I want to reach.

As we know, WearOS is based on AOSP source, but its framework part is closed source. We can say that WearOS is 80% same as full Android. For porting WearOS, we need a donor device system dump. I have

Asus Zenwatch 2 dump: WearOS2 Android 6 (too old),

Mi Watch dump: WearOS2 H MR2 Android 9 (Chinese)

TicWatch Pro dump: WearOS2 H Android 9

Galaxy Watch 4 dump: WearOS3 Android 11.

To run WearOS on a new device:

Copy all system and ramdisk files from donor device to new device.

Replace device specific files (init, fstab, rc files, hardware libraries, vendor libraries, binaries etc which we got from our AOSP build)

Get screen, USB, ADB working and solve errors from logs.

Solve driver issues.

Porting WearOS gets easier after working AOSP on device. We can build necessary libraries from source and replace donor device's libraries with our compiled ones.

My first goal is make AOSP 9 working for porting WearOS2. Because latest WearOS2 based on Android H MR2. My next goal is make AOSP 11 working for WearOS3. We can not use smdk7270 or exynos7580 source directly on Android 9 or 11. Too much compile errors. So I will try to build AOSP version by version and solve problems step by step. We see that AOSP 6 is working. I also built AOSP 7 and it is also working.

After Android 8, things changed. Google divided hardware management to HALs, libraries and services. First stage mount, system as root, vndk system showed themselves. I am solving problems on device tree and samsung libraries for building newer AOSP. Whenever we run AOSP 8, it will be easier to reach AOSP 11 and WearOS3.

I just need some more time. Stay tuned for good news.
[Samsung Gear S3] parasetam0l:
Hello @Granat1,

As I discovered SM-R760 uses tizen_solis_defconfig, SM-R770 uses tizen_pop_defconfig. So their kernel configurations are different. I am working on SM-R760 for now so I am not 100% sure. But I know it's just like you said. They should have same hardware and firmware.

EDIT: I read from another thread, tizen_pop_defconfig may be using for SM-R600 (Samsung Gear Sport) and tizen_solis_defconfig is for SM-R760 and SM-R770 (Gear S3 frontier-classic). As I said I am not sure. I am using tizen_solis_defconfig for Gear S3 SM-R760.
[Samsung Gear S3] parasetam0l:
Finally,

Display drivers made me tired. I successfully ported Exynos7570 framebuffer and Mali gpu drivers. I replaced dummy LCD driver with LCD driver from Tizen kernel and solved compilation errors. I also patched decon for right RGB colors. Now display is working as expected. It still needs some operation for always on display but that's enough work for the screen for now.

I compiled AOSP9. As I said, with a working Android 9 porting WearOS 2 will get easier. Here is the proof :)

View attachment 5570925

I can not pass setup screen, because bluetooth is not working. Tizen's bluetooth initialization procedure is different than Android. Gear S3 uses Broadcom BCM43012. Now I am searching Android devices which use this chip then I will fix the bluetooth.
[Samsung Gear S3] Falcon68_:
dude you're doing a great job. Can't wait to flash WearOs on my device if it will be a thing in the future!
[Samsung Gear S3] pedromms86:
Dude, thanks a lot for your work! Amazing

I have a active 2 don't know about coding but I think it could work in R820 too ??
[Samsung Gear S3] parasetam0l:
Hello, thank you!

This work is Gear S3 (SM-R760, SM-R770) only. It will not work on other devices.

I took a quick look at the features of GWA2 (SM-R820). It has Exynos 9110 with Mali T720MP1 (which is the same as Gear S3). GWA2 also has USB connection (with soldering), SBOOT from combination firmware (necessary for booting something other than tizen) and kernel source (for android specific code). So yes, it is possible to port WearOS. Porting system part will be easy. Difficult part is porting drivers for example sensors.
[Samsung Gear S3] GyuminLeo:
Thanks for the great work!!

I am looking forward to this project and wishing you luck!

I am wondering if I can install this port for my device in the future? I have Gear S3 Frontier (SM-R765K) Korean version. Also do I need to solder the usb to the device? Or can I flash it via wireless connection?

Thanks for the good work and good luck!
[XPERIA X1 General] GermanGuy:
Anybody have any info on when we can expect the Xperia to launch on ATT?
[XPERIA X1 General] Insaneboy:
The official press release about US availability is going to be on the 3rd of november.
[Sony Xperia Pro-I] jagwap42:
I have an Xperia Pro I, china version, with all the google stuff added.

I am continually getting Podcast Addict APP being shut down by the system while I am listening to it. I think I have turned off all the options that allow this, with no success.

I have "excepted" the APP in the "Power saving feature" menus in the APP settings, and excluded Podcast Addict from the restricted APPs in the Battery menu, but it keeps getting added back in even with "Use Battery Manager" switched off.

Any thoughts how to get this thing to behave? I have never had an issue before.
[Sony Xperia Pro-I] jagwap42:
I found the issue.

I have the Chinese version, and buried in the bloatware, is an APP called Power Optimiser. It seems this is overriding all my choices in Settings. Disabling this APP on these APPs seems to have fixed it. If this continues to work I may remove the APP entirely.