Related
I have a JVC head unit in my car paired up to my Galaxy S III, and no matter what I do (tried a different SIII, resets, different music apps, etc.) the Bluetooth drops when I go to skip tracks from the radio (AVRCP). I have been forced to go to the CM10 ROM to get a reliable connection (although I'm stuck on a build from about a month ago, as some Bluetooth bugs have introduced there as well). Anyway, I'm eyeing up the Note II, but I'm wondering if anyone can confirm/deny if the Note II (stock ROM) has a different Bluetooth driver than the SIII. I hate to say it, but I actually really like Samsung's new interface, but the Bluetooth issue I'm having is a deal breaker. The other question is if anyone knows if the 4.1 update coming out for the SIII will have the same BT driver as 4.0.
Thanks!
had you ever flashed the KT747 kernel on the stock ROM of your s3? it changes the WiFi and Bluetooth drivers.
OR, if you haven't, maybe give it a try since it changes the WiFi and Bluetooth drivers.
Russ77 said:
had you ever flashed the KT747 kernel on the stock ROM of your s3? it changes the WiFi and Bluetooth drivers.
OR, if you haven't, maybe give it a try since it changes the WiFi and Bluetooth drivers.
Click to expand...
Click to collapse
I have not tried that. I would prefer to keep it stock, but that's something to try.
I thought I was the only one with this issue. I can relate as well . I too have a JVC unit and also experience the same bug on JB TW Rom. It tends to disconnect after I skip a few tracks and reconnects again . It does F*** up the mood when jamming to your music. At the moment im trying a different kernel to see if it does the same. But like you said CM10 doesn't disconnect.
Sent from my SGH-T999 using xda premium
J-ROCK said:
I thought I was the only one with this issue. I can relate as well . I too have a JVC unit and also experience the same bug on JB TW Rom. It tends to disconnect after I skip a few tracks and reconnects again . It does F*** up the mood when jamming to your music. At the moment im trying a different kernel to see if it does the same. But like you said CM10 doesn't disconnect.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I emailed JVC on it, and they gave me the whole "did you try a reset" business... Infuriating. At this point I just want a stock ROM that works. My S & S II worked perfect on the same head unit...
How can you tell if the stock S III and Note II use the same BT driver? Oh, and let me know what your experience is with the new kernel.
It's a few more days until Jelly Bean is released. There are changes to the Bluetooth stack in Jelly Bean. I'd wait and give that a try before getting a new phone.
I had the same problem on my JVC receiver. Had the issue with Task's ROM too. Would happen when you skip through the songs fast. I switched to an Alpine deck and it still has slight issues but not as much. I also have an issue of it disconnecting and reconnecting right after I make a call. Hopefully Monday will bring a fix for us Canadians.
Sent from my SGH-I747M using xda app-developers app
Bluetooth has been messed up on the S3 from day one. I think it's an ICS issue because my gf's OneX has the same issues. I have a Mercedes B200 and I can't get sound through the car's speakers at all. Tried a bunch of different ROMs and kernels, including some JB (4.1) builds, all to no avail. I'm at this point waiting for 4.2.
I dont see any problems with my SG3 connecting my hyundai sonata car(2013 model) and honda CRV via bluetooth. No problems playing songs, phone calls and Google navigation.
Same phone didn't work with kia soronto SUV.
I feel the car bluetooth software has issues, not the phone software.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
nani4215 said:
I dont see any problems with my SG3 connecting my hyundai sonata car(2013 model) and honda CRV via bluetooth. No problems playing songs, phone calls and Google navigation.
Same phone didn't work with kia soronto SUV.
I feel the car bluetooth software has issues, not the phone software.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Click to expand...
Click to collapse
It could be, but I've used a Captivate, Infuse, & S2 on the same radios (two different JVC decks), and they've all worked perfect. Those all had stock ROMs (to start). I flashed CM9 and then CM10 on the Captivate & SII, and they still worked perfect. The only phone (stock/not stock ROM) that has ever had problems for me is the S3. My gut tells me it's a problem with the Bluetooth stack on the stock ROM, seeing as BT on CM9/CM10 works perfect on the S3 (other than the bass-less sound bug on the "stable" release and after - nice "stable" release).
Somebody on XDA should start hacking the software on these touchscreen head-units (they are update-able :good, then I'll be impressed.
Note 2 BT
Anyway, has anyone tried a Note 2 on one of the radios you had problems with? If not, I might try a re-post over in the Note 2 forum...
rytymu said:
Anyway, has anyone tried a Note 2 on one of the radios you had problems with? If not, I might try a re-post over in the Note 2 forum...
Click to expand...
Click to collapse
Well I bought a Note 2, SAME DAMN PROBLEM! I'm 95% sure I'm returning it, the only other option is to buy a different head unit. Anyone else have a GS3 and an aftermarket radio that DOESN'T drop the bluetooth connection when skipping tracks?
rytymu said:
Well I bought a Note 2, SAME DAMN PROBLEM! I'm 95% sure I'm returning it, the only other option is to buy a different head unit. Anyone else have a GS3 and an aftermarket radio that DOESN'T drop the bluetooth connection when skipping tracks?
Click to expand...
Click to collapse
i have a kenwood ddx 418 and ive got no issues with bluetooth, best bet would be to go to a bestbuy and try out the display units there imho
Bluetooth audio for music and calls works fine with my Ford Edge...however there is no track information (avrcp) sent to the headunit which is annoying. No change with the Jellybean update either.
mixxy said:
i have a kenwood ddx 418 and ive got no issues with bluetooth, best bet would be to go to a bestbuy and try out the display units there imho
Click to expand...
Click to collapse
funkydude101 said:
Bluetooth audio for music and calls works fine with my Ford Edge...however there is no track information (avrcp) sent to the headunit which is annoying. No change with the Jellybean update either.
Click to expand...
Click to collapse
But are both of you running bone-stock ROMs? If so, I may have to start looking at radios again.
Returned it. I guess that's a $35 experiment (thank you AT&T for the restocking fee). Either the Sammy BT stack is too advanced for my basic A2DP radio (as in ALL BT radios), or the Sammy BT stack is just horribly developed (which I've come to believe is true). Now I just have to wait for an apt-x head unit to come out, then I can try this experiment again...
Hi
Basically I have noticed that the sound quality when using bluetooth headphones on 4.3 is noticeably lower than 4.1.2. From what I remember from my Nexus 4, the 4.3 rom had a lower bitrate bluetooth binaries and these were sorted out in 4.4.
Does anyone know of a way to sort this out for the Note? The fix I used on the Nexus does not work on this phone. It's quite irritating if truth be told.
Cheers for any help
Blimey... Has no one noticed the utter cack sound quality on bluetooth since the update?
Sent from my GT-N7105 using Tapatalk
I'm interested in this as well.
I went straight for 4.3 when i got my note 2 (without knox crap so i could downgrade) and yesterday i received my BT S Pen (HM5100) and i'm not satisfied at all with the quality now i dont know whether it is because of the S Pen itself or if the Bluetooth Connection is poor.
Right now i dont have time to downgrade to 4.1.2 and test it out so if anyone could shed some light on this i would appreciate it.
peterhugelberg said:
I'm interested in this as well.
I went straight for 4.3 when i got my note 2 (without knox crap so i could downgrade) and yesterday i received my BT S Pen (HM5100) and i'm not satisfied at all with the quality now i dont know whether it is because of the S Pen itself or if the Bluetooth Connection is poor.
Right now i dont have time to downgrade to 4.1.2 and test it out so if anyone could shed some light on this i would appreciate it.
Click to expand...
Click to collapse
Hopefully someone has a solution
I tried replacing the A2DP bluetooth file using root explorer with the one from 4.1.2. Also tried replacing it with the KitKat one from my Nexus 4. They either literally broke bluetooth or just didn't make a difference in sound quality.
Hoping this can be sorted sometime soon because I've been unhappy with my phone for a while now and don't really fancy waiting for Kit Kat. There's more likelyhood of me buying a HTC One before this problem ever gets solved.
Hope I'm wrong.
Hey everyone. I made this topic just to discover who regrey buying LG G4 and the reason why they regret. If they dont regret then please let us know.
Sent from my LG-H818 using Tapatalk
Why?.I have it since a week and the phone is great,perfect.As an ex M9 user,the G4 is better IMO.
Waiting for 6.0.
No regrets after more than 4 months, you need a BT earphones for music as the 3.5mm is too low and some HTC ported apps to have a perfect UI (thanks Xpirt)
I didn't regret, but I do wish some things could be better (UI & Battery Life). Other than those, I've been relatively happy with my decision.
However, I installed the Resurrection Remix ROM last week and battery life is definitely better and the AOSP UI + CM13 theme engine is 100 times better than stock.
lastsamuraial said:
Why?.I have it since a week and the phone is great,perfect.As an ex M9 user,the G4 is better IMO.
Waiting for 6.0.
Click to expand...
Click to collapse
Which variant are you using? For most devices 6.0 is out there and you can manually install it (With or without root )
EDIT: To answer your question: No ragrets. Not even an "a" for an "e" :laugh: Best phone out there.
Came from a Note 4, love the G4 (stock) the most! Not as much bloat and nonsense as the note 4
I sold my G4 just for modding. I like to mod and unfortunately G4 have a small community. Good luck , best 2015 phone if you dont mind to be on stock.
only thing i regret about the G4 is the inability of most G4 variants to have an official unlocked bootloader ughh damn LG
I regret it and also not. I owned at least half a dozen android phones in the past two years, and the LG was the real bang for the buck with a very great camera. However, this was the only phone I had serious issues with.
H815 - First unit came with the display acting up (stuck pixel clusters), and finally RMAd it, when the motherboard died. I received it back repaired (PCB changed), but the display is now worse than before, the problem is, that it only shows after a few minutes of usage and probably they did not notice it. Stuck pixels + different brightness levels around the stuck pixel area. RMAing it again...
I don't really regret buying it, but if I were given the option again, I wouldn't chose G4.
My LG G4 is flawless. Battery is OK, no bootloops, no stutters/lags, etc. However, I bought it right after it was put in the market for a not-so-budget price and, for my needs, an S6 would've be better suited.
I mean... don't get me wrong. But as far as I don't need a spare battery/expandable storage, S6 would be a better choice. I just got tempted for the 5,5 screen and camera.
Follow_and_Feel said:
Which variant are you using? For most devices 6.0 is out there and you can manually install it (With or without root )
EDIT: To answer your question: No ragrets. Not even an "a" for an "e" :laugh: Best phone out there.
Came from a Note 4, love the G4 (stock) the most! Not as much bloat and nonsense as the note 4
Click to expand...
Click to collapse
Im using H815T.My phone just boot up after flashing V20B KDZ with LGUP.6.0 looks smoother than LP.With V20C after restart comes up an error,but this error is not present with V20B.
Sorry,my english is not the best,that's why i do some errors.
I regret because I have weirdo half screen touch problem, it becomes crazy, but it's not a real problem, but there's still a problem so... and I don't have time to send it back, It does not have fingerprint sensor which is a shame for a 2015 flagship and it's plastic, we need some metal with leather...
But I bought it because of his camera, that's it.
have it for 6 months now (it is my only phone)
I regret:
- bad battery life (no more than 3h SOT)
- no unlocked bootloader / dead development scene (only a handful of ROMs, most are buggy and almost all of them are for H815 eu only models)
- bad sound over the earphones (really weak)
- no fingerprint reader (when all the other flagships have one)
- features that are essentially broken (still to this day), like tap to unlock
Lg v10 hands down would have been much better to have but lg g4 is still a great phone non the less
Overall i do regret.
I really liked the phone camera (front and back), screen, design and the option to remove battery and insert an sd card if needed.
But as i said before i never buy an LG smartphone again. They unlock the bootloader for just a single model and thats it. I like to customize and install mods on my phones, mainly to make it better, faster and that stuff, but my H815P cant be unlocked, and now here i am with a "Porsche that can't past 60mph"
Yet on the bad side, battery is not the best, some bugs even on the stock rom, and etc.
LG, never again. I prefer a not so good phone but that i can do whatever i want than this. Note 5 is the target now.
lastsamuraial said:
Im using H815T.My phone just boot up after flashing V20B KDZ with LGUP.6.0 looks smoother than LP.With V20C after restart comes up an error,but this error is not present with V20B.
Sorry,my english is not the best,that's why i do some errors.
Click to expand...
Click to collapse
No problem So you're already on Marshmallow? Because you said you'd wait for it :laugh: But ok. Marshmallow's pretty nice Love it
Follow_and_Feel said:
No problem So you're already on Marshmallow? Because you said you'd wait for it :laugh: But ok. Marshmallow's pretty nice Love it
Click to expand...
Click to collapse
I was waiting for OTA or update to come through Bridge and couldnt wait more,so i used V20B KDZ and it's done with LGUP.Very smooth really.
regret and disappoint , all about the bootloader
I do ..because of the locked bootloader and i have g815p and i still didnt get MM
I moved to the V10 and I don't regret getting the G4 at all...because I still have it
These are similar phones spec-wise but in hand they are obviously quite different. I've had the G4 since July and just got the V10 a couple of weeks ago.
Already I keep trying to unlock the smaller phone via the non-existent fingerprint scanner lol!
youngchaos said:
I sold my G4 just for modding. I like to mod and unfortunately G4 have a small community. Good luck , best 2015 phone if you dont mind to be on stock.
Click to expand...
Click to collapse
No need to remain in stock, the community worked out ways how to root. But the biggest downer is definitely LGs position on bootloader unlocking. We can have Lollipop root without BL unlock, but no custom ROMs, no root for Marshmallow :/
It's my second Android, my previous one is a rather ****ty Galaxy Ace from 2011. So yeah, compared to that, Im happy with rooted 5.1.
I badly wanna buy this phone asap but every time I check out some reviews over the internet across various sites, a lot of people have complained about rapid auto shutdowns and volte issues. Although, there are some who have been using this phone since more than 6 months and everything worked fine for them.
Is there any such issues on this phone like these people have mentioned? Cause both would be horrible for me. Shutdowns can be frustrating and if volte doesn't works properly, then Jio would be useless and I rely on it a lot as its my primary carrier!
Please let me know about the known issues of this phone as it would really help me to boost my confidence to buy it. And I literally cant wait to get my hands on it. Using something with a SD 820 would be like a dream come true!
Your opinions would be much appreciated.
Thank you!
veezybaybee said:
I badly wanna buy this phone asap but every time I check out some reviews over the internet across various sites, a lot of people have complained about rapid auto shutdowns and volte issues. Although, there are some who have been using this phone since more than 6 months and everything worked fine for them.
Is there any such issues on this phone like these people have mentioned? Cause both would be horrible for me. Shutdowns can be frustrating and if volte doesn't works properly, then Jio would be useless and I rely on it a lot as its my primary carrier!
Please let me know about the known issues of this phone as it would really help me to boost my confidence to buy it. And I literally cant wait to get my hands on it. Using something with a SD 820 would be like a dream come true!
Your opinions would be much appreciated.
Thank you!
Click to expand...
Click to collapse
Tried 3 different roms and never had one of those issues.... Only minor bugs currently solved.
Lineage OS was ok
Darkness and citrus-caf super
Wil try discovery one of this days
Enviado do meu Z2 Plus através de Tapatalk
imarco.box said:
Tried 3 different roms and never had one of those issues.... Only minor bugs currently solved.
Lineage OS was ok
Darkness and citrus-caf super
Wil try discovery one of this days
Enviado do meu Z2 Plus através de Tapatalk
Click to expand...
Click to collapse
So, according to you, the stock rom has issues and custom ones dont is it? I also wanted to ask you something. I heard from some people that we can still get the warranty for Z2 Plus even after flashing custom roms. Is it? And does these custom roms support volte? I need that the most.
What is your final opinion regarding this phone buddy? Is it worth buying?
About the warranty I don't know.
Volte works in my area
Zui OS is still under development
The fone is great for this money you can't get better one. The only thing for my is the glass back.... It's really slipperie... So you Ned to be carefull with the falls
Enviado do meu Z2 Plus através de Tapatalk
Facing two very annoying issues.
1. The UI is pretty bad. It needs a custom ROM but that will void warranty so think about that.
2. When charging the touch goes bonkers. A slight touch would react very differently like the phone is broken.
I had VOLTE problem once, it left VOLTE band and didn't want to go back. Then after some changes in the APN didn't happen again.
n00b_dr0id said:
Facing two very annoying issues.
1. The UI is pretty bad. It needs a custom ROM but that will void warranty so think about that.
2. When charging the touch goes bonkers. A slight touch would react very differently like the phone is broken.
I had VOLTE problem once, it left VOLTE band and didn't want to go back. Then after some changes in the APN didn't happen again.
Click to expand...
Click to collapse
Are there any custom ROM which is supporting VoLTE? - the ZUI is not for me, its crap and slow.
debasish497 said:
Are there any custom ROM which is supporting VoLTE? - the ZUI is not for me, its crap and slow.
Click to expand...
Click to collapse
Every Indian ROM should, I don't intend to unlock the bootloader until the warranty expires. I have a hunch that it will need to see the service center quite a few times. First and last LENOVO phone I would ever spent. Though having a Lenovo laptop I knew about Lenovo quality but couldn't resist the discount now the return window is closed too, regrets.
debasish497 said:
Are there any custom ROM which is supporting VoLTE? - the ZUI is not for me, its crap and slow.
Click to expand...
Click to collapse
I don't know who told you that?
I had a lot of android phones since original Samsung Galaxy, LG, Sony, HTC, Amazon phone, Nexus 4-5...
So I find ZUI (China version 2.5.334 ST) snappy and one of the most stable ROMs I ever used...
About the issues, since there is no top developers involved in ROM development for ZUK 2 it seems to me that after unlocking bootloader and messing with various versions of ROMs even flashing India ROM on China based ZUK can cause some serious issues...
It is your call whether to buy or not...only thing I don't like is mediocre brightness of the display...
ZUI is the worst ROM I have ever seen. Period.
Ive been playing about with this phone now and making a rom and in my expericance so far and from somthing @ChazzMatt said that I realized something was not quite right and it happened after i flashed a new 10c kdz and did the normal thing twrp + Magisk + Viper that i found the Quad DAC to not be switching on. Volume at 50 is nowhere near what i should be with it on compared to off. Ive found something in the build prop but im not sure if its just a coincence or this is actually doing something but 2 things might be the cause of the DAC not switching on.
1. Persist.audio.dmb_hifidac = true
2.Persist.audio.hifi_dac = off
Ive found that playing with these options and rebooting causes the DAC to switch on again. Maybe someone else can confirm exactly which of these keeps it working.
In custom CM/LOS ROMs with the 2016 ZTE Axon 7, which also has a quad DAC, devs could not use the quad DAC for audio processing. They had to use the Qualcomm Snapdragon audio processor -- as ZTE would not release proprietary source code for their award-winning quad DAC.
I believe stock based custom ROMs still had access -- as those were just debloated, tweaked ZTE firmware.
(Last time I checked was a few months ago, so if devs overcame that hurdle, then good for them. I only know the situation last time I looked.)
I do not know about the LG V20 custom ROMs, either stock-based or CM/LOS. LG V20 of course also has quad DAC. I've not researched. Maybe someone coming from V20 can tell us, either a dev or a user?
It's just the quad DAC on this phone is one of the main selling points, so you want to make sure it's being used if possible... Your ROM is stock based, but LG does have limits in place. For instance, it checks for impedance. And there's things you don't want to break.
Sent from my carrier unlocked LG V30+ US998
Can confirm. After last twrp session updating to magisk 15 killed the quaddac.
Setting the values as follows and rebooting brought it back.
persist.audio.dmb_hifidac
true
persist.audio.hifi_dac
ON
donky kong 017 said:
Can confirm. After last twrp session updating to magisk 15 killed the quaddac.
Setting the values as follows and rebooting brought it back.
persist.audio.dmb_hifidac
true
persist.audio.hifi_dac
ON
Click to expand...
Click to collapse
Ok that's strange as I had it working on different settings.
Having just replaced my v30 twice. USB port broke on 1st phone then a vertical line was on the 2nd one I got. I'm now on my 3rd phone with your settings but nothing happened till I switched on viper master power and rebooted. There's some weird impedance thing going on with it.
Whiskeyomega said:
Ok that's strange as I had it working on different settings.
Having just replaced my v30 twice. USB port broke on 1st phone then a vertical line was on the 2nd one I got. I'm now on my 3rd phone with your settings but nothing happened till I switched on viper master power and rebooted. There's some weird impedance thing going on with it.
Click to expand...
Click to collapse
Yeah it's strange. Everything worked last time with old magisk (I had to go back to stock and reflash twrp after updating to magisk 15 got me a bootloop)
It seems odd that rooting changes such things in build.prop
I woke up this morning and plugged my phone into my speakers and then later in my headphones I noticed the dac not coming on despite not rebooting since the last time it worked. So I actually switched off the dac and kept plugging in the headphones until I noticed a difference in the sound and then the dac just came on. No reboot needed again.
Whiskeyomega said:
I woke up this morning and plugged my phone into my speakers and then later in my headphones I noticed the dac not coming on despite not rebooting since the last time it worked. So I actually switched off the dac and kept plugging in the headphones until I noticed a difference in the sound and then the dac just came on. No reboot needed again.
Click to expand...
Click to collapse
It's very strange. I noticed a short lag in sound when I tried to switch on/off dac and settings. As if it was about to change something but very delayed. Seemed like something was trying to do something but got stuck and never turned on settings or dac.
That was before I changed build.prop. After that all worked well. Like said before.
Could be that when i played around little more it would have switched on without changing build.prop. But did not have time to test because i was commuting.
Sent from my SM-G935F using Tapatalk
donky kong 017 said:
It's very strange. I noticed a short lag in sound when I tried to switch on/off dac and settings. As if it was about to change something but very delayed. Seemed like something was trying to do something but got stuck and never turned on settings or dac.
That was before I changed build.prop. After that all worked well. Like said before.
Could be that when i played around little more it would have switched on without changing build.prop. But did not have time to test because i was commuting.
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
What headphones do you have? I think it is to do with this. I just bought the Sennheiser HD630VB's which are only 23ohms. I also have the Momentum 2.0 over ears and the HD650s but ive only tried with the 630s and i suspect it needs 50ohms to really switch on DAC which in turn having Viper on would cause the checker to trick itself into thinking im running a higher impedance set of headphones so i need the dac on.
Whiskeyomega said:
What headphones do you have? I think it is to do with this. I just bought the Sennheiser HD630VB's which are only 23ohms. I also have the Momentum 2.0 over ears and the HD650s but ive only tried with the 630s and i suspect it needs 50ohms to really switch on DAC which in turn having Viper on would cause the checker to trick itself into thinking im running a higher impedance set of headphones so i need the dac on.
Click to expand...
Click to collapse
Atm im on vacation. I will look into it when I have the time. FYI I have ath m50x and teufel move inear
Sent from my SM-G935F using Tapatalk
so i've looked into it. my HP have 32 and 16 Ohm impedance.
they trigger the dac on when i connect them (after i changed the build.prop. it never stopped working for me again)
judging from this thread connecting higher impedance HP will trigger higher power output modes, but the dac is always on in the same way
If somebody was thinking battery test on youtube video streaming, i did that and got 8h 2min sot. Full brightness and volume.
can someone help me? have the feeling that my dac does not run since I use viper4android
with me the dac does not run with viper4android
Sony92 said:
with me the dac does not run with viper4android
Click to expand...
Click to collapse
Don't use that then. Instead use this:
Whiskeyomega's V30 Sound Mods
https://forum.xda-developers.com/lg-v30/themes/whiskeyomegas-v30-sound-mods-t3757115
What LG has done as made a bad job of the mixer_paths_tavil.xml which includes references a ES9018 which was never put in the phone or any phone AFAIK.
But what I have just noticed is if you are using a set of low impedance headphones, It goes through to the low power sound device chip but keeps the HIFI DAC switch working so the EQ can still work. Unless you make it think you are running a different type of headset which it calls "Advanced" which is high impedance then it runs to the decent DAC and there are no problems.
I have also noticed in all the mixer_paths_tavil.xml from around the world markets that there are differences in settings which should be the same. Which is what could account for some people saying Low Impedance still runs through the same decent DAC and some people saying it doesnt. Either way mixer_paths_tavil.xml is a maze of old and incorrect information.
So with that in mind. I'd Like to share the results of my work with more always coming.
Click to expand...
Click to collapse
Besides these standalone mods, some of this is implemented in at least two stock-based ROMs.
I do not want to use only the DAC, but also viper4android
Sony92 said:
I do not want to use only the DAC, but also viper4android
Click to expand...
Click to collapse
Those mods improve the DAC so you don't need viper4android.
Ok, I have to try it. but there is no way to use both?
because in the first posts was that someone has used it together with viper
Sony92 said:
Ok, I have to try it. but there is no way to use both?
because in the first posts was that someone has used it together with viper
Click to expand...
Click to collapse
You will have to ask them.
Sent via open market LG US998 V30/V30+
can it be because I installed a Costum Rom because the DAC is not running?
have the deep_buffer file restored. Now the DAC is running with Viper4Arise. I did not have to change any settings in Build.prop.