yashsingh1/xdaforums huggingface dataset:
[Touch CDMA Android Development] Magister2k7:
It works for me, but without GPS. Hovewer, I am using old 1.0 SDK build, and it runs almost normally.

Hovewer, there is no market... but 3D works ok :)

For now, I'm looking to try 1.5 built from source, maybe it will be better.

Also, kernel module compcache will help somewhat I think.
[Touch CDMA Android Development] thoughtlesskyle:
what about running the new 1.5 build with the swap file, from what i have read from the threads it acts like virtual memory does on a computer. i would give it a try and see what it does
[Touch CDMA Android Development] Magister2k7:
I do not think it is a good idea, as flash card is much slower than RAM, and repetitive writes will destroy it faster.

Compcache is the interesting thing, it uses some RAM to create a compressed swap, so the speed is good.
[Touch CDMA Android Development] craig0r:
There seems to be a problem.

The past couple days (I'm on all the latest system files, and have tried various system.img builds) a large amount of crashes have begun. Most of them appear to be related to the radio.

For example, on the latest mssmisonsystem.img from 2 days ago, com.android.phone crashes as soon as i try and dial out. On the more recent mssmisonrogers.img, it sometimes does calls fine, and sometimes resets the phone either when I make a call, or shortly following the call. On one of the non-themed builds from 5 days ago (can't recall which one I had downloaded) com.android.media (or whatever it's called) would constantly crash, and i had no audio except for in calls... this last one appears to be a seperate issue, and logcat suggested trying a fresh data.img, which I am presently about to try out.

It's the end of the work day, and I just want to get stable at this point. I can do some more messing around tomorrow and see if I can find any errors in dmesg/logcat.

EDIT: So far the build from 5 days ago is ok. Media's working fine with a fresh data.img, so that part isn't important.
[Touch CDMA Android Development] TheKartus:
I am also getting that com.android.media crash everytime I get a text, not sure about a phone call. It also happens when I try to access ringtone settings. It started after I switched back from Pre themed to Ion and is still crashing with the latest Ion build.
[Touch CDMA Android Development] craig0r:
I started with a fresh data.img and this problem seems to be gone. However, both myself and Ace2017 in the IRC room are having the radio issues with newer builds.
[Touch CDMA Android Development] TheKartus:
Right, I'll give the fresh data image a try. Even though I hate doing that. Maybe I have an older one saved I can revert to.
[Touch CDMA Android Development] vilord:
I'm still waiting for *somebody* to give me logs of what is happening, phone works perfectly for me, so I can't fix it unless I know what is wrong...

Same with the application crashes, we can't fix it without logs. App crashes need a logcat, radio issues need a logcat -b radio.

EDIT: Also regarding compcache... we already have very little ram, how would it help to take up ram and set it aside as VM?? This doesn't make much sense to me, cause then the OS would need to do more swapping in and out of the compcache....
[Touch CDMA Android Development] TheKartus:
Sorry, I don't have the adb connection setup to get a logcat of the crash. craig0r seems to have found the fix to my issue though, it seems its something wrong in the data image caused by the pre theme. His radio issues are another story.
[Touch CDMA Android Development] vilord:
My guess about the media crash issue is that it is trying to use a media file that doesn't exist....

I'd make sure that your media files are still in the /sdcard/media folder instead of just /sdcard as is used by the hero themes....
[Touch CDMA Android Development] TheKartus:
They are, or should be. I'll check just in case. It was a themed Ion build though, not a hero build. Which makes it a weird issue.
[Touch CDMA Android Development] vilord:
What i mean is that PRE probably included a bunch of sounds and ringtones internally, and your data file was likely pointing at one of them... then switching back to ion, which has nothing included, caused the issue... You'd want to somehow load back up pre and change to a ringtone and text message notification sound that is only on the SD card.
[Touch CDMA Android Development] TheKartus:
Right, I understand now. That makes sense. I'll see what I can do.
[Touch CDMA Android Development] craig0r:
I will get these to you tomorrow at some point. I need my phone to be stable tonight, and don't have time to mess around with it.

I had built my own kernel today, so until about 4:00, I had written off my crashes as a result of that, and was trying it with different builds.
[Touch CDMA Android Development] femmyade2001:
Incoming call contact

With the hero builds, does anyone know how to make the contact name show up on an incoming call rather than just the number?

...by the way, great job on the recent hero build. It really is super fast!
[Touch CDMA Android Development] femmyade2001:
...and is there anyway to reduce the frequent re-loading of the home screen?
[Touch CDMA Android Development] craig0r:
This happens due to lack of ram. When android's memory starts filling up, it quits idle apps. Maybe it can be fixed, so that the Home screen is an exception to this, but at the same time, that'd slow the rest of the apps down, because the home screen is what takes up ram and slows these builds down anyway, from what I understand.
[Touch CDMA Android Development] craig0r:
WELL! I've reloaded the rogers rom with a fresh data image, and it seems to dial ok. I just figured since Ace2017 and I got the same issue at the same time that it was a bug.... If this changes, I'll grab some logcats.
[Touch CDMA Android Development] femmyade2001:
Thanks, craig0r. I changed the RAM settings in my default.txt, and it is waaaaay much better!:D
[Touch CDMA Android Development] TheKartus:
Fixed the RAM settings? Added more RAM to be accessible to Android?
[Touch CDMA Android Development] vilord:
wish I could just edit my default.txt to add more ram, that'd be cool!

But i think we're already set right... unless we should be setting our ram to 160MB instead of 128MB? The 0x8000000 number is already 128 megs...
[Touch CDMA Android Development] enatefox:
tl;dr-- sorry if this is a stupid question

I thought the RAM spec in default.txt was hardware-dependent. What exactly would you be taking it from? Doesn't seem like an editable thing to me. I can't tell my laptop that I have 1Tb of RAM. As far as I know, things like enabling GPS in WinMo can affect it in Android so I don't think it's cleanly booting into Android and for that matter Haret so is there some remnant process that would be affected?
[Touch CDMA Android Development] TheKartus:
The only thing I can think of that was meant by that, is that we only allot a certain amount of the Vogue's RAM to Android in the default.txt. If that number were changed to a larger percentage of the Vogue's RAM it would run faster?

I am not sure if that is what the original poster meant, but that is what I took from it. I am not sure of how much physical ram the Vogue has to compare the numbers. If we are not using all of it? Why aren't we? Was there an issue in trying to use it?
[Touch CDMA Android Development] enatefox:
HTC Touch P3050 (HTC Vogue 100) and ATT Tilt/Kaiser:

RAM capacity: 128 MiB

ROM capacity: 256 MiB
[Touch CDMA Android Development] vilord:
the vogu100 kaiser, and polaris all have about 160MB of internal memory, but a bunch of it is reserved for the radio and wifi functionality, so we get about 128 megs effective memory... this isn't posted in most of the specs.

but before anyone gets any bright ideas, the 8000000 number in haret is in HEX, so it is already 128MB, don't go changing it to 0x128000000 as thats a lot more than you actually have :)
[Touch CDMA Android Development] TheKartus:
I wish that worked. We'd be running Sense UI better than the Hero.
[Touch CDMA Android Development] enatefox:
I'm going to try this when I get home. Should be compatible with Vogue as well.
[Touch CDMA Android Development] okcoolthnx:
I tried this with my Vogue, but couldn't get the phone to recognize the extra RAM. Have you had any success?
[Touch CDMA Android Development] enatefox:
I tried before but the problem was I was trying to type "free -m" to check and the tape was pressing all of the buttons when I hit the dash key. Still trying to figure out why my luke-warm Pringle can air intake on my car causes loss of RPMs. I might try to use alien to convert them to DEBs. (sorry, had to)
[Touch CDMA Android Development] femmyade2001:
yea, i simply changed the 0x8000000 to 0x40000000 and that must have increased the RAM a little bit because it drastically reduced the number of times it had to re-load the home screen. Now it just goes straight to the home screen without having to re-load it.
[Touch CDMA Android Development] TheKartus:
Are you being serious? That really does not make sense and seems like selective perception or some sort of coincidence. As stated by vilord, it is already set to recognize all of the ram build into the Vogue. Adding more numbers would not do anything except maybe confuse it.
[Touch CDMA Android Development] tatnai:
what's new with GPS? booting it up . . . won't be able to test gps tonight though.
[Touch CDMA Android Development] femmyade2001:
:Dit might be some sort of coincidence, but it worked a little better. It seems to freeze up a little once in a while tho
[Touch CDMA Android Development] dzo:
Kaiser gps wasn't working for those of us in the southern hemisphere.
[Touch CDMA Android Development] enatefox:
dzo, I'm assuming that's GPS with the newer kernel you said works for the southern hemisphere? Was that specific for Vogue? Not that it matters to me but just wondering if there was some difference there.
[Touch CDMA Android Development] femmyade2001:
Has anyone tried the recent build mssmisonsystem.img: mssmison's cupcake based build. Based on latest cyanogen work with all fun donut stuff. Not themed for now. I'll update later?

I tried it but there seems to be a problem with market, it crashes out. Also, it crashes out when you try to access ringtones. SMS's however go through, with no error message.

I tried my hero data.img and it wouldnt even boot with that. Maybe i have to wait for updates?
[Touch CDMA Android Development] myshinynewtouch:
use any google ion build data.img file and make sure you log into market, select a ringtone, select a wallpaper, try to play tunes while in ion.

Once you do that, use that data.img file to launch mssmison's donut build and everything will work fine.
[Touch CDMA Android Development] vilord:
enatefox: the GPS update was for kaiser and polaris only, related to the NMEA -> SRWALTER signalling conversion.
[Touch CDMA Android Development] okcoolthnx:
Is anyone else's Messaging app SUPER slow now? I keep having to hit the "Wait" button because the "Messaging app is not responding" comes up EVERY time I do anything with sms....
[Touch CDMA Android Development] enatefox:
What would it take to get 2.6.29 working? UBIFS looks like the speed would much better although I don't know about wear leveling with it. Requires 2.6.27+ to work though. Can we git and compile with the standard toolchain or would we need a specialized one for it?
[Touch CDMA Android Development] vilord:
2.6.27 wouldn't even work properly with our stuff... so I don't think 2.6.29 is likely at this point without significant rework
[Touch CDMA Android Development] enatefox:
I realize that a new kernel is not easy but I'd like to know some specifics (seems like the right place at least) and what it would take to get it going. I'm all in favor of significant rework if I can get some info or help with it. The worst thing would be for me to try and not continue with or undo the progress that has been done already. Anything that's been learned so far should be able to remain through an upgrade right? What was done to test a newer kernel and how could it have been improved?

Sorry if this isn't where all of you are trying to take things but a lot of threads don't get into specifics and stick with concepts. I'm just hoping for some kind of detailed info on the status. Thanks
[Touch CDMA Android Development] vilord:
here is where martin got with the conversion to .27: http://git.linuxtogo.org/?p=groups/...it;a=shortlog;h=refs/heads/htc-msm7x00-2.6.27

It crashes periodically, and therefore still needs work.

He decided his time would be better spent making other stuff work, than reworking existing stuff to make it go...

Feel free to check it out and try to get past the crashing :)
[Touch CDMA Android Development] craig0r:
OK, with the 08-15 kernel, what's the new "Home" button?

