yashsingh1/xdaforums huggingface dataset:
[Galaxy Note II Original Android Development] pulser_g2:
That's a combined WIP. Debugging - the best way is to use

XposedBridge.log("Message here");

That will be written to /data/xposed/debug.log

You should make loads of them, before and after each line, and you can be sure your code is being seen and run.

That's the basic way, I think there's a better way posted by tungstwenty in the thread I linked in the OP (towards the end?)
[Galaxy Note II Original Android Development] DirkStorck:
Thank you. Hope I will have time at the weekend to look into it. That whole framework sounds very interesting :)

Send from my Omega ROM powered SGS3 :)
[Galaxy Note II Original Android Development] Tungstwenty:
You're right.

Only recently did I find a way to directly debug it; before that it was through log messages as you suggested :)

Check this post for a much better way to debug.
[Galaxy Note II Original Android Development] Tungstwenty:
MOD - Additional languages for Android 4.2 keyboard

Here's my first mod contribution for the collection :)

It injects into the Android 4.2 keyboard an additional language resource of your choosing so you have dictionary and swipe support for it.

The available languages are the ones for which I found .dict files on the CM repo:

Bulgarian (bg)

Croatian (hr)

Czech (cs)

Danish (da)

Dutch (nl)

Finnish (fi)

Georgian (ka)

Greek (el)

Hebrew (iw)

Hungarian (hu)

Norwegian Bokmål (nb)

Portuguese (pt_PT)

Russian (ru)

Swedish (sv)

Tested for the Portuguese (pt_PT) language on ICS and 4.1 JB.

Please leave feedback if you try it out, especially for other languages.

I'm finishing some code cleanup and adding extensive comments, will push them to GitHub later today.
[Galaxy Note II Original Android Development] Tungstwenty:
The code is now available at https://github.com/Tungstwenty/Keyboard42DictInjector

I hope the comments can help you get started.

My next project will be way more complex and with more advanced techniques ;), so it will probably take me a few days to have it ready.
[Galaxy Note II Original Android Development] rovo89:
Quite a few hacks are already available in Tweakbox. The problem with it is the unknown scope. Some of the tweaks work only in Samsung stock ROMs, maybe limited to 4.0.3, as they activate or use features of TouchWiz. And for CRT, you even need a patched native library to make it work properly, which is hard to create and can only be exchanged as a whole, no partly patches possible that might work for different devices.

So I'm not sure what's better - many small mods or one bigger collection. If there is something to configure (apart from on/off), each mod would have to include its own configuration screen. On the other hand, bug report handling and releasing new versions is more flexible if you just need to look at one tweak and users don't need to install something they don't need. So yeah.. there are upsides and downsides for both.

There is also a big feature in Tweakbox which has no UI yet, but is working fine if you edit the configuration files directly: Changing DPI and things like that on a per-app basis. I mainly use this to force some Samsung apps to 240 DPI (for which they were hardcoded), while I use a lower DPI for the rest of my phone. I will look into creating a proper UI, but first the framework needs to be cleaned up a little.

And finally, I'm using a battery icon mod via Xposed. That would be a good demonstration of replacing resources and also some kind of template. I don't remember where exactly my icons came from (for credits/approval). I think it was JKay's mod for GB, but I can easily use any other battery mod for the demonstration if I don't find the author.
[Galaxy Note II Original Android Development] rovo89:
Alright, the developer tutorial is updated now to the latest APIs: https://github.com/rovo89/XposedBridge/wiki/Development-tutorial

It's really extensive, but if you're interested in learning what's behind Xposed, it will give you some nice insights. It also explains some of the basics of approaching a tweak target.

There is also a page on replacing resources (e.g. strings, booleans, but also images). It's not updated yet, things have become a bit easier meanwhile. Just to give you an idea what's also possible, additionally to pure coding hacks.
[Galaxy Note II Original Android Development] pulser_g2:
Awesome, nice work!
[Galaxy Note II Original Android Development] coolfire:
Tried the Xposed installer, didn't request t grant root and the allowlongsms.apk installed, but without any option to select anything else.

