Titanium Backup kills background services, don't restart - OnePlus 3 Questions & Answers

Hi everyone,
I've had a problem with background apps (3G Watchdog, Tasker, Sleep As Android and whatnot) disappearing over night, so they didn't run anymore in the morning (no alarm in the morning, 3G Watchdog / Tasker persistent notification missing, and so on).
I'm running sultans July 16th build with Magisk 13.3.
Last night, I recorded logcat loglevel warning and higher, and I found these:
Code:
07-25 01:00:02.948 W/ActivityManager( 2709): Scheduling restart of crashed service net.rgruet.android.g3watchdogpro/.service.NetMonitorService in 1000ms
07-25 01:00:04.618 W/ActivityManager( 2709): Scheduling restart of crashed service com.joaomgcd.autonotification/.service.ServiceNotificationIntercept in 100
0ms
07-25 01:00:34.078 W/ActivityManager( 2709): Scheduling restart of crashed service org.dmfs.carddav.Sync/org.dmfs.android.contactutils.service.CopyWorkerServ
ice in 1000ms
07-25 01:00:36.274 W/ActivityManager( 2709): Scheduling restart of crashed service com.dvtonder.chronus/.extensions.calendar.CalendarExtension in 1000ms
07-25 01:00:36.992 W/ActivityManager( 2709): Scheduling restart of crashed service net.nurik.roman.dashclock/com.google.android.apps.dashclock.DashClockServi
ce in 1000ms
07-25 01:00:39.188 W/ActivityManager( 2709): Scheduling restart of crashed service org.mozilla.firefox/org.mozilla.gecko.media.MediaControlService in 1000ms
07-25 01:01:00.985 W/ActivityManager( 2709): Scheduling restart of crashed service com.gsamlabs.bbm.pro/com.gsamlabs.bbm.lib.NotifyingService in 1000ms
07-25 01:01:07.936 W/ActivityManager( 2709): Scheduling restart of crashed service com.fsck.k9/.service.PushService in 1000ms
07-25 01:01:15.244 W/ActivityManager( 2709): Scheduling restart of crashed service keepass2android.keepass2android/md5f0702f468598c68ce18586502249fb40.Ongoin
gNotificationsService in 1000ms
07-25 01:02:09.179 W/ActivityManager( 2709): Scheduling restart of crashed service ca.rebootsramblings.musicboss/.MainService in 1000ms
07-25 01:02:09.179 W/ActivityManager( 2709): Scheduling restart of crashed service ca.rebootsramblings.musicboss/.NLService in 11000ms
07-25 01:02:13.544 W/ActivityManager( 2709): Scheduling restart of crashed service de.blinkt.openvpn/.OpenVPNTileService in 1000ms
07-25 01:02:37.085 W/ActivityManager( 2709): Scheduling restart of crashed service com.runtastic.android.pro2/com.runtastic.android.service.MusicListenerServ
ice in 1000ms
07-25 01:02:54.159 W/ActivityManager( 2709): Scheduling restart of crashed service com.touchtype.swiftkey/com.touchtype.KeyboardService in 1000ms
07-25 01:03:01.907 W/ActivityManager( 2709): Scheduling restart of crashed service com.lsdroid.cerberuss/com.lsdroid.cerberus.BackgroundService in 1000ms
07-25 01:03:01.907 W/ActivityManager( 2709): Scheduling restart of crashed service com.lsdroid.cerberuss/com.lsdroid.cerberus.NotificationListener in 10999ms
07-25 01:03:03.627 W/ActivityManager( 2709): Scheduling restart of crashed service net.dinglisch.android.taskerm/.MyAccessibilityService in 1000ms
07-25 01:03:03.627 W/ActivityManager( 2709): Scheduling restart of crashed service net.dinglisch.android.taskerm/.NotificationListenerService in 11000ms
07-25 01:03:03.627 W/ActivityManager( 2709): Scheduling restart of crashed service net.dinglisch.android.taskerm/.MonitorService in 21000ms
07-25 01:03:04.548 W/ActivityManager( 2709): Scheduling restart of crashed service org.telegram.messenger/.NotificationsService in 1000ms
07-25 01:03:18.957 W/ActivityManager( 2709): Scheduling restart of crashed service com.whatsapp/.ExternalMediaManager in 1000ms
01:00 is when Titanium Backup is scheduled to backup changed data. It take 3-5 minutes for me. As you can see, those log entries are in nice alphabetical order, just like Titanium goes through them.
Now I wonder - why did that problem suddenly start last week? Is it Titanium's job to handle this properly, or is my system faulty, failing to restart those services like it normally should? Or could the issue still be something else?
Just looking for advice where to go next. I can't just have my phone restart after the backup procedure, because it's encrypted and therefore it wouldn't restart. Thanks for taking the time, everyone.

Do you have Titanium Backup Pro? The pro version should give you the option to back up apps without closing them.

Related

[Q] CM 6.1.1: Screen not turning on from blank while downloading stuff via wifi

