Hey guys,
I'm having some issues with the NP remote. I can't seem to pair it! Nothing came up automatically as it did in Stock to pair. And home + back button isn't working. How can I enable it without another device? Any ideas? Thanks!
I've tried factory reset, no go. It won't even reset my OS. It'll be exactly the same. Straight to home screen, no prompt to set up.
I've tried using that remote app, but that requires the two devices be connected on the same network, which isn't something I can do. I haves absolutely no control over the player.
The remote works. I can pair it to my S3 and it'll work nicely. I can't get the NP to appear as a Bluetooth device. I think that might be the issue. Help!
I just reflashed and got the same thing. Bluetooth doesn't seem to work.. Flashed stock and got remote access back. Flash custom, lose it completely.
I'm running Lollirock + Chainfire root. When it boots, it goes straight to home screen. The standard Android set up doesn't come up. Also the NP doesn't come up as a BT device. I'm all out of ideas.
I think one of the things with lollyrock is that you have to boot it twice to pair the remote.
I hope that helps
Hi,
Thanks for the reply.
Can you elaborate on that a bit more? When you say "boot", do you simply mean unplug the player and restart? Basically flash the ROM, let it boot up, then unplug it and plug it back in again?
If so, unfortunately, I've tried that. Many, many times. :/
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
Replying to this duplicate post in the hope that someone else won't need to dupe post.
Your answer was in the rom's thread post 13 (2nd page) and points out that a keyboard and mouse are required to setup this rom as you cannot pair the Bluetooth remote until you can reach the Bluetooth screen in settings.
Also, you're not going to enjoy this rom if you plan on using that little remote. Reread the thread, Zulu (the LolliRock dev) States multiple times that he thinks that remote sucks and doesn't support it as it is missing way too many features.
Sorry if I'm a jerk with my blunt post, I don't really intend to be, but you could have answered your own question without double posting and just reading a measly 13 page thread. Honestly, this is what a lot of people on XDA need to hear.
Related
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
Problem: If I leave my Q idle overnight (I only use it mornings) I have to reboot it in order to play music on it.
Details: I'm controlling it with a Nexus 7. The N7 will see the reboot happen "Lost connection with Nexus Q" so I don't think it's a connectivity issue. I did notice that for whatever reason you have to be on the same wireless frequency as the Q to control it. My N4 and N10 are on 5Ghz and they can't talk to it at all. I'm using a Netgear R6300. The N7 reports "Unable to play requested stream." when I try to use the Q.
I called Google about it and no one at the support center even knew what it was. "I know you said it's a Nexus Q, but what *is* it? What does it look like? ... Everyone is huddled around my desk trying to figure out what this thing is! ... Have you tried calling the manufacturer?"
Look two threads below you. http://forum.xda-developers.com/showthread.php?t=2185112
Its being looked at by Google. We can only hope it gets fixed.
https://productforums.google.com/fo...oid-devices/other-google-products/0a0nDlo7Bz8
Sent from my Nexus 7 using xda premium
I'd read that thread and it didn't seem like the same thing to me. As long as I keep my Q playing it keeps working.
riddley said:
I'd read that thread and it didn't seem like the same thing to me. As long as I keep my Q playing it keeps working.
Click to expand...
Click to collapse
You tried factory data reset? I used to have that problem. Now that I think about it after re imaging after trying cm10 I haven't had it happen.
I've tried both the "GUI" version (telling the N7 to factory reset it) and the manual hold the button down version and neither has fixed it.
I was using my nexus player a little while ago with the remote that came with it when it suddenly stopped working and now the LED light constantly flashes. I have taken the batteries out and put them back in, still the same result. anybody have an idea what that means? maybe indication the batteries are dying?
chasew83 said:
I was using my nexus player a little while ago with the remote that came with it when it suddenly stopped working and now the LED light constantly flashes. I have taken the batteries out and put them back in, still the same result. anybody have an idea what that means? maybe indication the batteries are dying?
Click to expand...
Click to collapse
For whatever reason your remote lost sync with the NP. If you go to settings near the bottom, you can re-sync the remote in accessories, I believe (not in front of the player at the moment). If your remote is listed there already you can remove it then redo it. This will require pressing the Home and Back buttons at the same time to put the remote in discoverable mode.
Elrondolio said:
For whatever reason your remote lost sync with the NP. If you go to settings near the bottom, you can re-sync the remote in accessories, I believe (not in front of the player at the moment). If your remote is listed there already you can remove it then redo it. This will require pressing the Home and Back buttons at the same time to put the remote in discoverable mode.
Click to expand...
Click to collapse
Ah yes! Thank you! I did not even think about that!
This has happened to me multiple times. It is annoying. I wonder is anyone else is experiencing this.
It might be possible you hit the Home+Back buttons at the same time, putting the remote in discovery mode.
Sent from my Oneplus One with Tapatalk Pro.
I'm having the same issues listed. I've tried several times repairing. I have been using the Android TV remote app on my phone in place when it happens. Thankfully DroidMote server just updated to support the Nexus Player and works awesome! You have to be rooted but it makes the Nexus Player so much easier to manage with the option for trackpad/gamepad/remote all in one.
EDIT: I've also tried pairing a bluetooth mouse but haven't had success. Maybe it has something to do with the mouse I have. I bought it in Japan and it's an Elecom brand.
Pedro2NR said:
This has happened to me multiple times. It is annoying. I wonder is anyone else is experiencing this.
Click to expand...
Click to collapse
This happens to me quite regularly (every week or two). Luckily I have my phone setup as a backup remote, so I can fairly easily re-pair it, but it really makes the Nexus Player seem very much like a beta-quality release.
Seems that this is more that just a coincidence. Still no fix.
HelixOne said:
This happens to me quite regularly (every week or two). Luckily I have my phone setup as a backup remote, so I can fairly easily re-pair it, but it really makes the Nexus Player seem very much like a beta-quality release.
Click to expand...
Click to collapse
Me too. Every 2-3 weeks I should re-peir Nexus Player remote.
No matter what battery i have left, if i leave the tablet with the screen off for any length of time (half hour say), the tablet seems to die?
To start it again, i have to long press the power button and the device reboots.
Does anyone know why? Its only started since recent updates.
My N10 is not rooted, and running 5.0.1.
Any help would be appreciated.
I guess no one else has this issue?
I literally go back ten minutes after using the N10, and it has shut down. Only a long press to reboot will bring it back?
Frustrated
sparks7 said:
I guess no one else has this issue?
I literally go back ten minutes after using the N10, and it has shut down. Only a long press to reboot will bring it back?
Frustrated
Click to expand...
Click to collapse
I just bought/ordered a Nexus 10 so I might as well come in here and start talking to people about it. lol
I haven't used a Nexus 10 before but it should be like any other Nexus device. If your tablet is turning off on it's own, first off, pray it isn't hardware related. Hopefully some hardware inside isn't failing on you. But to make sure it isn't software related, I would say use the factory images and do a fresh install. This will set anything that is out of wack straight. If its software related, it will fix it.
Cheers for the reply.
Do you mean a factory reset, and I will lose all my saved stuff?
I'm not very clued up tbh, and only ever update the Nexus when notified.
sparks7 said:
Cheers for the reply.
Do you mean a factory reset, and I will lose all my saved stuff?
I'm not very clued up tbh, and only ever update the Nexus when notified.
Click to expand...
Click to collapse
It's not just a simple factory reset that you do in the settings or recovery. It will wipe your device (Internal storage and all) but it wipes everything including all system files and reflashes everything back to the way you got it out of the box. If you had a software issue and sent it in to get fixed, they would most likely do this. Its safe if you read up on it and know what you are doing. Google gives us the factory images for this reason. Here is an article for instructions. Not used to the Nexus 10 forums so I don't know if they have a dedicated thread for this:
http://www.androidbeat.com/2013/11/flash-factory-image-nexus-device/
I'm sure there are some videos on YouTube explaining in depth on how to do it as well. You might want to watch them and get familiar with the process. It's not that hard once you have everything you need to do it. Just back up everything onto your computer, flash the images and put everything back onto your tablet when done.
Thanks very much. I'll have a read up on that and give it a go.
My tablet used to do that. I've had this tablet since I pre-ordered it on initial release (so it's old!) It would also freeze/reboot at times, especially using any browser, so I naturally thought it was a browser problem. But, it would also occasionally do as you describe, wouldn't turn on unless I did a hard reset - holding power button 15-20 seconds or so. I'm also rooted so I started trying different roms. Finally, I flashed the 10.18 release of AOKP. It's beautiful & runs perfect. I've not had ANY, not a single issue & have been running it since last October. I don't think I'll ever change anything from here on. That's just my personal experience.
Sent from my Nexus 10 using Tapatalk 2
Thanks for your help.
I'm going to properly read up on things before I try to resolve it. I don't want to make a mess of it
I have neglected my phone because last time i tried to update my rom(from AEX oreo to a pie) because when i first booted i got that purple/blue blank screen, and the instructions to fix it looked overwhelming(almost the same process as unlocking bootloader) AND the link to some of the files was dead.
Is there a list of instructions thats a bit simpler, with all the required files available? I'm asking cause there too many minor annoying things about the AEX rom on my phone thats inhibiting its use(skips and loses connection with chromecast, cant manage to play music off blackplayer without skipping portions of the last song in queue, or using an equalizer, etc....)
well nobody is willing to address all the instructions and links in one post (neither am I). so I'll try to guide you to most of them.
just flash ZUI 3.5 + using qfil method
link: it's in the second post in this section ( most of the links are working i guess) .
so it'll relock your bootloader now you need to unlock it again using your unlock. img file.
you can find instructions easily. I'll trust you on this one!
then flash latest twrp.
link: https://forum.xda-developers.com/le...mwin-recovery-project-3-t3899166/post78881605
it'll guide you to it!
then you can finally flash the rom!
i think that's all still if anything doesn't turn out correct,
don't blame me?
(you can I won't mind)
the_harsh said:
well nobody is willing to address all the instructions and links in one post (neither am I). so I'll try to guide you to most of them.
just flash ZUI 3.5 + using qfil method
link: it's in the second post in this section ( most of the links are working i guess) .
so it'll relock your bootloader now you need to unlock it again using your unlock. img file.
you can find instructions easily. I'll trust you on this one!
then flash latest twrp.
link: https://forum.xda-developers.com/le...mwin-recovery-project-3-t3899166/post78881605
it'll guide you to it!
then you can finally flash the rom!
i think that's all still if anything doesn't turn out correct,
don't blame me
(you can I won't mind)
Click to expand...
Click to collapse
Thanks, i actually saw your post after i finished the process using This guide. Now i just need to pick a rom thats stable(I'm not gaming, just using it for day-to-day browsing and music. any recommendations?)
scott86 said:
Thanks, i actually saw your post after i finished the process using This guide. Now i just need to pick a rom thats stable(I'm not gaming, just using it for day-to-day browsing and music. any recommendations?)
Click to expand...
Click to collapse
pixys os is what i keep coming back to, everytime i switch to something else. you can try that!
for music try zero audio patch if you may! it'll add up to you experience!
So in case anyone is still checking in on this, i have tried a few roms(AICP, AEX, Lineage) and i seem to be running into the same issue on all of them, regardless of version or what android release its based off. Specifically: When i plug the USB cable into my PC, a lot of times the phone just "forgets" to ask me what to do, and automatically goes to charging. The only way i can get it to realize its plugged into something smarter than a charging adapter is to go into developer options and toggle the USB debug option on and off... THEN i'll get the option in the drop down notification to change to charge, transfer pictures, transfer files, etc... This was one of the annoying things that moved me to finally do a refresh on the phone to get a better rom, but its still happening now using the Lineage nightly rom from april 5th.
Another thing is the equalizer just doesn't seem to work. Both the AudioFX one that seems to be thrown into each rom, or the app specific ones for Poweramp or Blackplayer. This is especially annoying since about 80% of the use my phone gets is as a MP3 player. If i open it up and change around the sliders or switch to a pre-set genre, nothing actually happens, even when using decent quality IEM's where even a subtle change would be pretty obvious.
well well like i said earlier, try PixysOS it's nearly perfect!
scott86 said:
So in case anyone is still checking in on this, i have tried a few roms(AICP, AEX, Lineage) and i seem to be running into the same issue on all of them, regardless of version or what android release its based off. Specifically: When i plug the USB cable into my PC, a lot of times the phone just "forgets" to ask me what to do, and automatically goes to charging. The only way i can get it to realize its plugged into something smarter than a charging adapter is to go into developer options and toggle the USB debug option on and off... THEN i'll get the option in the drop down notification to change to charge, transfer pictures, transfer files, etc... This was one of the annoying things that moved me to finally do a refresh on the phone to get a better rom, but its still happening now using the Lineage nightly rom from april 5th.
Another thing is the equalizer just doesn't seem to work. Both the AudioFX one that seems to be thrown into each rom, or the app specific ones for Poweramp or Blackplayer. This is especially annoying since about 80% of the use my phone gets is as a MP3 player. If i open it up and change around the sliders or switch to a pre-set genre, nothing actually happens, even when using decent quality IEM's where even a subtle change would be pretty obvious.
Click to expand...
Click to collapse
Try to flash Dolby or Viper!