yashsingh1/xdaforums huggingface dataset:
[Samsung Gear 2] CLARiiON:
People tend to forget that Gear works with majority of Android devices (well, Samsung sells more than half of Android smartphones)

Another source: Samsung holds 65% of global Android market share

So, it might look odd that Gear works with only Samsung smartphones, in reality it means it works with majority of Android smartphones. And Samsung is taking the Apple-esque approach here. Instead of trying to make the Gear work for all devices, they are optimizing it for just Samsung devices, devices which they can control.

No wonder why Gear is the clear winner of Smartphone battle at this point.

Source:

http://blogs.strategyanalytics.com/...e-of-Global-SmartWATCH-Shipments-in-2013.aspx

https://www.strategyanalytics.com/default.aspx?mod=reportabstractviewer&a0=9389

Gear 2 SDK is already out. Now apps are also turning up. They mentioned over 100 apps already.

Currently available apps include: Atooma, Banjo, Dacadoo, EasilyDo, Feedly, Focus TRAINR, Glympse, iHeartRadio, iwunta (Cloudwear), Life360, Runtastic, Sleep Genius, Spritz, Strava, Vivino, CNN, eBay, Expedia, Flick Dat, MapMyFitness(Under Armour), MyMusicCloud, News Republic (Mobiles Republic)

It's not a bad position for Gear 2 like people here think. In reality, Samsung have the upper hand. They have a real product that people can purchase.
[Samsung Gear 2] AstroDigital:
Samsung promises over 70 apps for Galaxy Gear, these are the first 12, sounds familiar .... and all we got was the 12

So you believe Samsung now? They lied when the mentioned 70 Gear apps.

There are two things wrong with the chart, not all Samsung devices can run gear manager.

If you take in account iOS, and Windows Mobile the percentage of actual devices that work with the Gear is not great.
[Samsung Gear 2] CLARiiON:
The Gear didn't have any open SDK, everyone knows that. The Gear 2 is where their strategy is taking shape with better hardware design, batterylife and SDK.

Am I surprised with 100 apps? Not at all, I think it will quickly increase now. It's obvious.

Here's your list of compatible devices for Gear 2:

Samsung Galaxy S5 / Galaxy Grand 2 / Galaxy Note 3 / Galaxy Note 3 Neo / Galaxy Note 2 / Galaxy S4 / Galaxy S3 / Galaxy S4 Zoom / Galaxy S4 Active / Galaxy S4 mini /

Galaxy Mega 6.3 / Galaxy Mega 5.8 / Galaxy Note 10.1 (2014 Edition) / Galaxy NotePRO (12.2) / Galaxy TabPRO (12.2/10.1/8.4)

That list covers a huge amount of total Samsung smartphone market and easily millions of devices.
[Samsung Gear 2] jonstatt:
The Gear 2 is a cheaper hardware design, not necessarily better. The battery life of the Gear 1 is now very close to what the Gear 2 will have following significant firmware updates. And I expect that once the Gear Manager is updated to support all the devices you mentioned that the Gear 1 will become compatible with them all as well.

Samsung released the Gear 1 before the software/firmware to back it up was ready. They lied about the amount of development behind it and then had to reinvent themselves with the Gear 2 because the Gear 1 had such bad publicity already, even though the device was perfectly capable.

However I think Gear 2 won't be the big success either. If you look at the community application releases within the first few days for Sony's Smartwatch, they got it right. I don't think Samsung knows how to engage or encourage a development community. Most Smartwatch apps are free or very cheap, with a relatively low adoption rate, so developers normally do it for the thrill/fun rather than a profit. With devices from LG and Moto, what is really needed is for Google to define a common API that means apps can run on multiple smartwatches. Samsung with its transition to Tizen is going completely in the wrong direction in my personal opinion.
[Samsung Gear 2] calinormy:
I own gear 1 and I preordered gear2. It has everythong I wish, especially waterproof ip67. I don't care if is android or tiezen or wp or Symbian as long as it works without problems. Gear one is OK and with additional features like Ip67, heart rate monitor, and IR led will become much better. Just my opinion...
[Samsung Gear 2] raiu:
Just saw one at bb. It's much much thinner and lighter. That little bit does make a difference. I am still on the fence about changing out for one.
[Samsung Gear 2] gingerdude:
I'm going to keep my gear 1 for the foreseeable future, when I first got it I couldn't wait to root it and flash the null tom., but as time went on I zoned in on what I need from a smart watch and as Unpopular as it may be I think Samsung did a good job for a gen 1 product. It does what I need, it keeps me phone in my pocket until I actually need to use it, I no longer feel the urge to have the phone in the same room as me all the time. Yes it could have been better but to all those tech sites that Lord the pebble and slate the gear i say WTF!
[Samsung Gear 2] Dann:
From Sammobile Gear 2, Gear 2 Neo and Gear Fit pricing

