Database Users

CM7 Lockscreen Mods

Alright. Now that Cyanogenmod has fixed the android.git.kernel.org sync errors, I have continued my CM7 Development (lockscreen stuff for now).
There are currently four new features:
1) Changeable pattern lockscreen size (3x3 - 5x5).
2) Visible dot toggle, for pattern unlock screen.
3) Custom lockscreen message (on normal and keyguard ones).
4) Carrier name change. NOT MINE anymore. Thanks Frederic Van Assche
After I get these problems fixed and setting for all of the features, I will release the mods here, and hopefully into official CM7.
Now for some pictures. See attached (untill i upload). Note: all images are at 180 lcd density (sortof needed for 5x5)
---------- Post added at 01:28 PM ---------- Previous post was at 01:10 PM ----------
Development Section
Im currently really busy with school, so most of the work will be done on the weekends.
Current development status, and todo list.
1) The lockscreen size mod works fine. Few small code cleanup things and stuff needed.
2) The visible dot toggle has a setting and works perfect. The checkbox sometimes doesn't display right so you may have to click it twice to turn it on/off (not sure whats wrong, low priority).
3) Custom lockscreen message works great. Sometimes you have to enable+disable it for it to update (work on auto do/fix). And I haven't added it to the PIN lock and stuff (have to check). In the end I would like the enable/disable and message to be on a different settings screen (like on Honeycomb).
4) And the carrier name thing is now obsolete. Thanks to the patch by Frederic Van Assche, shown to me by one_love_420.
Ohh. And if any of you have any suggestions on things to add or change, i'm happy to listen and try.
Beta Testing.
Current Bugs
Code:
1. Choose pattern size, press back, doesn't revert size (ex: unlock problem from 5x5->3x3)
2. Change lock pattern size. Can't unlock from the actual lockscreen, in settings its fine. (IMPORTANT!)
Fixed by rebooting. Changing to same size is fine
Notes
These builds are buggy. Use at your own risk.
If you cannot unlock your phone, you can fail 5 times and then log in with your google account.
Downloads
http://androtransfer.com/development/smasher816/cm7 beta/

For a better way to do the custom carrier text and to have it in the settings as an option check this over at the gerrit. I have used since he posted it for review and it works great.
http://review.cyanogenmod.com/#change,7314
And
http://review.cyanogenmod.com/#change,7313
Sent from my PG06100 using Tapatalk

Thanks man.
I'm assuming I would run the patch command (git fetch http://review.cyanogenmod.com/p/CyanogenMod/android_frameworks_base refs/changes/14/7314/2 && git format-patch -1 --stdout FETCH_HEAD)
Edit: that seemed to do nothing but output the changes.
I did the checkout one ("git fetch http://review.cyanogenmod.com/p/CyanogenMod/android_frameworks_base refs/changes/14/7314/2 && git checkout FETCH_HEAD") and now it says
Code:
~/android/system/packages/apps/CMParts$ git fetch http://review.cyanogenmod.com/p/CyanogenMod/android_packages_apps_CMParts refs/changes/13/7313/3 && git checkout FETCH_HEAD
From http://review.cyanogenmod.com/p/CyanogenMod/android_packages_apps_CMParts
* branch refs/changes/13/7313/3 -> FETCH_HEAD
Note: checking out 'FETCH_HEAD'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:
git checkout -b new_branch_name
HEAD is now at 5ed9b01... Custom carrier label (2/2)
Sorry, i'm still pretty new at git. What do I do now?

I'm new to the git and I do it probably the more difficult way but it gets the job done. What I do is download each change one by one, use "meld" to compare my java/xml files and add the new edits in. Like I said the more difficult way to do it.
Sent from my PG06100 using Tapatalk

Smasher816 said:
Alright. Now that Cyanogenmod has fixed the android.git.kernel.org sync errors, I have continued my CM7 Development (lockscreen stuff for now).
There are currently four new features:
1) Changeable pattern lockscreen size (3x3 - 5x5).
2) Visible dot toggle, for pattern unlock screen.
3) Custom lockscreen message (on normal and keyguard ones).
4) Carrier name change. No setting yet.
After I get these problems fixed and setting for all of the features, I will release the mods here, and hopefully into official CM7.
Now for some pictures. See attached (untill i upload). Note: all images are at 180 lcd density (sortof needed for 5x5)
---------- Post added at 01:28 PM ---------- Previous post was at 01:10 PM ----------
Developer Help Needed Section.
1) For the carrier name replacement I edited
Code:
String plmn = "<WHATEVER>"; //ss.getOperatorAlphaLong();
(line 587) in GsmServiceStateTracker.java. I would like to find a way to add this as a setting to CMParts but haven't looked around enough to figure out how yet. If any of you could hint me in the right way or something that would make my life easier.
2) SOLVED
Click to expand...
Click to collapse
how do we change our pattern size???

