Jump to content
SAU Community

Recommended Posts

Spam on Android Phone

Hey all,

I use a Google phone (An LG Nexus 5X), I use the Chrome browser to view all websites, including SAU.
I can browse for an hour straight on normal sites, not an issue, but the moment I get to SAU my phone is highjacked by spam off to "You've won a new phone" "You've won this" etc etc

It's a royal pain in the ass, and it's stopping me from browsing to SAU, and considering most of my SAU time is done these days off my mobile phone, that's a real PITA!

Has anyone else come across this?

  • Like 1
Link to comment
https://www.sau.com.au/forums/topic/467497-spam-on-android-phone/
Share on other sites

Yeah this has been a doozy. We've had a few reports but cannot replicate the issue at all. I'm on Android and use Chrome and currently not getting any issues at all but I have seen them in the past. Our ad partner is reputable and wont just add any ads at all, so you can rest assured that the ad code is solid. 

Can you post some links where its happening for sure?

Have you tried the app?

I was actually going to post this up aswell, I'm on Apple iOS and I get redirects to tulpaserv or something, then onto this free phone crap.

I don't use Chrome, I just use the iOS Safari. Seems to happen only when I hit the frequently visited sites tile, rather than typing the SAU address directly.

Pretty annoying!

I also don't use the app because I find it uses too much data compared to just using safari....wierdly?

  • Like 1

I'm not sure if it's ads or not Christian. It does a complete redirect to a different site, then puts a popup on. Makes the phone vibrate like crazy.

It is honestly more like spam than from the ad server. But it only happens on Sau 

I get it mostly going to say.com.au, but also sometimes get it when I follow a link to a different section of the site or into a thread.

When I hit the back button my phone won't even Register that I was on the site I wanted (so it seems like its getting into your headers and copping a redirect somewhere)

So say I'm on Google.com.au and then I type into the address bar Sau.com.au I end up at a set of tulpaserv.com or some such, smash the back button and I'm straight back to google.com

Next time it pops up I'll screen shot it

  • Like 1

I got hit just now with this one:

 

Screenshot_20161031-061344.png

 

Unfortunately I missed the second screen shot of the tulpa server part as my phone was going spastic.

This time how ever this add did kick in by: I wasalready on the forums main screen, I scrolled down and clicked into the ideas and feedback area.

It half loaded the ideas and feedback area and then redirected me.

Using the back button this time did get me straight back to the ideas and feedback section.

I get this everytime I load sau from scratch or it refreshes after I have closed chrome/android browser.

 

It will also hang when trying to load an ad (4g middle of sydney) after changing to the next page or trying to load a new subsection. refresh url and bam mega pop up instantly. or quit the current tab and load sau.com.au and get the pop up.

 

Googled around and it seems like it is coming from the ad servers (happens occasionally on other sites as well)

  • Like 1

Here is something interesting....

 

On the home wifi now...so different set of ads and no pop up.

 

Turn wifi off and use 4g and back to  pop ups. 

 

And its only when an ad for mail order international sim cards appears in the top ad box first

  • Like 1
  • 2 weeks later...
On 11/2/2016 at 8:55 PM, zebra said:

This is the one.

Got the pop up .01secs afterthis screen shot

Screenshot_20161102-205325.png

I also get this screen, but sometimes without the pop up.

The interesting part is if you try and go to that ads site, or google them, they don't seem to exist (They didn't about 2 weeks back when I looked anyway)

Hey @PranK, there's a few people on the Skylines Australia Facebook group complaining of this saying they are getting it so much they're struggling to get on to SAU to post at all.

