yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] walter79:
I use different Keyboard layout file for my Rhodium 100 DE.

I use the Xandroid files.

Should i make a update.zip for easy switch the keyboard layout?

With xandroid layout i have home button on my callend button.

EDIT:

Some bad code in 16.jan. build

14:19:49.815 Error Libacoustic-wince 84 Failed to open /sdcard/AudioPara3.csv. Error Permission denied (13)
14:19:49.816 Error Libacoustic-wince 84 Trying with default file
14:19:49.816 Error Libacoustic-wince 84 Successfully opened /system/etc/AudioPara3.csv

14:20:02.128 Debug gralloc 132 UPDATE_ON_DEMAND supported
14:20:02.128 Debug libEGL 132 loaded /system/lib/egl/libGLES_android.so
14:20:02.254 Debug libEGL 132 loaded /system/lib/egl/libGLES_qcom.so
14:20:02.254 Debug EGL.oem 132 system process, deny GL context
14:20:02.255 Error libEGL 132 No EGLDisplay for hardware EGL!

14:20:13.022 Error EventHub 132 could not get driver version for /dev/input/mouse0, Not a typewriter
14:20:13.022 Debug dalvikvm 132 GC_CONCURRENT freed 140K, 40% free 4516K/7431K, external 0K/0K, paused 10ms+10ms
14:20:13.022 Error EventHub 132 could not get driver version for /dev/input/mice, Not a typewriter

14:20:22.695 Error GpsLocationProvider 132 no AGPS interface in agps_data_conn_open

14:21:01.214 Error QualcommCameraHardware 84 filterPictureSizes enter~!!
14:21:01.215 Error QualcommCameraHardware 84 filterPictureSizes MT9T013!!
14:21:01.215 Verbose QualcommCameraHardware 84 preview_size_values.string() = 800x480,640x480,480x320,384x288,352x288,320x240,240x160,176x144
14:21:01.215 Verbose QualcommCameraHardware 84 picture_size_values.string() = 2048x1536,1600x1200,1024x768,640x480
14:21:01.215 Verbose QualcommCameraHardware 84 antibanding_values.string() = off,50hz,60hz
14:21:01.215 Verbose QualcommCameraHardware 84 whitebalance_values.string() = auto,incandescent,fluorescent,daylight,cloudy-daylight,twilight,shade
14:21:01.215 Verbose QualcommCameraHardware 84 effect_values.string() = none,mono,negative,solarize,sepia,posterize,whiteboard,blackboard,aqua
14:21:01.324 Verbose QualcommCameraHardware 84 native_get_maxzoom E
14:21:01.324 Debug QualcommCameraHardware 84 ctrlCmd.value = 29
14:21:01.324 Verbose QualcommCameraHardware 84 native_get_maxzoom X
14:21:01.324 Debug QualcommCameraHardware 84 Maximum zoom value is 29
14:21:01.324 Error QualcommCameraHardware 84 Failed to get maximum zoom value...setting max zoom to zero
14:21:01.324 Debug Videos 549 youtube.core.transfer.TransferService.restore:152 restored 0 transfers
14:21:01.325 Error QualcommCameraHardware 84 setParameters: E params = 0x2b5b8

Complete LOG:

http://pastebin.com/20aYCz2f
[Touch Pro2, Tilt 2 Android Development] [ACL]:
Nope, the early errors on acoustinc are actually supposed to be there. We share code with xdandroid here and they load the csvs from sD card while we load from /system. So by default the lib checks sd first. I'll propose a compile time variable to the team so we can try to change this error.

14:20:02.254 Debug EGL.oem 132 system process, deny GL context
14:20:02.255 Error libEGL 132 No EGLDisplay for hardware EGL!

This is normal

14:20:22.695 Error GpsLocationProvider 132 no AGPS interface in agps_data_conn_open

Gps was not deployed with this build.

And rhod100 has cam issues. They will be fixed later.

Thanks for the feedback and no need to make an update. I included the DE layout but by default UK is installed. I havent decided yet but i may have the recovery have the ability to change the kb layout.
[Touch Pro2, Tilt 2 Android Development] [ACL]:
Anyone around to test the h2w(usb style) headset on a gsm rhod? We have an issue with cdma, just want to know if GSM is affected as well. We need to make sure the Mic is working.
[Touch Pro2, Tilt 2 Android Development] josephbrien:
I Have a question,

Can the android keyboard looklike on froyo build? because its bigger.

i dont wanna slide back n forth the unit because of the flex. :)

