Database Info

[ROM][PORT][ALPHA]jMod FroYo SDK Port for Dream/Sapphire 05/21

Sorry I couldn't get this earlier. I had the SDK since it dropped on developer.android.com, but I was waiting for somebody else to do it. It's been almost a day and nothing, so I did it myself (plus I've been working on getting android to work on my HD2...)
Release Name: jMod FroYo SDK Port
Release Version: 05212010.0410
Release Date: 05/21/10 04:10 AM
MD5 Sum: 229d7120460d6a737d22b4006a766b02
Credits: SDK system from Google, hardware files from HTC and AOSP.
Base Firmware: 2.2 SDK
Radio Required: 2.22.19.26i
SPL Required: Any
Partition Layout: Any/none, Ignored
Wipe Required: Yes
Special instructions: Just SDK Apps. Radio should work, so you can make calls and use the interwebs. Wifi broken. Bluetooth broken, Camera broken. Some weirdness going on with the LED, it will stay purple when not charging.
To sync Gmail and Contacts using exchange server settings:
email: [email protected]
password: password
Click to expand...
Click to collapse
Then Manual Setup, Exchange type, then
Domain\Username: [email protected]
password: password
Server: m.google.com
Use secure connection (SSL): check
Accept all SSL certificates: check
Click to expand...
Click to collapse
Download:jMod FroYo SDK Port

Wow, that was fast... downloading to give it a try
€: Funny thing. Installed, configured apn started browser, went to my favourite tech news site for testing -> Big headline: No Froyo update for G1
I think for a few hours porting time it is quite good. Sure, a lot of things don't work yet, but its much smoother than I imagined.

Yea so far it boots up and it just loaded up for me

Its not even that slow......transitions are nice but desktop scrolling isnt that good =)

I'm currently testing one with Gapps. if it works, I'll have it up in a few minutes

If Froyo AOSP source code isn't available, how the heck do we compile any wireless drivers for this?

xaueious said:
If Froyo AOSP source code isn't available, how the heck do we compile any wireless drivers for this?
Click to expand...
Click to collapse
We wait for AOSP

i have also ported this to G1 and have radio working etc.... mine was posted at ASpin so i never saw this but im wondering if if you (Jubeh) are interested in a colab to get things further along.... gtalk me [email protected] oh, i have LEDs fully functional also... working on wifi and BT but we really need gapps... they just FC for me at this point... CR

Go guys work together on this... If you need any extra testers to help I am sure many will help where they can.
Count me in if required

Has anyone tried if the Flash Player shows up in the Market when using this ROM cause Adobe said it would only appear on devices running 2.2

chrissshen said:
Has anyone tried if the Flash Player shows up in the Market when using this ROM cause Adobe said it would only appear on devices running 2.2
Click to expand...
Click to collapse
i am flashing now but believe we need google apps for that

chrissshen said:
Has anyone tried if the Flash Player shows up in the Market when using this ROM cause Adobe said it would only appear on devices running 2.2
Click to expand...
Click to collapse
That was answered many times in different threads: seems Flash requires new Market app and we don't have it yet.

I would also be glad to test, PM me. I would love to show off FroYo!
Plz work together!
If you both work on this together then we will have a working FroYo twice as fast, it would be tons of fun to beat the Nexus One to FroYo

I flashe this on the g1 2.22.23 image and it works fine u could even say its a little faster just thought I would input my discovery great work on the fast port to the g1!

the google apps?

Jit seems to be disabled, am I Right?
Linpack ~1.7 MFLOPS
dalvikvm -help says nothing of jit
Really looking forward to a more advanced build. Thumbs up for this alpha release it makes you want more froyo.

My Findings:
~First boot is quick but no set up wizard at all but timezone is defaulting to network values.
~ text messaging working however it sais that my message could not be sent yet they are recieved by recipient. as they are answering my questions.
~LED stays purple after usb unplugged.
~have set up uk vodafone APN but cannot connect to internet. No connection. (not sure why will keep trying)
~Holding Home button launches RECENTS
~NEW CAR HOME IS COOL
~ I had reformatted the SD card but states SD card is blank or unsupporte (will try reformatting)
~In Call volume seems low.
~fairly major one NOT RECEIVING INCOMING CALLS if I call myself it rings but phone doesnt show any incoming call in any way.
~Have sounds set for text messages yet no sound on incoming texts.
Will add if I find anything else

Thanks! Thanks!Thanks!Thanks!Thanks!Thanks!Thanks!Thanks!Thanks!Thanks!Thanks!Thanks!Thanks!Thanks!Thanks!Thanks!Thanks!Thanks!Thanks!Thanks!Thanks!Thanks!Thanks!Thanks!Thanks!Thanks!Thanks!Thanks!Thanks!Thanks!Thanks!Thanks!Thanks!Thanks!Thanks!Thanks!Thanks!Thanks!Thanks!Thanks!Thanks!Thanks!Thanks!Thanks!Thanks!Thanks!Thanks!Thanks!Thanks!

