Database Info

setting device to load on startup

So I've installed the older version of the camera drivers in order to fix a camera issue I'm getting with the 7201 CPU. Right now, I need to manually go into the task manager -> Devices -> start CIF1.DLL every time my phone is restarted, otherwise the camera won't initialize.
Short of cooking the old camera version into the rom, is there a way I can get the camera to load automatically?

did you install this using a cab? what camera cab did you use? did you just flash a new rom? if so, might be your radio
Lupe

overhaulengines said:
did you install this using a cab? what camera cab did you use? did you just flash a new rom? if so, might be your radio
Lupe
Click to expand...
Click to collapse
radio can't be issue because camera does work; he doesn't want to manually load the file for the camera every time he restarts his kaiser.
I never had this issue of having to start the camera manually. On xda live 3.0 the camera application is taken out but installation via cab makes it work without problem ...
search for "kyphur xda live 3.0"; that should bring up the thread for that rom. In the thread download the file that kyphur has on his 4shared account which includes things he removed from rom. In that zip file there are two different files for camera.
Try that and see what results you yield.

Can't you just put CIF1.DLL in to Windows/startup folder?

Thanks for the replies. I realized I should have been a bit clearer.
Ok, so I went back and looked at what I was loading and the file is called SJ CIF_314.CAB It's not the camera, but a device or driver that the camera uses. If I install this cab, but don't manually load it in the taskmanager, the camera won't initialize.
I'm loading this cab to address an issue my camera has when recording video (has to do with the 7201 CPU). You can read the details of this solution here:
http://forum.xda-developers.com/showthread.php?t=387057
Basically, because of my CPU, any of the roms cooked with the TYTNII PhotoQuality.cab fix seems to cause recording problems on my video camera. So to fix this, i need to install the SJ CIF_314.CAB.
So there is no issue with the camera after this device driver is loaded. But I need to load it manually each time my phone is reset.
When I go into task manager to find the device in the devices list, it is listed as $device\CIF1(CIF1 and it is unloaded. I just have to highlight and start it to get my camera working each time. In the registry it is linked to the file CIF.DLL
I'm basically asking if there is a way to get this device to load automatically like most of the other devices in the devices list. Like maybe changing or adding something in the registry?

so anyone know how to do this?

anyone have a resolution for this? I want to see this resolved as well heh

i have the same problem - anyone figured out how to fix this so the driver loads automatically on startup?

what i find strange is (i dont mean anything mean by this) it seems like Junior members are the only one with this issue. these days cooking a rom is simple with the kitchens out there i would just cook the drivers in and be done with it. also seems like that .cab might be messed up a little if its not over writting the "newer" driver no?
also all the wm6.1 roms have camera fix built in before the cooks touch it so its not like we are doing this on purpose sorry

yes it certainly looks suspicious that this happens only to junior members.
but, i had this problem after i loaded dutty's wm 6.1 rom, messed around for a day looking for the best radio rom (had issues like carrier signal dropping and coming back every 5 seconds, black screen camera and video camera).
i am not yet at the stage that i want to cook my own rom, so this issue is not a result of a junior member's rom, but rather playing with other roms which seem to be highly recognized in this community, and other strange behavior (ie locking up the device - found a fix for that today as well).
having said all that, do you know how to override boot settings so a driver is automatically started after every reset?

Advice for porting a rom from one device to another

Hi all,
I'm reaching out to the Android community as a whole hoping to get some pointers. I'm having a hard time finding the information I need here and by googling (although I'm sure it exists) so I was hoping to get some tips or pointers from some people in the know. I've reached out to a few people privately who I know have already done this kind of work but no one is responding to me which is kind of a bummer.
While I'm specifically trying to port the latest Incredible OTA to the EVO, I'm hoping any information gathered here will be helpful to others and applicable to other devices.
Why port the Incredible rom to the EVO? Well for starters the hardware is virtually identical from what I can tell, so it's a good starting point to teach myself some basics and get familiar with Android and rom construction. Second, it's to solve a strange MMS problem for EVO users on Cricket and MetroPCS. We can't send MMS using Sprint based roms but can with Verizon based ones, or by putting the Verizon MMS app on our Sprint roms, but it doesn't work properly. Some people are looking to disassemble the MMS app and figure out what it will take to get it working properly on a Sprint rom. I'm attacking from the other direction (since I have seen it work with the avafroyo vcrc3 rom) by taking the entire Incredible rom and making it work on the EVO.
So my starting point was to install a copy of the latest rooted Incredible OTA on to my phone and then install the latest EVO kernel from HTC. This definitely got me up and running, however I could not use the hardware buttons below the screen (VERY difficult to do anything on the phone lol) and also quickly found out that the SD card was not being recognized either.
I think it was about this time that I found the Android Kitchen that had support for both the incredible and the evo, and starting using that instead of my entirely manual way.
I found that to fix the hardware buttons below the screen I just needed to remove the incredible-keypad.kl file from /system/usr/keylayout and replace it with the supersonic-keypad.kl file from a EVO rom. Maybe renaming the incredible file would have done the trick? Is the kernel somehow looking for a file by that name? I have no idea how this works and would love some explanation.
So now that I had the buttons working I was able to freely navigate the phone and find what else didn't work. It seems that all thing related to the BCM4329 broadcom chip are not working, which means that there is no wifi, there is no bluetooth, and there is no FM radio. All of these features produce errors or don't work within any applications that use them or attempt to turn them on. The SD card was not being recognized so I couldn't read or write to it. Also screen rotation is not working.
Since I'm interested in preserving the apps and framework from the Incredible verizon rom I stayed away from the /system/app and /system/framework folders and looked in other places. I found that bin, etc, and lib folders also look virtually identical between the two roms except for a few minor differences. These also appear to be mostly drivers and stuff. So what I then did was merge the two versions from each rom and replace duplicates with the EVO versions. After this I found that I had proper SD card access again and I know GPS is working as well (no clue if it did before or not).
So at this point I have a rooted Incredible rom running on my EVO with the verizon incredible apps and framework. GPS, 3G, buttons, USB, sd card all work, however still no wifi, bluetooth, or fm radio. It's all this one BCM4329 chip. The drivers and related files all seem to be the same. The incredible and the EVO both use the same chip from what I can tell. I don't know where the breakdown occurs now. Is it in the framework or app? Is the support for the wifi and stuff built directly into the kernel? I've noticed during repacking of the boot image that there seems to be a driver in there for the broadcom chip.
I found a sensor file in the /system/lib/hw folder called sensors.inc.so. I copied over a sensors.supersonic.so file from the EVO rom and also renamed a copy to sensors.inc.so just in case. This hasn't helped with any of the rotation though. It seems like the contents of /system/lib are almost identical between the Incredible and EVO roms and these seem like they're all hardware drivers.
Anyone have any input towards getting screen rotation and the wireless stuff working? I feel like I've made decent progress literally replacing stuff, but I've either replaced too much, or there now needs to be some real editing somewhere, or something.

The bug of motorola's (android?) camera

I'm using my second android phone and I found that I'm dealing with the same problem as in my old phone again : Sometimes the camera just refuse to save the photo take and the gallery app doesn't show the right photos. Today I found what it may be the cause : there are some files with lots of dots "." in the filename making the system (camera app) confuse. There is no such problem anymore after I deleted/renamed such files. If you got the same problems, you may check it out.

[Q] Query on what to do after rooting HTC ChaCha (Noob Alert)

I've been having this phone for a year, and I've finally had the guts to go ahead and root the phone. I now have super user application. I have also installed Link2sd and linked all the big apps to a separate ext2 partition in my SD.
My question is , now since I've rooted this, what all options are there for me to explore and try out, in making this phone better. I've seen about various Cyanogen Mods, CM 7, CM9, CM10. But they all seem to have some issues. But sometimes even simple issues may be blown out of proportion. I just need some feed back on how bad the issues are, or how good the mods are actually. Basically I want to know if the impact of these certain issues will hinder me in enjoying my android experience. And i couldn't think of a better place to put these questions to.
Summary:
1) What options are present to make my device better, now since I've rooted it?
2) What kind of serious issues are there with the CM versions, and whether i can enjoy the phone despite these.
PS: One more thing. in Link2SD , despite linking those Apps to the ext partition, the internal memory only has 75 MB left, and some portion of it is reduced everytime I install a new app. is it a bug, or I've done something wrong?

