yashsingh1/xdaforums huggingface dataset:
[Atrix 4G Q&A, Help & Troubleshooting] Soldier-2Point0:
Negative.

MB860, CM7.2.0, Faux 026b1 1Ghz
[Atrix 4G Q&A, Help & Troubleshooting] Heisenberg420:
Thanks for your help. Working perfectly so far.
[Atrix 4G Q&A, Help & Troubleshooting] Soldier-2Point0:
That's why we are here. Perhaps someday you will help me out. :D

MB860, CM7.2.0, Faux 026b1 1Ghz
[HTC Sensation] Macklessdaddy:
when I put my OEM battery in the led turns orange for maybe 2 seconds then solid green as if it's full but my phone won't turn on,is the battery dead or a phone problem?thanks
[HTC Sensation] Skipjacks:
Does another battery work fine? If everything works with a different battery then you can be sure this one is dead.

Sent from a rebel ship by storing the message in an R2 unit. (Help me, XDA. You're my only hope)
[HTC Sensation] Macklessdaddy:
funny thing is it eventually turned on showed 100% and then my phone rebooted(another issue) and it wouldn't turn back on weird
[Android Q&A, Help & Troubleshooting] jetx2x:
Anyone know how to change the status bar ticker text color?

Its the text shown at the top of the screen
[Android Q&A, Help & Troubleshooting] jetx2x:
Geez... no one?
[Android Q&A, Help & Troubleshooting] ZKK007:
Did you ever figure it out? I would love to know how to change the default tickertext color
[Android Q&A, Help & Troubleshooting] m1keyb:
In framework styles you could do this

<style name="TextAppearance.StatusBar.Ticker" parent="@style/TextAppearance.StatusBar">
<item name="textColor">#your_text_color_here</item>
</style>

This is an example of where the original style gets its color from

<style name="TextAppearance.StatusBar.Ticker" parent="@style/TextAppearance.StatusBar" />

No attributes, go to parent

<style name="TextAppearance.StatusBar" parent="@style/TextAppearance">
<item name="textAppearance">?textAppearanceSmall</item>
</style>

An attribute

<style name="Theme">
<item name="colorForeground">@color/bright_foreground_dark</item>
<item name="colorBackground">@color/background_dark</item>
<item name="backgroundDimAmount">0.6</item>
<item name="disabledAlpha">0.5</item>
<snip>
<item name="textAppearanceLarge">@style/TextAppearance.Large</item>
<item name="textAppearanceMedium">@style/TextAppearance.Medium</item>
<item name=[COLOR="red"]"textAppearanceSmall">@style/TextAppearance.Small[/COLOR]</item>

<style name="TextAppearance.Small" parent="@style/TextAppearance">
<item name="textSize">14.0sp</item>
<item name=[COLOR="Red"]"textColor">?textColorSecondary[/COLOR]</item>
</style>

-

<item name="textColorSecondary">@color/secondary_text_dark</item>

secondary_text_dark

<?xml version="1.0" encoding="utf-8"?>
<selector
xmlns:android="http://schemas.android.com/apk/res/android">
<item android:state_window_focused="false" android:state_enabled="false" android:color="@color/dim_foreground_dark_disabled" />
<item android:state_window_focused="false" android:color="@color/dim_foreground_dark" />
<item android:state_enabled="false" android:state_selected="true" android:color="@color/dim_foreground_dark_inverse_disabled" />
<item android:state_enabled="false" android:state_pressed="true" android:color="@color/dim_foreground_dark_inverse_disabled" />
<item android:state_selected="true" android:color="@color/dim_foreground_dark_inverse" />
<item android:color="@color/bright_foreground_dark_inverse" android:state_activated="true" />
<item android:state_pressed="true" android:color="@color/dim_foreground_dark_inverse" />
<item android:state_enabled="false" android:color="@color/dim_foreground_dark_disabled" />
<item android:color="[COLOR="Red"]@color/dim_foreground_dark[/COLOR]" />
</selector>

<color name="dim_foreground_dark">#ffbebebe</color>
[Android Q&A, Help & Troubleshooting] MyLifeRocks10:
Decompile SystemUI.apk and goto res/layout and open status_bar.xml in Notepad++. Find Ticker in that xml file and under that there is two <TextView then add android:textColor="your text color" to both <TextView.

It should look something like this:

<com.android.systemui.statusbar.phone.TickerView android:id="@id/tickerText" android:paddingTop="2.0dip" android:paddingRight="10.0dip" android:layout_width="0.0dip" android:layout_height="wrap_content" android:layout_weight="1.0">
<TextView android:textAppearance="@style/TextAppearance.StatusBar.PhoneTicker" [COLOR="Red"]android:textColor="your text color"[/COLOR] android:layout_width="fill_parent" android:layout_height="wrap_content" android:singleLine="true" />
<TextView android:textAppearance="@style/TextAppearance.StatusBar.PhoneTicker" [COLOR="Red"]android:textColor="your text color"[/COLOR] android:layout_width="fill_parent" android:layout_height="wrap_content" android:singleLine="true" />

Then recompile.
[Android Q&A, Help & Troubleshooting] kxhan15:
Or you could just download and install xposed framework. Thru xposed download xblast tools which has a ticker editor built in
[Defy Q&A, Help & Troubleshooting] GeovaGioohh:
Is possible ntfs suport and usb host in my defy??

Sorry For Bad English
[Defy Q&A, Help & Troubleshooting] Gafanhotz:
Well, a simple search on the forums will explain that.

The response is: No. The locked bootloader don't allow us to flash custom kernels with these improvements.
[Defy Q&A, Help & Troubleshooting] yodawg:
hm Not too sure about that... for some things we don't need to flash a custom kernel, but it is sufficient to compile and load a kernel module... so at least ntfs could be supported? don't know if the hardware supports usb host, and without that, ntfs is a bit useless :P that's just what i think without doing some research.
[Verizon Samsung Galaxy S III] xicewallx:
Maybe this is a samsung thing but if you go to about phone and look up the signal strength the numbers are wrong. I have several apps that will tell you the signal strength and both my droid x and my moms razr report right around the dame numbers (-87) where the gs3 says (-117)

YET if I go to any app it says the same (-83 to -87 is what it usually floats around)
[Verizon Samsung Galaxy S III] switch81:
I'm totally bringing a thread back from the dead here... but I'm experiencing the same thing... I tried the G7 and K1 modems and it still reports funny numbers.

Network Signal Info app gives me: 526271 dBm (ASU:263192)

OpenSignal Maps gives me: -115dBm, -1asu

Settings->about device->status gives me: -92dBm, 48asu

This is all on LTE

Any ideas?

---------- Post added at 12:33 AM ---------- Previous post was at 12:32 AM ----------

Also, I'm running CleanROM 2.5
[Verizon Samsung Galaxy S III] Hulk0069:
Running clean Rom 2.1 my signal is great with the hd radio/modem

Lower is better then my phone signal is great my x2 signal reads 76dBm
[AT&T Samsung Galaxy Note I717] ZPaul2Fresh8:
Which one should I use for use on ATT in America? Thanks.

_________________________________

www.TheShortBusRiders.com
[AT&T Samsung Galaxy Note I717] ManelScout4Life:
UCLF5
[Vibrant Android Development] FaultException:
[font=Roboto,Arial]Arbiter[/font]

The Arbiter kernel is based on the teamhacksung Aries kernel (the stock kernel when you install CM9 on GS1-line phones). Support is only guaranteed for CM9. It appears to work on Team Nyx RC 5 and MIUI as well.

This is currently a baby kernel, it has one thing which is the OC right now. I'll add more stuff like more CPU governors later.. maybe.

Features

OC 1.3 GHz

More later...

Download

Latest 1.0 ---> Download here

MD5: b7747fbabe8d3b1dec668b5e1ce6e19e

Installation

Flash from CWM recovery.

Source

This kernel is 99% open source, you can grab the source off of GitHub from here, put it on your Linux box, and if you have the required dependencies, you should be able to just build.

Here's how to use the build script:

./build.sh # repackages (requires kernel to already be compiled)
./build.sh kernel # recompiles the kernel
./build.sh root # repackages ramdisk from staging/ramdisk/ into staging/ramdisk.img
./build.sh recovery # same as root above but repackages the recovery ramdisk instead
./build.sh root+recovery # does both of the above

I think you get the point. You can mix any of the above arguments by adding "+" in between. First time you run the build script you should pass "kernel" to compile the kernel, else the build script will fail because it's not compiled.

Thanks

* pawitp & teamhacksung
* sixstringsg for hosting
* Mr-Psycho cause I took a look at his kernel build scripts

P.S. This is not the Stock+ kernel me and creeve4 were making, this is forked from that kernel, and contains currently the same changes (OC) but this kernel is mine and will contain more changes later.
[Vibrant Android Development] FaultException:
Changelog

1.0
* First version
[Vibrant Android Development] trailblazerz11:
Looking forward to whats to come xD

Thanks for all that you do for the vibrant community Fault, We appreciate it :)
[Vibrant Android Development] c-pimp:
Awesome, can't wait for this to mature
[Vibrant Android Development] creepinm3:
Awesome, flashing this now... see how it does with a day of usage
[Vibrant Android Development] grose65:
Too late
[Vibrant Android Development] FaultException:
What?
[Vibrant Android Development] serendipityguy:
Great work FaultException, you have been thanked and this puppy has been added to the

