yashsingh1/xdaforums huggingface dataset:
[HTC One S] Krayvon:
Hi guys,

I recently switched to Ville and decided to do the CM10 on it instead of Sense UI as i prefer the true Google experience and look.

Here is the latest change logs and downloads for Ville as they get posted on CM, in no way am i affiliated with CM, i just love their work and want to pass it along to other noobs like me that share the same likes on here as I do. (I will update it as they get posted online)

Download Rom

Download Gapps

Donate to CM

Latest Radio

Changes in 20120927 cm10 nightly for ville

Built on Sep 27th (05:04)

am: Allow more hidden apps on devices with lots of RAM

MERGED ON SEP 26TH AT 20:45:16 IN ANDROID_FRAMEWORKS_BASE

Fix building when OUT_DIR is out of ANDROID_BUILD_TOP

MERGED ON SEP 26TH AT 14:48:53 IN ANDROID_BUILD

Add CPU boosting hooks

MERGED ON SEP 26TH AT 14:37:17 IN ANDROID_FRAMEWORKS_BASE

power: Add CPU boosting interface

MERGED ON SEP 26TH AT 14:35:59 IN ANDROID_FRAMEWORKS_BASE

apns: update MTNL settings, unified for mumbai and delhi

MERGED ON SEP 26TH AT 13:37:20 IN ANDROID_VENDOR_CM

skia: Several tunings

MERGED ON SEP 26TH AT 12:28:30 IN ANDROID_EXTERNAL_SKIA

Changes in 20120926 cm10 nightly for ville

Built on Sep 26th (07:43)

charger: make default to not suspend in charge mode

MERGED ON SEP 26TH AT 04:09:07 IN ANDROID_SYSTEM_CORE

build: Don't build the recovery-from-boot patch on CM

MERGED ON SEP 26TH AT 02:49:11 IN ANDROID_BUILD

Add @hide to MOCK_SMS stuff

MERGED ON SEP 26TH AT 00:32:00 IN ANDROID_FRAMEWORKS_BASE

Launcher: increasing the lower bound and upperbound of loaded pages to avoid stutter in applist scroll

MERGED ON SEP 25TH AT 12:36:59 IN ANDROID_PACKAGES_APPS_TREBUCHET

s5pc110: Add Power HAL (userspace CPU boosting)

MERGED ON SEP 25TH AT 08:08:39 IN ANDROID_HARDWARE_SAMSUNG

Revert "ril: avoid sending null aid string in getIMSI"

MERGED ON SEP 25TH AT 06:36:39 IN ANDROID_FRAMEWORKS_BASE

exynos: Apply format usage flag hack to YUV420P

MERGED ON SEP 25TH AT 05:57:33 IN ANDROID_FRAMEWORKS_NATIVE

ril: dedup mRilVer

MERGED ON SEP 25TH AT 04:06:15 IN ANDROID_FRAMEWORKS_BASE

libmedia: Fix build on non qcom hardware.

MERGED ON SEP 25TH AT 01:33:55 IN ANDROID_FRAMEWORKS_AV

Merge "audioflinger: Add support for post proc effects in Direct Track" into jellybean

MERGED ON SEP 25TH AT 00:09:59 IN ANDROID_FRAMEWORKS_AV

Merge "frameworks/av: Syncronize resume and onPauseTimeOut" into jellybean

MERGED ON SEP 25TH AT 00:09:25 IN ANDROID_FRAMEWORKS_AV

Merge "Fix / before ' breaking the build" into jellybean

MERGED ON SEP 24TH AT 23:48:27 IN ANDROID_PACKAGES_APPS_DESKCLOCK

Fix shortcut intent when all homescreens are full

MERGED ON SEP 24TH AT 23:48:03 IN ANDROID_PACKAGES_APPS_TREBUCHET
[HTC One S] dc211:
Hi Krayvon,

We already have 3 threads for the CM10 Nightlies. The main one is pretty much always on the front page of general. Here ya go.

http://xdaforums.com/showthread.php?t=1781011
[HTC One S] Krayvon:
!

