Develop Bugs

Evervolv WiFi & other issues

This is my first thread here at xda
I don't know if this issue is already known or if it's just me with this problem. I have an HTC Evo and I've tried both Evervolv Roms for Android 2.3 http://forum.xda-developers.com/showthread.php?t=878020 and 2.2 http://forum.xda-developers.com/showthread.php?t=840285. Both Roms have problems with connecting with WiFi automatically, even when connecting manually, and require me to constantly turn the WiFi on and off to connect. Sometimes a reboot is needed on the 2.3 version because the WiFi gets stuck on "turning off". I'm wondering if there's a fix for this or if the developer of Evervolv will fix this in the future. I'm not able to comment on the developer's thread so this is my only way to get the problem out there. Also in the 2.3 version, the application launcher crashes often and requires a reboot each time to get anything to work. Flash Player doesn't seem to work at all (in fact only way i was able to install it was through Titanium-backup, as trying to install it from the market doesn't work) . I've also noticed random reboots on both versions 2.2 and 2.3. I really like the 2.3 Rom but the constant crashes of the app launcher forced me to switch to the 2.2 version and the WiFi problems persist on that as well. (if anyone asks why don't i just try another launcher, it's cause i like stock Android launchers the best )

Welcome!! The 2.3 rom is still beta so issues will be there. Are you using stock kernel? I've used cm roms and know you must change your wifi policy to never sleep. Not 100% sure if that's where your problem lies but its worth checking. Also the aosp roms IMO are still kinda iffy. Most seem very promising and some run very well but all still need alot of work. If it is becoming to big of an issue I'd nandroid backup, completely wipe and format and try a sense based rom, im trying Koni's ELITE and so far, im very impressed. Just a Thought.

Reverting to a 3.30.651.3 based ROM

I want to preface this by apologizing if this has been covered, but I was unable to find anything with a search.
Every single 3.70 based ROM results in wakelock issues within 24-48 hours. I have tried everything, including flashing the stock rooted rom and no matter what, my phone stops sleeping after a day or so. I fully wipe, flash the rom, and I don't download a single app until the wakelock kicks in, at which point I grab spare parts and get no useful information.
I am currently alternating between CM7 and CM6 because AOSP roms work fine...they just aren't quite as solid as I would like them to be at this point. GPS bugs (I've tried the fixes), no HDMI (I've heard about the beta apps and I'll try those soon), no 4G (I realize this has been added to the nightlies for CM7, but the GPS issues are a deal breaker for now) and slow file transfers between my PC and my phone when using CM7 also kill the rom for me.
I figured I would simply flash the stock rooted 3.30.651.3 so that I could have a fully functional phone without wakelock issues if the need arose. But whenever I try to flash after a full wipe (including dalvik cache), I get stuck on the white HTC EVO screen. All 3.70 roms and AOSP roms flash fine so there must be something I'm missing...do I have to downgrade my radio or something? Any help would be greatly appreciated. And once again, I'm sorry for the post if this has been covered.

Yes the radio has to be downgraded first. I'm not sure which radio you need but you should check out one of Viruses rom threads since his roms are mostly 3.30 based.

[SOLUTION] For those having problems with CM7 on nordic 177

Since I can't post in the Dev forum yet, I'll do it here:
The culprit for the WiFi, Market not working, Google Talk spitting out connection errors is the nordic 177 ROM. I went back to 155 and everything is good here.
So everyone, go back to a more stable ROM in order to test CM7 without introducing more variables into the equation.
Thanks.

No problem in my case. CM7 on noric.

If it works for you then you're lucky. I had these issues and I read all over the forums about them. I hope my posy will help some people.

shiftear said:
If it works for you then you're lucky. I had these issues and I read all over the forums about them. I hope my posy will help some people.
Click to expand...
Click to collapse
It works for me as well. In fact, I flashed first the Fixed Nordic, and it crashed all over...but as soon as I flashed with the FULL nordic, since then, no issues. Everything that has been reported as working, including GPS (locking in 1-2 minutes), WiFi, Camera, video camera, and Mic on Speaker Phone.... is working so far. I just make sure that I wipe all the info before installing a new update.
And I installed the FULL nordic to another friend and no issue either for this other person.

People should stick 100% with instructions and if THEN something dont work, report. In any other case ppl are creating chaos.

[EDIT] Accidentally posted in wrong forum, sorry - but solved by completly reinstalling again in the meantime...
Apart from the GPS issues, I was very happy with this CM7 ROM until I noticed today that I have a problem receiving SMS - sending works fine, the SMSC number is correct and the SIM-card works fine in any other phone for that matter, but I cannot receive any text messages.
Calling, MMS and Mobile Data all work. Any idea what else I could try before performing a complete reinstall of beta5 or reverting back to an old backup?
I came from Barebones 1.5 on a x.155 base via 4.1, the busybox fix and then beta5 which all worked flawlessly.

