yashsingh1/xdaforums huggingface dataset:
[Touch CDMA Android Development] drkow19:
Agreed. DZO see if you can replicate that. I would think that you do most of your testing while plugged in anyway, in debugging mode, right? (I don't know)
[Touch CDMA Android Development] dzo:
I've made a few more changes to the adsp and interrupt code that might help. Can you try the NBH I just posted on my site.
[Touch CDMA Android Development] Shidell:
I've never had a firm grasp of how the kernel versions work with Android. Where does the kernel come from? Certainly it's not the full-blown kernel that linux desktop distros use, is it?

I'm assuming it's modified for a smaller platform, which would imply that we're getting that "custom" kernel from somewhere? And, from what I understand, the kernel we're using isn't the latest as compared to other Android phones. Anyone up for a sharing a bit of insight on the kernel?
[Touch CDMA Android Development] dzo:
It's the full linux kernel compiled for arm with just the drivers we need.

We use version 2.6.25 because that's the first that was released with the msm architecture and I haven't had time to port the changes to anything newer yet. What happened is that when google released their kernel for msm7x00a I took it and got it working with the older non-a chip. There are quite a lot of differences so its not easy to port to later versions but if anything important changes changes I just backport it to 2.6.25 (e.g. eclair hw3d). One day I'll get around to porting everything to 2.6.32 but it really wouldn't give you anything new.
[Touch CDMA Android Development] berardi:
I posted in Myn's Donut thread but it doesn't seem like anyone else had a similiar problem...

Having a strange issue - When I open Settings > Sound & Display > Ringer Volume, I get a "Sorry! The application Settings (process com.android.settings) has stopped unexpectedly. Please try again. Force Close."

I've tried formating, clean install, reinstall, etc. I can't seem to pin point the issue. This has happened in the past, but it resolved itself somehow. I flashed the latest 4-27 rom. I should note that using the side ringer volume buttons there is no problem adjusting, but I usually use this setting page to set my notification volume independently from the ringer volume.

Appreciate any ideas...Thanks!
[Touch CDMA Android Development] Shidell:
Much appreciated for the explanation, dzo.
[Touch CDMA Android Development] mssmison:
can you select ringtones?
[Touch CDMA Android Development] berardi:
Yes I'm able to successfully change the ringtone it's only "Ringer Volume" for whatever reason... obscure isn't it? lol.
[Touch CDMA Android Development] 4ultratech:
Bluetooth Question

Have a question about Bluetooth support.

I have a cordless phone in my house that connects to my phone by Bluetooth so I can

answer my home phone and cell phone on my cordless phone.

Under WinMobile it works without any problems.

I have switched to Myn's RLS5 and love everything about it but having problem with the

Bluetooth.

The problem is with disconnect and re-connect.

When I leave my house under WinMobile the phone drops the Bluetooth and then will

connect to my kit in my car. Under Android It never drops the cordless in the house and

then won't connect with the kit in the car unless I do it manual.

Also under WinMobile when I get home it will re-connect to the cordless and does not

under Android.

Any help or ideas on something I may be doing wrong would be great.

This may not be something that most people use, so if its not a priority just let me know.

Thanks....
[Touch CDMA Android Development] nathanlewan:
After updating to the latest nbh, i haven't had the camera crash anymore. Up until this point, it has always crashed on me. I have previously tried the 8th, 26th, and 27th nbh's, and it has never worked for me.

thanks for everything! My vogue is so much more fun because of all your hard work!

using myn's RL5, NAND, Default Theme, 240x320, clean install to RL5
[Touch CDMA Android Development] xport:
Woohoo!

Same here dzo! It worked here and there before, but I just flashed (voguimg-240x320-29-04-10.nbh) and its been stable through a number of tests (Using Myn's RLS5 on NAND, default theme). Thank you, Thank you, Thank you! :D
[Touch CDMA Android Development] kallt_kaffe:
FYI. I had to revert this commit in order to restore audio on my Kaiser: http://git.linuxtogo.org/?p=groups/...it;h=e31a36fc22b4d122261eb6d99596584854234459

Before reverting I could not play ringtones and had to force close settings when trying to select one. (using polymod 2.1d@320x428)
[Touch CDMA Android Development] berardi:
selecting ringtone? did you have any trouble clicking on ringer volume in setting? Where you can change volume for notifications? This is what happened to me
[Touch CDMA Android Development] kallt_kaffe:
I think changing volume worked but it didn't play any sound. How the problem appear may be different depending on what Anroid release you use. I use polymod 2.1d. It was most appearant when selecting ringtone. No sound and had to force close settings to exit.
[Touch CDMA Android Development] kallt_kaffe:
Tried the above with Myn's RLS5 and I get exactly the same freeze when quitting the Camera app: "Unable to handle kernel paging request at virtual address c6800000"
[Touch CDMA Android Development] JM-PDA:
Vogue Freezes up... Trying to use LogCat

Hello,

I am using Incubus26Jc's Super Eclair Lite 2.1 [RLS5] - [5/8/10].

It is working really well.

However, about once a day, I my phone freezes up.

Details:

During an incoming or outgoing call, I can click answer button.

I can take the call just fine, however my cell phone screen freezes.

It does not time out and go dark. Also, none of the physical keys work to turn it off or bring up the menu. Screen is essentially frozen.

After the phone call ends, it just sits on the same screen as though I was still on the call. I can hear through the ear piece that the call is now disconnected.

I tried to get a LogCat to provide Incubus.

However, the only way to do anyting on the phone is to reboot it.

After restarting the phone, I view the LogCat.

It appears that after rebooting, I loose the prior LogCat and it starts a new one.

Any ideas on how I can get the LogCat before it gets destroyed during a reboot?

Thanks for your help!
[Touch CDMA Android Development] dzo:
After the reboot, do cat /proc/last_kmsg to see the kernel messages.
[Touch CDMA Android Development] JM-PDA:
Dzo,

Will do that the next time this happens.

Thank you very much!!
[Touch CDMA Android Development] manu33xtro:
Same problem

Hi DZO,

I've a Polaris with Incubus build and your last kernel (07-05-2010). I've sometimes the same comportemnt... And after when I want to make call, I have to wait a few minutes to begin the conversation...

Cheers.
[Touch CDMA Android Development] JM-PDA:
Try to run the commend below that Dzo mentioned.

I've already started trying to recreate the problem. No luck yet.

Hopefully between the two of us we can provide Dzo the info he needs to get this resolved.
[Touch CDMA Android Development] JM-PDA:
Hello, Can someone provide me with some direction here?

I am not Linux savy and am trying to provide a kernel dump to Dzo.

I do not see what I am doing wrong. I actually did successfully run this command last night at a test. however, my phone froze and an attempting to get a kernel dump.

See below for my command and the message I got.

I attempted the commend twice.

Quick Note:

My phone froze up at 9:50AM with the screen turned on. Since I was then in a meeting for 2 hours and was not able to execute the last_kmsg command until about Noon. Not sure if that delay made any difference.

Thanks for your help!
[Touch CDMA Android Development] manu33xtro:
Try "su" and enter before the first command ;)

I will try to help us if I can...

Cheers.
[Touch CDMA Android Development] JM-PDA:
Dzo, per your request...

Background:

As mentioned in a previous post, from time to time my Vogue screen will freeze up and all hardware buttons are disabled.

See details below

Scenario resulting in a Frozen screen and all hardware buttons disabled:

Vogue connected to my laptop via USB cable for charging purposes.

I receive a phone call.

While still connected via USB, I press the GREEN answer button to answer the phone.

When I see that does now answer the call, I disconnect my cell phone.

I then press the GREEN answer button again, that now I an connected and the phone call works perfectly.

Except, now I see that the Vogue screen is still on the "Home" locked screen instead of the "in call" screen with the contact picture in the middle.

I then begin to press various hardware buttons on the Vogue with no results.

I continue to be successfully connected to my caller.

After a couple of minutes (phone screen is still frozen) they hang up on me to end the call successfully.

Lock up occurred at 12:45PM (PST). Not sure if the logs shows this time stamp anywhere.

As expected, my screen is still frozen.

I then rebooted the phone by using the stylus hole.

The phone rebooted and the first thing I did was the "last_msg" command.

I am not sure if this kernel dump will provide you with the info you need.

I would be more than happy to re-create the problem and provide you with another kernel dump if needed.

Let me know if you need anything else.

Thank you!!!
[Touch CDMA Android Development] manu33xtro:
Hi JM-PDA and DZO,

Same problem this morning : my wife call me (take a very long time before to see his phone number !) I take perfectly the communication and when I press the red button the phone (during one minutes) stay with the "in call" screen... And after, no network during two or three minutes ...

I've two files because the same problem just after the first in call...

May be the second files is not ok because I reboot my phone...

I hope It's can help you.

Cheers
[Touch CDMA Android Development] Dukenukemx:
How difficult would it be to implement support for ext3? Just to have journaling so in the event something bad happens (like ran out of battery power), at least nothing corrupts.

Also, is the reason why bluetooth and camera doesn't work in 2.1 builds because of the kernel?
[Touch CDMA Android Development] dzo:
Thanks, I don't think your problem is caused by the kernel, the kernel is still alive at the end of the dump. I'm guessing that you're using eclair running from the sd`card. Eclair still isn't very stable, try a donut build and see if it solves your problems.
[Touch CDMA Android Development] kallt_kaffe:
Update:

This kernel have a working Kaiser Camera in the Tattoo build (and likely the same goes for Myn's warm donut): http://it029000.massey.ac.nz/vogue/files/zImage-08-03-10

In this kernel it freezes on exiting the camera app: http://it029000.massey.ac.nz/vogue/files/zImage-11-03-10

Unfortunately there is a LOT of changes between those two kernels so it's hard for me to try to figure out what change broke the camera exit.
[Touch CDMA Android Development] JM-PDA:
Dzo,

Thank you for your response and advice.

You are correct. I am running from Eclair from Andboot folder on SD card with 2 EXT2 partitions. I have used Donut for months and have never experienced this issue.

I would really like to give Eclair a good try before I go back to Donut.

Question-1:

So, Eclair not as stable running from SD Card.

Is it more stable if I run it from NAND?

Question-2:

If Question-1 is a "yes", then I will bite the bullet and flash NBH to NAND.

Would Eclair tend to be equally stable if data is on NAND vs. EXT2 partition on SD card?

I really appreciate your input.

All the best to you!
[Touch CDMA Android Development] vilord:
We used to support ext3... but ext3 thrashes the SD so much that you'd need to toss your SD in the trash after a month or two... you wouldn't lose any data on a battery failure, but you would lose it all when the SD died.

BT and camera don't work in 2.1 builds because we need to look at both kernel and userspace driver support... we should be able to use the same kernel code, with modified userspace drivers, but nobody's got time to investigate.
[Touch CDMA Android Development] dzo:
I think I found the problem, /dev/pmem was using an allocator which it shouldn't be doing. I don't have a kaiser here to test but I pushed the change and put new NBHs and a kernel on my site
[Touch CDMA Android Development] milanche:
I tried zImage-19-05-10 but camera still hangs on exit.
[Touch CDMA Android Development] Dukenukemx:
Is that due to ext3 or a poor implementation of it?
[Touch CDMA Android Development] nahteecirp:
From linux.com/archive/feature/114295
[Touch CDMA Android Development] mrkite38:
Yeah, I wondered if there would be a try at LogFS since it's good to go with 2.6.25.
[Touch CDMA Android Development] dzo:
Strange, I just tried it on a kaiser and the camera doesn't crash at all for me. Are you using the standard donut camera app. Does it always crash? Are you running from nand or sd?
[Touch CDMA Android Development] kallt_kaffe:
Actually it's an app called Camera Pro and I'm currently HaRET booting and running from SD. I'll try installing Myn's warm Donut as it has the standard camera app. I've treid it in Myn's but that was before you made the change to the code.
[Touch CDMA Android Development] kallt_kaffe:
KAIS130

panel 1

Radio 1.71.09.01

Booting through HaRET from WinMo 6.1 (Solace 3.1)

Myn's warm donut RLS5 (new install on SD fat)

Same freeze, same virtual adress as always
[Touch CDMA Android Development] loserskater:
Using the latest nbh from DZO(5-19-10) and vilords tattoo, I'm able to use the camera fine. Opens up, takes a picture and returns to the home screen without any problems.
[Touch CDMA Android Development] kallt_kaffe:
Reflashed with the panel 1, no tilt, NBH but using same SD-card (system/data.img) installation and now it works. No freeze

EDIT: Flashed WinMo back, still the same Android install on the SD-card. Freeze!

EDIT2: Double checked that I really have your latest zImage, checked with hexeditor that the kernel parameters are the same in startup.txt and the NBH. Still freezing on camera exit when HaRET booting.

EDIT3: Something else has changed to with the latest changes... The installation menu runs painfully slow, or at least it reacts on keypress really, really slow. Makes it a pain to move from the top to the botton the be able to choose 10.Quit. Anyone else noticed that?

EDIT4: If I compile my own NBH with the new code it also does not work but your NBH does. I've done a "make clean" now and is recompiling from scratch to see if it matters.

EDIT5: Make clean made no difference. In fact, I made an NBH with your zImage and it still does not work. Still uname -a confirms that it is the same kernel as in your NBH. With a hexeditor I can see that you have a diffrent initrd.gz. The sizes do not match.

EDIT6: Now, I'll be damned... I get bootenv from git://androidhtc.git.sourceforge.net/gitroot/androidhtc/bootenv and it includes a initrd.gz but the instructions I initially followed told me to create an initrd-mini.gz and I did and have used it since. Now I switched to the initrd.gz that I got from pulling git://androidhtc.git.sourceforge.net/gitroot/androidhtc/bootenv and your zImage and well... Camera works. Next step will be to the one I compiled myself but I expect it will work also. The initrd.gz still doesn't match the size of the one in your NBH but at least it works.
[Touch CDMA Android Development] kallt_kaffe:
btw, I suppose that replacing initrd.gz in /andboot may fix the camera when HaRET booting too.
[Touch CDMA Android Development] loserskater:
I can confirm that the boot menu is extremely slow with the latest kernel. And thats using both the hardware dpad and the screen (as a giant dpad). Not sure if camera was working for me with the kernel before the change was made... will test that.
[Touch CDMA Android Development] dnessl:
filesystems for flash (ext3, logfs)

We're mixing two different things here. There are two types of flash memory:

(1) raw

(2) where there is a built-in wear-leveler interposed between the OS and the raw flash

The number one thing that flash needs is wear-leveling. Flash has a definite limit on the number of times a given block can be written (actually erased) before it wears out (fails). Standard Unix filesystems (ones meant for rotating media) tend to rewrite certain meta-data blocks a lot, so without wear leveling your flash would quickly fail.

An SD card has that wear-leveler built-in, so the Linux kernel has no control (or idea) where blocks are physically being written in the raw flash -- the intelligent wear-leveler built into the SD card handles that. On the other hand, the Linux kernel doesn't have to worry about doing wear-leveling on an SD card, so you can use a standard Linux filesystem like EXT2.

Using EXT3 on an SD card is problematic because its journaling creates lots of small writes to the transaction log, which turn into partial writes to the 128K-size flash blocks, and every write causes an erase to first reclaim a block. Pretty quickly, I/O to the SD card starts to get real slow, followed by premature failure of the SD card due to excessive erase-writes.

What might be interesting is to use EXT4 with journaling turned off, and set EXT4 to align to the SD card's erase blocks.

In contrast, the LogFS filesystem is meant for raw flash, so LogFS is doing the wear-leveling itself. I don't know if NAND in the Vogue is raw or has a built-in wear-leveler. If it is raw, then LogFS could be a boon for NAND installs.
[Touch CDMA Android Development] mnjm9b:
@kallt_kaffe

did you update tinboot as well.

new updates include adding hw3d.

although I think I am missing something because the diff shows:

.if hw3d==1

.ascii "hw3d.version=1 "

+.else

+ .ascii "hw3d.version=0 "

.endif

but I fail to see where it pulls the variable "hw3d==1" from to choose between the two.

also, it now will create a full spectrum of nbh's with diff res, tilt/nontilt and panel types

all at once.

which is why I question the hw3d, because they all default to hw3d=0

I guess I could just comment out the if part and have it set to hw3d=1

or change it to loop the hw3d setting like the rest of the variables and make a full set for donut and a full set for eclair.
[Touch CDMA Android Development] mrkite38:
Yeah, I meant for nand. :)
[Touch CDMA Android Development] mrkite38:
The script that compiles tinboot.S file sets that value based on a loop.

for eclair in 0 1; do
...
arm-none-linux-gnueabi-as tinboot.S -o tinboot.o --defsym res=$resolution --defsym MTYPE=1667 --defsym vogue=1 --defsym hw3d=$eclair

This particular change was so that people could hex edit the value to switch between eclair and donut without reflashing. Previously, the variable was absent from donut nbhs.
[Touch CDMA Android Development] mnjm9b:
Thank you,

I didn't even look at the compile script.

I was using the compilekaiser script and that was missing the hw3d setting.
[Touch CDMA Android Development] kallt_kaffe:
I actually have a compilekaiser that I made which compiles all panels, for all keypads (5 of them) for both donut and eclair but the amount of files created are just too much (90 different files). What is new in the new tinboot.S is that it adds the hw3d.version even if you compiles for donut so you can take a donut NBH from DZO's collection and hexedit it into an eclair NBH. That wasn't the case with the older version.

However, as you have read above the camera started to work once I used the initrd.gz that was included with bootenv instead of the one I created when I followed the instructions.

It would propably be a good idea that someone makes a new haretinstall.zip with an updated initrd.gz and the camera propably will start working for HaRET users too.

Compile all the 90 versions:

for eclair in 0 1; do
opt=""
if [ $eclair == "1" ]; then opt="-ECLAIR"; fi
for tilt in 0 1 2 3 4; do
for resolution in 428 480 320; do
for panel in 1 2 3; do
echo $panel,$resolution,$tilt
/home/<username>/android/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-as tinboot.S -o tinboot.o --defsym tilt=$tilt --defsym kaiser=1 --defsym MTYPE=1553 --defsym res=$resolution --defsym panel_type=$panel --defsym hw3d=$eclair
/home/<username>/android/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-objcopy tinboot.o -O binary tinboot
cp partition_table output.nb.payload
cat tinboot >> output.nb.payload
wine /usr/share/LinuxRomKitchen/NBMerge.exe -kaiser output.nb
yang -F KAISIMG-PANEL$panel-$resolution-TILT$tilt$opt.NBH -f output.nb -t 0x400 -s 64 -d "KAIS****" -c 11111111 -v 1.0.MARTIN -l WWE
done
done
done
done
[Touch CDMA Android Development] mnjm9b:
:eek: 90 versions :eek: lol

yeah, I just ran into that same problem with the initrd.gz

but I am on eclair so the camera fix is a null issue anyway.

just wondering what else is different.
[Touch CDMA Android Development] Dukenukemx:
Where can Tilt users get the latest kernel?
[Touch CDMA Android Development] kallt_kaffe:
http://it029000.massey.ac.nz/vogue/files/?C=M;O=D If you are running eclair, use a hexeditror and change hw3d.version to 1.
[Touch CDMA Android Development] Dukenukemx:
Doesn't seem to include your latest GPS fix. iGO crashes within 20-30 seconds of starting the application. This is with running GPS Test first before iGO.
[Touch CDMA Android Development] kallt_kaffe:
Try the latest one I posted here: http://xdaforums.com/showthread.php?t=660158

If it doesn't help, let me know in that thread and I'll put togheter some test versions for you. Also state what iGO version you are running so that I could try to reproduce the problem.
[Touch CDMA Android Development] kallt_kaffe:
Sorry, I think I messed up pretty bad. I just noticed that I had forgot to remove the latest DZO NBH and it likely took preference over the one I had just made and I wrongly assumed that changing initrd.gz fixed the problem. Camera still freezes.. :( (Unless you use DZO's NBH)
[Touch CDMA Android Development] Dukenukemx:
Woops, didn't see that. I mentioned it stills freezes in your thread.
[Touch CDMA Android Development] JM-PDA:
Dzo,

I had been holding off from going to NAND.

After your advice above, I decided to just go for it.

I've been running "Incubus26Jc's Super Eclair Lite 2.1 [RLS5] - [5/8/10]" on NAND for 2 days with no problems at all. While on SD, I would easily get 2 to 3 phone freezes a day when I answered/made a phone call.

Thanks again!
[Touch CDMA Android Development] dzo:
I just put some new NBHs for vogue on my site, these have a fix for a problem where the GPU platform memory wasn't released properly by an app sometimes. This meant that sometimes when you started a 3d application you just got a blank screen. It seems to have made the display much smoother for me.

There is also a change to the touchscreen driver that might make it more responsive. These changes were quite large so it's possible that they broke something else, let me know if you find any problems.

This should work on kaiser and polaris but I didn't make NBHs for theses devices.
[Touch CDMA Android Development] incubus26jc:
just flashed thanks. :) your the man
[Touch CDMA Android Development] inertone:
thanks alot man!

flashing as i type!
[Touch CDMA Android Development] kallt_kaffe:
Do you have any idea why making an NBH with the zImage from your site makes an NBH with a Camera that freezes on exit? Do you have something in your tinboot.S that is not present in this: http://androidhtc.git.sourceforge.n...f;hb=76d2e3db0999e3d1fc0ece006eea827d2d08cceb

Or do you have some tweak in initrd.gz?

Or another version of the compiler? I've tried compling with both arm-2008q3 and the one from here: git://android.git.kernel.org/platform/prebuilt.git

I'm out of ideas... except for, well, extract your initrd.gz from your NBH with hexeditor but just feels a tiny bit extreme. But my guess is that the initrd.gz is the answer. Propably some change in MAKEDEVS.
[Touch CDMA Android Development] kallt_kaffe:
btw, this line:

314 msleep(1000);

In: http://git.linuxtogo.org/?p=groups/...2ded3231636af9e9656f7a0d40f2eca28647542f#l314

is what causes the painful delays in the installation menu. Is there a reason why it was added for Kaiser and Poilaris? Vogue doesn't seem to have that delay.