magpie2000k said:
My Findings:
~First boot is quick but no set up wizard at all but timezone is defaulting to network values.
~ text messaging working however it sais that my message could not be sent yet they are recieved by recipient. as they are answering my questions.
~LED stays purple after usb unplugged.
~have set up uk vodafone APN but cannot connect to internet. No connection. (not sure why will keep trying)
~Holding Home button launches RECENTS
~NEW CAR HOME IS COOL
~ I had reformatted the SD card but states SD card is blank or unsupporte (will try reformatting)
~In Call volume seems low.
~fairly major one NOT RECEIVING INCOMING CALLS if I call myself it rings but phone doesnt show any incoming call in any way.
~Have sounds set for text messages yet no sound on incoming texts.
Will add if I find anything else
Click to expand...
Click to collapse
1. Setup Wizard is part of GApps, which we don't have.
3. Did you read the first post?
4. It's a rough port from a device that doesn't have radio, I would expect that (The first post says "should", not "is").
5. Hasn't it always done that?
7. The Emulator doesn't have an ACTUAL sdcard, so this should be expected.
9. See 4.

ChiefzReloaded has gotten Gapps and a different kernel running on his:
http://www.androidspin.com/2010/05/...-running-on-t-mobile-mt3g-with-data/#comments
But it's unreleased..

CM7 on D2G - issues with APNs, possibly Rogers specifically?

I'm posting this on the four android-related forums that I participate in, in hopes that someone has seen this before and knows what to do.
Here's what I had:
- Droid 2 Global, unlocked, rooted, with Fission ROM, using Rogers Wireless, a GSM network in Canada
- it had been working just fine for 5 months
Here's what I did:
- Used RSDLite and the SBF loader to flash the stock 2.4.330 firmware as seen here: http://droid.koumakan.jp/wiki/SBF
- ended up with a bootloop, as the directions said I would. cleared data and cashe, no problem, phone booted.
- started up phone, switched to GSM mode, entered APNs, immediately had data service, tested phone functionality, all was well, used APN backup/restore and APN Manager to make backup files of my APNs
- Used stock recovery mode to upgrade to 4.5.607 (gingerbread) firmware as seen here: http://droid.koumakan.jp/wiki/4.5.607_Firmware
- I used the file linked to from here: http://www.droid-life.com/2011/08/22/gingerbread-build-for-the-droid2-global-leaks/
- started up phone, switched to GSM mode, entered APNs, immediately had data service, tested phone functionality, all was well, used APN backup/restore and APN Manager to make backup files of my APNs
- rooted phone using the adb method that is out there. rebooted and confirmed root access. installed a couple apps that need root. tested phone functionality, all was well. used APN backup/restore and APN Manager to make backup files of my APNs
- As described here, http://droid.koumakan.jp/wiki/CyanogenMod Installed Droid 2 Recovery Bootstrap and ROM Manager in order to flash CWM. rebooted into CWM, factory reset, installed the latest release (10/06), and rebooted
- started up phone, switched to GSM mode, phone app crashed immediately (as is to be expected, based on known bugs), rebooted for it to take effect
Now here's the problem:
- phone can make calls and receive texts with no problem, but cannot get data. wifi also works.
- went into wireless settings, mobile networks, access point names, nothing shows up. Clicked "add APN". entered the APN info that had worked for me before at the past two junctions. hit menu button, then save. takes me back to the APN screen, but no APN shows up.
- repeated this cycle a few times following reboots, etc. Eventually the phone gets to the point where the "add APN" button will not even come up when the menu key is hit.
- during the above, was also checking the "network operators" setting. The phone does locate all of the networks that are "in the air" but no matter which one I choose it will tell me "your sim card does not allow a connection to this network"
- used root explorer to check /data/data/com.android.providers.telephony/databases/telephony.db. There is a list of about 1500 APNs. There are multiple entries for Rogers including all of the ones I tried to enter that appeared not to save.
- used APN backup/restore and APN manager to attempt deleting existing APNs, restoring the ones that were known to work, etc. Nothing works. These programs do work, and when I check the telephony.db file I can see what they have done to the file, but they are unfortnately unable to make any APN "stick" at the APN screen, and apparently that is the only way that it will work.
more info:
- I've noticed that the list of rogers entries seems to get larger and larger as I go through this process multiple times. I may be wrong, but it seems that this telephony.db file might not actually get changed or updated when you flash a new kernel/firmware/mod/rom to the phone.
- I'm sure that the lack of a list of APNs and the "sim card does not allow connection" message are related. For whatever reason there seems to be a bug in CM7 where the telephony.db file has problems "talking" to the APN screen in settings. But it must not affect most people.
- yes, I have tried a new SIM card.
- yes, I have tried clearing cache, data, dalvik, and fixing permissions.
- Anyone else on Rogers Running CM7 on a D2G? If so, I'd love to talk to you. Maybe I could convince you to send me a working CWM backup. I imagine that if you're a conscientious rommer, you have a backup made folling a fresh install of CM7.

I used to do at one point. The froyo base 2011.08.13 version was the last one that worked for me. Newer ones boot looped if SIM card is inside, no matter what I do. I stopped trying after couple further releases all of which boot looped. Essentially quit using CM4D2G due to bluetooth not working with BT handsfree. Later, after the official Motorola GB release came, I have not even looked back. Since I like few BLUR features, especially dialler, the GB Motorola released suits me very well. With the doubled battery life and the MUCH BETTER GSM radio in 606/607 bulds, phone finally settled down and I can now rely on it.
I have CM7 on another of my phones - actually 2 of them - a Milestone and (recently) a HTC Vision - I love CM7.1 especially on the latter!
I assume your phone works fine with stock rom - right?
Edit: I have a XT860 which is in for repairs - once I get it back and I have a reliable daily phone I plan to experiment with the new GB based CM4D2G. Hopefully this week...

