Related
Is there any possibility of implementing AVRCP 1.3 or 1.4 on our own instead of waiting for google? I pair my Incredible to my car stereo via Bluetooth and it would be nice to see the track information appear on the head unit display. It looks like it currently supports AVRCP 1.3 in target role, just not source.
http://source.android.com/porting/bluetooth.html
I would love this feature! I'll be willing to test anything.
Even more so, I would love for my phone to pair properly with my Alpine BT. If the phone has had the BT turned on fresh, and I get in the car - it will pair up without interaction and I can initiate a call from the radio. If I stop the car, get out and do something (gas station, errand, whatever) and get back in, turn the car on - the phone looks like it's paired but I will not be able to initiate a call from the radio. I have to do it from the phone or wait for a phone call to come in before it kicks over to the Alpine BT... (no previous phone had this issue, including the Eris, HTC Touch running Android or Windows, and Moto Razr)
I second this request.
Agreed. Hoping for a fix daily, but understand this may be a serious challenge.
For now, I've been switching back and forth between stock ROM and Cyanogen, where Cyanogen bluetooth without sense UI works fine for me. Specifically, I use the Wii remote software to control various emulators.
Sent from my ADR6300 using XDA App
bump......
Bump as well..
I don't have a way to test this, but just a thought --
In CM6, the latest nightly,
edit /etc/bluetooth/audio.conf
At the very top under [General] you see this:
Code:
[General]
Enable=Sink,Control
Disable=Headset,Gateway,Source
Try putting source under Enable.
Worth a try <shrug>
You'll need to reboot after making the change.
Did anyone try tdiman's suggestion? I'm currently reading up on AVRCP and the compatibility with my N1 (this DInc thread popped up on google).
I haven't bought my BT Head unit yet, but I'd be interested to see if we can get metadata via CM
I would love to see this implemented in CM Roms
I tied to edit my audio.conf changing the lines suggested above and it doesn't work. I'm guessing because the version of bluez included with android is only 3.69 and AVRCP 1.3 wasn't even a glimmer in the authors eye at that time.
Our only hope of getting this working is either someone compiles the latest version of bluez into a ROM or wait until google does it. Unfortunately from what I have read even Android 4.0 is going to have bluez 3.69 so it may be a long wait.
Total bummer
Edit: what it does do is make A2DP unstable, after editing this file my A2DP kept randomly disconnecting.
CarpeNoctem said:
I would love to see this implemented in CM Roms
Click to expand...
Click to collapse
My guess is that since bluez is part of the core android OS, CM won't have support for it either anytime soon. Hopefully I am wrong though.
No support in bluez, yet...
Well, currently bluez (the bluetooth stack of Android) does not support AVRCP 1.3. But I have started to work on this (google: Fixes for AVRCP 1.0 and preparation for AVRCP 1.3 bluez)
So, in the following months you will have the proper support in Android, which I'll eventually announce in my blog.
Any update on this? I am looking for this on my Moto Atrix as well. From what I have heard, the Moto Droid X supports it?
http://blog.gmane.org/gmane.linux.bluez.kernel
jiggytom said:
Any update on this? I am looking for this on my Moto Atrix as well. From what I have heard, the Moto Droid X supports it?
Click to expand...
Click to collapse
I have the X and I do not get any track info. My original Droid did display the song information on my head unit.
I have tried every music player on the market and each one says avrcp 1.3/1.4 coming soon...
Google? Bueller? Google? Bueller?
thanks for the amzing post
So anyone can create a pack to port into ROM code for AVRCP 1.3 updated instead waiting Google release?
I'm using my ONE X and it just work with Track ID displayed on CyanogenMod 9 ROM code with Birdplayer as below link
Player download:
http://dl.dropbox.com/u/78817430/Songbird_ mediaplayer_Ver1.3.apk
(share to any buddy still find this player )
Tks/Trung
well some devs got it into their ics roms, but we are looking for avrcp support for jelly bean now
trungvn1790us said:
So anyone can create a pack to port into ROM code for AVRCP 1.3 updated instead waiting Google release?
I'm using my ONE X and it just work with Track ID displayed on CyanogenMod 9 ROM code with Birdplayer as below link
Player download:
http://dl.dropbox.com/u/78817430/Songbird_ mediaplayer_Ver1.3.apk
(share to any buddy still find this player )
Tks/Trung
Click to expand...
Click to collapse
This is what im looking for, something universal that can be flashed over a rom to give it AVRCP 1.3 support. BTW, BlueZ now supports AVRCP 1.3
For use with a HTC GSM Hero
What is Fusion!ROM...
FusionROM is my hobby... it is the ROM I use with my phone everyday so it works very well for me and I hope it will work well for you. I also have a full time job so updates will come at complete random intervals as my life allows them.
Click to expand...
Click to collapse
Big thanks to all the people of the CyanogenMod team for all the great enhancements to android.
Thanks to the community for keeping our Hero's interesting.
Testing in progess report bugs please...
Whats not working...
Waiting for you to test and let me know.
Warnings ...
Trying to setup your google account in the Setup Wizard without a connection can cause problems... skip this step and setup in Settings.
The phone get very slow when the SD card is being checked for error just wait a few seconds for it to finish.
Tips
For stock In-Call UI (generic android style) and buttons ( Settings - Call Settings - In-call touch UI(uncheck) )
To remove the Lockscreen music controls ( Settings - CyanogenMod settings - Input settings - Lockscreen music controls)
Trackball press to skip to next music track when screen is off and music is already playing
Volume Up-Down long press to skip music tracks when screen is off and music is already playing
Apps2SD
Froyo APPS2SD is available...
You may need to manually enter your APNs but some are included.
report bugs and be nice and I'll try to help and fix what I can. If you want to be pro active also post to CyanogenMod forums so the Hero gets good support from there team also.
Fusion!ROM 2.2 includes Google apps
Change Log...
Update 7
Many changes in this release
New default setup and pre-installed dalvik-cache (all cyanogen settings are available you might need to look for them if you don't like the defaults)
GPS is working well in my tests
Rotation is disabled by default - enable it in settings
Added back Gallery3D with rotate hack (still might have some issues but works well enough for me)
Camera touch to focus mode.
All the latest from CyanogenMod
Update 8
New Fusion!ROM boot screen
Includes CPUSpeed for over-clocking and works very well
Synced to CyanogenMod lastest
Working compcache
Feels faster and gets higher linpack score then update 7
All updated google apps
Gallery 3D removed for customized Gallery app.
Some but not all APNs
Should boot for everyone now... please let me know.
Headphone jack icon
Many small changes
Update 9
Synced to CyanogenMod lastest
updated google apps
Gallery 3D returns and is better then ever
APNs updated
New kernel based on flykernel with my own additions and many overclocking options using CPUSpeed app.
Compcache on by default no slowdowns
GPS works very fast
Small cosmetic fixes not found in any other ROM see if you can find them
Update 10
Synced to CyanogenMod latest
Gallery 3D rotation bug is gone
APNs updated again
Maybe VPN is fixed but I can't test it.
Please be warned Fusion!ROM is under development and may contain bugs... this is BETAsoftware and testers are welcome!
Warning! this is a beta and may contains bugs you should backup before testing!
Full wipe recommended... too much has changed back up your data!!!!.
INSTALL FIRST Software over-clockable using included CPUSpeed app.
http://www.multiupload.com/M8LU4HAI2F
Optional Addons:
Older version Update9
http://www.multiupload.com/4OWQMP9EJW
Kernel sources are available on github
wooo lookin like 1st download. can u giv more indication as to what works what doesnt etc?
is camera fixed ?
Can you make list of features - working/not working.
Flashing, so I can benchmark this.
Remember to wait a while before you benchmark there is a lot going on in the background for about 15-20min
rbrucemtl said:
Remember to wait a while before you benchmark there is a lot going on in the background for about 15-20min
Click to expand...
Click to collapse
Why 20min? Also, I still can connect it to PC. Device is offline via ADB.
WOW !! Froyo for the Hero at last - been waiting for this - ill test
Some Screenshots please
How is it slimmed down?
Don't mix up AOSP with CyanogenMod..
And how is this different from the CM 6 alphas?
Linpack is 5012.
BenchmarkPI is 7200ms.
691Mhz.
Also, it counts as a cheat, since the 16 ROMs I've tested didn't have JIT enabled.
Pro-tip: Don't wait 20minutes. Restart the phone 3 times.
In order for Jit to work the java files need to be processed and this takes time. Plus if you have lots of music the album art will be processed too... etc.etc.
ADB works but you need latest driver and might have to reinstall the driver if in windows.
shokkapic said:
Why 20min? Also, I still can connect it to PC. Device is offline via ADB.
Click to expand...
Click to collapse
rbrucemtl said:
In order for Jit to work the java files need to be processed and this takes time.
Click to expand...
Click to collapse
Nope, it's done on the start of an app.
CyanogenMod is the base... try it...
maxisma said:
Don't mix up AOSP with CyanogenMod..
And how is this different from the CM 6 alphas?
Click to expand...
Click to collapse
OOOOKAY
maxisma said:
Nope, it's done on the start of an app.
Click to expand...
Click to collapse
deleted
luvgirl12345 said:
Is this rom up to par with the speed of current 2.1 roms?
Sent from my HTC Hero using XDA App
Click to expand...
Click to collapse
It is faster, because it has JIT enabled, by default.
2.1 ROMs with JIT are similar (but slightly inferior) to this ROM.
deleted
It's FAST!
Autobrightness doesn't work
Testing now
SD not working yet
ok so i know that its a Rom,
but how do i get it.
whats the benefits of it?
i mean whats all the hype about it?
please give me information about it =)
I also need to know where i can get the link fro
Should be on first page of development forum. Read OP for all info about the ROM and link will be there too.
[ROM][WTF][BBQ] CyanogenMod-6 - No Sense at ALL! - V6.0.0 (08/28/2010)
[INFO] Unofficial Cyanogen Mod 6.1 Nightly Thead/FAQ (Updated 9/23)
Basically, it's a fully open-source ROM that strictly adheres to the AOSP (believe it or not, while Android is FOSS, or Free Open Source Software, Sense is not, making it non open-source ROM. It's kinda like a moral high-ground, if you will).
100% of the CyanogenMod source code can be viewed on their Github
If you have a feature request, odds are it can and will be implemented in the next version (or if you're more daring, in the Nightly. See below)
If you have a bug report, you can issue it directly to the CM team on their issue tracker. Most bugs are fixed by the next version (and are progressively tested in the Nightly)
Features many speed, battery life, and UI tweaks not found in Sense ROMs, making it also very flexible, especially for skinning.
Has such features as the ability to force roaming-only mode (good for those who don't live in a city with good Sprint coverage, or work in such a location), no carrier-specific bloatware, and many other heavily requested items (for example, the next release will be featuring camera features that outshine even Sense's camera, such as continuous auto-focus, manual focus area, autofocus, and all of this even while recording video).
Has developers and a large community you can get help from, via forums, Twitter, or IRC.
Is recompiled from source every night, so the latest features, bugfixes, and improvements can be tested and tried by users, allowing for a better full release version.
Listed in ROM Manager, meaning that it's extremely easy for people to pull down release candidates, full versions, nightlies, etc.
Some other tweaks/features:
Has the Bluetooth bitpool setting fixed, so audio on BT headphones/headsets sounds superb.
Has the Stagefright AAC fix so AAC streams (Pandora before v1.4, Slacker, XiiaLive, etc.) don't sound like 32kbps MP3's.
Allows for 0, 90, 180, and 270 degree viewing, and you can turn off certain angles via the settings.
Nightlies are currently running a .34 kernel (faster, better battery life, etc.) and hopefully will have .35 or later in time for the official release of CM6.1 or 6.2.
Has a better Bluetooth stack which allows for the use of Wiimotes as gaming controllers, Bluetooth keyboards and mice, and other devices.
FPS unlocked
Both cameras take pictures and record videos.
kernel speed tweaks
Custom version of ADW launcher
Expanded Spare Parts app
DSP settings
Torch flashlight uses camera flash, includes widget
Additional settings and tweaks for Contacts, Dialer, and MMS (maybe more)
There's really a ton of features and things to find in there (like for example, they just added a feature where you can hold down the Back button to force-close the topmost application in case it locks up). You can see new updates as they're created by following the CMSrc bot on Twitter which posts all of the updates as they happen from Github.
And you know what, if you don't like it, fine, that's your opinion. You can always go back to stock, or whatever you want. No pressure.
EDIT: And let me say one more thing: On Stock, I got about 4 hours of battery life at work (-110dB signal, 20-60% Time without Signal). I get about 6-10 hours on CyanogenMod with the Snap 7.6 kernel, same exact environment, with more usage.
Dang,thanks guys.
Sent from my HTC EVO
FEEL FREE TO DONATE US FOR ALL WE'RE DOING FOR YOU!
For general discussions, bug reports and FAQ, write HERE!
Credits:
Jellaxy Team (in particular erikcas for CM9 / ICS sources and support)
marcin1147 (for support to make it booting)
OldDroid (for help with UMS / USB Mass Storage, test and support)
CyanogenMod team (for supporting ARMv6 devices)
Ganster41 (for OMX ICS hack that allowed anyone to have HW rendering)
Others for general support:
Bytecode
aspee
tioammar
MoltenMotherBoard!
Downloads:
MoltenMotherBoard mirror | AndroidFileHost
Full sources:
MoltenMotherBoard sources: MoltenMotherBoard | Github
Changelog:
Nightlies
Code updates
20141001
Huge sources cleanup
Code updates from AOSP, CyanogenMod
20130722
Code updates
RC9 | 20130616
USB and Wifi thetering fixed (broken till RC7)
Gapps updated to 2013.06.14
ADB icon hided
Hacked again AudioFilter.csv
Tethering improvements
Added new libs to manage partitions
Code updates
RC8 | 20130607
New kernel
New proprietary Bootsplash
Improved AudioFilter.csv
Code updates
RC7 | 20130511
Fixed UMS on new kernel
Added log Banner
New support for init.d scripts
Switched to Stock kernel
Added support for 4.7 GCC version and subsequent
Adjusted doubled props
Code updates
RC6 | 20130501
Settings: excluded System updates
Settings: excluded Bluetooth tethering
Launcher: 3 homescreens
MMS: Avatar showed in notification bar
Improved Camera effects
Included LiveWallpapersPicker
Code updates
RC5 | 20130403
Excluded WiFi Direct (not GIO compatible feature)
Excluded camcorder frame interval (not GIO compatible feature)
Excluded camcorder effects (not GIO compatible feature)
Increased SMS lenght from 8 to 100 (before converting to MMS)
Included 800MHz CPU speed
Re-included some UI sounds
Adjusted Camera layout
Usable without SIM card (after 1st boot - as we provide SetupWizard that needs it, not our fault)
Fixed Bluetooth issues (it broke after RC3)
Some changes for Dalvik and Battery life
Fixed Photo Editor (thank to vutaluk1995)
Fixed WiFi Tethering
Code updates
RC4 | 20130308
Switched to WEXT WiFi drivers
Fixed GPS (it broke after RC2)
Enabled Init.d support by default
Fixed GooglePlay Store - Error 491
Used Tiny_aosp.mk build config
Fixed RIL
Added AD-HOC network supports
Fixed YouTube reboots
Code updates
RC3 | 20130224
Fixed camcorder
Added GPS.conf mod
Added Ringtones loop
New updated specific Samsung libs
Added MMB-Vendor repo
Included Google vendor (Gapps on sources)
Code updates
RC2 | 20130127
Modded Hosts file (now no ads)
MMS: now with 'new-line' button
Added Superuser as default
Added apns-config.xml
Camera fixed in sources
Code updates
RC1 | 20130117
Fixed USB Mode
Cleaned init.rc
Fixed all display related lags
Added full support for QCom hardware devices
Cleaned Framework from other devices specifications
Fixed Browser
Fixed Camera (with erikcas CM9 prebuilts)
Added full support for Legacy Qualcomm OMX IL libs
Great improvements in Framework
Code updates
BETA3 | 20130103
Fixed WiFi
Fixed Display issues
Fixed GPS
Fixed compass
Force enabled Surface dithering
Code updates
BETA2 | 20121225
Added SU binaries (rooted by default)
Improvements in the framework
Improvements in display
Code updates
BETA1 | 20121215
First booting build
Issues:
-----
Do you want to report an issue? Do it here!
In order to do it, create a new issue, choosing correct labels corrisponding to: Device/OS which you're using, ROM/project you're on, kind of issue.
Also, please, be sure you're running the ROM/project in the exact way we've provided it to you (do not create issues if you're using different
kernel, mod, plugins and dependencies we didn't tell to use).
General Questions: MoltenMotherBoard Projects | General Questions and Info
Official Mantainer(s): Mackief, ItachiSama
AOSP:
XDA-Developers said:
The Android Open Source Project (AOSP), led by Google, is tasked with the maintenance and further development of Android. If you find a custom ROM that is based on AOSP, that means it will be closer to the original, vanilla Android created by Google rather than the bloated software created by Samsung, HTC, LG, and Motorola.
Click to expand...
Click to collapse
SearchConsumerization said:
The Android Open Source Project (AOSP) is an initiative created to guide development of the Android mobile platform. The Android platform consists of the operating system (OS), middleware and integral mobile applications.
The AOSP is overseen by the Open Handset Alliance (OHA), a Google-led coalition of over 30 wireless carriers, semiconductor companies, handset manufacturers and software companies. The purpose of the OHA is to further the development of open source standards for mobile devices.
The OHA member list includes Qualcomm, Broadcom, HTC, Intel, Samsung, Motorola, Sprint, Texas Instruments and Japanese wireless carriers KDDI and NTT DoCoMo. Companies that are conspicuously absent from the OHA member list include Nokia, Symbian, Apple, RIM, Microsoft, Verizon and Cingular.
Click to expand...
Click to collapse
AndroidCentral said:
AOSP is a term you'll see used a lot -- here, as well as at other Android-centric sites on the Internet. I'll admit I'm guilty of using it and just expecting everyone to know what I'm talking about, and I shouldn't. To rectify that, at least a little bit, I'll try to explain what the AOSP is now so we're all on the same page.
For some of us -- the nerdly types who build software -- the full name tells us what we need to know. AOSP stands for Android Open Source Project. The AOSP was designed and written by folks who had a vision that the world needed an open-source platform that exists for developers to easily build mobile applications. It wasn't designed to beat any other platform in market share, or to fight for user freedom from tyrannical CEOs -- it exists as a delivery mechanism for mobile apps -- like Google's mobile apps, or any of the 400,000+ in the Google Play store. Luckily, Google realized that using open-source software would ensure that this operating system/mobile application content delivery system is available for all, for free. And by choosing the licensing they did, it's also attractive to device manufacturers who can use it as a base to build their own mobile OS.
The premise plays out rather nicely. Google writes and maintains a tree of all the Android source code -- the AOSP. It's made available for everyone (you, me, manufacturers you've never heard of and not just big players like Samsung or HTC) to download, modify, and take ownership of. This means the folks at CyanogenMod can add cool stuff like audio profiles. It also means folks like HTC can change multitasking in ways that many of us don't like. You can't have one without having the other. The big players then use their modified version of this source to build their own operating system. Some, like Amazon, radically changed everything without a care to use Google's official applications and keep their device in compliance with Android guidelines. Some, like HTC radically changed everything yet followed the Android Compatibility Program (ACP) so they could include Google's core application suite -- including the Google Play store. Some, like the folks at CyanogenMod, enhance the pure AOSP code with additions but don't change the overall look and feel. Again -- that's how this open-source thing works. You can't have it without allowing folks to change it as they see fit, for better or worse.
Any of us can download and build the AOSP. We can even stay compliant with the ACP and contact Google about including their applications. Yes, any of us could build our own device using the AOSP code in our garage or basement with Google's full blessing. That's the beauty of the AOSP, and we wouldn't want it any other way.
Click to expand...
Click to collapse
So this will be AOSP based, and not CM9 based? If so, CAN'T WAIT!
it is AOSP, not AOSP based
Or CM9 or anything :laugh:
EDIT: Hope it will not end like Maclaw´s never released AOSP Project
Amazing,first AOSP for our gio.:laugh:
Not second but first. We had working closed-alpha of our AOSP ROM.
great! but why not JB?
belyava said:
great! but why not JB?
Click to expand...
Click to collapse
We prefer make a previous working version before making another.
That's like building ICS earlier than GB!? What the sense?
If we'll succeed to build AOSP ICS for GIO, then (maybe) we'll do the same with AOSP JB.
Cuz jellybean is very buggy and ics is much stable
Sent from my GT-S5660 using Tapatalk 2
marcin1147 said:
Not second but first. We had working closed-alpha of our AOSP ROM.
Click to expand...
Click to collapse
actually you are right.it is second aosp rom.
I wish you luck with this project
Still prefering AOSP gingerbread above ics. Am I the only one?
Sent from my GT-S5660 using xda app-developers app
Yeah but aosp gb on many phone is buggy We need a great developer to do it (I'm not thinking Px or SZ D)
Frankin96 said:
Yeah but aosp gb on many phone is buggy We need a great developer to do it (I'm not thinking Px or SZ D)
Click to expand...
Click to collapse
And you think ics isnt? Its the same
Sent from my GT-S5660 using xda app-developers app
Yeah I know but (Just my opinion) having an aosp gb is like having a cm without extra features, and cm7 without themes it's ugly, ics is awesome without any extra setting, because google team has done a great work , so , considering that with many build of aosp gb for msm based devices we have the bug of the first cm for gio or other (Wi-fi, gpu , radios ) , having an ics one with same bug of cm9 will be better
Too bad I dont have linux
Sent from my GT-S5660 using xda app-developers app
lol cm7 is built on aosp gb
I have also a closed-bate of aosp gb, bcoz of the cm7 device files i have a working aosp build
You no share?
Lol
Would be nice
Sent from my GT-S5660 using xda app-developers app
Now compile
Mobil cihazdan gönderildi...
aOS 2.3.6 BNC-GIO-R2
m.ali.ozkaya said:
Now compile
Mobil cihazdan gönderildi...
aOS 2.3.6 BNC-GIO-R2
Click to expand...
Click to collapse
Wow, now also we're commanded?!
Is the KitKat Exchange issue fixed in the AOSP 4.4.2. code base? Here is but one example of the problems that appears to persist through 4.4.2 in Nexus devices
http://www.androidpolice.com/2013/1...oid-4-4-users-no-single-cause-yet-determined/
I just downloaded PA 4.2 (beta3) for the HOXL and the Exchange issue is there in full force. Can't set up an Exchange account, can't get the stock Email app to connect, and third party apps such as CloudMagic barf too. To troubleshoot I
a) Installed CM10.2 which runs off the Android 4.3 base. Exchange problems went away
b) Extracted Email.apk from the PA 4.2 (beta 3) download and replaced CM10.2's Email.apk with it. Exchange stopped working in the stock app only but continued working in third-party apps such as CloudMagic
c) Tested Exchange on a tablet running Android 4.4.2 (proprietary version for an unreleased device I am test driving, can't share more details). Exchange does not work there too - neither with the stock apps nor with third-party apps like CloudMagic, so this appears to be more than an app issue with 4.4.2
Samsung and HTC just shipped flagship devices with 4.4.2., I can't believe they and the carriers would let such a bug out the door, so they must have fixed it without waiting for Google to take their thumb out of their a*s. Any advice? I really like PA much better than CM, but Exchange is a must-have for me and PA 3.99 does not exist for my device (AT&T HOXL).