yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
First off, you clearly added other things in the cmdline that aren't required or needed, which is why arrrghhh asked where the hell you got it. If it wasn't him posting that first, I'm sure you would have had many other people saying the same thing.

If you leave the startup.txt as is for your phone, as arrrghhh created them specifically for kbd layout etc, then you shouldn't have issues. You can update all you want with newer kernels, rootfs, etc, just follow the instructions on how to use them and where to put them (via incremental updates) and you should be fine, without adding any additional items to the startup.txt.
[Touch Pro2, Tilt 2 Android Development] elektrik2001:
I'm not interested in starting a flame war. With that said, I followed the instructions posted in the first post (http://xdandroid.com/wiki/Incremental_Updates) which says: "At this point, you may do either one of the following:

Edit the startup.txt to change the line set KERNEL zImage to set KERNEL zImage_VERSION, OR

Delete the original zImage file and rename the new zImage_VERSION file to zImage..."

...so I was merely following the instructions provided on the wiki.

Like I said, since I'm new to this, I *did* ask everyone to be gentle....I guess that's relative ;) I'll try the default startup.txt and rename the zImage so it's exactly called 'zImage'. Thanks.
[Touch Pro2, Tilt 2 Android Development] MrPib:
The only difference is the zImage? Here's the one you posted:

set ramsize 0x10000000

set ramaddr 0x10000000

set mtype 2292

set FBDURINGBOOT 0

set cmdline "root=/dev/mmcblk0p2 init=/init rootwait rw rootdelay=3 console=tty0 rootdelay=3 lcd.density=240 msmvkeyb_toggle=off gsensor_axis=2,1,3 force_cdma=1 pmem.extra=1 physkeyboard=rhod400 pm.sleep_mode = 1"

boot

You added FBDURINGBOOT, took out initrd, and completely changed the cmdline!

No wonder arrrghhh is wondering where the hell you got it.

He made startups for each RHOD variant for a reason, you know.
[Touch Pro2, Tilt 2 Android Development] elektrik2001:
Ah, you're right! I accidentally posted the contents of a 'different' startup.txt. I must have been too *quick* on the control-C / Control -V. The latest one I posted is the one I used (which is obviously different) from the one I originally posted. sorry for the confusion.
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
Glad you got it straightened out, you can clearly see now why arrrghhh responded as he did, and like I said, many others would say the same. As far as being gentle, arrrghhh was... you should see when he really gets pissed!! ;)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Heh, if the rear cam doesn't work, what chance does the front cam have of working? :p

Honestly tho, RHOD100 still have cam problems because the guy who wrote the cam code either hasn't had time to trace it or hasn't been able to trace it. See the cam testing thread for more information. I think several RHOD100 folk have submitted logs to help, see the end of that thread (I wouldn't expect you to read every post in the thread ;))

Anyhoo, there is no fix unfortunately. RHOD100 is pretty different from every other RHOD that exists, hence there are outlying issues with it. I haven't talked to jb (viruscrazy) in a while about it, perhaps some RHOD100 user would donate their device to the cause? He wrote the original code, so he's definitely the best candidate to fix the RHOD100 issues, as well as enable the front-facing cam (since that's the only RHOD with a front-facing cam, I doubt he's even taken a stab at it...)

Hence my reaction - that startup was obviously not the one provided in the FRX07 bundle... ;)

So did you get it sorted out? The Incremental Updates page is correct, you can either change the reference in the startup.txt, or jut rename the zImage_2394879872 to zImage to match the name in the startup.txt - your choice. I personally prefer renaming the zImage, but some might prefer editing the startup.txt - to each their own, they both achieve the same goal.
[Touch Pro2, Tilt 2 Android Development] elektrik2001:
No thanks.
[Touch Pro2, Tilt 2 Android Development] juzzwuzzz:
Thanks for the reply. going to scan through that thread you posted

posted a reply there to give some help
[Touch Pro2, Tilt 2 Android Development] oliwar:
WIFI is finally working!!! Thanks for the help!
[Touch Pro2, Tilt 2 Android Development] the show stopper:
i have my own wifi. but i don't know if it is wep or wpa2 coz verizon guy set it up.
[Touch Pro2, Tilt 2 Android Development] the show stopper:
what did you do to make it work ?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
It's easy, login to the router and find the wireless security settings. To find where to login, go to a command prompt (start, run, cmd) and type "ipconfig". The default gateway of your wireless card is what you put in the URL bar (usually 192.168.0.1). Type that into your browser, and login to it - it's your router, he gave you the credentials to login, right?

