yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] Hrithan2020:
The odexed one, i was able to flash successfully. But, I guess this won't be multi-DPI [for that changes needs to be made in dialertabactivity, I think] :)

Yeah, the wifi idle power consumption is way too high!!

By charging bug, do you mean the discharging which happens if your phone is still connected after 100% charged? I think, it is fixed, if you are using custom ROM's like TalonDev.
[Galaxy S I9000 Android Development] $omator:
i do not use custom kernels =) yes i mean that wierd discharge

http://xdaforums.com/showthread.php?p=17110617#post17110617

and no phone have only mentioned tweaks, i do not use other dpis
[Galaxy S I9000 Android Development] {Angel}:
Cf-root is a custom kernel :p
[Galaxy S I9000 Android Development] $omator:
its a root only, not touching anything else
[Galaxy S I9000 Android Development] {Angel}:
It has a modified initramfs with quite a few.more things other than root. But out of the alternatives its closest to stock.
[Galaxy S I9000 Android Development] $omator:
do you know what initramfs are ? =) and why it needs to modify it? lulzs
[Galaxy S I9000 Android Development] {Angel}:
Yes i happen to know what it is... You seem to think I am questioning why the initramfs has to be modified... I am not... Simply stating cfroot is a custom kernel. Custom comes from customized in case you didn't know :) its close to stock but custom nonetheless. I hope I made that clearer, mull on that for a couple of hours so your brain can process.
[Galaxy S I9000 Android Development] $omator:
am to lazy to decompile to show you exact diff betwen initramfs and explain to you whay those are 'no changes' but take a look what is added by cfroot

- Root

- Superuser 2.3.6.1

---- Busybox v1.16.2androidminimal (from CWM)

---- Integrated CWM 3.0.0.5 / RFS

that should let you understand difference betwen cfroot and custom kernel
[Galaxy S I9000 Android Development] {Angel}:
I bet that its not because you are too lazy, you just don't know **** about it :) its still a custom kernel whatever way you look at it. it's definitely modified, anything that is not pure stock is custom. this is the last thing I'll say about this pointless argument. Good day!
[Galaxy S I9000 Android Development] original_mos:
Works great :-)
[Galaxy S I9000 Android Development] gazou_hb:
Help for phone with BT in car

Dear All,

I have Installed JVR R4 rom of ficeto and the darkcore 3.1 Kernel, But I don't can begin or phone a call with the BT in car. my phone is paired with the BT.

I don't have any problem with call on my phone and no FC with the phone apk.

Do you have any idea for solve this problem?
[Galaxy S I9000 Android Development] gokhan76:
Reproduced Errors even after Patch

I had an FCs even after the patches today it just started after 3 days later.

Here are the logs...

Now its happening nearly after each call...

If I do loud speaker more ofthen
[Galaxy S I9000 Android Development] no.one.writeme:
Hi,

Are you using the correct version, ie, ODEX version with ODEX rom, DEODEX version with DEODEX rom?

Best regards.
[Galaxy S I9000 Android Development] gokhan76:
Well,

I am using Stock JVR with Semaphore + GalaxianEE

Now I though I should apply ODEX version which is correct for me.

But I still had these errors.
[Galaxy S I9000 Android Development] $omator:
so you scr#%&(*d up somewhere - fix is working great

oh and btw we do not have crystal balls to see what kind of errors youve got and why

and one thing more, how is that you use two kernels aat the same time =)
[Galaxy S I9000 Android Development] ghosty7:
I was one of the biggest critics for this bug, but this fix is definately working great. You must have done something wrong....
[Galaxy S I9000 Android Development] $omator:
btw odex version from my posts will work with jvr only probably

deodexed vesrion should not have such problems
[Galaxy S I9000 Android Development] manudevil:
I'm using the $omator version of this mod.

I have just a question: I have (had?) sometimes BSOD. Could it happen because of the phone.apk bug?
[Galaxy S I9000 Android Development] $omator:
i never saw blue screen of death on android :)

