Related
http://www.tmonews.com/2014/02/andr...alaxy-s4-s4-note-3-and-other-samsung-devices/
Today, Samsung announced that it would be pushing out KitKat to a slew of its Android-powered smartphones. Although we’re not precisely sure on specific dates for T-Mobile devices, the 4.4.2 update will be rolling out from today.
Among the list of devices being supported are the Galaxy Note 3, Galaxy S 4 and S 3 as well as others. Full press release below:
DALLAS, February 18, 2014 – Samsung Telecommunications America (Samsung Mobile) announced today that a number of Samsung Galaxy® devices will receive the Android 4.4.2 (KitKat) software update, enriching the Galaxy experience.
The upgrade provides a number of innovative, easy-to-use features that enhance the user experience, including a more intuitive user interface, enhanced messaging capabilities and updated applications:
· Location Menu: An integrated location menu enables users to easily activate GPS, Wi-Fi and mobile networks, while simultaneously checking the battery usage of apps running location service capabilities.
· Enhanced Messaging: Enables users to choose between Messages or Hangouts as their preferred default messaging application, and select from a larger assortment of updated Emoji icons.
· Upgraded Google Mobile Service™ (GMS) apps: Users can automatically back up photos and video and can open, view, rename and share Google Docs and files.
Samsung Galaxy U.S. devices currently scheduled to receive the KitKat update include select carrier variants of the Galaxy Note® 3, Galaxy Note® II, Galaxy S® 4, Galaxy S® 4 mini™, Galaxy S® 4 Active™, Galaxy S® 4 zoom™, Galaxy S® III, Galaxy S® III mini™, Galaxy Mega®, Galaxy Light, Galaxy Note® 8.0, Galaxy Tab® 3, Galaxy Note® 10.1, Galaxy Note® 10.1 2014 Edition.
Availability varies by carrier and product, with updates beginning today and continuing throughout the coming months.
If you have one of the Galaxy devices mentioned in the announcement, be sure to let us know when/if the update lands. T-Mobile isn’t always speedy when it comes to giving the green light to software updates on Android. Let’s hope these start to land pretty snappish.
Nice. going to have to Odin back to stock then.
Still months away
TWEAKED 2.0 NOTE 3
Dattack said:
Nice. going to have to Odin back to stock then.
Click to expand...
Click to collapse
Don't update, the bootloader might be locked. It best to wait for a dev to get a hold of the firmware and make it into a flashable rom that doesn't include the bootloader.
marcoxx626 said:
Don't update, the bootloader might be locked. It best to wait for a dev to get a hold of the firmware and make it into a flashable rom that doesn't include the bootloader.
Click to expand...
Click to collapse
I am used to waiting to take updates being on VZW and what they did with breaking root with the Bionic and then the S4 fiasco. But why would Tmobile launch a phone with an unlocked bootloader only to lock it after an OTA update? It's one thing to patch an exploit, but to lock an unlocked bootloader when it was meant to launch unlocked I think would be stange. Again, I'm waiting anyway, but I think the phone will stay unlocked.
Not sure how excited I am for 4.4.2
No app ops. I can't believe google would intentionally remove a vital security feature. I guess we'll just have to add it back in
cun7 said:
Not sure how excited I am for 4.4.2
No app ops. I can't believe google would intentionally remove a vital security feature. I guess we'll just have to add it back in
Click to expand...
Click to collapse
I agree! In fact, that's the first thing I thought about when I heard about the news.
We do, however, still have xPrivacy, though. I've donated to the developer and hopefully we'll see continued development including, I hope, a more user-friendly system closer to the way App Ops works. (For the record, I'm not knocking xProvacy; rather I'm pointing out that it could be easier to manage for laymen like myself.)
Eric214 said:
I am used to waiting to take updates being on VZW and what they did with breaking root with the Bionic and then the S4 fiasco. But why would Tmobile launch a phone with an unlocked bootloader only to lock it after an OTA update? It's one thing to patch an exploit, but to lock an unlocked bootloader when it was meant to launch unlocked I think would be stange. Again, I'm waiting anyway, but I think the phone will stay unlocked.
Click to expand...
Click to collapse
i'm guessing you are right. But you have to remember, it's not TMO that's doing it. It's all part of Sammy Knox initiative to make the phones more secure. If you have an unlocked bootloader, there's no way to say that your product is secure. We've picked apart the last 3 builds /na6/na7/nb3 of kitkat from germany, and there's alot of pointless crap built into these roms that will have to be pulled out to , along with the regular developmental crap that sammy puts in there for "Future Updates" Like fingerprints scanner perms and instructions, radios that will never be used, and something pointing to a backup antennae even though the phone does not have one (that's for the note 10.1)
I think they are being lazy, , making one huge TW Rom and then modifying it for individual devices. If you look at the S4 release and the Note 3 release, they are identical builds minus screen size settings and the addition of spen support.
Any idea when the TMobile update will be available? Sprint customers are getting theirs from today.
Some people from g+ are claiming to get the Sprint updates yesterday. Wonder if someone from TMO got updated too.
There is a complete silence regarding Tmobile update. Even the dog slow at&t has a leaked version out.
Apparently us cellular is getting their update as well.
Here's the link if any one is curious.
http://phandroid.com/2014/02/20/us-cellular-note-3-kitkat/
I hope we're next
posted while using my note 3
I've have been with tmo from the beginning of this computer like smart phone generation, and I will say we are almost always the last to get an update. .. Our wifi calling and wifi alone had a bug for 6 months now no update when other carriers got the fix. .. Just saying. ...
Evertime there's an update these discussions happen. ... When when when. .. sit back relax and flash someone else's rom. ... lol
Sent from my SM-N900T using XDA Premium 4 mobile app
Call it eye-Kat. Make it look exactly like iOS and give Apple the finger
Sent from another galaxy
Check this out guys. Got it from comments on this article:
http://www.tmonews.com/2014/02/andr...alaxy-s4-s4-note-3-and-other-samsung-devices/
I'm on a KK custom ROM on my Note 3 so I'm not getting it. Maybe I need to flash back to stock. I'm in TX too btw.
djtheraven said:
I've have been with tmo from the beginning of this computer like smart phone generation, and I will say we are almost always the last to get an update. .. Our wifi calling and wifi alone had a bug for 6 months now no update when other carriers got the fix. .. Just saying. ...
Evertime there's an update these discussions happen. ... When when when. .. sit back relax and flash someone else's rom. ... lol
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
IKR, the wifi bug is pissing me off!
Sent from my SM-N900T using XDA Premium 4 mobile app
marcoxx626 said:
Don't update, the bootloader might be locked. It best to wait for a dev to get a hold of the firmware and make it into a flashable rom that doesn't include the bootloader.
Click to expand...
Click to collapse
Apparently using Mobile Odin you can flash the update with rootkeeper and you keep Knox at 0x0 and get a rooted 4.4.2 (make sure you set it to reboot into download to flash the bootloader)
Details are in this thread:
http://forum.xda-developers.com/showthread.php?p=49502152
I wish T-Mobile would herry the heck up!!!!
dragonstalker said:
i'm guessing you are right. But you have to remember, it's not TMO that's doing it. It's all part of Sammy Knox initiative to make the phones more secure. If you have an unlocked bootloader, there's no way to say that your product is secure. We've picked apart the last 3 builds /na6/na7/nb3 of kitkat from germany, and there's alot of pointless crap built into these roms that will have to be pulled out to , along with the regular developmental crap that sammy puts in there for "Future Updates" Like fingerprints scanner perms and instructions, radios that will never be used, and something pointing to a backup antennae even though the phone does not have one (that's for the note 10.1)
I think they are being lazy, , making one huge TW Rom and then modifying it for individual devices. If you look at the S4 release and the Note 3 release, they are identical builds minus screen size settings and the addition of spen support.
Click to expand...
Click to collapse
Yeah i can see where you're coming from. but I still don't think Sammy will lock it down, but we'll see.
TMO is busy now with their "marketing campaign" to attract new customers.. They have no time to do software updates for existing customers
Come on peeps cut them some slack
daraj said:
TMO is busy now with their "marketing campaign" to attract new customers.. They have no time to do software updates for existing customers
Come on peeps cut them some slack
Click to expand...
Click to collapse
This is what I was afraid of when switching to TMO. Yeah I save money but at the cost of crappy CS service and very very slow to non-existant updates.
-Sent from my TMO Samsung Galaxy Note 3 using Tapatalk
Can i please get some advice? (sorry a bit long but thought i need to provide the background info).
I have been given a Samsung Note 7 as a compensation-related gift by my network operator Vodafone and to cut a very long story short i have almost exhausted all possibilities with Vodafone and Samsung to get it exchanged for a different model or a credit.
I am currently looking at the possibilities of keeping my Note 7 if i feel i can assess (and possibly repair) it privately to confirm the safety implications and any other issues that may come up.
My questions are as follows:
1. Has anyone had success changing the Imei and model number? The reason is to protect myself from network barring and to retain app support. I have a previous Note and can use the imei. My plan was to change the model to G935F that of an S7 Edge. (There are some sites i came across but I wasn’t sure the guides were tested)
2. Can i root it and will i be able to update it regularly from core android?
3. Will the Wifi-calling feature work? Sounds like a small thing but its quite important. I have this feature on my Note 7 already and activated on my account and its very useful to me.
I live in the UK and I am an Engineer by trade. I worked for a cellular phone repair centre a number of years ago that specialised with Samsung and Nokia phones.
Whilst i have some experience and contacts in the industry, my knowledge of the current software/ firmware platforms on the market is limited so i would greatly appreciate any advice you can give.
Thanks in advance
not too sure about how you would transplant the hardcoded iemi number mate... are uk note 7s actually confirmed being banned?
You can root it and from that you can add features from the xposed library that will surely extend the life of your note 7 for years.. by which time the note 8 should be out in some form.
I read on maybe this site, or another, that someone had their Note 7 thinking it was the S7 yet still fully functioning as a Note 7 (Grace UI, etc)
sonhy said:
not too sure about how you would transplant the hardcoded iemi number mate... are uk note 7s actually confirmed being banned?
You can root it and from that you can add features from the xposed library that will surely extend the life of your note 7 for years.. by which time the note 8 should be out in some form.
Click to expand...
Click to collapse
Thanks for info. I'm not sure if they will fully inforce a ban but the procedure for returning the n7's is pretty much the same, minus the fire proof boxes (read into that what you like). I want to see what needs to be put in place if they do.
Any idiots guide for rooting and where to download files would be appreciated.
The Phone Company said:
I read on maybe this site, or another, that someone had their Note 7 thinking it was the S7 yet still fully functioning as a Note 7 (Grace UI, etc)
Click to expand...
Click to collapse
If you do that would be great.
I'm trying to stoke up some support in the uk to appeal to Samsung to at least reassess the n7's already out there but there's only a few interested. I believe there is more support in the US which may provide a much stronger case.
ccsuk said:
If you do that would be great.
I'm trying to stoke up some support in the uk to appeal to Samsung to at least reassess the n7's already out there but there's only a few interested. I believe there is more support in the US which may provide a much stronger case.
Click to expand...
Click to collapse
The official release date in the UK for the Note 7 was next week, October 28th, which ironically was the same date as the Note 2 release, Note Edge release and Galaxy View release, just different years.
Call me crazy, I recognize a pattern here.
I am a serious Note user, so instead of following the crowd I will either consider the LARGE 18.4" Galaxy View or the 6" Curved Screen Huawei Mate 9. Hmmm, Mate, Note?
For some strange reason there aren't many Samsung Stylus Devices available, can't find the Note Pro 12.2 on sale anywhere. Something is definitely up. All I know is I feel sorry for those Pixel, iPhone 7, V20 blinded sheeple.
What's their reason for refusing to exchange?
Sent from my MI PAD 2 using Tapatalk
BozQ said:
What's their reason for refusing to exchange?
Click to expand...
Click to collapse
Samsung can't help because I didn't buy it direct and Vodafone said it was giving to me as a gift and not linked to my account so I need to deal with Samsung. I know this sounds ludicrous but Vodafone are a nightmare and I was ready to book myself into rehab after the effects of previous issues. I could take this up with an ombudsman but it takes time and I'm not sure I have the energy.
ccsuk said:
Samsung can't help because I didn't buy it direct and Vodafone said it was giving to me as a gift and not linked to my account so I need to deal with Samsung. I know this sounds ludicrous but Vodafone are a nightmare and I was ready to book myself into rehab after the effects of previous issues. I could take this up with an ombudsman but it takes time and I'm not sure I have the energy.
Click to expand...
Click to collapse
The recall is voluntary. Do not believe those people who say your IMEI will be blocked or barred. It will only be blocked if the phone was purchased in a payment plan and You fail to return it. Or if You fail to keep the payments. The recall is absolutely VOLUNTARY. Do not be afraid. Many of us are keeping the phone, because we know the risk is now minimal.
All electronics have the possibility to fail. All batteries have the risk of catching fires. This risk is a lot greater when the device begins their lifecycle. So now the risk is minimal. Samsung did not take "probability" into consideration before sending those replacement phones. Meaning if you had 50 in 2 million to catch fire with the original. Now you had 50+30* of catching fire in the replacement. (*More o Less)
Samsung has a great opportunity to collect data and usage information with us. Otherwise if people panic they will just scrap the Note Series all together.
Good Luck! ?
Sent from my SM-N930F using XDA-Developers mobile app
In short: No you can't change your IMEI, but that is not needed. If you don't want Samsung to directly know that your device is a Note 7, you need to change your device name in build.prop (but to do this you need root) and to deactivate software updates.
But I recommend you to not use the device. Samsung may not release any software updates, and the risk of exploding is still there. Even if the risk is very small, it can happen at any time, and the more time you spend with this device, the bigger is the risk.
SaschaHa said:
In short: No you can't change your IMEI, but that is not needed. If you don't want Samsung to directly know that your device is a Note 7, you need to change your device name in build.prop (but to do this you need root) and to deactivate software updates.
But I recommend you to not use the device. Samsung may not release any software updates, and the risk of exploding is still there. Even if the risk is very small, it can happen at any time, and the more time you spend with this device, the bigger is the risk.
Click to expand...
Click to collapse
Thanks for your reply SaschaHa. I am just weighing up my options while waiting for a reply from Samsung hq. If i was use it I would be after I had assessed it internally.
Although Samsung wont provide updates will I be able to semi - regularly update it manually from stock? Eg nougat 7 was originally in the pipeline for the n7.
Also would wifi - calling get carried over/ integrated in the build?
CerveCesar said:
The recall is voluntary. Do not believe those people who say your IMEI will be blocked or barred. It will only be blocked if the phone was purchased in a payment plan and You fail to return it. Or if You fail to keep the payments. The recall is absolutely VOLUNTARY. Do not be afraid. Many of us are keeping the phone, because we know the risk is now minimal.
All electronics have the possibility to fail. All batteries have the risk of catching fires. This risk is a lot greater when the device begins their lifecycle. So now the risk is minimal. Samsung did not take "probability" into consideration before sending those replacement phones. Meaning if you had 50 in 2 million to catch fire with the original. Now you had 50+30* of catching fire in the replacement. (*More o Less)
Samsung has a great opportunity to collect data and usage information with us. Otherwise if people panic they will just scrap the Note Series all together.
Good Luck! ?
Click to expand...
Click to collapse
Thanks CerveCesar for your advice. How will you be upgrading your roms ie to nougat 7 etc?
ccsuk said:
Thanks for your reply SaschaHa. I am just weighing up my options while waiting for a reply from Samsung hq. If i was use it I would be after I had assessed it internally.
Although Samsung wont provide updates will I be able to semi - regularly update it manually from stock? Eg nougat 7 was originally in the pipeline for the n7.
Also would wifi - calling get carried over/ integrated in the build?
Click to expand...
Click to collapse
You only can update it manually if some rom developers port firmwares from other Samsung devices to the Note 7 (if Samsung doesn't release updates). But that mostly is only possible for the same Android version, so there might never be a Nougat rom for Note 7. So then the only possibility to get a newer Android version is to use a AOSP / CM(14) based rom, if a developer created one for the Note 7. But without proper drivers by Samsung, that's difficult. And I think, the most developers are going to use other devices instead of risking a burning N7.
ccsuk said:
Thanks CerveCesar for your advice. How will you be upgrading your roms ie to nougat 7 etc?
Click to expand...
Click to collapse
I'm staying factory. I did not disable the 80% battery option because we ran a study and found overcharging to be 1 of 3 factors in starting fires. If Samsung sends the Nougat update, then I will just update. The customs ROMs I'm not a big fan of, because it seem one always looses some cool feature like heart monitor, Samsung Pay or scanner. I got a Note 3 that I plan to use as my flying phone and my Note 7 will be my daily driver
Sent from my SM-N930F using XDA-Developers mobile app
CerveCesar said:
I'm staying factory. I did not disable the 80% battery option because we ran a study and found overcharging to be 1 of 3 factors in starting fires. If Samsung sends the Nougat update, then I will just update. The customs ROMs I'm not a big fan of, because it seem one always looses some cool feature like heart monitor, Samsung Pay or scanner. I got a Note 3 that I plan to use as my flying phone and my Note 7 will be my daily driver
Click to expand...
Click to collapse
Do you mean 60% battery limitation update? Fyi I spoke with a samsung rep today that had called into one of the stores, he believes there is a kill type update coming to force customers hands. I have the 1st addition (non batt update) so if I was to keep it I would have to root. As mentioned wifi calling is also an issue. Samsungs got a lot to answer for ditching such a great device and one that can be repaired
ccsuk said:
Do you mean 60% battery limitation update? Fyi I spoke with a samsung rep today that had called into one of the stores, he believes there is a kill type update coming to force customers hands. I have the 1st addition (non batt update) so if I was to keep it I would have to root. As mentioned wifi calling is also an issue. Samsungs got a lot to answer for ditching such a great device and one that can be repaired
Click to expand...
Click to collapse
Unless they have a Sprint Note 7 60% otherwise you can bump up to 80% charge. I recommend you get advise from an Engineer rather than a Sales Rep
I no longer have the pictures but click:
1.- Settings
2.- Device Maintenance
3.- Battery Icon
4.- Advanced Settings Menu
5.- Disable the "Limit maximum charge to 60%" tab
?
Sent from my SM-N930F using XDA-Developers mobile app
ccsuk said:
Samsung can't help because I didn't buy it direct and Vodafone said it was giving to me as a gift and not linked to my account so I need to deal with Samsung. I know this sounds ludicrous but Vodafone are a nightmare and I was ready to book myself into rehab after the effects of previous issues. I could take this up with an ombudsman but it takes time and I'm not sure I have the energy.
Click to expand...
Click to collapse
CerveCesar said:
The recall is voluntary. Do not believe those people who say your IMEI will be blocked or barred. It will only be blocked if the phone was purchased in a payment plan and You fail to return it. Or if You fail to keep the payments. The recall is absolutely VOLUNTARY. Do not be afraid. Many of us are keeping the phone, because we know the risk is now minimal.
All electronics have the possibility to fail. All batteries have the risk of catching fires. This risk is a lot greater when the device begins their lifecycle. So now the risk is minimal. Samsung did not take "probability" into consideration before sending those replacement phones. Meaning if you had 50 in 2 million to catch fire with the original. Now you had 50+30* of catching fire in the replacement. (*More o Less)
Samsung has a great opportunity to collect data and usage information with us. Otherwise if people panic they will just scrap the Note Series all together.
Good Luck! ?
Sent from my SM-N930F using XDA-Developers mobile app
Click to expand...
Click to collapse
I just want to be clear about something. You guys are from the UK, yes?
Is the recall not the same as the US or elsewhere where the recall is mandatory and not voluntary?
BozQ said:
I just want to be clear about something. You guys are from the UK, yes?
Is the recall not the same as the US or elsewhere where the recall is mandatory and not voluntary?
Click to expand...
Click to collapse
I'm not from the UK however I did purchase the Singapore (Same as UK) version and I'm using it on ATT Mexico.
Please refer to the Voluntary recall at: http://www.samsung.com/us/note7recall/
As of today the recall is only mandatory in Germany. Note 7 is banned on all flights in the US and part of Mexico. The mandatory recall will take time as the Consumer Product Safety Commission has to run a full investigation on the matter
Sent from my SM-N930F using XDA-Developers mobile app
BozQ said:
I just want to be clear about something. You guys are from the UK, yes?
Is the recall not the same as the US or elsewhere where the recall is mandatory and not voluntary?
Click to expand...
Click to collapse
I am
CerveCesar said:
I'm not from the UK however I did purchase the Singapore (Same as UK) version and I'm using it on ATT Mexico.
Please refer to the Voluntary recall at: http://www.samsung.com/us/note7recall/
As of today the recall is only mandatory in Germany. Note 7 is banned on all flights in the US and part of Mexico. The mandatory recall will take time as the Consumer Product Safety Commission has to run a full investigation on the matter
Sent from my SM-N930F using XDA-Developers mobile app
Click to expand...
Click to collapse
Hello from Singapore then.
I suppose you're keeping your unit then.
I recently got the a520f after a few years with the iPhone. I was happy enough but then released there is 2 roms, 1 in alpha and another which is abandoned then noticed the updates from Samsung are sparse at best.
I'm unlocked in UK and stuck on 6.0.1, they "used" to say unlocked got updates first, noticed the way I said "used to" because carriers seem to be releasing 7.0 before unlocked, and while on the point 7.0 at this stage when Oreo will soon be released, even bringing the phone out with 7.0 would have been slow when 7.1 was available.
I am thinking I have made the wrong decision with the a520, Samsung are slow with updates anyway yes but the a520 seems to be at the bottom of Samsungs list of priorities. Last years a510 even has 7 for a while now.
hi !
Yes ,all people here want updates with another android version but i think that the most important thing is to enjoy with this phone :
it's a device with MM6 have enought power for to play game , it have the best super amoled screen ,it have a fabulous battery life ! , a fingerprints and "near" 20 differents sensors ,he have a good modem and hardware for 4G , this MM + sansung adds have all useful functions and parameters ....and the middle economic mode is impressive for the battery life...
The phone is receiving updates slowly cause the phone has owners all around the world, it's probably to make sure that OTA servers are not overloaded. Imagine what would happen if they released it at the same time for the whole world, the servers couldn't deliver acceptable speeds. That's just my guess though.
Nah, Samsung kinda sucks. I mean they couldnt make a proper working fingerprint sensor on stock MM, had to install nougat for the bloody thing to work.
aoyanagi said:
The phone is receiving updates slowly cause the phone has owners all around the world, it's probably to make sure that OTA servers are not overloaded. Imagine what would happen if they released it at the same time for the whole world, the servers couldn't deliver acceptable speeds. That's just my guess though.
Click to expand...
Click to collapse
How does Apple cope then?
That's Samsung decision to release update or not, as user we can wait for it or complaints to Samsung
Sent from my SM-A520F using Tapatalk
It has nothing to do with "the server not able to cope" or anything. There are a few reasons building up to the devices being in literally the bottom of the pile as you put it:
1) Samsung has heavily skinned Android with a lot of added features, which all take a while to port to a new verison.
2) Costs of development, Q/A testing and everything else that needs to be done before the update gets released public (not doing the update obviously means a lot of saved money)
3) Most people don't care about updates or are even annoyed by them and think they are something evil. That's excluding heavy updates to a new version which slow down the phone by a large margin with features you could have lived without (Apple are doing this), those updates really are evil. Due to the lack of updates though, this rarely happens on Android in all fairness.
4) It's a mid range price device
5) Samsung's policy of not wanting to update the phones too much anyway so the user buys a new one
The phone is probably going to be updated to 7.0 within the next month or two. I doubt extremely it will get updated to 8.0.
This is unacceptable for a phone that has come out for 2017, to not got an update of an OS to a version that is released in 2017 just a little over an year later. We should definetly not put up with it and complain to Samsung however, not on XDA.
We should make sure OEM's take note that we want our phones updated to new Android versions fast for at least a few years, just like iOS devices. And on top of complaining, we should vote with our wallets also. That gets the chain moving.
aoyanagi said:
The phone is receiving updates slowly cause the phone has owners all around the world, it's probably to make sure that OTA servers are not overloaded. Imagine what would happen if they released it at the same time for the whole world, the servers couldn't deliver acceptable speeds. That's just my guess though.
Click to expand...
Click to collapse
That is tackled in another way. Your phone randomly receive updates in batch.
Yes you can get an update if you manually go into settings and download updates.
But again it is automatically provided in random batches.
Samsung is late at updates because they have a large number of models.
Not like Iphone that only support 3 models of past I think.
Samsung also needs to provide stable updates which take a lot of testing.
Again it depends on your country and provider when the start rolling updates.
By the way A5 got certified for oreo.
https://www.wi-fi.org/product-finder-results?keywords=A520f
It has Oreo in Russia now
https://forum.xda-developers.com/samsung-a-series-2017/how-to/sm-a520f-oreo-russia-t3779287
Where can i check if i received this security update, is the krack wifi exploit hardware or software related
is it supposed to come from samsung(hardware) or google(software)
i think both of these companies ditched the note 2 years ago,
anywhere to check if i actually received the update? im only auto update, so i could've received it without my knowledge
mdude22 said:
Where can i check if i received this security update, is the krack wifi exploit hardware or software related
is it supposed to come from samsung(hardware) or google(software)
i think both of these companies ditched the note 2 years ago,
anywhere to check if i actually received the update? im only auto update, so i could've received it without my knowledge
Click to expand...
Click to collapse
Official updates for the note 2 stopped a long time ago.. So the answer would be no, you did not receive any patch, you can try custom roms which are regularly updated by developers and most will be patched sooner or later, but the official android provided by samsung has almost no chance of getting any patch, in fact I am sure it won't get any patches from Samsung. And Google in no way will provide support for phones from other companies.
that's too bad, seems like a waste of a good phone to purchase a new one,
Im going to install LineageOS, from what i read online, that one supports my phone and it seems to have a good community
NOTE: Either it has been a f***ing big time coincidence, or it was triggered on Samsung servers somehow (?) by trying to download the firmware to my notebook using SAMFIRM (it was identified, R805FXXU1ESI1, but failed to download), or Samsung reacted real quick to this post, but anyway in a matter of hours after posting this I'm getting the September update through the official channel (Galaxy Wearable app). The updates below were posted before this very note. Just installed. Loving the new look and all features and corrections I mentioned are there! At the time of this writing the online documentation (https://doc.samsungmobile.com/SM-R805F/ZTA/doc.html) still points to the February update (R805FXXU1DSB3, posted in May). EDIT: the update introduced a known bug, one that makes the watch disconnect while updating bundled apps and the update stalls. I guess this may be why Samsung was holding back the updates. OMG. A patch that solves a problem but introduces another. Like Microsoft with "Windwoes" 10.
UPDATE: now it doesn't even serve as a watch. It entered Daylight Savings Time, which has been abolished in the country, and the time settings option is grayed out. Well done, "Sam-Jong"!
UPDATE 2: it looks like there are builds for all regions up to September, but Sam-Jong is lazy enough not to publish them. Just change the region code (ZTA) in the link below and check it.
http://fota-cloud-dn.ospserver.net/firmware/ZTA/SM-R805F/version.test.xml
UPDATE 3: there is even an October update for region TGY:
http://fota-cloud-dn.ospserver.net/firmware/TGY/SM-R805F/version.test.xml
Samsung is holding off these releases for some obscure reason. One of them could be sabotaging Galaxy Watch to favor the Active lineup, like they did to the Note 9 to favor the Note 10.
***
I have an expensive Galaxy Watch LTE, a high-end product, bought at Claro/Brazil this week, national/legal, model SM-R805F.
I've read that it received an update that allows it to monitor outdoor swim training (at the sea), so I bought the model.
The problem is that, even after the firmware update, it does not offer this function, nor several others that have been announced. The lag in step count in walks goes uncorrected.
I did some research and found out that this same model (SM-R805F) received an update abroad in May, which is already outdated, but here there's no update since February, even more outdated.
What's the reason behind this disrespect towards Brazil, and especially towards the LTE variant, top of the line? The BT variant (model SM-R800, without LTE) was updated here in September. So LTE here is at least 7 months behind BT.
LTE for me is a requirement.
Here follows Samsung's own update documentation.
Germany (DBT Region, carrier-free):
https://doc.samsungmobile.com/SM-R805F/DBT/doc.html (May firmware)
Brazil (ZTA [Claro] and ZVV [Vivo]):
https://doc.samsungmobile.com/SM-R805F/ZTA/doc.html (February firmware)
https://doc.samsungmobile.com/SM-R805F/ZVV/doc.html (February firmware)
The ZTO region (Brazil, carrie-free) does not exist for this model, the following page does not exist:
https://doc.samsungmobile.com/SM-R805F/ZTO/doc.html
although the model is reported on sale by the Samsung Brazil page. It never existed, was never available for sale. Samsung says on its page that it is available in its own stores, but that has not left the papers. I went to several stores and the answer is always the same: "only available at the carriers".
The ZTO region only exists for the BT variant:
https://doc.samsungmobile.com/SM-R800/ZTO/doc.html (September firmware).
I've tried all the way to contact Samsung, chat, Samsung Members app and etc, I tried the number 0800-942-9060, a number that a store dealer gave me, but when I call during office hours a recorded voice informs you that at the moment they cannot answer, and at other times it informs you to call during office hours. A real booby trap.
All the answers I received by the other means were "we can do nothing". They don't even give a justification for what is happening.
I have a laptop, a TV, wired and wireless chargers, a dock, a tablet and a Note, all recent, all Samsung tops, but apparently the king has laid in splendid cradle and thinks he can abandon the user that bets in the company's products.
I am responsible for IT in a growing business, I recently recommended buying more than a dozen Samsung Expert X30 laptops for employees, but I am reviewing this recommendation.
As I said in the note topping the post, the watch finally got a firmware update. But it introduced a known bug, one that makes the watch disconnect while updating bundled apps and the update stalls. I guess this may be why Samsung was holding back the updates. OMG. A patch that solves a problem but introduces another. Like Microsoft with "Windwoes" 10.
Whammamoosha said:
As I said in the note topping the post, the watch finally got a firmware update. But it introduced a known bug, one that makes the watch disconnect while updating bundled apps and the update stalls. I guess this may be why Samsung was holding back the updates. OMG. A patch that solves a problem but introduces another. Like Microsoft with "Windwoes" 10.
Click to expand...
Click to collapse
I'm facing the same problem!
Whammamoosha said:
As I said in the note topping the post, the watch finally got a firmware update. But it introduced a known bug, one that makes the watch disconnect while updating bundled apps and the update stalls. I guess this may be why Samsung was holding back the updates. OMG. A patch that solves a problem but introduces another. Like Microsoft with "Windwoes" 10.
Click to expand...
Click to collapse
I guess I'm one of the lucky ones, Northeastern USA, Verizon 4G, watch (LTE) is SM-805U. Tizen 4.0.0.4, no issue, runs like a top....
Sent from my SM-N976V using Tapatalk
lcvleo said:
I'm facing the same problem!
Click to expand...
Click to collapse
So do I.
Did any of you report the problem to Samsung? If yes, what is the best channel? Samsung Members?
KruseLudsMobile said:
I guess I'm one of the lucky ones, Northeastern USA, Verizon 4G, watch (LTE) is SM-805U. Tizen 4.0.0.4, no issue, runs like a top....
Click to expand...
Click to collapse
The problem is localized. Brazil this time. It surfaced on other countries previously and was corrected.
But it seems Samsung didn't resist keeping its bad reputation with this watch and included the bug on the September update released this early November (2 months late). Gosh.
It's been 20 days since the cursed update and still no word from Samsung other than covering up for all the holes I depicted in this post.
A device that can't update its most meaningful app is something between lameness and insult.
Whammamoosha said:
It's been 20 days since the cursed update and still no word from Samsung other than covering up for all the holes I depicted in this post.
A device that can't update its most meaningful app is something between lameness and insult.
Click to expand...
Click to collapse
welcome to the club. except on my 805w, the app update issue has been going on since june or july's update or something.
also posting and expecting any resolution on xda will not yeild any support on the issue. samsung members and forums would be the most productive way of going about this.
Mine hasnt even pulled the update from earlier in the year. I always said I would never buy Samsung again.
Whammamoosha said:
It's been 20 days since the cursed update and still no word from Samsung other than covering up for all the holes I depicted in this post.
A device that can't update its most meaningful app is something between lameness and insult.
Click to expand...
Click to collapse
Raise a problem via Samsung members, with logs/ screenshot.
As far as I know, Gear side is still working on Tizen 3/4 on R8x5, so it maybe a problem from localization.
---------- Post added at 07:37 AM ---------- Previous post was at 07:25 AM ----------
Whammamoosha said:
It's been 20 days since the cursed update and still no word from Samsung other than covering up for all the holes I depicted in this post.
A device that can't update its most meaningful app is something between lameness and insult.
Click to expand...
Click to collapse
Raise a problem via Samsung members, with logs/ screenshot.
As far as I know, Gear side is still working on Tizen 3/4 on R8x5, so it maybe a problem from localization.
tinhduong said:
Raise a problem via Samsung members, with logs/ screenshot.
As far as I know, Gear side is still working on Tizen 3/4 on R8x5, so it maybe a problem from localization.
---------- Post added at 07:37 AM ---------- Previous post was at 07:25 AM ----------
Raise a problem via Samsung members, with logs/ screenshot.
As far as I know, Gear side is still working on Tizen 3/4 on R8x5, so it maybe a problem from localization.
Click to expand...
Click to collapse
Thanks for trying to help, but I've already raised the whole problem via Samsung Members, XDA, Reddit, the whole lot.
Since it's a long-dwelling, well-known and widespread bug, with thousand of complaints worldwide since it started appearing (and being corrected region-wise/variant-wise for a few random regions/variants), I wasn't supposed to *need* to report anything.
But in this post I reported the DNA of the bug *and* of the lack of support for the LTE variant, and also denounced an evident, just-in-time cover-up by Samsung for the latter.
So there's a plethora of detail here *and* from thousands of baffled users, so what's the point in posting pictures/logs? Had Samsung just picked a SM-R805FZSAZTA unit (in my case), upgraded the OS, factory reset it and tried to update the apps, and *fail* at that, it would have a *live* case to work on, with much more detail than a user could ever provide.
BTW Samsung's standard procedure through Samsung Members in publicly well-known cases is more psychological than technical: ask for pictures and logs to make the user believe the matter is being dealt with when it's actually just buying time. Samsung Members in most cases is *useless*. But Samsung just can't say "Sorry, it's a well-know problem, but due to the lack of standardization and centralization in dealing with our products' issues we're lost and haven't done much since the problem appeared. Some random, lucky regions/variants of the product have been contemplated with a solution, but because it's a mess here we've just introduced the bug again, this time in your region/variant, and it will take some awful time until your product's region/variant catches up".
Some issues can only be resolved when a few big heads roll.