yashsingh1/xdaforums huggingface dataset:
[HTC Rezound] Delldorado:
I entered in my Facebook account and it started uploading all my friends and added like 700 more contacts. Certainly didn't want that so I unchecked all the contacts stuffed went into people and unchecked Facebook there. I they all went away however when I am picking a contact when I start a message it shows all of the Facebook numbers again. I it did the same thing on my girlfriends rhyme as well and she'd like a solution too. Thanks in advance
[HTC Rezound] DrSadistic:
+1 this happens with Google + contacts also. Any advice on this one would be greatly appreciated.
[HTC Rezound] AtLemacks:
Google+ is part of your Google Account. All of your cantacts are synced together under that account. There is no way to separate it, even if you didn't have G+ on the phone.
[HTC Rezound] punman:
You entered your Facebook account info into your phone, and it started uploading your contacts to Facebook? Did you mean downloading your Facebook contacts to your phone? Yes, it does that. The People app in Sense loves to suck in ALL your contacts and combine them (it calls it "linking" and you can see what contacts it has linked for you in the Settings menu.) The Messages app pulls from that same database, and I couldn't find a way to restrict it either.

Have you tried Settings -> Accounts and Sync -> Facebook and uncheck "Contacts?" You may have to remove the account entirely, uncheck auto-sync long enough to get the account added, and then uncheck the Contacts box. Just a guess, I haven't tried it.
[HTC Rezound] Delldorado:
Yeah that didn't stop it from appearing when I would view contacts through a new text. I just completely removed the account seems fine now.
[HTC Rezound] Argent36:
Hrm my Facebook only synced with my existing contacts - it's an option in the Facebook app

Also I have like 9000 people on Google+ but they aren't in my phone either....

not sure what you guys are doing to get them all
[HTC Rezound] AtLemacks:
I don't have 9,000 people on G+ because I am not a whore, lol. But, there are options in both the apps and contacts to only sync with existing contacts, only add people with numbers, etc...

If you have 9,000 friends on G+ they are not your friends. I have been on since day 0 and have slightly over 100 people I know in real life ;)
[HTC Rezound] feralicious:
Apparently there's a big Facebook app update today so hopefully that helps.
[HTC Rezound] punman:
G+ is more like Twitter for me, I follow people I don't consider "friends" simply because I want to read what they have to say. I have a separate circle for real Friends (capital-F!)

Anyway, the person who was complaining about G+ contacts showing on his phone may have been noticing them in Talk, because the Big G just decided to default all your G+ circles into Talk contacts unless you go in and deselect them. I don't think there's any way to integrate G+ into your phone contacts.
[HTC Rezound] AtLemacks:
My G+ contacts are linked with their various phone contacts. But of course, all of my contacts have been backed up to Google and GMail since before Android even existed.
[HTC Rezound] punman:
They're linked with existing contacts, yeah. But I don't know if it imports from Google+ contact info for non-local or non-Google people. In other words, if the only place you've got info for someone is a Google+ circle, I think that's where they'll stay. Once you send them an email, though, if your GMail account is set to auto-add to contacts, it'll offer you the chance to link the G+ contact and the Google contact.

This seems like it makes sense to me, because the people I have in my G+ circles that I don't have any other contact info for do NOT show up on my phone or in GMail.
[EVO 4G Q&A, Help & Troubleshooting] redm1st:
updated voicemail app, and now I can't get my msg's on my phone. Does Anybody know how to fix this?

HTC Mobile 4G
[EVO 4G Q&A, Help & Troubleshooting] redm1st:
Also re-installed the old voicemail app. and still no luck.
[EVO 4G Q&A, Help & Troubleshooting] ToxicLiquid:
Don't know if this will help, But I had a similar problem a couple months ago. Try going into the voice mail app and compose a new msg to: activate@vvm.sprint.com and make a blank recording for at least 5 seconds. then send it. it should re-activate your voice mail.
[EVO 4G Q&A, Help & Troubleshooting] redm1st:
just recently found this post. will give this try.

