yashsingh1/xdaforums huggingface dataset:
[Sprint Samsung Galaxy S III] dante32278:
Anyone have the apk? This is all I get for 3 minutes now.
[Sprint Samsung Galaxy S III] The Root:
Ewwwww!!!!!!
[Sprint Samsung Galaxy S III] m20120:
Not too much excitement for the themes here either.
[Android Q&A, Help & Troubleshooting] nagar.xda:
Hello Guys,

Really I need to install Arabic in Android Emulator Bluestacks, I tried to install with several ways but no vain.

Used a way to update firmware.jar and add fonts but not sucess

tried to replace fonts but no vain also, still the same proplem, separated reversed fonts

so please can any one help me to read and write Arabic in Bluestacks last version.

Thanks For help ​
[Android Q&A, Help & Troubleshooting] nagar.xda:
No one ?

No one know how ? :(
[Android Q&A, Help & Troubleshooting] nagar.xda:
Any Suggestion

No Suggestion ???
[Android Q&A, Help & Troubleshooting] mohazia:
I have excellent experience in adding Arabic. But I have no experience in emulator.

just explain to me more what do you have, your frameware, your ROM, your android version. I provide all what I have.

Admins, move this threat to Q & A
[Android Q&A, Help & Troubleshooting] nagar.xda:
Bluestacks Android Emulator

Thanks Man for concern, Bluestacks running with android version Gingerbread 2.3.4, but i don't know how to get firmware details.

I extracted system.img and mount in linux but once change permission stop working,

Already rooted with super user, but can not mount system read and write, permission denied.

Thanks mate
[Android Q&A, Help & Troubleshooting] mohazia:
I download it now, and I'll reply soon in sha' allah
[Android Q&A, Help & Troubleshooting] nagar.xda:
Thanks Man, I'm Replying now from Bluestaks to see automatic device signature, waiting yours, I can upload rooted system.img for you
[Android Q&A, Help & Troubleshooting] mohazia:
Nothings work, file libwebcore.so compiled into amr processor, which is seem to beyond my knowledge. Sorry, dear.

But I read that they will isue ICS edition
[Galaxy Note II Q&A, Help & Troubleshooting] peter7769:
Hi All

Can anyone tell me where the aerial for the NFC is located, i thought it was on the back of the battery cover but ive seen some sites saying that its located on battery?

i want to get a second battery and im concered it might not have the aerial on it :(

Thanks

Pete
[Galaxy Note II Q&A, Help & Troubleshooting] prinzhernan:
Hello Pete. It is in the battery cover, not the battery.
[Galaxy Note II Q&A, Help & Troubleshooting] peter7769:
Thanks, thats just what I wanted to hear.
[Samsung Galaxy Nexus] milerx:
Hi,

I just update my galaxy nexus via OTA to android 4.1.2 and i want to check the name of some song, after looking for the Song Search Widget i haven't found, please help me or let me know if in your android 4.1.2 you have this widget, i use it a lot! :good: :fingers-crossed:

Note: Screenshots taken using android 4.1.1
[Samsung Galaxy Nexus] bozzykid:
Are you located outside the US? AFAIK, you are required to be in the US for the widget to be available.
[Samsung Galaxy Nexus] milerx:
Yeah, i'm in Colombia :(

But it was working until OTA to android 4.1.2, i guess i should use Shazam or SoundHound

Thanks for the replay.
[Samsung Galaxy Nexus] jlv3:
Hmm - I have a Sprint GNex using OTA 4.1.1 (thus, in the US), and I don't have the song search widget.

---------- Post added at 01:19 PM ---------- Previous post was at 12:28 PM ----------

I installed the transparent widget apk from [APP][4.0+] Google Ears/Sound Search (From Jelly Bean) and now I have the Sound Search widget.
[Samsung Galaxy Nexus] milerx:
HI, i just try the normal and the transparent widget and both get me errors while installing, it says that there's a current version of the app and it's signed so there's a error with the signature.
[Samsung Galaxy Nexus] Zepius:
i am on takju 4.1.2 and i still have sound search.
[Samsung Galaxy Nexus] milerx:
Hi, i'm on yakju (JZO54K) w/ 4.1.2
[Samsung Galaxy Nexus] explo_z:
I've gn GSM and i've the same pb ! Someone has solution ?
[Samsung Galaxy Nexus] efrant:
Not sure about yakju, but on takju, if you are not in the U.S., there are two apps and one widget that are disabled (although they are still installed):

Wallet

Magazines

Ears widget

You need to enable them to use them (and you have to enable them on every boot). You can use Package Enabler, or ROM Toolbox or Titanium Backup, or a few other apps to enable them.
[Samsung Galaxy Nexus] milerx:
Thanks a Lot, i Just check with Package Enabler and i have disabled Wallet, Magazines, Videos and Ears widget for Colombia (yakju on 4.1.2).
[Samsung Galaxy Nexus] milerx:
Hi, just try to activate it, but if you are running 4.1.2 and you are not inside the US, you have this disabled..
[Click General] pepingrilloxxx:
ADVISE: sorry for my horrible english.

Hello:

first of all, let me say that I searched for information before asking, but I have not get any light on this subject. I think a big problem is that sections of each type of smartphone (Galaxy, Tattoo, Nexus, Xperia, etc.) contain answers for that particular model of phone, but no general answers, so it is often difficult to clarify what works and what not for our device.

I would like to know different methods for passing applications (and their respective dalvik-cache, data, libraries, etc.) to SD. So far I've been using Link2SD and worked well, but because of it does not link the application data, I ended up staying out of space on the internal memory (some applications do not know what the **** they do but generate data of 19 MB, or as Facebook, without having used it, about 9 MB of data).

I've heard of different scripts like S2E, amarullz, int2ext, etc. but I have no idea how they work, if they serve to our Tattoo, disadvantages and problems they create, etc.

Thank you very much in advance and await your responses. greetings
[Click General] hackeronte:
Been using link2SD for a while and I think that song2even is better... since it can move data as well.

On the other hand it requires cyanogen... but it shouldn't be a big deal: )

---------- Post added at 12:03 AM ---------- Previous post was at 12:02 AM ----------

Stupid prediction... I meant s2e of course
[Android Software Development] Dees_Troy:
So, now, hopefully you've compiled TWRP for your device and gotten it working. Now, you'd like to know how to get TWRP officially supported for your device so that it can be installed automatically with the TWRP app. In order for us to add "official support" for your device we'll need the following:

1) Device configuration files to compile TWRP from source for your device. This means that you cannot have repacked a recovery.img by hand to get it working. We need to be able to compile it from source so that we can easily release future updates.

2) We'll build a copy of TWRP and send it to you for validation. Once you've validated that we can build a working image for your device, we'll add it to the official TWRP app.

