yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] Alcoholic:
doesnt work. shuts down as soon as i open haret. and the reason i had the startup the way i did was because i used to use the v1.3.1 startup utility and the startup is manually created in that. i only overclocked at 600 Mhz. and i also tried no overclock no hardware 3d.

the old kernel still works. so i doubt its the startup file.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Odd indeed. 10/23 kernel is the last functional kernel?
[Touch Pro2, Tilt 2 Android Development] Alcoholic:
yes that is correct..
[Touch Pro2, Tilt 2 Android Development] jphaus:
Yes, I most definitely get this error on my RHOD400. It seems like a small minority of us though based on the replies I have seen. This error I believe is keeping me from downloading/updating apps from the Market and also keeping Google maps from updating my Latitude (GPS works fine, but doesn't save to Latitude).
[Touch Pro2, Tilt 2 Android Development] Alcoholic:
maybe reef can give an official update so i'm not losing my mind trying everything i can think of to boot from the latest kernel :(
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Assuming you're installing these updates correctly, it would be no different than what reef does with the reference builds. Even on blazn, the only thing that's customized is the startup.txt and the system.ext2.
[Touch Pro2, Tilt 2 Android Development] Alcoholic:
thats what i get for typing that message while listening to the HR lady talk about the company hehe.

by update i meant maybe he can give an official yes on if this has been a kernel issue or not so we (rhod100 users) can continue to try to do everything to get it working.

for now ill continue to mess with the files to see if i can get it to work. ive already deleted data , roof and zimage and re downloaded them. ill see if i can create another startup.txt now.

if that doesnt work ill try reformat and clean install.
[Touch Pro2, Tilt 2 Android Development] Bieka:
Just to inform, the first 10/23 Kernel is working well. The second 10/23 and all subsequent kernel till now are the kernels which freezes the TP2.
[Touch Pro2, Tilt 2 Android Development] TragicPhill:
There are two things keeping this android from being usable day-to-day.

1. LauncherPro. Seriously. It constantly shuts itself down, and it keeps asking me for money? come on.

2. Just today, I was trying to make it through the whole day using android, but after having it going for roughly 9 hours, I lost my reception. It couldn't pick up a signal whatsoever, yet back in winmo everything is dandy, so I know it wasnt the actual phone/reception.

If anything can be done (mainly the first thing listed here), it would complete this project very nicely in my eyes.
[Touch Pro2, Tilt 2 Android Development] Bieka:
The Easy Way?

Get the XDAndroid Reference Version and install the home app of your choice. I am using the ADW Launcher. But you can just leave it as it comes so no launcher pro in there ;). There are ways to " uninstall" launcher pro on blazn build but the easiest way is the described one ;).
[Touch Pro2, Tilt 2 Android Development] TragicPhill:
I saw LauncherPro on the list of "uninstallable" applications and trust me, I was tempted. However I would need to replace it with something. How could I get a replacement launcher, perhaps this wondrous ADW you speak of, without sacrificing the BLAZN?
[Touch Pro2, Tilt 2 Android Development] snalbansed:
Launcher Pro crashes for me too, occassionally. Nothing to get too upset about. And it only suggests you upgrade to the paid version if you trigger the icon resize function, which happens to me very, very occassionally.

9 hours without losing reception? That's quite good! So reboot, and all will be well again.

So no, this build isn't ready to give to your Mum to use. But lots of us have been using it 24/7 (subject to crashing etc!) for months now - it just depends on your tolerance to IT issues and whether a phone is simply a tool that you use to get a job done, or whether the tool is the interest!
[Touch Pro2, Tilt 2 Android Development] michellxp:
Hi guys! Dear members, Please help. My TouchPro2 (Rhodium100) works flawlessly with WM6.5. But more like Android). Unfortunately, in the Android phone is not working, no incoming calls, although the LED turns from green to orange. Tried to install different versions of Android and Radio. But the result is triggered if Phone.apk, it then freezes and have to restart the Android or not working.
[Touch Pro2, Tilt 2 Android Development] Naadi900:
Not sure if i get your full message, but here's a few tips.

At first make sure you read and understand the FAQ (link on first page).

If that doesn't bring a solution, re-install. Just download newest reference, format your sd-card (with HP-tool, linked by arrrghhh a couple of pages back), extract rar file on sdcard, update with the newest kernel and rootfs, make sure your startup.txt is in order and boot.

