yashsingh1/xdaforums huggingface dataset:
[8525, TyTN, MDA Vario II, JasJam ROM Development] mrvanx:
Welcome to XDA-Developers.

Its not a silly question but there is ALOT of info on this in the various threads etc.

Internet Calling is the VoIP component in WM6, theres a BIG THREAD about how to work it in the general forum.
[8525, TyTN, MDA Vario II, JasJam ROM Development] hamoda_adola:
thnx for yu reply.but sorry again for my silly question :S . but it is free or it is with ratings. any links available ?
[8525, TyTN, MDA Vario II, JasJam ROM Development] mrvanx:
All info is in the thread dude.
[Note Edge Themes and Apps] deadlyheart4u:
I made a revamped App

Finally after 2 days of hardwork I managed to publish the new edition of wallpaper app and its online now as QHD Ultra Wallpaperz HD.

TRY it, its faster and better.

http://techenthu.com/qhd-ultra-wallpaper-hd-app-on-android/
[Note Edge Themes and Apps] DV8:
Getting 404 error on link.
[Note Edge Themes and Apps] droidnew:
404 error here as well
[Note Edge Themes and Apps] deadlyheart4u:
working now
[Note Edge Themes and Apps] parusia:
Still giving error 404.
[Note Edge Themes and Apps] micky387:
Thanks man
[Note Edge Themes and Apps] djsbad:
404 error

Sent from my SM-N915P using Xparent Green Tapatalk 2
[Note Edge Themes and Apps] micky387:
Not for me.. .
[Note Edge Themes and Apps] Martinjv71:
404 hear too bad
[Note Edge Themes and Apps] megatooth:
http://techenthu.com/note-4-edge-wallies-personal-collection/

This is the link you're looking for.

Thank you, deadlyheart4u.
[Note Edge Themes and Apps] deadlyheart4u:
if you people like my work, do press the thanks button
[Note Edge Themes and Apps] bluetooth101:
Not working
[Note Edge Themes and Apps] Cherub Belgium:
Well... maybe you could start with a working link... ;)...
[Note Edge Themes and Apps] deadlyheart4u:
sorry people the link was posted with some error, i fixed it and now its all working
[Note Edge Themes and Apps] Xhell:
Thanks. Linked working good and the app is nice.

Sent from hell
[Note Edge Themes and Apps] deadlyheart4u:
its for all so, share and share.
[Note Edge Themes and Apps] Bluecham:
I would like a preview of what it offers before having to download...
[Note Edge Themes and Apps] deadlyheart4u:
screenshots posted
[Note Edge Themes and Apps] deadlyheart4u:
I updated the app with many more wallpapers and all are high resolutions
[Note Edge Themes and Apps] deadlyheart4u:
Links Updated and more QHD Wallpapers Added
[Nexus 6 Accessories] rideascooter:
I'm looking for a vent clip (in car) with wireless charging. It seems the ones on the cheap market are too small or don't hold the N6 very well.

Just looking for low end unless I have to get the $40+ ones. Which is what I'm thinking is my path for now.
[Nexus 6 Accessories] psxindo:
http://www.amazon.com/gp/product/B00JS35ZKU/ref=od_aui_detailpages00?ie=UTF8&psc=1

I bought this for my N4 a couple of months ago.

It fits the N6 just fine. I never had problem with the N6.

The price has gone up by $5
[Nexus 6 Accessories] rideascooter:
Oddly, I bought that exact one on ebay! Edit: Link- eBay Found it on there for $20!

Good to hear that it works well.

Thanks for the reply!
[Samsung Galaxy Ace Plus S7500] QA Bot:
Q&A for Superuser.zip Installation aborted.

Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.

Before posting, please use the forum search and read through the discussion thread for Superuser.zip Installation aborted.. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.

Thanks for understanding and for helping to keep XDA neat and tidy! :)
[Samsung Galaxy Ace Plus S7500] Lihxor:
try to see this thread

http://xdaforums.com/showthread.php?t=2284737
[Android Software/Hacking General [Developers Only]] ShadowTehAmazing:
I made this video because it took me a long time to find the tool that can root this verson

This should work for 0.9.x

I really do hope it works for you guys

https://www.youtube.com/embed/BsR8Tp2wsvs
[XDA Assist] XDA Visitor:
i have gionee p3 mobile and i wants to upgrade its android jellybin 4.2.2 to 4.4 kitkat . how can i do this please help me .....
[Sprint HTC One (M7)] joposthauer:
Phone is s on hboot 1.6. Running cyanogen 12. I want to lock and go back to complete stock everything to get new lollipop update. Tried multiple ruus before after relocking and nothing finished. Too many errors. It is unlocked again just so i could at least boot the phone. Help is greatly appreciated.
[Android Q&A, Help & Troubleshooting] QA Bot:
[Q&A] [GUIDE] How to build CWM-based Recovery from source in Ubuntu 12.04 with CM-11

