yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] Rolandas3:
Hi, Ramad

would be nice to see dates when those FW were uploaded to site. Would be good for such dummies like me, which comes here once a month to see latest updates

Cheers

Rolandas
[Galaxy S I9000 Android Development] [Ramad]:
XXJVQ CWM and Odin packages are up.

That is a bit out of the topic of this thread, I think that this subject has been covered on General Section on the I9000 Forum. :)

Will try to do that as soon as possible. :)

Sorry for making you wait but I was testing the deodexed firmware before releasing it, I don't post a link before that I'm sure that it works as it should. :)
[Galaxy S I9000 Android Development] jaiiscool:
Wow!

that was lightning quick!
[Galaxy S I9000 Android Development] jaiiscool:
Deleted!
[Galaxy S I9000 Android Development] Rootax:
Hello Ramad.

I read on the jvq topic that smali need to be updated to have stable and quick deodexed roms.

Can you elaborate on that please ?
[Galaxy S I9000 Android Development] cenonmin:
Sorry for noob question...

If I flash JVQ w/ Odin I will not have CWM and stock 3e recovery right, so how can them get both back?

Thank you.
[Galaxy S I9000 Android Development] Cy4n1d3:
You have to flash a modified kernel with cwm recovery :)
[Galaxy S I9000 Android Development] cenonmin:
Oh I get it now, DOH :o

Have to wait then or try the JVQ ones ;)
[Galaxy S I9000 Android Development] webwude:
Are there any deodexed related problems with JVQ? I have read, that there are some issues with the browser?
[Galaxy S I9000 Android Development] mohanindia:
Yes...browser issues confirmed... i have switched to Opera for time being..

waiting for a fix..
[Galaxy S I9000 Android Development] electrotune1200:
Sweet....

I just popped over here to ask about this.. Flashed stock JVQ and flashed straight to the deodexed firmware....

Browser is painfully slow on scroll.
[Galaxy S I9000 Android Development] [Ramad]:
Yes, there is a problem with the browser which is not smooth at all, everything else works as it should but not the browser.

I have repeated the process yesterday using several methods and tools to see if it was related to other apk or jar files but it seems that it's only Browser.apk that does not work well. I will look into it again today and see if I can do anything about it. If you want to use JVQ then please install Dolphin HD or another browser.

I don't know if updating smali will solve the browser problem, smali needs to be updated when jar/apk files can't be deodexed, but in this case the apk file can be deodexed and it works but does not work well.
[Galaxy S I9000 Android Development] Rootax:
Ok thx for the explanations, and good luck with that. I hope you will find a solution :)
[Galaxy S I9000 Android Development] paarry:
This is great. i was thinking how to flash the stock XXJVQ as it was not de-odexed. u are really gr8 man. kep up d good work

:d:d:d:d:d:d:d:d:d:d
[Galaxy S I9000 Android Development] Lancey:
Is there stock AOSP Lockscreen for JVQ?
[Galaxy S I9000 Android Development] Gvdn:
Thx once again Ramad.

Just wondering if there is any way to donate to you?
[Galaxy S I9000 Android Development] gajahwhite:
wondering why sometimes i face FC after make a phone call? if not mistaken it mention there android.phone bla bla.. didn't remember..

it happen to me since i use JVP.. and today after flash to JVQ.. also face FC after phone call.. not always.. but sometimes only.. :)

wanna know if there got any method to fix it..
[Galaxy S I9000 Android Development] wiedroid:
Do you use Mod Dialer.apk ?

If yes, probably because of that.

I dont have anyproblem using Ramad JVP Deodexed.
[Galaxy S I9000 Android Development] gajahwhite:
nope.. i'm using the stock one..

maybe i can fix this by reinstall the dialer?
[Galaxy S I9000 Android Development] ken2291:
sometimes will be like tat. it's JVP's prob
[Galaxy S I9000 Android Development] poker_X:
can someone please post the stock kernel (TAR) for JVQ? I want to root with cf-root and then go back to stock.

thank you!
[Galaxy S I9000 Android Development] titooo7:
Its in he first page mate

Enviado desde mi GT-I9000 usando Tapatalk
[Galaxy S I9000 Android Development] cenonmin:
Hi all,

I wanna try JVQ, anyone found a solution to the browser issue yet?

I don't want to use a 3rd party browser so are there other stock or hacked stock browsers we can use?

