yashsingh1/xdaforums huggingface dataset:
[HTC One S] benjamin.j.goodwin:
Haha, a few hours!

Its good but very raw at the moment. I had to play with the pad.prop a lot to get a sort of half acceptable set up. So back to there 1.5 build.

Sent from a Paranoid Nexus
[HTC One S] Spider_Pig27:
will there be anmore updates on this? I really liked this Rom..
[HTC One S] benjamin.j.goodwin:
Yup. At the moment PA don't have anything to add and the new cm9 has the new key mapping which I don't want to add so am looking at a way of updating and not including it. :)
[HTC One S] Zekene:
how to have the light on 100 % on the keys ?

Sorry for bad english :/
[HTC One S] benjamin.j.goodwin:
I don't seem to be able to fix it nor matter what I do. It's really frustrating - sorry.

It's something to do with the framework files I have had to use but I can't find the relevant one to add to fix it.
[HTC One S] Spider_Pig27:
Ahhh cool
[HTC One S] benjamin.j.goodwin:
New build is up, nothing special at the moment but want you to keep having the most stable base from xkonni, plus a few edits to improve the ROM.
[HTC One S] Pheroh:
Awesome! Still no panorama?

Overall, I love this ROM but the stock camera is so good I couldn't let go :\

If this ROM ever gets a stock-ish camera functionality, I will wholeheartedly flash it without a second thought.
[HTC One S] benjamin.j.goodwin:
Well cm9 do have zero delay shooting which we could try and see if the cm9 builds we have could implement. They have it in One X at&t. That would allow some of the features. Honestly though, I just took a picture with the one s on this and using mys sisters using a stock camera and the quality is the same, just the functions that go. :(

Sent from a Paranoid Nexus
[HTC One S] warmonger26:
Does this have beats?

Sent from my Trickdroid One S.
[HTC One S] Pheroh:
Oh, I am not questioning the quality. The functionality is what I like in the stock camera. The burst mode, the pictures while video recording, and the 1080p video.

The burst mode is probably the most important one for me.. It works so well I don't have to worry when taking a photo about a blinking person or a blurry shot .. I just keep pressing and then I get the best shots..

720p videos are good enough for me but it's nice to have the upgrade..

Either way, I truly appreciate your ROM and most likely gonna reflash it once we reach a fully stable edition :D
[HTC One S] benjamin.j.goodwin:
No but you can get awesome beats and flash that on this ROM. :)

Sent from a Paranoid Nexus
[HTC One S] warmonger26:
Idk what awesome beats is, sorry.

Nm: did search on interwebs and found DSP with a.beats.

Sent from my Trickdroid One S.
[HTC One S] warmonger26:
Now about WiFi calling?

Sent from my Trickdroid One S.
[Galaxy S III Q&A, (US Carriers)] matrixzone5:
How come you can't change the screen density on this phone i tried setting it to 300 tto get that extra blast of crispness in text and pictures but it SHows a blank screen after samsung splashy until i restore my backup
[Galaxy S III Q&A, (US Carriers)] Epix4G:
Did you try with ROM tool box....that was easiest on nexus....

Sent from my Sprint Galaxy Nexus CDMA using Xparent ICS Blue Tapatalk 2
[Galaxy S III Q&A, (US Carriers)] matrixzone5:
i used the old sgs tools i will try ith rom toolbox after my sdcard i done formatting to exFat (wish ntfs was suppourted "best filesystem evaaarrrrr" ) haha but exfat is like mobile version of it .
[Galaxy S III Q&A, (US Carriers)] eyecon82:
how about changing the color saturation?
[Galaxy S III Q&A, (US Carriers)] matrixzone5:
i dont think we have the ability to do that just yet but i was able to change the density with rom toolbox
[Galaxy S III Q&A, (US Carriers)] zanderman112:
Easiest way is to manually edit the build.prop, for future reference.

~E.R.A.
[Galaxy S III Q&A, (US Carriers)] gtuansdiamm:
I like the density changer app cause you can set it to reset the screen density to normal on reboot
[T-Mobile LG G2x] aliamin86:
New cm nightly released.
[T-Mobile LG G2x] DJLamontagneIII:
Nice... It's set on an auto build schedule so every sun there will be a new nightly

cm-7-20120624-NIGHTLY-p999.zip (nightly) [Sun Jun 24 2012 06:01:57 GMT-0400 (EDT)]