Then change the security to WPA2 Personal. Put in whatever passcode you want - you'll have to change all the clients that connect as well, but only once - and this will prevent anyone from hacking your network. Can easily be done in just a couple of minutes on WEP, but it's nearly impossible on WPA/2...
[Touch Pro2, Tilt 2 Android Development] 800xl:
Same problem with cam=reboot even after cleaning the card, freshly unzipping frx07 and letting it boot/settle for 15 minutes. Will I need to get adb working in order to get logs up to the reboot? I'll check the dropbox and see what's there. Is there any quick easy way to tell the panel type and/or cam sensor? Like getlogs and then searching for a particular line or string? Seems unlikely that I'd have an oddball tilt2, purchased new from a small town local AT&T store about 1.5yrs ago, but never can tell.

The oddest part to me is that I know it did work with frx06, and even video was working (tho with an odd blue color shift to it) Maybe I should try to recreate that build/kernel combo and work ahead from there.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Blue color shift in FRX06!?? That... seems strange. You sure this is a RHOD...? lol.

Yes, you'll need adb to get logs. The getlogs app won't work since the phone is rebooting.

As for determining the cam sensor, I'm not sure. I also don't know if panel type is in regular kernels... WisTilt2's old kernel from April should still have it in there tho.

Looks like autobuild does have it. Look for this in dmesg:

Panel type detected: 14
[Touch Pro2, Tilt 2 Android Development] 800xl:
Yep, video looked very bluish, I still have the vids and its a RHOD, honest. :) Looking back it does seem very strange. But, I wasn't being careful then about which kernel or rootfs I was using. Life was good, things mostly worked and it didn't much matter what I tried or how sloppy. I had wistilt test stuff in, F22's rootfs with cmdline keymappings, RIL updates, and it was all tossed in pretty haphazardly. It shouldn't have worked as well then, now it breaks and I'm surgically dissecting each step. Lol ;)

I'll try to at least get the panel type nailed after I get off work.
[Touch Pro2, Tilt 2 Android Development] 800xl:
Here's what I found:

Panel type detected: 15
[Touch Pro2, Tilt 2 Android Development] aberry:
calibration or app bogging down

arrrghhh

I'm back. Formatted, fresh install, let it sit and really don't know what to say. I think it's a calibration issue, but really not sure. FRX07 works just like its supposed to if I use the hardware buttons or the arrow buttons and enter key on the keyboard. The touch screen is sporadic at best. Sometimes it will do what it's supposed to and other times it's nonexistent. I'm going to include the values in my ts-calibration file as maybe they can shine some light on this. Mind you, I have the same phone as you. Rhod400.

ts-calibration based on my spl

791,842,211,841,506,519,801,202,211,203

provided ts-calibration file with frx07

820,881,183,879,497,529,822,179,181,178

my old ts-calibration from frx06

815,864,195,866,504,522,820,178,189,179

after seeing Highlandsun's post in the old FRX06 thread I actually had some hope, but to no avail. My spl #'s are what I have in my ts-calibration now. I have tried the provided one and the old one from frx06 as well. I'm also attaching my latest log so you can see what it's doing while I'm tinkering.

I even tried a different win mob rom. I went back to energy thinking it might have been that. I'm was using an spb mobile shell rom. No overclocking at least that's what they say. I'm sure I'm missing something or it could just be hardware, but sure love any ideas if you have any. My next test will be GBX0A to see if that allows me to use the touch screen as to rule out a hardware issue, but I was thinking I may wait till it's next release. If any of this doesn't make sense let me know and I'll explain in more detail. Was trying not to fill a whole page! Thanks for all of your hard work!
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
That.. is very odd. I got a tester RHOD400, and the ts doesn't work right at all in landscape mode for some reason, but works fine in portrait - it's not one of those situations, is it...?

Also, I'm curious - does the ts work fine in WinMo? I know you said you changed it around... just wondering if it is working OK there. To me, that would rule out a hardware issue. I haven't heard of this one before, I don't know why Android wouldn't like your ts. Has it always been like this? You tried different kernels, rootfs', etc on 06&07? I guess I would be curious to see if GB is any different...
[Touch Pro2, Tilt 2 Android Development] SteelLife:
Do you mean where the haret is located?
[Touch Pro2, Tilt 2 Android Development] juzzwuzzz:
No... The Haret file is on the sdcard. The root is above that.

