Wake issues with newer ROMS - G1 Android Development

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.

Related

Anybody want to be a guinea pig

http://forum.xda-developers.com/showthread.php?t=743506
I was wondering if anybody was willing to try this on their captivate and see if it worked for us or any dev's willing to try and port this over to our side.
seems to be working fairly well for them
edit: their hitting 1400+ Quadrant scores and all functions work on their phone from what I see
UPDATE 3:
Tutorial:
-1. Download VibrantDeodexed.zip from thread posted.
1a. Flash stock Odin3 rom. (For the Captivate).
1b. Root
2. Download ROM Manager from Market.
3. FlashClockworkRecovery for Captivate in ROM Manager.
4. Transfer the VibrantDeodexed.zip to /sdcard/ root.
MAKE SURE YOUR ext3 PARTITIONED SDCARD IS INSERTED
5. Reboot to Recovery (in ROM Manager)
6. Install zip from sdcard>choose zip>VibrantDeodexed.zip
7. After it finishes, reboot and be patient. The initial startup takes some time...
Added Fortune090 instructions on how to get this on our captivates. KUDOS to him for testing it out for us
Please note this is still very EARLY and major problems could happen if you do this wrong.
We're not responsible. This is beta
UPDATE 4: I updated the tutorial to a more extensive one, but there is another thread
http://forum.xda-developers.com/showthread.php?t=747397
that is more promising, no gps problem. Waiting for an update version for easier install
The Captivate and Vibrant function completely differently as far as those speed fixes go.
Read this:
http://forum.xda-developers.com/showthread.php?t=740747
I was hitting around 1800 in Quadrant, but the fix wasn't showing any real-world speed increases, and had some bad issues regarding the mic and voice calls, along with wake up lag.
I'm not saying this won't work, but I'm assuming it won't work well or function the same way...
EDIT: Guess I can try it though, seeing as no one else has. Glad my phone's finally communicating with Odin properly so I don't have to worry about the brick I did before... I'll update with any issues.
UPDATE1: Rebooted into recovery and tried to reinstall packages to install the update, and it failed. Trying another one of the methods described to see if they'll work.
UPDATE2: Got it installed (I think), but it seemed to go way too fast and kept going between recovery and rommanager. Phone's loaded and it's running Quadrant now to see if there's any change.... Didn't think so. Still getting in the 900's. Time to continue trying... haha. I originally used Clockwork for Captivate, so that could have been the problem trying Vibrant to see if that'll make a difference...
thanks for the try, I guess we'll just have to wait until something more substantial gets worked up for our side
nammyczc said:
thanks for the try, I guess we'll just have to wait until something more substantial gets worked up for our side
Click to expand...
Click to collapse
I'm guessing that you'd have to flash the Vibrant ROM first, and I've known that's caused issues for Captivate users. I'm still trying with the Captivate stock Odin ROM though... Will definitely post if I have any success...
EDIT: I actually think I found my mistake... hold on...
EDIT2: Yes... definitely was a dumb mistake. It's copying the files now. Waiting for it to boot. Was told it takes awhile for the initial boot...
UPDATE: Ok, everything booted up fine, and I can tell this is the Vibrant ROM. The speed fix wasn't applied though. Might be because my external is partitioned with ext4. Could that be the problem? I didn't see any script load that didn't before...
UPDATE2: Reformatted my external to ext3 and got results!!! Quadrant got to 1446! Time to check some real world applications now. (phone call, bluetooth, I know wi-fi works, etc) I'll update with news.
Keep us updated. I don't know if the ROM includes the radio firmware, so make sure to have the stock captivate radio.
I'd love to see a speedtest.net to see if HSUPA works correctly!
Ok wow. I'm impressed. I'm seeing actual speed increases and so far everything is working perfect. No wake up lag, no static in phone calls, Quadrant scores are way up, plus you get some of the advantages of the Vibrant rom without having to flash it. (ie. OPTION to allow non-market apps, unlocked Market...)
So far it's a thumbs up all the way!
Tutorial:
1. Flash stock Odin rom (For the Captivate).
2. Download ROM Manager from Market.
3. Install the Captivate Clockwork for Captivate
4. Transfer the VibrantUpdate.zip to /sdcard/ root.
MAKE SURE YOUR ext3 PARTITIONED CARD IS INSERTED
5. Reboot to Recovery (in RM)
6. Install zip from sdcard>choose zip>VibrantUpdate.zip
7. After it finishes, reboot and be patient. The initial startup takes some time...
8. ENJOY!
Currently working on getting rid of the T-Mobile startups and shutdowns, but that takes no time at all. Thanks for this!!!
EDIT: Problem. GPS no longer functions at all from what I'm seeing. When using my location in Maps, the application freezes... Going to check the *#*#1472365#*#* settings to see if anything there's causing the problem...
madjsp said:
I'd love to see a speedtest.net to see if HSUPA works correctly!
Click to expand...
Click to collapse
Did a speed test...
1898 dl
341 ul
Is that HSUPA ratings or standard? I'm not sure...
Sorry for the triple post, but another thing I noticed... Titanium Backup is not recognizing all of the T-Mo bloatware or ANY of the installed applications... Anyone have any idea why?
Also, Swype FC's after about 3 seconds, but I'm assuming a reinstall will solve the problem... Haven't checked quite yet. Still testing a bunch of things.
EDIT: TB problem solved. Go to Problems? from the main menu, Yes do it. Everything showed up after it updated BusyBox.
Still trying to figure out the GPS problem...
Fortune090 said:
Sorry for the triple post, but another thing I noticed... Titanium Backup is not recognizing all of the T-Mo bloatware or ANY of the installed applications... Anyone have any idea why?
Also, Swype FC's after about 3 seconds, but I'm assuming a reinstall will solve the problem... Haven't checked quite yet. Still testing a bunch of things.
Click to expand...
Click to collapse
I believe you have to click on "problems?" in T.B , its the middle button on the main screen i believe it say problems or in the menu
mykenyc said:
I believe you have to click on "problems?" in T.B , its the middle button on the main screen i believe it say problems or in the menu
Click to expand...
Click to collapse
Yeah, got it.
GPS, GPS, GPS...
Changed the settings in the 1472365 menu, and nothing worked. Anything that involves GPS crashes the second you tell it to use it. Phone doesn't freeze though.
QUICK: Can someone post the STOCK shutdown files? Sound: /system/media/audio/ui/shutdown.ogg Video (folder of .pngs): /system/media/shutdown
Would be greatly appreciated. Want to get rid of the T-mo branding the update applied...
WOW, I'm amazed that it works, thats great to here there have been little problems except GPS function. It could be the drivers for vibrant are different for captivate? I'm not really sure I dont know much software but that seems like the most basic explanation I can think of.
EDIT: Did you try deleting the GPS data and starting over from scratch? or gps test from the market? its possible that GPS just needs to reset itself? or something...
nammyczc said:
WOW, I'm amazed that it works, thats great to here there have been little problems except GPS function. It could be the drivers for vibrant are different for captivate? I'm not really sure I dont know much software but that seems like the most basic explanation I can think of.
EDIT: Did you try deleting the GPS data and starting over from scratch? or gps test from the market? its possible that GPS just needs to reset itself? or something...
Click to expand...
Click to collapse
Hmmm... ill try that. Thanks! I'll update with what happens.
UPDATE: Nothing... froze again and GPS Test crashes at startup...
Sent from my Captivate
Thanks for your work, looking forward to what comes from this
sidenote I would upload the sound for you but not sure where its located through astrofile...
EDIT2: http://www.mediafire.com/?tcyzaykkkfphxtg that rar is shutdown picture file and sound
Hm, could be possible we need to get the gps stuff from the captivate kernal and not the vibrants?
EDIT: so I emailed the OP from the vibrant one, for the original mod, seeing if he can help us out with ext4 problem and the GPS problem as well. Hope we can get this fully up and running
nammyczc said:
Hm, could be possible we need to get the gps stuff from the captivate kernal and not the vibrants?
EDIT: so I emailed the OP from the vibrant one, for the original mod, seeing if he can help us out with ext4 problem and the GPS problem as well. Hope we can get this fully up and running
Click to expand...
Click to collapse
Alright sweet. Hopefully we see this completely take off. Not using the GPS at all, I'm seriously enjoying it, but I know it's a problem for everyone else.
Sent from my Captivate.
question for reverting back to stock is the same method in the forums? or will it be different
Can you use ROM manager's backups to undo the ROM flash? I want to make sure that I can go back to my stock AT&T ROM after I test out this vibrant ROM.
thats pretty sweet.
just gotta get the gps up and going now.
I'm not sure... When I flash I use Odin.
Another minor bug I've noticed is that with texts, the notification doesn't go away until you clear all notifications. Not TOO big a deal, but it didn't happen with my stock firmware. Might be a Vibrant thing... idk...

