yashsingh1/xdaforums huggingface dataset:
[Samsung Gear S2] adfree:
Puh... I am now on BOKK2... because EPK5 too many restrictions (for me)...

Examples...

This work easily on AOJ3 and now also with BOKK2

sdb root on
sdb shell
sh-3.2# whoami
root
sh-3.2# screenshot
"/opt/usr/media/Screenshots/Screen-20170515075700.bmp" saved
screenshot success

sh-3.2# testmode *#1234#
[libtbm:1801] bufmgr init: fd=18
[libtbm:1801] duplicate the drm_fd(18), bufmgr use fd(19).
[libtbm:1801] TBM module exynos4412: vendor="Samsung" ABI=1,1
[libtbm:1801] cache_crtl:TBM lock_crtl:TBM
[libtbm:1801] Success to load module(libtbm_default.so)
[libtbm:1801] create tizen bufmgr: ref_count:1
ERR<1801>:ecore_evas ecore_evas_extn.c:2202 ecore_evas_extn_plug_connect() Extn plug failed to connect:ipctype=0, svcname=elm_indicator_portrait, svcnum=0, svcsys=0

I need screenshot function and working testmode stuff and the other gadgets...

With EPK5 not possible for me at the moment... Maybe in future, if I am little bit smarter... okay maybe never happens...:D

BOKK2 Firmware allows this feature to init first time without Gear Manager enabled smartphone...

This thing with tapping at Logo/Icon...

AOJ3 not work so easy...

I was only able by luck to pressing and scratching some kind of weired Combination with 2 fingers... :eek:

I will check short if I can install Apps with SDB and with Platform and Partner Level signed...

Then I can desolder wires and play around...

With USB cable is not very comfortable to move the Watch...

I am ever scared to broke again wire(s)... :o

Best Regards
[Samsung Gear S2] adfree:
testmode *#774#	SSH MODE	ON/OFF
testmode *#1111#	FTA SW VERSION
testmode *#2222#	FTA HW VERSION
testmode *#12580*369#	Main Version
testmode *#2476633#	Air Mode
testmode *#09#	UN number
testmode *#7594#	SHUTDOWN APP ... menu
testmode *#251#	immer an glaub ich
testmode *#350#	keine Ahnung
testmode *#0002*28346#	keine Ahnung

testmode *#5231#	tests
testmode *#5232#	black screen
testmode *#5233#	black screen
testmode *#14789#	nix
testmode *#2664#	Touch Firmware Version
testmode *#8778378#	TSP Test mode ... Please insert SD :)
testmode *#4943#	HW id check
testmode *#5238973#	LCD Type	SDC_402015
testmode *#42662#	Brightness
testmode *#22235#	ccSensor Calibration
testmode *#6328378#	NFC test
testmode *#42663#	Brightness
testmode *#2288379#	FUELGAUGE REGISTER
testmode *#7547#	HIST_NV_LIST
testmode *#1232660#	keine Ahnung
testmode *#3366#	keine Ahnung
testmode *#46744674#	Factory Mode	ON/OFF
testmode *#12345#	Factory Mode
testmode *#3214789650#	keine Ahnung
testmode *#872564#	USB LOGGING
testmode *#746#	SVC DBG DUMP
testmode *#28346#	keine Ahnung
testmode *#33284#	Debug Setting menu UART etc..
testmode *#36633#	DEBUG MODE
testmode *#1105#	DFMS FAIL HISTORY
testmode *#2667653#	CONSOLE MODE
testmode *#9998*3288#	short output... keine Ahnung
testmode *#6472#	MISC	!!!!!!!!!!!!!
testmode *#84936#	Developer OPTION	ON/OFF
testmode *#87243#	USB ID
testmode *#8278#	UART menu
testmode *#232339#	WLAN TEST
testmode *#526#	WLAN TEST
testmode *#528#	keine Ahnung
testmode *#232338#	WLAN TEST ...more...
testmode *#533884#	Bluetooth Adaptive...
testmode *#533880#	SSP BT stuff... tests
testmode *#533883#	Bluetooth RF ... tests
testmode *#533881#	BT LE Testmode
testmode *#232331#	BT
testmode *#232337#	BT Address
testmode *#8736364#	keine Ahnung
testmode *#23646#	Software Version + Overheat...
testmode #23646*	keine Ahnung
testmode *#0000#	Software version
testmode *#273283*255*3282*#	max. 300 messages created...
testmode *#9876#	max. 300
testmode *#273283*255*663282*#	keine Ahnung
testmode *#3282*727336*#	keine Ahnung
testmode *#737425#	SN
testmode *#9920#	CSC verifier
testmode *#2218#	Battery status
testmode *#272*719434266344#	CSC Preconfig	!!!!!!!!
testmode *#0782#	RTC TIME
testmode *#9999#	Version info
testmode *#4327#	Connection Status
testmode *#0482#	Sensor Hub
testmode ##564#	keine Ahnung
##366633#	keine Ahnung
##7764726	keine Ahnung
testmode *#2627#	keine Ahnung
testmode *#107#	enable accessibility menu
testmode *#2788378#	CPU stability test
testmode *#272886*0#	keine Ahnung

