yashsingh1/xdaforums huggingface dataset:
[Samsung Gear 2] biktor_gj:
A couple of weeks ago I didn't know if I would be able to make video work, I don't know if I'll be able to, but you can be sure I will try!

(Removed your pics from the reply to not make a long post)

Thanks! I knew you guys would try it anyway ;)

But you know what is the best part of your pics? now I know it boots correctly on the Gear 2 with the camera hardware! Greeeaat news to see it doesn't crash half boot! I haven't put the camera libraries yet so there's no way it could actually work, but good enough to see it booting right now.

Just as a little note.. touchscreen DOES work in Android! it's the audio library crashing what doesn't let you touch the menu! Whenever you touch the screen it's reported by the android system server, but as it's busy restarting the mediaserver & audioflinger service, it doesn't get 'seen' by the setup assistant. If I get that out of the way, it will work. Aaand bluetooth should too, it seems it's already initialized by Android (obviously I haven't been able to pair it yet), and as the bluetooth controller is the same as the S5 Mini (BCM4334), the firmware is already on the image I uploaded.

Are those available in Android Wear? I don't expect S-Voice since that's Samsung's own thing, Google now? it should work, after all the image is based on the Gear Live. Wake up gestures... They should work. In fact the orientation and gyro look like they're sort of working. They are missing calibration data, the HRM is definitely _not_ working due to missing pieces, but I haven't even tried touching that until it's minimally usable. I guess we'll see with time what it can do :)

Right now I'm just focused on 3 things (from more to less important)

* Audio service -> Either disable it or make it work, or default it to A2DP if it can be done

* Bluetooth service -> Check if it's really working or only half of it. As soon as I get audio out of the way, I will be able to test this and hopefully remove it from the list directly

* Power management -> Reenable and test the power management in Android and remove all the debug stuff I enabled in the kernel. This is of no use if we get 4 hours of battery life ;)

Then will come:

* (everything that stops working after touching the first 3 points)

* All sensors: Gyro / accel / hrm. In fact, Sensor hub. Kernel side is OK, there are a lot of errors in the logcat, so half of them won't work (orientation, according to logcat, does, but not on the setup screen)

* (blindly): Get back all the camera libraries and hope for the best ;)

* Check all the recovery/ flash /sideload functions on my watch: make it as safe as possible

* Remove that screen corruption that happens just when the display is initialized by the kernel and it can't find the bootloader framebuffer info when loading the s3c-fb driver (the garbage just before the wear boot logo). It's driving me nuts!
[Samsung Gear 2] inpherno3:
Horray freedom from Samsung soon!
[Samsung Gear 2] geri005:
Dude, you are my savior...

Keep up the awesome work.
[Samsung Gear 2] Motivateme:
Is it still staying on Android 4.4W?

You are the savior. Thanks for the good and amazing work.

but I have a question: Is it still staying on Android 4.4W or there was some update?
[Samsung Gear 2] kavinzhao:
Firmware based on Gear Live's. Should be 4.4W.
[Samsung Gear 2] kavinzhao:
I think we can, but all he can do is telling you how he did it(hopefully how to fix it). I think he cant release the source without Samsung's permission.

Surprised to know Android Wear has no audio support.

---------- Post added at 01:17 PM ---------- Previous post was at 01:07 PM ----------

@biktor_gj Why not release an alpha now? With no audio support. We can help you test and find out other problems so that we can get things going faster. ;)
[Samsung Gear 2] WerWolv:
[MENTION=803006]biktor_gj[/MENTION]

I found this file online. It's the OTA Update of the Gear Live to Lollipop. Maybe this could help :3 http://goo.gl/pdrNai
[Samsung Gear 2] Hearten S:
Hi! biktor_gj! I really look forward to every process that you are porting Android! Every time you post new information, it makes me really pleased!

Anyway.. According to your post, the reason why Touchscreen DOESN'T work in Android is audio library crashing. Therefore, if you get rid of AUDIO, BT and Audio will work.

So, how about uploading an Android wear file without audio libraries? If that, we can test lots of things such as BT working... etc.
[Samsung Gear 2] kavinzhao:
That's what I suggested. Biktor comeon, give us an alpha to test.

And thats true, every time I see my phone's LED flashing orange(which means XDA Notification) I got very excited, cant wait.
[Samsung Gear 2] Kwbmm:
If I'm allowed to make a suggestion, I believe the first thing to do is try and test the Bluetooth connectivity: if this won't work, everything else will be useless..
[Samsung Gear 2] biktor_gj:
Android wear does have audio support, what I dont have is the required libraries to make it run correctly, since there are only binaries, not source