http://www.sammobile.com/2014/03/21/gear-2-gear-2-neo-and-gear-fit-pricing-details-and-launch-dates-for-canada-revealed/

Following news that AT&T will begin pre-orders for the Gear 2 and Gear Fit along with the Galaxy S5 later today, several Canadian carriers have revealed when these devices will be available. Samsung has officially announced that the Galaxy S5 along with the Gear 2, Gear 2 Neo and Gear Fir will be launched in Canada on April 11. Canadian carrier Rogers has announced that the Gear 2 will retail for $329.99, while the Gear 2 Neo and Gear Fit will be available for $219.99.The Gear 2 will be offered in a variety of colors that include Charcoal Black, Wild Orange, Gold Brown and Mocha Gray. The Gear Fit, meanwhile, will be available in black.

Telus has also mentioned that it will stock the Gear 2 and Gear Fit, but not the Gear 2 Neo. There is no word from Bell Canada regarding the availability of Samsung’s wearable devices, but considering that it is clearing its inventory of the original Galaxy Gear, it is likely that the carrier will stock the Gear 2 and Gear Fit in addition to the Galaxy S5.

---------- Post added at 01:02 AM ---------- Previous post was at 12:56 AM ----------

Source: http://www.sammobile.com/2014/03/21/gear-2-gear-2-neo-and-gear-fit-pricing-details-and-launch-dates-for-canada-revealed/

Samsung has announced that it will be showcasing the Galaxy S5, Gear 2, Gear 2 Neo and Gear Fit at over 1,400 retail locations worldwide. All four devices will be available for pre-order from the retail locations starting March 21. The devices will be making their way to over 300 Best Buy stores across the US and will be available in major retail stores in Switzerland starting Friday. Samsung has also announced that the devices will head to 59 other countries that include the UK, Germany, Brazil and China later this month. Samsung is bringing the handset as well as the wearable devices to major retail stores as well as electronic chains and exclusive Samsung outlets.

Younghee Lee, Executive Vice President of Global Marketing, IT & Mobile Division at Samsung Electronics, said that the initiative was designed to showcase all the new features that have been included in these devices. “The new Galaxy S5 and Gear devices are designed for what matters most to our consumers. We listened closely to our consumers when designing these products, and we want to give as many customers as possible the enough chance to experience of Galaxy S5, Gear 2, and Gear Fit before they purchase.”
[Samsung Gear 2] Dann:
Google introduces Android Wear

http://gigaom.com/2014/03/18/google-introduces-android-wear-here-comes-my-google-now-watch/
[Samsung Gear 2] griskaitalia:
just picked up mine

so i just got mine gear 2 form bestbuy.

first impression: lighter, more comfortable the absence of the camera on the wrist band is a plus, and the fact that the old bulky speaker moved back on the watch add slickness.

I lost all the android app, especially the one I loved evernote.

Till now the battery seems improved but I don't know how much. I love the new minimal charging cradle.

If you used the old one as a notification reminder, so this is better; if you were an advanced user {null, full android blah blah blah} you are gonna be disappointed probably.

I used to have the full android experience on the old gear, the problem was that using it as an android device the battery would die in less then 12 hours.

Hope this help somebody.
[Samsung Gear 2] nowy57:
do you feel any much more response on gear 2 vs GG ?

have you saw galaxy fit ?

what do you think about galaxy fit compare to gear 2 ?
[Samsung Gear 2] m3ha:
WTH? Where do you live where Best Buy got it in-stock today? There is no best buy within 100 miles of me selling it today. I live TN btw...
[Samsung Gear 2] raiu:
When taking calls, is the speaker louder on the gear 2?
[Samsung Gear 2] griskaitalia:
I don't feel any difference in responsiveness, it's almost the same. I am charging the battery right now so will see. I saw the fit, but honestly one of the thing that I use most on the gear is the camera so that wasn't an option. I hope that apps come soon otherwise I will go back to the galaxy gear.

I live in NYC and there was a remote best buy in COrtland manor, NY that had it so I purchased it online and picked up in store. ;)

I must say that the speaker sound the same or a little quieter compared to the galaxy gear, but it sounds crisper with the galaxy gear if you use volume level over 5/6 during calls the sound quality it's bad at least in my experience.
[Samsung Gear 2] djwood:
Yes, it needs more apps! At least web browse. This is my first one and so far I'm liking gear 2 alot.
[Samsung Gear 2] sohebq:
I skiped gg1 and was very excited to get gg2 but currently I am putting it on hold, just to see the development and apps capacity of it.

Sent from Note 3 (The beauty & beast)
[Samsung Gear 2] nowy57:
how can you guys compare g2 neo to gear fit ?

is it really two different watches ?

apart of speaking to watch (gear 2 neo)

it is almost same funcionality I think ? am I wrong ?
[Samsung Gear 2] raiu:
Gear neo has tizen mobile os and has an open sdk. Gear fit does not have tizen but a real time opperating system and does not have a speaker or mic and will probably have limited apps made.
[Samsung Gear 2] nowy57:
so for future it will be better to buy GEAR 2 couse it could have much more support/customization even on xda comunity
[Samsung Gear 2] raiu:
IMHO I think the gear neo and gear 2 will have more development then the fit will. Only time will tell. I honestly have a feeling that someone is going to port the original gear firmware to the gear 2 at some point
[Samsung Gear 2] nowy57:
no way :)

it will be so good to have android OS on gear 2 !
[Samsung Gear 2] Naddict:
lets go here..http://xdaforums.com/showthread.php?t=2599408
[Galaxy S 4 Active Original Android Development] snadge:
Note:

This thread started as a discussion for development of a working CM11.0 / KitKat build for GT-I9295 / S4 Active International. At first, with assistance from a CM dev who wishes to remain unnamed and does not want involvement with this, a build was produced for this device, based on work previously done by LeJay on CM10.2. Unfortunately, I have not been able to contact LeJay, which is the primary motivation for starting this thread. Since then, and in a short space of time, xda user [MENTION=3876105]spegelius[/MENTION], has managed to progress this to a fully functional build, which some users are already using as a daily driver.

After much hard work from pretty much everyone except me, it pleases me to write that this device has reached official status, and as such one can obtain nightly builds, updates, and source code, from the official CyanogenMod sources. Congratulations to all involved, and the effort thats been put in to make this happen.

Instructions:

1. Install CWM recovery from TODO: link official CWM here

2. Download the latest official nightly from: http://download.cyanogenmod.org/?device=jactivelte

Left for historic purposes (older pre-official builds): Credit: spegelius: https://drive.google.com/folderview?id=0BzJzDM42pkRvdDR0ZE00UERGU1E&usp=sharing

3. Download CM11.0 gapps from here

4. Boot into recovery by holding the Volume Up button as the phone is booting.

5. Back up your current ROM inside CWM recovery.

6. Flash CyanogenMod ROM to your device using CWM recovery.

7. Flash Google Applications to your device using CWM recovery.

8. Do a wipe data/factory reset from within CWM recovery.

9. Reboot system.

Known Issues:

1. None that I'm currently aware of.

2. Report them. Keeping this part up to date has proven to never actually happen, so maybe just read through the entire thread. Convenient right? ;)

Build from source:

Please consult this guide for setting up CyanogenMod for compile.

Please use

repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0

when you initialize the CyanogenMod repository so you get the source for CM-11.0.

Run 'repo sync' and compile with 'brunch jactivelte'. Proprietary files you can find on github, or extract them from an existing rom.

This is pretty much a word for word ripoff of LeJay's cm 10.2 post. This is where one would say something like, I take no responsibility if your device explodes, catches fire, invades a foreign nation, causes your cat to get run over by a car, etc.

Thanks goes to LeJay for being pretty much the sole reason a thread was created for this device on XDA, and in turn the people he gave thanks to, primarily the CM team. Additional thanks, of course, goes to spegelius, for running with this thread, and creating something that actually works.
[Galaxy S 4 Active Original Android Development] snadge:
Downloads here:

** TODO **
[Galaxy S 4 Active Original Android Development] snadge:
Changelog:

** TODO **
[Galaxy S 4 Active Original Android Development] x2pacx:
awesome! I look forward to a stable release :)
[Galaxy S 4 Active Original Android Development] spegelius:
Interesting, good to hear there's CM dev helping :). I've been playing with the idea of trying to compile CM11 since i got AOSP 4.3 working as daily driver. I'm also using LeJay's work, without it i propably wouldn't even have strated hacking with Android. And i haven't heard from him either, i hope he is okay.

Anyways, my first idea was to try it with same jactiveltexx stuff as cm-10.2 is done and see how far that takes me, but if you have already done it and no display, it's possible that the kenel needs to be updated and newer graphics libs used. Luckily i've done some merging between S4 and S4 Active kernels and i already had a look at CM11 S4 kernel code. There are some changes in the graphics code, so there's a very good possibility to get those merged to Active kernel, to me it looks like S4 and S4 Active have same kernel, except for camera, some gpio stuff and assorted tidbits around the kernel. As for the graphics drivers, i think it should be possible to use libs from S4's CM11 build?