Great work FaultException, you have been thanked and this puppy has been added to the Vibrant Kernel Thread.
[Vibrant Android Development] scrizz:
Keep up the excellent work FE.

I'm behind you 110%

:D
[Vibrant Android Development] ancifil:
What is benchmark results? Battery life? Does GPS works fine or only "one-time"?
[Vibrant Android Development] hkfan:
Flashing now
[Vibrant Android Development] N00B_IN_N33D:
Oh yeah? I'm behind him 111%! :p
[Vibrant Android Development] ferhanmm:
Can't tell if trolling or noobing
[Vibrant Android Development] ekeefe41:
Trying to download on my phone, but it is saving as a .htm file not .zip.
[Vibrant Android Development] FaultException:
Just rename it
[Vibrant Android Development] creepinm3:
Did anyone here get a boot hang. I wiped dalvik and cache nothing worked. I will flash 7/7/2012 nightly now and attempt to see if it works.

edit: flashed latest nightly and kernel it worked

edit again: nevermind weird rainbow color lines across my screen doesn't get past CM9 boot animation.
[Vibrant Android Development] FaultException:
Coming from SZ? That's probably why. It's best to go straight from stock CM9.
[Vibrant Android Development] creepinm3:
I went from stock, gave me rainbow lines across screen
[Vibrant Android Development] FaultException:
stock kernel CM9*
[Vibrant Android Development] ekeefe41:
Working great, hard to tell on battery life so far.. been using navigation and had it plugged in often.
[Vibrant Android Development] Xenoism:
Looks very cool :)

