I know this is a somewhat known issue, and I've found fixes of loading a sense based rom, getting a GPS fix then reloading a backup, but I'm not having any luck that way.
I've tried loading a Sense 2 and 3 based ROM (Infected and BAMF). I was never able to get a fix using BAMF, Infected I got a GPS fix without issues.
Anyone have a better method? Should I keep trying with a Sense 3 based ROM?
This is the only issue I'm having (at least that I notice/will ever use).
Thunderbolt CyanogenMOD 7.1.1 (I've tried the 7.2 beta rom that's out there too).
I flashed ThunderShed v1.1 (which actually looks like a pretty solid ROM if you don't want AOSP look/feel).
Back in CyanogenMod 7.1.1 and GPS is working!
Related
hey, ive been trying to figure out which custom rom + kernel combination should i use but in every rom i'm reading some or the other complaining about something not working, losing signal, or sudden batttery loss, random reboots
is ther a reliable custom rom out ther ? .. because i dont wanna miss out on an important call or message or e-mail at the right time
i really liked what brainmasters miui and kelmsking have done with their roms but still even though its written stable but users aint feeling it to b stable.
i wud like ur opinions on this, and also if u all could help me find a stable rom like the stock one. i am always travelling so i cant afford to have a buggy phone cuz i wudnt have time to go to my computer to do something about it.
i know i have read it many times ther is no best rom cuz its personal choice, but still i want to knw more about stable roms
GPA18
Sent from my Nexus S 4G using xda premium
What's GPA18? I just got my S a week ago, I downgraded from a HTC Sensation and I'm going to use this for a while until Ice Cream Sandwich comes out, but I'm using OXYGEN's rom right now. Stock kernel it comes with and everything, and it's pretty stable for me, great battery life, sometimes I lose data but that's because of the radio update, but other than that, it's great.
gpa 18 is peter alfonso rom, gpa 18 is still not stable though ..
Hi,
I tried CyanogenMod7 (Nightly Builds and Stable version 7.1.0), MIUI (latest version) and Oxygen 2.3.1.
CM7: This is a great ROM but I got random reboot or asking my PIN code. I only have Google Apps, nothing about G+ 2.0 or GWallet. I got those issue since a while on Nightly Builds.
MIUI: if you like IPhone style, this is a great ROM too. None reboot.
Oxygen: this is also a nice ROM. You need to custom it with Go Launcher, GO Weather, GO SMS, DSP Manager... because this is a little raw but, nothing to say only stable.
Performances are pretty good.
There is also NSCollab ROM which is built off Cyanogen Mod,and its a combination of both stock and Cyanogen which I've found to be more stable probably cause of the kernel I.e Matr1x which is built off the stock kernel
I'm using NSCollab 1.0.50 right now and I haven't had any issue yet
I tried netarchy and Trinity kernels with NSCollab but matr1x seems to be the best with NSCollab, gives me a Quadrant of 3000 at 1Ghz
Sent from my Expensive Magical Brick.
Brainmasters MIUI is my fav. No reboots no signal loss when installed clean.
Sent from my Google Nexus S 9020a
You could go stock deodexed, zip-aligned and with newest radio. You could play with kernels for BLN, Voodoo, and OC. Stable but with a few goodies.
Sent from my Google Nexus S 9020a
I'm running opensensation cm9 (latest version). the last few builds have been hell on my battery, on a full charge im getting 5 hours with no wifi bluetooth and so forth. my phone like overheated today and took forever to finally boot back up. someone mentioned switching kernels, idk anything about how that works or which ones are safe to use on which roms. any help would be nice. thanks.
Installing a kernel is done the same way you flashed the rom. Flash the zip file in your recovery.
I think your choices right now are either stock opensense kernel or faux's cm9/aosp kernel. Also, I don't think developers release kernels dangerous for your phone. Worst case scenario your phone gets stuck in a bootloop and you have to go back to stock kernel or reflash your rom.
Just keep in mind that a rom like that which is in alpha stage will have bugs that won't be fixed by just switching kernels. Luckily Vorbeth has been working nonstop on Opensense. One would think he was getting paid to dev.. Lol
Sent from my HTC Sensation Z710e using Tapatalk
I don't really recommend switching kernels since Vorbeth has done kernel-level fixes for OpenSensation. Flashing a different kernel has a good chance of breaking something in the ROM...until the wake lock issue is figured out, I suggest using a stable Sense ROM like Android Revolution HD or Virtuous Inquisition if you still want the ICS AOSP look.
Hello!
I flashed CM9 RC2 recently and now whatsapp doesn't work. I get warning after installing it saying that custom rom might cause whatsapp not to work properly. After starting whatsapp it simply closes down.
Before CM9 RC2 i used HyperSensation Rom (2.9 i think), and it worked normally without any problems.
Is there anything i can do to get this to work besides reflashing ROM?
Thank you.
Delete the data of the app.. Un-install it and install it again that might help
Sent from my pyramid using blazing fast sonic waves
Tried that several times. Problem still persists.
EDIT: Just to report. Eventually i installed latest AOKP rom from their site (Milestone 6), and it works fine now.
ive had this same problem. I am usuing the CM9 RC2 right from the cyanogen mod website for samsung captivate ATT. if i install the AOKP rom you think it will work. and if i do whats the difference between AOKP build 40 and milestone 6.
edit: ok i installed milestone 6 and still did not work. what the hell
hshaikh said:
ive had this same problem. I am usuing the CM9 RC2 right from the cyanogen mod website for samsung captivate ATT. if i install the AOKP rom you think it will work. and if i do whats the difference between AOKP build 40 and milestone 6.
edit: ok i installed milestone 6 and still did not work. what the hell
Click to expand...
Click to collapse
AOKP builds marked with number (for example: build 40) are something like beta builds and are more likely to have bugs. Milestone builds are more stable releases.
Regarding problem with whatsapp. Seriously i dont know why is this happening. I tried searching net and found couple guys with same problem but nobody offered solution. As i said in my first post, i used hypersensation which was build on one of earlier CM9 releases and it worked fine. So i would suggest to try some earlier releases of AOKP or CM9 or some rom from XDA based on them.
could you please provide me with a link to the rom you used. i will try that one
Here is hypersensation. However i used 2.9 version based on CM9, current version is 3.1. Download is in post 2. In post 3 you can find AOKP roms, but i haven't tried these.
I am using a samsung Captivate. will this rom work for me
My guess is no. You should probably go to Samsung Captivate forum and check there. I don't know anything about Captivate.
Guys, am I the only one getting constant reboots on the latest nightlies? I load up a nightly (have tried 3/17, 3/19, 3/23 so far) and I clear data cache and dalvik prior and post load. I also load the newest 4.2.2 gapps for jb.
The phone reboots itself on everything from Temple Run to basic browsing to music playing through Bluetooth. There seems to be no rhyme, reason, or specific app causing it.
I am using the built in kernel... Is this kernel instability I am seeing?
Please tell me I'm not the only one experiencing this. I am a big fan of cyanogenmod, have used it on many phones over the years but this has been very unreliable for me.
Thanks, Brian
Did you try to fix permission using cwm or ROM manager? That might help. if not, try aokp 4.2.2 or liquid smooth.
Sent from a Shaftamle Galaxy S3
Shaftamle said:
Did you try to fix permission using cwm or ROM manager? That might help. if not, try aokp 4.2.2 or liquid smooth.
Sent from a Shaftamle Galaxy S3
Click to expand...
Click to collapse
Ok so I fixed permissions on 3/23 cyanogenmod nightly, still constant reboots. Then I flashed aokp (hilbert) newest nightly based on 3.0.68 kernel and I am getting the same problem.
Is there any other way to troubleshoot this? Can someone else speak up who is running the newest night lies without FCs or reboots so I know I'm not crazy.?
Thanks for your IMs as well... I will definitely try newer builds.
bguild said:
Guys, am I the only one getting constant reboots on the latest nightlies?
Click to expand...
Click to collapse
I didn't get constant reboots but I did get random reboots from time to time.
I also noticed the latest nightly I ran (3/23) seems very slow.
My fix was to restore my backup of CleanRom and I may just not return to CM 10.1.
Lockups and random reboots have been discussed for the last few pages in both the thread in this section and the dev section, commonly seems to have started 3/18 nightly when they switched over to the 3.4 kernel..newest nightlies were supposed to have some fixes merged but I haven't tried it yet
http://forum.xda-developers.com/showthread.php?t=2071252&page=124
personally had the issue on both 3/20, 3/21 , rolled back to the last nightly on the old kernel which is 3/17 and haven't had it happen since as for AOKP I don't use that so couldn't tell you what the issue is with that ROM
NeoMagus said:
Lockups and random reboots have been discussed for the last few pages in both the thread in this section and the dev section, commonly seems to have started 3/18 nightly when they switched over to the 3.4 kernel..newest nightlies were supposed to have some fixes merged but I haven't tried it yet
http://forum.xda-developers.com/showthread.php?t=2071252&page=124
personally had the issue on both 3/20, 3/21 , rolled back to the last nightly on the old kernel which is 3/17 and haven't had it happen since as for AOKP I don't use that so couldn't tell you what the issue is with that ROM
Click to expand...
Click to collapse
My thought is that in my case there may be something else going on. So far I have tried Cyanogenmod 3/17,3/20 and 3/23 nightly, a 3/23 nightly for AOKP, and now I just installed CleanROM 6.2 R2, which is Android 4.1.2 based. I think most of these kernels are 3.0.x based. I am definitely still getting occasional reboots and FCs but I will say it seems CleanROM is the most stable.
The common thread on all of these builds seems to be that the most instability occurs when attempting to connect to a bluetooth device. That is when I get the constant reboots. I'm talking like you start to play a song, and it gets through half way and just completely reboots itself.
I'm going to keep trying here, but I might have found the common thread in bluetooth instability.
Does the 3.4 kernel report as 3.4.x on the newer nightlies?
Yes it shows in the settings, I personally haven't had any issues with connecting or using my A2DP rocketfish Bluetooth headset even when I was on the newer nightlies with the 3.4 kernel, it was more of hadn't used the phone for a while went to turn the screen on and it wouldn't come back had to battery pull.
Haven't had a single problem since rolling back lockup or otherwise so I'm watching the main threads to hear when they get the issues with the kernel figured out before flashing anything newer
Anyone know any reliable ROMs for a Nexus 6 on marshmallow 6.0.1
IV tried to search for ROMs and have installed and deleted about 6 in total none of them work one nearly worked benzo but had to many hickups to be any use tryed to install the kernel that came with it but had no effect I would like to use benzo I searched alot into this it seems ideal but as I'm new to this I didn't understand y it didn't work properly I wiped data after flashing it so should in theory work only thing I could put it down to is some settings are conflicting with one another not sure if this is possible as each and every other setting should override one another to priority I ended up restoring my phone and just using stock atm
Hey Mike. I have flashed several excellent and reliable ROMS that can be used as daily drivers on my Nexus 6. AOSiP was a nice, solid stable ROM with plenty of features. Pure Nexus is a ROM that I use as well without any issues. Currently I am running N6XShamu with the Blackb1rd Kernek and they work very nice together. Super fast, buttery smooth and an excellent ROM experience overall. What ROMs have you tried and what issues were you having ? What recovery are you using and what version? Do you know what bootloader version currently have? Also, when ashing the different ROMs did you make sure to do a clean install by wiping everything except your internal storage? I can help you get this figured out so you can enjoy a custom ROM.