I was afraid of rooting first too, but now that I rooted it, it totally worth it. First, I installed hexgore's stock plus rom with some modifications and used it for almost a year, then I decided to try out cm9. It was a lot better, and had almost zero problems (everything was working except the front-facing camera). Yesterday I installed cm10, and it is even better than cm9 I recommend you to install cm 10.
For making your phone better, you can install One Power Guard, Total Commander (give it root permissions instead of java), Cache Cleaner and Super Backup. These are the rooted apps I use/have used in the past.
Your "problem" with link2SD is not a bug, it is how it is supposed to work. It links the apk, the dalvik-cache and the cache, but it does NOT link the app's private data, which then is stored on your phone's internal storage. And that is taking up space.
Have fun with your rooted chacha!

Thanks
Thanks for your suggestion, I have decided to give CM10 a shot. Now, can u please send some link of a guide to follow, in order to flash CM10 in my HTC ChaCha. Also, a guide to revert back to the current ROM in case I fall into some issue with CM10.
Also, I wanted to know, is there any improvement in the battery? Mine is a year old and lasts for about 11 hours max. Anything that can improve this would be of great help.
I had earlier gone through a post on modifying a system file with a # sign in front of a line which makes the battery better, but I was unable to figure out how to edit a system file(I've located it using Astro file manager).
And I cant post there, since the forum rules say that the user must be at least 10 posts old to post in the dev section.
Any help is deeply appreciated.
Thanks in advance

