Develop Bugs

[FIX][HOWTO] Lockscreen loading Bug

This mod (JVU/JW4/JW5/JW6) fixes bug when battery is below 20 % in lockscreen displayed "charging %" instead of "Please connect charger".
HOWTO
1. Decompile android.policy.jar
For beginers here is a guide by pantrif13 : http://forum.xda-developers.com/show...1&postcount=16
2. Edit android.policy\smali\com\android\internal\policy\impl\ClockWidget.smali
Search
.method public setBatteryInfo()V
Change line:
Code:
invoke-virtual {v3}, Lcom/android/internal/policy/impl/KeyguardUpdateMonitor;->shouldShowBatteryInfo()Z
by
Code:
invoke-virtual {v3}, Lcom/android/internal/policy/impl/KeyguardUpdateMonitor;->shouldShowBatteryInfo1()Z
3. Edit android.policy\smali\com\android\internal\policy\impl\KeyguardUpdateMonitor.smali
Search
Code:
.line 360
new-instance v1, Lcom/android/internal/policy/impl/KeyguardUpdateMonitor$3;
invoke-direct {v1, p0}, Lcom/android/internal/policy/impl/KeyguardUpdateMonitor$3;-><init>(Lcom/android/internal/policy/impl/KeyguardUpdateMonitor;)V
invoke-virtual {p1, v1, v0}, Landroid/content/Context;->registerReceiver(Landroid/content/BroadcastReceiver;Landroid/content/IntentFilter;)Landroid/content/Intent;
Add bellow
Code:
new-instance v1, Lcom/android/internal/policy/impl/KeyguardUpdateMonitor$4;
invoke-direct {v1, p0}, Lcom/android/internal/policy/impl/KeyguardUpdateMonitor$4;-><init>(Lcom/android/internal/policy/impl/KeyguardUpdateMonitor;)V
invoke-virtual {p1, v1, v0}, Landroid/content/Context;->registerReceiver(Landroid/content/BroadcastReceiver;Landroid/content/IntentFilter;)Landroid/content/Intent;
And add to end of file
Code:
.method public shouldShowBatteryInfo1()Z
.locals 1
.prologue
.line 962
iget v0, p0, Lcom/android/internal/policy/impl/KeyguardUpdateMonitor;->mBatteryStatus:I
invoke-direct {p0, v0}, Lcom/android/internal/policy/impl/KeyguardUpdateMonitor;->isPluggedIn(I)Z
move-result v0
if-nez v0, :cond_0
iget v0, p0, Lcom/android/internal/policy/impl/KeyguardUpdateMonitor;->mBatteryLevel:I
invoke-direct {p0, v0}, Lcom/android/internal/policy/impl/KeyguardUpdateMonitor;->isBatteryLow(I)Z
move-result v0
if-eqz v0, :cond_1
:cond_0
const/4 v0, 0x1
:goto_0
return v0
:cond_1
const/4 v0, 0x0
goto :goto_0
.end method
4. Copy the file KeyguardUpdateMonitor$4.smali attached in "android.policy\smali\com\android\internal\policy\impl\" and recompile

Thanks, I hope to see your fix in some ROM now !
Sent from my GT-I9000 using XDA

.Slane. said:
Thanks, I hope to see your fix in some ROM now !
Sent from my GT-I9000 using XDA
Click to expand...
Click to collapse
S A U R O M - Projekt---> JW5/JW4/JVU/JW1/JVZ for I9000

Good news and good job. thanks

I'm just curious how ppl find something like that out. And what does the smileys mean?

What changes did you make to this fix in your jw6 rom?

Yes,jw6 aviable
Sent from my GT-I9000 using xda app-developers app

dark_knight35 said:
I'm just curious how ppl find something like that out. And what does the smileys mean?
Click to expand...
Click to collapse
The smileys ar ;/) (w/out "/" ) and the forum rules are the smileys are activated
Sent from my GT-I9000 using Tapatalk 2

Is there a chance for us with the lack of skills to get this as a flashable zip?

This bug is gone in 2.3.6 ZSJW4 for chinese market. I think it is the only version of JW...firmware that comes with this fixed.

Hey there lirik0.
I tried your guide so as to fix this bug for the Samsung Galaxy S Plus (i9001).
I have made all the changes to the files that you describe (with some differences on the 3rd - it was a different line number).
But i probably need a different attachment file to download and recompile.
Could you please help all the i9001 community to resolve this issue cause?
Thanks in advance!
PS: I have also attached our android.policy.jar from XXKQH ROM.

[MOD][JB/ICS][10/21/2012][AOKP JB-B5/M6] Vibrate on call connect/answer

