Develop Bugs

[prj][Donut 1.6 Donut][Samsung Galaxy S Theme][Released 07.16.2010]

Do Not Bother xdandroid devs, with fillrate or hw3d being faster on donut than on eclair, plz they are not mages, stuff dont just magically work out of no were
At long last i finally got around releasing it, as i said before this is based on a AOSP Donut Build.Speed and stability should be around the same as my last donut build, also i recently acquired a motorola cliq so i will most likely be developing for that device also, please report any bugs i may have missed,anyways hope you like the rom.
I need feedback from you guys to see what works or dosent, i do not own this device. Working and non working stuff will be populated once people have posted them on comments.
Whats Working:
Pending need testers
Click to expand...
Click to collapse
Whats not working:
Camera
GPS
BT
Click to expand...
Click to collapse
Download Link
http://www.mediafire.com/?01h66pvn4aan491
Click to expand...
Click to collapse
Root Fix
http://www.mediafire.com/?sn84lv46b9a244l[/COLOR]l
Click to expand...
Click to collapse
And last but not least, if you can plz donate whaever you can, iv never requested this before, but this really encourages me to make more themes and ports.
Click to expand...
Click to collapse
Follow me on Twitter: http://twitter.com/theunholy_
And remeber you can always find me in freenode, #xdandroid,#htc-linux, under Unholy

siulmagic said:
Hey there guys its me again, this time i bring you another Donut AOSP based build, with a Samsung Galaxy S Theme. This rom will be more or less as fast as my last one (noche oscura). Anyways this just a preview of the build, im still working out the quirks and stuff that need fixing still. But hey stay tunned for the release, and hopefully you like the rom as much as i do.
And remeber you can always find me in freenode, #xdandroid,#htc-linux, under Unholy
Click to expand...
Click to collapse
great job
ok, next week i'm in vacation, but when i'm back i'll try it ...
PLS: do you have the "touchscreen bug" on 1.6 ?
(sometimes touch screen is jumping to the left (2-3cm).
this can be tested via "dotty" or "paint", and this happen only if you use the finger and if you press on a position - mostly seen on middle to button)
because if it would work on 1.6, maybe i can use the calibration or touchscreen driver ....

camro said:
great job
ok, next week i'm in vacation, but when i'm back i'll try it ...
PLS: do you have the "touchscreen bug" on 1.6 ?
(sometimes touch screen is jumping to the left (2-3cm).
this can be tested via "dotty" or "paint", and this happen only if you use the finger and if you press on a position - mostly seen on middle to button)
because if it would work on 1.6, maybe i can use the calibration or touchscreen driver ....
Click to expand...
Click to collapse
Hi i tried one of apps you described, paint and i cant seem to get that bug, lines draw like they should no jumping.

siulmagic said:
Hi i tried one of apps you described, paint and i cant seem to get that bug, lines draw like they should no jumping.
Click to expand...
Click to collapse
thanks, when i'm back i'll try it ...
maybe we can combine some old parts to froyo to get it fixed on froyo also ...
or can you upload the startscript + touchscreen related drivers ?
or are they compiled in the kernel, but don't think so ...

