Where is the APN information stored inside rom.zip? - Hero CDMA Q&A, Help & Troubleshooting

I am trying to add/change the apn information inside the rom I am building(before flashing it).
I know in the aosp roms it is located in system\etc\apns-conf.xml
but where is it located in the sense roms??

It would be inside system/etc/apns-conf.xml. hope that helps bud.
Sent from my fresh hero.

when I look at the apns-conf.xml
It says
Code:
<?xml version="1.0" encoding="utf-8"?>
<!-- Copyright (C) 2008 The Android Open Source Project
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
<!-- This file contains fake APNs that are necessary for the emulator
to talk to the network. It should only be installed for SDK builds.
This file is not installed by the local Android.mk, it's installed using
a PRODUCT_COPY_FILES line in the sdk section of the toplevel Makefile.
-->
<!-- use empty string to specify no proxy or port -->
<!-- This version must agree with that in apps/common/res/apns.xml -->
<apns version="6">
<apn carrier="Android"
mcc="310"
mnc="995"
apn="internet"
user="*"
server="*"
password="*"
mmsc="null"
/>
<!--apn carrier="TelKila"
mcc="310"
mnc="260"
apn="internet"
user="*"
server="*"
password="*"
mmsc="null"
/-->
</apns>
but when I do an apn backup it spits out 36 or so... looking at the apns-conf.xml it only shows 2.. and neither of them are the mms info.

Related

[FIX][Tested-Working] How to fix MMS on Sense 3.0 Roms [Updated]

