yashsingh1/xdaforums huggingface dataset:
[Sprint Samsung Galaxy S III] Mongo23ny:
Re-did the mod with the same result, light goes off with the screen.
[Sprint Samsung Galaxy S III] Mongo23ny:
Check post # 82.
[Sprint Samsung Galaxy S III] stas333:
doesnt work for me. i keep getting systemui stopped. after restoring the original files, the phone was having major issues. so i restored my nandroid backup
[Sprint Samsung Galaxy S III] CNexus:
Ok, [MENTION=5660144]hissam8[/MENTION], [MENTION=4278317]Mongo23ny[/MENTION]

Make the following modifications to use DashLight as the app linked to your flashlight toggle.

Open your FlashlightQuickSettingButton.smali and find this code:

const-string v1, "net.cactii.flash2.TOGGLE_FLASHLIGHT"

invoke-direct {v0, v1}, Landroid/content/Intent;-><init>(Ljava/lang/String;)V

const-string v1, "net.cactii.flash2.EXTRA_DISABLE_NOTIFICATION"

then change it to

const-string v1, "com.spectrl.dashlight.FLASHLIGHT_TOGGLE"

invoke-direct {v0, v1}, Landroid/content/Intent;-><init>(Ljava/lang/String;)V

const-string v1, "com.spectrl.DashLight.tasker.extra.NOTIF_ACTION"

Recompile, sign and push the new SystemUI along with the Dashlight apk into /system/app and the flashlight toggle should work fine with screen turned off.

I can also disable DashClock from showing in app drawer and disable its notification if you like.
[Sprint Samsung Galaxy S III] Mongo23ny:
I will give it go. Thank you very much. How do you sign it in apktool? I thought you didn't sign system apps. Is there a modded Dash light apk or use from the app store?
[Sprint Samsung Galaxy S III] CNexus:
Sign it only if you aren't disabling signature verification in your entire rom...otherwise you need to copy the META-INF and AndroidManifest.xml from the original SystemUI.apk into the new SystemUI.apk to keep the system signature intact

As for DashClock, I can provide a modified one hidden from the app drawer and/or with notification disabled, or you can just grab it from the play store.
[Sprint Samsung Galaxy S III] Mongo23ny:
Oh, OK. I always pull those folders into the new apk after I recompile. Sorry for the confusion. That would be great unless you wanna tell me how to it.
[Sprint Samsung Galaxy S III] CNexus:
I already had it done, so here it is: https://www.dropbox.com/s/u4k89x8bsejgdwe/dashlight_mod.apk

But I can certainly tell you how I do it.

To disable in app drawer: Open AndroidManifest.xml and find these lines

<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />

Change "android.intent.category.LAUNCHER" to "android.intent.category.GADGET"

App will no longer show up in app drawer now.

------

To disable the notification, search all the smali files for this string:

Landroid/app/NotificationManager;->notify

Then comment out all lines that contain the string above and notifications will not show up from that app.
[Sprint Samsung Galaxy S III] Mongo23ny:
Thank you so much. Can I just edit the SystemUI I already did or do I need to start from scratch?
[Sprint Samsung Galaxy S III] CNexus:
You can use the one you already did
[Sprint Samsung Galaxy S III] Mongo23ny:
Coolio. Thanks
[Sprint Samsung Galaxy S III] hissam8:
Thank you so much for helping out.

s3rgio4 a member made the flashable zip for the ditto note 3 rom for note 2, he compiled the flashable zip https://docs.google.com/file/d/0B6iYj6loPIwHZlp3UGhoWU5vUHM/edit?pli=1

Since im a noob, can you please help me again and edit the files, im still learning :)
[Sprint Samsung Galaxy S III] hissam8:
ok got it to work. Thank you so much Cnexus, you are a genius indeed. Cheers :)
[Sprint Samsung Galaxy S III] Mongo23ny:
Redid the mod w/ the Dashlight apk, works perfectly. Thanks very much.
[Sprint Samsung Galaxy S III] CNexus:
Awesome, I'm glad it worked :thumbup::thumbup:
[Sprint Samsung Galaxy S III] Keyz450:
can i flash this in recovery?
[Sprint Samsung Galaxy S III] XxTeXx07xX:
Nice....

I hit the Thank you button already but thanks again! Great guide.... hope to see more 4.3 guides from you :good:

:laugh:

---------- Post added at 05:02 AM ---------- Previous post was at 04:23 AM ----------

Cnexus do I just delete the op torch.apk and install or replace the hiddenappdrawerTorch.apk ??? What is the process to replace the orginal Torch.apk with the hiddenappdrawer apk? Thankz

EDIT: just come to realize I can rename it to Torch.apk and overright... :)
[Sprint Samsung Galaxy S III] not-i:
Thanks so much mate. That's what was missing from my 4.4.2 Note 3 mod. Now it works. Awesome :D
[Sprint Samsung Galaxy S III] Chad The Pathfinder:
Is there a way to eliminate the slight lag there is when activating the the flashlight with the toggle? When using the "assistive light" widget the flashlight comes on and goes off instantly.
[Sprint Samsung Galaxy S III] CNexus:
Yeah it's because this one uses an external app...I'm looking into directly invoking the camera flash
[Sprint Samsung Galaxy S III] Unknownforce:
You can, but not without giving SystemUI CAMERA permission, which incidentally breaks the Signature of SystemUI. Which... on a dirty flash, isn't a problem, but on a clean flash, SystemUI won't work. It might be possible to somehow channel it through the framework and back out to another app that does have camera permission, but you'll probably end up with the same effect as using the torch app.
[Sprint Samsung Galaxy S III] CNexus:
Or you can just disable signature checking first and not have to deal with that at all, as well as avoiding having to copy over META-INF and the manifest every time you mod an app.

Or for yet another approach, just resign all system apps with your own keys, then resign future modded apps with those same keys.

tl;dr It's not difficult to avoid that scenario.
[Sprint Samsung Galaxy S III] Unknownforce:
It's not difficult, no, but then your mod is no longer fully compatible with other ROMs that exist from the same device. You could flash it after the first boot, but people that go to use the mod themselves for their own custom ROMs and don't disable the signature checking or sign their own files won't be able to incorporate it into their ROMs.

With apktool now being able to add the files back for you when you compile apks, I find it much easier to stick with the stock system signature and still work within that small limitation of not granting system apps any additional permissions.

But SamsungCamera2 might have a build in method to activate just the light, or it might be possible to inject a new method into to it, since that obviously has CAMERA permissions already.
[Sprint Samsung Galaxy S III] CNexus:
Well it's not like I'm providing a flashable for my goal to be to maintain compatibility with as many roms as possible. And even then 90%+ of roms disable signature checking anyway.

And it would have the same effect if I edit SamsungCamera2 as the toggle would still need to send a broadcast to launch the new method, and doing that would make implementing this mod more convoluted than it needs to be anyway.

I think I'll stick with the direction I was going.
[Sprint Samsung Galaxy S III] Chad The Pathfinder:
This probably wouldn't work but is it possible to somehow have the ROM think that the assistive light widget is activated by touching the flashlight toggle? I have no idea what would be required to do such a thing.
[Sprint Samsung Galaxy S III] not-i:
That's pretty much what the last few posts have been discussing
[Sprint Samsung Galaxy S III] Chad The Pathfinder:
Sorry. I misunderstood thinking they ment how to go straight to whatever the assistive light widget goes to rather than have the toggle turn on the widget.
[Sprint Samsung Galaxy S III] LeoDeos:
Great...

work fine on i9305 4.3

thanks :)

I have also modded SecSettingsProvider.apk and dont use the script on new flash rom or wipe data
[Sprint Samsung Galaxy S III] FeralFire:
[MENTION=4645794]CNexus[/MENTION]

I tried to follow this guide to add this toggle to my Note 3. But, well, I am stuck at the first step itself.

I decompiled my systemUI to find that there is no com folder in there.

Am I doing something wrong? Or is the Note 3 systemUI.apk inherently different?

View attachment 2603376
[Sprint Samsung Galaxy S III] CNexus:
Did you check the "original" folder? Otherwise, try just using apktool directly without a wrapper program like the AdvancedApkTool you seem to be using
[Sprint Samsung Galaxy S III] manufan721:
Did you baksmali? Its in smali files, not in root of apk..
[Sprint Samsung Galaxy S III] CNexus:
I think I got it, and with no complicated procedures/modifications to the existing code...

Inside SecHardwareInterface, there are predefined methods for setting the torch brightness...so just invoking that with the toggle value should do the trick

