yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] simplistian:
Ok I make it work with SQL, you need adb shell, root and sqlite3, backup first, do it at your own risk :)

First run the following command in adb shell to start SQLite with the contact database:

cd /data/data/com.android.providers.contacts/databases/
sqlite3 contacts2.db

Then run the following SQL statement to remove the contact named "Example Name" from the frequently contacted list in the people app:

update data_usage_stat set times_used=0 where stat_id = (select stat_id from data_usage_stat where data_id in (select _id from data where raw_contact_id in (select _id from raw_contacts where display_name = 'Example Name')));

Run the People app to see if it works. No reboot required.
[Samsung Galaxy Nexus] S0nico:
With my Galaxy Nexsus not work.

root@android:/ # cd /data/data/com.android.providers.contacts/databases/
cd /data/data/com.android.providers.contacts/databases/
root@android:/data/data/com.android.providers.contacts/databases # sqlite3 contacts2.db
3 contacts2.db <
SQLite version 3.7.4
Enter ".help" for instructions
Enter SQL statements terminated with a ";"
sqlite> update data_usage_stat set times_used=0 where stat_id = (select stat_id
from data_usage_stat where data_id in (select _id from data where raw_contact_id
in (select _id from raw_contacts where display_name = 'Casa')));
update data_usage_stat set times_used=0 where stat_id = (select stat_id from dat
a_usage_stat where data_id in (select _id from data where raw_contact_id in (sel
ect _id from raw_contacts where display_name = 'Casa')));
sqlite> .exit
.exit
root@android:/data/data/com.android.providers.contacts/databases # id
id
uid=0(root) gid=0(root)
root@android:/data/data/com.android.providers.contacts/databases #
[Samsung Galaxy Nexus] simplistian:
try replacing

display_name = 'Casa'

with

display_name like 'Casa%'
[Samsung Galaxy Nexus] anton2009:
I don't know why everybody is making this so difficult. Can't you just delete the contact (i.e. your ex), and then re-add him/her? That way he/she is not on your frequently called list without messing around with your other contacts...
[Samsung Galaxy Nexus] S0nico:
Ok, work on Pepople App but not work on Frequently call
[Samsung Galaxy Nexus] frankie4u:
I ran out into a solution that worked for me.

Create a simple .sh file with following content:

sqlite3 /data/data/com.android.providers.contacts/databases/contacts2.db "delete from data_usage_stat where data_usage_stat.data_id = (select data._id from data inner join raw_contacts on raw_contacts._id = data.raw_contact_id where data.data1 like '%1234567890');"

make sure to replace 1234567890 with the number you want to remove from that list, or use the following to remove the whole list:

sqlite3 /data/data/com.android.providers.contacts/databases/contacts2.db "delete from data_usage_stat;"

and save that file on your device.

Then download from market an app called "scriptMe". Run that app and select the file you have just saved.

tick "with root privilege" (obviously you must be rooted to do that) then "Execute script".

Ah, last thing: make sure the "phone" app isn't running or it retains the old data in memory and "apparently" don't do anything.

Just terminate the app in the way you best know and you are done.

I personally tested it on my GalaxyS with 2 different ICS rom and worked flawlessly. If you don't like "scriptMe" you can use whatever app you want to run .sh scripts. I'm not affiliate at all with the developer and i am totally noob on scripting but sql.

If there's errors on executing script probably your rom doesn't have "sqlite3" bin.

Search on every forum on how to install it and voilà.

Cheers.
[Samsung Galaxy Nexus] drbowden:
Frankie - the message I get trying to run this is "... line 1:/system/bin/sqlite3:Permission denied" I am not an sql user - can you help me understand what permission it wants/needs?

Thanks for any help you can provide.
[Samsung Galaxy Nexus] eventnick:
Ok so you put sqlite3 where it needs to be but you haven't granted it the proper permissions in android to run.

You can do a Chmod 755 from a terminal to sqlite or easiest, use Root Explorer navigate to /system/bin/ , mount the Dir as R/W, Long press on sqlite3. Go to "Permissions" and grant execute permissions to sqlite3. Reset Dir to R Only.

You should be ready to roll now mon frere
[Samsung Galaxy Nexus] spaceman860:
I know cm7 had the feature to remove that list on my nexus one try looking into cm9 rom

Sent from my GNex {GSM} T-Mobile
[Samsung Galaxy Nexus] kynon:
Thanks for the pointer! I didn't use sqlite3, but deleted all records from table data_usage_stat with SQLite Editor, this did the trick quite nicely.

