Boot-Loop Bug on Stock Phone - Diagnosis report - Galaxy Note 3 Q&A, Help & Troubleshooting

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Purpose
Synopsis
- This is my report of encountering a Double Boot-Loop.
- My report serves to show that the problem/bug occurs on stock (non-rooted) phones also.
- I have attempted to ascertain the exact triggering event to this bug/problem.
- Note, this Double-Boot-Loop is self-terminating after two boot loops, for which the device is fully operational thereafter. However, when the user initiates a manual reboot, then the double boot-loop reoccurs.
- My hope is that Google and Samsung read such reports on this Forum.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Reference
- This problem has been reported elsewhere on many rooted phones.
- There have been suggestions that this event might be triggered by either:
1) Selinux flag,
2) Knox hardware/software.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Overview
My device
- Samsung Galaxy Note 3
- Stock rom (not rooted)
- Locked to Canadian Bell phone network
What I did do:
- Configure device for user accounts, etc.
- Install apps from Google Play Store.
What I did not do:
- Unlocking of phone was not initiated.
- Rooting of ROM was not initiated.
- Knox security was not activated.
- No apps were installed from third party sources.
- All apps were installed on resident device (not extSdcard).
What worked:
- The factory startup.
- Configuring android settings.
- Creating email accounts.
- Installing apps from Google Play store.
What failed:
- Double-Boot-Loop occurred only after 17 Apps were installed.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Procedure
Procedure leading to boot-loop event:
- I installed 15 initial Apps, then did a reboot.
- Device performed a proper Single-Boot-Loop ... Good.
- In installed 35 more Apps, then did a reboot.
- Device performed a buggy Double-Boot-Loop ... Bad.
- I uninstalled each of the 50 Apps.
- When I uninstalled one, I did a reboot and observed if a double or single boot-loop occurred.
- Each 32 apps of the 50, individually uninstalled, caused a double boot-loop.
- Eventually I had removed 33 Apps, leaving 17 Apps installed.
- At this point the device did a Single boot-loop.
- Without changing the installation count from 17,
- I performed 10 manual reboots. In all but one case a single boot-loop occurred.
- There was one random incident of a double boot-loop.
- I added another App (totally 18 installed). At this point a manual reboot resulted in a double boot-loop.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Followup
- I reduced to total count of installed Apps to below 15, then progressive added more Apps. This time, I would initiate a manual reboot of each individual App installation. The motive there was to allow the Android device to reset of complete any potential pending activities associated with each installation. However, this did not prove to prevent the problem from occurring once the App count got over 15 total.
- I have done a Factory-Reset twice more, and repeated the above procedure. In those subsequent cases I uninstalled the excessive Apps (more than 15) in differing sequences. This was intended to identify a potential culprit App that might be triggering the event. Such did not occur. No one App was found to be the culprit. Instead, the event was always triggered merely by the quantity of Apps installed.
- In one of the Factory-Reset cases, I installed over 50 Apps. At such a high quantity of Apps, the device would occasionally perform a Triple-Boot-Loop.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Conclusions
- This problem/bug occurs on non-rooted stock phones.
- This is triggered by installing more than about 15 Apps.
- This is remedied by reducing the installed Apps to no more than about 15 Apps.
- The number of boot loops can exceed two loops; this occurs when the quantity of installed apps exceed somewhere above 50 Apps.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Recommendations
- I suggest that rebooting after each App installation is not necessary, and does not prevent the problem/bug from eventually arising.
- For users intent on installing more than 15 Apps, I suggest proceed regardless.
- The Double-Boot-Loop merely lengthens the boot sequence from a proper 1-minute for a Single-Loop to 2-minutes for a Double-Loop. Once the boot sequence has concluded, then the device seems to perform properly thereafter within that power-on session. Of course, the next reboot will repeat the multiple boot loops.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Proper reboot
Event: Proper boot sequence
Result: Single boot sequence
M:SS Sound Display Comment
----- ----- ------- ----------------
0:00 ----- Samsung I reboot device
0:10 ----- S.G.N.3 Model
0:30 Music SAMSUNG Company
0:50 Beep Homepage Lock screen, Login
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Buggy reboot
Event: Boot-Loop sequence
Result: Double boot sequence (*)
M:SS Sound Display Comment
----- ----- ------- ----------------
0:00 ----- Samsung User initiated reboot
0:10 ----- S.G.N.3 Model
0:30 Music SAMSUNG Company
0:50 Beep Homepage Lock screen, Login
* 1:10 ----- Samsung Device initiated reboot
* 2:00 Beep Homepage Lock screen, Login
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Related

