Related
hey everyone!
Alrighty i have been following the massive msm7k overclock thread and i have found a way to overclock stable to a 691 mhz with going to sleep and receive phone calls with no SOD.
I cant take all the credit for this because of it not being made by me sooo thanks to nettrip, mort (mortscrip), and RoboWang (throttling creator).
So if you think your Imagio needs a little kick start! This is your solution! USE AT OWN RISK (NOT ALL DEVICES WILL BE ABLE TO REACH ALL SPEEDS) USE AT YOUR OWN RISK AGAIN!
First off you must know how to regedit, create shortcuts, and navigate through file structures.
Download mort Script cab for you device. (google mortscript ( its the .de site) - download the zip for pcc)
Install it on your imagio
Download the v2 msm7kcupspeed from nettrip's thread here on xda and install. do not change any speed values in the program. You will use this to check that the OC is working and the scripts are installed correctly.
OKay here is the tricky part.... SO PAY ATTENTION!!!
Open your regedit (total commander is a good one) and your going to locate where your DispOn Registry is. Two locations to check. CHECK where it is or youll be doing all this work for nothinnnn!!
reg_root_bkl = "HKCU" <--------
reg_key_bkl = "ControlPanel\BackLight"
reg_val_bkl = "DispOn"
or
reg_root_bkl = "HKLM" <--------
reg_key_bkl = "Drivers\Display"
reg_val_bkl = "DispOn"
The rom i am using has it located at HKLU/ControlPanel/Backlight
Once you find your location download the correct file.
IF YOUR LOACTION IS HKLU then grab CSA_U.mscr
IF YOU LOCATION IS HKLM then grab CSA_M.mscr
Copy this file to your storage card. It is neccesary to put it on the storage card because if you clock too high you can just take out the SD card and run at normal speeds till you made corrections to the file.
You MUST know the location of DispOn to use the scripts. You must manually check.
Using your device file manager (activesync), create a shortcut for the .mscr file (rightclick on it and create short-cut). Then just copy the shortcut file to your device Window/Startup directory.
Then just reset and hopefully, you are good to go. One file, Auto OC.
You can use the MSM7 OC app to check the OC, but be sure to exit from it or you will get an error when the phone awakes.
Now for the OC settings.
This script has these settings in them for safety reasons. Not ALL cpus will overclock above the settings in them, but MOST will at least OC to these values.
values set are
start_speed = 37 710
boost_speed = 36 691
safe_speed = 31 604
These are the values that i am currently using... Feel free to change these values to accommodate your device max speeds. Always keep the safe speed at 31!!!! or you will get SOD's
Goodluck!
i hope this helps out my fellow imagio lovers!!! Its like i bought a new device yesterday! This phone is perfect!
Over Clock
Hey,
I live Va also, could I meet you somewhere in Richmond and have to do this to my Imagio?
Just wanted to say, worked like a charm, no problems, took a little googling outside of what is said here, but that is with never messing with my phone, all this takes is a little bit of common sense, thank you very much!
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
Good Evening Friends,
After a lot of research and reading various sites I seem to have found a solution to the proximity sensor issue with HD2 while using Windows 7 or 7.8.
Changing the dword from 0 to 1 did not work cos restarting the phone reset it back to 0 enabling the proximity sensor and turning screen off during calls without being able to get it back without restarting.
However by following the steps below one can restore the screen back during a call without disconnecting and waking up the screen for using the options onscreen and thus solve it once and for all cos restarting does not reset these values.
1. Install Lang HD2 Pdaimatejam Rom Wp7.8 OS 7.10.8858.136 RMT v8.6. Its a good rom and internet works on it unlike RMT8.7 wherein many are facing issues with internet. Moreover this rom is stable as i have myself tested it for 2 days now.
2. Install WP7 root tools from the following link http://www.wp7roottools.com/index.php/downloads
3. Grant/Enable root access in the root manager software which comes preinstalled as part of the rom.
4. Open WP7Root Tools and Click on HKEY LOCAL MACHINE
5. Click on Drivers---> Built In---> Proximity
6. Rename senscmdd.dll to senscmdd.dll2 by adding a 2 at the end.
7. Rename sensorpdd_htc.dll to sensorpdd_htc.dll2 by adding a 2 at the end.
8. Change ScreenOffThreshold valuedata by selecting it to 1000000
9. Now after saving the above exit wp7 root tools and reboot.
10. Once you have rebooted during a call you can press the red end call button without disconnecting the call and get the onscreen options without any trouble.
Hope this helps. Valuable feedback is welcome. You could thank me if this worked for you.
CHEERS...
WARNING:
This update zip use write mot_boot_mode as shell script to run bootmenu,
don't modify it. otherwise, maybe you will get stop at M logo.
NOTICE: This update zip is ONLY for mb511, if you want to update, please check your stock rom.
If you use this update zip at charm(mb502), is unstable, mb502 and mb511 still has some different.
My STOCK ROM VERSION:
Code:
RUTEM_U3_01.14.16_DEBLUR_SIGNED_USARUTH15ND0RTINT056.0R_PDS000_USARUTHEHKTWEMARA_P011_A010_HWp3_1FF.sbf
If you try to call, but can't hear sound or can't registration of the carrier network, try this ROM version to update RC version.
RC version 5: v0.7.4
configure sources
NOTICE:If you want update fix zip, you should use bootmenu to update.When boot at motologo,click click and click "vol -" to enter bootmenu.
->because bootmenu executed by mot_boot_mode, so /system can't umount, only can remount.
--and update zip have to modify updater-script, remount /system.
[2013/11/13]:
last update:
Seems we can use the command of telnetd to do emergency rescue.
I write telnetd as shell script. It's only to execute bootmenu, if someone modify mot_boot_mode maybe cause bootmenu can't execute.
The telnetd will execute by eclair's init_mapphone30_umts.rc. But it's only can use bootmenu to execute adb to do some things (ex. modify mot_boot_mode).
These days, I try using 2ndboot, but still freeze on hbootmod, I don't know why we can't execute hbootmod.
I can't find anything solution, and can't get more message.
For me, it's hard to debug, I'm not kernel developer. I try to understand the source code of hbootmod, should stuck on do_branch.
But I still can't get any idea to solve this question.
Hope someone can complete it, let we can use new kernel.
RC version 5 should can be a stable version.
[2013/10/04]:
RC version 5:
Seems when I try fix camera, has incorrect modify of sensors. Fix incorrect modify.
write shell script /etc/init.d/07cphostapconf, copy /system/etc/wifi/softap/hostapd.conf to /data/misc/wifi/hostapd.conf
modify updater-script, clear /data/dalvik-cache. if already upgraded previous version update zip, should can direct flash RC5, skip double wipe.
[2013/09/26]:
20130926.zip:
I forget modify configure sources of buttonblink.sh.
old buttonblink.sh file will get bad battery life.
[2013/09/19]:
20130919.zip:
According to this, use smartass is more stable, thanks edgarsongla.
modify init.mapphone30_umts.rc, set smartass as default and delete cpufreq_interactive.ko.
[2013/09/18]:
for traditional chinese user:
fork tcime unofficial for flipout.
upload tcime.apk for flipout.
source code
[2013/09/16]:
baseband:
use and modify cyanogenmod4milestone's configure files of mmparts.
but I'm not do full test, should be ok.
reduce reboot times:
seems wakelock cause reboot, I guess.
these steps maybe can reduce reboot times.
disable wi-fi or don't set wi-fi sleep policy at never.
disable Android debugging.
but maybe still has reboot problem. I can't find solution.
[2013/08/28]:
camera:
use and modify CyanogenKobe's configure of libcamera.
fix part of camera. Take picture is normal, solved rotation 90 degree problem. But video recorder still rotation 90 degree.
wifi:
use stock rom's files.
media:
add libraries of 720p files. but 720p still has problem.
[2013/08/15]:
fix part of magnetic sensor, tested by google map.
modify lights code. when enter standby to check notification, if exist set buttons backlight on.
and if already standby when get notification, set blink and backlight on.
delete /system/etc/init.d/99buttonblink, modify /system/xbin/buttonblink.sh(for enter standby and exist notification use).
[2013/08/08]:
seems write to Android services will get bad use of battery.
so write to /system/etc/init.d/99buttonblink, to start service (check blinking of buttons backlight).
[2013/08/01]:
fix notification blinking of buttons(menu, home and back) backlight.
[2013/07/03]:
find the way to compile tiap_drv.ko
-->if get error, try this command then reboot.
Code:
cp /system/etc/wifi/softap/hostapd.conf /data/misc/wifi/hostapd.conf
modify overlay of auto brightness and notification LED.
[2013/06/26]:
use CyanogenModXT720's libaudio.so, ril should be normal.
use CyanogenModXT720's dsp directory.
get some kernel modules from CyanogenModXT720.
-->seems tiap_drv.ko can use, but still has problem, try to fix in next version.
[2013/06/23]:
define open keyboard of orientation by overlay.
modify BoardConfig.mk.
use cyanogenmod4milestone's apns-conf.xml.
use "mka bacon" to compile cm7.
separate gapps:
-->attachments gapps.zip for bootmenu use.
can work:
camera
battd
fmradio
bluetooth
gps
sensors
usb connect
audio
half work:
video
-> 720p has problem.
wifi
->I only use 2G service, so I can't test softap.
ril
->I only use 2G service, so I can't test 3G.
use mknod to replace mv /dev/xxx
[2013/04/01]:
resume original parameter in init.mapphone30_umts.rc
->symlink /dev /dev/netmux
I don't know why I deleted it...
modify /system/bootmenu/2nd-init/init.rc:
/mnt/sdcard -> /sdcard
modify void.fstab:
/mnt/sdcard -> /sdcard
delete /system/etc/init.d/02movedevice
fix sdcard mount question.
replace files by upload zip, and delete /system/etc/init.d/02movedevice. Or wait release new version.
fix in preview version 2.
In terms of audio recorder, following information may help:
Flipout uses Sample Rate '16KHz' or "22KHz" to record sound, NOT '44KHz'. This is why flipout cannot use skype >_<. If you guys are using a recorder that uses Sample Rate "44KHz" (which almost all recorders set as default Sample Rate), you have to change the setting.
No phone to test
>.<
Sorry guy I can't help
May be I can help to fix this bugs.audio,fmradio,sensors,camera,ril&wifi,look this:https://github.com/xn-Dream/android_device_motorola_sage-1,and you can pm me else.
Seems use mb508's libaudio.so can use video(low quality,landscape orientation) and audio recorder.
-- hard decoding still problem, can use some player (like mxplayer) to play with soft decoding.
-- Spirit FM will be no sound.
-- call phone number still no sound.
[2013/04/02]:recompile cm7 with mb508's libaudio.so
Now we can hear sound from the other side , but the other side can't hear what I say .
But use speaker it's no problem.
sim unlock problem
Hi, first thanks for do this ROM :good:
I install but when start now the system want to give a sim unlock code, I was use before so do u have any idea or something that i have to do to solve this problem
Sorry for my english is not my native language
Best regards
phchshow said:
Seems use mb508's libaudio.so can use video(low quality,landscape orientation) and audio recorder.
-- hard decoding still problem, can use some player (like mxplayer) to play with soft decoding.
-- Spirit FM will be no sound.
-- call phone number still no sound.
[2013/04/02]:recompile cm7 with mb508's libaudio.so
Now we can hear sound from the other side , but the other side can't hear what I say .
But use speaker it's no problem.
Click to expand...
Click to collapse
error log
about 3G
3gw.Service 7225 Mobile Network not connected - not roaming
about codec
Error TIOMX_CORE 2045 dlopen libOMX.TI.720P.Decoder.so failed because Cannot load library: load_library[1111]: Library 'libOMX.TI.720P.Decoder.so' not found
Info TI_Video_Decoder 2045 TI Video Decoder
Error OMXCodec 2045 Profile and/or level exceed the decoder's capabilities.
Error MediaPlayer 16597 error (1, -2147483648)
Error MediaPlayer 16597 Error (1,-2147483648)
Error MX.Player.Joint 16597 1st error: what=1 extra=-2147483648
Use 508 libOMX.TI.720P.Decoder.so put into system/lib
Error OMXCodec 2048 [OMX.TI.720P.Decoder] ERROR(0x80001009, 1)
I'm impressed that you finally got it working, but i have a evil kind of Bug around here!
The Play Store vanishes every Reboot, Titanium says it is Frozen and im unable to unfreeze it.
If i can i would provide a logcat in the next hours!
Anyway, awesome to finally see 2.3.7 on MB511 ^^
//EDIT: I connected the Device with the Internet, now it is working fine ^^
everything is working except that when phone reboot version is still 2.1 and nothing changed :/
adout keylayout:
unzip keylayout.zip
--init.mapphone30_umts.rc
--init_prep_keypad.sh
to /system/bootmenu/2nd-init/
chmod 0644 /system/bootmenu/2nd-init/init.mapphone30_umts.rc
chmod 0755 /system/bootmenu/2nd-init/init_prep_keypad.sh
Integrate to fix-20130413.zip.
phchshow said:
adout keylayout:
unzip keylayout.zip
--init.mapphone30_umts.rc
--init_prep_keypad.sh
to /system/bootmenu/2nd-init/
chmod 0644 /system/bootmenu/2nd-init/init.mapphone30_umts.rc
chmod 0755 /system/bootmenu/2nd-init/init_prep_keypad.sh
Click to expand...
Click to collapse
Is This QWERTZ?
Should be QWERTY.
There are two files, ruthp0-keypad.kl and ruthp1-keypad.kl.
use this command
"cat /proc/device-tree/[email protected]/[email protected]/name"
My device get ruthp1-keypad.
If you want to use QWERTZ, you can try replace ruthp0-keypad.kl, ruthp1-keypad.kl, ruthp0-keypad.kcm.bin and ruthp1-keypad.kcm.bin.
Get from QWERTZ version.
ShockBuddy said:
Is This QWERTZ?
Click to expand...
Click to collapse
Maybe can solved Turn on USB storage problem.
Integrate to fix-20130413.zip.
if replug usb, maybe has problem, use killall com.motorola.usb to reset usb.
Hi to all,
Thanks to all that are working on this rom.
Since both models are merged in the same post because the same hardware, I wonder if I can deploy this rom into a Motorola Charm, or if I got to make changes on code, I guess at least have to change some files where refers to 511 to 512, and where refers "Ruth" to "Charm".
What other changes should I do to make this model work?
Thanx for response.
Please help
Please help me, How do i do to work because i have not service,
The problem is SIM NETWOR UNLOCK PIN
Please HELP!!!!
just the key pad related files, I was unable to compile this ROM from source using charm files, I think an update file to replace keypad files with charm should do the trick.
I shall try it and let you know.
there are so many attachments here
please put them into #1
Great job, men!
netmanmac said:
Please help me, How do i do to work because i have not service,
The problem is SIM NETWOR UNLOCK PIN
Please HELP!!!!
Click to expand...
Click to collapse
I dont have the Issue and i haven't inserted any SIM Card, it should be enough to reboot without Sim Card.
If you get to Homescreen, use a Root Explorer and edit /system/build.prop, check if
Code:
keyguard.no_require_sim=xyz
is set to "false", if it isn't in there, add it!
Hope i helped :fingers-crossed:
finally installed.is the screen orientation working good?when i flip out the keyboard the screen orientation remains protrait,pretty annoying!anyway great job,never though i'd have seen cm on flipout!love this device,unlike any other