Develop Bugs

Strange Browser Crashing

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?

[Q] Generic network failure... HELP!

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.

All calls go to voicemail - Help

Hey Everyone,
I am running the SGH-T989 with the latest Darkside (2.3) ROM and kernel. Though new to the forums I have been "trolling" here for years and rooting and moding every phone I have had since ... well I can't remember when.
Never had any serious troubles, but suddenly, about 2 days ago I stopped getting incoming calls. It acts as though the phone is off and all calls go straight to voice mail, this happens when I have full signal, and I can still make outgoing calls. I have done full wipes, charged fully, tried it plugged in, not plugged in, on WIFI calling, on cellular networks, different ROMs, and nothing seems to work.
Anyone have any suggestions?

check under settings --call--- call rejection---auto reject numbers---should be off or the ones you want rejected...may got switched to all calls

Thanks for the response Bobby. Unfortunately I checked that after posting and it is set to off.
However I retired again and I am receiving calls now over Wifi calling, just not over cellular networks.
This is herring frustrating and of course the missus blames me for routing and ROMing

Ok,actuakly I tried to type retried but you gotta love auto-correct.
Sent from my SGH-T989 using XDA App

What about call forwarding?

Just checked and Call forwarding is set to:
Always forward: Disabled
Forward when busy / unanswered / unreachable is all set to voicemail.
Could that be the culprit even if I show full signal and am able to make out going calls? Should I disable any of those?

A few weeks back I had flashed a new rom and did a full app restore from Titanium backup. I had the same thing happen with call going directly to VM. I did a full wipe and re-flashed and then restored only missing apps and the problem went away. I assume it may have been a conflict with the restore. Might be worth a try. Good luck.

myndsey said:
A few weeks back I had flashed a new rom and did a full app restore from Titanium backup. I had the same thing happen with call going directly to VM. I did a full wipe and re-flashed and then restored only missing apps and the problem went away. I assume it may have been a conflict with the restore. Might be worth a try. Good luck.
Click to expand...
Click to collapse
Yes if you restore system data that causes issues unless it's backed up and restored on the exact same rom.
Sent via Brain Drain

I am having the same exact problem on Jugs 5.0... very interesting. I did not do a Ti restore, but rather just upgraded from one iteration of Jugs (3.7) to the latest.

But what happens when you don't restore any apps / data? I tried a fresh ROM install and prior to installing any apps I was unable to get any incoming calls (except when on WIFI calling).
Thanks for the help everyone. I guess its time to break down and contact Tmo and see what's up.

You beat me by seconds Poser. I tried Jugs 5.0 too and the problem still didn't go away.

Mystic_ said:
But what happens when you don't restore any apps / data? I tried a fresh ROM install and prior to installing any apps I was unable to get any incoming calls (except when on WIFI calling).
Thanks for the help everyone. I guess its time to break down and contact Tmo and see what's up.
Click to expand...
Click to collapse
By fresh install did you go into recovery and:
1. wipe data/factory reset
2. wipe cache
3. wipe davlik
4. mnt /system and wipe
5. flash ROM
I only ask, because I am wondering if "ghosting" is leading to mine and your problem?

Well, with the Darkside ROM has its own script to do a wipe ..... But, I'm a little OCD so, especially after having the problem I went through and wipe / re-wiped / wiped dalvik / re-wiped and factor reset.
Then after the flash (no matter what ROM that I have tried since having this problem) I fix permissions and then leave it for some time after boot to let it "settle in".
Hopefully the "ghosting" is your problem and the full wipes will help.

Mystic_ said:
Well, with the Darkside ROM has its own script to do a wipe ..... But, I'm a little OCD so, especially after having the problem I went through and wipe / re-wiped / wiped dalvik / re-wiped and factor reset.
Then after the flash (no matter what ROM that I have tried since having this problem) I fix permissions and then leave it for some time after boot to let it "settle in".
Hopefully the "ghosting" is your problem and the full wipes will help.
Click to expand...
Click to collapse
No dice, same problem. Wonder if it is an /efs problem?

Don't know but it is odd. I can still make outgoing calls, get data and everything else.

I have the same exact symptoms...exactly. It also just began a couple of days ago. Have you restored to bone stock via ODIN (I can't, my usb port is shot)?

Get a new sim card. If factory reset doesn't do it and you think its not network related and you don't think you accidentally blacklisted all your friends its probably the sim card.
Sent from my HTC Vision using xda premium

Android_Monsters hit the nail on the head. I took it to a T-Mobile store, they replaced the sim and all is golden (except that my wife can now call me again )
And in case you are worried, my phone was still rooted / ROMed and the Tmobile rep working the store was simply stunned to see the custom boot screen. They didn't care in the slightest that the phone was rooted and ROMed. In fact he was upset because he couldn't do that because of company regulations.

Same here.... new Sim did the trick
Huh?

This happened to me b4 I called t-mobile and they fixed it without going anywhere.
Sent from my SGH-T989 using xda premium

Sound profile set to 'normal' again after (re)start

Hi all,
every time when I start or restart (normal or hot) my DHD the sound profile will be set to 'normal' independent from the selected sound profile before. I select the 'just vibrate' sound profile, shut down and restart or just restart my DHD again. At the beginning the previous selected sound profile is active but suddenly it changes to 'normal' again.
The day before yesterday I have flashed LeeDroid 5.1.1. Thus I assume the issue has to do with LeeDroid (not sure if this is really the case). I was not able to find anything in the settings and don't have an app installed which could do that. Furthermore I was not able to find anything regarding this topic via Google or forum searches.
Maybe some of you have or had the same issue and know how to fix it?
Many thanks in advance.

lelli1906 said:
Hi all,
every time when I start or restart (normal or hot) my DHD the sound profile will be set to 'normal' independent from the selected sound profile before. I select the 'just vibrate' sound profile, shut down and restart or just restart my DHD again. At the beginning the previous selected sound profile is active but suddenly it changes to 'normal' again.
The day before yesterday I have flashed LeeDroid 5.1.1. Thus I assume the issue has to do with LeeDroid (not sure if this is really the case). I was not able to find anything in the settings and don't have an app installed which could do that. Furthermore I was not able to find anything regarding this topic via Google or forum searches.
Maybe some of you have or had the same issue and know how to fix it?
Many thanks in advance.
Click to expand...
Click to collapse
Did you clear cache and dalvik cache before flashing? and did you fully wipe data?
It shouldn't be happening because the rom i'm on (sense 3.5), it doesn't give that sort of issue and i don't think leedroid should give you any issue like that since it is one of those old roms which are bug free...try what i told you to do and if it still gives you problem then your best bet is to flash a new rom...

Thanks for your reply.
I have flashed LeeDroid 5.1.0 via Rom Manager and selected the options for clearing cache and dalvik cache. After that I flashed the 5.1.1 patch to solve the 'no signal' issue (without wiping again). Which data do I have to wipe fully? I have also tried to use the wipe/factory reset functionality in the recovery mode but without flashing the ROM again (I have restored the created backup of LeeDroid - maybe that's what I shouldn't do?).
I'll give it another try with full data wipe before.

Random reboots // Not receiving calls

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.