I rebooted my phone and tried typing an sms, but it still auto-converted to an mms after 80 characters... :(

On a SHV-E250S btw. :o
[Galaxy Note II Original Android Development] rovo89:
Did you actually hit the "Install" button inside the installer? It should display a message that the installation was successful.
[Galaxy Note II Original Android Development] Tungstwenty:
After installing the XposedInstaller app, the "Install" button must be pressed and the device rebooted.

On the next execution you should see the correct values under "active", as on the attached picture.

Only then will the modules selected on the "Modules" tab be executed.
[Galaxy Note II Original Android Development] coolfire:
Appreciate your help & wonderful work mates!

I'm such a bonehead - after installing the XposedInstaller app, I noobishly chose to exit & started looking for the app to open. Should have just opened it right on the same screen... Everything's perfect now. Just sent myself a long sms... And it works! LOL
[Galaxy Note II Original Android Development] dr.ketan:
Thanks a lot

It worked perfact on leaked LJ2, I have enabled call recording and working like a charm. You have made call recording easy for all ROM.
[Galaxy Note II Original Android Development] :
Just want to say a big thanks to pulser_g2 for this. Installed and working perfectly. Its made these mods simple to install for us less technically gifted mere mortals.
[Galaxy Note II Original Android Development] pulser_g2:
You're welcome but you should really thank rovo89 and Tungstwenty for this :) I just decided to try to resurrect it on the Note 2 given they'd got it working on jellybean. And then managed to somehow get together a couple of tweaks based on the framework with a fair bit of assistance from them...
[Galaxy Note II Original Android Development] pulser_g2:
Brilliant, thanks for letting us know :)

Seems this works quite nicely for letting us upgrade between roms without losing our favoured tweaks!
[Galaxy Note II Original Android Development] :
Thank you I will pass my thanks on to them. Is there any way this could be used for the internal external memory swap mod and the any app multi window? It would certainly make it a lot easier for us noobs
[Galaxy Note II Original Android Development] pulser_g2:
Do you have details of these two patches? I can take a look, the multi window should be possible for any app. Not so sure about swapping over memory, I'd need to look at it, but that sounds more just a change in mount points to me tbh...
[Galaxy Note II Original Android Development] :
http://xdaforums.com/showthread.php?t=1953705 and http://xdaforums.com/showthread.php?t=1931500 are the 2 threads I'd been looking at. If they could be made into apk's I and a lot of other users would be delighted. There would be no worry about bricking the phone and hopefuly the mods would stay after any update.
[Galaxy Note II Original Android Development] MohJee:
Well, just tried this. It works like a charm, and so simple that an 8 year old can get it to work. Just press install and reboot and walla!! Tremendous work. Thanks to all who made this possible.
[Galaxy Note II Original Android Development] kevin_diu:
Feature request: auto 2g 3g 4g settings with control app or compatible with juicedefender. It must be great! :)

---------- Post added at 01:26 AM ---------- Previous post was at 12:44 AM ----------

One more request, allow other launcher to add stock widgets like SPlanner or Weather widget. Sorry that I have no time to develop myself, Thanks :)
[Galaxy Note II Original Android Development] whatllitbenext:
MOD request: 5x5 apps layout

To the Community:

I was running Jedi-X7.2 but I really couldn't live without WiFi calling so I went back to stock and did the Multi-Window mod (which is awesome!!!!! -- thanks pulser_g2, rovo89, Tungstwenty, et al.!). Now I'd really like to have the 5x5 apps layout that Jedi X had.

Can this be done with a simple mod using this framework?

Does anyone know if this has been done already? I've searched this topic and all the relevant forums to no avail.

Thanks in advance.
[Galaxy Note II Original Android Development] lpsi2000:
I think even better, can we have something where we can configure the layout ourselves. Maybe make the max 10x10. I am using Apex right now 9x9 with DPI at 240. Would love to be able to configure the TouchWiz launcher with 9x9.
[Galaxy Note II Original Android Development] xSmittSx:
I changed the DPI of my launcher, but anyway to change the DPI of the status bar? Thanks much!
[Galaxy Note II Original Android Development] :
I should imagine so pulser_g2's scrolling wallpaper mod already gives us an extra row of icons giving 4×5 layout
[Galaxy Note II Original Android Development] Tungstwenty:
Yes, change the settings for the package "System UI" (com.android.systemui)