Hi back, I did do a complete search and noticed that none of them get updated.

so I decided to give back to community by putting a package together. thanks.
[HTC One S] el_smurfo:
3 threads. Changelog on BBQlog. Please close
[HTC One S] O_G:
Thread Closed​

As explained above, we already have a CM10 nightly thread.​
[Verizon Samsung Galaxy S III] ProfLonghair:
I'm in a call, and got a text message from my brother. Ever since then it's been beeping every few seconds like I've got a call coming in on call waiting. Is that normal?

This may be a long call, and it's pretty annoying.
[Verizon Samsung Galaxy S III] x714x:
Do you have some sort of reminder settings on for your sms app?
[Verizon Samsung Galaxy S III] ProfLonghair:
Set for every two minutes, but this was like every 3 seconds. I killed the Messaging app and ti finally stopped, but reminder or not, I went to the app and actually read the email, not just checked the notification, which normally is enough to stop the reminder
[Android Q&A, Help & Troubleshooting] cookedude55:
I have seen how these look dont really understand how to use them I have a galaxy player 5.0 is it worth it to try and put either on my player and how do you do it thanx guys
[Android Q&A, Help & Troubleshooting] shimp208:
From what I have seen Jelly Bean based AOKP and CM10 have not yet been released for the galaxy player 5.0 yet but check out this great guide to rooting your device and what ROM's you can put on (Only up to ICS 4.04 as of this writing) it. For more information on CM10 look here and for more information on AOKP look here. These should give you an idea what there like.
[Galaxy Tab 10.1 Android Development] D2dyno:
Screens (Click the image for a larger version):

​

I am not an experienced developer. I'm more along the lines of a hacker, so I won't be able to fix bugs, outside of a compiler/builder's knowledge. I will be able to try as hard as I can to though :)

It is for the p-series tablets (p4wifi, p4, p4tmo, p4vzw).

CWM/TWRP: Wipe System, Data/Factory, Cache, Dalvik Cache.

Install ROM:

GTP7510 (p4wifi) - mirror - Latest Version: pa_p4wifi-2.99-1.9b.zip

GTP7500 (p4) - mirror - Latest Version: pa_p4-2.99-1.9a.zip

SGH-T859 (p4tmo) - mirror - Latest Version: pa_p4tmo-2.99-1.9a.zip

SCH-I905 (p4vzw) - mirror - Latest Version: pa_p4vzw-2.99-1.9a.zip

Install Gapps (20121011): Gapps

Reboot

If you have an issue and you want to call our attention, here's what you do:

Assume that the issue is on your side and try your best to isolate it.

... stay friendly, do not demand anything, do not threaten

... explain your issue as precise as you can, name the exact apps and conditions that cause trouble, help us to replicate the issue right away. If we can't there's no way we can fix it and your post will simply clutter the thread

Paranoid Android Devs

pershoot

Cyanogenmod Team

Dekudan

Yasir Javed Ansari

What doesn't work:

-Anything that doesn't work in CM10

-The date and Time are messed up without Gapps (GMT 0). Fix

You tell me
[Galaxy Tab 10.1 Android Development] D2dyno:
ROM Changelog:

1.9b:
-Synced with sources.

1.9a:
-Synced with sources. Includes Kernel updates, some PA updates, and Other fixes.
-Now building p4vzw version.

