I'm (very) new to Android, so I may have misunderstood some things.
I have rooted and flashed the latest CM, and that is running well. I note that the cooked ROMs tend to offer us things in a 1.6 base that would otherwise require >= 2.x.
I use Timeriffic, at a minimum, to switch my phone to mute/vibrate while I'm at work.
I am also using it as a partial power/battery management tool. ie. I have it set the phone to Airplane mode from 11pm-7am.
Timeriffic does offer the option to toggle Bluetooth automatically, but its disabled for me, which I'm guessing is b/c I've read some things that suggest that the API for this was not released until 2.0, thus progy's don't support it.
Question I have is whether
a) the app is simply detecting the OS version and assuming the feature isn't there
b) OR is the feature is something that can be back-ported into 1.6, altho then app in question may/not still realize its there and offer the user this control.
And/or is there any other 1.6 compatible time-based scheduler that offers the ability to control Bluetooth. Given my druthers, I would only enable it for 4-5 hours/weekday, and then all weekend, the times I am likely to be in my car, where I would use my BT headset.
thanks,
Mike
Related
My Apologies if this is in the incorrect forum but I have experienced problems with bluetooth and my Parrot 3100 incar bluetooth (newest firmware) with some of these ROMs. It is no fault of the ROM writers as it is with a certain windows version they use I am guessing.
Through a bunch of tests with different ROMs, by firstly going back to the Telstra HTC unit, all the Radios are fine with bluetooth and the Telstra ROM, but I have noticed that when you go to a different rom it may fail, Different Bluetooth Engines or drivers maybe I am not sure and no expert.
I noticed ROM's whereby Bluetooth configuration from Comms manager is done by clicking settings down the bottom only work OK. So if you click on the word bluetooth and the bluetooth switch turns on/off chances are it will work, if you must click on the switch to turn bluetooth on/off it may cause issues wth some devices.
So for thoe who know more about the differences, Telstra and KWBR (AKA A_Touch_of_HD) ROM's worked and most of the others (Dutty and EnergyROM were my most recent tests) wouldn't pair what so ever.
So if you are having problems, my siggestion, go back to your orignal ROM and get it working then start again with flashing these much improved ROMs.
If someone can explain maybe what the difference is between the versions is it would be great and allow us less competent people to keep experimenting with your newer creations.
Oh and BTW guys I have tried a lot of these ROMs and thank you for making this phone worth the money. If I was stuck with the telstra ROM chances are, I'd be using a phone for Calls and Text messaging only eek
All you developers are doing a great job
Can someone who already owns a captivate tell me if SPP bluetooth is available as a profile in the stock firmware (2.2 I guess is the current version).
I really just need a terminal for the moment to do external system control via the phone, and I am picking which smart phone to get now, not sure I want to go the full ROM route right away... It is a little overwhelming (there are so many choices I know nothing about).
Forgive the noob question, but I have several older android cell phones, I think it'd be neat to turn them into wifi enabled dedicated music players. I.e. no apps, less services to run. Are there such roms? How complicated would it be to build a rom with no cell radio, but bluetooth and wifi only? Would it be as easy as stripping a rom that exists for the phone to its bare essentials? What are the primary challenges in building a stripped-out rom for a individual legacy phones? Is there such a thing as a universal Android rom? Or, short of a full rom, a full launcher replacement that acts solely in this fashion?
I mean, if I have an old Verizon cell, and I'm on t-mobile or at&t, it seems a fate less worthy for a device that could still perform such a basic function as a music or media player.
I'm just thinking, that's all.
And if no such thing exists but is certainly possible, i'll probably become a new developer.
Lol
My old SII sits around the house as a dedicated music / radio streaming device. There's not really any need for a special ROM, just flash something light like CM or AOSP and remove anything not needed. Put it in airplane mode to disable the radio and leave wifi on, job done.
Hello
Background
I have a OnePlus 3 since Nov 2016. The phone is awesome. But doesnt play well with Android auto when using with custom roms. Atleast on my car, a Mahindra XUV 500.
In the initial few months, there was an issue with stock rom too, but OnePlus solved it and the stock rom works brilliantly with Android Auto.
What is the problem?
On custom roms - every time i connect my phone using the stock OEM cable to my car, android auto is detected and the headunit displays the interface. This lasts for a few seconds to a few minutes and Android Auto disconnects.It re initiates and the interface displays once again, only to disconnect once again. This goes on and on in an endless loop.
On stock rom - no problems. It stays on rock solid.
What have I explored so far
I have tried to triangulate the issue using circumstantial evidence. But there is nothing that consistently triggers this issue. I have tried:
- changing Roms [have tried 8-10 roms, all have this exact issue]
- changing cables [stock, aftermarket, et al. no luck]
- allowing all wakelocks in custom kernels
- disabling USB fast charge
- disabling charging all together
- enabling disabling various usb modes - debugging, mtp, ptp etc.
- upgrading/ downgrading Google play services and other google apps
- various quirky tweaks - with sim, without sim, display always on, etc etc.
There is no trend noticed whatsover
What works?
The only time the connection is stable is when there is activity happening on the screen. Which means, if there is active navigation through maps or music is playing or notifications are flowing. This is the only time when android auto does not disconnect.
My Theories
My conclusion is that there either some form of communication that is happening which keeps the connection going or there is some wakelock that is preventing the connecting from disconnecting.
It could also be something to do with the charging current. Stock rom usually forces the permissible limits but custom kernels push the limit on the amperage. But note that disabling USB fastcharge has no impact. So it could even be the normal USB current as included in the kernel.
Proposition
I am willing to offer a bounty to any developer who could help me by pin pointing the commits that are required to make custom roms/ kernels work. I am very confident this is possible because stock rom already has made it work long back.
Since the demand for android auto on custom roms is quite low, i dont find too many users talking about this. But i use AA extensively - couple of hours each way on my commute and i want to stick with custom roms. Hence this request and offer.
My initial offer is for USD 50 to whoever can help do it first.
Resources
the oneplus commit that they claim made AA work back in the days of N:
https://github.com/OnePlusOSS/andro...mmit/33a109bb360e89182a0db0b00e0650b1b915f4a2
look for the description that says "usb: change product name to OnePlus for Android Auto". After this the stock rom has been rock solid. Also note that this change did not find its way into the Oreo source code. No clue why. This only points to the fact the problem is elsewhere.
Example custom rom source, for reference, which doesnt work:
https://forum.xda-developers.com/on...ice-development/rom-nitrogen-os-beta-t3737654
https://github.com/nitrogen-project/android_kernel_oneplus_msm8996
PS: I hope this finds some takers. Really hoping!!
Will try to post a video later today.
Cheers!
Hi,
I've been using my trusty Nexus One as main phone for about a decade now. Unfortunately, the power button is starting to behave intermittently (which seems to be a known issue).
Before it fails completely, I think one option is to use a replacement image which has a patch to allow the trackball to act as an alternative power button. I'm currently using gingerbread (build GRK39F ?), so I don't need the latest and greatest android by any means. Just want something that's stable and has the basic hardware working (phone, wifi, bluetooth, audio, camera). A recent thread mentioned cm-7.2.0 : is that the one I want ?
The phone is unlocked and rooted. (I think I did that in order to be able to use 'link2sd' to move apps out to the sdcard. But that was a long time ago, so I've forgotten all the details.) Using linux on my pc, so no problem using adb, fastboot.
Thanks, Dave
To answer my own question, cm-7.2.0 works well (so far), and the trackball wake does exactly what I needed.