yashsingh1/xdaforums huggingface dataset:
[General Monetization] AGGevorgyan:
Hi, I am interested have anyone tried such deals? Is there any experienced users/developers?

The point is, that I can't register merchant account from my country and it means that I can't sell anything in google play. PayPal can't receive money in my country also. So I am currently using admob in my application which gives me less than 1$ for month :D

Many users writed in their reviews, that they want to donate money and support me, but there is no easy ways for that. For example many developers using strategy of selling "donated" apps on google play. So I think, that someone can register merchant account in supported country with his address and credit card, then attach it to my developer account. If there will be some money, then for example 10% of revenue will keep that user, and 90% will send to me via bank transfer for example.

Is there any experience related to this?

And have anyone tried to attach other user's merchant account to his own developer account?

Also we can create some community for this with users/developers from supported countries and developers from unsupported countries.
[General Monetization] danialgoodwin:
Interesting. I'm sure this would work if you could find the right person to work with. Though, have you tried using a proxy to create a developer account? (So, that Google servers would think you were in a different country).

You say PayPal can't receive money in your country, but I believe AdMob can deposit funds directly to a bank account (this is how I have it set up). Or, there are many other ad networks out there with possibly even more payment options.

I have a few developer accounts for when I was working at different places. And, as an experiment, I was able to create one of them with a Visa gift card to pay the $25 fee. The merchant account is still tied to the developer account via the email address used, but in the merchant account settings it is possible to add account access and change bank information.
[General Monetization] BradleyLewis:
Well, I think Payscout.com is the best alternative payment gateway for your business. They offer free account setup services to merchant.
[Sony Xperia S, Acro S, Ion] Karolinho:
http://www.ebay.co.uk/itm/NEW-DISPL...lePhonesCasesPouches&var=&hash=item56593f1706

http://www.ebay.co.uk/itm/5g-Disple...UK_Mobiles_Accessories_RL&hash=item58a398bf19

is it working?
[Sony Xperia S, Acro S, Ion] neoxx3m:
I used it to clean camera lens on xperia ion and it worked great. Its good for small scratches but dont expect miracles. :)
[Sony Xperia S, Acro S, Ion] apurba_ron:
It works for me

Thank you
[Sony Xperia S, Acro S, Ion] imm1304:
yup, this worked for me. Thanks
[Galaxy Grand Duos i9082 Q&A, Help & Troubleshootin] Awesome_Star:
hi there!! can anybody please suggest me some nice custom roms for gaming on my galaxy grand i19082 4.2.2...i am tired of gennxt rom cuz it's lagging a lot and i want a nice custom gaming rom ( FOR REAL HD GAMING) which has a unique and an awesome graphical interface....

thanks!
[Galaxy Grand Duos i9082 Q&A, Help & Troubleshootin] Awesome_Star:
and yes i want a rom which supports dual sim also...and which has less bugs.
[Galaxy S 4 Q&A, Help & Troubleshooting] bunleab:
Dear all members of xda,

I want to ask something about Samsung Galaxy S4 phone.

Phone model: Galaxy S4 GT-I9500

Firmware: Android 4.2.2

Baseband version: I9500XXUAMDK

Build number: JDQ39 . I9500XXUAMDK

AP: I9500XXUAMDK

CP: I9500XXUAMDK

CSC: I9500JVAMDK

Can you give me the link to download this original firmware?
[Galaxy S 4 Q&A, Help & Troubleshooting] coolsandie:
Download from SamMobile. You may need to login there to see the download links to firmwares.
[Galaxy Note II Q&A, Help & Troubleshooting] gexsamir:
The lower the voltage, save battery?
[Galaxy Note II Q&A, Help & Troubleshooting] tweeny80:
Yes, that is the usual motivation. It is similar to driving a car low on petrol...you ask yourself "how low can it go before I run into problems...."

Some kernel-tweaking combos I know of are Perseus & Adam = STweaks / Saber & others = Trickster / Devil kernel and Devil app
[Galaxy Note II Q&A, Help & Troubleshooting] gexsamir:
Oh. Another question. In my GPU, 533mhz is 1100. The 640mhz is 1075. So its better if i use 640mhz?
[Galaxy S 4 Q&A, Help & Troubleshooting] ofir91:
How can I find which carrier my Samsung Galaxy S4 GT-I9500 is locked to?

I want to unlock it, but I need to know first the network my phone is locked to.

