yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] dswaggz:
@Neopeek any good news
[Touch Pro2, Tilt 2 Android Development] Jandyman:
I'm sure neopeek will let us know when there are any serious developments. Asking won't make the project go any faster ;)
[Touch Pro2, Tilt 2 Android Development] dswaggz:
Ok every1 on tmo or at&t simple mobile is the way 2 go no contract or credit checc f that early term fee simple mobile 60$ a month unlimited everything
[Touch Pro2, Tilt 2 Android Development] mcnutty:
Just wanted to check in with you guys since I really do neglect XDA on this. The development is all being done over at PPC Geeks, and I often forget to come over here and give a status update.

I really want to apologize that GSM is still not fixed up. Unfortunately, it is a kernel issue that I don't have the expertise to fix, and ACL doesn't have a GSM device to work with. Stinebd has one and has been looking into it, and I know you have heard neopeek is now porting CM7 and possibly working on other things. I truly hope neopeek has a breakthrough, but I'm not sure if the kernel level stuff is something he's used to working with. I guess we'll see if he is able to come up with anything :)

The good news is, we are getting very close to releasing FRX05 Release Candidate for NAND. Keep in mind, the kernel is what is preventing booting for GSM users, and the FRX05 is the system (Android). There were a few things that had to be changed in FRX05 to work properly on NAND like moving modules and ppp out to the /data partition.

Also, a note on those asking about battery life. Unfortunately, NAND is going to consume a lot more battery for now because we don't have power management for NAND right now. Running off NAND certainly feels faster and more fluid than it did of SD card for me, but we are behind on commits and battery life. ACL is working overtime on all of this, so please be sure to show him your appreciation ;)
[Touch Pro2, Tilt 2 Android Development] dswaggz:
Hey was just ppcgeeks seeing if there was any gsm nand progress an seen the rhodium 100 was the last device then why is there no test nbh for us do we not have a right 2 some lovin
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Either you help, or not. Begging for "some lovin" isn't going to make any progress happen on GSM.

Neopeek is probably your best hope at this stage, as he has a GSM device (RHOD300) and is working on getting tinboot up and running.

That doesn't mean to go harass Neopeek and bug him for a release date. It'll be ready when it's ready, when something is ready to test for GSM you will know about it.
[Touch Pro2, Tilt 2 Android Development] buffalosolja42:
I have a TP2 with ATT I can loan (as long as I can get it back) I would like to help support this project and I am not using the phone since I am waiting on the NAND port because I enjoy my WP7 and would like to use this device just for tether gps on my nook color. Would one of the developers like to pm me I can send it to them, as long as it is returned when they are done building. Thats not to harsh right?
[Touch Pro2, Tilt 2 Android Development] helicopter88:
I talk with neopeek a lot,and he's doing an amazing job,with nand and cyanogen mod 7.

I can tell you that if you leave neopeek work without supid questions like when or what or who,he'll have something for you earlier.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
^^ this. Let Neopeek and the rest of the devs to work on this. There will be posts when testing is ready...
[Touch Pro2, Tilt 2 Android Development] TheDeadCPU:
Any way me and my RHOD100 can help?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Fix the SMD channel issue? :p.

I'm honestly not sure where Neopeek is at on his work, but last I checked RHOD's failed on SMD channels. I hear if you pull the SIM, it works... but then of course the phone is pretty useless as a phone.
[Touch Pro2, Tilt 2 Android Development] TheDeadCPU:
Right, I'll just go get my tinfoil hat.
[Touch Pro2, Tilt 2 Android Development] helicopter88:
i just went on htc-linux irc channel,and i had a small talk with cotulla,he said that magldr is done,now their work is on gingerbread,so i think that it should be soon...

don't ask for eta
[Touch Pro2, Tilt 2 Android Development] nathanpc:
Is it fully working with the RHOD210?
[Touch Pro2, Tilt 2 Android Development] dswaggz:
Wow an yes damn but I'm Lovin this phone though
[Touch Pro2, Tilt 2 Android Development] TheDeadCPU:
On all RHOD models?
[Touch Pro2, Tilt 2 Android Development] helicopter88:
I forget to ask,lol