2012-06-23 08:09 Don't let apps disable the SIM PIN entry screen. -[android_frameworks_base] 2012-06-23 08:07 CMUpdateNotify: Dutch translations -[android_packages_apps_CMUpdateNotify] 2012-06-23 08:07 CMWallpapers: Dutch translations -[android_packages_apps_CMWallpapers] 2012-06-23 08:07 CMWimaxSettings: Dutch translations -[android_packages_apps_CMWimaxSettings] 2012-06-23 08:07 Czech: added missing strings - [android_packages_apps_Calendar] 2012-06-23 08:06 Czech: added missing strings - [android_packages_inputmethods_LatinIME] 2012-06-23 08:06 Don't consider input restricted if keyguard is still disabled. -[android_frameworks_base] 2012-06-23 08:06 Tag: Dutch translations - [android_packages_apps_Tag] 2012-06-23 08:06 CMStats: Dutch translations - [android_packages_apps_CMStats] 2012-06-23 08:05 CMScreenshot: Dutch translations -[android_packages_apps_CMScreenshot] 2012-06-23 08:05 FM: Dutch translations - [android_packages_apps_FM] 2012-06-23 08:04 Polish translation update - [android_packages_apps_Usb] 2012-06-23 08:04 Usb hungarian translations - [android_packages_apps_Usb] 2012-06-23 08:04 update chinese translations - [android_packages_apps_Usb] 2012-06-23 08:03 Ringlock: hide album art when Minimal style is active -[android_frameworks_base] 2012-06-23 08:02 Protips: Dutch translations - [android_packages_apps_Protips] 2012-06-18 11:33 Apply haptic feedback to all buttons, not just the sound button. -[android_frameworks_base] 2012-06-17 20:45 Implement rotation compensation for landscape devices -[android_packages_apps_Camera] 2012-06-17 20:43 Prevent Sym key from showing the IME picker -[android_frameworks_base]
[T-Mobile LG G2x] SovereignKnight:
Bah... still doesnt fix bluetooth calling issue.
[T-Mobile LG G2x] aliamin86:
Idc I'm getting a sensation in tomorrow I can't take this phone no more.
[T-Mobile LG G2x] Rafase282:
Then why even open this thread? Is not like we cant go to CM website or get.cm to check for updates.
[T-Mobile LG G2x] aliamin86:
I say Idc no more out of envy really I love this phone and the devs really work hard to make this phone better than others.and this is a forum people are waiting for the bt fix.so I just try to help out and let everybody know there is an update from the cm team.
[T-Mobile LG G2x] Dralanmage:
I got a new phone but I'm still checking in here to see if this issue gets fixed. I still have my g2x and won't feel right selling it until Bluetooth is fixed. The stock rom, even the new one, makes the phone very buggy and unstable. CM7.2 is smooth as butter and lets the phone run for days without issue... if only Bluetooth were fixed.
[T-Mobile LG G2x] Mister Hat:
I would sell it stock, people might complain or buy it for a lower price if they think you "messed" with it
[T-Mobile LG G2x] aliamin86:
Your rite it is but the thing really bothers me about this phone is the speaker is sometimes low when I watch something on YouTube.
[Sony Xperia P, U, Sola, Go] pradeep19922:
i am flashed my mobile with ICS 6.1.A.0.452 {1257-3740} Generic CH and my BOOTLOADER is locked and i need to go back to Ginger bread how to downgrade back to Gingerbread ......i don't have any backup ftp file of my Gingerbread
[HTC Desire S] motopico:
Hello everyone. Every times i get into recovery mode, these messages are shown for an instant:

SD Checking...

Loading...[PC36DIAG.zip]

No image!

Loading...[PC36DIAG.nbh]

No image or wrong image!

Loading...[PC36IMG.zip]

No image!

Loading...[PC36.IMG.nbh]

No image or wrong image!

or something similar, but my desire is working without problems. Partition is already Fat32, is there something i should do and i don't know about it? Do anybody have the same problem?

Thanks a lot.
[HTC Desire S] Jack_R1:
You're definitely not talking about Desire S, but the messages are standard HTC bootloader behavior. Everything's fine.
[HTC Desire S] motopico:
Im on revolutionary, apart those messages everything is really fine, so can I ignore them without problems? Thanks.
[HTC Desire S] SimonTS:
When Jack_R1 says something it is worth listening as he tends to now what he's talking about. Those messages are purely the system telling you that it's looking for certain files (such as when you flash a new radio) and not finding them. Also, as he said, you're not talking about the Desire S as our device uses P88, not PC36.
[HTC Desire S] motopico:
It's P88, it's because i copy/pasted the messages from another thread and i forgot to edit them. I'm less worried now.
[HTC Desire S] Jack_R1:
When HTC bootloader loads, it scans SD card for specific files. File names have device-specific templates. These are system files with different diagnostic/flashing functionality. By default it shouldn't find any of those, and then it presents you with the menu where you choose "recovery". If it finds any of those - it acts accordingly, and in this case you won't be shown the standard menu of choices, and won't be able to get to recovery.

