Database Develop

Best Settings??

Hello All,
Have just started using this forum and failed to introduce myself previously, my name is Jay; I am 27 from DC but in Afghanistan for a few more months (yea..sucks) new to rooting, flashing and all that but I have recent interest in it and it passes the time better than most thing we are "allowed" to do over here.
I just switched from a HTC Desire to a Galaxy Captivate
So far...I have unlocked it (via cellunlocker.net), upgraded to the leaked 2.3.4 Gingerbread, Rooted using the 10step method posted here, Installed Victory v1.5 Rom, tried flashing Talon kernel but bricked the phone and had to redo the above...
My question is to those more knowledgeable than myself with all this...what is the best Kernel, Rom, Modem...whatever else...that I can have on this device to keep it running smoothly, fast and reliable?
I do all the basic call, txt, surf...play games, watch movies, use apps, etc...not a developer but want my phone to be tweaked as much as possible so it does not seem outdated or lag with new things being added.
My current settings are:
Baseband I897UCKH3
Firmware 2.3.4
Kernel 2.6.35.7-I897UCKH3-CL461307
Build VictoryRom_v1.5
There is nothing wrong with the phone...as I said above, if I could do more to it and have an overall better device and pass some time here I would enjoy that. Victory seems great but all I notice myself is the battery indicator has changed and...thats about it (a lot likely goes unnoticed by me)
I do have one problem with the phone that maybe a different modem can fix? (I hope) for some reason my GPRS will not work out here with my browser...I can use the market and apps that connect to the internet but my browser seems to be WiFi only. I have changed the settings from usa to europe since I am using a sim from over here but no luck...and added the gprs settings to the phone which allowed apps internet access but zero for browser..any ideas?
I really thank anyone who takes the time to reply...I am sure teaching a new person in this is annoying just as showing the new guy here how to clean his weapon...lol...but we were all new at everything once and I thank you all for reading my novel
-Jay

Jay,
Thank you so much for your service and contribution to our freedom, I know it must be hard to be away from the life you once knew. Hang in there It's not for nothing. Hopefully someone will be able to help with your GPRS settings. I am running the same setup on my captivate only I have used Boogs kernel to install clockwork recovery as well. You can flash boogs kernel over the kernel you have now and that will let you flash roms or speedmods later. If I were you I'd keep my eyes peeled for GPRS settings in your area and wait for EXT or speedmod kernel for the 2.3.4 They are saying RFS is pretty quick to begin with though. It may be hard to beat but im sure one of these great Devs will figure out a way to make 2.3.4 smokin fast. Once again thanks for doing what you do. Keep your head down Soldier!
Steve

If you like using your mobile providers Net, you might give I9000 ports a try. They allow for better Upload speeds but you will sacrifice Audience chip support (noise suppression processor that only I897 have). Also since I9000 source usually drop first they have all sorts of kernel mods like Voodoo sound, Voodoo color fix, BLN, init.d files tweaks like V6, among many more. Sadly I897 native roms always play catch up with I9000's.
Personally I prefer native rom, because they tend to run smoother for longer periods of time (I9000 tend to slow down over time on my phone, but thats just my experience) and I don't use ATT's network a whole lot (90% of the time I'm around a wifi connection) and I like the audience chip, it is a phone before anything else.
Edit: Also there isn't a "best" rom, kernel or modem. Each rom has their own pros and cons, same as Kernels. And no 2 phones are the exact same so not all of them take well to all the tweaks, mods, etc. And most of the time i9000 kernels wont work with i897 roms, at least in GB.

[SELFKANG AOSP ROM] CyanogenMod 7.1 GSM Version [UPDATE 10/23 AM]

I was sent this by XDA user: coreless88 who asked me to post this in the dev section (he doesn't have enough posts yet).
** WARNING: I HAVE NOT TESTED THIS PERSONALLY -- USE AT YOUR OWN RISK -- KEEP A BACKUP HANDY **
** THIS ROM IS INSTALLED WITH SAFESTRAP BOOTSTRAP. DO NOT USE KOUSH'S BOOTSTRAP OR YOU WILL SOFTBRICK YOUR DEVICE **
I dabbled in files for some time, twaked the build.prop a little (added some generally known hacks into it for faster touch reaction, better HSPA reception etc.), and added some files .lib/.ro files from Droid 2 Global.
It all worked out nicely. However, as I cannot use a CDMA network (I live in Turkey, so I have only GSM access), I cannot guarantee this will work with CDMA too. I will appriciate it if someone can test it.
Also, Your GSM card will be recognized instantly, but you need to activate the 3G network form the settings, you will need to add your APN manually, atleast in my case I had to put my carriers APN into the list, so this might not be necessary."
Here is the link: http://www.mediafire.com/?d17l4z4885ph4ov
Thanks needs to go to Hashcode, as I just modified and added a missing feature to it.
Click to expand...
Click to collapse

Thanks for the help Hashcode!
I got my clearence to Dev forums, so I will try to contribute even more to this community =] .
First of all, as in my quote in the first post, I cannot guarantee this will work in CDMA network, Hashcode will inspect the files and try to integrate the GSM feature to his original release.
You can find a screenshot of my phone working under the GSM network and 3G enabled.
!!!However, just like any other custom rom, I cannot accept any responsibilities if this rom bricks your phone. !!!
For installing, just use Hashcode's safestrap, for the rest i think you know the drill.
BUGS:
Videos dont run,
Sound is low,
Bluetooth is broken,
Camera is broken,
Also be aware, notification and ringtone sounds are silent by default, you just need to go to settings menu and choose a ringtone for yourself =] .
Edit: Also as I have only 1 Droid 3 at the moment, I need as much testers as I can find for checking if this works for all Europe SIM Cards.

