Messages

1

Cosmo Communicator - Hardware / Rooting the Cosmo Communicator

« on: March 27, 2020, 07:28:40 am »

I'm using Ninji's images which I flashed by using SP Flash Tool. It would be really nice if someone could upload the new boot (Magisk patch installed) and system images to somewhere again. Otherwise I don't know how to flash the update because the installation by using the official flashing tool fails. I don't know if the OTA zip file is flashable via fastboot?

Replying to my post: I was able to update from rooted V19 to V20 by re-flashing Ninji's V19 images and original (unrooted) boot img using SP Flash Tool. Then I did the upgrade manually by putting OTA.zip into phone's storage root and flashing it by using PlanetCom's update tool in Android (accessible via Settings). Upgrade was OK now. After that I re-flashed the rooted boot img provided by PlanetCom.

2

Cosmo Communicator - Hardware / Rooting the Cosmo Communicator

« on: March 26, 2020, 11:20:23 am »

I'm using Ninji's images which I flashed by using SP Flash Tool. It would be really nice if someone could upload the new boot (Magisk patch installed) and system images to somewhere again. Otherwise I don't know how to flash the update because the installation by using the official flashing tool fails. I don't know if the OTA zip file is flashable via fastboot?

3

Cosmo Communicator - General Discussion / Poor battery life

« on: February 16, 2020, 01:23:14 pm »

What about just disabling the Amoledison app. Should solve the problem and it is not useful anyways.

There isn't app called Amoledison? There's an app called LEDison but the wakelock has nothing to do with that. However I've tried to disable or remove LEDison app but it didn't help.

So, might this app help: https://f-droid.org/de/packages/com.suyashsrijan.forcedoze/ ?

I doubt that because Cosmo can't enter full sleep mode. I tried to use following commands in the shell to force the device into sleep:
dumpsys battery unplug
dumpsys deviceidle force-idle
dumpsys deviceidle enable
And it worked with Gemini PDA and my another Androidn phone just fine but in Cosmo it didn't work: the device is not sleeping properly.

4

Cosmo Communicator - General Discussion / Poor battery life

« on: February 13, 2020, 03:01:54 am »

1. Someone noticed that after CoDi had become a (temporary?) brick after a failed FW update, the wakelock was gone.

2. Has anyone checked if the shutdown of the CoDi helps here?

3 .Someone also mentioned that the fingerprint sensor LEDs stay on all the time. However, I have noticed that they have

- Double blue: Device unlocked
- Double red: Device locked

4. Anyway, after a while (5 mins?) of "double red", Codi turns off completely and the LEDs also turn off. I don't have the device on hand right now but I think it should be checked whether the wakelock is still there when the cover display & leds are totally off..

1. Yes, most probably because then the CoDi is completely shutdown / dead.
2. Yes, it doesn't help. The AmoledisonThread wakelock is still present even CoDi is not used / turned off.
3. Yes, but sometimes those lights will remain on (without any reason) even CoDi display turns off / blanks. This is a bug because restart of CoDi or sometimes opening the cover usually fixes it.
4. Yes, I've double checked this multiple times. I haven't found any case or scenario where the AmoledisonThread is gone and Cosmo enters deep sleep (CPU freq: 0) properly. Only what I've heard that if the CoDi is totally dead / bricked: then AmoledisonThread is not present (maybe because it's unable to communicate with the CoDi at that state and it turns off itself?).

5

Cosmo Communicator - General Discussion / Poor battery life

« on: February 13, 2020, 02:08:17 am »

If someone has rooten phone (mine is not yet, but i do know the app quite well from my sg7), he can try reduce / block wake locks using this:
https://forum.xda-developers.com/xposed/mod...elocks-t2853874

To prove the concept then mail it to developers.