maxib123 said:
how do we change our pattern size???
Click to expand...
Click to collapse
If you read, he's developing it. Hence, you can't get it as of this moment.

sixstringsg said:
If you read, he's developing it. Hence, you can't get it as of this moment.
Click to expand...
Click to collapse
sorry, it wasnt that clear first time i read it

If you want a tester btw, you know where to find me

Thanks dude. I was out of town this weekend but started work on getting the pattern size setting more formal and correct.
However my Ubuntu vm decided to not boot.
Edit: fixed it with commands in slax, then in some terminal on ubuntu reboot.
However everything seems to be only. And I can't change the folders permissions due to read only filesystem. Any ideas?
e2fsck /dev/sda2 from root recovery seems to say it was fixed. but continues to not boot, and allowing me to run that command again and again.
If this doesn't get fixed soon. I think I'm gone to attempt to get my edited files from the read only (but bootable) snapshot, and add them back into the last working snapshot.

Smasher816 said:
Thanks dude. I was out of town this weekend but started work on getting the pattern size setting more formal and correct.
However my Ubuntu vm decided to not boot.
Edit: fixed it with commands in slax, then in some terminal on ubuntu reboot.
However everything seems to be only. And I can't change the folders permissions due to read only filesystem. Any ideas?
e2fsck /dev/sda2 from root recovery seems to say it was fixed. but continues to not boot, and allowing me to run that command again and again.
If this doesn't get fixed soon. I think I'm gone to attempt to get my edited files from the read only (but bootable) snapshot, and add them back into the last working snapshot.
Click to expand...
Click to collapse
have you tried chmod 777? if im on the right page, that should work. if not i have no idea mate, sorry

Smasher816 said:
Thanks dude. I was out of town this weekend but started work on getting the pattern size setting more formal and correct.
However my Ubuntu vm decided to not boot.
Edit: fixed it with commands in slax, then in some terminal on ubuntu reboot.
However everything seems to be only. And I can't change the folders permissions due to read only filesystem. Any ideas?
e2fsck /dev/sda2 from root recovery seems to say it was fixed. but continues to not boot, and allowing me to run that command again and again.
If this doesn't get fixed soon. I think I'm gone to attempt to get my edited files from the read only (but bootable) snapshot, and add them back into the last working snapshot.
Click to expand...
Click to collapse
e2fsck -A /dev/sda2
Try that

I ended up getting my read only changes and putting them on my actual computer,
then re doing my VM and melding my changes back in.
I got a backup, and a build made.
However settings crashes (doesn't look like my edits). I will attempt to fix it. Worst comes to worse go back to the good build and merge piece by piece.
Edit: The last two weeks and weekends have been super busy, barely able to turn on my PC. Anyways I got a 4 day weekend coming up, I should hopefully have everything worked out then.

any progress yet?

maxib123 said:
any progress yet?
Click to expand...
Click to collapse
He's got most of the work done, he just needs to get it all merged and get it all up on github. He got distracted by a fun new build system for our kernel.

Edit: Disregard the old information. I now have some freetime over this weekend, the last two weeks have been crazy busy. I am slowly putting my tweaks into the latest nightly and making sure everything is working (vm redo). Anyways the newest build works! - You go to settings -> location and security -> Change Screen Lock -> Confirm saved pattern -> Choose unlock type (pattern) -> Choose pattern size (3-5) -> Draw new pattern (x2).
Where in the settings should the custom lockscreen message be? CMParts -> Lockscreen -> Widget Options -> Custom Message, or Security -> Owner Info (like honeycomb), or somewhere else?

i prefer
CMParts -> Lockscreen -> Widget Options -> Custom Message
Click to expand...
Click to collapse
what i like best about this project is
a) i`ve always wanted a 5*5 unlock pattern
b) you`re working this into the Cyanogenmod Project