[Q] Phone stopped working and won't start again

Hi, I have a g1 that has suddenly stopped working - when I start it I see the t-mobile screen and then it switches to the android screen and just stays like that and doesnt start.
It stalled while making a call and I was not able to restart it.
I have tried wiping everything from recovery console (http://forum.xda-developers.com/showthread.php?t=566669) and re-flashing my phone with my old firmware (http://forum.xda-developers.com/showthread.php?t=811620)
I don't know what's next here - can anyone please help?
some more background:
I had the phone for two years here in the US and have traveled out side of the country with it for several trips with no problems whatsoever, however, this phone I have given to my niece who doesnt live in the US.
The reason i'm saying this is that maybe the cause is a radio problem of some sort...
Let me know if you think of something coz I really don't know what do to next
Thanks,
e.
First of all, wrong section.. (Please post in Q&A)
If you had poked around and used the search feature, i'm pretty sure you can find what you are looking for
but anyhow, you need to flash another rom (via recovery) assuming you have already rooted because you somehow corrupted the system partition.
Thanks for the reply, I tried using cyanogen's mod but it didnt get me anywhere, I will try different mods but could this be a radio issue? is there a way to check that?
p.s. I did a thorough search of the forums and that's how i did all the things b4 posting but then I got stuck...
Hi, sorry I posted in the wrong section, just noticed what you mean.
Can any of the admins move this thread to q&a (or can I do it myself somehow)?
Data?
eladkatz said:
Thanks for the reply, I tried using cyanogen's mod but it didnt get me anywhere, I will try different mods but could this be a radio issue? is there a way to check that?
Click to expand...
Click to collapse
My friends phone is doing something extremely similar. He gave it to me to play with to make sure he wasn't mad, and it was actually the phone having issues.
Upon playing with it for a few hours problems started to occur. It would randomly shut off, then not want to reboot unless left sitting. It would get after the ROM screen and then shut off. I noticed that that a quick was to crash it was to start browsing the Internet over Wi-Fi. After a few pages loading and moving around the pages as they loaded the poor phone would just turn off.
Since he is using another phone in the mean time, I got his G1 without a SIM card. I was playing games on it, poking around in applications and more and the phone wouldn't turn off. I wasn't till I enabled Wi-Fi that problems started happening. I'm not sure if the Wi-Fi driver is part of the baseband unit or not but it seems that the more data the phone uses (3G or Wi-Fi) heightens its chance of turning off.
To get the phone to boot again I either have to take the battery our for a few minutes or leave it off for a while. Upon which time it will book as if nothing happens.
I also noted that every time it boots it shows an exception error related to "gapps" and you have to click force quit. His phone is running CyanogenMod 4.2. Also the Home key doesn't function, but this is software related because it can turn the screen on.
Scott

HOX on MIUI 2.8.24 v4 [JB], lots of errors

Hello,
First off, I know its a super buggy build, but some of the problem I've encountered aren't even reported so I feel like I'm the only one having them. As well, I would have posted on the actual topic, but I don't yet have 10 posts yet, so it won't let me.
Anyway, first problem.
I can't use/ setup voicemail! I don't really care about visual voicemail, but I literally can't even access my own voicemail. Dialing my own number just gives me a busy tone, what gives?
Secondly, on that matter, every time I make a phone call from my phone, the screen goes black the second the phone screen pops up. I thought it was like a proximity sensor or something, but even with the phone on a table, I can't get it to come out of the "black mode" while on a call. If I press the power button, the screen will flash on briefly, but not long enough to do anything with it. As such I can't hang out phone calls, so I have to force reboot after every phone call.
And finally, on the matter of the phone, there are times where people call me, I'll answer (get the same black thing) but I can't hear them at all, and they can't hear me at all, but we are connected, and since I can't hang up, and on a black screen, I am helpless.
Another problem... I connected my phone to my comp today to try and grab a new ROM, thought I'd mount the SD card, but when I plugged it in, there was literally no option to mount anything. I went through all my settings, developer stuff, nothing fixed it.
As well, since I couldn't connect to my computer, I couldn't run "adb logcat" to maybe see what was going on with the phone and such. So I used a mobile terminal app I use occasionally to run "adb logcat" locally on the device. Well when I first run "adb devices" my own phone doesn't even pop up... Yes, developer debugging is enabled, and yes, the mobile terminal app had complete root access. How do you explain this? A friend of mine suggested reinstalling the rom wiping the dalvic cache, which I did, but all the problems I've been having still persist.
It makes it extremely difficult to use my phone day to day with these issues, and since I can't do a logcat, I can't really report the problems accurately, even though I seem to be the only one having them. Don't get me wrong, I love MIUI and all the work the MIUI.us team does porting, but I just don't think I should be having so many problems.
Thanks for the help guys.
Did you do a full wipe before flashing miui? I haven't updated to v4 but voicemail/phone calls work fine for me on v3...maybe you should try flashing that instead? Can't help you with the adb stuff, sorry. I did have trouble getting my phone connect to my windows 7 laptop though but adb worked fine on vista
joorie said:
Did you do a full wipe before flashing miui? I haven't updated to v4 but voicemail/phone calls work fine for me on v3...maybe you should try flashing that instead? Can't help you with the adb stuff, sorry. I did have trouble getting my phone connect to my windows 7 laptop though but adb worked fine on vista
Click to expand...
Click to collapse
Yep, I did a full wipe many times actually. Could it be that I used a backup from an order version of MIUI (2.4.x) inside that backup/restore program and it's corrupting something? At least in regards to phonecalls and voicemail...
ItWasLuck3 said:
Yep, I did a full wipe many times actually. Could it be that I used a backup from an order version of MIUI (2.4.x) inside that backup/restore program and it's corrupting something? At least in regards to phonecalls and voicemail...
Click to expand...
Click to collapse
Try testing voicemail and calls before restoring?? I restored data from some games using MyBackUp Root or something and my phone has been working fine >_< If all else fails, I can upload the 2.8.24_v3 rom for you! I think blind is gonna have a new build up today though so up to you. Sorry I haven't been much help :\
joorie said:
Try testing voicemail and calls before restoring?? I restored data from some games using MyBackUp Root or something and my phone has been working fine >_< If all else fails, I can upload the 2.8.24_v3 rom for you! I think blind is gonna have a new build up today though so up to you. Sorry I haven't been much help :\
Click to expand...
Click to collapse
I'll give it a try next time I flash. I do appreciate the offer for the v3 rom, but maybe I'll just wait for blind to get the new one up and hope I have better luck. I did a little more research on the adb thing on JB roms, and apparently there's some other driver needed or whatnot, so I'd assume that the terminal app I'm using on my actual HOX doesn't have said driver. However, that doesn't explain why I couldn't mount my SD on my computer. Like I said, maybe this next update will solve everything lol.

[Q] Über-crash = reformat? What to do? thx

Hey gang -
Yesterday at home I pulled my phone out of my pocket and it was at the "touch the Android to begin" (!) screen. But it was still connected to my WiFi... And I was confused.
Rather than do that, I reset the phone, wiped Davlik cache and Fixed Permissions (took a long time!), then rebooted.
That sort of worked, but a LOT of my apps are crashing on start, and others are missing altogether. Even when I re-download them and re-install them, they don't work.
What's the way-ahead here? Am I stuck doing a factory reset? Or even formatting the SD card?
Thanks in advance.
When things get that fouled up, a clean install over a freshly formatted microSD is probably the best thing to do. You might be able to get away with restoring from a "nandroid" backup from before things started going bad, but "Your mileage may vary."
jeffsf said:
When things get that fouled up, a clean install over a freshly formatted microSD is probably the best thing to do. You might be able to get away with restoring from a "nandroid" backup from before things started going bad, but "Your mileage may vary."
Click to expand...
Click to collapse
Okay, thanks!
Anything else on the SD card I should back up besides DCIM / Media-> Ringtones/MP3s / "ui" / TitaniumBackup?
(Got about an hour while this stuff goes off to my HD...)
Hoo! Thought I effed myself for a sec - from CWM I was wiping all partitions... including /sdcard.
Then I realized... $#¡+... my ROM is on there!
Fortunately CWM has the "mount USB storage" option.
*whew!*
I was going to add format the sdcard from the phone. But you did that. Typically when what happened to you would happen to me it would be from some app updating and for whatever reason got corrupted during install and fouled the phone up. If you use TiB I highly suggest setting a automated task to back up your TiB backups to drop box, google drive or box.net. Then in these situations you have a recent TiB to fall back on.
JaimeZX said:
Hey gang -
Yesterday at home I pulled my phone out of my pocket and it was at the "touch the Android to begin" (!) screen. But it was still connected to my WiFi... And I was confused.[...]...a LOT of my apps are crashing on start, and others are missing altogether. Even when I re-download them and re-install them, they don't work.
Click to expand...
Click to collapse
Hi JaimeZX,
I am curious if you have recently rooted, flashed to stock, or installed the VB or Basic w/a twist kernel? I am running the exact same setup as you list (minus the modem) and this *exact* same scenario happened to me on the exact same day. March 12th, at about 10pm.
Detail as much information as you can, I've had many problems since flashing back to stock, formatting the SD, wiping everything multiple times, and re-installing Valhalla Black, Basic w/a Twist and all fresh apps d/l'd from the market. I'm on multiple attempts to stabilize the device and have questioned whether or not there is some issue with either the Rom or the Kernel. Perhaps there is an issue with the stock packages, or the USB driver ghosts (I've deleted all USB assigns at all ports and reinstalled for device detection in Heimdall). Hopefully we can get a good list of information to help us fix an issue that is apparently quite catastrophic (in that /data seems to corrupt) and save others from a future headache.
I have searched the dev threads to no avail, and as a general rule it seems that if problems are brought up they are usually met with "try flashing back to stock," "gremlins," "no one else is having problem 'X'," etc. even in cases of users with multiple complaints of the same issue. Both the DSP Sound force close upon EQ preset select and the issue that some had with the Messages, Phone Dialer, Search, Call Logs closing to homescreen are issues that I've seen this with. I believe this is a real issue, and I need to get it fixed without wasting time on messaging replies to anyone advising "try this," "Try that," etc.
My hope is that between the two of us we can address any of the common responses from developers before taking the issue to them and reporting it. I personally cannot today get my phone to boot without freezing (after boot cycle completes - not bootlooping or freezing during the bootleader seq) and am currently attempting to get into d'l mode without much luck.
When this happened to me on Tuesday night I was able to reboot to recovery, reflash the final-fixed.zip first without wiping data (which failed-/data is corrupted somehow here) and then *with* wipe/data and it booted, ran fine, so I then re-flashed BasicWithaTwist Kernel and was fine until late last night again.
I had been using the phone for some fairly constant web searching and the screen went black, appeared to soft reboot, and then froze. I pulled the battery, waited a few mins, reinstalled battery, once again, Freeze after boot.
No indication that an app crashes, phone just completely freezes, remains screen on, capkeys lit, power button does not respond, nor do softkeys or touchscreen. Makes it though the scan device and scan SD processes *sometimes* and other times freezes before it completes them.
I pulled the both the SD and the SIM and booted up, same issue, though it makes it through the scan device processes everytime since it's not scanning 18gb of data on an SD. This tells me it is not SD or SIM related, and is most likely software related, either ROM or Kernel. I've also ruled out the possibility of an old app/data package by reformatting the SD (long format - wipe all containers to "o,") let Android rebuild menu structure on SD, redownloaded a short list of commonly used apps and installed fresh - *NO* TiBackup apps were restored and the actual backup folder was not replaced to the SD after flashing.
I've tried both the Odin (Fb KJ6 back to stock) and the one click (lumin's tutorial) back to stock. Checked the download of Final-Fixed, MD5 checksum is correct. Cannot find MD5 on the sms-T959V-KJ6-antsvx.v1.1.3.zip file. Doesn't seem to be listed on Anton's github site, perhaps I don't know how to find it there. That is the only puzzle piece I haven't double checked.
All for now, looking forward to yours or anyone's replies or suggestions for anything I may be overlooking. Thanks.
0
---------- Post added at 11:19 AM ---------- Previous post was at 11:12 AM ----------
devlinandersen said:
Hi JaimeZX,
... I've had many problems since flashing back to stock, formatting the SD, wiping everything multiple times, and re-installing Valhalla Black, Basic w/a Twist and all fresh apps d/l'd from the market. I'm on multiple attempts to stabilize the device and have questioned whether or not there is some issue with either the Rom or the Kernel....
0
Click to expand...
Click to collapse
I should add that I have been on Valhalla Black Edition since it was in beta and have been quite happy with it. I only did a back to stock flash to try to (one more time) see if I could get a cooperative DSP sound manager. No such luck, and now a few headaches, and this issue on Tuesday coupled with yours in the exact same timeframe...I'm just thinking there is a problem somewhere in the chain of attack and hope to find it with the help of others.
Also, phone freezes after boot, needless to say, I'm not able to run a logcat.
devlinandersen said:
No indication that an app crashes
[...]
Also, phone freezes after boot, needless to say, I'm not able to run a logcat.
Click to expand...
Click to collapse
Try running logcat > /sdcard/some_file and cat /proc/kmsg > /sdcard/some_other_file so you have a capture of both the Android logs as well as the kernel logs. If you're not comfortable with command-line work, aLogrec should be able to at least help with the Android logs.
Given the number of people successfully running stock and custom ROMs on this device with stability, it either is going to be a hardware problem with your phone, corruption of a file system, or some app or combination of apps you are running, not a "dev" issue. Without logs, it is going to be nearly impossible to differentiate between the causes.
jeffsf said:
Try running logcat > /sdcard/some_file and cat /proc/kmsg > /sdcard/some_other_file so you have a capture of both the Android logs as well as the kernel logs. If you're not comfortable with command-line work, aLogrec should be able to at least help with the Android logs.
Click to expand...
Click to collapse
I will try in a bit, collecting files for another fresh install, different ROM.
jeffsf said:
Given the number of people successfully running stock and custom ROMs on this device with stability, it either is going to be a hardware problem with your phone, corruption of a file system, or some app or combination of apps you are running, not a "dev" issue. Without logs, it is going to be nearly impossible to differentiate between the causes.
Click to expand...
Click to collapse
This is false logic and is just what I was trying to avoid. I will attempt to explain to hopefully help build a stronger environment that is conducive to problem solving. It still very well could be a dev issue if say, a certain ROM or Kernel begins to wrestle with an app that has recently updated. Is it the apps or the rom's fault? Maybe it is a seldom used feature of an app that just missed all the users testing until now, it's well within the realm of possibilities and would just like to see helpful comments (such as the first portion directly above) to help solve issues. Truth is, I don't know *what* is wrong and neither do you, so a focus on constructive commentary would just help everyone out.
Logs or it didn't happen.
Update...
After a factory reset/data wipe, wipe cache, wipe dalvik cache I had to let the battery charge for a bit. Came back and decided to just try to boot phone, still freezes after boot sequence. I decide that I will flash a different kernel and a different ROM in order to see if I can make a difference. Before flashing Blastoff v2.5 Kernel I decided to factory wipe/data wipe, wipe cache and dalvik again...I am not sure if this is news, but when doing the Dalvik cache wipe in CWM it returned no result, perhaps because I had previously performed and is empty, but I thought it strange that there was *no* communication that it was already empty/wiped, etc.
Installed Blastoff v2.5 and was able to boot without freezing. Something else was damaged with the Rom as well, would not load home screen, only had pulldown menu. Rebooted to Recovery and flashed Unnamed RC-2.zip and have been charging the battery, talking on the phone and reinstalling apps from market.
Same error happened twice to me and once with Jaime. Both of us on VB and Basic+Twist. After installing new kernel i'd point towards kernel. Also uninstalled DSP and installed voodoo sound on VB, but had that on previous version as well. If I had to start somewhere, I'd start right around there.
Hope this helps, will provide logs from SD backup I made before reflash of new kernel/rom. Gotta run. Adios...
-devil.
I had to get my phone going today, it appears to be working without freezing, though on this new app the phone dialer/phone caller force closes on outgoing calls (I am only mentioning here, I will visit the Q&A for the ROM if I need assistance). Unfortunately I was unable to replicate the problem without flashing back to my previous nandroid. I have it saved and given some time I will do my due diligence and get a logcat **if** Jaime doesn't do it before me...because I kinda have a feeling that something was updated in the market on Tuesday evening that is now fighting with the kernel somehow. But again...I didn't run a logcat so it's not even happening...yet...
...to be continued...
Devlin - sorry for the delayed reply.
I did notice that I'd had more and more apps FCing on me in the week leading up to the Über-crash. Unfortunately I don't have any more "background" to add than that.
I backed up everything I wanted on the SD card and then formatted that, plus /data, /system /everythingelsethatwasanoptioninCWM. Then did my installs.
FORTUNATELY (knock on wood) I have not had any recurrence of the major issue.

