Related
Hello:
I am looking to build the official Atrix-dev CM7 weekly/nightly, however, cannot find any instructions/guide to do so. Of course, I could simply pull everything from the Atrix-dev CM7 github and overlay on base CM7 source, but thought I'd ask before I do that.
Why build from source? I am not looking to build a CM7 based ROM or release anything, just change some minor things for my own consumption:
- Not have mmcblk1p2 mount as /sd-ext [currently set in a .mk file according to vanilla CM7 source for olympus]
- Since webtop doesnt work in CM7 (and I dont need it) expand /data(p16) to include the partition space of /osh(p13) [means mucking around with the partition table, and the init scripts to change mounts]
- have emmc mount on /sdcard and external sdcard mount on /sd-ext so that backups from other ROMs work
Cheers
acerbix said:
Hello:
I am looking to build the official Atrix-dev CM7 weekly/nightly, however, cannot find any instructions/guide to do so. Of course, I could simply pull everything from the Atrix-dev CM7 github and overlay on base CM7 source, but thought I'd ask before I do that.
Why build from source? I am not looking to build a CM7 based ROM or release anything, just change some minor things for my own consumption:
- Not have mmcblk1p2 mount as /sd-ext [currently set in a .mk file according to vanilla CM7 source for olympus]
- Since webtop doesnt work in CM7 (and I dont need it) expand /data(p16) to include the partition space of /osh(p13) [means mucking around with the partition table, and the init scripts to change mounts]
- have emmc mount on /sdcard and external sdcard mount on /sd-ext so that backups from other ROMs work
Cheers
Click to expand...
Click to collapse
Check here.
http://forum.xda-developers.com/showthread.php?t=915435
It's not for Atrix but you can just do it by modifying model name.
I just followed this method.
(Currently having java related problem though)
+1 it's a good one and is one of my references too.
AndroidON said:
Check here.
http://forum.xda-developers.com/showthread.php?t=915435
It's not for Atrix but you can just do it by modifying model name.
I just followed this method.
(Currently having java related problem though)
Click to expand...
Click to collapse
+1. Great recommendation. Just used it to complete my first build.
Sent from my MB860 using XDA App
AndroidON said:
Check here.
http://forum.xda-developers.com/showthread.php?t=915435
It's not for Atrix but you can just do it by modifying model name.
I just followed this method.
(Currently having java related problem though)
Click to expand...
Click to collapse
Thanks for the info - not quite what I was looking for though. If you follow these instructions you build the vanilla CM7. I wanted to get/build the Atrix customized bits (i.e fingerprint scanner for example) which are not in the vanilla sources. I am guessing that can be pulled down from Atrix-dev github. Original post was to see if there was an easy way to do that.
After looking at the atrix developer github, found a default.xml for the .repo that should work, and used it.
acerbix said:
Thanks for the info - not quite what I was looking for though. If you follow these instructions you build the vanilla CM7. I wanted to get/build the Atrix customized bits (i.e fingerprint scanner for example) which are not in the vanilla sources. I am guessing that can be pulled down from Atrix-dev github. Original post was to see if there was an easy way to do that.
After looking at the atrix developer github, found a default.xml for the .repo that should work, and used it.
Click to expand...
Click to collapse
The fingerprint scanner was working in my kang. The only thing I pulled from the atrix-dev-team's github were the proprietary vendor files. Other than that those instructions should get you an up to date nightly build.
Sent from my MB860 using XDA App
ghost_og said:
The fingerprint scanner was working in my kang. The only thing I pulled from the atrix-dev-team's github were the proprietary vendor files. Other than that those instructions should get you an up to date nightly build.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Thanks so much for the info - trying it now.
ghost_og said:
The fingerprint scanner was working in my kang. The only thing I pulled from the atrix-dev-team's github were the proprietary vendor files. Other than that those instructions should get you an up to date nightly build.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Hmm you have put that in the local_manifest.xml which line did you use? I'm trying to get it to work but somehow can't get the FP unlock option or the change of navigation with fp (navigation does work though).
acerbix said:
Thanks so much for the info - trying it now.
Click to expand...
Click to collapse
crnkoj said:
Hmm you have put that in the local_manifest.xml which line did you use? I'm trying to get it to work but somehow can't get the FP unlock option or the change of navigation with fp (navigation does work though).
Click to expand...
Click to collapse
Well I'm a big dummy. Looks like the only thing that was working was the trackpad navigation. I never use the scan/unlock feature so I just assumed it was working also. I should have checked before posting. I just caught up on my reading and saw your posts with t.s. eliot over in the Weeklys thread, crnkoj. Sorry for the misinformation acerbix.
Anyone else successfully built from source with full FP functionality?
ghost_og said:
Well I'm a big dummy. Looks like the only thing that was working was the trackpad navigation. I never use the scan/unlock feature so I just assumed it was working also. I should have checked before posting. I just caught up on my reading and saw your posts with t.s. eliot over in the Weeklys thread, crnkoj. Sorry for the misinformation acerbix.
Anyone else successfully built from source with full FP functionality?
Click to expand...
Click to collapse
Oh okay - I thought I must be doing something stupid so I PM'd you last night rather than post here. So we all can get trackpad working in the kang but not device setting/lock/unlock
crnkoj said:
Hmm you have put that in the local_manifest.xml which line did you use? I'm trying to get it to work but somehow can't get the FP unlock option or the change of navigation with fp (navigation does work though).
Click to expand...
Click to collapse
I tried replacing default.xml in .repo with the one in Atrix dev git repository, and then pulling down the code. That lead to multiple build failure, so I am assuming hte changes in the atrix dev github are not synced with the changes upstream coz vanilla cyanogenmod builds fine.
I am not even getting the "Device Settings" option that shows up in the weekly build, though the trackpad works fine. I'll try looking at the Settings.apk code to see if there is something I am missing.
cmkoj: Do you have a local_manifest.xml that works and gives you a good build? Open to sharing that?
ah ghost_og i see, i was like how could he get it to work np though anyhow i think one has to implement this: https://github.com/Atrix-Dev-Team/android_packages_apps_Settings into teh build aswell to get fp (read the latest commits there ). second to that probably one has to use https://github.com/Atrix-Dev-Team/android_device_motorola_olympus.git with the branch fingerprint int he local manifest to get it to work than (i have tried this like a few times still not working ...)
acerbix im not sure what you need? do you need a local manifest that makes fp work as it should ( i havent managed to get it to work yet) or just one that works for building? i can sure share the latter one
crnkoj said:
ah ghost_og i see, i was like how could he get it to work np though anyhow i think one has to implement this: https://github.com/Atrix-Dev-Team/android_packages_apps_Settings into teh build aswell to get fp (read the latest commits there ). second to that probably one has to use https://github.com/Atrix-Dev-Team/android_device_motorola_olympus.git with the branch fingerprint int he local manifest to get it to work than (i have tried this like a few times still not working ...)
acerbix im not sure what you need? do you need a local manifest that makes fp work as it should ( i havent managed to get it to work yet) or just one that works for building? i can sure share the latter one
Click to expand...
Click to collapse
Thanks! I feel like such an idiot now. When I changed the drop down list for the branch, I saw the source for the fingerprint unlock actions! (i.e chooselockfinger.java, confirmlockfinger.java).
Off to try a build now!
crnkoj said:
ah ghost_og i see, i was like how could he get it to work np though anyhow i think one has to implement this: https://github.com/Atrix-Dev-Team/android_packages_apps_Settings into teh build aswell to get fp (read the latest commits there ). second to that probably one has to use https://github.com/Atrix-Dev-Team/android_device_motorola_olympus.git with the branch fingerprint int he local manifest to get it to work than (i have tried this like a few times still not working ...)
acerbix im not sure what you need? do you need a local manifest that makes fp work as it should ( i havent managed to get it to work yet) or just one that works for building? i can sure share the latter one
Click to expand...
Click to collapse
Right now, I'd settle for one that works for building. I manually overlay files, so that will definitely be easier
t.s.eliot said:
Thanks! I feel like such an idiot now. When I changed the drop down list for the branch, I saw the source for the fingerprint unlock actions! (i.e chooselockfinger.java, confirmlockfinger.java).
Off to try a build now!
Click to expand...
Click to collapse
Lets know if you get it working I'm building too [clobber build just for the heck of it - will keep you posted]
Thanks a ton, cmkoj for all the help/pointers!
crnkoj said:
ah ghost_og i see, i was like how could he get it to work np though anyhow i think one has to implement this: https://github.com/Atrix-Dev-Team/android_packages_apps_Settings into teh build aswell to get fp (read the latest commits there ). second to that probably one has to use https://github.com/Atrix-Dev-Team/android_device_motorola_olympus.git with the branch fingerprint int he local manifest to get it to work than (i have tried this like a few times still not working ...)
acerbix im not sure what you need? do you need a local manifest that makes fp work as it should ( i havent managed to get it to work yet) or just one that works for building? i can sure share the latter one
Click to expand...
Click to collapse
Thank you for pointing out the Settings and Device branches. Was definitely using the old gingerbread branches before. I just replaced those two folders with the fingerprint branch and am building again. Will check back in once it's done.
*Update* Still no luck. I tried using the updated Device and Settings folders but only navigation works still. Dang.
ghost_og said:
Thank you for pointing out the Settings and Device branches. Was definitely using the old gingerbread branches before. I just replaced those two folders with the fingerprint branch and am building again. Will check back in once it's done.
*Update* Still no luck. I tried using the updated Device and Settings folders but only navigation works still. Dang.
Click to expand...
Click to collapse
Away from my Atrix so cant try this yet - do you think the kernel matters? Did you switch to the kernel included in the build?
acerbix said:
Away from my Atrix so cant try this yet - do you think the kernel matters? Did you switch to the kernel included in the build?
Click to expand...
Click to collapse
Hey guys, I also noticed that android_ frameworks_base has a fingerprint branch with updated commits from t0dbld. I've included this third replacement folder and will be trying another build. Might want to try including this with the 2 branches crnjok pointed out above. I'm keeping my fingers crossed for this one.
I have not replaced any kernels prior to building and use what comes with the stock build. That's a whole other issue for me. When I try to compile just the kernel my zImage ends up being 1mb bigger than faux's and the packaged boot.img I create will not boot. I'm guessing this is due to my being on a 32-bit machine, but I'm not positive.
ghost_og said:
Hey guys, I also noticed that android_ frameworks_base has a fingerprint branch with updated commits from t0dbld. I've included this third replacement folder and will be trying another build. Might want to try including this with the 2 branches crnjok pointed out above. I'm keeping my fingers crossed for this one.
I have not replaced any kernels prior to building and use what comes with the stock build. That's a whole other issue for me. When I try to compile just the kernel my zImage ends up being 1mb bigger than faux's and the packaged boot.img I create will not boot. I'm guessing this is due to my being on a 32-bit machine, but I'm not positive.
Click to expand...
Click to collapse
ye i forgot to mention that one lol, i thought its in the fingerprint build though. for my use i manually git cloned the vendor_motorola repo into /working_dir/vendor/ but havent had any luck. regarding the kernel afaik if you put the additional repos into your local_manifest.xml it should use the kernel from there (if one is available). but i dont really think the kernel is needed to be changed, since on my builds i had the authentec.truesuite (or whatever the process for fp is called) running, only the fp unlock/device option were missing (there is a Fingerprintsomething.apk in the vendor repo of atrix dev team that i have had pulled in and built with but it didnt work, so yes im slowly giving up (second to that i tried setting up a build env on a second pc that drastically faster than the other one an i cannot get repo sync to sync android_prebuilt - just deleted the whole thing and did init again...)
as for the local_manifest.xml it should look like this http://pastebin.com/ccvVi2k9 for building the gb (that is with nav functioning fp but no unlock) if you want to get unlock to work you need to probably put in the other ones aswell (just by copying the <project path="device/motorola/olympus"
name="Atrix-Dev-Team/android_device_motorola_olympus.git"
remote="gh"
revision="gingerbread"/>
part and changing the name to appropriate and teh revision in all to fingerprint)
thanks go to fattire from the nook color forums who thought me how to make and edit these local_manifest.xml files and i used his file as a template for mine aswell.
i have to admit it im slowly sick of not being able to build one with working fp =/
Guys, see here for what directories to be pulled from atrix-dev-team github vs what to be kept in original CM7:
https://github.com/Atrix-Dev-Team/android/blob/gingerbread/default.xml
crnkoj said:
(second to that i tried setting up a build env on a second pc that drastically faster than the other one an i cannot get repo sync to sync android_prebuilt - just deleted the whole thing and did init again...)
Click to expand...
Click to collapse
Try updating ~/android/system/.repo/manifests/default.xml. I used this to fix the problem with the prebuilt repo sync:
Another workaround is to add the following remote definition:
Code:
<remote name="github-https"
fetch="https://github.com/" />
Then change the project definition to:
Code:
<project path="prebuilt" name="CyanogenMod/android_prebuilt" remote="github-https"/>
Once things are back to normal, you can remove the additional remote, and restore the original manifest.
Click to expand...
Click to collapse
It was provided in the comments section here.
ghost_og said:
Try updating ~/android/system/.repo/manifests/default.xml. I used this to fix the problem with the prebuilt repo sync:
It was provided in the comments section here.
Click to expand...
Click to collapse
yes thanks, lol, i knew about the fix and had the first part of it done with changing to https, but forgot about the second part, idiot i...
anyhow i resynced and am building now on the other pc with this local manifest http://paste.pocoo.org/show/534837/
Unofficial CyanogenMod 10.1
Rom: Unofficial CyanogenMod 10.1
Android version: 4.2.2
Status: Alpha (means not ready as beta or even stable release!)
What doesn't work:
Sound partially, only calls not working right
Wifi
GPS
Bluetooth
Brightness control
Airplane mode
Camera, did work though in earlier version
Disclaimer
I am not responsible for bricked devices, broken hearts, thermonuclear war or you getting fired because the alarm app failed. It's up to you, not to me.
Click to expand...
Click to collapse
Downloads:
Google Drive CM10.1
Mirror, hosted by Burn02
The version differences:
Code:
24/2/14
[LIST]
[*] Using new audio hall
[*] Microphone works now, call still doesn't
10/2/14
[LIST]
[*] Initial audio support
[*] Fixed Wifi symlink for MAC-adres
[*] ICS_AUDIO_BLOB disabled
[/LIST]
01/12/13
[LIST]
[*] ICS_AUDIO_BLOB enabled
[*] Using original audio blobs
[/LIST]
14/11/13
[LIST]
[*] Both Internal storage and external storage working
[*] Build modified init from source
[*] Dalvik with x86 houdini support
[*] More modules build from source
[/LIST]
6/11/13
[LIST]
[*] Only internal storage working
[*] Libc with x86 wrappers support
[*] Pixelflinger/charger with x86 encoder support
[*] Ramdisk changes
[*] Android Build fixes for x86
[*] Add intel specific codes
[/LIST]
Workarounds:
The Rom can bootloop when installed in TWRP. If so use CWM instead for a while till TWRP is working correctly.
Want to help?
This Rom is made by many people that contribute to it, if it is in code, new information or just bug logs. Everybody can help. Make a 'Logcat' about the problems u encounter and post them here. Give a brief explanation of what u did and wanted to archive (we will try our best to get them sorted, eventually) or contribute with code into my github at the moment.
Click to expand...
Click to collapse
Source:
https://www.github.com/HazouPH
About the sound:
When using the rom zip with ICS_BLOBS_ENABLED and adding the right files:
etc/parameter-framework/*
etc/sound.conf
etc/audio_effects.conf
etc/media_codecs.xml
etc/phonecall_es305b_*
lib/hw/alsa.smi.so
lib/hw/audio.primary.smi.so
lib/hw/audio_policy.smi.so
lib/parameter-framework-plugins/*
lib/libasound.so
usr/lib/alsa-lib/*
usr/share/alsa/*
The rom will bootloop and the mediaserver will crash with a log file. See attachment. If u have any idea on how to solve it, i would happily like to know.
Hazou said:
About the sound:
When using the rom zip with ICS_BLOBS_ENABLED and adding the right files:
etc/parameter-framework/*
etc/sound.conf
etc/audio_effects.conf
etc/media_codecs.xml
etc/phonecall_es305b_*
lib/hw/alsa.smi.so
lib/hw/audio.primary.smi.so
lib/hw/audio_policy.smi.so
lib/parameter-framework-plugins/*
lib/libasound.so
usr/lib/alsa-lib/*
usr/share/alsa/*
The rom will bootloop and the mediaserver will crash with a log file. See attachment. If u have any idea on how to solve it, i would happily like to know.
Click to expand...
Click to collapse
Good work Hazou !
I will give you some idea. And why don't you use JB libs ?
1. Replace mediaserver by ICS one
2. Replace /system/lib/hw/audio.primary.smi.so by CyanogenMod file
3. There is a problem with libc.so, so just try to replace this lib with ICS one....
4. Replace /system/lib/libat-manager.so (if exist) by CM one
Do these steps one by one and logcat for each step.
GalaxyUser
GalaxyUser said:
Good work Hazou !
I will give you some idea. And why don't you use JB libs ?
1. Replace mediaserver by ICS one
2. Replace /system/lib/hw/audio.primary.smi.so by CyanogenMod file
3. There is a problem with libc.so, so just try to replace this lib with ICS one....
4. Replace /system/lib/libat-manager.so (if exist) by CM one
Do these steps one by one and logcat for each step.
GalaxyUser
Click to expand...
Click to collapse
Ty, for the suggestions. Some i can already answer
1. We could try this, but then also the libaudioflinger needs replacing. And maybe another file.
2. Can try it, but most likely doesn't work. The stock cyanogenmod one doesn't have the right code the execute our soundcard. I found out that the audio_policy.smi.so is the stock one with just small modifications.
3. Libc can't be switched. To many things depend on libc. And besides that, the code in libc were it goes wrong is the same one as my modified jb libc
4. libat-manager is a specific module for our device. we don't have the right sources to build it. But i can maybe replace it with the one from the 4.2.2 drop of the chineze version. But then it has some restrictions because off the chinese firewall.
Keep up the ideas. Maybe we get there someday
Hazou
Hazou said:
Ty, for the suggestions. Some i can already answer
1. We could try this, but then also the libaudioflinger needs replacing. And maybe another file.
2. Can try it, but most likely doesn't work. The stock cyanogenmod one doesn't have the right code the execute our soundcard. I found out that the audio_policy.smi.so is the stock one with just small modifications.
3. Libc can't be switched. To many things depend on libc. And besides that, the code in libc were it goes wrong is the same one as my modified jb libc
4. libat-manager is a specific module for our device. we don't have the right sources to build it. But i can maybe replace it with the one from the 4.2.2 drop of the chineze version. But then it has some restrictions because off the chinese firewall.
Keep up the ideas. Maybe we get there someday
Hazou
Click to expand...
Click to collapse
Thanks for answer.
1. Try to replace libaudioflinger.so, then provide a logcat please. It may need hex edit (and I can do it).
4. Yes try it because sound need this lib.
I think first answer is the best... If the rom allow logcat access after replacement.
Edit 1: my Razr I is broken but I would like to help
Edit 2: Sound is very hard to works on porting rom (even if it's not the same thing with CM), so perhaps it needs some others files to change
Edit 3: Try to replace these libs too, with the chineze version:
/system/lib/libamc.so
/system/lib/libevent-listener.so
And you need to add FM's lib because ICS libaudioflinger.so needs these files:
Code:
12-05 16:14:35.939 527 527 E AudioHardwareALSA: Cannot load FM HW Module
http://xt890.blogspot.com.ar/2013/12/101-rom-cyanogenmod-build-3-para.html the site over there claims that the wifi is working..can you have a look?
EDIT: the rom download link is your google drive
Hazou said:
Unofficial CyanogenMod 10.1
Click to expand...
Click to collapse
Thanks!.. is a great news...
antkalaitzakis96 said:
http://xt890.blogspot.com.ar/2013/12/101-rom-cyanogenmod-build-3-para.html the site over there claims that the wifi is working..can you have a look?
EDIT: the rom download link is your google drive
Click to expand...
Click to collapse
Y' i know. He asked permission tot post it
Wifi working isn't a very big problem. I want to first hopefully fix the sound, or hope that some ideas might help.
Sent from my GT-P5110 using XDA Premium HD app
Hey can somebody post some screenshots ??
I don't think it's the right thread to post screenshot. This thread is for helping to develop and make all features work.
great .. thanks @Hazou
Enviado desde mi Moto usando Tapatalk
ICuaI said:
I don't think it's the right thread to post screenshot. This thread is for helping to develop and make all features work.
Click to expand...
Click to collapse
What would be the thread to post in, other than the one who actually presents the rom we are taking screenshots of?
hotpokets said:
What would be the thread to post in, other than the one who actually presents the rom we are taking screenshots of?
Click to expand...
Click to collapse
You don't need a screenshot, if this doesn't work yet. This is a thread to make the rom functional. Then it can be released to the regular users like us, who just want to use it regardless of the making process
You can go in every CM10.1-thread in this forum. I am sure that you will find enough screenshots of CM10.1. The rom for our xt890 doesn't have another look.
Or try this alpha-build on your own phone
And now for me I'll stop being of topic
Sorry for that to all the devs
GalaxyUser said:
Thanks for answer.
1. Try to replace libaudioflinger.so, then provide a logcat please. It may need hex edit (and I can do it).
4. Yes try it because sound need this lib.
I think first answer is the best... If the rom allow logcat access after replacement.
Edit 1: my Razr I is broken but I would like to help
Edit 2: Sound is very hard to works on porting rom (even if it's not the same thing with CM), so perhaps it needs some others files to change
Edit 3: Try to replace these libs too, with the chineze version:
/system/lib/libamc.so
/system/lib/libevent-listener.so
And you need to add FM's lib because ICS libaudioflinger.so needs these files:
Code:
12-05 16:14:35.939 527 527 E AudioHardwareALSA: Cannot load FM HW Module
Click to expand...
Click to collapse
So, i tested the methods u supposed.
first off, the roms doesn't need the fm module to work It's like the usb and hdmi audio modules that are expanding the audio functions, but aren't necessary for booting.
Than the rest, i found out that all the libamc, libevent*, libat-* etc. the files were we don't have the source from are the same as the stock jelly ones. So no need to change those. Like the other libs, mediaserver is the same as the one i compiled compared to the chinese 4.2.2 one.
For the libaudioflinger part, if i switch them, they won't boot up there service anymore. Why i doný know, but i have the feeling that the libaudioflinger won't solve the mystery.
Another thing i read from the logcat is that it crashes right at the moment the sound-card (medfieldaudio) aka 0x00000002 is called, after it is set that it can be used. So it seems to me that the alsa lib can't read the device properly. Somewhere allong the line a thing can't reach it or is giving the wrong data. But what....
The next thing i gonna try is making my own alsa module with tinyalsa implementation. To get only the sound working. FM and the audience driver won't work then. Great chance that it won't work, but you gotta try
Hazou said:
So, i tested the methods u supposed.
first off, the roms doesn't need the fm module to work It's like the usb and hdmi audio modules that are expanding the audio functions, but aren't necessary for booting.
Than the rest, i found out that all the libamc, libevent*, libat-* etc. the files were we don't have the source from are the same as the stock jelly ones. So no need to change those. Like the other libs, mediaserver is the same as the one i compiled compared to the chinese 4.2.2 one.
For the libaudioflinger part, if i switch them, they won't boot up there service anymore. Why i doný know, but i have the feeling that the libaudioflinger won't solve the mystery.
Another thing i read from the logcat is that it crashes right at the moment the sound-card (medfieldaudio) aka 0x00000002 is called, after it is set that it can be used. So it seems to me that the alsa lib can't read the device properly. Somewhere allong the line a thing can't reach it or is giving the wrong data. But what....
The next thing i gonna try is making my own alsa module with tinyalsa implementation. To get only the sound working. FM and the audience driver won't work then. Great chance that it won't work, but you gotta try
Click to expand...
Click to collapse
Will this ROM work on Lenovo K900?
charming.arpit said:
Will this ROM work on Lenovo K900?
Click to expand...
Click to collapse
Not out of the box, no.
Sent from my GT-P5110 using XDA Premium HD app
intel released source code for android 4.4
http://software.intel.com/en-us/articles/android-4-4-kitkat-x86-emulator-system-image
if its helpful
Did you guys saw this?
http://software.intel.com/en-us/articles/android-4-4-kitkat-x86-emulator-system-image
drunk_ryder24 said:
http://software.intel.com/en-us/articles/android-4-4-kitkat-x86-emulator-system-image
if its helpful
Click to expand...
Click to collapse
hey this is just
Android* 4.4 (KitKat) x86 Emulator System Image
this is for developers who running a pc (x86) and want to emulate the newest android.
this has nothing to do with our fone.
i think the problem is, this image dont got the drivers for our device.or any drivers expect for emulation.. dont know but thanks for the info that intel is developin
regard
CM12.{0,1} (Lollipop) official/unofficial builds for the Droid 4
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.0/5.1 (Lollipop), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at any of us for messing up your device, we will laugh at you.
* Collectively, and at the same time.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review.
These are WIP builds of porting CM12.{0,1} to the Droid 4 (and also other devices using the same device/motorola/omap4-common-infrastructure). They probably won't work, so don't expect too much. Use on your own risk!
Builds:
Last official build:
http://droid.cs.fau.de/cm-12.1/official/
Old manual builds:
http://droid.cs.fau.de/cm-12.0/pre-alpha-test/new_safestrap/
Changes (only device/family specific, CM base is always synced before build and contains more changes):
2015-04-16:
Switched CM build-target, new nightlies will now be 12.1: http://review.cyanogenmod.org/#/c/94693/
2015-02-01:
No more unofficial builds! See: http://review.cyanogenmod.org/#/c/87596/
2015-01-28:
Mobile data fixes
Remaining com.android.phone crashes on VZW finally fixed (thanks @joojoobee666)
2015-01-24:
Fixed sw-keyboard popup when hw-keyboard is used (thanks @joojoobee666)
Fixed reboot to recovery
Fixed sepolicy for whisperd (dock service)
2015-01-22:
Fixed su-permissions
Crashes on Verizon most likely fixed, please report back
2015-01-20:
Fixed flashlight
2015-01-18:
SELinux updates.
This requires manual action for applications to continue being able to access their own files when upgrading from 2014-01-14 or 2014-01-15 (older versions are fine)!
Due to SELinux-bugs in 2014-01-1{4,5}, you have to relabel your data-partition on the first boot when upgrading from 2014-01-14/-15. This only needs to be done once. To do this, enable adb/usb debugging and grant root to adb (both in developer settings) and execute via an adb shell:
Code:
su -c 'for i in /data/*; do echo "${i}"; restorecon -DFrv "${i}"; done; sync; reboot'
2015-01-1{4,5}:
More fixes for {,umts_}spyder
sepolicy updates
GSM fixes
notable CM changes: su integration fixed
2015-01-11:
Updated SELinux policies (mostly for spyder/umts_spyder)
Added kernel stability fixes
Video decoding fixes
2015-01-09:
Enabled SELinux enforcing
Add SELinux-policies for motorola services
Enable ro.telephony.get_imsi_from_sim on VZW devices (thanks @joojoobee666)
2015-01-02:
Sync CM changes
2014-12-23:
Fixed stock camera
2014-12-22:
Sync CM changes
Fix build due to P2P changes (fix pushed into CM)
Enabled security for adb (keys/not root by default)
2014-11-30:
Added APN fixes for CDMA/LTE
Enabled multiuser mode (might not work yet)
Last update for a couple of weeks
2014-11-27:
Fixed graphics glitches
2014-11-26:
Fixed HW video-decoding
Enabled doze mode (no pickup sensor in the devices!)
CM resync as always
2014-11-23:
Probably fixed mobile data on LTE
Fixed WiFi-tethering
2014-11-22:
Requires a recovery supporting SELinux
What's working:
Phone (tested on Verizon and on GSM/UMTS in Europe)
Mobile data (at least on GSM/UMTS in Europe)
WiFi
WiFi-tethering
GPS
Camera
Playback of DRM-protected content (using Widevine from OnePlusOne)
What's not working:
Probably most everything else, including, but not limited to:
Some connectivity issues (should be solved now)
Data encryption
Gapps (CM-12.0):
Dhacker29 provides gapps for Lollipop:
http://d-h.st/YQG
http://d-h.st/jzr
http://droid.cs.fau.de/cm-12.0/gapps/ (Mirror)
Gapps (CM-12.1):
https://github.com/cgapps/vendor_google/releases/
Installation:
You need a new recovery supporting SELinux
An updated Safestrap (3.75) which supports SELinux can be found here: https://github.com/stargo/android_packages_apps_Safestrap/releases/tag/v3.75
Please read the instructions on how to install this version and follow the order of the steps in it.
GSM users:
To use this CM12.{0,1}-ROM on GSM-networks you should install Mentor.37's GSM patch
Source / Repositories:
maserati device-support: https://github.com/CyanogenMod/android_device_motorola_maserati
omap4-common device-support: https://github.com/CyanogenMod/android_device_motorola_omap4-common
omap4-common kernel: https://github.com/CyanogenMod/android_kernel_motorola_omap4-common
local manifest to build cm-12 for the Droid 4: http://droid.cs.fau.de/cm-12.0/pre-alpha-test/new_safestrap/local_manifest.xml
XDA:DevDB Information
CM 12.{0,1} on Motorola Droid4, ROM for the Motorola Droid 4
Contributors
stargo, Hashcode, Dhacker29
Source Code: https://github.com/CyanogenMod
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: No Longer Updated
Created 2014-11-23
Last Updated 2016-02-16
thank you @stargo, I am so pleased to see this thread, I was wondering when this thread is going to appear. Looks like I will continue to cling onto my droid 4 for a while, no virtual keyboard can beat a droid 4 keyboard.
Is data encryption enabled by default like on the nexus 6? I read that it greatly reduces the performance of the device. I meant this: http://www.xda-developers.com/android/disable-data-encryption-nexus-6/
Once again, thank you so much for your efforts in keeping this device alive.
sharptv said:
thank you @stargo, I am so pleased to see this thread, I was wondering when this thread is going to appear. Looks like I will continue to cling onto my droid 4 for a while, no virtual keyboard can beat a droid 4 keyboard.
Click to expand...
Click to collapse
Is data encryption enabled by default like on the nexus 6? I read that it greatly reduces the performance of the device. I meant this: http://www.xda-developers.com/android/disable-data-encryption-nexus-6/
Click to expand...
Click to collapse
No, data encryption is not enabled by default (and still doesn't even work for us).
Cheers,
Michael
Flipping sweet thanks y'all rock i love xda
Cast Screen
Hey stargo. thanks a lot for this! :good:
The 'Cast Screen' under settings pull-down menu is not working. It does not find any of the chromecasts that I have nearby.
Not a big deal, and not a priority at all for me, but just wanted to let you know.
Thanks again!
G'day,
just wanted to confirm the procedure for updating SafeStrap, since some people have CM11 in their stock slot:
in the first step (when you say 'go back to stock'), are you saying simply to boot the stock slot, regardless of ROM (since once SS is unistalled the 'slots' don't exist)?
Or do you mean boot to stock ROM, in stock slot?
I'm guessing it's the former, but I'd like to be sure before taking the plunge =)
thanks for your work! I gave the 2011 version a run over the weekend, it worked pretty well all things considered =)
gabhroo123 said:
Hey stargo. thanks a lot for this! :good:
The 'Cast Screen' under settings pull-down menu is not working. It does not find any of the chromecasts that I have nearby.
Not a big deal, and not a priority at all for me, but just wanted to let you know.
Thanks again!
Click to expand...
Click to collapse
May not ever work, IIRC, chromecasting the screen requires hardware we just don't have. :[
Shobai said:
G'day,
just wanted to confirm the procedure for updating SafeStrap, since some people have CM11 in their stock slot:
in the first step (when you say 'go back to stock'), are you saying simply to boot the stock slot, regardless of ROM (since once SS is unistalled the 'slots' don't exist)?
Or do you mean boot to stock ROM, in stock slot?
I'm guessing it's the former, but I'd like to be sure before taking the plunge =)
thanks for your work! I gave the 2011 version a run over the weekend, it worked pretty well all things considered =)
Click to expand...
Click to collapse
assuming that cm11 is currently installed in your stock slot and you want to update to the new test safestrap by stargo:
uninstall the existing safestrap using the original safestrap, for instance, if the existing safestrap is 3.73, you should install safestrap 3.73 and uninstall the recovery.
DO NOT REBOOT YOUR PHONE IN THE PROCESS
after you have uninstalled the existing recovery, uninstall safestrap(3.73), and then install the new safestrap by stargo, and install the recovery.
your safestrap is now updated, and nothing will be wiped.
YOU MUST NOT REBOOT YOUR PHONE DURING THE PROCESS, you can only reboot after a recovery has been installed.
hope you find this useful
thelolotov said:
May not ever work, IIRC, chromecasting the screen requires hardware we just don't have. :[
Click to expand...
Click to collapse
It need some kernel changes... but it should work...original gnex have the same cpu/gpu and they make it work... @lucize was seeing that but i dont know what happend with that
---------- Post added at 07:38 AM ---------- Previous post was at 07:37 AM ----------
By the way....thanks michael for your great work!...please make a donation link to send you some beer money!
Cheers, sharptv, much obliged =)
gabhroo123 said:
The 'Cast Screen' under settings pull-down menu is not working. It does not find any of the chromecasts that I have nearby.
Not a big deal, and not a priority at all for me, but just wanted to let you know.
Click to expand...
Click to collapse
Yes, our GPU driver does not support WFD. And in contrast to the GNEX, Motorola added much stuff to our version, so it's not easy to sync it back with the upstream kernel. Last time I tried that, I ended up with a non-working display and couldn't figure out why...
Shobai said:
just wanted to confirm the procedure for updating SafeStrap, since some people have CM11 in their stock slot:
in the first step (when you say 'go back to stock'), are you saying simply to boot the stock slot, regardless of ROM (since once SS is unistalled the 'slots' don't exist)?
Click to expand...
Click to collapse
Just boot to whatever you currently have installed in the stock slot. And I have to underline what @sharptv said, never reboot your phone in the process (it might work when you have the stock ROM in the stock slot, but it will surely break in every other case).
Cheers,
Michael
Will cm12 be pre-rooted in future? I can't seem to find anything solid on this, hopefully someone will be able to shed some light on this.
This App Camera work fine: https://play.google.com/store/apps/details?id=com.radcam.camera
---------- Post added at 11:34 AM ---------- Previous post was at 11:31 AM ----------
sharptv said:
Will cm12 be pre-rooted in future? I can't seem to find anything solid on this, hopefully someone will be able to shed some light on this.
Click to expand...
Click to collapse
See this thread: http://www.xda-developers.com/android/supersu-beta-lollipop-root-stock-kernel/
Download and install with recovery
I can confirm that at least on my phone that LTE is working. Great work .
flash these zips in recovery for root i got the from my nexus 7 root toolkit
HOPE IT WORKS FOR YOU :good::cyclops:
TheXG6HD said:
I can confirm that at least on my phone that LTE is working. Great work .
Click to expand...
Click to collapse
Yay! Thanks for confirming
It is a really bad hack, but if it works... http://review.cyanogenmod.org/78845
Cheers,
Michael
stargo said:
Yay! Thanks for confirming
It is a really bad hack, but if it works... http://review.cyanogenmod.org/78845
Cheers,
Michael
Click to expand...
Click to collapse
Data doesn't come up on its own, still needs some prodding (selecting the APN) and will go out randomly. Still not ready for prime time, sadly.... :<
It does come up a lot quicker, however.
thelolotov said:
Data doesn't come up on its own, still needs some prodding (selecting the APN) and will go out randomly. Still not ready for prime time, sadly.... :<
It does come up a lot quicker, however.
Click to expand...
Click to collapse
That's VZW weirdness
But if it comes up, then data is actually passing? Because that is what my patch was intended to fix. Before that the data-indicator would show up, but data would not actually get transmitted...
Can you probably send me the output of "ip route list" and "ip addr list" when LTE data is connected?
Would be interesting to see, what is actually happening now. I can only guess from here...
Regards,
Michael
stargo said:
That's VZW weirdness
But if it comes up, then data is actually passing? Because that is what my patch was intended to fix. Before that the data-indicator would show up, but data would not actually get transmitted...
Can you probably send me the output of "ip route list" and "ip addr list" when LTE data is connected?
Would be interesting to see, what is actually happening now. I can only guess from here...
Regards,
Michael
Click to expand...
Click to collapse
LTE was working on first build, just took 10+ mins to connect then worked good.
Sent from my XT907 using Tapatalk
stargo said:
That's VZW weirdness
But if it comes up, then data is actually passing? Because that is what my patch was intended to fix. Before that the data-indicator would show up, but data would not actually get transmitted...
Can you probably send me the output of "ip route list" and "ip addr list" when LTE data is connected?
Would be interesting to see, what is actually happening now. I can only guess from here...
Regards,
Michael
Click to expand...
Click to collapse
The deal is, the data works at first, then at random intervals it breaks and needs to be manually reset. I'm travelling right now so I can't really risk using CM12 right now, but I'll get you some logs when possible. JJB is having the same issue, I'll ask him to try and get you some details.
Hello XDA,
As all of you may know there is a 4G LTE version of the Moto G 2nd Generation, better known under the model number XT1072 and XT1079. Unfortunately almost all ROMs are created for the titan. While the titan ROMs boot just fine because of the almost exact HW, when installing those ROMS we don't get 4G and the speakers and earpeace, especially while calling, get unusable.
So instead of sitting on my butt and asking LUK to develop a 4G patch, can anyone guide me ? I know how to setup the SDK and know the theory about compiling from source but have never done it. Do we have to recompile something or can I just replace certain files with some other files from the (one and only) CM12.1 port for the THEA ?
This must be doable I think.
soulaiman said:
Hello XDA,
As all of you may know there is a 4G LTE version of the Moto G 2nd Generation, better known under the model number XT1072 and XT1079. Unfortunately almost all ROMs are created for the titan. While the titan ROMs boot just fine because of the almost exact HW, when installing those ROMS we don't get 4G and the speakers and earpeace, especially while calling, get unusable.
So instead of sitting on my butt and asking LUK to develop a 4G patch, can anyone guide me ? I know how to setup the SDK and know the theory about compiling from source but have never done it. Do we have to recompile something or can I just replace certain files with some other files from the (one and only) CM12.1 port for the THEA ?
This must be doable I think.
Click to expand...
Click to collapse
It's easy but I'm not going to help in dirty ports. Build roms from source instead, this is my recommendation.
If you want to learn how to build roms from source I can help you but you'll need to have Linux machine to do that.
LuK1337 said:
It's easy but I'm not going to help in dirty ports. Build roms from source instead, this is my recommendation.
If you want to learn how to build roms from source I can help you but you'll need to have Linux machine to do that.
Click to expand...
Click to collapse
Thanks for the reply Luk, I also think that building from source is the same. I have followed many, many guides but somehow the part where I have to point to the thea specific HW blobs fails. The extract-files.sh points to ./../../$VENDOR/msm8226-common/setup-makefiles.sh [email protected] wich I understand is the motorola folder in the WORKING_DIRECTORY. Somehow I can't find the right repo on github to point it at.
Sorry for the noobish Q... There is a first time for everything.
EDIT: I wanted to say that I think that porting from source is better, not the same.
soulaiman said:
Thanks for the reply Luk, I also think that building from source is the same. I have followed many, many guides but somehow the part where I have to point to the thea specific HW blobs fails. The extract-files.sh points to ./../../$VENDOR/msm8226-common/setup-makefiles.sh [email protected] wich I understand is the motorola folder in the WORKING_DIRECTORY. Somehow I can't find the right repo on github to point it at.
Sorry for the noobish Q... There is a first time for everything.
EDIT: I wanted to say that I think that porting from source is better, not the same.
Click to expand...
Click to collapse
You could use blobs from TheMuppets instead: https://github.com/TheMuppets/proprietary_vendor_motorola
LuK1337 said:
You could use blobs from TheMuppets instead: https://github.com/TheMuppets/proprietary_vendor_motorola
Click to expand...
Click to collapse
Thanks !!
I was really confused and got the CM12 branch instead the first time. Lol now I feel like a noob haha (wich I am when it comes to developing).
Will post here if I have any Questions/errors (that google can't help me with).
:good:
soulaiman said:
Thanks !!
I was really confused and got the CM12 branch instead the first time. Lol now I feel like a noob haha (wich I am when it comes to developing).
Will post here if I have any Questions/errors (that google can't help me with).
:good:
Click to expand...
Click to collapse
Also don't use git clone manually, make your local_manifests xml instead.
LuK1337 said:
Also don't use git clone manually, make your local_manifests xml instead.
Click to expand...
Click to collapse
Oh okay, I will look into that in a minute.
Now I got an issue that really got my head hurting... When I do the lunch command, my Moto G isn't in the list of devices... What Am I doing wrong ?
I have got a directory called thea in WORKING_DIRECTORY/device/moto/thea
I have got also an old thea directory (cm12.1) in WORKING_DIRECTORY/thea and WORKING_DIRECTORY/thea2
All the blobs from TheMuppits repo are in de device/moto/thea dir
All the poperiatary blobs are also in the XT907 dir...
I've done the
Code:
cd /device/moto/thea
init android-5.1.1_rx
repo sync
and let it finish without errors.
Once I get over this I will be good to go.
Oh, and thanks for sharing the knowledge !
soulaiman said:
Oh okay, I will look into that in a minute.
Now I got an issue that really got my head hurting... When I do the lunch command, my Moto G isn't in the list of devices... What Am I doing wrong ?
I have got a directory called thea in WORKING_DIRECTORY/device/moto/thea
I have got also an old thea directory (cm12.1) in WORKING_DIRECTORY/thea and WORKING_DIRECTORY/thea2
All the blobs from TheMuppits repo are in de device/moto/thea dir
All the poperiatary blobs are also in the XT907 dir...
I've done the
Code:
cd /device/moto/thea
init android-5.1.1_rx
repo sync
and let it finish without errors.
Once I get over this I will be good to go.
Oh, and thanks for sharing the knowledge !
Click to expand...
Click to collapse
Your directories are bit off, it should be looking like this.
CM/device/motorola/msm8226-common
CM/device/motorola/thea
CM/device/qcom/sepolicy
CM/device/qcom/common
CM/kernel/mototola/msm8226
CM/vendor/motorola
Don't forget about rest of CM source :3
LuK1337 said:
Your directories are bit off, it should be looking like this.
CM/device/motorola/msm8226-common
CM/device/motorola/thea
CM/device/qcom/sepolicy
CM/device/qcom/common
CM/kernel/mototola/msm8226
CM/vendor/motorola
Don't forget about rest of CM source :3
Click to expand...
Click to collapse
Oh okay got ya. Do I have to do some kind of refresh command when I touch the folders ?
soulaiman said:
Oh okay got ya. Do I have to do some kind of refresh command when I touch the folders ?
Click to expand...
Click to collapse
If you're building CM then all you have to do is to get vendor, do envsetup.sh and just brunch thea.
LuK1337 said:
If you're building CM then all you have to do is to get vendor, do envsetup.sh and just brunch thea.
Click to expand...
Click to collapse
I'm trying to build an AOSP build like yours to learn. I'm following this guide:
http://forum.xda-developers.com/chef-central/android/tutorial-compile-lollipop-ubuntu-t2929410
I guess it is similar in steps as what you described ?
Even with all the files in the correct directories when I exec the lunch command it doesn't list the moto G. See screenshot.
soulaiman said:
I'm trying to build an AOSP build like yours to learn. I'm following this guide:
http://forum.xda-developers.com/chef-central/android/tutorial-compile-lollipop-ubuntu-t2929410
I guess it is similar in steps as what you described ?
Even with all the files in the correct directories when I exec the lunch command it doesn't list the moto G. See screenshot.
Click to expand...
Click to collapse
You won't get clean AOSP to build, also u messed up directories as you put vendor in device.
If you have hangouts you can add me ( https://plus.google.com/108108436166506337243 ) so I could help you live.
LuK1337 said:
You won't get clean AOSP to build, also u messed up directories as you put vendor in device.
If you have hangouts you can add me ( https://plus.google.com/108108436166506337243 ) so I could help you live.
Click to expand...
Click to collapse
Thanks for all the help man, really appreciate it !
Yeah stupid fault of my part. Will try it.
About Hangouts: My hangouts app allways FC's on me so that will be for another day. I'll add you asap ! Thanks!
Also it is 1:45AM here so
soulaiman said:
Thanks for all the help man, really appreciate it !
Yeah stupid fault of my part. Will try it.
About Hangouts: My hangouts app allways FC's on me so that will be for another day. I'll add you asap ! Thanks!
Also it is 1:45AM here so [emoji14]
Click to expand...
Click to collapse
K, I'm in the same time zone fyi.
I was thinking: since we have an unlocked bootloader and custom roms, how hard would be to port AOSP Nougat?
There is any tecnical difficulty, like kernel version, that can block us?
Not much, I would imagine.
As far as I can tell, it'd just take a dev that's interested in putting in the effort.
Yes, this counts as my "yes, please" vote for Z00T.
I am votting with yes
I was thinking about do a try and compile it straight away, but i fear i'm not experienced enough to make something bootable
I don't think that the kernel or other thing will block it, but we got a custom ROM so late and I don't think we'll have a CM14 very soon
Cm14 should be prettt easy since we have cm 13, the point is that right now is not worth it because it's still in early stage, so a fully fledged cm13 would be more usefull.
AOSP is another talk because it's so barebone
Jhyrachy said:
Cm14 should be prettt easy since we have cm 13, the point is that right now is not worth it because it's still in early stage, so a fully fledged cm13 would be more usefull.
AOSP is another talk because it's so barebone
Click to expand...
Click to collapse
Umm, thanks for your thoughts about trying to bring N, it seem you got the answer yourself
from what i look at Z00L/T source, other than some fix and caf one, they could bring N to L/T with some borrowed libs. And looking from our source, I still found some line with L/T on it, so, yes, dev may bring N to this device, just hope that libs going to work with this devices.
But as you said, a fully fledged cm13 would be useful, using RR build for 3 days, and got the problem as they says. Plus, for me, front camera isn't working (called arclib or something, front camera effect when using asus camera, it's working fine with other camera because they didn't load that lib). Constant lag when using GPS other than "gps only" (might RR only problem). etc..
Either way, I hope that you could join the team (or, is he a one man army?) maintaining this device, fixing things come first, upgrade when everything is fine. At least "ok".
I don't know about AOSP, but many say choose CM because of CM broad compatibility layer. If that's true, then AOSP might slightly harder...
or... not really.
Sent from my ASUS_Z00RD using XDA Labs
Interesting, I'm not developer but I think this is possibke, Android 7.0 supports S410, maybe CM14 will better than AOSP.
yeah i still waiting ??
Sent from my ASUS_Z00ED using Tapatalk
Who wants to test BeanStalk 6.25 for Z00RD/Z00E?
imjohncarlo9 said:
Who wants to test BeanStalk 6.25 for Z00RD/Z00E?
Click to expand...
Click to collapse
I, but it will be possible tonight because now i working , phone at home
imjohncarlo9 said:
Who wants to test BeanStalk 6.25 for Z00RD/Z00E?
Click to expand...
Click to collapse
i will try tomorrow ...good for this ??
Sent from my ASUS_Z00ED using Tapatalk
Some news?
waiting :victory:
Waiting for some USEFUL news.
Today I try to compile it, but do not know if I aim, because I'm not a developer and I have no experience, but I try the same, stay connected, sorry for my bad english
I can't download the sources because it me give an errore i can't compile a ROM,sorry
Still waiting for news.
I tried to compile it myself, I downloaded all the sources, but since the Z00ED / RD is not officially supported by CyanogenMod, and then the repository and everything else must be manually added, I tried but I get error during compilation. Now we must wait for some developer is able to have time to complete it, because basically if you have created for the Z00L / Z00T do not see why you can not fill because they have the same processor. Sorry for my bad English
kurnalcool said:
I tried to compile it myself, I downloaded all the sources, but since the Z00ED / RD is not officially supported by CyanogenMod, and then the repository and everything else must be manually added, I tried but I get error during compilation. Now we must wait for some developer is able to have time to complete it, because basically if you have created for the Z00L / Z00T do not see why you can not fill because they have the same processor. Sorry for my bad English
Click to expand...
Click to collapse
Hi! Could this help you in some way? I don't know how, but I hope there is something usefull. This is a link to a russian forum where CM13 for ZE500KL was first posted by his original creator. Is in russian but I think you can use google translate to read the forum http://4pda.ru/forum/index.php?showtopic=766921