[Vibrant Android Development] Jarmezrocks:
Hey Raymond, hold off on your excitement, I think I have a solution on many parts. I have made a fair few changes. This just could work....maybe?

Firstly the module is places in with the rest of the modules because as far as I know these are related to the kernel? All modules are related to the kernel...aren't they? so this meaning that ICS now has its modules in a different place the Ganril app cannot see the module. That being said I am going to try two things...one is just wishful thinking because it seems easy. The second is a bit more tricky-dicky. What I am thinking is that I put a new folder in the right place, modules/kineto_gan.ko inside of it. That will satisfy the app for locating the .ko file its respectful position. I am going to loosen the permissions on allowing access to this file for the system and its applications.

Second thing I am thinking is also leave a kineto_gan.ko module (yes a duplicate) with the rest of the system modules. This may or may not work? At least the rest it will be in the respectful location as with the rest of the modules so if there is anything to partake from the .ko interaction with the kernel.....then it can. I just don't know if it is being there that what ever it does and communicates will get back to the app?

Second option is to leave it where it is, and then set up a symlink in the installation proceedure so that it IS actually with the other modules however the app sees it as where it should be and does what it needs to do? I think this is going to be more successful

Next change I have performed is new install script with the vibrant modem...so no more modem issues after this...? I hope. I am confident at least. For some reason the reverse script on i9000 breaks the modem and the as it does with the i9000 script breaking modem on vibrant. That seems right....right? what ever its changed to what its supposed to be now. Some of the values in the coding don't make sense to me and I was going off on a sever tangent for a moment telling my self I need to figure this **** out...when the truth is I don't...unless I have to. So I switched it back....and its as if it was stock, and no second guessing on my behalf. Good done.

Next thing to address. The app is trying to communicate with the system and its getting denied even before it is allowed to. So.....that being said the RILD is responsible for making this **** happen. I have figured that in most instances that the phone system gets info from the RILD for the modem functions (which is a binary file and it has rights to do so) and no one thought about "hey hang on a second we have an app in system that is allowed to dig as deep as all system apps are allowed to go by virtue....but T-mob app wants to talk directly to RILD...have we not checked to make sure the system is allowing this?"

My thoughts are, NO! No we haven't so lets allow this but not just allow it from installation but allow continued communication should any all need to. So lets allow all restrictions to come off RILD (especially if the modem.bin has been the only allowance so far) and allow any app (wait for it this is the key part here) that has permissions to do this. Where do apps get permissions from? Of course they are set on the file when it is installed and that allows things to access the app and or communicate with the app, but what about the app being able to communicate execute what ever.......with everything else? In this case how is the app getting the permissions to talk to wifi? Wifi might be able to talk to it (as in the system will allow anything that we say so to access wifi) that means everything like internet browser, sync'ing bla bla bla. Wifi emits the app recieves. However T-mob wifi app needs to do its checks on things like "Are you running the right sim? Are you a T-mob user? Is your wifi on? Can I tell it to turn on if you have not done it yet after you have initiallised the app (F*ck I am talking like first person as it I am freakin app LOL - Is Jarmez going crazy? YES! :D ) Anyway I diverse....two things spring to mind here. 1) We allow this communication to take place and it will stop T-mob getting invalid sim argument throwing on screen. It sees wifi and it checks all the boxes and ALLOWS it to make further communications to RILD to initiate a call from the various other system apps that are used for calling i.e. phone or dialer....then allow it to put through what ever route or mechanism the signals or inputs to various parts/sensors on the device? So it needs HARDWARE permissions! Chaaaarrr-f*cking-ching! I now have a permissions xml. sitting within the permissions folder to allow this! Lastly with the modem now "installed correctly" leta hope that this will initiate and work.

I now need to do one last thing and that is create a new version of the zip that has everything as is but with the symlink between the .ko and the imaginary "modules" folder. I will now upload 3 new versions of the ROM for you all to try.

I NEED log cats. Raymond your last log cat was tops. Thanks heaps, you have no idea how valuable that is to be able to see what is going on and why. It's like I can be in your phone whilst your doing **** and seeing whats failed (see now I really am thinking I am crazy first I think I am an app next I think I am in your phone....soon I will think I am an android alien or something crazy!).

Fingers crossed.

BRB