yashsingh1/xdaforums huggingface dataset:
[Desire General] cez10:
to be honest i dont care bout the size of attachments and the size cuz i know i got lots left anyway, and im not sure about trusting google with emails after the rumours of them reading the emails. lol
[Desire General] Barff1984:
anyway so back to the point

is Android here to stay?

or do people think Winmob 7 will be better?
[Desire General] cez10:
for me as a normal user/ graphic designer windows phone 7 is a total failure, it looks like a candy for twit-facebook addicts having trouble with their sight needing big buttons text etc.

definitely prefer droid and winmo6.5
[Desire General] irkan:
Android will stay, WM7 will have to prove itself, and it will be difficult cuz it will be too locked (just like iCrap) it will be hard for WM7 to gain market shares at the beginning considering that the platform will be brand new (very different than other WM) and with the bad reputation the WM brand generated through out the past years.

I can easily say android is a very safe choice right now
[Touch Diamond, MDA Compact IV Themes and Apps] beblioy:
i can't connect my phone and my pc with remote desktop:confused::confused::confused:
[Touch Diamond, MDA Compact IV Themes and Apps] beblioy:
http://www.youtube.com/watch?v=axULHGCt98o&feature=player_embedded what is this kimoshi.net ?
[Hero, G2 Touch Q&A, Help & Troubleshooting] Piercy0812:
i cannot seem to get mms working on any of the villain roms. i had the way before mmszap working once, but all upgrades after i havent been able to do it. The apn settings seems correct.

I am on a Vodafone uk 18 month contract.

can anyone help with this please. Other people have said its working i just cant get it working for me :/
[Hero, G2 Touch Q&A, Help & Troubleshooting] nprussell:
It works out of the box on 4.0 Beta 2, but I haven't yet tested in 5.0
[Hero, G2 Touch Q&A, Help & Troubleshooting] Gr3m1in:
by all accounts its broken in 5.0 again
[Hero, G2 Touch Q&A, Help & Troubleshooting] nprussell:
That'll be due to the CDMA origin of the rom I'd guess.

MMSZap for now if it's essential to you. Try the old, manual version - I hear it's less intensive on the battery.
[Hero, G2 Touch Q&A, Help & Troubleshooting] Gr3m1in:
Figured as much mate

just created a bug tracker issue about the 5.0 MMS issue on behalf of everyone so its not posted across all these different threads

anyone else havign this issue please confirm/post about it on its bug tracker entry here http://www.villainrom.co.uk/bug/view.php?id=91
[Hero, G2 Touch Q&A, Help & Troubleshooting] Devkoko:
Try to switch in MMS and Internet APN "Authentication Type" to "PAP or CHAP"

It worked for me in Orange Poland
[Nexus One Android Development] jblazea50:
Do you use the xtra version, if so have you noticed any problems
[Nexus One Android Development] britoso:
Nice release, will definitely try sometime.
[Nexus One Android Development] seanowns:
Grrr!!! checked for updated version right before leaving for work, and just missed it!

I am using the one you posted in the other forum without any issues. Does it possess the same undervolting as the Xtra version?
[Nexus One Android Development] Ivan Dimkovic:
Yes, _xtra is using same undervolt as the version from yesterday.

Additionally, this version contains more optimizations (loop unrolling) that I managed to cram-in by removing more debug options of the kernel (otherwise it would not fit)
[Nexus One Android Development] pzumk:
What is loop unrolling?
[Nexus One Android Development] hotweiss:
Awesome, I'll pull the config to see what you have done...
[Nexus One Android Development] RaistlinMaje:
just installed on my device. so far so good, using the extra undervolt. booted fine and everything so will report back later if I notice anything weird.
[Nexus One Android Development] die-hard:
Hi man, in first thanks for this work...

Now can u tell me how can i use your kernel?

Thanks in advanced
[Nexus One Android Development] pzumk:
just

[power off your phone and boot into fastboot]

fastboot flash zimage zImage

[reboot]

adb remount

adb push bcm4329.ko system/lib/modules/bcm4329.ko
[Nexus One Android Development] intersectRaven:
interesting...I've been experimenting with the compiler optimizations in my own build...it made the kernel bigger although I feel a bit more responsiveness now...almost not noticeable but I think its there...
[Nexus One Android Development] Ivan Dimkovic:
Loop unrolling is the optimization technique used by modern compilers to potentially speed-up execution by decreasing overhead of the loop passes.

For example, imagine that you have a loop, that does something 4 times:

for(x=0; x<4; x++) {
do_something;
}

In this case, some % of the execution will be checking if the x is less than 4, and if no - "doing_something" again. This check has to be performed for every step (so, it is done 4 times)

Now, if you unroll this loop, it would look like this:

do_something; x++;
do_something; x++;
do_something; x++;
do_something; x++;

^ So, in this case, we completely eliminated checks.

Or, if the loop is much bigger (say, x goes up to 800):

for(x=0; x<800; x+=4) {
do_something;
do_something[x+1];
do_something[x+2];
do_something[x+3];
}

See? In this case, you reduce the number of condition checks for bigger loops.

This can sometimes make code faster - but the downside is that it makes the code bigger (which is obvious even in those examples above).

In Android Kernel 2.6.33.1 case - loop unrolling increases zImage size by ~350K. If I didn't strip debugging stuff out, zImage would be too big to fit on Nexus One.

Fortunately, there was approx. 400K to be saved by just kicking out features that enable kernel debugging. I don't think most of the people need that. These features are useful for kernel and driver developers, but most of others can perfectly live without them :)
[Nexus One Android Development] pzumk:
Alright, thank you!

will try _xtra when Paul released the new Desire cam. Thanks for your work
[Nexus One Android Development] sir*mez:
on point. i like what i see. i will try this out.
[Nexus One Android Development] bethedealer:
If I use the powersave governor option, SetCPU always show it running at minimum 245MHz. Is it working as expected?
[Nexus One Android Development] intersectRaven:
That's fine since the powersave governor clocks it to the lowest for maximum power savings. :)
[Nexus One Android Development] pzumk:
standby 245/245 governor is better than on demand?
[Nexus One Android Development] mgear356:
Curious about this too!
[Nexus One Android Development] intersectRaven:
It's not necessarily better. It depends on what you're optimizing for. For example, powersave governor optimizes for power savings in return for slowest clock speed which may be apparent when using CPU intensive apps. Ondemand tries to balance it somewhat while giving more importance to CPU speed since it clocks the CPU back to full speed whenever an app runs and downclocking when appropriate. The conservative governor I use in my kernel also tries to balance this but gives more importance to power savings since when an app runs it slowly ramps up the clock speed until the app finishes. Hope this clears it up! ;)
[Nexus One Android Development] Ivan Dimkovic:
Note that powersave might actually consume more power at the end if you do some intensive work.

Why? Because it will force CPU to stay at the lower clock, even if the task could be completet much quicker with the higher clock.

At the end - it could very well be that running the task quicker @higher clock speed could consume less power total!

Unfortunately, there is no easy way to test what is better, unless someone writes a script that performs some tasks repeatedly until battery dies, and compares the baterry life between different CPU scaling strategies.

I'd definitely not use powersave governor. Rather, I'd play with the "up threshold" and "profiles" in SetCPU to make the CPU frequency scaling more conservative.
[Nexus One Android Development] milton007:
Please DONT lend assistance to someone like this. IF they cant bither to read THE MOST SIMPLEST instructions, they should NOT be attempting this in the first place...thats just sheer ignorance...
[Nexus One Android Development] Ivan Dimkovic:
Yes, all my kernels include audio boost.
[Nexus One Android Development] www1:
Can U made a version with stock speed and not OC?

Thanks
[Nexus One Android Development] seanowns:
1.05 AVS feels great. I've noticed my Juice Defender seems to work faster now as well. All around great kernel thus far.
[Nexus One Android Development] christiankk:
one random reboot so far.

tried making a phone call and now the other party can hear me! :eek:;)
[Nexus One Android Development] hotweiss:
Well I also had reboots with 1.04 (non-avs), so I guess that my CPU can't handle the voltage. Thanks, I will keep on following your kernels.
[Nexus One Android Development] konrad1337:
Well, I have been running 1.05 AVS non OC'ed and after about 3-4 random reboots or reboots because of a system hang, everything seems golden now. Haven't seen many issues since the reboots stopped.
[Nexus One Android Development] pzumk:
I did flash the normal kernel (no avs) but the kernel info sais uv_avs_oc .. #42 ??
[Nexus One Android Development] Ivan Dimkovic:
It is OK - non-AVS kernel is still not updated - this is just a signature. Package is OK, and kernel is not using AVS.

I have to write a script to build all those kernels and change settings appropriately :)
[Nexus One Android Development] pzumk:
okay thanks for the fast reply :)
[Nexus One Android Development] Ivan Dimkovic:
Interesting read - this patent application seems to describe how AVS works:

http://www.faqs.org/patents/app/20090031155
[Nexus One Android Development] seanhassars:
Thanks so much for this, I'm loving the AVS OC UV kernel. After 10 hours with 3g and wifi enabled along with a moderate amount of texting, I was only down to 70%. VERY impressive if you ask me.
[Nexus One Android Development] fleebailey33:
So far very good on the AVS undervolted. Not OC'd

Very stable!
[Nexus One Android Development] christiankk:
hmm - i can run this kernel stable for about 24 hours and then things go crazy and I can't get the phone to startup, it just hangs. :(

i am giving intersects a shot.
[Nexus One Android Development] decayed.cell:
Which ROM are you using
[Nexus One Android Development] carlos805424:
im a newbie

can sumone plz like help me out by putting full written instructions here because im totally lost im sorry for my dumb question lol :p
[Nexus One Android Development] decayed.cell:
http://xdaforums.com/showpost.php?p=6019458&postcount=10
[Nexus One Android Development] stryker759a:
What are you having trouble with?
[Nexus One Android Development] St.Jimmy!:
Going to test AVS NO-OC out tomorrow. I'll post with results!
[Nexus One Android Development] solidmac:
every time i flash the NORMAL diet kernel and boot up i check the "about phone" section, it says i flashed the 2.6.33.1-psyq_uv_avs_oc!!! Is it suppose to say that because I dont want to brick my phone for improper labling of the zip files.
[Nexus One Android Development] SimFox3:
Tried the AVS No-OC with the Emon's ROM. I made sure to clear the dalvik-cache (i hope that's the cache everyone is talking about) using Amon Ra.

First boot, crashed and rebooted when configuring SetCPU profiles.

Second boot, rebooted again when configuring setCPU.

Afterwards, the device would never boot. It would keep rebooting, but never actually get to the unlock page. I waited about 6 reboots before restoring a recent nand backup.
[Nexus One Android Development] b1337:
Re: Diet Kernel for Nexus One (CM 5.0.5.3), incl. undervolting+OC + TEST AVS SUPPORT!

mine took about twenty five boots before she started purring...ride it out see what happens for ya
[Nexus One Android Development] solidmac:
i flash the NORMAL diet kernel and boot up i check the "about phone" section, it says i flashed the 2.6.33.1-psyq_uv_avs_oc!!! Is it suppose to say that?
[Nexus One Android Development] jlevy73:
That is correct.
[Nexus One Android Development] seanhassars:
latest version of cyan with the latest nextheme skin
[Nexus One Android Development] solidmac:
thank you so much for clearing that up i was so confused because i dont want avs i just wanted the normal "stable" one which is the first attachment on the list "psyq_2.6.33-1.diet_kernel.zip"
[Nexus One Android Development] St.Jimmy!:
I come from kmobs UV Kernel and feel that my battery life is completely gone. I made 2 or 3 2-minute calls and i'm already at 94%. I don't think that was like that before. It took a lot longer to pass the 95% "barrier".

I'm tired of reading 15hrs - 70% battery everywhere thanks to AVS. I'm on AVS NO-OC and for now (1 hour since last charge) it doesn't look as I'll be getting those results.

Any comments or feedback on that? Anyone else in my situation?
[Nexus One Android Development] solidmac:
i think those people use alot of background apps and dont use their phone as much as you do. i find 15hrs and only use 30% battery life to be a bit odd if you are using the phone moderately
[Nexus One Android Development] jblazea50:
i usually lose about 7-10% battery life for like 45 minutes of continuous browsing websites

i'm on the AVS no OC kernel
[Nexus One Android Development] St.Jimmy!:
I've lost 15% for having my phone on standby for about 3h and receiving a few calls, maybe 2 or 3 1-minute calls.
[Nexus One Android Development] seanhassars:
make sure you're using setcpu, governor is ondemand, and enable the charging and standby profiles
[Nexus One Android Development] jblazea50:
maybe you have background apps that are syncing very often

anyway, i also have setCPU configured (3 different profiles along with charging and standby, which is set to max 245)

what's your screen brightness level? is your 2G/3G always on? i leave my wifi always on, but when it standby, wifi is killed;

i don't lose much battery life while in standby/idle mode
[Nexus One Android Development] jblazea50:
Ivan, any chance of you updating your kernel with .33.2 with the 8MB of free ram along with your UV/OC with AVS?

the latest kernel by pershoot (.33.2 with 8MB RAM free) is very responsive and fast; it would be great if you can implement those changes to your fantastic kernel

thanks
[Nexus One Android Development] Ivan Dimkovic:
Yes I definitely plan to do it... it will most likely happen on Wednesday if I manage to grab some free time... :)
[Nexus One Android Development] jblazea50:
awesome, will be trying it out whenever you release it
[Nexus One Android Development] seanowns:
Agree with the others. The new OC/UV kernel is very fast. Feels faster and benchmarks improved even.

Would love to get that thing included with AVS and other optimizations.(That was my favorite up until this recent 8mb thing)

I love trying all of these kernels!
[Nexus One Android Development] stryker759a:
How do you do this enable the charging and standby profiles? Im running this

psyq_2.6.33-1.diet_kernel_AVS.zip .

Jason

Nm Figured it out.
[Nexus One Android Development] Mantisen:
I love the UV AVS kernel! My phone stayed alive for a bit more than 45 hours with wifi and 3G up constantly. Some phone calls, texts and gaming on that as well! Truly great work! Can add that the battery was at 94% charge when I unplugged it as well.

Typing this from my phone but I'll upload a screenshot of the battery screen when I get a chance.

EDIT: Screenshot up now :)
[Nexus One Android Development] hugonz:
Ivan,

I just noticed this in the AVS kernel documentation:

"AVS assumes it is the only process changing the supply voltage. Other coprocessors must not change the Scorpion voltage. The bootloader must not change the Scorpion Voltage when warm booting from power collapse."

It could potentially be the source of instability. As far as I know/can tell, the bootloader sources are not published, however it'd be pretty easy to add some debug hooks to log voltages on power collapse and verify that they haven't changed on warm boot.
[Nexus One Android Development] Ivan Dimkovic:
This is a good find! I will definitely add some traces to check the voltages on the boot.

On the other hand I find it hard to imagine that the bootloader is dealing with the voltages - but that one is not so hard to check.

My bigger concern is reboot issue after cold booting that some people are getting, too...
[Nexus One Android Development] xandr00:
should be...

[power off your phone and boot into fastboot]
fastboot flash zimage zImage
[reboot]
adb remount
adb push bcm4329.ko /system/lib/modules/bcm4329.ko

not sure if anyone else stated it or not but I had some trouble pushing it onto the device because i didn't put / in there. :) haha
[Nexus One Android Development] intersectRaven:
Interesting find! I just tested an edited AVS now and I got a boot loop. But I really think there's something here. The problem seems to be that the arch-init-scorpion.c file changes the scorpion voltage to boot from power collapse.

*I'm not pretty sure yet since it was just a quick browse through the file. :p

** After reading through...its not there...I think... :p
[Nexus One Android Development] St.Jimmy!:
13 hours since last charged, 50% battery with normal use (AVS version)
[Nexus One Android Development] jazzor:
has anyone had any success of having it idle UNDER 1000 mv? It seems that the cpu can and will request a lower voltage if you allow it however the voltage regulator does not seem to be able to set such voltage (not even 975mv) despite being in its voltage table (look at the voltage regulator source). perhaps a hardware restriction?? Nevertheless, I would have thought with AVS we could do better than 1000mv at idle... could be worth a look anyone?
[Nexus One Android Development] jazzor:
Nevermind my previous post. After mucking around with board-mahimahi ive managed to successfully let AVS scale the voltage down to 925mV during idle (I lowered the voltage constraints to 800mV-1300mV as per tps65023 specs). It looks like that is as low as AVS is willing to set it. Going to check stability and battery savings now, hopefully no hw dmg either...
[Nexus One Android Development] Ivan Dimkovic:
Good find jazzor!

Please let us know about the stability results, if it is stable enough I'll also add it in my kernels.
[Nexus One Android Development] intersectRaven:
This would be interestingly nice for AVS if ever since it could scale lower. :)
[Nexus One Android Development] Ivan Dimkovic:
I just enabled voltage scaling down to 0.8v - will test this today on my phone and if it is stable enough (meaning... "AVS stable" unfortunately) I'll integrate it in my kernels, too.
[Nexus One Android Development] Ivan Dimkovic:
Looks like no luck here with my phone - it is in the endless reboot cycle with 0.8v

I will try to set the limit to 0.925v and see how it goes
[Nexus One Android Development] Ivan Dimkovic:
Ok

It boots with 0.925v set as the minimum voltage - let's see how it goes.

I have to investigate more why is 0.8v breaking it - this was just a quick hack, maybe something is trying to set that minimum voltage at the inappropriate time.
[Nexus One Android Development] eboy44:
dont know what im doing wrong im on CM 5.0.5.3 tried updating kernal it worked then when i pushed the .ko files i got infinite loop and then just freezing on the nexus loading...ended up doing a nand restore...

any help will be appreciated
[Nexus One Android Development] vegetaleb:
Does it work with ENOM 1.8.1?
[Nexus One Android Development] Ivan Dimkovic:
Note,

I added "super_avs_test.zip" which is the kernel running AVS and going down to 0.925v. Early birds can use it to see how stable it is. If you end up with endless reboot, please post it on this forum.

Unfortunately I am too busy during this week with my regular work - but over weekend I will be migrating to the latest CM source and also adding some more things.

Note - super_avs_test kernel also has overclocking, but you can easily disable it by setting the maximum frequency to 1 GHz in SetCPU.
[Nexus One Android Development] youkell:
Thanks for the new super kernel. So far so good. No reboot problem =)
[Nexus One Android Development] eboy44:
the new kernal also gave me a endless reboot...
[Nexus One Android Development] Ivan Dimkovic:
@eboy44

When do you get the restart - does the boot animation show up, or the phone reboots on the initial screen?
[Nexus One Android Development] eboy44:
i get bast the initial boot screen then where the animatiion comes i get infinite loop
[Nexus One Android Development] Harry454:
how do I remove the bcm4329.ko file I uninstalled the kernal was giving me signal problems
[Nexus One Android Development] Ivan Dimkovic:
You just need to copy the bcm4329.ko to the same place, from the kernel you are using.
[Nexus One Android Development] seanowns:
Just flashed SUPER AVS. Booted up fine. Will report tomorrow.

*update*

Just ran the set cpu stress test for like 15 minutes straight with 0 errors. Phone is at 30.6C which seems good too after stressing it! Will report back further tomorrow for real this time:)
[Nexus One Android Development] :
problem

Hi

After flash diet kernet I've got some trouble with bluetooth connection to my car: connection been lost from time to time. Part of logcat dump you can see below:

I/bluetooth_ScoSocket.cpp( 187): Listening SCO socket...
D/ActivityManager( 106): Uninstalling process com.android.bluetooth
D/ActivityManager( 106): Force removing process ProcessRecord{460ff3c0 288:com.
android.bluetooth/10031} (com.android.bluetooth/10031)
W/ActivityManager( 106): Scheduling restart of crashed service com.android.blue
tooth/.pbap.BluetoothPbapService in 5000ms
W/ActivityManager( 106): Scheduling restart of crashed service com.android.blue
tooth/.opp.BluetoothOppService in 14998ms
D/CachedBluetoothDevice( 1780): onProfileStateChanged:[]
I/Bluetooth HeadsetBase( 187): headset read error 5
V/BluetoothEventRedirector( 1780): Received android.bluetooth.headset.action.STA
TE_CHANGED

With native CM-kernel all is ok.

How can i resolve this problem?

Thanks in advanced
[Nexus One Android Development] intersectRaven:
Odd...I tried 800 Mhz on my private build and its been stable so far. Maybe another case of CPU variance. :(
[Nexus One Android Development] Ivan Dimkovic:
New update:

V1.06 - Update

- Moved to kernel 2.6.33.2 from Cyanogen's 5.0.5.6 source
- AVS kernels are capable of undervolting down to 0.925v instead of 1.000v
- Minor cleanups

I will be looking into 0.8v issue further...
[Nexus One Android Development] Ivan Dimkovic:
Which variant of the kernel are you using? Diet, AVS or AVS+OC?
[Nexus One Android Development] Ivan Dimkovic:
I just re-enabled 0.8v again, now on 2.6.33.2, and double checked everything - still the same result :(

Reboot occurs even before boot animation. Looks like another problem which is related to individual CPUs.

I will keep it @0.925v for now. Let's see how many people will have those early reboots with 0.925v.
[Nexus One Android Development] zdiamant:
AVS seems to cause endless loop on boot. non AVS works like a charm... And not just yours... Could it be that I have one of those processors that won't allow me to use AVS?
[Nexus One Android Development] Ivan Dimkovic:
Are you getting to the boot animation?

If yes, try wiping the battery stats and cache, and try few more times. Weird as it sounds, but it is known that this works for some people after series of reboots (!)

If you are getting to the boot animation, I believe it is not the CPU which is an issue - it is just that our AVS support is "patched" to a different kernel, which has different Qualcomm codebase. It appears that the N1 codebase is doing something which just does not work well with AVS for some.