http://xdaforums.com/showthread.php?t=1197274
[Samsung Galaxy Nexus] coolbho3000:
This is a *clean* kernel based on the latest sources in AOSP (with the volume down interference fix), but also adds an undervolting interface and a 1.4GHz speed step, and brings the GPU to 384MHz instead of 307MHz. It also uses paulobrien's ramdisk for unsecure adb. :)

As with everything, use at your own risk! Overclocking/overvolting can be dangerous for your phone.

UV control + 1.4GHz GPU 384MHz. I encourage you to test this out before flashing.

UV control only - use this if you get stuttering issues at 1.4GHz GPU 384MHz

Or, if you prefer a tweaked kernel with more features, both Francisco and Paul have implemented the UV patch in their kernels. Feel free to post feed back about the UV in this thread, though.

To test: fastboot boot gnex_oc_uv.img

To flash: fastboot flash boot gnex_oc_uv.img

The undervolting interface works exactly as it does in the Nexus S CM kernel. Read the current voltages from /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table and write voltages to the same file space-delimited in mV (millivolts). SetCPU undervolting and probably some other undervolting apps support this interface.

Some users have experienced slowness with the new 1.4GHz speed. If you do, please post a dmesg and your exact symptoms (how slow? benchmark speeds, etc). Thanks to franciscofranco for implementing the overclock in his kernel and having users test. The undervolting patch alone should be 100% stable.

Here is a diff of the 1.4GHz patch and undervolting patch applied to the base kernel.

Available on my github too: http://github.com/coolbho3k

Quick video demo/screenshots:

[youtube]s431hx4OArs[/youtube]

I'm working on getting this phone to faster speeds than 1.4GHz, but it's not as easy as "just remove the underclock because OMAP4460 *should* be 1.5GHz."

A note about the undervolt patch: It's the only change to omap2plus_cpufreq.c in the above diff (you can see it as a single commit (with a typo :P) in the Galaxy Nexus kernel repo on my github). This patch is fairly clean in that it is implemented purely in the omap4 cpufreq driver and supports an arbitrary number of frequencies. It should also work with any recent OMAP4 kernel, not just the Galaxy Nexus. If there are any other devices that use the OMAP4 and have an unlocked bootloader, I welcome developers to try it out!
[Samsung Galaxy Nexus] noobdeagle:
why is it so difficult to hit that 1.5 mark ? kinda curious :P
[Samsung Galaxy Nexus] bigxie:
So, unfortunately, I'm one of those that experiences the stutters at 1.4GHz.

Symptom is pretty simple, it's super slow, with tiny bursts of regular speed. In fact, it took me almost 20 minutes to boot the kernel (I did wipe caches before flashing it). The boot animation would creep slowly, and have a couple short bursts of regular speed, then back to a crawl. Same thing as the apps were being optimized, the progress circle would spin slowly then quickly, etc.

All that's in dmesg are dpll_mpu_ck fails. Here's what I grabbed:

http://pastie.org/2979080
[Samsung Galaxy Nexus] coolbho3000:
It's the exact problem bigxie is having, except I get it at 1.5.

bigxie: thanks for the dmesg, that answers a lot.

I *have* gotten the phone to boot at faster speeds, which should also remedy the problem illustrated above. But it is not consistently stable. It's really weird. It's an issue with something called Duty Cycle Correction, which seems to be unstable on my device, but is required for higher frequencies. DCC seems to be required at lower frequencies for some than others. I wish we could get someone from TI over here ;)

EDIT: posted the test kernel that I used to achieve the above 1.6GHz result. Flash at your own risk!
[Samsung Galaxy Nexus] vivanshah:
if we eventually set "apply on boot" for voltage and it ends up being unstable, we should still be able to get into fastboot and simply reflash the boot.img, correct?
[Samsung Galaxy Nexus] bigxie:
Heh, maybe for you.

I get a nice Google logo when I booted the 1.6GHz :-)

I think I got the short end of the stick when it comes to chips. I noticed with francisco's kernel that I was getting some screen artifacts too, most likely from running the GPU at 384MHz?

