yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] DualJoe:
No, sorry. Its impossible to tell anything for sure. It depends on many things and i don't recommend trying this if you can't recover from a bootlooped state.

That's the same thing i had in mind. Did it work?
[Miscellaneous Android Development] max0r4axor:
I haven't gotten the chance to work the bugs out it semi works and since I can't really brick this cause I have the original firmware I'm trying lots of different things
[Miscellaneous Android Development] DualJoe:
I would load all modules and see if it works. If not try switching to your kernel. Watch 'twrp.log' and 'dmesg' for errors to clean up at the end.
[Miscellaneous Android Development] summan1G:
Hi,I want to install you TWRP,but i have Read-only file system. Can you help me to remount my Tablet on rw file system?

I have Assistant AP-110,on Allwinner A20 / 10,1"/ but command mount -o remount,rw /system or mount -o remount,rw /dev/block/system /system, or mount -o remount,rw /dev/block/nandd /system not work...(EXT4 FS)...

Help me please)
[Miscellaneous Android Development] DualJoe:
The device is probably not rooted. That's an individual problem i can't help you with.
[Miscellaneous Android Development] randomblame:
[MENTION=4293606]DualJoe[/MENTION] can you share the device tree you used to build this? Trying to set up a device tree for a20
[Miscellaneous Android Development] DualJoe:
I've set up a git repo.

https://github.com/BlueMax/android_device_softwinners_wing_d9
[Miscellaneous Android Development] randomblame:
many thanks, I found the a20 sdk with included trees and was aghast at the coding style I've been trying to clean it and adapt it to my needs all day. The kernel source that was included in that sdk is borked too. could you include your wing-common folder as well and if you're compiling kernel that too would be very much appreciated. if not that's ok I'll keep working on the sdk code base
[Miscellaneous Android Development] DualJoe:
I have no wing-common folder. The device folder is the only custom data i used. Rest is original TWRP/CM10.2 fork only. The kernel is just extracted from original image.

I started from scratch with a dumped dd image and extracted data created with cm10.1/build/tools/device/mkvendor.sh.
[Miscellaneous Android Development] randomblame:
awesome thanks a lot I'll poke through it :D
[Miscellaneous Android Development] randomblame:
I'm working on a cm11 compatible tree for my skytex sp1020 a20 device and I thought I'd share it as it's mostly generic to a20 devices. I need to fix the boot.img it outputs and hwcomposer,audio,camera are all nooped at the moment due to old incomplete source. I'm hoping to find the a23 kitkat sdk one of these days that should provide some updated code for those hals. https://github.com/randomblame/android_device_softwinner_sp1020 I'll push changes as I make them.
[Miscellaneous Android Development] insomniacno1:
Awesome post, but I do have some questions:

1. How do you get the device info - which app did you use?

2. does this recovery work for tablets without volume rocker - is it touchbased?

3. Android system info gave me the following info, do you think this recovery can be used with my tablet - it has Allwinner A20 Dualcore 1.2ghz, 1GB DDR3 Ram, 8GB Rom, MicroSD slot for 32GB card, Mini-HDMI, USB OTG port for charging and connectivity, Power button and Back button but no volume rocker.

It has 1024x600 display, and 10 partitions up to nandj?

OS

Browser UserAgent : Mozilla/5.0 (Linux; U; Android 4.2.2; en-us; M-750 Build/JDQ39) AppleWebKit/534.30 (KHTML, like Gecko) Version/4.0 Safari/534.30

Android ID : fb574b4414f81cf8

BuildInfos

Android version : 4.2.2

Release Codename : REL

API LEVEL : 17

CPU ABI : armeabi-v7a

Manufacturer : unknown

Bootloader : unknown

CPU ABI2 : armeabi

Hardware : sun7i

Radio : unknown

Board : wing

Brand : MINAMI

Device : wing-ibt

Display : A20_K70_K702B_1305238.20130824

Fingerprint : MINAMI/wing_ibt/wing-ibt:4.2.2/JDQ39/20130824:eng/test-keys

Host : supperFAE

ID : JDQ39

Model : M-750

Product : wing_ibt

Tags : test-keys

Type : eng

User : inet_wupangpang

I have tried searching on all this info and not much come up, so i'm a bit lost here - hope for some guidance:)

With kind regards

JBJ
[Miscellaneous Android Development] NiceIceDice96:
Hi thanks for it looks good but touch is not working anyway to make it working please really and what TWRP why not CWM need reply I need touch really anything you want from my device to make touch work I'm ready I think you need to input my libinput.so file in the kernel right if yes I will upload it. Wait reply
[Miscellaneous Android Development] silentarts:
Can anyone help me out

Can anyone help me out with an issue accessing Fastboot/Bootloader @ this link
[Miscellaneous Android Development] Wel1973:
Hi, Good morning.

The first thing, to give it thanks for this tutorial.

He wanted to ask, if this recovery: is it Touch?.

Because my Tablet, it is of similar characteristics, and even the kernel has the same partitions in bootloader. But it does not possess buttons to handle it.

The one that it brings for shortcoming (recovery) one handles from the screen, and not for buttons. That's why of my question.

The inconvenient only one is that instead of a D9, my tablet is a D8. But it is similar in everything to the information that appear in the OP.

And the resolution is 1024x600, which I see in the OP that is the correct thing.

In advance, thanks for the posible responses. Tablet is rooted, and memory partitions in bootloader and Kernel, are identical.
[Miscellaneous Android Development] DualJoe:
TWRP is touch only and needs correct touch device driver.
[Miscellaneous Android Development] Wel1973:
Well, come to this point I installed Recovery and he settled well, but my drivers do not support Touch on screen in this way.

What I do not realize yet well, it is because recovery for shortcoming if he supports the Touch..:confused:

I leave a relation of the drivers, which are very similar to those who appear in OP.

I do not know if it might do anything for it, but the knowledge does not come to me to that..

Therefore, I give them to him thanks for everything, anyway.

cdc_ether 2906 0 - Live 0x00000000
rtl8150 8154 0 - Live 0x00000000
mcs7830 4947 0 - Live 0x00000000
qf9700 5167 0 - Live 0x00000000
asix 12313 0 - Live 0x00000000
usbnet 12504 4 cdc_ether,mcs7830,qf9700,asix, Live 0x00000000
sunxi_csi0 28580 0 - Live 0x00000000
gc0308 10968 1 - Live 0x00000000
gc2035 12910 1 - Live 0x00000000
camera 39005 1 sunxi_csi0, Live 0x00000000
videobuf_dma_contig 3816 1 sunxi_csi0, Live 0x00000000
videobuf_core 15283 2 sunxi_csi0,videobuf_dma_contig, Live 0x00000000
gslX680 775149 0 - Live 0x00000000
ft5x02 43271 0 - Live 0x00000000
ft5x06_ts 168678 0 - Live 0x00000000
inet_ctp 1690 3 gslX680,ft5x02,ft5x06_ts, Live 0x00000000
mma865x 6255 0 - Live 0x00000000
bma250 6919 0 - Live 0x00000000
mali 183986 101 - Live 0x00000000 (O)
ump 29740 21 mali, Live 0x00000000 (O)
hdmi 22078 0 - Live 0x00000000
lcd 4126 0 - Live 0x00000000
disp 258280 14 mali,hdmi,lcd, Live 0x00000000
nand 132588 8 - Live 0x00000000 (O)

M.P: Well, now there is nothing to do....

I recovered backup-recovery for shortcoming and now the Tablet dont wont boot.

its stuck in the Splashscreen...I cant understand that, but its true.

Forget any type of help .... it will not serve for anything, in this case..:good:

And sorry for inconveniences.
[Miscellaneous Android Development] NiceIceDice96:
So please help us we need it replace the touch driver i think it is libinput.so in system folder so please help us you are our hope for A20
[Miscellaneous Android Development] DualJoe:
There are too many different drivers. You have to take care of that yourself.

