yashsingh1/xdaforums huggingface dataset:
[Huawei Ideos X5 U8800] lemonade747:
BIG ISSUE:

-->WHEN U TURN OFF UR PHONE

-->PLUG IN THE CHARGER

-->THEN UR PHONE WILL AUTOMATICALLY GO TO CWM!!!

==>THIS IS VERY ANNOYING, I CANT CHARGE MY PHONE WHEN IT IS TURNED OFF :(

+++++++++++++++++++

‡ Sent From My U8800 ‡

+++++++++++++++++++
[Huawei Ideos X5 U8800] dangerous_johnh:
I have the same behavior, it's a bit annoying.

Other than that, I can't seem to be able to see the contents of my sd card, when I choose that option it shows the contents of the internal card. Which is a big drawback because you can't mount it and place zips there.
[Huawei Ideos X5 U8800] spirosbond:
True and annoying...
[Huawei Ideos X5 U8800] chandramani123:
omg it works like a charm its like 3:AM in the morning ...............
[Galaxy S III Q&A, Help & Troubleshooting] port76:
Hi guys m l have a question I have a problem I'm on jb and unable to download anything using my stick browser its the same on a few jb rom iv tryed does anyone know a fix ?
[Galaxy S III Q&A, Help & Troubleshooting] fethi2:
you can try mobile opera, it is a great downloader. I download every file from that browser.
[Galaxy S III Q&A, Help & Troubleshooting] port76:
that's what I'm doing at the moment thanks . But it doesn't solve the dload problem my friend thanks for your input :thumbup::D
[Galaxy S III Q&A, Help & Troubleshooting] fethi2:
is there anychance that u use Ext2IntSd Mod???

Cause sometimes in that mod MicroSD behaves like write protected :)

if you use it just delete the file and flash again...
[Off-topic] 063_XOBX:
I would take part but so far not a single online petition I've seen has ever done anything. Also I hate mailing lists.
[Off-topic] Breezer23:
Signed.
[Off-topic] SimonTS:
Normally I would agree with you, but the EFF have some serious clout behind them, which is why I have signed this petition.
[Nexus 7 Q&A, Help & Troubleshooting] throcker:
hey guys, can you help me with some feedbacks/suggestions?

I am valuing to buy a nexus 7, but...I really don't know why, I saw it on a leaflet and is so beautiful, so attractive, SO CHEAP!

so...now I'm trying to search some reasons for buy it XD

let's start...

-is a tablet, is very portable...is fast...I never go out without my laptop and, do you think that it could replace my notebook? when I'm out I use it just for browsing, some...FB, twitter, xda...downlaod roms, zips, apks, mods...with a wifi is enough fast and dependable?

-is a nexus...so I deserve 2 major updates :) 2 years of official support...nothing can pay this...

-again is a nexus, so...tons of roms!!!! I love flashing...

-can I plug in a mouse/keyboard? does it have the usb OTG? this would be great..also pair a bluetooth mouse, is it possible?

please, give me some reasons for buy it!

sorry if is not the smartest thread in the section XD
[Xperia Arc Themes and Apps] FAdrums:
The first of many custom battery Icons. :cool:

Instalation:

Open your systemUI with winrar -> go to res/drawable-hdpi -> Copy the battery png's of your choice and paste it on the drawable-hdpi folder -> Chose "Store" instead of the default "Normal" on winrar -> Close WinRar -> Move systemUI with rw-r-r permissions onto your system/app folder -> Reboot -> DONE!

Screenshot and Preview

Download

Available in:

Green

Red

Orange

Blue

Say thanks if you like my work! :fingers-crossed:​
[Xperia Arc Themes and Apps] SXUsr:
Going to try the green in my IceGreen theme. :)
[Xperia Arc Themes and Apps] FAdrums:
Coolness! :thumbup:
[Xperia Arc Themes and Apps] SXUsr:
Just put a few of the images against the statusbar in PS and I hate to say that I won't be using them unfortunately, the green is perfect as is the effect but you've left a slight diagonal blue line across the top left of the images which is such a shame as that's too much editing for me. :crying:

Other than that though they do look amazing, good work. :)
[Xperia Arc Themes and Apps] FAdrums:
Thanks for the feedback. I might edit the main battery png then...if I have the time. :) ThilinaC is "pushing" me to go forward with my rom so I have to think what am I going to do Androidwise! :p
[Xperia Arc Themes and Apps] SXUsr:
Have you got a psd file?
[Xperia Arc Themes and Apps] FAdrums:
Not sure dude! I'll check! ;)
[Defy Q&A, Help & Troubleshooting] drawkcaB:
I have a green lens defy which was running cm7.2 stable. Earlier today i opened it to see if i could get rid of a crackling noise from the earpiece. I opened and closed up the phone and the crackling stopped however the bottom half of my screen started giving trouble.i can control the top half perfectly but the bottom half keeps behaving like im touching and leaving the phone so when Swyping i get it as if ive tapped multiple letters rather than drawn a line across them. Ive cleaned out the cache and even gone back to stock to no avail. Ive done the obvious of reopening phone and checking the connector between the digitizer and the circuitry but thats fine. I removed and inserted it multiple times with no change. The bottom half seems to pick up taps properly but no drags and all drags that are picked up are pick up as horizontal lines. Ive even adjusted the digitiser connector while the phone was powered on to see if it was a loose connection of sorts but to no avail. Contacts and the like are clean. Warrtny expired 10 days ago :/ . Any ideas?
[Defy Q&A, Help & Troubleshooting] ela1103:
you must change the touch screen ok ,there is option to reassemble ok .iam also having this trouble in touch screen ok .i changed the touch screen in moto service centre ok.it cost 3500rs
[Defy Q&A, Help & Troubleshooting] underzander:
I have the same problem in red lens

Hello, I had the same problem with one red lens, the touchscreen was broken and replace it (only touch unframed), then manually pasted what the problem started exactly at the top, I thought it was spoiled (badly damaged pegadao ) and change it again, but still the same, so I thought some of the software and did everything and nothing, now I buy a touchscreen with frame to avoid having to manually paste if that works. What do you think? What do I do?
[Defy Q&A, Help & Troubleshooting] drawkcaB:
Ive ordered exactly the same thing. Mine got lost in transit so i just ordered another. it could take a month to reach but ill let you know what happens for me.

Let me know how yours goes.
[HTC One X] mavrick1591:
not my work , just copied the link

google now for ICS port(for those who cant wait)

download and flash by CWM as always

tested on viper x 2.1.0 , running great

http://d-h.st/Xse
[HTC One X] rik-sik:
Works on mine , Maximus v3 :)

although i feel like a goon asking my phone questions lol :cyclops:
[HTC One X] BATFINK74:
so this is not possible on stock rom?
[HTC One X] vivek_bhoj:
if you are rooted then you can flash this zip
[HTC One X] BATFINK74:
any workaround for unrooted?
[HTC One X] vivek_bhoj:
Not at present you will have to wait for official jb release by HTC
[HTC One X] DTMHibbert10:
Won't install on my viper X 2.10 (installation aborted)
[HTC One X] forgir:
Works well with my ViperX 2.1.0! Nice!

Sent from the past with One X
[HTC One X] BATFINK74:
ok cheers dude
[HTC One X] Baldilocks:
Works great on stock rooted 2.17.

Sent from my HTC One X
[HTC One X] Gormsen:
Works like a charm on ViperX 2.1.. well okay, it works, but I can only get Google Now to show the weather card, anyone else experience this?
[HTC One X] shahravi94:
works fine on arhd 9.0.0
[HTC One X] mavrick1591:
U will have to wait a ask it some other stuff as I think the cards r based in ur searches ,places ,etc....
[HTC One X] DTMHibbert10:
Works well for me now had a dodgy download lol
[HTC One X] guoloong:
Anyone has a mirror of this download? dev-host seems to be doing maintenance
[HTC One X] benno4403:
Yep, they should be online by now but I guess they are still working on it, as far as I know there are no mirrors.

We will either have to wait or someone has to post the zip elsewhere.
[HTC One X] eyosen:
And on your location. In my home country i get only weather. In Us, many other cards popped up last week.
[Samsung Infuse 4G] electricpete1:
In the above analysis, I have assumed that power consumed by the cpu can be predicted from the cpu frequency (for a given voltage setting of course).

I now believe that assumption might be incorrect.

The reason I believe it is false is a result of another experiment I just did.

I set the cpu governor to performance to maintain constant 1200Mhz.

Then I looked at the cpu power usage trace in "Power Tutor" program.

I expected to see power attributed to cpu usage as constant, but it was varying up and down.