Ahh, oh well, I'm so much more interested in UV than OC anyways. Any chance you could post a non overclocked kernel with UV? :D
[Samsung Galaxy Nexus] coolbho3000:
Yes. Just do an adb reboot bootloader during the boot animation. Or, to be extra safe, use fastboot boot instead of fastboot flash until you find stable voltages.

Or, if you want, press "menu" in SetCPU's main tab and extract the safe mode zip to the internal memory. If things go haywire, boot into recovery and flash the zip and the boot voltages will be ignored.
[Samsung Galaxy Nexus] Chirality:
Are you sure DCC is necessary for 1.5GHz? As you probably already know, the TI manual says DCC should be used for 1GHz and greater. But in the stock kernel code for the GN, DCC is bypassed even for 1.5GHz. I dug through the commit logs to find where they changed this:

commit eac0b0094edb42732c4ab095357d8ca9679e94bc
Author: Nishanth Menon <nm@ti.com>
Date: Tue Sep 20 15:45:29 2011 -0500

OMAP4460: DPLL: use DCC bypass until 1.5GHz

DCC is to be bypassed untill 1.5GHz now that samples are trimmed
for DPLL operation upto 3GHz.

Change-Id: I55b7b52656e1630460d84876b994fce561d17b40
Signed-off-by: Nishanth Menon <nm@ti.com>

commit 0e8f213258af4127f7299ed897aeafc20040c7ee
Author: Colin Cross <ccross@android.com>
Date: Tue Sep 6 12:38:25 2011 -0700

ARM: omap4: dpll44xx: Don't use DCC at 1.2GHz

Transitioning from DCC on to DCC off seems to cause rare lockups.
Disable DCC for 1.2 GHz, where it is not strictly necessary.
To lock the DPLL @ 2.4 GHz DPLL trim-override needs to be used.

Based on patch by Vishwanath BS <vishwanath.bs@ti.com>.

Change-Id: I6979f2e5e0d8368c99a466215e6a1153510a6516
Signed-off-by: Colin Cross <ccross@android.com>

It sounds like DCC isn't necessary even for 1.5GHz? If it's not possible to hit 1.5GHz on the GN, it's probably due to binning. Seems like the PRM module may also be binned, those certified to run 3GHz DPLL without DCC are used for 1.5GHz binned chips, while the chips binned for 1.2GHz don't have the good PRM modules. DCC for the MPU clock is probably not usable, since even TI couldn't get it to work without lockups.
[Samsung Galaxy Nexus] coolbho3000:
Posted. As for 384MHz GPU, that's what the GPU is supposed to be at - Google reduced the GPU speed in the final build to save on a bit of battery, but in my experience some UV balances that out nicely.

I can't lock to 1.5GHz with DCC off (see bigxie's 1.4GHz dmesg - the same thing happens), but I can with DCC on (changing the value of OMAP_1_5GHz in dpll44xx.c changes the threshold at which DCC is turned on). Sometimes I can get past the Google logo with DCC on, and I can be perfectly stable within Android, sometimes (with the same binary that I made when it was stable), I can't. The above 1.6GHz kernel I posted does have DCC enabled for 1.6GHz, and at the moment, I can boot into Android. Why this happens totally beyond me right now.

Maybe some of the PRMs in GN units are binned for 1.2GHz and others for 1.5GHz. That would not, however, explain my chip, which works at 1.4GHz but not 1.5GHz (DCC off).

Where did you find that info? The 4460 documentation (for an earlier SoC revision) does say DCC needs to be turned on for over 1GHz. I can't find a technical reference manual for the revision used in the Galaxy Nexus. It would be a shame if we could not get DCC/M3 output to work ever, since we would be essentially stuck at 1.2GHz then.

Also, to pour more knowledge into this, I did look at the omap4_trim_quirks.c and tried to trim the DPLL for operation above 1.2GHz by writing to those registers directly. It seems like on my chip those registers were set up for DPLL operation up to 1.5GHz, so I increased this even more. This did not work.

