Jump to content

JolyonS

Members
  • Content Count

    144
  • Joined

  • Last visited

Community Reputation

11 Good

About JolyonS

  • Rank
    Regular

Contact Methods

  • Website URL
    http://
  • ICQ
    0

Profile Information

  • Your Current Device(s)
    San Francisco
  1. Yes, it's nice and stable and yes, it's fine on my Orange San Francisco. There might not be a compelling reason to move from it if you are happy with your current ROM but there's nothing I've found that would make you regret the change if you made it.
  2. This is very impressive, tilal - looks like it may well be good enough to be my everyday ROM. What launchers are people using? I've tried Nova but had a force close or two (admittedly when I was downloading dozens of apps from the Market). Apex seems to be okay but is either of these a significant improvement over Trebuchet?
  3. Never got anywhere near that with any ROM (and I have tried almost all of them). I might have to let a vanilla CM7 install sit in airplane mode and see how long I get out of it (is the shutdown due to low battery event logged anywhere useful so I could get timings on this?)
  4. When booting I get the following errors logged W/PackageManager( 177): Unknown permission android.permission.READ_OWNER_DATA in package com.google .android.setupwizard W/PackageManager( 177): Unknown permission android.permission.WRITE_OWNER_DATA in package com.googl e.android.setupwizard And indeed the setup wizard does not run. Get a few other unknown / not granted permission errors too: W/PackageManager( 177): Not granting permission com.google.android.gm.permission.READ_GMAIL to pack age com.google.android.apps.uploader (protectionLevel=2 flags=0x8be45) W/PackageManager( 177): Unknown permission android.permission.READ_EXTERNAL_STORAGE in package com. android.vending W/PackageManager( 177): Not granting permission android.permission.SEND_DOWNLOAD_COMPLETED_INTENTS to package com.android.vending (protectionLevel=2 flags=0xabe45) W/PackageManager( 177): Unknown permission com.android.providers.im.permission.READ_ONLY in package com.google.android.apps.maps W/PackageManager( 177): Not granting permission android.permission.DEVICE_POWER to package com.andr oid.deskclock (protectionLevel=2 flags=0x8be45)
  5. Having problems with GO Launcher - see log snippet below if you are interested. This was with Android Widgets Pro / Google Reader. Going to try a different launcher and see how I get on. E/Adreno200-EGL( 3531): egliGetNativeWindowSize: unable to dequeue native buffer D/SurfaceTexture( 104): SurfaceTexture::dequeue: Not allowed to dequeue more than a buffer SLEEPING D/SurfaceTexture( 104): SurfaceTexture::dequeue: Not allowed to dequeue more than a buffer SLEEPING D/SurfaceTexture( 104): SurfaceTexture::dequeue: Not allowed to dequeue more than a buffer SLEEPING D/SurfaceTexture( 104): SurfaceTexture::dequeue: Not allowed to dequeue more than a buffer SLEEPING D/SurfaceTexture( 104): SurfaceTexture::dequeue: Not allowed to dequeue more than a buffer RETRY mBufferCount:2 mServerBufferCount:2 E/memalloc( 104): /dev/pmem: No more pmem available W/memalloc( 104): Falling back to ashmem E/memalloc( 104): alloc mmap(fd=36, size=1536000, prot=3) failed (Try again) E/msm7x27.gralloc( 104): gralloc failed err=Try again W/GraphicBufferAllocator( 104): alloc(480, 800, 1, 00000303, ...) failed -11 (Try again) E/SurfaceFlinger( 104): GraphicBufferAlloc::createGraphicBuffer(w=480, h=800) failed (Try again), handle=0x0 E/SurfaceTexture( 104): [com.gau.go.launcherex/com.jiubang.ggheart.apps.desks.diy.GoLauncher] dequeueBuffer: SurfaceComposer::createGraphicBuffer failed E/Adreno200-EGL( 3531): egliGetNativeWindowSize: unable to dequeue native buffer E/libEGL ( 3531): eglMakeCurrent:678 error 3003 (EGL_BAD_ALLOC) E/ViewRootImpl( 3531): OutOfResourcesException initializing HW surface E/ViewRootImpl( 3531): android.view.Surface$OutOfResourcesException: eglMakeCurrent failed EGL_BAD_ALLOC E/ViewRootImpl( 3531): at android.view.HardwareRenderer$GlRenderer.createEglSurface(HardwareRenderer.java:689) E/ViewRootImpl( 3531): at android.view.HardwareRenderer$GlRenderer.initialize(HardwareRenderer.java:519) E/ViewRootImpl( 3531): at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:1300) E/ViewRootImpl( 3531): at android.view.ViewRootImpl.handleMessage(ViewRootImpl.java:2442) E/ViewRootImpl( 3531): at android.os.Handler.dispatchMessage(Handler.java:99) E/ViewRootImpl( 3531): at android.os.Looper.loop(Looper.java:137) E/ViewRootImpl( 3531): at android.app.ActivityThread.main(ActivityThread.java:4424) E/ViewRootImpl( 3531): at java.lang.reflect.Method.invokeNative(Native Method) E/ViewRootImpl( 3531): at java.lang.reflect.Method.invoke(Method.java:511) E/ViewRootImpl( 3531): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:787) E/ViewRootImpl( 3531): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:554) E/ViewRootImpl( 3531): at dalvik.system.NativeStart.main(Native Method) I/Process ( 3531): Sending signal. PID: 3531 SIG: 9 I/WindowManager( 186): Out of memory for surface! Looking for leaks... W/WindowManager( 186): No leaked surfaces; killing applicatons! W/ActivityManager( 186): Killing processes Free memory at adjustment 5 W/ViewRootImpl( 3531): No processes killed for memory; killing self I/WindowManager( 186): WIN DEATH: Window{41769f10 com.gau.go.launcherex/com.jiubang.ggheart.apps.desks.diy.GoLauncher paused=false} W/WindowManager( 186): Due to memory failure, waiting a bit for next layout I/ActivityManager( 186): Process android.process.acore (pid 3531) has died. W/NetworkManagementSocketTagger( 186): setKernelCountSet(10059, 0) failed with errno -2 W/ActivityManager( 186): Scheduling restart of crashed service com.gau.go.launcherex/com.jiubang.ggheart.data.AppService in 5000ms
  6. Ah, that might well be it as it seems fine for a short while then bombs out - perhaps at the first instruction. It isn't something I need as I walk rather than driving, I just fired it up because the button was there! Which is the 'full' gapps package?
  7. Well, I have this installed and running and no major problems so far. Google Maps navigation FCs every time I try it and I've had one unexpected reboot. I don't use this phone for calls and texts but the browsing is fine and the basic google maps is great so it's good enough for my needs from a functional point of view. Battery life seems poor - but it hasn't been a normal usage pattern for me so I'll see how that settles down. The Gapps package could be better - did not get the Welcome to Android start up with either of the packages linked in this thread but still, gmail and google reader are syncing okay now. Market needed a bit of fiddling to get up and running - the initial request to sign in produced a black screen with keyboard overlay that ground to a near halt and then eventually FCd at which point it was possible to sign in by from the menu in the market app. I'm very impressed with how quickly this has become a stable and usable product, good work.
  8. When the first Stir Fry ROMs came out they provided better battery life than the CyanogenMod build available at the same time - this was tested by several of us using same application load and same usage patterns on each. The later releases of the Stir Fry ROMs were less superior to subsequent CyanogenMods and the current state of affairs with CM is perfectly adequate as far as battery life is concerned - I'd be surprised to find it significantly outperformed by any of the other available ROMs.
  9. Brunch, lunch, bacon, Newegg, Ice Cream Sandwich - I am now very hungry.
  10. Not necessarily true - there may be features of a particular ROM which cause an application to produce excessive drain. As I say I have no scientific tests and I don't really think that it is possible for an individual to produce anything generally useful but I can say that in my experience I got notably better battery life from early GSF builds than anything else I have tried with the same apps installed and the same usage patterns in the same locations. CM7 has improved in this regard over time and I now feel like I can rely on 24 hours but unfortunately that still means a daily recharge.
  11. I suspect both of those two myself in a completely unscientific way. I can bin Facebook but Google Maps is probably in the top three apps I use - are there any good alternatives? (I don't need navigation, just reliable mapping).
  12. If you could produce a list of these that would be really appreciated. Well which is it?! ;) As will the strength of signal, I guess. I may have to get busy with Tasker and be more selective about where and when 3G is enabled.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.