Develop Bugs

Is streaming/internet radio working on your Desire? (issue with wireless N patch?)

It's not working properly on mine, ever since I moved up to FroYo a couple of weeks ago.
Streaming works fine over 3G but if I use it on wi-fi, with the screen switched off, the music starts stuttering and eventually skips.
Thought it was an issue with the rom I was using, but I've tried three different ones (including one of the new ones from this afternoon) and I'm seeing the same issue.
Wi-fi policy is set to never sleep so it can't be that.
Could somebody test it out and let me know?
NB
It only happens on wi-fi
It only happens when the screen has been off for one-two minutes

Update, in the off-chance that somebody, somewhere has actually bothered to read this...
Flashed back to 2.1 and the issue was gone. Back to 2.2 and the issue is there again.
edited to remove pointless speculation. solution is on page 2.

why would you call HTC support, surely thats a job for the last.fm development team to work out.

Because I don't think it's an issue with last.fm. It apparently works fine on non-Sense phones, and even works fine with the earlier versions of HTC Sense.
Last.fm has permission to keep the phone awake, and it does so over 3G but not over wi-fi.
It doesn't really make sense unless the newer version of Sense is throttling the wi-fi when it goes into sleep mode and is not allowing last.fm to keep the phone awake.
Can't really verify that though... I might try to find another app that uses the wi-fi connection and see if it exhibits the same behaviour when the screen is off.
edit: just checked with the speedtest.net app and switching the screen off freezes the download in its tracks. Resumes again when you switch the screen back on.

Phone/Wifi sleep issue while not plugged in
Hi, I can confirm that this is happening to me with XiiaLive in an identical way.
- 3G streaming works ok
- Wifi + screen on works ok
- Wifi + screen off BUT plugged into AC works ok
- Wifi + screen off => drops the connection after a couple of minutes
I went mad yesterday trying to make xiia work, but then realized that this could be the case and found this post and another one on Modaco (http://android.modaco.com/content/h...s-possibly-a-request-for-the-next-modaco-rom/)
So you actually saved me the time of testing it in other roms, but anyway, which rom have you got ? I have ieftm one.
I can save you the time to test it with other streaming services, I've tried them all hehe.
It could be a phone sleep issue, rather that a wifi sleep.

Well, like I said above, my guess is that the newer version of sense is throttling the wi-fi to save battery life when the phone is idle. The wi-fi is still working but it's capped at a lower speed.
You can test this by installing tunewiki and trying out a few radio streams. 96kbps works perfectly, 128kbps is ok but stutters a little at times. Then when you go up to 192kbps (which I think is the quality last.fm streams at) it can't keep up anymore and the tracks skip.
re:roms - I was on ieftm, am currently on modaco and was on modaco r5 and r6 before that. All of them have the same issue and all are based on the FroYo/Sense roms.

Hm, it´s working just fine for me. Listening to it right now with display turned off, no problem here.
Using the original Froyo on a debranded Desire...

What do you mean by original FroYo? As in vanilla?
From what I can tell it's only happening on Sense roms.

My statement was a little misleading. I was referring to the normal OTA update...

Sibbi said:
My statement was a little misleading. I was referring to the normal OTA update...
Click to expand...
Click to collapse
Hmm. And it's on wi-fi and it's not plugged in to the mains?
Weird. I can't replicate this on any FroYo + Sense rom. I haven't tried an unrooted 2.2 rom, though.
Be good if we could get somebody else on an OTA 2.2 rom to confirm this.

tuatha said:
Hmm. And it's on wi-fi and it's not plugged in to the mains?
Weird. I can't replicate this on any FroYo + Sense rom. I haven't tried an unrooted 2.2 rom, though.
Be good if we could get somebody else on an OTA 2.2 rom to confirm this.
Click to expand...
Click to collapse
Nope, neither on 3G, nor plugged in... Used last.fm quite a lot in the past days and never experienced your troubles. It only runs on Wifi and mostly unplugged.

Very odd. Thanks anyway.
Maybe this is unique to rooted roms, then.
edit: all the roms I've used have had the wi-fi n patch, now that I think about it. Will see if I can find one that's unmodified.

That's a nice finding (about throttling speed). About n patch: it had problems from day one (and I don't need it), but I can't recall if the version of ieftm I installed has it. Any way to check it, or do you know if it was included from the start ?

Fixed. Did a full wipe and installed a rom that didn't have the wireless n patch. Problem gone.
Sibbi, thanks for posting. Wouldn't have occurred to me otherwise.
Anybody else experiencing an issue with streaming radio/podcasts over wi-fi while the screen is idle, you can grab a rom without the wireless n patch here:
http://android.modaco.com/content/h...-froyo-pre-rooted-no-hboot-with-radio-deodex/
Pick one of the 'with radio' roms. Odexed or deodexed doesn't matter. Make sure to do a full wipe first.