Transitioning from DCC on to DCC off seems to cause rare lockups.

I did dig extensively through the commit logs, but actually did not see this particular sentence before. That's a shame - I hope we'll be able to solve that problem.

Also of note is Colin Cross's commit disabling 1.5GHz, in which he states the "tuna board is not compatible with 1.5GHz" but does not elaborate further. That's puzzling as well.
[Samsung Galaxy Nexus] Chirality:
Sounds like you are hitting the bug that caused Google/TI to turn off DCC for 1.2GHz in the first place. It seems like getting the device to be stable with DCC would be pretty difficult, and the chip in the GN is not binned for letting the DPLL_MPU to be able to lock at 3GHz, which means it'll be very difficult to impossible to get 1.5GHz to work...

According to omap4_trim_quirks.c, it seems the chip used in the GN is a so-called "PRE_RTP" device, which is not trimmed. So it's using a software trim override to enable the DPLL_MPU to lock at 2.4GHz, and presumably beyond. It sounds like the problem with hitting frequencies higher than 1.2GHz is not due to software trim locks (since this is overridden to allow the DPLL_MPU to lock at any frequency) but rather due to limitations of the silicon itself. This would explain why, with DCC off, some people can hit 1.4GHz while others can not: the PRM is not binned for 3GHz operation, so between 2.4GHz and 3GHz, we'll have some chips running ok and others not being able to lock the DPLL.
[Samsung Galaxy Nexus] noobdeagle:
surely if there were different binning the ones that fail to reach 1.5ghz would be clocked at 1.2ghz and would be sold as 4430's, considering the gnex is advertised as 4460 i would assume its something else likely with that dcc.

im sure the talented people on xda will figure it out eventually :D

also as a side note wasn't there reports of TI being unable to get good yields of 4460's ?
[Samsung Galaxy Nexus] bigxie:
Well, at least I have some great news regarding UV. Seems like the stock voltages were waaaay high.

root@android:/ # cat /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table
cat /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table
1200mhz: 1150 mV
920mhz: 1025 mV
700mhz: 950 mV
350mhz: 875 mV
root@android:/ # cat /sys/devices/system/cpu/cpu1/cpufreq/UV_mV_table
cat /sys/devices/system/cpu/cpu1/cpufreq/UV_mV_table
1200mhz: 1150 mV
920mhz: 1025 mV
700mhz: 950 mV
350mhz: 875 mV