Thank you.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
There's tons of aftermarket keyboards on the Market. Look for hacker keyboard, or Swype.
[Touch Pro2, Tilt 2 Android Development] josephbrien:
usb headset gsm seems working fine. voice search recognizes what I'm saying.

rhod100

BTW,

can I custom calibrate the screen? it's kinda off
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Reading the first post does wonders:

Also, run the headset thru the full gambit. Phone calls are going to be the most important part here - but I kinda thought that would go without saying.

You're also on the newest build, correct?
[Touch Pro2, Tilt 2 Android Development] josephbrien:
Yup. I'm on the newest build.

Ok will test phone calls later and the "full gambit?" its 3am here.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Last I checked I didn't ask you to stay up until 3am...:rolleyes:

By full gambit I mean try every scenario you can think of with the headset. Phone calls mainly, but plug/unplug in the call, put it on speakerphone and plug it in, try every scenario you can think of - see if you can get it to fail. If you can't, great!
[Touch Pro2, Tilt 2 Android Development] [ACL]:
Thanks for testing.
[Touch Pro2, Tilt 2 Android Development] 4dn4n:
Rhodium 100, the dial tone is still a problem, the first call is ringing. Sound does not play the next calls. speaker is crackling.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Logs please.
[Touch Pro2, Tilt 2 Android Development] milda25:
I haven't problem with this on my Rhod100. Are you on latest build? Have you started from scratch? This build has also new LK. Have you flashed it?
[Touch Pro2, Tilt 2 Android Development] PoXFreak:
I assume this is a NAND build that is mostly working with a few bugs, correct?

What is the known issues thus far, and how can I help?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
By... testing?

There are a few bugs still outstanding. Help us find them! There are some well-known bugs that exist on HaRET and NAND. There are a handful of bugs that only exist on NAND and actually there's some bugs that exist on HaRET that don't exist on NAND.

It's kind of a hodgepodge as you can tell. Search is always your friend, and ACL has a semi-exhaustive list that spans the first 2 posts.

So did you get a TP2 dude? This is RHOD-only. If you're still on the RAPH, I'm sure those users would LOVE if you could get it working on that device - but this won't be a straight flash to the RAPH. You're gonna have to get a little dirty to get it workin... I'm sure ACL would be willing to provide some guidance.
[Touch Pro2, Tilt 2 Android Development] 4dn4n:
How can I get log file?

Yes, I installed the latest version. I get the same errors as in previous versions.

Other features works great.
[Touch Pro2, Tilt 2 Android Development] intergon:
Use this app: [APP] GetLogs - Get dmesg, logcat, radio, etc with one click!
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Indeed.

If you want to learn moar, http://xdandroid.com/wiki/Logs.

If you don't, just use GetLogs ;).
[Touch Pro2, Tilt 2 Android Development] josephbrien:
GoodMorning.

So far I don't have problems on the usb headset.

On the unit, One time I only hear is static noise coming from the back speaker when

I answered the call. bug is gone when i restarted the phone.

this just happened once.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Did you get logs of the noise coming from the back speaker?

That's a sure-fire sign that you lost all audio.
[Touch Pro2, Tilt 2 Android Development] randomblame:
Its working great on my wife's rhod300 a couple of things:

In recovery the power button is usually enter it freaked me out for a minute

Gallery is garbled in landscape

End call really should be mapped to home or use the ptt button

A cyanogenmod style settings/performance menu would be very shiny

Live wallpapers broken

That's it for now. This poor rhod barely lived to see the day haha it got drenched in an energy drink last month and its been dropped thousands of times springs are sticking out the slider rails and the USB port is barely making a connection anymore.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Power isn't used :confused: You use send call for enter. Use CWM recovery too... it's much better IMHO. Works much better for me at least!

If you start it in landscape, it's fine. Same thing happens with Google Maps... I think this is all related to the GLES problem.

I think end call should = home as it does in XDAndroid. You forget, only the RHOD300 has a PTT button. No other RHOD has such a button.

With that said, a way to remap buttons easily would be very nice... Not sure how that is achieved on native devices - probably not easily? :confused:

OMGB is pretty much AOSP. There's a CM7 build, but it's pretty slow. Hoping ACL takes another crack at it, but CM is kinda bloated.

