yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] irotsoma:
Were you getting errors about the string.xml file and having multiple entries for certain strings when running brunch? I noticed that when I just tried it now. Looks like the patch program is creating a string.xml.orig file in the Settings app resource folder even though it's not rejecting the patch. This was because there were some modifications to the string.xml file, but not enough that it wasn't able to figure out how to apply the patch. Since the build system is set up to look at ALL files in the res directory rather than just ones ending in .xml, it was picking up both the patched file and the orig file. Deleting that orig file seemed to correct the problem. You can run this command from the same place you have the patch scripts to delete any .orig or .rej files you might have lingering from failed patches:

find . \( -name \*.orig -o -name \*.rej \) -delete

Once that's done, run brunch again. If you have run the apply script too many times, that also can cause issues that this command will fix.

I am updating the archive file in the OP with a new patch for the strings.xml that should not get disrupted so easily by changes. I also added a reset script that will do a hard reset for git repos of the affected packages. Don't use this script if you have made any other customizations to the Settings app, NFC app or the frameworks/base code as you will lose them. Just do things in this order: 1) run reset script, 2) run repo sync, 3) extract tar again, 4) run apply script, 5) if no errors, run find command above to get rid of any stray rej or orig files, 5) run brunch again. That should correct the problem with the strings.xml errors.

If you are getting a different error, or having a different problem, please explain further and I'll try to help. Let me know if that works for you.
[Samsung Galaxy Nexus] mrplowdan:
Wow I just build my first maguro cm10.1 build using this patch. Works great.

So when new nightly builds come out, as long as the nfc and settings sources don't change, I can just copy over my built Settings.apk and Nfc.apk right? Or do I need to grab framework-res.apk or framework.jar as well?

Oh yah, you might want to add that little find . one liner above to the OP as well, the OP says to run the script above but its not there.
[Samsung Galaxy Nexus] Schiehallion:
Re: [MOD] NFC with Screen Locked/Off CM10 & 10.1

Yeah I do keep it for each nightly, can use a script to save manual copying it all the time but same difference
[Samsung Galaxy Nexus] jadle:
Thx!!

Thanks buddy, works like a charm!!

CM 10.1 (Android 4.2.2)

Franco Kernel

First flashed "NFC_Screen_Locked_CM10.1.zip", but didn't work, then flashed NFC_Screen_Off_CM10.1.zip, now works when the screen is off and even pattern locked 6X6 :D

Thanks again, made my day.
[Samsung Galaxy Nexus] Hessi93:
Sv: [MOD] NFC with Screen Locked/Off CM10 & 10.1

Didn't work for me, flashed the NFC_Screen_Locked.....
[Samsung Galaxy Nexus] irotsoma:
I'll try to build some new ones as soon as I have time over the next few days for those who are having trouble.
[Samsung Galaxy Nexus] irotsoma:
OK, I posted a new version of the Screen Locked for CM10.1 on the OP. Let me know if anyone is still having issues with it. I'm building a Screen Off version too just in case. I'll update that in a little bit.
[Samsung Galaxy Nexus] smartfön:
not writing tags anymore with NFC_Screen_Off_CM10.1

Hello!

I tried the Screen Off for CM10.1 on Cm10.1. Reading a tag with the screen off worked! However, it coulnd't write to NFC tags (using NFC task launcher) anymore. I had put back the original Nfc.apk to be able to write tags again :(

Any intentions on updating one more time?

Thanks for the efforts anyways.

Cheers!
[Samsung Galaxy Nexus] CcAi:
Nice! Great work!
[Samsung Galaxy Nexus] irotsoma:
I'll try building a new one and test it out on my device as soon as I get some free time. I hadn't tried to write a tag for a while, but I know it did work on my device with the screen locked version a couple of months ago. Which device do you have? What release of CM10.1 did you try it on?
[Samsung Galaxy Nexus] Schiehallion:
Always use this mod, can report that I can read tags with screen off. Also write tags with Nfc task launcher. Using cm 10.1 nightlies
[Samsung Galaxy Nexus] nojokez:
Works on Maguro with

PitchBlack ROM 2.0 <based on< BeanStalk 1.205 <based on< CM10.1
[Samsung Galaxy Nexus] lfdmp:
NFC_Screen_Locked_CM10.1.zip works in a Maguro (Google Galaxy Nexus GSM) with CM 10.1.3 (final version) Android 4.2.2

Great job!

Thanks

