yashsingh1/xdaforums huggingface dataset:
[Desire General] I RICHY I:
So, I like to link my contacts to their Facebook accounts. However, since I upgraded to 2.2 I've been unable to link a particular friend and now I'm having trouble with another.

I've tried deleting my Facebook account off my phone and readding but it doesn't seem to work. Anyone know a fix?
[Desire General] iL_FeD:
wich ROM are you using? Facebook for HTC Sense makes it easier to link contacts, but in stock Androids contact app is also possible, have you check that the facebook account is not actually linked to another contact?
[Desire General] PureLoneWolf:
I had a similar issue earlier (am using Cyanogen)...turns out my friends name on Facebook was wildly different to his name in my contacts.

I had to set a nickname for him that was the same as his facebook name..then he showed up as a suggested contact when I chose to join.

Not sure if that might help.
[Galaxy S I9000 General] Vertigem:
Greetings mates, I bought my SGS - I9000 2 weeks ago and I'm delighted with it's capabilities (not mentioning some occasional lag, but nothing to worry about).

So, my SGS is network blocked, and recurring to a guy who owns a mobile store and unblocking my SGS would cost me 10€. But I thought "why Am I going to pay 10€ to unblock a phone that already has it's own unlock codes inside it and Im able to block it again for warranty purposes, while this guy just wants to hard-unblock it?!".

I've read the guide about unlocking the phone using the tool "Generate Unlock Windows" and the "SGS Unlock Tool", seen a few vids showing how it was done.

I did exactly this:

1 - Turned on Kies

2 - Turned on USB Debugging on phone

3 - Plugged the USB cable

4 - Mounted SD Card

5 - Ran "Generate Unlock Windows"

Everything was running smooth when I got this:

===============================================================

===============================================================

Generate unlock code for any Samsung Galaxy S

===============================================================

===============================================================

__________________________________________________________

Copy nv_data.bin

* daemon not running. starting it now *

* daemon started successfully *

Extract code

SGUX v0.92b (C) 2010 By Mark0 & rbnet

Samsung Galaxy Unlock code eXtractor

(based on info by rhcp0112345 & RazvanG)

* Error: unable to find file <.\nv_data.bin>

It wasnt possible to find D:\DOWNLOADS\Samsung Galaxy S\Generate Unlock Windows

\Generate Unlock Windows\nv_data.bin

===============================================================

===============================================================

Please donate to DagentooBoy for the script

Please donate to rbnet.it and marcopon for the SGUX utility used in the script

===============================================================

===============================================================

Script complete!

After I got this message I went searching for nv_data.bin on the phone and sdcard, and in fact there was absolutly no nv_data.bin file around. Therefore, I tried the following steps:

6 - Installed SGS Unlock tool on phone

7- Ran it and got the following message: "Sorry, no codes found. File not found: Do you have a Samsung Galaxy S?". I depreend that the file it cant find is nv_data.bin..so the same issue remains and once again, nv_data nowhere to be found.

8 - Installed "Terminal Emulator" and ran the following commands: "cat /efs/nv_data.bin >> /sdcard/nv_data.bin"

9 - This action resulted in the message: "Permission denied"

10 - After all this I realized that nv_data.bin was now showing on the phone main directory. But the file had 0 bytes.

11 - Tried again to use the "Generate Unlock Tool" but got the same message as before.

So after all this, I would be very pleased if anyone could help me understand what's going on and how to fix this issue.

I payed 600€ for this phone and I'm still using the old one for the main SIM (Vodafone), and I'm no way willing to pay 280€ to my network to unblock the phone.

Cheers
[Galaxy S I9000 General] andreschardong:
I have same problem here. looking for help. thanks
[Galaxy S I9000 General] ppmanrique71:
I have the same problem

My firm is I9000XXJPK.
[Galaxy S I9000 General] Vertigem:
I forgot to post some phone information that might be useful to solve this problem:

Version: I9000XXJM4

Kernel version: 2.6.29

root@SE-S603 #2

Compilation number:

ECLAIR.XWJM8

Also, I was able to find the file through "Android Mate" (after rooting the phone) and was able to copy it to the SD, although I still got the same problem using "Generate Unlock Windows".

I even tried to use an Hex editor to find the code, but all I've found was the network operator number.