Nice ! Any way to remove the n patch without changing rom ?

Don't know. It could be as simple as extracting the rom and removing the patch, but I couldn't say.
If we could find out where exactly the N patch is and what it's called, I'd be willing to try it out.
You'd still have to wipe and reinstall though

I'll try to find the original n patch and see what changes in regards to modaco original rom

forum.xda-developers.com/showthread.php?t=707873&highlight=Wireless+patch
This was for 2.1, but it might just be the same hack ? It's a small hex edit and a file substitution (kernel module if I'm not mistaken). Will try it tomorrow if nobody does it in the meantime, too drunk right now ...

I'd be a bit wary of that tbh. I don't know enough to go messing around with it. Especially not at two in the morning, when I should already be in bed.
I did find this part interesting:
"Also in theory WiFi n will most prob drain more battery than WiFi g but in my zip's there is k newer firmware which is suppose to help in battery drain."
I wonder if the improvement to battery drain that he's talking about involved throttling down the wi-fi connection when the phone was idle?! Hmm.

Probably, will mess with it tomorrow after a sleep and a nandroid

[Q] AOSP roms and bluetooth

Hi, I was wondering if anybody has come up with a fix for AOSP roms for Bluetooth yet. Sense roms connect to my bluetooth stereo perfectly, but none of the AOSP roms (Cyanogen, ect.) can connect consistently.
The very odd issue is that yesterday I thought I came up with a solution, so I flashed CM7 on and tested. It worked. However I couldn't connect to the market because I forgot to install the gapps addon, so I did, and didn't think twice until last night when going to work, and bluetooth wouldn't work again. It seemed like the gapps addon broke bluetooth, but it could have been some unknown external factor. I can test this later today to see if the gapps addon does in fact kill it somehow.
Can anybody shine light on the bluetooth issues and maybe enlighten me as to a fix if there is one?

Not one response? That's disappointing. I was doing some testing with CM7 today and I could not reproduce the bluetooth breakage that I have experienced every other time. I was trying to isolate what was causing the issue by lashing the rom, then booting, testing, then flashing the RIL, booting, testing, then flashing the gapps package, booting, testing, then re-installing all apps one at a time from titanium backup (the same as I did before) and nothing broke it. Over a full day now and bluetooth is rock solid.
This poses a problem because I don't know WHY it is working. The only variable I actually changed is booting after each thing I flashed. This still will not change issues with any other AOSP roms even if the solution is to flash each separately, because the rest come with gapps installed, and they are broken both before and after a RIL flash.
Also to further convolute things, I started the day testing LeeDroid. Bluetooth would not connect. This is a rom that should have connected just fine.

Hi mrcandyman,
I too have noticed that a lot of AOSP roms have (imho) severe BT problems, mainly with connection to earpieces in my case (voice dialling). I have tried AOSP roms on both my desire and sgs2 and had the same problems on both. Flashing back to rooted stock roms has always cured my problems with BT. I am not a dev or programmer so have no idea what or where the problem lies only that stock roms I've tried don't have BT problems and AOSP do.
feeling your pain,
Night....

Bluetooth Only Connects ONCE!

This annoying problem popped out of nowhere I can think of.
Originally running AOKP #37. Since then I've tried all version of AOKP back to M5, wiping, formatting /system, CM9, faux123 16m, 17m, 18 b3. Each ROM the same problem.
I can connect to a media device once, either the car of speakers then a reboot is needed to [play] media again. The phone does show it being connected to the car but it's phone only.
If music is playing, through the phones speaker, and a call is placed the music plays [with] the call.
I've restored to AOKP b34 which seems to work, and totally wiped the phone to factory 4.02 which also seemed to work. Wiped flashed b37 back and was fine for a day.
I'm lost. It's annoying having to reboot at every 7-Eleven, gas station or Starbucks.

rinse and repeat? try a different rom? different kernel?

I rinsed and repeated constantly over the last week.
It's with all the ROMS I tried except for returning to stock, I think, I didn't keep it more than half a day and with AOKP b34 restored.
Oh, I had the "hybrid" radios, I've since installed 4.0.2 radios, 4.0.4 radios and am back to 4.02 thanks to returning to factory.
This is a VZ Galaxy Nexus.

I think I found my issue finally. I think a few more tests will confirm it's the MIUI permissions mod.

I've found the Bluetooth on the GN a bit buggy too. Though i manage to live with it.
When connecting to bluetooth devices i usually get the device to do the connection. If that doesnt work i just toggle Airplane mode on and off, and then it's working again.
If I manually turn off bluetooth it will end up hanging when turning on again.
After i switched to CM9 I think bluetooth overall is working a little better (might be placebo effect though).