Now I wonder if it would be possible to add an "after insert/update" database trigger to automatically delete any new records added to data_usage_stat, this way the table would remain always empty.
[Samsung Galaxy Nexus] eventnick:
You could always script it to be done periodically or possibly use Tasker to monitor the file or look for a call event and then to clear it.
[Samsung Galaxy Nexus] kynon:
Well, here's a simple solution which works for me on stock 4.0.4. - without periodically executing a script or having some external tool monitoring call events. I didn't notice any negative side effects yet, but please proceed with caution and have a backup (at least of contacts2.db) ready.

What I did was simply adding a trigger to the database - I used aSQLiteManager & aShell for this, but it *should* work with sqlite3, too:

sqlite3 /data/data/com.android.providers.contacts/databases/contacts2.db "create trigger force_empty after insert on data_usage_stat begin delete from data_usage_stat; end;"

This trigger will automatically fire after an insert. It will delete all rows from the table which forces the list of frequently called contacts to be empty all the time (also the list header will not be displayed any more in the phone app).

Thanks again to frankie4u for finding out and pointing us to this database table!
[Samsung Galaxy Nexus] S0nico:
Great!

and if I wanted to remove the trigger? after inserting it?
[Samsung Galaxy Nexus] kynon:
"drop trigger force_empty;" should do the trick...

Here's the syntax:

http://www.sqlite.org/lang_createtrigger.html

http://www.sqlite.org/lang_droptrigger.html
[Samsung Galaxy Nexus] S0nico:
OK!

tnks
[Samsung Galaxy Nexus] S0nico:
You can also use my App ScriptRunner

https://play.google.com/store/apps/details?id=com.snclabs.scriptrunner&feature=search_result

you can run up to 4 script at the same time!

Tnks
[Samsung Galaxy Nexus] palmdude:
Thanks for the script!

It works, but only partially.

Did you notice, that the same frequently called list is also stored in the google search bar?

Any idea how which table we have to clear to get rid of this list (without disabling the search bar)?

See also http://xdaforums.com/showthread.php?t=1706670
[Samsung Galaxy Nexus] kynon:
I found that I could remove a contact from the list of suggestions in the Google search bar by setting its times_contacted and last_time_contacted fields in table contacts of the aforementioned database contacts2.db to 0.

Although I tried this for one contact only using SQLite Editor, I guess you could do this for all contacts using an SQL statement like "update contacts set times_contacted = 0, last_time_contacted = 0;".

To avoid contacts reappearing in the list, you would have to add an after update and/or after insert trigger similar to what I described a few posts earlier for table data_usage_stat.

BTW those two fields also appear in table raw_contacts, but setting those to 0 didn't seem to have any effect on the Google search bar suggestion list.
[Samsung Galaxy Nexus] palmdude:
@kynon good detective work! thanks! That should do the trick.

Well, this is really Google style: try to collect everything, don't forget anything :-)

By the way, did anybody look at cyanogenmod 9 (soon rc1)? Does it have the same database design and/or does it allow to handle this data?