I currently have a CM 6.1.1 stable installed on my Desire, which runs just fine.
But there has always been this annoying problem that, when the screen turns off while the market or sth is downloading stuff via wifi,
there is a high chance of screen not turning on again. The phone is still responsive, and I can log into it via usb cable.
Logcat shows the following piece of info each time I tap OJ/Power:
D/KeyguardViewMediator( 283): wakeWhenReadyLocked(26)
D/KeyguardViewMediator( 283): handleWakeWhenReady(26)
D/KeyguardViewMediator( 283): pokeWakelock(5000)
I/power ( 283): *** set_screen_state 1
D/AK8973 ( 227): Compass Start
D/WifiService( 283): ACTION_SCREEN_ON
D/setcpu ( 631): Charging Profile 1113600, 1113600, ondemand
D/dalvikvm( 504): GC_EXPLICIT freed 220 objects / 10224 bytes in 37ms
D/dalvikvm( 631): GC_EXPLICIT freed 1633 objects / 77736 bytes in 33ms
I/power ( 283): *** set_screen_state 0
I/GPSButton( 283): Update State
D/WifiService( 283): ACTION_SCREEN_OFF
D/setcpu ( 631): Charging Profile 1113600, 1113600, ondemand
D/AK8973 ( 227): Compass CLOSE
D/dalvikvm( 504): GC_EXPLICIT freed 47 objects / 2472 bytes in 25ms
And dmesg shows nothing.
When I type 'adb shell reboot', nothing happens and the reboot command does not return.
This happens before setcpu is installed, so I think it is not to blame.
I use Darktremor a2sd script to install app in SD card, but this happens when SD card is removed, so it is not to blame, either.
Any suggestions or moves from you guys that I can try on my phone? The situation occurs quite frequently.
Thanks in advance.
P.S. I believe this to be a software issue because 3 days ago I was running another ROM and did not have this problem.
I checked Logcat of normal situation, which reads:
D/KeyguardViewMediator( 283): handleWakeWhenReady(0)
D/KeyguardViewMediator( 283): pokeWakelock(5000)
I/power ( 283): *** set_screen_state 1
D/SurfaceFlinger( 283): Screen about to return, flinger = 0x12d0e8
D/AK8973 ( 227): Compass Start
D/WifiService( 283): ACTION_SCREEN_ON
D/setcpu ( 634): Charging Profile 1113600, 1113600, ondemand
D/dalvikvm( 504): GC_EXPLICIT freed 178 objects / 7760 bytes in 85ms
D/dalvikvm( 504): GC_EXPLICIT freed 212 objects / 9680 bytes in 42ms
Comparing to this, one line was missing from the problematic log, the SurfaceFlinger:
'D/SurfaceFlinger( 283): Screen about to return, flinger = 0x12d0e8'
which means the surface flinger may have died when the screen no longer wakes up, I suppose?

[Q] Problem with Cyanogen 7.1.5 Cyanogen Setting - Lockscreen - Widget Options

Hi,
i've run nightly cyanogen mod 7 from 29.11.2011. But in this and previous version (nightly 27.11.2011) appeared a bug, that i can't get into Widget settings in Cyanogen Settings - Lockscreen cause error appeared that something is wrong in proces com.cyanogenmod.cmparts. Here is log
10-30 20:54:18.085 I/ActivityManager(2143): Displayed com.cyanogenmod.cmparts/.activities.MainActivity: +393ms
10-30 20:54:19.069 I/ActivityManager(2143): Starting: Intent { act=android.intent.action.MAIN cmp=com.cyanogenmod.cmparts/.activities.LockscreenActivity } from pid 5945
10-30 20:54:19.405 I/ActivityManager(2143): Displayed com.cyanogenmod.cmparts/.activities.LockscreenActivity: +326ms
10-30 20:54:20.553 I/ActivityManager(2143): Starting: Intent { act=android.intent.action.MAIN cmp=com.cyanogenmod.cmparts/.activities.LockscreenWidgetsActivity } from pid 5945
10-30 20:54:20.592 W/Resources(5945): Converting to string: TypedValue{t=0x10/d=0x0 a=-1}
10-30 20:54:20.608 D/AndroidRuntime(5945): Shutting down VM
10-30 20:54:20.608 W/dalvikvm(5945): threadid=1: thread exiting with uncaught exception (group=0x40015560)
10-30 20:54:20.608 E/AndroidRuntime(5945): FATAL EXCEPTION: main
10-30 20:54:20.608 E/AndroidRuntime(5945): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.cyanogenmod.cmparts/com.cyanogenmod.cmparts.activities.LockscreenWidgetsActivity}: java.lang.NullPointerException
10-30 20:54:20.608 E/AndroidRuntime(5945): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1768)
10-30 20:54:20.608 E/AndroidRuntime(5945): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:1784)
10-30 20:54:20.608 E/AndroidRuntime(5945): at android.app.ActivityThread.access$1500(ActivityThread.java:123)
10-30 20:54:20.608 E/AndroidRuntime(5945): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:939)
10-30 20:54:20.608 E/AndroidRuntime(5945): at android.os.Handler.dispatchMessage(Handler.java:99)
10-30 20:54:20.608 E/AndroidRuntime(5945): at android.os.Looper.loop(Looper.java:130)
10-30 20:54:20.608 E/AndroidRuntime(5945): at android.app.ActivityThread.main(ActivityThread.java:3835)
10-30 20:54:20.608 E/AndroidRuntime(5945): at java.lang.reflect.Method.invokeNative(Native Method)
10-30 20:54:20.608 E/AndroidRuntime(5945): at java.lang.reflect.Method.invoke(Method.java:507)
10-30 20:54:20.608 E/AndroidRuntime(5945): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:858)
10-30 20:54:20.608 E/AndroidRuntime(5945): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
10-30 20:54:20.608 E/AndroidRuntime(5945): at dalvik.system.NativeStart.main(Native Method)
10-30 20:54:20.608 E/AndroidRuntime(5945): Caused by: java.lang.NullPointerException
10-30 20:54:20.608 E/AndroidRuntime(5945): at android.preference.MultiSelectListPreference.setValue(MultiSelectListPreference.java:65)
10-30 20:54:20.608 E/AndroidRuntime(5945): at com.cyanogenmod.cmparts.activities.LockscreenWidgetsActivity.onCreate(LockscreenWidgetsActivity.java:120)
10-30 20:54:20.608 E/AndroidRuntime(5945): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1047)
10-30 20:54:20.608 E/AndroidRuntime(5945): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1722)
10-30 20:54:20.608 E/AndroidRuntime(5945): ... 11 more
10-30 20:54:20.616 W/ActivityManager(2143): Force finishing activity com.cyanogenmod.cmparts/.activities.LockscreenWidgetsActivity
10-30 20:54:20.616 W/ActivityManager(2143): Force finishing activity com.cyanogenmod.cmparts/.activities.LockscreenActivity
10-30 20:54:21.124 W/ActivityManager(2143): Activity pause timeout for HistoryRecord{40871398 com.cyanogenmod.cmparts/.activities.LockscreenWidgetsActivity}
10-30 20:54:23.897 I/Process (5945): Sending signal. PID: 5945 SIG: 9
10-30 20:54:23.936 I/ActivityManager(2143): Process com.cyanogenmod.cmparts (pid 5945) has died.
10-30 20:54:23.944 E/InputDispatcher(2143): channel '40850d78 com.cyanogenmod.cmparts/com.cyanogenmod.cmparts.activities.MainActivity (server)' ~ Consumer closed input channel or an error occurred. events=0x8
10-30 20:54:23.944 E/InputDispatcher(2143): channel '40850d78 com.cyanogenmod.cmparts/com.cyanogenmod.cmparts.activities.MainActivity (server)' ~ Channel is unrecoverably broken and will be disposed!
10-30 20:54:23.952 I/WindowManager(2143): WIN DEATH: Window{40850d78 com.cyanogenmod.cmparts/com.cyanogenmod.cmparts.activities.MainActivity paused=false}
10-30 20:54:23.952 I/WindowManager(2143): WIN DEATH: Window{40864468 com.cyanogenmod.cmparts/com.cyanogenmod.cmparts.activities.LockscreenActivity paused=true}
10-30 20:54:24.030 W/InputManagerService(2143): Got RemoteException sending setActive(false) notification to pid 5945 uid 1000
10-30 20:54:26.569 I/ActivityManager(2143): Starting: Intent { act=android.intent.action.MAIN cmp=com.cyanogenmod.cmparts/.activities.MainActivity } from pid 2723
10-30 20:54:26.616 I/ActivityManager(2143): Start proc com.cyanogenmod.cmparts for activity com.cyanogenmod.cmparts/.activities.MainActivity: pid=6001 uid=1000 gids={3002, 3001, 3003, 1015}
10-30 20:54:26.811 D/szipinf (6001): Initializing inflate state
10-30 20:54:26.850 I/ActivityThread(6001): Pub com.cyanogenmod.cmparts.provider.Settings: com.cyanogenmod.cmparts.provider.SettingsProvider
10-30 20:54:27.046 I/ActivityManager(2143): Displayed com.cyanogenmod.cmparts/.activities.MainActivity: +441ms (total +6s485ms)
10-30 20:54:44.311 W/InputManagerService(2143): Starting input on non-focused client [email protected] (uid=1000 pid=6001)
Please, could someone say, if there is problem in cyanogen or it's caused by some application? I'm pretty sure that this error never appeared in nightly from 15.10.2011.
Thx in advance for any help.
The best option for you is started of instalation Froyo in all steps. Try.
boy, we have a time traveler here. you meant nightly 29.10.2011, right? so, it can be caused by a missing application. have you uninstalled any system apps? if not, try wiping cache first, if that doesnt help, just reinstall the nightly, see if that solves it. if that doesnt solve it either, my advice is to change nightly
sent from my cm7.1 defy...
Yes,Sure.I meant 29.10.2011.Any system app wasnt uninstalled.And the problem appeared in 27.10. nightly already.Ok, i will try wipe cache.Thanx.
Ok, so i tried wipe cache and guess what? nothing happens. Error still remains. Could someone tried this option on own device? Or it's only me who got this issue?