I've tried another way as well, which was to copy the nv_data.bin or the bml3.bak files to the SD and then copy them to C:. After that I placed "Sgux" in the same directory and ran it (as read on a tutorial on XDA), so everything was running fine, Sgux found the codes but didn't displayed them.

As shown:

c:\>sgux2.exe nv_data.bin

SGUX v0.92b (C) 2010 By Mar

Samsung Galaxy Unlock code

(based on info by rhcp01123

Opening file <nv_data.bin>.

Searching code block...

Found.

Searching codes...

<---------------------- The codes should be displayed here, but they aren't

c:\>

:confused:
[Galaxy S I9000 General] andreschardong:
seems that with I9000XXJPK it's impossible extract unlock code.. still trying.
[Galaxy S I9000 General] Kajolas:
I have also this problem with JPK (2.2) and JFF(2.1 July), can someone help?
[Galaxy S I9000 General] tony604:
I manually extracted my code with the info from this web site:

h t t p : / / thetechjournal.com/electronics/mobile/how-to-unlock-galaxy-s.xhtml

I installed the unlock app from market and it gave me a code which did not work for some reason, which is why I decided to manually extract the code. Ironically, it was the same code. I ended up locking it the carrier I wanted to use it with, not the carrier it was originally locked to which works at the end of the day anyways :) Hope this helps
[Galaxy S I9000 General] Vertigem:
Well I did that already, and all I got was this:

.........SSNV.....M..9. F....u..@c<...F].~q.+.....b7..{..',.Xq;.g....h.....R..A...FFFFFFFF........................26806#

Where 26806 is the network code, and i dont know what the rest is. I even tried to convert the string "FFFFFFFF" but no luck with the obtained combination.
[Galaxy S I9000 General] vinclar:
Can I unlock my galaxy S

It didn't work the two sgs unlock apps, neither sgu.exe and sgu2.exe

Galaxy S JPK

I can't unlock it too in bml3.bak I found four strings SSNV allocated in:
[Galaxy S I9000 General] eflizano:
I have the same problem... I only can do a emergency calls, please is somebody know how to solve the problem .... please help.... i´m desseparate
[Galaxy S I9000 General] lupy:
Your phone needs to be rooted to copy the file, you can find different solutions on the forum
[Galaxy S I9000 General] coradux:
Upgrading to JPC, JPH or JPK corrupts efs files, that's why you can't extract codes from nv_data.bin. The code is now FFFFFFFF but you can't enter it because you can only enter numbers. I also upgraded to JPH and couldn't extract network code from nv_data.bin. You have to edit the nv_data.bin files to enter a network code that you could use when you insert another SIM. I followed this steps and unlocked my phone thanks to helroz:

http://xdaforums.com/showpost.php?p=8182729&postcount=107
[Galaxy S I9000 General] tzh2231:
I have all FFFFs for my code too, however, even if I follow steps in the modify nv_data.bin link, it is not working for me. I have a few questions if any of you guys succeeded with the method:

1. Offset 188021 (page 3137) put "XEF" (for france) or whatever, this seems not necessary? since my model string is SGH-T959ZKBTMB and that offset is already TMB. What is your experience?

2. Offset 18146E (page 3083) Change "FFFFFFFF" to "00000000".

I think he mean change to ascii characters "00000000"? So the hex would be "3030303030303030", right? I did this and it is not working for me.

Actually I am very confused by this step, becase this offset is no where close to my SSNV string. My first set of FFFFFFF start at offset 180049, and 2nd set

maybe this guy.

Did the post miss the 1st set of FFFs?
[Vibrant Q&A, Help & Troubleshooting] willsnews:
Just a question I haven't seen it up before so I figured I would ask

Willsnews
[Vibrant Q&A, Help & Troubleshooting] gravis86:
That would be awesome and if I knew how to make one, I would. I did a quick Google and found nothing :(
[Vibrant Q&A, Help & Troubleshooting] willsnews:
I was going to grab the attention of a developer with this post it would be awesome

Willsnews
[Vibrant Q&A, Help & Troubleshooting] SBboundbRONCOS:
i agree this would be super freaking cool
[Android Software/Hacking General [Developers Only]] fmvidal1:
So I installed unlease the beast runs great just still no wifi tether so I wanna delete it and instal on that works but can't seem to delete it even with root explorer :( any suggestions
[Android Software/Hacking General [Developers Only]] evilkorn:
You have to mount /system/ as rw. Search and ye shall find.
[Tilt, TyTN II, MDA Vario III Android Development] elander:
wow, first time I get to post first post, what an honor, jejeje, anyways this is looking good I'll download and try it, the timing couldn't be better as I am using myn's warm donut and after messing around with njtr2 battery mods somebody told me that I'll have troubles because of the sysinit.rc had some codelines to set it at 2000mah so I had to change that, anyways since I messed both system and data so much I was going to reinstall everything, but now I'll try yours first. thanks
[Tilt, TyTN II, MDA Vario III Android Development] WarByte:
I am glad you feel honored, you must also know this is the first thread that I create and so I am even a little nervous about the reception. Oh I know what ya mean, I've been messing around with that famous sysinit.rc and trust me, it was a headache. Tried both a new battery that I got and my old messed up one, which drops to almost nothing in 5 mins. In both cases, the battery seems to indicate an accurate current charge and recharge. Good luck with everything, and please let me know what you think :)
[Tilt, TyTN II, MDA Vario III Android Development] elander:
weird, I'm trying to download this from the link (mediafire) but after I click on the "click to start download" it stays on your download is about to start....
[Tilt, TyTN II, MDA Vario III Android Development] WarByte:
Hmmm weird, just tried the link here. Works okay and starts. I had a couple issues some weeks ago when downloading from media fire. The server would not be found, it was okay later. Could I ask you to wait a little and try again? if it doesn't work for you I will try to have a mirror link as well.
[Tilt, TyTN II, MDA Vario III Android Development] elander:
thanks for such a fast reply, I told you what happened so you know, but I was going to wait anyways, (as some say patience is the key, lol) on a side note (and a little off topic as well) could you please tell me how did you manage to get rid of the battery settings on sysinit.rc, cuz I'd love to try the new battery kernel in my current installation (as it is pretty much broken anyways) as I wait for mediafire to "like me". thanks!
[Tilt, TyTN II, MDA Vario III Android Development] WarByte:
Sure thing. well, I guess this is gonna be a feared answer but the method is by hand. Grab an editor that does not mess up your ends of line. I use pspad for this kind of thing. the .tar file is just a compressed file you can open with winrar or 7zip for a free alternative. Open your sysinit.rc, look for the lines sys/module/board_kaiser_battery/parameters/battery_capacity, that is where the value is set. The most common builds I have seen have a #battery patch comment so you can just delete that section. Save your file, dump it back in your .tar file and install.

I have also used androidupdate.tar if you wanna make it an update instead of a reinstall, just make sure it is in the correct path. Should be the same path you see in androidinstall.tar.

One thing I gotta warn you, I have always been tempted to realign tabs and delete unnecessary whitespace. The last time I did that it resulted in weird wifi and bluetooth behavior, so be careful and only change what you need. Save a copy of your original file so you can always "update" it with the old one in case you mess something up accidentally. Patience, that works. Take a deep breath, watch some tv, then try again :)
[Tilt, TyTN II, MDA Vario III Android Development] cnigro1279:
Nice....

I must say it is refreshing to see someone doing something new with the Kaiser!!! I just may give this a whirl tomorrow!!! I'll chime in if I do......
[Tilt, TyTN II, MDA Vario III Android Development] fahkin:
i wanna try it....

let me download it first
[Tilt, TyTN II, MDA Vario III Android Development] WarByte:
@cnigro1279 There aren't too many new things with this, just trying to save people some time and work :) I have great love for the Kaiser, it's like a good old faithful friend. It just goes through several battery packs. Please give us some feedback if you decide to try it.

@fahkin Appreciate the interest :)
[Tilt, TyTN II, MDA Vario III Android Development] elander:
I´ve been messing with this build for a couple of hours and I must say It is great so far, the only issues I have are: the terminal emulator force closes, but it is not a big deal I just uninstalled it and downloaded it again from the market, and the second one is not really an issue but raher a matter of taste, I installed this with the recommended resolution 320*428 with a 144 dpi setting, thinking that maybe this time I´d get it to look less blurry than last time I tried such resolution, but it´s still the same, so I´m gonna try this with 240*320 and a dpi value of 117 (as I recall being able to fit almost everything onscreen last time I did it) so, I feel tempted to ask, What are the chances of getting a fix for 240*320 resolution? (myn´s warm donut has it I think) anyways great work, oh by the way I love the look on this one, it makes me forget about froyo (although if I could them the widgets to look like the froyo´s it´d be a dream come true,lol), overall very fast and stable (so far) build, with great looks and the fact that it is deodexed leaves rom for theming it the way you like it. thanks.
[Tilt, TyTN II, MDA Vario III Android Development] kljoki:
Thank you !

