Database Develop

[ROM] Perf Tweaked Rom Build 1 by DJ_Steve

I take no credit for this, just passing information on for others to use. YMMV, use at your own risk..
roebeet pointed this out in irc;
SOURCE: http://notioninkhacks.com/forums/viewtopic.php?f=29&t=891
by StephenH » Wed Feb 16, 2011 1:58 pm
ok folks im hoping people can test this for me,
just built a new build (my first for the adam) based on the newest official 2.2 build but with some interesting tweaks
NOTE: i am a dev working for NI especially on honeycomb soon, but these roms are my own.
changelog:
New Kernel with NTFS support, android does not mount this by default but you can mount it via adb read only. (kernel has rw support but i couldnt get it to mount a ext drive rw)
Kernel has few other tweaks and changes and doesn seem to die when sleeping either now
performance tweaks (minor ones) made to the os itself
full google apps added (untested )
ability to disable ril/phone features to conserve battery (see below for info)
adhoc wifi courtesy of the update posted on this site previously
disabled some of the logspam that was enabled but isnt needed
boot.img is first stage prepped for honeycomb
install instructions
download the file linked below and copy to either sd or your adams internal memory and flash as normal
download:
Code:
Please refer to original post linked above for download link
RIL Disabling Information
ok this is a creative feature. all adams be them 3g or wifi only versions keep thje phone related applications and services running in the background and on the wifi only adams this causes a higher battery drain due to system constantly trying to connect to a network, i have implemented a way to disable this by setting a simple property in the system
to do this you need to edit the /system/build.prop file and change the mentioned line to 1 instead of 0 then reboot
if that doesn work then try the below route
open a terminal and run the following command then reboot
Code:
setprop persist.ril-off 1
Click to expand...
Click to collapse

I am amazed by the lack of discussion about this. I wonder if this Stephen fella can let that kernel out...
Sent from my ADR6300 using XDA App

football0552 said:
I am amazed by the lack of discussion about this. I wonder if this Stephen fella can let that kernel out...
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
It is probably because there aren't very many Adam users yet.

keitht said:
It is probably because there aren't very many Adam users yet.
Click to expand...
Click to collapse
Yeah I think there are very very few adam owners out in the wild. Might be a decent bump after this next delivery round next week.
And NI has not officially released their kernel source and from my discussions with them I wouldn't expect it real soon. I did however explain to them that it will have to be eventually so I think they might be working on it.

rothnic said:
Yeah I think there are very very few adam owners out in the wild. Might be a decent bump after this next delivery round next week.
And NI has not officially released their kernel source and from my discussions with them I wouldn't expect it real soon. I did however explain to them that it will have to be eventually so I think they might be working on it.
Click to expand...
Click to collapse
They don't seem so keen on sharing huh? Interesting since they like to use other people's open source code...
Guess I will have to join in and start hounding them about it.
Sent from my ADR6300 using XDA App

keitht said:
It is probably because there aren't very many Adam users yet.
Click to expand...
Click to collapse
I second that. Am a fervent flasher (the right kind....) and when I get my Adam I will certainly be putting my own 2 cents in to get the most out of it, both OS and UI wise.
I am not alone, so definitely expect a flury of activity by Adam enthousiasts once the next 2 batches are delivered.
Sent from my HTC Desire using XDA App

You guys are lucky to have djsteve as your new Dev. He's put in a lot of work for the Dell Streak since it first came out and he will probably put in a lot of work for the Adam ink as well.
football0552 said:
I am amazed by the lack of discussion about this. I wonder if this Stephen fella can let that kernel out...
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Sent from my Dell Streak using XDA App

I get mine tommorrow so I'm very excited.. will def try this
sent from gv1.5 on g2

Update: 10/03/2011:
UPDATE: 10/03/2011:
time for another update
changelog:
reverted vold change as it screws up things
added some more perf tweaks,
added data2ext script from gtab forum on xda, seems to work nicely, can hit quadrant scores of ~3200 now
flash you will need to install yourself at moment, i forgot to readd it link for flash : http://forum.xda-developers.com/showpos ... stcount=26
Code:
refer to original thread/forum for download links
enjoy folks and if anyone wants to do another video feel free.
---------------
UPDATE: 17/02/2011:
ok have tweaked a bit more and made a few more changes.
changelog:
new vold added with ntfs mount support (see below for some issues known with this)
flash player added and should auto install
fixed market and facebook
fixed superuser ability
added estrongs file manger for root use
tweaked the ril scripts to be easier to use.
added modified nvrm_daemon to increase 2d framerate
Code:
refer to original thread/forum for download links
*note for VOLD, this now mounts ntfs drives read only, but it has slightly screwed up the mounts, if you power up device with no microsd plugged in it will mount the internal storage and allow access to is via usb, if you plug in a microsd or boot with one in it will mount both internal and external sds but share the external over usb, it quite happily detects and mounts my 1tb usb hdd which is ntfs formatted though now.
ril tweaks: now all you need to do is create a empty file on your memory card called riloff.txt then reboot and script should do the rest to reenable rename the file rilon.txt and reboot
enjoy folks and if anyone wants to do another video feel free.
-----------------------
ok folks im hoping people can test this for me,
just built a new build (my first for the adam) based on the newest official 2.2 build but with some interesting tweaks
NOTE: i am a dev working for NI especially on honeycomb soon, but these roms are my own.
changelog:
New Kernel with NTFS support, android does not mount this by default but you can mount it via adb read only. (kernel has rw support but i couldnt get it to mount a ext drive rw)
Kernel has few other tweaks and changes and doesn seem to die when sleeping either now
performance tweaks (minor ones) made to the os itself
full google apps added (untested )
ability to disable ril/phone features to conserve battery (see below for info)
adhoc wifi courtesy of the update posted on this site previously
disabled some of the logspam that was enabled but isnt needed
boot.img is first stage prepped for honeycomb
install instructions
download the file linked below and copy to either sd or your adams internal memory and flash as normal
Code:
refer to original thread/forum for download links
RIL Disabling Information
ok this is a creative feature. all adams be them 3g or wifi only versions keep thje phone related applications and services running in the background and on the wifi only adams this causes a higher battery drain due to system constantly trying to connect to a network, i have implemented a way to disable this by setting a simple property in the system
to do this you need to edit the /system/build.prop file and change the mentioned line to 1 instead of 0 then reboot
if that doesn work then try the below route
open a terminal and run the following command then reboot
Code:
setprop persist.ril-off 1
Last edited by StephenH on Thu Mar 10, 2011 6:15 pm, edited 2 times in total.
Click to expand...
Click to collapse

