The Cyanogenmod port for the Defy also works with the Bravo. The only thing not working is the camera. Other than that it is very smooth (especially when overclocked to 1.2ghz) and I have experienced no bugs whatsoever yet.
Anyways, I thought someone over here might know how things work a little better and I was wondering what parts in the phones files are needed to be replaced or changed for the camera to run? Do we need to compile some camera libs over? Which ones? Edit some xmls where in the phone? And paste what part of the build prop from the original 2.2.2 stock blur rom to the CM7 rom?
This all may sound very specific, but any suggestions will help. These phones are so similar we may almost be able to share work. The only difference between these phones compatibility with roms wise is the camera and the carrier. The problems that have arose from the different carriers have been fixed easily. The only problems that remain is the camera.
Thanks in advanced for any suggestions
Related
I'm flashing different ROMs every time, and I've noticed that gps fix is really slow in some of them. I'm always using the same radio (54) and RIL and the same gps.conf file, but there's still a lot of variation between different ROMs. Is the kernel also related? Or maybe other files from the ROM?
No ROM is as good with gps as Redux... but I like CM tweaks so any help will be much appreciated!
Thanks
Go to app market and download
Fasterfix
Sent from my HTC Runnymede using XDA App
Thanks, I'll give a try, but don't think it's going to help me, and that's not the answer I wanted (I don't want to be rude, I just don't know the best way to say it)
I mean that I want to know what affects the ggps performance, as with the same radio, same kernel, same RIL and same gps.conf (this file is the one that fasterfix changes) I have worse performance in different ROMs.
Thanks anyway for your help
Are you changing the RILs Yourself?
Yes. I'm using 1.001, but I always try first without changing the RIL, and seems like there is no difference
OK. I was just going to say that The RILs that come with the ROM may be better, thats all.
But Yes, Kernel, ROM, Radio, RIL can all affect it.
and what more...?
Maybe some drivers on the ROM? (I thought they are all the same and can not be tweaked)
Too bad ihlades has left the forum leaving so many secrets unrevealed (as the gps performance or the cool multitasking panel)
Yeah its a shame, I would have loved to see his sources for the Multi-task
In the ROM, possibly:
/etc/gps.conf
/system/lib/hw/gps.bravo.so
/system/lib/hw/gps.goldfish.so
Not sure what these are but the name looks quite self explanatory:
/data/misc/rild_agps.feature
/data/misc/rild_agps.mode
Thanks, I'll make a nandroid and try changing those files for the Redux2 ones.
If that doesn't work, I'll assume that the chaos theory is operating under that.
May or may not work. Libs generally have dependancies during the compile process so often hot swapping them doesn't work.
Best of luck!
Well, this is mad.
I looked into Redux and I didn't find the gps.goldfish.so , so only replaced gps.bravo.so. Same performance
Then I thought "Well, let's try leaving everything just as on Redux2" I deleted gps.goldfish.so and now I have much better performance.
Im happy now, but if someone with development knowledge can understand what has happened, I hope it'll be useful for more people.
In my ROM, I must have these two files gps.conf & SuplRootCert which help a lot with GPS locking. Attached here, but this is for Malaysia. Maybe you can check the SuplRootCert on why it helps the GPS reception for my ROM.
OK, so i've been running a few different ICS roms and i notice that most have issues with VoiceSearch (or the mic in general in anything outside of a phone call) and obviously they all have issues with the camera.
I'm not too experienced but i know it has to do with the /system/lib or rather the libraries for ICS and lack of support from qualcom and htc. Is there any way to bring over the GB Lib (and even the GB Cam) into ICS?
I tried messing with it a bit myself but with no luck. I also notice ICS has a lot more files in /system/lib/hw that don't even exist in GB. Is this because ICS is using more "hw" (hardware) decoding so there are more "hw" libs?
Any answer would be greatly appreciated. Not looking for anyone to solve my problems, just let me know if you think it's possible
Ah crud, thanked instead of quoting.
Anyway, that would probably not work as these are two completely different operating systems. They have different frameworks, hence different libs, hence why it will not work.
perhaps for camera, but i've read of people doing it for the mic.. which is why i was curious. Actually 90% of the libs seem the same, its just the ones in /hw that seem to be the most diff
The andromadous v12 seems to have a working mic for voice search and other apps like shazam same with quattro these are the only 2 roms I came across that had the working mic
All of the lib files tell the hardware how to interact with GB, we need files that tell them how to interact with ICS. Its hit or miss what will work and what won't as some things in ics work the same as GB but others (camera, mic, videorecprding) don't. So don't expect support for devices like the G2 which htc has no plans on updating to ICS. Our best bet is to wait for another official release of some other phone that has similar enough libs to work. Imho
Sent from my HTC Desire Z using Tapatalk
The similar threads weren't of any help on this issue from what I could tell, and I'm sure it's something that's a straight forward answer, but I really just wanted to know if there's any way to fix my camera on my G2. The issue I'm having is that while using the Un-Official CM9-RC2 build I'm having serious issues with the camera taking a bit low quality images from time to time, as well as being unable to scan in bar codes due to the fact that it's unable to auto-focus, or even focus on anything for that matter.
If more information needs to be provided, I'll be glad to. I don't consider myself an expert on Android development, so excuse me for this question. Thanks!
Wolfy9247 said:
The similar threads weren't of any help on this issue from what I could tell, and I'm sure it's something that's a straight forward answer, but I really just wanted to know if there's any way to fix my camera on my G2. The issue I'm having is that while using the Un-Official CM9-RC2 build I'm having serious issues with the camera taking a bit low quality images from time to time, as well as being unable to scan in bar codes due to the fact that it's unable to auto-focus, or even focus on anything for that matter.
If more information needs to be provided, I'll be glad to. I don't consider myself an expert on Android development, so excuse me for this question. Thanks!
Click to expand...
Click to collapse
First of all you are on an unofficial cm build so you should no get every thing working perfect, try clearing camera data in settings if it does not help
then its certainly your rom but also try clearing cache if it still does not go then maybe you have to change the rom, there are many roms that have camera working in good shape check the developer section an un-official CM will not help always read the details of rom before downloading them every rom has its good and bad so its your choice looking at the kind of roms here i dont think CM is gonna help some dev use them as a base to build stable roms try those
you can try andromadus audacity or mimicry ics and for sense try gen y visionx there are sooo many good roms out there why stick to un -official ones HOPE I HELPED
strip419 said:
First of all, you're on an un-official CM build so you shouldn't get everything working perfectly, however I'd recommend clearing the camera data in your settings if it doesn't help. If that doesn't work, try clearing the cache. If those don't work, it's most certainly your ROM, and you should maybe considering switching to a ROM that has the camera working in good shape. Check the developer section, an un-official CM will not always work, so read the details of the ROM before downloading them to determine whether it's good or bad.
You can always try Andromadus, Audacity, or Mimicry ICS and for Sense you might try gen y visionx. There are so many good ROMS out there, why stick to the un-official ones? Hope I helped!
Click to expand...
Click to collapse
(The quoted post was edited for more clarity and understanding while I was trying to read over it.)
The camera app doesn't have any cache, I did clear the data but the problem still persists. I'll consider using another ROM, however I do believe it's mainly the camera drivers for ICS for G2 that are just rubbish at the moment though. I was mainly seeing if anyone had any fixes or recommendations besides just switching.
Wolfy9247 said:
(The quoted post was edited for more clarity and understanding while I was trying to read over it.)
The camera app doesn't have any cache, I did clear the data but the problem still persists. I'll consider using another ROM, however I do believe it's mainly the camera drivers for ICS for G2 that are just rubbish at the moment though. I was mainly seeing if anyone had any fixes or recommendations besides just switching.
Click to expand...
Click to collapse
You're right, the quality won't be as good in ICS as it was in GB. I can't say the same for JB, but for ICS we need(ed) major changes/rewrites to the camera drivers in general.
Developers tried tirelessly to get the camera codes from Qualcomm, not sure they gave them out so the dev had to work around it. But some sense ics roms have very good camera quality and HD video . I am on gen y vision X you can try that
Sent from my HTC Desire Z using xda premium
Just wondering if anyone has figured out why the camera on aosp Roms focuses for some and not for others. I've had the problem right from the very first aosp flash I did. Maybe a full data wipe and adb side load would help? I know there's a script work around but it doesn't make sense that it works for some and not others. Not to me anyways. But great job on the Roms. Really liking them and thanks.
bowhunt2005 said:
Just wondering if anyone has figured out why the camera on aosp Roms focuses for some and not for others. I've had the problem right from the very first aosp flash I did. Maybe a full data wipe and adb side load would help? I know there's a script work around but it doesn't make sense that it works for some and not others. Not to me anyways. But great job on the Roms. Really liking them and thanks.
Click to expand...
Click to collapse
The problem exist because of the differences in the Nexus 4 camera and the one in our phone. Because LG hasn't released open source drivers for our phone's camera (and/or doesn't see the monetary benefit in supporting 3rd party development) LGOG developers appear to be stuck using and trying to adapt the software from the Nexus 4. The camera will focus during the first launch of the camera apk then be unable to focus until the process is killed completely and restarted.
Those who are reporting that their camera works just fine in an AOSP ROM are one of the following: Those who have applied the kill / relaunch script, those who only tested their camera on first launch, or those who are so accustomed to crappy phone cameras that they consider anything greater than a completely blurry mess to be "in focus."
I often wondered if it was really working for some. But thanks for the info and I guess I will just try to stay patient. Hopefully there is an improvement soon. The camera takes great photos on lifeless but I really like the aosp Roms.
Hey guys I'm a little sad :/
As many of you would know G3 camera support on AOSP is in a really poor condition.
The driver made by LG isn't present on AOSP, making it an utter disappointment after you get over the thrilling speed compared to LG's own rom.
I know the G2 camera has been ported, I also found a post requesting a port for G3 (last response in october), but that didn't happen.
I don't know in detail how hard the problem is, but I imagine that it should be doable unless of course this is completely proprietary code by LG.
I am imagining that you could simply move the right apk's to the phone and try out if something will work, unless of course it is in the LG kernel itself, but then maybe an LG kernel could be used with AOSP, who knows.
The guy who is working on LG XCam for both the G2 and G3 already said he will focus on LG's own roms, so that a no go as well. I have really been looking, but nothing seems to be up.
So is anyone working on this and does anyone know in detail how hard it is to solve?
Coming from Nexus 5 with SlimKat on it, LG G3 seems like the slowest thing known to man, haha, so AOSP is a must, preferably with a good camera as well.
1 moving some files wil not work start by understanding how a total framework works.
2 ya you can do kernel but do you know how it works with driver and app .
3 if you love the cam so mutch why not build a rom with lg framework ?
Jhinta said:
1 moving some files wil not work start by understanding how a total framework works.
2 ya you can do kernel but do you know how it works with driver and app .
3 if you love the cam so mutch why not build a rom with lg framework ?
Click to expand...
Click to collapse
1. I don't think the whole framework needs to be understood to port the functionality of the camera
2. No I don't, but I think the kernel is actually containing the driver, if I understand how a Linux Kernel works, but I could be wrong, since I don't know for sure on Android. Furthermore I was thinking both (parts of) the kernel and camera app could be applied to AOSP.
3. It's not the camera app or LG framework, it's the fact that the camera does not work properly on AOSP. I don't care about settings, GUI or functionality, but it simply performs like a phone from 5 years ago with 15 fps video and poor colors and constrast in images.