I created a new thread for this because the old one was for development, and there's no more development
I finally decoded all the information GPS is providing, and updated the drivers to provide full GPS support.
Rootfs link below for those running from SD or NAND
This thread is for people who want the latest and greatest! As ROM builders integrate these libraries into their ROMs, you shouldn't have to come back here. GPS 5.0 is likely to stay, as I don't foresee any bugs.
Check out the old thread as well. Shidell put some work into an ADB how-to:
http://forum.xda-developers.com/showthread.php?t=616436
Rootfs with libgps5.0already pushed in (fixed some file permissions in this version and verified libgps is in there):
http://dl.dropbox.com/u/58383/rootfs-libgps5.0.zip
NBH (thanks jamezelle!):
http://5d698f86.linkbucks.com/
zImage and libgps.so attached! Rootfs above!
INSTRUCTIONS (SD): Replace your zImage and rootfs.img with the ones provided and reboot! (Put them in the android directory).
INSTRUCTIONS (NAND): Flash the new NBH. Then either flash the new rootfs.img, or adb push the library to your /lib/donut, /lib/eclair, and /lib directories.
Bugs remaining (I don't feel like hunting them down):
* Satellite reporting is finicky (this is an issue with the gps messages themselves). Satellites disappear and come back randomly. Only way to fix this is put in a state machine that combines satellite messages over multiple seconds. Also you'd need to prune satellites that are old. I implemented one, but had crashing issues so I ditched it.
* [Fixed] After booting, the first time you try to use GPS with Google Maps/Nav, it will fail. Exit out and re-enter and it will always work from then onward.
Changes:
-2.2: Fixed 'no position in maps/nav on first try after reboot'
-5.0: Fixed issue with negative altitudes, also rebaselined versioning to match versioning inside the software
For maximum compatibility, make sure you're running a 3.42.50 radio (CDMA):
http://forum.ppcgeeks.com/showpost.php?p=389964&postcount=8
Radio-only nbh that won't mess up your NAND.
Most newer NoMoRootfs (andboot) builds should already have this cooked in!
Kaiser zImage:
http://dl.dropbox.com/u/58383/kaiser_zImage.zip
(also any of dzo's newer zImages work)
i was using the previous zimage from 1/23/10 with rootfs 1/26/10 through sd card ext2. worked great. before that, I used the 1.4 version (the one before 1.5) without any problem (pushing the libgps.so).
however, with the 2.1 zimage and rootfs, the sattelite does not appear at all, after entering and exiting maps/gpstest numerous times and rebooting. any clue? going to try a few things (maybe will try pushing the libgps instead, or the old zimage) to see if I can sort it out.
You can try this one that uses a constant accuracy like the old ones to see if that fixes it. You'll have to push it.
The new lib uses 64-bit location values, which are much more accurate than the other things (this isn't causing your issue). The new one also uses different accuracy reporting, which android may not like.
Others: The above files definitely work, please don't use the attached.
Edit: Looks like I wasn't actually pushing libgps.so into rootfs! Don't use the below, it fakes the accuracy.
[Removed file]
I may have figured out what's causing the "no position lock on first try after reboot" problem. I put a fix together, it worked, but crashed the phone. I'll debug it later.
Tatnai's problem may be related. I'm assuming AGPS isn't working on his phone and that's causing the issue.
So with the new zImage, just drop that, along with your rootfs into the android folder, and that's it, right?
JacenSolo2001 said:
So with the new zImage, just drop that, along with your rootfs into the android folder, and that's it, right?
Click to expand...
Click to collapse
Yup, just put it in the android directory.
ok, done, and if GPSTest just sits there and never even gets 1 bar, is there an obvious reason or something that's messed up?
JacenSolo2001 said:
ok, done, and if GPSTest just sits there and never even gets 1 bar, is there an obvious reason or something that's messed up?
Click to expand...
Click to collapse
Whoops, I think my script was never actually pushing libgps to rootfs. I just looked and the timestamp is old. It may have been storing it in data.img. This means you're probably actually using the old libgps + new kernel = does not work.
I'm removing it for now. Either:
1) Go back to an old zImage/rootfs (I'll post a new one later)
2) Push it into android using shiddell's instructions: http://forum.xda-developers.com/showthread.php?t=616436
I'd appricate it if you'd do #2, so I can get testers to work out bugs (there shouldn't be any). However, I'll be putting out a libgps-2.2 later that fixes the "failed first lock on fresh reboot" bug, so I understand if you'll want until then for a new rootfs.
I may try the push tonight when i get in from work.
LOL, i had thought this was fairly "idiot proof", as you intended, so i was feeling like an idiot
Thanks again for all you're doing !
JacenSolo2001 said:
I may try the push tonight when i get in from work.
LOL, i had thought this was fairly "idiot proof", as you intended, so i was feeling like an idiot
Thanks again for all you're doing !
Click to expand...
Click to collapse
If you have ASTRO in your app tray, can you go to /lib and click-hold the libgps file. Hit details. What timestamp is it?
I don't have a /lib folder, i do have the file in my root directory for android, i just placed it there earlier when I got the zip file. The date for that is Jan 24
JacenSolo2001 said:
I don't have a /lib folder, i do have the file in my root directory for android, i just placed it there earlier when I got the zip file. The date for that is Jan 24
Click to expand...
Click to collapse
I'm talking about when android is booted (not /lib on the sdcard). It mounts the rootfs.img as a file system.
If you don't have a /lib directory, then it has to go in /system/lib
LD_LIBRARY_PATH usually only looks in /lib, then /system/lib
So it's possible I was pushing it into rootfs.img properly, and the modified timestamps aren't being updated.
Jan 26 2010
JacenSolo2001 said:
Jan 26 2010
Click to expand...
Click to collapse
Did you download the rootfs.img, or just put the libgps.so in the /sdcard/android directory.
Jan 26 is yesterday's update (libgps-1.6). Today's should be Jan 27th.
I'll include clearer directions when I push out a new libgps one last time that includes the latest bugfixes.
jnadke said:
Did you download the rootfs.img, or just put the libgps.so in the /sdcard/android directory.
Jan 26 is yesterday's update (libgps-1.6). Today's should be Jan 27th.
I'll include clearer directions when I push out a new libgps one last time that includes the latest bugfixes.
Click to expand...
Click to collapse
im going to make nbh's for the NAND flashers which files should i use
EDIT NVM seen your remark in post 3, im going to make nbh files with 2.1 zImage
jamezelle said:
im going to make nbh's for the NAND flashers which files should i use
EDIT NVM seen your remark in post 3, im going to make nbh files with 2.1 zImage
Click to expand...
Click to collapse
Thanks. This saves me from resizing my VMWare image to install Wine + LinuxPPCKitchen.
The zImage-2.1 should be final.
I'll be coming out with a libgps-2.2 which fixes the 'maps/nav no GPS first try after reboot' issue.
Apparently you need to set the HAS_ACCURACY flag all the time. I was trying to not set it if accuracy was 0.0. Apparently the flag not being there causes Maps/Nav to crash if position is reported. I did come out with a zImage-2.2 that checks if accuracy isn't 0 before sending a message to libgps, but this triggered random reboots (looks like it doesn't like this). Right now it just checks if a gpstime is being reported (which isn't right because it should report that even if no position lock is present).
I'm not sure what the proper method for Android GPS is to gracefully indicate GPS is lost, but the libgps-2.2 version on my phone seems to work with zImage-2.1.
jnadke said:
Thanks. This saves me from resizing my VMWare image to install Wine + LinuxPPCKitchen.
The zImage-2.1 should be final.
I'll be coming out with a libgps-2.2 which fixes the 'maps/nav no GPS first try after reboot' issue.
Apparently you need to set the HAS_ACCURACY flag all the time. I was trying to not set it if accuracy was 0.0. Apparently the flag not being there causes Maps/Nav to crash if position is reported.
Click to expand...
Click to collapse
here you go ppl use the rootfs in the first post!!! this contains all 3 resolutions for vogue only right now
NAND NBH FILES 2.1 "240 428 and 480"
btw jnadke im not getting a lock with this in 2.1(2.1 eclair btw) not sure if it is compatible
EDIT: pulled up maps and it rebooted phone ill try again
EDIT2: 10 min not one sat, so i backed out fof GPS Test and it rebooted phone
EDIT3: ok so im an idiot and didnt use your rootfs and pushed the lib to /lib and my init points to /system/lib lol so i fixed it all is well it works just fine
So does the rootfs.img file still need to be matched to the NBH file in some way? Is rootfs.img where the /lib directory is?
dmulligan said:
So does the rootfs.img file still need to be matched to the NBH file in some way? Is rootfs.img where the /lib directory is?
Click to expand...
Click to collapse
use the rootfs in the first post and the nbh's in my post on this page
i can confirm a lock
jamezelle said:
use the rootfs in the first post and the nbh's in my post on this page
i can confirm a lock
Click to expand...
Click to collapse
jnadke removed that file this morning.
Related
This is a very clean build of android / cupcake.
Credits for the kernel (zImage) go to DZO. This kernel is unmodified, it is his latest kernel
Credits for the system image go to many people, haykuro is the original source, then further modified by me to get data, market, and SD card working
The initrd is pretty much all mine now, with a radio library from DZO, srwalter, and myself
PROJECT HOME
HOW TO GET IT RUNNING
SCREENSHOTS!
DOWNLOADS
UPDATE 27-June-2009:
Updated initrd with new RIL that provides:
-Grabs your carrier's name instead of "Android" for cdma devices.
mssmison uploaded a new TheDude image with partially working music. Check out the screenshots!
UPDATE 26-June-2009:
Updated initrd that provides:
-Automated backups of your data, just press a key when prompted and it'll show up in /sdcard/backups
-Filesystem checking of the SD card, should keep things from getting corrupted and from files disappearing from SD
UPDATE 24-June-2009:
-mssmison uploaded his themes
UPDATE 23-June-2009:
-Updated initrd with new RIL that provides:
*fixed SMS for Bell
*preliminary GPS support
*boot options for the SMS fix and for lcd density
-Updated system.img that provides:
*updated Maps.apk
*removed recovery.img
*preliminary GPS support
-Updated zImage that provides:
*preliminary GPS support
UPDATE 21-June-2009 evening:
-Updated initrd with new RIL that provides:
*Bug fixes on the 3G notification icons, sometimes it would show disconnected when connected etc.
*Supports reading the ESN and phone number from the radio. Check settings->about->status, your ESN will show up under IMEI.
*No longer using mountd, should free up a little memory
UPDATE 21-June-2009:
-Updated initrd with new RIL that provides:
*EV/1X status monitoring (will show 3G for EVDO and G for 1XRTT connections)
*Doesn't show connected, and won't "try" to connect, when disconnected in Modem
*Mute works! And you can un-mute too
-Updated system.img that provides:
*data connections work on initial boot, does not require a reboot
UPDATE 20-June-2009:
-Updated initrd with better modem controls, plus new RIL that properly handles call waiting ID and VMI for verizon/others
-Automatic timezone and time/date now supported!!!
-Google Sign-on supported
-Proper radio initialization implemented
UPDATE 18-June-2009:
-Updated initrd to support both 1.1 and 1.5 android, including new libreference (for call waiting ID and voicemail notification)
-back to using zImage per DZO's updates.
UPDATE 10-June-2009:
now using zImage-adb
UPDATE 08-June-2009:
split up the archive, updated initrd.gz fixes a bug where mountListener needed vold (vold now started at boot)
Terminal
It looks like the developer's terminal isn't here in this release, just head to the market and download the better terminal that supports the on-screen keyboard.
Eventually I'll modify DZO's kernel to completely disable the blue keyboard, then the camera button will simply rotate the screen
Awesome fantastic work! Power collapse works perfectly and haven't come across any other bugs yet.
Thanks heaps.
Cheers
I can't get this version to run. I also can't get DZO's 1.1 version to run. But TheDude 1.5b will run. I'm not sure what's going on.
Edit:
If I replace the system file in TheDude's folder with the system in the Ion folder and run Haret then Ion will run. But it will not run with the files inside this zip
Thanks
Thanks for your efforts. I had built my own image last night but this one is a lot better than the one I made. Also has anyone tried the hero-saphire build? I built an image last night but couldn't get past the htc android boot splash. I would really love to see that new ui on the vogue.
aven_soulgazer said:
I can't get this version to run. I also can't get DZO's 1.1 version to run. But TheDude 1.5b will run. I'm not sure what's going on.
Edit:
If I replace the system file in TheDude's folder with the system in the Ion folder and run Haret then Ion will run. But it will not run with the files inside this zip
Click to expand...
Click to collapse
The only differences in the files from thedude's folder and from this one is 1)default.txt: I use different defaults than mssmison does
2)zImage: I custom built the one in thedude's build using the 4/25 "non-gpu" kernel with working vibrate. The one I have in this ion build is DZO's latest kernel.
So I think your problem is that something in the latest zImage/kernel breaks your sd card... but if it works well with my custom kernel from thedude's build, you can go with that until we get a newer kernel from DZO
seems to take a while booting up or my phone is just stuck. it wont go pass were it says "android" before the splash screen. any ideas
how long have you waited?
On my phone the first boot up it takes about 5 minutes at "extracting data.img" then another about 5 minutes after it initializes the modem before the splash screen comes up.
Once it finally comes up, and a couple reboots later, the total boot time from hitting run in haret to being at the home screen is about 2 minutes.
ok thanks ill let it chill for awhile.
Thanks, the other image was killed my battery in 5 hours. Screen brightness apps are still broken though, did you see martin's note regarding folks building cupcakes (maybe we should call it baking? ha) need to includes some libraries or something, check the 1.1 thread, just posted today.
EDIT: Disregard, just needed to update the flashlight and fastbright. If an app doesnt work for you then try checking the market for available updates. Theres probably a new build available with cupcake support.
Thanks again, great work!
I checked and both of the libraries are already in this system... I'm still not sure about battery life, will have to do some more investigating, as mine seems to last forever sometimes and die quick others.
Also not sure what's up with screen brightness apps, I know that on my vogue it works fine in settings -> sound & display -> brightness
yeah from what we can tell google completely redid alot of things in this build. They added cache's for speed, as well as the brightness setting is just like in 1.1 (works) and battery life is alot better. I'm really glad you got this one working vilord.
I've been playing around for a while now and have had some browser crashes on even some lite sites. Force close comes up but is frozen, requiring a soft reset. Bummer, everything else seems to be pretty smooth. Max apps is set at 4.
you set your own max apps to 4, or it is already set at 4?
So I just use the data image I have from 1.1, download this, and I'm good?
vilord said:
The only differences in the files from thedude's folder and from this one is 1)default.txt: I use different defaults than mssmison does
2)zImage: I custom built the one in thedude's build using the 4/25 "non-gpu" kernel with working vibrate. The one I have in this ion build is DZO's latest kernel.
So I think your problem is that something in the latest zImage/kernel breaks your sd card... but if it works well with my custom kernel from thedude's build, you can go with that until we get a newer kernel from DZO
Click to expand...
Click to collapse
I guess I don't understand what the different parts are. If I change the system file it changes the Android that's running. If I just change over the zimage from DZO's build then it still boots up TheDood's 1.5
Edit:
I'll try TheDood's zimage with DZO's other files. Is that what you meant to get 1.1 running so I can login? It boots through and goes to a black screen with a blinking red light with the occasional green light blinking.
I keep getting an error "Failed to load file \Storage card\android\intrid.gz
What exactly should I have in my Android folder and in my sd root? I already set up my market account using 1.1
vilord said:
you set your own max apps to 4, or it is already set at 4?
Click to expand...
Click to collapse
I set it up for 4, but the modem comes on automatically now, which is nice. If we could bake in the calibration settings for the vogue that would be pretty cool, but I imagine if you did this it may differ depending on resolution settings, maybe?
hexto said:
I keep getting an error "Failed to load file \Storage card\android\intrid.gz
What exactly should I have in my Android folder and in my sd root? I already set up my market account using 1.1
Click to expand...
Click to collapse
there should be 5 files... data.gz, system.img, default.txt, initrd.gz, and zImage
put *all* of them in the root of your SD, you don't need an android folder at all.
you want to use DZO's system.img and data.gz at first, then once you set up your data and your google accounts, leave the data stuff alone (it will now be called data.img), and replace DZO's system.img with the one in the original post.
vilord said:
there should be 5 files... data.gz, system.img, default.txt, initrd.gz, and zImage
put *all* of them in the root of your SD, you don't need an android folder at all.
you want to use DZO's system.img and data.gz at first, then once you set up your data and your google accounts, leave the data stuff alone (it will now be called data.img), and replace DZO's system.img with the one in the original post.
Click to expand...
Click to collapse
How about Haret?
this script is based on the work to Danesham90 and others see link
http://forum.xda-developers.com/showthread.php?t=598026
===============================================================================
Tested on the Samsung Vibrant, Script may need modification for other phones
===============================================================================
===============================================================================
Directions:
===============================================================================
the easy way:
1. turn on USB debugging
2. plug phone in to computer
3. run the script and follow the screen pormpts
the script will download everything needed to make a
signed deodexed clockwork flashable update.zip while also
adding root and the modified 3e recovery in the proccess.
===============================================================================
the hard way:
http://forum.xda-developers.com/showpost.php?p=10986893&postcount=28
================================================== =============================
Code:
/* This program is free software. It comes without any warranty, to
* the extent permitted by applicable law. You can redistribute it
* and/or modify it under the terms of the Do What The **** You Want
* To Public License, Version 2, as published by Sam Hocevar. See
* http://sam.zoy.org/wtfpl/COPYING for more details. */
UPDATED 02/03/2010
bug fix to signupdate.jar
clockwork script tweeks
UPDATED 02/02/2011
added upload to ROM to SDCard
added reboot recovery
added test sign all apk's in ROM - see README for details
added pull "/data/app/" and install "/data/app"
UPDATED 02/01/2011
added adb on by default toggle
added data wipe toggle
updated smali/baksmali to 1.2.6
UPDATED 01/31/2011
updated adb
fix similar filename deletion when using delete.txt
added barebones_delete.txt deletes everything that
does not cause phone to crash
UPDATED 01/29/2011
add "symlink dumpstate SYSTEM:bin/dumpmesg" to update-script.
add "symlink debuggerd SYSTEM:bin/csview" to update-script.
completed secondary method to make ROM from extracted Odin files.
see this post for instructions
http://forum.xda-developers.com/showpost.php?p=10986893&postcount=28
UPDATED 01/28/2011
added auto delete apk's (bloat removal), edit bin/example_delete.txt and rename to delete.txt
added auto add apk's (pre-install or update apk's) add apk's to bin/apks directory
UPDATED 01/23/2011
fix path error when space in user name
UPDATED 01/22/2011
updated TempRoot.exe to not trigger anti-virus
updated Superuser.apk
This is fantastic! Thank you for always making things a little less troublesome.
Oooops, last minute change broke something, fixed and re-uploaded.
untermensch said:
Oooops, last minute change broke something, fixed and re-uploaded.
Click to expand...
Click to collapse
Thanks for the heads up. I was just testing this on KA5 for funsies. It looked like it went ok but there was a prob with temp root at the beginning and it looked like a few java errors at the end. I'll re-download and give it another go.
Edit: Ah, looks like it's working now. Temp root worked and it downloaded the modem and kernel.
Edit2: So it looked as though everything worked fine, but when I went to install it I got
E:Can't symlink /system/bin/cat
E:Failure at line15:
symlink toolbox SYSTEM:bin/cat
Installation aborted.
Whitehawkx said:
Thanks for the heads up. I was just testing this on KA5 for funsies. It looked like it went ok but there was a prob with temp root at the beginning and it looked like a few java errors at the end. I'll re-download and give it another go.
Edit: Ah, looks like it's working now. Temp root worked and it downloaded the modem and kernel.
Click to expand...
Click to collapse
I just tested on my laptop and got a java out of memory error
while signing the rom so I increased the heap size which seems
to have fixed it.
untermensch said:
I just tested on my laptop and got a java out of memory error
while signing the rom so I increased the heap size which seems
to have fixed it.
Click to expand...
Click to collapse
Yea I got the same thing as well. Thanks again, will give it another go.
Update: The process was more in-depth when deodexing. Signing went through np and when I flashed through clockwork it worked (goodbye splash screen!). There must be some issue with KA5 though. It got through to the Galaxy S screen and then started vibrating and then blackscreen. T_T
Thank god for this.. (Deodexer)
Thanks untermensch, your the best
Really really appreciate this. Thanks a bunch!
Most useful tool EVAR!
I T W O R K E D~!
My final attempt last night did not shoot out the "signed_ROM.zip" at the end. I ran it again this morning on KA5 and when it finished I had the signed_ROM.zip in the folder. Put that on my internal, flashed through clockwork and viola! Doedexed KA5 with root and modded 3e recovery. I can't thank you enough Untermensch for putting this together for everyone.
"Give a man fish feed him for a day. Provide him with tools to fish and feed him for a lifetime." (Yea I tweaked it but you get the idea!)
I noticed one thing. During the deodexing process I got [null] on one file in the core.odex. After it had all finished up I looked in the framework folder and core.odex was still there. So am I correct in assuming that it did not doedex properly? Other than that everything else looks golden.
Oh this is sick. i was looking for this all day the otherday when i was trying to deodex ka5! you rock and rule. i cant wait to explore the possiblities!
Whitehawkx said:
I noticed one thing. During the deodexing process I got [null] on one file in the core.odex. After it had all finished up I looked in the framework folder and core.odex was still there. So am I correct in assuming that it did not doedex properly? Other than that everything else looks golden.
Click to expand...
Click to collapse
I deleted the core.odex file and rebooted just to see what would happen and it soft bricked and is stuck at the Vibrant screen. So it seems the only issue lies in deodexing the core.jar at this point.
can i use this to port a rom? forgive me if that is a noob question. just wanted to know if i had the right idea...
Whitehawkx said:
I noticed one thing. During the deodexing process I got [null] on one file in the core.odex. After it had all finished up I looked in the framework folder and core.odex was still there. So am I correct in assuming that it did not doedex properly? Other than that everything else looks golden.
Click to expand...
Click to collapse
yep that was an baksmali error, likely you could run the script again and it
would baksmali OK.
this script is a real system stress test, any way I increased the java maxmem
setting for framework files to 1024m added error logging and the script will
now stop if there is an error. hopefully to prevent a broken ROM from being
released.
Whitehawkx said:
I deleted the core.odex file and rebooted just to see what would happen and it soft bricked and is stuck at the Vibrant screen. So it seems the only issue lies in deodexing the core.jar at this point.
Click to expand...
Click to collapse
can you reproduce this error? I have seen it once but cant reproduce it
untermensch said:
yep that was an baksmali error, likely you could run the script again and it
would baksmali OK.
this script is a real system stress test, any way I increased the java maxmem
setting for framework files to 1024m added error logging and the script will
now stop if there is an error. hopefully to prevent a broken ROM from being
released.
Click to expand...
Click to collapse
untermensch said:
can you reproduce this error? I have seen it once but cant reproduce it
Click to expand...
Click to collapse
Pretty sure the core.odex [null] error I got happened every time I ran the program. I ran it once after the 1:25am update and it happened. That is also the time it did not produce the signed_ROM.zip. I ran it again this morning after I saw the OP had been updated and it did produce the signed_ROM.zip but I still got the [null] error on core.odex. I'm going to Odin KA5 and do it again right now. I will let you know how it works out.
On a side note. I flashed the one I recieved this morning with everything being deodexed except the core.jar and it ran great until I deleted the odex file. Anywho, will test now. Also, not sure if this matters but I am running 32-bit Windows 7.
Update1: Initial news is good. Core.jar was deodexed properly with no errors. Will let you know how the entire process fairs once its completed.
Worked perfectly. I got no errors and everything deodexed properly. Flashed it on my phone and it's running just fine. You are awesome.
Thanks for retesting, glad it worked, there are thousands of files being generated
an lots of java processes being spawned so there are bound to be an occasional
error. I have added an automatic retry when there is an error to the next version
should be posted some time tomorrow.
I'm about 3/4 the way through testing this out - it seems to be working just fine with the exception that every command is appended with "ATTRIB" is not recognized as...
Hopefully it will work anyway.
One thing I noticed that might speed the script up in the beginning would be a root check, I have already rooted this rom but it still needed to run rageagainstthecage.
I've been looking for something like this forever now, thanks so much! Can't wait to play with it.
Sent from my SGH-T959 using Tapatalk
I tried both Paul's version and the latest clockworkmod recovery from ROM Manager, but both of these would put wrong backup dates in the backup image files and folder. What's wrong? The phone or the recovery program??
It's a bit inconvenient, since if i rename to the correct date/time, the MD5 checksum would be wrong, so I need to keep the wrong ones as well.
What I observed is that the month is always +1 and the time is always using UTC timezone.
dohanin said:
I tried both Paul's version and the latest clockworkmod recovery from ROM Manager, but both of these would put wrong backup dates in the backup image files and folder. What's wrong? The phone or the recovery program??
It's a bit inconvenient, since if i rename to the correct date/time, the MD5 checksum would be wrong, so I need to keep the wrong ones as well.
What I observed is that the month is always +1 and the time is always using UTC timezone.
Click to expand...
Click to collapse
i am definitely noobie, so i could be totally wrong. please anybody correct me if say something totally absurd.
md5 checksum is for individual image files, not entire directory. for example mine is
# cat nandroid.md5
ee5f9313d30caa0956a8a6b24f75ddfa boot.img
8786667ac7d45546156b2e19bc0168cf cache.img
4b3fda00aa2255e2314fbbd20fa22d5d data.img
d4de133f5d712f7164151f319cebb728 recovery.img
93c71d12eab5c13d2a66e08a1b346696 system.img
i don't think renaming the directory will affect any md5 checking. sure, it is a bit inconvenient, but not the end of the world, i guess. maybe you can copy whole directory, rename it, and do recovery see if that works.
i agree wrong date is probably bug, and should be fixed.
as for time, i'm guessing (and i'm totally guessing here) that system is using UTC and get timezone information from network, so that clock is always correct even though you travel other region, instead of using local clock and figure out UTC. another reason i can think of is to use android market. i don't know why market checks time and date, but lots of people reported not being able to use market when date is set wrong. since market (or any other google servers) is kind of global, it is just easy to use UTC and then apply local time zone.
you may be able to disable getting clock from network by go and uncheck "Settings > Date & Time > Automatic" and manually set your local clock might do the trick ?
I have the same problem, its really annoying to restore several backups before you find the latest.
You can easily rename backups through ROM manager
I currently have backups named MCR14 and CM-nightly. I have them both on SD and internal memory due to CM switching them around.
pastime1971 said:
md5 checksum is for individual image files, not entire directory. for example mine is
Click to expand...
Click to collapse
yes, that's what I thought. But when I restore the whole backup (not individual img) in the clockworkmod recovery, it was not allowed. Then I renamed the folder to the original date/time, it passed. So, maybe the recovery program actually did check the files's dates against the folder name then? if not, then probably my new name was a bit long.
Did you put a space in the new name? It doesn't like them.
oh yes, then that's the reason.
now i use rom manager's interface, and it defaults the folder name to the correct date & time, that's good enough (although the actual file date/time still wrong)
Sent from my LG-P990 using XDA App
I have this issue as well and its bloody effing annoying. Makes it more of a hassle restoring your backups.
Please fix ASAP.
Not only that, but it sometimes changes the system date when flashing a new ROM to a month in the past as well...
Anybody know who the dev is (so we can let them know as they obviously don't seem to know about it)?
Sent from my LG-P990
withoutwings said:
Not only that, but it sometimes changes the system date when flashing a new ROM to a month in the past as well...
Anybody know who the dev is (so we can let them know as they obviously don't seem to know about it)?
Sent from my LG-P990
Click to expand...
Click to collapse
Amonth in the past I could live with. But CWM 3.2.0.0 ALWAYS puts mine a month in the future, so If I get a text/call before changing the date then that stays at the top of the list for a whole month. VERY silly schoolboy error.
I always rename backup folders, have been for a year. No issues.
Hey folks,
This is a completely new build, with all the new changes baked in. We wanted to do a semi-official test release to collect bugs and hopefully do a formal official release with everything settled. The main pain point is the CSV files (see pre-install prep).
So a brief overview:
New acoustic routing code baked in. Should fix most if not all audio routing problems, and will provide more debugging if stuff does go wrong. Also allows for more granular tweaking, see the CSV files.
GPS fixes for GB - GPS not only works in GB now, but it doesn't kill sleep! I was able to use GPS, get a solid lock, and put the device to sleep no problem.
BT should work & well with the new acoustic code. Post results.
RHOD users now have a choice of kernels. .35+ all have the new acoustic - so .35, .39, 3.0 and 3.1 are all fair game now... This is bundled with .27!!
Keep in mind, autobuild .27 kernels will produce no audio in this build... Obviously the bundled kernel will work, and the absolute newest .27 autobuild kernel does work now - Feb.27 2012 or newer.
rootfs tweaks - first, it will detect which kernel you're on (.27 or .35+) and automatically apply the correct firmware. Second, is it will always copy/extract the modules... failures there were getting annoying, and this is surefire if brute-force...
Few Easter egg apk's...
Probably a lot I'm forgetting, this might change
Pre-Install Prep REQUIRED!!!
This step is crucial, and I forgot all about it! You must copy all of the *.CSV file from your WinMo ROM - these are in the \Windows\ directory. There's a very easy way to do this. It involves the Total Commander app for WinMo (Direct Link for the perpetually lazy...) (included in EnergyROM and others probably).
Now you're in Total Commander looking at your \Windows\ directory. Whew... lots of files. Fear not! Hit the "CTRL" button, then the green "Plus" button. This opens the Select/Unselect files dialog. Put in *.csv, press "select" and voila. All CSV files are selected. Now - File -> Copy/Move -> I want you to copy these (should be 10) files to the ROOT of your SD card. No folders!!! This is hardset right now, until we get it all implemented into the build properly. Thanks!
Install
Assuming you've done the pre-install prep; this is installed just like the other XDAndroid builds - grab your startup.txt (don't forget rel_path= if you don't have it at the root of the SD!), ts-calibration and boot!
Download
Caveat List
CDMA users might get a crash in phone.apk and no service on boot. If waiting doesn't resolve the issue, then reboot. Should come up fine...
BT might still be flaky
The CSV files from my TOPA100 are attached for the lazy. I'd like to gather CSV's from each RHOD, I'm curious if any ROM devs have changed them out either... This could get interesting. If you folks don't mind, post up your CSV's, point out differences with mine, etc... We're trying to figure out how to unify these, if possible! Thanks!
Please post back any issues, enjoy!
GBX0C Changelog
Camcorder: Now works (tested on rhodium).
Acoustic: Bug-fix : correct random loss of dual(rear)-mic.
MMS: Bug-fix: Slides with zero duration on Sprint.
Gps: Bug-fix: Init/de-init sequence fix (correct gps not starting up after being unchecked in Settings).
Gps: Bug-fix: End gps session with a correct rpc call (relevant to amss6125 devices).
Gps: Bug-fix: Don't send delayed position requests after session has ended (possibly relevant to Navigation issues).
Gps: New feature: Xtra (aGPS) -> verified to work on rhodium/cdma raph.
X1 specific: Screen rotation patch.
Added tytung's GPS injector app to AndroidApps\Other as well as updating/cleaning up some apps in AndroidApps.
Modified rootfs for newest apsta firmware & wifi firmware - wifi tethering now works flawlessly in the newest kernels! .27 is still bundled for the record...
not works for me (Topa100) stock on boot=(
doma999 said:
not works for me (Topa100) stock on boot=(
Click to expand...
Click to collapse
Any information you'd like to provide? I can't really help you, you've given me nothing to go on.
I assume you mean "stuck" on boot. So stuck on the haret loading bar? Stuck on the flying text? Stuck on the boot animation? C'mon.
sorry, of course, I install like you write above...in console it can't detect build type...install on root of sd all std startup for topaz, no changes...if it help I'll can take a photo of console
doma999 said:
sorry, of course, I install like you write above...in console it can't detect build type...install on root of sd all std startup for topaz, no changes...if it help I'll can take a photo of console
Click to expand...
Click to collapse
Can't detect build type... I had that yesterday, and forgot no_partitions in my startup. Perhaps same issue for you? Obviously this setup runs without a partitioned card, and if your card is partitioned you must tell the system that you want to ignore the partitions and just boot looped.
Yes, I have partitioned sd...can you post me right startup, please?
(or I have to add 'no_partitions' to my startup.txt?)
doma999 said:
Yes, I have partitioned sd...can you post me right startup, please?
(or I have to add 'no_partitions' to my startup.txt?)
Click to expand...
Click to collapse
Sigh.
Yes, you have to add "no_partitions" to your startup.txt, as below.
Code:
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2293
set KERNEL zImage
set initrd initrd.gz
set initrd_offset 0x00a00000
set cmdline "lcd.density=240 msmvkeyb_toggle=off sensor=topaz pm.sleep_mode=1 no_partitions"
boot
Hi,
First of all thanks for your hard work and i'm so impressed by the way that XDAndroid changed my phone. But in this new version i remarqued that i have some missed applications in Android Market like "Tunis Radar" who is working in FRX07. There is a solution for this problem please ?
Thanks for respanding and sorry for my bad english
Poucet_OO7 said:
Hi,
First of all thanks for your hard work and i'm so impressed by the way that XDAndroid changed my phone. But in this new version i remarqued that i have some missed applications in Android Market like "Tunis Radar" who is working in FRX07. There is a solution for this problem please ?
Thanks for respanding and sorry for my bad english
Click to expand...
Click to collapse
Uhm.
From what I gather, there's apps that work in FRX07 that don't work here. Tunis Radar? Is that a GPS app..? Any other apps that don't work?
Logs please.
...Or are you saying they don't show up in the Market?
Hello,
Yes it's a GPS application and i can't see it in android market (it display that they are 15 results but i can see only Sygic (GPS App)).
What about to make this build in CWM?
Poucet_OO7 said:
Hello,
Yes it's a GPS application and i can't see it in android market (it display that they are 15 results but i can see only Sygic (GPS App)).
Click to expand...
Click to collapse
Perhaps it doesn't work for your device? I don't know, try to get an apk.
doma999 said:
What about to make this build in CWM?
Click to expand...
Click to collapse
Why? It runs off the SD card, full-blown recovery is ridiculous overkill.
wifi not working
wifi not working,topa100 device
edit1: ok fixed if i open it before booting haret
scarface5323 said:
wifi not working,topa100 device
edit1: ok fixed if i open it before booting haret
Click to expand...
Click to collapse
This bug has existed forever. Probably since wifi was enabled for you guys. C'mon.
hi, first of all thanks and happy new year
i was testing it and i can not run "my backup pro" in order to restore all my apps. i have tried versions 2.66 and 3.01 of this app.
anybody with success in this stuff? thanks a lot
maybe with titanium backup?
i know...my backup is from froyo frx07 version but i think it is possible if the app can run and not force closes itself at the begining
what about battery? any longer results in batt life? maybe not...
lmemperador said:
hi, first of all thanks and happy new year
i was testing it and i can not run "my backup pro" in order to restore all my apps. i have tried versions 2.66 and 3.01 of this app.
anybody with success in this stuff? thanks a lot
maybe with titanium backup?
i know...my backup is from froyo frx07 version but i think it is possible if the app can run and not force closes itself at the begining
what about battery? any longer results in batt life? maybe not...
Click to expand...
Click to collapse
Battery hasn't really changed.
Titanium Backup works great, I use it almost every day.
arrrghhh said:
Battery hasn't really changed.
Titanium Backup works great, I use it almost every day.
Click to expand...
Click to collapse
thanks a lot, i will try it
sorry if i post in wrong section, but i found no topic about GBX0B for HTC Raphael.
i use this GBX0B for my HTC Raphael 100, and the micro doesn't work.
how can i use it?
p/s: sorry for my bad english.
williamsnyder said:
sorry if i post in wrong section, but i found no topic about GBX0B for HTC Raphael.
i use this GBX0B for my HTC Raphael 100, and the micro doesn't work.
how can i use it?
p/s: sorry for my bad english.
Click to expand...
Click to collapse
What the hell is the micro?
I assume you mean the extUSB dongle?
Looking around in various threads I found numerous gps fixes. In some (most) the files are not original T959 files. While they may work, since they are not T959 KB5 files the possibility of 911 working diminishes. I set out to find any gps fix out there and build a flash-able package that would reset everything back to the proper (or as close to) files for our phones (T959).
Also I have found some ROMs utilized the SUPL port of 7276. This port was found to create gps log-spam and the "fix" was to reset the port to 7275. This IMO also resulted in quicker locks.
See HERE and HERE for more info.
For the 911 info go HERE (or just click it in FaultException's signature)
What this tells me is you want matched GPS libraries with the proper T959 RIL.
So I have searched a few threads and found 1 GPS fix so far and built mine to reset or undo any possible mismatched files flashed. If you find any GPS fix that some might use for CM10.1 please post it an I shall try to adapt mine to reset it to the proper files.
I have made:
North American version (NA)
Europe Version (EU)
Global Version (GL)
USA Version (US)
Asia Version (AS)
YMMV between USA and North America if you live in the states.
2nd post I will also post my custom version with some extra advice and good signal locks. What I need is for people to nanadroid first and test it. Also to post / link and GPS fixes they may have come across so I can check them. Point to note is I am attempting to fix non T959 GPS fixes as much as make a good GPS fix for our phones. Posting links to other "fixes" will help. Thanks
With any JB / ICS ROM you have taken the responsibility of possible breaking 911. No difference here. Flash at own risk.
NANDROID FIRST!!!
Big thanks to FaultException for the time, info, and files required for our phones.
Original version may mute calls > Revert to nanadroid if the case. V2 shouldn't effect calls. Please test.
Checking original Froyo gps files here is the the MD5's Ive found so far:
JFD (558kb)
0F3376A81E85AE6044D2BF68D63E2A55
JI6 (554kb)
4761E7B01E0A71A048458F50DE64BC62
KB1 (554kb)
870A5D6F3542FD7421B215FCB37D884C
KB5 (554kb)
870A5D6F3542FD7421B215FCB37D884C
(KB5 is what is in CM10.1 also)
Ok here is the file for my custom GPS setup. I have not had and deep-sleep issues (DS). Some of the following may work, or not. Its just some tips and stuff I do.
Zip file attached. NTP is set to north america so you can edit as needed.
This will also install Angrygps app for you. When you boot up open the app and set the following:
Settings > General Settings > Operation Mode = "MSBASED"
Settings > SUPL Settings > Server = supl.sonyericsson.com and PORT = 7275
Also I suggest you install an app called LeoAGPS injector. Found HERE
Install it like any normal app (no push), open the app and select "Pop-up message". After that go to your home screen and app the LeoAGPS widget. Click the widget to inject AGPS data. Wait a few seconds then reboot.
Try out the GPS and see how it goes.
Version 1 broke sound on the RemICS ROMs so I pulled the RIL files out. Now just custom gps files / fixes
Change log:
Added a USA version. May or may not work better than the North America version.
1/10/2013 - Since it appears the version 1 broke phone sound on the RemICS builds I removed the RIL files. Now v2 will only fix / replace gps files and not RIL files.
1/18/2014 - Added some MD5's of gpsd/agpsd files Ive extracted from Samsung dumps.
GPS fixes reset:
http://forum.xda-developers.com/showpost.php?p=33575684&postcount=504
If you want to try and adapt it to your specific country:
Open in a text editor: /system/etc/gps.conf
Change the NTP server line (top line) to your country. Country list found HERE
Edit / reboot / check
I do suggest the LeoAGPS app in post #2. It has seemed to work well for me.
Moped_Ryder said:
Ok here is the file for my custom GPS setup. I have not had and deep-sleep issues (DS). Some of the following may work, or not. Its just some tips and stuff I do.
Click to expand...
Click to collapse
Thanks for this awesome post! I know I'm suppose to test these files before asking but you might already have the answer: with these fixes, in your experience, do you still need to get a lock before DS in order to prevent issues after DS? Or after you reboot and getting into DS before locking first, you are able to get GPS to lock after DS?
Thanks for all your help!
davidgs said:
Thanks for this awesome post! I know I'm suppose to test these files before asking but you might already have the answer: with these fixes, in your experience, do you still need to get a lock before DS in order to prevent issues after DS? Or after you reboot and getting into DS before locking first, you are able to get GPS to lock after DS?
Thanks for all your help!
Click to expand...
Click to collapse
It was not addressed to me, my 5 cents anyway. I think it's more a kernel issue, at least it was so on ICS until the great SubZero came into play. You should try his GPS-wrapper, I think it could help (preventing the GPSD getting incidentally corrupted) - find the flashable zip in the "3 files fix" post of Jrafael (see post No 3 above).
I am also very interested in getting our Vibrant's GPS as much functional as it can be. My own "fix" (check for Igps.zip) was giving me best results for accuracy (down to 3 m!) on some ROMs (JB 4.1 and 4.1.2, but not 4.2.1). I found out that there are many useless files (such as gps.xml or secgps.conf), and that GPS will still lock and pretty quickly even without gps.conf tweaks (and even without this file). However I don't have coding skills to organize my empirical findings.
@ MR - where did you get your RIL files from, with the Europe fix file I have no sound on phone call (I use instead the MP's RIL files, working fine for me).
Got the RIL from KB5 / CM10.1 - same boat here about sound. Gonna pull the downloads and check on it. If anything Ill re-up without the RIL and just GPS files and try again. Im getting what looks to by Bluetooth errors when trying to connect. Even when BT is turned off with the RemICS ROMs.
Whenever able CM10.1 use the Froyo KB5 RIL / Drivers and such. Some times it just doesn't work. The RIL and AGPS files from Froyo KB5 match the CM10.1 ROMS.
Testing my original fixes - the following so far are the outcomes:
RemICS-JB: Breaks sound. Version 1 RIL and GPS doesnt match CM10.1 / KB5.
Slimbean: No issues - Sound works fine. Confirmed the base RIL / AGPS files in ROM match CM10.1
HellyBean: No issues - Sound works fine. Confirmed the base RIL / AGPS files in ROM match CM10.1
CM10.1: No issues - Sound works fine. Confirmed the base RIL / AGPS files in ROM match CM10.1
FIRST
I will apologize to those who flash the original version on RemICS ROMs. It broke your call sound. Return to your nandroid and all should be well. For those on Slim / Helly / CM10.1 you are fine.
The RemICS ROM is very smooth but the RIL / GPS files don't match the Samsung T959 KB5 (also in CM10.1) files. Replacing 3 of the RIL files with the proper KB5 ones broke the sound. Ill keep at it.
For now - Version2 no longer replaces and RIL files. All the above GPS fixes will replace gps files / remove un-needed gps files.
First I want to thanks Mr. Moped for jb GPS fix great job.I am using remics jb 4.2 and moped GPS files NA-Version 2 it works good, I lost signal than it reconnect so that issue is fixed in Version 2 and sound is working also thanks .
Sent from my SGH-T959 using xda app-developers app
Gps works good sound also ,only sound is bad when I put on speaker when i am on phone call to much noise . we used to control mic from in call volume control feature in advance setting and now we are missing that feature in 4.2.
Sent from my SGH-T959 using xda app-developers app
Moped_Ryder, I just flashed 4.2.1 and flashed your USA version GPS fix after flashing GAPPs. I'm coming from 4.1.2, and only got locks down to 30m intermittently. The norm was 800 m accuracy (vik5 responded to some of my posts). More importantly, thank you for doing this post (clicked the Thanks) and appreciate you explaining the reasoning behind your updates as well.
*Update* First lock in GPS Checker occurred after 31s with 8 "fixed satellites". Marked improvement over GPS performance on Team RemICS 4.1.2 (highest I ever got was 3 satellites, lock took 242 s). Thanks Moped!!
Cap'nO said:
Moped_Ryder, I just flashed 4.2.1 and flashed your USA version GPS fix after flashing GAPPs. I'm coming from 4.1.2, and only got locks down to 30m intermittently. The norm was 800 m accuracy (vik5 responded to some of my posts). More importantly, thank you for doing this post (clicked the Thanks) and appreciate you explaining the reasoning behind your updates as well.
*Update* First lock in GPS Checker occurred after 31s with 8 "fixed satellites". Marked improvement over GPS performance on Team RemICS 4.1.2 (highest I ever got was 3 satellites, lock took 242 s). Thanks Moped!!
Click to expand...
Click to collapse
Do me a favor if you have time. Do a Nandroid and try my Custom fix in post #2 (to include AngryGPS settings). Also combine that with the LeoGPS I linked as well.
See if that works any better for you. Revet back to your Nandroid after if you wish.
Moped_Ryder said:
Do me a favor if you have time. Do a Nandroid and try my Custom fix in post #2 (to include AngryGPS settings). Also combine that with the LeoGPS I linked as well.
See if that works any better for you. Revet back to your Nandroid after if you wish.
Click to expand...
Click to collapse
Will do
Sent from my SGH-T959 using xda app-developers app
Moped_Ryder said:
If you want to try and adapt it to your specific country:
Open in a text editor: /system/etc/gps.conf
Change the NTP server line (top line) to your country. Country list found HERE
Edit / reboot / check
I do suggest the LeoAGPS app in post #2. It has seemed to work well for me.
Click to expand...
Click to collapse
Hi, I tried to edit gps.conf file as mentioned. But whether I changed the supl_port to 7275 it remains 7276 it asks me to save the changes but doesnt save
Probably /system is not set for read/write.
Ill make ya a Flashable zip tonight if you give me the country you want from that list.
Moped_Ryder said:
Probably /system is not set for read/write.
Ill make ya a Flashable zip tonight if you give me the country you want from that list.
Click to expand...
Click to collapse
I don't suppose I could request a flashable zip for New Zealand (Oceania) gps settings?
I flashed from 2.3 to Cyanogen 10 then 10.1 and now have no gps when I did initially have it working in 2.3
Moped_Ryder said:
Probably /system is not set for read/write.
Ill make ya a Flashable zip tonight if you give me the country you want from that list.
Click to expand...
Click to collapse
Hi,
Thanx for the reply Moped I am using root explorer and set the r/o to r/w and opened the conf file in text editor.. I can edit the file but changes wont stick
I am living in sri lanka which comes under Asia — asia.pool.ntp.org Sri Lanka — lk.pool.ntp.org
Thank you again.
EDIT: I edited the gps.conf file using the es explorer (with root access enabled). there is a new file created inside root explorer gps.conf.bak and theres nothing inside gps.conf file (inside root explorer).
BUT gps.conf file (inside es explorer) has the changes I made. I rebooted but still the same
EDIT (update): Set the permission READ for all USER, GROUP, OTHERS and voila gps.conf file has the changes
Hope these info will help anyone having this issue
I can take care of it tonight.
If anyone wants to do it themselves its not hard.
1. Download and install a program called 7zip
2.. Download any of my GPS fixes
3. Right click on it (GPS fix). Browse thru 7zip to the /system/etc folder and drag the gps.conf file out to desktop (or somewhere).
4. Dont close the 7zip yet
5. Open the gps.conf file you just extracted and edit the NTP line to suit your needs. Save it.
6. With the archive still open in 7zip drag the edited gps.conf file into the /system/etc folder in 7zip. Overright old file.
7. Close zip. Its ready to transfer to your phone and flash it.
...You may be abnle to edit the gps.conf file right from 7zip (cant test Im at work right now)
I can always help someone with it. Just though peopl would like to try it out themselves too.
Moped_Ryder said:
I can take care of it tonight.
If anyone wants to do it themselves its not hard.
1. Download and install a program called 7zip
2.. Download any of my GPS fixes
3. Right click on it (GPS fix). Browse thru 7zip to the /system/etc folder and drag the gps.conf file out to desktop (or somewhere).
4. Dont close the 7zip yet
5. Open the gps.conf file you just extracted and edit the NTP line to suit your needs. Save it.
6. With the archive still open in 7zip drag the edited gps.conf file into the /system/etc folder in 7zip. Overright old file.
7. Close zip. Its ready to transfer to your phone and flash it.
...You may be abnle to edit the gps.conf file right from 7zip (cant test Im at work right now)
I can always help someone with it. Just though peopl would like to try it out themselves too.
Click to expand...
Click to collapse
One can make a custom flashable zip right on his/her phone.
1. Use a file explorer which has archiving function (I have Solid Explorer) and unzip any flashable zip you want to change.
2. Make your changes.
3. Compress to zip again. IMPORTANT: you must ONLY include the content itself and NOT the uppest folder (if your zip has two folders, META-INF and System, first select the two and compress these two in a single archive). Otherwise it won't be cwm flashable.
To change the gps.conf file on the go use Faster GPS (NOT Faster fix) free in Playstore.
Moped...i tried the other zip; No good lock on this one. Flashed Custom zip file and changed settings in Angry GPS as instructed. No lock..no satellite signals. Reverting back to old setup..using your US version, which worked perfect.
Sent from my SGH-T959 using xda app-developers app