need support with a logcat. would appreciate any insight - Nexus S Q&A, Help & Troubleshooting

I am on Paranoid Android 1.9.2 (JB) with default kernel and settings.
Of course, my device is Nexus S with amoled.
Overnight, I observed that the system is waking up quite often. battery usage screenshot, logcat, wakelock are attached.
Checking the logcat, I could only find below every 30 minutes or so popping up regularly. Since, looking into Android logcat is something new to me, I would like support of the experienced with some time to spare and kind heart to care.
===================================
[ 08-02 03:31:22.062 267: 596 E/NotificationService ]
An error occurred profiling the notification.
java.lang.NullPointerException
at com.android.server.NotificationManagerService.enqueueNotificationInternal(NotificationManagerService.java:1147)
at com.android.server.NotificationManagerService.enqueueNotificationWithTag(NotificationManagerService.java:983)
at android.app.INotificationManager$Stub.onTransact(INotificationManager.java:129)
at android.os.Binder.execTransact(Binder.java:367)
at dalvik.system.NativeStart.run(Native Method)
[ 08-02 03:31:22.082 267: 284 E/NotificationService ]
An error occurred profiling the notification.
java.lang.NullPointerException
at com.android.server.NotificationManagerService.enqueueNotificationInternal(NotificationManagerService.java:1147)
at com.android.server.am.ServiceRecord$1.run(ServiceRecord.java:368)
at android.os.Handler.handleCallback(Handler.java:615)
at android.os.Handler.dispatchMessage(Handler.java:92)
at android.os.Looper.loop(Looper.java:137)
at com.android.server.am.ActivityManagerService$AThread.run(ActivityManagerService.java:1431)

Related

race condition between lowmemorykiller and ActivityManager?

Having the game Dead Trigger lag on my phone sometimes have prompted me to investigate further about why it lags only sometimes.
I realise that the lowmemorykiller have kicked into action when Dead Trigger is being played, and some processes are being killed. However, the ActivityManager will actually attempt to restart them back, from logcat, I get two types of messages, one is like
I/ActivityManager( 250): Process com.google.android.gsf.login (pid 18553) has died.
...
I/ActivityManager( 250): Start proc com.google.android.gsf.login for service com.google.android.gsf.login/com.google.android.gsf.loginservice.GoogleLoginService: pid=18790 uid=10012 gids={3003, 1015, 1028, 1007, 2001, 3006}
And the second type is like this:
I/ActivityManager( 250): Process com.google.android.apps.maps (pid 18716) has died.
W/ActivityManager( 250): Scheduling restart of crashed service com.google.android.apps.maps/com.google.googlenav.prefetch.android.PrefetcherService in 20000ms
What I don't get is that, doesn't this causes the process/service to be killed and restarted, killed and restarted, when I am having a foreground app that needs a lot of memory??
I would have expected ActivityManager to not restart the apps back when they are being killed by the lowmemorykiller, but it seems like there's no way the ActivityManager can know.
should I repost this in the Android General section?

Apps keep blinking/pausing/refreshing

