yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] Mopral:
My JM8 is untouched so I need the non-deoxed files with menu button fix

When I put your files in /system/framework , my phone seems to be stuck on first boot screen...
[Galaxy S I9000 Android Development] jodue:
just installed on JPK. works great, looks awesome, thanks a lot! ;)
[Galaxy S I9000 Android Development] torres76:
That happened to me but i realised i was still using the file for jph but i had started using jm8 so had to re-flash and download the correct odex file. It works great now.
[Galaxy S I9000 Android Development] grumly_37:
How do you do, me, I can't replace the android.policy.odex file. I tried with Root Explorer but it doesn't works.

If I delete the file, ok but the file re-appears (not the one I would like of course) :(
[Galaxy S I9000 Android Development] Project1.exe:
there's been a change in JP4/5 and JPK firmwares that current root methods don't work completely, at the least it gives us root access tho readonly on some of the folders (like /system)

to get around that, if you've already "rooted" (heh) install "Terminal Emulator" in the market and try to do this

$ su

# mount -o remount,rw /system

then try to replace the odex again
[Galaxy S I9000 Android Development] Rawat:
Just did this via PC before your post was up, adapting the method given by m1ket and others in the "The Fightspit's Circle Battery mod repository thread"

I saved the downloaded file on the internal sdcard, and backed up the original beforehand.

adb shell
su
busybox mount -o remount,rw /system
rm /system/framework/android.policy.odex
mv /sdcard/android.policy.odex /system/framework/android.policy.odex
sync
reboot
[Galaxy S I9000 Android Development] grumly_37:
Thanks a lot, now, it's working fine, great :)
[Galaxy S I9000 Android Development] jodue:
lol! sorry for being picky but thats just wrong. root works perfectly but /system is mounted READ ONLY! remount and everything works like before (till the next reboot at least)

(so now it's like on most other devices and especially htc-phones. i actually wondered about the system folder/partition being WRITEABLE when i got my phone since this provides additional security)
[Galaxy S I9000 Android Development] pinku1:
I removed android.policy.odex using terminal,

Tried to move new android.policy.odex to system, it gave error.

Phone rebooted, guess what? Its not booting!

It keeps on showing Galaxy S screen. Phone is dead!

Help me people. What to do now?
[Galaxy S I9000 Android Development] Quiksilver78:
I know it is not exactly the same but can't we just use WidgetLocker to get stock Android lock screen? works really well.
[Galaxy S I9000 Android Development] Project1.exe:
exactly my point :) there were changes on these kernels that existing update.zips which are meant to give full read/write access are only given read permissions after the scripts inside the zip executes. so perhaps if leshak(the original update.zip root provider afaik) or BackfireNL or others might provide another version of the scripts for rooting for these f/w (perhaps adding another line of code to remount /system again for rw or something) that would be great, but then again it's just an idea as i'm just a developer on a different platform :)

i do agree with you that the read only resulting from existing zips is a security advantage, unfortunately it looses the full essense of rooting
[Galaxy S I9000 Android Development] Project1.exe:
widgetlocker is an app and not something really integrated in android itself, hence it can be controlled with other apps like task killers or even dalvik itself if it chooses to on really desperate resources.

this lockscreen is built right in android, and what Samsung (and perhaps other manufacturers as well) did is to write their own parts of their customization (including the TouchWiz lockscreen) and modify the android framework sources to invoke their own implementations instead of stock ones. what we did here is the reverse for the lockscreen, calling the stock implementations hence native.
[Galaxy S I9000 Android Development] jodue:
your problem was most likely that you didn't remount the system partition readwrite...you can fix your error like this:

* boot into recovery

* connect phone over usb

* adb push android.policy.odex /tmp/

* adb shell

* su

* cp /tmp/android.policy.odex /system/framework/
[Galaxy S I9000 Android Development] jodue:
if you are that desperate for permanent write access to /system you can try this:

adb shell
su
mount -o remount rw /system
mv /system/bin/playlogos1 /system/bin/playlogos1_ORIGINAL
echo '#!/system/bin/sh' > /system/bin/playlogos1
echo '/system/xbin/busybox mount -o remount rw /system' >> /system/bin/playlogos1
echo '/system/bin/playlogos1_ORIGINAL' >> /system/bin/playlogos1
chmod +x /system/bin/playlogos1