Of course it's been brought up time and time again that hitting "Back" to get to the Home screen is impractical, so I'm hoping this wasn't overlooked.
[Touch CDMA Android Development] katmandu421:
Covered several times already. Go into spare parts and set end button behavior to "Home, then sleep".
[Touch CDMA Android Development] craig0r:
thanks! it's monday morning, and i knew this already... i apologize for the dumb question.
[Touch CDMA Android Development] enatefox:
Just referring the post along to people who might actually fix it: link
[Touch CDMA Android Development] vilord:
thanks nate :)

we actually already are sending AT+CPIN="4223" in this case... and it still isn't working right...

I just haven't had time to check into it, it should be a reasonably easy fix.
[Touch CDMA Android Development] vilord:
I've updated the rootfs again with newer RIL code that should hopefully not lock up on people anymore... included martin's wlan.ko
[Touch CDMA Android Development] enatefox:
Go on... do you mean lock up when people make calls? I haven't had that issue with the radio myself. Martin's wlan.ko is the original that's been modded to work with DMA and not Addisu's right? What's the status on power collapsing with it because I could not turn it off in the settings (crashed the process) and it was stuck on getting hotter by the minute.
[Touch CDMA Android Development] vilord:
I don't know where the wlan.ko came from... it is something that martin uploaded last night, and I'm just including it... it may be addisu's, or not, I really don't know.

Same deal with power collapsing with it... I think we need user wakelocks support added to the kernel before that will work, but I haven't even touched it :)
[Touch CDMA Android Development] enatefox:
I feel like I'm showing how to dribble a basketball in front of the Globetrotters but: http://www.kandroid.org/android_pdk/power_management.html
[Touch CDMA Android Development] vilord:
yup... that all doesn't work on our kernel, hasn't been implemented :)
[Touch CDMA Android Development] enatefox:
So 2.6.27+ then for it? I'll take a look at what dzo did but I'm having some issues if anyone has any guides to follow. I can cross compile, I can reference the Armel toolchain and type make. I've made zImages but they're bone stock from git. I don't know how to customize modules though. Is it easier than I think? Like "make --configure makepowerlockwork=1..." or is there something special? I know I need dependencies for things I want in the kernel to be in sub folders but I dunno much more.

I had dabbled in chrooting an ARM environment with a customized QEMU build and got stuck at like step 80 of over 9000. Dignity aside, any info would help me out. Thanks
[Touch CDMA Android Development] vilord:
the best option is to backport wakelocks to our 2.6.25 kernel... you'll have to look at android.git.kernel.org at the msm kernel project, and find all references to user wakelocks, and then everything they did, do it in the 2.6.25 kernel with the correct 2.6.25 files.

LOTS of changes to the PM code...
[Touch CDMA Android Development] mbg19:
This post is for DZO for bringing us to this wonderful world of running android on our vogue he deserves credit for all of this :)
[Touch CDMA Android Development] dzo:
Bluetooth

I've made a start at bluetooth.

It seems to mostly work and you can pair with other devices but I haven't really tested anything.

I'm pretty sure that audio won't work because that will need some changes to the audio routing code and I don't have a bt headset to test it with.

This is only for Ion on Vogue at the moment but it won't be hard to get it working on other builds and devices.

I haven't implemented any power management or wakeup so it's not really that useful but if you want to try it get the latest rootfs and kernel on the google code site.
[Touch CDMA Android Development] punk.kaos:
Thats awesome Dzo! Thats the biggest feature missing for me. And the only reason I've had to reboot into winmo.

EDIT: After pairing it with my headset, it indicates that call audio is routed to the BT headset, and the dialer says audio is going to the headset, but the audio actually comes out of the phone speaker like usual.
[Touch CDMA Android Development] imfloflo:
@dzo Niceeeeee, hope it will be port to polaris soon and not to much hard to be port
[Touch CDMA Android Development] mssmison:
Not yet working on the rogers build but I'll try and have my builds updated tonight to work.
[Touch CDMA Android Development] TheKartus:
Bluetooth is working (or working as far as it should) on your cupcake build. The power switch widget can turn it on, and the icon shows on the notification bar. I have not tried to pair yet, but I will do some testing. It seems as though it should be fine.
[Touch CDMA Android Development] craig0r:
I can confirm the functionality you've listed. Also, discovery seems to work. A PowerMac found my phone just fine. My friend's Sony W810i phone did NOT find it, however... although his phone's always been sorta sketchy about bluetooth, so I don't put much weight in that.

As far as audio goes, I have a BT FM transmitter (A2DP) that I can test out, although since the Mac found "no configurable services" on my phone, I'm sure I won't get far.

EDIT: Oh, and I can confirm that it pairs just fine. I paired with the W810i (because I could discover it, although it could not discover me) and the Mac. The status upon pairing is "Paired but not connected."
[Touch CDMA Android Development] craig0r:
Try it... the BT chipset is the same, I believe.
[Touch CDMA Android Development] mssmison:
Thanks for checking it for me. I figured it would work on the cupcake base as it and ion are really close.
[Touch CDMA Android Development] bchi49:
I had success on pairing with Moto Rockr. It plays audio tunewiki, but pauses 2-3 times a second.

When connect fails I restart bluetooth and it works.

Pause seem to be the issue now.

Great start!
[Touch CDMA Android Development] craig0r:
That's likely because the bluetooth driver isn't able to reach anything near the full bandwidth it's supposed to. This will definitely get fixed. There's a fair bit of work left to do, from what I gather, but the main obstacle has been overcome :D
[Touch CDMA Android Development] katmandu421:
I failed to connect to my Clarion car stereo that does voice and A2DP BT.

Also, did we lose the "back" function on the cam button?

EDIT: Hmm, for some reason it stopped working, then the next time I picked up the phone, it was working again.
[Touch CDMA Android Development] craig0r:
I definitely haven't had the EASIEST time connecting bluetooth to my A2DP unit. (Motorola MOTOROKR T505.) Sometimes it will connect fine, sometimes it will only connect as a phone device, but not a media device, sometimes it won't connect at all. Again, I suspect once it is running full speed, these issues may go away. The best way I've found to connect my MOTOROKR is to turn it off, turn android's bluetooth off, then turn android's bluetooth back on, turn the MOTOROKR back on, then run a scan on the phone and pair with it.

Now, the MOTOROKR's PIN is 0000, and my phone doesn't ask for it, so I'm guessing that android stores 0000 as a default. Also, I think the only reason my MOTOROKR connects to android is that I have paired it in WinMo before... the MOTOROKR recognizes the same MAC address (hardware address) of the bluetooth chip in my phone and knows that this is the device it's supposed to connect to.

If none of this advice helps, maybe check out a logcat throughout this process and see if you can determine what the issue is. I have noticed now that bluetooth has a LOT of logcat output, which I haven't deciphered all of myself, but I can make sense of a good deal of it.

EDIT: I've just noticed the same behaviour with the Back (camera) button. I plug in a usb cable, and it fixes itself... but it's happened twice now in the past half hour or so.

EDIT AGAIN: Make that 3 times... It seems that the Back button becomes non functional when the phone goes to sleep. Rebooting now to see if that fixes it.

EDIT A THIRD TIME: No, that didn't seem to get rid of the problem, however turning Bluetooth off seems to have fixed it for the time being.
[Touch CDMA Android Development] mssmison:
I'm uploading an updated rootfs with the changes required to make the rogers build and hopefully the hero build have working bluetooth as well. Mileage may vary :)

I've confirmed it working on Rogers but not on Hero currently. I'll look into it more later for my new hero build
[Touch CDMA Android Development] tatnai:
File is huge for rootfs, like 10mb. I assume you should only update if you have rogers or hero . . . could you label it on google code that it is to be used with rogers/hero if that is the case?
[Touch CDMA Android Development] jamuka:
In case it might help to know

Couldn't connect with my Macbook pro after pairing.

By the way--thanks. VERY exciting to see progress being made on Bluetooth. You guys are amazing.
[Touch CDMA Android Development] craig0r:
@tatnai: This is the same size rootfs.img always is. You're probably noticing a difference because the Download site usually has it zipped, so it APPEARS considerably smaller when you're downloading, but once you unzip that, it's 10mb, so the size of the img hasn't changed. :)

@jamuka: So far, hands-free and A2DP audio seem to be the only bluetooth profiles that work. This is expected.
[Touch CDMA Android Development] enatefox:
Thought I'd share a script I made to do shallow or recursive comparisons of files. I need some help with trimming the output of MD5 to make it a liitle more accurate. I needed to install md5deep to do easy recursive scans:

example for recursive scan with MD5 sigs:

diff_dir 1 md5 /old/rootfs_mount/ /new/rootfs_mount/

#!/bin/bash
if [ "$2" = "md5" ]; then
if [ "$1" = "1" ]; then
diff <(md5deep -r "$3") <(md5deep -r "$4")
fi
if [ "$1" = "0" ]; then
diff -e <(md5sum `ls "$3"/*` ) <(md5sum `ls "$4"/*`)
fi
fi
if [ "$2" = "ls" ]; then
if [ "$1" = "1" ]; then
diff -e <(ls -alR "$3") <(ls -alR "$4")
fi
if [ "$1" = "0" ]; then
diff -e <(ls -al "$3") <(ls -al "$4")
fi
fi

Using ls works well, I could use some help getting the MD5 output a little better-- it's showing the paths which of course will be different so it's not really comparing the sigs.

And for good measure, I'll just include a web scraper I made for the Vogue-Android site to check for new builds. I have it in a plasmoid on my desktop and the script this is a part of injects HTML into the widget to alert me. Fan-----tastic.

NEWESTBUILD=`wget -q -O- http://code.google.com/p/vogue-android/downloads/list | sed -e 's/>/>\
/g' | grep '<a' | grep android | grep cancelBubble | grep detail | nawk '{print substr($3,19,26)}' -|line`
echo $NEWESTBUILD
echo "Click Here To Download It: http://code.google.com/p/vogue-android/downloads/detail?name=$NEWESTBUILD"

Doesn't check for anything but bundles but it's not too hard to change that. Also, it's a little outdated since the formatting has changed.

If anyone can improve them a little, please share.
[Touch CDMA Android Development] keith204:
hey guys, what's the latest and most stable release there's been lately? I believe it was the 7/09 that worked well for me, and I have an early-august release that reboots too often and loses signal & I have to reset the modem. Is there a recent release that is considered stable?