:victory:
[Samsung Galaxy Nexus] lagendbun:
thumb up...great work...
[Galaxy S III Q&A, Help & Troubleshooting] AL92:
Hi, I've a Samsung Galaxy s3...i've modded Status Bar in Notification Center (where there is operator string!) modding SystemUI.apk (drawable xhdpi), but the operator string overlaps status bar modded! How i can delete string of operator??
[Galaxy S III Q&A, Help & Troubleshooting] AL92:
up
[Galaxy S III Q&A, Help & Troubleshooting] zoot1:
Can you post a screenshot ..

sent from here, there, somewhere!!
[Galaxy S III Q&A, Help & Troubleshooting] AL92:
String "TIM" is on "CaponMod4NSS"

Sent From GS3 with CaponMod4NSS
[Galaxy S III Q&A, Help & Troubleshooting] AL92:
Up

Sent From GS3 with CaponMod4NSS
[HTC Amaze 4G] TheChronicDroid:
Can't get to my recovery, whenever i boot it, it goes to a screen with green arrows in a circle, one pointing at a phone. (it is rooted)

Factory reset won't work either.

Tried downloading a new recovery and put it on my external SD, also renamed it PH85IMG.zip, still didnt work.

Any more advice??

Thanks guys.
[HTC Amaze 4G] mahgninnuc93:
Try Hasoon's all in one. I was in a similar situation and that will help you get it back to the point you can go to factory and then root etc....can you post a picture of what the screen looks like?
[HTC Amaze 4G] PeartFan40:
I think it's safe to assume I can lock this up.

Chongo, I will re-open upon request.

Thread Closed.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

"If you choose not to decide, you still have made a choice"
[Nexus 7 Q&A, Help & Troubleshooting] PathologicalTruther:
I'm using the Google Nexus 7 ToolKit V3.2.0 from the very popular thread on the development forum. I have successfully unlocked the Bootloader and am on step 2. The issue I have is with the "You have chosen Root for Build 4.1.1 JR003D" statement. I'm running version 4.1.2 build JZO54K on my Nexus 7. Will this be an issue or should I just continue with step 2? The prompt is currently waiting for USB debugging to be enabled.
[Nexus 7 Q&A, Help & Troubleshooting] PathologicalTruther:
If anyone was wondering, it's okay to proceed, step 2 worked even though I was running 4.1.2 JZO54K.
[Nexus 4 Q&A, Help & Troubleshooting] ksc6000:
I'm really confused by Google about this.

Various websites (including androidcentral and androidandme) show google's press release to show that the phone has 15.3 hours of talk, and 390 hours of standby time.

But Google has told the verge that it will have "up to 10" hours of talk time.

Then my friend found this: http://support.google.com/nexus/bin/answer.py?hl=en&answer=2840740&topic=2775467&ctx=topic

Which essentially says "up to 10" hours of talk time, and 250 hours standby.

If that is the case, and it looks like it is, I am disappointed. With my OEM 2000 Mah battery in my Galaxy Nexus, I can also obtain about 10 hours of talk time. So then that leads me to believe this Li-polymer battery is no more efficient than the regular li-ion that we have currently...and most of all, I don't see how the phone's crappy "screen on time" (which is a measely 4 hours on mine) will improve.
[Nexus 4 Q&A, Help & Troubleshooting] theoneofgod:
It's not how big the battery is that determines the length of time it takes to drain it. It's how the battery is used. We have to wait for reviews before making judgements.
[Nexus 4 Q&A, Help & Troubleshooting] comminus:
What's the point of speculating? I've never seen any device's battery last as long as the product data sheet says it will. Once the phone is more thoroughly reviewed we'll have a better idea. Even then, the battery life is completely relative to how it's being used.
[Nexus 4 Q&A, Help & Troubleshooting] ksc6000:
I understand what you're saying about relativity to use, but ratings have to have some stem of truth to them, and even if they are inaccurate, they are measuring points.

The point is, they rated the Galaxy Nexus's original 1750Mah battery at 8 hours of talk time.

They've rated this phone's 2100 mah battery at "up to 10".

1750 is 83% of 2100 mah. 83% of 10 hours is 8 hours and 19 minutes. So if in fact by their measurement, the new li-ion-polymer battery in this does only yield "up to 10" hours of battery life, then it's not any significantly more efficient than the Galaxy Nexus' batteries.

In the press releases that all the android websites have seemed to have recieved, it says 15.3 hours of talk time. If that is true, that means this battery is 63% more efficient. That's HUGE. So it's not something to be glossed over. Something is not right. And honestly when I first read those press releases, that made me very excited.

