yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Nope, not to my knowledge.

Edit - just realized how this phrase looked... retarded. Wifi is still broken, although it seems we're getting closer to it being functional.
[Touch Pro2, Tilt 2 Android Development] muziling:
Does someone g-sensor works. It doesn't work for me.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I forgot to ask/comment about this... I found this problem as well. Thanks for reminding & confirming for me all in one post ;).

Gonna ping jonpry about this one now!

Edit - ironically jonpry said that change came the same time as the new acoustic stuffs - so on the newest g-sensor should work.
[Touch Pro2, Tilt 2 Android Development] skimike02:
I'm not sure what I am doing wrong. When I run haret, it boots straight back into winmo. This is on a rhod210 with a (nearly) stock setup. arrrgggghhh's FRX06 package with updated initrd.gz and rootfs from xdandroid.com, and the kernel, modules, and haret from the first post here. What is weird is it doesn't even try to go to linux, just straight to winmo. If I use an old version of haret, it scrolls a few lines and comes up with error messages.

Any idea what I'm doing wrong? I'd love to try out these new kernels. Thanks for any help.
[Touch Pro2, Tilt 2 Android Development] Vromoth:
Has anyone tried wifi Ace to fix the wifi? If fixed it for me in older kernels. Also if I try this kernel out will I be able to change back to my old one once I've finished testing it out?
[Touch Pro2, Tilt 2 Android Development] shatred:
yeah, i asked with some other people about a month ago in his thread but since then there was not any activity in the thread.

Is jerome still active or?..
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
Did you add this line to your startup:

set initrd_offset 0x00a00000
[Touch Pro2, Tilt 2 Android Development] skimike02:
Most certainly. If I try the new haret with old builds (I.e. stock or audio routing) I get the same effect. Reboots straight to winmo splash screen. Change the haret and everything works fine.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Hrm, you're the first to have this issue. Try with a (completely) stock FRX06 I guess...? jonpry has a 210, so I'm not sure dude. Maybe try a different SD... Also, where are you placing that set command in the startup.txt? Post it please.

Wifi-ace was only to fix issues with WEP networks. Don't use WEP, and I don't see what it has to do with this thread, unless you think it'll magically fix broken wifi in .39, which it won't.

Yes, he's still active... I don't know if he visits the forum often or not, but he's been working on the new acoustic code for a while now.
[Touch Pro2, Tilt 2 Android Development] motisu:
I also have a Rhod 210 and this .39 kernel boots without any problems, so it can't be the model type which is your problem.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Crap. I don't know what to tell you, your startup.txt looks fine.

Have you tried pulling ramconsole logs (might need to poke at them...)? Does the typical HaRET.exe loading bar pop up? As soon as it fills, that's when it reboots? Do you get the double vibe?

This is an odd one.
[Touch Pro2, Tilt 2 Android Development] skimike02:
Loading bar pops up. As soon as it fills, double vibe and reboots. I will look into how to do ramconsole logs...
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Yea, get some logs. I really am at a loss, as it seems you have done everything correctly...

The new haret should also work with older builds/kernels (does for me) so perhaps that is an indication.
[Touch Pro2, Tilt 2 Android Development] mbellot:
Good news with the latest .39, I'm not locking up as described here

Using the latest kernel and rootfs I still had to copy the audio libs to get sound, but that's working good too. Is there a new system.etx2 that has the libs integrated?

Gonna try running it while in Denmark on prepaid now that I have data worked out (thanks arrrghhh .
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
np. As for a system image that has the new audio routing hotness, hyc's is the only public one I'm aware of.
[Touch Pro2, Tilt 2 Android Development] ThrottleAbuse:
Is there something wrong with the link for the latest autobuild? It is only a 1 kb file?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Ah crap, I thought 3.0 was the only one that had this problem... jonpry is lookin into it, but WisTilt2 is away at the moment... Hopefully jonpry can sort it out.
[Touch Pro2, Tilt 2 Android Development] pdawg17:
Yeah...tried the 6/21 .39 kernel just posted and I'm getting a 4 kb file...
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Damn thanks button.

Yes, I already confirmed this. Not sure what the deal is, but without build logs I don't know what jonpry will be able to do... :/
[Touch Pro2, Tilt 2 Android Development] skimike02:
So, I poked around and didn't find much on ramconsole logs, other than to put "pwf dmesg.txt 0x8e0000 0x20000" as the startup text and run HaRET immediately after rebooting. That gave me the attached log, which seems useless... I've also attached the log from haretconsole, but I don't know what to make of it. Note, this is trying to run stock FRX06 with the new HaRET. As soon as I hit boot, the HaRET loading bar fills up, it vibrates ONCE, and goes to winmo splash screen.

Is there a different log I should be getting? Thanks.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Well you use haretconsole and do the pwf command. You had the right command, the only tricky part is haretconsole... do you need help with it? Use the new HaRET and a .39 kernel.
[Touch Pro2, Tilt 2 Android Development] skimike02:
I tried to boot the .39 kernel using the new HaRET. Phone restarted. Then I used haret console to grab the ramconsole log (attached). If this isn't the right log, then yes, I do need some additional help. Thanks.
[Touch Pro2, Tilt 2 Android Development] ThrottleAbuse:
Is there anywhere else I can get the newer kernal? Just trying to upgrade from stock FRX06
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Hrm, I can't really make heads or tails of that log.

Try the kernel I've attached to this post (.39 autobuild is hosed ATM...) It's the newest before the autobuild for .39 was hosed (I think... Date/timestamp is 6/19, 21:28) so it's not ancient.

Triple check your startup.txt and location for the kernel. Make damned sure you have it in the right place and the startup.txt kernel name matches the actual name of the zImage file...

Well I'm posting a kernel for skimike02, go ahead and grab it.
[Touch Pro2, Tilt 2 Android Development] randomblame:
If you get desperate you can always git the source and compile it yourselves
[Touch Pro2, Tilt 2 Android Development] xanathar:
Just tried the new kernel with the new acoustic code, it works pretty good on my RHOD100.

arrrghhh, I am having the same problems as you, i/o seems to slow down the entire system, with kswapd and loop processes consuming notable cpu cycles. I am using a Kingston class 4 card. This problem is not specific to the latest kernel, it also happens with previous .39 kernels.

Going to try it with a fresh data image.
[Touch Pro2, Tilt 2 Android Development] skimike02:
Thanks for your help. The 6/19 kernel is the one I have been using, but I tried again to be sure. Everything is at the root of the SD card, and as it works if I just replace kernel and HaRET with old versions, I am sure everything is in the right place. If 'set kernel' in startup.txt does not match actual file, HaRET doesn't load at all.

Does it help to know that it is only vibrating once on reboot to winmo, instead of twice like when it boots to android?

I've attached the log from 0x16f00000 if it is useful. Also, is there a place I can read up on changes between previous HaRET and current? This seems to be a HaRET rather than a kernel issue, since the problem is consistent across kernels, but always occurs with new HaRET. Thanks.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Hrm, I'll check the log. So when you say it's only vibrating once - you get the double vibe indicating the kernel has started, then a third vibe once the phone reboots, right? I thought earlier we established you were getting the double vibe.

You need the new HaRET for this new kernel, and tons of other people are using it. If you want the source, check the mailing list... I don't recall seeing it there tho.

Edit - log is pretty meaningless to me, I'm hoping it makes sense to jonpry... certainly more verbose than any of the others.

Yea, same experience - all .39 kernels were painfully slow at times for me. Lately I've narrowed it down to i/o, glad to hear a GSM user confirm the issue (using the same card as me too ;)).

I've been running some benchmarks per bzo, going to try and see if any of my SD cards have any better random write performance. In the two cards I tested (one being a nameless/classless 2gb card, the other my 8gb kingston c4 card...) both scored a paltry 20kb/s on random writes. Hopefully we can nail down this issue, jonpry was trying a dedicated swap file on the card, instead of using mmapping. I'm planning on trying to do the same.
[Touch Pro2, Tilt 2 Android Development] skimike02:
Sorry, I must have been mistaken earlier. I just checked (twice) and it is only a single vibe. HaRET loading bar - black screen - one vibe - winmo splash screen.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Hrm. jonpry suggested this might be an AMSS issue. Are you on some funky radio? Can you try flashing the stock radio and perhaps even stock ROM? This is definitely a strange problem, you're literally the only one who has reported anything even close to this...
[Touch Pro2, Tilt 2 Android Development] skimike02:
I am on the stock t-mobile ROM and radio, and I believe the latest version.

ROM Version: 1.91.531.4 (74508) WWE

ROM Date: 12/15/2009

Radio Version: 4.49.25.57

Protocol Version: 61.44tc.25.32AU

Definitely willing to flash new ones, or reflash the old, to see if it works. When I get a chance, I'll try my SD card in another rhod210 with the same settings...
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
lol, of course. I think this is the 'grab at straws' method, so yea... try anything at this point. I'm really not sure what could be holding it up. I almost wish someone else would have the issue so we can compare.... unless someone is being quiet, no one else has had this problem :p.
[Touch Pro2, Tilt 2 Android Development] reckert:
I've been playing a lot with the sd cards to see where the performance hit is. : it looks like in the drivers/mmc/card/block.c code, the driver assumes all cards use 512 byte blocks. - Based on some things i've read, and some tests I ran with HD_Speed, a lot of the larger cards have much larger block sizes- the two cards I have seem to be either 16K or 32k. so each 512byte write is actually 16k to the card. - since my card is formatted at 4k blocks, I was thinking if the writes were at 4k, that would speed things up dramatically. (Possibly make it a kernel parameter)

If what I think is right, then the combination of the .39 kernel and changing this could also make the class 10 cards useable.

UPDATE: the 512 byte blocks are also set throughout the mmc core, it will take a bit more to decode.
[Touch Pro2, Tilt 2 Android Development] pdawg17:
Is there any other way to get the updated .39 kernels? There is another new one dated today but it still spits out a 4kb file...
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
There's still some build error obviously...

I'll bug jonpry about it. In the meantime, use that last kernel I posted. If there's something really juicy in the newest, I'll post it.

Edit - looking at git, looks like he just added TOPA. Not earth-shattering :p.
[Touch Pro2, Tilt 2 Android Development] randomblame:
another commit went up fixing ipv6 stuff not too relevant to most folks
[Touch Pro2, Tilt 2 Android Development] ReeS86:
Hey the autobuild looks like its up again, just downloaded the build of .39 from today and the filesize was normal and the zip had both zimage and modules

Rees
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Yes indeedy, have at it you animals! ;)
[Touch Pro2, Tilt 2 Android Development] ImCoKeMaN:
Just wanted to post that I do have this problem as well on my RHOD400. I don't have much other helpful info at the moment though.

EDIT: actually it looks liek HaRET is detecting the device as a Leo for some reason, still not sure why, but that looks to be the problem (run haret without a startup.txt to test)

EDIT 2: It looks like this is listed in HKLM\system\platform\OEMString reg entry, but not sure how it's getting set as a reboot resets it and it is still found as LEO after resetting that reg entry and running HaRET

EDIT 3 (SOLVED): I reset the HKLM\system\platform\OEMString entry to t7380 and deleted the \\Windows\ModelName.txt file which had the T-Mobile_LEO incorrect data and now it is working. i'm still unsure what stupid cab file i installed that set that up, but i'm glad it's fixed hope this works for the one other case too =)
[Touch Pro2, Tilt 2 Android Development] skimike02:
Sweet! Thanks. My txt file was right, but I had to make the reg change.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
What a wacky bug. Glad it's fixed for you too, I'll add this to the first post ;).
[Touch Pro2, Tilt 2 Android Development] xanathar:
Does anyone have problems with extUSB headset/headphones? Latest kernels with the new acoustic code outputs audio to the speaker even if a headset is attached. Tried it with the standard HTC headset, a cheap extUSB-3,5 adapter and with HTC YC-A300. .29 with the acoustic code works fine.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I assume you mean .27 ;)

Interesting observation. Not sure jb is aware - are you running FRX06 with the manual audio routing changes from the "[TESTING] New audio routing for Froyo" thread? There's some new stuff, but I don't think there's been any binaries of it.
[Touch Pro2, Tilt 2 Android Development] xanathar:
oh, crap :D

Yes, I'm using the latest libraries -- jb's repository for userland libs https://gitorious.org/~jbruneaux/xdandroid/hardware_msm7k_libacoustic does not have any new stuff.

Userland logs do not show anything about headset, I remember it reporting plug/unplug events on .27.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I don't think the testing thread has the newest code from jb's repo which you've linked above - did you compile from his repo yourself...?
[Touch Pro2, Tilt 2 Android Development] xanathar:
Hey, you're right. I'm currently compiling the libs, will report back.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Post 'em in the audio routing thread if you could please :D
[Touch Pro2, Tilt 2 Android Development] Starfox:
I really hope that .39 becomes usable soon. I just had to nuke my data.img because the phone battery died and it kept panicking during boot. Going to a journaled FS should get rid of the nonsense.

-- Starfox
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
So.. .39 isn't to blame then? I'm confused, you say a journaled FS would solve your problems...

jonpry has run out of things to fix supposedly on .39. I still haven't been able to figure out why it's slower - his theory was memory getting overrun, but even with swap space it still is painful. I know swap is slow, but it's better to have that than run out of RAM... which these phones seem to do so fairly quickly.
[Touch Pro2, Tilt 2 Android Development] manekineko:
No, he's hoping that he can switch to .39 fulltime soon, so he can use a journaled filesystem.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Well I'd like to run .39 fulltime as well, but the crippling slowdowns are... unbearable. Wish I could figure out what the deal with that was.
[Touch Pro2, Tilt 2 Android Development] djcrosstunez:
I just installed the latest kernel from 17 july.

Noted that wifi seems to work. But when connecting it hangs at ; getting ip adress..?

Is overclocking supported jet?

Thanks for the hard work devs!!
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Neither OC nor wifi is supported yet. With some additional firmware, you can get wifi working (supposedly) but I was never able to...
[Touch Pro2, Tilt 2 Android Development] detule:
For people proficient in an adb shell, instructions to get wifi working on .39:

Step 1. Download the new firmware from: http://nv-tegra.nvidia.com/gitweb/?...n;hb=5e9802c5cb6f7bd0d1e763b6d604cd3003fda8f8

Step 2. Make sure you have rw access to /etc (note, in FRX06+ this means remounting /system as rw)

Step 3. Repace the file /etc/wifi/bcm432x/bcm4325-rtecdc.bin with the one you downloaded in Step 1.

Step 4. Thank jonpry, wistilt2, arrrghhh, rpierce99, etc for developing and testing this nice piece of work. From some of the other threads, it's a little baffling to read the sense of entitlement oozing from people's posts when it comes to these builds.

On my Rhod400, using the above firmware I have had no problems connecting to open/WPA secured networks.

The original instructions as conveyed by jonpry can be gleaned from the logs found here:

http://irclog.netripper.com/htc-linux/2011/6/11/
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Thanks dude, I'll add this to the second post!
[Touch Pro2, Tilt 2 Android Development] detule:
Jonpry, powertop output during badness:

Wakeups-from-idle per second : 1932.9 interval: 10.0s

Top causes for wakeups:

67.6% (1302.9) <interrupt> : vsync

16.5% (317.3) <interrupt> : msm_otg, msm_hsusb

6.0% (114.7) <interrupt> : gp_timer

5.2% (100.1) <kernel core> : hrtimer_start_range_ns (tick_sched_timer)

3.7% ( 70.7) <interrupt> : msm_i2c

0.3% ( 4.9) PowerManagerSer : hrtimer_start (bma150_poll_timer)

Couple of notes: these numbers are not really accurate, at least the parenthesized per second numbers - upon initializing powertop the on screen message says "collecting data for 5 seconds" but in reality it collects data for ~120 sec. This is confirmed by manually counting gp_timer in /proc/interrupts counting at approx 5 ticks / sec. So perhaps dividing the parenthesized numbers by a factor of twenty-something should provide a more accurate per second.

Also, msm_i2c is not counting fast -> these numbers are pulled from an adb shell opposed to earlier when i was counting using ConnectBot - those keystrokes were driving up that count, as you suspected.

For sake of completeness, here is my powertop output during normal operation:

Screen off:

Wakeups-from-idle per second : 228.2 interval: 10.0s

Top causes for wakeups:

46.5% (103.4) <interrupt> : gp_timer

45.0% (100.1) <kernel core> : hrtimer_start_range_ns (tick_sched_timer)

6.5% ( 14.5) <interrupt> : msm_otg, msm_hsusb

0.8% ( 1.8) er.ServerThread : hrtimer_start_range_ns (hrtimer_wakeup)

0.4% ( 1.0) m.android.phone : hrtimer_start_range_ns (hrtimer_wakeup)

0.3% ( 0.6) <interrupt> : msm_mdp

Screen on:

Top causes for wakeups:

30.1% (110.3) <interrupt> : gp_timer

27.4% (100.3) <kernel core> : hrtimer_start_range_ns (tick_sched_timer)

20.9% ( 76.7) <interrupt> : msm_i2c

16.3% ( 59.7) <interrupt> : vsync

2.6% ( 9.7) <interrupt> : msm_otg, msm_hsusb

1.4% ( 5.0) PowerManagerSer : hrtimer_start (bma150_poll_timer)

I need to recompile the kernel with CONFIG_LATENCYTOP and I will try and get you some latencytop output (perhaps next week).

Thanks
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Thanks detule! Should've told me, I would've updated the first post :p.

Heck, I can probably even give you rights to this thread and just make it yours. Its more yours than mine anyways ;).
[Touch Pro2, Tilt 2 Android Development] großa:
Hmm, yes it is fast.

Copied the csv files to the root of the sd card, overwrote the wifi firmware and the libaudio files. No need to chmod it, it was already ch modded.

Working fine untill I call somebody. Tried it with my wifes phone.

Her phone is ringing, the screen on the rhod goes black and that's it :confused::confused: Can't wake it up. If I call my Rhod, it won't ring.

Something with the new prox sensor perhaps?!

Could somebody please post the new libacoustic files? Just got the ones from hyc's old post (may 2011).

Also the "not cleanly unmounted.." message appears again. Wasn't that fixed in the autobuild kernels or just in starfoxes test kernel?
[Touch Pro2, Tilt 2 Android Development] detule:
Try it without mounting the sensor library -> with the stock/old sensor library the proximity sensor _never_ gets enabled. If you encounter similar behavior then it's not the proximity sensor, and it's probably a matter of the manner in which you integrated acoustic. Posting logs would also be helpful.

Here's the deal: recently there was a change in the way "the new" acoustic device is handled -> its name was changed in the new libaudio libraries. So it's either the kernel works with 06+/old libraries, or the kernel works with the new libraries that are not widely available yet.

It's a very minor correction for me to change the kernel to make it compatible with the new libraries, but for now hyc's build/audio libraries are more widely available (even though perhaps somewhat outdated).
[Touch Pro2, Tilt 2 Android Development] großa:
I'm starting from the scratch. Forgot pm.sleep_mode=1 in the startup.txt :D (because I'm using starfox test kernel, there's no need for it)

Here are 2 logs (still without pm.sleep_mode=1).

Second one is with increased space for initrd and rootfs (saw errors which said "not enough space".

Same behavior:

I'm calling out, screen goes black, sound is fine. After I end the call (b4home) screen stays black. After a while and trying to call my phone, sliding the keyboard out etc, screen is awake again.

After that, I tried to call my other phone again, got no sound. Ending the call did not work. Had to reboot.

So next round, with pm.sleep_mode=1 enabled. Almost the same thing as before, but this time I could make a second call (perhaps more) and my phone could be called with sounds.
[Touch Pro2, Tilt 2 Android Development] aichemist:
When you guys get this running, can we get some instructions on the 1st page ? Sorry about the demand, Thanks!! We would love to test this =)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
There.... are instructions on the first post. It's been running for ages. The directions have been there for ages as well.

Edit - Detule's directions are pretty clear... I'm not going to add it to the first post until the autobuild is updated.
[Touch Pro2, Tilt 2 Android Development] großa:
Some new logs:

four with increased system.ext2

five with increased system.ext2 but without sensors.default.so (ACL mentioned it's only for GB not Froyo)

Both times working fine at the beginning, rear speaker does some noise and suddenly rear speaker is on and doing noise all the time. Sounds are completely dead.
[Touch Pro2, Tilt 2 Android Development] detule:
Thanks for your logs. This kernel includes a small modification to the proximity driver that enables the sensor for froyo not just gingerbread. The caveat is, in froyo the sensor library is pretty dumb, and to ensure (all) sensors is being polled, you need to make sure that you have Auto-Rotate enabled in Settings->Display.

Audio routing issues are because the acoustic libraries in 06+ and in Hyc's thrread are outdated. There is active work on this front, and I will update my tree as soon as a definitive acoustic userland product appears. I see you have a RHOD100 -> if you are interested in testing some of these libraries, stop by #xdandroid.

WisTilt2 is also interested in picking up where he left of with this kernel so this bodes well for .39.