We would love to take a crack at this phone but unfortunately we don't have one yet.

In terms of the software and hardware though how is the quality? Is there any button lag, is the software fluid and fast? How does it compare to an LG Classic or Exalt?

[Login to see the link] [Login to see the link]

I just had our secretary order 3 of them for our developers. Let's see what we can do.

  • darthLevel 6 - Platinum Elite Member

    • Post #47

    There is no button lag. When you disable apps the icon disappears and the other ones shift in the grid (unlike the awkward blank space in the classic). Buttons are good and has plastic in between them so you shouldn't have the buckling issue that Ive had with the classic. Has extra buttons which could be utilized if we got button mapper working. I havent actually used the phone as a phone yet but the texting has kt9, I havent found a way to add to the dictionary. Any other specific questions?

    Thanks for the response, it sounds like a high quality piece, so once they come and our developers get a crack at it we will see if we can start loading up some kosher apps on it.

      Apps4Flip-Admin Yeah, it's pretty high quality, maybe even nicer than LG Classic. Charges with USB-C.

        • darthLevel 6 - Platinum Elite Member

          • Post #51

          Biden2020prez Yes. It seems like it goes into download mode (with volume up) and immediately goes out, judging by the device attached and the device detached pings from my computer.

            • darthLevel 6 - Platinum Elite Member

              • Post #53
              • Edited

              Biden2020prez I tried that. It didnt work. This is what it showed:
              Waiting for device
              Found port = COM12
              Device hw code: 0x699
              Device hw sub code: 0x8a00
              Device hw version: 0xcb00
              Device sw version: 0x2
              Device secure boot: True
              Device serial link authorization: True
              Device download agent authorization: True
              Found device in preloader mode, trying to crash...
              status is 7024
              Waiting for device
              Seemingly the device is going to preloader instead of brom, the fix to this should be some vol+/- pressing when plugging in. Issue is I cant find what to press and Im scared its something else because there are so many physical buttons (eg keypad works in recovery)

                Yes, this is pretty similar

                Using library Brom_DLL_v7.1813.3
                Engine version 1.0.0.5737
                Searching phone in normal mode;
                [connect the phone powered off with volume down and up pressed to the usb cable]
                Phone detected (MediaTek PreLoader USB VCOM (Android) (COM167)) (Driver version: 3.0.1504.0)
                Preparing to start flash mode;
                Preparing to open COM167
                Device hw code: 0699
                Device hw sub code: 8A00
                Device hw version: CB00
                Device sw version: 0002
                Device secure boot: True
                Device serial link authorization: True
                Device download agent authorization: True
                Disabling watchdog timer;
                ERROR: Timeout waiting !
                ERROR: BOOT_PHONE;

                darth I'm trying to create the same error you have (didn't have it). Please post the full adb commands you used to get that error

                  It's an interesting error. I think it usually happens when someone tries to install an update to an app but the original app didn't uninstall correctly.

                  So, I found two models of TCL phones in my warehouse(which both run Android 11). I extracted the APK for settings and tried to install it on my phone, the same thing happened to both: First, it didn't let me because it was a downgrade (not even sure why that's a downgrade.) The I did ADB install -d which allows downgrade, but I got error that the signatures didn't match. And then out of curiosity, I tried to install one Smartphone's settings APK to the other smartphone, and it had the same error. I guess TCL signs all their APK's with different signature's (never had this issue with LG).

                    I just tried the camera app from another phone and got the error Failure [INSTALL_FAILED_NO_MATCHING_ABIS: Failed to extract native libraries, res=-113]. I guess TCL signs all their com.tcl (very few exist) apps with same signature but not com.android

                    They put a lot of hurdles to install APKs, and once you get past the hurdle, there's another one waiting. Hopefully there is a bright light at the end of the tunnel...