I'm having a strange problem here on my Nexus 4. Lately, a problem has come up that seems to be affecting pretty much any app that I happen to be running. The apps just seem to get interrupted in some way for a split second. This manifests itself in different ways depending on what app I'm running, some more annoying than others. And this seems to happen every couple of minutes, so its very frequent.
Chrome scrolls back to the top of whatever page I'm currently reading and resets to the default zoom level.
The browser in RedditIsFun does the same thing.
Gmail just flashes white for a moment.
Youtube flashes black for a split second and pauses the video.
Netflix flashes black for a split second and pauses the video.
Mxplayer flashes black for a split second and then continues playing a video.
It seems to be affecting other apps too, but these are the ones I use the most, so I have noticed it a lot.
Last night I finally upgraded from JellyBean to KitKat, hoping that might resolve the problem, but it didn't help.
I checked my logcat files after the problems were happening, and I filtered them to just display information about the app I was running.
Here is the log info for netflix, during which the problem occurred multiple times.
Code:
01-15 00:44:05.262 I/ActivityManager(637): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.netflix.mediaclient/.UIWebViewActivity bnds=[6,486][154,660]} from pid 1267
01-15 00:44:05.362 I/ActivityManager(637): Start proc com.netflix.mediaclient for activity com.netflix.mediaclient/.UIWebViewActivity: pid=25960 uid=10076 gids={50076, 3002, 3003}
01-15 00:44:07.605 I/ActivityManager(637): START u0 {flg=0x4000000 cmp=com.netflix.mediaclient/.ui.home.HomeActivity (has extras)} from pid 25960
01-15 00:45:38.442 I/ActivityManager(637): START u0 {flg=0x20000 cmp=com.netflix.mediaclient/.ui.details.MovieDetailsActivity (has extras)} from pid 25960
01-15 00:45:50.064 I/ActivityManager(637): START u0 {flg=0x20000 cmp=com.netflix.mediaclient/.ui.details.MovieDetailsActivity (has extras)} from pid 25960
01-15 00:46:17.033 I/ActivityManager(637): START u0 {flg=0x20000 cmp=com.netflix.mediaclient/.ui.details.MovieDetailsActivity (has extras)} from pid 25960
01-15 00:47:58.982 I/ActivityManager(637): START u0 {flg=0x20000 cmp=com.netflix.mediaclient/.ui.details.MovieDetailsActivity (has extras)} from pid 25960
01-15 00:49:50.291 I/ActivityManager(637): START u0 {act=android.intent.action.VIEW cmp=com.netflix.mediaclient/.ui.search.SearchActivity} from pid 25960
01-15 00:50:19.562 I/ActivityManager(637): START u0 {flg=0x20000 cmp=com.netflix.mediaclient/.ui.details.MovieDetailsActivity (has extras)} from pid 25960
01-15 00:50:38.782 I/ActivityManager(637): START u0 {flg=0x20000 cmp=com.netflix.mediaclient/.ui.details.MovieDetailsActivity (has extras)} from pid 25960
01-15 00:50:56.992 I/ActivityManager(637): START u0 {act=android.intent.action.VIEW cmp=com.netflix.mediaclient/.ui.search.SearchActivity} from pid 25960
01-15 00:51:08.114 I/ActivityManager(637): START u0 {flg=0x20000 cmp=com.netflix.mediaclient/.ui.details.MovieDetailsActivity (has extras)} from pid 25960
01-15 00:51:23.720 I/ActivityManager(637): START u0 {act=android.intent.action.VIEW cmp=com.netflix.mediaclient/.ui.search.SearchActivity} from pid 25960
01-15 00:51:39.307 I/ActivityManager(637): START u0 {cmp=com.netflix.mediaclient/.ui.search.SearchQueryDetailsActivity (has extras)} from pid 25960
01-15 00:51:47.656 I/ActivityManager(637): START u0 {cmp=com.netflix.mediaclient/.ui.details.ShowDetailsActivity (has extras)} from pid 25960
01-15 00:52:01.661 I/ActivityManager(637): START u0 {act=android.intent.action.VIEW cmp=com.netflix.mediaclient/.ui.search.SearchActivity} from pid 25960
01-15 00:52:15.455 I/ActivityManager(637): START u0 {cmp=com.netflix.mediaclient/.ui.details.ShowDetailsActivity (has extras)} from pid 25960
01-15 00:53:38.314 I/ActivityManager(637): START u0 {flg=0x20000 cmp=com.netflix.mediaclient/.ui.player.PlayerActivity (has extras)} from pid 25960
01-15 00:53:38.784 I/WindowManager(637): Screen frozen for +404ms due to Window{424dcb48 u0 com.netflix.mediaclient/com.netflix.mediaclient.ui.player.PlayerActivity}
01-15 00:54:33.763 I/WindowManager(637): Screen frozen for +315ms due to Window{428887e8 u0 com.netflix.mediaclient/com.netflix.mediaclient.ui.details.ShowDetailsActivity}
01-15 00:55:01.412 I/ActivityManager(637): START u0 {flg=0x20000 cmp=com.netflix.mediaclient/.ui.player.PlayerActivity (has extras)} from pid 25960
01-15 00:55:01.793 I/WindowManager(637): Screen frozen for +360ms due to Window{42181748 u0 com.netflix.mediaclient/com.netflix.mediaclient.ui.player.PlayerActivity}
01-15 00:55:31.114 I/ActivityManager(637): START u0 {act=android.intent.action.VIEW cmp=com.netflix.mediaclient/.ui.search.SearchActivity} from pid 25960
01-15 00:55:51.556 I/ActivityManager(637): START u0 {flg=0x20000 cmp=com.netflix.mediaclient/.ui.player.PlayerActivity (has extras)} from pid 25960
01-15 00:55:51.936 I/WindowManager(637): Screen frozen for +333ms due to Window{423ac418 u0 com.netflix.mediaclient/com.netflix.mediaclient.ui.player.PlayerActivity}
01-15 01:01:25.182 I/WindowManager(637): Screen frozen for +133ms due to Window{423ac418 u0 com.netflix.mediaclient/com.netflix.mediaclient.ui.player.PlayerActivity}
01-15 01:01:27.615 I/ActivityManager(637): START u0 {flg=0x20000 cmp=com.netflix.mediaclient/.ui.player.PlayerActivity (has extras)} from pid 25960
01-15 01:01:27.995 I/WindowManager(637): Screen frozen for +359ms due to Window{41fc2fb8 u0 com.netflix.mediaclient/com.netflix.mediaclient.ui.player.PlayerActivity}
01-15 01:11:26.003 I/WindowManager(637): Screen frozen for +54ms due to Window{41fc2fb8 u0 com.netflix.mediaclient/com.netflix.mediaclient.ui.player.PlayerActivity}
01-15 01:11:26.594 I/WindowManager(637): Screen frozen for +350ms due to Window{422c9448 u0 com.netflix.mediaclient/com.netflix.mediaclient.ui.details.ShowDetailsActivity}
01-15 01:11:28.356 I/ActivityManager(637): START u0 {flg=0x20000 cmp=com.netflix.mediaclient/.ui.player.PlayerActivity (has extras)} from pid 25960
01-15 01:11:28.736 I/WindowManager(637): Screen frozen for +362ms due to Window{422e9460 u0 com.netflix.mediaclient/com.netflix.mediaclient.ui.player.PlayerActivity}
01-15 01:35:06.729 I/ActivityManager(637): START u0 {flg=0x20000 cmp=com.netflix.mediaclient/.ui.player.PlayerActivity (has extras)} from pid 25960
01-15 01:35:06.839 I/MediaFocusControl(637): AudioFocus requestAudioFocus() from [email protected][email protected]
01-15 01:35:07.100 E/NetflixTransport-JNI(25960): Java_com_netflix_mediaclient_javabridge_transport_NativeTransport_native_1setVOapi systemAndroid set VO API
01-15 01:35:07.100 E/NetflixTransport-JNI(25960): Custom params sw analytics params set
01-15 01:35:07.130 I/ActivityManager(637): Displayed com.netflix.mediaclient/.ui.player.PlayerActivity: +381ms
01-15 01:35:07.130 I/WindowManager(637): Screen frozen for +356ms due to Window{42181748 u0 com.netflix.mediaclient/com.netflix.mediaclient.ui.player.PlayerActivity}
01-15 01:41:27.275 I/MediaFocusControl(637): AudioFocus abandonAudioFocus() from [email protected][email protected]
01-15 01:41:27.305 I/WindowManager(637): Screen frozen for +76ms due to Window{42181748 u0 com.netflix.mediaclient/com.netflix.mediaclient.ui.player.PlayerActivity}
01-15 01:41:27.375 I/MediaFocusControl(637): AudioFocus requestAudioFocus() from [email protected][email protected]
01-15 01:41:27.896 I/WindowManager(637): Screen frozen for +332ms due to Window{4244b4c0 u0 com.netflix.mediaclient/com.netflix.mediaclient.ui.details.ShowDetailsActivity}
01-15 01:41:27.936 I/MediaFocusControl(637): AudioFocus abandonAudioFocus() from [email protected][email protected]
01-15 01:44:49.331 I/ActivityManager(637): START u0 {flg=0x20000 cmp=com.netflix.mediaclient/.ui.player.PlayerActivity (has extras)} from pid 25960
01-15 01:44:49.441 I/MediaFocusControl(637): AudioFocus requestAudioFocus() from [email protected][email protected]
01-15 01:44:49.681 E/NetflixTransport-JNI(25960): Java_com_netflix_mediaclient_javabridge_transport_NativeTransport_native_1setVOapi systemAndroid set VO API
01-15 01:44:49.681 E/NetflixTransport-JNI(25960): Custom params sw analytics params set
01-15 01:44:49.721 I/ActivityManager(637): Displayed com.netflix.mediaclient/.ui.player.PlayerActivity: +382ms
01-15 01:44:49.721 I/WindowManager(637): Screen frozen for +364ms due to Window{422e9460 u0 com.netflix.mediaclient/com.netflix.mediaclient.ui.player.PlayerActivity}
01-15 01:46:14.662 I/MediaFocusControl(637): AudioFocus abandonAudioFocus() from [email protected][email protected]
01-15 01:46:44.784 W/PackageManager(637): Unknown permission com.amazon.permission.SET_FLAG_NOSOFTKEYS in package com.netflix.mediaclient
01-15 01:48:50.488 I/ActivityManager(637): START u0 {flg=0x20000 cmp=com.netflix.mediaclient/.ui.player.PlayerActivity (has extras)} from pid 25960
01-15 01:48:50.598 I/MediaFocusControl(637): AudioFocus requestAudioFocus() from [email protected][email protected]
01-15 01:48:50.849 E/NetflixTransport-JNI(25960): Java_com_netflix_mediaclient_javabridge_transport_NativeTransport_native_1setVOapi systemAndroid set VO API
01-15 01:48:50.849 E/NetflixTransport-JNI(25960): Custom params sw analytics params set
01-15 01:48:50.879 I/ActivityManager(637): Displayed com.netflix.mediaclient/.ui.player.PlayerActivity: +378ms (total +2m43s171ms)
01-15 01:48:50.879 I/WindowManager(637): Screen frozen for +361ms due to Window{421856c8 u0 com.netflix.mediaclient/com.netflix.mediaclient.ui.player.PlayerActivity}
01-15 01:51:27.946 I/MediaFocusControl(637): AudioFocus abandonAudioFocus() from [email protected][email protected]
01-15 01:51:27.956 I/WindowManager(637): Screen frozen for +50ms due to Window{421856c8 u0 com.netflix.mediaclient/com.netflix.mediaclient.ui.player.PlayerActivity}
01-15 01:51:28.016 I/MediaFocusControl(637): AudioFocus requestAudioFocus() from [email protected][email protected]
01-15 01:51:28.537 I/WindowManager(637): Screen frozen for +332ms due to Window{422c3d20 u0 com.netflix.mediaclient/com.netflix.mediaclient.ui.details.ShowDetailsActivity}
01-15 01:51:28.547 I/MediaFocusControl(637): AudioFocus abandonAudioFocus() from [email protected][email protected]
I checked over the logs for several other apps like Youtube and Chrome, and I see the common thing between them is the following line:
01-15 01:51:28.537 I/WindowManager(637): Screen frozen for +332ms due to Window{422c3d20 u0 com.netflix.mediaclient/com.netflix.mediaclient.ui.details.ShowDetailsActivity}
Everytime my screen freezes up, this line is there saying that the screen was indeed frozen.
What could be causing this??
Try a factory reset
Sent from my GT-I9070 using Tapatalk
PradeepMurugan said:
Try a factory reset
Sent from my GT-I9070 using Tapatalk
Click to expand...
Click to collapse
Will this unroot my phone?
Zarxrax said:
Will this unroot my phone?
Click to expand...
Click to collapse
Factory reset will delete the supersu app but not the binaries, so after factory reset just install supersu app that's enough
Sent from my GT-I9070 using Tapatalk
This worked. Everything is working correctly now.
Well, the problem seems to have started up again. I happened to notice it a few days ago, then rebooted and everything was back to normal. Now today it has started happening again and a reboot didn't fix it.
I'm not sure what could be going on here.
Several months later, I'm still struggling with this. Someone had suggested wiping the caches in the clockwork mod boot screen, which doesn't really seem to be any more effective than rebooting.
Sometimes the problem does not occur for several hours or days after I reboot. Sometimes it starts happening immediately after I reboot. I was thinking perhaps some app I have installed is causing it, but I have not been able to isolate anything in particular.
Does anyone out there have any other ideas? This is really diving me crazy. This page refreshed 3 times while I was writing this post.

