Just wondering, is Android a ridiculously stupid OS to troubleshoot?
Does android make it very hard to find exactly what the OS is doing? Are problems almost impossible to find, or do people just not know where to look?
The reason I ask, I've had a problem where my phone will often lag for up to 10 seconds, especially upon waking. I've spent over a year searching for the solution, tried all sorts of diagnostic apps, and I've even asked the question in detail multiple times in various places over the past year with zero response.
A 10 second lag should not be hard to diagnose. If it were windows, you could easily look at the task manager and see what errant program is causing it. On android however I have been completely unsuccessful to identify something which should be so blatantly obvious. What's the deal?
Related
Hi everyone, I hope im not being too naive by posting this.
I joined the forums for one thing, to improve my TG01.
Let me explain firstly; ive had my TG01 for a few months now - wasnt happy it was on WinMo as it was, but i managed. Then i saw some Android stuff and decided that was what this phone needed..so i browsed and i browsed...nothing, only got so close to be denied time and time again. haRET actually seen to get the boot screen up, but freezes with about 5 lines of text which is too small to read then resets the device.
What i want to know is, is there any sign of getting Android on the TG01, if so, how long? and if not, what else can i do? I dont know a thing about ROMs, but i want to make this phone all it can be...
Suggestions?
you should follow this thread
http://forum.xda-developers.com/showthread.php?t=672234
Hi,
Please forgive me if there is already a thread existing for this, as I am new here.
I have a question regarding my HTC Sensation XL, which is currently running Android 2.3.
I rooted my phone some time after I got it. I'll admit that my knowledge of such things is extremely limited, so I may have done something stupid. Anyway, I used some sort of one-click-rooting program (I honestly can't remember what it was called) to root my device. The root was successful and I was happy with this. However, I found that this caused my phone to show the bootloader menu, whenever I turned it on.
This caused an issue when I attempted to update my phone to Android 4.0. I could download the update, but the installation would be interrupted upon reboot, due to the bootloader menu showing up (or so it would seem).
To fix this, I attempted to unroot my phone using an app called 'Ginger Unroot', which seemed to work. However, the issue with the bootloader menu interrupting the update still occurs.
I'm aware that I've probably done something very stupid by opting for these one-click methods of rooting/unrooting, as many sites seem to suggest different, more complex methods. This is probably a lesson for me not to mess around with things that I don't quite understand.
Anyways, does anyone have any advice on how I may go about either solving or getting around this problem?
Your help is most appreciated!
N.B: My device has recently started turning itself off for no apparent reason, if that has anything to do with the problem at hand.
I have been having this problem pretty much since day 1, I've also searched the Nokia Support Discussions and it seems quite a lot of people are experiencing this. I was actually surprised that my Go-To forum here at XDA doesn't have a thread on it.
My Black Lumia 920 (EE, Phones4U, Unlocked) reboots on average about 5 times a day. Yesterday was probably the worst yet with roughly 8 reboots. That may have been more noticeable to me because I used a SIM which requires a pin though.
What I've noticed:
-The device is roughly 10 days old.
-It has been rebooting an average of 5-8 times a day
-It mostly reboots when idle (so when I'm not using it)
-I've had it reboot only twice while in use when making a call
-I've had it reboot only once when playing music.
-I've only ever noticed it rebooting when it is face up
-Rebooting happens regardless of the SIM (although I have not used it without a SIM at all) (Used both a micro SIM and a SIM cut down to size, used the original carrier SIM and other SIM, no difference to rebooting behaviour)
-I only turn on the radios I need when I need them, so 2G active 100%, 3G/4G, WiFi, Bluetooth, GPS, NFC off for 70% of the time.
-It is not due to battery drain as I usually have about 40% battery at the end of the day.
This has been my experience with the rebooting problem. The figures and estimates I'm giving are not over stating and I've tried giving as much detail so as to try and provide useful information for a solution.
Has anyone else been having this problem?
Has anyone found a working solution?
Has anyone heard or read anything concerning a fix for this?
nope - blue one on AT&T
I'd look at your installed apps, apps enabled to run in the background, etc. It should not be rebooting at all.
I have seen some posts like yours on the internets, but its not a "common" as in most 920s do it problem. Which leads me to think its some issue with an app or apps installed on some phones.
Possible solution
Hi kyrirhcp
I had a similar problem. I reset the phone which bricked it and then used this tutorial to un-brick it:
http://forums.wpcentral.com/nokia-l...after-reset-flash-process-defined-inside.html
The only difference is that I downloaded the "Nokia Data Package Manager" (not sure where from but I'm sure you can find it). This software allows you to download the firmware files directly into the correct folder. You could also look at this tutorial:
http://aydon.wordpress.com/2012/11/29/how-to-flash-your-lumia-920english/
The ROM you want is the EE specific one. It even specifies the colour of the phone. The version number is: 1232.2110.1244.3011
If you reset the device and it does not brick (i.e. freeze up on reformat) then the problem is solved and you don't need to worry. If it bricks (which it probably will) then you need to flash to recover the phone.
God bless
andrew-in-woking
Hi Andrew, thanks for your suggestions but I'm avoiding it like the plague if I'm honest. Resetting my phone and risking a brick, even with your added fix tutorial really doesn't seem worth it. Also I'm assuming that the problem you PM'd me with regarding the loss of some functionality is a result of the fix you suggest. I'm not yet willing or ready to f with my device the same way as I did with my SGNote, even more so since developers haven't yet gotten the experience they have with android. Anyway, i seem to have perhaps solved the problem at least for my device. I changed the regional settings for a completely unrelated matter and I have not since had a single reset or the accompanying massive battery drain. It's now been 3 days. The only other change was that I removed tunein radio an reinstalled it. So it seems that my problem has been solved (fingers crossed, knock on wood, ftou ftou ftou, wearing an evil eye). I hope this helps others with their problems and makes this amazing device useable to those that had this problem.
Sent from my RM-821_eu_euro1_342 using XDA Windows Phone 7 App
Try removing Whatsapp if you've got that installed.
I have had a lot of the same problems. My phone locks up a few times per day. This is the 2nd Lumia 920 I've had. After getting the second with the same problem, I decided to wait for the Portico update that was supposed to address random restarts.
Since then, I've been communicating with Nokia and Windows Phone support on twitter. All they suggest is uninstalling apps, disabling radios, contacting individual developers, and resetting your phone.
I have a hard time wrapping my mind around that. How is it possible for a user level application to take down the whole operating system/firmware?? There are plenty of crappy apps on the Windows Phone Store, I don't think it should be up to me to figure out which is destroying my experience.
I used to root/hack all my old Windows Mobile phones/android phones. When it locked up, it really was up to me to fix it and figure it out!! I chose Windows Phone since it had the locked ecosystem similar to Apple. While that may not appeal to everyone, I have a very busy life and I don't want to spend more time screwing with my phone. It just needs to work! This is my 3rd Windows phone and it's been the worst so far.
Lately I've been suffering seemingly random FC in multiple apps, Swype keyboard won't popup, lose use of soft buttons, and my device has crashed several times.
Of course this only happens at the most inopportune times.
Device:
Rooted
TWRP
NABD
Nova Launcher
Stock kernel
I'm a long time lurker, fist time poster. Though I've rooted several devices over the years my knowledge level is that of a noob. I have the capability and desire to learn more but need somebody to hold my hand and point me the right direction.
Specifically what would be most helpful at the moment is somebody to walk me through the forensic methodology of tracking down the cause of issues. What to me seems random is surely quite logical, but I don't know what I don't know. And grasping at straws is not my MO.
Or perhaps I'm overthinking this.
Educate me, please.
Could this be related?
For a while this is how Chrome has been loading some pages:
Okay, a dual question here. One specific and one general but they are both related and one will help the other. Hopefully if anyone provides good answers others will find this post useful. I have a Asus Zenfone Selfie which has begun boot-looping. The phone is rooted and has TWRP installed. Once in a while it boots up as far as the home screen, then sometimes only up to the Asus logo. I have flashed several different ROMs (stock and custom) and again, it boots up to the setup screen then only up to the Asus logo so I was assuming this must mean it's hardware related. However, I can boot into TWRP and stay there for hours with no bootlooping. If it were hardware then it should bootloop for TWRP too so it must be software related, right? One more thing: I usually flash in TWRP but many times it crashes during the flash process. Sometimes it does succeed with no issues though. On my PC I might be running some disk or RAM checking tools to see if there was a bad sector or track on my hard drive or a bad module... Yeah, I'm confused. Why is it bootlooping and what, if anything, can I do to fix it?
This leads to my general question. Over the past 20 years I have had several phones, many of which ended up bootlooping. I know the LG G4 & G5 had a hardware flaw that cased them to bootloop and I know screwy flashes can cause bootlooping. But what about all my phones? Some were new, well, only a year or two old, some were 6 or 7 years old. Some were Android, some were Windows Phone. Some were rooted, some were unrooted, some were stock, some were custom ROMs. Some had updated or recently got new apps installed, others hadn't had anything new in ages. Some were in use when they started bootlooping, some were just sitting there. Some had a full charge on the battery, some were close to empty. What can be done to prevent this? What can be done once it has started, especially with one of these newer phones that they STUPIDLY like to make with sealed in batteries. And the given button combination just reboots the phone - again. Depending on who I talk to (or where I read) they say one thing or the other. It's software related. Okay, how? Why? I know on my PC Windows will sometime crash and reboot just for the hell of it, but that's usually just MS fixing an issue with a PC that runs too smoothly. And when that happens, it can be fixed. As an aside to any software developers reading this, I know you may not want to take the time to rewrite everything to work on Linux but you could take a little bit and make your software work with WINE, just a thought guys.
Anyway, so if it's software related, what can really be done to fix it? I can understand the big companies may like it if your phone bootloops so you'll need to buy a new one, but there are tons of developers out there making great custom ROMs. I know they don't have the resources to really fix all the bugs but I assume they would do a better job than certain big companies right? And why would the software suddenly crash like that? Sometimes literally NOTHING is happening, so why the sudden desire to bootloop? What about hardware? Can't we design software to work around the flaw? I would think manufacturers would want to fix problems to make their products as good as they can be but from what we have seen, I guess not. If you read my list above, many of those phones have nothing in common except the bootlooping. So where is the error coming from? Is there really nothing that we can do?
Any ideas and explanations would be appreciated, as would any help on my more recent bootloop device the Asus Zenfone Selfie Z00UD/z00T. Just to mention, that is a newer phone. It may not be now but it bootlooped probably a little over a year ago. It takes me a while to get around to things sometimes, like writing a letter to post on a forum. I had in mind to take it to this one repair shop (they had to replace the USB charging port maybe 3 months before the bootlooping so I assumed there might be a connection) but when I finally got there they told me it was software related and wouldn't look at it. Also, I don't want to make it sound like all my phones bootloop. I have had many many phones that died due to other issues and many more that are still in use, even old ones. I just want to try to understand and grasp any common factors that cause some phones to bootloop, and to maybe use that knowledge to prevent future phones from bootlooping even if I can't repair the ones that already do.
Thanks for your time in reading this and in advance for your answers. If you googled your way here, I hope there is info here that can help you too.