yashsingh1/xdaforums huggingface dataset:
[Touch Pro, Fuze Android Development] arrrghhh:
You're... kind of a moron. But I guess your sig already says it all without any need to read your post...

First, this build is listed as ALPHA. So things are going to break, there's another build listed STABLE. Might want to try that one...

Also, for the connection settings? That means you're simply getting them wrong!!! The only reason it will clear out the info is if the connection isn't valid. It's idiot-proof, it certainly did a good job of blocking you. So if the information is correct, it will save correctly... if not, the APN is "hidden", because it's invalid... unusable.

Keyboard works great for me and others. I'm not sure why it's broken for some, but there's a fix in the second freakin' post of this thread, which evidently you didn't take the time to read. Also, if you have a RAPH - why the hell not just use the physical keyboard? Again, in the 'stable' version the soft keyboard should work just fine out of the box.

Almost every app does work for me... perhaps you're just being impatient and tried to use everything immediately - I've had that cause FC's. Our port is far from finished - the phone was made for WinMo, not Android...

YouTube works great - so long as you don't try to use HQ. There's a fix for it, hopefully will make it into the next build - but again most of the attention is on FroYo at the moment.... not GB.
[Touch Pro, Fuze Android Development] RyanMogul:
Yea buddy, I am really a moron because of my signature! Least I have a signature, and an avatar, and I am a Recognized Developer that has been considered for Mod already, you have tons of posts and a horrible attitude, you will never be anything on this site other than a Senior Member, and you have never been considered for a Mod position.. So put that in your pipe and smoke it.

Why put all that time and stress into a WM phone to use for Android? Just spend 100 on ebay for a decent android phone and BOOM! Working android and nobody has to deal with your directionless absurd comments to their questions. You are the one to post builds with 10% of the build working and then get mad when people have problems.. Wait until you have working builds before you release them, also none of this is your work. You are just a copy/paster bud..

I am getting the APN settings wrong for my Carrier? Hmm, I dont think so bud, I know Cricket settings like I know the g spots of your wife, mother and sister. Here is link to confirmed settings, only worry about the end of that post where the APN settings are. I also jotted down the settings from an Actual Cricket Android Phone and they are the same. When you change the MCC to anything but default the connection gets deleted. Yet another thing to put in your pipe and smoke buddy..

Actually you are a criminal of your own crime, I said before that I already read how to get around the buggy jumbled android keyboard issue. That is using the Japenese IME, and yes I see you can download the Keyboard 8 or whatever the stupid app from the unexisting (on your posted build) android market application..

Yet again, you are a criminal of your own crime, you are not READING!! I said before that I tried everything, including a million resets, so that means android absolutely had to of finished updating its media and file stores or whatever dumb operation the linux OS performs preventing you from getting good use from your phone when you first start using it.. Apple/Mac = bunch of goofballs.

Youtube application crashes even after a million resets. Will not even start.
[Touch Pro, Fuze Android Development] RyanMogul:
Made a little progress so far so a partial appology is due.

I got the data connection to work, but so far its flakey doesnt always work. Ended up being that my phone is set to Simple IP only (PST settings) and will not work like that. My cricket market requires Simple IP but putting it on Mobile IP preffered lets it work. Not sure if it messes my connection up in WM yet but we will see.

Edit: And like I said changing the MNC value from default will delete the connection so I leave it at default 995 seems to work.

Also the Android Market finally showed up once the connection is working so that may or may not have something to do with it.

Build is decent, but am going to try the Stable version of Froyo, although I see your fine print saying stable is in quotes and that things may still not function all the time.
[Touch Pro, Fuze Android Development] arrrghhh:
Alright, I don't want to have a freakin war with you over this. All I know is I'm not a dev, I am distributing others work - but that should be pretty clear if you visit our site, www.xdandroid.com...

I guess we shouldn't have released anything until it's completely flawless? It may never get released, and will never attract any other developer attention... isn't that the point of xda-developers? It's listed as ALPHA, so I'm sorry it's not flawless. There's lots of good people working to make it better, but it's slow going as devs have real lives... I've been doing my best to help get a new build out, but there's only so much I can do...

What can you do? If you can help, please do. If you can't, sit down and enjoy what's been provided. Have a nice day.

