Related
http://www.geardiary.com/2007/06/17/unboxing-the-htc-mogul-sprints-new-wm6-phone/
this phone looks promising.. hopefully it isnt a flop like the 6700
already there....
Telus P4000
http://www.telusmobilite.com/qc/pcs/handset_htc_p4000.shtml
Sprint Mogul
http://nextelonline.nextel.com/NASApp/onlinestore/en/Action/DisplayPhones?phoneSKU=PPC6800SP
Actually it came today.. UPS just dropped mine off from Sprint.
OK I have 7 days to get out of my TMO contract to go with the cheaper service of sprint.
Bugout...how it the phone (I have a Wizard)? The main confusing I'm having is Sprint lists it as having GPS-A and no where can I see that in any specs (nor can I find the claim it has ATI graphics). Any validity, first thoughts.
There's reviews all over the place.. but here are my first thoughts coming from 2 weeks with an 8525 (which im returning back to AT&T) and a 700p..
The keyboard has a very nice "spring" to it, unlike the hermes, which requires more of a push/pull to open and close it.
I dont know the exact number, but it's about 10mm thinner then a hermes, but it feels much thinner and lighter then a hermes.
I'm still wet behind the ears with WM (long time palm user and the 700p nightmare had me jump ship). All the applications are very snappy. There is no button in the comm manager to turn on/off wi-fi, there is however a hard switch on the lower left to turn it on and off. SPB pocket plus will turn wifi off/on via an the screen button.
It came with 2 Y adapters in the box. 1 for a/c charge and usb sync, and another for charge and a 3.5mm standard headset jack.
The GPSA is only for location based services, it does not have a standard usable GPS in it. As far as I know it also does not have ATI graphics.
I'm still having usability issues because there seems to be steep learning curve coming from palm i.e. no contact list in the sms app, very annoying or maybe I haven't found it yet, or I just have to retrain my brain to send SMS from contacts instead of the actual SMS app.
Another very annoying this is that there is no battery meter on the top bar. I have to do my research to figure out how to turn that on.
My Mogul should arrive today. I ordered it because I wanted a reliable 3G phone. I've been using an 8525 with Cingy. The 3G internet works great. However, voice call quality with Cingy in Salt Lake City sucks. Lots of dropped and garbled calls. Also, battery life is about 10 hours.
It's rumored that The Mogul has better battery life. Sprint also offers some very nice data packages and 3G in many more places than even Verizon.
I cannot wait to give the phone a try.
Here's the link to the ATI claim http://www.dailytech.com/article.aspx?newsid=7748
I think Dailytech is just confused because the chipset uses it (it also allows for an 8mp camera which would be nice )
I know GPSA is location based only but supposedly Sprint is offering their Navigator program with it to work. GPSA does talk to GPS satellites...just with a network and probably something proprietary.
Does anyone know how hackable the Mogul will be. I don't want it on a different network, just maybe a different ROM or something. I've always seen the issues with unlocking CDMA phone but the Apaches seemed to unlock sooo.
Sorry for all the questions...I just now have 6 days to switch (which I'm going to as sprint offered to take my $70 monthly bill to $30). And sprints basic call centers dont understand some of my spec questions.
if alltell gets this by december ill get it thru them because i was thinking of switching to alltell around that time..
My gfs doing that same with Altell...however...someone just reminded me of this http://www.engadget.com/2007/06/07/feds-impose-partial-ban-on-qualcomm-powered-phones/ Qualcomm phones now have a partial ban on them (shipping into the US) which could lead to supply issues.
On a sidenote either one of the sprint people what to do the $25 refer a friends. I sign up, claim you (give them your cell) refered me...you make $25...i make $25....PM me if your in!
hmm well that ban sucks ass.. if sprint wasnt such a POS id switch over to them..
yes, sprint does offer a navigation service, but it's $9.99/mo.
The internal GPS on this thing is very accurate. I signed up for the free trial of "Sprint family locator" and it had me pegged exactly where I was. Locating my wifes phone (a treo 650 which is in the same house was 2 miles off).
I don't think anyone knows how hackable the mogul is just yet.. That's what we get for "bleeding edge"
can someone post the sprint today theme
I'm still still new to this, but if you can point me to a link that shows me how/where it is, I'd be happy to.
edit found it:
http://rapidshare.com/files/38364040/Sprint_Default.tsk.html
Verizon is getting ready to launch the HTC Thunderbolt/Incredible HD, which is an androidd phone with a front facing camera (basically verizons version of the Evo).
I know they have the trophy and a couple other wp7 devices on the way but i wanted to know will there be any devices with a front facing camera? is Windows Phone 7 capable of using a front facing camera? since the launch of iphone 4, the newest ipod touch and the evo, the front facing Camera has been the latest craze in cell phone features, im currently eyeing the HTC 7 Pro if verizon gets it in January but if they will have future phones and wp7 is capable of handling a front facing camera i may consider waiting. I havent seen anything about wp7 and front facing cameras so i was curious is this was even possible with wp7
I don't see why not really. Just a matter of getting drivers setup for it.
I remember reading somewhere (don't remember where) about a portrait camera mentioned in the code somewhere, so yes, in theory is hould support them, it is up to the OEM's to put them in.
deadwrong03 said:
Verizon is getting ready to launch the HTC Thunderbolt/Incredible HD, which is an androidd phone with a front facing camera (basically verizons version of the Evo).
I know they have the trophy and a couple other wp7 devices on the way but i wanted to know will there be any devices with a front facing camera? is Windows Phone 7 capable of using a front facing camera? since the launch of iphone 4, the newest ipod touch and the evo, the front facing Camera has been the latest craze in cell phone features, im currently eyeing the HTC 7 Pro if verizon gets it in January but if they will have future phones and wp7 is capable of handling a front facing camera i may consider waiting. I havent seen anything about wp7 and front facing cameras so i was curious is this was even possible with wp7
Click to expand...
Click to collapse
What good would it be if there's no software/apps supporting it? Until it's added to MS'es minimum hardware standard for WP7, it would be pretty pointless having one on a device. This is the problem with the minimum standard approach...it's too minimum to seriously compete with other devices.
WhyBe said:
What good would it be if there's no software/apps supporting it? Until it's added to MS'es minimum hardware standard for WP7, it would be pretty pointless having one on a device. This is the problem with the minimum standard approach...it's too minimum to seriously compete with other devices.
Click to expand...
Click to collapse
Then get an Android device and have fun complaining about how 95% of the people you know can't video chat with you anyways.
The hardware specs have to be reasonably minimum. OEM that want to make and sell an awesome phone can and will go above the minimum.
Android has no minimum specs and that creates obvious issues. You act like the grass is greener there.
Furthermore even if they did have them on first Gen devices they'd probably be VGA front came, which are about as good as not having one at all IMO...
Sent from my SGH-T959 using XDA App
N8ter said:
The hardware specs have to be reasonably minimum. OEM that want to make and sell an awesome phone can and will go above the minimum.
Click to expand...
Click to collapse
No they won't and neither will the available apps support it. What's the iP4 minimum spec?
Android has no minimum specs and that creates obvious issues. You act like the grass is greener there.
Click to expand...
Click to collapse
Were you referring to me? I said nothing about Android.
Furthermore even if they did have them on first Gen devices they'd probably be VGA front cam, which are about as good as not having one at all IMO...
Click to expand...
Click to collapse
What type of front cam are you expecting? Video chat is only going to support a very small resolution. VGA is more than enough.
WhyBe said:
No they won't and neither will the available apps support it. What's the iP4 minimum spec?
Click to expand...
Click to collapse
The i4 minimum and maximum spec is what Apple designed into the phone. iPhone is one phone model from basically one manufacturer.
I like how you asked about that phone particularly, though. Apple has always maintained one device for all of its touch devices (iTouch and iPhone). Microsoft has minimum specs, but the manufacturers can go above it if they want. Most of hte phones went with minimum specs because it's a new platform and OEMs want to test the water.
Can you blame them? No. Android didn't come out the gate with 6+ phones on several carriers, AFAIK, and it was facing many of the same hurdles that Microsoft is facing with WP7. The only difference is that Microsoft is going about it in a more organized and sane fashion than Google did (Google just cares about getting Android on as many phones as possible, user experience has always been secondary).
Were you referring to me? I said nothing about Android.
Click to expand...
Click to collapse
You inferred Android and iOS when you insinuated they wouldn't be able to compete with the current minimum specs. You don't have to say it, most people can read between the lines.
What type of front cam are you expecting? Video chat is only going to support a very small resolution. VGA is more than enough.
Click to expand...
Click to collapse
Some devices have 1.3 MegaPixel front cams. On an HSPA+, WiMax, or 4G LTE connection the network can more than handle video conferencing at that resolution. VGA sensors are notoriously bad in low light situations (unless the device does some post processing magic).
They simply aren't that good, especially when they can take the place of something that ads value as well like a LED indicator (with different colors), etc. VGA quality is just bad. It's bad no a 6+ mbps home internet connection, and it's bad on a cell phone.
Furtherore, 90% of phones don't have a front cam (at least in the US), so they are still more of a novelty feature than something that is required or should even be expected.
A good example is the Nexus S, which has no LED indicator light, and had to shed HD video recording to make room for the NFC chip. Since most people want thinner, lighter phones. It ultimately means the phones have less room in them, so concessions have to be made.
I think the OS can support FFCs, but until these video chat networks become more popular and are more fleshed out I don't see a need to rush it.
@N8ter:
Again, having a minimum spec leads to all of the apps supporting mainly the minimum spec devices. This happened with WVGA, accelerometers, extra RAM, and FFC's on WM devices. No matter how many devices WP7 or Android has, they are ALL competing with one iP4. The iP4 minimum spec (it's only spec) is pretty much cutting edge.
Because companies (especially Android and MS) seem to be run by accountants (as opposed to smartphone enthusiasts and designers), I don't expect many to try and go above the minimum standard. Even if they do, refer to my first paragraph.
Video calling dictates a certain resolution regardless of the camera you're using. There won't be any 1.3MP video conferencing for a while (bandwidth limitations). And besides, megapixels DO NOT improve picture quality. This is a popular misconception about camera quality.
Maybe you're in a different country/carrier but the video resolution is dictated by the carrier, not the device. So no mater how many MP you camera has, the carrier specifies it's video chat resolution.
When 4G actually becomes standard and carriers stop charging an arm and a leg for it, video chat will take off.
everyone shut it about android... the person asked a question about front facing cameras... the answer is, at present they aren't supported but given how times are changing i would expect them to come for windows phone 8 (though this is still another 2 years away, so hopefully MS relaxes a bit and we see them earlier then that).
n8ter, i think you misunderstood the lead in sentances about what is available, and what will shortly available. it didn't read like a slam on wp7, or promoting android phones. you might be more sensitive in that area than needed ?
i'm very curious about if/when wp7 devices will have video calling. having a 3 way communication between an android, iphone, and wp7 would be such an awesome achievement technically speaking.
WP7 doesn't support front facing cameras. As someone stated earlier maybe in WP8, or hopefully the Mango Update.
Another thing, you guys keep mentioning WP7 Minimum Specs, but you never mention the Restrictions. OEM's can't do a lot of stuff.
WhyBe said:
@N8ter:
Again, having a minimum spec leads to all of the apps supporting mainly the minimum spec devices. This happened with WVGA, accelerometers, extra RAM, and FFC's on WM devices. No matter how many devices WP7 or Android has, they are ALL competing with one iP4. The iP4 minimum spec (it's only spec) is pretty much cutting edge.
Click to expand...
Click to collapse
It depends on how you look at it. 3GS was pretty cutting edge, but halfway through its lifecycle other handsets eclipsed it. This happens with every phone. Nexus One? HD2? They were all cutting edge at some point in time. I don't know if the i4 can be referred to as cutting edge anymore. Even when it was released, it wasn't much better than other devices like the Galaxy S, Droid X, and a couple others. The only thing it has is the Retina Screen (but Samsung has sAMOLED, and IIRC a better GPU in the Galaxy S phones... so not the i4 wasn't as revolutionary as you're insinuating).
Apple achieves good performance through decent programming and standardized specs. The hardware isn't so OMGCRAZY. The designs are nice too, people like that in their "lifestyle" gadgets...
It's not good to base a platform off of "cutting edge" hardware unless you are the only one developing it. This works for Game Consoles and the iPhone. It does not work for Android and WP7 handsets. The business model is different. Making the minimum specs cutting edge discriminates against low cost assemblers (by making them incapable of competing with the likes of Samsung, Motorola, HTC in price, since you're making the OEMs spend ridiculous amounts just to build the phones) and locks you out of emerging markets (full of people who won't be able to afford the devices to begin with). It also makes it near impossible for most people to purchase the devices off contract, due to cost.
Not everyone wants to buy $600-700 phones.
Because companies (especially Android and MS) seem to be run by accountants (as opposed to smartphone enthusiasts and designers), I don't expect many to try and go above the minimum standard. Even if they do, refer to my first paragraph.
Click to expand...
Click to collapse
The platform is new. You SHOULDN'T expect many to go above minimum standard. Although it is out of the realm of certainty, failure is still an option at this point.
Video calling dictates a certain resolution regardless of the camera you're using. There won't be any 1.3MP video conferencing for a while (bandwidth limitations). And besides, megapixels DO NOT improve picture quality. This is a popular misconception about camera quality.
Click to expand...
Click to collapse
Megapixels do improve picture quality
If you're video chatting with someone on a desktop via VGA webcam (or VGA FFC) and they go to full screen mode your picture will look terrible.
Using tech like Fring's DVQ you can adjust the quality of the stream based on available bandwidth/connection speed and current "4G" technologies (HSPA+, LTE, and WiMax) are more than capable of handling HD Video Conferencing.
I know, because my internet connection here is slower than T-Mobile's 3G and I conference from my "home work computer" all the time using a HD WebCam.
Maybe you're in a different country/carrier but the video resolution is dictated by the carrier, not the device. So no mater how many MP you camera has, the carrier specifies it's video chat resolution.
Click to expand...
Click to collapse
This information is patently false. What resolutions your video camera can record in is hardware. If it doesn't have a sensor capable of doing HD video, it won't do HD video.
The only way the carriers have anything to do with it, is if they ask the OEM to take out an HD FFC and replace it with VGA (which most will naturally do - NOW - because the demand for FFC is low and most people simply won't care).
But VGA quality streaming is terrible. I rather have a LED indicator at this point in time than a VGA front cam.
When 4G actually becomes standard and carriers stop charging an arm and a leg for it, video chat will take off.
Click to expand...
Click to collapse
Current "4G" is not charged an arm and a leg for, and people here aren't forced to go with expensive carriers (AT&T and Verizon) unless they live in areas where the smaller networks cannot get them decent coverage, they want a phone exclusive to the carrier, or they can afford it and simply don't care about the price.
The reason Video Chatting didn't take off is because phones are already expensive enough. Putting a FFC in a phone usually means losing something else that has value ALL the time in ALL situations. Also, most phones do NOT have front facing cams on them, so there isn't much reason to want one right now. It's like getting a Blackberry for BBM, when you have no one to BBM... Why bother?
By the time FFCs become an "expected" feature, most people who brought a phone in 2010 will be getting ready to upgrade, and can simply get a phone with a FFC on it...
On top of that, most smartphone OSes don't have the capabilities in-built into the OS. Trying to video chat when you have people using 10 different video chat apps is ridiculously hard. You can't just download one client to access them all like you do for IM services. It's too much of a hassle right now. That's why BBM keeps people on Blackberries, but no one has heard of WhatsApp and half of the people you know on non-Android phones can't be bothered to download and use Google Talk.
The demand simply isn't that high, and people who need it for business reasons, etc. simply get a phone with that capability - irregardless of what OS it runs. Getting stuff done > preference.
Also, there are very, very few things that will kill your battery faster than video chatting.
A phone that turns off halfway during the day isn't fun to use - FFC or not.
ohgood said:
n8ter, i think you misunderstood the lead in sentances about what is available, and what will shortly available. it didn't read like a slam on wp7, or promoting android phones. you might be more sensitive in that area than needed ?
i'm very curious about if/when wp7 devices will have video calling. having a 3 way communication between an android, iphone, and wp7 would be such an awesome achievement technically speaking.
Click to expand...
Click to collapse
I didn't misunderstand anything.
I'm just calling a spade a spade.
vetvito said:
WP7 doesn't support front facing cameras. As someone stated earlier maybe in WP8, or hopefully the Mango Update.
Another thing, you guys keep mentioning WP7 Minimum Specs, but you never mention the Restrictions. OEM's can't do a lot of stuff.
Click to expand...
Click to collapse
You have no idea what WP7 supports, because you don't have access to Microsoft's repositories or a list of the device drivers they have written. It's totally possible that the OS supports FFC (i.e. has drivers written) but there is no phone with the hardware and no Applications to take advantage of it.
Putting a FFC in a phone comes at a price. Monetarily and sometimes it can degrade the quality of the back camera in addition to requiring the OEM to remove something else in the device to make room for that FFC.
No one but a Microsoft WP7 driver dev can confirm or deny what hardware the OS supports. Anything else is pure speculation.
Asking if the OS supports FFC is a bad question. The question should be:
"When will a WP7 device with a FFC be released?"
Because whether or not it can support a FFC is irrelevant as long as there are no devices out there with FFCs in them.
When the devices with FFCs are released, rest assured that Microsoft will have written the drivers for it, and it will work as expected.
And with them releasing Lync with WP7 soon, expect these devices to start propping up probably in the first half of next year, if not the first quarter.
Video Conferencing is a major feature of Lync (the next version of Office Communicator).
In all honesty, what on earth do you want a front-facing camera for?
I remember a few years back having an HTC Tytn with a FFC, and I made one video call with it. The video was really awful quality, about 1 frame per second, and I could hardly see what was going on on the other end. To top it all, the call cost me £3.00 (50p per minute) and that call wasn't even included in my free call plan so it was added to my bill.
Video calling is an overpriced pile of crap and I cannot for the life of me see why anyone would want to use it.
Do you know how many times my friends and family have asked me if I can take video calls in the last 5 years? Never. There's a reason for that, and before you say it, it's not due to a lack of friends and family!
It's a rubbish technology looking for idiot customers with deep pockets.
Jim Coleman said:
Video calling is an overpriced pile of crap and I cannot for the life of me see why anyone would want to use it.
Do you know how many times my friends and family have asked me if I can take video calls in the last 5 years? Never. There's a reason for that, and before you say it, it's not due to a lack of friends and family!
It's a rubbish technology looking for idiot customers with deep pockets.
Click to expand...
Click to collapse
Absolutely right! I have TP2 with front camera. Only once did I use it in the last 2 years. It is not worth it at all. Plus I have to clean the dirt off the lense area, and it is a pain in the butt.
Well Carriers don't charge for the type of video calling that Jim Coleman is talking about. It works over you data connection.
But he's right, it's not a priority because hardly anyone uses it, or even wants to use it. Only a few first party IM clients support it, it's a ridiculous battery drain, and for all practical purposes it's simply inconvenient.
Don't want to have to stare at a phone screen and hold my phone a certain way for half of my phone calls. Thanks but no thanks...
i can say that it was probably added onto the windows 7 phone platform and then dropped right before they put out the final specs. the LG panther, first win7phone didnt have it but the Samsung Taylor did. the front camera doesnt do anything on my taylor on the release version, but i suspect that it might be a future spec.
Stop misusing the word spec.
Microsoft will not make a front-facing camera a required feature in WP7, at least not anytime soon.
They do, however, need to make LED indicator lights a required feature.
I recently bought the Gear S2 after using my Gear 2 Neo daily for almost a year.
I used my Neo for:
- Occasionally taking calls via Bluetooth when my hands were otherwise occupied (e.g. carrying stuff).
- Occasionally controlling the TV via IR blaster
- Tracking my sleep habits, how much I was getting and how much tossing/turning I did that night
- Timekeeping
- Notifications
For reasons I can't really fathom, the Gear S2 only does the latter 2. I can't really understand why Samsung would remove those features from their flagship smartwatch line. What's more, I REALLY can't understand why this watch is getting ABSOLUTELY RAVE reviews across the board. It's almost like people didn't know the Gear 2 Neo even existed.
I guess it has something to do with the fact that sleep tracking, IR device control, and accepting phone calls via bluetooth are things MOST watches are incapable of for various reasons, so it's not much of a drawback from a reviewer's standpoint when those features are removed. As someone coming from the Neo to the S2, I have a hard time getting past the fact that I have an older, cheaper device that is far more capable sitting in a drawer unused. :/
Don't get me wrong, though. What the S2 can do it does do very well. The screen is gorgeous. The rotating bezel is brilliant. This version of Tizen is lightning fast and very intuitive. The "always on" feature is great, and notifications are handled much better. But I can't really escape the feeling that, while the Neo was a smartwatch, the S2 is just a $300 watch that can send text messages and receive email.
Am I missing something here?
Oh, and for some reason I can't get mine to vibrate when text messages are received. Calls only.
I sold my lovely Gear 2 in readiness for the S2 thinking it would finally get better app support and a better UI on top of the camera and ability to make and receive calls.
What a disappointment, apps are worse or as bad as the prior 3 watches, no camera or calling !!!
If you get a 3g model then it will have a speaker...therefore allowing for calls over bluetooth even if you don't have a sim card for the watch. On the sport models there is no speaker though. For the other functions like ir blaster, I guess they figured people don't use it as much and they had to cut something out to include new things like a different form factor, NFC, etc. Not defending, just saying they evolved to something else. Personally, I love my original gear s which basically has everything but the new round size of the S2.
Yeah it's pretty crazy our Gear 2's are the still the most capable smartwatches on the market.
Tends to happen when you strap a phone on your wrist instead of a watch.
JazzMac251 said:
...I have a hard time getting past the fact that I have an older, cheaper device that is far more capable sitting in a drawer unused. :/
Click to expand...
Click to collapse
I don't understand. You say you have a more capable watch sitting in the drawer unused, yet you recently bought a new S2 that is less capable and you are using it. Why not return the S2, use your Neo and save $300 bucks. Just because the S2 is out now, doesn't mean that your Neo can't be used again.
I had a Moto 360 V1 and Gear Fit, I returned both of them after a while because I didn't like them for one reason or another. No point in keeping unused depreciating assets like phones and wearables IMO, it's not like a classic Bugatti or classic Rolex that you can pass on or will gain value.
As far as the S2 is concerned, I think it will outsell all other Gear watches combined easily. The general public just doesn't want the whole entire kitchen sink in their watches. This is evident by previously poor Gear sales. Sure, they will lose some previous Gear customers, but they are gaining many more. That's the way business works unfortunately, maximum unit sales for maximum profits. I will say though that the BT version of the S2 really needs a speaker and Google voice recognition.
supersoulfly said:
Tends to happen when you strap a phone on your wrist instead of a watch.
Click to expand...
Click to collapse
Ha, you cannot stop the inevitable. That point that most of the posters in this thread are making, is that Samsung DROPPED a lot of features and that didn't go over well with a segment of Samsung smartwatch users. I was in the thread where they were saying the S2 was selling out in Korea.. Wow, I figured that was just plain sales talk or there must be users that don't care about the PAST features that were on past Galaxy Gear Watches. Gear 2 was nice, but I even went for the Gear S, I am fully independent of my Note 4 if I choose to be.. They have put the S2 out there without a speaker, and they downsized it..
People are not talking against the S2 just to be talking, that's for sure..
Back to your comment, why don't Samsung just make a PLAIN WATCH, and leave all Tizen, email, and small tech stuff that you can do on the S2 alone?
Get the S2 3g model if you want an independent experience. (why do people keep acting like this model doesn't exist and doesn't address most of the complaints prior S users have?)
As far as making a plain watch? I might consider wearing that before the monstrosities Samsung has put out before. Gear 2 and Gear S, lots of cool tech, but the only place I'd be seen wearing one is if I went to a Star Trek convention.
This thread reminds me of a book I read years back: "Crossing the Chasm." It's about the challenge technology companies have selling to different kinds of customers: technology enthusiastic early adopters vs. the pragmatic broader market. According to the author, Geoffrey Moore, the former are an important way to launch an product in a new space, but represent a very small market. The latter are a much larger market but are not going to buy a product until it reaches a level of maturity, refinement, and clarity of purpose.
I usually consider myself an early adopter, but I gotta say, I really like the S2, but I had no interest whatsoever in the Gear 2 or Gear S. But for those who like that sort of product, hopefully there will continue to be options in future.
I get that there's a lot of "can't please everyone" talk going on here, but here's why the removal of these features is kind of nuts to me:
The single driving complaint the public has with this type of wearable technology is that it's pointless. The iPad and the iPhone were brilliant because they were able to fill a niche solving problems in people's lives that they didn't know existed. People argue that the physical form-factor limitations inherent with smartwatches makes them redundant at best and extravagantly wasteful at worst. The problem is that this characterization is largely correct.
For smartwatches to break out of that mold, I think the key is for them to be as Swiss-army-knife as possible. Can't find the remote, got it. Can't answer call because its impractical (hands full, can't find phone, doing chores, etc), got it. Would like to evaluate sleep habits, got it. Need to make NFC payment, got it. Want to track your heart rate, got it. The second you start dumping features is the second you move the device even more into the realm of "$300+ dollar device to check your email". The rotating bezel is super cool, but the primary concern people have with smartwatches is that they're pointless, not that they need to be easy to use.
The point I was trying to make is that I was one of the few people for whom Samsung successfully created a product that actually DID fill a unique little niche in my life. As they're trying to expand their product base, it seems the last thing they would want to do is create a flagship device that has absolutely 0 appeal to someone that is already super into smartwatches anyway.
This is actually the first time I've ever upgraded a piece of technology to find it woefully inadequate to what I already had. As a technophile, that's a really strange concept to me. The technology in device is great - I love the hardware, the software, and the implementation. Unfortunately, this device really is a $350 way to read text messages on your wrist and that's all it is, which is why I'll be returning it ASAP.
Also, I have to say, it kinda looks feminine. I much prefer the squared off look of the Gear 2. That's just personal preference, though.
JazzMac251 said:
I get that there's a lot of "can't please everyone" talk going on here, but here's why the removal of these features is kind of nuts to me:
The single driving complaint the public has with this type of wearable technology is that it's pointless. The iPad and the iPhone were brilliant because they were able to fill a niche solving problems in people's lives that they didn't know existed. People argue that the physical form-factor limitations inherent with smartwatches makes them redundant at best and extravagantly wasteful at worst. The problem is that this characterization is largely correct.
For smartwatches to break out of that mold, I think the key is for them to be as Swiss-army-knife as possible. Can't find the remote, got it. Can't answer call because its impractical (hands full, can't find phone, doing chores, etc), got it. Would like to evaluate sleep habits, got it. Need to make NFC payment, got it. Want to track your heart rate, got it. The second you start dumping features is the second you move the device even more into the realm of "$300+ dollar device to check your email". The rotating bezel is super cool, but the primary concern people have with smartwatches is that they're pointless, not that they need to be easy to use.
The point I was trying to make is that I was one of the few people for whom Samsung successfully created a product that actually DID fill a unique little niche in my life. As they're trying to expand their product base, it seems the last thing they would want to do is create a flagship device that has absolutely 0 appeal to someone that is already super into smartwatches anyway.
This is actually the first time I've ever upgraded a piece of technology to find it woefully inadequate to what I already had. As a technophile, that's a really strange concept to me. The technology in device is great - I love the hardware, the software, and the implementation. Unfortunately, this device really is a $350 way to read text messages on your wrist and that's all it is, which is why I'll be returning it ASAP.
Also, I have to say, it kinda looks feminine. I much prefer the squared off look of the Gear 2. That's just personal preference, though.
Click to expand...
Click to collapse
Agree with everything you wrote except for the part where you said you think the watch looks kinda feminine. ?
Sent from my SM-G925P using Tapatalk
supersoulfly said:
Get the S2 3g model if you want an independent experience. (why do people keep acting like this model doesn't exist and doesn't address most of the complaints prior S users have?)
As far as making a plain watch? I might consider wearing that before the monstrosities Samsung has put out before. Gear 2 and Gear S, lots of cool tech, but the only place I'd be seen wearing one is if I went to a Star Trek convention.
Click to expand...
Click to collapse
, Gotta give the Star Wars Crack was a good one.
However, if the S2 was so much a winner, we wouldn't be having this conversation. Instead we all would be breaking or necks to get one. As you can see that is not the case. A lot of users that WOULD be breaking their necks to get on are instead turned off by the new design and features.
You can't ignore that, just read some of the comments.
Since I am a Samsung Fanboy, I will wait for the S3 and Note and see what happens!
I am a Star Wars fan, now I'm addicted to Guardians Of The Galaxy.
I'll gladly sale my gear 2 neo to anyone reading this.
IR blaster went away on phones and watch, just didn't make the cut for usability. I played with ir for the first day to show off then never used it again myself.
Camera in a watch was another one. Apple watch will sale a **** ton without these features for more money. It's not needed by enough people.
Speaker, u just bought the wrong model, but they should have put it in all models. I agree on that part.
Other problems are app issues and tizen is always gonna behind google wear, they are trying to swim upstream and I'm afraid they will never catchup in shear amount of apps.
The 3G model is not coming to all markets the UK being one.
Samsung is just a Apple sheep soon as the Apple watch fan boys like the whole making and taking calls Samsung will do the mother of U turn and the S3 gear will be out this time next year if not earlier.
My Gear 2 was great battery and did the notification basics and handy calling features but the lack of apps was a killer and here we are again the same crap this time 1000 apps at launch.
I think the Neo was a massively underrated device and I'll be keeping mine.
That said, the additional functionality versus the S2 were largely novelty items for me... it's core functions of time, notifications and step tracking were all I used on a daily basis. I can understand the frustration if you used these regularly.
The form factor (s2 is a beautiful watch in its own right) and the bezel navigation are worth the price of admission IMO.
I agree with JazzMac about the S2. I have had the original "Galaxy Gear", Gear 2, Gear S, and then picked up a Gear S2. After 2 days I returned it. Loved the round form factor and rotating bezel, but realized I wanted at least the receive & talk capability on the watch. I would wait for the 3G version. I have had the 3G version for about 3 weeks now and absolutely love it. Does almost everything I want, has great battery life, and I enjoy the freedom of leaving my phone for runs and other quick trips and still being connected.
I find it bizarre that video and audio recordings created on either my S7 (which I purchased in July of 2016) or on my brand-new S7 Edge (which I just obtained yesterday) are plagued with persistent, intermittent static-type crackling sounds which can virtually ruin the shot video footage or captured audio.
But what I find even more bizarre is the fact that there are almost no posts about this problem that I've been able to find here on xda. First, I've been thinking it must be a relatively common issue considering that I've ended up with two new S7 devices that both experience it. And next, I've noticed identical pops/crackles on various YouTube videos shot with S7 or S7 Edge devices, but typically with no remarks about said noises from the individuals posting those videos. And the most peculiar thing is that I'm finding very few complaints on the Internet at large concerning the topic. Considering the huge number of Galaxy S devices in use, I would think that if this were actually a common problem there would be far more complaints out there.
Here is one thread on the topic at the Samsung support community website:
https://us.community.samsung.com/t5...s-have-strange-static-noises-at-the/td-p/1993
https://us.community.samsung.com/t5...icpage/board-id/GalaxyS/thread-id/1048/page/5
And here's the only thread I can find addressing the issue at xda (maybe I'm searching wrong?):
https://forum.xda-developers.com/galaxy-s7/help/problem-noise-clacking-popping-static-t3427910
I guess what I'm really wondering is whether I may have been unlucky enough to acquire two new devices suffering from the same rare problem? Or whether the problem is actually quite common (as suggested in the threads I've cited above where it's claimed that the issue has existed within Galaxy S devices all the way back as far as the S4)?
I would very much like to hear others' thoughts and/or experiences concerning this problem.
I have got the same issue but if i take a quick video or audio recording prior to actual video the crackling is gone... this leads me to believe that it is software based especially because it happens in the stock camera app and snapchat which just uses the camera's viewfinder instead of proper camera api's... I also think it is a software issue because apps like instagram do not have this problem when recording videos and I know instagram uses the proper api's. Some on the web say that this is a hardware issue but i really hope not. I have a 930u what model do you have?
I have a 930P and a 935P. They both do it; however the 930P only does a couple of chirps/crackles/pops on the first few seconds of the first video I've shot since at least an hour before. And if I keep shooting new videos it won't do it at all. It used to be a lot worse on the 930P. But the more videos I've shot as the months passed, the less severe the problem has become. I use the quick prior video technique you mention as well. But I can't really use it on footage that I decide to shoot on the spur of the moment when there's a surprise incident I want to capture.
I personally can't be sure whether the issue is software or hardware based. I can tell you, though, that it happens on audio (voice) recordings as well.... so it's not app-specific. And considering that the crackling usually happens when the recording software hasn't been used for a while, it almost suggests that it's a thermal issue (which would be hardware), or a electro-static charge issue (which would be hardware as well).
I'm surprised that Samsung hasn't had enough complaints on this issue to identify the cause and come up with a solution over the years. And I still don't get why more people aren't complaining about it. Whatever the answer, if Samsung repair technicians are actually able to fix this issue on the devices that people send in for having it fixed, why is it that they can't implement a permanent fix for it on their assembly lines?
I took quite a few videos yesterday with the stock Samsung camera app, 4k and 1080p 60fps on my Xynos S7 Normal and no popping or scratching noises. I do have a rubber type case on so if the popping is fingers moving on the phone that might be why I do not have this problem.
Jonathan-H said:
I took quite a few videos yesterday with the stock Samsung camera app, 4k and 1080p 60fps on my Xynos S7 Normal and no popping or scratching noises. I do have a rubber type case on so if the popping is fingers moving on the phone that might be why I do not have this problem.
Click to expand...
Click to collapse
The S7s I have are the SD820 models. I'm unsure whether any of the Exynos models suffer from this issue. But I think they may based on the regions some of the video clips I've seen (that contained the same sort of popping) have been shot in. Here's a link to one of the videos someone shot to demonstrate the problem:
https://www.youtube.com/watch?v=vj2Hd2hpnDs
With my phones it's not caused by hand or finger movements. It happens when the devices are perfectly still, even sitting stationary on a table. And it makes no difference whether a case is on or off of them.
Am I simply unlucky enough to have acquired an S7 and an S7 Edge that have this (possibly very rare) problem in common? Or is it a fairly common problem that goes largely unreported for some reason? I'm not sure.
God damn, i have that problem too. I dont notice it before
Video taken 5 minutes ago
https://youtu.be/MraHDORny4g
Sent from my SM-G930F using XDA-Developers Legacy app
olafsand said:
God damn, i have that problem too. I dont notice it before
Video taken 5 minutes ago
https://youtu.be/MraHDORny4g
Sent from my SM-G930F using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yep, you sure do. So this proves that the problem exists on the Exynos models as well. I think it also may suggest that many S7 users just haven't noticed the problem yet, like yourself. It could be that when some users hear these crackles, they think they are just background audio that was picked up during the recording. I wonder how many other S7/S7 Edge owners really have this issue but simply haven't noticed it? It's quite frustrating!
One thing I have just discovered: If I cover the bottom mic hole with my thumb and then start to record video (leaving my thumb over the bottom mic hole until I stop recording), when I play the video I've just recorded there is a muffled rushing sound for the first several seconds and the periodic pops can be heard in the background under that sound. But after those several seconds, with my thumb still over the lower mic hole, there is one final loud-ish pop, after which both the muffled rushing sound and the pops are seemingly gone. I have duplicated this 5 times so far. It has always behaved the same way. The impression I have from my testing is that upon the point at which the loud-ish pop occurs and the rushing noise vanishes, the device has somehow detected that the bottom mic has been blocked and thus auto ports its mic input instead from the device's top mic, simultaneously cutting off input from the bottom mic. Whereas if I perform a similar blocking of the top mic during a recording, nothing at all seems to happen. I can't even hear any change in noise from my finger touching the top mic hole. That is, until I force the switch by plugging the bottom mic hole.
So what does this all mean as far as the popping/crackling issue? One thing it seems to indicate is that the unwanted pops/crackles are introduced to the audio input circuitry when the device is listening through the bottom mic hole. So the problem may be within the circuitry connected to that lower microphone. If there were some way to force a permanent switch to the upper mic (or turn off the lower mic) during recording, it may solve the popping/crackling issue.
Thoughts anyone? Please test this on your devices and post back with your findings.
Wow! Here's a thread that I hadn't seen before just now (started in 2013):
https://forum.xda-developers.com/showthread.php?t=2317900
And here's a short YouTube vid that includes a discussion which I just found as well and it's right on point:
https://forum.xda-developers.com/showthread.php?t=2317900
The guy who posted the video confirms part of my findings, that the bottom mic is the one that typically produces the crackles when it's in circuit. He speculates that it may be a built up static condition on the lower condenser microphone. I was actually thinking the same thing. I mentioned it in post number 3 in this thread in fact. He mentioned that if you shoot a burst of compressed air into the lower mic hole the static goes away for a while. Yesterday, I discovered that, too. And that's what led me to the mic hole blocking tests I've been doing today.
This has been going on with Samsung devices for at least 3.5 years, and without being resolved! And when you call Samsung tech support about it they always tell you that they've never heard of it before. They did so with me concerning my S7's audio popping and they told some of the people in the discussions I've posted links for above the same thing 3.5 years ago.
I guess most people have just given up on this matter, since the problem is still seemingly built-in to many of Samsung's devices and there are so few new complaints posted anymore about it. What angers me the most is that Samsung continues to disavow any knowledge of this longstanding issue. They collect everyone's money for new devices that possess this flaw, but they have failed to fix the problem in over 3 years (have they even tried?), and they continue to tell those experiencing the issue that they've never heard of it before. Too bad everyone with the issue doesn't decide to organize and hold Samsung legally accountable for selling us these flawed devices at premium prices.
Update:
Yesterday evening I spent over one hour on the phone with Samsung customer support concerning this issue. The support representative was quite courteous. He was even outgoing, in terms of his willingness to check various resources during the course of our discussion. He proceeded to share the substance of my complaint with his supervisor and his second tier support contact person throughout our phone session. Nonetheless, my anger prevails.
I'm still angry because not only did this Samsung support representative claim that he'd never heard of this recorded audio popping/crackling issue among Galaxy S model devices before... he as well conveyed that neither his supervisor nor his second tier support person had ever encountered complaints about it either. Those responses simply do not comport with Internet reports to the contrary, some of which describe the issue being discussed with Samsung customer support personnel, and even being conferenced with cell carrier service support folks. Nor do they comport with the number of Internet forum complaints springing up on the problem ever since the S4 was a current device, not to mention with the two separately purchased S7 devices of mine, which both demonstrate said recorded audio crackling.
Another indication that this is a widespread flaw among Samsung Galaxy phones is the number of statements I've read from people who've experienced the crackling issue who claimed that after they had received replacement devices of the same models, those replacement devices demonstrated the identical recorded audio crackling. If those claims are in fact true --and I believe they are-- I think it's fairly conclusive that a serious design or quality control issue exists in the midst of Samsung's engineering and manufacturing. When someone pays $600 to $800 for a brand-new device, once they begin using the device's video recording function they shouldn't have to learn that said device will randomly ruin their video footage. While that's bad enough, Samsung's phone support people consistently disavowing awareness of the issue is unconscionably unacceptable to me. Selling flawed devices while pretending the problem doesn't exist is not a mark of integrity for a technology company. But unfortunately Samsung has no qualms in doing so while they become richer and richer.
I still can't understand why there aren't more folks currently concerned about this issue here on xda? It's hard to imagine that that's the case since I know there has to be quite a lot of crackling Samsung devices among xda's member base. Perhaps most Samsung-using xda members don't shoot much video so haven't noticed the problem... or maybe video and audio recording simply isn't very important to the majority of Samsung device owners here. But I have to say I find that somewhat difficult to believe.
Just tested making several videos and I really don't har any popping sounds but it's true that in the videos shared above it's very obvious. I have an Exynos model bought 3 months ago.
ciprigeorgiu said:
Just tested making several videos and I really don't har any popping sounds but it's true that in the videos shared above it's very obvious. I have an Exynos model bought 3 months ago.
Click to expand...
Click to collapse
I'm glad your device doesn't appear to have the problem. I'm unsure what the percentage of affected Samsung phones may in fact be. Even if it were, say, only 5%... that's a lot of phones considering how many of them are out there. That 5% would be 50,000 devices for every 1,000,000 sold. And I suspect that the figure is well above 5%. Thanks for testing and for sharing your result.
Now this guy is REALLY upset about the crackling:
https://www.youtube.com/watch?v=mXBtgcSDxsA
Please be warned before clicking, he uses lots of expletives.
S7 Exynos Model, bought in December.
I have no popping or crackling whatsoever. Just tested every resolution.
nothing like this on my g930f purchased in august 2016
I'm happy for those of you whose devices don't suffer from this recorded audio crackling problem... thanks for reporting on it. It's a shame though that so many Samsung phones in fact do demonstrate the problem. And it's disturbing that Samsung hasn't taken responsibility to isolate and fix the issue during the past 3.5 years of its presence. I find it especially unacceptable that Samsung refuses to even acknowledge that the issue exists after all of that time.
I am reasonably certain that these crackly pops are built-up static charges that tend to discharge during audio recording sessions, and that said static charges exist somewhere in the audio input circuitry, or perhaps in the lower microphone element itself. And I have actually found one way that seems to dramatically reduce the frequency of those discharges or, in some cases, even eliminate them altogether. I'll explain below.
If your device suffers from the recorded audio crackling problem, you might want to try an extended recording burn-in period. Simply bring up your camera app, hit the video recording button, then leave the device on a table. Allow it to record without interruption for at least one hour. After that, you can either review the footage to observe the periodic crackles bleeding down to nonexistence, or you can simply delete the footage. From that point you may seldom, if ever, notice any crackling again on your recordings. It seems to have worked on both of my S7s. It may or may not work for you, however. And I'm aware that the crackling may reappear at some point for me. But the results here have been good so far... so I think it's worth a try for you.
The best of luck with your crackling issues. If you perform a burn-in session, please report back here with the results.
Thanks
Hey !
I have just activated 4G on the watch and am very disappointed.
I thought that 4G would work without bluetooth, but I realize that this is not the case (or that I do not know how to do it).
With 4G no Whatsapp, no Discord notifications, no connection to Galaxy Wearable on the phone if bluetooth is not activated.
Is this normal behavior?
I thought the watch was going to connect directly to the phone with 4G if needed to replace bluetooth and it doesn't seem to be the case. Am I doing it wrong or apart from receiving calls / SMS and notifications only for the applications installed on the watch the rest is impossible?
Thanks !
As far as I'm aware call and texts are all that work without Bluetooth connected. So yeah your right on your conclusion
Thanks, that confirms what I thought.
We realize that the years go by but that evidence is still not developed on connected watches.
It is a pity that technology or the will to develop obvious things does not follow.
The fault lies with the builders but also the developers who undoubtedly see neither interest nor profit in making things happen in the right direction.
I've had smartwatches since 2014 and realize that very little has changed in 7 years.
These watches are useful, but they fall far short of what they could do.
At the beginning I left time for things to move forward but to a lesser extent it reminds me of the lack of development and interest in virtual reality.
A market that is undoubtedly too small (although in expansion), the difference with VR being that the cost remains more affordable.
It's a shame when technology doesn't live up to expectations when things are possible and achievable.
Excuse my English, this is a Google translation.