what do you mean by that
[Galaxy S I9000 Android Development] ZaneZam:
No no, he means bad seed of devil!

:-)
[Galaxy S I9000 Android Development] $omator:
youve lost me here :)
[Galaxy S I9000 Android Development] ZaneZam:
To be serious, i never had one of these Black Sheeps of Destruction on my phone but i got definitely phone process fc's and nuked bluetooth + Gsm functionality right after phone process crashes WITHOUT that fix. All this when using bluetooth equipment+screen off+other side hangs up. I never experienced that on regular calls. But u can easily check this by reverting to stock and see if the sheeps are gone ;-) imho this must be caused by another messed thing.
[Galaxy S I9000 Android Development] manudevil:
I guess you're right. It is hard to track the bug. Anyway, the fix is working well. No FC, that is good.

I still have black screen of death sometimes, forcing to hard reboot, but there are so many possible parameters...
[Galaxy S I9000 Android Development] $omator:
i always forgot to connect phone to pc and do abd bugreport > c:/bug.txt

when it happens - its a rare but it indeed happens even with Phone FC Fix
[Galaxy S I9000 Android Development] fallenfuzz:
Any issues with new JVS 2.3.5?
[Galaxy S I9000 Android Development] flo2lacanau:
phone.apk FC bug is still in JVS.

Thanks to make a "[MOD] Phone.apk process FC (Force Close) fix for JVS" !!

Please ...:(
[Galaxy S I9000 Android Development] no.one.writeme:
Hi,

Look here.

Best regards.
[Galaxy S I9000 Android Development] bushgegner:
Thx for posting! Will test and report on JVR Jetpack3.1 ROM.
[Galaxy S I9000 Android Development] Tagtag123:
Sorry if this has already been answered,

can anybody tell me what can i do to eliminate FC on XXJVQ stock+CF-Root?

FC happens when the other side hangs up!

---------- Post added at 12:25 PM ---------- Previous post was at 12:21 PM ----------

Hey buddy can you or anybody else post a file which will work on XXJVQ + Cf-kernel i.e with those .odex files deleted?

Thanks in advance!

---------- Post added at 12:34 PM ---------- Previous post was at 12:25 PM ----------

okay i could open both the .apk files with winrar, now the files to delete for this to work on XXJVQ odexed are the classes.dex in both the apks?

---------- Post added at 12:45 PM ---------- Previous post was at 12:34 PM ----------

okay i guess i have to delete phone.odex and dialleractivitytab.odex from the phone with root explorer and then use the zip along with CWM to get this working on Stock JVQ!!

sorry for the mess i made!
[Galaxy S I9000 Android Development] anas_xrt:
I am using XXJVS (2.3.5) with [KERNEL] Semaphore JVS 1.7.0 (1.7.0bm) (CF-Root + Voodoo Sound v10 + OC/UV + BLN) and fix the problem of Phone.apk FC by using this MOD fix, Working Great..

Refer KERNEL from http://xdaforums.com/showthread.php?t=1112908
[Galaxy S I9000 Android Development] $omator:
and who cares on what kernel it is used
[Galaxy S I9000 Android Development] beat.kitano:
Custom Rom deoxed, based on firmware JVR. Kernel: Talon Dev #0.4.4.22.

I had the force close of the process com.android.phone. Today i have installed the fix. And now i have a new issue: when the phone has been out of use for a few hours, when i try to to push the "on/off" button or the menu button, the screen will not activate, it just stays black.

Before i have never had this issue. Can you help me?
[Galaxy S I9000 Android Development] kuka:
How can I install this phone fix? I've got the same problem. I've put the Phone.apk and Phone.odex in \system\app with Droid Explorer but after I have restarted the phone the problem is there still again. Is there a tutorial to fix the problem? Please help me.
[Galaxy S I9000 Android Development] marbed40:
You should instal this fix with CWM mode. It is not automatic fix by its own existence in file system.
[Galaxy S I9000 Android Development] gsw5700:
Will youth be creating a fix for JVT?

Thx

Sent using TCP/IP
[Galaxy S I9000 Android Development] andip71:
You can try this...

Hi,

for me, the fix I posted in the following thread was working on stock JVT odex.

http://xdaforums.com/showpost.php?p=18233030&postcount=83

Maybe you dare to give it a try...

Cheers

Andi
[Galaxy S I9000 Android Development] gsw5700:
Thx dude, applied the fix and its looking good, appreciate your help

Sent using TCP/IP
[Galaxy S I9000 Android Development] andip71:
Glad to know it's not only working for me :)
[Galaxy S I9000 Android Development] wittanny:
Hey AndiP,

I'm on stock JVT odexed. Do I need to delete anything first or just flash your fix?
[Galaxy S I9000 Android Development] Masoud.ebi:
Hi

Need this files for 2.3.5 xxjvt Deodexed .

thx
[Galaxy S I9000 Android Development] milets:
anybody got fix for jvu. fix from this http://xdaforums.com/showthread.php?t=1236500 is not working, it worked about 2 days after that its got even worse with fc.
[Galaxy S I9000 Android Development] geo2002:
I have the stock xxjvq with semaphore kernel and ive deleted the two files (dialer and phone apk) and put the new ones in place.Now the problem is that on the dialing screen when its dialing a number it apears VOICEMAIL NUMBER "DAN" .Normaly it must say DIALING "DAN".

Anyone faced this problem? What is the solution ?I did something wrong ?

Please help
[Galaxy S I9000 Android Development] ruh01:
jvq stock deodexed files

You can equally try these files extracted from stock deodexed JVQ version. I don't know how to build an .apk but here you have phone.apk and dialertabacivity.apk to replace the old ones in system/app.

good luck
[Galaxy S I9000 Android Development] squashfanatic:
Thank you so much for this, the fc after bluetooth call was driving me mad.
[Galaxy S I9000 Android Development] $omator:
those files are extracted from 2.3.3 and you use them on 2.3.4 =)
[Galaxy S I9000 Android Development] fallenfuzz:
That is obviously, at least we don't have phone fc with those files :)
[Galaxy S I9000 Android Development] $omator:
if flashing 2.3.3 file fixes your problem that means youve got 2.3.3 leftovers in system
[Galaxy S I9000 Android Development] KMino:
The leftovers are?