PS - I just realized your problems with MMC/MNC are RIL related... I do apologize. There's a new RIL here... A fantastic dev, hyc has built CDMA support from the ground-up for us.
[Touch Pro, Fuze Android Development] RyanMogul:
You are right, everyone works together to get something from beta to final. Dev's, distributors, and users. I just had hoped for better and I guess I was a little ridiculous as well in my first post. You guys are doing a great job porting these new builds and making them work way decent on WM phones. Even better for the ones using NAND method. I will definately pass on my findings and help in some way with the solutions. Thanks for the info on the new RIL thing. So far so good though just leaving the MNC as the default 995. Everything works, pretty happy with the builds. I have to be more patient when something doesnt go right. Has been a flaw of mine all my life. It does have its advantages though like attention to detail and so forth.
[Touch Pro, Fuze Android Development] arrrghhh:
np, I took some cheap shots too...

Anyhoo, glad to have you on board... the new build is going to be fantastic, the new RIL is one of many improvements that are going to make things much better.

However, there's still some pieces of hardware that aren't functional yet, and obviously there's a lot of little software gremlins that we need to wrangle out. Any help is appreciated, as there aren't many devs with older devices. We've got a few RHOD devs, and some devs that keep a RAPH or DIAM kickin' around.. but there are more RHOD folk out there, and it does get more of the attention.

So the more the merrier! Hop on IRC if you want to talk moar about development. #xdandroid on freenode is where we hang out!
[Touch Pro, Fuze Android Development] babijoee:
wow, glad to see you guys finally calmed down. :p

@arrrghhh: i know it can get frustrating somtimes with many new users but everyone starts somewhere.

You are a great contribution to XDAndroid and i acknowledge when credit is due.

@RyanMogul: This isn't directly posted towards you but everyone posting on these forums, please respect all other members. Everyone has different opinions and sometimes people can disagree and flamewars can start.

Thats pretty much all i have to say at this stage.
[Touch Pro, Fuze Android Development] colinkhalid:
I have installed the Gingerbread Bundle on my RAPH300. I used the RAPH100 startup file with the following added : board-htcraphael-navi.inversion=1 and used the ts-calibration file from this thread.

I have been very impressed. I know it is an Alpha but really I have found it quite stable and will use it instead of the winmob. In fact it seems no more or less stable than win mob which I usually reset at least daily.

I have installed many apps with only the occasional crash. The Andriod OS is so much better than the clunkly winmob.

Thanks for the hard work and looking forward to any updates
[Touch Pro, Fuze Android Development] mizaa:
i'm having this problem...and I don't know how to solve it

mdp irg already on 4 4

mdp_dma : busy

(kthread+0x4c/0x78)

r6 : 00000000 r5 :d4888cc0 r4 :c006ec88

mdp irg already on 4 4

mdp_dma : busy

what should I do then??

yeaaa...I'm a noob

please somebody gimme a clear answer... :(:confused:
[Touch Pro, Fuze Android Development] arrrghhh:
I'm guessing the actual problem is the phone doesn't boot...?

Did you do the ts-calibration step?? Step5.

Pretty ironic that you ask for a clear answer, but your question is far from clear. You don't describe anything... Just some crap from the screen I assume, and "what to do"...
[Touch Pro, Fuze Android Development] HooloovooUK:
I'm trying to get this running on my RAPH300 after having success with Froyo.

It runs ok, and even turns the screen off correctly unlike Froyo. It seems to have much better power management so it doesn't run the battery down in a few hours. However, as expected it is rather more unstable.

I have installed all the incremental updates (zImage, rootfs, and initrd) in the hope that the latest versions would be more stable. It seems to have worked - it crashes much less frequently now. But the updates have killed the 3G data connection. With a stock install of the Gingerbread Bundle 3G data works fine. But after the updates it does not. Is there any known reason why 3G shouldn't work in the latest builds?

If I could just solve the data problem I might be able to start running Android permanently. I can't use Froyo due to the power management problems, but the latest build of Gingerbread seems stable enough.

Wifi works just fine, it's only the mobile data that does not connect.

Any help would be much appreciated :)
[Touch Pro, Fuze Android Development] arrrghhh:
I'd guess it's related to the new RIL. Assuming you've setup your data connection properly, that would be the only thing holding it up.

Not sure about 'production' rootfs', but the goal is to get the RIL in /system/lib, which it currently is not. I would think if you had no RIL, you wouldn't get any voice services, so maybe that isn't the issue.

Might be best to wait for the next release. We're (XDAndroid) kinda in limbo right now, trying to get a new FroYo build out.
[Touch Pro, Fuze Android Development] HooloovooUK:
Well, I haven't actually set anything up. Both the Froyo and Gingerbread bundles work with data out the box. I don't have to do anything with either.

