Little Help? - G1 Android Development

hey guys, love the Forum, used it for about 7 phones I've had over the years, but recently i effed up:
so my G1 has worked great and I've been running jf1.42 rc33, and then had the android aero theme. and last night a birdie told me that cupcake was coming so I got a little download happy and didn't realize that it's not out for my phone yet, just the ADP.
Long story short i tried to install it on my G1 and then realized my error and reinstalled jf 1.42 - but now my home button doesn't do anything and my green call button doesn't bring up the contacts/recent calls stuff anymore. but it does work to answer a call or send a call, and the home button will bring it out of sleep and i can enter the recovery mode.
Anyone have any ideas? Factory reset? simple patch-fix? any input would be welcomed before tonight (or at all really) and I'll let you all know what works!!
Thanks in advance!!

bessertier said:
hey guys, love the Forum, used it for about 7 phones I've had over the years, but recently i effed up:
so my G1 has worked great and I've been running jf1.42 rc33, and then had the android aero theme. and last night a birdie told me that cupcake was coming so I got a little download happy and didn't realize that it's not out for my phone yet, just the ADP.
Long story short i tried to install it on my G1 and then realized my error and reinstalled jf 1.42 - but now my home button doesn't do anything and my green call button doesn't bring up the contacts/recent calls stuff anymore. but it does work to answer a call or send a call, and the home button will bring it out of sleep and i can enter the recovery mode.
Anyone have any ideas? Factory reset? simple patch-fix? any input would be welcomed before tonight (or at all really) and I'll let you all know what works!!
Thanks in advance!!
Click to expand...
Click to collapse
Try a wipe(start up phone with home+power and then alt-w at the menu). That said, there are cupcake builds for the G1 as well on here, including one of them by JF himself(JF1.5)

I've only seen jfv15 for the adp - and I thought that they were different variations of the Dream... am I wrong about this? and yeah I think my guy could use a fresh start.

bessertier said:
I've only seen jfv15 for the adp - and I thought that they were different variations of the Dream... am I wrong about this? and yeah I think my guy could use a fresh start.
Click to expand...
Click to collapse
JF1.5 is a modified version of the ADP1.5 firmware which will work on rooted G1's as well as ADP's.