You can use Android Image Kitchen to unpack the image and replace the files yourself. In the case of Wel1973 i would replace 'ft5x_ts' with 'ft5x02' and 'ft5x06_ts' by swapping the files and changing 'init.rc' respectively. You can also try to swap the kernel (/split_img/recovery.img-zImage). Always make sure you have a backup dd image of your /system partition in case you have to recover with LiveSuite, PhoenixCard. I can't help with that any further.
[Miscellaneous Android Development] Wel1973:
God knows that I am trying it... ;)

I don´t get tired so easily, think that I will recover it.

Thanks for the info. Anyway..

When I have it, I will try it again.:cool: if it´s posible.
[Miscellaneous Android Development] NiceIceDice96:
I will try in 2 and half month
[Miscellaneous Android Development] Wel1973:
Hello again.

Since I recovered the Tablet, as i said, I returned for the recovery, but it continues touch one does not work in the above mentioned way.

I did the modifications of Software that mentioned, and it continues without running for me. There is no touch one on the screen of recovery, therefore it is not possible to use.

The changes were the following ones....

[STRIKE]insmod/ft5x_ts.ko[/STRIKE]

insmod/ft5x02.ko
insmod/ft5x06_ts.ko

I don`t know what more to do so that it works.
[Miscellaneous Android Development] NiceIceDice96:
I dont know why all that just make it cwm it is better than TWRP thats alk right just make it cwm and the custom roms will be alot.
[Miscellaneous Android Development] Wel1973:
It is well, but .... where I can find CWM for A20.

I was looking but I did not find it.

If you are so kind of indicating me ... please.
[Miscellaneous Android Development] NiceIceDice96:
I mean I think you can compile one since I dont have pc right now or I did compile and but thats it and I think you can from source tree and it don't need a lot of space like roms
[Miscellaneous Android Development] DualJoe:
[MENTION=4512200]Wel1973[/MENTION]:

You're missing a space in the command. Also check logcat and /tmp/log.txt in TWRP/ADB that the drivers are properly loaded.

It doesn't matter if TWRP or CWM. Its just a matter of preference. You need correct drivers and kernel for both. CWM doesn't work either without hw buttons.
[Miscellaneous Android Development] Wel1973:
The Ist´, thanks for the interjection, I know to true science that CWM it is not Touch. Also, which can adapt oneself only is valid in 10 partitions.

And I`ve got 11....

Therefore, I will continue in this thread, because I am interested it more and cause I prefer this recovery.

Its the recovery that used in my HTC One, and it is the one that I want that it takes my Tablet.

On the other hand, I do not know that you say to me of the space in the command.

I leave to you the drivers that I have at present installed, for if it can help.

I believe that it should not leave to me any space. But I leave them just in case.

cdc_ether 2927 0 - Live 0x00000000
rtl8150 8115 0 - Live 0x00000000
mcs7830 4948 0 - Live 0x00000000
qf9700 5168 0 - Live 0x00000000
asix 12318 0 - Live 0x00000000
usbnet 12521 4 cdc_ether,mcs7830,qf9700,asix, Live 0x00000000
sunxi_csi0 28933 0 - Live 0x00000000
gc0308 10969 1 - Live 0x00000000
gc2035 12911 1 - Live 0x00000000
camera 37886 1 sunxi_csi0, Live 0x00000000
videobuf_dma_contig 3817 1 sunxi_csi0, Live 0x00000000
videobuf_core 15292 2 sunxi_csi0,videobuf_dma_contig, Live 0x000
gslX680new 395888 0 - Live 0x00000000 (F)
ft5x02 45456 0 - Live 0x00000000
ft5x06_ts 15337 0 - Live 0x00000000
inet_ctp 1691 3 gslX680new,ft5x02,ft5x06_ts, Live 0x00000000
mma865x 6273 0 - Live 0x00000000
bma250 6776 0 - Live 0x00000000
mali 115478 61 - Live 0x00000000 (O)
ump 29858 15 mali, Live 0x00000000 (O)
hdmi 22821 0 - Live 0x00000000 (O)
lcd 8150 0 - Live 0x00000000
disp 260142 18 mali,hdmi,lcd, Live 0x00000000
nand 133273 8 - Live 0x00000000 (O)
[Miscellaneous Android Development] DualJoe:
wrong:
insmod/ft5x02.ko
insmod/ft5x06_ts.ko