leobg said:
I used to do at one point. The froyo base 2011.08.13 version was the last one that worked for me. Newer ones boot looped if SIM card is inside, no matter what I do. I stopped trying after couple further releases all of which boot looped. Essentially quit using CM4D2G due to bluetooth not working with BT handsfree. Later, after the official Motorola GB release came, I have not even looked back. Since I like few BLUR features, especially dialler, the GB Motorola released suits me very well. With the doubled battery life and the MUCH BETTER GSM radio in 606/607 bulds, phone finally settled down and I can now rely on it.
I have CM7 on another of my phones - actually 2 of them - a Milestone and (recently) a HTC Vision - I love CM7.1 especially on the latter!
I assume your phone works fine with stock rom - right?
Click to expand...
Click to collapse
Yes, everything works really well with stock rom. I was quite impressed, as it was my first GB experience. Unfortunately, as with cars, I am all about the "options", and I can't seem to let go of a feature once I have experienced it. I love CM7 and I really want to make it work for my D2G.
I posted this same thing at the rootzwiki thread, and one of the head developers said "You my friend may finally have identified where the gsm data issues are coming from. it isnt just you, it's 98% of the gsm users that arent having data". Another user got me to change a couple of permissions. I thought he was onto something but it didn't work, either. Nonetheless, I think I brought enough attention to this issue and also gave them something to work with through all my trial and error. I am optimistic.
But, for now, I think I have to take CM7. I want my data! I am really tempted to just give stock GB a shot. But Blur scares me. Most people don't seem to like it, though I admit I don't fully understand what Blur is! I see there is MIUI and apex, angel Hexen and VenusX. I might have to try them first.

hallo!
had exactly the same problem! i bought a verizon phone an using it in greece!
But i simply dowloaded some APNs manager from the market and within 2 minutes my phone was connecting to the internet!! So if this worked for me i`m sure its gonna work for u too!!

greek_lover_69 said:
hallo!
had exactly the same problem! i bought a verizon phone an using it in greece!
But i simply dowloaded some APNs manager from the market and within 2 minutes my phone was connecting to the internet!! So if this worked for me i`m sure its gonna work for u too!!
Click to expand...
Click to collapse
Can you be more specific as to what you did? Because it sounds exactly like something I tried already. What was the exact name of the software you used? Was your problem 100% exactly the same as mine, or just similar? I literally can't make an APN show up at the APN screen at all.

seventieslord said:
Can you be more specific as to what you did? Because it sounds exactly like something I tried already. What was the exact name of the software you used? Was your problem 100% exactly the same as mine, or just similar? I literally can't make an APN show up at the APN screen at all.
Click to expand...
Click to collapse
Some people have this exact problem with the D3, looks like in the D3 placing the phone in airplane mode and then on again is enough to make the APN manager able to read the MCC/MNC codes and, consequently, to store the provided apn.

I wish it was that easy, but it's not. I have tried a number of solutions similar to that but no dice. I appreciate the attempt though.
Sent from my DROID2 GLOBAL using XDA App

For the record I have that problem on the D2g flashed with the latest builds of cyanogen rom, (with the same SIMs perfectly working on D3 and D2g with the stock rom), and the airplane mode trick doesn't works too.
So far I haven't found a solution

To get my wife's d2g to work in japan I had to use root explorer to manually edit a file. The file is located at etc/ppp/peers/pppd-ril.options mount the file rw and manually edit the user name and password to match your apn. Toggle airplane mode on off after saving changes and it should work.
Sent from my HTC S710d using XDA Premium App

Thanks, i guessed that if a proper fix may be hard to find, a workaround was easy enough, I'll try it later with the gingerbread froyo.

dobosininja said:
To get my wife's d2g to work in japan I had to use root explorer to manually edit a file. The file is located at etc/ppp/peers/pppd-ril.options mount the file rw and manually edit the user name and password to match your apn. Toggle airplane mode on off after saving changes and it should work.
Sent from my HTC S710d using XDA Premium App
Click to expand...
Click to collapse
sounds interesting. I will give that a try the next time I flash CM7. I moved on to Apex. It's ok, but absolutely dreadful for battery life. I can't imagine CM7 is any better considering it has about 50 more bells and 125 more whistles. But I do prefer CM7 to anything else so as soon as I actually have some tweaking time again, I'll give this a shot.
Since both CM7 and Apex are built off the same firmware, I could just flash them overtop eachother, and wipe date and cache, right? As long as it's that easy, I could see myself trying this sooner.

seventieslord said:
sounds interesting. I will give that a try the next time I flash CM7. I moved on to Apex. It's ok, but absolutely dreadful for battery life. I can't imagine CM7 is any better considering it has about 50 more bells and 125 more whistles. But I do prefer CM7 to anything else so as soon as I actually have some tweaking time again, I'll give this a shot.
Since both CM7 and Apex are built off the same firmware, I could just flash them overtop eachother, and wipe date and cache, right? As long as it's that easy, I could see myself trying this sooner.
Click to expand...
Click to collapse
I gave this a try, and no dice. Too bad.
Thanks anyways.

The Solutor said:
Some people have this exact problem with the D3, looks like in the D3 placing the phone in airplane mode and then on again is enough to make the APN manager able to read the MCC/MNC codes and, consequently, to store the provided apn.
Click to expand...
Click to collapse
I now own a D3. CM9 is doing the exact same thing to me!
I tried what you said and I am still not getting data. phone and texts work though, just like before.

CM7 APN Issue is Fixed!