Androidcentral did a poll and found battery life to be at the top of people's concerns with their phones. So this is definitely relevant.

With that in mind, I'm guessing a lot of people, like myself included were hoping for an increase in our screen on time, and now I'm pessemistic about that.
[Nexus 4 Q&A, Help & Troubleshooting] Androidmarketuser:
Battery life should be comparable to the one of LG Optimus G (battery is from LG, too, and it is stated, like for the LG that the charging cycles are 800, instead of the usual 500). Hardware is nearly the same.

http://www.phonearena.com/news/LG-O...-Galaxy-S-III-claims-an-LG-experiment_id35585

This experiment was made by LG itself, so it isn't confident but I believe that it could be around 15hrs.
[Nexus 4 Q&A, Help & Troubleshooting] comminus:
I agree that battery life is a huge area of concern for Android users, and I too hope that there are improvements with the Nexus 4 over the Galaxy Nexus. My point is that the variance in how these devices are used from person to person, what types of applications are running, signal strength, etc makes a numbers like 15.3 or 10 hours of talk time generally moot.

Given the extremely limited amount of information to work with due to so few in-depth reviews being released at the moment, we need to wait and see. Will we all see 15.3 hours of talk time? Probably not. Will it be better than the Galaxy Nexus? I think it will, but how much better remains to be seen and will vary.
[Nexus 4 Q&A, Help & Troubleshooting] ksc6000:
I hope you're right, that it is better. Of course I don't actually expect the battery to be a whole 63% more efficient, but I hope that there is some truth to it being more efficient. Maybe 40% more efficient?

The implications could be very good if it's true, because LG is also claiming that this screen is 60% more efficient.

Now let's look at it another way:

If I can get 4.5 hours of screen on, on the Galaxy Nexus, then if their claims were fully true (which we'll know is not the case, but let's look at it for fun's sake)...then 4.5 x 1.63 (63% more efficient battery) x 1.60 (60% more efficient screen) = 11.736 of screen on time.

Is that realistic? I HIGHLY doubt it.

What if their claims were somewhat true?

Let's say it's only 40% for either:

4.5 x 1.4 x 1.4 = 8.82. That's still something I would love.

Is it a pipe dream? Probably. But one can dream.
[Nexus 4 Q&A, Help & Troubleshooting] poid:
OP you're not comparing apples to apples here; the Nexus 4 is completely different hardware so trying to compare the efficiency of the different battery technologies is a pointless exercise.

trying to do math when you've got the underlying assumptions wrong will just yield wrong answers.
[Galaxy Note II Themes and Apps] jujuburi:
As the title says. Just extracted them from the dump. Everything related to it is a hit now, damn!

https://hotfile.com/dl/178252205/b174a3e/Nexus_4_stuffs.zip.html
[Samsung Galaxy Nexus] finakechi:
Anyone know if this will work out of the box with the GN? If not would it just require new software or is it hardware incompatible?
[Samsung Galaxy Nexus] finakechi:
I would really love to use this thing if anyone has any idea.
[Samsung Galaxy Nexus] 063_XOBX:
If you mean a basic micro USB dock (like the one here) there's no reason it wouldn't work.
[Samsung Galaxy Nexus] finakechi:
Specifically I mean this one. I like the USB connections and HDMI out. I know that the GN supports MHL and USB host, I just don't know if it all works at once.

http://www.androidauthority.com/samsung-galaxy-note-2-galaxy-smart-dock-127378/
[Android Software Development] 0xD34D:
I recently went searching for a collection of build.prop for any and all devices and although I could find build props for several devices, I usually needed to know some specifics about the device and then search google for the build.prop. This is all fine and dandy for finding a build.prop here and there but what I really wanted to find was a centralized location for any and all build prop files. Will this be useful? Who knows, but it's easy enough to gather this data and present it in a way that is easily searchable and open to the entire public.

With that goal in mind I have started by creating a very simple application that will allow a user to upload their build.prop to my server. I'll be working on the server side to make it possible for anyone to simply browse through the various build props that have been collected via this application.

Participating is as simple as installing the app and clicking a button. After successful upload of your build.prop you can simply uninstall the app. If you are game for participating then please check use the link below to download the app and submit your build.prop. Once I get the server side all set up I will update this OP and provide the url for where you can access the acquired build props.

DOWNLOAD

OpenBuildProp.apk

APP SOURCE CODE

https://github.com/0xD34D/OpenBuildProp

OpenBuildProp Site

http://openbuildprop.scheffsblend.com/

Thank you in advance to those that participate and contribute to my efforts in providing a central repository for device build props.
[Android Software Development] jcase:
Wow whoever thought of using an app to do this is truely a Genius!
[Android Software Development] 0xD34D:
I agree and whoever offered to retweet about it and did not is a douche. :p

To be fair though, this isn't an entirely new concept. I have an app on the market that pulled specific fields from the build prop and would sync that up with a central DB if the user opted to do so. This goes a step further and collects the entire build.prop for later use, and for others to look up as well.
[Android Software Development] rezzsha:
Not a bad idea,shall submit soon, could this also be expanded to be used (in the near future) to edit the certain aspects of the build.prop automatically, ie; to adjust Ro.product.model from default to Galaxy Nexus or which ever phone model, to make certain apps work , ie camera , and then back to default if you wanted to. mere suggestions though
[Android Software Development] Motorhead1991:
I forgot that I had a modded build.prop :o. I tweaked it to make use of the 4.2 camera. Please pull the "Google Nexus 4 sgh-i847". I'd hate to be spreading false information
[Android Software Development] neim81094:
Fascinating I will be uploading mine as well, if I have a custom ROM will that change the build.prop in anyway?
[Android Software Development] akshatsourav:
great idea ...

submitted mine ... :)
[Android Software Development] mateorod:
I have been thinking a bunch about how best to optimize the information in the build.prop. There are so many non-standard ways of doing things.

