renfred89
Arch-Supremacy Member
- Joined
- Nov 11, 2007
- Messages
- 17,520
- Reaction score
- 19
then you carry on lor... everyone is moving forward and you still sitting there. hahas...
Galaxy Note 3 4.4.2 Kit Kat update
- Thread starter Jurong640
- Start date
then you carry on lor... everyone is moving forward and you still sitting there. hahas...
renfred89
Arch-Supremacy Member
- Joined
- Nov 11, 2007
- Messages
- 17,520
- Reaction score
- 19
kies 3 doesn't update, it only install a fresh copy of firmware without affecting user data.
If you ask me, i prefer kies 3 than OTA.
zXioNGz
Supremacy Member
- Joined
- Oct 7, 2008
- Messages
- 9,520
- Reaction score
- 235
renfred89
Arch-Supremacy Member
- Joined
- Nov 11, 2007
- Messages
- 17,520
- Reaction score
- 19
Moving forward with regrets and problems, no thanks
actually depends. I don't find any problems because the problems encountered by other users are not problems to me. I don't write to exSD, and I don't root. Therefore I welcome new updates provided it is known to be stable.
With the new update, my battery life is better than before, why not? hahas
user preference bah.. hahas
zXioNGz
Supremacy Member
- Joined
- Oct 7, 2008
- Messages
- 9,520
- Reaction score
- 235
Haha, true, because for my case I also replaced my motherboard that's why I can't update OTA or Kies 3... Have to trouble go down.
Battery non-issue got the freebie extra battery and external Charger haha
Sharing my experience with kitkat update on N3.
Frequent random reboot after the update. This was happening at every few minutes if the phone was under heavy usage. factory rebuild several times and clear cache didn't fix the problem. It has gotten annoying to the point that I have to switch to a backup phone. Either internal ic or overheat problem.
Sent it to Service center. After 3 days it came back the officer said they couldn't detect the random hang issue, and reflashed the firmware. Obviously It came back unfixed.
Waited couple of weeks and saw the new firmware update. Patched it and problem persist. Somewhere in hwz I read that this could be fixed by replacing the mb.
Sent to service center second time. Took the effort to explain to them I want the motherboard to be replaced. Customer service wrote down all the details (random freeze, second visit, need motherboard replace etc).
3 days later went back and again the officer told me they couldn't duplicate the issue and did a reflash of firmware. The invoice has a BIG QC Pass chop. I wonder what kind of QC work did they do behind the wall. I did a test on the spot and showed to them the phone hanged and rebooted. Your fix didn't work!
Here came the best part: The customer service took my phone, navigated to the RAM screen and calmly told me "Sir, you see this RAM status. If you run a lot of apps, and it maxed out all the memory, your phone will restart."
Despite my best effort to be reasonable after wasting the time and effort, this last sentence did it in. Being ignorant is one thing, taking your customer as an idiot is another. How can Samsung allowed for such idiotic reply for one of the flagship products.
Anyway, after giving him my 200 dollars worth of view, I have asked for the manager, re-emphasized the whole situation, and after yet another 3 days, the phone came back with motherboard being replaced, and problem no more.
This much I have to say about Samsung after sale customer care.
Sorry for long post.
Frequent random reboot after the update. This was happening at every few minutes if the phone was under heavy usage. factory rebuild several times and clear cache didn't fix the problem. It has gotten annoying to the point that I have to switch to a backup phone. Either internal ic or overheat problem.
Sent it to Service center. After 3 days it came back the officer said they couldn't detect the random hang issue, and reflashed the firmware. Obviously It came back unfixed.
Waited couple of weeks and saw the new firmware update. Patched it and problem persist. Somewhere in hwz I read that this could be fixed by replacing the mb.
Sent to service center second time. Took the effort to explain to them I want the motherboard to be replaced. Customer service wrote down all the details (random freeze, second visit, need motherboard replace etc).
3 days later went back and again the officer told me they couldn't duplicate the issue and did a reflash of firmware. The invoice has a BIG QC Pass chop. I wonder what kind of QC work did they do behind the wall. I did a test on the spot and showed to them the phone hanged and rebooted. Your fix didn't work!
Here came the best part: The customer service took my phone, navigated to the RAM screen and calmly told me "Sir, you see this RAM status. If you run a lot of apps, and it maxed out all the memory, your phone will restart."
Despite my best effort to be reasonable after wasting the time and effort, this last sentence did it in. Being ignorant is one thing, taking your customer as an idiot is another. How can Samsung allowed for such idiotic reply for one of the flagship products.
Anyway, after giving him my 200 dollars worth of view, I have asked for the manager, re-emphasized the whole situation, and after yet another 3 days, the phone came back with motherboard being replaced, and problem no more.
This much I have to say about Samsung after sale customer care.
Sorry for long post.
I still have this problem that the Google music playing music until half way no sound. Check the phone and try to reboot it. Have to wait for about 10 mins and it keeps showing an error message. Sometimes I simply open the back cover and remove the battery. Anyone encounter similar issue before?
How did you do the test?
jesgirl
Arch-Supremacy Member
- Joined
- Apr 16, 2008
- Messages
- 12,549
- Reaction score
- 14
"A common misunderstanding about Android multitasking is the difference between a process and an application. In Android these are not tightly coupled entities: applications may seem present to the user without an actual process currently running the app; multiple applications may share processes, or one application may make use of multiple processes depending on its needs; the process(es) of an application may be kept around by Android even when that application is not actively doing something.
The fact that you can see an application's process "running" does not mean the application is running or doing anything. It may simply be there because Android needed it at some point, and has decided that it would be best to keep it around in case it needs it again. Likewise, you may leave an application for a little bit and return to it from where you left off, and during that time Android may have needed to get rid of the process for other things.
A key to how Android handles applications in this way is that processes don't shut down cleanly. When the user leaves an application, its process is kept around in the background, allowing it to continue working (for example downloading web pages) if needed, and come immediately to the foreground if the user returns to it. If a device never runs out of memory, then Android will keep all of these processes around, truly leaving all applications "running" all of the time.
Of course, there is a limited amount of memory, and to accommodate this Android must decide when to get rid of processes that are not needed. This leads to Android's process lifecycle, the rules it uses to decide how important each process is and thus the next one that should be dropped. These rules are based on both how important a process is for the user's current experience, as well as how long it has been since the process was last needed by the user.
Once Android determines that it needs to remove a process, it does this brutally, simply force-killing it. The kernel can then immediately reclaim all resources needed by the process, without relying on that application being well written and responsive to a polite request to exit. Allowing the kernel to immediately reclaim application resources makes it a lot easier to avoid serious out of memory situations."
Never reboot, dun bluff
Multitasking the Android Way | Android Developers Blog
The fact that you can see an application's process "running" does not mean the application is running or doing anything. It may simply be there because Android needed it at some point, and has decided that it would be best to keep it around in case it needs it again. Likewise, you may leave an application for a little bit and return to it from where you left off, and during that time Android may have needed to get rid of the process for other things.
A key to how Android handles applications in this way is that processes don't shut down cleanly. When the user leaves an application, its process is kept around in the background, allowing it to continue working (for example downloading web pages) if needed, and come immediately to the foreground if the user returns to it. If a device never runs out of memory, then Android will keep all of these processes around, truly leaving all applications "running" all of the time.
Of course, there is a limited amount of memory, and to accommodate this Android must decide when to get rid of processes that are not needed. This leads to Android's process lifecycle, the rules it uses to decide how important each process is and thus the next one that should be dropped. These rules are based on both how important a process is for the user's current experience, as well as how long it has been since the process was last needed by the user.
Once Android determines that it needs to remove a process, it does this brutally, simply force-killing it. The kernel can then immediately reclaim all resources needed by the process, without relying on that application being well written and responsive to a polite request to exit. Allowing the kernel to immediately reclaim application resources makes it a lot easier to avoid serious out of memory situations."
Never reboot, dun bluff
Multitasking the Android Way | Android Developers Blog
It's actually from your SIM card, that's why it cannot be deleted. Not all SIM cards have that network pre-installed. My SingTel one does, and it's quite irritating when my Note Pro decides to suddenly attempt to connect to that worthless network.
KwayChup
Senior Member
- Joined
- Dec 12, 2013
- Messages
- 1,498
- Reaction score
- 62
The Note 3 was fine until the latest firmware update cause battery drain fast.
mine also! i slept with 60+ percent and woke up with my phone dead. thought it was SDS totally scared me LOL
After the update yesterday mine freeze a few times and got to press on loooong restart button to reboot, and yet it auto rebooted every 1 or 2 hours. Will monitor again today. Just woke up...
renfred89
Arch-Supremacy Member
- Joined
- Nov 11, 2007
- Messages
- 17,520
- Reaction score
- 19
After the update yesterday mine freeze a few times and got to press on loooong restart button to reboot, and yet it auto rebooted every 1 or 2 hours. Will monitor again today. Just woke up...
If u inserted a microsd card, remove it and observe again. Sometimes defective card can cause such symptoms due to short circuit.
Oh thanks thanks. I will do it and monitor again. have a great weekend guys!
dexterkim
High Supremacy Member
- Joined
- Jun 6, 2011
- Messages
- 28,426
- Reaction score
- 4,508
The Note 3 was fine until the latest firmware update cause battery drain fast.
mine also
- Joined
- Nov 27, 2000
- Messages
- 28,588
- Reaction score
- 8,209
The index service is draining the battery fast after updating to ND3.
renfred89
Arch-Supremacy Member
- Joined
- Nov 11, 2007
- Messages
- 17,520
- Reaction score
- 19
mine also
Meeee toooo... sigh...
Important Forum Advisory Note
This forum is moderated by volunteer moderators who will react only to members' feedback on posts. Moderators are not employees or representatives of HWZ Forums. Forum members and moderators are responsible for their own posts.
Please refer to our Community Guidelines and Standards and Terms and Conditions for more information.
