yashsingh1/xdaforums huggingface dataset:
[Nook Color General] christoophat:
I installed both "the official" xbmc remote, and the other one that is rated well, but neither one is working. The official one asks that I set up Hosts in Settings, but the settings page it offers is blank. So there is no way to do what it is asking

The other one, keeps telling me to make sure XBMC is allowing control via HTTP in Network settings (which it is) My Nook is connected to my wlan, so it should be connecting :confused:
[Nook Color General] RASTAVIPER:
Unified Remote Control offers the most remotes I have seen in 1 program.

Really simple and handy. ;)
[Nook Color General] christoophat:
Do you know if it successfully works in XBMC?
[Gen8, Gen9, Gen10 Q&A, Help & Troubleshooting] kakkuk:
hi, i tryed meny times but my archos 101 no developer menus please can some one tell me or post video or photo please

i tryed

3) Reboot your Archos holding "Volume -"

4) Recovery System -> Developer Edition Menu -> Flash Kernel and Initramfs

there is no develoepr menu
[Gen8, Gen9, Gen10 Q&A, Help & Troubleshooting] chrulri:
Have you installed the SDE firmware? I don't think so
[Gen8, Gen9, Gen10 Q&A, Help & Troubleshooting] umberto.sulla:
You need to download SDE Firmware first, from Archos downlad section.

Then you need to "Update firmware" holding vol-

Only with SDE fw installed you will be able to flash custom Kernel and Initramfs.

Read well Archos disclaimer...
[Gen8, Gen9, Gen10 Q&A, Help & Troubleshooting] evo_x212:
Hi...i'm newbie here about my Archos 7o 250gb

i've some problem here...after install the SDE..i can't enter recovery mode anymore...

i try reboot then hold "Volume"...it's always enter the SDE (angStrom) not the recovery mode..

Now i'm used 2.1.3 Froyo...

(sorry for the english)
[Gen8, Gen9, Gen10 Q&A, Help & Troubleshooting] umberto.sulla:
Usually this behaviour is due to pressing both Vol+Vol- athe same time with power button.

If you only press vol+ and power button you should be able to access developer menu...

Please check.
[Vibrant Q&A, Help & Troubleshooting] kamikazimonky:
high im new to the vibrant flashing. ive been here for awhile started with g1 then to nexus one now vibrant. ok i rooted n flashed rom and phone was running great. i was running axura 2.2.7.1 and i came acrossed this vodoo kernel http://xdaforums.com/showthread.php?t=870480. And i flashed it from the sgs flash kernal app and when it rebooted it said some bout no rom on partion and wouldnt boot. so i went to recovery to nandroid and my intire internal sd was wiped clean. so i data reset and tried flashing a rom and get this....

Formatting system...

formatting cache....

formatting datadata...

formating data....

E:can't mount /dev/block/mmcblk0p2

(file exists)

error mounting /data/!

skiping format...

deleting files....

deleting files...

deleting files...

E:can't mount /dev/block/mmcblk0p2

(file exists)

copying files...

copying files...

E:can't mount /dev/block/mmcblk0p2

(file exists)

E:can't mount data:

E: failure at line 13:

copy_dir PACKAGE:data DATA:

installation abort

and when i boot the phone it gets stuck on the vibrant boot and i think it says convert system partion.

ive never fully bricked a phone before is this what a full brick is??? can some one please help me who knows this stuff better and if you can fix it i will donate very generiously if someone will take the time to help thank you for your time.
[Vibrant Q&A, Help & Troubleshooting] Gibsonusa:
Sounds like a case of odin and restarting. Pretty easy think the odin stuff is a sticky in the general portion of vibrant section. It's almost impossible to f up this phone beyond fixing.
[Vibrant Q&A, Help & Troubleshooting] kamikazimonky:
ok yeah when i came from the nexus one i saw the odin and vodoo stuff but stupid me didnt research it any figured everything was like nexus... wow was i wrong things little different on here ill look into the odin thing and if i can get it back to runinng i will donate to you if able. if i cant would you be willing to help me further. im not a noob just its lot different from the nexus one.
[Vibrant Q&A, Help & Troubleshooting] kamikazimonky:
how do i get odin from herehttp://xdaforums.com/showthread.php?t=848737 i download the one that says odin but its just a rar file and dont do any thing. how do i put the files with it?
[Vibrant Q&A, Help & Troubleshooting] iynfynity:
did you even try to extract the one that you download? :p
[Vibrant Q&A, Help & Troubleshooting] kamikazimonky:
for some reason on the rar file its not letting me have an extcart option sorry if all this is a lil dumb not the biggest comp. person. screen shot attached
[Vibrant Q&A, Help & Troubleshooting] Oniyuri:
you need winrar in order to open rar files. not sure if 7zip can do it, but it's worth a try (seeing as it's free and all).
[Vibrant Q&A, Help & Troubleshooting] kamikazimonky:
7zip worked fine and i put them in and click start and does nothing n i am in download screen on vibrant.
[Vibrant Q&A, Help & Troubleshooting] nomadrider123:
not sure what is up but this might help

http://www.youtube.com/watch?v=KyAIUOYufrU

Part 2: http://www.youtube.com/watch?v=33I-aNCypVM
[Vibrant Q&A, Help & Troubleshooting] jmcghee1973:
Your gonna need ODIN and eugenes froyo that doesnt brick

You will also need 512.pit and JFD.tar file .. you can get these via the Bible sticky ..eugenes froyo is on his site..

Try to see if you can get into Download Mode:

Pull everything out ..battery, sim, scdard

Open ODIN and leave it on your PC

Plug the USB cable into the PC

Put the battery back in

Hold down on both of the volume buttons

Plug the usb into your phone...keep holding the buttons

It should go into D/L mode....we hope..

If it gets that far..make sure you see a yellow COM port in ODIN

Not sure with eugenes froyo but 512.pit goes in the PIT line

eugenes froyo.tar goes in the PDA line

I think you may need Repartition checked in your case to get the filesystem back but if his site says not to then dont.

Hit start

This is not a daily driver ROM...just to allow you to re ODIN

If it works...again we hope... You need to go back into D/L mode

check for COM port

add the 512.pit & this time the JFD.tar to PDA

uncheck repartition and hit start

and hopefully you will get back to stock 2.1
[Vibrant Q&A, Help & Troubleshooting] bartek25:
one question did you repartiton your internal sd with rom manager or just voodoo it ?
[Vibrant Q&A, Help & Troubleshooting] kamikazimonky:
im having trouble finding the eugenes froyo.tar file anywhere.

edit: i believe i found it at the right place will try it out http://eb-productions.net/vibrant/vibrant-unofficial-tmo-2-2.html
[Vibrant Q&A, Help & Troubleshooting] kamikazimonky:
just vodooed it never mest with partitions with the card
[Vibrant Q&A, Help & Troubleshooting] Gibsonusa:
Also not sure what version of odin you might be using. I used odin v1 and it wouldn't work for me after more looking around read that v1.7 was the one that would work. I think that one is in the q&a stickies says like root odin stuff like that. Also found that the pit that ended in 12 worked better than the one that ended in 13. Fact I also couldn't get 13 to work either.
[Vibrant Q&A, Help & Troubleshooting] kamikazimonky:
well both 1.0 or 1.7 neither reconize my phone now for some reason and windows says im missing dirver s or some that hardware wasnt installed right. man this is getting so frustating and i love this phone
[Vibrant Q&A, Help & Troubleshooting] Gibsonusa:
Ill get on computer in a minute and tey to peovide you some links
[Vibrant Q&A, Help & Troubleshooting] Gibsonusa:
Samsung drivers for your computer so it picks up the phone.(just read the things to click i had a ***** of a time finding it and thought that you had to buy the software but you dont im just not that great at looking at what i need to be clicking on.)