Most likely it will not boot because you have a Rhod100, if that's the case revert back to the first 10/23 kernel and don't update for a while until it's fixed.

Have fun with Android! But keep in mind that there will be crashes, bugs, losses of signal etc. once in a while. Do not use it in very important circumstances!
[Touch Pro2, Tilt 2 Android Development] michellxp:
Many thanks Naadi900! Is there something I missed when installing and configuring the phone and Android. Once again, read the FAQ and followed your advice. But I want to add the last version of a malfunctioning but worked
[Touch Pro2, Tilt 2 Android Development] J-Hop2o6:
thats weird.. Launcher Pro works for me perfectly.. the only time it asks me to pay (for Plus) is when i (accidentally) try to re-size the widget, or add a Launcher Pro Plus widget.. other than that, i LOVE LP! it'll only crash is if Android is loading like craaaazy (aka overload for our slower processor).
[Touch Pro2, Tilt 2 Android Development] snalbansed:
Are you overclocking? If so, try removing the overclock for a while and see if it becomes more stable.
[Touch Pro2, Tilt 2 Android Development] kaybegod:
Very nicely put. You hit the head right on the nail.:cool: I think that is what some people seem to forget, this is still in DEVELOPMENT hence the forum name xdaDEVELOPERS. There is nothing wrong with posting problems one might be having but its another when people post things complaining and whining about whats wrong with this project. Development takes time and like you said if you don't have patience or tolerance for IT issues, don't bother installing this on your phone.
[Touch Pro2, Tilt 2 Android Development] TragicPhill:
I wasn't complaining or whining (as stated earlier). I'm still using the build, experimenting and such. Isn't it important for a developer to know when a user is having significant issues with specific areas of a development? Perhaps they'll understand from my posts that right now, there are only very specific issues for the build on a tilt 2, which would not only be a compliment to the work thus far, but let them know the small scope of the work left to be done as well. I tolerate the issues just fine, but it's my belief that the ultimate goal of any project is to make it 100% usable 24/7, which is impossible without knowing issues and their severity as they differ among users and devices.
[Touch Pro2, Tilt 2 Android Development] Captain_Throwback:
Low Volume Issue on RHOD300

I'm currently running the latest kernel (11/11) & latest rootfs (11/8) on my Tilt 2, along with the FRX02 build.

I noticed that one of the recent kernels finally got the microphone working on our RHOD's without having to do the dial-in-to-VM-in-WM trick, however this weekend I attempted to use Google Navigation, and realized that the volume is barely audible, even when maxxed out. Then, I decided to boot back into WM & do the VM trick, to see if it would make a difference, and it made a HUGE difference. Has anyone else noticed that the ring/media/navigation volume is very low on the device, using the latest kernel?

It's good to see progress is being made on the microphone issue, but it seems like there's still something missing to get the volume where it should be.
[Touch Pro2, Tilt 2 Android Development] kaybegod:
I wasn't referring to you at all, your post was fine. I was referring to someone who posted something this weeking saying that they was going back to windows mobile because they was mad that their phone kept rebooting.
[Touch Pro2, Tilt 2 Android Development] vnes1984:
I have a Rhod400 and I noticed that too. After you use the mic, the media/ringtone speaker volume is noticeable lower than before. Also, after using the mic my LED turns off on the front and switches to the back mic LED for about an hour or so, then turns off and works as normal.
[Touch Pro2, Tilt 2 Android Development] F22:
Mic/Speakerphone sound, including volume levels, is actively being worked on currently.
[Touch Pro2, Tilt 2 Android Development] kaybegod:
I did notice this as well and I think the simple explanation for this is because the windows voicemail trick enables you to use the speakerphone as a mic and speaker where as the mic fix enables you to use the regular mic and earpiece therefore its not as loud.
[Touch Pro2, Tilt 2 Android Development] hmida:
the package take more than one hour rebooting in my sprint htc pro 2 !

What I'm doing Wrong, Please HELP!!
[Touch Pro2, Tilt 2 Android Development] kaybegod:
What package?
[Touch Pro2, Tilt 2 Android Development] xcuter:
cant establish a reliable data connection to the server

I'm getting this message when i try to connect to my goggle account. My phone has working fine till this weekend when i was running multiple apps at once. The phone crashed and when i restarted it every app would crash. Today i download the latest patches and when i try to connect to my Google account i get this message. I'm able to browse the net so i know my data connection is working. Anyone else have this issue?
[Touch Pro2, Tilt 2 Android Development] jataxda:
hey guys,

