Database Users

Change to froyo

Forgive me if I have posted this in the wrong place but this is all very new to me. I recently flashed my phone to 2.2 and some strange things have been happening. I have two examples I would like to share which both have the same outcome. Trying to import a book into aldiko from the sd card ends in the program being force closed. The phone vibrates once, pauses a few seconds, vibrates three times and then the error message comes up. The second example is pretty much the exact same except it happens when trying to launch a game with psx4droid. One vibration, pause, three vibrations, program closes. Both of these programs worked without issue prior to the change in OS. Could anyone suggest any reasons and solutions to the situation? I was on the last chapter of an amazing book. Thanks in advance,
Gino.
Sent from my GT-I9000 using XDA App

yep doing it to me too, not very often, it was happening a lot at first, but i did a factory reset and it cleared up a lot of them.

I dis one factory reset with no result.should I just keep trying til it goes away?
Sent from my GT-I9000 using XDA App

This has been happening to myself and my partner's Samsung Galaxy S since we upgraded to the official UK Froyo update. Just about any app can crash with the vibrate, pause, 3 vibrates. While mine is rooted with z4root and I have a ton of stuff on it, my partner's is not rooted and only runs some very basic apps.

Did you update through Kies? What version of FroYo are you on?
Try to uninstall the apps, download them and reinstall. Also, using the Kies Registry Patcher, see if Kies will flash the stock 2.2 ROM. All stock ROMs can be found here.
Follow these steps
Ian

Updated with Kies to Froyo (JPO) a month or two ago. I notice JPY is now available through Kies so currently trying that.
I had tried installing/uninstalling apps previously, but according to logcat just about any process can crash with this vibrate pulse, pause, three pulses issue. I've had System, acore, TWL, Market, Gmail, the browser (stock and Dolphin HD), etc. These aren't the normal force closes either. The logs show them as SIGBUS or SIGILL (no K, not SIGKILL) errors, which normally mean a hardware fault, but, given so many people are having the problem after updating to FroYo, and given it's happening on two phones I'm in possession of personally, I'm sure it's related to the FroYo update.

Well, since updating to JPY 6 hours ago I've had zero crashes and the phone seems far more responsive and faster. My quadrant score has increased by around 20%.
There were a number of things that would nearly always crash the phone in the way I described previously - such as updating more than 2 or 3 apps at the same time, rapidly scrolling around certain websites, etc. I updated 10 apps simultaneously, I've gone to all of the websites that would crash the browser, and tried a whole load of other things that were "high risk" on JPO. Zero crashes.
If the phone does crash in the next week or two I will come back and mention it here. But so far, it looks great.

We took a Froyo update and the phone is now no longer able to accept incoming calls or texts when ANY other web-using application is running, e.g. you open the Facebook app and leave it running in the background so you can get notifications from FB and you can't receive any calls or texts until you have shut down FB. You open a browser, you can't receive any calls or texts until you shut down the browser!
Not even sure how to report this as a problem because all the websites we are directed to seem to be FAQs for people who have never seen a phone before. Any recommendations so we can return to the use of phone calls? For the next week or so we have only pay as you surf mobile broadband and no Kies, which resticts things somewhat, but is there anything we can do right away? What about when we get back to a full net connection and Kies? Where do we even report this error, as everyone seems to be having a different type of error with this update, and we'd like to make sure they know about this one, a smartphone that doesn't receive phone calls unless you turn everything else off is a little pointless!
Incidentally, site designers, any chance you could put some text descriptions for your button images? I loaded this site with no pictures and it doesn't come up saying where the reply buttons and such are located like it does when you have alternative text. If people use screenreaders (e.g. blind people like many of my friends) they cannot navigate this site without these. Cheers!

I've tested this and it works fine for me.
Are you sure this isn't just the limitation that's present on ALL GSM networks whereby if you're on 2G (i.e. not WiFi or 3G) then you can only have either a data connection OR a voice call? 2G only supports one type of connection at a time. If you're using data and want to make/receive calls you must use either 3G or WiFi.

The phone is definitely showing 3G as the connection type, and we have two phones on the same network in the same room and only the Froyo one has this problem, which it has never had before. Even in areas where the connection type is showing as HSDPA (never get those letters in the correct order!) it is impossible to get any kind of incoming call when a web application is open. It also applies to applications which are open but not currently using data. Not sure if they use data in a background kind of a way, but if you open a browser and load e.g. Google and after it is fully loaded attempt to call that phone you still get the answerphone. You can only get a phone call if all apps which might potentially use a web connection are shut down. Renders every aspect of the phone useless because you have to shut off Facebook, all browsers, email, weather updates, news feeds... basically everything, just in case you might potentially receive a telephone call.
We had 2 T-mobile phones on Windows Mobile in this same room and neither of those has this problem either. The phones are 2x HTC TYTNII (Tmobile MDA Vario 3) and 1x HTC Wildfire with Android 2.1 which all work and one Samsung Galaxy S on Android 2.2 which worked (in terms of being able to get calls with web apps loaded) up until 2.2 was loaded.

