Jump to content

_W_

Members
  • Content Count

    9
  • Joined

  • Last visited

Community Reputation

3 Neutral

About _W_

  • Rank
    New Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. @mbam_mtbr I think Customization and such are old last gen inserts. They are evolving as quickly as you can find them. Things like Online Plus, News and a few apps are always push installed by Assurance on activation, much like what Sprint does on their own branded phones. These are installed on all Assurance phone an an attempt to unify their appearance, i.e., color, wallpaper, app layout, so on, but UMX pushes something way beyond other brands. The standard Assurance installs can be disabled and they generally stay disabled, but the UMX's specific malware are very invasive. UMX is curre
  2. I hate to break it to you guys but the Wiko brand seem to have licensed their name to ANS in the US. Their parent company TInno has had an interesting past but I think is a bit better than TeleEpoch that made the UMX phone. Assurance try at all cost not to ship out Wiko phones as insisting on UMX phones. If you manage to get a Wiko phone, then you'd have to move to the T-Mobile network as they are shipped with T-Mobile network SIM now.
  3. The agents in the Philippines are clueless. T-Mobile/Sprint merger was known in the industry for sometime and many Assurance phones, even old ones, can support T-Mobile LTE network fully. It was a requirement to the Chinese phone makers. It's just a matter of sending a T-Mobile based SIM and these phones can work on T-Mobile network with not the need of a new phone. The other problem is Wiko mayhave licensed their name to ANS, so the ANS phone is now under the Wiko brand. This mess is not going away. I can't imagine with these phones causing so many problems and Assurance having to
  4. I spent some time last several weeks to track down the browser redirect on launch. The people wrote those malicious codes are savvy. I used an array of tools to monitor the Android OS but it seems the code can detect the tools are running, so it won't pop/re-direct. The moment I disable the tools, it starts to pop again. The level of maliciousness is sickening. I am working on some the methods to monitor the OS more transparently. The malware code is very deeply embedded in the OS. I think best recourse is for users to file FCC complaint and force Assurance to take responsibility and
  5. I poked around the phone some more. Whomever designed the UMX software or did the Android integration are extremely lazy and just very careless engineers if I am being nice. I found traces of settings and conduits related to Chinese cellphone carriers that should never be in a phone destined for the US, taking up storage. There are several setting themes and overlays for CMCC (China Mobile) and CT (China Telecom) they are left in the phone software. On phones destined for China, those settings allow some carrier-base information exchange, like getting plan information, data/min used/left,
  6. I thought about that but the phone is being used by a non-tech senior, so it's another layer of permission that may cause more problems. I do believe there is value in Android security update pushed by UMX sans the malware/adware in the payload. The issue is still that they have a software development process custody issue, or maybe they are doing this on purpose. Do you do block-all and then grant permission based on access attempt, or have you developed a block list (from the malware's triggered activities)? If so, can you share block list?
  7. By the way, if Assurance tell you the issue will go ahead once merged/transitioned to the T-Mobile network, then they are grossly misinforming customers. I've checked with industry contacts, the Assurance put out bids for phones knowing the Sprint network will be decommissioned. For a couple of years now, all the new phone designs are required to support all of T-Mobile LTE bands, including the latest bands, 12, 41, 66 and 71. These phones will not need to be replaced and they simply have to send you a new T-Mobile based SIM card. This means whatever backdoor and weakness will still be in
  8. A repost from me, from another thread: I work in the technical field of smartphones, including Android, so I have more than sufficient technical knowledge. I have been helping a family friend, a senior, with solving this exact issues on the U693CL. I am dumbfounded why Assurance and UMX allow this to continue to happen. I implemented some tools from the previous rounds to shutdown and clean off these malware pushes. After 3 UMX security updates, and based on behaviors I saw and tracked, I am certain the Android Security updates pushed out by UMX has weakness/vulnerabilities. It may s
  9. I work in the technical field of smartphones, including Android, so I have more than sufficient technical knowledge. I have been helping a family friend, a senior, with solving this exact issues on the U693CL. I am dumbfounded why Assurance and UMX allow this to continue to happen. I implemented some tools from the previous rounds to shutdown and clean off these malware pushes. After 3 UMX security updates, and based on behaviors I saw and tracked, I am certain the Android Security updates pushed out by UMX has weakness/vulnerabilities. It may seen like it cleaned off some malware but in
Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.