Issue with backlight and prediction
archacha said:
I was afraid of rooting first too, but now that I rooted it, it totally worth it. First, I installed hexgore's stock plus rom with some modifications and used it for almost a year, then I decided to try out cm9. It was a lot better, and had almost zero problems (everything was working except the front-facing camera). Yesterday I installed cm10, and it is even better than cm9 I recommend you to install cm 10.
Your "problem" with link2SD is not a bug, it is how it is supposed to work. It links the apk, the dalvik-cache and the cache, but it does NOT link the app's private data, which then is stored on your phone's internal storage. And that is taking up space.
Have fun with your rooted chacha!
Click to expand...
Click to collapse
Heyy!
I took ur advice and installed it, and there is almost no problem for me, I never use much of the front camera anyway. The thing is, the Keyboard backlight doesnt work when the brightness is on automatic. is there a work around?
Also, the prediction, as I mentioned in another thread, does not work good. there is no prediction as a matter of fact, no options come out for me to select.
One more thing is that I am unable to see a list of users to select from that and send messages to. I have to type in the name of each user and add it manually. Any work around or apps available to solve it?

[Q] Issues with .RAW Camera Setting in SlimKat Unofficial 2.3

Sorry if this should go in the SlimKat forum, but I figured it is a 4.4 issue, possibly not specific to SlimKat.
I was messing with my camera settings the other day taking some photos, and I came across the option to change from .jpeg to .raw. I changed to .raw hoping to review later and see if I could improve the photos. I took several photos in .raw format, but now I cannot view them. At first they appeared as just gray boxes in the photo gallery (which was my first clue), and then I thought i would just transfer them to my computer and i would view/process them there.
However, I am completely unable to view these photos. I have installed RawDroid on my phone, but it will not view the files (actual or thumbnail). I have also tried several different programs on my Windows 7 PC (File Explorer, Corel Paintshop 6, Paint Shop Pro, and even Irfanview) - none of them will display the photos. I know there is data there - each file is about 10.2MB in size; I just can't get them to display no matter what I try. I am extremely disappointed because there are at least 4 of the files that I would really like to keep.
Any ideas on how I can get the photos to display? I have searched Google and the forums here to no avail. I cannot seem to find anyone or an article on this particular issue.
And, as I said, my apologies if this should go in the SlimKat forum - Mods, please move if necessary.
-Mark
AT&T HTC One X
Rooted and S-Off
SlimKat 4.4 Unofficial Beta 2.3
Slim Gapps