[WIP] Ubuntu on G9 v0.2

Hey guys,
let's try to get Ubuntu working on our tablets.
adbd is included in the images, so you have a root shell over adb
SDE required.
Extract all.
adb push ubu1204.img.ext4 /data/media/
Reboot - SDE - Flash kernel and initrd
Multiboot menu 0.3 - ubu1204.img.ext4 (from the menu to start the ICS, such as "archos.ext4")
Done.
(passwords: ubuntu - ubuntu root - root)
Working:
- Booting on 80G9 and 101G9
- Touchscreen (touchpad mode)
- Keyboard via OTG cable
- Mass storage on rear USB-prt
- SD card automount on plugin
- LCD backlight brightness control via command line, lol
- Networking (incl. WiFi)
Changelog:
0.2:
- Made by szanalmas
- Upgrade to 12.04
- Kernel 3.0.8+
- Working WiFi (try adding a dummy network, then it works), Sound
- Switched from Unity to Gnome Classic
0.1:
- Initial build.
Todo:
- Bluetooth
- Hardware acceleration
- Camera
- Battery
Download v0.2:
Image: Download
SHA: View
Kernel: Download
SHA: View
Download v0.1:
sysroot_ice.img http://hotfile.com/dl/145362762/7e3f710/ubuntu.img.rar.html MD5:2d9dbc775820db5dda281df84ab7db64
initramfs.cpio.gz http://hotfile.com/dl/145366156/8c56f1d/initramfs.cpio.gz.html MD5:150fc53be381ac3247d44226061868af
zImage http://hotfile.com/dl/145366657/34f75c7/zImage.html MD5:4de6efeec193aa5809f2ff871a96ef2d
Thanks to
- szanalmas for upgrade to 12.04, kernel 3.0.8+, WiFi
- letama for provided kernel + initramfs
- trevd for testing on 101G9 and reuploading stuff
- Adam / OPPO

great a1Pha !
but i would like ubuntu and ICE.. (lol)

This can be made. I'll have to check the initramfs tomorrow

Upload done, post edited - have fun @ testing

a1Pha said:
This can be made. I'll have to check the initramfs tomorrow
Click to expand...
Click to collapse
thx , i testing that this morning

wow. I was going to get working on this when my tablet arrives but you beat me to the race.. maybe we can work on it together in the future

Could you post some screenshots of ubuntu on g9?

dual boot
how would you go about dual bopoting i want to get into the whole programming of it just need a pointer to the start of things

TjaXanK said:
wow. I was going to get working on this when my tablet arrives but you beat me to the race.. maybe we can work on it together in the future
Click to expand...
Click to collapse
For sure - just contact me when your tablet has arrived
142857 said:
Could you post some screenshots of ubuntu on g9?
Click to expand...
Click to collapse
Okay, I have edited the first post and added some links to screenshots.
twinnaz said:
how would you go about dual bopoting i want to get into the whole programming of it just need a pointer to the start of things
Click to expand...
Click to collapse
Sorry, I don't understand your question :S

how would i implement a dualboot

You can take the initramfs.cpio.gz posted by letama in another thread (look at the link to Ice Cream Sandwich - the file is inside the archive you download).
Then extract it and have look at the scripts, which are provided there.
Basically you have to get the system to ask you, from which filesystem image you want to boot

yep! you need to install SDE, restart your device, go in the developer menu and flash the initramfs.cpio.gz that letama posted in the ICS post, atleast that's how it was in the Gen8... by the looks of it the SDE menu is the same. Hope I helped

i wait the multi OS install
2.3
4.0
Ubuntu

Nice, I'll give this a go now.
Edit:
Works on the 101G9.
Keyboard Functions through OTG/Host Cable.
USB Mass Storage (Pen Drive) Functions on 3G Stick Port
Not tried anything else yet.
Are you using a lot of the same kernel objects which android is using?
Excellent Work.

alright thanks

trevd said:
Works on the 101G9.
Keyboard Functions through OTG/Host Cable.
USB Mass Storage (Pen Drive) Functions on 3G Stick Port
Are you using a lot of the same kernel objects which android is using?
Click to expand...
Click to collapse
Thank you very much, and also thanks for testing
I am using initramfs + kernel + modules provided by letama for his ICS-build.
By the way - I will upload a new build this night.
I have managed to get basic network functionality via adb + usbcable, so I have upgraded all packages and installed a touchscreen keyboard.
In the new build the LCD backlight brightness is now set to max on boot.
I also have added a user with sudo-permissions, so now settings are saved on reboot (not like in 0.1 where guest sessions were created).
Oh, and I will change the filesystem type from ext3 to ext4.
Still no real progress on WiFi or sound
P.S.: New build will support choosing between booting ICS and Ubuntu
//edit: sry guys, got some problems with my internet provider. i get reconnects every 30 seconds. i hope they get it fixed till tomorrow... sorry for delay, i'm going to upload the stuff tomorrow..

