yashsingh1/xdaforums huggingface dataset:
[Samsung Gear S] chiikko561:
Guys I'm afraid I have stumbled upon a bit of news in the Gear 2 thread...

[quote name="tooandrew" post=63086714]@<a href="http://xdaforums.com/member.php?u=803006" target="_blank">biktor_gj</a> have you hit a wall with the camera functionality? No go on that?<br />

<br />

<br />

I'm affraid what I have is lost. I have lost one of the hard drives in my PC, and with that I've lost:<br />

<br />

* All the work in progress stuff I've done with the Gear S (the entire cyanogenmod tree and the kernel changes including bluetooth fixes and the display tests)<br />

* The AOSP tree work done for the Gear 2<br />

* Google Glass image I was working on for the Gear 2<br />

At least I managed to save the reference kernels and most of the things I use to build the images for the gear 2...<br />

About the camera, yes, I've lost hope on making the camera work. I know it *can* work, but I don't have the necessary knowledge to make the Android libraries work. Unfortunately, I have to start over with the rest of the stuff I was working on...

---------- Post added at 09:29 AM ---------- Previous post was at 09:23 AM ----------

Here is link to Original post by Biktor http://xdaforums.com/showthread.php?p=63116849
[Samsung Gear S] Kirrrr:
We MUST wait.

;)
[Samsung Gear S] gidi:
<br />

<br />

I'm affraid what I have is lost. I have lost one of the hard drives in my PC, and with that I've lost:<br />

<br />

* All the work in progress stuff I've done with the Gear S (the entire cyanogenmod tree and the kernel changes including bluetooth fixes and the display tests)<br />

* The AOSP tree work done for the Gear 2<br />

* Google Glass image I was working on for the Gear 2<br />

At least I managed to save the reference kernels and most of the things I use to build the images for the gear 2...<br />

About the camera, yes, I've lost hope on making the camera work. I know it *can* work, but I don't have the necessary knowledge to make the Android libraries work. Unfortunately, I have to start over with the rest of the stuff I was working on...

---------- Post added at 09:29 AM ---------- Previous post was at 09:23 AM ----------

Here is link to Original post by Biktor http://xdaforums.com/showthread.php?p=63116849

[MENTION=803006]biktor_gj[/MENTION] Can you please confirm this bad luck? OMG dude take your time with the build. It is so frustrating to lose your work!!!
[Samsung Gear S] biktor_gj:
[MENTION=803006]biktor_gj[/MENTION] Can you please confirm this bad luck? OMG dude take your time with the build. It is so frustrating to lose your work!!!

Yepp, unfortunately it happened. There was a storm where I live last thursday, and power went down a few times while I was at work. Of course I always leave the computer up, either compiling something or just to be available in case I have time to work on something. When I turned it on the following day I noticed my vm was running erratically and though 'this smells bad', and true, it smelled like another seagate drive f***d up.

On one side, my bad for not having the backups running, on the other side, if I had maybe my server would have been hit too, so not too sure if I was still lucky on not having lost 4.4 tb of data :)

As a result of this, regarding the Gear S, I've lost:

Everything since the last github commit. That means bluetooth and any wlan progress I had done, along with a lot of tests with the display driver. Bluetooth is easy to fix since I know what I did, display driver will take most of the hit kernel side since I think I had it almost working except for some issues with the irq driver.

The entire AOSP tree, with everything I had advanced for both the Gear 2 and the Gear S. I'm working on a parallell device tree config for AOSP, hoping to produce compatible libraries to port them to Android Wear without all the cyanogenmod code (specially what relates to libui and libhwui). This I have to start over. Moral of the story? Better loose some cycles with a rsync backup running every day than risk it again... Will keep you posted!
[Samsung Gear S] gidi:
[MENTION=803006]biktor_gj[/MENTION] we love you man! Love your attitude and your determination. Keep it up my friend!
[Samsung Gear S] choong001:
gear s can't back to tizen

hi !anybody can send me the {sysdata.tar},i want to flash back tizen:crying:
[Samsung Gear S] Beukhof1:
[QUOTE="biktor_gj, post: 63148557, member: 803006"][MENTION=803006]biktor_gj[/MENTION] Can you please confirm this bad luck? OMG dude take your time with the build. It is so frustrating to lose your work!!!

Yepp, unfortunately it happened. There was a storm where I live last thursday, and power went down a few times while I was at work. Of course I always leave the computer up, either compiling something or just to be available in case I have time to work on something. When I turned it on the following day I noticed my vm was running erratically and though 'this smells bad', and true, it smelled like another seagate drive f***d up.