Screen Randomly Turn off & Flicker in Dark [Possible Fix added]

As it say in title my N5's Screen Randomly Turn off & Flicker in Dark (any ROM..stock 6.0.1/Pure nexus/AOSPA 7.1)
after sceen goes off it doesn't wake by power button or any other means till either i turn on the light in room or force reboot by holding power button.
Important things to consider :
Random (mostly happens on Browsing, Streaming video in chrome, FB , News apps But never happened in YouTube or MX Player while playing video)
Only happens in Dark (it never happened in Day)
Can easily wake the sceen once i turn on light in room but there is no other way to turns it on in Dark once it goes off.
Some times Screen flickers before going off (not always)
from this points i tend to believe it's related to proximity sensor but tried checking it's working via some apps and they shows it's working perfectly.
even tried resting proximity data via EFS backup still no luck.
if you know something about this issue kindly help
Thanks in advance
i have the same problem.
i onlin turn on the image when disconnect the baterry for 2 or 3 minutes, but nothing resolve the problem.
i chainge the lcd but not resolve the problema.
jineshpatel30 said:
As it say in title my N5's Screen Randomly Turn off & Flicker in Dark (any ROM..stock 6.0.1/Pure nexus/AOSPA 7.1)
after sceen goes off it doesn't wake by power button or any other means till either i turn on the light in room or force reboot by holding power button.
Important things to consider :
Random (mostly happens on Browsing, Streaming video in chrome, FB , News apps But never happened in YouTube or MX Player while playing video)
Only happens in Dark (it never happened in Day)
Can easily wake the sceen once i turn on light in room but there is no other way to turns it on in Dark once it goes off.
Some times Screen flickers before going off (not always)
from this points i tend to believe it's related to proximity sensor but tried checking it's working via some apps and they shows it's working perfectly.
even tried resting proximity data via EFS backup still no luck.
if you know something about this issue kindly help
Thanks in advance
Click to expand...
Click to collapse
@devs Kindly check logs in attachment and help me in finding exact culprit for this problem (with possible solution )
this type of entries are present all over the logs (i don't know if it's relevant to this issue or not)
Code:
07-31 00:19:30.312 I/WindowManager( 752): Screen frozen for +223ms due to Window{1c3e4be u0 NavigationBar}
07-31 00:19:31.630 I/ActivityManager( 752): Waited long enough for: ServiceRecord{834a3ca u0 com.whatsapp/.messaging.MessageService}
07-31 00:21:19.461 I/PowerManagerService( 752): Going to sleep due to power button (uid 1000)...
07-31 00:21:20.088 I/DisplayManagerService( 752): Display device changed state: "Built-in Screen", OFF
07-31 00:21:20.363 I/PowerManagerService( 752): Sleeping (uid 1000)...
07-31 00:21:20.493 I/ActivityManager( 752): Config changes=480 {1.0 404mcc57mnc en_IN ldltr sw360dp w360dp h576dp 480dpi nrml port finger -keyb/v/h -nav/h as.1 s.9}
07-31 00:21:20.573 I/PowerManagerService( 752): Waking up from sleep (uid 1000)...
07-31 00:21:20.589 I/DisplayPowerController( 752): Blocking screen on until initial contents have been drawn.
07-31 00:21:20.668 I/DisplayManagerService( 752): Display device changed state: "Built-in Screen", ON
07-31 00:21:20.865 D/PowerManagerService( 752): acquireWakeLock: ignoring request from com.android.nfc
07-31 00:21:21.021 D/PowerManagerService( 752): acquireWakeLock: ignoring request from com.android.nfc
07-31 00:21:21.050 I/DisplayPowerController( 752): Unblocked screen on after 461 ms
07-31 00:21:22.239 I/PowerManagerService( 752): Going to sleep due to power button (uid 1000)...
07-31 00:21:22.826 I/DisplayManagerService( 752): Display device changed state: "Built-in Screen", OFF
07-31 00:21:23.101 I/PowerManagerService( 752): Sleeping (uid 1000)...
07-31 00:21:23.133 D/PowerManagerService( 752): acquireWakeLock: ignoring request from com.android.nfc
07-31 00:21:34.403 I/PowerManagerService( 752): Waking up from sleep (uid 1000)...
07-31 00:21:34.464 I/DisplayPowerController( 752): Blocking screen on until initial contents have been drawn.
07-31 00:21:34.491 D/PowerManagerService( 752): acquireWakeLock: ignoring request from com.android.nfc
07-31 00:21:34.548 I/DisplayManagerService( 752): Display device changed state: "Built-in Screen", ON
07-31 00:21:34.624 I/DisplayPowerController( 752): Unblocked screen on after 160 ms
@marcomarinho i know you are busy with PA but if you get some time please check this and let me know what you find
i have this issue before when I'm watching youtube vids specially when the phone is in landscape mode, happens also 1 time when i was playing.
Edit: The lcd of my device has already been replaced.
Any input from logs ?
@osm0sis if you get some please take a look at logs and let me know if you find cause of issue in OP.
Thanks in advance
Turning OFF "adaptive (auto) brightness" seems to fix the problem.. atleast for now. Not a ideal solution but still..
So i guess issue is related to light sensor.