I haven't even gotten it to lock up yet, just kept going down by 25-50mV increments and using SetCPU/CF-Bench to test all the frequencies. Are these for sure being applied? ;-)
[Samsung Galaxy Nexus] coolbho3000:
I wonder if we can just use CLKOUTX2_M3 and DCC all the time (the TRM says we can't).

Try going real low for one of the higher frequencies, ie. 1000 mV. It'll lock up instantly. My heat testing does show these are being applied, and I can boot up at 1150mV hard coded in the kernel too. I imagine it's not too stable.
[Samsung Galaxy Nexus] Chirality:
Given what we know so far, I think it's likely that things went something like this.

Originally, TI designed the 4460 to run at >1GHz using DCC. At this point the 4460s are not binned, and all chips were thought to be able to run at 1.5GHz since with DCC this only required the DPLL to lock at 1.5GHz. But it was later discovered that DCC is not stable. TI seems to have given up on DCC entirely, but this means that the DPLL needs to be able to lock at 3GHz to run the processor at 1.5GHz. Unfortunately not all yields were able to lock DPLL this high, so the 4460s started to be binned. The 4460s that can lock DPLL at 3GHz has this ability hardwired in the efuse, and are called "speed bin." These have the ability to run the processor at 1.5GHz. The 4460s that can't lock DPLL at 3GHz are the normal bin, these can run at up to 1.2GHz, most likely because the minimum DPLL lock that can be obtained by all yields is 2.4GHz. This would explain why yields of 4460s that can clock at 1.5GHz is low, and why all 4460s on the market right now are only binned for 1.2GHz operation.
[Samsung Galaxy Nexus] bigxie:
Yeah, I finally hit the barrier. So, how do you test stability? I ran tons of consecutive short/long/native benches with the max set at each frequency and if it passed all that, a run or two of CF-Bench.

I'll run it more tomorrow, but for now, it seems to me that each frequency is stable at these voltages for my device:

Also, a little OT, but doesn't OMAP4 support NEON? How come there isn't a score in the native bench? IIRC, there was one for devices that support it.

Thanks for all the hard work you've put into this!

EDIT: Mandelbrot in Smartbench crashed this config, had to raise 1200MHz to 1100mV and it all straightened out. Quadrant, Antutu, Smartbench, CF-Bench, Asphalt 6, Fruit Ninja, etc. all run fine.
[Samsung Galaxy Nexus] coolbho3000:
The lack of a NEON benchmark is a bug that I'll just fix.
[Samsung Galaxy Nexus] ande_uk:
my phone froze while running quadrant (the red and blue dna strand) at these voltages..

runs ok at

1200:1200

920:1100

700:1000

350:900

will probably try again half way between..

**update**

full quadrant and asphalt 6 hd run ok at

1200:1150

920:1050

700:950

350:850
[Samsung Galaxy Nexus] Tung_meister:
Can't get anywhere with the 1.6Ghz kernel, it either hangs as the google logo or goes blank and reboots.
[Samsung Galaxy Nexus] Chirality:
It sounds like you already tried directly setting these trimming bits to try to get the DPLL to lock at 3GHz. But in case you haven't, perhaps this will help:

http://www.ti.com/pdfs/wtbu/SWPZ017A.pdf page 53.

Hmmm...which value are you setting in the register to try to get the DPLL to lock at a higher freq? Looking at the TRM again, it seems writting 0x29 to the CONTROL_DPLL_NWELL_TRIM_0 register overrides the DPLL trim to 0x1, which only allows DPLL up to 2.4GHz. To allow up to 3.0GHz, it looks like 0x2b should be written there instead. Also it looks like by default the override is only used when the DPLL trim register reads 0x0. But I'm guessing on the GN 4460 this register reads 0x1. Not sure if you tried to take out this conditional in your original attempt?
[Samsung Galaxy Nexus] Arcadia310:
What are the stock voltages set at? I'm looking to root my device and am a lot more interested in UV than OC. Why do these companies set the voltage so high on stock?
[Samsung Galaxy Nexus] dario3040:
It's not a 1.5 Ghz CPU before they make it run at that clock speed.

And that seems to be their issue.
[Samsung Galaxy Nexus] sblantipodi:
Who said this to you? A cook? :rolleyes:
[Samsung Galaxy Nexus] dario3040:
No :|

It was just incredibly obvious?
[Samsung Galaxy Nexus] jopherr:
Just Google Texas instruments 4460 delays. There should be a couple articles where they state that TI was having difficulties producing a good batch of 1.5 Ghz omap4's
[Samsung Galaxy Nexus] sblantipodi:
obvious for non technical people :)

OMAP4460 born as a 1.5GHz CPU and it is able to run at that frequency.

Cooks wasn't able to push that CPU at that level because they weren't able to give them enough current to work stable.

Another huge problem that cooks generally ignore is the deep idle.

Deep idle help in saving battery but enlarge the current gap between the idle state to the load state, managing the right current in this transition is something critical and no cook as far as I seen taked this into consideration.

The problem is that cooking mama are generally kids playing around with kernels and hacks but they often don't have the skills or the possibility to access "the required data" to correctly work. Only TI engineer can understand some tech specs of that CPUs and this is what our cooks lacks.

The only thing sure now is that TI is selling only one type of OMAP4460 (a lower clocked version is named OMAP4430 and not OMAP4460 clocked at lower freq).

The OMAP4460 is a 1.5GHz CPU, full stop.

---------- Post added at 02:06 PM ---------- Previous post was at 02:04 PM ----------

