yashsingh1/xdaforums huggingface dataset:
[Touch CDMA Android Development] dzo:
Thanks a lot for that, I've had a look at the logs and it's crashing in the pthreads futex code. This means that it's probably a locking problem which makes sense since it's quite random. Futexes are implemented in the kernel so perhaps our kernel doesn't support a feature that the bionic pthread lib is using. I'll investigate further and try to find a solution.
[Touch CDMA Android Development] Backwardsblade:
I have a question about resolutions... I'm trying to adjust the resolution to 320x480 for gps. I see several nbh's with that option but they all appear to be the 240. Is there any option to modify resolution on my end or could there possibly be a future update.

Thanks in advance.

S
[Touch CDMA Android Development] loserskater:
Use my NBH editor. (in my sig)

But once you boot android everything will look tiny, so you'll need Rogue Tools to adjust density to 160.

Or you can open up the tgz with 7zip and go to the system folder and open the buil.prop with a text editor and look for this line:

ro.sf.lcd_density=120

and change it to 160

then install like normal.
[Touch CDMA Android Development] n2rjt:
How to compile kernel?

Nice instructions in the first post on how to build Android.

Now, what if I wanted to build a kernel from the sources that DZO uses?

How might I do that?

I really just need tun.ko so I can get openvpn to work, but "teach a man to fish".

Am familiar with building Linux in general, but would appreciate a step-by-step that was as clear as the Android-building instructions.

I am guessing that the instructions are buried in that massively long kernel thread somewhere. But, alas, I have not found them, so I must ask.
[Touch CDMA Android Development] dzo:
If you've got the android source you'll also have the latest vogue kernel and a cross compiler, just do:

cd kernel

edit the Makefile and change the CROSS_COMPILE line to:

CROSS_COMPILE=../prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-

make vogue_defconfig

make

now the kernel will be in arch/arm/boot/
[Touch CDMA Android Development] mantorp:
Did you get Data to work on this yet? I use the 7/26 kernel and have everything on SD.

edit. I get data to work using kallt_kaffe's build from post 635
[Touch CDMA Android Development] n2rjt:
Thanks! Kernel builds successfully.

Now, maybe openvpn will work for me? We'll see...
[Touch CDMA Android Development] blindguyinanorgy:
turns out my data problems have nothing to do with android. I put my sim in the iphone i have to play around and it locked out my data. ATT sux why do i need different plans for different phones when both are unlimited.
[Touch CDMA Android Development] mantorp:
Wonder if ATT is punishing me for connecting in WinMo and Android several times per day? #ATTFAIL
[Touch CDMA Android Development] kallt_kaffe:
New build

I've put up a new build here: http://www.mediafire.com/?ar4rfgtbpc5aaet

I didn't put it in the usual place as it has not been "built" from scratch like very new release usually is.

It contains the following:

- The official 26-07-10 release (odexed)

- The wifi tethering update (odexed)

- New versions of the Google Apps (gmail, market etc..) that have mdpi graphics (odexed)

So, what's the deal with this? Well, our previous Google Apps were made for the Nexus which means they only included graphics (buttons etc.) scaled for 480x800. These Google Apps are also FRF91 and I found them in the official CyanogenMod 6 thread over at the G1 forums. The only difference asfaik is that they contain both hdpi and mdpi graphics instead of just hdpi graphics. You will actually notice the difference visually in the Market where it now shows the grey background correctly. But more importantly it should use less memory and possibly be a little bit faster, at least in theory.

I've pushed these changes to the official repo so the next build from dzo will include it so please report ASAP if anything got broken by the change.
[Touch CDMA Android Development] mantorp:
Everything works, except if I let it go to sleep it won't wake back up. No LEDs are on and it doesn't respond to anything except a stylus in the you know where.

Edit: Might have been a one off occurrence, been using it the rest of the day w no problems. Great work!! dzo and Kallt_Kaffe are legends!
[Touch CDMA Android Development] LoveMyPhone:
Do you have an iPhone data plan? If so, the access point settings that are online for ATT are no good for us iPhone data plan users. Check out my post here:

http://xdaforums.com/showthread.php?t=738794

Edit: And if you have the old iPhone Unlimited or PDA Unlimited data plan, at least 1 ATT rep told me that I could switch between the two freely. So if you're on the PDA Unlimited plan you might be able switch to the iPhone plan then set up all your phones to use the settings above.

Good luck!
[Touch CDMA Android Development] scooter1556:
Seems to work fine, had to clear data which i haven't had to for other Froyo build updates because if i didn't google accounts would not work.The only options i in the accounts section of setup were corporate or facebook. Fresh install with data wipe worked fine though but not sure what caused this.
[Touch CDMA Android Development] mnjm9b:
I just built from repo.

haven't tried everything yet but so far here is what I am having issues with.

Betterterminal FC

Neocore wont install

droidwall widget doesnt work (although droidwall app works fine)

other than that it seems ok... (haven't tried BT or Tether yet)

however, It may be my own fault because I customized a few things before installing.

so if nobody else has these problems I may try to reinstall.
[Touch CDMA Android Development] kallt_kaffe:
Works for me.

Same problem here "Unknown error -18", doing a logcat shows some complaints about asec. I'll reinstall a plain 26/7 release to see if it works to make sure if I broke it or if was allready broken.

EDIT: Plain original 26-07-10 build and Neocore install still fails and the error is "Unknown reason -18" and not "Unknown error -18" as I claimed above. This means the new Google Apps and the wifi tethering/superuser update is not to blaim.

I know I've seen the Betterterminal FC before and I think it was either getprop or setprop that was missing. Make sure you have the toolbox symlinks in place.
[Touch CDMA Android Development] milanche:
Not sure if it's been discussed already, but here's a part of build.prop I discovered in one of the CyanogenMod6 mods for G1:

#ro.build.description=cyanogen_dream_sapphire-eng 2.2 MASTER eng.shade.20100710.235517 test-keys
#ro.build.fingerprint=google/passion/passion/mahimahi:2.2/FRF91/43546:user/release-keys
# The following 2 lines trick Market into thinking this is not Froyo and so copy protected apps will be available:
ro.build.description=passion-user 2.1-update1 ERE27 24178 release-keys
ro.build.fingerprint=google/passion/passion/mahimahi:2.1-update1/ERE27/24178:user/release-keys
[Touch CDMA Android Development] mensa07:
I just want to add that neocore can only install via adb and if copied to sdcard and install via file manager (oi / linda / astro). it was tested on fresh froyo and CM 6 nightly build.
[Touch CDMA Android Development] kallt_kaffe:
That has been taken care of allready, I've made a script for that, just do this in a terminal if you need to access an non-froyo app.

$ su

# market.sh eclair

<reboot phone>

To go back:

$ su

# market.sh froyo

<reboot phone>

And the same script can also be used for temporary access to paid apps:

<make sure market is not running>

$ su

# market.sh paid

<start market>
[Touch CDMA Android Development] wanderso:
Martin already has a Kaiser - maybe it will become his "daily driver"?
[Touch CDMA Android Development] kallt_kaffe:
I most certainly hope so...
[Touch CDMA Android Development] kallt_kaffe:
dzo, do you have any idea why cell tower location works on Kaiser with this libhtcgeneric-ril.so on a CM6 port but not in Fresh Froyo? Could we be lacking some lib needed for this?
[Touch CDMA Android Development] nabicat:
Same observations re clearing data to make Google accounts work again. Thank KK for the update.
[Touch CDMA Android Development] vinny13:
How do I change the launcher home screens from 5 to 3? I can't find that setting, if there is one?

And is the signal strength reporting accurate? Mine only ever shows 4, 2, 0, or X, when usually its no more then 3.
[Touch CDMA Android Development] kallt_kaffe:
While trying to find out why this is giving troubles I compared our manifest with the official froyo one and I think I spotted something that may need our attention (although it likely doesn't have anything to do with cell tower location).

The SDK has recently moved from r6 to r7 and the official manifest is "locked" to r6 while we are not (using the master branch I guess?)

We may want to change these:

<project path="external/qemu" name="platform/external/qemu"/>

<project path="sdk" name="platform/sdk"/>

to:

<project path="external/qemu" name="platform/external/qemu" revision="tools_r6"/>

<project path="sdk" name="platform/sdk" revision="tools_r6"/>

Not sure the qemu has any real effect but I guess the sdk may be important?

The official build also defaults to:

<default revision="froyo" remote="korg"/>

while we use:

<default revision="froyo-release" remote="korg"/>

but I suppose these two branches are identical?

EDIT: Or wait... I think you can ignore this... default revision froyo-release seems to make sure we do in fact get tools_r6. False alarm...
[Touch CDMA Android Development] kallt_kaffe:
Just for information. I did change the same two lines for the eclair libhtcgeneric-ril.so and compiled it and now I have working cell tower location running VaniljEclair RLS9 but I can't figure out why it refuses to work in Fresh Froyo.
[Touch CDMA Android Development] NFHimself:
To whom it may concern, the file system-froyo-unodex-26-07-10_16.tgz is showing as corrupt, so is the file posted on mediafire based on the same file. I downloaded the 7-15 file and that one was fine. Used winrar and 7zip.
[Touch CDMA Android Development] -Arturo-:
Hopefully you will get it to work on Froyo soon, Kalt. Any feedback from DZO on the issue?
[Touch CDMA Android Development] -Arturo-:
Kalt I've just installed this build and the contact photo, fonts and buttons are huge in email view of gmail app again.

I reverted back to the version modified by DZO for the time being.
[Touch CDMA Android Development] n2rjt:
As a sanity test, have you tried building the libhtcgeneric-ril.so for Fresh Froyo yourself? Perhaps the one I built isn't quite right, somehow?

My build environment seems a bit flaky, in that whenever I run the commands in the first post I get errors. I can build shared libraries, but haven't yet successfully built the entire thing.

The commands I use are:

repo sync

. build/envsetup.sh

lunch us_vogue-userdebug

make && tar czvf androidinstall.tgz system
​

The error is (with a different .so every time):

target SharedLib: libandroid_runtime (out/target/product/vogue/obj/SHARED_LIBRARIES/libandroid_runtime_intermediates/LINKED/libandroid_runtime.so)

out/target/product/vogue/obj/lib/libnativehelper.so: file not recognized: File format not recognized

collect2: ld returned 1 exit status

make: *** [out/target/product/vogue/obj/SHARED_LIBRARIES/libandroid_runtime_intermediates/LINKED/libandroid_runtime.so] Error 1
​
[Touch CDMA Android Development] n2rjt:
In CM when I select "Use Wireless Networks", I get a pop-up prompt:

Location consent

------------------

Allow Google's location service to collect anonymous location data. Collection will occur even when no applications are running. <Agree> <Disagree>​

I don't get that in Fresh Froyo.
[Touch CDMA Android Development] kallt_kaffe:
No, I deleted my froyo sources to make room for eclair. I may try that later but I doubt it will help as it works in the CM6 port.
[Touch CDMA Android Development] kallt_kaffe:
Maybe it's one of the missing Google Apps after all. I did add the missing ones but I don't remember if I added it after install or if I did a fresh install with them in place. That may make a difference. I'll try that when/if time allows.
[Touch CDMA Android Development] kallt_kaffe:
Nope, that didn't do the trick... :(
[Touch CDMA Android Development] kallt_kaffe:
Here we go... I also added the SIM pincode patch.

Still no network location. :(
[Touch CDMA Android Development] kallt_kaffe:
Maybe...

In BoardConfig.mk for Dream and Sapphire one line looks like this:

BOARD_GPS_LIBRARIES := libgps librpc

The same line in our BoardConfig.mk looks like this:

BOARD_GPS_LIBRARIES := libgps

The CM6 we usually port are built for Dream/Sapphire... Not sure but maybe this is a clue to why network location doesn't work in Fresh Froyo?

EDIT: Or maybe not... Other devices don't do the rpc's in the kernel like we do when talking to the GPS so that's propably why we don't have (or use) that one.
[Touch CDMA Android Development] spiritssight:
Hello Devs,

I wanted to say thanks for a wonderful build!

Here is what I have noticed with the build:

When the phone falls asleep it will have hard time waking up and it wakes up slow other times, also once and while it will wake up from a hard to sleep, by opening the keyboard, then close and open again waiting 30 sec.

If I put the phone into airplain mode it will not go into deep sleep, even if it is left all day/night. Also the LEDs don't always work correctly.

I have also had issue where my google account disappears and other strange behavors happen

I also don't get a GPS fix for long periods and the location functions does not seem to work.

I am using the latest build that is on sourceforge.

I was wondering with all the latest changes will there be a fully packed update on sourcefroge soon?

God Bless,

Christopher
[Touch CDMA Android Development] plemen:
I'm trying to build this on an Ubuntu VM and keep running into this error:

acp: file 'out/host/linux-x86/obj/EXECUTABLES/vm-tests_intermediates/tests/data' does not exist

make: *** [out/host/linux-x86/bin/../cts_dalviktests/timestamp] Error 1

Does anybody have any idea's on how to get past this?

Thanks.
[Touch CDMA Android Development] kallt_kaffe:
Here's another libhtcgeneric-ril.so.

Apart from all the other recent changes it enabled the "Use only 2G networks" button on GSM phones.
[Touch CDMA Android Development] -Arturo-:
Great work Kalt, the new fix works very well.

Kalt are you still working on cell tower location for dzo,s froyo or have you abandoned the project?
[Touch CDMA Android Development] kallt_kaffe:
I've postponed it... I'm on Eclair again and it works very well. Not a single freeze in days. I'm working on VaniljEclair RLS10 with and then I have a new idea about the strange GPS problems I get in eclair but not in froyo that I'd like to investigate.
[Touch CDMA Android Development] pentagramII:
Kalt, Is that possible to set "messaging" under mail button?
[Touch CDMA Android Development] karlandreasa:
went back to enclair too, but still having this strange crashes (sometimes when i pick up my phone, i cant wake it up, no sign of life, have to reset. using build 9.

thanks
[Touch CDMA Android Development] -Arturo-:
Dzo is there any chance for cell tower location working on fresh froyo for gsm users?
[Touch CDMA Android Development] dzo:
Yes, k_k has pushed his changes so it just needs recompiling. I'm a bit busy at the moment but I'll eventually get around to it. Unless somebody else wants to do it that is, just follow the instructions in the first post.
[Touch CDMA Android Development] -Arturo-:
Oh ok thanks for your reply Dzo, but I should have asked a bit different question.:)

I'm aware that Kalt has pushed the changes but for some reason cell location doesn't work on fresh Froyo even though it works perfectly on KK's vanillaeclair and CyanogenMod 6 Froyo by Milanche. So my question should be .......do you know why it doesn't work on fresh froyo?
[Touch CDMA Android Development] kallt_kaffe:
Here's yet another libhtcgeneric-ril.so.

This time the "Use only 2G networks" works really well.
[Touch CDMA Android Development] mrkite38:
understatement. but i like the looks of it. :D
[Touch CDMA Android Development] SuperJMN:
kallt_kaffe, the 2G only toggle is working really good!

Wow, that is what I call speed!

I have marked it as a solved issue. Thanks a lot!!
[Touch CDMA Android Development] flinx42:
Last night I switched back from FreshFroyo to VaniljEclair V10 on my Kaiser for the same reason i.e. too many times it just hanging on me. Had been running it for a week. Most of the time as described above it happened during standby.

This morning I took the phone of the charger. It still worked after lunch, but just now I've found it unable to wake up again - just like with Froyo before. :(

So my guess it's the kernel which is at fault or both Android versions have the same problem and sent the wrong or too many processes asleep during standby. As far as I can remember there were a couple times with Froyo where the phone hung during the running of an application, while it was drawing something, so could also be display driver related (just saying as panel type and sleep/wakeup are related)

FYI I've found that panel type 3 seems to give me less hangers than panel type 2

When the phone gets into this state of not being able to be woken up again, I've found:

- The LEDs are still working.

- Sliding out the keyboard enables the keyboard light for about 4sec

So the phone isn't totally dead.

Also, if you just press the reset button the following boot is very slow and stops for a while at message:

"No IRQF_TRIGGER set_type function for IRQ 190 (kaisergpio)"

It then takes a VERY long time on the X animation and just now after something like 5min reported with a graphical error message:

"Sorry! Process system is not responding. [Force close][Wait]"

Touchscreen is not active at this point, so used Dpad to select WAIT.

-> Blank screen and eventually the lock screen comes up (almost 10min :O), but even then the phone is still very slow and essentially not working!

What seems to help it boot normally (fast) is to pull the battery for a few seconds instead of pressing reset.

Finally, at one point last week while still running Froyo, one of these hangers or the resulting reset, caused quite severe corruption of the installation. Almost all apps/widgets lost their settings and most needed re-installing. After a day or so I actually totally reinstalled the OS (not the kernel) including wiping data

Maybe these observations are of some help for fixing the issue.

Keep going, you're really close to having the Kaiser running Android perfectly!
[Touch CDMA Android Development] samjam:
I've observed all this too. The best you can do for now is to install your data on data.img on SD instead of on NAND. Then you don't get the missing icons. (Although I now get vanishing exchange sync accounts).

I don't know if it is reasonable to expect more than this... there comes a point when the value of the effort could be directed to a phone with hardware support from the manufacturer.

On another note; if you are feeling grateful be sure to donate some $ to dzo, kalt kaffe and others you think are deserving. It's the only sort of encouragement that we can even expect might prioritize such work :-) But if you do give some $, do it as a gift of gratitude and not expectation for more... for it is hard without manufacturer support...

Sam
[Touch CDMA Android Development] cb2002:
I definitely have similar issues for my Kaiser. Sometimes it would wake up and hang on the white/static screen. Some times it would not wake up at all, just black screen and I need to use the pen to push the reset button. Sometimes it occurs on incoming call and the phone tries to wake up.

Quite often the reset needed would corrupt the NAND and just lost contacts/settings or having app force close constantly after a long slow boot. To fix the phone when it is in that state requires reinstallation from scratch.

It really does affect the stability and usage of the phone. I have not had any build running for more than a week or two without reinstallation.

Thus it is number one issues for me to have a stable phone.

The issues occurs in all Android build I tried, some more often than others. If we can get this resolved that would be really awesome.

We definitely have come a long way for Android on Kaiser. Pretty much all the major features we need are there. Kudos to all developers and contributors for the great work.
[Touch CDMA Android Development] spiritssight:
Android & Hardware

Hello All & Devs,

Could you please make the best recommendation for hardware for running Android? My AT&T Tilt has gone to the grave yards for the rest!

I would like to get a phone that would work on AT&T network and has a keyboard. I will do a contract with them to get it (don't have much money)

or is there any rooted verions of Android for any of the AT&T verisons? and which one would be best hardware/keyboard?

God Bless,

Christopher
[Touch CDMA Android Development] Joe1981AL:
make is running, it has been for over 2 hrs in a ubuntu VM. decided I wanted to play with it, but first would compile as is... I am by no means a trained programmer but know how to read doc files and understand the logic of the code, but waiting for this make to finish makes me wish I was back at univ as a server admin...
[Touch CDMA Android Development] Joe1981AL:
Poo... So 2 1/2 hours in I get:

make: *** No rule to make target 'device/htc/vogue/updates/bin/bootanim.sh.sh', needed by 'out/target/product/vogue/system/bin/bootanim.sh'. Stop.

No Good... Have to go to bowling league now, will work on later tonight.
[Touch CDMA Android Development] n2rjt:
I saw the same. It seems like a typo in a makefile: device/htc/vogue/device_vogue.mk. When I fixed it locally, the build completes but has issues. I'm trying to figure out why, but steep learning curve.

The userinit.sh script gives an error:

[: 0: unknown operand

Usage: default_network.sh <num>

0 => Dual mode, WCDMA preferred

1 => GSM Only

2 => WCDMA only

#

Even though build.prop contains ro.telephony.default_network=0, the command `getprop ro.telephony.default_network` emits only a blank line. Maybe it needs to be a boot parameter?
[Touch CDMA Android Development] samjam:
I'm finding the reset also loses me data with data.img - it seems like the ext2 file system image on fat32 combination doesn't flush/fsync or sync properly.

If I ever have to do a reset then I lose my exchange email sync account - even if I have done a full reboot since creating the account. I guess it is because the account sync settings were corrupt through not entirely being written to disk.

I wonder if I can get yaffs to work on an image... without have raw flash to work on
[Touch CDMA Android Development] leona:
This depends on your budget, but (like me) if you need a hardware keyboard and want an android phone, then at the bottom of the budget is a HTC G1/Dream (£50-£90 2nd hand) or top end, Motorola Milestone (£200 - £250 2nd hand, or £320 - £399 new). Apparently next year (2011) HTC will be releasing a new Android phone with keyboard, 'World Phone' or something, looks good, hope they keep the red keyboard.
[Touch CDMA Android Development] pentagramII:
Hey Kalt, could You compile the newest build with latest changes? Thanks
[Touch CDMA Android Development] cb2002:
My first thought was it sounds like a flush/sync issue too. Seems like we don't write to the NAND until we shutdown or some arbitrary time, so in a reset we would lose new data or corrupt the file sytem.
[Touch CDMA Android Development] Joe1981AL:
Well trying again, I didn't feel like digging through mk files to find it so I just put a symlinked bootanim.sh.sh>bootanim.sh and it passed it, then my VM ran out of space... So today I setup a new VM on a desktop at office some I'm not killing my laptop and have it running now :)
[Touch CDMA Android Development] mssmison:
You'd really like the milestone, I really like mine