[Update 10/21/2012]
Added Phone.apk for AOKP JB Build 5;
This thread is dedicated to the method of modifying Phone.apk so that when an outgoing call is connected (answered) the phone vibrates to notify. This feature is useful when driving and is good for health as the wireless signal boosts at the instant when a call is connected so it is better to keep it at a distance and be notified as soon as it is connected.
The method here is inspired by the codes in CM9, but much simpler: only less than 30 lines of smali codes are added to a single file. It works on the latest Phone.apk source codes, and also a modded Phone.apk for AOKP M6 is provided as an attachment. Feel free to mod it in your own ROM, but I just did for AOKP (at least for now) since I would stick to that ROM for best LED notification support.
After baksmali-ing Phone.apk, the file to modify is CallNotifier.smali. Added codes are marked by "+" and "+ { }" and are in red. All modifications below are based on AOKP M6.
1. Add two instance variables
Code:
# instance fields
...
[COLOR="Red"]+.field private mVibrator:Landroid/os/Vibrator;
+.field private mLastVibratedCall:J
[/COLOR]
2. Modify init method to initialize Vibrator
Code:
.method private constructor <init>(Lcom/android/phone/PhoneApp;Lcom/android/internal/telephony/Phone;Lcom/android/phone/Ringer;Lcom/android/phone/BluetoothHandsfree;Lcom/android/phone/CallLogAsync;)V
.registers 11
.parameter "app"
.parameter "phone"
.parameter "ringer"
.parameter "btMgr"
.parameter "callLog"
.prologue
const/4 v3, 0x0
.line 198
invoke-direct {p0}, Landroid/os/Handler;-><init>()V
[COLOR="red"]+ new-instance v2, Landroid/os/Vibrator;
+ invoke-direct {v2}, Landroid/os/Vibrator;-><init>()V
+ iput-object v2, p0, Lcom/android/phone/CallNotifier;->mVibrator:Landroid/os/Vibrator;
[/COLOR]
.line 105
iput-boolean v3, p0, Lcom/android/phone/CallNotifier;->mCallWaitingTimeOut:Z
Note: for JB, use
Code:
[COLOR="red"]+ new-instance v2, Landroid/os/SystemVibrator;;
+ invoke-direct {v2}, Landroid/os/SystemVibrator;-><init>()V
[/COLOR]
3. Add the codes in method onPhoneStateChanged to implement the vibrate logic when an outgoing call is connected (with removal of potential repetitive vibrates). This happens right after the CallWaitingTonePlayer codes and before the setAudioMode codes.
Code:
.method private onPhoneStateChanged(Landroid/os/AsyncResult;)V
...
if-ne v4, v6, :cond_ae
.line 801
iget-object v6, p0, Lcom/android/phone/CallNotifier;->mCallWaitingTonePlayer:Lcom/android/phone/CallNotifier$InCallTonePlayer;
if-eqz v6, :cond_72
.line 802
iget-object v6, p0, Lcom/android/phone/CallNotifier;->mCallWaitingTonePlayer:Lcom/android/phone/CallNotifier$InCallTonePlayer;
invoke-virtual {v6}, Lcom/android/phone/CallNotifier$InCallTonePlayer;->stopTone()V
.line 803
iput-object v13, p0, Lcom/android/phone/CallNotifier;->mCallWaitingTonePlayer:Lcom/android/phone/CallNotifier$InCallTonePlayer;
.line 808
:cond_72
[COLOR="red"]+ {
invoke-interface {v3}, Lcom/android/internal/telephony/Phone;->getForegroundCall()Lcom/android/internal/telephony/Call;
move-result-object v6
invoke-virtual {v6}, Lcom/android/internal/telephony/Call;->getState()Lcom/android/internal/telephony/Call$State;
move-result-object v6
sget-object v9, Lcom/android/internal/telephony/Call$State;->ACTIVE:Lcom/android/internal/telephony/Call$State;
if-ne v6, v9, :cond_72end
invoke-interface {v3}, Lcom/android/internal/telephony/Phone;->getForegroundCall()Lcom/android/internal/telephony/Call;
move-result-object v6
invoke-virtual {v6}, Lcom/android/internal/telephony/Call;->getLatestConnection()Lcom/android/internal/telephony/Connection;
move-result-object v6
invoke-virtual {v6}, Lcom/android/internal/telephony/Connection;->isIncoming()Z
move-result v9
if-nez v9, :cond_72end
invoke-virtual {v6}, Lcom/android/internal/telephony/Connection;->getCreateTime()J
move-result-wide v5
iget-wide v9, p0, Lcom/android/phone/CallNotifier;->mLastVibratedCall:J
cmp-long v9, v5, v9
if-eqz v9, :cond_72end
iput-wide v5, p0, Lcom/android/phone/CallNotifier;->mLastVibratedCall:J
iget-object v6, p0, Lcom/android/phone/CallNotifier;->mVibrator:Landroid/os/Vibrator;
const-wide/16 v9, 0x100
invoke-virtual {v6, v9, v10}, Landroid/os/Vibrator;->vibrate(J)V
:cond_72end
}
[/COLOR]
iget-object v6, p0, Lcom/android/phone/CallNotifier;->mCM:Lcom/android/internal/telephony/CallManager;
invoke-static {v6}, Lcom/android/phone/PhoneUtils;->setAudioMode(Lcom/android/internal/telephony/CallManager;)V
...
As you can see only a small amount of codes is needed to implement the feature. What the mod does in detail:
(1) When a call changes its state to ACTIVE,
(2) Check if it is outgoing,
(3) Also check if it has already vibrated on connect/answer (if we don't have this code then an outgoing connected call will vibrate each time the Phone app switches in/out home screen),
(4) If Y in (2) and N in (3), then vibrate and store the creation time of this call for future checks in (3).
Note that the codes do not create any new objects when a call is connected/answered so the memory overhead should be approximately zero.
See attachment for the modded Phone.apk for AOKP M6. I may do it also for JB ROMs when I switch to them. If you want to cook this mod into your own ROM feel free to do so.
Phone.apk for AOKP JB Build 5 is added on 10/21/2012.

Is this working with JB roms? Just flash this phone.apk in cwm?
Sent from my Galaxy Nexus using xda app-developers app

Great work ! ! ! I tried the modified .apk for AOKP M6 and it works.
The vibration upon call connect is very responsive. I mean... on my girlfriend's Desire S running MIUI, it is delayed by half a second or so.
It'd be nice if it would vibrate when the call disconnects, too.
Sent from my Galaxy Nexus

what about the noob people like me
is there ready flashable or apk file can be installed directly, I tried to installed the attached file but have not installed message
Sent from my Galaxy Nexus using Tapatalk 2

lupipe said:
Is this working with JB roms? Just flash this phone.apk in cwm?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
+1

how to install this on JB rom?!

Hash123 said:
what about the noob people like me
is there ready flashable or apk file can be installed directly, I tried to installed the attached file but have not installed message
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
true true what about us?:laugh:

Hash123 said:
what about the noob people like me
is there ready flashable or apk file can be installed directly, I tried to installed the attached file but have not installed message
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Copy and paste the attached Phone.apk into your /system/app/ folder. Rewrite the existing file, obviously. As the OP said, it's for AOKP M6, but I have a feeling it should work on CM9, AOSP and such... except for ParanoidAndroid and MIUI, of course.
---------- Post added at 03:58 PM ---------- Previous post was at 03:57 PM ----------
lupipe said:
Is this working with JB roms? Just flash this phone.apk in cwm?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Good luck flashing an .apk from Recovery. Or anything that is not .zip, for that matter...

Formhault said:
Copy and paste the attached Phone.apk into your /system/app/ folder. Rewrite the existing file, obviously. As the OP said, it's for AOKP M6, but I have a feeling it should work on CM9, AOSP and such... except for ParanoidAndroid and MIUI, of course.
---------- Post added at 03:58 PM ---------- Previous post was at 03:57 PM ----------
Good luck flashing an .apk from Recovery. Or anything that is not .zip, for that matter...
Click to expand...
Click to collapse
Just moved this phone.apk in system/app but it says cannot copy...im on jb 4.1.1
Sent from my Galaxy Nexus using xda app-developers app

Very nice work, Maybe I should give it a try .

mrzzheng said:
This thread is dedicated to the method of modifying Phone.apk so that when an outgoing call is connected (answered) the phone vibrates to notify. This feature is useful when driving and is good for health as the wireless signal boosts at the instant when a call is connected so it is better to keep it at a distance and be notified as soon as it is connected.
The method here is inspired by the codes in CM9, but much simpler: only less than 30 lines of smali codes are added to a single file. It works on the latest Phone.apk source codes, and also a modded Phone.apk for AOKP M6 is provided as an attachment. Feel free to mod it in your own ROM, but I just did for AOKP (at least for now) since I would stick to that ROM for best LED notification support.
After baksmali-ing Phone.apk, the file to modify is CallNotifier.smali. Added codes are marked by "+" and "+ { }" and are in red. All modifications below are based on AOKP M6.
1. Add two instance variables
Code:
# instance fields
...
[COLOR="Red"]+.field private mVibrator:Landroid/os/Vibrator;
+.field private mLastVibratedCall:J
[/COLOR]
2. Modify init method to initialize Vibrator
Code:
.method private constructor <init>(Lcom/android/phone/PhoneApp;Lcom/android/internal/telephony/Phone;Lcom/android/phone/Ringer;Lcom/android/phone/BluetoothHandsfree;Lcom/android/phone/CallLogAsync;)V
.registers 11
.parameter "app"
.parameter "phone"
.parameter "ringer"
.parameter "btMgr"
.parameter "callLog"
.prologue
const/4 v3, 0x0
.line 198
invoke-direct {p0}, Landroid/os/Handler;-><init>()V
[COLOR="red"]+ new-instance v2, Landroid/os/Vibrator;
+ invoke-direct {v2}, Landroid/os/Vibrator;-><init>()V
+ iput-object v2, p0, Lcom/android/phone/CallNotifier;->mVibrator:Landroid/os/Vibrator;
[/COLOR]
.line 105
iput-boolean v3, p0, Lcom/android/phone/CallNotifier;->mCallWaitingTimeOut:Z
3. Add the codes in method onPhoneStateChanged to implement the vibrate logic when an outgoing call is connected (with removal of potential repetitive vibrates). This happens right after the CallWaitingTonePlayer codes and before the setAudioMode codes.
Code:
.method private onPhoneStateChanged(Landroid/os/AsyncResult;)V
...
if-ne v4, v6, :cond_ae
.line 801
iget-object v6, p0, Lcom/android/phone/CallNotifier;->mCallWaitingTonePlayer:Lcom/android/phone/CallNotifier$InCallTonePlayer;
if-eqz v6, :cond_72
.line 802
iget-object v6, p0, Lcom/android/phone/CallNotifier;->mCallWaitingTonePlayer:Lcom/android/phone/CallNotifier$InCallTonePlayer;
invoke-virtual {v6}, Lcom/android/phone/CallNotifier$InCallTonePlayer;->stopTone()V
.line 803
iput-object v13, p0, Lcom/android/phone/CallNotifier;->mCallWaitingTonePlayer:Lcom/android/phone/CallNotifier$InCallTonePlayer;
.line 808
:cond_72
[COLOR="red"]+ {
invoke-interface {v3}, Lcom/android/internal/telephony/Phone;->getForegroundCall()Lcom/android/internal/telephony/Call;
move-result-object v6
invoke-virtual {v6}, Lcom/android/internal/telephony/Call;->getState()Lcom/android/internal/telephony/Call$State;
move-result-object v6
sget-object v9, Lcom/android/internal/telephony/Call$State;->ACTIVE:Lcom/android/internal/telephony/Call$State;
if-ne v6, v9, :cond_72end
invoke-interface {v3}, Lcom/android/internal/telephony/Phone;->getForegroundCall()Lcom/android/internal/telephony/Call;
move-result-object v6
invoke-virtual {v6}, Lcom/android/internal/telephony/Call;->getLatestConnection()Lcom/android/internal/telephony/Connection;
move-result-object v6
invoke-virtual {v6}, Lcom/android/internal/telephony/Connection;->isIncoming()Z
move-result v9
if-nez v9, :cond_72end
invoke-virtual {v6}, Lcom/android/internal/telephony/Connection;->getCreateTime()J
move-result-wide v5
iget-wide v9, p0, Lcom/android/phone/CallNotifier;->mLastVibratedCall:J
cmp-long v9, v5, v9
if-eqz v9, :cond_72end
iput-wide v5, p0, Lcom/android/phone/CallNotifier;->mLastVibratedCall:J
iget-object v6, p0, Lcom/android/phone/CallNotifier;->mVibrator:Landroid/os/Vibrator;
const-wide/16 v9, 0x100
invoke-virtual {v6, v9, v10}, Landroid/os/Vibrator;->vibrate(J)V
:cond_72end
}
[/COLOR]
iget-object v6, p0, Lcom/android/phone/CallNotifier;->mCM:Lcom/android/internal/telephony/CallManager;
invoke-static {v6}, Lcom/android/phone/PhoneUtils;->setAudioMode(Lcom/android/internal/telephony/CallManager;)V
...
As you can see only a small amount of codes is needed to implement the feature. What the mod does in detail:
(1) When a call changes its state to ACTIVE,
(2) Check if it is outgoing,
(3) Also check if it has already vibrated on connect/answer (if we don't have this code then an outgoing connected call will vibrate each time the Phone app switches in/out home screen),
(4) If Y in (2) and N in (3), then vibrate and store the creation time of this call for future checks in (3).
Note that the codes do not create any new objects when a call is connected/answered so the memory overhead should be approximately zero.
See attachment for the modded Phone.apk for AOKP M6. I may do it also for JB ROMs when I switch to them. If you want to cook this mod into your own ROM feel free to do so.
Click to expand...
Click to collapse
Thank you. jb aspect version. thanks

Formhault said:
Copy and paste the attached Phone.apk into your /system/app/ folder. Rewrite the existing file, obviously. As the OP said, it's for AOKP M6, but I have a feeling it should work on CM9, AOSP and such... except for ParanoidAndroid and MIUI, of course.
---------- Post added at 03:58 PM ---------- Previous post was at 03:57 PM ----------
Good luck flashing an .apk from Recovery. Or anything that is not .zip, for that matter...
Click to expand...
Click to collapse
I did as you said, replaced the phone.apk file with the modified on but nothing was changed , I am on AOKP M6

Hash123 said:
I did as you said, replaced the phone.apk file with the modified on but nothing was changed , I am on AOKP M6
Click to expand...
Click to collapse
restart to let the magic happen.

lupipe said:
Just moved this phone.apk in system/app but it says cannot copy...im on jb 4.1.1
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
That's because the Phone.apk is for AOKP M6, which is based on 4.0.4. That file might work on other 4.0.4-based ROMs, but no way it's gonna work on JB...
Hash123 said:
I did as you said, replaced the phone.apk file with the modified on but nothing was changed , I am on AOKP M6
Click to expand...
Click to collapse
When I replaced the file and went into the Phone, Contacts stopped working. So I figured a reboot is requred. Restarted the phone and everything was fine .
I flashed this mod today... I sold my Nexus today... Happy & sad at the same time. Oh well... guess I'll be off this topic/forum, lol.

Hello. you can do. version. jb? thanks: Rolleyes:

mrzzheng said:
restart to let the magic happen.
Click to expand...
Click to collapse
Formhault said:
That's because the Phone.apk is for AOKP M6, which is based on 4.0.4. That file might work on other 4.0.4-based ROMs, but no way it's gonna work on JB...
When I replaced the file and went into the Phone, Contacts stopped working. So I figured a reboot is requred. Restarted the phone and everything was fine .
I flashed this mod today... I sold my Nexus today... Happy & sad at the same time. Oh well... guess I'll be off this topic/forum, lol.
Click to expand...
Click to collapse
yes you are right, it is working as should be
Sent from my Galaxy Nexus using Tapatalk 2

Can someone make this mod for JB?
Sent from my Galaxy Nexus using xda app-developers app

Can someone make this mod for JB? thanks

I hope you can make a JB version, since this is a very useful feature
Sent from my GT-P6200 using xda app-developers app

So does it work with JB or not?

[DEV] [MOD] [HOW-TO] Call Recording on LG2 Based Sprint ROMS [MOD]

Hey everyone! In response to sudden events i am deciding to make tutorials for all my MODS for interested DEVS. I'm going to start off with the Call recording MOD
First you're going to need to decompile the Smali in SecPhone.apk
Navigate to the following smali file: \com\android\phone\PhoneFeature.smali
Edit the following code:
Code:
:cond_4e
[COLOR="Green"]++:goto_4e[/COLOR]
const/4 v1, 0x1
[COLOR="Red"]--:goto_4e[/COLOR]
invoke-static {v1}, Ljava/lang/Boolean;->valueOf(Z)Ljava/lang/Boolean;
move-result-object v8
.line 575
const-string v1, "SKT"
Now compile and push apk too /system/app/ and you are done
**ATTENTION** Your goto id's may be something different just add the line listed above and change the goto ID to the one listed in your smali.
Have fun

Did this add a third button to the normal phone app? Can you post the recompiled app or is that against the policy
Sent from my SPH-L710...if some one helps you press the thanks button

xtrezpasor said:
Did this add a third button to the normal phone app? Can you post the recompiled app or is that against the policy
Sent from my SPH-L710...if some one helps you press the thanks button
Click to expand...
Click to collapse
This adds a button to the stock app
Sent from my SPH-L710 using Tapatalk 2

clark44 said:
This adds a button to the stock app
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Do you lose the swap button?
Sent from my SPH-L710...if some one helps you press the thanks button

xtrezpasor said:
Do you lose the swap button?
Sent from my SPH-L710...if some one helps you press the thanks button
Click to expand...
Click to collapse
I haven't really checked that out. I dident get any reports of that issue.
Sent from my SPH-L710 using Tapatalk 2

clark44 said:
I haven't really checked that out. I dident get any reports of that issue.
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
I'll try to do this my self but if you can post a copy of yours working that be awesome
Sent from my SPH-L710...if some one helps you press the thanks button

I've done this mod, slightly different, but it worked nonetheless.
Either method will make "additional settings" under call settings force close.
My method was this
LOOK FOR:
Code:
const-string v2, "restore_spk_unplugged_dock"
invoke-virtual {v1, v2, v8}, Ljava/util/HashMap;->put(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;
invoke-static {}, Lcom/android/phone/PhoneFeature;->makeFeatureForKor()V
invoke-static {}, Lcom/android/phone/PhoneFeature;->makeFeatureForUsa()V
return-void
:cond_8ca
const/4 v1, 0x0
goto/16 :goto_28
:cond_8cd
const/4 v1, 0x0
goto/16 :goto_4f
LOOK AROUND:
Code:
:cond_8cd
const/4 v1, 0x0
goto/16 :goto_4f
CHANGE:
Code:
const/4 v1, 0x0
INTO:
Code:
const/4 v1, 0x1

freeza said:
I've done this mod, slightly different, but it worked nonetheless.
Either method will make "additional settings" under call settings force close.
My method was this
LOOK FOR:
Code:
const-string v2, "restore_spk_unplugged_dock"
invoke-virtual {v1, v2, v8}, Ljava/util/HashMap;->put(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;
invoke-static {}, Lcom/android/phone/PhoneFeature;->makeFeatureForKor()V
invoke-static {}, Lcom/android/phone/PhoneFeature;->makeFeatureForUsa()V
return-void
:cond_8ca
const/4 v1, 0x0
goto/16 :goto_28
:cond_8cd
const/4 v1, 0x0
goto/16 :goto_4f
LOOK AROUND:
Code:
:cond_8cd
const/4 v1, 0x0
goto/16 :goto_4f
CHANGE:
Code:
const/4 v1, 0x0
INTO:
Code:
const/4 v1, 0x1
Click to expand...
Click to collapse
I see you're just enabling the feature. Same thing. Yours is slightly simpler. Good information for people who can't get mine to work
Sent from my SPH-L710 using Tapatalk 2

Sorry so by doing all of this it will basically enable call recording without having to use a third party app over speaker phone. And I've never done this before so I'm I too user terminal for all off this ? Thanks again for the help.
Sent from my SPH-L710 using xda premium

Yelp, anyone please help. Does this work for lg8
Sent from my SPH-L710 using xda premium

Does not seem to work on LG8.

Didact74 said:
Does not seem to work on LG8.
Click to expand...
Click to collapse
I'm running Blazer v1.8 with LG8 and have it working just fine. Are you on a stock rom?
I installed the zip from this post:
http://forum.xda-developers.com/showpost.php?p=28164335&postcount=2
---------- Post added at 02:06 PM ---------- Previous post was at 02:03 PM ----------
Does any one know how to mod this so it automatically records all calls?

Would this work with CM10?

joelstitch said:
Would this work with CM10?
Click to expand...
Click to collapse
Only works with ics Roms unfortunately, not working with Jelly yet.

i apologize but how do i get to the point to add the mod?

freeza said:
I've done this mod, slightly different, but it worked nonetheless.
Either method will make "additional settings" under call settings force close.
My method was this
LOOK FOR:
Code:
const-string v2, "restore_spk_unplugged_dock"
invoke-virtual {v1, v2, v8}, Ljava/util/HashMap;->put(Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/Object;
invoke-static {}, Lcom/android/phone/PhoneFeature;->makeFeatureForKor()V
invoke-static {}, Lcom/android/phone/PhoneFeature;->makeFeatureForUsa()V
return-void
:cond_8ca
const/4 v1, 0x0
goto/16 :goto_28
:cond_8cd
const/4 v1, 0x0
goto/16 :goto_4f
LOOK AROUND:
Code:
:cond_8cd
const/4 v1, 0x0
goto/16 :goto_4f
CHANGE:
Code:
const/4 v1, 0x0
INTO:
Code:
const/4 v1, 0x1
Click to expand...
Click to collapse
Freeza have you managed to get this working on JB and if so can you make an Xposed framework module for it?

dyehya said:
Freeza have you managed to get this working on JB and if so can you make an Xposed framework module for it?
Click to expand...
Click to collapse
yes have you gotten it to work?
Sent from my SPH-L710 using xda premium

[DEV] [MOD] [HOW-TO] Remove Fully Charge Notification on LG8 Based Sprint ROMS [MOD]

Hello again! Here is a quick tutorial on how to remove the annoying fully battery notification! This also disables the screen from turning on by itself when its fully charged!
First you're going to need to decompile the Smali in SystemUI.apk
TIP: When decompiling classes.dex, run the -b tag as well so you can remove all the .line's ect and keep it just code
Navigate to the following smali file: com\android\systemui\power\PowerUI.smali
Remove the the following lines (Or comment them out, whichever you prefer):
Code:
invoke-virtual {v7, v8, v6, v5, v3}, Landroid/app/Notification;->setLatestEventInfo(Landroid/content/Context;Ljava/lang/CharSequence;Ljava/lang/CharSequence;Landroid/app/PendingIntent;)V
iget-object v7, p0, Lcom/android/systemui/power/PowerUI;->mFullBatteryNotification:Landroid/app/Notification;
iget v7, v7, Landroid/app/Notification;->icon:I
iget-object v8, p0, Lcom/android/systemui/power/PowerUI;->mFullBatteryNotification:Landroid/app/Notification;
[COLOR="Red"] [B]--[/B] invoke-virtual {v2, v7, v8}, Landroid/app/NotificationManager;->notify(ILandroid/app/Notification;)V[/COLOR]
iget-object v7, p0, Lcom/android/systemui/SystemUI;->mContext:Landroid/content/Context;
const-string v8, "power"
invoke-virtual {v7, v8}, Landroid/content/Context;->getSystemService(Ljava/lang/String;)Ljava/lang/Object;
move-result-object v4
check-cast v4, Landroid/os/PowerManager;
The next line is here:
Code:
const-string v8, "PowerUI"
invoke-virtual {v4, v7, v8}, Landroid/os/PowerManager;->newWakeLock(ILjava/lang/String;)Landroid/os/PowerManager$WakeLock;
move-result-object v0
const-wide/16 v7, 0x4e20
[COLOR="red"][B]--[/B] invoke-virtual {v0, v7, v8}, Landroid/os/PowerManager$WakeLock;->acquire(J)V[/COLOR]
goto :goto_14
.end method
.method playSound(Landroid/net/Uri;)V
.registers 10
const-string v4, "PowerUI"
new-instance v5, Ljava/lang/StringBuilder;
invoke-direct {v5}, Ljava/lang/StringBuilder;-><init>()V
Thats it! Now compile and push your new SystemUI.apk and enjoy not being bugged by that annoying notification
Have fun!

thanks for this! I had this mod on my Samsung Moment and Samsung Transform, but they made it a flashable zip. Any chance of that happening?

So umm how about that mms mod lol sorry couldn't resist
Apple just give up the IPHONE sucks deal with it.

blackdragon79 said:
So umm how about that mms mod lol sorry couldn't resist
Apple just give up the IPHONE sucks deal with it.
Click to expand...
Click to collapse
Haha its STILL a WIP. Its a tough MOD trust me.

Thank you again sir. Its nice to see you sharing helpful information the way that you do.
Sent from my SGS3 while experiencing some Wicked Sensations™.

clark44 said:
Haha its STILL a WIP. Its a tough MOD trust me.
Click to expand...
Click to collapse
Apple just give up the IPHONE sucks deal with it.
Trust me I know it is. Wish Samsung wouldn't put a limit on that.

Hmm I did this as my first adventure in DE-compile/rebuild all seem to work fine.. I also wiped dalvik/cache after reinstal of modded SUI.
Since Iv'e noticed two things. That the phone no longer wakes up on an incoming call. and it seems to take a really long time to boot. Maybe I did something wrong (I did pull/install framework-res.apk b4 decompile of SUI could that have messed up something?)
LP

That's great. thanks for share.

Is there a ZIP for this? I am a little slow with the changing of codes.
Sent from my SPH-L710 using xda premium

Great Work OP!
I too would appreciate a flashable zip file for this Mod since I have not taken the time to learn to alter the code strings myself.
I am on Blazer ROM 1.8 and for some reason Mod's like this are not present even on the most recent version.

[MOD][GUIDE] Device Status Info "Normal" Instead Of "Modified" Mod!

[MOD][GUIDE] Device Status Info "Normal" Instead Of "Modified" Mod!
Hello to all Developers and XDA members! I have come here to give you a guide on how you can change the device status info from "Modified" to "Normal" and here is how you can do it!
What Is Required...
★ First you need to have experience and know how to decompile/recompile apks with Apktools, apkmanager, smali, and baksmali
★ Have 7-zip installed onto your computer/laptop
★ Make sure you have Notepad++ also installed!
★HOW TO CHANGE THE DEVICE STATUS INFO FROM "MODIFIED" TO "NORMAL"★
WHAT DOES THIS MOD DO: Instead Of The Device Status Showing As "Modified" It Now Shows As "Normal". So Now The Custom Rom Can Look More Like It's Stock.
STEP 1
★ Go into your system/app folder and take out your "SecSettings.apk"
★ Then use one of the applications such as apktools or apkmanager and then use the commands to decompile the SecSettings.apk
★ Once you have decompiled the SecSettings.apk, navigate and go to:
smali/com/android/settings/deviceinfo/Status.smali
Click to expand...
Click to collapse
Now open up "Status.smali" with Notepad++ for editing:
Now for this part of this guide what I have highlighted in GREEN text is what you have to find using Notepad++, What you see in RED is the line you have to remove/delete, And also what you see in BLUE is the line you have to make the modified changes to:
SEARCH FOR METHOD:
Code:
[COLOR="Green"].method private changeSysScopeStatus()V[/COLOR]
NOW REMOVE THIS WHOLE ENTIRE LINE THAT YOU SEE IN RED ALL THE WAY DOWN TO THE .END METHOD:
Code:
[COLOR="Green"].method private changeSysScopeStatus()V[/COLOR]
[COLOR="Red"].locals 7
.prologue
const-wide/16 v3, 0x3e8
const v6, 0x7f090129
const/4 v5, -0x1
.line 827
const-string v0, "sysscope_status"
invoke-virtual {p0, v0}, Lcom/android/settings/deviceinfo/Status;->findPreference(Ljava/lang/CharSequence;)Landroid/preference/Preference;
move-result-object v2
.line 829
invoke-static {}, Landroid/os/SystemClock;->uptimeMillis()J
move-result-wide v0
div-long/2addr v0, v3
.line 830
invoke-static {}, Landroid/os/SystemClock;->elapsedRealtime()J
move-result-wide v0
div-long/2addr v0, v3
.line 832
const-wide/16 v3, 0x0
cmp-long v3, v0, v3
if-nez v3, :cond_0
.line 833
const-wide/16 v0, 0x1
.line 836
:cond_0
iget-object v3, p0, Lcom/android/settings/deviceinfo/Status;->mSysScope:Lcom/sec/android/app/sysscope/service/SysScope;
invoke-virtual {v3}, Lcom/sec/android/app/sysscope/service/SysScope;->isConnected()Z
move-result v3
if-nez v3, :cond_1
const-wide/16 v3, 0x78
cmp-long v0, v0, v3
if-lez v0, :cond_1
.line 837
invoke-virtual {p0, v6}, Lcom/android/settings/deviceinfo/Status;->getString(I)Ljava/lang/String;
move-result-object v0
.line 854
:goto_0
invoke-virtual {v2, v0}, Landroid/preference/Preference;->setSummary(Ljava/lang/CharSequence;)V
.line 855
return-void
.line 840
:cond_1
:try_start_0
iget-object v0, p0, Lcom/android/settings/deviceinfo/Status;->mSysScope:Lcom/sec/android/app/sysscope/service/SysScope;
invoke-virtual {v0}, Lcom/sec/android/app/sysscope/service/SysScope;->getLastScanResult()Lcom/sec/android/app/sysscope/service/SysScopeResultInfo;
move-result-object v0
invoke-virtual {v0}, Lcom/sec/android/app/sysscope/service/SysScopeResultInfo;->getResult()I
move-result v0
iput v0, p0, Lcom/android/settings/deviceinfo/Status;->isSysScopeStatus:I
:try_end_0
.catch Ljava/lang/Exception; {:try_start_0 .. :try_end_0} :catch_0
.line 845
:goto_1
iget v0, p0, Lcom/android/settings/deviceinfo/Status;->isSysScopeStatus:I
const/4 v1, 0x2
if-ne v0, v1, :cond_2
.line 846
invoke-virtual {p0, v6}, Lcom/android/settings/deviceinfo/Status;->getString(I)Ljava/lang/String;
move-result-object v0
goto :goto_0
.line 841
:catch_0
move-exception v0
.line 842
iput v5, p0, Lcom/android/settings/deviceinfo/Status;->isSysScopeStatus:I
goto :goto_1
.line 847
:cond_2
iget v0, p0, Lcom/android/settings/deviceinfo/Status;->isSysScopeStatus:I
if-ne v0, v5, :cond_3
.line 848
const v0, 0x7f09012a
invoke-virtual {p0, v0}, Lcom/android/settings/deviceinfo/Status;->getString(I)Ljava/lang/String;
move-result-object v0
goto :goto_0
.line 850
:cond_3
const v0, 0x7f09012a
invoke-virtual {p0, v0}, Lcom/android/settings/deviceinfo/Status;->getString(I)Ljava/lang/String;
move-result-object v0
goto :goto_0
.end method[/COLOR]
AND THEN ADD THIS ENTIRE NEW METHOD RIGHT UNDER TO THE METHOD YOU HAVE SEARCHED FOR IN GREEN:
Code:
[COLOR="Green"].method private changeSysScopeStatus()V[/COLOR]
[COLOR="Blue"].locals 2
const-string v0, "sysscope_status"
invoke-virtual {p0, v0}, Lcom/android/settings/deviceinfo/Status;->findPreference(Ljava/lang/CharSequence;)Landroid/preference/Preference;
move-result-object v0
const v1, 0x7f090128 #sysscope_normal
invoke-virtual {p0, v1}, Lcom/android/settings/deviceinfo/Status;->getString(I)Ljava/lang/String;
move-result-object v1
invoke-virtual {v0, v1}, Landroid/preference/Preference;->setSummary(Ljava/lang/CharSequence;)V
return-void
.end method
[/COLOR]
STEP 2
I have added a hashtag which is #sysscope_normal from the new method you have to add from above that I have highlighted in BLUE. For your next step on how you can find your public id which mines in this guide is 0x7f090128 for sysscope_normal since for other carriers your public id might be different. To find yours here is how...
Once your "SecSettings.apk" is decompiled head to:
res/values/public.xml
Click to expand...
Click to collapse
Now open up "public.xml" with Notepad++:
Now for this part what I have highlighted in GREEN text is what you have to find using Notepad++, What you see in BLUE is the line you have to look at to get your sysscope_normal public string id:
SEARCH FOR PUBLIC STRING:
Code:
[COLOR="Green"]<public type="string" name="sysscope_normal"[/COLOR]
My syscope_normal public string id for T-Mobile is what you see in BLUE:
Code:
[COLOR="Green"]<public type="string" name="sysscope_normal" id="[/COLOR][COLOR="Blue"]0x7f090128[/COLOR][COLOR="Green"]" />[/COLOR]
If your sysscope_normal public string id is different than mines, what your going to need to do is copy your public string id that's different, and then paste it over the the public id right next to #sysscope_normal from the entire new method that you have added that is highlighted in BLUE from STEP 1.
Now once your done with modifying the "Status.smali" and checking that you have the right public id, Save your Notepad changes, Recompile your SecSettings.apk using apktool or smali commands and your DONE! You should now head to "Settings - About device - Status" and where it says "Device Status" It should now say "Normal" Instead Of "Modified"!... ENJOY!
REMINDER...
Remember this works for all S3 Devices on all carriers T-Mobile, ATT, Verizon, Sprint, And Etc!

Oh man.... this.... this is freaking awesome! You rock Jovy! Amazing job as always man. So adding to my next update. Thanks bro.

nice find! :good:

I have think there is a typo in step one, you said to decompile SecMms.apk, I believe you meant SecSettings
Sent from my Galaxy Note 10.1!

Jamison904 said:
Oh man.... this.... this is freaking awesome! You rock Jovy! Amazing job as always man. So adding to my next update. Thanks bro.
Click to expand...
Click to collapse
Thanks bro! Enjoy the mod its great implementing this mod on any modified rom, the modified rom now acts as if its a real stock rom since it is now "Normal"! :good:
Sent from my SGH-T999 using Tapatalk 2

semorebutts123 said:
nice find! :good:
Click to expand...
Click to collapse
Thanks! :good:
Sent from my SGH-T999 using Tapatalk 2

Great job bro!!! I have been waiting for something like this for a while.... Your instructions are on point and easy to follow. Thanks for your dedication man.

LoopDoGG79 said:
I have think there is a typo in step one, you said to decompile SecMms.apk, I believe you meant SecSettings
Sent from my Galaxy Note 10.1!
Click to expand...
Click to collapse
Oops thanks for the heads up I have just fixed it and also to let everyone know I have updated the OP with a Reminder for the people who have a S3 device on another carrier...

prototype.77 said:
Great job bro!!! I have been waiting for something like this for a while.... Your instructions are on point and easy to follow. Thanks for your dedication man.
Click to expand...
Click to collapse
Your welcome bro. :good:
Sent from my SGH-T999 using Tapatalk 2

Damn Jovy you always find the best tweaks! Great job man. Will try it and install Isis wallet
One question though, Will this let your phone search for updates or OTA when their out? And not say your device is modded anymore

gypsy214 said:
Damn Jovy you always find the best tweaks! Great job man. Will try it and install Isis wallet
One question though, Will this let your phone search for updates or OTA when their out? And not say your device is modded anymore
Click to expand...
Click to collapse
Im not sure since i always remove/hide the firmware update setting from my roms so i cant test that part out hopefully someone could post and let me know, but imo it shouldnt ask for firmware OTA updates if the developer has already removed the specific apk files that has to do with anything about checking/searching for OTA updates.
Sent from my SGH-T999 using Tapatalk 2

jovy23 said:
Im not sure since i always remove/hide the firmware update setting from my roms so i cant test that part out hopefully someone could post and let me know, but imo it shouldnt ask for firmware OTA updates if the developer has already removed the specific apk files that has to do with anything about checking/searching for OTA updates.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Well every now and then I like to go completely stock. Was just wondering if with this method it will actually notify when there is an update. Will go flash the stock ROM with a previous firmware and this and see if it happens.
Was just wondering

Nice work and find bro!

sbreen94 said:
Nice work and find bro!
Click to expand...
Click to collapse
Thanks man! Enjoy... :good:

Shows normal but apps that check for root like media hub still won't work.
Sent from my SGH-T999 using xda premium

Great job! I'll be sure and add the credit to the how-to here. Oh wait..how did the date on this thread? Definitely something weird....
http://forum.xda-developers.com/showthread.php?t=2192199

digiblur said:
Great job! I'll be sure and add the credit to the how-to here. Oh wait..how did the date on this thread? Definitely something weird....
http://forum.xda-developers.com/showthread.php?t=2192199
Click to expand...
Click to collapse
lol nice work digiblur! I added your mod to my rom and it worked great! I will be giving you credit in my op for making the mod
Thanx for sharing

Hey Jovy. I love the ROM. X2 is definitely a beast. After I flashed the mod for normal status, it shows normal but I still can't play content from media hub or connect via all share cast. Any help would be greatly appreciated being that I would like to use this awesome ROM and view on big screen via all share cast.
Sent from my SGH-T999 using xda premium

seshaz said:
Shows normal but apps that check for root like media hub still won't work.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Media Hub does work with root. I'm rooted stock right now and I have a working media hub. as long as device status is "normal" media hub should work fine.

christucker97 said:
Hey Jovy. I love the ROM. X2 is definitely a beast. After I flashed the mod for normal status, it shows normal but I still can't play content from media hub or connect via all share cast. Any help would be greatly appreciated being that I would like to use this awesome ROM and view on big screen via all share cast.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
It's because it is a cosmetic change only.
Sent from my little Note2