yashsingh1/xdaforums huggingface dataset:
[Galaxy Note II Original Android Development] Tungstwenty:
I'm not sure whether this is the explanation for parsePackageLite (the messages don't quite match the ones in the source) but anyway it might mean that some packages won't be possible to identify (apk -> packageName) using that function.

Let's see if the code in XResources can be improved to catch those edge cases and still obtain the package name, if it's not running in the context of an app that indeed doesn't have access to a 3rd package.
[Galaxy Note II Original Android Development] qwerty12:
I've looked and, to be honest, it seems more like a bug in the package itself (as its manifest is using an ID to a string not present in the APK itself [you saw the contents of res/]). Honestly, it's not really a problem, as it doesn't affect anything, really.
[Galaxy Note II Original Android Development] neol23:
Is someone working on Blocking mode statusbar icon mod compatibility for xposed 2.0.2? :)
[Galaxy Note II Original Android Development] jujuburi:
The long sms and call recording mod by Pulser aren't compatible yet for 2.0.2 right? Because I get this,

Sent from my GT-N7100
[Galaxy Note II Original Android Development] rovo89:
Not sure if these are the ones you have installed, but they are updated:

http://www.villainrom.co.uk/forum/index.php?microdownloads/1/fileupdates

http://www.villainrom.co.uk/forum/index.php?microdownloads/3/fileupdates
[Galaxy Note II Original Android Development] jujuburi:
I installed them from the link that Dr.Ketan posted 2 or 3 pages back, which had all the modules listed.

But those links you've provided are working! So which page actually has all the updated modules? I'm sure the one listed in OP is not the updated one, or am I wrong?

Sent from my GT-N7100
[Galaxy Note II Original Android Development] dr.ketan:
That link was given by Rovo only(page 51 first post) , and I have just recheck, it shows its updated for 2.0.*

Yes listed on op (direct attachments) are older.

Actually i am using call recorder from tweakbox.
[Galaxy Note II Original Android Development] rovo89:
For all apps listed there, this is the most up-to-date list:

http://www.villainrom.co.uk/forum/microdownloads/ (or http://www.villainrom.co.uk/forum/forums/xposed_framework_mods/, you will get to the same files).

If you are referring to this post, that's the same links (the list could become incomplete of course after some time).

So could you mention which path you followed to the outdated modules? As most modules have been updated for Xposed 2.0 by now, I'd like to see the outdated copies start vanishing. ;)

EDIT: Ah, now I see what you might mean with "original post". The one in the threads on the download pages? Well, immediately above the attachment, it says " Attached is the LEGACY version of this plugin for Xposed API 2.0 RC2. DO NOT USE THIS VERSION. Use the up-to-date one in the download manager."
[Galaxy Note II Original Android Development] dr.ketan:
@rovo

I think module on op (direct download github) only are outdated

While on repository

disable block mode notification, but that actually still not available for 2.0.2
[Galaxy Note II Original Android Development] pulser_g2:
A user posted an updated version in the comments, so I will update the stored version tomorrow for it.
[Galaxy Note II Original Android Development] _TB_TB_:
"a user", thanks :P
[Galaxy Note II Original Android Development] pulser_g2:
Haha, yeah should teach me from trying to write my hurried replies :D

s/a user/_TB_TB_ :)

BTW I added your modification to the gallery, as you'd not submitted it through that way - could you apply for membership of the Xposed Uploaders group (instructions in the OP or one of the first posts for "developers"), and I'll add that so you can look after your own modification you had made :)

Cheers

P
[Galaxy Note II Original Android Development] dr.ketan:
Ok found user

now thanks to tb_ tb too :)
[Galaxy Note II Original Android Development] :
Dont know if anyone else is having this but a few apps keep force closing when full screen is selected in the dpi app. Email gmail and messaging all eventually force close when full screen selected
[Galaxy Note II Original Android Development] Tungstwenty:
The exception thrown by gmail was:

java.lang.NullPointerException
at com.android.mail.ui.AbstractActivityController.updateAccounts(AbstractActivityController.java:1953)
at com.android.mail.ui.AbstractActivityController.onLoadFinished(AbstractActivityController.java:2013)
at com.android.mail.ui.AbstractActivityController.onLoadFinished(AbstractActivityController.java:120)
at android.app.LoaderManagerImpl$LoaderInfo.callOnLoadFinished(LoaderManager.java:438)
at android.app.LoaderManagerImpl$LoaderInfo.onLoadComplete(LoaderManager.java:406)
at android.content.Loader.deliverResult(Loader.java:125)
at android.content.CursorLoader.deliverResult(CursorLoader.java:88)
at android.content.CursorLoader.deliverResult(CursorLoader.java:42)
at android.content.AsyncTaskLoader.dispatchOnLoadComplete(AsyncTaskLoader.java:236)
at android.content.AsyncTaskLoader$LoadTask.onPostExecute(AsyncTaskLoader.java:76)
at android.os.AsyncTask.finish(AsyncTask.java:602)

Looking at line 1953 there's this code:

iget-object v0, p0, Lcom/android/mail/ui/AbstractActivityController;->[COLOR="Red"]mActionBarView[/COLOR]:Lcom/android/mail/ui/MailActionBarView;

When the window runs in fullscreen there's no action bar, but the app is expecting it and fails.

I don't know if there's much that can be done, unless anyone can suggest something.
[Galaxy Note II Original Android Development] :
It's not a problem it doesn't make much difference anyway. Ive just got to say a massive thank you for all your work. The whole xposed framework and the dpi mods are the best things to happen to android they are so powerful but simple to use.
[Galaxy Note II Original Android Development] DAGr8:
This is not pa this is xposed.

Pa is built from source and not based of touchwiz..

Multi dpi has nothing to do with pa either in fact pa rendered it useless

Rovo: I was saying ..

Android handles the size of the statusbar (as Random example here) by looking at the 3.0dip (size)specified in *.xml

When reducing the dpi in build.prop the dip value becomes scaled (300 to 200 for example then that is what results in poor layout for apps like the dialer where it would only fill 2/3 of the screen)

By changing 3.0dip to 6.0px android 'ignores' the value and does not scale

it results in normal resolution for the dialer..

An xposed mod would be to auto calculate/convert dip to px on the fly so users could run global dpi lower then normal and enjoy full screen apps like the dialer or camera. .

The problem is some very important *.dip are located in dimens.xml

(Resources.arsc)
[Galaxy Note II Original Android Development] appro77:
I've installed Xposed and a couple of modules, namely the Xposed Settings and Swiftkey modules. When I look at the modules in the app they are disabled and I'm seeing the message ""This module was created for Xposed version 2. but due to incompatible changes in version 2.0b2,it has been disabled."

What is causing this? I've installed Xposed on Omega rom that uses the Simplistic Framework. Is this the issue?
[Galaxy Note II Original Android Development] liquidguru:
The version 2.0b2 is an old version. You need to follow the link in the 2nd post of this thread and install the latest version of the Xposed Framework. It will work fine with your Rom

sent from somewhere
[Galaxy Note II Original Android Development] Pax_fr:
Hi and thanks for your work.

AlternateAppPicker is not working on GNII, JB 4.1.2, it conducts some apps to FC when the window open to choose a program, and this windows have not the buttons always / once.

Ex: tag Nfc open this sort of windows, you click (or not) and got a message "Nfc stopped".

No problem with Doubletap but this app is not very much efficient because you double tap instead of tap twice :confused:

Nfc on screen lock/off do not work as well on mine GNII XXDLL4.

Not lucky I guess :angel:
[Galaxy Note II Original Android Development] dyehya:
I would really like to see either the repository or when the in app goes live way down the road be stored in a more categorized format. I don't know if you guys realize this but I have been talking this up to other devs that handle modding numerous devices and several are extremely interested and I see this quickly taking off and don't want to run into the issue of having to find Samsung specific patches and android version specific patches that ain't apply to an updated version like the alternate app picker for 4.1.x is useless in 4.2 and ICS. I worry what that repository will look like when you have hundreds and thousands of modules. No rush on this but I want to make sure you guys are thinking about it and planning like you did when you jumped to 2.0 version.