On one side, my bad for not having the backups running, on the other side, if I had maybe my server would have been hit too, so not too sure if I was still lucky on not having lost 4.4 tb of data :)

As a result of this, regarding the Gear S, I've lost:

Everything since the last github commit. That means bluetooth and any wlan progress I had done, along with a lot of tests with the display driver. Bluetooth is easy to fix since I know what I did, display driver will take most of the hit kernel side since I think I had it almost working except for some issues with the irq driver.

The entire AOSP tree, with everything I had advanced for both the Gear 2 and the Gear S. I'm working on a parallell device tree config for AOSP, hoping to produce compatible libraries to port them to Android Wear without all the cyanogenmod code (specially what relates to libui and libhwui). This I have to start over. Moral of the story? Better loose some cycles with a rsync backup running every day than risk it again... Will keep you posted!

That suck dude. I lost a disk once during a power outage. It's really not cool to loose data.

I just ordered a Gear S because you are porting cm to it. Will you continue your work? Otherwise i think i will cancel my order.
[Samsung Gear S] djsmeegy:
Ohh...

Damn, that really sucks.

But sh*t happens.

I hope - and don't think I'm the only one - you will not give it up [MENTION=803006]biktor_gj[/MENTION], for many of us you're the only hope we can use our Gear S...

Bcoz you can only full fill their potential! :)

In the other hand I will sell them.
[Samsung Gear S] biktor_gj:
Why does everyone think I'm going to quit? I never said that! I'm only saying I have to redo a lot of stuff, but I'm not giving up! Relax ;)
[Samsung Gear S] andrew.mackew:
Thanks mate! You rock! :good:
[Samsung Gear S] t2bacdp:
Thank a lot. If you need help, I'm here, not an expert and I use Gear S everyday :/
[Samsung Gear S] djsmeegy:
Thanks biktor!!! Thanx a lot :)
[Samsung Gear S] Beukhof1:
Your the best!

Are you anywhere close to start development again? I dont know much about rom building and stuff but flashing and testing and im your man!
[Samsung Gear S] runningwarrior08:
I am just having terrible luck. Got a T mobile version in today and of course it isn't clean ESN like the seller said.. Yay.

What versions are you guys using. I know the T model works, has anyone tried W which is the international unlocked version?
[Samsung Gear S] biktor_gj:
Getting back in business

[MENTION=2532582]runningwarrior08[/MENTION] I'm using a generic SM-R750, though in the box it stated SM-R750Z or something like that... Generic unlocked GSM version, don't know about T-mobile ones though...

[MENTION=535343]all[/MENTION]

I have rebuilt my development environment for Cyanogenmod, and slowly trying to make it compile the AOSP tree. Given that I already had a good mess, I decided to spend a little more time making it easier to build bootable images out of the cyanogenmod build system. I've started with the kernel, which is the most involved process, I will slowly go making changes to the rest of the build process and try to make it build everything automatically so a simple "make" in CM's source produces a fully flashable image.

So, to begin with the automatic building, I've made some small modifications to the kernel tree to allow full building and packing without needing to have the entire Samsung build environment standing there, and to avoid needing to chroot to some random folder just to build a kernel. I've placed two scripts on top of the kernel tree. This includes the mkdzimage binary blob from samsung, its' libraries, and a precompiled dtbtool binary placed at buildDeps/ directory on top of the kernel source. I also modified some scripts to automate it a little more.

To build a kernel:

Step 0: Install a gcc toolchain, and qemu on your development machine. Without the gcc toolchain you won't be able to compile anything, without qemu you won't be able to run mkdzimage, which is required to make a bootable dzImage

Step 1:run fixLibs.sh. Run it before compiling the first time, this will put the libraries required by 'mkdzimage' at /lib so the tool can run.

Step 2: Make sure your gcc toolchain is available as make "arm-linux-gnueabi-*" If it's not, adjust the "buildKernel" script at the line where it says make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- and rename the CROSS_COMPILE parameter to your toolchain.

Step 3: run ./buildKernel . This will compile the entire kernel source, then run the dtbTool for you, pack the zImage + merged-dtb and put it in a tar file named GearS_Kernel___[DATE].tar at the top of the kernel tree.

The rest of the times just running buildKernel will be enough to get a new build.

Now to re-fix bluetooth and get back to work on the screen and wifi...

Have a good day!
[Samsung Gear S] t2bacdp:
Hello biktor_gj, thanks for all.