Tested today few testmode Commands with BOKK Firmware...

Later I could add Screenshots...

Best Regards
[Samsung Gear S2] adfree:
Before I go to my bed...

Few tests with Shell scripts... *.sh

sh-3.2# wifi-direct-dhcp.sh
Target is REDWOOD and interface p2p: .
wifi-direct-dhcp.sh [server] [client] [stop] [status]

This looks interesting...

sh-3.2# wifi-direct-server.sh
wifi-direct-server.sh [start] [stop] [status]

Need more time... will check if my SM-Z130H or RD-PQ have something similar...

Best Regards

Edit 1.

sh-3.2# wifi-direct-server.sh start
method return sender=:1.0 -> dest=:1.336 reply_serial=2
object path "/org/freedesktop/systemd1/job/3472"

sh-3.2# wifi-direct-dhcp.sh server
Target is REDWOOD and interface p2p: .
/usr/sbin/udhcpd: no process found
interface(p2p) is not up

sh-3.2# wifi-direct-dhcp.sh client
Target is REDWOOD and interface p2p: .
/usr/sbin/udhcpd: no process found
interface(p2p) is not up

sh-3.2# wifi-direct-dhcp.sh status
Target is REDWOOD and interface p2p: .
/usr/bin/udhcpc is not running
/usr/sbin/udhcpd is not running

Edit 2.

sh-3.2# udhcpc --help
usage: udhcpc [-fbnqvoCRB] [-i IFACE] [-r IP] [-s PROG] [-p PIDFILE]
[-H HOSTNAME] [-V VENDOR] [-x OPT:VAL] [-O OPT]

Configure network dynamicaly using DHCP.

-i Interface to use (default eth0)
-p Create pidfile
-s Run PROG at DHCP events (default /usr/share/udhcpc/default.script)
-B Request broadcast replies
-t Send up to N discover packets
-T Pause between packets (default 3 seconds)
-A Wait N seconds after failure (default 20)
-f Run in foreground
-b Background if lease is not obtained
-n Exit if lease is not obtained
-q Exit after obtaining lease
-R Release IP on exit
-S Log to syslog too
-a Use arping to validate offered address
-O Request option OPT from server (cumulative)
-o Don't request any options (unless -O is given)
-r Request this IP address
-x OPT:VAL Include option OPT in sent packets (cumulative)
-F Ask server to update DNS mapping for NAME
-H Send NAME as client hostname (default none)
-V VENDOR Vendor identifier (default 'udhcp VERSION')
-C Don't send MAC as client identifier
-v Verbose

Signals:
USR1 Renew current lease
USR2 Release current lease

udhcpc: Unknown option help

sh-3.2# udhcpd --help
Usage: udhcpd [-fS] [-P N] [CONFFILE]

-f Run in foreground
-S Log to syslog too
-P N Use port N (default 67)
udhcpd: Unknown option help
[Samsung Gear S2] adfree:
sh-3.2# pkg --help
pkg: unrecognized option '--help'
========================================================
Package manager tool version: 1.0.0
Copyright (C) 2013-2014 - Application framework team
--------------------------------------------------------
Usage:
pkg [-l|--list]
[-i|--install <path>]
[-u|--uninstall <pkgid>]
[-e|--enable <pkgid>]
[-d|--disable <pkgid>]
[-m|--move <pkgid>]
[-c|--csc]
[-f|--filter <key> <value>]
[-t|--api-test <1~5>]
[-k|--keep-data <file|path>]
[-v|--keep-vconfkey <vconfkey>]
[-r|--recover-data <path>]
[-b|--broadcast <pkgtype> <pkgid> <key> <value>]
[--launch <appid>]
--------------------------------------------------------
Example:
pkg -l
pkg -i /opt/usr/media/com.samsung.hello_0.1.2_armv7l.tpk
pkg -i /opt/usr/media/watchface-result.xml -x pkgid -y lable
pkg -i /opt/usr/media/watchface-preview.png -x pkgid
pkg -u com.samsung.hello
pkg -e com.samsung.hello
pkg -e com.samsung.hello:org.tizen.testapp
pkg -d com.samsung.hello
pkg -d com.samsung.hello:org.tizen.testapp
pkg -m com.samsung.hello
pkg -c
pkg -f category http://tizen.org/category/ime
pkg -t 1
pkg -k /opt/usr/dbspace
pkg -k /opt/usr/dbspace/.spd_service.db-journal
pkg -v db/private/wifi/wearable_wifi_use
pkg -r /opt/system/softreset_preserved
pkg -b rpm com.saung.hello start uninstall
========================================================
spend time is [11]ms

This is how to start app by ID... aka "folder name"

sh-3.2# launch_app com.samsung.wemail
... successfully launched

This is how I can kick off this app from database...

sh-3.2# pkg -d com.samsung.wemail
disable broadcast_pkgid_list : :com.samsung.wemail:
spend time is [127]ms

Not tested if Gear Manager detect changed stuff...

Best Regards
[Samsung Gear S2] adfree:
Found interesting mix of infos in this Youtube Video...

https://www.youtube.com/watch?v=3bDqTQhzWh0

In main it could be usefull, to see how netOdin work.

If I found English Videos Odin related... I will add...

Best Regards
[Samsung Gear S2] adfree:
If I have time, I will check "arguments" for reboot command...

Short found in Kernel...zImage

COMBINATION-FTMA_R732XXXU2AOI8

fota
fota_bl
wdownload
wdownload_update
download
upload
wupload
secure
silent
swsel
sud
emergency

Not all tested yet... be carefully...

Rebooting with argument...

Best Regards
[Samsung Gear S2] adfree:
Since my first activities with Gear Manager and paired SM-R732...

I was never able to check for Firmware... FOTA

Today I spend few hours to solve this "problem"... :rolleyes:

Idea 1...

I thought because my SM-R732 is rooted...

Okidoki... Flashed Orignal Stock Firmware...

No success... f. Gear Manager not connect to FOTA Server... Error

Idea 2.

Aha...

Maybe because my GT-I9300 is rooted too

Several attempts to unroot...

F&%$ Gear Manager not connect to FOTA Server and check for update with my NOT rooted Gear and NOT rooted (hided su) Android handset...

Okidoki...

Idea 3 to 10...

My GT-I9300 have no valid IMEI...

no

My GT-I9300 is Live Demo Unit... maybe...

no

Several attempts to look into log files...

Hmmmm.

Maybe because no SIM card is inside... :confused:

Okidoki...

I took my second SIM card from my SM-Z130H... because first attempt with not Micro SIM card.... :D :rolleyes: :o

And yes...

This was the reason...

F&$$§%%%%ing Gear M. require mandatory SIM card inside... inside the GT-I9300 to update the f.ing Gear... :cyclops:

Okidoki...

Firmware on SM-R732 was R732XXU2AOJ3

[com.sec.accessory.fotaprovider.socket.request.SocketResultGetDeviceInfo(33/setContent)] [GEARINFO]R732XXU2AOJ3/R732OXX2AOJ3/

