Guest Bomberjack Posted September 30, 2012 Report Share Posted September 30, 2012 (edited) Hi, I hope somebody can help me. I use this latest build, and I used the previous version too. When I start a call, my LCD screen go to black. I can't STOP a call, I can't do anything (and the screen is black). How can I fix this problem? Is anybody have the same problem? 2nd problem is the memory allocator for opengl textures. You can test it in angry birds seasons, and I can reproduce it in my app.\ I didn't show it in the standard angry birds. At first, I switched on Large Heap mode. (it have to be allows 64 mbyte heap). And I try to allocate textures, but It generate various crashes: 1. simple out of memory, my app killed by system 2. my app started with white blocks (some textures is a simple white 0xffffffff, some textures works) 3. the phone crash and reboot When I started my app I had 197Mb free memory(I check it in ES Task manager widget) My app worked with the factory's 2.3 system. I get error messages in Logcat: 09-30 18:08:15.430: D/dalvikvm(8327): GC_FOR_ALLOC freed 5130K, 52% free 5849K/12103K, paused 40ms, total 43ms 09-30 18:08:15.440: I/dalvikvm-heap(8327): Grow heap (frag case) to 17.956MB for 4194320-byte allocation 09-30 18:08:15.590: D/dalvikvm(8327): GC_CONCURRENT freed 10K, 33% free 10963K/16263K, paused 4ms+24ms, total 144ms 09-30 18:08:15.700: I/dalvikvm(8327): Jit: resizing JitTable from 1024 to 2048 09-30 18:08:15.970: D/dalvikvm(8327): GC_FOR_ALLOC freed 4104K, 58% free 6875K/16263K, paused 29ms, total 29ms 09-30 18:08:15.970: I/dalvikvm-heap(8327): Grow heap (frag case) to 18.958MB for 4194320-byte allocation 09-30 18:08:16.110: D/dalvikvm(8327): GC_CONCURRENT freed <1K, 33% free 10970K/16263K, paused 4ms+6ms, total 140ms 09-30 18:08:16.590: D/TEX LOADED(8327): loaded - w:1024 h:1024 09-30 18:08:16.710: D/dalvikvm(8327): GC_FOR_ALLOC freed 4096K, 58% free 6874K/16263K, paused 31ms, total 31ms 09-30 18:08:17.140: I/dalvikvm-heap(8327): Grow heap (frag case) to 23.708MB for 9175056-byte allocation 09-30 18:08:17.370: D/dalvikvm(8327): GC_CONCURRENT freed <1K, 38% free 15834K/25287K, paused 16ms+45ms, total 226ms 09-30 18:08:19.270: D/TEX LOADED(8327): loaded - w:2048 h:1120 09-30 18:08:20.080: I/Adreno(8327): ioctl code 0xc00c092f (IOCTL_KGSL_GPMEM_ALLOC) failed: errno 12 Out of memory 09-30 18:08:20.120: I/Adreno(8327): ioctl code 0xc00c092f (IOCTL_KGSL_GPMEM_ALLOC) failed: errno 12 Out of memory 09-30 18:08:20.120: E/Adreno200-ES20(8327): <qgl2DrvAPI_glTexImage2D:412>: GL_OUT_OF_MEMORY 09-30 18:08:20.120: E/Adreno200-ES11(8327): <qglDrvAPI_glTexImage2D:1914>: GL_OUT_OF_MEMORY 09-30 18:08:20.140: D/TEX LOADED(8327): loaded - w:256 h:128 09-30 18:08:20.140: E/Adreno200-ES11(8327): <qglDrvAPI_glTexImage2D:1913>: GL_OUT_OF_MEMORY 09-30 18:08:20.250: D/TEX LOADED(8327): loaded - w:1024 h:1024 09-30 18:08:20.310: E/Adreno200-ES11(8327): <qglDrvAPI_glTexImage2D:1913>: GL_OUT_OF_MEMORY 09-30 18:08:20.340: D/dalvikvm(8327): GC_FOR_ALLOC freed 13184K, 73% free 6875K/25287K, paused 31ms, total 32ms 09-30 18:08:20.340: I/dalvikvm-heap(8327): Grow heap (frag case) to 18.958MB for 4194320-byte allocation 09-30 18:08:20.470: D/dalvikvm(8327): GC_CONCURRENT freed <1K, 57% free 10970K/25287K, paused 4ms+36ms, total 127ms 09-30 18:08:20.480: D/TEX LOADED(8327): loaded - w:1024 h:1024 09-30 18:08:20.980: E/Adreno200-ES11(8327): <qglDrvAPI_glTexImage2D:1913>: GL_OUT_OF_MEMORY 09-30 18:08:21.010: D/dalvikvm(8327): GC_FOR_ALLOC freed 4096K, 73% free 6874K/25287K, paused 32ms, total 33ms 09-30 18:08:21.010: I/dalvikvm-heap(8327): Grow heap (frag case) to 18.958MB for 4194320-byte allocation 09-30 18:08:21.130: D/dalvikvm(8327): GC_CONCURRENT freed <1K, 57% free 10970K/25287K, paused 4ms+6ms, total 119ms 09-30 18:08:21.150: D/TEX LOADED(8327): loaded - w:1024 h:1024 09-30 18:08:22.030: E/Adreno200-ES11(8327): <qglDrvAPI_glTexImage2D:1913>: GL_OUT_OF_MEMORY 09-30 18:08:22.070: D/dalvikvm(8327): GC_FOR_ALLOC freed 4096K, 73% free 6874K/25287K, paused 32ms, total 33ms 09-30 18:08:22.070: I/dalvikvm-heap(8327): Grow heap (frag case) to 18.958MB for 4194320-byte allocation 09-30 18:08:22.200: D/dalvikvm(8327): GC_CONCURRENT freed <1K, 57% free 10970K/25287K, paused 4ms+47ms, total 132ms 09-30 18:08:22.210: D/TEX LOADED(8327): loaded - w:1024 h:1024 09-30 18:08:22.470: E/Adreno200-ES11(8327): <qglDrvAPI_glTexImage2D:1913>: GL_OUT_OF_MEMORY 09-30 18:08:22.470: D/TEX LOADED(8327): loaded - w:16 h:6 09-30 18:08:22.470: E/Adreno200-ES11(8327): <qglDrvAPI_glTexImage2D:1913>: GL_OUT_OF_MEMORY edited: grammar issues Edited September 30, 2012 by Bomberjack Link to comment Share on other sites More sharing options...
Guest hugobosslives Posted September 30, 2012 Report Share Posted September 30, 2012 Hi, I hope somebody can help me. I use this latest build, and I used the previous version too. When I start a call, my LCD screen go to black. I can't STOP a call, I can't do anything (and the screen is black). How can I fix this problem? Is anybody have the same problem? yer its common. go settings. advanced. and then calibrate the proximity sensor. Link to comment Share on other sites More sharing options...
Guest Bomberjack Posted September 30, 2012 Report Share Posted September 30, 2012 (edited) hurray! its works fine now, BIG thanks :) Edited September 30, 2012 by Bomberjack Link to comment Share on other sites More sharing options...
Guest razzmataz1478 Posted September 30, 2012 Report Share Posted September 30, 2012 Hi, I hope somebody can help me. I use this latest build, and I used the previous version too. When I start a call, my LCD screen go to black. I can't STOP a call, I can't do anything (and the screen is black). How can I fix this problem? Is anybody have the same problem? 2nd problem is the memory allocator for opengl textures. You can test it in angry birds seasons, and I can reproduce it in my app.\ I didn't show it in the standard angry birds. At first, I switched on Large Heap mode. (it have to be allows 64 mbyte heap). And I try to allocate textures, but It generate various crashes: 1. simple out of memory, my app killed by system 2. my app started with white blocks (some textures is a simple white 0xffffffff, some textures works) 3. the phone crash and reboot When I started my app I had 197Mb free memory(I check it in ES Task manager widget) My app worked with the factory's 2.3 system. I get error messages in Logcat: 09-30 18:08:15.430: D/dalvikvm(8327): GC_FOR_ALLOC freed 5130K, 52% free 5849K/12103K, paused 40ms, total 43ms 09-30 18:08:15.440: I/dalvikvm-heap(8327): Grow heap (frag case) to 17.956MB for 4194320-byte allocation 09-30 18:08:15.590: D/dalvikvm(8327): GC_CONCURRENT freed 10K, 33% free 10963K/16263K, paused 4ms+24ms, total 144ms 09-30 18:08:15.700: I/dalvikvm(8327): Jit: resizing JitTable from 1024 to 2048 09-30 18:08:15.970: D/dalvikvm(8327): GC_FOR_ALLOC freed 4104K, 58% free 6875K/16263K, paused 29ms, total 29ms 09-30 18:08:15.970: I/dalvikvm-heap(8327): Grow heap (frag case) to 18.958MB for 4194320-byte allocation 09-30 18:08:16.110: D/dalvikvm(8327): GC_CONCURRENT freed <1K, 33% free 10970K/16263K, paused 4ms+6ms, total 140ms 09-30 18:08:16.590: D/TEX LOADED(8327): loaded - w:1024 h:1024 09-30 18:08:16.710: D/dalvikvm(8327): GC_FOR_ALLOC freed 4096K, 58% free 6874K/16263K, paused 31ms, total 31ms 09-30 18:08:17.140: I/dalvikvm-heap(8327): Grow heap (frag case) to 23.708MB for 9175056-byte allocation 09-30 18:08:17.370: D/dalvikvm(8327): GC_CONCURRENT freed <1K, 38% free 15834K/25287K, paused 16ms+45ms, total 226ms 09-30 18:08:19.270: D/TEX LOADED(8327): loaded - w:2048 h:1120 09-30 18:08:20.080: I/Adreno(8327): ioctl code 0xc00c092f (IOCTL_KGSL_GPMEM_ALLOC) failed: errno 12 Out of memory 09-30 18:08:20.120: I/Adreno(8327): ioctl code 0xc00c092f (IOCTL_KGSL_GPMEM_ALLOC) failed: errno 12 Out of memory 09-30 18:08:20.120: E/Adreno200-ES20(8327): <qgl2DrvAPI_glTexImage2D:412>: GL_OUT_OF_MEMORY 09-30 18:08:20.120: E/Adreno200-ES11(8327): <qglDrvAPI_glTexImage2D:1914>: GL_OUT_OF_MEMORY 09-30 18:08:20.140: D/TEX LOADED(8327): loaded - w:256 h:128 09-30 18:08:20.140: E/Adreno200-ES11(8327): <qglDrvAPI_glTexImage2D:1913>: GL_OUT_OF_MEMORY 09-30 18:08:20.250: D/TEX LOADED(8327): loaded - w:1024 h:1024 09-30 18:08:20.310: E/Adreno200-ES11(8327): <qglDrvAPI_glTexImage2D:1913>: GL_OUT_OF_MEMORY 09-30 18:08:20.340: D/dalvikvm(8327): GC_FOR_ALLOC freed 13184K, 73% free 6875K/25287K, paused 31ms, total 32ms 09-30 18:08:20.340: I/dalvikvm-heap(8327): Grow heap (frag case) to 18.958MB for 4194320-byte allocation 09-30 18:08:20.470: D/dalvikvm(8327): GC_CONCURRENT freed <1K, 57% free 10970K/25287K, paused 4ms+36ms, total 127ms 09-30 18:08:20.480: D/TEX LOADED(8327): loaded - w:1024 h:1024 09-30 18:08:20.980: E/Adreno200-ES11(8327): <qglDrvAPI_glTexImage2D:1913>: GL_OUT_OF_MEMORY 09-30 18:08:21.010: D/dalvikvm(8327): GC_FOR_ALLOC freed 4096K, 73% free 6874K/25287K, paused 32ms, total 33ms 09-30 18:08:21.010: I/dalvikvm-heap(8327): Grow heap (frag case) to 18.958MB for 4194320-byte allocation 09-30 18:08:21.130: D/dalvikvm(8327): GC_CONCURRENT freed <1K, 57% free 10970K/25287K, paused 4ms+6ms, total 119ms 09-30 18:08:21.150: D/TEX LOADED(8327): loaded - w:1024 h:1024 09-30 18:08:22.030: E/Adreno200-ES11(8327): <qglDrvAPI_glTexImage2D:1913>: GL_OUT_OF_MEMORY 09-30 18:08:22.070: D/dalvikvm(8327): GC_FOR_ALLOC freed 4096K, 73% free 6874K/25287K, paused 32ms, total 33ms 09-30 18:08:22.070: I/dalvikvm-heap(8327): Grow heap (frag case) to 18.958MB for 4194320-byte allocation 09-30 18:08:22.200: D/dalvikvm(8327): GC_CONCURRENT freed <1K, 57% free 10970K/25287K, paused 4ms+47ms, total 132ms 09-30 18:08:22.210: D/TEX LOADED(8327): loaded - w:1024 h:1024 09-30 18:08:22.470: E/Adreno200-ES11(8327): <qglDrvAPI_glTexImage2D:1913>: GL_OUT_OF_MEMORY 09-30 18:08:22.470: D/TEX LOADED(8327): loaded - w:16 h:6 09-30 18:08:22.470: E/Adreno200-ES11(8327): <qglDrvAPI_glTexImage2D:1913>: GL_OUT_OF_MEMORY edited: grammar issues I've noticed big memory problems, especially with the bitmap renderer. Link to comment Share on other sites More sharing options...
Guest tilal6991 Posted September 30, 2012 Report Share Posted September 30, 2012 There are massive memory/graphics issues - basically the stuff that makes the ROM smooth also causes this stuff. Link to comment Share on other sites More sharing options...
Guest razzmataz1478 Posted September 30, 2012 Report Share Posted September 30, 2012 There are massive memory/graphics issues - basically the stuff that makes the ROM smooth also causes this stuff. So our 512mb RAM is feeling the effect, eh? A personal opinion: I feel that this is the final OS version that our trusty Skates will be able to handle without it being unusable. A sad note but hopefully it will be some time before this happens and we still have this to play with until then. Who knows I may be wrong... I'm thinking you're right. Link to comment Share on other sites More sharing options...
Guest utternoob Posted September 30, 2012 Report Share Posted September 30, 2012 Such a shame :'( Link to comment Share on other sites More sharing options...
Guest razzmataz1478 Posted September 30, 2012 Report Share Posted September 30, 2012 (edited) Off topic..but: @Lalit You're slightly late to the party... http://www.xda-developers.com/android/cyanogenmod-for-the-sony-xperia-t-in-three-different-flavors/ Edited September 30, 2012 by razzmataz1478 Link to comment Share on other sites More sharing options...
Guest matt4321 Posted September 30, 2012 Report Share Posted September 30, 2012 Computing and Maths at University.I'm younger than the rest of my year. That's why there is a gap between you and me Raz. Applying to Oxford and Imperial as well as 3 Scottish Unis. I'm doing computing at uni next year! Not at Oxford, not smart enough, although i do live there. Its an awesome place! You'd love it. Link to comment Share on other sites More sharing options...
Guest Bomberjack Posted September 30, 2012 Report Share Posted September 30, 2012 I've noticed big memory problems, especially with the bitmap renderer. yes, I found a new fun, the memory is leaking in the os (not in my game). When I rebooted the phone, this problem gone. But I'm working on the phone, so I have to reboot to free this leaks. Link to comment Share on other sites More sharing options...
Guest ir1997 Posted September 30, 2012 Report Share Posted September 30, 2012 tilal if you have time can you do a gapps update if there is a update Link to comment Share on other sites More sharing options...
Guest ScouseMouse Posted September 30, 2012 Report Share Posted September 30, 2012 (edited) I got 2 zte skates, ive put this rom on both of them however on 1 of them the wifi isnt working...I know the wifi is ok as it was working fine on a different rom I had on it earlier...any ideas? Edited September 30, 2012 by ScouseMouse Link to comment Share on other sites More sharing options...
Guest iYowo Posted October 1, 2012 Report Share Posted October 1, 2012 (edited) what is cfx2nightly? http://goo.im/devs/tilal6991/roms/skate/cfx2nightly/cm-10-20120930-EXPERIMENTAL-skate-ColdFusionX2-tilal6991.zip Edited October 1, 2012 by iYowo Link to comment Share on other sites More sharing options...
Guest tilal6991 Posted October 1, 2012 Report Share Posted October 1, 2012 Nightly builds of the ROM. Link to comment Share on other sites More sharing options...
Guest skywalkerctu Posted October 1, 2012 Report Share Posted October 1, 2012 Nightly builds of the ROM. what's the difference? is it safe to flash? Link to comment Share on other sites More sharing options...
Guest gacama Posted October 1, 2012 Report Share Posted October 1, 2012 Any fix in latest build? Link to comment Share on other sites More sharing options...
Guest creedence Posted October 1, 2012 Report Share Posted October 1, 2012 Dear tilal The new build is ready for download? 2012.09.30 and 2012.10.01 ? Link to comment Share on other sites More sharing options...
Guest mrpuzz Posted October 1, 2012 Report Share Posted October 1, 2012 I downloaded both, but I noticed some graphical errors... so i turn back to 09.16 Link to comment Share on other sites More sharing options...
Guest utternoob Posted October 1, 2012 Report Share Posted October 1, 2012 Nightly builds of the ROM. Does it have full OTA updater? I hear it went official last night/ this morning http://www.talkandroid.com/134341-cm-updater-officially-official-with-cm10-on-deck-to-take-advantage-of-feature-first/ Link to comment Share on other sites More sharing options...
Guest rangeoshun Posted October 1, 2012 Report Share Posted October 1, 2012 what's the difference? is it safe to flash? Flashing should be safe, but it's not intended to be stable. Otherwise it would be in the first post. It's the experimental build of the experimental rom :) Link to comment Share on other sites More sharing options...
Guest tilal6991 Posted October 1, 2012 Report Share Posted October 1, 2012 I've decided to test run nightly builds. Both "theoretically" should be safe to flag but they are untested. Link to comment Share on other sites More sharing options...
Guest creedence Posted October 1, 2012 Report Share Posted October 1, 2012 I've decided to test run nightly builds. Both "theoretically" should be safe to flag but they are untested. No problem! We will test it. Thank you Link to comment Share on other sites More sharing options...
Guest betasergio Posted October 1, 2012 Report Share Posted October 1, 2012 I've decided to test run nightly builds. Both "theoretically" should be safe to flag but they are untested. The 2 compilations doesn`t start properly, one has poblem graphics, and the other doesn`t start. I love your job tilial. Waiting for a new release. Link to comment Share on other sites More sharing options...
Guest creedence Posted October 1, 2012 Report Share Posted October 1, 2012 2012. 09. 30. and 2012. 10. 01. Is there a distinction between the two versions? Link to comment Share on other sites More sharing options...
Guest dandare75 Posted October 1, 2012 Report Share Posted October 1, 2012 Just flashed 10/01 and i get graphics error on boot up... :unsure: Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now