[Request] VSW S3 Code Improvements - Galaxy S III Q&A, (US Carriers)

As the VZW source code has been released and we now have root, I would like to make a request of the developers.
Can we improve on Samsungs stock image?
I actually kind of like what Samsung has done with their implementation of Android.
Is it possible to add swipe to expand notifications to the launcher and rebuild the stock tethering app so it doesn't check your account for the feature?
Anyone else have any idea's on minor changes to improve the stock image?

Related

[Q] how to make the stock launcher widgets visible in other launchers

Dear m8s
there's no doubt that Xperis S stock launcher is awesome
but still i want to experience other launchers
for me, i found Nemus launcher is so great
my only problem is that i can't place the stock widgets (timescape) and Accuweather on any of the home screens
as it's not available in Widgets list in any launcher except the stock one only
tried some other launchers to check, and result is still the same
available only in stock launcher widgets list
and not available for any other launcher
My Q is, is there any method i could make the stock launcher widgets list available for all launchers
i'm sorry to place a Q in this forum, but i think my Q is related to this forum only
i'm not trying to break any rules
Thanks in advance.
You can't use Sony widgets with other launchers.
I've wanted this for a while but my research yielded nothing :-(
Sent from my XperiaS via subspace beacon.
Not possible...sorry and actually that is the reason I didn't move to other launchers...
i really can't believe it that Devs can cook a complete ROM
and they r unable to port some widgets only !!
ChIcO*GsM said:
i really can't believe it that Devs can cook a complete ROM
and they r unable to port some widgets only !!
Click to expand...
Click to collapse
You see, when you modify the stock firmware, you don't have sources for anything but the kernel. You can add tweaks and overclocking and init.d without going deeper, but after that it's all decompiling. You probably know a toolchain named smali. If you don't, smali is like assembly for Android. You can't get java code from a built app, just as you can't get C++ from an EXE. Now say we want a part of that app ( widgets ). This is the very moment smali comes in. With smali, you can get some very basic, assembly like code from a prebuilt app. That's the code Android uses to run it. And that's where the interesting things are. To allow using Sony widgets on other launchers, you need to find the code responsible for loading them, displaying them and all the code the previous two depend on. It can be in the launcher or in the frameworks, so it's two huge source trees that you can't even search through. When you get all this code, you need to integrate it into your launcher app. Ironically, Android doesn't support smali code directly, so you have to either rewrite it back into Java ( which is hard) or build your launcher first and then add the code using smali ( which is not easier) .
K900 said:
You see, when you modify the stock firmware, you don't have sources for anything but the kernel. You can add tweaks and overclocking and init.d without going deeper, but after that it's all decompiling. You probably know a toolchain named smali. If you don't, smali is like assembly for Android. You can't get java code from a built app, just as you can't get C++ from an EXE. Now say we want a part of that app ( widgets ). This is the very moment smali comes in. With smali, you can get some very basic, assembly like code from a prebuilt app. That's the code Android uses to run it. And that's where the interesting things are. To allow using Sony widgets on other launchers, you need to find the code responsible for loading them, displaying them and all the code the previous two depend on. It can be in the launcher or in the frameworks, so it's two huge source trees that you can't even search through. When you get all this code, you need to integrate it into your launcher app. Ironically, Android doesn't support smali code directly, so you have to either rewrite it back into Java ( which is hard) or build your launcher first and then add the code using smali ( which is not easier) .
Click to expand...
Click to collapse
in short words
i have to wait till Android support this smali
or to wait for some Dev to wast his time on this
as i dun have any other solution yet
So,Waiting .....

[Q] Implementing a Windows 8 style progress ring animation in Android

