yashsingh1/xdaforums huggingface dataset:
[Optimus One, P500, V Q&A, Help & Troubleshooting] mesaja:
Sorry to bump the old thread, just confused whether to make a new thread or should join this thread.

I got same symptom with my compass keeps stuck in SW direction, since self upgrade to stock rom P500. tried with CM7.2, PowerGB X, Oxygen 2.8 no cure.

Tilting will result movement of compass arrow, but not with magnetic orientation.

here's chronology:

1. stock ROM froyo 2.2 => compass with working flawlessly

2. self upgrade to stock ROM GB (2.3.3) V20G (via LG Mobile Support Tool) = compass problem

3. flash to PowerGB X (2.3.7) => same problem

4. flash to CM 7.2 (2.3.7) => same problem

5. flash to Oxygen 2.8 (2.3.7) => same problem

googling found solution for HTC, SonyEricsson, Samsung, but not for LG (P500 specifically).

The above solutions involved editing sensors.conf file in system/etc directory, in which no such files exists in system/etc LG P500.

Could anyone help me? I want GB based ROM, but how to fix the magnetic sensor problem?
[Optimus One, P500, V Q&A, Help & Troubleshooting] Joel Chan:
For me I calibrated the sensors by moving the phone in figures of eight. At first it didn't work, but when I did it near a weak magnet, problem solved
[Optimus One, P500, V Q&A, Help & Troubleshooting] mesaja:
Just tried that, but no help.

link :

code.google.com/p/cyanogenmod/issues/detail?id=5356
[Optimus One, P500, V Q&A, Help & Troubleshooting] mesaja:
solved by installing built in standard LG O1 compass from snaptic, first time it launched the apps detected abnormal magnetic configuration, it suggests to calibrate, when I did it, the compass works finally!
[Galaxy Tab General] beestee:
Got SIP and GV working on my tab, now I just need an unlimited data package. Virgin Mobile seems to have the most reasonable unlimited mobile broadband package I can find.

Would it be easy/possible to activate the VZW Tab as a mobile broadband device through Virgin Mobile? Do I need to unlock the device? Any other particulars I should know before trying to do this? Thanks!

EDIT: Looking into it more I think I might just pick up a Mifi2200 to use with the plan, that way I do not have to use the battery on the tab to do tethering. The Mifi device is pretty sleek and small, so it wouldn't seem too burdensome to keep it with the tab.
[Android Software/Hacking General [Developers Only]] pipposanta:
Hi,

I am a user of the joggler.info community. We are trying to create a working build of Android 2.2 using the android-x86 source and the vilivs5 modifications.

Until now what has been achieved is the following:

basic graphic support (the image is 8bit color) most of the time the interface is fluid during the transitions not. Many games doesn't work, I tyhink because of the lack of opengl es.

wireless support

ethernet works

touchscreen works

audio works

We would like help overall for the graphic/display driver. The user who is working on this has also tried to apply the 32bpp patch but the result is a yellowish image.

If anyone knows how to make any changes or improvements post it here.

Thanks!!!
[Android Software/Hacking General [Developers Only]] fredfrop:
+1 for this please
[Android Software/Hacking General [Developers Only]] UKseagull:
I'd love to see this developed too. :D
[Android Software/Hacking General [Developers Only]] pipposanta:
in the meantime we have an almost full working image of Android 2.2. You can download it here: http://www.multiupload.com/FSK4RWEYTR

You can follow the development here: http://joggler.info/forum/index.php (software -> mobile os section, android 2.2 thread)
[Android Software/Hacking General [Developers Only]] markeh:
bump....

i wish i knew anything useful about android to help with this
[Android Software/Hacking General [Developers Only]] mur76:
cmon anyone want to take the challenge up, we nearly have a £50 android 2.2 tablet, that runs very well, we just need expert help
[Android Software/Hacking General [Developers Only]] darkwildchild79:
Damn what happen, you just forgot about this section or was it a completely fail project??? if i am lucky i might try a jellybean when i get mine, just need some foundation help :)
[Desire HD Accessories] JamesBarnes:
I bought a desktop dock which was very cheap (same one thats floating around everywhere for ~£12)

It ok, but it had a few problems.

Firstly the micro USB plug is too long and the phone doesnt sit snugly in the dock, its suspended in the air so it wobbles and tilts.

Fix: Lenscloth (3 layers) + Scalpel + Hotglue = Mini Cusion!

Secondly, there is no on/off switch for some reason, which means having to unplug the damn thing if you dont want the lights on or dont want it to charge.

Fix: Pliers + File + Soldering Iron = Switch!

Lastly, the blue led is bright as hell! It projects a huge blue circle on the ceiling.

Fix: Squirt it with hotglue :)
[Desire HD Accessories] sromer:
good idea, i might get around to doing the same to mine eventually
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] sudeep6258:
As the title says.. Whenever I use the hard key buttons the touchscreen stops responding + at times it randomly decides not to response. Kindly suggest..

Things I have done :

1.) Flashed new radio + ROM

2.) Removed screen protector.

3.) Did task 29 and then flashed a new rom.

Kindly help :)
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] boomboomer:
Sounds like a hardware failure, which isn't uncommon for the touchscreen - search this forum for more examples.

Warranty or repair are your options.
[Touch Pro2, Tilt 2 Android Development] d_PhantoM17:
hey! i've got this issue with the mapping of the italian keyboard. The FN key doesn't work, when i press it, it gives me the @ symbol. I wanted to fix the problem my self by editing the file in the rootfs.img, but to open it you need to mount it in Ubuntu. I installed Ubuntu, but i couldn't manage to mount the file, since it's the first time i use linux. I entered in boot mode by typing: sudo bash (it makes me a root user)

then i typed: mkdir mnt/New_folder, but it kept on saying "cannot create directory" . So now i can't create the new folder to mount the rootfs.img !!!! It's driving me crazy!! please help!! I would appreciate if someone could explain me how to do it or fix this thing for me!!! Thanks!!!!!!
[Touch Pro2, Tilt 2 Android Development] sad0felix:
Hi, there's a typo in the example "startup.txt", you have to put the _ like for other keyboard layouts, i.e. "rhod100_it"

Happy xdandroiding

Ciao, c'è un errore di battitura nei file di esempio, devi mettere il trattino basso _ come negli altri: "rhod100_it".
[Touch Pro2, Tilt 2 Android Development] F22:
Italian Rhod 100 Key Map

It just so happens that I was working on a new keymap for the Italian Rhod 100. I'll see if I can post a new version of my rootfs package with the updated Italian and French keymaps later today.
[Touch Pro2, Tilt 2 Android Development] d_PhantoM17:
Wow!! that's all?!?!? i can't believe i wasted an entire day after this! thanks!!

tutto qui`!?!? non credevo fosse cosi` banale la soluzione XD e io che ci ho perso un giorno intero!! grazie mille :)

EDIT: the keyboard is still not fully functional. The FN works to put all the secondary letters and symbols, but it doesn't work to enable caps lock, to open the window with all the symbols, to enable xt9, to open a new sms and to go on the web.

@F22 : thanks! i really hope your edit made it fully functional!!
[Touch Pro2, Tilt 2 Android Development] F22:
*cough* There's fully functional and there's fully functional. Let me explain. You have a keyboard designed for Windows Mobile 6.1/6.5. Some keys in Windows Mobile don't exist in Android. Some of the keyboard combinations that are available on Windows Mobile just aren't available on Android. To get the same functionality in android you thus need to adapt to the android way of doing things. The symbol palette for android is also pretty minimal (just 12 characters) unfortunately. I've submitted a patch to system.ext2 to expand it to 18 characters, but most people won't see the expanded symbol palette until FRX04 is released, probably in late December. So no, you won't get everything that is currently printed on your keys even with my new Italian keymap. Your FN, Ctrl and SYM keys will work. Envelope will be mapped to SEARCH. Internet & SMS won't work because there is no way to assign that sort of functionality to a key without replacing the keycode and losing the rest of the key's functionality.

My suggestion would be to use short-cuts from within android for things like the internet and sms from the keyboard. Once your envelope key is matched to SEARCH in the new keymap you'll be able to do that since short-cuts in android combine the search key with another key. For example, by default, search+b opens up your browser, search+s opens up messaging, search+g opens up Gmail, search+e opens up email, search+m opens up the music player, etc... (These are adjustable from within Settings>Applications>Quick Launch. Personally, on my phone, I've moved messaging to Search+M and the music player to Search+P for easier use since it's awkward to press S while holding down the envelope key.) I'll look into XT9. I'm not sure about that one at the moment as it doesn't exist on my 210.
[Touch Pro2, Tilt 2 Android Development] d_PhantoM17:
OK, i understand now. I really cared about the SYM function, the rest doesn't matter so much. Thank you for explaining me!!....i wanted to ask 2 more things.

