[ROM] xFlytouch 1.9_88 v0.4 [RUDROID] ROOT, MARKET, 400Mhz KERNEL
Posted 04 October 2010 - 02:16 AM
Posted 04 October 2010 - 02:34 AM
Posted 04 October 2010 - 03:08 AM
thanks hideperso....cant wait with ur new fw release...this fw works fast and smooth...i realy like it....its so cool...
This ROM for 128Mb PAD mainly and this just Alpha version :)I will pack 256Mb version and describe how to restore support for huawei k3565 some hours later. This is testing ROM
Posted 04 October 2010 - 03:34 AM
Posted 04 October 2010 - 03:46 AM
Posted 04 October 2010 - 03:52 AM
Posted 04 October 2010 - 03:53 AM
Posted 04 October 2010 - 04:03 AM
Posted 04 October 2010 - 04:12 AM
Posted 04 October 2010 - 04:17 AM
Posted 04 October 2010 - 04:34 AM
This may sound like a silly question' date=' but are you sure it is fully charged before you use it? My experience so far is that the power metering on this device is quite badly broken, and fails even on the most basic things (e.g. the battery charge level should [B']never[/B] go up unless it is being charged, and I have seen it bouncing between green and yellow levels and yellow and red levels quite a lot as the cpu usage varies. I have also found that when the battery is showing as full, it may not be anywhere nearly full. I have seen it take several hours of charge when it was saying it was full before the charge indicator went off.
Does any one have some ideas of what could be going on with my device batery?
Posted 04 October 2010 - 04:41 AM
Posted 04 October 2010 - 05:07 AM
Posted 04 October 2010 - 06:36 AM
This mean what your CPU can't be so overclocked - try to use 387Mhz.
Mine is locked-up @ 400MHz (stuck) it did zip along though now SDCard won't work nor will it work! I am down for now.. Try again later when morning come.. To fix it.. Wish me luck?
Posted 04 October 2010 - 06:40 AM
Pad always start on 350Mhz - standard speed. If you try set 400Mhz in SetCpu and it stack - just reset device (this mean what your CPU can't overclock so hight)
Can you please tell what the problem was? Did you just reflash an older firmware?? Just want to make sure before I run into the same problem
Posted 04 October 2010 - 06:51 AM
You are right! But your questions just show what your never try to use SetCPU :)This kernel support governors (user, maximum speed and so one) and you can set any on startup settings. You can set your own rules as user governors what to-do with CPU speed on some event. Also you can try to do something with WIFI, as i say before here, projectgus put into git Android kernel source. I was dancing some weeks with their. Modify and compile (but you can have some troubles with drivers, some code still in binary). Git hub source
http://edc.intel.com/Link.aspx?id=3322[/url] )This means that clock speed is linearly related to the power consumption and increasing the clock speed from 350MHz to 400MHz will reduce battery life by approximately 14%. In practice, the reduction will be much smaller because the two massively dominant power consuming features are WiFi and the screen backlight. CPU's power usage is very distant 3rd.I am curious about this profile setting, though. Is there a way to adjust the clock speed dynamically during runtime? In full-fat Linux this is done by the cpuspeed daemon. Does Android do such things automatically? If not, then perhaps implementing/adding something like cpuspeed with a user-space governor might be quite useful in improving battery life. That's assuming something like that isn't already happening.Also, is the voltage of the CPU dynamically adjustable in software? If so, then exponentially bigger power saving gains could be achieved, too (power consumption follows the square of voltage).Another thing - I'm finding in normal web browsing usage that WiFi is using even more energy than the screen backlight. Can the transciever power be dynamically adjusted at run-time? How does the TxPower parameter work and what does it do? What I'm thinking about is doing something that would detect when the WiFi is idle and slow it down and reduce transmission power to a minimum until an incoming packet is detected. This could be done with something potentially as simple as iptables "recent" packet match and a userspace packet logger that actually adjusts the power up when a packet arrives, and drops it when the connection has been idle for a few seconds.Any thoughts on this?
Posted 04 October 2010 - 06:56 AM
You lucky man with good CPU :)I have same issue with battery - small or old. Calibration help me to know it real charging status but i havn't time to hardware mod - think will buy external battery or new internal later.
-Performance at 400mhz AWESOME.Does any one have some ideas of what could be going on with my device batery?
Posted 04 October 2010 - 06:57 AM