Downloaded package is 150 MB big...

I was to stupid to find the Link... to ... bin

But final result is stored here, as update.zip in:

/storage/emulated/0/afota/update.zip

According to sboot.bin inside... it could be:

R732XXU2DPFB

At the moment I will not update yet... to prevent trouble to downgrade Bootloader...

I will try to collect more infos...

Where local FOTA test is on SM-R732... path etc...

With my SM-Z130H I did long time ago few experiments...

And rooted Firmware was updated with FOTA/delta package... and ROOT not removed...

Will see how it work on SM-R732...

Best Regards
[Samsung Gear S2] adfree:
Today I was drunken enough to check Bootloader sboot.bin downgrade.

Without soldered wires/USB cable... only WiFi

Little tiny little problem... you need ROOT... :rolleyes:

I have flashed back my Combination Firmware R732XXU2AOJ2...

To check Bootloader Version on Gear Wearable:

cat /proc/cmdline

sh-3.2# cat /proc/cmdline
console=ram loglevel=4 root=/dev/ram0 rw initrd=0x42000000,8M bootmode=ramdisk pwron.reason=ap:pinrst,pmic:pwron sec_debug.enable=0 sec_debug.enable_user=0

sec_watchdog.sec_pet=5
sec_log=0x200000@0x46000000 sec_tima_log=0x200000@0x46202000 lcdtype=402015 oops=panic pmic_info=83 sysscope=0xee000000 cordon=c14026785626324ad4bb4d2dcd80f0cb

warrantybit=1 serial
no=4100ed7b5567828b tizenboot.sec_atd.tty=/dev/ttySAC1 tizenboot.emmc_checksum=0 tizenboot.odin=0 bootloader.ver=R732XXE2BOJ2 bootloader.fb=0x48000000

bootloader.log=0x13ee@0x46000
000 bootloader.elapsed=2318

On my device was BOJE2 Bootloader aka sboot.bin

Steps to downgrade.

1.

mkdir /opt/usr/media/Others

2.

sdb push sboot.bin /opt/usr/media/Others
pushed sboot.bin 100% 1MB
1 file(s) pushed. 0 file(s) skipped.
sboot.bin 409 KB/s (1410304 bytes in 3.359s)

3.

sh-3.2# dd if=/opt/usr/media/Others/sboot.bin of=/dev/mmcblk0p1
2754+1 records in
2754+1 records out
1410304 bytes (1.4 MB) copied, 0.316914 s, 4.5 MB/s

3.1

You can check if written correct... but not really necessary... IMHO sboot makes self check...

So you can not flash not signed nonsense... I think...

sh-3.2# dd if=/dev/mmcblk0p1 of=/opt/usr/media/Others/bota0.bin
8192+0 records in
8192+0 records out
4194304 bytes (4.2 MB) copied, 0.29215 s, 14.4 MB/s

4.

sh-3.2# reboot fota_bl
Rebooting with argument 'fota_bl'.

Now my Gear S2 reboot... and after finished correct Booting... :victory:

5.

sh-3.2# cat /proc/cmdline
console=ram loglevel=4 root=/dev/ram0 rw initrd=0x42000000,8M bootmode=ramdisk pwron.reason=ap:swrst,pmic:pwron sec_debug.enable=0 sec_debug.enable_user=0

sec_watchdog.sec_pet=5 se
c_log=0x200000@0x46000000 sec_tima_log=0x200000@0x46202000 lcdtype=402015 oops=panic pmic_info=83 sysscope=0xee000000 cordon=84c53094a349bafd818cd9671981ac4a

warrantybit=1 serialno
=4100ed7b5567828b tizenboot.sec_atd.tty=/dev/ttySAC1 tizenboot.emmc_checksum=0 tizenboot.odin=0 bootloader.ver=R732XXU2AOJ3 bootloader.fb=0x48000000

bootloader.log=0x10c9@0x460406f
5 bootloader.elapsed=2158

:cool:

I have now Bootloader from AOJ3 on my SM-R732...

