yashsingh1/xdaforums huggingface dataset:
[Android Software Development] ls777777:
hei , i can't unpack my kernel boot.img，what should i do?​

Android Image Kitchen - UnpackImg Script

by osm0sis @ xda-developers

Supplied image: boot.img

Removing old work folders and files . . .

Setting up work folders . . .

Image type: AOSP

Signature with "AVBv2" type detected.

Splitting image to "split_img/" . . .

ANDROID! magic found at: 0

BOARD_KERNEL_CMDLINE console=ttyMSM0,115200n8 androidboot.hardware=qcom androidboot.console=ttyMSM0 androidboot.memcg=1 lpm_levels.sleep_disabled=1 video=vfb:640x400,bpp=32,memsize=3072000 msm_rtb.filter=0x237 service_locator.enable=1 swiotlb=1 androidboot.usbcontroller=a600000.dwc3 firmware_class.path=/vendor/firmware_mnt/image earlycon=msm_geni_serial,0x880000 loop.max_part=7 cgroup.memory=nokmem,nosocket buildvariant=user

BOARD_KERNEL_BASE 0x00000000

BOARD_NAME

BOARD_PAGE_SIZE 4096

BOARD_HASH_TYPE sha1

BOARD_KERNEL_OFFSET 0x00008000

BOARD_RAMDISK_OFFSET 0x01000000

BOARD_SECOND_OFFSET 0x00f00000

BOARD_TAGS_OFFSET 0x00000100

BOARD_OS_VERSION 9.0.0

BOARD_OS_PATCH_LEVEL 2019-05

BOARD_HEADER_VERSION 1

BOARD_HEADER_SIZE 1648

Warning: No ramdisk found to be unpacked!

View attachment 5907087
[Android Software Development] osm0sis:
Your log shows it unpacks perfectly. Read the FAQ.
[Android Software Development] psycko31360:
hello ! have a problem when i repackimg.bat, no work and give me ramdisk-new.cpio.tar ?

i'm on w10 and i try unpackimg and repackimg a recovery.img
[Android Software Development] osm0sis:
No log, no .img, no help.

Have you read the FAQ lately?
[Android Software Development] ivan jo hann:
Thanks
[Android Software Development] Ggff5:
Mkbootimg: Repacking Android recovery produce corrupted image

I want to replace the kernel inside twrp 12.1 recovery with my kernel that I built. Now with only unpacking and repacking the recovery image I end up with an image of different size The recovery im...

android.stackexchange.com
[Android Software Development] osm0sis:
Not my tool, also, read the faqqing FAQ.
[Android Software Development] sunnysigara:
I unpack rooted moto e2 2015 (outus, Android 5.0) boot.img with this. Only changed one line fstab.qcom to use my sdcard (f2fs) as internel storage. Test Booted with flashboot boot image-new.img.

It works except wifi and 3G. Wifi won't toggle nor 3g. Wifi config is disabled as well.

Bluetooth, audio also also works. Didn't change anything to /persist. And it still doesn't work. What could be the issue here ?
[Android Software Development] vicenteicc2008@gmail.com:
i have a samsung galaxy s5 mini duos with qualcomm snapdragon 400 and i am trying to boot EDK2 (UEFI) on my samsung galaxy s5 mini duos and it is stuck on the boot logo (i made the boot image with AIK)
[Android Software Development] badabing2003:
Is this a known issue?

Passing the --local fails with

Unrecognized format.
Error!

But without it works fine

E:\pf-data\boot_images4\fcfe07f67b4e676f04b88659ef52f4e79727ad74\boot>C:\Apps\AndroidImageKitchen\unpackimg.bat --local boot.img
Android Image Kitchen - UnpackImg Script
by osm0sis @ xda-developers

Supplied image: boot.img

Setting up work folders . . .

Unrecognized format.
Error!

Press any key to continue . . .

E:\pf-data\boot_images4\fcfe07f67b4e676f04b88659ef52f4e79727ad74\boot>C:\Apps\AndroidImageKitchen\unpackimg.bat boot.img
Android Image Kitchen - UnpackImg Script
by osm0sis @ xda-developers

Supplied image: boot.img

Setting up work folders . . .

Image type: AOSP

Signature with "AVBv2" type detected.

Splitting image to "split_img/" . . .