Thx
[Galaxy S I9000 Android Development] mohanindia:
no update so far... i went back to stock and flashed CF kernel... all is well.. will wait more for a deodexed rom
[Galaxy S I9000 Android Development] cenonmin:
I might try this one http://xdaforums.com/showthread.php?t=980111&highlight=hacked+browser ;)
[Galaxy S I9000 Android Development] pikachu01:
Not even Opera Mini/Mobile?

They just updated their browsers with some nifty features. Might try to take another look :)

Smoother than stock browser.
[Galaxy S I9000 Android Development] wiedroid:
Have you try get the browser from stock JVQ, then flash XXJVQ Deodexed and then replace the browser from the stock ?
[Galaxy S I9000 Android Development] rtoussaint:
Except for the browser, this rom is pretty sweet! I missed CWM, so tried the speedmod kernel. It was too dark on automatic brightness for me, so installed Darkcore kernel for JVQ. After lagfixing it is flying! I hope the browser can be fixed somehow, otherwise you'll have to switch to a 3rd party browser :(
[Galaxy S I9000 Android Development] flo2lacanau:
no ... no bug for me ...
[Galaxy S I9000 Android Development] specialex:
does it works for you?
[Galaxy S I9000 Android Development] [Ramad]:
Just an update regarding the browser issue:

Still no luck, as soon as the browser application is deodexed then it will behave differently (bad response), it does not matter if I de-odex it with or without compression, with or without optimization, it will work but not as in the stock firmware.

You are welcome. :)

No need for donations, it's all a part of sharing :)

If you feel that you want to donate anyway then make it to Heimdall project by Benjamin Dobell which I think will be good for all Samsung devices.

And

Please try to flash the CWM package of JVP or JVQ, use the firmware as it is with the stock Kernel without restoring applications, settings or installing themes and modified apk files.

Try to use it for 3 days and let me know if you still have issues, I'm almost sure that you will not have any issue because that I'm suspecting some Kernels or modified apk files to be behind these issues.
[Galaxy S I9000 Android Development] [Ramad]:
Not so long ago, Norton did remove Windows system files by thinking that these files were viruses, so I would not trust Norton AV...search the internet for that and you will see.

However here is an example:

Link of scanning ZSJPG_WiFi_TGY.exe:http://virusscan.jotti.org/en/scanresult/8083bb2d0c0c1e2217e10851e2e9fabb53ad7ba1
[Galaxy S I9000 Android Development] tsinc:
It's not a virus, really. WS.Reputation.1 means that Norton thinks it's a virus because of its reputation (which is none)! It's just a very NEW executable file for Norton and its community.
[Galaxy S I9000 Android Development] [Ramad]:
I'm half way on a guide that will show how to deodex and build a ROM for CWM, I will post it as soon as I have time to finish it.

Edit:Are you getting errors while flashing, if so then what is the error ? or while deodexing, I might be able to help now if it's not a complicated matter.
[Galaxy S I9000 Android Development] Tricky103:
Thanks for the reply..

I have an error after flashing a custom ZSJPG.

The com.process.media forces close, I have tried many things to fix it.. I also get an error if I click WIFI, ( I was going to install the JPA drivers )
[Galaxy S I9000 Android Development] [Ramad]:
It sounds like permissions issue in the update-script, here is what I use:

Also if the CSC that is being installed is TGY then there is a configuration file that you can find at CSC/system/etc, it should be added to /system/etc only when the CSC that is installed is TGY.

Edit: Another thing, did you use xUltimate to deodex and optimize?
[Galaxy S I9000 Android Development] Tricky103:
Thank you very much.

I will try :) You saved me another headache this evening
[Galaxy S I9000 Android Development] [Ramad]:
You are welcome, however I did edit the post and asked if you have deodexed and optimized using xUltimate..if so then you need to do deodex again using xUltimate but without optimizing, optimizing the apks using xUltimate does also give a lot of force closing, I hope that you can read this post some time later and good luck on your work. :)
[Galaxy S I9000 Android Development] Tricky103:
Yes I used xUltimate to deodex and optimise the apk's and framework
[Galaxy S I9000 Android Development] [Ramad]:
I'm sorry my friend but you have deodex again, the optimized apks will not work. I'm sure that you will have it working this time without any issues.
[Galaxy S I9000 Android Development] Tricky103:
I have also flashed just with deoxed and no optmization, that hasn't worked for me.. So next will be looking at the updater-script, I had added the apk's from the TGI/system/app, but not added the etc file.