http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-USB-Driver-for-Windows-x86.shtml

A nice little how to unfunk your vibrant and how to get it into dl mode

http://xdaforums.com/showthread.php?t=848737

Odin 1.7 rar files

http://xdaforums.com/showpost.php?p=8863820&postcount=138

(sorry if you have this stuff but these are the steps that i went threw when i had boned my phone pretty hard)

Eugene 2.2 stock odin thingy

dont use the odin that comes with this btw i know i didnt or i think i tried and it was dumb and wouldnt work.

http://www.mediafire.com/?cb8vpwob8hz6yxv

alright man so go step by step unpack the sammy drivers and open odin 1.7 then plug in your phone SHOULD find your phone after you get those drivers installed on your comp. any port will do when odin finds your phone.

put the 512 pit file in the pit spot (uncheck repartition if it is checked)

then put the tar file or what not in the tar spot and click start it SHOULD only take about 3-5 minutes depending think it took me less then two but everyone seems to have different times i guess.

When you are back to stock let it sit a minute or 5 reboot to work out whatever kinks it might have then find you a rom and flash. FOLLOW THE DEV INSTRUCTION ON WHATEVER ROM YOU PICK. hehe pm me if you still have problems, shouldnt though
[Touch Pro2, Tilt 2 Android Development] F22:
Available Keymaps/Layout Sets

In this rootfs, the following rhodium keymap/layout sets are available:

rhod100_de

rhod100_es - new!

rhod100_fr

rhod100_it

rhod100_nl - new!

rhod100_nordic

rhod100_uk

rhod110 - new!

rhod210

rhod300 or tilt2

rhod400

rhod500

They may be selected in the usual physkeyboard= manner from within the startup.txt file in the android boot folder. If you experience issues with any of these keymap/layout sets after downloading & installing the rootfs above please do not hesitate to let me know.
[Touch Pro2, Tilt 2 Android Development] EGOvoruhk:
Oh Em Gee

<3
[Touch Pro2, Tilt 2 Android Development] XavierGr:
What about rhod100_gr? I have a rhod100 device with greek layout. The only difference is that the envelope key will toggle between English and the respective Greek characters. Any pointers how to achieve this?
[Touch Pro2, Tilt 2 Android Development] jmstumme:
rhod500 has no space bar :-\

edit:

no phone, settings, back buttons
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Nice work F22, lookin forward to seeing this committed! I'll test this out sometime today, doing some battery testing for WisTilt2 :p.

Glad to see you did both rhod300 and tilt2, so old startups don't break and new ones can actually make sense by using rhod300!

I do have one stupid question that I'm pretty sure you've partially answered already - if you do the b4Home trick, and don't remap power=end call, you lose the end call button... correct? If so, you may want to add that caveat with this line

Y'know, for stupid people like me ;).

Thanks again! I'll give ya some feedback later.
[Touch Pro2, Tilt 2 Android Development] F22:
Rhod500 Issue

That sounds like a microp layout issue. Look at the contents of /sdcard/kbd_info and tell me what you see. As an example, here is what I'm seeing in mine:

I expect that yours should say rhod500 wherever mine says rhod210. Note that this file is only written to if you're running my rootfs. It will still be present however if you switch back to your original rootfs. I created it specifically to help debug issues like yours. It would also be helpful if you'd post your startup.txt just to make sure that looks good as well.
[Touch Pro2, Tilt 2 Android Development] F22:
Greek & Other Cyrillic Keyboards