Will updated tomorrow after I test it
[Sprint Samsung Galaxy S III] Chad The Pathfinder:
Awesome. Let me know if I can help in some way. :thumbup:
[Sprint Samsung Galaxy S III] CNexus:
const v3: string text id

const v4: on drawable id

const v5: off drawable id
[Sprint Samsung Galaxy S III] CNexus:
Ok here it is

Replace the onClick method of the FlashlightQuickSettingButton.smali with the following, then you don't need an external app

.method public onClick(Z)V
.locals 5
.parameter "paramBoolean"

.prologue
.line 29
const/4 v2, 0x0

.line 30
.local v2, localIntent:Landroid/content/Intent;
const/4 v1, 0x0

.line 32
.local v1, bc:Ljava/lang/String;
const/4 v0, 0x2

.line 34
.local v0, activateStatus:I
iget v3, p0, Lcom/android/systemui/statusbar/policy/quicksetting/FlashlightQuickSettingButton;->mFlashlight:I

add-int/lit8 v3, v3, 0x1

iput v3, p0, Lcom/android/systemui/statusbar/policy/quicksetting/FlashlightQuickSettingButton;->mFlashlight:I

.line 36
iget v3, p0, Lcom/android/systemui/statusbar/policy/quicksetting/FlashlightQuickSettingButton;->mFlashlight:I

rem-int/lit8 v3, v3, 0x2

iput v3, p0, Lcom/android/systemui/statusbar/policy/quicksetting/FlashlightQuickSettingButton;->mFlashlight:I

.line 38
iget v3, p0, Lcom/android/systemui/statusbar/policy/quicksetting/FlashlightQuickSettingButton;->mFlashlight:I

const/4 v4, 0x1

if-ne v3, v4, :cond_0

.line 39
const-string v1, "com.sec.samsung.torchwidget.torch_on_3"

.line 40
const/4 v0, 0x1

.line 45
:goto_0
invoke-virtual {p0, v0}, Lcom/android/systemui/statusbar/policy/quicksetting/FlashlightQuickSettingButton;->setActivateStatus(I)V

.line 47
new-instance v2, Landroid/content/Intent;

.end local v2 #localIntent:Landroid/content/Intent;
invoke-direct {v2, v1}, Landroid/content/Intent;->(Ljava/lang/String;)V

.line 49
.restart local v2 #localIntent:Landroid/content/Intent;
iget-object v3, p0, Lcom/android/systemui/statusbar/policy/quicksetting/FlashlightQuickSettingButton;->mContext:Landroid/content/Context;

invoke-virtual {v3, v2}, Landroid/content/Context;->sendBroadcast(Landroid/content/Intent;)V

.line 53
return-void

.line 42
:cond_0
const-string v1, "com.sec.samsung.torchwidget.torch_off"

goto :goto_0
.end method
[Sprint Samsung Galaxy S III] CNexus:
And in case any of you were wondering, NO I did not write that method in smali.

Instead, I cheated. I wrote it in Java, compiled, and then grabbed the resulting smali :D:D
[Sprint Samsung Galaxy S III] Chad The Pathfinder:
Where is the onClick method? Is it in the FlashlightQuickSettingButton.smali?

Edit: I flashed the new zip from the OP and the toggle acts the same way as before, with the slight lag... :eek:
[Sprint Samsung Galaxy S III] CNexus:
The zip in the OP only makes the toggle show up if you've implemented it. It doesn't actually do anything else, or flash already modified files

And yes, replace the onClick method of the FlashlightQuickSettingButton.smali with the code above
[Sprint Samsung Galaxy S III] metalfan78:
I'm working on the SystemUI part right now and after I make the edits and add the files I get this error when I recompile, not sure what it means. Any help would be appreciated.

C:\apktool>apktool b SystemUI

I: Checking whether sources has changed...

I: Smaling...

[139,54] no viable alternative at input '('

Exception in thread "main" brut.androlib.AndrolibException: Could not smali file

: java.io.FileInputStream@572863a9

at brut.androlib.src.DexFileBuilder.addSmaliFile(DexFileBuilder.java:45)

at brut.androlib.src.DexFileBuilder.addSmaliFile(DexFileBuilder.java:33)

at brut.androlib.src.SmaliBuilder.buildFile(SmaliBuilder.java:66)

at brut.androlib.src.SmaliBuilder.build(SmaliBuilder.java:50)

