I had to build CM9 issue 6. I installed the new rom. the problem continues. Is there a solution
Build 7
Sent from my bananaphone.
Related
Hello!
I just got my desire and put the MildWild CM-3.8 on. Everything is ok but GPS is not working at all. I can turn it on but there is no GPS sign in task bar in any app that is using it (Igo, sportstracker, gps status, z-device test)...
What to do?
Thank you!
solved
I installed 3.7 and then 3.8 over and now it is working....
EDIT: Not solved I went running with app sportstracker and after 10 min the phone restarted. And started app again and it restarted again after 2 minutes...So there is something wrong with GPS in this ROM....
I will go to another ROM. Does anybody know if there is the same problem with MildWild V-3.5 Based on Oxygen 2.3.2 ?
i have same problem with mildwild 3.7 :S
tried latest radio and agps fix but nothing works
humercab said:
I will go to another ROM. Does anybody know if there is the same problem with MildWild V-3.5 Based on Oxygen 2.3.2 ?
Click to expand...
Click to collapse
I've had all latest Mildwild oxygen releases, and flashing the agps fix it all works.
http://forum.xda-developers.com/showthread.php?t=1466516
So in original rom there is the same problem with GPS? I will try it today. Will this fix the problem in CM7 version too?
Thx
I used fasterfix app on CM 3.7, and GPS works while running My Tracks and Runkeeper at the same time. Haven't tested CM 3.8 yet.
Sent from my HTC Desire using XDA App
if your gps isn't working at all:
settings->location and security->gps source->use internal antenna
i know its preset on stock roms so many ppl dont think about it when using custom
happened to myself^^
I tryed out new MildWild V-3.6 Based on Oxygen 2.3.2 + GPS fix + new kernel 2.6.35.14_r4. Went running with sportstracker + music from stock player and there was no problem... This is realy great rom . Thx MildWild !
I got annoying and strange problem. I've been running Andromedus Test Builds, but after 75 bulid I lost wifi, so I installed CM9 beta5 and everything was fine. Today camcorder did force exit and didn't want to run properly. Did nandroid, upgrade to beta6 w/ kernel 7 and lost wifi additionally. Then did recover of beta 5. Nothing changed. Now I'm running again Andromedus Test Build, but very low number - 64. And it seems to work right. But why, for sake, any new upgrade goes crazy? Any ideas?
Have been trying different kernels. DZ unlocked by htcdev (so every one must be upgrading manually).
Hope my english is good enough to understand me
Those are still beta builds - expect bugs if you use them
Sent from my HTC Vision using xda premium
What do you mean by lost wifi? It doesn't toggle or just doesn't find your network?
Also, I assume you're doing full wipes between roms as the test builds are odexed and the cm9 unofficial rom isn't. If you don't wipe you're gonna be boned..
Sent from my HTC Vision using xda premium
A port of IAmTheDarkOne's 4.2 rom from the Nexus S. Can't really test what works and what doesn't as it keeps displaying an error that the process com.android.phone has stopped. If anyone knows how to fix it hopefully it can help us have a fully working 4.2 rom.
Link to rom
http://www.mediafire.com/?2d8d6yr4abzn5ov
ubnub82 said:
A port of IAmTheDarkOne's 4.2 rom from the Nexus S. Can't really test what works and what doesn't as it keeps displaying an error that the process com.android.phone has stopped. If anyone knows how to fix it hopefully it can help us have a fully working 4.2 rom.
Link to rom
http://www.mediafire.com/?2d8d6yr4abzn5ov
Click to expand...
Click to collapse
The FC ( process com.android.phone ) is kernel related. try to use the stock kernel that came with IAmTheDarkOne's 4.2 rom
khan_frd2002 said:
The FC ( process com.android.phone ) is kernel related. try to use the stock kernel that came with IAmTheDarkOne's 4.2 rom
Click to expand...
Click to collapse
Still happened.
Try using a stock cm10 kernel
Sent from my Nexus S 4G using Tapatalk 2
replace the phone and contact apk files with those from an aosp 4.1.2 rom
this trick help you but you cannot make calls and baseband should be unknown
the only thing is that deleted the phone.apk and contacts.apk and then install the rom. its boots up fine with no fc
build a new kernel aint that hard
hey guys,
i was on official 4.3 firmware
i tried latest build of SlimKat and CM11, but seems camera is broken in both rom with this error "Can't connect to the camera"
is it just me or is a known issue?
EDIT
i just tried Slim-4.3.build.2.2 Stable build, still same camera error
what is the problem?
there was no error with camera in official 4.3 firmware
EDIT2 - FIXED
I fixed it by adding SlimISP_GK.bin from /data/ of official 4.3 FW to /system/cameradata/ of CM11 rom and setting correct permission,
Most likely Camera firmware got corrupted in some flash. I'd Odin back to Stock and then try flashing Recovery and Slim.
I am running IOKP 4.4.2 on a TMO GS3 and the camera is working fine
Okay guys,
I fixed it by adding SlimISP_GK.bin from /data/ of official 4.3 FW to /system/cameradata/ of CM11 rom and setting correct permission,
thanks
It's fine on the latest Slimbean weekly.
Sent from my SGH-T999 using xda app-developers app
Hi I don't know if this is the appropriate place to post this but I was wondering if anyone had a known fix for the camera for my t-mobile galaxy S3. It used to work before the last two snapshots of CM, now it just says Camera has stopped working on all Camera applications. Maybe I should go back to the last stable? That was a while now.. Thank you in advance! Also Have tried flashing Slimkat, seemed to work but I care for the ROM much. Maybe can someone point me in the direction of a good ROM to use?
Try Nexus Camera
I was on CM 11 M12 and was having a similar issue. Any time I would try to change the flash status the camera app would fail (Cannot Connect to Camera) and not come back until I rebooted the phone. I switched from CM11 M12 to Pac Rom 4.4.4 KTU84Q and had the exact same issue. Tried the CM Camera Fix App (CMFix) and that did nothing. I went and got the Nexus Camera App from the Play Store and haven't had any issues with the camera since. It's kind of weird because it appears to be the EXACT same camera but it worked for me.