Develop Bugs

TouchFlo Finally Working!!!!

Managed to get Touch Flo working tonight (between 5&6am), i am using Shadow as ROM, the steps i completed are as follows:
Install Instructions
1) install touchflo and softreset
2) Delete the bio.lnk in Windows/startup
3) Delete the reg file in HKLM/Software/HTC/Biotouch/Biotouch ver
4) Map Touchflo to any free button
5) Softreset
6) Start touchflo, then go to Windows folder and start Biotouch.exe
(These are exactly the steps i took, i dont know anything else, these just worked for me and i posted them in the hope they might work for someone else!!)
Usage Instructions
1) Press the hardware button you specified to start toughflo
2) Press the hardware button you specified to rotate the cube
3) Press the red call end button to stop it and get back to the main screen
If there are any hangs, uninstall TouchFlo and start again
There are 2 irritating things (very minor!!!)
1) Cant be used with finger like real touchflo i.e. cannot drag finger up to launch or down to exit (yet!!)
2) The hardware button rotates the screen as well as starting touchflo, this might not sould like much but, for example, if the last screen you were looking at was the Music/Photos/Videos page and you pressed the red call end button to get out of TouchFlo, and you want to go back to the Music/Photos/Videos page, you will press the hardware button to start TouchFlo, but at the same time as starting it, it also rotates the screen so it is on the page after the last page you were using, resulting in needing to press the hardware button once to start TouchFlo and twice more to get back to the screen you left off at.
As i said these are minor but this should work for now untill it is properly sorted out
Enjoy
Regards

hey
i will mod my cab and release a beta once i confirm its working.
thanks again

Awesome work guys, all of you cannot be thanked enough. It's a thankless job sometimes, but this ain't one of them! Keep it up

jasjamming said:
hey
i will mod my cab and release a beta once i confirm its working.
thanks again
Click to expand...
Click to collapse
i have done no modification to your alpha cab, i followed some instructions i found on your other site and they didnt work for me, black screens, massively slowed down Shadow, so i did it slightly differently and it worked first time, nice and fast and everything seems to be working!!!
As i said i am using your Shadow rom, no mods, my own software installed thru cabs, and using the instructions detailed above
I must say thanks to you for releasing the alpha for me to play with!!!
Thanks again JJ
P.S. is it ok to PM you i have afew questions that are off topic here!!
Regards
Bennec83

OK, this all sounds promising, but are you saying that you still cannot use your finger to do anything? That everything still needs to be done via buttons? Can you use your finger to scroll thru lists? Its progress that it is working at least, but isn't being able to use your finger the whole point? Or perhaps I'm misunderstanding you.

jomo25 said:
OK, this all sounds promising, but are you saying that you still cannot use your finger to do anything? That everything still needs to be done via buttons? Can you use your finger to scroll thru lists? Its progress that it is working at least, but isn't being able to use your finger the whole point? Or perhaps I'm misunderstanding you.
Click to expand...
Click to collapse
Dude,
First Point: it is 6:36am i have been messing with this thing since 4am, i have a disertation to research and im taking time out to do this, everyone on almost every forum(Trinity, Wizard, Hermes, other sites etc etc) wants this working, and we have it!!!
Second Point: This is an ALPHA RELEASE that basically means it only works sometimes, i have sat here installed checked it works, flashed my f'ing phone with the Shadow ROM, so there was nothing there that could possible help this work and installed it again.
Third Point: Yes the idea is that you use your finger for everything, but as the second point states this is an ALPHA, later releases will have this im surebut for now i appologise for not sorting that but im tired, y dont you try and get it working with your finger? (that wasnt ment to sound perverse but it does!!!)

i keep getting the black screen no graphics? please help ?

