yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] squashfanatic:
Congratulations! My phone is always in portrait when I am in the car on bluetooth. Maybe I could buy a different case :-)
[Galaxy S I9000 Android Development] $omator:
only way to make this fc is like you said:

- a call (initiate/recive)

- wait till screen turns ITSELF out (system setting turn screen off)

- wait till the person you speak to hangs up

no fc when:

-

phone is turned into landscape at least once durnig conversation

-

in landscape mode with any of above conditions

-

when screen goes off triggered by proximity sensor

(basicly your head triggers it and the screen goes dark when your head is near phone front)

-

when you end a call

and the only downside of it is reloading Phone.apk witch takes seconds, and you are able to recive calls imidietley after that

well it is worth reporting to someone from samsung working on 2.3.4

but the conditions and consequences are so dimly that

it is absolutley safe to use stock jvq files

=) use the mod to enable landscape and just put phone to landscape

i guess this bug will be ironed down in next release, it is nt worth to be bothered with much
[Galaxy S I9000 Android Development] squashfanatic:
After my fc bluetooth stays on but does not work, even after I go out of range it shows connected but is not.

So Mr $omator, who has said for a long time this bug does not exist and we all can not have flashed properly etc etc, is there a slight hint of an apology, just a little quiet one?:-)
[Galaxy S I9000 Android Development] $omator:
because i was unable to replicate this

and today suddenly bam :)

need more data ;dddd
[Galaxy S I9000 Android Development] squashfanatic:
I could not quite see the word sorry, come on, it hurts I know but you can do it. I will accept Polish, I do at least know that word!
[Galaxy S I9000 Android Development] $omator:
=))))))))))) i am working on it / let me do my flash dance from froyo till gb
[Galaxy S I9000 Android Development] squashfanatic:
Ok, good to joust with you. And by the way, this guys fix does work, how strange is that! ;-)
[Galaxy S I9000 Android Development] $omator:
=) anyway this bug triggered my intentions to learn java

i see the error output in logs i can decompile the app to see those lines in code affected

but i have no idea how to fix it - this pisses me off over the edge

so in the process i might bugfix this apk sooner or later =)

from now every free second will be focused on java

and anyways he could add a odex version also
[Galaxy S I9000 Android Development] squashfanatic:
Well good luck for that, and thanks for your mods, could have been written with me in mind, same again next time a new rom appears, I did not like it when you went for the nexus data display, current one just right. Dobranoc
[Galaxy S I9000 Android Development] $omator:
thats why i attached all posible customizations ive found =) goodnite
[Galaxy S I9000 Android Development] Brotuck:
When using a phone.apk from 2.3.3 the phone uses more memory. But it works i guess.
[Galaxy S I9000 Android Development] fallenfuzz:
I know that ROM makers include that fix on their ROMs and customize it too.

Hope it will be fixed in the next samfirmware
[Galaxy S I9000 Android Development] embryo1:
Great fix. No more troubles in XXJVQ with Car BT or voice roaming. Tested 2 days.
[Galaxy S I9000 Android Development] senotrius:
the fix works well..10/10..using it for more than a week..but think the signal reception has got poorer..somehow??is it possible due to this fix
[Galaxy S I9000 Android Development] flypubec:
Learning Java will only make you drink more cofee,

unless you want to write your own Phone app.

If you decompile app's dex/odex you'll probably end up with smali, which is not even close to Java :)
[Galaxy S I9000 Android Development] flo2lacanau:
Your MOD fixed my FC !

After 2 weeks : no bug ...:D

Thanks.
[Galaxy S I9000 Android Development] ghosty7:
I cannot believe it, just tested JVR and that bloody phone bug is still there. you would think they would have fixed it...
[Galaxy S I9000 Android Development] fallenfuzz:
Did you test the mod if it works on JVR too?
[Galaxy S I9000 Android Development] squashfanatic:
+1

Until there is a fix for that bug JVR is a non starter
[Galaxy S I9000 Android Development] ghosty7:
The mod works, but still not the answer we all want.
[Galaxy S I9000 Android Development] $omator:
bull****, no phone bug on JVR

at least i can not trigger it the way i did on JVQ -> http://xdaforums.com/showpost.php?p=16013801&postcount=80
[Galaxy S I9000 Android Development] $omator:
hehe and now i see it is still there Oo once it fcs second time not ;) so i guess they are working on it. need to compare files
[Galaxy S I9000 Android Development] LULAFULA:
hey :) i just bought my galaxy s few days ago and flashed this JVR.

Since im a rookie in android id like to know what FC means .

