yashsingh1/xdaforums huggingface dataset:
[HD2 General] DillonBladez:
Well, perhaps you would know what I meant if you tried some first, and maybe second generation android devices. Here's a scenario. If you slide down the left part of the screen from top to bottom while also sliding up on the right side, somewhere near the middle the two touch points would "snap" together. It's rather hard to explain, but but I'll try to find a video showing the issue. It's not that all two point multi touch screens have this problem, but it is an inherent issue in older model capacitive touch "sensors" (not quite sure what it's called).

Edit: I think I found a video explaining the problem.

http://www.youtube.com/watch?v=SVc9NMKmYyA&feature=youtube_gdata_player

Pay attention when he opens the multitouch visualizer application. It shows everything ahaha,
[HD2 General] htccraze:
I watched the video but I didnt really see a problme. It may have been a bit laggy but thats about it. The multi-touch zoom (pinch to zoom) works very well on the HD2 or you can always double tap which will do the same thing.
[HD2 General] DillonBladez:
Its a bit hard to see and definitely more noticeable when using it. It just makes typing a pain since if both thumbs are touching the screen at once then it'll give me some random letter from the middle of the keyboard.

Edit: found a thread pertaining to my problem.

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

It seems like it is indeed a hardware issue. If so, then I may just pick up the hd2 as a toy. I need full multi touch capabilities for a daily driver.
[HD2 General] htccraze:
I type quite a bit. At my highest point around 3000 texts a month. I can say I have never came across that problem on my HD2. I admit that I use portrait mode mainly and go back and forth between a few different keyboards.
[HD2 General] DillonBladez:
Perhaps I just need to learn how to type aha.

In any case I can just fall back to Swype which has been pretty reliable for me.

I'm still deciding though. With the quad core kraits coming out soon I'm hoping there'll be a price drop on some old flagships.
[HD2 General] DillonBladez:
Osht double post my bad
[HD2 General] htccraze:
The 3000 texts was a typo. It was supposed to say 5000. I'm no where near that nowadays though. I've personally tried about 35 different keyboards intill I settled on my top 5 I go back and forth between. My top five favorites are Swype, Better keyboard 8, TouchPal keyboard, SwiftKey X / Swiftkey 3 & Slideit. Touchpal is a new one I've come across and it shows a lot of promise. Its free in the market so you may want to check it out.
[HD2 General] jeromejeremytay:
Hi, I figured out a literally unusual question here. Let's say I have HTC HD2 dual booted (with wp7 in nand and ics in sd of course). When booted in wp7 and I received a text message, will I able to read that particular message when I switch off my phone and booted in android? Sorry but I'm very new to this dual boot thing. Thanks alot btw

Sent from Galaxy Nexus running ICS AOKP M4
[HD2 General] samsamuel:
No.
[HD2 General] htccraze:
In short as samsamuel stated no. To slightly explain in detail a bit, dual booting is having two different operating systems on the same device. This is like having two phones side by side. If you get a text message on one phone you wont be able to read it on the other one. Stuff you sign into like facebook or what not you can see those messages on both when you sign into those services but when the messages are sent directly to the phone you wont be able to see them when you sign out of WP7 and into Android. I hope that made sense. Been a long day for me. :(
[AT&T, Rogers HTC One X, Telstra One XL] c5satellite2:
http://phandroid.com/2012/07/26/hac...ble/?utm_medium=referral&utm_source=pulsenews
[AT&T, Rogers HTC One X, Telstra One XL] rohan32:
As long as you don't go around letting people touch your phone to their phone you should be fine... NFC literally needs to be right up against another.
[AT&T, Rogers HTC One X, Telstra One XL] Ragingsheep:
Or just keep NFC off it you don't trust it.
[AT&T, Rogers HTC One X, Telstra One XL] jspidey:
This is such a farce. This is how NFC works - the radio is activated and an action is taken. The worst they could probably do is send you to a page where you *could* download something malicious if you were ignorant in what you were looking at. I can see how scanning an NFC tag could force a download depending on the URL provided but I don't believe there is any way that this action will install something without the user's knowledge. You might as well say that you can "hack" Android via the Internet because in his example, he used NFC to prompt the phone to go to a particular webpage.

You want to talk about insecure? How many people still carry around house keys?
[AT&T, Rogers HTC One X, Telstra One XL] AstroDigital:
Wear a tin-foil hat or trust technology.

Me I rather have convenience technology gives us and will offer
[AT&T, Rogers HTC One X, Telstra One XL] Itaintrite:
In other news, your wallets with all your CC info can also be stolen by a hacking technique called "pickpocket".

Jokes aside, all this means is that Google will have another patch out soon. Oh wait, too late. Already fixed in JB.
[AT&T, Rogers HTC One X, Telstra One XL] Vendetta-NY:
Remember Bluejacking? Nothing like sending a (harmless) "your phone has been virus infected" message to a train car full of commuters and watching all the faces. Ah, the good ol' days...
[AT&T, Rogers HTC One X, Telstra One XL] redpoint73:
Right, when I've played with NFC, the tag has to be close enough to almost touch (with millimeters) before the phone reads the tag. And the way NFC normally works when I've used it, the phone has to be screen on, and off the lockscreen. Unless there is some way around this?
[Android General] c5satellite2:
http://phandroid.com/2012/07/26/hac...ble/?utm_medium=referral&utm_source=pulsenews
[General Topics] c5satellite2:
http://phandroid.com/2012/07/26/hac...ble/?utm_medium=referral&utm_source=pulsenews
[General Topics] MissionImprobable:
A lot more than NFC is open to attack it seems. Making Nexus devices look more and more sexy everyday.
[NFC Hacking] c5satellite2:
http://phandroid.com/2012/07/26/hac...ble/?utm_medium=referral&utm_source=pulsenews
[NFC Hacking] garrettcorn:
good read good thing i keep my nfc off all the time :)
[NFC Hacking] c5satellite2:
Can anyone confirm that the radio is actually off when NFC is unchecked in settings?
[NFC Hacking] NFC Guy:
This vulnerability affects very few users. Furthermore, those users that it does affect must have their phone's screen turned on for the vulnerability to be exploited. Surely if you have your screen on, you'd be aware of any foul play from third parties; why are you worried?
[NFC Hacking] JamesR913:
Screen has to be on and it has to be VERY close or near (hence the n in nfc)

Sent from my Nocturnal HOX
[NFC Hacking] krohnjw:
Screen on, device unlocked *and* within a few cm of this device (this is the NFC antenna portion of the device, not just anywhere on the device).
[NFC Hacking] Amanoo:
I'm rather interested in how exactly this could be done. Though I reckon it could potentially be dangerous to publicly release that info, I could call it a case of "it's not a bug, it's a feature" and do pretty useful things with it. I'm thinking along the lines of making the phone connect to wifi, which without such hacks is only possible if the phone that scans it has one from a number of NFC apps installed. Pre-installing that app too just so you can log into wifi at someone's house kind of eliminates the purpose of using NFC to login in the first place.
[NFC Hacking] bitbang3r:
If you programmed a NFC tag with a url that contained embedded javascript (or escaped characters that would later unescape to javascript) *and* the browser interpreted them instead of ignoring them or invalidating the whole url... maybe. But it's a big 'if'.

Most new-ish browsers now disallow Javascript in URLs. The other main attack vector would be a trusted site with reflected XSS vulnerability (ie, a site that renders URL-encoded parameters into the rendered page, like a 404 page that displays the requested URL within the error message), but it's more likely that an attacker would just host his own page since the URL target of a NFC tag is opaque until read, anyway.

The main thing: don't allow NFC to launch the browser without previewing the URL's value, and don't preview the url's value in any container that can be induced to interpret its content as HTML.
[NFC Hacking] Amanoo:
Well, if it is possible to make someone connect to wifi using javascript, then it might be interesting to put a small website online with just that bit of javascript. I could then put a hyperlink to that page in the NFC tag. Would still require internet access, but it would use a lot less data to work that way (the normal way is installing an app first, which costs way more data) and it would also be faster and require less actions. From the user's view, it is a lot more elegant. This would mean you don't have to inject the javascript directly into the url and run the risk of the url being blocked by the browser.

Bad side is that you will in all likelyhood practically be putting your wifi password on the internet. That might be a major security issue.

That is assuming it is possible to make devices connect to wlan using javascript, which I understand from your post it is, though I can't find out any information on this.

What do you think about this theory?
[NFC Hacking] bitbang3r:
It depends mainly upon how Android handles NFC events. If it fires an intent that relays the NFC tag's content to a handler that blindly fires it off as another intent, or blindly opens it in a browser window... well... there's a good chance that Bad Things(tm) will eventually happen somehow. If Android makes at least half an attempt to sanitize the NFC-read content, and doesn't have any command-injection vulnerabilities along the way, it'll probably be OK.

I'm still reading up on Android's specific implementation of it. Much of what I wrote above is actually based on naive handling of QR-encoded URLs.

Speaking in the abstract, the worst thing I can imagine an end user doing today is downloading (or writing) cobbled-together handler with no sanity-checking or sanitizing that registers itself as a listener for NFC events, gets the user to make it the official handler, then does something completely stupid, like reading the String straight from the tag and using it to blindly construct a new Intent and fire it off. The thought of someone doing that gives me chills.
[NFC Hacking] Buddy39914:
what if someone where to place a chip near a pay-pass location while using google wallet? what then?
[NFC Hacking] bitbang3r:
A 'chip' ? Basically nothing, except possible denial-of-service due to interference (you can't read two tags simultaneously).

There's nothing magic about NFC. At the end of the day, it's basically a low-ceremony moderate-speed serial link that allows parasitic powering of low-cost radio+eeprom modules in the form of tags. It's what you and the software make of it.

NFC payments are no more or less inherently secure than online paypal purchases encrypted with SSL. In the grand scheme of things, the actual data transfer is usually the *least* of your problems, compared to how the data is stored on your end & handled on the other end.

Would you ever allow your PC to indiscriminately send $10 via Paypal to anybody who manages to plug in a flash drive for 7 seconds? Then don't run a payment client that automatically satisfies any payment request you literally wave in front of it without at least requiring some form of affirmative confirmation & approval from you.

Can a badly-implemented NFC app be cloned or impersonated? Sure. And so can your Visa card, if you hand it to the waiter & he swipes it through his own capture device when you aren't looking. That's why you never, ever want to agree to TOS that leave you on the hook for basically unlimited charges.

NFC payments backed by Visa or Mastercard are a wonderful thing. If somebody defrauds you, you fill out a form, file a police report if necessary, and maybe pay $50 if you have bad credit & your issuer feels like they can screw you as a subprime customer. Otherwise, that's the end of it, unless the bank can prove you committed fraud or engaged in wantonly reckless and unfathomably stupid behavior.

NFC payments backed by my checking account, and no daily hard purchase limit like $50? No. Way. In. HELL. I had a debit card stolen 10 years ago. By the time the bank contacted me, my account was overdrawn by almost $5,000. For almost a week, I couldn't even cash a check from my parents, because it would have just gotten absorbed by the overdraft. I spent 2 days just fighting with the bank to get the ongoing $29+ overdraft fees (for legit expenses autopaid after the thief overdrew my account) waived (after they finally credited the fraudulent charges back to me, ~2 weeks after it happened, and I was able to argue that they wouldn't have *been* overdrafts if the bank had done its job and noticed charges for stores and things I've never bought in my life). The truth is, it's *very* hard to unwind and fix a checking account catastrophe.

So, in summary:

* wave my phone over a sensor to blindly pay $3 and board a subway train that's going to depart without me in 17 seconds if I don't run like a mofo up the escalator, paid from a fund that gets topped off $25 at a time, at most twice per week? Sure.

* wave my phone over a vending machine that requires a pin code the first time I do it at a new location, is backed by a credit card, and maxes out at $10/day? Sure.

* ditto SPECIFICALLY for Taco Bell.

Bigger charges? Ask me, and make me explicitly authorize them after demonstrating my knowledge of a passphrase.
[NFC Hacking] WhammyDroid:
NFC is absolutely insecure. It was discussed by Steve Gibson of GRC on last week's (Oct 3rd) podcast of Security Now.

http://twit.tv/show/security-now/372
[NFC Hacking] bitbang3r:
It was discussed by him, and if you read the whole thing, he basically said exactly what I did. NFC itself is security-neutral. It's a slow short-range wireless serial port.

If someone wrote a proof-of-concept app that ran on your PC, monitored COM1 at 9600-8-N-1 & responded to "transfer://amt=100&acct=123456789" by blindly transferring $100 to account #123456789 without even asking for confirmation, would you declare that serial ports are "totally insecure", too?

NFC is a hardware capability. Nothing less, nothing more. Software can use it for good *or* mischief. Include a compensating control that requires physical affirmation of intent, and legal controls to limit your total liability, and its use for payment is no worse than a prepaid transit card. Security isn't a thing, it's a process with layers of things, some of which WILL occasionally fail.

Remember, if a mugger marches you up to an ATM with a gun in your back, the bank isn't going to refund your withdrawal, either.
[NFC Hacking] elementalx:
WOW that sucks. My bank would. Sucks to be you.

Sent from my squirrel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] EthanMG:
which drivers tend to work better for our phone? i installed the samsung drivers from their support site, but when i plug my (stock) phone into my computer while in recovery, it fails to install drivers, which would cause problems if i wanted to use any adb commands while in recovery. it istalled fine otherwise, while in debugging and in download. some users have mentioned using the naked open source drivers from here http://xdaforums.com/showthread.php?t=1161769 and i am wondering if these work just as well or better. thanks for any help!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
Install the naked drivers while your phone is connected and in recovery. They will be used in recovery only; the Samsung drivers will be used when you're in the ROM.

Works great for me.
[HTC Vivid, Raider, Velocity] mightyquin73:
I successfully s-off my vivid, now i keep bootlooping, cwm will not load
[HTC Vivid, Raider, Velocity] mg2195:
can you get into hboot/fastboot? if you can then use the HTC Vivid All-In-One Toolkit to flash a recovery (cwm)

if that doesnt work the use the HTC Vivid All-In-One Toolkit to relock the bootloader (assuming its unlocked)

once bootloader is relocked flash the HTC AT&T Stock ICS RUU in order to flash the ruu you must first download it on a pc, make sure you have htc drivers-then run the ruu like you would any other pc program...it will walk you through the rest of the way...if for some reason you cant download the ruu from the link above, i got the link from here http://www.htc.com/us/support/htc-vivid-att/software-updates

let me know if any of that worked and/or didnt work...
[HTC Vivid, Raider, Velocity] mightyquin73:
i ran the ruu, rooted again and i am still s-off, can u tell me how to proceed
[HTC Vivid, Raider, Velocity] mg2195:
Ruu won't remove s-off...just wanted to see if that would fix the reboot issue...here was a thread a while back on how to go back to s-on...ill try and find it for you :)
[HTC Vivid, Raider, Velocity] mg2195:
Here's a guide for going back to s-on...never tried it but here you go http://xdaforums.com/showthread.php?t=1630569
[HTC Vivid, Raider, Velocity] mightyquin73:
thanx for the help, i am trying to install a custom kernel/rom
[HTC Vivid, Raider, Velocity] mightyquin73:
I got going, thanks for the help
[HTC Vivid, Raider, Velocity] rsarasam:
Hello,

I have the same issue, but with option S-ON. Today I UNLOCKED bootloader with HTC Vivid All-In-One Toolkit and bi-mistake I flashed NEW ROM from SD card...then it started rebooting all the time. What should I do to get my OS back on my Vivid. Please help...
[HTC Vivid, Raider, Velocity] ronnie498:
Have you reflashed the boot.img?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] smokin1337:
CPU Editor Snapdragon