Thank you again :) Looks like I know what I will be doing this evening :)

edit: Sorry for Hijacking your thread also :) But it was worth it :D
[Galaxy S I9000 Android Development] [Ramad]:
I think that you are missing some files, when xUltimate finishes then only the files paired with .odex extension files are moved to done_app and done_frame, which means that the files with out .odex are left at origi_app and origi_frame.

I did explain what do with that earlier in post #43 in this thread here: http://xdaforums.com/showthread.php?t=948790&page=5 step 8 to step 11 is what you need.

It's all about deodexing then it's related to the thread ;), and I hope that other members can benefit of our posts..:)
[Galaxy S I9000 Android Development] Tricky103:
I am sure they will Ramad, I will let you know how I get on :)
[Galaxy S I9000 Android Development] [Ramad]:
The Armani font CWM package have been added.
[Galaxy S I9000 Android Development] g00ndu:
Can you deodex GB?

I believe you can't. Probably baksmali and smali need to be updated to GB version.
[Galaxy S I9000 Android Development] [Ramad]:
It's done, now testing the ROM.

I might not make a stock ROM out of it, it does not seem to be worth it...beside that, it's still only a beta. But I might post the deodexed app and framework files.
[Galaxy S I9000 Android Development] hatori:
Nice job. Waiting for JV1
[Galaxy S I9000 Android Development] [Ramad]:
XWJS7 has been added.
[Galaxy S I9000 Android Development] sonyz7:
Great, thank You Ramad! :cool:
[Galaxy S I9000 Android Development] jornbjorn:
thanx! nice job! just what i was looking for, and also the new js7! quick!
[Galaxy S I9000 Android Development] tsinc:
Thanks for everything Ramad! (fast, helping everybody, no "donate to me")
[Galaxy S I9000 Android Development] mohanindia:
The stock browser has undergone changes with this version...so i dont want to revert back to an older version. Hopefully when the build is released by samsung later...Ramad will be able to help us out
[Galaxy S I9000 Android Development] $omator:
it is not the browser apk fault my guess

modifications of android.policy & framework out of your deodexed files (well SystemUI also but dubt that problem is there)

and browser in odex became laggy =)
[Galaxy S I9000 Android Development] malcho:
Don't worry ithink it's problem with bad flashing.Anyway i will try what you told me and let you know..

Thanks for support
[Galaxy S I9000 Android Development] Bo$s:
Please check if browser bug isn't caused by wrong permisions ($omator's update.zip's fixing all permission, like deodexed rom's packages) , maybe something changed in JVQ?
[Galaxy S I9000 Android Development] [Ramad]:
I will do what I can, but I may or may not be able to figure this out, it could be that some files are left behind or deleted when deodexing or we might need smali updated...etc.

I was suspecting the browser application for the issue but it's not, I got the deodexed browser application working perfectly on the stock firmware.

I think now that it might be one of the jar files, well, we will find out soon.
[Galaxy S I9000 Android Development] $omator:
realy appreciate man
[Galaxy S I9000 Android Development] specialex:
I thought the problem is only on framework.jar

because when i modify it, the browser became laggy

modifying android.policy, systemui and framework-res is fine
[Galaxy S I9000 Android Development] Cy4n1d3:
Keep up the great work Ramad, I'm using Dolphin for the time being :)

Thanks alot!
[Galaxy S I9000 Android Development] [Ramad]:
I have to agree here, I have tested SystemUI this morning and there was nothing wrong with it.

I'm down to framework.jar and core.jar but leaning more toward framework.jar, something goes wrong when the odex file is extracted and converted.

Unfortunately, we don't have/know other tools than the known baksmali and smali to do the de-odexeing tasks, all we can do is wait for the author of the tools to look at it and see where it goes wrong.

Well it comes down to this, if you need to use the stock browser then flashing to the stock firmware is the only way, I can't see another way until our good and working tools get better on handling the files.
[Galaxy S I9000 Android Development] Cy4n1d3:
No one to blame here, except for the browser the JVQ version delivers a very good experience for me ;)
[Galaxy S I9000 Android Development] [Ramad]:
A little update regarding browser issue:

I have deodexed and build classes of all framework files manually(one by one) 2 times yesterday while leaving the jar compressing as it is, still no luck.