Well, that's very strange. All I can say is that my SGS and my partner's SGS, both were running 2.2 for a couple of months, and now both running 2.2.1 have been fine. I tested both again just now and I can make/receive calls fine on both even while actively using the browser.

Updated post: Can't get my phone to work at all

I've got two main problems with my galaxy s.
1) Today at around 1pm I had to force close something (I don't even remember what it was. I had just woken up the phone and went to check my mail, so I assume Launcher pro or something). It kept prompting me to force close, so I just took out the battery and reboot it. The phone can no longer get passed the initial screen (before the S). I've tried to reset to factory defaults, and it still doesn't work. I assume I can re-flash (not home yet) - but I'm wondering what would cause this type of behavior. FYI - I've been running 2.2 JPH with Rombie's mod)
2) I get really bad reception. I constantly will have my phone go from no service to 3-4 bars while sitting in the same spot. I also have a problem in busy areas where I'll lose my connection completely (whereas other people with different phones seem to have no problem right beside me). Is there anything that could be causing these issues?
Side note: When I originally upgraded to 2.2 JPH I had efs issues for a while, and it took me a while to get it up and running. It's working now (phone and data) - I'm just worried there's some residual effects of a mildly corrupted efs or something.

Update...
Things have gotten worse and I really need some suggestions.
I've tried flashing about 5 different firmwares and I can't get the thing going.
The closest I've come is with the stock jh2 firmware. It boots and it goes to a black screen after the S logo. I know this has been brought up but I have not had success with solutions I've found in other threads. I've tried it with pit512 513 and 803. I've tried it with repartition checked and unchecked.
When I try a 2.2 rom (such as the latest jpk) and upon resetting in the recovery mode, I receive an SDCARD failed to mount error (although one time I also received a failed to load DBDATA error). It also won't let me format the sdcard in this screen as obviously it can't mount it.
The closest I've come to getting the sdcard working is on the jh2 firmware i can "load update.zip" from my firmware, and it seems to actually load - unfortunately that update.zip is completely useless (as it's just an unlocker update i believe) - and I can't change the update.zip as I can't access the sdcard.
Please help if you can!