1) after i changed from :"rhod100it" to "rhod100_it" and rebooted android through the XDANDROID icon, it changed back to "rhod100it", so i have to boot android with haret.exe

after i change it. Will this problem be solved with your rootfs.img? if not, can i solve it on my own?

2)the change i made in startup.txt, made the power button not functional in android. With the power button and the home button(hang call) i used to turn off/on the screen (i changed the function of the home button in the OPTIONS and gave it the function to go back on the home page). Now i can't turn off the screen(i can only turn it on when the screen turns off by it self) unless i put the home button's function back to default. Again, will this problem be solved with your rootfs.img? if not, can i solve it on my own?
[Touch Pro2, Tilt 2 Android Development] F22:
The init script in rootfs specifically looks for physkeyboard=rhod100_it in your startup.txt. If it sees that then the Italian keyboard map & layout files will be used. If your startup.txt is being overwritten then I assume you're using some sort of startup utility. That isn't part of the rootfs. Sovereign wrote the startup utility which Reefer packages into his builds. If you're using one of Reefer's builds then you you should talk to Reefer or Sovereign about fixing that so that it works properly in the future for Italian 100's.

I wasn't aware that there's an option in startup.txt that makes the power button non-functional. How did you do that? My rootfs.img doesn't touch the power button. It operates as it normally does. It simply adds an option to startup.txt to remap the endcall button to the keycode HOME so that it not only works as home on a short press, but the ability to long press it and get the recent apps list is also preserved. (The software option in spare parts that currently exists doesn't remap the scan code, and thus the ability to pull up the recent apps list is lost.)
[Touch Pro2, Tilt 2 Android Development] d_PhantoM17:
OK thank you! i'll talk to him if i can't fix it!

You misunderstood...when i said "change in the startup.txt" i meant the change from "rhod100it" to "rhod100_it". After this change, the power button became nonfunctional...this is why i asked you...
[Touch Pro2, Tilt 2 Android Development] F22:
That's strange. Your keyboard should have no effect on the power button. In fact, you can't change the power button's functionality from the rootfs where the keyboard is handled, only the kernel. What version of the kernel are you currently running? And please post your startup.txt.
[Touch Pro2, Tilt 2 Android Development] sad0felix:
Hi both.

I guess, because all of this happened to me too the very first time I approched to Xdandroid, that if no correct value is found in startup, the default keymap is loaded.

Can't be sure but I think default is Tilt2.

Maybe Tilt2 has power/endcall ... tilted ... :P

Therefore some language could be more advanced than others in regard of testing branches/key assignments' scripts.

In this regard I am using your personalized rootfs, with endcall/power on power button and home/recent tasks on red button.

For sym I use touch keyboard, which contains all accents. Quite tricky closing and opening, but not as slow as only touch :D

Cheers

ps

I read in another thread that you might need some italian to complete/check the IT keymap.

Can I help?
[Touch Pro2, Tilt 2 Android Development] d_PhantoM17:
I'm using this kernel: htc-msm-linux @ 20101124_215731(the newest one) and this is my startup.txt:

set ramsize 0x10000000

set ramaddr 0x10000000

set mtype 2292

set KERNEL zImage

set initrd initrd.gz

set cmdline "lcd.density=240 msmts_calib=0x9f.0x39a.0x35c.0x78 msmvkeyb_toggle=off pmem.extra=1 gsensor_axis=2,1,3 force_cdma=0 pm.sleep_mode=2 acpuclock.oc_freq_khz=786432 hw3d.force=1 physkeyboard=rhod100_it"

boot
[Touch Pro2, Tilt 2 Android Development] F22:
I copied your startup above onto my phone and I'm having no trouble using the power button to sleep/wake my phone. Now granted, the first time I tried it my phone was incredibly sluggish, and several of my keys seemed to produce 2 or 3 copies of the same letter every time they were pressed. Nevertheless initial sluggishness when you replace an XDAndroid component is a common issue unfortunately. A reboot fixed that and now all seems well with your startup.txt. So it doesn't look like your startup.txt is the source of your problem with the power button. Are you absolutely certain you updated to the 11/24 kernel and not an older one? Your problem sounds very much like a kernel issue.
[Touch Pro2, Tilt 2 Android Development] sad0felix:
What about the setting Power Button Ends Call, in Settings, Accessibility?

Could that be guilty?