1.9:
-Synced with sources (some major updates, find out for yourself from pershoot, CM, PA, etc Github's).
-Solved Bluetooth issue which caused the builds to not complete.

1.8:
-Synced with sources (includes some CM updates, Apollo update, bugfixes, etc).
-Now building p4tmo version of PA.

1.7:
-Switched system wide DPI from MDPI to -Large-MDPI. This is the proper setting for our tablet, and should fix just about every DPI issue ever encountered (Not all though).
-Synced with sources (Not much new though).

1.6 (Broken):
-Synced with latest pershoot kernel updates.
-Synced with PA 2.99
-Possible solution to the DPI not being changeable through PA prefs.
-Synced sources

1.5:
-Fixed DPI issue with Navigation bar (sorry).
-Fixed Paranoid Preferences FC, caused by missing system APK.

1.4:
-Fixed a bug in the building process which caused CMFilemanager to not be added to the ROM automatically.
-Potentially fixed Paranoid Preferences, by switching around some DPI settings.
-Synced with PA 2.55
-Added P4 (3G) version.
-Switched DPI to MDPI, (LDPI no longer supported) and will switch to MDPI-large next build.

1.2:
-Added CMFileManager (CyanogenMod File Manager)

1.1:
-Fixed few remaining DPI issues (HDPI rather than LDPI).
-Changed boot animation to CM10 Animation, to fix the black screen bug.

1.0:
-Synced all sources.
-Paranoid Android 2.5.4
-Proper Kernel in use.
-Use DPI from Tablets.
-Using Paranoid Settings from source.
-Wi-Fi fixed.

PARANOIDANDROID changelog
[Galaxy Tab 10.1 Android Development] D2dyno:
How to's:

Enable Navigation bar:

Enable it under: Settings>Display>Navigation>Enable Navigation Bar.

Fix time:

Settings>Date & Time> Select Time Zone. If you flashed Google apps before you started your device, this is not necessary, as setup has the time zone picker.

Enable Menu Button:

Enable "Show action overflow", in Settings>System>Hardware Keys. The way the ROM is made though, is that you simply hold down the recents button, and the menu for the app appears/is activated.

Enable MTP:

http://xdaforums.com/showthread.php?p=30986826
[Galaxy Tab 10.1 Android Development] used2hvatreo:
First!?
[Galaxy Tab 10.1 Android Development] Jay Rock:
Sweet
[Galaxy Tab 10.1 Android Development] D2dyno:
Yep. My tab actually booted up. Glad it works. Still have to sort a BUNCH of stuff out, since I was aiming at working, not perfect. As long as I know it works, I'll begin getting it perfect (besides a DPI issue, which is easy to fix, it seems pretty smooth). I have to get the kernel sorted out as well...lol

But hey, I knew this was going to be rough for the first few versions.
[Galaxy Tab 10.1 Android Development] D2dyno:
Version 0.1 uploaded.

Contains preferences fix.

NOTE: for today (will fix tomorrow), the DPI is HUGE. You can wait till tomorrow, or manually fix it in the Paranoid Preferences section.
[Galaxy Tab 10.1 Android Development] trunks986:
and for p7500??
[Galaxy Tab 10.1 Android Development] ekrichi:
Thanks forma your effort

Enviado desde mi GT-P7510 usando Tapatalk 2
[Galaxy Tab 10.1 Android Development] mobileguynz:
Hi good to see on install throughs up error with my 7510 wifi. seen this before on other Rom like cm10 had to edit out 2 lines

\META-INF\com\google\android\updater-scriptremove line 2 and

http://xdaforums.com/showpost.php?p=28731560&postcount=104

Now its very late at night I may have this all wrong but I will try this in the morning.
[Galaxy Tab 10.1 Android Development] rickyq12:
Running PA on my S2 and love it.

Cool to see it available for our WiFi tab.

Will be checking it out soon.
[Galaxy Tab 10.1 Android Development] D2dyno:
Hello,

Yes, it is the assert code, checking that your device is "p4wifi".

I have it on my S2 as well! Lol. Yeah, it's a great ROM.
[Galaxy Tab 10.1 Android Development] D2dyno:
Making new build, with the DPI fix in it. Will upload it once it's done.

This will be a fairly stable rom, besides the lack of WIFI. Just the build I made yesterday was very smooth, and no force closes. Once all the visual bugs are squahsed, and the wi-fi works, this could be a daily driver :D
[Galaxy Tab 10.1 Android Development] mr.fast:
Thanks a lot.

What's the difference between this build and the original ROM?
[Galaxy Tab 10.1 Android Development] D2dyno:
Hello,

Do you mean the previous build? I hope this will be the exact same as any PA build. Right now, the difference is the bugs, which I am trying to sort out. Other than that, nothing.
[Galaxy Tab 10.1 Android Development] mobileguynz:
fix for 7510 error on install

Cool thanks D2dyno

Can confirm now all up and going. Downloaded you file and unzipped it into a folder.

went to this location: \META-INF\com\google\android\

thats in this file: updater-script

line 1

assert(getprop("ro.product.device") == "p4wifi" || getprop("ro.build.product") == "p4wifi");

I removed line one that's the line above.

Save file and then Rezipped and installed - success

Also note I came from was [ROM][ICS 4.0.4][7510][UELPL] - Infamous 2 v1.2 - Sep 3, 2012

A ICS rom I didn't wipe etc incase of brick I went back to this once your rom was installed.
[Galaxy Tab 10.1 Android Development] D2dyno:
Yep, those are the lines to remove ;)