a1Pha said:
Thank you very much, and also thanks for testing
I am using initramfs + kernel + modules provided by letama for his ICS-build.
Click to expand...
Click to collapse
Might be worth giving it a go with a version 3 kernel, you may get some free driver support. although I could be talking nonsense
a1Pha said:
By the way - I will upload a new build this night.
I have managed to get basic network functionality via adb + usbcable, so I have upgraded all packages and installed a touchscreen keyboard.
In the new build the LCD backlight brightness is now set to max on boot.
I also have added a user with sudo-permissions, so now settings are saved on reboot (not like in 0.1 where guest sessions were created).
Oh, and I will change the filesystem type from ext3 to ext4.
Click to expand...
Click to collapse
I activated the root login with my own password from adb and the touchscreen keyboard worked straight away on the 101. It must come with the the drivers preinstalled. I think letma's' done some work into the difference between the 80 and 101.
a1Pha said:
Still no real progress on WiFi or sound
Click to expand...
Click to collapse
I've been playing with this all night. I think the drivers have been integrated in the main linux kernel so you should be able to build your own.
They could some prebuilt binaries out there as the OMAP4 board seems quite a popular board.
Also you might have some joy with this http://dev.omapzoom.org/pub/scm/integration/
It's all Good!
Archos 101 G9, HTC Sensation, HTC Hero

Hi Guys,
A1Pha, sorry, didn't have time to test your build, too much stuff going on...
Here is a quick feedback on wifi that may help you:
In android, here is how it works (from memory, don't have my laptop to check)
1) you need to create a nvs file corresponding to tablet, check android init.rc for the way it's done there...
2) Then when you do need wifi, insmod the tiwlan.ko
3) Then, load firmware (check wlan_loader in android init.rc, you should be able to reuse the command) and nvs. If all goes well up to here, you should be able to do ifconfig tiwlan0 and it should have a mac address.
4) Then start wpa_supplicant. You need the appropriate version of wpa_supplicant, 0.8 I think in android source code. You may want to build source code from android source with the appropriate options to remove android extensions.
Again, this is from memory, I'll try to give you more details tomorrow.
Regarding audio, this is mostly alsa so it shouldn't be impossible, you should be able to re-use the configuration found in archos rootfs in /usr/ sub directories. You have to insmod the proper modules though.
Best,
LeTama

Suggestion for the sound, try running the alsamixer and playing with that... worked in debian...