The APN issue in CM7 is finally fixed!
Check out the last few comments here - http://code.google.com/p/cyanogenmo...on Model Network Owner Summary Stars Priority
*I TAKE NO CREDIT FOR THIS*

Wow that's awesome thanks for the update
Sent from my LG-P999 using xda premium

That didn't take long to make it over here. Lol.
Seems good so far here.

Awesome news...loving my G2x more and more every day! Can I just download that boot.img and flash it to my existing ROM through ADB? I'm on EagleBlood 2.3.7 which is a CM7 variant.

pettigrew95 said:
Awesome news...loving my G2x more and more every day! Can I just download that boot.img and flash it to my existing ROM through ADB? I'm on EagleBlood 2.3.7 which is a CM7 variant.
Click to expand...
Click to collapse
It should work fine. The change appears to be in the ramdisk, so if your ROM didn't require anything odd from it, you should be fine. Last time I played with EB, it didn't do anything odd in there.

ttabbal said:
It should work fine. The change appears to be in the ramdisk, so if your ROM didn't require anything odd from it, you should be fine. Last time I played with EB, it didn't do anything odd in there.
Click to expand...
Click to collapse
Thanks going to flash now!!!

Which comment I should read. .?

Reading those comments, it doesn't appear it was "fixed" but rather "helped". It seems that certain reboots didn't shut down the radio "perfectly" and the stock OTA files had some top layer reboot switch, which would reboot the radio after a set time of being disconnected.... which CM lacked.
It is weird because I am running MIUI and I haven't had a disappearing APN in some time... although we don't have a functioning WiFi calling app (Invalid SIM). I just thought it was funny when ricardo threw out Kinteco (or whatever WiFi Calling APK is) as I have wondered why CM7 had bad APN issues when MIUI has bad WiFi Calling. I see they tried building a rom without Kinteco (?) and the issue persisted, so I don't know.
So now, resetting from the UI is the same as a hard reset (pwr + volup) and a battery pull. I think bootup will also recycle the radio so it properly turns up too.
Sweet. While I don't know if it is perfected, it looks like they are on top of it and should be cooked in nightlies within a few days.

First a2dp now apn fix.... Ricardo is a genius, everyone should buy him a beer!!