Referved for future use/updates/etc...

Awesome, very thanks to both Hascode and Coreless88
All work fine in france the signal bdm hspda is very good, than the xt883 rom. Exept the camera all work fine for me.
I'm test, if you want, all other release in france, on bouygues telecom.....

thank YOU !! Hashcode and Coreless88

No thank you guys, for trying it and giving me an easy breath as it is my very first development attempt!
nikeusfr said:
Awesome, very thanks to both Hascode and Coreless88
All work fine in france the signal bdm hspda is very good, than the xt883 rom. Exept the camera all work fine for me.
I'm test, if you want, all other release in france, on bouygues telecom.....
Click to expand...
Click to collapse
Also I forgot to mention, my tweaks and Cyanogen codes makes GSM reception and HSDPA signal is much more improved than the stock XT862 Rom.
Right now bluetooth doesn't work, but GPU and CPU working properly, if not better than before.
Here are some more screenshots, for Quadrant, SpeedTest, and A Samurai Vengance 2 (BTW Game runs incredibly smooth).

one another bug, i'haven't delivery report on sms/mms, there's no sound in the build speaker when i phone or receive call, and the sound is very quiet in the speaker phone or handset.

nikeusfr said:
one another bug, i'haven't delivery report on sms/mms, there's no sound in the build speaker when i phone or receive call, and the sound is very quiet in the speaker phone or handset.
Click to expand...
Click to collapse
Hi,
First of all, thanks for your input. I need your opinions to make this better. So here we go,
All notifications and ringtones are silent by default.
You need to get to:
"settings>sounds>ring tone/notification tone" menus and choose your ringtones from there.
Sounds are in this built generally low, because there isn't any proper sound resources prepared with OMAP 4 series of SoC's. I will try to enhance them, but I will need time.
But you can make the phone louder on the speaker by going to:
settings>cyanogenmod settings>sound menu then choose the settings you like the most.

What "general" GSM build.prop tweaks are we talking about here?

DoubleYouPee said:
What "general" GSM build.prop tweaks are we talking about here?
Click to expand...
Click to collapse
Hi,
I've added Tweaks for getting stronger reception, making the GSM default network at the boot, tweaks for faster response, etc... You can download the file and look at the system>build.prop (open it via wordpad if you are on windows) and compare it to Hashcode's build.prop.
BTW I am experimenting with audio and video files right now. Post I will post the results when I finish the testing.

Could I apply these build.prop changes my XT862 rom?
Or did you use droid 2 global hacks like someone tried before?

DoubleYouPee said:
Could I apply these build.prop changes my XT862 rom?
Click to expand...
Click to collapse
Why not, this is a free world, and as long as you know what you are doing you will be safe, but if you're not...
Be aware, "build.prop" is a very risky file to touch, and has a central role for the Android to run correctly. I had to use RSD to get back to original software because I stuck at the Motorola logo after some changes. So I took the hit for you allready =].
My advice, directly flash this rom and don't do any editing. Because I did not just edited the build.prop, also added several library files, done a lot of testing, finded new libraries or edited them to make it work.
It will include lots of time, effort, patience and hell of a risk.