The new build has most display issues fixed, now it's just a matter of Wi-Fi...lol
[Galaxy Tab 10.1 Android Development] mobileguynz:
Read your post above as I typed this for the known bug -Wifi (kernel issue, will fix later)

Will wait patiently also keen as beta tester for you as well!

This looks really nice on my tab awesome work so much quicker and more responsive that ICS thanks.
[Galaxy Tab 10.1 Android Development] D2dyno:
New build - 0.2 Uploaded!

This version fixes:

-DPI issues

-Changed preferences to Nexus 7 preferences.
[Galaxy Tab 10.1 Android Development] jonsat:
Please give some joy for 7500 users, if possible... ;)
[Verizon Samsung Galaxy S III] aypeeootrek:
I hook up my phone to my auxiliary in my car and when it's fully plugged in, it only works with one speaker. Same happened when I used headphones as well. If I twist the aux cable a little, I can get it to work somewhat but it's very annoying because pretty much any movement causes it to go back to one speaker. Definitely an annoying issue especially while trying to use my phone as a music player as well. This happen to anyone else? Any type of fix for this?
[Verizon Samsung Galaxy S III] leroybrute:
I have the same exact issues. I don't believe there is a fix without opening the phone up. I have heard of others having the same issues but I haven't done any research on it.
[Verizon Samsung Galaxy S III] aypeeootrek:
I definitely thought I read about other ppl having this issue when the phone first launched. Also vaguely remember a thread about it too. But thanks for replying and def not opening my phone lol. It'll become a $300 paper weight
[Verizon Samsung Galaxy S III] incubus26jc:
I had this issue as well. It was a problem from the first time i ever plugged headphones in. I thought i was going to have to send it back. It went on for weeks. Turns out, I didnt have them plugged all the way in even though i thought i did. I had to push much harder for them to go all the way in. I felt stupid. Work great now lol. Not saying that you have this problem. Just giving my experience.
[Verizon Samsung Galaxy S III] annoyingduck:
Samsung uses a metric variation on thier male headphone jack. The actual female phono jack on the device is for 1/8" connectors. For some reason headphone/line cables are coming out in a metric size that the manufacturers claim is compatible with a true 1/8" jack and they are, but they are slightly undersized than a true 1/8" jack which can cause a loose connection resulting in channels not working properly.

The tip is also slightly modified on the metric male jacks causing that "not fully inserted issue".

Stick with good name cables/headphones with true 1/8" plugs, and that will stop alot of issues that may arise.

Sent from my VZW GS3 running Synergy/Trinity/Dark Horse Rises
[Verizon Samsung Galaxy S III] leroybrute:
My son works for verizon and has a GS3 also and he says try shutting off voice commands if you have them on. They cause issues with the head phone jack sometimes.

