yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] crownvn:
very sad.... it still can't with the messages not successful I wonder if it was lock by security?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I'm not sure. Is this in a card reader device (like a full size SD converter?) or are you doing this through your TP2?
[Touch Pro2, Tilt 2 Android Development] crownvn:
first time I ran NeoFroyo V0.1 with partitions 3ext by mini tool then I came back your build with the text " no_partitons" in startup.txt ( no format my SD Card) android 's running normal until I updated latest kernel then came back original kernel I found the problem. I checked my SD card have free space 545 MB.

I used mini tool delete or format 3 ext the notice successful but it was not deleted or formated . now my SD still runs android with latest kernel normally except cut, paste, delete file or folder and format in there :D
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Perhaps you've written to the card too many times? Dunno.
[Touch Pro2, Tilt 2 Android Development] jordanthompson:
what happened to Glemson's build site?

Seems it is off the air :-(
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
It is, use the mirror.

See Incremental Updates.
[Touch Pro2, Tilt 2 Android Development] jordanthompson:
Thanks for pointing out the mirror I completely missed it.

I have downloaded the latest two updates and tried to install them the way I always have (erase zImage and modulesxxx, copy the new files onto the card, rename the new zImagexxx to zImage and reboot) but when haret gets to "rebooting in 5 seconds..." the phone reboots back into windows.

I slowed the clock frequency to apcuclock.oc_freq_khz=680000 (just in case) but it always reboots at the same point in time.

---------- Post added at 07:27 PM ---------- Previous post was at 07:16 PM ----------

I'm thinking my SD card died. Am HP-Formatting it now...
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Hrm. I dunno, I guess let us know what happens after the format.
[Touch Pro2, Tilt 2 Android Development] geminix2:
I too had missed the mirror link, thanks
[Touch Pro2, Tilt 2 Android Development] jordanthompson:
Well that was a bust too :mad:

I am now just starting from scratch:

downloading FROYO from here:http://xdandroid.com/wiki/Version_FRX07

downloading updates from here:https://code.google.com/p/zimages/downloads/list

and here: http://files.xdandroid.com/rootfs/

I'll keep you posted...

---------- Post added at 09:30 PM ---------- Previous post was at 09:10 PM ----------

I am getting nowhere fast! Still no joy. Now I am going to try a plain Jane FROYO from here:http://xdandroid.com/wiki/Version_FRX07 with no changes.

---------- Post added at 09:40 PM ---------- Previous post was at 09:30 PM ----------

So I had to add my startup.txt and ts-calibrarion files, but it is booting fine right now! I will add the latest zimage next. One thing at a time ;-)

---------- Post added at 09:58 PM ---------- Previous post was at 09:40 PM ----------

Same stuff (it crashes during boot at the same point.) When I use the FROYO out of the box, it works fine. When I add the zimage from the mirror, it crashes... Its like the zimage isn't for my htc sprint touch pro 2!

---------- Post added at 10:53 PM ---------- Previous post was at 09:58 PM ----------

Anyone have any suggestions?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Don't use that zImage? Have you narrowed down which one starts the problems?

I sincerely hope you're downloading a .27 zImage.... If you're downloading a .35 or .39 zImage, that would certainly explain it.
[Touch Pro2, Tilt 2 Android Development] jordanthompson:
It seems that anything I download from the mirror site causes the problem. I went back about 5 zImages and none of them worked. I never had to differentiate between releases on the glemson site - I always just grabbed the latest one.

Not sure what you mean by .35 or .39. The most recent ones are: modules-2.6.35.14-93975-gc18f055.tar.gz and zImage_20111201_185011 but as I said, I tried all of them back to modules-2.6.35.14-93975-gc18f055.tar.gz and zImage_20111201_185011.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Sigh. Did you bother looking at the numbers?

modules-2.6.35.14-93975-gc18f055.tar.gz

Please download a .27 kernel.

Edit - perhaps I should've been more clear, and that's my fault - but that mirror site is just a jumble of all the kernels being built by the autobuild service. GlemSom's actual site would break it down by kernel type, so if you went to the 'main' page you would only be presented with .27 kernels.
[Touch Pro2, Tilt 2 Android Development] jordanthompson:
Well I do appreciate your patience. It looks like the most recent 27 kernel is modules-2.6.27.46-01356-gd4c73bd.tar.gz which is what I already have from my July 15 build. I guess I was hoping for something a little newer.
[Touch Pro2, Tilt 2 Android Development] JDog2pt0:
Would there be any advantage to running a .39 kernel over a .27? After going through the trouble to make it work that is.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
2 things.

htc-msm-linux-20111017_080427-package.tar.bz2	build: htc-msm-linux , timestamp: 20111017_080427	Oct 16	2.4 MB	8576

Is the latest .27 kernel. That's October 16 - FRX07.1 was released before that, so there's a newer kernel.

Second, you have to keep in mind - .27 is ancient, and the devs aren't focusing on it. They're focusing on getting the newer kernels up to speed, and in theory they will eventually surpass .27. In the meantime, .27 isn't going to get any attention. What's the point in putting limited resources in an old hacked up kernel? New base is very appealing, for many reasons.

Not at this time. .27 is more stable. Unless you want to test and work with the devs, I don't see any reason for a 'normal' user to run anything but .27.
[Touch Pro2, Tilt 2 Android Development] JDog2pt0:
Well, I'd love to, but since I'm brand new to Android and know nothing about it, all I can be right now is a user; not a contributor.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Yea, .27 works pretty well - it is quite mature. Just an older codebase, so the newer kernels will hopefully in time work better with newer builds. They just need more polishing, and include things like the new acoustic code adding additional complexity for the average user.
[Touch Pro2, Tilt 2 Android Development] jordanthompson:
It seems it is back on the air :-)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Seems to be! Thanks for the report.
[Touch Pro2, Tilt 2 Android Development] majkeljj:
not fixed on Raphael GSM, hangs on "HARET: Booting Linux..." window:(

edit:

not working newest kernel ...37. this one ...34 for raph/diam works ok :)
[Touch Pro2, Tilt 2 Android Development] d0nate110:
Hello, man !

Thanks for newest kernel updates !

Could you use this thread for uploading newest kernels till htc-msm site is down ?

Thank you anyway !!!
[Touch Pro2, Tilt 2 Android Development] xUmaRix:
wlan: version magic '2.6.27.46-01231-gfca2168 preempt mod_unload ARMv6 ' should be '2.6.27.46-01237-g8c0ce38 preempt mod_unload ARMv6 '
[ 5464.647033] wl1251: version magic '2.6.27.46-01231-gfca2168 preempt mod_unload ARMv6 ' should be '2.6.27.46-01237-g8c0ce38 preempt mod_unload ARMv6 '
[ 5464.874969] wl1251: version magic '2.6.27.46-01231-gfca2168 preempt mod_unload ARMv6 ' should be '2.6.27.46-01237-g8c0ce38 preempt mod_unload ARMv6 '

seems like there are differences in the module version.hope u can re check againt
[Touch Pro2, Tilt 2 Android Development] xrshwy:
I am testing...

Kernel: zImage-2.6.27.46-01237-g8c0ce38

Modules: modules-2.6.27.46-01237-g8c0ce38.tar.gz

but, wifi doesn't work!
[Touch Pro2, Tilt 2 Android Development] pdawg17:
Wifi fine on Rhod400 (if that helps troubleshoot)...
[Touch Pro2, Tilt 2 Android Development] solevi:
Are You using overclock utility like OCT? if Yes, Disable it before launching Haret!
[Touch Pro2, Tilt 2 Android Development] majkeljj:
no, I don't use any overclock utility, but I noticed that haret booting problem I have in the newest kernel 1237 (the same was in 1233). with 1234 for raph/diam android booting ok.
[Touch Pro2, Tilt 2 Android Development] pdawg17:
Is it possible to post the newest kernel soon? I see there is one posted today by ACL for "speakerphone mic fix"...or is there somewhere I can find it myself?
[Touch Pro2, Tilt 2 Android Development] F22:
Dec 18th Kernel (1238) - Speakerphone Mic Fix

New Kernel posted. And yes, this one includes WisTilt2's speakerphone mic fix. Enjoy! As always, look at the Latest Kernel entry in the first post of this thread for more info.
[Touch Pro2, Tilt 2 Android Development] pdawg17:
Thanks a lot!
[Touch Pro2, Tilt 2 Android Development] F22:
non rhodium wifi

Try the 1238 kernel and its modules file. Hopefully the issue is now fixed.

EDIT: Whoops! My scripts packaged the 1237 version of the module with 1238. Will fix and put a new modules file up for 1238.
[Touch Pro2, Tilt 2 Android Development] DmK75:
I also noticed this mismatch.

If 1237 zImage used with 1238 modules, renamed to "modules-2.6.27.46-01237-g8c0ce38.tar.gz" Wifi works now :)
[Touch Pro2, Tilt 2 Android Development] F22:
WiFi Fix for Non-Rhodiums

I've updated the modules download for 1238 in the first post. Anyone with a non-rhodium (Topaz, Raphael, Diamond, Blackstone, Kovsky) whose wifi stopped working after trying the kernels posted here, please try the latest build and let me know how it works. Hopefully the problem is fixed!
[Touch Pro2, Tilt 2 Android Development] F22:
Heheheheheh...I'm going to rename it and change the link for 1237. Both 1237 and 1238 should work for wifi on non-rhodiums now. Thanks for the confirmation.
[Touch Pro2, Tilt 2 Android Development] DmK75:
OK, with new 1238 wifi working. Thanks.
[Touch Pro2, Tilt 2 Android Development] iris_aim:
wifi not working on t-mobile touch pro 2

hi every1

recently i went on to try the neopeek edition hoping it would keep my storage card cleaner when i work in windows mobile but have tumbled upon a problem...perveiosly perfectly workin wifi on FRX 03 edition is no longer working for me in neopeek...i definitly want to keep neopeek ediion...to solve the problem ive copied the latest kernel from here and copied it to both the root of the storage card aswell as "zimage" into the folder named "npkinstall"

i a newbie in android world so please guide me what do i need to do to get the wofo going(carrier data is working fine for me)

Help please
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
So you crosspost, create a new thread... and still you're not posting in the neopeek thread.
[Touch Pro2, Tilt 2 Android Development] majkeljj:
hangs on booting linux screen on Raphael The same was in 1233, 1237, only 1234/5 works ok on FRX03 XDANDROID.

edit: after adding new build.prop and 3d drivers 1238 start to work:) I noticed only wakeup problem during and after call, restart required. also end call button don't end call.
[Touch Pro2, Tilt 2 Android Development] revanmj:
On my Touch Pro WiFi works only for a few minutes. After that it always shows an error and disables itself.
[Touch Pro2, Tilt 2 Android Development] DmK75:
I noticed that Topaz with 1238 kernel have constant little noise from speaker.
[Touch Pro2, Tilt 2 Android Development] R^7Z:
No wifi for me (error when enabled) but that doesn't mean it doesn't work for anyone else. Will recheck and post again but I did a logcat and will upload to pastebin and attach HERE. Keep in mind, this is a

trimmed

logcat, I figured you only needed the part that states there is an error when the action is done. I am going to try again, this time use the package that was working to confirm the data.img isn't corrupt and post back my reply.

For reference the package that is causing the error for my Fuze/RAPH110 is Commit# 1238. Last time wifi worked was with Commit# 1232 and I will be testing with Commit# 1235, which includes Commit# 1234.

After I have done all of that (if still not working), I am going to see about starting over from scratch. This includes formatting (fat32), extracting the package and testing out the packages. If needed, I can provide my startup.txt as well. Let me know if this helps or if I need to try to post another trimmed logcat. Either case will be posting more after I run my tests. Thanks in advance for any help any of you can provide. :)

[EDIT]WiFi is working with Commit# 1232 only so far. Going to try a clean install, not sure if I'm the only person having problems with this but I don't require WiFi use, just trying to help identify and or isolate the problem(s)[/EDIT]
[Touch Pro2, Tilt 2 Android Development] F22:
I can't really tell what's going on from the logcat. Get me a dmesg too. If you need instructions, just let me know. Btw, what rootfs.img are you using? The error that occurs when loading your keymap binary tips me off that you're not running the stock rootfs, and it makes me wonder what else has been "modified" in your build. So yes, try the clean install first, and if you still have a problem, then post the dmesg.
[Touch Pro2, Tilt 2 Android Development] R^7Z:
Going to run from scratch any way specifically you want me to run the dmesg and logcat? At the moment, I am using an app that runs these commands. Also going to re-download everything and use everything from the xdandroid site, minus the kernel package. Going to start with what I know works from Commit# 1232. No idea as to what's going on with the rootfs but I modified some settings from within Android, not sure this make a difference. I am also

not

going to change a thing, minus add a few apps to AndroidApps folder. Thank you kindly for assisting me with this.

[EDIT]Here is what I re-downloaded: rootfs-20101115-42b44e2.zip, initrd-20100813-b11116a.gz and system-FRX03.ext2.zip I was using XDANDROID.2.2.1.AOSP.FRX03.21.11.10.FULL_PACKAGE.zip (both from http://htcandroid.xland.cz) Here are the logs:

logcat, dmesg and my startup[/EDIT]
[Touch Pro2, Tilt 2 Android Development] F22:
See the last line of my previous reply. :D It looks like you read my post and started your response before my edit showed up.
[Touch Pro2, Tilt 2 Android Development] R^7Z:
That unfortunately is from a clean install: format fat32 and copied over the files. The only exception are/should be the startup.txt and the added apps, right? I can post up my current config and let you take a look; everything should be "stock" minus the apps. Would this even be considered an issue if it displays an error?

ALSO, I re-downloaded the kernel pack from your first post, not sure that makes a difference, don't know why it would... :confused:
[Touch Pro2, Tilt 2 Android Development] F22:
I'm a bit confused too. The dmesg/logcat in your previous post was from the 1232 kernel that you said worked, not 1238. Is wifi still working? Or is it not working this time around? If it's not working at least it (1232) is now working the way I expect for non-rhodiums, as in not at all. It was 1237 and 1238 that I said should have working wifi for non-rhodiums.
[Touch Pro2, Tilt 2 Android Development] R^7Z:
Dude, I'm rolling back. Sorry, this is getting waaay to weird for me to keep track. For now, let's go with the assumption that I haven't a clue as to what I'm doing (it saves for attempting to explain things at any rate and probably some confusion) It's all good, doesn't seem like anyone else is having this problem so we're good for now, I think.

I might try again later but I think I'm losing my mind ( short trip for me :p ). At first, I thought it was 1232 that was working but now, I'm not so sure... :confused:
[Touch Pro2, Tilt 2 Android Development] d0nate110:
18.12.2010 - Battery drain

Man, this new kernel 18. DEC drains battery fast as hell !

5-9% per hour !

Can somebody integrate mic fix into old kernel from 12.dec or so ? Cuz otherwise its just brings the battery to fast down...

Thank anyways for amazing work !
[Touch Pro2, Tilt 2 Android Development] bauner:
Wifi works for me with 1238 on raphael and blackstone after boot.

But after switching it off I have to reboot to get it working again.

same problem on my 2 devices. With this kernel I have constant very low volume noise from external speaker.

I think this is the battery drain...
[Touch Pro2, Tilt 2 Android Development] pdawg17:
I have noticed the "noise" on my Sprint rhod400 as well...I was curious if anyone else was going to mention it...

I really need the speakerphone mic fix for hands-free but hopefully some more tweaking can be done...
[Touch Pro2, Tilt 2 Android Development] F22:
Power Drain

It's believed that one of the commits on the 17th is responsible for the additional power drain. I wasn't able to try out all the kernels I posted myself. I'm wondering if there is a consensus on which of the kernels the increased power drain first appeared. Thanks.
[Touch Pro2, Tilt 2 Android Development] F22:
Identifying the Problem Commit

I'm willing to build a kernel without the commit that increases the battery drain (until it's fixed) if we can identify the commit that caused it. Identifying the commit responsible will also enable the development team to permanently fix the issue more quickly.
[Touch Pro2, Tilt 2 Android Development] d0nate110:
HELP

I'm a little linux pro, so if I can help you somehow - just let me know !

I'm not sure how I can help you, but these kernels all are looking same as standard linux build. May be with some know-how from you I can test it right on my PC ?

Anyway I'm ready to help be it test-issue or advice, just let me know !
[Touch Pro2, Tilt 2 Android Development] F22:
battery drain problem

I have three kernels from the 17th that are downloadable from the first post. In which of those does the accelerated battery drain first appear?
[Touch Pro2, Tilt 2 Android Development] d0nate110:
Man, I already deleted all "bad" kernels :( . If you give me 2 days - I'll make a new test for all 3 kernels from 17.DEC. But I believe in 13.DEC the issue wasn't there...

What has been changed since this 13.DEC kernel ?
[Touch Pro2, Tilt 2 Android Development] F22:
There were no commits on the 12th through 16th. So you're probably using someone's test kernel. The last commit before the 17th was on the 11th. All the commits to the official tree are listed in my first post. Look at the commit messages associated with the individual commits. You will also find a link to the commit log on the repository in the first post of this thread, it's the linux-msm repo link. From there you can view the actual edits to the kernel that were made in each commit.
[Touch Pro2, Tilt 2 Android Development] DmK75:
I sure it because audio always enabled, continuous noise in speaker.

В динамике постоянное шипение.
[Touch Pro2, Tilt 2 Android Development] F22:
battery drain problem

This was my thought too, but I discussed it with the author of the patch earlier today and he believes they're separate issues. He removed the commits to the kernel tree after Dec. 4th, leaving only his own Dec. 18th commit in place, and the accelerated power drain issue disappeared. Given how short the Dec. 11th commit is, we're fairly certain that isn't the cause. It must be one of the Dec. 17th commits.
[Touch Pro2, Tilt 2 Android Development] DmK75:
Maybe drain is not in this, but i replaced kernel to 1237 and noise disappeared.

In any case, working speaker will consume more battery.
[Touch Pro2, Tilt 2 Android Development] d0nate110:
Which latest kernel has NO fast drain ?

Thanks for speaker advice !

(Я проверю кстати шум идёт или нет.)
[Touch Pro2, Tilt 2 Android Development] F22:
Yes, reverting to 1237 should address the noise issue at least. Let me know if you get any power savings, and if so how much.
[Touch Pro2, Tilt 2 Android Development] SyubSnunb:
With rhod 400 when I boot kernel 1238 the first time wifi is working but any subsequent boots wifi reports an error and android becomes very slow. Is anyone else experiencing this with a rhod 400 or any of the other rhods? I have not had a chance yet to go back and try any of the other kernels F22 has so graciously posted since glemsom autobuild is down.
[Touch Pro2, Tilt 2 Android Development] princ3ofd3sis:
Rhodium Fix?

"Note: Module file builds prior to the Dec. 19th update for 1237 & 1238 did not have working wifi for non-rhodiums."

i installed the 1238 but my wifi still isn't fixed so is that a misprint, and what you mean to say was that did not have working wifi for rhodium?

or do the earlier ones before dec 19th have working wifi for rhodium?

sorry if this is a noob question.

i did what was written but after installing 1238 my wifi wasn't fixed (although the USB was connecting and the sign came up on the phone for it. just gotta somehow install the driver now).

any help would be much appreciated.

and of course, thanks a lot for this!
[Touch Pro2, Tilt 2 Android Development] F22:
WiFi Issues

Wifi should work on rhodium with all of the posted kernels. Wifi on non-rhodiums should only work for the modules files associated with the two latest kernels (1237 & 1238), and even then only for the module files updated on Dec. 19th, and not the earlier ones. Prior to that the driver wasn't being compiled for the correct release. Nevertheless, there have been enough complaints regarding non-rhodium wifi since this last update that it does look like there are some remaining issues, at least for some people. I will look into this further.
[Touch Pro2, Tilt 2 Android Development] ice.bogdan:
Hello,

I'm running a TOPAZ and I've been testing your builds for a while now.

Quick question, what does this mean?

mdp irq already on 4 4

mdp_dma: busy

it keeps looping on boot

system_server is at 99% cpu on top and the system is really slow.

Also, wifi doesn't work, it can't find any network.

I've tested 1237 & 1238 on a fresh install. I also build the 1239 kernel from git today and it's the same, the only good this is the speaker hissing sound disappeared.
[Touch Pro2, Tilt 2 Android Development] JimboJoe:
Commit 1239 seems to be a fix to the hissing sound and battery drain.

The 99% CPU is a recurring issue, that has been happening for a couple of months.

Reboot usually solves the problem, and I happened to find out that charging the phone solves this issue after a dozen of minutes.
[Touch Pro2, Tilt 2 Android Development] ice.bogdan:
Thanks for the reply. I have no clue what I did, but I got the wifi working and also it stopped lagging. I'll get back after more testing.
[Touch Pro2, Tilt 2 Android Development] F22:
New Kernel (1239) Dec. 21, 2010

New kernel posted. See first post for details.

ice.bogdan: JimboJoe is right. The 99% CPU problem is a recurring issue that has been around for a few months. The system_server process goes berserk and grabs as much of the cpu as it possibly can, leaving little processing power for everything else, and thus making the system slower than a turtle. Often letting the handset sit for awhile (but not always) fixes it. JimboJoe's assertion that leaving it in the charger will fix it is interesting as usually my handset is connected to the charger while I'm letting it sit... Rebooting will also usually (but again not always) fix it. It's a very annoying issue, but hasn't yet made it to the top of a dev's priority list.
[Touch Pro2, Tilt 2 Android Development] Thelightning87:
Thanks a bunch for keeping us updated!
[Touch Pro2, Tilt 2 Android Development] perern:
this is happening on my TOPAZ too :(

works for 5 min and freezes
[Touch Pro2, Tilt 2 Android Development] trusa1:
Did you mount something in froyo.user.conf?

Check the size of mounted files. Probably some of the mounted files is corrupted.

I've had the same error.
[Touch Pro2, Tilt 2 Android Development] sad0felix:
Sorry, was out for a week, didn't have time to check kernels in midst of it.

Going to test the latest now, the previous one (2010.12.11 first version, 8mb modules) gave me lots of problems on boot (system_process).

This is my mirror of the latest, in case you have probs with mediafire:

zImage-2.6.27.46-01239-gacf4596

modules-2.6.27.46-01239-gacf4596.tar.gz

Cheers