Database Develop

Tons of problems with Tilt after installing new CAB

I know this is my first post here but I've done my best to search the forums and I haven't found anything that looks like it helps me.
I just got my AT&T Tilt yesterday. It came unlocked (I'm using it with T-Mobile) and has an HTC ROM installed as well as various other apps (Ms. Pacman, TomTom 6, SuperDoku, etc.). I had some issues with it locking up yesterday (similar to what I'm experiencing now but to a much, much lesser degree) when I was playing around with it but those issues somehow corrected themselves.
This morning I installed the Tilt keyboard fix that TaurusBullba posted on here back in June to fix some mapping issues. Since I installed and soft reseted, everything has been going kinda haywire. The Wi-Fi turned itself off and I can't turn it back on. When I slide out the keyboard the orientation stays in portrait mode. When I try to shut down the phone using the power button it hangs forever. Now, actually, half the time I press the power button nothing happens at all.
I've tried uninstalling the CAB but that didn't fix anything at all. I'm afraid to try a hard reset because, from my understanding, I'm going to lose everything that came pre-installed on my phone for me. I should probably also add that last night I installed the Google Maps CAB with no problems whatsoever. Is there some simple solution I'm overlooking? Thanks much!

I would advise that if you have tried soft resets to try and resolve the issues and it hasn't worked, then perhaps a hard reset?
It sounds as if the software you have installed as either caused the problems or exacberated them (ie made them worse).
With hard reset it wipes everything back to when you got it. If you are able I would suggest that you plug it into the computer and make sure ActiveSync backups up your contents. You may also want to use this get all the files on the main memory either to the storage card or to you're PC.
As this is yo're first post I don't know how au fait you are with the above that I have mentioned

The preloaded apps will be reloaded again. You won't have an empty ROM if you do a hard reset. It will be as if you just flashed the ROM again.

Thanks for the replies guys. I went ahead and did a hard reset and it looks like the only thing I lost (or at least the only thing I miss) was TomTom. I've already reinstalled that using a link I found on here, and everything seems to be good to go.
I still have no idea what might have caused the problems though, so I'm afraid that they might come back or I might repeat some dumb mistake I made. I guess I'll just have to live with that for now.

clear storage / hard resets no big deal, just expect to do it every other week while you're finding all the cabs that work (or dont work) for you..
I generally clear storaged every week when i first got my tilt until I found all the app's I liked that didn't have side effects

Won't turn off and keyboard is dead

I'm experiencing a weird problem. All of a sudden my Kaiser won't turn off and the keyboard has stopped working. I've tried restarting it about 10 times and took the battery out for 5 mins and it's still doing it.
I really don't want to completely reset it, does anyone have any ideas what could be up with it?

Ok, so I just softreset it whilst it was on charge and it seems to be working now! Never had this bug before so I'd still be interested to know if anyone knows anything about this in case it happens again.

i had this the other week, it wouldnt do anything, load any programs, kept saying missing DLL files.
Turned out, when i uninstalled a program "Google Navigator" or something, it screwed my file system up.
Sounds like a hard reset is the only way to fix these sort of problems mate.

Yeah, I kind of guessed that, just didn't want to admit it .
Think I'm gonna upgrade to WM6.1 anyway so now is probably a good time to do it.

Touchscreen broke, way to bypass welcome screen?

Hey all, I've been looking around the past few days and didn't see anything on this particular issue.
Basically, I washed my G1 and had to get a new one. The one that got washed has been starting up (slowly, and not always), but the touchscreen no longer works. I reflashed the software to hopefully alleviate any of the problems when it was starting up. My initial thought was to use fastboot to flash the backup I made on my new phone with nandroid, but the bootloader isn't working properly (I'll try a reflash of that too).
So, do any of you guys know of any other ways to bypass the startup welcome touchscreen?

Try placing your finger on the Android, press the trackball, then lift the finger and press the trackball again
Tommy

IzzeLing said:
Hey all, I've been looking around the past few days and didn't see anything on this particular issue.
Basically, I washed my G1 and had to get a new one. The one that got washed has been starting up (slowly, and not always), but the touchscreen no longer works. I reflashed the software to hopefully alleviate any of the problems when it was starting up. My initial thought was to use fastboot to flash the backup I made on my new phone with nandroid, but the bootloader isn't working properly (I'll try a reflash of that too).
So, do any of you guys know of any other ways to bypass the startup welcome touchscreen?
Click to expand...
Click to collapse
Flash the ADP1 software.
Edit: You'd still need touch for that, sorry.

The driver was all wonky, uninstalled, reinstalled, fastboot works now Flashed over to my new G1's state, but forgot to take off the lock screen... Flashing yet again. Everything should be good from here.
Edit: Alright, washing the G1 makes it wacky. The touchscreen works now after restoring it to the new G1's state. Weeeirrrdd.
Edit 2: Anddd now the touchscreen doesn't work :S

well.. when my touchscreen broke i used remote control software to control my ppc from pc .. thats one way to bypass welcome screen, but won't get you much further. I used it for making a backup from my phone.