first i have to say i preciate all the work developers and others ve done for this project.

i have a rhod100de and first i had isntalled blazn.

a few days ago i turned to the latest reference version which is more satisfying for me. battery status works fine i think, wifi works (but not if using gen y...), no sleep of death...

but now i wanted to update the kernel in hope google navigation will work.(i think its a gps problem, because its saying always "google blabla is not supported in this location yet" and google maps says i´m in the gulf of guinea but i´m actually in germany)

so i downloaded kernel

htc-msm-linux @ 20101111_213418 and

rootfs-20101108-c11971c.zip,

unzipped, put everything in "andboot", renamed the zImage.... to "zImage" and the rootfs..... to "rootfs" (overwritten the old, but made backup)so i don´t have to change the startup.txt!!?

now, trying to boot from the startup utility, phone virbrates shortly and freezes (no boot screen) and has to be reset.

what do i make wrong? any tips how to get gps/google navigation working?
[Touch Pro2, Tilt 2 Android Development] F22:
Rename "rootfs" to "rootfs.img".
[Touch Pro2, Tilt 2 Android Development] jataxda:
so it should be rootfs.img.img ? ;>
[Touch Pro2, Tilt 2 Android Development] F22:
Didn't realize you were hiding file extensions. That's always the first thing i turn off in Windows on those occasions when I'm on a Windows computer. :p It sounds like the new kernel is unable to bring the panel up. Try going back to your old kernel while keeping the new rootfs. If that works, then at least we've ruled out the rootfs.
[Touch Pro2, Tilt 2 Android Development] jataxda:
yieah...i´ve a fresh windows vm ... on macos ;)

so i turned back to old kernel and rootfs of latest reference build...till someone tells me how to make it right.

other issues:

1) sometimes i´m forced to enter pin - disconnected from gsm

2) around an hour after booting the led doesn´t turn to green light, only orange

3) gps isn´t working, do someone experienced something else on the reference build? do i need a newer kernel+rootfs?

hope someone can help me with these issues.

edit: ok i´ll try...read your post too late...
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
GPS is sometimes slow to lock. Make sure you have your PIN code auth turned off in WinMo. LED should indicate sleep/wake status, but if you have GPS enabled the phone will not sleep. Known issue.

With that said, you should be able to update to the newest without an issue. Rootfs should be 'rootfs.img' and zImage should be just that - 'zImage' without a file extension. modules need not be renamed, but you should delete out any old files when you update.
[Touch Pro2, Tilt 2 Android Development] pgdrz4:
hmm not good

when this is downloaded regular winmo freezes and i get exe error reports. i uninstalled.
[Touch Pro2, Tilt 2 Android Development] bonestock:
I'm having the same issue, anyone get flash to work?
[Touch Pro2, Tilt 2 Android Development] mwf:
rootfs updated

rootfs has been updated - anyone know if it has changed anything for us?

http://files.xdandroid.com/rootfs/
[Touch Pro2, Tilt 2 Android Development] snalbansed:
Crash on latest kernel: You have a rhod100, and most of them will crash as you described on any kernel after the auto_bl changes were made. Therefore, try updating to the first kernel of 23rd October (I think). The second one and beyond won't work, and it isn't clear yet why :( Rootfs should be fine, though the last one didn't work very well for me, but aparently there is a new one today.

GPS Navigation: You will only be able to use navigation when the GPS confirms you are somewhere Google can plot a route in. When you first turn GPS on, it puts you at 0,0 until it can find a lock. This can take a long time the first time you try, though when you get a lock it is quick on subsequent attempts until you next reboot. Start google maps, select to Go to my position, and give it a while - for me normally about 30s with a clear view of the sky, but for some it is 20 minutes! Eventually, it will find you, and then you can navigate :)
[Touch Pro2, Tilt 2 Android Development] Alcoholic:
As others have said android is not working on rhod100 with the latest kernel. either go back to oct 23rd or wait for fix :o
[Touch Pro2, Tilt 2 Android Development] jataxda:
thanks for the answers.

i checked out the gps function today again with reference build and its brought with kernel... works well after around 30sec.

okay. so let´s wait for a new kernel which will work, hopefully!
[Touch Pro2, Tilt 2 Android Development] Colombia81er:
Having the same issue with calls and speaker going off in the middle of the call. Hope this will be fixed :)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Hrm. Perhaps we didn't test autobl on the RHOD100... Not enough of you guys hang out in IRC evidently, no body to blame but yourselves :p

Seriously tho, it seems like we may need a RHOD100 tester to help with ensuring what is pushed out doen't break things. We rigorously tested on every other RHOD before releasing, and I thought we tested a little on the RHOD100, but like I said there isn't anyone with one that hangs out on IRC...
[Touch Pro2, Tilt 2 Android Development] minikirchner:
Update through Android

Hey guys, I was wondering if there was a way to see if there was an update without rebooting to windows. It takes so long to boot to either one, it's kind of annoying for me. I don't mind if there isn't because I love Android that much. Just curious if this has been brought up yet. Thanks for everything you guys are doing!!
[Touch Pro2, Tilt 2 Android Development] the show stopper:
i tried to install flash 10 on android got an error mssg. does anybody have flash working on android ?
[Touch Pro2, Tilt 2 Android Development] kwoodyusa:
For anyone having problems with ring tones not loading afer android install. The panasonic formater works perfect for me.
[Touch Pro2, Tilt 2 Android Development] uub11:
Can anyone using the blazin version do me a favor, i'm trying to see if blazin has 2 specific lib files and i need someone to use root explorer to tell me if they see the following

/system/lib/libRS.so

/system/lib/librs_jni.so

thanks in advance!!

*Edit Ok found out the reference build was missing certain files for me to get livewallpapers running I found the above libs and added them and now live wallpapers is working thank you all.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Our hardware is limited, I don't think it'll work very well. With that said, see this thread. Sorry to link to another forum, it was just the best post/thread I could find on the matter.
[Touch Pro2, Tilt 2 Android Development] kaybegod:
I have a Rhod400 and the same thing happened to me
[Touch Pro2, Tilt 2 Android Development] snalbansed:
Go to the faq (link in first post), click on Project Tracking, then follow the links to the kernel, rootfs and init. Bookmark each page, and check them every now and again!

Personally I prefer the git repository pages rather than the download page, as you can see the actual commits, the comments and the changed files. Links to the rootfs git page are at the top of the rootfs autobuild download page, and the kernel equivalent is linked to again in the rootfs autobuild download page.
[Touch Pro2, Tilt 2 Android Development] godersandor:
volume?! wow :p

i dont know if anyone observed that since we have sound ,thanks god .....and by god i mean the developers :p the rhodium is like a boombox :) my touch pro2 was never so loud ,can this affect my speakers by blowing them or something, to be precise i speak about music not conversations with the loudspeakers;
[Touch Pro2, Tilt 2 Android Development] aberry:
rhodium400 call issue

Specifically what just happened to me on a Rhod400 is when I'm on a call and someone calls me and the call waiting beep starts going off, it then turns on the speaker on the back of the phone and the call waiting beep goes off in my ear until I end the call. I'm on 11/3 kernel and 11/3 rootfs. Just an update. I know that nand and camera take precedence. Thanks for everything, Devs!
[Touch Pro2, Tilt 2 Android Development] Raul^:
I'm not sure if FAQ about overclocking is correct.

"

Overclock capabilities - acpuclock.oc_freq_khz=XXXXXX - Replace X's with frequency in Khz not Mhz.

You have to enter speeds in Khz though so

540672 = 528Mhz Stock speed

716800 = 700Mhz

786432 = 768Mhz Reported to be stable "

That would mean that Mhz is 1024 Khz and not 1000 Khz as it should be.
[Touch Pro2, Tilt 2 Android Development] Captain_Throwback:
Those specific numbers aren't right, though - the steps are 19200Khz. To get stock speed, you just leave the parameter out. The next higher overclock speed is 537600, and the increases are in 19200 steps.

So for 700Mhz, it would be 691200 or 710400, and "768Mhz" is literally 768000. I had my original Tilt 2 overclocked as high as 825600 at one point (but that was a bit unstable) - I was using 806400 with relative success.
[Touch Pro2, Tilt 2 Android Development] herhangibi:
hello,i am looking the last version of android rom for my touch pro2.from this link i cant download it because the web site which the link inside is ban here.

could u help me for finding the lastest version of android rom for my tilt2

thanks
[Touch Pro2, Tilt 2 Android Development] Raul^:
Thanks, I was comparing those values with OCT oveclock for windows and that's why I asked. I'm using 710400 and it's quite stable (some problems with "reset to no service" from time to time).
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Download link works just fine... you can't go to sites.google.com?!? Or is the .info site that mirrors the download...?
[Touch Pro2, Tilt 2 Android Development] kaybegod:
I'm running the Blazn build on my Rhod400 and I'm running the 11/8 builds and this happened. In my case there was no other incoming call, it just randomly went to speaker in the middle of my call.
[Touch Pro2, Tilt 2 Android Development] the show stopper:
ahh thanx i will give it a try 2marrow :D
[Touch Pro2, Tilt 2 Android Development] Bieka:
Hey,

i just saw that there is a new rootfs. I edited my rootfs to fix the german keyboard. So i just want to ask what this new rootfs does.

In changelog there is a comment that says:

Add correct lights.msm7k.so as referenced in c11971c

Which lights are meant there. Is it worth it to edit the new one and copy it over? ;)

Thanks a lot. Oh and just to ask another question... Are there any new informations about the freezing problem with the rhod 100?

Regards

Bieka
[Touch Pro2, Tilt 2 Android Development] michellxp:
Hi! Unfortunately the new root system is not working on Rodium100. No incoming calls. Slows down and freezes. Crashes in the WM. We are waiting with great hope the corrected version/
[Touch Pro2, Tilt 2 Android Development] Bieka:
Hi,

Newer rootfs versions are always working to me. Tested this one without editing the keyboard layout and it seems to work pretty fine. Only thing i know is that the kernels newer than 10/23 arent working. For this i hope for a corrected version. Also hopefully with enabled bluetooth. I read about someone who posted that in irc. There is also a thread @ppcgeeks with this topic.

So i tested the new rootfs and it works on rhodium 100 de but i switched back now till i have edited the keyboard layout. But what is meant with the light correction. Is it just the backlight (auto bl) which works from 10/23 2nd on or is it another light... evetually keyboard bl? ;)
[Touch Pro2, Tilt 2 Android Development] charburble:
Does anybody know if there will be a new update to the Blazin version? That one seemed to work a lot better and faster for me on my phone. ( The T-Mobile Rhodium).
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Not since 9/28.... As it says on the download page.
[Touch Pro2, Tilt 2 Android Development] kaybegod:
I think the question was more targeted towards the developers basically asking has the Blazin build been forgotten about since there haven't been an update since 9/28?
[Touch Pro2, Tilt 2 Android Development] tuna629:
Just update to the new rootfs last night, everything seems great (not sure about calls though, didn't make/receive any calls, I had the same problem as the guy above of not receiving calls in the last rootfs) except for one thing : the backlight behind the call/windows/back/hangup keys are always on. This has never happened to me before. Any quick solution/fix for this? Thanks.

Rodium210
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
It's just a system image... but Reef builds those by himself. So it's not like there's a team working on BLAZN. I'm still trying to get the necessary stuff from Reef to help him keep up with the updates, but I haven't seen him much lately.

You had them turned on when you booted Android from WinMo. If those are on when you boot Android, they'll be stuck on until they're fixed. Same with kbd backlight.
[Touch Pro2, Tilt 2 Android Development] TragicPhill:
Hey everyone. I'm switching to the reference build as that seems to be where this project is heading (and I have heard less stability complaints :D). While it's downloading, I was wondering if anyone was having problems with INCOMING calls on the reference build? I was using the blazn and outgoing calls worked fine, but when I answered incoming calls there was just zero noise on the line. Is this not an issue for the stock build? Or is this something we're all still dealing with?

...Or is it just me....:(
[Touch Pro2, Tilt 2 Android Development] dswaggz:
Hey kno this soundz retarded but can we get some nand love & a working camera
[Touch Pro2, Tilt 2 Android Development] plug_it_in:
Android Update Issue on Rhodium

In the last two releases Ive tried to download on my phone the download completes, but the unzip fails with :

An unexpected error has occured in XDAAndroidSraertup.exe . Bad state (oversubscribed dynamic bit lengths tree)

Current version 2010_11_08

Installed version 2010_10_30

I installed full download last time and started over. I dont want to do this again.
[Touch Pro2, Tilt 2 Android Development] pitflyer:
When I had that error I just deleted the temp directory in xdandroidsetup and updated again. Worked fine.