In case you think I don't know what I'm talking about - search for it in Google, and you'll have as many confirmations as you want. It's generally a better idea than just asking the same question again in the same thread.
[Galaxy S III General (US Carriers)] jvjidNite:
Hey guys I'm sue most if not all our you know about the black ink marks with the SGS III. I was wondering if it would be a good idea to take the phone back and get a new one but now I'm not sure because I hear that almost all the SGS III handsets have them. How many of you have taken yours back and was it worth it?
[Galaxy S III General (US Carriers)] nabbed:
Sorry, I've seen pictures but I really don't know how to find out if i have them.
[Galaxy S III General (US Carriers)] jvjidNite:
You can only see them when it's dark. At first I didn't think it would be a big deal but last night I opened my message app and I could clearly see them.

Edit: has to be a black background.
[Galaxy S III General (US Carriers)] nabbed:
I have none at all. I used the texting app and andftp.
[Galaxy S III General (US Carriers)] teh roxxorz:
I didn't have any on mine, though waiting now on my new ordered phone.
[Galaxy S III General (US Carriers)] jvjidNite:
Hmm well I'm going to be exchanging mine in a few days.
[Galaxy S III General (US Carriers)] LightningPhoenix:
I noticed a couple on mine, but they really are only noticeable in total darkness on a black background. If they get worse I'll consider getting it replaced, but its such a minor issue, it doesn't seem worth the hassle of a replacement.

The screen is amazing compared to my OG Epic.
[Galaxy S III General (US Carriers)] benefit14snake:
They are "normal" for amoled screens. Ive had about 12 razr/razr maxx and everyone had it to a certain extent. They never got worse. As long as you dont have the black line running top to bottom you should be fine.

Sent from my Axiom MAXX!!
[Galaxy S III General (US Carriers)] ReggieTee:
I don't look for stuff like this. I just did and don't see anything.
[Galaxy S III General (US Carriers)] eyecon82:
can you describe these black lines? I haven't noticed it on my phone just yet...but I dont knwo what im looking for? :confused:
[Galaxy S III General (US Carriers)] sewhuy:
Try using this background turn off the lights and see if you can spot the splotches.

http://db.tt/xexCOitH
[Galaxy S III General (US Carriers)] kronium:
Here's how to test:

1) Download Display Tester, Go to Colors, then Dead Pixel.

2) Swipe the screen to the black color Page.

3) Go into a dark closet and look for anything weird on the screen.

I'm pretty sure that everyone who posted here will not have a perfect screen.
[Galaxy S III General (US Carriers)] Jeffbucc:
I have a couple but never notice them unless the screen is super dark...not too worried unless I notice them under normal conditions.
[Galaxy S III General (US Carriers)] Becoming:
Here's an idea; if you have to test for something under extremely particular circumstances and don't notice it otherwise maybe you shouldn't go looking for a reason to make yourself unhappy.

Just a thought.

If you stand on a chair holding the phone at 37 degree angle while watching a specific Nickelback video and get a weird tint...don't do it?
[Galaxy S III General (US Carriers)] Skunk Ape1:
I downloaded display tester and didn't see anything weird at all on my phone's screen. All the colors were smooth and even with no spotting.

____________

Just Flash It !!!
[Galaxy S III General (US Carriers)] falconator:
I noticed a few splotches on day one, but just now after looking at the almost black test image I couldn't see anything at any angle or lighting conditions. Is it possible that this goes away over some time?
[Galaxy S III General (US Carriers)] eyecon82:
i have 2 lines that are about 3x1mm....I cant even notice it unless I really really look for it
[Galaxy S III General (US Carriers)] kronium:
If you ever watch a dark movie, you will notice it. It can be irritating to say the least.
[Galaxy S III General (US Carriers)] jvjidNite:
I wasn't looking for them. I didn't even know they existed. I actually noticed them one night when I was texting. It sucks that some have them and some don't... I would like to be one of the few that doesn't if you know what I mean
[Galaxy S III General (US Carriers)] Becoming:
Yeah, I can definitely understand being irritated if you see it during normal use, it just seems like some people (big thread on this in the international section too) go looking for it. Personally unless if actually seen it during my normal usage I'd never go looking for some flaw that I'd then always know was there.

