Ye I tried Clean Project option already. The error appeasers right after compiling a clean build or any change. Though no error on building the app.
[SOURCE CODE][DEV TOOL][SDK 21+]6thGear RomControl v2.+ for Devs
- Thread starter daxgirl
- Start date
Ye I tried Clean Project option already. The error appeasers right after compiling a clean build or any change. Though no error on building the app.
Uninstall Android Studio completely from everywhere on ur pc , then after uninstall it & deleted all files & folders related to a.s restart ur pc then reinstall it again with updated everything all plugins , repository , gradle , then. Try it again , only this way fixed my errors when i start working on v2.1 , ..
Solved !!!!
Many Thanks to @thereassaad for his tip [emoji6]
http://forum.xda-developers.com/showthread.php?p=68670992
So for use command as app
ackageName ToKill, app:dependentValue, or any other commands witch are working in ui_prefs.xml into all others xml prefs :Exemple for phone_prefs.xml
I replace at the beginning of xml :
Code:
<PreferenceScreen xmlns:android="http://schemas.android.com/apk/res/android">By
Code:
<PreferenceScreen xmlns:android="http://schemas.android.com/apk/res/android" xmlns:app="http://schemas.android.com/apk/res-auto">
Last edited:
i have got this during gradle built any one help me a im building RC for the first time..
PHP:
4:43:11 PM Gradle sync started
4:43:31 PM Gradle sync failed: Unable to start the daemon process.
This problem might be caused by incorrect configuration of the daemon.
For example, an unrecognized jvm option is used.
Please refer to the user guide chapter on the daemon at https://docs.gradle.org/2.14.1/userguide/gradle_daemon.html
Please read the following process output to find out more:
-----------------------
Error occurred during initialization of VM
Could not reserve enough space for object heap
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
Consult IDE log for more details (Help | Show Log)
4:43:47 PM Error Loading Project: Cannot load 2 modules Details...Delete all gradle golders / files from everywhere on ur pc then try to sync it again & let it got the updated by itself or u need to launch the latest gradle versions check google about this ,,
Need some help
i have build the rc and it runs fine in emulator and in phone
when sharing to git -> success
but all files are not getting synced
See this pics all the green and red marked files are not present in git
For two drawable images its marked as red and is not present in git account
and new xml prefs are marked green and not shown in git
but its showing in rc fine
when i click->> Validate for some of those red files I get This error
My github link
https://github.com/yash92duster/Wanted_Rom_Control/tree/master/app/src/main/res
Sorry if i shouldn't ask this but i cant find any proper solution
thanks in advance
i have build the rc and it runs fine in emulator and in phone
when sharing to git -> success
but all files are not getting synced
See this pics all the green and red marked files are not present in git
For two drawable images its marked as red and is not present in git account
and new xml prefs are marked green and not shown in git
but its showing in rc fine
when i click->> Validate for some of those red files I get This error
My github link
https://github.com/yash92duster/Wanted_Rom_Control/tree/master/app/src/main/res
Sorry if i shouldn't ask this but i cant find any proper solution
thanks in advance
Last edited:
Right click on files which are not synced > Git > addNeed some help
i have build the rc and it runs fine in emulator and in phone
when sharing to git -> success
but all files are not getting synced
See this pics all the green and red marked files are not present in git
View attachment 3884091
View attachment 3884092
View attachment 3884093
For two drawable images its marked as red and is not present in git account
and new xml prefs are marked green and not shown in git
but its showing in rc fine
View attachment 3884100View attachment 3884101
when i click->> Validate for some of those red files I get This error
My github link
https://github.com/yash92duster/Wanted_Rom_Control/tree/master/app/src/main/res
Sorry if i shouldn't ask this but i cant find any proper solution
thanks in advance
Then commit and push changes again.
And yeah you can find proper solutions. Android studio git supports is well documented and you only needed to google. Tons of advice and answers on Google documentation and stackoverflow.
Sent from my SM-N920C using Tapatalk
Hi all,
Is there a way for RC2.1 to auto switch ? I explain : i use a mod witch show Analog clock in Lockscreen instead of stock numeric one.
If i switch off Normal clock i would like to Analog clock switch on automaticly and virse-versa.
Is it possible ?
Is there a way for RC2.1 to auto switch ? I explain : i use a mod witch show Analog clock in Lockscreen instead of stock numeric one.
If i switch off Normal clock i would like to Analog clock switch on automaticly and virse-versa.
Is it possible ?
Did you miss the reverse dependency or what's wrong with you??? ???
Sent from my SM-N920C using Tapatalk
No i do reverse dependency but it only disable second switch if first one is not enable. It not put on first and put off second off automaticly and virse-versa. So like a command :
if first switch is on then second switch is off
if first switch is off then second switch is on
Or i miss something...
Last edited:
Oh I see. You want cross setChecked... That needs java edits, dear.
Sent from my SM-N920C using Tapatalk
Java edits can always be done. Question is whether you're willing to go into java for that.
Sent from my SM-N920C using Tapatalk
Hi @daxgirl
I want add more themes without default themes on rom control v2
On rom control v1 more easy but on v2 is little more difficult..
You can help me with it..
Thanks!
I want add more themes without default themes on rom control v2
On rom control v1 more easy but on v2 is little more difficult..
You can help me with it..
Thanks!
Is that a question? Are you asking if I can help you with it? Because if you are, the answer is in the op. No theming questions allowed. No theming requests. This is not an application, this is a source code. It comes with no support and no warranty. Anything you do with it is your right and responsibility.
If you're telling me that I can help you with it, well... in that case... LOL
You're a noob with any language, my friend. Nevertheless, this is not a request thread. We gave you a code, you can do what you want with it. Including java edits. It is your right. So go ahead and make an edit to cross switch. Read on SO, read on documentation. You can do it.
Please how i can call this in Rc?
<dashboard-tile android:icon="@drawable/ic_setting_grid_autostarts" android:id="@id/autostarts_settings" android:title="@string/autostarts_title" android:fragment="com.android.settings.autostarts.LewaManageAutostarts" settings:tilecategoryid="@id/system_section" settings:removetileapps="KIOSKCONTAINER" />
Sent from my SM-N930F using XDA-Developers mobile app
<dashboard-tile android:icon="@drawable/ic_setting_grid_autostarts" android:id="@id/autostarts_settings" android:title="@string/autostarts_title" android:fragment="com.android.settings.autostarts.LewaManageAutostarts" settings:tilecategoryid="@id/system_section" settings:removetileapps="KIOSKCONTAINER" />
Sent from my SM-N930F using XDA-Developers mobile app
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
55
6htGear Rom control V2.1
By @Wuby986 & Daxgirl
Hello everyone!
So here we go again... V2.0
Big thanks:
We would like to begin from crediting people, who gave us ideas, inspiration and, most importantly, their free time, in order to make v2.0 a reality.
To our dearest friends and talented developers, @tdunham and @DaOldMan:
Guys, you OWN this. You made this happen. You pushed us and we pushed you, and together, you, us and rom control, have grown to be what we are today.
No thanks can ever be enough for long nights of applying patches, merging sources, connecting through teamviewer and working out kinks together. @Wuby986 and I are forever in your debt.
Why different thread?
1. The entire application is different. It barely qualifies as an update anymore.
2. All the preferences are different. The way they work is different. It requires new way of doing things. Radically new.
3. new support library and new basic structure.
4. To sum it up... it's too different to maintain same thread for both versions
Project characteristics:
1. Rom control is an open source project, designed to provide rom builders with a core code for compiling android application for controlling core functions of their roms and mods through Content Provider of Settings.System sqlite table
2. Rom control is designed with consideration of the fact that most rom builders do not have sufficient skills in original android development to build application with this functionality on their own
3. The emphasis is given in this version (even more than previous one) to outsource most conditions and attributes to xml, and so to minimize the need of the user (rom builder) to be subjected to java programming
4. In addition to familiar utilization of ContentResolver to pass data between RomControl and system, the project offers additional properties, such as file based preference, URI selection preference, Direct intent to shortcut app preference, preference listing image thumbnails for previews, script running preference, automated template for "About Us" section, automated dialog for changelog, backup and restore finctionality and more.
5. The project is designed to be compiled in Android Studio using the latest sdk tools and gradle tools.
6. The project essentially is designed to be a system application with privileged access, and therefore needs to be installed in /system/priv-app to be granted some of its permissions
7. The project requires root access for some of its functionality. Mainly running shell scripts with su and killing some app processes.
License and sharing policy:
1. This project is distributed under GNU General Public License as open source code. The copy of said license can be obtained and reviewed here
2. As such, this project is protected from claiming exclusivity by anyone.
3. Any developer wishing to use this code, with accordance to the license, must provide full source code for each updated version. That means, for any new version of the rom including updated RomControl application, a link to full source code of the latest version must be provided.
4. By modifying and using this code, you automatically accept the License conditions and must be compliant with GPL, as stated below:
5. You're under no obligation to thank us, credit us or tag us in your official postings while distributing your copy.
6. You ARE, however, prohibited from removing our copyright information from our source code.
7. You are obligated to keep the code open under GPL. Failure to provide sources for updated copies of your work will result in complaint first to XDA officials for license infringement and further to GPL legal department.
8. Using the source code on any other forum outside of xda is of course allowed with accordance to the license and sharing policy, provided the sources are kept open and obtainable by anyone.
9. Using apktool to compile a copy of this code after making changes in the decompiled form of someone else's application is strictly prohibited, as the developer will not be able to provide full open source of their version. Any illegal use of any copy of this project can be and should be legally stopped by the owner of the code copy.
10. This voids rule number 12 of xda promising a developer exclusivity over their product. This product is yours, but the code belongs to the public. You are NOT TO HOLD COPY OF ROM CONTROL EXCLUSIVE.
Open source libraries included in this project:
1. RootTools by Stericson
2. Sergey Margaritov's ColorPickerPreference modified to adopt to our needs
3. CircleImageView by hdodenhof
Project requirements:
1. Installed and updated android sdk, including but not limited to:
Android SDK Build-Tools 24
Android SDK Platform-Tools 24
Android support repository 33
Google repository, rev 29
Latest android support library
2. Android studio version AT LEAST the latest stable version (currently 2.1.2), you can use the canary channel as well, currently on 2.2.0 preview 5.
3. Updated gradle tools
4. Working knowledge of importing project into Android Studio and troubleshooting gradle sync. If you don't know how to, Google it.
5. EXTENSIVE knowledge in android modding:
This project is for rom developers and modders. It helps coordinate between your users and your mods. If you don't build roms or don't have mods, this project means nothing to you.
What support you can expect to get:
1. Code explanation regarding major functionality
2. Adding new preferences and navigation items
What support you CANNOT expect:
1. Setting up android studio
2. Debugging gradle issues and compiling
3. Changing colors, strings, adding themes, design, changing setup... - Android documentation is vast and Stackoverflow is even vaster.
4. Smali modding
5. Private messaging support - DO NOT EVEN TRY
6. Asking for compiled apk file.
This is NOT an application thread. This is NOT an application. This is a SOURCE CODE for MAKING application.
The answer to a question "Can someone give me a compiled version" is "And what are you going to do with it?"
Project main Git repository:
Here
Thread list of contents:
XDA:DevDB Information
6thGear RomControl v2.0, Tool/Utility for all devices (see above for details)
Contributors
daxgirl, wuby986, tdunham, DaOldMan
Version Information
Status: Testing
Current Stable Version: 2.1
Stable Release Date: 2016-08-26
Created 2016-07-06
Last Updated 2016-08-26
Latest Update details:
Post number 195
23
Step 1 - Importing the project:
1. Perform full installation of the latest stable version of Android Studio in your environment. You can find info about stable and canary releases here
2. You can have more than one version of android studio installed on single platform. For more information please read further on the same page in section Using Multiple Android Studio Versions. I personally do recommend the latest canary build, which is currently AndroidStudio 2.2.0 preview 5. But you can always go with the stable release. Or beta channel.
3. Make sure your sdk is updated, including sdk for platform 24 (nougat). The compile sdk for this project is 24.
4. Make sure your support repositories are configured and updated.
5. Click on our github repository link on the OP first post and make sure you're connected with your github account. If you don't have one - create it! Why? because you will need to share your sources for this project. And because you all use as mantra that you can mod android apps because it's open source. So BE OPEN SOURCE. Have your name on github.
6. Once you're logged in into github, fork our repository. In the right upper corner of our main git repository you have those buttons:
Click "fork" to make a copy of this repository in your own repositories. Now you have your own repository.
7. On YOUR repository find this green button on the top right above the code, which says "Clone and Download". DO NOT DOWNLOAD ZIP. Instead, click the little "clipboard" icon to copy the .git uri and return to studio.
8. In studio: File > New >Project from Version Control > Git
9. Paste the git uri and choose destination. Click ok. Android studio will import the project from git and open it for you.
10. At this point if you're asked to update gradle build tools or anything else, do it. Wait for gradle to sync with project files. If you get errors, resolve them as referenced. If you cannot, google is your friend.
We WILL provide some support for initial importing of the project and setting it up for a very limited period of time. Gradle can be a tricky business. Please be sure to provide us with specific error from gradle log and a line in the gradle script on which the error is made.
11. We WILL know if your errors are because you didn't update sdk and build tools. And we will kick your butts for posting without following instructions. Remember, our time is valuable and given to you for free. Our instructions are clear and we made a huge effort to write them. If you can't be bothered with following them, beware.
12. Once the gradle is done syncing without errors, just in case, click Build > Rebuild Project. Once that is done without errors and it says BUILD SUCCESSFUL, you can start building your project following the instructions on the next post.
23
Adding items to the Navigation Drawer:
1. Switch to project view.
It will be easier for you to navigate through project files. For that:
On the left panel on top, below the android studio menu, find this:
This is what your project will look right after you import it. This is module view. By default it is categorized and to work with it you need some understanding of this view.
Click the 2 arrow icon which is circled in blue and select "project"
Your structure will now change.
Navigate into the project by the following path: Project name > app > src > main
Now you will see directories, like: java, res, assets... and so on.
This is your working directory. You will be making your code changes here.
2. Find a file called nav_drawer_arrays.xml. It is located in res/values folder. Double click on it to open.
You will see the following 3 arrays inside. The first one is a reference array (simple typed array) and the other 2 are strings arrays.
Those are WORKING ARRAYS. When you run the app as it is now, you will see all the items created in the navigation drawer based on this info.
Please read the comments we wrote in the xml file for you:
3. Let's say you have 10 preference files in directory called xml. That means you will want to have 10 items referring to your preference files in the navigation drawer. That means you will need to have 10 items in EACH array. Create 10 empty preference files. DO NOT COPY THE ONES FROM RC v1.0. Just right click the xml folder, choose "New" and choose "New XML resource file". Give it a name and click ok. Leave them empty for now. create all the icons you need for them in the navigation drawer.
4. Populate the arrays with titles, icons and xml names. You're done. You now have a working items in the navigation drawer. You do not need any changes in java files. the items are being generated on run time and their onClicks redirected accordingly. If you run the app right now you should have 10 empty preference files.
We strongly encourage you to keep the ui_prefs.xml file and references to it in your project while you're working on it. It contains most valuable information about the kinds of preferences we have included and their various usages. You can remove it from arrays before making the release version. You can have it as last item in your arrays and use it as test dummy to see how things should work properly
23
Preferences - Part 2: Types of Preferences
1. Two state preferences (meaning - can be true or false)
MySwitchPreference & MyCheckboxPreference
FilePreference
2. Dialog preferences
ColorPickerPreferece
MyListPreference
ThumbnailListPreference
IntentDialogPreference
MyEditTextPreference
3. Special Preferences
OpenAppPreference
UriSelectionPreference
RunScriptPreference
ImageHeaderPreference
21
Preferences - Part 1: Introduction
1. Major change in implementation:
1. For this release we made a major change in how preferences are handled. They are not handled anymore. They handle themselves.
2. For that to happen we needed to subclass ALL native android preferences except PreferenceScreen and PreferenceCategory.
3. What does it mean to subclass? That means we created java classses which extend (resemble) native android preferences and we wrote our own implementation of how they should behave, how they should load their values and write their values.
4. That being said - there is no more standard android preferences in this project. No more SwitchPreference, no more CheckboxPreference, no ListPreference... None of those.
5. Two reasons for that:
1. We didn't want you to get lost in special conditions anymore. We wanted you to be able to set if the preference should restart systemui from xml file when you declare preference. For that we needed to add custom xml attributes. For that we needed a preference class to be able to acknowledge that. So we needed a custom preference class.
2. We wanted the preference to manage itself in by reading and writing from and to database. Instead of fragment running endless iterations and conditions. When our new preferences are born (attached to the screen), they get their value from the database directly. No one needs to set values to them. When they are changed, they know to write into database directly. From their own class. Not containing fragment doing that for them.
2. Types of preferences
1. Two state preferences:
MySwitchPreference
MyCheckboxPreference
FilePreference
2. Dialog preferences:
MyListPreference
MyEditTextPreference
IntentDialogPreference
ThumbnailListPreference
ColorPickerPreference
3. Native preferences(PreferenceGroup subclasses):
PreferenceScreen
PreferenceCategory
4. Slider Preference:
MySeekBarPreference
5. Special preferences:
OpenAppPreference
UriSelectionPreference
RunScriptPreference
ImageHeaderPreference
3. Setting defaults:
It is ABSOLUTELY VITALLY IMPORTANT that you set android:defaultValue to all the preferences that change and read values. That means:
MySwitchPreference
MyCheckboxPreference
FilePreference
MyListPreference
MyEditTextPreference
ThumbnailListPreference
ColorPickerPreference
MySeekBarPreference
4. What happens if we use regular android preferences? Like SwitchPreference or ListPreference?
Nothing! Absolutely nothing will happen nor to this project, nor to your database and, MOST IMPORTANTLY, nor to your mods.
It will act like normal preference. It will not write to database. Your mods will not be affected and WILL NOT WORK.
5. Custom attributes for value changing preferences and RunScriptPreference
1. app: packageNameToKill
This attribute is of type string and you will need to provide which app you want to restart when this preference changes value.2. app:isSilent
This is a boolean type attribute, which is by default set to true. That means that if you don't set this attribute and you DO set the package name to kill, it will restart the app you want without warning as soon as the value has been changed. If it is set to "false", upon value change a dialog will appear with app icon and test informing user that for this action to take effect an app restart is required. They can then choose to kill app now or cancel the dialog and kill it later.3. app:rebootRequired
This is also a boolean type of preference which by default is set to false. If you set it to "true", upon preference value change a dialog will appear, informing the user that reboot is required for this action to take effect. good example for that is changing the default app intent to open on home button double click. That needs framework reload.
If rebootRequired is set to true and you ALSO set package name to kill, reboot takes preference. Package to kill will be ignored.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone