Sr My English is very bad
I've been running Nexus v4.0.5 on my Apollo device. The issue is my kindle start to rebooting or turning off after entering sleep mode I wanted to try another rom, but I'm not sure it could help
What is the problem ?Please help.
Sigosuuu said:
Sr My English is very bad
I've been running Nexus v4.0.5 on my Apollo device. The issue is my kindle start to rebooting or turning off after entering sleep mode I wanted to try another rom, but I'm not sure it could help
What is the problem ?Please help.
Click to expand...
Click to collapse
Nexus v4.0.5 is very old and is no longer supported. Suggest installing the immediate successor (Fire Nexus) which you can do without loss of data.
Is the device running Safestrap?
Davey126 said:
Nexus v4.0.5 is very old and is no longer supported. Suggest installing the immediate successor (Fire Nexus) which you can do without loss of data.
Is the device running Safestrap?
Click to expand...
Click to collapse
I installed (Fire Nexus) but the issue not fix :crying::crying::crying::crying::crying::crying::crying:
Sigosuuu said:
I installed (Fire Nexus) but the issue not fix :crying::crying::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
Likely an app. You will need to use a tool like GSAM or BBS to identify the culprit.
My Apollo HDX behaves similarly, and has since I got it (refurbished) six months ago: very shortly after going into screen-off mode, a reboot occurs.
This happened under the stock 4.5.5.2 OS, but seemed to be mitigated if I set it to keep wifi on during sleep.
Under LineageOS 14.1, however, it reboots whether that option is enabled or disabled.
I've tried several times to see if anything interesting appears via wireless logcat, but nothing is terribly obvious. Here's the last attempt:
Code:
07-03 01:59:19.246 1157 1234 E WifiHAL : wifi_error acquire_supported_features(wifi_interface_handle, feature_set *): requestResponse Error:-95
07-03 01:59:19.247 1157 1540 E BatteryStatsService: no controller energy info supplied
07-03 01:59:19.247 1157 1540 E BatteryStatsService: no controller energy info supplied
07-03 01:59:19.248 1567 1567 E PhoneInterfaceManager: [PhoneIntfMgr] queryModemActivityInfo: Empty response
07-03 01:59:19.257 1157 1540 E BatteryStatsService: modem info is invalid: ModemActivityInfo{ mTimestamp=0 mSleepTimeMs=0 mIdleTimeMs=0 mTxTimeMs[]=[0, 0, 0, 0, 0] mRxTimeMs=0 mEnergyUsed=0}
07-03 01:59:20.383 544 884 D audio_hw_primary: out_standby: enter: stream (0xb624ab00) usecase(1: low-latency-playback)
07-03 01:59:20.489 544 884 D hardware_info: hw_info_append_hw_type : device_name = speaker
After that, the device no longer pings as it has begun restarting.
Using Wake Lock (https://play.google.com/store/apps/details?id=eu.thedarken.wl), I found certain combinations that would prevent reboots when the screen goes off:
wifi on, wakelock WIFI_MODE_FULL_HIGH_PERF => ok
wifi on, wakelock WIFI_MODE_FULL (or less) => *restart on sleep*
wifi off, wakelock PARTIAL_WAKELOCK => ok
wifi off, wakelock WIFI_MODE_FULL_HIGH_PERF (or less) => *restart on sleep*
airplane mode, no wakelock => ok
Seems almost like some sort of hardware/driver issue.
Related
I bought a new Samsung GT-S5570 (stock ROM: Android 2.2.1, baseband S5570XXKB2, kernel 2.6.32.9-perf root(at)DELL106 #1, build FROYO.XIKF1).
I set the Wi-Fi sleep policy to Never, to keep it always on, I installed a few very popular apps from the Market and used the phone normally.
After a random number of hours (10-20 or so) the phone hangs: black screen, no response to keypresses, no ringing if I call from another phone (but at the other phone I hear the normal ringback tone). The only thing I can do is press the power button for 10 seconds to restart the phone.
Sometimes if I just wait for one hour or so the phone starts working again, but the wi-fi doesn't work anymore until I reboot.
I tried it with a different access point and it was the same.
I brought the phone back to the store and they gave me another GT-S5570.. it was exactly the same.
The last time, when the phone woke up, I could read the following kernel messages repeated many times per second:
Code:
09/26/2011 01:00:23 [ALERT] Debug Assert Caught, File /SRC/S5570_MAIN_WORKING/Android/kernel/../system/wlan/atheros/AR6kSDK.3.0/host/os/linux/../../hif/sdio/linux_sdio/src/hif.c, Line: 848, Test:status == A_OK || status == A_ECANCELED
09/26/2011 01:00:23 [ERROR] mmc1: Data CRC error
09/26/2011 01:00:23 [ERROR] msmsdcc_data_err: opcode 0x00000035
09/26/2011 01:00:23 [ERROR] msmsdcc_data_err: blksz 24, blocks
09/26/2011 01:00:23 [INFORMATION] mmc1: Controller has been reset
09/26/2011 01:00:23 [WARNING] pc_clk_set_rate id : 21, rate : 144000
09/26/2011 01:00:23 [WARNING] pc_clk_set_rate id : 0, rate : 144000
09/26/2011 01:00:23 [WARNING] , rc : 0
09/26/2011 01:00:23 [ALERT] AR6000: SDIO bus operation failed! MMC stack returned : -84
Logcat only showed a one hour long black hole:
Code:
09/25/2011 22:59:33 [DEBUG] WifiService(177) [mPersistState] : On
09/25/2011 22:59:35 [DEBUG] WifiService(177) [mPersistState] : On
09/25/2011 23:00:33 [DEBUG] WifiService(177) [mPersistState] : On
09/25/2011 23:00:34 [DEBUG] WifiService(177) [mPersistState] : On
09/26/2011 01:00:26 [DEBUG] KeyguardViewMediator(177) onWakeKeyWhenKeyguardShowing(3)
09/26/2011 01:00:26 [DEBUG] KeyguardViewMediator(177) wakeWhenReadyLocked(3)
09/26/2011 01:00:26 [DEBUG] KeyguardViewMediator(177) onWakeKeyWhenKeyguardShowing(3)
09/26/2011 01:00:26 [DEBUG] KeyguardViewMediator(177) wakeWhenReadyLocked(3)
09/26/2011 01:00:26 [DEBUG] KeyguardViewMediator(177) onWakeKeyWhenKeyguardShowing(3)
09/26/2011 01:00:26 [DEBUG] KeyguardViewMediator(177) wakeWhenReadyLocked(3)
09/26/2011 01:00:26 [DEBUG] KeyguardViewMediator(177) onWakeKeyWhenKeyguardShowing(3)
09/26/2011 01:00:26 [DEBUG] KeyguardViewMediator(177) wakeWhenReadyLocked(3)
09/26/2011 01:00:26 [DEBUG] KeyguardViewMediator(177) handleWakeWhenReady(3)
09/26/2011 01:00:26 [ERROR] power(177) *** set_screen_state 1
How can this be possible? Hardware fault? Buggy driver? Are all the GT-S5570s affected?
Thank you
I brought this second defective phone to the store and they gave me another GT-S5570 (different colour this time! ).
On this third phone I did not install any of the apps I had installed on the previous ones and I didn't even put my SIM card in. I just configured a wi-fi connection and set the Wi-Fi sleep policy to Never.
Here we are again. I just found it like this: black screen, no response to keypresses, completely dead until I press the power button for 10 seconds.
Is the Samsung Galaxy Next/Mini GT-S5570 a broken phone? Am I missing something?
Hi, if you have warranty just change your phone but I believe you are having problem with your OS I mean is a soft problem
Enviado desde mi GT-S5570 usando XDA Premium App
I did it. I already changed three different GT-S5570s and they all had the same problem. They all had the stock OS.
I tried with two (very different) wi-fi access points. In the last phone I did not install any app.
are you successfully using the wi-fi connection always on for many hours?
Yes I am I'm using emanon rom and I'm not having any problem
Sent from my GT-S5570 using xda premium
jacopoL said:
I bought a new Samsung GT-S5570 (stock ROM: Android 2.2.1, baseband S5570XXKB2, kernel 2.6.32.9-perf root(at)DELL106 #1, build FROYO.XIKF1).
I set the Wi-Fi sleep policy to Never, to keep it always on, I installed a few very popular apps from the Market and used the phone normally.
Click to expand...
Click to collapse
Jacopol, you made my day. My phone used to crash the same. I stopped setting the wifi-policy to "Never" and it does not crash any more! Thanks for a great workaround.
The ar6000/ar6k does not look reliable in Gingerbread Galaxy; you can find plenty of other people on the web complaining about it. I personally have experienced another problem with it: sometimes it just refuses to load. When trying to enable wifi the on-screen button turns green for a split second and then grey again. alogcat displays: "INFO: ar6000.ko failed to load" (yes, at the "INFO" level...)
It was incredible for me to find a hardware/driver problem like this in a production device from a quite big brand. I tested three different phones and they were all affected: no always-on wi-fi connection was possible.
I ended up asking for my money back and I bought another phone.
skew4 said:
Jacopol, you made my day. My phone used to crash the same. I stopped setting the wifi-policy to "Never" and it does not crash any more! Thanks for a great workaround.
Click to expand...
Click to collapse
I unfortunately have to take some of that back. Thanks to this workaround it crashes... LESS OFTEN
It also seems to be highly environment/AP-dependent, roaming across APs making it worse.
jacopoL said:
It was incredible for me to find a hardware/driver problem like this in a production device from a quite big brand.
Click to expand...
Click to collapse
I guess many people are not affected.
Looks like gingerbread fixed this... crossing fingers.
I've had the phone for 2 months without any issues (other than the crappy GPS and compass) and about a week ago, all of a sudden it started to randomly turn itself off. At about the same time it completely destroyed the SD card, after warning me a few times that it was 'unexpectedly removed' which always fixed itself on its own within a few minutes - anyway, gutted about losing all my precious data but I suppose it's otherwise unrelated, the new card runs OK so far.
The shutdowns occur on average 3 times a day and the phone can't be turned on without removing the battery, which is the biggest annoyance. Running stock G4W 20130819-085550 (upgraded from previous version but not sure what that was) but even tried MIUI 3.11.16 by sta-s2z - same problem. Bought it from uredeal.com which appears to be down so can't even ask about warranty. Not aware of installing anything that could be the cause.
Some logs from CatLog are attached, surprised by the huge number of errors, some fatal in case of the 2nd and 3rd log but they don't seem to be the same cause (?) also suppose the 1st log might not have any fatal errors only cos I had the write period set too long, then reduced it to 5 lines. I have no idea what to do or try next. Any ideas, please?
One more log... can somebody help please?
bump... please... :crying:
If u can access play bstore, searcha and install jiayu.es application, it´s in english . it will give u access to latest stock rom without the chinese stuff.
Hope it solves your problem.
guerrix: thanks but unfortunately the issue prevails under that ROM, too
My Nokia phone also appears you this kind of situation, I am very upset, don't know how to solve.
tyrol_gangster said:
I've had the phone for 2 months without any issues (other than the crappy GPS and compass) and about a week ago, all of a sudden it started to randomly turn itself off. At about the same time it completely destroyed the SD card, after warning me a few times that it was 'unexpectedly removed' which always fixed itself on its own within a few minutes - anyway, gutted about losing all my precious data but I suppose it's otherwise unrelated, the new card runs OK so far.
The shutdowns occur on average 3 times a day and the phone can't be turned on without removing the battery, which is the biggest annoyance. Running stock G4W 20130819-085550 (upgraded from previous version but not sure what that was) but even tried MIUI 3.11.16 by sta-s2z - same problem. Bought it from uredeal.com which appears to be down so can't even ask about warranty. Not aware of installing anything that could be the cause.
Some logs from CatLog are attached, surprised by the huge number of errors, some fatal in case of the 2nd and 3rd log but they don't seem to be the same cause (?) also suppose the 1st log might not have any fatal errors only cos I had the write period set too long, then reduced it to 5 lines. I have no idea what to do or try next. Any ideas, please?
Click to expand...
Click to collapse
Experiencing exactly the same issues with a Jiayu G3S, did you manage to get to the bottom of it????
phatrat: afraid not
ok so work-around found thanks to jiayu.es forums, use app Wake Lock to setup partial wake + apply on boot + notification. eats lots of battery but no shutdowns for several days now.
I have this same problem of random shutdowns. It switches of completely random, at least that's what it looks like. I have found out at least two things:
1)Try to turn of wifi! If you turn of wifi, it has never happened to me that it shut down randomly. I do never use 3g or 2g mobile internet, so I don't know if an active 2/3g makes the phone shut down. At least I recommend you to do it.
2) Most oftenly, the phone turns off when I receive some whatsapp messages. I can see it, because of the warning light on top of the phone that is flickering. Furthermore removing your complete whatsapp and reinstall it cleanly, does not solve it. Cleaning or removing your SD neither does. I'm still on it, but do not expect major breakthroughs from my side. I'm not a phone technician.
I haven't tried a fresh install, somewhere I think it would solve the problem. But that is my phone instinct.
Do you guys have changed stuff in the internals? Like change the framework, install xposed, etc?
tyrol_gangster said:
ok so work-around found thanks to jiayu.es forums, use app Wake Lock to setup partial wake + apply on boot + notification. eats lots of battery but no shutdowns for several days now.
Click to expand...
Click to collapse
Thanks for the reply. Could you be more specific in regards to the steps necessary, is the app required called 'Wakelock Detector-Save Battery'? I had a look on the Jiayu.es forums but couldn't find anything in regard to the solution you suggested (doesn't help it being in Spanish). Any help would be greatly appreciated.
foro.jiayu.es + google translate: Install an app called Wake Lock (A light bulb with a padlock.) This application makes it unique is that the phone when "locked" not enter hibernation state and therefore the CPU is always running. Advantage : Well, so far has not given me any failure mobile and took almost 3 days with the application. Disadvantage : It is assumed that sucks a lot of battery, but I loaded it yesterday evening and now I have 78% battery. How is this application set? 1. Open the application. 2. Click "PARTIAL_WAKE_LOCK". By pressing a series of numbers appear (to 4) and put as text "Partial. Ensures That the CPU is running. The Might not be on screen.". 3. Press the button on the left to open the mobile application options and click on "Options" and have labeled "Autostart on boot" and "Notification".
deleted
tyrol_gangster said:
deleted
Click to expand...
Click to collapse
I have a G4A. Which model are you running -- basic, or advanced or other? What ROM are you running?
Have you tried any kind of debug or test to determine which component of the phone is the culprit? Try to fresh power-on the phone from power-off, enable debugging in settings, connect a USB cable to a computer (and phone) and running "adb bugreport > results.txt" command and post the results.txt file here. Also can use "CatLog" app or some other logcat app or dmesg app to record logs, and post the log file to here.
Just for kicks, you can also try 'factory mode' ? This will test hardware and output some messages. This can be done by taking out the battery, hold the VOL DOWN button, plug in a USB cable to computer, keep holding VOL DOWN button until the phone powers on and shows a chinese menu. On the first menu item, press POWER button once.
http://adbshell.com/commands/adb-bugreport/how-to-use-adb-bugreport.html
I have the same problem (i;ve tried 4 different roms)
I've tried the last official
staz and kiloes miuis
with no luck
i've seen that when i use two sim cards the problem is worse..
i'm posting the adb bugreport (because i cannot indestand it..)
miaoumiaou said:
I've tried the last official
staz and kiloes miuis
with no luck
i've seen that when i use two sim cards the problem is worse..
i'm posting the adb bugreport (because i cannot indestand it..)
Click to expand...
Click to collapse
bump!:victory:
miaoumiaou said:
bump!:victory:
Click to expand...
Click to collapse
didn't see anything bad in your 'results txt' file. try logcat or catlog app from android google play or download its apk file and record / save its log and post that here. note: some devices show nothing useful from logcat or catlog (like my Jiayu)
also try a "dmesg" log app.
UIComposeThread -- Error
petesimon said:
didn't see anything bad in your 'results txt' file. try logcat or catlog app from android google play or download its apk file and record / save its log and post that here. note: some devices show nothing useful from logcat or catlog (like my Jiayu)
also try a "dmesg" log app.
Click to expand...
Click to collapse
Code:
<4>[ 8964.893014] (0)[546:UIComposeThread]ERROR!!!Layer 3 format error!!!
<5>[ 8964.895583] (0)[16302:pal.androidterm][Power/GPU_DVFS] mt_gpufreq_keep_frequency_non_OD_get, mt_gpufreq_keep_specific_frequency = 0
<4>[ 8964.908995] (0)[546:UIComposeThread]ERROR!!!Layer 3 format error!!!
<5>[ 8964.911452] (0)[16302:pal.androidterm][Power/GPU_DVFS] mt_gpufreq_keep_frequency_non_OD_get, mt_gpufreq_keep_specific_frequency = 0
<4>[ 8964.925037] (0)[546:UIComposeThread]ERROR!!!Layer 3 format error!!!
<5>[ 8964.927552] (0)[16302:pal.androidterm][Power/GPU_DVFS] mt_gpufreq_keep_frequency_non_OD_get, mt_gpufreq_keep_specific_frequency = 0
<4>[ 8964.942011] (0)[546:UIComposeThread]ERROR!!!Layer 3 format error!!!
<5>[ 8964.945884] (1)[16302:pal.androidterm][Power/GPU_DVFS] mt_gpufreq_keep_frequency_non_OD_get, mt_gpufreq_keep_specific_frequency = 0
<4>[ 8964.958120] (0)[546:UIComposeThread]ERROR!!!Layer 3 format error!!!
<5>[ 8964.961902] (0)[16302:pal.androidterm][Power/GPU_DVFS] mt_gpufreq_keep_frequency_non_OD_get, mt_gpufreq_keep_specific_frequency = 0
<4>[ 8964.975137] (0)[546:UIComposeThread]ERROR!!!Layer 3 format error!!!
<5>[ 8964.981266] (0)[16302:pal.androidterm][Power/GPU_DVFS] mt_gpufreq_keep_frequency_non_OD_get, mt_gpufreq_keep_specific_frequency = 0
<4>[ 8964.991238] (0)[546:UIComposeThread]ERROR!!!Layer 3 format error!!!
<5>[ 8964.997252] (0)[16302:pal.androidterm][Power/GPU_DVFS] mt_gpufreq_keep_frequency_non_OD_get, mt_gpufreq_keep_specific_frequency = 0
<4>[ 8965.007323] (0)[546:UIComposeThread]ERROR!!!Layer 3 format error!!!
<5>[ 8965.013268] (0)[16302:pal.androidterm][Power/GPU_DVFS] mt_gpufreq_keep_frequency_non_OD_get, mt_gpufreq_keep_specific_frequency = 0
<4>[ 8965.023325] (0)[546:UIComposeThread]ERROR!!!Layer 3 format error!!!
<5>[ 8965.029292] (0)[16302:pal.androidterm][Power/GPU_DVFS] mt_gpufreq_keep_frequency_non_OD_get, mt_gpufreq_keep_specific_frequency = 0
<4>[ 8965.039414] (0)[546:UIComposeThread]ERROR!!!Layer 3 format error!!!
<5>[ 8965.045342] (0)[16302:pal.androidterm][Power/GPU_DVFS] mt_gpufreq_keep_frequency_non_OD_get, mt_gpufreq_keep_specific_frequency = 0
<4>[ 8965.055405] (0)[546:UIComposeThread]ERROR!!!Layer 3 format error!!!
<5>[ 8965.061320] (0)[16302:pal.androidterm][Power/GPU_DVFS] mt_gpufreq_keep_frequency_non_OD_get, mt_gpufreq_keep_specific_frequency = 0
<4>[ 8965.071463] (0)[546:UIComposeThread]ERROR!!!Layer 3 format error!!!
<5>[ 8965.086371] (0)[641:ndroid.systemui][Power/GPU_DVFS] mt_gpufreq_keep_frequency_non_OD_get, mt_gpufreq_keep_specific_frequency = 0
<4>[ 8965.087409] (0)[546:UIComposeThread]ERROR!!!Layer 3 format error!!!
<4>[ 8965.103667] (0)[546:UIComposeThread]ERROR!!!Layer 3 format error!!!
<4>[ 8965.119479] (0)[546:UIComposeThread]ERROR!!!Layer 3 format error!!!
<4>[ 8965.135596] (0)[546:UIComposeThread]ERROR!!!Layer 3 format error!!!
i got this error report when i was trying these directions "Fortunately, there is a kernel file /proc/kmsg which does exactly the same thing. One can just run the following command to continuously dump the kernel messages. "
with this command # adb shell cat /proc/kmsg
but i cannot understand these errors..
miaoumiaou said:
Code:
<4>[ 8964.893014] (0)[546:UIComposeThread]ERROR!!!Layer 3 format error!!!
<5>[ 8965.086371] (0)[641:ndroid.systemui][Power/GPU_DVFS] mt_gpufreq_keep_frequency_non_OD_get, mt_gpufreq_keep_specific_frequency
i got this error report when i was trying these directions "Fortunately, there is a kernel file /proc/kmsg which does exactly the same thing. One can just run the following command to continuously dump the kernel messages. "
with this command # adb shell cat /proc/kmsg but i cannot understand these errors..
Click to expand...
Click to collapse
disregard those messages because I also got hundred's of those when I capture kmsg output but my phone works fine. I don't know what those messages mean either. but no worries.
Code:
adb kill-server
adb devices
adb shell su -c cat /proc/kmsg > kmsg-output.txt
[ CTRL C ]
zip kmsg-output.txt.zip
did you try "logcat" app or adb logcat command? try this. the file will be large so please zip (compress) the file and attach this zip file here.
Code:
adb kill-server
adb devices
adb logcat -v long > adblogcat-output.txt
[ CTRL C ]
zip adblogcat-output.txt.zip adblogcat-output.txt
if adb logcat does not work then try this alternative command (needs root) :
Code:
adb shell su -c cat /dev/log/system > adblogcat-output.txt
[ CTRL C ]
you may see my logs for comparison. good luck.
Hello there,
My Samsusng Galaxy S2 (i9100) has recently stopped working as it is supposed to. While I tried debugging the issue in any way I could, I figured out I might get some help over here.
At any time that the device itself isn't connected to a power source (USB cable [adb] or the charger), it randomly crashes (the screen turns black and I have to turn the phone on again). I also must say that this problem doesn't happen while on the recovery screen (CWM based recovery).
At first I thought this may happen because I've installed a pretty old version of Cyanogenmod (the cm11 installer version), so I installed the recent monthly build, but the issue still persists. I've tried debugging the device wirelessly (because when it was connected to a power source it never crashed), so I played a game which makes the CPU work abit, and I thought I'll get a crash log - which I didn't get. The last radio signal I got from the phone was this:
I/LibraryLoader( 2817): Expected native library version number "",actual native
library version number ""
I/chromium( 2817): [INFO:library_loader_hooks.cc(116)] Chromium logging enabled:
level = 0, default verbosity = 0
I/BrowserStartupController( 2817): Initializing chromium process, renderers=0
D/TinyALSA-Audio Hardware( 1855): audio_hw_get_mic_mute(0x4003e938, 0x4126daeb)
D/BluetoothManagerService( 2205): Message: 20
D/BluetoothManagerService( 2205): Added callback: android.bluetooth.IBluetoothMa
[email protected]:true
D/BluetoothAdapter( 2817): 1112752792: getState() : mService = null. Returning
STATE_OFF
D/libEGL ( 2817): loaded /system/lib/egl/libEGL_mali.so
D/libEGL ( 2817): loaded /system/lib/egl/libGLESv1_CM_mali.so
D/libEGL ( 2817): loaded /system/lib/egl/libGLESv2_mali.so
E/ ( 2817): Device driver API match
E/ ( 2817): Device driver API version: 23
E/ ( 2817): User space API version: 23
E/ ( 2817): mali: REVISION=Linux-r3p2-01rel3 BUILD_DATE=Wed Oct 9 21:05:
57 KST 2013
W/chromium( 2817): [WARNINGroxy_service.cc(890)] PAC support disabled because
there is no system implementation
I/chromium( 2817): [INFO:CONSOLE(0)] "Document was loaded from Application Cache
with manifest {URL}
k-core-v40.appcache", source: {URL}
d/sdk/native/sdk-core-v40.html (0)
I/chromium( 2817): [INFO:CONSOLE(0)] "Application Cache Checking event", source:
{URL}
l (0)
I/chromium( 2817): [INFO:CONSOLE(0)] "Application Cache NoUpdate event", source:
{URL}
l (0)
W/chromium( 6284): [WARNINGroxy_service.cc(890)] PAC support disabled because
there is no system implementation
I/chromium( 6284): [INFO:simple_index_file.cc(437)] Simple Cache Index is being
restored from disk.
D/Yamaha-MC1N2-Audio( 1855): yamaha_mc1n2_audio_output_stop()
D/Yamaha-MC1N2-Audio( 1855): yamaha_mc1n2_audio_route_start()
Click to expand...
Click to collapse
I've tried tracing the log files the system automatically creates in the ./system folder, but I couldn't find any useful information except from some deamon crash logs.
I tried resetting the dalvik cache, reinstalling my ROM manually (adb sideload), preforming a complete factory reset and wiping cache partition, and yet it didn't work.
I'm quite sure the issue relates to my phone's battery (which overheated a bit when I used it for a long time), but I'm still not completely sure this is the issue, so I would like to hear your suggestions.
Thanks in advance,
Eden
Eden Campo said:
Hello there,
....
I've tried tracing the log files the system automatically creates in the ./system folder, but I couldn't find any useful information except from some deamon crash logs.
I tried resetting the dalvik cache, reinstalling my ROM manually (adb sideload), preforming a complete factory reset and wiping cache partition, and yet it didn't work.
I'm quite sure the issue relates to my phone's battery (which overheated a bit when I used it for a long time), but I'm still not completely sure this is the issue, so I would like to hear your suggestions.
Thanks in advance,
Eden
Click to expand...
Click to collapse
I also read your logcat or yeah the part of it and it seems all to be fine, normal lines.
I don't own the S2 anymore and I didn't had the issue. But I suggest to try somethings first before buying a new battery.
Try another rom instead of cyanogenmod, Cyanogenmod is supporting Alot of devices and it's not really good specific for devices so I suggest to try one of the roms from the development forums.(Cyanogenmod always have bugs.)
Try to flash back to stock with odin
Try to borrow a battery from a friend and see or you still have the same problem
Remove the battery out of the phone and leave your phone without a battery for like 1-5 minutes.
It could be maybe the battery that it got issues cause the S2 is not the newest phone anymore and hardware also has a lifetime sadly. But your screen goes black and your device goes off right?
Hi guys,
my problem is that my Nexus 5 is rebooting all the time since yesterday. My roommate had the same problem yesterday, but now its suddenly gone. My Android version is 6.0.1 and I can tell you the last few logs before the restart occures:
Code:
03-12 15:17:51.221 203-924/? D/NuPlayerDriver: reset(0xb60585e0)
03-12 15:17:51.221 203-924/? D/NuPlayerDriver: notifyListener_l(0xb60585e0), (8, 0, 0)
03-12 15:17:51.221 203-7815/? D/NuPlayerDriver: notifyResetComplete(0xb60585e0)
03-12 15:17:51.222 812-826/? I/ActivityManager: Killing 4914:android.process.acore/u0a2 (adj 15): empty #17
03-12 15:17:52.052 1908-4068/? W/ctxmgr: [AclManager]checkPermissionTypeStatus: no inject permission for { uid=10010, packageName=com.google.android.gms }. Returned permission was: PACKAGE_NOT_WHITELISTED for context name=POWER_CONNECTION, account=account#-517948760#
03-12 15:17:52.054 1908-4068/? W/ctxmgr: [AclManager]checkPermissionTypeStatus: no inject permission for { uid=10010, packageName=com.google.android.gms }. Returned permission was: PACKAGE_NOT_WHITELISTED for context name=POWER_CONNECTION, account=account#-517948760#
03-12 15:17:52.055 1908-1908/? E/ctxmgr: [PowerConnectionProducer]Could not write powerInfo=Plug state: 2 BatteryLevel: 0.77, status=Status{statusCode=unknown status code: 7503, resolution=null}
01-01 00:00:00.000 0-0/? E/Internal: device 'XXXXXXXXX' not found
I really have no idea where to start looking for the problem. I mean, the log does not tell me much about a fault or something like that and as far as I know Android does not provide crash logs on reboot.
Do you have any hints?
Ah and by the way: The only app I installed recently before the problem occured was runtastic, but removing it did not change anything.
Best regards,
Arma
Ok, it was the power button...
I would get a case that protects the power button .
Removed
moto actions?
the system is not compatible with the Turbo Power function, it is not the charger because I tested it in Lineage 15 and it is working perfectly
KamiGooDz said:
moto actions?
Click to expand...
Click to collapse
Yes, it's available
snapchat don't work, how fix?
Update
aicp_montana_o-13.1-UNOFFICIAL-20190116
Changes
January security patch
Fixed battery drain on devices without NFC
Changed default CPU governor for the little cluster to interactive (was performance before, caused some battery drain as well)
Download: http://www.mediafire.com/file/3cblc9qd2zjqera/aicp_montana_o-13.1-UNOFFICIAL-20190116.zip/file
FpX said:
the system is not compatible with the Turbo Power function, it is not the charger because I tested it in Lineage 15 and it is working perfectly
Click to expand...
Click to collapse
On my device it shows "charging slowly" but after a few seconds/minutes it starts charging quickly. Can you take a logcat?
KamiGooDz said:
snapchat don't work, how fix?
Click to expand...
Click to collapse
I think you need to pass the SafetyNet check for it to work. I passed SafetyNet on this ROM by installing the SafetyPatch Magisk module and enabling Magisk Hide for Google Services Framework and Google Play Store.
AsD Monio said:
aicp_montana_o-13.1-UNOFFICIAL-20190116
Changes
January security patch
Fixed battery drain on devices without NFC
Changed default CPU governor for the little cluster to interactive (was performance before, caused some battery drain as well)
Download: http://www.mediafire.com/file/3cblc9qd2zjqera/aicp_montana_o-13.1-UNOFFICIAL-20190116.zip/file
On my device it shows "charging slowly" but after a few seconds/minutes it starts charging quickly. Can you take a logcat?
I think you need to pass the SafetyNet check for it to work. I passed SafetyNet on this ROM by installing the SafetyPatch Magisk module and enabling Magisk Hide for Google Services Framework and Google Play Store.
Click to expand...
Click to collapse
01-19 12:02:45.025 W/BroadcastQueue( 704): Background execution not allowed: receiving Intent { act=android.intent.action.ACTION_POWER_DISCONNECTED flg=0x4000010 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver
01-19 12:02:45.060 E/MDMCTBK ( 753): [0] - showStatus:MdmCutbackHndler Status: Qmi =1, cg=0, ep=0, vc=0, dc=0, cn=0, wf=0, mf=0,wfd=0, apm=0, usb=0, stopqmi=0, wireless=0, bf=1, md=0,fpf=1
01-19 12:02:45.064 E/MDMCTBK ( 753): [0] - eventLoop:Event Loop - time to execute = 0.003964(secs)
01-19 12:02:45.064 E/MDMCTBK ( 753): [0] - eventLoop:Event Loop - time to execute = 0.000189(secs)
01-19 12:02:45.082 E/BatteryExternalStatsWorker( 704): no controller energy info supplied for bluetooth
01-19 12:02:45.113 E/QCOM PowerHAL( 488): extract_stats: failed to open: /d/system_stats Error = No such file or directory
01-19 12:02:45.114 E/BatteryExternalStatsWorker( 704): modem info is invalid: ModemActivityInfo{ mTimestamp=3549929 mSleepTimeMs=3248076 mIdleTimeMs=-3228711 mTxTimeMs[]=[0, 0, 0, 0, 0] mRxTimeMs=280 mEnergyUsed=0}
01-19 12:02:45.173 E/MDMCTBK ( 753): [0] - eventLoop:Event Loop - time to execute = 0.000448(secs)
anybody tested nin moto g5S xt1795 indian edition
anybody tested in moto g5S xt1795 indian edition
---------- Post added at 07:28 AM ---------- Previous post was at 07:26 AM ----------
anybody tested in moto g5S xt1795 indian edition
---------- Post added at 07:29 AM ---------- Previous post was at 07:28 AM ----------
anybody tested in moto g5S xt1795 indian edition ?
FpX said:
01-19 12:02:45.025 W/BroadcastQueue( 704): Background execution not allowed: receiving Intent { act=android.intent.action.ACTION_POWER_DISCONNECTED flg=0x4000010 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver
01-19 12:02:45.060 E/MDMCTBK ( 753): [0] - showStatus:MdmCutbackHndler Status: Qmi =1, cg=0, ep=0, vc=0, dc=0, cn=0, wf=0, mf=0,wfd=0, apm=0, usb=0, stopqmi=0, wireless=0, bf=1, md=0,fpf=1
01-19 12:02:45.064 E/MDMCTBK ( 753): [0] - eventLoop:Event Loop - time to execute = 0.003964(secs)
01-19 12:02:45.064 E/MDMCTBK ( 753): [0] - eventLoop:Event Loop - time to execute = 0.000189(secs)
01-19 12:02:45.082 E/BatteryExternalStatsWorker( 704): no controller energy info supplied for bluetooth
01-19 12:02:45.113 E/QCOM PowerHAL( 488): extract_stats: failed to open: /d/system_stats Error = No such file or directory
01-19 12:02:45.114 E/BatteryExternalStatsWorker( 704): modem info is invalid: ModemActivityInfo{ mTimestamp=3549929 mSleepTimeMs=3248076 mIdleTimeMs=-3228711 mTxTimeMs[]=[0, 0, 0, 0, 0] mRxTimeMs=280 mEnergyUsed=0}
01-19 12:02:45.173 E/MDMCTBK ( 753): [0] - eventLoop:Event Loop - time to execute = 0.000448(secs)
Click to expand...
Click to collapse
All of these lines are also present in the logcat on my device and they do not seem to be related to charging. Can you send the full logcat? And maybe a dmesg kernel log since it may be kernel related. Also, what model do you have (XTxxxx) and which firmware are you running? Does it still not work in the new build? The old one from the 13th had some battery drain which could result in slow charging, especially on models without NFC - the NFC service caused a permanent wakelock.
AsD Monio said:
All of these lines are also present in the logcat on my device and they do not seem to be related to charging. Can you send the full logcat? And maybe a dmesg kernel log since it may be kernel related. Also, what model do you have (XTxxxx) and which firmware are you running? Does it still not work in the new build? The old one from the 13th had some battery drain which could result in slow charging, especially on models without NFC - the NFC service caused a permanent wakelock.
Click to expand...
Click to collapse
I was using the previous build, now it's working perfectly, thanks!
Update
aicp_montana_o-13.1-UNOFFICIAL-20190121
Changes
Enforcing SELinux
Download: http://www.mediafire.com/file/hquz82ge8werfgf/aicp_montana_o-13.1-UNOFFICIAL-20190121.zip/file
Thanks, ROM is quite stable. I have a question-
How to enable the front battery led for notifications, similar to crdroid in this ROM.
newinnov said:
Thanks, ROM is quite stable. I have a question-
How to enable the front battery led for notifications, similar to crdroid in this ROM.
Click to expand...
Click to collapse
Settings -> Apps and notifications -> Notifications -> Notification LED
I think it should be enabled by default.
AsD Monio said:
Settings -> Apps and notifications -> Notifications -> Notification LED
I think it should be enabled by default.
Click to expand...
Click to collapse
Yes, It was indeed! Actually I flashed the custom kernel on top of that , somehow that was causing trouble. Thanks again.
Flashed it om my wifes phone yesterday, she's very happy, less battery drain and wifi is better, which was the main reason to try a custom rom.
Thanks guys!
Hi, is Fingerprint, camera photo/video recording, and Moto display notifications working good ?
Thank´s
One thing is weird, the phone always reboots to twrp. To boot the system I then have to reboot from twrp to bootloader and then press "start"
SvenHee said:
One thing is weird, the phone always reboots to twrp. To boot the system I then have to reboot from twrp to bootloader and then press "start"
Click to expand...
Click to collapse
I had that happen to me as well, it's not the ROM's fault. Either fastboot or the stock recovery store some data in the /misc partition. That tells the bootloader/kernel to boot to recovery by default. It's probably meant to ensure that a partially upgraded system does not get booted while flashing a stock ROM. To fix it just wipe the /misc partition, I recommend making a backup first. I used dd in the terminal in TWRP for both operations (adb shell will work as well but it has some problems with displaying some characters in the Windows command prompt). To back up the partition:
Code:
dd if=/dev/block/bootdevice/by-name/misc of=/external_sd/misc.img
^ (replace "external_sd" with "data/media/0" to save it in the internal storage instead of the external microSD card)
To wipe /misc:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc
It may also work using fastboot, though I have not tried this way:
Code:
fastboot erase misc
Thanks!
That is slightly intimidating to execute but I'll give it a go!
aicp_montana_o-13.1-UNOFFICIAL-20190116
My device : xt1799-2
64bit os.
VoLte works for my xt1799-2.
Bugs:
1. Can't copy any file from the device to my PC. The same bug in crDroid 8.1.0 rom. And lineageos. This happens in all the third party rom between 8.1.0-9.0. Date at least before 2019-09-23. But can copy the folder from the device. But also can send file to the device, so weird.
________________________________________________
I see the lineageos 15.1 changelog:
2019-09-23:
September security patch
Optimized SEPolicy
Fixed MTP (thanks to @wiktorek140)
We're back to LTE
________________________________________________
But can copy the folder from the device. But also can send file to the device, so weird.
2. Front camera doesn't work.
3. Fingerprint doesn't work.
4. Delay a lot when you scroll the page, or move the app icon. The same bug in crDroid 8.1.0.
5. Call recorder. If you don't open the speaker, the inner voice recorded from the other side is too small, unable to hear it clearly.