coreless88 said:
Why not, this is a free world, and as long as you know what you are doing you will be safe, but if you're not...
Be aware, "build.prop" is a very risky file to touch, and has a central role for the Android to run correctly. I had to use RSD to get back to original software because I stuck at the Motorola logo after some changes. So I took the hit for you allready =].
My advice, directly flash this rom and don't do any editing. Because I did not just edited the build.prop, also added several library files, done a lot of testing, finded new libraries or edited them to make it work.
It will include lots of time, effort, patience and hell of a risk.
Click to expand...
Click to collapse
Well I would love to use this mod, but because:
Videos dont run,
Sound is low,
Bluetooth is broken,
Camera is broken
I'd rather have a GSM-fix for the my current ROM, (kinda like XT883, but then easier)

DoubleYouPee said:
Well I would love to use this mod, but because:
Videos dont run,
Sound is low,
Bluetooth is broken,
Camera is broken
I'd rather have a GSM-fix for the my current ROM, (kinda like XT883, but then easier)
Click to expand...
Click to collapse
Oh!
I completely misunderstand you, I thought you were asking about Hashcode's Cyanogen release. You cannot use these fixes for Motorola roms or any rom that based on a Motorola rom. These fixes and libraries are only for Cyanogen builds, at least thats what I think, as I don't have any development experience with any Motorola rom.
You may try, but that will only make the risk even bigger.
Please be patient, I am trying to fix camera and sound problems right now, and I will try to fix bluetooth in a later date, as I didn't see anyone using bluetooth for ages =] .

Giving this a whirl on my xt860 right now, will edit this post with results. Very nice fellas, thank you both very much! Just want to make sure, this is built for Hashcodes safestrap?
Seems to be doing the same as previous on my bell phone, loops on the first screen, I'm not getting to the boot animation.

coreless88 said:
Also I forgot to mention, my tweaks and Cyanogen codes makes GSM reception and HSDPA signal is much more improved than the stock XT862 Rom.
Click to expand...
Click to collapse
Yes, as I wrote elsewere looks like the wrong signal measurement is a purposely limit introduced by verizon request.
On D2g is the same, the Cyanogen rom, with the same radio have the correct measurement, the XT883 too.
So could be interesting to understand where that three bars are lost and if a quick fix for the stock ROMS could be possible.