bennec83 said:
2) The hardware button rotates the screen as well as starting touchflo, this might not sould like much but, for example, if the last screen you were looking at was the Music/Photos/Videos page and you pressed the red call end button to get out of TouchFlo, and you want to go back to the Music/Photos/Videos page, you will press the hardware button to start TouchFlo, but at the same time as starting it, it also rotates the screen so it is on the page after the last page you were using, resulting in needing to press the hardware button once to start TouchFlo and twice more to get back to the screen you left off at.
As i said these are minor but this should work for now untill it is properly sorted out
Click to expand...
Click to collapse
Why not use the scroll weel for that? Like> up is forward and down is back

leoiden said:
i keep getting the black screen no graphics? please help ?
Click to expand...
Click to collapse
if you can give me 15 mins i have jus run into a problem with my install method, ive jus installed an app and it totally fubar'd it, now i get nothing at all!!! jus give me a sec, ill pm you wen i sorted if you like?

Bram87 said:
Why not use the scroll weel for that? Like> up is forward and down is back
Click to expand...
Click to collapse
Good question/idea!! do you know to implement that?

once i SR
it gives me blank screen again
I m running on LSVW rom

the cube
the cube works perfectly with this rom... i got no slow downs, no need to delete files or anything like that, all you need to do is map a key to touch flo
http://forum.xda-developers.com/showthread.php?t=312604

leakwoon said:
once i SR
it gives me blank screen again
I m running on LSVW rom
Click to expand...
Click to collapse
i think the thing you will find with this is the fact that this is deoendant on the ROM used too!! i cannot provide support for this i dont really know the ins and outs of it, i just posted what i did to get it to work!!!
the official link for problems and developing is here:
http://www.4winmobile.com/forums/htc-hermes/10127-touchflo-alpha-testing-discussion.html
if you read this it seems that the functionality of this is very dependant on the ROM

sgabriel001 said:
the cube works perfectly with this rom... i got no slow downs, no need to delete files or anything like that, all you need to do is map a key to touch flo
http://forum.xda-developers.com/showthread.php?t=312604
Click to expand...
Click to collapse
hard reset your phone!!! if it works then you are ok, if you get a black screen get back in the boat with the rest of us!!!

bennec83 said:
hard reset your phone!!! if it works then you are ok, if you get a black screen get back in the boat with the rest of us!!!
Click to expand...
Click to collapse
i just got it to work with Black Shadow.. but a few hours ago i installed Shap's rom and i installed touch flo and it worked perfectly, i didn't had to delete any keys or go into /windows folder or any of that stuff with schap's rom
another thing* for those of you having problems, try installing the audiomanager today plug in to see if you get different results, i have noticed that whenever the plugin is not in the today screen the cube seems to not work*

I assume this only works on a Mobile 6 Rom, and not on Mobile 4 (WM2003SE)

VoodooBOB said:
I assume this only works on a Mobile 6 Rom, and not on Mobile 4 (WM2003SE)
Click to expand...
Click to collapse
you assume right

sgabriel001 said:
i just got it to work with Black Shadow.. but a few hours ago i installed Shap's rom and i installed touch flo and it worked perfectly, i didn't had to delete any keys or go into /windows folder or any of that stuff with schap's rom
another thing* for those of you having problems, try installing the audiomanager today plug in to see if you get different results, i have noticed that whenever the plugin is not in the today screen the cube seems to not work*
Click to expand...
Click to collapse
This uses HTC audio manager so the audio plugin shouldnt matter, i have just done a sprite restore after my F*** UP, and after a hard reset it is givin me the black screen again.
Im getting really P*ssed off with this i aint slept yet, i cnt let this stupid thing beat me

bennec83 said:
This uses HTC audio manager so the audio plugin shouldnt matter, i have just done a sprite restore after my F*** UP, and after a hard reset it is givin me the black screen again.
Im getting really P*ssed off with this i aint slept yet, i cnt let this stupid thing beat me
Click to expand...
Click to collapse
lol give installing the audio plugin a try just to see what happens, if it doesn't work just delete it but if you really are that desperate install schap's rom just for a minute and try it there

sgabriel001 said:
lol give installing the audio plugin a try just to see what happens, if it doesn't work just delete it but if you really are that desperate install schap's rom just for a minute and try it there
Click to expand...
Click to collapse
Doesnt work, i dont get y someone doesnt just fix this f****** thing, 12 hours i have sat here with this, it is 8am this was a night not worth trying to help out, i understand now why people ignore you, i stupidly took a look at this coz so many people were moaning about it, i know now why i shouldnt bother 12 hours and so many attempts for nothing
not even microsofts releases have this many problems this is a joke

[Donut 1.6][12-10][Neopeek Team Donut by Kenia][SuperFast!!]

Original thread: http://forum.xda-developers.com/showthread.php?p=8590273#post8590273
For RAPH users : delete ts-calibration file, before first start.
Download : in original thread.
Im testing it now on my RAPH100
+very..very..very fast
+wifi works
+nice
+battery indicator seems to work
+market works
-BT dont work

hello guys. I'm new to this. This build is great and fast but,I still can play 3d games. How can we make this happen? Thanks again for this great build.
Sent from my Neopeek Team Donut by Kenia using XDA App

tiad8 said:
hello guys. I'm new to this. This build is great and fast but,I still can play 3d games. How can we make this happen? Thanks again for this great build.
Click to expand...
Click to collapse
Crap a snapdragon core into your phone?

sorry. arrrghhh. I didn't mean to say that. I have reef system on my phone sprint htc touch pro 2. It runs great. Thanks man for you support
Sent from my Neopeek Team Donut by Kenia using XDA App

hy ....this rom is so fast ..\but on my diamond i cannot able to play video plzzzzz help me .....thanks

Just tried this ROM and noticed that the £ symbol doesnt come up when i press FN and W (i have a Raph).
Also how would I put HTC sence UI on this ROM? I looked around on the forum and I cant seem to find any downloads for it.
Thanks,
-c

ceanth said:
Just tried this ROM and noticed that the £ symbol doesnt come up when i press FN and W (i have a Raph).
Also how would I put HTC sence UI on this ROM? I looked around on the forum and I cant seem to find any downloads for it.
Click to expand...
Click to collapse
Sounds like the kbd layout is incorrect. Make sure that's set in your startup.
Can't just 'put' sense on... it's part of the build so you need an image that has sense in it. There's a 2.1 build called 'rosie' that has sense on it, but it's awful.

ah right, which would probably explain why i couldnt find it
My startup looks like this:
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 rel_path=Donut"
boot
What would i need to change? I have an O2 version of the Raph but in the download files there is a Raph and a Raph800. What is the difference between them?
Thanks,
-c

RAPH800 = Sprint RAPH. You can see which RAPH you have by pulling your battery, there will be a line somewhere saying RAPHXXX. If you're on O2 it's probably a RAPH100 or 110.

RAPH120
Been playing around with the ROM and i like it a lot, its amazing how fast it is!
I noticed that sometimes i manage to accidently bring up an overview of the 3 home screens at the bottom, how do i do this? I tried holding the ok centre button but that didnt work.
My brother has a touch pro 2 so will try this ROM out on his device.
The device did not like having the USB cable plugged in, it prompted to mount the SD card but then locked up the notification screen (where you slide down from the top).

WOW!
WOW! Really great Android ROM for RAPH100! Looks nice and works very fast
The only bug i've found so far, is that the earpiece in incoming calls don't work... I'm gonna have a look at the original thread
@ceanth
Double tap the Home screen for the previews...

ceanth said:
RAPH120
Been playing around with the ROM and i like it a lot, its amazing how fast it is!
I noticed that sometimes i manage to accidently bring up an overview of the 3 home screens at the bottom, how do i do this? I tried holding the ok centre button but that didnt work.
Click to expand...
Click to collapse
Try hitting the power button once.

Hitting the power button works a treat
I am unable to get gps working with this ROM. It's a shame because it would have been perfect for me but I need gps

ceanth said:
Hitting the power button works a treat
I am unable to get gps working with this ROM. It's a shame because it would have been perfect for me but I need gps
Click to expand...
Click to collapse
gps, accelerometer will most likely never work, libs would have to be backported for them to work on donut, and there no one interested in doing that right now, and most likely never will be.

