BY JOVE! I THINK THAT WORKED! As per your advice, I turned on battery saver, then turned off the phone, and plugged it into the charger... then I forgot about it till about a half hour ago. I then unplugged it and turned it on, and the battery indicator came up with that little plus sign on it. A half hour ago it was at 100%, and right now it's at... 100%
Thank you for that tip. Now I just have to remember to turn off my phone before charging it, and hoping nobody calls me!
Oh, and Velvet, if push comes to shove, you could see if Alcatel would be willing to accept the phones one phone at a time, and you can send the next one when you recieve the previous one...
Bierbaum, I’m glad to hear that it worked for you too!
But it is still a workaround. We demand cricket and alcatel to fix this battery drainage problem as soon as possible, and push the new update to all existing pulsemixes.
For some reason, just turning battery saver on doesn't stop the power drain. For what it's worth, the above mentioned silly method works at taming this problem:
It actually works for taming the power drain issue, until you turn off battery saver mode, or recharge your phone while in turned on/standby mode (which itself turns off battery saver.)
There are significant drawbacks to this method:
I get around point three by charging the phone while it's on (from the wall socket charger. The computer can't keep up with the drainage), and just go through the whole routine above in rapid sequence, only waiting long enough for that Alcatel screen to go blank before unplugging the charger. That said, I feel like I've got basically a highly over-engineered flip-phone instead of an actual smartphone.
Thanks. This worked for me also. It looks like you have to turn on the power with the battery saver already on for the battery saver to prevent the rogue background process causing the problem to start.
If you turn the battery saver after you turn on the power, the rogue process has already started and the battery saver does not stop it so that it does not help.
You can charge the phone with the phone on but charging automatically turns off the battery saver so you have to unplug the phone from the charger, turn on the battery saver, turn the phone power off and then turn back the phone on.
I contacted Cricket on this. They said it was Alcatel's issue and gave me Alcatel's phone number. I told them that even if it was Alcatel's issue it should be Cricket's responsibility to make Alcatel fix it.
For anyone still interested in this. I have since bitten the bullet and bought another phone (Nokia 6.1), and put the SIM card in that phone. An interesting effect is, it solved the power drain issue on my pulsemix, not having a SIM. I can now run the Pulsemix as a wireless smart-not-phone device that doesn't get warm, and is STILL AT 100% an hour and a half after I charged it!
The only two things I did were a.) removed the SIM card, and b.) in the MyCricket app (which I installed on the new phone) I turned off the Cricket Wireless Manager setting there.
If anyone is up for some experiments, you might try:
Since I've moved on to another phone, I'm too lazy to attempt moving on to part two of experiment 2, myself, so I'll leave it to those who may still be interested in the results of this.
Otherwise, well, the Pulsemix will make a nice internet-enabled mp3 player droid-pod kind of device.
This happened to my Alcatel device as well, about a month ago Alcalel sent me a refurbished Pulsemix to solve the high cpu usage issue under warranty. Everything worked as it should for the last few weeks until Cricket forced the 4F7UCY7 build update on the already replaced phone. Once again the replaced phone's cpu load average spiked up from 6-10 all the way to 20's and the battery once again is used up in hours. The battery saver trick is helping alot as it has dropped the CPU load average to 10-12. Its a good work around but is there any hope Cricket has even acknowledged the issue or is Cricket trying to sabotage these phones?