Since I bought the One I'm running Sense Roms (at the moment it's Android Revolution HD). For the last few days I have been trying to flash ParanoidRom and CM11 Nightlies but with both of them I encounter weird problems.
1. Both roms seem to break DHCP for me. I can connect to any Wifi but I don't get an IP. If I set the IP manually everything works fine. I already deleted the files in /data/misc/dhcp a few times but still no change.
2. With both roms I have freezes when waking the phone up from sleep. Most of the time it works, but 5-10 times a day the softkeys light up but the phone freezes when I try to wake it up from sleep. The problem exists with stock and with custom kernels.
Before flashing I wipe Data/Factory Reset, Dalvik and Cache. Last time I even wiped /system, just to try if it makes a difference.
Restoring my old rom fixes all the problems.
Is there anything I did wrong? I have no idea what else to do now
Related
When I try to enable WIFI on my G1, for a couple of seconds it says: enabling WIFI, but then the phone becomes unresponsive (for about 1 second) and it reboots.
IIRC the problem started when I upgraded to the new CynogenMod ROM (4.1.99, but not sure), but it doesn't seem to be linked to the ROM.
I have always used CyanogenMod and update with every new version.
I tried to go back to the default HTC rom, but this doesn't solve the issue.
Does anyone know what may cause this or give me some tips on how to debug this?
I tried to run 'adb logcat' but it shows no info.
The exception browser in the CyanogenMod is also empty.
I don't know what else I could try.
Some extra info:
HSPL 10.95.3000
Radio 2.22.19.26I
CynogenMod ROM 4.1.99 is not the newest. Wipe, flash the htc image, flash cyan's newest and try wifi again.
No, I know, but I think that's when the problems started.
Latest version I installed was 4.2.13
I have installed the RC7 dreaimg.nbh now (used to root the G1), and when I try to enable WIFI on this rom, the phone doesn't reboot, it keeps working, but I get an error saying that WIFI could not be started.
I'm also having problems with wifi causing random reboots. For me it usually happens once a day if wifi is enabled and not at all if its disabled. Once the phone reboots, it hangs at the android screen and I have to do a battery pull to reset it. The problem also appears to be rom independent. Very weird, it has started happening in the last few weeks and I can't think of anything that has changed.
mattb3 said:
I'm also having problems with wifi causing random reboots. For me it usually happens once a day if wifi is enabled and not at all if its disabled. Once the phone reboots, it hangs at the android screen and I have to do a battery pull to reset it. The problem also appears to be rom independent. Very weird, it has started happening in the last few weeks and I can't think of anything that has changed.
Click to expand...
Click to collapse
This is consistent with my experience as well. By far, the VAST majority of spontaneous reboots that have occurred on my phone have been when using wifi. Some of the older Cyan ROMs were really bad about this, but this continues to occur (although much less frequently) regardless of the ROM. I am presently using SuperD and have had one reboot in the past week.
This seems to happen most often when using the wifi heavily; for instance, I get a reboot probably every 3rd or 4th time when I'm doing my weekly podcast downloads. I don't remember any reboots when just surfing the web or downloading apps, though.
I have never had this happen when I was running cyan.
Are you wiping everything? Even EXT and dalvick?
Are you using any other apps when this is running and rebooting? Perhaps an offending app?
You should also open ADB and run ADB Logcat and try to replicate the issue and try to get a log submitted so the dev can help determine what is causing this issue.
I wiped everything and even without any apps installed, it just reboots.
adb logcat doesn't show a thing when the phone reboots, it just exits.
In addition to the home and talk buttons not working. The phone will not lock when I hit end, it just puts into a sleep mode.
Holding end only gives a reboot and shut down option. This problem surfaced after installing the new SuperD mod. I did a wipe and reinstalled it two nights ago and the problem was resolved, but it has resurfaced tonight.
Anyone have any thoughts on the matter? Should I go back to the old version?
Which new version? The beta or 1.10.2? If it's beta - then you def should go back to stable. If it's 1.10.2 - then you most likely have a hardware problem. A lot of people run Super-D with no problems.
Further more, sometimes your trout-keypad-v3.kl (located in /system/usr/keylayout/) can get corrupted and cause that. It's extremely rare but you may try either re-flashing or just pushing that specific file.
Word of advice (which you may already know): if anything goes wrong and you want to rule out software problem - install a base rom (like the defanged from Cyan's wiki), complete wipe and min options (no Apps2sd, no swap, etc) and see if it fixes the problem. If the problem is gone - you're in lock and something went wrong with the rom. If problem is still there- start looking for a new phone.
Good luck.
I did a fresh install. I repartitioned the sd card, reinstalled all apps. did a factory wipe, reinstalled the base defanged, then did super D. It wasn't the beta, i had upgraded to 1.10.2 and experienced the problems.
It would work fine for two days, then if my phone would shut off (battery has weird contacts) then it would boot back up and my settings would be all messed up, and the keys would work. I would try re installing the ROM, but no fix.
A wipe remedies the problem. I went back to cyanogen last night to see if the problem appears on this rom, so far it hasn't.
I never had this problem until i upgraded from 1.9.3
I'm on CM dal .32 test build 3.1
Today I tried setting up a VPN but failed. The screen became frozen and I decided to reboot my Nook Color. However, after rebooting my wifi is no longer working. It says "connecting" but then "disconnected" Scan option didn't show any network.
Anyone can help me?
CM7.0.3 with Nook Color no longer works
Hi,
I've run into the same issue with my nook color. I'm not sure if this is an issue with the kernel or the physical device. I know that this is not a router issue since I'm able to connect other machines to my router. Also, I no longer see any other hotspots with the Nook.
I tried some suggestions that I've found on other websites, which include
Shutdown Tablet and start again
Re-install Google Apps
Use Fix Permissions in Rom Manager
None of these work. Any suggestions or is this a known bug?
lazinase said:
I'm on CM dal .32 test build 3.1
Today I tried setting up a VPN but failed. The screen became frozen and I decided to reboot my Nook Color. However, after rebooting my wifi is no longer working. It says "connecting" but then "disconnected" Scan option didn't show any network.
Anyone can help me?
Click to expand...
Click to collapse
Same here, I was using nightly 115 with Dalingrin's 6/18 OC kernel when the problem started. I've since rebooted multiple times, fixed permission both from CWM and in Rom Manager, flashed nightly 117 without flashing OC kernel, and still haven't solved the problem.
Wifi just stays "Connecting" and then changed to "Disconnected" briefly and go back to "Connecting" again.
Just reflash your ROM or the latest ROM and DON'T mess with any OC kernels.
Does it work? If so, try the OC kernel again. If it fails, let Dal know in his OC kernel thread, and just re-flash your ROM again to return to the stock kernel. Wipe cache/dalvik as necessary, but don't wipe data and you're not going to lose anything.
One suggestion I have is if you're using AES on your router, try changing from WPA2 to WPA or changing WPA AES (or AES+TKIP) to just WPA TKIP and see if that fixes the problem.
There's a long standing issue with some routers regarding AES in Android, and apparently some laptops also had this issue on older kernels.
Flashing to the latest rom without messing with the kernel was the first thing I tried (other than turning wifi on and off multiple times). It didn't work.
What eventually worked was when I wiped data and factory reset it. Some how that fixed the wifi.
The strange thing is I had just recently factory re-setted coming from an old (pre 2.6.32) nightly a couple of days ago, and had not gotten around to installing much, and I did not restore from backup. i.e. the only thing installed when the wifi problem suddenly appeared were the google apps, Aldiko, QuickPic, Rom Manager, MoboPlayer, and a few ADW themes. None of which sound like they should do anything that messes up the wifi.
I doubt it has anything to do with the router, because I tried connecting it to my router (tkip), hotspot from my android phone (unlocked) and hotspot from my iphone (unlocked). My phone just did not see any network around at all, not even the 5-6 different network from other people in the building.
As mentioned, I have factory wiped my NC and all is fine again now, so I'm not too concerned right now, just curious what could have caused the problem.
First, hello
Since a few days, I encountered big network problems with my phone:
I can't call or receive a call, and I can't send or receive SMS anymore. It's very hazardous, but most of the time it doesn't work. My network connection is often unavailable: most of the time it disconnects when i try to use the network and reconnects seconds later, sometimes without improvements.
I was running the Temasek's Kang with the ETANA kernet when this problem appeared. I tried to reboot, wipe cache, wipe dalvic cache, update CM7 and the Kernel. I tried to do a wipe data/factory reset and install the last updates, without success. :S
So I tried NVflash... I install the V10B version, and my phone seems to works better. But not perfectly at all. Sometimes it works, sometimes it doesn't.
I tried to install the last BB (824), nothing better. I tried with the 218, the problem persists.
It's very annoying, I miss all the call I receive: my phone doesn't ring and my correspondent goes directly to the "voicemail" (I don't know how do you call that ^^)
I don't know what to do, and where the problem could be.
If you got any idea, please share
Thanks!
Hello guys,
I was looking for the answer for a long time, but I didn't find a solution for my case. My problem is a serious battery drain AFTER making a call. When i finish a call, the battery starts to lose about 7-10% of the energy per hour, even though the phone is not used and is in the same place as previously (so its not a problem with the poor gsm signal). The only solution is to restart my phone - it helps immediately, but onlyas long as there is no new phone call made.
I have installed Better Battery Stats, what I could notice is:
- in "CPU states" before the call the processor stays in "Deep sleep" for most of the time, after a call it remains at 100MHz
- in "Kernel wakelock" a gpsd process appears and takes most of the time
GPS is switched off all the time.
I think that the problem had appeared after one of the CM 11 update, however during the last month i thing i have installed really many different ROMs - CM 9, several CM 10 versions (10, 10.1, 10.1.3 etc), finally i came back to the stock 2.3.6, unfortunatelly - nothing has changed. Before each ROM installation i did factory reset and cache wipe. Yesterday i alsohad formatted internal SD card, after that i installed CWM 2.7.4 with CM 10.1.3 (this was working well couple of months ago) and completely nothing has changed.
Could you please work out the reason and a solution? Its obvious for me that the problem comes after making a call and now I really can't work out any ideas how to solve the problem. Yesterday I changed the radio ROM - no change at all...
Hope you guys can help me
Strange issue. Did you recently try to format /system before installing any of those ROMs? It is usually not required in the i9000 threads, but for all other devices formatting /system is a substantial step to insure that the next installation will be fine.
tetakpatalked from Nexus 7 flo
tetakpatak said:
Strange issue. Did you recently try to format /system before installing any of those ROMs? It is usually not required in the i9000 threads, but for all other devices formatting /system is a substantial step to insure that the next installation will be fine.
Click to expand...
Click to collapse
Thanks for reply. As far as i remember - I did it last time (as well as I formatted /boot, /data, /cache and rest of the format options from Mount and Storage in CWM).