In android i do the following

I downloaded ES file explorer from the market place.

1. Open ES file explorer

2. go to settings and find there an option to give es explorer root permission

3. Go to the root of your phone (top left corner the SD card icon), and on top it first said (icon of a telephone)/sdcard and after you clicked the SD icon you only see the (icon of a telefphone)/

4. find the folder Data

5. Then find there the file wifi-nvram.txt and open it in the editor
[Touch Pro2, Tilt 2 Android Development] SteelLife:
Uninstall superuser?
[Touch Pro2, Tilt 2 Android Development] juzzwuzzz:
No you need superuser. Es file explorer asks superuser for permission to get into the root of the xdandroid.
[Touch Pro2, Tilt 2 Android Development] aberry:
Yes, it works fine in win mob. The orientation doesn't seem to make a difference. I have the latest kernel and rootfs in my build now. I will try ginger next and see. Ill let you know.
[Touch Pro2, Tilt 2 Android Development] AkumaX:
wow, smoothest experience yet...

Usually I would get a couple FC or hard resets a day, and after a bit I'll get FC galore which requires me to start over (deleting data.img). but this build.. not one FC yet!

FRX07

8/5/11 kernel

7/27/11 rootfs

8/5/11 hyc's ril
[Touch Pro2, Tilt 2 Android Development] aberry:
calibration

Here's my results. Using the calibration files I had I got the same results using GB and then went back to FRX06 and got the same results. Deleted ts file in 06 and rebooted with 1225 kernel and manually did calibration in 06. It worked. Copied that ts file to 07 and back to the same issues. I'm out of time to try combinations now, but will try again over the next couple of days. I will try all the standard things next chance I have. I'm going to put it all in an andboot folder like 06 is. Run the same old kernel,module and rootfs from 06 in 07 with the new ts file. I'll post again when I can. Thanks!
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Good luck! Let me know if GB is any different too... I'm honestly not sure what could cause this issue for you, unless the system is just bogged down - nothing really works well on the phone when it's crunching numbers. I've missed many a phone call because the phone won't display the call in time.
[Touch Pro2, Tilt 2 Android Development] teemo:
RHOD100

- 1. Backup my apps

- 2. Wipe SDCard w. HP full format

- 3. Copy FRX07 edit startup and add ts-calibration

- 4. Boot haret, all seem good

- 5. Setting google account and wait for sync to finish

- 6. Start Market to dl TitaniumBackup (damn autoupdate on all the G-stuff)

- 7. Market updates 5+ apps, so I switch to WiFi (without issues), Market updates, no problems.

- 8. Restore all apps from backup

- 9. So far NO issues. (BT connects to my HTC earphones but as expected, no audio routing)

- I'm happy!

Big THANKS to all developers and arrrghhh for keeping everybody updated.
[Touch Pro2, Tilt 2 Android Development] zooster:
Ok, it's the kernel bundled with frx07 that doesn't work, with the previous kernel it can boot, but there is an issue with the sim. It doesn't get any network (no service), nor it prompt for a sim pin (finally I deactivated it but no success). It's like radio is not working...

edit: if i try to get "status" report in "about phone" under settings, nothing turns back...

edit2: it actually doesn't seem to see the sim, but sim works perfectly in winm and previous frx...

edit3: IMEI doesn't show up using *#06#.
[Touch Pro2, Tilt 2 Android Development] rtrip:
Has anyone found a version of Flash that works?

I tried sideloading a few 10.3 apks, none of which would install.
[Touch Pro2, Tilt 2 Android Development] snalbansed:
Thanks everyone, just booting...

Seems the long boot routine with all the text has returned - haven't seen that for ages! But I guess it will mean kernel logs work again :-)
[Touch Pro2, Tilt 2 Android Development] trusa1:
Hi arrrghhh,

rootfs.img from the FRX07 full bundle and latest one (rootfs-20110716-8a5419e) from the rootfs build service are not the same. Which version is more accurate?

MD5 rootfs.img from the FRX07 full bundle: 3f93e0a4449ef0d745c47dfb5133107a

MD5 rootfs.img from the rootfs build service: 17b69bb5d063d840aa69ddf81e9b7e1d
[Touch Pro2, Tilt 2 Android Development] stinebd:
The latest rootfs, rootfs-20110716-245f68a.zip, fixes this issue, which is caused by the wifi interface rename in cases where a data.img already exists. Thanks.
[Touch Pro2, Tilt 2 Android Development] zooster:
Stinebd, do you have a clue about the problem with my topaz?