I have a Nexus 5 and I install TWRP Multirom, do you think that it could be port to Gear S to keep Tizen for everyday and CM12 for test?
[Samsung Gear S] biktor_gj:
There's not enough space in 4Gb of flash to keep both OS at the same time. Also, the kernels are completely different and incompatible with each other so... not possible in any way.
[Samsung Gear S] Beukhof1:
Just wanted to thank you for all the time you put in this project. Thank you!

Can't wait to try it with working wifi.
[Samsung Gear S] biktor_gj:
Well, I have been carrying the watch all day, just letting it idle and looking if it still was alive some times, and I must admit that battery is not that bad.

Not a scientific test by any means, but check the different battery stats to get a glimpse of what you can get with telephony enabled and almost zero use...

View attachment 3503421 View attachment 3503422 View attachment 3503423

** All photos are from today at different times, without charging the watch at any time. If you keep the display on battery goes down quite fast, but if you leave it suspended it's relatively good. It is a bit less than what you can get in Tizen with telephony enabled, but not much less after all, so not that bad.

Note: Display isn't fixed, I just moved the problem somewhere else and now I don't have video and have video corruption on overlays but suspend and resume work correctly, so I can actually measure the watch power consumption having it idle, suspended and on cpu collapse modes.

I fixed bluetooth again by the way, tomorrow I'll update the github repo ;)
[Samsung Gear S] Beukhof1:
Wow that looks great!! Will you be building twrp flashable zips for us testers?
[Samsung Gear S] :
Cool look nice !!!!!!?????

I'll stay on on the beta 's

I have No interest in going back to tizan

Been waiting for this since I brought the GearS

Have u made any progress on the WiFi? ??
[Samsung Gear S] gidi:
Eagerly waiting for a beta release! You sir, are one of a kind.

If (when i dare say) you fix WiFi and screen suspend do you think it would be a good time for a user beta that we can f;lash via Odin or TWRP?
[Samsung Gear S] hurdlejade:
I'm afraid once this rom is more stable and finsihed, the price of Gear S will be higher than S2 ;)
[Samsung Gear S] gidi:
Go out and shop for one while you can!
[Samsung Gear S] drkfngthdragnlrd:
T-Mobile has Certified Pre-Owned for $199.99, aka $0 down and $8.34 a month.

http://www.t-mobile.com/internet-devices/samsung-gear-s-certified-pre-owned.html
[Samsung Gear S] Beukhof1:
[MENTION=803006]biktor_gj[/MENTION] was just wondering how close are you to a working wifi and/or data connection?

btw i had sometime to test it now and im really impressed by the speed and battery life. Only big problem is the random reboots.
[Samsung Gear S] Kovs:
Question:

With the soon to be release of the LG Watch Urbane 2 with Cell support AND android wear, what are the odds of an Android Wear port coming? If it were possible, I would be on the Gear S in a heart beat!
[Samsung Gear S] hurdlejade:
I think 99% here DO NOT want Android Wear. It's simply notification system, nothing more. When it's updated to work with GSM etc then maybe it's worth having another look, but right now, PLEASE DO NOT. Stock Android is so much more powerful - just look at Gear 1.

If you want Android Wear, just buy any of the 1st generation watches. I have super cheap LG G Watch and for sure I do not want this system as daily driver.
[Samsung Gear S] Beukhof1:
[MENTION=803006]biktor_gj[/MENTION] any progress?
[Samsung Gear S] chiikko561:
Stop asking him that man... let him work. I mean damn he did just lose all his work.
[Samsung Gear S] voden07:
Im not gonna lie, you have a point there, when this is up and running, with a proper daily driver released, i see the gear s increase in sales!

i only come to xda, for this forum...eagerly waiting!
[Samsung Gear S] biktor_gj:
Ok guys still fighting the wifi and data...

I thought it was the msm8226 ril overlay driver (device/samsung/msm8226-common/ril) what was causing the network to not come up, but I was wrong. I replaced part of the code and it's still misbehaving...

About wifi, pretty much the same, android side frameworks attempt to start, and the wpa supplicant tries to start too, but both fail and the kernel ends up crashing on some vendor command (net/wireless/nl80211). I have it more or less traced but still no fix... Other than that not too much to report, hope I will get a little lucky at some point and make some more progress... In the meantime, if someone wants to try the kernel with video issues but not crashing with suspend let me know. It still has problems with the wifi making it reboot every once in a while and twrp fails miserably but at least is "usable" ;)
[Samsung Gear S] t2bacdp:
If I can go back to Tizen after test (to use Gear S daily after holidays) I'm OK to test. Instructions in first page are updated? Is this safe for all version of Gear S?
[Samsung Gear S] biktor_gj:
Kernel tree is up to date, device tree has a few modifications pending but not pushing them just yet since they don't work ;)

By the way, *this* is exactly why mobile data is not working:

D/DHCP ( 3427): op 53 len 1 { 05 } ack
D/DHCP ( 3427): op 1 len 4 { ff ff ff f8 }
D/DHCP ( 3427): op 3 len 4 { 0a 78 58 45 }
D/DHCP ( 3427): op 6 len 8 { d4 a6 d2 06 d4 49 20 43 }
D/DHCP ( 3427): op 54 len 4 { 0a 78 58 45 }
D/DHCP ( 3427): op 51 len 4 { 00 00 1c 20 }
D/DHCP ( 3427): --- dhcp ack (5) ---
D/DHCP ( 3427): ip 10.120.88.68 gw 10.120.88.69 prefixLength 29
D/DHCP ( 3427): dns1: 212.166.210.6
D/DHCP ( 3427): dns2: 212.73.32.67
D/DHCP ( 3427): server 10.120.88.69, lease 7200 seconds
D/DHCP ( 3427): configuring rmnet0
D/DHCP ( 3427): failed to set default route 10.120.88.69: No such process

It correctly gets an IP address for the modem, and sets it fine, but when it's about to store the default gateway route, it stops and shouts out "No such process". Now, I'm ashamed that I am a sysadmin and have no clue why it rejects it when the gateway IS in the same segment as the given IP address. Trying to set it manually gives the same response. Either there's still something missing kernel side, or something is not correctly parsed by the android framework when setting it and this is a ghost message coming from somewhere else...

So, a little close to mobile data, but not there yet :)
[Samsung Gear S] Antartica:
That seems like a timing problem. As I read it, it seems that you are trying to set up the gateway before the interface if fully up, so it fails with a "No such process".
[Samsung Gear S] Beukhof1:
Again dude thanks for all you work!!!

It's gonna be so cool when you have data and wifi working!
[Samsung Gear S] hurdlejade:
I'm really inpatient! Can't wait to put Nova and my own icon on Gear S and rock unlimited possibilities :)
[Samsung Gear S] skyred5:
ALRIGHT! keep doing what you're doing now! lotsa gear S owners are rooting for you! I don't want to set any expectation, but having this by Christmas will be one of the greatest gifts! #justsaying
[Samsung Gear S] Shum Channel:
biktor_gj, do you know that Gear S is not connected to the 12 and 13 channel Wi-Fi in the 2.4GHz frequency?
[Samsung Gear S] ChardC:
[MENTION=803006]biktor_gj[/MENTION]

do you know if a privilege user/account/service should be setting the default route and or is the network configuration file allowed for edits by the said user? What are the permissions like for the directiory or file where the host or dhcp files are stored?
[Samsung Gear S] jongcruz:
I was ready to sell mine, this thread is the only thing holding me back.
[Samsung Gear S] Beukhof1:
Yeah... I had one before but sold it. Now because of this I have bought one again.
[Samsung Gear S] algonzalez03:
We should start a bounty.
[Samsung Gear S] Beukhof1:
Count me in!

How do you start one?
[Samsung Gear S] mlodziezy:
Me too !!!
[Samsung Gear S] Beukhof1:
How do you start a bounty for this?
[Samsung Gear S] biktor_gj:
Oh good god, at damn last!

Wifi stopped crashing... It doesn't get an IP address, and it looks like I f***d up something in the RIL layer, but at least wifi powers up/shuts down and scans networks... (github updated)

View attachment 3517992

Edit: aha! Now it connects to WPA protected networks! Wifi is finally working :) Now to wait until it finishes rebuilding CM to see if I fixed the RIL...
[Samsung Gear S] xEliteNinja:
Cant wait to beta test this. Biktor are you accepting donations?
[Samsung Gear S] Beukhof1:
Will you be posting a new flashable kernel/build?
[Samsung Gear S] biktor_gj:
It seems today is one of those days... 3G data working! I'll post a new image probably tonight with the patched video too. Doesn't work well and kills twrp, but since it allows suspend/resume without dying you can start playing with it correctly :)

View attachment 3518148
[Samsung Gear S] t2bacdp:
Can you explain how to install it step by step (with backup). Thanks à lot!
[Samsung Gear S] Apsterdam:
Wow awesome news biktor your the man i really appreciate all your hard work thx
[Samsung Gear S] dr.mazen:
awesome.. awesome i can not wait to run android in my gear s.

thank you very much
[Samsung Gear S] gidi:
[MENTION=803006]biktor_gj[/MENTION] Christmas is early this year!!!!

When can we expect a beta that is stable enough for a non dev?