Phone Fc what ?? :))) Sorry for my stupidity in this question.

Thanx
[Galaxy S I9000 Android Development] bbgt2:
FC= Force Close

An application you are using takes a big ol dump and doesnt work.
[Galaxy S I9000 Android Development] flypubec:
$omator you skepticism is epic. :D

I wonder if you beleive your mother that she gave birth to you.
[Galaxy S I9000 Android Development] bbgt2:
fallen fuz you are a genius. You saved this Captivate from being thrown into a wood chipper.

Thank you.
[Galaxy S I9000 Android Development] $omator:
hehe i know but thats the way it is

i had 2 fcs on 20 attempts today =)

but still fc ;D
[Galaxy S I9000 Android Development] ghosty7:
Your process to trigger is not correct, you need to be connected to bluetooth handsfree or have earphones connected, when this is done it will force close every time using my procudure. I use the car bluetooth all the time so this is a very serious bug for me and others. So please stop saying it does not exist, when clearly it does. Just follow the yellow brick road :-)
[Galaxy S I9000 Android Development] $omator:
does not need bt i guess =)
[Galaxy S I9000 Android Development] bbgt2:
Worked fine for one day and then today BAM, phone FC and reboot and BT not working again. Wood chipper you are gonna be fed soon.
[Galaxy S I9000 Android Development] $omator:
i guess it will just restart crashed services after the Phone.apk FC

making this bug even less harmfull than it is :)
[Galaxy S I9000 Android Development] squashfanatic:
Unfortunately not until you say ok to the fc dialog.box, in the car this may not be noticed. In my case the bt will not work again until I reboot.
[Galaxy S I9000 Android Development] fallenfuzz:
With the installed MOD or the stock files?
[Galaxy S I9000 Android Development] $omator:
yes you must press ok and bt should be restarted after 15 seconds after recognition of killed state so i guess you did not wait long enought.

and god damn it why i can not make a pattern here. sometimes same actions does not trigger the fc and sometimes does.

hopefully it will be fixed in next leak as theyve fixed a lot of stuff betwen jvq and jvr
[Galaxy S I9000 Android Development] cristi87:
I tried deleting the two files and flashing the fix.. Still FC on bluetooth headset on 2.3.4 xxjvq. Any more ideas? thx
[Galaxy S I9000 Android Development] fallenfuzz:
Guys,

Those who has the phone FC, your phones are 16G or 8G?
[Galaxy S I9000 Android Development] Birba:
@fallenfuzz: mine is a 8GB
[Galaxy S I9000 Android Development] fallenfuzz:
and u have phone fc?
[Galaxy S I9000 Android Development] Birba:
Yes, I do have FC when bluetooth is connected.
[Galaxy S I9000 Android Development] fallenfuzz:
what about headphone/regular call or speaker?

in what circumstances you have FC?
[Galaxy S I9000 Android Development] fallenfuzz:
works fine on Demian's tornado JVR, tested myself
[Galaxy S I9000 Android Development] squashfanatic:
Never let me down on JVQ but just had my first fc on JVR. 8G
[Galaxy S I9000 Android Development] cristi87:
I also have 8g and it FC's only after a call has ended with the bluetooth headset connected. Without it , there's no FC.
[Galaxy S I9000 Android Development] $omator:
Lets hope samsung developers follow such threads so we can have this problem sorted out in next release
[Galaxy S I9000 Android Development] :
Guys, i had this problem too (every time when using a BT headset), so i flashed the fix from OP.

After that seems to be working fine, i just have a question. When i'm in the phone aplication, and press the "menu", the menu shows up with dark grey icons, when the rest of the system has light grey.

I'm running a KIES version of JVQ, no themes, just CF-Root. Any ideias how to make it the same color? It really annoys me.
[Galaxy S I9000 Android Development] cristi87:
If it is a bluetooth problem , shouldn't there be a bluetooth.apk that we could get from somewhere ?:) It FC's not only when ending a call on bluetooth headset but after receiving data via bluetooth connection.
[Galaxy S I9000 Android Development] {Angel}:
Not that i dont appreciate the share but I would like to know what was done and maybe reproduce the hack. I dont feel comfortable installing a hacked phone apk without any details on what was done.
[Galaxy S I9000 Android Development] $omator:
everything you asked for is in first post mate ... just lol
[Galaxy S I9000 Android Development] {Angel}:
so it's they are just stock files? I don't believe that. I flash the fix out of curiosity and even the dialer icon changed and when you hit the menu button inside the dialer the menu items are darker (granted this could be an artifact of being a 2.3.3 apk)