I agree but I don't think the browser application itself is behind the improvements, this is why it does not function correctly when framework files are touched.

As much as I hate this, at the same time I became a good friend with the new Opera mini browser, even if we manage to fix the browser issue, I don't think that I'm going to use the stock browser or Dolphin again. The new Opera mini is very smooth and responsive, it also uses only half of the resources of what the stock browser does.
[Galaxy S I9000 Android Development] Bo$s:
[Ramad], maybe you should report baksmali issue to smali/baksmali author? http://code.google.com/p/smali/issues/list
[Galaxy S I9000 Android Development] betoNL:
It took me just a while to get used with Dolphin HD and Dolphin Mini (even better) and what a difference !

The stock browser always have been problematic...

I said bye-bye to the stock browser and stock launcher (TW) ages ago...

They are just not well written

Any other browser and launcher I tried, are way smoother than these stock ones..
[Galaxy S I9000 Android Development] SamHaLeKe:
Hi Ramad!

Have you seen this http://www.xda-developers.com/android/fix-for-deodexed-browser-on-the-sgs2/

Perhaps you can ask pulser_g2 how he fixed the deodexed browser in SGS2 and try that on deodexed JVQ Browser

If the above was all that, please ignore this post :D
[Galaxy S I9000 Android Development] Gvdn:
Ramad just wanted to let u know i used your deodexed version and had the browser problem but i alos had gps locking very hard and loosing lock alot. Was unusable. Running your stock version atm with only cf root and everything works flawless atm.
[Galaxy S I9000 Android Development] [Ramad]:
I did try to set dalvik heap size all the way down to 32M on the very first GB that have been leaked, the device worked fine with only 32M but I did set it to 48M in all the firmwares to be on the safe side, also because this is what Samsung used to set it to on Froyo firmwares.

You can try to set it to 64M and try it, find out what is best for you.

Thanks, I thought about it too when I was reading on his page to find out if I'm missing something, I will contact him for sure if we are unable to fix here at XDA.

Used Opera Mini once before, was not good at all, didn't use my phone as a phone for a long time now, I don't remember a day where I did not flash it at least 1 time because of a new firmware or a new experiment. :)

Thanks for the link and the info., will contact him for sure. :)

Do you live in Europe? I always edit gps.conf and change it to fit the region the firmware is released to, JVQ is a European firmware so I have changed the pool.ntp to Europe instead of North-America, let me know, this is easy to fix.

Beside that, you need to update to the latest Maps if you haven't yet, if this does not help then try to flash again but staying with the stock Kernel and find out if you still have the problem.

Just to let you know, my device needs only a few seconds to get signal, the very first use takes a bit longer of course.
[Galaxy S I9000 Android Development] Cy4n1d3:
Ah, was already wondering why it was already correct before even firing up fasterfix ;)
[Galaxy S I9000 Android Development] $omator:
i stoped editing gps.conf and see no difference with ttff (time to first fix) time as when i set it to polish ntp server...
[Galaxy S I9000 Android Development] War Report:
hi Ramad,having problems with wifi on jvq.its not connecting..

ok sorry,its working again..
[Galaxy S I9000 Android Development] pulser_g2:
Regarding browser performance after deodexing, we found an older SGS2 browser app worked fine.

But that'st not a good solution, but I compared the old and new browsers, and removed references to something like WebViewSurface3D in the code.

I ended up swapping 2 smali files for the older versions to get it to work, but I can't find which 2 files it was right now :(
[Galaxy S I9000 Android Development] [Ramad]:
Hi and thanks for your post, glad that you have time to help :)

I'm thinking that you are referring to BitmapWebViewSurface3D in the 'out' folder files, these are 10 files on the browser folder. These files should give the browser 3D effects when changing from portrait to landscape and when opening/closing tabs, removing references to these files will disable these futures, I'm I correct here?

I would like to ask if the deodexed browser worked as it should on an odexed SGS II firmware, I'm asking because it appears that the browser itself works fine, meaning that it works fine when deodexed on an odexed firmware, I have tried it to find out if deodexing the browser was what went wrong but that was not the case, so maybe we are looking on 2 different problems here, I'm asking because your input is valuable here.

Thanks again for your help and your time, it's very much appreciated. :)
[Galaxy S I9000 Android Development] SamHaLeKe:
True

, deodexed JVQ browser works

fine

on odexed ROM, it's

only

when you deodex framework.jar where all the troubles begin (f.e. browser lagging and who knows what else)

