Hey,
I'm new to writing in the forum but have been viewing topics for quite some time.
In the past week I had my HTC One X crashing on me with 'com.google.process.gapps' / 'Android.process.acore' has stopped unexpectedly causign all the apps not to work.
I'm running Jelly beans (4.1.1) with Sense 4+.
I browsed the forums for a while and saw suggestions to cancel google internet sync and to clear to contacts cache.
I did both and after it did not help I tried factory reset and recovery boot.
Although things run a bit better i'm still encountering these errors every now and then (and I have to hard boot the device).
Any suggestions how to resolve this issue ? Could it be a hardware malfunction ?
Would love to hear any thoughts on the matter.
full wipe and reflash could solve the problem, or maybe you downloaded a corrupted zip but the ROM still managed to flash - happened to me before.
My phone is not rooted and does not use a custom ROM so I don't think a corrupted zip is the issue. Should I root it just for reflashing it ?
Related
My Desire has intermittent freezing issues. I thought it might have been due to a poor rom installation so I wiped the Dalkvik cache and factory wipe before I re-flashed LeeDroid 2.2a. I've kept the phone clean and not installed any apps so I can rule out and problems caused by them.
It was working fine yesterday until I was showing a friend how to wipe battery stats, when I went to reboot the phone from ClockworkMod it then froze at the lock screen. I had to pull the battery twice before it actually started up correctly.
It's fine now but I'm just waiting on it happening again.
Has anyone else had these issues?
It was a t-mobile uk handset and I would need to restore to their rom before returning, so if that is the likely solution, can someone pass a link so I can put their rom back on the phone.
Any help or advice appreciated.
I've just got my Desire back from repair (after 6 weeks of grief with HTC, but that's another story on another thread!) and it's doing exactly the same as yours....will appear to work fine, then randomly freeze. This could happen after 10 minutes or sometimes even during boot.
I've rooted it, but it's still got the stock T-Mobile (UK) ROM. I'm wondering if the problem might be caused by rooting, but have downloaded the 2 stock ROMs on the relevant thread on here, but neither will install.
Have you had any joy with your issue?
I'll email you as well.
Cheers,
Rich
Hi,
First off, apologies if this doesn't belong here, getting confused as to where things should go, can someone move it if it's in the wrong place please.
I have Flashed the LeeDrOiD v2.2d ROM and when accessing the Stock browser it will randomly crash, it's a strange crash because normally a crash will mean that you will exit from the browser and next time it will load to the homepage, on mine though it will sort of crash but then load the page I was on, even if it wasn't my homepage, if I had any tabs open I would also lose all of those, which is how I know it's crashing.
This isn't specific to this version of the ROM though as I've had this since v1.4 or to any ROM because I've Flashed 3 different other ROM's (2 Sense and 1 Stock) and this still happens. I've asked before in the XDA LeeDrOiD thread and they said it could be related to backing up and restoring data whilst moving from Android 2.1 to 2.2.
What I have done this time though is not backup anything, no SMS, no system settings, nothing! I deleted everything off my SD Card, cleared the cache, then cleared the Dalvik cache, did a factory reset, Flashed the ROM and then Flashed the radio but still this problem exists, I haven't backed up anything this time, even created a new Google account so it didn't sync my contacts.
There's no particular website that does it, I've got the Flash setting to "On Demand", so that's not crashing it.
This is really starting to annoy me now but I can't figure out for the life of me why it happens, I've tried replicating it to narrow down the cause but I can make it happen one time doing it a certain way but then doing it that way again it'll be fine.
Has anyone got any ideas of how I can overcome this problem or how to Flash the ROM so that my browser will work correctly, this browser problem is the only problem I have with the ROM, apart from that it is superb.
To Flash the ROM I would do the following:
I go into the Recovery mode, wipe the Dalvik cache, then wipe the cache, do a Factory Reset and then Flash the Radio and then the ROM.
Isn't that supposed to completely wipe the phone and then anything Flashed from there is brand new, which is confusing if it is happening in different ROM's.
Also, the browser can crash whether I'm connected to a data plan/Wi-Fi or not!
Any help very much appreciated!
HTC Desire btw.
Anyone?
Someone must have an idea.
It has happend to me few times also, altho it seems preaty random but for me the latest version of lee it seems kinda laggy on stock hrowser, i even flashed the text reflow fix, i started to hate it on some forums since it was scrooling me back to the top of the page... welak with u'r problem and mine, no idea, but well u aint alone
littlej said:
It has happend to me few times also, altho it seems preaty random but for me the latest version of lee it seems kinda laggy on stock hrowser, i even flashed the text reflow fix, i started to hate it on some forums since it was scrooling me back to the top of the page... welak with u'r problem and mine, no idea, but well u aint alone
Click to expand...
Click to collapse
In a strange way that's good to know mate, at least it's not just me.
Hopefully there's a fix to this problem, finding the cause is hard enough though!
Well, I've managed to narrow it down as much as possible, seems to happen more when downloading from the Market or the Internet connection switches from 2g, H or to WiFi.
I personally think it has something to do with the cache, once it starts happening it happens alot, a restart later and it probably won't happen for most of the day, it's like something leaks and builds up and then crashes the browser with a restart resetting everything.
Anyone got any ideas?
Hey guys, its my first post on here and I was hoping to get some help with my device. (Yes, I've searched extensively over the internets. No, I can't find anything related to this issue for the One X)
So let me start from scratch. About a month or so ago, my phone started rebooting randomly, I have been using ViperX 2.7.1 by Team Venom since day one of getting my phone and only started experiencing these issues after upgrading my hboot to 1.31, switching to MaXimus and returning back to ViperX. If it was the occasional reboot, I wouldn't be half as annoyed as I am this very moment. Unfortunately, my phone does not ring when I get a call. Does not ring, screen doesn't even turn on, does not notify, nothing. I called it from another number, did not ring, tried turning the screen on, did not turn on, just rebooted. This does not happen all the time, but has been happening a lot recently. So far, I have fresh installed ViperX numerous times, (wiped cache, factory reset, wiped dalvik cache and full wiped from the ViperX aroma installer) thought maybe an app was misbehaving so fresh installed from the play store instead of Titanium Backup. Even tried switching ROMS but I can't for some reason. Tried installing CM10 the other day, didn't go past the white screen. The good people on androidforums.com told me that I need a different boot.img for newer hboots so I got that, but the CM ring at startup freezes followed by a reboot. Switched to ViperX 3.2 (JB) couple days back hoping this issue wouldn't follow me here as well, but alas, it still has. Then yesterday, I thought upgrading my hboot and wiping my phone the way up'ing the firmware does might fix it, so I up'ed my hboot to 1.39. (strangely though, I still have my files on my sdcard) I followed this guide: http://forum.xda-developers.com/showthread.php?t=1920060 Only step I couldn't follow was the adb reboot oem-78, I got some strange error (did not happen when I up'ed to 1.31) After getting 1.39, I flashed ViperX 3.2 again but I still have this error.
I'm completely out of ideas and am really close to giving up and selling my phone. Any help/advice on what I could do would be greatly appreciated!
Original post: http://androidforums.com/international-tegra-3-one-x-all-things-root/667919-random-reboots.html
Disable AOSP lockscreen in tweaks.
stifler05 said:
Disable AOSP lockscreen in tweaks.
Click to expand...
Click to collapse
Woah, no way. Is that it? It worked perfectly fine before I up'ed my hboot to 1.31 (always used the AOSP lockscreen). Have you encountered a similar issue? I'm trying this out now, will keep you posted.
Hello all,
Recently I installed the Avatar rom from this page (http://forum.xda-developers.com/showthread.php?t=2130852) on to my galaxy s2. I did a full backup in twrp before wiping my caches and installing the rom. Upon installing I run into unrelenting com.android.phone crashes. I go to restore my backup and when I boot to that, my dialpad is missing and I get no service. Can anyone please help me with this? Thanks!
Edit: I have now tried flashing it to stock and I still run into this issue.
Have you tried flashing a new radio?
Sent from my SAMSUNG-SGH-T989
Fix
Okay I managed to fix this issue. Just to clarify what the issue was for anyone with similar problems:
After flashing a new rom I continuously get com.android.phone errors, no service, and no dialpad. Using my twrp full recoveries (2 of them) didn't fix the issue as I still got the crash and missing dialpad and no service.
To fix this, I flashed to stock using the Jellybean file from a thread. (Can't submit links but a google search of "[HOW TO] Odin any stock rom" provides the thread as the first result).
That alone didn't fix it, the last step is what fixed the problem for me, which was a factory reset and cache wipe after the flash.
I have fixed the issue but I am still left with the question of how this was possible. Isn't the dialpad simply an apk that should be in the backup?
Why would flashing a new rom leave me with this error?
Any help in clearing up the cause of the issue here would be much appreciated.
edk128 said:
Okay I managed to fix this issue. Just to clarify what the issue was for anyone with similar problems:
After flashing a new rom I continuously get com.android.phone errors, no service, and no dialpad. Using my twrp full recoveries (2 of them) didn't fix the issue as I still got the crash and missing dialpad and no service.
To fix this, I flashed to stock using the Jellybean file from a thread. (Can't submit links but a google search of "[HOW TO] Odin any stock rom" provides the thread as the first result).
That alone didn't fix it, the last step is what fixed the problem for me, which was a factory reset and cache wipe after the flash.
I have fixed the issue but I am still left with the question of how this was possible. Isn't the dialpad simply an apk that should be in the backup?
Why would flashing a new rom leave me with this error?
Any help in clearing up the cause of the issue here would be much appreciated.
Click to expand...
Click to collapse
I still think it was the radio, If you didn't get any signal then the first thing I would do is reflash the radio. The same thing happened to me on CM 10.1..I don't remember if the dialer was crashing on me but it probably was BUT I do know I was getting horrible battery life and I had no signal. I just flashed the latest radio and I was good It could be that the radio you had when you were flashing Avatar didn't support it.
edk128 said:
Okay I managed to fix this issue. Just to clarify what the issue was for anyone with similar problems:
After flashing a new rom I continuously get com.android.phone errors, no service, and no dialpad. Using my twrp full recoveries (2 of them) didn't fix the issue as I still got the crash and missing dialpad and no service.
To fix this, I flashed to stock using the Jellybean file from a thread. (Can't submit links but a google search of "[HOW TO] Odin any stock rom" provides the thread as the first result).
That alone didn't fix it, the last step is what fixed the problem for me, which was a factory reset and cache wipe after the flash.
I have fixed the issue but I am still left with the question of how this was possible. Isn't the dialpad simply an apk that should be in the backup?
Why would flashing a new rom leave me with this error?
Any help in clearing up the cause of the issue here would be much appreciated.
Click to expand...
Click to collapse
Sometimes what happens when flashing a rom or even restoring a backup sometimes with newer roms that support the preload partition is the recovery doesn't properly load the preload partition, causing some apps or system software to malfunction, what recovery are u using?
Sent from my SGH-T989 using xda premium
I use twrp. I think 2.5. Is there any way to prevent this problem? I want to try reflashing the avatar ROM but it's a pain to have to flash back to stock and then root and then restore my backup
I have read around regarding this problem without luck, and hope that someone can advise if I have missed anything.
I used to use this phone and as I liked to tweak it was running a custom rom (think it was Wanams). Anyway I got an upgrade ages ago, and my wife carried on using the phone for a while. As she just needs a standard rom I recently decided to factory reset and use Odin to flash the newest stock rom (N7100XXUFNE1 - UK). This is when the problems started. Initially the Wifi wouldn't come on, but after factory resetting and using the Samsung Updater in Kies I finally managed to get Wifi back. Then, while setting it up and installing apps from the Play store it started freezing and had to be rebooted every 5 or 10 mins. Finally after doing this a couple of times, all the apps were installed and after leaving it to "settle" it seemed to be better. Now however, 2 or 3 times a day, when playing games or using other apps, it will just reboot.
What I have tried is:
* I have tried clearing cache through the stock recovery
* Tried a number of Factory Resets
* After reading about the SDS problem I have tried running the "dummy file generator" to fill the internal memory and this completes ok. I guess this means that although I have memory that is/was susceptible I applied the original SDS fix early enough with the custom rom that all the memory is still ok?
As I have the newest bootloader I can't downgrade that, but as I don't care about triggering Knox I was thinking of rooting and installing a custom rom to see if any of the other Kernels help?
Has anyone got any idea's what could be causing this and what I can do to fix it?
Thanks.