Develop Bugs

BLUETOOTH AUDIO : Rhodium + Motorola HT820

I tried to mess around with advanced config tool but had no success listening to music on headset without blanks or skips every time i moved my head...
then i did the HT280 firmware update i just found in the forum but its worst
any of u guys using HT820 and happy with it ?
i remember having to struggle on every HTC to get this working...
seems like this will be never fixed by htc
hope some of you have same material and can post your settings and feedback on your situation
thx

Yep have the Moto too, great headset (a little uncomfortable at times but great audio and features)
No issues here with mine, though I manually changed bitpool settings.
I have found that Advanced Config can cause issues on the Rhodium so adv ise not using it for now, just change your required settings manually.
I'll try and dig out my settings during the week and post back.
If you have manually installed AC then try un-installing and testing.
Cheers,
Beasty

thx for your answer mate, thx for your time to post yours settings eventually
actually i cant uninstall Advanced Config : it s in the custom ROM im using...
i just flashed latest version and didnt install tom tom yet in case it was the problem
but seems like it isnt...as usual with HTC : stereo BT out the box is ****

tnt23 said:
thx for your answer mate, thx for your time to post yours settings
actually i cant uninstall Advanced Config : it was in the custom ROM im using...
i think i got a problem with BTstack since tomtom 7install
i renamed or recopied older versions of those corrupted files...but still i cant add a new device anymore...
Click to expand...
Click to collapse
I am also using NRGZ build, but have not launched AC.
Once I dig out my settings (2moro if I get a chance) I'll post, you may have to hard reset though. I advise not running AC untill we have an updated version.
Also TT7, my version does not replace the BT files, I post the version number for that 2 moro too.
Cheers,
Beasty

ok man ill wont start AC on this new flash yet...
how about WGVA Tweak ?

I am using that headset on my stock Telus TP2 with no problems and have not done any regestry edits to Bluetooth.

tnt23 said:
ok man ill wont start AC on this new flash yet...
how about WGVA Tweak ?
Click to expand...
Click to collapse
Current Bitpool and MaxBitpool I have set to 1e (30) which is the same setting I used on my Universal for years without issue.
Have played 3 songs this am without any lag or skipping using Touch Flo Player. CorePlayer also works flawlessly, haven't tested and don't use M$ Media Player.
HDTweak and other tweak tools I don't like to use so can not comment as most will apply a default setting for certain items. I prefer to only modify what "I" want.
Cheers,
Beasty

[DEV] ION 1.6 (Donut)

Disclaimer: For devs only. Updating to it will wipe your device. I am not responsible of any damage of any sort or data loss or anything.
Google Ion 1.6 for HTC Hero.
This project aims at getting the stock Google Ion Rom to run on HTC Hero. No Rosie or any HTC apps will be ever added to that rom. Once fully functional it could be used as a base for cookers.
Current release: Lox-ION-1.0b3 (logcat)
What works:
- place, receive calls
- wifi
- Market
- GPRS
What does not do far
- bluetooth (logcat seems it is relative to libc.so - Uncompatible with current kernel ?)
- trackball
- compass & accelerometer (with akmd > logcat - with ak8973 > logcat )
- GPS
- camera
Note: devs please test hack and share if you fix anything or have any idea

Great! I hope the rest will be fixed soon!

I second that!

Great to hear it.
are you working on the hardware that doesn't work? and whats the progress.

you forgot to mention that the camera doesnt work aswell
Just flashed it, gonna see what I can get working(if anything).