[ROM][flo][deb][7.1.2]USB Host based on RR and Timur's

The ROM is designed to be used as a fixed car dash installation.
Rom based on Resurection Remix nougat, ElementalX kernel with Timur's usb host mode.
Features in addition to Resurection Remix and ElementalX:
Code:
- USB Host Mode with External Power
- Fast Charging while in USB Host Mode
- FI-Mode - Auto-Suspend on Power-Loss
- Preferred Slot Auto-Mounting of up 4 USB Drives
- Firm Sleep + RTC Alarm Killer (barely uses battery when suspended)
- Easy App-Killer for reliable Suspend mode
- Power-Up On-Screen-Display
- HD/Hi-Res UVC Frame-Grabber support for Backup-Cam with MJPG encoding
- Set to permissive permanently (required by PowerEventMgr)
- Magisk SU
​-INITIAL INSTALLATION INSTRUCTIONS-
- Download the latest build
- Download BeansGapps-Mini
- Full wipe and factory reset
- Flash ROM using TWRP 3.x Recovery
- Flash Gapps
- Reboot
- Enable SU for PowerEventMgr in Magisk
-Installation Files-
TWRP
Flo (WiFi) Builds
Deb (LTE) Builds
BeansGapps-Mini
-UVC Frame-Grabber support-
Driver modules for frame grabbers are in /system/lib/modules directory. You need to load the drivers in /data/local/userinit.sh using insmod.
Example for oryginal EasyCAP DC60:
Code:
insmod /system/lib/modules/saa7115.ko
insmod /system/lib/modules/stk1160.ko
Install VCam2.apk (available in Download section) app and enable detection mode in PowerEventManager.
-Battery-less instalation-
-FI-mode-
-Car installation hints-
To create good looking and easy to use desktop for car dash you can use psd files:
Car dash wallpaper images.
It can be used with following apps to create home screen with transparent widgets that will start apps:
Desktop VisualizeR
Nova Launcher
-External resources-
Timur's kernel
-Changelog-
Code:
v5.8.5-20171215
- Merged with latest RR repo v5.8.5 Android 7.1.2_r36
- USB audio drivers included in kernel
- Fixed settings bug
- Fixed SU problems and USB drive permission problems
- Clean install recommended
-Github Source-
-Common problems-
- USB audio is crackling: https://forum.xda-developers.com/showpost.php?p=74920088&postcount=51
XDA:DevDB Information
USB Host, ROM for the Nexus 7 (2013)
Contributors
elektro255, apascual89, Timur
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Based On: LineageOS
Version Information
Status: Beta
Current Beta Version: v5.8.5-20171215
Beta Release Date: 2017-12-15
Created 2017-08-20
Last Updated 2018-01-06
For USB Audio I had to use the following userinit.sh
insmod /system/lib/modules/ssnd-hwdep.ko
insmod /system/lib/modules/snd-usbmidi-lib.ko
insmod /system/lib/modules/snd-usb-audio.ko
pacmanb said:
For USB Audio I had to use the following userinit.sh
insmod /system/lib/modules/ssnd-hwdep.ko
insmod /system/lib/modules/snd-usbmidi-lib.ko
insmod /system/lib/modules/snd-usb-audio.ko
Click to expand...
Click to collapse
Thanks for the info. I've updated instructions.
tks teamm..
THANKS!!!
I'm building a tablet for my car right now, can't wait to try this!
If I already have timur's kernel loaded, do I need to reload?
Nice work! I got 2 questions:
Is it possible to add driver modules for the UTV007 Video Grabber that used to work with timur v3 kernel on android 5.1.1?
With android 6 and Nexus 7 2013 there was an issue with usb dacs that only had mono output instead of stereo. Is this issue corrected in Android 7?
Thanks for the info.
Thanks for this and nice work. I have a question though, and apologies if I am asking in wrong place... How do I configure Power Event Manager to put my tablet to deep sleep when incoming power is turned off? I tried to test it with a wall charger, but nothing happened when I disconnected it, and it did not turn off wifi / BT and activate flight mode. Does this only work when I have OTG devices plugged in?
---------- Post added at 06:49 PM ---------- Previous post was at 06:35 PM ----------
Two bugs -
- When I open Display in settings, Settings crashed
- When I launch File Manager, it closes with a prompt that it was unable to get relevant priviledges. It looks like it displays a dialogue to ask to allow SU (I assume), but this prompt closes immediately before I can tap yes.
carry a problem, when you press the sitema display generates app error and closes. when trying to open file manager does not start properly something as described by friend sopra.in beyond this my personal opinion this rom seems to be studied by using the kernel for mounted car devices but take out drivers for devices and say turn on this in insmod, for unhelpful user it turns out to be a problem and abandon rom
Great ROM, many thanks for this. I actually paid for Timurs kernel but the downloads are no longer available and it hasn't been updated in ages.
I cannot get usb audio to work. The device is recognised in powerevent manager and the devices LED lights up but audio plays through the tablets internal speakers.
I created a userinit.sh file in data/local/ and added:
#!/system/bin/sh
insmod /system/lib/modules/ssnd-hwdep.ko
insmod /system/lib/modules/snd-usbmidi-lib.ko
insmod /system/lib/modules/snd-usb-audio.ko
After restarting the device my issues are as described above. Can anyone point to where I'm going wrong or help troubleshoot? Thanks.
EDIT: I changed the line "insmod /system/lib/modules/ssnd-hwdep.ko" to "insmod /system/lib/modules/snd-hwdep.ko" (Removed an extra 's') and I am able to execute the script manually after boot and the audio works fine
---------- Post added at 07:12 PM ---------- Previous post was at 06:25 PM ----------
With android 6 and Nexus 7 2013 there was an issue with usb dacs that only had mono output instead of stereo. Is this issue corrected in Android 7?
Click to expand...
Click to collapse
I'm using a Behringer 202 DAC and the mono issue does not seem to be present in this version. Full stereo here!
Another bug I've noticed that hasn't been mentioned. About 50% of the time when I reboot the tablet, it gets stuck on the Google logo. I have to hold power off + volume up to force reboot, where it normally boots fine.
I have had to abandon this ROM as it is currently too unstable for daily use in the car. I'm sorry but I can't produce any logs as I've reverted to 5.1.1 as I have a fixed installation which is a major pain to remove any time I encounter a problem.
(I'm not even sure if this ROM is in development or has been abandoned)
Issues I've faced:
Screen sometimes won't turn on. Touches are registered but the only way to turn the screen on is a hard reset (In a fixed install this is a big problem). This appears to happen randomly.
USB audio produces a lot of crackling. After researching, this appears to be a nougat issue but in a car install this isn't acceptable.
uberNoobZA said:
I tried to test it with a wall charger, but nothing happened when I disconnected it, and it did not turn off wifi / BT and activate flight mode. Does this only work when I have OTG devices plugged in?
Two bugs -
- When I open Display in settings, Settings crashed
- When I launch File Manager, it closes with a prompt that it was unable to get relevant priviledges. It looks like it displays a dialogue to ask to allow SU (I assume), but this prompt closes immediately before I can tap yes.
Click to expand...
Click to collapse
It only works with OTG in FI-Mode.
Have you tried adding SU permission in Magisk ?
tenerif88 said:
carry a problem, when you press the sitema display generates app error and closes. when trying to open file manager does not start properly something as described by friend sopra.in beyond this my personal opinion this rom seems to be studied by using the kernel for mounted car devices but take out drivers for devices and say turn on this in insmod, for unhelpful user it turns out to be a problem and abandon rom
Click to expand...
Click to collapse
The modules were made loadable (removed from kernel and added using insmod to fix problem with installations that are using Bluetooth audio and easycap (that was setting volume to max when USB audio driver is present).
HellmetButter said:
EDIT: I changed the line "insmod /system/lib/modules/ssnd-hwdep.ko" to "insmod /system/lib/modules/snd-hwdep.ko" (Removed an extra 's') and I am able to execute the script manually after boot and the audio works fine
Another bug I've noticed that hasn't been mentioned. About 50% of the time when I reboot the tablet, it gets stuck on the Google logo. I have to hold power off + volume up to force reboot, where it normally boots fine.
Click to expand...
Click to collapse
thanks, I've removed typo
What build are you using I've never experienced that with flo build, I don't have access to test deb. Are there any steps to reproduce, will you be able to get output of `cat /proc/last_kmsg ` after restarting stuck tablet or get ADB log when boot gets stuck.
deb gets stuck at Google boot screen
i feel like such a noob. i have flashed many rom before, but i cant get the deb rom to work.
using twrp 3.1.1
wiped everything cache, data, system, internal storage, etc
installed deb rom
installed gapps
reboot
it just gets stuck on the Google boot screen with the unlock.
manually powered off and power on
manually reboot in bootloader
just gets stuck in Google boot screen
any help would be appreciated!
What build are you using I've never experienced that with flo build, I don't have access to test deb. Are there any steps to reproduce, will you be able to get output of `cat /proc/last_kmsg ` after restarting stuck tablet or get ADB log when boot gets stuck.
Click to expand...
Click to collapse
I'm using the flo build. I can't post any logs at the moment as I've reverted back to lollipop, if I have time later I'll make a backup and try again. It happened at pretty much any normal reboot. although it always booted from system to recovery and from recovery to system without problems.
Is everyone else getting crackling when using USB audio?
chuckcheeze said:
i feel like such a noob. i have flashed many rom before, but i cant get the deb rom to work.
using twrp 3.1.1
wiped everything cache, data, system, internal storage, etc
installed deb rom
installed gapps
reboot
it just gets stuck on the Google boot screen with the unlock.
manually powered off and power on
manually reboot in bootloader
just gets stuck in Google boot screen
any help would be appreciated!
Click to expand...
Click to collapse
It is possible that deb build is not working as I don't have deb device to test I'll take a look on weekend to see we this build is different.
i greatly appreciate it. i am currently running stock 6.0.1 with timur and i want a custom rom!
let me know if i can help by providing logs thru twrp :good:
i even tried tapping the back (seen on youtube) to reset the sensor (theory) :silly:
First off, thanks for the great work guys/gals.
I tested the rom while driving from Boston to Miami over the last few days and can confirm the same usb audo crackling and hanging upon reboot. I had also purchased timur's kernal during his initial development and ended up going to EXKM and tasker once newer versions of android were available. I had the car in storage over the past two years, so I'm just now getting back into it. I initially ran RR but just couldn't get the power situation working (although usb dac audio worked fine w/7.1.2).
Anyway, I had added the userinit amendments and usb audio started working with this rom after reboot, but unfortunately I had the crackling audio as well. I confirmed it was an issue with this rom/kernal based on the fact that I could plug in my nexus 6 to the same fixed setup and had no crackling. After some reading this evening (this is after tearing apart my wiring thinking I had a ground issue), now I'm wondering if it's a sampling issue. I've changed audiopolicy.conf from "dynamic" to 41000 and will test tomorrow morning and report back. This usb dac crackling is a popular topic if you google it. I haven't used logcat in a couple years, if I can remember how to use it, I'll post the log.
Also of note, I get the same "google" boot hang that the previous user mentioned which is only resolved by holding the power button until reboot occurs. I still got this after doing a factory reset as well as formatting user data. I don't tihnk this will be an issue since I won't be rebooting once I get functional usb audio. I wish I had more time to actually learn how to edit a kernel... Maybe after residency...
chuckcheeze said:
i greatly appreciate it. i am currently running stock 6.0.1 with timur and i want a custom rom!
let me know if i can help by providing logs thru twrp :good:
i even tried tapping the back (seen on youtube) to reset the sensor (theory) :silly:
Click to expand...
Click to collapse
Also using Timur's and stock MOB30X without any kind of trouble. But 6.0.1 is becoming old and security patches are outdated, so thats why i would like to have a much more recents ROM working with Timurs
Installed your ROM yesterday, and i had my first travel today using it (home --work...work---home) so far no trouble with it, except "settings/display" is force closing, i'll post some logs tonight. Probably some issues with Automate and Carlauncher. Othetwise..such a great work you did porting timurs on Nougat.
Here's the log:
roidRuntime(24569): at android.os.Looper.loop(Looper.java:154)
09-18 23:49:38.502 E/AndroidRuntime(24569): at android.app.ActivityThread.main(ActivityThread.java:6236)
09-18 23:49:38.502 E/AndroidRuntime(24569): at java.lang.reflect.Method.invoke(Native Method)
09-18 23:49:38.502 E/AndroidRuntime(24569): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:891)
09-18 23:49:38.502 E/AndroidRuntime(24569): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:781)
09-18 23:49:38.502 E/AndroidRuntime(24569): Caused by: java.lang.ArrayIndexOutOfBoundsException: length=7; index=7
09-18 23:49:38.502 E/AndroidRuntime(24569): at com.android.settings.DisplaySettings.updateTimeoutPreferenceDescription(DisplaySettings.java:329)
09-18 23:49:38.502 E/AndroidRuntime(24569): at com.android.settings.DisplaySettings.onResume(DisplaySettings.java:353)
09-18 23:49:38.502 E/AndroidRuntime(24569): at android.app.Fragment.performResume(Fragment.java:2399)
09-18 23:49:38.502 E/AndroidRuntime(24569): at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1032)
09-18 23:49:38.502 E/AndroidRuntime(24569): at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1171)
09-18 23:49:38.502 E/AndroidRuntime(24569): at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1153)
09-18 23:49:38.502 E/AndroidRuntime(24569): at android.app.FragmentManagerImpl.dispatchResume(FragmentManager.java:2049)
09-18 23:49:38.502 E/AndroidRuntime(24569): at android.app.FragmentController.dispatchResume(FragmentController.java:198)
09-18 23:49:38.502 E/AndroidRuntime(24569): at android.app.Activity.performResume(Activity.java:6809)
09-18 23:49:38.502 E/AndroidRuntime(24569): at android.app.ActivityThread.performResumeActivity(ActivityThread.java:3446)
09-18 23:49:38.502 E/AndroidRuntime(24569): ... 10 more
09-18 23:49:38.506 W/ActivityManager(592): Force finishing activity com.android.settings/.Settings$DisplaySettingsActivity
09-18 23:49:38.516 W/ActivityManager(592): Force finishing activity com.android.settings/.Settings
09-18 23:49:38.523 I/WindowManager(592): setFocusedApp token: Token{13b447 ActivityRecord{409f386 u0 com.autolauncher.motorcar/.Speed_Activity t68}} requestedOrientation: 0
09-18 23:49:38.524 W/ContextImpl(592): Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:877 com.android.server.am.AppErrors.crashApplicationInner:375 com.android.server.am.AppErrors.crashApplication:309 com.android.server.am.ActivityManagerService.handleApplicationCrashInner:13757 com.android.server.am.ActivityManagerService.handleApplicationCrash:13739
09-18 23:49:38.548 D/Index (24569): Indexing locale 'fr_FR' took 74 millis
09-18 23:49:38.578 I/OpenGLRenderer(592): Initialized EGL, version 1.4
09-18 23:49:38.578 D/OpenGLRenderer(592): Swap behavior 1
09-18 23:49:38.720 D/Index (24569): Indexing locale 'fr_FR' took 19 millis
09-18 23:49:38.866 W/TileUtils(24569): Found com.android.settings.Settings$PaymentSettingsActivity for intent Intent { act=com.android.settings.action.SETTINGS pkg=com.android.settings } missing metadata com.android.settings.category
09-18 23:49:38.869 W/TileUtils(24569): Found org.cyanogenmod.cmparts.input.ButtonSettings for intent Intent { act=com.android.settings.action.EXTRA_SETTINGS } missing metadata com.android.settings.category
09-18 23:49:38.869 W/TileUtils(24569): Found org.cyanogenmod.cmparts.statusbar.StatusBarSettings for intent Intent { act=com.android.settings.action.EXTRA_SETTINGS } missing metadata com.android.settings.category
09-18 23:49:38.870 W/TileUtils(24569): Found com.android.systemui.tuner.TunerActivity for intent Intent { act=com.android.settings.action.EXTRA_SETTINGS } missing metadata
09-18 23:49:39.018 W/ActivityManager(592): Activity pause timeout for ActivityRecord{9ef998f u0 com.android.settings/.Settings$DisplaySettingsActivity t87 f}
09-18 23:49:39.049 I/LOG_TAG (1377): Сработал onStart
09-18 23:49:39.049 D/YWeatherGetter4a(1377): query yahoo weather by gps
09-18 23:49:39.051 I/LOG_TAG (1377): Сработал onResume
09-18 23:49:39.052 I/WindowManager(592): setAppOrientation token: Token{13b447 ActivityRecord{409f386 u0 com.autolauncher.motorcar/.Speed_Activity t68}} requestedOrientation: 0
09-18 23:49:39.503 D/AudioService(592): Stream muted, skip playback
09-18 23:49:39.503 W/ActivityManager(592): Force finishing activity com.android.settings/.Settings$DisplaySettingsActivity
09-18 23:49:39.503 W/ActivityManager(592): Force finishing activity com.android.settings/.Settings
09-18 23:49:39.509 I/ActivityManager(592): Killing 24569:com.android.settings/1000 (adj 900): crash
09-18 23:49:39.513 D/ActivityManager(592): cleanUpApplicationRecord -- 24569
09-18 23:49:39.549 D/GraphicsStats(592): Buffer count: 12
09-18 23:49:39.631 W/AppOps (592): Finishing op nesting under-run: uid 1000 pkg android code 24 time=0 duration=0 nesting=0
09-18 23:49:41.072 D/AudioService(592): Stream muted, skip playback
09-18 23:49:41.177 I/ActivityManager(592): START u0 {flg=0x10804000 cmp=com.android.systemui/.recents.RecentsActivity} from uid 10038 on display 0
09-18 23:49:41.192 I/LOG_TAG (1377): Сработал onPause
09-18 23:49:41.226 I/LOG_TAG (1377): Сработал onStop
09-18 23:49:42.438 D/AudioService(592): Stream muted, skip playback
09-18 23:49:42.464 E/ActivityManager(592): applyOptionsLocked: Unknown animationType=0
09-18 23:49:42.587 V/PhoneStatusBar(714): setLightsOn(true)
09-18 23:49:42.644 V/PhoneStatusBar(714): setLightsOn(true)
09-18 23:49:42.725 V/PhoneStatusBar(714): setLightsOn(true)
09-18 23:49:42.875 V/PhoneStatusBar(714): setLightsOn(true)
09-18 23:49:43.471 I/LOG_TAG (1377): run start
09-18 23:49:43.480 I/LOG_TAG (1377): СbackProbeg 58145.957 MyApplication.ProbegPoezd 0.0 = 58145.957
09-18 23:49:43.481 I/LOG_TAG (1377): backDvizen 26148 MyApplication.dvizenPoezd 42 = 26190
09-18 23:49:43.563 I/LOG_TAG (1377): run finish
09-18 23:49:46.207 D/AudioService(592): Stream muted, skip playback
09-18 23:49:46.373 I/art (20690): Background sticky concurrent mark sweep GC freed 10819(425KB) AllocSpace objects, 0(0B) LOS objects, 0% free, 15MB/15MB, paused 457us total 102.142ms
09-18 23:49:47.981 D/AudioService(592): Stream muted, skip playback
09-18 23:49:48.600 I/Icing (1467): IndexChimeraService.getServiceInterface callingPackage=com.android.chrome componentName=null serviceId=36
09-18 23:49:48.783 I/Icing (1467): App usage reports: 4
09-18 23:49:48.783 I/Icing (1467): Usage reports 4 indexed 0 rejected 0 imm upload false
09-18 23:49:49.034 D/AudioService(592): Stream muted, skip playback
09-18 23:49:49.196 V/PhoneStatusBar(714): setLightsOn(true)
09-18 23:49:49.198 D/AudioService(592): Stream muted, skip playback
09-18 23:49:49.209 V/PhoneStatusBar(714): setLightsOn(true)
09-18 23:49:49.223 V/PhoneStatusBar(714): setLightsOn(true)
09-18 23:49:49.249 V/PhoneStatusBar(714): setLightsOn(true)
09-18 23:49:49.252 V/PhoneStatusBar(714): setLightsOn(true)
09-18 23:49:49.258 V/PhoneStatusBar(714): setLightsOn(true)
09-18 23:49:49.373 V/PhoneStatusBar(714): setLightsOn(true)
09-18 23:49:49.750 I/DeviceScanner(1467): [MDNS] Received response from "HT-XT3" (bbc7b31dcb23733e97d2242075cdd5c6) with result "0 No change"
09-18 23:49:49.750 I/DeviceScanner(1467): [MDNS] notifyDeviceOnline: "HT-XT3" (bbc7b31dcb23733e97d2242075cdd5c6), criteria , statusText ''
09-18 23:49:49.853 I/Icing (1467): Indexing 17A36E7C253B00A930025F14F201E93143B279CA from com.android.chrome
09-18 23:49:49.986 I/Icing (1467): Indexing done 17A36E7C253B00A930025F14F201E93143B279CA
09-18 23:49:50.942 I/Icing (1467): IndexChimeraService.getServiceInterface callingPackage=com.android.chrome componentName=null serviceId=36
09-18 23:49:51.061 I/Icing (1467): Usage reports 0 indexed 0 rejected 0 imm upload false
09-18 23:49:51.800 V/PhoneStatusBar(714): setLightsOn(true)
09-18 23:49:51.803 D/AudioService(592): Stream muted, skip playback
09-18 23:49:51.812 V/PhoneStatusBar(714): setLightsOn(true)
09-18 23:49:51.822 V/PhoneStatusBar(714): setLightsOn(true)
09-18 23:49:51.838 W/InputMethodService(701): Window size has been changed. This may cause jankiness of resizing window: -1 -> -2
09-18 23:49:51.841 V/PhoneStatusBar(714): setLightsOn(true)
09-18 23:49:51.846 I/LatinIME(701): Starting input. Cursor position = 0,19
09-18 23:49:51.865 V/PhoneStatusBar(714): setLightsOn(true)
09-18 23:49:51.867 V/PhoneStatusBar(714): setLightsOn(true)
09-18 23:49:51.873 V/PhoneStatusBar(714): setLightsOn(true)
09-18 23:49:51.887 V/PhoneStatusBar(714): setLightsOn(true)
09-18 23:49:51.979 V/PhoneStatusBar(714): setLightsOn(true)
09-18 23:49:51.984 V/PhoneStatusBar(714): setLightsOn(true)
09-18 23:49:52.007 V/PhoneStatusBar(714): setLightsOn(true)
09-18 23:49:52.085 W/InputAttributes(701): Unexpected input class: inputType=0x000000b0 imeOptions=0x00000006
09-18 23:49:52.144 V/PhoneStatusBar(714): setLightsOn(true)
09-18 23:49:52.239 V/PhoneStatusBar(714): setLightsOn(true)
09-18 23:49:52.296 I/art (701): Background sticky concurrent mark sweep GC freed 2261(78KB) AllocSpace objects, 0(0B) LOS objects, 1% free, 12MB/12MB, paused 32.958ms total 41.717ms
09-18 23:49:52.308 V/PhoneStatusBar(714): setLightsOn(true)
09-18 23:49:52.310 V/PhoneStatusBar(714): setLightsOn(true)
09-18 23:49:52.318 V/PhoneStatusBar(714): setLightsOn(true)
09-18 23:49:52.435 V/PhoneStatusBar(714): setLightsOn(true)
09-18 23:49:52.534 V/PhoneStatusBar(714): setLightsOn(true)
09-18 23:49:53.143 D/AudioService(592): Stream muted, skip playback
Same issue with Settings/Display crashing after clean install. Hope we'll get answer from developper soon