One of my projects probes and sorts devices based on their build.prop and I am constantly amazed at how wildly they differ. Even sorting CyanogenMod and CM kangs is difficult to do well. Sorting by build date took me a long time as well.

I have a feeling you are going to see a bunch of modified info, as some apps and users mod theirs and then forget. But maybe you have some sor of aggregation method that will eventually overrule bad data.

I find it maddening that the build.prop contains no standardized information about screen resolution, i.e. large-mdpi or xhdpi, etc.

I will be looking, thanks for trying to make some sense of this world. It won't always be like this, thankfully. I am glad you asked me to vent my frustrations while I was here...:silly:

Edit: I have maybe 80-100 random builds on my desktop at any given moment, for bunches of devices. Any plans for a web uploader or did I miss it?
[Android Software Development] h3adcrash:
great idea! just submitted mine, hope many others will follow to make this collection successful.
[Android Software Development] babylonbwoy:
Submitted mine and then realised after reading comments that it's tweaked, I went to your site to find it (under LT26i label). It contains v6 superchager data in the bottom of the file. Please remove it if needed.
[Android Software Development] elbaroark:
OpenBuildProp Project

Uploaded my build.prop file from the phone for LGL45C Optimus Net from Net10.
[Android Software Development] UtCollector@gmail.com:
Nice i will do this later for my Gio phone and Tom-Tec tablet.

Would be nice if this helps me out to find device that are like my tablet. (Telechip, Arm7,)
[Android Software Development] jcase:
lol
[Android Software Development] hakan42:
Would this app work with minSdkVersion 7 as well? My Nook Touch reader (eInk display, touch) still runs Android 2.1 :o
[Android Software Development] exadeci:
Uploaded Nexus4 with another update
[Android Software Development] dheeraj (dhlalit11):
uploaded build.prop of captivate running slim ics 4.2

and 1 thing I would like to see is to add a button in the app which will take the user to the website when pressed

and really nice work and idea
[Android Software Development] bombadier:
Uploaded HTC Vision running Andromadus Mimicry 1.5 ICS

also can't upload from my stock Nexus 7 running Jelly Bean 4.2 get a failed to upload error,any suggestions?

cheers
[Android Software Development] tnpapadakos:
this is awesome

thanks for doing it

i would also love to see maybe a spin off of this project which lists known meanings for the abbreviations used in the build.props

tried to start one such thread here awhile ago

it never really caught on
[Asus Transformer TF700] TommyPoehee:
Since a few days my email wont download thew whole mail.

I only see a part of the messege and when i press the button for "download whole email" it says downloading failed!

Ive already put the mail size to 100k ( highest possible)

Does anyone know how to fix this issue?
[Asus Transformer TF700] Alitheia:
Are you referring to the ASUS mail app? I'm not seeing the 100k you're referring to. What mail app are you using?
[Asus Transformer TF700] TommyPoehee:
Well it is the standard widget email which i use

Ive only set it to hotmail.com instead of google mail.