This mod allows you to easily change cpu settings on the fly, and supports dual core devices. Easier and cheaper $$ than available apps that do the same thing !!

Features:

Change CPU Governor

Change CPU Min/Max Frequencies

Set Dual Core CPU's Independently - Governor and Frequencies

Force Dual Core - Second Core Online ALL The Time

View Current Settings For Everything

Settings applied on boot/reboot

OnDemand Profiling

Edit I/O Scheduler

Edit Cache Size

Usage:

Flash in recovery

Reboot

Open terminal

Type "su" without the quotes

Type "cpu" without the quotes

Make your selections

Notes:

An error appears sometimes when enabling or disabling force dual core, it's ok the settings still get applied.

Settings get applied immediately

Cores can be set independently, you can make the governors and frequencies different on each core. Could be a great battery saver by limiting the second cores resources.

Force Dual Core will make the second core stay online all the time

Some kernels do not have a available_scaling_freq so the available frequencies will not be displayed, look up the settings your kernel has either in your rom thread or kernel thread.

OnDemand Profiling allows you to set profiles for ondemand governor, the settings possible are performance, performance and battery, and battery saver. Setting will only apply to ondemand govenor !! This will overwrite your cpu settings ie. Governor and frequency.

If you experience a dip in performance while using battery saver, in v3+ you can set your own cpu speed and still use the profile. By default battery saver underclocks the cpus to 1242000, you can now run "cpu" and set battery saver for ondemand profile then edit maxcpu0 and maxcpu1 to a higher frequency like 1350000 until your performance is how you want it.