They would have to be user created files the non-wipe didn't replace or couldn't replace that aren't on /system (scripts etc sitting in a directory somewhere else, that get exec automatically). In theory all system files and assoc config files should be replaced.

Only asking questions. As then ROM creators can then delete these old files that are causing problems, when a non-wipe is performed. I am presuming config files, not on /system are being used by the system and are not being automatically created on the apps first run, as they already exist (so are used).
[Galaxy S I9000 Android Development] ruh01:
2.3.4

@somator

i guarantee that the files I posted are extracted from stock deodexed jvq posted by ramad, so no harm using them. have a nice day
[Galaxy S I9000 Android Development] fallenfuzz:
How do you know? did you compare hash,size? did you check with JVP or JVH?

Thanks
[Galaxy S I9000 Android Development] ukdtweak:
I have Never installed a 2.3.3 rom, went from 2.2.1 JS8 straight to 2.3.4 JVP via ODin, then flashed Ramads Deodexed ROM, so if there are any 2.3.3 file in my system, they came with JVP.
[Galaxy S I9000 Android Development] ruh01:
2.3.4

@fallenfuzz

I took ramad's deodexed stock 2.3.4 jvq rom from the specific thread, opened it, inside you will find system/app folder. there are all system files in specific rom, in this case 2.3.4 jvq.

So these files are inside stock deodexed 2.3.4 jvq rom. If samsung decided to keep these 2 files from jvp, it wold be stupid from them. of course they changed it to new jvq core.
[Galaxy S I9000 Android Development] $omator:
but those files are not always deleted