Thanks.
Heres a little development update. Im working on getting the 5x5 lockscreen perfect before adding back in the lockscreen message and stuff. The actual 5x5 works fine, all my problems come from the dynamically changing size. Im trying to fix these two important bugs I have found. Hopefully I can get it solved, if not I might upload my work and see if you guys can help me out
Code:
#BUGS#
1. Choose pattern size, press back, doesn't revert size (ex: unlock problem from 5x5->3x3)
2. Change lock pattern size. Can't unlock from the actual lockscreen, in settings its fine. (IMPORTANT!)
Fixed by rebooting. Changing to same size is fine
If your willing to put up with these bugs check the OP.

Is there anyway to add this on to a current build of cyanogen nightly rather than flashing an older one?
Sent from my Nexus One using XDA App

Ummmmm. I edited frameworks/base and packages/apps/Settings
So So replace the Settings.apk and framework folder or something.

This is something,I don't mind testing out. hopefully it'll work on cm7.1
From my fist to your face, enjoy.

[Q] G-Sensor Calibration - Devs/Senior members PLEASE HELP

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:

[stop-dev][TWHK][cm7][flipout-mb511-ruth][testing] status: become stable

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

[general][Q&A][Discussions] cyanogenmod 12

Hello folks at xda
i think it's better to ask our questions that are not helping developers to make stable cm12 here,and not post spams on dev thread.
i just want to say : leave developer threads for developers.:good:
ask general questions here.so devs can focus on important things.
Download rom from this mirror link if you can't download it from mega
Also you can try Resurrection remix [Lollipop 5.0.2] [Credit : @Furrydaus]
[*]USB Charging : Ok
[*]USB ADB : Ok
[*]USB MTP : Ok
[*]Video : Ok
[*]Audio : Ok
[*]Sensors : Ok
[*]Screen rotation : Ok
[*]WLAN : Ok
[*]Wifi hotspot : seems to be working ( Fix! [credit : @MrSteve555] )
[*]GPS : Ok
[*]GSM : Ok
[*]GSM Data : (Fix! [credit : @Sylvester lobo] || or this => A comprehensive Mobile Data fix)
[*]GSM Voice : Ok ( Fix! [credit : @MrSteve555] )
[*]GSM SMS : OK
[*]Bluetooth : Ok
[*]NFC : Ok
[*]Camera : Ok
[*]FM Radio : Not work
[*]Keyboard : Ok
[*]MHL : Not tested
[*]OTG : Ok ( this post )
[*]VPN : Doesn't work
[*]...

How to install cm12 (mrsteve) on sp . by @[SIZE="5"]Dammer Martins[/SIZE]
Small tutorial for instalation of the steves build with working camera and wifi:
1-Download the ROM , ramdix fix, stock kernel and root fix
2-Open the ROM zip an push the ramdisk fiz in to system/bin folder
3-Now, put the ROM zip fixed, stock kernel and the root fix in your sdcard
4-Reboot in recovery, wipe data, cache and dalvik cache
5-Install the ROM, the stock kernel and then the root fix
6-Now reboot the system and wait the phone boot up (this take a veeery long time, trust me )
Tips: don't flash the gapps with the ROM instalation and disable the adaptive brightness to make the auto reboots stop.
Click to expand...
Click to collapse

