yashsingh1/xdaforums huggingface dataset:
[Eee Pad Transformer General] ToddW2011:
When clicking the power button twice, the screen flickers (on press #2) but remains off. The following is emitted:

05-20 10:52:20.800: DEBUG/PowerManagerService(127): @PowerManagement: Sleep state requested, reason:2
05-20 10:52:20.800: DEBUG/PowerManagerService(127): @PowerManagement: Screen Bright {true -> false}
05-20 10:52:21.100: INFO/power(127): *** set_screen_state 0
05-20 10:52:21.100: DEBUG/SurfaceFlinger(127): screenshot: sw=230, sh=143, minZ=0, maxZ=21010
05-20 10:52:21.100: DEBUG/PowerManagerService(127): @PowerManagement: Screen turned off mScreenOnTime=1700988ms Battery<C,V>: <96,8>
05-20 10:52:21.100: DEBUG/PowerManagerService(127): @PowerManagement: Acquire UWL 'sleep_broadcast' flags [partial] refcount=1
05-20 10:52:21.110: DEBUG/SurfaceFlinger(127): About to give-up screen, flinger = 0x135fc8
05-20 10:52:21.120: DEBUG/SurfaceFlinger(127): screenshot: result = OK
05-20 10:52:21.130: DEBUG/PowerManagerService(127): @PowerManagement: sending ordered bcast for ACTION_SCREEN_OFF
05-20 10:52:21.130: DEBUG/WifiService(127): ACTION_SCREEN_OFF
05-20 10:52:21.140: DEBUG/AlarmManager(127): Added alarm Alarm{4098c8e8 type 2 com.google.android.gsf} type:ELAPSED_REALTIME_WAKEUP when: After 0h:4m:59.0s
05-20 10:52:21.150: DEBUG/PowerManagerService(127): @PowerManagement: Release UWL 'sleep_broadcast' flags [partial] refcount=0
05-20 10:52:26.190: DEBUG/dalvikvm(223): GC_EXPLICIT freed 77K, 19% free 15652K/19143K, paused 4ms+2ms
05-20 10:52:46.030: INFO/power(127): *** set_screen_state 1
05-20 10:52:46.030: DEBUG/PowerManagerService(127): @PowerManagement: Screen Bright {false -> true}
05-20 10:52:46.030: DEBUG/PowerManagerService(127): @PowerManagement: Screen turned on mScreenOffTime=24929ms Battery<C,V>: <96,8>
05-20 10:52:46.030: DEBUG/PowerManagerService(127): @PowerManagement: Acquire UWL 'sleep_broadcast' flags [partial] refcount=1
05-20 10:52:46.040: DEBUG/WindowManager(127): readLidState, sw:1
05-20 10:52:46.140: DEBUG/WindowManager(127): adjustConfigurationLw, config:{ scale=1.0 imsi=0/0 loc=null touch=3 keys=2/1/1 nav=1/1 orien=L layout=0x10000014 uiMode=0x0} mLidOpen:1 config.hardKeyboardHidden:1
05-20 10:52:46.180: DEBUG/PowerManagerService(127): @PowerManagement: sending ordered bcast for ACTION_SCREEN_ON
05-20 10:52:46.180: DEBUG/WifiService(127): ACTION_SCREEN_ON
05-20 10:52:46.190: WARN/TestFlashPlugin(786): support: true
05-20 10:52:46.220: DEBUG/PowerManagerService(127): @PowerManagement: Release UWL 'sleep_broadcast' flags [partial] refcount=0
05-20 10:52:46.470: DEBUG/SurfaceFlinger(127): Screen about to return, flinger = 0x135fc8
[Eee Pad Transformer General] EP2008:
I wish I understood what that stuff means Todd. I should note that for me, this problem only happens in the browser. I have Flash "always on" and it seems to only happen when I'm viewing flash content. I do have auto brightness on with a 5 minute timeout on my device.
[Eee Pad Transformer General] ToddW2011:
No worries. I'm glad others have the issue but when the wife finds out I've got another "bleeding edge" device it's going to be trouble! She still hasn't forgiven me for the Nokia N800 thing...
[Eee Pad Transformer General] ToddW2011:
One thing that makes this less hairy is the handy Eclipse'd devkit. I *really* wish RIM had the brains to release their NDK in a similarly slick manner. We have a Playbook in the office and, while fun, can't do much for us right now.
[Eee Pad Transformer General] ToddW2011:
Another report: http://www.transformerforums.com/forum/asus-transformer-help/387-browser-problem-black-screen.html

Hopefully cross-pollinating some links will improve the search results on this problem. I wasn't able to Google any the first time around.
[Eee Pad Transformer General] UKseagull:
Good find!

Sent from my HTC Desire
[Eee Pad Transformer General] ToddW2011:
I gave up on trying to solve it, unfortunately. :mad: I returned it and my replacement arrived today. Hopefully I will be one the blissful many who only have to deal with market issues and FCs! Looking forward to trying out GEMRB and Planescape on it. :D

Cheers,

Todd.
[Eee Pad Transformer General] PuerkitoBio:
Don't want to hijack the thread, so you can PM me the answer (I did not PM the question because, well, when you don't expect a PM, it may go unnoticed for a while!), how did the RMA process go? Did you RMA to Asus or the store? Delay? Shipping fees? Will probably do the same due to unresponsive touchscreen.
[Eee Pad Transformer General] fernando nogueira:
Expectations...

I had so high expectations regarding this tablet and after seeing some posts in this and other threads i guess ill keep my folio for now and perhaps consider buy an ipad 2,never was an apple fan ,on the contrary but i'm really tiered of this tablets with bad build quality and tons of bugs i just want something that works for once...

I really enjoy tweak with the devices and all it gives me a lot of occupation in the spare time and i have lot's of respect for every one in the forums expecially developers but i think android is not mature enough and also i have my doubts about tegra 2 processors...
[Eee Pad Transformer General] EP2008:
Fyi. I ju got the dim of death on the Acer A500! So its not a Transformer problem. I hope Honeycomb 3.1 fixes this.

Sent from the Acer A500 while my Transformer gets fixed :(
[Eee Pad Transformer General] b1ackplague:
3.1 hasn't fixed it for me.

Sent from my TF Decepticon
[Eee Pad Transformer General] EP2008:
Is it only happening in the stock browser? Both my transformer and the A500 get it ONLY in the stock browser.

Sent from the Acer A500 while my Transformer gets fixed :(
[Eee Pad Transformer General] PuerkitoBio:
Not sure if what I have is officially the "dim of death ", but every once in a while the screen will just turn completely black (cannot even slightly see the home screen) with a high-pitched, barely discernable sound that lasts no more than a second. I press power once, screen stays black. Press power again, lock screen comes on. Which makes me believe the bug doesn't turn the screen off, but turns brightness to 0 (I'll have to test setting the brightness with my dock next time) .

It seems to happen mostly in portrait mode, with apps having a white background. I'm not using auto-brightness, too low for my taste.

Forgot to mention, for me this bug happens in other apps, rarely (if ever, don't remember) in the browser.
[Eee Pad Transformer General] b1ackplague:
Mine isn't directly related to the browser. It doesn't matter where i'm at in the system be it settings, browser, in game, home screen, if I turn the brightness up past 50% the backlight shuts off. Sometimes I'm able to just press the power button once then again to show the lockscreen and it works fine but sets the brightness to 0. Sometimes though I get it to where it just flickers when i press the power button. I think i'm going to RMA it within the week.

The crazy thing was that, in the first 2 or 3 days (both stock and rooted w/ prime), i could change the brightness to any level and it would be fine. Then, all of a sudden, it stopped working correctly.
[Eee Pad Transformer General] b1ackplague:
So today I flashed clemsyn v4 kernel for HC 3.1 and it seemed to have partially solved my issue. I can set brightness to Max and l, as long as I don't open quick settings, it will stay there. If I touch the quick settings with full brightness the backlight shuts off but a lock then unlock will allow to come back on every time.

Sent from my TF Decepticon
[Galaxy S I9000 Q&A, Help & Troubleshooting] reco1:
hello i am an arab galaxy s user and just instaled the new 2.2.1 jpjm and i found that there is a lag fix calld vodoo which dosent require the phone to be rotted my queston is will instaling vodoo kernel void my waranty and if yes is there any way i can lag fix without voiding the waranty ? since i have the mobile sine 4 months and i dont want to void my waranty . thank u for your concern
[Galaxy S I9000 Q&A, Help & Troubleshooting] beerdaddy:
I'm pretty sure there is know way around it. If you want lagfix you will void your warranty.

You can find a stock kernal and keep it safe in case you need to claim warranty repair, that way you can flash your stock kernal before sending it away for repair.

Hope that makes sense??
[Galaxy S I9000 Q&A, Help & Troubleshooting] reco1:
first, thank for your reply.second what u mean is that i can keep the original kernel so i reflash it when i want the waranty so falshing vodoo dosent void the waranty as i can go back to the orignal kernel any time leaving no trace right ? and by the way which is the best lag fix out there for 2.2.1.
[Galaxy S I9000 Q&A, Help & Troubleshooting] beerdaddy:
Yeah that's right if you want to change anything make sure you make a back up first or download one. If you search on here you should find the stock Kernal.

The only lagfixes I have used is RyanZA's OCLF (one click lag fix) and Supercurios Voodoo lag fix. I found the best to be Voodoo and it does not require root. It also has support for Voodoo sound control (this does require root) which really unlocks the potential of your headphone amp.
[Galaxy S I9000 Q&A, Help & Troubleshooting] bekh:
Idea for you

HI

CHECK FOR YOU FIRMWARE ON THIS WEBSITE

http://www.samfirmware.com/fwandroid.htm

IF YOU FIND IT....:)

GO FOR LAGFIX.......OCLF

WHEN YOU NEED TO GO TO SERVICE CENTER, YOU EITHER

1- FACTORY RESET AFTER BACKING UP YOUR DATA INCLUDING FORMATING INTERNAL SD

THIS SHOULD REMOVE THE LAGFIX......IF NOT... :(

RE IMAGE THE DOWNLOADED FIRMWARE FROM WEBSITE ABOVE.

IN CASE YOUR PHONE IS DEAD......:) NO BODY WILL KNOW ABOUT LAGFIX

NOTE: YOUR OWN RESPONISIBILITY

ENJOY
[Galaxy S I9000 Q&A, Help & Troubleshooting] radeon_x:
Worst suggestion ever. OCLF is outdated and dangerous.

If you're worried about your "warranty" then don't both applying any file system conversion (aka lagfix). And the reality is that on a 2.2.1 the benefits of using EXT4 as a lagfix are questionable at best - the stock RFS file system is pretty fast as is.

If you want to try for yourself though, the easiest way is to flash the Speedmod kernel and apply the lagfix from the recovery menu.

The instructions are here: http://touristinparadise.blogspot.com/2010/11/samsung-galaxy-s-how-to-install.html

Read, pay attention, and it's all very safe.

After you install, enter recovery by pressing (from power off) Volume-Up + Home + Power and follow the menu to the lagfix options.
[Galaxy S I9000 Q&A, Help & Troubleshooting] reco1:
thank u for your help every one
[Galaxy S I9000 Q&A, Help & Troubleshooting] PhoenixFx:
Yes DO NOT use OCLF.

IMO 2.2.1 and later ROMs don't really need a lagfix like previous versions. They work pretty smooth without one. From 2.2.1 JPY onwards I never used a lag fix. Do you really feel the ROM slow and laggy ?? if not, then why fix something that isn’t broken :p ?
[Atrix 4G Q&A, Help & Troubleshooting] BluePlanetMan:
Hey All,

Has anyone attempted to access the Fingerprint sensor? I know that Moto has not released the dev kit for this yet (and may not), I am wondering if we can get a look at the files and determine how to program to it on our own. Any ideas?

-BluePlanetMan
[Atrix 4G Q&A, Help & Troubleshooting] roharia:
I'm no (Android) dev but what could they even do with it? Not being an ass, just wondering.
[Atrix 4G Q&A, Help & Troubleshooting] Mr. Clown:
Thread moved.
[Atrix 4G Q&A, Help & Troubleshooting] WiredPirate:
Lock apps individually or require fp for access to sensitive files.. First thing I thought of anyways..
[Atrix 4G Q&A, Help & Troubleshooting] jeffc:
My understanding is its an Authentec sensor and that Moto has to have an agreement from that company to allow access to the sensor driver/api.

I've been in the fingerprint industry for 7 years and Authentec can be a pain to work with. They are very stingy about their fingerprint algorithm. They make very good sensors but I’ve never been thrilled about their SDKs.

Anyway, a fingerprint device isn’t like most input devices. Just being able to talk to the device driver isn’t enough because without the algorithm you really can’t do much. Fingerprint algorithms are not simple i/o, they are complex image comparison and fingerprint minutiae measurement and probability matching.

Now, I will say that because the locking app calls the fingerprint driver you could probably analyze that code and see the call structure for the fingerprint functions and copy that. If its like on the Windows Authentec drivers it shouldn’t be all that complicated. There are functions for sampling and storing the fingerprint templates, and then for verification of live fingerprints along with threshold settings for tolerances (how strict the match should be, for example 70% confidence).

My company is registered with Motorola and I’ve requested they open up the FP api for us. If they do, I’ll be one of the first to jump on it and I’ll drop a note here.
[Atrix 4G Q&A, Help & Troubleshooting] ChongoDroid:
Interesting... I'll check this thread again lol
[Atrix 4G Q&A, Help & Troubleshooting] Dave__C:
Please check the Motodev site for recent news on this topic.
[Xoom Q&A, Help & Troubleshooting] Brenardo:
When I got up this morning the option to update was available so I went for it. Immediately I realized my mistake because I had rerooted the Xoom last night and of course the update failed. Now I have returned completely bak to stock expecting to be able to update. No dice.

I have tried changing the date to pull the option to update again still no dice. Just wondering if there are any other options to pull this update again or do I just have to wait?

Will it show back up?
[Xoom Q&A, Help & Troubleshooting] lordao:
I went back to stock and no sign of the update either. guess we will just have to wait.

Lordao
[Xoom Q&A, Help & Troubleshooting] Brenardo:
I spoke with a VZW Tech support Rep tonight and was told that the devices are updated by device ID #'s. I was told that since I missed the update that if I did not receive the update by midnight tonight then it probably wasn't gonna happen.

I hope like hell he is wrong and I feel like chances are he is. But he got me just that much more nervous about loosing the chance to get the update yesterday morning
[T-Mobile LG G2x] mapin0518:
Haven't tried it yet, but it looks hopeful ! Thanks to Paul.

http://android.modaco.com/content/software/339390/r1-12-may-google-video-talk-installer/
[T-Mobile LG G2x] mapin0518:
No go. Just tried it and it didn't work in neither CM7 #16 nor stock 2.2.
[Eee Pad Transformer Q&A, Help & Troubleshooting] K900:
So, did anyone try hacking 3.1 on the TF? Mine is still preordered, but I want FLAC playback badly :)
[HTC Incredible S] mazinya:
When ice cream sandwich will be out, will HTC roll out the update to the IS also?