concentrate on understanding what i will post now:

it does not matter if you extracted it from ramadsfiles or samfirmware files

if there are some core files left in your system partition or others you will end up with fcs, not working bt, drains - not always wipe and factory reset codes are workin properly on gb thats all

so those are js8 leftovers jessus christ, phone was failing because it was js8 and you copied over proper - jvp one - clear now ?
[Galaxy S I9000 Android Development] squashfanatic:
I had fc's, I know how to flash without leaving old files, I have never had a problem before, many people have this problem, this guy fixed the problem and I thank him, if you do not have this problen why are you on this thread? Jog on, you are becoming a bore, but I think you have been told this on many other threads.
[Galaxy S I9000 Android Development] $omator:
if you had force closes of phone apk or any other you do not know how to flash =)

i was so hippe like you untill i had same issues back in the days when first 2.3.3 leaked

but i did not stoped and said o jezz what a crappy firmware but investigated the issue as far as i was capable

and i came wit a conclusion that its me that is wrong, that ive made a mistake - and oh i was correct

this humility lesson back then results in no problems with new firmwares

imagine that youre trying to cover an ugly scratch on your new car with some spit and a bit of sleeve polish it will not work for long =)

why i am in this thread? it made me curious and i am explaining you all why it might work in some cases

also maybe it will open eyes of few users hopefully
[Galaxy S I9000 Android Development] criscan:
Hy Friends, This is the non increasing ring tone version of the phone fix.

Its working nice for me on JVQ.

Take your feedback

phone fix_NoIncRT.zip (2.35 MB)

http://www.multiupload.com/S11JYCGMPF
[Galaxy S I9000 Android Development] cooldoc007:
does it work with jvp/jvh?
[Galaxy S I9000 Android Development] criscan:
It's the same file of the first post, i just remove increasing ring tone.

The file is for deodexed rom, but its easy to make works on odexed too. You can remove phone.odex using Root Explorer, then flash the zip.
[Galaxy S I9000 Android Development] fallenfuzz:
So what was the mistake you did?