at brut.androlib.src.SmaliBuilder.build(SmaliBuilder.java:37)

at brut.androlib.Androlib.buildSourcesSmali(Androlib.java:256)

at brut.androlib.Androlib.buildSources(Androlib.java:213)

at brut.androlib.Androlib.build(Androlib.java:204)

at brut.androlib.Androlib.build(Androlib.java:176)

at brut.apktool.Main.cmdBuild(Main.java:218)

at brut.apktool.Main.main(Main.java:74)

C:\apktool>

---------- Post added at 07:25 AM ---------- Previous post was at 06:47 AM ----------

Also, when I compiled SecSettings my new one is about 20 mb smaller than original. That doesn't seem right to me.
[Sprint Samsung Galaxy S III] Ohh_Trenton:
Try to replace your flashlightquicksettingbutton onclick method with this one and see if it works

.method public onClick(Z)V
.locals 6

const/4 v2, 0x1

if-nez p1, :cond_2

move v1, v2

:goto_0
iget-boolean v3, p0, Lcom/android/systemui/statusbar/policy/quicksetting/FlashlightQuickSettingButton;->mFlashlight:Z

if-eq v1, v3, :cond_0

iput-boolean v1, p0, Lcom/android/systemui/statusbar/policy/quicksetting/FlashlightQuickSettingButton;->mFlashlight:Z

new-instance v0, Landroid/content/Intent;

const-string v1, "net.cactii.flash2.TOGGLE_FLASHLIGHT"

invoke-direct {v0, v1}, Landroid/content/Intent;-><init>(Ljava/lang/String;)V

const-string v1, "net.cactii.flash2.EXTRA_DISABLE_NOTIFICATION"

const/4 v2, 0x1

invoke-virtual {v0, v1, v2}, Landroid/content/Intent;->putExtra(Ljava/lang/String;Z)Landroid/content/Intent;

iget-object v1, p0, Lcom/android/systemui/statusbar/policy/quicksetting/FlashlightQuickSettingButton;->mContext:Landroid/content/Context;

invoke-virtual {v1, v0}, Landroid/content/Context;->sendBroadcast(Landroid/content/Intent;)V

if-eqz p1, :cond_3

invoke-virtual {p0, v2}, Lcom/android/systemui/statusbar/policy/quicksetting/FlashlightQuickSettingButton;->setActivateStatus(I)V

:cond_0
:goto_1
iget-object v1, p0, Lcom/android/systemui/statusbar/policy/quicksetting/QuickSettingButton;->mContext:Landroid/content/Context;

invoke-virtual {v1}, Landroid/content/Context;->getContentResolver()Landroid/content/ContentResolver;

move-result-object v1

const-string v2, "collapse_panel"

const/4 v3, 0x0

invoke-static {v1, v2, v3}, Landroid/provider/Settings$System;->getInt(Landroid/content/ContentResolver;Ljava/lang/String;I)I

move-result v1

if-eqz v1, :cond_1

iget-object v1, p0, Lcom/android/systemui/statusbar/policy/quicksetting/QuickSettingButton;->mContext:Landroid/content/Context;

const-string v2, "statusbar"

invoke-virtual {v1, v2}, Landroid/content/Context;->getSystemService(Ljava/lang/String;)Ljava/lang/Object;

move-result-object v3

check-cast v3, Landroid/app/StatusBarManager;

invoke-virtual {v3}, Landroid/app/StatusBarManager;->collapsePanels()V

:cond_1
return-void

:cond_2
const/4 v1, 0x0

goto :goto_0

:cond_3
const/4 v2, 0x2

invoke-virtual {p0, v2}, Lcom/android/systemui/statusbar/policy/quicksetting/FlashlightQuickSettingButton;->setActivateStatus(I)V

goto :goto_1
.end method

.method public onLongClick()V
.locals 0

return-void
.end method

I had the same error as you but I replaced it with this one and it works. Just keep in mind to replace those Ids

# text id

const v3, 0x0

# on image id

const v4, 0x0

# off off id

const v5, 0x0

With your own IDS from step 11.
[Sprint Samsung Galaxy S III] metalfan78:
I tried your method, and apktool threw a bunch of errors about system bar notification and system bar settings view. So I decided to decompile and the recompile without making any changes and I got the same errors. I'm not sure what the problem is, because SecSettings compiled fine.
[Sprint Samsung Galaxy S III] Ohh_Trenton:
Ya gotta follow this guide for that.

