Guest tsakaji30 Posted January 22, 2011 Report Posted January 22, 2011 Hi folks, is there a way to deactivate the weird transitions configured by default on this mod? Or maybe show me the file that I need to modify to get it back to normal? By the way, very good job! This rom is perfect, and the idea of a community edition is perfect! Congratulations team!! Thank you very much!
Guest Richard_Arkless Posted January 22, 2011 Report Posted January 22, 2011 (edited) Hi folks, is there a way to deactivate the weird transitions configured by default on this mod? Or maybe show me the file that I need to modify to get it back to normal? By the way, very good job! This rom is perfect, and the idea of a community edition is perfect! Congratulations team!! Thank you very much! you need to modify the framework-res.apk but if you want to wait ill make a flashable zip which will install either the vanilla or the gingerbread framework done look in the optional stuff then framework and choose what one you want Edited January 22, 2011 by Richard_Arkless
Guest ve100 Posted January 22, 2011 Report Posted January 22, 2011 (edited) toti, you seem to be getting close. good work on troubleshooting.... when i was looking at our camera issue, i checked logcat and was thinking the same. i was also suspecting the camer service. so i opened up one of the newish cm6.1.2 roms, and compared the system libs. i found a camera_client in there, which is not in our rom. could this be a possible issue? then i got busy at work, and couldn't really play with this phone as i don't have a spare. i think it is the client call which triggers the lock and release. our rom might or might not be using a client, but then something needs to lock and release the lock. if lock release is not cleanly handled, the next attempt at hardware access is denied by android. so no further hardware access, till the app supposedly accessing that resource releases it. hence, further attempts at using the camera app are unsuccessful, till after a reboot. http://developer.android.com/reference/and...are/Camera.html public final void unlock () Since: API Level 5 Unlocks the camera to allow another process to access it. Normally, the camera is locked to the process with an active Camera object until release() is called. To allow rapid handoff between processes, you can call this method to release the camera temporarily for another process to use; once the other process is done you can call reconnect() to reclaim the camera. This must be done before calling setCamera(Camera). If you are not recording video, you probably do not need this method. Throws RuntimeException if the camera cannot be unlocked. so i suspect the exception is caused by the camera app calling unavailable functions/libraries incorrectly. can anyone check how our huawei rom's camera app used those libraries? Edited January 22, 2011 by ve100
Guest totiadrenalin Posted January 22, 2011 Report Posted January 22, 2011 The new gralloc.msm7k.so is cosing the 3DGallery not working properly on rotation. So I'll remove it for now.
Guest totiadrenalin Posted January 22, 2011 Report Posted January 22, 2011 (edited) toti, you seem to be getting close. good work on troubleshooting.... when i was looking at our camera issue, i checked logcat and was thinking the same. i was also suspecting the camer service. so i opened up one of the newish cm6.1.2 roms, and compared the system libs. i found a camera_client in there, which is not in our rom. could this be a possible issue? then i got busy at work, and couldn't really play with this phone as i don't have a spare. i think it is the client call which triggers the lock and release. our rom might or might not be using a client, but then something needs to lock and release the lock. if lock release is not cleanly handled, the next attempt at hardware access is denied by android. so no further hardware access, till the app supposedly accessing that resource releases it. hence, further attempts at using the camera app are unsuccessful, till after a reboot. http://developer.android.com/reference/and...are/Camera.html public final void unlock () Since: API Level 5 Unlocks the camera to allow another process to access it. Normally, the camera is locked to the process with an active Camera object until release() is called. To allow rapid handoff between processes, you can call this method to release the camera temporarily for another process to use; once the other process is done you can call reconnect() to reclaim the camera. This must be done before calling setCamera(Camera). If you are not recording video, you probably do not need this method. Throws RuntimeException if the camera cannot be unlocked. so i suspect the exception is caused by the camera app calling unavailable functions/libraries incorrectly. can anyone check how our huawei rom's camera app used those libraries? Yes for sure! In both 2.1 and 1.5 the camera can make zoom in and out buy pressing the volume up and down buttons. startSmoothZoom(int value) and stopSmoothZoom() Bot not in aosp-froyo, cm6 rom, not in aosp-gingerbread and even not in the cm7 alpha build rom. So is there some problem with binding the buttons or or with the camera app, or maiby in the libs? Can somebody tell me how to port applications, so I can make them able to be installed on froyo? I know that there's some sdk lock, but is it in AndroidManifest or somewhere else? Do i need to unpack the camera apk, or what? Since we still use the same kernel .29 I don't think so that there could be any driver incompatibility! I just need to know how to unpack the classes.dex in the application?! Edited January 22, 2011 by totiadrenalin
Guest totiadrenalin Posted January 23, 2011 Report Posted January 23, 2011 Ok! Now a beet reverse-engineering of the camera.apk from 2.1 rom Now if somebody could help me? I just need somebody to tell me where to look, to find the problem of releasing the camera device. Best rebards TOTIcamera_reverse_engineering.zip
Guest rangeoshun Posted January 23, 2011 Report Posted January 23, 2011 (edited) Hi! Have you guys encountered the problem, that in the statusbar the texts are black? If yes, is there an easy way to change that? I tried modify it previously via services.jar but i failed then. Any advices? Thanx in advance! Found it ^ By the way, as far as tried this rom it's really nice, so thanx for it! Great work, and BIG UPS! Edited January 23, 2011 by rangeoshun
Guest totiadrenalin Posted January 23, 2011 Report Posted January 23, 2011 (edited) Hi! Have you guys encountered the problem, that in the statusbar the texts are black? If yes, is there an easy way to change that? I tried modify it previously via services.jar but i failed then. Any advices? Thanx in advance! Found it ^ By the way, as far as tried this rom it's really nice, so thanx for it! Great work, and BIG UPS! Unzip this file. and put the CMTheme folder in root directory of your SDCARD. then: Settings>CyanogenMod settings>User interface>Tweaks extras>Select a theme>gingerbread>OK Avoid the prompt to reboot your phone. No need to reboot. EDIT: I also add this file in my folder in Richards Dropbox. Best Regards TOTIWhite_Clock_StatusBar.zip Edited January 23, 2011 by totiadrenalin
Guest totiadrenalin Posted January 23, 2011 Report Posted January 23, 2011 The new gralloc.msm7k.so is cosing the 3DGallery not working properly on rotation. So I'll remove it for now. Richard! I found out that the Gallery3D it self is defective! And not the gralloc.msm7k.so is causing the rotation bug in the gallery3d app So I'll add a working one Gallery3D.apk in my folder in Dropbox.
Guest Richard_Arkless Posted January 23, 2011 Report Posted January 23, 2011 (edited) Unzip this file. and put the CMTheme folder in root directory of your SDCARD. then: Settings>CyanogenMod settings>User interface>Tweaks extras>Select a theme>gingerbread>OK Avoid the prompt to reboot your phone. No need to reboot. EDIT: I also add this file in my folder in Richards Dropbox. Best Regards TOTI this file is already in the cm parts so it will be in the "select a theme option" under "stock" as soon as they install the rom so no need to put that file on the sd card, problem is setting it to the default so the user doesnt need to do this, I thought naming it the same as the one it normally chooses would work but it doesnt Richard! I found out that the Gallery3D it self is defective! And not the gralloc.msm7k.so is causing the rotation bug in the gallery3d app So I'll add a working one Gallery3D.apk in my folder in Dropbox. ok Edited January 23, 2011 by Richard_Arkless
Guest doivey Posted January 23, 2011 Report Posted January 23, 2011 this file is already in the cm parts so it will be in the "select a theme option" under "stock" as soon as they install the rom so no need to put that file on the sd card, problem is setting it to the default so the user doesnt need to do this, I thought naming it the same as the one it normally chooses would work but it doesnt ok Thanks for this I have finally got my clock back in the status bar :lol: nice one !
Guest darkdevil1 Posted January 23, 2011 Report Posted January 23, 2011 (edited) Maybe its not made for our phones, I would wait for someone to release it or an alternative in the market Yes that is still an issue, I messaged tom g a couple of weeks ago about some other matter and he mentioned in his reply that he is planning on releasing a final of cm6 which fixes some last minute things but I dunno what it will fix, if it will fix this or when it is released for that matter Alright thanks for the info. Might be a good idea to mention that in the OP btw, does anyone else have issues playing HQ youtube videos? The majority display a black screen with no sound, but as soon as I switch to low quality it plays just fine. Rolled back to FLB 1.7 and strangely this also has the same issue :lol: Did youtube change something? Edited January 23, 2011 by darkdevil1
Guest Richard_Arkless Posted January 24, 2011 Report Posted January 24, 2011 btw, does anyone else have issues playing HQ youtube videos? The majority display a black screen with no sound, but as soon as I switch to low quality it plays just fine. Rolled back to FLB 1.7 and strangely this also has the same issue :lol: Did youtube change something? I think (I say I think because the pulse is not my main device now) that youtube videos play fine, dont quote me on that though, tomorrow I will probably test it out and get back to you
Guest Richard_Arkless Posted January 24, 2011 Report Posted January 24, 2011 (edited) right guys im getting the reboot problem now after I wiped and started afresh, im going to look in more detail to discover the reason why we are getting this problem, one thing im kinda concerned about is the fact that the original cm port rom doesnt have this problem which makes me believe it may be something else One thing I want you guys to consider is whether I should remove dtapp2sd from the rom, the fact is we dont really need it as froyo does have a pretty good one that comes by default as for swap toti is making a script that will mount it on boot Edited January 24, 2011 by Richard_Arkless
Guest twrock Posted January 24, 2011 Report Posted January 24, 2011 One thing I want you guys to consider is whether I should remove dtapp2sd from the rom, the fact is we dont really need it as froyo does have a pretty good one that comes by default as for swap toti is making a script that will mount it on boot Maybe most can do just fine without DT, but once you start having a significant number of widgets and a number of programs that can't use the built-in apps2sd, then the space starts to fill up really fast. I'm really surprised at how much space each "regular" app still needs to have in onboard memory with the built-in system. I don't understand why they couldn't do a better job of moving stuff over like DT does. But as long as people can still install DT separately, I guess there really isn't any harm in removing it. Just give those who "must" have it a link and let them DIY. Oh, and one question for people who use the built-in version. When you have the phone in USB drive mode, can you still use the apps on the SD card? I haven't used it enough to know.
Guest Posted January 24, 2011 Report Posted January 24, 2011 (edited) So it looks like the German T-Mobile 2.1 ROM partitioning the /system to 90MB so if you are able to shrink your needed space to under 90MB it sure isnt tragic to go on without dt's a2sd because with 20MB more on /data it would be easier to get along with the given space and built in a2sd. Doesn't anyone know how the partitions are made? So it would be possible to let the /cache partition shrink about 10-15MB... for a bigger /data.... Edited January 24, 2011 by Guest
Guest Richard_Arkless Posted January 24, 2011 Report Posted January 24, 2011 (edited) Maybe most can do just fine without DT, but once you start having a significant number of widgets and a number of programs that can't use the built-in apps2sd, then the space starts to fill up really fast. I'm really surprised at how much space each "regular" app still needs to have in onboard memory with the built-in system. I don't understand why they couldn't do a better job of moving stuff over like DT does. But as long as people can still install DT separately, I guess there really isn't any harm in removing it. Just give those who "must" have it a link and let them DIY. Oh, and one question for people who use the built-in version. When you have the phone in USB drive mode, can you still use the apps on the SD card? I haven't used it enough to know. the thing is google had to move as much as possible that would both make the developers happy and the user, with dtapp2sd with all the apps being on the sd card as soon as you insert it into another phone and reboot all the apps will appear on the phone, however with googles implementation it doesnt move the app but does move the images and stuff like that which the app depends on to the sd card So it looks like the German T-Mobile 2.1 ROM partitioning the /system to 90MB so if you are able to shrink your needed space to under 90MB it sure isnt tragic to go on without dt's a2sd because with 20MB more on /data it would be easier to get along with the given space and built in a2sd. Doesn't anyone know how the partitions are made? So it would be possible to let the /cache partition shrink about 10-15MB... for a bigger /data.... I currently am not planning on optimizing the rom for the german rom but if I do decide to then I will keep you posted, How the partitions are made is by official roms and currently we can not do it ourselves Edited January 24, 2011 by Richard_Arkless
Guest Posted January 24, 2011 Report Posted January 24, 2011 the thing is google had to move as much as possible that would both make the developers happy and the user, with dtapp2sd with all the apps being on the sd card as soon as you insert it into another phone and reboot all the apps will appear on the phone, however with googles implementation it doesnt move the app but does move the images and stuff like that which the app depends on to the sd card I currently am not planning on optimizing the rom for the german rom but if I do decide to then I will keep you posed, How the partitions are made is by official roms and currently we can not do it ourselves Is there a way to (partially) use the odexed-APK's from e.g. the HTC Magic Official Froyo Rom? This would increase the space on /data!
Guest EXBARBOSS Posted January 24, 2011 Report Posted January 24, 2011 Hello everybody! I've have problem with BT file transferring. Device doesn't want to receive files. I've tried Bluetooth File Manager и Astro BT Manager from market and nothing changed. Does some body bumped this?
Guest rulerofkaos Posted January 24, 2011 Report Posted January 24, 2011 (edited) Hello everybody! I've have problem with BT file transferring. Device doesn't want to receive files. I've tried Bluetooth File Manager и Astro BT Manager from market and nothing changed. Does some body bumped this? If you are using Windows, it is a known problem. Edited January 24, 2011 by rulerofkaos
Guest EXBARBOSS Posted January 24, 2011 Report Posted January 24, 2011 (edited) If you are using Windows, it is a known problem. I'm transferring from my another phone (Nokia 5610). It says "Storage Error", but my sd is working properly. Edited January 24, 2011 by EXBARBOSS
Guest totiadrenalin Posted January 24, 2011 Report Posted January 24, 2011 (edited) Maybe most can do just fine without DT, but once you start having a significant number of widgets and a number of programs that can't use the built-in apps2sd, then the space starts to fill up really fast. I'm really surprised at how much space each "regular" app still needs to have in onboard memory with the built-in system. I don't understand why they couldn't do a better job of moving stuff over like DT does. But as long as people can still install DT separately, I guess there really isn't any harm in removing it. Just give those who "must" have it a link and let them DIY. Oh, and one question for people who use the built-in version. When you have the phone in USB drive mode, can you still use the apps on the SD card? I haven't used it enough to know. I was using the build in froyo apps2sd. But I don't recommend this if you wan't to use widgets. Espessial Winamp or etc. But I found the reason why this rom is getting stack from times to times It's about the lowmemory killer. The problem is because of thet the low memory killer is set to kill Hidden apps all lower ranked apps are set to, much lower the moderate. I Can't tell it exact because I'm not at home right now. But simply set it to moderate via a2sd lowmemory-moderate and activate swap or compcache I personally recomend swap over compcache. But if you have low class sdcard, then compcache will be much better solution. set the swappiness somewhere between 30-60. a2sd swappy45 was the best solution for me. And swap partition from 32-128MB. I was using 128, but now I repartition my sdcard and set 64MB swap partition. But it's work good with compcache. But set the up threshol to 45, and use OC for sure. somewhere between 614Mhz-690Mhz. And if you don't care abot the battery live? Well use the 710Mhz whe you play games. But don play games with overclocked CPU while the phone is connected to Charger. Best regards TOTI Edited January 24, 2011 by totiadrenalin
Guest spanner44 Posted January 24, 2011 Report Posted January 24, 2011 One thing I want you guys to consider is whether I should remove dtapp2sd from the rom, the fact is we dont really need it as froyo does have a pretty good one that comes by default as for swap toti is making a script that will mount it on boot I would prefer you keep the dtapp2sd in rather than out, as I have tried it without when I first swithed to 2.2, but always ran out of space after just a few apps installed. Something I have noticed is that so far I have just 11% of my ext space used up with dtapps2sd, but I am now suffering from low memory space problems, so I would imagine that some apps are not moving automatically to the DS card. Is this normal. Also I am still on the last version you did, so what is the easiest way to go onto this version, as last time I did a full wipe, and then reinstalled all the apps, or should I wait until the next version you release ? Keep up the good work.
Guest totiadrenalin Posted January 24, 2011 Report Posted January 24, 2011 (edited) The main reason of the restart during installing apps is because Market app, Market updater, and et.c apps are in the ram, and the devices ram is getting ovrloaded. Kernel panic and chrash. I can confirm that. just look in logcat. Tka a look in /data/anr/traces.txt There you will se what's going on with the kernel, and the DalvikVM. And if you simply perform the a2sd lowmem-moderate. this will make sure that your ram will never get overloaded. So you will allways have at least 30MB of ram available for the Android System. So you will get pretty nice working android Phone (Pulse). And to make sure that some apps loaded in ram will stay there until you stop the process, or some higher priority app take it's place. Simply try it. You just have nothing to loose. The problem is in init.rc In al Kernels kreated for the CM6 Ported rom for Pulse Edited January 24, 2011 by totiadrenalin
Guest Ellia Posted January 24, 2011 Report Posted January 24, 2011 The main reason of the restart during installing apps is because Market app, Market updater, and et.c apps are in the ram, and the devices ram is getting ovrloaded. Kernel panic and chrash. I can confirm that. just look in logcat. Tka a look in /data/anr/traces.txt There you will se what's going on with the kernel, and the DalvikVM. And if you simply perform the a2sd lowmem-moderate. this will make sure that your ram will never get overloaded. So you will allways have at least 30MB of ram available for the Android System. So you will get pretty nice working android Phone (Pulse). And to make sure that some apps loaded in ram will stay there until you stop the process, or some higher priority app take it's place. Simply try it. You just have nothing to loose. The problem is in init.rc In al Kernels kreated for the CM6 Ported rom for Pulse My experience is that the lowmen-moderate setting "disable" the multitasking. It can hold just a few apps in the RAM.
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now