yashsingh1/xdaforums huggingface dataset:
[Touch CDMA Android Development] sshark:
It seems that my phone is not at all going into power suspend mode.

Whenever I click up button of d-pad, it wakes up, which was not used to happen.

Is it because of new changes in button mapping ? Any thoughts?
[Touch CDMA Android Development] enatefox:
keith, there's no such thing as a stable version at this point. We have a very stable setup but I wouldn't officially call it that. Just keep updated with the downloads and help test and you'll see along with us what works and what doesn't. While I and many others have a good experience with it, many also have issues with purportedly similar setups.
[Touch CDMA Android Development] akyboy:
Hi

Last night i downloaded

rootfs-20-08-09.img and zImage-20-08-09

Battery live is,... actuality there is no one--- batery drained in 4 hours! No one call made.

Also, when coming off suspend mode, i see 1sec of `terminal` screen than home screen.

Maybe u guys can take a look at this when u have time.

Luckily i had my old, previous versions, i put it back and my phone was alive again! ;)

Just couple of toughs!

Tnx
[Touch CDMA Android Development] mssmison:
Again the bluetooth is just initial work. I can confirm that battery life is much less even with the bluetooth not enabled. Really though for this point it's only the initial release. It will improve.
[Touch CDMA Android Development] akyboy:
ok ok , so battery life is decreased because of BT?

if yes ill go back to previous version ....

should i change (go back) both of the files or just one of them
[Touch CDMA Android Development] akyboy:
forgot to mention,.... but i never had BT enabled. I guess no matter?
[Touch CDMA Android Development] craig0r:
Weird... Yesterday when I first installed the BT kernel, I left BT enabled for about 6 hours, and didn't notice significant battery drainage... Yes, the battery went down slightly faster than normal, but more or less what I would've expected. What device are you on? I'm using a Vogue on Telus.

EDIT: (actually, the only reason I turned BT off was because my "Back" button stopped working when it was enabled.)
[Touch CDMA Android Development] akyboy:
Vogue on Bell here,... with old ones i could use my phone day and a half , minimum full day
[Touch CDMA Android Development] TheKartus:
I am reverting to the pre bluetooth files. I have had very serious battery life issues using that kernal.
[Touch CDMA Android Development] TheKartus:
So now I am having very serious battery issues. I have reverted to the last files before bluetooth and an using mssmision's cupcake system image.

I plugged in my phone to charge it overnight, unplugged it when it turned green and said it was full. This morning when I woke up, it told me I had less than 15 percent of my battery left. I did not use the phone all night nor did I receive any calls or texts. Background data was not on.

I hope this is not my phones battery. Could keeping it on the charger past when it is full really destroy my battery life this much? I may try a different system image and see what the issue is. My sleep mode is set to 0.

EDIT: I reformatted and got all new files, the ones before bluetooth and the cupcake build. Using my old DATA image. Going to see if the battery life improves and try to see what the issue was.
[Touch CDMA Android Development] bchi49:
Same here. I'm using the latest with bluetooth.
[Touch CDMA Android Development] grktaurus83:
This sounds like you didn't leave it plugged in over night (unless I'm just reading that wrong).

Our battery driver is not entirely accurate in reading the actual charge of the battery. This has been a known issue for a long time.

While charging quickly, batteries tend to heat up (especially lithium ion batteries) and our driver will read 100% without it actually being 100% due to the effect of temperature. So when you think your battery is full, it's actually not.

Usually leaving the phone plugged in overnight will provide sufficient time for the battery to charge as much as it can. The phone will eventually cool down (since it will stop charging when thinks it's at 100%), the actual battery reading will drop down again (closer to it's actual value) and it will start charging again.
[Touch CDMA Android Development] craig0r:
+1 to this. The first day I used bluetooth, everything seemed fine... Then all weekend, my battery would last a couple of hours and then die.
[Touch CDMA Android Development] dzo:
Looks like it's a problem with the audio system, with bt enabled it behaves differently and it doesn't go into power collapse correctly. I'll try to fix it today.
[Touch CDMA Android Development] TheKartus:
Much appreciated.
[Touch CDMA Android Development] dzo:
I've put an experimental kernel on the google code site that should hopefully fix the power collapse problem. It still doesn't do the bt audio routing properly but it's getting closer.
[Touch CDMA Android Development] pmos69:
SquashFS