[Q] Camera Problem "Cannot connect to camera"

I found a new problem, which can potentially be really annoying since there's no other way to solve it apart from power cycle the phone.
I was messing around with the phone camera and switching between camcorder and camera mode, then the whole screen went black with the soft buttons showing in "dot" form.
I went back to the home screen and launched Camera app once again and still no activity. After a few seconds the OS informed that Camera app stopped working so I hit "Close". Then once I tried starting the Camera app again, there was this error "Cannot connect to camera"
Has anyone had this problem before?
cannot connect to camera
Just had this problem today. Was doing some video of setting up a new generator. That went ok. Got things set up and was going to take a pic. Screen was black. Tried opening a couple of times and got message "cannot connect to camera. I am doing a power cycle now.
Al
yeah I've had it before using cyanogen on my HTC sensation. had to power cycle. its annoying, happens often.
Sent from my Sensation using XDA App
It happened once on mine and I'm running standard 4.02. Never had it happen til yesterday.
Sent from my Galaxy Nexus using Tapatalk
This happened to me yesterday. Running stock 4.02. power cycle was the only way to get the camera working again.
Has happened to me on every rom i've tried, stock 4.0.1, arhd 2.1, cyanogenmod, villianrom etc. Very odd, happens when i try to enter the camera from the lock screen and rotate the device to landscape.
I'm also getting the same issue; has happened about 6 times in 4 days. Power cycle fixes it, which is very annoying. I'm not sure if the camera is active too long? It's usually running in Recent Apps.
I've been trying to exit out of the camera when I'm done as opposed to swapping apps or going to standby to see if that helps.
I'm having the same issue with my G-Nexus... 2nd time it's happened in 5 days.
Read in another blog that it could be caused by apps that access the camera that are not updated for ICS. NOt sure. But I uninstalled all such apps... we'll see.
I have this issue as well on my new GSM G-NEX that I have own for only three days now. Getting "cannot connect to camera" whenever I try to access camera, and power cycling doesn't help.
cannot connect to camera
after installation of cm7.1 i have the same problem with my zte blade. when i open the camera app, it says cannot connect to camera. idont no what to do. please help
I've had that problem a few times, usually from bad camera apps. Force closing the camera apps seem to fix the problem for me
Sent from my GT-P1000 using XDA App
I started having the same problem yesterday after taking a handful of pictures. Tried force stoping the Camera app, tried clearing its data/cache - no luck.
Here's a screenshot of the error:
h ttp://dev.npike.net/public/1325185257.png
I've read that if you have "force GDP rendering" on in the developer options it is screwing up the camera and camera apps
I don't have the option to force hardware acceleration enabled, but here is the output of logcat during the error:
Code:
I/ActivityManager( 185): START {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.google.android.camera/com.android.camera.Camera bnds=[40,785][200,985]} from pid 476
I/WindowManager( 185): createSurface Window{41f14030 Starting com.google.android.camera paused=false}: DRAW NOW PENDING
I/InputReader( 185): Reconfiguring input devices. changes=0x00000004
I/InputReader( 185): Device reconfigured: id=6, name='Melfas MMSxxx Touchscreen', surface size is now 720x1280, mode is 1
I/ActivityManager( 185): Config changed: {1.0 311mcc480mnc en_US layoutdir=0 sw360dp w598dp h360dp nrml land finger -keyb/v/h -nav/h s.29}
D/OpenGLRenderer( 268): Flushing caches (mode 0)
D/OpenGLRenderer( 268): Flushing caches (mode 0)
V/CameraHolder( 3737): open camera 0
W/CameraService( 118): CameraService::connect X (pid 3737) rejected (existing client).
E/CameraHolder( 3737): fail to connect Camera
E/CameraHolder( 3737): java.lang.RuntimeException: Fail to connect to camera service
E/CameraHolder( 3737): at android.hardware.Camera.native_setup(Native Method)
E/CameraHolder( 3737): at android.hardware.Camera.<init>(Camera.java:302)
E/CameraHolder( 3737): at android.hardware.Camera.open(Camera.java:264)
E/CameraHolder( 3737): at com.android.camera.CameraHolder.open(CameraHolder.java:131)
E/CameraHolder( 3737): at com.android.camera.Util.openCamera(Util.java:267)
E/CameraHolder( 3737): at com.android.camera.Camera$4.run(Camera.java:1008)
E/CameraHolder( 3737): at java.lang.Thread.run(Thread.java:856)
D/dalvikvm( 3737): GC_FOR_ALLOC freed 142K, 2% free 16021K/16263K, paused 22ms
I/dalvikvm-heap( 3737): Grow heap (frag case) to 16.346MB for 662416-byte allocation
D/dalvikvm( 3737): GC_CONCURRENT freed 1535K, 11% free 15132K/16967K, paused 2ms+4ms
D/OpenGLRenderer( 476): Flushing caches (mode 0)
D/dalvikvm( 3737): GC_FOR_ALLOC freed 18K, 9% free 15476K/16967K, paused 14ms
D/dalvikvm( 3737): GC_CONCURRENT freed 8K, 7% free 15928K/16967K, paused 1ms+2ms
I/WindowManager( 185): createSurface Window{41cf6e00 com.google.android.camera/com.android.camera.Camera paused=false}: DRAW NOW PENDING
I/WindowManager( 185): createSurface Window{41ee9870 com.google.android.camera/com.android.camera.Camera paused=false}: DRAW NOW PENDING
D/OpenGLRenderer( 476): Flushing caches (mode 1)
D/OpenGLRenderer( 476): Flushing caches (mode 0)
I/WindowManager( 185): createSurface Window{42067810 SurfaceView paused=false}: DRAW NOW PENDING
V/camera ( 3737): surfaceChanged. w=960. h=720
I/ActivityManager( 185): Displayed com.google.android.camera/com.android.camera.Camera: +822ms
It sounds like when the Camera app crashes it doesn't release its resources correctly - preventing anything else on the system from acquiring the camera.
Update: I have reported this issue to Google ht tp://code.google.com/p/android/issues/detail?id=23776
Strange.. I had this phone for quite a while and I suddenly started seeing this problem. That's after moving from Franco's kernel to popcorn. I'm wondering if its something to do with the kernel.
Any updates so far?
I've had this problem--but only when I accidentally started the Cartoon Camera app. Essentially, my GN hates it when two apps are using the same camera .
dmmarck said:
I've had this problem--but only when I accidentally started the Cartoon Camera app. Essentially, my GN hates it when two apps are using the same camera .
Click to expand...
Click to collapse
I've also discovered that the official battery might be the factor. I have two official samsung galaxy nexus batteries, I think one is causing the camera to crash everytime. Maybe the NFC inside the battery?
I've had the problem numerous times. Stock 4.0.2. Sometimes it's when I'm out and about. I was beginning to think it could be related to GPS. I've sent several email trouble reports to Google and received no feedback/response.
I have the same issue, it seems to occur when I use the camera for a while, and joum between home and camera a lot. I have a completely stock setup at the moment and it happens much less frequently now than it did when I was running MRC r10.
Well, from what I am experiencing, it's something about task switching (like what TheBishopOfSoho mentioned) and also probably something about screen rotation. I have very little apps which I allow to rotate (camera is one of them) so it has to vigorously switch rotation when I switch apps.
But overall, the prob always comes unexpectedly.. so it's hard to pinpoint it
EDIT: One thing that has remained constant throughout my experience is that all camera problems were present when I was using the Popcorn kernel. Franco's kernel hasn't experienced it yet.
Franco 18.2: OK
Popcorn 7.x : Cam problems started appearing (can't remember which version I used)
Franco: 18.5: OK
Franco: 18.6: OK so far...
So maybe it's something in the kernel.. the cpu governor, speed, etc..
Just trying to get as much info as possible so hopefully we can find out the root cause of this..

[Q] [ICS 4.0.3 CM9] PowerAmp crashing

Hi guys,
I have problems with PowerAmp in ICS, it is crashing quite often, sometimes it plays 2 hours just fine, and then I switch track or open library and it frozes and force quits.
Does anyone knows what is wrong? Author says that PowerAmp should be complatible with ICS.
There are logs:
D/ComprehensiveCountryDetector( 632): onServiceStateChanged
W/InputManagerService( 632): Window already focused, ignoring focus gain of: [email protected]
W/InputManagerService( 632): Starting input on non-focused client [email protected] (uid=1000 pid=632)
I/ActivityManager( 632): START {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.maxmpz.audioplayer/.StartupActivity} from pid 847
I/ActivityManager( 632): START {flg=0x24000000 cmp=com.maxmpz.audioplayer/.PlayerUIActivity} from pid 4595
V/PhoneStatusBar( 706): setLightsOn(true)
D/libEGL ( 4595): loaded /system/lib/egl/libGLES_android.so
D/libEGL ( 4595): loaded /system/lib/egl/libEGL_adreno200.so
D/libEGL ( 4595): loaded /system/lib/egl/libGLESv1_CM_adreno200.so
D/libEGL ( 4595): loaded /system/lib/egl/libGLESv2_adreno200.so
I/ActivityManager( 632): Displayed com.maxmpz.audioplayer/.PlayerUIActivity: +742ms (total +805ms)
W/InputManagerService( 632): Starting input on non-focused client [email protected] (uid=10021 pid=847)
D/SurfaceTexture( 79): SurfaceTexture::dequeue: Not allowed to dequeue more than a buffer SLEEPING
D/SurfaceTexture( 79): SurfaceTexture::dequeue: Not allowed to dequeue more than a buffer SLEEPING
D/SurfaceTexture( 79): SurfaceTexture::dequeue: Not allowed to dequeue more than a buffer SLEEPING
D/SurfaceTexture( 79): SurfaceTexture::dequeue: Not allowed to dequeue more than a buffer SLEEPING
D/SurfaceTexture( 79): SurfaceTexture::dequeue: Not allowed to dequeue more than a buffer RETRY mBufferCount:2 mServerBufferCount:2
D/SurfaceTexture( 79): SurfaceTexture::dequeuebuffer: MIN EXCEEDED mBuffer:3 bumped
D/SurfaceTexture( 79): SurfaceTexture::dequeuebuffer: MIN EXCEEDED mBuffer:4 bumped
D/SurfaceTexture( 79): SurfaceTexture::dequeuebuffer: MIN EXCEEDED mBuffer:5 bumped
D/ActivityThread( 4595): Loading provider com.maxmpz.audioplayer: com.maxmpz.audioplayer.unlock.DataProvider
D/SurfaceTexture( 79): SurfaceTexture::dequeuebuffer: MIN EXCEEDED mBuffer:6 bumped
D/SurfaceTexture( 79): SurfaceTexture::dequeuebuffer: MIN EXCEEDED mBuffer:7 bumped
I/ActivityManager( 632): START {dat=content://com.maxmpz.audioplayer.data/files/20 flg=0x20000000 cmp=com.maxmpz.audioplayer/.PlayListActivity} from pid 4595
V/PhoneStatusBar( 706): setLightsOn(true)
I/ActivityManager( 632): Displayed com.maxmpz.audioplayer/.PlayListActivity: +662ms
D/ActivityThread( 4595): Loading provider com.maxmpz.audioplayer: com.maxmpz.audioplayer.unlock.DataProvider
D/SettingsProvider( 632): external modification to /data/data/com.android.providers.settings/databases/settings.db; event=2
D/SettingsProvider( 632): updating our caches for /data/data/com.android.providers.settings/databases/settings.db
D/SettingsProvider( 632): cache for settings table 'secure' rows=47; fullycached=true
D/SettingsProvider( 632): cache for settings table 'system' rows=60; fullycached=true
I/ActivityManager( 632): START {flg=0x24000000 cmp=com.maxmpz.audioplayer/.PlayerUIActivity} from pid 4595
D/SurfaceTexture( 79): SurfaceTexture::dequeue: Not allowed to dequeue more than a buffer SLEEPING
D/SurfaceTexture( 79): SurfaceTexture::dequeue: Not allowed to dequeue more than a buffer SLEEPING
D/SurfaceTexture( 79): SurfaceTexture::dequeue: Not allowed to dequeue more than a buffer SLEEPING
D/SurfaceTexture( 79): SurfaceTexture::dequeue: Not allowed to dequeue more than a buffer SLEEPING
D/SurfaceTexture( 79): SurfaceTexture::dequeue: Not allowed to dequeue more than a buffer RETRY mBufferCount:2 mServerBufferCount:2
I/InputDispatcher( 632): Application is not responding: AppWindowToken{41919ba8 token=Token{41838c68 ActivityRecord{4183d440 com.maxmpz.audioplayer/.PlayerUIActivity}}}. 5001.2ms since event, 5000.9ms since wait started
I/WindowManager( 632): Input event dispatching timed out sending to application AppWindowToken{41919ba8 token=Token{41838c68 ActivityRecord{4183d440 com.maxmpz.audioplayer/.PlayerUIActivity}}}
I/Process ( 632): Sending signal. PID: 4595 SIG: 3
I/dalvikvm( 4595): threadid=3: reacting to signal 3
I/dalvikvm( 4595): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 632): Sending signal. PID: 632 SIG: 3
I/dalvikvm( 632): threadid=3: reacting to signal 3
I/dalvikvm( 632): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 632): Sending signal. PID: 706 SIG: 3
I/dalvikvm( 706): threadid=3: reacting to signal 3
I/dalvikvm( 706): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 632): Sending signal. PID: 832 SIG: 3
I/dalvikvm( 832): threadid=3: reacting to signal 3
I/dalvikvm( 832): Wrote stack traces to '/data/anr/traces.txt'
D/dalvikvm( 632): GC_EXPLICIT freed 1145K, 15% free 17014K/19847K, paused 3ms+8ms
E/ActivityManager( 632): ANR in com.maxmpz.audioplayer (com.maxmpz.audioplayer/.PlayerUIActivity)
E/ActivityManager( 632): Reason: keyDispatchingTimedOut
E/ActivityManager( 632): Load: 2.4 / 2.17 / 2.13
E/ActivityManager( 632): CPU usage from 11063ms to 81ms ago with 99% awake:
E/ActivityManager( 632): 2.2% 632/system_server: 0.7% user + 1.5% kernel / faults: 84 minor
E/ActivityManager( 632): 2.2% 4595/com.maxmpz.audioplayer: 1.7% user + 0.5% kernel / faults: 213 minor 2 major
E/ActivityManager( 632): 1.8% 79/surfaceflinger: 0.9% user + 0.9% kernel / faults: 5341 minor
E/ActivityManager( 632): 0.2% 706/com.android.systemui: 0.1% user + 0% kernel / faults: 1 minor
E/ActivityManager( 632): 0.2% 5020/kworker/0:2: 0% user + 0.2% kernel
E/ActivityManager( 632): 0.1% 4623/com.quoord.tapatalkxdapre.activity: 0% user + 0% kernel / faults: 1 minor
E/ActivityManager( 632): 0% 6/rcu_kthread: 0% user + 0% kernel
E/ActivityManager( 632): 0% 847/com.teslacoilsw.launcher: 0% user + 0% kernel / faults: 58 minor
E/ActivityManager( 632): 0% 1589/com.touchtype.swiftkey: 0% user + 0% kernel / faults: 2 minor
E/ActivityManager( 632): 0% 3037/com.twitter.android: 0% user + 0% kernel
E/ActivityManager( 632): 0% 3638/wpa_supplicant: 0% user + 0% kernel
E/ActivityManager( 632): 0% 5026/logcat: 0% user + 0% kernel
E/ActivityManager( 632): 10% TOTAL: 3.6% user + 3.2% kernel + 3.8% iowait
E/ActivityManager( 632): CPU usage from 1215ms to 1821ms later with 99% awake:
E/ActivityManager( 632): 20% 632/system_server: 4.7% user + 15% kernel / faults: 1 minor
E/ActivityManager( 632): 20% 668/InputDispatcher: 1.5% user + 19% kernel
E/ActivityManager( 632): 18% TOTAL: 3.2% user + 14% kernel
W/ActivityManager( 632): Force finishing activity com.maxmpz.audioplayer/.PlayerUIActivity
I/ActivityManager( 632): Killing ProcessRecord{41a8bfe0 4595:com.maxmpz.audioplayer/10071}: user's request
I/ActivityManager( 632): Process com.maxmpz.audioplayer (pid 4595) has died.
I/WindowManager( 632): WIN DEATH: Window{416d18f8 com.maxmpz.audioplayer/com.maxmpz.audioplayer.PlayerUIActivity paused=true}
W/WindowManager( 632): Force-removing child win Window{416da920 SurfaceView paused=false} from container Window{416d18f8 com.maxmpz.audioplayer/com.maxmpz.audioplayer.PlayerUIActivity paused=true}
W/ActivityManager( 632): Service crashed 2 times, stopping: ServiceRecord{41790680 com.maxmpz.audioplayer/.player.PlayerService}
W/ActivityManager( 632): Service crashed 2 times, stopping: ServiceRecord{4178a7a8 com.maxmpz.audioplayer/.widgetpackcommon.WidgetUpdaterService}
E/SurfaceTexture( 79): [SurfaceView] dequeueBuffer: SurfaceTexture has been abandoned!
W/InputDispatcher( 632): channel '41769160 com.maxmpz.audioplayer/com.maxmpz.audioplayer.PlayListActivity (server)' ~ Consumer closed input channel or an error occurred. events=0x8
E/InputDispatcher( 632): channel '41769160 com.maxmpz.audioplayer/com.maxmpz.audioplayer.PlayListActivity (server)' ~ Channel is unrecoverably broken and will be disposed!
W/WindowManager( 632): Failed looking up window
W/WindowManager( 632): java.lang.IllegalArgumentException: Requested window [email protected] does not exist
W/WindowManager( 632): at com.android.server.wm.WindowManagerService.windowForClientLocked(WindowManagerService.java:7156)
W/WindowManager( 632): at com.android.server.wm.WindowManagerService.windowForClientLocked(WindowManagerService.java:7147)
W/WindowManager( 632): at com.android.server.wm.WindowState$DeathRecipient.binderDied(WindowState.java:1529)
W/WindowManager( 632): at android.os.BinderProxy.sendDeathNotice(Binder.java:417)
W/WindowManager( 632): at dalvik.system.NativeStart.run(Native Method)
W/InputDispatcher( 632): Attempted to unregister already unregistered input channel '41769160 com.maxmpz.audioplayer/com.maxmpz.audioplayer.PlayListActivity (server)'
I/WindowManager( 632): WIN DEATH: null
I/WindowManager( 632): WIN DEATH: Window{41769160 com.maxmpz.audioplayer/com.maxmpz.audioplayer.PlayListActivity paused=false}
I/WindowManager( 632): WINDOW DIED Window{41769160 com.maxmpz.audioplayer/com.maxmpz.audioplayer.PlayListActivity paused=false}
W/ActivityManager( 632): Launch timeout has expired, giving up wake lock!
W/InputManagerService( 632): Got RemoteException sending setActive(false) notification to pid 4595 uid 10071
Click to expand...
Click to collapse
Thx for any help.

