Related
So I had been on the beta version since it was released and participated a few times in the thread here: https://forum.xda-developers.com/pixel-xl/how-to/android-o-beta-issues-t3609335 and others were having the same issue.
The issue is no song/artist information being displayed on my touchscreen stereo, and I cannot use the stereo to pause/skip to the next track (I have to do it through my phone). Ive tried a local audio player, Google Music, and Pandora all to no avail. The deck is a Pioneer double-din AVH-P8400BH.
In my daily car, my phone bluetooth name appears and I can change song ect thru the deck. It is not a touchscreen and it probably 10 years old.
Ive gone into the bluetooth settings and have tried changing the AVRCP from 1.4 to 1.6 (neither work), and audio codec from default to enable optional (neither worked).
Anything else I should try out?
TIA
Please add your experiences to this website... they currently have over 100 replies of this issue and some other Bluetooth issues. https://productforums.google.com/fo...eDphsoOJ4;context-place=forum/phone-by-google
I had the same issue, but a simple unpair and forget from both devices then repair fixed my problem
marcjc said:
Please add your experiences to this website... they currently have over 100 replies of this issue and some other Bluetooth issues. https://productforums.google.com/fo...eDphsoOJ4;context-place=forum/phone-by-google
Click to expand...
Click to collapse
Ill throw in my comments, thanks for the link!
mjc2251 said:
I had the same issue, but a simple unpair and forget from both devices then repair fixed my problem
Click to expand...
Click to collapse
Ill have to give this a shot!
mine has awful streaming. It has so many skips...snags...audio blanks...whatever term you want to call it....its not "uninterrupted".
I was hoping google IMPROVED Bluetooth. I don't understand why they have this struggle to be honest. Its 2017....Bluetooth is not new technology.
Maybe they should stop expanding their department to provide data to the government to spy on private citizens using smart devices, and they would use those resources to fix bluetooth
Pioneer brand head units in particular I have seen Bluetooth streaming issues when paired to flagship model phones for years...even back as far as my LG G3. I got a Kenwood head unit instead, never had an issue.
As far a the Pixel XL and BT streaming...I have only had issues with dropouts zap sounds or pops, when i am out mowing my back property with my tractor...phone in pocket and BT headphones on. But my previous phones did this...most certainly due to the railroad nearby and high rise high voltage power lines and towers that are above me in that area.
speedingcheetah said:
Pioneer brand head units in particular I have seen Bluetooth streaming issues when paired to flagship model phones for years...even back as far as my LG G3. I got a Kenwood head unit instead, never had an issue.
As far a the Pixel XL and BT streaming...I have only had issues with dropouts zap sounds or pops, when i am out mowing my back property with my tractor...phone in pocket and BT headphones on. But my previous phones did this...most certainly due to the railroad nearby and high rise high voltage power lines and towers that are above me in that area.
Click to expand...
Click to collapse
Pioneer uses a cheaper bluetooth and never updates the firmware of the chips to fully support the available Bluetooth profiles even when they are developing their units and new profile updates are available. I have had a very long and annoying history with them to the point where I was in direct contact with their build team after all my complaining. That was back in 2012. Never used another of their products again. :good:
I have the same issue on my Chevy Colorado 2017. Everything works fine on Spotify on my Huawei Mate 9, and iPhone 7. It also worked fine on 7.1.2. Spotify works and music comes through but no info is displayed. I unpaired both things with no success. Frustraring.
I tried unpairing mine as well, no luck either
stupidchicken03 said:
I tried unpairing mine as well, no luck either
Click to expand...
Click to collapse
Have you tried unticking "media" in the profile hitting ok, going back in and ticking media again?
pcriz said:
Have you tried unticking "media" in the profile hitting ok, going back in and ticking media again?
Click to expand...
Click to collapse
I have not. Ill give it a shot today.
No idea if this problem is related or not but might be worth a check if you have time. First time I put Oreo on my phone it was fine. Then I screwed something up and just ADB flashed the image again. Everything was fine until I tried bluetooth a few days later. It wouldn't connect until ticking that media box many times. Then I flashed the image again and it worked fine again.
So I just got the 8.0 OTA (not on beta). I see in the dev options that it shows what BT codec it is using.
I have noticed that only the option "Bluetooth AVRCP Version:" is the only value that changin it does it stick. The other setting appear to be on auto and revert to auto depending on what device u pair supports.
My first test on my Kenwood KDC-BT762HD it paired fine and it said it was using AptX. Streamed for a few min fine. Then after I got back in the car and it auto paired, music started skipping every several seconds. I turned radio off then on to repair it and it started streaming fine again....but was using SBC according to Dev options.
When I changed AVRCP version to 1.6.....it connects and uses AptX fine. However, the radio display no longer displays the BT media metadata(title/artist), but the controls on the radio still work. I change to AVRCP ver 1.4 and that restores metadata, but then it uses SBC again. (using ver 1.5 results in SBC and no metadata).
I don't really care about the song info not being displayed on my radio....but definitely seems to be something fishy with BT in this new update.
EDIT Update: so now I am noticing it auto re-connecting and using SBC all the time now. WOnt use aptX unless i delete the device and re-pair it. then it works for a few reconnects, but then drops to sbc cagin.
Thanks for posting, I won't be updating. The Bluetooth has never been right and now seems to have regressed.
Sent from my SM-T280 using Tapatalk
i think i'm having slightly fewer drop outs with oreo than with nougat. my moto x pure on marshmallow was really bad.
FZ1Darren said:
i think i'm having slightly fewer drop outs with oreo than with nougat..
Click to expand...
Click to collapse
i agree and although i dont get the proper song listing on my car stereo it seems everything else is better. on nougat my BT headset i use for work all day (moto buds) would often stop connecting properly and i would make a call and have to select "phone" then "headset" again to get audio back on headset and om Oreo it happens less frequently
fletch33 said:
i agree and although i dont get the proper song listing on my car stereo it seems everything else is better. on nougat my BT headset i use for work all day (moto buds) would often stop connecting properly and i would make a call and have to select "phone" then "headset" again to get audio back on headset and om Oreo it happens less frequently
Click to expand...
Click to collapse
If you switch to a rom that uses the CAF based bluetooth (all lineageos based ones should, crDroid does for sure as that is what I use) implementation this won't happen. Still haven't been able to track down exactly why, but for now I'm sticking with CAF based ROMs to avoid this.
Do any of you guys having this issue have an Android wear watch? I've had heaps of issues with Bluetooth streaming being all "jittery" and just skipping since the update. However, I found this is basically completely fixed when I turn my android wear (LG urbane) off, or at least the Bluetooth on it.
Tried all the developer options for BT but hasn't made a difference. At the moment, my solution is turning off BT on my watch when I'm listening to music. Bit crap but it works.
I have factory reset the watch and cleared BT cache on pixel.
Any other ideas?
Is anyone else still having problems with Bluetooth on Oreo? I was hoping the official 8.1 release would help me, but I'm seeing no change. I have a Kenwood BT952HD, and experience issues similar to what the OP describes. Audio is plays fine, no unreasonable stuttering. But I get no song info, and can't skip tracks. Also, the pairing isn't as automatic. Every time I turn on the car, I have to wake the phone up, and wait for the pairing to complete, which takes longer than usual.
I've tried playing with the AVRCP settings, along with clearing registrations at both ends and repairing, with no luck. Is anyone else still seeing similar issues?
8.1 working fine with my Kenwood BT762HD. I use PowerAmp v2 alpha build 704 app.
I keep on setting the audio bluetooth codec under dev optioons on "aptx" but after exiting the option goes back on "default".
Anyone can help?
thegios said:
I keep on setting the audio bluetooth codec under dev optioons on "aptx" but after exiting the option goes back on "default". Anyone can help?
Click to expand...
Click to collapse
Mine doesn't appear to stick either, but when I use my BT speaker I see an option in the connect dialog to use the Qualcomm aptX driver even though the codec is set to default (SBC). I don't see this aptX option when using my car or earbuds. I know this doesn't really help much, but I thought it was relative. I do know that the AVRCP setting does stick. Have you looked in the Google Issue Tracker? I'll go and star the issue if I can find it.
Edit: It is THERE listed as closed due to lack of data, feedback. Seems they ignored the obvious.... codec selection not sticking?
How do you tell if aptx is working while you're playing something to say a wireless speaker?
Sent from my Pixel 2 XL using Tapatalk
pixelsquish said:
How do you tell if aptx is working while you're playing something to say a wireless speaker?
Click to expand...
Click to collapse
In BT settings I see a toggle for Qualcomm aptX and it's on... but in Dev Ops the BT codec still says Default: SBC. I think the audio codec setting there is busted, but the phone seems to use the best available codec. The device is a Creative (Soundblaster) Roar BT speaker. Now if I could only get the phone to auto connect to my car kit. Stays paired but will only manually connect which is a real pain.
v12xke said:
In BT settings I see a toggle for Qualcomm aptX and it's on... but in Dev Ops the BT codec still says Default: SBC. I think the audio codec setting there is busted, but the phone seems to use the best available codec. The device is a Creative (Soundblaster) Roar BT speaker. Now if I could only get the phone to auto connect to my car kit. Stays paired but will only manually connect which is a real pain.
Click to expand...
Click to collapse
Hmmm. My JBL Flip 4 is paired and it can use aptx but no option there. Weird.
My fm transmitter car kit will connect automatically, as long as it's set for media and phone calls.. Is yours just set for media only?
pixelsquish said:
Hmmm. My JBL Flip 4 is paired and it can use aptx but no option there. Weird.
My fm transmitter car kit will connect automatically, as long as it's set for media and phone calls.. Is yours just set for media only?
Click to expand...
Click to collapse
Yes, I've tried every combination there. It was working perfect with the N6P, and has never worked with the P2XL. Car kit is the absolute cheapest Chinese one you can find on Ebay... audio only, BT version 2.0 I think with no phone mic lol. Time to pony up and get a newer/better one. Had not considered FM transmitter because my car has the line in AUX. in my console so I can hide it.... It's about the size of a matchbox. This is a first world problem I know, but really annoying to me, and I know it's the phone because the Nexus was working for a year no problems. Thanks for your response.
v12xke said:
Yes, I've tried every combination there. It was working perfect with the N6P, and has never worked with the P2XL. Car kit is the absolute cheapest Chinese one you can find on Ebay... audio only, BT version 2.0 I think with no phone mic lol. Time to pony up and get a newer/better one. Had not considered FM transmitter because my car has the line in AUX. in my console so I can hide it.... It's about the size of a matchbox. This is a first world problem I know, but really annoying to me, and I know it's the phone because the Nexus was working for a year no problems. Thanks for your response.
Click to expand...
Click to collapse
We are both very frustrated here. Me cause I know I have an aptx capable device and am not getting to use it. You because you can't do a simple auto connect via bluetooth. Oy! Come on January update!
see my post here for a similar issue that I was able to workaround fairly easy
TLDR: You need root, edit your build.prop (using text editor, some app from the play store, etc) and change the following key: persist.vendor.bt.a2dp_offload_cap
by removing -aac from the string.
I'm sorry if it looks like I'm spamming I just encountered this issue on a lot of forums with no result and I do hope that this will help some
Hello. I change phones alot and have noticed that some phones(all android) have better bluetooth playback than others.
I had a oneplus 7 pro before this phone and the bluetooth quality to my truck was great and had no issues but with this phone the highs sounds scratchy or like if the speaker is bad. But if i connect it with a wire connection it sounds great. Everything with the 2 phones is the same. On both i was using the galaxy watch and pretty much the same apps. On a previous phone the note 8 i had the same issue but it was a different car. Seems like its the way samsung handles bluetooth.
Has anyone had this issue? If so was there a fix?
Thanks
make sure not on mic
Sent from my SM-N975F using Tapatalk
jemfalor said:
make sure not on mic
Sent from my SM-N975F using Tapatalk
Click to expand...
Click to collapse
What do you mean?
The only two things I think about is the codec used that may be different across devices, and the Bluetooth settings that sync the phones volume with the headset (the differences are noticeable).
Since no DAC is used in Bluetooth, I don't think it can comes from them, for a same headset.
On Samsung phones you should run the adapt sound process. Try this.
I tried with the sync volume off too and no improvement.
I looked for the adapt sound and my phone doesn't have that setting. Or is it something different?
It's in Sounds and Vibration 》 Advanced Sound settings 》Sound Quality and effects 》 Adapt sound
You have to do this in a quiet place and ensure to answer honestly. If you can't hear the beeping press no.
After doing this the sound quality is night and day difference.
Ok found it. Ill play with it a bit. Thanks
I've had issues sometimes with audio being piped through the "Calls" Bluetooth channel versus the "Audio" channel so worth checking as the quality is obviously night and day.
I also like enabling Dolby Atmos on my Note 10+ for music so worth playing with too. Additionally, I recently found Samsung's Sound Assistant app which let's you customize a bunch of sound settings so worth checking out as well:
https://play.google.com/store/apps/details?id=com.samsung.android.soundassistant
sansnil said:
I've had issues sometimes with audio being piped through the "Calls" Bluetooth channel versus the "Audio" channel so worth checking as the quality is obviously night and day.
I also like enabling Dolby Atmos on my Note 10+ for music so worth playing with too. Additionally, I recently found Samsung's Sound Assistant app which let's you customize a bunch of sound settings so worth checking out as well:
https://play.google.com/store/apps/details?id=com.samsung.android.soundassistant
Click to expand...
Click to collapse
Is there an easy way to tell if the audio is going through the call channel?
ErickF said:
Is there an easy way to tell if the audio is going through the call channel?
Click to expand...
Click to collapse
Easiest is probably just uncheck calls in your phones BT settings for your truck (and make sure audio is enabled). If the sound is still not great then this isn't the issue.
Sorry to respond to an old thread, but I was wondering if any of this fixed the OP's problem. I followed all the recommendations here and on other threads but have not been able to solve my recent Bluetooth audio problem. The sound has been terrible lately.
Same issue here on my s10+. When playing any audio in my car via BT i hear the distortion/hissing noise especially when the song has a higher treble frequency.
I have just about tried all fixes i could find on Google, and no luck.
When connecting to my ear buds (Jabra Elite 65t) it disappears and checked in developer mode that it supports to AAC for BT Codecs.
But when connecting to the car it reverts to SBC.
The issue clearly lies on Samsungs side, as my brother has a Huawei p30 Pro, also has bluetooth 5 and plays amazingly well in all aspects (Bass-Mids-Treble).
I know I'm posting this almost a year later, but i am desperately looking for a fix.
SN. I have recently updated my phone to Android 10, despite all the complaints to Samsung from many users... Sadly this issue has not being fixed on my side.
From what i see online, people have given up on Samsung and opted for Rooting their Samsungs and installing Viper4Andriod.
Has any one done this and can confirm that it fixed the issue?
Hello everyone.
Since 2 months I know have this "strange" phenomenon that when I connect my Realme 6 Pro to my Bluetooth sound device of my choice, for the first few times connecting there are only popping/cracking noise sounds coming out. No music or anything relatable. After connecting around 5-10 times, it finally will play music (also it suddenly goes back to the cracking state when clicking around in youtube).
Bonus: most of the time (even if connected right and playing music) the microphone wont work in calls.
I cant fix this sh*t and it really bothers me a lot lately.
Hopefully someone can help, or else I´m going to throw this phone into the trash can... xD
Greetings.
My BT works fine for the most part, but sometimes it breaks up. I am really hoping it's just a software issue
Me too, for about 2 or 3 months now. Wasn't a problem before. Thinking I'll try factory reset soon, see if that fixes it.
Hey! I also have this problem and what i found is, if your Bluetooth audio support Aptx codec, it will enable option "Use High Quality Audio" in your audio bluetooth settings. Try to disable (it will use SBC Codec) and my problem disappear.
But, it really annoying. I already try my bluetooth audio with another phone and it worked fine with Aptx, so i know my bluetooth audio is not my problem. My workaround so far are disable high quality audio, then enable Aptx manually in developer options with AVCRP 1.6
Not sure if my device actually using SBC codec or Aptx after change it manually on developer options
Hi All! I solved problems with Bluetooth by switch off Dolby Atmos!
HeavyBrownCat said:
Hey! I also have this problem and what i found is, if your Bluetooth audio support Aptx codec, it will enable option "Use High Quality Audio" in your audio bluetooth settings. Try to disable (it will use SBC Codec) and my problem disappear.
But, it really annoying. I already try my bluetooth audio with another phone and it worked fine with Aptx, so i know my bluetooth audio is not my problem. My workaround so far are disable high quality audio, then enable Aptx manually in developer options with AVCRP 1.6
Not sure if my device actually using SBC codec or Aptx after change it manually on developer options
Click to expand...
Click to collapse
Hi! I solved problems with Bluetooth by switch off Dolby Atmos!
Hello there fellow Xiaomi users, I have a problem with my Bluetooth earbuds and it's driving me insane! I hope you can help me out. When I connected my newly purchased bluetooth sony earbuds (the model is WF-XB700) I noticed that the volume was really low, maybe 50% less than it should've been. I was perplexed, but had a couple of quick ways to determine the problem. I connected the earplugs to a Iphone 8 and they worked just fine, 100% of their capacity. Then I connected my Xiaomi Mi 2A lite to some other bluetooth headphones (model Pioneer se-ms7bt) and they also worked as they should've. Then I connected the earbuds to a Xiaomi Mi A3 and to my surprise, I could also detect the Low Volume Issue there too! So, it must be something Android/Xiaomi related.
Then I went on a really energy draining odyssey on google to find a solution. What I did find was, firsty, that it was a known issue and secondly, that the myriad of solutions presented did not help me at all. This is a list of the things I tried, some of which spawned problems too :
1) Disabling absolute volume in developer settings.
2) Tinkering with all the options in the develper option - even the following (I will copy paste in from an other thread , which according to many people has worked :
Enable Developer Options (options -> system -> about phone -> click build number 7 times)
Press back
Go to settings, and search AVRCP.
Click on Bluetooth AVRCP Version and ensure it is on 1.6.
Next, search for Absolute
Select Disable Absolute Volume and turn this toggle on, if it isn't already.
Unpair all Bluetooth devices. Restart your device. Pair the devices again. To the right of each Paired Bluetooth device in the Bluetooth settings page is a gear icon, go into each device and turn off the Phone Calls toggle, leaving only Media audio enabled.
Exit settings, connect to the Bluetooth device, start playing something. Increase the volume using the volume up button and rejoice as the volume goes as loud as you need!!!
3) Putting the volume up in the Sony Headphones app. - So, officially the app doesn't support the WF-XB700. There are two options for detection. The first is a list of the supported devices (mine is not there) and the other is a ,,detect via bluetooth''. Tried the second option but it doesn't work
4) Increasing the volume on the physical buttons on the device. Mine are earbuds and have only one button for on/off
5) Ensuring the eartips are tightly fit in my ear.
6) Making sure the earbud isn't blocked by anything.
7) Resetting the phone
8) Changing the Region - This I actually did not succeed in doing. It turns out that the option to change the region has been removed. If there is a way to do it, please inform me.
9) Trying all the volume booster apps in the store.
10) Restart or enable and disable airplane mode
11) Forgeting and pairing the device again
Could the bluetooth version difference be the problem. Mine is 4.2 and the buds are 5.0. According to google there should't be a difference regarding the sound volume/quality, only range and connection strenght. Please help me, I have wasted more than five hours already and I ran out of options to try. Thanks in advance !
My current software version : Android 10 / Security patch level: October 1,2020 / Baseband version 953_GEN_PACK-1/ Kernel version: 3.18.124-perf-gceec2f0 /
Xiaomi removes Bluetooth codecs intentionally from this phone (and seems like from Mi A3 too). Because Xiaomi dont want to pay 1$ fee for codec. Thats why it works as expected on iPhone. It's all about greediness.
Same codec issue is proper on Miui roms too. This means Redmi 6 Pro has an Bluetooth codec issue too. We can probably say same thing (according to ur first post) for Mi A3 and for its Miui version Xiaomi Mi CC9e.
- Redmi 6 Pro
- Xiaomi Mi A2 Lite
- Xiaomi Mi A3
- Xiaomi Mi CC9e
All of them probably has same issue. I didnt use any flagship of Xiaomi or any other Android phone since Jelly Bean so cant say anything about other brands except Apple. I used an iPhone between those times. iPhones has proper bluetooth codecs. You cant fix it via resetting ur phone or something like that.
SBC is the default codec and none of others will work.
Qualcomm is the owner of these aptX, aptX LL, aptX HD, aptX Adaptive audio codecs. We have an qualcomm chipset on our phone too but xiaomi didnt want to pay for these to earn more money from us. So thats why we are stuck on SBC. Dont buy any android device just by looking its specs from websites. Check out everything in the shop (bluetooth, camera,..etc.) before buy.
AndreyTsvetkov said:
Hello there fellow Xiaomi users, I have a problem with my Bluetooth earbuds and it's driving me insane! I hope you can help me out. When I connected my newly purchased bluetooth sony earbuds (the model is WF-XB700) I noticed that the volume was really low, maybe 50% less than it should've been. I was perplexed, but had a couple of quick ways to determine the problem. I connected the earplugs to a Iphone 8 and they worked just fine, 100% of their capacity. Then I connected my Xiaomi Mi 2A lite to some other bluetooth headphones (model Pioneer se-ms7bt) and they also worked as they should've. Then I connected the earbuds to a Xiaomi Mi A3 and to my surprise, I could also detect the Low Volume Issue there too! So, it must be something Android/Xiaomi related.
Then I went on a really energy draining odyssey on google to find a solution. What I did find was, firsty, that it was a known issue and secondly, that the myriad of solutions presented did not help me at all. This is a list of the things I tried, some of which spawned problems too :
1) Disabling absolute volume in developer settings.
2) Tinkering with all the options in the develper option - even the following (I will copy paste in from an other thread , which according to many people has worked :
Enable Developer Options (options -> system -> about phone -> click build number 7 times)
Press back
Go to settings, and search AVRCP.
Click on Bluetooth AVRCP Version and ensure it is on 1.6.
Next, search for Absolute
Select Disable Absolute Volume and turn this toggle on, if it isn't already.
Unpair all Bluetooth devices. Restart your device. Pair the devices again. To the right of each Paired Bluetooth device in the Bluetooth settings page is a gear icon, go into each device and turn off the Phone Calls toggle, leaving only Media audio enabled.
Exit settings, connect to the Bluetooth device, start playing something. Increase the volume using the volume up button and rejoice as the volume goes as loud as you need!!!
3) Putting the volume up in the Sony Headphones app. - So, officially the app doesn't support the WF-XB700. There are two options for detection. The first is a list of the supported devices (mine is not there) and the other is a ,,detect via bluetooth''. Tried the second option but it doesn't work
4) Increasing the volume on the physical buttons on the device. Mine are earbuds and have only one button for on/off
5) Ensuring the eartips are tightly fit in my ear.
6) Making sure the earbud isn't blocked by anything.
7) Resetting the phone
8) Changing the Region - This I actually did not succeed in doing. It turns out that the option to change the region has been removed. If there is a way to do it, please inform me.
9) Trying all the volume booster apps in the store.
10) Restart or enable and disable airplane mode
11) Forgeting and pairing the device again
Could the bluetooth version difference be the problem. Mine is 4.2 and the buds are 5.0. According to google there should't be a difference regarding the sound volume/quality, only range and connection strenght. Please help me, I have wasted more than five hours already and I ran out of options to try. Thanks in advance !
My current software version : Android 10 / Security patch level: October 1,2020 / Baseband version 953_GEN_PACK-1/ Kernel version: 3.18.124-perf-gceec2f0 /
Click to expand...
Click to collapse
that's the same problem i am facing on my redmi note 5/5 Plus (Vince) got any solution? or should i change my phone
perfect_ said:
Xiaomi removes Bluetooth codecs intentionally from this phone (and seems like from Mi A3 too). Because Xiaomi dont want to pay 1$ fee for codec. Thats why it works as expected on iPhone. It's all about greediness.
Same codec issue is proper on Miui roms too. This means Redmi 6 Pro has an Bluetooth codec issue too. We can probably say same thing (according to ur first post) for Mi A3 and for its Miui version Xiaomi Mi CC9e.
- Redmi 6 Pro
- Xiaomi Mi A2 Lite
- Xiaomi Mi A3
- Xiaomi Mi CC9e
All of them probably has same issue. I didnt use any flagship of Xiaomi or any other Android phone since Jelly Bean so cant say anything about other brands except Apple. I used an iPhone between those times. iPhones has proper bluetooth codecs. You cant fix it via resetting ur phone or something like that.
SBC is the default codec and none of others will work.
Qualcomm is the owner of these aptX, aptX LL, aptX HD, aptX Adaptive audio codecs. We have an qualcomm chipset on our phone too but xiaomi didnt want to pay for these to earn more money from us. So thats why we are stuck on SBC. Dont buy any android device just by looking its specs from websites. Check out everything in the shop (bluetooth, camera,..etc.) before buy.
Click to expand...
Click to collapse
They are literally making 1$ per phone. Stop spreading missinformation