Because not matter how, when I flash I had phone FC, even after investigating, logs, adb and many more, I even format my SD and flashed with odin, and still had phone FC.
[Galaxy S I9000 Android Development] fallenfuzz:
Guys, let me know on which ROMs that fixed worked for you so I'll update OP.
[Galaxy S I9000 Android Development] mNiosu:
Nice one Doc. ;)) ! Thanks mate! Works like a charm!
[Galaxy S I9000 Android Development] fallenfuzz:
What ROM are you on?
[Galaxy S I9000 Android Development] weileong:
on CF kernel with 2.3.4 JVQ , after flash with cww..Still not working...i had bluetooth call after call disconnected still show the msg :(
[Galaxy S I9000 Android Development] fallenfuzz:
is it odexed or deodexed?

it doesn't work on odexed as far as I know?
[Galaxy S I9000 Android Development] alexkno:
tried it yesterday on ficeto's deodexed JVQ with DC2.9, after flashing and boot I got an FC of a 'message process' and was not asked for my PIN anymore, thus couldn't use my phone as phone, so needed to restore
[Galaxy S I9000 Android Development] criscan:
There's no reason to flash this fix on Custom Roms. If flashed on Stock Rom you might deodex only the phone app, deleting phone.odex before flashing. As I said It's running perfect on stock JVQ.

It's necessary check it out on JVP.

criscan -from my I9000 XDA Premium app
[Galaxy S I9000 Android Development] fallenfuzz:
Works flawlessly for me with Deodexed Ficeto's JVQ.

I installed stock JVQ from samfirmware, tested a call, got FC, flashed Ficeto's JVQ deodexed, applied the fix and works great, no errors, nothing.
[Galaxy S I9000 Android Development] shumilica:
It seems to work on a stock JVQ odexed version with CF-Root (previous to install I deleted the .odex files of DialerTabActivity and phone app). I tested just once, called somebody, let the screen go off and then let the one that I called to hang-up. No FC anymore.

Hope it lasts because this was my only problem with JVQ!

Thanks!
[Galaxy S I9000 Android Development] weileong:
aiks...think mine is odexed rom..with CF root..how to reverse back to stock phone.apk ?
[Galaxy S I9000 Android Development] fallenfuzz:
just delete the odex files and see it it helps
[Galaxy S I9000 Android Development] husq510:
i have JVQ stock rom, and phone force close, I tried to install this apk but signature fails. Any help ?
[Galaxy S I9000 Android Development] flo2lacanau:
test on JVQ Deodexed

I still can use my phone ... i'll see if i still have FC later ...
[Galaxy S I9000 Android Development] ukdtweak:
Actually, I flashed Stock JVP over JS8 via Odin, format and re partition, even wiped my SD card, did not restore any apps or data with titanium, so don't see how there could have been any JS8 files left on the system?

How can we check?
[Galaxy S I9000 Android Development] dipenv:
Stock Rom JVQ, Odexed + CF Root = Worked.. However..

Okay.. So it worked. (BIG THANKS). Have been using it for more than 15 Hrs now. Made Numerous calls using BT and no force closes. I deleted the phone.odex and dialeractivity.odex files using Root Explorer before flashing. Then I flashed this using CWM.

However.. I think I lost my Edge connectivity. It might be completely unrelated also. However I checked with my Same Network Buddies here and his Internet is okay. All APN settings are fine but still no Edge for me. Any thoughts ?
[Galaxy S I9000 Android Development] bazsoczi:
Hi, sorry for the noob question,but how should I install this?

I'm on stock JVP, rooted, ext4. What files should I remove?

Thanks,

Balazs
[Galaxy S I9000 Android Development] fallenfuzz:
just flash if from recovery with "install zip from sdcard"
[Galaxy S I9000 Android Development] heeheehee:
thank you for your really great sharing!!
[Galaxy S I9000 Android Development] Imaginati0n:
I made the update and the fc are rare but still some lag and I had two or three fc and had to restart the phone. Apk didn't restarted alone. I want to put again the stock apk. I also have a cdma message while disconecting a call and my phone is from europe.

Anyone can upload the update with the stock from JVQ european version?
[Galaxy S I9000 Android Development] Birba:
This fix works perfectly on S.U.R.F.A.C.E v2.1. Thanks for that

I also tried to flash back to froyo stock, and then again to gingerbread stock to have a clean flash. But without this fix the phone.apk crashes!

But why do some have this issue and other don't have it?

I also tried a different BT headset, without success.

Maybe the logcat output below helps some dev to find where the problem comes from.

The phone.apk crashes only if the screen turns off during the call.

http://pastebin.com/RZHK7H1n
[Galaxy S I9000 Android Development] $omator:
ive heard that my phone files works ok as long you do not touch them =)

look for them at my signature
[Galaxy S I9000 Android Development] Donald Nice:
Still no working solution for odexed JVQ?
[Galaxy S I9000 Android Development] turbare:
Aren't Ramad's stock rom's deodexed? If so, I've been running the fix for one or two weeks now and I've had no more FC's.
[Galaxy S I9000 Android Development] Donald Nice:
Yes Ramads are deodexed.. but im using the stock-jvq, because of the browser problems of the deodexed one.

But i hate the fcs of phone.apk.. Its the only issue i have with JVQ, so a solution for the odexed firmware would be great!
[Galaxy S I9000 Android Development] bahadir_bado:
i flashed deodexed ramads rom JVQ , and rooted it , make factory reset and clear caches.

then i installed this patch and no problem for 2 weeks , but as you said deodexed browser sucks...

i speak 2 hours in a day and it is stable. thanx.
[Galaxy S I9000 Android Development] ghosty7:
There is definitely a problem with JVQ phone files even yours. However it is also phone related as well. I have spent many hours testing and have found the following results using an I9000 and an I9000T.