Hello everyone,
I've been searching for some more info on the new spinner/preloader animation in the new Windows 8 UI, and I was hoping I might be able to find someone here that might be able to assist me. My first preference is that I would like to add it as a part of my theme chooser theme via the T-Mobile Theme Engine for cm-10.1 or similar Android 4.2 AOSP-based ROMs. I'm thinking that this may not be possible, and if not I would still like to add it to my ROMs that I compile from source (currently I've been using PAC-man as my source, which is a hybrid of cm-10.1, AOKP jb-mr1, and PA 3.1+) . I'm not sure exactly where the file resources for it are located on the Win8 OS, however I *think* it might be in C:\Windows\System32\Windows.UI.Xaml.dll. I did find these guides on the Microsoft Dev Center site, though:
Quickstart: adding progress controls (Windows Store apps using JavaScript and HTML)
How to style progress controls (Windows Store apps using JavaScript and HTML)
which refers to the animation I'm looking for as an Indeterminate Progress Ring. I also found some additional info in the API reference here:
ProgressRing class
ProgressRing constructor
Progress element | Progress object
Here's a crude animated gif of the progress ring animation to give you an idea of what I'm referring to (it's white with a transparent background so you can't see it if I embed it directly here):
http://imgur.com/uOcWPjy
And here's a pretty close representation of it coded in CSS3:
http://codepen.io/jameswyse/pen/uisvk
(note: the animation at that link displays fine when I'm on my Windows partition, but doesn't seem to display correctly with either Firefox or Chrome/Chromium on my Linux partition)
So I guess my question is, how might I be able to incorporate that animation into my ROM to replace the default Activity Circle animation (or spinner animation)? I would assume that it would be better to implement it through java rather than trying to implement it using a gif or a frame animation that would require adding 103 additional images to the source files just for this animation. However, I would consider myself a total n00b when it comes to coding in java for Android. I can kang some code together or modify bits and pieces of existing code without too much trouble, but I've never tried to write anything from scratch.
Any help would be much appreciated. Thanks.

[Q] How to implement animation-list (or similar) in an Android Live Wallpaper

I recently downloaded this Android LWP source code (http://www.codeproject.com/Articles/108390/How-To-Create-Android-Live-Wallpaper) to get started with LWP development. The thing is, I'd like to implement a frame-by-frame animation with a set of predefined images. I've been testing animation-list in a XML file but inside an application itself, not with a LWP.
Does anyone have an idea of how I can achieve that or something similiar?
Thank you in advance, I'd truly appreciate any guidance.
Try to implement it in the same way (actually, a live wallpaper is much like any other android app). You can also use OpenGL to take advantage of the hardware acceleration (using AndEngine, for example).
If you wish more tutorials, take a look here.

[Q] Need help for creating NavBar Replacement

I wish to create a NavBar replacement sort of like a floater and need pointers on where to start......
Sort of like Pie Controls and a Toucher combined in some sort of idea I'm having.
I want to know where and how I can start.....
I think maybe I'll need xposed and standout libraries.
But just some pointers in general on where to start coding from and how to do it
coz I believe this project will need root capabilities and I have only developed a basic textbox and spinner database projects uptil now.

How do I skin my custom ROM?

I'm trying to make a custom ROM (for now, only for x86, because I don't want to flash anything on my actual phone) and I want to modify the default UI throughout the entire system. This includes colors, outlines, corners on buttons, etc. Is there something in the AOSP source that would allow me to make these changes? I'm hoping I don't have to open the source for each individual application to change the look.
MasterPixelDestroyer said:
I'm trying to make a custom ROM (for now, only for x86, because I don't want to flash anything on my actual phone) and I want to modify the default UI throughout the entire system. This includes colors, outlines, corners on buttons, etc. Is there something in the AOSP source that would allow me to make these changes? I'm hoping I don't have to open the source for each individual application to change the look.
Click to expand...
Click to collapse
Sorry to say that but you'll have to mod each and everyone of your apps to have those changes (outlined, colors).
I've heard of a substratum theme that might fit your expectations, but I you want to do it yourself (which is more fun) you'll have to modify each and every apps. When you'll mod systemUI your modification will go "system wide" (quick settings and stuff) but the phone app won't be changed.
Have a good day
@MasterPixelDestroyer
Several XPosed Framework modules exist that do the job.
Study their source code to get an idea how to tweak system UI ( read: home screen ) is done.

Categories

Resources