And by moving the homescreens around, I could create a dramatic and predictable increase in power usage of cpu (as indicated on Power Tutor).

All of this change in power consumption of the cpu occurred while the cpu governor was in performance mode with cpu frequency constant at1200Mhz.

I didn't expect that. I can't really explain it (can anyone else?). But clearly there is more to the story than I thought (assuming that the cpu power usage reported by the Power Tutor is correct, which I'm not sure of either).

To evaluate the battery friendliness of variouis governor settings, it might be more useful to watch the power tutor results when performing the above experiments, instead of just watching the cpu frequency as I did before.
[Samsung Infuse 4G] Truckerglenn:
:confused::confused::confused: Over my head...
[Samsung Infuse 4G] qkster:
How does the battery cycle pan out?

It would be nice if you or someone else had a spare phone to test this battery consumption theory.

I would wonder if the report of consumption is also correct.

The bottom line that I would be interested in seeing is how long can the phone, running a certain kernel and governor, last.

For example: Charge to 100%. Take off charger. Wifi off, Cell data off and in Airplane mode (removing signal variable).

Then run kernel with governor - record the battery duration.
[Samsung Infuse 4G] Zen Arcade:
e.pete - nice work! I appreciate your empirical approach to this topic.

I can add the following: you have described accurately how the conservative governor works. For OnDemand, the governor behavior results in the CPU at max under load and minimum when idle, with a smaller amount of time being spent at the steps in between based on thresholds. On my phone today with OnDemand, for example, I'm at 1600mhz 6% of the time, 100mhz 5% of the time, and 800mhz 2% of the time. Deep sleep is 83% and the other CPU frequencies are all below 0.5%.

In general use, conservative should be kinder to the battery and to the hardware. The recommendations I have seen for Linux platforms is to use conservative where battery life matters and ondemand when there is a constant external source of power (i.e. PC or server). Of course, actual use determines how the governor performs. Most smartphones have a lot going on even when the screen is off. A good indicator of average CPU use over the course of a day is CPUSpy. This app, combined with a decent battery monitor can help tell the story from a macro/whole system perspective over time. On the "be kind to hardware" topic, conservative should increment and decrement to adjacent frequencies based on load. This behavior might be happening too fast for SetCPU or other realtime monitor to capture..that's where CPUSpy can show what is happening over a larger period of time. These more gradual transitions may result in less wear and tear on the phone hardware, but I have not seen any significant evidence that this is a factor in the usual life span of a smartphone. (On the flip side, setting the governor to performance and OC to max setting...that is NOT recommended and could harm the phone).

That said, the two kernels you tested have the following default characteristics:

Entropy DD - Conservative/BFQ - Optimized for stability and battery life

Infusion (Bedwa/Zen) - OnDemand/CFQ - Optimized for performance

The Infusion kernels do not include optimization settings for conservative. As you surmised, the expectation is that if you are going to change these settings you have some idea of what you are aiming for and will adjust accordingly.

If battery life is your aim, I've found that the best savings are realized in optimizing transition to sleep when the phone is not being used, minimizing the number of apps that attempt to keep the phone awake, and being selective in your use of wifi and data radios (although too much mucking around with this last option can lead to triggering some of the known bugs in these kernels which manifest as a higher than normal Android OS or Dialer/RILD drains - as seen on the standard battery usage screen in Settings).

On this last topic, there's another thread (which I see you have visited) which covers discussion and work on these known battery drain anomalies: http://xdaforums.com/showthread.php?t=1408433

Here is some additional information on governors courtesy of Big Blue... http://publib.boulder.ibm.com/infoc...?topic=/liaai/cpufreq/TheOndemandGovernor.htm

And a bit more info ... https://wiki.archlinux.org/index.php/CPU_Frequency_Scaling
[Samsung Infuse 4G] Smokestack360:
:what: I'm so glad there are people much smarter then myself here. Great work electricpete :thumbup: even if I followed about half of it :D

Sent from a de-FUNKt Infuse
[Samsung Infuse 4G] Zen Arcade:
Pete - Here's a link to a thread that has a lot of information about governors, i/o schedulers, tweaks, scripts, and kernel objects:

http://xdaforums.com/showthread.php?t=1369817
[Samsung Infuse 4G] electricpete1:
Thanks everyone, a lot of good info.

Especially Zen, very useful info and links.

It was a very interesting comment about certain governor strategies being hardware unfriendly if they jump increase the cpu from min to max.

I never realized that was a factor (only thought the max speed was important).

But it definitely sounds plausible. Maybe (?) the rapid temperature increase causes uneven temperature (cpu gets hot before attached plate gets hot) and therefore uneven thermal expansion, which causes mechanical stresses. I can imagine there are other subtle aspect of the cycling up/down that can be important. If you have any more info or links on the effects of cpu governor strategy upon hardware life readily available, I'd be very interested to hear it. (If not readily available, that's fine too, I will do some googling).

I did find this link which suggested it's better for the hardware life to run at 100% (I guess for us that's 1200Mhz) than it is to cycle up/down. It's not written about phones but about PCs. There might be some differences in the technical aspects. There are of course big differences in the priorities for PCs... they don't care about power usage as much as phones do, and pc users probably expect a longer life than phone users do.

http://www.overclockers.com/overclockings-impact-on-cpu-life/

Thanks again.

I will report back if I get some free time to continue experimenting... maybe this weekend.
[Samsung Infuse 4G] Zen Arcade:
Primary consideration (as you've noted) with smartphones is battery conservation. ARM processors are engineered to operate at multiple frequency steps, and to turn off where possible. Without this capability phones would need a much higher capacity battery. As for PCs, current processors include frequency stepping technology to reduce power consumption and heat, and perhaps extend life by keeping temps lower.

The main conclusion of the article you referenced (which is 13 years old, btw, but does contain a wealth of good foundational information) is that heat is the primary enemy. This is a major factor with smartphones as they have limited ability to dissipate heat. An Infuse running at 1200mhz (or 1600mhz OCed) confined to a purse or pocket, or (as reported in these forums a while back) under a pillow gets hot very quickly. This will lead to conditions that will harm the phone. At one time, my phone had an error condition causing the Dialer to go crazy (rild process) and peg the CPU at 100% for an extended period of time, while the phone was also plugged into a charger (thus heat from the charging process too). The end result of this was a temperature that tripped a heat sensor threshold, causing the phone to shut itself off. So there are, at least, limited protections against extreme events.

As I noted above, I've not seen any evidence that the normal (or even OCed) frequency stepping that occurs with smartphones leads to failures within the normal in service period for these devices - 2 to 4 years in most cases. Running at 100% all the time may put your phone's health at risk and will definitely impair your battery life.
[Samsung Infuse 4G] electricpete1:
Zen - Good points. One thing I do take away from the article (along with your comments) is the cuumulative effect of cycling, So when I settle on up/down threshholds, I may try to avoid putting them too close together in order to avoid extra cycling (keep Max/Min threshhold ratio >2). Although I do realize these particular cycles between two adjacent frequencies are not as bad as bad as the cycle between min and max frequency.
[Samsung Infuse 4G] electricpete1:
I have heard Entropy mention that before changing kernels we should always reset UV settings (and reboot) and reset other cpu related settings (Fmin and Fmax I assume).

I would like to add another item: always uninstall setcpu before changing kernels and reinstall it after you change.

The reason: I have seen some very weird results of setcpu when I left it installed in between swapping kernels. Like for example cpu running at 1600Mhz even though Fmax is 1200Mhz and there are no profiles allowing 1600. Those weird results are not included in the above data (I observed the frequencies during each trial as reported in the spreadsheet).
[Samsung Infuse 4G] electricpete1:
unintended consequences from changing up threshhold

I used the following setup for almost a month:

Zen’s Infusion A Kernel (with my stock GB), conservative governor

UpThreshold = 95

DownThreshhold = 45

Only twice during the month, I saw the following:

Received a phone call. I could see the name of the caller. I couldn’t hear the caller. When I finally got hold of them later, they told me they could hear me even though I couldn't hear them.

That was very tough to figure out because it only occurred on two out of probably 30 or 40 phone calls received in a month.

The two phone calls did originate from cell phones in the same geographic area (near my work, an hour away from my home).

Then I had a breakthrough when I set up my work voicemail to automatically call my Android phone. Almost every time it called, the problem appeared (I couldn’t hear the robot voice telling me I had a message).

I kept leaving myself messages to reproduce the problem and narrow it down.

I found out it only occurs when my phone is asleep at time of the call (doesn’t occur if phone is awake at time of the call).

I removed my UV and problem continued.

I adjusted my governor and could make problem go away.

I narrowed it down to the up threshhold.

Repeatable with 95/45 up/down, the problem occurs.

Repeatably with 80/45 up/down, the problem does not occur.

I have gone back and forth between those two settings at least four times and each time it confirms the symptom is directly related to the governor setting.

Exactly why that is I’m not sure. Maybe the cpu is to slow to wake up to handle the call? Sounds kind of hokey, but I guess it doens’t really matter.

The bottom line for me: 80/45 is a great place for me to stay. Eliminates the “can’t hear caller” problem and still does pretty good at preventing cpu from going to high frequency when listening to my relax and sleep program for long periods of time.

If anyone has gone to 95/45 based on my recommendation, you might rethink it, especially if you see unusual behavior.
[Android General] thronnos:
I urge everyone to take one minute out of their busy lives to read and then sign this petition from the EFF for patent reform. It's very simple, and very well thought out. Many big players and developers already support this. Please do your part as an American Citizen and a member of our great community to stop the patent tyranny that Apple had taken advantage of.

https://defendinnovation.org/

Please reshare this to everyone and every forum you know.

Shifted from Outer Space
[Android General] thronnos:
Bump for some more sigs

Shifted from Outer Space
[Android General] sparytrainor:
This is awesome!! Come on people, more sigs!!!
[Android General] ProDriver77:
Signed. Let's keep this moving people!

Sent from my Galaxy Nexus on Verizon Wireless
[Android General] thebobp:
Until we get another blackout, I don't particularly see this going anywhere.
[Android General] Instynct:
Signed, thanks for posting this. :good:
[Android General] Snakeplizkn:
Waste

Yes, let's all take the time to provide our email address to an organization looking for donations to advance ideas that have ZERO chance of ever seeing the light of day. The last patent reform effort hasn't even kicked I yet. Congress won't look at this issue again for another 50 years, least of all at the urging of these hacks.
[TouchPad Q&A, Help & Troubleshooting] Aganar:
So I bought the HP Touchpad Wireless keyboard for my TP and love it. My only problem at this point is that some of the buttons don't work on Android. Obviously the Card button which was meant for WebOS does nothing here, and even though the Play/Pause button works, the skip track prev and next do not. I see that most of the keys are still sending inputs file the KeyEvent program, but are not mapped properly.

I tried changing one of the keyboard files (when googling this it was recommended I change qwerty.kl) to properly map to the input the keyboard was sending, but it didn't appear to have any effect. My suspicion is that perhaps the HP BT keyboard uses something like /system/usr/keylayout/Generic.kl instead of qwerty.kl, but how do I know for sure? There are like a dozen in there. Is there a way I can make a customized one and somehow tell CM9 to point to that layout file when the BT keyboard connects?
[AT&T, Rogers HTC One X, Telstra One XL] zombiej79:
I'm new to the One X and was wondering if there are any custom kernels for it

sent from my beautiful One X
[AT&T, Rogers HTC One X, Telstra One XL] E.Cadro:
There is currently only one kernel for our phone http://xdaforums.com/showthread.php?t=1797251

It only works with 4.0.3 based roms

Sent from my HTC One XL using Forum Runner
[AT&T, Rogers HTC One X, Telstra One XL] InflatedTitan:
There is one custom kernel called blackout beast mode. Its for 4.0.3 base roms ONLY. So do some research before you flash. It can be over clocked up to 2.1 GHz, and the GPU is also over clocked.
[AT&T, Rogers HTC One X, Telstra One XL] zombiej79:
Thanks guys guess it's still somewhat new so kernels might take time
[AT&T, Rogers HTC One X, Telstra One XL] robertmoore208:
Wild Child has a few custom kernels over in his forum ... Well worth the checking out:)

WCX HTC One "Hell of a fast phone" X
[AT&T, Rogers HTC One X, Telstra One XL] zombiej79:
Do you have a link?
[AT&T, Rogers HTC One X, Telstra One XL] robertmoore208:
http://www.wcxxperia-nce.com/forum.php

WCX HTC One "Hell of a fast phone" X
[AT&T, Rogers HTC One X, Telstra One XL] twistedddx:
Wild child site does not work for anyone outside of USA.
[AT&T, Rogers HTC One X, Telstra One XL] gridlock489:
Is there any benefit to flashing a new kernel if my aim is battery life and not overclocking? Currently I underclock my processor to 1.2GHz and I have gotten noticeably better battery life. Could it be even better with the Blackout kernel?