Issues with calls and various other things.

Hello! Here I am with my Q.
I got it last week, rooted w/o BL unlock, then a few days later I went to Moto to unlock the boot loader. all went well. (AHAHA, They worded the terms for the unlock as if EVERYTHING at ONCE will break. It seems to me that this has become reality.)
Then I had issues with GPS and Camera not working at all.
With each flash I got one or the other working, not usually both.
Now Both Camera and GPS are working wonderfully. Here's the kicker, I've found that calls are not working well.
I make calls, they go through but end shortly after they start with silence. when you attempt to end the call, it wont do it, or it will about 5 minutes after end has been pressed.
On receiving calls, often times it wont come through at all, if it does there's a chance that you wont get to pick it up. It will act like the caller has hung up. Missed call. Some times it will let it through, and a few seconds in and go to silence.
Here was my process.
1. Rooted with Motochopper. Played around in stock for a while then got fed up with it and all of it's bloat. Not to mention horrible batterylife.(Still has horrible battery life on CM, even when underclocked.)
2. Unlocked bootloader via Motorola.
2a flashed OpenRecovery, CM10.1 (Yes the CDMA version)and gapps.
3. Yay CM. Sadly, nothing works right. (Yes there were wipes.)
4. Was suggested to flash JB FXZ, did that.
5. Flashed TWRP and CM+Gapps. (No camera, but GPS worked.)
5a. Flashed 5/20 Build. Camera worked but no GPS.
5b. Flashed 5/26 build over 5/20 and both Cam and GPS work now.
The call issues were persistent throughout all of the builds I tried.
5/20 5/23 5/26
Sys info screenshot
lionspaws.net/android/ignoreme/Screenshot_2013-05-29-21-48-50.png
Please help me diagnose this.
I'm not looking for "It's you/your device/doin' it wrong/works for me" or "go back to stock"
I'm looking for help. I need a working device.
Here's some logs with a test call.
it failed about 2 sec in. Skype hung up due to dead line. Phone wont hang up.
Radio reset, data resync.
then I powered off the device after it 'hung up'(radio reset)(If I dont hit hang up, the call timer will continue count up)
lionspaws.net/android/ignoreme/logs.zip (zip,bzip2)
Halp!
Bump?
I've been having the same call issues, with every rom except stock.
Sounds like you tinkered alot.
I suggest you do a full reflash with rsd/ stock rom. Since u have unlocked bootloader I suggest you to install custom recovery like twrp or cwm. That will also root your device. After that retry flashing cm10.1 nightly and gapps exactly as described in their threads.
Everything else would be tinkering around broken builds. So start with fully clean device through rsd.
Also about the gps problem: it is suggested to get a gps lock on stock rom before installing aftermarket rom.
I'm having the same problem, I've RSD'd to stock and all that stuff too. I ALWAYS clean install. Yet I'm having this problem on most roms. I haven't tried any kernels yet, so maybe that would help things but I dunno. I'm gonna play around with that some time and figure it out.
xLoveHateLegend said:
I'm having the same problem, I've RSD'd to stock and all that stuff too. I ALWAYS clean install. Yet I'm having this problem on most roms. I haven't tried any kernels yet, so maybe that would help things but I dunno. I'm gonna play around with that some time and figure it out.
Click to expand...
Click to collapse
This is the first I have ever heard of this type of issue...
Logs please, with thorough detail on what happened. I can't recreate this, and 99% of others can't either (or just put up with a non-functional phone. Seems doubtful...)
Edit - as far as I know, the OP has fixed all of the issues they were having... maybe they can chime in with the process, but my kernel would have nothing to do with cell service.
Alright, here's a logcat... it's weird, I can only hear the first word they say and vice versa. Then the call gets quiet but stays connected. Then after clicking hang up, the call isn't really hung up. I have to go back to the dialer and click hang up again. Then, after a minute or so I'll hear the hang up tone and it'll finally hang up. I'm doing clean installs so I'm not sure what's going on here. Hopefully this will help resolve this issue, 'cus it's a huge problem for me :/
EDIT: Just flashed a stock rom and I'm not having this issue at all.
Sent from that one MoPho... Q
Anyone have a clue what's going on with my phone?

Categories

Resources