right:
insmod /ft5x02.ko
insmod /ft5x06_ts.ko

Then start twrp, connect adb and look up the log files.

dmesg
cat /tmp/log.txt (not sure if the name is correct. Its the twrp log file).

They will tell you if some dependencies are missing or something's wrong. You can also inject even more driver or even inject them manually with adb after twrp has been started (at least to verify that they can be loaded properly).
[Miscellaneous Android Development] NiceIceDice96:
If he did that do it will work on my tablet hey listen please can you please tell us the specs and pictures of your tab
[Miscellaneous Android Development] Wel1973:
Of course...

View attachment 2670060

LCD 7" TFT Screen

Screen Resolution 1024 x 600 Pix

Processor 1.0 Ghz Dual Core Allwinners A20 (i think its posible to be 1.2 but not working ever on this frecuencies)

Chipset / Boxchip Allwinner A20

RAM1 1GB DDR3 DRAM

Built in Memory 8 GB

External Memory Support Micro Card (Max 32GB)

Wifi 802.11 b/g/n supported

Bluetooth N/A

Sim N/A

Camera 0.3 Megapixel front , 1.3 mp rare cam

HDMI /3g Dongle HDMI (1080 P) ,Support 3G Dongle

Microphone Built IN

Android: 4.2.2

If you need something more, tell me please.

[MENTION=4293606]DualJoe[/MENTION].

It is not possible for me, to connect ADB being in TWRP, because I do not have mounted Data.

It is a foolery that he says to you, that it is not possible that it mounts it because I cannot gain access to the option Mount.

And so, in this moment I am stopped again in recovery without ADB and without knowing that to do.
[Miscellaneous Android Development] DualJoe:
But you can connect to the device? You actually get a shell? If yes, can you post the output of 'mount'?
[Miscellaneous Android Development] Wel1973:
Yes, I´ve got shell but not in recovery mode. In this way it does not tune in adb, unless you have mounted Data, across the same recovery. correct me if I am wrong.

But only I have shell when I´ve got Tab booted in systema. But not in recovery.

Not even the recovery Stcok, connects me for adb. I say this, because this recovery takes the option of Adb Sideload, which me never worked.

|root@android:/ # mount
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/system /system ext4 ro,relatime,nobarrier,data=ordered 0 0
/dev/block/data /data ext4 rw,nosuid,nodev,noatime,journal_checksum,nobarrier,no
auto_da_alloc,data=ordered 0 0
/dev/block/cache /cache ext4 rw,nosuid,nodev,noatime,journal_checksum,nobarrier,
noauto_da_alloc,data=ordered 0 0
/dev/block/vold/93:80 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,u
id=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset
=ascii,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/93:80 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relat
ime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioch
arset=ascii,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.aldiko.android-1 ext4 ro,dirsync,nosuid,nodev,noat
ime 0 0
root@android:/ #
[Miscellaneous Android Development] NiceIceDice96:
The same exaxtly mine just my tablet 8inch not 7 and res 1024*768

View attachment 2670235

View attachment 2670239

Rootes replaced most apps with the stock 4.2.2 apps original like launcher keyboard vrowser gallery what I can say everything and I wish I have a recovery lije cwm or TWRP but I think I wilk get one soon right? You can answer me i will make a custom rom soon and overlocked kernel and maybe cm10.1 or cm11 ;)
[Miscellaneous Android Development] DualJoe:
Give me the output of:

cat /proc/cmdline
cat /proc/partitions

There's probably something wrong with enumerating/aliasing/mounting the partitions. That's usually been done by the 'init_parttion.sh' script that is fired up in 'init.rc'. We can try to do it manually that might be more reliable.

Also make sure if you ever edit any text files to use Linux line endings (LF). Use tools like Notepad++ to edit if you work on Windows.

