yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] einsteinecker:
Hi everyone, major updates here. Thanks to nalanickal, we have a way for 3G data to work (I was able to browse online!), as well as making calls but not receiving. Luckily I know what's wrong, but how to go about it, I honestly don't know. www2287, do you know which part of Android that accesses the Sim card?

I will try to update tomorrow for the above tests, hopefully pizzaboy can use this method for CDMA data, supposing my CDMA test is carried.

That is a toolchain. Think of it as, like a factory, it is what builds the Android kernel. Different toolchains have different results ;)

My main problem is USB, there is that charging delay, and it doesn't enable USB mass storage as well as ADB. All of ajeet's .32 kernels have this working very well, but the code is missing from .35. I would really appreciate it if you can find the .32 sources, as I'm hoping to use the USB code from there for .35.

Edit: Aw :(
[Miscellaneous Android Development] pizzaboy192:
I haven't had a chance yet to try out the Android builds, but I'll get looking into it. I'll probably be starting in the next day or so in testing it.

EDIT: Got Android to boot on my phone(s)

1: it only fully boots sometimes. Every 2 or 3 attempts gets me to the lock screen. Other attempts will reboot the phone.

2: times that it gets to the lockscreen, I have a 1 in 4 chance of being able to unlock. Other attempts cause phone to turn off.

3: I have only gotten the phone past lockscreen once, but it was on my test phone which isn't activated. It said "searching for service" but I don't know if it was using GSM or CDMA (I had the VerizonWireless Vodaphone SIM in, so both modems were active)

4: Screen lock button on side does work. Top button seems useless. Keyboard works fine.

5: I'll check hardware versions after I am done with classes to see if there's a difference. Test phone 1 is running Official LG V4 ROM. Test phone 2 is running UnOfficial V6 rom by Me (customized to work with AT&T US and T-Mobile US). My phone is running a special build of my V6 ROM with lots of extra stuff, and it seems to boot sporadically. I'll see if I can get some more details on it.

Hope that helps.

EDIT2:

boot issue after lock screen (where the device just shuts down) shows an SD card something at the top of the display (notification area?) and then dies. Will try to record on video to get proper look.

EDIT3: Got it to fully boot after quite a few tries. Ended up renaming the "device type" or whatever for HARET to VS750 and it seemed to help. I am currently getting no service. Not able to see any networks, not able to see any part of the CDMA radio (can't read MEID, IMEI, etc) so it won't work until that can happen.

Hopefully you can get it to go somewhere. I'm extremely tempted to throw together a new ROM designed just to boot android (mortscript based) and I'll see what comes from that.
[Miscellaneous Android Development] g680423:
please check this links for the gsm maybe:rolleyes: it can help

http://code.google.com/p/seek-for-android/

http://developer.android.com/reference/android/telephony/TelephonyManager.html

http://code.google.com/p/seek-for-a...ummary+Uploaded+Size+DownloadCount+UploadedBy
[Miscellaneous Android Development] pizzaboy192:
I would check those, but I have absolutely no knowledge of how Android works. I have minimal Linux knowledge as well. I just have a pile of Fathoms, and want to see what they can all do.

I'll see if they yield anything that I can understand, but I doubt it.
[Miscellaneous Android Development] einsteinecker:
That is interesting, I could learn something from this :victory:

Say, is Edit3 after root copying the CDMA files that I uploaded?

I'm not sure if I mentioned this earlier:eek:, but the phone must be charging on first boot in order for batterystats.bin to write the proper data. Subsequent boots afterwards do not require the charger at startup as long as battery is properly calibrated for its real low-battery warning (as in, charge the battery to full, drain to 5%, then charge again.)
[Miscellaneous Android Development] rising power:
I tried to try your kernel over the cyanogenmod march 2012 to test CDMA reception, but I couldn´t. I get the same ugly screen of the post #101. I tried with the phone half charged, full charged unplugged, full charged and plugged, It didn´t pass that screen, and the only file I got was a 12.txt, showing (I think) a record of the decompressed files. I overwrote the kernel before booting, only that. I´ll keep waiting for your new kernel.
[Miscellaneous Android Development] einsteinecker:
There shouldn't be anything wrong with the kernel, www2287, Georgio, pizzaboy and I are able to boot the kernel, perhaps it's your SD card.

But before you reformat your sd card, try the kernel from this post, if you haven't yet. I had suspected the first kernel was corrupted during the upload, even though there are no errors in the archive.
[Miscellaneous Android Development] g680423:
maybe we need that radio stuff check this bro

http://xdaforums.com/showthread.php?t=611787

also for USB Tethering

http://wiki.gentoo.org/wiki/Android_USB_Tethering
[Miscellaneous Android Development] pizzaboy192:
EDIT's 1, 2, and 3 all have the CDMA files copied and your instructions followed. (new kernel too)

I do get the odd screen on startup with the display corruption, but every few attempts result in a successful boot. Haven't had a need to plug it into the charger just yet, as it seems to boot fine without. Plus, my battery stats would be rather off, since I have 3 batteries that I switch between my devices.

hopefully we can get something that works. I'm replacing my Fathom soon with a HTC Trophy, but I'd like something fun to do with the Fathom afterwords.
[Miscellaneous Android Development] einsteinecker:
Naw, those are radio's that you have to flash to the phone, and those are incompatible with our Fathoms.

I see. So the problem now looks to be the kernel. Just hold onto the system.ext2 file, and I'll see if I can get a different AMSS into there.
[Miscellaneous Android Development] g680423:
:)i got some amss here u go:D

I'm posting here the copies of AMSS they are basically the same version (AABBQMLYM129005 ie Huawei U8800 which has android 2.2 OS ) but are all slightly different.

To install one of these, extract it from the 7z file, this will give you something like amss.mbn-162, rename this to amss.mbn and copy it to the /cust_backup/image folder on your phone. You can do this from a running system, from recovery (it's /cust/image in that case), or from the bootloader (pink screen).

see those files

1 amss-162.7z

xdaforums.com/attachment.php?attachmentid=683469&d=1312948463

2 amss-160.7z

xdaforums.com/attachment.php?attachmentid=683470&d=1312948503

3 amss-136.7z

xdaforums.com/attachment.php?attachmentid=683472&d=1312948592

hope this works:rolleyes:
[Miscellaneous Android Development] pizzaboy192:
I do not have a cust_backup/image folder. (or a cust_backup folder for that matter)

Any other suggestions?
[Miscellaneous Android Development] g680423:
NO WAIT I DONT KNOW IT REALY WORKS OR NOT LET einsteinecker DECIDE FIRST
[Miscellaneous Android Development] g680423:
OKAY FOR THE SD ERROR fix

try this maybe it can help

Multi Mount SD-Card v2.31 APK

http://www19.zippyshare.com/v/74030381/file.html
[Miscellaneous Android Development] ednello:
Information in Spanish language

Hi, einsteinecker, I hope that you have very much progress in your work with android for the Lg Fathom. i wish to ask you if it is possible that you write the situation actual in the advances of the thread, but no much , only a three lines for tell us: which is the more stable version for download and put in our phones ?, and which are the more important bugs in this ? :eek:.

All this is for i might write a little information here in spanish for all comunity of Latin America :cowboy: which have this phone and they are almost for throwing your phones in the garbage !:crying:

Thanks Again !!:good:

and Sorry for the many Nuisances !!
[Miscellaneous Android Development] rising power:
ensteinecker dice que está resumiendo el trabajo de ajeet17181, quien abandonó el proyecto/teléfono hace tiempo y cerraron el otro thread. Él ha estado buscando el último kernel de ajeet, que medio funcionaba, pero no lo ha conseguido, así que está trabajando con lo que hay.

En este thread han habido varias líneas de acción: o trabajar con froyo, o con gingerbread, o con cyanogenmod. En estos momentos el esfuerzo se está concentrando en esto último, por lo mismo de que no se consigue un kernel más o menos pulido que montar sobre los archivos base.

Estamos en fase alfa. Si alguien quiere sumarse a las pruebas, tiene que decidir sobre qué versión trabajar, bajar los archivos correspondientes y seguir las instrucciones mencionados(as), copiar eso a una carpeta de una buena microSD y tratar. Tomar en cuenta que cuando se habla de que hay que sobrescribir tal cosa por tal cosa o copiar tal cosa a tal lugar, hay que hacerlo como root desde Android (excepto el kernel, que hay que hacerlo antes de arrancar).

Resumen rápido. Saludos.
[Miscellaneous Android Development] rising power:
einsteinecker, I haven´t been able to boot cyanogenmod march 2012 with your last kernel. At least pizzaboy192 can, sometimes.

I attach the only file generated during the boot process, to help you figure out what is going wrong.
[Miscellaneous Android Development] pizzaboy192:
Does it only get to the distorted screen before the CyanoGen Mod logo appears? (The one that had an image posted of the strange corrupted display a few pages back?)

If so, you'll need to make sure the data and system files are not fragmented. After defragmenting my card, it seems to boot slightly more reliably.

If you have a card reader on one of your computers, a program like MyDefrag works rather well at making sure that all your files are not fragmented on the card, allowing a proper boot.
[Miscellaneous Android Development] rising power:
no go

Thanks, pizzaboy192. I have never reached the CyanoGenMod logo, it get stucks on the distorted screen of post #101.

I tried to defrag the microSD card on my XP computer, and I ended formating it on one 7 computer. Still, can't pass the stripes screen, and I only get the 12.txt file, so einsteinecker, any luck with the log?
[Miscellaneous Android Development] pizzaboy192:
Can you post your startup.txt file, and the dmsg.txt file?

Also, what zimage file are you using? is it the latest? (zimage = kernel)
[Miscellaneous Android Development] rising power:
Thanks, it was my startup.txt not pointing at the right path. BTW I'm using the system of post #97 with its default dmsg.txt, and the kernel of post #106.

Now I can boot into cyanogenmod7 most of the times, but my system crashes every few minutes (battery ~50%).

Issues: My SIM cards has a PIN, I can't see where to enter it, so it stay unregistered. I can turn on WiFi but it doesn't ask me for joining a network, so it limits my testing (I would like to test picking CDMA signal but I don't see a root explorer and don't know how to add it in this situtation). I don't see the internal memory. If I play music and try to do other things, the music stutter like a bad CD. The system is not as responsive as it should. Camera is not working (white screen). I cannot turn off GPS (if is really on, it draws battery a lot). The system crashes (hangs) without an obvious pattern, it powered itself down one time. The messagee LED remains red after unpluging the charger.

Haven't tried the keyboard and/or layout.

It is needed improvement, but of course we all know this is WIP. Keep going.

Thanks
[Miscellaneous Android Development] pizzaboy192:
It would be awesome if someone could port nativeSD to the Fathom. (nativeSD creates an EXT4 partition on the SD card, allowing a huge speed increase in boot times.) I'll look into how this may work on the fathom and see what can be done to make it work properly. It may end up requiring a linux machine to get it working properly. We'll see how that turns out. If it works, we should also be able to boot TG01 and HD2 ICS and Jellybean ROMs probably.
[Miscellaneous Android Development] pizzaboy192:
I'm glad you're putting time into it. I know how the whole money thing feels. as a suggestion, you can always check out Amazon's Mechanical Turk program if you're over 18 and want to earn some quick cash.

I'm personally fine without CDMA funcationality, as I'm replacing my phone within the next two weeks with an HTC Trophy. as long as we can get a reliable boot, I'd be fine. WiFi and Bluetooth would be nice, but at this point, I can sideload any apps that I feel necessary.
[Miscellaneous Android Development] g680423:
pizzaboy192 u have a blog :eek:
[Miscellaneous Android Development] einsteinecker:
Okay folks, I want to show you why the kernel source on github is not the kind of source we need. Thanks to nalanickal for giving me ajeet's last known work, I'd like everyone's feedback on how this works for you.

LG Fathom Gingerbread 2.3.7 with working 3G data + Wifi

First you''ll want to download it: https://rapidshare.com/files/2409340512/Punnoose.7z

Now that you have the ROM, you will need to edit your phone. Download this: http://www.mediafire.com/?azm89r85x6k2hhz (link thanks to da_reeseboy here.)

Please read the .txt inside the LGNPST archive on how to install. I can't help in that regard as I too funked my install until I undid everything and followed the txt file :p

After you set that up, download this: https://rapidshare.com/files/606560282/Clipboard01.zip, Or the the texty no frills way:

In windows mobile, change Fathom's USB mode to VZaccess manager mode. Open LGNPST and connect your Fathom. Go to "phone setting" and change default phone mode to GSM, and change the APN setting to the one your carrier uses.​

I must warn that Android will attempt to connect when it boots, so be sure you have either an unlimited data plan or make sure you won't be charged if you use prepaid. So what does this build have?

Pros:

-3G internet!

-Accelerometer!

-Real USB support.

Get ready for the Cons because it's a real deal breaker.

-Cons:

-D-pad is not aligned correctly. You can fix it yourself though...

-Incredible power drain. This is caused by the phone remaining at a high mhz without any way to fix it. Even if you use SetCPU to change the governor, the voltage looks like it remains the same so power drains even at 245mhz! :crying:

-No multimedia. And by that I mean no gaming for you, anything 3D is not even enabled on the kernel.​

As you can see, the only cons of my kernel is poor USB support and no 3G data. Granted I made a kernel that can also connect, but it's that USB that prohibits the SD card from mounting properly :(

That's the only reason why I'm focusing on fixing the USB functionality right now, I hate seeing the "connect charger" and no sd card errors, if only I can fix that then the kernel is fine, becuase wifi and bluetooth works okay, it's just that darn USB...

Edit: After 3 days, I finally fixed the USB problem. The bad news is, the phone does not detect a battery :eek:
[Miscellaneous Android Development] pizzaboy192:
Is the build you linked to one that is a flash-to-NAND build? (Not an SD card build?)

If so, that's awesome. I'll look into how it was made and try to work out what to do for easy cooking in the future.

Who provided you with that build?
[Miscellaneous Android Development] einsteinecker:
It is an SD build. The LGNPST thing is just to change the phone's default setting :D

As I mentioned, nalanickal gave it to me. It has a February 2012 build date, so I presume this is ajeet's unshared work, which is strange, why wasn't this shared before? I know everything that is wrong with the kernel, and if I had that source, I could have compiled a fully working kernel. :(
[Miscellaneous Android Development] pizzaboy192:
I wish I would have known about setting the GSM radio to default earlier. I replaced my fiancee's Fathom with a HTC Radar because of issues with it trying to default to CDMA.

Thanks for the info. I"m still looking into the idea of building a NAND or slim WinMO ROM that allows you to direct-boot off the SD card (or stored on NAND, depending)
[Miscellaneous Android Development] einsteinecker:
When I was building ROMs for my Touch Pro, I did something very funny: I included the Touch Diamond internal storage driver. I made a partition inside the ROM storage that acted as an SD card. You could try that.
[Miscellaneous Android Development] pizzaboy192:
I was thinking of the easier method of just running a mortscript at startup to boot Android. I could try the other way. Does HARET require an SD card to boot off of?
[Miscellaneous Android Development] einsteinecker:
I'm not sure. The part that I was thinking about was how to designate Haret to create the data.img where you want it to be. I've buried my head in the kernel so anything WM is alien to me :p

There is a program called "Android Loader" here at XDA, see if that works. I know genY dualboot doesn't, but Android Loader is said to work with any Android version.
[Miscellaneous Android Development] pizzaboy192:
I've gotten RunDroid to work (it's just a set of mortscripts) and it seems to be fine. I'll see what I can find about booting Android and specifying where data.img should be. otherwise I could possibly get the EXT4 settings working.
[Miscellaneous Android Development] g680423:
Creating a new ext4 filesystem is very easy once you have upgraded to e2fsprogs 1.41 or later. Simply type:

# mke2fs -t ext4 /dev/DEV

or

# mkfs.ext4 /dev/DEV

Once the filesystem is created, it can be mounted as follows:

# mount -t ext4 /dev/DEV /wherever

If you have a sufficiently new system, the "-t ext4" should not be needed.

NOTE: Although very large fileystems are on ext4's feature list, current e2fsprogs currently still limits the filesystem size to 2^32 blocks (16TiB for a 4KiB block filesystem). Allowing filesystems larger than 16T is one of the very next high-priority features to complete for ext4. :cyclops:

or watch this http://www.youtube.com/watch?v=Cygl0qZnbaM
[Miscellaneous Android Development] g680423:
:crying::crying::crying:still no camera and incoming calls front speaker died in this version so outgoing calls died too :crying::crying::crying::crying:

---------- Post added at 11:22 AM ---------- Previous post was at 11:06 AM ----------
[Miscellaneous Android Development] einsteinecker:
I never said I fixed the camera, and please read carefully: that is Ajeet's kernel, not mine, so I have no idea what the heck is that kernel made out of.
[Miscellaneous Android Development] pizzaboy192:
I found some interesting and helpful stuff. I haven't had a chance to check if any of it works, but here's a link from XDA on some kernel commands.

http://xdandroid.com/wiki/Kernel_boot_command-line_parameters

Two of interest (to me) are: htc_battery_smem.fake (turns off battery warnings)

and force_CDMA which works for phones like the HTC TouchPro 2 which have dual-GSM\CDMA radios.
[Miscellaneous Android Development] einsteinecker:
That's actually the CDMA parts I asked you to try, which I got from XDAndroid :p When my Fathom was defaulted to CDMA, I did force_gsm and it still didn't work.

I've not tried smem.fake though, but inside the kernel there already was an option to disable the warning (I made sure the warning was disabled), so I think that's one of the options they said haret will ignore.

Now, my latest kernel is a weird one. If plugged in, the SD card will mount on boot, and you can see the USB mass storage + ADB at the top left. Subsequent connections of the charger will no longer trigger the USB functionality. Without the charger connected at boot, the Sd card may/may not mount.

Other than that, the wonderful part is no "connect charger" errors and the 3G data works, but when I enable the wifi modules, 3G is a hit and miss. This hasn't been an easy ride :silly:
[Miscellaneous Android Development] pizzaboy192:
at least we are getting somewhere. I'll try the "Force_CDMA" switch some time this coming week when I have some time. I won't have time to test much in the next week or so, but who knows how holidays work and such.

EDIT: Tried the force_cdma=1 switch and I went from "no service" to "Searching for service".

I'm getting some new MicroSD cards (faster, different brand) this coming week, so I can do testing on my non-main device. It seems to have made a good change. I'm still using your old build, not the new one that seems to have fixed things, as I haven't had a chance to download and install it to my phone yet (Rapidshare is blocked on campus)
[Miscellaneous Android Development] einsteinecker:
Oh yeah, faster Micro SD's... I wanted to test that, though the fastest I have is a Class6 4GB, but I wonder if it would actually save battery life (thanks to lower access times for the card).

Since I was really busy today, I'll try to post the big Kernel update tomorrow, but I wanted to ask Fathom users about something. Now, my phone wasn't brand new, and the charger that came with it was actually the wrong plug, and it charges fine after I modded it, but the phone is hot while charging. I want to know if this happens to you folks too, starting from below the camera lens all the way down to beside the USB port, my phone get's rather warm, as if I was playing a 3D game on Android. In fact, I encountered an high temperature restart on Android once while playing a game while charging:silly:

More info about my findings into the kernel problems I've been having.

-You know how the sound dies sometimes, especially when you plug in a headset? Yeah, that is thanks to a .32 driver, since we are using a .35 kernel, hello bugs :p

-I believe this is also the main reason why we can't get a fully functional USB support working. Ajeet mixed .32 power drivers with .35 ones, making compatibility so unstable. As you can tell in my latest attempts to fix it, it ended up with only 2 results: full USB without battery recognition, or unstable USB with battery recognition, both affecting the SD card mount status.
[Miscellaneous Android Development] pizzaboy192:
the cards i am getting are class 6 as well. i cureently use a class 4 and it doesn't work reliably in windows mobile or android.

as for charging, my phone does not have that heat issue. some times it gets warm, but nit often. how many amps does it put out at 5 volts? my OEM charger purs out 1 amp.

i charge my extra fathoms from my computer. have you had issues doing that?
[Miscellaneous Android Development] einsteinecker:
I also use Class 4 when testing Android :p

My charger has little information on it, other than an output of 650ma. I used a different charger that charged at a slower rate, the same way if I plug into computer USB port. So I'm guessing my modded charger is pushing a lot more power, which is strange, when I used my other charger, my fathom shows that "this cable is not authorized for the phone" or something similar, yet my modded charger does not have that message.

It gets weirder, as my modded charger does not activate the Android ADB function, but my other charger does. Oh, looks like I have more testing to do :D
[Miscellaneous Android Development] rising power:
Actually, I have done a lot of research about that topic ;) The phone senses the charger type is connected to, and ask for certain ammount of charge units accordingly (1CU = 100mA). So, depending on the charger used and the temp of the battery sensor, it can ask for good ammount of current, or ask for the standard 500mA, or by the contrary, show the message of the wrong cable, all depending upon the port it finds is connected to.

At hone with the original charger it gets warm, but nothing to worry about; but in my car gets really hot (I have it over my gearbox), and with charger and the GPS on for more than a hour, it warns about battery overheat and ask for charger disconnect, and/or even shut off as protection. As a mod, I added an active cooler to the base yesterday, and I´m testing it ;)

Yes, in this phone, a china Class4 makes wm6 show my external shotcuts with generic icons (have tried with two cards) I will need to use a faster one, although my first Class4 worked fine. I think I going to get a Class6 at least.