Hey guys so I m pretty much flat out new to theming and Android in general but I've gotten by so far with google and sites such as this, and androidforums. Except I keep running into problems and I figured posting my self would probably be best. My plan is to update this post with new questions I have and also keeping updated with the correct answer if provided for easy reference for future use.
So without further ado my first problem lies currently in twframework-res.apk.
Currently I am trying to edit the tw_tab_selected.9.png. I have an odd problem in that when I edit it and add in the proper guidelines in draw9- which was none (*Note the original tw_tab_selected.9.png actually does not have any guidelines even though it is a .9png) it seems to stretch out like below:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The image SHOULD stretch out and appear like the following image:
Couple of notes:
- I have tried adding guidelines to my modified tw_tab_selected.9.png, below is an example of one of the guideline formats I tried but still yielded similar results as above picture #1 (This was following the draw9 guidelines of a similar image tw_tab_selected_ss.9.png)
Related
Well, after looking for an not finding what I wanted...I just decided to build it.
#1 - place to compare ROMs and Kitchens..with filter and sorting.
#2 - place to keep track of my own personal ROIM experiences
#3 - place to keep track of cabs I load (how many cabs do you have on your storage card you have no idea what it is)
So I built up this Sharepoint site and gave a bunch of Cookers rights to post their stuff...but more is better!
So, now I'm going to the public.
Here are some screenshots of the basic idea
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here are some of the cool stuff you can do with lists:
filter By Carrier
Filter By system
here's where users can track their experiences with different ROMs and Kitchens
Here they can track stuff on different Programs and Cab and such.
So....after all that...
The site is located at : http://sp.textultant.com/Mobility
The URL will redirect you there : http://TheMobilityExperts.com
Please understand that adding users is not automatic and somewhat cumbersome....I will try to process requests as soon as I can...but I just want to set expectations...It may by 24 hours or more in some cases. since I'm the only Admin right now.
Hope you like it...There's a survey out there on the site to let me know what you think.
EVERYONE can View...
there are instructions on the site for how to Join and Use
Here goes..........................
CHEERS!
Matt
Hi Guys,
I'm a designer and have put together a concept of a Google Search Widget that I wouldn't mind sitting on my home screen. I've integrated styles from other parts of the UI so that it'll fit more seamlessly into the user experience.
I've never developed for Android before but have done a lot of background reading and am aware of the various \res\drawable images I'll need to replace. My question is whether or not I'll be able to replace those images without rooting my device, using ASTRO for example?
Also, is it a simple case of replacing the \res\drawable images and it working or is there more to it?
I've got a locked bootloader and don't want to unlock it, so am waiting for ICS and a hopeful way to root with a locked bootloader then.
Screenshot of what it will look like:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'll be re-designing the app that launches upon touch to look more like the Xperia UI menus
Cheers,
M
Bump for post edit (didn't want to duplicate/start a new topic)
Ok, so every mod/guide/apk I have found for CM9/ICS does not seem to work with any of our ICS Roms. From reading comments, it seems that somewhere mid 2012 something changed in the SystemUI source that stopped the previous mods from working. I am guessing that is our problem.
Well there is a source patch that does work for ASOP by Evilisto.
I used that diff patch as a somewhat 'guide' for editing the systemUI.apk of CM9 and it works!! Just thought I would share.
Just a couple of notes...
1. There is no 'res/layout-sw600dp/navigation_bar.xml'
2. No need to edit the launcher portion
3. The changes to 'res/values/colors.xml' actually need to be made to our 'res/values/drawables.xml'
4. When editing 'com/android/systemui/statusbar/phone/PhoneStatusBar.smali'
- Do a search for 'mPixelFormat' and directly above that line change 'const/4 v8, -0x1' to 'const/4 v8, -0x3'
- That is equivalent to making the 'mPixelFormat = PixelFormat.TRANSLUCENT;' change.
- Thats the only edit you need to make to that file
5. No need to edit 'com/android/systemui/statusbar/tablet/TabletStatusBar.java', our phones not a tablet
Screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi, all. I have a question that I hope someone can help me answer. I've been using MeteoNotifier (gplay link here) for the last little while. The app creates two persistent notifications via 2 xml's and, on KitKat, the notifications were Current Conditions on top and the Forecast on the bottom (see example below)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
With the 5.0 Lollipop update, I noticed that the notifications have switched orders (i.e. Forecast on top, Current Conditions on the bottom)(see example below)
My question is, does anyone know how I can change the order of the notifications back and can this be done by editing the xml files? I am not a developer (i.e. no Java knowledge) but I am handy with apktool and xml editing (and very limited knowledge of smali editing). Logic tells me that this most likely cannot be done by simple xml editing but I thought that I'd ask. Thanks.
PS I'm almost certain that the app has been abandoned by the dev (it has not been updated in almost 2 years) and that is why I'm posting the question here. Plus, I enjoy learning about this stuff
Last week I released a thread to introduce my new app Parasol which can solve the permission problem on Android M. I am so excited that i got lots of supports and feedback from users here. I am so appreciated.
Here is the link: http://forum.xda-developers.com/android/apps-games/app-parasol-alpha-t3190615
Because the feature of modifying permission settings cannot be implemented on the OS lower than Android M (users can read permission tags on Android 5.x and lower), I have designed a popup to give a tip to users, just like the pic shows:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I noticed that some users felt confused about the tip: "you can't modify your permission settings under Android M."
what i want to tell users is: [highlight]you can't modify your permission settings if your os version is lower than Android M.[/highlight]
But it seems like the word "under" made the expression is diametrically opposed with my original idea.
Can i just say: you can't modify your permission settings below Android M.
OR,
Can native speakers give me a suggestion on a better expression?
Also, any feedback about the app is welcomed. love you guys~