Related
I'm having very low volume even at max when listening to music with headphones. Are you experiencing the same?
I haven't had this issue.
what music app are you using? try the stock app with SRS WOWHD in equalizer.
simplistian said:
what music app are you using? try the stock app with SRS WOWHD in equalizer.
Click to expand...
Click to collapse
is the stock app called "Music"?
i couldnt find a setting with equalizer.. in fact i couldnt find any settings in this app..
iamelton said:
is the stock app called "Music"?
i couldnt find a setting with equalizer.. in fact i couldnt find any settings in this app..
Click to expand...
Click to collapse
try to play a song first, then hit the menu button, you won't see the settings in playlists.
simplistian said:
try to play a song first, then hit the menu button, you won't see the settings in playlists.
Click to expand...
Click to collapse
got it.. thx!
iamelton said:
got it.. thx!
Click to expand...
Click to collapse
No luck for me. I have installed the Honeycomb Music app and removed the Froyo app. This one doesn't have much at all in settings. Anyone else?
Also my loud speaker and phone speaker are simply not loud enough. Any noise at all nearby and I cannot hear the caller talking. Do you think there will be fixes for this?
GolfCranK said:
No luck for me. I have installed the Honeycomb Music app and removed the Froyo app. This one doesn't have much at all in settings. Anyone else?
Also my loud speaker and phone speaker are simply not loud enough. Any noise at all nearby and I cannot hear the caller talking. Do you think there will be fixes for this?
Click to expand...
Click to collapse
I suggest to get the stock Music app back, your will be surprised by the SRS WOWHD equalizer with a good earplug
Try experimenting with the values in /system/etc/hwVolumeFactor.cfg. I haven't tried modifying this as I don't have an issue but I'm sure it's what you're looking for. It only has values for wired headset and speaker though, so whether speaker is both earpiece and loudspeaker or just loudspeaker I don't know. Give it a go and post your results.
@stockwell
You are right.
You have to increase the value "wired_headset". I changed mine from 60 to 70 and now it works prefectly with my on-ear headset. A bit too loud at max though.
If you need assistance feel free to ask ;-)
@AliWam- Please give instructions. Will be appreciated.
Hi !
Do i need to root my phone to change the value to 65 or above?
I cant save the changes because the mapp is write protected
Hey,
I'm sorry for the late reply, quite busy these days.
I take no responsibility for any harm that comes to your phone as a result of applying this mod.
1. You need a rooted device (e.g. z4root), Busybox[1] installed and a text editor (e.g. Text Editor from Market).
2. Open /system/etc/hwVolumeFactor.cfg in the text editor, replace the value(s) as you like and save it as a new file e.g. /mnt/sdcard/myVol.cfg. The file might look like this:
Code:
speaker=80
wired_headset=70
3. Remount the related partition writeable:
Code:
mount -o remount,rw /dev/block/mmcblk0p12 /system
4. Copy your new file and replace the old system file:
Code:
cp /mnt/sdcard/myVol.cfg /system/etc/hwVolumeFactor.cfg
5. Reboot your phone and then the new values should be applied.
------
[1]I'm not sure if you really need Busybox installed for these steps.
no sdk
To change the volume without the SDK (not use console command).
- install on your computer AndroidCommander
- in the phone menu choose the "applications / developer / debugging usb"
- connect phone to a PC
- run AndroidCommander on your computer.
- find / system / etc / hwVolumeFactor.cfg in AndroidCommander (right panel is a telephone system files)
- copy the file "VolumeFactor.cfg" to your computer and change values
- in the left window AndroidCommander find the edited file and move (copy) to "/ system / etc / hwVolumeFactor.cfg" on the window phone.
- disconnect the phone and restart
In this way you can change other files, but be careful .
Guys, i try all this even tho my phone is rooted when i paste my new file says its read only and when i try at android commander it says not rooted even tho it is i checked with root checker !!
any ideas ?
ektorgre said:
Guys, i try all this even tho my phone is rooted when i paste my new file says its read only and when i try at android commander it says not rooted even tho it is i checked with root checker !!
any ideas ?
Click to expand...
Click to collapse
I had no success changing the values in the file / system / etc / hwVolumeFactor.cfg using "es explorer" so upon advice in another thread I bought Root Explorer in the Market and it works. Once you are in the etc folder press the Mount R/W button and then you can edit the .cfg file by longpressing on it. It will auto create a backup. I increased my values to 99 and 70.
I also found from a poster here that the stock music player has an equalizer that you only see once you select a track to play. The default setting is very quiet but the SRS WOWHD is much better. Happy listening
Sorry for my silliness in advance guys. I can't make Android Commander work. It says "device not found". Have any ideas on what I'm doing wrong?
Alexcxvtr said:
Sorry for my silliness in advance guys. I can't make Android Commander work. It says "device not found". Have any ideas on what I'm doing wrong?
Click to expand...
Click to collapse
Make sure you have debugging enabled on the phone:
Go to settings > applications > development
Then enable USB debugging.
Poulsen8r said:
Make sure you have debugging enabled on the phone:
Go to settings > applications > development
Then enable USB debugging.
Click to expand...
Click to collapse
Thanks for the quick response. I do have usb debugging enabled. I can't figure out what I'm doing wrong whatsoever. Any other ideas?
Computer:
Is the SDK installed and did you set your path variables?
Have you installed the ADB driver for the phone?
Phone:
Do you have busybox?
Root?
Hi,
I have TyphooN_CM7_v3.7.0-MAGLDR Android (2.3.7) on NAND since a few months now, no complaints except for one small thing which is a bit irritating. The G-Sensor is a bit off by a few degrees, vertically and horizontally.
There are a couple of posts on the forum (http://forum.xda-developers.com/showthread.php?t=803242) and (http://forum.xda-developers.com/showthread.php?t=979879) which mention that altering the file AK8973Prms.txt in folder /data/misc should be the remedy. However, I found that the values within the file on my system are completely different, here's what I mean:
AK8973prms.txt on my phone:
Code:
[AK8973]
HDOE_STATUS=2
HDOE_SUCTEMP=128
HDAC.x=129
HDAC.y=131
HDAC.z=133
HOFFSET.x=-767
HOFFSET.y=39
HOFFSET.z=-97
ASENSE.x=256
ASENSE.y=256
ASENSE.z=256
AOFFSET.x=0
AOFFSET.y=0
AOFFSET.z=0
Suggested Values on the thread/s:
Code:
[AK8973]
HDOE_STATUS_SLIDER_OPEN=1
HDOE_STATUS_SLIDER_CLOSE=0
HDOE_SUCTEMP=114
HDAC_SLIDER_OPEN.x=128
HDAC_SLIDER_OPEN.y=135
HDAC_SLIDER_OPEN.z=4
HOFFSET_SLIDER_OPEN.x=250
HOFFSET_SLIDER_OPEN.y=593
HOFFSET_SLIDER_OPEN.z=175
HDAC_SLIDER_CLOSE.x=0
HDAC_SLIDER_CLOSE.y=0
HDAC_SLIDER_CLOSE.z=0
HOFFSET_SLIDER_CLOSE.x=0
HOFFSET_SLIDER_CLOSE.y=0
HOFFSET_SLIDER_CLOSE.z=0
ASENSE.x=256
ASENSE.y=256
ASENSE.z=256
AOFFSET.x=0
AOFFSET.y=0
AOFFSET.z=0
I am afraid to replace the whole file. If I have to edit the values, which ones do I edit, the values are poles apart! Some suggestions please....
Jiggy
Hi I have the same problem,The orizontal line (y Axis) is a little bit out of calibration.Don t know if it s an hardware fault cause,2 days after buying my hd2 I putted android on it,but from what I can remember in windows mobile I had not this problem.For almost 1 year I used typhon cyanogenmod rom,in witch i could modify the calibration data from ak8973prms file.
You have to change only the last 3 parameters value
AOFFSET.x=0
AOFFSET.y=0
AOFFSET.z=0
Let the other untouched.For example in mine i had :
[AK8973]
HDOE_STATUS=2
HDOE_SUCTEMP=128
HDAC.x=129
HDAC.y=131
HDAC.z=133
HOFFSET.x=-767
HOFFSET.y=39
HOFFSET.z=-97
ASENSE.x=256
ASENSE.y=256
ASENSE.z=256
AOFFSET.x=10
AOFFSET.y=-20
AOFFSET.z=0
You have then to set the permission to this file to read only in some rom and restart to let the change take effect.
The problem now is:
I passed to dorimanx rom because the no more support from typhon to his great rom.In this rom I can t modify this file,everytime I restart the system the file is restored with default value,even if I change permission.I talked to dorimanx (he is a great developer and give great support to the comunity and users with his rom) and he said that I have this problem cause now the gsensor calibration is kernel related,so the kernel overwrite everytime this file.Sadly he can t change those value in his kernel or else every other user will experience a wrong calibration.
Does any other user notice a wrong calibration issue?Could be even related to an hardware revision wich is not supported completly by the kernel,same as the users wich experience a non working g-sensor under android but wich work under windows mobile.
It would be great to override this problem by developing something to calibrate the gsensor,like in sense rom settings.
Please everyone with a not working or inaccurate gsensor under android,but perfect in windoiws mobile,report the experience here.Maybe with the help of the entire comunity we can solve the problem
I hope you can understand my english
Axel85 said:
Hi I have the same problem,The orizontal line (y Axis) is a little bit out of calibration.Don t know if it s an hardware fault cause,2 days after buying my hd2 I putted android on it,but from what I can remember in windows mobile I had not this problem.For almost 1 year I used typhon cyanogenmod rom,in witch i could modify the calibration data from ak8973prms file.
You have to change only the last 3 parameters value
AOFFSET.x=0
AOFFSET.y=0
AOFFSET.z=0
Let the other untouched.For example in mine i had :
[AK8973]
HDOE_STATUS=2
HDOE_SUCTEMP=128
HDAC.x=129
HDAC.y=131
HDAC.z=133
HOFFSET.x=-767
HOFFSET.y=39
HOFFSET.z=-97
ASENSE.x=256
ASENSE.y=256
ASENSE.z=256
AOFFSET.x=10
AOFFSET.y=-20
AOFFSET.z=0
You have then to set the permission to this file to read only in some rom and restart to let the change take effect.
The problem now is:
I passed to dorimanx rom because the no more support from typhon to his great rom.In this rom I can t modify this file,everytime I restart the system the file is restored with default value,even if I change permission.I talked to dorimanx (he is a great developer and give great support to the comunity and users with his rom) and he said that I have this problem cause now the gsensor calibration is kernel related,so the kernel overwrite everytime this file.Sadly he can t change those value in his kernel or else every other user will experience a wrong calibration.
Does any other user notice a wrong calibration issue?Could be even related to an hardware revision wich is not supported completly by the kernel,same as the users wich experience a non working g-sensor under android but wich work under windows mobile.
It would be great to override this problem by developing something to calibrate the gsensor,like in sense rom settings.
Please everyone with a not working or inaccurate gsensor under android,but perfect in windoiws mobile,report the experience here.Maybe with the help of the entire comunity we can solve the problem
I hope you can understand my english
Click to expand...
Click to collapse
I too am on dorimanx kernel , and my sugestion to you would to use an init.d script to set the values of your text file upon boot . that way its set to your device specific values upon boot every time .
elesbb said:
I too am on dorimanx kernel , and my sugestion to you would to use an init.d script to set the values of your text file upon boot . that way its set to your device specific values upon boot every time .
Click to expand...
Click to collapse
Starting from the dorimanx last 4.4 kernel could you help me editing this file?Have you seen a guide in wich I can learn about this editing process?So maybe i can help some people.My idea is to creat an application wich calibrate the g sensor,like in gps status for expample,but for the whole system not only the application itself.We have an example in sense rom under the settings were you can find g-sensor calibration
Thanks for your reply.
The AOFFSET values are already set to '0' in the original file on my device. So what do I change here?
you have to change the last 3 value and test,restart and test your sensor.I used the google sky map orizontal line.To know the faulty axis i donloaded sensor debug from market,the procedyure is descripted in this thread:
http://forum.xda-developers.com/showpost.php?p=7067687&postcount=53
you have to try values,because sensor debug value is only used to see wich axis is uncalibrated.Then you can start with an high value to see if it change something and then fine tweak the whole thing
I'm using an actual level finder here... my sensor is off by approx 6.3 degrees! I'll try a few values and post back here....
This will take a lot of fine tuning... getting there..
Axel85 said:
Starting from the dorimanx last 4.4 kernel could you help me editing this file?Have you seen a guide in wich I can learn about this editing process?So maybe i can help some people.My idea is to creat an application wich calibrate the g sensor,like in gps status for expample,but for the whole system not only the application itself.We have an example in sense rom under the settings were you can find g-sensor calibration
Click to expand...
Click to collapse
Well you could have the application set the values to zero . But I think that wont "calibrate" the g sensor . It would be tough creating an application that would calibrate the g sensor since the g sensor could be different across all devices . A script placed inside the init.d folder should serve its purpose to set the device specific settings . Maybe the app could run through different settings and the user picks the best one for their device .
Sent from my HTC HD2 using Tapatalk
elesbb said:
Well you could have the application set the values to zero . But I think that wont "calibrate" the g sensor . It would be tough creating an application that would calibrate the g sensor since the g sensor could be different across all devices . A script placed inside the init.d folder should serve its purpose to set the device specific settings . Maybe the app could run through different settings and the user picks the best one for their device .
Sent from my HTC HD2 using Tapatalk
Click to expand...
Click to collapse
My idea is an app that read the axis degree with the phone on a flat surface,and set those values as the default 0 value in AK8973Prms.txt.but the problem is the fact that in new roms this calibration is integrated in kernel,and changing value to this file does not work anymore,since the file is resetted every boot.Do you know about any guide to create those scripts to pòut in int.d folder?
Axel85 said:
My idea is an app that read the axis degree with the phone on a flat surface,and set those values as the default 0 value in AK8973Prms.txt.but the problem is the fact that in new roms this calibration is integrated in kernel,and changing value to this file does not work anymore,since the file is resetted every boot.Do you know about any guide to create those scripts to pòut in int.d folder?
Click to expand...
Click to collapse
that sounds like a good idea , and to counteract the values being reset on boot , have the program make a file in the "init.d" directory with the settings so it resets itself upon boot . for guides just google , i usually take on that already in my init.d folder and edit it to my liking .
but heres some that i found :
http://www.ehow.com/how_4924505_write-script-unix.html
http://www.hpcvl.org/sites/default/...reference.pdf?phpMyAdmin=fec4e5f8403t4839c515
https://www.google.com/#hl=en&sclie....,cf.osb&fp=e92f2272b3130b4a&biw=1144&bih=626
Axel85 said:
you have to change the last 3 value and test,restart and test your sensor.I used the google sky map orizontal line.To know the faulty axis i donloaded sensor debug from market,the procedyure is descripted in this thread:
http://forum.xda-developers.com/showpost.php?p=7067687&postcount=53
you have to try values,because sensor debug value is only used to see wich axis is uncalibrated.Then you can start with an high value to see if it change something and then fine tweak the whole thing
Click to expand...
Click to collapse
Changing the last three values greatly also did not change much, if anything at all. I then changed ALL the values to the ones mentioned here: http://forum.xda-developers.com/showpost.php?p=7067687&postcount=53
Now it seems to be ok (+/- 1 degree). I think all are related.
They should not be related...They are the three axis X Y Z.You have to restart for change to take effect everytime.When iI apllied this method I started modifying 1 axis at time.putting at first a big value as 50 or -50 and looking at the change,after many tweaks I found my calibration value
---------- Post added at 11:02 AM ---------- Previous post was at 11:00 AM ----------
elesbb said:
that sounds like a good idea , and to counteract the values being reset on boot , have the program make a file in the "init.d" directory with the settings so it resets itself upon boot . for guides just google , i usually take on that already in my init.d folder and edit it to my liking .
but heres some that i found :
http://www.ehow.com/how_4924505_write-script-unix.html
http://www.hpcvl.org/sites/default/...reference.pdf?phpMyAdmin=fec4e5f8403t4839c515
https://www.google.com/#hl=en&sclie....,cf.osb&fp=e92f2272b3130b4a&biw=1144&bih=626
Click to expand...
Click to collapse
Ok I will try if I can understand something about programming for android.I think it would be even an easy process to create a program like this,but I start from 0
Axel85 said:
They should not be related...They are the three axis X Y Z.You have to restart for change to take effect everytime.When iI apllied this method I started modifying 1 axis at time.putting at first a big value as 50 or -50 and looking at the change,after many tweaks I found my calibration value
---------- Post added at 11:02 AM ---------- Previous post was at 11:00 AM ----------
Ok I will try if I can understand something about programming for android.I think it would be even an easy process to create a program like this,but I start from 0
Click to expand...
Click to collapse
The links are only about script writing to be placed in the init.d folder . To write a full fledged android program you must write in Java .
Sent from my HTC HD2 using Tapatalk
elesbb said:
The links are only about script writing to be placed in the init.d folder . To write a full fledged android program you must write in Java .
Sent from my HTC HD2 using Tapatalk
Click to expand...
Click to collapse
i know i know
Guys, I have a nexus s 4g from sprint. The g-sensor either doesn't work or this file is wrong. I'm on gingerbread, and i'm rooted. I have es file explorer installed with all the correct root options enabled. I have ran a search for the AK8973Prms.txt file, but it doesn't seem to be there. However, if i run a search for just "ak" I get other folders such as AK8973, but nothing inside it. Should I create a file and push it to the phone or what? and if so where does the file go on the nexus s 4g?
wailer247 said:
Guys, I have a nexus s 4g from sprint. The g-sensor either doesn't work or this file is wrong. I'm on gingerbread, and i'm rooted. I have es file explorer installed with all the correct root options enabled. I have ran a search for the AK8973Prms.txt file, but it doesn't seem to be there. However, if i run a search for just "ak" I get other folders such as AK8973, but nothing inside it. Should I create a file and push it to the phone or what? and if so where does the file go on the nexus s 4g?
Click to expand...
Click to collapse
Hi,
I have recently purchased a Sony Xperia S with Android 2.3.7 (it is still unrooted), though ES explorer does display the root files. (It only displays them).
On the Xperia, there is no misc folder (or AK8973Prms.txt for that matter) in the /data/ folder. So I suppose it could be only a custom ROM file. Is yours a custom ROM or the original?
JK
Setting.apk
Copy Setting.apk from similar phone model that has g-sensor calibration and u will have it too. Setting.apk in System/app folder:victory:
For Chinese MTK6573 based phone search custom rom v3.3 by Bruno Martins and extract the file needed:victory:
Hello all,
I've been a user of SwiftDroid, SDSL, now switched to AOSP.
So, in the thread http://forum.xda-developers.com/showthread.php?p=30733440 the line "Increased Screen Backlight;" caught my attention. Can anyone please tell me if this is safe for the phone? Or how can I modify that parameter? I've tried searching through the files in the installation package for recovery, for strings like "light", "backlight", "brightness", but nothing obvious came out of those searches.
Thanks in advance for the answer.
For backlight, after setting and the config files directory at:
Code:
/sys/class/backlight/rt9393
And the files are:
actual_brightness
brightness
max_brightness
bl_power
WORK IN PROGRESS.. UNTIL NOW NOT GETTING 100%
This was for CM11s, Don't try on CM12s
As soon as we found right procedure we'll Update here
This tutorial is not for newbies.. If you are not little advance user don't do this
After reboot Values reset to Orignal setting (Reset)
need to prevent NV recovery
1. Download Files Here containing all the necessary files and extract it on desktop.
2. Enable Android Debugging on your phone and connect it to your computer,
3. Open up ADB and type the following:
Code:
adb shell
su
setprop sys.usb.config diag,adb
4. Launch Device Manager go to & expand Other Devices,
Right click Android (or something related) listed under that menu
Choose Update Driver Software,
Browse my computer for driver software,
Let me pick from a list of device drivers on my computer,
Just Click Next,
Have Disk,
Browse to where you extracted YU Diagnostics Driver folder
Inside you will find 32bit and 64bit versions, pick one as per your OS
Select htcdiag.inf (for 32bit) or HtcUsbMdmV64.inf (for 64bit) file that you will Open.
Accept all warning messages and let the installation of the driver complete.
5. Once everything is done installing, under Modems or Ports (Com & LPT) in Device Manager you will find HTC USB Modem.
Right click and select Properties; in this you will see Port: COM<number>. Remember that COM<number> or write it down.
6. Open QPST v2.7 Build 4.11 > run as administrator setup.exe (Don’t run QPST.2.7.411.msi)
7. Open QPST Configuration from Start Menu,
Go to the Ports tab,
Click on Add New Port (right bottom corner);
In the Port field type in the COM<number> you wrote down/remembered from step 5 and in Port Label type YU and finally click OK (left bottom corner).
If you've followed all the steps correctly until here, you should be able to see something like this in the Active Phones tab:
View attachment 3258366
Keep QPST Configuration window open
8. Open QXDM-3.12.714 > run as administrator setup.exe (Don’t run QXDMInstaller.msi)
9. Open QXDM Professional (run as administrator),
go to Options menu,
Select Communications
Set Target port to your phone COM<number> you wrote down/remembered from step 5 from dropdown list, Press OK.
View attachment 3258367
10. Back to QXDM main window, in the "View" drop-down menu, selects NV Browser
View attachment 3258368
now the fun part begins
View attachment 3259381
Put check mark on Dual SIM (as shown above SS) for apply all setting to both SIMs (Thanks to @tirta.agung)
11. Inside the NV Browser window,
Scroll down and click on line 01877 (rf_bc_config)
Click the Read button save original value in notepad in case something goes wrong.
Replace Input value with 3460734838925427584
Click on Write button.
12. Inside the NV Browser window,
Scroll down and click on line 00946 (band_pref_16_31);
Click the Read button, save original value in notepad in case something goes wrong.
Replace Input value with 0x0FF8 (please don't be an idiot and don't edit the empty one with "nam" in the name)
Click on Write button.
13. Inside the NV Browser window,
scroll down and click on line 02954 (band_pref_32_63);
click the Read button, save original value in notepad in case something goes wrong.
replace Input value with 805765120 (please don't be an idiot and don't edit the empty one with "nam" in the name)
click on Write button.
14. Inside the NV Browser window,
scroll down and click on line 00441 (band_pref);
click the Read button, save original value in notepad in case something goes wrong.
replace Input value with 0x380 or 0xFFFF (please don't be an idiot and don't edit the empty one with "nam" in the name)
click on Write button.
If you have problem with selection, you can edit it directly from your phone: *#*#4636#*#* /Phone information /Menu /Select radio band > Automatic
15. Inside the NV Browser window,
scroll down and click on line 06828 (lte_bc_config);
click the Read button, save original value in notepad in case something goes wrong.
replace Input value with 1904863 (please don't be an idiot and don't edit the empty one with "ext" in the name)
click on Write button.
16. Now Close QXDM; Wait 30 seconds,
disable Android Debugging on your phone,
unplug it and reboot your device;
Once it comes back on, it might take a minute or two for it to acquire signal so don't panic.
DO this on your own risk.. No body is responcible for any lost
Conclusion:
The only real way to know if the whole thing got applied is to do steps 1 through 10 again (obviously skipping installations)
and reading all values or if you are in an area where you previously had bad or no reception.
You can see unlocked GSM/UMPTS bands from the *#*#4636#*#* /Phone information /Menu /Select radio band
For more features of QXDM i.e. recover lost IMEI or ESN go HERE (Thanks to @tirta.agung)
Credits:
Thanks to @BlackSoulxxx for his original work with the Qualcomm baseband software, for the modified Drivers and for the LTE NV values
Thanks to @olokos for his original tutorial
Thanks to @devilsshadow for his original tutorial
Thanks to @Albirew for his original tutorial
Thanks to @tirta.agung for bringing the original thread to my attention & Guide me in many ways
Thanks to @fards for finding the diagnostics command that made all this possible
Thanks to @hem12 who raised my will for finding these tutorials.
Thanks to @d3athwarrior for post this tutorial.
Reserved
Don't forget to put check marks on dual sims, and apply all settings to sim0 and sim1 (see attachment). By the way before u messed things up, back up your modemst1, modemst2, fsc, and fsg.
By the way we can also use qxdm to recover lost imei, just go to 0550, and insert your imei for SIM 1 (sim0 in qxdm) and SIM 2 (sim1 in qxdm), for example:
Code:
If your IMEI was: 954091051099226, then the boxes would look like so:
8
9a
45
90
1
15
90
29
62
or also recover lost esn (item no 0 and 5597) or meid (1943 and 5598).
Great guide, guys !:good::good::good:
---------- Post added at 04:02 AM ---------- Previous post was at 03:59 AM ----------
Some error down there: "OPO" and huge load of credited people that seem dont fit in here. Clearly copied from OPO thread?
BlackSoulxxx said:
Great guide, guys !:good::good::good:
---------- Post added at 04:02 AM ---------- Previous post was at 03:59 AM ----------
Some error down there: "OPO" and huge load of credited people that seem dont fit in here. Clearly copied from OPO thread?
Click to expand...
Click to collapse
Yes you'r right.. I don't want to leave anyone in credit for them work :good:
OPO removed :Hawkeye:
but that works for me..
Need help for prevent NV recovery from you all
If it's the same as the 1+1, replacing /system/bin/rmt_storage with a version not locked would prevent nv recovery (do you know if NV values were sticking in an older version? If so, take it's rmt_storage and try to replace current one with older one, I think it's worth trying)
Albirew said:
If it's the same as the 1+1, replacing /system/bin/rmt_storage with a version not locked would prevent nv recovery (do you know if NV values were sticking in an older version? If so, take it's rmt_storage and try to replace current one with older one, I think it's worth trying)
Click to expand...
Click to collapse
Hmmm, as far as I know, all NV settings, including IMEI, or MEID, ESN, etc, resides in your modemst1 and modemst2 partition. If you don't believe me and eager to try, first make a backup of those two partitions, then format or wipe the two partition inside your phone (use fastboot to do this), I'll bet for your YU, now your IMEI and NV settings are all gone.
To be honest, I just found out from this thread that there is an rmt_storage in CM phones, wkwkwkwkw, . If the rmt_storage function is trough, then CM is locking the phone NV settings from the HLOS side not Non-HLOS side. I'll do some research on this rmt_storage.
Need Help from your side
tirta.agung said:
Don't forget to put check marks on dual sims, and apply all settings to sim0 and sim1 (see attachment). By the way before u messed things up, back up your modemst1, modemst2, fsc, and fsg.
.....
or also recover lost esn (item no 0 and 5597) or meid (1943 and 5598).
Click to expand...
Click to collapse
BlackSoulxxx said:
Great guide, guys !:good::good::good:
Some error down there: "OPO" and huge load of credited people that seem dont fit in here. Clearly copied from OPO thread?
Click to expand...
Click to collapse
Albirew said:
If it's the same as the
.....
current one with older one, I think it's worth trying)
Click to expand...
Click to collapse
Now current status is
when I connect mobile
it shows me like that
Even I change USB config to diag,adb
thru ADB or manually
this time its present in default.prop
I try both
trying to disable MTP in mobile USB connection is not working
Window for Settings > Storage > 3dot > USB computer connection is working
but when I disable MTP.. its not working3
So need help from your side..
how I enter / install diag mode
@tirta.agung
I read your complete Guide regarding unbrick YU
but as that post has multipal guides ... I little confused ..
Sorry I am Xtreme noob for all that
Can you guide me an easy way to connect with QPST for enable LTE band
Can I try
Guide #3. REVIVING YOUR IMEIs (That for 32bit or 64bit)??
for connect QXDM
ekhasti said:
@tirta.agung
I read your complete Guide regarding unbrick YU
but as that post has multipal guides ... I little confused ..
Sorry I am Xtreme noob for all that
Can you guide me an easy way to connect with QPST for enable LTE band
Can I try
Guide #3. REVIVING YOUR IMEIs (That for 32bit or 64bit)??
for connect QXDM
Click to expand...
Click to collapse
Yes use guide number three, and download the necessary file there. By the way, to use the guide you have to be in stock CM kitkat.
How to use these tools for Xperia C6602
Long story short, did it work in the end for more than 1 person?
thanks for the post. but i have a Lollipop rom. I will wait for you to update the thread ....
Can we try this in lollipop??? Is there any update on this???
ekhasti said:
WORK IN PROGRESS.. UNTIL NOW NOT GETTING 100%
CM12s
As soon as we found right procedure we'll Update here
Click to expand...
Click to collapse
Hi there, attached is boot.img and a hack rmt_storage for CM 12.1. Just flash the boot.img to your phone and connect it with QXDM. Your phone will be recognized as qualcomm diagnostic port 903A. Copy and paste (you can use TWRP's file manager to do this) the rmt_storage to "/system/bin" and change its permission (chmod) to 0755. This will make your changes stick upon reboot.
By the way, to use all these files, you need to be on stock CM 12.1. I haven't tried it on any other ROM.
Bro...im on cm12.1 ...rooted...I didn't understand the procedure... Pls can u explain step by step ..pls....wats that qxad ..? Is a software...? Wer I get that..,pls reply bro
Sent from my AO5510 using XDA Free mobile app
tirta.agung said:
Hi there, attached is boot.img and a hack rmt_storage for CM 12.1. Just flash the boot.img to your phone and connect it with QXDM. Your phone will be recognized as qualcomm diagnostic port 903A. Copy and paste (you can use TWRP's file manager to do this) the rmt_storage to "/system/bin" and change its permission (chmod) to 0755. This will make your changes stick upon reboot.
By the way, to use all these files, you need to be on stock CM 12.1. I haven't tried it on any other ROM.
Click to expand...
Click to collapse
Now i upgraded to cm13.....can these two files work for me....pls reply
Sent from my AO5510 using XDA Forums
@ekhasti
I have tried doing this on Yureka - CM11 XNPH05Q. Installed all the drivers & softwares successfully. When I startup the QPST config to add a new port,
1. I have to uncheck the "Show serial and USB/QC diag ports only" to make the HTCUSBModem port visible.
2. Although I am able to add the port successfully I am unable to see the phone number, it says "No Phone".
Since it is unable to get the phone details I am unable to proceed further. Nothing is visible/editable QXDM. either.
I have manually edited the build.prop file to make sure USB debugging is enabled but to no avail. Please check the attached files, what is it that I am missing?
P.S - I am able to get my IMEI number using *#06#
Any suggestion Guys???
bluebl0od said:
Any suggestion Guys???
Click to expand...
Click to collapse
Guys, I am eagerly waiting for your updates
Hi guys;
I found a way to enable the double tap to wake up in LineageOS and RR for the mi mix.
Here it comes:
1: Donwload the Root Explorer and the QuickEdit;
2: With Root Explorer, go to sys/bus/i2c/12-0038/wakeup-mode;
3: Open that with Quick Edit and change the value "0" to "1";
4: Save it;
5: Have fun.
This is my first post here, take easy guys. I searched here for a solution for this problem, but didn't find anything about this two roms.
Thanks if it works!
PS: The only problem is that when you reboot the system, the system automatically returns to "0", so you will have to do the whole process again every time you restart the device. Does anyone know the solution to leave this fixed by default?
I'll add that to init process in ramdisk and enable it in source again. In build 0412 it is disabled, but it seems to work anyway Thx for finding it out.
pappschlumpf said:
I'll add that to init process in ramdisk and enable it in source again. In build 0412 it is disabled, but it seems to work anyway Thx for finding it out.
Click to expand...
Click to collapse
No problem! This is a tweak that I cant live without! And, congratulations for the amazing job. The ROM is perfect to me, Im using as my daily driver. The only 2 problens that I found, is this one and the low volume in Calls. Thanks to provide this ROM, I really appreciated.
Great! Is working fine...
Hello ,
works fine , but after reboot it is back to"0"
mfg , hjf
hjfisch said:
Hello ,
works fine , but after reboot it is back to"0"
mfg , hjf
Click to expand...
Click to collapse
As I said
Couldn't i just change the value and save the file as read only? I'm kind of afraid to try it out but wouldn't that work?
Blackphantom said:
Couldn't i just change the value and save the file as read only? I'm kind of afraid to try it out but wouldn't that work?
Click to expand...
Click to collapse
Will work. Just change the value to 1, save and exit. But, every time that you reboot the device, u will need make the process again.
I understand that. My question was if i save the file as read only wouldn't that "deny" the system from changing the value even after rebooting?
Blackphantom said:
I understand that. My question was if i save the file as read only wouldn't that "deny" the system from changing the value even after rebooting?
Click to expand...
Click to collapse
Dont know. Could you try and post the result?
Blackphantom said:
I understand that. My question was if i save the file as read only wouldn't that "deny" the system from changing the value even after rebooting?
Click to expand...
Click to collapse
NO, as /sys is just a mountpoint for a virtual Filesystem (type sysfs)
So basically, everything under /sys/ is virtual, so no real Files, so no persistance after a reboot. At least not by interacting with sysfs.
This is the Linux way of making runtime live adaptations of certain hardware or software features.
Let me give you an example.
On a regular Dektop-Linux, if you do:
>> echo "1" > /sys/block/sda/device/delete
on the command line, you tell the kernel to flush the caches of the sda disk and spin it down. (so you could safely hotswap)
and if you do not replace your disk, but now want to get that disk spinning again, you put:
>> echo "0 0 0" > /sys/bus/scsi/devices/host1/scsi_host/host1/scan
into console.
So some of the Files there are read only (in like nothing happens when you change the content) , and others can be tampered with, but every change is gone after reboot.
except when you can manage to let some startup-skript make those changes, or you can edit the kernel-source default initialisation variables.
rootgremlin said:
NO, as /sys is just a mountpoint for a virtual Filesystem (type sysfs)
So basically, everything under /sys/ is virtual, so no real Files, so no persistance after a reboot. At least not by interacting with sysfs.
This is the Linux way of making runtime live adaptations of certain hardware or software features.
Let me give you an example.
On a regular Dektop-Linux, if you do:
>> echo "1" > /sys/block/sda/device/delete
on the command line, you tell the kernel to flush the caches of the sda disk and spin it down. (so you could safely hotswap)
and if you do not replace your disk, but now want to get that disk spinning again, you put:
>> echo "0 0 0" > /sys/bus/scsi/devices/host1/scsi_host/host1/scan
into console.
So some of the Files there are read only (in like nothing happens when you change the content) , and others can be tampered with, but every change is gone after reboot.
except when you can manage to let some startup-skript make those changes, or you can edit the kernel-source default initialisation variables.
Click to expand...
Click to collapse
Yeah that makes sense. I tried it and realized that it was set back to zero every time i restarted so i figured it would be something like that. Luckily DT2W works now in the build so we don't have to do that anymore.
Thanks for the explanation though. Really appreciated.
Hey there
i followed your steps but i cant seem to find the 12-0038 folder after i2c. Any thoughts?
If you're using Lineage just install the DragonXiaKernel. Double Tap To Wake is working fine.
Tiago A said:
Hi guys;
I found a way to enable the double tap to wake up in LineageOS and RR for the mi mix.
Here it comes:
1: Donwload the Root Explorer and the QuickEdit;
2: With Root Explorer, go to sys/bus/i2c/12-0038/wakeup-mode;
3: Open that with Quick Edit and change the value "0" to "1";
4: Save it;
5: Have fun.
This is my first post here, take easy guys. I searched here for a solution for this problem, but didn't find anything about this two roms.
Thanks if it works!
PS: The only problem is that when you reboot the system, the system automatically returns to "0", so you will have to do the whole process again every time you restart the device. Does anyone know the solution to leave this fixed by default?
Click to expand...
Click to collapse
I installed "lineage-14.1-20170415-UNOFFICIAL-X3". I only get path till sys/bus/i2c/
There is no 12-0038/ folder. Can you help me out on this? I need it badly.
same here, no 12-0038
running smooth with 14.1-20170725-NIGHTLY-hammerhead though
Same for me on 14.1 LG g4 can't t find the file
Ls .../i2c/devices/
0-0006
0-a004
0-a006
1-0051
10-0048
11-003b
...
There iz no 12-0038 in both /i2c/ and /i2c/devices/
:crying:
Vipxpert said:
Ls .../i2c/devices/
0-0006
0-a004
0-a006
1-0051
10-0048
11-003b
...
There iz no 12-0038 in both /i2c/ and /i2c/devices/
:crying:
Click to expand...
Click to collapse
DT2W is working in RR (Oreo) just fine and I assume it's the same for Lineage 15.1 (Oreo). Which ROM are you using?
gavin19 said:
DT2W is working in RR (Oreo) just fine and I assume it's the same for Lineage 15.1 (Oreo). Which ROM are you using?
Click to expand...
Click to collapse
RR oreo as u said !