Making an image without audio support is not as easy as removing some files, the MediaServer depends on it, and without it it doesn't boot. I would have to

a) Recompile the framework without AudioPolicy support so the service doesn't crash, which I can't do because I don't have Wear source code

b) Code a dummy audio library for the platform that simply says all is good, which right now I don't know how to do (I see some people have done it though). I'm trying not to do the same work twice, so if I have to code the audio library myself, I rather make it so it actually works ;)

First I will try to get the RIL daemon working, since that's what making the universal3470 audio library crash, and if that doesn't work, I will give a shot at rewriting the audio library...
[Samsung Gear 2] tharindunw:
superb work

willing purchase it again
[Samsung Gear 2] soylomass:
Gear 2 is one of the best smartwatches available, camera, ir blaster. It doesn't have Wi-Fi but it's still very powerful.

With Android wear it will be modern for much more time, as there will be new apps everyday.
[Samsung Gear 2] gidi:
[MENTION=803006]biktor_gj[/MENTION] You rule sir. You are one hell of a dev. Even though i do not own a Gear 2 i want to congratulate you! Any chance you might port over to Gear S in the future?
[Samsung Gear 2] Shum Channel:
Thank you for your work, Biktor! :good:

Your work is very important for everyone who wants to choose from!

Gear S community is waiting for you with impatience!
[Samsung Gear 2] djsplitimage:
You are the man and I know there are plenty of Gear users who are looking forward to seeing how this progresses. Kudos to you :good:
[Samsung Gear 2] OldDroid:
wait wait wait, so far i know google pushed the wear source code to their git ... ^^

(from moto 360 here) ;)

If you need any specific help, pm me [MENTION=803006]biktor_gj[/MENTION]

EDIT:

https://android.googlesource.com/platform/manifest/+/android-wear-5.0.0_r1

you could also checkout the lollipop-wear-release branch
[Samsung Gear 2] annson08:
Try to unpair all your previously paired watch on your phone first then try to re-pair your watch. For further discussion with this matter, I suggest we head over the Q&A thread. Thank you.
[Samsung Gear 2] tihimasmo:
I'm nowhere near an expert on android but I got trouble with notifications to wear when I started messing around with root permissions for music, sound and Google services. I haven't been able to pin it down closer. Worst case you need to wipe ext4 partition (reflash rom) on phone. Best case scenario uninstall latest apps until everything works again. I had either solution work on different occasions.
[Samsung Gear 2] fernandogdl:
yeah sorry i post it in development section specially as i was on the first to complain about this posts, just tought it was some kind of bug with the new kernel modifications, anyway it solved itself after like 20 wipes (i had already unpaired before) and letting tthe watch to rest in the connection screen for like 30 mins. weird but solved
[Samsung Gear 2] Wilsonb:
Maybe update the instructions to be more specific..

After flashing the "big" file... How to flash the bottom files? Through Odin and using AP slot or using recovery install? It's confusing because the original file I flashed 7-19-2015 was 500+mb, this one is only 284mb ???

"After flashing the big file, flash one of these, depending on what you need:

ADB only boot image: http://www.mediafire.com/download/cu...e_ADB_ONLY.tar

ADB+MTP boot image: http://www.mediafire.com/download/bs...TP_AND_ADB.tar "
[Samsung Gear 2] IkeaKast:
I also only flashed the big file, not small file, it should work. What problems do you have?
[Samsung Gear 2] 2ndcarpenter:
[MENTION=803006]biktor_gj[/MENTION] I have followed this thread since I read about it on Sammobile back in April (maybe somewhere around page 13). First I would like to congratulate you and all that have contributed, what you accomplished is great. I only installed it last week, using the 07.31 build, and I must say, it works quite well. It runs smooth. I am enjoying the life and newness you have brought back to my watch. thank you very much. I have the Gear 2 Neo so the camera isn't an issue. I sent a small donation(99716720DY721034P), I know it isn't much but it should be enough to buy you dinner and a few beers. Thanks again for all your hard work.
[Samsung Gear 2] spityu85hun:
When can we expect new releases? try it how much better than 22/07 build...
[Samsung Gear 2] Wilsonb:
Hi,

Where did you find build 7-31 ? I was lucky to stumble on this forum group that had 7-22
[Samsung Gear 2] 2ndcarpenter:
Post #1683 or HERE OP says it's still beta though, that's why it isn't listed yet
[Samsung Gear 2] Wilsonb:
Could someone explain what these two files are, how to determine which one a person needs, and how to install.. Is it installed via Odin or through zip install in recovery on watch itself?