The problem is that the port is from Sprint, and thus, the APNs point to, well Sprint.
Here is how to fix!
1. Navigate to /data/VR-System/system.etc/
2. There is a file named apns-conf.xml
3. Replace Content with:
Code:
<?xml version="1.0" encoding="utf-8"?>
<apns version="8">
<apn carrier="Verizon"
mcc="310"
mnc="004"
apn=""
user="*"
server="*"
password="*"
mmsc="http://mms.vtext.com/servlets/mms"
/>
<apn name="Production"
numeric="310012"
mcc="310"
mnc="012"
apn="1"
user="null"
server="null"
password="null"
proxy="null"
port=""
mmsproxy=""
mmsport=""
mmsprotocol="2.0"
mmsc="http://mms.vtext.com/servlets/mms"
type="mms"
/>
</apns>
Now the harder part!
4. Take framework-res.apk out of the Rom
5. Decompile framework-res.apk
6. Navigate to /res/xml/apns.xml
7. Replace content with this code:
Code:
<apns version="8">
<apn carrier="Verizon"
mcc="310"
mnc="004"
apn=""
user="*"
server="*"
password="*"
mmsc="http://mms.vtext.com/servlets/mms"
/>
<apn name="Production"
numeric="310012"
mcc="310"
mnc="012"
apn="1"
user="null"
server="null"
password="null"
proxy="null"
port=""
mmsproxy=""
mmsport=""
mmsprotocol="2.0"
mmsc="http://mms.vtext.com/servlets/mms"
type="mms"
/>
</apns>
8. Recompile framework-res.apk
9. Important part! Take the apns.xml from the newly compiled framework, and place it in the old in the same place. Can now delete the newly created framework!
10.Reintegrate into the rom!
11. Enjoy!
This is intended for devs that could use the extra time to work on more important problems! If you are experienced, and don't want to wait, well then go ahead and do it yourself! I am not responsible for any problems you may encounter!
SWEET!!!!!!!!!
You can use bettercut to make a shortcut to your APN settings and edit like that. There are a few other ways aswell ... you can use QPST, if your handy in that area.
Cricket customers check this out http://forum.xda-developers.com/showthread.php?t=492824
get apn backup and restore from the market. unzip this xml and then load apn from program.
https://market.android.com/details?id=com.riteshsahu.APNBackupRestore
All valid methods, I was just showing the way to do it for a rom for release is all! Thanks for the additions!
Afteraffekt said:
All valid methods, I was just showing the way to do it for a rom for release is all! Thanks for the additions!
Click to expand...
Click to collapse
If anyone's having mms problems on sense 3.0 roms not sense 2.1/3.0 i'll post y framework-res.apk if you want.
DWhite456 said:
get apn backup and restore from the market. unzip this xml and then load apn from program.
https://market.android.com/details?id=com.riteshsahu.APNBackupRestore
Click to expand...
Click to collapse
Can You confirm this works I tried it this morning on Gingersense remix and it didn't work. I also entered manually in the mms settings
I cant as my carrier is actually sprint. but when I load a vzw rom on my phone I use the same method to get my sprint mms working
DWhite456 said:
I cant as my carrier is actually sprint. but when I load a vzw rom on my phone I use the same method to get my sprint mms working
Click to expand...
Click to collapse
Ok tried a few times even pulled the apns posted for optimized still unabe to send a pic,however regular texting works
JoelZ9614 said:
If anyone's having mms problems on sense 3.0 roms not sense 2.1/3.0 i'll post y framework-res.apk if you want.
Click to expand...
Click to collapse
post it i need it for your uber kingdom
I updated the thread to reveal the proper way to fix MMS, this method is MUCH easier, and is the PROPER way, and well - actually works!
what would be the best program to open a xml file to change it on windows?
tribbey said:
what would be the best program to open a xml file to change it on windows?
Click to expand...
Click to collapse
I recommend Notepad++ free program thats the best for XML on windows.
Afteraffekt said:
I recommend Notepad++ free program thats the best for XML on windows.
Click to expand...
Click to collapse
is this what it should be showing me now?
and if so would i be able to just move that xml file the new one of course through root explorer and replace the sprint one?
Code:
- <apns version="8">
<apn carrier="Verizon" mcc="310" mnc="004" apn="" user="*" server="*" password="*" mmsc="http://mms.vtext.com/servlets/mms" />
<apn name="Production" numeric="310012" mcc="310" mnc="012" apn="1" user="null" server="null" password="null" proxy="null" port="" mmsproxy="" mmsport="" mmsprotocol="2.0" mmsc="http://mms.vtext.com/servlets/mms" type="mms" />
</apns>
tribbey said:
is this what it should be showing me now?
Code:
- <apns version="8">
<apn carrier="Verizon" mcc="310" mnc="004" apn="" user="*" server="*" password="*" mmsc="http://mms.vtext.com/servlets/mms" />
<apn name="Production" numeric="310012" mcc="310" mnc="012" apn="1" user="null" server="null" password="null" proxy="null" port="" mmsproxy="" mmsport="" mmsprotocol="2.0" mmsc="http://mms.vtext.com/servlets/mms" type="mms" />
</apns>
Click to expand...
Click to collapse
I, honestly, have no idea. Because that's what I have, except I hav <apns version="6" but it won't work. Does that work for you?
asianbobo15 said:
I, honestly, have no idea. Because that's what I have, except I hav <apns version="6" but it won't work. Does that work for you?
Click to expand...
Click to collapse
i edited my post asking a question i havent tried it yet
.
oh i edited for Afteraffekt but ill let you know when i change it
tribbey said:
i edited my post asking a question i havent tried it yet
Click to expand...
Click to collapse
ohh. well i tried replacing it with mine, and it didn't do anything. so it doesn't do any harm to try.
It must say version 8, and it must have the XML version at the top! Also, you may have to make this change to the rom itself, and not after firstboot as it may not work! The file needs to look like this:
Code:
<?xml version="1.0" encoding="utf-8"?>
<!-- Copyright (C) 2008 The Android Open Source Project
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
<!-- This file contains fake APNs that are necessary for the emulator
to talk to the network. It should only be installed for SDK builds.
This file is not installed by the local Android.mk, it's installed using
a PRODUCT_COPY_FILES line in the sdk section of the toplevel Makefile.
-->
<apns version="8">
<apn carrier="Verizon"
mcc="310"
mnc="004"
apn=""
user="*"
server="*"
password="*"
mmsc="http://mms.vtext.com/servlets/mms"
/>
<apn name="Production"
numeric="310012"
mcc="310"
mnc="012"
apn="1"
user="null"
server="null"
password="null"
proxy="null"
port=""
mmsproxy=""
mmsport=""
mmsprotocol="2.0"
mmsc="http://mms.vtext.com/servlets/mms"
type="mms"
/>
</apns>
Only the commented (#) lines are optional!
Again, this fix may need to be present at first boot!
That's exactly what my xml file says I'm still waiting I put it on the ROM then reflashed
Sent from my ADR6300 using XDA App
Alright guys this probably won't work i'll post a thread tommorow on how to fix it
Edit: OR just tell the OP to edit his post with the one that works

[DEV][Q] What's wrong with Sense GSM

Hi folks I want to ask. As you can see,I'm trying to port decently Sense ROM to P500. But GSM isn't working. For making it work i tried to use and import the following libs from devoid:
Code:
[B]/system/lib[/B]
libril-qc-1.so
liboncrpc.so
libdsm.so
libqueue.so
libdiag.so
libauth.so
libcm.so
libnv.so
libpbmlib.so
libwms.so
libwmsts.so
libmmgsdilib.so
libgsdi_exp.so
libgstk_exp.so
libril-qcril-hook-oem.so
liboem_rapi.so
libsnd.so
libqmi.so
libdll.so
liblgeat.so
liblgdrm.so
liblgdrmwbxml.so
liblgerft.so
libbcmwl.so
libdss.so
[B]/system/bin[/B]
rild
But nothing. Mik also gave me a link of his sources,telling me that maybe I had to add some lg proprietary things.
Code:
[B]/system/bin[/B]
qmuxd
rmt_storage
port-bridge
wiperiface
tsdown
netmgrd
[B]/system/etc[/B]
MELFAS_FIRM.bin (I know it's a TS thang,but just to be sure...)
[B]/system/lib[/B]
libsdutils.so
libnetmgr.so
Did I miss something? I don't think so. I've imported all libs specified here.
It's impossible! GSM Still isn't working. I'm now thinking it's a permission problem,found this in logcat:
Code:
W/PackageManager( 1405): Unknown permission android.permission.ACCESS_NETWORK_LOCATION in package com.htc.android.locationpicker
W/PackageManager( 1405): Unknown permission android.permission.ACCESS_NETWORK_LOCATION in package com.htc.htcsettingwidgets
E/ConnectivityService( 1405): Error in networkAttributes - ignoring attempt to adopt radio 6
Any ideas?
Zecanilis made a mistake here. Why moving it to general section? I'm talking about a PORTING,which is a DEV thing.
Sent from my LG Optimus One P500 using XDA App
ciaox said:
Zecanilis made a mistake here. Why moving it to general section? I'm talking about a PORTING,which is a DEV thing.
I agree. Why? This is made by a dev who is talking dev. +1 to moving this back.
Sent from my LG Optimus One P500 using XDA App
Click to expand...
Click to collapse
Sent from my LG-P500 using XDA App
I think I know a solution, will look into it and if I'm right I'll let you know.
Sent from my LG-P500 using XDA App
Like I thought, in /system/etc/permissions/ this permission is missing, adding it to platform.xml perhaps solves it.
_Arjen_ said:
Like I thought, in /system/etc/permissions/ this permission is missing, adding it to platform.xml perhaps solves it.
Click to expand...
Click to collapse
I will let you know,thanks. If it doesn't work,I really don't know how to solve it,because I've tried it all.
Ok here's my platform.xml:
Code:
<?xml version="1.0" encoding="utf-8"?>
<!-- Copyright (C) 2008 The Android Open Source Project
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
<!-- This file is used to define the mappings between lower-level system
user and group IDs and the higher-level permission names managed
by the platform.
Be VERY careful when editing this file! Mistakes made here can open
big security holes.
-->
<permissions>
<!-- ================================================================== -->
<!-- ================================================================== -->
<!-- ================================================================== -->
<!-- The following tags are associating low-level group IDs with
permission names. By specifying such a mapping, you are saying
that any application process granted the given permission will
also be running with the given group ID attached to its process,
so it can perform any filesystem (read, write, execute) operations
allowed for that group. -->
<permission name="android.permission.BLUETOOTH_ADMIN" >
<group gid="net_bt_admin" />
</permission>
<permission name="android.permission.BLUETOOTH" >
<group gid="net_bt" />
</permission>
<permission name="android.permission.INTERNET" >
<group gid="inet" />
</permission>
<permission name="android.permission.CAMERA" >
<group gid="camera" />
</permission>
<permission name="android.permission.READ_LOGS" >
<group gid="log" />
</permission>
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_rw" />
</permission>
<!-- The group that /cache belongs to, linked to the permission
set on the applications that can access /cache -->
<permission name="android.permission.ACCESS_CACHE_FILESYSTEM" >
<group gid="cache" />
</permission>
<!-- RW permissions to any system resources owned by group 'diag'.
This is for carrier and manufacture diagnostics tools that must be
installable from the framework. Be careful. -->
<permission name="android.permission.DIAGNOSTIC" >
<group gid="input" />
<group gid="diag" />
</permission>
<!-- ================================================================== -->
<!-- ================================================================== -->
<!-- ================================================================== -->
<!-- The following tags are assigning high-level permissions to specific
user IDs. These are used to allow specific core system users to
perform the given operations with the higher-level framework. For
example, we give a wide variety of permissions to the shell user
since that is the user the adb shell runs under and developers and
others should have a fairly open environment in which to
interact with the system. -->
<!-- Standard permissions granted to the shell. -->
<assign-permission name="android.permission.WRITE_EXTERNAL_STORAGE" uid="shell" />
<assign-permission name="android.permission.SEND_SMS" uid="shell" />
<assign-permission name="android.permission.CALL_PHONE" uid="shell" />
<assign-permission name="android.permission.READ_CONTACTS" uid="shell" />
<assign-permission name="android.permission.WRITE_CONTACTS" uid="shell" />
<assign-permission name="android.permission.READ_OWNER_DATA" uid="shell" />
<assign-permission name="android.permission.WRITE_OWNER_DATA" uid="shell" />
<assign-permission name="android.permission.READ_CALENDAR" uid="shell" />
<assign-permission name="android.permission.WRITE_CALENDAR" uid="shell" />
<assign-permission name="android.permission.READ_USER_DICTIONARY" uid="shell" />
<assign-permission name="android.permission.WRITE_USER_DICTIONARY" uid="shell" />
<assign-permission name="android.permission.ACCESS_FINE_LOCATION" uid="shell" />
<assign-permission name="android.permission.ACCESS_COARSE_LOCATION" uid="shell" />
<assign-permission name="android.permission.ACCESS_LOCATION_EXTRA_COMMANDS" uid="shell" />
<assign-permission name="android.permission.ACCESS_NETWORK_STATE" uid="shell" />
<assign-permission name="android.permission.ACCESS_WIFI_STATE" uid="shell" />
<assign-permission name="android.permission.BLUETOOTH" uid="shell" />
<!-- System tool permissions granted to the shell. -->
<assign-permission name="android.permission.GET_TASKS" uid="shell" />
<assign-permission name="android.permission.CHANGE_CONFIGURATION" uid="shell" />
<assign-permission name="android.permission.REORDER_TASKS" uid="shell" />
<assign-permission name="android.permission.SET_ANIMATION_SCALE" uid="shell" />
<assign-permission name="android.permission.SET_PREFERRED_APPLICATIONS" uid="shell" />
<assign-permission name="android.permission.WRITE_SETTINGS" uid="shell" />
<assign-permission name="android.permission.WRITE_SECURE_SETTINGS" uid="shell" />
<assign-permission name="android.permission.BROADCAST_STICKY" uid="shell" />
<!-- Development tool permissions granted to the shell. -->
<assign-permission name="android.permission.SET_DEBUG_APP" uid="shell" />
<assign-permission name="android.permission.SET_PROCESS_LIMIT" uid="shell" />
<assign-permission name="android.permission.SET_ALWAYS_FINISH" uid="shell" />
<assign-permission name="android.permission.DUMP" uid="shell" />
<assign-permission name="android.permission.SIGNAL_PERSISTENT_PROCESSES" uid="shell" />
<!-- Internal permissions granted to the shell. -->
<assign-permission name="android.permission.FORCE_BACK" uid="shell" />
<assign-permission name="android.permission.BATTERY_STATS" uid="shell" />
<assign-permission name="android.permission.INTERNAL_SYSTEM_WINDOW" uid="shell" />
<assign-permission name="android.permission.INJECT_EVENTS" uid="shell" />
<assign-permission name="android.permission.SET_ACTIVITY_WATCHER" uid="shell" />
<assign-permission name="android.permission.READ_INPUT_STATE" uid="shell" />
<assign-permission name="android.permission.SET_ORIENTATION" uid="shell" />
<assign-permission name="android.permission.INSTALL_PACKAGES" uid="shell" />
<assign-permission name="android.permission.CLEAR_APP_USER_DATA" uid="shell" />
<assign-permission name="android.permission.DELETE_CACHE_FILES" uid="shell" />
<assign-permission name="android.permission.DELETE_PACKAGES" uid="shell" />
<assign-permission name="android.permission.ACCESS_SURFACE_FLINGER" uid="shell" />
<assign-permission name="android.permission.READ_FRAME_BUFFER" uid="shell" />
<assign-permission name="android.permission.DEVICE_POWER" uid="shell" />
<assign-permission name="android.permission.INSTALL_LOCATION_PROVIDER" uid="shell" />
<assign-permission name="android.permission.BACKUP" uid="shell" />
<assign-permission name="android.permission.MODIFY_AUDIO_SETTINGS" uid="media" />
<assign-permission name="android.permission.ACCESS_DRM" uid="media" />
<assign-permission name="android.permission.ACCESS_SURFACE_FLINGER" uid="media" />
<assign-permission name="android.permission.ACCESS_SURFACE_FLINGER" uid="graphics" />
<!-- This is a list of all the libraries available for application
code to link against. -->
<library name="android.test.runner"
file="/system/framework/android.test.runner.jar" />
<library name="javax.obex"
file="/system/framework/javax.obex.jar"/>
<!-- HTC PIM library (Contacts / Calendar / Mail / Sync ...) -->
<library name="com.htc.android.pimlib"
file="/system/framework/com.htc.android.pimlib.jar"/>
<!-- HTC EAS shared library (for OpenSource parts) -->
<library name="com.htc.android.easopen"
file="/system/framework/com.htc.android.easopen.jar"/>
<!-- add by Justin_Liu, for scalado library -->
<library name="com.scalado.util.ScaladoUtil"
file="/system/framework/com.scalado.util.ScaladoUtil.jar"/>
</permissions>
So,I need to add something like this:
Code:
<permission name="android.permission.ACCESS_NETWORK_LOCATION" >
<group gid="sdcard_rw" />
</permission>
But,I also need to change "group gid". Any idea of what I need to put in that "group gid"?
Also I found some other interesting things. I found this in platform.xml:
Code:
<assign-permission name="android.permission.WRITE_EXTERNAL_STORAGE" uid="shell" />
<assign-permission name="android.permission.SEND_SMS" uid="shell" />
<assign-permission name="android.permission.CALL_PHONE" uid="shell" />
<assign-permission name="android.permission.READ_CONTACTS" uid="shell" />
<assign-permission name="android.permission.WRITE_CONTACTS" uid="shell" />
<assign-permission name="android.permission.READ_OWNER_DATA" uid="shell" />
<assign-permission name="android.permission.WRITE_OWNER_DATA" uid="shell" />
<assign-permission name="android.permission.READ_CALENDAR" uid="shell" />
<assign-permission name="android.permission.WRITE_CALENDAR" uid="shell" />
<assign-permission name="android.permission.READ_USER_DICTIONARY" uid="shell" />
<assign-permission name="android.permission.WRITE_USER_DICTIONARY" uid="shell" />
<assign-permission name="android.permission.ACCESS_FINE_LOCATION" uid="shell" />
<assign-permission name="android.permission.ACCESS_COARSE_LOCATION" uid="shell" />
<assign-permission name="android.permission.ACCESS_LOCATION_EXTRA_COMMANDS" uid="shell" />
<assign-permission name="android.permission.[B]ACCESS_NETWORK_STATE[/B]" uid="shell" />
<assign-permission name="android.permission.ACCESS_WIFI_STATE" uid="shell" />
<assign-permission name="android.permission.BLUETOOTH" uid="shell" />
<!-- System tool permissions granted to the shell. -->
<assign-permission name="android.permission.GET_TASKS" uid="shell" />
<assign-permission name="android.permission.CHANGE_CONFIGURATION" uid="shell" />
<assign-permission name="android.permission.REORDER_TASKS" uid="shell" />
<assign-permission name="android.permission.SET_ANIMATION_SCALE" uid="shell" />
<assign-permission name="android.permission.SET_PREFERRED_APPLICATIONS" uid="shell" />
<assign-permission name="android.permission.WRITE_SETTINGS" uid="shell" />
<assign-permission name="android.permission.WRITE_SECURE_SETTINGS" uid="shell" />
<assign-permission name="android.permission.BROADCAST_STICKY" uid="shell" />
<!-- Development tool permissions granted to the shell. -->
<assign-permission name="android.permission.SET_DEBUG_APP" uid="shell" />
<assign-permission name="android.permission.SET_PROCESS_LIMIT" uid="shell" />
<assign-permission name="android.permission.SET_ALWAYS_FINISH" uid="shell" />
<assign-permission name="android.permission.DUMP" uid="shell" />
<assign-permission name="android.permission.SIGNAL_PERSISTENT_PROCESSES" uid="shell" />
<!-- Internal permissions granted to the shell. -->
<assign-permission name="android.permission.FORCE_BACK" uid="shell" />
<assign-permission name="android.permission.BATTERY_STATS" uid="shell" />
<assign-permission name="android.permission.INTERNAL_SYSTEM_WINDOW" uid="shell" />
<assign-permission name="android.permission.INJECT_EVENTS" uid="shell" />
<assign-permission name="android.permission.SET_ACTIVITY_WATCHER" uid="shell" />
<assign-permission name="android.permission.READ_INPUT_STATE" uid="shell" />
<assign-permission name="android.permission.SET_ORIENTATION" uid="shell" />
<assign-permission name="android.permission.INSTALL_PACKAGES" uid="shell" />
<assign-permission name="android.permission.CLEAR_APP_USER_DATA" uid="shell" />
<assign-permission name="android.permission.DELETE_CACHE_FILES" uid="shell" />
<assign-permission name="android.permission.DELETE_PACKAGES" uid="shell" />
<assign-permission name="android.permission.ACCESS_SURFACE_FLINGER" uid="shell" />
<assign-permission name="android.permission.READ_FRAME_BUFFER" uid="shell" />
<assign-permission name="android.permission.DEVICE_POWER" uid="shell" />
<assign-permission name="android.permission.INSTALL_LOCATION_PROVIDER" uid="shell" />
<assign-permission name="android.permission.BACKUP" uid="shell" />
<assign-permission name="android.permission.MODIFY_AUDIO_SETTINGS" uid="media" />
<assign-permission name="android.permission.ACCESS_DRM" uid="media" />
<assign-permission name="android.permission.ACCESS_SURFACE_FLINGER" uid="media" />
<assign-permission name="android.permission.ACCESS_SURFACE_FLINGER" uid="graphics" />
These should be the declared permissions.
I've seen that here android.permission.ACCESS_NETWORK_STATE is declared but it isn't declared here:
Code:
<permission name="android.permission.BLUETOOTH_ADMIN" >
<group gid="net_bt_admin" />
</permission>
<permission name="android.permission.BLUETOOTH" >
<group gid="net_bt" />
</permission>
<permission name="android.permission.INTERNET" >
<group gid="inet" />
</permission>
<permission name="android.permission.CAMERA" >
<group gid="camera" />
</permission>
<permission name="android.permission.READ_LOGS" >
<group gid="log" />
</permission>
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_rw" />
</permission>
<!-- The group that /cache belongs to, linked to the permission
set on the applications that can access /cache -->
<permission name="android.permission.ACCESS_CACHE_FILESYSTEM" >
<group gid="cache" />
</permission>
<!-- RW permissions to any system resources owned by group 'diag'.
This is for carrier and manufacture diagnostics tools that must be
installable from the framework. Be careful. -->
<permission name="android.permission.DIAGNOSTIC" >
<group gid="input" />
<group gid="diag" />
</permission>
I should declare it together with android.permission.ACCESS_NETWORK_LOCATION,shouldn't I?
ciaox said:
Zecanilis made a mistake here. Why moving it to general section? I'm talking about a PORTING,which is a DEV thing.
Sent from my LG Optimus One P500 using XDA App
Click to expand...
Click to collapse
Yes i made a mistake, for 2 minutes. I'm human you know!
And if you've changed the name of the thread it whouldn't happen. So please change the [Q] to [DEV Q].
Cheers
Zecanilis said:
Yes i made a mistake, for 2 minutes. I'm human you know!
And if you've changed the name of the thread it whouldn't happen. So please change the [Q] to [DEV Q].
Cheers
Click to expand...
Click to collapse
Ok I will. But don't get mad!
you are missing the lib libril.so and the binary rild
if its still not working, have a look in init.rc and init.thunderg.rc files to see
how and when services are started
andy572 said:
you are missing the lib libril.so and the binary rild
if its still not working, have a look in init.rc and init.thunderg.rc files to see
how and when services are started
Click to expand...
Click to collapse
No,i didn't miss rild binary and neither libril.so
Ok i'll take a look at that .rc files.
I'm not sure if you have to use uid or gid here, try with uid=shell,
will take a look for possible gid
ciaox Cant you add the gsm etc from the russian exe available for GB roms and thn we can flash this sense rom ? Any idea
mansirawat said:
ciaox Cant you add the gsm etc from the russian exe available for GB roms and thn we can flash this sense rom ? Any idea
Click to expand...
Click to collapse
Thanks for the idea,but i need some Froyo libs.
upd: I looked after froyo platform.xml but ACCESS_NETWORK_LOCATION isn't declared there too. So,I now think that it's something in .rc files,but I'll try to touch platform.xml too.
ciaox
upd:Got it working. Took libs from my openOptimus rom and opensource rild binary. One question: I can't make calls,but I can recieve 'em. Why? Trying with another dialer.
ciaox said:
upd:Got it working. Took libs from my openOptimus rom and opensource rild binary. One question: I can't make calls,but I can recieve 'em. Why? Trying with another dialer.
Click to expand...
Click to collapse
Well, just symlink gsmincomingcall.so to gsmoutgoingcall.so?
OK, seriously - maybe upload it somewhere so that people can mess with it and possibly find out? (After all, incoming calls working is still a whole lot better than no GSM altogether - which is what people are stuck with ATM.)
doktornotor said:
Well, just symlink gsmincomingcall.so to gsmoutgoingcall.so?
OK, seriously - maybe upload it somewhere so that people can mess with it and possibly find out? (After all, incoming calls working is still a whole lot better than no GSM altogether - which is what people are stuck with ATM.)
Click to expand...
Click to collapse
Upload what man? The whole rom or what?
ciaox said:
Upload what man? The whole rom or what?
Click to expand...
Click to collapse
Well yeah... kinda hard to debug such stuff when you have nothing at hand to experiment with. Or maybe just some flashable "hotfix" zip to the first alpha you posted here.
doktornotor said:
Well yeah... kinda hard to debug such stuff when you have nothing at hand to experiment with. Or maybe just some flashable "hotfix" zip to the first alpha you posted here.
Click to expand...
Click to collapse
Even dialer One fails(Uses same system method for calling).

[DEV]CM 10.1 Salsa development

Hey Salsa users and devs,
I try to build a clean CM 10.1 on my PC (Linux Mint 15 x64 on an Intel Core 2 Duo E8200 with 4GB RAM).
The CM 7/9/10 development thread seems a bit overloaded and I want to collect all neccessary facts, when I try to build CM 10.1.
What will be needed here?
- Manifest files for build a clean repository (which devicetree, linux kernel, display libs ...)
- Which patches were used?
- Kernel configs and additional kernel driver
What will be the aim?
- Get a functional CM 10.1 on HTC Salsa with most of the hardware features
Builds for testing pruposes will be posted here in this dev thread.
This thread is aimed for development purposes not for whishes like "Can you make feature xyz working?". It is the main task to get most of the things on Salsa working like front cam, camcorder, Bluetooth, GPS.
theschneidi said:
Hey Salsa users and devs,
I try to build a clean CM 10.1 on my PC (Linux Mint 15 x64 on an Intel Core 2 Duo E8200 with 4GB RAM).
The CM 7/9/10 development thread seems a bit overloaded and I want to collect all neccessary facts, when I try to build CM 10.1.
What will be needed here?
- Manifest files for build a clean repository (which devicetree, linux kernel, display libs ...)
- Which patches were used?
- Kernel configs and additional kernel driver
What will be the aim?
- Get a functional CM 10.1 on HTC Salsa with most of the hardware features
Builds for testing pruposes will be posted here in this dev thread.
This thread is aimed for development purposes not for whishes like "Can you make feature xyz working?". It is the main task to get most of the things on Salsa working like front cam, camcorder, Bluetooth, GPS.
Click to expand...
Click to collapse
Great Schneider!
In case you need the git here it is- https://github.com/vigoos/android_salsa_cm_10.1/
I've added front camera support, it must work now
Kernel version- Try this if you can- http://git.cryptomilk.org/projects/marvel/kernel_htc_msm7227-3.0.git
Feel free to tell me whatever you need, I'll provide.
Best Of Luck.
vigoos said:
Great Schneider!
In case you need the git here it is- https://github.com/vigoos/android_salsa_cm_10.1/
I've added front camera support, it must work now
Kernel version- Try this if you can- http://git.cryptomilk.org/projects/marvel/kernel_htc_msm7227-3.0.git
Feel free to tell me whatever you need, I'll provide.
Best Of Luck.
Click to expand...
Click to collapse
Thanks,
Still downloading all packages
Hope it will work
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_htc_common" path="device/htc/common" revision="gingerbread" />
<project name="vigoos/android_salsa_cm_10.1" path="device/htc/icong" revision="jellybean-r2" />
<remote name="cryptomilk" fetch="git://git.cryptomilk.org/" />
<project name="projects/marvel/kernel_htc_msm7227-3.0.git" path="kernel/htc/msm7227" revision="master" remote="cryptomilk" />
<!-- Fix framework -->
<remove-project name="CyanogenMod/android_frameworks_av" />
<project name="Ganster41/android_frameworks_av" path="frameworks/av" revision="jellybean"/>
<!-- Fix display -->
<remove-project name="CyanogenMod/android_hardware_qcom_display" />
<project name="WinSuk/android_hardware_qcom_display" path="hardware/qcom/display" revision="jellybean"/>
<!-- Fix msm7k -->
<remove-project name="CyanogenMod/android_hardware_msm7k" />
<project name="ProjectLlama/android_hardware_msm7k" path="hardware/msm7k" revision="jellybean"/>
</manifest>
vigoos said:
...
In case you need the git here it is- https://github.com/vigoos/android_salsa_cm_10.1/
...
Click to expand...
Click to collapse
vendorsetup.sh needs to be changed ( marvel->icong ) :
add_lunch_combo cm_icong-userdebug
add_lunch_combo cm_icong-eng
BoardConfig.mk:
BOARD_VENDOR_QCOM_GPS_LOC_API_HARDWARE := icong
BOARD_EGL_CFG := device/htc/icong/egl.cfg
Error in Lunch, cannot find a file .. I know it is a mdpi phone but hdpi settings might work too
icong.mk:
# dalvik heap config for devices with 512MB memory
$(call inherit-product, frameworks/native/build/phone-hdpi-512-dalvik-heap.mk)
EDIT
libcamera/Android.mk:14: *** Leerer Variablenname
LOCAL_SRC_FILES := QcomCamera.cpp
:= mt9v113.c
needs to be
LOCAL_SRC_FILES := QcomCamera.cpp, mt9v113.c
EDIT2: in key/
marvel-keypad.kcm.bin -> icong-keypad.kcm.bin
theschneidi said:
vendorsetup.sh needs to be changed ( marvel->icong ) :
add_lunch_combo cm_icong-userdebug
add_lunch_combo cm_icong-eng
BoardConfig.mk:
BOARD_VENDOR_QCOM_GPS_LOC_API_HARDWARE := icong
BOARD_EGL_CFG := device/htc/icong/egl.cfg
Error in Lunch, cannot find a file .. I know it is a mdpi phone but hdpi settings might work too
icong.mk:
# dalvik heap config for devices with 512MB memory
$(call inherit-product, frameworks/native/build/phone-hdpi-512-dalvik-heap.mk)
EDIT
libcamera/Android.mk:14: *** Leerer Variablenname
LOCAL_SRC_FILES := QcomCamera.cpp
:= mt9v113.c
needs to be
LOCAL_SRC_FILES := QcomCamera.cpp, mt9v113.c
EDIT2: in key/
marvel-keypad.kcm.bin -> icong-keypad.kcm.bin
Click to expand...
Click to collapse
Thanks mate, I'll fix it once I get home.
EDIT 1- I'm getting a feeling front cam is gonna work this time around. If it doesn't I got one more way it can,
Sent from my GT-P3100 using Tapatalk
vigoos said:
Thanks mate, I'll fix it once I get home.
EDIT 1- I'm getting a feeling front cam is gonna work this time around. If it doesn't I got one more way it can,
Sent from my GT-P3100 using Tapatalk
Click to expand...
Click to collapse
What does this error mean?
Code:
device/htc/icong/overlay/frameworks/base/core/res/res/values/config.xml:50: error: Resource at config_networkLocationProviderPackageName appears in overlay but not in the base package; use <add-resource> to add.
device/htc/icong/overlay/frameworks/base/core/res/res/values/config.xml:53: error: Resource at config_geocodeProviderPackageName appears in overlay but not in the base package; use <add-resource> to add.
device/htc/icong/overlay/frameworks/base/core/res/res/values/config.xml:128: error: Resource at config_bluetooth_adapter_quick_switch appears in overlay but not in the base package; use <add-resource> to add.
theschneidi said:
What does this error mean?
Code:
device/htc/icong/overlay/frameworks/base/core/res/res/values/config.xml:50: error: Resource at config_networkLocationProviderPackageName appears in overlay but not in the base package; use <add-resource> to add.
device/htc/icong/overlay/frameworks/base/core/res/res/values/config.xml:53: error: Resource at config_geocodeProviderPackageName appears in overlay but not in the base package; use <add-resource> to add.
device/htc/icong/overlay/frameworks/base/core/res/res/values/config.xml:128: error: Resource at config_bluetooth_adapter_quick_switch appears in overlay but not in the base package; use <add-resource> to add.
Click to expand...
Click to collapse
There's some problem in that XML it means, I'll study the XML from ma few other devices so I can get an idea where the problem is
Sent from my GT-P3100 using Tapatalk
theschneidi said:
vendorsetup.sh needs to be changed ( marvel->icong ) :
add_lunch_combo cm_icong-userdebug
add_lunch_combo cm_icong-eng
BoardConfig.mk:
BOARD_VENDOR_QCOM_GPS_LOC_API_HARDWARE := icong
BOARD_EGL_CFG := device/htc/icong/egl.cfg
Error in Lunch, cannot find a file .. I know it is a mdpi phone but hdpi settings might work too
icong.mk:
# dalvik heap config for devices with 512MB memory
$(call inherit-product, frameworks/native/build/phone-hdpi-512-dalvik-heap.mk)
EDIT
libcamera/Android.mk:14: *** Leerer Variablenname
LOCAL_SRC_FILES := QcomCamera.cpp
:= mt9v113.c
needs to be
LOCAL_SRC_FILES := QcomCamera.cpp, mt9v113.c
EDIT2: in key/
marvel-keypad.kcm.bin -> icong-keypad.kcm.bin
Click to expand...
Click to collapse
Fixed all these niggles.... I'll see the XML soon
Sent from my GT-P3100 using Tapatalk
vigoos said:
Fixed all these niggles.... I'll see the XML soon
Sent from my GT-P3100 using Tapatalk
Click to expand...
Click to collapse
In some threads I read that they deleted those lines in the XML. I will try that method first. Hope I'll get a build this evening. I got some other errors, which I post here in a few days.
vigoos said:
Kernel version- Try this if you can- http://git.cryptomilk.org/projects/marvel/kernel_htc_msm7227-3.0.git
Feel free to tell me whatever you need, I'll provide.
Click to expand...
Click to collapse
I don't mean to interrupt your conversation, but this kernel doesn't work (even on marvel) and the development has been dead for one year (or longer?) now. For CM10.1, 2.6 kernel can be used. We are even trying to get CM10.2 working on marvel using this kernel.
EDIT: You might want to check this and this out.
The manifest I'd suggest you to use... (remove my comments )
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_htc_common" path="device/htc/common" revision="gingerbread" />
<project name="vigoos/android_salsa_cm_10.1" path="device/htc/icong" revision="jellybean-r2" />
<project name="Do not use 3.x kernel..." />
<!-- Fix framework -->
<remove-project name="CyanogenMod/android_frameworks_av" />
<project name="androidarmv6/android_frameworks_av" path="frameworks/av" revision="jellybean"/>
<!-- Fix display -->
<remove-project name="CyanogenMod/android_hardware_qcom_display" />
<project name="WinSuk/android_hardware_qcom_display" path="hardware/qcom/display" revision="jellybean"/>
<!-- Fix msm7k -->
<remove-project name="CyanogenMod/android_hardware_msm7k" />
<project name="androidarmv6/android_hardware_msm7k" path="hardware/msm7k" revision="jellybean"/> androidarmv6 ones are newer, ProjectLlama is old.
</manifest>
You can use this kernel, but you'll probably have to add icong support.
Gesendet von meinem Xperia S mit Tapatalk
djolivier said:
I don't mean to interrupt your conversation, but this kernel doesn't work (even on marvel) and the development has been dead for one year (or longer?) now. For CM10.1, 2.6 kernel can be used. We are even trying to get CM10.2 working on marvel using this kernel.
EDIT: You might want to check this and this out.
The manifest I'd suggest you to use... (remove my comments )
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_htc_common" path="device/htc/common" revision="gingerbread" />
<project name="vigoos/android_salsa_cm_10.1" path="device/htc/icong" revision="jellybean-r2" />
<project name="Do not use 3.x kernel..." />
<!-- Fix framework -->
<remove-project name="CyanogenMod/android_frameworks_av" />
<project name="androidarmv6/android_frameworks_av" path="frameworks/av" revision="jellybean"/>
<!-- Fix display -->
<remove-project name="CyanogenMod/android_hardware_qcom_display" />
<project name="WinSuk/android_hardware_qcom_display" path="hardware/qcom/display" revision="jellybean"/>
<!-- Fix msm7k -->
<remove-project name="CyanogenMod/android_hardware_msm7k" />
<project name="androidarmv6/android_hardware_msm7k" path="hardware/msm7k" revision="jellybean"/> androidarmv6 ones are newer, ProjectLlama is old.
</manifest>
You can use this kernel, but you'll probably have to add icong support.
Gesendet von meinem Xperia S mit Tapatalk
Click to expand...
Click to collapse
Ok, I will try it. Some things I had to change in kernel. When all things from 3.0 don't work I switch to the good old 2.6.x kernel.
OWL-Predator works with Salsa, the last CM10 for icong is built with it.
Vielen Dank DjOlivier
djolivier said:
I don't mean to interrupt your conversation, but this kernel doesn't work (even on marvel) and the development has been dead for one year (or longer?) now. For CM10.1, 2.6 kernel can be used. We are even trying to get CM10.2 working on marvel using this kernel.
EDIT: You might want to check this and this out.
The manifest I'd suggest you to use... (remove my comments )
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_htc_common" path="device/htc/common" revision="gingerbread" />
<project name="vigoos/android_salsa_cm_10.1" path="device/htc/icong" revision="jellybean-r2" />
<project name="Do not use 3.x kernel..." />
<!-- Fix framework -->
<remove-project name="CyanogenMod/android_frameworks_av" />
<project name="androidarmv6/android_frameworks_av" path="frameworks/av" revision="jellybean"/>
<!-- Fix display -->
<remove-project name="CyanogenMod/android_hardware_qcom_display" />
<project name="WinSuk/android_hardware_qcom_display" path="hardware/qcom/display" revision="jellybean"/>
<!-- Fix msm7k -->
<remove-project name="CyanogenMod/android_hardware_msm7k" />
<project name="androidarmv6/android_hardware_msm7k" path="hardware/msm7k" revision="jellybean"/> androidarmv6 ones are newer, ProjectLlama is old.
</manifest>
You can use this kernel, but you'll probably have to add icong support.
Gesendet von meinem Xperia S mit Tapatalk
Click to expand...
Click to collapse
Danke DjOlivier. It wasn't interrupting but it was rather a big boost.... So we will switch back to owl now. We are able to compile with owl properly, it is not a really big deal. And vielen dank for the XML. I'll fix it today.
Sent from my GT-P3100 using Tapatalk
No problem... Here's CM10.1 git for marvel. I'm utterly convinced CM10.1 will work on icong. 3.x kernel has also been discontinued because the developer lacks time. There are many other devs who have tried to continue, but none of them has succeeded yet. If you need help with CM10.1, I'm here. Also @Kevinjoa, @thehacka1 or @izi501 are experts from wfs fora...
Gesendet von meinem LT26i mit Tapatalk
I got a Question if you dont mind me asking, how stable or bugfree is CM10.1 for WFS? Also since 4.4 got out why not just go directly for that as it seems to be running on a lot of the older devices.
CM10.1 is 90-95% bugfree, there are some small bugs here and there but it depends on the user if he notices them or not.
As for CM11 (4.4), we are currently fighting with CM10.2 for WFS. I don't think it's possible to port it. Nah, wait: It's certainly possible, but that will cost you a huge amount of time and it will probably never run well. Support for ARMv6 was dropped long time ago and there are so many features that won't work on armv6. So let's better port CM10.1 and make it as stable as possible.
Gesendet von meinem LT26i mit Tapatalk
djolivier said:
...
<project name="androidarmv6/android_frameworks_av" path="frameworks/av" revision="cm-10.1"/>
<!-- Fix msm7k -->
<remove-project name="CyanogenMod/android_hardware_msm7k" />
<project name="androidarmv6/android_hardware_msm7k" path="hardware/msm7k" revision="cm-10.1"/>
Click to expand...
Click to collapse
I would suggest the branch cm-10.1 instead of jellybean because it doesn't compile without error.
djolivier said:
<project name="airk000/hardware_qcom_display" path="hardware/qcom/display" revision="jellybean2" />
Click to expand...
Click to collapse
I try now airk000 instead of WinSuk.
The guys from AndroidARMv6 have a CM-10.2 and 11 branch too, so we can hope that maybe a device like Wildfire S or Salsa could run the newer Android versions. But that doesn't make sense, if only three or more people try to get these Android versions working. It is not very difficult but it takes a long time. I do that only in my free time as an engineer student.
EDIT:
 @vigoos
device/htc/icong/libcamera/mt9v113.c:25:23: fatal error: linux/io.h: No such file or directory
I think media/mt9v113.h and mt9v113_regs.h could be the next error messages. I have to check this first, but mt9v113 is not in kernel 3.0.x. Switching back to an older kernel would be a better idea or I try to find the right files to integrate them into kernel.
I totally agree with you, but why not using WinSuk's qcom display?
As I said above, 4.4 is possible. But I also lack time since I'm a student (who goes to school) and a build environment. Back to Kitkat, it may work, but if not, we have to accept that armv6 development slows down and it's only a matter of time until even devs abandon their projects and move along to other devices (if they haven't already).
Gesendet von meinem ODYS-Chrono mit Tapatalk 2
I made a CM10.1 build for icong but I am not sure if it will boot. I used marvel things and renamed them to icong.
Can anyone make a kernel config for icong based for this kernel :https://github.com/OWLProject/OWL-Predator-KERNEL
CM10.1 build is here: cm-10.1-20131115-UNOFFICIAL-icong.zip - 115.99 MB
Kevinjoa said:
I made a CM10.1 build for icong but I am not sure if it will boot. I used marvel things and renamed them to icong.
Can anyone make a kernel config for icong based for this kernel :https://github.com/OWLProject/OWL-Predator-KERNEL
CM10.1 build is here: cm-10.1-20131115-UNOFFICIAL-icong.zip - 115.99 MB
Click to expand...
Click to collapse
In arch/arm/configs/cyanogen_msm7227_defconfig from OWL-Predator-KERNEL you find a config that works. Maybe CPU frequencies have to be changed.
Make me a icong.config and I will build rom again and you will tell me if it works

[GUIDE]Adding Extra Pages in Settings

Hello Today I Have Bring {GUIDE}.All the Credits goes to PineappleOWL.So I have Modify Some Things.
Downloads-Link in Attachment
Instructions:
Pull Setting from Your Phone
apktool d Settings.apk
Downloads the File and extract
Open AndroidManiFiest
find
HTML:
<uses-library android:name="touchwiz" />
below add this
HTML:
<activity android:name="ExtraPages" />
recomnile settings
decomnile its again
open Pubic.xml from for values/public
find extra_pages note ids code
open smali/com/shadman0/ExtraPages
Find
[HTM]L0x7f04003b[/HTML]
change it to accroding to your Public.xml
open string add this
HTML:
<string name="extra_pages">Extra Pages</string>
befor </resources>
open res/xml/settings.xml
paste this before Resources
HTML:
<com.android.settings.IconPreferenceScreen android:title="@string/extra_page" settings:icon="@drawable/milkshake_bar">
<intent android:targetPackage="com.android.settings" android:action="android.intent.action.MAIN" android:targetClass="com.android.shadman0.ExtraPages" />
</com.android.settings.IconPreferenceScreen>
Credits:
PineappleOWL
Reserved

Out of no where, Errors w/in AndroidManifest.xml - Help Please...

Things have been going good within the app and I have been running the app on my phone or tablet throughout the build with no issues.
All of a sudden, I have errors within the Manifest and it will not run/load on to my phone or tablet any longer.
I have googled for answers and "fixes" but have not been able to make any progress, I hope that I can get help here and get everything back in working order so I can move forward with the build.
The only thing I can think of that I did prior to seeing the errors was I may have "Alt+Enter" and chose API Google by accident at one point.
I went back and deleted all the Google things from my manifest and so forth. It was at this point I noticed the errors within the manifest.
AndroidManifest.xml
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="com.example.z.flowmaster">
<application ---------------------------> App is not indexable by Google Search; consider adding at least one Activity with an ACTION-VIEW intent filler.
android:allowBackup="true" --------------------------------------------- On SDK Version 23 and up, your app data will be automatically backed up and restored on app install. Consider adding the
android:icon="@mipmap/ic_launcher" ---------------------------------attribute android:fullBackupContent to specify an @xml resource which configures which files to backup. More info at ............
android:label="Backflow Master"
android:supportsRtl="true"
android:theme="@style/AppTheme" />
<activity android:name=".ActivityHome"> ------------> Element activity not allowed here / This inspection highlights unallowable XML ......
<intent-filter> --------------> Element intent-filter is not allowed here / This inspection highlights unallowable XML tags in Android rsource files & AndroidManifest.xml
<action android:name="android.intent.action.MAIN" /> --------> Element action is not allowed here / This inspection highlights unallowed XML .....
<category android:name="android.intent.category.LAUNCHER" /> --------> Element catagory is not allowed here / This inspection highlights ......
</intent-filter> ----------> Element intent-filter is not allowed here / This inspection highlights unallowable XML tags in Android resource files & AndroidMainfest.xml
</activity> --------------------------> says same as below "activity"
<activity android:name=".TestingMain" /> ---------------> "activity" is highlighted "Element activity is not allowed here."
<activity android:name=".TestingRP" /> --------------------------- This inspection highlights unallowed XML tags in Android resource files and AndroidManifest.xml
<activity android:name=".TestingDC" />
<activity android:name=".TestingPVB" />
<activity android:name=".TestingSRVB" />
<application/>
</manifest>
Assuming you are using AS, under the build tab in Android Studio, try clicking on "Clean" and then do a "Re-build"
Yes, I am using Android Studio 2.1.1
* However, I will note that at the time the error first occurred I was using 1.5.1 I believe.
After getting the error and trying a few things to rid the error, I finally just uninstalled the full program and reinstalled (new version) Android Studio.
I think I reinstalled everything correctly but I could have left something out or something is out of place I guess.
I feel like I have checked to make sure the reinstall was done correctly but that's not saying I didn't miss something...
After going to >Build >Clean Project I receive the following in my Messages "Gradle Build":
! A problem occurred evaluating project ':app'.
>Failed to apply plugin [id'com.android.application']
>Gradle version 2.10 is required. Current version is 2.8. If using the gradle wrapper, try editing the distributionUrl in C:/Users .....
! BUILD FAILED
! Total time: 0.611 secs
! 1 error
! 0 warnings
! See complete output in console
When I "Rebuild" it gives me the same as above.
Can you post the contents of your Gradle properties files here. I think this is where the issue lies "Gradle version 2.10 is required. Current version is 2.8. If using the gradle wrapper, try editing the distributionUrl in C:/Users ....."
-Project-
v Flowmaster
v app
build.gradle
apply plugin: 'com.android.application'
android {
compileSdkVersion 23
buildToolsVersion "23.0.1"
defaultConfig {
applicationId "com.example.z.flowmaster"
minSdkVersion 16
targetSdkVersion 23
versionCode 1
versionName "1.0"
}
buildTypes {
release {
minifyEnabled false
proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
}
}
}
dependencies {
compile fileTree(dir: 'libs', include: ['*.jar'])
testCompile 'junit:junit:4.12'
compile 'com.android.support:appcompat-v7:24.0.0-alpha1' ----------> This support library should not use a different version (24) than the compileSdkVersion(23) / There are some combinations of libraries, or tools and libraries, that are incompatible, or can lead to bugs. One such incompatibility is compiling with a version of the Android support libraries that is not the latest version (or in particular, a version lower than your targetSdkVersion.)
}
-Project-
v Flowmaster
v gradle
v wrapper
- gradle-wrapper.jar
v gradle-wrapper.properties
#Wed Oct 21 11:34:03 PDT 2015
distributionBase=GRADLE_USER_HOME
distributionPath=wrapper/dists
zipStoreBase=GRADLE_USER_HOME
zipStorePath=wrapper/dists
distributionUrl=https\://services.gradle.org/distributions/gradle-2.8-all.zip
-Project-
v Flowmaster
v gradle
- build.gradle
// Top-level build file where you can add configuration options common to all sub-projects/modules.
buildscript {
repositories {
jcenter()
}
dependencies {
classpath 'com.android.tools.build:gradle:2.1.0'
// NOTE: Do not place your application dependencies here; they belong
// in the individual module build.gradle files
}
}
allprojects {
repositories {
jcenter()
}
}
task clean(type: Delete) {
delete rootProject.buildDir
}
-Project-
v Flowmaster
v gradle
- build.properties
# Project-wide Gradle settings.
# IDE (e.g. Android Studio) users:
# Gradle settings configured through the IDE *will override*
# any settings specified in this file.
# For more details on how to configure your build environment visit
# http://www.gradle.org/docs/current/userguide/build_environment.html
# Specifies the JVM arguments used for the daemon process.
# The setting is particularly useful for tweaking memory settings.
# Default value: -Xmx10248m -XX:MaxPermSize=256m
# org.gradle.jvmargs=-Xmx2048m -XX:MaxPermSize=512m -XX:+HeapDumpOnOutOfMemoryError -Dfile.encoding=UTF-8
# When configured, Gradle will run in incubating parallel mode.
# This option should only be used with decoupled projects. More details, visit
# http://www.gradle.org/docs/current/userguide/multi_project_builds.html#sec:decoupled_projects
# org.gradle.parallel=true

Categories

Resources