yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] egingell:
I have no idea. There are way too many Activities flying around to pinpoint exactly where. If it were mine, I'd wrap that line in a try...catch and log variables.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[Xposed Framework Modules] RadarNyan:
ActivityForceNewTask 1.7 update breaks XHaloFloatingWindow :(

Back to 1.6.1, please fix this. They're both good module I don't want to give up any one of them.
[Xposed Framework Modules] Pkt_Lnt:
Enable logging and whitelist it!

This module give YOU the power to control it, it is not a bug, only you can "fix" it.
[Xposed Framework Modules] GermainZ:
Try the attached version please.

I don't see how without manually adding SuperSU/Superuser/etc myself, which I don't want to do (if there's something I'm missing and that could be used to detect what shouldn't be changed, I'd be glad to hear suggestions.) But then again I recommend using the whitelist. :D
[Xposed Framework Modules] egingell:
Well I'm not getting the error, just debug noise ("your package name String: target package name/target activity name").

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[Xposed Framework Modules] _jis_:
Thank you for very useful module!

I am using it without any problem, but I am getting these lines in Xposed Debug Log on my Samsung Galaxy Note II stock ROM 4.1.2. Are they indicating any problem?

23.3.2014 0:00:53 UTC
Loading Xposed v42 (for com.android.commands.am.Am)...
Loading modules from /data/app/com.germainz.activityforcenewtask-2.apk
Loading class com.germainz.activityforcenewtask.XposedMod
java.lang.NullPointerException
at de.robv.android.xposed.XposedHelpers.callMethod(XposedHelpers.java:917)
at com.germainz.activityforcenewtask.XposedMod$1.afterHookedMethod(XposedMod.java:44)
at de.robv.android.xposed.XposedBridge.handleHookedMethod(XposedBridge.java:561)
at com.android.server.am.ActivityRecord.<init>(Native Method)
at com.android.server.am.ActivityStack.startActivityLocked(ActivityStack.java:3307)
at com.android.server.am.ActivityStack.startActivityMayWait(ActivityStack.java:3927)
at com.android.server.am.ActivityManagerService.startActivity(ActivityManagerService.java:2682)
at android.app.ActivityManagerNative.onTransact(ActivityManagerNative.java:148)
at com.android.server.am.ActivityManagerService.onTransact(ActivityManagerService.java:1740)
at android.os.Binder.execTransact(Binder.java:367)
at dalvik.system.NativeStart.run(Native Method)
[Xposed Framework Modules] GermainZ:
It's only happening once at boot time right? Probably because there's still no activity thread at that stage, I guess. Nothing to be worried about, but it could be handled better.

Are you using the latest version, though?
[Xposed Framework Modules] _jis_:
Yes, I asked, because it didn't happening in previous versions of ActivityForceNewTask. I know this, because I have backed up old Xposed Debug Logs and there wasn't such a lines from ActivityForceNewTask. Debug Log should be dedicated just for errors I think.

Yes. :)

OT about Xposed Debug Log:

It is a little bit of topic, but it is a pity that Xposed Debug Log doesn't contain version for every Xposed module by design.

Another Xposed Debug Log glitch is that after some restarts Log is clean from any module messages when it shouldn't be, because I didn't changed any installed module settings. See this example:

22.3.2014 19:16:59 UTC
Loading Xposed v42 (for Zygote)...
Loading modules from /data/app/uk.co.villainrom.pulser.fivebyfourlauncher-1.apk
Loading class uk.co.villainrom.pulser.fivebyfourlauncher.FiveByFourLauncher
Loading modules from /data/app/ds.cpuoverlay-1.apk
Loading class ds.cpuoverlay.xposed.XposedHooks
[COLOR="Red"]CoolTool: hook statusbar methods
CoolTool: Hook layouts
CoolTool: Hook layouts
CoolTool: hook cooltool methods
CoolTool: App.onCreate hooked[/COLOR]
-----------------
22.3.2014 19:22:36 UTC
Loading Xposed v42 (for com.android.commands.am.Am)...
Loading modules from /data/app/uk.co.villainrom.pulser.fivebyfourlauncher-1.apk
Loading class uk.co.villainrom.pulser.fivebyfourlauncher.FiveByFourLauncher
Loading modules from /data/app/ds.cpuoverlay-1.apk
Loading class ds.cpuoverlay.xposed.XposedHooks
-----------------
22.3.2014 19:48:49 UTC
Loading Xposed v42 (for Zygote)...
Loading modules from /data/app/uk.co.villainrom.pulser.fivebyfourlauncher-1.apk
Loading class uk.co.villainrom.pulser.fivebyfourlauncher.FiveByFourLauncher
Loading modules from /data/app/ds.cpuoverlay-1.apk
Loading class ds.cpuoverlay.xposed.XposedHooks
[COLOR="red"]CoolTool: hook statusbar methods
CoolTool: Hook layouts
CoolTool: Hook layouts
CoolTool: hook cooltool methods
CoolTool: App.onCreate hooked
CoolTool: Hook layouts[/COLOR]
[Xposed Framework Modules] RadarNyan:
Works Perfectly with XHalo and doesn't appears to "overkill" (so may settings in Recent Apps view…) as 1.7, cheers
[Xposed Framework Modules] GermainZ:
Sorry, I misspoke. I meant to ask if you were using the version posted a few posts above yours, here. It's not the one in the repo.

