yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] tas0s:
Guys are you still experiencing battery drain?

I'm almost certain that it has to do with auto brightness.At

least in my build for u8120 I have disabled it and the battery consumption went really smooth and slow.Three hours and more and its still in 99% with two calls and a couple of sms.

just set <bool name="config_automatic_brightness_available">false</bool> in overlay/frameworks/base/core/res/res/values/config.xml on your overlay folder ;)
[Android Software/Hacking General [Developers Only]] Hetfield666:
this is a really interesting thing as i usually set it.....

isn't enough not to mark the auto as used from the GUI?
[Android Software/Hacking General [Developers Only]] tilal6991:
What ROM are you using?
[Android Software/Hacking General [Developers Only]] tilal6991:
Will do
[Android Software/Hacking General [Developers Only]] tilal6991:
The first boot is really slow because it rebuilds the dalvik cache. Putting back to default launcher in next release. Launcher pro can be used and rom doesn't matter.
[Android Software/Hacking General [Developers Only]] Kyrle:
Thanks, good to know. You didn't address the melfas issue however. Is there a fix available/in-the-works/planned?

I originally bought this phone knowing it didn't have multitouch, then I got a glimmer of hope that it might, then got smashed down by melfas. I can live without it, but it would be nice to have if its possible.

How hard would it be to put toggle buttons in the notification area for turning on and of stuff like wifi, gps, and wireless data?

I don't know if its just a problem with mine or not, but the battery percentage number only shows in the green area of the battery display. As the battery gets lower, the number on the left side gets cut off, and I'm guessing, when it gets really low, you lose the numbers altogether. This isn't an issue for me, just thought you might want to know about it.
[Android Software/Hacking General [Developers Only]] tilal6991:
Its still unclear whether melfas could have multitouch. It should be possible but no one seems yo be working on it. The icons in the notification area is a cyanogen only thing. The batter icon I know abut :)
[Android Software/Hacking General [Developers Only]] maury1234:
@tilal

Look at the new oemlogo i have made!

It promotes our team and gives a better look to our devices :D

Tell me what you guys think about it..

.zip file included for those who want to implement it.
[Android Software/Hacking General [Developers Only]] tilal6991:
Looks great :). I tried to create one like it but I'm really bad at designing graphics so I just used a stock android one.
[Android Software/Hacking General [Developers Only]] maury1234:
shall we use it?
[Android Software/Hacking General [Developers Only]] Nitemar3:
to be honest guys . yeh im not in da team but i looks good but you can improve on the font color and background btw.
[Android Software/Hacking General [Developers Only]] eqzgkxokwa:
How to turn back old status bar color&icon?
[Android Software/Hacking General [Developers Only]] Trekker56:
Thnkx for the advice guys. I was able to load FROYOMAN after a wipe. Link2SD is also working with ext2, and multitouch is also working. Will download linpack to see if the under and overclock are also working.

Great job guys!

My wishlist now is

1. A black theme,

2. Circular battery indicator with %,

3. Semitransparent notification dropdown.

I hope these might be incorpoarted in a newer version.
[Android Software/Hacking General [Developers Only]] King_Rat:
GPS back & working after restoring Cyanoman from Froyoman (maybe If I restore my Froyoman nand BU over my restored Cyanoman - it will have fixed itself too ^^ i.e. no more unlcean shutdowns (:wth: does that mean anyhow???) + lagginess may have vanished ^^

Try soon & let you's know
[Android Software/Hacking General [Developers Only]] platysquatch:
Hi all and thanks for all your work.

This is my first foray into rooting my phone and installing roms. I thought I would share my experiences.

Firstly I installed Clockworkmod and Rom Manager. That took me a little while to figure out because I forgot to add execute permissions to the clockworkmod installer on linux.

Then I messed around for a while because I was unaware roms were installed from a zip, so extracted the files (Froyoman) before transferring. That confused me for a while and I did a few reboots trying to get that to work.

When I did install, I noticed clockworkmod still says installing Froyoman v2 when I had downloaded version 3.

Starting up for the first time I was impatient and so took my battery out before it got through the whole startup (updating cache?) and then manually deleted data and cache because I saw that mentioned as a fix for hanging on startup. Then I did wait long enough for boot, but didn't have any of my data. I proceeded as normal not knowing any better and attempted to install all the apps I wanted. Multitouch worked great and it was way snappier than stock. Many thanks to the devs! I did notice battery seemed to be draining more quickly but maybe I was just not accustomed to watching a numerical indicator.

Eventually I realised my gmail contacts were not syncing (empty contacts list) and couldn't find a way to get it to do so. Is this a bug or a quirk from me not doing things properly?

So I restored my backup to stock and then decided to try FUSIONIdeos. This kept all my data so I thought "Ok I must have done something wrong before" and installed Froyoman again. This time I waited and I kept all my data and everything works great including contacts (I think it's syncing, not just using stored contact info but not sure...) except I found that I have no gTalk. I can see when people are online in my contacts and messaging lists but simply do not have the app. Does anyone know where I can get an .apk to restore this? Is this expected behaviour of this ROM?

Thanks again to all.
[Android Software/Hacking General [Developers Only]] King_Rat:
@ platy you need gapps installed :mmm:

Froyoman took a while to bed down... (flashed this avo)

Had 3 unclean reboots/shutdowns - settings not apllied :yadda: :yadda:

happening while transfering apps to/from SD card...

Go Launcher needs to Go away :lol: UI is fugly :imo:

adw :ftw: (I use adw ex)

:woot: ROM is OC'd but feels laggier than Cyanoman...

Not so keen on new battery icon & 2G/3G icons... (2G icon come sand goes?! Is mostly gone ^^ 3G icon stays put)

Froyoman seems a little thirsty... you'll need to use Titanium Back Up to freeze a few things...

Maybe Green for select rather than blue ^^

:2ThumbsUp: Mutlitouch working a treat ^^ plus glad to have GPS back...

Love new bootanimation :rox:

Not as much internal memory i.e. room as Cyanoman... there's another 6 or 7 apps I had running on CM6 that I'd like to install on FM.. but I'm down to 57MB already :eek:

Will post more as I get more familiar :yes:
[Android Software/Hacking General [Developers Only]] platysquatch:
Thanks King_Rat. Apps from the OP fixed it for me.
[Android Software/Hacking General [Developers Only]] crispybbq:
I can't seem to download froyoman or cyanoman from GitHub. Get random Access Denied messages. Any tips? :\
[Android Software/Hacking General [Developers Only]] samwyze:
Glad to hear link2sd is working, I'll reflash after a full wipe and see if that helps it work for me!

Seems like launchers are a personal preference thing, so why not have something lightweight like zeam as default and let peeps install there own favorite if they want? Just an idea :)
[Android Software/Hacking General [Developers Only]] tilal6991:
You don't download from github. You can download using the links I put up on the first page
[Android Software/Hacking General [Developers Only]] tilal6991:
Wow so many questions and comments. I'm not near a computer right now but as soon as I get one ill answer all questions. Thanks for all the support and feedback guys.
[Android Software/Hacking General [Developers Only]] oppi56:
Now ive got the best rom... returned to launcher2 and replaced framework by nero di seppias. Looks great and is super fast. The slight oc is great. I dont need more... its perfect
[Android Software/Hacking General [Developers Only]] aorth:
Flash a fixed boot.img

That particular bug comes from a change that happened in CM7 after builds around September 25th... I posted a fixed boot.img here: http://cleanimport.xda/index.php?posts/17886958/. Check there for more information, but here's the fix:

Download this boot.img: http://www.mediafire.com/?livfk72509r8vgd

Shutdown your phone completely.

Reboot into bootloader mode; with your phone off and unplugged from USB:

Hold down RED, volume down, and then press power for a few seconds.

It should vibrate and then stop at the IDEOS screen.

Find and download a copy of fastboot (use your brain, google it).

Plug your phone into the computer.

Flash (use your brain, replace my name with yours):

/home/aorth/Downloads/fastboot flash boot /home/aorth/Downloads/boot.img
/home/aorth/Downloads/fastboot reboot

This boot.img contains a kernel which has a max of 672MHz, min of 30MHz, and is using the smartassV2 CPU scheduler by default.

Hey, yep... I remember tilal saying he used a higher overclock setting, like 700+ MHz. The highest my phone could ever go was 672, so that's where I cap kernels in all my builds which have overclock enabled.
[Android Software/Hacking General [Developers Only]] tas0s:
Funny enough but I think that no:p, it must be disabled from config.

At least in my previous builds that I have enabled it in config but disabled in GUI

the battery drain was still an issue.

I will do some more tests to be sure, but try it by yourself and tell me if you can.

I see that now, in battery status the Android system occupies 33% where in the previous builds was 99%:)
[Android Software/Hacking General [Developers Only]] Hetfield666:
i have 2 issues with nightly: battery and headphones.

as soon as these two wonderful guys will post a new snapshot with headphones working i will test battery usage too
[Android Software/Hacking General [Developers Only]] aorth:
The problem with battery!

The problem with battery is that people flash too much, me included. :) Every time you erase your ROM you wipe out the battery stats. Battery usage really isn't reliable until you've had a full charge/discharge cycle or two, and I erase my phone at least once a day to test some new kernel or CM7 build, etc... ;)

People need to run the builds for a few days and give their batteries a chance to calibrate.

btw, haven't looked at sound much lately... been really busy with life/work...
[Android Software/Hacking General [Developers Only]] project2:
i tried your boot.img too, same effect as the original from gingerman cm7:

ideos logo, the android appears skating, then the circle turns around and around but nothing happens anymore

without replacing boot.img its not getting past the ideos logo

damn.... i wanna try the nightly ;)
[Android Software/Hacking General [Developers Only]] Hetfield666:
i don't agree alan.

whatever rom you put, you can see battery is almost ok.

the % number is done reading the voltage values (stock vs read).

so the stats will just add a little tuning nothing expecial.

infact, if you flash stock kenya rom or fusion rom you get immediately a good battery usage.
[Android Software/Hacking General [Developers Only]] lazyfai:
currently, the only way to stop the battery from dropping quickly, is to turn off mobile data, wether it is 2G or 3G, once turned off, the battery can then last at least 2 times longer.

the drain happens even I just turn on mobile data and do nothing, so it should be related to kernl drivers or userlands related to mobile data.

this is typed on my N900 because I am testing the maximal life without mobile data.
[Android Software/Hacking General [Developers Only]] Hetfield666:
i don't agree with you either :P at least on my u8150-D device.

test is quite easy:

full charge, flash a rom, leave in flight mode for a night long (6-7 hrs) with ondemand governor and 60min /352 mhz max.

stock rom -> from 100% to about 98%

fusion -> drop to 99/98%

nightly -> drop to 74-76%

so no wifi, no bluetooth, no data, not even gsm, no screen activity (i'm sleeping!) just OS running.
[Android Software/Hacking General [Developers Only]] crispybbq:
Mirroring?

I'll try mirroring future ROMs on Minus. Any new nightlies, try uploading them to my Minus folder, if it works...

If that collaboration link doesn't work, try this read-only link to download the files or to follow the folder with your own (if any) Minus account. Either way, if I see a nightly in this thread before I see one in the folder, I'll mirror it myself ^_^

Let me know if there are any links/references/notes/whatever I should be mindful of with the uploads....
[Android Software/Hacking General [Developers Only]] SyedAnique:
can someone please confirm that the rotation sensor and compass are not working with the latest nightly
[Android Software/Hacking General [Developers Only]] dc959:
yup there not working but sometimes the screen automatically rotates when you go out of sleep so i have a small feeling that it works when the phone is in sleep
[Android Software/Hacking General [Developers Only]] aorth:
This would be the perfect time to learn how to use adb logcat, have you ever tried it? If you started logcat and then rebooted your phone you'd see exactly what was going on. I'm very curious why my boot.img didn't work.
[Android Software/Hacking General [Developers Only]] SyedAnique:
Yes i have also noted that.

Thanks

---------- Post added at 01:17 PM ---------- Previous post was at 01:15 PM ----------

By the way does ice cream sandwich needs hardware acceleration to work or not
[Android Software/Hacking General [Developers Only]] aorth:
To an extent you're right. The battery usage on these CM7 builds does seem to be a bit higher. Note: the definition of "bit" varies ;).

Still, here I have 13 hours of battery.

The phone was not in airplane mode, wifi was on... That was flashing a new boot image (with new test U8150 kernel and smartassV2 CPU governor), then using the phone on the bus home, and periodically through the night, then I was sleeping, woke up and did some twitter on the phone. So it's not HORRIBLE, for me at least. :)

---------- Post added at 03:05 PM ---------- Previous post was at 02:21 PM ----------

In other news, Android 2.3.7 somehow eeked its way into the git repositories. Freshly compiled:

As far as I know, anything past 2.3.4 is pretty much device-specific fixes for Nexus S (4G?). But still cool to have a +2 on the version number, eh? Nothing like a good ol' placebo effect!
[Android Software/Hacking General [Developers Only]] kahush:
Vipi?I want to install the notification bar framework from the nightly on Gingerman 7...any help?
[Android Software/Hacking General [Developers Only]] lazyfai:
Originally the battery can only last for ~12 hours even just a few phone calls and sms and a few whatsapp messages (with the help of juice defender already!)

I haven't turn on mobile data today.

Now the battery is still 51% full after 10 hours of usage (a few phone calls and sms)
[Android Software/Hacking General [Developers Only]] Hetfield666:
way too low.

with 2G and data off i can get 5 days uptime with 3 hrs phone calls and 10 sms.

using the smartphone as a normal phone only.
[Android Software/Hacking General [Developers Only]] project2:
here it is...

i found this one repeating ever and ever:

I/Netd ( 247): Netd 1.0 starting
E/SocketListener( 247): Obtaining file descriptor socket 'dnsproxyd' failed: No such file or directory
E/Netd ( 247): Unable to start DnsProxyListener (No such file or directory)

check my attachment...
[Android Software/Hacking General [Developers Only]] aorth:
Five days is a long time... we'll see what we can do once we start sorting out the other issues (I'm currently trying to shoehorn U8160 synaptics multi-touch support into the U8150 kernel).

Ah-hah! That's a bug that came in nightlies after September ~21. See my commit here which fixes it: init: add service for "dnsproxyd". Flashing that boot image should have fixed it (in fact, any of my boot images after that date will have the fix)... try the one I've attached. FYI, this boot image uses a U8150 kernel, has a max overclock of 672MHz, and the smartassV2 CPU governor.

Here: boot.img (md5sum: 92b2ac21c8bc28eb8a5ee68561e7ed1a... my connection is on the fritz)
[Android Software/Hacking General [Developers Only]] project2:
thanks, that worked!
[Android Software/Hacking General [Developers Only]] kallt_kaffe:
Hi tilal,

try this for overclocking:

Restore the original acpuclock.c then modify it like this:

https://github.com/kalltkaffe/u8160-kernel/commit/3927eb770dc9e9b0ec2508375d11604df22db5cf

Do NOT set change any CPU frequency in any startup scripts. Instead add this to the kernel config:

CONFIG_MSM_CPU_FREQ_SET_MIN_MAX=y

CONFIG_MSM_CPU_FREQ_MAX=614400

CONFIG_MSM_CPU_FREQ_MIN=245760

CONFIG_MSM_CPU_FREQ_OVERCLOCK=y

This will make it boot on 614.4MHz on all devices but with SetCPU, NoFrills CPU control or CMParts it can be changed up to 768MHz (More frequencies can be added easily but I doubt many MSM7225 phones can go higher than that).
[Android Software/Hacking General [Developers Only]] Hetfield666:
but that doesn't have underclock freqs (like 30/49/60 mhz)
[Android Software/Hacking General [Developers Only]] kallt_kaffe:
That's easy to add, but I'm not so sure underclocking below 122MHz will make much of a difference to battery life.
[Android Software/Hacking General [Developers Only]] Hetfield666:
totally agree with you. infact you can easily see that if you use 30-600 with on demand, lots of time is spent on 600.

this may even shorten the battery life.

on the other side, using high freq will make the cpu complete the job faster and go to sleep C1 state and save energy.

it's really difficult to find a good compromise.

personally i use 60-350 or 122-350 when using the phone...just as phone.
[Android Software/Hacking General [Developers Only]] aorth:
I'm not sure... but here's an interesting log from SetCPU. The phone's been on battery for 11 hours, and was mostly just sitting there while I was sleeping.

I'm not sure how SetCPU gets its logs... but it does show that the phone is spending ~25% of its time at 30MHz. We have to consider implications to battery, but also to user experience. For example: if the CPU is at 30MHz and then the CPU governor ramps up to account for increased activity, is there any lag going from 30 -> MAX versus 122 -> MAX?

That's what we need beta testers for... ;)
[Android Software/Hacking General [Developers Only]] Hetfield666:
stats come from linux kernel /proc....something so it should be reliable

your stats look good but mora than 50% of time is spent over 600 mhz.

did u integrate the patch against xml file to disable to auto dimmering of screen light?
[Android Software/Hacking General [Developers Only]] kallt_kaffe:
Underclocking:

https://github.com/kalltkaffe/u8160-kernel/commit/cbe418581f94a6702259ba7265743be6a1662a43
[Android Software/Hacking General [Developers Only]] project2:
i have an other issue.. my gps isnt working anymore :(

the icon is blinking and then its showing location cannot be deteced

it works only with stock firmware

i tried ginger cm7, your nightly, fusion, dronix... no one works..

wheres the problem?
[Android Software/Hacking General [Developers Only]] aorth:
I forgot to mention that this was using the smartassV2 governor. Nah, I didn't integrate tas0s' fix... I'll toss it in there and recompile real quick. I guess it disables the availability of the "Auto Brightness" checkbox...? I guess auto brightness is supposed to theoretically increase battery life... but I've never seen the auto brightness actually adjust the screen... I walked around my house in the dark the other day with my phone trying to get it to do something hahaha.

Satellites? :) I dunno, dude... very weird. Keep an eye on it.
[Android Software/Hacking General [Developers Only]] project2:
no matter where i try - blank sky, at work, at home... no detection. that really sucks ;)

and its confusing that only the stock firmware works properly

i am the only one with this bug?
[Android Software/Hacking General [Developers Only]] aorth:
Auto brightness...

Yep, that config key disables the Auto Brightness checkbox:

I honestly couldn't care less if it's there or not... I always check it, but I've never noticed it actually doing anything. Do you guys generally use or notice that Auto Brightness feature working?
[Android Software/Hacking General [Developers Only]] Hetfield666:
tas0s said that's a bug in cyanogen framework (some handlers?) that may affect battery usage.

just leave the whole night and check if something changes
[Android Software/Hacking General [Developers Only]] project2:
in stock firmware and gingerman cm7 its working.

i disabled it because i think it eats battery

maybe it checks while the phone is in sleep mode?

the interrupt for the light sensor is definitly gaining more power, but is it really noticeable?

how about decreasing the check interval of the sensor?
[Android Software/Hacking General [Developers Only]] lazyfai:
Amazing, with this boot.img the batter drain issue seems disappeared...

(95% battery left after 3 hrs)
[Android Software/Hacking General [Developers Only]] aorth:
October 2, 2011 nightly

As I've added a number of tweaks/features to the kernel and the CM device tree I figure I should post a newer nightly for y'all to play with. If you don't know how to back up your data to cover your ass, or don't know how to get back from a soft brick... don't try this.

List of changes:

Android 2.3.7 (this is the latest version of AOSP, it's basically just a number, but shows we're in sync with the latest sources)

GPS works (just tested it, with mobile data on)

Includes tas0s' proposed auto brightness fix in the U8150 CM frameworks overlay. This disables auto brightness completely, which should help with battery? Let's monitor this cuz I'm a bit skeptical.

Using a kernel based on my U8150 sources, meaning the following are working:

Over/underclocking (672MHz max, 30MHz min)

Auto rotate

... and the following are not working:

Multi touch (tjstyle's patch breaks touch on Gingerbread... I tried porting multi touch from subpsyke's U8160 kernel sources but meh. Besides, not everyone has a synaptics touchscreen anyways, so meh again.)

Haptic feedback for the row of four virtual keys

I haven't looked any more at audio routing but headphone audio works for me™ (maybe Hetfield666 can try and then comment, as his U8150 seems to hate me!)

Download: update-cm-7.1.0-RC1-02102011-U8150-KANG-signed.zip

Flash (from ROM Manager):

Copy to your sdcard

Select "Install ROM from sdcard" and navigate to the zip you copied

Check "Wipe Dalvik cache" and "Backup current ROM"

Click "Ok"

Get ready to taste zesty vegan bacon :)

Optional: clockworkmod_5.0.2.3_u8150.img

Here's the latest ClockworkMod Recovery for Huawei U8150. I've been using it for a week and I think it works better than the 3.0.2.4 copy that has been floating around. This is not necessary for this new nightly or anything, I just like the newer CWM Recoveries better. It's your choice!

Reboot your phone to bootloader mode, and then flash with:

fastboot flash recovery clockworkmod_5.0.2.3_u8150.img
fastboot reboot
[Android Software/Hacking General [Developers Only]] f1ng3r:
Are you sure GPS is not working? Use an app of gps monitoring and check if the app can detect any satellite and your position(latitude etc...without using wifi or data). Tip: i use Ulysse Gizmos(free) for this. It may need many minutes for detection but this way you can be 100% sure if GPS īs working or not. Time optimisation for the detection is another question and there are many tweaks out there...only for the braves :-)