Note that we won't take credit for your port. You'll still get to post it on XDA to collect all the credit that goes with releasing something new for your device along with having your name listed on our website as the maintainer for the device. Also note that it's not always possible to provide automated installs for all devices.

You can now boot TWRP in an emulator. If you're trying to help develop TWRP, this can be a huge help as you don't have to risk your device and you can do everything directly on your computer.

Download this set of device configuration files.

Compile a recoveryimage using those device files. In the Android SDK, click on Tools -> Manage AVDs. Click New. Set it up as the following:

AVD Name: TWRP

Device: Galaxy Nexus

Target: ICS or newer though anything will probably work here

CPU: ARM (armeabi-v7a)

Check the box for hardware keyboard (your computer's keyboard will work in TWRP)

Up to you if you want to have the skin with controls present

Front Camera: None

Back Camera: None

RAM: 1024 VM Heap: 64

Internal Storage: 200

SD Card: Size: 500 MiB

Then click OK.

Once you have your AVD and your recoveryimage, you can boot TWRP in the emulator by browsing to your android-sdk/tools folder and run this command:

./emulator -avd TWRP -ramdisk CMFOLDER/out/target/product/twrp/ramdisk-recovery.img

Note that ADB doesn't work right away. About 10 to 15 seconds after TWRP finishes booting, ADB will come online. We start ADB via init.rc so even if TWRP fails to boot due to some kind of code error that you may have made, ADB should still work. Enjoy!
[Android Software Development] ViViDboarder:
Beep boop zee doop
[Android Software Development] sgt. meow:
I know I've PM'ed you but I would like to ask you again. What should I do after compiling the TWRP recovery binary? What files have to be copied and where? I'm trying to integrate it with an ICS kernel.
[Android Software Development] mfsr98:
I don't get this part. What is lunch supposed to be? is it supposed to be a individual command for a device or can I do "lunch full_tenderloin-eng" for all devices? Because I am building for a device that doesn't run Android natively (at least out of-the-box) so cyanogenmod doesn't support it on any way...

Also, can I use this for resistive screens? Just to make sure.

Thanks for the guide, I have been looking for this for a long time :D
[Android Software Development] manuel100:
thanks for the guide, well structured and not so complicated

i have only a question: i'm trying to build it for galaxy 5, the problem is that the resolution is 320x240, so can you tip me on modify the sources? (i've done this some days ago, but images were too large)
[Android Software Development] mg2195:
Set the device resolution to 320x240...I'm pretty sure they have support for that resolution...and if they don't then you can copy one of there's except resize it all to 320x240

