Hello,
Does anyone have trouble the first time they use Slacker after a re-boot?
I rooted my phone and everything works well except Slacker. I can live with this one issue, I like CM10 a lot.
Workaround (thanks to MDMOWER)
Do these one at a time, don't try to copy/paste the whole thing:
./adb root
./adb remount
./adb shell
# Make sure you have a # prompt now. If $ prompt, the following will not work.
sed -i 's/Multimedia3/MultiMedia3/g' /system/etc/snd_soc_msm/snd_soc_msm_2x
sed -i 's/lpa\.decode=false/lpa\.decode=true/g' /system/build.prop
exit
./adb reboot
wait for phone to reboot
./adb pull /data/app/com.slacker.radio-1.apk ./
#From the phone, Uninstall Slacker
./adb install -s com.slacker.radio-1.apk
Do your own thing.
This might be related to the problem with media playback in general after a reboot. If you try playing audio using a different app after a reboot you will likely experience the same issue. I first came across it using Google Music and reported it in the CM thread. I don't think there's been any progress on it.
altayh said:
This might be related to the problem with media playback in general after a reboot. If you try playing audio using a different app after a reboot you will likely experience the same issue. I first came across it using Google Music and reported it in the CM thread. I don't think there's been any progress on it.
Click to expand...
Click to collapse
Thanks for the info. I'll widen my search to more generic media.
Thanks for the hint.
I found a build.prop modification that seems to work: lpa.decode=truefalse
Reboot and Slacker worked first try. Any idea what lpa.decode is responsible for?
Sum Dumb Guy said:
I found a build.prop modification that seems to work: lpa.decode=true
Click to expand...
Click to collapse
Setting it to true fixed the problem completely? Did it have any side effects?
Sum Dumb Guy said:
Reboot and Slacker worked first try. Any idea what lpa.decode is responsible for?
Click to expand...
Click to collapse
It looks like it's an option to enable low power audio. This and this were all I could find about it.
altayh said:
Setting it to true fixed the problem completely? Did it have any side effects?
It looks like it's an option to enable low power audio. This and this were all I could find about it.
Click to expand...
Click to collapse
At this point I haven't encountered any ill effects. Granted, I mainly use my "phone" for music, GPS, text and email (in that order) and all have continued to work as needed.
Sum Dumb Guy said:
Thanks for the hint.
I found a build.prop modification that seems to work: lpa.decode=true
Reboot and Slacker worked first try. Any idea what lpa.decode is responsible for?
Click to expand...
Click to collapse
lpa.decode is already set to true. Do you mean you set it to false? Was it sufficient or did you also have to change lpa.use-stagefright?
My bad, you're correct, it should say lpa.decode=false. I haven't changed anything else in the build.prop. Are there other adjustments that might be beneficial? What is the lpa.use-stagefright all about? It's not in my current build.prop.
Sum Dumb Guy said:
My bad, you're correct, it should say lpa.decode=false. I haven't changed anything else in the build.prop. Are there other adjustments that might be beneficial? What is the lpa.use-stagefright all about? It's not in my current build.prop.
Click to expand...
Click to collapse
A logcat that captures the crash would be helpful. Keeping low-power-audio enabled is generally a good idea. While you're at it, also grab dmesg.
mdmower said:
A logcat that captures the crash would be helpful. Keeping low-power-audio enabled is generally a good idea. While you're at it, also grab dmesg.
Click to expand...
Click to collapse
Will do.
I'll work on getting those reports this weekend. In the meantime, I'll set my build.prop back to default.
Sum Dumb Guy said:
Will do.
I'll work on getting those reports this weekend. In the meantime, I'll set my build.prop back to default.
Click to expand...
Click to collapse
No need to provide a logcat, I've reproduced the issue. Seems LPA isn't working right now, so setting lpa.decode=false is the best thing to do for now.
mdmower said:
No need to provide a logcat, I've reproduced the issue. Seems LPA isn't working right now, so setting lpa.decode=false is the best thing to do for now.
Click to expand...
Click to collapse
Great, I'm glad you've reproduced the issue. Is there any onther setting I should consider besides lpa.decode=false?
BTW, I tried the PAC rom from goo. Didn't like it much, my phone rebooted randomly. Back to CM10.1RC2.
Thanks,
dafteed and
mdmower said:
No need to provide a logcat, I've reproduced the issue. Seems LPA isn't working right now, so setting lpa.decode=false is the best thing to do for now.
Click to expand...
Click to collapse
mdmower,
Since you've reproduced the issue, have you been able to determine if it's a CM10.1 issue or an Incredible 4g issue? Also, I've seen a couple posts about LPA and stagefright but not a lot of real info as to what they do or the consequences of turning them on or off. I currently have lpa.use-stagefright=true and lpa.decode=false. Should I expect reduced battery life or lack of DSP control? I can't hear any difference with stagefright not included, true, or false. I don't know if that's related to the LPA.decode=false or not.
Thanks,
J
Sum Dumb Guy said:
mdmower,
Since you've reproduced the issue, have you been able to determine if it's a CM10.1 issue or an Incredible 4g issue? Also, I've seen a couple posts about LPA and stagefright but not a lot of real info as to what they do or the consequences of turning them on or off. I currently have lpa.use-stagefright=true and lpa.decode=false. Should I expect reduced battery life or lack of DSP control? I can't hear any difference with stagefright not included, true, or false. I don't know if that's related to the LPA.decode=false or not.
Thanks,
J
Click to expand...
Click to collapse
It is a fireball issue. For now, the lpa.decode=false fix is sufficient and a good idea. It should have negligible impact on battery life.
mdmower said:
It is a fireball issue. For now, the lpa.decode=false fix is sufficient and a good idea. It should have negligible impact on battery life.
Click to expand...
Click to collapse
Is this likely to be incorporated into the next build, or will it remain unchanged to keep the CyanogenMod ROM pure?
EDIT: I see you already addressed this in the CyanogenMod thread. I take it you'll make the change in an upcoming build.
Slacker Current Status
I started using RC4 this weekend. It seems to be pretty good: Slacker has been +95% stable. One time it didn't want to play or update the cache but a force close and reopen solved that issue. Another of my other apps that was a little unstable (TDA Trader) is working without any problems.
MDMower: Thanks for your support and work on CM10
It seems a couple typos messed up low power audio (Multimedia instead of MultiMedia) - thanks go to intervigil for finding the error. This bug is quite easy to fix.
Step 1) Settings > Developer options > Root access: Apps and ADB
Step 2) Type these lines one at a time at a command prompt (do not copy/paste the whole block at once):
Code:
adb root
adb remount
adb shell
# Make sure you have a # prompt now. If $ prompt, the following will not work.
sed -i 's/Multimedia3/MultiMedia3/g' /system/etc/snd_soc_msm/snd_soc_msm_2x
sed -i 's/lpa\.decode=false/lpa\.decode=true/g' /system/build.prop
exit
adb reboot
It should be safe to perform even if you're unsure of whether lpa.decode is currently set to true or false.
mdmower said:
It seems a couple typos messed up low power audio (Multimedia instead of MultiMedia) - thanks go to intervigil for finding the error. This bug is quite easy to fix.
Step 1) Settings > Developer options > Root access: Apps and ADB
Step 2) Type these lines one at a time at a command prompt (do not copy/paste the whole block at once):
Code:
adb root
adb remount
adb shell
# Make sure you have a # prompt now. If $ prompt, the following will not work.
sed -i 's/Multimedia3/MultiMedia3/g' /system/etc/snd_soc_msm/snd_soc_msm_2x
sed -i 's/lpa\.decode=false/lpa\.decode=true/g' /system/build.prop
exit
adb reboot
It should be safe to perform even if you're unsure of whether lpa.decode is currently set to true or false.
Click to expand...
Click to collapse
I'm on RC5 now. I did the above and after a re-boot confirmed that lpa was changed to true. I'm not sure how to check if the other command executed correctly. Slacker started and I was able to play a streaming station without any problems.
My cached stations did not work. I received a message: Tuning Error Station not found. I closed (using quit from the slacker menu) and reopened but cached still didn't work. forced close, reopen slacker and both streaming and cached worked. I rebooted a couple of times with the exact same results.
For grins, I forced close Slacker immediately after a reboot and cache worked first time.
Any ideas, do you want a logcat, or should I start something with Slacker?
Thanks,
I think I found a workaround. I uninstalled Slacker and installed through ADB onto the sdcard.
The current setup:
10.1 nightly 7.2.13
Followed your instructions for MultiMedia. I don't know if it's still needed, but I figured out what the command sed was after I ran it.
./adb root
./adb remount
./adb shell
# Make sure you have a # prompt now. If $ prompt, the following will not work.
sed -i 's/Multimedia3/MultiMedia3/g' /system/etc/snd_soc_msm/snd_soc_msm_2x
sed -i 's/lpa\.decode=false/lpa\.decode=true/g' /system/build.prop
exit
./adb reboot
wait for phone to reboot
./adb pull /data/app/com.slacker.radio-1.apk ./
Uninstall Slacker
./adb install -s com.slacker.radio-1.apk
First time opening Slacker it wanted to reset the cache. Select OK.
No problem listening to streaming or cache stations.
Rebooted a couple of times, kept working, no problem.
Weeeeeeeeeeeeeeee!!!!!!!!!!!!!!!!!!!!!!
Related
[How To][Fix] Improve Battery Life By Removing "Cell Service" ORIGONAL THREAD.
Improve Battery Life By Removing Cell Standby:
Explanation:
Cell Standby is the service that your phone, in this case the nook color, uses to communicate with the cell tower. It has three main components, two of witch are located on the nook color: Mms.apk, Phone.apk, TelephonyProvider.apk. This service regulates the communication of the device with a GSM or CDMA based mobile network. The nook color doesn't have a need for this because of the lack of a cell radio. If we remove both Phone.apk, and TelephonyProvider.apk from the nook color, the service will no longer drain battery, and the device will still run!
Method One: backs up both files in c:/
adb pull /system/app/Phone.apk c:/
adb pull /system/app/TelephonyProvider.apk c:/
adb shell
mount -o remount,rw /dev/block/mmcblk0p5 /system
rm /system/app/Phone.apk
rm /system/app/TelephonyProvider.apk
reboot
Method Two: renames both files so they are no longer active.
adb shell
mount -o remount,rw /dev/block/mmcblk0p5 /system
mv /system/app/Phone.apka
mv /system/app/TelephonyProvider.apka
reboot
Method Three: use root explorer
Pick witch method you like, back up or rename, and simply do it in root explorer. Just remember to reboot when your done.
Questions and Answers:
Q: I did this but i still see the "Phone Idle" service running, what's up with that?
Phone Idle is the service that keeps the phone going when nothing is happing, like sitting with your car in neutral the engine still pumps small amounts of gas into the pistons to keep it going. Cell standby is the only service that I know of associated with actual specific phone to cell network communication.
Nice find. However, I had no mms.apk which may be due to the rooting method I used. I used RootExplorer to rename phone.apk and TelephonyProvider.apk to new filenames with a .bak extension. Rebooted and I can see the service is no longer running.
Yes, I have done this and also didn't have mms.apk. Great find! And, when checking running services, I see something called "IN-STORE SERVICE". Is it possible that this can be stopped? I think it's an app watching for a possible update?
docfreed said:
Yes, I have done this and also didn't have mms.apk. Great find! And, when checking running services, I see something called "IN-STORE SERVICE". Is it possible that this can be stopped? I think it's an app watching for a possible update?
Click to expand...
Click to collapse
I also found yesterday (while sniffing for WEP on laptop) that the wifi sends probes for something like "attwifibarnesnobles". It must be linked to that service. Didn't find a way to disable it yet.
Unless you're paranoid, why would you want to disable it? That service is how B&N detects your device in-store to be able to give you special treatment, offers, etc when connected to in-store WiFi. It's not doing any harm as far as I'm concerned. Of course, I'm only interested in removing services that are still running even though the associated hardware is missing. Done with that.
boutch55555 said:
I also found yesterday (while sniffing for WEP on laptop) that the wifi sends probes for something like "attwifibarnesnobles". It must be linked to that service. Didn't find a way to disable it yet.
Click to expand...
Click to collapse
If you disable the in store service or the B&N services you will disable the Barnes and Noble services for in-store book reading. If that's not your thing, go for it.
But if you use your Nook for anything B&N that may be something you break. fyi.
mrodlies said:
The nooks system image still has both the Phone.apk and TelephonyProvider.apk
If we remove both of these .apk's the "cell standby" service will never run and drain life.
Must have rooted nook color, adb access/root explorer, and a brain.
1. Type this up in adb or do it in root explorer:
adb pull /system/app/Mms.apk c:/
adb pull /system/app/TelephonyProvider.apk c:/
adb shell
mount -o remount,rw /dev/block/mmcblk0p5 /system
rm /system/app/Mms.apk
rm /system/app/TelephonyProvider.apk
reboot
Its as simples as that. Cell standby no longer runs, and therefore no longer drains valuable battery life, and the old .apk's are backed up if we need them later for some odd reason.
Click to expand...
Click to collapse
I have a feeling poster copied and pasted this from somewhere because notice how his first sentence says "Phone.apk and TelephonyProvider.apk" but then his script says "Mms.apk"....what happened to Phone.apk because there is no Mms.apk in the system folder on any Nook I have. So below is the corrected script and also this entire process in done in dos instead of in adb;
Code:
adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system
adb shell mv /system/app/Phone.apk /system/app/Phone.OLD
adb shell mv /system/app/TelephonyProvider.apk /system/app/TelephonyProvider.OLD
adb reboot
There is no adverse effect from doing this & it's confirmed after while in NookTools there is no Cellstandy service running. Your files are just renamed instead of removed.
Want to undo this process?
Code:
adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system
adb shell mv /system/app/Phone.OLD /system/app/Phone.apk
adb shell mv /system/app/TelephonyProvider.OLD /system/app/TelephonyProvider.apk
adb reboot
Effects on battery life of removing Cell Services
My battery life on the Nook has really been excellent thus far. I have been using it to do all of my web browsing, and have not even turned my laptop on except for using ADB to tinker with the Nook. I am able to get 2 days of substantial use including some gameplay and listening to podcast or music. So it will be interesting to see what effect removing the Cell Services has on battery life.
I too did not have the Mms.apk on my Nook already and instead removed the Phone.apk.
A huge side benefit of using my Nook is that I haven't been tinkering with my Droid hardly at all now. I've offloaded many of the duties that I relied on my phone to handle off on to the Nook Color. This has drastically increased the battery life of my phone and I now can get away with charging it once every other day. I was routinely charging my Droid twice a day previously.
I seem to always be around a WiFi network so I haven't had to really use my Droid WiFi tether to share internet with the Nook.
The nook really has changed how I use all my devices and is now my primary internet access device. Something I totally didn't expect would happen when I purchased the device.
Nice find. Cell standby was using 75% of my battery!
Sent from my NookColor using the XDA app
Nice find but i'm gonna lock this due to incorrect code/
Use http://forum.xda-developers.com/showthread.php?t=888216
Reopened.......although from the findings i see.
You reworded from http://nookdevs.com/NookColor:_Nookie_Froyo_Tips#Removing_Cell_Standby_Battery_Usage
To be honest you cant miss-type phone.apk with mms.apk
So i reopened the thread cause you asked me to.
Although going into someone else thread and commenting the words you did, was/is uncalled for.
He only fixed the commands you "found" and made scripts for the commands.
How about you start linking your source? Cause the source i see has the same mistake.
It happens. We ALL are here to better our Nooks.
Mikey1022 said:
Reopened.......although from the findings i see.
You reworded from http://nookdevs.com/NookColor:_Nookie_Froyo_Tips#Removing_Cell_Standby_Battery_Usage
To be honest you cant miss-type phone.apk with mms.apk
So i reopened the thread cause you asked me to.
Although going into someone else thread and commenting the words you did, was/is uncalled for.
He only fixed the commands you "found" and made scripts for the commands.
How about you start linking your source? Cause the source i see has the same mistake.
It happens. We ALL are here to better our Nooks.
Click to expand...
Click to collapse
My source was my brain. The other posts source was me, and no credit was given.
Sent from my LogicPD Zoom2 using XDA App
OMFG.
Can we just get this re-locked?
mrodlies said:
My source was my brain. The other posts source was me, and no credit was given.
Sent from my LogicPD Zoom2 using XDA App
Click to expand...
Click to collapse
Either it is a HUGE coincidence or the odds of you picking the same 3 files to delete in system folder is astronomical. Since one of the three files never existed
http://forum.xda-developers.com/Revision as of 21:22, 22 December 2010 (view source)http://nookdevs.com/index.php?title=NookColor:_Nookie_Froyo_Tips&diff=4413&oldid=4393
Are you still gonna lie to a mod and the community??
Since your thread was created after the fact......... Yesterday, 04:16 AM
Anyways, have some respect
Mikey1022 said:
Either it is a HUGE coincidence or the odds of you picking the same 3 files to delete in system folder is astronomical. Since one of the three files never existed
http://forum.xda-developers.com/Revision as of 21:22, 22 December 2010 (view source)http://nookdevs.com/index.php?title=NookColor:_Nookie_Froyo_Tips&diff=4413&oldid=4393
Are you still gonna lie to a mod and the community??
Since your thread was created after the fact......... Yesterday, 04:16 AM
Anyways, have some respect
Click to expand...
Click to collapse
if you know anything about the actual android system you would know that on regular android phones that have the "cell standby" service is always three files: Phone.apk, Mms.apk, and TelephonyProvider.apk. So my natural response to removing this service was to try and delete all three of those files. If you want to call me a lie, i cant change what you think, but if you want the truth, i didnt copy it from any where, it was just head knowledge of messing with android for 2+ years.
some people just like a good ol witch-hunt for credit
i read the OP and moved out what was there and have some pretty damn good battery life.
thx to the OP
nice find dude don't worry about the haters
Thanks OP! I tried it last night and already I can tell a difference!
Sent from my rooted Nook Color using XDA App
I am the person who added this information to the Wiki and I did it specifically for the Nookie Froyo build, which is why it includes the Mms.apk.
I could care less one way or the other who uses it or for what purpose, I am just glad that we can use it on our devices using the stock software as well as the Froyo build.
It is perfectly reasonable to expect that more than one person could come to the same conclusion about the impact of removing these services, so please ease up on mrodlies and lets get on with life..
In addition, this "trick" has been documented several times in threads for different tablet devices without cell based services....
-Robert
BertoJG said:
I am the person who added this information to the Wiki and I did it specifically for the Nookie Froyo build, which is why it includes the Mms.apk.
I could care less one way or the other who uses it or for what purpose, I am just glad that we can use it on our devices using the stock software as well as the Froyo build.
It is perfectly reasonable to expect that more than one person could come to the same conclusion about the impact of removing these services, so please ease up on mrodlies and lets get on with life..
In addition, this "trick" has been documented several times in threads for different tablet devices without cell based services....
-Robert
Click to expand...
Click to collapse
Leave it to Dr. Bunson Honeydew to put it all in perspective.
Like many others I was seeing many wakeups by com.android.phone, and as noted by others this is because of fast dormancy. Or rather, because of LG's implementation of it.
I'm not gonna go into too much detail, but the offending implementation can be found in com/android/internal/telephony/LgeFDHandlerInterfaceImpl . This class is in /system/framework/com.lge.core.jar . After data activity on HSPA networks they use AlarmManager to periodically wake up and check the number of bytes transmitted over the network interface. This goes on until some time after it stops changing, and the connection is considered dormant.
This periodic checking is what's waking the device, and for every new byte transferred the wakeup/polling period is extended and device doesn't sleep. The chattier apps are, the more awake time you'll get.
Enough of the boring details, here's how I disabled it and got rid of the com.android.phone wakeups. Root required.
Code:
$ adb shell
# su
# sqlite3 /data/data/com.android.providers.telephony/databases/telephony.db
update dcm_settings set fastdormancy="0" where numeric="310410";
.quit
# reboot
This helped me, hope it does the same for you.
Edit 2:
I've written a quick and dirty app that tries to handle this setting without need for terminals or root. Try it and report issues here: http://forum.xda-developers.com/showthread.php?t=2021248
Edit 1:
In essence you need to change a value in a sqlite database and there are many ways to do it. There are apps, use adb shell etc. Whatever works for you. If someone wants to write an app that makes this easier, be my guest
Reversal is restoring the original value "1,0,0,1000,5000,60000,3000,5000,1,8" and reboot:
Code:
update dcm_settings set fastdormancy="1,0,0,1000,5000,60000,3000,5000,1,8" where numeric="310410";
This database is not there after a wipe, so future ROM chefs wanting to include it by default should edit /etc/dcm_settings.xml as this is where the initial database contents come from. Just replace the original value with "0" for ATT.
Code:
<profile>
<siminfo
operator="ATT"
country="US"
mcc="310"
mnc="410"
extraid=""
/>
<settings
fastdormancy_param="1,0,0,1000,5000,60000,3000,5000,1,8"
ipmtu="1410"
/>
</profile>
Holy Hell!!!
so far so good...it's a shame I can only thank so much!!!
jonasl said:
Like many others I was seeing many wakeups by com.android.phone, and as noted by others this is because of fast dormancy. Or rather, because of LG's implementation of it.
I'm not gonna go into too much detail, but the offending implementation can be found in com/android/internal/telephony/LgeFDHandlerInterfaceImpl . This class is in /system/framework/com.lge.core.jar . After data activity on HSPA networks they use AlarmManager to periodically wake up and check the number of bytes transmitted over the network interface. This goes on until some time after it stops changing, and the connection is considered dormant.
This periodic checking is what's waking the device, and for every new byte transferred the wakeup/polling period is extended and device doesn't sleep. The chattier apps are, the more awake time you'll get.
Enough of the boring details, here's how I disabled it and got rid of the com.android.phone wakeups. Root required.
Code:
$ adb shell
# su
# sqlite3 /data/data/com.android.providers.telephony/databases/telephony.db
update dcm_settings set fastdormancy="0" where numeric="310410";
.quit
# reboot
This helped me, hope it does the same for you.
Click to expand...
Click to collapse
I use Comand prompt and copy these codes?
Thanks a lot for this, can you please explain how to use this code, i am rooted and am trying to run this on my computer with adb and i get a message sqlite3 not found
I plugged my phone in as charge only and ran this code using cmd.
After the end of each line simply press enter and it prompts for the next.
When you prompt for reboot, it takes a couple of seconds, for those who get confused when their phone sits there.
Anyway, the code seems to work for me, looking forward to results.
Hope this helped.
Im getting a no sqlite3 found error as well
pfoxdizzle said:
Im getting a no sqlite3 found error as well
Click to expand...
Click to collapse
I just used sqlite editor from the market and edited the value to "0". I can confirm that this process works, i have been struggling with this wakelock for 2 weeks now and have tried so many things but this is the only thing that has worked. Kudos to the OP!!:fingers-crossed:
Are you both rooted and have unlocked bootloader? Not sure why you're getting errors. Did any of you retry this process via computer cmd with USB debugging?
Sent from my LG-E970 using xda app-developers app
rooted yes. Unlocked no.
Unlock. It literally takes no time.
Sent from my LG-E970 using xda app-developers app
unlocking should not affect this. And there isnt anything worth unlocking for yet. So i will keep my warranty
Warranty is kinda meh unless you're prone to breaking your phone. But everyone does things their own way.
Are you sure that you have sqlite3 on your phone and/or are you typing the code correctly in cmd? Via computer is the easiest way.
Ok, I have my LGOG rooted and unlocked and been trying to run this and can't get it to take. I'm not a noob, and I've used cmd prompt plenty for other phones. I had to use it a ton for my HTC One X. For some reason I can't get it to recognize the phone. Any suggestions?
What's the output from the cmd prompt?
Sent from my LG-E970 using xda app-developers app
pfoxdizzle said:
Im getting a no sqlite3 found error as well
Click to expand...
Click to collapse
Something not mentioned, you are in a command prompt within the folder containing these tools right?
NVM
I'm assuming this fix was properly applied on my end?
Yoreo said:
I'm assuming this fix was properly applied on my end?
Click to expand...
Click to collapse
That's what I got, too.
I think yes, that took care of it.
LTE issues
I'm guessing this fix won't necessarily disable LTE when available and the phone would be able to switch back to LTE from DC-HSPA+ when it sees that LTE is available in the area?
Murasakiii said:
What's the output from the cmd prompt?
Sent from my LG-E970 using xda app-developers app
Click to expand...
Click to collapse
Hopefully the image is coming through on the errors I'm getting while trying this. I'm sure I'm tired and doing something stupid, I just can't figure it out.
Right guys THIS thread is for reporting bugs\issues and for solutions, i will update this with every new release\hot\bugfix.
Please post logcats and please post your error like this:
Version of rom your running
DETAILED ERROR HERE (not just wifi doesnt work, explain on how it didnt work so we can reproduce)
Any mods your running and kernel version
Code:
Currently Not working
NFC ---- fixed for when i release the next build
Bluetooth (kernel issue not rom so bug maxwen about this)
Please tell me if anything else is broken
We have a hard time with audio because we currently cannot use
the stock audio drivers since they crash in loading - Big thanks to HTC
We found a way using HOX drivers for now and changing kernel
so that we have "basic" audio now.
If all goes well when I get home from work expect a audio "fixed" build
Sent from my One V using Tapatalk 2
Use this thread to give me bug reports and so on...
oops i forgot about the menu button "issue" for now remap the buttons settings > system > hardware keys
Sometimes when unlocking the lock screen or changing activity, a red frame appears for about 0.5 sec and disappears
it's because i did an engineering build and not a user build
if it really annoys you edit the build.prop
look for
ro.build.type=eng
and change it to
ro.build.type=user
i'll do user builds from now on
Just a short one
I switched to CM10 now as my "daily" on HOX+
Runs absolutley stable.
So you shoulda give it a try
used a test version without audio solution from Lloir a few days above.
having trouble with wifi...there was no connection.
a give CM a new try, after update to CM10.1
i think LLoir will build it in a few weeks
skdubg said:
used a test version without audio solution from Lloir a few days above.
having trouble with wifi...there was no connection.
a give CM a new try, after update to CM10.1
i think LLoir will build it in a few weeks
Click to expand...
Click to collapse
a logcat would help...wifi works perfectly for everyone else :/
how can i create this logcat?
this thread has everything you need in http://forum.xda-developers.com/showthread.php?t=1616059
thats all?
only
adb logcat > logcat.txt
?
skdubg said:
thats all?
only
adb logcat > logcat.txt
?
Click to expand...
Click to collapse
yes
but you can also record logcats on the device with an app
like e.g. alogcat
thanks...
sounds very simple to do
skdubg said:
thanks...
sounds very simple to do
Click to expand...
Click to collapse
Oh BTW missed something about this
In JB an app needs permissions to read the logs
So if you use e.g. alogcat and it actually doesnt display the log
do the following in a shell (only required once)
Code:
adb shell pm grant <pkg> android.permission.READ_LOGS
for alogcat replace <pkg> with org.jtb.alogcat
So finally this becomes for alogcat
Code:
adb shell pm grant org.jtb.alogcat android.permission.READ_LOGS
okay maxwen. thanks again :fingers-crossed:
i will do it later this day....
I have found a non-important issue but can't find the reason. Sometimes when i turn off the phone it doesn't shows me the crt effect and also sometimes it directly passes through the lock screen. I don't have a pass code or any kind of security on my device. Both of them are not important for me but they are still a issue. If it's necessary I can provide a logcat as soon as I arrive home.
By the way when I was using aosp derived roms on my HTC one x there was a huge drain issue, fortunately this rom doesn't have that issue. Great job.
Sent from my HTC One X+ using XDA Premium HD app
leventccc said:
I have found a non-important issue but can't find the reason. Sometimes when i turn off the phone it doesn't shows me the crt effect and also sometimes it directly passes through the lock screen. I don't have a pass code or any kind of security on my device. Both of them are not important for me but they are still a issue. If it's necessary I can provide a logcat as soon as I arrive home.
Click to expand...
Click to collapse
These are two "known issues" regarding both CRT animation
and lock screen in current CM10 code. I have seen these also on the HOV
hey,
i have no telephone-app in the drawer and my SMS app don't work.
greez
Hi!
I am using DSC's ROM (on 1.7 ATM) and I sometimes get a "flashing lights" and immediate reboot when my phone tries to use location services -I can't be sure if it's GPS, WiFi, or both-. I think I flashed the right BB when I installed the ROM -there was a batch script that took care of that if I remember correctly-, but quite frankly, after having spent many hours around the forums, not being sure what to do exactly, and having a bit of fear of bricking it/whatever; I'd rather ask beforehand. So:
What should I do?
About phone says:
BB: GAUSB1A1406214-EU
Thanks!
try disabling > use wireless networks
it should be inside > location & security settings
something similar..
I just did; the phone crashed and it's now rebooting. I was running logcat at the time, but nothing relevant showed before the reboot.
well... usually try using dsc 1.0 and see what happen..
there are reports that google maps is the causing of the problem though.. i dont use it btw...
Oddly enough, I've just tried several apps which use location services and it has not yet crashed. It's not getting a fix since I'm indoors, but at least it hasn't crashed yet...
europeancity said:
Oddly enough, I've just tried several apps which use location services and it has not yet crashed. It's not getting a fix since I'm indoors, but at least it hasn't crashed yet...
Click to expand...
Click to collapse
Try installing the latest version (2.1) or DSC 2.0 they have less or even none issues. Don't forget to wipe caches and fix permissions.
The behaviour didn't change when I upgraded from an older DSC ROM to 1.7... Why would it matter exactly? Were there any bugs corrected on that release that could affect the location services?
europeancity said:
The behaviour didn't change when I upgraded from an older DSC ROM to 1.7... Why would it matter exactly? Were there any bugs corrected on that release that could affect the location services?
Click to expand...
Click to collapse
Take a look here:
http://forum.xda-developers.com/showthread.php?t=1751041
I read the linked thread and it sounds very much like the problem I'm having. However, I thought that problem had already been corrected by 1.7, and I couldn't see any output on the logcat the last time it rebooted. So: should I try with the 366BB and Kernel? Should I upgrade to 2.1? Thanks!
europeancity said:
I read the linked thread and it sounds very much like the problem I'm having. However, I thought that problem had already been corrected by 1.7, and I couldn't see any output on the logcat the last time it rebooted. So: should I try with the 366BB and Kernel? Should I upgrade to 2.1? Thanks!
Click to expand...
Click to collapse
I disabled the reboot code in kernel but no idea if it helps really.
Upgrade won't hurt i think.
_n0p_ said:
I disabled the reboot code in kernel but no idea if it helps really.
Upgrade won't hurt i think.
Click to expand...
Click to collapse
I can't really be sure about it, but... wasn't that change already present in 1.7?
How long could it take, and how hard would it be for a n00b like myself (although with some programming experience) to add some logging output when the reboot *would have* happened?
Thank you really! I'm getting more and more interested in this!
europeancity said:
I can't really be sure about it, but... wasn't that change already present in 1.7?
How long could it take, and how hard would it be for a n00b like myself (although with some programming experience) to add some logging output when the reboot *would have* happened?
Thank you really! I'm getting more and more interested in this!
Click to expand...
Click to collapse
2.1 has an option to disable kernel NoSync hack.
Also, look here:
http://forum.xda-developers.com/showpost.php?p=35386212&postcount=5686
Sweet. I will flash it and come back with feedback.
Thanks!
Sent from my Dell Streak using xda app-developers app
Let's start a list of build.prop modifications that work!
net.tethering.noprovisioning=true
Enabled tethering
persist.debug.wfd.enable=1
Enables miracast. Go into cast settings and enable wireless display
Change persist.audio.fluence.voicecall to false
Disable noise cancellation
This is all I have found so far. What other mods are you using?
User contributions:
enable multi window
ro.build.type=userdebug
lock screen auto rotate
log.tag.launcher_force_rotate=VERBOSE
lockscreen.rot_override=true
Disable the nav bar
qemu.hw.mainkeys=1
ro.build.type=userdebug
That will allow you to enable multi-window.
I'm guessing these changes will break Android pay?
Sent from my Nexus 6P using Tapatalk
will.bates94 said:
I'm guessing these changes will break Android pay?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I would like to know the same. I want to enable miracast but not break android pay
will.bates94 said:
I'm guessing these changes will break Android pay?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I think it would be best practice to assume that any mods to the sys folder, including modifying build.prop, will cause the SafetyNet tests to fail, therefore causing Android Pay and all other apps that use that API to stop working. That being said, I THINK some mods to the build.prop have gone undetected. Also, reverting any changes should restore full functionality.
I enabled miricast. It doesn't work with every app, but maybe that's due to a root check or something...
SomeGuy4 said:
net.tethering.noprovisioning=true
Enabled tethering
Click to expand...
Click to collapse
I heard a rumor that the native tether works out of the box, so the build.prop mod may not be necessary....? I am able to turn it on, but i didn't try connecting to it with another device yet, so I can't verify.
I'd love to know more build.prop mods, too!
AranelAlasse said:
I enabled miricast. It doesn't work with every app, but maybe that's due to a root check or something...
I heard a rumor that the native tether works out of the box, so the build.prop mod may not be necessary....? I am able to turn it on, but i didn't try connecting to it with another device yet, so I can't verify.
I'd love to know more build.prop mods, too!
Click to expand...
Click to collapse
I have the tethering build.prop edit and I am able to add a card to Android Pay. I have not been able to test it at a retailer yet.
As far as native tethering goes, that will depend on your carrier. I have Cricket who actively started blocking it a while ago so they can charge a $10 fee to turn it on. Prior to that it worked fine natively.
iamyourdemize said:
As far as native tethering goes, that will depend on your carrier. I have Cricket who actively started blocking it a while ago so they can charge a $10 fee to turn it on. Prior to that it worked fine natively.
Click to expand...
Click to collapse
Interesting. I have Verizon, and still on the unlimited data plan... Hotspot worked great for me last night for several hours using the native toggle (without a build.prop edit). I'll be curious and wary for a while, though, to see if something on my bill changes...
Android pay works for me after the tweaks. I actually temp booted TWRP to add these two lines into the build.prop therefore root not needed at all to accomplish this.
sarcoptic said:
I actually temp booted TWRP to add these two lines into the build.prop
Click to expand...
Click to collapse
I tried to modify build.prop in TWRP, but couldn't figure out how... What steps do you use to do that?
AranelAlasse said:
I tried to modify build.prop in TWRP, but couldn't figure out how... What steps do you use to do that?
Click to expand...
Click to collapse
1. Boot twrp
fastboot boot recovery.img
2. Go to Mounts and mount the system partition, by default mine was not checked
3. Pull build.prop
adb pull /system/build.prop
4. Edit build.prop
net.tethering.noprovisioning=true
persist.debug.wfd.enable=1
5. Push build.prop
adb push build.prop /system/build.prop
6. Set permissions
adb shell
chmod 644 /system/build.prop
7. Reboot and profit
sarcoptic said:
1. Boot twrp
fastboot boot recovery.img
2. Go to Mounts and mount the system partition, by default mine was not checked
3. Pull build.prop
adb pull /system/build.prop
4. Edit build.prop
net.tethering.noprovisioning=true
persist.debug.wfd.enable=1
5. Push build.prop
adb push build.prop /system/build.prop
6. Set permissions
adb shell
chmod 644 /system/build.prop
7. Reboot and profit
Click to expand...
Click to collapse
Aah, I see. Yes, I read about doing it that way, but I didn't have my computer cord handy and couldn't use adb or fastboot. I was trying to use the terminal inside of TWRP. vi just gave endless output... and I saw that ed is on there somewhere, but didn't know how to use it... plus i don't know if those editors are usable from TWRP command line or if they're only there for the system's use. It's been too long since I've been in the linux world (sad. ), so I didn't try very hard.
---------- Post added at 12:34 PM ---------- Previous post was at 12:31 PM ----------
on a different note, I think the (experimental) multi-window feature can be enabled via build.props, but I don't recall the details.
I edited my build.prop to turn off noise cancellation (change value to false)
Afterwords, safetynet still passes (using safetynet helper app).
luigidk said:
I edited my build.prop to turn off noise cancellation (change value to false)
Afterwords, safetynet still passes (using safetynet helper app).
Click to expand...
Click to collapse
what is the benefit of turning off noise cancellation?
Sent from my Nexus 6P using Tapatalk
slaydog said:
what is the benefit of turning off noise cancellation?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
so people can hear you better (most of us get "we can't hear you" though we're shouting) (that's what i understood from the post)
slaydog said:
what is the benefit of turning off noise cancellation?
Click to expand...
Click to collapse
Some say it makes a difference in call quality, some not. Worth a shot if you have issues.
RockyAJ said:
so people can hear you better (most of us get "we can't hear you" though we're shouting) (that's what i understood from the post)
Click to expand...
Click to collapse
jejb said:
Some say it makes a difference in call quality, some not. Worth a shot if you have issues.
Click to expand...
Click to collapse
Thanks for the heads up, guys!
Sent from my Nexus 6P using Tapatalk
AranelAlasse said:
I tried to modify build.prop in TWRP, but couldn't figure out how... What steps do you use to do that?
Click to expand...
Click to collapse
Why not just use a root explorer and go to the system folder. Remember to reboot for changes to take effect.
Sent from my Nexus 6P using Tapatalk
SomeGuy4 said:
Why not just use a root explorer and go to the system folder. Remember to reboot for changes to take effect.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Just wanted to do it without an app, that's all. I didn't feel like cluttering up my phone just yet. In the end, I gave up anyways and just use an app after all. But I would still love to know if there's a way to edit text files inside of TWRP...
Pull the build prop thru adb then modify it and push it back .. No app needed