And the most important thing: Make sure you have a 'dd' image of your /system partition on your PC. If you lose that data (essential files, drivers) the device might be useless. Many A20 devices are noname products without any vendor support and thus have no rom images on the net.
[Miscellaneous Android Development] NiceIceDice96:
But I think the most important thing recovert kernel cuz the system can be found in any A20 firmware and there is a lot of them when you lose your system be sure you have the kernel and recocery then inject via adb recocery the system file and that is all right
[Miscellaneous Android Development] Wel1973:
Of course. In same moment that has it decisive, we speak. And if it is possible promptly...

It would be loved of helping you, on your Rom.

I have someone done for my phone. And I share them, not in this forum but yes in one of Spain. I speak with Sense, but I love CM. It is wonderful.

If achievement to put it, you and the presents will be it first in seeing it.

But now, I have to stop, it is in the evening in Spain and my duties as father begin at once.:D

---------- Post added at 08:45 PM ---------- Previous post was at 08:34 PM ----------

Do not worry about that, I already have it quite tied, have a Firmware of recovery of my Tab.

So nothing to lose. Also I´ve made a backup of ALL lol that I have installed by ADB. Which I can recover in any time.

Bony, that I have everything what I need to set it to run...

I understand his worry but there is not of that to do it;)

cat /proc/cmdline

console=ttyS0,115200 root=/dev/system init=/init loglevel=4 partitions=bootloade
r@nanda:env@nandb:boot@nandc:system@nandd:data@nande:misc@nandf:recovery@nandg:c
ache@nandh:databk@nandi:private@nandj:UDISK@nandk

cat /proc/partitions

major minor #blocks name

7 0 16664 loop0
93 0 16384 nanda
93 8 16384 nandb
93 16 16384 nandc
93 24 638976 nandd
93 32 1048576 nande
93 40 16384 nandf
93 48 32768 nandg
93 56 524288 nandh
93 64 262144 nandi
93 72 16384 nandj
93 80 4276224 nandk
254 0 16663 dm-0
[Miscellaneous Android Development] DualJoe:
Looks like the partition boundaries are wrong. Use the kernel from your rom instead. Post a 'dmesg' log.
[Miscellaneous Android Development] DualJoe:
If that was dmesg already i meant the other log then. Post /tmp/log.txt. But swap the kernel first. This all is not necessary if it works out of the box then.
[Miscellaneous Android Development] Wel1973:
No, No log.txt

I can´t find any files on temparay.

~ # ←[6ncat /temp/log.txt
cat /temp/log.txt
cat: can't open '/temp/log.txt': No such file or directory
~ # ←[6ncat /temp/twrp.txt
cat /temp/twrp.txt
cat: can't open '/temp/twrp.txt': No such file or directory
~ # ←[6ncat /temp/recoverylog.txt
cat /temp/recoverylog.txt
cat: can't open '/temp/recoverylog.txt': No such file or directory
~ # ←[6ncat /proc/temp/log.txt
cat /proc/temp/log.txt
cat: can't open '/proc/temp/log.txt': No such file or directory
~ # ←[6ncat /temp/twrp
cat /temp/twrp
cat: can't open '/temp/twrp': No such file or directory
~ # ←[6ncat /temp/twrp.txt
cat /temp/twrp.txt
cat: can't open '/temp/twrp.txt': No such file or directory
~ # ←[6ncat /temp/recoverylog.txt
cat /temp/recoverylog.txt
cat: can't open '/temp/recoverylog.txt': No such file or directory
~ # ←[6ncat /temp/recovery.log
cat /temp/recovery.log
cat: can't open '/temp/recovery.log': No such file or directory
~ # ←[6n

And, look at that. There´s no files on Sdcard root about recovery.

~ # ←[6ncd /sdcard/
cd /sdcard/
/sdcard # ←[6nls
ls
Alarms
DCIM
Download
LOST.DIR
Movies
Music
Notifications
Pictures
Podcasts
Ringtones
TWRP
/sdcard # ←[6n

Inside TWRP, there is no file. Thing that is still rarer...
[Miscellaneous Android Development] DualJoe:
Read carefully.. Its tmp not temp. Do an 'ls' first. That's basic bash-fu.