letama said:
Hi Guys,
A1Pha, sorry, didn't have time to test your build, too much stuff going on...
Here is a quick feedback on wifi that may help you:
In android, here is how it works (from memory, don't have my laptop to check)
.....
Click to expand...
Click to collapse
ahh. Thanks for that letama , You're a fountain of knowledge.
I'll give it a try during the holidays.
I was playing about with wpa_supplicant and android kernel drivers. I didn't have the right magic ) and my kernel knowledge is still in it's early stages (only been on the linux desktop for 1 year).

[celoxhd][SGH-I757M][CWM Advanced Edition] PhilZ Touch

Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
celoxhd
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
Original dev supporter:
http://www.androidfilehost.com/?w=files&flid=12461
Click to expand...
Click to collapse
Huge thanks and credits to @titanic_fanatic
He ported the sources and provided all needed stuff to build it

Excellent, many thanks for all the work you put into this for us. We very much appreciate it
On the topic of bugs, I only have two (but I really don't mind at all). The screenshot works except for the resulting image is wavy coloured lines and no vibration regardless of the setting.
We've never had either, so I'm not missing them at all, but wanted to let you know.
Take care Phil
Sent from my SGH-I757M using XDA Premium 4 mobile app

titanic_fanatic said:
Excellent, many thanks for all the work you put into this for us. We very much appreciate it
On the topic of bugs, I only have two (but I really don't mind at all). The screenshot works except for the resulting image is wavy coloured lines and no vibration regardless of the setting.
We've never had either, so I'm not missing them at all, but wanted to let you know.
Take care Phil
Sent from my SGH-I757M using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Added you to credits on the device page in main thread and here in OP :good:
screen shots: forget it, I should disable it once for all on new devices. Sadly, we have no working thing for most new devices. Only some Sammy and the mako did work
vibration: can you provide the path for vibrator?, it should be in kernel drivers I guess. Currently I use:
Code:
/sys/class/timed_output/vibrator/enable
We echo some msec value there and it Bzzzzz for that msec

Phil3759 said:
Added you to credits on the device page in main thread and here in OP :good:
screen shots: forget it, I should disable it once for all on new devices. Sadly, we have no working thing for most new devices. Only some Sammy and the mako did work
vibration: can you provide the path for vibrator?, it should be in kernel drivers I guess. Currently I use:
Code:
/sys/class/timed_output/vibrator/enable
We echo some msec value there and it Bzzzzz for that msec
Click to expand...
Click to collapse
That's the correct path Maybe the driver isn't loading properly... I'll see if I can get a dmesg Log when booting recovery to see if the driver actually loads
Sent from my SGH-I757M using XDA Premium 4 mobile app

Vibrator Fixed
Hey @Phil3759, I did a whole lot of investigating tonight and have figured out and fixed the vibration issue. I discovered that it was trying to load the module from /system/lib/modules/vibrator.ko. This is my roms ko file and is currently for cm10.2. The kerenel I setup for this recovery is our cm11 kernel and uses a different module (compiled against that kernel). It was trying to load the cm10.2 module from my rom into the cm11 kernel which obviously doesn't work, so I split the recovery.img added the correct module at /tmp/system/lib/modules added the necessary lines to init.recovery.qcom.rc and repackaged the kernel and new ramdisk.
I have flashed this and tested it. it works like a charm now Can you replace the version in your repo with this new one?

titanic_fanatic said:
Hey @Phil3759, I did a whole lot of investigating tonight and have figured out and fixed the vibration issue. I discovered that it was trying to load the module from /system/lib/modules/vibrator.ko. This is my roms ko file and is currently for cm10.2. The kerenel I setup for this recovery is our cm11 kernel and uses a different module (compiled against that kernel). It was trying to load the cm10.2 module from my rom into the cm11 kernel which obviously doesn't work, so I split the recovery.img added the correct module at /tmp/system/lib/modules added the necessary lines to init.recovery.qcom.rc and repackaged the kernel and new ramdisk.
I have flashed this and tested it. it works like a charm now Can you replace the version in your repo with this new one?
Click to expand...
Click to collapse
If you update your device tree, it would be even better. That way, my next updates won't be affected again

Phil3759 said:
If you update your device tree, it would be even better. That way, my next updates won't be affected again
Click to expand...
Click to collapse
I just finished updating my device tree with the necessary fixes for the vibrator to work in recovery
https://github.com/titanic-fanatic/android_device_samsung_celoxhd/commit/6f005f4045551e48adfa0ac228641bf8d6a12128
Also, not that I care, but Amarullz was able to get screenshots working in the latest AromaInstaller (Flamboyan I think). If your interested, maybe ask him what he did to get it to work. He could probably point you to the commits
Take Care

titanic_fanatic said:
I just finished updating my device tree with the necessary fixes for the vibrator to work in recovery
https://github.com/titanic-fanatic/...mmit/6f005f4045551e48adfa0ac228641bf8d6a12128
Also, not that I care, but Amarullz was able to get screenshots working in the latest AromaInstaller (Flamboyan I think). If your interested, maybe ask him what he did to get it to work. He could probably point you to the commits
Take Care
Click to expand...
Click to collapse
Looking at it quickly: why that first extra / at end of copy files?
Also, won't be cleaner to use standard path like /lib/modules?
/tmp can be wiped and modified by installers and recovery

Phil3759 said:
Looking at it quickly: why that first extra / at end of copy files?
Also, won't be cleaner to use standard path like /lib/modules?
/tmp can be wiped and modified by installers and recovery
Click to expand...
Click to collapse
The first / is because it's part of a set of chained product copy files directives:
# Ramdisk
PRODUCT_COPY_FILES += \
device/samsung/celoxhd/ramdisk/init.qcom.usb.rc:root/init.qcom.usb.rc \
# BT firmware
PRODUCT_COPY_FILES += \
device/samsung/celoxhd/firmware/bcm4330B1.hcd:system/etc/firmware/bcm4330B1.hcd \
# Needed for vibrator to work in recovery
PRODUCT_COPY_FILES += \
device/samsung/celoxhd/recovery/root/lib/modules/vibrator.ko:recovery/root/lib/modules/vibrator.ko \
device/samsung/celoxhd/recovery/root/init.recovery.qcom.rc:recovery/root/init.recovery.qcom.rc
Click to expand...
Click to collapse
I did this only to adhere to the existing pattern in my device.mk file, the one appended to the first PRODUCT_COPY_FILES was already there from when I forked the project and took that as being a set of chained commands. If this is wrong, I will change it
I definitely see your point on the /tmp dir. I here the commit that fixes that
https://github.com/titanic-fanatic/android_device_samsung_celoxhd/commit/61da6be2d60a03797ddc31c0187cc5c62bb3a97a

titanic_fanatic said:
The first / is because it's part of a set of chained product copy files directives:
I did this only to adhere to the existing pattern in my device.mk file, the one appended to the first PRODUCT_COPY_FILES was already there from when I forked the project and took that as being a set of chained commands. If this is wrong, I will change it
I definitely see your point on the /tmp dir. I here the commit that fixes that
https://github.com/titanic-fanatic/android_device_samsung_celoxhd/commit/61da6be2d60a03797ddc31c0187cc5c62bb3a97a
Click to expand...
Click to collapse
I uploaded 6.01.2 with your fixed vibrator :good:
PRODUCT_COPY_FILES:
Maybe I am wrong, but usually, in make files, only the last element has no trailing /
Code:
# Ramdisk
PRODUCT_COPY_FILES += \
device/samsung/celoxhd/ramdisk/init.qcom.usb.rc:root/init.qcom.usb.rc
xxx-yyy \
zzz-pppp\
last_one
# BT firmware
PRODUCT_COPY_FILES += \
device/samsung/celoxhd/firmware/bcm4330B1.hcd:system/etc/firmware/bcm4330B1.hcd
# Needed for vibrator to work in recovery
PRODUCT_COPY_FILES += \
device/samsung/celoxhd/recovery/root/tmp/system/lib/modules/vibrator.ko:recovery/root/tmp/system/lib/modules/vibrator.ko \
device/samsung/celoxhd/recovery/root/init.recovery.qcom.rc:recovery/root/init.recovery.qcom.rc
Also, just for info, my full gui builds need these, often in cm.mk:
Code:
TARGET_SCREEN_HEIGHT := 1280
TARGET_SCREEN_WIDTH := 720

Phil3759 said:
I uploaded 6.01.2 with your fixed vibrator :good:
PRODUCT_COPY_FILES:
Maybe I am wrong, but usually, in make files, only the last element has no trailing /
Code:
# Ramdisk
PRODUCT_COPY_FILES += \
device/samsung/celoxhd/ramdisk/init.qcom.usb.rc:root/init.qcom.usb.rc
xxx-yyy \
zzz-pppp\
last_one
# BT firmware
PRODUCT_COPY_FILES += \
device/samsung/celoxhd/firmware/bcm4330B1.hcd:system/etc/firmware/bcm4330B1.hcd
# Needed for vibrator to work in recovery
PRODUCT_COPY_FILES += \
device/samsung/celoxhd/recovery/root/tmp/system/lib/modules/vibrator.ko:recovery/root/tmp/system/lib/modules/vibrator.ko \
device/samsung/celoxhd/recovery/root/init.recovery.qcom.rc:recovery/root/init.recovery.qcom.rc
Also, just for info, my full gui builds need these, often in cm.mk:
Code:
TARGET_SCREEN_HEIGHT := 1280
TARGET_SCREEN_WIDTH := 720
Click to expand...
Click to collapse
It seems that the extra \ was introduced in our JB branch and has never been fixed. Various examples in googles repo confirm that you are correct. I have removed the extra \ and added the properties you mentioned above to the cm.mk file. Here is the relevant commit:
https://github.com/titanic-fanatic/android_device_samsung_celoxhd/commit/6ce5f482d63cd70cf64a3d1428ad2428844e23cb

Hey @Phil3759, I just downloaded and flashed the latest version. Thanks kindly for the update
I see that I made a boo boo and forgot to update the path to the vibrator in the init.recovery.qcom.rc file and so the vibrator isn't loading. I've fixed that with the following commit:
https://github.com/titanic-fanatic/android_device_samsung_celoxhd/commit/b87b3267d75a0de1bb94f68850ae6986ac4dde92
One other thing, for some reason the background is tiled 4 times as if my devices dimensions were not set correctly. I do have that set in my cm.mk file. Here was the commit for that:
https://github.com/titanic-fanatic/android_device_samsung_celoxhd/commit/6ce5f482d63cd70cf64a3d1428ad2428844e23cb
Is there somewhere else I'm supposed to specify the device screen dimensions?
Thanks again for the new version and I apologize for missing that path in the init.recovery.qcom.rc.

titanic_fanatic said:
Hey @Phil3759, I just downloaded and flashed the latest version. Thanks kindly for the update
I see that I made a boo boo and forgot to update the path to the vibrator in the init.recovery.qcom.rc file and so the vibrator isn't loading. I've fixed that with the following commit:
https://github.com/titanic-fanatic/android_device_samsung_celoxhd/commit/b87b3267d75a0de1bb94f68850ae6986ac4dde92
One other thing, for some reason the background is tiled 4 times as if my devices dimensions were not set correctly. I do have that set in my cm.mk file. Here was the commit for that:
https://github.com/titanic-fanatic/android_device_samsung_celoxhd/commit/6ce5f482d63cd70cf64a3d1428ad2428844e23cb
Is there somewhere else I'm supposed to specify the device screen dimensions?
Thanks again for the new version and I apologize for missing that path in the init.recovery.qcom.rc.
Click to expand...
Click to collapse
About background image:
I think this is the cause:
https://github.com/CyanogenMod/android_device_samsung_celox-common/blob/cm-11.0/celox-common.mk#L45
called here:
https://github.com/titanic-fanatic/...xhd/blob/philz-recovery-cm-11.0/device.mk#L37
Your cm.mk settings are overridden
Maybe just move device resolution from cm.mk to device.mk after Line 37
About the vibrator: do you need exfat through kernel modules? If yes, let me know. It is much faster than fuse. For that, you'll need to compile the kernel with samsung exfat sources. I can guide you for that
Else, link me to what exactly is needed in your kernel for the vibrator to work. If it is just a change in defconfig, I can add it and compile along exfat

Phil3759 said:
About background image:
I think this is the cause:
https://github.com/CyanogenMod/android_device_samsung_celox-common/blob/cm-11.0/celox-common.mk#L45
called here:
https://github.com/titanic-fanatic/...xhd/blob/philz-recovery-cm-11.0/device.mk#L37
Your cm.mk settings are overridden
Maybe just move device resolution from cm.mk to device.mk after Line 37
About the vibrator: do you need exfat through kernel modules? If yes, let me know. It is much faster than fuse. For that, you'll need to compile the kernel with samsung exfat sources. I can guide you for that
Else, link me to what exactly is needed in your kernel for the vibrator to work. If it is just a change in defconfig, I can add it and compile along exfat
Click to expand...
Click to collapse
I see it, and now as you've recommended I reset the values after calling celox-common.mk. The commit is here:
https://github.com/titanic-fanatic/android_device_samsung_celoxhd/commit/cd44b44b7cbb0ddb3b649ac5c4f8d5d1f51d7998
As for exfat, I will be adding this when I have some time to rebuild this kernel. We can worry about exfat for the next time you do device updates and hopefully I'll have it ready by that time. I have your main thread in my subscriptions, so I'll know when your ready to release a new version and will remind you to sync with my repo at that time
Thanks for catching that issue with screen size

titanic_fanatic said:
I see it, and now as you've recommended I reset the values after calling celox-common.mk. The commit is here:
https://github.com/titanic-fanatic/android_device_samsung_celoxhd/commit/cd44b44b7cbb0ddb3b649ac5c4f8d5d1f51d7998
As for exfat, I will be adding this when I have some time to rebuild this kernel. We can worry about exfat for the next time you do device updates and hopefully I'll have it ready by that time. I have your main thread in my subscriptions, so I'll know when your ready to release a new version and will remind you to sync with my repo at that time
Thanks for catching that issue with screen size
Click to expand...
Click to collapse
np
Let me know if you need info to add exfat
I will update with the current fixes asap

Phil3759 said:
np
Let me know if you need info to add exfat
I will update with the current fixes asap
Click to expand...
Click to collapse
Can I get a link to these fixes please when you have it ready

titanic_fanatic said:
Can I get a link to these fixes please when you have it ready
Click to expand...
Click to collapse
https://github.com/PhilZ-cwm6/GE-Ed...mmit/a8963ca853cfd88466716f8a25434d5c469a2bb9
It is just adding the exfat folder in drivers and edit the makefile with -y to have it built as static. No need to separate modules

Phil3759 said:
https://github.com/PhilZ-cwm6/GE-Ed...mmit/a8963ca853cfd88466716f8a25434d5c469a2bb9
It is just adding the exfat folder in drivers and edit the makefile with -y to have it built as static. No need to separate modules
Click to expand...
Click to collapse
Excellent. I'll add it soon, it should be a pretty quick process.
Quick question though since we are currently having some issues with random reboots in all of my latest builds of cm-11.0. My kernel was updated at some point, and that's when my builds started having random reboots. They are actually not random, but seem rather consistent.
My question is this, do you think this will affect operation in recovery? I believe the reboots are due to kernel panic from a graphics related issue but am not sure if that will only affect the rom and not recovery.
If this might affect recovery, I think I'll build it as a module so I can just add it to my device tree instead of having to update the entire zImage. This will at least give us the old working kernel with the exfat module included.
What do you think?
Sent from my SGH-I757M using XDA Premium 4 mobile app

titanic_fanatic said:
Excellent. I'll add it soon, it should be a pretty quick process.
Quick question though since we are currently having some issues with random reboots in all of my latest builds of cm-11.0. My kernel was updated at some point, and that's when my builds started having random reboots. They are actually not random, but seem rather consistent.
My question is this, do you think this will affect operation in recovery? I believe the reboots are due to kernel panic from a graphics related issue but am not sure if that will only affect the rom and not recovery.
If this might affect recovery, I think I'll build it as a module so I can just add it to my device tree instead of having to update the entire zImage. This will at least give us the old working kernel with the exfat module included.
What do you think?
Sent from my SGH-I757M using XDA Premium 4 mobile app
Click to expand...
Click to collapse
you'll end up with magic number mismatch errors
There are some hacks to force loading on mismatch, but, in my previous experience, they failed on many devices
the drivers must be compiled along the zImage
Now, why don't we drop to celox-common kernel which seems to work fine on skyrocket and other phones?

Phil3759 said:
you'll end up with magic number mismatch errors
There are some hacks to force loading on mismatch, but, in my previous experience, they failed on many devices
the drivers must be compiled along the zImage
Now, why don't we drop to celox-common kernel which seems to work fine on skyrocket and other phones?
Click to expand...
Click to collapse
It is for the most part the same kernel with the few quirks of my device. More notably is my devices display drivers are mipi s6e8aa0_720hd and had to fork the kernel to apply some fixes to that driver as it's not maintained by cm.
Hmmm. I'll be the guinea pig. I will build with the new kernel and I'll test the recovery before you upload. I just think that the issue might be a memory leak in android causing the kernel to panic (overlay issue) and might not have an effect in recovery since its graphics are very basic.
I'll let you know when it's ready
Sent from my SGH-I757M using XDA Premium 4 mobile app

[moto_msm8960][CWM Advanced Edition] PhilZ Touch 6.xx.* and upwards.

Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
Click to expand...
Click to collapse
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Addendum: Unified builds, in particular this one for moto_msm8960 devices:
Supposed list of unified devices: Previous RAZR HD, Photon Q, Atrix HD, etc. : xt897, xt901, xt905, xt907, xt905, xt925, xt926, mb886 are now:
Now: moto_msm8960
I'm going to put them in a list so I can get around to checking Y on known working ones, and N on known non-working ones:
- xt926 (Y)
- xt925 (Y)
- mb886 (Y)
- xt897 (Y)
- xt901 (?)
- xt905 (?)
- xt907 (Y)​
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Quick notes about unified devices:
Do they all work in this build? I have no idea, but am pretty sure that from feedback that xt926/5, xt907 and xt897 have been reported to work.
The bottom line is that I rely on anyone reading here (or who is directed here from their development pages) to let me know what works, what doesn't so please let me know.
----------------------------
Download links
Latest versions built by me can be found here: (currently 6.xx.* and up).
Note: 6.58.7 final/stable is the latest (see the main development thread if not understood)
Changelogs:
v6.58.7 - new code and fixes
Click to expand...
Click to collapse
6.43.6 (02.06.2014)
- fix recursive path creation bug for /data/media/0
- default to /data/media/0 unless we define BOARD_HAS_NO_MULTIUSER_SUPPORT
- use lstat to check if file exists
6.43.4 - Final, Stable
- fix text print color could persist after md5 check
6.42.9 - Final & Stable
- default again to libtar for backup/restore
6.42.7 - Stable
- default to busybox tar:
- use busybox tar by default as it now supports selinux context backup/restore
- unify libtar and busybox tar options (-p for selinux context)
- remove now deprecated external selinux container code
6.41.6 - Stable & perhaps Final
- update exfat to dorimanx 1.2.9 latest sources
- fix compile error when enabling BOARD_RECOVERY_USE_BBTAR
- repo sync latest sources
- Galaxy Tab Pro 8.4 WiFi SM-T320 (mondrianwifi)
- HTC M7 variants: use new cm kernel with exfat sources
- HTC M8 variants: use new unified recovery
6.41.5 - Stable
- libtouch_gui 1.21: auto detect BRIGHTNESS_SYS_FILE path if it is not set during compile
* search for the file in most common locations
* if found, save it to recovery settings ini file to be called on next recovery starts
* else, disable adjust brightness function to avoid error logs on recovery start
- fix various compiler warnings and errors
- enhance pre-compile setup
- dedupe: merge clean up code from @xiaolu
- merge: fix restorecon_from_file potential crash from @xiaolu (only for BOARD_RECOVERY_USE_BBTAR)
- fix 240x320 images
- merge "cwm: Honor recovery variant "
- merge "cwm: Remove hardcoded paths"
- merge "Keep 'show log' on screen until user dismisses it"
- create /data/media directory after internal storage is wiped
prevents denial to read/write from internal storage under some circumstances
- open source touch_gui library
- update licence files
Click to expand...
Click to collapse
- Unified msm8960: 6.58.7 (4.4.4): Image : http://d-h.st/2xD
- v6.43.6: Unified msm8960: http://d-h.st/HgH
- v6.43.4: Unified msm8960: http://d-h.st/sQQ
- v6.42.9: Unified msm8960: http://d-h.st/SjY
- v6.42.7: Unified msm8960: http://d-h.st/9pD
- v6.41.6: Unified msm8960: http://d-h.st/uq1
- v6.41.5: Unified msm8960: http://d-h.st/QiK
Click to expand...
Click to collapse
Note: tested only on my xt926. Aroma has a few little glitches but is not often maintained.
Older versions built by Phil (or his 'crew'):
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/xt926 // oldest (and substitute your dev name for pre-unified builds)
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/moto_msm8960 // newer, recent.
Click to expand...
Click to collapse
My github(just created/work-in-progress) for tracking changes on this: https://github.com/Hachamacha/philz.git
Click to expand...
Click to collapse
Note: My part in this is very minuscule. I just got (git) his source and stuck it into cm11 as a build base. I changed very little, only added the msm8960 build since I think phil is working on the source rather than many individual builds due to time. If you look at his github from the main page link, the only file I really changed was ./boardconfig/BoardConfig.mk under ./recovery.
Goal: Just to make this available and keep people out of the main thread that aren't developing. If I can help with the specific device I'd do it, but I'm really not an xt926/5 expert. Still, if you've got msm8960 questions (so: device-specific, not general philz touch) ask them here about the device and recovery since odds are better you'll get an answer here than in the main thread. I'll try to update this with latest builds each week.
Disclaimer: The usual stuff you read in all of these threads. If your mind turns into margarine after installation, please send a sample to the CDC labs in Virginia. I searched all over XDA for a thread for philz for the msm8960 but didn't find it. If you do, feel free to destroy this thread, call me names, threaten my relatives (please do this), etc.
Credits: I think all credit should go to Phil, @Orphee and the CM11 guys if you like this type of recovery.

Thanks for doing this bro. Otherwise AHD'd be on 6.0.7x..
EDIT: Great job, I can confirm, 6.22.1 flashes and screen touches work perfect, format, wipe clean new rom, install new rom, restore backup on the Atrix HD/mb886.

Who wouldn't like the best recovery of all? Right? Thanks a lot

Works with keys only on the 907. Thanks.

aviwdoowks said:
Works with keys only on the 907. Thanks.
Click to expand...
Click to collapse
I don't recall the xt907 being unified into the msm8960, at least not in the philz code, but I could be wrong. Could you try a recent (6.19.x) build from over here http://goo.im/devs/philz_touch/CWM_Advanced_Edition/xt907 and let me know if that works? I think the msm8960 so-called unified builds are still a bit confused. It looks to me like only xt926 and 5 are covered.
If the build I linked to works, then it's to do with the 'unified' setup and I might need to grab some vender ID's etc.
By saying "works with keys only": I assume you're saying that the touchscreen stuff is off-kilter or just off period?
Thanks and I'll look it over for that device.
Everyone else: Glad it's working out for you. I'll update as soon as there's another git update.

No touch function at all. The mb886, 'hd & photon Q (screen input works too, albeit mirrored) recoveries have always worked on the M.
Any can be used on the others for key only use.
The Q twrp works 100% on the m but mirrored input. Arrrghhh said he may port his version to the m.

Since we can have unified recoveries now, would it be possible to make TWRP and have it work for all the unified devices?
Sent from my ATRIX HD using Tapatalk

aviwdoowks said:
No touch function at all. The mb886, 'hd & photon Q (screen input works too, albeit mirrored) recoveries have always worked on the M.
Any can be used on the others for key only use.
The Q twrp works 100% on the m but mirrored input. Arrrghhh said he may port his version to the m.
Click to expand...
Click to collapse
Took a look at the cm11 base I'm using as a building platform for philz code and it appears xt907 isn't yet part of the unified group though it ought to be according to CM. I'll leave a note and see if that's in the works. I'll check if xt907 has it's own build over there. By the way, from your reply I wasn't sure if you'd tried the pre-unified version I linked to on goo.im? Also philz stuff is using his own touch library GUI these days, and there might be something about that and the 907. Got some stuff to figure out.
Looks like (Atrix HD, Electrify M, Photon Q, Razr HD, and Razr M) are supposed to be part of it but from the way the code looks, (boardconfig) , not sure I believe it's yet been worked out. Razr M has some 9xx x {?} resolution, right?
Edit: CM11 looks fine as far as unified for xt907, so it must be something in the philz code that's not yet ready for the full array of unified devices.

penser said:
Since we can have unified recoveries now, would it be possible to make TWRP and have it work for all the unified devices?
Sent from my ATRIX HD using Tapatalk
Click to expand...
Click to collapse
I've used TWRP and like it a lot, but haven't looked at the build requirements yet. It seems possible to do unified builds for anything especially if you can do something like build the cm11 default code with it's default recovery, then substitute TWRP recovery for the default CWM in the ./bootable/recovery code. TWRP would have to be setup for that which is something I don't know. CM11 is where the unified structure is coming from in the case of these recoveries.

The 6221 you posted works.

aviwdoowks said:
The 6221 you posted works.
Click to expand...
Click to collapse
Cool! Thanks for letting me know.

hachamacha said:
Cool! Thanks for letting me know.
Click to expand...
Click to collapse
Are you savvy enough to allow/provide a partition backup of /persist?
At least Philz no longer lets noobs format it. Why not back it up? As it gets clobbered often.
---------- Post added at 09:41 AM ---------- Previous post was at 09:22 AM ----------
Could it have been the previous presence/oversight of the fomat command the the cwmr base gave be used on the phones that is the sole cause of all the /persist hubub & it being only on the phone is not an issue?
---------- Post added at 10:17 AM ---------- Previous post was at 09:41 AM ----------
More on persist
http://forum.xda-developers.com/showthread.php?t=2589790

aviwdoowks said:
Are you savy enough to allow/provide a partition backup of /persist?
At least Philz no longer lets noobs format it. Why not back it up? As it gets clobbered often.
---------- Post added at 09:41 AM ---------- Previous post was at 09:22 AM ----------
Could it have been the previous presence/oversight of the fomat command the the cwmr base gave be used on the phones that is the sole cause of all the /persist hubub & it being only on the phone is not an issue?
Click to expand...
Click to collapse
savvy: I don't know the answer to that yet
I just took a look at a) the main thread, noticed this (http://forum.xda-developers.com/showthread.php?p=48940651&highlight=persist#post48940651) and b) the code. What I come up with is that while in recovery, I can go to 'mounts' and mounting "persist" is an option which works for me. It's not on the backup list, mounted or not, but shows up in aroma FM when it's mounted. That link I put there claims there is allowed 5 "extra" partitions for backup/restore, so I might be able to set up /persist as one of them. I'm still new to this recovery code for android so don't expect too much. Looks like if I can get it to work on mine, then it ought to on yours.
As a workaround (if ADB is working to your box in recovery) , you could yank (pull) that /persist stuff yourself, but I think a new version is coming along pretty soon and I'll try to see if I can get it to work. (Time permitting etc etc)
edit: I realized that /persist is in the recovery.fstab file when I build which is why it's a mount choice in that menu. The other stuff (make it a backup choice) appears to be hard-coded in one of the .c files so it could be added, but there's a fair amount of stuff to do to add it. Yeah, it could be modified, but I'd want to ask Phil about it before messing with it. I suspect he had some reason since I noticed you and he talked about this in the main thread. Did he ever get back to you?

Mount is ok. When I posted the now unavailable format was there.

aviwdoowks said:
Mount is ok. When I posted the now unavailable format was there.
Click to expand...
Click to collapse
I'm trying to reopen the discussion in the main thread so we'll see how that goes.
Edit: General build update.
There's a new build, same version but some fixes that I'll put up eventually here. CM11 probably has the newest API and I'm restructuring my environment, so need to sync and clobber repo, include philz as a localrepo. Might take .. all day for the syncing and building to complete. Doing this in a VM today

Fixed: Aroma now works with screen input when booted from the msm version while key only from philz.
Translation: aroma works fully while using this on a 907.

hachamacha said:
savvy: I don't know the answer to that yet
I just took a look at a) the main thread, noticed this (http://forum.xda-developers.com/showthread.php?p=48940651&highlight=persist#post48940651) and b) the code. What I come up with is that while in recovery, I can go to 'mounts' and mounting "persist" is an option which works for me. It's not on the backup list, mounted or not, but shows up in aroma FM when it's mounted. That link I put there claims there is allowed 5 "extra" partitions for backup/restore, so I might be able to set up /persist as one of them. I'm still new to this recovery code for android so don't expect too much. Looks like if I can get it to work on mine, then it ought to on yours.
As a workaround (if ADB is working to your box in recovery) , you could yank (pull) that /persist stuff yourself, but I think a new version is coming along pretty soon and I'll try to see if I can get it to work. (Time permitting etc etc)
edit: I realized that /persist is in the recovery.fstab file when I build which is why it's a mount choice in that menu. The other stuff (make it a backup choice) appears to be hard-coded in one of the .c files so it could be added, but there's a fair amount of stuff to do to add it. Yeah, it could be modified, but I'd want to ask Phil about it before messing with it. I suspect he had some reason since I noticed you and he talked about this in the main thread. Did he ever get back to you?
Click to expand...
Click to collapse
Currently, recovery doesn't allow backup/restore of all what's in fstab
It would be dangerous in my opinion as you sometimes have the bootloader there
try to edit this line:
Code:
/dev/block/platform/msm_sdcc.1/by-name/persist /preload ext4 rw,nosuid,nodev,noatime,nodiratime,barrier=1
setting the mountpoint to preload will add it to my mod as it supports that partition
However, restoring could fail if you do not add the selinux needed permissions
Also, you can follow my guide here to add extra partitions using this flag: EXTRA_PARTITIONS_PATH
Actually, without adding the flag or recompiling, you can just edit recovery.fstab to:
Code:
/dev/block/platform/msm_sdcc.1/by-name/persist /extra_part1 ext4 rw,nosuid,nodev,noatime,nodiratime,barrier=1
by default, it is enabled when you name it extra_part1 to extra_part5
That way, you can easily add support to 5 extra partitions to nandroid menu with just a repack, no recompile needed

Phil3759 said:
Currently, recovery doesn't allow backup/restore of all what's in fstab
It would be dangerous in my opinion as you sometimes have the bootloader there
try to edit this line:
Code:
/dev/block/platform/msm_sdcc.1/by-name/persist /preload ext4 rw,nosuid,nodev,noatime,nodiratime,barrier=1
setting the mountpoint to preload will add it to my mod as it supports that partition
However, restoring could fail if you do not add the selinux needed permissions
Also, you can follow my guide here to add extra partitions using this flag: EXTRA_PARTITIONS_PATH
Actually, without adding the flag or recompiling, you can just edit recovery.fstab to:
Code:
/dev/block/platform/msm_sdcc.1/by-name/persist /extra_part1 ext4 rw,nosuid,nodev,noatime,nodiratime,barrier=1
by default, it is enabled when you name it extra_part1 to extra_part5
That way, you can easily add support to 5 extra partitions to nandroid menu with just a repack, no recompile needed
Click to expand...
Click to collapse
Thanks for the tips. After I test the next version (6.23.x) I'll try these techniques out, see how it goes on mine.

hachamacha said:
Thanks for the tips. After I test the next version (6.23.x) I'll try these techniques out, see how it goes on mine.
Click to expand...
Click to collapse
also, take a look here, at the highlighted line:
https://github.com/CyanogenMod/andr...8960/blob/cm-11.0/device_moto_msm8960.mk#L121
You have also a ro property to forbid mount:
Code:
ro.cwm.forbid_mount
Both these properties affect the format/mount options in "Mounts and Storage" menu

As far as screen input for the 907 goes, are you not almost there if aroma works?
---------- Post added at 08:12 AM ---------- Previous post was at 08:10 AM ----------
It works on 6227.

[ROM][5.{0,1}][AOSP][{Un,}Official] CM12.{0,1} (Lollipop)

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.