ANDROID! magic found at: 0
BOARD_KERNEL_CMDLINE
BOARD_PAGE_SIZE 4096
BOARD_OS_VERSION 13.0.0
BOARD_OS_PATCH_LEVEL 2023-08
BOARD_HEADER_VERSION 3
BOARD_HEADER_SIZE 1580

Unpacking ramdisk to "ramdisk/" . . .

Compression used: lz4-l
6975 blocks

Done!
[Android Software Development] ipdev:
Not sure if it helps but, it works correctly on Linux.

[Fedora 37]

[ip@lost AIK-Linux]$ ./unpackimg.sh boot.img

Android Image Kitchen - UnpackImg Script
by osm0sis @ xda-developers

Supplied image: boot.img

Setting up work folders...

Image type: AOSP

Signature with "AVBv2" type detected.

Splitting image to "split_img/"...
ANDROID! magic found at: 0
BOARD_KERNEL_CMDLINE
BOARD_PAGE_SIZE 4096
BOARD_OS_VERSION 13.0.0
BOARD_OS_PATCH_LEVEL 2023-08
BOARD_HEADER_VERSION 3
BOARD_HEADER_SIZE 1580

Unpacking ramdisk (as root) to "ramdisk/"...

Warning: Using cpio 2.13 may result in an unusable repack; downgrade to 2.12 to be safe!

Compression used: lz4-l
6975 blocks

Done!

Out of curiosity did it only start with the Pixel 5 Aug. build?

[TQ3A.230805.001]

Cheers. :cowboy:
[Android Software Development] badabing2003:
I'll do some testing, I had used that flag previously, perhaps it has something to do with the long path, or it being on a different drive.

In fact I had created a Windows SendTo wrapper script to unpack in the directory of the IMG with a consistent naming pattern to make it easy to diff with patched IMG.

It always used that flag.

Yesterday I wanted to use it and to my surprise it failed.

I'll do some more testing, just wanted to check first if it was a known issue before diving in.
[Android Software Development] badabing2003:
It's the file command that is failing when the image file is not on the same drive as the tools.

C:\Temp>"C:\Apps\AndroidImageKitchen\\android_win_tools"\file -m "C:\Apps\AndroidImageKitchen\android_win_tools\androidbootimg.magic" "E:\Temp\boot.img"
C, 0: Warning: using regular magic file `\Apps\AndroidImageKitchen\\android_win_tools\androidbootimg.magic'
E:\Temp\boot.img: AOSP bootimg

C:\Temp>e:

E:\Temp>"C:\Apps\AndroidImageKitchen\\android_win_tools"\file -m "C:\Apps\AndroidImageKitchen\android_win_tools\androidbootimg.magic" "E:\Temp\boot.img"
C, 0: Warning: using regular magic file `\Apps\AndroidImageKitchen\\android_win_tools\androidbootimg.magic'
file: could not find any valid magic files! (No such file or directory)

A non-consequential minor issue is that this "%bin%"\file

is adding a duplicate unnecessary \
[Android Software Development] BORETS24:
Hi. I have OnePlus Nord C3 Lite 5G running Android 13 and unlocked bootloader of course. Even if I try unpack stock ROM boot.img then repack without any changes then flash in both slots A and B then I get unbootable device with red screen

View attachment 5979763

(when I flash only in one of the slots then bootloader restarts and boot phone with other slot successfully which have non-modified boot.img)

Unpack log

Android Image Kitchen - UnpackImg Script
by osm0sis @ xda-developers

Supplied image: bootc3.img

Removing old work folders and files (as root)...

Setting up work folders...

Image type: AOSP

Signature with "AVBv2" type detected.

Splitting image to "split_img/"...
ANDROID! magic found at: 0
BOARD_KERNEL_CMDLINE
BOARD_PAGE_SIZE 4096
BOARD_OS_VERSION 12.0.0
BOARD_OS_PATCH_LEVEL 2023-07
BOARD_HEADER_VERSION 3
BOARD_HEADER_SIZE 1580

Unpacking ramdisk (as root) to "ramdisk/"...

Warning: Using cpio 2.13 may result in an unusable repack; downgrade to 2.12 to be safe!

Compression used: gzip
103977 blocks

Done!
borets@borets-virtual-machine:~/1/AIK-Linux$

Repack log with ./unpackimg.sh --origsize command