Gotta try this myself later this week :)
[Galaxy S 4 Active Original Android Development] snadge:
I have tried compiling the stock CM jf common kernel, with s4 active config. SurfaceFlinger fails to initialise EGL libs. I have tried porting LeJay's cm-10.2 active kernel to build on cm11.0, that also fails in the same way. It seems you' are right. The graphics updates for the other s4 devices likely need to be done for active as well, which may require some new props. Jftleatt's props might be worth look at for display props, same cpu/gpu, different lcd panel.. I'm using my phone as a daily, and haven't had much of a chance to test builds.
[Galaxy S 4 Active Original Android Development] emersonas:
When big boys does the taking we just wait for candies...
[Galaxy S 4 Active Original Android Development] spegelius:
Weel i made a build myself, tweaked the makefiles etc. but there;s a problem: i can't get past the initial text. Something goes wrong about the build and i don't quite know what. I think i'll do a clean repo sync, current source tree is from cm-10.2 and even though repo status says it's clean, i have a feeling something might be wrong with it.

I did some kernel source merging and the build process does build it, so now to get that damn thing to boot...
[Galaxy S 4 Active Original Android Development] spegelius:
Some testing done:

clean CM11 repo sync, still no go with cm-10.2 jactive kernel or the one with merges from jf kernel i made. No adb connection, last_kmsg: http://pastebin.com/Nj5rStTc

using jf kernel and jactive config, with small mods to get it to build, goes a bit further. Screen turns black after the initial Samsung text, adb connection doesn't show up and no last_kmsg available :confused:

In he last_kmsg above, it seems that the kernel doesn't mount stuff properly or something?
[Galaxy S 4 Active Original Android Development] spegelius:
Finally figured out why i wasn't getting past the initial boot text; a bad formatting in jf-common makefile left almost all of the qcom init files out of the boot.img so no wonder stuff didn't work... :rolleyes: teaches me to proofread stuff...

Ok, now that i got that sorted out, i get it to boot. Display stays back, but loking at the logcat, Surfaceflinger doesn't die. So it seems the problem now is that the panel isn't turned on correctly, but otherwise the thing works, maybe. I'm using a mix of blobs from Active and latest jflte CM11 nighly.

Now i need to go to sauna and drink beer ->
[Galaxy S 4 Active Original Android Development] spegelius:
Hrmm, it seems the stuff responsible for panel is crashing. Last_kmsg: http://pastebin.com/jZyDLcXw

[ 15.869781] ======== dsi clock dump ++++ =====================
[ 15.869781] 0x0130 : 00000005
[ 15.869781] 0x0134 : 00000000
[ 15.869781] 0x0138 : 00002003
[ 15.869781] 0x004c : 00000005
[ 15.869812] 0x0050 : 00000000
[ 15.869812] 0x0054 : 00000003
[ 15.869812] ======== dsi clock dump ---- =====================
[ 15.869842] [<c010badc>] (unwind_backtrace+0x0/0xe0) from [<c0402284>] (mipi_dsi_cmd_dma_tx+0x1a0/0x25c)
[ 15.869842] [<c0402284>] (mipi_dsi_cmd_dma_tx+0x1a0/0x25c) from [<c040252c>] (mipi_dsi_cmds_tx+0xa8/0xf8)
[ 15.869842] [<c040252c>] (mipi_dsi_cmds_tx+0xa8/0xf8) from [<c0402a78>] (mipi_dsi_cmdlist_tx+0x30/0x48)
[ 15.869873] [<c0402a78>] (mipi_dsi_cmdlist_tx+0x30/0x48) from [<c0402be0>] (mipi_dsi_cmdlist_commit+0xd4/0x100)
[ 15.869873] [<c0402be0>] (mipi_dsi_cmdlist_commit+0xd4/0x100) from [<c0402cdc>] (mipi_dsi_cmdlist_put+0xd0/0xf4)
[ 15.869873] [<c0402cdc>] (mipi_dsi_cmdlist_put+0xd0/0xf4) from [<c04033c4>] (mipi_samsung_disp_send_cmd+0x188/0x1c4)
[ 15.869903] [<c04033c4>] (mipi_samsung_disp_send_cmd+0x188/0x1c4) from [<c0403fec>] (mipi_samsung_disp_on_in_video_engine+0x30/0x10c)
[ 15.869903] [<c0403fec>] (mipi_samsung_disp_on_in_video_engine+0x30/0x10c) from [<c0404dd0>] (panel_next_late_init+0x38/0x44)
[ 15.897583] msm_ta_detect_work: USB exit ta detection - frindex
[ 16.067596] mipi_dsi_cmd_dma_tx: dma timeout error
[ 16.067596] dumpreg: =============IT's Fail case ==============

