yashsingh1/xdaforums huggingface dataset:
[MDA III, XDA III, PDA2k, 9090 ROM Development] d-two:
Current Kernel Status

With default battery...

I don't want support haret in the future! But with HTC-Flasher you can restore WM without lose your data ;)
[MDA III, XDA III, PDA2k, 9090 ROM Development] TheAH:
Ok, cool!

What do you mean by reverse engineering the camera driver?
[MDA III, XDA III, PDA2k, 9090 ROM Development] gbl08ma:
Put simply, it's basically looking at the camera driver we have for Windows Mobile and "read" it to find any clues about how the camera works and how to write a Linux driver for it.
[MDA III, XDA III, PDA2k, 9090 ROM Development] d-two:
It sounds so simple :laugh:
[MDA III, XDA III, PDA2k, 9090 ROM Development] gbl08ma:
Yeah, I know I made it sound easy, I wanted to make sure he understood :)

I had my own reverse engineering adventures too, I know how hard it is...
[MDA III, XDA III, PDA2k, 9090 ROM Development] notime2d8:
I remember seeing a USB driver for the camera that I think can be changed to work with i2c but...the i2c is on the ATI chip which we have no info on...?
[MDA III, XDA III, PDA2k, 9090 ROM Development] TheAH:
Well I'm not a derp, so you don't have to put everything so simply. I have not been working on Dev'ing since 2 years ago :P.
[MDA III, XDA III, PDA2k, 9090 ROM Development] d-two:
I have make my first Phone call with my girlfriend (with speaker and mic) :good:

But it is a little bit tricky it looks like the UDA1380 sound card reset the i2c connection and this is the reason why it only work without the linux sound driver ?!

But i have now a trace to fix it :D
[MDA III, XDA III, PDA2k, 9090 ROM Development] gbl08ma:
That's good!

So let me understand. If you disable the Linux sound driver, the GSM module can use the microphone and you are heard on the other side of the call, right?

If that's the case, isn't it just a matter of disabling the sound driver (or at least the connection between the microphone and the driver) when a call is made or received, and enabling it back again when hanging up?

EDIT: by "disabling the connection" I mean make it look to the sound driver as if the mic had been removed during the course of the call.
[MDA III, XDA III, PDA2k, 9090 ROM Development] TheAH:
Wow! Congrats D-Two!
[MDA III, XDA III, PDA2k, 9090 ROM Development] B-44:
Yeah.

I presume this trick'll serve Hima too?

(And maybe Alpine?)
[MDA III, XDA III, PDA2k, 9090 ROM Development] d-two:
it can happens both use the same Sound / GSM chip ;)

Have you see this for Hima?
[MDA III, XDA III, PDA2k, 9090 ROM Development] TheAH:
Did you mean to quote someone else :)?

Also D-Two, so on the phone, is it the speaker that works when you put it next to your ear or does loudspeaker also work?

Sorry for bugging the community with all these questions :(.
[MDA III, XDA III, PDA2k, 9090 ROM Development] gbl08ma:
I'm not sure, but I think that on the BA at least, it's the same speaker for the loudspeaker and for the phone calls. Only they are set at different volumes according to the use they are given.
[MDA III, XDA III, PDA2k, 9090 ROM Development] TheAH:
Yeah! They use the same speaker, but I think it has two modes, one for speaker and one for loudspeaker. I learned the hard way how to turn on speaker in WM.
[MDA III, XDA III, PDA2k, 9090 ROM Development] gbl08ma:
Maybe as d-two does more tests on the behavior of the UDA1380, we can understand if there's really a different speaker mode for the GSM, or if it's just audio routing plus a lower volume. I think that at least on WM 6.5, on the BA, sounds like the "busy" indicator are played in the WM theme, but still at low speaker volume (or else it was because I had the system sounds set to low volume, can't remember).

I'm not sure how it is done on the Universal, but there it should be easier to detect the different speaker modes as the phone speakers and the loudspeakers are physically separate.
[MDA III, XDA III, PDA2k, 9090 ROM Development] B-44:
Of course ;)

[MENTION=5158380]TheAH[/MENTION]: What else? :laugh::laugh::laugh:
[MDA III, XDA III, PDA2k, 9090 ROM Development] TheAH:
Well, I won't post anything else if you don't want me to... I thought this forum was about helping each other...
[MDA III, XDA III, PDA2k, 9090 ROM Development] B-44:
Little princess ;)

