Related
SuperJustKitchen v0.9 Released.
Go to my site: http://justkitchen.info to get the updates and the info. It takes to long to update every device's forum that is supported, and I plan to support all devices, eventually.
Word of warning:
Not all EXT's have been tested or modified for the every device. Please test test and test and then let me know which packages don't work and what YOU've done to fix them. (I don't have time to fix ALL of them by myself.) Some packages will only be compatible with some devices.
(I'm no longer updating each thread separately for each device but just updating my site and posting the release info here. I will only update each thread to say that a new version is out.)
**Warning**
Before using this kitchen, you MUST read the whole thread. Any questions that have been answered will be ignored. This is your only warning.
**Disclaimer**
I am not responsible for any damage that may be done to your phone with a ROM created in this kitchen.
I am not responsible for any damage done to your computer.
I am not responsible for anything... at all.
Introducing SuperJustKitchen!
SuperJustKitchen is based on [http://forum.xda-developers.com/member.php?u=843218"]airxtreme[/URL]'s osKitchen Zero. All credit on for the kitchen backend goes to him.
Features
A completely stripped ROM. (Work in progress for some devices.)
LZX and XPR compression (Also option for No compression.)
Auto clean files that are language specific or DPI specific that your ROM does not need
Auto port missing language MUI files
Automatic rec'loc'ing for devices without native 6.5 nk's
6.1 and 6.5 support
Auto XIP and SYS porting
Auto NBH packing
Tool to convert OEM packages to EXT packages
Auto file conflict fix (don't have to removing older file that conflict (not that there are any. )
Save custom ROM settings (for cooks for multiple ROMs)
Cook multiple languages at the same time with the same ROM settings (Have to add language support yourself. I removed the required MUI's a while back because they made updating the kitchen and adding devices a nightmare.)
MUCH better organization of EXT packages
Active development instead of a program that is no longer being developed
Cleaner and easier to use interface
A built-in and customizable Tutorial section
And more!
Builds included
21056 - WM6.1
23658 - WM6.5 with new redesigned GUI
At the moment, this is an ENGLISH (WWE) only kitchen. This might change...
NOTE: In order for me to keep track of whether my time was well spent or wasted, if you use this kitchen to make a ROM, please either include SJK in the name or just mention that it was SJK cooked in your ROM's thread.
NOTE: This kitchen assumes that you know how to flash through SD, recover from a bad flash and are able to backtrack your steps to figure out how you broke your own ROM. If you do not understand these, please learn them first. Do not PM me asking me. I have written numerous walkthroughs on all these except on how to backtrack your steps. For that, just remember what you're doing as you do it and keep backups.
If you find any issues, PLEASE report them to the bug tracker in my website. It will help me make this kitchen better!
ENJOY!!!
thanks i will try....
oh!!!!! it takes a long time as Compaed to earvius kitchen.....also i am not able to flash .nbh file it stops at 1% in ruu and then device restarts.......
Not working
indresh88 said:
oh!!!!! it takes a long time as Compaed to earvius kitchen.....also i am not able to flash .nbh file it stops at 1% in ruu and then device restarts.......
Click to expand...
Click to collapse
same here...the final ROM when flashed says image corrupt
Same here all the rom file made by sjkv0.8 gives unflashable rom.
Something might be broken then. I changed the executable last minute. What size is the NBH you are all producing?
ivan the output nbh size is ok it seems for a lite rom it produces about 56mb and remember the one nbh u provided for testing is also having prob it says its corrupt.
help me...SJK won't cook
i cannot make it work...
i get an error while cooking about some files (ringtones) not able to be copied and then hangs.
i tried it on Windows7 and it says that the some payload.nb file is not found in temp folder.
gui-wise/appearance wise...this is the best kitchen ever!!
can someone please tell me where i went wrong? i download four files from the SJK website: ext package, sys package, opal package and the SJK package and extracted to the same folder.
Update:
v0.8.1 - Fixed unflashable ROM bug
Thanks ivan now finally i can use sjk v0.8 (now 0.8.1) after using sjk 7 for so long time.
v0.8.2
Fixed LZX
still gives an error...
ivanmmj said:
v0.8.2
Fixed LZX
Click to expand...
Click to collapse
last night, i cooked 3-4 times using different settings, compression, rom version but it still gives a flash write error for me
cooking works fine except for some errors regarding some *.wma ringtone files inside SYS/PhoneRedist folder not being able to be copied (i overcame them by deleting)
flashing goes upto 100% (i used RUU via the usb cable) but the device reboots and goes to tri-color screen and says Rom Code Error.
btw...do i have to re-download every thing (SYS, EXT, *device_specific*) and the SJK_0.*.* or just the single SJK_0.*.* file?????
+1 Exactly same result since v8 and above
freelancer81 said:
last night, i cooked 3-4 times using different settings, compression, rom version but it still gives a flash write error for me
cooking works fine except for some errors regarding some *.wma ringtone files inside SYS/PhoneRedist folder not being able to be copied (i overcame them by deleting)
flashing goes upto 100% (i used RUU via the usb cable) but the device reboots and goes to tri-color screen and says Rom Code Error.
btw...do i have to re-download every thing (SYS, EXT, *device_specific*) and the SJK_0.*.* or just the single SJK_0.*.* file?????
Click to expand...
Click to collapse
No, if you already had the *_0.8 for all the files, just download the SJK_0.8.3. If you didn't have anything, download EVERY file that's not device specific and your device's file.
You're getting a flash write error?
Still error
what might be the problem????
flashing goes upto 100%, device reboots and goes to tri-color screen
and displays a "ROM CODE ERROR".
i tried all compression methods including UPX on EXT packages but same problem.
freelancer81 said:
what might be the problem????
flashing goes upto 100%, device reboots and goes to tri-color screen
and displays a "ROM CODE ERROR".
i tried all compression methods including UPX on EXT packages but same problem.
Click to expand...
Click to collapse
I think I know what happened. Please hold while I work with airxtreme to fix it.
gooooddddyyyy....i am looking forward to it!!!
Try this:
http://justkitchen.info/main/rokdownloads/SJK_0.8.5.7z
Please let me know ASAP if it works.
thank you for your promptness...i will surely try and let you know.
freelancer81 said:
thank you for your promptness...i will surely try and let you know.
Click to expand...
Click to collapse
Did you ever get a chance to try it out?
So I've tried to install android build. I had stock rom 3.14.479.2 and I've tried to install HD2Froyo_V3. I've followed the instruction and after running haret few lines of text showed and than nothing, htc display appeared and stayed that way until I've removed the battery. Then I've read that I have to flash a coked Rom in order to install build for android so I downgraded it to 1.48 so I can install HSPL (not sure that it was necessary). I've flashed Energy.Leo.21916.Sense2.5.Cookie.Nov.02 with Radio_2_12_50_02_2 and copied Android folder again, same result. After flashing between stock Rom and Energy.Leo.21916.Sense2.5.Cookie.Nov.02 million of times I'm out of options. The same problem I had with FroyoStone_Sense_V3.2 too. It seemed so easy when I saw it on youtube and I can not believe that I had so bad luck. What I've done wrong? What should I do?
Anyone help?
One word: wait!
the kernel usually creates a 1GB storage for android. This will need some minutes (can take up to 10 minutes on class 2)
Some words for ROMs. Nearly all ROMs will work (the 2.14 ROMs don't) as long as you have a new radio. use 2.10 or higher. some have robo voice problems when calling. if you experience robo try another Radio.
(you should post questions like that in android development discussion. this subforum is for development only)
The folder-name of your rom, what is it and did you change it? You have to change a value in startup.txt aswell if it is different from 'Android'.
Ultimaex is right. Creating a 1gb storage for android will take some time, be patient. I have a 2gb storage which took about 20 minutes from start to finish.
fyi, my setup is tmous stock rom 3.14 and tytung's NexusHD2-FRG83 Froyo 2.2.1 build.
Mr_Q said:
The folder-name of your rom, what is it and did you change it? You have to change a value in startup.txt aswell if it is different from 'Android'.
Click to expand...
Click to collapse
It is Android. And I've been waiting more than 15 minutes and nothing changes, only black screen with HTC on it...
mila1909 said:
It is Android. And I've been waiting more than 15 minutes and nothing changes, only black screen with HTC on it...
Click to expand...
Click to collapse
Ive had this happen to me when I was switching builds. I deleted everything on my sd card that was related to android. Usually, the folders that android makes on your sd card are all lowercase letters. The folders are start with a capital letter are Windows Mobile specific folders. So delete all those folders, dont forget to show hidden files just to make sure you get all the folders. Afterwards, with whatever build you plan on using, its probably best to re-download that build just to make sure no files were edited and copy them to your sd card.
Basically just start with a clean slate and you should be good to go.
i had the same problem just reformat ure memory card on ure htc hd2
I formated the sd every time I tried. It's not that
Same
I got the same problem I have tried everything waited more dan 20 minutes. Formatted 25 times. Iam searching all forums to find something
Ok, I have mentioned this a couple of times and it seems to fix this issue, format the SD card within windows (a full format not a quick one) and ensure that you format it to clusters that are 32kb.
Also what radio are you both using?
I use 2.15.50.14 now, bit tried with every radio over 2.8
fig_jam_uk said:
Ok, I have mentioned this a couple of times and it seems to fix this issue, format the SD card within windows (a full format not a quick one) and ensure that you format it to clusters that are 32kb.
Also what radio are you both using?
Click to expand...
Click to collapse
Iam now trieying what you said. I let u know about it.
I use radio 12.50
nope, again not working...I am desperate
mila1909 said:
nope, again not working...I am desperate
Click to expand...
Click to collapse
Same format didnt help, iam now gonna try other kernels.
well finally works!!! I instaled hspl3 and energy rom and tried with mattcleofroyo1.8 and it happend ...I don't know if it works with another build but this one is good, no problems till now
mila1909 said:
well finally works!!! I instaled hspl3 and energy rom and tried with mattcleofroyo1.8 and it happend ...I don't know if it works with another build but this one is good, no problems till now
Click to expand...
Click to collapse
I got energy rom 2 and hspl3 gonna try that android build i let you know if it works. try to use the zImage from mattcleofroyo with another build.
That build didnt work for me after jumping kernel my leds flashed an i got whit streak.
coolgut said:
That build didnt work for me after jumping kernel my leds flashed an i got whit streak.
Click to expand...
Click to collapse
That's normal at the first boot, he wrote it in his thread.. Was the same for my phone, just let it doin' his thing it will finish after about 10min.
And what I wanted to say, I think mattc 1.8 is one of the best Sense builds out there.. Works so damm' smooth. Old but gold
Yes I agree. I've tried several after this one and got back on mattc...There are few problems but I hope that will be fixed in other versions....
coolgut said:
That build didnt work for me after jumping kernel my leds flashed an i got whit streak.
Click to expand...
Click to collapse
You mean you got all kinds of distorted graphics all over the screen. Black and white stripes kind of thing? If so, that's because you probably replaced zImage but didn't replace initrd.gz. Regardless, if you leave it on the screwed up black/white screen, it should load within 10-15 min.
NOTE: This is a thread for the build devs.
Users who want to try this solution themselves should head over to TheAgent1982's thread: RTL Support Project, or go to the Hebrew guide at htcaddicts.com.
Update: Hey devs. Just so you'd know, we're even willing to do the framework.jar patching for you!
All we ask from you is to deodex your builds, and include the patched framework.jar (which appears to be almost the same for all builds, barring sense/non-sense differences).
PM if you're willing to let us help
Hey devs
First of all, thanks to all the devs who are doing a great work with everything!
There's one thing though that's a pox on all Android builds (even native android devices), and that is full-on right-to-left support. What do I mean?
Sure, there are Hebrew (and I assume Arabic) fonts in Android, and MOST applications work just fine, with the notable exceptions of Gmail, Google maps, and most native Google-apps, who all display Hebrew backwards.
A far more stressing issue, however, is that ALL android applications without exception display numbers backwards in right-to-left texts (so 10 becomes 01, 12 becomes 21, etc. It can get really confusing really fast).
Any way, there exists a solution for both these problems that can USUALLY be fixed with a medium amount of experience on native Android devices, but requires a bit of a hassle for HD2 owners.
Hopefully, you devs can incorporate this fix to future releases, once the fixed files are obtained it shouldn't be too hard to spread in the future.
Here's the process:
BTW, This only works on completely deodexed builds!
First, you have to download this zip file. It basically contains the fixed files and some other stuff you devs probably won't need.
The fix then involves extracting 'framework.jar' from the phone, and extracting the 'classes' file thusly:
Code:
java -jar baksmali-1.2.2.jar -o classes classes.dex
Then, in the subsequently created "classes" folder, you need to replace the files in "/classes/android/graphics/" and "classes/android/text" with the relevant files in the aforementioned zip file (from the corresponding folders, of course, under "files/froyo/")
After that is done, you need to re-create 'classes.dex' using:
Code:
java -Xmx512M -jar smali-1.2.2.jar classes -o classes_new.dex
Then, replace the old 'classes.dex' in 'framework.jar' with the new one (after renaming it back to 'classes.dex', of course), and push the new and fixed 'framework.jar' back to the phone.
Reboot, and voila: full-on Left-to-Right support!
I'm sure you devs have far better ways of including these fixed files without having to edit the entire thing every time, but what would I know?
We would be extremely appreciative to all you builds devs if you could incorporate those fixed 'classes' files in future builds, it'll save us a ton of work.
Also, if any of you guys also need volunteers for beta-testing this solution (as I'm sure you don't have Hebrew content to test it with), feel free to PM me.
Thank you for listening, and keep up the great work!
((PS, thanks to member silverbluem who helped simplify the process))
+1
i use the htc sense to read sms so
the msg wont appear word4 word3 word2 word1
+1 for that. although i am using bifbif ver 1.2 with CM6 and its OK here.
i've test it on Mdj Evolution 2.3 and it work perfect:
i never copied the files to /graphic only to /text folder
to put the Framework.jar in the device because we dont have recovery mode
use this commands:
to pull the file:
adb pull system/framework/framework.jar
install the attached files
adb push (your file location/framework.jar) system/framework/framework.jar
after putting the file restart the device
restart might take 5-10 min first run after applying the file
thanks
silverbluem said:
i've test it on Mdj Evolution 2.3 and it work perfect:
i never copied the files to /graphic only to /text folder
to put the Framework.jar in the device because we dont have recovery mode
use this commands:
to pull the file:
adb pull system/framework/framework.jar
install the attached files
adb push (your file location/framework.jar) system/framework/framework.jar
after putting the file restart the device
restart might take 5-10 min first run after applying the file
thanks
Click to expand...
Click to collapse
This sure does absolve us of needing to use Linux and needing all that messy system.ext2 stuff. I'll give it a try.
Still, it'd be nice to have these updated files already incorporated into future builds.
Ambious said:
This sure does absolve us of needing to use Linux and needing all that messy system.ext2 stuff. I'll give it a try.
Still, it'd be nice to have these updated files already incorporated into future builds.
Click to expand...
Click to collapse
still need to figure out how to replace the graphic file
cause the view is not perfect without it...
Ambious said:
Edit: I tried this method, and while it DID boot, the solution didn't work - numbers still backwards, Google applications still reverse.
Click to expand...
Click to collapse
what rom are you using?
EDIT: the only thing that need to change to you is the phone book is now need to be RTL and the number backwards
Gmail need the Graphic file
silverbluem said:
what rom are you using?
EDIT: the only thing that need to change to you is the phone book is now need to be RTL and the number backwards
Gmail need the Graphic file
Click to expand...
Click to collapse
My WM rom is OzDROID2.0, my Android rom is MDJ FroyoHD 3.7
Well, the phone book was never a problem for me, only hybrid text/numbers like in text messages etc.
Anyway, turns out I didn't modify framework.jar correctly, so I tried again using the script, and this time the phone just won't boot (like when I used Linux, it just hangs at boot screen).
Edit: Tried all day, all combinations of 'texts' files and with or w/o the 'graphics' file, and it always either just didn't fix anything (when I did the fix manually), or didn't boot at all (when I tried the script). This got me to conclude that I must not be doing it right, or else it would fail to boot for me as well (at least, I'm not even considering me being able to totally fix it myself )
Not a week ago, i was referred to the Samsung Galaxy S's newest ROM which came from Orange..
The rom includes (to my understanding) all the latest fixes regarding left to right text and even a hebrew version of Swype
It is easily retrievable. Obviously, it isn't legal to extract their work and use it to manutfacture a widespread ROM... but you can use it for personal use if you want to check how to fix that annoying hebrew thing.
+1000
Thanks
nir36 said:
Not a week ago, i was referred to the Samsung Galaxy S's newest ROM which came from Orange..
The rom includes (to my understanding) all the latest fixes regarding left to right text and even a hebrew version of Swype
It is easily retrievable. Obviously, it isn't legal to extract their work and use it to manutfacture a widespread ROM... but you can use it for personal use if you want to check how to fix that annoying hebrew thing.
Click to expand...
Click to collapse
It COULD be used to reverse engineer some of the stuff, but I doubt it's similar enough to the HD2 builds to use it.
+1
Thanks
Hebrew RTL Support
For those who are asking, i have made a working framework.jar , time ago.
It is working for most FROYO Sence, CM6.+ does not need it...
BUT NOT Desire HD Sence ( Because is is odex files, not only *.jar).
If needed i will upload it, and put a tutorial how to make it work...
Good Day!
RTL HEbrew
Please do that !
Thanks
Framework.jar
Tomorrow i will post the file with short tut how to put it, i must say that Ambious bring a good tut directly from iAndroid
Any way, Ambious, if i will upload the file please stick it to 1st page.
For now, good night...
This fix is a must for all RTL language users.
As mentioned, CM6+ already includes the fix and is working pretty good!
Problem is, for some reason, CM6 builds are rare...
I tried a few Sense builds but eventually i came back to a CM6 based build
because of it's support for RTL languages.
Devs, please include this fix in you builds, to make them as much accessible
as possible.
Thanks.
TheAgent1982 said:
Tomorrow i will post the file with short tut how to put it, i must say that Ambious bring a good tut directly from iAndroid
Any way, Ambious, if i will upload the file please stick it to 1st page.
For now, good night...
Click to expand...
Click to collapse
I sure will!
Thank you
However, as a Sense user myself, I'm pretty anxious to see if a fix can be applied to any of the Sense builds (especially DesireHD, which is my current build).
Well Organized Post
I have made well organized post for it:
RTL Support Post.
I must say, it will NOT Work for Desire HD for now, because it is ODEX and jar combined, and as you have read at iAndroid, for now there is NO solution for it,
and i do not have the experience and time to learn and convert it, since i am a student.
But i will give it a try between the semesters...
Hey,
The HD2 Desire HD builds are fully deodexed.
Froyo HD 3.7 for example: http://forum.xda-developers.com/showthread.php?t=795914
Maybe you could use them for preparing a RTL fix for when the deodexed desire HD ROMS come and for us HD2 android users.
Cheers.
It may be my semi-n00bness, but all my attempts to create a fix for DesireHD 3.7 failed.
Also, trying the supplied fix in the thread above on MDJ Sense Clean (non HD based) failed, wouldn't boot.
Hopefully someone can get it to work, and better yet - that the devs will incorporate those fixes in their builds.
OK I tried to cook up a theme for the Virtuous Unity 1.27 and failed....
When I flashed it I tried too boot and ended up with i/o error....it stuck on boot animation. I tried logcat and got i.o error instead of output...tried to flash room without wiping and got logcat going and got i/o errors so had to wipe it clean.
I am guessing I screwed something up....
I used the virtous ROM 1.27 in the kitchen for the rom....
Edify scripting with MTD as default
Patch 9 autofix
Theme chooser preview (think this might of been the issue)
anyone want to chime in if the theme chooser was the problem or another error tick?
for flashing method (i think its called), select eMMC instead if MTD.
that should definitely work. When ever you use that site for this phone, make sure to select that.
the theme chooser preview option doesn't make a difference, just makes ever theme slightly larger because its another png file in there
I've made a few with UOT Kitchen for the Unity ROM, on 1.26.0 and 1.27.0, and it's worked every time without changing any settings...try uploading the files yourself if nothing works just to see. Weird...
Sent from my HTC Glacier using XDA App
make sure everything is green on summary page and also make sure your uploading all 3 necessary files for gb sense.
Sent from my HTC Glacier using XDA Premium App
Well everything was green.....
I used the built in 1.27 rom...and emmc huh?....I can try that....
If someone wants to look at what I goot and see if they see an obvious problem I could put it on drop box for someone to look at
I can almost guarantee its the emmc thing. i had that same issue. but nothing is for sure..
JDV28 said:
I can almost guarantee its the emmc thing. i had that same issue. but nothing is for sure..
Click to expand...
Click to collapse
I will give the emmc change a shot....i know it had the 3 files....so will try that
Hi guys, bit of a newbie here.
Ive seen on the site abut getting gps to work on this version and followed instructions but nothing seems to work.
It got me thinking... would an external Bluetooth GPS work instead? Just as a bit of a work around?
Many thanks for your help here
johnpodlesak said:
Hi guys, bit of a newbie here.
Ive seen on the site abut getting gps to work on this version and followed instructions but nothing seems to work.
It got me thinking... would an external Bluetooth GPS work instead? Just as a bit of a work around?
Many thanks for your help here
Click to expand...
Click to collapse
Do u mean that u have tried this too. http://forum.xda-developers.com/showthread.php?t=1100114
It work for me and a lot of other people who tried it.
nghockcheng said:
Do u mean that u have tried this too. http://forum.xda-developers.com/showthread.php?t=1100114
It work for me and a lot of other people who tried it.
Click to expand...
Click to collapse
The OP may also want to check the gps.conf file to determine if it is optimized for the region. Check this thread out as well: http://forum.xda-developers.com/showthread.php?t=953630
I am using Tytung's Gingerbread 2.3.5 Nexus HD2 v2.9 build with both the GPS v2.0 and an optimized gps.conf file on my phone. First locks are under 10 seconds and relocks are almost immediate using the built-in Google Navigation on the phone. Without the optimized gps.conf file, first lock was around 20 seconds. Tytung's ROM is set up for the North America. If you are not in North America, then you will need to change the gps.conf file to match your region.
The build-in gps must work, but a bluetooth gps will work to.
Sent from my mercury using XDA App
GPS problem
Hey guys I don't want to open a new thread, so I'll just post here...
I have the same GPS problems as most people here – GPS Status and GPS Essentials are showing no satellites, 0 visible and 0 used for fix.
I’ve left the phone to search for 10min in couple of occasions and nothing.
I think I’ve tried about everything here to fix it (and this is begging to bug me majorly)...
Updated the libraries with v2.0 RPC tytungs update (before that I’ve used the AngleDeath Europe.zip patch)…
Then edited the gps.conf file
first added the eurpe.pool.ntp.org,
then tried following lines
0.europe.pool.ntp.org;
1.europe.pool.ntp.org;
…etc.
Event tried the (my) country specific server address (pulled it of from the NTP POOL PROJECT website)
rs.pool.ntp.org
Installed the xtra.bin injector
Tried it on a perfect summer day and/or night, with 3g and WIFI on… but no results…
I’m running
CyanogenMod-7-NIGHTLY-Desire[TyphooN_V3.5.7-MAGLDR]
Tytungs r11_beta2 kernel (the lock screen lag fix)
CW 3.1.0.0
Radio Leo 2.15.50.14
Any ideas?
hi, this is what ive used but i must be doing something wrong and dont understand what im doing with the files etc
Im using MDJ_GingerBread_HD2_v.1.0_RC4_RAM_MODDED SC Card version
does that make any difference?
Is anyone with this problem using one of the latest roms with agps support? I can lock on in about 20 seconds from a restart. Also is everyone on the latest magldr?
never had any problems using MDJ Gingerbread... no editing or anything else - it works perfect right from the get-go...
t00tall said:
Hey guys I don't want to open a new thread, so I'll just post here...
I have the same GPS problems as most people here – GPS Status and GPS Essentials are showing no satellites, 0 visible and 0 used for fix.
I’ve left the phone to search for 10min in couple of occasions and nothing.
I think I’ve tried about everything here to fix it (and this is begging to bug me majorly)...
Updated the libraries with v2.0 RPC tytungs update (before that I’ve used the AngleDeath Europe.zip patch)…
Then edited the gps.conf file
first added the eurpe.pool.ntp.org,
then tried following lines
0.europe.pool.ntp.org;
1.europe.pool.ntp.org;
…etc.
Event tried the (my) country specific server address (pulled it of from the NTP POOL PROJECT website)
rs.pool.ntp.org
Installed the xtra.bin injector
Tried it on a perfect summer day and/or night, with 3g and WIFI on… but no results…
I’m running
CyanogenMod-7-NIGHTLY-Desire[TyphooN_V3.5.7-MAGLDR]
Tytungs r11_beta2 kernel (the lock screen lag fix)
CW 3.1.0.0
Radio Leo 2.15.50.14
Any ideas?
Click to expand...
Click to collapse
I think the problem is that on your build they recommend using Tytung's NMEA and not the RPC file that you tried. Try loading v2.0 NMEA by Tytung and give it a try. On some of these builds, only one of these files will work. I suspect your build is one that will need only the NMEA file to make the GPS work properly.
slbenz said:
I think the problem is that on your build they recommend using Tytung's NMEA and not the RPC file that you tried. Try loading v2.0 NMEA by Tytung and give it a try. On some of these builds, only one of these files will work. I suspect your build is one that will need only the NMEA file to make the GPS work properly.
Click to expand...
Click to collapse
Yeha, I’ve noticed a after my post here that in the “update” list of the TyphooN ROM is stated that the NMEA lib is implemented in it… anyhow, re-loaded the NMEA lib… edited the .conf file again… rebooted… injected the xtra.bin … left the phone outside for like 5min to try to find any satellites… 0 hits :/
Man, this is frustrating… I would hate to have to change or re-flash the rom, I’m quite satisfied with this one… maybe I’ll switch to iOS XD
t00tall said:
Yeha, I’ve noticed a after my post here that in the “update” list of the TyphooN ROM is stated that the NMEA lib is implemented in it… anyhow, re-loaded the NMEA lib… edited the .conf file again… rebooted… injected the xtra.bin … left the phone outside for like 5min to try to find any satellites… 0 hits :/
Man, this is frustrating… I would hate to have to change or re-flash the rom, I’m quite satisfied with this one… maybe I’ll switch to iOS XD
Click to expand...
Click to collapse
With all the changes that you did, you may have no choice but to reflash the ROM again. Then only change the gps.conf files to your region after the reflash if it is not correct for your area. Then hopefully your GPS will be working again. If after all that, and it still doesn't work, you may have to look in the GPS antenna to see if it is working.
slbenz said:
With all the changes that you did, you may have no choice but to reflash the ROM again. Then only change the gps.conf files to your region after the reflash if it is not correct for your area. Then hopefully your GPS will be working again. If after all that, and it still doesn't work, you may have to look in the GPS antenna to see if it is working.
Click to expand...
Click to collapse
I've flashed my phone (yet again) the newest build of the TyphooN ROM... edited the .conf file, AND... nothing :| maybe I wrote the conf file in a wrong way... should it look like this?
i54.tinypic. com/11qgv8h.png (c/p the link for a screenshot of the conf file - I still cant post outside links)
any help would be greatly appreciated!
t00tall said:
I've flashed my phone (yet again) the newest build of the TyphooN ROM... edited the .conf file, AND... nothing :| maybe I wrote the conf file in a wrong way... should it look like this?
i54.tinypic. com/11qgv8h.png (c/p the link for a screenshot of the conf file - I still cant post outside links)
any help would be greatly appreciated!
Click to expand...
Click to collapse
Unfortunately, I can't see the link. Maybe you should try the quick and easy way to change your region by using FasterFix that is free on the Market. At least it will quickly change your first gps.conf file line to the correct region and hopefully get you a gps lock. I suspect that the gps.conf file you are changing may not be correct or possibly the changes you are making are not being taken and the original gps.conf file keeps staying? I don't think it is the build. I've used TyphooN in the past with my custom gps.conf file that I use with no problem.
slbenz said:
Unfortunately, I can't see the link. Maybe you should try the quick and easy way to change your region by using FasterFix that is free on the Market. At least it will quickly change your first gps.conf file line to the correct region and hopefully get you a gps lock. I suspect that the gps.conf file you are changing may not be correct or possibly the changes you are making are not being taken and the original gps.conf file keeps staying? I don't think it is the build. I've used TyphooN in the past with my custom gps.conf file that I use with no problem.
Click to expand...
Click to collapse
Thnx anyway... I think I'm going to flash the win 6.5 back on... to check is my GPS receiver working... maybe it's a hardware fault, I've recently purchased it used, and flashed it to android immediately...