Or only the sensation is going to enjoy the new OS?
[HTC Incredible S] vido.ardes:
No one has said anything about any device, it is far to early to speculate
[HTC Incredible S] RellikZephyr:
Is Sensation built on ice cream? I didn't think so, first I've heard of it

New version of sense, but don't think new version of android

Rellikzephyr
[HTC Incredible S] mazinya:
I didnt mean to say that the sensation is built on ice cream. I meant that because sensation is the 1st dual core phone of HTC and ofcourse their flagship phone, then i was asking if when ice cream is out, HTC will update the sensation with it and not their other devices also
[HTC Incredible S] RellikZephyr:
Ah righto

Yeah I think they will definitely update it, how long it might take is the real question. Will it be quick or not

Rellikzephyr
[HTC Incredible S] NardVa:
f the Nexus S gets Ice Cream Sandwich, which it will, I'm pretty sure the Incredible S will get Ice Cream Sandwich since they have similar specs.
[HTC Incredible S] LeanNSupreme:
I wouldn't even think about Ice Cream Sandwhich when HTC hasn't even pushed out Gingerbread to all the Incredible S's.
[HTC Incredible S] hussainmushahid:
only time will tell, HTC's gone slow.
[HTC Incredible S] doctorsax:
If anything, HTC is faster than it used to be. I waited 8 months for a 2.1 update on my Hero from the first announcement to actual delivery. It's been less that half that for the IS.
[HTC Incredible S] MissMuffitt:
Does anyone know if there has been any news about ICS and the IS?

