A fresh flash of Tesla 1.5, booting in and then changing to "Airplane Mode On" then to "Airplane Mode Off" results in a reboot.
This is after a CMR 3.0.2.5 "wipe data/factory reset" has been performed. I was having the issue with all my apps restored from TI and decided to back up.
Next step is to go back to my pre-TC and try Sense again. If it still behaves that way there, there are more problems.
I came across this scenario when trying to resolve a 3G connectivity issue once WiFi is used. I can never use 3G unless I force a restart.
I have made a backup of the "wiped system" if that image will help with tracking the issue down.
Was very repeatable until...
I removed the battery. Stable without enabling WiFi
Enable Wifi -> Turn On Airplane mode -> Turn Off Airplane mode
Must have been something hanging on from all the flash/restores?
I have had this issue with TeslaCoil 1.5 and also switching back to the Sense ROM running the latest radios (one after Stock).
I then ran "adb logcat" and the phone powered down at the last line (there were many more lines going on, but nothing seemed to stick out):
D/ResourceType( 1757): calling getConfigurations
D/ResourceType( 1757): called getConfigurations size=230
I/CheckinTask( 1757): Checkin success: https://android.clients.google.com/checkin (1 requests sent)
I/CheckinService( 1757): From server: Intent { act=android.server.checkin.FOTA_CANCEL }
W/ActivityManager( 1560): Permission Denial: broadcasting Intent { act=android.server.checkin.FOTA_C
ANCEL } from com.google.android.gsf (pid=1757, uid=10012) requires android.permission.HTC_FOTA_UPDAT
E due to registered receiver BroadcastFilter{47b299c0 ReceiverList{47b29948 1560 system/1000 local:4
7ad5cf8}}
Hello !
I updated my X10 to 2.3.3 and I have a big problem with this rom.
When the battery level reduced to 40-50% my phone turn off. If I turn on it will be do it again.
I removed the SIM and the memory card, but it is not helped.
On 2.1/2.2 works perfect.
In xRecovery I wiped the cache, data, battery stats and I installed lots of custom ROM, but none of them helped.
Please help !
(sorry for my english)
Hi I think you should calibrate your battery with this app https://market.android.com/details?id=com.nema.batterycalibration&feature=search_result you must do at least twice, inform us
let the batery to fully discharge and then recharge 100% and calibrate
Thanx, I will try this
Sent from my X10 TripNMiUI-Iris using XDA App
unfortunately does not work
pppn said:
unfortunately does not work
Click to expand...
Click to collapse
This can be a side-effect from wiping battery stats.
Did it start happening after you wiped battery stats or before?
Make a few charge circles (charge it to full once it turns off)
and see if it will keep happening. If yes, consider reflashing or repairing with SEUS.
repair it with SEUS,then see what happens.
It start before I wiped the battery stats.
I repaired with SEUS and Flashtool many times, but not helped.
"Make a few charge circles (charge it to full once it turns off)"
I will try it
Thanx everybody
I did it 5-6 times, but always turn off on 80% ...
Sent from my X10i using XDA App
I've noticed this too.
I'll take my phone out of my pocket and it will be turned off. Then I then it back on and I'll have 30 - 50% battery left... strange.
Sent from my X10i using XDA Premium App
I've been having this same issue in various forms since I switched to Wolfbreak v007 a month and a half or so ago, and it has continued through over a dozen ROM and BB changes, and through 5 or 6 full wipes and completely fresh ROM installs (though I'll admit I didn't try using SEUS to reset things that way). It does seem to have gotten worse with the official 2.3.3 update however, as it happens with me around 80% battery as well (it used to be at less than 60%, usually closer to 45% or 50%).
I should also note that the phone isn't simply dieing, but actually shutting down properly when this happens. There's no advanced warning like there is when you hit 15% battery, but the phone will chirp and vibrate, and then will show the "Shutting down" dialog and power itself down just as if I had told it to do so, though when it does shut off the LED will blink red 3 times rapidly.
I have tried wiping the battery stats directly through xRecovery, as well as through the BatteryCalibration app available on the market. Doesn't seem to matter (for reference, I've attached my current batterystats.bin below).
The issue does seem to be at the OS level though, because as others stated the phone will shut itself off again if rebooted, but if I boot into xRecovery it will happily function there for a long time on battery power (I've never left it there long enough to have it shut itself off, but I have accidentally left it there at that point for well over an hour).
On what I think is a related note, my battery level seems to drain at odd rates. It'll sit at a percentage for a while, and then I check it again moments later and it's dropped by like 2-3%, where it'll again sit for a while before dropping rapidly. f I'm actively using the phone I can watch the battery percentage drop quite readily, yet all my usage statistics seem normal (deep sleep occurs, no extended wakelocks, CPU usage is normal according to SystemPanel).
I may try to re-install everything starting with a SEUS install, but any other ideas would be greatly appreciated.
I reflashed my phone with SEUS (many times) and is isn'thelped :/
And if we replace our battery stats to a well-functioning x10's battery stats ?
Just to note, I just upgraded to Wolf's 2.3.3 006 ROM. I wiped battery stats (as well as performed a phone wipe, cache wipe, and Dalvik wipe) in xRecovery before the install. Installed and then rebooted fresh without re-installing anything (ie: a clean ROM).
Battery was reporting around 95% when I started. I configured the base system prefs, lauched a few default apps (Talk, Gmail) and configured those too. Then my phone shut itself down just a few minutes ago while I was using it. I couldn't tell you the exact battery percentage as there's no numerical display in the stock theme, but it looked to be around 80%.
So it doesn't seem to have anything to do with any of the third-party apps I'm using.
And PPPN, I'd like to see what a well functioning batterystats for an X10 is. I've taken a look at my battery stats, and I can't figure out how it actually stores any useful data. I don't see any listings for direct battery charge, which is how I'd assume it would track.
Very interesting issue, I've been running various tests to rule out things like heat running stability test and the like. So far I suspect it's either a issue with some of our batteries, something related to power, or a little of both, maybe even SIM/SD access, suffice it to say I've been prodding at the possible hardware factors, as personal as they may be to my particular situation. I have a New battery on the way so if that changes anything at all I'll let you guys know.
Is log recording working for you guys?
I've tried three different logging programs to try to record a log of when the shutdown occurs to help diagnose the problem, and with all three logging apps (aLogcat, LogViewer Lite, and Log Collector) I get the same output and nothing more:
Code:
08-04 15:07:04.111 I/checkabortedflash( 1061): [125] Latest flash seems OK.
08-04 15:07:07.631 I/DEBUG ( 1078): debuggerd: Jul 13 2011 19:25:06
08-04 15:07:07.741 I/Vold ( 1076): Vold 2.1 (the revenge) firing up
08-04 15:07:07.741 D/DHCP ( 1088): failed to set ip addr for eth0 to 0.0.0.0: No such device
08-04 15:07:07.811 V/DrmIOService( 1082): instantiate
08-04 15:07:07.811 V/DrmIOService( 1082): created
08-04 15:07:07.821 D/Vold ( 1076): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media)
08-04 15:07:07.861 E/NetlinkEvent( 1076): NetlinkEvent::FindParam(): Parameter 'NPARTS' not found
08-04 15:07:07.861 W/DirectVolume( 1076): Kernel block uevent missing 'NPARTS'
08-04 15:07:07.861 D/Vold ( 1076): Volume sdcard state changing 0 (No-Media) -> 2 (Pending)
08-04 15:07:07.861 E/NetlinkEvent( 1076): NetlinkEvent::FindParam(): Parameter 'PARTN' not found
08-04 15:07:07.861 W/DirectVolume( 1076): Kernel block uevent missing 'PARTN'
08-04 15:07:07.861 D/Vold ( 1076): Volume sdcard state changing 2 (Pending) -> 1 (Idle-Unmounted)
08-04 15:07:08.051 I/iddd ( 1101): Starting up...
08-04 15:07:08.061 I/Netd ( 1077): Netd 1.0 starting
The last line (not recorded in the log I saved) reads:
Code:
08-04 15:07:08.051 I/iddd Ready to serve the world.
This is the first time since a few ROMs ago that I've tried to run any logging software.
Actually, that log file resembles something I saw during my testing, specifically the snippet pertaining to "NPARTS" and all that.
OK, I got logs working... kind of.
In aLogcat (and only aLogcat) I set the buffer setting to "Events". This reports all the events that are going on. However since the app can only automatically save every 15 minutes (at best), I can't seem to get it to save the log file as the system shuts down. Launching the app after I boot back up doesn't seem to pull up any log data from before the shutdown from what I can tell (with my total lack of Android-coding experience). So no luck in getting a log of what's going on for me.
I can attest to the fact that on 4 separate occasions I have had my phone shut itself down at 88% battery as I was attempting to get this logging thing going.
At this rate, I may have to revert back to stock 2.1 just to have a usable X10.
Principle on UK Generic works fine, only bad on ARO.
Can somebody confirm this ?
Hi there!
You should try battery stats wiping when phone is on 100%. I googled it, and it says that you should first charge your battery to 100%, not just until green light, then drain it until phone turns itself off, then recharge to 100% again. You should give it a try. As I read, battery stats can go confused when you flash with battery level under 100% many times.
my Batttery went von 80% to 40% in like one minute. I put in on the charger and it still went down. After 5 min ist was soo low it restartet itself and when it finished starting the battery was 91% again. now it goes slowly down but it is still random because the Batterie wennt from 80% to 86% without charging. I updatet wb rom v007 today. Before i got wb v005 and hat no problems.
So i downloaded BetterBatteryStats and found that in my wakelock there is a service "AlarmManager" that won't stop and i believe is the reason behind my "phone idle" battery drain issue...is it safe to stop it? and if so, how can i stop it?
I can't seem to find it in Titanium Backup to freeze..
bump...
I have the same issue. I'm going to try this fix.
http://forum.xda-developers.com/showthread.php?t=1198333
I also see a lot of wakelocks caused by AlarmManager. When I look at my battery stats the phone is active about 50% even though the screen is only on 10% of the time. The activity doesn't seem to correlate to anything either. It isn't cyclical like an hourly update or something.
According to Google, the AlarmManager handles the following:
This class provides access to the system alarm services. These allow you to schedule your application to be run at some point in the future. When an alarm goes off, the Intent that had been registered for it is broadcast by the system, automatically starting the target application if it is not already running. Registered alarms are retained while the device is asleep (and can optionally wake the device up if they go off during that time), but will be cleared if it is turned off and rebooted.
The Alarm Manager holds a CPU wake lock as long as the alarm receiver's onReceive() method is executing. This guarantees that the phone will not sleep until you have finished handling the broadcast. Once onReceive() returns, the Alarm Manager releases this wake lock. This means that the phone will in some cases sleep as soon as your onReceive() method completes. If your alarm receiver called Context.startService(), it is possible that the phone will sleep before the requested service is launched. To prevent this, your BroadcastReceiver and Service will need to implement a separate wake lock policy to ensure that the phone continues running until the service becomes available.
Note: The Alarm Manager is intended for cases where you want to have your application code run at a specific time, even if your application is not currently running. For normal timing operations (ticks, timeouts, etc) it is easier and much more efficient to use Handler.
You do not instantiate this class directly; instead, retrieve it through Context.getSystemService(Context.ALARM_SERVICE).
Click to expand...
Click to collapse
http://developer.android.com/reference/android/app/AlarmManager.html
This leads me to believe that something is registering events that are causing the phone to frequently wake up. I may try reviewing the logs to find out what is doing this.
EDIT: After spending sometime, I couldn't find anything. I recently downloaded BetterBatteryStats version 0.7.0 which seems much improved. I no longer see AlarmManager in the list, so maybe it was a red herring and nothing was wrong? I will keep monitoring
Nope, still getting a lot of partial wakelocks for AlarmManager. About 1 hour for every 8 hours of run time.
Anyone have any idea how to track down what is registering for the wakelocks in AlarmManager?
krkeegan said:
Nope, still getting a lot of partial wakelocks for AlarmManager. About 1 hour for every 8 hours of run time.
Anyone have any idea how to track down what is registering for the wakelocks in AlarmManager?
Click to expand...
Click to collapse
I'm not sure if you're still looking for this information but running the command below should show you registered events hooked into the alarmmanager service.
adb shell dumpsys alarm
Hi all,
I think I’ve broken the bt functionality of my alcatel ot 995 by installing and applying fixes that were told to solve issues with headsets. Well, they did so: since then I haven’t been able to use it at all.
How could I restore the original settings of Bluetooth Share? I tried and cleared data in app manager but still, I can’t even pair my phone to other devices because of its slow reaction. It displays the pairing code only after the other device has given up the pairing request. I tried to look at logcat and bt seems to generate a lot of events even after turning it off. But so much that I feel like Neo in Matrix as the lines are scrolling down in cmd.
While bt is turned off, I received error messages such as:
I/ActivityManager( 186): Start proc com.broadcom.bt.app.system for restart com.
broadcom.bt.app.system: pid=29110 uid=1002 gids={3001, 3002}
V/WindowManager( 186): Layout: mDisplayFrozen=false holdScreen=null
D/AndroidRuntime(29110): Get string from web_user_agent Mozilla/5.0 (Linux; U; A
ndroid 2.3.6; en-gb; ALCATEL_one_touch_995 Build/GINGERBREAD) AppleWebKit/533.1
(KHTML, like Gecko) Version/4.0 Mobile Safari/533.1
W/ActivityManager( 186): Unable to start service Intent { cmp=com.android.music
/.MediaPlaybackService }: not found
I/InputManager-Callbacks( 186): No input device calibration properties found fo
r device AVRCP.
V/WindowManager( 186): Layout: mDisplayFrozen=false holdScreen=null
I/ActivityManager( 186): Process com.broadcom.bt.app.system (pid 29110) has die
d.
W/ActivityManager( 186): Scheduling restart of crashed service com.broadcom.bt.
app.system/.OppService in 20000ms
I/ActivityManager( 186): Start proc com.broadcom.bt.app.system for restart com.
broadcom.bt.app.system: pid=29119 uid=1002 gids={3001, 3002}
Whereas, after turning bt off, I get these lines:
V/BluetoothPbapService(27835): Accept exception: java.io.IOException: Software c
aused connection abort
V/BluetoothPbapService(27835): Accept exception: java.io.IOException: Software c
aused connection abort
This endless flow can be stopped by disabling and re-enabling CREATE_LIVE_FOLDER event of Bluetooth Share and then android won’t consume a lot of energy any more.
Could you please give me some tips what I could reset or fix in order to get the system work properly again? Unfortunately I haven’t made any backups (except for a One Touch backup but restoring that did not work)
I have resolved this by reinstalling the default music app. Sorry for starting a new thread, it could be deleted.
Hello,
I got the following phone:
Moto G Pure | 2021 | 2-Day battery | Unlocked | Made for US by Motorola | 3/32GB | 13MP Camera | Deep Indigo
https://www.amazon.com/gp/product/B09BTB5MKT/
It has an Android 11 installed. The phone is typically connected to the local WiFi network and can reach 300mbps download/20mbps upload speeds when running the speedtest app.
I noticed that sometimes (once every few days or couple of weeks) the phone stops reacting to downloading new data from the internet.
So If I try to go to chrome browser and load a page, it would load the page forever. The WiFi icon will still show as it's connected to the WiFi and connected to the network. If I try to do a speedtest, the app would be stuck and not start downloading everything.
If I try to toggle the WiFi on and off, or use the cellular it doesn't seem to resolve the issue always, typically this would require a reboot of the phone.
I also noticed that sometimes this issue is even worst, when the cellular would stop working too, so if I send text messages to the phone, and go to the messages app, the new messages wouldn't show, neither the cellular internet would work or it will be really slow.
One time, I ran into this issue with the "internet freeze" when I configured a VPN (software-defined mesh virtual private network), and I set the VPN to always be on in settings, the internet still worked, but when I tried to reboot the phone, although the VPN got automatically connected as expected after reboot, it went into the "internet freeze", and only way I was able to resolve it is when I turned the VPN off. Still, the VPN by itself shouldn't be an issue with the internet still working, as evident when I turned on the VPN when the internet was already working and no problem there, but somehow the turn VPN always might have been the trigger point to the get "internet freeze" issue. Previous times the issue happened, I didn't run any VPNs so I'm suspecting there could be multiple trigger points that could cause this issue.
When I spoke with Motorola tech support, there wasn't really much troubleshooting other than making sure the software is up to date and keeping track of when the issue happens or how often. They did show me how to generate a bug report, so when the issue happens again, I could send it to them for further investigation. I was able to get bug report when the issue happened today - Actually Android automatically identified that there was an issue and generated the report. I know it might have some private sensitive information so I might not want to share it, but are there parts in it that I could safely share? For example, in the file dumpstate_log.txt when I search for the word "wifi" I can see this message repeatedly:
######################################################################
Warning: Skipping "[email protected]::ISupplicant/default": cannot be fetched from service manager (null)
and similar messages to it such as:
Warning: Skipping "[email protected]::IAllocator/ashmem": cannot be fetched from service manager (null)
######################################################################
Here are some other suspicious lines:
######################################################################
*** command 'lshal debug -E [email protected]::ISupplicant/default' failed: exit code 128
[email protected]::IAllocator/ashmem does not exist, or no permission to connect.
*** command 'lshal debug -E [email protected]::IMtkRadioEx/mtkRsu1' failed: exit code 128
[email protected]::IMtkRadioEx/mtkSe1 does not exist, or no permission to connect.
######################################################################
In file bugreport-ellis_retail-RRHS31.Q3-46-123-5-2-2023-05-28-20-41-03 I'm seeing these suspicious lines:
######################################################################
05-28 20:19:43.501 1000 1431 1459 W ActivityManager: Slow operation: 88ms so far, now at startProcess: returned from zygote!
05-28 20:19:43.501 1000 1431 1459 W ActivityManager: Slow operation: 88ms so far, now at startProcess: done updating battery stats
05-28 20:19:43.501 1000 1431 1459 W ActivityManager: Slow operation: 88ms so far, now at startProcess: building log message
05-28 20:19:45.625 1000 1431 1431 W Looper : Slow dispatch took 104ms main h=com.android.server.job.JobSchedulerService$JobHandler c=null m=4
05-28 20:20:34.311 1000 1431 1459 W ActivityManager: Slow operation: 272ms so far, now at startProcess: starting to update pids map
05-28 20:20:34.314 1000 1431 1459 W ActivityManager: Slow operation: 275ms so far, now at startProcess: done updating pids ma
######################################################################
Is there anything in particular in the log I should look for? I see there are additional folders such as FS, lshal-debug, proto.
I'm mostly interested to know what causes the phone to go into "internet freeze" issue - How can this issue be prevented all together, is there some setting or something? Is this a common issue with this phone or with Android? Did this happen with your phone too?
Thanks.