Maybe Americano enabled it while in berserk mode to get a solution :D
[Touch Pro2, Tilt 2 Android Development] F22:
It would still work as power outside of a phone call. Inside of a phone call you'd just have to press it twice, once to end the call, and then a second time to put the phone asleep.
[Touch Pro2, Tilt 2 Android Development] sad0felix:
Wow, I never tried, I guess sleepmode 2 is to have it stable while so overclocked ... your battery must by crying, mate!
[Touch Pro2, Tilt 2 Android Development] F22:
Updating the Italian Key Map

Well there are two defaults. First there's the keyboard entry in the default startup.txt and second there is the default keyboard if there is no keyboard entry in startup.txt. The first is either a tilt2 or a rhod210 depending on where you pull your startup.txt from. The second is the raphael (touch pro 1), that's what the init script assigns if you don't tell it anything at all about your keyboard.

Currently the key maps/layouts are a hodgepodge. People created them for their own devices, sometimes hex-editing a different model's key map binary instead of creating a source file and then compiling it. So over half the existing keymaps in the rootfs repository lack source files. And it's pretty clear that a lot of the entries were just stabs in the dark by people who didn't understand what they were doing. I'm trying to bring some order to the mess. This project would be taking me far less time if I only did my 210 and stopped there, but I've expanded the project to include all rhod & raph models that we currently have keymaps/layouts for. Currently that's 9 for the rhod & 5 for the raph. I've even created a keymap/layout set for rhodiums with broken keyboards. So make that 10 for the rhod. :p

You'll have a working SYM key as soon as I get around to updating my rootfs. The Italian and French keymaps are the only two that weren't updated in the Nov. 22nd rootfs I posted. Well they were the only rhodium keymaps that weren't. Still need to do nearly all the raph keymaps, and I haven't even looked at the kovsky keymaps yet...

Certainly. Can you post a pic of your Italian keyboard? I've already adjusted the key layout and decompiled the key map binary. I'm trying to place the same keys in the Italian map that I've added to the other keyboards. I'd like to see what's taken and what's available. We can then discuss alternate places to put those keys if the place I've used on the other keyboards is taken. I already know that fn-a which I've used for { on other keyboards is taken. On the German key map I've moved it to fn-d, but I'm not sure if that's available on your keyboard or not. According to the drawing in the manual it's available, but I suspect the drawing may be wrong since there was a ? there in the binary and I don't see the ? character printed on any of the keys in the drawing.

Preferably I'd like to pick keys that are both intuitive and available on all nine rhodium keyboards that we currently have defined within XDAndroid, and if not all, then at least the five 100's that are currently available in XDAndroid.
[Touch Pro2, Tilt 2 Android Development] sad0felix:
Yep, I wasn't clear, that's how I guessed it had to be working: no physkeyboard? Fallback set. I obviously didn't know what it was, though :D

I can imagine the mess.

And yup, I read the thread of the unlucky guy with the swimming rhodium ... and crazy keyb.

Rice is very useful in such cases. My good old E71 knows something about it.

Sure ... just wait till I get home, TP2 is great phone but can't shoot itself :P

Let's keep adherent to the standard.

Just to talk: I don't even know if it's possible to make them work in Android, but the keyb combos I miss most are CTRL+arrows, CTRL+SHIFT+arrows, CTRL+X, CTRL+C, CTRL+V.

All the rest is not very much used, really.

I'll post the picture ASAP.

Then will wait for files to update/check :D
[Touch Pro2, Tilt 2 Android Development] F22:
Rice? How did you apply your um...treatment?

Whether or not these combinations will work is dependent on the application. Android doesn't have a ctrl keycode, but many applications treat the keycode DPAD_CENTER as if it were the ctrl key. So mapping DPAD_CENTER to the scan code for the physical ctrl key gives us a functional ctrl key in many applications including terminal emulator. Four of the five Euro 100's had their ctrl keys mapped to MENU instead in their layout files however. I had to replace MENU with DPAD_CENTER to make the ctrl key work. Everyone I've talked prefers a working ctrl key, but there's probably someone out there who will scream when this change gets committed and subsequently makes it into the auto-build.

Sounds good.
[Touch Pro2, Tilt 2 Android Development] sad0felix:
LOL, don't tell me you grandma never told you this secret!!!!

Rice is very, very hygroscopic. Even more than common salt (sodium chloride).

In fact here is common to see rice mixed with salt, as a speedy remedy to keep salt dry.

Only silica sachets are better than rice, but they are very expensive or too small to fit the role here.

I bet everyone will agree that diving an electronic device into salt would not end well.

On the other side, diving an electronic device into rice grains is safe (even if some grain get into it, it's easy to shake them away when all is dried up), and clean (rice doesn't produce as much powder/dust as, i.e., wheat, that could cloak up wet stuff).

----------

My E71 falled into a river, while staying, supposedly safe, into my pocket ... ^_^

A friend pushed me in. On his defence, he didn't know I had it. Happens.

The phone is still fine, after more than 1 year after that unexpected bath.

Yup, that's sure. Never change anything unexpectedly ... or the barbarians will roll over you in seconds.

But no one forbids people to shape their keyboard layout as they like best, right?

So maybe I can help the project a little bit, while learning how to fish so to avoid just asking for fishes, if you know what I mean :D

Being able to build things on my own gives me a lot more satisfaction than taking/buying them done.
[Touch Pro2, Tilt 2 Android Development] d_PhantoM17:
i'm absolutely sure it's the 11/24 kernel. And besides.....before i changed the rhod100it in the startup.txt everything worked fine! also i have a friend of mine that has the exact same problem, and we both upgraded to the 11/24 kernel...do you know if there will be a new release soon??? it could be my only hope! it's a really weird situation...i don't know why but i have the feeling that when i'll substitute my rootfs with yours, everything is going to work out!! :D i guess i'll just have to wait until then........

yeah!! can't get to the end of the day!! is there something i can do to improve it??

EDIT

I just ran android through the startup program (since it overwrites the stratup.txt changing rhod100_it to rhod100it) instead of running it with haret.exe, and the power button works again but obviously i have a crappy keyboard :(
[Touch Pro2, Tilt 2 Android Development] sad0felix:
Improving battery life in your case is quite simple:

1) put pm.sleep_mode=1

2) eventually (if the phone starts to be unstable) do not overclock.