Same thing with cm10.2 Active code and code from S4 kernel...
[Galaxy S 4 Active Original Android Development] mythi:
Hi sir ... As my experience with dirt porting ... You have fixed everything in kerenl as I see the issues come from different libs in /system/lib...

JFLTE libs differ a lot from ours ... Some how the screen has to with the GPU driver... I am saying this because I have tried porting a jflte cm 4.3.1 ROM using the old cm 4.3 kernel by Lejay... It booted (yay) but the screen looks orangish the WiFi doesn't work the ril doesn't work ...but replacing the nessary libs from your aosp fixed the issues (the ROM didn't boot here) I've known these details from a small debugging event I made ...

BTW is there a way of building a device tree for 4.4 ?? Wouldn't that make it easier on us ??
[Galaxy S 4 Active Original Android Development] spegelius:
Hmm, i was afraid that the GPU drivers would be somehow related to to panel, even though i was thnking that they are separate stuff so if done correctly, one driver doesn't need to stuff that orher driver does...

I did a build with cm10.2 kernel and libs from the AOSP build and suprisingly same results: lcd init fails, Surfaceflinger doesn't die... i need to do more testing with using some qcom stuff from cm10.2 to help pinpointing things.

By device tree do you mean the makefiles etc. like in jf-common? Already done, they are in my github, cm-11.0 branch has been added. No repo for proprietary files yet, though, need to get something working first...
[Galaxy S 4 Active Original Android Development] mythi:
Why not play with the framebuffer/Screenflinger/ Surfaceflinger in the ramdisk of the kernel i think the init file has to do something for lauching the screen :laugh:

Yes the device tree with all qcom propiretory stuff etc..etc..
[Galaxy S 4 Active Original Android Development] spegelius:
Yeah, those init files could be causing this. I tried using cm10.2 device tree (jf-common, qcom-common and msm8960) but there's to much changed and getting it to compile would be too much hassle. I'll see about swapping some init files...

Currently for jactive there are LeJay's devicetree, which contains the jactiveltexx and modified jf-common (some proprietary caera files are disabled). I've updated them a bit and added the cm11 branch. In addition, hardware/samsung, qcom-common and msm8960-common are needed, but these have nothing jactive specific, at least not yet...

---------- Post added at 09:40 PM ---------- Previous post was at 09:24 PM ----------

Holy sh*t, i got visual :cool:. Using:

cm10.2 jactive kernel

cm10.2 jactive blobs

hardware/samsung from cm10.2

otherwise all cm11 stuff

But now mediaserver crashes and system can't fully boot due to not being able to starte the service. But nevertheless, looking good! Gonna try audio blobs from jflte
[Galaxy S 4 Active Original Android Development] spegelius:
Ok now this is getting plain weird: i can't make a build that has working display anymore. Same sources, nothing is modified. I run brunch as always and the result: no display... wtf? And, if i use the boot.img from the one and only working build with another buil, there's display :silly: :confused:. Me no understand...
[Galaxy S 4 Active Original Android Development] mythi:
Hahahhaahha... Seams we are getting it near ... Could you post a ksmg/logcat or any thing helpful ...will try to help this has bright future of success if we all join
[Galaxy S 4 Active Original Android Development] spegelius:
Yeah, here are the last_kmsg and logcat from a build that has display: https://drive.google.com/folderview?id=0BzJzDM42pkRvdDR0ZE00UERGU1E&usp=sharing

I'm uploading the build also and some other last_kmsg's + logcats

Gonna try to create a bootimg with kernel from aosp. I mean, every build i make now doesn't turn the display on. But if i swap the zImage from the only working build, then the build suddenly has display. I also tried building the kernel separately and creating a bootimg with it, no display...

Edit: with aosp zImage, display is shown... so does this mean that the CM11 gcc somehow borks the kernel build? Or wtf? The kernel i'm building has only some filesystem changes vs. aosp kernel...

Edit2: found out why display wan't turning on: when making device tree, i modified BoardConfig.mk to look as much like jfltexx BoardConfig.mk. With that, kernel variant config and kernel config strings switched places. Turns out, in those two kernel defconfig files (jactive_defconfig and cyanogen_defconfig) two different panels are configured. And when configs were switched, the wrong panel config was taken into use... aargh. Damn, i was looking at those lines and thinking if should change them or not...