Don't forget to create an image with your kernel first. That's the most important step. The logs are only important after your kernel is running.
[Miscellaneous Android Development] DualJoe:
Then finally tell us what exactly led to success fixing the partition table/boundaries. Swapping just the kernel?
[Miscellaneous Android Development] Wel1973:
I am sorry not to have explained well.

I have only in recovery.log, but it continues without covering the recovery.

There is still not touch in recovery,....

But I do not know because it does not work.
[Miscellaneous Android Development] DualJoe:
I would swap the kernel (zImage) and put all drivers in the image that are running in the main system. Then manually load them with ADB ('insmod ft5x02.ko' and such) one by one. The order might be important (errors about missing symbols/functions) since some drivers rely on others. You have to fiddle around with them, start twice and such. Not all are necessary. Some drivers might even need more files/blobs/dependencies. You will see when you load them manually. Drivers which load properly put in 'init.rc' (Touchscreen drivers need to be started before TWRP anyway).
[Miscellaneous Android Development] NiceIceDice96:
Can you do it by yoyrself please?:rolleyes:
[Miscellaneous Android Development] DualJoe:
I don't have any of these devices anymore and thus cannot test it but you can send me the files and i will try to assemble it as far as possible.

For this i need the following (boot image, system image, root files):

busybox dd if=/dev/block/nandc of=/sdcard/boot.img bs=8M
busybox dd if=/dev/block/nandd of=/sdcard/system.img bs=8M
- all files (*.*) from root folder (/)

Rar/7z it, upload to Zippyshare or any other fast hoster and PM me the links.
[Miscellaneous Android Development] NiceIceDice96:
I will but you have to wait I have a slow speed internet connection maybe in 2 days okay
[Miscellaneous Android Development] DualJoe:
If that's an issue just send me the bootimage (nandc), the root files, system/etc, system/lib, system/vendor and system/build.prop.
[Miscellaneous Android Development] NiceIceDice96:
Okay that is simple wait
[Miscellaneous Android Development] Wel1973:
In agreement.

I´m going to upload files, so that you try to do it, when you have time for us. If it is not an inconvenience.

I am very grateful to him by his gesture.

Anyhow, I on my part will keep on trying, the form that you said to me.:good:
[Miscellaneous Android Development] DualJoe:
But forget about the nandd system image. I've seen its 1GB on some systems. That's not necessary. Use the selected files I've mentioned instead. If there's something missing i will tell ya.

[MENTION=5057875]NiceIceDice96[/MENTION]:

Will check your files in some hours.
[Miscellaneous Android Development] NiceIceDice96:
Okay bty from where you know "ya" are you arabian
[Miscellaneous Android Development] Wel1973:
Ok.

I´ve just sent to him all files.

If something is absent, don´t forget to remember it.

Big THX for all.
[Miscellaneous Android Development] DualJoe:
[MENTION=4512200]Wel1973[/MENTION]:

Sorry, i cannot download from Mega. Use Zippyshare or Dropbox. And better use 7z/rar not zip. Its much smaller.

I just need the boot image, build.prop and vendor folder. No need for system image.

[MENTION=5057875]NiceIceDice96[/MENTION]:

Give me an output of lsmod. I'm not sure what the touch driver is.

Edit:

[MENTION=5057875]NiceIceDice96[/MENTION]:

Try this:
[Miscellaneous Android Development] Wel1973:
Ok, PM send again with links on Dropbox.

Thx!!
[Miscellaneous Android Development] DualJoe:
Thx, nice file size now...

Regarding both images.. I'm quite sure about picking the right touch drivers but i cannot make sure about additional dependencies or loading order. Its possible that it needs some additional tweaking. If anything is not working post both logs again.

Let's see if it runs...
[Miscellaneous Android Development] Wel1973:
Tonight will be flashed.

Not at home at this time. And haven't got Tab here.

Them, will comment results.

Thx in advance.

Enviado desde mi HTC One S mediante Tapatalk
[Miscellaneous Android Development] NiceIceDice96:
Maybe cuz it is not developed for your device now try it please wait