Originally Posted by arrrghhh

Oh, I see. So none of the NAND builds worked? I would've thought GBX0* is pretty much GBX0C with modifications to make it work on NAND...

No none of them worked, they all gave a kernel panic. By removing one of the audio files from the /system/lib directory (in this case libhtc_acoustic.so) it boots up successfully with everything else working.
I don't know much about Android debugging/troubleshooting and pinpointing the problem and how to solve it (yet).

When looking at the repositories I see some changes with jbrenaux regarding the audio routing but I have no knowledge how to actually use these (tar.gz) files or the content of the files.

So arrrghhh, you are fully aware of my problem now?

Thanks for reading.

[extra info]
For NAND CM7.2 (k:2.6.27) the keyboard + keys kept working, with GBX0* + 3.3.x they broke (if they normally would work that is) so switched back to the CM7.2 2.6.27 version.
Also posted a complete getlogs

Originally Posted by Alchedin

No none of them worked, they all gave a kernel panic. By removing one of the audio files from the /system/lib directory (in this case libhtc_acoustic.so) it boots up successfully with everything else working.
I don't know much about Android debugging/troubleshooting and pinpointing the problem and how to solve it (yet).

When looking at the repositories I see some changes with jbrenaux regarding the audio routing but I have no knowledge how to actually use these (tar.gz) files or the content of the files.

So arrrghhh, you are fully aware of my problem now?

Thanks for reading.

[extra info]
For NAND CM7.2 (k:2.6.27) the keyboard + keys kept working, with GBX0* + 3.3.x they broke (if they normally would work that is) so switched back to the CM7.2 2.6.27 version.
Also posted a complete getlogs

Am I aware of your problem? Yes. Do I have any idea on where to even start with fixing the issue? Not really.

Obviously you've narrowed it down to some audio issue - which, kudos for getting that far. I wish there was some more sage advice I could give you to nudge you along - but really, you'll have to start tearing into the source and trying to sort out why it's failing.

Good luck.

Originally Posted by arrrghhh

Am I aware of your problem? Yes. Do I have any idea on where to even start with fixing the issue? Not really.

Obviously you've narrowed it down to some audio issue - which, kudos for getting that far. I wish there was some more sage advice I could give you to nudge you along - but really, you'll have to start tearing into the source and trying to sort out why it's failing.

Good luck.

Going into the source is just the thing i'm not familiar with at all. Simple file replacements I can do but coding is to far-fetched for me.

Can you perhaps give a heads up to one of your might-be-interested developer affiliates with too much free time?
If there are really none, don't waste your time.

Thanks any-way's, i'll try some stuff a bit longer myself but i'm not getting my hopes up.

Originally Posted by Alchedin

Can you perhaps give a heads up to one of your might-be-interested developer affiliates with too much free time?
If there are really none, don't waste your time.

Well, if you were here about 8 months ago, you would've been right in the middle of a lot of exciting development here...

Unfortunately you are late to the party. detule is typically one of the move responsive devs on the forums here, and he made the GBX0* NAND - which is the NAND version I expected to work on your device.

Post in his thread, post logs, detail, as much info as you can muster - but make SURE all the information pertains to GBX0* if you're going to post complaints in that thread.

He might just help ya out. He's still an active developer... just not very active on this device anymore.

Originally Posted by arrrghhh

Well, if you were here about 8 months ago, you would've been right in the middle of a lot of exciting development here...

Unfortunately you are late to the party. detule is typically one of the move responsive devs on the forums here, and he made the GBX0* NAND - which is the NAND version I expected to work on your device.

Post in his thread, post logs, detail, as much info as you can muster - but make SURE all the information pertains to GBX0* if you're going to post complaints in that thread.

He might just help ya out. He's still an active developer... just not very active on this device anymore.

Damn shame I missed it. I will however gather as much info I can pull out of this device which shouldn't be too hard.
I tried the GBX0* NAND earlier which gave me the same problem (kernel panic) like any other NAND build.
What i've read about GBX0* is that it has some kind of new audio routing in it, but even with that it fails on this 'beautiful' phone.

I will try it again as soon as possible. Thanks again.

Originally Posted by Alchedin

Damn shame I missed it. I will however gather as much info I can pull out of this device which shouldn't be too hard.
I tried the GBX0* NAND earlier which gave me the same problem (kernel panic) like any other NAND build.
What i've read about GBX0* is that it has some kind of new audio routing in it, but even with that it fails on this 'beautiful' phone.

I will try it again as soon as possible. Thanks again.

GBX0C and GBX0* should have basically the exact same audio routing. The kernels are different - but I'm not positive to the extent. Obviously something is not agreeing with your device, at a very basic level - somehow your device is different from every other RHOD...

Originally Posted by arrrghhh

GBX0C and GBX0* should have basically the exact same audio routing. The kernels are different - but I'm not positive to the extent. Obviously something is not agreeing with your device, at a very basic level - somehow your device is different from every other RHOD...

Then you can imagine how frustrating my issue is, trying out all nand/kernel builds back and forth with a certain hope it successfully gets past the audio part. And every time you think it get's past it you'll see a locked [ACL] logo and that's about it.
Well on the other hand, you can see that the audio initialisation isn't fail-safe. It doesn't skip when it fails but just crashes the kernel. Reminds me of Windows Me

When i'm home from work today I will start with the GBX0* data gathering and post it in detule's thread.

Originally Posted by Alchedin

Well on the other hand, you can see that the audio initialisation isn't fail-safe. It doesn't skip when it fails but just crashes the kernel. Reminds me of Windows Me

As I previously stated many times, your device is obviously a one-off. Audio works fine on all the other RHOD's, so the code is as solid as it needs to be for all the RHOD's that participated in the testing.

Surely there's some difference with your device, so please again show a little respect to the developers. I'd like to think we've done something a little better than WinME - besides, who knows - you could even have some hardware issue with your device that's crippling it. I don't know, this is really quite strange.

As you've missed the fever of development, I'm not really hopeful that someone will swoop in and fix your issues. Good luck.

Originally Posted by arrrghhh

As I previously stated many times, your device is obviously a one-off. Audio works fine on all the other RHOD's, so the code is as solid as it needs to be for all the RHOD's that participated in the testing.

Surely there's some difference with your device, so please again show a little respect to the developers. I'd like to think we've done something a little better than WinME - besides, who knows - you could even have some hardware issue with your device that's crippling it. I don't know, this is really quite strange.

As you've missed the fever of development, I'm not really hopeful that someone will swoop in and fix your issues. Good luck.

Dear arrrghhh,

I hear you on the audio part, you repeated it many times so I get it already LOL.
You thought right, of course you guys/gals do it better. Perhaps you shouldn't have linked my funny to the developers here, how dare you! (kidding)
There was nothing bad intended to the developers here, rather I have the utmost respect for them and your contributions. If I didn't respect them why should I post here asking for help in the first place right?

But I don't think it's an hardware issue, with WinMo the device works to all it's glory and functionality. Audio playback is perfect and recording is crystal clear.
I will check what kind of audiochip is in this bad boy which perhaps makes it a little easier for the dev's.

Personally I feel this device is one of the latest Rhodium 100's created with a newer unidentified audiochip (Audience AXXXX ?) in it which wasn't able to get into the development fever as you stated.
Tonight I will take it apart and look into it closer. Nothing interesting to be seen...

[11-09-2012]
After some time of thinking I'm letting this phone slip, tinkering with the device is too time consuming for me.
Arrrghhh, if you feel closing this thread be my guest.