Root 2.3.6 lockscreen

[doowop0593]

Hey Does anyone know how to take the stock lockscreen from 2.3.6 and use it for Monster 5.3? Just thought it would be cool to add to such a smooth creation. Thanks

 

[qandres12]

its already been talked about somewhere on here. i believe it was said that the screen lock was located in the framework (dont remember) but it takes decompiling to get it. anyways the new screen lock is cool looking but its way easier to unlock by accident.

 

[doowop0593]

Nice to know that I guess I'll try decompiling the stock lockscreen from the esteem. I believe its gonna be a pain but here goes.

 

[Slickinator]

You don't want that lockscreen, looks nice but its so easy for it to unlock in your pocket

 

[KageBeast]

You don't want that lockscreen, looks nice but its so easy for it to unlock in your pocket

Well it cant unlock if your phone screen is turned off

 

[Slickinator]

It does for me, the back and home buttons get pressed constantly in my pants lol

 

[Spz0]

its already been talked about somewhere on here. i believe it was said that the screen lock was located in the framework (dont remember) but it takes decompiling to get it. anyways the new screen lock is cool looking but its way easier to unlock by accident.

You make it sound easy.

You would need to decompile android.policy, services.jar, framework-res.apk on both roms.
Then you would have to dex-to-jar the necessary lockscreen smalis to view them as readable code.
You would then have to kang, or rewrite the lockscreen code in java.
Then you would have to convert the java smali back to dex.
Then you would have to get into framework-res.apk and add the new images, then add the values to the corresponding xml files.
Then recompile everything and pray that when you reinsert the files your phone doesnt throw up all over the place.
Im sure theres more, but thats it in a nutshell.

Sound easy? heh

 

[qandres12]

You make it sound easy.

You would need to decompile android.policy, services.jar, framework-res.apk on both roms.
Then you would have to dex-to-jar the necessary lockscreen smalis to view them as readable code.
You would then have to kang, or rewrite the lockscreen code in java.
Then you would have to convert the java smali back to dex.
Then you would have to get into framework-res.apk and add the new images, then add the values to the corresponding xml files.
Then recompile everything and pray that when you reinsert the files your phone doesnt throw up all over the place.
Im sure theres more, but thats it in a nutshell.

Sound easy? heh

i didnt mean to under sell it lol i dont know from experience but from what all the devs say its a pain. but yeah you clarified the entire process lol :thumbup:

 

[ShinySide]

You make it sound easy.

You would need to decompile android.policy, services.jar, framework-res.apk on both roms.
Then you would have to dex-to-jar the necessary lockscreen smalis to view them as readable code.
You would then have to kang, or rewrite the lockscreen code in java.
Then you would have to convert the java smali back to dex.
Then you would have to get into framework-res.apk and add the new images, then add the values to the corresponding xml files.
Then recompile everything and pray that when you reinsert the files your phone doesnt throw up all over the place.
Im sure theres more, but thats it in a nutshell.

Sound easy? heh

+1 lots and lots and lots of samli