Thank you WarByte !

I will give it a ride on mine Kaiser :)
[Tilt, TyTN II, MDA Vario III Android Development] kljoki:
About resolution confusion

@elander

you can take a look at:

xdaforums.com/showthread.php?t=667581&page=4

xdaforums.com/showpost.php?p=7767902&postcount=3
[Tilt, TyTN II, MDA Vario III Android Development] WarByte:
Thanks for reporting!

@elander Thank you for reporting back. Yeah the clearest screen you can get is using the native QVGA resolution of the Kaiser, I might suggest trying a DPI of 121, that one looks great with that resolution. I could attach another kernel and an androidupdate.tar with the DPI setting, though you could edit the kernel with Atools and the included Rogue Tools app in the rom lets you change the DPI setting to anything you might want to try. After the change you just need to reboot. I got some apps force closing if already included in the package as opposed to installing them after the rom. Apparently I missed Terminal. I also thought about using Better Terminal since most builds have it and the one I am using doesnt let you use a soft keyboard. I am glad you liked the build :) By the way if you use a QVGA resolution your dialer is gonna look messed up, buttons over each other. Please check out a modified dialer for Warm Donut at http://xdaforums.com/showpost.php?p=6402522&postcount=4080. This should work well with it.

@kljoki Please do and let us know how it goes, if there's anything I can help with I'll be glad to try my best.
[Tilt, TyTN II, MDA Vario III Android Development] kljoki:
ok, don't forget I'm using HaRET

The things which does not work on my Kaiser or I didn't have a luck:

- camera force closing (FC)

- terminal (ok, you just explained why)

unstable:

- wifi signal, I had a lot of system confusions and retries, in general it working

- WiFi Static

I was trying with panel 3,2 and 1 in default.txt,

and was thinking to flash an old radio as you suggested

but from your sig I can see we are using same radio versions.