I only updated the existing key maps/layouts in the repo, and unfortunately Greek wasn't in that list. The Cyrillic key layout on the Greek keyboard presents an additional layout issue, ie. the language key you just mentioned . To be entirely honest at this point, I'm not certain how android handles that. I can look at android's documentation as my time permits. What native android handsets are currently available in Greece or Russia? If we could pull the key layout/map files off of one to serve as an example, that would make creating Cyrillic layout/map sets much easier.
[Touch Pro2, Tilt 2 Android Development] F22:
LOL! Ok. Done. (On the caveat.)
[Touch Pro2, Tilt 2 Android Development] jmstumme:
Selected Keyboard: rhod500
RhodInfo=rhod500
RhodModel=rhod500
Rhod100Lang=
RhodOptions=
mpkl=rhod500
Selected MicroP Key Layout: /init.etc/keymaps/rhod500_microp-keypad.kl
Selected MicroP Key Code Map: /init.etc/keymaps/rhod500_microp-keypad.kcm
Mapping Button 4 to ENDCALL
Selected Keyboard: rhod500
RhodInfo=rhod500
RhodModel=rhod500
Rhod100Lang=
RhodOptions=
mpkl=rhod500
Selected MicroP Key Layout: /init.etc/keymaps/rhod500_microp-keypad.kl
Selected MicroP Key Code Map: /init.etc/keymaps/rhod500_microp-keypad.kcm
Mapping Button 4 to ENDCALL
Selected Keyboard: rhod500
RhodInfo=rhod500
RhodModel=rhod500
Rhod100Lang=
RhodOptions=
mpkl=rhod500
Selected MicroP Key Layout: /init.etc/keymaps/rhod500_microp-keypad.kl
Selected MicroP Key Code Map: /init.etc/keymaps/rhod500_microp-keypad.kcm
Mapping Button 4 to ENDCALL
[Touch Pro2, Tilt 2 Android Development] XavierGr:
Currently Desire Z is a native Greek android phone. I looked on the HTC Greek manual and the keys are double inscribed (corresponding Greek characters are inscribed next to the Latin ones). This means that Desire Z can write Greek with the hardware keyboard but I am not sure which is the exact procedure to change between layouts.
[Touch Pro2, Tilt 2 Android Development] F22:
Re: Rhod500 Issue

Hmmm...that looks exactly as it should. Is anyone else with a rhod500 experiencing this issue? When I return later tonight I'll tell my rhodium it has a 500 kbd and see if I experience the same issue. The three microp front panel buttons (call, menu, back) are the same across all of the model layouts.
[Touch Pro2, Tilt 2 Android Development] F22:
The easiest/quickest way to make a Greek key map/layout for the rhod100_gr is to get someone you know who has a Desire Z to copy the .kl & .kcm files off their handset and use them as a guide. Alternately, if we can obtain a Greek version of the Desire Z ROM then we can pull the required files off it. Failing that we'd need to first look up how to handle the language key in the android docs and replace envelope with that in a new Greek key layout file, and then find the utf8 representation of each Cyrillic character and add them all to a new Greek keymap. It would be far quicker to pull the utf8 hex codes from a pre-existing Android Greek .kcm file however.
[Touch Pro2, Tilt 2 Android Development] dancingtimmy:
I tried this out today on a rhodium100 using rhodium100_uk setting. I originally did not try the b4Home cmdline option, but found a problem with prehome.

I used spare parts to set the end key to be home. and then set prehome to be my home app and then configed prehome to launch launcher as the home app. The "end" key worked as desired and launched prehome. But I could not get the second press of home (while in prehome) to trigger and launch launcher. Nor would a double press of home get me to the launcher.

This issue could be a prehome issue.

I will do some more testing tomorrow using the b4Home feature (first test of it did not work too well as i seem to be stuck in prehome with no way of getting out as the home key does nothing once inside prehome).
[Touch Pro2, Tilt 2 Android Development] highlandsun:
If we use this b4home option, is the Spare Parts end button setting relevant any more? Do we have to undo anything on that setting, or does it just not matter?
[Touch Pro2, Tilt 2 Android Development] dancingtimmy:
I have confirmed that the b4Home option has no effect on my rhodium 100. Maybe I am doing it wrong? I simply added the text b4Home as an extra argument inside the quotes of the set cmdline in startup.txt. (I also tried b4home - lowercase h). During these tests i removed the spare parts setting for the end key.