That's by design, the log will be cleared (renamed, actually) on boot if it's bigger than 20K. If it's a different issue you might want to report that in the Xposed Framework thread, though.

Good to know, thanks for reporting and testing. I'll push an update when I get some other things checked (see above.)
[Xposed Framework Modules] _jis_:
You guessed it right, I meant the latest version from repo... So I just installed the latest version posted here and Xposed Debug Log is now clean. :)

-----------------
23.3.2014 17:39:50 UTC
Loading Xposed v46 (for Zygote)...
Running ROM 'JZO54K.N7100XXDME6' with fingerprint 'samsung/t03gxx/t03g:4.1.2/JZO54K/N7100XXDME6:user/release-keys'
Loading modules from /data/app/hk.valenta.completeactionplus-2.apk
Loading class hk.valenta.completeactionplus.XCompleteActionPlus
Loading modules from /data/app/uk.co.villainrom.pulser.fivebyfourlauncher-1.apk
Loading class uk.co.villainrom.pulser.fivebyfourlauncher.FiveByFourLauncher
Loading modules from /data/app/com.ugglynoodle.allnotificationsexpanded-1.apk
Loading class com.ugglynoodle.allnotificationsexpanded.AllNotificationsExpanded
Loading modules from /data/app/de.robv.android.xposed.mods.appsettings-1.apk
Loading class de.robv.android.xposed.mods.appsettings.XposedMod
Loading modules from /data/app/com.germainz.crappalinks-2.apk
Loading class com.germainz.crappalinks.CrappaLinks
Loading modules from /data/app/com.greenbattery-1.apk
Loading class com.dully79.xposed.mods.batteryreplacement.BatteryReplacement
Loading modules from /data/app/com.oasisfeng.greenify-1.apk
Loading class com.oasisfeng.greenify.pro.FrameworkPatch
Loading modules from /data/app/pk.qwerty12.playstorelinkinappinfo-1.apk
Loading class pk.qwerty12.playstorelinkinappinfo.PlayStoreLinkInAppInfo
Loading modules from /data/app/com.mohammadag.burnttoast-2.apk
Loading class com.mohammadag.burnttoast.XposedMod
Loading modules from /data/app/com.germainz.activityforcenewtask-1.apk
Loading class com.germainz.activityforcenewtask.XposedMod
Loading modules from /data/app/com.germainz.stopswitchdelay-2.apk
Loading class com.germainz.stopswitchdelay.XposedMod
Loading modules from /data/app/com.mohammadag.smoothsystemprogressbars-2.apk
Loading class com.mohammadag.smoothsystemprogressbars.SmoothSystemPBar
Loading modules from /data/app/ma.wanam.youtubeadaway-2.apk
Loading class ma.wanam.youtubeadaway.Xposed

Ok, I'll.

Thank you very much.
[Xposed Framework Modules] GermainZ:
Update:

This is the same as the version posted a few posts above, except for the translations.
[Xposed Framework Modules] claytonjn:
[MENTION=4775688]GermainZ[/MENTION]

People have started complaining in the SuperSU thread about it not working properly, which was caused by this module. I know you've made it VERY clear that you recommend whitelist mode, you've provided instructions how to fix SuperSU in blacklist mode, etc but obviously people aren't paying attention to that. I guess I shouldn't still be surprised that people blindly install whatever without reading anything, but I digress.

Anyways, my concern is that Chainfire will continue to get complaints in his thread, in the Play Store, etc due to this module. I think perhaps it would be best if you remove the whitelist/blacklist modes and just have the app always and only work in whitelist mode. Although I know there would be a slight performance hit in parsing the whitelist and it would be a little more work for users to set up, I don't think there are many cases where the user wouldn't have to blacklist anything, and forcing them to add things will force them to learn more about how it works. Plus, they would hopefully remember whitelisting an app and would disable the module before complaining to the respective app developer.

I think this would stop a lot of the complaints in this thread, and it should definitely keep Chainfire and other app developers from getting complaints for things they cannot fix. Since you so strongly recommend whitelist mode anyway you might as well make the decision that the app will only work that way.
[Xposed Framework Modules] GermainZ:
This is version 1.9. I've removed the filtering options in this version. ActivityForceNewTask will now do nothing by default, you have to use the whitelist (now known as "Enabled Components") to enable activities you want to launch in a new task. I've updated the OP to reflect this, but haven't uploaded 1.9 to the Xposed repo yet.

Please test for a bit to ensure it still works as intended and no minor changes should be made before I upload it to the repo. Thanks. :)

EDIT: You don't really have to, but you can clear the app's data if you want to get rid of now unused entries.
[Xposed Framework Modules] defim:
[MENTION=4775688]GermainZ[/MENTION] I'm using now version 1.6.1 which works great with SuperSU. What's the advanced of later versions? Had it a built in b/w list? What's the cause that SuperSU has no problems with the old version?
[Xposed Framework Modules] claytonjn:
I would guess it's this in the changelog:

Different hook, the previous one didn't catch all new activities.

I'm guessing the new hook is fixing other apps but breaking that particular aspect of SuperSU.
[Xposed Framework Modules] Ja_som:
Can you please update your strings, so we can translate them before you release v1.9 to repo?

Thanks :)

Sent from my tablet. Odoslané z môjho tabletu.
[Xposed Framework Modules] GermainZ:
1.6 only hooked Activity.startActivity(...) when there are other ways to start an activity.

Done, thanks. :)
[Xposed Framework Modules] neyenlives:
Man I have been running this a couple weeks and it increased my battery utilization by like double. Obviously this has to do with the device using more active memory to maintain all the extra open processes. Had to disable for now. Thanks for the development though, I like the concept.
[Xposed Framework Modules] jacknicholson:
All seems well on my end.

Ideally, you'd be running those processes anyway -- you're just able to see the activity in your recents list now. That said, trying the (now mandatory) whitelist can't hurt your odds.
[Xposed Framework Modules] neyenlives:
Yeah I use my device, I don't run apps or actively cancel tasks like all the "free memory" whores of the Windows XP pc generation. I believe in using whats there as a proper OS will manage memory effectively for you. I am gaging this purely on battery stats with no changes to usage other than enabling this module in xposed.
[Xposed Framework Modules] GermainZ:
Update:

I suppose that would be possible if you used no filtering or the blacklist. That being said, not a lot of info is provided, so it could be circumstantial/caused by something else, since battery consumption depends on many factors (apps, services, coverage, foreground/background usage, etc.) You can try the new version if you want.
[Xposed Framework Modules] chrisb906:
How is this used?
[Xposed Framework Modules] GermainZ:
Pushed 1.9.1 to the repo. This is a rebuild of 1.9 as that wasn't working as intended for some reason.

After reading the OP, which part(s) don't you understand?
[Xposed Framework Modules] Pkt_Lnt:
Explained here.
[Xposed Framework Modules] RadarNyan:
Why whitelist only??

I understand it is preferred to use whitelist, but it would require going to the configure page every time I face a unexpected situation (an app opens another app's activity inside its own task) and That would be such a pain in the ass…

On the other hands, this method causing unexpected behavior of an app rarely happens, that's why I have been always using none filter and only disable this module through the quick switch in configure page (as you said before a whitelist/blacklist needs an extra step) when necessary.

But how do I use this module is not the point. I mean, if nearly all apps works perfectly and only a few apps doesn't behave as usual, it would be much more easier to maintenance a blacklist than whitelist We can even implant some build-in blacklist entries for new users providing a better experience. On the other hand, the method used now (whitelist and whitelist only) would take no effect at all by default which may very confuse new users, and with all due respect, not everyone understands which activity belongs to which app, seriously.

So please, don't take the old filter selections away, at least keep the blacklist. If you insist to use whitelist (well, it's your app anyway, your app your right), just make your prefered method as default value, everyone's happy.
[Xposed Framework Modules] defim:
Just use version 1.6.1, works great for me
[Xposed Framework Modules] chrisb906:
1.6.1 doesn't work
[Xposed Framework Modules] GermainZ:
When my module can break other apps and causes users to complain to those apps' developers, it's rather obvious that not everyone is happy, and it would be inconsiderate from my part to leave that feature. It's mostly the user's fault, yes, but that doesn't mean I can blame the users and move on when it is my module that's causing these complaints.