ChangeLog:

v3:

- Added I/O scheduler

- Added cache size

- Added clear all settings ie., disable

- Made it possible to change cpu frequencies when using a profile

Screenshot:

View attachment 1230344

Anyone having trouble with settings sticking use a file explorer and go to /system/xbin and look for a file called start-stop-daemon, if it's not there flash start_stop_daemon.zip in attachments... The script DEPENDS on this file, it will be in the next version to be sure its there :)

Please report any bugs you may find here.

Thanks to -viperboy- for some of the code used

Enjoy ....
​
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jroyalty7:
Firsts

Thanks bro!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] godfirst:
So with this you no longer need setcpu.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] smokin1337:
It does pretty much the same thing except my profiles are preset. Try the battery saver I use it all the time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] godfirst:
So if I enable dual and max for both cpu will it over write the battery saving profile? It also doesn't have the see current settings.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dx9:
Was in the middle of charging my phone. Flashed the script, set to battery saver, rebooted and finished charging the phone. Already at 18 min screen time and battery is at 98%. Pretty sweet.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] caveman999:
So, I flash the zip in CWM and then use terminal to apply the settings?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] godfirst:
Correct
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pannik:
Can you post the settings you are using for the script?

I would like to test the settings you are using.

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JibbsIsMe:
Hmm, I can't seem to get the settings I set to stick at boot. What I'm trying to do is keep my phone in 'battery saver' mode, so I set it, and it works completely. I confirm this by checking my max CPU, and it is changed, so it worked.