Sorry if this is a dumb question, but is SquashFS supported in the latest image?
[Touch CDMA Android Development] dzo:
No, but it would be a good idea to use squashfs rather than cramfs. Anybody fancy adding the patches to the kernel, I'm a bit busy trying to fix bt at the moment, shouldn't be too hard.
[Touch CDMA Android Development] Magister2k7:
Just added squashfs 3.4 to git.

Hovewer, there is no LZMA support, and I do not think it is needed, as decompression speed is better with zlib.
[Touch CDMA Android Development] enatefox:
edit: nevermind, found how to git it.
[Touch CDMA Android Development] craig0r:
I know this isn't part of what you planned on fixing, but I want to point out that the "Back" button still doesn't function most of the time that BT is enabled. Turn it off, and the "back" button starts working right away.
[Touch CDMA Android Development] pmos69:
Thanks.

Is SquashFS support compiled directly in the kernel or is it necessary to load a squashfs module?

Tried to mount a squashfs system image at boot and failed...

losetup /dev/block/loop1 /sdcard/system.sqsh
mount -t squashfs -o ro,noatime,nodiratime /dev/block/loop1 /system

gives me

failed: no such device

I took care to gererate the image with the -nolzma option, so I don't think that's the problem.

cat /proc/filesystems does not show SquashFS anyway...
[Touch CDMA Android Development] dzo:
I've just pushed a big patch by szsoftware to rearrange the source in mach-msm, it was getting a bit cluttered. It shouldn't cause any problems but if you have made any recent changes to the source you may need to reapply them to the moved files. I may also have missed some files, if it doesn't compile now let me know.
[Touch CDMA Android Development] dzo:
A workaround for this seems to be to plug and unplug usb.
[Touch CDMA Android Development] pmos69:
OK. bit the bullet, got the sources and compiled a kernel.

I had assumed that vogue_defconfig would include squashfs support in the .config, but that is not the case. Had to make menuconfig and enable squashfs support before compiling.

But then, after compiling ok, another problem:

When booting, with the new kernel, the phone boots until it gets to the Hero lock screen. after that, it freezes.

This happens, if I'm mounting a squashfs system.img or not. Even when system.img is a CramFS image.

In the case of a SquashFS image, I took care to create it with -nolzma, but that is obviously not the problem, since the freeze happens even when not mounting any SquashFS image.

Can anything more be wrong?

As I said, I just used "make vogue_defconfig", and then "make menuconfig" to add squashfs support and compiled.

Can someone else test this?

Thanks in advance.
[Touch CDMA Android Development] enatefox:
I call samesies. I needed Zen's blank but premade data.img to get any recent build (after SuperHero and Pure Black) to boot.
[Touch CDMA Android Development] mikeastock:
Sounds on Vogue don't work

my phone won't ring or make any noises. I replaced the resources file but it doesn't seem to be working.
[Touch CDMA Android Development] craig0r:
Yeah, I noticed this myself, but it only seems to last until my phone goes to sleep. After waking it back up, the back button stops working again.
[Touch CDMA Android Development] pmos69:
Hummm. Must be doing something really dumb (what a surprise).

Compiling a kernel without SquashFS support gives me the same result. The Phone completelly freezes when the Hero lock screen first appears.

Used the .config generated by "make vogue_defconfig" without any modifications.

(help?)
[Touch CDMA Android Development] enatefox:
What build are you testing that with
[Touch CDMA Android Development] pmos69:
system-jacheroski1.6 (but it works with a downloaded kernel.)

