yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] Viper Matrix Wireless:
I do the same thing usually except for I may have apps in the androidapps folder upon initial boot. However, I have noticed an issue in FRX03 having to do with media scanning of sounds. Seems it works partially but it causes the system to be hardly unresponsive until I run media scanner in dev tools. Ever since FRX03's release I have had issues on past kernels even prior to FRX03 release. FRX02 does not have the performance problems that occur in FRX03. I did get the 1245 kernel to work. I havent had a problem with it. I also own 2 SD Cards & am using the newest one 16GB Class 10 I received 2 days ago. I have managed to get the performance issue to go away mostly but I have to manually set ringtones & such for them to sound off.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Sorry to lump the quotes together, but what I'm going to say applies to both:

There's an issue with the system_server process. It's probably something that's missing or gets hung within the system, not sure what the root cause of the issue is... but basically system_server process steals every last processor cycle it can grab, which with our already slow procs isn't a very pleasant experience.

There's been some "fixes" (workarounds, if you can even call them that :p) - some people say running Places/Maps makes it go away, some said making a phone call does as well. I haven't found anything that gets rid of it 100% of the time. Sometimes just waiting for it to work out its daemons is enough. But other times it never recovers (or I just get impatient) and I just end up soft resetting.

Rebooting can fix it, but sometimes you'll have to reboot several times. It honestly has gotten much worse recently, and the devs have recognized that. Hopefully we'll get some resolution to it soon...
[Touch Pro2, Tilt 2 Android Development] Viper Matrix Wireless:
But the problem does not occur in FRX02. Its speedy in the beginning with no waiting. When FRX03 was put together something got messed up.
[Touch Pro2, Tilt 2 Android Development] MassStash:
Should(could) we use a different build entirely than FRX03, like a neopeek? See what thats like? been thinking bout tryin it n havnt yet....
[Touch Pro2, Tilt 2 Android Development] Viper Matrix Wireless:
You can get older builds like FRX02 from here:

http://htcandroid.xland.cz/?C=M;O=D

I just ran FRX02 from Oct. 25 & found it performs very well & doesnt get stuck like FRX03.
[Touch Pro2, Tilt 2 Android Development] MassStash:
Right right, that's interesting... the neopeek builds were pretty business tho because thats basically all I ran when i was doin dual boot. Superfroyo was really good n I definately could go for a cm61 rom working on nand, oooooooowwweeeeeee

from a Rhod400: runnin' CustomNandFRX03: usin' XDA App
[Touch Pro2, Tilt 2 Android Development] d0nate110:
Battery test report

Just ended the testing of 1245-Kernel

In 19 hours drain was from 100% to 68% (32%) it's about 1,68%/hour.

Just sleep mode drained 1,66%/hour its worse as 1242 !

BTW wifi didn't worked after awaking from long sleep !

So for the time being the 1242-Kernel is the best !
[Touch Pro2, Tilt 2 Android Development] dbox2:
Tried also the 1245 kernel together with the modules, and the system.ext2 version frx02 (25 Oct). After a few minutes Wifi didn't work anymore and after installing a few programs and a reset the haret.exe does not boot anymore, it hangs somewhere.. Think I'll try the ext2 version frx03, maybe that works better for me.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I can assure you the system_server bug exists in FRX02 - it just occurs much less frequently. For whatever reason, the newest stuff seems to be making the issue more of an issue...

Either way, I do have a question for ya - are you running kernels from 10/25, or just the system image FRX02 with a new kernel? Just curious to see if it's a userland or kernel problem - I have a pretty strong feeling it's userland, but I'd like to confirm.

I'll try to pull some logs when I get a boot where system_server is killing everything. Hopefully then if it happens early in the process I can capture the root cause and we can start working towards a resolution.

Hope you guys all have a Merry Christmas, this project is making insane progress. Once we get it all committed, there will no doubt be a lot of cleanup work to do. We're getting very close to "completion"!
[Touch Pro2, Tilt 2 Android Development] gmanfuzing:
First i would like to say thank you to f22 for being so gracious as to put these files on the site so i don't have to go to glensom and look for them myself

Second i wanted to ask if anyone else with a rhodium is experiencing wifi generating an error EVER OTHER BOOT. Initially wifi works great. It's upon my next boot however (which usually only happens because i stop getting radio signal) that i loose wifi and start getting an error, but if i reboot again wifi comes back strong. Just wanted to see if others had this strange problem out there.

Also I know im not in a strong service area, but whenever i loose service in WM it always comes back and i never loose it for that long. The difference is in android sometime after a random amount of time i loose service all together and it will not come back even if i try putting the phone in airplane mode and taking it back out :\

Does anyone have a clue whats goin on here either?
[Touch Pro2, Tilt 2 Android Development] Viper Matrix Wireless:
I can tell you that running an older kernel gives me a better result. However, when running FRX02 with a new kernel its not as bad as running FRX03. Seems when I ran FRX02 last nite that it upgraded to FRX03. I'm trying to figure out when this happened because it shows FRX03 in the system info but im sure its FRX02.

They really need to find why it shows its busy on IRQ 4 4 is how im interpreting it. Maybe that is one of the causing problems. I also want to test bringing down the processor power in WinMo before I boot into Android & see if I can get Android to stop stuttering like that.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
A) the IRQ 4 4 can be ignored, it'll get commented out soon (per ACL).

B) what do you mean 'bringing down the processor power in WinMo"? You shouldn't be overclocking WinMo at all, I didn't think Android would even boot otherwise.

C) Not sure why you would see FRX03 in the build number, if you believe you're running FRX02... All I can say is double-check the download, and double-check the placement of the file. The only sure-fire way I can think of to verify is if you have JIT disabled - adb shell, logcat |grep -i jit. If you see anything, you're probably running FRX02. Now there was some build.prop files floating around, be sure you're not using one of those for the test - it'll skew the results pretty severely.
[Touch Pro2, Tilt 2 Android Development] Viper Matrix Wireless:
I was speaking of underclocking & not overclocking. I wonder if somehow the processor is somewhat under WinMOs management. So what im trying to test is if I make it 300MHz in WinMO & Boot into Android am I going to see a performance boost as WinMO kicks down some additional speed.

I am using a build.prop actually from the 3D thread in the 12/19 performance 3d plus w/ new boot animation. But it doesnt make the problem worse in FRX03 nor make it better before it was released. I have been on FRX03 since its first day of release & have been going around trying to figure out how I could possibly make the performance problem go away.
[Touch Pro2, Tilt 2 Android Development] jchutch2:
I had an issue similar to this. I installed Wefi, turned the wifi on with this app and this resolved the issue.
[Touch Pro2, Tilt 2 Android Development] samizzlah:
I get this error on haret when trying to boot to Android

"[ 8.692199] waiting for root device /dev/mmcblk0p2..."

I have a Blackstone, clocked @ 710mz with FRG83 R6 build, worked flawlessly with older kernels
[Touch Pro2, Tilt 2 Android Development] F22:
compat-wireless & compcache

I've rebuilt the modules file for kernel 1245 to include the compat-wireless & compcache packages. I've also enabled 802.11e QoS support in compat-wireless. The modules files for all new kernels going forward will include support for these packages as well. I've updated the link to 1245's modules file in the first post of this thread to point to the new version.

If there is any confusion, You can tell the difference between the two by their sizes. The older version of 1245's modules file is 760 kB while the newer one is 859 kB.

One last note, I am considering the possibility of creating a test kernel that includes the "swap free notify" patch to potentially improve compcache's performance, and I'm interested in hearing back from anyone who has already looked into this possibility.
[Touch Pro2, Tilt 2 Android Development] ice.bogdan:
Is it possible for the topaz to run at 50-60 fps in 2D? It feels like it's capped at 30fps. Is this a hardware limitation?
[Touch Pro2, Tilt 2 Android Development] jab73180:
great job on the new kernals. i am able to oc to 700 and no probs so far on my rhod400.
[Touch Pro2, Tilt 2 Android Development] F22:
ACL is looking into this on the rhodium, and emwe has been working with him to apply anything discovered to topaz as well. We're not entirely certain at this point. Given the results of fps2d however, it certainly seems like there is room for further improvement.
[Touch Pro2, Tilt 2 Android Development] DmK75:
No, simple GL test on WinMo shows just enough fps (~60).
[Touch Pro2, Tilt 2 Android Development] trusa1:
I replaced the old kernel 1245 with new one, but rom still contains the old modules. It seems that we need fresh install.
[Touch Pro2, Tilt 2 Android Development] BigOnes69:
Installed

I installed some thing work faster and better. But lost a few things.

Wifi is working as a client but no longer able to use tethering for root user. It activates but unable to establish tethering. Is this expected with this kernel?

Also some programs with video seem to be operating better such as Moviephone. Trailers that were not playing are now. But have lost some flash content that was working before in browser.

3g speeds seem improved. Is this my imagination?

Battery life is improved.

AAArghs trick with booting Harret while in a phone call to use 3.5 jack is not working. Is there another way to do this?

Thanks for all the work, hope my input helps.
[Touch Pro2, Tilt 2 Android Development] F22:
Forcing a new modules file to install over an old one

By "rom", do you mean that the new modules file doesn't get installed in XDAndroid if you've already installed a different modules file with the same kernel version previously? Then yes, that's true unfortunately. The way to get around that is by typing the following at the command prompt in the terminal emulator:

su

rm /data/modules/wlan.ko

Then if you reboot, it should install the new modules file.
[Touch Pro2, Tilt 2 Android Development] pdawg17:
On my Rhod400 (Sprint TP2) I get "error" on Wifi with the Dec 26th update...I've never had this problem before...is it ok to use the "old" one or am I missing out on something?
[Touch Pro2, Tilt 2 Android Development] F22:
It's fine to use the old one. The new modules file just has some additional modules which aren't used by most builds.
[Touch Pro2, Tilt 2 Android Development] trusa1:
Yes, I've already installed a different modules file under with the same kernel version and the new modules file doesn't get installed.

Thank you for the tip.

This new kernel/modules are faster than the previous one. Gallery 3D loads photos faster. Astro File Manager loads faster directories/files. BRAVO, very nice progress.
[Touch Pro2, Tilt 2 Android Development] tariche:
I use FRX03 with latest modules on my Topaz. Once I boot in android I set time, but after two days of use it gets half an hour late. Is this a known bug or I am missing something?

Thnx for a beautiful work.
[Touch Pro2, Tilt 2 Android Development] manekineko:
Known issue, use clocksync from the market for now to keep your clock in sync automatically.
[Touch Pro2, Tilt 2 Android Development] bauner:
I had this problem on my blackstone nearly every startup.

it can only be random, but after disabling pin code usage it occured only 1 time in over 30 startups.
[Touch Pro2, Tilt 2 Android Development] randomblame:
I'm having a strange issue with my tilt2, I just did a clean install of frx03 with the december 23rd kernel and modules and I have working wifi but no phone radio. It can't seem to read my baseband version or read my sim card either. I've tried using the older modules file and now I'm reverting to an older kernel to see if that works
[Touch Pro2, Tilt 2 Android Development] randomblame:
just tried 1242 kernel same results grr never had any problems when I compiled myself and just used haret - there must be bugs introduced by the project android loader or something.
[Touch Pro2, Tilt 2 Android Development] MassStash:
yes i'm pretty sure that thing is janky... use straight haret after refixing startup and stuff
[Touch Pro2, Tilt 2 Android Development] AkumaX:
quick q - where do i put the ts-calibration file? in andboot or root?
[Touch Pro2, Tilt 2 Android Development] R^7Z:
root if you aren't using rel_path=andboot in the startup.txt where andboot is a folder under root.

If you are using the startup option, put it under the andboot folder; which should be under root.
[Touch Pro2, Tilt 2 Android Development] szoto:
I'm using Cm6minimumSystem with Topaz.

With 1238 kernel now the speaker is working (this was the first kernel which working!), but the battery drain is 8-10%/hour.

I tried the 1239,1242 and 1245 but the speaker work only with the 1238 kernel. :(
[Touch Pro2, Tilt 2 Android Development] F22:
start-up utility problems

I don't use the start-up utility either. I boot directly from haret too.
[Touch Pro2, Tilt 2 Android Development] F22:
Mic in Speakerphone & Battery Life

Mic in speakerphone should work for all kernels since 1238. It wasn't removed in 1239. I'm not sure what to tell you other than that there haven't been any other complaints regarding this.

The increased battery drain issue is believed to have been inadvertently introduced in 1233. The new clocks in 1245 should hopefully improve battery life, and if you over-clock, so should 1241's fix to pm.sleep_mode that allows you to send the phone into a deeper sleep without fear of it not waking up. WisTilt2's latest test kernel in [TESTING] New Kernel (Speakerphone/autobl) hopefully stomps the battery draining bug introduced in 1233 while adjusting the mic speaker's volume level to make it easier to hear on the other end.
[Touch Pro2, Tilt 2 Android Development] szoto:
Thanks!

The battery drain with 1245 is 4%/hour.

I'm using pm.sleep_mode=1, no overclock.

I don't know why, but 1238 is the working kernel only. (maybe Neopeek build..)

With Camro V21 kernel (now testing):

- battery drain 0.6%/hour

- speaker working, but mic doesn't until pressing the volume button

:confused:

I will test Xda build soon..
[Touch Pro2, Tilt 2 Android Development] Christiaan91:
my 2gb sd car doesn't mount in the 1245 kernel(with 26 dec update).

my phone is a rhod100
[Touch Pro2, Tilt 2 Android Development] [ACL]:
According to the documentation we can reach such fps. But we have not been able to yet. Still working on it tho.

This is the same limitation as the Evo which was lifted a while back.
[Touch Pro2, Tilt 2 Android Development] [ACL]:
After discussing this with some of the fellas. I'm wondering why we are still doing this calib outside of android.

Is there a third party app we can run to create this file? or is this something we should include in android itself ? suggestions ? ideas ? anything ?
[Touch Pro2, Tilt 2 Android Development] majkeljj:
I have also 2GB sd card and with 1245 new and old during boot I have: "Waiting for SD Card" loop or "unable to mount sd card" loop:( android don't start:( i have no such a problem with 1242. RAPH100 FRX03
[Touch Pro2, Tilt 2 Android Development] xUmaRix:
make sure u add this in your startup.txt msmsdcc_1bit msmsdcc_fmax=14000000
[Touch Pro2, Tilt 2 Android Development] R^7Z:
Probably just create a good/optional ts-calib file for each device (supported) and have the user (or person who is having difficulty starting the initial setup) drop it to the root, like the startup.txt or is this too "simple" of a method/work-around :confused:
[Touch Pro2, Tilt 2 Android Development] majkeljj:
great! now it works :) THX!
[Touch Pro2, Tilt 2 Android Development] perern:
you saying that 1238 works with neopeek?

been getting freezes since gemsom quited
[Touch Pro2, Tilt 2 Android Development] [ACL]:
Well we need a long term solution. How do the older android devices deal with this ? any ideas?
[Touch Pro2, Tilt 2 Android Development] szoto:
Yes, but there is a noise in the speaker.

I'm just tested XDA FRX03 with 1245 kernel,: not worked :(

no speaker, and after end of a call it was restarted.
[Touch Pro2, Tilt 2 Android Development] Thegn:
Apparently the HTC G2 has an app for screen calibration. But I guess it's closed code, so it won't to us any good. I own a HTC Blackstone, and right now the initial screen calibration is worthless, because it only shows for fractions of a second, and then the squares are overwritten by all the booting text. This used to work a couple of months ago, but not with the later kernels/android ROM:s. So right now I keep a previously made calibration file, and copy it to root before testing a new ROM.

The beautiful way would be to run a graphical app directly after the loading screen is done and before Android starts when it asks for languange/press the Android icon. Also this app would stay on the phone, so you could re-calibrate it later whenever you want (for instance, if you slipped somewhat during initial calibration).

An easy solution would be that the ROM builders delivers with their ROM:s pre-made calibration files with their distributions, and the users copy their respective calibration file from a folder (just like we do with startup.txt), to their root folder. This can also be made somewhat prettier by scripting, for instance, if we can incorporate into Haret and startup.txt, linking to the correct calibration file. As an example, a Blackstone startup.txt: "... set calibration "root/calibrations/Blackstone/ts-calibration" ..."

Cheers,
[Touch Pro2, Tilt 2 Android Development] R^7Z:
Here's an APK that was included with Eclair a while back. Took me a minute to rummage the contents of my older HDD :p :rolleyes:

I find that it doesn't work with FRX03.

NOTE: Save/rename with extension .apk
[Touch Pro2, Tilt 2 Android Development] gengt:
I'm a bit confused on what is working and not working with BT. I've made some test with the last kernels and i can send and receive files with other devices, i can pair the BT with the basic hands free on my car (it only support voice gateway and hands free, no agenda, etc), but when i call no voice is working, is this correct, or voice over BT is not supported yet?
[Touch Pro2, Tilt 2 Android Development] GroteBozewolf:
I had the same experience with BT Voice.
[Touch Pro2, Tilt 2 Android Development] pdawg17:
Over the last several kernels I have started having freezing and SOD problems on my Sprint TP2 (rhod400)...I went back and tried each kernel and it seems the problems start at 1239 and continue through the current 1245...

It's strange because there doesn't seem to be much difference between 1238 and 1239...and the change seems to do with the speakerphone yet the freezing and SOD occur when not using it...I have even tried the test kernels (which I think are based on 1239?) and I have the same problems...

I am not overclocking and I have reformatted my card 3 times just in case...I have also made sure not to install any extra programs with my tests so these problems happen when using the "stock" Android...

Anyone else having SOD/freezing problems on rhodium (or more specifically rhod400)?
[Touch Pro2, Tilt 2 Android Development] vnes1984:
I'm OC'd to 700, sleep mode 1, FRX03, on rhod 400 with 1245 kernal and I have had no SOD issues at all for a couple days now. Maybe you need to OC? not sure :)
[Touch Pro2, Tilt 2 Android Development] randomblame:
anyone know if ramconsole is enabled in the 1245 kernel and what the address is? I'm having a few issues - the module isn't loading for some reason and I just discovered that project android wrote a 716mhz oc to my startup txt without permission - the reason I've been having so many issues lately I believe.
[Touch Pro2, Tilt 2 Android Development] F22:
New Experimental Camera Kernel - Testers Needed

This thread is dedicated to kernels built from the official repository tree on Gitorious. Nevertheless, kernel developers will at times make experimental kernels available for testing that contain modifications which are not yet ready to be committed to the main tree.

I'm currently aware of two such test kernels. The first is WisTilt2's new kernel which includes speakerphone mic improvements, an autobl rewrite, and battery drain reduction improvements. This test kernel is currently for rhodiums only.

The second is VirusCrazy's experimental camera kernel which while initially developed for diamond, is now being extended to other xdandroid supported devices such as the rhodium, raphael & blackstone. Not having anything other than a diamond himself, he is currently looking for testers for these devices, and anyone wishing to help get the camera working on their device by being a tester is encouraged to go to the Camera Tests thread in the raphael subforum, try out the new kernel, and provide feedback so that he'll know what works and what still needs to be adjusted. The sooner he (with assistance from bzo, Alex[sp3dev] & WisTilt2) can get camera working, the sooner we'll have working camera in the main repo tree whose builds I've been posting here.
[Touch Pro2, Tilt 2 Android Development] LENINred:
This is coool!)) but what about TOPAZ??
[Touch Pro2, Tilt 2 Android Development] R^7Z:
I don't see why you couldn't test it out and report? Don't know for a fact that it doesn't work (I don't think). Just copy the contents of your microSD and archive it, if you are worried about ruining a good data.img.
[Touch Pro2, Tilt 2 Android Development] pdawg17:
I've tried the camera test and only get a blank screen when starting camera...I have posted my results there...

Only question is that Viruscrazy talks about using ADB shell to install the files...how do I do that? Instead I used the conf file to bind the files (like we do with the 3d files)...what are the steps to use ADB shell?
[Touch Pro2, Tilt 2 Android Development] R^7Z:
This isn't the best place to discuss this, probably best to either ask in his thread or PM him. I think he is open to replying back with how to do it either case.
[Touch Pro2, Tilt 2 Android Development] [ACL]:
We need a long term solution for this. I'm on nand and eventually we will start moving away from the crazy console window and into the bootlogo straight to android. So it would be good to do it the way other devices do it.

Hero and the g1 should have such calib apps right? i wonder how cyanogen does it. Time to research i suppose.
[Touch Pro2, Tilt 2 Android Development] [ACL]:
Do you happen to know where this came from?
[Touch Pro2, Tilt 2 Android Development] R^7Z:
I'll have to do some tinkering around but I think it was from one of the earlier threads for Eclair. It was in a zip that was called eclair addons or something like that.

EDIT: Maybe it was the SenseUI from Klinuxs' thread?
[Touch Pro2, Tilt 2 Android Development] pdawg17:
With 1245 when my phone is asleep I have a blinking green light and when I wake it up the light becomes solid and it sometimes takes 3-5 seconds for the screen to light up...other times it responds immediately...

Is this what you guys see? I'm trying to troubleshoot my SOD problems...kernels like 1238, 1239 do not exhibit this behavior...

Rhod400 with no o/c
[Touch Pro2, Tilt 2 Android Development] MassStash:
This ones from tattoo rom dump
[Touch Pro2, Tilt 2 Android Development] [ACL]:
does this work on frx03?

if so i say we use it. Need to remove that damn tscalib during boot.