LEM12 Pro A10 Official Support

[pablo11]

Google translate should work…
I will test it.
Google calendar cannot work because of the stock calendar app and the calendar storage provider sync app, which is not in the system like the older watches.

[wulfman]

Many thanks, I had already tried the AVRP change to 1.6 but it didn’t help. I changed the audio codec and it may have improved a bit but I haven’t tested enough. Since it drops when you cover the face with your hand, it is apparent that the signal is coming more out of the glass and less out the metal sides of the watch in a somewhat directional way .This explains why I get drops riding a bike as the watch face points outwards and is on the other side of my arm. Btw, I have a soft bracelet and not a metal one. I am waiting for a Prime-2 and it will be interesting to see how the BT performs outward from a bigger screen. I assume that these are BT class 2 devices and I guess to really solve the problem, it will be with a class-1.5 implementation and a bigger battery to support it. Until then…

[wulfman]

Many thanks, I managed to get all the interactive buttons to work with the new pkg and cls names except the Phone. I am not sure what pkg name to use. I tried “dialer”, “phone” “telephony”…but none worked. The package name app gave the cls for all these as “null” so I tried to put nothing in the space, tried to delete the cls entry and also tried to put in “null” as the cls. I am tired of the trial and error novice approach. any suggestions?

[noidremained]

try this:

Watch face and engine Q&A for Prime 2 and A10

If anyone is looking for the code for putting a phone button on their watch face I am posting here as it was not working on a watch face I was trying to fix for the Prime 2. I could not get the information from the “Package Names” app I usually use to obtain that nor could I get it from “MyApk Pro” app which is a similar app. I found it in the /system/media/insideClockSkin folder in Clock 6 which was the only one which comes with the Prime 2 that has a phone button on the clock face. Here is…

[Cybereu]

Ordered one on Aliexpress, will get in hands about 30 days from today, fingers crossed.
Does this smartwatch is root capaeble ?

[pablo11]

Root access on Android 10 is pointless.
We have it and published it.
But removed it because people didn’t understand that root access on A10 is purely systemless…
Check it out on google

[wulfman]

Just to confirm…I still have the problem with the stock alarm setting one hour ahead. I downloaded the google alarm clock and it also sets one hour ahead. So I guess the problem is with an internal clock address or array somewhere in A10?

[wulfman]

Many thanks. All the interactive buttons on my clock face now work.

[Eric_Crochemore]

Have you used manual timezone and checked dst ?

[pablo11]

Yeah, that’s the way.
Check Timezone and DST…

[lrr]