Now, when I try to reboot, the settings don't stick. I checked out my root logs, and disabled all apps that may be changing anything CPU related. Then I ran the script again, set to battery saver mode, and rebooted.

Same thing, the script isn't applied anymore.

I'm running AOKP on JK with the KT747 kernel.

I also tried to make a script and get it to run on boot with ROM Toolbox, but I have no idea how to do that. I tried:

su
cpu
8
3

x

but that didn't work at all.

Any help or advice would be greatly appreciated!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] FrankJL_:
AWESOME!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] godfirst:
You have to apply sticky mode after you set the battery setting so it will stick on a reboot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] corythug:
Effin sweet! Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Spartoi:
So will this work on Stock LG1 with ktoonsez kernel?

Also, instead of flashing via CWM, could I just transfer the files to their respective directory via Root Explorer?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] godfirst:
I flashed through twrp. The file comes in a zip, have you extracted it to see where it goes? Also it seems to be working, good mod.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Spartoi:
Yes, the files go in /system/xbin and /system/etc.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] godfirst:
Well then I don't see why not if that is the only two files in the zip. Make a nand and try it out, but if you make a nand you might as well flash it lol. Or at least backup original files if it will do any replacing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Spartoi:
I just installed TWRP and then installed the .zip and ran the script. All seems well for now. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] godfirst:
Sounds good!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DUBVGALAXY:
Would you care to explain how to do this for a n00b?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] awaisuk:
Can you guys also share what rom and kernel are you using and what battery profile?

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dx9:
Wanamlite 1.2 with ktoonesz kernel 19c and have ondemand profile battery saver.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DudeWatsThat:
Wanamlite v1.2 with faux kernel v007 battery saver profile ondemand @ 1.3ghz

Sent from my GSIII