I used safestrap 3.11, made a Rom Slot, flashed 10.1 (not the alpha version), flashed gapps, booted up, and everything works except for the bluetooth. I can't even turn it on, much less connect to anything. I click it and it immediately turns off like it was stuck in the "off" position.
I'm using a Razr MAXX, which shouldn't make any difference (just in case it does), and I rebooted it several times. Any suggestions other than reflashing?
I'm also having trouble with Facebook actually syncing with my contact photos but I am under the impression that this is Facebook's fault, not CM 10.1's fault.
Anyone have any trouble with this/know how to solve it?
its resolved in the last nightly build.....the Rom forum ........posted by Hashcode
Related
First off, this was a replacement handset, as soon as I got it I upgraded it to 2.3.6 rooted it and unlocked the bootloader. I then installed RomRacer's CWM. At this time I wiped phone through CWM and proceeded to install Aura (ROM) http://forum.xda-developers.com/showthread.php?t=1186990 everything went well and the phone booted up and that was that. I left the phone out all night and when I woke up I saw that the phone was asleep and wouldn't wake. No backups were restored so it isn't a corrupt backup. Phone kept doing it randomly and so I wiped it again and again to see if it would help but every time it would do the same. To cut the story short, I then completely wiped the rom off of the phone and installed nottachtix 1.2.9b..... and the same thing is still happening! I've tried different batteries just in case and nothing. What could be wrong here?
i had the same problem with neutrino 2.5...had to pull the battery to wake it up...have you tried any other roms like red pill or dark side? i am using neutrino 1.4-s with no wake issues...
Today it happened for the first time ever on my phone using cm7 weekly feb 20. I think I'm going to try out some other roms.
I just applied the wake with volume keys hack... so let's see what happens. I've only tried aura and nottachtix, but trying 2 different ROMS and having the same issue is making me think it might not be the ROMS
Sent from my MB865 using xda premium
i never had the wake issue on miui either...could also be ghosts in the machine
i'm having this problem too. both on stock rom and custom rom (mrom) so i'm thinking its not the rom it has to be something else
I'm getting the same thing using the newest CM 10.1 build by epinter, released today.
If I play music, and then put the screen to sleep, the music keeps playing, but I cannot wake up the screen using the power or volume keys. I have to pull the battery to reboot.
I disabled all volume mods I could find (wake on vol, skip tracks, etc), but same result in two different music players (apollo, mixzing), can't wake while music playing.
I don't think I had that issue on other roms (beanstalk, avatar) but i think those use an older kernel (2.X), whereas CM 10.1 uses the alpha 3.1 kernel. Using beanstalk was almost perfect, but for some reason Mixzing on beanstalk couldn't contact its servers to build playlists (and ads), which I really need.
d'ohhh, 2 steps forward, one step back
EDIT: looks like it might have been bad installs, all above mentioned issues now working in the various roms.
Hello, I've had a problem with the latest galaxy s3 I9300 build (ending in 8)
I'm on three and when making outgoing calls both me and the person on the other end get static and distortion. This is on landlines and mobiles. I tried a settings patch for hd voice but it wouldn't install. I have is this an ongoing problem, or is there a solution? I thanks
I'm on Three and running a Modaco rom with the same issue! Call audio was previously fine which leads me think this might be a network issue...
Update: Scratch that, reading around it seems this is a known bug, fix seems to be to re-flash stock and try CM again..
Still there
Have updated to most recent rev from stock and problem persists. It goes away whenever I turn mobile data off curiously, but this is impractical.
Thanks for responding
Interesting, I've spent most of the day baking and flashing the S3. It's not a kernel issue or a modem issue, I'm now using Modaco TW prebake with XLF5 modem and CF Root. No bug, but the moment I flash a vanilla pre-bake or a vanilla rom (CM9/AOPK) call audio is distorted. :/
Problem Persists with latest Nightly
I tried flashing the latest Nightly yesterday and the problem persists. I can no longer disable the distortion by disabling mobile data either. I am almost convinced that it is something to do with the Mobile data settings though.
Every Vanilla Rom
Confirmed, it's every vanilla rom I try too. CM9/AOKP etc. When I return to stock, or go Omega 7 the problem is none existant.
What did you guys do to resolv this? I was on RC2 and updated to 04.08. and now I do have those distortions.
I tried to change the radio but nothing really helps. Any hint on this?
My US Galaxy Player 5:
Model: YP-G70
ROM: Eryigit Rom 3.0 USA
Firmware: 2.3.6 Gingerbread
Launcher: ADW
Rooted: Yes
Sorry if this question has already been answered elsewhere, but I have scoured the forums and have seen no other people with an experience similar to mine.
I bought a refurbished galaxy player 5.0 US version on amazon about 6 months ago. Since about a week or two after I bought it, I have had nothing but problems with it:
-The player will randomly say the SD card has become unmounted (never on for more than 2 hours without the SD card being unmounted,) and the only way for it to recognize the SD card is a reboot
-The player will freeze when I am trying to open an app, and I am forced to hard reboot
-Occasionally starts randomly playing songs at full volume through the speakers, even though the player is on silent and is not being used (and there is no alarm on.)
I was originally using the stock ROM, and these problems gradually became worse and worse. After the freezing became so bad that I was literally forced to reboot (sometimes multiple times) any time I wanted to switch between apps, I decided to try using Cyanogen instead of Stock Gingerbread.
I loaded version CM7.2.0, and all of these problems completely disappeared (except for the SD card unmounting problem, but even this was way less frequent.) I used CM7 for a few weeks, and ran into the problem where flight mode was stuck on and I couldn't use my WIFI.
I tried to factory reset a few times, but still couldn't get it to work, so I tried flashing the Stock Gingerbread 2.3.6 back on, but got the boot loop error. I ignored the boot loop and used CWM to put CM7.2 back onto my player. I eventually got the WIFI to work through a third party app, and was able to use my player with no errors for about a week, until it went completely haywire and started crashing any time I tried to use any apps that WERE NOT third party apps. Also, none of the features like WIFI, bluetooth, camera, etc. were working. My app I use to study Chinese was still working, so I waited a few weeks before I tried to recover the player in case doing so made it unusable. I tried a hard reset, and this time I got a boot loop for Cyanogen as well. After a few weeks and about 40+ hours of flashing different ROMs onto the player and using different strategies to do so, I finally got past the a boot loop using Eryigit Rom 3.0 USA.
I was very happy to have use of my player back, but only a few days after flashing the stock ROM, the problems that plagued my player initially have returned.
Sorry for the novel, but I wanted to make sure I included a detailed history of my problems in case any lend some insight in to what is wrong with the device. Does anyone have any advice on what to do moving forward to fix any of these problems? Thanks in advanced.
Also, this probably isn't related, but I would like to note that my player stayed on without being charged for 10 straight days (with intermittent use over the period) when I had CM7 flashed and it was messed up. Wanted to point that out in case it signified that some specific critical process was not running, which led to buggy usage, but super long battery life.
Did you wipe the data partition and dalvik cache when you installed each new rom? If you didn't, I suspect that's causing a lot of your problems right there. To fix it, you'll need to use the "reset to factory" and 'wipe dalvik cache" options in CWM.
A couple of your problems are standard behavior. Specifically, the lack of bluetooth, camera, and hw acceleration are normal with CM9 or later on this device. Also bootloops will happen if you reboot your device while it's connected to a computer.
One possible solution for your sd-card issue is to unmount the drive (in the settings/control panel) then physically eject the card and reinsert it (making sure to push it in all the way, you'll feel it latch). That's what I did when I had a similar problem with my player and the sdcard.
Could be you did not wipe when you install rooms .. also try some 4.1 rom offcourse with wipe
Sent from my Galaxy Nexus using xda app-developers app
[Updated]
I recently put CM 11 on my Verizon S4. Everything was working fine. I decided to update to a more recent nightly (likely last weekend). After the update, my camera doesn't work any more. When I go in to the camera it shows a blank screen for the camera image, freezes for a while and then a popup says that the Camera Failed! After googling, I tried restoring the previous CM 11 image that worked previously. I tried wiping the cache, force closing the app and clearing cache and data, I re-flashed the original Samsung image, I did a factory reset. Nothing worked to restore the camera. I went in today to a phone repair shop and they replaced the camera module. That didn't help - it still didn't work. Thankfully they didn't charge me anything for their time which was really nice of them. I get home and restored the CM 11 backup of the working image. The camera still doesn't work and now the external speakers don't work for media files. I was afraid that it was something forgotten to be reconnected by the repair shop, but I can hear the phone ring when I make a call. (I haven't received a call yet so I don't know if it is only on outgoing calls).
Can anyone point me to help or resources for how I can diagnose and hopefully fix these problems? My phone is falling apart and I don't know what to do!
Peter
[Update] I solved the camera problem by restoring a backup of the original TW rom. This seems similar to a problem I had with dubbsy's rom where the GPS wouldn't work some times after a flash and required restoring the touchwiz rom to get it to work and then re-flashing the custom rom. Once the camera started working again with the original rom it continues to work with the OctOS rom. Strange but at least it works.
The external speaker was resolved by taking it back to the repair shop. He switched the external speaker module with one from another S4. Putting it back together it worked, but when he put back in all the screws and closed things up it didn't work again. Finally loosening a few screws, getting it to work and then retightening solved it. I don't think it was the original speaker module, but something about opening it up and closing it back up caused the speaker not to work at all. Now it does and I can hear the ringer and notifications agin.
My RAZR worked perfectly with CM12, but ever since I started using CM13, my Bluetooth begins to stutter or will not remember paired devices. I will need to reboot, then my paired device is not present, I need to Repair. I turned OFF Smart Lock (Trust Agent) from Google, this seems to make it worse.
When I do have BT working, it will work for a while ( < 15 min ) then it will start to stutter, and will not reconnect when I turn off BT then back on, I need to reboot.
I tried Clean Flashing numerous times, with no luck, It's definitely a coding error since I tried my phone on numerous BT devices, and it does it every time.
I turned off Smart Lock (Google Trust Agent) since this was always asking to setup every time I pair my device and I thought this was the problem but the problem remains.
My last build was 20160304-Nightly-spyder, (Yesterday's build).
I had the same problem on latest CM13 umts spyder. I was fed up and went back to stock ROM (ICS), which works perfectly not only with bluetooth, but in every other respect as well. It's a much smoother experience to CM13.
EDIT: Oh man. 4.0.4 doesn't support TLS 1.1 or 1.2.
I think I might go back to CM11/12/12.1.
EDIT2: I'm going to try MoKee ROM: http://forum.xda-developers.com/showthread.php?t=2596176
I'll get back to you and see how bluetooth is.
EDIT3: MoKee ROM killed itself (it started doing weird things from the get go, like asking me for my google account during the welcome phase after I had already logged in), and I didn't have enough time to test bluetooth with my cars headunit, which is where your symptoms occur for me, but I was able to test it on my PC's bluetooth dongle, where it showed the exact same symptoms as CM13 did. That is, I would have to reinitiate the pair every single time my phone connected, and not only that, but I would end up in a pairing loop, where as soon as I'd accept the pair, it would ask me again to accept a new pair, ad infinitum. Given this, I'm going to conclude that MoKee ROM's bluetooth is not the answer for our problem. By the way, the next time I booted MoKee ROM it reinitated the updating apps thing at startup, like I had just wiped cache (which I hadn't), and after I let it finish, it never booted properly.
The latest CM13 has an interesting commit: http://review.cyanogenmod.org/#/c/137459/
It might just solve one aspect of our problem so I'm going to test it and come back to you.
EDIT4: Nope. Same problem with headunit and dongle. FYI headunit is Pioneer MVH-X380BT (not old).
EDIT5: I'm on LiquidSmooth KitKat and I've called it a day. Bluetooth works as it should.