Edit-they only have 320x480 https://github.com/TeamWin/Team-Win-Recovery-Project/

My question: I built twrp from source a while ago using smasher's Samsung inject twrp zip...that worked fine for a while...but recently we switched to mtd format so that inject twrp zip doesn't work...neither does the inhect twrp button within twrp anymore...I've seen that the galaxy s has the same problem as well...just wondering if you know of a work around...
[Android Software Development] manuel100:
thanks for respond, however i've tried resizing images to 320x240 but i don't know what should be the size of bottoms, because they are alway out-of-screen

what is smasher's Samsung inject twrp zip? but i think that the recovery doesn't work because you have to built it with mtd support (for ex. on madteam they are trying to build a mtd kernel, but for install that testing rom they built a special cwm with mtd support)
[Android Software Development] mg2195:
Smashers inject twrp zip is a tool for Samsung devices that let's you get the recovery without flashing the whole kernel. You basically put the ramdisk-recovery.img in the zip and then flash. During the flash process it pulls the boot.img, replaces the current ramdisk-recovery.img with the new one that contains twrp. It then deletes the old boot.img and flashes the new one...not affecting the actual kernel...

The recovery itself has mtd support...I can use it if I flash the whole boot.img, but I don't want to release the recovery within a whole kernel...because then I have to keep it up to date with both twrp and kernel sources, not to mention the different kernels available for my device....I can't make a recovery for each kernel...don't have the time for that...that's where the inject came in handy....the user could use any kernel he wanted while still using twrp

Recovery logs say it fails to find the ramdisk inside the boot.img and then in parenthesis something about may not be using gzip compression...which it is....

---------- Post added at 07:21 AM ---------- Previous post was at 07:19 AM ----------

Deestroy did this same tutorial on rootzwiki...if you look at the second post you'll see info about the smasher inject twrp I was referring to...http://rootzwiki.com/index.php?/topic/23903-How-to-Compile-TWRP-from-Source
[Android Software Development] mfsr98:
can I get help here please? :)
[Android Software Development] mg2195:
Its a single command...it opens up the menu for devices...just type lunch into the terminal and hit enter...you'll see what I mean. You will probably have to add your device to the menu by creating a vendorsetup.sh in your device repo if it doesn't already exist....
[Android Software Development] mfsr98:
Thank you for the quick answer. Yes, I already have vendorsetup.sh on the boot.img. Sorry for the noob question :D
[Android Software Development] Devarishi:
What about for android beginners???
[Android Software Development] Dees_Troy:
There's only so much that you can dumb it down and simplify it. There's lots of other guides out there for getting started. Compiling a recovery is not a super simple task that anyone and everyone can do and there's plenty of potential pitfalls including the possibility of bricking your device. If none or very little of this guide makes sense, then you might see if a developer for your device is interested in working on it instead.
[Android Software Development] azoller1:
how would you compile this for a device without an official cm9 build?
[Android Software Development] Hikari:
Well, you don't need official cm9 if you can find any working device tree for you phone you are good to go.. For lg spectrum 4g, this could be useful.
[Android Software Development] ktempleton:
Hey guys I'm trying to compile this for my phone the problem I'm running into is I need the root.ts I've searched and it doesn't come up with anything any help would be appreciated thanks
[Android Software Development] gls9:
I have a mtk6577 device which is not in de device tree of CM9.

I can compile CWM for my device with CM9. Because I was only making recovery, there was no need for setting up boardconfig.

In this guide there is a part starting with TARGET_RECOVERY_INITRC which is not there in my boardconfig.

Also is stated:

"Your board config also needs to include architecture and platform settings. Usually these are already included if you're using device configs that someone else created, but if you created your own, you may need to add them. Without them, recovery will often seg fault during startup and you'll just see the teamwin curtain flash on the screen over and over."