:cool:

Best Regards
[Samsung Gear S2] adfree:
Today I have flashed Tizen 3 Image:

tizen-wearable_20170403.2.20170404.044936_wearable-wayland-armv7l-tw1.tar.gz

I have decompressed *.gz and used only *.tar file with NetOdin3...

My Gear S2 is alive and boot into Tizen 3... :good:

So really only Kernel related... no additional U-Boot Bootloader required.

Only 1 sideeffect yet...

I can not enable WiFi... :o

So I can not take Screenshots...

Will later check if BT work...

Now I will download Tizen 4 Images... maybe more luck...

Best Regards

Edit 1.

:rolleyes:

Okidoki...

Download (wireless) Option shows only Gear S2 Logo...

So I need to solder my wires again... before I am able to flash other Tizen Firmware...

In Download (usb) I can see:

K:Custom
P:Custom

Really interesting...

I have no idea. if attempts with Open Source Kernel leads to same result...

:confused:

I mean these stuff:

http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=SM-R732

Is this safe usable, or will this also deactivate WiFi...
[Samsung Gear S2] adfree:
After soldering wires...

I have flashed successfully Tizen 4 Image:

tizen-unified_20170529.1.20170530.011650_wearable-wayland-armv7l-tw1.tar.gz

Again decompressed to TAR file...

Hmmm.

Still I can not use WiFi...

This time I can activate WiFi, but I can see text WiFi disabled... :rolleyes:

Also little problem to connect MTP... and SDB... and... :rolleyes: :D

1 wire lost connection...

Need to resolder...

Anyway.

I think WiFi problem remembers me on RD-PQ... so I am sure it is not mistake or incompatibilty... something is missing...

MTP I have solved with my RD-PQ only by correct RPM:

https://xdaforums.com/showpost.php?p=69873112&postcount=82

And WiFi only by follow instruction:

https://xdaforums.com/samsung-tizen/development/wifi-issue-tizen-2-3-rd-pq-m0-t3088577

New is... I can not access via SDB... :D

So I have no chance to install something...

Hopefully I can fix SDB or find Image where SDB is working... by mistake... :D

Also not new is... how to make Screenshot... on Wayland... :rolleyes: :rolleyes:

Best Regards
[Samsung Gear S2] adfree:
Hmmm...

Maybe this time because my soldering... :rolleyes:

after wire 1... few minutes later I lost also second wire... :o

After resolder...

SDB work... :cool:

MTP looks also possible...

Not tested to transfer something... but folders etc. looks valid...

First search via SDB for Shell script *.sh

So I have short tested...

bash-3.2# wifi-direct-dhcp.sh
Target is TM1 and interface p2p: p2p0.
wifi-direct-dhcp.sh [server] [client] [stop] [status]
bash-3.2# wifi-direct-dhcp.sh server
Target is TM1 and interface p2p: p2p0.
RTNETLINK answers: Operation not supported
got config : start : 192.168.49.20
got config : end : 192.168.49.40
got config : max_leases : 20
got config : notify_file : /usr/bin/dhcpd-notify.sh
got config : lease_file : /opt/var/lib/misc/dhcpd.leases
got config : option : value : 255.255.255.0 : subnet
got config : option : value : 192.168.49.1 : router
got config : option : value : 864000 : lease
got config : option : value : 192.168.49.255 : broadcast
toybox dhcpd started
dhcpd: Failed to get interface p2p0

bash-3.2# wifi-direct-dhcp.sh status
Target is TM1 and interface p2p: p2p0.
/usr/bin/dhcp is not running
/usr/sbin/dhcpd is not running
bash-3.2# wifi-direct-dhcp.sh client
Target is TM1 and interface p2p: p2p0.
RTNETLINK answers: Operation not supported
bash-3.2# dhcp started
dhcp: Failed to get interface p2p0

bash-3.2# wifi-direct-dhcp.sh server
Target is TM1 and interface p2p: p2p0.
RTNETLINK answers: Operation not supported
RTNETLINK answers: File exists
got config : start : 192.168.49.20
got config : end : 192.168.49.40
got config : max_leases : 20
got config : notify_file : /usr/bin/dhcpd-notify.sh
got config : lease_file : /opt/var/lib/misc/dhcpd.leases
got config : option : value : 255.255.255.0 : subnet
got config : option : value : 192.168.49.1 : router
got config : option : value : 864000 : lease
got config : option : value : 192.168.49.255 : broadcast
toybox dhcpd started
dhcpd: Failed to get interface p2p0

bash-3.2# wifi-direct-dhcp.sh server
Target is TM1 and interface p2p: p2p0.
RTNETLINK answers: Operation not supported
RTNETLINK answers: File exists
got config : start : 192.168.49.20
got config : end : 192.168.49.40
got config : max_leases : 20
got config : notify_file : /usr/bin/dhcpd-notify.sh
got config : lease_file : /opt/var/lib/misc/dhcpd.leases
got config : option : value : 255.255.255.0 : subnet
got config : option : value : 192.168.49.1 : router
got config : option : value : 864000 : lease
got config : option : value : 192.168.49.255 : broadcast
toybox dhcpd started
dhcpd: Failed to get interface p2p0

bash-3.2# wifi-direct-dhcp.sh client
Target is TM1 and interface p2p: p2p0.
RTNETLINK answers: Operation not supported
bash-3.2# dhcp started
dhcp: Failed to get interface p2p0

In theory this Tizen 4 Image should be dotNet capable...

I have only no dotNet example... :o

Best Regards
[Samsung Gear S2] tids2k:
Thats good news. So sboot.bin can be flashed thru combination software ?
[Samsung Gear S2] adfree:
Few Tizen 4 "tests"...

[B]sdb capability[/B]
secure_protocol:disabled
intershell_support:enabled
filesync_support:pushpull
usbproto_support:enabled
sockproto_support:enabled
syncwinsz_support:enabled
sdbd_rootperm:disabled
rootonoff_support:enabled
encryption_support:disabled
zone_support:disabled
multiuser_support:enabled
cpu_arch:armv7
sdk_toolpath:/home/owner/share/tmp/sdk_tools
profile_name:wearable
vendor_name:Tizen
can_launch:unknown
[B]platform_version:4.0[/B]
product_version:unknown
sdbd_version:2.2.31
sdbd_plugin_version:unknown
sdbd_cap_version:1.0
log_enable:disabled
log_path:/home/owner/share/sdbdlog
appcmd_support:enabled
appid2pid_support:enabled
pkgcmd_debugmode:enabled

I have logged why WiFi not work...

Need some time to understand...

:rolleyes:

I hope really it is similar to RD-PQ WiFi problem long time ago... I have fixed this from nice Tutorial and created my own Batch file:

sdb root on
sdb push wlandrv-plugin-tizen2.1-bcm43xx-1.0.4-1.armv7l.rpm /home
sdb push usleep-1-4.1.armv7l.rpm /home
sdb shell rpm -ivh --force --nodeps /home/*.rpm
Pause
sdb shell ln -s /usr/sbin/modprobe /sbin/modprobe
sdb shell ln -s /usr/sbin/rmmod /sbin/rmmod
sdb shell /usr/bin/wlan.sh start
sdb shell /usr/sbin/wpa_supp.sh start

Now I need to find correct RPMs for my Gear S2...

Best Regards
[Samsung Gear S2] adfree:
Download (wireless) also not work... if I have TIzen 3 or 4 on my SM-R732...

Maybe reason could be inside this file/image...

ramdisk.img

Will try what happens if I flash with Odin this file from Retail Firmware... maybe also Kernel required...

I will see...

Best Regards

Edit 1.

Flashed ramdisk.img from AOJ3 only... Tizen 4 not boot... I hear only Vibrator... and can see Gear S2 Logo

Download (wireless" still not work... I see only Gear S2 Logo

Will try to investigate what is inside ramdisk...

Edit 2.

Flashed ramdisk.img from working Tizen 3 package...

Tizen 4 boot correct...
[Samsung Gear S2] adfree:
I have searched for this answer around 6 months... :rolleyes:

How to make screenshots under Tizen 3 "Wayland"... now same problem under Tizen 4... :rolleyes: :rolleyes:

But today I solved this. :angel:

With SDB simple Command:

enlightenment_info -dump_topvwins /opt/usr/home/owner/media/Images

:victory:

Now I can show few Screenshots from Tizen 3 and Tizen 4... on my SM-R732...

:D

Best Regards
[Samsung Gear S2] tids2k:
How did you install those apps [MENTION=1030585]adfree[/MENTION] i could not get anything installed. Did you try to connect the watch to samsung gear app after installing tizen ?
[Samsung Gear S2] adfree:
All apps on Screenshots are allready preinstalled.

I have not installed any apps in Tizen 3 nor Tizen 4...

Remember Samsungs Security policy... with 100000 different Certificates...

Firmware for Reference/Test Devices have not same Certificates preinstalled like Commercial Device and versa vie...

To bypass this funny "protection"...

Variant A.

Sign again with Hashsigner

or Variant B.

Add commercial Certs and edit fingerprint...xml

Before I install any apps I have to manage how to add WiFi Driver... :rolleyes:

Looks like this time no RPM available... :silly:

So I have to copy & paste WiFi related files manualy...

For instance wlan.sh is not inside...

Best Regards

Edit 1.

Copied few files from Retail Firmware... but have few forgotten...

sh-3.2# wlan.sh
sh: /usr/bin/wlan.sh: Permission denied
sh-3.2# cd /usr/bin
sh-3.2# chmod +x wlan.sh
sh-3.2# wlan.sh
wlan.sh [start] [stop] [softap] [p2p] w [rftest]
sh-3.2# wlan.sh start
/usr/bin/wlan.sh: line 5: /usr/bin/wifi-loader: No such file or directory

Edit 2.

sh-3.2# cp wifi-loader /usr/bin
sh-3.2# wlan.sh start
/usr/bin/wlan.sh: line 5: /usr/bin/wifi-loader: Permission denied
sh-3.2# chmod +x /usr/bin/wifi-loader
sh-3.2# wlan.sh start
sh-3.2#

Looks like I have managed to get WiFi... :cool: :victory:

Need few tests...

But after added wifi-loader... wlan.sh start work. :good:

I was able to find AP and connect after Password...

Later I will try transfer of files... ehm I mean any kind of Wifi test...

Btw.

I saw file in /usr/bin folder:

wireless-download

If this is what I think it is...

Then maybe more clear why Download (wireless) is deactivated... :rolleyes:

Best Regards
[Samsung Gear S2] tids2k:
I might buy my watch back next week. Will continue to check.

Please also check if you can connect to samsung gear with vanilla tizen os.

---------- Post added at 03:02 PM ---------- Previous post was at 03:01 PM ----------

I have backup of some apps as .wgt if you want i will send and u can try ?

---------- Post added at 03:04 PM ---------- Previous post was at 03:02 PM ----------

This is very good news. You are heading in the right direction. If we have tizen os on the watch with tizen store ;) thats it. Mission accomplished.
[Samsung Gear S2] adfree:
Few days ago I have tried...

But Samsung Gear aka Gear Manager app not work with Tizen 3 nor Tizen 4...

They ever make funtastic big difference between Commercial Final Firmware... and Tizen Images for Development...

:good:

Yes please.

Write me PM with Link for Download.

So I can test Installation on Tizen 4...

Will try my few Backups in next few days...

Mission for this week.

1.

Add Hashsigner... to Tizen 4...

To sign also with SM-R732...

Should be easy to manage...

I hope... :D

2.

I will try to install few apps from Tizen repo... RPM...

Maybe something nice I can find...

3.

Very cool would be.

If I can find all puzzle parts for Download (wireless).

Or maybe I am able to find minimal incredients for Download (wireless)... to have chance to use netOdin... for update or to rollback to Retail Firmware...

So I can desolder wires for better testing...

My WiFi solution work... tested with SDB. :cool:

Also after Reboot WiFi connect to my Access Point. :good:

Best Regards