so when theme makers change framework.jar (f.e. add overglow and extended powermenu code), they have to deodex it first (and odex it later for odexed ROM) with there tools, right? The same counts for people that make a clean deodexed ROM, as framework.jar will also be deodexed, so issues arise (f.e. the confirmed browser lag).
[Galaxy S I9000 Android Development] [Ramad]:
An update about the browser issue and a temporary fix

An update about the browser issue and a temporary fix:

I managed to get the browser working on a deodexed JVQ.

Here is a temporary fix until we find how to fix the browser issue without the need for any odex files. You need to be on fully a stock firmware(non stock kernel is OK), means no modded apk files or framework files, because I have only tested it on a stock firmware, but if your firmware is modded and you don't mind re-flashing if it goes wrong

then use at your own risk, making a CWM backup is a good idea on moded firmwares

, you can copy the files using CWM or manually, choose what works best for you:

This is for developers and experienced users:

It's not that simple as it appears that 4 odex files must be on /system/framework in order to get the browser running as it should, these 4 files are:

bouncycastle.odex

core.odex

ext.odex

framework.odex

Remove one of these files and the circle collapses and the browser lags as you know.

I don't know if it's because the browser is programmed to look for the odex/classes files on /system/framework, if that is the case then it might be possible to change some lines in the browser classes files or the apk file itself.

Just wanted to share that with you before going to sleep, I have been up whole night trying to find a connection, this is what I found so far.
[Galaxy S I9000 Android Development] cwc289:
Just applied the method and now the browser is working as it should!
[Galaxy S I9000 Android Development] Sebm0r:
The temp fix works for me too! :) thanks
[Galaxy S I9000 Android Development] War Report:
after flashed the fix,now i got bootloops..
[Galaxy S I9000 Android Development] lj-_-:
It works but when trying to install crysis sensation theme it boot loops.
[Galaxy S I9000 Android Development] cwc289:
Don't flash the browser fix if you applied other custom theme before.
[Galaxy S I9000 Android Development] [Ramad]:
And

Please read:

I have now added that making a CWM backup is a good idea if your firmware is modded.

You are correct sir :) This is very much for deodexed unmodified stock XXJVQ.
[Galaxy S I9000 Android Development] mariotme:
so if we apply a theme after the fix i guess the them would break the browser again am i right? :D
[Galaxy S I9000 Android Development] sebarkh:
Ramad, you are truly amazing. I'm also thinking about the browser issue all the time. It made me swap to cyanogen for the time being... Sounds stupid, but this issue is annoying... even though I rarely use the stock browser

Sent no matter where from. Concentrate on the topic...
[Galaxy S I9000 Android Development] [Ramad]:
I think so.

Thanks, I don't think that I will be using more time on the browser issue, I used too much time on it, I think that I will leave the rest for our bright minds here at XDA.

Cyanogen is good, the only minus is that it uses more power than stock firmware, otherwise it is a special firmware.
[Galaxy S I9000 Android Development] squashfanatic:
For me the phone is perfect until I step into the car, the bluetooth seems to cause the android phone f c, but only when the other party hangs up first. I tried 4 times today, three times I cut the call short, no fc, last call I waited and let them hang up first - fc
[Galaxy S I9000 Android Development] [Ramad]:
Are you using the stock Kernel or another Kernel?
[Galaxy S I9000 Android Development] squashfanatic:
Speedmod, I guess I could return to the original and test
[Galaxy S I9000 Android Development] sebarkh:
They managed to improve the battery life, I suppose.

Beside, does it matter if I need to recharge every six hours (cm7) or every 9 hrs (stock)? It's still everyday duty of i9000 users :)
[Galaxy S I9000 Android Development] :
Is it really 3 hours difference in battery life? :eek: To me it matters much if i can use it 3h longer.
[Galaxy S I9000 Android Development] sebarkh:
no, it was just an assumption. dunno... But if done on daily basis....
[Galaxy S I9000 Android Development] habylab:
How does the browser compare to Dolphin HD 5? Wants the point of using deodex if to get the browser working you can't flash themes afterwards? Or will there be a permanent solution, hopefully.
[Galaxy S I9000 Android Development] mawardi:
Fix's working fine but after a while, it freezes my phone. So no stock browser for me. Using xScope for now.

I'm using TalonDev kernel and OCK's AOSP Gingerbread theme.