http://xdaforums.com/showthread.php?t=2264380

That should get you going.
[Sprint Samsung Galaxy S III] metalfan78:
Thanks, I'll give it a try.
[Sprint Samsung Galaxy S III] CNexus:
I'll be posting another update soon to make it even easier...this time you won't need to manually put in your drawable ids, the smali will automatically retrieve the id based on the names of the images it's looking for
[Sprint Samsung Galaxy S III] metalfan78:
I used this to solve my issue, worked perfectly

http://xdaforums.com/showthread.php?t=2549452
[Sprint Samsung Galaxy S III] CNexus:
Nice, good to know
[Sprint Samsung Galaxy S III] metalfan78:
Small issue, when I edit the buttons in settings, the flashlight button is labeled 'flashlight' but in the pulldown it looks like this. And also if I want to bake it into my rom do I just add the tools folder from the enable zip to system?

---------- Post added at 08:00 AM ---------- Previous post was at 07:27 AM ----------

Did I use a wrong id for that?
[Sprint Samsung Galaxy S III] CNexus:
Yes, you used the wrong id and set the text id to one of the drawable ids?
[Sprint Samsung Galaxy S III] metalfan78:
Dammit, that's what I thought. Thanks

---------- Post added at 08:19 AM ---------- Previous post was at 08:06 AM ----------

Fixed, thanks.
[Sprint Samsung Galaxy S III] metalfan78:
I'm still unclear on how to add this to my rom with the need to flash the enabler zip. Any help would be appreciated
[Sprint Samsung Galaxy S III] r_hippy:
You can just add the enable feature

In the ststem/csc/feature.xml file..

There are a few threads on enabling around

This may help you narrow your search down

<CscFeature_Setting_DefNotificationPanelOrder>

Or enable this script to flash during install.
[Sprint Samsung Galaxy S III] CNexus:
Flashlight will automatically show up on clean flash, the system (for us) is already adding it if the smali exists

However if you add any other toggles, those won't show on a clean flash
[Sprint Samsung Galaxy S III] metalfan78:
That's what I have looking for but I can't find the notification panel order in csc features

---------- Post added at 11:12 AM ---------- Previous post was at 11:08 AM ----------

Nevermind, brainfart, I just realized I needed to add the whole thing.
[Sprint Samsung Galaxy S III] CNexus:
MOD UPDATED

==============

- 4.3 and 4.4 zips added

- No need to write down ANY id's anymore. I've made it so that the id's get looked up on the fly by name, so just make sure you don't rename the drawables/string names as per this guide

- Flashlight is super fast now, no need to use an external app
[Sprint Samsung Galaxy S III] metalfan78:
Strange. I pushed to system and this worked, when I built into my rom and flashed I got constant system UI force closes.
[Sprint Samsung Galaxy S III] Mongo23ny:
Awesome, thank you.
[Sprint Samsung Galaxy S III] metalfan78:
Turns out that it was the csc features I added. Now I have csc features flashlight but still need to flash the enabler zip.
[Sprint Samsung Galaxy S III] Chad The Pathfinder:
I've been trying to change my SystemUI.apk following the new instructions but my SystemUI keeps FCing. Am I supposed to delete the old torch.apk of something? Not sure what could be causing the problem since I got it working the old way with no trouble. :confused:
[Sprint Samsung Galaxy S III] CNexus:
Hm..are you copying over the META-INF and AndroidManifest.xml from the original SystemUI over to the new one? And I tested this with the stock SystemUI so it can't be the code...
[Sprint Samsung Galaxy S III] Chad The Pathfinder:
Yes I did that but thats what its acting like. Maybe the new file in the op is conflicting with another SystemUI mod but I don't see how. I'll try to get a logcat tomorrow.
[Sprint Samsung Galaxy S III] CNexus:
Were you able to work this out? I tested on the pure stock systemui before posting and it worked perfectly...

Let me know how it goes.
[Sprint Samsung Galaxy S III] Chad The Pathfinder:
It turns out I've been having trouble with my computer not compiling correctly. Figured it out with a crazy framework-res. I got the problem worked out now so I'll give this a go again over the weekend.
[Sprint Samsung Galaxy S III] antiochasylum:
[MENTION=4645794]CNexus[/MENTION]

I get this upon recompile of the systemui, android 4.4

\Decompiled_apk\SystemUI\smali\com\android\systemui\statusbar\policy\quicksetting\FlashlightQuickSettingButton.smali[22,4] Error for input '.parameter': Invalid directive
..\Decompiled_apk\SystemUI\smali\com\android\systemui\statusbar\policy\quicksetting\FlashlightQuickSettingButton.smali[22,15] mismatched input '"context"' expecting END_METHOD_DIRECTIVE
..\Decompiled_apk\SystemUI\smali\com\android\systemui\statusbar\policy\quicksetting\FlashlightQuickSettingButton.smali[121,4] Error for input '.parameter': Invalid directive
..\Decompiled_apk\SystemUI\smali\com\android\systemui\statusbar\policy\quicksetting\FlashlightQuickSettingButton.smali[121,15] mismatched input '"paramBoolean"' expecting END_METHOD_DIRECTIVE
Exception in thread "main" brut.androlib.AndrolibException: Could not smali file: com/android/systemui/statusbar/policy/quicksetting/FlashlightQuickSettingButton.smali
at brut.androlib.src.SmaliBuilder.buildFile(SmaliBuilder.java:72)
at brut.androlib.src.SmaliBuilder.build(SmaliBuilder.java:56)
at brut.androlib.src.SmaliBuilder.build(SmaliBuilder.java:41)
at brut.androlib.Androlib.buildSourcesSmali(Androlib.java:338)
at brut.androlib.Androlib.buildSources(Androlib.java:299)
at brut.androlib.Androlib.build(Androlib.java:285)
at brut.androlib.Androlib.build(Androlib.java:258)
at brut.apktool.Main.cmdBuild(Main.java:236)
at brut.apktool.Main.main(Main.java:88)
[Sprint Samsung Galaxy S III] Ticklefish:
This is often caused by the version of apktool you're using. If you're using a version of apktool 2, try using apktool 1 instead. Or the other way around.
[Sprint Samsung Galaxy S III] antiochasylum:
I've tried every version, 1.5.1,1.5.2, and the new 2.0 beta 7 and beta 9. Nothing.
[Sprint Samsung Galaxy S III] CNexus:
That error should really not be happening because .parameter is a valid directive....but try deleting it, it shouldn't make a difference

Apktool shouldn't be throwing that error though
[Sprint Samsung Galaxy S III] antiochasylum:
I've got to be doing something wrong. Now this. after deleting those lines...

..\Decompiled_apk\SystemUI\smali\com\android\systemui\statusbar\policy\quicksetting\FlashlightQuickSettingButton.smali[126,15] no viable alternative at input 'localIntent'
..\Decompiled_apk\SystemUI\smali\com\android\systemui\statusbar\policy\quicksetting\FlashlightQuickSettingButton.smali[126,27] no viable alternative at input 'Landroid/content/Intent;'
..\Decompiled_apk\SystemUI\smali\com\android\systemui\statusbar\policy\quicksetting\FlashlightQuickSettingButton.smali[130,15] no viable alternative at input 'bc'
..\Decompiled_apk\SystemUI\smali\com\android\systemui\statusbar\policy\quicksetting\FlashlightQuickSettingButton.smali[130,18] no viable alternative at input 'Ljava/lang/String;'
..\Decompiled_apk\SystemUI\smali\com\android\systemui\statusbar\policy\quicksetting\FlashlightQuickSettingButton.smali[134,15] no viable alternative at input 'activateStatus'
[Nexus 5 Accessories] thor6577:
I found a nice wireless charger online, but due to the fact that I haven't bought a wireless charger before, I have no idea if the specifications it has are any good. Here's a link : http://www.amazon.com/gp/product/B00F9SKJN6/ref=ox_sc_act_title_2?ie=UTF8&psc=1&smid=A1E57UY6AMKO25

What do you guys think?
[Nexus 5 Accessories] johnq54:
I bought the same one. Had it for about a week now, and with no problems charging the phone.

My only issue is trying to find a case for the phone that doesn't slide off the charger. Both spigen cases I have bought, the phone slides off after a few minutes. Without a case, the phone stays on beautifully. However, I like to keep my phone in a case all the time. Any suggestions?
[Nexus 5 Accessories] thor6577:
Try attaching some thin magnets on the surface of the charger. You could alternatively buy some magnet tape and apply that.