Also I tried copying the apk and odex files from a 2.3.3 release and it did not work.

What I can take from this is that he means is that it is not themed not that the files are unmodified.

If the OP could clarify and give us more details, like from which release did he take the files and if they are modded in any way...
[Galaxy S I9000 Android Development] $omator:
STOCK do you understand?
[Galaxy S I9000 Android Development] {Angel}:
Yeah I understand, but I don't think you do. Man if you are not going to contribute in a polite way then just don't do it. What he means by that can be different from what you may understand. I asked some legitimate questions... like what release is this from and have they been hacked in any way becuase I tried to reproduce it with other files from a 2.3.3 release and it did not work, and they icons are different from stock.
[Galaxy S I9000 Android Development] $omator:
for crying out loud are you thinking for one freakin second?

do you understand what does stock mean?

untouched. he also added not themed, because people like to ask stupid questions

do you understand what does 2.3.3 stand for?

it means not jvp,jvq,jvr - because those are 2.3.4

now thinking more. files are apk only -> they are deodexed

where does xda user search for deodexed firmwares?

in ramads thread -> LINK

now we take 1st european 2.3.3 of the top of the list,

oh look it is jvk for serbia - who cares we do not have eternity

now we decompile files provided there and oh what a suprise,

those serbian files matches the ones provided in this post

was it hard?

youve just wasted 25 minutes of my life - are you proud of yourself? =)
[Galaxy S I9000 Android Development] ghosty7:
It is not a bluetooth problem, it also does it with the normal headsets plugged in or the speaker turned on. It is definately in the dialer files.
[Galaxy S I9000 Android Development] cristi87:
@ghosty

I don't have this error after a normal call, only when I use the headset or transfer some files. It used to happen even after a normal call but the fix solved it, so that's why I believe it's still from the bluetooth.
[Galaxy S I9000 Android Development] squashfanatic:
Lol $omator, you nailed it.
[Galaxy S I9000 Android Development] paroulis:
does anybody knows if it is posible,to change the 2.3.4 bluetooth files with others from a 2.2.1 rom?
[Galaxy S I9000 Android Development] cristi87:
Yeap Ghosty is right , it's a phone and dialer error, it started again to lose signal and FC in normal calls also...
[Galaxy S I9000 Android Development] fallenfuzz:
Mate, you made me cry, ahahahahahahahahahahaha!

Great answer
[Galaxy S I9000 Android Development] {Angel}:
First off, I made some completely valid questions, he does not mention what 2.3.3 release he used, so I was not about to try every release out there and how would I know he used one of ramads deodexed releases? He could have deodexed them himself. If you did that (download release and compare them) then you got lucky and I wonder why you even bothered... hmmm... I think the OP giving an answer seems easier then doing some investigation to find where he got them from, I don't have that kind of time like you do on my hands. It's obvious the OP says they are stock but as I said I tried the files from a 2.3.3 release and it did NOT work, and the files posted here even changed the dialer icon when I flashed it.

The OP was not clear and you my friend try to sound more intelligent than the rest but you gotta admit it's kinda foolish to flash system apps that some random guy posts and not question where they come from.

Get a life man.
[Galaxy S I9000 Android Development] $omator:
i just showed you that it needed just a litle thinking and reading with understanding

sadly, you are true waste of time
[Galaxy S I9000 Android Development] cristi87:
come on guys , where just trying to solve a problem...so chill...regarding that , does anybody have another idea?
[Galaxy S I9000 Android Development] SnoopyDog:
If you mean with "stock" that these files in the patch are the originals from any Samsung ROM: No, they are not! They contain "dex" files which means they are deodexed. The original files from Samsung are never deodexed!
[Galaxy S I9000 Android Development] $omator:
i see you troll multit hreads

odex/deodex is irrelevant

there is not a single space or letter changed, do you copy?
[Galaxy S I9000 Android Development] SnoopyDog:
@fallenfuzz: Thank you very much for providing these files. :) They definitely fix the FCs when the other side hangs up on blutooth calls (or e.g. also IP calls with the Android native SIP stack).

If you have an odexed ROM, it is important to delete the 2 .odex files as mentioned in the first post. And i also deleted the dalvik-cache, don't know if it's necessary, but sometimes the phone behaves a bit strange after you replace the Phone.apk file.
[Galaxy S I9000 Android Development] Advali:
thanks a lot man! the files do indeed fix the FC while im playing thru my BT headset, received a call and then hangsup. I'm on F1 Galaxy by the way, and it really fixed the issue! Thanks!
[Galaxy S I9000 Android Development] shaarky:
Hi,