camro said:
thanks, when i'm back i'll try it ...
maybe we can combine some old parts to froyo to get it fixed on froyo also ...
or can you upload the startscript + touchscreen related drivers ?
or are they compiled in the kernel, but don't think so ...
Click to expand...
Click to collapse
I dont think you could port libs from donut to froyo(and evenif it could be done, that's beyond my knowledge), also this rom has not been tested on the blackstone yet, you would have to wait for me to release to see how it works, all my releases are tested on a raph110 witch is the device i own.

siulmagic said:
I dont think you could port libs from donut to froyo(and evenif it could be done, that's beyond my knowledge), also this rom has not been tested on the blackstone yet, you would have to wait for me to release to see how it works, all my releases are tested on a raph110 witch is the device i own.
Click to expand...
Click to collapse
this is sure, that mixing is never a good idea ...
meanwhile i know that this is a HARET problem (there the irqs for touchscreen will be registered ..).
so there will also no module for it ...
we will see how it works
can't wait for your version

camro said:
this is sure, that mixing is never a good idea ...
meanwhile i know that this is a HARET problem (there the irqs for touchscreen will be registered ..).
so there will also no module for it ...
we will see how it works
can't wait for your version
Click to expand...
Click to collapse
You can if you want, test my other build it is almost the same as this one, only diferent theme's and minor optimizations, a link to it is on my signature. Look for Noche oscura

[Q] Some WIFI Problems with FROYO X on Rhod210 - HTC Touch Pro 2

Hi, I noob on this of an Android Phone, I have a HTC TOUCH PRO 2, RHOD210.
I install the FROYO X 2011.01.12 and i put the kernel that have the packet than run the camera and this is OK.
My problem is that the wifi interface is not workink, i am try a lot of solutions that found in this forum, but nothing is ok for me, i change the rootfs like suggest in a forum, modify the wifi-nvram.txt and put the mac address of the wifi, i update the kernel to Latest Kernel Commit# 1253, and i have the same problem.
could someone tell me how to solve the wifi of my rhod210?
Please, I do not want to use windows mobile

How about you just run with vanilla FRX03 and then try to get fancy with it?
Let us know how that works, then we can work on updating your kernel. If you're a noob at swimming, you don't start in the deep end...

arrrghhh said:
How about you just run with vanilla FRX03 and then try to get fancy with it?
Let us know how that works, then we can work on updating your kernel. If you're a noob at swimming, you don't start in the deep end...
Click to expand...
Click to collapse
Sorry, i'm only was trying to solve the problems for my self.
I understand that some of these RHOD210 if they have managed to run the wifi.
I tell you that I use from the beginning FRX03 and it worked well, at least part of the telephone, sound and GPS, but other things did not work, so I started to search the forums and trying different solutions. but I have not found a way to walk the wifi which is what most interests me, so probe, with the latest versions of the kernel etc.
Thanks, I know I'm a rookie, but I like trying to find solutions to the problems I have ....

kleper said:
Sorry, i'm only was trying to solve the problems for my self.
I understand that some of these RHOD210 if they have managed to run the wifi.
I tell you that I use from the beginning FRX03 and it worked well, at least part of the telephone, sound and GPS, but other things did not work, so I started to search the forums and trying different solutions. but I have not found a way to walk the wifi which is what most interests me, so probe, with the latest versions of the kernel etc.
Thanks, I know I'm a rookie, but I like trying to find solutions to the problems I have ....
Click to expand...
Click to collapse
Yes, and I'm trying to help you triage. You said a lot in this post, but didn't answer my question.
Does wifi work with a vanilla FRX03 bundle?

arrrghhh said:
Yes, and I'm trying to help you triage. You said a lot in this post, but didn't answer my question.
Does wifi work with a vanilla FRX03 bundle?
Click to expand...
Click to collapse
Does't work wifi in vanilla FRX03, in fact, the phone worki slow with this kernel, with FROYO is more faster.
Thanks.

kleper said:
Does't work wifi in vanilla FRX03, in fact, the phone worki slow with this kernel, with FROYO is more faster.
Thanks.
Click to expand...
Click to collapse
Erm, I guess I should be more specific.
Where did you download vanilla FRX03? Also, FRX03 is Froyo, so I assume you mean that Froyo 'X' build tiad8 put together.
Also, I'm not sure what you mean "slow with this kernel" - by vanilla FRX03 build, I mean the complete bundle - not just the kernel. Plus, kernels are not tied to system images... So I'm not sure what you mean.

arrrghhh said:
Erm, I guess I should be more specific.
Where did you download vanilla FRX03? Also, FRX03 is Froyo, so I assume you mean that Froyo 'X' build tiad8 put together.
Click to expand...
Click to collapse
Yes, is this build, i look de dmesg logs of the phone, and i see an error that say: can't found the mac address of the wifi. and, i look the file, wifi-nvram.txt and this file have the mac address that i look on windows mobile.

kleper said:
Yes, is this build, i look de dmesg logs of the phone, and i see an error that say: can't found the mac address of the wifi. and, i look the file, wifi-nvram.txt and this file have the mac address that i look on windows mobile.
Click to expand...
Click to collapse
I thought I already directed you to this thread, but it seems to be your issue... so follow these directions. See F22's post.

arrrghhh said:
I thought I already directed you to this thread, but it seems to be your issue... so follow these directions. See F22's post.
Click to expand...
Click to collapse
I do that, and don't work for me.
Thanks

kleper said:
I do that, and don't work for me.
Click to expand...
Click to collapse
Well then, I guess you just can't have wifi...
Honestly, every single person either wifi "just works", or they have to do the wifi-nvram trick. I've never heard of anyone not being able to use wifi, that didn't try the wifi-nvram trick - and those people were definitely in the minority. Vast majority of people, wifi works perfectly fine for.
Please, be a little more diligent. I can't do this troubleshooting for you, I can only point you in the right direction. I need you to do some legwork, as I can't see what you're doing.

arrrghhh said:
Well then, I guess you just can't have wifi...
Honestly, every single person either wifi "just works", or they have to do the wifi-nvram trick. I've never heard of anyone not being able to use wifi, that didn't try the wifi-nvram trick - and those people were definitely in the minority. Vast majority of people, wifi works perfectly fine for.
Please, be a little more diligent. I can't do this troubleshooting for you, I can only point you in the right direction. I need you to do some legwork, as I can't see what you're doing.
Click to expand...
Click to collapse
Fine, i go to format again my SD-CARD and start from zero, any installer recomeded? or pick the installer that i want?

how do I find out my exact model, I'm assuming is that it's RHOD210 for photos and that according to information I have read I understand that T-Mobile only has this HTC TOUCH PRO2, can that be part of my error, there is a way to identify exactly which model is?

kleper said:
how do I find out my exact model, I'm assuming is that it's RHOD210 for photos and that according to information I have read I understand that T-Mobile only has this HTC TOUCH PRO2, can that be part of my error, there is a way to identify exactly which model is?
Click to expand...
Click to collapse
Sticker underneath the battery - not on the battery itself. It's usually in tiny gray font.
kleper said:
Fine, i go to format again my SD-CARD and start from zero, any installer recomeded? or pick the installer that i want?
Click to expand...
Click to collapse
Well, I'd format with the HP tool. (Full format, FAT32) Download this bundle as well.

[SOLVED]
Thank you very much to everyone who answered me and all the developers of this project so interesting, yesterday succeeded in solving the problems I had, my SD formatting, reinstalling Froyo x version 2011.01.12 and puts a kernel of the chamber, after That did the trick again wifi-nvram.txt file, according to the link that let me arrrghhh one of the threads of this forum, after that the WIFI has started to work wonders.
Then my HTC Touch Pro 2, RHOD210 remain with:
WIFI
CAMERA
GPS
PHONE, DATA AND YOU
AUDIO
Thank you very much.

Remember to use zImage and Modules package from the same place and that only WPA is working , NO WEP !

eu0741924381 said:
Remember to use zImage and Modules package from the same place and that only WPA is working , NO WEP !
Click to expand...
Click to collapse
WEP actually seems to work on mine. Strange as that is.

Other problems
These days I've been testing my phone RHOD210 Android, after having settled about the WIFI, but I noticed a problem is that the phone is locked, I can receive a call and make a call, and thereafter ceases to operate the module telephony, change the 1214-Dirty kernel that runs the camera for the 1253 and I have the same problem, another thing I noticed is that the speakerphone does not work completely, it is telling me the microphone works but not the headphones, someone happened?

kleper said:
These days I've been testing my phone RHOD210 Android, after having settled about the WIFI, but I noticed a problem is that the phone is locked, I can receive a call and make a call, and thereafter ceases to operate the module telephony, change the 1214-Dirty kernel that runs the camera for the 1253 and I have the same problem, another thing I noticed is that the speakerphone does not work completely, it is telling me the microphone works but not the headphones, someone happened?
Click to expand...
Click to collapse
Uhm... the older kernel doesn't have the commits for speakerphone mic I would say. Once it all gets committed to GIT it will be a lot less confusing - just a lot of code that's in testing right now basically.
jchutch2 said:
WEP actually seems to work on mine. Strange as that is.
Click to expand...
Click to collapse
WEP should never, ever be used in any circumstances if it can be avoided. That protocol is extremely insecure...

arrrghhh said:
Uhm... the older kernel doesn't have the commits for speakerphone mic I would say. Once it all gets committed to GIT it will be a lot less confusing - just a lot of code that's in testing right now basically.
Click to expand...
Click to collapse
What kernel do you recommend for my RHOD210, the 1253 is doing that the phone will be frozen and I have to Quiaro the battery and put it again to restart the system.
Wonder that in the future will be able to remove the windows and flash the device with adro to make it natively? : D
Thank you very much

kleper said:
What kernel do you recommend for my RHOD210, the 1253 is doing that the phone will be frozen and I have to Quiaro the battery and put it again to restart the system.
Wonder that in the future will be able to remove the windows and flash the device with adro to make it natively? : D
Thank you very much
Click to expand...
Click to collapse
Well, I'd recommend 1250 then I guess... Usually I recommend the newest GIT kernel, which is currently 1253.
FYI, you already can remove Windows and flash the device to run Android natively. It's just not as stable as haret, but it's getting there. Plus, it's only a partial NAND boot - only init and the zImage are actually loaded on the MTD if I'm not mistaken, everything else is on the SD card (which is still 99% of the data...)
But, if you're feeling brave and really do want to completely get rid of WinMo, NAND boot away... can't say I didn't warn ya

[DEV] We have a 90% working cam now

Ok, so, Thanks to aread22 We have a 90% working cam, since we still dont have 720p and some effects ares still broke, but share and set as both work which was the original goal of this, and while we dont have 720p recording yet, im sure we will get there (eventually )
Heres that Cam:View attachment HTCCamera.apk
oh and btw, its from the 1.84 desire sense rom.
So things still to fix:
-720P
-Some effects (graphic intensive ones, probably gpu related)
(and i really hope some mod doesn't move this thread to q&a like my last thread, WHICH WAS NOT A Q&A THREAD)

* reserved*

Ok, i guess what ill put here are the tools that will help anyone who wants to contribute to this,
Beyond compare: A very very good compare tool for directory's and files
http://www.scootersoftware.com/
Apk manager: a very easy feature rich app script package for apk's that will let you extract,decompile,recompile and a ton of other stuff
http://forum.xda-developers.com/showthread.php?t=695701
Notepad++: one of the best text/data editors i have ever used, very handy..
http://notepad-plus-plus.org/
DroidExplorer: will let you access your android device like an explorer window..
http://de.codeplex.com/
dsixda's HTC Android Kitchen: a very easy kitchen to use, windows (with cygwin) and linux compatible
http://forum.xda-developers.com/showthread.php?t=633246

u forgot cmylxgo's desire HD camera fix..

dailomac said:
u forgot cmylxgo's desire HD camera fix..
Click to expand...
Click to collapse
omfg not this sh*t again..
i defer you to this:
http://forum.xda-developers.com/showthread.php?t=981881
hell, go read cmylxgos thread, hes using my fixed apk..
and one of the people collaborating with us on this is cmylxgo along with g.lewarne,dandiest and a few others should be contributing too..

ok, anyways.. i have been pouring over smali files for days, trying different files in lib,bin and from looking at the log, my current guess is that the issue lies with the recording of audio when you hit record, which it runs into an error when it tries and crashes the apk.. i dont know if thats correct and im not sure what needs to be done to fix it, but thats why we have a dev thread for eh?

How about 720 recording ...is it just not possible cause I figured someone would have figured this out by now

tigerz0202 said:
How about 720 recording ...is it just not possible cause I figured someone would have figured this out by now
Click to expand...
Click to collapse
well, that isnt something i believe that can be done at the moment, but i do believe it is possible and from what i have read its mostly a kernel issue, seeing as how wp7 can do it on our hardware and thats all software..
but before we even approach that here, i would like to get just basic recording working with the newer camcorder function..

pyrorob said:
well, that isnt something i believe that can be done at the moment, but i do believe it is possible and from what i have read its mostly a kernel issue, seeing as how wp7 can do it on our hardware and thats all software..
but before we even approach that here, i would like to get just basic recording working with the newer camcorder function..
Click to expand...
Click to collapse
Which apk is the one with all the boxy border .....I hate that one, the one that comes with cmyxlo builds is the one I would love to have in my cm7 rom I'm currently on. And will it install

tigerz0202 said:
Which apk is the one with all the boxy border .....I hate that one, the one that comes with cmyxlo builds is the one I would love to have in my cm7 rom I'm currently on. And will it install
Click to expand...
Click to collapse
the boxy border? i have not seen that.. and the one in cmylxgo's rom is of course, the older one with the working camcorder function..

pyrorob said:
the boxy border? i have not seen that.. and the one in cmylxgo's rom is of course, the older one with the working camcorder function..
Click to expand...
Click to collapse
Its got a grey border around the screen. Some devs skin it some don't

tigerz0202 said:
How about 720 recording ...is it just not possible cause I figured someone would have figured this out by now
Click to expand...
Click to collapse
What about A/V sync in Sense builds? I've been flashing and flashing, and have yet to find a truly working camcorder in this regard? Is this likely to be fixed?

inconceeeivable said:
What about A/V sync in Sense builds? I've been flashing and flashing, and have yet to find a truly working camcorder in this regard? Is this likely to be fixed?
Click to expand...
Click to collapse
well, who knows? maybe the different version of the camcorder could fix it? who knows until we get it working...

i think people are more likely to be using the camera so if we get a camera,it will be a big breakthrough and then the camcorder will probably come after you figured out the camera,keep up the hard work

Keep up the good work ! And this thread deserves to be in the stickies !

Finally, I'm glad to see that you've taken the initiative to get this moving. Can this also apply to the currently non-working camera that appears in the new Gingerbread Sense build by iMilka (and for other future builds)?

jonboyuk said:
Finally, I'm glad to see that you've taken the initiative to get this moving. Can this also apply to the currently non-working camera that appears in the new Gingerbread Sense build by iMilka (and for other future builds)?
Click to expand...
Click to collapse
well, who knows, what i would like to see is people posting logs from alogcat at the time the try to run the camera (if it fc's as soon as you open it) or when they hit record (if it fc's there)
i dont know what the issue is with the gb camera (does it fc on open?)
but i wouldn't mind if this say, became the thread where we work out camera issues on all builds
and if enough people posted log snippets, just maybe we can find a commonality and that would head us in the right direction..
as it stands im figuring that the issue lies in the kernel or the libs, with the kernel looking more likely, im figuring it needs updated code to be compatible with the newer cameras and more then likely if we can get the newer camera working here, then the gb camera would also..

logcat
here i have attached the logcat. this is my first time. so im not sure if ok. i have started the logcat and then i click the camera then it did soft reset and reboot i close the logcat.
pyrorob said:
well, who knows, what i would like to see is people posting logs from alogcat at the time the try to run the camera (if it fc's as soon as you open it) or when they hit record (if it fc's there)
i dont know what the issue is with the gb camera (does it fc on open?)
but i wouldn't mind if this say, became the thread where we work out camera issues on all builds
and if enough people posted log snippets, just maybe we can find a commonality and that would head us in the right direction..
as it stands im figuring that the issue lies in the kernel or the libs, with the kernel looking more likely, im figuring it needs updated code to be compatible with the newer cameras and more then likely if we can get the newer camera working here, then the gb camera would also..
Click to expand...
Click to collapse

rasumia said:
here i have attached the logcat. this is my first time. so im not sure if ok. i have started the logcat and then i click the camera then it did soft reset and reboot i close the logcat.
Click to expand...
Click to collapse
what camera apk is this and what rom?
and do this when you post these, look at the time on your watch or computer when you hit record and mention that. as long as its set the same as your device (your pc should have its clocked auto synced just like your phone so its times should match). this way there wont be a need to do a bunch of fishing for the error in the log.. oh, and set your log type to long under alogcat preferences..
edit: ok i see this is the gingerbread rom..
and wow lots of permission errors and a java failed binder transaction then all your services die..
and another odd, it seems to be connecting to htc database servers to check for updates..

camera
Sooo.. for ex. I have frankinstein droid 1.5 rom, when i hit record it doesn't work, and i must reboot my hd2.
What i wanna install ?

DONT BOTHER WITH THIS SEE Herosso

This is now obsolete, Erasmux has ported the hardware (some of it) which i am havign trouble doing.I dont intend to steal his work so please use his!
http://forum.xda-developers.com/showthread.php?t=1026699
To revert MTD and flash back please see HERE

Issues and Changelog
Changelog..
First version..
Issues..
WIFI
MICROPHONE
CAMERA
NETWORK DATA - A little fishy
ROTATE - Think ive fixed in next version
MARKET - Loops Crashing?
BROWSER - Loops Crashing?

Well no bug or something, but I've added the rom on my mirror . here

Good luck with this. It's great to see that there are still some people who believe in a 2.2 sense rom for the hero
when the rom is tested a bit i will add it to my rom database

dude, you built a rom! congrats on being so bleeding edge bonesy!
I'm impressed with your guts
um, don't take this the wrong way, but I'm not about to try it just yet... ;-) It's just because I need my phone and it's camera etc for daily use. I have faith in you - you've been messing with this stuff longer than I have probably dude and your flashing instructions are VERY clear which is comforting.
I'm really impressed that you persevered like this though man!
cheers
Don

Like I said gonna give it a try when at work. Great work man. And ill report back in here all my findings.
Like don said. Great to see this still happening to the hero.
Sent from my HTC Hero using Tapatalk

What is working? What not?

krygo said:
What is working? What not?
Click to expand...
Click to collapse
see 2nd post,Lots working but lots not,was up untill 4am trying to fix some,as soon as i get mic and / or wifi going ill release 0.2

hi there!
I'm a bit puzzled how to revert to pre-MTD changes state.
I am willing to test this rom, but I would like to have an option to nandroid back without much of a problem. I read through the topic bonesy linked, but haven't found a simple answer/solution.
I hope I could help some more, at least confirm bugs or something.
Cheers!
brat.haneq
EDIT:
Is it as simple, as flashing "remove" zip?

Nearly, you will need to re-flash recovery too, Through fastboot..
Im struggling at the moment as i have 2 different builds on 2 different computers.As soon as i can get to my work computer i can carry on with it all

Call me stupid but is CustomMTD really necessary ? This rom can't work as all roms do? I've flashed it without MTD method and I am stuck on first splash-screen (mine says HERO on black background).
BTW ty for working on a Froyo Sense port for Hero GSM

omg Ninpo is involved, <3 him (nogay)
I will try when it's a little bit better ^^ and can be used for 1 day at school
good work man!

Wupper said:
Well no bug or something, but I've added the rom on my mirror . here
Click to expand...
Click to collapse
offtopic:
omg you again XD hahahaha

I will not flash this yet but still I want to say thanks to all devs for working on froyo sense

@bonesy. how are you hoping the development of this ROM will be community driven? Would you like us to simply try it and report bugs (no different to most other ROMS I think) or would you like us to get down and dirty with code wherever possible?
Im just a regular user but i'd like to help with the development of this rom. if i was pointed in the right direction I would even be willing to learn about how to develop this rom!
anyway good effort for starting on this (I expect, long) journey

f_padia said:
@bonesy. how are you hoping the development of this ROM will be community driven? Would you like us to simply try it and report bugs (no different to most other ROMS I think) or would you like us to get down and dirty with code wherever possible?
Im just a regular user but i'd like to help with the development of this rom. if i was pointed in the right direction I would even be willing to learn about how to develop this rom!
anyway good effort for starting on this (I expect, long) journey
Click to expand...
Click to collapse
Im hoping all devs will see that there are still people wanting Sense on their hero's,FroYo sense stopped as soon as GB was booting up on the hero and now it seems to be forgotten.Ideally id like to learn how to do ll the porting but theres not much in the way of advice out there..
Is custom MTD really necessary?
Click to expand...
Click to collapse
In a word..Yes (its over 200mb in size just on /system partition) hopeing eventually it wont need it

bonesy said:
Im hoping all devs will see that there are still people wanting Sense on their hero's,FroYo sense stopped as soon as GB was booting up on the hero and now it seems to be forgotten.Ideally id like to learn how to do ll the porting but theres not much in the way of advice out there..
Click to expand...
Click to collapse
I couldnt agree more! well if you do find anything useful I will help anyway I can

bonesy said:
Im hoping all devs will see that there are still people wanting Sense on their hero's,FroYo sense stopped as soon as GB was booting up on the hero and now it seems to be forgotten.Ideally id like to learn how to do ll the porting but theres not much in the way of advice out there..
In a word..Yes (its over 200mb in size just on /system partition) hopeing eventually it wont need it
Click to expand...
Click to collapse
Well took a quick look at this. Will try to devout some more time over the next few days and see if it'll get me anywhere.
What I got for now is:
a) There is quite a lot of "junk" on the system partition here, after a short cleanup it fits very nicely without the MTD patch .
b) libwebcore.so fixes the browser crashes and most likely the markets too.
If I have time tomorrow I'll try to give the microphone a shot, cause this is the most critical problem at this point - whats the point of having a telephone you even talk to...
Hopefully I'll also release something for testing tomorrow...