But i think that it should work on all models..
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Cotulla is only working on his 210... I'm not sure how much he's going to work with other models, but he seemed open to having different models test when it's ready.
[Touch Pro2, Tilt 2 Android Development] dswaggz:
After they work out the bugz I'm buying me a new tp2 maybe this mytouch 3g kinda nice though
[Touch Pro2, Tilt 2 Android Development] mcnutty:
OK, I need a GSM tester to try this out for me. You need 3 files which are linked below.

androidinstall.tgz - http://htcdevs.wirelesstcp.net/files/xdandroid/FRX5/androidinstall.tgz

androidupdate.tgz and NBH - http://dl.dropbox.com/u/11790134/gsmtest.zip

Put androidinstall.tgz and androidupdate.tgz in /sdcard/andboot, then flash the NBH.

On first boot, it will go into recovery. Use the power button to bring up the menu, volume up and down to change selection, and end key to select. Pick android install, then yes on the wipe data page, then reboot

This should let you into Android, but I'm not 100% certain if data will work. Data does not work on first boot for CDMA users, but it works after a reboot, so if someone could test that, it would be greatly appreciated!
[Touch Pro2, Tilt 2 Android Development] blitzer320:
no luck tilt2 still "smd ch 0 OPENING -> OPENED"
[Touch Pro2, Tilt 2 Android Development] nasapunk88:
same for me too =(
[Touch Pro2, Tilt 2 Android Development] Trekfan422991:
using these files and the recovery from the first post i am booting in to android on my sisters at&t tilt2 (rhod300) as we speak...

It is at a boot screen that almost looks plaid... With black and white droid characters... And one big green one in the bottom left...

Lets see what happens....

(edit)... never mind... somehow it quit... could repeat the result just says matching modules not installed
[Touch Pro2, Tilt 2 Android Development] ryannathans:
rhod110

On both these files and OP files it gets down to the line where it says push vol up or something and then restarts and goes over and over and over, restarts pretty much as soon as it hits this line. regardless of if i hold vol up or not.
[Touch Pro2, Tilt 2 Android Development] mcnutty:
Thanks for the update guys. I thought I had followed neopeek's advice properly, but I must have missed something. I'll try to get something else together for you guys tomorrow. Gonna play with this some more tonight since we have a few more commits to go.

If any of your are feeling adventurous, you guys could try to the GSM test files again, but make one minor change to the build.prop file in androidupdate.tgz. Using something like 7zip, open anroidupdate.tgz and edit build.prop by deleting the line for rild arguments where it says =-d /dev/smd0. Let it save the change to the tgz and then try flashing and installing again.
[Touch Pro2, Tilt 2 Android Development] mcnutty:
Thank you very much for the dmesg and bootlog. They both look the way that they should, so I believe the rhod100 users actually have a different problem than the rhod210/300 users. rhod210 and rhod300 seem to just be the smd0 which neopeek has a workaround for but last I heard did not have data working with the workaround.

It seems the rhod100 users must have something wrong with the SD card slot location because it is when we attempt to mount the sd card that those devices fail. I know that on the CDMA phones, we have a similar issue if we have the SIM card in. It's almost as if it sees the SIM card and thinks it is the sd card and tries to mount it (which fails miserably causing a restart). Not sure if that is exactly what is happening, but that's my best guess right now.
[Touch Pro2, Tilt 2 Android Development] BigOnes69:
Rhodium 400

I have a couple of questions before I install this.

1. We will be limited to updates that are put into a flash update package right? If so will there or is there a haret type program for this so we can test other packages?

2. Can we use our FRX05 data image with this or if we need a new one will Titanium backup restore our settings and programs in this?

3. Is there any way to use other kernels with this? Specifically Wistilts. Is there any benefit?
[Touch Pro2, Tilt 2 Android Development] Trekfan422991:
is there anyway someone could post the workaround with any required instructions... cause not having data is no issue for me... dont have a data plan...

PLEASE

PLEASE

PLEASE
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
1. Androidupdate.tgz is how we will update in the future methinks.

2. data is no longer looped - it's a partition on the NAND... so... no.

3. No. NAND kernel is heavily modified to work on... you guessed it, NAND.

Keep in mind, this is just for testing at this stage. No where near ready to run full time.
[Touch Pro2, Tilt 2 Android Development] mcnutty:
I am working on compiling the new FRX06 for NAND. I will make the modifications I mentioned and upload it as a test for GSM users. Also, I found that those who get a reboot at the Press Volume Up spot are having issues because of their SIM card. This seems to only be rhod100 users, and if they remove the SIM card (which I realize defeats the purpose right now), it should let them boot further.

For the GSM users that are stuck on opening smd0, I will have a new set of test files once I get FRX06 booting properly.

Thanks arrrghhh :)