Since my device is encrypted, it is not that easy anymore to flash and test new ROMs :(
[Samsung Galaxy Nexus] fhiso:
I worked perfect before, now with 4.1 Jelly Bean does not work, someone could modify it to work with the new version? greetings and thanks!
[Samsung Galaxy Nexus] anton2009:
Uh... Go to phone app ---> navigate to favorites/recently called ---> hit the settings button in the bottom left ---> "Clear Frequents"
[Samsung Galaxy Nexus] hittzman:
Seems like the "Voila" process worked for me too. I have a Galaxy S4G running ICS CM9 - Fah-Q Edition. Mission accomplished. Thanks Much Frankie4u:good:

EDIT> Also worked on my wife's LG E739 (My Touch) running cm-9-20130331-NIGHTLY.
[Samsung Epic 4G Touch] MJHawaii:
I rooted and cwm my epic touch i dont like this kernal i am a little slower i also lost wifi i would like to stay on my stock rom and go back to ek02 unrooted or flash another kernal advice please
[Samsung Epic 4G Touch] solehjeff:
go to developement section and pick what you want and flash. im from haleiwa north shore nice to see some locals on here.
[Android Q&A, Help & Troubleshooting] Marcus_SwJ:
Hello guys! I wanted to ask whether is anybody facing the same problem as I do?

My Samsung Galaxy SL's vibration for the haptic feedback + UI was very low even when I set the vibration intensity settings to maximum?? I cant remember is it like this the 1st day I use the fon...

Would reli appreciate it if anybody could help me out... Thank you...
[Android Q&A, Help & Troubleshooting] Marcus_SwJ:
Will it solve this if I upgrade my firmware??
[HTC Wildfire S] iamchenxin:
I get four wildfire s. one is s510e from singapore. others are pg76100 from UK.

The screen of s510e is pretty.

But the screen of pg76100 can see many black line at 10cm distance.

it looks like this .

this is because of pg76100 have a different screen ?

Or My pg76100 is a damaged mobile?

thanks.
[HTC Wildfire S] iamchenxin:
this is s510e

This is s510e.

it is different.
[HTC Wildfire S] *se-nsei.:
I personally don't ever look at the screen from 10cm distance, so I think I'm okay with it. :D
[HTC Wildfire S] iamchenxin:
thanks

your screen like the pg76100 ?

all of the pg76100 have this style of pixel gap?

so this pixel gap of my pg76100 is made by HTC ? it does not mean a faked one?

thank you.
[HTC Wildfire S] iamchenxin:
is there any one looks like my pg76100 ?

thx
[Galaxy S II Q&A, Help & Troubleshooting] sharp2G:
Which micro SD card should I get for my galaxy s2? :p
[Galaxy S II Q&A, Help & Troubleshooting] tazer4:
Patriot LX Signature Flash, 32GB microSDHC Class 10 (PSF32GMCSDHC10)

This one is a very good card.
[Galaxy S II Q&A, Help & Troubleshooting] MistahBungle:
Never had any problems with Sandisk cards. I can get a class 4 32GB for less than $50 AUD which is plenty for me.

Unless you want one of their new 64GB micro-SDXC cards for ~$200 ? ;-)

Or you could fork out a bit extra for a class 10 like Tazer mentioned (around $85 AUD for me).
[Galaxy S II Q&A, Help & Troubleshooting] ItsMyMama:
Like you, I faced the same problem and did a little google. I decided on a sandisk 32GB Class 4, which works like a charm. Smooth recording, etc.

A person on androidforums said a class 2 was enough though.

In the end, i guess it depends on your budget and requirements :D
[Galaxy S II Q&A, Help & Troubleshooting] sharp2G:
amazing info guys thanks! :D
[Galaxy S II Q&A, Help & Troubleshooting] Joey2o11:
Personally i'd go with class10. Transferring files onto a class4 card is a slow process !!
[Galaxy S II Q&A, Help & Troubleshooting] sharp2G:
we'll see where I get the most for my buck on boxing day =P
[Galaxy S II Q&A, Help & Troubleshooting] rahulsuneja:
Using Samsung's 16GB Class 6 MicroSD ever since I bought my I9100. It came with a Card Reader as well. The package cost me INR 900 ($19). If you're from India, you can order it online on Homeshop18.com!

Cheers.
[Galaxy S II Q&A, Help & Troubleshooting] JJEgan:
But a lot of the user reviews of class 10 cards say they are slower on the phone than a class 4 . Thats due to poor random read write speeds .

jje
[Galaxy S II Q&A, Help & Troubleshooting] leron09:
erm dont mind i ask but why do we still need a memory card when the phone already had 16gb? and is backing up to sd card better then backing up to titanium backup? And also i had seen people memory card became corrupt and they are unable to use it, how it became corrupt?
[Galaxy S II Q&A, Help & Troubleshooting] ItsMyMama:
Well, some people have a really HUGE music collection. Others , like me, like to download games / try ROMs. So the space is really needed but if you can live with 16GB, good for you :D

What do you mean by backing up to the sd card? As in a nandroid backup?

No idea about the last question though.
[Galaxy S II Q&A, Help & Troubleshooting] leron09:
because i have seen people saying that they can move their backups or even apps to their memory card, so i just wanna know is there any advantage of backing up to your memory card or cont using titanium backup to backup my stuff
[Galaxy S II Q&A, Help & Troubleshooting] MistahBungle:
You can set Titanium (and CW Recovery) to make backups to your external SD. Saves heaps of space on your internal card.
[Galaxy S II Q&A, Help & Troubleshooting] leron09:
hey bro so u know anything about corrupt memory card? how it becomes corrupt and how to restore it back to normal to use it again?
[Galaxy S II Q&A, Help & Troubleshooting] JJEgan:
Format .