Android Image Kitchen - RepackImg Script
by osm0sis @ xda-developers

Packing ramdisk (as root)...

Warning: Using cpio 2.13 may result in an unusable repack; downgrade to 2.12 to be safe!

Using compression: gzip

Getting build information...
kernel = bootc3.img-kernel
cmdline =
os_version = 12.0.0
os_patch_level = 2023-07
header_version = 3

Building image...

Using format: AOSP

Padding to original size...

Done!
borets@borets-virtual-machine:~/1/AIK-Linux$

*-bootc3.img is the name of my stock non-modified boot.img

Attach stock ROM boot.img here. Please give me advices what should I do? Thanks anyway
[Android Software Development] osm0sis:
Well first of all you ignored the cpio warning, and if that doesn't fix it then it might need proper avb 2.0 signing to boot.

Not sure what part of "unusable repack" made you think it would work.
[Android Software Development] BORETS24:
When I'm used Andoid Pie and Q device's boot.img then AIK-Linux after unpacking created /split_img/"boot_name".img-sigtype file contains "AVB" text then I repack and got signed boot.img, In present time on OnePlus Android 13 I have no sigtype-file after repack, it means AIK-Linux packing unsigned boot.img in my case? How can I try to sign repacked boot.img with AVBv2 key? Any utilities? In your repackimg.sh scpript I can't to find any info abot AVBv2. Sorry, it's my first phone with android 11+ specific boot images, A/B slots etc. and I can't to know some important (or simply even)things
[Android Software Development] osm0sis:
Read FAQ #2 for avb 2.0 info.
[Android Software Development] osm0sis:
Read the FAQ. Or the post directly before yours.
[Android Software Development] badhabit_wb:
I'm not sure why but can't get the boot image to work on Pixel 8 pro. any help is appreciated. It's my first time using it. I attached the repacked image. I used the correct image from anykernel3. I'm still using magisk.

Microsoft Windows [Version 10.0.22621.2506]

(c) Microsoft Corporation. All rights reserved.

C:\Users\Herman\Desktop\Desktop\Pixel 8 Pro\AIK\Android.Image.Kitchen.v3.8-Win32\Android Image Kitchen>unpackimg.bat boot.img

Android Image Kitchen - UnpackImg Script

by osm0sis @ xda-developers

Supplied image: boot.img

Setting up work folders . . .

Image type: AOSP

Signature with "AVBv2" type detected.

Splitting image to "split_img/" . . .

ANDROID! magic found at: 0

BOARD_KERNEL_CMDLINE

BOARD_PAGE_SIZE 4096

BOARD_HEADER_VERSION 4

BOARD_HEADER_SIZE 1584

Warning: No ramdisk found to be unpacked!

Done!

Press any key to continue . . .

C:\Users\Herman\Desktop\Desktop\Pixel 8 Pro\AIK\Android.Image.Kitchen.v3.8-Win32\Android Image Kitchen>repackimg.bat

Android Image Kitchen - RepackImg Script

by osm0sis @ xda-developers

Warning: Using empty ramdisk for repack!

Getting build information . . .

kernel = boot.img-kernel

cmdline =

os_version = 0.0.0

os_patch_level = 0-00

header_version = 4

Building image . . .

Using format: AOSP

Done!

Press any key to continue . . .

C:\Users\Herman\Desktop\Desktop\Pixel 8 Pro\AIK\Android.Image.Kitchen.v3.8-Win32\Android Image Kitchen>
[Android Software Development] badhabit_wb:
removed
[Android Software Development] Daniel_47:
Hello Everyone, So I decided to compile the Nothing Phone 1's kernel from the original source code. (Link)

I managed to compile it with the AOSP toolchain and got Image, Image.gz files. Then I unpacked the original boot.img from the stock rom and replaced the boot.img-kernel with the Image (renamed it to boot.img-kernel) inside the split_img folder. After that I packed it again and signed the boot image but it just causes bootloop. Here are the commands which I executed. If someone knows what I am doing wrong and can help a bit then that would be great.

Android Image Kitchen - UnpackImg Script
by osm0sis @ xda-developers

Supplied image: boot.img

Setting up work folders...

Image type: AOSP

Signature with "AVBv2" type detected.

Splitting image to "split_img/"...
ANDROID! magic found at: 0
BOARD_KERNEL_CMDLINE
BOARD_PAGE_SIZE 4096
BOARD_OS_VERSION 11.0.0
BOARD_OS_PATCH_LEVEL 2022-11
BOARD_HEADER_VERSION 3
BOARD_HEADER_SIZE 1580

Unpacking ramdisk (as root) to "ramdisk/"...

Compression used: gzip
42353 blocks

Done!

Android Image Kitchen - RepackImg Script
by osm0sis @ xda-developers

Warning: Overwriting existing files!

Packing ramdisk (as root)...

Using compression: gzip

Getting build information...
kernel = boot.img-kernel
cmdline =
os_version = 11.0.0
os_patch_level = 2022-11
header_version = 3

Building image...

Using format: AOSP

Done!

Command which I used to sign:

avbtool.py add_hash_footer --image image-new.img --partition_size 100663296 --partition_name boot

Thanks!
[Android Software Development] osm0sis:
That looks correct to me. Have you tried repackimg --original to rule out the ramdisk? Should be fine repacking with root, but always a good first step in troubleshooting. Failing that I'd suggest talking to someone else who's built for your device before; maybe your bootloader needs verity/verification disabled in vbmeta in order to accept altered images, or something.
[Android Software Development] Eric gagnon:
Ok cool
[Android Software Development] whatsisnametake2:
I'm currently doing exactly the same with my p8p. I came here to check what the ramdisk parts of the readout were but I see yours is the same. have you made any progress? what problems were you encountering?
[Android Software Development] osm0sis:
Remember, ramdisk is in init_boot now, kernel is in boot. That said, AIK is not ready to repack hdr_v4 at all yet. Maybe I'll have some time to work on it over the holidays, we'll see.
[Android Software Development] whatsisnametake2:
header version 4 is what comes up when I repack my pixel 8 pro img. does the cmd readout a few posts up from a pixel 8 pro look correct? its the same as I get. a user in the pixel 8 forums is saying he is successfully using kernelsu on this device.

on repack I get:

warning: using empty ramdisk for repack!
[Android Software Development] osm0sis:
Yeah if that's your boot image there's no ramdisk, as I just said. And yeah, just because it knows the header version doesn't mean it can repack it correctly.
[Android Software Development] badhabit_wb:
The boot image is not repacked correctly so it won't boot.I didn't flash it I just booted to it.
[Android Software Development] Postman1year:
the NEW MOD img must be SAME-SIZE with the ORG, these must be 96MB, and AVB must add.

And if you want to MOD img (system, boot, vendor, etc.) you had better to MOD your VBMETA.img to remove the boot.img VERIFY, you can offer the ORG VBMETA.img and let me Modify by HEXEDITOR

I just try to Make a img with your new kenel from your FILE(image-new.img), you can test, wait your reply.
[Android Software Development] fbalder18:
Hej Daniel_47, how exactly did you build your kernel? What exact toolchain (from where) and what commands? I don't find a KSU kernel for my device and need to build one, but I never did before...
[Android Software Development] Ibrahim699345:
Hey! Im trying to unpack and repack recovery.img (samsung tab s6 lite), unpacking works but repacking does not , i have installed the following to try to fix it:

Gsudo

Sudo

gzip

But they are not working, can anyone help please?

Error code:

File Not Found

The parameter is incorrect.

Android Image Kitchen - RepackImg Script

by osm0sis @ xda-developers

Packing ramdisk (as root) . . .

Windows sudo required but not found.

*** Reinstall Android Image Kitchen, then add ***

*** sudo.exe to your antivirus exceptions! ***

Error!

Press any key to continue . . .

I was also following this XDA Forum and Yt link and it had these steps mentioned:

How to Downgrade Android Version in Samsung Devices if Device is in Higher Binery

How to Downgrade Android Version in Samsung Devices if Device is in Higher Binery * Your warranty is now void. * I am not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels. * You do it at your...

xdaforums.com
[Android Software Development] osm0sis:
Read the instructions and FAQ please. Sounds like you're trying to use the Windows package on Linux, or just cloned it from GitHub and expected it to work without any of the AIK packages' included binaries. 🤔
[Android Software Development] Ibrahim117:
I'm not on Linux, I'm on windows