Thanks Erasmux, i would have gtalked you today but been at work and the boss was in...so no devvin on the work pc lol.Got market and browser fixed as you say and also rotate and i think light sensor.I removed nabservice.apk as it only FC'd.Would be great if we can arrange a time over the W/end to talk

Opened a new thread for "my" version of this port:
http://forum.xda-developers.com/showthread.php?t=1026699
Please note, that the amount of effort I will be able on such a (closed source) ROM is limited. I mainly what to see how far I can get this, especially in terms of hardware support, with my past experience.
So its up to you if you want to continue to keep your version going in parallel. If you do (or anyone else), please feel free to reuse anything from "my" ROM....

[BUILD] **Complete GingerBread Bundle!!** GBX0A - Alpha! Camera!

Please read this entire post!
<<<This is a link to the... FAQ Click it!!>>>​
I have created a complete bundle of GingerBread with the newest kernel from GIT (Feb 28 / 1276), and the newest rootfs from GIT (Feb 24).
Please, feel free to DONATE to the XDAndroid project!
Every little bit helps! We don't make empty promises, we just provide solid and complete builds. No ETA's, no threads without download links or instructions... Enjoy!
Directions:
1. Download the full bundle (zip). (Updated Mar. 11 2011)
If instead you just want the system.ext2 (zip) file (updated Mar. 25 2011) by itself... Don't download this unless you know you want to update!!
2. Extract it. You’ll see a folder, GBX0A, copy its contents to the root (base) of your SD card. If you want to run Android from a folder instead of all the files on the root of the card, follow the steps below.
3. Go into the STARTUPS folder. Grab the appropriate startup.txt for your device (if you don't know what device you have, you should read the FAQ), and move it to the root of the card (or where you run haret.exe from. If you want to change the location of the build, put a rel_path= statement in the cmdline section of the startup.txt. Mine is located two folders deep on the SD, so my rel_path=Androids/TP2Ref)
4. Download the ts-calibration file from this post (should work for BLAC) and extract the .zip to where you run haret.exe from - typically the root or 'base' folder of the SD card. Not within any folders, unless you run haret.exe from a folder!
**If you have issues with the above file, you must calibrate manually. To start manual calibration, just delete any ts-calibration files and boot. Sometimes this doesn't work, and you have to use an older kernel from GIT (I found 1225 works well) and generate the ts-calibration file by booting and pressing the 5 zones. Once you have a good calibration file hold on to it (make 15 copies if it's a really good one ), reboot & go back to the newest kernel from the autobuild service! Thanks**
6. Run haret.exe... Profit!
Let it settle out on the first boot. Many have reported they had to reboot basically because it was so slow - if you let it sit for about 10 mins or so the media scanner can go thru everything, etc. If you want adb in and watch the processes via top, you'll see why the phone seems so slow - there's lots of background processes cranking because this is the first boot .
Troubleshooting:
Please read the... FAQ
If you have any issues with the kernel, feel free to change it:
There are some devices that are having issues with the newest kernels. Please see the kernel autobuild service to get newer or archived kernels. Once you download a replacement kernel, go to where you run haret.exe from - remove your old zImage/modules-xxxxx.tar.gz. Take the new zImage/modules-xxxxx.tar.gz and replace the old ones, same folder - where you run haret.exe from. Make sure the ‘zImage’ is named just that. Do not rename the modules file, do not extract it - should be in .tar.gz format.
In addition, I am using the newest rootfs from GIT - Feb. 10. There are other rootfs options, see F22’s thread if you want to use more keys or move around the home button. Of course, there's always the roofs autobuild service if you want "stock" rootfs images - F22 builds his off of these and modifies them .
See Incremental Updates for more information on this topic of updating!!
Random issues can often be solved by forcing the system to create a new data.img. If you're worried about losing data, Titanium Backup works quite well. If you wish, you can rename the data.img to something else, and let the system create a new one - just to see if it resolves your problem.
Similarly, if you wish try formatting your SD card - I prefer to use the HP Tool - do a full format, FAT32.
Obviously this build is Alpha, and there are going to be problems. The next post will address issues particular to this build - PLEASE READ THESE before asking questions! Feel free to post questions in this thread, I will do my best to address them. Big thanks to stinebd for releasing the system image, and of course the other developers for their hard work on making these kernels available.
stinebd's original post HERE
Mar. 11 2011 Changelog

