Related
ever since updating to the cyanogen 4 series of roms i have been getting 3g issues. by this i mean that sometimes it doesnt want to connect to the internet from any program, like the market, google voice, or the browser. sometimes it does work, but sometimes i have to reboot the phone or just turn off 3G in order to browse the web. i am running haykuros spl with apps2sd with a 800mb ext4 partition. and im running the latest cyan mod.
can any one assist me in this?
what can i do to fix this?
do i need a new g1?
I dunno if wipe helps have you tried that? boot into recovery, wipe (alt+w)
if not, jacxrom is a good alternative to cyan, i guess...
but chances are your phone's hardware itself is fine, and you won't need a new one.
jcarrz1 said:
I dunno if wipe helps have you tried that? boot into recovery, wipe (alt+w)
if not, jacxrom is a good alternative to cyan, i guess...
but chances are your phone's hardware itself is fine, and you won't need a new one.
Click to expand...
Click to collapse
i just wiped coming from his previous rom. 4.04
ive never had this problem and i dont want to switch rom series
can any one help me?
this is really weird.
I had same problem.. so instead of doing an upgrade.. I did a complete wipe and installed the new stable CM fresh... since then I feel that I don't have this issue..
dilfatx said:
I had same problem.. so instead of doing an upgrade.. I did a complete wipe and installed the new stable CM fresh... since then I feel that I don't have this issue..
Click to expand...
Click to collapse
forreals?
because i had just wiped and i havent updated to anything since then..
has anyone else experienced this and how did u fix it?
ive had the same thing happening lately. i had it happen tonight with just my edge connection i had to reset the phone. I also just wiped and reformatted my sd card for a linux-swap partition before flashing this rom so i know that isnt the problem.
2.0t03speed said:
ive had the same thing happening lately. i had it happen tonight with just my edge connection i had to reset the phone. I also just wiped and reformatted my sd card for a linux-swap partition before flashing this rom so i know that isnt the problem.
Click to expand...
Click to collapse
so how did u fix it?
Try re-installing the radio.
I had to do a second wipe after installed to fix the 3g problem. Since then I haven't noticed any problems
bootleg16 said:
so how did u fix it?
Click to expand...
Click to collapse
just rebooted the phone and all was well.
I dunno if this is related, but Ive been having bluetooth issues since the latest few updates, bluetooth has never been perfect for me, but when I listen to mp3s over bluetooth it almost constantly stutters, like its dropping the BT connection, because the music seems to have been going on playing while I don't hear anything.
what is with all these questions in the wrong forum? where is Mikey when you need him?
READ THE STICKIES. POST IN THE Q&A FORUM.
Mod request to delete thread: fix for BT and 3G issues
1. power down the unit with the red key. Wait a minute. Power back up.
2. Try reinstalling the radio
3. Try reinstalling the ROM, and then reinstall the radio again
5. You shouldn't have to, but wipe, re-create (not just reformat) your ext# partition (you can back it up and refill it, but occaisionally stuff gets left behind) reinstall the ROM, wipe, install again, install the radio, full power cycle.
5. (Last) post your issue
This actually belongs in the ROM forum, but not until these basics have been tried.
Janis said:
1. power down the unit with the red key. Wait a minute. Power back up.
2. Try reinstalling the radio
3. Try reinstalling the ROM, and then reinstall the radio again
5. You shouldn't have to, but wipe, re-create (not just reformat) your ext# partition (you can back it up and refill it, but occaisionally stuff gets left behind) reinstall the ROM, wipe, install again, install the radio, full power cycle.
5. (Last) post your issue
This actually belongs in the ROM forum, but not until these basics have been tried.
Click to expand...
Click to collapse
i tried this but still no cigar,
=[
I don't believe this to be a problem with a ROM or radio. I've had similar connection issues recently. i noticed it after flashing a Hero Theme to Cyan 3.9somethin. I thought the rom might have been the cause of the issue but a buddy of mine that i work with has a stock G1 and has similar connection issues. Also a customer came into the store who had a Samsung Highlight with similar problems, i figured it was a problem on Tmobile's End. It still hasn't fixed itself so i plan to give customer service a call in the morning and see if they have any resolutions or if its a recognized issue. I'll post back with what i get tomorrow.
MOD EDIT
Moved to Q&A forum
no signal..
As of late my phone was good... but now it says no service all day why.. an what can i do to fix... i was running cyanogen 4.0.4... i beive i hav the latest raido.. spl dont know... the wifi still works thou.. help please..
Hey guys,
I upgraded my G1/Dream from an older cyanogen version, to the newer one 4.2.15.1
and now for some reason my phone keeps restarting Any reason why ?
Can you please tell me how to fix it?
I've taken battery out & Also 'green+home+red' . Same keeps happening.
It restarts when it wants, can be 2 minutes, 10, 30.. but lately ever 1 minute or so..
What can I do?
Bump
bump
Anyone?? please
I'd recommend a full wipe and reinstall of your desired rom from scratch. Sounds like kernel panics to me.
my g1 was freezin up alot on cm4.15.1.... before it died and i had to get it replace....try unrootin and then root again and if it doesnt work it could be a hardware prob.
Tone-E said:
my g1 was freezin up alot on cm4.15.1.... before it died and i had to get it replace....try unrootin and then root again and if it doesnt work it could be a hardware prob.
Click to expand...
Click to collapse
Why would you completely unroot and reroot? That's just too much work.
Wipe, and reflash. Also, a few apps have a problem with custom ROMs, try disabling apps that run in the background one by one until you find that your phone no longer reboots.
However, if you didn't wipe, I highly recommend that as the person before me said.
Hi guys,
I have a problem with my Magic 32B and hope one of you guys could figure out where this all come from.
Since a couple of weeks my magic has become very unstable and I would say I have about 20 to 30 freezes or reboots a day. It suddenly started when I switched from a nightly froyo to another and since then regardless on the ROM I flash I always have the same behaviour (I'm currently on the CM6 RC1).
I tried the following:
- full wipe via AmonRa + format of SD (128 SWAP + 512 EXT + FAT) clean reinstall of a presumably stable rom --> failed keeps rebooting or freezing
- I did a fastboot erase system -w + flash of a clean ROM --> failed
The bizarre thing is it never crashes when the phone is USB plugged on my laptop, therefore I've never seen a logcat showing anything bad ...
Also I can't identify any pattern or scenario which would systematically frag my magic... Even when I install a fresh new ROM, it can work pretty well for as long as an hour but then start being screwed up.
I've spent quite some time on this forum desperately looking for someone experiencing the same troubles but so far unsuccessfully ...
Would you guys have any idea ?
cheers
ZeRoT
zerot said:
Hi guys,
I have a problem with my Magic 32B and hope one of you guys could figure out where this all come from.
Since a couple of weeks my magic has become very unstable and I would say I have about 20 to 30 freezes or reboots a day. It suddenly started when I switched from a nightly froyo to another and since then regardless on the ROM I flash I always have the same behaviour (I'm currently on the CM6 RC1).
I tried the following:
- full wipe via AmonRa + format of SD (128 SWAP + 512 EXT + FAT) clean reinstall of a presumably stable rom --> failed keeps rebooting or freezing
- I did a fastboot erase system -w + flash of a clean ROM --> failed
The bizarre thing is it never crashes when the phone is USB plugged on my laptop, therefore I've never seen a logcat showing anything bad ...
Also I can't identify any pattern or scenario which would systematically frag my magic... Even when I install a fresh new ROM, it can work pretty well for as long as an hour but then start being screwed up.
I've spent quite some time on this forum desperately looking for someone experiencing the same troubles but so far unsuccessfully ...
Would you guys have any idea ?
cheers
ZeRoT
Click to expand...
Click to collapse
Probably other people will say it, but wrong forum.
Also, what ROMs have you flashed after the nightly froyo? Nightly froyos are cautioned, which I'm sure you knew.
yep, I used a couple of FroYo SP French Connection nightlies and then switched to CM V6.0.0-RC1.
(sorry if it's the wrong forum, @admins, please feel free to move it to wherever make sense)
zerot said:
Hi guys,
I have a problem with my Magic 32B and hope one of you guys could figure out where this all come from.
Since a couple of weeks my magic has become very unstable and I would say I have about 20 to 30 freezes or reboots a day. It suddenly started when I switched from a nightly froyo to another and since then regardless on the ROM I flash I always have the same behaviour (I'm currently on the CM6 RC1).
I tried the following:
- full wipe via AmonRa + format of SD (128 SWAP + 512 EXT + FAT) clean reinstall of a presumably stable rom --> failed keeps rebooting or freezing
- I did a fastboot erase system -w + flash of a clean ROM --> failed
The bizarre thing is it never crashes when the phone is USB plugged on my laptop, therefore I've never seen a logcat showing anything bad ...
Also I can't identify any pattern or scenario which would systematically frag my magic... Even when I install a fresh new ROM, it can work pretty well for as long as an hour but then start being screwed up.
I've spent quite some time on this forum desperately looking for someone experiencing the same troubles but so far unsuccessfully ...
Would you guys have any idea ?
cheers
ZeRoT
Click to expand...
Click to collapse
This may not be your problem, but I found personaly that as soon as I enabled swap, my phone became a bit unstable. It was not rebooting itself when I had compcache on. Then I turned that off and switched to swap and now my phone rebooted itself sometimes. For me compcache was noticeably faster but swap multitasks better. So I've kept swap in spite of reboots. I have also found that switching between them either way my phone becomes unstable and rebooted itself multiple times before becoming stable on compcache or at least not rebooting as much on swap.
Sent from my HTC Magic using XDA App
well i had the same issue. nothing helped, i reinstalled the spl, radio, rom, recovery, everything.
the only thing that helped is :
REROOTING YOUR PHONE
there´s no other way.
have a good day.
zerot said:
Hi guys,
I have a problem with my Magic 32B and hope one of you guys could figure out where this all come from.
Since a couple of weeks my magic has become very unstable and I would say I have about 20 to 30 freezes or reboots a day. It suddenly started when I switched from a nightly froyo to another and since then regardless on the ROM I flash I always have the same behaviour (I'm currently on the CM6 RC1).
<snip>
Click to expand...
Click to collapse
I would expect a Donut based ROM to be fine. Which ROMs have you tried since the freezing/rebooting problem started?
The next time it reboots you should take a copy of /proc/last_kmsg and post it here. You can do so with:
Code:
adb shell cat /proc/last_kmsg > last_kmsg.log
Reboot cycle
I'm sorry if I'm in the wrong area, but I also have the same problem. I have a mytouch 3g (32B). I recently flashed it with "Froyo SPF Connection" and that made it reboot just about every 30 seconds. I restored it to the 1.6 Donut rom and it kept rebooting but repeated the process and now it seems fine. The problem is I don't want the 1.6 rom but that's all can have right now since everything else slows it down and freezes it. Please help me solve this problem. I'm opened to any useful recommendations and every help is appreciated.
benjaminb007 said:
I'm sorry if I'm in the wrong area, but I also have the same problem. I have a mytouch 3g (32B). I recently flashed it with "Froyo SPF Connection" and that made it reboot just about every 30 seconds. I restored it to the 1.6 Donut rom and it kept rebooting but repeated the process and now it seems fine. The problem is I don't want the 1.6 rom but that's all can have right now since everything else slows it down and freezes it. Please help me solve this problem. I'm opened to any useful recommendations and every help is appreciated.
Click to expand...
Click to collapse
Eclair ROMs are just as stable as donut ROMs and as fast as donut. Just don't use Froyo till it's stable. Use CM5.0.8 or any CM variant and you should be fine.
I'm having the same problem after flashing the new radio the phone will boot and as soon as its done loading the home screen it will reboot then load the home scree and turn off
Flashed French Connection ROM few days back and have had same problems as above ever sense.. Flash other ROM's and they constantly Reboot. cy 6.0 Working for me now, But only my Nandroid back up of it. Re flashed it fresh and it reboots...
why dont you reroot ur phones like i told you?
This freezing and rebooting problem is weird - it doesn't make sense a lot of the time.
I've developed a ROM based on AOSP 2.2 for the G1 and it also seemingly randomly freezes or reboots.
When it reboots it's usually the result of an ARM9 crash and so far I have tracked it down to a call to a proprietary library function which doesn't return to the correct return address. It seemingly returns to a random address and the consequences of doing so is random. Sometimes it causes a freeze or a reboot and other times it doesn't.
I'm starting to suspect something in the JNI code is causing the problem but it's difficult to track it down.
FroYo SP French Connection is overclocked to 614 by default. My Mytouch (32B) reboots and freezes constantly if i don't turn it down to 576. Try turning the overclock down in set cpu to 528 first then if its stable you can try turning it up a little.
Urgh, I hadn't considered clock speed as a potential problem.
What if some of our phones are unstable at the default Froyo maximum of 528 MHz?
I am (was) in the same situation (Magic 32B). It started with CM6 RC1 first and after it, my nandroid backups got weird too! I always wiped everything and rebooted by myself several times. I never played with overclocking, compcache or ext partition - but after trying other FROYO ROMs as well, even a clean install of CM5.0.8 final was unstable got fc's and rebooted...
So, after one year of trying nearly every ROM out there, i finally made a decision: i went back to my stock rooted 1.5 cupcake!! Yes, 1.5! I never tried this ROM before - even in my first days i immediately switched to sense...
And what should i say? I'm blown away by the speed and stability of this ROM! Unbelievable! ... sad day ... really sad ....
And my decision after that: i will wait for an official FROYO for Magic, which was at least officially announced...
sad, sad, sad...
alutastisch said:
why dont you reroot ur phones like i told you?
Click to expand...
Click to collapse
Well, i think - like my approach - rerooting will not bug down the fault in FROYO ROMs. I hope it will be sorted out, but for me the daily flashing is over for now. I really appreciate the hard work of all the devs and i also donated to some, but at the end of the day i just want my phone and don't want to wait for going to homescreen or missing a call because of the lags...
sad, sad, sad...
akivlin said:
Urgh, I hadn't considered clock speed as a potential problem.
What if some of our phones are unstable at the default Froyo maximum of 528 MHz?
Click to expand...
Click to collapse
Well, I think default for stock unrooted phones is like three hundred something you could try that but it would be really slow.
hudl said:
I am (was) in the same situation (Magic 32B). It started with CM6 RC1 first and after it, my nandroid backups got weird too! I always wiped everything and rebooted by myself several times. I never played with overclocking, compcache or ext partition - but after trying other FROYO ROMs as well, even a clean install of CM5.0.8 final was unstable got fc's and rebooted...
So, after one year of trying nearly every ROM out there, i finally made a decision: i went back to my stock rooted 1.5 cupcake!! Yes, 1.5! I never tried this ROM before - even in my first days i immediately switched to sense...
And what should i say? I'm blown away by the speed and stability of this ROM! Unbelievable! ... sad day ... really sad ....
And my decision after that: i will wait for an official FROYO for Magic, which was at least officially announced...
sad, sad, sad...
Well, i think - like my approach - rerooting will not bug down the fault in FROYO ROMs. I hope it will be sorted out, but for me the daily flashing is over for now. I really appreciate the hard work of all the devs and i also donated to some, but at the end of the day i just want my phone and don't want to wait for going to homescreen or missing a call because of the lags...
sad, sad, sad...
Click to expand...
Click to collapse
I totally agree. I know waiting for the official Froyo for the Magic may take years before it's finally released, but I'm tired of flashing and testing new roms every day without getting the results I want. As a result of this frustration, I will go back to Donut 1.6 for now and wait for the official update. Hopefully 5.1 won't be out before we finally get the update
TJ Gonz said:
Well, I think default for stock unrooted phones is like three hundred something you could try that but it would be really slow.
Click to expand...
Click to collapse
Yes, I will find out the maximum Donut clock speed and test at that speed.
TJ Gonz said:
Well, I think default for stock unrooted phones is like three hundred something you could try that but it would be really slow.
Click to expand...
Click to collapse
I modified the kernel to allow only the following frequencies:
09-12 01:41:12.579 D/setcpu ( 281): Autodetecting Frequencies
09-12 01:41:12.599 D/setcpu ( 281): Frequencies autodetected: 122880 128000 245760
Click to expand...
Click to collapse
Unfortunately the phone still rebooted due to an ARM9 crash.
I've attached a small CM6 RC1 update as a test fix for the ARM9 crashing.
Anyone experiencing random freezing or reboots should give it a try by copying it to your SD card and boot to recovery to flash it.
If you install the test fix but still experience random reboots I'd appreciate if you could upload a copy of /proc/last_kmsg to http://android.pastebin.com and post the link to it in here. A logcat up to the point of the reboot would be very helpful too.
I was running the new version of cyanogen Froyo rom (RC3) and it worked fine for about a day or two but then I started having random restarts. At first it was just once in a while but then last night it got really bad. It was restarting every 2-3 minutes.
I thought the rom was the problem so I decided to try out zachattack052 & xillius200's 2.1&1.5HERO rom but I could not get the gapps to work.
At this point I was getting frustrated so I decided to just get the newest stable cyanogen rom (v5.0.8) thinking that at least this one is known to be pretty stable. Unfortunately, I am having random restart problems again (less than 30 minutes after flashing this rom). I think it most frequently restarts when I am sliding the screen back after using the keyboard. Not only that but it's noticeably slower than the other two roms.
I am getting a bit annoyed. Is it the roms that are the problem? Is it me, am I doing something wrong? Or is it a hardware problem with my phone?
Firmware version: 2.1-update1
Kernel version: 2.6.34-cyanogenmod
Mod version: CyanogenMod-5.0.8-DS
Recovery: RA-dream-v1.7.0
Programs running: Advanced Task Killer, Power Manager, Google Voice, Fancy Widget.
i have that Problem Too but then mine usually happens when its low on battery
it restarts once I take out the battery put it back in and it works fine for a while just keep it charging b4 it goes low thats what i did with mine
you just need to clean your system, run fastboot erase system -w and then try any rom you want. that should do the trick. I cant help you if you dont know how to use fastboot, in that case search for it in the forum n_n
etu_aty said:
you just need to clean your system, run fastboot erase system -w and then try any rom you want. that should do the trick. I cant help you if you dont know how to use fastboot, in that case search for it in the forum n_n
Click to expand...
Click to collapse
I've never used fastboot but I am sure I can figure it out. Does doing a wipe from fastboot clean more than doing a wipe from recovery? If so I will definitely try it.
I am running KiNgxKxROM Sapphire Sense to G1 Port v1.4 right now. I like it but I am still getting a couple random restarts a day. Two so far today, both of which were while the phone was sitting unused in my pocket.
same problem
I was having the same problem, except that my G1 was with CM 6 RC2 and it does restart only when i was trying to connect to internet through wifi or 3G. If I didnt connect to internet the phone was working OK. After I made upgrate to RC3 the problem disapiered.
Sorry for my english
You can either fastboot(you SHOULD know how to do this if you are rooted) or something that worked for me was that I switched to clockwork(using rom manager app) and flashed a new rom. BTW this should be in Q&A bud.
etu_aty said:
you just need to clean your system, run fastboot erase system -w and then try any rom you want. that should do the trick. I cant help you if you dont know how to use fastboot, in that case search for it in the forum n_n
Click to expand...
Click to collapse
fastboot -w bricked my phone.
after I erased everything it randomly restarted. went to the G1 screen then turned off. I have tried removing the battery but it still will not turn on. I have tried Home + Power, Camer + Power, Call + Menu + Power, and the power button by itself with no luck.
T-Mobile is sending me a new phone now.
Have you checked your battery lately? How old is it? What does it look like? Any bloating?
sent from superfroyo dream
Xx12thANG3LxX said:
Have you checked your battery lately? How old is it? What does it look like? Any bloating?
sent from superfroyo dream
Click to expand...
Click to collapse
I have two batteries and I tried it with both. One battery is brand new and the other is the original. When I plug it in the orange "charging" light doesn't even come on.
Hi,
I managed to brick my Milestone, terminally I'm afraid, but the symptoms are different than what I see around the forum so they might interest someone else.
So, I first backed up everything with GOT Nandroid and Titanium Backup then modded CyanogenMod 7 RC4 0.08-11.04.05 (Android 2.3.3) successfully, except that the SIM was locked and would not unlock, although it works in another phone. This was a bug supposedly fixed in version 6 of Cyanogen...
Browsing the forums, the only thing that made a bit of sense was that maybe the GSM frequency was set to the wrong value. There is a Nandroid mod (but not GOT) that allows you to change that so I entered GOT Nandroid again. Since it had no such option, I Rebooted. Then, the fun begun.
The phone got stuck on the Motorola logo and no button, not even Power, worked anymore. After waiting for many minutes with no progress, I took out the battery - that made a change , the phone shut down. I then put it back - the phone immediatelly, no, instantly, cause there's no delay as when you were powering it up, lights up with the same Motorola logo. Tried several times, always the same behavior.
I left it booting (but also connected to the charger) for a whole night, no change.
The phone is not seen by the PC when connected to USB. It won't reboot, normally or to recovery. Buttons won't work at all. Yeah, tried with or without the SIM and the sdcard, no change. Tried to start without battery, just the charger, doesn't work.
Useless to say, I am getting bored of that Motorola logo
I suspect that the bootloader in the internal memory got corrupted. Can this be flashed even if the device is not seen by the PC (I mean by the RDSLite installed on it)?
Cheers
When the charger is connected to the phone try at the same timeull out and pull in the battery while holding the buttons who will get you in the OR
Yup, it worked. So first I got the battery with a question mark. Then I put in the battery and I got a battery at 60%. Since I was holding Power+Camera, it continued to the Recovery mode and now I have a working Milestone with Cyanogen mod!!
Thank you a lot, Mikicishte.
I still have to see about the initial locked SIM problem... but that will be mostly fun.
florinadrian said:
I still have to see about the initial locked SIM problem... but that will be mostly fun.
Click to expand...
Click to collapse
Have you tried to factory reset the Milestone, to see if after that the SIM is accessible again ?
http://forum.cyanogenmod.com/topic/14099-sim-card-not-detected-after-factory-reset/
You could try also to install a logger application catlog for example (https://market.android.com/details?id=com.nolanlawson.logcat&feature=search_result ) to see in the logs if you can find out more details to help you with the investigations...
I did the factory reset as part of installing the mod.
Even if the post quoted reports the wipe as the source of the problem and not as a solution, I just wiped again with no good result.
Will try catlog.
florinadrian said:
I did the factory reset as part of installing the mod.
Even if the post quoted reports the wipe as the source of the problem and not as a solution, I just wiped again with no good result.
Will try catlog.
Click to expand...
Click to collapse
or maybe you could try to use an unlock tool to see what error is reporting
https://market.android.com/details?id=com.droidgram.bladeunlock&feature=search_result