I quoted you because you had written just the right statement and there had been NOTHING to add... so please go on, you're right by me :up:

Concerning this other person posting frequently- why don't you make your word worth trusting and leave, if you don't see any sense in this project?

If you are disillusioned, it may result from your own expectations, and not from D-two's merits.

Clicking thanks for every bull**** doesn't optimize it, cos this is no bazaar.

Sorry for being this harsh.
[MDA III, XDA III, PDA2k, 9090 ROM Development] TheAH:
Lol, bro I'm sorry about being harsh with you too. I was not pointing out the obvious; just stating my thoughts. Gbl08 said that it might just be the loudspeaker at a lower volume. But I was just talking with gl8 about the sound driver.

Again, I am sorry for this B-44!

(BTW good job getting the gender right ;)

Got your sarcasm there ^^ :))

---------- Post added at 06:39 PM ---------- Previous post was at 05:43 PM ----------

I understand B-44's pain. If you believe that the project will not go on, then have your word for it. D-Two is an amazing man, and you know his magic! Maybe you should understand the economical value of just even $1 today.

I think it is you being the BABY here.
[MDA III, XDA III, PDA2k, 9090 ROM Development] L]e[G:
man ... if you want an android NOW, go to the store and buy it

Inviato dal mio Vodafone Smart II con Tapatalk 2
[MDA III, XDA III, PDA2k, 9090 ROM Development] egzthunder1:
I have deleted many of your posts in the past and it seems you still don't grasp the concept of this forum. This is your last friendly warning about your posts. If you have nothing constructive to add, please don't post. Failure to do this might result in infractions and/or bans.

Sent from mALL GLORY TO THE HYPNOTOAD!!
[MDA III, XDA III, PDA2k, 9090 ROM Development] TheAH:
It is not possible to write the GSM driver to work on EDGE, right?
[MDA III, XDA III, PDA2k, 9090 ROM Development] gbl08ma:
Probably not, since the radio must have support for EDGE. It's not just a drivers thing. If it had support for EDGE, I don't see why the WM driver wouldn't support it, so most likely it doesn't.
[MDA III, XDA III, PDA2k, 9090 ROM Development] TheAH:
Bump, just to make sure it goes up in the new posts :P.
[MDA III, XDA III, PDA2k, 9090 ROM Development] gbl08ma:
It would be nice if we got a status update from d-two... :)
[MDA III, XDA III, PDA2k, 9090 ROM Development] B-44:
I presume him to be on holidays, as he's been online for the last time on august 19th...
[MDA III, XDA III, PDA2k, 9090 ROM Development] TheAH:
Hope he can come back soon!
[MDA III, XDA III, PDA2k, 9090 ROM Development] gbl08ma:
He probably ended up having less free time than he initially thought... it's understandable.
[MDA III, XDA III, PDA2k, 9090 ROM Development] B-44:
I don't think so. He hasn't been online since August,19th.

As we all know he has lately finished School-

Think he's just taken some time out.

IF he'd like to abandon his project, he for shure would tell us

(Hard to believe, as he has come this far.)

Other reasons i don't even want to imagine.

Had this point right here quite a year ago.

I know waiting can be hard not only to children on Xmas eve-

but it's the only thing we can do.

In confidence.
[MDA III, XDA III, PDA2k, 9090 ROM Development] TheAH:
D-Two is a very sincere person, I agree.