I had the same problem. My phone was working fine and then it just turned off and froze. I resetted it a few times and it would go to the S logo and then the screen would go blank and the buttons would light up. Resetting it a few more times made it work once but then when i started it again the phone would go back to the same problem.
I tried a ton of rom on it and some worked (but my internal sd card wouldn't mount). The problem got progressively worse by it's self and my phone wouldn't even start now. I recently send it back to Bell to get it repaired and hopefully they don't ping me saying it was my fault for ****ing around, which I doubt they will find out at this point since the damn thing doesn't even turn on.
I researched this a fair bit (2 full nights) and found out that it had something to do with me flashing Jp3 and that set my internal sd card as read only somehow. It's a bug and if you google it a lot of people have had this problem but none had a working solution and everyone of them had to send it back for repair.
Edit: I am also Canadian with a bell phone.

If I end up sending it back to bell, will flashing back to something like JH2 help cover my tracks?
Any idea how long it takes? I can't really go without a phone for more than a couple days =/

fuffalo said:
If I end up sending it back to bell, will flashing back to something like JH2 help cover my tracks?
Any idea how long it takes? I can't really go without a phone for more than a couple days =/
Click to expand...
Click to collapse
Honestly, it is a very frustrating process. They quote you a 2 - 6 week window and do not give you any hard time table and to top that off they don't have any loaner phones that are smart phones. The loaners cost $25 and $250 down.
I had to go out and find one from a friend and even then they wouldn't let me use a CDMA phone since i had a HSPA+ data plan and it some how ****s with their system. The only way you can use a phone on their network is using a HSPA+ phone if you need data. Luckily a friend had a HTC magic that was unlocked so I am using that now.
You can try to load up the default rom that ships with it and then send it in for repair.

Is the default rom JH2?

I believe it is this one I9000UGJH2

Alright so I can adb in to my phone when it's in recovery mode.
Does this help at all? Can i try anything from here?

***EPIC - NEED HELP TXT MESSAGING, BLUETOOTH, QIK for EB13 *PLEASE!

OK I need help and serious input since these are the things I use the most. I will give you a little history also. On 0:00 Tuesday 02/22/2011 I downloaded samsung update for EB13. I flashed the phone, and everything went well even the one-click-root-2.5.5. So with my issues appearing I researched and seen many others had issues not like mine. I called Sprint they had me do a hard reset on my phone. Still the issues are a not real bad but I had having to restart my phone 6 or 7 times a day. I even went to the store and the rep said there were no so called "quote issues with the EPIC cause he has one". I need my phone re-flash. I told him I did that. He said have a hard reset done to it. I did it the day after the I flashed it. I told him I still have issues and no one has been able to help me. He said take the phone back and get a new one then. His name is Mike at the Sprint Store on Oleander Dr Wilmington, NC. Lots of help Mike. Just admit the software is sh*t like the phone reps did on the phone. Re-flashing and a hard reset is something I already did, and removed alot of useless app, from the guide on switch apps to remove. So PLEASE someone come up with some mods or ideas to help me. PLEASE. I got no clue on this.
1. Txt messaging. After an hour of non use when trying to send a txt. The txt hangs. I tried de-activating and a signal refresh. Dont work. Only fix is re-start the phone, and re-send the txt.
2. Bluetooth. After non use for an hr Bluetooth says it is still connected. When calls comes in however it is not connected. I have to manual connect, or if no call, I have to do a signal refresh. Not even turning off bluetooth works. The Sprint rep says it is the only work around they have and know about it.
3. QIK. Ok Qik on 2.1 used do a portrait on the front camera. Now it records only as landscape, but shows as portrait. I spoke to Sprint about this also and they said it some I am going to have to deal with. I drive alot to job to job, so I dont have alot of time to play with settings.

bluetooth problems?
i have flashed the eb13 froyo onto my epic with the eb13 supernova,genocide .3a kernal and everything seems to be almost perfect except i still can not give voice commands over my bluetooth ....it will activate, say speak now and then it will disconnect before i can even give a command...if there is a fix for this please let me know...thanks

Txt messenging found
I found the same issue and a fix for it other than reboot. This was found back in July on another phone and carrier but with Android 2.2 Froyo. So this issue is with the OS its self.
A. Settings menu
B. Applications menu
C. Manage Applications
D. Messaging app
E. Force Close button
07-16-2010, 02:05 PM
LugusLuna
Smoke signaler
LugusLuna has no status.
Join Date: Jul 2010
Posts: 3
Re: Android 2.2 text message problem
Fixed it!!! In case anyone else out there is having the same problem, the way I fixed it was by going to the Settings menu from the home screen, then to the Applications menu, then to Manage Applications, then to the Running tab, then to the Messaging app with the icon that Andriod uses for the text function. Then I clicked on the Force Close button. Now it sends text message with no problem. Go figure.

Back up your data with MyBackup Root, use Odin to restore full, clean EB13, then use the Market or AppBrain to reinstall your apps, and your backup to restore only the data for those specific apps. That will solve almost all problems related to the OTA update, including yours, OP.

k0nane said:
Back up your data with MyBackup Root, use Odin to restore full, clean EB13, then use the Market or AppBrain to reinstall your apps, and your backup to restore only the data for those specific apps. That will solve almost all problems related to the OTA update, including yours, OP.
Click to expand...
Click to collapse
But he used the .exe...
I think he mightve removed something by accident...was the "apps safe to remove" thread updated for EB13?
Sent from my SPH-D700 using XDA App

Thanks everyone for replying with some needed input and issues of your own. I do think I can live with the messaging app since I found a temp fix for it(force close). I also believe I can live with Qik recording in landscape, even though it was not designed that way for the front camera. However I cannot live the issue of Bluetooth. I need as I will never put a touch screen phone to my ear or listen to it on speaker, like some of these dumb a$$ doing this walking around in public. I drive from job to job and it is very difficult for me to play with setting while driving. NC is becoming a handsfree cell phone state like so many others, and there is no txting while driving at all. It is a dangerous thing to do. I have read older posts from other phone that received 2.2 much earlier in the year and I believe that is OS is $hit. However 2.1 does not have Bluetooth activated command dialing.
*So for you people that are catching up, I did install from the exe and seemed to work fine and even after I rooted with a clockworkmod 2.5.1 recovery. I even did a hard reset with Sprint. I did not removed any important applications as mobile hotspot is this there. I have not upgraded to any new kernel, or rom. These issues are minor, but a major inconvenience. Bluetooth will work for awhile, but then with a call comes in after a hr of rebooting I have to connect manually after it has been paired. ""Sprint said that this was a issue known in the OS, but I am wondering if anyone has found a kernel or mod to correct this issue?""

Why not back it up and then go into cwm and clear the cache/DCache and then run the .exe without removing ANYTHING and see if your problems persist?
If they don't, then take out an .apk one at a time until you find the one that breaks your functions...
Sent from my SPH-D700 using XDA App

Nexus 6p Mobile hotspot not working properly (T-mobile)

Have searched extensively and found no working solution to this issue. Return would be a last and unwanted resort. Here's the deal. Mobile Hotspot performs strangely no matter what android version I run. In marshmallow it would turn off during use. In nougat it would just crash and need to be restarted. It most reliably occurs when playing lan minecraft over 2 comps on the hotspot but will still have the issue randomly even when only 1 device is connected. Many calls to various companies have all resulted in "send it back in". This is infuriating as this feels like a software issue not a hardware issue, I just can't see how it can be any other way. I have tried everything I could think of and had no luck, here's the list of what i've tried so far:
Restart phone
Factory reset
update to latest firmware
downgrade back to original marshmallow firmware
there is no access to advanced settings for hotspot so timeout is non-existant
reset network settings
edit: also tried ElementX kernel still have the same problem
tried flash-all to stock Marshmallow firmware without restoring apps or settings
RMA TWICE
etc. (any others I've forgotten that I did I will edit and add if ppl suggest it)
Nothing works, before I downgraded back to MM I did capture a bug report when the crash happened on latest nougat. I have no idea if I caught relevant info but will include the zip here anyway. Any help is massively appreciated.

Flash the correct factory images using google flash-all method (backup data first or remove -w in the script!). Upon startup do NOT restore settings apps etc.. and test.
If it doesn't work post a bug report on google website.

rchtk said:
Flash the correct factory images using google flash-all method (backup data first or remove -w in the script!). Upon startup do NOT restore settings apps etc.. and test.
If it doesn't work post a bug report on google website.
Click to expand...
Click to collapse
if it wasn't clear in my post I was at factory default and the problem occurred and have restored and erased a few times. If the method you're describing is different form having out of the box stock please elaborate, I only flashed a kernel recently as a further last resort.
By not restoring settings are you referring to not allowing google backups to restore? and finally if you can provide a link to where exactly I am to post this bug report I would appreciate it, I have posted in what I thought was official channels with a bug report and was told to call in, which is stupid, considering if I leave a bug report why not read it and get back to me?
Anyways thanks for reply and any further info you give

rchtk said:
Flash the correct factory images using google flash-all method (backup data first or remove -w in the script!). Upon startup do NOT restore settings apps etc.. and test.
If it doesn't work post a bug report on google website.
Click to expand...
Click to collapse
Finally got back from vacation and had time to try your request. used flash-all method and did not restore any apps or settings and hotspot still did not work. any other info or at least a link to where I should post a bug report to google as I have used the report function through the device and have posted on nexus help forums and not received answers. I really don't want to have to do an rma as I hate the thought of receiving a refurb phone when I wanted a brand new one and they sent me a broken one

well all is officially lost as I am in the process of doing an RMA. Multiple phone calls between carrier and manufacturer see each company blaming the other with no solution in sight. Fingers crossed hard enough to bleed that somehow a new phone or any "repairs" done to mine will fix the issue. Come back in a few weeks for an update. :crying:

I would confirm with T-Mobile that your line is provisioned with Tethering. When testing an AT&T SIM from a friends UDP (no tethering) account, this is what would happen. My T-Mobile and Verizon accounts both allow it, so it just works.

SpookyTunes said:
I would confirm with T-Mobile that your line is provisioned with Tethering. When testing an AT&T SIM from a friends UDP (no tethering) account, this is what would happen. My T-Mobile and Verizon accounts both allow it, so it just works.
Click to expand...
Click to collapse
I have tethering on my account and have had it for 2 years. worked flawlessly on other devices before switching to this one. It also doesn't explain why it could work for hours at a time before failing. Or why it would consistently fail within minutes when playing LAN minecraft.

Well Huaweii has been an absolute joke, after 3 weeks of terrible communication and no transparency I finally received my phone in the mail (no email notification on if it is a replacement device or not) and the issue still persists. I'm at a loss for what to do.

Two problems after upgrading to Lollipop

A couple of months back, I updated from Kitkat to Lollipop using these great instructions and ever since, I've had two persistent problems, and I'm wondering if anyone else has:
1) Wi-fi cuts out every few days requiring a reboot fix. This seems to be related to some sort of DNS issue.
2) Receiving picture texts (MMS) show up as "Message size: 2KB Expires: (date)" with no way to download or view. I see no workaround other to tell friends to email me pictures instead of texting them.
In short, I've got two problems that involve sending/receiving data after I put a ROM on this Verizon phone.
I've tried a factory reset, but haven't gone back to Odin yet to try to put PB1 on again (or a different ROM?). The good news is SafeStrap recovery is on the phone now, so maybe I can play with that somehow. What can I try next to resolve these two problems? I can live with them with the reboot and avoiding MMS, but they are not trivial, and really, kind of annoying.
Thanks for any guidance or advice. Please help.