As for adding a static blacklist for problematic components myself inside the module, that won't happen. It makes things worse because it would then be expected that the module works flawlessly, and it would become my responsibility to test every other app out there. I don't want that.

That's not to say I'm against something that makes it easier for users. I'm not, if it works and doesn't cause (silent) breakage. So if any of you have suggestions to bring back the other modes, backed up by research/documentation/code, I'd be happy to have a look.

Is the whitelist a pain in the ass to use as you say? Well, it might require more effort but the log makes that as easy as it can be. Besides, with the newest version, the log will only show activities that have been started without FLAG_ACTIVITY_NEW_TASK set, so it should be much cleaner and easier to use as well. I'm also willing to add anything that would make using the app easier, if there are suggestions.
[Xposed Framework Modules] chrisb906:
tried this with HTC One xl running PA beta 2. Can't get it to operate
[Xposed Framework Modules] max229:
Sorry but the new white list only feature is a real step in the wrong direction in my opinion.

Sent via mobile
[Xposed Framework Modules] chrisb906:
I'm not dissing your dev skills.. Just letting u know that this module isn't compatible with my device and rom. If u would like a log cat I can provide one. I think the module caused a soft reboot. I didn't get a logcat then though.

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

I just didn't understand why I wasn't able to open an app inside another. I did read the op
[Xposed Framework Modules] GermainZ:
See posts above.

I don't understand your question. I suppose you didn't configure the module, though.
[Xposed Framework Modules] chrisb906:
Yes. It was configured. Are u supposed to be able to launch an app inside another with this module? That was my assumption.
[Xposed Framework Modules] GermainZ:
No, see the picture in the OP. I can't explain it any better than that.
[Xposed Framework Modules] chrisb906:
OK. Thanks
[Xposed Framework Modules] GermainZ:
As I've said above, the reason for removing the blacklist was that it's affecting other developers by having unaware users complain to them/throw low ratings, and I didn't want that. That being said, I'm all for what's easier for the user without those side effects, which is why I've been trying multiple ideas (and multiple methods for each) to try and get rid of those.

I think 2.0 will be usable with the blacklist without affecting other apps (I've tested it with all the previous known issues and none of them are occurring.) I'm attaching a beta to this post for you guys to test, please report any issues and leave your feedback.

Translators, please send an update when you can.

Changes:

Ignore activities that are launched by their own apps;

Added filtering options back. You can choose between the whitelist and the blacklist, but the no filtering option has been removed;

Added help dialogs for the whitelist/blacklist/log;

Bug fix: duplicate log entries when returning to the app with the log viewer open.

Other minor changes: use icons for action bar items, reorder preferences.

You need to clear the app's data.

Also pasting a commit message here since it has some extra info and I'm too lazy to reword it:

If everything works as intended, I'll push this update to the repo in a day or two. :)
[Xposed Framework Modules] kotey:
It works great!

I was going to complaint about several things, but seems all that was fixed in v2.0. I'm going to list it anyway:

1. Blacklist is the way. I have 600+ apps. Probably more than half will spawn new tasks. Whitelisting each app will simply not do.

2. v1.6.1 works flawlessly. New hook introduced in v1.7-1.81 requires blacklisting "Android System" otherwise I'll see the ugly "choose default action" screen in addition to parent task and new task. I like the old hook method better.

Both seems fixed in 2.0, yay!

p/s: btw, app seems grew another 10kb in size (one third old size). are there debug codes or something? To me v2.0 = v1.6.1 only bigger :p
[Xposed Framework Modules] GermainZ:
Action bar icons. ;)
[Xposed Framework Modules] jfriend33:
So I know on the Droid Maxx when you have the long press recent to enable menu key, it doesn't always show you the correct list of recent apps. You have to hit home then recent to see the correct list.

Would this app fix this? I guess I am still slightly confused on what this module does.
[Xposed Framework Modules] claytonjn:
No, this app wouldn't fix this.

-Sent from my Developer Edition Galaxy S4 using Tapatalk
[Java for Android App Development] searayman:
I have a navigationDrawer that I am implementing for the first time, and each time I close the navigationDrawer without selecting an option in the listVIew it reloads a fragment.... I need help on how to reorganize my code so the drawer can close without reloading the fragments each time.

public class MainDraw extends FragmentActivity {
final String[] data ={"Statistics","Discover","three"};
final String[] fragments ={
"com.beerportfolio.beerportfoliopro.StatisticsPage",
"com.beerportfolio.beerportfoliopro.Discover",
"com.beerportfolio.beerportfoliopro.FragmentThree"};
@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.fragment_main);