Don't kill it to apply settings immediately, though, as you can't relaunch it. Instead, reboot.
[Galaxy Note II Original Android Development] nerys71:
thank you so much for the directions. I had just reflashed my rom after a day of trying to get the thing to erase itself (bad cwm install it seems) so I wanted to do it right to avoid having to wipe again :) hehe

going to push the updates now looking forward to more modules!

so the tweakbox. this is a note II thread but it says ICS and the note II never came with ICS.

so it works on JB on the Note II? does the CRT effect work on the note II ? (I miss that such a small thing but so missed :)

a suggestion for the DPI module. since it already has its own UI for tweaking the apps would be nice to add a "backup/restore" option here. this way we can backup our app settings and then restore them if needed :)
[Galaxy Note II Original Android Development] rovo89:
I don't know if Tweakbox works on JB and if so, which tweaks work and which don't.. but you can just try it. ;) Very likely though CRT won't work. Look at the last posts in the Tweakbox thread and you'll find my explanation for this.

If you want to backup the DPI settings, you can simply use Titanium Backup or something like that and back up the data of the App Settings app. This is where all the settings are saved.
[Galaxy Note II Original Android Development] nerys71:
yep thats what I did for now.

is it going to be possible to get CRT working in JB or is that a lost cause?

Down the line a way to auto update modules would be nice too. I have no idea how hard or impractical that may or may not be but it would be pretty slick.

I am truly addicted to this multi dpi thing. all we need now is a multi scale function. IE "scale" the app larger without making its components larger.

Not sure if I am describing it properly so let me make an analogy.

when you "adjust" the dpi of an app its like increasing the resolution on a computer. everything gets "smaller"

so a 640x480 window is still a 640x480 window its just smaller now relative to the rest of the display.

when I change the individual DPI for that app back to say 320 in order to scale it to the screen I am making all its "components" larger as well.

what I want to do is grab the corner of the window and drag it making the WINDOW larger without actually scalling up its components.

does that makes sense?

when bala makes his "mods" for some like the dialer he does what results in exactly the same thing as what your multi dpi does.

SCALES the components as if it were back to 320dpi. BUT for other programs such as the pop up browser the side bar he does NOT scale it up.

he keeps the scale the same and simply instructs the app to "use" more of the screen real estate now created.

Here is an example. there are two ways to scale a program that is not DPI compatible. stretch it or instruct it to consume more space without stretching it.

your app setting stretches (which is what we want for things like dialer or calculator etc..) but NOT what we want for things like side bar or pop up browser etc..

Here is what your program does - - - - - - - - - - - - - - - - - - - - - - - - - -and here is what bala's mods does

Is there anyway to do "THAT" I know he is not changing any of the "physical" stuff in the file just XML information.

Imgur is not rendering properly right now so here are full size links

http://i.imgur.com/E9Pq0.png (your program stretching)

http://i.imgur.com/zTcts.jpg (Bala_Gamer's mod)
[Galaxy Note II Original Android Development] Tungstwenty:
Your device's stock DPI is 320, right? If so, you should enter a lower DPI value on the app (in this case the one that renders the multi-window list) so its contents show up smaller. What happens if you set a lower value like 240 for instance?

Also, can you post the list shown when you press the button to take a look at the resources bundled with that package?

(I'm pretty sure it's not as simple as this :) but just for the sake of understanding your issue)
[Galaxy Note II Original Android Development] nerys71:
hmm knew this would be a problem. its something that is much easier to show than to explain.

some apps "do not work" at 240dpi. they are "hard coded" for one DPI (in this case 320) so when you change to 240dpi they either FC or display wrong such as the dialer

now your program and bala_gamer's mods do the same thing as far as the "result" goes. your program instructs the dialer to load at 320 his mods "stretches" the program to full size "AT" 240dpi.

for fixed scale subjects like the dialer and calculator the result is the same BUT for non fixed scale subjects like the side bar you don't end up with the same thing.

notice how much "larger" the bar is with your program and how many more icons "fit" with Bala's mods.

ie your program DISPLAYS the app at 320dpi his modifications MAKE the program display correctly at 240dpi. ie he rescales it correctly for 240dpi instead of just scaling it back up to 320dpi.

what resources do you want me to get ?ie what package ?

think of it this way. your program will let you stay at 320 and then make some programs load at 240.

