OESF Portables Forum
Model Specific Forums => Cosmo Communicator => Cosmo Communicator - General Discussion => Topic started by: mitchelln on November 26, 2019, 05:26:53 pm
-
Is anyone else experiencing really poor battery life?
I can watch the battery percentage literally dropping as I'm using it.
It's dropping about 8% an hour even in standby with hardly any apps installed, so it'll barely make it to the morning.
Hopefully this can be improved or this simply isn't viable as a daily use device.
-
Is anyone else experiencing really poor battery life?
I can watch the battery percentage literally dropping as I'm using it.
It's dropping about 8% an hour even in standby with hardly any apps installed, so it'll barely make it to the morning.
Hopefully this can be improved or this simply isn't viable as a daily use device.
Pretty much the same for me, 100% down to 37% after 5 1/2 hours. Ok, so I did install my apps etc which used the 4G data and CPU - but the drain has continued. I've had to switch off Duraspeed to keep my Galaxy Watch connected which doesn't help.
I think Planet do need to look into this, but perhaps tomorrow it will be better - it will be the first full day of use and a more realistic test. I'll let you know what I find.
-
Unfortunately, I suspect the cover display. I'm going to turn it off and see what effect it has.
I really hope Planet take a look at this.
-
This is an important topic, and will contribute what I have been experiencing so far.
I too experience short battery life when I first received the Cosmo Communicator. The Cosmo battery was seemingly full when I first turned it on, which was strange to receive a mobile with so much battery initially. I let it drain down to 4%, which was not long, and charged it up using the USB-C (quick charging) next to the headphone input. The Cosmo charged up to 100% really quick, like in less than 2 hours. However, the battery charge declined 30% after 3 to 4 hours of no use. I then charged it using the other USB-C (regular charging), which took longer and I left it charging after it got to 100%.
Note: One initial issue I had initially with the Cosmo that might have drained power was a constantly on purple Wireless LED on the front cover above the 24mp camera.
After resolving the constantly on purple LED and charging the Cosmo using the regular charging USB-C for an hour or two beyond when it first reached 100%, I am pleased to report that today, the Cosmo battery was at 50% after ~18 hours of occasional use throughout the day (battery saver was not used), indicating that the battery can last more than a day. I am not as concerned about the Cosmo battery life after today. However, I am planning on not charging the Cosmo during the night tonight and see how long this current battery charge will last.
Tomorrow will be more heavy use as I will be traveling by train (approximately 2 hours in the morning and 2 hours in the evening) during which I will be using cellular data frequently, listening to podcasts, sending SMS, and an occasional phone call. I will be pleased if the remaining charge on this battery (currently 50%) will last through the night, during the commute tomorrow morning of moderately heavy use, and not recharging until mid-morning or mid-day tomorrow (a total of 36 hours on a single charge). If this can be achieved, then perhaps
Note: Others in this forum may not so pleased with 50% usage after ~18 hours, and may expect greater battery life.
I am wondering whether which of the following factors has a greater impact on obtaining a full charge versus consuming the battery. - Specific USB-C port is used for charging
- Duration of the charging period
- Enabling/disabling wifi, bluetooth, and cellular data when needed vs not needed
- Extent to which the Cosmo is used (light, moderate, versus heavy)
Cheers!
-
Overnight with all the radios turned off, airplane mode on and the cover display switched off, it dropped 10%. Which is a little high. My Mate 20 phone typically drops 3-4% overnight.
I'm going to try again tonight with the cover display enabled and see if that is a major source of drain.
Do you have the two blue LEDs next to the fingerprint sensor permanently on drhood?
-
Ok, based on what I have seen so far today.
I charged the device all night from the "slow" USB-C port (the one of the right hand side). So far the device has been, essentially, on standby for almost two hours - it is connected to my watch, WiFi and 4G and has received a few emails.
So far, 1% battery use. So perhaps the initial charge level calibration was borked? Wil keep you guys updated.
-
Do you have the two blue LEDs next to the fingerprint sensor permanently on drhood?
Hello - The two blue LEDs next to the fingerprint sensor are not permanently on. I notice these lights are on and blinking when playing media (e.g., a song).
-
Do you have the two blue LEDs next to the fingerprint sensor permanently on drhood?
Hello - The two blue LEDs next to the fingerprint sensor are not permanently on. I notice these lights are on and blinking when playing media (e.g., a song).
Okay, that's interesting thanks. On mine they are permanently on and I can see no way to turn them off. I tried disabling and re-enabling the cover display service, but it makes no difference.
-
I repeated the overnight standby test with radios off and airplane mode on, but this time with the cover display enabled.
This time the battery dropped a whopping 25%. So for a full day on my unit, the cover display is burning half the battery.
Clearly something isn't right. I hope Planet can sort this out.
-
Hmmm it seems things are a bit uneven here. Yesterday, was the first full day of Cosmo use.
Removed from charge at around 0800
Went to bed at around 0045 and put on charge (next morning) charge was around 38%
This was with the cover display on, Duraspeed off, Bluetooth enabled, 4G LTE, WiFi (with VoWiFi enabled) and plenty of hours of music played.
One thing I have noticed is that the cover display turns on every time there is a notification, WiFi network found - screen lights up. Watch (Bluetooth connection) connects or disconnects, screen lights up. Mobile network changes from 4G to 3G (or drops VoLTE), screen lights up. Macrodroid updates it's notification icon, screen lights up.
I understand why it does this, and I suspect it needs a blacklist (or even better a whitelist) to prevent excessive external screen initialisation.
Mitchelln, do you have any software (like Macrodroid) that adds notification icons and refreshes them regularly?
-
Nope. Nothing that keeps waking up the cover display as far as I know. It's the reason I turned the radios off and switched on airplane mode and do not disturb to hopefully stop notifications for the test.
I suspect there's something preventing the cover display CPU from sleeping properly in certain situations. I also have the two blue LEDs stuck on, which others don't. Something is not right.
-
I left my new Cosmo closed overnight, with the cover display off (no LEDs showing), and nothing running. (Nothing installed or set up, even — I've hardly touched it!)
This morning it was dead, with the battery completely empty; it wouldn't even respond until I plugged it in, and then took a while before waking up enough to flash ‘0%’ on the screen when I pressed the On button.
This does not bode well…
-
I left my new Cosmo closed overnight, with the cover display off (no LEDs showing), and nothing running. (Nothing installed or set up, even — I've hardly touched it!)
This morning it was dead, with the battery completely empty; it wouldn't even respond until I plugged it in, and then took a while before waking up enough to flash ‘0%’ on the screen when I pressed the On button.
This does not bode well…
Indeed. Just out of interest, what was the charge level when you left it for the night?
Apparently there is going to be a firmware update next week (I'll believe it when I see it though), perhaps this will be one of the sorted issues?
-
I left my new Cosmo closed overnight, with the cover display off (no LEDs showing), and nothing running. (Nothing installed or set up, even — I've hardly touched it!)
This morning it was dead, with the battery completely empty; it wouldn't even respond until I plugged it in, and then took a while before waking up enough to flash ‘0%’ on the screen when I pressed the On button.
This does not bode well…
Also did you charge it with left or right port? From this thread it seems quick charging is buggy and going for slow charge is the way for now
-
Unfortunately the right USB port doesn't seem to charge for me.
-
I've had the cosmo for about 2 weeks now, and I'm easily getting a day out of it. Off the charger (left side) at 6am, back from work around 6pm, lots of use during the evening (it is still a new toy ), and I am around 30-40%. I connect a smart watch, so I have disabled Duraspeed, and routinely turn off the cover (and LEDs) with the silver button when I close the cosmo. The display pops back when something happens (eg sms, email etc). Not had any battery issues. I will say that I completely charged it before turning on for the first time - and this must be the first time I have ever done this.....
It is 3:30pm here, and the battery is currently 70%, I have made a few phone calls, visited many web pages and read email/sms. So, 9.5 hours for 30% is about 3% per hour. Not all that bad. I have 4G data turned on, I'm connected to the corporate wifi, and my watch is connected via bluetooth.
If you are having battery problems, have you checkout out the battery settings? It can show a graph of the battery usage, and what apps have used the most etc. Oh, My screen is at about 50% brightness.
-
If you are having battery problems, have you checkout out the battery settings? It can show a graph of the battery usage, and what apps have used the most etc. Oh, My screen is at about 50% brightness.
I get the graph, but I get "data not available" below. I check here often and have never seen app data here. I wonder if there is a setting somewhere that I've got wrong.
I take it you do see the list of apps and their power usage, @vader?
-
Same here. I get no battery usage stats available.
-
My Cosmo's battery bleeds out like a guillotined French nobleman.
"Lucky" if it makes 12 hours JUST ON and little used.
Planet had the audacity to tell me that my battery performs better than all the Cosmos in their offices!
WTH?!
P.S. I regret backing this novel and severely dysfunctional thing.
-
I've had the cosmo for about 2 weeks now, and I'm easily getting a day out of it. Off the charger (left side) at 6am, back from work around 6pm, lots of use during the evening (it is still a new toy ), and I am around 30-40%. I connect a smart watch, so I have disabled Duraspeed, and routinely turn off the cover (and LEDs) with the silver button when I close the cosmo. The display pops back when something happens (eg sms, email etc). Not had any battery issues. I will say that I completely charged it before turning on for the first time - and this must be the first time I have ever done this.....
It is 3:30pm here, and the battery is currently 70%, I have made a few phone calls, visited many web pages and read email/sms. So, 9.5 hours for 30% is about 3% per hour. Not all that bad. I have 4G data turned on, I'm connected to the corporate wifi, and my watch is connected via bluetooth.
If you are having battery problems, have you checkout out the battery settings? It can show a graph of the battery usage, and what apps have used the most etc. Oh, My screen is at about 50% brightness.
After about a week of use, I report similar experience. I am getting more than a day's use out of the battery. Currently, after 22 hours, I have 25% battery remaining and Android estimates next recharge will be in 7 hours. My usage has been SMS testing, Notes App, Audio Podcasts, and web browsing (news and this forum). I recharge the Cosmo when the battery is down to less than 10% (sometimes less than 5%). The next week will include same use but with some YouTube video watching.
I will be happy with a 24+ hour battery life; however, I will appreciate any software optimizations that can make the battery last longer.
Cheers!
-
My unit, with essentially no use and all radios turned off & no SIM installed will last ~3 days from a full charge with outer screen turned off (in Cosmo Settings) and ~1.5 days with outer screen turned on- in both cases with battery saver switched off. So baseline 'standby' battery drain for the outer screen unit appears essentially the same as for the main unit...
-
Just my two cents. According to the spec sheet the battery capacity should be 4220mAh. Tested my Cosmo with a program named Ampere and got 2900mAh. Hmm. I think I missed something...
Bye for now Fred
-
Just my two cents. According to the spec sheet the battery capacity should be 4220mAh. Tested my Cosmo with a program named Ampere and got 2900mAh. Hmm. I think I missed something...
From the horse's mouth:
dumpsys battery
Current Battery Service state:
AC powered: false
USB powered: true
Wireless powered: false
Max charging current: 500000
Max charging voltage: 5000000
Charge counter: 2946000
status: 2
health: 2
present: true
level: 100
scale: 100
voltage: 4418
temperature: 230
technology: Li-ion
cat /sys/class/power_supply/battery/capacity
100
cat /sys/class/power_supply/battery/charge_full
2946000Looks like thats where number from your app come from. I am not sure how much you can rely on those numbers coming from drivers. I would only trust if someone would measure the actual charge from discharged state with a meter.
-
I've noticed that when I'm mostly home on the weekend and on WiFi, my battery lasts much longer than on weekdays when I'm commuting and on LTE (my office's corporate WiFi is too annoying to deal with so I'm on LTE all day).
Weekend at home on WiFi: from 100% at 07h30 to 30% at 10h30.
Weekday at work on LTE: from 100% at 06h30 to 5% at 10h30 (most days I give it a quick boost whilst at my desk - from say 55% to 65% - just so I can have enough to end the day at 15% or so).
I have been using it quite a lot. Reading books keeps the screen on a lot, things staying alive in background like IRC running in Termux, VoIP via MizuDroid, BT connection to Smartwatch and to BT headset.
I've also disabled DuraSpeed and allowed a few apps to run in the background un-optimized, per @vader and others' helpful advice for watch users.
One thing I have noticed with my other Li-Ion devices and with previous smartphones, battery performance does improve over time as you use them compared to out-of-the-box. I know Li-Ion is not supposed to have memory but maybe there is a break-in period?
-
Oh for goodness sake! Even switched right off after charging the Cosmo to 100% (not standby), after 3 days the battery is completely dead. Nothing ruins a lithium battery quicker than keep discharging it completely. If switching off completely isn’t an option to stop complete battery drain, then what is the answer?
This simply isn’t good enough Planet!
-
I forgot to note earlier:
Every once in awhile, some process or other consumes a lot of power. I don't know what it is, but opening / unlocking seems to resolve it.
Whatever it is, it makes the front side of the device warm, especially right under the cover display.
While I can see the sharp downturn in the Battery Usage monitor-graph, I cannot see what app is causing the drain. I always see "Battery usage data isn't available".
Does anyone else get that? I wonder if it correlates with people who have disabled DuraSpeed?
Maybe if I can figure out how to get that usage data working I can troubleshoot to find what app or process occasionally attacks my battery.
-
I'm beginning to suspect that the battery stats has been deliberately disabled to hide a problem.
-
Turn off the cover display (not sleep, completely disable it using the quicktoggle or cosmo settings). Until the firmware is updated, there is a serious problem with the display. Doing this has more than doubled my battery life, and significantly improved my standby time. I no longer need to charge every night on light days.
-
Oh for goodness sake! Even switched right off after charging the Cosmo to 100% (not standby), after 3 days the battery is completely dead. Nothing ruins a lithium battery quicker than keep discharging it completely. If switching off completely isn’t an option to stop complete battery drain, then what is the answer?
This simply isn’t good enough Planet!
As "shinkamui" says:
Turn off the cover display (not sleep, completely disable it using the quicktoggle or cosmo settings). Until the firmware is updated, there is a serious problem with the display. Doing this has more than doubled my battery life, and significantly improved my standby time. I no longer need to charge every night on light days.
As I understand it, if you don't disable it, the processor for the cover display is still "on" (and interprets things like the side button to turn the device on), and the cover display (or probably it's processor) has terrible power consumption with the current firmware... Hope that can help...
-
Maybe if I can figure out how to get that usage data working I can troubleshoot to find what app or process occasionally attacks my battery.
After a bit of checking, people say the way to resolve the "Battery usage data not available" isue is to boot in recovery mode and wipe the cache.
I tried rebooting and holding down the ESC button, holding down ESC plus Side button, and holding down just the Side button, but none of those gets me into recovery mode.
Does anyone know how to get into the recovery menu?
-
NormMonkey, won't help you much: As you I didn't find a way to enter recovery just using keys. But if your Cosmo is rooted (like mine) it's easy to enter recovery. Start Magisk, open the menu (upper left corner), start Modules, then open the 3-dot-menu in the upper right corner and "Reboot to Recovery". Well, you'll reach a black screen with a "lying around Android". At this point I got stuck again. A long press on Esc brings you back to a working Cosmo. Well, without TWRP or a cache cleaner program ( (like "Fast optimizer" by HDM Dev Team) we can't do anything.
Bye for now Fred
-
NormMonkey, won't help you much: As you I didn't find a way to enter recovery just using keys. But if your Cosmo is rooted (like mine) it's easy to enter recovery. Start Magisk, open the menu (upper left corner), start Modules, then open the 3-dot-menu in the upper right corner and "Reboot to Recovery". Well, you'll reach a black screen with a "lying around Android". At this point I got stuck again. A long press on Esc brings you back to a working Cosmo. Well, without TWRP or a cache cleaner program ( (like "Fast optimizer" by HDM Dev Team) we can't do anything.
Thanks Fred,
I haven't rooted yet. I have been watching that thread, though.
I figure things are going to change a bunch when PC has boot-to-linux ready, and I'll wait patiently for that. In the meantime I'm getting used to all the quirks and behaviour as it comes out of the box, so I have a baseline to compare to when I eventually root it. I'm just being a bit lazy and want to minimize the number of times I end up doing what amounts to a factory reset and apps reinstall and restores from backup.
I did have an idea that somewhere in Developer Options there might be a setting to cause the phone to reboot into recovery mode, but alas I could not find it.
Whilst in Developer Options, I came across this:
Developer Options : Debug : Feature Flags : settings_battery_display_app_list which was set to FALSE on mine.
I set it to true, but as yet it hasn't changed anything yet.
Could be it needs to go through a charge cycle or at least a bit of time to do data gathering, or could be it needs reboot to see the setting, or could be it isn't related and/or I still need to find a way to do the "wipe cache" thing.
-
Interesting...
Cycled battery by discharging to 5% then charging to 100% on fast charge, restarting phone disconnected from power, reconnecting to charge x 2, leaving overnight on fast charge @ 100% battery.
Now, 72 hrs later (albeit with minimal use and with outer screen & all radios turned off) battery is still @ 40%
It sounds as if, in keeping with others' observations, the battery may charge more fully or report charge more accurately after several charge/recharge cycles.
As I reported previously, to begin with I was previously getting only 72hrs from full charge to discharged under the same circumstances.
-
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!
-
Let's face it 2 screens are going to drain battery faster if you want more battery life turn front screen off simples
-
Let's face it 2 screens are going to drain battery faster if you want more battery life turn front screen off simples
That makes no sense. When the cover is closed, the main screen is off, and when the cover is open, the cover screen goes off shortly.
I've had lots of phones with two screens, all of them having better battery life even out of a smaller battery. Hell, my E90 communicator`s battery is still good for 2.5 days. And it's a 5 year old battery.
-
Let's face it 2 screens are going to drain battery faster if you want more battery life turn front screen off simples
Mine is using 3.1% per hour minimum as long as all apps are killed before closing the lid, if you leave apps running its up to 8% per hour....
as I said before it is because they are not deep sleeping!
-
Let's face it 2 screens are going to drain battery faster if you want more battery life turn front screen off simples
You think a one inch screen should use 3x as much battery on its own as a 6 inch screen and a powerful phone/computer using wifi and GSM?? Simples!
-
Updating the cover display firmware has helped to reduce the rate of battery drain.
-
Is anyone else experiencing really poor battery life?
Yes, and I find it interesting that I'm not alone with the problem.
I get usually around 6 to 7 hours from 100% to 0%. It varies, but it's usually closer to 6 hours. And that's in airplane mode, with power saving standby enabled, the cover display turned off and the lid closed. If I use it the battery is empty even quicker. Accordingly, the lid is constantly pretty warm, very hot if it's in my pocket for a while. This is "within the normal temperatures" according to support. It doesn't get noticeably warm when it's completely turned off. But the battery is still discharging in a couple of hours.
Battery usage data is not available. It looks like that's the same for every Cosmo. So I don't know why support points to the non-existing statistic. I've analysed battery usage with ADB, but as far as I can tell nothing is using a lot of CPU and I'm not sure how to interpret the rest of ADBs output to find a process that is draining the battery.
I assumed it was a problem with an app that I've installed. So I did a reset and only installed what I really needed. (My Gemini broke so I need the Cosmo almost daily.) It looked fine for the first few hours but at the end of the day the battery was empty again. I never found an app that might be at fault and the recent firmware update didn't help either. ADB is estimating the battery capacity at 1Ah, but as I understand it that estimation is usually far off, anyway.
So I'm out of ideas. Planet suggested to reset again and install the firmware updates again, which I will probably do at some point. But I don't expect anything to change.
So I guess all we can do is compare our devices and find the differences between those that work properly and those that don't. What differences are there? I doubt the keyboard plays a role, but mine is German and it's the European model. I can't think of anything else.
-
Is anyone else experiencing really poor battery life?
Yes, and I find it interesting that I'm not alone with the problem.
I get usually around 6 to 7 hours from 100% to 0%. It varies, but it's usually closer to 6 hours. And that's in airplane mode, with power saving standby enabled, the cover display turned off and the lid closed. If I use it the battery is empty even quicker. Accordingly, the lid is constantly pretty warm, very hot if it's in my pocket for a while. This is "within the normal temperatures" according to support. It doesn't get noticeably warm when it's completely turned off. But the battery is still discharging in a couple of hours.
Battery usage data is not available. It looks like that's the same for every Cosmo. So I don't know why support points to the non-existing statistic. I've analysed battery usage with ADB, but as far as I can tell nothing is using a lot of CPU and I'm not sure how to interpret the rest of ADBs output to find a process that is draining the battery.
I assumed it was a problem with an app that I've installed. So I did a reset and only installed what I really needed. (My Gemini broke so I need the Cosmo almost daily.) It looked fine for the first few hours but at the end of the day the battery was empty again. I never found an app that might be at fault and the recent firmware update didn't help either. ADB is estimating the battery capacity at 1Ah, but as I understand it that estimation is usually far off, anyway.
So I'm out of ideas. Planet suggested to reset again and install the firmware updates again, which I will probably do at some point. But I don't expect anything to change.
So I guess all we can do is compare our devices and find the differences between those that work properly and those that don't. What differences are there? I doubt the keyboard plays a role, but mine is German and it's the European model. I can't think of anything else.
what software version are you on?
mine has done 6 hours since full charge with 1 hour 4 mins screen time and is on 75%
one of the software versions properly ate the battery and was always warm as you describe but it seems better on V19
-
one of the software versions properly ate the battery and was always warm as you describe but it seems better on V19
I'm on V19 as well. I haven't noticed any change since the update. But I'll measure the time again tomorrow when I won't be using it much anyway.
-
I'm on V19 as well. I haven't noticed any change since the update. But I'll measure the time again tomorrow when I won't be using it much anyway.
After resetting I had trouble updating CoDi. But after the 8th or so attempt it finally flashed completely. I charged to 100 %, then did nothing (lid closed). After about 4 hours it's down to 43 %. Not really an improvement. To be sure, what is the current CoDi version? I'm on 1.1.1.12 now.
Edit: typo
-
I'm on V19 as well. I haven't noticed any change since the update. But I'll measure the time again tomorrow when I won't be using it much anyway.
After resetting I had trouble updating CoDi. But after the 8th or so attempt it finally flashed completely. I charged to 100 %, the did nothing (lid closed). After about 4 hours it's down to 43 %. Not really an improvement. To be sure, what is the current CoDi version? I'm on 1.1.1.12 now.
Have you tried to disable NFC?
@see: https://www.oesf.org/forum/index.php?showtopic=36003 (https://www.oesf.org/forum/index.php?showtopic=36003)
Maybe this helps for the time being.
-
Have you tried to disable NFC?
@see: https://www.oesf.org/forum/index.php?showtopic=36003 (https://www.oesf.org/forum/index.php?showtopic=36003)
Thanks for the hint! I haven't seen this post. In my battery usage recordings from ADB android.hardware.nfc@1.1-service always stayed way below 1s of CPU time. But I've disabled NFC and will see if it helps.
-
So, I did another reset and was now offered CoDi V1.1.1.13 and it got flashed quickly first try. So I guess my attempts to flash CoDi haven't actually been successful before. After that I had again half a day where the battery percentage hardly dropped and the cover did not get hot. But after a while it started again. I'm about to send the device in (need to get myself another phone first). But I'm holding back a bit because I somehow feel like I'm very close to solving this. I feel like it is a software problem indeed. Especially since at least for some it seems firmware updates have solved the problem. Maybe I'll try rooting it first.
-
It feels like a firmware problem to me, too. I'm expecting it to be fixed in a future release, and, of the bugs the software has, I hope it's the one with the highest priority.
It feels as if something is spinning, waiting for data that isn't going to come, because the other end thinks it's done. I base this only on the observation that when it gets hot, opening and closing the thing (which obviously triggers some comms between the CoDi and the main device) can fix the problem. And it usually starts again when something has triggered something which causes something to display on the CoDi.
Might be totally wrong, of course. Without the source it's impossible to say.
-
Have you tried to disable NFC?
@see: https://www.oesf.org/forum/index.php?showtopic=36003 (https://www.oesf.org/forum/index.php?showtopic=36003)
Thanks for the hint! I haven't seen this post. In my battery usage recordings from ADB android.hardware.nfc@1.1-service always stayed way below 1s of CPU time. But I've disabled NFC and will see if it helps.
ON NFC
---
I hadn't seen that post either.
I think it's worth noting that I keep NFC on all the time and I have not noticed a battery problem yet. (took my Cosmo off charger this morning 7h ago, battery now at 78%)
THE SOMETHING
---
There is the odd time where *something* in my phone causes the CPU to run at full berries and battery drains at 20%/hr instead of 4%/hr. GSam attributes this to "phone services" but I'm sure it is something else that is obscured, perhaps by continually calling for a function that "phone services" provides.
Whatever *something* is that does this, it stops as soon as I open the phone and log in with fingerprint ID. However, if I don't notice it the *something* will continue to drive the CPU at full berries. Longest I've seen is probably 1hr.
I have GSam set to alert me when the temp goes above 36 degrees, which is how I usually discover this problem is in the midst of occurring.
-
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.
-
Go figure...
[ You are not allowed to view attachments ]
-
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.
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!
-
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 (https://developer.android.com/reference/android/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.
-
Incidentally, how does one get the battery usage graph? It doesn't appear for me in the battery settings aas it has in previous Android devices I've used.
-
Incidentally, how does one get the battery usage graph? It doesn't appear for me in the battery settings aas it has in previous Android devices I've used.
When you are in battery settings, hit the three dots menu in the upper right, and then "Battery usage".
-
Incidentally, how does one get the battery usage graph? It doesn't appear for me in the battery settings aas it has in previous Android devices I've used.
When you are in battery settings, hit the three dots menu in the upper right, and then "Battery usage".
Ah, thanks.
-
Unfortunately the right USB port doesn't seem to charge for me.
Same for me, I have only used the left USB port for charging. the device does not seem to accept charge on the right side using USB from my computer or the charging brick. First full charge my cosmo got fairly warm during the charging process. Since then i have not noticed any elevated temperature during charging.
-
When I first got my Cosmo, the right port wouldn't charge it. Since upgrading both the Android and CoDi firmware, it now does.
-
I too thought only the left port works for charging because it takes about 4 seconds after plugging in until the icon changes and it becomes visible that it's charging.
-
Go figure...
[ You are not allowed to view attachments ]
After testing different SD cards for a while I can confirm that it was just a bad SD card that caused the heat and battery issue for me. I don't know why the Cosmo doesn't like that particular card. It's working and I had no issues with it in the Gemini. It's also not the card itself that's getting hot and it's not doing it for a while after the first boot after a reset.
-
I removed mine, and it seem to have had some impact, but not a lot.
I'm more worried about the seemingly endless chatting requests for DNS entries for Google's ad and analytics servers, both of which I have blocked at the DNS level via a VPN and Pi-hole. I'm getting worrying entries every minute or so, which can't be doing the battery any good whatsoever.
-
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!
-
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").
-
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").
I can see this too. I tried killing that process but it's just respawned right away. I reported this via Planet support form (although it's probably a duplicate).
-
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").
I checked once again, I have the same problem. It drains battery a bit lower but still drains. Cosmo never goes to sleep
-
From the name of the process - AmoledisonThread - I'm guessing what others have already assumed. Form some reason the communication with the CoDi needs the device to stay awake. So I'm guessing that PC have set this process to keep the device awake and respawn if stopped. Even if the CoDi is switched off, the process stays running. Maybe in a future firmware update, PC will tweak it so that - if you turn off the CoDi - the process is killed. That would at least give more battery life to those who don't need CoDi on.
-
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").
You might be into something, yesterday my flash of external display failed and it was "dead". The battery took forever, a few percent in whole day but with airplane and do not disturb mode. Then I have succeeded flashing it, and it is vanishing rapidly again.
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 (https://forum.xda-developers.com/xposed/modules/mod-nlpunbounce-reduce-nlp-wakelocks-t2853874)
To prove the concept then mail it to developers.
-
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 (https://forum.xda-developers.com/xposed/modules/mod-nlpunbounce-reduce-nlp-wakelocks-t2853874)
Github shows that there has been no updates to that code for 4-6 years. Is there a more maintained solution?
-
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 (https://forum.xda-developers.com/xposed/modules/mod-nlpunbounce-reduce-nlp-wakelocks-t2853874)
Github shows that there has been no updates to that code for 4-6 years. Is there a more maintained solution?
Yeah I have noticed, it fits for me on lineage, but try it might still work.
-
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 (https://forum.xda-developers.com/xposed/modules/mod-nlpunbounce-reduce-nlp-wakelocks-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.
-
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.
Someone noticed that after CoDi had become a (temporary?) brick after a failed FW update, the wakelock was gone.
Has anyone checked if the shutdown of the CoDi helps here?
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
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. 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?).
-
What about just disabling the Amoledison app. Should solve the problem and it is not useful anyways.
-
What about just disabling the Amoledison app. Should solve the problem and it is not useful anyways.
I may be wrong, but I believe that - since it is a system app - you can only disable it with root. Also I'm guessing that disabling it will stop the CoDi from working (this may or may not be an issue for you).
Also - I'm guessing again - but due to the way the CoDi operates it may be that this app needs to keep the device awake. So the best we might be able to hope for is that PC make a change in a future update that allows this app to be disabled by the system if you turn off the CoDi.
-
I deleted that app ages ago, no change to anything!
-
Hi Mitchelln
Is anyone else experiencing really poor battery life?
I can watch the battery percentage literally dropping as I'm using it.
For me, battery llife is still an issue.
I switch "energy saving" on a soon as possible, BT, Location normally off. Frequent closing of unneeded apps (is there a way to simplify this?).
I need the CODI, but while carrying the phone in my trouser-pocket, random contacts with the touchscreen lead to things like BT
-switch on or at least random unlock-trials, waking the screen up.
Still, it remains unreliable, whether I get through a normal day or not.
So, might this app help: https://f-droid.org/de/packages/com.suyashsrijan.forcedoze/ (https://f-droid.org/de/packages/com.suyashsrijan.forcedoze/) ?
Thanks for your advice!
-
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/ (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.
-
Not sure this helps in any way, but I don't want to keep to myself what I noticed the other day. My Codi is broken. (It just cracked while it was inside my pocket, don't know how/why.) While it's turned on there are only very colorful lines and a white spot along the crack. So I keep it permanently turned off. But when I'm in an absolutely dark room (German window shutters down at night kind of dark) I can still see those lines and the white spot. It looks exactly as if the background light was on, but way darker.
So apparently the display isn't even turned off. The backlight gets turned down and all pixels are black, but it's still on.
-
...My Codi is broken. (It just cracked while it was inside my pocket, don't know how/why.)...
Did you report cracked CoDi to Planet? And did you get some answer?
-
Did you report cracked CoDi to Planet?
I did not. Android is so buggy on the Cosmo that I gave up on bringing it in a state that makes it usable as a daily driver. If I'll only use it as an SSH client or portable keyboard I don't need an external display. I don't feel like arguing about the build quality, so I didn't report it. If you're interested, I'm relatively sure now how it must have happened. It was in my front trouser pocket, CoDi facing outside and I squeezed myself through a narrow part of a hallway. It was narrow because somebody was searching for something in a cabinet. I didn't want to interrupt them so I held the cabinet door open while going by sideways. The edge of the door must have pushed on the display. I didn't feel anything at the time and it wasn't a lot of pressure (the door would have been pushed close) so I didn't think that could have been it at first. But that's the only thing I can think of that happened around the time it must have happened where there was any pressure on the display. Sorry for off-topic. Just wanted to anwser the question.
-
I did not. Android is so buggy on the Cosmo that I gave up on bringing it in a state that makes it usable as a daily driver.
Can you elaborate on this? I haven't seen any problems with my Android (running V19, I've got no experience on older versions). "Everything" seems to work (except apparently the builtin mic's voice quality is not so good), nothing wrong on Android level as such. What problems have you ran into with Android?
Also, battery life hopefully improves with the next FW update - I guess the wakelock held by the Codi will be gone.
-
Yeah, the recently announced update sounds good. It has my hopes especially in regards to battery life.
Some of the problems I have on a regular basis: The status LEDs activate randomly. Maybe it means something, idk. Often they don't turn off when closing the lid, which is especially annoying when I was playing media before closing. It never stops blinking. After opening the lid the display turns on and sometimes just when I want to unlock it it turns off again. All I can do is close and open again, hoping it works this time. Two times I had to reboot in this state. About once a day it reboots on its own. Usually while I'm not using it. Sometimes while typing. It seems to be random. Since my SIM card is locked I'm offline until I notice it. Sometimes it doesn't turn back on on its own, sometimes it does. Sometimes the display stays black after the reboot. Then all I can do is enter recovery mode and reboot. Keyboard backlight doesn't turn off when it's not used. Sometimes the setting changes to off when the device is closed for a while. The CoDi update app notifies about its background activity all the time. I have to delete the notification almost every time I open it. Sometimes it does actually find a new CoDi version. Even when there is none. Camera quality is very bad. I stopped using it. Maybe in the summer it will be of more use when there is more sunlight. All Cosmo settings are reset to default on every reboot. Some apps are only usable in portrait mode. Autorotate doesn't work though. Sometimes it rotates for no apparent reason. Then I have to force rotate which rotates it back to landscape instead of portrait as usual. This sometimes crashes the app I was currently using, sometimes not. Bluetooth turns off when I'm not using it for a few days, WiFi can't be turned off at all. Do not disturb doesn't turn off after the set time. Sometimes while do not disturb is on incoming calls ring for about a third second then become silent. Battery usage data is not available. I lost all files on my SD card once and have no idea why. Scrolling background pictures are incredibly complicated to set up. I once brought it into a state where it rotated the screen at a rate of more than 1 Hz because I chose a file with the wrong dimensions apparently. I managed to change the background back after two days. Sometimes while charging the device unlocks without being touched. And so on. Probably all of this can be fixed in software. I'm looking forward to it. But right now I'm saving up for a different device.
-
Sorry for off-topic. Just wanted to anwser the question.
Off-topic or not, it's still good to know that the CoDi might be quite fragile, so thank you for sharing it, though I am sorry you it found out the hard way. While at it, the CoDi is an OLED display, in which each (sub)pixel makes it's own light, so it has no "backlight" as such. A "black" pixel is just off, and should not emit any light of it's own, which is why OLED screens are sometimes said to have an "infinite" constrast ratio. When the CoDi screen is off, it's interface electronics may still have power though, and as yours is damaged, there might be a tad of leakage in some unintended way.
Some of the problems I have on a regular basis:
Hm, interesting. I turn WiFi off and on every day, without an issue. That has worked just fine for me on the V15, V16 and V19 firmwares. Mostly for correctness, a "bug" is when software doesn't behave as the developer intended. The "not working" auto-rotate or that the keyboard backlight doesn't turn off when not used, are likely deliberate design choices (that I may not agree with), and it's hardly a fault of the Como that some third party apps tries to brute force themselves into portrait mode and/or won't play nice in landscape. I'd guess the wake locks preventing the Cosmo to sleep properly is rather one of several deliberately cut corners, to not delay the release further. Still, there are indeed plenty of actual bugs too, so I'm also looking forward to the next firmware, especially as the Cosmo is my daily driver.
-
Well some have a different definition of the term bug. But I think you're right. I may have included too much in the post because I'm overall annoyed by this device and it's behaviour and it's inability to shut evenly and it's loose rubber thingies and it's inconsistent key travel and now it's broken cover display. I didn't know it's an OLED. Then my theory doesn't make too much sense and you're probably right it's caused by the damage.
-
Yeah, the recently announced update sounds good. It has my hopes especially in regards to battery life.
Some of the problems I have on a regular basis: The status LEDs activate randomly. Maybe it means something, idk. Often they don't turn off when closing the lid, which is especially annoying when I was playing media before closing. It never stops blinking. After opening the lid the display turns on and sometimes just when I want to unlock it it turns off again. All I can do is close and open again, hoping it works this time. Two times I had to reboot in this state. About once a day it reboots on its own. Usually while I'm not using it. Sometimes while typing. It seems to be random. Since my SIM card is locked I'm offline until I notice it. Sometimes it doesn't turn back on on its own, sometimes it does. Sometimes the display stays black after the reboot. Then all I can do is enter recovery mode and reboot. Keyboard backlight doesn't turn off when it's not used. Sometimes the setting changes to off when the device is closed for a while. The CoDi update app notifies about its background activity all the time. I have to delete the notification almost every time I open it. Sometimes it does actually find a new CoDi version. Even when there is none. Camera quality is very bad. I stopped using it. Maybe in the summer it will be of more use when there is more sunlight. All Cosmo settings are reset to default on every reboot. Some apps are only usable in portrait mode. Autorotate doesn't work though. Sometimes it rotates for no apparent reason. Then I have to force rotate which rotates it back to landscape instead of portrait as usual. This sometimes crashes the app I was currently using, sometimes not. Bluetooth turns off when I'm not using it for a few days, WiFi can't be turned off at all. Do not disturb doesn't turn off after the set time. Sometimes while do not disturb is on incoming calls ring for about a third second then become silent. Battery usage data is not available. I lost all files on my SD card once and have no idea why. Scrolling background pictures are incredibly complicated to set up. I once brought it into a state where it rotated the screen at a rate of more than 1 Hz because I chose a file with the wrong dimensions apparently. I managed to change the background back after two days. Sometimes while charging the device unlocks without being touched. And so on. Probably all of this can be fixed in software. I'm looking forward to it. But right now I'm saving up for a different device.
Dude - you have a faulty unit. I have none of those bugs except for the auto rotate (which you can fix with Tasker) and the battery usage not being available (which you can work around with an app). All those other bugs do not happen on my Cosmo. I really think you should return it to PC for a warranty exchange. If I had all those issues I'd be really frustrated too!
-
you have a faulty unit.
One would think that reading the list. It's a device that is officially released to the market, after all. But I'm not so sure. For almost all of these things you can find reports, complaints or questions by others too on this forum.
I really think you should return it to PC for a warranty exchange.
I did ask Planet about the sudden reboots though. They didn't see a problem with this. They also tried to argue away my SD card issue when the Cosmo got so hot it would hurt my fingers when I touched the hinge after opening. Quote: "The heating issue wouldn't be a fault until your device tells you on screen that it's too hot to operate." Ignoring the fact that I hardly get 6 hours of standby time out of the battery this way. They let me know though that they will charge me for repair if I do send it in and they don't see an issue covered by the warranty. Since it has a physical damage now they can claim any fault came from misusing it. At least German laws still allow for that. I don't know about the UK. Also since I have rooted it before it was officially available they'll probably charge me extra for fixing that. They didn't say how much for the software reinstallation, so a bit risky. Even if they don't repair it and I don't even want it back they charge $25 for diagnostics. So I rather wait for my new phone, install Debian on the Cosmo and see how that goes. It is still a working device after all.
Edit: I'm not criticising their rates or the fact that they charge for repair not covered by warranty. I think $25 is cheaper than any fee of that sort that I've seen before. I just want to make sure it's really necessary to send it in before I do so.
-
Ah man - that sucks. I really don't understand how many people can have similar issues but others don't. Maybe a bad batch or something? I'm so glad mine doesn't have any of these issues that stop me from using it as a daily driver... But I'm frustrated for you. It's an expensive door stop! The sad thing is - if you have one that works it really is a most amazing machine. I hope you find joy with Linux - or if not, maybe pester PC until they agree to fix it or swap it out.
Good luck!
-
The battery life on mine has been reasonable, but today it was running very hot and dropped to 2% in under 6 hours from full (and it was being topped up for half an hour of that by by bike's dynamo, though it was also playing a podcast over bluetooth). I noticed a notification from Ledison, but tapping it didn't do anything. When I tried to open Ledison I got an "application is not responding: wait or close?" message. I rather suspect these might not be unconnected.
-
Some of the problems I have on a regular basis: The status LEDs activate randomly. Maybe it means something, idk. Often they don't turn off when closing the lid, which is especially annoying when I was playing media before closing. It never stops blinking. After opening the lid the display turns on and sometimes just when I want to unlock it it turns off again. All I can do is close and open again, hoping it works this time. Two times I had to reboot in this state. About once a day it reboots on its own. Usually while I'm not using it. Sometimes while typing. It seems to be random. Since my SIM card is locked I'm offline until I notice it. Sometimes it doesn't turn back on on its own, sometimes it does. Sometimes the display stays black after the reboot. Then all I can do is enter recovery mode and reboot. Keyboard backlight doesn't turn off when it's not used. Sometimes the setting changes to off when the device is closed for a while. The CoDi update app notifies about its background activity all the time. I have to delete the notification almost every time I open it. Sometimes it does actually find a new CoDi version. Even when there is none. Camera quality is very bad. I stopped using it. Maybe in the summer it will be of more use when there is more sunlight. All Cosmo settings are reset to default on every reboot. Some apps are only usable in portrait mode. Autorotate doesn't work though. Sometimes it rotates for no apparent reason. Then I have to force rotate which rotates it back to landscape instead of portrait as usual. This sometimes crashes the app I was currently using, sometimes not. Bluetooth turns off when I'm not using it for a few days, WiFi can't be turned off at all. Do not disturb doesn't turn off after the set time. Sometimes while do not disturb is on incoming calls ring for about a third second then become silent. Battery usage data is not available. I lost all files on my SD card once and have no idea why. Scrolling background pictures are incredibly complicated to set up. I once brought it into a state where it rotated the screen at a rate of more than 1 Hz because I chose a file with the wrong dimensions apparently. I managed to change the background back after two days. Sometimes while charging the device unlocks without being touched. And so on. Probably all of this can be fixed in software. I'm looking forward to it. But right now I'm saving up for a different device.
[Status LEDs activate randomly] - I have this problem too
[Reboots on its own] - I have this problem too, but more like once a week.
[keyboard backlight doesn't turn off] - Does this mean [a] keyboard backlight stays on when lid is closed, or keyboard backlight stays on when not touching any keys but does turn off when lid closed? Mine behaves like . I kind of like this, I often use it to read in the dark and I like seeing the keyboard even if I'm not typing. But it would be nice to have the option to poke a key like [Ctrl] to wake the keyboard backlight up.
[CoDi update notification] - I haven't had this problem. Although I do find my CoDi wakes up even when persistent notification changes state, like if battery level goes down a percent or my step count goes up. CoDi wakes up *a lot*.
[Camera quality is bad] - I have this problem too. Hello 1999, would you like your high JPG compression potato-quality camera back? I find myself apologizing to people for my camera's picture quality a lot.
[Settings reset to default] - I haven't had this problem.
[Rotate sucks] - I sort of have this problem. A bunch of apps don't work well in landscape, so I force rotate them to portrait. Most apps seem to remember their rotation state and so when I run them again, I don't need to re-force-rotate them. However, sometimes it doesn't work right and it is super-annoying because the app usually loses state when it rotates. Like, if I'm logged in (e.g. to banking) I get logged out and have to re-auth. Or if I'm halfway through reading a long page, it forgets how far I've scrolled and goes back to the top. Or stuff that I was typing in a textbox disappears.
[Bluetooth] - Haven't had any problems with it turning off and on. I do have a smart-watch constantly paired. I have noticed that when I pair to other devices (like headsets) then all devices (watch and other device(s)) disconnect for brief periods but then reconnect again. Happens randomly.
[WiFi] - My WiFi has behaved perfectly, but I always leave it on even when out and about on mobile data. I only turn it off rarely (like if I'm in the car loading directions and I'm close enough to the house to get WiFi signal but the signal is very poor).
[Do not disturb] - This turns on and off for me at the proper times and seems to work consistently. I haven't received calls during Do Not Disturb mode so I don't know about the thing where it rings for a brief moment.
[Battery usage data] - I have this problem too. I use the GSam app.
[SD Card files gone] - I haven't had this happen yet. My SD card is set up as as shared device, not an Android exclusive device, maybe this only happens in the latter case?
[Scrolling pictures] - I haven't changed my background picture yet. Maybe now, after your horror story, I won't.
[Device unlocks] - I have the reverse problem... my Cosmo occasionally locks itself spontaneously. Maybe once per day. Doesn't seem to matter if I was typing or just reading without touching any screen or buttons or keys.
I totally understand your frustration. Even with the fewer issues I have, I'm considering whether I really want this as my daily driver. If I were in your shoes I'd probably be looking for a better daily driver. The camera quality really bugs me. I'm also disappointed that the HDMI output only mirrors the display, seemingly in hardware with no future hope for change.
I've also realized that there are good Bluetooth keyboards out there and thanks to this forum, there is a way to have Linux running well under Android using Devuan. I haven't tried this yet but really looking forward to it. The two big reasons I backed the Cosmo were for the keyboard and for linux. I realize now that I could probably answer those with BT-kbd and with Devuan-method using any modern Android phone.
-
Re: sudden reboots: I had that issue on my previous phones as well every once in a while, so that's not something Planet can fix.
-
[Reboots on its own] - I have this problem too, but more like once a week.
To be honest it's not really daily for me either. I didn't take notes. But it's definitely more than once a week.
[keyboard backlight doesn't turn off] - Does this mean [a] keyboard backlight stays on when lid is closed, or keyboard backlight stays on when not touching any keys but does turn off when lid closed? Mine behaves like . I kind of like this, I often use it to read in the dark and I like seeing the keyboard even if I'm not typing. But it would be nice to have the option to poke a key like [Ctrl] to wake the keyboard backlight up.
I don't think it stays on when it's closed. It's good that it stays on while the screen is on and maybe a bit longer. But it usually never turns off when it's sitting on the desk open and left alone. But at other times the setting changes to off while it's in my pocket so I also can't trust it to be always on. It feels like it's always off when I pull it out in the dark.
[CoDi update notification] - I haven't had this problem. Although I do find my CoDi wakes up even when persistent notification changes state, like if battery level goes down a percent or my step count goes up. CoDi wakes up *a lot*.
The other day I opened the lid and there was no notification endlessly searching for updates. I thought something was wrong. The notification is my constant companion every day. I don't even know why it exists. There's nothing to be notified of, even if it wouldn't hang.
[Settings reset to default] - I haven't had this problem.
I've read about it at least once here. So, I'm not sure if you're lucky or I'm unlucky.
[Rotate sucks] [...]
I was used to that on the Gemini. And I just realised that the strange behaviour may come from the Tasker app that I never got to auto rotate. I didn't remove the configuration that was supposed to auto rotate. I'll see if that gets better when I remove the app.
[Bluetooth] - Haven't had any problems with it turning off and on.
I think it's not bluetooth specifically. Sometims airplane mode randomly turns on while it's in my pocket. And when I still had CoDi on it would sometimes redial the last number which got some people very annoyed. So maybe that's connected to it unlocking itself randomly.
[WiFi] - My WiFi has behaved perfectly, but I always leave it on even when out and about on mobile data. I only turn it off rarely (like if I'm in the car loading directions and I'm close enough to the house to get WiFi signal but the signal is very poor).
Sometimes it turns off when I tap the icon, but never for more than a few seconds.
[Scrolling pictures] - I haven't changed my background picture yet. Maybe now, after your horror story, I won't.
To still be honest, it didn't take two days to change it back. It took a few hours. But then I wanted to know what had happened and selected a picture with the same dimension agains and it started to rotate constantly again. That's why I know that really was the cause. I tried to change it back again for a while but wasn't quick enough. Tried again the next day and managed to do it after a while. Somehow that became "two days" in my head when I wrote my previous post. (Maybe because it was the second day.)
I've also realized that there are good Bluetooth keyboards out there and thanks to this forum, there is a way to have Linux running well under Android using Devuan. I haven't tried this yet but really looking forward to it. The two big reasons I backed the Cosmo were for the keyboard and for linux. I realize now that I could probably answer those with BT-kbd and with Devuan-method using any modern Android phone.
Yeah, same here. I'm more of a thumb-typer on the phone anyway. So now that I know the F(x)tec Pro¹ exists, I think I'll try that. Hopefully I'll have a chance to try it out without buying it first. I still type best on a Nokia Communicator though. I don't know what it is, but that keyboard seems to be designed specifcally for my fingers. I wish there was a phone pretty much exactly like that but with newer hardware.
-
The battery life on mine has been reasonable, but today it was running very hot and dropped to 2% in under 6 hours from full (and it was being topped up for half an hour of that by by bike's dynamo, though it was also playing a podcast over bluetooth). I noticed a notification from Ledison, but tapping it didn't do anything. When I tried to open Ledison I got an "application is not responding: wait or close?" message. I rather suspect these might not be unconnected.
Did it get better again after that? Have you inserted a new SD card by any chance? Mine is the only case I know of where that happened. But your post reminded me of the time I put in my first SD card.
-
Re: sudden reboots: I had that issue on my previous phones as well every once in a while, so that's not something Planet can fix.
Do you mean other phones or have you had different Cosmo units?
-
Re: sudden reboots: I had that issue on my previous phones as well every once in a while, so that's not something Planet can fix.
Do you mean other phones or have you had different Cosmo units?
No, other phones, like the Blackberry KEY2 (Android 8.1), BlackBerry Passport (BB10), Motorola Razr i (Android 4), etc.
-
The battery life on mine has been reasonable, but today it was running very hot and dropped to 2% in under 6 hours from full (and it was being topped up for half an hour of that by by bike's dynamo, though it was also playing a podcast over bluetooth). I noticed a notification from Ledison, but tapping it didn't do anything. When I tried to open Ledison I got an "application is not responding: wait or close?" message. I rather suspect these might not be unconnected.
Did it get better again after that? Have you inserted a new SD card by any chance? Mine is the only case I know of where that happened. But your post reminded me of the time I put in my first SD card.
Not too bad today. The SD card hasn't been changed since December.
-
[RE: Keyboard backlight]
I don't think it stays on when it's closed. It's good that it stays on while the screen is on and maybe a bit longer. But it usually never turns off when it's sitting on the desk open and left alone. But at other times the setting changes to off while it's in my pocket so I also can't trust it to be always on. It feels like it's always off when I pull it out in the dark.
I did check to confirm the backlight turns off when the lid is closed on mine. If I turn it on, it will stay on if I leave it sitting on the desk open, even when Android locks.
I'm OK with this. I usually just use [Fn]+[Shift]+( | [N] ) to change the kbd brightness so it's not much bother to turn on or off. I also usually have it at the lowest brightness when I turn it on, so I'm pretty sure the power drain is negligible especially since this Cosmo has poor battery life to begin with. (that might get better with the new firmware which is supposed to significantly improve battery drain)
I haven't ever had the keyboard brightness do an un-commanded change.
[RE: settings go back to default]
I've read about it at least once here. So, I'm not sure if you're lucky or I'm unlucky.
I haven't had this happen where all settings go to default.
However, I *have* had it happen where I have touched the CoDi screen while my Cosmo is open, and accidentally turned things on or off that way. Like today I accidentally turned on battery saver mode when I touched CoDi while Cosmo is open.
It has been noted in the forum (and I have confirmed) that even when the Planet logo is showing, CoDi will accept input. You can swipe the controls down and poke icons.
I always lock my device with fingerprint lock before putting it in a pocket so accidental CoDi input won't do anything, but if yours is unlocked or swipe-locked that might explain some of your un-commanded settings changes. WiFi, Bluetooth, Airplane Mode, Battery Saver, etc. can all be accidentally switched from the CoDi menus.
-
However, I *have* had it happen where I have touched the CoDi screen while my Cosmo is open, and accidentally turned things on or off that way. Like today I accidentally turned on battery saver mode when I touched CoDi while Cosmo is open.
It has been noted in the forum (and I have confirmed) that even when the Planet logo is showing, CoDi will accept input. You can swipe the controls down and poke icons.
I always lock my device with fingerprint lock before putting it in a pocket so accidental CoDi input won't do anything, but if yours is unlocked or swipe-locked that might explain some of your un-commanded settings changes. WiFi, Bluetooth, Airplane Mode, Battery Saver, etc. can all be accidentally switched from the CoDi menus.
Mine randomly changes some stuff.
Like right now I looked at it and CODI had turned location on. It has been sitting on a desk all day and I only turn location on when I am using maps (which I wasn't). So yeah it definitely did that on its own.
I also noticed that if you turn the ringer to vibrate only on the main screen, when you close it the Do Not Disturb icon will be activated.
Additionally if I lose signal in the parking garage it turns on location for some reason.
Minor bugs though.
-
I haven't had this happen where all settings go to default.
However, I *have* had it happen where I have touched the CoDi screen while my Cosmo is open, and accidentally turned things on or off that way. Like today I accidentally turned on battery saver mode when I touched CoDi while Cosmo is open.
It has been noted in the forum (and I have confirmed) that even when the Planet logo is showing, CoDi will accept input. You can swipe the controls down and poke icons.
I always lock my device with fingerprint lock before putting it in a pocket so accidental CoDi input won't do anything, but if yours is unlocked or swipe-locked that might explain some of your un-commanded settings changes. WiFi, Bluetooth, Airplane Mode, Battery Saver, etc. can all be accidentally switched from the CoDi menus.
I had that happen to me too. My CoDi recorded a 2 minute video by itselt while I was doing something else on the inner scree.
-
V20 Deep sleep now works
-
V20 Deep sleep now works
Nice. I'm curious how long the battery life will be more.
-
V20 Deep sleep now works
Nice. I'm curious how long the battery life will be more.
Early indication looks like double which is good news
-
A lot better here as well. Normally, my battery level around 18:00/6 PM would be down to 30% at best, but usually between 10-20%. Today at 18:00 though, it was still at 43%.
-
Nice. Any luck with auto rotate? It isn't working for me.
Again not a big deal but it would help out for 1 use case of mine
-
Nice. Any luck with auto rotate? It isn't working for me.
Again not a big deal but it would help out for 1 use case of mine
Auto rotate is working much better than before for me. Sometimes I had to use the shortcut a few times and open recents for it to rotate back, but now it rotates back after pressing the shortcut once, like it's supposed to.
-
New FW battery is really good ! Old FW in the mornin without chargin the phone would be dead in the morning. Now itwas over 40% !
i dont notice any odd behavour with the new FW like the rest.
Only hoping that the modem will work under linux, tried a lot but no luck.
device gets better with every update
-
New FW battery is really good ! Old FW in the mornin without chargin the phone would be dead in the morning. Now itwas over 40% !
i dont notice any odd behavour with the new FW like the rest.
Only hoping that the modem will work under linux, tried a lot but no luck.
device gets better with every update
Had a couple issues with the new firmware, namely never had problems with Codi crashing before but do now after using it open....the fix just pushed requires a FULL WIPE!!!