just had to install this because I experienced FC issue when I was calling abroad!(like +421xxxxxxx but +420xxxx are ok?!).But - on Juwe's 5.3 it didn't help, still I'm experiencing FC issue.

It starts ringing and then error - force close of android.phone - Any idea please ? Thank you.

*update* strange - it crash,but I was able to make the call.After I quit the call, signal get lost for few seconds and error message - after confirmation everything is back to normal?
[Galaxy S I9000 Android Development] {Angel}:
I don't know why I bother with you.... but the difference between odex and deodex is not irrelevant. Ask anyone with lag issues on an deodexed 2.3.4 fw.

Stock is indeed original odexed.

good day.
[Galaxy S I9000 Android Development] fallenfuzz:
I think that this fix is already included on Juwe's ROMs
[Galaxy S I9000 Android Development] jelle2503:
Framework fix for this lag you mention is already out. So deodex or odex is irrelevant.

But maybe you should not flash it since its made by a random guy.
[Galaxy S I9000 Android Development] Brotuck:
There actually is a difference in deodexed and odexed versions.

If it would be all the same why would samsung then release a odex version ?

In tests i did on my own ROM odexed and deodexed there actually is a difference in booting and starting apps. This is no placebo effect, there really is a difference.
[Galaxy S I9000 Android Development] SnoopyDog:
Yes, this is true. But you can NOT replace odexed apps with other versions 1:1. You need deodexed files and delete the original .odex files!
[Galaxy S I9000 Android Development] cristi87:
does anyone know if this problem is also on xxjvr?
[Galaxy S I9000 Android Development] {Angel}:
It is.
[Galaxy S I9000 Android Development] ZaneZam:
at least on this "scary" first leaked JVR stock, and for me this fix worked!

unfortunately the new "swisscom" leak seems to be the same rom except CSC part

so we can assume the bug is still present in this rom. :(
[Galaxy S I9000 Android Development] DeusEx80:
@fallenfuzz: Thank you very much for providing these files. They definitely fix the FCs when the other side hangs up on bluetooth calls.

I have applied this fix on JVQ and now on JVR :)
[Galaxy S I9000 Android Development] Hrithan2020:
Need help. I am not able to get this working on odexed stock JVR.

I deleted the corresponding .odex files, and then flashed this, but the phone application is not showing now. The permissions is set as 644. Any idea what the issue could be?
[Galaxy S I9000 Android Development] ZaneZam:
If you use twlauncher you could try to delete homescreen settings (delete data in app settings) and reboot right after that. note, this will reset all your screens to stock default but maybe it helps. ;-)
[Galaxy S I9000 Android Development] Hrithan2020:
I am not using twlauncher, and the problem doesn't seem to be with the app drawer. Using search via google [the widget] or titanium backup , fails to show the phone app.

