Related
it would just freeze randomly when left alone...and i wouldn't even know unless i push the standby key and it doesn't turn on or the time on the LCD is way wrong
worst is i cant get any calls while it's frozen and i can never recieve a txtmsg sent while it's frozen..even if i reboot the txtmsg will never be recieved
even worst is when it freezes while the lcd is on...it just sits there like that draining the battery
i cant figure out why..i report,as well as others, about this problem before but no one has any idea what's causing it
and no, there is no 3rd party programs running and yes this will happen on a clean cooked rom with no options checks off..i've tried everything...my only guess is that tmail.exe or the messaging system is causing it..but i cant be sure
does anyone have any ideas, i have to poke my phone 5-6 times a day when it freezes. is there any memory resident apps that can detect a frozen OS and force a soft reboot? and coders want to have ago at it?
What ROM/Radio/apps are you running? My Titan has never done that except when There were some reg entries I botched when I first got it.
No offense, but it is usually user error when things go awry, from adding bad oem's to the kitchen or messing with the registry entries.
A little more info is needed please.
Mine will freeze up if I leave the wifi switch on and then hit the power button to put it in standby. Or if I just let it time out and it goes into standby with the wifi switch on.
I upgraded to the VZW MR1 update and all is fixed!!
im running D.C.D 3.2.6 and radio 3.42.50
but this has been happening since before 3.2.X
no oems added, and like i said i would happen with a clean rom with no apps installed
i tried that to make sure it was a program i installed that was caussing it to freeze
i take it Windows Mobile doesnt have an event log or crash dump
Fr3nZy said:
im running D.C.D 3.2.6 and radio 3.42.50
but this has been happening since before 3.2.X
no oems added, and like i said i would happen with a clean rom with no apps installed
i tried that to make sure it was a program i installed that was caussing it to freeze
i take it Windows Mobile doesnt have an event log or crash dump
Click to expand...
Click to collapse
Try radio 3.42.40 Some ppl were having problems with 3.42.50, but I used it for a couple of months ok.
Well, honestly, this is far out of my range of advice. I have been running DCD ROM's since I got my phone, and re-flashing has cured my no wifi/no bluetooth/no whatever problems since I started. Delete the kitchen package, restart your computer, re-download, build ROM and flash again.
Its not the most convenient option, but it will tell you whether you have a hardware problem or not.
I have had many problems with the no2chem rom I am running now, but in comparison DCD's ROMs should be solid. I suggest you re-download the kitchen and build again. Start fresh, then report back.
1999TL said:
Try radio 3.42.40 Some ppl were having problems with 3.42.50, but I used it for a couple of months ok.
Click to expand...
Click to collapse
this happen with all radio's released since 3.40.02...i dont think it's the radio.
and i've tried recooking and reflashing with no success
wat it did try was this....i left the taskmanager running in process view and sorted by cpu usage..if i is a program i might catch it in action if the phone freezes with display on
and it did eventually...the program at the top wen it froze was tmail.exe @ 36% cpu useage...im not complete certain its the cause
and tmail.exe is a base OS file right? it's pocket outlook and i need it for TXTMSG
Do you have a lot of text messages saved? I have about 1500 saved... and if I keep more, freaky stuff happens... like bad restores with PIM and slow texting.
actually, i do about 4000
i'll archive them with PIMbackup and erase them
i'll report back
Fr3nZy said:
actually, i do about 4000
i'll archive them with PIMbackup and erase them
i'll report back
Click to expand...
Click to collapse
nope it didnt help...froze 4 times today
had exact same problem u did. did everything possible... nothing worked. turns out its a product defect that it crashes so brought it into telus store and they switched it for me.. since it was still under warranty if u have warranty i suggest u do the same... if not... im sorry mate this is not a software issue.
i had that defected phone for atleast a month.. and trust me when i say this.. i tried EVERYTHING. lol
actually its still under warrenty
i'll bear it and try and see if it is a software issue
i dont want to take it in for servicing if it's really not a hardware issue
the phone is pretty much new still
i might try flashing the official sprint rom and see if it fixes it
did you do a hardreset after each flash that you do. Cause if not you will have alot of footprint left over.
Only one app consistently locked my phone...
CorePlayer. I finally removed it after installing Kinoma Play (full edtion).
I had the Standby of Death SOD this is when the phone fails to come out of standby with a power button press. This issue only affects some people on some networks. I'm not sure if its a network problem or a software problem but as only a minority of people have it, I suspect its mainly a network problem there is a software solution.
The solution is to change the phone settings band option from auto 3G/2G to either 3G Only (WCDMA + UTMS 2100 in Europe) or 2G Only (GSM + AUTO) depending on your requirements.
Also read this thread http://forum.xda-developers.com/showthread.php?t=540943&highlight=standby&page=2where the resolution was to get a new SIM.
Obviously this only solves the problem when the crash is because of the sim and/or settings which impact the sim. To rule out a software cause its best to start with a hard reset.
mine actually frooze when i have it in my pocket only. i found out that if the power on button is held down a long time, it might freeze light that. thats what i learned since i have it. it might strange weird but this is how it freeze with me.
DCD 3.2.6 and radio 3.42.50.
Cabanon said:
mine actually frooze when i have it in my pocket only. i found out that if the power on button is held down a long time, it might freeze light that. thats what i learned since i have it. it might strange weird but this is how it freeze with me.
DCD 3.2.6 and radio 3.42.50.
Click to expand...
Click to collapse
It may be because you are going into a weak 3G area whilst its in your pocket (which causes the problem when the phone auto-switches bands) the solution is to try what I suggest and if not entirely satisfied then perhaps try to update the radio.
nlel said:
It may be because you are going into a weak 3G area whilst its in your pocket (which causes the problem when the phone auto-switches bands) the solution is to try what I suggest and if not entirely satisfied then perhaps try to update the radio.
Click to expand...
Click to collapse
well, maybe., but i dont use the 3g band at all, im not even using a data plan because i dont surf the web at all other than at home via wifi. if it freeze, i just reboot. im not that too worried about that as it happen really few times.
Cabanon said:
well, maybe., but i dont use the 3g band at all, im not even using a data plan because i dont surf the web at all other than at home via wifi. if it freeze, i just reboot. im not that too worried about that as it happen really few times.
Click to expand...
Click to collapse
Do you not gt a 3G signal in your area or have you disabled it on the phone, you always have some type of signal going to the phone whether or not you actually run data connections.
If you are not using 3G then your must be getting an Edge or GPRS connection that you can make phone calls with. Its still worth setting the band type to GSM + AUTO even if you don't get a 3G signal in your area.
hang up etc
I installed everything in main memory and nothing but storage on card and doped to 49% on cpu, until phone is used and the around 55% , I dont know if that might help you but it did for me.
I recently flashed CyanogenMod Nightly #64, because I was hoping to get a crack at a working Google Talk with video chat.
My operation (via RA2.3) followed:
- Nandoid Backup
- Titanium Backup
- Wipe Dalvik, Cache, Data.
- Install cm_supersonic_full-64.zip.
- Install gapps-gb-20110503-signed.zip.
- Reboot
I was unable to test from PC to phone because the phone's Talk account was listed as 'Voice/video chat is not yet available'. I was able to establish a connection from phone to PC, but ran into a few problems...
#1 - The audio connection included a high-pitched screeching noise, like a horribly oversensitive microphone.
#2 - The phone received video from the PC, but the PC did not receive video from the phone.
#3 - Changing the camera-in-use from front to back caused a Force Close.
I know that as a nightly this build is experimental/unstable, so I'm not expecting any kind of "here's how to fix it" answers (although if there are any out there, I wouldn't turn them down). I'm just curious if anyone else is seeing the same problems I am (particularly the mic screeching -- I hope that isn't a hardware problem).
Thanks!
1. Was the phone and the PC next to another, I accidently tried to test it with them next to another and it made that noise. Moved to another room and it went away.
2. I didn't have that issue. Worked fine.
3. That is a known issue with many people (if not everyone).
BrandonEnr7 said:
1. Was the phone and the PC next to another, I accidently tried to test it with them next to another and it made that noise. Moved to another room and it went away.
2. I didn't have that issue. Worked fine.
3. That is a known issue with many people (if not everyone).
Click to expand...
Click to collapse
1. I tried with three PCs, one was in my apartment, one was in another part of the same city, and one was in a different time zone. (I called friends with the last two, who both remarked on the screeching noise).
Could you tell me what you did to set up your Talk? Is there a step I missed?
csharpdflat said:
- Install gapps-gb-20110503-signed.zip.
#1 - The audio connection included a high-pitched screeching noise, like a horribly oversensitive microphone.
#2 - The phone received video from the PC, but the PC did not receive video from the phone.
#3 - Changing the camera-in-use from front to back caused a Force Close.
Click to expand...
Click to collapse
I couldn't get GTalk video calls to work until I used CM7-64 with gapps-20110504. Everything except the back cam is working. I tested it by making a call to my PC. With the phone right next to the PC there was no issue with audio.
I had tried a few other methods mentioned in other threads to get GTalk video to work using CM7 ROMs with different versions of gapps, but the ROM and gapps I mentioned above is the only combination that worked for me.
bbrodus said:
I couldn't get GTalk video calls to work until I used CM7-64 with gapps-20110504. Everything except the back cam is working. I tested it by making a call to my PC. With the phone right next to the PC there was no issue with audio.
I had tried a few other methods mentioned in other threads to get GTalk video to work using CM7 ROMs with different versions of gapps, but the ROM and gapps I mentioned above is the only combination that worked for me.
Click to expand...
Click to collapse
Is gapps-20110504 a savagedzen specific gapps package? If so, I assume I'd need to flash that kernel to use it?
csharpdflat said:
Is gapps-20110504 a savagedzen specific gapps package? If so, I assume I'd need to flash that kernel to use it?
Click to expand...
Click to collapse
Lol a kernel has nothing to do with installing apps.
Sent from my PC36100 using XDA App
I really wish people would just search before flashing away...
Please, look on here, I've explained the problem at least twice, another five times on Twitter, and again on the CyanogenMod forums.
At this rate, I may just create a FAQ/blog about GApps or something.
Not really sure why its working.
I have had no issues with the nightlies and I'm currently on #65.
Here is my post from the [APP] Google Talk w/Video & Voice for 2.3.3 roms CONFIRMED WORKING!!
I hope that this helps.
Just wanted to come back and say that I did finally get everything working with the Google Talk video chat.
Running N66 + Lithid's GApps recommended by drmacinyasha: http://goo-inside.me/google-apps/ ("So what's up with the 2.3.4 GApps?").
Thanks everyone!
A new problem has started for me and and a Google search has shown some other people have also mentioned in but no solutions have come up.
Since iv started using any Android 2. 3. 7 roms around 1once a day to once a couple of days answering a call causes phone app to freeze and the phone speaker makes a constant buzz sound that eventually stops. After the phone signal and 3g returns all is well but trying to make a call result in a full phone freeze wich needs a battery pull. Best thing I do now after this crash is reboot normally.
Also good thing is the call is not answered as far as the carrier is concerned so I can still follow up on the call with voicemail.
I'm considering I have to go back to an older nexushd2 Rom or some sense Rom wich usually has Android 2. 3. 5
Anyone know a way to fix it? Maybe flash an Android 2. 3. 6 apk or a modded libaudio ?
I had that happening to my old phone.... freezing, buzzing, battery pull.
It started happening after I overclocked the phone to 1.5ghz . And then just kept happening even when i stopped overclocking. The phone would be hot on the bottom. And sometimes wouldnt boot till it cooled off. All i can say is hopefully you have insurance bc if its anything like with mine it'll be happening more and more often with time. After 3 months of it, it was happening a couple times a day , till i got a replacement.
Visentinel said:
A new problem has started for me and and a Google search has shown some other people have also mentioned in but no solutions have come up.
Since iv started using any Android 2. 3. 7 roms around 1once a day to once a couple of days answering a call causes phone app to freeze and the phone speaker makes a constant buzz sound that eventually stops. After the phone signal and 3g returns all is well but trying to make a call result in a full phone freeze wich needs a battery pull. Best thing I do now after this crash is reboot normally.
Also good thing is the call is not answered as far as the carrier is concerned so I can still follow up on the call with voicemail.
I'm considering I have to go back to an older nexushd2 Rom or some sense Rom wich usually has Android 2. 3. 5
Anyone know a way to fix it? Maybe flash an Android 2. 3. 6 apk or a modded libaudio ?
Click to expand...
Click to collapse
This is related to the No Sound bug alright. What other apps do you have - SIP/ Viber/ any other VoIP? And do you use BT? There were a few post in the No Sound thread and Tytung's kernel thread few days back about what libaudio.so works fine for what kind of a usage.
Android 2.3.7 is just a coincidence, me thinks
ph03n!x said:
This is related to the No Sound bug alright. What other apps do you have - SIP/ Viber/ any other VoIP? And do you use BT? There were a few post in the No Sound thread and Tytung's kernel thread few days back about what libaudio.so works fine for what kind of a usage.
Android 2.3.7 is just a coincidence, me thinks
Click to expand...
Click to collapse
None of the above and I don't use Bluetooth.
Guess it ain't a coincidence. I wouldn't of posted if I thought it was part of the no sound bug.
Sent from my Nexus One using Tapatalk
I had a similar issue some time ago: for me the problem was the cpu/governor settings and i fix it with an appropriate SetCPU profile. Using another rom though.
Try to set an "in call" profile as the phone won'to go under 400 Mhz (roughly) and see if it happen again.
mi too
i using miu rom, HD2 NDT GINGER and recovery 3.0.2.4 with this i don have this problem. with any sense rom I have that problem
Sorry my bad english
Re: [ROM][NIGHTLY] CyanogenMod 9 for Motorola Milestone 2 (Android 4.0.4)
This is kinda sad, that I can't reply directly to the ROM thread, but here it is, I just hope someone will tell them, or see it to adress these problems correctly:
There's a couple of problems with this ROM. First of all it loses the data connection after sometime of inactivity. Browser won't load anything, asking to check the connection. Going to settings -> data usage -> mobile data switch -> turning it off and then on solves the problem, but it's kind of annoying to do that five to six times a day.
Secondly - just after flashing this ROM keyboard backlight was working fine. But after installing the gapps it stopped. Just won't work. ((
Third(ly))) - Apollo app crashes at random when trying to listen to podcast/music from sdcard. Also annoying. Disabling data connection seem to solve the issue tho as it stopped crashing yesterday.
Fourth - some sensor shanannigans when you're trying to use chrome (games are fine with it) while charging. Random zoom-ins and stuff.
Fifth - and most terrifying. Sometimes it loops, as if I was repeatedly taping the screen at the center or somewhere near it. Can't even reboot when it happens. Power button to lockscreen seem to solve the issue.
Otherwise this ROM is smooth and good and I like it a lot. Using it for a few months now.
Big thanks.
Sent from my MotoA953 using xda app-developers app
sintu_cf said:
This is kinda sad, that I can't reply directly to the ROM thread, but here it is, I just hope someone will tell them, or see it to adress these problems correctly:
There's a couple of problems with this ROM. First of all it loses the data connection after sometime of inactivity. Browser won't load anything, asking to check the connection. Going to settings -> data usage -> mobile data switch -> turning it off and then on solves the problem, but it's kind of annoying to do that five to six times a day.
Secondly - just after flashing this ROM keyboard backlight was working fine. But after installing the gapps it stopped. Just won't work. ((
Third(ly))) - Apollo app crashes at random when trying to listen to podcast/music from sdcard. Also annoying. Disabling data connection seem to solve the issue tho as it stopped crashing yesterday.
Fourth - some sensor shanannigans when you're trying to use chrome (games are fine with it) while charging. Random zoom-ins and stuff.
Fifth - and most terrifying. Sometimes it loops, as if I was repeatedly taping the screen at the center or somewhere near it. Can't even reboot when it happens. Power button to lockscreen seem to solve the issue.
Otherwise this ROM is smooth and good and I like it a lot. Using it for a few months now.
Big thanks.
Sent from my MotoA953 using xda app-developers app
Click to expand...
Click to collapse
The Data connexion loss is a recuring bug for some, mostly people who have a Carrier that use roaming (ie : use another's carrier's network). No known fix for know, but some people seems to have it working "better" by disabling data roaming/national data roaming in options, but it's not for everyone, since some carriers require that to be toggled for data to work.
For the Backlight on the keyboard, be sure to check if the automatic gestion of automatic backlight is activated, it's required for it to work. There is too a "fix" for the problem in the last 5/6 pages of the main topic from memory, but don't recall it exactly, so you'll have to dig to try it.
No idea about Apollo, but it seems to have quite some quirks, and most people use other players so not sure about it, maybe start by checking the Apollo dev's page and market comments to be sure it's not related to Apollo but to the ROM.
The "random sensor shennanigans" while charging is something that happens to a lot of people, i think it's a multi touch bug from the kernel, but not sure (ie : not really solvable by the dev, unless he finds a way to remake tezet's fix (i think it was tezet) or we all use CH kernel since it seems the bug isn't there in this kernel [ wtb a way to use custom kernels :/]).
Your last problem is a weird bug, probably linked to the ROM, but i must admit it'll be hard to pinpoint, since i don't have it but my brother do, while both phones are the exact same model, and flashed the same, in the same order, with the same sbf/rom versions and so on.
I guess you can try to make a full wipe/factory reset (only backuping data you REALLY need to keep like contacts/sms/call log and so on) and redo your phone config, because as far as i know, the only difference between my phone and my brother's is that i had to did that again after i screwed up a couple times, installing an app that was bricking the phone (took me a few wipes to identify it), it might be the reason why i don't have it and he does, or not.
Hi guys, I am having some issues with my Girlfriends S4 (i337 AT&T Version).
The issues I am having are below, but I want to know if you guys would recomend me upgrading it from 4.2.2 to some other ROM that may clear out these issues and what you would suggest me to upgrade it to?
I want something that is STABLE, fairly close to the stock S4 Build or even the Stock Android GUI and easy to upgrade too.
Or is the phone just screwed and I should look into replacing it? I have not upgraded the phone from 4.2.2 because as I understand it, doing that locks the bootloader and makes it a pain in the ass to root and upgrade.
Issues she has:
-When recording video, sometimes it wont record voice, sometimes it does. No idea why this is doing this.
-Sometimes video's refuse to play, then it starts working again.
-SD Card appears to disengage at times. Its Lexmar, maybe I need to get a Patriot like mine.
-The phone just intermittantly disengages from the Cell Network or Wi-Fi network. She sees it mostly when she uses Viber. It runs well, then it just up and loses its connection then starts working well again
-Has had a few issues where people dialing her just cant get to her, its as if the phone has been turned off, or she cant dial out on the network.
-In certain cases repowering it corrects the issues for a while so I tell her to repower the phone once or twice a week.
This is what her phone is running:
SAMSUNG-SGH-I337
4.2.2
I337UCUAMDB
JDQ39.I337UCUAMDB
If this is not the correct place to ask these questions, please direct me to a better place, but I have found this forum to be an amazing resource with knowledgable people and I am not sure where to go
Need more info... like:
1. Is the phone rooted?
2. Location the phone is used?
DID you try OTA update
Mithanx said:
Hi guys, I am having some issues with my Girlfriends S4 (i337 AT&T Version).
The issues I am having are below, but I want to know if you guys would recomend me upgrading it from 4.2.2 to some other ROM that may clear out these issues and what you would suggest me to upgrade it to?
I want something that is STABLE, fairly close to the stock S4 Build or even the Stock Android GUI and easy to upgrade too.
Or is the phone just screwed and I should look into replacing it? I have not upgraded the phone from 4.2.2 because as I understand it, doing that locks the bootloader and makes it a pain in the ass to root and upgrade.
Issues she has:
-When recording video, sometimes it wont record voice, sometimes it does. No idea why this is doing this.
-Sometimes video's refuse to play, then it starts working again.
-SD Card appears to disengage at times. Its Lexmar, maybe I need to get a Patriot like mine.
-The phone just intermittantly disengages from the Cell Network or Wi-Fi network. She sees it mostly when she uses Viber. It runs well, then it just up and loses its connection then starts working well again
-Has had a few issues where people dialing her just cant get to her, its as if the phone has been turned off, or she cant dial out on the network.
-In certain cases repowering it corrects the issues for a while so I tell her to repower the phone once or twice a week.
This is what her phone is running:
SAMSUNG-SGH-I337
4.2.2
I337UCUAMDB
JDQ39.I337UCUAMDB
If this is not the correct place to ask these questions, please direct me to a better place, but I have found this forum to be an amazing resource with knowledgable people and I am not sure where to go
Click to expand...
Click to collapse
First off don't let it do any updates, and if you are on MDL, it will be trying to.....get rooted real fast, and go from there....
Root the device
flash a recovery
then go rom hunting....
And for some reason you do not want to do all I have mentioned, do a factory reset and see if that fixes the issues.....if you factory reset, beware that it WILL wipe your internal sdcard...back it up first....
good luck!