I've even tried installing the bundle, checking everything works, and then installing the latest incremental updates. With no changes in settings data goes from working to not working following up the update. Although I have checked the data settings, and nothing seems to be wrong.

Yes, voice works fine.

Fair enough. I'll keep an eye out for new releases.

I see now that there is already a thread on this problem, so my apologies for the duplication.

Thanks for your help :cool:
[Touch Pro, Fuze Android Development] arrrghhh:
Then I'd say revert the rootfs. I can almost guarantee that file update is the culprit. Figure out which one it breaks on, I'd bet a dollar it's the RIL update ;).
[Touch Pro, Fuze Android Development] HooloovooUK:
I tried a fresh install of the Gingerbread bundle, and before booting I copied in the latest initrd and zImage. I'm not sure if that's the best way to do it, but it feels the right way compared with booting and letting it set everything up and then copying in updates.

I now get a 3G icon and it seems to be trying to transfer data, but it still can't connect to anything. The APN looks correct. Additionally, once the phone goes in to standby it never comes out again. Oh well.

Will the new Froyo release have the Gingerbread power management that seems to work on my Raphael? Or is that something specific to Gingerbread?

I guess this means I'll just have to go out and get that Galaxy S2 :D
[Touch Pro, Fuze Android Development] arrrghhh:
No clue how to respond to this, other than enjoy your SGS2.
[Touch Pro, Fuze Android Development] krish_nank:
Startup .txt

Sorry added more information in my second post
[Touch Pro, Fuze Android Development] krish_nank:
I am also stuck at same screen ...

also tried htc-msm-linux-20110214_200559-package kernel

Tried hard resetting the phone and formatting the SD card...

Any one have startup.txt for raph410. My problem unable to complete first boot process.... waited for more than an hour...

Stock ROM -RUU_Raphael_hTC_Asia_WWE_5.07.707.2_Radio_Signed_R aphael_52.58.25.30_1.11.25.01

Using the same kernel provided with package...

tried both raph100 and 110

using non 3G handset.... the ROM details are mentioned as above.

8gb SDcard formatted with fat32
[Touch Pro, Fuze Android Development] arrrghhh:
RAPH410? Are you sure!!? Because that's yet another new RAPH if so. I already have to add info for RAPH300...
[Touch Pro, Fuze Android Development] krish_nank:
Its not new bro...its an old one already googled about it once user called madnish has asked same startup file no one answered him.....
[Touch Pro, Fuze Android Development] arrrghhh:
Well no the RAPH isn't new, but the device is to our project. I've never heard of it, hence no startup.txt.

Confirm that's the model number please.
[Touch Pro, Fuze Android Development] krish_nank:
lol i am not newtoo raphel at least double confirmed.... both at boot loader and below the battery...

just for your reference

http://xdaforums.com/showpost.php?p=7144101&postcount=36
[Touch Pro, Fuze Android Development] arrrghhh:
Well you're the first with a supposed 410 to report issues... so my count is "2". I don't remember that other dude's post, but to be fair it wasn't in any of my threads.

Sounds like you're SOL. Is the device GSM?
[Touch Pro, Fuze Android Development] krish_nank:
Thank you for having patience in helping me out bro........

after lot of searching i got to know what mistake i did.

I haven't formatted SD card as primary because of which i was getting message as failed to mount sd card, cannot continue then i use to get the other some busy message stuff.

below tool easy to use for formatting sd card.... i used Raph110 startup.txt and succeeded up to 90% now

http://www.partitionwizard.com/download.html

Using

set ramsize 0x10000000

set ramaddr 0x10000000

set mtype 1910

set KERNEL zImage

set initrd initrd.gz

set cmdline "lcd.density=210 clock-7x00.a11=500 msmvkeyb_toggle=off gsensor_axis=-1,-2,3 board-htcraphael-navi.wake=0 physkeyboard=raph"

boot

for startup.txt from

https://sites.google.com/site/androidport/faq
[Touch Pro, Fuze Android Development] arrrghhh:
That FAQ is ancient and outdated. There's an FAQ in the first post.

Is that the RAPH100 startup? I see at least one deprecated command, and no pm.sleep_mode...

Edit - just wondering which one did work, keymap-wise - do all the keys work with the RAPH100 startup? If so I can just copy that one and add a RAPH410 folder. Pretty much what I'm doing for RAPH300 ;).
[Touch Pro, Fuze Android Development] krish_nank:
Have few issues.... i am very new-bee to work with android on touch pro... whenn i slide out key board phone freezes some time i have to reboot again. Some times phone doesn't wake up...... about command lines i haven't learned much.