I'll have to try this out soon

Thank you for the awesome work
[Vibrant Android Development] FaultException:
Can anyone confirm if this works on AOKP and MIUI?
[Vibrant Android Development] ioancr:
It does work on Team Nyx RC 5.
[Vibrant Android Development] Stevethegreat:
May I ask why is this not the kernel used on mainline CM9 releases? Apart from it's overclocking abilities it seems to be "stock" and even overclocking is conveniently "hidden" only accessible to those willing enough to venture into the settings menus (and even then there's a giant warning against it).

With the above being the case it's not as if having an overclocked version as the main CM9 kernel something that can (or will) affect negatively CM's standards of "purity"... so "why not?"
[Vibrant Android Development] trailblazerz11:
"This is currently a baby kernel.... I'll add more stuff like more CPU governors later.. maybe."

It has just started.. more will probably be added to make it different than stock kernel.

and imo Stock kernel is what it is. Stock, no need for extra features, just stability. Great idea by Fault to give us stock+extras.
[Vibrant Android Development] Stevethegreat:
Yeah but that was -kinda- my point too, the option to overclock does not affect stability negatively, to *actually* overclock does but so does to use the live-oc option offered from NS tools and so many others. I.e. in those it's not your kernel's fault if you brick the phone, the kernel itself is as stable as stock, no?

I'm asking because OC is the only extra feature which I would need over the stock CM9 kernel so everytime I am to install a new CM version I wouldn't like to have to install another kernel as well (I would be happy with what I would have had). And I'm sure many other are like this (it's not as if the OC *feature* destroys the kernel's purity). Hope my point is taken...
[Vibrant Android Development] FaultException:
Yep.
[Vibrant Android Development] jrongi1:
Works with MIUIv4 only hiccup was first install with out any prep it hung @ kernel splash, went back to recovery ran a kernel cleaning script then installed and looking good so far.

Edit: Also noticed that nstools set max clock to 1300 by default.

Vibrant MiuiV4 360° Productions
[Vibrant Android Development] jrongi1:
Just a quick gps post got a lock in fair time after deep sleep. Again on MIUI.

Vibrant MiuiV4 360° Productions
[Vibrant Android Development] FaultException:
Yeah, it was still defaulting to max when I released 1.0
[Galaxy S III General (US Carriers)] gennadiy008:
Just looking an international I9300 ROM development forum, and jealous :crying:, so many amazing custom ROMS like this , and this one, and here for my AT&T model is ...- 2 if you can even call it a "ROM's", -sad. I switched from international SII I9100 which had tons of custom ROMs to I747 for which a cant even download CallRec MOD.