just leave it off for a while and keep it someplace dry and warm so it can dry out.

You may try to modify build.prop in the rom you flash
ro.setupwizard.mode=DISABLED
I think it will skip the setup

Sorry can't help myself. In the laundry?
I guess I'm wondering what exactly you did. I'm assuming it didn't make it into the dryer....
If you need the data off it, you might be able to ADB pull what you want to keep. If I'm not mistaken, ADB is as close as we have to remote controlling for Android at the moment.
There may be some places around, like PPC Techs, that can do hardware repair. I'm guessing what will happen is you'll occaisionally get it to work for brief stints after reflashing or whatever, but it'll keep conking out until the hardware issue goes away/gets fixed. Hardware issues do that, printers, routers, sometimes PCs.
Not to be a naysayer, but I don't think changing out the software is going to help.

I washed my G1 (was in pocket of jeans under the water for about 90 seconds), and after that I disassembled it to let it dry. It was running fine up to the day I SPL bricked it.

Hey.. i split water on my phone.. it couldnt have been that much but the touch screen wasnt working.. thought if i factory reset it, it may started working..
I dont actually understand all the lingo you guys use.. but any ideas on how i can fix it?
J x
oh the main issue is i cant get past the touch android to continue set up... please i just want my android to work!!! J x

I'm having a similar issue... My phone randomly stopped loading android.process.acore and it's messing with my heart. The touch screen doesn't respond but I can use the trackball to navigate, and every acore process force closes instantly upon activation, such as dialer, contacts, music, etc. The wonderfully helpful people at T-Mobile instructed me to do a factory reset on my G1, and it should fix the problem.
New problem: I can't get past the "Touch me, I'm an Android logo" screen. When I click Emergency Dial, it force closes because the acore processes are still messing up. The intention today was to reload the Cupcake SPL and Radios onto the phone. The issue there is that I can't touch the screen to start the USB connection with my computer.
Anyone have any suggestions aside from paying another $130 bucks??

This will do the trick
google androidscreencast it will allow you to contol your G1 via your PC
...let me know if you have resolved android.process.acore im on the same boat and a wipe and flash has yet to solve it...

same boat for me too! wow, this is three, maybe 4 of us currently experiencing same problem!
I love screen cast. Droid explorer is great too, basically a GUI for adb, and has a plugin for screen cast. Too bad you have to be online though, I'd love to use screencast offline!
I'll update if I figure out the error problem!

Well it looks like a complete wipe and a flash back to non root status is whats gonna take to fix the android.process.acore issue. BUT now w/o root, I cant access the G1 via android screen cast...so im totally stuck on the "Touch Android to begin" screen... sucks to be me lol

I think I'm in the same boat. I didn't know about the screencast application before I did a complete wipe to stock. So I'm stuck at the "touch android" as well. This phones pretty much junk to me right now.

I wonder if any of you have tried restoring your latest back up?

Yes, no help, either on the touchscreen, or the incessant errors. I think there must be some code that checks whether the touchscreen works, and sends back an error if it doesn't. I've tried almost every combination of radios and spls mixed with several different cyanogen roms going back to 4.1, both fresh installs and nand restores.
Currently I'm running the latest cyanogen, radio and hard spl. I get errors often, and can't use the phone / dialer at all without force closing. For now texts and google voice work so I have at least some communication. Ironically, I can't even unroot because none of the spls will flash dreaimg.nbh, but that probelm is in my unresponsive bootloader thread.
Sorry to hear about your predicaments allthrottle and r1ch. Strangely you are right where I'm trying to get, I have warranty coverage to fall back on.

Way, Way Too Many Reboots

Hola,
Dont know if Im over (ab)using my phone or if anyone else has the same issues.
My phone loves to reboot
-When I answer a call once in a while.
-When I turn off StreamFurious once in a while.
-When I disconnect the usb every once in a while.
-For no apparent reason every once in a while (ex. Ill find it turned off in my pocket or on my desk, but I never turned it off)
This happens about 3-5 times per day.
Also, on some of the StreamFurious reboots, it turns off and I have to pull the battery or it gets stuck on the G1 screen and never finishes.
Do you think I need a replacement or is this just a version 1 hardware thing?
Thanks in advance for your input!

We are going to need some more information to better assist you.
1) What Build are you using
2) Are you running Apps2SD
3) How much space do you have left on your internal storage?

Sure, thanks
Jf 1.5
Radio: 26I
No A2SD
31MB free
Nothing crazy.
I wipe every time I flash.
I've tried factory resetting too.
I try to keep the system clean.

he3 said:
Hola,
Dont know if Im over (ab)using my phone or if anyone else has the same issues.
My phone loves to reboot
-When I answer a call once in a while.
-When I turn off StreamFurious once in a while.
-When I disconnect the usb every once in a while.
-For no apparent reason every once in a while (ex. Ill find it turned off in my pocket or on my desk, but I never turned it off)
This happens about 3-5 times per day.
Also, on some of the StreamFurious reboots, it turns off and I have to pull the battery or it gets stuck on the G1 screen and never finishes.
Do you think I need a replacement or is this just a version 1 hardware thing?
Thanks in advance for your input!
Click to expand...
Click to collapse
Something like this happened to me about a month or more ago. It was everytime I try and use my phone when I was charging it, it would reboot. After a few days it would just do it at random. I just called tmobile and they just sent me a new one out.

the same thing is happening to me. my phone randomly crashes/reboots and i was starting to think it is the Haykuro build im using. is there any way to test the hardware? is there something like that in an app?

help
Are you using ahome or someting like that cause those programs cause problem with 1.5 uninstall all your theme apps if you have any

No, no themes.
Called t-mob, since I've had the device (sans insurance) less than a year, they are sending new hardware without a battery to replace mine. I decided to add insurance to the new hardware just incase. Thanks for the input! Glad I called!
Now to virginize the phone... heh

I have the same problem. There's a lot of this going around. It sure seems like a coincidence that it started with Cupcake for most all of us.

This has been something that has been happening since the RC33 load it...

Now I got the stupid random reboot problem. This is a warranty replacement and my first one never did this. I guess I gotta get another warranty replacement. Anyone find a definitive cause for this yet?

almost 100% sure you have a hardware problem

savethechicken said:
This has been something that has been happening since the RC33 load it...
Click to expand...
Click to collapse
I used to have the same issues WAAAY back after I recieved an OTA update from tmobile for rc33 or whichever one it was in march... back when I had still no idea what "cupcake" was...
always seemed to happen when I was:
answering a call, recieving a text while in a call that I started, etc.
but after I found out about the linux bit of my phone, I immediately cracked it... and... cupcake... and then? there weren't any reboots.... I wonder whats up with that? maybe something to do with OTA spls? I don't remember lol

rikupw said:
I used to have the same issues WAAAY back after I recieved an OTA update from tmobile for rc33 or whichever one it was in march... back when I had still no idea what "cupcake" was...
always seemed to happen when I was:
answering a call, recieving a text while in a call that I started, etc.
but after I found out about the linux bit of my phone, I immediately cracked it... and... cupcake... and then? there weren't any reboots.... I wonder whats up with that? maybe something to do with OTA spls? I don't remember lol
Click to expand...
Click to collapse
RC33 was the OTA was in March I believe maybe Feb. This didn't happen as much on RC30 and then RC33 came out and this started to happened more often. Obviously it is not the ROM doing it as not everyone has the problem but something seemed to trigger it on some devices.

alapapa said:
almost 100% sure you have a hardware problem
Click to expand...
Click to collapse
Going to have to agree. This is starting to seem like a Hardware problem, considering all the feedback we are being given.

I have the same exact problem.
It's definitely a hardware issue.
I was thinking it was because my extended battery pack is a little loose or some loose wiring. It happens when the phone is bumped a little. Like putting it on a table too roughly or flipping the screen up too quickly or it shaking in my pocket. Probably going to replace it.

I have this same problem...i had it originally with RC33 then it went away with the cupcake update and I recently root and install cynogen's build and its back to screw up my day
i don't think its a hardware thing ...at least in my case doesn't make sense to be gone for a month and then come right back after rooting

I also experience random reboot issue. Usually when the phone hang first then next thing you know, it is rebooting. Sometimes the phone will be just sitting there and it will reboot by itself. I always thought it is the ROM issue, never suspect hardware. I am running an old version of Dudes v1.3a build.

For me too
I am getting too many reboots too, just got a replacement phones(previous one did this too), same with this phone, first i thought it was Hardware but now it think its the roms. On hero it rebooted 3 times while booting the first time, on cyanogen it rebooted in a couple of hours, just dont know what the problem is, maybe abusing the phone

I got a replacement phone and still have reboots issue on it when booting, playing music etc.

charnsingh_online said:
I got a replacement phone and still have reboots issue on it when booting, playing music etc.
Click to expand...
Click to collapse
Makes me wonder on the apps your using in the background or settings you have up, or even the ROM. Do you have any extra info whats up before it reboots? Does it choke out due to low memory maybe?

My Diamond's acting strangely...

Hello, over the last few days, my Diamond's being doing something very strange and seriously annoying:
All of a sudden, my handset began to perform sluggishly, and eventually hanging, meaning I had to reset.
After this, the handset had returned to factory settings (apart from the internal storage card) and required setting up as new.
Once I'd set the phone up again, re-installing all my usual programs, the phone worked as normal for around 6 hours, then the same thing happened.
I've installed a new ROM, and had the same trouble. The phone isn't completely unusable when symptoms start (I can still send and receive texts and make calls) but I can't use any installed programs such as Opera etc.
The way the phone acts feels similar to when a PS harddrive begins to develop bad sectors etc.
Anyone had similar problems and been able to fix without having to send the phone away? Somehow I don't think my operator would repair it!
Thanks for any help.
N x