jje
[Galaxy S II Q&A, Help & Troubleshooting] MistahBungle:
I don't know why memory cards sometimes become corrupt. That's never happened to me before :confused:

Maybe you could put it in your PC and run Windoze checkdisk on it (if you have a card reader) ? Windoze might (probably a long shot) be able to fix errors on the card.

If I had a situation where a card was giving me problems, I'd probably buy a new card rather than mess around with it. I realise that doesn't help you if you've got a lot of stuff on the card you'll probably lose tho :(

A good thing to do is to keep a copy of all the stuff on your external SD card on your PC just in case it goes bad (as well as copies of your EFS, Titanium & Nandroid backups), that way you wont lose everything if the card dies.
[Galaxy S II Q&A, Help & Troubleshooting] leron09:
sry for the noob question but can anyone tell me if what i had written down is correct?

undervolting meaning i can make my battery life last long?

overclocking meaning i can make my phone more faster but also drain my battery faster?

if i'm correct can someone please link me to a guide or page where i can see how i can undervolt my phone? i had already root my phone and try out quite some of different roms and kernel. current i'm using Galaxyzero rom and phenomenal kernel but my battery life still drain out quite fast. from a 100% charge to less then 10% took me just less then 14hours. so please i really do need some help out there. thx to whoever is able to help me?
[Galaxy S II Q&A, Help & Troubleshooting] MistahBungle:
Please don't ask the exact same question word for word in multiple threads :(
[Motorola Droid Bionic] ddggttff3:
OK, I have seen lots of threads about people returning or replacing rooted phones, and getting literally RAGED at by this community, so I am personally wondering, what is seen as wrong as right? I am not trying to start a post war, I am just honestly wondering... here is what it seems to be from what I have read.

If Not Rooted

*warranty covers failure, but not drops/spills etc.

*Covers spills/drops only if you pay extra for insurance, and u replace through insurance.

IF ROOTED/MODDED in any way

*Normal WARRANTY VOID FROM EVERYTHING

*IF you have insurance, AND you go through INSURANCE for replacement and pay, then it is OK as you pay for the service.

Correct here or not?
[Motorola Droid Bionic] PG101:
If not rooted.. correct points..

If rooted.. point 1 is correct... point 2.. you would have to look at the insurance TnC
[Motorola Droid Bionic] cellzealot:
I think this is an excellent thread and a much needed discussion.

If you root and flash anything to your phone at all, you have voided your warranty and should take responsibility for the consequences.

I have never had insurance, but my understanding of full coverage is that it has no restrictions. You are paying both a monthly premium plus a very high deductible for a replacement phone and you can throw it under a bus if you want to.

That seems perfectly reasonable to me... ;)
[Motorola Droid Bionic] Son et Lumiere:
Here's the deal, you should not expect your manufacturer or service provider to replace the phone you ****ed up by tinkering with it, this is what many people have done and it's called fraud, it's also a major reason why OEMs are starting to lock them down tight (along with people getting free tethering). If, however, you rooted and are having issues with the phones that are plain bugs with the stock software than you have every right to restore it and request a replacement. If you hack your phone up and screw up the boot process it is your fault and you need to take the hit. In most cases the phone can be recovered anyways, people are just too quick to assume it's "bricked" and don't know what they're doing.

If you pay extra for insurance then I suppose you have the right to use it but I still think it's not very moral, the insurance is supposed to cover accidental damage or loss, not failure due to hacking. It's kind of like when people drop their phones in toilets on purpose or they magically 'get lost' or 'stolen' so they can get a different phone.
[Motorola Droid Bionic] nateohio:
Since these smart phones are just mini computers has anyone considered how computer manufacturers warranty their products?

If i give myself administrator access, or install a clean OS, or install linux, it doesn't void my warranty.

Now if something I did caused a hardware failure (ie overclocking the processor) than obviously the warranty FOR THAT PART is null and void. But not the warranty on the ram or hard drive.

I look at rooting and roming the same way. BUT I also know how to recover from my mistakes and will only do a restore/replacement through warranty channels if its hardware related.

If you mess around and dont know what you're doing, that's a different story.
[Motorola Droid Bionic] heavyMGS:
This seems spot on to me.
[Motorola Droid Bionic] greeneink:
"If you root and flash anything to your phone at all, you have voided your warranty and should take responsibility for the consequences."