The problem is definitely the MIUI permission mod.
Reinstalled it today and the issue returned immediately.
The stock Bluetooth system actually worked pretty good. from Nexus WAS controllable from the car stereo to an extent.

Bluetooth on 4.4.2 ROMs and KT747/Quantum kernel

I'm running the lates 3.21 quantum release with either the included kernel or using ktoonsez's kt747. Bluetooth issues were never an issue with 4.2.x ROM's but seem to be an issue on every ROM/Kernel I've found on the SGS3.
Does anyone know what the actual issue is? Seems like one driver worked possibly with the BMS kernel in early december but hasn't worked since.
I never get disconnects after connection, but once I turn off a bluetooth device I can't reconnect to it without a reboot.

I've been having a nightmare with bluetooth in my car.
It works flawlessly the first time - new connection, pair, works. Then if I disconnect by any method after that and try to reconnect, it spends about 10 minutes reconnecting and then is very sporadic and will disable/crash my phone. When my phone restarts, same thing unless I forget the pairing and recreate from scratch.

Official CM12.1 Nightlies for SGH-i747

CyanogenMod 12.1 is a free, community built distribution of Android 5.1.x (Lollipop) which greatly extends the capabilities of your phone.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
This is the support thread for CM12.1 on the AT&T Galaxy S3. All bug reports must be submitted with a log. Feature requests will be ignored, I only work to make the ROM stable on this phone, I do not work on major enhancements to the ROM itself.
Known issues:
Front camera does not work in some apps like Retrica and Instagram.
Install instructions:
1. Install TWRP Recovery for "d2att".
2. Download your correct, updated bootloader/modem. For the US variant you should be on NJ1.. Note that you must do MJB -> NE4 -> NJ1 in order. After MJB you can no longer downgrade your bootloader! Be warned if you are coming from earlier versions. See here and here for the files for the US d2att. I will add links for SGH-i747m if someone sends them to me.
3. Get the nightly build here.
4. Reboot into recovery and install both.
Follow the changelog!
http://www.cmxlog.com/12.1/d2att/
I stole the nice colors above from a post by @InfiniteCaffeine
XDA:DevDB Information
CyanogenMod for d2att, ROM for the AT&T Samsung Galaxy S III
Contributors
Nardholio, invisiblek
Source Code: https://github.com/CyanogenMod
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: NJ1 bootloader/modem
Based On: CyanogenMod
Version Information
Status: Nightly
Created 2015-05-05
Last Updated 2015-05-04

Reserved

Yahoo! First!!
Thanks for this! I hope this fixes the issue I have with Lollipop where when I hit the home button my device goes black except for the status bar!
Thanks!

I installed this and kept having issues with the keyboard not working at all. When I restored via nandroid to my stock setup, nothing worked. It was super whacky. I had to factory reset and restore everything via TiBu. Gonna try a newer nightly and see what happens.

slicetwo said:
I installed this and kept having issues with the keyboard not working at all. When I restored via nandroid to my stock setup, nothing worked. It was super whacky. I had to factory reset and restore everything via TiBu. Gonna try a newer nightly and see what happens.
Click to expand...
Click to collapse
In my side all working good except mobile network the slide all time off..see pic

bluetooth
ok so i dont know if im able to ask this or not but are all the features in this in the unofficial one my amf66
also is bluetooth working
just wondering
thanks
again sorry

So I got it working on my phone, but honestly, I kinda hate Lollipop. I don't like the notifications on my lockscreen instead of at the top in the status bar. I don't like the new animations (I turn all that **** off anyway). I'm not feeling the whole way the sound/alarms/notifications thing is going, either.
Guess I'll downgrade back to my 4.4.2 and be happy with how well things worked on there.

Works great
Installed the 20150504-NIGHTLY last night (dirty flash) and had no issues. No reboots. no signal drop. no camera problems. Thank you!

Hi,
Dirty flashed it over amf66's 4/28 version. It seems very stable, I had one reboot, but I'm sure it was because the phone was overheating (GPS + stuck in traffic + sunroof + warm sunny day).
The only concern I have is regarding bluetooth. It works very well, but the autoconnect fuction does not seem to work. I have to manually connect it (not pair, connect) every time. Once connected, it's smooooth.
This said, I tried to redo de pairing, with multiple devices, screen on / off, cleared "bluetooth sharing" data, etc.
Basically, I have two ways of using it:
Either I keep bluetooth off and turn it on when i'm near a device, it will connect right after turning it on. I can also leave it on and simply select my device when it is in range, and it will connect flawlessly. BUT, if for any reason, the device is turned off, the phone won't reconnect unless I do it manually.
Any thoughts? Anyone else? If i'm the only one with this problem, i'm probably good for a clean flash.