player911 said:
Reading those comments, it doesn't appear it was "fixed" but rather "helped". It seems that certain reboots didn't shut down the radio "perfectly" and the stock OTA files had some top layer reboot switch, which would reboot the radio after a set time of being disconnected.... which CM lacked.
It is weird because I am running MIUI and I haven't had a disappearing APN in some time... although we don't have a functioning WiFi calling app (Invalid SIM). I just thought it was funny when ricardo threw out Kinteco (or whatever WiFi Calling APK is) as I have wondered why CM7 had bad APN issues when MIUI has bad WiFi Calling. I see they tried building a rom without Kinteco (?) and the issue persisted, so I don't know.
So now, resetting from the UI is the same as a hard reset (pwr + volup) and a battery pull. I think bootup will also recycle the radio so it properly turns up too.
Sweet. While I don't know if it is perfected, it looks like they are on top of it and should be cooked in nightlies within a few days.
Click to expand...
Click to collapse
Actually, I don't think that's quite correct.
The change makes it so the ril-daemon shuts down earlier on reboot, to make sure the radio is stuck in a funny state when the system boots back up, hence the apn issue. Also, the only problem they were reporting still having is sometimes it happens when you come out of cwm and reboot back to android. I just looked at the changelogs on cm7 and it appears he's just patched this as well. Hard reset is not the same as the new reboot function. If you look at the code, you'll see he just added
on property:sys.shutdown.requested=1
stop ril-daemon
at the end of the shutdown sequence. A hard reboot is not the healthiest thing to do on our phone because it's a journaling file system, can create corruption. (It's very rare, but it happens.) This reboot is the same as regular, shutting down everything properly, just adding the stop command to the ril-daemon (the service that controls the radio chip, essentially).
First part of your post was correct, though (Plus, it's already in the nightlies. 165 has the stop ril-daemon on shutdown, and 166 it looks like will have it on rebooting from recovery as well.)
Ricardo is the man

Also, please be sure to keep an eye on the thread. Ricardo has been asking for various radio logcats from both Stock and CM7 ROMs. Everyone that knows how to do this (logcat -b radio) should pitch in with logs as he requests them.
Here's to a %100 working CM7.
And yes, beers.

mstrk242 said:
A hard reboot is not the healthiest thing to do on our phone because it's a journaling file system, can create corruption.
Click to expand...
Click to collapse
I was under the impression that a journaling file system is specifically there to protect against file system corruption. Your comment made it sound like it's riskier to hard-shutdown a journaled file system than a non-journaled one...or maybe I'm misreading you.
Quoth wikipedia:
"A journaling file system is a file system that keeps track of the changes that will be made in a journal (usually a circular log in a dedicated area of the file system) before committing them to the main file system. In the event of a system crash or power failure, such file systems are quicker to bring back online and less likely to become corrupted.[1]"

Read the sentence after. Its very rare but it happens. Ext2/3/4 filesystems are extremely robust. Much better than ntfs and the like. On most other file systems its very likely a hard reboot will corrupt data. Its super rare on journaling file systems but there is a possibility. I just wanted to point out the difference in that post not scare people into not hard rebooting if the need arises.
Sent from my LG-P999

LG Fathom VS750 Android development

Well, since our old thread was locked, and since I'm continuing the development, the new thread is here. Many thanks to ajeet17181 for giving me the final piece of the puzzle to resume the work.
​
I am continuing ajeet17181's work on bringing a working Android build to our Windows Mobile phone, the LG Fathom. As of this moment I am only working on the Kernel, where most of the fixes need to be worked on, so let's get to it, shall we?
Download any of the following Android versions:
Gingerbread 2.3.7 (includes Kernel build #119)
DOWNLOAD "einsteinecker_android.rar" (thanks to pizzaboy192 for hosting)
alternate link (untested upload)
What works:
-3G data
-Wifi
-Limited Bluetooth functionality
-Video playback
-3D gaming
-Accelerometer
-Outgoing calls
What doesn't work:
-Camera
-Incoming calls
-SMS
-Vibrator
-Light sensor
-USB
-SD card has a low chance of being mounted.​
-
Latest Cyanogenmod Nov 26, 2012
Cyanogenmod with working audio fix, updated link August 28 2013:
Part 1
Part 2
(split into 2 parts because my internet kept cutting it off)
Dead link
Thanks to www2287. Read this post for more info.​
-
In some cases, the usual Google apps aren't built into the rom. Read this or this on how to get them.
-
Unsupported Android builds
ajeet's LG Fathom Gingerbread 2.3.7
Download here
What works:
-3G internet!
-Accelerometer!
-Wifi
-Real USB support.
-Outgoing calls
What doesn't work:
-D-pad is not aligned correctly.
-Cannot power off from shutdown menu.
-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.
-No camera
-No SMS
-Cannot receive calls
-No light sensor
-No vibrator
Cyanogen Mod
Download here (link thanks to Giorgi-geo)
-
Cyanogen March 2012 build
Download here. from www2287. This build is not a final build, that means many things are broken in it.
-
Android 2.2 Froyo
Download here (NOTE: Due to Froyo not working in some areas, I will not provide support for it)
-
LATEST KERNEL: (March 14 2013)
ReRun March 13 2013: New compiling method to fix several bugs. Read this post for more info.
Previous Kernel:
Rerun kernel build #120
Rerun kernel build #119 (This kernel is a restart of my previous work. I basically started over from scratch and compiled it well over 100 times to find an acceptable solution to the battery issue.)
(Can't type the "." symbol? Download this.)
Kernel source:
https://github.com/ajeet17181/fathom-kernel Note: this source is broken, and since I have heavily modified it, wait for me to upload full source someday.​
Booting Android​-Now, to use it with one of the above Android versions, first extract the android version into your MicroSD card (You must have at least 750MB free space on your card), and then copy the 3 files inside the kernel archive into the Android folder, overwriting any older files. Next, open startup.txt and make sure the line "rel_path=fathom" has the name of the Android folder in your microSD card, if the folder is "2.2", change "fathom" to 2.2.
-Same as usual, run clrcad.exe about 5 times, then click on "haret" .exe file. The kernel will take a while to boot, so let it sit.
Preparing your phone to enable 3G internet on Android
Now that you have the ROM, you will need to edit your phone to enable 3G internet. 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
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. ​
Current developments: Next phase of development will focus on the phone side (calls, sms, data). Because I am in a GSM country, I will be focusing on that.
Note: I am quite a busy person, and I won't be updating everyday, at the moment I have a grave matter to handle, and it is my 1TB hard drive. It has corrupt sectors, and it needs to be replaced. It holds crucial XDA data on it, so it is important to me. At the moment I can't afford a new one, so any donations is greatly appreciated in helping me remedy that problem. You can read more about my Hard Drive here.

Changelog
Latest Kernel:
March 14 2013
ReRun New Compile
This kernel was compiled differently than previous kernels, intended to join together the incompatible drivers with the rest of the drivers. This fixed several problems. Read here for more info.​
-
November 23, 2012
ReRun kernel build 119
This kernel was restarted from the beginning, and slowly configured to the point where I found a solution to the "connect charger" error on boot. Basically, the kernel source had conflicting power settings combined from the HD2 and Tsunagi sources, and I simply removed the HD2 battery settings and provided a new working source code for the battery. I expect to use this as a base as I further eliminate the invalid .32 codes and replace it with .35 sources.​
-
einstein 4x1 (NOTE: read any "readme.txt" files for instructions!!)
-Now, phone will no longer reboot when booting into android. You must make sure your battery level is over 26% in order to avoid this Reboot of Death bug, as it seems like the current build will reset if Android is in a mode where it will warn you to connect your charger. Perhaps we can change Android's low battery notification?
-NVRAM now pointed to /system/etc/wifi/, be sure to root copy the nvram.txt file into the new location.
-(for my modified Gingerbread build) attached are the correct key layouts for the Fathom hardware keyboard (thanks to www2287​
Extreme Battery 003
-Re-started kernel development to ensure junk drivers were no longer included. This led to working Wifi, partial bluetooth, fully working headphone support, accelerometer, and as before, no immense power drain on standby. Overnight standby now a reality with Kernel 003!​
Extreme Battery 002
Fixes:
-Wifi for Froyo, Bluetooth for Gingerbread
-Accelerometer works for Gingerbread only
-Headphones now work without fail
-Need more feedback regarding resetting while phone is on or off​
Extreme Battery 001
Features:
-More CPU governors
-Overclock enabled (use at your own risk!)
-Extreme battery saving (need confirmation, my battery only dropped 2% overnight!)
Working:
-Main speaker
-Phone earpiece
-d-pad now aligned properly
-No more torn screen on the left side!
-Real power-down! Power button is the task manager button beside the camera button. Press this to turn your phone on or off.
Not working:
-Same as before, no outgoing SMS
-Wifi is dead :silly:
-Camera not working
-Never tried GPS...
-When headphones are plugged in, sound dies globally in Android.​

Frequently Asked Questions
Where's my microSD card?
It seems strange, but this way worked for me: before you boot into Android, remove the sd card from your phone, then insert it, and then immediately boot into Android. If you did not do this when booting Android for the first time, do this method.
I'm low on storage space.
In "startup.txt", change "data_size=256" to "data_size=512" for 512MB of storage space. If you want more, change 512 to 1024 or 2048 for 1GB / 2GB respectively. Make sure you have that much free space on your MicroSD before you continue!
Can't start Froyo 2.2?
When you see the system process error, immediately press the side button beside the camera, then choose wait, then hold side button, then select power off, and the phone should look like it's booting again, and it should go into Froyo. If it doesn't, repeat again.
Can't boot into Gingerbread 2.3?
Due to a fault in ajeet's battery driver, the OS does not know what the battery life is at boot, and it thinks the battery is dead. Solution? Just make sure you have at least 70% or higher battery life when you boot into Android. I will try to focus on this, but as of the moment, I have not had much success in porting drivers into the kernel, as it is a rather complicated process and it has to be done in a way that will not break the wifi again. (This issue has been fixed in ReRun kernel build 119)

Reserved

Awesome that we have someone working on this again. Slightly curious how hard it would be to port this work over to OpenWebOS... But I'll love to see where Android goes. I'd try using it if the CDMA radio worked.

pizzaboy192 said:
Awesome that we have someone working on this again. Slightly curious how hard it would be to port this work over to OpenWebOS... But I'll love to see where Android goes. I'd try using it if the CDMA radio worked.
Click to expand...
Click to collapse
I'm optimistic CDMA would work, that unfortunately might need to have the Android OS edited to support dual mode CDMA/GSM. A nice place to start would be the Android builds for the Touch Pro2.

einsteinecker said:
I'm optimistic CDMA would work, that unfortunately might need to have the Android OS edited to support dual mode CDMA/GSM. A nice place to start would be the Android builds for the Touch Pro2.
Click to expand...
Click to collapse
We should also see what other Android-only devices used the same modems. The Droid series usually were world devices, as were a few others (none off the top of my head, but I bet they're pretty easy to find)
Worst case scenario would be to compile two different Android versions that are either CDMA only or GSM only.
I've got 3 Fathoms to test on, and would be more than willing to sell my unlocked one to someone who could use it better than I could (it's currently de-activated and I don't have a GSM SIM to test.

nice! thanks for your work einsteinecker

so here's my problem. i did everything as said. HTC logo comes on and that's it. i waited for 40+ minutes for it to load but nothing
edit: never mind. On the third try it loaded correctly
---------- Post added at 09:38 PM ---------- Previous post was at 09:00 PM ----------
-No more torn screen on the left side!
-Real power-down! Power button is the task manager button beside the camera button. Press this to turn your phone on or off.
Click to expand...
Click to collapse
love you. please fix wi-fi soon )
---------- Post added at 09:44 PM ---------- Previous post was at 09:38 PM ----------
i was using 2.3.1 android before this. now i installed 2.2 and the difference in performance is huge. 2.2 is much faster and smoother on our device. can you tell me what is the key difference between 2.3.1 and 2.2? if there is none I think it will be better to have 2.2
forget this too. looks like both build work better with your help )

Also. when in android, and i connect USB and transfer some files onto sdcard. they dont show up in file manager until reboot, and sometimes they just disappear. this is happening since first ajeet build - not a new problem, but maybe you could look into it.
---------- Post added at 02:47 AM ---------- Previous post was at 02:36 AM ----------
Not working:
-Same as before, no outgoing SMS
-Wifi is dead :silly:
-Camera not working
-Never tried GPS...
-When headphones are plugged in, sound dies globally in Android.
Click to expand...
Click to collapse
bluetooth also does not work )

Sorry folks, I meant to update yesterday but I had a mind crushing headache
pizzaboy192 said:
We should also see what other Android-only devices used the same modems. The Droid series usually were world devices, as were a few others (none off the top of my head, but I bet they're pretty easy to find)
Worst case scenario would be to compile two different Android versions that are either CDMA only or GSM only.
Click to expand...
Click to collapse
I recall most Droids from Motorola have the OMAP cpu, so I'm not sure if using the code for that would work on our Qualcomm stuff (I believe LG used a Qualcomm reference guide for the Fathom). I figured checking Qualcomm's sources first is a good try.
I've got 3 Fathoms to test on, and would be more than willing to sell my unlocked one to someone who could use it better than I could (it's currently de-activated and I don't have a GSM SIM to test.
Click to expand...
Click to collapse
I've been interested in something. How is android on the newer updates? What I mean is that, I'm still running stock V4 Windows Mobile ROM on my Fathom, and there is no performance lock like on the HTC HD2 (full 1Ghz on battery). Does the V5 or V7 WM Roms have this too?
Giorgi-geo said:
i was using 2.3.1 android before this. now i installed 2.2 and the difference in performance is huge. 2.2 is much faster and smoother on our device. can you tell me what is the key difference between 2.3.1 and 2.2? if there is none I think it will be better to have 2.2
forget this too. looks like both build work better with your help )
Click to expand...
Click to collapse
One main difference I see between 2.2 and 2.3, is that 2.3 rotates the screen immediately after you slide out the keyboard. 2.2 will only rotate once you open a program.
Giorgi-geo said:
Also. when in android, and i connect USB and transfer some files onto sdcard. they dont show up in file manager until reboot, and sometimes they just disappear. this is happening since first ajeet build - not a new problem, but maybe you could look into it.
Click to expand...
Click to collapse
If you read the readme text file inside the 2.2 Android build, you'll see it's a problem of the OS:
"- USB Mass Storage (You can copy files from PC to PC. But Android apps cannot see the copied files in the phone before rebooting.)"
I think that is because we run Android from our SD card.
bluetooth also does not work )
Click to expand...
Click to collapse
Thanks for the feedback. I was going to upload the headphone fix yesterday, but maybe I'll try that bluetooth fix too.

einsteinecker said:
I recall most Droids from Motorola have the OMAP cpu, so I'm not sure if using the code for that would work on our Qualcomm stuff (I believe LG used a Qualcomm reference guide for the Fathom). I figured checking Qualcomm's sources first is a good try.
I've been interested in something. How is android on the newer updates? What I mean is that, I'm still running stock V4 Windows Mobile ROM on my Fathom, and there is no performance lock like on the HTC HD2 (full 1Ghz on battery). Does the V5 or V7 WM Roms have this too?
Click to expand...
Click to collapse
I am not sure what the differences between the OMAP refrence and the Qualcomm refrence designs are. I know the Fathom is a 1ghz Snapdragon, but not sure what else it has in it.
Also, what do you mean by performance lock? I run my own ROM (V6) and it seems to run well. I don't do OC, but I have successfully underclocked the device to 215mhz (somewhere around there) as a test and it was stable. Eeked almost two weeks of battery out of a test device that way.

maybe you could fix wi-fi too? it was working before, so if you could compare the code you could probably fix it fast.
---------- Post added at 12:42 PM ---------- Previous post was at 12:19 PM ----------
one more thing. in android it only shows 165mb ram
---------- Post added at 12:54 PM ---------- Previous post was at 12:42 PM ----------
IMPORTANT: when going back to Windows Mobile, do not, I repeat DO NOT reset the phone while Android is off (screen off, standby). Make sure Android is on before you go back into Windows Mobile, if you don't, Android will be locked into an eternal "off" state, and you will never be able to go back into Android again.
Click to expand...
Click to collapse
I think this just happened to me. every time i load android it goes to unlock screen and then turns off. i always turned android off from its own menu so i dont know why it happened. there has to be a way to fix this, help please?
---------- Post added at 01:46 PM ---------- Previous post was at 12:54 PM ----------
after 5 tries, i connected phone with charger and on the second try it turned on

Hi folks, after my previous build work for headphones and not Bluetooth, I tried fixing Bluetooth but now the headphone port is wonky :silly:
While that was happening, I found out why Wifi wasn't working. Now, on 2.3 Gingerbread Wifi doesn't work (probably firmware problem), but in 2.2 Froyo it does work, but can't find any networks
That's when I was trying to fix things on the Android side (not the kernel) when I apparently got one thing to partially work:
I hope you noticed the 3G icon on the top, yes it's very close to working, the only problem I've got is making the phone realize that there is a sim in there (and the outgoing number to dial). Now, 2.3 Gingerbread can see the sim, so I'm going to try that, but if this works, I think we're in for a heck of a ride
Once I have both headphone and Bluetooth support stabilized, I will upload that. The 3G and Wifi fixes involve the Android OS itself, so that means I have to uploaded the OS or give instructions how to patch them in yourself.
pizzaboy192 said:
I am not sure what the differences between the OMAP refrence and the Qualcomm refrence designs are. I know the Fathom is a 1ghz Snapdragon, but not sure what else it has in it.
Click to expand...
Click to collapse
Well I certainly won't rule anything out. Right now any thing is a good thing to test, who knows, maybe the Droid actually has what I'm looking for
Also, what do you mean by performance lock? I run my own ROM (V6) and it seems to run well. I don't do OC, but I have successfully underclocked the device to 215mhz (somewhere around there) as a test and it was stable. Eeked almost two weeks of battery out of a test device that way.
Click to expand...
Click to collapse
Performance lock is like this: when I had the HD2, while on battery (no AC plugged in) the phone will have only a maximum speed of 768Mhz. My Fathom does not have this, it is a max 1Ghz on battery and on AC. What I'm wondering is, maybe LG's V5/V6/V7 updates changed something, I'm not sure. I sure don't want to risk my only phone either, and there's more: what if all this time LG's updates also updated the phone baseband. So while I'm porting Android to our phones, maybe my updates won't work with the old V4 I'm running. There certainly is a lot of things to consider when doing this stuff :silly:
Giorgi-geo said:
I think this just happened to me. every time i load android it goes to unlock screen and then turns off. i always turned android off from its own menu so i dont know why it happened. there has to be a way to fix this, help please?
Click to expand...
Click to collapse
I think there might be a way to fix this, unfortunately I have had little succes porting drivers over to my kernel. It is one of the reasons why I can't get the camera to work yet, porting drivers is not as simple as copying and pasting drivers like in windows mobile.
But I think it could work, you see, my idea was to tell Android that there's a reset button onboard the phone (the one beside the charging port). LG has the code for this, which I was able to see, but haven't been able to get working yet.
Edit: Wifi is still dead on 2.3 Gingerbread, but I fixed the Accelerometer :victory:
Couldn't test Froyo because I broke the Android build, will redo and continue further tests

Awesome work! I'll run some tests on my end with the CDMA half if you'd like and report back to see what is and isn't working connectivity wise there.
As for the WiFi half: is it getting an IP address? Can you check the DNS settings to make sure they are being set properly?
As for the performance lock: none that I know of.
And as for the question about baseband: No baseband differences between ROM versions. They're purely a WinMO flash, and not a BaseBand flash. If you'd like, I can run tests on all 3 OEM versions of the ROM though, as I have 3 unused Fathoms, all on different ROM versions currently. I've even tried cooking a WinMo ROM that autoboots into Android (almost works, tempted to just put a HaRET shortcut in startup and strip out all WinMO core programs.

Froyo doesn't like my kernel anymore, even tried a different SD card and it still has a system crash on boot. I guess it's time to work on a new OS :crying:
pizzaboy192 said:
As for the WiFi half: is it getting an IP address? Can you check the DNS settings to make sure they are being set properly?
Click to expand...
Click to collapse
It's just scanning, it won't even find the network
And as for the question about baseband: No baseband differences between ROM versions. They're purely a WinMO flash, and not a BaseBand flash. If you'd like, I can run tests on all 3 OEM versions of the ROM though, as I have 3 unused Fathoms, all on different ROM versions currently. I've even tried cooking a WinMo ROM that autoboots into Android (almost works, tempted to just put a HaRET shortcut in startup and strip out all WinMO core programs.
Click to expand...
Click to collapse
Oh, that's what I wanted to know, if the LG updates include a radio update. I'm highly interested in knowing if there will be better performance in Android if they updated the radio.

einsteinecker said:
Oh, that's what I wanted to know, if the LG updates include a radio update. I'm highly interested in knowing if there will be better performance in Android if they updated the radio.
Click to expand...
Click to collapse
We could also see what other devices used the same radio chip. I know that plenty of them are out there, it's just a matter of finding one that will provide an updated baseband and see how badly it screws up the phone (since we don't have the OEM baseband, doing that would probably brick any device you modded, if it went wrong)
How are you doing your work? any possibility of throwing it on some place like github so that people like me can try out changes and put our own in to help out? I have a test fleet just sitting doing nothing since I can't get much more out of Windows Mobile and cooking ROMs has gotten rather repetitive.

