yashsingh1/xdaforums huggingface dataset:
[Galaxy Note II Original Android Development] neol23:
AWESOME! Thanks,
[Galaxy Note II Original Android Development] Dovidhalevi:
XposeAppSetup and Trebuchet Launcher

Trebuchet launcher, when used with more the four rows, does not correctly scale its icons and text labels. Longstanding bug, minor, certainly OK and usable, but ...

With a Paranoid ROM and Trebuchet 0.2, resizing to 130 or so yielded perfect results, both portrait and, surprisingly, in landscape!

XposeAppSetup and Trebuchet 1.0, such resizing yields nice results in portrait, text missing in landscape. Trebuchet crashes repeatedly so I switch the mod off.
[Galaxy Note II Original Android Development] rovo89:
Sounds possible and should be a rather easy mod. Maybe something for someone who wants to write their first module?

What do you mean? Apps are not shown in Play Store? Or where do they vanish from?

Or you simply install the latest version of App Settings, which includes a feature to override the orientation: http://xdaforums.com/showthread.php?p=36624442
[Galaxy Note II Original Android Development] debernardis:
R: Making "Stock" Custom ROMs Defunct (XposedFramework) - Tweaks for any ROM Version

I have had instability and crashes with " AlternateAppPicker: ICS-style default app chooser for JB" on Touchwiz (note 2, LL4 ROM, perseus 3.1 kernel) with the inability to change desktop background which resulted in force close. Xposed 2.0.2.

Had to uninstall; same effect is provided, more or less, by "Doubletap in AppPicker" with no problems at all.

Hope it helps.
[Galaxy Note II Original Android Development] Xaddict:
Was there a trick to getting it working?
[Galaxy Note II Original Android Development] GezDixon:
sometimes when I open play store I get a box popup with accept / decline. If I accept with my touchwiz modded to 270 some apps don't seem to show up in the different sections as I only get 1 page (normally when you scroll down another page loads) but now it doesn't. also if I do a search for chrome or firefox it says my device is not compatible.

the only way to fix is to turn off appsettings and uninstall all play service updates + clear cache from service and play store then reboot.

When I open play store now with default dpi (320) I tap on accept and everything works (multiple pages from top paid/top free and get no not compatible errors) even when I enable appsettings and change back to 270dpi. only seems to happen when I get play service update.

I think this might be the solution http://xdaforums.com/showthread.php?t=1580827

EDIT: just installed the All apps in Play Store mod so will see if I have any probs
[Galaxy Note II Original Android Development] dr.ketan:
Nope, I used patched apk

http://xdaforums.com/showthread.php?t=2104028
[Galaxy Note II Original Android Development] RomBox:
so nice! thank you! :laugh::highfive:
[Galaxy Note II Original Android Development] rovo89:
This is not because of Xposed. It's because of the custom DPI. Google transmits the DPI to its servers from time to time (I don't know the intervals) and only shows you those apps which it thinks are available for your phone. As this is server code, there is no way for us to influence it. Most workarounds I'm aware of try to fake the DPI that is submitted to the standard one. The mod you mentioned is by myself, using the patches from the thread you linked to. However, after some while I was back to the limitations, therefore I'm currently testing modded APKs. Patching Play Store alone was not enough, so now I'm trying the patched GoogleServicesFramework as well. If this works, I will look into the details what was changed and try to implement this as Xposed mod. But I have the bad feeling that this won't work either as my mod patches GSF as well...

Give thanks to Tungstwenty, he implemented it. ;) But I take your thanks as well as I re-implemented it a bit differently for the next version. :)
[Galaxy Note II Original Android Development] _TB_TB_:
Hah, an updated version + uploaded to Microdownloads!

http://www.villainrom.co.uk/forum/microdownloads/deliverynotify-toast.23/viewfile

- supports multilanguage

- handles only "Delivered" notification
[Galaxy Note II Original Android Development] GezDixon:
I think it is googleservicesframework that is the problem at the moment it is a pain in the ass
[Galaxy Note II Original Android Development] SenK9:
Re: Making "Stock" Custom ROMs Defunct (XposedFramework) - Tweaks for any ROM Version

The NFC addown doesn't seem to be working for a lot of people at the moment. The author has been informed and is working on it.
[Galaxy Note II Original Android Development] Pliind:
Re: Making "Stock" Custom ROMs Defunct (XposedFramework) - Tweaks for any ROM Version

Hello,

I cant seam to be able to get app settings to work.

I have installed and rebooted as i should, applied and activated everytjing and rebooted again but the apps take no effect of what i do. All saved settings dissapear when i reboot. Any ideas? Using pers kernel if that makes any difference jag
[Galaxy Note II Original Android Development] OXINARF:
Well just posted my first app/Xposed mod in S3 forum: http://xdaforums.com/showthread.php?t=2106490

It is a really simple app to change the number you have registered in your SIM card.

I'm not thinking about putting it in our repo because I won't give much support, don't plan on releasing another version and it is only tested on S3 (and not that much), but if anyone asks for that I'll do it.
[Galaxy Note II Original Android Development] :
Re: Making "Stock" Custom ROMs Defunct (XposedFramework) - Tweaks for any ROM Version

Ive set the message apk to always portrait using the xposed app settings. When you open a message to read it the always portrait stops working. Does anyone know what else I have to set to portrait to stop it?

Many thanks in advance
[Galaxy Note II Original Android Development] OXINARF:
It also works on mine 4.1.1 S3.
[Galaxy Note II Original Android Development] Kitschki:
Re: Making "Stock" Custom ROMs Defunct (XposedFramework) - Tweaks for any ROM Version

Um.. Is there a fix for the parsing error out here? Havent been lookin in this thread for a long time :/
[Galaxy Note II Original Android Development] rovo89:
Do you mean those settings you made in App Settings, e.g. enabling the mod for an app and changing the DPI? Have you clicked the "save" button? The way settings are saved is absolute Android standard.

I have completely rewritten the way the screen orientation, fullscreen mode and permissions are set. That will be in the next version (no ETA yet). I suggest you try again once the next version is out.

"The parsing error" I'm aware of was related to minSDK specified in AndroidManifest.xml of those modules. E.g. some have set minSDK=16, which throws a parsing error on ICS. Blame Android for mentioning the real reason only in logcat. So it's not really a bug, but a feature. The module author probably could only test it on JB, so he decided not to release it for ICS. After all, quite a few things have changed between these versions, so even if you could install it, it might not work. If you want to try anyway, decompile the module, change the minSDK and compile it again. Then check if it works for you. If it does, you may contact the module author to inform him about this and he may decide to lower the minSDK limit.
[Galaxy Note II Original Android Development] Pliind:
Re: Making "Stock" Custom ROMs Defunct (XposedFramework) - Tweaks for any ROM Version

Yes i hit the floppy icon, but nothing happens to the app.
[Galaxy Note II Original Android Development] rovo89:
But you mentioned that the settings disappear after a reboot. So you reboot, open App Settings and whatever you changed is gone? Just to make sure that you have installed Xposed correctly, can you post the file /data/xposed/debug.log?
[Galaxy Note II Original Android Development] tacchan23:
Really hope someone could pick it up! I tried to read the Xposed documentation/tutorial 3 times but it's really too much for a guy with zero knowledge, ehehe
[Galaxy Note II Original Android Development] Pliind:
Re: Making "Stock" Custom ROMs Defunct (XposedFramework) - Tweaks for any ROM Version

Heres my log, but the thing is that other modules work.

Btw does the fact that i chose 240 dpi as stock dpi have anything to do with it? I got xposed framework along with a custom stock rom installed with aroma.

pliind.dyndns.info/debug.log
[Galaxy Note II Original Android Development] rovo89:
Thanks. At least the last try looks fine.

Setting a different DPI in build.prop is no problem. The custom ROM might be if they have changed some very central parts of the Android platform.

Regarding my question: Are the choices you make in App Settings still there after a reboot? If not, you probably have a big problem with your ROM or permissions or so. You can also try uninstalling the module completely (including data) and reinstall.
[Galaxy Note II Original Android Development] Pliind:
Re: Making "Stock" Custom ROMs Defunct (XposedFramework) - Tweaks for any ROM Version

Choices are reset after reboot yeah.

Ill give it a go to reinstall the app, upgrading didnt seam to work either.

Oh in the rom thread i was adviced to install the rom again and chose 320dpi instead of 240. Dont know if that will change anuthing though.

Thanks for your advice!
[Galaxy Note II Original Android Development] rovo89:
Settings are stored in /data/data/<package name>/shared_prefs as XML files. If that doesn't work, then you do have a problem. After uninstalling, make sure that /data/data/de.robv.android.xposed.mods.appsettings is gone completely. Then you might have chances that it will be recreated properly.

Btw, it could also be that case that the file has wrong permissions. After installing again, make sure to open the app first and configure something before activating the module and rebooting. Some ROMs seem to create the XML file even when only read access happens. A workaround should exist in the latest App Settings though. In addition to that, Xposed 2.1 will use its own implementation of SharedPreferences to avoid misbehaviors.
[Galaxy Note II Original Android Development] Pliind:
Re: Making "Stock" Custom ROMs Defunct (XposedFramework) - Tweaks for any ROM Version

Wiped and uninstalled with Titanium, installed new Package and all is good now :) camera finaly looking normal :)

Thanks!
[Galaxy Note II Original Android Development] theory_87:
Re: Making "Stock" Custom ROMs Defunct (XposedFramework) - Tweaks for any ROM Version

Can anyone do a module to switch on the USB debuging mode permanently? It always switch off after a reboot with stock kernel
[Galaxy Note II Original Android Development] genei.09:
aalupatti asked this question in the wrong thread: http://xdaforums.com/showpost.php?p=36881870&postcount=432

On my phone in landscape view gmail ALWAYS puts the buttons at the top. In portrait view gmail will put the buttons at the bottom. Changing the DPI and tablet/phone mode of the app will not effect the button placement. Another mod in xposed may be able to change that but I haven't seen one yet.

Question of my own:

I'm using Touchdown for my corporate Exchange account. It has a tablet UI that I see on my tablet (ICS) but when I try to enable that on my phone (JB) I only see the dpi change and not the interface. Gmail changes interface as expected, as does Netflix. I've tried a few different DPI values and resolution values to no avail. Any thoughts?
[Galaxy Note II Original Android Development] Tungstwenty:
The buttons placed at the top vs bottom is a matter of available space.

That bar is called the "ActionBar" and one of its possible behaviors (which GMail is probably using) is splitting across top/bottom when there's not enough space for everything. More info here: http://developer.android.com/guide/topics/ui/actionbar.html#SplitBar

I'd take a wild shot and say that if you change the DPI to some bigger or smaller values, you'll still get the bottom bar in portrait but one or two buttons might start appearing in the bottom instead of the top or vice-versa, no?

Can you take a look at the existing resources in the app (press the "List Res" button) and post it here? You might need to change the reported screen size and/or activate the "Tablet" checkbox in order to trigger loading alternate layouts, if they exist.
[Galaxy Note II Original Android Development] genei.09:
drawable

drawable-hdpi

layout

layout-hdpi

layout-xlarge

menu

menu-hdpi

menu-xlarge

raw

xml

I've tried the settings that work for gmail (dpi 160 800x1280 tablet mode) but no ui change, just resolution. I tried more extreme settings on their own and in combination with and without the tablet mode checked. I know in ICS on my tablet it has an alternate UI, but I don't have a tablet running JB at the moment to know if the alternate layout works in JB.
[Galaxy Note II Original Android Development] Tungstwenty:
The *-hdpi resources (drawables, menu, layout) will be loaded if the DPI is in the ~240 range or above.

This means that if you reduce the dpi so that the displayed content is smaller and there's more space for stuff, as a downside you might get layouts that are meant for "worse" screens.

I'm hoping to introduce in one of the next versions a separate DPI setting for the resource *selection* and for the actual rendering on the screen. In other words, selecting the resources meant for large DPIs, but still rendering them smaller.

As for the *-xlarge resources, they're selected if the screen dimensions (which you can override) are at least 960 x 720. Or, in alternative, if you check the "Tablet" setting, which activates the SCREENLAYOUT_SIZE_XLARGE flag.

This page describes how the resources are selected based on the qualifiers and the device characteristics.

In a nutshell, I'd say that for this particular example you should get the "large" resources by merely activating the Tablet checkbox, which should trigger loading the *-xlarge layout and other resources. They might not be have you were expecting, though...
[Galaxy Note II Original Android Development] rovo89:
Yes, but are you sure that this isn't calculated before the value are overridden? I think this is calculated once in the system server and then sent to the applications. I would like to see this being calculated automatically though as these xlarge etc. are just groups of screen sizes.
[Galaxy Note II Original Android Development] genei.09:
I tried all of the following in every permutation with the same results

DPI 60, 160, 240, 260, 300

Resolution: Default, 320x480, 800x1280, 1000x1600

Tablet UI: checked, unchecked

The size of the elements changed but the layout never did. In some of the tests I tried rotating the screen, but not all of them. I have rotation disabled on my tablet and haven't tried it in portrait mode.

-edit-

I'm estimating my tablet to be ~135dpi and 1366x768
[Galaxy Note II Original Android Development] appro77:
I'm using this framework on my 7100 and loving it. Absolutely brilliant. Not sure if this is a dumb question, but will it work with the 7105?
[Galaxy Note II Original Android Development] rovo89:
Just as a quick note: I assume that these are hardware pixel sizes. The hardware dpi are not directly related to the dpi used for rendering. And the screen sizes you can select are also defined as "dp", a unit which scales with the (software) dpi.