I am hoping that the update might fix my random reboot problem I have with my IS
[HTC Incredible S] System92:
Even if HTC doesn't give official support for it (Ice Cream Sandwhich), 3rd party developers such as CyanogenMod would probably port it over. Since the Nexus S will surely get the OTA update, it's a good guess that the Incredible S would be able to run it as well.

My $0,02.
[HTC Incredible S] itsbeertimenow:
There is no way in hell we'll get ics, these phones were never designed to run anything over gb and sense 3.0. From what we've seen from our development teams it will be ported over from another handset providing that something with similar specs gets the update.
[HTC Incredible S] incrediblealex:
I dont understand why you would wait 8 months for HTC to release the update when you can get now?

HTC IS is still on 2.3.3 and why hasn't it been updated to 2.3.7?
[HTC Incredible S] System92:
Well I can't talk on the behalf of HTC, but I can only say that I wasn't the one waiting for them... I'm rockin' on 2.3.7 :D

And plan to be rockin' on 4.0 when the time comes ;)
[HTC Incredible S] scoobysnacks:
Hardly any phones have been updated to 2.3.7...

Only nexus phones afaik
[HTC Incredible S] incrediblealex:
I thought that the android updates were like the IOS ones where they added features and patched bugs. So you should be on the latest firmware?
[HTC Incredible S] scoobysnacks:
It doesn't really work like that..

