Recent content by majdinj

Goldie you are amazing man by writing such comprehensive tutorials for understanding smali codes.. I just logged in and guess what; a great thread is there. :laugh: I really learned from you a lot, and your thread helped me to polish my existing knowledge about smali.. :good: ...BETTER SHARE...

Since it is requested by many users, I will share my current running ROM on my device with you guys :) This is only an update package to my old GloryROM v4.5 LSB firmware that includes almost all mods guides incorporated that I wrote until now. This is the same LSB version but with all features...

Zipalign only optimizes java classes source.. It will not optimize resources like images or compress the file.. RAM will depend on both source and resources optimization.

Can you post your smali mate. Please use [hide] and [code] flag, so I can help you without need to download the smali :)

Have you read the tip??? "Some CSC needs restart to load changes" :)

WOW, that's really awesome,, I know these overridden codes sometimes cause problem... Although I am not a big fan for AOSP skin, but at least your guide gives AOSP layout some meaning for existing ;).. I will link your post man in OP. Reason for not sharing this in general section: mm,, since I...

The code for "CscFeature_Setting_EnableMenuBlockCallMsg" in Settings.smali before editing is looked like this: .line 596 invoke-static {}, Lcom/sec/android/app/CscFeature;->getInstance()Lcom/sec/android/app/CscFeature; move-result-object v3 const-string v6...

There is problem with smali editing. Make sure of your editing buddy.

Heh, I don't need money buddy. If I wanted, I would put donate link, right? Some THANKS is enough for me :)

You can do this trick instead: - Use baksmali/smali manager to baksmali your SecSettings.apk - Add the new smali there for AllShareCast. - Use baksmali/smali manager to smali your SecSettings.apk - Move Modded_SecSettings.apk to apktool working folder. - Decompile using apktool and apply your...

remove: it will remove all debugging lines like those lines which make problem with compiling using apktool (.param, .local, .line...) retain: it will baksmali without removing any debugging. Then it will ask to use .locals or .registers for smali's methods Read JF home page here for more...

In your log, it shows something like this: java version "1.7.0_21" Java(TM) SE Runtime Environment (build 1.7.0_21-b11) Java HotSpot(TM) 64-Bit Server VM (build 23.21-b01, mixed mode) I: Checking whether sources has changed... I: Smaling... [17,4] Error for input '.param': Invalid directive...

This is because the decompiler you use (apktool), use parameter instead of param (which is used by baksmali),, Just delete all lines that the log points, and you should be OK (These are only used for debugging..!!) 1- There is thread for that in xda by shoman94, search it and you will find it...

Lol,, thanks ;)

most likely within 2 weeks,,, I have to travel to several areas to collect my study samples.. You were a great help Goldie,, I learned from you a lot.. :o To all, please forgive me if I made un-intended thing that you don't like,, xda was and still a great family to me.. Se ya all guys after...