For a number of reasons, I'm thinking of rooting my Droid R2D2 and installing CM7.2. Given that I'm on 2.3.4 and the hoops required to root it, I would love it if someone could verify that the following features all work on their Droid2 or R2D2 with CM7.2. I haven't been able to find a consolidated list of what does or doesn't work on this particular phone. I'll update this post with reported statuses as people respond for others to use as a reference.
Comments in blue are consolidated feedback from others. Comments in green are my own experiences after taking the plunge.
Phone calls: Yes Confirmed
3G Data: Yes Confirmed
WiFi: Intermittent. Sometimes people have to reboot every time you toggle, but not everyone has this issue I've noticed sometimes when on WiFi I lose all data connectivity. Disabling WiFi sometimes fixes it, but not always. Rebooting seems to do the trick every time though.
GPS: Yes Confirmed
Phone-over-Bluetooth: Yes Confirmed
Stream Audio over Bluetooth: Yes, possible lag entering menus/rotating screen/unlocking due to using power amp Pandora works fine for me
Still Camera: Yes Confirmed
Video Camera: Yes Confirmed
Physical Keyboard: Every key except 'ALT LOCK' Confirmed
Motorola Desktop Dock detection/integration: Yes, though it doesn't seem to remember that I've hit the brightness/dim button between inserts as it used to when on stock.
Motorola Car Dock detection/integration: Yes
SMS/MMS (I use Google Voice for most of my SMS needs, but for sake of completeness):Yes SMS - yes. MMS - haven't tested.
In addition, if you could address the following, that would be great: One of the reasons I want to get rid of the installed firmware is because of a strange problem I have when I stream audio over bluetooth to my car. The problem is: when I'm streaming audio, and only when I'm streaming audio, if I use my car's steering-mounted controls to initiate a phone call, it seems to sever the bluetooth connection with the phone. I have to manually re-connect the car to the phone (not re-pair, just re-connect). When I'm not streaming audio, using the steering wheel-mounted controls don't cause the sever to occur. I use both Pandora and iHeartRadio, and have seen the same problem in both apps. Using the iOS version of the same apps on my work-issued iPhone don't have the problem, so I don't think it is an problem inherent with my car, I think it is an issue with the Android installation. If switching to CM7.2 suffers this same problem as the official 2.3.4, it wouldn't be worth the effort to me to switch. But if it DOES fix the problem ... I might be more forgiving if everything in the above list doesn't work fully. I still suffer the same problem.
Thanks in advance!
Other things I've noticed:
Airplane Mode: I've noticed that trying to trigger Airplane Mode doesn't seem to work properly. When I attempt to trigger it, nothing appears to happen. If I then reboot the phone, I see the airplane icon in the status bar, data doesn't work (as one would expect when in Airplane Mode), but the Bluetooth icon is visible, as if Bluetooth were still turned on. Attempting to turn off Airplane Mode also requires a reboot.
Lock Screen: Initially, changing the settings for the lock screen worked just fine. Now, for some reason, the settings don't seem to "stick" ... I set them, but they have no effect. But, if I then reboot, the settings that I tried to set take effect. So they are being persisted somewhere, somehow ...​Airplane Mode and Lock Screen: Originally I noticed the two above items. I just did a factory reset of the phone (Settings --> Privacy --> Factory data reset), and the problems went away. Airplane Mode seems to work properly, and the Lock Screen settings update as expected, just like when I first installed CM. I didn't do all that much previously, so I can't imagine what broke these the first time, but if I happen to recreate the problem and isolate the cause I'll mention it here.
ADW Launcher: When Cyanogenmod first booted up, I couldn't add, move, or remove anything from the default home screens by long-pressing. The haptic would trigger, so I know it was recognizing the presses. By going through the ADW settings and choosing simply to restart ADW, everything started working fine.
Lock Screen: I love the flexibility and customization it allows. At first though, I thought it wasn't showing the time/date of the next upcoming alarm. Then I realized that by disabling the "show next calendar event" feature, it would show up in the same place that the calendar event was otherwise appearing in.
It's fast!: The phone feels MUCH more responsive than when I was on stock.
Phone calls: Yes
3G Data: Yes
WiFi: Intermittent. I have to reboot every time you toggle, but not everyone has this issue.
GPS: Yes
Phone-over-Bluetooth: Yes
Stream Audio over Bluetooth: Never tried
Still Camera: Yes
Video Camera: Yes
Physical Keyboard: Every key except 'ALT LOCK'
Motorola Media Dock detection/integration: Never tried
Motorola Car Dock detection/integration: Never tried
SMS/MMS (I use Google Voice for most of my SMS needs, but for sake of completeness): Yes. I use both also
jlitowitz said:
In addition, if you could address the following, that would be great: One of the reasons I want to get rid of the installed firmware is because of a strange problem I have when I stream audio over bluetooth to my car. The problem is: when I'm streaming audio, and only when I'm streaming audio, if I use my car's steering-mounted controls to initiate a phone call, it seems to sever the bluetooth connection with the phone. I have to manually re-connect the car to the phone (not re-pair, just re-connect). When I'm not streaming audio, using the steering wheel-mounted controls don't cause the sever to occur. I use both Pandora and iHeartRadio, and have seen the same problem in both apps. Using the iOS version of the same apps on my work-issued iPhone don't have the problem, so I don't think it is an problem inherent with my car, I think it is an issue with the Android installation. If switching to CM7.2 suffers this same problem as the official 2.3.4, it wouldn't be worth the effort to me to switch. But if it DOES fix the problem ... I might be more forgiving if everything in the above list doesn't work fully.
Thanks in advance!
Click to expand...
Click to collapse
Does it do this with your standard music app while playing music off your SD card?
Your logic seems sound enough, but you assume Android is a perfect OS. It might just be the way Pandora and iHeartRadio are designed to handle that situation in the Android operating environment and it might just be a bug across 2.3.4. My suggestion to you would be to try these same exact things with a couple DIFFERENT Android phones (a friend's, the wife's, etc.) to see if that's just how it plays out within the Android OS. Worst case scenario, that's just a problem with the apps themselves and you write an email to them asking for an update with a solution.
Sent from my DROID2 using xda premium
Thanks for the info!
pomeroythomas said:
Does it do this with your standard music app while playing music off your SD card?
Click to expand...
Click to collapse
You know, that's a really good thought that I haven't tried yet.
pomeroythomas said:
Your logic seems sound enough, but you assume Android is a perfect OS. It might just be the way Pandora and iHeartRadio are designed to handle that situation in the Android operating environment and it might just be a bug across 2.3.4. My suggestion to you would be to try these same exact things with a couple DIFFERENT Android phones (a friend's, the wife's, etc.) to see if that's just how it plays out within the Android OS. Worst case scenario, that's just a problem with the apps themselves and you write an email to them asking for an update with a solution.
Click to expand...
Click to collapse
Sadly, everyone that I know is an iPhone fanboy. I'm the only one with an Android-based phone!
I'm also aware that the ROM has baked-in support for Motorola's media and car docks, though I don't own one to tell you how well it works. I assume its the same code, just stolen from source, and I've NEVER seen anyone complaining about it on Gingerbread. Maybe head over to the Droid 2 Accessories part of the forum and see if there are any complaints.
Sent from my fully flashed cricKet Droid 2 on CM7.2 using xda premium
Per your advice, I ran a couple of more tests, and found the following. In addition to severing the bluetooth connection when streaming audio from Pandora or iHeartRadio and using the steering wheel-mounted controls to initiate a phone call, the bluetooth connection also gets severed in the same manner when streaming sound from YouTube.
Interestingly, it does NOT sever the connection when streaming audio from the local media player or through Play Music when streaming over 3G. However, even in this circumstance, if I hit the steering wheel "Mode" button to switch to AM/FM, it severs the bluetooth connection. If I recall from past tests, this also would also sever Pandora/iHeartRadio, though I didn't repeat that this morning.
So ... it's not just Pandora or iHeartRadio, but some of Google's own software, though sometimes only when switching radio modes and not always when placing a call.
Is anyone out there running CM7.2 connected to a car and able to verify whether the same problems plague CM7.2 as stock 2.3.4?
2.3.4 and the hoops required to root it,
Click to expand...
Click to collapse
it's not that difficult, just need a decent pc
download iso file (50mb),
mount image to cd, dvd, or usb drive
reboot pc to drive
run program, read onscreen instructions, takes about 10 mins or less
wipe cache, reboot
done your rooted
just know how to boot to bootloader and recovery, read http://droid.koumakan.jp/wiki/Welcome
written for d2G, but same steps
Stream Audio over Bluetooth: Yes, possible lag (music pausing/skipping for a split second ) entering menus/rotating screen/unlocking but maybe because I am using power amp or the kernel that I am using
Dock: There is a dock menu in settings that looks to be specific to this phone (as in I have not seen it on other cm7.2 phones) so it may work
Edit: FYI I had a fun (hard) time getting from stock (froyo) to CM7.2. I had to flash the stock (gingerbread) before I could get to 7.2 (Someone here provided me the file to flash which I may be able to dig up)
Well, I hooped myself crazy, am rooted and on 2.3.4 - and the CM7.2 install script still honks that I'm not on the right version.
Anyone else seen this one?
(I realize I'm a little late to the game - I just got a D2 off of craigslist...)
rprussell said:
Well, I hooped myself crazy, am rooted and on 2.3.4 - and the CM7.2 install script still honks that I'm not on the right version.
Anyone else seen this one?
(I realize I'm a little late to the game - I just got a D2 off of craigslist...)
Click to expand...
Click to collapse
You may need to tweak the Cyanogenmod installer. See the following post for instructions on how to fix. Copying/pasting the instructions here for reference. This worked for me. I ran CM7.2 for quite a while, but eventually got rid of it due to my R2D2 having WiFi issues under CM7.2 (it would sometimes stop having internet connectivity over WiFi, and the only way to fix the issue was to reboot).
http://rootzwiki.com/topic/29930-ne...2-found-droid2-r2d2/page__st__110#entry849398
GregMoens said:
Look like you're failing the check_kernel script. This was put in place to prevent someone with a Froyo based kernel from flashing a CM version that required the Gingerbread kernel. If you open up the cm-7.2.0-droid2.zip file and look at /system/etc/check_kernel, you'll see that the required kernel version is 2.6.32.9-gca08d89, which matches my Droid2 exactly. I'm assuming your version does not match. That 2.3.4 update must have bumped the kernel version. This new kernel may or may not work with CM7.2.
Couple options I can think of. You could change the required version in the check_kernel script. Or you can blank out that entire file and replace it with:
#!/sbin/sh
exit 0
You could also edit the main update script found under /META-INF/com/google/android/updater-script and delete this line:
assert(run_program("/tmp/check_kernel") == 0);
Just make any of those changes, repackage the zip file, and try flashing that. You could very well get stuck in a bootloop due to the new kernel being incompatible and you may have to SBF back to rooted 2.3.4 and live with that for now. Good luck!
based on that post from GregMoens
I've written more detailed instructions here
[How To] Remove Kernel Check on a Rom
---------- Post added at 11:58 AM ---------- Previous post was at 11:54 AM ----------
I have also removed kernel check from a couple of roms, and posted links in my list
sd_shadow's [Collection] of Links: FAQs, Guides, Rooting, SBFs, ROMs... - Google Docs
Related
So I was trying to get the new 2.3.20 firmware and I went to the Archos website. But it looks like there was a new firmware posted this morning. 2.3.26.
I don't know how to direct link, but i'll try.
http://update.archos.com/8/gen8/gen8_2.3.26/firmware_archos_android_gen8.aos
Version 2.3.26 - April 21st, 2011
Wi-Fi: fix cannot scan on an access point above channel 11 regression
Phone tethering: fix TCP/IP header compression setting crash
System stability: avoid Android reboot in case of missing audio
Media library: fix media libray not updated on hard drive based A70
Notification: decrease low battery notification volume
Application: attempt to solve Pandora application not able to switch songs
Application: solve music lag in applications using OGG format
Bluetooth GPS: increase compatibility with 3rd party applications
Display: avoid white/black screen happening sometimes when switching back the display on
Thx jknut, i'm such a noob I forgot to post the changelog. I usually wait till theres a uruk version, but i'm gonna install now cause i'm fairly sure we'll get uruk in a couple of days.
Techngro said:
Thx jknut, i'm such a noob I forgot to post the changelog. I usually wait till theres a uruk version, but i'm gonna install now cause i'm fairly sure we'll get uruk in a couple of days.
Click to expand...
Click to collapse
Not that much of a noob, you posted the link to the firmware that should end my buggy horrors
Thanks jknut for the changelog
Hi, I have one question.
If I have the permanent root from churli (I'm sorry if I miss-spelled it..), do I just updated it regularly? I used to update all the firmwares by just downloading the firmware right on my A70 and install it right away.. but will that work if I have the root? I just rooted my A70 yesterday...and I'm a newbie haha
sw6lee said:
Hi, I have one question.
If I have the permanent root from churli (I'm sorry if I miss-spelled it..), do I just updated it regularly? I used to update all the firmwares by just downloading the firmware right on my A70 and install it right away.. but will that work if I have the root? I just rooted my A70 yesterday...and I'm a newbie haha
Click to expand...
Click to collapse
I just followed Steps 2, 3, 4 of Chulri's post. Chulri already has the new files for "fw 2.3.26 +rw" for Step 3. I like the optional Step 4 because I don't have to worry about holding down the volume button everytime I boot to get root.
Hi,
Has somebody tested this new release?
I updated to version 3.2.20 last week and I was very happy when I realized that cinema plugin was not required to play all the formats which I was not able to before the update (AAC, AC3, MPEG2, etc)
Can somebody confirm if this has not been "fixed"?
Thank you.
Well I have tried this new release and all I can say is bootloop, oh and to top it off I think that my right speaker has blown.
Archos I hope you're reading this, you need to sort your firmware releases out. Whilst you're at it Gingerbread would be nice. If you can put it on the Arnova with inferior hardware you have no excuse but to port it to the 101.
toyface said:
Well I have tried this new release and all I can say is bootloop, oh and to top it off I think that my right speaker has blown.
Archos I hope you're reading this, you need to sort your firmware releases out. Whilst you're at it Gingerbread would be nice. If you can put it on the Arnova with inferior hardware you have no excuse but to port it to the 101.
Click to expand...
Click to collapse
I just noticed the update when I went to the archosfans 2.3.20 bugs thread to report wifi drop powersave disabled while running tunein radio...
OTA update went fine, just waiting for A43 to charge up, then I'm going to do the A32 as well...
[EDIT]
Power LED blinking -> UI batt meter (and About Device) say 98% charge...
had this once with 2.3.20 showing 97% when LED blinking but next charge and thereafter showed 100% when LED blinking...
[/EDIT]
I had this Problem from the first day.
LED blinks and the battery show around 90%.
If i unplug the power the status goes to 98-100%, most 100%.
If i reboot the device with plugged power, the status is 75-90% after restart.
Sometimes the status falls to 87-91% if i plugged the power in.
I can live with it, but it is annoying.
did they remove bluetooth PAN tether ? I had dun/pan option while setting up BT tether with 2.3.20. but now no more that option. the probken for me is, i am using cdma phone(bell htc touch) but with BT DUN the Archos cannot dial CDMA number #777. I set bell APN (pda.bell.ca) it's not working. Actully even if it works I worry about it because it may charge me more.
Before with 2.3.20 , it worked perfect with BT PAN and my phone set to Internet sharing.
This update cleared up my waking-up issue.
It's pretty much an instant on now after the monitor idles off. Before, (after being off for more than a few minutes) it was a crap-shoot as to whether or not the screen would come on and I often had to fight with it and double, triple, quadruple tap the power button to get things alive. No longer.
still reboot cycles problems when charging the 101..problem started with these last 2 updates.
twit.tv app FCs all of the time with this fw...
I wonder why they released this one OTA as it seems to be more broken than .20 was...
youtube and many other flash video played in the browser hangs after about 15 seconds or so. Soemtime this causes the whole system to freeze requiring forced reboot.
This is the worse build so far, my A70 was most stable at 2.1.08.
Wow. I am having the exact opposite experience with this firmware. I find the browser and flash to be very solid. Before I could never play even youtube mobile in HD without it freezing and forcing a hard reboot.
Also, i'm having less general freezes.
I am still having absolutely no luck whatsoever with tethering to my Android phone (cliq). It's driving me crazy cause this was one of the main reasons I went with Archos.
Have you guys done a full reinitialization? That's what I did and, even though it's a pain to reload all your files, it might help with many of the problems you are having.
Techngro said:
Wow. I am having the exact opposite experience with this firmware. I find the browser and flash to be very solid. Before I could never play even youtube mobile in HD without it freezing and forcing a hard reboot.
Also, i'm having less general freezes.
I am still having absolutely no luck whatsoever with tethering to my Android phone (cliq). It's driving me crazy cause this was one of the main reasons I went with Archos.
Have you guys done a full reinitialization? That's what I did and, even though it's a pain to reload all your files, it might help with many of the problems you are having.
Click to expand...
Click to collapse
As a matter of fact I did an Android reset to get away from some of the problems I was having with bootloops and such. This has helped with the general performance of the 101, which I'd say is down to the 64mb swap file I now enjoy.
I did have a couple bootloops until I enabled a lock screen pattern unlock and I have now experienced nothing but fairly good performance
It seems that 2.3.26 is different from vesions before
Need more language for External Keyboard Layout such as Thai
jakkrith said:
Need more language for External Keyboard Layout such as Thai
Click to expand...
Click to collapse
You'd probably be better off posting in the archosfans.com forum's bug list thread for 2.3.26 as Archos employees actually monitor that site and have actually even started some of the buglist/fw release threads... i.e. I'm not sure that they're even aware of the xda-devs gen8 section and even if they were would they bother to read it...
I recently flashed CyanogenMod Nightly #64, because I was hoping to get a crack at a working Google Talk with video chat.
My operation (via RA2.3) followed:
- Nandoid Backup
- Titanium Backup
- Wipe Dalvik, Cache, Data.
- Install cm_supersonic_full-64.zip.
- Install gapps-gb-20110503-signed.zip.
- Reboot
I was unable to test from PC to phone because the phone's Talk account was listed as 'Voice/video chat is not yet available'. I was able to establish a connection from phone to PC, but ran into a few problems...
#1 - The audio connection included a high-pitched screeching noise, like a horribly oversensitive microphone.
#2 - The phone received video from the PC, but the PC did not receive video from the phone.
#3 - Changing the camera-in-use from front to back caused a Force Close.
I know that as a nightly this build is experimental/unstable, so I'm not expecting any kind of "here's how to fix it" answers (although if there are any out there, I wouldn't turn them down). I'm just curious if anyone else is seeing the same problems I am (particularly the mic screeching -- I hope that isn't a hardware problem).
Thanks!
1. Was the phone and the PC next to another, I accidently tried to test it with them next to another and it made that noise. Moved to another room and it went away.
2. I didn't have that issue. Worked fine.
3. That is a known issue with many people (if not everyone).
BrandonEnr7 said:
1. Was the phone and the PC next to another, I accidently tried to test it with them next to another and it made that noise. Moved to another room and it went away.
2. I didn't have that issue. Worked fine.
3. That is a known issue with many people (if not everyone).
Click to expand...
Click to collapse
1. I tried with three PCs, one was in my apartment, one was in another part of the same city, and one was in a different time zone. (I called friends with the last two, who both remarked on the screeching noise).
Could you tell me what you did to set up your Talk? Is there a step I missed?
csharpdflat said:
- Install gapps-gb-20110503-signed.zip.
#1 - The audio connection included a high-pitched screeching noise, like a horribly oversensitive microphone.
#2 - The phone received video from the PC, but the PC did not receive video from the phone.
#3 - Changing the camera-in-use from front to back caused a Force Close.
Click to expand...
Click to collapse
I couldn't get GTalk video calls to work until I used CM7-64 with gapps-20110504. Everything except the back cam is working. I tested it by making a call to my PC. With the phone right next to the PC there was no issue with audio.
I had tried a few other methods mentioned in other threads to get GTalk video to work using CM7 ROMs with different versions of gapps, but the ROM and gapps I mentioned above is the only combination that worked for me.
bbrodus said:
I couldn't get GTalk video calls to work until I used CM7-64 with gapps-20110504. Everything except the back cam is working. I tested it by making a call to my PC. With the phone right next to the PC there was no issue with audio.
I had tried a few other methods mentioned in other threads to get GTalk video to work using CM7 ROMs with different versions of gapps, but the ROM and gapps I mentioned above is the only combination that worked for me.
Click to expand...
Click to collapse
Is gapps-20110504 a savagedzen specific gapps package? If so, I assume I'd need to flash that kernel to use it?
csharpdflat said:
Is gapps-20110504 a savagedzen specific gapps package? If so, I assume I'd need to flash that kernel to use it?
Click to expand...
Click to collapse
Lol a kernel has nothing to do with installing apps.
Sent from my PC36100 using XDA App
I really wish people would just search before flashing away...
Please, look on here, I've explained the problem at least twice, another five times on Twitter, and again on the CyanogenMod forums.
At this rate, I may just create a FAQ/blog about GApps or something.
Not really sure why its working.
I have had no issues with the nightlies and I'm currently on #65.
Here is my post from the [APP] Google Talk w/Video & Voice for 2.3.3 roms CONFIRMED WORKING!!
I hope that this helps.
Just wanted to come back and say that I did finally get everything working with the Google Talk video chat.
Running N66 + Lithid's GApps recommended by drmacinyasha: http://goo-inside.me/google-apps/ ("So what's up with the 2.3.4 GApps?").
Thanks everyone!
I don't have any Mobile network on Rebuild of Evervolv-Perdo-2.1.0p2-passion
But I don't have enough posts to ask on this thread http://forum.xda-developers.com/showthread.php?t=1366897
Anyone have the same problem like me ???Need some help
You have to search for network twice. It will fail first time .. it will also complain 2nd time with "No network found" error but you'll see the network status icon on the notification bar.
you may have ongoing problems with this until 3.0 kernel is out
I have issues with every build and sometimes takes numerous tries and sometimes doesn't work. This is well documented in thread--
mori90 said:
I don't have any Mobile network on Rebuild of Evervolv-Perdo-2.1.0p2-passion
But I don't have enough posts to ask on this thread http://forum.xda-developers.com/showthread.php?t=1366897
Anyone have the same problem like me ???Need some help
Click to expand...
Click to collapse
Install the latest ROM (p3) from this thread, it solved the mobile network issue. Auto connects on reboot. I'm enjoying it
I tried a couple of the ICS roms (they are pretty much identical) but did find many features lacking, app support and hardware support are the biggest issues so far. The 3.0 Kernel will fix a lot of those when drivers have support. I tried the supposed fixed version but my phone network wouldn't connect at all even trying automatic selection. Then again I wasn't exactly impressed with ICS either mostly the UI changes that just don't seem to fit in with phones. ICS looks like a bad port of a tablet OS and I guess that's what it is.
indiangeek said:
Install the latest ROM (p3) from this thread, it solved the mobile network issue. Auto connects on reboot. I'm enjoying it
Click to expand...
Click to collapse
I had all kinds of issues with the p3 build (miniskirt). Overall slow performance, market and gtalk missing, people app not logging in, stuck notifications, broken a2sd etc.
I am sticking with p2 for awhile.
I keep getting a prompt requesting a reboot because the sim card was added. If I press the back key, it just works anyway.
shahrier said:
I had all kinds of issues with the p3 build (miniskirt). Overall slow performance, market and gtalk missing, people app not logging in, stuck notifications, broken a2sd etc.
I am sticking with p2 for awhile.
Click to expand...
Click to collapse
@shahrier: guess the miniskirt version doesn't include gtalk, market etc. Also I was not using miniskirt versions (was on custom blackrose since quite some weeks).
Anyway, let's hope for a p4 or p5 build with working camera
Well, rapmv78 has already given us N1 geeks the perfect New Years gift. ICS on the NexusOne is now effectively feature complete with proof-of-concept camera. As of now, running the p4 build with the camera hack (in TexasIce's thread). Yes, lots of crashes and freezes but its a small price to pay to live on the bleeding edge!
Mobile network autoconnect works, but I'm experiencing soft-reboots periodically, and then a prompt to reboot due to SIM reinsertion or something, which I can surprisingly ignore by hitting the back button. This could be because I didn't wipe my data partition while upgrading from p3. Or the camera hack.
Anyone else experience this? Possible solutions?
EDIT: Fix for mobile network on p2 (atleast for 5.08.004 radio) - While selecting network, hit 'Select Automatically'. It will show an error prompt. Do not touch anything. Within ten seconds, your network should connect automatically. Hit the back button and start making calls and sending texts!
The full p3 (as well as p4) build is much better it seems like compared to miniskirt version. So yeah go with one of those builds if you want auto network connectivity. Oh and camera kind of works now with the work that rampv78 did. Follow these steps to get camera working on p3/p4 build:
http://forum.xda-developers.com/showpost.php?p=20897640&postcount=1074
Also, if u haven't been following, there are some solutions to try for soft reboot problems - disable lock screen, move dalvik to internal, remove ext partition). Strangely one solution works for one person.
Looks like moving dalvik to internal, fixed the reboot issues for me (no reboot since 10 hours)
Re: [ROM][NIGHTLY] CyanogenMod 9 for Motorola Milestone 2 (Android 4.0.4)
This is kinda sad, that I can't reply directly to the ROM thread, but here it is, I just hope someone will tell them, or see it to adress these problems correctly:
There's a couple of problems with this ROM. First of all it loses the data connection after sometime of inactivity. Browser won't load anything, asking to check the connection. Going to settings -> data usage -> mobile data switch -> turning it off and then on solves the problem, but it's kind of annoying to do that five to six times a day.
Secondly - just after flashing this ROM keyboard backlight was working fine. But after installing the gapps it stopped. Just won't work. ((
Third(ly))) - Apollo app crashes at random when trying to listen to podcast/music from sdcard. Also annoying. Disabling data connection seem to solve the issue tho as it stopped crashing yesterday.
Fourth - some sensor shanannigans when you're trying to use chrome (games are fine with it) while charging. Random zoom-ins and stuff.
Fifth - and most terrifying. Sometimes it loops, as if I was repeatedly taping the screen at the center or somewhere near it. Can't even reboot when it happens. Power button to lockscreen seem to solve the issue.
Otherwise this ROM is smooth and good and I like it a lot. Using it for a few months now.
Big thanks.
Sent from my MotoA953 using xda app-developers app
sintu_cf said:
This is kinda sad, that I can't reply directly to the ROM thread, but here it is, I just hope someone will tell them, or see it to adress these problems correctly:
There's a couple of problems with this ROM. First of all it loses the data connection after sometime of inactivity. Browser won't load anything, asking to check the connection. Going to settings -> data usage -> mobile data switch -> turning it off and then on solves the problem, but it's kind of annoying to do that five to six times a day.
Secondly - just after flashing this ROM keyboard backlight was working fine. But after installing the gapps it stopped. Just won't work. ((
Third(ly))) - Apollo app crashes at random when trying to listen to podcast/music from sdcard. Also annoying. Disabling data connection seem to solve the issue tho as it stopped crashing yesterday.
Fourth - some sensor shanannigans when you're trying to use chrome (games are fine with it) while charging. Random zoom-ins and stuff.
Fifth - and most terrifying. Sometimes it loops, as if I was repeatedly taping the screen at the center or somewhere near it. Can't even reboot when it happens. Power button to lockscreen seem to solve the issue.
Otherwise this ROM is smooth and good and I like it a lot. Using it for a few months now.
Big thanks.
Sent from my MotoA953 using xda app-developers app
Click to expand...
Click to collapse
The Data connexion loss is a recuring bug for some, mostly people who have a Carrier that use roaming (ie : use another's carrier's network). No known fix for know, but some people seems to have it working "better" by disabling data roaming/national data roaming in options, but it's not for everyone, since some carriers require that to be toggled for data to work.
For the Backlight on the keyboard, be sure to check if the automatic gestion of automatic backlight is activated, it's required for it to work. There is too a "fix" for the problem in the last 5/6 pages of the main topic from memory, but don't recall it exactly, so you'll have to dig to try it.
No idea about Apollo, but it seems to have quite some quirks, and most people use other players so not sure about it, maybe start by checking the Apollo dev's page and market comments to be sure it's not related to Apollo but to the ROM.
The "random sensor shennanigans" while charging is something that happens to a lot of people, i think it's a multi touch bug from the kernel, but not sure (ie : not really solvable by the dev, unless he finds a way to remake tezet's fix (i think it was tezet) or we all use CH kernel since it seems the bug isn't there in this kernel [ wtb a way to use custom kernels :/]).
Your last problem is a weird bug, probably linked to the ROM, but i must admit it'll be hard to pinpoint, since i don't have it but my brother do, while both phones are the exact same model, and flashed the same, in the same order, with the same sbf/rom versions and so on.
I guess you can try to make a full wipe/factory reset (only backuping data you REALLY need to keep like contacts/sms/call log and so on) and redo your phone config, because as far as i know, the only difference between my phone and my brother's is that i had to did that again after i screwed up a couple times, installing an app that was bricking the phone (took me a few wipes to identify it), it might be the reason why i don't have it and he does, or not.
NEXUS 4,ANDROID 4.4 16S & 16O,Plantronics savor M1100 bluetooth headset or jabra bluetooth headset.Often disconnected during a call.Very high frequency,But 4.3 have not problem.What is the problem?
Find a temporary solution, as long as open WIFI, Bluetooth will be disconnected, closed WIFI, Bluetooth never broken! Currently only so used!
Final, to find a solution, just need to turn off WIFI 5G. Settings - WIFI - Advanced - Wi-Fi frequency band - 2.4GHz only ,ALL OK
Please don't use such a large text size, it's kinda annoying.
I will second you on the Bluetooth issue. I've noticed it with my car, where I usually spend some time on a call or two. It seems intermittent for me, usually starting after about 1 minute and then randomly disconnecting. Either the phone or the car BT will then reconnect, but it'll disconnect again within one to two minutes. Music streaming isn't affected by dropouts, but I have noticed some minor issues with it, such as stuttering.
Android 4.4 Kit Kat, Bluetooth issues
motokochan said:
Please don't use such a large text size, it's kinda annoying.
I will second you on the Bluetooth issue. I've noticed it with my car, where I usually spend some time on a call or two. It seems intermittent for me, usually starting after about 1 minute and then randomly disconnecting. Either the phone or the car BT will then reconnect, but it'll disconnect again within one to two minutes. Music streaming isn't affected by dropouts, but I have noticed some minor issues with it, such as stuttering.
Click to expand...
Click to collapse
I also have the same issue after 4.4 install. Using Nexus 4. I have contacted google, and as expected they can't help!
Sound is very crackly when making calls from my car.. :crying:
Well, let's see if we can't collectively determine what the problem is and at the least submit a good bug report to Google. The first thing I'm going to do is try to reproduce the issue with a standard bluetooth headset. If the problems happens there, I'll then run adb logcat and see if I can grab a log of any error messages.
I encourage anyone else having this problem to do the same and report back on this topic.
Also, to see if it's isolated to specific cars or something, I experience the issue with a 2011 Mazda 3. What is everyone else using?
motokochan said:
Well, let's see if we can't collectively determine what the problem is and at the least submit a good bug report to Google. The first thing I'm going to do is try to reproduce the issue with a standard bluetooth headset. If the problems happens there, I'll then run adb logcat and see if I can grab a log of any error messages.
I encourage anyone else having this problem to do the same and report back on this topic.
Also, to see if it's isolated to specific cars or something, I experience the issue with a 2011 Mazda 3. What is everyone else using?
Click to expand...
Click to collapse
My headset is Plantronics savor M1100 & Jebra BT2010,Same problem.
I am experiencing the same issue with my Alpine CDE-136BT. Running krt16s.
Sent from my Nexus 4 using Tapatalk
Also, to get some extra data, please indicate if you upgraded via official OTA, factory image, or some other method. Also, please say if you did a factory reset or if you did not.
In my case, I saw this using the old 16O factory image (no reset) and also with the 16S OTA from 66Y (4.3), no reset again.
Also worth noting if you have WiFi on and if it's pulling data at the same time...
Sent from my Nexus 4 using Tapatalk
In the car I don't get any problems with quality and/or stuttering, but the BT volume control doesn't seem to work
Also, the 'volume' sent to my car is very low, causing me to control the volume by the car (and putting it very loud)
I didn't try it with a call yet, just music, I'm going to try a call when I get the chance
Here, I'm using the factory image KRT16O, did a clean flash, and the car is a 2013 ford focus
I had the same problem on 4.4 ROMs that don't have the proper Nexus 4 libraries. I switched ROMs, and my problem is gone.
Sent from my Nexus 4 using XDA Premium 4 mobile app
kakabartz said:
but the BT volume control doesn't seem to work
Also, the 'volume' sent to my car is very low, causing me to control the volume by the car (and putting it very loud)
Click to expand...
Click to collapse
Volume seems to still be independent between the headset and the phone. When in a call, use the phone volume keys to raise the volume to near max (I usually put it two presses down from max) and use the car/headset volume to further adjust as needed. Same way with music.
trackmastersteve said:
I had the same problem on 4.4 ROMs that don't have the proper Nexus 4 libraries. I switched ROMs, and my problem is gone.
Click to expand...
Click to collapse
That would be a good option except some people will actually want to be on stock. I would hope Google has the proper libraries for the stock KRT16S factory images and OTA files.
motokochan said:
Volume seems to still be independent between the headset and the phone. When in a call, use the phone volume keys to raise the volume to near max (I usually put it two presses down from max) and use the car/headset volume to further adjust as needed. Same way with music.
Click to expand...
Click to collapse
Yes, thats how it is supposed to work, but I actually can't control the volume at the device at all
Leaving it in the max or the minimum sends the same volume to the car, and its very low
All my other android devices work properly, so its something with my nexus
motokochan said:
Also, to get some extra data, please indicate if you upgraded via official OTA, factory image, or some other method. Also, please say if you did a factory reset or if you did not.
In my case, I saw this using the old 16O factory image (no reset) and also with the 16S OTA from 66Y (4.3), no reset again.
Click to expand...
Click to collapse
16O is full factory image,all clear,two wipe,16S too.not OTA
Definitely a 4.4 bluetooth problem
motokochan said:
Also, to get some extra data, please indicate if you upgraded via official OTA, factory image, or some other method. Also, please say if you did a factory reset or if you did not.
In my case, I saw this using the old 16O factory image (no reset) and also with the 16S OTA from 66Y (4.3), no reset again.
Click to expand...
Click to collapse
I am using TMo OTA image on a Nexus 4. Was rock solid on car connection (Nissan Leaf) until 4.4. My wife's Samsung Galaxy S3 is not on 4.4 and still works great. Problem for me is exactly as described earlier, 1-2 minutes connected then intermittently cutting out so bad it is unusable as a bluetooth connection. Show stopper.
Tested today using a Morotola Elite Flip BT headset and also with my car (while hooked up and logging via adb) while in the garage. I could not reproduce the issue after over 10 minutes of talk. We'll see how it does on an actual drive tomorrow.
climber_paul said:
Problem for me is exactly as described earlier, 1-2 minutes connected then intermittently cutting out so bad it is unusable as a bluetooth connection. Show stopper.
Click to expand...
Click to collapse
Yep, that's what I was seeing. Hopefully someone will be able to get to the bottom of this. If you don't mind taking a laptop into your car, try using it while stationary and grabbing the log output from adb. If the issue occurs, there might be something in the log that can help diagnose the problem.
linkabc said:
NEXUS 4,ANDROID 4.4 16S & 16O,Plantronics savor M1100 bluetooth headset or jabra bluetooth headset.Often disconnected during a call.Very high frequency,But 4.3 have not problem.What is the problem?
Click to expand...
Click to collapse
I think I'm seeing more problems when using Bluetooth at the same time as WiFi is pulling data on it's 2.4Ghz setting (same band as Bluetooth). Can those with Bluetooth issues confirm they persist with WiFi disabled?
same intermittent bluetooth dropout
I wiped my phone before installing 4.4 factory image (16S).
I'm seeing phone bluetooth connection with car drop and reconnect about every 2 to 3 min. while in call. No problem with bluetooth media streaming.
jkang29 said:
I wiped my phone before installing 4.4 factory image (16S).
I'm seeing phone bluetooth connection with car drop and reconnect about every 2 to 3 min. while in call. No problem with bluetooth media streaming.
Click to expand...
Click to collapse
Same problem here. Never had it on 4.3. Currently solved it by using old (from 4.3) bootloader and 0.84 radio.
Took this tip from other thread on XDA.
I also disable wifi when on call (using tasker) - but this along do not solve the disconnect/connect issue. However, this will fix the
call interference in the first 5-10 sec of the call.
Can somehow bootloader and/or radio affect this issue ?
BTW, on 4.4 I finally have stable 5 GHz WiFi connection. So Google definetly fixed something in WiFi code which can now create an issue with the Bluetooth.
Nexus 4 - 4.4
I also experience the stutter when listening to bluetooth headphones, only since the update, 4.3 worked beautifully. It stutters any time I unlock the phone or lock it, very annoying. I'm using Bludio R's, although from what I've read most people are experiencing it regardless of BT type.
Edit: For anyone else experiencing the stuttering; I found a link on the google support where someone else had this issue. Someone mentioned it went away if you turn the screen lock sound off. Haven't had a chance to test as I have no BT headsets in the office, but thought I'd share.
Up for all