LTE? - thanks, u can keep it! Anyone willing to trade international for I747 ?
[Galaxy S III General (US Carriers)] The_Biz:
The international has been out a bit longer. And you're always gonna see more dev work for an international phone. That's just the way it is. Be patient. It will come man. ;)
[Galaxy S III General (US Carriers)] jgalan14:
Just wait a bit longer, theme section is making a lot progress on theme department, plus we got myn making rom for it too(Idk if you heard about his work but he has done some great things for evo) so is just matter of time, the phone been out for 2 weeks and I think it will be great device for routers and developers
[Galaxy S III General (US Carriers)] gennadiy008:
..AT&T with 2 ROMs, and Verizon with 0 ROMs - 2 most BIG time

Retarded sections ,.. unbelievable, - even to compare to T-Mobile and Sprint with at least 5 ROMs to choose.,

Willing to donate, but ...
[Galaxy S III General (US Carriers)] Ascertion:
Goo Sprint devs! :D
[Galaxy S III General (US Carriers)] jgalan14:
Yup sprint developers are really good Verizon too but the problem now is Verizon is locked but I doubt it will be for long
[Galaxy S III General (US Carriers)] eep2378:
You had to start a new thread for this? Pretty lame. Since AT&T version just came out why don't you return it and buy the international version? Then you'll have nothing to complain about :D
[Galaxy S III General (US Carriers)] RampageRR:
I don't know how you expect there to be a bunch of roms out already. The phone was only available with a pre order, and was just released in stores today. Patience.

A wise man once said, "Settle down, Beavis".
[Galaxy S III General (US Carriers)] nakedninja42:
Exactly, today is the launch day for AT&T. By my count there is 5 ROMs and a lot of devs who just mentioned they just got the phone. Patiences... amazing things are in the works... :highfive:
[Galaxy S III General (US Carriers)] gennadiy008:
Yes, why not?? I think i deserve one ,There is so many MUCH meaningless threads around, and i think this one is not a waist , + unfortunately i cant just "return it", so i offer my week old for exchange right in this thread
[Galaxy S III General (US Carriers)] lopezpm:
Hope you drop your phone. Way to put down the devs on the att side. Take it back to the store and go get the international one.

edit: if you can't return it then sell it.
[Galaxy S III General (US Carriers)] gtuansdiamm:
So you give reasons y the international ver is better and you expect to get a trade for your "inferior" version

This is bad marketing

Besides there will be plenty of toms in no time

Also I personally kepp my phone on stock for at least 2 weeks after getting the phone

Mostly just to see what Sammy expects normal people to deal with
[Galaxy S III General (US Carriers)] rakeshchn:
Honestly the stock Rom is running so good i haven't thought of flashing one yet. Heck good battery life has made me even not to root and debloat yet. But anyway i will root soon just to install adblock and tools like TB. My point is that during initial days of my previous phone which is SG1 there were so many issues like lag, gps, rfs file system etc etc which made flashing roms inevitable. But so far i am really enjoying stock software.

Sent from my SGH-T999
[Galaxy S III General (US Carriers)] tylerdurdin:
List your phone one the XDA market place for sale or trade....someone will take it off your hands.:)
[Galaxy S III General (US Carriers)] uranis:
I see what you mean coming from a nexus on aokp and jelly bean back to touchwiz is a huge blah, but when roms are available this device will be amazing!! Just patiently sitting this through.