The only way I can get a working home key is to use spare parts and assign home as the end key action. Single press of home then works correctly, but a double press does not work (it seems to do nothing). A press of the home key after invoking prehome or task switcher does nothing.

I have a very early T7373 model and am using the 100_uk keyboard setting as I have the dollar, euro and pound symbols on my keyboard.

I believe i applied the rootfs.img correctly as the envelope key opens search and envelope b opens the browser.

About phone reveals

Android version 2.2.1

kernel version 2.6.27.46-01202-g6c41ca6

build number FRX03

I previously had installed android back in september and was never able to get a working home key.

Any hints on other tests / tweaks I could perform?
[Touch Pro2, Tilt 2 Android Development] F22:
Combining b4home with the spare parts option

The Spare Parts setting becomes irrelevant if the b4home option is used. The Spare Parts option changes the behavior of the button assigned the ENDCALL keycode. The b4home option on the other hand changes the actual keycode of the button from ENDCALL to HOME. There is thus no longer a button or key assigned the keycode ENDCALL for Spare Parts to modify.
[Touch Pro2, Tilt 2 Android Development] F22:
GPIO key layout not loading properly.

This isn't entirely surprising. The option in spare parts doesn't truly make endcall the home key, it just enables the endcall key to function as home on short presses. Long presses still don't work, and if preHome checks the actual keycode of the key, it will see endcall and not home. So I'm not particularly surprised that preHome isn't working with the option in spare parts.

There are actually 2 different layout files that XDAndroid uses depending on the driver responsible for the keys/buttons in question. It sounds like your microp layout file is working splendidly as evidenced by envelope working fine as search/short cuts. Nevertheless it sounds like you're not loading the correct gpio layout file.

The option to reassign button 4 on the front panel to Home is actually b4HOME, and not b4Home or b4home. Linux is case sensitive and there was an error in my instructions above. I've now fixed the instructions in post #1. Thanks for reporting the issue.
[Touch Pro2, Tilt 2 Android Development] dancingtimmy:
Awesome!

the b4HOME works a treat on my rhod100_uk. prehome working as expected with launcher now. single, double and long press all work.

no need to remap the end key versus spare parts.

thanks!
[Touch Pro2, Tilt 2 Android Development] F22:
New Rootfs (Feb 1st) - Tilt2 Bug Fixed

I've posted a new (Feb 1st) release of my rootfs. See the 1st post for the download link. It includes two changes:

1) The Feb 1st release fixes a bug biting Tilt2's. In the previous Jan 31st release a symbolic link was missing causing the copying over of the microp keymap binary to fail. Tilt2 users who were experiencing issues with the Jan 31st version should go ahead and try the new version. Thank you randomblame for reporting the bug.

2) It also adds a default keyboard set for rhodium, so that rhodiums will get the rhod100_uk keyboard set assigned by default if no "physkeyboard=" field is present in startup.txt. Previously a non-rhodium keyboard that worked poorly on rhodiums had been assigned.
[Touch Pro2, Tilt 2 Android Development] sportfisio:
Thanks! But how can I open and edit that file?

EDIT> I think on excel...?
[Touch Pro2, Tilt 2 Android Development] F22:
Opening & Editing a .7z file.

Unfortunately xda-devs only allows files to be saved with specific extensions. I saved it as a .7z file for simplicity. So you need to use an archival utility that understands 7zip format to uncompress it. Google 7zip if you don't already have one. Once you have it uncompressed, you can edit it with your favorite text editor. Notepad will work if your computer is running MS Windows.
[Touch Pro2, Tilt 2 Android Development] dcmedic:
Sorry Delete this post
[Touch Pro2, Tilt 2 Android Development] F22:
UTF-16 Key Map Codes