Q&A for [GUIDE] How to build CWM-based Recovery from source in Ubuntu 12.04 with CM-11.0

Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.

Before posting, please use the forum search and read through the discussion thread for [GUIDE] How to build CWM-based Recovery from source in Ubuntu 12.04 with CM-11.0. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.

Thanks for understanding and for helping to keep XDA neat and tidy! :)
[Android Q&A, Help & Troubleshooting] denizyildizi345:
My phone has 16mb recovery part but the recovery.img I made is 25 mb so I can't flash it :( In BoardConfig.mk, I can wrote at least 24.936.448 at the line of BOARD_RECOVERYIMAGE_SIZE to compile the recovery image. How can I solve this problem? Can I reduce the size of the .img file to 16 mb?
[Android Q&A, Help & Troubleshooting] Deleted member 5186178:
I don't understand how you ended up with such a big recovery... The biggest ramdisk I saw (in TWRP) is not more than 4-5 Mb. Do you have a kernel over 20Mb? It can't be, otherwise the stock recovery will be oversized too. Somewhere you made a mistake probably.

And to answer your question, no you can't reduce the size of recovery that big; if you have a kernel compressed in xz, you may try to compress the ramdisk in xz too, and the size will be smaller, but not enough... you need to downsize it with 9Mb, which is not possible.

So check again, to see if there isn't a mistake somewhere.
[Android Q&A, Help & Troubleshooting] denizyildizi345:
I took a screenshot of my CM11-0/out/target/product/msm8226/root folder which is 25 mb. There is a boot.img file. I think the problem is that file. I unpacked a few recovery.img files but none of them included that file. If problem is this, how can I remove that file from my ramdisk?

I removed that file and flashed new recovery.img but now my phone isn't booting in recovery mode.
[Android Q&A, Help & Troubleshooting] Deleted member 5186178:
No, for checking recovery root you need to look here: CM11-0/out/target/product/msm8226/recovery/root . But anyway that folder looks strange (I see a perl script there)....

Check my screenshot below.

And type a

make clobber

before stating a new build, or

make clean

between repetitive builds.
[Android Q&A, Help & Troubleshooting] george676:
im getting this error each time i try to compile:

make: *** No rule to make target `/etc/init.rc'

please any suggestions
[Android Q&A, Help & Troubleshooting] Deleted member 5186178:
You need to be more specific: what recovery you try to build, in what environment (if it's not cm-11), and post a link to your device folder tree. That error means that the compiler can't find an init.rc file to add in ramdisk.
[Android Q&A, Help & Troubleshooting] Tatsun0x0:
Compiler stops after a few segments

This is shown in my terminal:

cp: cannot stat ‘/home/paul/cm-10.2/out/target/product/Ultra/root/init.recovery.*.rc’: No such file or directory
make: [/home/paul/cm-10.2/out/target/product/Ultra/recovery/root.ts] Error 1 (ignored)
mkdir -p /home/paul/cm-10.2/out/target/product/Ultra/recovery/root/system/bin
cp -rf device/CherryMobile/Ultra/recovery/root /home/paul/cm-10.2/out/target/product/Ultra/recovery/
cp: omitting directory ‘device/CherryMobile/Ultra’
make: *** [/home/paul/cm-10.2/out/target/product/Ultra/recovery/root.ts] Error 1
paul@MS-7816-Mint ~/cm-10.2 $ make clobber

And you wrote about the problem:

During the build process you may encounter some errors or warnings.

*********************

Code:

cp: cannot stat `/home/carliv/CM11-0/out/target/product/P780/root/init.recovery.*.rc': No such file or directory
make: [/home/carliv/CM11-0/out/target/product/P780/recovery/root.ts] Error 1 (ignored)

This will not stop the build, and it appears if you don't use a init.recovery.{hardware}.rc file. Can be ignored, as the build process does.

Though in my terminal it just stopped at that part so I had to rename mine which was originally init.recovery.qcom.rc to init.recovery.*.rc

--edit--

And yet it still would not continue :(... Any ideas on how to fix this?

--edit # 2--

Here's the pastebin link just in case ->biQ7kjV8 add that to pastebin...(I can't post links)

--edit # 3--