I am as my title suggests a contributor and my biggest contribution is to talk this up to as many devs I know most of which are well known and have huge followings. My goal is for this to be THE method of theming, app modding, and other changes.

I am a living success as I installed the beta Tapatalk HD which is designed for 7" screens and even though my DPI on my S3 is lowered from 320dpi to 240dpi it was still huge. I was able to go into the App Settings module within seconds and try a few different settings until I found the size I was happy with.

So instead of decompiling, modding, recompiling, etc. I was done in 30 sec. They also just updated it again... did I have to uninstall my modded version... nope Play Store updates and everything works as before.

My biggest suggestion is think bigger than you thought big was as this is useful for ALL android devices and there are more and more daily. As this gets adopted you won't be able to have one chat regarding all these different mod bugs but it will be as it is now with each ROM having its own thread even though it is just a collection of modules.

Remind me not to message when I'm half asleep I tend to rant...
[Galaxy Note II Original Android Development] rovo89:
@dyehya: Thanks! I do agree with many points, but also have to mention some things from the developer perspective. I will reply in detail later.

Please read this post: http://xdaforums.com/showpost.php?p=36215483&postcount=402

1. Changing everything to px will only work properly for the same screen size.

2. The factor to calculate px from dpi is the density, and this is exactly what you can change with the App Settings module. The calculation formula should also be used for the dimens.xml, so it should be universal enough.

I don't think this is different from what you will achieve with PA. Of course, as they can change the source as they wish, they will probably not use hardcoded values in the first place, avoiding this question completely.
[Galaxy Note II Original Android Development] EdgaBimbam:
My feedback about "Cosmetic Device Status Normal Modification" mod. For me it is working on DLL7 stock firmware with perseus kernel :)
[Galaxy Note II Original Android Development] jujuburi:
Actually those links are different. The first one will redirect to a page like this,

And the second link is this,

So the latter one is more updated than the first one.

Sent from my GT-N7100
[Galaxy Note II Original Android Development] Tungstwenty:
The 1st link is for the "Top 10 newest downloads".

But if you select from the right one of the categories (User Interface Modifications, App Modifications, System Modifications), you are able to access the whole list.
[Galaxy Note II Original Android Development] GreenDroid:
if it is possible to make a module that the removes the annoying instructions on how to clear defaults, each time a default program is set that would just add to the awesomeness of this. thumbs UP

Sendt fra min GT-I9300 med Tapatalk2
[Galaxy Note II Original Android Development] Nuvolaz:
There is a module for whatsapp that let send original size photos?
[Galaxy Note II Original Android Development] DAGr8:
I am a bit out of the loop here since I havent tried latest version but if this would work just like PA then why is sustemui not FCing when you ask it to go in tablet mode ? it should since its missing the proper ressources .. instead ( and in a way its a good thing) it uses the existing ressources and scales them down, the problem is even if the ressources are added it still scales the 'standard layout' instead of using the tablet ressources ... thats another reason I conclude this aint working like pa ..

yes that is exactly what I meant 'per specific app' , 'app per dpi' 'layout per apps' I dont think the current module does all that (as pa does)

1. if my native is 320 dpi , then my values in dip for my stock dialer (random example ) will be different then the ones for a phone with native of 240 . if you hardcode specific *.px in the module ofc its not going to work . or am I missing something here ?

I use a little script here that targets dip values in folders and change them to px I can tell them to target whatever dpi I want . of course I need to extract ressources that is why I meant im not sure how this is going to work on Xposed . but if you have the aboility to scale down whats inside ressources.arsc then 'in theory' the same sort of script I use coudl be added to a module and do it on the fly in the actual phone , or woudl that be to much work ?

I apologize in advanced for not reading the whole thread in between post (thx for linking me ) since you seem to have covered pretty much all side of this , just wanted to shed some light on how I been doing this for last 2 years and maybe make it availbale much easier for everyone since making them apps one by one , even with this script is lots of work ..
[Galaxy Note II Original Android Development] rascal123:
Im a complete noob now..I download the module from vilain website however it is a zip file and no apks in it...how do I install the module into the phone
[Galaxy Note II Original Android Development] dr.ketan:
Rename it with extension. apk then install. It's browser issue.
[Galaxy Note II Original Android Development] DAGr8:
Well cm10.1 ie android 4.2 doesn't allow tablet mode like we got use to .. so that trick is to allow it..