ArrayAdapter<String> adapter = new ArrayAdapter<String>(getActionBar().getThemedContext(), android.R.layout.simple_list_item_1, data);

final DrawerLayout drawer = (DrawerLayout)findViewById(R.id.drawer_layout);

final ListView navList = (ListView) findViewById(R.id.drawer);
navList.setAdapter(adapter);

navList.setOnItemClickListener(new AdapterView.OnItemClickListener(){

@Override
public void onItemClick(AdapterView<?> parent, View view, final int pos,long id){
drawer.setDrawerListener( new DrawerLayout.SimpleDrawerListener(){

@Override
public void onDrawerClosed(View drawerView){
super.onDrawerClosed(drawerView);
FragmentTransaction tx = getSupportFragmentManager().beginTransaction();
tx.replace(R.id.main, Fragment.instantiate(MainDraw.this, fragments[pos]));
tx.commit();

}

});

drawer.closeDrawer(navList);

}
});

FragmentTransaction tx = getSupportFragmentManager().beginTransaction();
tx.replace(R.id.main,Fragment.instantiate(MainDraw.this, fragments[0]));
tx.commit();

}

}
[Verizon Samsung Galaxy Note II] z4fir:
I would like a ROM that utilizes the full potential of the speakers for loud music playback. I found this feature only on stock ROMS for some reason but I don't really like stock ROMS over Vanilla ROMS. So if it be is there a ROM that is stable that also isn't stock and has loud speakers with loaders of custom settings like the PAC Man ROM and many others?
[Verizon Samsung Galaxy Note II] MunkinDrunky:
Maybe rephrase your title question so this thread doesn't get closed for "which is best rom" category. I forget but some roms have audio mods for sound boost (look for something like viper or aroma features which add sound boosters and settings) and or you can use a kernel with such options (usually with the use of a kernel settings app that allows you to control sound levels only supported for that kernel)

See my signature I use what's there and I've liked my audio options. Use that as a starting reference maybe.
[Verizon Samsung Galaxy Note II] Naddict:
As XDA is not a support site, members are expected to do their own, independent research and read was is offered in the development sections.

Try them all, all are good and stable.
[General Questions and Answers] ryz4eva:
Hi guys

Just wondered if anybody has been able to get fitbit data into tasker? I want to be able to store steps taken and calories burnt into a variable if thats possible
[Sprint Samsung Galaxy S 4 General] ChadH42:
Let's hope this is true...

http://www.androidcentral.com/inter...axy-s4-will-see-kitkat-update-starting-feb-13
[Sprint Samsung Galaxy S 4 General] arys64:
Time has come

It has been installed already in some devices:

http://xdaforums.com/showpost.php?p=50288096&postcount=2
[Galaxy S III Q&A, Help & Troubleshooting] djpat16:
anyone know how this happen?

my GS3 is only 16gb, but when i checked imei.info, it says 32768mb on built in memory. the first owner also told me that when he installed a 32gb microsd card in this unit, his files exceeded 50gb. not sure if this is a glitch or something, but i really wanna know if i can use the whole 32gb.

without the sd card, my phone is only 16gb (sd card wont work anymore, its a sandisk class 4 32gb)
[General Topics] krismc:
hi guys i have a brand new boxed etc (obviously as its new lol)

imate k jam for sale

any offers pref from uk before i put it up for sale elsewhere?
[Nexus 5 Q&A, Help & Troubleshooting] edved:
I have through time noticed my phone being quite hot to the touch while it's being charged. Be it while in it's (condom) case or lying inadvertently underdeath my pillow while I sleep. My battery life was never great, but was sufficient, but I'm afraid now that it's at about %50-60 of what it once was.

I haven't treated this phone any differentyl than I have the other phones I've previously owned, but the durability of this battery is suspect! I'd love to get a battery replacement for it, but I don't think that's an option at this point.

Anyone else notice this? I've read another post where someone else noticed similar results with their battery life while charging their phone and playing games.
[Nexus 5 Q&A, Help & Troubleshooting] comscier:
First of all, all smartphones gets hot while playing games and charging at the same time.

And charging the phone do generate small amount of heat, so do not put it underneath your pillow while charging. (shouldn't be hot to touch though)

If you are not doing anything mention above and the battery is still getting dangerously hot while charging, contact Google customer service (if its from play store) or your carrier.

*Do not use third party charger if possible.
[Nexus 5 Q&A, Help & Troubleshooting] edved:
Uh, gee. Thanks for the in-depth analysis!

G.
[Nexus 5 Q&A, Help & Troubleshooting] danarama:
If anyone is going to help you now, i'd be amazed. Ever heard the phrase "don't bite the hand that feeds you"?