Related
Is there a way to enlarge the fonts size and color of the Calendar events in the TODAY screen? The current font size is too small for me.
Yea, I have same problem, while TF3D , the calendar fonts are too small and gray (on the today screen) , I can read the time , but I can't read what I have in this meeting..
If I open calendar I can see it ofcorse.. ,
I saw some threads about fonts , but those change all the TF3D fonts, I would like to change only the Calendar fonts so I can read it like without TF3D on the Today screen .
In normal way without TF3D, the Today screen fonts using Sytem fonts which you can control the size by Text Size from screen control.
Seems like TF3D does'nt care about the Text Size from screen control , and it has his own wired small fonts...
I was hoping for a better answer, but found none over the web Can someone suggest a fix? I am convinced i am not the only one who is not happy with the current font size/color.
elrik said:
I was hoping for a better answer, but found none over the web Can someone suggest a fix? I am convinced i am not the only one who is not happy with the current font size/color.
Click to expand...
Click to collapse
I'm no happy too...
Ciao, Andrea
I've tried to edit the files contain Color and font size in manila
for example 209b5cdc_manila
just something like
<Style Name="BlueTheme_BlackColor">
<!-- Black -->
<Property Name="Color" Value="0, 0, 0, 255" />
</Style>
but no matter how hard I tried
nothings changed.
I think it might be set in other files .
These registries will have an impact only if you turn off the TFL3D.
Hi,
I was just wondering, is there any way to have an animated widget on the android homescreen, which stays animated and consists of multiple frames? For instance, an animated flash, gif or png sequence?
Thanks
i never used animations on an app, but try it with gifs, or looped zip files, like bootanimation.zip, that creates an animated picture, from multiple files.
ilendemli said:
i never used animations on an app, but try it with gifs, or looped zip files, like bootanimation.zip, that creates an animated picture, from multiple files.
Click to expand...
Click to collapse
And this can be used as a simple widget?
don't know, wait for other posts, you can make a onclicklistener to an image
I'm not talking from experience here, but since widgets update in real time (facebook and twitter for example), there's obviously a method of updating what's displayed so I can't see any reason that you couldn't have an animated widget (other than the usual CPU and battery issues).
maybe develop a service that is constantly pushing messages to the widget? but I suppose this will be a huge battery drainer....
There should be a way to do it. After all, under the "res" folder, there is a supported and standard sub-directory called "anim" that can be used to bring compiled animation files to your app. Look into on the android developer site. I'm thinking this is the way to do it.
Here is a reference from the adroid dev site on using a class called AnimationDrawable:
public class
AnimationDrawable
extends DrawableContainer
implements Animatable Runnable
java.lang.Object
↳ android.graphics.drawable.Drawable
↳ android.graphics.drawable.DrawableContainer
↳ android.graphics.drawable.AnimationDrawable
Class Overview
An object used to create frame-by-frame animations, defined by a series of Drawable objects, which can be used as a View object's background.
The simplest way to create a frame-by-frame animation is to define the animation in an XML file, placed in the res/drawable/ folder, and set it as the background to a View object. Then, call run() to start the animation.
An AnimationDrawable defined in XML consists of a single <animation-list> element, and a series of nested <item> tags. Each item defines a frame of the animation. See the example below.
spin_animation.xml file in res/drawable/ folder:
Code:
<!-- Animation frames are wheel0.png -- wheel5.png files inside the
res/drawable/ folder -->
<animation-list android:id="selected" android:oneshot="false">
<item android:drawable="@drawable/wheel0" android:duration="50" />
<item android:drawable="@drawable/wheel1" android:duration="50" />
<item android:drawable="@drawable/wheel2" android:duration="50" />
<item android:drawable="@drawable/wheel3" android:duration="50" />
<item android:drawable="@drawable/wheel4" android:duration="50" />
<item android:drawable="@drawable/wheel5" android:duration="50" />
</animation-list>
Here is the code to load and play this animation.
Code:
// Load the ImageView that will host the animation and
// set its background to our AnimationDrawable XML resource.
ImageView img = (ImageView)findViewById(R.id.spinning_wheel_image);
img.setBackgroundResource(R.drawable.spin_animation);
// Get the background, which has been compiled to an AnimationDrawable object.
AnimationDrawable frameAnimation = (AnimationDrawable) img.getBackground();
// Start the animation (looped playback by default).
frameAnimation.start()
For more information, see the guide to Animation Resources.
demaxmeister said:
Hi,
I was just wondering, is there any way to have an animated widget on the android homescreen, which stays animated and consists of multiple frames? For instance, an animated flash, gif or png sequence?
Thanks
Click to expand...
Click to collapse
did you ever figure out a simple method to creating an animated simple widget? i was just wondering b/c this is something i too would like to have.
I found this on modaco a few days ago:
http://www.youtube.com/watch?v=G-4k62ln4j4
http://android.modaco.com/content/advent-vega-vega-modaco-com/329946/3d-desktop-plugin/#entry1567646
I think it is for a tablet? Is it possible to port?
Animation in widgets is possible, check my widget.
first off, yes animated widgets are possible. second, animated gifs are not supported natively by ImageView.
http://stackoverflow.com/questions/3660209/android-display-animated-gif
however agif is supported by the WebView so you could make a widget that is just a WebView that displays an animated gif.
http://stackoverflow.com/questions/2702860/how-to-make-animated-gifs-work-from-android-webview
it will suffer performance wise but it would work.
or you could just split the animated gif and make an AnimationDrawable
http://developer.android.com/reference/android/graphics/drawable/AnimationDrawable.html
cheers!
Please try Animated Photo Frame Widget
https://play.google.com/store/apps/details?id=com.hikaru.photowidgetad
Bump.
Year 2016, still can't figure out how to animated widget.
Can somebody help me please? I tried to google for it, but all i got was gif animation loops and animations in progress bar. I want to know how do people animate the widgets like that of MIUI, DU battery saver and other weather widgets. Is there a library to do it?
I decided to give a quick update to an old app that I use quite often, but thought was in need of a UI makeover. So heres CPU Spy with Material Design!
Features:
* CPU, Device & Kernel information
* CPU core & temperature monitoring
* Shake to Refresh & Automatic Refresh
* Widget to reset timers from home screen
* Option to hide states below a certain percentage
* Automatically resets states once battery is charged
* Light & Dark themes + Auto theme based on time of day
* Background monitoring service that notifys if device doesn't enter deep sleep
Code:
[B]v3.2.1[/B]
- Updated translations
- Optimize new profile pngs
- Update some deprecated APIs
- Fix a couple NullPointerExceptions
- Fix ListView padding and text sizes
- Fix crash when showing error text
- More layout fixes for tablet devices
- Only show last 500 lines of logcat log
- Do not center full kernel version text
- Update developer circleimageview border
- Use new BottomSheet from support library
- Simplify setting logcat progress bar color
- Bind more colors/string using ButterKnife
- Simplify tinting of text selector handles
- Use wrap_content for AppCompatButton width
- Always use accentColor for text input field
- Disable user from changing color input alpha
- Update 3rd party libraries to latest versions
- Fix Running Processes title on KitKat devices
- Update charged drawable to be more material-ish
- Use new Support Vector Drawables instead of pngs
- Update colors and elevations to match guidelines
- Only set background color when cardview is shown
- Fix NullPointerException when closing InfoFragment
- Add null pointer check when setting mLogcatSummary
- Use Fragment and DialogFragment from support library
- Replace Listview with RecyclerView from support library
- Show error text when temp monitor throws an exception
[B]v3.2.0[/B]
- Rewrite CPU usage code
- Fix padding on tablet devices
- Show list of running services
- Use Butterknife resource binding
- Define size of sliding tab ArrayLists
- Only call Utils.isXposedInstalled once
- Check if a light accent color is used
- Add new developer section to Settings
- Fix colored nav bar enabling by default
- Use Chrome custom tab when opening links
- Only recreate if theme preference changes
- Rename kernel/device menus to match action
- Fix padding for credits and license layouts
- Allow multiple retries when updating states
- Catch exception when checking for an update
- Allow checking for multiple update versions
- Use primary color for deep sleep notify icon
- Allow better support for Right to Left layouts
- Fix cpu usage crashing when exiting InfoFragment
- Update libraries and build tools to latest versions
- Define ArrayList sizes for Credits and Licenses
- Use AccelerateDecelerateInterpolator for animations
- Allow catching exception when setting core visibility
- Hack to fix DiscreteSeekBar text color with light accent
[B]v3.1.9[/B]
- Fix ProgressBar height on Lollipop devices
- Remove DynamicCheckBox background color
[B]v3.1.8[/B]
- Update to latest build tools
- Move openURL method to Utils
- Use vector drawables for API 21+
- Use ArrayList instead of LinkedList
- Add Translators to Credits section
- Add CPU usage monitoring to Info tab
- Reduce number of calls to getActivity
- Only call CPUUtils.getCoreCount() once
- Add missing onCreate() to CpuSpyApp
- Remove useless code from CpuSpyPreference
- Use vector drawables for Preference icons
- Fix ProgressBar height on KitKat devices
- Use String.format() to fix lint warnings
- Automate checking if new version is available
- Add setting to change primary and accent colors
- Tint AppCompatButton to match new accent color
- Tint charged image to match new accent color
- Use new Design Support Library for sliding tabs
- Allow using String Array for changelog content
- Recreate activity when dismissing Xposed warning
[B]v3.1.7[/B]
- Updated translations
- Add support for Marshmallow
- Fix charged view card alignment
- Revert back to using text for tabs
- Use AppCompatButton for all buttons
- Adjust full kernel version text size
- Remove redundant calls to getResources()
- Show the total number of unused states
- Add bootloader information to Info tab
- Use SwitchPreference for API 21+ devices
- Update primary colors to match guidelines
- Summarize which theme is selected in Settings
- Specify initial size of getStates ArrayList<>
- Disable layout transitions during charged view
- Allow animating progress bars with Auto Refresh
- Simplify checking views when Auto Reset is enabled
- Fix background color not showing correctly on KitKat
- Move hiding states below percentage to new toolbar
- Add toolbar for hiding/resetting/restoring states
- Use ContextCompat.getColor() from support library
- Allow Settings to keep scroll position during recreate
- Override KeyEvent instead of using BackHandledFragment
[B]v3.1.6[/B]
- Fix crash on KitKat devices
[B]v3.1.5[/B]
- Check if new update is available
- Reduce total state time text size
- Update libraries to latest versions
- Animate progress bars on app launch
- Use icons instead for sliding tabs
- Updates and fixes to theme changing
- Use Roboto-Medium for snackbar actions
- Fix crash if checkCoreMonitor returns zero
- Use Butter Knife to bind button listeners
- Show warning dialog if Xposed is installed
- Use sliding cardview for full kernel version
- Return null if unable to retrieve cpu info
[B]v3.1.4[/B]
- Remove unnecessary return functions
- Remove useless call to ButterKnife.bind
- Add Exception catch for CPU core monitoring
- Add null pointer check to fix issues #69 and #70
- Dont refresh onShake if mSwipeLayout.isRefreshing
- Add local SeekBarPreference to fix KitKat margin issues
[B]v3.1.3[/B]
- More variables can be final
- Add checking runtime to Device Info
- Update Butter Knife library to v7.0.1
- Update Android Support Library to v22.2.1
- Make hasTemp() return false if file length is 0
- Update to latest gradle and android build tools
- Add service to check if device is entering deep sleep
- Catch ActivityNotFoundException if unable to open intent
[B]v3.1.2[/B]
- assert mActionBar != null
- Move app version to build.gradle
- Update Snackbar library to v2.10.10
- Add function to show/hide unused states
- Clean up SharedPreferences in CpuSpyApp
- MainActivity: Add missing @Override to onResume()
- Add option to hide states below certain percentage
- CpuSpyApp: Use SparseArray instead of HashMap
- CpuStateMonitor: Fix logging and handle exception
- Stop monitoring temperature if getTemp() returns null
- Remove usesless call to CPUUtils.getKernelVersion()
[B]v3.1.1[/B]
- Handle NFE instead of ignoring it
- Fix lint warning by using apply()
- Add support for monitoring 6-8 CPU cores
- Fix some padding issues on KitKat devices
- PrefsActivity: Add missing switch break
- Random code clean up and improvements
[B]v3.1.0[/B]
- More variables can be final
- Switch to new sliding tab layout
- Fix Auto Refresh causing crash
- Add reusable method for reading files
- Move core monitoring to CPU Info card
- Show unused states when resetting timers
- Use simple listview for open source licenses
- Enable monitoring only if fragment is visible
- Update material-dialogs library to v0.7.6.0
- New Auto theme based on the time of day
- Disable swipe to refresh if auto is enabled
- Add null pointer check when removing all views
[B]v3.0-BETA8[/B]
- Remove circle reveal animation
- Add widget info to welcome card
- Support more devices CPU temp
- Add action button back to snackbars
- Merged French translations (Micks29)
- Add colored btn_selector to buttons
- Update to latest build tools and gradle
- Fix Info text overlapping if multiple lines
- Fix setting Preference icons based on theme
- Add style for setting ActionBar elevation
- Apply dialog content color based on theme
[B]v3.0-BETA6[/B]
- Added Shake to Refresh timers
- Added CPU Temp monitoring
- Refreshed charged view layout
- Added new widget to reset timers
- Added indicator to kernel version
- Added darker primary text color
- Adjusted layout for tablets/TVs
- Updated to latest support libraries
- Use native font on API 21 and above
- Tons of code cleanup and fixes
- Fixed main card animation from being cut off
- Improve checking if states file exists
- More improvements to theme changing
- Simplified getting/setting of cpu frequencies
[B]v3.0-BETA5[/B]
- Fix memory leak when setting typeface
- Updated internal 3rd party libraries
- Removed deprecated getDrawable
- Revert using webview for dialogs
- Simplify getting/setting cpu freqs
- Decrease card animation duration
- Random code cleanup and fixes
- Improve reading of states file
- Improve reading cpu information
- Improve theme changing and dark theme
- Simplify checking which views to show
[B]v3.0-BETA4[/B]
- Add Material Ripple library (KitKat)
- Updated internal 3rd party libraries
- Animate About cardview sliding up
- Adjust padding for welcome cardview
- Add donate to settings overflow menu
- Kernel version should use singleLine
- Add custom Typeface for ActionBar title
- Revert back to using CheckBoxPreference
- Add colored navigation bar and dark theme
- Disable cpu monitoring when app is paused
[B]v3.0-BETA3[/B]
- Refreshed UI to be more Material
- Fix settings menu for KitKat devices
- Some random code clean up and fixes
- Add decimal to states view percentage
- Add new Info page with CPU/Kernel info
- Casting '_app' to 'Context' is redundant
- Sync material-dialogs library with v0.6.x
- Update snackbar and WhatsNew strings
- Add WhatsNew option in overflow menu
- Add option to reset timers when charged
- Add new WelcomeCard on first launch
- Use SnackbarManager to handle queues
- Clean up WhatsNew dialog webview usage
- Click states cardview to view unused states
- Add anonymous crash and usage reporting
- Switch to new blue primary/accent colors
- Switch to Handler instead for Auto Refresh
- Fix mBatInfoReceiver causing an exception
- Add per CPU core and frequency monitoring
[B]v2.0[/B]
- Added Pull to Refresh library
- Fixed a few more lint warnings
- New About and License menus
- Added support for KitKat and TVs
- New Material style launcher icon
- Use colored nav bar on Lollipop
- Optimized/removed unused PNGs
- Add Gmail-like Snackbar library
- Timers now reset when battery full
- Add Auto Refresh option to settings
- New WhatsNew dialog for new releases
[B]v1.2[/B]
- Fix issue when no states file found
- Adjust padding to match Material guidelines
- Rearrange home_layout and fix xml formatting
- Move 'Total State Time' above 'Unused CPU States'
[B]v1.1[/B]
- Adjusted padding a little
- Reduced some text sizes
- Removed some unused PNGs
- Removed 'Time in State' header
- Added shadow to action bar
- Fixed progress bar background color
- Added temporary icon until one can be made
[B]v1.0[/B]
- Initial release
Now available on Amazon App Store
Source: https://github.com/existz/cpuspy
Credits to the original dev @storm717.
Link to original thread: http://goo.gl/N3drrP
TODO: Updated 5/19/15
- Option to view time in state for each core (?).
Thanks man, works fine
If you want to follow progress of this app, check my G+ page... Currently looking for other devs to help out.. Please reshare if you use G+.
I should have an update very soon.
https://plus.google.com/111678887963556771807/posts/Jzdag2yhcvT
Really good thanks mate
UPDATE:
v1.1
- Adjusted padding a little
- Reduced some text sizes
- Removed some unused PNGs
- Removed 'Time in State' header
- Added shadow to action bar
- Fixed progress bar background color
- Added temporary icon until one can be made
Great ?
Finally a re-design, very well
Inviato dal mio Nexus 4
great very well .. thanks broo
much needed
thnx
So I've had quite a few people point out that the padding does not follow Material guidelines (which is 16dp).. Although I do agree that it needs spaced over a little more, but I'm not sure how I feel about 16dp yet (but it is growing on me the more I see it). Below is a screenshot of the padding adjusted to follow material guidelines..thoughts?
existz said:
So I've had quite a few people point out that the padding does not follow Material guidelines (which is 16dp).. Although I do agree that it needs spaced over a little more, but I'm not sure how I feel about 16dp yet (but it is growing on me the more I see it). Below is a screenshot of the padding adjusted to follow material guidelines..thoughts?
Click to expand...
Click to collapse
Looking between the current setup and the 16dp I personally prefer the 16dp
I'll have an update tomorrow with more UI improvements and small bug fixes. This will probably be the last update for a week or so, at least until I can get more of the important stuff done (ie pull to refresh..etc), I dont like having a bunch of small releases back to back to back, like I have been doing these last couple of days lol. But I want to get this next release out soon because it puts things more inline with Material guidelines.
existz said:
I'll have an update tomorrow with more UI improvements and small bug fixes. This will probably be the last update for a week or so, at least until I can get more of the important stuff done (ie pull to refresh..etc), I dont like having a bunch of small releases back to back to back, like I have been doing these last couple of days lol. But I want to get this next release out soon because it puts things more inline with Material guidelines.
Click to expand...
Click to collapse
Tbh as an end user I personally prefer having larger releases with more content unless it is just a bug fix release take your time to make a stellar product.
UPDATE:
v1.2
- Fix issue when no states file found
- Adjust padding to match Material guidelines
- Rearrange home_layout and fix xml formatting
- Move 'Total State Time' above 'Unused CPU States'
This will probably be the last update for a week or two, at least until im able to get more of the important stuff done (ie pull to refresh..etc), sorry for all the updates back-to-back.
Great man, thanks
I might take up the offer on the icon. Hello, existz, it's nice to see you again; back from the DHD days.
kingofnice said:
I might take up the offer on the icon. Hello, existz, it's nice to see you again; back from the DHD days.
Click to expand...
Click to collapse
The good ole' days
existz said:
The good ole' days
Click to expand...
Click to collapse
I have made a similar app before and has more functionalityy than this
I Just recently updated it with material design )
If you want to save some time you can update that one
https://www.dropbox.com/s/gmu3y80gynd1t4y/Cpu_States_2.0.0b199.apk?dl=0
If you want the source please PM me )
@existz
Do you mind changing that the app requires a touchscreen there are devices that do not have touchscreen such as TV based devices
From developer.android.com for devices that use android.hardware.faketouch
"Note: Because applications require the android.hardware.touchscreen feature by default, if you want your application to be available to devices that provide a fake touch interface, you must also explicitly declare that a touch screen is not required by declaring <uses-feature android:name="android.hardware.touchscreen" android:required="false" />"
Hi, There
IMPORTANT - This topic is for experienced users ONLY
Themes As you all know already Theme Engine in Lollipop did not give so much to do things on 4.4 KK.
Sony has blocked us the opportunity to Lollipop.
But it's already past!!!
Today I discovered a way to add the ability to unlock the Xperia Theme Engine.
Unfortunately it work in all of the app you need to edit them separately.
I will show you an example of Sony Lollipop SystemUI.apk. But the scheme is similar in other Sony apps
Before we start a little bit of knowledge:
Each application Sony Xperia contains somc_skin_permissions.xml file.
It is always in the folder res / xml / somc_skin_permissions.xml
This is the file that gives permission for Themes. All values that are out there give you the ability to change them using themes. If it is not missing there possibilities to change it using the Sony themes
What we need:
-To ApkTool supported Lollipop
-Notepad
-Brain
Lets Start
First Decompile Your Sony app and find file somc_skin_permissions.xml . I will show you an example of the systemUI.
How add permission to changes colors:
Add red lines between (<overlay-resources>) And next group filters ( <filter-group group="status-bar">)
Code:
<?xml version="1.0" encoding="utf-8"?>
<overlay-resources>
[COLOR="Red"] <filter-group group="color">
<filter type="type" value="color" />
</filter-group>[/COLOR]
<filter-group group="status-bar">
<filter type="type" value="color,bitmap,nine-patch,vector" />
<filter type="lightness" value="0.425" tolerance="0.425">
<filter type="type" value="color" />
</filter>
.............
To the End Add color values from SystemUI ( Colors.xml ) I add only this values , but you can add all from colors.xml
Code:
.....
<overlay id="@bool/somc_enableKeyButtonGlow" />
[COLOR="red"] <overlay id="@color/system_bar_background_opaque" filters="color" />
<overlay id="@color/system_bar_background_semi_transparent" filters="color" />
<overlay id="@color/system_bar_background_transparent" filters="color" />
<overlay id="@color/system_primary_color" filters="color" />
<overlay id="@color/system_secondary_color" filters="color" />
<overlay id="@color/system_accent_color" filters="color" /> [/COLOR]
</overlay-resources>
Save it
From now , your systemUI have permission to change the colors with Themes
Of course, they must be placed in the file
How add permission to changes navigation buttons:
Add this lines .( Ic_sysbar is png files navigation buttons )
Code:
<overlay id="@drawable/somc_navbar_ime_switcher_btn_immersive_land" filters="sysbar-key-land" />
<overlay id="@drawable/somc_navbar_ime_switcher_btn_no_background_land" filters="sysbar-key-land" />
[COLOR="red"] <overlay id="@drawable/ic_sysbar_back" filters="sysbar-key-port" />
<overlay id="@drawable/ic_sysbar_back_land" filters="sysbar-key-land" />
<overlay id="@drawable/ic_sysbar_home" filters="sysbar-key-port" />
<overlay id="@drawable/ic_sysbar_home_land" filters="sysbar-key-land" />
<overlay id="@drawable/ic_sysbar_recent" filters="sysbar-key-port" />
<overlay id="@drawable/ic_sysbar_recent_land" filters="sysbar-key-land" />
<overlay id="@drawable/ic_sysbar_menu" filters="sysbar-key-port" />
<overlay id="@drawable/ic_sysbar_menu_land" filters="sysbar-key-land" />
<overlay id="@drawable/ic_sysbar_back_ime" filters="sysbar-key-port" />
<overlay id="@drawable/ic_sysbar_back_ime_land" filters="sysbar-key-land" />[/COLOR]
<overlay id="@bool/somc_enableKeyButtonGlow" />
.......
Save and compile your app
From now , your systemUI have permission to change the ic_sysbar buttons with Themes
Soon I will add more examples. But a lot can be downloaded from 4.4 KK apps
You have to keep in mind that the Group filters Varying in different applications.
But you can see how they look applications KK and what is missing
Attached files:
SystemUI of values in unlocked by @serajr
Theme which changes colors and buttons.
Mod and not mod files somc_skin_permissions.xml
Creadits:
RXS MoonBreakers Team
res
res3
res3
like always top work bro.
tanx
alinolaw71 said:
like always top work bro.
tanx
Click to expand...
Click to collapse
Thanks. I'm trying to find solution without mod apps. But don't know whay isn't possible. In kk everything works and some value isn't added.
Ambor said:
Thanks. I'm trying to find solution without mod apps. But don't know whay isn't possible. In kk everything works and some value isn't added.
Click to expand...
Click to collapse
Giving permissions isn't enough for runtime-skinning, it's only the starting point. The app must also handle the theme changes while the app is running. That can be done only in smali. I know because I made my expanded status bar (notifications header and quick settings background) color change the moment you change a theme (instead of having to reboot the device to apply the changes).
And you can't do that without modding the apps, each app handles it on its own behalf.
IaguCool said:
Giving permissions isn't enough for runtime-skinning, it's only the starting point. The app must also handle the theme changes while the app is running. That can be done only in smali. I know because I made my expanded status bar (notifications header and quick settings background) color change the moment you change a theme (instead of having to reboot the device to apply the changes).
And you can't do that without modding the apps, each app handles it on its own behalf.
Click to expand...
Click to collapse
I know that, but for now this is the only way that I know that the theme work.
KK theme work, even as there was no value in skin_permission
At Lollipop if I add value is not in skin_permission the theme file zip does not work.
try to use my theme for stock systemUI. Your buttons do not change.
I think that this is not a big problem for Members that you have to restart the phone to do.
On KK need to restart phone and it was no one complained
As you have any ideas
would love to hear
Regards
I know where are smili files in KK. But where are in Lollipop
Ambor said:
I know where are smili files in KK. But where are in Lollipop
Click to expand...
Click to collapse
Hah, the smali files are in the same place XD
Ambor said:
I know that, but for now this is the only way that I know that the theme work.
KK theme work, even as there was no value in skin_permission
At Lollipop if I add value is not in skin_permission the theme file zip does not work.
try to use my theme for stock systemUI. Your buttons do not change.
I think that this is not a big problem for Members that you have to restart the phone to do.
On KK need to restart phone and it was no one complained
As you have any ideas
would love to hear
Regards
Click to expand...
Click to collapse
Most likely it's because that MyExampleTheme isn't implemented correctly. Try the attached theme on a stock SystemUI and you'll see that the navigation buttons change immediately, no restart needed.
IaguCool said:
Hah, the smali files are in the same place XD
Most likely it's because that MyExampleTheme isn't implemented correctly. Try the attached theme on a stock SystemUI and you'll see that the navigation buttons change immediately, no restart needed.
Click to expand...
Click to collapse
Your theme have bug brother. I know what part of theme request reboot. Button will not changed in album apk
Ambor said:
Your theme have bug brother. I know what part of theme request reboot. Button will not changed in album apk
Click to expand...
Click to collapse
1st - It's not my theme.
2nd - I don't know what you mean. What does it have to do with Album apk?
IaguCool said:
1st - It's not my theme.
2nd - I don't know what you mean. What does it have to do with Album apk?
Click to expand...
Click to collapse
Appy theme button will change
Go to Sony album apk and see ( buttons will back to stock )
IaguCool said:
Hah, the smali files are in the same place XD
Most likely it's because that MyExampleTheme isn't implemented correctly. Try the attached theme on a stock SystemUI and you'll see that the navigation buttons change immediately, no restart needed.
Click to expand...
Click to collapse
Not all applications are in the same place ...
And as you know where they are then why do not you share in ???
Or you do not guide how to do it. We are happy to see it ...
I came up with a way for action Themes.
But I see that you're so smart with know better ... So we are waiting for your guide ...
Regards
Ambor said:
Not all applications are in the same place ...
And as you know where they are then why do not you share in ???
Or you do not guide how to do it. We are happy to see it ...
I came up with a way for action Themes.
But I see that you're so smart with know better ... So we are waiting for your guide ...
Regards
Click to expand...
Click to collapse
I never said you weren't right, I said that it's just incomplete, so pick your tone very carefully. Sorry, not dealing well with narcissistic pricks.
And just for your information - maybe adding the navigation buttons is good (for old themes compatibility) but for colors?
Colors should not be set in systemui.zip, because SystemUI.apk use system-wide colors, which can be found in framework-res.apk and the basic are:
Code:
<color name="somc_color_dark_primary_dark">#ff158597</color>
<color name="somc_color_primary_dark">#ff009faf</color>
<color name="somc_color_accent_dark">#ffd15b40</color>
<color name="somc_color_dark_primary_light">#ff2699a5</color>
<color name="somc_color_primary_light">#ff2ab9d2</color>
<color name="somc_color_accent_light">#ffed6642</color>
<color name="somc_color_background_light">#fffafafa</color>
And framework-res.apk already has the required permissions built-in:
Code:
<overlay id="@color/somc_color_dark_primary_dark" filters="color" />
<overlay id="@color/somc_color_primary_dark" filters="color" />
<overlay id="@color/somc_color_accent_dark" filters="color" />
<overlay id="@color/somc_color_dark_primary_light" filters="color" />
<overlay id="@color/somc_color_primary_light" filters="color" />
<overlay id="@color/somc_color_accent_light" filters="color" />
The themes must override these in android.zip, not systemui.zip, unless you want to do everything twice and add pointless permissions and exactly the same color values in another zip file of the theme.
Now if you want to tweak SystemUI to use the system-wide colors, you don't need extra permissions, you need to set system-wide references:
First you need to set "system_primary_color" to use "@android:color/somc_color_dark_primary_dark" (This is the slightly darker one, by default).
Then you need to set "system_secondary_color" to use "@android:color/somc_color_primary_dark" (This is the slightly brighter one, by default).
Then you need to set "system_accent_color" to use "@android:color/somc_color_accent_dark".
Then you need to set the color "system_bar_background_opaque" to use "@color/system_primary_color".
You can leave the "system_bar_background_semi_transparent" permission in, if you really think that changing the semi-transparent color is a good idea.
The color "system_bar_background_transparent" should NEVER be skinnable, because, well - it's transparent!
There is an extra step needed to make sure the navigation bar is black in "lights-out" mode (like for example - in desk clock).
Now I'm looking to unify the color changes made to the status bar and the navigation bar, since they are set separately by apps, example - Gmail app's style sets only the status bar to red:
Code:
<item name="android:statusBarColor">@color/mail_activity_status_bar_color</item>
While to change the navigation bar color the style needs to set "android:navigationBarColor" also.
To do that, it's only by editing smali in android.policy.jar.
Here's the current result, in the attachment. Some apps show a transparent navigation bar background instead (like Gmail and Google Keep) which I'm trying to solve, but others colorize the navigation bar correctly.
That being said, each app can set the android:navigationBarColor item in their styles.xml, they just chose not to.
IaguCool said:
I never said you weren't right, I said that it's just incomplete, so pick your tone very carefully. Sorry, not dealing well with narcissistic pricks.
And just for your information - maybe adding the navigation buttons is good (for old themes compatibility) but for colors?
Colors should not be set in systemui.zip, because SystemUI.apk use system-wide colors, which can be found in framework-res.apk and the basic are:
Code:
<color name="somc_color_dark_primary_dark">#ff158597</color>
<color name="somc_color_primary_dark">#ff009faf</color>
<color name="somc_color_accent_dark">#ffd15b40</color>
<color name="somc_color_dark_primary_light">#ff2699a5</color>
<color name="somc_color_primary_light">#ff2ab9d2</color>
<color name="somc_color_accent_light">#ffed6642</color>
<color name="somc_color_background_light">#fffafafa</color>
And framework-res.apk already has the required permissions built-in:
Code:
<overlay id="@color/somc_color_dark_primary_dark" filters="color" />
<overlay id="@color/somc_color_primary_dark" filters="color" />
<overlay id="@color/somc_color_accent_dark" filters="color" />
<overlay id="@color/somc_color_dark_primary_light" filters="color" />
<overlay id="@color/somc_color_primary_light" filters="color" />
<overlay id="@color/somc_color_accent_light" filters="color" />
The themes must override these in android.zip, not systemui.zip, unless you want to do everything twice and add pointless permissions and exactly the same color values in another zip file of the theme.
Now if you want to tweak SystemUI to use the system-wide colors, you don't need extra permissions, you need to set system-wide references:
First you need to set "system_primary_color" to use "@android:color/somc_color_dark_primary_dark" (This is the slightly darker one, by default).
Then you need to set "system_secondary_color" to use "@android:color/somc_color_primary_dark" (This is the slightly brighter one, by default).
Then you need to set "system_accent_color" to use "@android:color/somc_color_accent_dark".
Then you need to set the color "system_bar_background_opaque" to use "@color/system_primary_color".
You can leave the "system_bar_background_semi_transparent" permission in, if you really think that changing the semi-transparent color is a good idea.
The color "system_bar_background_transparent" should NEVER be skinnable, because, well - it's transparent!
There is an extra step needed to make sure the navigation bar is black in "lights-out" mode (like for example - in desk clock).
Now I'm looking to unify the color changes made to the status bar and the navigation bar, since they are set separately by apps, example - Gmail app's style sets only the status bar to red:
Code:
<item name="android:statusBarColor">@color/mail_activity_status_bar_color</item>
While to change the navigation bar color the style needs to set "android:navigationBarColor" also.
To do that, it's only by editing smali in android.policy.jar.
Click to expand...
Click to collapse
Bro no need to edit smili
you only add this
Code:
<item name="colorPrimary">@color/somc_color_primary_dark</item>
<item name="colorPrimaryDark">@color/somc_color_dark_primary_dark</item>
<item name="statusBarColor">?colorPrimaryDark</item>
<item name="navigationBarColor">?colorPrimary</item>
[COLOR="Red"] <item name="somcSkinnableTranslucentBars">false</item>[/COLOR]
This code block SONY SYSTEMUI dimming
<item name="somcSkinnableTranslucentBars">false</item>
and navi bar will be dimming colorPrimary
and statusbar to colorPrimaryDark
These things I have done 1 month ago ...
Look:
http://forum.xda-developers.com/cro...-modded-stock-tele-service-semcphone-t3059884
http://forum.xda-developers.com/cro...d-theme-accent-widgets-sony-lollipop-t3069971
Ambor said:
Bro no need to edit smili
you only add this
Code:
<item name="colorPrimary">@color/somc_color_primary_dark</item>
<item name="colorPrimaryDark">@color/somc_color_dark_primary_dark</item>
<item name="statusBarColor">?colorPrimaryDark</item>
<item name="navigationBarColor">?colorPrimary</item>
[COLOR="Red"] <item name="somcSkinnableTranslucentBars">false</item>[/COLOR]
This code block SONY SYSTEMUI dimming
<item name="somcSkinnableTranslucentBars">false</item>
and navi bar will be dimming colorPrimary
and statusbar to colorPrimaryDark
These things I have done 1 month ago ...
Look:
http://forum.xda-developers.com/cro...-modded-stock-tele-service-semcphone-t3059884
http://forum.xda-developers.com/cro...d-theme-accent-widgets-sony-lollipop-t3069971
Click to expand...
Click to collapse
Did you even look at the screenshots? What you mention is navigation bar colorizing in SONY apps. What I'm talking about is colorizing in ALL others apps, according to the app's specific theme, not your Xperia theme accent. The screenshots show you how the nav bar's color is changed to red in YouTube, while changes to dark-green in Whatsapp and light-green in Pushbullet. Those are NOT theme accent colors, those colors are set by the application.
IaguCool said:
Did you even look at the screenshots? What you mention is navigation bar colorizing in SONY apps. What I'm talking about is colorizing in ALL others apps, according to the app's specific theme, not your Xperia theme accent. The screenshots show you how the nav bar's color is changed to red in YouTube, while changes to dark-green in Whatsapp and light-green in Pushbullet. Those are NOT theme accent colors, those colors are set by the application.
Click to expand...
Click to collapse
this block dimming
<item name="somcSkinnableTranslucentBars">false</item>
Stock valiue is
<item name="somcSkinnableTranslucentBars">true</item>
I'm not talking to you. You do not understand me. I know the method I have described.
and the effect will be similar
Code:
<style name="Theme.Material" parent="@style/Theme">
<style name="Theme.Material.Light" parent="@style/Theme.Light">
<item name="navigationBarColor">?colorPrimary</item>
besides colors are just an example.
This way you can give permission to a lot of other things as changing PNG files or other icons.
I do try to change icons with just a Theme...happy to see him
Instead of spamming my topic, do something useful write a guide.
Ambor said:
Instead of spamming my topic, do something useful write a guide.
Click to expand...
Click to collapse
Do you even know what "spamming" means? You've got some real issues.
Re: Kernel Default values
I wish to maintain the changes I have made to my current Kernel (ElementX) even after a factory reset.
I adjusted the RGB colour values to prevent screen retention/screen burn and wish for these settings to be the default values, how would I be able to do that?