That was what I was getting at, just to clarify.
[Galaxy S III General (US Carriers)] djlenoir:
So I read my kindle app in bed at night and use the sepia background (sort of a light tan). Well, I noticed a red tinted splotch in the bottom right quadrant of the screen. I tried to just ignore it at first thinking it was just an angle related thing. It started bugging me and then I noticed a red tinted dot in the bottom left quadrant as well. I finally decided to fix the problem by changing the text background to blank (white text). At first I thought that took care of it, but then I noticed that the same blotch and spot were still noticeable (maybe more so) as inky black color that was darker than the normal black (which is pretty black). I can probably make myself ignore the discoloration, but it is annoying for such an expensive device. I know someone mentioned this is common with AMOLED screens. Can someone shed more information on 'why' this common? Wondering if I should get the phone replaced but if it is a situation where there is a better chance it will be there on the replacement then not, I will just live with it.
[Galaxy S III General (US Carriers)] eyecon82:
i exchanged mine because my home button kept sticking

the new one has hardley any black spots at all.....nothing like my old unit with streaks everywhere...phew!
[Galaxy S III General (US Carriers)] kronium:
Hopefully they improved quality control with the newer batches. Also I hope to get a Sony camera sensor in my exchanged S3.
[Galaxy S III General (US Carriers)] eyecon82:
i can actually honestly say i don't have any black marks on my new phone.

how are you guys taking pictures of it? I did a screenshot, but it came out all black
[Galaxy S III General (US Carriers)] zmore:
Hah. Riiiight.
[Samsung Epic 4G Touch] Astrozombie44:
I found a really awesome gif that i would like for a boot screen, i think other might like this as well but maybe the image is to small

Any help is appreciated even a link to a guild would be great. Thank in advance.
[Samsung Epic 4G Touch] VikingoRMCF:
Don't mean to hijack your thread, but I too have a request, .GIF file.. :D

http://db.tt/dMPQEF3z
[Samsung Epic 4G Touch] AddamsonFlint:
Hey everybody,

Like many others, I want to finally make the move over to ICS, but am still hesitant given all that's happened over the last several months. I soft-bricked my E4GT back in Feb. when the first versions of ICS were coming out. My understanding of GB was very thorough, but like many, I simply didn't know about the kernel issues surrounding using CWM and ICS.

I've been running custom roms for 3 years, and have always tried to be as informed as possible as to safe practices with flashing, roms and kernels, recovery and nandroid backups. I never bricked my phone before, or did any stupid/reckless practices when it comes to flashing.

I just wanted to qualify that I've always tried to be as educated as possible and not make stupid noob mistakes when running custom roms.

That being said- after my learning experience and takeaways from my earlier mishap, I've read everything I can on where things stand now. But there are so many threads and so much information now, and so many options now for custom ICS builds- I want to make sure my understanding is correct on everything before I start.

Also, I've seen that there are now many custom recovery options available in ICS, so most importantly, I want to make sure I know what I can do in recovery in ICS, what I can't or shouldn't do, and instead Odin back to EL29 for.

I've read:

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

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

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

http://forums.androidcentral.com/ep...nt-read-before-working-tw-ics-leaks-aosp.html

My understanding is:

Don't flash a custom rom while in ICS, Odin back to EL29 first

Don't factory reset or data wipe while in ICS

Don't restore a GB backup in ICS and vice versa

And as far I know, don't use CWM recovery in ICS

What I need to know is:

Is running a custom recovery "reasonably" safe now in ICS?

Can I do backups (or restore) in ICS safely with these recoveries?

Can I use stock ICS recovery to do most of these tasks?

Can I/should I use Calkulin's Format-All zip in ICS?

If so, when can/should I do a wipe in ICS, and when is it not necessary?

I'm also seeing all these threads for repacked kernels with recovery in ICS, including ones with CWM.

Can I safely flash a kernel while in ICS?

Can I flash the .tFE22_Repack_ACS kernel while in stock FF11?

Can I flash the .tFE22_Repack_ACS kernel while in Calkulin's V 1.6 (FE22)?

Any input with answers to these questions would be greatly appreciated.

Again, I've done the research to be as thoroughly up-to-speed on the do's-and-don'ts of running ICS safely and responsibly, and so I'm not just throwing up this post asking questions instead of looking for the answers to questions that can be easily found with a basic search.

So, I'd respectfully ask that folks only offer helpful positive input to this thread, instead of it filling up with post after post of typical noob-hating smack talking and back-and-forth arguing and attacks, which sadly, many threads often end up becoming.

Again, any help is greatly appreciated in advance.