update: with or without sim inserted it doesn't change or detect anything... still an x above net bars.
[Touch Pro2, Tilt 2 Android Development] fortunz:
That was fast. :eek: Thanks stinedb and xanathar both. You are gentlemen and scholars. It works perfectly now. :)
[Touch Pro2, Tilt 2 Android Development] maff1989:
Personally, I've had a snappier experience with this ROM over CWM.. although it may well be my 2GB SD card causing the sluggish CWM performance, but the loopback FS is working best for me :D
[Touch Pro2, Tilt 2 Android Development] waltibaba:
Excellent work and great looking rom so far! I actually enjoy loopback much more than cwm, and at our current level of progress, nand is a definite no-go hehe.

I do have a question though; I just recently got my rhod100 and am now finding that no rom lets me use wifi (including yours). When I turn wifi on it says unable to scan networks, and turns itself off again. I looked around and noticed that this issue was spoken of before (latest I found was around december/jan). Was there a solution to that? In particular with your rom, I doubt an early kernel build will work well (or at all). Does anyone here know of a solution? I'd be very grateful!

Once again, thank you for your great work and dedication!
[Touch Pro2, Tilt 2 Android Development] dadaR6:
This release works really well, I can finally leave my SIM card inside my RHOD400.

FYI, I noticed that if Windows was booted up with BT ON or BT was used in Windows (even turned OFF before booting Android), then Android will not enter deep sleeps. BT needs to be OFF from beginning to end in Windows. I verified this with a fresh data.img and no app was installed.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
For wifi, have you read this section of the FAQ...?

Interesting find. I don't ever have BT on in WinMo (or anything for that matter :p) so I'd never run into this bug. I'll add it to the caveat list.

To those who have working BT headsets - wow! I didn't expect audio to route correctly.... Seems hit or miss. Don't expect it to work well :p.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
I'd say you should add "Leave WinMo in Airplane Mode" onto the caveats. Having any of the radios activated while HaRet boots is bad news all around.
[Touch Pro2, Tilt 2 Android Development] MisterNauta:
I'm succesfully running FRX07 on my RHODIUM. It works great, just a little bit irresponsive (I mean slow to respond). in some situations. I'm using TIM Mobile operator from Brazil.
[Touch Pro2, Tilt 2 Android Development] 951porsche:
Can anyone running FRX07 see if they can install the bestparking.com app? I've been trying to work out why it won't install for hours now and I can't get it to install, it was fine on my FRX06 before but everytime I try to install it gives me the "installation unsucessful" error.
[Touch Pro2, Tilt 2 Android Development] juryrigger:
Anyone else not getting video with the YouTube app? Sound yes, video no?
[Touch Pro2, Tilt 2 Android Development] Eodun:
Have you tried deactivating HD?
[Touch Pro2, Tilt 2 Android Development] juryrigger:
If you're asking if I have the "high quality on mobile" option unchecked, yes, it is unchecked, and no video.
[Touch Pro2, Tilt 2 Android Development] nasapunk88:
great battery

I just restarted from a fresh setup last night before bed and this morning went to Disneyland. I had FRX07 running and installed all my apps, didn't turn any autokill on or shut anything down from Syncing automatically. My phone lasted from 8am to around 9:30pm. O_O i've never had this long before when I'm actually using the phone. I was even on/off gps checking in (foursquare) to all places and using it in lines. Amazing Battery Life! That's 13 1/2 hours. Avg on FRX06 was 8 for me.

Excellent work! Now I have time to start playing/testing each component and I'll get back to you.
[Touch Pro2, Tilt 2 Android Development] Raul^:
I can confirm, with new wifi file moved to data wifi still doest find any net in FRX07 for me.
[Touch Pro2, Tilt 2 Android Development] SteelLife:
I have no wifi so I can't goto market place! I think superuser is blocking me
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
SU doesn't block anything, unless you tell it to (a dialog will pop up when any app requests root access - allow/deny).

As for wifi in general, it certainly doesn't block wifi. Did you have to do the wifi-nvram.txt trick in FRX06? If so, just re-use that same file...
[Touch Pro2, Tilt 2 Android Development] juzzwuzzz:
Like said above.. Super user doesnt block.. It give's permission to get into the root. So dont uninstall it.