On the 05/05 build I had Dialer force close this morning that required a reboot before it would function again. Haven't gotten it to repeat since the reboot, although it did happen once just now when swiping in Dialer from the lockscreen. Also wanted to note that long press media controls are working again. It's been nonfunctional the past 3 or 4 builds and it's great to have them back!:good:

Aw, yeah. Official thread is a go!
Thanks for maintaining our trusty ol' S3, nardholio. This ROM runs even better than CM11 did on my phone.
I'll throw in a quick bug report, though. In all of these builds (including the unofficial ones) YouTube videos tend to freeze briefly about 8-10 seconds in. This happens with every video when viewed in the YouTube app, regardless of resolution or quality. I haven't noticed it happening with videos using the YouTube API in other apps such as Relay for Reddit.
That's pretty much the only issue I've ever had with these builds. They're pretty fantastic.

Hello guys,
Just a little update regarding the bluetooth issues. I did a clean flash, and it made it somehow better but not perfect. Now, as long as the screen is on or if there is something streaming, everything works well. But, if the phone screen is off, the bluetooth commands stop working (play, next...)...and they work fine if I turn the screen back on. Same goes for the auto connect, it does work when the screen is on, but won't connect if it isn't.
What I think is that the way lollipop acts when the phone is standby simply prevents the bluetooth app from updating it's status or recieving inbound commands. Now, the thing is that it used to work fine in previous builds (amf66 before 4/28 if I remember correctly), and that would mean that some setting was changed, probably in the CM source.
Once again, good job on maintaining our old devices, it really is appreciated.
And..no pressure here, just something I think would be worth looking into.
Dom

Try turning off ambient display for your Bluetooth issues. I'm thinking of permanently disabling it for the S3 anyway as it eats battery.

Nardholio said:
Try turning off ambient display for your Bluetooth issues. I'm thinking of permanently disabling it for the S3 anyway as it eats battery.
Click to expand...
Click to collapse
Tried it this morning, you are on the right track. Once connected, commands now work (phone, play/payse, next etc) even if the screen is off. But, I still have to connect it from the phone, and if the bluetooth device is turned off, it won't reconnect.
Thanks for the support! Are there any other functions that might prevent the phone from scanning for bluetooth devices?

Running the 5/4 nightly. Did the cleanest install possible - formatted through TWRP everthing on the phone, installed the ROM and gApps, then let the play store install all my apps. Everyting is running well for almost 4 hours now. Not a single reboot. Bluetooth has worked for several calls.
Issues I have noticed are -
1. Audio throug the car dock is broken. Once again, as has happened numerous times in the past on Cyanogen, the audio is not being routed through the dock with the phone is docked. I really hope this one gets fixed. Much of my phones use is inthe dock in the car.
2. Although the phone initially bootted with LTE working, it eventiually lost it. As has been noted elsewhere, removing all the other APNs and only leaving the one required for your particular provider fixes this.
3. Was getting pretty bad battery drain about 5-7% per hour at idle. Turned out that fixing the LTE issue as noted in #2 also fixed this issue. Somewhat surprising since the phone is almost always on Wi-Fi anyway. FWIW, I did not have wakelocks from Google Play. Battery concumption over the last hour of idle is only .9% per hour as reported by BBS.
So now, really only issue #1 remains!

jswclw said:
3. Was getting pretty bad battery drain about 5-7% per hour at idle. Turned out that fixing the LTE issue as noted in #2 also fixed this issue. Somewhat surprising since the phone is almost always on Wi-Fi anyway. FWIW, I did not have wakelocks from Google Play. Battery concumption over the last hour of idle is only .9% per hour as reported by BBS.
Click to expand...
Click to collapse
Which BBS version do you have working with android 5.1.1? I've tried a few of the betas with mixed results, but mostly FC's.

jason2678 said:
Which BBS version do you have working with android 5.1.1? I've tried a few of the betas with mixed results, but mostly FC's.
Click to expand...
Click to collapse
I used the latest BBS, 2.1b3 I believe. Also had to flash the helper app, then install BBS again. In the end, it does work.

Is it still recommended that we deny Google Play Services' Wake Up and Keep Awake permissions in Privacy Guard? I had them denied when I was rocking the earlier unofficial builds, but I have had them unblocked as of late. I didn't notice any difference at first, but not Google Play Services is my top battery drainer again.

I notice that I had the contacts repeated. Only one of the contacts had information.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app

does it works on the sgh-i747m ?