Aosp systemui pre 4.2 had tablet mod ressources.. so no hack needed.. and no pa 's system ui pre 4.2 was not different from cm's stricktly tablet ressources speaking of course ...

I based of touch wiz tablet in order to add the missing ressources to my systemui and afaik I tried all possible combination to trigger it using xposed.. but I already have a way around that by forcing tablet at any dpi then scaling it using your module ...

Edit:

That method you linked me to.. All I did was change the hex value that triggers system ui.. instead of looking for 160 or less its now looking for 320 or less.. much simpler and similar result...

When one lowers global dpi that is when systemui gets triggered in tablet mod.. unless you hack phonewindowmanager .. maybe bypassing this we could make it work , ie the module would apply the hack to policy.jar when someone tries to trigger tablet mode on systemui and undo it accordingly .. ofc reboot woudl def be required .. andthat would only work on hybrid 'modified systemui' , come to think of it maybe I coudl make my first mod for xposed to enable the tablet ressources on any TW systemui ..
[Galaxy Note II Original Android Development] _TB_TB_:
How did you hook the PhoneWindowManager? It looks like you used "handleLoadPackage()", but with which package?

I tried different combinations, "initZygote()", etc., still no success (and no errors...)
[Galaxy Note II Original Android Development] Tungstwenty:
Either handle package "android", or if that happens too late do it on initZygote and it will apply to all processes, although regular apps might not execute that code and it only happens in the system_server process ("android" package).
[Galaxy Note II Original Android Development] rovo89:
Hooking it in initZygote() should work as Tungstwenty said. handleLoadPackage() for "android", although I'm not sure if this is works properly only with 2.1 (not released yet), where the callback is called earlier in the process.

@DAGr8: It seems that we have quite different views on the topic. My impression is that you are mainly interested in tablet mode for the SystemUI. This is not the target of the module, and it's not what is meant with "tablet" in the configuration. The module contains settings that can be used for any app, whereas you are targeting more the framework with specific changes.

Talking about that, I find it easier and more obvious to set mSystemNavBar directly than changing the criteria when it is set. As I have shown you, this triggers tablet mode just fine if it exists. No need to patch any files, which reverses the idea behind Xposed.

I have the feeling that our discussion is going nowhere. If you can list in detail which changes you make manually, we could probably find a way to do the same (or something with the same effct) in Xposed.
[Galaxy Note II Original Android Development] pulser_g2:
Afraid the latter one (the SD switch) cannot be put into an APK as far as I can see, as that is a custom kernel... OK yes someone could probably write an APK that flashes a kernel, but that's not what we're talking about here...

Other one is probably possible, would require 2 APK installs though :)
[Galaxy Note II Original Android Development] Tungstwenty:
Actually, a single APK should suffice.

It would be a similar approach to the Keyboard 4.2 mod I shared before:

- one of the classes is for the UI used when the mod is launched as any other app (in my case it's for selecting the language you want and saving that on a preferences file)

- a different class from the same APK is the mod itself, which is injected in the execution of the target process, loads the preferences defined in the UI, and acts accordingly

Let me know if you need any help following the sources.
[Galaxy Note II Original Android Development] :
http://www.modaco.com/topic/358494-lj1-note-2-multi-window-tool/ This is another thread on the multi window tool that should work with a bit of jiggering
[Galaxy Note II Original Android Development] pulser_g2:
Ah, I didn't intend to have my own UI - I was thinking mod apk to patch framework, and separately install their little app...?
[Galaxy Note II Original Android Development] Tungstwenty:
Ah, silly me :o

Provided you modify the framework to still read the expected settings created by the existing APK, there's no need to reimplement it :)

On a related note, this feature can only be applied on a ROM that already has that feature - it's merely allowing extra apps to be part of it and a few other tweaks but not entirely adding the feature where it's not present at all. Right?
[Galaxy Note II Original Android Development] pulser_g2:
Not necessarily, I was planning to make an enabler for multi view on other devices... I know on my S2 I was able to enable it using some code hack... So xposed could also force enable it on unsupported devices.

The tweak here just lets you add any apps you choose to the list of available multitasking apps.
[Galaxy Note II Original Android Development] iakovidis:
I use it a few days now. Call record from pulser_g2 works like a charm

I also installed tweakbox from rovo89 and i use it for skip tracks with volume buttons ( working ) , change notification bar color ( working ).

I also tried signal bars but its not working ( shows just empty bars , phone working )

I have to admit , this thing made me think twice about diving into developing. But my time is extremely limited :(

Excellent job guys
[Galaxy Note II Original Android Development] dr.ketan:
Have you tried SIP ?

I cudn't find option on phone UI
[Galaxy Note II Original Android Development] pulser_g2:
I have SIP here natively...

Perhaps I need to enable it for anyone without it on their phone app?

Open phone, hit menu, settings, should be down at the bottom
[Galaxy Note II Original Android Development] dr.ketan:
Yes, I have already added account too.

But there is no sip options while on dialling, I have To select manually. I mean to say there is no shortcut like video call /record menu while on dialling screen.
[Galaxy Note II Original Android Development] pulser_g2:
Oh I see... Unfortunately I do not have any SIP account I can make outbound calls on.

I am not sure what the expected behaviour is here... Should it prompt the user? I'm sure you can pick what you want to do, as I recall choosing "ask me for every call", and I'm fairly certain I saw a pop up after dialing, asking if it should use cellular or IP...
[Galaxy Note II Original Android Development] Tungstwenty:
I remember that rovo inserted a hack in Tweakbox (snippet here) to allow using SIP.

But I also don't have a clue about what the expected behavior is as I never used SIP.

EDIT: I see dr.ketan's point now. With the tweak active, I have the options "Accounts" and "Use internet calling: always prompt / for all calls / only for internet calls" on the Dialer settings. But on the main dialer screen, there's no explicit button to dial using the SIP account. Only if the setting is on Always Prompt will it ask when pressing the dial button. I'm not sure what "internet calls" means, i.e. how the dialer knows that your destination number is an internet call.
[Galaxy Note II Original Android Development] Lennyuk:
Ignore this, I am an idiot today!
[Galaxy Note II Original Android Development] dr.ketan:
Yes, that's issue. If I have to keep option to select from sip or mobile it pop up every time before dialling

If there is shortcut like video call is available to call from sip it would be great, but anyway I can understand limitations and one can't expect everything own way.

Anyway thanking you for great app.
[Galaxy Note II Original Android Development] :
Excuse another noob question but is there anyway this could be used to let stock rom support themes? I like the op am very happy with twizz on note 2 but a lot of people install custom roms just to support themes.
[Galaxy Note II Original Android Development] rovo89:
It depends what exactly you want to theme. It's possible to exchange icons etc. easily. You can manipulate existing layouts with Java commands after they have been loaded from the resources. And replacing complete layouts is also possible, but there are some hurdles and it's also against the philosophy to create patches rather than replacing things as a whole. I'm not sure what else themers would touch. Some things are too deeply integrated into native code which cannot be patched by Xposed. With some concrete examples of what should be changed, I think I could give a better answer.
[Galaxy Note II Original Android Development] dr.ketan:
Yes there are three option available to use SIP call (it is there in stock too)

-For all calls when network available - That dial all call with SIP

-Only for internet call - It dials all regular call by mobile, may be some internet numbers can be detected by this, but regular numbers are always been dialed from mobile network

-Ask foe every call - this will popup at dialing every number.

So, I was saying if any shortcut available on dialling screen (like Simple call and video call available) would be great. We can select during call what to use simple call/video call/SIP.
[Galaxy Note II Original Android Development] grgsiocl:
IP call can be added also on the seccontacts.apk & secphone.apk along with other buttons, so that it is easier for using (Only needs to be editied some smali files) ! It is already available in lidroid ROM!