[Q] How to do the best with what you've got?

Overclocking, underclocking, managing performance, tempoerature, speed, and battery life - for any Droid X phones with gingerbread - and special thanks to all those who are mentioned below and created the programs below as well as links with explanations - and anyone have any corrections and/or other ideas?
The below document has four sections:
A. Simplified - overall concept on the biggest speed bosster - steps A1-A9
B. Simplified "Details" with links to deeper information - the above steps in "A" restated (as B1-B9) how to actually do those steps with links to full details and where to get the files required for each step.
C. Pieces of "must have" software
D. Additional Tips for further porformance increases - some of these make a BIG difference!
- - - -
A. Simplified - overall concept (steps A1-A9):
A1. If you have not yet upgraded your phone, then do so Over The Air (OTA) from your carrier so the carrier has you listed in their records as you having upgraded to the latest ROM (otherwise they may send you reminders or try to upgrade your phone in the background, etc.)
A2. Gingerbread (2.3.3) CANNOT be rooted, you have to root Froyo (2.2.1) so you need to downgrade your phone to that version of the stock ROM FIRST.
A3. Then reboot - and to be able to make phone calls you will be walked through one simple phone call by an automated system from your phone carrier to re-enable your phone to make phone calls with your account. Completely automated by the phone company, no live person on the other end.
A4. Gain superuser (unfettered) access to your phone. "Root" it.
A5. Take steps and install software to set up your phone to be able to upgrade to the newest android "gingerbread" version WITHOUT loosing the root - just doing a plain upgrade you will lose the root.
A6. Then upgrade from rooted Froyo (2.2.1) to Gingerbread (2.3.3) as in B6 below. Note, you can ONLY overclock your phone (using easily found and easily useable software on the market) if you are using a stock ROM that is overclocked - that specific kernel is required besause the overclocking software changes values at specific addresses in the kernel's memory (custom ROMs often have different memory addresses for the overclock settings so the software for overclocking would not work).
A7. The Droid X stock Kernel is designed to only run at 4 specific speeds, but you can set what they are (and the voltages for each) with another piece of software. I use "Android Overclocker" for this. Details below under B7.
A8. Software which allows you to manage what speed is used and when is different from the software that assigned the 4 levels of CPU speed set in the previous step. You want to be able to to set which CPU speeds (frequencies) are used and under which circumstances (CPU load, whether the screen is off, whether or not the phone is above a certain temperature, etc.). My opinion is that SetCPU is the best software for this. Details are below under B8.
- - - -
B. Simplified "Details" with links to deeper information - the above steps restated but how to actually do it with links to full details and the files required for each step:
B1. (as in A1 above): Self Explanatory.
B2. (as in A2 above): Gingerbread (2.3.3) CANNOT be rooted, you have to root Froyo (2.2.1 is used here with the above files), so you have to SBF back to Froyo and root THAT first. So to downgrade from Gingerbread (version 2.3.3 - either rooted with leaked ROM or not, it does not matter) to Froyo (2.2.1) as instructed in this link, http://www.lancelhoff.com/downgrade-gingerbread-to-froyo/). I had to do this using RSDLite - and maybe you should too - the other way is to create a Linux Disc - I built my PC on my own and the Linux disc could not deal with the custom PC components (for instance it would not recognize my PCI cards, and came up with other weird error messages, etc.). When using RSDLite there is a bug in that program mentioned as specified in the link above. (Note: to get around that bug, after you try to load the ROM file and it does not load as specified in the log file as mentioned in the above link - leave the RSDListe program running on your PC when you look at the log - just make a copy of the ROM file as specified in the detailed instructions WHILE RSDLITE IS RUNNING) - and switch the program to using the renamed ROM file - and it will then work like a charm). This link should help as well: "http://www.droidxforums.com/forum/droid-x-sbf/23638-linux-solution-your-windows-rsd-lite-problems.html".
B3. (as in A3 above): Self Explanatory - HOWEVER - DO NOT, DO NOT, put your google userid and password into the phone when it first boots up because automatic upgdates which are totally unecessary will take place with your phone (your contact data from the cloud, etc) which will complicate and slow down the process) and are totally unecessary at this point.
B4. (as in A4 above): You need to allow unfettered superuser access to your phone. To do this, use the files from "http://www.lancelhoff.com/how-to-root-droid-x/" for detailed guidance, root your phone as instructed (using z4root v.1.3.0) as it is now the Froyo (2.2.1 version) and can be rooted.
B5. (as in A5 above): To allow a rooted upgrade of your phone to a newer ROM to Gingerbread (2.3.3) that remains rooted - special steps need to be taken (using any stock ROM with the regular method will 'unroot' your phone so you lose the root). You must us a stock ROM or you will not be able to overlcok your phone. Use the files from this link (http://www.droid-life.com/2011/05/28/download-official-droidx-gingerbread-4-5-596-for-rooted-users/) - and only pay attention to the section entitled "Instructions (running Froyo):". For detailed guidance, bootstrap your phone using "droid 2 bootstrap" (dropid2bootstrap.apk) - notice, DO NOT use any "droid x bootstrap" (droid x bootstrap even for droid x phones often does NOT work with the newer Gingerbread ROM). Also, when moving the two zip files onto your sdcard, rename "Blur_Version.2.3.340.MB810.US-Part1.zip" to "1Blur_Version.2.3.340.MB810.US-Part1.zip" and rename "Blur_Version.2.3.340.MB810.US-Part2.zip" to "2Blur_Version.2.3.340.MB810.US-Part2.zip" (putting the 1 and 2 in front of each file name) or else you will not be able to tell which is which when you are installing them - the screen on the handheld does not show the entire file name - (and they have to be installed in the proper order).
B6. (as in A6 above): Upgrade from rooted Froyo (2.2.1) to Gingerbread (2.3.3) using the files and instructions as shown in this youtube video: "http://youtu.be/bedGIM6pL0E" For more details on all the steps shown in B2-B5 and A2-A5 here is a link showing the earlier parts of the process. Pay special attention to the section where the DROID2BOOTSTRAP program is run, which is what you are doing here for step B6.
B7. (as in A7 above): Android Overclock - to set the speeds allowed for the CPU to run at... The lowest speed that can be set is 300MHZm but the sky is the limit for the highest speed (typically alot of phones become unstable if you set the highest speed to anything above 1250MHZ (1.25GHZ). (The CPU in the Droid X has a normal max of 1000MHZ (1GHZ).) Software I have checked out for this is "Milestone Overclock" which is updated regularly (but did not have the user-friendly level of functionality granularity that I wanted - you could only set the Max level unless you wanted to do some low-level hacking which is a pain).). Another one was "D2 / DX Overclocker" which has more functionality but had not been updated for a long time so users are complaining of support issues. The third and last (which I use) is called "Android Overclocker" which allows you to set the MHZ and voltage for each of the four "slots" (speeds) used by the Kernel for the overclocking. I set up my speeds as 300000 with the voltage - "vsel" value set to 33, then 600000 with vsel of 56, then 9000000 with vsel of 66, and 12500000 with vsel of 80.
B8. (as in A8 above): SetCPU - only used for managing the speeds already available, not specifying what they are. For SetCPU to understand what the four speeds are for that CPU, put a file called SetCPU.txt in the root directory of your sdcard as specified in the instructions for the SetCPU application. The full text of this file is one line with nothing but:
300000,6000000,9000000,1250000
Note, this tool is great for stopping my phone from overheating and to manage the speed properly. With no specific profiles I noticed my phone was ready to melt when it was busy, so I got involved with the profiles. I have only one profile which seems to make everything run really well - it handles the following (read the directions within the application for more details and instructions):
* When screen is off, set speed to min of 300MHZ and max of 300MHZ.
* When battery is less than 3% remaining, min speed of 300 and max speed of 600.
* When temperature is > 52 degress centigrade, min speed = 300 and max speed = 900
* When temperature is > 60 degress centigrade, min speed = 300 and max speed = 600
* When charging, min = 300 and max = 1250 (may be unecessary as that is already my 'default')
- - - -
C. Pieces of "must have" software for your phone with regards to carefully monitoring the temperature and maximizing the performance as well as battery life -
"Temp Monitor" - shows temperature on top barets alarms for temperature warnings.
"Juice Defender" - outstanding software for maximizing your battery.
"AutoKiller Memory Optimizer" - software which is outstanding for managing your memory.
"AnTuTu Benchmark" - for benchmarking your phone
"Root Explorer" - for navigating ALL directories on your phone (and creating/editing text files, etc.)
"SuperBox Pro" - for moving as many applications as possible to you SDcard to save memory - and a toolbox of other good apps.
"Eray" - for deep analysis of your phone's processes, etc. Also has a great widget to put a huge number of switches (wifi, etc) into ne widget on one screen.
"SeePU++" - for showing CPU load and RAM usage realtime in the top bar.
"WidgetLocker" - for replacing the login screen on your phone - and also to alloow you to use the follwogin program to put your name and home phone number on your main lock screen (in case your phone is lost):
"Banner" (see widgetlocker above)
"Widgetsoid" - very granular control over setting up your own widgets, also allows you to put a bunch of switches accessable from your drop-down menu - so you don't have to go away from other programs to for example, turn on your wifi, etc.
"Folder Organizer" - lets you assign one or more custom categories to apps and then you can put shortcuts on your screens to those categories to get a popup window of icons for all the associate apps. As you uninstall and install different apps this will allow yo0u to automatically keep the links on your screens to those apps up to date without going out of your mind.
"Launcher Pro" - Seems to be the quickest and most stable launcher / home screen replacement with extended functionality. "SPB Shell 3D" has the slickes interface I have ever seen for this - but it is at the expense of being a resource and CPU hog and slowing your phone down. "ADW Launcher" I tried also but that seemed to crash pretty often - and also was slower than "Launcher Pro". (NOTE THE SECOND TIP BELOW IN SECTION D.)
"Pulse" - for news - also there a a million of those news apps, CNN, etc. (I noticed CNN launches backfround processes without telling me which I do not like though).
"Fancy Widgets" - Outstanding clock/weather widget for main home screen.
I could go on and on... !
- - -
D. Additional Tips for further porformance increases - some of these make a BIG difference!
Use the "SetCPU" widget instead of the "Android Overclocker" widget in my opinion - uses less screen real estate (both verify your overclocking/underclocking is running as expected)).
When installing a launcher over your generic android home screen setup, first DELETE all the widgets on the default home screen before installing the launcher. I was not originally aware of this but those widgets on the old generic android screens are all running in the background although you have them all vovered up by your own different launcher. Even before I did any overclocking I noticed a very big difference in performance when I got rid of all those hidden unused running widgets.
Go into the Amazon Marketplace and start using it. They have a free (different) application every day (which are normally paid applications but you can get them free!). I look at this every day and sometimes do not install the application of the day but often do. If there is an app there you want but you don't want to install it, Install it anyway and then uninstall it. Then you could install it later for free when you are ready (instead of paying for it then).
There also is an Amazon MP3 store which has a free song of the day as well (although I have not used that very much - it seems the soongs are never hits that I like).
Thanks for istening to my diatribe - and anyone have any corrections/additions/suggestions? DeOdexed - ? Any other ideas?
Update to Gingerbread (to fix gingerbread bugs) pushed from Verizon...
Starting today there are messages on my phone with a countdown timer asking for permission to give me an update to gingerbread. If I do not respond, it installs anyway.
My research Finds it does fix some bugs but also removes the rooting, disables google maps, and may put other software and restrictions on your phone that you do not want.
However, I think I found a work around. There is news that a clockwork mod does not have this issue - but I had no backup so I bought titanium backup plus. in titanium backup just go and the application called updater 2.3.3 and 'freeze' it. Fortunately that did not stop updates from the marketplace from google and amazon for applications.
I have not received any more software update requests but it has only been a couple hours and time will tell. Thoughts on any of this from anyone?
Sent from my DROIDX using XDA Premium App
Chainfire, can be a nice help. At least for my X it is.
Sent from my DROIDX using XDA Premium App
Chainfire... also SD Speed
Chainfire is a good idea, I have to check that out. I also updated my SD card cache from the measly 128K to 2048K, which seems to help further...

[Q] S4 9505 - suddelny slow / stuttery - any hints? [solved]

I have this weird problem with my S4, that just surfaced yesterday. Overall it just feels a little slow and laggy. For example the home screen left-right-swipe animation looks like it's rendered at ~10 fps, same with scrolling lists. I know for certain that this was better just a few days ago.
What i'm running:
- Stock Rom (XXUBMEA) + Root
- Some apps removed (Widgets, some Samsung Apps, some Google Apps)
Things i recently tried / changed:
- I just installed tasker
- I used Titanium Backup for the first time
Things i already checked:
- There's no energy-saving setting enabled
- There's nothing running out of the ordinary (Settings / Apps / Running)
- System-Load is not outrageous (around 2.0 for 1m, 5m and 15m)
- I deactivated tasker and titanium (see below)
- Rebooting does not help
I am mentioning Titanium Backup, because this is probably the most invasive thing i did to my phone over the past 1-2 days. I did a full "Backup user apps and system data" run, after which my wallpaper was missing and my keyboard was reset to the Samsung one. Also, the clock on my lock screen (stock samsung) didn't run anymore (though this was fixed by a reboot).
I hope any of you guys can give me a pointer in the right direction. Right now, i don't really know where else to look.
solved: Samsung Push Service made things very slow.
Well, that was a short first introduction.
The answer was indeed already in here:
[Q] Samsung S4 somewhat sluggish and slow?
I just uninstalled Samsung Push Service - and it really seems to solve the problem?
I wish to apologize by the people developing Tasker and Titanium Backup for even suggesting that this could have been their fault.
Anyway, thanks for reading. Maybe this is still useful to someone googling the issue in my words

Annoying "service enabled" toasts

Been getting them, more often (or at least it feels like it).
Generic message, so I can't tell which app or system generating them.
How would you troubleshoot this, without phone reset?
Brand new and Bone stock 4.3, haven't had a chance to root yet.
Thanks.
gidal said:
Been getting them, more often (or at least it feels like it).
Generic message, so I can't tell which app or system generating them.
How would you troubleshoot this, without phone reset?
Click to expand...
Click to collapse
One way to solve it isn't nice, but it works:
1. Root, make nandroid backup (subsequent steps are risky), and install Titanium Backup
2. Filter for user apps
3. Disable everything
4. Reboot and confirm that problem is gone.
5. Enable the first 1/2 of the apps. (In the batch operations menu, long press an app in the middle and choose "Select all below".)
If the problem has returned:
- Of the enabled apps, one is bad. Disable half of those enabled apps.
- Go to step 5.
If the problem is still gone:
- One of the still disabled apps is causing the problem. Enable half of the most recently disabled apps.
- Go to step 5.
This method is a little time consuming, but not as bad as it seems. For 125 user apps, it will take 7 iterations to find the culprit. For fewer user apps, it will take less time. If you disable ALL user apps and the problem persists, the issue is with system data and you need to wipe some system app's data or factory reset.
fenstre said:
One way to solve it isn't nice, but it works:
1. Root, make nandroid backup (subsequent steps are risky), and install Titanium Backup
2. Filter for user apps
3. Disable everything
4. Reboot and confirm that problem is gone.
5. Enable the first 1/2 of the apps. (In the batch operations menu, long press an app in the middle and choose "Select all below".)
If the problem has returned:
- Of the enabled apps, one is bad. Disable half of those enabled apps.
- Go to step 5.
If the problem is still gone:
- One of the still disabled apps is causing the problem. Enable half of the most recently disabled apps.
- Go to step 5.
This method is a little time consuming, but not as bad as it seems. For 125 user apps, it will take 7 iterations to find the culprit. For fewer user apps, it will take less time. If you disable ALL user apps and the problem persists, the issue is with system data and you need to wipe some system app's data or factory reset.
Click to expand...
Click to collapse
Thanks - very good troubleshooting technique.
I'll do that this weekend. I'm afraid it's due to some system apps that I disabled. Thing is, I reenabled all and still getting the toasts. I'll probably do a factory reset and install my apps one at a time.
What's weird is, this is what I usually do when I get new Android device. Only this N4 responds differently to my initial set up process.
Found the culprit, it was flip silent. I didn't suspect it at first since I've been using it with my other Android devices, including on CM10.2 (4.3), and never ran into toasts issue like with N4.

Apps crashing when trying to load web content, Android System Webview problem?

Hi, so I've been having a serious issue with my Oneplus Two that I've been trying to troubleshoot for 2 months now and I feel like I've done everything but still have the issue. Wondering if I can get a second/third opinion or something.
My OS is currently Oxygen 2.2.0.
I've noticed many of my apps very frequently crash to the launcher when attempting to do specific actions. No messages, no "app has stopped responding". Just freeze, then launcher. These actions include:
* Opening an email in gmail
* Searching for something in Google now (what's funny is Google New will respond, and then mid-sentence stop, and boom crash, every time)
* Opening specific pages in the Steam app that looks like it loads web pages in the app?
* Pretty much every time a webpage is loaded in an app.
It doesn't crash every time, but I would say 85% of the time it does. After doing some research I started to look into the Android System Webview app as a possible source, since the phone runs flawlessly in every other aspect with no crashing, except when I specifically do those actions listed above. Also, when I notice that it keeps crashing, I've force stopped the Android System Webview app, then went and tried to open an email for example and it works. But 15 minutes later it begins crashing again.
What I've tried:
* Force stopped the ASW app
* Uninstalled all updates to ASW
* Re-installed the updates to ASW
* Factory reset the phone (what's funny about this one is even after factor resetting, there's a point in the initial setup where the setup app actually crashes when it tries to load the Google authenticator page and goes back to the beginning, thus making it impossible to complete the setup. Eventually after trying like 20 times it doesn't crash and allows you to complete.)
I'm convinced it's ASW and that's the only thing that makes sense, but I've tried everything to get it to work but this problem is still present across multiple factory resets and TWRP installations. I'm at a loss. Any ideas?
Strange, works great for me every time. Did you delete /Android/ folder when you resetet your phone? Maybe the failure sticks in there.
Donald Nice said:
Strange, works great for me every time. Did you delete /Android/ folder when you resetet your phone? Maybe the failure sticks in there.
Click to expand...
Click to collapse
No I didn't, I just did the standard TWRP wipe data/factory reset bit. I'll give that a shot though and see if it helps. Will edit back with results.
Uninstall updates of web view and see the difference.
If problem persists than format and don't update web view.

There is an easy way to discover what causes a phone reboot?

Master, my Nexus 6P is rebooting , and I am quite sure that some app is responsible for this.
Please, there is any way to discover what app was responsible for the reboot, like a log file that register the last logs before a kernel panic?
Thanks!!
Search for logcat. Should be droid info you're looking for.
For information and feedback, I am using the phone without reboots for 5 days. First I removed Snapchat and downgraded all applications I participate as tester from Beta to last released version, but the reboots still happened.
So I removed some players widgets (groove, tunein and spotify) but the reboots still happened.
So I disabled System UI Tuner (I used to display the battery percentage in batt icon) and cleaned up the Settings cache to remove the developer settings (I do not enabled any option there) and I do not seen any reboot since this Settings cleanup o/

Categories

Resources