Absolutely right. I have unfrozen my Gmail app to try this myself. With 192 dpi and no change in screen size (default S2 dimensions), the buttons are at the bottom in portrait mode and at the top in landscape mode. At 600x1024dp, they are always at the top. The reason is rather simple: There is a boolean resources in the Android framework called "split_action_bar_is_narrow", which decides whether the action bar should actually be split when this UI attribute is set. It defaults to true, but in "values-w480dp", it is set to false. That means that the action bar will not be split when there are more than 480dp (not pixel) of width available (as this isn't "narrow" anymore).

There should be a configuration where your screen is wider than 480dp (to disable the split action bar), but still narrower than 600dp (to avoid the tablet layout). As dp depends on density, this could be triggered by a certain rang of density, depending on your actual screen size in pixels.

Of course, the "split_action_bar_is_narrow" could be modified as well:

XResources.setSystemWideReplacement("android", "bool", "split_action_bar_is_narrow", true);

This code is for the whole system, but it could easily be limited to a single app. Setting the value to true will always display the buttons at the bottom, false will always put them at the top. This works independently from tablet layout or not (i.e. with the code above, the buttons are at the bottom even in tablet mode).

As this works independent from the app, it could be another candidate for a dropdown in App Settings [(default), always split, never split], but well.. the UI is quite full already. :(

It's not a dump question, but I can't answer it. Chances a pretty good that it will work (at least the framework - modules are more likely to depend on a certain ROM environment). If it doesn't, please let me know.
[Galaxy Note II Original Android Development] :
Re: Making "Stock" Custom ROMs Defunct (XposedFramework) - Tweaks for any ROM Version

Works fine on 7105. Ive been using it since pulser first started the thread
[Galaxy Note II Original Android Development] aalupatti:
Re: Making "Stock" Custom ROMs Defunct (XposedFramework) - Tweaks for any ROM Version

Wow... loved your explanation. Really like it when devs describe things in noobs language.

Also it would be great to have such an option for people lke me who use the portrait mode most of the time. The top action bar is sometimes difficult to reach.

Edit : can this be implemented on a personal level by pushing thismcode somewhere using terminal (thats the limit of my knowledge)
[Galaxy Note II Original Android Development] chrisryn:
Re: Making "Stock" Custom ROMs Defunct (XposedFramework) - Tweaks for any ROM Version

Pulsar_g2 I might have missed it, did you/could you post source on the 5x4 mod to twlauncher.
[Galaxy Note II Original Android Development] joseangel.alv:
I've also missed it... But I suppose it's similar to the scrolling wallpaper one (main java mod here), but modifying the variables and values in this other post. :highfive:
[Galaxy Note II Original Android Development] 白い熊:
Re: Making "Stock" Custom ROMs Defunct (XposedFramework) - Tweaks for any ROM Version

I've used the DPI per app tweak to change the "System UI" to make the toolbar smaller.

While it has made the toolbar icons and text smaller, the vertical dimension of the toolbar stayed the same, so there's small icons in the fat toolbar and the apps don't cover the now empty vertical part of the toolbar.

Is this hardcoded somewhere? The vertical dimensions of the toolbar.

--

白い熊
[Galaxy Note II Original Android Development] rovo89:
Kind of. The statusbar height is set in the class PhoneWindowManager in the system_server, not in the System UI itself. This would require a more targeted modification, whereas App Settings has otherwise settings that can apply to all apps. On the other hand, setting the correct height should consider the System UI dpi, which could be a reason to include this tweak... not sure.
[Galaxy Note II Original Android Development] Dovidhalevi:
Dropdown size:

Phone --> full screen

Phablet --> half screen

Tablet --> partial screen?

Paranoid change of DPI changed the font and icon sizes also in the drop down.

AppSetup module changed the font and icon and height of the closed system bar (on top). Dropdown text sizes seem unchanged.
[Galaxy Note II Original Android Development] rovo89:
As far as I understood, the question was not about the dropdown size (expanded notifications), but about the status bar height (closed). The latter is not changed by Xposed as it is not calculate in the System UI "app".

You are correct about the the notifications inside the dropdown. At least on CM10.1, the notifications don't scale. I'm not feeling like spending the time to investigate, but my guess is that the layout for the notifications is rendered in the context of the app which posted them. I did a quick test to apply the resources with the settings of the current process, not of the app from which the resources are, and then the notifications scale with the System UI density. This might have other consequences though, so this has to be considered carefully.
[Galaxy Note II Original Android Development] Pliind:
Re: Making "Stock" Custom ROMs Defunct (XposedFramework) - Tweaks for any ROM Version

I dont know if this is my rom or the framework, but im guessing the framework.

Whenever i dock my phone in the original cradle my statusbar fc's

And when i wake up in the morning samsungs stupid battery full notification is stuck in the drawer. Cant clear it.

If I close the app the notification disappears and my wallpaper goes to samsung stock.

My dpi is 240dpi

Any ideas?
[Galaxy Note II Original Android Development] _TB_TB_:
Re: Making "Stock" Custom ROMs Defunct (XposedFramework) - Tweaks for any ROM Version

The status bar height can be changed via Xposed : just re-write the height in layout XML (hook resources loading). Additionally you should poke around PhoneWindowManager and WindowManagerService (or similar, no PC access right now...) to include the new height in "available workspace size" calculation.

Sent from my GT-P3100
[Galaxy Note II Original Android Development] 白い熊:
Re: Making "Stock" Custom ROMs Defunct (XposedFramework) - Tweaks for any ROM Version

What is this AppSetup module you're talking about that can do this? I haven't seen it anywhere. I'm using Xposed App Settings and this doesn't change the closed system bar height.

--

白い熊

---------- Post added at 09:27 AM ---------- Previous post was at 09:22 AM ----------

You mean extract the systemui apk, make the edits there etc.? So how is that doing it via Xposed?

Or am I not understanding?

--

白い熊
[Galaxy Note II Original Android Development] Dovidhalevi:
That is the one.

The closed height is changed, at least on mine, but goes back to original height when touched, i.e. to adjust screen brightness. But that also changes the content/order. Drop-down sizes are not changed.

Correction: On light background see the total height might not have changed. No sooo awful, however. Options to make it transparent and/or hideable might be appreciated. Would not mind the new Ubuntu approach: swipe from the appropriate screen edge to see this stuff. If either or both bars are hidden, expand desktop.
[Galaxy Note II Original Android Development] rovo89:
Correct in the general case, however I think you are better off by hooking PhoneWindowManager.setInitialDisplaySize() and setting mStatusBarHeight as wanted for this very specific case. The status bar is a special thing because it influences the size that is available for apps.
[Galaxy Note II Original Android Development] chrisryn:
Ok working on my first modification and have gotten my self really confused. I under stand the process for replacing values in the res. What I haven't figured out is how to tell it which xml file in which directory that the value to change is located.

com.sec.android.app.launcher", "bool" thats obviously a bool.xml file but if you decompile the apk there are several bool.xml.

I'm still learning but the only thing I could figure out is it only loads on of each type of xml file and the others would be called if for instance language was changed.<--- Best way I can explain what I think is working.