Thank you sir. You are a phenomenal programmer.
[Samsung Gear S] xEliteNinja:
I was going to donate, I cannot express to you the level of happiness I have for this and your work and honestly dude I'd pay well over 450$ for a watch with full Android you have literally made my watch worth more than double its value. I must say that I will be telling everyone who asks me about this that a "GREAT " friend of mine named biktor has done this for me and I've no idea how!! Good job man I have been watching this thread for literally since the beginning when everyone said it was impossible. I didn't wanna bother you guys too much but goodness biktor you have me and LOTS of other users here extremely excited for this!!! I cannot wait until "tonight" or whenever you post the flashable image... I know it may not be in beta but I can't wait any longer!!! Love you man thank you so much for spending your time doing this
[Samsung Gear S] Azatot:
Yes, it's an incredible job man. I hope that this work goes on! Thanks a lot!!

Enviado desde mi SM-N920C mediante Tapatalk
[Samsung Gear S] xEliteNinja:
If there is any way that I can contribute let me know. I have well over 20thousand subscribers on my YouTube channel and if you'd like a shout out once this is in stable condition I can do so and also post a tutorial and links to your social media. Let me know man I am very grateful. It makes me happy to know that the time you have left on this planet you have spent a piece of it to make our lives better or easier or just make us all look extremely cool like James Bond! Lol thanks again buddy
[Samsung Gear S] violin.siva:
Wow super very soon my gear S will be running Android lollipop
[Samsung Gear S] Beukhof1:
[MENTION=803006]biktor_gj[/MENTION] when will you be posting the new builds? Can wait to try them.

Thanks for your work man!
[Samsung Gear S] biktor_gj:
I made a few modifications more and flashing now, if I didn't f*** anything up and it works correctly, I'll zip it and upload it in a few minutes ;)
[Samsung Gear S] Beukhof1:
Can't wait!!! Is there somewhere I can make a donation?
[Samsung Gear S] raineyland:
So excited!!
[Samsung Gear S] gidi:
You are a f***ing hero!

Please share a donation email for all of us to see.
[Samsung Gear S] biktor_gj:
If you want to donate something feel free to click in the button under my username on any of my posts ;)

Okay, link ready!

SAME WARNINGS AND INSTRUCTIONS APPLY. IF YOU ALREADY HAVE YOUR SYSTEM-DATA PARTITION BACKUP, YOU CAN SIMPLY FLASH THIS OVER TIZEN, IF YOU DON'T, REFER TO MY PREVIOUS POST ON HOW TO MAKE YOUR BACKUPS.

T-MOBILE USERS, YOU'LL HAVE TO COPY BACK YOUR MODEM FIRMWARE TO THE SYSTEM PARTITION TO GET MODEM WORKING!

CDMA USERS: STILL DON'T KNOW IF ANY OF THIS WILL WORK FOR YOU, BE CAREFUL!

Things fixed from the previous version:

More stable display. It is NOT finished, and it has a lot of problems, but at least you can't take the watch out for a walk with it and don't have to reboot everytime you want to check the time.

WLAN: Seems to be working fine. I haven't tested P2P modes (tethering), but at least AP mode works (feel free to try!)

3G Data: Finally found out what was blocking the route adding by android, and there was even something like a patch for that! Of course the patch wasn't suitable for the Tizen kernel, but I repurposed the networking from the KLTE kernel and now it works fine. You should be able to also tether watch's data over bluetooth/wlan, though I haven't tried that far.

GPS: I see the icon come and go but no idea if it works. Feel fre to check!

Things that still aren't working

Microphone: I need to find a day with enough patiente to go through /system/etc/mixer_paths.xml (android) and check each entry against /usr/share/alsa/ucm-ponte-eur/msm8226-tapan-snd-card-es705 in Tizen

It's not hard, but it's really boring... If anyone wants to help me out be my guest!

Display: The fix is temporary, I'll have to get back to it if we want a really functional display

Sensors: I haven't even started with them, and this will possibly be harder than the display...

MTP is disabled for now to allow it to debug, but it works if you modify the boot scripts & default.prop

Oh, and if you push it, it will heat up like a toaster... I think it makes sense since the poor thing is doing a lot more than what it was doing with Tizen... If it gets too hot, let it rest for a few minutes just in case.

Have fun!

http://www.mediafire.com/download/m65p1awdjcrlxq5/CM_Build27.zip
[Samsung Gear S] xEliteNinja:
What are the steps to copy the modem firmware back? Everything seems pretty clear on what to do besides that. Am I taking a file from my system partition backup? Or am I going to find this somewhere else?