application does not work on rooted samsung galaxy ace - General Questions and Answers

The version checked in the settings of the phone shows 4.1.1, A rooted , custom rom of 4.1.1 is being used. However, while installing an apk that needs (min sdk of 15), I am getting this weird error in eclipse.
ERROR: Application requires API version 14. Device API version is 10 (Android 4.1.1)
Is this the case with custom roms ?

Related

Upgrade an Android device by using "Android Control"

Is it safe to use the "android Control" tool to upgrade android device??
I have a Sharp is01, which is a Adnroid 1.6 system, and I wanted to upgrade it to 2.2 (there is 2.2 froyo system done by another developer)
the software I found here - seems have fuction to flash boot image
http://forum.xda-developers.com/showthread.php?t=1049115

[Q] Simpe app from 4.0.1 mono for android isnt working on lg gt540 2.3.7

here's the problem :
installed
xp sp3
vs 2010 ultimate
monoandroid 4.0.1
installer_r18-windows
- android 4.0.3 (API 15)
- android 4.0 (API 14)
- android 2.2 (API 8)
LGDrivers (I think, that is not necessary)
after i create the default app (with Button and click) in VS 2010
1. run with no debugger
( I try with both API 14 and API 8 too )
And I get :
name.name.apk
name.name-Signed.apk
2. adb install -r name.name-Signed.apk
i receive a text saying "success" and it works on my emulator
BUT
when I run this on my LG GT540 currently running 2.3.7 version I get a message saying:
application has unexpectedly stopped ..
I also tried copying the apk to the phones sdcard and it still didnt work and i also rebooted the phone after instaling the app.
what am i doing wrong ?
why do i get a double name for my app ?
I wont give up from mono for android. Its wonderful and new for me like C# programmer.
I only wont to see default mono app running on my mobile device.

[Q] Problems with galaxy note [N7000] & android commander

Hello this will be my very first post at XDA although i have browsed the forums everyday since i can remember...
here is what i have:
Device: Galaxy Note N7000
Rooted: Yes
CWM: Yes
Rom: Slim Bean [latest version] & all the mods/add ons
Android Version: 4.1.2
Kernel: I did not flash one so it would be the one that comes with slim bean rom.. here is the info in my "about phone settings" 3.0.15-CM-gf76e4eb [email protected] #1
here is my problem:
i have installed everything by the book and i have a fully working note with the slim bean v3.1 [latest] adb works and i can successfully get root access using "adb shell su" i have the latest busybox pro installed and the latest supersu pro installed.
i have always used android commander to pull and push files to and from devices and other stuff without any problems, but with my new galaxy note i constantly get the root access NO. i have usb debugging enabled and i even have adb over network enable either way i still have no root access... if anyone can help me solve this i will be willing to donate i am at my witts end trying to figure it out..
people have told me many things such as i have a stock kernel or i need to fnd a way of changing secure adb to insecure adb whatever this means...
thanks in advance
[SOLVED]
it was the kernel which stopped root access being given to android and total commander so the slimbean kernel was based on stock or so i would guess.. i flashed the hydracore OC v7 kernel from xda and bam it works great now lol..

Mount your Android device properly on Linux.

Hi all ,
This topic is about how to mount your Android device and have it transferring files easily & smoothly using Linux on your PC.
- This topic is related to solving the unstable file transfer between the linux system and MTP file system included in Android version 4.xxx & Higher ( Starting from Ice Cream Sandwich - ICS ).
- All Android version before ICS should not continue reading , as their devices should be read as ( Mass storage Device ) , in other words , the Linux OS will read devices as if it was a USB flash memory.
- The is solution for the laggy Folder opening , Solving the problem of which the files transfer suddenly stops before completing the transfer , specially with big files such as Films , Albums ,...etc.
- I'M NOT SURE that this is going to work with all ICS , JB & Higher devices but the below was tested on a Samsung Tab 2 P5100 device running Jelly bean ( JB ) 4.1.2 official stock ROM , & The below worked perfectly for me.
- Using Linux Mint 14 Cinnamon ( MINT is based on UBUNTU ) / 64 Bit version / Kernel Upgraded _unofficially_ to the latest stable kernel release 3.9.2
1. get Android SDK for Linux from : developer.android.com/sdk/index.html
2. Unpack it to your location
Note: if you have already downloaded Android SDK before, check that the version of SDK tools is latest.
3. turn on Debug mode in your Samsung tab.
4. run the command:
[your location]/android-sdk-linux_x86/tools/ddms
OR just open the folder TOOLS from the extracted folder & Run DDMS ( RUN it normally , Not RUN IN TERMINAL).
5. Click in menu Device -> File Explorer
Here you drag-n-drop your files to any location on your device.
Source (Including snapshots) :
- misha.beshkin.lv/how-to-copy-files-to-samsung-galaxy-ii-tab-from-linux-via-usb/
Thank you & Sorry if my topic looks messy , this is my first time here.
mehrdadfisher said:
This is my own experience as well.
Would it be possible please send me the details.
Click to expand...
Click to collapse
Hi there , wud u plz clarify what do u mean by the details ? , I think the details are already mentioned up there , If you are talking about using the developer's SDK to transfer files.

android emulate failed using AOSP source

Hi, I downloaded android full sources 5.1, 6.0, 7.0 and i built them.
I tried to check operating using the android emulator in sdk, but it failed except 5.1.
I replaced original image file( system.img, ramdisk.img, userdata.img) to new built files. And then I run. But I can't see android logo and it didn't progress.
I chose mini-emulator-arm-debug and original emulator image same to version and AOSP.
I didn't know why android 5.1 is operated but android 6.0 and 7.0 didn't do it. Has the method of execution changed?
So please help me.
1. The source build is succeeded.
2.Emulator screen showed only black. I tried to connect using adb shell but failed.

Categories

Resources