all right well I have class for 2 hours now (and since I'm such a good student I'll wipe and rewrite my G1 and let you all know how it is once I'm done

and the ADP is the G1 minus the T-mobile branding and more unlocked bootloader/software

ok - update 1 : yes wiping the phone to factory default fixed the call button and the home button.
downloading jf1.5 now and will install it - so the ADP version wont have the tmobile myfavs and that stuff, but will work just fine on my phone?

Yes.
Make sure you download and apply the separate radio update, which is also required. http://sapphire-port-dream.googlecode.com/files/ota-radio-2_22_19_26I.zip

mmmk I did download JF's radio update, I'm assuming that it's this update
and YEAH!!!! my phone works perfectly now, just going back through grabbing all the apk's off my computer and reinstalling everything, sah-weet, loving it!
Thanks guys!! (or girls, gotta be Politically Correct nowadays...)

Related

Safe Mode on G1

From androidcommunity.com, not sure how useful.
found a way to enter "safe mode" which will bypass the initial gmail signin and allow you to straight to the good stuff with out activating via google. You can also bypass the security drawing pattern.
1. Power off your device
2. While device is powering back on press and hold the "menu" key, keep holding it past the G1 and android splash screen.
Phone will boot all the way to the main screen and display "safe mode" in lower left corner.
I have confirmed that data is still fully operational and all of my downloaded programs.
http://androidcommunity.com/forums/f41/g1-safe-mode-2565/
Which firmware are you running? I'm on ota rc30 and I can't repro. I wonder if this was fixed in an update.
I should say, I can get into safe mode, but I can't get past the initial google sign-in screen.
Bypassing Google Activation is not Possible in any Version
Bypassing the Drawing Pattern was Patch in RC30
For for RC30 user they are out of luck.
hetaldp said:
Bypassing Google Activation is not Possible in any Version...
Click to expand...
Click to collapse
Shouldn't it help to start the phone with non T-mobile sim card?
Why u require to bypass Activation Process
You can Unlock the Phone and add your GPRS Setting and Activate the Phone Officially on your Carrier.
Well... Don't you still need valid T-mobile sim-card for the first boot after unlocking?
The real reason is, I tried to use my G1 without G1 data plan (-$25 cheaper . It was Ok, I could use WiFi for internet, but I made a factory reset and was not able to pass that activation after - can not use WiFi for that.
You require Valid TMobile SIM only for Activation becuase GPRS Setting Preset in Phone.
But if you have Any other Non TMobile SIM Card Press Menu Button this will popup APN Setting Just Press it again Press Menu Button this will popup New APN Just Add your Carrier APN, Mobile Country Code and Mobile Network Code And reboot. If you can see G or E or 3G on top Bar your Data is Activated Just follow with your Google A/c and Password and you did it
hetaldp said:
You require Valid TMobile SIM only for Activation becuase GPRS Setting Preset in Phone.
But if you have Any other Non TMobile SIM Card Press Menu Button this will popup APN Setting Just Press it again Press Menu Button this will popup New APN Just Add your Carrier APN, Mobile Country Code and Mobile Network Code And reboot. If you can see G or E or 3G on top Bar your Data is Activated Just follow with your Google A/c and Password and you did it
Click to expand...
Click to collapse
@Hetaldp
Thanks 8! i was going almost crazy to get around this checked almost every forum but no body could give me a suggestion like this! thanks for you now i know how to set up my own account!
WBR
ReyTech.
I was able to get into safe mode via holding down the Menu Key while booting. Open Home was giving me issues and i was unable to get past the "Android" splash screen. Booted to safe mode via the initial instructions and was able to uninstall open home. I'm using JF's 1.5 ADP w/LucidREM App2Sd image. So the "safe mode" works in the newest release. I can't account for getting past the drawing pattern thing since i don't lock my phone and not sure about the activation thing. But it does boot to safe mode
hetaldp said:
Bypassing Google Activation is not Possible in any Version
Bypassing the Drawing Pattern was Patch in RC30
For for RC30 user they are out of luck.
Click to expand...
Click to collapse
In safe mode, only stock apps are loaded. I can post the whole log if anyone wants me to. And yes, its much like windows' safe mode, in a sense.
My wife's g1 is stuck in safe mode.
I have tried the holding menu+power buttons till it boots thing but nothing.
I flashed back to jk 1.41 and nothing.
Any ideas on how to get out of this safe mode.
BigJPR said:
My wife's g1 is stuck in safe mode.
I have tried the holding menu+power buttons till it boots thing but nothing.
I flashed back to jk 1.41 and nothing.
Any ideas on how to get out of this safe mode.
Click to expand...
Click to collapse
?
what do you mean? if you hold the menu + power button, it puts it into safe mode..
boot by holding the power only? also if you know how to use adb hook up your phone and do the following in a cmd prompt
Code:
adb logcat
we may be able to find something causing it, even if it is a little late. and by jk 1.41 you mean jf right?
andonnguyen said:
In safe mode, only stock apps are loaded. I can post the whole log if anyone wants me to. And yes, its much like windows' safe mode, in a sense.
Click to expand...
Click to collapse
B-man007 said:
?
what do you mean? if you hold the menu + power button, it puts it into safe mode..
boot by holding the power only? also if you know how to use adb hook up your phone and do the following in a cmd prompt
Code:
adb logcat
we may be able to find something causing it, even if it is a little late. and by jk 1.41 you mean jf right?
Click to expand...
Click to collapse
I'm sorry, Yeah I meant Jesus freak. If by adb you mean having the setup to develop on the pc then nope, don't have that.
Now I did search this forums and did a google search and found out that if I power off the phone then press and hold both "menu & power red button" I was supposed to get rid of the safe mode, I should say get out of safe mode.
When the phone got stuck in safe mode she was running on of the first rom from JF for 1.5. I also read that if the holding down the bittons thing didn't work I should either reflash or master reset. Is master reset what you do from the phones settttings?
Maybe I'm just missing something. I'm usually not this dumb @ following directions lol. I got on my phone one of the hero rom w apps2sd so I have done some major things (for me) to the phone (this on a different phone. My phone lol). But this got me scratching my head.
Thanks for replying man.
* update
I did the "return to master settings" thing. The phone rebooted and went to the console then I did an alt+w and the thing rebooted to the first activation with the dang "safe mode" still there. Sorry if I'm having a hard time explaining this.
She don't have that new spl. Do you think she can run a non hero rom with it? I want to try and get the new radio and maybe the spl and that newer recovery image in her phone and just maybe a newer 1.5 stable non hero rom and see what happens, eventhou I think non of it has anything to do with phone being stuck on safe mode.
BigJPR said:
I'm sorry, Yeah I meant Jesus freak. If by adb you mean having the setup to develop on the pc then nope, don't have that.
Now I did search this forums and did a google search and found out that if I power off the phone then press and hold both "menu & power red button" I was supposed to get rid of the safe mode, I should say get out of safe mode.
When the phone got stuck in safe mode she was running on of the first rom from JF for 1.5. I also read that if the holding down the bittons thing didn't work I should either reflash or master reset. Is master reset what you do from the phones settttings?
Maybe I'm just missing something. I'm usually not this dumb @ following directions lol. I got on my phone one of the hero rom w apps2sd so I have done some major things (for me) to the phone (this on a different phone. My phone lol). But this got me scratching my head.
Thanks for replying man.
* update
I did the "return to master settings" thing. The phone rebooted and went to the console then I did an alt+w and the thing rebooted to the first activation with the dang "safe mode" still there. Sorry if I'm having a hard time explaining this.
She don't have that new spl. Do you think she can run a non hero rom with it? I want to try and get the new radio and maybe the spl and that newer recovery image in her phone and just maybe a newer 1.5 stable non hero rom and see what happens, eventhou I think non of it has anything to do with phone being stuck on safe mode.
Click to expand...
Click to collapse
Its no problem I'm pretty sure I understand what your saying. Your menu key isn't, stuck is it? The new SPL by Haykuro will work on any almost any ROM, Hero or not. Flashing the radio might help and probably should be done. You can also try to start from step one and go through the steps to re-root it, but DO NOT PUT THE NEW SPL ON YOUR PHONE IF YOU ARE GOING TO DO THIS. downgrading the radio and/or un-rooting while the new spl is still on the phone will brick your phone.
I don't know how the safe mode is persisting across a master-reset (Alt + W)
If you are under warranty or insurance, it might be a good idea to unroot and restore original settings, and have them look at it.
You should also wait for more input by some of the community members here as I'm still inexperienced with Android.
The wife is desperate. She went to our buddy on the tmo store and he tried everything they know on it ofcourse then he found out it was a flashed g1 and told her it might be something screwy going on with it.
At the end of the visit he got the warranty department to send her a new one because "the menu button isn't working" yeah yeah... lol
Anyways... should I un root it anyways for when I have to send it? Thanks for the help man. I've been a member here since I had a dash a couple of years ago but usually don't post cause I sually find the answers to my problems by searching... the ol art of searching ah
Thanks again... ill check the un rooting thread again and will try that.
lol i've only been here a few days and i learned a lot. the people here are generally very helpful and i find almost all of my questions answered so i don't have that many posts either.
Ya you should unroot it because you don't want to have your RMA rejected and besides.... its getting RMA'ed anyway so whats there to lose
B-man007 said:
lol i've only been here a few days and i learned a lot. the people here are generally very helpful and i find almost all of my questions answered so i don't have that many posts either.
Ya you should unroot it because you don't want to have your RMA rejected and besides.... its getting RMA'ed anyway so whats there to lose
Click to expand...
Click to collapse
ive sent back a few g1s rooted with various roms on them, i even asked tech support if it was a issue that it was rooted, let alone running a leaked version of cupcake at the time
the responce i got back both times i asked was that as long as they can get the phone back to a stock rom, it didnt matter what rom was on it, ive yet to have an issue sending back g1's with cupcake on them before cupcake was released
Dimath said:
Well... Don't you still need valid T-mobile sim-card for the first boot after unlocking?
The real reason is, I tried to use my G1 without G1 data plan (-$25 cheaper . It was Ok, I could use WiFi for internet, but I made a factory reset and was not able to pass that activation after - can not use WiFi for that.
Click to expand...
Click to collapse
If you have a SIM with no data plan, you can just bring up the settings menu, connect to WiFi, and then activate. How? Connect using adb shell and type:
Code:
am start -a android.intent.action.MAIN -n com.android.settings/.Settings
All credit goes to JesusFreke for the find:
http://forum.xda-developers.com/showthread.php?t=452316
I really do hope someone will find some interesting uses for safe mode. Since I've already activated with my Google account, Gmail and Market both worked fine for me in safe mode. The only difference I see so far is that all widgets are disabled except: Analog clock, Calendar, Music, Picture frame, and Search. It did not bypass the "connect-the-dots" security drawing pattern for me. Anyone notice some other differences in safe mode?
ive got a black g1 and its stuck on the activation screen how do i get it to the home screen !?.
elkhiid said:
ive got a black g1 and its stuck on the activation screen how do i get it to the home screen !?.
Click to expand...
Click to collapse
What do u mean stuck ? As in u dont have a data plan and want to activate it ? if so refer to this.

How do you make sure there's no evidence that you ever rooted your G1?

So earlier today I decided I wanted to take my phone off root because it had become really buggy so I followed these instructions from another thread:
"download this http://koushikdutta.blurryfox.com/G1/DREAIMG-RC29.zip unzip it and load it to the root of your sd card and reboot the phone holding down the camera and power key then follow the instructions in screen then reboot and wait for the update. how many more times must i type this? can you people not see the search button."
SOURCE: http://forum.xda-developers.com/showthread.php?t=478856&highlight=original+firmware
After doing this, my phone was working fine. Everything worked. For some reason like 2 hours later, my threaded txt messages started showing up in the wrong order. I called T-Mo and they had no solution so they're going to sen me a new one. I wanna make sure there is no evidence on the phone that it was ever rooted. How do I make sure? Thank you so much!
just make sure you updated to original firmware after you changed your fastboot images... that is... if you changed the fastboot images... then you are good to go.
I never messed with fast boot and all that, after I rooted it, I updated JF1.41 with auto rotate and multi touch. thats it. when I went to original firmware, literally I did exatly what he said with the DREAIMG.nbh file, and rebooted. ( Copied the DREAIMG.nbh file to root of SD, restarted with camera+power, ran the update, rebooted) Was there a step I missed?
The problem now is, I dont wanna change much at this point bc if it fixes the threaded txt issue, then theyll prob charge me for the new phone if the txt problem is fixed.
find the SPL thread(sticky) and make sure that your bootloader screen looks like the stock one and you should be fine as well, RC29 already wipes everything else
my threaded txt messages were going in a crazy order last night. but i assumed it was cuz of daylight savings time lol. my g1 to g1 messages would show up in correct order. but everyone else' messages were in screwy order.
yeah its because of DST. T-mobile changed the clocks to early lol. Either that or the g1 screwed something up.
we will see what happens
I posted this in another thread so ill be brief ...
due to a hardware error I returned a white g1 which I had rooted and tricked out with JF's RC33 a theme and the dev BL... I was feeling lazy so I just wiped it and made sure it was back to the stock theme and sent it off with a flat battery, I dont think they will scrutinize them much, we will see, most of the time you play stoopid say you took it to a store and they did some stuff, whatever, PROVE IT, pry my replacement from my cold dead hand.
ill post if I get some response to my tricked out g1 returned due to a bad bt radio
bhang

is it ahome????????????????

after installing ahome my touchscreen was a little to responsive when i dialed 1 pressing once it would dial it 2 times so i thought a factory reset would fix it when i did the factory reset my phone wont get past the flashing android im probably just going to flash back to rc29 and check with if the touch screen works like it should if it doesnt i can take it to t-mobile for a fix if it does work ill go back to jf rc33 1.42
Oh. Ok. Thanks for telling us.
nabzilla1990 said:
after installing ahome my touchscreen was a little to responsive when i dialed 1 pressing once it would dial it 2 times so i thought a factory reset would fix it when i did the factory reset my phone wont get past the flashing android im probably just going to flash back to rc29 and check with if the touch screen works like it should if it doesnt i can take it to t-mobile for a fix if it does work ill go back to jf rc33 1.42
Click to expand...
Click to collapse
First of all... let me address this before someone rips you apart here. Your question (if it is one) is a bit difficult to read. I am certainly not an english teacher but maybe a period here and there would make it easier to understand. Because I honestly don't know if you are asking a question, stating that you're having a problem with reflashing, going back to factory settings or other. I mean I had to read it 5 times!
Secondly... if you do a factory restore from the settings and you get the flashing android on boot you should let it keep flashing for a few minutes. You need to be patient because it is wiping all of your previous data/settings and restoring them to default.
Third. If it stays on the flashing android for longer then say three to five minutes (depending on how much you need to wipe) then go ahead and boot up in recovery mode and do a wipe from there. If you still get stuck on the flashing android then yes... reflash.
Fourth. Do not assume it is an app that causes this problem unless you are CERTAIN of it. Hundreds if not thousands of people have downloaded this app (including myself) and have not had a similar problem. Maybe do a search for the app name and read what people are saying about it. If it is the app then believe me you won't be the only one commenting. If you're lucky there will be a fix so you won't have to wipe or reflash.
Finally... every so often (especially before making a major change like apps to sd, themes, etc) it'll be a good idea to do a backup with Nand so even if you do end up messing something up (by app or user error) you can always reflash your image to your phone.
Good luck!
EDIT: Whoops! Wrong thread!
I'm very sorry for my poor English but my story is after installing ahome
everything was fine until I rebooted my phone. After rebooting the phone I
tried dialing a number and when I pressed a number once the it would dial
the number twice for example when dialing 7 instead of only dialing the
number 7 it would dial 77, or when using useful switchers turning off the wifi I
would try to check the wifi on but with one push it would check and uncheck
the wifi. Later I did a factory data reset and rebooted the phone I couldn't get
past the flashing android. I reverted back to stock rc33 just in case its a
hardware problem I can let t-mobile know thanks for the replies
i doubt it's a hardware problem.
i had the same problem, coincidentally after installing aHome; i was unable to get past the "flashing android" screen. The first reboot that i did, though, was after using the JF auto-updater app, so i'm not entirely sure where the problem lies.
long story short, i wiped my system, and am now in the process of installing Windows and the Android SDK to my system so i can do a restore.
thanks im gonna go back to root then
yeah, aHome still has lots of thigns to be fixed specially that force close issue every time u return to home :/ i liek dxtop better dont feel like scrolling tru 10 pages like the iphone..

accelerometer not working

I'm not sure it has to do with this, but I flashed my NAND with nandroid with one from a different G1.
and one of the axes in the accelerometer doesn't work at all (its stuck).
any idea how to fix this ? (again,i'm not sure the nand has to do with this)
I had the same problem and ended up just doing a whip and setting everything back up. I had a black G1 that I traded for a White one. It might of also been that i flashed a different version of JF on it was well but wasnt worth the time to flash back to 1.41 nand retore and then flash to 1.42. It only really took me about 15 mins to reinstall all the apps and setup options.
i think i read somewhere that accalerometer doesnt work with nandroid.... mine stopped working this week- just did a wipe and a reflash and it works fine now.....
Can Someone help me? I was playing Labyrinth and when I finish, the accelerometer has stopped working. It does not work with anything, either games or any application. nybody know how to reactivate? Thanks.
PS. I Dont make any mod on G1. It is R33 version.
PS2: It never dropped.
Hmmmm, this happened out of the blue for me a long time ago. I think I had to reinstall the firmware, and maybe even a wipe. Been fine ever since...
-oldsk00lz
Accelerometer probelm - Just happened to my rooted rc33
Hey gents, this just happened to my rooted g1 yesterday.
The accelerometer now only works on one axis. I'm pretty sure its a software issue. I tested the accel using Api demo's OS/sensors. The one graphical output and the three dials at the top. The graph changes and registers the change when i rotate it but it just doesn't want to work with any programs that use the accel. ie labrynth, bubble level etc.
I'd really like to know what happened, what caused this. I didn't drop my phone or do anything of the sorts. I did max out my memory installing too many apps that day but I couldn't see that affecting it.
***re-installing is not an option if this constantly happens. I don't have a data plan to keep logging into the start screen every time I wipe my unit. I know there's a thread about getting around this but I'm still not to comfortable using the sdk.
I haven't tried to wipe and reinstall via recovery mode yet. I was wondering though,
1. how do i find out what version of jesus freak rc33 i have. I think Its 1.41 but I forget and just looking at the buildnumber i can't figure it out. and are the newer versions better should i be upgrading?
2. Is there anyway to fix this with a reinstall. Is there anyway to examine the accel. data readout or code.
3. If not, should i just try wiping and reinstalling the same version of jf rc33 or do i have to reinstall a packaged (oem) version of rc33 and loose root (i don't want that to happen,root is a necessity for me )
I'll glady post my findings and even write up the step step process. I just need some answers first.
Thanks for you help (your form seems to be the only place i get solid answers about my phone) http://forum.xda-developers.com/images/icons/icon10.gif
this happened to mine a while back. a wipe and reflash fixed it. use mybackup to quickly get back to where you were.
this just happened to me the other day i posted here about it but it might of been deleted as i was the only one to post and answered my own question through trial and error.
you might try the app bubble it might allow you to calibrate it (i didn't know this until i read it somewhere this morning) other than that when i had the issue i just reinstalled everything the old fashioned way one apk at a time although first you would need to alt+w in the loader menu then install the latest jf update

Wake issues with newer ROMS

I am posting a new thread because I'm experiencing the issue with several diffrent ROMs so obviously it's a general issue not a ROM specific one. Also I have read through countless pages of posts with no luck so hopefully someone can shed some light. Over the past few days I've flashed (forgive my spelling) dude's .5, ravenge, cynogen 3.4 and I have been having issues with the phone not waking after either I put to standby myself or the screen times out. I know it's not an issue with my phone or card because I go back to virtudude's ROM without the issue. I have tried everything, formatting my partition, ext2, ext3, wipe, no wipe, everything I can think of and still have the issue accross mutiple ROMs. I know it's not just me because my friend with a G1 is having the same issue, as well as many people posting in the threads. Can someone please point me in the right direction to fix this issue please?
My phone:
G1 with JF 1.42
Newest SPL 2005
Newest 26I radio
8gb SD card, class6, ext2 or ext3 partition (same issue on either)
Thanks in advance for any help!
me too
I noticed this same problem, its related to wifi, when I disable wifi my phone wakes up, also I have searched everywhere too for a solution. I think the compiled wifi deiver in these roms are not compiled right. So its either this or some other problem.
Is your phone connected to wifi with wpa2 personal? One other thing I noticed is this happens at random, when it does happen adb and ddms say device is offline when the led is blinking, also bottom of phone gets hot.
Can any devs shed some light on what exactly happens when the phone shuts off? Because something is locking the phone up when the light goes off and is in standby.
I am doing a test, im leaving wifi on while the screen is off in settings, will report back
This happens to me also but its only with hero I also have the new radio and spl. I can run hero with no problems as long as I don't use apps to sd or lucids txt. The wired thing is that after I use any apps to sd it works great but only for a day sometimes a few hours. Then I will start to see freezing up or it won't wake up at all, unless I reboot or pull battery. I've tried to reformat my card, resize my partition I'm also lost on this one fresh out of ideas.
Do you guys think it might have somthing to do with the sdcards? Im useing a 4g class 6 transcend micro SD, its only about 2 weeks old. Jason what other roms gave you these problems?
defconoi said:
Is your phone connected to wifi with wpa2 personal? One other thing I noticed is this happens at random, when it does happen adb and ddms say device is offline when the led is blinking, also bottom of phone gets hot.
Can any devs shed some light on what exactly happens when the phone shuts off? Because something is locking the phone up when the light goes off and is in standby.
Click to expand...
Click to collapse
I personnally don't see the correlation between locking and WiFi, I was at work the other day and flashed a ROM and it was doing it. I have my WiFi off at work so that wouldn't have been the case that day. I do notice the bottom of the phone getting hot though.
In response to the other person with the sd card question I really don't think it's that as I have a class 6, have formatted every way possible. Unless the issue has to do with apps2sd, I use apps2sd on every ROM.
Glad to see I'm not the only crazy one on xda!
joe v said:
Jason what other roms gave you these problems?
Click to expand...
Click to collapse
Almost every ROM to come out in the last couple weeks has done it. TheDude's .5, Ravenge's ramjet, Cyanogen's 3.4.1, and the Cyanogenized Rogers ROM.
You know looking at these the one thing these all have in common is being Cyanogenized. And the only ROM to come out in the past few weeks that hasn't had that issue is Virtuedude's Rogers ROM, which isn't Cyanogenized.
If any devs are reading this thread if you can make a version of your most recent ROM without Cyan's build kernel and boot and see if that helps. I'd be happy to test it for you to try and get to the bottom of this. If you wanna shoot me an email hit up jasonsyn at gmail.
I've had the same problem, but for me it started after flashing Cyanogen's 3.4 release. Since then I've reverted back to his 3.3.3 release and everything is fine again. Perhaps it has something to do with the new SPL and these ROM's?
That seems to be the one constant among all of us with problems, we've all flashed the new SPL and radio.
EDIT: I asked cyanogen about it, we'll see what he says.
indiekid97 said:
I've had the same problem, but for me it started after flashing Cyanogen's 3.4 release. Since then I've reverted back to his 3.3.3 release and everything is fine again. Perhaps it has something to do with the new SPL and these ROM's?
That seems to be the one constant among all of us with problems, we've all flashed the new SPL and radio.
EDIT: I asked cyanogen about it, we'll see what he says.
Click to expand...
Click to collapse
Yeah but I've had the new SPL and Radio for a month and this just started a week or so ago...
I am having the exact same issue. I usually have wifi bluetooth and 3g disabled (saves battery) I noticed this started after grabbing the new spl, ever since it's been freezing in standby randomly. I'm going to try Virtudude's rogers rom to see if the combination of Cyanogen's boot image and the new spl is causing the freezing. Hopefully seeing as Virtududes rom isn't based on Cyanogen's boot image it won't freeze. I'll report back with my results.
I thought my button got worn out. I never had the symptoms on rc33. When I switched to cupcake back during hatkuros prime just before dudes first releases I noticed it. I thought if it wasn't my button it might be somehow related to jf kitchen since almost all my roms touch it at some point. Just speculation though, donno what causes it.
Hey what recovery image are you all running?
I'm gonna flash the new Cyanogens 1.2 Recovery image and see if that's the issue.
Ok so how gay is this? I just hung up from a phone call and the phone is stuck sleeping! I was using it and it won't wake up, this is so incredibly frustrating!!
I have the new recovery image, 3.4.1, and still issues.
Jason Syn said:
Ok so how gay is this? I just hung up from a phone call and the phone is stuck sleeping! I was using it and it won't wake up, this is so incredibly frustrating!!
I have the new recovery image, 3.4.1, and still issues.
Click to expand...
Click to collapse
try holding down menu or the power button...i had this issue and my sd card would "unmount unexpectedly" and then this ended up into my sd bein fried
for those who are having this issue, try saving a log of it from ddms after that adb shell reboot thats what ive been doing ... instead of removing the battery, though my issues seem to happen every 24 hours i was on cy's 1.1 just flashed 1.2 perhaps that was is the issue?.. either way... we should try to collect all the info we can while this is happening to us.
dbhatesyou said:
for those who are having this issue, try saving a log of it from ddms after that adb shell reboot thats what ive been doing ... instead of removing the battery, though my issues seem to happen every 24 hours i was on cy's 1.1 just flashed 1.2 perhaps that was is the issue?.. either way... we should try to collect all the info we can while this is happening to us.
Click to expand...
Click to collapse
Ok I'll be happy to but I'm a linux virgin...would you mind giving me step by step in adb and I'll give whoever the log that can make sense of it.
This happens to me also on The Dudes Roger built. I don't have WiFi enabled so it isn't that it seems pretty random and just I get no response from the phone and have to so the soft reset (Call Menu Power) and then it'll work again. Normally only happens like once a day though so I can live with it but it is a inconvenience and can be annoying if it does it when you actually need to use your phone for something with some importance.
well if you're on linux and have it to where adb runs from terminal , just type
Code:
adb shell reboot
but before all that ddms (dalvik monitor) just type ddms in terminal it will boot up and show everything your phones basically working with.. and issues,
now if your linux terminal doesnt work well with adb (cant get it to work , google "50-android.rules" and "51-android.rules" n see if those help, and also set your echo path right )
now if you're on windows just hit windows key + r type cmd , and set yourself into the sdk/tools directory, then type ddms that will start the dalvik monitor (try and save a log) make sure the log saves before rebooting the phone, when you're done you can just ctrl+c and type adb shell reboot, and your phone should reboot.
[just the basic]
i've ran into this intermittently...most of the time while using the browser or using the onscreen keypad during a phone call.
I'm on JF CRB43(which is 1.51 i think) with the Hard SPL and JF Recovery.
Only thing I've been able to do to get the phone to wake up is wait. eventually it'll come around. or pull the battery, which i try not to do.

Categories

Resources