Android 2.0 Eclair - Bluetooth shame!!! - G1 Q&A, Help & Troubleshooting

Hello folks,
in the new Android 2.0 there's a limit on Bluetooth: you can't enable DISCOVERABLE mode without passing through an Android dialogbox and only for a limited period of time (max 300 seconds): SHAME!!! This means that for DUN connections (or similar) the user should press YES every 300 secs (on Droid probably there's a bug, only 120 secs are allowed).
The problem could be found on the GIT at line 758: the application requires the WRITE_SECURE_SETTINGS permission to run the setScanMode method, unfortunately not available at user level.
Solution> The easiest solution is changing WRITE_SECURE_SETTINGS to BLUETOOTH_ADMIN_PERM, as it should be.
Hope this could be fixed for homebrew roms.
Cheers
PS - I do my apologies for the double post.

That doesn't even make sense. Android 1.5/1.6 only allows discoverable for a short amount of time as well, but once two devices are paired, neither device needs to be discoverable anymore -- they already know about each other.

outZider said:
That doesn't even make sense. Android 1.5/1.6 only allows discoverable for a short amount of time as well, but once two devices are paired, neither device needs to be discoverable anymore -- they already know about each other.
Click to expand...
Click to collapse
That's true, but you don't need to press YES into a ****ty dialogbox. If your application already have a proprietary dialogbox, then with Android 2.0 you have to press a button TWICE!!!
Finally, what if a user want to make a service ALWAYS available, without enabling discovery mode every 2 minutes???
Cheers

outZider said:
That doesn't even make sense. Android 1.5/1.6 only allows discoverable for a short amount of time as well, but once two devices are paired, neither device needs to be discoverable anymore -- they already know about each other.
Click to expand...
Click to collapse
I agree with outZider.
You don't need to keep the device discoverable once you have paired it to your pc (for example) to establish a dialup connection.
You only need to ENABLE bluetooth on both devices.

I dont know, if i understand something wrong, but i used pdanet with bluetooth yesterday. the connection was stable over more than an hour. i have a german milestone.
if its right, what was said here, that wouldnt be possible?

Like others said, I really don't see the issue. I'm pretty sure the limit on 1.6 is 120 seconds, anyway -- more than enough time to pair your devices.
Besides, I know very little about Bluetooth technology, but I'm sure that CONSTANTLY transmitting a Bluetooth signal in a "discoverable" way would kill the battery. I might be wrong, but I'm sure there's a reason behind the limit.

jay652 said:
Like others said, I really don't see the issue. I'm pretty sure the limit on 1.6 is 120 seconds, anyway -- more than enough time to pair your devices.
Besides, I know very little about Bluetooth technology, but I'm sure that CONSTANTLY transmitting a Bluetooth signal in a "discoverable" way would kill the battery. I might be wrong, but I'm sure there's a reason behind the limit.
Click to expand...
Click to collapse
its really a security issue. bluetooth isnt the most secure transmission method out.

bluetooth discoverable mode
Hi,
I am doing an app that requires the android phone to be on discoverable mode for a long time. However, the public APIs I have looked at only allow me to have up to 300 seconds and my app cannot set the bluetooth to be on discoverable mode. I do not want the user to have to click "YES" each time the dialog comes up to make the phone discoverable. I saw that you suggest us to changed the WRITE_SECURE SETTINGS to BLUETOOTH_ADMIN_PERM but this would mean I have to obtain the private APIs and altering its codes, right? Has this problem ever been solved? Is there anyway around this problem?
Thank you.
AndroidTeam5

Related

Reverse-Tethering on a Vogue with Android (Share Windows PC's Internet with phone)

I have done the NAND install method on my Vogue with Myn's Warm Donut RLS3 from 2010-02-20. Since I do not have a data plan, and have the XV6900, which comes without WiFi, I cannot just connect to a local network to get internet access, so how do I get access over the USB cable or via Bluetooth? This would basically be like "Reverse-tethering", that you can do in Windows via ActiveSync (when you are hooked up you can use the desktop PC's internet connection)
So, how do we do this now on Android?
Thanks,
-C
Short version: we don't. Do you want details?
Well, without looking very hard... I know this is possible, since you can do almost anything on Linux. Here's a brief description of how this is done, although it may need some modification for our builds:
http://www.htc-android.com/viewtopic.php?f=5&t=154
OR
http://forums.androidandme.com/topic/internet-over-usb
Search for android ifconfig usb and see what you can find.
polyrhythmic said:
Well, without looking very hard... I know this is possible, since you can do almost anything on Linux. Here's a brief description of how this is done, although it may need some modification for our builds:
http://www.htc-android.com/viewtopic.php?f=5&t=154
OR
http://forums.androidandme.com/topic/internet-over-usb
Search for android ifconfig usb and see what you can find.
Click to expand...
Click to collapse
We certainly could if it was supported in our kernel, but our only USB drivers are adb and mass storage. I believe dzo and mssmison are working on some other. cdc, ethernet, rndis, etc. aren't currently supported.
mrkite38 said:
Short version: we don't. Do you want details?
Click to expand...
Click to collapse
Hmm bummer. Most people with cell service are STILL not paying for data plans, and only about 50% of people with smartphones have data plans yet. Heck...I got a data plan and then got rid of it after 6 months...that alone was $180 worth that was totally wasted for what...the convenience of checking email on my lunch break....yeah that's worth it. At least ATT is only $10 a month now if you are on a shared plan with your family for unlimited data. To bad I an on VZW, lol...
So anyway, it seems like this would almost be a must. I would gladly pay a developer here $50 if he came up with a widget to do it. He'd make a lot more than that on the market too if he developed that.
crobs808 said:
So anyway, it seems like this would almost be a must. I would gladly pay a developer here $50 if he came up with a widget to do it. He'd make a lot more than that on the market too if he developed that.
Click to expand...
Click to collapse
'Real' android phones can do it, our kernel can't. Plus, you can't download from market or use youtube, etc, over bluetooth tethering (I've tried) or via usb from what I've read. Only the cellular data connection and wifi are considered 'valid' by Android. So the dev would have to fix that, too, to make it worthwhile.
mrkite38 said:
'Real' android phones can do it, our kernel can't. Plus, you can't download from market or use youtube, etc, over bluetooth tethering (I've tried) or via usb from what I've read. Only the cellular data connection and wifi are considered 'valid' by Android. So the dev would have to fix that, too, to make it worthwhile.
Click to expand...
Click to collapse
I would be happy just to have WiFi, but the XV6900 (Verizon Touch) doesnt even have WiFi at all. I am considering getting the Nexus when it comes to Verizon in a few months.
crobs808 said:
I would be happy just to have WiFi, but the XV6900 (Verizon Touch) doesnt even have WiFi at all. I am considering getting the Nexus when it comes to Verizon in a few months.
Click to expand...
Click to collapse
Yeah, and the mogul might be a good solve but it only has a 64 MB ROM... I know, been through it all in my head before, too.
Thanks
Thanks. It can sure take some time searching to find some of this info, but even with the NO it won't work I'll still be searching
I want the Bluetooth PAN on Android!
It does not make any sense that Google would know I'm connecting via Bluetooth PAN vs. WiFi to my PC since this occurs behind my Router??? The IP is set at the Router level, my phone should not be visible.
edit... misread post above.
I guess Android itself would know, but that seems odd. But Odd rules sometimes.
Any updates on possibilities yet ??? or there is still no way to use internet on Vogue Andriod without having data plan ?
gogodj said:
Any updates on possibilities yet ??? or there is still no way to use internet on Vogue Andriod without having data plan ?
Click to expand...
Click to collapse
Not yet... the reasons posted above are still true.
Are there any plans to add this feature to future ROMS? The only reason I haven't switched to android from windows mobile is because of this.
damaph said:
Are there any plans to add this feature to future ROMS? The only reason I haven't switched to android from windows mobile is because of this.
Click to expand...
Click to collapse
I don't think so. It's a kernel thing, not a rom thing, and it requires a lot of driver work. But even if it did work, android wouldn't recognize it as a valid connection.
rfcomm + pppd to tether both ways?
I am new to android, but I have networking experience with Linux. I am running Myn's latest Warm Donut on my Sprint Touch. And it seems that hciconfig/hcitool are working to associate the phone with another bluetooth interface. Also, rfcomm seems to be working. And lastly, pppd is installed and (indeed) necessary for the 3g/edge connection as evidenced by the ppp0 in ifconfig. Also, reviewing dmesg, I see L2CAP and BNEP are compiled into the kernel. And pand is also compiled and running. I am not familiar with these, but it seems to offer another route for maybe getting a bluetooth IP link established.
So, my question is simply this. Can we not use the hci commands to associate the phone to another bluetooth adapter on, say, a networked Linux system? Then use rfcomm to build a bluetooth serial connection between the two systems, and finally establish a ppp interface on each end of that serial link? Once that is done, the two systems will share a point-to-point IP link over BT over which they can communicate. Then it is simply a matter of establishing gateways, proxies, iptables NAT, DNS, and routes to make either forwarded or reversed tethered connections. I am reasonably confident I can do that. With a Class 1 bluetooth interface on the Linux server side, the range could be extended for reverse tethering...perhaps making it useful as a moderate range wifi replacement. Other webpages discuss similar approaches using bluetooth rfcomm/pppd. It might require experimentation to find reasonable baud rates for the serial link, etc., but nothing seems obviously impossible. And bluetooth can provide a 1 Mbps+ speeds...again, not great, but better than Edge or dodgy EVDO.
Likewise, we may be able to build a proper PAN connection. I am not familiar with pand and bnep interfaces, but I could probably figure it out.
As I said, I am new to Android, and I am just starting to test this on my phone. Is there something that I am missing with regard to existing hci/rfcomm/pand functionality? Dmesg reports all of these compiled in and hcitool scan seems to do something...it blinks the blue light and find my laptop. I guess I am just asking if someone can shoot holes in my idea before I waste too much time pursuing it.
Thanks.
mprinkey said:
I am new to android, but I have networking experience with Linux. I am running Myn's latest Warm Donut on my Sprint Touch. And it seems that hciconfig/hcitool are working to associate the phone with another bluetooth interface. Also, rfcomm seems to be working. And lastly, pppd is installed and (indeed) necessary for the 3g/edge connection as evidenced by the ppp0 in ifconfig. Also, reviewing dmesg, I see L2CAP and BNEP are compiled into the kernel. And pand is also compiled and running. I am not familiar with these, but it seems to offer another route for maybe getting a bluetooth IP link established.
So, my question is simply this. Can we not use the hci commands to associate the phone to another bluetooth adapter on, say, a networked Linux system? Then use rfcomm to build a bluetooth serial connection between the two systems, and finally establish a ppp interface on each end of that serial link? Once that is done, the two systems will share a point-to-point IP link over BT over which they can communicate. Then it is simply a matter of establishing gateways, proxies, iptables NAT, DNS, and routes to make either forwarded or reversed tethered connections. I am reasonably confident I can do that. With a Class 1 bluetooth interface on the Linux server side, the range could be extended for reverse tethering...perhaps making it useful as a moderate range wifi replacement. Other webpages discuss similar approaches using bluetooth rfcomm/pppd. It might require experimentation to find reasonable baud rates for the serial link, etc., but nothing seems obviously impossible. And bluetooth can provide a 1 Mbps+ speeds...again, not great, but better than Edge or dodgy EVDO.
Likewise, we may be able to build a proper PAN connection. I am not familiar with pand and bnep interfaces, but I could probably figure it out.
As I said, I am new to Android, and I am just starting to test this on my phone. Is there something that I am missing with regard to existing hci/rfcomm/pand functionality? Dmesg reports all of these compiled in and hcitool scan seems to do something...it blinks the blue light and find my laptop. I guess I am just asking if someone can shoot holes in my idea before I waste too much time pursuing it.
Thanks.
Click to expand...
Click to collapse
That's all correct, and I've done it before. But the issue is that Android only acknowledges TWO kinds of data connections: cellular and wifi. When I setup a pan and iptable'd my way to the internet, I was able to get google maps, but not market. I haven't tried Opera but the android browser didn't work. Etc., etc. So I think the usefulness of pan is limited. The real challenge here is for someone to dig through the source and find out how to ADD bt and USB as 'valid' data interfaces. I've never looked into that.
Cellular connection is ppp0. Have you tried running pppd over rfcomm? Or assign an identical IP address to the pan/pppd interface and set it's metric a notch lower so it is preferred over the ppp0 one? Also, will Android route over a VPN? Setup pan and VPN over it. VPN seems to "own" Internet traffic when it is configured according to this: http://code.google.com/p/android/issues/detail?id=4205
Also, I've seen posts indicating that the default browser can be configured to use a proxy.
Just ideas and I'd like to know what you've tried so I don't waste my time. Thanks for your input.
mprinkey said:
Cellular connection is ppp0. Have you tried running pppd over rfcomm? Or assign an identical IP address to the pan/pppd interface and set it's metric a notch lower so it is preferred over the ppp0 one? Also, will Android route over a VPN? Setup pan and VPN over it. Also, I've seen posts indicating that the default browser can be configured to use a proxy.
Just ideas and I'd like to know what you've tried so I don't waste my time. Thanks for your input.
Click to expand...
Click to collapse
Nope, didn't try any fancy-pants stuff. When I did all this, I was a total n00b to linux (only a partial n00b now) and it didn't take too long, so I say - give it a try! That's the spirit around here.
mrkite38 said:
Nope, didn't try any fancy-pants stuff. When I did all this, I was a total n00b to linux (only a partial n00b now) and it didn't take too long, so I say - give it a try! That's the spirit around here.
Click to expand...
Click to collapse
Great. That is encouraging. The link that I edited into my previous post seems to indicate that ALL traffic gets routed over the VPN when it is established. That would fix any security concerns I'd have about using a high-powered BT adapter. I think I will give it a spin.
USB Ethernet
In my kernel hacking trying to get Debian to run, I managed to enable USB Ethernet (the function driver; USB gadget crashes the phone) working, and I've been using it to SSH into my phone. I've used it to apt-get update without any problems. I believe it's just a kernel config option (although I might have done some code modifications), so the problem isn't the driver, it's with Android's userspace.
gTan64 said:
In my kernel hacking trying to get Debian to run, I managed to enable USB Ethernet (the function driver; USB gadget crashes the phone) working, and I've been using it to SSH into my phone. I've used it to apt-get update without any problems. I believe it's just a kernel config option (although I might have done some code modifications), so the problem isn't the driver, it's with Android's userspace.
Click to expand...
Click to collapse
So you enabled USB ether in the kernel config and it's working for you? Against a linux host or Windows? that would be nice, I haven't tried that in ages.
Edit: yes, the 'valid' connection check is definitely in Android userspace. But I either forgot or didn't know that our usb ether func driver worked when enabled.

Bluetooth help!!!

Hi!!
I need help about getting Bluetooth in the Nexus One to be discoverable for more than 300 seconds and also doing this without the user having to click "YES" every time the dialog pops up asking for Bluetooth Permission. I am writing a small app that requires bluetooth to be on for a much longer time than that. Thus, I need to know if there is someway around this problem without having to change the whole android platform. I saw a thread posted by Paragnosta showing us where the problem lies. However, I do not know how to achieve this solution. This is the code that would enable bluetooth discoverable mode for 300 seconds. Any time more than that will be "capped."
Intent discoverableIntent = new Intent(BluetoothAdapter.ACTION_REQUEST_DISCOVERABLE); discoverableIntent.putExtra(BluetoothAdapter.EXTRA_DISCOVERABLE_DURATION, 300);
startActivity(discoverableIntent);
Thank you.
Sincerely,
AndroidTeam5

[Q] G1 rom without phone bulk?

Hi All
Straight to the point:
Is it possible to create a rom that is very light wieght such that it no longer has the capacity to function as a phone (no phone.apk, no sim reading, no 3g). So it is just a wifi tablet. And in doing so will this free up memory/space/speed up the device.
Basically is it possible, or is it strongly coupled within the android source?
Best Regards
DarkFlare
I imagine things like phone and mms.apk would be easy to remove, but things like the network location reporting service would be a good deal more difficult.
Settings/Wireless & networks/Mobile networks:
Uncheck "Data enabled"
Settings/Location & security:
Uncheck "Use wireless networks"
Uncheck "Use GPS satellites"
Now set up your wifi connection and you've got exactly what you're asking for.
Removing apks doesn't help performance in any way whatsoever. You free up space in /system, but that's just about it and, since that partition is read-only, there's no benefit to having more free space on it, you wouldn't be able to use it anyway.
Also note, removing TelephonyProvider.apk also has a chance (it did in cupcake back when I had the same stupid idea) of disabling ALL your wireless connections, including wifi.
Seemed like a good idea.
It's like a step in the wrong direction. In this day and age where you can take your internet anywhere, I see no purpose on gimping a device capable from it's wireless data connectivity.
The device supports all of those features (phone, data) so why keep them unused?
I know that for some of us it feel like carrying features we don't use is like carrying extra weight, but, when you thing about it, the features are still there even if you remove access to them...
This might be what you want instead: http://www.engadget.com/2010/07/26/augens-150-android-tablet-hits-kmart-circular-coming-to-store/
Well, what if someone does not need the telephony functions? Disabling them will not remove or unload them from RAM, so it will take same amount of memory, but if he wants to have them unloaded, he's got to remove them.
I think this would be cool. I wanted to do something simliar with my MT3G when I geta new phone so I could basically turn it into my remote control for things like XBMC. Figured fully removing things such as Phone, 3G, Bluetooth, basically only leaving wifi would save heavily on battery.
Then again I guess I could turn all that stuff off as well.
edru said:
I think this would be cool. I wanted to do something simliar with my MT3G when I geta new phone so I could basically turn it into my remote control for things like XBMC. Figured fully removing things such as Phone, 3G, Bluetooth, basically only leaving wifi would save heavily on battery.
Then again I guess I could turn all that stuff off as well.
Click to expand...
Click to collapse
My thoughts exactly.
biglo said:
My thoughts exactly.
Click to expand...
Click to collapse
edru said:
I think this would be cool. I wanted to do something simliar with my MT3G when I geta new phone so I could basically turn it into my remote control for things like XBMC. Figured fully removing things such as Phone, 3G, Bluetooth, basically only leaving wifi would save heavily on battery.
Then again I guess I could turn all that stuff off as well.
Click to expand...
Click to collapse
This is precisely what I am aiming to achieve. Personally I use EventGhost to controll my win 7 pc, but any remote app would do.
jubeh said:
Settings/Wireless & networks/Mobile networks:
Uncheck "Data enabled"
Settings/Location & security:
Uncheck "Use wireless networks"
Uncheck "Use GPS satellites"
Now set up your wifi connection and you've got exactly what you're asking for.
Removing apks doesn't help performance in any way whatsoever. You free up space in /system, but that's just about it and, since that partition is read-only, there's no benefit to having more free space on it, you wouldn't be able to use it anyway.
Also note, removing TelephonyProvider.apk also has a chance (it did in cupcake back when I had the same stupid idea) of disabling ALL your wireless connections, including wifi.
Click to expand...
Click to collapse
I understand what your saying however Im not looking to just deprive connectivity. I figure if the phone doesnt have a Sim card then theres no reason for it to have the ability to recieve sms so remove all the apps that are setting up broadcast recievers for sms, and/or the code that is emitting the broadcast reciever for sms. This is just an example. But there must be things that can be removed that relate to the sim/phone side.
The tablet you linked too doesnt interest me at all since its a new device and my goal is to repurpose an old (and loved =P) device.
Any rom devs care to kick in there two cents about how achievable any of this is? Removing apk's just seems partially cosmetic as Im thinking its more core than that.
Also thanks to all who have provided responces, its great to have some discussion about this
I will take a Froyo ROM and strip it for you, some time next week.
sleepyfu said:
I will take a Froyo ROM and strip it for you, some time next week.
Click to expand...
Click to collapse
Sounds ace, could you detail some what your planning on doing? Since Im not planning on retiring my g1 just yet but would love to know the steps to create a rom like that further down the line!
you just need to read the cm wiki and you'll find what you need
SO if I understand it right, you want to make it so your phone cannot connect to any GSM service, am I right? And you would like to be able to still use the internet with wifi. Removing APK's or editing framework or the kernel won't change anything. The only way to completely achieve what you want is installing a radio that only supports wifi. No such radio is currently available. You will have to code your own. lbcoder proved that a mismatching radio+SPL=brick, so if I was you I wouldn't be messing with that. Best advice I can give is to switch to airplane mode.
So basically, you want to use your device like an iPad or iPod Touch? Correct me if i'm wrong.
The real thing I still have a problem with is that, as far as I can tell, OP is still thinking that there's some benefit to removing apps rather than just disabling data.
Sure, you can do it, but there's really no point, no benefit, nothing.
Krician said:
So basically, you want to use your device like an iPad or iPod Touch? Correct me if i'm wrong.
Click to expand...
Click to collapse
If that's the case, and I'm on the right track, then I guess you'd also like the build coming together nicely.
I'm not a fan of force-closes, and if you remove stuff, you're bound to find points in the OS where pressing the wrong thing (for example, on Gallery app, choosing the "send via MMS" option) will give you a force-close.
I guess if you want a MID-esque build that actually comes together nicely (ie, disables all menu options and anything else that would cause a force-close due to just plainly removing apks), then I do guess you have a nice project on your hands.
A straight build from AOSP should give you something close, don't know if you'd want Market and Gapps too.
I guess I'll get your mind jogging. Ok, so imagine you do make such a build, then you're still dealing with the fact that your phone still has the hardware and, because of it's nature (a system-on-chip), the radio, etc, are still consuming battery.
You'll never be able to remove everything and you'll always have that itch for "now how do I get rid of this?"...
mejorguille said:
SO if I understand it right, you want to make it so your phone cannot connect to any GSM service, am I right? And you would like to be able to still use the internet with wifi. Removing APK's or editing framework or the kernel won't change anything. The only way to completely achieve what you want is installing a radio that only supports wifi. No such radio is currently available. You will have to code your own. lbcoder proved that a mismatching radio+SPL=brick, so if I was you I wouldn't be messing with that. Best advice I can give is to switch to airplane mode.
Click to expand...
Click to collapse
.. one thing to note is that the mismatched radio/spl brick was due to the KERNEL not booting. Things like FASTBOOT still work, and the only reason they are inaccessible is that the MISC partition is telling the SPL to boot recovery.
Something that recently occurred to me is that it may be possible to replace the radio code with something a little more generic, like redboot http://ecos.sourceware.org/ecos/hardware.html . If you disable the radio processor and don't allocate any memory to it (or very very little), you may even be able to reclaim the memory otherwise being lost to it, i.e. the device actually has 192 MB of RAM, but we only have <100 available to Android.
http://ecos.sourceware.org/fom-serv/ecos/cache/27.html
** doesn't that look just perfect?
Someone correct me if I'm wrong, but I think that the radio processor is exclusively for cell service and that wifi and bluetooth don't depend on it. If this is the case, then you'd be able to use it as a fully functional wifi phone with 192 MB RAM. Even if this is incorrect, read the next paragraph for alternative. Or, of course, a bluetooth or wifi dongle.
A second interesting thought.... USB host mode + UMTS modem = cell phone with cell phone service (or at least VoIP) with 192 MB RAM. Side effect being, of course, that there is a usb dongle duct taped onto the back of the phone, but for adding in close to an extra 100 MB of ram, worth it?
I think that at this point, people should start looking into crazy ideas and weird hacks. Some of this stuff is *DEFINITELY* possible. Even weird things may be possible, like taking over the radio core as a second CPU core (albeit a slower one). Its not like the radio core is a mystery... its an ARM9, so its a simple (eh, in theory) matter of shoving something in that is built for the appropriate instruction set.
lbcoder said:
Someone correct me if I'm wrong, but I think that the radio processor is exclusively for cell service and that wifi and bluetooth don't depend on it. If this is the case, then you'd be able to use it as a fully functional wifi phone with 192 MB RAM.
Click to expand...
Click to collapse
Hey, if you're willing to give it a shot, I have a G1 that I'm willing to torture to death. I'm not a dev but I can certainly test stuff out and get logs and I don't care if I brick that thing.
lbcoder said:
.. one thing to note is that the mismatched radio/spl brick was due to the KERNEL not booting. Things like FASTBOOT still work, and the only reason they are inaccessible is that the MISC partition is telling the SPL to boot recovery.
Something that recently occurred to me is that it may be possible to replace the radio code with something a little more generic, like redboot http://ecos.sourceware.org/ecos/hardware.html . If you disable the radio processor and don't allocate any memory to it (or very very little), you may even be able to reclaim the memory otherwise being lost to it, i.e. the device actually has 192 MB of RAM, but we only have <100 available to Android.
http://ecos.sourceware.org/fom-serv/ecos/cache/27.html
** doesn't that look just perfect?
Someone correct me if I'm wrong, but I think that the radio processor is exclusively for cell service and that wifi and bluetooth don't depend on it. If this is the case, then you'd be able to use it as a fully functional wifi phone with 192 MB RAM. Even if this is incorrect, read the next paragraph for alternative. Or, of course, a bluetooth or wifi dongle.
A second interesting thought.... USB host mode + UMTS modem = cell phone with cell phone service (or at least VoIP) with 192 MB RAM. Side effect being, of course, that there is a usb dongle duct taped onto the back of the phone, but for adding in close to an extra 100 MB of ram, worth it?
I think that at this point, people should start looking into crazy ideas and weird hacks. Some of this stuff is *DEFINITELY* possible. Even weird things may be possible, like taking over the radio core as a second CPU core (albeit a slower one). Its not like the radio core is a mystery... its an ARM9, so its a simple (eh, in theory) matter of shoving something in that is built for the appropriate instruction set.
Click to expand...
Click to collapse
that's so what i (and i think OP here) want. at least the first part. 64 mb of ram reclaimed goes a LONG way to functionality of the device.
the rom should be named G1 Touch ^_^
lbcoder said:
Someone correct me if I'm wrong, but I think that the radio processor is exclusively for cell service and that wifi and bluetooth don't depend on it. If this is the case, then you'd be able to use it as a fully functional wifi phone with 192 MB RAM. Even if this is incorrect, read the next paragraph for alternative. Or, of course, a bluetooth or wifi dongle.
Click to expand...
Click to collapse
On MSM7201A, the modem "owns" the bulk of the clock control registers and the PMIC (and thus voltage rail control), and Linux issues low level rpc calls (proc_comm) to the modem to control clocks and power. Also the modem is responsible for handling power collapse and sleep modes.
If you're going to replace the stock modem firmware, you're going to need to somehow provide this functionality in its place, otherwise Linux is dead in the water.
Brian

[Q] Bluetooth Issues After Stopping Sixaxis Controller

Hey all, so I recently spent some time learning up on these awesome forums, and at least for getting started I decided to just modify stock 2.2, I have just really wanted to be able to play games using my ps3 controller on my nook so I thought the easiest path was to root using the Universal Rev3, and the Unknown Apps, at least to get me started. I have a bluetooth keyboard I also use with this setup for school. Okay so that's the upfront details.
My issue is that, while my bluetooth is connecting fine with everything before I run sixaxis, and my controller works (yay, i got what i wanted!) while I'm running the program, it's when I stop sixaxis and it restores my bluetooth (or says it does... or gets stuck and never says it does) my bluetooth simply can't be switched back on until after I reboot... I've completely stopped and disabled and cleared the cache on the sixaxis app... and nothing, still won't turn back on. Now this is a cadillac issue, my controller works, my keyboard works, but I just have to reset. The problem is that I know it shouldn't be this way and if it has to be, I'll survive, but if not I'd love a way to make it work right, or at the very least see if there's an option to... "respring" (I know that's an iphone thing I just didn't know if there was a faster equivalent to a reboot without having to completely turn it off and back on)?
Anyone else had this problem? Any thoughts? Any options? Thanks for your time and information, have a great day!
"t's when I stop sixaxis and it restores my bluetooth (or says it does... or gets stuck and never says it does) my bluetooth simply can't be switched back on until after I reboot..."
Obviously, its at the fault of the app, because otherwise (sixaxis not installed/used) bluetooth would function properly and no restart would be required.
Therefore, sixaxis is not ending support of the controller properly, re-enabling bluetooth support, or whatever its trying to do for the device, android version, or whatever its problem is in code.
Probably good to let the app's dev know about it and find out if they say anything.
Since root access is required, it definitely requires some deeper access to android (the deeper the more problems are likely to occur). Some code doesn't even work for all devices and they could have gone that route with their app knowingly - whether it was a necessary side effect due to the type of app they created or specifically because of a workaround of what google allows devs to do with android.
Either way it is often an app with problems as reviews show.
sandsofmyst said:
"t's when I stop sixaxis and it restores my bluetooth (or says it does... or gets stuck and never says it does) my bluetooth simply can't be switched back on until after I reboot..."
Obviously, its at the fault of the app, because otherwise (sixaxis not installed/used) bluetooth would function properly and no restart would be required.
Therefore, sixaxis is not ending support of the controller properly, re-enabling bluetooth support, or whatever its trying to do for the device, android version, or whatever its problem is in code.
Probably good to let the app's dev know about it and find out if they say anything.
Since root access is required, it definitely requires some deeper access to android (the deeper the more problems are likely to occur). Some code doesn't even work for all devices and they could have gone that route with their app knowingly - whether it was a necessary side effect due to the type of app they created or specifically because of a workaround of what google allows devs to do with android.
Either way it is often an app with problems as reviews show.
Click to expand...
Click to collapse
Hey thanks a ton for the information. I had started to suspect that but since I'm a noob here I thought it was best to ask. Will contact the developer. But hey for now if all I have to do is a reset after a gaming session to make all things right, it's not so bad. Thanks again!
EDIT: Okay, so after doing some fiddling with my own Nook HD+ it looks like the Nook itself has trouble shutting down bluetooth! When I go into my battery use bluetooth is staying on permanently after initially turning it on. The time continues to run no matter what I do or shutdown with Android Task Manger. And it appears I'm not the only one. http://bookclubs.barnesandnoble.com...Bluetooth-won-t-turn-off-Nook-HD/td-p/1462091
Also since mine is rooted and has unknown sources installed I felt like I needed a control group. So I borrowed my wifes Nook HD+ which is completely stock, no mods at all... and it does the exact same thing... This is mind boggling. Could a few people turn their bluetooth on long enough to register in their battery monitor, then turn it off, and tell me if their time is still running for the bluetooth? It would really help me identify whether this a software problem with Nook software, or it's a hardware issue that they had amongst several models and they shipped with bad parts, etc. Thanks!
gregorcarbine said:
Could a few people turn their bluetooth on long enough to register in their battery monitor, then turn it off, and tell me if their time is still running for the bluetooth? It would really help me identify whether this a software problem with Nook software, or it's a hardware issue that they had amongst several models and they shipped with bad parts, etc. Thanks!
Click to expand...
Click to collapse
It could also be this or similar: https://code.google.com/p/android/issues/detail?id=69135
Quote, "Problem: When turning off the Jawbone, it causes the Bluetooth(BT) to misbehave and not turn off nor function."
...Though that's for android 4.4.2 and nook 2.2 is android 2.2... wow that's old... that could of course be it as well - if the problem is with android, it could have been fixed in a later android version.
In the end, it doesn't appear to have to do with the device itself, but perhaps with that android version's bluetooth package or an installed app. And which android version (if any) would work for you idk. I remember people saying cm and sixaxis didn't work with bluetooth on the nook in the past, so if that's still the case, don't know that either.
I'm not sure how far back many apps are going today with android versions but something like: https://play.google.com/store/apps/details?id=org.myklos.btautoconnect&hl=en
could possibly do something(?). But, I'm just reaching there for anything in the you never know category.
But hopefully that gives a better picture as to what it could be. Sorry, I can't give an actual [working] solution, though for all I know I gave a path to the only solution.

Text and SMS display via bluetooth

Looking for opinions and suggestions for enabling texts and SMS messages to display on the MTCB unit while driving. What, if anything are you guys using?
I searched around already, and found one thread where someone was using tasker and other functions to get messages displayed on the unit from their phone, but that solution didn't appear to be very reliable.
Is there an app that everyone is using? Or am I just late to the party? lol
I realize quite a few of you are using 3G connections with your MTCB, so this conversation is more geared towards those utilizing their Bluetooth only phone connection.
thewesman said:
I realize quite a few of you are using 3G connections with your MTCB, so this conversation is more geared towards those utilizing their Bluetooth only phone connection.
Click to expand...
Click to collapse
Even using a 3G/4G dongle cannot solve the SMS reception problem because these SMS are normally sent to the phone number, not to the 3G/4G SIM number. At most the dongle can be used to send SMS.
ATM no easy solution to this problem (and for social networks use too).
Have you looked at Tablet Talk? I'm not sure it would work over BT since the BT in these devices is locked down, but I believe there is also the option of using Wifi.
The other thread was mine and I was looking for the same thing
As mentioned above, I don't think it's actually possible with these units since it seems the Bluetooth is locked down. Can't remember the specific details but I'm sure it's to do with the Bluetooth service that handles the messages.
I could be wrong though but I know its not possible with tasker anyway and I don't think tablet talk works with Bluetooth cause I looked into that too. At the moment the way I do it is through data which as you say isn't quite as reliable
If you find anything though let me know
dc5daft said:
The other thread was mine and I was looking for the same thing
As mentioned above, I don't think it's actually possible with these units since it seems the Bluetooth is locked down. Can't remember the specific details but I'm sure it's to do with the Bluetooth service that handles the messages.
I could be wrong though but I know its not possible with tasker anyway and I don't think tablet talk works with Bluetooth cause I looked into that too. At the moment the way I do it is through data which as you say isn't quite as reliable
If you find anything though let me know
Click to expand...
Click to collapse
That's why I started this thread, to see if anyone had made any breakthroughs since your initial post. I went ahead and wasted the money on Tablet Talk, and I can confirm that the Bluetooth connection is the issue (Error Code:1) with our units. This seems like such a basic feature that Android would be capable of... my wife's Jeep does it automatically in Uconnect.
One thing I was considering trying with TabletTalk is to go into the factory settings, with the 126 password, and toggle around the Bluetooth type the unit is currently using. I know saving anything in this menu will effectively reset my unit, unless I save settings in Xposed, so I need a block of time to try it that I don't have right now. If it would even make a difference.
thewesman said:
That's why I started this thread, to see if anyone had made any breakthroughs since your initial post. I went ahead and wasted the money on Tablet Talk, and I can confirm that the Bluetooth connection is the issue (Error Code:1) with our units. This seems like such a basic feature that Android would be capable of... my wife's Jeep does it automatically in Uconnect.
One thing I was considering trying with TabletTalk is to go into the factory settings, with the 126 password, and toggle around the Bluetooth type the unit is currently using. I know saving anything in this menu will effectively reset my unit, unless I save settings in Xposed, so I need a block of time to try it that I don't have right now. If it would even make a difference.
Click to expand...
Click to collapse
That's a good idea actually! If I get some free time I'll have a go

Categories

Resources