AOSP build failing camera, bluetooth

Hi there,
for some days I try to build a clean AOSP build for my Galaxy Nexus GSM Edition.
I read this guide and the whole topic but I still fail, asking on the android devel list didn't really help so seems like you guys are my last chance, so here in short what I have done:
I set up an Ubuntu 10.04 LTS like you advised me to.
Chose repo with:
repo init -u https://android.googlesource.com/platform/manifest -b
android-4.0.3_r1
synced it.
Downloaded the 2 sh files for building properitary modules via
http://code.google.com/intl/de/android/nexus/drivers.html#maguro
Started both sh files to extract? modules.
Started building with:
source build/envsetup.sh
lunch -> 8 for maguro
make clobber
make -j2
make -j2 otapackage
First installationtry was wiping the device and applying the
update.zip file.
This resulted in a non working bluetooth and camera.
So I thought about applying img. files via fastboot and I packed them
alltogether to an .zip file, like the factory images, applied the
android-info.txt and did a
fastboot -w update update.zip.
Got the bootloop, rebooted after some time, android starts up but adb
lolcat gives me those:
Code:
I/bluedroid( 208): bt_enable: ret: -1, errno: 19
I/bluedroid( 208): bt_enable: ret: -1, errno: 19
I/bluedroid( 208): bt_enable: ret: -1, errno: 19
I/bluedroid( 208): bt_enable: ret: -1, errno: 19
I/bluedroid( 208): bt_enable: ret: -1, errno: 19
Ok... no bluetooth, I could live without that but after starting
camera, nothing happened.
Screen black, device did not really respond on pressing backkeys in
the Logs I can see:
Code:
/ActivityManager( 196): Start proc com.android.camera for activity
com.android.camera/.Camera: pid=968 uid=10007 gids={1006, 1015}
D/OpenGLRenderer( 374): Flushing caches (mode 1)
E/CameraHAL( 120): Couldn't get camera properties
W/dalvikvm( 968): threadid=11: thread exiting with uncaught exception
(group=0x40a351f8)
E/AndroidRuntime( 968): FATAL EXCEPTION: Thread-72
E/AndroidRuntime( 968): java.lang.RuntimeException: Fail to get
camera info
E/AndroidRuntime( 968): at
android.hardware.Camera.getCameraInfo(Native Method)
E/AndroidRuntime( 968): at
com.android.camera.CameraHolder.<init>(CameraHolder.java:102)
E/AndroidRuntime( 968): at
com.android.camera.CameraHolder.instance(CameraHolder.java:66)
E/AndroidRuntime( 968): at
com.android.camera.Util.openCamera(Util.java:267)
E/AndroidRuntime( 968): at com.android.camera.Camera
$4.run(Camera.java:1100)
E/AndroidRuntime( 968): at java.lang.Thread.run(Thread.java:856)
W/ActivityManager( 196): Force finishing activity
com.android.camera/.Camera
D/OpenGLRenderer( 374): Flushing caches (mode 0)
D/dalvikvm( 968): GC_CONCURRENT freed 207K, 3% free 12857K/13127K,
paused 2ms+3ms
D/dalvikvm( 968): GC_FOR_ALLOC freed 11K, 2% free 12893K/13127K,
paused 13ms
I/dalvikvm-heap( 968): Grow heap (frag case) to 13.283MB for 662416-
byte allocation
D/dalvikvm( 196): GC_FOR_ALLOC freed 1829K, 14% free 16064K/18631K,
paused 38ms
D/dalvikvm( 968): GC_FOR_ALLOC freed 1K, 3% free 13538K/13831K,
paused 11ms
D/dalvikvm( 968): GC_FOR_ALLOC freed 20K, 2% free 13885K/14087K,
paused 14ms
D/dalvikvm( 968): GC_FOR_ALLOC freed 5K, 2% free 14259K/14471K,
paused 12ms
E/CameraHAL( 120): Couldn't get camera properties
D/AndroidRuntime( 968): Shutting down VM
W/dalvikvm( 968): threadid=1: thread exiting with uncaught exception
(group=0x40a351f8)
I/Process ( 968): Sending signal. PID: 968 SIG: 9
I/ActivityManager( 196): Process com.android.camera (pid 968) has
died.
W/InputManagerService( 196): Window already focused, ignoring focus
gain of: com.android.internal.view.IInputMethodClient$Stub
[email protected]
I/ActivityManager( 196): START {act=android.intent.action.MAIN
cat=[android.intent.category.LAUNCHER] flg=0x10200000
cmp=com.android.camera/.Camera bnds=[40,785][200,985]} from pid 374
I/ActivityManager( 196): Start proc com.android.camera for activity
com.android.camera/.Camera: pid=990 uid=10007 gids={1006, 1015}
D/dalvikvm( 118): GC_EXPLICIT freed 36K, 3% free 12559K/12867K,
paused 2ms+3ms
D/OpenGLRenderer( 374): Flushing caches (mode 1)
D/dalvikvm( 118): GC_EXPLICIT freed <1K, 3% free 12559K/12867K,
paused 9ms+2ms
D/OpenGLRenderer( 374): Flushing caches (mode 0)
D/dalvikvm( 118): GC_EXPLICIT freed <1K, 3% free 12559K/12867K,
paused 1ms+2ms
E/CameraHAL( 120): Couldn't get camera properties
W/dalvikvm( 990): threadid=11: thread exiting with uncaught exception
(group=0x40a351f8)
E/AndroidRuntime( 990): FATAL EXCEPTION: Thread-75
E/AndroidRuntime( 990): java.lang.RuntimeException: Fail to get
camera info
E/AndroidRuntime( 990): at
android.hardware.Camera.getCameraInfo(Native Method)
E/AndroidRuntime( 990): at
com.android.camera.CameraHolder.<init>(CameraHolder.java:102)
E/AndroidRuntime( 990): at
com.android.camera.CameraHolder.instance(CameraHolder.java:66)
E/AndroidRuntime( 990): at
com.android.camera.Util.openCamera(Util.java:267)
E/AndroidRuntime( 990): at com.android.camera.Camera
$4.run(Camera.java:1100)
E/AndroidRuntime( 990): at java.lang.Thread.run(Thread.java:856)
W/ActivityManager( 196): Force finishing activity
com.android.camera/.Camera
D/dalvikvm( 196): GC_CONCURRENT freed 530K, 13% free 16374K/18631K,
paused 7ms+6ms
D/dalvikvm( 990): GC_CONCURRENT freed 236K, 3% free 12824K/13127K,
paused 3ms+7ms
D/dalvikvm( 990): GC_FOR_ALLOC freed 12K, 2% free 12899K/13127K,
paused 13ms
I/dalvikvm-heap( 990): Grow heap (frag case) to 13.290MB for 662416-
byte allocation
D/dalvikvm( 990): GC_CONCURRENT freed 3K, 3% free 13543K/13831K,
paused 2ms+4ms
D/dalvikvm( 990): GC_FOR_ALLOC freed 20K, 2% free 13889K/14087K,
paused 20ms
D/dalvikvm( 990): GC_FOR_ALLOC freed 5K, 2% free 14263K/14471K,
paused 13ms
E/CameraHAL( 120): Couldn't get camera properties
D/AndroidRuntime( 990): Shutting down VM
W/dalvikvm( 990): threadid=1: thread exiting with uncaught exception
(group=0x40a351f8)
I/Process ( 990): Sending signal. PID: 990 SIG: 9
I/ActivityManager( 196): Process com.android.camera (pid 990) has
died.
W/InputManagerService( 196): Window already focused, ignoring focus
gain of: com.android.internal.view.IInputMethodClient$Stub
[email protected]
D/dalvikvm( 374): GC_CONCURRENT freed 1178K, 30% free 17250K/24583K,
paused 6ms+5ms
I/ActivityManager( 196): START {act=android.intent.action.MAIN
cat=[android.intent.category.LAUNCHER] flg=0x10200000
cmp=com.android.camera/.Camera bnds=[40,785][200,985]} from pid 374
I/ActivityManager( 196): Start proc com.android.camera for activity
com.android.camera/.Camera: pid=1011 uid=10007 gids={1006, 1015}
D/OpenGLRenderer( 374): Flushing caches (mode 1)
D/OpenGLRenderer( 374): Flushing caches (mode 0)
E/CameraHAL( 120): Couldn't get camera properties
W/dalvikvm( 1011): threadid=11: thread exiting with uncaught exception
(group=0x40a351f8)
E/AndroidRuntime( 1011): FATAL EXCEPTION: Thread-78
E/AndroidRuntime( 1011): java.lang.RuntimeException: Fail to get
camera info
E/AndroidRuntime( 1011): at
android.hardware.Camera.getCameraInfo(Native Method)
E/AndroidRuntime( 1011): at
com.android.camera.CameraHolder.<init>(CameraHolder.java:102)
E/AndroidRuntime( 1011): at
com.android.camera.CameraHolder.instance(CameraHolder.java:66)
E/AndroidRuntime( 1011): at
com.android.camera.Util.openCamera(Util.java:267)
E/AndroidRuntime( 1011): at com.android.camera.Camera
$4.run(Camera.java:1100)
E/AndroidRuntime( 1011): at java.lang.Thread.run(Thread.java:856)
W/ActivityManager( 196): Force finishing activity
com.android.camera/.Camera
D/dalvikvm( 1011): GC_CONCURRENT freed 206K, 3% free 12858K/13127K,
paused 7ms+3ms
D/dalvikvm( 1011): GC_FOR_ALLOC freed 11K, 2% free 12898K/13127K,
paused 13ms
I/dalvikvm-heap( 1011): Grow heap (frag case) to 13.288MB for 662416-
byte allocation
D/dalvikvm( 1011): GC_CONCURRENT freed 1K, 3% free 13543K/13831K,
paused 7ms+1ms
D/dalvikvm( 1011): GC_FOR_ALLOC freed 20K, 2% free 13889K/14087K,
paused 32ms
D/dalvikvm( 1011): GC_FOR_ALLOC freed 5K, 2% free 14263K/14471K,
paused 31ms
E/CameraHAL( 120): Couldn't get camera properties
D/AndroidRuntime( 1011): Shutting down VM
W/dalvikvm( 1011): threadid=1: thread exiting with uncaught exception
(group=0x40a351f8)
I/Process ( 1011): Sending signal. PID: 1011 SIG: 9
I/ActivityManager( 196): Process com.android.camera (pid 1011) has
died.
W/InputManagerService( 196): Window already focused, ignoring focus
gain of: com.android.internal.view.IInputMethodClient$Stub
[email protected]
I/power ( 196): *** set_screen_state 0
D/SurfaceFlinger( 117): About to give-up screen, flinger = 0xf1b918
D/dalvikvm( 196): GC_CONCURRENT freed 913K, 12% free 16407K/18631K,
paused 6ms+6ms
D/dalvikvm( 196): GC_EXPLICIT freed 54K, 13% free 16352K/18631K,
paused 3ms+6ms
D/NfcService( 359): NFC-C OFF, disconnect
V/TransportControlView( 196): Create TCV
[email protected]
D/PhoneStatusBar( 263): disable: < expand icons alerts ticker
system_info back home RECENT* clock >
D/dalvikvm( 196): GC_CONCURRENT freed 34K, 8% free 17147K/18631K,
paused 3ms+7ms
W/IInputConnectionWrapper( 196): showStatusIcon on inactive
InputConnection
and
Code:
I/ActivityManager( 196): START {act=android.intent.action.MAIN
cat=[android.intent.category.LAUNCHER] flg=0x10200000
cmp=com.android.camera/.Camera bnds=[40,785][200,985]} from pid 374
I/ActivityManager( 196): Start proc com.android.camera for activity
com.android.camera/.Camera: pid=968 uid=10007 gids={1006, 1015}
D/OpenGLRenderer( 374): Flushing caches (mode 1)
E/CameraHAL( 120): Couldn't get camera properties
W/dalvikvm( 968): threadid=11: thread exiting with uncaught exception
(group=0x40a351f8)
E/AndroidRuntime( 968): FATAL EXCEPTION: Thread-72
E/AndroidRuntime( 968): java.lang.RuntimeException: Fail to get
camera info
E/AndroidRuntime( 968): at
android.hardware.Camera.getCameraInfo(Native Method)
E/AndroidRuntime( 968): at
com.android.camera.CameraHolder.<init>(CameraHolder.java:102)
E/AndroidRuntime( 968): at
com.android.camera.CameraHolder.instance(CameraHolder.java:66)
E/AndroidRuntime( 968): at
com.android.camera.Util.openCamera(Util.java:267)
E/AndroidRuntime( 968): at com.android.camera.Camera
$4.run(Camera.java:1100)
E/AndroidRuntime( 968): at java.lang.Thread.run(Thread.java:856)
W/ActivityManager( 196): Force finishing activity
com.android.camera/.Camera
D/OpenGLRenderer( 374): Flushing caches (mode 0)
D/dalvikvm( 968): GC_CONCURRENT freed 207K, 3% free 12857K/13127K,
paused 2ms+3ms
D/dalvikvm( 968): GC_FOR_ALLOC freed 11K, 2% free 12893K/13127K,
paused 13ms
I/dalvikvm-heap( 968): Grow heap (frag case) to 13.283MB for 662416-
byte allocation
D/dalvikvm( 196): GC_FOR_ALLOC freed 1829K, 14% free 16064K/18631K,
paused 38ms
D/dalvikvm( 968): GC_FOR_ALLOC freed 1K, 3% free 13538K/13831K,
paused 11ms
D/dalvikvm( 968): GC_FOR_ALLOC freed 20K, 2% free 13885K/14087K,
paused 14ms
D/dalvikvm( 968): GC_FOR_ALLOC freed 5K, 2% free 14259K/14471K,
paused 12ms
E/CameraHAL( 120): Couldn't get camera properties
D/AndroidRuntime( 968): Shutting down VM
W/dalvikvm( 968): threadid=1: thread exiting with uncaught exception
(group=0x40a351f8)
I/Process ( 968): Sending signal. PID: 968 SIG: 9
I/ActivityManager( 196): Process com.android.camera (pid 968) has
died.
W/InputManagerService( 196): Window already focused, ignoring focus
gain of: com.android.internal.view.IInputMethodClient$Stub
[email protected]
Some guy on IRC told me that the imgtech properitaeries are extracted to the wrong folder so I tried copying them like this:
Code:
cp -av vendor/imgtec/maguro/* vendor/samsung/maguro/
This didn't work.
I also tried the documentation from: http://www.franziroesner.com/blog/2...ary-binaries-for-custom-android-galaxy-nexus/
Did not work. I get mad...
And yes, I could have this one attached to the build thread, but I didn't want to brick this one more and get a new clean starting for help.
Pretty sure camera and bt proprietaries come from 4.0.2.
As said, there are different binaries needed for camera/bluetooth. Not got a link personally but I have seen it somewhere in the Compile thread on here
I read the thread and tried both ways of getting the properitary modules.
Both fail.
You might want to contact the dev of this http://forum.xda-developers.com/showthread.php?t=1444413
Sorry, I can't help much, as I am not a developer
Sent from my Galaxy Nexus using xda premium
t4c said:
I read the thread and tried both ways of getting the properitary modules.
Both fail.
Click to expand...
Click to collapse
Define 'both ways'.
adrynalyne I tried to extract the files via the 2 files I can download on the code.google page.
The other way I tried was the one mentioned in the build thread: http://www.franziroesner.com/blog/2...ary-binaries-for-custom-android-galaxy-nexus/
Did you make clean? The second method certainly should have worked.
I always make clean before make.

Categories

Resources