Does this mean that I cannot build TWRP without it, even I can build CWM ?
[Android Software Development] Dees_Troy:
Look for another mtk6577 device that has CM & copy the arch flags from it.
[Android Software Development] Fr3ddY303:
Thanks for your post Nice work...

I have install TWRP on my Huawei Y300-0151 but the touch screen won't work after the flashing.Tried two versions v2.5.0.1 and v2.6.0.0 both no touch working...
[Android Software Development] aidfarh:
I think TWRP is not yet compilable against cm-10.2 branch.
[Android Software Development] m4570d0n:
Ahh, okay. After I ran into that error, I decided to just run make recoveryimage instead of trying to build TWRP while doing a full ROM build, and that actually completed. However, when I flashed it and rebooted into TWRP, I could not access any partitions. When I clicked on Mounts it showed a blank list. Not only was there no internal or external SD visible, but also no /system /data, /cache, etc. I suppose it's possible it could be an issue with my fstab.qcom, but I'm not sure what would be wrong with it. I didn't think any changes to it were necessary from what's in the msm8660-common repo in CM:

https://github.com/CyanogenMod/andr...60-common/blob/cm-10.2/rootdir/etc/fstab.qcom

I looked at the skyrocket device repo on TWRP's github, and it hasn't been updated since ICS. Since then, a lot of the configs defined there have been consolidated into celox-common, msm8660-common, and qcom-common. The skyrocket and hercules both inherit the configs, make files, etc. from those three device trees and between the all of them, nearly all of the configs added in TWRP's skyrocket repo are already there except for these (which I did add):

BOARD_HAS_NO_REAL_SDCARD := true
DEVICE_RESOLUTION := 480x800
TW_NO_REBOOT_BOOTLOADER := true
TW_INTERNAL_STORAGE_PATH := "/sdcard"
TW_INTERNAL_STORAGE_MOUNT_POINT := "sdcard"
TW_EXTERNAL_STORAGE_PATH := "/external_sdcard"
TW_EXTERNAL_STORAGE_MOUNT_POINT := "external_sdcard"
TW_INCLUDE_CRYPTO := true
TW_CRYPTO_FS_TYPE := "ext4"
TW_CRYPTO_REAL_BLKDEV := "/dev/block/mmcblk0p25"
TW_CRYPTO_MNT_POINT := "/data"
TW_CRYPTO_FS_OPTIONS := "noauto_da_alloc"
TW_CRYPTO_FS_FLAGS := "0x00000006"
TW_CRYPTO_KEY_LOC := "/efs/metadata"

The only thing that still has me a little confused though is the mount points as this changed from ICS to JB. The actual mount points for the SD cards are /storage/sdcard0 and /storage/sdcard1. Then there's a symlink for sdcard0 at /sdcard and for sdcard1 at /external_sdcard. I'm not sure if that makes a difference, but either way, it wouldn't explain why the recovery image I made couldn't see any part of the file system or any partition.
[Android Software Development] ktempleton:
did you figure this one out ive got the same thing going on
[Android Software Development] Ryuinferno:
That is because the new CWM (in CM10.2) utilises fstab v2, unified fstab for both system and recovery, but TWRP is still using fstab v1, the old version...
[Android Software Development] Perseus:
So does that mean if I try to compile TWRP for a ICS or JB Device, it won't see the file system ?
[Android Software Development] Ryuinferno:
If you build it against the CM10.2 build system, I am afraid not except if you revert to the older fstab version...
[Android Software Development] Perseus:
Oh ok. I see. Well I am building for a TV Stick based on AMLOGIC A9 chipset. (Link in Signature) To my knowledge, no one has compiled CM 10.2 for this. So the only FSTAB I will need to tackle are the AMLOGIC ones. So I shouldn't run into this bug. am I right ?
[Android Software Development] Ryuinferno:
No idea...you will have to experiment...it depends on your device tree, whether which fstab version is used...
[Android Software Development] Dees_Troy:
Personally I don't think you should leave recovery building up to an automated builder. I have seen many builds of CWM made with the builder that were horribly broken. It's a nice thought, but I'd rather make a higher quality product that actually works and works well even if it requires a developer than have derps trying to publish automatically built images that don't work.

Some of the Huawei devices needed an updated kernel to fix touch because Huawei is using 2 or 3 different digitizers in their products.

For CM10.2 you will need to add another flag: HAVE_SELINUX := true

See next comment.