Settings/language and imput/voice command for apps.
[Verizon Samsung Galaxy S III] aypeeootrek:
Will try this next time I can and the other suggestions next time I'm in my car. Just don't want to jam it too far in though and end up breaking it lol. Too bad my cars blue tooth audio doesn't work because then this issue would be solved for most of my audio uses
[Verizon Samsung Galaxy S III] chickenmon:
Exact same problem here. Started within the first week of owning the phone. Cant plug it in any further. I think its a bad jack as every 3.5 mm connector ive tried including the one that came with the phone has the same problem. Found this on ebay http://www.ebay.com/itm/OEM-Flex-Ca...051?pt=LH_DefaultDomain_0&hash=item19d3950c8b Im guessing it will fix the problem but I am waiting to see if its more reliable then what shipped with the phone. I plugged mine in daily at least 5 times. Just using bluetooth now got a belkin bluetooth adapator for 25 from amazon that is tied in with a fm modulator from amazon for 14. A hack on a hack but it works. Not the best audio fidelity but good enough.
[Verizon Samsung Galaxy S III] ooofest:
I've only been recently using my headphones with this phone, though they have worked fine. That final click for a positive stereo connection is more tough than one might expect for a portable device, but it's quite secure feeling.

With my Sennheiser PX-100 portables, there's no connection problem with this phone and balance between the speakers seems good. The connection needs to be made fully, pushed down flush with the phone edge and any phone protector needs to lie out of range of the connector, IMHO.

I then tested with my over-the-ear cans, but purposefully using a 1/4" to 1/8" adapter whose 1/8" connector was bent, and noticed a slight left channel bias. The bent adapter did seem to have a problem getting 100% into the jack, as well - still, it was pretty much all the way in with only the slightest bit of lift on one side.

So, I would agree with the poster above who mentioned that - if there are differences between your headphone's male connector and the type they happen to use in this phone - even a slight difference in connector vs jack size could cause an issue for playback.

If all male connectors give problems, I guess the possibilities are:

a. Male connector is not being inserted 100% flush to the phone edge

b. Phone cover is interfering with the connector being 100% inserted

c. Bad phone jack or downstream connection

- ooofest
[Verizon Samsung Galaxy S III] chickenmon:
Pushing it in all the way is not always the fix.. Cant push any of the several headsets I tried in any further. Bad jack add insult to injury the factory charger that came with the phone mysteriously just died wtf .
[Verizon Samsung Galaxy S III] ooofest:
If it won't push in such that the male connector's body is flush with the phone edge, then it is either a bad jack on the phone to begin with (your guess) or all your connectors are somehow incompatible with the new size of jack this phone uses, it would seem.

You're saying the wall charger just died? Might be a warranty on that from Verizon, I'd go to a store or give them a call.

- ooofest
[Verizon Samsung Galaxy S III] Bellamym:
Galaxy s3 headphone jack temp fix

I've had the same problem, tried buying a new cable but audio would only play from one channel

Today playing about I noticed if I pressed the jack slightly to one side it would work, so simple solution, I've bent the metal end of the jack ever so slightly and now it works like a charm with my galaxy s3. No more endlessly messing about playing withthe cable till iit works. Now I say again, vend the jack end slightly till it works, not too much else it might not plug in at all. Hope this helps people out!! Mark
[Verizon Samsung Galaxy S III] zzzaapppman:
I also have exactly the same problem in my car. I have a 3.5mm audio cable which worked fine for the first few weeks and then all of a sudden it stopped playing through the left speaker. At the same time, I also have crackling connection issues when I plug my S3 into a speaker in the kitchen. Headphones seem to work fine though.

It's almost as if some static caused a fault inside the female jack on the S3 given that it worked perfectly for ages and then all the problems came at once.

I tried disabling the voice commands as someone noted above (they were annoying me anyway) and it seemed to make a difference to the crackling but not the reception out of the left speaker - its still very low volume.

I was interested in the post from the guy who said there was a slight difference between 1/8 and 3.5 mm. Which way around is it? The cables I have all claim to be 3.5mm, so are you saying that the S3 has a 1/8th female jack?