Cant you go to the market on your mobile plan? Or else use this link to go to es file explorer in android market
[Touch Pro2, Tilt 2 Android Development] the show stopper:
what is wifi-nvram.txt trick ?
[Touch Pro2, Tilt 2 Android Development] SteelLife:
Yes, I tried to but Terminal Emulator keeps crashing.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Have you read the FAQ?

Can you get logs after it crashes? I'm really wondering 'why' this happens to some but not others.

GetLogs is a great app that helps you easily... get logs :p. In AndroidApps\Other.
[Touch Pro2, Tilt 2 Android Development] cougargt:
I'm kinda new at this and kinda lost. I've done all kinds of searches but can't seem to find the answer. I have a Tilt2 and I don't get any sounds in Android. Now I did get sounds a couple times when bootin into Android but would loose them when I used something like a bar code scanner. I'm using the up to date files, but just not getting any sounds. And after 2 screen picks in the settings for sound I have to force close the app. I really do like Android for somethings and would like to use it But it's useless if I can't hear any thing. Could someone at least point me in the right direction?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Hrm... that's an odd one.

Format your card with the HP Tool. Full format, FAT32. Then start fresh with the bundle in the first post.

If you get sounds at first, then they stop working then something odd indeed is happening. Have you added any of the experimental acoustic code? If no, then I'd be interested in seeing some logs while sound is working for you, then some more after it dies.... If it keeps happening, this is going to be the only way to truly see what's happening. GetLogs is a great tool for this, it's in AndroidApps\Other.
[Touch Pro2, Tilt 2 Android Development] cougargt:
Ok....I'll give everything a try.
[Touch Pro2, Tilt 2 Android Development] lbazil:
Power management and Bluetooth

Observed on Sprint Touch Pro 2 (RHOD400), but probably applies to other versions, as well: the phone will not go into sleep properly if Bluetooth is ON in Windows Mobile (WM 6.5) at the time HaRet is executed to boot Android. In suspend mode the phone will continuously try to go to sleep and then instantly wake up (as can be seen in the logs) blinking the LED between orange and green, though not turning on the screen.

This obviously eats up the battery pretty quickly while keeping the phone warm.

All you have to do is make sure Bluetooth is OFF in WinMo before you boot into Android.

This has already been discussed in fragments, but I have not seen a clear connection made between pre-boot Bluetooth status and phone sleep state in FRX07, so I think this issue belongs in the FAQ.

Regards,

Leo.
[Touch Pro2, Tilt 2 Android Development] cougargt:
Getlog

Reformated the card and loaded a fresh copy of frx07 with rel_path=android in the startup.txt. Everything loaded (i think) but no sound. And I get the force close window when trying to pick more than 2 or 3 things in the sound settings.
[Touch Pro2, Tilt 2 Android Development] kern417:
Ringtones folder?

Where do you store personal ringtones/notifications? I had a 'media' folder with subfolders for each category but somehow i must have deleted it. Can anyone let me know the file paths so i can recreate the folders?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Agreed! It is a wiki, but I can add it later ;).

Hrm... I wonder if that's the issue.

I'll take a look at your logs, but can you try a folder name other than 'android'? The reason I ask, is there is an 'android' folder created by the Android system. I don't know if that would interfere, but it might...

You can store them wherever. You can even re-create the media folder, you don't need any special 'file paths'. Just put the media on the card wherever you see fit. The 'media' folder was removed from this build, as all the ringtones/notifications are now baked into the system image.
[Touch Pro2, Tilt 2 Android Development] kern417:
ok that makes sense. I was really trying to figure out when did i delete it haha. So how do i make the phone find ringtones/notifcations? I did a workaround for ringtones and went thru the music app and made a song a ringtone, but for notifications i have some sounds i like to use for text/tweets but it doesnt pick them up as an option

Edit: nvmd i found my FRX06 zip file and unzipped to figure out the media file path. this still works for anyone who's wondering, just make a folder in the same location as ur haret file named 'media', another under that named 'audio,' and then i made 2 under that, one for 'alarms' and one for 'notifications.' this is the same way it was under 06 and i didnt even have to restart android, the next time i went to select a notifcation ringtone it was already on the list like it was preloaded. hope this helps anyone in my predicament.
[Touch Pro2, Tilt 2 Android Development] SteelLife:
It says the data log text is to large
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
...wat.... you don't have space on your SD?
[Touch Pro2, Tilt 2 Android Development] SteelLife:
no, no, I have 3gb's free, when I try and upload to here it says its to large a file