aGPS working only for me?
Hi, just to mention that I did flash the FULL nordic SBF + beta5, and they say that SBF doesn't make any difference. I cannot tell, I have only tested this one so far.
If I am not wrong at enabling aGPS, I guess under the menu Settings -> Location, if the wireless networks option is enabled, the aGPS should be working. If I start the compass, it displays my location with GPS off. And If I go to another part of the city, it will display quite accurately the new location (no GPS was turned on in the meantime). So I assume that aGPS is working.

Were you fixed or Full nordic, shiftear?

Full nordic. Apart from the above issues I also had market failing downloads. Since then I went back to 155 and reflashed CM7, so far zero problems.
I cannot stress this enough, something newer isn't necessarily better, I was lucky because I had CM7 on 155 before and made the correlation when I "upgraded" to 177. This nordic SBF doesn't play well with my (EU) Defy.
Check this out: http://forum.xda-developers.com/showthread.php?t=1060347, again market failing downloads. Too bad I can't post in Dev yet.

It is true with market failing downloads but after second page download, same thing with browser, maybe wi-fi it is the problem?
I have also CM7 after 3.5.1. nordic 177 also with camera zoom. I will try reflash 155 and then CM7.

[Q] Feasibility: Multiboot: Stock Froyo and CM7

Hi,
I need to know if it is feasible to have the following multiboot setup:
1) Stock Froyo as base (rooted)
2) CM7 as second boot option.
I need to do this because Tmobile wifi calling works consistantly on Stock Froyo but I'd like to have CM7 as an option when Im not in a place where I need wifi calling. I understand they are working on getting wifi calling working with CM7 however, it is not working yet in the stable build and I absolutely need the stability and wifi calling.
Thanks in advance for all responses.

Isn't there wifi calling in CM7? Not sure but check out CM7 whiterabbit edition

Wifi calling seems to work on CM7. It's very recent (impleme'ted only last week).
As to the main question, ask maniac if his multiboot mod works with stock ROMs. I think it does.
CM7 + CM9 double boot

yes its totally feasible... and i have tested it.
after installing 2nd init, install latest CWM bootmenu.
This will give you latest and stable recovery
Then follow the usual steps for multiboot...

Hi I tried to use the multiboot manager and it turned out to be a disaster.
I ended up flashing CM7 nightly over my stock because I couldn't figure out how to get to the second virtual recovery. I tried following the instructions and they just were not clear enough to avoid mistakes.
Now that I have flashed CM7, though I am pleased with the speed and the smoothness (very nice work fellas), i have lost the functionality of the wifi calling app working without an echo... so i cant use it. I guess this will get fixed eventually.
Im not sure where I went wrong, but its not as easily done as it is written out to be. I want to try again, but I am afraid to overwrite my CM7 and have to redo everything.

Use This guide but let the real system be and only flash the virtual system. Should do it. You don't need the app.

Hey thanks for the recommendation. I think i might have to go back to stock while the work out the kineto calling issues. I am a little scared but willing to try now that i am sure my contacts are backed up.

all applications stopping unexpectedly

Within 30-40 seconds after opening any application (including the android system ones that auto-load @ boot), they crash ; promting: "__ has stopped unexpectedly. please try again."
Recent changes:
installed avast! (recently uninstalled)
set up swift key X
any ideas/fixes?
on cm7 btw.

As a last resort, if nobody is able to come up with a specific fix for you, I would suggest reflashing the ROM or restoring to factory settings within the ROM. It can be a pain in the butt, but if nothing else works, it's like starting from scratch in the ROM. That tends to be what i do when i have problems that are widespread like that and it always fixes it for me.
Out of curiousity which build of CM7 are you using? I have the latest nightly (420) of 7.2 and it is the most stable and customizable DInc ROM I've tried.
EDIT: I am flashing CM 7.2 RC2 right now, I didn't realize it came out a few days ago. Until further notice though, I still would recommend the nightly just because I haven't really tried this yet, knowing CM though they wouldn't release an RC if it wasn't ready. Hopefully they will start work on CM9 for dinc soon if we cross our fingers.

of course >.<
i believe its a standard build of 7.0.2, i cant check though because settings crashes immediately
ugh.. now its bootlooping.

flashed to 7.2 RC2;
please lock.

vassskk said:
flashed to 7.2 RC2;
please lock.
Click to expand...
Click to collapse
I hope it works out for you!! if you have anymore problems, come on back and someone will try to help you out.