I have been experiencing some sound quality issues with Pandora 1.3/1.4 where it sounds like a tin can. All peaks are stripped out. like base and treble are all in the negative range. I have to run it in high quality range to get it to sound ok. Wit that said I get more skips and glitches/ interruptions. ;-(
According to Pandora support it is an issue with Froyo and how it handles AAC+ audio. I thought I'd share my findings and in the hopes one of you awesome devs might have a work around/ patch for the EVO.
Email from Pandora Support:
Hi Gregory,
Thanks for writing.
Froyo has a problem processing our AAC+ files. We have confirmed that this is an issue in the OS, and we think they should have it fixed in a future Android release. Thanks for your patience in the meantime.
As far as the error you're getting, sorry you are having problems with this.
My first suggestion is to power down the phone and pull the battery out. Put the battery back in, turn the phone on, and then try launching our app again.
If that doesn't help, try uninstalling then reinstalling the app.
From the home screen, press the menu key and select "Settings" then "Applications". Next select "Manage Applications". Scroll down and select Pandora. Then uninstall.
To reinstall, go to the Android Market and search for Pandora. You should also see it in the most popular apps list.
Let me know if this helps.
Best,
Jed
Pandora Listener Support
*More questions about Pandora? Please visit our FAQ:
http://blog.pandora.com/faq
Neotype33 said:
I have been experiencing some sound quality issues with Pandora 1.3/1.4 where it sounds like a tin can. All peaks are stripped out. like base and treble are all in the negative range. I have to run it in high quality range to get it to sound ok. Wit that said I get more skips and glitches/ interruptions. ;-(
According to Pandora support it is an issue with Froyo and how it handles AAC+ audio. I thought I'd share my findings and in the hopes one of you awesome devs might have a work around/ patch for the EVO.
Email from Pandora Support:
Hi Gregory,
Thanks for writing.
Froyo has a problem processing our AAC+ files. We have confirmed that this is an issue in the OS, and we think they should have it fixed in a future Android release. Thanks for your patience in the meantime.
As far as the error you're getting, sorry you are having problems with this.
My first suggestion is to power down the phone and pull the battery out. Put the battery back in, turn the phone on, and then try launching our app again.
If that doesn't help, try uninstalling then reinstalling the app.
From the home screen, press the menu key and select "Settings" then "Applications". Next select "Manage Applications". Scroll down and select Pandora. Then uninstall.
To reinstall, go to the Android Market and search for Pandora. You should also see it in the most popular apps list.
Let me know if this helps.
Best,
Jed
Pandora Listener Support
*More questions about Pandora? Please visit our FAQ:
http://blog.pandora.com/faq
Click to expand...
Click to collapse
I'm using Pandora on FroYo just fine myself. Actually I remember some tin sounds on 2.1 but since 2.2 I've had a better experience.
It may be a problem in the Kernel which would make sense because I am using the netarchy custom kernel verses the stock one.
Either that or its in the ROM, but I use my own ROM so maybe that's it...
Are you using stock or are you rooted and running custom? If rooted do a nandroid and try Netarchy's kernel (I prefer version 3.7.8b for now)
I have tried the Stock Pre-release Rom and the current Stock Rom. I rooted both. There has been no reason other than this issue to move to a custom Rom on the Froyo since speed and performance for me has not been an issue. I do like the sense interface. (My Hero was a different story, slow and over whelmed.I customized the crap out of it since it needed all the cpu cycles I could get.)
Thanks for the suggestion. I might have to check out some other Roms to see if it is in deed a kernel issue.
There's an update for pandora in the market. Maybe they fixed the issue?
This issue has been addressed several times in this forum. The workaround is performed with adb commands at a Windows Command Prompt.
Temporary fix (no root required):
adb shell setprop media.stagefright.enable-player false
Click to expand...
Click to collapse
The temporary fix revert back everytime you reboot your phone.
For a more permanent fix (requires root and nand unlock):
-adb pull /system/build.prop
-edit build.prop (opens in DOS text editor)
-change (media.stagefright.enable-player=true) to (media.stagefright.enable-player=false) and save and exit editor.
-adb remount
-adb push c:\directory where you pulled the file to\build.prop /system/
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App
The issue is with the Stagefright media decoder. All Froyo ROMs and kernels experience this problem.
Sent from my PC36100 using XDA App
There was an update for Pandora this morning. Maybe that corrected the issue?
bpqow said:
There's an update for pandora in the market. Maybe they fixed the issue?
Click to expand...
Click to collapse
Yeap, that is 1.4. This effects all version of the stock build of 2.2.
sombdy said:
This issue has been addressed several times in this forum. The workaround is performed with adb commands at a Windows Command Prompt.
Temporary fix (no root required):
The temporary fix revert back everytime you reboot your phone.
For a more permanent fix (requires root and nand unlock):
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Thanks I'll have to check that out.
Permanent fix: Use the latest CM6 Nightly. Cyanogen pushed the official fix for the Stagefright decoder from Google, and all AAC+ streams sound perfect now.
sombdy said:
Temporary fix (no root required):
Code:
adb shell setprop media.stagefright.enable-player false
Click to expand...
Click to collapse
That does not work on non-rooted phones. THe command executes with no error, but doesn't actually do or change anything (confirm this with a getprop command immediately afterwards).
In short, if you are on the 2.2 OTA you are SOL until HTC releases a fix (Google has already committed their code for it) or someone finds a way to root 2.2 OTA.
sohr said:
That does not work on non-rooted phones. THe command executes with no error, but doesn't actually do or change anything (confirm this with a getprop command immediately afterwards).
In short, if you are on the 2.2 OTA you are SOL until HTC releases a fix (Google has already committed their code for it) or someone finds a way to root 2.2 OTA.
Click to expand...
Click to collapse
That command line does work on a non-rooted phone. The setprop command does not require root access. And as I said in the post, it is not a permanent fix. I know it does not change the build.prop file, but it does change your settings for the current session. If you reboot the phone, the settings return to enable-player = true, hence a temporary fix. Just issue the command again to turn off Stagefright.
So, dude, you are not completely SOL.
Sent from my PC36100 using XDA App
sombdy said:
That command line does work on a non-rooted phone. The setprop command does not require root access. And as I said in the post, it is not a permanent fix. I know it does not change the build.prop file, but it does change your settings for the current session. If you reboot the phone, the settings return to enable-player = true, hence a temporary fix. Just issue the command again to turn off Stagefright.
So, dude, you are not completely SOL.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I know setprop does not require root access-- however, without it it appears to do nothing for the stagefright setting.
Running "adb shell getprop" and looking for the appropriate stagefright setting shows it is still set to true immediately after running the setprop command that is supposed to set it to false.
EDIT-- And a quick soundtest of Pandor/Slacker/Yahoo Radio after running the command shows no discernable difference in sound quality-- still sounds like listening to a low-bitrate stream.
sohr said:
I know setprop does not require root access-- however, without it it appears to do nothing for the stagefright setting.
Running "adb shell getprop" and looking for the appropriate stagefright setting shows it is still set to true immediately after running the setprop command that is supposed to set it to false.
EDIT-- And a quick soundtest of Pandor/Slacker/Yahoo Radio after running the command shows no discernable difference in sound quality-- still sounds like listening to a low-bitrate stream.
Click to expand...
Click to collapse
After issuing the command, be sure to skip foreward in the player so that it buffers a new song. Any previous song that was downloaded before will sound garbled. I experienced this same thing. Trust me. Just let it run for a bit and it will clear up the sound. Skip a few songs and you will hear the difference. Getprop only tells what is in build.prop, but we are not changing build.prop because that requires root. Get it? So of course you will not see a change in getprop. But this does work. You just have to have a song buffered after issuing the command.
Sent from my PC36100 using XDA App
Related
http://www.siriusxm.com/android/indexd.html
View attachment 403113
Awesome, love my XM.
Sent from my PC36100 using XDA App
Just tried it a bit. I'm on Fresh 3.2. It used to not even connect, just say "Aquiring Data Connection"
With this update it plays and doesn't loop, but it sure does jump and skip quite a bit. Guess it's a start....
Only Froyo ROM I've ever gotten SXM to work right on is CM6 - which I don't wanna go back to.
Nice thanks for the update. I guess signing up on their webpage for an update email was pointless.
dwertz said:
Nice thanks for the update. I guess signing up on their webpage for an update email was pointless.
Click to expand...
Click to collapse
Well thats how I found out they emailed me. Also make sure you dont have the stagefright fix since I am also running Fresh 3.2 and had to switch back to stock stagefright files in order for it to play properly.
1 hr running and no problems so far... Thanks XM
playya said:
Well thats how I found out they emailed me. Also make sure you dont have the stagefright fix since I am also running Fresh 3.2 and had to switch back to stock stagefright files in order for it to play properly.
1 hr running and no problems so far... Thanks XM
Click to expand...
Click to collapse
Please tell me what you did to stagefright. I know Flipz made some changes to it but I don't know how to undo them. In my build.prop the player is enabled and it still skips a lot.
Thanks!!
I am using Fresh 3.2 and the new SiriusXM app is working fine for me. I'd say about 3 skips every hour or so. I actually only use this for Bloomberg and CNBC - I much prefer slacker and pandora for music, so a couple of skips is no big deal for me.
What I desperately can't figure out is how to record a live stream off the sound card (for lack of a better term). All recording apps seem to use the microphone only. Any ideas so that I can listen to specific CNBC shows like Kudlow on my ride home?
fchipm said:
Please tell me what you did to stagefright. I know Flipz made some changes to it but I don't know how to undo them. In my build.prop the player is enabled and it still skips a lot.
Thanks!!
Click to expand...
Click to collapse
Just extract the stagefright files from your original rar file and then ad push or copy and paste with Root explorer into the system/lib folder overwriting the files that are there now
Then replace the build.prop with the one from your original rom rar file as well.
I WIll try and attached them here for you.... what rom are you running
tnnm said:
I am using Fresh 3.2 and the new SiriusXM app is working fine for me. I'd say about 3 skips every hour or so. I actually only use this for Bloomberg and CNBC - I much prefer slacker and pandora for music, so a couple of skips is no big deal for me.
What I desperately can't figure out is how to record a live stream off the sound card (for lack of a better term). All recording apps seem to use the microphone only. Any ideas so that I can listen to specific CNBC shows like Kudlow on my ride home?
Click to expand...
Click to collapse
I am on the same rom and 0 skips at all....
playya said:
I am on the same rom and 0 skips at all....
Click to expand...
Click to collapse
Actually, after a reboot, I'm finding no skips at all as well.
Hate to bump this thread up again, but seemed like the best place to post rather than making a new thread.
Is anybody having issues with SXM 1.1 and connecting in the past couple of days? Its worked flawlessly for me since the update, and I've been happy with it again. However, now, on startup, the application hangs on "Checking for Updates".
Tried clearing data, uninstall/reinstall, and hard reset fresh install. All no dice.
Anybody else having issues?
Code:
I am not a member of the CM team, I am just a CM user trying to help the community.
Official CM7 Wiki can be found here.
Fixes:
Missing Market/Google Apps (or market force closing):
You either forgot to download and flash Gapps, or got the wrong one, or RomManager/Clockwork didn't flash it right. If you used are on nightly 11 or newer or RC2 or newer you will need the latest gapps. They were updated 03/07 (20110307).
Download the CM7/Gingerbread Gapps Universal here and flash in recovery
While in recovery remember to wipe cache/dalvic and Fix Permissions (after flashing while still in AmonRA recovery go to "Other > Fix apk uid mismatches").
GPS:
Firstly, Cyanogen himself knows this is a problem
cyanogen said:
The GPS in the Evo is the buggiest thing I have ever seen. Before 2.3, we were using binary blobs for the GPS driver which contains who-the-hell-knows-what from HTC to fix these things. Now we are using opensource code that is based on Qualcomm reference designs which is pretty close to correct but sometimes the hardware just fails certain calls for no apparent reason (and sometimes they work just fine).
This is a blocker bug for 7.0 final, so it'll get resolved.
Click to expand...
Click to collapse
There is a "temporary fix" that seems to work for most people. It does not work 100% of the time nor does it work on 100% of phones. (Sorry I couldn't find the original poster of this for credit, if someone knows who discovered this I will give credit where it is due).
Make a Nandroid of your current CM7 setup.
Boot into recovery and perform a full wipe (or use Calkulin Format ALL zip)
Flash any Sense ROM
Open the Market and download MSL Reader, write down MSL.
Open Dialer/Phone and type ##4772579# (##GPSCLRX#)
When it asks you for a password type in your MSL
Reboot phone
BE OUTSIDE
Turn on GPS and open Maps, allow it to fully lock your location (may take a few minutes, do not just wait for initial lock).
Leave GPS on
Turn off phone, reboot into recovery.
Nandroid restore your CM7 backup
Click to expand...
Click to collapse
Wifi Sleeping
This is yet another tricky issue. For some the "fix" works but others say it does nothing and makes the problem worse. Some say that the problem is the router or security type (WEP theoretically is to blame).
Go to: Menu>Settings>Wireless & networks>Wi-Fi settings>Menu>Advanced>Wi-Fi sleep policy>Never
Facebook Contacts do not sync:
There are two fixes for this:
By phone:Open Facebook app settings> Sync Contacts: pick either sync existing if you only want to match up current contacts or pick sync all if you want to add Facebook friends to your contacts list.
Now open your Contacts app and select a contact to "fix": then hit Menu>Edit Contact>Menu>Join
You will have to do this will all bad contacts.
By computer: Start on your phone and go to Facebook settings and sync contacts as before. Then go to your homescreen>Menu>settings>Accounts and sync and manually sync BOTH Google and Facebook contacts.
Then go to your Gmail on your computer (You can probably do this through your phone's browser but I have not tested it).
Click: Contacts then "More actions \/" then "Find and merge duplicates..." Be sure to double check them!
After that be sure to go back to your phone and manually sync. It may alert you saying that a LOT of contacts have been deleted, just accept that.
Wimax Disconnect Bug:
Problem with wimax/4G disconnecting? Open "Terminal Emulator" and type:
Code:
su <press enter>
killall dhcpcd <press enter>
Swype double tap to change word not working:
This is an issue with the text selection built in to Gingerbread itself. There are two fixes that are essentially the same. First is to single tap the word (placing the cursor in or next to it) then tap the "Swype" key. The second is to upgrade to the latest version of Swype (be sure to uninstall and current version). Instructions are in the next post. The most recent version simply stops trying to change the word on double tap so you will still have to tap the "Swype" key to change the word.
That is all I have for Fixes! Next post will be Tweaks and/or workarounds!
Tweaks to CM7:
4G:
4G/Wimax is a part of the nightlies and is in RC2. Simply update to the latest nightly/RC to enjoy!
HDMI:
#teamwin has this one figured out as well! As of this posting sound through HDMI is still not working but it works through the phone still (or external headset/speakers plugged in the headphone jack). You can download the app through the Market (Click here for market page). This no longer requires an accelerated kernel but it is helpful. If you are running CM7 Nightlies this has been included since Nightly 23. If you are on an older nightly, or RC1 or RC2 you can download it here.
Camera Shutter Sound Removal:
To remove the shutter sound remove or rename (through adb or Root Explorer or other file manager) shutter.ogg in /system/media/audio/ui (if it won't let you remember to mount R/W first!)
Swype:
Go to http://beta.swype.com and register for the beta. When installing a notification will pop up saying that it may interfere with stock beta; do not worry, this is for Sense users and Swype comes in stock Sense now.
Contact searching:
Again there are multiple work arounds:
The simplest is under the stock contacts tab (won't work under phone tab) simply long press Menu. This will bring the keyboard up and you can type to search.
You can also download "Dialer one" or "Dialer2" from the Market.
Visual Voicemail:
There is argument about this fix working.
Nandroid Backup your current CM7 setup. Wipe and flash a stock ROM. Use titanium backup to backup the app and data for VVM. Then Nandroid restore CM7 and restore the app and data for VVM.
The other option is simply to use Google Voice, you do NOT have to get a new number to do this. You can set this up at www.google.com/voice
SD Card speeds:
Transfer speeds are currently very slow with the newest kernel. This is being worked on and should be fixed before CM7 final. Until then you can either boot into recovery and use USB-MS to transfer files or you can download an app called Multi Mount SD-Card from the Market.
Force close ANY app via long-pressing back button:
Go to Menu > Settings > Applications > Development > check "Stop app via long-press"
ADW Launcher "Slow"?
midri said:
Those of you getting slugish results need to update their ADW settings (the defaults suck)
1) Screen Preferences - Desktop scrolling speed - set to something low-ish like 150-200, default settings are just plain moronic here. Desktop overshoot should be fine at 30 or 40.
2) Drawer Settings - Horizontal Drawer definite on (this is far superior to the scrolling drawer if you have more than a few apps, and feels much smoother).
3) Drawer Settings - Zoom effect speed - 400 is a decent setting, default was way too high.
4) Drawer Settings - Columns/Rows - 4x4 is a nice setting for portrait, if you don't like a crammed screen.
5) System Preferences - Wallpaper Hack - check this. If you have issues, change wallpapers to something of a sane size.
6) System Preferences - Use Screen Cache - check this.
7) System Preferences - Scrollable Widget support - you should start with this unchecked. Only check it if you have issues with some widgets. In my experience it didn't make a huge difference in performance or smoothness.
Click to expand...
Click to collapse
For now I am using this for kernels.
Savaged-Zen [2.6.37.4] [HAVS+CFS/BFS!] [with SBC]
Savaged-Zen [2.6.37.4] [HAVS+CFS/BFS!] [with noSBC]
Tiamat [2.6.37.4] [HAVS+BFS] [with or without SBC]
If you are having any problems while using these kernels please flash the stock kernel back (by reflashing the ROM) to see if the problem is the kernel or CM itself.
Changelog:
For a changelog of CM7 go here.
And lastly if you are having any hardware problems with your phone and need to return it to Sprint: Click here to unroot.
Great post. This should help a lot of people who have basic problems.
Powered by TeamWin's Innovation
Hope this doesn't sound too dumb...
But how do you get holding the "back" capacitive button to force close the app you're in? I always thought that was a CM feature, but I've never been able to figure out how to enable it...
cheapskate88 said:
Hope this doesn't sound too dumb...
But how do you get holding the "back" capacitive button to force close the app you're in? I always thought that was a CM feature, but I've never been able to figure out how to enable it...
Click to expand...
Click to collapse
Settings > Applications > Development > check "Stop app via long-press"
Swyped from my EVO
shift_ said:
Settings > Applications > Development > check "Stop app via long-press"
Swyped from my EVO
Click to expand...
Click to collapse
Thanks, added.
There is no tweak for the weak wifi drivers in AOSP(as compared to sense)
Sent from my PC36100 using XDA Premium App
dirkyd3rk said:
There is no tweak for the weak wifi drivers in AOSP(as compared to sense)
Click to expand...
Click to collapse
Do you have a tweak for this or just trolling?
PS: does anyone know of a
Spoiler
type tag that works on xda? I would like to have the individual sections minimized until clicked and spoiler doesn't work.
rstuckmaier said:
Do you have a tweak for this or just trolling?
PS: does anyone know of a
Spoiler
type tag that works on xda? I would like to have the individual sections minimized until clicked and spoiler doesn't work.
Click to expand...
Click to collapse
Spoiler
Not trolling but I do love that word. I'm running cm7 as we speak. I love cm and sense we all know the aosp wifi drivers are weak. I don't know why and no one can explain it.
Sent from my PC36100 using XDA Premium App
Last I checked, HDMwIn no longer needs a special kernel. The HDMI code was merged in to CM7 Nightlies:
http://review.cyanogenmod.com/#change,3939
Thanks, I verified that because I wasn't completely certain. But I heard it from Shinzul himself (I guess I always just assumed Shinzul was a he, apologies if I'm wrong).
hey op can you add this
su <enter>
killall dhcpcd <enter>
Its for the wimax disconnect bug. You can put that into terminal instead of reseting your phone to get back onto wimax.
Good post. Can you link the OP to the Wiki as well? There's a CM7-specific page that has a lot of this information. Would be good to cross-pollinate.
http://forum.xda-developers.com/wiki/index.php?title=HTC_Supersonic/ROMs/CM7
id love to see some lense mods, including changing the text from black to white.
baller2319 said:
hey op can you add this
su <enter>
killall dhcpcd <enter>
Its for the wimax disconnect bug. You can put that into terminal instead of reseting your phone to get back onto wimax.
Click to expand...
Click to collapse
Thanks, forgot that one because I'm not in a 4g area
sjwaste said:
Good post. Can you link the OP to the Wiki as well? There's a CM7-specific page that has a lot of this information. Would be good to cross-pollinate.
http://forum.xda-developers.com/wiki/index.php?title=HTC_Supersonic/ROMs/CM7
Click to expand...
Click to collapse
Added to the OP, thanks (ran out of xda thanks.... I'll hit you back tomorrow)
fixxxer2008 said:
id love to see some lense mods, including changing the text from black to white.
Click to expand...
Click to collapse
I know it may seem arbitrary but I'm trying to keep this just fixes and small tweaks that improve usability. Other mods are more of a person preference issue. I would like to see a thread for that, though. Maybe you could start it
This might also be of interest. From the RC2 Thread in the Development Sub-Forum.
http://forum.xda-developers.com/showpost.php?p=11388458&postcount=2
Also one thing that might want to note:
RC1 requires the 20110120 GApps which are designed for Android 2.3-2.3.2.
RC2 and Nightly 11+ require the 20110307 GApps which are designed for Android 2.3.3.
The 20110120 GApps can be grabbed from http://goo-inside.me/gapps/ and the 20110307 (since they're newest) can be found at http://goo-inside.me/gapps/latest/7/universal/
Vegasden said:
This might also be of interest. From the RC2 Thread in the Development Sub-Forum.
http://forum.xda-developers.com/showpost.php?p=11388458&postcount=2
Click to expand...
Click to collapse
Yeah, that is actually where I kanged some of the material. I just hoped that having a fresh topic would help people to find the answer as many have trouble searching the CM and nightly thread.
drmacinyasha said:
Also one thing that might want to note:
RC1 requires the 20110120 GApps which are designed for Android 2.3-2.3.2.
RC2 and Nightly 11+ require the 20110307 GApps which are designed for Android 2.3.3.
The 20110120 GApps can be grabbed from http://goo-inside.me/gapps/ and the 20110307 (since they're newest) can be found at http://goo-inside.me/gapps/latest/7/universal/
Click to expand...
Click to collapse
Yeah, I was aware of that but I figured no one would be on RC1 or pre-11 nightly anymore.
Thanks for all the help guys!
I just want to point out that the CyanogenMod kernel shipped by default uses the BFS scheduler. BFS in theory should be a better scheduler for a device like a cell phone than CFS.
Is this of value to anyone?
http://www.multiupload.com/NPZ062QIZB
Netflix is not supported on this device. Please check the Netflix website for a list of supported devices.
krymzon40 said:
Netflix is not supported on this device. Please check the Netflix website for a list of supported devices.
Click to expand...
Click to collapse
That sucks. But I was more interested in using a .prop file that pretends to be a Nexus One and would then allow the app to work. Some folks around here are pretty bright.
Does anyone know if this works on ED12?
Seems to work on the Captivate with Gingerbread:
http://forum.xda-developers.com/showthread.php?p=13730833#post13730833
tbob18 said:
Does anyone know if this works on ED12?
Seems to work on the Captivate with Gingerbread:
http://forum.xda-developers.com/showthread.php?p=13730833#post13730833
Click to expand...
Click to collapse
Good sleuthing. Hopefully someone with Gingerbread in here will try it out.
was gonna ask the same thing. obviously if the nexus S is running it, we should be able to as well since both phone use the 1gh hummingbird but im assuming the DRM security setting are probably only found in gingerbread for us so we may have to wait unless like Zenlnsight said, possibly install a workaround so it is compatible for us on froyo
Android 2.2 phones are supported, so it doesn't seem to be a Gingerbread only thing. Maybe it's a hardware support only thing.
ZenInsight said:
That sucks. But I was more interested in using a .prop file that pretends to be a Nexus One and would then allow the app to work. Some folks around here are pretty bright.
Click to expand...
Click to collapse
This
10char
Getting Protected Apps To Show in Market (Nook example below)
Certain apps (e.g. SlingPlayer) have special settings which prevent them from being backed up normally. These apps do not appear by default in the market. To enable these apps you need to change the device fingerprint and spoof a valid device.
adb pull /system/build.prop
Edit the following line:
ro.build.fingerprint=generic/sdk/generic:Honeycomb/Nook/eng.rbrune.20110131.162619:eng/test-keys
so that it reads:
ro.build.fingerprint=google/soju/crespo:2.3.2/GRH78C/93600:user/release-keys
This spoofs the Nexus S running Android 2.3.2 per this site
Save the modified build.prop to NC.
adb remount
adb push build.prop /system/
Now clear the Market cache. On the NC, open the settings app and make the following changes:
Settings -> Manage Applications -> All -> Market
Clear Cache then Force Stop -- DO NOT clear data
Settings -> Manage Applications -> All -> Google Services Framework
Clear data then Force Stop
Then reboot the NC, for example:
adb reboot
Disconnect the USB cable.
Market should now show the protected apps.
Anyone want to try to run Netflix after messing with their build.prop file?
Going to poke around and see what I can do.
Didnt get the unsupported device popup after changing bulid.prop but after inputting my email and password the app stopped and went to the homescreen. Im restarting my phone and will try again. I may have put in the wrong login info also as I haven't logged into netflix in a long time.
After restarting the unsupported device prompt comes back and it still doesn't work. FU Netflix
What about changing ro.build.description?
I edited my build.prop, was able to get to the login screen but then got dumped to homescreen after putting in my info. I also tried incorrect info, which it informed me was wrong but did not dump me to homescreen.
Don't really know what any of this means, but it's what happened.
Has anyone tried running this on a Gingerbread rom + spoofing their build prop?
On Gingerbread it may be running a gingerbread only function...or etc..
also tried running a logcat while doing it?
Schuby said:
Going to poke around and see what I can do.
Click to expand...
Click to collapse
Schweet! Do it bro. I'm at work right now. I'm going to try it later.
Edit: I just saw replies coming in . May be I spoke to soon.
Someone posted the Nexus S 4g build.prop here:
Android Hacking Netflix thread:
http://forum.xda-developers.com/showpost.php?p=13733918&postcount=170
Nexus S 4g Build.prop file
Someone else said:
I don't know what to say - I'm watching Futurama on my Nook Color as I type here on my laptop. I changed the build.prop to match my G2, and it worked right away.
What changes did you make
ro.product.model=HTC Vision
ro.product.brand=tmobile
ro.product.name=vision
ro.product.device=vision
ro.product.board=vision
ro.product.manufacturer=HTC
ro.build.fingerprint=tmobile/htc_vision/vision/vision:2.2/FRF91/277427:user/release-keys
Also, it's not actually working on my G2 as it turns out, just on my nook, which is weird.
Click to expand...
Click to collapse
Keep in mind when you guys modify this stuff, Netflix might be leaving behind residual data in /data or the SD card. If you merely change the build.prop and re-try, it may not continue to work.
This almost works for me:
ro.product.model=HTC Vision
ro.product.brand=tmobile
ro.product.name=vision
ro.product.device=vision
ro.product.board=vision
ro.product.manufacturer=HTC
ro.build.fingerprint=tmobile/htc_vision/vision/vision:2.2/FRF91/277427:user/release-keys
I used SGS Tools to change the values
It starts playing but only audio, no video and then goes back to the main netflix screen.
found it here:
http://forum.xda-developers.com/showpost.php?p=13732640&postcount=11
haas599 said:
Didnt get the unsupported device popup after changing bulid.prop but after inputting my email and password the app stopped and went to the homescreen. Im restarting my phone and will try again. I may have put in the wrong login info also as I haven't logged into netflix in a long time.
After restarting the unsupported device prompt comes back and it still doesn't work. FU Netflix
What about changing ro.build.description?
Click to expand...
Click to collapse
Are you on Gingerbread though?
Hey guys. Can we start listing what ROMs and version of Android we are using? I only think this works with Gingerbread ROMs...like ED12.
ZenInsight said:
Hey guys. Can we start listing what ROMs and version of Android we are using? I only think this works with Gingerbread ROMs...like ED12.
Click to expand...
Click to collapse
Evo4g is supported and it doesn't have official Gingerbread yet.
As far as the Epic goes, nobody has it working yet.
The epic 4G continues to be the bastard child of support and development.
Sent from my SPH-D700 using Tapatalk
When listening via built-in speakers (US TF101), it sounds like 1/3 of the original volume I had before the upgrade. Maxed out the sliders in settings etc, to no avail. Tried "Equalizer" app, no cigar either.
Is Asus aware of this issue ? A real bummer.
Same problem here. To boost the sound a bit I use PowerAmp's equalizer function. But that's not a good solution, want my sound back!
Use dspmanager if you're rooted. It amplifies the sound dramatically
i had the same problem, sound was noticeably lower and a factory reset after upgrading didn't work either.
however, the next patch they released, along with another factory reset sorted out the problem for me. have you installed the latest patch?
if you have the *17 FOTA the sound should be as it was on HC.
blackdesp said:
Use dspmanager if you're rooted. It amplifies the sound dramatically
Click to expand...
Click to collapse
no it does not, im using megatron rom
CoopZor said:
no it does not, im using megatron rom
Click to expand...
Click to collapse
I would be fine with it being louder when i use headphones. I dont use the built in speakers.
CoopZor said:
no it does not, im using megatron rom
Click to expand...
Click to collapse
Did you set the apk's permissions right? I am on revolution 3.1.0 and it runs perfectly.
acdcking12345 said:
I would be fine with it being louder when i use headphones. I dont use the built in speakers.
Click to expand...
Click to collapse
You can set speaker, headset and bluetooth headset independently with dspmanager
I am on whatever the latest FW is (I think 0317). I didn't do any factory reset or likes, not looking forward to having to reinstall 20 or so apps that I have.
I can not believe there is not an official apology from ASUS and/or a patch to fix our issues (constant reboots and this volume issue).
I've been an ASUS man for a while: a half-dozen mobos (including X79 Pro), 2 TF101 .... feels really bad to be treated like this
blackdesp said:
Did you set the apk's permissions right? I am on revolution 3.1.0 and it runs perfectly.
Click to expand...
Click to collapse
what do you mean with set apk permissions ?
rashid11 said:
I am on whatever the latest FW is (I think 0317). I didn't do any factory reset or likes, not looking forward to having to reinstall 20 or so apps that I have.
I can not believe there is not an official apology from ASUS and/or a patch to fix our issues (constant reboots and this volume issue).
I've been an ASUS man for a while: a half-dozen mobos (including X79 Pro), 2 TF101 .... feels really bad to be treated like this
Click to expand...
Click to collapse
Use the app backup tool that asus provides (and backup any photos, files + the app backup file if you are not using a micro sd card).
Doesn't take long and worth the effort if it works, and if not, you've only lost 20 min of your time - quicker than it took me to write this post cos my tablet rebooted twice in the process
CoopZor said:
what do you mean with set apk permissions ?
Click to expand...
Click to collapse
If you install the dspmanager.apk file to your /system/app/ folder manually, you have to set the user permission of this file to read and write. And group and other permissions to read only.
You can use es file explorer for setting the permissions. Navigate to /system/app/ folder, then find dspmanager.apk and long tap the file to open menu and select properties. Tap change and check the boxes as i said. But you have to enable root explorer and mount file system checkboxes under the settings of es file explorer.
Looks like is 4.0.4 is imminent and fixes some of the issues we've had since the ICS, will wait for that
I can't seem to find the equivalent to the setting that disables the "Pop-Up" notification setting in Nougat 7.0. This link explained how to do it in MM...
https://www.androidexplained.com/galaxy-s7-disable-heads-up-notifications/
Anyone find something like this?
Same here.
Well I did that and worked for me in Nougat on my S7 Edge Duos. I tried it with whatsapp and I'm not getting the preview pop-up anymore while using the phone
Sent from SM-G935FD w/ TapaTalk
sentinelvdx said:
Well I did that and worked for me in Nougat on my S7 Edge Duos. I tried it with whatsapp and I'm not getting the preview pop-up anymore while using the phone
Sent from SM-G935FD w/ TapaTalk
Click to expand...
Click to collapse
but you wont get the vibration alerts either
They actually removed that exact feature from Nougat. You can silent the entire notification, but cannot turn off the floating notifications.
I was looking for solution on this either, stupid sumsung removed one of the best nougat control over notifications that you could define levels of notifications control and their priorities even of the list (The power controls notifications)... Idiots.
Now or you only have 2 options:
NO PEEK+NO VIBRATION/SOUND
PEEK + VIBRATIONS
instead of the great different levels of notifications control. Samsung always does some **** to piss off users.... because they decreasing the control that the user have over the phone instead of increasing.
Archmag3 said:
but you wont get the vibration alerts either
Click to expand...
Click to collapse
F! That's true... sorry... I was on DND mode so I didn't realize that.
Hope we find some way...
Unless there is maybe a port from somewhere or an xposed alternative but still might not be possible since it can be far too complex as it mixes the notifications and settings, so I doubt we will ever get this properly working...
https://forum.xda-developers.com/android/general/howto-4-to-disable-heads-notifications-t3197660
I had tried HeadsOff ... no go.
stygi4n said:
https://forum.xda-developers.com/android/general/howto-4-to-disable-heads-notifications-t3197660
Click to expand...
Click to collapse
ADB method confirmed working! Thank you!!!!
(extract below...)
a) Open a terminal and check if the device is connected using the following command:
Code:
adb devices
b) You should see your phone on the list that appears. Now use the following command:
Code:
adb shell settings put global heads_up_notifications_enabled 0c) Reboot your phone.
d) Done!
mickliq said:
ADB method confirmed working! Thank you!!!!
(extract below...)
a) Open a terminal and check if the device is connected using the following command:
Code:
adb devices
b) You should see your phone on the list that appears. Now use the following command:
Code:
adb shell settings put global heads_up_notifications_enabled 0
c) Reboot your phone.
d) Done!
Click to expand...
Click to collapse
So with this method there is not PEEK but the sound still works right?
The drawback for me is that I wanted only certain apps without peek+sound, but not all the apps...
insaned said:
So with this method there is not PEEK but the sound still works right?
The drawback for me is that I wanted only certain apps without peek+sound, but not all the apps...
Click to expand...
Click to collapse
Kills peek for everything, but honestly, I don't mind.
Does anybody have a problem with count badge notification on Viber?
After update it's not working for me.
Nemanjath said:
Does anybody have a problem with count badge notification on Viber?
After update it's not working for me.
Click to expand...
Click to collapse
Is that on the home screen? If so, you can always use a launcher like Nova w/Tesla badge notification. Mine are working properly with Nova (but I don't use Viber...)
mickliq said:
Kills peek for everything, but honestly, I don't mind.
Click to expand...
Click to collapse
THis is weird but the command goes trough.. but I still have peak notifications.... wtf
edit: already tried twice
insaned said:
THis is weird but the command goes trough.. but I still have peak notifications.... wtf
edit: already tried twice
Click to expand...
Click to collapse
try to use the terminal emulator method.
stygi4n said:
try to use the terminal emulator method.
Click to expand...
Click to collapse
I just realized it's working.
However I was referring not only this peek preview but also on the notification bar... when you have a message and you slide down the bar and you have the message there.
Crap samsung has some brain freeze once in a while for eliminating this ..
What is this adb everyone is talking about? I'm having this same complaint with the peeking and use to have it turned off on most apps. Just got android 7 this morning so still looking around, but sounds like dropping this code in is an easy fix.... But where do I drop it? Is this an app for the phone or is it on my pc? Can someone please describe how to do this from the beginning, not just "use adb, put in this code. Done." maybe for some of us less intelligent but equally annoyed with peeking people so we can remove it as well. Thanks!
I can also confirm that this worked. No more heads up popup when I get messages. Tested in Google Hangout and Whatapps.
---------- Post added at 08:38 AM ---------- Previous post was at 08:32 AM ----------
Bd757 said:
What is this adb everyone is talking about? I'm having this same complaint with the peeking and use to have it turned off on most apps. Just got android 7 this morning so still looking around, but sounds like dropping this code in is an easy fix.... But where do I drop it? Is this an app for the phone or is it on my pc? Can someone please describe how to do this from the beginning, not just "use adb, put in this code. Done." maybe for some of us less intelligent but equally annoyed with peeking people so we can remove it as well. Thanks!
Click to expand...
Click to collapse
ADB is a software you need to install on your PC computer (some where there is a 5 sec installation for it). Then you need to set your phone to USB debug mode and plug it into your PC with the USB cable. Your PC will detect your device.
Go to Start on your PC and in the search area type "cmd" to bring up the black box terminal window. Then just follow the two command lines listed to first detect your phone, then run the flag to turn off the popup. Reboot. Then it will work.
Test and tried on a Sprint Samsung S7.
It will remove the popup window but preserve sound.