This was my idea as well and I even tried WakeBlock instead of this (since it's actively developed and supported). But AFAIK the Amplify has the same "weakness" than WakeBlock has: It's unable to list or block kernel level wakelocks. And I think AmoledisonThread is holding that kind of lock because it's not shown in WakeBlock.

6

Cosmo Communicator - General Discussion / Poor battery life

« on: February 11, 2020, 02:08:34 am »

For me it's not NFC related.

What I found, ccmni_md1 kernel wakelock nad PhoneWindowManager.mPowerKeyWakeLock partial wakelock keep the device awake most of the time...

FIXED! Dear members, I found the solution! After unplugging charger just open the device and press Fn+Esc twice! That's a bug with looping power button!

Do you mean your device is going to deep sleep now (CPU freq: 0)? Using GSam Battery Monitor you should be able to verify this.

I tried your solution but my Cosmo still isn't deep sleeping / suspending properly (CPU freq: 0), there's always 'AmoledisonThread' keeping PARTIAL_WAKE_LOCK which (AFAIK) prevents the device to suspend (can be checked by using command: "dumpsys power").

7

Cosmo Communicator - CoDi / Controlling the CoDi from Android CLI / adb

« on: February 04, 2020, 06:14:19 am »

Has anyone figured out / reverse engineered how the CoDi could be controlled from the Android CLI / adb? AFAIK the Android is communicating with the CoDi via some serial interface, am I right? I'm wondering if there were some methods to manually trigger some kind of functions like turning on/off/restarting CoDi, changing the colors two status LEDs etc.

This could be as easy as echoing some bytes from the bash shell to certain devices under /dev/ or /sys/ but I haven't found the correct destinations yet.

8

Cosmo Communicator - General Discussion / Poor battery life

« on: February 01, 2020, 12:33:27 pm »

PowerManagerService wakelocks is the over arching description afaik and I seemed to hit a brick wall with finding what is causing the issue!

My device had a hot moment the other day and it appeared to be due to poor signal on sim 2 which reminded me of a couple of devices my wife has had that when they have been in her locker at work they get really warm and drain like crazy and we assume it is because it has no signal....

I had a look at the time spent in different cpu states the other day & it looked like it was running at the lowest frequency most of the time!

I executed "dumpsys power" via adb and there is this PARTIAL_WAKE_LOCK present always and it's blocking the device going to completely in sleep mode (CPU freq 0 etc.):

Wake Locks: size=1
  PARTIAL_WAKE_LOCK              'AmoledisonThread' (uid=1000 pid=1131)

I pretty certain it's related to communication with the CoDi. And according this web page: https://developer.android.com/reference/and...os/PowerManager PARTIAL_WAKE_LOCK blocks the Android going fully in suspend / "real" deep sleep mode. According BetterBatteryStats the CPU is on all the time and most of the time it's at its lowest CPU freq (when the device is not used).

I really hope this is a bug and not a feature. It's too bad if Cosmo is designed in such a way that it's not able to sleep correctly.  

9

Cosmo Communicator - General Discussion / Poor battery life

« on: January 31, 2020, 04:26:24 am »

They are not deep sleeping.....

Equally there is some odd behaviour with regard to the charging circuit as sometimes the better battery app is showing the device plugged in when it isn't!

I think you're correct. I've been using BetterBatteryStats or GSam and they both report the device never goes to sleep (not even into "light sleep" seen in GSam). My Gemini PDA goes in sleep mode OK. I've struggled with this kind of issue before, with other Android phones years ago but I can't remember how did I manage to find the root cause / application which prevents the device going to sleep. I can see from BetterBatteryStats (Kernel Wakelocks) that PowerManagerService.WakeLocks is 100% but don't know how to proceed from there, need to investigate this more deeply.

Maybe this is intentional behaviour? If PlanetCom's Android is configured to be awake all the time because of otherwise CoDi doesn't work? But if I disable the CoDi the device is still awake all the time... Anyway, if his intentionally configured feature or not this is so wrong. My experience is that if Android does not sleep at all it will use all the power from the battery like in 1/5th of the time vs. if the sleeping is working correctly.  

10

Cosmo Communicator - Hardware / Auto-rotate.

« on: January 31, 2020, 04:23:39 am »

I posted this message into Gemini Planet's Facebook group as well but it might be good idea to post it here as well:

"I'm 100% sure the automatic screen rotation used to work with my Cosmo with the stock FW version (V15) installed: After I ticked "Force landscape" and "Force portrait" modes off from App bar's settings the automatic screen rotation worked when I rotated the device. After I upgraded the FW to V19 it stopped working. The only way to rotate the screen is manually trigger it from the App bar: "Force Rotate".
And I just verified the automatic screen rotation is working with the same settings in my Gemini PDA. So I assume this is a bug in Cosmo's latest firmware(s)?
Luckily I was able to create a workaround by using Tasker to force the screen oriantation to landscape or to portrait mode, depending the state of "orientation sensor". Now the screen is rotating automatically if I rotate the device. But still I think this is a bug in Cosmo's Android. I've reported this issue to PlanetCom, let's see what they'll respond..."

And here are the screenshots how I implemented this in Tasker: https://imgur.com/a/MrcMDub