This thread is for those having proximity sensor issues with Deck's CM10 Jelly Bean builds, but may work for proximity sensor issues in general.
If you simply want to fix proximity sensor issues in Deck's CM10, please download and flash the "signed_cm10_proxfix_update.zip" in recovery.
The below is for those that would like more information on the fix, and how to apply it manually:
After doing some research, prior HTC devices have had this issue, most notably, the HTC Desire HD. From what I have seen, it boils down to improper calibration settings of the proximity sensor. This has been addressed in many XDA, Desire HD, and foreign forums. The below is inspired by those forums, and a previous proximity sensor fix posted by xda member, ClipCarl. Thank you very much CC.
To easily test the reported distance of the sensor, one can download "Proximity Sensor Finder," free from the play store.
When properly working, a "9" will be reported when nothing is in front of the sensor, and a "0" when there is an object is detected; there are no range of values reported.
There is an easy way to apply calibration settings:
In adb shell or terminal emulator, execute:
Code:
su
echo 0x0a0f 0x140b6050 > /sys/devices/virtual/optical_sensors/proximity/ps_kadc
This will immediately change the calibration of the sensor, but will not persist after reboot.
If this calibration setting makes your proximity sensor function properly, the settings can be made persistent after reboot.
You can either add a script to init.d, using the following instructions, or flash the attatched signed_cm10-proxfix-update.zip.
Create a file (named "99proximity_init" for example, without a file extension) containing the following code:
Code:
#!/system/bin/sh
echo 0x0a0f 0x140b6050 > /sys/devices/virtual/optical_sensors/proximity/ps_kadc
Using adb or a file manager with /system mounted, copy the file to "/system/etc/init.d/"
Verify permissions are set appropriately:
Code:
chown root:shell /system/etc/init.d/99proximity_init
chmod 755 /system/etc/init.d/99proximity_init
Reboot to see if the sensor is working.
Please post your experiences and findings.
But what about those strange looking calibration values? 0x0a0f and 0x140b6050
Shell uses the prefix 0x for numeric constants represented in hex.
You can use a hex calculator, such as Windows Calculator set to programmer view, to play with the values. "0x" may need to be left out of for some calculators to work properly.
Use the terminal emulator or adb method to quickly test the effects of different parameters:
Code:
su
echo 0x<param1> 0x<param2> > /sys/devices/virtual/optical_sensors/proximity/ps_kadc
The first parameter seems to be the lower thresh hold, but does not have a large impact by my testing. Increasingly larger values, +100 dec at a time, seem to give the sensor a better range to detect an object.
The second parameter seems to be the upper thresh hold, and has a large impact on the sensors calibration. Lowering this value further, by -100 dec steps, caused the sensor to not work properly. While raising the value decreased the "detection range" of the sensor.
What are your findings? Did you find something that works better?
Code:
#!/system/bin/sh
echo 0x0a0f 0x140b6050 > /sys/devices/virtual/optical_sensors/proximity/ps_kadc
The above worked perfectly for me. Thanks!
Awesome. I'm glad it worked for you!
Do I need to enter those commands or can I just flash the zip file?
Sent from my EVO using xda premium
You can just flash the zip file.
The commands are there for a more hands on approach: to see how it works; testing; and tinkering.
Galaxy Nexus?
can this work on a galaxy nexus? I need to disable the sensor... :/
I'm not sure if the sensor is affected. This was originally made for an htc desire, but I found that it works on our evo lte.
It should affect your sensor distance if you have a "/sys/devices/virtual/optical_sensors/proximity/ps_kadc" file.
Though I'm not sure how to disable it, but the values can probably be played with make the sensor always report what you want.
Worked for me! Shouldnt this been in the original development sub forum with all the cm10 roms? I probably would've discovered this a long time ago thanks!
Sent from my EVO using xda premium
The two development forums confuse me. I picked this forum because I saw the majority of Cm10 *mods* posted here. Please feel free to ask a mod to move it if you feel it would benefit the community.
I'm very glad it worked for you! I was expecting the proximity sensor issue to be more prominent, mostly because it happened to me, but it really does seem to affect a low percentage.
<-- NitemareX
Glad you posted this up Firkin!
I keep my own copy of the file on my sdcard and on my dropbox account and flash after I flash a new nightly.
This fix works great with Paranoid Android JB rom! I was trying to use another fix linked in that thread, but it wasn't working. Now I tried this and it works perfectly!
Thanks
Using Decks 10-06 build the proximity sensor works as it should.
Sent from my EVO using xda app-developers app
FrikinImpossible, thank you so much! It works for my HTC One X, too!:good::good:
I've tried countless other methods including another fix, but nothing worked.
Keep up the good work!
t.o.m. said:
Using Decks 10-06 build the proximity sensor works as it should.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
After updating my rom to deck's 10/16 irc build, I did not need to flash the proximity fix. It seems deck has fixed proximity sensor issues!
Thank you for the tip tom!
omgomgomgomgomgomg it worked. I've been avoiding making calls because of this. Thank you so much!
This thread REALLY doesn't get anywhere near as much attention as it deserves. Bumping and thanking for being awesome
htc one x
FrikinImpossible said:
The two development forums confuse me. I picked this forum because I saw the majority of Cm10 *mods* posted here. Please feel free to ask a mod to move it if you feel it would benefit the community.
I'm very glad it worked for you! I was expecting the proximity sensor issue to be more prominent, mostly because it happened to me, but it really does seem to affect a low percentage.
Click to expand...
Click to collapse
great :good: work on htc one x running viperx rom,,thanks
The script via terminal works great on my HOX with ARHD 18.
I try to put the script in system/.. to be able to keep the script active after reboot, but that doesn't work... After every reboot i need to put the code in a terminal screen... Not really handy, but very thankfull i have a working P-sensor at least...
::steven:: said:
The script via terminal works great on my HOX with ARHD 18.
I try to put the script in system/.. to be able to keep the script active after reboot, but that doesn't work... After every reboot i need to put the code in a terminal screen... Not really handy, but very thankfull i have a working P-sensor at least...
Click to expand...
Click to collapse
To help me better understand your situation:
Did you try using the update.zip in the first post, or did you manually create the script, move it to the proper directory, then set permissions?
You may want to try the update.zip.
Does your Rom support init.d and have the "system/etc/init.d" directory already created for you?
Some developers create a Rom specific init.d directory.
Are you getting errors copying the script into the "system/etc/init.d" directory or setting the permissions? Sometimes, file explorers are finicky when messing with root and system partitions.
The proper permissions are really important!
Related
Symptom: With the new evo based kernels there is too much mic gain and the remote party you are calling hears too much background noise and complains they can't understand you, or they think you are outside in a noisy place while you are indoors in a reasonably quiet place.
The fix is to use rootexplorer or similar file manager to rename default.acdb file in /system/etc/firmware (rename to any name you want, you can always rename it back) then reboot.
- Don't do this if you have a nexus one based kernel.
- BEWARE, if you rename default.acdb file you may start getting robo voice, depending on your winmo rom.
Renaming the file is all that is needed if you don't get robot voice.
If you get robo voice you need to change your winmo rom that has intentially older oem drivers (even if it is new base)
VBN Roms newest version works fine.
http://forum.xda-developers.com/showthread.php?t=776971
Energy roms are also fine.
Miri's newest rom doesn't work. (has robo voice) (Keep in mind that this rom does not have robo voice with the default.acdb untouched)
If you have another winmo rom that doesn't have robo voice please post and I will add it here. Don't forget radio version please.
Please test and provide feedback about winmo roms, call quality and robo voice.
IF YOU WANT TO TEST BY YOURSELF call another phone that you hold on your ear and put hd2 on a table or something. And tap your nails to a hard surface within 1 meter range. You will hear a lot of banging as if it is not your nails but a hammer. Then rename the defaut.acdb file and reboot. Test again and you will see the background noise (mic gain) is lowered to winmo levels and your nails sound like nails! And of course when you talk to
someone they will understand you clearly.
Credit goes to Cotulla, and a few people in htc-linux chat on netripper irc(log) and lippa from shubcraft thread.
Integrating this to android builds would be good development move.
Popular kernel info:
hastarins newer kernels, michyprimas r1 kernel, huanyus newer kernels are evo based.
michyprimas r11 is nexus one based.
if you have camera flash problems, you have an evo kernel.
EDIT: With some configurations, robo voice may only be present in first call only. And again with some configurations you may get system not responding: wait error on startup. Try: search and find new htcleo.acdb file and put it in the same folder as new kernels look for that filename.
Great post! I suspect a few have had this problem. I for one suffered this when using ANY EVO kernel. Now just to get BT working and its nearly perfect!
Great job buddy! Worked flawlessly! No more "speak slowly and NOT loudly please" comments from the people i call... I had VBN as Winmo so no robo voice...
Thanks again...
awesome
Great job! Worked perfect for me.
Kernel Help
What Kernel are you guys using? I've been trying some recent ones but they have not booted successfully. I've been using the desire Z build but I am going to give shubcraft's build another try.
what is that screen shot for?
No robo voice with leaked T-Mo 2.14 rom.
justwonder said:
what is that screen shot for?
Click to expand...
Click to collapse
Quadrant advanced benchmark. On the Desire Z build. Shubcraft was like 1400, the Z was 1897
After a full day of talking, every person I call is happy now. (They used to curse me ) No adverse effects.
i have the exact same problem weird noise and echo coming in the other end and people complaining they don't hear !! (not robo voice)
but there is no "firmware" folder all i got is "PPP" folder and a file named "AudioBTID"
i already searched the forum for 2 days and couldn't find a solution ..
tried several radios and several WM Roms with no luck i updated the kernal to the Evo latest 9th OCT and it didn't fix the problem ..
please guide me to a solution ..
D69K said:
i have the exact same problem weird noise and echo coming in the other end and people complaining they don't hear !! (not robo voice)
but there is no "firmware" folder all i got is "PPP" folder and a file named "AudioBTID"
i already searched the forum for 2 days and couldn't find a solution ..
tried several radios and several WM Roms with no luck i updated the kernal to the Evo latest 9th OCT and it didn't fix the problem ..
please guide me to a solution ..
Click to expand...
Click to collapse
Try:
Update your su binary through superuser app settings TWICE.
Use rootexplorer app and search the filename (default.acdb)
What is your build BTW?
updated SU binary and everytime i run root explorer it force close ..??!!
i already granted the access via superuser and it doesn't work ...
i am using "shubCRAFT" 1.5
thanks for your help
@D69K
Can you try this:
Open up terminal emulator and enter these commands:
su
chmod 777 /system
mount -o remount rw /system
and try to see with Astro file manaeger if you could now see the contents of /system/etc/firmware.
Thanks!
Mic gain problem is fixed by it. No robot voice. T-mobile 2.14 rom
But there is error report about android.pocess.media stopped, and some media player cannot open due to this... I'm using mattc 1.8 with michy's R1 EVO kernel...
Thnx
This fix. Seem to be working great.
Been about 4 days of usage now, everybody is happy.
If you get android system not responding on bootup (with some builds) just tap wait. It will work normally.
Thanks a lot
Thanks, I it works perfect.
T-MO HD2, Miris 20.0 Radio 2.11 Android 2.2.1
By the way the EVO kernel now has a good camera flash (since 10/17?), just as the Nexus kernel.
Thanks.
Hi,
I noticed that my phone having background noise issue after upgraded to the latest mdeejay desire Rom version 2.6, so I try to use the method suggested in this post to fix it but seems there are actually two default.acdb, one is in /system/etc/firmware while the other one is in /etc/firmware. I am wondering which one I should rename or I need to rename both?
I tried to rename the one in /system/etc/firmware but seems still got heavy background noise. I am with radio 2.15 also tried radio 2.14.
Thanks for help in advance.
Sent from my HTC HD2 T8585 using XDA App
I finally deleted both default.acdb and it seems like the noise reduced a lot, thanks!
I just wondering what will be affectes by deleting these files?
Sent from my HTC HD2 T8585 using XDA App
Hey Folks.
I'm just a beginner for Android, but have some expirience with several PC-Programming languages. Hopefully this is the right place for this Question?
The first thing I'd like to do sounds simple, but there is a point where I'm not able to find a solution.
The Quest:
I'd like to have 1%steps in akku-display. on my DEFY
What I' found until now:
There are 2 Files containing the Information!
/sys/devices/platform/cpcap_battery/power_supply/battery/capacity
there is a symlink to that file
/sys/class/power_supply/battery/capacity
and the file can be found on two furthermore places:
/d/battery
/sys/kernel/debug/battery
at the same locations there is a second file : charge_counter
This is also with the named other directorys.
The file "charge_counter" contains the 1%step-value for the akku-level!
The file "capacity" contains the 10%step-value which is displayed by all the Widgeds and tools
The files in /sys/devices and /sys/class can't be changed. Even with 777 they resist any write-atempt
The files in /d/battery and /sys/kernel/debug/battery CAN changed they are 666 by default.
So the idea was just to copy the content from "charge_counter" to "capacity" if "charge_counter" change its value.
at first it seems to work! Every Value I wrote to "capacity" is present with the whole System! It changes the value in every presence of "capacity" I found. Also It changes the Batt-Widgets content, the status-bar-symbol and so on.
BUT
The Problem:
Once changed the value in "capacity" the phone doesn'd update "charge_counter" any more. Also "voltage" an some other Values in that directory will stop showing the real state!
So once I copied the value it will shown fine and than never change again until reboot.
Question: HOW can I avoid stopping the Update?
Sorry for typo ... english is not the language I usaly speak
any ideas?
This should be in the development thread. Not many have their eye on this section.
Sent from my MB525 using XDA App
Sounds good... post in development. If we have 1% step values, must be a way to be show.
I think I can't ... hav not enough Posts here until now! Maybe someone else may post it?
"bitboy0, you do not have permission to access this page. This could be due to one of several reasons:"
Leave it in this forum for now. It's related to Apps from what I understand.
Also, you won't be able to post in the Dev sections until you have 10 posts
Yes, I knew that 10-posts-thing as I red the stickys
Until now I tried to solve the "problem" without Java ... just using "Tasker" and the locale-execute-plugin ...
But I think It would be more effektive to handle that using Java? ...
It makes me sad to know: here the pro's doesn't read ...
Where the pro's are I can't write.
Excellent question!
bitboy0 said:
It makes me sad to know: here the pro's doesn't read ...
Where the pro's are I can't write.
Click to expand...
Click to collapse
Here you go a new thread has been create to see if someone will take on hacking the Defy to get 1% increment
See here: http://forum.xda-developers.com/showthread.php?p=11295128
Do you think that can help ?
http://grepcode.com/file/repository...2_r1.1/com/android/server/BatteryService.java
I don't think this all is needed. I am almost sure, that it's just about editing battery stats (and maybe some others) xml's and png's in framework-res.apk. Nothing more.
edit: And maybe something in services.jar. I had it changed on X10 mini.
Battery Monitor Widget now supports Motorola Defy
Hello,
Just to let you know support for the Defy has been added in BMW (which can be download from Market).
You can follow the app thread here.
Can someone test it and let me know if it works ok, not having a Defy makes it hard for testing
By the way Defy supports need to be activated in settings / monitoring settings!
Works perfectly. Wondering if it depletes more battery.
ttld1oh1 said:
Works perfectly. Wondering if it depletes more battery.
Click to expand...
Click to collapse
Good question! As I don't have a Defy can't say... Last week I checked consumption and found it as low as 0.05% CPU consumption on both a HD2 and Samsung Galaxy S!
Yesterday test results are attached, logging and refreshing every minute, screen on with mA in notification bar and didn't start the UI, just monitoring.
Will add more test result (screen-off, etc) in the app thread
Nevertheless on the Defy, the app will get % from a file (instead of event-based) and will also compute mA estimates, so it will definitely consume a little more...
Maybe you could run some tests comparison with or without activating the support?
EDIT:
Removed any comparison with other app
Hi, I noticed that our wifi driver can be controlled via iwconfig to increase TX power. It's not too impressive change (from default 14dbm to max 15dbm), but still it's a ~25% transmission power increase considering miliwatts (25mW->32mW)
Please remember it will slightly improve your wifi connection, but also increase the power consumption!
HOWTO:
Use the file everytime you switch on the wifi (or create a relevant script):
Code:
iwconfig wlan0 txpower 15
Download: iwconfig
Cheers,
z
Welcome back pal, and get ready for a welcome warmth.
thanks man
really happy to see you here
;-)
Here you can find an app for better controlling that setting http://4pda.ru/forum/index.php?showtopic=220775. Settings are changed by tapping on a widget.
Good to see you again zdzihu!
How to configure it for tether wlan?
Welcome back Z!
Don't notice much a of a difference, but I'm sure its doing its thing.
Sent from my X10i using xda premium
Nice Work There
Sent from my SO-01C using xda premium
Nice bro. Another great discovery. Thanks.
welcome back Z, I am looking forward on the new developments you are up to I presume.
hi, sorry for asking stupid Q.
can any tell me how to open it?
just simply press on it? but it asked to open with ..(text viewer/ SQlite database viewer and so on... )
Too happy to c u bck!!! Bt did u buy an arc???
Sent from my X10i using xda premium
now z's one guy who drops in from nowhere to give amazing things....
how do you know such minute details of the phone??? lol
thanks lot....
n any new development????
To use this script, execute it from the terminal. Copy it to anywhere into your memory card. Open up Terminal Emulator, cd to /sdcard/location/of/the/file/ (e.g. /sdcard/download) and enter the command from the first post.
Here's a simple script that might work. I haven't tested it yet:
Code:
#!/system/bin/sh
/system/bin/iwconfig wlan0 txpower 15
Save as whateveryouwanttonameit.sh in anywhere you want (a folder for scripts in sdcard is recommended). You need to copy the 'iwconfig' file into /system/bin for this to work and run this script from Script Manager or Gscript or anything that can run the script (including Terminal Emulator). If I'm not mistaken, you can create a simple widget for scripts using Script Manager.
Hope it works. Thanks zdzihu for this great find.
I'm glad to see you, Mr. Z
welcome back
The alternative suggested to Zdzihu's does not work
creage said:
Here you can find an app for better controlling that setting http://4pda.ru/forum/index.php?showtopic=220775. Settings are changed by tapping on a widget.
Click to expand...
Click to collapse
Nobody has found the widget suggested in this link as an alternative to work! English translation of the Russian thread. Its battery draining effect however persists. Take care!
@rapatu2010
well man, I'm using it quite OK, and don't experience any drains at all. It works great for me as well as for many other users. If you can't install it, then don't complain to app.
Help guys! I really dont understand how to use it. Please someone explain it specifically? It always show error on wlan tx power. The request is not permitted or something like that.. tnx!
Sent from my X10i using XDA App
when im typing /system/bin/iwconfig wlan0 txpower 15
Error for wireless request "Set Tx Power" (8B26) :
SET failed on device wlan0 ; Operation not permitted.
wannaburjer said:
when im typing /system/bin/iwconfig wlan0 txpower 15
Error for wireless request "Set Tx Power" (8B26) :
SET failed on device wlan0 ; Operation not permitted.
Click to expand...
Click to collapse
You need to be in root mode first. If you're on Terminal Emulator, you need to execute the command su first to be in root mode and you're good to go.
Well, that time has come. I feel like our ROM is stable enough that I can finally proide support for it without you guys (unintentionally) clogging up the dev thread.
If you have a question, POST IT HERE. If you want to ask about install issues, how to get into devving, or rabid toasters, POST IT HERE. I am closing off the dev thread now that this is created. If you post there without a constructive helpful comment (I will put up criteria there), you will get yelled at, beaten, and sent to slink back to your hole from whence you came.
Okay, now that that's over, I will be providing support in this thread. I am not mean, scary, nasty, or like to drown puppies for fun, despite what the impression the above may give you. I am actually a very helpful person (as most pre-existing members here will agree), and will try to help you, even if you think it's a stupid question.
One rule here: Search first!
I cannot emphasize how important this is. As I said, I am more than happy to answer questions, but for the love of god please don't post something like "wherez the ICS guyzz, I don;t see it in this thrad, this forum sukks". Please use search first before posting. Thank you, and have a nice day.
Well, have fun, and I will answer any questions you have (even if they don't directly relate to ICS).
Install instructions:
Special thanks to daniel644 for the video and his high praises of me .
Guides (thanks to goldflame for these):
Drm manager
YOU MUST HAVE ROOT IN ORDER TO DO THIS!!!!
http://forum.xda-developers.com/showthread.php?p=31201787
Run this in terminal with su permissions
Open terminal Type su Accept the superuser request Follow the code from the post One condition if you reboot you have to repeat the third line of code.
This will fix the market
Here is rooting:
Download tsparky root on your computer from here: http://forum.xda-developers.com/showthread.php?p=31067529
Extract the zip plug in your Samsung, turn on USB debugging which can be found in settings-devoloper-usb debugging and run the bat file.
For those of you like me that when you open super user it fcs, here is a guide on how to fix that:
I have rooted, super user won't open now
OK follow theses steps
1) download and install Android commander (Google it)
1a) plug in your device and make sure USB debugging is on
2) open android commander
3) on the right panel go to /system/app and delete super user.apk
4) then go to /system/xbin and delete busybox and su
5) reboot and root again
Worked for me and two other people so it should work for you.
This is a good idea ... hopefully we will see more people pop in here than the dev thread, like to see you guys progress whenever possible and not so much "I need help installing this". I read a few posts of one of your guys requesting people to PM for help but maybe this thread will alleviate that "burden"...
da1writer said:
This is a good idea ... hopefully we will see more people pop in here than the dev thread, like to see you guys progress whenever possible and not so much "I need help installing this". I read a few posts of one of your guys requesting people to PM for help but maybe this thread will alleviate that "burden"...
Click to expand...
Click to collapse
Well, answering questions is not a "burden" more than it is something not 100% relevent to our dev thread, which (unfortunately) sometimes gets us off on a tangent. This way, I can help you guys, and we can still be productive in the original thread. Even if your question isn't relevant, pop me a PM, and I will be happy to help you, as long as you have researched first (meaning not stuff like "where's the stock rom"?).
hanthesolo said:
Well, answering questions is not a "burden" more than it is something not 100% relevent to our dev thread, which (unfortunately) sometimes gets us off on a tangent. This way, I can help you guys, and we can still be productive in the original thread. Even if your question isn't relevant, pop me a PM, and I will be happy to help you, as long as you have researched first (meaning not stuff like "where's the stock rom"?).
Click to expand...
Click to collapse
This is simply a suggestion, but maybe you guys could make a skype group, if you guys don't do that already. I guess it's a good thing to post in the dev thread the little updates, but I think a skype may be more convenient.
euphoriaflow said:
This is simply a suggestion, but maybe you guys could make a skype group, if you guys don't do that already. I guess it's a good thing to post in the dev thread the little updates, but I think a skype may be more convenient.
Click to expand...
Click to collapse
Between devs yes, we use Gtalk on a daily basis, and has been invaluable in getting work done quickly. It would be interesting to use skype and/or Gtalk for support, although we would need a dedicated account for that (and we are currently locked out of our Nova Gmail account, because we forgot the password ).
Not trolling here, but just wondering. Since when did discussion become development? Shouldn't this be in general?
In our one s forums all discussion threads are in the general section.
Sent from my HTC One S using Tapatalk 2
Same at the epic 4g touch forums, but to be honest, I don't mind it being here at all. Not too late to move this over there, though.
Sent from my SPH-D710 using xda app-developers app
hanthesolo said:
Between devs yes, we use Gtalk on a daily basis, and has been invaluable in getting work done quickly. It would be interesting to use skype and/or Gtalk for support, although we would need a dedicated account for that (and we are currently locked out of our Nova Gmail account, because we forgot the password ).
Click to expand...
Click to collapse
I do have the pass (I saved them in case we forget it). Also klin, it is considered for general but can be considered like dev too (in the sense of error reporting).
klin1344 said:
Not trolling here, but just wondering. Since when did discussion become development? Shouldn't this be in general?
In our one s forums all discussion threads are in the general section.
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
This is a subsection of our development thread, and while it may be better placed in general, it is best here, as we remove the chance of people who create accounts just to complain, and we obtain easier access for users. Plus, I believe I may have an idea to put the community to work, I just need to polish it a bit more.
hanthesolo said:
Between devs yes, we use Gtalk on a daily basis, and has been invaluable in getting work done quickly. It would be interesting to use skype and/or Gtalk for support, although we would need a dedicated account for that (and we are currently locked out of our Nova Gmail account, because we forgot the password ).
Click to expand...
Click to collapse
Can't you reset it. Should be easy if you put a recovery email
Sent From My YP-G1 running ICS build 3.5
is this version (3.5) already better than the GB Roms out there? or is it better for domeone like me who likes gaming and music to stay on my current rom until HW and such things are fixed?
btw im using dream Ultra right now because my device makes weird noises when im using other roms
crancpiti said:
is this version (3.5) already better than the GB Roms out there? or is it better for domeone like me who likes gaming and music to stay on my current rom until HW and such things are fixed?
btw im using dream Ultra right now because my device makes weird noises when im using other roms
Click to expand...
Click to collapse
I would hold off, but only for a little while longer, there are a few details (market download fix and proper sdcard support) that need to be added into the next ROM build so you don't have to ADB push things or use terminal to enter code after every boot, once those issues are fixed then it should be a good daily. But, if your comfortable and know how to ADB push files and stuff like that then go for it, just remember you WILL be charging it EVERY night due to the deep sleep bug inherited from the CM7 kernel that was used as the base for our CM9 kernel.
daniel644 said:
I would hold off, but only for a little while longer, there are a few details (market download fix and proper sdcard support) that need to be added into the next ROM build so you don't have to ADB push things or use terminal to enter code after every boot, once those issues are fixed then it should be a good daily. But, if your comfortable and know how to ADB push files and stuff like that then go for it, just remember you WILL be charging it EVERY night due to the deep sleep bug inherited from the CM7 kernel that was used as the base for our CM9 kernel.
Click to expand...
Click to collapse
Is it possible to fix that deep sleep bug?
My milestones that need to be crossed for daily usage would be:
H/W Acceleration
SD Card fixed (internal and external)
Deep Sleep
Everything else either has already been added/fixed (Voodoo!!! Beats removed and optional ) or I could wait for (bluetooth, camera, gps).
You guys are doing a great job though, can't wait for the next build to see how you guys are doing.
da1writer said:
Is it possible to fix that deep sleep bug?
My milestones that need to be crossed for daily usage would be:
H/W Acceleration
SD Card fixed (internal and external)
Deep Sleep
Everything else either has already been added/fixed (Voodoo!!! Beats removed and optional ) or I could wait for (bluetooth, camera, gps).
You guys are doing a great job though, can't wait for the next build to see how you guys are doing.
Click to expand...
Click to collapse
once oisis gets his sgp 4.0, he can port a 3.0.x kernal and all these will will be fixed.
da1writer said:
Is it possible to fix that deep sleep bug?
My milestones that need to be crossed for daily usage would be:
H/W Acceleration
SD Card fixed (internal and external)
Deep Sleep
Everything else either has already been added/fixed (Voodoo!!! Beats removed and optional ) or I could wait for (bluetooth, camera, gps).
You guys are doing a great job though, can't wait for the next build to see how you guys are doing.
Click to expand...
Click to collapse
if/when Oisis gets a 3.0.x kernel up and going (after he gets his player) hopefully the deep sleep bug will be no more, since its a carry over from the CM7 base kernel and if we have a new kernel that should solve that issue, and should get us to where bluetooth, camera and H/W acceleration could all be possible aswell.
Han, while we wait for Oisis to get his player and do his magic can we get one more build that has the fixed vold.fstab to have both internal and external memory working normally without having to ADB push files to the player and the market fix (if there's an easy way to do it)?
daniel644 said:
if/when Oisis gets a 3.0.x kernel up and going (after he gets his player) hopefully the deep sleep bug will be no more, since its a carry over from the CM7 base kernel and if we have a new kernel that should solve that issue, and should get us to where bluetooth, camera and H/W acceleration could all be possible aswell.
Han, while we wait for Oisis to get his player and do his magic can we get one more build that has the fixed vold.fstab to have both internal and external memory working normally without having to ADB push files to the player and the market fix (if there's an easy way to do it)?
Click to expand...
Click to collapse
A build with a fixed vold.fstab is possible but for the market fix, this is something related to the initrd that actually needs one more line of code for it to be activated lool.
goldflame09 said:
once oisis gets his sgp 4.0, he can port a 3.0.x kernal and all these will will be fixed.
Click to expand...
Click to collapse
Hold up a sec, I'm unsure of the situation a bit here... does oisis HAVE a Samsung Galaxy 4.0?
If not, I'm willing to toss a couple Tens his way (won't mention how much here) with a stipulation. I'm talking about Amazon Credit (which I have alot of) here... An Amazon gift card (via email) would have to be used as Amazon being the purchase website. PM me if there is an interest oisis if this is the case of you not having an actual SGP 4.0 ...
Edit: Ok, I just read that oisis actually did order one from China (?) but if it takes too long I'm still willing to help money wise if needed for any of these great 4.0 devs here developing the ICS rom
zaclimon said:
A build with a fixed vold.fstab is possible but for the market fix, this is something related to the initrd that actually needs one more line of code for it to be activated lool.
Click to expand...
Click to collapse
OK then, a build with fixed vold.fstab and a file browser like the free ES File explorer so I can sideload my apps.
daniel644 said:
OK then, a build with fixed vold.fstab and a file browser like the free ES File explorer so I can sideload my apps.
Click to expand...
Click to collapse
A file explorer? I think I will just fix the kernel so that the drmserver can work on boot. As for the vold.fstab, I cleaned all my repo so it will take a long time before I can get one, I will get it more presumably on the weekend.
zaclimon said:
A file explorer? I think I will just fix the kernel so that the drmserver can work on boot. As for the vold.fstab, I cleaned all my repo so it will take a long time before I can get one, I will get it more presumably on the weekend.
Click to expand...
Click to collapse
Yeah a file explorer (file browser) so I can access the LEGALLY obtained .apk's I've collected from the developers websites, to install them. for whatever reason there is NO file browser app in this CM9.
Since VZW and Samsung Level 2 support didn't know the answer, here is how to enable the hidden menus on the dialer screen for the Verizon GS4. Previously, there was a 'master' code that enabled the hidden menus. Now it is a filesystem based check. Boo!
Due to editing /system/build.prop and /efs/carrier/HiddenMenu you MUST be rooted. Also, you must be on a stock TouchWiz-based ROM. This will not work on CM builds/etc. At a very minimum, hiddenmenu.apk must be present on your stock device for this to work, but possibly others, so beware of ROMs that remove 'bloat' APKs.
1) Add the following line* to /system/build.prop
Code:
sys.hiddenmenu.enable=1
Edit: I noticed that after I hosed build.prop, it was replaced when I loaded the default system image, so in fact, step 1 above is not necessary, at least for the Verizon variant. This means that once you do step #2 below, the changes made to /efs/carrier/HiddenMenu will persist after an Odin restore of the NoWipe Factory Image posted here. What this means is that root is only required to make the modification, and one could revert to stock afterwards with the hidden menus enabled.
2) Change the contents of /efs/carrier/HiddenMenu from OFF to ON
3) Reboot.
4) Try it out! Go to the phone dialer and enter *#06# (show MEID) as a test.
For more codes that worked on the S3 that (may) also work on the S4, see below:
http://androidforums.com/samsung-ga...unlocking-jelly-bean-service-modes-found.html
Having the hidden menus enabled is particularly useful for those who want to disable WiFi Power Saving mode -- I was having issues with an access point at work, but sadly disabling it didn't fix the problem. Otherwise, the hidden menus are useful to test your sensors/display/etc or just looking around in general. Enjoy!
For those that are NOT rooted, there is an alternative to get to SOME of these menus, but it is not a free app (currently $1.99). It's called "Sammy S Mode". Note that I am not affiliated with the developer, I just bought it to test if the menus were present before I dug deeper into finding out how to fully enable the hidden menus on my Verizon Galaxy S4. When I have time in the next day or so, I'll try to figure out how the app calls the menus, and update the post if I find a free solution for those that are not rooted.
---
* Note: I added the "sys.hiddenmenu.enable=1" line right after the "persist.cne.feature=0" one, but I don't think it matters where you add it. Just be careful editing this file. I managed to get my phone boot-looping, probably because I used notepad to edit the file and it added Windows CR/LFs to it, and had to use the NoWipe Factory Image posted here to restore my phone. The second time around I used Root Explorer's built in text editor and it worked fine.
In case anyone is curious how I figured this out, click here.
Mods: Thanks for moving this to the development section since it fits better here.
---
I wanted to compile a list of the ones that seem useful or new in general and working for me:
*#197328640# Service Mode
*#0228# BatteryStatus
*#0*# Screen/Sensor/Vibration/Touch/Speaker/LED/etc testing -- even gives out raw values for light sensor, barometer, etc in real time
*#2263 RF Band Selection
*#66336 MDM Randump Mode (defaults to OFF)
Thanks OP! Confirmed to be working on my Verizon S4. Followed your guide with the same placement in build.prop and using root explorer.
Thanks, worked great! :thumbup:
Sent from my SCH-I545 using xda app-developers app
I can't be rooted due to work MDM. I hope an alternative method is found. I hate the constant wifi notification.
dmichael said:
I can't be rooted due to work MDM. I hope an alternative method is found. I hate the constant wifi notification.
Click to expand...
Click to collapse
If you were talking about the menu on the S3 that opened "HiddenMenuWifiOffload" dialing *#6335623#, this does not work on my S4. In fact, it stopped working after a software update on the S3. There is a temporary solution that is lost on reboot. I tried it and it works for me. See link below:
http://androidcommunity.com/how-to-...i-notification-on-verizon-galaxy-s-4-20130527
For anyone that needs to get to a service menu without being rooted, here is the basic idea. You'll have to get a launcher or shortcut app that supports creating shortcuts to activities.
Code:
Intent localIntent1 = new Intent("android.intent.action.MAIN");
localIntent1.putExtra("keyString", "0011");
localIntent1.setClassName("com.sec.android.RilServiceModeApp", "com.sec.android.RilServiceModeApp.ServiceModeApp");
startActivity(localIntent1);
I'll expand later using a free app that supports doing that when I get it to work on my end. In the meantime, here's a very simple app that can serve as a template to place the values above:
http://viralpatel.net/blogs/android-install-uninstall-shortcut-example/
Edit 1: A free app can be used to create the shortcut. It is called Manual Intent Shortcuts.
Not working for me, did exactly what was posted. I even posted the line in the same place
Sent from Verizon Galaxy S4
tCizler said:
Not working for me, did exactly what was posted. I even posted the line in the same place
Sent from Verizon Galaxy S4
Click to expand...
Click to collapse
I should note that this only works if you're running a stock ROM. If you're running CM or some other non-TouchWiz ROM or missing hiddenmenu.apk this won't work. I have added this to the OP.
vacaloca said:
I should note that this only works if you're running a stock ROM. If you're running CM or some other non-TouchWiz ROM or missing hiddenmenu.apk this won't work. I have added this to the OP.
Click to expand...
Click to collapse
Yep, stock and rooted
Sent from Verizon Galaxy S4
thank you!
tCizler said:
Not working for me, did exactly what was posted. I even posted the line in the same place
Click to expand...
Click to collapse
tCizler said:
Yep, stock and rooted
Click to expand...
Click to collapse
The only thing I can think of is perhaps there is a space in the /efs/carrier/HiddenMenu file that is failing the code check. It is an exact match:
Code:
if (new File(this.HIDDENMENU_ENABLE_PATH).exists())
try
{
String str = read(this.HIDDENMENU_ENABLE_PATH);
if (str.equals("ON"))
return true;
You can also issue the command when USB debugging is set/connected to PC:
Code:
adb shell getprop sys.hiddenmenu.enable
or
Code:
getprop sys.hiddenmenu.enable
from a terminal emulator app on your phone to verify that the property is set correctly. Either command should return the value input -- 1 in this case.
I'll see if I make a recovery flashable update.zip to make it easier for everyone.
vacaloca said:
The only thing I can think of is perhaps there is a space in the /efs/carrier/HiddenMenu file that is failing the code check. It is an exact match:
Code:
if (new File(this.HIDDENMENU_ENABLE_PATH).exists())
try
{
String str = read(this.HIDDENMENU_ENABLE_PATH);
if (str.equals("ON"))
return true;
You can also issue the command when USB debugging is set/connected to PC:
Code:
adb shell getprop sys.hiddenmenu.enable
or
Code:
getprop sys.hiddenmenu.enable
from a terminal emulator app on your phone to verify that the property is set correctly. Either command should return the value input -- 1 in this case.
I'll see if I make a recovery flashable update.zip to make it easier for everyone.
Click to expand...
Click to collapse
I ran the "getprop sys.hiddenmenu.enable" line in terminal emulator and it came back with a value of "1".
Also, if it's any help, the *#06# code works. A few others work too. Just can't get the hidden menu *#26337# (*#codes#)
Sent from Verizon Galaxy S4
tCizler said:
I ran the "getprop sys.hiddenmenu.enable" line in terminal emulator and it came back with a value of "1".
Also, if it's any help, the *#06# code works. A few others work too. Just can't get the hidden menu *#26337# (*#codes#)
Sent from Verizon Galaxy S4
Click to expand...
Click to collapse
Oh, duh, haha. That's my fault. That was just an example of the format of the codes. There is no *#CODES# menu. :facepalm: I removed that from the OP. Sorry for the confusion, and thanks for testing/helping me clarify my post
The Service Mode Main Menu code is: *#197328640#.
vacaloca said:
Oh, duh, haha. That's my fault. That was just an example of the format of the codes. There is no *#CODES# menu. :facepalm: I removed that from the OP. Sorry for the confusion.
The Service Mode Main Menu code is: *#197328640#.
Click to expand...
Click to collapse
Hahahahaha! Wow now I feel like an ass! The facepalm should be for me
Sent from Verizon Galaxy S4
awesome!!!
vacaloca said:
The Service Mode Main Menu code is: *#197328640#.
Click to expand...
Click to collapse
Working for me.
Interesting choice of code sequence. 1973, 286 (intel), 40 (your age this year if born in 73)
Sent from my SGS4 using one opposable thumb.
ProfEngr said:
Working for me.
Interesting choice of code sequence. 1973, 286 (intel), 40 (your age this year if born in 73)
Sent from my SGS4 using one opposable thumb.
Click to expand...
Click to collapse
Ha, That sure it makes it easy to remember now
Can anyone else share their service mode setting (*#197328640#) under sim information, check nv, band pref? Mine says unexpected value.
Trying to figure out if my sim is borked and causing 4g slowness.
Sent from my SCH-I545 using xda premium
crookedview said:
Can anyone else share their service mode setting (*#197328640#) under sim information, check nv, band pref? Mine says unexpected value.
Trying to figure out if my sim is borked and causing 4g slowness.
Sent from my SCH-I545 using xda premium
Click to expand...
Click to collapse
Mine says the same and no 4g issues here either. If you have another phone handy that you can swap sims, that would be one way to test. *#2263 has band preference settings, but I haven't touched mine and don't plan to just in case, want to avoid resetting to stock and re-rooting/going back to recovery if the phone doesn't like some setting I picked there.
vacaloca said:
Mine says the same. If you have another phone handy that you can swap sims, that would be one way to test. *#2263 has band preference settings, but I haven't touched mine and don't plan to just in case, haha.
Click to expand...
Click to collapse
Mine says the same, and I have no 4g issues
Sent from Verizon Galaxy S4