Hello,
I’ve tested Translate again, this is what I get from logcat after it crashes, I never succeeded in getting it up and running:
--------- beginning of crash
11-25 23:52:59.933 6172 6172 E AndroidRuntime: FATAL EXCEPTION: main
11-25 23:52:59.933 6172 6172 E AndroidRuntime: Process: com.google.android.apps.translate, PID: 6172
11-25 23:52:59.933 6172 6172 E AndroidRuntime: java.lang.ClassCastException: android.widget.FrameLayout cannot be cast to com.google.android.libraries.material.aspectratio.FixedAspectRatioFrameLayout
11-25 23:52:59.933 6172 6172 E AndroidRuntime: at com.google.android.libraries.material.accountswitcher.SelectedAccountHeader.d(PG:5)
11-25 23:52:59.933 6172 6172 E AndroidRuntime: at fgg.a(Unknown Source:51)
11-25 23:52:59.933 6172 6172 E AndroidRuntime: at kf.onApplyWindowInsets(PG:2)
11-25 23:52:59.933 6172 6172 E AndroidRuntime: at android.view.View.dispatchApplyWindowInsets(View.java:10528)
11-25 23:52:59.933 6172 6172 E AndroidRuntime: at android.view.ViewGroup.dispatchApplyWindowInsets(ViewGroup.java:7266)
11-25 23:52:59.933 6172 6172 E AndroidRuntime: at kp.N(PG:2)
11-25 23:52:59.933 6172 6172 E AndroidRuntime: at androidx.drawerlayout.widget.DrawerLayout.onMeasure(PG:23)
11-25 23:52:59.933 6172 6172 E AndroidRuntime: at android.view.View.measure(View.java:24746)
11-25 23:52:59.933 6172 6172 E AndroidRuntime: at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:6903)
11-25 23:52:59.933 6172 6172 E AndroidRuntime: at android.widget.FrameLayout.onMeasure(FrameLayout.java:194)
11-25 23:52:59.933 6172 6172 E AndroidRuntime: at android.support.v7.widget.ContentFrameLayout.onMeasure(PG:23)
11-25 23:52:59.933 6172 6172 E AndroidRuntime: at android.view.View.measure(View.java:24746)
11-25 23:52:59.933 6172 6172 E AndroidRuntime: at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:6903)
11-25 23:52:59.933 6172 6172 E AndroidRuntime: at android.widget.FrameLayout.onMeasure(FrameLayout.java:194)
11-25 23:52:59.933 6172 6172 E AndroidRuntime: at android.view.View.measure(View.java:24746)
11-25 23:52:59.933 6172 6172 E AndroidRuntime: at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:6903)
11-25 23:52:59.933 6172 6172 E AndroidRuntime: at android.widget.FrameLayout.onMeasure(FrameLayout.java:194)
11-25 23:52:59.933 6172 6172 E AndroidRuntime: at android.view.View.measure(View.java:24746)
11-25 23:52:59.933 6172 6172 E AndroidRuntime: at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:6903)
11-25 23:52:59.933 6172 6172 E AndroidRuntime: at android.widget.LinearLayout.measureChildBeforeLayout(LinearLayout.java:1552)
11-25 23:52:59.933 6172 6172 E AndroidRuntime: at android.widget.LinearLayout.measureVertical(LinearLayout.java:842)
11-25 23:52:59.933 6172 6172 E AndroidRuntime: at android.widget.LinearLayout.onMeasure(LinearLayout.java:721)
11-25 23:52:59.933 6172 6172 E AndroidRuntime: at android.view.View.measure(View.java:24746)
11-25 23:52:59.933 6172 6172 E AndroidRuntime: at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:6903)
11-25 23:52:59.933 6172 6172 E AndroidRuntime: at android.widget.FrameLayout.onMeasure(FrameLayout.java:194)
11-25 23:52:59.933 6172 6172 E AndroidRuntime: at com.android.internal.policy.DecorView.onMeasure(DecorView.java:742)
11-25 23:52:59.933 6172 6172 E AndroidRuntime: at android.view.View.measure(View.java:24746)
11-25 23:52:59.933 6172 6172 E AndroidRuntime: at android.view.ViewRootImpl.performMeasure(ViewRootImpl.java:3135)
11-25 23:52:59.933 6172 6172 E AndroidRuntime: at android.view.ViewRootImpl.measureHierarchy(ViewRootImpl.java:1903)
11-25 23:52:59.933 6172 6172 E AndroidRuntime: at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:2203)
11-25 23:52:59.933 6172 6172 E AndroidRuntime: at android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:1791)
11-25 23:52:59.933 6172 6172 E AndroidRuntime: at android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:7867)
11-25 23:52:59.933 6172 6172 E AndroidRuntime: at android.view.Choreographer$CallbackRecord.run(Choreographer.java:967)
11-25 23:52:59.933 6172 6172 E AndroidRuntime: at android.view.Choreographer.doCallbacks(Choreographer.java:791)
11-25 23:52:59.933 6172 6172 E AndroidRuntime: at android.view.Choreographer.doFrame(Choreographer.java:726)
11-25 23:52:59.933 6172 6172 E AndroidRuntime: at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:952)
11-25 23:52:59.933 6172 6172 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:883)
11-25 23:52:59.933 6172 6172 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:100)
11-25 23:52:59.933 6172 6172 E AndroidRuntime: at android.os.Looper.loop(Looper.java:214)
11-25 23:52:59.933 6172 6172 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:7386)
11-25 23:52:59.933 6172 6172 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
11-25 23:52:59.933 6172 6172 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:492)
11-25 23:52:59.933 6172 6172 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:980)

[pablo11]

@none what do you think about this?
I think it is a google dependency. Maybe

[yoyolemz]

The watch checked for firmware updates and successfully downlaoded ota and installed version 6 dated 202001102.
But now the watch overheats when charging and will not switch on at all. It is unusable, blank screen. Version 6 update seems to have "bricked " the watch.
Please any ideas on how to fix this?

[pablo11]

Factory reset.
Always after an OTA update
V6 is fine

[yoyolemz]

Thank you. Confirming I simply followed the instructions on the watch as it successfully completed the OTA firmware update to V6. Are there any options to unbrick the watch?

[pablo11]

Press and hold power key for 30 seconds to force a boot and then factory reset

[pablo11]

If this fails you can just flash the firmware manually

[yoyolemz]

Thank you. Yes tried power button held, but failed. Meaning the watch did not turn on at all unfortunately.

[pablo11]

That is unfortunate.
So now your choice is to flash the firmware using a Windows PC or return the watch to the vendor.

[yoyolemz]

Thank you for your help. Much appreciated. But failed, the PC could not find the watch to flash. Image of successful completion a few days ago to vers 06.
And image no find watch to flash