thx!
[Galaxy S 4 Q&A, Help & Troubleshooting] gee2012:
How about the carrier where the phone came from or where you have your contract?
[Galaxy S 4 Q&A, Help & Troubleshooting] parkerr42:
Last time I check this site give phone carrier network, then base on it you can guess lock status: Check samsung carrier
[JAM, MDA Compact, S100 Software Upgrading] kentian:
i have bought a german version black xda mini at Hong Kong Mongkok, the machine is flashed with a Traditional Chinese version - thanks to the shop it's the latest, but I face some problem that I need the use the IME of Hanyupinyin and that's why I need to use the Simplified Chinese version.

May I ask if someone can help refer a latest Simplified Chinese ROM, and together with some instructions...

Many Thanks.
[JAM, MDA Compact, S100 Software Upgrading] denier:
JUST CONTACT ME

QQ:12325737
[JAM, MDA Compact, S100 Software Upgrading] mmgirlmm:
HI Can u upload the CHS rom to the ftp server, thanks
[JAM, MDA Compact, S100 Software Upgrading] denier:
sorry, i don't know any about ftp info.
[JAM, MDA Compact, S100 Software Upgrading] jackleung:
Why don't you guys do a search on the old posts before posting a new request? Latest rom are available in the FTP, and instructions could be found in the forum very easily.

Here are the locations U should look for before requesting an "existing" rom (user/pass: xda/xda)

ftp://xdaforums.com/Magician/

ftp://xdaforums.com/Uploads/Magician/
[Galaxy Ace S5830i Q&A, Help & Troubleshooting] gal357:
Hello everyone. I am sorry if there was a thread like this before, as I haven't found one.

:laugh:

And please excuse me for any mistakes I make, as I just registered.

So, I have a problem with my Galaxy Ace S5830. The touchscreen doesn't work properly as it should. An example of this is I try to select an icon or anything for that matter (ie. settings) and I have to like massage the icon for the touchscreen to detect the touch. All the physical keys work fine.

I have tried absolutely everything I can imagine, rooting, flashing official firmware, flashing cm7, different kernel. I'm now currently running CM7 with CWM. I really have no idea what to do from here on, as my phone is now basically useless.:crying:

Thanks in advance!

Gal
[Galaxy Ace S5830i Q&A, Help & Troubleshooting] Cakawuete:
Have you a s5830 or a s5830i ?

It seems to be a hardware problem, cant be fixed with root or rom.

You should try to send it back to samsung.

Sorry :(
[Galaxy Ace S5830i Q&A, Help & Troubleshooting] gal357:
It's a GT-s5830, it's not an i version. I would take it back to samsung, if it still had a warranty, and if it would be free lol. I'm just really confused, because sometimes it works normaly for like 2 seconds, then it's back to massaging it.... I really don't know what to do, in the worst case scenario I'll just give it to the local phone fixer here in my place and hope he won't rip me off for more then what the phone's worth (I got the phone for free, it's pretty beat up at the corners, but otherwise okay)
[Galaxy Ace S5830i Q&A, Help & Troubleshooting] Cakawuete:
You have posted in ace i section ;)

May be you could try to ask for this in the good section.
[Galaxy Ace S5830i Q&A, Help & Troubleshooting] gal357:
Oh, I'm sorry for that, I'll make a new thread in the S5830 section.
[Galaxy Ace S5830i Q&A, Help & Troubleshooting] gal357:
Link to new thread.

http://xdaforums.com/showthread.php?p=44907094#post44907094
[Galaxy Ace S5830i Q&A, Help & Troubleshooting] Cakawuete:
Good luck ! I hope you will solve it.
[Galaxy S II Q&A, Help & Troubleshooting] d4rkpulse:
With the update to 4.1.2, it seems that the Australian version has the bottom icons locked. You can't change them. I've researched this and its only in Australia.... I was pretty pissed off with this, but I thought I could get used to it. Well, I can't.

So being the noob that I am, I thought simply rooting the device would allow me to solve this issue, but it doesn't seem to be that simple.

What I want to do with this phone is to unlock the bottom icons, and get rid of all carrier related stuff (boot animations, apps, etc.). Ideally I want to run pure android 4.1.2, as I'm not a fan of touchwiz, but I tried looking and I couldn't find anything, which is probably down to me being a noob. I wouldn't have a clue how to install it properly either.

So it's a Galaxy S2 I900T

The phone is on Telstra

It has been rooted

It's running stock 4.1.2

If there is anymore info you need to know in order to help me, just let me know and I'll add it.

Thanks in advance! :D
[Galaxy S II Q&A, Help & Troubleshooting] Hopper8:
Well...... You could just run a custom launcher. Search for Nova launcher on the play store. It's the one I use, it's customisable to just about whatever you want.

If you're rooted and do actually want to run stock android instead of just changing the launcher, then look for the index of ROMs in the s2 section. I think GaboWinter is the OP. Look under the AOSP section in there for the stock android ones.

Quick tip, if you do flash a rom you'll have to flash an i9100"t" specific modem or your coverage will be dismal.

Ps. Is it really just the Australian version that can't change the dock icons. How rubbish.

Sent from a galaxy far, far away
[Galaxy S II Q&A, Help & Troubleshooting] eskriminal:
if you want pure android, you'll probably be unable to find 4.1 since it's obsolete in aosp and I'd advise you to go with either 4.2 or even 4.3, as 4.2 especially is highly stable.

also, the guy above me is mistaken about modems, the stock i9100 modems work fine on the t variant, just depends on your carrier which ones you want to use.

to install a rom just flash a recovery image from odin (e.g. Dorimanx or PhilZ) and then copy the necessary zips to your sd, boot to recovery, and flash them :)

remember to back up your data first though
[Galaxy S II Q&A, Help & Troubleshooting] Hopper8:
Just to clarify.... "the guy above you" owns an i9100 and maintains a friend's i9100T. If you mean the international i9100 modem is able to be flashed on an i9100T, I agree. I've done it. I know you also own "T" variant.

What happens in my case is that the data speeds are so dismal you'd be better off using an encyclopaedia than googling something (literally 2Kb/s in some areas. Flashing a "T" specific modem sees the speed jump to 250-300Kb/s or so in the same spot). I'm guessing by your post you have better success than that with i9100 modems on a "t" variant.
[Galaxy S II Q&A, Help & Troubleshooting] eskriminal:
oh, my apologies, hadn't seen anyone with that poor a result

I do indeed get much better results with xxms2 for example :)
[Galaxy S II Q&A, Help & Troubleshooting] Hopper8:
No probs mate :) Odd that you say that, I use XXMS2 /MS3 myself, so naturally tried them on my friend's T variant immediately after rooting. Both modems were dismal and got the 2Kb/s (sometimes hitting 20ishKb/s :0) I mentioned. Now I've got them on DULP4 & no issues at all :)
[Galaxy S II Q&A, Help & Troubleshooting] eskriminal:
oh okay, that's odd

I'm testing dvls3 right now, the Vodafone jb modem, which is a t modem, but normally I run xxms2 or nelp3
[Galaxy S II Q&A, Help & Troubleshooting] Hopper8:
Yeah I've flashed dvls3 for them, it wasn't that good. Which is even weirder as they're on vodafone. Eh oh well, not my phone so I can't be constantly testing.
[Samsung Galaxy Nexus] hgmichna:
I have a rooted Galaxy Nexus with stock Android 4.3 and TWRP 2.6.0.0 (latest available for this device).

Today I received the OTA update to Android 4.3 build JWR66Y from JWR66V and accepted it. It immediately failed due to some ZIP signature problem.

I suspected that this is a TWRP problem, booted into TWRP, located the OTA update file, whose name I could still see in the log display, in /cache, and proceeded to flash it manually with TWRP after disabling the ZIP sig checking.

This worked better. Several patches appeared to run through just fine.

But then it still failed with some other error that I could not recognize quickly enough, but TWRP showed a red "Failed" signal. I could not find the log either, so I still don't know what exactly TWRP thought to have failed.

TWRP then told me that the root/superuser access rights are not OK and offered to fix them, which I gladly accepted.

I rebooted and checked the system, and everything still seems to work, including the root functionality. But the system still shows JWR66V, not JWR66Y. This is what the boot loader shows:

PRODUCT NAME - tuna

VARIANT - maguro 16GB

HW VERSION - 9

BOOTLOADER VERSION - PRIMEMD04

BASEBAND VERSION - I9250XXLJ1

Android also still behaves absolutely normally, as far as I can tell.

Normally previous OTA updates ran through just fine. They only removed root, so I always used the Nexus Root Toolkit to re-root. That was convenient enough and left me with the assurance that each update had worked perfectly. Unfortunately this time it was different.

Does anybody have an idea what has failed? Did the update indeed patch some files and then stalled after doing only half its work? Is the system now in a mixed state, some files already JWR66Y, but the rest still JWR66V? Or does the recovery roll back an incomplete update? Should I unroot the phone to let the update proceed?
[Samsung Galaxy Nexus] beekay201:
You should use JWR66Y factory images+fastboot to "update".
[Samsung Galaxy Nexus] thegios:
remove root, flash OTA zip file, re-apply root
[Samsung Galaxy Nexus] hgmichna:
Yes, the hope is that after unrooting the OTA update will automatically be offered for installation. But what if not?

I don't even know whether I can flash the update manually after unrooting, i.e. with the standard recovery. Can I? Not used to unrooted phones. :)
[Samsung Galaxy Nexus] thegios:
if u remove root and have standard recovery, wait for the OTA notification and it should install, otherwise unlock bootloader, isntall twrp, flash ota and then flash root
[Samsung Galaxy Nexus] hgmichna:
I just removed busybox, flashed standard recovery, then removed root. Checking system updates yielded only the statement that my system is up to date. Since the update file is already in /cache, shouldn't it have offered the update straight away? Or do I still have to wait, which would be rather stupid?

Here is TWRP's log. Stupidly, it cuts off the lines, so longer lines are cropped.

…

Warning: No file_contexts

Verifying current system. . .

Removing unneeded files. . .

Patching system files. . .

Unpacking new recovery. . .

Symlinks and permissions. . .

set_perm: some changes failed

E:Error executing updater binary in zip '/cache/

Error flashing zip '/cache//1b0ac7dfb2907e5981

Updating partition details. . .

I have also tried unrooting and putting the stock recovery back in place, then booting into a temporary TWRP to flash the OTA update file. Finally I used the Nexus Root Toolkit with its ADB sideload update function, which flashed the OTA update file with the stock recovery. Nothing worked. The error is always the same: set_perm: some changes failed

Next I will try to analyze the update file and see what it wants to do. Perhaps I can find out what would be likely to fail.

Generally this makes using a rooted phone awkward. Until now it was easy, but this situation turns a regular event that used to last a few minutes into an hour-long ordeal. It would be even worse if it required a total wipe. The backup situation has got worse too, both Titanium Backup and Helium are currently buggy and unreliable, not to mention very time-consuming.

Am I the only one who has this problem?
[Samsung Galaxy Nexus] marcars:
I have the same problem, have you found the solution
[Samsung Galaxy Nexus] hgmichna:
Some program had written a file install-recovery.sh into /system/etc and marked it immutable, apparently with the command:

chattr +i /system/etc/install-recovery.sh

The OTA update wanted to write this file by unzipping and failed.

So what I did:

adb shell

su

mount -o remount,rw /system

cd /system/etc

chattr -i install-recovery.sh

rm install-recovery.sh

After that I could install the OTA update with TWRP without any further hitch.
[Samsung Galaxy Nexus] marcars:
rdallion Secret

ok i have found a solution:) in your case you need factory image from developers.google.com/android/nexus/images#nakasijwr66y

unzip this package and edit file .bat if you using windows or .sh when linux is your operating system. Erase in from command "- w" and save the file. Now copy all files from package to C:\Program Files (x86)\Android\android-sdk\platform-tools and start the (double click) .bat file. After that just boot your device in fastboot mode (power + volume-) and the update start the installation. This is not erase your user data if you have modified a .bat file.
[Samsung Galaxy Nexus] hgmichna:
Weird.
[Samsung Galaxy Nexus] hgmichna:
Thanks for the information!

As we now see, this decision to use the immutable property of an ext partition may not have been a very good idea. Many root users will stumble into this trap and waste time, so we are facing a considerable total cost.

I guess that the immutable bit was not meant to be used in normal programs. Does Android use it at all? I would not be surprised if it did not.

Perhaps we need a code of conduct for programmers whose products have root rights. Having root rights does not mean that the entire operating system should now be modified liberally. I propose that a better strategy is to keep modifications requiring root rights to an absolute minimum, treat the operating system gently, and provide some easy means to undo modifications. Inserting an immutable file into the center of the operating system feels more like hiding a land mine in a children's playground.

Before Android 4.3, OTA updates always ran fine on my rooted phone and merely required re-rooting, which was easy and quickly enough to do. But the last two OTA updates both failed.

So now we know that we have to be particularly careful not to get in the way of OTA updates. On my phone the previous update to Android 4.3 failed, because somebody or something had modified the file debuggerd. I guess this can only have been a program with root rights. I don't know which it was. But I now fear that root programs might become a regular source of OTA update problems.

Of course I realise that it is easy to say such things in retrospect. The Germans have a saying, "You are always wiser when you come from the town hall." Also I think we are all grateful that SuperSU exists in the first place and is even free. So don't take the above as an accusation. But if a similar thing happened with the next OTA update and then again the next thereafter, then the root programmers would have to accede that they have had ample prior knowledge and that their products may not be quite perfect yet.

Perhaps these programs need a function called, "Prepare for OTA update". The obvious wish is that rooted phones have a way of accepting OTA updates without wiping data or, worse, a factory reset, because these take too much time and some settings may get lost. In any case I hope that this fresh experience will be a cause for some thorough thinking.
[Samsung Galaxy Nexus] beekay201:
I took the ota today - bone stock JWR66V to JWR66Y, not a single issue.

a maguro sent this.
[Samsung Galaxy Nexus] jazzruby:
It's not exactly the "center" of the operating system and I promise you nothing is going to blow up and no children will be hurt.:p:fingers-crossed:

More than likely it was a USB (un)mounting program, e.g. in my case it is Chainfire's StickMount however it does make a backup (debuggerd.backup).

There is indeed a function for this in SuperSU (Survival mode) but it is to protect the su binar(y/ies) and this is where chattr sets the immutable bit and prevents the recursive chmod, chown, etc.. on /system from stripping the su binary of it's owner/group (root) and setuid/setgid.

The install-recovery.sh is a sort of special case because it behaves as an init.d which can execute init START at boot for daemon process which is what's needed for Superuser (su) in Android 4.3 but it also used by alot of modders to take advantage of it's 'init' behavior even when there's no support in kernel.

Normally install-recovery.sh runs a hash check on the recovery partition at boot and if/when fails this check it calls/executes /system/recovery-from-boot which subsequently flashes/installs the stock recovery.

TWRP saves it's recovery by renaming the file recovery-from-boot.bak before booting back to system and preventing the install of stock recovery however it has been seen in the past that some people will modify/delete install-recovery.sh and this is why Chainfire has chosen to chattr +i the file, he does however provision for 'modders' to continue to use by calling a second init (install-recovery-2.sh) at the end of the script.

If you open/view install-recovery.sh you'll see:

#!/system/bin/sh

# If you're implementing this in a custom kernel/firmware,
# I suggest you use a different script name, and add a service
# to launch it from init.rc

# Launches SuperSU in daemon mode only on Android 4.3+.
# Nothing will happen on 4.2.x or older.
# If you want to force loading the daemon, use "--daemon" instead

/system/xbin/daemonsu --auto-daemon &

# Some apps like to run stuff from this script as well, but the
# installer will have done "chattr +i" on this file to prevent
# accidental modification and deletion. In your code, just search
# this file for "install-recovery-2.sh", and if present, write
# there instead.

/system/etc/install-recovery-2.sh

-JR-
[Samsung Galaxy Nexus] hgmichna:
Except that it reliably kills all OTA updates. I think that is bad enough. I find the idea of using the ext immutable bit quite remarkable. Can you guess the total cost of all the people now running around in circles trying to find out why their OTA update failed? Not everybody is conversant with chattr.

Yes, that was the most likely cause of the 4.2.2 to 4.3 OTA update failure on my phone. If StickMount really has to modify system files, which I doubt, it should at least warn users about breaking OTA updates and provide a clean uninstall function. On my phone StickMount still works after I have replaced debuggerd with the original. Surprise, surprise, modifying the file seems to be quite unnecessary.

Perhaps one should simply walk a big arc around everything coming from Chainfire. The guy seems to be beset by the idea of killing OTA updates one way or another.

How generous! He seems to assume that people only know his Superuser tool and will gladly cater to its particular idiosyncrasies.

I'm a programmer, though not an Android programmer. In my book such ruthless programming is subsumed under "arrogant coding".
[Samsung Galaxy Nexus] adeelhayat90:
pls help

Hello,

This is the first time ever I'm posting something. I own a Nexus 4 and I live in Pakistan. Actually I bought this phone from a local shop which offered used handsets and this nexus 4 was bought in UK and somehow had reached here in Pakistan. Now when I reset the phone first to input my details and it restarted I got to know that it had cyanogen mod installed also doing a factory reset deleted its chrome and play apps as well. It was rooted running android 4.3 build JWR66V. I don't know but I wanted a normal nexus 4 running everything stock. I wanted to get the OTAs so I followed this thread to unroot it:

http://xdaforums.com/showthread.php?t=2010312

and installed the stock android 4.3 build JWR66V factory image with stock recovery and everything else.

Just left the bootloader unlocked.

But now the OTA build JWR66Y is available but every time I check it says my phone is up to date. Please help how will I be able to receive OTAs. Thanks in advance