Don't use startup tool. It really messes up the startup.txt file with little advantage of updating system files (and this is dangerous: if something works, don't change it!!).

Create a link to haret from start or from sense shortcuts ...

-----------

Attached is the IT keyboard layout picture.
[Touch Pro2, Tilt 2 Android Development] d_PhantoM17:
OK! thanks!! I'll give it a shot!! ;)

EDIT

ok it's unstable...i guess i'll have to not overclok if i want the battery to last longer....any news from F22 ????????????
[Touch Pro2, Tilt 2 Android Development] F22:
Key Assignments for the Italian Rhodium 100 Key Map

Thanks. Ok...here is a list of changes I've made:

1) Fixed SYM key.

2) Fixed ctrl key so it behaves as control instead of menu.

3) Added startup.txt set cmdline option "b4=HOME" to remap the endcall button to home/recent apps for those who want it.

4) Mapped fn-z x c v and t to [ ] < > and ~.

5) Mapped fn-<space> to <tab>.

The above assignments match pretty closely what I've done for the other rhodium kbds.

Existing Italian keymap issues:

1) Placement of ` ---> I've assigned this one to fn-q on the other kbds, except the Nordic which has it mapped to fn-f. Fn-q was already taken on the Nordic kbd just as it is on the Italian kbd. I've told that fn-f for a quote is intuitive for Nordic speakers. I'm really not sure where to put this one. What makes sense for the single backward leaning quote on an Italian kbd? fn-d as on the Nordic kbd? fn-w so it's close to its normal position on a standard kbd? or somewhere else?

2) Placement of ? ---> All kbds except the Italian kbd have this printed on a key. The existing Italian keymap binary in the repo currently assigns it to fn-d. On the other kbd's this character is printed on either the M key, the B key, or the D key. The M and B keys are already taken on the Italian kbd by other printed characters, so it makes sense to keep it on the D key if we can.

3) Placement of | ---> Most other qwerty rhodium kbd's have the pipe symbol assigned to fn-y which is taken on the Italian kbd. The German keyboard didn't have that key open however, so it was placed at fn-r. I'm considering doing the same for the Italian kbd.

4) Placement of { and } ---> Braces assigned to fn-a and s on most other kbds, but fn-a is taken on the Italian, French and German kbds. I've already assigned them to fn-d and f on the German kbd. I could do the same for the Italian & French kbds, but I'm also seriously considering moving them for all rhod's to shift-9 and shift-0instead. This would also allow the ? to stay fn-d on the Italian keymap.