Are we able to get a trial with ads turned off or something to see if it stops the problem for a week?

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Similar Content

  • Latest Posts

    • So this being my first contribution to the SAU forums, I'd like to present and show how I had to solve probably one of the most annoying fixes on any car I've owned: replacing a speedometer (or "speedo") sensor on my newly acquired Series 1 Stagea 260RS Autech Version. I'm simply documenting how I went about to fix this issue, and as I understand it is relatively rare to happen to this generation of cars, it is a gigantic PITA so I hope this helps serve as reference to anyone else who may encounter this issue. NOTE: Although I say this is meant for the 260RS, because the gearbox/drivetrain is shared with the R33 GTR with the 5-speed manual, the application should be exactly the same. Background So after driving my new-to-me Stagea for about 1500km, one night while driving home the speedometer and odometer suddenly stopped working. No clunking noise, no indication something was broken, the speedometer would just stop reading anything and the odometer stopped going up. This is a huge worry for me, because my car is relatively low mileage (only 45k km when purchased) so although I plan to own the car for a long time, a mismatched odometer reading would be hugely detrimental to resale should the day come to sell the car. Thankfully this only occurred a mile or two from home so it wasn't extremely significant. Also, the OCD part of me would be extremely irked if the numbers that showed on my dash doesn't match the actual ageing of the car. Diagnosing I had been in communication with the well renown GTR shop in the USA, U.P.garage up near University Point in Washington state. After some back and forth they said it could be one of two things: 1) The speedometer sensor that goes into the transfer case is broken 2) The actual cluster has a component that went kaput. They said this is common in older Nissan gauge clusters and that would indicate a rebuild is necessary. As I tried to figure out if it was problem #1, I resolved problem #2 by sending my cluster over to Relentless Motorsports in Dallas, TX, whom is local to me and does cluster and ECU rebuilds. He is a one man operation who meticulously replaces every chip, resistor, capacitor, and electronic component on the PCB's on a wide variety of classic and modern cars. His specialty is Lexus and Toyota, but he came highly recommended by Erik of U.P.garage since he does the rebuilds for them on GTR clusters.  For those that don't know, on R32 and R33 GTR gearboxes, the speedometer sensor is mounted in the transfer case and is purely an analog mini "generator" (opposite of an alternator essentially). Based on the speed the sensor spins it generates an AC sine wave voltage up to 5V, and sends that via two wires up to the cluster which then interprets it via the speedometer dial. The signal does NOT go to the ECU first, the wiring goes to the cluster first then the ECU after (or so I'm told).  Problems/Roadblocks I first removed the part from the car on the underside of the transfer case (drain your transfer case fluid/ATF first, guess who found out that the hard way?), and noted the transfer case fluid was EXTREMELY black, most likely never changed on my car. When attempting to turn the gears it felt extremely gritty, as if something was binding the shaft from rotating properly. I got absolutely no voltage reading out of the sensor no matter how fast I turned the shaft. After having to reflow the solder on my AFM sensors based on another SAU guide here, I attempted to disassemble the silicone seal on the back of the sensor to see what happened inside the sensor; turns out, it basically disintegrated itself. Wonderful. Not only had the electrical components destroyed themselves, the magnetic portion on what I thought was on the shaft also chipped and was broken. Solution So solution: find a spare part right? Wrong. Nissan has long discontinued the proper sensor part number 32702-21U19, and it is no longer obtainable either through Nissan NSA or Nissan Japan. I was SOL without proper speed or mileage readings unless I figured out a way to replace this sensor. After tons of Googling and searching on SAU, I found that there IS however a sensor that looks almost exactly like the R33/260RS one: a sensor meant for the R33/R34 GTT and GTS-T with the 5 speed manual. The part number was 25010-21U00, and the body, plug, and shaft all looked exactly the same. The gear was different at the end, but knowing the sensor's gear is held on with a circlip, I figured I could just order the part and swap the gears. Cue me ordering a new part from JustJap down in Kirrawee, NSW, then waiting almost 3 weeks for shipping and customs clearing. The part finally arrives and what did I find? The freaking shaft lengths don't match. $&%* I discussed with Erik how to proceed, and figuring that I basically destroyed the sensor trying to get the shaft out of the damaged sensor from my car. we deemed it too dangerous to try and attempt to swap shafts to the correct length. I had to find a local CNC machinist to help me cut and notch down the shaft. After tons of frantic calling on a Friday afternoon, I managed to get hold of someone and he said he'd be able to do it over half a week. I sent him photos and had him take measurements to match not only the correct length and notch fitment, but also a groove to machine out to hold the retentive circlip. And the end result? *chef's kiss* Perfect. Since I didn't have pliers with me when I picked up the items, I tested the old gear and circlip on. Perfect fit. After that it was simply swapping out the plug bracket to the new sensor, mount it on the transfer case, refill with ATF/Nissan Matic Fluid D, then test out function. Thankfully with the rebuilt cluster and the new sensor, both the speedometer and odometer and now working properly!   And there you have it. About 5-6 weeks of headaches wrapped up in a 15 minute photo essay. As I was told it is rare for sensors of this generation to die so dramatically, but you never know what could go wrong with a 25+ year old car. I HOPE that no one else has to go through this problem like I did, so with my take on a solution I hope it helps others who may encounter this issue in the future. For the TL;DR: 1) Sensor breaks. 2) Find a replacement GTT/GTS-T sensor. 3) Find a CNC machinist to have you cut it down to proper specs. 4) Reinstall then pray to the JDM gods.   Hope this guide/story helps anyone else encountering this problem!
    • So this being my first contribution to the SAU forums, I'd like to present and show how I had to solve probably one of the most annoying fixes on any car I've owned: replacing a speedometer (or "speedo") sensor on my newly acquired Series 1 Stagea 260RS Autech Version. I'm simply documenting how I went about to fix this issue, and as I understand it is relatively rare to happen to this generation of cars, it is a gigantic PITA so I hope this helps serve as reference to anyone else who may encounter this issue. NOTE: Although I say this is meant for the 260RS, because the gearbox/drivetrain is shared with the R33 GTR with the 5-speed manual, the application should be exactly the same. Background So after driving my new-to-me Stagea for about 1500km, one night while driving home the speedometer and odometer suddenly stopped working. No clunking noise, no indication something was broken, the speedometer would just stop reading anything and the odometer stopped going up. This is a huge worry for me, because my car is relatively low mileage (only 45k km when purchased) so although I plan to own the car for a long time, a mismatched odometer reading would be hugely detrimental to resale should the day come to sell the car. Thankfully this only occurred a mile or two from home so it wasn't extremely significant. Also, the OCD part of me would be extremely irked if the numbers that showed on my dash doesn't match the actual ageing of the car. Diagnosing I had been in communication with the well renown GTR shop in the USA, U.P.garage up near University Point in Washington state. After some back and forth they said it could be one of two things: 1) The speedometer sensor that goes into the transfer case is broken 2) The actual cluster has a component that went kaput. They said this is common in older Nissan gauge clusters and that would indicate a rebuild is necessary. As I tried to figure out if it was problem #1, I resolved problem #2 by sending my cluster over to Relentless Motorsports in Dallas, TX, whom is local to me and does cluster and ECU rebuilds. He is a one man operation who meticulously replaces every chip, resistor, capacitor, and electronic component on the PCB's on a wide variety of classic and modern cars. His specialty is Lexus and Toyota, but he came highly recommended by Erik of U.P.garage since he does the rebuilds for them on GTR clusters.  For those that don't know, on R32 and R33 GTR gearboxes, the speedometer sensor is mounted in the transfer case and is purely an analog mini "generator" (opposite of an alternator essentially). Based on the speed the sensor spins it generates an AC sine wave voltage up to 5V, and sends that via two wires up to the cluster which then interprets it via the speedometer dial. The signal does NOT go to the ECU first, the wiring goes to the cluster first then the ECU after (or so I'm told).  Problems/Roadblocks I first removed the part from the car on the underside of the transfer case (drain your transfer case fluid/ATF first, guess who found out that the hard way?), and noted the transfer case fluid was EXTREMELY black, most likely never changed on my car. When attempting to turn the gears it felt extremely gritty, as if shttps://imgur.com/6TQCG3xomething was binding the shaft from rotating properly. After having to reflow the solder on my AFM sensors based on another SAU guide here, I attempted to disassemble the silicone seal on the back of the sensor to see what happened inside the sensor; turns out, it basically disintegrated itself. Wonderful. Not only had the electrical components destroyed themselves, the magnetic portion on what I thought was on the shaft also chipped and was broken. Solution So solution: find a spare part right? Wrong. Nissan has long discontinued the proper sensor part number 32702-21U19, and it is no longer obtainable either through Nissan NSA or Nissan Japan. I was SOL without proper speed or mileage readings unless I figured out a way to replace this sensor. After tons of Googling and searching on SAU, I found that there IS however a sensor that looks almost exactly like the R33/260RS one: a sensor meant for the R33/R34 GTT and GTS-T with the 5 speed manual. The part number was 25010-21U00, and the body, plug, and shaft all looked exactly the same. The gear was different at the end, but knowing the sensor's gear is held on with a circlip, I figured I could just order the part and swap the gears. Cue me ordering a new part from JustJap down in Kirrawee, NSW, then waiting almost 3 weeks for shipping and customs clearing. The part finally arrives and what did I find? The freaking shaft lengths don't match. $&%* I discussed with Erik how to proceed, and figuring that I basically destroyed the sensor trying to get the shaft out of the damaged sensor from my car. we deemed it too dangerous to try and attempt to swap shafts to the correct length. I had to find a local CNC machinist to help me cut and notch down the shaft. After tons of frantic calling on a Friday afternoon, I managed to get hold of someone and he said he'd be able to do it over half a week. I sent him photos and had him take measurements to match not only the correct length and notch fitment, but also a groove to machine out to hold the retentive circlip. And the end result? *chef's kiss* Perfect. Since I didn't have pliers with me when I picked up the items, I tested the old gear and circlip on. Perfect fit. After that it was simply swapping out the plug bracket to the new sensor, mount it on the transfer case, refill with ATF/Nissan Matic Fluid D, then test out function. Thankfully with the rebuilt cluster and the new sensor, both the speedometer and odometer and now working properly!   And there you have it. About 5-6 weeks of headaches wrapped up in a 15 minute photo essay. As I was told it is rare for sensors of this generation to die so dramatically, but you never know what could go wrong with a 25+ year old car. I HOPE that no one else has to go through this problem like I did, so with my take on a solution I hope it helps others who may encounter this issue in the future. For the TL;DR: 1) Sensor breaks. 2) Find a replacement GTT/GTS-T sensor. 3) Find a CNC machinist to have you cut it down to proper specs. 4) Reinstall then pray to the JDM gods.   Hope this guide/story helps anyone else encountering this problem!
    • perhaps i should have mentioned, I plugged the unit in before i handed over to the electronics repair shop to see what damaged had been caused and the unit worked (ac controls, rear demister etc) bar the lights behind the lcd. i would assume that the diode was only to control lighting and didnt harm anything else i got the unit back from the electronics repair shop and all is well (to a point). The lights are back on and ac controls are working. im still paranoid as i beleive the repairer just put in any zener diode he could find and admitted asking chatgpt if its compatible   i do however have another issue... sometimes when i turn the ignition on, the climate control unit now goes through a diagnostics procedure which normally occurs when you disconnect and reconnect but this may be due to the below   to top everything off, and feel free to shoot me as im just about to do it myself anyway, while i was checking the newly repaired board by plugging in the climate control unit bare without the housing, i believe i may have shorted it on the headunit surround. Climate control unit still works but now the keyless entry doesnt work along with the dome light not turning on when you open the door. to add to this tricky situation, when you start the car and remove the key ( i have a turbo timer so car remains on) the keyless entry works. the dome light also works when you switch to the on position. fuses were checked and all ok ive deduced that the short somehow has messed with the smart entry control module as that is what controls the keyless entry and dome light on door opening   you guys wouldnt happen to have any experience with that topic lmao... im only laughing as its all i can do right now my self diagnosed adhd always gets me in a situation as i have no patience and want to get everything done in shortest amount of time as possible often ignoring crucial steps such as disconnecting battery when stuffing around with electronics or even placing a simple rag over the metallic headunit surround when placing a live pcb board on top of it   FML
    • Bit of a pity we don't have good images of the back/front of the PCB ~ that said, I found a YT vid of a teardown to replace dicky clock switches, and got enough of a glimpse to realize this PCB is the front-end to a connected to what I'll call PCBA, and as such this is all digital on this PCB..ergo, battery voltage probably doesn't make an appearance here ; that is, I'd expect them to do something on PCBA wrt power conditioning for the adjustment/display/switch PCB.... ....given what's transpired..ie; some permutation of 12vdc on a 5vdc with or without correct polarity...would explain why the zener said "no" and exploded. The transistor Q5 (M33) is likely to be a digital switching transistor...that is, package has builtin bias resistors to ensure it saturates as soon as base threshold voltage is reached (minimal rise/fall time)....and wrt the question 'what else could've fried?' ....well, I know there's an MCU on this board (display, I/O at a guess), and you hope they isolated it from this scenario...I got my crayons out, it looks a bit like this...   ...not a lot to see, or rather, everything you'd like to see disappears down a via to the other side...base drive for the transistor comes from somewhere else, what this transistor is switching is somewhere else...but the zener circuit is exclusive to all this ~ it's providing a set voltage (current limited by the 1K3 resistor R19)...and disappears somewhere else down the via I marked V out ; if the errant voltage 'jumped' the diode in the millisecond before it exploded, whatever that V out via feeds may have seen a spike... ....I'll just imagine that Q5 was switched off at the time, thus no damage should've been done....but whatever that zener feeds has to be checked... HTH
×
×
  • Create New...