I'd like to try it - but can you go back by using Nandroid - or reflashing Modaco's ROM ( I'm on 2.3 )

J-Zeus said:
I'd like to try it - but can you go back by using Nandroid - or reflashing Modaco's ROM ( I'm on 2.3 )
Click to expand...
Click to collapse
yes you can

I dont know how gecka feels but could we try and keep this thread informative

Just did a bit of snooping around and the GPS does work, you sure you checked it right? I did a bit of tinkering but none of it was related to the GPS at all. Trackball I'm still not sure about, the keylayouts have the same keycodes but still doesn't seem to want to work. Accelerometer just needs the permission to be granted to execute, except I'm not to sure how to do that cause I'm a bit new to linux. As for the bluetooth, don't get me started, its giving me a headache lol xD

hey i m using this rom and its working beautiful...man nice job and the trackball blinks when a phone is ringing ....but doesnt blind at the time of reminders....but still great job...

What about headphone detection? I know with the other Ion ROMs, when you plugged in headphones, it went unnoticed unless you downloaded an app to manually switch the audio over.

For devs only!
Hi guys,
Please, consider the [DEV] in the subject: this thread is for devs only.
If you don't give any fix, just follow the thread by subscribing to it and don't polute it! Thanks.
For now this build is buggy, you'll certainly find more and more bugs, witch I don't care for now as I want main functionality to work first (bluetooth, gps etc...)

robertosandros said:
Just did a bit of snooping around and the GPS does work, you sure you checked it right?
Click to expand...
Click to collapse
Please read carrefully before posting. GPS in in the "not working" list....
robertosandros said:
Accelerometer just needs the permission to be granted to execute
Click to expand...
Click to collapse
Right! Wrong permissions on witch file ???

Good work gecka,
I'm downloading to have a lookie and install now, see if I can have a go at the trackball.
Can I ask a question though, whats actually involved in fixing these issues?? Is it blind luck playing with config settings and that, or are you getting debug output?

kwiksand said:
Can I ask a question though, whats actually involved in fixing these issues?? Is it blind luck playing with config settings and that, or are you getting debug output?
Click to expand...
Click to collapse
Well, both in fact. The only debug output I get is from logcat and device logs.
Some issues might also be tight to kernel version.
But please there is a how to cook thread

gecka said:
Please read carrefully before posting. GPS in in the "not working" list....
Right! Wrong permissions on witch file ???
Click to expand...
Click to collapse
Thats what I'm saying, you've listed GPS as not working but its working for me.
Still trying to figure that part out

robertosandros said:
Thats what I'm saying, you've listed GPS as not working but its working for me.
Still trying to figure that part out
Click to expand...
Click to collapse
You sure the phone is not locating you based just on nearby cell towers?

gecka said:
Well, both in fact. The only debug output I get is from logcat and device logs.
Some issues might also be tight to kernel version.
But please there is a how to cook thread
Click to expand...
Click to collapse
i dount known if this works but maybe, behnaam haw gotten Accelerometer (Screen rotation) Fixed!
http://forum.xda-developers.com/showthread.php?t=563772
haw u triad hes files? maybe works and maybe u using different kernel ver

Market Apps
Hey all.
We've got a problem with the Donut Market over in the Vogue forums. In Donut, when we load up the Market, there are only 20-30 apps available. Going back to Cupcake builds, the problem persists. However, logging in with a fresh Gmail account gets rid of the problem (in Cupcake.)
So far, my guess as to the cause of this is that Google's server have taken note of any "pirates" accessing the as-of-yet unreleased Donut market, and locked them out. However, I don't see any complaints along those lines here.
So, my question to all of you is, while you say the Donut Market is working, do you still seem to have access to all the applications you did in Cupcake?

craig0r said:
Hey all.
We've got a problem with the Donut Market over in the Vogue forums. In Donut, when we load up the Market, there are only 20-30 apps available. Going back to Cupcake builds, the problem persists. However, logging in with a fresh Gmail account gets rid of the problem (in Cupcake.)
So far, my guess as to the cause of this is that Google's server have taken note of any "pirates" accessing the as-of-yet unreleased Donut market, and locked them out. However, I don't see any complaints along those lines here.
So, my question to all of you is, while you say the Donut Market is working, do you still seem to have access to all the applications you did in Cupcake?
Click to expand...
Click to collapse
whats your build.prop?

[DEV]How to fix bluetooth audio in AOSP ROMs

Hey there devs. I just fixed A2DP for VanillaEclair, and I have to share this. Now we can all provide full-featured AOSP-roms, so good luck with tweaking your kernels!
Apparently the solution was simplier than we all thought. We had a missing bluetooth firmware file. Put this to /system/etc/firmware and you'll get A2DP working properly. I got this idea from Darchstar, while I was looking at the firmware file in his rom. Damn... we could've fixed this months ago! So... enjoy and let the fun begin!
PS: unzip this, of course...

Ah, you little bugger You beat me to it.
I actually saw this yesterday while trying to pull proprietary files to compile Cyanogen's Hero port, and noticed that this exact file was missing from my phone. I didn't take too much notice of it until I realized what 'brf' could stand for (Bluetooth Radio Firmware). Was just busy experimenting around this morning
Anyway, well done on the fix - you've made a lot of AOSP lovers happy Might I suggest that you possibly look for further missing files that may solve some other hardware bugs (maybe trackball LED?). I'll see what I find missing today in the ROM.
Mr P.

solved yesterday ....

You've ported Darchstar's ROM, eh? Damn file, this could have been solved for ages. But it's good to have it now anyway.

cheer for you

missing firmware? I had a feeling the problem would be very simple
gonna try this on aHero .. thanks man

RaduG said:
You've ported Darchstar's ROM, eh? Damn file, this could have been solved for ages. But it's good to have it now anyway.
Click to expand...
Click to collapse
but what I think is not enough in some cases, I also worked on the driver liba2dp

The firmware file itself fixes the issue. Nothing else is required.

great! it works! thx

RaduG said:
The firmware file itself fixes the issue. Nothing else is required.
Click to expand...
Click to collapse
I have not had a chance to test it with my edits, though I now also works on bluetooth transfer after work on liba2dp

Now we have it sticky. Thanks Fallen Spartan!

robin04 said:
but what I think is not enough in some cases, I also worked on the driver liba2dp
Click to expand...
Click to collapse
One thing to keep in mind: although the term A2DP is thrown around a lot when talking about bluetooth audio, A2DP has been working fine for a while now. A2DP is the bluetooth profile for high quality uni-directional stereo sound. HFP and HSP are the profiles that allow you to actually talk to someone on a call.
en.wikipedia.org/wiki/Bluetooth_profile
It doesn't make much of a difference when conversing with others on the forums, but if you are actually diving into code it makes a huge difference.
This is ignoring the fact that the problem could have been bluetooth not switching away from A2DP properly or some other such problem, but that didn't seem to be the case because headsets that don't support A2DP still did not work right. This is also assuming that the bluetooth stack in these devices don't depend on A2DP code for all audio over bluetooth as I have not looked at much of the code.
If you already know this, then sorry for the post, but if you didn't, it might save you many hours of banging your head against the wall. On the other hand, if you know for certain that the A2DP code is used when making a call, I'd like to know that as well so I don't get frustrated figuring out how it all ties together.
Derek

Nebvin said:
One thing to keep in mind: although the term A2DP is thrown around a lot when talking about bluetooth audio, A2DP has been working fine for a while now. A2DP is the bluetooth profile for high quality uni-directional stereo sound. HFP and HSP are the profiles that allow you to actually talk to someone on a call.
en.wikipedia.org/wiki/Bluetooth_profile
It doesn't make much of a difference when conversing with others on the forums, but if you are actually diving into code it makes a huge difference.
This is ignoring the fact that the problem could have been bluetooth not switching away from A2DP properly or some other such problem, but that didn't seem to be the case because headsets that don't support A2DP still did not work right. This is also assuming that the bluetooth stack in these devices don't depend on A2DP code for all audio over bluetooth as I have not looked at much of the code.
If you already know this, then sorry for the post, but if you didn't, it might save you many hours of banging your head against the wall. On the other hand, if you know for certain that the A2DP code is used when making a call, I'd like to know that as well so I don't get frustrated figuring out how it all ties together.
Derek
Click to expand...
Click to collapse
I'm not banging my head. mine is the first rom that works on bluetooth audio.
However, as I wrote in the post, in some cases may be associated with
A2DP, in fact, I added the firmware missing
Regards,
robin04

robin04 said:
I'm not banging my head. mine is the first rom that works on bluetooth audio.
However, as I wrote in the post, in some cases may be associated with
A2DP, in fact, I added the firmware missing
Regards,
robin04
Click to expand...
Click to collapse
Like I said, if you already know all of that, then sorry for posting it. There are many on these forums that don't know the difference though, so maybe it will help them. Most headsets don't even support A2DP, my Jawbone Icon only recently got support for it (yay!).
I currently use your rom as I need one with a BFS kernel. The Audible beta app runs with barely any stuttering with it, whereas those with higher end devices are complaining about the poor performance. Thanks!
Derek

What's the point in saying you have fixed it first if you didn't even bother to share? Many things appeared in my ROM for the first time, but I didn't even mention it. We both went out on kicking some guy's ass because he wasn't helping the community, but it seems that you didn't have that in mind either.
Anyway... now everything works in the Vanilla ROMs and that's good.

RaduG said:
What's the point in saying you have fixed it first if you didn't even bother to share? Many things appeared in my ROM for the first time, but I didn't even mention it. We both went out on kicking some guy's ass because he wasn't helping the community, but it seems that you didn't have that in mind either.
Anyway... now everything works in the Vanilla ROMs and that's good.
Click to expand...
Click to collapse
I've simple answered nebvin ....
I do not understand why you have to start a war for anything.
I was going to share (you ask xenoside) but have not had time to make a package to flash.
collect information before judging.
Regards,
robin04

I knew it! I knew it! I knew it! Why did I not follow my instincts on this! I saw all the other ROMs from the G1 area and they had this file. But I should have realized it!

RaduG what's the difference between this and brf6300.bin? Do we need both?

I don't think we need brf6300.bin. Here's the difference:
BRF6300
The BlueLink 5.0 platform from TI is a highly integrated, digital CMOS, single-chip solution supporting Bluetooth® Specification v2.0 and all software needed for Bluetooth operation.
Click to expand...
Click to collapse
BRF6350
The BlueLink 6.0 platform from TI,BRF6350, integrated device includes Bluetooth baseband, RF transceiver, ARM7TDMI®, memory (ROM and RAM), power management and an FM receiver.
Click to expand...
Click to collapse
So these are two different chips, and we have only one inside our heros. What's curious is the fact that the taiwan 2.1 ROM only included BRF6300 firmware and A2DP works with that. One more interesting think is that apparently BRF6350 includes an FM reciever, so in theory we might be able to get the radio functionality.

I see. Thanks!

[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

[MOD]AOSP/TW StereoSound & InCall Fix Note2 (TWRP/CWM flashable.zips)

Hello Note 2 users...(ATT)
Here you'll find a set of modified files for our device that allow stereo sound from both device speakers.... (pretty sweet sound when they both play your music tracks)...
And for you AOSP fans, it includes a fix for that annoying in-call audio issue that forces a toggle down/up to get sound back to acceptable levels.
See below for installation instructions, warnings (got to love those) and other important info about the up's and down's of these sound mods.
First: Credit
Hosting for these files has been graciously provided by @rogersb11 and his AFH account. (thank you brother)...
Please mash the H*** out of his thanks button if you would please, for not only the space to host the files, but for his mad skills in testing and helping me present these for you. He also kindly zipped these up for me. (can't thank you enough man).
And to Cyanogenmod, for the bits needed to create the AOSP VERSION of these files.
Of course, a big thanks goes out to Samsung for everything we love and hate about our NOTE 2.
Second: Disclaimer
The use of these files, resides solely with YOU, THE USER...
I'm not twisting any arms here, so if you decide to go for it and your phone explodes.....well, you know the deal. These files were created for my personal device and use.
I'm offering them to you with that knowledge, and the choice resides with you, or not, to use them for yourselves.
I accept no liability if "YOU" flash these files and something happens that you don't like. (rant off)
These files operate at the hardware level, and "WILL" change the primary operation and sound outputs of your device. So please read carefully, and as you'll see below, MAKE A BACKUP OF YOUR PRIMARY SOUND FILES !! (because you might need an easy way back should you change your mind)...:highfive:
Third: Install
The first file is for Touchwiz based roms...versions 4.4.x
Note: I've tested the TW file on 4.1.2 stock rom as well and it works perfectly .>>>>> UNTESTED>>>>may work on 4.2/4.3 as well....
On Android File Host, locate the StereoSound-TW-Note2.zip
Download it and place to the root of your SD CARD.
Once placed, go into your root explorer app and locate the following file in system/etc/. tinyucm.conf.
When located, use your explorer app and add .bak to the tinyucm.conf file. This preserves it as a backup for later use. (DONT FORGET TO SAVE)...:good:
Once your stock file is backed up...you can then boot into your TWRP or CWM recovery and flash the file you downloaded, then reboot/enjoy.
Note: Audio output enhancements have been made to the flash file, and volume levels will increase approx. 20% beyond the obvious addition of the front earpiece now acting as a speaker......
BE CAREFUL WITH IT !!
The next file is for AOSP based builds versions 4.4.x
Note: no lower android version testing has been done using this file. >>>>>UNTESTED>>>>may work on 4.2/4.3 as well....
On Android File Host, locate the StereoSound&InCallFix-AOSP-Note2.zip
Download it and place to the root of your SD CARD.
Once placed, go into your root explorer app and locate the following file in system/etc/sound. tiny_hw.xml.
When located, use your root explorer app and add .bak to the tiny_hw.xml file. This preserves it as a backup for later use. (DONT FORGET TO SAVE)....:good:
Once your stock file is backed up...you can then boot into your TWRP or CWM recovery and flash the file you downloaded, then reboot/enjoy.
Note: Audio output enhancements have been made to the flash file, and volume levels will increase approx. 20% beyond the obvious addition of the front earpiece now acting
as a speaker......
BE CAREFUL WITH IT !!
Bugs/issues:
Anytime we change the root files for a device, a price is paid. In this case we have gained stereo sound and call fixes for a host of android versions/roms, but it comes with a downside.
During audio playback with headphones plugged in, we get a low level audio output from both speakers.
For some of you, this will be a show stopper especially if you are in the office or in other situations where music playing could end your fun.
But for those who throw their phone into a purse or pocket and blast music through headphones outside or during recreation, this downside is a small price to pay.
I will continue to explore and mod these files in an attempt to eliminate this bug, but so far my efforts break the stereo function and kill the mod altogether.
Should you decide these mods are not for you after flashing them, or if something does not work right, the revert steps are pretty easy.
Just use your root explorer app and delete the new file you flashed from it's appropriate location in your system file. (It will be right next to the file you added the .bak too.)
Then remove the .bak from your original file and reboot-done.
Edit:
Some users are reporting a failure of the in call mod for some AOSP variant builds.
If your are using vipermod for sound boosting, you will need to remove the viper driver before flashing the sound file for AOSP.
I'm working on a patch for this issue, and will update the OP as more information becomes available...g
Enjoy the Mods....g
DOWNLOAD LINK :https://www.androidfilehost.com/?w=files&flid=21747

Update:
The AOSP FILE is confirmed working on lollipop builds as well..
Work continues on the speaker bug...g

One more. ..

Damn.... Just saw this. Uploading a NJ1 Buttnaked now. I'll add this thread as a link.
Thanks man !

dicksteele said:
Damn.... Just saw this. Uploading a NJ1 Buttnaked now. I'll add this thread as a link.
Thanks man !
Click to expand...
Click to collapse
Thanks brother. .
They are fun to have. .and improve the device dramatically.
The mods make our old Note 2's sound like a new device. ..g

Certainly have to try this. Thanks Greg
ROGERS • LG G Flex D950G • Stock ROOT 4.4.2 • V4A • 180DPI • FLEXIN'

Great Mod if it wasn't for the deal breaker (for me) as I use headphones on public transport.
Could you please post the AOSP Fix for in Call Volume by itself.

Blackfyre said:
Great Mod if it wasn't for the deal breaker (for me) as I use headphones on public transport.
Could you please post the AOSP Fix for in Call Volume by itself.
Click to expand...
Click to collapse
Greg did these, I just told him which file for aosp, zipped and tested so as of this moment they must be combined for it to work unfortunately. However this will be gone into further because it 100% solves the incall issue. Just have to figure out how to seperate them. This was intended as only a stereo mod and then noticed the incall

Blackfyre said:
Great Mod if it wasn't for the deal breaker (for me) as I use headphones on public transport.
Could you please post the AOSP Fix for in Call Volume by itself.
Click to expand...
Click to collapse
Package deal ATM...
As mentioned above..
Changing the structure will break the effect... But I'm working it...g

For me, I get sound out of both speakers, but it didnt fix the in call issue I still have to hit down, then up.

storm_rider_1 said:
For me, I get sound out of both speakers, but it didnt fix the in call issue I still have to hit down, then up.
Click to expand...
Click to collapse
Which AOSP rom are you using ?
I'm forming a list of builds that are presenting problems. ..and also the effects of other sound mods like boeffla and viper..
I've had no in call issues at all with pure CM, carbon, cyanide...and the list is growing.
Not to say that you are doing anything wrong of course. .I'm just interested in finding the problems so I can attempt a fix.
Thank you for the report. ..g

gregsarg said:
Which AOSP rom are you using ?
I'm forming a list of builds that are presenting problems. ..and also the effects of other sound mods like boeffla and viper..
I've had no in call issues at all with pure CM, carbon, cyanide...and the list is growing.
Not to say that you are doing anything wrong of course. .I'm just interested in finding the problems so I can attempt a fix.
Thank you for the report. ..g
Click to expand...
Click to collapse
I am on Bliss Stalk, I get the sound out of both speakers and the low amount of sound out of the speakers with the headphones in, but it didn't fix the in call audio. And I am not using any other sounds mods.

storm_rider_1 said:
I am on Bliss Stalk, I get the sound out of both speakers and the low amount of sound out of the speakers with the headphones in, but it didn't fix the in call audio. And I am not using any other sounds mods.
Click to expand...
Click to collapse
I'll have a look at the sound files in the ROM. .
It has viper and EQ settings built in. ..and may be having a conflict. ..
I'll let you know what I find. ..g

What a great Find!! Thanks for sharing.

In call audio didn't change on PAC ROM still have to manually adjust volume

That's 2 in a row..damn..
I'll compare the files for both. ..
And I'd wager they look very much alike. ..
A Taylor made fix is possible there I think.
Thanks gents...g

storm_rider_1 said:
I am on Bliss Stalk, I get the sound out of both speakers and the low amount of sound out of the speakers with the headphones in, but it didn't fix the in call audio. And I am not using any other sounds mods.
Click to expand...
Click to collapse
gregsarg said:
I'll have a look at the sound files in the ROM. .
It has viper and EQ settings built in. ..and may be having a conflict. ..
I'll let you know what I find. ..g
Click to expand...
Click to collapse
I'm on Bliss Stalk too. GregSarg was on the right track. Uninstall the viper driver, reboot, and then follow the installation steps. Finally a fix for the GD incall volume thing. Thank you, thank you, thank you!

Pr4MetheuS said:
I'm on Bliss Stalk too. GregSarg was on the right track. Uninstall the viper driver, reboot, and then follow the installation steps. Finally a fix for the GD incall volume thing. Thank you, thank you, thank you!
Click to expand...
Click to collapse
A great find. ..Thank you Sir...
I'll adjust the OP to include the information. ..g

gregsarg said:
That's 2 in a row..damn..
I'll compare the files for both. ..
And I'd wager they look very much alike. ..
A Taylor made fix is possible there I think.
Thanks gents...g
Click to expand...
Click to collapse
Edit:
Viper mod is causing the in call volume fix to fail.
Prior to flashing my sound mod file. .remove the viper driver and flash the file. ..g

gregsarg said:
A great find. ..Thank you Sir...
I'll adjust the OP to include the information. ..g
Click to expand...
Click to collapse
All the credit belongs to you. Solving the incall volume issue is monumental. Thanks for your contribution towards our still wonderful GN2. A very happy Thanksgiving to you and all the xda community.