I fixed it... Turns out that it was just a BoardConfig.mk parameter that I forgot to complete
[Android Q&A, Help & Troubleshooting] Tatsun0x0:
Calculate proper BoardConfig.mk partition sizes

I have this log:

----- Making recovery image ------
/home/paul/cm-10.2/out/target/product/Ultra/recovery.img maxsize=8380416 blocksize=135168 total=8409088 reserve=270336
error: /home/paul/cm-10.2/out/target/product/Ultra/recovery.img too large (8409088 > [8650752 - 270336])
make: *** [/home/paul/cm-10.2/out/target/product/Ultra/recovery.img] Error 1
make: *** Deleting file `/home/paul/cm-10.2/out/target/product/Ultra/recovery.img'

Meaning I have wrong sizes for the partitions so I need help on it...

When I ran the following:

cat /proc/mtd

cat /proc/emmc

they both return: No such file or directory...

Now If I run the command: cat /proc/partitions

it comes up with this:

As far as I know.... mmcblk1p1 is my external sd card which is about 32 GB...

My system image is about 1 GB and more(confirmed) when I used the dd command(to dump it) and is located at mmcblk0p16

Userdata reaches more than 4 GB as reported by the dd command(file size too large) and is located at mmbblk0p25

here(recovery.fstab):

/boot mtd /dev/block/mmcblk0p10

/cache yaffs2 /dev/block/mmcblk0p18

/data yaffs2 /dev/block/mmcblk0p25

/misc mtd /dev/block/mmcblk0p20

/recovery mtd /dev/block/mmcblk0p19

/system yaffs2 /dev/block/mmcblk0p16

-- edit --

I solved this already
[Android Q&A, Help & Troubleshooting] Eversmile23:
Help required for compiling CWM for android 4.4.2 version only?

I am on Ubuntu 14.0.4 and I am trying to build a CWM recovery for Celkon Q 5009android 4.4.2, Broadcom processor). I have set up build environment and currently working on syncing repo. I have heard that it takes too much time and disk space to complete this process. I am interested to know in the following particular scenario : want to build only CWM recovery from source for an android running on version 4.4.2. So do I have to download all repositories or is there any shortcut that would enable me to not download all, but a certain part that is required for android 4.4.2? If yes, how to go about it? please help.
[Android Q&A, Help & Troubleshooting] Eversmile23:
Please help. I do not undertstand why 'repo sync' always fails at a particular stage, though I have 30+ GB of disk space available in my working folder named 'cm12'. Following is the last screen message :

Fetching project platform/external/ant-glob

Fetching projects: 8% (40/495) Receiving objects: 86% (2389/2771), 26.68 MiBerror: RPC failed; result=56, HTTP code = 200iB | 124.00 KiB/s

fatal: The remote end hung up unexpectedly

fatal: early EOF

fatal: index-pack failed

remote: Sending approximately 1.94 GiB ...

remote: Counting objects: 85, done

remote: Finding sources: 100% (85/85)

error: RPC failed; result=56, HTTP code = 200iB | 88.00 KiB/s

fatal: The remote end hung up unexpectedly

Now should I run 'repo sync' again or should I use 'repo sync -j1' ?

fatal: early EOF

fatal: index-pack failed

error: Cannot fetch device/lge/mako-kernel

error: Exited sync due to fetch errors
[Android Q&A, Help & Troubleshooting] Black Manta:
Hey,

In which size are the values in BoardConfig.mk at BOARD_BOOTIMAGE_PARTITION_ZISE? bit?

And how I can convert blocks to this size because my lge only print out the partition sizes in blocks.

LG Noel
[Android Q&A, Help & Troubleshooting] Deleted member 5186178:
http://xdaforums.com/showpost.php?p=60297989&postcount=51

Somewhere around that post you will find your answer.
[Android Q&A, Help & Troubleshooting] 4javier:
Hi. Your guide is the most useful I found on the net. Much more than the official cyanogenmod wiki's porting one. Thanks a lot.

I'm trying to use it to build a cm 12.1 (lollipop) cwm on a mediatek device.

1) My stock rom (also Android 5.1) already ships a fstab.mt6795 file into the ramdisk. I moved it inside /recovery/root, and copied its content in /recovery/recovery.fstab

This is its content, should I make any change inside it?

# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK

/dev/block/platform/mtk-msdc.0/by-name/system /system ext4 ro wait
/dev/block/platform/mtk-msdc.0/by-name/userdata /data ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check,resize,encryptable=footer
/dev/block/platform/mtk-msdc.0/by-name/cache /cache ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check
/dev/block/platform/mtk-msdc.0/by-name/protect1 /protect_f ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check,autoformat
/dev/block/platform/mtk-msdc.0/by-name/protect2 /protect_s ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check,autoformat

#please add cip or persist on project fstab
#/dev/block/platform/mtk-msdc.0/by-name/persist /persist ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check,autoformat
#/dev/block/platform/mtk-msdc.0/by-name/custom /custom ext4 ro wait
/devices/mtk-msdc.0/11230000.MSDC0 auto vfat defaults voldmanaged=sdcard0:emmc@intsd,noemulatedsd
/devices/mtk-msdc.0/11240000.MSDC1 auto vfat defaults voldmanaged=sdcard1:auto
/devices/bus.2/11270000.USB3_XHCI auto vfat defaults voldmanaged=usbotg:auto
/dev/block/platform/mtk-msdc.0/by-name/frp /persistent emmc defaults

2) How can I find out which of the .rc files available in stock ramdisk include in my recovery, besides the renamed init.rc copied from /bootable/recovery/etc ?

3) My stock rom obviously already ships a init.mt6795.rc. Should I merge any of its lines to the one I copied from /bootable/recovery/etc in my /recovery folder?

Thanks in advance for your time and your efforts.
[Android Q&A, Help & Troubleshooting] Deleted member 5186178:
First let me ask you where did you find a cwm for lollipop to build it? I'm interested to see that.

Second in recovery fstab you may want to add emmc partitions like boot, recovery... Check my github and look at elephone p6000 device folder (it's close enough to understand). If internal sdcard is on data/media you don't have to add it at all in fstab (at least that was the rule for kitkat... again I need to see the source for that lollipop cwm to tell you exactly). In elephone device recovery fstab you can see that usb and external sdcard are defined as auto for type not vfat because it is better to let minivold manage that.

Normaly for cm12.1 ther is no need to copy any rc file in root, only the fstab. {hardware}, which you said you did.

Again I can tell more if I will see the source code for the recovery, and last thing my guide is quite old now but I'm glad you found it useful.
[Android Q&A, Help & Troubleshooting] 4javier:
Thanks for your quick reply. :)

I think I've not been so clear explaining what I'm doing: when I talk about "Lollipo CWM" I just mean that I'm working on 12.1 branch of cyanogenmod source tree, that as you know is based on the same sources of Lollipop, instead of the one the guide was originally aimed to.

1) I feel really dumb at this moment. I don't know exactly how many time I read that fstab file, and I never noticed that it lacks entries for partitions not managed by stock recovery. Sorry if I wasted your time with a stupid question.

2)For sdcards, then it's better to leave untouched the voldmanaged options, but change the filesystem type to auto?

3) I don't need to copy any other .rc file (init.mt6795.usb.rc, init.xlog.rc, etc...), nor to merge anything from init.mt6795.rc of the stock rom. Right?

Thanks again. :svetius:
[Android Q&A, Help & Troubleshooting] Deleted member 5186178:
I did understand it's cm12.1, but that was my question since there is no cwm for cm12.1 only cyanogenmod recovery which is different. At the moment I only recommend twrp for cm12.1+ and for that you have to use a different fstab, easy to find on github or here on xda in twrp threads.
[Android Q&A, Help & Troubleshooting] 4javier:
Then, if I'm not too much confused:

- since CM12, Clockworkmod isn't anymore included in its source tree

- if I don't set any RECOVERY_VARIANT it defaults to CyanogenMod Recovery, not CWM anymore

- the recovery.img I built is, at its best, a Cyanogenmod recovery

- the recovery.fstab I used (the one i posted before, but now with /boot, /recovery and /nvram entries added) is in version 2 format, that twrp doesn't understand. So I have to find out how to convert in the old fstab format.

Am I right?

Another question: I used the last version of your CarlivKitchen. That doesn't offer anymore the choice to re/pack for standard android or for mtk images, because it automatically detect the format. But when it repacks, it adds the mtk header if the original image had it? Or am I forced to use a custom boot image maker?
[Android Q&A, Help & Troubleshooting] Deleted member 5186178:
Yes for all and for twrp fstab I think you can study device folders from twrp github (few are mediatek).

My kitchen now detects if image has mtk header and will repack it the same way (it stores a variable in unpacked folder which will tell that it must add a mtk header).
[Android Q&A, Help & Troubleshooting] 4javier:
I decided to follow this guide to integrate the changes needed to build twrp instead of cwm: http://xdaforums.com/showthread.php?t=1943625

It doesn't cover all the preparation steps like yours do. Do you think there are changes to be made to make your guide suitable for cm12 and twrp, or I can follow it until the " Build a CWM-based Recovery " paragraph?
[Android Q&A, Help & Troubleshooting] :
That's a very good guide since it's written by the main developer of twrp. You can use the parts that suits you from both guides.
[Android Q&A, Help & Troubleshooting] 4javier:
Excuse me Carliv. If your tool detect an MTK recovery, and automatically re-add MTK header when repacking, how can it be used to make the img suitable for mkbootimg? In your guide you say to use ./unpack_MTK_img recovery.img to unpack the stock recovery, and ./repack_img recovery. But in your last version, the tool will automatically call ./repack_MTK_img recovery, because the original image was an MTK one.

I'm just curious. I think it worked for me, but I cannot understand why it didn't fail.

EDIT:

I think I found the answer by myself. The guy in this thread talk about different device but same board of mine.

http://xdaforums.com/showpost.php?p=63494216&postcount=39

EDIT2:

There's something not so clear. I found a tree for a device based on the same board MT6795, and in its BoardConfig it uses a custom image generator, that AFAIK should just add the mtk headers.

BOARD_MKBOOTIMG_ARGS := --base 0x40078000 --pagesize 2048 --kernel_offset 0x00008000 --ramdisk_offset 0x03f88000 --second_offset 0x00e88000 --tags_offset 0x0df88000 --board Bule
TARGET_PREBUILT_KERNEL := $(LOCAL_PATH)/prebuilt/kernel
BOARD_CUSTOM_BOOTIMG := true
# MKImage
TARGET_MKIMAGE := $(LOCAL_PATH)/mkimage
TARGET_USE_BUILT_BOOTIMAGE := true
[Android Q&A, Help & Troubleshooting] :
I don't really understand what you ask. If you want to unpack an image with mtk header and repack it without mtk header for using with unpackbootimg for making the device tree and you want to do it with my kitchen just delete the file boot.img-mtk or recovery.img-mtk from unpacked folder before repacking. The repacked image won't work in your phone if it was with mtk header but will work with cyanogenmod unpackbootimg.

All the other things you say I can't understand, but if you try to understand the mtk images building process just search the xda mtk threads, even my old posts from zopo zp995 threads or github accounts and you will understand. The information it is already there.
[Android Q&A, Help & Troubleshooting] 4javier:
Your answer is exactly what I was asking for. The problem is that your guide isn't updated to your tool's last version, and this can confuse people. :)

In the rest of my post I'm trying to understand if my stock rom uses mtk header or not. CarlivKitchen seems to not detect any mtk header, because it doesn't create any recovery.img-mtk file in "recovery" directory.

This fact seems to be confirmed by the post I linked previously, where an user said that a rom for the same board doesn't have any mtk header.

The tree for redmi note (based on the same board) instead, uses a custom mkimage, which means that its rom needs the mtk header.

What I'm asking is: can your tool be wrong detecting the absence of mtk header? Is there a way I can check by myself?
[Android Q&A, Help & Troubleshooting] DeadSquirrel01:
Hey, i'm trying to build cwm-based recovery, but when I type lunch full_a5ultexx-eng I get : "trying dependencies only mode on a non-existing device tree?" and it stops. I've also tried with brunch command but when I flash it, the recovery flashes in download mode partition (see attached photo). My recovery.fstab is this:

# mount point	fstype	device	[device2] fstype2

/boot	emmc	/dev/block/bootdevice/by-name/boot
/system	ext4	/dev/block/bootdevice/by-name/system
/cache	ext4	/dev/block/bootdevice/by-name/cache
/data	ext4	/dev/block/bootdevice/by-name/userdata	length=-16384
/sdcard	vfat	/dev/block/mmcblk1p1

What do you think about this problem?

PS: My device is a samsung galaxy A5 and I'm on kali (based on debian)

PHOTO
[Android Q&A, Help & Troubleshooting] :
Need more info: a link to your device tree, what recovery do you try to build (link to source) and in what environment (cm-10.1, 11, 12 or other) do you use. Any of these can cause the issue.
[Android Q&A, Help & Troubleshooting] DeadSquirrel01:
Ok, I've tried building CWM, CTR, and Philz, and i get the same error, so I think it isn't a recovery problem. Device tree is unofficial and it's the following https://github.com/mygalaxya/android_device_samsung_a5ultexx, I've tried this https://github.com/TheWhisp/android_device_samsung_a5ultexx, too and I'm compiling on cm-10 sources