When u opend email go config>( your account> and then u should find the settings of the download size (100k is highest)
[Android Q&A, Help & Troubleshooting] teufel007:
Hi Guys,

does somebody knows from where are the languages loading to the settings menu?

I know normally language strings are stored inside the apk, but I would know where can I edit the languages list which is selectable from any user.

I have attached a picture too :)

Thank you:

Teufel
[Android Q&A, Help & Troubleshooting] Jrcon:
Inside the apk file, look in res folder, values then strings.XML

res/values/strings.xml

I believe, it should be inside res folder though. :thumbup:
[Android Q&A, Help & Troubleshooting] harshaxdadevelopers:
The Android device in question is a Micromax A87(a relatively unknown brand in global market but I hope that should'nt matter).

In Ubuntu, I have double checked the udev rules. They all look perfect. (I cross checked using another phone too). The USB debug mode doesn't show up no matter what. And I have the adb_usb.ini in the right place. I have tried running all possible combinations of running

adb, adb start-server as root. But

adb devices

shows no devices at all.

However, with the USB debugging option enabled on phone, it worked on Win7 after windows installed a Common handset driver.

Now the interesting part. :cool:

If I go back to Ubuntu without disconnecting the cable and do

$ adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
[B]1234567890ABCDEF[/B]	device

The product id is 1234567890ABCDEF and I am able to see it and everthing works fine!!

But the moment I disconnect the USB cable, its gone. :(

So I guess it's not the development machine that is at fault. The device seems to be setting a property while in Windows which stays latched till the usb connection goes off.

What could be a way to get this to work? (Besides developing on Windows :silly: )

Btw the

/data/property/persist.service.adb.enable

is 1 too.
[Android Q&A, Help & Troubleshooting] post-mortem:
What is your computer setup? Are you using a Windows machine, with Ubuntu in a vm? Dual-boot? Other?
[Android Q&A, Help & Troubleshooting] harshaxdadevelopers:
My setup:

Dual boot.

Ubuntu 12.04 and Windows 7.
[Android Q&A, Help & Troubleshooting] post-mortem:
Ok, how about if you plug in the USB with the computer's power off, then boot into Ubuntu?
[Android Q&A, Help & Troubleshooting] jurben:
i have the clone of this phone. mine is Mito A78.

lsusb command shows it as 1c9e:9e08

so idVendor =1c9e and idProduct = 9e08

for now, what you say (plugin to windows and reboot to ubuntu without unplug the phone) is the solution.

i will see if lsusb output still the same.

okay, have checked on windows pc, it should be switched to idVendor =1c9e and idProduct = 9e18

anyway, what you say is a clue that the solution may be around usb_modeswitch and modem manager

further search on usb_modeswitch 1c9e 9e08 found the solution here: http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=3&t=1351

have tried, but not yet switched to idVendor =1c9e and idProduct = 9e18

have to find the correct rules on /etc/usb_modeswitch.d/1c9e:9e08

########################################################
# Mito A78

DefaultVendor=0x1c9e
DefaultProduct=0x9e08

TargetVendor=0x1c9e
TargetProduct=0x9e18

SierraMode=1

CheckSuccess=20

NoDriverLoading=1

found it.

after writing the rules, insert

# Mito A78
ATTR{idVendor}=="1c9e", ATTR{idProduct}=="9e08", RUN+="usb_modeswitch '%b/%k'"

to /lib/udev/rules.d/40-usb_modeswitch.rules

i than have to run

sudo usb_modeswitch -v 0x1c9e -p 0x9e08 -S -R -W

and then the phone switched to idVendor =1c9e and idProduct = 9e18 and adb can access the phone.

:good: :good: :good:
[Android Q&A, Help & Troubleshooting] spicysomtam:
I-mobile IQ 5.1 has same issue, but adb still can't see device

The usb_modeswitch is exactly the same for this phone (same usb vid/pid). However adb still doesn't find the phone under Windows and Ubuntu. lsusb shows the product id switch did work and it all looks right.

Under windows it spins up a cdrom device from the phone so you can install the windows drivers (this lives as an *.iso file under /system); after the driver install, you get the adb device in device manager and two com ports,with all devices having a pid of 9e18 (original 9e08). However adb does not see the device!

I recon there is something wrong on the phone side. This is a very new phone (only release about 5 days ago), so I suspect this is one of the early release bugs...

Since I don't even have a custom recovery for it (CWM, etc) I can even backup my phone and try and do a factory reset.