I am no on Ver. 7-31-2015

"After flashing the big file, flash one of these, depending on what you need:

ADB only boot image: http://www.mediafire.com/download/cu...e_ADB_ONLY.tar

ADB+MTP boot image: http://www.mediafire.com/download/bs...TP_AND_ADB.tar "

---------- Post added at 10:30 AM ---------- Previous post was at 10:28 AM ----------

Is it me or is the sound not functioning yet? I thought that was fixed in the later releases.

Makes no sound.
[Samsung Gear 2] fernandogdl:
it has mentioned before several and several times before, you could use search function or use the Q&A section as this is development.
[Samsung Gear 2] Wilsonb:
Thanks but ........

There is nothing giving details on these two files..

"After flashing the big file, flash one of these, depending on what you need:

ADB only boot image: http://www.mediafire.com/download/cu...e_ADB_ONLY.tar

ADB+MTP boot image: http://www.mediafire.com/download/bs...TP_AND_ADB.tar "
[Samsung Gear 2] Jnioms:
MTP means Media Transfer Protocol, that means connecting your watch to the computer and it being detected as a media device where you can drop or take files.

If you don't know what ADB means then you shouldn't be here yet, you have a high chance of breaking your watch as you will not be able to recover it if something fails.

Go look what adb is and some basic commands first, then you can journey in biktor's work.
[Samsung Gear 2] kavinzhao:
Hey guys, long time since I talked.(did anyone think i left?) How's the Camera? and biktor I think the 100ms delay on screen brightness change is a bit annoying.. can you remove it..or make it shorter?
[Samsung Gear 2] biktor_gj:
No luck with the camera I'm affraid...

The brightness delay was removed long ago, what you see is Android's own delay and that I can't remove (we have 6 brightness levels but Android goes from 0 to 255 so everytime it dims it goes from 255 to 0 repeating the steps, hence the delay)

I'm uploading a new build. I'm not sure if it fixes the color-depth issue with notifications but at least it's clean and has the kernel settings app, this shouldn't give the Android Wear has stopped issue (haven't tested much because I did it 15 minutes ago).

About 13 minutes and I'll post the link on the first page!
[Samsung Gear 2] fil286n:
In the 7/31 beta, sometimes in dim mode, watchface jumped around, not stick in center of the watch. Is it fixed?

lol. I'm keep refreshing first page till the link appear :D
[Samsung Gear 2] biktor_gj:
That doesn't need to be fixed, that jumping around is made to avoid burning the pixels on the screen ;)

Here: http://www.mediafire.com/download/ar8ir73m32yx05n/Wear_511__08_13_2015.tar
[Samsung Gear 2] McGuigew:
Hey Biktor, I have a question, wha about tricking the watch into believing that it has wifi through the bluetooth connection? I read this somwhere here but don't remember seeing the outcome of that proposition :) cheers!
[Samsung Gear 2] hadobac:
Dear Biktor,

I would like to post this follow 2 bugs, after thorough test with both builds July 22nd and August 13th,

1. Step counter does not work

Precondition

:

Google Fit is installed in both phone and Gear

Gear is disconnected from the phone - airplane mode

Steps to replicate

The user went out for a 30-min intense run

What happens

No steps are counted AT ALL.

I tried to have some steps, by installing a few stand-alone step-counter / fitness-tracking apps: VimoFit and Run a' Wear. Neither reports my arm movements.

2. Unable to navigates from Maps from Gear

Precondition

:

Maps on phone is of version 9.12

Maps on Gear opens and loads map correctly

I've turned on High-accuracy mode for Maps on phone

Steps to replicate

Open Maps on Gear, wait for the map to load

Dropped a pin on the street, by hold on a spot on the screen

Tap on 'Navigate' on Gear

Expected behaviour

Maps on phone vibrates and shows the direction.

Maps on Gear shows the direction, as demoed in this video.

What happens instead

Maps on Gear stuck at 'Starting Navigation' screen for about a minute, then shows error message 'Could not navigate to destination'.
[Samsung Gear 2] fernandogdl:
What's the changelog in the new build?
[Samsung Gear 2] ricketkm:
great work just flashed the latest build...
[Samsung Gear 2] jeffc83:
Flashed 8/13 build and first, all was well for the first ten minutes. Then I got "bug report sender has stopped working". I hit OK. Then I got "Android Wear has stopped working", could NOT press OK (completely frozen, waited a few minutes) Since I was not near a PC, I did a hard reboot....all has been working fine so far but I wanted to report my "first boot" issue. If it happens again, I guess I'll do a factory reset.

EDIT: Something is dreadfully wrong now. Black screen after 10 minutes on my wrist (no notifications) and had to do the hard reboot again. Will do a factory reset....

EDIT 2: So far so good after the factory reset/resync...time will tell. 36 minutes (approximately) I got that black screen again, had to hard reboot. I'm going back to the 7/31 build for now.
[Samsung Gear 2] biktor_gj:
Interesting... Mine has been working fine all day... You had a gear 2, didn't you? Maybe something is going on with the kernel camera driver and it doesn't happen if you don't have it... Any other one having issues with last build?
[Samsung Gear 2] AltCtrl701:
Gear 2 here, been running 6 hrs no problems with newest build

Also did not need to factory reset, did not install root either.

Sent from my SAMSUNG-SM-G900A
[Samsung Gear 2] biktor_gj:
It just did it to me, but managed to grab a logcat, and in my case it was Wifi cloud sync what was making it crash (I had been playing with it beforw). [MENTION=2808427]jeffc83[/MENTION], by any chance, do you have wifi sync enabled?
[Samsung Gear 2] jeffc83:
[MENTION=803006]biktor_gj[/MENTION] - I haven't flashed the Gear 2 yet and it's still sitting in a box so "ahem" doesn't get upset with me for modifying it...makes no sense but a happy wife is, well you all know the drill;) Having said that, all of my testing has been done on my Neo so far. Thanks VERY much, that setting may have been the cause;) I have WiFi sync ON for my Urbane and since it is a global setting in Wear, I am forced to turn it off now on all watches...no big deal at all to me. So, I ended up re-flashing 8/13 and it is sitting pretty with the WiFi Sync setting OFF! Thanks my friend, I seriously owe you another donation very soon!!!!
[Samsung Gear 2] Redmen:
I had the same problems as [MENTION=2808427]jeffc83[/MENTION] BUT i do have a Gear 2 (with the cam).

After decline the Wifi-Cloud sync and disable Wifi in the watch settings i haven't experienced any error so far.

I bought this watch for the camera mostly so i'm considering to "borrow" you my watch to get the camera fully working but i will get in trouble with my miss's :)
[Samsung Gear 2] Arry87:
Hi [MENTION=803006]biktor_gj[/MENTION], is this an option? To borrow you a gear 2 to be able to mess around inside the camera? I will be willing to send you mine if this is the case?

Obviously I will pay for postage both way!
[Samsung Gear 2] biktor_gj:
Thanks for the offer, but I wouldn't get different results... Both Neo and Gear 2 are essentially the same code wise. The only difference with the camera, is that it actually receives something when the device is opened, but the signal processor and all the rest are in the Neo too, so if I get a black screen and all the devices are correctly opened and processed kernel side, it should be good to go with the gear 2.

The thing is that the reference libraries are making the kernel crash, All the supposed devices are being opened in the correct order, but it's like one of the function calls sent to the kernel by the library is not being sent to the correct device node on the kernel, thus making it crash... Not easy for me ;)
[Samsung Gear 2] andrew.mackew:
Thanks biktor_gj! :good:

Do you have any hope that camera will work any time soon?
[Samsung Gear 2] leojab:
Thank you for the great ROM biktor_gj

Any hopes for the palm over screen to get screen off feature. I use that quite often on my SW3
[Samsung Gear 2] flatherskevin:
I would like to remind everyone that this a development thread. If you are going to use this port, that biktor_gj has put a lot of effort into, and continually fill this thread with crap, then you don't deserve to be using the port. Keep discussion on task, and act professional.

Back to development: Is the wifi issue being addressed at any point? I know there is no wifi antenna, but there doesn't have to be to use bluetooth tethering. What is holding the watch back from being able to have a successful connection with a sideloaded app like Chrome? This is where the watch is falling really short of the officially supported Wear watches.

Also, can anyone try porting the android phone app over to wear so that it will operate the same as on tizen? All it would take is re-routing the signal right from the sim to the watch, rather than the phone. I am no programmer, so I don't have these capabilities, but hands free calling would put this watch well on top of any other smart watch out there.
[Samsung Gear 2] :
Thread cleaned.

I'll remind everyone to post respectfully, or don't post at all. :good:

Thanks,

Darth

Forum Moderator
[Samsung Gear 2] Jnioms:
i didn't test 1), but with 2) i have the same issue.
[Samsung Gear 2] biktor_gj:
Let's see if I can answer everyone ;)

Not much hope to be honest. My knowledge about camera functionality is veeery limited. I sort of understand how it is supposed to work, but I don't know enough to fix it. If there's someone who has fought that kind of war I would gladly accept his/her help :)

That war is lost. In theory, the touchscreen does have a parameter to detect if you're touching with your palm. In practice, it doesn't detect anything. I tried to manually code it, but resulted in a lot of problems when using it in all other circunstances...

In all other cases that function seems to be implemented with a proximity sensor that we don't even have...

Network should always be tethered. Another thing is if Chrome has access to it given wear's permission structure is allowed.

Despite the fact that I don't understand why you need to run chrome from that tiny little screen (but that's none of my business so no questions asked ;)), have you tried to push the application into the SYSTEM partition? Applicatons residing in /data don't have the same access rights like system apps, so maybe the clockwork proxy is forbidding it...

Fast check for anyone who knows adb.

1. Adb sideload the app

2. Reboot to recovery

3. Adb shell mount system partition

4. Adb shell cp -rfp /data/app/theapptotest /system/app

5. Adb shell rm -rf /data/app/theapptotest

6. Reboot

About the audio routing, I won't make it for a lot of reasons (already said it a hundred times but I'll list it again for newcomers):

1. Android wear doesn't have source code. It is closed. You not only need access to the filesystem, you need modifications to the framework which you can't do.

2. You need to replace the bluetooth stack from bluedroid to bluez, with all the problems that it would cause (it was hard enough to make it work, it would be a nightmare to replace it)

3. You need not the telephone app, but something like the lg call app, + a2dp server on the watch, +ability to detect where are you picking from to route the audio correctly.

4. You'll probably need source code for the audio libraries to allow it, which we don't have.

That can be months of work, which I personally won't do, I didn't even use it when I had it. If someone's willing to give it a try and succeed it and doesn't give more problems that what we already have, I'll put it in my builds, but I think I have already spent my fair share of time with this watch to get into a function that doesn't even exist in Wear.

Gyro doesn't work on Wear (it does have one!!) , that might be one of the issues... I'll take a look and see what I can do...
[Samsung Gear 2] SumTuusDeus:
SUCCESS!!!!

I can't tell you how much this means to me! I CANNOT STAND TOUCHWIZ! And this finally allows me to use my watch with a non-TW rom. And it runs beautifully so far. So, biktor_gj, could you please throw up a bitcoin address or a QR code so I can send you some bucks? It won't be much, because I am a broke college kid. But, I would very much like to throw you some bitcoin as a thank you!!!!!!!! :) Or PM me an address if you don't want it to be public. THANK YOU!!!!!
[Samsung Gear 2] tooandrew:
EDIT: nevermind, I was going to chastise someone for making a post with no other purpose than to chastise someone else for chastising them about staying on topic, but it's just more pointless clutter.

[MENTION=803006]biktor_gj[/MENTION] I'm sorry man, my power supply fried my whole pc when it died, I'm out for the count as far as flashing and testing and will remain so for the foreseeable future. I'm getting great battery on a very old build, though and I'm quite happy with it.
[Samsung Gear 2] AuRoN89:
latest version is totally unusable for me.

Android Wear keep crashing every 5 sec lol
[Samsung Gear 2] biktor_gj:
Did you wipe and disable wifi sync?
[Samsung Gear 2] AuRoN89:
i wiped but i can't disable wifi because it keep crashing.
[Samsung Gear 2] biktor_gj:
Disable it from Android Wear app on the phone!
[Samsung Gear 2] AuRoN89:
how i'm supposed to disable it via phone app if i still need to pair with my phone? but of course i can't pair it because it keep crashing :(

i'll flash it again and let you know if something change.
[Samsung Gear 2] NakedFaerie:
I like some of the apps and features. Its working great for me.

Pity they gimped Android Wear. No sound, no phone calls, no thanks. Thats why im keeping my main Gear 2 on Tizen as i prefer sound notifications and i do use it for calls when im driving as its a lot easier that searching for my headset. If you could impliment sound notifications and phone calls then ill switch to Wear.
[Samsung Gear 2] kraziekool:
hello all,

been enjoy the android port on my neo 2 and decided to upgrade to the 8/13 build.

now my screen is black and i cant do anything. the watch is connected to the phone and receive notification but cant do nothing as screen is black.

had wifi sync off and screen always on to off as well.tried reboot severally but no luck...

need some assistance please on what to do..