Some Problems with OPO6 and Pie

Hi,
I updated recently to 9.02.
Unfortunately i have some problems wie Pie versions (before i already tested 9.0, but went back to 8.x due to the same probs)
I used Nova Launcher.
I use the "Swipe up" gesture to lock my phone.
The Screen lock method was set to "root". (with "device admin", unlocking with Fingerprint is not possible)
I also use Alarmdroid.
When i set an alarm, and lock my OPO6 with a swipe up, the alarm is never activated. The phone was nearly unusable, like a program took 100%CPU. (Probably Nova and/or Alarmdroid).
This combination worked on every previous Android versions.
Second Problem is that Android Auto always stops with a message:
"Something went wrong - Google play services doesn't seem to be working right now".
Third Problem: My Luxspeed application does not start anymore (worked fine with 8.x versions)
Code:
D/ActivityManager( 910): # addPackageDependency # packageName=com.google.android.gms -> proc: ProcessRecord{f932016 11289:com.pitschneider.luxspeed/u0a254}
D/ActivityManager( 910): # addPackageDependency # packageName=com.android.chrome -> proc: ProcessRecord{f932016 11289:com.pitschneider.luxspeed/u0a254}
D/ActivityManager( 910): # addPackageDependency # packageName=com.android.chrome -> proc: ProcessRecord{f932016 11289:com.pitschneider.luxspeed/u0a254}
I/ActivityManager( 910): Start proc 11359:com.android.chrome:sandboxed_process0/u0i6 for webview_service com.pitschneider.luxspeed/org.chromium.content.app.SandboxedProcessService0
I/ActivityManager( 910): Start proc 11379:com.android.chrome:sandboxed_process0/u0i7 for webview_service com.pitschneider.luxspeed/org.chromium.content.app.SandboxedProcessService0
E/OnePlusSmartBoostManager( 910): cmd: iop_start 11289 com.pitschneider.luxspeed /data/app/com.pitschneider.luxspeed-WQJscZhKGHMabc9A86_l8w== false length = 108
D/RestartProcessManager( 910): Duration is too short, ignore : 853 in com.pitschneider.luxspeed
E/AndroidRuntime(11289): Process: com.pitschneider.luxspeed, PID: 11289
I/WindowManager( 910): WIN DEATH: Window{a5dcfe3 u0 com.pitschneider.luxspeed/com.pitschneider.luxspeed.MainActivity}
I/ActivityManager( 910): Process com.pitschneider.luxspeed (pid 11289) has died: vis TOP
W/ActivityManager( 910): Force removing ActivityRecord{930dcfd u0 com.pitschneider.luxspeed/.MainActivity t701}: app died, no saved state
I/ActivityManager( 910): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.pitschneider.luxspeed/.MainActivity bnds=[642,167][845,495]} from uid 10060 pid 3614
E/OnePlusSmartBoostManager( 910): cmd: iop_start -1 com.pitschneider.luxspeed /data/app/com.pitschneider.luxspeed-WQJscZhKGHMabc9A86_l8w== false length = 105
D/RestartProcessManager( 910): updateSelf : com.pitschneider.luxspeed, size : 5
I/ActivityManager( 910): Start proc 11596:com.pitschneider.luxspeed/u0a254 for activity com.pitschneider.luxspeed/.MainActivity
D/OnePlusSmartBoostManager( 910): writeHotCount com.pitschneider.luxspeed, pid=11596
Anyone had similar errors/problems?
Thanks
Nop.
I use Nova (old beta version) but i nver use gestures...
Alarm works as suposed...
The only problem i have is double tap sometimes doesnt work, and rotation also freezes....
first things first. open up settings battery battery optimization 3 dot menu advanced optimization. turn off advanced optimization. then go back 1 menu, and set what ever app you need to not optimize so android (i mean oos) does not kill said app. give that a try.
Advanced Optimization was already disabled.
Also Alarmdroid was set to not optimized.
I changed the other problem apps to not optimize.

Categories

Resources