Related
I guess this is development, so here goes:
Ok, some people have repoted success with my Audio Hack on the Nexus whilst some people have reported no change at all.
If my app or the manual hack works for you can you please let me know what ROM you're running, and which version of my hack you used, it would be very helpful
Cheers!
Meltus said:
I guess this is development, so here goes:
Ok, some people have repoted success with my Audio Hack on the Nexus whilst some people have reported no change at all.
If my app or the manual hack works for you can you please let me know what ROM you're running, and which version of my hack you used, it would be very helpful
Cheers!
Click to expand...
Click to collapse
I'll help ...
I'll give her a test whirl in a little bit and report back some solid testing results for you as soon as I can.
~enom~
i tried every possible combo with the options this morning and i still have nothing. oddly, i get a double screen option on the headphone boost screen. 2 yes and 2 no's. one pair is white the other yes is green and the other no is red.
my results and some information
Meltus,
Do you have a N1 to play with? or are you shooting in the dark (and thus need help)?
Anyhow ...
Some details ...
I implemented via manually pushing the AudioPara4.csv, AudioFilter.csv, & AudioPreProcess.csv files to /system/etc and then rebooting.
I tried both G7_v3r2 and G7_v2r2. Both resulted in (from what I can tell) no change. I did not witness any volume gain or decrease. No distortion. No nothin'. Literally everything appeared unchanged.
Some interesting things I found for you ...
The stock (or shipping) AudioPara4.csv in the Nexus1 (ERD79) is the exact match for all Stock-sapphire-32B(MT3G) ROM's/devices.
Also, AudioPreProcess.csv and AudioFilter.csv are not present on the Nexus1.
Also, the Nexus1 is shipping with a couple new .csv files in the /system/etc directory ... AdieHWCodecSetting.csv & AudioBTID.csv.
That's the results I obtained and the relevant detail I observed. If you need anything else from me in way of producing an audio mod. I'd be happy to assist.
~enom~
simms22 said:
i tried every possible combo with the options this morning and i still have nothing. oddly, i get a double screen option on the headphone boost screen. 2 yes and 2 no's. one pair is white the other yes is green and the other no is red.
Click to expand...
Click to collapse
Hmm that's odd, not sure why that happens. could be something to do with the screen resolution.
i'll look into it
enomther said:
Meltus,
Do you have a N1 to play with? or are you shooting in the dark (and thus need help)?
Anyhow ...
Some details ...
I implemented via manually pushing the AudioPara4.csv, AudioFilter.csv, & AudioPreProcess.csv files to /system/etc and then rebooting.
I tried both G7_v3r2 and G7_v2r2. Both resulted in (from what I can tell) no change. I did not witness any volume gain or decrease. No distortion. No nothin'. Literally everything appeared unchanged.
Some interesting things I found for you ...
The stock (or shipping) AudioPara4.csv in the Nexus1 (ERD79) is the exact match for all Stock-sapphire-32B(MT3G) ROM's/devices.
Also, AudioPreProcess.csv and AudioFilter.csv are not present on the Nexus1.
Also, the Nexus1 is shipping with a couple new .csv files in the /system/etc directory ... AdieHWCodecSetting.csv & AudioBTID.csv.
That's the results I obtained and the relevant detail I observed. If you need anything else from me in way of producing an audio mod. I'd be happy to assist.
~enom~
Click to expand...
Click to collapse
Yeah, i'm pretty much guessing at the moment, with help from simms22, but we've still not been able to get the volume hack to work.
It's strange though, some people have reported success whilst most others haven't. And, from checking the logcat when the mediaserver restarts, it loads the AudioPara4.csv fine, so my files should make a difference and the headset boost option should work fine, but it doesn't ><
So far, we've established that the AudioFilter.csv and AudioPreProcess.csv aren't used by the Nexus, but the strange thing is, some of the Nexus firmware dumps which people provided for me include these files and some don't. It seems as if there's 2 versions of the nexus, either that or people added the files in when they sent me the dump.
So, it seems that the nexus loads the AudioPara file, but i'm not sure why as it doesn't do anything. The other 2 files seem to be bluetooth related, so i'm not sure they'll make a difference.
God, this phone's more trouble than it's worth
could it be that the nexus for google employees and the nexus for the public are that different. ive asked around also, no one has that app working on their nexus that i know of. could it be that some people are lying and just saying that it works(to be cool).
simms22 said:
could it be that the nexus for google employees and the nexus for the public are that different. ive asked around also, no one has that app working on their nexus that i know of. could it be that some people are lying and just saying that it works(to be cool).
Click to expand...
Click to collapse
Good point, and them lying is a possibility (albeit a strange one ).
This doesn't make much sense to me, i'm gonna speak to some ROM devs and see if they have an answer
Cheers for your help guys!
simms22 said:
could it be that the nexus for google employees and the nexus for the public are that different. ive asked around also, no one has that app working on their nexus that i know of. could it be that some people are lying and just saying that it works(to be cool).
Click to expand...
Click to collapse
yea I dunno ... it would certainly be hard to believe that this type of issue would be "intermittent".
This seems to me like an all or nothing affair, in which it really should either work or not. I could be wrong, I've seen stranger things happen, but I really don't see how this would be working for a "select few".
~enom~
enomther said:
yea I dunno ... it would certainly be hard to believe that this type of issue would be "intermittent".
This seems to me like an all or nothing affair, in which it really should either work or not. I could be wrong, I've seen stranger things happen, but I really don't see how this would be working for a "select few".
~enom~
Click to expand...
Click to collapse
Very true, unless there are 2 different versions (like simms said, maybe one for google employee's), but even if there was, i don't see why they would make it different. (unless they made it different for the public, specifically to stop me doing this, which i highly doubt lol)
Meltus said:
Very true, unless there are 2 different versions (like simms said, maybe one for google employee's), but even if there was, i don't see why they would make it different. (unless they made it different for the public, specifically to stop me doing this, which i highly doubt lol)
Click to expand...
Click to collapse
hahahahah...! theres always a conspiracy somewhere. but, me being more science minded than programming, the simplest answer is usually the correct one.
Meltus said:
Very true, unless there are 2 different versions (like simms said, maybe one for google employee's), but even if there was, i don't see why they would make it different. (unless they made it different for the public, specifically to stop me doing this, which i highly doubt lol)
Click to expand...
Click to collapse
My money's on a placebo effect. They get the new file on there, so they're under the impression it sounds better/louder.
Mi|enko said:
My money's on a placebo effect. They get the new file on there, so they're under the impression it sounds better/louder.
Click to expand...
Click to collapse
Probably. I remember a while ago, quite a few people (myself included) thought that the EQ was affecting the headset but it turned out to be making no difference at all. I would have put money on it too ><
Meltus said:
Hmm that's odd, not sure why that happens. could be something to do with the screen resolution.
i'll look into it
It's strange though, some people have reported success whilst most others haven't.
I have 3 N1's in my home. we all have your app and it doesnt seem to work. their most likely lying!!! btw, we all are getting the double screen too.
keep up the good work!!!!
Click to expand...
Click to collapse
[email protected] said:
Meltus said:
Hmm that's odd, not sure why that happens. could be something to do with the screen resolution.
i'll look into it
It's strange though, some people have reported success whilst most others haven't.
I have 3 N1's in my home. we all have your app and it doesnt seem to work. their most likely lying!!! btw, we all are getting the double screen too.
keep up the good work!!!!
Click to expand...
Click to collapse
yeah, i may have to add compatibility for higher resolution devices. Either that or there's an image i forgot to delete underneath. I'll have a look either later or tomorrow night, got a busy day tomorrow.
Click to expand...
Click to collapse
Meltus said:
Probably. I remember a while ago, quite a few people (myself included) thought that the EQ was affecting the headset but it turned out to be making no difference at all. I would have put money on it too ><
Click to expand...
Click to collapse
lol..I wanted an EQ so bad I think I convinced myself something was actually happening.
I am not getting the double screen at all. I saw no difference in the volume either with the external speaker or the headphones after installation and setting up V2r2.
Volume Hack
I have the double icons on the headset screen. I haven't had a change in the volume.
Now I could have sworn when I tried it that the volume got worse and then I tried the files on your site the stock ones and it got better but after playing with it continuously for about 3 days I have come to the conclusion it is a placebo effect and nothing more.
EDIT: Im dumb xD
Driskol said:
EDIT: Im dumb xD
Click to expand...
Click to collapse
hahaha....! one of my top 5 favorite posts of all time! but this statement isnt nexus one development. lol, wrong section
Hello, I just got my new Evo 4g LTE and it was upgraded from an Evo 4g, so I am already pretty settled in with the phone. I've only had one real problem with it so far, and I was hoping someone here might know the fix.
I got it from Best Buy, and went I went to the store the day after I bought it to transfer my contacts, some glitch started occuring after I left.
Here's the glitch: When I switch screens (Like opening up settings, or going to my texts, or even switching websites on the stock mobile browser), a real quick flash of red comes on the screen in the form of a box that outlines the screen. It's very subtle, and doesn't slow the phone down, but can get pretty annoying.
Do you guys know is this something that can be fixed? I asked Best Buy and they refused to even take it out of my hands and look at it because the supervisor there was "100% positive" it's a software problem and has to do with the ice cream sandwich software and will PROBABLY be fixed with an update that is released...but I haven't heard of it anywhere else so I don't want to wait for my manufactur's warranty to run out (21 days now) just for an update that may not even fix the glitch. Any help would be greatly appreciated, thanks!
It could be Strict mode, go to Settings --> Developer options and check that "Strict mode" is not enabled
miguelfp1 said:
It could be Strict mode, go to Settings --> Developer options and check that "Strict mode" is not enabled
Click to expand...
Click to collapse
I actually checked that yesterday, and made sure it wasn't the problem...but it is not enabled. Thanks for the reply, any other ideas?
Tolmes said:
I actually checked that yesterday, and made sure it wasn't the problem...but it is not enabled. Thanks for the reply, any other ideas?
Click to expand...
Click to collapse
unfortunately, short of factory resetting the phone and starting over, that was the only thing that came to mind
Anything else in settings/development enabled?
gpz1100 said:
Anything else in settings/development enabled?
Click to expand...
Click to collapse
Nah, everything is disabled...hmm guess I might try to reset it. If not, l'm regretablly switching to the iphone. I f'n hate apple, but HTC phones just cause me too much angst.
Tolmes said:
Nah, everything is disabled...hmm guess I might try to reset it. If not, l'm regretablly switching to the iphone. I f'n hate apple, but HTC phones just cause me too much angst.
Click to expand...
Click to collapse
Have you tried Forcing GPU rendering Under Developer Settings?
Can you post a screen shot of what you're seeing? Maybe that will trip off some light bulbs.
Disable Strict Mode under Development Tools and then restart the phone. That should fix it!
Has anyone seen a working wallet for our device?
Sent from my HTC One using Tapatalk 4 Beta
It's being worked on but afaik there hasn't been a proven method yet.
Sent from my HTC One using xda premium
Bladerunner1825us said:
It's being worked on but afaik there hasn't been a proven method yet.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Not yet. If they do get it working, it'll be through an international ROM. AT&T has refused to support it so far.
Yeah, I've tried the modaco toolkit version(from the youtube vid I found) and that person got it working, but it is on an Sprint HTC One.
Guess I'll wait and see what happens.
I found a verion that works on sprint, but on my phone (running cognition 0.6 - based upon dev rom) it still says "Device/carrier not supported"
I'm sure its based upon some carrier flag perhaps... not sure why/how at&t can actually keep google from releasing it... especially on a "deveoper" version of the phone...
centex99 said:
I found a verion that works on sprint, but on my phone (running cognition 0.6 - based upon dev rom) it still says "Device/carrier not supported"
I'm sure its based upon some carrier flag perhaps... not sure why/how at&t can actually keep google from releasing it... especially on a "deveoper" version of the phone...
Click to expand...
Click to collapse
Sprint is the only us carrier that can use wallet. Speaking from previous phones on their network. If I'm not mistaken the s3 on sprint and nexus all use wallet straight from the market.
Sent from my HTC One using Tapatalk 2
godfirst said:
Sprint is the only us carrier that can use wallet. Speaking from previous phones on their network. If I'm not mistaken the s3 on sprint and nexus all use wallet straight from the market.
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Yeah but they(devs here) found a way to use the Sprint version of the phones to bypass the carrier locks. I had GW on my AT&T S3 via wallet installer. Requires root, but it was a simple build.prop edit to get it working.
nest75068 said:
Yeah but they(devs here) found a way to use the Sprint version of the phones to bypass the carrier locks. I had GW on my AT&T S3 via wallet installer. Requires root, but it was a simple build.prop edit to get it working.
Click to expand...
Click to collapse
Yeah I had it on mine as well.
Sent from my HTC One using Tapatalk 4 Beta
Well, looking at the build.prop I have, am running Cognition 0.6 rom... it has a line of ro.product.brand=cingular_us...
I wonder if we could just change that line to the sprint version (maybe sprint_us, not sure exactly what it's value is but we should be able to find out), reboot the phone, setup wallet, set the line back, reboot and have working wallet.... anyone want to try it?
centex99 said:
Well, looking at the build.prop I have, am running Cognition 0.6 rom... it has a line of ro.product.brand=cingular_us...
I wonder if we could just change that line to the sprint version (maybe sprint_us, not sure exactly what it's value is but we should be able to find out), reboot the phone, setup wallet, set the line back, reboot and have working wallet.... anyone want to try it?
Click to expand...
Click to collapse
I remember that I could get Google Wallet to work on my Galaxy SIII by changing the phone name in the build.prop to HTC RAIDER and it would work.
I can't seem to find the thread that detailed how to do it, but I bet with a rooted ROM you could use the same hack and install via the APK
giving it a shot
There were two lines I think in the build.prop related to at&t... may want to compare build.props against a sprint phone.... let me know how it goes...
veritas2884 said:
I remember that I could get Google Wallet to work on my Galaxy SIII by changing the phone name in the build.prop to HTC RAIDER and it would work.
I can't seem to find the thread that detailed how to do it, but I bet with a rooted ROM you could use the same hack and install via the APK
Click to expand...
Click to collapse
Go to this thread
http://forum.xda-developers.com/showthread.php?t=2245776
I got in touch with the dev who got wallet working on the s3, he is working on it for the s4 and the One as well.
I've tried all the build prop edits, along with Modaco toolkit using Xposed framework and removing carrier/root checks. Still nothing. Leads me to believe we need some files from the Sprint HTC One like the S3 needed to get this working.
nest75068 said:
Go to this thread
http://forum.xda-developers.com/showthread.php?t=2245776
I got in touch with the dev who got wallet working on the s3, he is working on it for the s4 and the One as well.
I've tried all the build prop edits, along with Modaco toolkit using Xposed framework and removing carrier/root checks. Still nothing. Leads me to believe we need some files from the Sprint HTC One like the S3 needed to get this working.
Click to expand...
Click to collapse
I've pulled all the nfc libs/files from the sprint ROM as per the other workarounds that have gotten google wallet working and flashed them, changed build.prop, installed all the modded wallet apks i could find as well as the play store version, but it never gets past the first screen (logcat showed a No Secure Element Error). I've recently, however, been told that the Secure Element is located in the micro sim, which currently i don't have (i'm using a cut mini sim, so ISIS doesn't even work. Can anyone check to see if ISIS will install for them?). Here is the flashable package iwth the nfc libs/files from the Sprint ROM, if anyone would like to try to see if it will utilize the secure element in the sim (it will still require the other workarounds, I'm guessing).
Keep in mind this is from the original ROM, before their update yesterday (or two days ago) that enabled wallet. Once i find a dump from the update, i'll redo the flashable with the most current files.. ah i see there's one posted, downloading now... will have a new flashable shortly.. i'm also gonna check out the new build.prop to see what, if any, changes happened there that might be necessary.
Edit: removed this one. New one will be up in about 15 minutes
homeslice976 said:
I've pulled all the nfc libs/files from the sprint ROM as per the other workarounds that have gotten google wallet working and flashed them, changed build.prop, installed all the modded wallet apks i could find as well as the play store version, but it never gets past the first screen (logcat showed a No Secure Element Error). I've recently, however, been told that the Secure Element is located in the micro sim, which currently i don't have (i'm using a cut mini sim, so ISIS doesn't even work. Can anyone check to see if ISIS will install for them?). Here is the flashable package iwth the nfc libs/files from the Sprint ROM, if anyone would like to try to see if it will utilize the secure element in the sim (it will still require the other workarounds, I'm guessing).
Keep in mind this is from the original ROM, before their update yesterday (or two days ago) that enabled wallet. Once i find a dump from the update, i'll redo the flashable with the most current files.. ah i see there's one posted, downloading now... will have a new flashable shortly.. i'm also gonna check out the new build.prop to see what, if any, changes happened there that might be necessary.
Click to expand...
Click to collapse
Once you get the new package I'll try flashing and see what happens.
I can install Isis from the Play store, but it won't let me initialize cause I'm rooted. Also not sure if my micro sim has a secure element or not(since I am not located in one of the test markets).
nest75068 said:
Once you get the new package I'll try flashing and see what happens.
I can install Isis from the Play store, but it won't let me initialize cause I'm rooted. Also not sure if my micro sim has a secure element or not(since I am not located in one of the test markets).
Click to expand...
Click to collapse
I can't even install ISIS..tells me my device is unsupported. So since you can, my guess is you do have a secure element. I was told by a chat representative yesterday (I know, taken with a grain of salt), that all of ATT's micro SD's have a secure element.
10 minutes left on the download, then some comparison, then I'll have a flashable
homeslice976 said:
I can't even install ISIS..tells me my device is unsupported. So since you can, my guess is you do have a secure element. I was told by a chat representative yesterday (I know, taken with a grain of salt), that all of ATT's micro SD's have a secure element.
10 minutes left on the download, then some comparison, then I'll have a flashable
Click to expand...
Click to collapse
Ok, I'm making a Nandroid right now, I'm going to try the flashable zip you already included to see if that works.
I'm going to update my build prop to one of the following and see if that bypasses it
ro.product.model=Galaxy Nexus
ro.product.name=yakju
ro.product.device=maguro
ro.product.model=htc_jewel
ro.product.name=htc_jewel
ro.product.device=htc_jewel
Both of those worked for the S3
nest75068 said:
Ok, I'm making a Nandroid right now, I'm going to try the flashable zip you already included to see if that works.
I'm going to update my build prop to one of the following and see if that bypasses it
ro.product.model=Galaxy Nexus
ro.product.name=yakju
ro.product.device=maguro
ro.product.model=htc_jewel
ro.product.name=htc_jewel
ro.product.device=htc_jewel
Both of those worked for the S3
Click to expand...
Click to collapse
yea i tried both of those, as well as M7WLS, m7wls, m7wls (as in Sprint's build.prop), and none worked - but again, I think it's a different issue for me
ok. i forgot that flashable had an issue. after you flash, nfc probably will be greyed out and won't turn on - go to /system/lib/hw/ and change nfc.m7wls.so to nfc.m7.so and reboot
or just wait for the new one and I'll have that issue fixed...
a
homeslice976 said:
yea i tried both of those, as well as M7WLS, m7wls, m7wls (as in Sprint's build.prop), and none worked - but again, I think it's a different issue for me
ok. i forgot that flashable had an issue. after you flash, nfc probably will be greyed out and won't turn on - go to /system/lib/hw/ and change nfc.m7wls.so to nfc.m7.so and reboot
or just wait for the new one and I'll have that issue fixed...
a
Click to expand...
Click to collapse
Already flashed it, I'll update the settings. Going through Android is upgrading right now
Wallet installed, and it is sitting at the setting up wallet screen(where it always does)
So looks like those lib files are a no go.
nest75068 said:
Already flashed it, I'll update the settings. Going through Android is upgrading right now
Click to expand...
Click to collapse
here's a flashable package with the libs/app/files from yesterday's Sprint update. build.prop changes in the update appeared to be negligible (just changes in version numbers, etc).
I'm not sure how long this has been going on but I was on a call to customer service last night trying to get the WatchESPN app running properly on my phone and the "tier 2" technician asked if it would be okay to take control of my phone. I've been in the IT field quite some time and I knew he was asking to remote into my phone (ala pcAnywhere.)
I gave him permission and quickly got a text message saying vdm (Verizon desktop manager?) was trying to connect. I'm rooted with Dubbsy's 4.2.2 GPE ROM and I was nervous about a Verizon rep snooping around my phone (warranty concern.) I'm not sure if it was the ROM or the fact that I was in a bad cell area, but he was never able to connect. We never did get the app to run properly either.
Just giving people a heads up about Verizon's (new???) capability; I've never had anyone ask me in over three years with the company. Careful rooted users, if they see you've rooted they may make a notation (with or without telling you) in your account and when you bring your phone in for service--it may get declined.
Pretty scary stuff. At least they can't get in unattended (we hope?)
I wonder which apk performs this. I'd like to freeze it.
asharad said:
I wonder which apk performs this. I'd like to freeze it.
Click to expand...
Click to collapse
Verizon remote diagnostics...or something similiar to that. I have seen it a couple of times.
Aetherpal
It doesn't work in my builds because the only thing I keep from Verizon is their apns and service. They can keep the bloat and locked down updates. Especially their big brother program...
sent from my GE gs4
It's been around since about the second release for the S3. Nothing new.
asharad said:
I wonder which apk performs this. I'd like to freeze it.
Click to expand...
Click to collapse
Erisnoob said:
Verizon remote diagnostics...or something similiar to that. I have seen it a couple of times.
Click to expand...
Click to collapse
magneticzero said:
Aetherpal
Click to expand...
Click to collapse
I did some research on this and, apparently, it's been around for about 18 months and you're both right:
Verizon Remote Diagnostics
Aetherpal teardown
Aetherpal can/does check for root access. There's two good things about this service. First, you can simply refuse the assistance from the customer support. Second, there's a terms of service you have to accept even if you gave permission for them to remote desktop. You can reject the ToS. I haven't had a TW ROM installed on my phone for a long time, so maybe someone else can post a screen of which .apk(s) they can freeze in TiBu.
Dubbsy said:
It doesn't work in my builds because the only thing I keep from Verizon is their apns and service. They can keep the bloat and locked down updates. Especially their big brother program...
Click to expand...
Click to collapse
+1
docnok63 said:
I did some research on this and, apparently, it's been around for about 18 months and you're both right:
I haven't had a TW ROM installed on my phone for a long time, so maybe someone else can post a screen of which .apk(s) they can freeze in TiBu.
Click to expand...
Click to collapse
Verizon Remote Diagnostics shows up as com.Aetherpal.device on my stock phone...
i just removed that aetherpal apk from /system/app when i removed all that crappy bloat the day i got the phone
Lookout Security keeps throwing up a notification that says the following:
Prevention Information
An application has been forced to stop for an unauthorized attempt to access system in your device. It may be safe to delete an application obtained from an unauthorized route. Check now?
Click to expand...
Click to collapse
When I click OK, though, it just takes me to a list of applications, with no further guidance about which app it is. Anyone know what this is, what it means, and how to rectify it?
jrtoastyman said:
Lookout Security keeps throwing up a notification that says the following:
When I click OK, though, it just takes me to a list of applications, with no further guidance about which app it is. Anyone know what this is, what it means, and how to rectify it?
Click to expand...
Click to collapse
Its not look out it is the Knox software on your phone. I used to get it until I did what is posted here.
http://forum.xda-developers.com/showpost.php?p=47141522&postcount=30
copc said:
Its not look out it is the Knox software on your phone. I used to get it until I did what is posted here.
http://forum.xda-developers.com/showpost.php?p=47141522&postcount=30
Click to expand...
Click to collapse
Ah, OK, saw the shield icon and assumed it was lookout. Thanks!
jrtoastyman said:
Ah, OK, saw the shield icon and assumed it was lookout. Thanks!
Click to expand...
Click to collapse
Is rooting the device the only way to get rid of this? Is there a way without root to disable this?
if you are with sprint, if you read the Sprint TOS that you signed when you got the phone it says that rooting will not void your warranty they just ask that u put it back to stock when upgrading or having service done to it. Who has ever went to upgrade their phone and the rep put it in to download mode to check something like that? And when I had my s2 rooted and needed service on the ear piece I just left cm 10 and all my stuff just the way it was and they never said anything to me about it.
Sent from my SM-N900P using XDA Premium 4 mobile app
wolverinesfan35 said:
I just left cm 10 and all my stuff just the way it was and they never said anything to me about it.
Click to expand...
Click to collapse
I forgot to move my rooted tether app from my home screen and took it for service. The rep looked down, looked up at me, and went to a different screen to work from. Classic.
yeah, when I went to Sprint to have my last phone looked at, the rep asked me point blank if the phone was rooted -- but it was not in an accusatory way, it was more a "I need to know for the purposes of what I'm doing." Did not get the sense from the way she asked that it would have made a bit of difference to her in terms of whether they would still work on the phone.
As an aside, does anyone know what exactly could be causing the alert? It popped up when I was logged onto an airport wifi network, which gives me some concern.
jrtoastyman said:
yeah, when I went to Sprint to have my last phone looked at, the rep asked me point blank if the phone was rooted -- but it was not in an accusatory way, it was more a "I need to know for the purposes of what I'm doing." Did not get the sense from the way she asked that it would have made a bit of difference to her in terms of whether they would still work on the phone.
As an aside, does anyone know what exactly could be causing the alert? It popped up when I was logged onto an airport wifi network, which gives me some concern.
Click to expand...
Click to collapse
It is a known issue, not by Lookout, but Knox AND a fix is coming from Sprint. Many threads to be found.
toenail_flicker said:
Many threads to be found.
Click to expand...
Click to collapse
Ah, you know, I did search before I posted, but I was searching for "Lookout." My bad.
jrtoastyman said:
Ah, you know, I did search before I posted, but I was searching for "Lookout." My bad.
Click to expand...
Click to collapse
Not just you. A lot of folks think it's Lookout. Just letting you know the info is out there.
I have a tough time getting reasonable search results on the forum, but that's just me. I do search anyway, every time.