On the I9000T the only time i do not get FC is when using the files from 2.3.3(the fix in this thread)

On the i9000 i do not get FC no matter what files i use.

Also, it is not easy to repeat the testing, you must be connected to bluetooth handsfree and turn off screen and the other side must hang up.

This is not a flashing issue(i am sure there is a little of that in some cases) there is definately something in the JVQ files that is causing it in combination with some phones. If it was not for the fix on this thread my I9000T would be still on Froyo.
[Galaxy S I9000 Android Development] Donald Nice:
@all with this problem and odexed firmware:

This fix works also for odexed firmwares!! Like the other posters said before, you only have to delete the system/app/Phone.odex and system/app/DialerTabActivity.odex before installing the mod.

Works great, self tested!
[Galaxy S I9000 Android Development] $omator:
maybe you should update your initial post with info?
[Galaxy S I9000 Android Development] fallenfuzz:
wasn't around for some time, OP updated
[Galaxy S I9000 Android Development] komoornik:
Not true.

10 characters
[Galaxy S I9000 Android Development] $omator:
well they aparently work for over 300 people that have downloaded them because ive heard no complain
[Galaxy S I9000 Android Development] komoornik:
Sorry to disappoint you - probably most of them end call first.

8/10 tests i get fc .

Installed non inc version based on one from the first post - working flawlessly.
[Galaxy S I9000 Android Development] $omator:
ffs i end call first i used bt i tryed everything

try to understand the words that i will write now

first post phone apk is from 2.3.3 mine is from 2.3.4 - following?

you claim to have jvq yes? and you have fc with my 2.3.4 based phone apk?

but no problems with phone apk attached to first post that is pure 2.3.3?

you still does not see a patern here?
[Galaxy S I9000 Android Development] squashfanatic:
$omator,

Let me explain this easy for you.

I had JVP and fc after BT call when other party hangs up first,

I move to JVQ and same problem, easy to understand so far?

I and many others report this problem, have we all suddenly become incapable of flashing correctly? Still with me?

I do a complete wipe and check using a military wipe tool - I work for a company that sells FIPS standard usb drives - and reflash JVQ, and believe me it is not so hard, a child could do it and that may very well include you.

I get same FC.

This guy posts a fix and IT WORKS! Ok so far?

So really I don't give a sh1t where the files came from, I don't care if he dreamt them up in a drug induced haze or if he found them on his old Atari, bottom line, they work.

Are you getting the picture $omator? Is this too hard for you? I have tried to make it very simple.

So really mate learn to accept some things and just STFU sometimes.
[Galaxy S I9000 Android Development] $omator:
:]]]]]]]]]] lulz

anyways it is the same as with android os drain bug, does not exists for me
[Galaxy S I9000 Android Development] squashfanatic:
No I dont get that drain either. Yes, after we test memory cards and usb drives we have to make sure that no files are left AND that none can be recovered by any recovery software
[Galaxy S I9000 Android Development] $omator:
well there is something wrong with your copy

maybe use samfirmware.com files like i always do (if you do not)

i would really want to help as i like to get to the bottom of such issues

maybe that is deodexing maybe the kernel you use or the theme/rom hard to bugtrace as i can not reproduce such behaviour :(
[Galaxy S I9000 Android Development] fallenfuzz:
I tried JVQ from samfirmware and had same phone.apk FC
[Galaxy S I9000 Android Development] $omator:
and tryed 'my way'

-install 3 file froyo

-do not root there do a factory reset all wipes out there from cwm menu there

-then install jvq

-do not root there do a factory reset all wipes out there from cwm menu there

?
[Galaxy S I9000 Android Development] Fekke:
Thanks for this fix. Using it over Darky 10.2. Now i wonder, could it be themed without getting fc?
[Galaxy S I9000 Android Development] $omator:
yeeeeeeehaaaa ive got the phone fc :))))

fun part is that it affects only portrait mode, no fc at landscape