I had to switch back to the odexed phone apk for now . Would love to have the multi-DPI dialer :(
[Galaxy S I9000 Android Development] $omator:
http://www.multiupload.com/MISEHLWM8A via cwm recovery
[Galaxy S I9000 Android Development] Hrithan2020:
May I know the difference between the one posted in OP, and this link?

Does this also have the multi-DPI dialer?
[Galaxy S I9000 Android Development] $omator:
no diff - the file is stock 2.3.3 suitable for both odex & deodexed
[Galaxy S I9000 Android Development] Hrithan2020:
Tried still doesn't work. :( ..

Any tips/suggestions to go about solving this issue?
[Galaxy S I9000 Android Development] fallenfuzz:
Try to manually extract and replace 2 files with root explorer.
[Galaxy S I9000 Android Development] Hrithan2020:
Did that too. Still not working. Can't fathom how others with odexed ROM's are able to get this working.
[Galaxy S I9000 Android Development] Brotuck:
What rom are u using ?
[Galaxy S I9000 Android Development] Hrithan2020:
Stock odexed ROM.
[Galaxy S I9000 Android Development] gokhan76:
I have replaced both Phone and Dialer apk after deleting odex files with Root Explorer.

When I rebooted the Phone I only had contacts messages and menu icon was in the main screen Phone icon disappeared somehow.

Using Stock JVR with Semaphore 1.5 Galaxy S I9000

Also My It couldn't read my sim card afterward
[Galaxy S I9000 Android Development] Hrithan2020:
You mean the Phone app is not visible [even in the app drawer, or via search]? I am having the same issue. Seems like noone knows how to resolve this :(
[Galaxy S I9000 Android Development] gokhan76:
Yes exactly the same issue,
[Galaxy S I9000 Android Development] $omator:
- is it listen in app list in settings/applications/manage aplications ?

- try clearing cache there if it is

- try clearing dalvik cache

- try deleting the files rebooting and copying them once more (then reboot + cwm fix permissions)

it is not possible that it disapears, you guys are doing something wrong
[Galaxy S I9000 Android Development] mbarreto:
Thanks for this! It's AWESOME and works great. I was freaking out with all the FC.

As for you guys, that disappearing thing happened to me and I fixed it. Delete the .odex files and then FLASH the phone fix.zip using CWM. If you copy the two .apk files with root explorer it won't work.

ROM: 2.3.4 Stock JVR

Kernel: Semaphore 1.6.0beta1 (CF-Root + Voodoo Sound v10 + OC/UV + BLN)
[Galaxy S I9000 Android Development] ZaneZam:
Yeah, and DON'T reboot before flashing the fix. I did this accidentally and my phone app disappeared. So thats the right order: delete odex files then boot into recovery then flash fix and finaly boot normal. Then all should be good! ;-)
[Galaxy S I9000 Android Development] Hrithan2020:
Forgot to check whether it was getting listed in the applications, but considering that both Titanium backup and normal search wasn't able to solve this, I don't think it would have been listed.

Tried clearing, flashing, reflashing, fixing permissions etc. Seems like it just won't work. If someone, does get it working magically do let me know, what I am doing wrong, lol.

It doesn't work via FLASHING.
[Galaxy S I9000 Android Development] mbarreto:
Mine is working. Maybe you have a compatibility problem. Whats your ROM/Kernel?
[Galaxy S I9000 Android Development] gokhan76:
Can you tell us Exactly how did you manage to do it from CWM?

Mine does not work either Stock JVR + Semaphore 1.5 with Galaxian EE

Regards,
[Galaxy S I9000 Android Development] Hrithan2020:
Stock JVR odexed with TalonDev 0.4.21.
[Galaxy S I9000 Android Development] $omator:
ok again me, new probable way of fixing fc issue. this time fully 2.3.4 based Phone with bugfixed code (probably) can you guys that was able to reproduce the issue try the new files?

you must copy those manualy

http://xdaforums.com/showpost.php?p=17086002&postcount=1272
[Galaxy S I9000 Android Development] fallenfuzz:
First try with speaker, no FC.

I'll try later with headphones.

Thanks for the fix
[Galaxy S I9000 Android Development] nozerogravity:
Thanks stary :) Works great on JVP.
[Galaxy S I9000 Android Development] $omator:
thats not me that came up with the fix but thanks anyway =)
[Galaxy S I9000 Android Development] mbarreto:
Sorry

Sorry, I didn't see this before. After copying the files with root explorer and rebooting, my phone app disappeared. I really didn't know what to do, so I flashed it like any other zip, nothing different. After rebooting it was working with no more FC. That's it :)
[Galaxy S I9000 Android Development] ZaneZam:
Great, thanks! Also working for me here on JVR stock! I was on that "2.3.3-fix" before and i've cross-checked with stock files. The fc reappeared instantly! After applying your file fc was gone (hopefully forever!) :-) But one "little" negative thing i have to report: i'm on speedmod kernel with su installed from that and your permission-juggling in the update-script nuked the su command! Why happend that? can you check this? Will see if reinstalling su in speedmod- recovery will fix this and let u know!

Btw i discovered your stock+ mods. Very nice work, found some missing stuff for my customizing-study! Also thx for that! ;-)
[Galaxy Tab 10.1 General] cyberleader:
Ive read through the forums and how to restore to the stock ROM. Now I figured out how to not only restore to the stock rom but keep root access as well. Just takes a long time to do it. If you are willing to wait its a much more stable way to fix your rom problems.

First of all you will use ODIN and the PDA_SIGNED_P7105.tar.md5 rom.

This rom comes pre rooted. Now after you get that reloaded with odin download rom manager and do the flash clockwork mod feature.

Now open Setting on your tablet and then go to About tablet.

Now select the system Update selection then click on update

Now click on check for update and Select ok when prompted.

It will then bring you to a place where you will need to sign in with your samsung account. Sign in and update and walla after 40 minutes you are back to stock rom with the root access as well as the CWM.

It will then reboot to the TABLET 10.1 SPLASH screen and do a very very slow update. It will have a status bar. If you see that then you are on the right track. Remember it took a long time to do this sort of upgrade.

I also updated the kernel for the OC part of SETCPU.

Also if you have the samsung dock. Do not use it. It messes up flashing any type of roms or installing some programs. IMHO think it was a rip off it doesnt work correctly.