pizzaboy192 said:
We could also see what other devices used the same radio chip. I know that plenty of them are out there, it's just a matter of finding one that will provide an updated baseband and see how badly it screws up the phone (since we don't have the OEM baseband, doing that would probably brick any device you modded, if it went wrong)
How are you doing your work? any possibility of throwing it on some place like github so that people like me can try out changes and put our own in to help out? I have a test fleet just sitting doing nothing since I can't get much more out of Windows Mobile and cooking ROMs has gotten rather repetitive.
Click to expand...
Click to collapse
The kernel source is in the first post That's all I'm doing now, I get discouraged when I see the steps I have to take to make the Android OS, neither ajeet or www27 uploaded that and it's going to be a lot to download (I have limited bandwidth) What I've been doing is modifying Android while it's running (root access), and that's how I applied the accelerometer and that 3G thing.
Tomorrow I will upload the latest fix, which includes:
-bluetooth support (paired with headset and able to receive files)
-headphone support fixed
-how-to for the accelerometer (I will add a game so you can test it )
I'm currently prioritizing 3 things: why the SD card doesn't always mount on boot, charging the phone while using Android, and why my kernel doesn't like Froyo and the fixes that used to work.

einsteinecker said:
I'm currently prioritizing 3 things: why the SD card doesn't always mount on boot, charging the phone while using Android, and why my kernel doesn't like Froyo and the fixes that used to work.
Click to expand...
Click to collapse
what's wrong with charging? i dont see any problems