hardware keyboard working..fn, shift, shift doesn't work

startup.txt used as above said

set ramsize 0x10000000

set ramaddr 0x10000000

set mtype 1910

set KERNEL zImage

set initrd initrd.gz

set cmdline "lcd.density=210 clock-7x00.a11=500 msmvkeyb_toggle=off gsensor_axis=-1,-2,3 board-htcraphael-navi.wake=0 physkeyboard=raph"

boot
[Touch Pro, Fuze Android Development] arrrghhh:
Not sure about the freezing, but perhaps stick to FroYo. GB isn't so stable...

As for the keyboard, have you tried any different physkeyboard's?
[Touch Pro, Fuze Android Development] Sev3rus:
what about project progress ?
[Touch Pro, Fuze Android Development] arrrghhh:
GingerBread hasn't made much lately, at least not publicly. There has been some work on the codebase, but there's going to be some work to get all of the patches in FroYo up to GB.
[Touch Pro, Fuze Android Development] drugusv:
help please: with system.ext2 from 25.03.2011, and initrd-20110429-a3eace0.gz and

with kernel from 17.10.2011 on my raph100 i cant start wifi, all time it say "ERROR". i tried many kernel modules but no result. tell me please what combination of this modules i must to make to start wifi?
[Touch Pro, Fuze Android Development] arrrghhh:
Sorry this Gingerbread build is old. If you're using a new rootfs, it might not work. Have you tried FRX07.1? Wifi should work fine there. We're hoping to have a new GB release soon.
[Touch Pro, Fuze Android Development] drugusv:
:(

:( yes i tried FRX07.1, work fine. but, i want to try GB. i read in forums about GB work faster than FR.

i will wait changes for GB :)
[Touch Pro, Fuze Android Development] MAJID_TAEBI:
Hi,

my device is raph 100...

i m using this Bundle.but after 30 sec screen locked and i cant unlock screen.i tried every buttons.... how to unlock???...!help me...
[Touch Pro, Fuze Android Development] arrrghhh:
This build is pretty old. Please, use FroYo or GBX0B.
[Touch Pro, Fuze Android Development] nightcrawler218:
Should I remove the sim card when I run HaRET.exe or install the android for the first time in my phone...?
[Touch Pro, Fuze Android Development] PojntFX:
Sorry gor OFF TOPIC, but IS ANYBODY interrested in iOS 7 (Niro OS) For this.ROM?

Its working on HD2 for now but I will do a special build for this device if anybody Like it. Link is in my Profile
[Touch Pro, Fuze Android Development] axe_1337:
You mean IOS for touchpro??

Would love to see it :eek:, it's sad that the touch pro isn't worked on anymore.
[Touch Pro, Fuze Android Development] PojntFX:
Ya thats what I meant.
[Touch Pro, Fuze Android Development] CrashingDutchman:
What version should this be? My phone says: Android 2.3.1, is that correct?
[Touch Pro, Fuze Android Development] arrrghhh:
2.3.1 is correct. I think 2.3.2 is out, not sure if AOSP code is available yet for it or not...
[Touch Pro, Fuze Android Development] Mr.Sir:
Mine just hangs shortly after entering deep sleep and gets really hot. :confused: I downloaded and used everything that came with the simple package on the first page. I got a normal GSM europe Raphael.
[Touch Pro, Fuze Android Development] R^7Z:
Does this reoccur every reboot? Have you attempted to delete the file called data.img and let the system recreate it? Have you attempted to use the newer kernel package from Glemsom's site? Additionally, which RAPH model is the GSM/europe? (HINT: I have an at&t Fuze and it is a RAPH110) :)
[Touch Pro, Fuze Android Development] arrrghhh:
What is your sleep_mode set to?
[Touch Pro, Fuze Android Development] McFlyH:
Camera not working on raph100 kernel 1258.
[Touch Pro, Fuze Android Development] R^7Z:
Camera testing still in progress

Camera code has not been committed yet. In the meantime, if you'd like, there is a camera testing thread HERE

You will need some basic understanding of ADB in order to be helpful. It is also strongly suggested to read the first post several times so you understand what is being asked of you.

:cool:

n-Joie! (Enjoy)
[Touch Pro, Fuze Android Development] McFlyH:
In first (and second) post has not any world about camera
[Touch Pro, Fuze Android Development] R^7Z:
I noticed that as well however, I have no control over this thread. I can only make suggestions and assist in that manner. I'm guessing it was decided to not make mention of this due to the previous continuous testing or it might have something to do with him being human ( yes, I am j/p, arrrghhh is actually a robot :D ).

For everything else, you will have to wait till the threadOP wakes up and responds. Till then, you have that thread to mull over :)