just a question....how can I check if I'm in umts mode???
when I scan the mobile sources I can't see my operetor: 3G ITA
ciao scusate ma come faccio a vedere se sono collegato alla rete 3G??

[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

[TESTING] XDAndroid GBX0C 2.3.7 Build

Hey folks,
This is a completely new build, with all the new changes baked in. We wanted to do a semi-official test release to collect bugs and hopefully do a formal official release with everything settled. The main pain point is the CSV files (see pre-install prep).
So a brief overview:
New acoustic routing code baked in. Should fix most if not all audio routing problems, and will provide more debugging if stuff does go wrong. Also allows for more granular tweaking, see the CSV files.
GPS fixes for GB - GPS not only works in GB now, but it doesn't kill sleep! I was able to use GPS, get a solid lock, and put the device to sleep no problem.
BT should work & well with the new acoustic code. Post results.
RHOD users now have a choice of kernels. .35+ all have the new acoustic - so .35, .39, 3.0 and 3.1 are all fair game now... This is bundled with .27!!
Keep in mind, autobuild .27 kernels will produce no audio in this build... Obviously the bundled kernel will work, and the absolute newest .27 autobuild kernel does work now - Feb.27 2012 or newer.
rootfs tweaks - first, it will detect which kernel you're on (.27 or .35+) and automatically apply the correct firmware. Second, is it will always copy/extract the modules... failures there were getting annoying, and this is surefire if brute-force...
Few Easter egg apk's...
Probably a lot I'm forgetting, this might change
Pre-Install Prep REQUIRED!!!​
This step is crucial, and I forgot all about it! You must copy all of the *.CSV file from your WinMo ROM - these are in the \Windows\ directory. There's a very easy way to do this. It involves the Total Commander app for WinMo (Direct Link for the perpetually lazy...) (included in EnergyROM and others probably).
Now you're in Total Commander looking at your \Windows\ directory. Whew... lots of files. Fear not! Hit the "CTRL" button, then the green "Plus" button. This opens the Select/Unselect files dialog. Put in *.csv, press "select" and voila. All CSV files are selected. Now - File -> Copy/Move -> I want you to copy these (should be 10) files to the ROOT of your SD card. No folders!!! This is hardset right now, until we get it all implemented into the build properly. Thanks!
Install​
Assuming you've done the pre-install prep; this is installed just like the other XDAndroid builds - grab your startup.txt (don't forget rel_path= if you don't have it at the root of the SD!), ts-calibration and boot!
Download

Caveats:​
Audio stutters every 10sec. The only fix I've heard is using a kernel from G3rmo (unfortunately it is old), or
Code:
su
kill -9 28
Which kills the [battery] process. I'm sure this will have negative effects on the battery meter/battery life...
SD Card not working...? "Waiting for SD Card" appearing on boot...? Try putting this command in your startup.txt
Code:
msmsdcc_1bit msmsdcc_fmax=14000000 msmsdcc_nopwrsave
See gummbah30's post reminding us of these commands.
SD Card has partitions? (If you used a non-XDAndroid build the answer is YES) Then you need to add "no_partitions" to your startup.txt. Between the quotes on the set cmdline line. Do not put it on its own line, it goes in between the quotes! Make sure there is one space between each item.
BT might still be flaky
The CSV files from my BLAC100 are attached for the lazy. I'd like to gather CSV's from each RHOD, I'm curious if any ROM devs have changed them out either... This could get interesting. If you folks don't mind, post up your CSV's, point out differences with mine, etc... We're trying to figure out how to unify these, if possible! Thanks!
Keyboard tiny/unusable? Either change the IME (long press on the input box) Get rid of it! I've heard "Hackers Keyboard" is a good alternative - many options. There's also "Better Keyboard", Swype, etc... Side load the APK using AndroidApps, adb install, etc.
Please post back any issues, enjoy!
GBX0C Changelog​​
Camcorder: Now works (tested on rhodium).
Acoustic: Bug-fix : correct random loss of dual(rear)-mic.
MMS: Bug-fix: Slides with zero duration on Sprint.
Gps: Bug-fix: Init/de-init sequence fix (correct gps not starting up after being unchecked in Settings).
Gps: Bug-fix: End gps session with a correct rpc call (relevant to amss6125 devices).
Gps: Bug-fix: Don't send delayed position requests after session has ended (possibly relevant to Navigation issues).
Gps: New feature: Xtra (aGPS) -> verified to work on rhodium/cdma raph.
X1 specific: Screen rotation patch.
Added tytung's GPS injector app to AndroidApps\Other as well as updating/cleaning up some apps in AndroidApps.
Modified rootfs for newest apsta firmware & wifi firmware - wifi tethering now works flawlessly in the newest kernels! .27 is still bundled for the record...

logcat attached
just like to say speakers when making a call works........loud rear speakers (speakerphone) don't work nor does sound in touch selection when going threw screen selection and playing music does not work also.....hope this helps

welard said:
just like to say speakers when making a call works........loud rear speakers (speakerphone) don't work nor does sound in touch selection when going threw screen selection and playing music does not work also.....hope this helps
Click to expand...
Click to collapse
Interesting, does any sound work...? Does it play thru the earpiece instead of the rear speaker? What about previewing ringtones? Next time you pull a logcat, make sure to use -v time. Using GetLogs makes it much easier .
Thanks for testing btw. The more the merrier! If we're going to make this change global, we want to make sure no devices are left in the dust. So it's up to you guys to test and ensure that it works properly! If it doesn't, we'll try to fix it.
If anyone feels like hopping on #xdandroid on freenode while testing, that would be great! Thanks again!

i attached the file i found on sd card after pulling the logs with getlogs. i hope this is the file you wanted.
i just added following commands to my startup, because i cant boot without them:
msmsdcc_1bit msmsdcc_fmax=14000000 msmsdcc_nopwrsave

am20033 said:
i attached the file i found on sd card after pulling the logs with getlogs. i hope this is the file you wanted.
i just added following commands to my startup, because i cant boot without them:
msmsdcc_1bit msmsdcc_fmax=14000000 msmsdcc_nopwrsave
Click to expand...
Click to collapse
Those commands are necessary if you have a SD card that doesn't play nicely. If you need 'em, put 'em in.
Thanks for the logs, I'll pass them on. Anything you can say about 'em? What happened during the logs...? Please be as specific as possible. The more information, the better.

Bump...
I made a mistake. Messed up bad folks! I forgot an extremely crucial step... See the first post! Pre-install Prep .
am20033 already has given pretty good feedback, once having done this step. So send it through the ringer guys, c'mon!

arrrghhh said:
Bump...
I made a mistake. Messed up bad folks! I forgot an extremely crucial step... See the first post! Pre-install Prep .
am20033 already has given pretty good feedback, once having done this step. So send it through the ringer guys, c'mon!
Click to expand...
Click to collapse
wooooow......thats all i can say......loudspeaker in call works perfect.... incall audio perfect.......touchsceen click works well......overall system louder......have not tested music but in (sound settings)....ringtone, media and alarm works well...bluetooth audio headset has lots of background noise u can hear the other person but not very well but audio is rooted to bt headset.....will test further and report back asap......
p.s. there are 5 c.s.v file in window mobile on blackstone....ive re-check and found 5.....if anyone find more please let me know, but far as i know there is 5 not 10.....thanks

welard said:
wooooow......thats all i can say......loudspeaker in call works perfect.... incall audio perfect.......touchsceen click works well......overall system louder......have not tested music but in (sound settings)....ringtone, media and alarm works well...bluetooth audio headset has lots of background noise u can hear the other person but not very well but audio is rooted to bt headset.....will test further and report back asap......
p.s. there are 5 c.s.v file in window mobile on blackstone....ive re-check and found 5.....if anyone find more please let me know, but far as i know there is 5 not 10.....thanks
Click to expand...
Click to collapse
Good deal! Some headsets seem to work better than others - we'll have to work on that once everything has settled. Glad everything else is working well!
As for there only being 5 CSV's, that might be true for Blackstone. What WinMo ROM are you on...? Perhaps some other users can verify. On my RHOD running EnergyROM there's definitely 10 CSV files in \Windows\. I might ask everyone post theirs so we can detect any differences - so if anyone would like to post all the CSV's they have in a zip file here that would be great!

arrrghhh said:
Good deal! Some headsets seem to work better than others - we'll have to work on that once everything has settled. Glad everything else is working well!
As for there only being 5 CSV's, that might be true for Blackstone. What WinMo ROM are you on...? Perhaps some other users can verify. On my RHOD running EnergyROM there's definitely 10 CSV files in \Windows\. I might ask everyone post theirs so we can detect any differences - so if anyone would like to post all the CSV's they have in a zip file here that would be great!
Click to expand...
Click to collapse
im on window 6.5 kwbr rom,....im not sure if files are different than in the orignal 6.1 for blackstone........thanks

welard said:
im on window 6.5 kwbr rom,....im not sure if files are different than in the orignal 6.1 for blackstone........thanks
Click to expand...
Click to collapse
Post those CSV's if you could!

arrrghhh said:
Post those CSV's if you could!
Click to expand...
Click to collapse
hear are my csv's......thanks...

arrrghhh said:
Post those CSV's if you could!
Click to expand...
Click to collapse
Thank's Arrrghhh , that is my best news today .
I'm a former HD owner and today i have a HD mini Photon , my current Android ROM is working very well .
The only real problem for me is the audio routing . Could you give me some help to test this in Photon? I can try to change my ROM in order to apply your fix. Don't worry if i don't have success doing that , i know devices are not the same and i don't disturb you .
Because this is HD forum if you want you can PM me.
Thank's a lot

cbolumar said:
Thank's Arrrghhh , that is my best news today .
I'm a former HD owner and today i have a HD mini Photon , my current Android ROM is working very well .
The only real problem for me is the audio routing . Could you give me some help to test this in Photon? I can try to change my ROM in order to apply your fix. Don't worry if i don't have success doing that , i know devices are not the same and i don't disturb you .
Because this is HD forum if you want you can PM me.
Thank's a lot
Click to expand...
Click to collapse
If you're on a native Android device and you're having audio routing problems I would talk to the developer of the ROM. If you re-read the first post, I detail why we have audio routing problems to day, and why this test build fixes those issues.
Your issue is completely different and entirely unique compared to our woes. Sorry.

arrrghhh said:
If you're on a native Android device and you're having audio routing problems I would talk to the developer of the ROM. If you re-read the first post, I detail why we have audio routing problems to day, and why this test build fixes those issues.
Your issue is completely different and entirely unique compared to our woes. Sorry.
Click to expand...
Click to collapse
Thank's arrrghhh , Photon is a WM 6.5 device (maybe the last HTC WM device) and the issue is the same I had in my blackstone for two years. (BT pairing but not audio ) it was my bigger problem there and with photon .... having the same problem..
I'm reading some times the blackstone thread looking for some light about this issue and today i found your thread. Trust me , the issue is the same and the way to resolve it must be similar.
I had success booting android HD blackstone roms in photon (more or less) and i will try to test your build. at the moment the booting animation start well but never end.
I'm changing some modules to obtain a bootable build but i don't know which libs or kernel modules are you changing here.
Thank's

cbolumar said:
Thank's arrrghhh , Photon is a WM 6.5 device (maybe the last HTC WM device) and the issue is the same I had in my blackstone for two years. (BT pairing but not audio ) it was my bigger problem there and with photon .... having the same problem..
I'm reading some times the blackstone thread looking for some light about this issue and today i found your thread. Trust me , the issue is the same and the way to resolve it must be similar.
I had success booting android HD blackstone roms in photon (more or less) and i will try to test your build. at the moment the booting animation start well but never end.
I'm changing some modules to obtain a bootable build but i don't know which libs or kernel modules are you changing here.
Thank's
Click to expand...
Click to collapse
Oh I see.
Others have this same problem...? I'm wondering if it's your headset, or the port. Do you know how audio routing works on the port for the Mini? Is it a kernel-only affair, or does userland effect it...?

arrrghhh said:
Oh I see.
Others have this same problem...? I'm wondering if it's your headset, or the port. Do you know how audio routing works on the port for the Mini? Is it a kernel-only affair, or does userland effect it...?
Click to expand...
Click to collapse
Is a general problem , I don't know if the problem is only in the kernel but i can give you some issues we have with the sound:
- the stereo wired headset sound only works if we use headset with micro , if we use headset without micro the sound is mono.
- The fm radio sound only works if we start de FM radio in WM before run haret , in other case we have only 5 seconds sound in Android FM radio, after 5 seconds the sound stops suddenly.
- the loudspeaker and sound in general in incoming calls is very low.
- The Bluetooth headset and the bluetooth hand free paired without problems but not redirect the sound.
I think the problem is not so different you want fix here in blackstone.

cbolumar said:
Is a general problem , I don't know if the problem is only in the kernel but i can give you some issues we have with the sound:
- the stereo wired headset sound only works if we use headset with micro , if we use headset without micro the sound is mono.
- The fm radio sound only works if we start de FM radio in WM before run haret , in other case we have only 5 seconds sound in Android FM radio, after 5 seconds the sound stops suddenly.
- the loudspeaker and sound in general in incoming calls is very low.
- The Bluetooth headset and the bluetooth hand free paired without problems but not redirect the sound.
I think the problem is not so different you want fix here in blackstone.
Click to expand...
Click to collapse
The fixes here apply to MSM7k devices. I'm not sure what you would need to port it to other devices... pretty sure our kernel would not work on your phone. That's going to be the hurdle. I would encourage you to analyze the userland stuff tho - that certainly might be useful to you.

arrrghhh said:
The fixes here apply to MSM7k devices. I'm not sure what you would need to port it to other devices... pretty sure our kernel would not work on your phone. That's going to be the hurdle. I would encourage you to analyze the userland stuff tho - that certainly might be useful to you.
Click to expand...
Click to collapse
Thank's arrrghhh , the hD mini have the MSM7227 processor, i will follow here your work.

cbolumar said:
Thank's arrrghhh , the hD mini have the MSM7227 processor, i will follow here your work.
Click to expand...
Click to collapse
Don't misconstrue, I haven't done any of the actual development on this acoustic code .
See Jerome's tree if you want to see where this all started. A few others have cloned his tree and made some modifications. We're still working out the kinks. Perhaps it can help your port as well...
Like I said earlier, I am betting the userland stuff will work for you folks without a ton of changes (don't know for sure!). The kernel stuff for this new acoustic will need to be ported - our kernel will not work on your device.

HTC Desire JB by Vijendrah - Track Pad problem

Hi,
I do not have the access to post in that forum, so I want to just do a check here, does anyone have this similar problem.
ROM : http://forum.xda-developers.com/showthread.php?t=1945441
Problem: Trackpad no longer works in latest v3.0
V3.0 is all and good, the OS I have been waiting for my desire (for 3 years I dare say) However, the track pad is not working. Anyone have this similar problem or is there something I don't know about that I should be doing.
Thanks!

Hi anybody with the above mentioned rom care to chime in? The ROM is great FYI I have been using it for months. Been thinking about getting another HTC desire to flash it to this rom for my mom.

I don't usually use the track pad, but just tested and it seems ok
Sent from my HTC Desire using Tapatalk 2

frosty68 said:
I don't usually use the track pad, but just tested and it seems ok
Sent from my HTC Desire using Tapatalk 2
Click to expand...
Click to collapse
ah ok thanks, no wonder nobody was complaining in the forum thread... now i'm at a lost what to do. you flashed version 3.0 right? i haven't had this issue until 3.0

whimsywhimsy said:
ah ok thanks, no wonder nobody was complaining in the forum thread... now i'm at a lost what to do. you flashed version 3.0 right? i haven't had this issue until 3.0
Click to expand...
Click to collapse
I just verified this and trackpad is working fine here. Am on v3.0 as well. Did you do a full wipe before flashing?

led notification not work in desire on miui 4.1

whimsywhimsy said:
Hi,
I do not have the access to post in that forum, so I want to just do a check here, does anyone have this similar problem.
ROM : http://forum.xda-developers.com/showthread.php?t=1945441
Problem: Trackpad no longer works in latest v3.0
V3.0 is all and good, the OS I have been waiting for my desire (for 3 years I dare say) However, the track pad is not working. Anyone have this similar problem or is there something I don't know about that I should be doing.
Thanks!
Click to expand...
Click to collapse
i have benn using this rom for about three weeks.i don't have this problem or u reflash the rom.
vijendrahs have new work for htc desire: http://forum.xda-developers.com/showthread.php?t=2070704

dvsk69 said:
I just verified this and trackpad is working fine here. Am on v3.0 as well. Did you do a full wipe before flashing?
Click to expand...
Click to collapse
Sorry was busy for a few days, forgot about this thread, yeah I always do full wipe, not sure what I did but unchecking custom actions and then reboot... suddenly the track pad works again. I tried to recreate the problem by checking the custom actions, couldn't reproduce it... maybe it's just my track pad being dirty after 3 years? dunno. Anyway it works again, thanks for taking time to notify me.
Also... the link to the new work... I think I cannot test alpha builds... I really need my phone. but I will donate again if I move to new version haha, his work is great!
p/s anyone kind enough to explain what is the main difference at least between this new work and existing one? I'm kind of a noob and the last time I tried to read a cyanogenmod nightly changelog I almost fainted. Incremental builds from VJ I can understand, the rest... are totally alien to me, even finding the CM changelog was a challenge!

Just FYI I decided to try out the install a2sd from terminal with the Y Y Y command, and then when I tried to revert it back to the Y N Y setting, all my settings/sms/data was gone. So caveat emptor... or maybe you guys already know this, I for one did not.
Anyway now it's my HOME button that has lost functionality, the trackpad is ok... bummer... I didn't know how much I used it until it was gone. Even the settings under System > Hardware keys > Enable Custom Actions did now show a Home Key button (just has a Home key (long press) option)
er... help? I have restarted a few times... doggone it. I want my home button back!

whimsywhimsy said:
Just FYI I decided to try out the install a2sd from terminal with the Y Y Y command, and then when I tried to revert it back to the Y N Y setting, all my settings/sms/data was gone. So caveat emptor... or maybe you guys already know this, I for one did not.
Anyway now it's my HOME button that has lost functionality, the trackpad is ok... bummer... I didn't know how much I used it until it was gone. Even the settings under System > Hardware keys > Enable Custom Actions did now show a Home Key button (just has a Home key (long press) option)
er... help? I have restarted a few times... doggone it. I want my home button back!
Click to expand...
Click to collapse
I reflashed the ROM everything works now, I guess I was lucky never hard this experience before. I guess next time I should have a nandroid back up.
For anyone that just want an idea of what's the difference VJ has posted it himself. Please find notes below ty.
For actual differences between 4.1.2 and 4.2.1 google yourself.
But the improvements from my CM10 v3.0 to CM10.1 v4.2.1 is that:
1. The games which was not able to play in either any of the Jelly Bean version is playing now and better than GB ROM's.
2. Notification lights works
3. FM Works
4. Much Smoother
5. Video play back is very good (No more flickering)
6. Improved HWA
and find out yourself....
What's not working yet?
Same as Evervolv 4.2.1 (We fixed Bluetooth, Notification lights before them)

for me trackpad works fine