Thanks.
[Tilt, TyTN II, MDA Vario III Android Development] rollride:
Downloading... will try it later `cause i am really tired but thanks for the build anyway :)
[Tilt, TyTN II, MDA Vario III Android Development] elander:
THanks for the tips, but I already knew how to work with resolutions and rogue tools/atools/nbheditor, thats why I said that I was going to try this with a 117 dpi/240*320 resolution as I know that most things, (including the dialer) fits the screen and also looks better/less blurry, what I meant is that I wanted to know if there was a chance for this to get fixed to fit in a 240*320/120 dpi, that's why I mentioned warm donut, (cuz somebody got most things including dialer fixed for a 240*320/120dpi and put up an android install), so that way we wouldn't need to use 320*428/144 dpi, as (in my humble opinion) it looks a little blurry. anyways thanks for everything so far this is in my top 3 list and this is only the beggining (rls1). kaizen!!!!
[Tilt, TyTN II, MDA Vario III Android Development] xtr3m3:
I just recently got the Kaiser, and have been trying out Android.

After messing around with most the ROMs, I must say, this one is stable and already has wifi and bluetooth working for me.

Thanks!
[Tilt, TyTN II, MDA Vario III Android Development] WarByte:
@elander Sorry about forgetting haret, I just way too used to nand. I know what you mean now and actually a couple days ago i was trying a lockbot demo and it wouldnt fit so i found a dpi that gave me almost the same QVGA look though blurry. I thought of resizing the dialer. You got me interested so I'll work on it. Test on my quasi QVGA and I'll rely on you for some actual final testing since i cant flash another kernel. Maybe later on we can get some froyo looking widgets a reality :)

@randomgoon Glad it worked for you. Appreciate your feedback.

@All i can confirm working radios: Nikki, 1.70 and 1.71. I have never gone below 1.65 and noticed almost no difference. Most people recommend a 1.65 radio.

--
[Tilt, TyTN II, MDA Vario III Android Development] WarByte:
Rollride! Good to see you here. Get some rest then let us know what you think. Hope you like it :)

--
[Tilt, TyTN II, MDA Vario III Android Development] WarByte:
Is there a chance you got a corrupted .tar file? Putting more stuff into /data/app shouldn't break anything, worst case scenario, the app won't run at all.

I don't think SPL has something to do with it, and that radio should work just fine, try a 1.65 radio, some people have reported it being great with Android.

Panel types are not related to battery display AFAIK. Without reinstalling try your old battery. Was your old battery reporting accurate charge?

Have you changed kernels since the last time you saw accurate battery charge? if you did try going back to the kernel that worked best for you.
[Tilt, TyTN II, MDA Vario III Android Development] marcelotorres:
I'll will download 1.65 radio.

The panel that i was use is 27-06-10, but i was thinking what kernel could works better for me...the olders like this 27-06-10 (2.6.25) or the newest like 09-09-10 (2.6.32) booth from DZO's site.

I was trying to use the latest kernel from l1qu1d's site, edited to use on kaiser.

Maybe my "changes" have broken something in the build.
[Tilt, TyTN II, MDA Vario III Android Development] WarByte:
I like 2.6.25 (I kinda have to), try them all and see what works better. Do a fresh install with the default RLS03 and try every kernel for a couple of days, see which one works best for your battery readings. Once you have solved that issue then go ahead and add some apps. If you try to test too many things at once you might lose track of what is causing what.
[Tilt, TyTN II, MDA Vario III Android Development] marcelotorres:
I have read a thread about a mod kernel that promisse display the true battery %

i will post the link.

This is the link:

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

It's a kernel or just a way to do the kernel show the real % battery?
[Tilt, TyTN II, MDA Vario III Android Development] WarByte:
I think n2rjt could help you more over there than I can over this thread if it is strictly related to his modifications. If I remember correctly Elander was succesful using attempt #5 in that same thread.

Have you tried your clean install with the kernel I attached? Try the clean install with each kernel for a couple of days. If it was working well before there is no reason for a new battery to cause that unless of course your battery is defective. Did you try your old battery as I told you and checked the readings?
[Tilt, TyTN II, MDA Vario III Android Development] WarByte:
Please ignore this. Double post due to crappy connection.
[Tilt, TyTN II, MDA Vario III Android Development] marcelotorres:
I will try now, in a few minutes i will post result

I'm trying this now

So, why the font is so little?
[Tilt, TyTN II, MDA Vario III Android Development] marcelotorres:
Warbyte

I found the kernel that i was use is 26-07-10, not 27-06-10.

Everything is working now.

Thanks man!

I PM you, see your inbox.

Good night my friend!

:D
[Tilt, TyTN II, MDA Vario III Android Development] WarByte:
Glad it's working now. Good night man.
[Tilt, TyTN II, MDA Vario III Android Development] Ducamau:
Congrats for this mod android version.

I tray many others, and this was only that fits with no problema in my Kaiser (TyTN II)

Other cooks when I install sys on NAND and data on SD partition ext2, runs very slowly, or get some yafs error and force close, or wifi does not work.. etc

But in that, everything works fine... and very fast.

Well.. peraphs some minor erros apears afters 48hs

Some minor issues:

- Freeze when standby (the display does not turn on when I press power in sometimes, and I have to do a cold reset)

- Wifi signal is instable sometimes, and does not conect with my network (and I have to turnoff and turnon again wifi in setup ... and then conection occurs)

- Market stops work properly yesterday... when I press Install in any program i get a window error: "Sorry! The process com.google.process.gapps has stopped unexpecteldly. Please try again".. but everytime now is the same (in begginin the market works fine)..

Similar error message apears when I start GoogleTalk, but the process name is differente (com.google.android.talk).

_ Battery uptime with WM6.5 is around 3 days (moderate usage) and 1 day (above 24hs) with hard use... in Android (even this cook), batt drains around 12hours... 14 maybe

Ther is some hint (or update) to fix this issues ?

TIA

[]s