Might I also make one other suggestion, please do not ask just to ask as there are many testers in there and for other devices and they really want the same thing as you, thanks! :)
[Touch Pro, Fuze Android Development] arrrghhh:
Heh, sorry I didn't mention the camera.

I actually wasn't sure if it would work or not, I'll adjust the post and state that it doesn't...

I assume you're running the cam testing kernel and all the necessary libs for cam? Again, I haven't tested it myself with GB. Plus I only have a RHOD to test with... I'm just waiting until the cam code is in the mainline kernel personally.
[Touch Pro, Fuze Android Development] R^7Z:
Yeah yeah... The likely story! ;) :p

I kind of figured you meant to leave it out since the testing was only dealing with FroYo for the moment. At the very least, it might help the dev of that thread a little by keeping it centralized with the FroYo build(s) and devices. Perhaps should've checked with him to ensure it was kool to send some GB testing first but oh well! :D
[Touch Pro, Fuze Android Development] xtremists:
i dont know why froyo is slow than gb

evn froyo is much stable now and gb is just for testing and its work great

wifi working awesm speed more good then froyo no lags

jus waiting for battery fix :)
[Touch Pro, Fuze Android Development] arrrghhh:
Battery fix? Not sure what you mean. There's a lot of things wrong with the battery...
[Touch Pro, Fuze Android Development] R^7Z:
I NOMinate arrrghhh to fix the battery! :p

On that note, anyone heard from Camro lately?
[Touch Pro, Fuze Android Development] xtremists:
actually m saying battery is getting drain quickly so is there anyway to increase well m sure developers must b building something for this

i installed keyboard for this version gingerbread keyboard posted in this thread its the same :S
[Touch Pro, Fuze Android Development] arrrghhh:
Lots of things to fix on battery, even for RHOD. Although on RHOD we are getting much, MUCH better battery life now that we're correctly collapsing the panel. Lots of crap to still sort out, as now we're having issues with the panel waking correctly :p.

Hopefully that code can eventually be extended to RAPH/DIAM devices, I know our battery life skyrocketed when we were finally able to correctly collapse the panel.

So until that happens, not much will really change with battery life, sorry... Not many devs have the DIAM or RAPH...

As for the built-in keyboard being tiny stinebd is fixing that in the next version. He also has the g-sensor fixed, but he wants to fix gapps before the next release. Stay tuned!
[Touch Pro, Fuze Android Development] R^7Z:
For the time being, you will need to select it to display the GB keyboard
[Touch Pro, Fuze Android Development] xtremists:
thnkxx alot man well m hoping for nand release

well this is also ok if someone increase the battery life then its awesm winwo is kinda freaky eats lot of ram no fun andriod is cool
[Touch Pro, Fuze Android Development] Maxi21066:
idk about the battery life but for me it last all day when im at school. the only thing i didn't like is the g-sensor not working but, since you guys got that fix then its perfect (and it is more stable than froyo). I can care less about the camera now.
[Touch Pro, Fuze Android Development] Eligos4ever:
Thanks for all the hard work guys.

I'm getting the split screen effect like you see half of the screen vertically.

Do you guys have this fixed in the next release?

Thanks!
[Touch Pro, Fuze Android Development] arrrghhh:
That's a kernel bug that only effects the CDMA RAPH/DIAM's. What kernel are you on? This *should* be fixed on the newest kernel, if not I know it's fixed in 1258.
[Touch Pro, Fuze Android Development] Eligos4ever:
All I installed is the download in the first post of the thread. The kernel that's included is what I'm using.

Thanks for the heads-up.

What date is the 1258 kernel? I'm on Glemsom's site.

Update: using htc-msm-linux @ 20110222_203532 and so far, all is well. Boy is this GB fast on my phone.
[Touch Pro, Fuze Android Development] arrrghhh:
htc-msm-linux @ 20110214_200559 is 1258. Can you try with the newest one, 1262? I'm curious to see if the issue came back.
[Touch Pro, Fuze Android Development] Eligos4ever:
See my post update.

Just curious, where does it say 1258 on Glemsom's?