Develop Bugs

Error messages, process failure

Hello, I have a weird situation on my hands here and was wondering if you might be able to help.
Firstly...
HTC incredible.
CM-7.0.3 stable (most recent)
CM kernel2.6.37.4 #27
Overckocled 1.1GHz
radio 2.15.00.09.01 (going to work now, need to update, just saw it was outdated)
Long story short.
my phone has been working fine, no issues whatsoever until yesterday. Yesterday my Market app and browser started crashing as soon as I started them.
Today more things are crashing, and at a much higher rate of failure. Normally I would just clear the cache, and the applications cache, and the problem would be fixed (this has been a problem in the past) however this is more than just one application.
popup error reporting reports that specific applications have failed (market, browser, etc), but I also get general "framework" crash popups. Ideas?
Side note. I am also noticing a very long startup time on restarts, much longer than in the past.
I have not made any recent changes to my phone (over-clocking, kernels, radios, ROMS) other than of course installing apps.
Warning message example.
com.android.market
com.google.processes.gapps
android.processes.media
Ideas

first thing i would do is clear cache and dalvik cache and try fixing permissions.
If those don't work which I won't be surprised if they don't I would...
clear all data and reflash the ROM. Quick and Painless with titanium backup.

I already cleared the caches and fixed permissions.
I know re-flashing everything will work, and I have doen that in the past, however I am really tired of it. It seems to be mort stable now, and almost fixed completely. (I didn't change anything after repair attempts stated above)
My question is really what ic causing this, and is there anything I can do to stop this from happening.

If this is something that happens all the time.... must be something you are specifically doing.
My friends inc was doin the same.thing. I couldn't even get into Rom manager or titanium. Never ran into that problem before in almost a year with the inc. Reflashing was the only thing that worked. As for the cause... its a computer. Computers don't need reasons to go hay wire.
There was a time my inc wouldn't stop rebooting... multiple times a day... very annoying. Did everything including goin back to stock. One day after a couple months of that crap.... it just stopped randomly rebooting...

Well...
Firstly I agree, but dont know why...
This happens with different severity levels on average .9 times a month.
The strange thing is that I do nothing specifically at the time to cause this. No kernel installs, reflashes, rom updates, radio updates, or anything specific. It is just general use. It is not as if this happens as soon as I do anything in particular.
Any thought on any specific configurations that might cause this to happen over time, or settings that I can change? I would understand this happening on a system update, or major change, but that does not seem to be the cause in this case, or any other times this has happened.

What I would do...
Go completely back to stock. Run that for a month. If it STILL happens... take it to Verizon to exchange for a new one cause this isn't normal.

Thats the thing...
Hmmm... I have considered doing that. I am not sure I want to go through the trouble. Any other thoughts? (assuming that the phone itself is fine for the sake of this thread.)

[Q] Maps/Navigation force closing on custom ROM/Kernel - HELP Please!

Hi all,
Hopefully someone can shed some light on this and help a tortured soul. By no means am I an Android expert, but I definitely am not a noob. I had an S2 in the past and done plenty of flashing there, and now own a Bell SGH-I747M S3... my precious...
First off I tried a whole bunch of different ROMs, of all flavors (AOSP, AOKP, CM10, PARANOID, and some TW), and a lot of them are awesome. However, I found that after having done so much flashing and customizing using other people's work, it was now time for me and attempt to make my own ROM. I feel I now have the knowledge to do so. Don't get me wrong, I am far from a Dev, and I don't do much coding at all. I found this great suite called Android Kitchen, which pretty much guides you through the steps for making your own ROM, and it's great for learning.
In the end, I was able to come up with a final working version of my own ROM, built from scratch using the original official Bell JB 4.1.1 update file. and I have to say I am quite proud of it, as it has all the apps, features and theming that I want, and works quite well I might add. I get great results performance and battery wise (for my taste and needs) when using my ROM with KToonsez kernel.
BUT!!... as good as I think the ROM is, it is unfortunately not flawless. I do have an issue (the only one I could find so far after 2 weeks using it), and for me it is a BIG issue. Maps/Navigation does not seem to like the ROM/kernel combo on MY phone. I say MY phone because I have setup a friend with pretty much the same thing, and he is not experiencing the same issue.
Here is a description of the problem I get. Let's say I go to my contacts and select one with an address. I will touch the address, then Maps opens no problem, and finds the place, and I also get fast GPS lock, no issues there either. Then I will select Navigate to get a voice turn by turn description while driving. The Nav app starts OK as well and seems to work fine. Then after a few minutes (sometimes 2 sometimes 10), Navigation will shutdown, and I get a pop-up saying "Unfortunately Maps has stopped working...". When I OK that, after a few seconds, Navigation starts talking to me again, although not on screen. Also a Navigation icon will appear in the notification area, and if I hit that it resumes Nav, as if nothing had happened. Another few minutes like that, and then I get the same message again, but this time it crashes for good. ALWAYS!!
Troubleshooting:
- Flashed the ROM/Kernel 3 times now. Always wiping and formatting ALL!
- Cleared cache and data from Android Settings/Applications
- Cleared cache from Maps settings.
- Re-installed Maps
- Wiped phone cache, dalvik cache and fixed permissions from recovery.
- Changed kernel back to stock (that seems to work fine btw,, but I do not want stock kernel, plus the setup I want works well on my friend's S3, same as mine, which I setup myself for him (he's a total noob)).
- Changed kernel again from stock to KToonsez (that also works fine after that, however I get other things that start not working well... too many).
- I always wipe cache, dalvik cache and fix permissions after changing kernels.
I have been poking at this for about a week now, and I am tired! I was hoping someone would have a suggestion, maybe from past experience. The only thing I can think of that is different on his phone and mine is the apps that we restore after installing the ROM and kernel (Titanium Backup, user apps and data only, nothing related to system is touched). I am guessing one of my apps could cause a conflict, but pardon my laziness, but I really do not feel like testing / installing my apps one by one to hopefully without guarantee find a culprit... way too many apps for that So I am testing my luck here on XDA... there are a lot of smart people here
I appologize for the lenghty post, but this way, there is less chance I left anything out... PLEASE HELP!!!
Raz...

Sorry for the bump guys... I was really hoping someone can give some input here. Desperate for a solution here!!
Thanks

So is there no fix/ solution for random reboots?

I got my Nexus 7 when it first came out last year, rooted it, installed TWRP, and have been on several different ROMs since. Didn't have any issues with random reboots for several months. Early this year, I started having an issue where the tablet would freeze while I'm using it, then automatically reboot itself. I thought perhaps it was a problem with the ROM I was running, but I had switched ROMs a few times after that, and every single ROM I've been on since then has had the same problem. It usually only happens when I'm browsing the Internet (with Chrome being my browser of choice), but I've had it happen once while using the camera app, as well.
The other day, I upgraded TWRP to the latest version, and I installed the 4.04 bootloader in preparation for Lollipop ROMs. I was hoping on some slim chance that perhaps an upgraded bootloader might fix the problem, but I'm still getting random reboots.
I know I've seen people talk about random reboots as well, but in the past, I never saw anyone find any kind of solution. Is there one, or is it one of those things I just have to live with, at this point? It's odd to me that I didn't start experiencing this issue right away, and that it only started several months after I had had the device. To me, that makes it seem like it's not a hardware issue/ defect, but I guess no one has been able to pinpoint what the problem is, why it occurs, and how to fix it, huh?

mrw1215 said:
I know I've seen people talk about random reboots as well, but in the past, I never saw anyone find any kind of solution. Is there one, or is it one of those things I just have to live with, at this point? It's odd to me that I didn't start experiencing this issue right away, and that it only started several months after I had had the device. To me, that makes it seem like it's not a hardware issue/ defect, but I guess no one has been able to pinpoint what the problem is, why it occurs, and how to fix it, huh?
Click to expand...
Click to collapse
I'd tend to agree with you it's a software thing. However, my approach would be a bit more radical than yours: that I would erase everything, including formatting the internal storage twice (after making a backup, of course), then install a completely clean rom, use it for a while to make sure it doesn't act up again before restoring any apps.
On the side, I've seen a Nexus doing random reboots whose owner had opened the back and bent the cover somehow, which slightly depressed the power button. While the button operated normally, this condition forced it to "click" randomly, which caused the reboots. It stopped after the owner replaced the back cover. You might want to check this part. Good luck.

Most of the time, random reboots are kernel related. If you are overclocked try to set max CPU lower and see if the problem fixes itself. If you don't overclock try installing something like Trickster Mod, and lower max CPU to see if that helps. What ROM and kernel are you running?
Sent from my 2013 Nexus 7
"Until death, I will remain a Dirty Unicorn.."

I always recommend flashing back to stock to rule out software issues. If it continues, you've got a hardware issue.

I haven't really messed around with kernels, I've typically just used whatever was included in a particular ROM, and I never adjust to overclock or anything like that. I don't remember what all the ROMs I've been on are, but I've been on CM before, and I'm currently using CleanROM. I think the only time I ever specifically tried a different kernel was a while back, when I flashed an Elemental kernel, but I've since wiped and been on a different ROM.
For now, I'm trying to hold out wiping anything until a good, rooted build of Lollipop is available, at which point, I'll try wiping out everything, including internal storage, and see if that helps.
I guess I could also try flashing back to stock before I do that, though. I think I've seen one stock ROM for the N7 floating around. The only problem is, it's really hard to "test" this, because the reboots are very inconsistent. The other day, after I had updated the bootloader, I was browsing Chrome for over an hour before I got a random reboot. One time, I was browsing Chrome for an hour and had 4-5 random reboots within that hour. So, that makes it difficult to determine if it's fixed in a timely manner. :/

Alright, so now that there's a proper build of Lollipop out, I did a factory reset and wiped internal storage (twice), and I'm now running stock Lollipop. I spent about an hour or so getting everything set up, and no reboots thus far; but the reboots mainly occur when I'm using Chrome, and I didn't really do any browsing, as I was getting all my accounts and apps and whatnot set up. Hopefully within the next couple of days, I'll have used it enough to get a good idea as to whether or not I'm still experiencing issues.

So far, no reboots, though i don't want to jinx it, heh... I'll be glad if the issue is finally fixed, but I'll also feel kinda dumb that all it took to fix it was something as simple as wiping internal storage and/ or reflashing a stock ROM. Lollipop is pretty nice, as well.

Yeah I'm using a custom version of L myself. You need to flash custom kernel to get working root access with SuperSU BETA 2.19
Sent from my 2013 Nexus 7
"Until death, I will remain a Dirty Unicorn.."

[Q] Phone freezes and is slow after all kinds of troubleshooting

Hello,
I've done lots of searching for answers to my questions here and elsewhere and come up empty-handed, so I apologize if I've missed something and this has been covered already.
My phone occasionally runs smoothly and fast, like it's supposed to. More often -- pretty much every time I need to interact with the phone and across all apps I use -- it freezes when I tap on something, whether it's to open an app or interact with an app that's already running. It will completely freeze up for anywhere from five to 15 seconds before reacting, and it's extremely frustrating at times. Sometimes, the screen will time out before I can enter my PIN to unlock it; sometimes when somebody calls and I tap "answer," the phone doesn't react fast enough to actually answer and I miss the call. As I said, very frustrating. It did this both before the update to Lollipop last week, and after.
Here's what I've tried: Hard reset; restarting; deleting or disabling all the apps (including Blinkfeed) I thought I safely could, usually just one or two at a time. I've run it in safe mode, and the phone works normally that way -- I just can't figure out what's making it freeze up. I've run a CPU monitor program, and haven't seen any huge spikes from any apps; and according to the app manager in settings, I typically have about 1G of RAM free.
I'm very hesitant to root the phone, mostly because this is a warranty replacement for a Verizon M7 I had rooted (and returned to stock), and none of the ROMs I tried with the previous phone worked well -- if at all -- with the security policies I am required to use to log in to my employer's Exchange server. Those policies include data encryption.
I'm running stock Lollipop 5.0.2 and Sense 6.0 on Build number 6.22.605.3, Baseband 1.13.41.1209.
If anybody has ideas for me to try, I'd greatly appreciate it. My upgrade date is late August of this year, but it's getting harder and harder to live with this phone, which I absolutely need for my work.
Thank you very much in advance.

It's been a month now since the Lollipop update. I have read through a few threads about performance issues in general after the update. I am going to assume that your phone too has become a victim of the update. I have NOT updated to Lollipop. Mainly because of my recent root and install of TWRP custom recovery, EX Kernel and ViperROM 7.0.2. If these issues aren't resolved, I will not update. Besides, KitKat is doing great for me. I would suspect certain services not running in safe mode that allow the phone to react normally as opposed to all services running in normal mode. Have you contacted VZN and/or HTC for possible t/sing solutions? I see that you have done what I would've done. After failing I would assume it is because of the Lollipop update

[Q] Phone problems since day 1.

Hey guys!
Sorry for the long post, I'm going to write down in one post the story of the phone, because I've had so many problems with it (probably because I'm an amateur) since day 1.
1. When I got my phone I had the usual problems, lagging interface, subpar battery life - I installed nova launcher, tried all the best, it was nearly ok.
2. When android 5.0 came out the phone by itself didn't offer it, however when I plugged it in the PC Suite said that there was new software available, so I installed it. This happened again with another update. The weird thing that after every update, when I switched on the phone it said something like 'the current version is not available for user, somethingsomething' as a notification, but I could easily press the side and it disappeared.
3. About a month ago my phone started going crazy. Firstly it overheated really fast. Secondly, which was much more annoying, it rebooted at random times. A week ago it started rebooting so often I could barely use it. I tried monitoring which apps they were, uninstalling but nothing changed.
4. For this reason I rooted, tried memory leak fix, tried greenify and amplify. The problem still persisted. So my thoughts were, that this must be a hardware issue (the reason I thought this, is because sometimes after rebooting it said it had below 20% battery, even if before rebooting it showed 60%).
5. I unrooted (I think I nearly bricked my phone), and put on stock TOT, so I can bring it back to the provider for a fix. Now it has android 4.4.1., the lagging interface is still there, the problems are just like at day 1. However there is no random rebooting, so its not hardware issue, so Im not rushing to my provider (they take a month and dont give substitute phone).
I tried software update again (I'm european d855), but it said there werent any new software available. I would like to have lollipop.
Please can someone explain why it was overheating and how I can have a stable and rock solid android 5.0 on my phone with normal battery life and without lagging interface? I would love to love this phone but it makes my job very difficult
Thank you in advance!

Have you tried any custom ROM?