They'll just slow down the phone... also see the GLES problem I mentioned earlier, it's almost certainly related.
[Touch Pro2, Tilt 2 Android Development] randomblame:
Cm7 isn't really bloated other than adw which I push to it anyways. Usually remapping the keys can be done in key layouts in /system/usr but it didn't work when I tried it. In recovery end call is enter but on 99% of other devices power is enter so it threw me off. Cwm would be better good point there. There is definately a weirdness with gralloc or Gles not a big deal though all in all its a great build. Still using .27 kernel are the newer ones going to be adapted for nand?
[Touch Pro2, Tilt 2 Android Development] randomblame:
also yaffs is so 2008 can't we get some ext4 love up in mere
[Touch Pro2, Tilt 2 Android Development] boggsie:
Do you use (only) the version on the google code page, or can it work along with the version from market or the neopeek version?

Best regards,

-boggsie
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
CM is kinda bloated. Look at the source if you want to change keymaps, I can't find it right now. Send call = enter on CWM. End call I think just turns off the screen... Most native devices don't have send/end buttons dude. wth.

CWM works great, use it all the time. The AOSP recovery is... well, just not as powerful, and doesn't work so well IMHO.

GLES will get fixed, in time. I've been buggin ACL about it.

Newer kernels might get adapted, but who cares? .27 is actually faster than any .35+ kernel that I've tested, and everything works on .27... I don't really care what kernel is used, so long as it works...

LOL why would you put a journaled FS on a NAND flash chip? That's dumb, and probably dangerous.

I only use the CWM version from the Google Code page. I'm not aware of any CWM versions on the Market (how would that even work? :p) and neopeek's version is certainly not going to work, lol. That's setup for SD card installs...
[Touch Pro2, Tilt 2 Android Development] boggsie:
You are right. It is Rom Manager and once you get it installed from the market, you can, at that point, install CWM from within Rom Manager.

So the question turns to: How to get the CWM version from the Google Code page available through Rom Manager? That is what I was trying to originally express / ask.

Best regards,

-boggsie
[Touch Pro2, Tilt 2 Android Development] randomblame:
Ext4 isn't dangerous for nand as long as there is a controller in front of it doing wear leveling

a lot of new devices use it I'm using it on my inspire which I've flashed zillions of times. Older nand is more resilient anyways I'm sure it would live lol. Google set ext4 as the recommended default for 2.3+ is this thing using emmc or is it just raw nand? Doesn't really matter just my 2 cents

One last thought for now since most rhods are no longer in use as primary phones why not make a "drawer phone edition" with a default over clock and lots of possibly destructive features haha I know there isn't much development time to spare on such trivial things these days just throwing it out there I have 3 other devices I'm working on and no time for rhod so I certainly don't expect anyone else to either.
[Touch Pro2, Tilt 2 Android Development] hashtowent:
how about rhod100?

any progress? [can it be used "staple" for calling and sms? (not to miss calls as no ring, not shown etc) ]

how about flashing w/o adb? (can someone .nbh this?) -> no need for diffiuclt fastboot and adb would be precious!
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
What's the point? We don't have a native Android device, so that would probably just break things horribly. What are you missing that ROM Manager provides? It's not like we have 15 different choices on ROM Manager to flash with lol.

How about RHOD100? No devs have one. ACL has literally supported this device "blindly" for a long time now.

I don't know what your issues are, but clearly describe them. Staple for calling? Staple for SMS kinda makes sense, you mean MMS/pic mail? That should work great.

Not to miss calls as no ring is a general issue, make sure the phone is on 'vibrate always'.

Flashing without adb will come when it's stable I'm sure. No point now, since things change so frequently. Suck it up, this is still clearly in TESTING!!!
[Touch Pro2, Tilt 2 Android Development] hashtowent:
i know its for testing purpose but i have no experience with adb nor with fastboot. so i can't test it and bugreport =( i suppose thats matching many rhod100 owners (mostly german people?)

with a detailed help for setting adb and fb up i could start experimenting ;)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
It's already in the XDAndroid FAQ. If you have adb setup, fastboot comes with it (unless you're on Linux).
[Touch Pro2, Tilt 2 Android Development] hashtowent:
BUGLIST RHOD100: To Be updated for later builds

Hello, thanks acl, thanks arrrghhh!, thanks to all other who helped on this!

Now here's whats wrong atw:

SCREEN: Not perfectly accurate borders [ can't press open appslist (with zeamlauncher) directly over scrollbar no real issue]

YOUTUBE: Keyboard/Frontkey backlight stays on!

Battery: inaccurate [ known]

OSK: very tiny, not useable atm (w/o stylus)

MP3: NO ARTIST but plays

Great:

WIFI Works (wpa2) great

sms

email

launcher

Speedstepping 245/745

titanium launcher

ROOT

YOUTUBE (HQ)

SOUND

GOOGLE-SYNC

MARKET APP

MP3-Playback

SD-CARD

Speaker (music, calls)

3G- mobile data (apn setup etc automatic!)

untested:

calling

gps

bluetooth

browsing

headset

malfunction/unstaple:

camera (max. one picture then freeze with 2nd capture)

flight mode (no more network till reboot!)

HANG UP via button doesn't work with german layout!

AT ALL: Great improvement compared to sdcard images! kepp the stone roling!

Now running on battery from this morning, normal usage for me, still left with battery ( no shutdown forced till now, telling of 87% [can't be true but thats known])

seems staple so far for the most important functions
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Cam won't work for RHOD100.

LED indicates sleep/wake state.

There is no right LED, lol. That's a sensor.

If the calibration is off, use the calib app. See the first post.

Artifacts will hopefully be resolved soon. Working with ACL on those.
[Touch Pro2, Tilt 2 Android Development] walter79:
german rhod 100 keymap files View attachment 870880

home = end call

I will test the new gps.rhodium.so

Edit:

GPS works now. http://code.google.com/p/rhodium-nand/downloads/list

Sygic 11 GPS Navigation work now.

Big thanks.
[Touch Pro2, Tilt 2 Android Development] hashtowent:
How about navigation itself? is it useable of more lagging especcialy the voice/ map dispatch (position?)
[Touch Pro2, Tilt 2 Android Development] [ACL]:
Right now you cant. Rom manager only supports the official of roms. We arent officially supported by cyanogenmod so there is no official code posted on rommanager for download.
[Touch Pro2, Tilt 2 Android Development] [ACL]:
Its not so simple. You nee to look at the big picture here. Lets say we support ext4 on the kernel, then we need to make sure the bootloader is also able to write ext4. Right now it does not.
[Touch Pro2, Tilt 2 Android Development] [ACL]:
I try to work with Emwe a lot on our patches. .35 is actually very good candidate for nand, but i'm not too sure if we will benefit much from it. Maybe if we decide to venture into ICS.. who knows. Also the next kernel i put out has OC all the way past 800mhz for those animals who really want to push the limits..lol
[Touch Pro2, Tilt 2 Android Development] [ACL]:
No, the whole point of going to nand is to become an android device. So if you want nand, you need to learn adb/fastboot.

BUT !!!. when we finally release a stable rom, we will be able to use the native android flashers over usb. So stayed tunned for that.
[Touch Pro2, Tilt 2 Android Development] mbellot:
ACL - Silly question, but is the phone OC'ed in any way by default?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
No, you have to use SetCPU or some such app to overclock.
[Touch Pro2, Tilt 2 Android Development] mbellot:
Thanks! That was the answer I was hoping for... :D
[Touch Pro2, Tilt 2 Android Development] randomblame:
Ics is what I had in mind I have it booting on pandigital novel with 256mb of ram and an 800mhz armv6-vfp without 3d/2d acel and its decently speedy this is with the stock 2 6.29 kernel that was tailored for eclair. Those animals at pandigital refuse to release kernel sources so I had to patch the input stuff to work with the old kernel and the resistive screen point is it works even got wifi working but internet permissions seem to be broken at a kernel level ping from a privileged terminal works but the only app or browser with internet access is opera mobile I think its a lack of ipv6 support or the data usage monitoring - I don't know but the point is rhod has kernel source it should be a slam dunk for basic functionality and a fun project
[Touch Pro2, Tilt 2 Android Development] hashtowent:
i did learn it ;) using my rhod with android now.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Uhm... we don't have any kernel source, other than the stuff that was baked internally.

ICS boots, it's just an atrocious experience.
[Touch Pro2, Tilt 2 Android Development] randomblame:
Obviously argh the home made kernels are fine they work well and can be modified whereas in my novel port I'm stuck with the stock kernel and have to modify userland .

A fun project is not nessicarily a useful one. Did you get jit working because that made a huge difference in usability in my port. A few million tweaks and rhod could have 3d and 2d acceleration in the UI which would really speed it up too whereas my novel port could never have that anyways im going back to sleep
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
lolwut

First, JIT has worked for a loooooooooong time. Our arch can't take full advantage of it seemingly, because it causes lots of problems and slows down the system - so what's the point?

Second, 3d acceleration works, but it'll never work in the UI unless we go up to ICS.. You should know that.

Sigh... I say put up or shut up. You keep talking about all these things you want to do for RHOD - well do it! All our code is available. No point in speculating about it.
[Touch Pro2, Tilt 2 Android Development] randomblame:
You just keep misunderstanding lol when my wife's rhod is retired I'll start playing with it should be in a few weeks.

The jit thing: Ics doesn't support armv6 j or vfp without patching it and the only working jit implementation for armv6 that I've seen on Ics was on tom3qs unoficial Spica build and my novel build that's why I asked, I didn't realize jit causes issues on rhod is that due to a lack of vfp?

The 3d accel point: I was talking about Ics
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
ICS probably won't work, unless someone figures out how to get an adreno130 or msm7200/1 to run it...

I don't know what the technical issues are around JIT. It just caused wacky insane issues on FroYo - like if you spammed the volume up/down while in call it would reset. Plus, it was slower... so there was no point.

Again, I don't *think* our arch can take advantage of JIT. I'm by no means an expert on the subject tho.
[Touch Pro2, Tilt 2 Android Development] randomblame:
hmmm are the adreno 130 libs open or closed source? I'm putting together an initial test build right now but I won't be able to test it till the wife gets her upgrade - she said if I screw with her phone anymore she'll stab me haha anyways I've got init.rc modified to work with ics and I'm cooking the dream system.img up at the moment - I'll compile once I figure out which libs work and I have a device to actually test on.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
No idea, but most Qualcomm stuff is very closed.

Good luck.
[Touch Pro2, Tilt 2 Android Development] randomblame:
finished building it - aparently the dream/saphire builds are compiled for armv5te - this is going to be SLOW

I'll upload it to mediafire if someone wants to test it who can actually pull me some logcat output pm me

I'll stop cluttering up this thread

*edit

Looking at the device tree in boardconfig.mk I see:

# Let's get some speed by default now.

WITH_JIT := true

JS_ENGINE := v8

So... I'm confused hehe
[Touch Pro2, Tilt 2 Android Development] ryannathans:
I really doubt that camera is fully functional.

I am going to try this out tomorrow! Looks awesome, great work.

I have almost never had a working camera in android, i'm currently on gbx0b with a 3.0 kernel.

There was a V3 cam testing .27 somewhere but that's that only time it ever worked.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Jeebus dude, you have a RHOD1XX - therefore your cam doesn't work.

Please, you know this. Cam is fully functional for everyone else... Again, you freakin know this.
[Touch Pro2, Tilt 2 Android Development] Paco_marine:
wifi won't turn on

I just flashed it, but the wifi doesn't turn on, what can I do to fix it?

Regards.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Haven't heard of this on NAND.

Please post some logs. Reboot, turn on wifi, it fails... then pull logs immediately. The less you do the better basically.
[Touch Pro2, Tilt 2 Android Development] Paco_marine:
I have RHOD210, I did a fresh install.

In first boot I settled down the phone to charge everything then I reboot.

After this I turn on the wifi, but it stuck in "Turning on". not matter if I want to do it in the first boot or after reboot.

You talked about logs, how can I take out this logs in android?

Thank you.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
You're in a testing thread...(in a development section) and don't know how to pull logs? Shame on you :p.

http://xdandroid.com/wiki/Logs
[Touch Pro2, Tilt 2 Android Development] ryannathans:
There was a fix posted, it worked flawlessly from what I tested, about 50 photos.

I was hoping it was integrated.
[Touch Pro2, Tilt 2 Android Development] igor45:
[Q] Installing LK

...does LK absolutely have to be installed via SDcard or is there a way from USB/RUU?

Only 4GbHD card here & bootloader does not like it.
[Touch Pro2, Tilt 2 Android Development] mbellot:
Try reformatting it with one of the tools argh recommends.

I had two identical 1gb cards, one that wouldn't work and one that did.

Reformatting the "bad" one with the HP utility was all it took to get it working.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Considering that guy never actually made a patch? No.

We've tried to pick it apart, but I don't think anyone has given it a lot of time - not many really understand the cam code. JB did, and we tried to enlist his help... but he's been very busy lately.

Unfortunately that brinka guy that made the patch never really seemed to care about actually making it worthy for main-line. Trust me, it was a battle just trying to get him to compile & run his own kernel... Was quite ridiculous.

Heed mbellot's words. The card must be formatted FAT32.

Copy all the data off the card, do a full FAT32 format with the HP Tool, copy the data back and you should be good to go.

Unless you feel like fixing the bug with not being able to flash via USB ;).