I hope nothing bad happened to him :nailbiting:.
[MDA III, XDA III, PDA2k, 9090 ROM Development] TheAH:
Unfortunately, I think that D-Two may have stopped development of PXA Droid :(.

But where could he be, after a month?
[MDA III, XDA III, PDA2k, 9090 ROM Development] B-44:
Did you take a look- he hasn`t been online on XDA since August... had been active on different threads... nothing.

Last year same time he had also been off.

No sleep till hammersmith ;)

Come this far and vanish? No.
[MDA III, XDA III, PDA2k, 9090 ROM Development] TheAH:
Okay. I was alarmed that he had not been on since August. Oh, I feel better now knowing that this went into a slight lull at this time last year. Thanks!
[MDA III, XDA III, PDA2k, 9090 ROM Development] gbl08ma:
Oh well, if only he had posted a semi-working version of his bootloader or CWM and updated kernel sources before leaving... this way we're stuck with a kernel which even supports SDHC, but where many other things lack and since we don't have the source for it, there's nothing that can be done.
[MDA III, XDA III, PDA2k, 9090 ROM Development] TheAH:
Yeah. I guess I will put down my BA for a while :(.
[MDA III, XDA III, PDA2k, 9090 ROM Development] gbl08ma:
Android 2.3, while probably fast enough after many optimizations (and assuming one can make full use of the ATI chip capabilities), is getting phased out very quick (which, globally, it's a positive thing). Right now, Firefox OS is the only modern OS that I believe would be useful on the BA - it is designed for less powerful devices on emerging markets, and while it aims at running on a device with 512 MB of RAM, from what I know it could run in just 128 MB of RAM, as well. However I think we can pretty much forget multitasking. The whole thing would need to be recompiled for ARMv5, and speed would get a big cut.

My goal, when d-two would release a more complete, working kernel, along with some kind of recovery, would be to experiment with FF OS. But, with things the way they are now, we can pretty much forget that.
[MDA III, XDA III, PDA2k, 9090 ROM Development] B-44:
Getting a bit worried- think i'll send him a postcard.
[MDA III, XDA III, PDA2k, 9090 ROM Development] TheAH:
Okay! Do you mean physically?
[MDA III, XDA III, PDA2k, 9090 ROM Development] B-44:
Yeah, really one of those oldfashioned devices with a stamp :D
[MDA III, XDA III, PDA2k, 9090 ROM Development] TheAH:
Did you get any response? I hope he is okay!
[MDA III, XDA III, PDA2k, 9090 ROM Development] B-44:
not yet

btw...

[MENTION=465326]admin[/MENTION]: cracking toast! ;)
[MDA III, XDA III, PDA2k, 9090 ROM Development] Stephen:
Moderator Warning
​

Guys I have just cleaned up some posts. Remember forum rules. Keep posts on toping. if a user posts a comment you are not happy with do not start a flame war. Simply report the post to the moderators and let us deal with it.

Many thanks

Ghost​
[MDA III, XDA III, PDA2k, 9090 ROM Development] TheAH:
Has anyone heard any news about d-two? I hope he is okay.

Happy new year!
[MDA III, XDA III, PDA2k, 9090 ROM Development] gbl08ma:
I haven't heard or read anything. I guess the batteries, or some other (possible unreplaceable) component of my BAs will die (like what happened with my Uni's battery and camera) before they see a byte of CWM or a newer kernel or Android build.

This situation is really regrettable, and if this was what d-two wanted from the beginning, it's quite arrogant of him to create the "toys" just to be the only one to play with them, while saying "look at me, I'm playing with them and you can't".

Happy new year to you too.
[MDA III, XDA III, PDA2k, 9090 ROM Development] B-44:
I can't manage to contact him- and inbetween am really worried, as he hasn't been online for months now.

Nowhere...

Quoth the raven ...
[MDA III, XDA III, PDA2k, 9090 ROM Development] d-two:
Hy, i was a little bit out of time :silly:

I work on my Car... but i will continue my work sooon...

Greetings D-Two...
[MDA III, XDA III, PDA2k, 9090 ROM Development] egzthunder1:
For what is worth, I am truly glad to see that you are ok :)
[MDA III, XDA III, PDA2k, 9090 ROM Development] gbl08ma:
I too am glad to see you are alive and ok... or has your XDA account been stolen? :)

I'll say one last time (and I promise it is the last time I say this to you, because by now I've certainly become annoying): publishing more source code/documentation for your work and/or coming here more often would be good...

If you are continuing your work soon, I'd suggest that we think for a bit on what would make sense to work on: Android 2.3 is quickly phasing out, and from there new versions just kept on increasing their RAM, CPU and GPU requirements. KitKat has a "low-memory" mode but it still needs 512 MB of RAM - four times what we have available on the BA. In my honest opinion, it makes no sense to port a OS as an alternative to the obsolete Windows Mobile, when that new OS is already obsolete too. Perhaps the best thing to do right now is to just get the Linux kernel working perfectly, and forget about any fancy thing running on top of that kernel - then the BA, Uni and friends could be used as general-purpose embedded devices that also happen to have a built-in GSM modem.

On a related note, Firefox OS has an ongoing project to make FF OS work in just 128 MB of RAM ( https://wiki.mozilla.org/FirefoxOS/Tarako ).

Seeing that some OEM plans to launch a $25 FF OS smartphone with 128 MB of RAM ( http://www.cnx-software.com/2014/02...ox-os-smartphones-with-spreadtrum-sc6821-soc/ ), it is likely that the project will be successful.

There is, however, still the issue that the PXA263 is ARMv5, where nowadays getting projects to support ARMv6 is already hard (fortunately, lots of people own Raspberry Pis). I can imagine FF OS being really slow on such a CPU, but seeing what you did with Android, we'd have to "wait and see".
[MDA III, XDA III, PDA2k, 9090 ROM Development] d-two:
[MENTION=2150610]gbl08ma[/MENTION]

I have post the Kernel source for a long time and nobody have continue my work...

http://sourceforge.net/p/pxadroid/pxakernel/ci/master/tree/
[MDA III, XDA III, PDA2k, 9090 ROM Development] gbl08ma:
I could never get a working kernel out of that source tree, I think it is not up to date, or are there some patches I'm missing? Perhaps it's better if the patches (if any) were applied to the main source and uploaded...
[MDA III, XDA III, PDA2k, 9090 ROM Development] d-two:
The sourcecode is working, if you can not create a working kernel it's not my fault...
[MDA III, XDA III, PDA2k, 9090 ROM Development] gbl08ma:
I haven't experimented in some months, so I can't fully remember, but I know that the kernel would compile but it would almost always panic at the very beginning of the boot, and when it didn't panic, major things didn't work (WiFi for example) that worked on your builds. This makes sense and is expected, because the source that is on SourceForge is from 2012... so if I wanted to continue your work, I'd need to work on the public source kernel to match the abilities of your kernel, and only then mine would eventually surpass yours in terms of completeness.
[MDA III, XDA III, PDA2k, 9090 ROM Development] d-two:
The source code is from Kernel 3.5 and here is the list what exacly works...

http://xdaforums.com/showpost.php?p=11073139&postcount=2

And i can't see that Wifi ist working...
[MDA III, XDA III, PDA2k, 9090 ROM Development] gbl08ma:
That's the list of what works for your public builds. Apart from that, you demoed on your videos a lot of things for which you never made public any binary or source. That's what I'm complaining about, that you seem to have made much progress which you never made public. And of course I or anyone else would not start working on something that was done already...

With my code tree, which I built from what is on SourceForge and possibly some patches posted on this thread (not sure if I applied the patches or not, I can't remember), what I get is this: http://s.lowendshare.com/4/1401127029.380.zImage (rename to zImage if it doesn't rename automatically)

Is this the "state of art" of the kernel 3.5 on the BA?

By the way: regarding your bootloader and recovery, how are things going? As you may have read my last SD non-HC card broke. This makes it a pain to load new kernels on the device for debugging, because WM doesn't support SDHC cards on this device. I would need to transfer the kernel to WM's "internal storage", along with HaRET; this requires using ActiveSync for transferring files or Bluetooth, which is less practical than putting files on a SD card and simply rebooting. Imagine doing this 20 times a day while trying to fix something...

Is it possible to have a bootloader that loads the kernel from the SD card? Or is this too hard (because the bootloader would need to have SD card drivers)?

EDIT:

I eventually found a way to update the zImage, it consists of using a HTTP server on the computer and Internet Explorer on the BA to download a new zImage every time I compile the kernel.

Unfortunately it's hard to test further, because the init binaries I have are not compatible with kernel 3.5 (they were made for 2.6). This causes a kernel panic ("attempted to kill init") right at the beginning. There seems to be no source code for userland binaries, but these are probably unmodified and can be built from the Android source tree...

Speaking of the Android source tree, you haven't released any source code for the modifications you made to the Android part, have you? Have you considered using git and GitHub or SourceForge to push your source code to, e.g. weekly? That would make it easier for people to follow the development.

EDIT2:

On the 2.6 kernel, did the asic3 "interrupt processing overrun" problem exist? If yes, how did you solve it? I found some references on the internet, it seems it's because some bit is getting stuck in the registers, and to me it appears it is related to pressing more than one key at a time. It also appears to be specific to the BA. But nothing concrete on how to solve it.
[MDA III, XDA III, PDA2k, 9090 ROM Development] B-44:
I'm just glad you're back.
[MDA III, XDA III, PDA2k, 9090 ROM Development] gbl08ma:
<nevermind, I solved my problem right after I posted this. For reference: never forget to enable the mtd support option >

----

OK, new problem. I managed to compile things to the point where the kernel boots and init starts, then it begins to start Android services. However, no services can start, they all exit with some error (including servicemanager). I had to remove the "critical" from the servicemanager part in init.rc if I wanted to see anything at all, because otherwise it would reboot to "recovery".

The main problem is, I would like to debug why services are failing, but for this I need adb to work. The adb service appears to be running, however (and unlike what happens on the 3.4 kernel that leaked on SourceForge), the USB doesn't work (no kernel messages when I connect/disconnect from cradle, adb on the computer doesn't detect device). I think I enabled all the kernel options that were needed. Is there anything more to do?

I'm sure the cradle is connected to the computer and that the USB port on the computer is working :D

By the way, this is my kernel config right now: https://clbin.com/lptxB

Ah, and I have compiled and I'm trying to run ICS 4.0.4 (CM9).
[MDA III, XDA III, PDA2k, 9090 ROM Development] d-two:
Check your init.rc for enable ADB... your config looks ok... in my opinon start with GB this is a lot much easier.

PS: you are use 3.5 not 3.4 kernel ;)
[MDA III, XDA III, PDA2k, 9090 ROM Development] gbl08ma:
I am sure adb is being started, I know this because I added some debug lines that get printed on the screen to init.rc, and furthermore I see messages from adb on the screen. Tomorrow I'll post my init.rc (I'm on mobile now).

I am 99% sure it is a problem with the kernel, because if USB was working I would see some messages on the screen when connecting USB (I have compiled kernel with USB debug enabled).

And I know this is kernel 3.5. I was mentioning the 3.4 kernel that is meant for flashing with HTC-Flasher, which even has a PXAdroid logo while booting (and includes a initramfs where adb works).

I'll try checking out the CM7/GB code tree to see if it makes a difference, but I think that for ADB and USB it makes no difference as the kernel will be the same and init is similar.
[MDA III, XDA III, PDA2k, 9090 ROM Development] d-two:
the prints on the Display has nothing todo with ADB (Android Debug Bridge) and the configuration between GB and ICS is diffrent... The problem is not the Kernel... I think your Init.rc is not correct...
[MDA III, XDA III, PDA2k, 9090 ROM Development] gbl08ma:
Sorry, I have been busy in the last days and more or less forgot to post my init.rc.

Here's my init.rc for ICS: http://tny.im/pxaicsinitrc (you can click "View raw contents" if you want to save the file)

The "GBL DEBUG" lines were added by me to make sure that certain code paths were being executed (and that some others weren't).
[MDA III, XDA III, PDA2k, 9090 ROM Development] Essef1959:
SDcard

Hi

Following D-Two,s instructions ive hit a brick wall sort of, as i cant access the EXT2 portion of the SDcard in windows to load the rom image for SD install ?.

Any assistance will be appreciated

Thanks

Essef ;)
[MDA III, XDA III, PDA2k, 9090 ROM Development] ares93:
hmm, the pointercal file from my android tablet contains this:

34658 110 -1746778 123 57812 414160 65530

so i'm guessing thats not pointercal. even if the calibration was messed up, the formatting should be the same.
[MDA III, XDA III, PDA2k, 9090 ROM Development] d-two:
no this was my pointercal... i talk with notime for this problem... under evtest i have correct x,y coords
[MDA III, XDA III, PDA2k, 9090 ROM Development] tomcug:
Well, for me it's a calibration software issue, maybe it doesn't work well with TSC2200. Anyway, I think that you should ask here, in Android Chef section, try that d-two :D.

http://xdaforums.com/forumdisplay.php?f=613
[MDA III, XDA III, PDA2k, 9090 ROM Development] tomcug:
I've got one idea, d-two. Maybe you could finally upload all your sources and use our help here. Together we can do it much faster and also better for sure!

EDIT:

Okay, forget it man, we can live without Froyo :(.
[MDA III, XDA III, PDA2k, 9090 ROM Development] legmovement:
dont be like that...maybe the man wants to complete this callange alone. it his right...
[MDA III, XDA III, PDA2k, 9090 ROM Development] tomcug:
Yes, it is, but I'm just worried about this project. There weren't any updates for over two weeks. And it's just touchscreen driver, so think how much it will take to make entire ROM :(.
[MDA III, XDA III, PDA2k, 9090 ROM Development] d-two:
I have buy new PC parts... now i can continue on the project... and i have make a small filesystem with tslib and the touchscreen work very well and momentary i work on the android filesystem!!! When you can't wait buy an HTC Desire ...
[MDA III, XDA III, PDA2k, 9090 ROM Development] tomcug:
Nice to see you're alive d-two :D. And I'm just waiting for Froyo to give it a try, I don't even use Blue Angel as my primary phone, however it's legend so I keep it :D.
[MDA III, XDA III, PDA2k, 9090 ROM Development] fpopic:
any news :) ?
[MDA III, XDA III, PDA2k, 9090 ROM Development] d-two:
Yes, gingerbread work :D but it has the same problem with touchscreen :mad:

EDIT: work on an way to debug!
[MDA III, XDA III, PDA2k, 9090 ROM Development] tomcug:
I wouldn't try Gingerbread on Blue Angel. It already works so slow on Kaiser, so I bet it would be disaster on this phone. Tell us something more about touchscreen :D.
[MDA III, XDA III, PDA2k, 9090 ROM Development] tomcug:
Looks like d-two doesn't want to give us more details :p. He doesn't want any help too, well, it's his choice :confused:.
[MDA III, XDA III, PDA2k, 9090 ROM Development] barnaclebilly:
he will give it to us when he's ready
[MDA III, XDA III, PDA2k, 9090 ROM Development] tomcug:
I don't want him to give us Froyo right now. I just asked about touchscreen issue :mad:.
[MDA III, XDA III, PDA2k, 9090 ROM Development] B3nGz:
can i install talk box on blue angel with your froyo and use wifi to talk box iphone user?

i mean i really curious if it can install apps
[MDA III, XDA III, PDA2k, 9090 ROM Development] tomcug:
Man, he doesn't even have working release yet :p.
[MDA III, XDA III, PDA2k, 9090 ROM Development] barnaclebilly:
if i was you B3nGZ buy an iphone..cant see froyo on a blue angel this year.