I have following problems with my bt headsets: the connection gets small interferences very often (when I connect the same headset to my laptop there are almost never interferences and it works stable on larger distance) . The most annoying part is the sound stops working on calls (still works on media) and than I have to restart the phone to get it working again. Didn't have this issue when I had stock rom. Is there a fix for this problem? do other roms do it better?
Yes, other ROMs do better but this is such a relative term. Every ROM has its perfections and imperfections. It is up to you to decide which one to stick with. What I mean is, flash ROMs until you find the one. Most importantly, you should know that Lineage 14.1 is currently in 'nightly' mode meaning that there will be bugs here and there and for that reason frequent updates are dispatched. What you need is a stable ROM. There are many ROMs which are stable and you should try them out.
Here is the list of 'STABLE' ROMs you could try:
https://forum.xda-developers.com/honor-5x/development/aokp-unofficial-build-mm-t3398902
Related
Hello all,
I was hoping someone could point me in the right direction to a Gingerbread ROM with a working media start/stop/call end headphone button (I'm using the OEM headphones that came with the phone) and 911. Both of these issues are documented bugs.
I've tried CM 7 and a couple of MIUI ROMs and the non-functioning headphone is pretty much a deal breaker, as I use my Vibrant for podcasts more or less everyday; the fact that 911 doesn't work just seems dangerous.
I've scanned lots of posts for different ROMs and neither issue really seems to come up telling me one way or the other and I don't have a day to load every single available GB ROM and figure it out via trial and error. Search hasn't been particularly revealing either.
For now, it's back to Team Whiskey NextGen v2, but I've tasted Gingerbread and I like it.
Thanks for your time.
The 911 issue should be fixed in the future. As for the head phone button issue - it will never be fixed until the GB source drops for our vibrant.
The button function is a kernel issue, not a ROM issue. The current kernels are ports of other phones hacked to work for our phone (thus another reason not so good battery life). (IE: I9000 kernels)
Don't hold your breath - don't think GB source will ever drop for our phones - Samsung dropped us like a wet diaper.
Hey everyone, I was previously a MIUI user.. although this was when it was freshly was being ported over to SGS2 and there was a number of bugs. So I made the switch to Samsung based rom Hyperdroid haven't looked back since.
So my question is what is the known buglist at the moment on the latest stable release...
In specific has the reception issue been fixed ? I remember you were restricted in using 2G otherwise your reception would cut out and the phone goes into flight mode ?
&
Headset volume, having to boost your volume using a third party application to get over half volume sucked ! you loose quality along with that it barely made a difference...
Last I heard the official MIUI team had started development and people were hopeful this would solve alot of problems.. although all I can find here are the latest ICS ports...
Any other known bugs would be great.. Im just trying to decide if I should even waste my time making the switch. I dont want to be lead to disappointment.
Also if possible if you could please provide a link to the ROM your speaking about.
Thanks for reading.
I was running CM9 nightlies, which worked great. Then I flashed back to an official ROM and updated to the official ICS. Now I'm getting frequent disconnects when listening to music via bluetooth audio (bluetooth speaker dock, in-car bluetooth, etc). I never once had this issue with CM9 nightlies.
Anyone else experience similar issues?
EvilTelephone said:
I was running CM9 nightlies, which worked great. Then I flashed back to an official ROM and updated to the official ICS. Now I'm getting frequent disconnects when listening to music via bluetooth audio (bluetooth speaker dock, in-car bluetooth, etc). I never once had this issue with CM9 nightlies.
Anyone else experience similar issues?
Click to expand...
Click to collapse
I am too. Never had a problem with Gingerbread but just upgraded to the official ICS and it's freaking annoying.
I'll probably be switching back to CM9 nightlies. Even in its pre-beta state, it seems far more reliable than the official ICS ROM.
I do really like Samsung's music player app, though. I only wish I could install that on CM9 somehow.
If you are having BT disconnects on ICS,
Try plugging in the charger while testing it. The phone won't enter deep sleep while charging.
Some of the BT devices are not playing well with ICS.
My BT under ICS is about the same as under GB (all stock) except that my headset pause/play button no longer works under ICS.
daverup said:
If you are having BT disconnects on ICS,
Try plugging in the charger while testing it. The phone won't enter deep sleep while charging.
Some of the BT devices are not playing well with ICS.
Click to expand...
Click to collapse
Well, CM9 is ICS and I had no issues with my BT devices. It's something unique to the official ROM.
Maybe there's a way to modify the BT/sleep behavior on the official ROM, but at that point why not just use a custom ROM that works better?
EvilTelephone said:
Well, CM9 is ICS and I had no issues with my BT devices. It's something unique to the official ROM.
Maybe there's a way to modify the BT/sleep behavior on the official ROM, but at that point why not just use a custom ROM that works better?
Click to expand...
Click to collapse
I started having trouble with BT disconnects a few months back when I began testing Shostock2 and AOKP custom roms. I think custom roms are great, I just prefer Shostock2.
The charging cable plugged in work around will be my best suggestion for non-rooted ICS with BT disconnect issues.
My thread on this is:
http://forum.xda-developers.com/showthread.php?t=1609686
I'm still using Tasker to avoid the problem.
Probably something changed in the BT software somewhere...
I'm getting high voltage warnings with the stock ics and once the battery passes 35 percent it drains quickly. If I plug it to charge the phone just gets hot I have to restart to get it to charge
Sent from my SAMSUNG-SGH-I777 using xda app-developers app
daverup said:
I started having trouble with BT disconnects a few months back when I began testing Shostock2 and AOKP custom roms. I think custom roms are great, I just prefer Shostock2.
The charging cable plugged in work around will be my best suggestion for non-rooted ICS with BT disconnect issues.
My thread on this is:
http://forum.xda-developers.com/showthread.php?t=1609686
I'm still using Tasker to avoid the problem.
Probably something changed in the BT software somewhere...
Click to expand...
Click to collapse
I installed the F1 Galaxy Nexus ROM (ICS 4.0.4) and never had any problems with Bluetooth disconnects. So hopefully it's fixed now. I'm dl'ing the latest ShoStock 4.0.4 and will see if it's fixed as well.
Hi all,
I have an AT&T Galaxy SII (I777) which as everyone knows has the unsupported un-open Exynos4 chipset. I am currently on CM 9.1, which I like and is pretty stable for me.
I've been watching the nightlies in the CM10, CM10.1 and now CM10.2 threads hoping to see some sort of M or RC release. I think at some point, we were close to having an RC, but I guess the decision was changed.
As you might expect, I am looking for a daily driver build that is stable because I don't have as much time now as before to flash on a daily, weekly or even monthly basis, but I would like to get close to the cutting edge of software.
I noticed that AOKP has released jb-mr1 Milestone 1 back in April 2013 for the Samsung Galaxy S2 (i9100 INTL Exynos) (I777 ported by Task650). Then Milestone 2 in July 2013 (with I777 ports). So I am very interested in this.
My question/confusion: How is it possible that somewhat stable (i.e. milestone build) AOKP is available for i9100 when we haven't had anything but nightlies by CM. I thought AOKP is partly based on CM. Have they been able to fix certain things that the CM team couldn't? Or have they decided to have milestone builds despite some known bugs/issues? Can these AOKP builds (and their counterpart I777 ports) be considered daily drivers?
Thanks in advance!
I find most of the roms I have run are suitable for a daily driver. I am a flashaholic. I tend to change my daily driver monthly if not bimonthly. Task's rom is a good one. Of late I have been running Carbon, and it runs pretty well with the included kernel. I have ran Pacrom in the past as a daily, and performed pretty well too. I find with most of the 4.2.2 roms I like the STI kernel for better battery life. I really like the 4.2.2 interface. There is no reason not to try it out. I don't have any issues with any of the features I use on a daily basis ie Bluetooth, wifi, gps, and mobile data all seem to work nicely on the roms I have used. If something starts acting wonky a simple reboot fixes any problems.
Butchr said:
I find most of the roms I have run are suitable for a daily driver. I am a flashaholic. I tend to change my daily driver monthly if not bimonthly. Task's rom is a good one. Of late I have been running Carbon, and it runs pretty well with the included kernel. I have ran Pacrom in the past as a daily, and performed pretty well too. I find with most of the 4.2.2 roms I like the STI kernel for better battery life. I really like the 4.2.2 interface. There is no reason not to try it out. I don't have any issues with any of the features I use on a daily basis ie Bluetooth, wifi, gps, and mobile data all seem to work nicely on the roms I have used. If something starts acting wonky a simple reboot fixes any problems.
Click to expand...
Click to collapse
I agree. I went from task ics to sho stock jb and i can tell that is by far, imo, the most stable rom. But it is 4.1.2, now mr cook has the official att version moded and seems to be good. I've been on pac man for about 4 months now with sti kernel and it's been great. Don't update always to the latest build because nothing is broken for me. I agree with butcher, try it out and you will see.
Sent from the second to last Galaxy
PACman Rom 23.0
STI kernel 2.38
Hi guys,
Thanks a lot for the recommendations.
This past weekend I started by flashing Task650's AOKP ROM. It seemed awesome at first, but then I ran into the following annoying issues which were non-issues with my previous CM 9.1 ROM:
I am unable to turn ring or notification vibrate off even though I uncheck all the boxes I am aware of.
Battery life *feels* worse than CM 9.1. Also, I sometimes get the sudden drop in battery percentage on phone reboot, even though I re-calibrated the battery by discharging and charging it fully.
Voice dialer using Bluetooth doesn't work/ gets stuck at Start up. It also freezes with Google Search. Seems to be a known JB issue so I am very surprised. This functionality is critical as I commute 2 hours and it's safer for me to use the Voice Dialer for calls.
Audio defaults to Bluetooth when I have both my headphone jack and Bluetooth connected. I have to unplug my headphones and plug them again to get the sound re-routed to the headphones. With CM 9.1, it always defaulted to the headphones.
I think I will try PACman next because at least I see it at RC1, which gives an indication of some sort of stability. I hope the above issues are fixed.
As a last resort, I would probably go to Shostock3.
The battery going from somewhere under fifty percent down to the teens on reboot is a known issue for any jellybean rom. I found the battery on Tasks rom not so great as well. Flashing Sti kernel helped mine drastically. Never had all the Bluetooth problems everyone else complains about. I mean sometimes it was a little wonky, but a simple phone reboot always took care of any issue with my Bluetooth. Granted I only use it once a week or so with my LG headset when I mow the grass. I am waiting on Pac to release 4.3 for our phone before I flash back to Pac.
Thanks for your reply, Butchr.
A couple of nights ago was an interesting night for me. I was already on Task's AOKP and I decided to give PAC a shot. After copying the ROM's ZIP to my internal SD card and formatting system, the flash failed because it couldn't identify my phone as an I777. So I had to comment out the first lines of the updater scripts in order to bypass the check. However, I didn't have a way to push the updated ZIP file over to the internal SD card. I tried adb but it didn't work in recovery. Also, USB mounting in recovery doesn't work, at least not with Windows.
After a couple of hours, I wound up having to flash creepyncrawly's rooted 4.0.4 build using Odin. From there, I put PAC. It seemed awesome at first. Unfortunately, it had the exact same problem with Bluetooth that is affecting 4.2.2--bluetooth audio works fine, but bluetooth dialing causes the Voice Dialer or the Google Search to hang up at startup and fail initialization. It would be awesome if this is fixed in the last build, even though it seems like a Jelly Bean issue.
Immediately afterwards, I jumped on SHOstock's 4.1.2 ROM. Here are my thoughts:
- Not a big fan of touchwiz, but it's a little better than the Gingerbread days.
- I also don't like the notification panel because it's just packed with things, not leaving enough space for the actual notification. Could be a little more compact. Even after removing the brightness adjustment section. Cannot get rid of all the quick settings buttons.
- Another thing was when I downloaded Google maps, it always force-closed when attempting to start navigation. I had to uninstall it and download the APK for the latest version of Google Maps (with the interface changes). That worked fine.
- GPS locks very quickly.
- Battery life is awesome.
- No Bluetooth dialing issue. Had to use Google Search because Voice Dialer is not packaged in it.
- There is a known issue with notification sounds sometimes getting cut off. My first alarm this morning got cut off very quickly that I didn't wake up, but the first snooze alarm was fine, and that's when I woke up (10 minutes late).
I am interested in PAC if the bluetooth problem is fixed.
coming from 4.3, I've been going from rom to rom this week in search of a truly stable kitkat TW rom. I won't lie the roms were great in every way but each of them had a major flaw that caused me to switch (constant crashing, gps not working, wifi not working). I've tried dn3, r3ds, trents, and possibly more I don't even remember. yes I've tried agni. And trust me each time I did extensive thread-searching to troubleshoot my issues to no avail which is why I'm getting frustrated. I'm not asking for much. I just want a rom with a working gps, working wifi, and stability. And by stability I mean not just labeled "stable" but doesn't reboot five times a day and won't shut down in the middle of the night to fail to wake me in the morning. I also need s note 3. I don't even care about anything else, seriously. Has anyone had luck finding a rom with the aforementioned criteria? Thanks.
edit: never mind, finally found one.
R3d its the best.