yashsingh1/xdaforums huggingface dataset:
[Verizon Droid Charge] burningembers:
Does anybody else's screen have a blue tint to the white's at any angle other than straight on?

I ask because mine does, and my Fascinate does, but it isn't even really noticeable.

I remember when I got my HTC incredible that some had it worse than others so I'm kind of curious if the Charge I have is an overt anomaly or if I'm just being picky.
[Verizon Droid Charge] gerelee:
i've owned the fascinate, the vibrant and now the charge... they all looked 'bluish' to me... especially when you compared the screens to another phone that is not an amoled.
[Verizon Droid Charge] NotATreoFan:
Engadget mentioned this in their review of the Charge. Disable the auto-brightness setting, and dial it up manually. You should see the blueish tint disappear.
[Verizon Droid Charge] gerelee:
the bluish tint never really goes away .. at least in my experience with 3 different samsungs .. regardless of the brightness setting. turning it up all the way helps but it's definitely still noticeable .. depends on whether or not you can live with it :)
[Verizon Droid Charge] NotATreoFan:
I'm planning to pick up a Charge this Saturday, and will be going to the store with a list of "concerns" such as this one. If I can reporduce the blue tint and then make it disappear enough to not annoy the hell out of me, I'll be leaving with one.

Luckily I know the salesperson I'm buying it from, so it will not have the OTA installed when he hands it over. :)
[Verizon Droid Charge] burningembers:
FWIW, I just realized all of my tinting issues were due to the Zagg Invisible Shield I had on it. I realized this after I took the generic brand protector off my Fascinate and realized all the colors popped more.

Yes, OLED/AMOLED/SAMOLED/SAMOLED+ screens have pink or blue tint depending on the angle, but mine was *awful* compared to my Epic 4G, Fascinate, and HTC Incredible.

Zagg screen protector off, Phantom Skin screen protector on...takes a significantly greater angle to cause the degree of tinting issues I was seeing with anything but straight-on.

Much, MUCH happier with the display now :)
[Verizon Droid Charge] DroidXcon:
I actually work in the oled industry , the reason you see a blusish tint is because blue lives the shortest. so to avoid degradation and increase efficiency they optimize the screens using blue as the jump point.

although it is a blue tint it by industry standards is called a cool white. when you increase intensity on the screen you see less of this tint because at the higher points the three colors intensity start to create a more pure white.

you must remember OLED compared to other screen technology is in its infancy, we have developed blue molecules that will live longer with better efficiency when you start to see these roll out in the industry more pure whites will be acheived.

You can complain about blue tint all you want but it is by design so there is nothing you can change.....now with voodoo kernels you can adjust this but you run the risk of color degradation more quickly so dont leave static images on your screen as colors will degrade faster than others and you will see "Burn in " if you will
[Verizon Droid Charge] burningembers:
Oh, I totally understand the blue tint to OLED's, and I'm fine with it. No complaints.

But this was *bad*. Even using the phone in my hand, every slight movement was causing it to flicker from pink to blue to warm tones and so the screen itself looked like it was having a film waved in front of it. It was distracting and awful compared to my other OLED-ish devices.

Lo and behold, it was just the screen protector type I was using. No issues with it now. :D

(I actually prefer cool tones to my displays anyway, so its all good.)
[Verizon Droid Charge] moondrius:
I am comparing 2 Charges side by side and one has a really blue tint and the other has perfect whites. Mine is the one that is really blue. My display is noticeably dimmer then the one without the bluish tint. As much as I hate to do it I might swap it out to see if I get one that does not have the blue tint.

I have used the dock on mine for about 2 weeks nightly. Could have have caused a burn in effect by keeping the clock screen on at night?

Edit: nothing is wrong with the screen. Its only noticeable if you have both right next to each other. If you look at one then the other you really can't even tell. I bought an episode of South Park on media hub and it looks better then my 46 inch Samsung led tv.
[Eee Pad Transformer Android Development] crater:
Anyone have an idea how hard it would be to port this tiamat kernel over to Transformer? built for XOOM and others, and the XOOM hardware is near identical right? Just a thought, this thread has the info and link to the github of the sources.

http://xdaforums.com/showthread.php?t=978013
[Eee Pad Transformer Android Development] andrew53517:
I posted in the thread if he could develop for us and everyone yelled me. I thought it'd be easy too. But I agree. I hope someone could port this because this kernel seems amazing.

Thunderbolt Rooted!
[Eee Pad Transformer Android Development] crater:
Yeah, I was going to PM him, but he has PMs disabled, and I wasn't going to post in the thread because people hate that, me included. There is nothing more annoying in a thread when someone else comes in asking to do this all to their device. While this is a situation where at least the device internals are pretty similar, still not a polite thing to do. The github of his work should be enough for any dev here to port the work over pretty easily I'd think. We'll see though.
[Eee Pad Transformer Android Development] rothnic:
The hardware is fairly similar but they are based on two completely different OEM boards. Transformer=Ventana, Xoom=Stingray.

The Tiamat kernel modificationc could possibly be ported to the transformer kernel, but it isn't as straight forward and simple as you might think.
[Eee Pad Transformer Android Development] jbarns:
definitely would be sweet.. dual 1.6GHZ sounds pretty good:)

Hopefully we get some support soon.. I wish I knew how to do this stuff.
[Eee Pad Transformer Android Development] bigmo7:
I'm not sure what it is but the forum for the Eee pad seem a bit dead tbh, is it just because of limited stock? :confused:
[Eee Pad Transformer Android Development] andrew53517:
I sure hope so. I know R2doesinc is ordering one, he is a great developer. So we have another one on board soon. But I think it is a combination between that and that there are so many choices out there. I hope it picks up soon.. :cool:
[Eee Pad Transformer Android Development] graffixnyc:
I talk to brd all the time. He also hangs out in the asus-transformer irc channel. I spoke to him briefly about of a few weeks ago and he was going to look into it but got busy with tiamat
[Eee Pad Transformer Android Development] egzthunder1:
I know netarchy is currently working on a kernel for the Transformer as he has a repo up and running. In case you aren't familiar with him, he makes some killers kernels for the EVO. Just fyi...
[Eee Pad Transformer Android Development] graffixnyc:
Yeah, he hangs out in the irc channel too. Most of the devs do :-)
[Eee Pad Transformer Android Development] funnycreature:
Now this all sounds sooo exciting!! I bet once the ball starts rolling there will be no stopping it!

Sent from my TF101
[Eee Pad Transformer Android Development] graffixnyc:
I actually think there are a few dev's working on kernel projects :)
[Eee Pad Transformer Android Development] Jocelyn:
Now THIS is refreshing to hear!
[Eee Pad Transformer Android Development] Blades:
I just got this today.. rooted it.. and now I'm flashing a test OC kernel with modded ramdisk (took that stupid ntfs module out of /sbin/ and the insmod in the init.ventana script).... among other things...

so far so good.. yay.. I'm in!

yes!! that was f***n easy.. 1.2ghz... now for more speed..
[Eee Pad Transformer Android Development] psicrest:
Thanks for sharing the kernel.
[Eee Pad Transformer Android Development] Blades:
there is some hardcore douchery going on with sku checks.. I'm chasing variables all over the place.. I give up for the night.. this is like the xoom source, but again fuse data screws us.. I never should've opened this god damn box.. i knew i'd hate it. I haven't used it all.. I prefer my gtab.. argh.. sorry its late.. late late. still want to frisbee it.. :mad:
[Eee Pad Transformer Android Development] freeza:
Can't wait for the ability to OC :)
[Eee Pad Transformer Android Development] silenceforus:
I miss IRC.

And I hope we get some development on this soon. It'd be a shame to see people sticking to products like the xoom, just because the TF is so limited in its availability. We need availability to pick up for this product.
[Eee Pad Transformer Android Development] Blades:
Its not limited in just availability, its limited in 'mod-ability'.. It could just be the product maker following the guidelines for that particular board and making use of 'security' features specific to that board, but its still a pain in the ass. Work was put in to make the end user work harder to be able to customize.

I have the gtab (harmony), Xoom (stingray) , and eeepad (ventana). The gtab is the fastest, the easiest to mod, the hardest to brick.. and the heaviest with the worst screen. The eeepad is the slowest, the worst to mod and the lightest.. guess what .. best screen.

I am typing this on the gtab tho.. and I just got the eeepad today. It'll probably collect dust. Tried to play south park (originally avi/xvid/mp3) converted/muxed to mp4/xvid/aac and the Asus would play it... but volume control was not working it was full blast or mute. My gtab plays xvid avi/mp3 without a hiccup. Any other format I can throw at it too (sans multichannel audio and high profile h264). Its really surprising how far this has come. Since its oc'd every which way, it makes everything else seem very very slow. Only thing I haven't been able to get oc'd yet is emc.

Getting the ability and the clocks setup for the Asus was a breeze. Configuring/adjusting /making sense of all the bits and pieces of dvfs was not. speedo_id is a new one to me, and that seems to be the value that is read from fuse data and locks down max clocks
[Eee Pad Transformer Android Development] bigrushdog:
You guys got Blades and Netarchy on the case. You don't need me lol. I would LOVE to have Netarchy working on stingray.
[Eee Pad Transformer Android Development] jbarns:
I look forward to your development on the eee pad:). I too have noticed the performance is not up to par (to ipad2 you could say) and it won't get used much until it gets OC'd.
[Eee Pad Transformer Android Development] seshmaru:
I thought benchmarks showed the transformer to be faster than the Xoom on stock?
[Eee Pad Transformer Android Development] clamknuckle:
Benchmarks don't always equal real world performance gains. It's pretty easy to make your device murder benchmark programs.
[Eee Pad Transformer Android Development] seshmaru:
There was also an explenation, the transformer's RAM is clocked higher than the Xoom.
[Eee Pad Transformer Android Development] -viperboy-:
The best way to get ahold of the OP of Tiamat (Cayniarb) would be in his IRC channel on freenode, channel name #tiamat. I'm usually hanging out in there with a few other people. I know he has alot of things going on now with all of his work, but it's always worth a shot :)
[Eee Pad Transformer Android Development] Blades:
That's not true. Both have a max of 333mhz and while I have not checked out the Xoom's emc scaling policy, the Asus does not clock the ram @ 333mhz at anything below 816mhz. Here's an excerpt of cpu-tegra.c outlining the details of said scaling.

clk_set_rate(emc_clk, 600000000); /* cpu 816 MHz, emc max */

else if (rate >= 608000)

clk_set_rate(emc_clk, 300000000); /* cpu 608 MHz, emc 150Mhz */

else if (rate >= 456000)

clk_set_rate(emc_clk, 150000000); /* cpu 456 MHz, emc 75Mhz */

else if (rate >= 312000)

clk_set_rate(emc_clk, 100000000); /* cpu 312 MHz, emc 50Mhz */

else

clk_set_rate(emc_clk, 50000000); /* emc 25Mhz */

emc = external memory controller

With the aforementioned issue with the gov not exactly hitting all the clocks under various loads (meaning its either 216 or 1ghz), that's annoying. We either see 25mhz, or 300mhz.

Apparently we either have Elpida or hynix chips ... and from the kernel log mine says

Elpida 8Gb 333 Mhz memory found

there are also possibilities for it to say 4gb.. I honestly don't know what that's on about, but its probably a single chip from a stick of ddr. Although I was not aware that ddr2 was available in 8gb.

So, what's with the 600mhz emc and thus 300mhz memory? I don't know.. My gtab reports the memory at 333mhz, tf reports it as 333 but clocked at 300. Nice huh?

And with both cores on, maxed at 1ghz, cpu0 is averaging 18-20% usage. And im not even using the damn thing. Logcat that intensive huh? Thanks Asus.
[Eee Pad Transformer Android Development] Blades:
It really doesn't help that this source is for 3 different models. There is all kinds of silly sku checks going on. I probably have some voltage stuff wrong. Its the worst when the kernel compiles fine and the device just straight up won't boot. At least there is the loud ass camera click and speaker pop to verify the kernel booting. Whem does that happen, the sku crap happens very early, like 4 seconds in. I hate this. I'm going to start over, set everything to speedo_id 2 specs and see whats what. That way i can leave voltage stuff be for now. Can someone explain process_id? Process_id 2 makes no sense to me.. Is anyone else working on this?

At this point, I'd rather tape a keyboard to the bottom of a Xoom.
[Eee Pad Transformer Android Development] seshmaru:
Netarchy is working on a custom kernel.
[Eee Pad Transformer Android Development] netarchy:
Speedo ID determines which set of freqs is used in tegra2_dvfs, in the case of the TF, it's the second batch (speedo ID 1). Process ID is just like on the xoom (ie; 0,1,2,3) with the tiers.

SKU ID looks pretty easy to deal with, the only spot I've noticed it doing anything that would interfere with clocking up the cpu is in tegra2_clocks where it controls the rate limits (SKU on TF is 8), 3 entries at 1ghz by default that can be changed, freq table to extend is 1p0GHz, as well as extending the pll_x freq table if you want to clock higher than 1.2.

Also a few other entries in tegra2_clocks that need to be bumped to a higher max than 1.2ghz.

The confusion sets in because they have tables to cover 3 different configurations, which is a bit annoying.

At the moment I'm toying with 1.4ghz. Not quite stable atm, but then I haven't had time to really dive in. Planning to dedicate time today to work on it more.
[Eee Pad Transformer Android Development] Blades:
Yes, I have gotten that far.. But thank you very much for the sanity check.. The three speedo_ids were confusing at first, but its all very easily sorted.. In the future, I'd like to narrow it down for just the TF101... Just to make things neater - but thats quite the task.. I've also looked for any way to read out the SBK.. or at least provide some information on any part of the 'equation'..

What I find hard to understand are the tiers in general.. specifically #2.. Just what they do and how they work.. If there were no reference values, I'd probably be lost.

Also, the voltage constraints for the board - It looks like cpu_vdd is set at 1500. Which is strange.. but maybe its just something thats default on a ventana dev board.

what are the values noted in bold? The size of the table or where in the cpufreq table to set the min/max freqs for throttling?

static struct tegra_cpufreq_table_data cpufreq_tables[] = {

{ freq_table_1p0GHz, 2, 6 },

{ freq_table_1p2GHz, 2, 7 },
[Eee Pad Transformer Android Development] netarchy:
Items in bold are the thermal throttle limits, they correspond to the numbered entries in the freq table. It's found in clock.h.

struct tegra_cpufreq_table_data {
struct cpufreq_frequency_table *freq_table;
int throttle_lowest_index;
int throttle_highest_index;
};

I'm not entirely clear on the tiers yet myself, we appear to be lacking decent datasheets for the tegra2.

SBK Looks like it's locked down, after taking a quick-ish look at the fuse stuff, not sure what luck we're gonna have there. I could be wrong ofc.
[Eee Pad Transformer Android Development] ivan.volosyuk:
Does SKU has anything to do with hardware? I flashed US firmware together with kernel on my TW device and it seems to work fine.
[Eee Pad Transformer Android Development] Roach2010:
I've not looked at the kernel source but I assume that the SKU's being mentioned here are nothing to do with locations but rather the three Asus tablet versions, TF101 SL101 and JN101, The Transformer, The Slider and the 'other' one.

Let's keep the thread OT though please as it's hopefully starting to go somewhere.
[Eee Pad Transformer Android Development] Buembel:
That would be just great! Let it be :D
[Eee Pad Transformer Android Development] psicrest:
I wish someone could put some guides and download of the stock asus kernel source. I would love to tinker with the kernel even if i don't know what im doing. But im a very good copy and paste programmer. LOL!
[Eee Pad Transformer Android Development] Blades:
Heres one odd thing I've been wondering, why make conservative the default scaling gov in kconfig but then set it to interactive during init script? I have interactive as the default gov in the kernel, and it seems to be ... terrible... favoring scaling_min_freq 90% of the time.

Ok check this out.. worse than i thought.

/data/local # tcpsvd: end 1967 exit 0

/data/local # cd /sys/devices/system/cpu/cpu0/cpufreq/

/sys/devices/system/cpu/cpu0/cpufreq # cat scaling_cur_freq

216000

/sys/devices/system/cpu/cpu0/cpufreq # cat scaling_min_freq

760000

/sys/devices/system/cpu/cpu0/cpufreq #

It seems like i have to set this device to 1ghz min/max just to get it usable. Anyways, light sensor and battery info really need to stop crapping all over the kernel log.. thats something achievable...
[Eee Pad Transformer Android Development] netarchy:
http://twitpic.com/50q8yg

:D
[Eee Pad Transformer Android Development] The-Kevster:
Awesome!!!
[Eee Pad Transformer Android Development] corwinmortac:
i can feel it.....its sooooo close....whats that you say....Netarchy has done it again :-)
[Eee Pad Transformer Android Development] urundai:
Way to go, Netarchy

Another feather in your cap. Looking forward to the release ;)
[Eee Pad Transformer Android Development] Blades:
Damn. my kernel does not boot.. There again I'm attempting to overclock everything.. possibly too much.. is your pclk at a max of 150? or is it left at 120?

Could you just link me up to those two ever important dvfs and clocks files? I want to see how far off i am..

damn.. just realized i didn't have to start from the 'stock' asus kernel source.. :(
[Eee Pad Transformer Android Development] netarchy:
I'll have a commit on my github in a lil bit so you can see how I did it.
[Eee Pad Transformer Android Development] Blades:
I think I might know how I borked one thing or another.. do the cpufreq tables need to be a certain length? It doesn't seem like it. but I know that on the gtab, you can only have a certain # of freq steppings.

I've gotten my kernel to get past the camera click. heh.. I'm clearly 'doing it wrong'.. Thanks so much..

commit up yet? Oh the irony.. I just got everything to boot stable.. I'm still missing my 400mhz gpu clock tho. :( WAH!
[Eee Pad Transformer Android Development] Blades:
Oh and its much nicer with al3000.c edited to not be such a chatty catty in the kernel log. Have you figured out temp conversiom of batt info? I don't think its in kelvin! Unless my batt is 65° F

it does mention kelvin to celsius.. cept its probably wrong.. The asus modded section of the battery source has provisions for the keyboard dock and what you'd expect as well as a 'Car Mount'.. Wheres that at, this would make one hell of a nav system. heh.
[Eee Pad Transformer Android Development] Blades:
I think you forgot to set the speedo_id 'enforced' core and cpu nominal millivolts.. they are still at stock settings. I got 1.6 to work, but its slightly unstable. Will be trying 1.504 kang'd from Xoom setup.

just got avp (sys bus) & vde (video decoding engine) up at 300mhz.. along with gpu at 400.. pclk is thus now at 150mhz as well.

240->300 - vde/sys

300->400 - gpu

120->150 - pclk

btw.. the device -seems- to have a ~50fps limit.

btw.. perhaps keeping the nominal mv at stock settings was a good mistake.. or perhaps intentional.. I can definately tell where the cpu is now.. lower right corner if held in landscape..
[Eee Pad Transformer Android Development] Buembel:
will there be any way to get USB ethernet working as it is in the Xoom Tiamat? :eek:
[Eee Pad Transformer Android Development] Blades:
There is a usb eth driver built into the kernel, its strange as i think it may be the same model that my gtab's dock uses. What do you have? I need to get the keyboard dock when it becomes available for purchase. I have a feeling the VL600 drivers 2.6.39 will work, (lg vzw 4g).
[Eee Pad Transformer Android Development] Buembel:
well I would really like to charge my old Touch HD while tethering 3G over USB :)
[Galaxy S I9000 Q&A, Help & Troubleshooting] rcb07:
Hi everyone. I've had MIUI installed on my phone during 2 days now.

I have this problem with the sms system, whenever i receive a message it appears like one i sent and when i send a message it appears like a message i received and the message notification sounds.

Help please!
[Galaxy S I9000 Q&A, Help & Troubleshooting] azzledazzle:
i find it hard to understand what you mean??

are you referring to the message conversations ? like message bubbles ?

and as for the notification sound, do you mean it makes the message tone after the message has sent ?
[Galaxy S I9000 Q&A, Help & Troubleshooting] rcb07:
Yes, in the conversation screen, my messages appear like the ones i received and the ones i actually received appear like the ones y sent. It's kinda weird.

And when i send a message it does play the message tone.

Hope it helps...
[Acer Iconia A500] gunnyman:
Only thing I've done is root with Gingerbreak.

Anyone else seen random lockups? Mine's frozen twice today. Do I have a dud?
[Acer Iconia A500] gammaRascal:
It's unlikely it's a dud if lockups are the concern. (though one shouldn't necessarily rule that out as far as HW issues are concerned - bad ram, flaky cpu, loosened solder etc)

But it does happen from time to time. Ideally, try and stick with Honeycomb apps (or those that have recently been updated to work on HC) and definitely do not install any 'questionable' apps from 'shady' sources.

If you can rule those out as not being the source of the instability then look at the 'market' apps you've installed - it's not unheard of for free or paid apps from the Android Market not playing very well at all.

Not everybody should be coding.
[Acer Iconia A500] gunnyman:
oddly enough I unrooted and my Tab got more stable.
[Galaxy S II General] sindrefyrn:
Kies says the update files for my phone are:

PDA:KE2 / PHONE:KDJ / CSC:KE2 (NEE)

I'm unable to update through Kies, but I can through Odin. Any way I can get those update files?
[Galaxy S II General] Intratech:
Yes you download them from here. Use search function.
[Galaxy S II General] sindrefyrn:
Hey and thanks for your reply. I have been searching although I didn't find exactly those files, that's why I posted asking for help. :)
[Galaxy S II General] Intratech:
Ok, I've downloaded and decrypted it for you. Now uploading. It will be in the thread in the dev forum. :)
[Galaxy S II General] Intratech:
Ok, it's been added to the thread in the Dev Forum under the KE2 section
[Galaxy S II General] sindrefyrn:
Thanks alot! :D
[Galaxy S II General] hanhav:
Thank you! Been looking for that NEE-version.
[Galaxy S II Q&A, Help & Troubleshooting] eddie21:
Running exe getting ERROR 1152 error extracting :(......help!

(win xp sp2)
[Galaxy S II Q&A, Help & Troubleshooting] turborider:
try Run As Administrator
[Galaxy S II Q&A, Help & Troubleshooting] eddie21:
I am set as Administrator