Willis111 said:
Giving this a whirl on my xt860 right now, will edit this post with results. Very nice fellas, thank you both very much! Just want to make sure, this is built for Hashcodes safestrap?
Seems to be doing the same as previous on my bell phone, loops on the first screen, I'm not getting to the boot animation.
Click to expand...
Click to collapse
Hi,
Your thanks are appriciated, and I am sorry for this rom also did not worked for your XT860 =/ . I guess Motorola did everything they possibly can to protect their region based software versions.
I guess the fix will be simple, but I am afraid either Canadian Android developers are rare (BTW I don't think so), or they don't want to develop for / they don't have this device.
The Solutor said:
Yes, as I wrote elsewere looks like the wrong signal measurement is a purposely limit introduced by verizon request.
On D2g is the same, the Cyanogen rom, with the same radio have the correct measurement, the XT883 too.
So could be interesting to understand where that three bars are lost and if a quick fix for the stock ROMS could be possible.
Click to expand...
Click to collapse
Indeed, It seems low GSM signal was the goal for them. Either for the purpose of making the Verizon "look like" superior to European Networks, or just for making it a Verizon semi-exclusive and a pain in the ass for any other carrier.
The problem is the Verizon's firmware itself, for example, even the non-US devices (XT860, XT883... you name it) are listed by "cdma_solano" in the build.props, and while those files are filled with CDMA codes, there are hardly more than 6 lines of GSM related codes. So my simple tweaks does nothing to improve the signal (tested/proven).

coreless88 said:
Indeed, It seems low GSM signal was the goal for them. Either for the purpose of making the Verizon "look like" superior to European Networks, or just for making it a Verizon semi-exclusive and a pain in the ass for any other carrier.
Click to expand...
Click to collapse
Indeed this is the only reasonable explanation, the same behavior in five ROMs can't be a bug.
The problem is the Verizon's firmware itself, for example, even the non-US devices (XT860, XT883... you name it) are listed by "cdma_solano" in the build.props, and while those files are filled with CDMA codes, there are hardly more than 6 lines of GSM related codes. So my simple tweaks does nothing to improve the signal (tested/proven).
Click to expand...
Click to collapse
Maybe is omething hardcoded in the libril or whatever in the userland, surely is not the radio itself.
XT883 is not affected, so we should try to replace some piece to spot the culprit, BTW this process would be easier when the bootstrap will be fixed to work on XT883, (why doesn't work on that rom is a another nice mystery).

Indeed, a GSM ROM would be great

FYI, audio and video codec issues are being addressed in my next build of CM7.
I'm going to give the GSM ROM a test drive and see how the CDMA stuff is affected. As well as look at the differences by file.
Hopefully, i can incorporate coreless88's changes back into the main ROM so that we don't end up with 2 CM7 ROMs (CDMA and GSM).

911 and e911 explained

Personal background: Associate degree in Laser Electro Optics. 12 years research and development semiconductor manufacturing, 15 years as an EMT, last 10 years as a 911 telecommunicator for Austin-Travis County Emergency Medical Services. 6 of those years as a Training Officer.
The reason for my (cough) resume is so everyone understands I have the technical background and experience to explain the differences between e911 and 911.
Public Safety Answering Point: the local organization tasked with answering emergency request phone calls and dispatching appropriate emergency resources. PSAP's are broken into two types, primary and secondary. The primary PSAP is typically the local police department for city's and the local sheriff's department for unincorporated areas. Some colleges have their own police department and may have their own PSAP. So realistically a person can connect to a different 911 call center depending upon their location within a small geographic area.
Large urban areas typically have secondary PSAP's. The secondary PSAP usually consists of public safety departments not related to law enforcement such as fire and/or emergency medical services (ambulance services) specially trained to send request specific resources dependent upon the emergency. In Austin and Travis County we run 120 thousand EMS 911 calls per year. The police department takes about 2000 911 calls per day.
911: a simple to remember phone number nation wide allowing everyone access to emergency services. No location information is transmitted or received. The PSAP is responsible for determining location by interrogation of the caller. This can a problem if the caller is altered or otherwise unable to give accurate information.
e911: Enhanced 911 was created to ensure location information was transmitted to the 911 call center regardless of the callers ability to give this information. The phone companies are responsible for ensuring this information is available and transmitted to the PSAP. Conventional e911 is effective for landline phones. Cell phones present a completely different problem.
Cell phones are required to meet two different location technology standards.
Phase 1 wireless data: as cell phone use skyrocketed in the nineties, legislation was passed requiring provider's to transmit location data based on the cell phone tower that the cell phone was connected to. While this is helpful, it is problematic due to the sheer size of the area that had to be searched if the caller was unable to give their location.
Phase 2 wireless data: legislation now requires GPS location data be provided by the cell phone company. This location information can be transmitted via the gps chip from the cell phone or via radio location triangulation using the cell towers in the immediate area of the caller.
So in a nut shell, my test of neobuddy's ICS indicated that 911 worked for a sim loaded phone. I did not test the phone with the sim pulled. I also did NOT verify that GPS data was being received by the PSAP.
If 911 works with your phone it should work in any area. I was connecting with two different PSAP's as I live right between two different area's and sometimes connect to one or the other.
Hope this clears some of the confusion. A good explanation is located at en.wikipedia.org/wiki/Enhanced_9-1-1.
genesis3 and I are still working on the cm7 issue and getting closer to a resolution.
Later tators
Sent from my Touchpad using xda premium

thanks a lot. i can confirm cm7.1 has 911 issue.
Sent from my SGH-T959 using XDA Premium App

Developers should also note that as technology continues to advance, video conferencing and text message 911 activation requirements will also be legislated in.
I firmly believe that Google should begin requiring manufacturers make their modem software and audio software open source. Manufacturers should also be required to provide detailed explanations of how the relevant library's interface with the operating system, modems and audio system when activating an emergency call. This is Androids achilles heel. All it will take is one national media event to slam the door on open source operating systems for cell phones. I love the freedom Android provides and the exceptional programing skilss of our developers.

Im sorry, while this is a great explanation, i really didnt get the bottom line....
What we have on nonsamsung roms then is just a plain 911 incapable of transmitting location?
Sent from a cell tower to the XDA server to you.

Im sorry, while this is a great explanation, i really didnt get the bottom line....
What we have on nonsamsung roms then is just a plain 911 incapable of transmitting location?
Click to expand...
Click to collapse
correct as none had the source code....but for 2.3 onwards rom.
genesis3 and I are still working on the cm7 issue and getting closer to a resolution.
Click to expand...
Click to collapse
made my day.....thanks a lot....will be keeping a close eye on this thread...

My understanding is the issue is only without a sim right?

The 911 issue is with SIM, i don't know about without and im not planning on finding out.

HaloMediaz said:
My understanding is the issue is only without a sim right?
Click to expand...
Click to collapse
It has to do with emergency mode (no dim) and when no compatible roaming network is around (no service) .
Sent from my HTC Sensation 4G

hmmm I havent called 911 in YEARS but it still feels nice to have the ability and this was a nice explantion thank you

MIUI 360 in Asheville NC works fine but not in other areas?

Hopefully they can test the cm9 test ports that are out now.
Sent from my SGH-T959 using xda premium

http://www.mediafire.com/?czo03t36py5sai4
CM7 with WORKING 911 (oh yeah, GPS works too and is VERY fast to lock. Insanely so in fact -- pretty much identical to what you expect with the LG Optimus! Those who say the GPS is broken in the hardware in these phones -- you're wrong.)
No support available at this point from me since the original source for the replaced bits hasn't been disclosed. Had there been some documentation on where the original source for those bits came from I bet this would have been fixed a lot faster. If that is disclosed in the future I'll consider supporting it, but for those who want it, here it is.
Incidentally it works on CM9 too.

Genesis3 said:
http://www.mediafire.com/?czo03t36py5sai4
CM7 with WORKING 911 (oh yeah, GPS works too and is VERY fast to lock. Insanely so in fact -- pretty much identical to what you expect with the LG Optimus! Those who say the GPS is broken in the hardware in these phones -- you're wrong.)
No support available at this point from me since the original source for the replaced bits hasn't been disclosed. Had there been some documentation on where the original source for those bits came from I bet this would have been fixed a lot faster. If that is disclosed in the future I'll consider supporting it, but for those who want it, here it is.
Incidentally it works on CM9 too.
Click to expand...
Click to collapse
Can we get independent confirmation of this? (not that I don't believe you)
Sent from my SGH-T959 using xda premium

Uh, the guy who tested and verified it is the OP on this thread.
Read the first post.

You typed all that from your touch pad? props
Sent from my SGH-T959 using XDA App

Genesis3 said:
Uh, the guy who tested and verified it is the OP on this thread.
Read the first post.
Click to expand...
Click to collapse
No, I get that. Just wanted to make sure he verified was all..

Genesis3 said:
http://www.mediafire.com/?czo03t36py5sai4
CM7 with WORKING 911 (oh yeah, GPS works too and is VERY fast to lock. Insanely so in fact -- pretty much identical to what you expect with the LG Optimus! Those who say the GPS is broken in the hardware in these phones -- you're wrong.)
No support available at this point from me since the original source for the replaced bits hasn't been disclosed. Had there been some documentation on where the original source for those bits came from I bet this would have been fixed a lot faster. If that is disclosed in the future I'll consider supporting it, but for those who want it, here it is.
Incidentally it works on CM9 too.
Click to expand...
Click to collapse
Don't know who you are or where you came from but, you sir may have saved CM development for the vibrant community. Here's hoping and you're the man!!!
Sent from my SGH-T959

Genesis3 said:
http://www.mediafire.com/?czo03t36py5sai4
CM7 with WORKING 911 (oh yeah, GPS works too and is VERY fast to lock. Insanely so in fact -- pretty much identical to what you expect with the LG Optimus! Those who say the GPS is broken in the hardware in these phones -- you're wrong.)
No support available at this point from me since the original source for the replaced bits hasn't been disclosed. Had there been some documentation on where the original source for those bits came from I bet this would have been fixed a lot faster. If that is disclosed in the future I'll consider supporting it, but for those who want it, here it is.
Incidentally it works on CM9 too.
Click to expand...
Click to collapse
I just downloaded your kang and running great so far, Thanks for you work !!
Question, is this 911 fix kernel dependent ? ie will it break if I flash another cm7 kernel ?
Thanks again for your hard work !!!

will replacing the kernel break both 911 and gps fixes?

I didn't save anything.
Here's the bottom line, if you're interested in it.
In the original Vibrant device directory there was a set of sources for libaudio -- one of the shared libraries that Android depends on to talk to the audio hardware in the phone. There was no documentation as to where this source came from, but I know where it didn't come from -- it didn't come from a public Gingerbread source for the Vibrant, because there isn't one.
It turns out the library this source builds does not work correctly but exactly why I'm not certain of. One of the problems with debugging this is that I have to have someone else test for me, which means I can't do the sort of testing I like to when I'm tracing things like this (a highly-iterative process that requires that I actually be staring at the debugging screen while doing the deeds that cause the bad behavior) since I can't call 911 myself.. Had the provenance of this code been documented originally (or lack thereof) I would have investigated this possible connection, as I knew the problem lay in the audio connectivity due to myriad kernel and application traces a couple of months ago. I didn't chase that library down and attempt to graft in other related versions because I assumed that the CM people knew what they were doing building that library from source rather than using a cribbed copy from, for example, Froyo or a different gingerbread build off a similar device.
Picking up a different shared library does work. Exactly what the provenance of that library is (e.g. was it grabbed from a binary, was it built from DIFFERENT source, where did it come from?) is also unknown.
Now that I have a working shared library on this device and a non-working one I'm going to compare traces. Maybe I'll get lucky and find the changes necessary in the source that's in the build tree and be able to fix that, at which point I'll know what I've got rather than having a "magic" library from God-knows-where.
Now here's the part that annoys me -- I was all over some of the CM guys about audio problems with other Samsung devices and tried to get access to the "not yet finished" repos because I expected that if I could run down the same sort of problem with ordinary calls in one of the OTHER Samsungs it was rather more likely than not that the same fix would be pertinent in some way on the Vibrant -- simply because manufacturers tend to use the same chipsets and bits, along with APIs, between different devices (it makes it easier for their coders and maintainers to do their jobs.) In addition when I started working one this one of the other protagonists didn't give me jack and crap about the provenance of anything in the device tree and, again, there's no docs embedded in the tree either. You can find the flamewar and slander aimed at me here if you'd like. It turns out I was on the right path; the problem this library allegedly fixed was having to hit <MUTE> twice to turn off and on the audio path. Sound familiar? Well, the pointer to the file that I found and integrated was from a bug logged against the I-9000, a similar phone to the Vibrant, and that library version works. What's changed in it? There's no set of commits logged against the ZIP file provided in that patch; is it a binary lift from a different build (e.g. some factory build) or did someone fix the source?
Who the hell knows because again, it's not documented in the bugtracker. Until I know where it came from and, if there's source, I have access to it, I won't support it. I don't play the "hide the sausage" game when it comes to alleged community coding projects.
I ran into something similar with the Triumph in that there was a different set of parameters coming up from the hardware when a wired headset was plugged in. That was easy to run down because I could do it and see what was going on; it was a literal couple of line change in the code once I found it. There are a couple of places in the libaudio source that might be the cause of this now that I have a reason to look in there, but without being able to easily reproduce the condition that creates the failure (e.g. call 911) it's a guess.
The ICS builds out at present have a different copy of the same compiled library and it also works. I bet that one works too on CM7 as it's fairly close to the metal and thus the API's probably the same (or close) on the Android side but I haven't tried it yet. I've got little reason to since I now have a libaudio.so that's functional on CM7 in any event.
While I've been working on the 911 issue (for a couple months on and off) I also traced down some actual working (properly) GPS libraries that handle the AGPS assist data in the correct way, something that other sets of them do not, and added those too. I also made a few other changes. The battery life is reported to be rather impressive, and the near-instant GPS locks most-definitely are. I can't speak much to the battery life view of the world as of yet but I will be looking at that; that's an area I know quite a bit about (getting these devices to properly go into deep sleep as they should) and the source tree I'm working with does have kernel source.
Any sideloaded kernel that leaves libaudio.so alone (check the zip file to make sure that /system/lib/libaudio.so is NOT present) should be ok, but no promises. Before you go screwing with kernels make sure you want to --you might break GPS performance as a number of the kernels have various attempts to get the GPS to work right and load various libraries along with the kernel itself with varying degrees of success.
I'd be willing to maintain this port but there are two conditions -- first, I expect apologies from the CM people who attacked me, in public, and second, I expect a formal commitment that there will be no more hiding of information. "I don't know" is an acceptable answer provided you run down the person who does -- someone does know because someone DID either import or code the material in question; silence and lack of documenting where things came from and how they came to be is not acceptable. When things go into the codebase through review they damn well ought to be documented. I played "talking to the brick wall" with the Triumph and now the Vibrant and I won't do it if I'm taking on responsibility for maintaining something.
If CM wants me involved in this that's the deal. If not I'll consider setting up a parallel build and set of repos for the bits that have to be changed from the base CM7 Gingerbread branch as I did for the Triumph if there are people interested in it, but my time is not unlimited and in all honesty my taste for working with the CM people and the CM code in general has been seriously damaged, never mind that what I have here seems to work just fine. As such the benefits of continued efforts are likely to be relatively small. If I decide against a continuing effort I will take the build environment that produced that I have now and attempt to set up a manifest so it can be cloned by anyone else who cares to do so, which should take care of others being able to build and run the KANGs from source if they wish. The latter may take a while as I need to find a day when I'm not busy and can put that together (again, lack of documentation doesn't help) and then pull a clean test from a zero base and make sure it builds and runs.
The Vibrant is no longer my daily device but I do still own one, and given its relatively modest resale value I'll probably keep it as a spare device -- it's a very credible phone and with working GPS code it actually locks faster and better than my Hercules does. It's biggest shortcoming is that it's relatively RAM-starved compared to more-modern devices.
Fancy that.

[Q] How much open is Android on LG Optimus 4X HD?

The title may look weird but that's the best sentence I could find to summarize my question.
One of the myths about mobile phones is that they have back doors for the secret services or goverments to tap into and listen to phone calls or SMS messages. This was something we could never be sure about at the old days of Nokia (R.I.P.) "black box" phones.
I've been developing software for more than 20 years but my experience with Android is only 10 months and I've not dived into the big sea of custom ROMs and kernels yet.
My question is simple. How much of custom ROMs and kernels on this device (or any other Android phone) are open source and is it "much" enough to be sure that there is no back door or hidden function?
I would be grateful if ROM and kernel experts can answer this question.

well, honestly this Q sounds a bit strange, but here we go:
1) kernel:
all kernels MUST be 100% open source.
2) device tree
also the device tree has to be open source, just like the kernels
3) ROM
ROMs do not have to be open source. but nearly all (except stock based) custom ROMs for our device are open sourced. otherwise we wouldn't be able to compile them
a special topic are stock ROMs.... i have never seen an open sourced stock ROM from any manufacturer (except google ofc).
now, back doors:
i never heard of a rumor that custom ROMs would have back doors. actually we are working on finding unknown (unwanted) backdoors to fix them.
But for stock ROMs, i personally wouldn't be too sure there is no back door...
Backdoor or not, big agencies (like the NSA for example) do not need backdoors to your phone, they have way more capabilities/possibilities
So it's quite useless thinking about it IMO, as you cannot change anything about it

postacik said:
My question is simple. How much of custom ROMs and kernels on this device (or any other Android phone) are open source and is it "much" enough to be sure that there is no back door or hidden function?
Click to expand...
Click to collapse
Short answer: Not enough.
Longer answer: The kernel and some custom ROMS are open source, but many of the drivers (which operate at root level) remain closed. It should also be plausible to hard-code additional functionality into the hardware of a phone.

The thing that gets the least scrutiny is baseband since it runs on custom hardware. Even with closed source drivers it's arm code running on Linux so lots of people can understand it.
ROMs and kernels aren't really an issue though.

Update addressing "Reorganizing internal processes" coming in November?

Hi all, I hope I can provide reliable good news: LG support says some providers made some changes to some repeaters (e.g. E-Plus in Germany). They have a solution and provide us with an update released around the end of October.
Now is probably a good time to point LG to some of the major problems introduced with the JB update (4.1.3), as the new Update will likely be a smaller improvement of the latter.
In my case:
- very slow return to home screen when closing apps and problems navigating the home screens, when some more icons and widgets are present
- can't write onto external SD with some backup apps (e.g. Super Backup)
EDIT: I would be totally happy about a way to port the updated system files, once they are out, to other Roms (e.g. the ICS Stock Rom).

I'm extremely skeptical that LG would release an update for our phone. Are you sure our model is on the list?

I called them personally regarding a prior support case (repair order -> "no error found") because somebody reported the techs had replaced some parts (new IMEI) and solved the problem. I wanted the same for my P880. They told me about the changes to some repeaters, the upcoming update, and the soon following update for the P920 (?) Optimus 3D.
I am as surprised and sceptical as you are. But as I have read about this update from a second, independent, source (the German forum at AndroidPit.de), I am starting to believe and, thus, spreading the news.

pegnose said:
I called them personally regarding a prior support case (repair order -> "no error found") because somebody reported the techs had replaced some parts (new IMEI) and solved the problem. I wanted the same for my P880. They told me about the changes to some repeaters, the upcoming update, and the soon following update for the P920 (?) Optimus 3D.
I am as surprised and sceptical as you are. But as I have read about this update from a second, independent, source (the German forum at AndroidPit.de), I am starting to believe and, thus, spreading the news.
Click to expand...
Click to collapse
Can you please point us to that article on androidpit.de. Thanks
I Tried to find but no result.

See here (look for "FETTES UPDATE" on top of the page):
http://www.androidpit.de/forum/562054/lg-optimus-4x-hd-reorganisation-interner-prozesse/page/2
Sorry, this is a German post. Although the writer confused repeater with router, P920 with P990, and another user confused software and hardware update.
EDIT: My support guy explicitly statet that this will be an OTA update. I am sceptical, as it happens often with LG that updates have to be installed manually/via PC. Very likely he meant that I won't have to "bring in" my device again.

I just called them again and explicitly named the increasing delay when returning to and browsing the home sreen as the major problem with the official JB rom on the P880. If some hundred more users do the same, LG hopefully addresses the issue as well.

pegnose said:
I just called them again and explicitly named the increasing delay when returning to and browsing the home sreen as the major problem with the official JB rom on the P880. If some hundred more users do the same, LG hopefully addresses the issue as well.
Click to expand...
Click to collapse
I just don't think that some repair guy from LG can do anything else then told you what you want to hear and mark it as solved. I think they are just waiting till you buy new device. I'm lucky because I have no such problems with RIL. I disabled PIN protection and installed Mahdi. Now I sometimes (once per day?) can see no signal for second or two but it's ok.. no problems (there is no way for no signal, I'm living next to the mobile transmitter and I usualy have full signal bar). There is only one thing which gets me so angry - lags, usualy when listening music from youtube on background and browsing the Internet. My friend with Galaxy S laughs when my phone gets his lucky mood and he sees it, his phone is more smooth then mine, it's crazy.

Of course, this might all be a big hoax. BUT:
By now, I know of three different people who got pretty much the same information from LG support. Although you never know, for my part, I wouldn't like to suspect that LG internally agreed on certain standards on how to efficiently lie to their customers in this particular matter through personal communication - especially by giving an approximate release date (end of october) for the update AND outlining the release for the P920 as well. But that's just me thinking positively of other people and of the future.
Btw, could you elaborate a bit on this Mahdi thing you mentioned? I tried different Roms (Cyanogen, OmniRom) and none of them solved the RIP (Reorganizing internal processes) issue. Plus I unsuccessfully tried to fix it with EPRJ RIL implementation following this guide (experts might go *facepalm*, I tried anyways):
http://forum.xda-developers.com/showthread.php?t=2496075
Therefore I came to believe that RIP (my ideosyncratic acronym) and RIL are two pairs of shoes. No? Also, I don't really understand, what PIN protection has to do with anything.

pegnose said:
Of course, this might all be a big hoax. BUT:
By now, I know of three different people who got pretty much the same information from LG support. Although you never know, for my part, I wouldn't like to suspect that LG internally agreed on certain standards on how to efficiently lie to their customers in this particular matter through personal communication - especially by giving an approximate release date (end of october) for the update AND outlining the release for the P920 as well. But that's just me thinking positively of other people and of the future.
Btw, could you elaborate a bit on this Mahdi thing you mentioned? I tried different Roms (Cyanogen, OmniRom) and none of them solved the RIP (Reorganizing internal processes) issue. Plus I unsuccessfully tried to fix it with EPRJ RIL implementation following this guide (experts might go *facepalm*, I tried anyways):
http://forum.xda-developers.com/showthread.php?t=2496075
Therefore I came to believe that RIP (my ideosyncratic acronym) and RIL are two pairs of shoes. No? Also, I don't really understand, what PIN protection has to do with anything.
Click to expand...
Click to collapse
Mahdi is mod like Cyanogenmod, we have unofficial support from alfsamsung (he's great developer) you can find the thread in Optimus 4x development section (without "original"). He did a lot of changes in baseband driver & ril. Btw that reorganising bug is only in stock isn't it? I think in CM based roms is only crashing ril and asking for pin again or full crash of ril and baseband driver so you have to reboot your phone.
When I was running stock I never saw it (that reorganising..) I only saw someone talking about it here on xda.
I'm not optimistic because LG said that our phone won't get any update in future. I just don't think that they changed their opinion because of few people crying to their hotlink.
I'm so sorry about my english, my skills are just terrible

An update for Germany is out:
http://www.android-hilfe.de/lg-optimus-4x-hd-p880-forum/623458-update-v20c.html
Looks like the problem is gone!!!