Related
supportforums.motorola.com/message/379884#379884
This is first update, as far as I know for Non-US milestone 2. Still didn't installed due to lack of time. Looks like they just update UK,FR and DE devices to Italian firmware. At least we got something...
Start up here:
direct.motorola.com/hellomoto/support/update/
Sent from my MotoA953 using XDA App
Currently Flashing UK SBF to install this: Just a bugfix tho :/
enhanced phone and calling stability
updates google services/apps
enhanced calling performance
enhanced security...
if you ask me, really lame
and said something about touchscreen *PLEASE BE 3 FINGER INPUT!*
Can't install update now so, can you please, share with us your experience. Does screen sensor works better?
Sent from my MotoA953 using XDA App
Just downloaded this.
As a heads up:
The UK update is identical to the one that leaked on here a few days ago.
Compared the hashes for the extracted sbfs for both the leak and the one MSU downloads.
.sbf (not .sbf.gz):
CRC32: 7617F5CE
MD5: 94E43968E736D1A89767170FCFB88F42
SHA-1: 3B83020E6E6731ECA74984BC7EA72677FD1AD169
I didn't have a chance to get at the gzipped sbf before Moto software update extracted it, but I would assume it matched the leak too.
Regardless, the underlying data matches.
As far as experience goes, haven't flashed back to UK 2.2.2 again yet, but before it rebooted a lot. I have a feeling this was down to Milestone Overclock not being fully compatible with the newer version. I also know that the wifi STILL cut out for me.
Performance was better overall, and I think it squashed the double typing bug with hw keyboard.
aislen said:
Can't install update now so, can you please, share with us your experience. Does screen sensor works better?
Sent from my MotoA953 using XDA App
Click to expand...
Click to collapse
So, since this is the leak - no 3 point touch screen. I even read the guess that it is hardware wise kept to 2 points...
Sorry for doublepost...
PhoenixTank said:
Performance was better overall, and I think it squashed the double typing bug with hw keyboard.
Click to expand...
Click to collapse
Someone even said it re-occured after updating his MS2
Aww...no update for AU region. =(
oTToToTenTanz said:
Sorry for doublepost...
Someone even said it re-occured after updating his MS2
Click to expand...
Click to collapse
Quite possibly true - I had only tested it for a little while. As soon as the wifi cut out I swore and bought a HTC Desire Z.
Indentical to the previously leaked 2.2.2 SBF?
I have been using that version for some time now, wondering whether to flash back to 2.2 and re-flash this pack.
chris0202 said:
Indentical to the previously leaked 2.2.2 SBF?
I have been using that version for some time now, wondering whether to flash back to 2.2 and re-flash this pack.
Click to expand...
Click to collapse
PhoenixTank said:
Just downloaded this.
As a heads up:
The UK update is identical to the one that leaked on here a few days ago.
Click to expand...
Click to collapse
As I posted earlier, yes.
PhoenixTank said:
As I posted earlier, yes.
Click to expand...
Click to collapse
Thanks. hmm, then i will stick to the present one.
interesting, they only used a patch about 25mb to make such a difference. wonder what took them a few months.
For me the Wlan now works fine. The connection did not cut off anymore on mixed wlan with n.
Sent from my MotoA953 using XDA App
there is no update to argentinian M2! can i install the leaked?
I did install this official patch but could not feel any change.
I still hope to see a Gingerbread update for Motorola Milestone 2 soon.
can anyone confirm that the headphone button doesn't work anymore with the stock music app since the update?
neumaennl said:
can anyone confirm that the headphone button doesn't work anymore with the stock music app since the update?
Click to expand...
Click to collapse
What button do you mean?
Cheers,
Steve.
StevePritchard said:
What button do you mean?
Cheers,
Steve.
Click to expand...
Click to collapse
I don't know how many button you have on your headphones.
I was referring to the headphones that came with the phone.
They have a hidden button next to the microphone.
That button allows you to pick up and end a call.
It could also be used to pause and unpause music playback.
Since the update I can't pause and unpause music playback using that button anymore in the preinstalled media player. Can anybody confirm this?
Picking up calls still works, though and if I install another media player (e.g. music mod), I can pause and unpause music playback with the headphone button in those players.
I hope this makes more sense now.
neumaennl said:
I don't know how many button you have on your headphones.
I was referring to the headphones that came with the phone.
They have a hidden button next to the microphone.
That button allows you to pick up and end a call.
It could also be used to pause and unpause music playback.
Since the update I can't pause and unpause music playback using that button anymore in the preinstalled media player. Can anybody confirm this?
Picking up calls still works, though and if I install another media player (e.g. music mod), I can pause and unpause music playback with the headphone button in those players.
I hope this makes more sense now.
Click to expand...
Click to collapse
Yes, it does make sense. I never used those headphones, in fact, I can't remember it coming with any, but I guess it did and I just ignored them.
I thought you were talking about an on-screen button.
Cheers,
Steve.
According to the announcement, the Nexus S (which is a Galaxy S with a curved screen, NFC, and GB) is supported for streaming, even though it's supposed to only be available for Snapdragons, and not yet for Hummingbird.
Anyone manage to snag the APK yet? It won't let me install from the Market, even though even Google thinks I'm running a Nexus S (when in reality, it's just a Fascinate with CM7).
http://www.businessinsider.com/how-to-get-netflix-on-your-android-phone-2011-3
Sent from my SCH-I500 using XDA App
Using that version of the app just gives you a message saying the phone is unsupported for streaming. Would changing the ID of the device in the build.prop or something similar be enough to fool Netflix?
Sent from my SCH-I500 using XDA App
caesus said:
Using that version of the app just gives you a message saying the phone is unsupported for streaming. Would changing the ID of the device in the build.prop or something similar be enough to fool Netflix?
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
That's the question I have. Trying to find out where I could edit it to see what it does.
I downloaded it on my Nexus and transfered the apk to my i500 but when I installed it it gave me the "unsupported device" error.
AlexDeGruven said:
That's the question I have. Trying to find out where I could edit it to see what it does.
Click to expand...
Click to collapse
Please share if you get this working.
http://forum.xda-developers.com/showthread.php?t=1076260
If I can get my hands on the build.prop from either the Nexus S on AT&T or the Nexus S 4G, then I might be able to figure out the pertinent tweaks to make the Fascinate appear as either of those to the app when it tries to stream.
If it runs and streams on the NS, then the purported hardware limitation that was supposed to be there doesn't exist, and they're implementing the device lockout entirely in software. This means it will be easy to hack around, and probably be able to do so cleanly without hammering any important settings for the phone.
Edit: The Incredible (and presumably, by extension, the Thunderbolt) is supported, so it's not a carrier lockout, either. This tells me that it's only software, which is heartening.
http://t.co/n7QDwJ4
Courtesy of koush
Sent from my SCH-I500 using XDA App
Awesome. I'll check this out tonight and see what I can come up with.
Sent by touching a featureless glass panel with mysterious lights behind it.
"HELL YEAH!!!!.... aww man...."
it pretty much happened just like that.
Hmm no luck so far. Not really sure what to change without breaking the whole show.
Hopefully, someone with more expertise than I can chime in with the right changes.
Sent by touching a featureless glass panel with mysterious lights behind it.
Tech buzz widget has an androidpolice article about what lines in the build prop to edit. Haven't tried it yet...
OTB Comm.Rominate
Found this in the evo forums...maybe it'll help you guys
mikel719 said:
Ok, so I was in the virus kingdom rom thread and seen this asked a couple of times.
I found this info on another site, I'll past the link in a few but here are the instructions...
So how’s it done? Well, the instructions are actually fairly straightforward, and come courtesy of tipster/redditor natemckn:
Root is required. Make a Nandroid backup! (I accidentally deleted by build.prop file and bootlooped my phone)
Download ES File Explorer (Or any other root file editor)
In ES File Explorer, go into Setting > Root Settings and enable both check boxes
Navigate to /system/ and copy/paste build.prop to /sdcard/ (just in case)
Open & edit /system/build.prop
Change the following lines to make your phone think it is a HTC G2:
ro.product.model=HTC Vision
ro.product.brand=tmobile
ro.product.name=vision
ro.product.device=vision
ro.product.board=vision
ro.product.manufacturer=HTC
Reboot the phone
Install the netflix apk (if you haven’t already)
Enjoy
Update: Apparently you don’t need to do the lines that are crossed out in Step 6 – only the product model and manufacturer need to be changed.Also, it appears that this is hit-or-miss at the moment. Works for some, partially (but not really) for others.
Heres the link,, if its not clickable its because I'm doing this from my phone, so copy and paste.
http://www.androidpolice.com/2011/0...to-thinking-your-rooted-device-is-supported/#
Sent from the hidden underground command bunker
Click to expand...
Click to collapse
Tried it on my Fascinate with CM 7 (5/11/11). Changed build.prop to the HTC Vision. Installed netflix app without any errors, but when I play a movie, it only plays the audio, the video is just a black screen. Anyone else have this problem and found a solution??
emortio said:
Tried it on my Fascinate with CM 7 (5/11/11). Changed build.prop to the HTC Vision. Installed netflix app without any errors, but when I play a movie, it only plays the audio, the video is just a black screen. Anyone else have this problem and found a solution??
Click to expand...
Click to collapse
Afaik, our cm7 builds are missing a lot of codecs... this could be part of your video problems.
Sent from my HTC Vision using Tapatalk (heh... well, I guess we know where Tapatalk gets its model info. )
* The Netflix app runs on these phones:
1. HTC Incredible with Android 2.2
2. HTC Nexus One with Android 2.2, 2.3
3. HTC Evo 4G with Android 2.2
4. HTC G2 with Android 2.2
5. Samsung Nexus S with Android 2.3.
Thank you for repeating the information that we already know.
We're aware of the devices it works on, we're trying to make our devices masquerade as one of those in an attempt to get streaming working.
Not much luck so far. Time to work now. Might hack on it some more tonight.
The apk running around here doesn't work, either. At least not on 2.2.
Ok, so I said I was going to quit, but it's just too juicy.
Here's what I've found:
Work on Nexus S with GB. The NS is identical to the rest of the Galaxy S line from a hardware standpoint (with the exception of the NFC and curved screen, which have nothing to do with things). The only difference between them is the software.
Some more digging revealed that the key difference in a device working or not working is the Stagefright media framework, which is supposed to be the stock setup in 2.2, but OEMs mostly felt like they needed to hack it out in favor of their own stuff.
So... To get this working on the Fascinate, we need one of the following:
1. A CM7/AOSP GB build with working video codecs (we're almost there on that point)
2. A CM6/AOSP FroYo build with Stagefright media framework in place.
3. A custom ROM with the Stagefright framework hacked in.
AlexDeGruven said:
So... To get this working on the Fascinate, we need one of the following:
1. A CM7/AOSP GB build with working video codecs (we're almost there on that point)
2. A CM6/AOSP FroYo build with Stagefright media framework in place.
3. A custom ROM with the Stagefright framework hacked in.
Click to expand...
Click to collapse
4. A Samsung GB leak. Don't laugh -- now that i9000 GB is final, it's already official for the GSM Tab, and the Epic has a leak (now two) as well. US Galaxy S models running Touchwiz GB have run Netflix with no problem.
The reason I'm asking is because this (https://play.google.com/store/apps/details?id=com.directv.dvrscheduler) is one of the main apps I use on my nexus 10 and ever since I did the upgrade to 4.2.2 it exhibits stutter during live TV playback. I can't be certain this is related to 4.2.2 and thus my question, is anyone using this app with 4.2.2 and successfully playing back live TV stutter free? Like I said, it was stable for me up until just a couple weeks ago.
In the event there aren't too many others using this app does anyone know how to reach those who are responsible for developing and sending out stock os updates? It might not mean anything to them but I've thought of providing feedback around what I'm seeing and I guess it I'd worth a try. Who knows, maybe they could release a fix in the next update.
I have the app. Don't use it for watching shows because it's horrible. Basically use the dvr function to record shows. You could probably go to the website and complain. I think that i looked into it once before.
Have you seen their Ipad app? It is absolutely beautiful and works flawlessly. The guide looks just like the web version and it also has a built in remote so you can control all of your receivers. It is the one app that I want updated on android!
Sent from my Nexus 10 using Tapatalk HD
Droid_Junky said:
I have the app. Don't use it for watching shows because it's horrible. Basically use the dvr function to record shows. You could probably go to the website and complain. I think that i looked into it once before.
Have you seen their Ipad app? It is absolutely beautiful and works flawlessly. The guide looks just like the web version and it also has a built in remote so you can control all of your receivers. It is the one app that I want updated on android!
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
Yes, I've seen it on the iPad. The GUI is much better, as you mentioned, but typically the live playback was the same in my experience. They both looked acceptable on the iPad and my Nexus 10. Of course with 4.2.2 all that seemed to change and now I have stutter. I really hope this can somehow be resolved. I only use probably about 5 apps on my N10 on a consistent basis and this is one of them.
JPW1 said:
The reason I'm asking is because this (https://play.google.com/store/apps/details?id=com.directv.dvrscheduler) is one of the main apps I use on my nexus 10 and ever since I did the upgrade to 4.2.2 it exhibits stutter during live TV playback. I can't be certain this is related to 4.2.2 and thus my question, is anyone using this app with 4.2.2 and successfully playing back live TV stutter free? Like I said, it was stable for me up until just a couple weeks ago.
Click to expand...
Click to collapse
Do you have the full range of channels to watch live? Or a select few?
SayWhat10 said:
Do you have the full range of channels to watch live? Or a select few?
Click to expand...
Click to collapse
The app only allows for a select number, but I think there are quite a few, something like channel 200 and above. Personally, I watch it for The Tennis Channel and HGTV while I'm working out. Of course I can't any more since something seems to be an issue. I keep wondering whether anyone on 4.2.2 is able to stream live TV or not. I was able to do it with 4.2.1 just fine.
JPW1 said:
The app only allows for a select number, but I think there are quite a few, something like channel 200 and above. Personally, I watch it for The Tennis Channel and HGTV while I'm working out. Of course I can't any more since something seems to be an issue. I keep wondering whether anyone on 4.2.2 is able to stream live TV or not. I was able to do it with 4.2.1 just fine.
Click to expand...
Click to collapse
I just pulled up the DirecTv app for the first time since the 4.2.2 update to do live streaming. EXACT same problem as you. Stuttering where it was smooth before. Same is true for the tablet and phone version of the app. I would say 4.2.2 is the likely culprit unfortunately.
fooldog01 said:
I just pulled up the DirecTv app for the first time since the 4.2.2 update to do live streaming. EXACT same problem as you. Stuttering where it was smooth before. Same is true for the tablet and phone version of the app. I would say 4.2.2 is the likely culprit unfortunately.
Click to expand...
Click to collapse
Thank you so much for confirming this. Any thoughts on who we might be able to reach out to so that they have an awareness that this issue exists? I'm not quite sure who is best to contact when it comes to the developers of the android operating system.
JPW1 said:
Thank you so much for confirming this. Any thoughts on who we might be able to reach out to so that they have an awareness that this issue exists? I'm not quite sure who is best to contact when it comes to the developers of the android operating system.
Click to expand...
Click to collapse
I'm guessing there's pretty much nothing you can do other than downrating in the market and explaining why. That's what I did.
Sent from my SAMSUNG-SGH-I747 using xda premium
I can't take this any longer. Watching DirecTV on my tablet was one of the primary reasons I purchased it. DirecTV just released a brand new app for Android and it looks almost identical to the iPad's (very nice GUI). But guess what? The stupid live streaming also fails on the Nexus 10 with the latest OS updates in the same way their other app did. Unbelievable. I've done what I can to contact DirecTV and Google about the issues, but I'm not seeing much response and since it has already been probably 4 months I'm not expecting a true resolution any time soon.
SO...this leaves me with taking matters in to my own hands. I'm a complete newbie when it comes to rooting, but I guess what I need to do is root the device and either install a different build or roll back the Google OS to 4.2.1, the version that worked with the DirecTV app. Could anyone point me in the right direction of what the best course of action might be to accomplish this? There are so many posts with what seems like so many options I am overwhelmed. Any guidance is appreciated.
Now with the update to 4.3 it won't stream at all. Just goes blank. Fantastic.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4 Beta
fooldog01 said:
Now with the update to 4.3 it won't stream at all. Just goes blank. Fantastic.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I'm getting the exact same thing after the 4.3 update. What is Google thinking!?!? And how long before they actually fix major bugs like this?
Finally finally finally. DirecTV has fixed this app. It doesn't appear the picture quality is as good as it used to be, but I'm not really going to complain about that. They at least have it operational again. Where I will complain is around the time it took to get a resolution. For as much DirecTV is advertising their mobile viewing ability with tablets and cell phones, this should have been an "all hands on deck" priority for them and it wasn't. DirecTV, you can do better, but for the moment, I will give them credit for getting it done.
I'm on Verizon and my MMS photos come in very low. Does anyone know how to fix this?
Sent from my XT1575 using Tapatalk
I had the same issue, tried every single SMS app, did a full wipe. No difference. Will be sending the phone back if I can't figure it out soon. I though it may have been an issue with Verizon not recognizing the phone. Will try to edit the build prop
Moto x 2014 on Verizon had the same problem. Thread died out so maybe they found a solution
http://forum.xda-developers.com/moto-x-2014/help/q-vzw-moto-x-mms-low-res-t2975525
I tried editing the build prop with a different phone make and model, no difference. Its going back to amazon.
This makes no sense. There has to be a solution
Sent from my SCH-I545 using Tapatalk 2
I know this doesn't help, but I have no problem with MMS on At&t. I use YAATA as my MMS app.
Just wanted to add - Im on VZW as well, same low res images, I've only tried Google Messenger so far, and I agree would be a deal breaker for me.
This used to happen on other Phones if I used CM12.1, as it was a known bug, and I couldn't handle using CM becuase of it.
its verizon reducing the quality of the image in order to reduce its data footprint. Very doubtful its a problem just with the moto x
racinwarrior said:
its verizon reducing the quality of the image in order to reduce its data footprint. Very doubtful its a problem just with the moto x
Click to expand...
Click to collapse
I came from Nexus 6 ( Also not bought via VZW) and did not have this issue. It's def VZW related though it seems.
gchase23 said:
I came from Nexus 6 ( Also not bought via VZW) and did not have this issue. It's def VZW related though it seems.
Click to expand...
Click to collapse
The quality of MMS on my Nexus 6 isn't that great a lot of the time. How much worse is this? Are the pictures unusable?
you know, at first I was just somewhat annoyed by this, but after getting some over the last two days, it may be a deal breaker. The pictures are over saturated and grainy, and generally look like s#*t. If this is just " how it is", coupled with the other Verizon issues (no HD calling, no video chat) I may have to take a pass...
ret4425 said:
you know, at first I was just somewhat annoyed by this, but after getting some over the last two days, it may be a deal breaker. The pictures are over saturated and grainy, and generally look like s#*t. If this is just " how it is", coupled with the other Verizon issues (no HD calling, no video chat) I may have to take a pass...
Click to expand...
Click to collapse
FYI - I think HD Calling works fine? - "enhanced 4g LTE mode" is on for me, you may have to call vzw to get it to work (I had to with Nexus 6), b/c it won't be turned on unless they mark you with a phone that they know is compatible. (also have to add it to your account, although its free).
But I agree, the photo quality is so low that you can't use them for anything, blurry photos.
The photo's are coming through at between 10-20kb, completely unusable.
LeonTLR said:
The photo's are coming through at between 10-20kb, completely unusable.
Click to expand...
Click to collapse
Wow, really??? Yeah, I tried saving one and sending it to a friend, and he asked me if I got it off my dial up connection on AOL...
gchase23 said:
FYI - I think HD Calling works fine? - "enhanced 4g LTE mode" is on for me, you may have to call vzw to get it to work (I had to with Nexus 6), b/c it won't be turned on unless they mark you with a phone that they know is compatible. (also have to add it to your account, although its free).
But I agree, the photo quality is so low that you can't use them for anything, blurry photos.
Click to expand...
Click to collapse
Is this something I can enable on my account page on myvzw?
Also the mms image quality is at an all time low. Any way to edit build.prop for better mms?
Edit: Sending mms isn't a problem. Sent mms to wife and her galaxy s6 received the image at around 720kb.
Sent me an mms and it comes in at 17kb.
I am rooted. So, if their is a root method to fixing this, that would be great.
NoFear1183 said:
Is this something I can enable on my account page on myvzw?
Also the mms image quality is at an all time low. Any way to edit build.prop for better mms?
Edit: Sending mms isn't a problem. Sent mms to wife and her galaxy s6 received the image at around 720kb.
Sent me an mms and it comes in at 17kb.
I am rooted. So, if their is a root method to fixing this, that would be great.
Click to expand...
Click to collapse
When I tried to enable online it said I had to call in, so I did and was fine.
Yes I agree - I found a discussion for HTC phones where someone was manually editing mms.apk to allow for higher total, I didn't see anywhere on how to actually do it, or am I technical enough to do it.
Currently using MXP rooted on Textra and have not had an issue with mms. Granted my mom's phone is a POS but they're coming in at ~110-170 kbs
Also using Textra and get pics at 100-200 in size. Perhaps it's the default messaging app?
Sent from my XT1575
I'm using Messenger, not the default messaging app. Quality suck azz
For those of you that rooted, did you use the heisenberg method? Im wondering if the alternative root method (windycity rocker) may be causing some issues
Sent from my SCH-I545 using Tapatalk 2
I am rooting as soon as it is available. Why?
-Xposed works perfect now
-Viper4android
-Adaway
That is why I want root.
I don't care about samsung pay, at all.
Adaway, viper, titanium backup, busybox, etc
Only thing I find myself needing these days is Adaway, everything else is cosmetic...
Found Adguard now, so no need to root for ad blocking.
Probably won't bother rooting this one to be honest.
Sent from my Nexus 6P using Tapatalk
I'm rooting ASAP to begin tweaking settings and for when source drops so I can begin work on my kernel
I never root straight away. I'll use the phone for a while then decide what tweaks I want to make, then I will root. If the phone is fine without root I'll continue to use it without root.
I use 2 apps that only work on non-rooted devices so this is one thing that stops me rooting too, but if I feel I need to root, I will.
does adguard work for you? it reeaally drains the battery on my nexus 5, it took 24%! the phone didn't last through half a day with it running. i have used the VPN sinkhole, not the proxy option. same happened to other "noroot firewalls" i have tried (e.g. from "grey shirts" in playstore) so i guess it's a common problem with the VPN sinkhole solution..
Xileforce said:
I'm rooting ASAP to begin tweaking settings and for when source drops so I can begin work on my kernel
Click to expand...
Click to collapse
Hi,
Will your kernel then work also on the european exynos variant? :fingers-crossed:
Thanks!
Oh you are going to root your new phone. Woww!!!
BWA80 said:
Hi,
Will your kernel then work also on the european exynos variant? :fingers-crossed:
Thanks!
Click to expand...
Click to collapse
Unfortunately not as the snapdragon version is what I have. They are likely totally different source wise. I'm sorry
Yes if i decide to root my s7 edge ill be looking at bringing a kernel out. That will be for exynos model. Not sure if ill root yet thought but a kernel sounds good
Rooting for me is absolutely essential, I use too many Xposed modules (XPrivacy in particular for me is essential). But most of all, I need root for Viper4Android. Once you listen to your music through that, there is no going back. I've been using it for over two years.
It's for these reasons I will be returning the phone if the Vodafone bootloader is locked. Dealing without root for a month or two whilst someone makes it happen is one thing. Knowing I won't have it for the two years I'm contracted to pay for the phone is something else entirely, it's a complete deal breaker. I'd sooner stick with my Note 3 than have an S7 without root for two years, never mind being expected to pay £40 a month for the privilege. In some ways I'm actually envious of people who are prepared to have an Android phone without it, because it would make things so much easier if I felt the same way.
Beefheart said:
Rooting for me is absolutely essential, I use too many Xposed modules (XPrivacy in particular for me is essential). But most of all, I need root for Viper4Android. Once you listen to your music through that, there is no going back. I've been using it for over two years.
It's for these reasons I will be returning the phone if the Vodafone bootloader is locked. Dealing without root for a month or two whilst someone makes it happen is one thing. Knowing I won't have it for the two years I'm contracted to pay for the phone is something else entirely, it's a complete deal breaker. I'd sooner stick with my Note 3 than have an S7 without root for two years, never mind being expected to pay £40 a month for the privilege. In some ways I'm actually envious of people who are prepared to have an Android phone without it, because it would make things so much easier if I felt the same way.
Click to expand...
Click to collapse
Mines coming direct from EE and I believe they lock the bootloader. However my wife is getting hers direct from carphone warehouse and has agreed to swap so I can root quicker (she doesn't care for root. As long as she can use Facebook and WhatsApp she's happy).
I had always assumed that Viper4Android wouldn't make much difference so I'll have to give it a whirl.
I agree with everything everyone says here, viper yes, adaway yes, xposed definitely, but I so want to try it Samsung pay. The ads suck.
Sent from my SM-G935T using Tapatalk
CuBz90 said:
I had always assumed that Viper4Android wouldn't make much difference so I'll have to give it a whirl.
Click to expand...
Click to collapse
In audio terms, going from stock sound to Viper4Android is like going from a Ford Focus to a McLaren. And that isn't an exaggeration.
I will root ASAP for ARU-R to use on pioneer app radio. I am also hoping for lots of development and custom ROMs and kernel. A boy can dream......
Sent from my LG-VS980 using XDA Free mobile app
Beefheart said:
In audio terms, going from stock sound to Viper4Android is like going from a Ford Focus to a McLaren. And that isn't an exaggeration.
Click to expand...
Click to collapse
Well I guess I shouldn't assume. I've coped with crap volume on my Samsung devices for years.
Beefheart said:
In audio terms, going from stock sound to Viper4Android is like going from a Ford Focus to a McLaren. And that isn't an exaggeration.
Click to expand...
Click to collapse
On my 6P Viper actually sounded worse than stock... Even using the "audiophile" profiles designed for the phone.
geoff5093 said:
On my 6P Viper actually sounded worse than stock... Even using the "audiophile" profiles designed for the phone.
Click to expand...
Click to collapse
That's odd. I use it for most of my Bluetooth devices now. Especially my wireless senheissers.
Sent from my SM-N920W8 using Tapatalk
geoff5093 said:
On my 6P Viper actually sounded worse than stock... Even using the "audiophile" profiles designed for the phone.
Click to expand...
Click to collapse
Very strange. I don't want to insult you by claiming you mustn't have set it up properly but what settings were you using? The good thing about it is that virtually every aspect of a sounds dynamics can be adjusted. Did you simply use it with the profile you downloaded, or did you set the UI to Expert and make the fine adjustments yourself to the various settings until you got the desired sound? It can take a long time to set up correctly. I have various profiles I have made myself for different music genres and particular bands and artists. They took me hours of trial and error to set up.
Beefheart said:
In audio terms, going from stock sound to Viper4Android is like going from a Ford Focus to a McLaren. And that isn't an exaggeration.
Click to expand...
Click to collapse
Beefheart said:
Very strange. I don't want to insult you by claiming you mustn't have set it up properly but what settings were you using? The good thing about it is that virtually every aspect of a sounds dynamics can be adjusted. Did you simply use it with the profile you downloaded, or did you set the UI to Expert and make the fine adjustments yourself to the various settings until you got the desired sound? It can take a long time to set up correctly. I have various profiles I have made myself for different music genres and particular bands and artists. They took me hours of trial and error to set up.
Click to expand...
Click to collapse
I flashed Viper, used the audiophile profile that was posted in the OP of a very large Nexus thread. The sound was obviously different, but was very treble biased. Listening to music on my phone speakers or to my BT speaker without an equalizer, it was ear piercingly high. I tried playing with the settings using what people had posted that had many upvotes, and it still sounded poor.