Thanks...
[Samsung Epic 4G Touch] Esoteric68:
That's a lot to respond to but I'm glad you are asking in depth questions before just plowing ahead. I'll answer what I feel comfortable with and hopefully others will chime in.

First, running custom recovery has always been safe, you just have to be cautious of what you do with that recovery. Flashing ROMs, Kernels and modems has proven relatively safe (especially kernels & modems).

Recent repacks (like agat63's recoveries) have proven safe for backups/restore, but again always follow the safest path suggested in most OPs of every development thread before proceeding.

To my knowledge you still can not use stock ICS recovery for most of these functions, however sfhub has put out a few unlocked stock recovery builds that allowed safe flashing but still warned against wipe data/factory reset.

In my opinion (please note use of opinion) it is still safest to either flash el26+cwm for wiping data/factory reset but most of us have been successfully using Calkulins format_all, Rujelus' format_x2 and/or sfhub's one-click Odin recently released (I say recently it's been a bit now).

Typically full wipes are necessary between ROM flashing, going from one custom to another. If you stick with sfhub's one-click packages this is all taken care of for you and it is the absolute best way to venture into ICS for the first time.

To the three repacked questions at the bottom of your post I believe the answer is a safe, yes.

Remember, asking all this upfront is a fantastic way to start but never hesitate to ask again if you feel even the least bit uncertain about any of the instructions.

Good luck, happy flashing and welcome to ICS.
[Samsung Epic 4G Touch] AddamsonFlint:
Hey, thanks for all the feedback sir!

My follow up questions would be:

Everything I've read has said "don't factory reset or data wipe in ICS"

Is this still the case, or can I do it (using el26+cwm or Calk's Format-All) like you had mentioned?

Also, while looking at this page:

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

I see kernels with CWM recoveries in ICS

Like:

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

I thought CWM isn't safe to use in ICS until the legitimate stock kernel is released from Sprint/Samsung, etc?

That is my biggest concern since that is how I soft-bricked my original E4GT back in Feb, using CWM.
[Samsung Epic 4G Touch] Esoteric68:
Not a Sir (points to pink penguin and wrinkles nose) lol but I get that a lot.

A lot of people choose to flash el26+cwm to do data wipe/factory reset and then flash their ROM of choice.

I've been sticking with the format_all, format_x2 and one-click because it's just what I'm comfortable with.

Kernels repacked with cwm are safe, again it's what you do with those recoveries that can lead to problems. You can safely flash ROMs, kernels and modems (personal experience others may warn against ROMs) but, for now, continue to avoid doing a data wipe/factory reset.

If you want further educating on problems with data wipe/factory reset in ICS recoveries then read the emmc corruption thread. But keep in mind it's chock full of information that may overwhelm you at this point, however it is a valuable resource to keep on hand.

http://xdaforums.com/showthread.php?t=1644364
[HTC Desire S] AEGEAN_GR:
Well guys..I am so afraid of bricking my brand new phone so i have been searching for alternatives(rather than using adb push stuff)to root it the last 3-4 days.I have a DS running 2.3.5,software version 2.10.163.5 and hboot 2.00.0002,branded.Can i use Superoneclick to root it and then flash a custom rom or i need to unlock my bootloader by using htcdev(its better to stay stock rather than using that) and then use the Superoneclick?I dont want to blow up my phone so i am asking for your help guys..
[HTC Desire S] Jack_R1:
You can't be bothered reading, can you? It's so much easier to open 10 threads with questions that are answered 100000 times, than to sit and just read, is it?
[HTC Desire S] AEGEAN_GR:
First of all relax.You have no F@ idea how much reading have i done for this.I have like 23 bookmarks on my browser to try short things out.So give me a break.Most of the guides i found have comments below that say "Not working","Error,HELP" and stuff.All i wanted is a clear answer.YES or NO.I am so F@ confuced about the methods so i asked for a clear answer.If you got it i will push the "thanks" button and say i appreciate your help.If not,please do not even bother saying read because i have done MUCH reading.Believe me.
[HTC Desire S] Jack_R1:
You're reading the wrong sources then.

Read the index thread.

Read the guides.

Read them and try to understand, what each part and each command is doing, and what it's needed for.

You're asking the most basic questions that just about anyone knows the answer to. Try asking Google: "what is S-OFF", "what is the difference between root and S-OFF". Read the answers.

And really, yet again, the same piece of advice: not all phones have to be rooted. Stay stock until you understand enough to mess with your phone. It's better for you, and it's better for your phone. Believe me, having 10 apps you don't use means nothing for your phone.