... this replaces the boot animation script with the remount command and then plays the boot-animation ... works fine hereon stock JPK. it may cause problems with some custom roms and lag-fixes.
[Galaxy S I9000 Android Development] Project1.exe:
that's a little weird. are you using GT-i9000 international version? are you on JP8 or JPH or JPK? the phone rebooted itself after you've removed the android.policy.odex? what/where did you use to remove the file? if you didn't enable ADB like the first post mentioned, you'll unfortunately have to reflash as that's the only way you can push a file even if it's stuck on the "S" :(
[Galaxy S I9000 Android Development] jodue:
you can push files/get shell access when you are in the recovery ... so no real problem here ...

edit: see my post above for the solution to the problem (i even tried it before posting) ...
[Galaxy S I9000 Android Development] pinku1:
Sorry, but can you please tell me how to do this part:

adb push android.policy.odex /tmp/

where I have to type this ?
[Galaxy S I9000 Android Development] Project1.exe:
thanks! :) i'll surely revisit this post when I get to the annoyed level and get that rw /system access persistent. hopefully other's pick this tip too. so far i'm happy with just being able to apply this lockscreen (and also delete nv_data.bin and md5 :D)
[Galaxy S I9000 Android Development] Project1.exe:
cool! so recovery always runs adb server on the phone even if you didn't set it normally?
[Galaxy S I9000 Android Development] jodue:
from the terminal. you have to get adb before that. it's part of the android sdk and you can get it from here.

yeah its really great to have the stock lockscreen (back) :) ... thanks for that!
[Galaxy S I9000 Android Development] jodue:
exactly ;)
[Galaxy S I9000 Android Development] Project1.exe:
you need to have adb like the OP mentioned for contingency. please download android sdk
[Galaxy S I9000 Android Development] Project1.exe:
very nice! learned one from you :D
[Galaxy S I9000 Android Development] pinku1:
Just flashed phone with Froyo xxJPK (Odin). Everything fine again.

Thanks :)
[Galaxy S I9000 Android Development] emlo16:
On my JPK don't work. When I delete android.policy.odex, close system/framework and open it again I see the same android.policy.odex :(
[Galaxy S I9000 Android Development] Project1.exe:
backread please :)
[Galaxy S I9000 Android Development] jodue:
i guess you missed the "remount the /system readwrite" ... as root type: "mount -o remount rw /system"

only do this if you know what you are doing or you will suffer the same fate as pinku1 and have to reflash ...

edit: too late i guess :D ... but you are right, this has been covered more than enough already in this and other JPK threads ...
[Galaxy S I9000 Android Development] Project1.exe:
lol yeah, it's been asked all over JPK threads. i've added your post's url for persistent rw access on the OP if you don't mind :)
[Galaxy S I9000 Android Development] Aery:
Stock Lockscreen for untouched JPK with Recovery 2e as update.zip with Autobackup

http://xdaforums.com/showpost.php?p=8308233&postcount=160
[Galaxy S I9000 Android Development] jodue:
suit yourself!

that's the nice thing about xda ... it's all about sharing the knowledge! :)
[Galaxy S I9000 Android Development] Project1.exe:
double thumbs up!
[Galaxy S I9000 Android Development] Project1.exe:
cool, thanks Aery. mind if i also put this on OP?
[Galaxy S I9000 Android Development] Aery:
Do it. ;-)

I´ve done it to share.
[Galaxy S I9000 Android Development] emlo16:
Thanks. Works great with Recovery 2e :)
[Galaxy S I9000 Android Development] Aery:
And now? What will come next?

Maybe: How can i go back to Samsung Lockscreen?

Stock Lockscreen Remover for untouched JPK

Download: http://www.multiupload.com/0KP69HOTIK

;-)
[Galaxy S I9000 Android Development] Mopral:
Instuctions from OP still do not work for me

I can't make odex files with menu button fix for untouched JM8

Will have to stay with samsung lockscreen...

Thanks for your work
[Galaxy S I9000 Android Development] Project1.exe:
hahaha :D nice
[Galaxy S I9000 Android Development] Project1.exe:
ima try to flash to jm8 tomorrow to fix that, i'm feeling my JPK is a little messed with playing right now
[Galaxy S I9000 Android Development] karayemis:
I still dont understand how to do this. They copy NEW odex file to .... But what new odex file are they talking about and what is recovery 2e pff am i stupid or what
[Galaxy S I9000 Android Development] itaykoren:
Can you please make this MOD for I9000JPJG8 ?
[Galaxy S I9000 Android Development] Spycraft:
Stock Lockscreen.. but not recieved msg lock screen? :)

Ok, great stuff i like the stock lockscreen better than the glass samsung one..

But did someone notice that when you do get a missed call or text message(i tested with msges not missed calls :P if it makes any diff) the lock screen is glass one again but with the puzzles to move to get the unread msg?