Random question: any way to get the Android main to boot off the internal flash? if so, I could build "ROMs" that boot WinMo and immediately start HaRET and handoff to Android. I tried earlier, but ended up with a failed boot every time.

[Q] Picture mail not working, Phone number is wrong?

Okay, So I checked my MMS settings and changed them. They're correct based on everything I've seen.
After that. I've discovered my phone number says its 000-000-8642
im running CM 10.0
I need to change this.
I cannot send picture mail currently. This pisses me off
But what could be going on?

captainwtf said:
Okay, So I checked my MMS settings and changed them. They're correct based on everything I've seen.
After that. I've discovered my phone number says its 000-000-8642
im running CM 10.0
I need to change this.
I cannot send picture mail currently. This pisses me off
But what could be going on?
Click to expand...
Click to collapse
CM10's not used a lot here anymore, as most are in cm10.1, but here are a few things:
I'm on cm10.1, and am working off it, but may be able to help:
first, need to check your IMEI: where you found that your phone number is 000s check your IMEI. should be about 14-15 numbers. If you still have it, then check your network settings
go into menu, system settings (or something like it) look for mobile networks. on cm10.1 it is in "more..." roll down to network mode and make sure you are on LTE/ CDMA / EvDo
then go to CDMA subscription (again or something like it) and make sure you are on CDMA/RUIM and not NV
if all of these are set, and you still can't get your number to show up, would sugest either trying to clean flash another ROM, or you can ODIN back to stock, and start over.
sorry, nothing i have is CM10 so am working in the dark here
:cyclops: