Home › Forums › Galaxy Note discussion forum › Firmware updates like crazy ICS 4.0.4
- This topic has 2 replies, 2 voices, and was last updated 12 years ago by Anonymous.
-
AuthorPosts
-
September 20, 2012 at 11:10 am #448AnonymousInactive
What is going on with 4.0.4 updates ?
Its seems like every week there is another 4.0.4 update. Perhaps i shouldn’t complain given the number of people not getting updates.
The problem being i must encrypt my phone for work (mobile iron) and must decrypt it before updating. Its a pain.
Why isn’t there any published information or release notes about which version does what. Seriously….. three updates in 1 month i gotta wonder whether its even worth updating but without release notes i can’t tell whether its worth going through all the hassle of decryp and encrypt.
Anyone know what PDA:LRT/PHONE:LKR/CSC:LRT adds or changes ? I’ve currently got PDA:LRQ/PHONE:LKR/CSC:LRQ and it seems to have fixed my batter issues however i have had a few device reboots i’ve never seen before.
Come on Samsung please make this whole updating thing a bit clearer.
Thanks
September 20, 2012 at 12:14 pm #451Galaxy NoteMemberUsually you should take such updates because they are usually critical updates, which fix some serious problem in the firmware you re using.
Otherwise, most manufactures will accumulate a large update package.
Yes, Samsung is very poor in communication to its users, perhaps they never expected the big success of their Galaxy series.
September 20, 2012 at 9:55 pm #455AnonymousInactiveok thanks. As longs as its just not just me.
I live in Australia but have a German handset and it appears these phone get a lot of the updates first. If i had the Australian handset i would be still waiting for 4.0.4 or even ICS depending on the carrier.
I wonder if Samsung are breaking more things than they are fixing in their releases. 4.0.4 now has at least three try’s to get it right.
My phone now works OK so i dont want to go forward if it makes things worse.
Anyway thanks
-
AuthorPosts
- You must be logged in to reply to this topic.