How do i get rid of the glass samsung one alltoghether can i delete something hehe?

To clarify

i have done this mod on JPK and it works.

When i have it locked and i recieve a msg it is fine the lockscreen doesent change.

When i unlock it, DONT read the msg, and just relock it. I get the glass lock screen with the puzzles to move to get to the msgs and this glass lock screen remains until i read them i can lock and unlock many times i will get the glass screen everytime up until msgs bein read.

So as i hate the glass lock i would like to know if anyone knows a fix for this or to just COMPLETLY delete glass samsung screens form the phone.

thanks

Regards!
[Galaxy S I9000 Android Development] Project1.exe:
Thanks for pointing that out. Since I've been applying it out on froyo, i only changed all the invokes for Glasslock (the normal lock) and not the other types of glasslock (for other lock instances). I'll try to update them again after work
[Galaxy S I9000 Android Development] Spycraft:
Thought it would be something like that :) .. Great looking forward to the update! :)
[Galaxy S I9000 Android Development] Kilack:
Just one thing, I have noticed that if I press the home button which then brings up the lock screen.. if you press the button to the left of the home button (menu button) it goes straight into the launcher without having to use the lockscreen.. Is that the way it is supposed to be? this is with jm8.

update: Ahh I see disabling the menu button is an option.
[Galaxy S I9000 Android Development] NeidRider:
I just made a version for JPK with stock lockscreen also in case of missed calls.

Menu button is disabled as well.

Running it on my device with no side-effects, feedback is welcome of course ;-)

md5 of extracted file: 5e03c85c6a782ef47158ca3316defa8c

P.S.: It's only the .odex file, so you'll have to remount rw and copy it over manually. If anybody wants to build an update.zip, feel free.
[Galaxy S I9000 Android Development] Rickstur:
JPK very nice, works flawless here!

Thanx
[Galaxy S I9000 Android Development] d3885u:
Can I use this for froyo DXJP1 firmware?

It would be so much nicer if I can use it to my firmware version...

Thanks in advance..
[Galaxy S I9000 Android Development] honeycured:
worked like a charm on my SGS running DocRom's Slim ROM on JPK. I did the above steps using Terminal Emulator then opened up Root explorer to transfer the file to /system/framework

Thanks heaps!
[Galaxy S I9000 Android Development] Spycraft:
Perfect! thanks!
[Galaxy S I9000 Android Development] tigerminx:
Worked like a treat. Much appreciated. Been dying to get rid of that frustrating glass unlock screen.
[Galaxy S I9000 Android Development] Kilack:
any chance of an update for jm9?
[Galaxy S I9000 Android Development] Project1.exe:
not yet, soon enough.. i'm still at work ^^;
[Galaxy S I9000 Android Development] huxflux2003:
JM9 Pleaaaase
[Galaxy S I9000 Android Development] Husknuten:
Perfect. Thanks :)
[Galaxy S I9000 Android Development] davidhoria2@yahoo.com:
Also a version for JJ1 would be great.
[Galaxy S I9000 Android Development] Dexter_nlb:
Silent is for meetings, where 20+ others dont want to be disturbed by a vibrator or a phone ringing..

and Silent when you dont want to be disturbing others when its on the table? it does make a load noise compared to just flashing when silent is on.

Silent is more frequently used than vibrate function, at least when you get a job and úse the phone at your job.. for teens im sure its worth nothing or pointless functionality.
[Galaxy S I9000 Android Development] Kev-Lo:
Wanting a version of ZUJP2, which is a faster and more stable Froyo ROM

Hope if someone can update it...
[Galaxy S I9000 Android Development] pajendame:
Working great on JPK.

Thanks.
[Galaxy S I9000 Android Development] Kev-Lo:
Sorry to bother.. I tried the one for JPH and is working nice on my SGS with ZUJP2... Excellent

Sent from my GT-I9000
[Galaxy S I9000 Android Development] celeronix:
Can we receive a file for JM9, please. Thanks!

I wonder if this from JM8 could work on JM9 !?!?! Anybody tried this?

