[Miscellaneous Android Development] einsteinecker:
I have been very frustrated lately the more I dig into the uncontrolled mess that is the kernel source that I have been working on. Not to mention I have to take care of my hard drive, honestly I'd rather spend more time earning extra cash to buy a new hdd than work on the Fathom kernel, it's so depressing that the source that was uploaded is not configured well.

In effect I have spent the past 2 months wasting my time. And then the problem was right there: USB gadget functionality. Let me explain. Every one of the kernel issues in my kernels are because of the USB drivers not compiling properly or whatever the heck is going wrong with it. It controls the way we use Android: the reason why we don't have good SD card mounting is because there is no USB mass storage support, the reason why we have the connect charger error is because well, there is no USB support (right now, my kernel is charging the Fathom through it's internal control, and not through Android). This is the main reason why we can't boot properly, it is the main reason why the system doesn't work properly because the SD card is not detected, even the audio, this whole problem with the USB support is the final obstacle. If you ask me, I would have preferred to continue the work from .32 instead of .35.

I have confirmed this in my latest kernel that I was able to compile, after configuring the USB gadget, it will only boot if the charger is plugged in, and there it shows correct USB mass storage and ADB. You will notice none of my previous kernels have this when you connect a charger.

For those of you concerned aboaut telephone functionality, I suggest you give this link a read. After reading that, I hope you realize how difficult it is to fix the phone part. Because our Fathom's are dual CDMA-GSM, this is the reason why only half the functionality works: we just don't have the RIL to support sending the correct commands to the phone. What's worse, there are hardly any Android phones with the QSD8650 dual-mode chipset, it's either only CDMA or only GSM.

Now, I did not say this is impossible. I will figure out the problems in the kernel, but I have spent the past 2 days completely into this and it's not easy. So it will take time, and that's something I don't have a lot of, I'm just a normal joe, so I appreciate if everyone can be a little patient in this regard. I will also try to post later ajeet's final build, so that everyone can see why I prefer the .32 kernel over the .35 kernel. (Right now ajeet's .32 kernel is as good as you will get until I figure out the USB problem)

As mentioned, March 2012 is an extremely experimental build, meaning much of the functionality is going to be completely broken. The main purpose of the test was for the "connect charger" message at boot, which I've already found the problem.

I did not compile modules, so wifi was going to be broken anyways. You can always try the kernel in the first post, that has modules, which you will need to root access into the /system folder.

Remember that we are running Android from the SD card. When you are constantly streaming something from the card, as well as using other apps, you are taxing the card twice as much compared to doing the same things on Windows Mobile.

You need to install SystemPanel and end currently running programs. GPS is a no-no, and I don't think I'll ever bother with it. If the system hangs alot, you need to turn off that live wallpaper. Charger responds slowly due to bad USB functionality in the kernel.

I won't address these issues anymore. I'm sure you are aware that most of your issues are due to the build being very old and not optimized, the only purpose of the test was for connect charger issues which I already know about. The test is now concluded, so I would appreciate issue feedback regarding the working builds. Well, until I make a new kernel anyways :p

I will take my time. With a little know-how those phones can be sold instead of trashed and used for a better purpose if you don't want to wait :cyclops: