Related
Thanks to Kallt_kaffe http://forum.xda-developers.com/showthread.php?t=700669 for his build : all you want is working very good...
I use the latest DZO kernell http://it029000.massey.ac.nz/vogue/files/?C=M;O=D or the modify file by Kallt_kaffe himself http://forum.xda-developers.com/showthread.php?t=660158 with the the Loserskater NBH editor http://forum.xda-developers.com/showthread.php?t=689812 for choice the good panel for our phone
what is fully good in this build :
- phone of course... and very very fast
- battery : you have to use last kernel of DZO...
- Wifi : no problem
- BT : no problem
- MMS : you can receive and send
- GPS with Igo : a bit slower after first installation
- GPS with Navigon : very fast
- synchronize data ok
- market (I think full but I'm not sure)
- live wallpapers
- and more and more...
I installed in nand.
I use it with ADW launcher : very beautiful and fast !!
I think you have to do all Kallt_kaffe advise for his build work well...
THANKS for them !!
Hope it works for all of Polaris users.
AND you can now upgrade your radio with this version 1.65.38.14
See the thread for this new version here...
Cheers.
manu33xtro said:
Thanks to Kallt_kaffe http://forum.xda-developers.com/showthread.php?t=700669 for his build : all you want is working very good...
I use the latest DZO kernell http://it029000.massey.ac.nz/vogue/files/?C=M;O=D or the modify file by Kallt_kaffe himself http://forum.xda-developers.com/showthread.php?t=660158 with the the Loserskater NBH editor http://forum.xda-developers.com/showthread.php?t=689812 for choice the good panel for our phone
what is fully good in this build :
- phone of course... Sometimes a bit slower when you want to make a call or in a call end (maybe Eclair or kernel... I have make a lot of test but not sure for the results...)
- battery : I don't know why but sometimes I see 30% and a few minutes after my phone is completly discharge !!
- Wifi
- BT : not yet for carkit
- MMS : you can receive and send
- GPS with Igo : a bit slower after first installation but if you use odex file, It's much better
- synchronize data
- market (I think full but I'm not sure)
- live wallpapers
I installed in nand and modify userinit.sh for enable automatic odexing.
I use it with launcherpro : very beautiful and fast !!
I think you have to do all Kallt_kaffe advise for his build work well...
Maybe just one (big ?) problem : I lose sometimes network ! just few minutes but when you want to call... It's a problem : you have to wait few seconds to have a new good signal...
THANKS for them !!
Hope it works for all of Polaris users.
Cheers.
Click to expand...
Click to collapse
I can recommend it, too. For me, it's faster than Myn's Eclair RLS1. By the way, I managed to connect to my car kit successfully out-of-the-box with the latest kernel (.NBH). It experiences some slowdowns when running memory intensive applications and you switch back to, for example, Home Screen, but it's really good.
Congratulations to kallt_kaffe.
Nice!!
Its the same speed level as myns eclair rls 1.
For me its more stable than myns, but maby i made crap ;D
-----
The behavior when stressed is different from myns.. i got these lack untill the homescreen apears too. But overall it looks more stable.
How can i get these dots in the corner to switch home screens?
Can i change the way the middle button(all apps) behaves? In myns there is full screen and all apps are flying in, in this build the slider goes up, but it "feels" a bit small compared to myn :/
(and a offtopic question: nexusmod wallpaper from market dosnt work. is there a nexus like live wallpaper? Cant find the orginal one, i think its not in the market)
This is the only build working Wifi/BT for my Pola100, with PAIPO Zimage of 26/03/2010 !!!
It's a GREAT BUILD ... Maybe a bit slower than Myn's Eclair, but works perfectly!!!
Only a question:
- When I try to install "LAUNCHERPRO" ... AFTER installing nothing change on "Home" Screen. Nothing.
How Installing Launcherpro correctly ?
(My installation is on SD with Haret, Not NAND).
Please any help is appreciated.
Thanks in Advance.
SuperJMN said:
I can recommend it, too. For me, it's faster than Myn's Eclair RLS1. By the way, I managed to connect to my car kit successfully out-of-the-box with the latest kernel (.NBH). It experiences some slowdowns when running memory intensive applications and you switch back to, for example, Home Screen, but it's really good.
Congratulations to kallt_kaffe.
Click to expand...
Click to collapse
I use this version of rom with a brand new battery. I use it about 2 houres, approx. 15 minutes of talk time and small WIFI and the battery is 70 percent. Is there any way increase uptime?
Hi, can you tell me which version of nbh and zImage do you use?
Use latest nbh and wait same days. The dzo kernel recalibrate the battery use.
The power drain is a quite big problem for our device :-(
I think you have to press one time on power button and a toolbox is coming to make your choice for launcherpro.
Cheers.
foxct2005 said:
This is the only build working Wifi/BT for my Pola100, with PAIPO Zimage of 26/03/2010 !!!
It's a GREAT BUILD ... Maybe a bit slower than Myn's Eclair, but works perfectly!!!
Only a question:
- When I try to install "LAUNCHERPRO" ... AFTER installing nothing change on "Home" Screen. Nothing.
How Installing Launcherpro correctly ?
(My installation is on SD with Haret, Not NAND).
Please any help is appreciated.
Thanks in Advance.
Click to expand...
Click to collapse
Hi SuperJMN,
Well I tryed to connect with my audio car : It's ok but no sound, I grew just a breath !!!
Do you have a kit included in the car or like a radio ?
Thanks.
Cheers.
SuperJMN said:
I can recommend it, too. For me, it's faster than Myn's Eclair RLS1. By the way, I managed to connect to my car kit successfully out-of-the-box with the latest kernel (.NBH). It experiences some slowdowns when running memory intensive applications and you switch back to, for example, Home Screen, but it's really good.
Congratulations to kallt_kaffe.
Click to expand...
Click to collapse
I think you should install launcherpro...
dertester123 said:
Nice!!
Its the same speed level as myns eclair rls 1.
For me its more stable than myns, but maby i made crap ;D
-----
The behavior when stressed is different from myns.. i got these lack untill the homescreen apears too. But overall it looks more stable.
How can i get these dots in the corner to switch home screens?
Can i change the way the middle button(all apps) behaves? In myns there is full screen and all apps are flying in, in this build the slider goes up, but it "feels" a bit small compared to myn :/
(and a offtopic question: nexusmod wallpaper from market dosnt work. is there a nexus like live wallpaper? Cant find the orginal one, i think its not in the market)
Click to expand...
Click to collapse
Faster than newest Warm Donuts newest Android RLS5?
Hey guys,
is this android version fastern than Warm Donuts RLS 5?
thanks...
manu33xtro said:
Hi SuperJMN,
Well I tryed to connect with my audio car : It's ok but no sound, I grew just a breath !!!
Do you have a kit included in the car or like a radio ?
Thanks.
Cheers.
Click to expand...
Click to collapse
Manu33xtro, now that you mention it, I connected the car audio but I didn't test it. I'll have to make some tests to see if it works properly. It's a Parrot CK3100-LCD.
New build : Cm5.0.8
Maybe yes but you should test it...
And now Kallt_kaffe has release a new build port of CM5.0.8 : I will test it right now
Cheers.
Pr3d1ction said:
Hey guys,
is this android version fastern than Warm Donuts RLS 5?
thanks...
Click to expand...
Click to collapse
manu33xtro said:
Maybe yes but you should test it...
And now Kallt_kaffe has release a new build port of CM5.0.8 : I will test it right now
Cheers.
Click to expand...
Click to collapse
i'm so curious about it !!
Hi,
What version of IGO you are using? Where did you get 320x240 version? I have found modified data.gro, but still not perfect.
Usnig this build since RL2. Some remarks:
- overclocked with Rogue tools to 450 MHz -> runs smoother. But phone must be charged every day.
- cant understand the logic how calls end. Some times it ends exactly after caller disconnects. Sometimes no, disconnects after some time.
- WiFi on/off. My network has hidden SSID. WiFi turns on, but don't connects to network. I have to go Settings -> WiFi settings, and then phone connects to network
- GPS works, but sometimes looses satelites. Can be fixed with phone restart.
- Battery on RL3 stuck on 100%
Phone working, SMS working, battery life is ok for me.
Update:
with RLS5 looks like phone don't charges -> stuck on 15%
Leryan said:
Hi,
What version of IGO you are using? Where did you get 320x240 version? I have found modified data.gro, but still not perfect.
Click to expand...
Click to collapse
Hi,
where did you find the data.gro file on your phone?!?!
Data.gro is located: /data/data/com.navngo.igo.javaclient/data.gro
I can send you pm with link to modified file tomorrow.
Try it right now : much better than RSL3b... I will post my test later (after more test...)
chourmovs said:
i'm so curious about it !!
Click to expand...
Click to collapse
The last version : 139242 (look at PPCWAREZ). But like you, the data.gro is not perfect and I find IGO a bit slower and lose sometimes the GPS position ! I will try with the CM5.0.8.
- I doesn't use overclocking
- same effect for calls but i think it's better with this last build : I wait to do more tests
- Wifi works good !?! I see all networks... Maybe with the last kernel ??
- same for us, the battery life must be better : DZO know this problem
Leryan said:
Hi,
What version of IGO you are using? Where did you get 320x240 version? I have found modified data.gro, but still not perfect.
Usnig this build since RL2. Some remarks:
- overclocked with Rogue tools to 450 MHz -> runs smoother. But phone must be charged every day.
- cant understand the logic how calls end. Some times it ends exactly after caller disconnects. Sometimes no, disconnects after some time.
- WiFi on/off. My network has hidden SSID. WiFi turns on, but don't connects to network. I have to go Settings -> WiFi settings, and then phone connects to network
- GPS works, but sometimes looses satelites. Can be fixed with phone restart.
- Battery on RL3 stuck on 100%
Phone working, SMS working, battery life is ok for me.
Update:
with RLS5 looks like phone don't charges -> stuck on 15%
Click to expand...
Click to collapse
You have to use root explorer or apk like this to replace the file...
Leryan said:
Data.gro is located: /data/data/com.navngo.igo.javaclient/data.gro
I can send you pm with link to modified file tomorrow.
Click to expand...
Click to collapse
Phone charged - left the phone charging over the night.
But when i connected charger, al least for 1/2 an hour, battery level stay at 15%. Maybe battery fallen below the critical level.
WiFi is working ok, when connected But when I turn it on, i have to go Settings -> WiFi settings. Otherwise nothing happens.
Update.
dzo released a new kernel, flashing right now
Leryan said:
Phone charged - left the phone charging over the night.
But when i connected charger, al least for 1/2 an hour, battery level stay at 15%. Maybe battery fallen below the critical level.
Click to expand...
Click to collapse
that's a classical eclair's build issue
Be patient, try some reboot and connect/deconnect your charger and after some charging/decharging cycle, battery accuracy will be better
slow..compare to incumbus, even after set cpu speed to 450
LATEST FIRMWARE:
I5800XXJPA for I5800 EUROPE (November 2010) - CLICK HERE - Android 2.2 FROYO (pass = samfirmware.com)
Please feel free to discuss about JPA firmware
Ciao
Just installed and restoring my apps. No bugs found yet.....
Compared to JP8 (the firmware I was using befor):
- Standard SMS is fully functional, but because of the beter groups sms functionality I will use Handcent again.
- Video (tested with an Divx file) is working again.
- Less lagtime.
But sill no good flash player....
Quite stable firmware. Most likely the official release coming soon.
Some bugs,
- the application file size displayed as number without the respective "Mb" or "Kb" unit. Ex. 4 megabytes displayed as "4".
- proximity sensor not working. When phone lifted off the ear, the screen display won't resumed back to dial pad. Probably not the sensor but some setting to be corrected.
- GPS still need small adjustment
- Powering off still take quite some time
- At times, the phone will be sluggish for no obvious reason ( but not common)
- 2.2 JIT built-into this release? Seems like not much speed improvement. I get an initialisation failed when i do adb shell dalvikvm -help
I am about to upgrade this on my i5801 (Asia), any suggestions? Please?
Last time I upgraded with I5800XXJP9 ## and used it, then after a restart my phone never started. I again had to install I5801DDJG6 # !
just fully charged my galaxy 3 and after 1h doing nothing with phone my battery have only 80%
I have some bugs:
- when somebody is calling the phone freezing, and the network is restarting, and i don't know who called me
- i don't can exit from Contacts, just with the Home button
- the phone don't receive the text messages
before i update to I5800XXJPA not hard reset the phone maybe this make the problems maybe not, i don't know
/Sorry my bad English/
Installed JPA. No problems found.
mobile9999 said:
- GPS still need small adjustment
Click to expand...
Click to collapse
any suggestion for gpsfix of this jpa firmware?
the only way is rooting (with superoneclick, z4root and others didn't seem to work) and then use fasterfix ?
i have also a galaxy s and I used SGS tools to fix that (plus lbstestmode). does it work on galaxy 3 ?
thanks
ps: jpa is a good fw in my opinion
abibibi said:
any suggestion for gpsfix of this jpa firmware?
the only way is rooting (with superoneclick, z4root and others didn't seem to work) and then use fasterfix ?
i have also a galaxy s and I used SGS tools to fix that (plus lbstestmode). does it work on galaxy 3 ?
thanks
ps: jpa is a good fw in my opinion
Click to expand...
Click to collapse
JPA works fine until now. 2 hours of testing. No wifi drop error, no freezing.
No GPS though..
I'm exactly in your position, got an SGS too, so if u find out anything pls send a PM.
Thanks.
If you are in the europe region, most likely you don't have to fix the gps.conf. Just run the gpssetup2 and finetune some of the parameters. Else, you have to get rooted and use fasterfix or edit gps.conf manually.
Not too sure about the SGS tools.
abibibi said:
any suggestion for gpsfix of this jpa firmware?
the only way is rooting (with superoneclick, z4root and others didn't seem to work) and then use fasterfix ?
i have also a galaxy s and I used SGS tools to fix that (plus lbstestmode). does it work on galaxy 3 ?
thanks
ps: jpa is a good fw in my opinion
Click to expand...
Click to collapse
I noticed a very critical issue with this JPA release. The phone will become unstable or hang when loading more memory intense apps. For example, i tried loading a trace.txt file, after exit, the phone became sluggish and not responsive.
If you are normal usage, probably not a concern.
try hard reset again. I encountered this before, after hard reset, set the APN entry right, it will be alright.
Diesel1017 said:
I have some bugs:
- when somebody is calling the phone freezing, and the network is restarting, and i don't know who called me
- i don't can exit from Contacts, just with the Home button
- the phone don't receive the text messages
before i update to I5800XXJPA not hard reset the phone maybe this make the problems maybe not, i don't know
/Sorry my bad English/
Click to expand...
Click to collapse
mobile9999 said:
If you are in the europe region, most likely you don't have to fix the gps.conf. Just run the gpssetup2 and finetune some of the parameters. Else, you have to get rooted and use fasterfix or edit gps.conf manually.
Not too sure about the SGS tools.
Click to expand...
Click to collapse
You got any idea how to finetune it ?
i tried
Dail: *#*#3214789650#*#* --> settings --> Parameter Settings --> SSL --> I disabled it and changed it to Google Server. After that I changed Start mode to "Cold Start" and restarted the device.
Again dialed *#*#3214789650#*#* --> Commands --> Get positions, and wait 30 sec for an fix.
Back to settings --> Parameter Settings --> Start mode --> and changed it back to Hot Start. Restart device again.
i installed GPS Test and it got connected to satellites but is the a navigation software i can use ? I have iGO Amigo in my SGS 800*480, but on 400*240 i didn't find anything.
airpd said:
You got any idea how to finetune it ?
i tried
Dail: *#*#3214789650#*#* --> settings --> Parameter Settings --> SSL --> I disabled it and changed it to Google Server. After that I changed Start mode to "Cold Start" and restarted the device.
Again dialed *#*#3214789650#*#* --> Commands --> Get positions, and wait 30 sec for an fix.
Back to settings --> Parameter Settings --> Start mode --> and changed it back to Hot Start. Restart device again.
i installed GPS Test and it got connected to satellites but is the a navigation software i can use ? I have iGO Amigo in my SGS 800*480, but on 400*240 i didn't find anything.
Click to expand...
Click to collapse
Yes I did change with this secret code, but I must switch off and on the phone with enabled GPS - then it works fine. But it takes time to switch off and on the phone. Any suggestions ? I've tryed also OCTY application and others.
One day after installed:
battery at 80%
problem on restoring apps from Titanium backup
sms works ok
wifi works ok
good speed
gps buggy like always
stable
Can anyone confirm that proximity sensor still sucks? I mean sittuation when we finish call...
abibibi said:
any suggestion for gpsfix of this jpa firmware?
the only way is rooting (with superoneclick, z4root and others didn't seem to work) and then use fasterfix ?
i have also a galaxy s and I used SGS tools to fix that (plus lbstestmode). does it work on galaxy 3 ?
thanks
ps: jpa is a good fw in my opinion
Click to expand...
Click to collapse
is it better / faster / more stable than JP9 ?
airpd said:
i installed GPS Test and it got connected to satellites but is the a navigation software i can use ? I have iGO Amigo in my SGS 800*480, but on 400*240 i didn't find anything.
Click to expand...
Click to collapse
Hi, i use Ndrive, it is good on my opinion. Almost a perfect replacement for the iGo.
Hi team,
hope you can help me...I just rooted my phone, did everything what was needed before flashing a custom rom.
I tried the Android Revolution HD 2.1 custom rom, and it worked fine, but once I made my first phone call, the process com.android.phone started to consume 100% of my CPU, the phone started to be hot, battery rapidly down etc. The only thing helped was the restart and not to make phone call. I searched in the different forums, I tried the USB debugging and also to clear calendar cache, but nothing...I flashed a different kernel as well (Leddroid) but no luck...still the same issue, 100% cpu usage after a phone call.
I decided to flash another custom rom, which was Leedroid 2.2.0...was hoping that it will fix the problem, but again...phone call and cpu on 100%...the strange thing is, that this time it did not do right after the first phone call, but 2 days later. Tried to disable all the synchs, usb debugging, calendar cache etc. but still got this problem
Anybody can help please? I would appreciate
Weird..
I've noticed my phone burning my leg while its in my pocket randomly when im not using it? Maybe a bug on HTC's behalf.Download fast reboot off the market and try using that to kill all the apps, its the best one ive used and normally stops it being so hot
Thank you, but it did not help...it actually kills everything, but as soon as I make the next phone call, the CPU gets back to 100% :-(
Anybody can help please...I installed a different kernel as well, but no luck...tried stock, Leedroid kernel and still got the 100% cpu issue.
Perhaps a full wipe can help. Make a Backup before.
Thanks MysthMob...I tried that one as well...used the SuperWipe from mike and from Leedroid as well...reinstalled the custom rom, everything worked fine till the first phone call...than it went up again to 100%
I was thinking of that it is caused by any 3rd party app...I have these installed:
Advanced task killer pro
Battery widget pro
Automatic bluetooth dongle pro
You dont need a task killer! Sense has one built in called Low Memory Killer
Good to know thank you...just removed, but the problem still persist...I am tired to reboot the phone all the time I make a phone call.
If you still have problems i would send it back for repair, Maybe it has a hardware fault
Do not think so...it was working fine with stock Rom...its just in custom Roms..but with all? I flashed back stock Rom and its working fine, but I want a custom one, I think I do not need to explain why
I will probably go back to the stock rom :-(
Mike is planing to release his 3.0.1 version, maybe he will include a fix...will wait till he posts it
I have got HTC Sensation XE.(it is rooted,revolutionary s-off,super CID,unlocked).
My old ROM was ARHD 3.6.9 and i was really satisfied except it was a bit laggy so after witnessing people's admirations of this new ROM (ARHD 6.6.3) i decided to upgrade.
After all i installed the ARHD 6.6.3 but i have these new problems now:
1.My mobile screen turns on and off involuntarily what should i do?
2.Battery drains too fast in comparison to my previous ROM(ARHD 3.6.9) e.g today with only 3 calls and no other actions(no video and audio usage and no internet browsing)2 P.M in the afternoon i had only 23 percent juice.
Of course i think one of the main causes is that screen turn-on and off.
3.Wireless doesn't work at all sometimes it finds the wirelss networks and sometimes not.
After finding the net it can not connect and shows this message "not in range"
4.Before installing this ROM i succeeded to connect to my mobile through Adb and make it SuperCID but now adb does not recognize my mobile what has happened?
So i couldn't install the Radio.But in "About" option my Radio version reads 11.69..... is it still necessary to install it?
5.There is not any options in menus and settings for enabling GPS or i could not find the one.Of course after opening Maverick program ,GPS started but it is very laggy and after about 8 mins it found the location .Before this it was very speedy about 2 mins it could connect.So what should i do to bring that speed back?
6.Maps program does not work and steadily a message shows up "unfortunately Maps stopped"
What's the problem?
Some of my other programs does not work as well and this message shows up after trying to open them.
7.After these all i am really regretful and disappointed of this ROM.Why should i upgrade and face these all problems even i thought to sell my phone and change it.
8.Is there any way to downgrade or use main kernels from HTC to solve all of these?
I tried to downgrade my HBOOT from 1.27 to 1.17 and bring my old ROM back but i couldn't.
After flashing the old firmware(1.17 HBOOT) the system hung and couldn't start and only 4EXT recovery touch removed and Clockwork recovery recovered but the HBOOT version was still 1.27 and the system could not start.
Excuse i really bothered you people with my long questions.
1. Settings > Display. What does it say under sleep?
2. It take a few days for the battery to reach its full charge after flashing a new ROM.
5. Setting > Location > GPS Satellites or put a toggle widget on your homescreen.
6. Update maps?
7. If you really dont like it go back to your old ROM.
Personally ARHD 6.6.3 works perfectly for me.
i am a noob but i think i have answers to your questions
2) kernel problem? if you're using faux123 kernel, download System Tuner by 3c from market and make sure governor is intellidemand (it was ondemand by default for me for some reason), or reflash faux123 kernel
havent test with sebastianFM yet, sorrry
3) ICS WiFi bug?
5) Setting > Location > GPS Satellite, install GPS fix tweak?
based on my experience, gps lock speed varies by apps
for example, Sygic locate gps fast than HTC location most of the time
6) clear ur old map from ur SD card
Settings > Storage > (under SD card) Make more space > Maps
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.