Edit: I have tried and it's working :)
[Galaxy S I9000 Android Development] sackynuts:
No support for JM2? :( I hate the samsung lockscreen!
[Galaxy S I9000 Android Development] Project1.exe:
just updated OP with JM9 versions, sorry i've only find time now.

i'm a little unsure about installing I9000TDOJJ1 cause i just installed JM9, and it seems to be having some issues i don't feel a "clean" leak but it's looking to be great. I'm still thinking about it.

for other versions, i'd love to cater you guys :( but i only have this sweet daily driver to play with.
[Galaxy S I9000 Android Development] Project1.exe:
Cool :) I'm glad it worked. just remember it might not work for other froyo builds/versions, we might just got lucky this time ;)
[Galaxy S I9000 Android Development] Onraad:
When I unpack deodexed-jm8-android.policy.jar.rar I get a crc error: file is broken :(
[Galaxy S I9000 Android Development] Project1.exe:
i just redownloaded it from OP and it's good. download again?
[Galaxy S I9000 Android Development] Onraad:
Weird, I also downloaded from another PC and got the same error.. Maybe 7zip is the problem, will try again..

Still not working, tried winrar too. In 7zip it says the size is 125 198, but the packed size is 125 124.. I tried downloading/unpacking some of the other rar files from this topic and they are working just fine.

I'll just upgrade to JM9+Tayutama 1.2 and see how that goes, at least that rar file isn't giving me an error :)
[Galaxy S I9000 Android Development] rithvikgv:
I am getting the same CRC error.I think that particular file is corrupt.
[Galaxy S I9000 Android Development] jodue:
awesome (again), thanks for the jm9 version! makes the sgs a lot better :)
[Galaxy S I9000 Android Development] Project1.exe:
i tried redownloading again, still working with no problems. I've re-uploaded it anyway should work now
[Galaxy S I9000 Android Development] Rawat:
Can we have a new version for JPM? Thanks :)
[Galaxy S I9000 Android Development] Project1.exe:
aww wth?! i dunno if i'm liking a sprint for releases or not lol :D
[Galaxy S I9000 Android Development] Tayutama:
welcome to how we feel ;)

I can make the deoxed version for both JPM and JP6 if you want... i'm about to deoxed both version now
[Galaxy S I9000 Android Development] efegue:
JPM version, please! ;)
[Galaxy S I9000 Android Development] sayli:
+1 for a JPM version please ! :D, thanks in advance
[Galaxy S I9000 Android Development] XlAfbk:
tried to create a JPM version but my phone won't boot with it :-( guess i'll have to let someone else have a go at it...
[Galaxy S I9000 Android Development] Tayutama:
Should have a working version for JPM ready now but haven't rooted my phone yet so isn't tested yet
[Galaxy S I9000 Android Development] teriemer:
Don't forget JP6

Hi Tayutama - please make a version as well for JP6 firmware :D:D:D

In advance, thx
[Galaxy S I9000 Android Development] Bierfreund:
Can you post the file? I have JPM installed rooted and a ClockworkMod Backup, so i could test without any danger...
[Galaxy S I9000 Android Development] Tayutama:
It doesn't work for some reason... phone boots but homescreen keeps looping and mediascanner keeps restarting with it and getting a few vibrations :(
[Galaxy S I9000 Android Development] Project1.exe:
can i get a vote on which is better? i'm still confused if i should flash to JP6 or JPM, so far as i'm reading JP6 seems to perform a little faster. please help me justify
[Galaxy S I9000 Android Development] Tayutama:
You don't really need to flash if you wanna make to lockscreen i can give you the files both for the odexed and the deodexed version if you want

But i'm using JPM mainly since that is what samsung release source code for
[Galaxy S I9000 Android Development] Razer(x):
JP6 version too..
[Galaxy S I9000 Android Development] Project1.exe:
:D it's very much welcome! i'll post it on OP if you please
[Galaxy S I9000 Android Development] Tayutama:
Meaning i can supply you with the stock files ;)

haven't been able to get stock lockscreen to work yet :(
[Galaxy S I9000 Android Development] Project1.exe:
s'ok :) i'm still downloading them both b_ttloads on my slow cxn :(
[Galaxy S I9000 Android Development] Rawat:
Pretty much this for me too. Seems like JPM is the base version, and JP6/JPA are derivatives with regional support (Nordic and African respectively)
[Galaxy S I9000 Android Development] Project1.exe:
Update for JPM

JPM UPDATE

Hi guys, i just realized the reason why they reserver first few posts ^^; so i'm attaching it here.

for JP6, forgive me, jp6 download corrupted so i'm not going to be able to get you one soon. pm me if you want a walkthrough.
[Galaxy S I9000 Android Development] mike.sw:
any chance you can write a short how-to here? :-)

I want it to work for JPA which isn't a very popular version so don't think you'll want to waste your time with.
[Galaxy S I9000 Android Development] mike.sw:
wow thanks for the detailed post! :rolleyes:

going to try it after I get few sleeping hours.
[Galaxy S I9000 Android Development] hayder.jabar:
& for the jpa ?!

Hi, is it possible to modify it for the I9000JPJPA f/w:confused:

Thanks
[Galaxy S I9000 Android Development] mike.sw:
OK it worked! Thanks Project1.exe!

Tested on my device, and looks good. :D
[Galaxy S I9000 Android Development] hayder.jabar:
Great, its just work fine. Thanks x 10e6
[General Topics] DroidBois:
HTC seem to be developing a history of dropping development and support on their models after 6 months, which is extremely annoying unless you like to upgrade every 6 months. Is this false? Or should we all migrate away from HTC to other phones for this reason? My particular interest is in Android.

I was going to get my wife a HTC Desire Z but now I'm wondering if she's better off with an Android phone from a brand with a support history longer than 6 months.
[General Topics] felix1234:
Which Android vendor provides you with long support?

For me, I have just bought a HTC Dream more than 2 years after its release because there are tons of custom roms on xda. The Dream lives on because of the large community.

Make sure what you buy is a popular phone, so when official support stops you would stil get new roms from the community.
[General Topics] DroidBois:
Inclined to agree, I have the original Desire so I am reading up on rooting and custom ROMs. Any suggestions or warnings?
[General Topics] ericc191:
Take your time and read those stickies on the Desire forums. You'll be glad you did.

To OP, I think most are about the same. Though, I am still a little annoyed at the whole TyTN II debacle a few years ago, lol. For me, it really comes down to build quality and not much competes with HTC. Especially when they try. Like the HD2.
[General Topics] DroidBois:
I sure am taking my time. I am the kind of person who drives everyone nuts with questions on every detail.
[General Topics] jelliottz:
This site is a benefit to anyone who uses it. It will extend the life of your phone. Many of the manufacturers will drop support after a few months. Most don't provide upgrades to software. Being able to use this site provides you with both: technical support for problems and upgraded software as newer versions becomes available.

My advice to you; buy a phone supported by XDA. If its not on here, don't buy it...
[General Topics] DroidBois:
Wise words. I am so thankful I got the STOCK factory standard unlocked / unbranded AMOLED UK HTC Desire now, that's about as 'vanilla' as you can get by the sounds of it and I should be ok for ROM support then. Now to work out the right rooting / ROM procedure and which ROM to use!!
[Droid Incredible Q&A, Help & Troubleshooting] iakamand:
i Flashed CM6.0.2 on my DInc and it works perfect for me except when i tried to view a spread sheet through my browser. all i get is the sheet with no data in it.

it's a calculator document that i need for work and it just wont load. can anyone help me with this?

PS the spreadsheet works with the Stock Sense, skyrider 3.0 (latest)

thank you
[Epic 4G General] Blitzpwnage:
I really don't get it, someone posts a legitimate thread, take for instance the thread about Froyo 2.2 and you have people, from an EVO forum come and rip on the device and Samsung. I just dont get the point of trolling another forum, when all of these phones are running android operating systems. I mean do iPhone 3GS people from iPhone 3G people and iPhone 4 people troll the 3GS and the 3G, I really dont know and couldnt tell you but the immaturity is just astounding.

I too would like to know when 2.2 will be released, this is a very good question but for someone to post this and not get any useful information other than the usual. Oh if samsung doesnt have an update out by the end of this month im going back to the EVO or some other phone...Well I felt like ranting.

Also, many people have been saying many phones will be having 3.0 Gingerbread by the time we have 2.2 Does this have any merit to this? :eek:
[Epic 4G General] drewX2:
No clue to 2.2 and no clue to 3.0. Really... I have no clue.
[Epic 4G General] hydralisk:
People that say that are just trying to troll you. They think that because they have 2.2, they can rip on everyone else that still has 2.1.

There are rumors of 2.2 hitting us in October\November. Gingerbread doesn't get released til January I believe.
[Epic 4G General] NeonMonster:
I said that I'm not willing to stick with the Epic past the 30 day return period for a reason. We all know that Samsung as a company has been flakey with updates.

I paid a good deal of money for a device that I expect to be supported and updated within the companies own claimed schedule.

Stating that I'm gonna switch to a different phone if the company proves to not be reliable only means that I'm NOT going to get roped into a 2 year contract with the phone when I could exchange the phone within the 30 day period, and get a phone that IS being supported or even canceling my Sprint plan and going back to TMobile.

posted from a EPIC4G.
[Epic 4G General] hydralisk:
Good for you. I think what Blitz is saying here is that nobody in the Epic forums really cares about people who aren't using the Epic. And I agree. I didn't go in the EVO forums and tell everyone that I'm switching to the Epic because of all the reasons I like it more. Ya know why? They don't care.