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?
Related
I have never had this issue with any roms before.
I had been running Fresh Rom 3.1.0.2 or whatever, and recently upgraded to Fresh Rom 3.2
I made sure to wipe everything before installing this rom and now i have weird data issues no matter what rom i use
data works randomly no matter what signal strength i have with the market, signing into google, etc. ( i get network error messages loading market things saying i need to retry even though my browser works )
I have cleared everything many times trying different roms and updating my PRL and Profile also.
Most of the time my data arrows only show uploading too.
I am thinking about going and RUU to 2.1 or whatever and re rooting but which do i use? the PC36IMG.zip or RUU something? a little confused here.
i just wanna go back to stock everything to wipe everything and start fresh to make sure everything is fine.
Thanks!!
I've been having the same issue. A hard reset has fixed the problem, for today at least.
Sent from my PC36100 using XDA App
anon20 said:
I've been having the same issue. A hard reset has fixed the problem, for today at least.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
as far as hard reset, what are you referring to? powering off and pulling the battery? or what?
thanks!
I have been having the same issues. I just used the newest rooting method for 2.2 the other day. My web browsing and email pushes are fine but anything related to google (market, maps, signing in) fail out. I just tried wiping cache and it seems to work for now. It is extremely annoying.
Let me start by saying, I have searched all of the treads for my phone, and the ones suggested before posting a new one, with no luck. I also searched all over other sites for an answer, about 3 hours now, and still nothing that quite fits my problem..
I have a Verizon HTC Inc2
-running 2.3.4
-Virtuous Unity v2.39.0
The problem I keep running into is that whenever I flash a new rom, or do a factory reset with clockworkmod, I can never get my phone to send or recieve MMS. It always says, generic network failure. I have tried with the HTC messages app and handsent app, both failed. The data icon in the notification area usually does not even show activity. I tried wiping the cache several times, restarts, changing data and wifi settings but to no avail. Funny thing is, I can restore my phone to the first backup I made, Gingerbread 2.3.3, and then MMS works.
Any ideas as to what may be happening? I can give you any additional info you need or ask as well. I'm not a total noob, but I feel like one right now. I just can't figure this one out on my own. Thanks!
my3kgt said:
Let me start by saying, I have searched all of the treads for my phone, and the ones suggested before posting a new one, with no luck. I also searched all over other sites for an answer, about 3 hours now, and still nothing that quite fits my problem..
I have a Verizon HTC Inc2
-running 2.3.4
-Virtuous Unity v2.39.0
The problem I keep running into is that whenever I flash a new rom, or do a factory reset with clockworkmod, I can never get my phone to send or recieve MMS. It always says, generic network failure. I have tried with the HTC messages app and handsent app, both failed. The data icon in the notification area usually does not even show activity. I tried wiping the cache several times, restarts, changing data and wifi settings but to no avail. Funny thing is, I can restore my phone to the first backup I made, Gingerbread 2.3.3, and then MMS works.
Any ideas as to what may be happening? I can give you any additional info you need or ask as well. I'm not a total noob, but I feel like one right now. I just can't figure this one out on my own. Thanks!
Click to expand...
Click to collapse
General Network Error is when the system returns an error stating that you have no connectivity to send a message or an MMS (at least from my experience w/ it). I have this issue a lot with any messaging on my end because of shoddy reception. Which other ROMs besides Virtuous are you flashing that are giving this error? I know for a fact the CM7 has been having a LOT of issues with data connectivity. The last ones I remember hearing about with working data is #79 (or was it #80, I can't remember) and #85 and for a few people, #92.
I do have plenty of reception, always around 2 to 3 bars. Sorry I worded that wrong in my post, Virtuous is the only and first rom I flashed. I did it because Verizon OTA updates kept freezing my phone and I would get the blue android with the !. What I meant was, even when I did a factory reset, my MMS wouldnt work. First time I got that error, I was able to use bootloader and make a backup of eberything, then did a factory reset/wipe data and thats when I first noticed MMS was not working. So I copied the backup to my laptop, did another factory reset and format SD card, then I copied the backup to my card again, and did a restore with that backup. I restored data, cache, system, and boot I believe, and everything was back to normal and MMS was working. Unfortunetly I kept getting the OTA updates and each time, same problem, so this morning I read on a forum that a custom rom would prevent OTA updates, so I flashed Virtuous. I just found it odd that a normal factory reset, with no custom rom, would prevent MMS.
One more thing, not sure if its related, but I keep recieving messages from #6250 that say "VZWNMN: 1." Google searched that, most responses in forums are people saying they get the same thing and that Verizon told them they know nothing about it..
Have you tried a different radio?
Sent from my Incredible 2 using xda premium
my3kgt said:
I do have plenty of reception, always around 2 to 3 bars. Sorry I worded that wrong in my post, Virtuous is the only and first rom I flashed. I did it because Verizon OTA updates kept freezing my phone and I would get the blue android with the !. What I meant was, even when I did a factory reset, my MMS wouldnt work. First time I got that error, I was able to use bootloader and make a backup of eberything, then did a factory reset/wipe data and thats when I first noticed MMS was not working. So I copied the backup to my laptop, did another factory reset and format SD card, then I copied the backup to my card again, and did a restore with that backup. I restored data, cache, system, and boot I believe, and everything was back to normal and MMS was working. Unfortunetly I kept getting the OTA updates and each time, same problem, so this morning I read on a forum that a custom rom would prevent OTA updates, so I flashed Virtuous. I just found it odd that a normal factory reset, with no custom rom, would prevent MMS.
One more thing, not sure if its related, but I keep recieving messages from #6250 that say "VZWNMN: 1." Google searched that, most responses in forums are people saying they get the same thing and that Verizon told them they know nothing about it..
Click to expand...
Click to collapse
People on CM were complaining of the same exact issue. They'd get bars of reception but MMS was just broken. I was just stating that when I try to send a message thru verizon and not google voice, I often get the same error message you're getting, which means that the data is being prevented from going out. I probably should've clarified that a little better lol. When you installed Virtuous, did you do a wipe data/cache and a wipe dalvik cache?
Also, if you restore back to your Gingerbread 2.3.3 that's rooted and your MMS is working fine there, then I don't believe it could be your radio. A possibility would be the kernel, but I doubt that Virtuous would package a kernel that would crash the MMS function. And since it's any SMS/MMS app, that knocks out the possibility of it being application based. The only thing I can suggest, would be to test out another ROM. If you're looking for sense based roms, go for BAMF's (http://www.teambamf.net) or Newt's Incredible 2 HD (http://www.themikmik.com). If you're looking for an AOSP based rom, go for CM7 (found on ROM Manager or at http://www.cyanogenmod.com) or MIUI (ROM Manager again, or http://www.miuiandroid.com). If you want a hybrid, I would suggest Skyraider Zeus (http://www.teambamf.net) or Gingersense (it can be found in the development portion of XDA). Remember when you flash a rom for the very first time, I'm sure you know this already, but you need to backup your rom first and then wipe data/cache and wipe your dalvik cache. Not doing either wipe before installing a brand new rom for the first time can cause unforseen errors.
Ok I found the answer while actually looking for new radios, so thanks for the post! haha
For all you out there who might run into the same problem, this is the solution I found..
Instructions to fix MMS (by xelsewherex)
1.Go to the market and download apn backup and restore (Market Link APN B&R).
2.Create a folder on your sdcard named APNBackupRestore if it doesn't exist already.
3.Copy this file, ht tp://db.tt/9Ao5ErR, to APNBackupRestore folder (If you aren't doing this on desktop, hit menu now in xda and choose browser. File is an xml and your phone will not know what to do with it. Long press the link and use 'save link'). This is an XML doc, sorry but since I'm new I can't just post a link, just remove the spaces between ht and tp.
4.Run APN Backup Restore and press Delete Apns and then Restore from the downloaded file.
5.You should be good to go from there. MMS should now work and the softkey lights do as well.
I have been having a problem every time I change roms where after it boots up, i get maybe 5 minutes to play around and then the home screen crashes. It reloads, finds a signal, media scanner running etc, just like i just turned the phone on. Before I can do anything, it crashes again and repeats forever. Its not boot looping though. But it makes the phone useless.
This happened last time i tried the 12 lockscreens mod (im on calkulins 2.8.1), so i had to wipe and reflash calks rom since my backup was bad. Then i made another backup to be safe, which is working. Today i tried flashing blu kuban by rujelus22. Same thing happened. Which makes me thing there is a deep seated issue somewhere in the phone.
Every time i flash a new rom, i wipe cache and dalvik, and format system. I also tried a factory reset. Nothing solves my problem and I cant find anything similar anywhere.
I really hope one of you has a brilliant idea for me because I really love this phone, but If im stuck with one rom forever I would be a very sad panda
BTW i have to thank all the devs for all the sweet roms and hacks, you guys rock
Download calkulins wipe all.zip
Run that then try to flash your rom
Also in CWM run the fix permissions option....that usually fixes alot of issues
Sent from the near past
I've recently been trying out ICS ROMs for the Evo, but decided to return to Gingerbread because ICS seems to mess up GPS accuracy, no matter which ROM I try. I'm now on my third different Gingerbread ROM today because I've run into a problem I've never seen before. When I first install I'm able to turn on WiFi and connect to my router no problem, but sometime later, the phone refuses to connect. In wireless settings you can turn on WiFi, and it will think about it for awhile, and then just stop trying. Sometimes I get a com.android.settings not responding message, but not always. Anyway, I tried searching for this but couldn't really even figure out how to word it. This sound familiar to anyone? Thanks.
Re-Install your Rom, first.
Update your Radios.
Simple.
alexdz said:
I've recently been trying out ICS ROMs for the Evo, but decided to return to Gingerbread because ICS seems to mess up GPS accuracy, no matter which ROM I try. I'm now on my third different Gingerbread ROM today because I've run into a problem I've never seen before. When I first install I'm able to turn on WiFi and connect to my router no problem, but sometime later, the phone refuses to connect. In wireless settings you can turn on WiFi, and it will think about it for awhile, and then just stop trying. Sometimes I get a com.android.settings not responding message, but not always. Anyway, I tried searching for this but couldn't really even figure out how to word it. This sound familiar to anyone? Thanks.
Click to expand...
Click to collapse
Try what Nickitt said first, and if that doesn't work, try this out --
Go into recovery, clear boot, dalvik, and do a factory reset. Then, install a ROM of your choice.
For some odd reason, I started having similar WiFi issues on my EVO after installing the Mason kernel, where the WiFi would indicate that it's on for a few seconds, and then move back to the off position (or, it would stay permanently in the state where it seems like it's turning on). Reflashing the ROM by itself didn't work, but clearing boot somehow did the trick.
Go figure.
vdude8 said:
Try what Nickitt said first, and if that doesn't work, try this out --
Go into recovery, clear boot, dalvik, and do a factory reset. Then, install a ROM of your choice.
For some odd reason, I started having similar WiFi issues on my EVO after installing the Mason kernel, where the WiFi would indicate that it's on for a few seconds, and then move back to the off position (or, it would stay permanently in the state where it seems like it's turning on). Reflashing the ROM by itself didn't work, but clearing boot somehow did the trick.
Go figure.
Click to expand...
Click to collapse
I failed to mention initially, but I did try updating the radios as well. Regardless, I'm not having the problem anymore, and it's possible that there was simply something in my Titanium backups (done while on ICS) that it didn't like. I started thinking back on the timing and realized that the issue was showing up only after I went through the batch restore process, so this time I only restored a few apps that had data I didn't want to lose, and nothing else. So far so good.
Except of course that I'm now having a new problem that may be associated with a2sd, but I'll post that in that Deck's Reloaded thread...
Thanks!
I had a lot of force closes after restoring ICS backups in GB. Don't think the backups are backwards compatable...not all the time anyway.
Every time I try to open the notification log widget/shortcut on my home screen, it crashes settings. I have not gotten this to work since discovering it's existence a few months ago and cannot find a fix. Can anyone help?
Very odd. if youre not afraid of factory resets, i say back it up and wipe that thing clean!
If it still persist, try and flash a factory image, if not the latest one then on that you recall that worked.
If rooted, be cautious of trying to restore app/app data with titanium, this causes all sorts of weird problems most of the time, and has been the source of many problems in the forums.