"Here's the deal, you should not expect your manufacturer or service provider to replace the phone you ****ed up by tinkering with it, this is what many people have done and it's called fraud, it's also a major reason why OEMs are starting to lock them down tight (along with people getting free tethering)."

Nothing I did injured the phone or software. To back up your apps and SETTINGs correctly, you need root. I bought the phone with a data connection issue and a rebooting issue, I didn't create them. If Moto and Verizon aren't going to push software to repair these issues, I have the right to do it with a leaked file. If they don't want the return phones, release the OS's without all the verifications.

I purchased a phone that workes as advertised per MY contract and I didn't receive that.

As for the tether issue, Verizon shouldn't have the right to control how you use data plan, especially if it's capped.

It wouldn't surprise me if alot of the haters are Verizon employees. They lurked everywhere on Crackberry when I was still using my BB and running hybrids.
[Motorola Droid Bionic] Nicelysedated:
Unless I run software that melts the inside of my phone how is it really voiding the warrnty? Seriously, any software problem we create could be easily fixed with the properly released software.

You give me a phone that works all the time and ill stop messing with it. Verizon doesn't care about incovincing you, why would I care if I cause them trouble by tampering with my phone and then exchanging it, when they can easily release the software so I can fix it myself?
[Motorola Droid Bionic] skatastic:
I'm not a lawyer so take this with a grain of salt but the "voided warranty" issue can be looked at in the framework of cars. I believe there is a law that says a warranty on one part of the car can't be considered void because of some other alteration. For example if you get an aftermarket exhaust and then a week later your transmission bites the dust the manufacturer can't say that the exhaust you put on caused a problem with the transmission so they therefore must honor the warranty on the transmission. So if you root your phone, put a new ROM on it, and then your display goes out then in theory, the law should say they still have to honor the warranty because the software change didn't cause the display to fail. Anything else is on you. So, if you are dissatisfied with any aspect of the performance of the stock phone which leads you flash something that you are equally dissatisfied with then legally you have given up your right to complain even if the same problem existed with the stock phone. Morally, I might argue that if the problem existed from the onset and it continued to exist after the flash then you only tried to mitigate the original problem so in certain circumstances you might be justified in returning. If you flash something that causes FCs, or some other new problem then that is squarely on you.

The insurance question isn't a question either morally or legally. I don't believe there are any insurance policies that take into account software tinkering so you shouldn't lean on the insurance for your mistakes. I don't think insurance for bad flashes could be offered as they'd suffer from adverse selection. Adverse selection is where the only people that want to buy insurance are the ones that will almost certainly use it. If the only people that want to buy insurance are the ones that will almost certainly use it then the premium would end up very high.

As far as the analogy to desktop/laptop warranties, I don't think that is a good analogy. With desktop PCs the OS lives on a hard drive and the BIOS is rarely if ever flashed. With phones, the OS lives on firmware so updates are all flashed which in some cases is a process that can't be undone without a JTAG (or similar). With a desktop computer, no matter how bad you screw up your system with viruses, malware, driver corruption, etc; you can just reformat your hard drive and start over.

just my $0.02
[Motorola Droid Bionic] technomaje:
You are right on both counts. If your device is acting up mechanically or electrically then the warranty covers, provided it is not rooted when it comes into Verizon. That's the whole key right there. Just don't mention it was rooted. Here is why. The warranty says it has to be mechanical or electrical failures. Rooting (except for overclocking) wont cause that. It can mimic it, for instance the screen cutting out or power cycles. As long as its locked and stock when it comes into the returns warehouse your ok.

As for insurance. If its Asurion, which it probably is, they will replace it. Insurance covers loss, theft, and damage. Bricking it is no different than dropping it in the lake, or a glass of tea. It's not fraud. It's what you pay for.

Now for a short soap box. Don't just brick it and call Asurion. Try to fix it, it's usually fixable.

Now for the Verizon Employee hater. Get bent. Those employees are here on their own time doing things with their equipment. Im sick of people making them out as the bad guys. They work their ass off day in and day out. Its a job. For those that say that employee should be ashamed of working for the company, get real. Its a service. The employees need a job and most try very hard to balance the policies and customer satisfaction. I don't see you quitting your job because people *****. You take it with a grain of salt, help how you can, and move on. The people that complain constantly are a very small minority that are no better than trolls. Complain when you have need to. Like the bs $2.00 convenience fee. Thanks to customer complaints it was cancelled.

I'll take my soap box and go now. Just keep in mind, working for a company, doesn't make one bad.