Find this articles. We don't need forum rumors, cook rumors or stupid analogies, we need an official statement from TI to say what you are saying.

In any case, suppose that this was true, why they created the OMAP4460 if they had the OMAP4430?
[Samsung Galaxy Nexus] jopherr:
These are some things you must understand.

1. GN has a 4460 in it.

2. Google underclocked the gpu in the GN to save power. It may seem like we have an over locked 4430, but that's pretty much what a 4460 is. Also, see point one.

2. The 4460 differs from the 4430 by its increased CPU & GPU clock speeds.

3. You don't need to be a TI engineer to understand the tech specs of the OMAP4 cpus. All the this "required data" you speak of is made available on TI's website.

4. "Cooks" on xda are alot more intelligent than you are giving them credit for. If you have read all the posts in this thread as well as many others, you would understand that all the real devs that are messing with UV and OC have a rather concise knowledge of what they are working with. Yes. Some read TI's documentation.

5. Just cause we have a 4460 does not mean it can run at 1.5 ghz. Not all cpus are created equal. This applies to all silicon chipsets regardless of what we are talking about. Mobile or desktop cpus, mobile or desktop gpus, mobos, etc.

/end rant.
[Samsung Galaxy Nexus] dario3040:
I hope that wasn't directed at me.
[Samsung Galaxy Nexus] @rbiter:
Does anybody happen to know if samsung used 3d transistors? I am guessing no, but they did a nice job with what they had. TI also.

My grandma beat me down and took my nexus. Sent from a jitterbug with beats by dre.
[Samsung Galaxy Nexus] sblantipodi:
go to school, every 1.5GHz CPU can run 1.5GHz. there is no overclock there is only wrong voltages that cookes

aren't able to get correctly for some reasons.

also my grandmother can read the documentation that TI gives as public, the real documentation, the one that worth reading in this case isn't public.
[Samsung Galaxy Nexus] jopherr:
I'm starting to believe that you are just trolling. You honestly have no clue as to what are you talking about. You realize that if the problem with overclocking is because"cooks able to get the voltages correct for some reasons", these developers would figured this out ages ago.

Just for clarification.

The 4460, on paper is a 1.5 ghz CPU.

On. Paper.

Just because it is said to be a 1.5 ghz CPU doesn't make it so. First TI would need to create it running at 1.5 ghz before it would be considered a 1.5 ghz cpu. Until we see it, it is all just smoke.

I suggest you go and see if qualcomm or Samsung would give you as much information to understand the snapdragon or exynos architecture as TI has done for it's OMAP4 SoC.

Nvm there's no use trying to convince someone on the internet lol. Good day.
[Samsung Galaxy Nexus] repvik:
And yes, there's no problem getting the voltage correct.
[Samsung Galaxy Nexus] sblantipodi:
In history I have never seen a CPU that isn't able to get the default frequency advertised on paper.
[Samsung Galaxy Nexus] dario3040:
Making it run at 1.5 GHz is not an issue because of voltage, I suggest that you read the whole thread first.
[Samsung Galaxy Nexus] Luxferro:
Also it's not just a CPU it's a SOC.
[Samsung Galaxy Nexus] sblantipodi:
This thread is full of doubtful information, a 1.5GHz CPU on paper can surely run at 1.5GHz, no need to argue on this ;)
[Samsung Galaxy Nexus] jopherr:
Except our phone is advertised with default frequency of 1.2 ghz not 1.5 ghz. On paper it runs at 1.2 ghz. And that is what it is.
[Samsung Galaxy Nexus] DynamicRam:
deleted . . .
[Samsung Galaxy Nexus] dario3040:
None of this is doubtful information.
[Samsung Galaxy Nexus] BrandonPrice31:
Where do I flash this to? Boot? System?
[Samsung Galaxy Nexus] b15love:
Can a dev create a 512mhz gpu oc for us?? OP said it was possible..
[Samsung Galaxy Nexus] Simmo3D:
I have been waiting for this too.. currently running my GPU at 384MHz but 512MHz would be beast!