Fix hot reboots by turning off adaptive brightness(settings->display->adaptive brightness)
Fix connectivity problem on CM12.by @noahvt
Hello,
Finally a fix has arrived for android 5.0 which will allow wi-fi data, outgoing calls, ... to work again
Steps:
1: Make sure your device is running android 5.0 by mrsteve555: http://forum.xda-developers.com/xper...8#post56946968
2: root the device by flashing this file: http://download.chainfire.eu/589/Sup...erSU-v2.16.zip
3: Reboot your device and open up terminal emulator
4: type su, press enter and give it root acces
5: type setenforce 0 and press enter
6: WAIT untill the device asks you to enter your sim pin (this means that it worked)
7: turn on wi-fi (it might take a little long to turn on wi-fi though)
8: that's it
9: well not yet there is one step you can do to make it easier to change the selinux state, Download and install this app:https://play.google.com/store/apps/d....selinux&hl=en
10: again make sure your device is rooted
11: open the app and now you can switch between permissive (this mode is the one that fixed the issues) and enforcing (default mode: wi-fi, ... don't work on this mode)
FAQ:
What is not affected (what doesn't work): The camera (can't connect to camera or hot reboot when launching camera app), more?
What is affected (what is fixed): WI-FI, Data (LTE too) Outgoing calls, more?
Do i have to do this everytime i boot my device: Yes for now you do
On what build does it run: mrsteve555's build, there were 2 reports of it not working on bagy's build
Credits:
Mrsteve555 and bagyusz for the amazing rom
Click to expand...
Click to collapse
just update titanium backup to latest version in case of super user access error.like this : can't aquire root provileges....this attemtp was made using the "/system/xbin/su" command.
Fix wifi hotspot => credit : MrSteve555
setup zram in android 5[credit : Mrsteve555]
Code:
#!/system/bin/sh
sleep 30
echo xM > /sys/block/zram0/disksize
mkswap /dev/block/zram0
swapon /dev/block/zram0
Replace x with your desired value(in MB)
And zram doesn't make phone "much faster", it just allows more multitasking while slowing the phone a bit.
Click to expand...
Click to collapse
fix sdcard mount problem [credit : Mrsteve555]
Code:
su
depmod
rmmod texfat
modprobe exfat_core
modprobe exfat_fs
These commands will try to load different exfat modules, I didn't test it myself, though.
Click to expand...
Click to collapse
Fix for unresponsive touch screen[credit : Mrsteve555]
Code:
#!/system/bin/sh
echo 20 > /sys/devices/i2c-3/3-0024/main_ttsp_core.cyttsp4_i2c_adapter/finger_threshold
chmod 666 /sys/devices/i2c-3/3-0024/main_ttsp_core.cyttsp4_i2c_adapter/signal_disparity
echo 0 > /sys/devices/i2c-3/3-0024/main_ttsp_core.cyttsp4_i2c_adapter/signal_disparity
Fix for music file not playing when you uncheck nuplayer in developer options
The solution to that will be installing viper audio. There is a different version for lollipop. You have to flash 3 zips. They need nuplayer off so you can play music and videos easily with nuplayer off
Click to expand...
Click to collapse
Download from this post [Thanks@pranavthombare]

r 3

and-roid007 said:
Fix hot reboots by turning off adaptive brightness(settings->display->adaptive brightness)
Fix connectivity problem on CM12.by @noahvt
Click to expand...
Click to collapse
Really thks ;D

Youve stated that GSM voice hasnt been tested - This is voice calls. Are they working on MrSteves build with the latest fixes or not as there seems to be mixed reports.
---------- Post added at 02:54 PM ---------- Previous post was at 02:52 PM ----------
Also your link to the https://play.google.com/store/apps/d....selinux&hl=en doesnt work
I assume its this app? https://play.google.com/store/apps/details?id=com.mrbimc.selinux&hl=en_GB

and-roid007 said:
Fix hot reboots by turning off adaptive brightness(settings->display->adaptive brightness)
Fix connectivity problem on CM12.by @noahvt
Click to expand...
Click to collapse
The fix isn't working for me

@Oblox
you are right about both.corrected

Sorry the pin code doesn't apear because i don't have set any pin code ... IM REALLYYYYYYY NOOOOOB! xD
Edit: But i can't send call, i recieve

bobslesbricoleurs said:
Sorry the pin code doesn't apear because i don't have set any pin code ... IM REALLYYYYYYY NOOOOOB! xD
Edit: But i can't send call, i recieve
Click to expand...
Click to collapse
just open terminal : type su-> type setenforce 0,hit enter.if no dialog appears dont worry,it's ok.
go to settings-> about phone-> make sure that SELinux status = premissive.
see the bug list :
GSM Voice : doesn't works (Only can recieve calls)
Click to expand...
Click to collapse

and-roid007 said:
How to install cm12 (mrsteve) on sp . by @Dammer Martins
Click to expand...
Click to collapse
What's the problem if I flash GApps with the ROM?

sohan3421 said:
What's the problem if I flash GApps with the ROM?
Click to expand...
Click to collapse
The problem will occur if you do this on first flash as itll take a lot longer to boot and the auto brightness forced reboot will kick in before it finishes. Once system is in and auto brightness disabled then install gapps.

No new about calls?
Sent from my Xperia SP using XDA Premium 4 mobile app

Navigation bar and Pie controls
I know when I moved from 4.4 to 5.0 most things that I could get from xposed or custom roms were gone such as pie controls. I've been looking around for ages and I've managed to remove navigation bar using build.prop and adding a highly customizable pie controls app. If anyone wants a tutorial made to hide navigation bar and get pie controls just ask and ill do it

Pie
Keep Pie In Memory​
1. Search root explorer in Google play 3rd one down.
2. Open it and press mount R/W ( top of app)
3. Go into root directory and open the folder data.
4. Create new file and name it local.prop
5. Long hold the newly created app and press open in text editor.
6. Add com.android.lmt
This is to prevent android removing the service from memory when it is low.
Remove Navigation Bar​
1. Open build.prop located on /system
2. Add qemu.hw .mainkeys = 1 Remember to add a space between either side of the equals or it won't work
3.Do not reboot until you have downloaded LMT launcher
Add Pie Controls​
LMT Launcher ( PIe Controls (Not an actual launcher like nova or apex its just called that) )
1. Download the latest apk from here http://forum.xda-developers.com/showthread.php?t=1330150
2. Open the app make sure autostart is selected
3. Swipe right until you get to Pie.
4.Use these settings ( navigate to the screenshots) it will get rid of the unneeded two extra slots of pie controls
Finally Reboot
If you have titanium backup convert lmt launcher into a system app to integrate the pie controls more into the system

and-roid007 said:
How to install cm12 (mrsteve) on sp . by @[SIZE="5"]Dammer Martins[/SIZE]
Click to expand...
Click to collapse
Why should I add ramdisk fix?

sohan3421 said:
Why should I add ramdisk fix?
Click to expand...
Click to collapse
Why not?
Because the ramdisk inside the zip is either corrupt or incomplete, resulting in bootloop if flashed.

sohan3421 said:
Why should I add ramdisk fix?
Click to expand...
Click to collapse
Coz it'll go in a bootloop if you don't and then clog this thread too, by begging for a link and a guide which was clearly given and posted by many users.

gapps working fine?

shahrukhqasim said:
gapps working fine?
Click to expand...
Click to collapse
yes.i think

[GUIDE] How to properly change / remove zoom error in eui/miuipro

Guys as we all know when we root our eui we get stuck with zoom sheeting on every app.
But I have found out a fix.
First things first tools required:
1:terminal emulator
2:build prop editor / root file manager
Fix:
Go ahead and open terminal emulator.
Enter the following code
Su
And click enter
wm density ###
### us where you input the amount of DPI you want 420 is normal DPI
-1st part done!
Now open build prop editor
Next Look for "ro.sf.lcd_density=###"
Change ### to previous value which you have set in terminal emulator.
Reboot!
Done!
Now you may think I might have done this in some DPI app but it will make more problems than solving it . believe me!
Special thanks my friend: snehashish
For providing me the fix
Hit thanks if you like my work!
Cheers:highfive:

Guys you can also use this to properly change DPI in eui and miui pro without font or clock glitches.:good:

Gautham V said:
Guys as we all know when we root our eui we get stuck with zoom sheeting on every app.
But I have found out a fix.
First things first tools required:
1:terminal emulator
2:build prop editor / root file manager
Fix:
Go ahead and open terminal emulator.
Enter the following code
Su
And click enter
wm density ###
### us where you input the amount of DPI you want 420 is normal DPI
-1st part done!
Now open build prop editor
Next Look for "ro.sf.lcd_density=###"
Change ### to previous value which you have set in terminal emulator.
Reboot!
Done!
Now you may think I might have done this in some DPI app but it will make more problems than solving it . believe me!
Special thanks my friend: snehashish
For providing me the fix
Hit thanks if you like my work!
Cheers:highfive:
Click to expand...
Click to collapse
The first part works. The second part does not: there is no ro.sf.lcd_density setting in the build.prop. And the settings app still reports the display as zoomed.

emkorial said:
The first part works. The second part does not: there is no ro.sf.lcd_density setting in the build.prop. And the settings app still reports the display as zoomed.
Click to expand...
Click to collapse
It does still say zoomed in settings but it is not

emkorial said:
The first part works. The second part does not: there is no ro.sf.lcd_density setting in the build.prop. And the settings app still reports the display as zoomed.
Click to expand...
Click to collapse
You wil fund the line ro.sf.lcd_density in all ROM except eUI, in eUI you can search for persist.ro.sf.lcd_density
Or similar to this one but that line start with persist

after doing this trick in miui pro rom i am continuously getting an error that system stopped

Rajashekar0675 said:
after doing this trick in miui pro rom i am continuously getting an error that system stopped
Click to expand...
Click to collapse
You must have messed somewhere

I tried the fix and didnt get any errors, but it still randomly switches from zoom mode to normal when opening apps. I really only notice it in gmail and chrome.

Guess changing the DPI has resulted in zoomed in pictures when cropping, cropping happens right as the markers indicate but the crop preview is zoomed in which makes it impossible to edit pictures. Is there a solution/hack for this?