I wonder also if there is a 3.5mm to 1/8 inch converter that would do the job. A quick google search didn't throw anything up though.
[T-Mobile LG G2x] rasdabess:
Is it because it is based on hardware acceleration which we do not have?
[T-Mobile LG G2x] noahk423:
Yes that is why. Yet again we need kernel source for everything to work properly, although even with that, project butter might not work as fully as possible.
[T-Mobile LG G2x] FatalityBoyZahy:
Why wouldn't it work of we have kernel sources?
[T-Mobile LG G2x] TMOfo:
Cause Country Crock hasn't churned it out yet.
[T-Mobile LG G2x] noahk423:
I can't remember exactly, since jelly bean isn't available for the 2x, the project butter will be harder to enable fully, I read it somewhere, the basic stuff of butter could only possibly work. Possibly.
[Galaxy Ace S5830 Q&A, Help & Troubleshooting] gordo1701e:
OK, I posted a question regarding Bluetooth Voice dial on here quite a while ago with essentially no responses so I'm gonna try this again.

Is there a rom out there that has a voice dialer/command option that will work with a Bluetooth headset? I'm currently running AOKP_Cooper_Unofficial September 23 Build by the gang over at Jellaxy. The voicedial will work when no Bluetooth headset is connected but when I try to start it with the button on the headset it sits on the "Starting Up" screen and doesn't do anything. I'm a Delivery Driver by trade and it's illegal to use your phone while driving where I live so as you can imagine this feature is EXTREMELY important to me. Any thoughts or suggestions are greatly appreciated. BTW I'm running a GT-S5830D SGA if that makes any difference.
[LG Optimus Black] no14me:
Texas Instruments has announced it will stop investing in mobile chips, and turn its attention to the "embedded processor" market instead.

http://www.digitaltrends.com/mobile/texas-instruments-stops-mobile-processor-investment/

After completed work on OMAP3. So are we lucky? :D
[LG Optimus Black] RomWiz:
We are veery lucky :D

Sent from my Black Jelly phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dixit:
So Ive had my GS3 for a few weeks now and no issues, been stock rooted with the 6.0.1.2 CWM (non touch).

Was browsing around on the General forum and noticed this sticky called "[INDEX] AT&T GS III - I747 {ROMs/Root/Recovery.. etc}"

In there was a 6.0.1.4 CWM, I noticed both were CWM flashable. One for touch and nontouch.

So I downloaded it directly to the phone, booted into CWM, flashed the touch version, and told it to reboot recovery. And since then the phone is basically bricked. It never turned back on, screen remains black. Nothing happens. Cant force it into Download mode either. I took the battery out and put the USB cable in and all I get is the RED LED for about 1min. I get a qhsusb_dload driver that doesnt load on the computer, nothing else. So the phone is basically bricked.

I then decided to see what happened, i downloaded the flash file that was in that thread which is here

http://dl.dropbox.com/u/31151290/CWM/CWM_Touch_6.0.1.4.zip

When I open it and look at the updater-script, I see a problem. This is flashing the recovery to mmcblk0p8

The i747's recovery partition is mmcblk0p18

So this thread that is referencing these two CWMs probably should be pulled or fixed, cause p8 partition is tz. Not sure what that is, but it almost looks like its completely screwed the bootloader part.

Any way to recover this or is JTAG service the only option for my paper weight?

Dixit
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] qwahchees:
I've heard on another thread someone installing CWM Touch had the same problem, vaguely light yours.

All I can say from what knowledge I have is Odin or getting a Jig. Last resort's are better than Service, lol.

Goodluck :]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fallenkirmit:
Jig won't work. You are hard bricked :( sorry for your bad luck!!! I had a hard brick and had to send mine for jtag repair. If you live in the states you could send your phone to get repaired and get it back in 4 business days average. (varies).

If you still have warrenty... go that route!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
http://xdaforums.com/showthread.php?p=32113899

Check this thread
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dixit:
What sucks is the thread is a sticky and points to these two CWM files to use and technically both are wrong. The moderators need to pull those two links. As I mentioned earlier, those two zips are flashing to pEIGHT (p8) when it whould be pEIGHTEEN(p18). Thats why it got bricked.

Dixit
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GerardAnthony:
I did the same thing. It was for the Galaxy Nexus. The person linked to a single post, so it was to hard to tell what that recovery was for. I still wonder if that person did it on purpose.