Sent from my SAMSUNG-SGH-I747
[Galaxy S III General (US Carriers)] aj8600:
Locked bootloader :(
[Galaxy S III General (US Carriers)] Nickel Dime Bay:
I was actually thinking of trading my intetnational for the att variant. Then I remembered all the developement we have, I'm on MIUi right now. When the att version gets more I'll probably trade, should be soon!
[Galaxy S III General (US Carriers)] Vincent Vegas:
The phone became widely available in the US just a week ago. Give it some time.
[Galaxy S III General (US Carriers)] Narcistic:
Different variants for the us and Canada also hurt and slow the initial development as well
[Galaxy S III General (US Carriers)] w98seeng:
Every time I see people complaining about custom ROMs for the S3 (or any other phone) I get miffed.

Stop *****ing about what other people do or don't do for you. If you want a custom ROM that meets your needs, build one yourself or pay someone to do it.

The people who create these ROMs do so because they love doing it, not because it's their job (Though people do donate to them, I am sure they do not get what creating ROMs like this is really worth).

I see you're on Telus, well the Telus phone only came out 10 days ago, I know because I got one on the first day. How long do you think it takes to make a custom Android ROM for a phone? I have no idea, but I am sure there are hundreds of hours spent on creating each and every one.

Besides, did you get the S3 because of the custom ROMs available for it or because it is the best phone out there right now? This little beast can do things no other phone can dream of and you ***** about custom ROMs.

Ian
[Galaxy S III General (US Carriers)] milleirish:
Dude, most of the devs. Haven't even received their phones yet. The phone can't even be bought in the stores yet. Some of us were lucky and got their preorders sent out and received them. Be patient, if you want a custom Rom that bad, take on the adventure yourself. It takes time and and knowledge to make them, which is why I haven't tried making any. That **** looks confusing as hell, we will get them, be patient grasshopper.
[Galaxy S III General (US Carriers)] bonebeatz1234:
The international version was released pretty much for the entire world accept the United states and thanks to some dip sh$t who thought our phones should run on different frequencies than the rest of the world pretty much screwed us from getting what everybody else gets. Everytime a phone comes out it has to be specially made for the us. The United states is roughly ten percent of phone sells and that's why they don't care if a phone make it here or not.
[Galaxy S III General (US Carriers)] xlazaruzx:
Some people just can't wait. I just rooted and debloated my AT&T S3 and it's good.
[Galaxy S III General (US Carriers)] eep2378:
By my account this thread is just as meaningless as the others. Why can't you return it? Your expectations are NOT real. The device just came out in the last few days. Trust me there will be some major Roms out in the near future.

Also coming from an international phone vs a carrier branded phone is no exsuce to ***** about lack of roms. You bought a AT&T stock phone from Samsung, did you not know that it runs on TW ui??
[Samsung Galaxy Nexus] coldfusionb:
What's the best way to format the internal memory without doing anything harmful?
[Samsung Galaxy Nexus] efrant:
Use "fastboot erase" for the 5 partitions: boot, cache, system, userdata, recovery, e.g., fastboot erase cache

You will obviously have no ROM or recovery, so you will need to reflash.

Note: "fastboot erase userdata" WILL wipe /sdcard.
[Samsung Galaxy Nexus] msedek:
Easier relock and unlock the bootloader that's it
[Samsung Galaxy Nexus] isinisterx:
Easiest: Select all the stuff on your internal sd card, and delete it, then do a factory restore.
[Samsung Galaxy Nexus] efrant:
What both of you are suggesting ONLY erases the userdata partition. It doesn't touch the other partitions at all...
[Samsung Galaxy Nexus] harveydent:
A question (or two): "fastboot erase userdata" is the same as "fastboot erase" but it also includes the sd card partition? and if I use it and flash a new ROM and recovery, the necessary data in the other partitions will also be reinstalled?
[Samsung Galaxy Nexus] isinisterx:
But can data be recovered after this has been done (using my method)?

I'd sold a few things locally and thats how i've done it... is that a safe way?
[Samsung Galaxy Nexus] efrant:
I don't think you can use "fastboot erase" without specifying a partition. It needs to be "fastboot erase <name-of-partition>.

If you really want to wipe your device, you need to reboot into fastboot mode and type the following:

fastboot erase boot

fastboot erase system

fastboot erase userdata <-- this will wipe /sdcard

fastboot erase recovery

fastboot erase cache

No, the data cannot be recovered. But as I said, the kernel, ROM and recovery will still be there. What you are doing is the same thing as "fastboot erase userdata"
[Samsung Galaxy Nexus] isinisterx:
Phew, my heart was beating for a minute there. Thanks for clearing that up.

(The recovery backups are stored on that sd card too right)?
[Samsung Galaxy Nexus] efrant:
:)

Yup, recovery backups are located in /sdcard, which resides on the userdata partition.
[Samsung Galaxy Nexus] kptnk:
Maybe you can help me there, but i think my internal memory is wasted : when i try to flash/wipe or move any file on the phone, using recovery, file manager or while connected to windows, nothing happens ; i mean no files move, and flash or wipe process in recovery are said to be successful, but in fact are not effectiv at all.

My phone is now in boootloop. So i tried to flash a stock image using toolkit, process went fine, but once again, phone wasn't wiped it kept bootlooping.

So do you think tryi'g to wipe using fastbot will work ? Have you ever seen this ? Or as i think i face a hardware problem ?
[Samsung Galaxy Nexus] efrant:
1) Stop using toolkits.

2) Try wiping the partitions as I mentioned above.

3) Then re-flash stock using the steps in the "flash" link in my signature.
[Samsung Galaxy Nexus] ErichMoraga:
I think you have pretty much the same problem I described here...

http://xdaforums.com/showthread.php?p=28571828#post28571828

Writing to the memory card isn't actually committed, effectively making it read-only. My new phone will arrive Monday so I'll be able to perform more comparative analysis then.