2. 3.7 was mostly about adding nfc chip capabilities
[HTC Incredible S] shiningarmor:
are you trying to jump infront of time with a time machine? even nexus prime hasn't been announced yet and now you're already wanting to know whether incredible s gets ICS.

take a chill pill, we'll all know when time comes.
[HTC Incredible S] FDPM:
I've been with HTC device since 2001 (my old Wallaby....), but I'm really annoyed by HTC behaviour: instead of releasing a phone once a week they should really take care and support their devices and their customer.

I became very lazy and I haven't yet installed a custom rom on my IS (yet), but thanx God, there are people like the CyanogenMod team that helps us keeping our devices up to date.

Thanx folks.

I do not think the problem is whether the device was designed for ICS or not. It's just too expensive to build, test and support all the devices they are putting into the market.

Regards,
[HTC Incredible S] Raithmir:
I don't know why people are moaning so much, what other phones have official ICS right now? That's right, just one.

Have patience, HTC are one of the better companies with regards to updates. Samsung are terrible.
[HTC Incredible S] sabret00the:
If you've been following the announcements from HTC, you'll know that we won't get an official ICS update. Install CM9 when it comes out or wait for your upgrade.
[HTC Incredible S] Raithmir:
Link? I know the IncS wasn't in HTC's list of phones to get ICS in the first wave, but I've not seen anything that says we definitely won't be getting it eventually.
[HTC Incredible S] RicarduZonta:
It has already received a froyo to gb update after it came out. Now we have 2.3.5 and sense 3.0 coming in december. I am grateful, not being greedy, I think this is plenty of love from htc and htc might think the same...

Personally I don't expect ICS coming at all.

http://www.htcinside.de/htc-beschenkt-uns-mit-updates-im-dezember/
[HTC Incredible S] katu2006:
I agree with you...HTC has been providing updates and 2.3.5 is good enough for this phone. Honestly, ICS is not that fantastic from what I've seen on the web.

Also, keep in mind that the new OTA update will upgrade the Hboot as well, so Revolutionary/Alpharevx won't work anymore...
[HTC Incredible S] st.matt:
It's not entirely unlikely that they would do an ICS port.. There are many similarities between the 7x30-based devices by HTC so they could port it to all of them without too much hassle.
[HTC Incredible S] System92:
CM9 progress report:

http://www.cyanogenmod.com/blog/cm9-progress-update

At one point they mention that they will try to port over to CM9 all devices currently supported by CM7.
[HTC Incredible S] Splux:
"The first devices (besides the Nexus S, which you can already get from Koush’s section on ROM Manager) that we’ll have ready will mostly likely be devices based on OMAP4, MSM8660/7X30, and Exynos."

7X30, isn't that the same as in the IncS? :D

Or am I just dreaming? :(
[HTC Incredible S] incrediblealex:
Yeah the incredible s is 7X30 :D
[HTC Incredible S] colgate13:
No, it has a MSM8255. The Desire Z has 7230, which is similar but slower.
[HTC Incredible S] Splux:
Since I got two different answers, and not as tired as last time I looked it up;

http://tiamat-dev.com/7x30-changes/

Our device is listed there, so we should have the 7X30. I suspect that they have not listed our device under the wrong kernel... :D

Sometimes I wonder why I just didn't google it at the first place, lol.

*edit*

http://chromloop.com/2011/11/what-android-devices-can-be-updated-to-icsice-cream-sandwich/

Is that site trustworthy?
[HTC Incredible S] P1n3apqlExpr3ss:
They dont mention the sensation XE or XL or the Amaze 4G. I honestly dont see the Salsa or Desire Z being popular enough to get the update
[HTC Incredible S] Splux:
Hopefully there's a bit of truth...

Well, I'm going to wait for the next CyanogenMod instead, and hope that we have the 7x30 and nothing else :D
[HTC Incredible S] colgate13:
Strictly speaking, my post above was correct and that site you are quoting is wrong. The Incredible S has a 8255. So do the Desire HD and Desire S. Phones like the Desire Z have a 7230. Now the chips are very similar so draw whatever conclusions you will.

https://developer.qualcomm.com/device/htc-incredible-s

https://developer.qualcomm.com/device/htc-desire-z
[HTC Incredible S] Splux:
Awh, :(

Then I guess we'll have to wait for cm9 a bit longer.
[HTC Incredible S] uggies:
There is a port

but its too laggy and not customisable enough..
[HTC Incredible S] P1n3apqlExpr3ss:
Even this one? http://xdaforums.com/showthread.php?t=1377828

I find it to be much better then the first one
[HTC Incredible S] vido.ardes:
The actual chip in a Incredible S is an MSM8255. As far as build targets are concerned in the kernel, it's a 7x30. Don't ask me why, 'cause I don't know why, but that is the case. The vivo is a 7x30, but with overrides in the code to cater for the fact it is actually a MSM8255.

In short, I believe the CM message about 7x30 includes devices such as the Incredible S and Desire S
[HTC Incredible S] unknown2011:
wait for the cm9 ~ flash rom is easy for incredible s i think.. as i did it quite smooth
[HTC Incredible S] System92:
Thanks for sharing that link! Will definitely give it a shot tonight.
[HTC Incredible S] Splux:
@prophet: then we should be included in the first releases of cm9?

Or?
[HTC Incredible S] joshi101:
Facebook

Does anyone know how to get facebook intergration working on the ICS beta 1 build ?
[HTC Incredible S] nsg86:
Without sense,there are no facebook integration,ICS beta build is aosp

for your information ..you can get normal Facebook for android though..
[Galaxy S II Themes and Apps] vimto25:
Hi does any1 no if htc sence clock and weather widget work on SGS2? if so where can i find it?, if not anyone no of the best looking widget thats identical to it?

thanks
[Galaxy S II Themes and Apps] MrDeacon:
Without any doubt, "Beautiful Widgets". There are tons of Sense themes to this set of widgets.
[Galaxy S II Themes and Apps] vimto25:
yeh i did notice that but didnt see any in there that look identicaly the same, would there be a apk for the proper htc sence widget that would work on our sgs2?
[Galaxy S II Themes and Apps] MrDeacon:
I personally use the SuperClock with SuperSense theme. Looks very good and "sensy" to me. :)
[Galaxy S II Themes and Apps] turborider:
here is a video and might help u install it http://youtu.be/bXz0BbdPR_w ;)