(I'm the same person)
[Android Software Development] Ibrahim117:
And can you help me in this one
[Android Software Development] osm0sis:
Download the zip for Windows from the OP, and read the FAQ. #4 specifically. And follow what the error message told you to do.
[Android Software Development] Indashio:
Has anyone managed to extract files from system.img and product.img from Galaxy s24 ultra?
[Android Software Development] osm0sis:
This thread isn't about those kinds of images.
[Android Software Development] bakaekze:
I'm trying to repack a kernel on an unofficial lineage 17.1 build to remove lineage from the kernel name (I changed it to l1neage). Device: Sharp Aquos S2.

The issue is that boot.img-kernel seem to be extra compressed with gz.

So in order to hex edit, i have to do gunzip boot.img-kernel. After that I can't seem to boot my device anymore. No change if i gzip the kernel back again or leave it as is and just repack. Tried using --original and --origsize, didn't help. My phone can only boot to bootloader (fastboot) after flashing it.

Any help is appreciated.

1 is original

2 is mine after recompressing via gzip

Spoiler content hidden.
[Android Software Development] CXZa:
You did add trailing garbage back didn't you...?
[Android Software Development] bakaekze:
I most definitely did not! Thank you for the resposne!

I just used `gzip filename`. Is there any tool or script to add/keep trailing garbage that I might have missed?
[Android Software Development] CXZa:
a hex editor?
[Android Software Development] bakaekze:
What I did basically:

Unpack using AIK

Extract boot.img-kernel using gzip

Change some instances of lineage to l1neage using hex editor

gzip boot.img-kernel back and remove .gz from the filename

Repack using AIK with --original

I'm not sure what is there to be done with the trailing garbage... ):
[Android Software Development] CXZa:
tailed with some nuls + orig. garbage...

maybe works, maybe not...
[Android Software Development] bakaekze:
Thank you for trying. Unfortunately it only boots to "Download mode"
[Android Software Development] CXZa:
tailed with orig. garbage + some nuls added to the end (needed? IDK)...

in case garbage's start is just gzip's end.

probably does not work either... :LOL:
[Android Software Development] bakaekze:
You wouldn't believe it! It loaded!

But! It doesn't get MEETS_DEVICE_INTEGRITY

Could be checking something else (build number?)

Dam google.....

Spoiler content hidden.
[Android Software Development] CXZa:
Made one having nuls removed... but maybe it's better to leave it there...

Someone with more info might know more about those checks...
[Android Software Development] badabing2003:
You can't change some random instances, you have to change a specific one.

Give this one a try and see if it works.
[Android Software Development] bakaekze:
Thanks for reaching out! I didn't change random instances, they were specific. The problem was that trailing garbage. That phone seem to be sensitive to the boot image and only loads when compressed a certain way. I even tried not changing anything and repacking and it didn't help. @CXZa kernel loaded with the changed name, but it didn't help with getting play integrity sorted.
[Android Software Development] bakaekze:
@badabing2003 the one you provided does boot as well, but same issue. No MEETS_DEVICE_INTEGRITY

EDIT: Nevermind, got it to work with a different fingerprint!
[Android Software Development] mylove90:
Hello Sir,

How about Oracle cloud Ampere A1 ARM free tier servers ?

uname -s: Linux

uname -m: aarch64

neofetch:

.-/+oossssoo+/-. ubuntu@instance-20231104-0510
`:+ssssssssssssssssss+:` -----------------------------
-+ssssssssssssssssssyyssss+- OS: Ubuntu 22.04.3 LTS aarch64
.ossssssssssssssssssdMMMNysssso. Host: KVM Virtual Machine virt-4.2
/ssssssssssshdmmNNmmyNMMMMhssssss/ Kernel: 5.15.0-1049-oracle
+ssssssssshmydMMMMMMMNddddyssssssss+ Uptime: 29 days, 16 hours, 49 mins
/sssssssshNMMMyhhyyyyhmNMMMNhssssssss/ Packages: 955 (dpkg), 6 (snap)
.ssssssssdMMMNhsssssssssshNMMMdssssssss. Shell: bash 5.1.16
+sssshhhyNMMNyssssssssssssyNMMMysssssss+ Resolution: 1024x768
ossyNMMMNyMMhsssssssssssssshmmmhssssssso Terminal: /dev/pts/0
ossyNMMMNyMMhsssssssssssssshmmmhssssssso CPU: (4)
+sssshhhyNMMNyssssssssssssyNMMMysssssss+ GPU: 00:01.0 Red Hat, Inc. Virtio GPU
.ssssssssdMMMNhsssssssssshNMMMdssssssss. Memory: 339MiB / 23987MiB
/sssssssshNMMMyhhyyyyhdNMMMNhssssssss/
+sssssssssdmydMMMMMMMMddddyssssssss+
/ssssssssssshdmNNNNmyNMMMMhssssss/
.ossssssssssssssssssdMMMNysssso.
-+sssssssssssssssssyyyssss+-
`:+ssssssssssssssssss+:`
.-/+oossssoo+/-.
[Android Software Development] VámpírKecske:
Hi osm0sis! I downloaded the latest, but somehow it wont work. it creates 2 directory as it should but its empty (the split image durectory contains a .originalsize extension file). Tried run it as admin. The commandprompt dont even shows up. Do you have any suggestion? Or its not intented to unpack motorola files?

Edit: The windows version, and the phone is motorola edge 40
[Android Software Development] Belgrade.:
I have folowing file (recovery.img):

https://mega.nz/file/pDUUUZIa#gKyV53CFF5fRG187fhELUh4fsh6gsyQdubT_fdW56iI

I unpacked it and overwrote file ramdisk\prop.default with file (prop.default):

https://mega.nz/file/4WNWWTwA#7-BBSYeOqOClLWC6Ncf6ynhuAI5xX7uPWwd1KUeNAp8

Then after repacking recovery.img post above minor change instead of getting recovery.img with original file size of around 24MB, repacked IMG file is only around 16MB.

What am I doing wrong here? (For both unpacking/repacking I used AIK-Linux-v3.8-ALL.tar.gz)
[Android Software Development] osm0sis:
FAQ #3

FAQ #2
[Android Software Development] osm0sis:
Well well, it's been a very long while, (roughly the age of a toddler 😛)... let's do things a little differently this time so people can have something hopefully of use until I get all the features and platforms complete... 😉

Here is the first of likely a number of WIP AIK snapshots I'll do as things progress towards my release checklist. As it is a work in progress, expect some things could change before final, or possible regressions, but that I'm fairly happy with what I've got for the features implemented at this point. 🤠

It's arm64 AIK-mobile only for now, zipped directly off of the device I'm currently writing it on. The other prerequisite is that you know what you're doing enough to have installed AIK-mobile v3.8 already and can unzip my attached zip over top of it, into /data/local, and know how to help figure things out if something goes wrong in your testing. 🙌

AIK-mobile v3.9 WIP 20240416:

- grow ext4 ramdisk.img to 192 MB for unpacking larger ramdisks (AIK-mobile)

- add latest (1bbcd66) AOSP avbtool.py for AVBv2 signing support (QPython app install required on AIK-mobile)

- retain and allow modifying important AVBv2 hash footer argument values

- update loop mount logic to reduce errors (AIK-mobile)

- update busybox binary (1.36.1) with the latest patches and fixes from my repo (AIK-mobile)

- support detecting and adding any SEANDROIDENFORCE string before AVBv2 signing

Lots more to come! 😎
[Android Software Development] quartic polynomial:
stray from the subject，delete
[Android Software Development] osm0sis:
Start by being in the correct thread.
[Android Software Development] ogj22317:
2019 version (stock ROM) is unsupported due to the signature
[Android Software Development] ogj22317:
It does not work if you modify anything, even with an unlocked bootloader
[Android Software Development] D4V1D3_008:
I'm trying to use your tool to edit the twrp img, but even when I repack with --origsize, my phone gets stuck in fastboot.

This happens even if I flash the unmodified img after I unpack and repack it.

Could it be the AVBv2 signature fault? I see it getting detected during the unpacking but it does not seem to get added again while repacking.

I'm trying this on my Poco X3 Pro.

Thank you in advance.
[Android Software Development] osm0sis:
Correct.
[Android Software Development] D4V1D3_008:
So I need to sign it with the avbtool python script as you wrote in the FAQs?
[Android Software Development] osm0sis:
Most likely.
[Android Software Development] D4V1D3_008:
Finally managed to do it, now I can boot in a customized recovery.
[Android Software Development] MrMarkEdward:
TY so much worked awesome TY again
[Android Software Development] nk7:
You testing these on the Nexus 7? I might have to get a phone for testing this out. Sounds interesting