AOSP recovery switched to using fs_mgr to handle a lot of the partition management (mounting, and I think wiping). The source code for this it outside of bootable/recovery. TWRP already includes its own advanced partition manager that we feel works even better. The biggest problem with "fstab v2" as you call it is that the same fstab file is shared between Android and recovery. Because of some of the partition manager features that TWRP has, we can't share fstab files with Android. In our latest source, TWRP will check for the existence of /etc/twrp.fstab and use this instead of /etc/recovery.fstab if it's present. You can create a twrp.fstab file and then use PRODUCT_COPY_FILES += device/oem/codename/twrp.fstab:recovery/root/etc/twrp.fstab to get the twrp.fstab into the recovery ramdisk. Using this method will allow you to retain the regular fstab file for building CWM and for building full ROMs for Android itself.

I'll be updating the documentation here next week to document both this twrp.fstab and some of the "flags" that you can set in the twrp.fstab

One of the problems that TWRP currently has is there is no way to use it in a non-touch setup like a TV stick. I plan to eventually update TWRP sources to work on devices such as TV sticks, but it hasn't been a priority yet. Soon, I hope.
[Android Software Development] Perseus:
Oh! Thanks for letting me know. The TV Stick comes with a touchpad. Well, here's the thing when I boot ICS, I typically get a Cursor like Windoz. I use the trackpad to manipulate the Cursor and click on the icons like windoz. I thought that same process would work for the Touch Recovery.

Am I being too hopeful ?
[Android Software Development] Dees_Troy:
There's currently no mouse support in recovery. You are welcome to work on adding it of course.
[Android Software Development] Perseus:
Ah Well. As I suspected. I will try.
[Android Software Development] iurnait:
So i got TWRP to boot on my Galaxy Player 5, but something is weird with the fstab and nothing get mounted.

error:

E:Invalid block device on '/dev/block/mmcblk0p11', 'emmc', 35

E:Invalid block device on '/dev/block/mmcblk0p12', 'emmc', 38

E:Invalid block device on '/dev/block/mmcblk0p14', 'ext4', 35

and that error happens to all the partitions. I have tried with a unified fstab and with a a twrp.fstab
[Android Software Development] jagdeepmarahar:
Can somebody please make a twrp recovery my device i have xolo q700 quard core

Here is the stock recovery of my device

http://www.4shared.com/file/K2KmyQQS/recovery.html
[Android Software Development] m4570d0n:
Do I smell TWRP 2.7? :D

Just ran a build with the twrp2.7 branch and it looks to be working great so far. It required a one line edit to /system/core/charger/charger.c to revert a workaround commit for gr_text, that is not needed anymore. But other than that, it build without error and after flashing it on my phone it seems to be working well.
[Android Software Development] aidfarh:
Share your device config and maybe we can see what's wrong.
[Android Software Development] :
Is there a way to sync only recovery code not whole device. Whole source is 8+ GB. It would take days to complete sync on my connection
[Android Software Development] m4570d0n:
Nope. You need the code in the rest of those repos to build the recovery image. It doesn't take that long to sync, though. If it literally would take you days to download that, perhaps you should consider upgrading from from your Intel 486/66 and your dial-up modem. :p
[Android Software Development] Pavlex4:
I cloned it to cm 11: https://postimg.org/image/et5gns713/
[Android Software Development] MSF Jarvis:
Go visit your Mom and Dad, tell them you're sorry for all the times you've accidentally been bad to them, then follow these steps to start compiling the recovery :

1) move to your root dir, the place where the output of 'ls' includes folders named build, vendor, bootable and a few more.

2) type this : 'mkdir -p .repo/local_manifests/ && cd .repo/local_manifests/'

3) and then this : 'git clone https://github.com/iBullRay/manifest_s3ve3g'

4) and finally 'cd ../../ && repo sync --no-tags -c --no-repo-verify --force-sync -f'

Then you should have all the sources and you can follow the guide to compile the recovery now :)
[Android Software Development] Pavlex4:
In this last command what to cd? cd ../../ && repo sync --no-tags -c --no-repo-verify --force-sync -f'
[Android Software Development] MSF Jarvis:
cd ../../ will go two directory levels back, in your case, the folder where you have sources synced
[Android Software Development] Muhammad Ashraf:
Please how can I decompile recovery image to modify it??

i have sony xperia z3 dual, there is a pre-built recovery image for z3 so can I modify it to become compatible with my phone