Things broken in this build:
libgps - explains itself, no GPS and probably no netloc (cell-tower based location)
HW3D is either not working, or just not preset - I ran neocore and let's just say a lot of textures are missing. Got a ridiculous score, but again - no textures, not much to render haha.
This line should be in the startup.txt file if that wasn't obvious .
Thanks to emc02 for that solution!
The keyboard should be fine, but I've had some Blackstone users complain - if you want, switch the keyboard out with another. mr_grisha's original post. Others have said this is a horrible keyboard, and you should just use Swype. I'm a big fan of use what works for you, so you folks make the decision for yourself!
Anything that's broken in Froyo, is probably broken in this build.
Blackstone users - help me flesh out this section! Anything that's not working let me know!

Changelog​ March 25, 2011
Further tuned keyboard sizing to be useful on VGA (also made the key labels bigger)
World-phone settings support (very important for future RIL enhancements especially on CDMA)
Enabled HSPA icon (someone on GSM please let me know if it actually works)

Enabled HSPA icon (someone on GSM please let me know if it actually works).....this does not work on my blackstone.....nor does it work on frx06.......overall gbxoa and frx06 works resonable well.....

Startup.txt that works with frx06 and gbx0a
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2030
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msm_blackstone_pad.vibrate=1 msmvkeyb_toggle=off gsensor_axis=-2,-1,3 msmsdcc_nopwrsave rel_path=GBX0A"
boot
use as "rel_path=*****",where ***** is the name of the folder where haret and other files are located (GBX0A in this example),eg if using stock names use FRX06 for frx06 and GBX0A for gbx0a
sensor rotation should be as it is in the text above
also stock android keyboard doesn't work,and keyboard suggested in first post works a bit crappy (with all due respect),so you should use some other,i personally use swype and it doesn't matter if you swype or just type,because swype is great for typing too,it's fast and responses instantly (unlike betterkeyboard)
i think F22's rootfs are modified to fit rhodium which has keyboard and different button mapping so there is no need to use it...you know,no need for additional code lines which are not necessary
i suggest using zeam launcher it's faster and lighter than the stock one
what else does not work:
led notifications (do not work at all,also if you plug in the cable in WM before you run haret, orange notification(or green if it's fully charged) will continue to glow,so our android has no control over it,not even to turn it off)
front camera
(will add if i remember something)
what works especially good
overall speed and performance is great
the build is stable,i almost never got SOD,sometimes you have to FC apps,but very rarely....anyway, performance mesmerizes you so well that you don't even notice those issues
calls are perfect,no "turn speaker on/off" bug,no rejecting calls
if you want to be able to install more apps,go to this thread and grab the data.img maker (resize tool)
http://forum.xda-developers.com/showthread.php?t=824154
if you need storage access,use wifi explorers,they proved very good solution for not being able to access sotrage via usb

welard said:
Enabled HSPA icon (someone on GSM please let me know if it actually works).....this does not work on my blackstone.....nor does it work on frx06.......overall gbxoa and frx06 works resonable well.....
Click to expand...
Click to collapse
Yea, IIRC the new RIL is required to properly show H. Does it show in WinMo? Thanks for the feedback .
farukb said:
not sure if pmem.extra=1 is needed at all and does it perfor better without it,i read somewhere that it does....maybe arrrghhh knows
use as "rel_path=*****",where ***** is the name of the folder where haret and other files are located (GBX0A in this example),eg if using stock names use FRX06 for frx06 and GBX0A for gbx0a
sensor rotation should be as it is in the text above
i've attached ts-calibration for blackstone,so if anyone needs it,it is precisely calibrated....additionally if someone wants to do it by himself,he (she) should use 11** kernels (current are 13**),because calibraiton feature was removed from later kernels
Click to expand...
Click to collapse
Just saw this. Do I need to change anything in the startup.txt file for Blackstone? rel_path is up to you, pmem.extra is deprecated. Please don't use it - won't hurt anything, but it does nothing .

arrrghhh said:
Just saw this. Do I need to change anything in the startup.txt file for Blackstone? rel_path is up to you, pmem.extra is deprecated. Please don't use it - won't hurt anything, but it does nothing .
Click to expand...
Click to collapse
yeah...i read that...think it was your post i remember you being allergic to that line
that in blue and red was for user who don't know how to do it,just a little hint....also i think provided startup.txt is ok,i just posted this so someone who maybe modified it or lost it can have it easily without having to download whole 120mb package

farukb said:
yeah...i read that...think it was your post i remember you being allergic to that line
that in blue and red was for user who don't know how to do it,just a little hint....also i think provided startup.txt is ok,i just posted this so someone who maybe modified it or lost it can have it easily without having to download whole 120mb package
Click to expand...
Click to collapse
Ah no worries. Let me know if there is something you think I should change, I don't have a Blackstone and I'm always looking to improve the process for you guys!

arrrghhh said:
Yea, IIRC the new RIL is required to properly show H. Does it show in WinMo? Thanks for the feedback .
Just saw this. Do I need to change anything in the startup.txt file for Blackstone? rel_path is up to you, pmem.extra is deprecated. Please don't use it - won't hurt anything, but it does nothing .
Click to expand...
Click to collapse
yes it shows in window....thanks

what else does not work:
led notifications (do not work at all,also if you plug in the cable in WM before you run haret, orange notification(or green if it's fully charged) will continue to glow,so our android has no control over it,not even to turn it off)
front camera
if you use glemsom kernels your audio will stutter a bit,you can overcome this by using g3rm0's kernel found in this forum section....although it'd be nice if someone implemented anti-stuttering into glemsom(xdandroid official) kernels
(will add if i remember something)
what works especially good
overall speed and performance is great
the build is stable,i almost never got SOD,sometimes you have to FC apps,but very rarely....anyway, performance mesmerizes you so well that you don't even notice those issues
calls are perfect,no "turn speaker on/off" bug,no rejecting calls
if you want to be able to install more apps,go to this thread and grab the data.img maker (resize tool)
http://forum.xda-developers.com/showthread.php?t=824154
copied everything to 5th post,so it's all in one place

farukb said:
what else does not work:
led notifications (do not work at all,also if you plug in the cable in WM before you run haret, orange notification(or green if it's fully charged) will continue to glow,so our android has no control over it,not even to turn it off)
front camera
if you use glemsom kernels your audio will stutter a bit,you can overcome this by using g3rm0's kernel found in this forum section....although it'd be nice if someone implemented anti-stuttering into glemsom(xdandroid official) kernels
(will add if i remember something)
what works especially good
overall speed and performance is great
the build is stable,i almost never got SOD,sometimes you have to FC apps,but very rarely....anyway, performance mesmerizes you so well that you don't even notice those issues
calls are perfect,no "turn speaker on/off" bug,no rejecting calls
Click to expand...
Click to collapse
all above quoted the same for me to......sometime loading apps can sometime take time to load and battery life falls quickly when downloading from market.........

farukb said:
also stock android keyboard doesn't work,and keyboard suggested in first post works a bit crappy (with all due respect),so you should use some other,i personally use swype and it doesn't matter if you swype or just type,because swype is great for typing too,it's fast and responses instantly (unlike betterkeyboard)
Click to expand...
Click to collapse
What recommendation do you have? I didn't think Swype was free..?
farukb said:
i think F22's rootfs are modified to fit rhodium which has keyboard and different button mapping so there is no need to use it...you know,no need for additional code lines which are not necessary
Click to expand...
Click to collapse
Probably true, I'll take that part out thanks.
farukb said:
what else does not work:
led notifications (do not work at all,also if you plug in the cable in WM before you run haret, orange notification(or green if it's fully charged) will continue to glow,so our android has no control over it,not even to turn it off)
Click to expand...
Click to collapse
orly... that's an odd bug. It seems that the hardware is not initialized by Android...
farukb said:
front camera
Click to expand...
Click to collapse
I'll add it, but don't expect it to work anytime soon .
farukb said:
if you use glemsom kernels your audio will stutter a bit,you can overcome this by using g3rm0's kernel found in this forum section....although it'd be nice if someone implemented anti-stuttering into glemsom(xdandroid official) kernels
Click to expand...
Click to collapse
I remember this bug, related to the battery code. g3rm0's kernel isn't such a good solution, it just kills the battery provider... I'll see if I can bug a dev into fixing it. Not sure what the actual problem is - does this persist even in the newest autobuild kernels?
farukb said:
@arrrghhh, i think you should remove the sensor rotation part of the post,because could confuse people...but then again you're the boss,so do as you please
Click to expand...
Click to collapse
For the DIAM? Is that not required? Sorry 'bout that. I removed it . I want this to be a Blackstone-specific thread, after all it is in the Blackstone forum. So anything I can do to help newbies with Blackstones is great. Keep up the feedback, and let me know how I can improve!
welard said:
all above quoted the same for me to......sometime loading apps can sometime take time to load and battery life falls quickly when downloading from market.........
Click to expand...
Click to collapse
Yup... apps loading for a while are partially due to the old hardware. Some of it might be the SD card being slow... NAND won't be a ton faster, but should give a little boost.
Battery life falls quickly because the battery driver is inherently flawed. There's some new battery software (SCBS) and it should improve this, but it doesn't seem like it'll be implemented into mainline anytime soon (many devices need support...)

arrrghhh said:
What recommendation do you have? I didn't think Swype was free..?
Probably true, I'll take that part out thanks.
orly... that's an odd bug. It seems that the hardware is not initialized by Android...
I'll add it, but don't expect it to work anytime soon .
I remember this bug, related to the battery code. g3rm0's kernel isn't such a good solution, it just kills the battery provider... I'll see if I can bug a dev into fixing it. Not sure what the actual problem is - does this persist even in the newest autobuild kernels?
For the DIAM? Is that not required? Sorry 'bout that. I removed it . I want this to be a Blackstone-specific thread, after all it is in the Blackstone forum. So anything I can do to help newbies with Blackstones is great. Keep up the feedback, and let me know how I can improve!
Yup... apps loading for a while are partially due to the old hardware. Some of it might be the SD card being slow... NAND won't be a ton faster, but should give a little boost.
Battery life falls quickly because the battery driver is inherently flawed. There's some new battery software (SCBS) and it should improve this, but it doesn't seem like it'll be implemented into mainline anytime soon (many devices need support...)
Click to expand...
Click to collapse
will we see meny of these fixes in frx07 and gingerbread in the next release? (nice to see things are happening here again by the way)

@argh
swype is free,you just need to register and you gain access to swype beta
it's called beta because it is made for devices that don't come with if out of the box and therefore are still developing it,but it works great,nevertheless

welard said:
will we see meny of these fixes in frx07 and gingerbread in the next release? (nice to see things are happening here again by the way)
Click to expand...
Click to collapse
well actually,nothing is happening at all all this is available since march (except for some of the incremental updates which chronologically came out later)

farukb said:
well actually,nothing is happening at all all this is available since march (except for some of the incremental updates which chronologically came out later)
Click to expand...
Click to collapse
what mean is help for making our blackstone run better because there was no one here to tell the problems we face on frx06 and gingerbread......now that arrrghhh is looking into our problems things mite just happen now.........

welard said:
what mean is help for making our blackstone run better because there was no one here to tell the problems we face on frx06 and gingerbread......now that arrrghhh is looking into our problems things mite just happen now.........
Click to expand...
Click to collapse
they might,but arrrghhh is a tester,not sure if he is a dev himself,but he could help pursue devs to do it
as for improvements,very few improvements happened at all over last few months to any device supported by xdandroid project

welard said:
what mean is help for making our blackstone run better because there was no one here to tell the problems we face on frx06 and gingerbread......now that arrrghhh is looking into our problems things mite just happen now.........
Click to expand...
Click to collapse
I was always around, but having dedicated threads in the Blackstone section will help. I tried to get others to create threads to support Blackstone, but I guess no one ever did... So here I am! Trying to support without a device.
If anyone feels like donating a device, it would be much appreciated. XDAndroid will pay shipping if you're willing to donate the device to a dev!
farukb said:
they might,but arrrghhh is a tester,not sure if he is a dev himself,but he could help pursue devs to do it
as for improvements,very few improvements happened at all over last few months to any device supported by xdandroid project
Click to expand...
Click to collapse
This is not true! There's been a ton of development over the last few months... It happens in spurts, but there has been quite a bit.
I'm not much of a dev (played around with init, working on getting rid of manual ts-calibration) but I am 'lead tester' for the project, I maintain the wiki, releases, and track bugs on the bugtracker.

arrrghhh said:
I was always around, but having dedicated threads in the Blackstone section will help. I tried to get others to create threads to support Blackstone, but I guess no one ever did... So here I am! Trying to support without a device.
If anyone feels like donating a device, it would be much appreciated. XDAndroid will pay shipping if you're willing to donate the device to a dev!
This is not true! There's been a ton of development over the last few months... It happens in spurts, but there has been quite a bit.
I'm not much of a dev (played around with init, working on getting rid of manual ts-calibration) but I am 'lead tester' for the project, I maintain the wiki, releases, and track bugs on the bugtracker.
Click to expand...
Click to collapse
i have not a device to donate.....but if we all donate for a device that would speed things up much faster...... i think you should start a new thread for donate for a blackstone device......im sure theres lots of blackstone users willing to do this because the end result will pay off for all of us.......

i had a sod and now i can't boot,the animation just keeps looping...hw buttons vibrate then i touch them,but do not work....power button doesn't work either
happened to me once before,but i don't know what i did to solve it...i maybe deleted the data.img
this time i tried to wipe and format the partition,didn't help
i tried with fresh files (except for the data.img) but still nothing...
@arrrghhh: wanna swap with me for your rhodium,if you want it badly?
@werald and others:if we are going to donate a device,it'd be best to donate it do a dev,maybe stinebd,don't know