Actually you made a good point. It's UTF-16 not UTF-8. Google's porting doc is wrong, and I really should have caught Google's mistake when I used a 16 bit example.... I've corrected my original post. Thanks for catching it.
[Touch Pro2, Tilt 2 Android Development] sportfisio:
Ok, I'm on it! But, for non-ASCII symbols, do you mean regular or not extended ASCII too? I mean: by pressin Fn+A, I should get "á" symbol..."á" is not regular ASCII, but I found is present on extended ASCII tables...So, how I put his? As "á", or in UTF-16 hex?

Thanks!

EDIT2: Finally got greatful help from tiad8.com, and gt this! Hope this is ok!! (reuploaded the final layout, thanks to mewzickl!!!)
[Touch Pro2, Tilt 2 Android Development] F22:
Rhod 100 ES (Spanish) Key Map

Hmmm...this appears to match the keyboard exactly, but is missing most of the extra characters I added previously. (See the spreadsheet attached to the first post if you're not sure what I'm talking about.) That's ok, it looks like many of extra characters will need to be moved around to fit them in. It may take me a day or two to get around to it however. I'll post a new rootfs once I've taken care of that.
[Touch Pro2, Tilt 2 Android Development] Starfox:
When you post the new rootfs, can you do a few things?

1) Integrate hyc's init ppp patch

2) Support for the battery monitoring thing (scms) from ppcgeeks.

3) Compress the file with 7zip using 6mb or smaller dictionary (which according to AndroZip is the max an Android app can malloc at a time). That or use zip/bz2/rar, since I haven't run across a problem decompressing types other than 7z on my phone.

Thanks...

-- Starfox
[Touch Pro2, Tilt 2 Android Development] highlandsun:
You can get these files here in case you were wondering. But now there's some discussion about whether the ppp device name belongs in init.rc, or whether the ril should just determine it itself. (E.g., checking for the existence of /dev/smd7 first.) So the init.rc files may change again. I'll keep you posted.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Why can't you decompress on your PC? I don't think I would ever want to decompress anything on the phone, if I can help it.

Also, scbs isn't stable, and shouldn't be integrated yet. Stuff is likely to change, so there's no point in integrating it. Same probably goes for hyc's work, as he stated above.
[Touch Pro2, Tilt 2 Android Development] Starfox:
Because I don't have access to a computer right now (been that way for 2 month). I can do a lot of things, but changing system allocation limit is, unfortunately, a bit beyond what one can do with a smartphone.

-- Starfox
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I guess I assume most people on here either a) have a computer or b) have access to a computer that they can borrow.

Updating your Android build must be a chore!
[Touch Pro2, Tilt 2 Android Development] F22:
1) I'm willing to consider this. I need to discuss it with hylandsun since it's his patch. If I do, it probably won't make the next build.

2) As already noted by Arrrghhh, scbs doesn't seem to be stable at the moment. I'm thus not inclined to add it until it stabilizes.

3) I'm kind of torn on this one. Switching to either a lower compression level or a different archiver will result in larger file sizes. Lowering 7z's compression from 5 to 3 (there is no 4), reduces the dictionary size from 16MB to 1MB, but also results in a file size increase from 9.2MB to 10.3MB. Switching to bz2 results in a size increase to 11.8MB, and gzip results in an increase to 11.9MB. (rar is proprietary so I don't much care for that one.) What does everyone else think? I know some people have bandwidth caps.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
I've updated my merge request for these changes on gitorious. I'd say they're ready to be incorporated into a build. There's no downside to this particular change, it's fully backward compatible.

https://gitorious.org/xdandroid/rootfs/merge_requests
[Touch Pro2, Tilt 2 Android Development] Entropy512:
2MB growth on a 9MB file - Stay the way it is. Someone who has no access to a PC for recovery purposes if they screw something up shouldn't be messing with xdandroid in the first place...