I am using your program for the opposite purpose. I am display EVERYTHING at 240 and then using your program to display SOME programs at 320dpi (the ones not compatible with 240dpi

ahh figured another analogy. YOUR program makes the "screen smaller" his program makes the APP bigger.

so its like I am on a computer at 1280x1024 but the dialer don't work at 1280x1024 so when I load dialer your program changes my screen to 640x480 just for the dialer and then back to 1280x1024 when I leave the dialer.

bala's mod "ALTERS" the program itself to display correct AT 1280x1024. ie makes the program bigger (but does not scale up its components)

make more sense?
[Galaxy Note II Original Android Development] Tungstwenty:
Not yet, sorry :D

Can you point me to his mod? Perhaps looking at some examples or even source code might help understand what changes could be done.
[Galaxy Note II Original Android Development] rovo89:
Found something:

I don't think this can be done in a consistent way as there are many different attributes which can have dimension values. I think the only way to consistently apply a certain factor to all dip values is to change the density. To me it seems that the key is not to change all of the sizes consistently but leave some dimensions (e.g. font/icon sizes) as they are (with lower DPI). The sidebar or popup browser are not available in my 4.0.3 S2 ROM, so that's nothing I could try.. are there any other examples (except for calculator etc. where the result would be the same as you said)?

Anyway, I think this would require a selection of which resources to scale and which not to scale... it's questionable if this can be decided by a machine (i.e. following strict rules). And even if there was a way to determine this, we are back at my initial concern: Is there a universal place to find and change these dimensions? So I doubt there can be a solution for this other than manually editing the app or maybe writing a module which targets exactly that app and modifies it in the correct way.
[Galaxy Note II Original Android Development] nerys71:
i was just starting to think the same thing. that there is also little NEED since its only going to be a couple tops so direct correct mods would likely remain the right way to do it. sometimes he has to try several times to get "all the bits" modded right so would likely be very hard to do from an automated program perspective.
[Galaxy Note II Original Android Development] chemcup:
Anyway to change the DPI of the side bar that renders the multi-window list?
[Galaxy Note II Original Android Development] nerys71:
yes and it works fine. you need to tweak the program named

com.sec.android.app.FlashBarService

it is only compatible with 320dpi (to look right) it works FINE in 240dpi just looks funny and the edit button is missing in long side but their in short side mode.
[Galaxy Note II Original Android Development] lpsi2000:
This was exactly the feature I was asking for early on (when DAGr8 commented on this). You might be right about your comments, however they must be something that can be done because there is a way to make app MultiDPI using the method above, it no longer care what DPI you use because it seems to scale at any dpi properly. I believe DAGr8 share this information with bala_gamer who now have a couple of apps (Dialer, etc...) who will scale at any dpi. I believe PA (ParanoidAndroid) does have this feature (so it must be possible somehow). I think you need to understand what bala_gamer does for the multipdi dialer in order to understand what were are asking.

Thank you for explaining this a little bit better than I was able to do.

---------- Post added at 08:09 PM ---------- Previous post was at 08:07 PM ----------

exactly, but the one that is made for 240 or multidpi works great with no funny looks
[Galaxy Note II Original Android Development] nerys71:
ahh you need to goto bala_gamer's thread with his mods for sprint note II (also one for international note II) and flash his mod for the flash bar. I have tested it on the Sprint Note II and it works great.
[Galaxy Note II Original Android Development] whatllitbenext:
Hey sawdoctor:

not sure what you're talking about -- I downloaded the scrolling wallpaper mod and it works but I only have a 4x4 layout.

:confused:
[Galaxy Note II Original Android Development] :
I think pulser_g2 has updated his scrolling wallpaper paper app. The original one still works for the layout but scrolling didn't work on 4.1.2. Its near the start of this thread. I'll try and upload it if you can't find it.
[Galaxy Note II Original Android Development] drjamit:
Small Dialer Info and More of a Contacts Photo

Can we have thin line on Contacts photo and Smaller size Options below contacts photo if we Scale to 240 DPI. Which app is to be made 240 DPI , if we can without disturbing any mobile function..
[Galaxy Note II Original Android Development] jujuburi:
Hmm seeing too many interest about DPI, well for our loving eyes, do you guys think it's okay? I mean just boosting up the DPI value to see 'more stuffs' on this 5.5" tiny screen! Certainly not for me, even with my near perfect vision.

Just a thought, no offense to anyone.

I can't find it. If you've it kindly redirect there. Also if any other modules have been updated already please do inform.

Sent from my GT-N7100
[Galaxy Note II Original Android Development] Tungstwenty:
Well, as you say it's really a matter of personal taste.

I also don't use this a lot, I only reduce the "zoom" in a couple of apps in order to view more info: status bar; settings; BBS; google quick search; Samsung memos ... and AppSettings itself :)

Kudos to rovo for clearly explaining the whole resizing issue :good:

Basically, a layout where everything is using gravity, weight, wrap_content/match_parent etc. in order to automatically adjust the contents based on their size and the entire available space, will pretty much work. Whenever there are explicit sizes on some stuff, there you go ...

Just like layout managers in plain old Java swing - "don't use absolute layout" :)
[Galaxy Note II Original Android Development] SandeepEmekar:
@pulser: Can you please update "Blocking Mode Icon Remover" to V2?
[Galaxy Note II Original Android Development] Lennyuk:
Pulser will update all his mods when he has the time to do so.
[Galaxy Note II Original Android Development] nerys71:
I use 240dpi throughout (any smaller and most apps are a bit too small if you go past 240dpi plus 240dpi is a "standard" so no play store issues.

some apps I run at 320 so they format properly (dialer calculator) some so they don't crash (clock package)

I run gmail at 200 and I run parcels at 160

gmail looks great at 160 but too hard to read on the 5.5" display 200 is on the edge but a nice compromise.

I guess my eye is good cause I can't stand it at 320dpi. such a horrible waste of a gorgeous screen. even my S2 I ran at 240dpi. same with the S3.
[Galaxy Note II Original Android Development] lpsi2000:
+1, such a gorgeous screen and the additional real-estate helps too:D
[Galaxy Note II Original Android Development] neol23:
Sorry but I cannot understand -some mods are working with xposed app v.2.0, and other with v.2.0rc2... Those from villan repo, pointed in OP.

Are they not yet updated to work all with latest version 2.0, according original xposedframework tread?!

Thanks.
[Galaxy Note II Original Android Development] Lennyuk:
All the mods added in 2013 are working on 2.0 as is the DPI chaging mod as this was updated for it. The rest will only work on rc2 for the time being.
[Galaxy Note II Original Android Development] RomBox:
can we control the rotation use the xposedApp? some apps actually only run better in portrait mode, such as tapatalk, but it can't be locked to that...
[Galaxy Note II Original Android Development] Tungstwenty:
Not currently, but there should be some way to implement it in an app-independent way. And that makes it a good candidate to be added to the mod.

I'll try to see if it can be done, when I have some free time.
[Galaxy Note II Original Android Development] chemcup:
How you fixed the Samsung keyboard at 240dpi

Samsung keyboard FC at 240dpi when using and when Xposed to change it dpi to 320 I can see only half of the keyboard
[Galaxy Note II Original Android Development] jiannist:
Could someone please compile the modules at the repository with the SDK for 4.0?
[Galaxy Note II Original Android Development] neol23:
I hope all old mods will be fixed to work with 2.0 as well...
[Galaxy Note II Original Android Development] benj29:
I have the same trouble. I'll use SwiftKey and no trouble in 240dpi.

Envoyé depuis mon GT-N7100 avec Tapatalk
[Galaxy Note II Original Android Development] chemcup:
With other keyboards no handwriting ?
[Galaxy Note II Original Android Development] benj29:
I prefer SwiftKey... It is the best for me. :)

Envoyé depuis mon GT-N7100 avec Tapatalk
[Galaxy Note II Original Android Development] pulser_g2:
No, they were made and tested on JB. If you want to run them on 4.0, you will need to test them yourself. I am not happy publishing APKs for 4.0, as I can't test them, and their behaviour will be unknown. Some definitely won't work.
[Galaxy Note II Original Android Development] RomBox:
i have set the system ui to use dpi 220, it looks ok at home screen, but when i start an app, there will be a gap between the statusbar and the app. how can i close the gap?
[Galaxy Note II Original Android Development] fga:
Try this :thumbup:

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

★GT-N7100★
[Galaxy Note II Original Android Development] RickROM:
Change the Android System DPI to the same also