Although this really is in testing stages, I must admit that I've been running NAND for the last couple of weeks with very, very few issues. I think both Haret and NAND are getting really close to stable enough to run full time even for the average user. Really trying to find a way to make NAND more user friendly by automating as much as possible. If you (or anyone really) has an idea for improvements, we're all ears :D
[Touch Pro2, Tilt 2 Android Development] dcmedic:
this was suppose to be a quoted reply to the post directly above this post.

I don't know about other RHOD300 users, But I've also been having this issue, not sure if arrrghhh mentioned it to you.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
You guys are doing a great job, and you are doing a fantastic job of making it easy for noobs.

Problem is in my eyes - the kernel. No offense going to ACL - he's doing wonderful work, but he's going it alone on that front. Seems PM and collapse need some lovin, and to me that's kinda essential for NAND. Plus, the battery meter seems to be more off than we think it is - I've had all sorts of reports of random people saying that it was 75% in Android -> reboot to WinMo 8%...

So yea, just some things that need to get brushed up in general methinks, mostly kernel-related. Again, not to knock on the project or its state - progress is going well. But until it stabilizes, I wouldn't run it full time - I mean updates are flyin to this thing! That's not a bad thing, just not something I'd want to flash permanently at the moment ;).

Edit - as for DcMedic's problem, his dmesg is here. Appears there's some issue once it tries to mount the partitions. Not sure tho...
[Touch Pro2, Tilt 2 Android Development] mcnutty:
Yeah, I agree ACL needs additional resources :)

As for the dmesg, it looks perfect. That yaffs mount is actually recovery being mounted, then dmesg is output to the sdcard once he boots out of recovery. So, I can tell that recovery was successfully installed from that, but unfortunately, it stops there. In my next commit, I am moving dmesg to the end of init since it really is worthless for anything after recovery.
[Touch Pro2, Tilt 2 Android Development] mcnutty:
Can you try this one out and let me know how it goes?

Put androidinstall.tgz and androidupdate.tgz in your andboot folder, then flash the NBH. It should auto-boot into recovery, press power to get menu, volume down to highlight install, then end key to select, then down key to Yes, then end key to select again, then when finished, hit end key to reboot.

I have it doing a little sed magic when it finds a GSM model (rhod300 or rhod210 only since rhod100 has a kernel issue that I can't fix with sed). Hopefully it boots in OK, but it most likely will not have data. Again, I can't test unfortunately, so I apologize if it doesn't work the way I'm expecting it to.

http://www.multiupload.com/TX8984OE5K
[Touch Pro2, Tilt 2 Android Development] toadlife:
Tried it. Reboot loop for me. Rhod 210.
[Touch Pro2, Tilt 2 Android Development] mcnutty:
Any chance you could test without the SIM card in?
[Touch Pro2, Tilt 2 Android Development] djcrosstunez:
Should I test it on rhod100?

Wich kernel problem do you mean? The SMD?
[Touch Pro2, Tilt 2 Android Development] nasapunk88:
testing the new link files on my Tilt 2 and still no luck =(

im gettin to SMD: ch 0 Opening ->Opened

ive tried with and without my sim card
[Touch Pro2, Tilt 2 Android Development] dcmedic:
Nate, the boot loop is not present while the sim card is out. I have been able to install and apply the update without a problem, as long as the sim card is out. But I'm getting caught up at the smd0 also, while using your latest test for gsm.

RHOD300
[Touch Pro2, Tilt 2 Android Development] BigOnes69:
If we NAND can we use Harret.exe from this to test other versions on the SD card?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
No. NAND takes over the phone, literally :p.

haret.exe is naturally Windows software....
[Touch Pro2, Tilt 2 Android Development] toadlife:
Yup. Just tried it myself without the SIM card. Stuck at SMD: ch o Opening.....
[Touch Pro2, Tilt 2 Android Development] the_mouse:
Same here tried without out SIM stopped at same point

TP2 100_uk
[Touch Pro2, Tilt 2 Android Development] muziling:
sorry for wrong post
[Touch Pro2, Tilt 2 Android Development] mcnutty:
Thanks all of you who tested that out. I really appreciate it. We are working on FRX06 and moving modules and ppp back into the system partion. I'll try to ask Neopeek what other changes he had to make to get his GSM rhod booting properly.
[Touch Pro2, Tilt 2 Android Development] nasapunk88:
can't wait to try out more!! ty for doing all this =)
[Touch Pro2, Tilt 2 Android Development] Germypan:
Hi guys, i have a rhod100_it and i would try the android nand. but i don't understand a little parts of this tutorial, if i wanted to return to winmo, i must flash the stock rom or i must to do another things?

Sorry for my bad english!

Germy
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Not quite ready for GSM. You can try it, but it'll probably fail... please wait until we sort out the problems ;).
[Touch Pro2, Tilt 2 Android Development] Germypan:
Thanks for the answer, but for the future, if i wanted to return to winmo, i must flash the stock rom or i must to do another things?

Sorry my bad anglish!

Germy
[Touch Pro2, Tilt 2 Android Development] toadlife:
Yes. Aafter trying this, to return to WinMo you will need to flash a WinMo ROM.
[Touch Pro2, Tilt 2 Android Development] Germypan:
Hi Guys, i tried to flash android on nand, but after the splash screen, i pressed for a lot of time the volume up but it don't work and the rhod have loop boot ever! I wait the android gsm nand! Thanks for all information. you're fantastic! thanks.

Sorry for my bad english

Germy
[Touch Pro2, Tilt 2 Android Development] ryannathans:
Yeah I had this too. I believe a fix is in the works...

I have a rhod 110
[Touch Pro2, Tilt 2 Android Development] Germypan:
I hope this! i want android on my tp2!

Germy
[Touch Pro2, Tilt 2 Android Development] jeffgarret:
Flashed last night and things are good apart from what we know doesn't work.

I am getting SOD on my rhod500 but have found that if I open the keyboard and tilt the screen it always comes back on.

Does that work for other SOD sufferers?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
SoD means sleep of death - as in, the phone is dead, impossible to wake back up. What you're experiencing is just a failed wake, and as Nate said before if you hold the button for a second or so it'll usually come up every time.

The kernel needs quite a bit of work, which I'm sure in time it will get the attention it deserves. Just lots of other stuff to clean up and finalize...
[Touch Pro2, Tilt 2 Android Development] jeffgarret:
I get the failed wake too and yes holding the button down longer will get it on. Usually with failed wake the keyboard lights and the bottom button lights are but nothing else. This other SoD issue now won't have any signs of life but if I open and tilit it is resurrected.
[Touch Pro2, Tilt 2 Android Development] dcmedic:
Just as arrrghhh advised you're not having a "sleep of death", if you were you would have to do a battery pull or reset to

recover. You're experiencing a failure to wake, and all the failures will not appear the same, some are longer some are shorter, and some require intervention.

Sent from my MSM using the XDA mobile application powered by Tapatalk
[Touch Pro2, Tilt 2 Android Development] eelektro:
hi I have a problem with my phone... I instaled that Rhodum

but problem is that I cant uninstal it :( how?

and when i turn that phone on its just showing those letters and then restarting and again .... like in circle ....

and I prest that vol up button only few times other times it didnt work

i tried to instal android it sayd that its finished but its yust keep restarting ...

by the way I have a GSM phone... help please
[Touch Pro2, Tilt 2 Android Development] Germypan:
You can return to winmo flashing a winmo rom!
[Touch Pro2, Tilt 2 Android Development] jamtoday2:
i did it ,but :

smd:ch 0 opening -> opened

is stop run .
[Touch Pro2, Tilt 2 Android Development] dcmedic:
Are you using a GSM device, if so that is a known issue. Also GSM isn't fully supported quite yet.

Sent from my MSM using the XDA mobile application powered by Tapatalk
[Touch Pro2, Tilt 2 Android Development] jamtoday2:
yes , i used GSM device, juest see an update ,so do it . . ..
[Touch Pro2, Tilt 2 Android Development] xturbo91:
had the same problem with RHOD100, just use task29 and then flash a windows ROM
[Touch Pro2, Tilt 2 Android Development] Germypan:
Hi Guys, have you any news about GSM Rhod?

Hi guys, i flashed nand without sim card and now i can use recovery, but after i installed on screen of my rhod i see some words but android don't start!

sorry for may bad english

edit: my Rhod crashes on written smd: opening ch 0 -> Opened and then no more

edit 2: i tried with http://www.multiupload.com/TX8984OE5K but nada, rhod crashes on written smd.

Germy
[Touch Pro2, Tilt 2 Android Development] Germypan:
Hi guys, android run on my rhod100_it, i downloaded this files: http://www.multiupload.com/TX8984OE5K and i put in the androidupdate.tgz the build.prop mod from gsm test of mcmutty, and now i see on the screen of my rod the animation of xdaandroid. i post to you the build.prop which i used. But with sim card the rhod looped!
[Touch Pro2, Tilt 2 Android Development] mcnutty:
Thanks Germypan. The reason it restarts with SIM in is because it tries to mount as a SD card. ACL has been looking into it in between other things. He can get it to boot with a SIM in, but it breaks the SD card so you can't install Android... I think he's getting fairly close, but not having a GSM phone to develop on is pretty hard.
[Touch Pro2, Tilt 2 Android Development] Lmiller1708:
Charging works great for me. I don't think it has been a issue for a long time either.

Nate does have a working and non-working list on his second post and is it up to date.

The only big problem I'm having is GPS... I can never get a lock, yes I have waited a really long time too... Works great with Haret but not on NAND. :(
[Touch Pro2, Tilt 2 Android Development] mcnutty:
Apologies for the massive multi-quote here. I do spend most of my time over at the PPCG thread (when I have the time). Hopefully these answers are good enough for now, and I should have a new rootfs posted soon that may resolve a lot of these issues (since the latest rootfs had a lot of testing junk in it).

For wifi errors, it's almost always because the modules name did not match what the kernel expected. Make sure that you don't rename the modules, and always download the modules that are paired with the kernel. During startup, you should also see an error about the modules not installing (if you can catch it in the sea of text before it flies by).

Excellent. It's hard to find people with the non-US variants to test things out. I'm also curious about the panel and might have you do a mmutrace for me (I'll give clear instructions, I promise) ;)

I have never run Neopeek's. The rootfs is only modified to do some of the stuff that startup.txt would normally do for Haret (plus some things Haret doesn't have like keyboard assignment based on hardware rather than reading a text file). I can't say for sure that it will work, but you can certainly give it a try :)

Yeah, I have a feeling this might be due to some of the testing with gralloc and libGLES that we were doing when I made that last rootfs. The next one I'm putting up will have conditional clauses to load the drivers from the SD Card if they are there or load the default ones if they are not.

You shouldn't need the .kb file unless you are trying to override the keyboard layout. I added this in there because we had a rhod400 tester who wanted to check the rhod500 layout.

I also think part of the problem is the gralloc and libGLES that I baked into the last rootfs for testing ACL's files. The new rootfs should be up soon, and maybe that will resolve this issue.

The rootfs does recognize squashfs because I have only modified init to add the NAND specific stuff. Otherwise, it is identical to the init used for haret.

Hopefully the rootfs change will fix it.

We haven't had any charging issues since Wozzer was still working on this project months ago. Him and ACL ironed that out long ago :)

That being said, I am looking at releasing two NBH files for this next compile due to a popular request. Some people would like pm.sleep_mode=1 to extend battery life, and some want an overclock to 710 MHz which isn't on the autobuild.
[Touch Pro2, Tilt 2 Android Development] mcnutty:
OK, I have added all of the rhod100 variants to rootfs now. Just use rhod100_de.kb, rhod100_fr.kb, rhod100_it.kb, rhod100_uk.kb, or rhod100_nordic.kb with the new rootfs I'll be uploading here in just a minute.

Once we get the machine_variant value for your devices, I can hard code the detection in and do away with the .kb files :)
[Touch Pro2, Tilt 2 Android Development] mcnutty:
New rootfs and kernel/modules are in the first post. The rootfs should help with some of the graphical oddities people have been having, and it will auto-mount gralloc, libGLES, and build.prop if they are on the root of your sdcard.

The kernel update today from ACL attempts to fix more of the panel initialization stuff. Apparently there are several different panels used on our devices, and each one requires a little different code to get working. ACL is working hard on that, so be sure to give him some thanks ;)
[Touch Pro2, Tilt 2 Android Development] MobileMini:
Amazing project guys! This really is an achievement :)!

I was wondering is this project focussed on specific phones (Touch Pro2, tilt)? Or can this be flashed to all recent HTC phones. I have a HTC HD Mini, what happens when I try to flash this on the Mini? I like to experiment, but not bricking it ;).