When I say freeze, it's a real freeze. The phone is dead and does not respond to any sort of input. Have to remove battery to recover.
[Touch CDMA Android Development] enatefox:
Can you run DDM while booting? Sounds like it's getting far enough for it or ADB to connect even if it's just enough to get a system state and dump. I haven't made a kernel in a good minute and it was stock. I'll try what you did later on though. A log from DDM might be useful though
[Touch CDMA Android Development] katmandu421:
Just a note regarding bluetooth that may help testers. I think this was mentioned before, but I have confirmed that pairing works best if you first pair the devide in winmo (if you haven't already done so) and note the device name of your phone (something like WM_Yourname). Then in Android, change the bluetooth device name to match and you should be all set! This worked with my Clarion BT stereo.

A2DP said it was streaming, though no audio was coming through, same with the handsfree profile. I think these are known limitations and are wip. I'm just excited to see pairing! Can't wait for more development!
[Touch CDMA Android Development] pmos69:
Checkout htc-vogue up to the last wifi update, compiled, and it boots.

Guess there's some housecleaning to do after the last updates...
[Touch CDMA Android Development] katmandu421:
Also something I noticed (probably already known, but thought I'd throw it out there). Once you are paired with a device, there is no un-pairing. I auto-connected to my bt stereo, pretty sweet. Then when I left the car and got out of range, the phone still looks like it is connected (three dots going through the bt icon) but there is no connection. If I try to toggle off bt at this time it reboots Android...not a full phone restart, just Android.

EDIT: I found that I have to go into settings>wireless controls> bluetooth settings, long press the connected device and select "disconnect".
[Touch CDMA Android Development] dzo:
I finally got the bluetooth audio routing to work. The google code site is read only so I put a new rootfs and kernel here:

http://cs-alb-pc3.massey.ac.nz/vogue/files/

This took me days to figure out, in the end I had to create a new firmware file for the brf6300. It still has problems after power collapse so it not very usable yet but you can at least make calls using the bt headset. Seems to have fixed the back button problem too.
[Touch CDMA Android Development] canyoufindben:
I love the classics: who's build are you using? Did you start with a data.img or no?
[Touch CDMA Android Development] craig0r:
Sadly, the back button problem still remains for me. Yes, plugging in USB fixes it, but it breaks again after the phone goes to sleep.

As far as bluetooth calls go... "headset" and "hands-free" are two different profiles, I believe. I've got a hands-free set, and yes, the phone audio now appears to be routing through this device properly, however, it seems to be really scrambled and unlistenable. Of course, I would still assume that this is a result of the low-speed serial driver we're using.

I'm curious to see if it works better with a "headset" device rather than a "hands-free" device. I will try my headset when I get home from work.

Also, my hands-free device has a "phone" button on it. In WinMo, it would bring up the Voice Dial feature. In Android, it just redials the last number.

I will post all this info under the BT issue on the google code site as well.
[Touch CDMA Android Development] pmos69:
Anybody have an idea why the latest kernel kills background processes like it had a machinegun?

The previous one I was using didn't do that. (with the SquashFS commit).

With this one, my compcache hardly gets used anymore.

Before the rearrangement of the source code, that didn't happen...

Forget that... after running for a while, that stoped happening and memory started being used properly again.

Weird
[Touch CDMA Android Development] mikeastock:
I am using dzo's latest bundle I believe, I downloaded this zip http://vogue-android.googlecode.com/files/android-1.5-2009-08-08.zip. I did not start with a data.img and I have a Verizon XV6900. I have tried the a hero build and it also did not work. The sound does work though in Microsoft Windows Mobile 6.1. Its just the notifications and ring tones that don't make a sound. I also have the sound turned up all the way when I go to boot into Android. Any tips to solve the problem? Thanks
[Touch CDMA Android Development] canyoufindben:
From before you said you replaced the "resources" file, did you just put the resources.zip out on your SD card? If so, it has to be unzipped, and the "Media" folder from that zip file has to be placed in the root of your SD card.
[Touch CDMA Android Development] pmos69:
HTC Kernel sources

This could be of interest: http://xdaforums.com/showpost.php?p=4415405&postcount=1
[Touch CDMA Android Development] enatefox:
I've mentioned the verbosity of power states before and I believe that if it was at least toned down a little it would greatly increase battery life considering the sheer amount that is printed to the console. I don't know how useful it is but I can provide Dalvik debug dumps. Taking a screenshot of my phone while sleeping, it is still printing power states. I attached an example. What can be done? I think if we could have a test kernel that suppressed this and compared the performance it would be striking.
[Touch CDMA Android Development] dzo:
Firstly, when usb is plugged in it never sleeps so your screenshot doesn't mean anything.

Secondly, when it is asleep the application CPU is completely powered down so it can't print anything. It only gets woken up by the modem processor. There are probably power savings that can be made but I'm afraid it's not as simple as not printing some messages.
[Touch CDMA Android Development] enatefox:
Well, I know that oftentimes the priority of a process is affected by verbosity. I posted the screenshot just as an example of what the console is constantly printing-- along with wifi messages if applicable. Just seems like if it was less noisy, it would at the least be able to run faster without the need to wait for the print command.

I know it would probably be splitting hairs, but for example, it's generally more acceptable in PHP to print with apostrophes versus quotes as it can execute faster even if not by much so not printing to stdout might help a little. That and I don't really know enough to go and try it myself.
[Touch CDMA Android Development] craig0r:
Bluetooth and Rogers build

OK. Loaded up the new rogers build with the second-to-newest kernel with bluetooth (with proper power management, but not audio routing.) Turned on bluetooth, paired with my T505, seemed cool. Rebooted to WinMo (where BT was turned off), switched to the new kernel/rootfs (WITH audio routing) and then booted back to Android. Now the blue LED is blinking, indicating that the BT hardware is turned on, but the Android settings indicate that it's turned off.

When I try and turn it on, it hangs for a bit, and the settings continue to indicate the bluetooth is off, but the LED is still blinking. I did a logcat during the process of "turning it on," and immediately got the following:

V/LocalBluetoothManager( 519): setBluetoothEnabled call, manager didn't return success for enabled: true

Went back to WinMo, turned BT on there, went back into Android... same deal. Also reverted back to the previous kernel/rootfs, and it did not resolve the issue.

It's like Linux has remembered the "Enabled" state of Bluetooth, and Android has forgotten it, and is not polling the Linux kernel/driver to find out the current state. I didn't have this problem in Ion, so it would seem like a Rogers-specific issue. I will try wiping my data.img out, trying this again, and try turning off bluetooth before rebooting, see where it gets me.

EDIT: OK, I'm getting dizzy with all the different things I've tried.

Here's a summary. The newest kernel breaks the bluetooth on reboot, whether you turn the phone off with bluetooth enabled, or disabled. Reverting to the previous kernel at this point does nothing to fix it.

The previous kernel seems fine, although if you leave bluetooth on and reboot, it SEEMS like the problem is still there, it just takes a little longer to enable.

ADDITIONAL NOTE:

Now, when starting with a new data.img, one thing I noticed when turning on BT is this line in logcat

E/AudioService( 149): Invalid routing action. Node A2DP does not exist.

Don't know if that means anything bad, or if it's just because there was no A2DP device to connect with when BT was turned on.
[Touch CDMA Android Development] dzo:
Try "echo 0 > /sys/class/rfkill/rfkill0/state" from a root shell, that should turn bt off.
[Touch CDMA Android Development] enatefox:
If that turns it off, I (someone) can make a Gscript button to toggle for now while it's being worked on:

#!/bin/bash
if [ "0" = `cat /sys/class/rfkill/rfkill0/state` ]; then
echo 1 > /sys/class/rfkill/rfkill0/state
fi
if [ "1" = `cat /sys/class/rfkill/rfkill0/state` ]; then
echo 0 > /sys/class/rfkill/rfkill0/state
fi

Which could clearly suck less but that should toggle it.
[Touch CDMA Android Development] craig0r:
It doesn't seem to fix it. Yes, it does turn the BT hardware off because the blue LED stops blinking, but Android refuses to turn it back on still. Again, this is only on the latest kernel. If you're on the previous one, it seems ok.
[Touch CDMA Android Development] grktaurus83:
The reason why BT wouldn't turn back on with the code that was posted (assuming you are using that code) is because the first if statement sees that BT is off and turn it off, and the following if statement sees that BT is on and turn it off. Both statements execute and the last statement just happens to be the "off" statement. They need to be set up so that only one of the two commands is run and not both.

The above code merges the two individual if statements into an if and else if statement.

Shouldn't the code read like this?

#!/bin/bash
if [ "0" = `cat /sys/class/rfkill/rfkill0/state` ]; then
echo 1 > /sys/class/rfkill/rfkill0/state
elif [ "1" = `cat /sys/class/rfkill/rfkill0/state` ]; then
echo 0 > /sys/class/rfkill/rfkill0/state
fi
[Touch CDMA Android Development] enatefox:
Yea, I forgot if it was elif but assumed that even if both if's were tested only one would be true. Completely didn't see that... the script you posted is right.
[Touch CDMA Android Development] tallnerd1985:
HaReT

I got a question for the programmers here on the board about seeing if this would be a quick easy task or labor intensive job. How hard would it be to update the GUI for Haret to allow for a easier way to edit the default.txt file to change the screen resolution, processor speed, lcd density and etc, etc?
[Touch CDMA Android Development] enatefox:
Word mobile is good enough for me but I don't ever touch the default.txt file. The source for Haret is available though
[Touch CDMA Android Development] bchi49:
Anyone got bluetooth tethering working? http://androidactivity.com/
[Touch CDMA Android Development] enatefox:
So, I've had some issues with headphone audio even if I start the player with them plugged in. It was working great a while ago and I hadn't messed with it since. Is it safe to say that if I pull the latest kernel from git that all of the recent changes and additions will be included? I'm pretty sure but just wondering if there's some additional steps that were needed before/after running make menucfg
[Touch CDMA Android Development] thoughtlesskyle:
not to clog up this thread with stupid stuff but i looked and wasnt able to find a clear cut answer, but is there anyway to make the red key function like the camera button and make the camera button the end key

i have been thinking about it and i think for me that would have the best functionality, im not good with deving or the like, but from what i read the key mapping is part of the kernel thats why i am posting it here
[Touch CDMA Android Development] piperthedj:
who do i have to thank for this build?? THANK YOU THANK YOU THANK YOU and THANK YOU.

i been playing around with android for a few weeks now liking a little here and there... started with 1.1 and was disappointed- too slow. found old cupcake 1.5 and was semi impressed, too many apps and a little clunky. played with keiser, and hero, and tried ion. keep in mind all of these do not have normal support for my data carrier- who bythe way is US cellular (USCC) well got this build and something just said 'this is full functional' it just feels right... well i got it last night and i cant keep it out of my hands. it runs great and is super functional.

thanks again- keep up the super smashing job gents'

btw: is there a 'to do' program around for android? or a video player

and if so, how do i go about adding it?

keep rockin
[Touch CDMA Android Development] craig0r:
I had a program called "Shopping List" (or maybe one word, ShoppingList) that was a good To Do program, at least for simple task lists... it wasn't complex by any means, but you made a list with checkboxes that you could tick off as you do each item. You can find it in the Market.
[Touch CDMA Android Development] katmandu421:
Astrid is a decent to do app that has "Remember the milk" (an online task manager) integration.

For video, I've always had the native player work for me most of the time. Recently, however, vodcasts have stopped "working". what I mean is they start to play, but then the video freezes. I have no idea when this started happening. Is it a kernel issue? It's like it runs out of memory for buffering the feed.
[Touch CDMA Android Development] pmos69:
noop I/O scheduler

Just wondering:

What's the default elevator used by vogue kernel?

Shouldn't the noop elevator be used?

Will adding "elevator=noop" to the cmdline in default.txt do the trick?
[Touch CDMA Android Development] enatefox:
default is anticipatory. noop is the only other option
[Touch CDMA Android Development] pmos69:
Just tested adding elevator=noop to default.txt and it is applied correctly as system default.

I suggest the vogue default.txt in the kernel sources should probably be updated with this parameter.
[Touch CDMA Android Development] craig0r:
What does this do for us?
[Touch CDMA Android Development] enatefox:
It did this for me:

http://xdaforums.com/showpost.php?p=4448936&postcount=1150

Notice that some aspects took a penalty while others gained from the setting. I ran them back to back on an already running system (so there was no lag to account for)
[Touch CDMA Android Development] pmos69:
noop should be the most adequate io scheduler for flash based storage devices like the ones we are using.

(Although some good results can also be obtained with the deadline scheduler on some SSDs)

You can read a bit about linux io schedulers here, for example: http://linux.com/index.php?option=com_rubberdoc&view=doc&id=12&format=raw