Database Develop

g1 button remap for global search?

With the latest release of cyanogens update I started using the global search which I really love but unfortunately htc didn't give us a search button like the mytouch 3g has, I also find that I don't use the camera button at all so is it possible to remap the camera button to function as a quick launch for the global search like we can remap the end key?

I was wondering the same thing.
I have been looking at the filesystem & the /system/usr folder contains the folders "keylayout" and "keychars".
Inside the keylayout folder are several .kl (presumably .kl stands for key layout) files. If you edit them you should be able to change what ANY key on the device does, in theory anyway.
The qwerty.kl & trout-keypad.kl files appear to be the same unless I am missing something. They seem to be the layout files for normal US Dream devices. There is also trout-qwertz.kl which seems to be for the French QWERTZ key layout. I don't know how the trout-keypad-v2.kl & the trout-keypad-v3.kl are different from the traditional trout-keypad files, however you can look at that yourself.
I am looking at the trout-keypad.kl file for my ADP1 and am kinda struggling with a few of the keys. Obviously all I believe you have to do is change the line:
"key 212 CAMERA" to "key 212 SEARCH"
The SEARCH label is typically mapped to key 127.
However, I am at a loss as to what key 211 could possibly be, it is labeled as FOCUS, could it be when you press the camera key halfway down to focus in the camera app & key 212 be fully pressed?
I will do a little exploring & I will post back with my test results when I push the file to /system/usr/keylayout on my device later. Since they are just files I don't believe that you need to resign an update that contains them, you should be able to just push them to the device.
If it works I will upload the modded file here.
EDIT 1: You should also be able to add the tag WAKE in the next column over (where the other WAKE or WAKE_DROPPED tags are) if you want that key to wake the device.

Yeah I saw those files but can't do anything with them atm since I'm out and about but I assumed that they pertained to the slideout keyboard only so Ill look at them when I'm home.

They appear to be for ALL keys on the device, there are also some for BT headsets.
I updated all of the files with the camera & focus keys mapped to search, however it accomplished nothing. It still launches camera. I am running the JACxROM, but I am gunna try it with my old CM 3.6.8.1 build (which I preferred over JACxROM anyway). I'll post back later.

Geniusdog254 said:
They appear to be for ALL keys on the device, there are also some for BT headsets.
I updated all of the files with the camera & focus keys mapped to search, however it accomplished nothing. It still launches camera. I am running the JACxROM, but I am gunna try it with my old CM 3.6.8.1 build (which I preferred over JACxROM anyway). I'll post back later.
Click to expand...
Click to collapse
I was wondering if u edited the zip file then flashed it. Maybe that might help. I was thinking of doing something like this for myself but wasnt sure where to start

All I did as of yet was change the files, push them, and reboot. I am in the process of making an update and flashing it. Also, it didn't work with the first method on the CM build. The update I am signing will be based on the CM build.
One thing I also don't understand, is the *.kcm.bin files in the keychars folder. When I open them in a hex editor I cant understand them, are they encrypted, do they need unpacked, am I just an idiot??
EDIT: I'm an idiot. Just pushing the files doesn't work. For whatever the odd reason, it seems you have to package them in an update.zip file & sign them. It works great now. You can either push the button halfway down (FOCUS) and it will pop up, or push it all the way down (CAMERA) and it will pop up.
I can't upload the whole CM update (don't have the bandwith) but I will try to make an update.zip that contains just the new files (kinda like a theme update.zip file) and upload it.

Ok. I can't figure out how to make a plain update.zip with the files needed.
I put them in an update.zip file containing two directory trees:
META-INF/com/google/android/ which contains update-script (my custom one for this)
and
system/usr/ which contains all of the .kl files that needed modified.
My update-script file is as follows:
copy_dir PACKAGE:system SYSTEM:
What am I doing wrong? Whenever I try to flash the update I get an error that says "Syntax error in update script". I'm using the same convention used in theme update-script files. What should I do?
PS: The update is being signed, I'm not that stupid

Geniusdog254 said:
Ok. I can't figure out how to make a plain update.zip with the files needed.
I put them in an update.zip file containing two directory trees:
META-INF/com/google/android/ which contains update-script (my custom one for this)
and
system/usr/ which contains all of the .kl files that needed modified.
My update-script file is as follows:
copy_dir PACKAGE:system SYSTEM:
What am I doing wrong? Whenever I try to flash the update I get an error that says "Syntax error in update script". I'm using the same convention used in theme update-script files. What should I do?
PS: The update is being signed, I'm not that stupid
Click to expand...
Click to collapse
Cool I can't wait for this. If all goes well I can remove the search widget to free up space and memory. U should drop this by cyanogen so he can include it in the next update. I'm sure this would go great with the global search once the bugs r worked out of it.

Well since I can't figure out the stand-alone update.zip here are the plain files so that you can just add them to /system/usr in your update.zip of choice and re-sign it. I have PMd Cyanogen about this and will see what he says.
Glad I could help guys!
EDIT: Words of caution. I am not responsible if you screw up with this. Also, if you just press the camera button it will bring up the search box, but if you hold the camera button it brings up Voice SEARCH (not voice dial)
EDIT 2: I've added two new versions. The "keyboard_mod_cam-norm_focus-search.zip" file makes it so if you press camera completely down then it still opens camera, but if you just press it halfway down (to focus mode) it brings up search. Holding it at halfway still brings up voice search *see edit three*.
The "keyboard_mod_cam-search_focus-norm.zip" file makes it the opposite. Pressing all the way down opens search, pressing halfway down still focuses if you are in the camera app. Holding it all the way down still brings up voice search *see edit three*.
And of course the original file stays the same. Either position brings up search and holding still brings up voice search *see edit three* from any position.
EDIT 3: OK, it seems that voice search is only activated on a long press on CM 3.6.8.1! If you are using the latest (CM 3.9.11.2) it does NOT activate voice search anymore.

Can't you just use the original update and replace what you need in there?
Ok whoa you work fast but thanks for it! Hopefully cyanogen considers adding a setting for it, thanks so much!

thelamacmdr said:
Can't you just use the original update and replace what you need in there?
Ok whoa you work fast but thanks for it! Hopefully cyanogen considers adding a setting for it, thanks so much!
Click to expand...
Click to collapse
Yea thats exactly what I had to do to make it work, just replace the files in the original update and re-sign it then flash it. You can use any of the versions I posted to replace the files and it will work for you too.
And no problem. I haven't gotten a reply from Cyan yet but I did PM him.
Thanks for the compliment btw lol.

Ha ha well great job! Can't wait to get home and flash with this in it =D.

worked great thanx! i used ADB File Explorer v0.3 by makethetick makes pushing and pulling apk's a brezze no need to remember commands! if anyone would like to try it head over here, its the the op a few headers down
http://forum.xda-developers.com/showthread.php?t=532719

Hmm. It worked for you by pushing? I couldnt make it work that way, I had to flash a custom update that I put the files in. Did you do anything extra? Change permissions? Did you reboot? Check if it still works after a reboot, because mine didnt.

its still working after at least 4 reboots. did u pull out the stock files b4 u pushed it? in the abd file explorer i deleted the stock then just pushed from there. as of now this is my 5th reboot (once i find a setting i like i get update my nandroid). if u need to drop my a line faster than the forum check my signature for my gmail

Using the JacHero 2.1 which has camera key remapped to search. Don't seem to be able to reassign to camera - what's the keycode for the G1's camera button? Thought it was 211 (focus) 212 (take piccy).
Oh I should probably say hi - first post lol. I'm a bit n00bish but I have successfully reflashed this G1 5 or 6 times with different roms and haven't asked loads of questions without reading instructions - but can't figure this camera issue out. Cheers
Sorry about this post! All info was supplied earlier in thread! Mustve been a long day at work that day!

[BOOTSTRAP] Custom Safestrap v1.08f Released - 4-16-2012

Huge thanks to Hashcode for all his hard work thus far, what with the totally ingenious Safestrap and his latest victories with CM9. I hope this helps somebody out and that at least *someone* out there thinks this is as cool as I do.
Pushing OK+Backspace will force the console to kick you out back into the recovery, in case you get stuck. Keep in mind that the console is pretty powerful but also really dangerous if you don't know exactly what you're doing. Although, you'll never learn how to do anything awesome unless you get your hands dirty.
The Microphone button is now ESC, command history works, tab-autocompletion works via either the hardware Tab key or by pushing OK+i, and you can scroll back up through the text one line at at time with Alt+Up or Alt+Down or in chunks of 8 lines with Shift+Up and Shift+Down. Home is the home softkey, or the Search button on the keyboard, and End is the Power button. You could also push OK+A or OK+E for Home and End, respectively.
Make sure you uninstall Safestrap and then remove the application before you install this one. I just jacked Hashcode's .apk and stuffed my new binaries inside the .zips, if you don't want to bother with uninstalling and reinstalling the .apk, you can extract the recovery.zip and 2nd-init.zip from the archive and push them both to /system/etc/safestrap and reboot. Enjoy.
..............................................................
EDIT: I finally got my act together and put my modified sources on github:
http://github.com/buddyrich/android_bootable_recovery
............…………………………………………
EDIT: Just finished up my latest update to this branch of Hashcode/Koush's work. Added:
-Use numbers on the hardware keyboard to select menu entries. Got really tired of scrolling around and thought this would make things a bit quicker.
-Scrolling/repeating keys. Holding in for longer than about half a second will repeat even faster now, similar to a real terminal on a PC for instance.
-vim statically compiled to avoid the need for any external libs (ie: having /system or /systemorig mounted). Full color support and syntax is working great now; the only thing missing is background colors, which will be tricky to implement.
-a $HOME directory is now made at /emmc/safestrap/home. This is set up when the .apk is installed; it isn't necessary so it can be deleted if you want, but it is required if you want to have a persistent command history in bash as well as the ability to customize your .bashrc and .vimrc files. Most of you won't really know what this means, but if you do you'll probably appreciate it.
-Revamped all the menus and made everything look a little cooler. Let me know what you guys think! I got rid of the highlighting box that shows which menu entry is currently selected and changed it to simply highlight the text in white to distinguish from the green/yellow menus; I think it's a little easier on the eyes but some feedback would be cool. It wouldn't be very hard to allow the users to customize the menu colours themselves via external files placed on the sdcard/through a menu option.
-Fixed the issue some people were having with restoring to /systemorig; there aren't any more issues mounting/unmounting /systemorig or /system during a restore
-Probably many more things I've forgotten
-.bashrc tweaks, fixed a few aliases, nothing major
-You can flash updates from either safe or non-safe mode now, look in the advanced menu. Really though, be careful and remember to make backups of your /systemorig partitions. Don't say I didn't warn you! Guaranteed, someone out there will complain that they broke their phone so I was pretty hesitant to let that out in the wild, but I know I've found myself in the situation where I could've used it so there you have it.
Let me know if anyone finds any issues, I've done a pretty thorough job testing this over the last few weeks but there's always something to be missed. The new .apk is over the size limit to be posted in the forum due to the new bash and vim binaries and the vim runtime files, so you can download the new version from my dropbox here:
Safestrap (Tweaked) v1.08e for Droid 3
http://db.tt/CArenxr7
EDIT:
----------------------
Just finished thoroughly testing my latest release and think it's ready for human consumption! Another batch of sweet additions:
1) Proper implementation of /systemorig flashing while in non-safe mode... without any modifications needed to the updater-script present in any flashable zip. Even if the updater-script inside the. zip file you are flashing targets "/system", if you confirm it about three times in non-safe mode it will know to copy the files onto /systemorig to replace your stock system.
You can install Gingerbread-based ROMs such as MavROM 3.5 to the stock /system partition while in non-safe mode via the Advanced menu. Safestrap will backup and afterwards restore it's own files needed to ensure you can still get back in after a flash of the /systemorig partition. Note that flashing your original /system partition with an ICS ROM won't work yet because they need custom init.*.rc scripts in place during the 2nd-init process; this isn't hard to do but I was getting anxious to get something out so it'll have to wait until next time.
2) Redesign of the layout for the menus, much more organized
/* 3) Allow for rebooting directly into the recovery, either via the shell command "reboot recovery" or through the Reboot Menu */
// EDIT: Seemed to be causing some users to persistently boot straight into the recovery so on the backburner for now
4) Allow for custom colors for either safe or non-safe mode; to change the colors for now you have to execute a few little shell commands. Here's an example to change safe mode colors to a blue-grey and then non-safe mode colors to maroon:
Code:
s_rgb 139 137 137
ns_rgb 127 34 10
cc
Basically, "s_rgb" sets the colors for safe-mode and the three arguments (139 137 137 in the above example) are the codes for the red, green and blue components of the end result; you can look up rgb color codes for your own custom colors. "ns_rgb" is the command for non-safe colors. "cc" just tells the recovery to update the colors to whatever they've been changed to. If you don't like what you've done and just want to revert back to the stock ones, you can just wipe your /cache partition and they'll go back to normal.
Eventually I thought it'd be cool to be able to do this via the recovery UI but I haven't been able to envision how it would work yet.
5) Added background colors/highlighting in the console now, makes vim look a lot prettier. If there's anyone out there who cares, I preinstalled a few plugins (MiniBufExplorer, MRU (most recently used files), bash-style path completion, etc.)
Also, changed the cursor from the big ol' ugly white block to an easier-on-the-eyes one-character underline.
Yeah, it's overboard.
6) Much faster backups and somewhat quicker restores now. I clocked full backups (including /systemorig and ~350mb /data partition) at around 2 mins and full restores at around 7 minutes. Also fixed up the progress bars so they give a more accurate representation of how much longer the backup/restore will be.
7) Moved $HOME and other misc. Safestrap files to /cache instead of the /sdcard
8) Probably half a dozen other OCD details that I've already forgotten.
Test it out and let me know what you guys think!
As always, sources are posted on my github:
https://github.com/buddyrich/android_bootable_recovery
You can get the new .apk here:
Safestrap (Tweaked) 1.08f for Droid 3
http://db.tt/u4vAwv2u

i need this about 6 hrs ago lol.

Quite useful mate cheers.
=smc

Thank you so much for sharing this file. Your work is greatly appreciated.

This is a nice little(big)addition to safestrap! Thanks for adding it in!

I can't think of any better use for Christmas Eve than coding a bash console into recovery! Merry Christmas to the D3! Thank You!

Sounds good. I haven't grabbed it yet (as I need to keep my own customised Safestrap for ME863 nandroid support) but one thing I'd note is that the "OK" button (i.e. trackball click) is used for "Control" in Console+, and the console in Amon_RA's HTC Dream recovery. That saves you losing the @^ key.
Edit: Also: Source? Sounds like something that could be pushed upstream. I always found the console in Amon_RA's recovery very useful, missed it on my current device, when I didn't have a computer with ADB handy.

TBBIe,
I have an XT860, so I'm curious to see if this would work on your ME863. I remember seeing a post of yours a few months ago mentioning issues with the preinstall and data partitions (I think it seemed that the data partition was extended into the first bytes of the preinstall partition, rendering it unmountable during init) that should also have affected the XT860, but I have never experienced any issues with the partitions since Hashcode released v1.06.
I'll commit my sources to github shortly so you have take a look.

I am trying to get through the preinstall problem myself after flahing xt883 and I was wondering if I could fix it with this?
Sent from my DROID3 using xda premium

Hey there guys, Village Idiot here...I've been successfully using Hash's SafeStrap for a while now and wanted to try this one out. What's the difference here? Just by looking at it, I can't tell. It seems better from what everyone is saying, but I have no idea how to utilize it. Would you mind dumbing it down for Simple Jack over here? Thanks.

redsox985 said:
Hey there guys, Village Idiot here...I've been successfully using Hash's SafeStrap for a while now and wanted to try this one out. What's the difference here? Just by looking at it, I can't tell. It seems better from what everyone is saying, but I have no idea how to utilize it. Would you mind dumbing it down for Simple Jack over here? Thanks.
Click to expand...
Click to collapse
It has a console option included, allowing you to run shell commands, which could potentially save your butt if used right.
Otherwise it the same
Sent from my XT860 using xda premium

Endoroid said:
It has a console option included, allowing you to run shell commands, which could potentially save your butt if used right.
Otherwise it the same
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
Which it just did lmao..hash really needs to include this in his release!
Once again thanks for this mod it is PERFECT!

ovelayer said:
Which it just did lmao..hash really needs to include this in his release!
Once again thanks for this mod it is PERFECT!
Click to expand...
Click to collapse
Oh I'm sure I'll be damn thankful at some point. Made a point of installinng it
Sent from my XT860 using xda premium

Rick#2 said:
I have an XT860, so I'm curious to see if this would work on your ME863. I remember seeing a post of yours a few months ago mentioning issues with the preinstall and data partitions (I think it seemed that the data partition was extended into the first bytes of the preinstall partition, rendering it unmountable during init) that should also have affected the XT860, but I have never experienced any issues with the partitions since Hashcode released v1.06.
Click to expand...
Click to collapse
The difference is the other way 'round. The /data partition is extended backwards over the end of the /preinstall partition.
It doesn't cause problems during init, it was causing nandroid to fail mounting /system, and presumably would make switching to safe-mode fail (although I never tried)
My patch to fix this for nandroid was based on 1.06. The only way this could be 'fixed completely' in safestrap was if safestrap had had repartitioning code added at some point to resize /data back down and grow /preinstall to be large enough to hold a safe system. And Hashcode'd said he didn't have time or real inclination to do that, I thought.
I'm fairly strapped for time at the moment, so I don't know when I'll have a chance to look at the source and/or try out your build. But it's definitely somewhere in my TODO list. ^_^

orry for dumb question...ok, i wanr root my friends drodi 3,i think i know how to do it using the one click software the same i used to root my bionic,now to order to go into custom recovery i need install this apk file am i right,i mean is the same as in bionics bootstrap???? sorr y for noob qustion ,just that i dont speak english very well so i need be 100% sure what am doing thanks again,,btw do u know if the last wifi tethering works on this droid 3???

@rick#2
I'm running CM9 for daily use, but it's a bit wobbly at times, so I run 7.1 as the "non-safe" system. The big limitation to this is that I can't maintain the 7.1 fallback properly as hashcode deliberately disabled installing zips in non-safe mode.
If the wife has forgiven you by now - any chance of adding the ability to install .zips when in non-safe mode?
The alternative is to keep swapping bootstraps all the time, and all it takes is one late night sleepy mistake to stop the device booting one system or both.

I'm in favor of this as well, and have even mentioned it in the main SS thread. Could you add flashing to non-safe, but say with like 3 layers of warnings saying something like "THIS IS YOUR NON-SAFE, MAIN SYSTEM. FLASHING HERE CAN BRICK YOU."
This would be really nice because it's a PITA to keep switching strappers, albeit it easy, just a burden.

This is a great hack! I was considering doing this myself but you beat me to it! BTW, is your modified source code on github or somewhere like that, or can you send it to me if not? Thanks again!

Hey guys, sorry for the lack of updates to this thread. Been buuuusy.
I made an account on github about two weeks ago, but still haven't gotten the chance to upload the sources there, for those of you who are interested. I'll do that shortly.
I've got a new version I'll put up pretty soon, just need to do some more testing. I've enabled scrolling (ie: holding a key down to repeat it as opposed to requiring you to push it each time) but have to iron a few things out, and I'd like to add another menu enabling some of the (somewhat dangerous although useful if you know what you're doing) features some of you have requested.

Rick#2 said:
Hey guys, sorry for the lack of updates to this thread. Been buuuusy.
I made an account on github about two weeks ago, but still haven't gotten the chance to upload the sources there, for those of you who are interested. I'll do that shortly.
I've got a new version I'll put up pretty soon, just need to do some more testing. I've enabled scrolling (ie: holding a key down to repeat it as opposed to requiring you to push it each time) but have to iron a few things out, and I'd like to add another menu enabling some of the (somewhat dangerous although useful if you know what you're doing) features some of you have requested.
Click to expand...
Click to collapse
Dude you rock!
Sence you introduced your mod i have used nothing else..
The scrolling feature would be a HUGE improvement i agree ..
Also it would be nice if you could flash on the non-safe system as well..
Hope you can get er done..
I allways seem to watch this thread for updated..i really hope you can continue this adventure without the wife killing you lol..stay real!
---------- Post added at 12:45 PM ---------- Previous post was at 12:41 PM ----------
denpad2010 said:
orry for dumb question...ok, i wanr root my friends drodi 3,i think i know how to do it using the one click software the same i used to root my bionic,now to order to go into custom recovery i need install this apk file am i right,i mean is the same as in bionics bootstrap???? sorr y for noob qustion ,just that i dont speak english very well so i need be 100% sure what am doing thanks again,,btw do u know if the last wifi tethering works on this droid 3???
Click to expand...
Click to collapse
Hey bro if you want wifi teather look up android-wifi-teather..it works!

[PORT] RAZR JB OTA on D4 via kexec

known bugs:
occasionally modem may take a while to come up. toggle with airplane mode and/or reboot
fixed bugs:
slider/onscreen kb / phys kb issue.
everything else i tested works. wifi, bt, hwc, camera, calls, webtop, etc
releasing as safestrap V3.10 backup for now., might do flashable zip later.
unzip to sdcard, don't overwrite your own backups, and
restore to a clean romslot, haven't tested overwriting any other builds. it might work since it was an ota but who knows?
Link: http://www.mediafire.com/?x9aec82a8xcm4c1
Updated framework-res.apk fixes keyboard issue.
http://www.mediafire.com/file/jfsc35gr40yf8g5/framework-res.apk
to install framework res: mount system of romslot in safestrap make sure it's the right slot
adb push framework-res.apk /system/framework/
adb shell chmod 0644 /system/framework/framework-res.apk
wipe cache and dalvik cache just to be sure, and reboot
please report bugs.
kernel source here: https://github.com/kfazz/kernel_mapphone_kexec/tree/razr_jb

this rom has been superseeded by this: http://forum.xda-developers.com/showthread.php?t=2199741
it's almost exactly the same, but based on D4 JB leak, and everything works.

Is this too good to be true?
Can I ask what specific things on the hardware keyboard isn't working?

captainstarbucs said:
Is this too good to be true?
Can I ask what specific things on the hardware keyboard isn't working?
Click to expand...
Click to collapse
the slider event doesn't trigger that the hw keybaord is out or away, so
with Hardware keyboard turned on: the rom thinks the keyboard is out all the time, onscreen kb doesn't appear
with Hardware kb off: onscreen kb pops up all the time, regardless of whether real kb is in or out, hardware kb still works
the "mapphone switch" device sends the slider event via /dev/input/event5
runing getevent -l /dev/input/event5 shows SW_LID events, they just don't do anything.
i tried editing keyboard bools inside framework-res.apk, but they don't appear to make a difference.

Boooooo motoblur crap... Otherwise nice port! Will stick with cm10.1 for now. We should be getting jb ota soon anyway
Sent from my XT894 using xda app-developers app

Nice work kfazz
MotoBlur or not, this is a GREAT example of the kind of things we can now do on the phones using the new kexec kernel.
Glad to see it's already being put to good use!

Kexec is amazing. More mods should be coming.
Sent from my XT897 using Tapatalk 2

Nice ;] Sounds good iam going to test it
still waiting for a JB release
Edit: it not coming up for me. It start and update the application after that it reboot in boot loop

cannot wait to test this first thing tomorrow. Thanks so much

Could hash use this rom for fixes to the current issues with the JB builds he is working on?
Sent from my Motorola Droid 4 via XDA-developers app

how do we install this? i'm unfamiliar
edit: specifically the framework-res.apk. I'm assuming that for the ROM we just wipe and open it as a backup

FWIW: restored this from SS 3.11 just fine.
Strange issues with my sdcard, but other than that, everything seems to work.
Would love it if someone could make a flashable patch for the framework. My USB cable is touch and go..
Sent from my DROID 4 using Tapatalk 2

huhu1312 said:
Nice ;] Sounds good iam going to test it
still waiting for a JB release
Edit: it not coming up for me. It start and update the application after that it reboot in boot loop
Click to expand...
Click to collapse
did you restore on a a fresh romslot? try wiping data/cache.
Sent from my DROID 4 using xda app-developers app

Well that didn't take long! Good work.
Sent from my XT894 using Tapatalk 2

This ROM also works on GSM with no tweaks other than APNs. Does this mean we can flash any RAZR stock-based ROM or is it more involved than that?
Only problem I have found with it (other than Verizon bloat) is the keymappings for ; and : (normally accessed via Shift + , and .) don't work right, they get you < and > instead. Also the SYM key doesn't work, capslock light doesn't work. I've tried copying over omap4-keypak.kl and .kcm from ICS but it doesn't help, it actually makes things worse.
Also the damn motocast cdrom automount is back, and olegfusion's patch for it doesn't work with this ROM. Will need someone a lot better than me to fix that one!
Here is my GSM variant of this ROM with the following changes:
apns-conf.xml preloaded
framework-res.apk fix pre-applied
"This sim is from an unknown source" error fixed
Verizon crud removed
Misc debloating
Part1: http://www.mediafire.com/?2tcisw2za29wrt7
Part2: http://www.mediafire.com/?m7dfoomkcojejpf

Lum_UK said:
This ROM also works on GSM with no tweaks other than APNs. Does this mean we can flash any RAZR stock-based ROM or is it more involved than that?
Only problem I have found with it (other than Verizon bloat) is the keymappings for ; and : (normally accessed via Shift + , and .) don't work right, they get you < and > instead. Also the SYM key doesn't work, capslock light doesn't work. I've tried copying over omap4-keypak.kl and .kcm from ICS but it doesn't help, it actually makes things worse.
Also the damn motocast cdrom automount is back, and olegfusion's patch for it doesn't work with this ROM. Will need someone a lot better than me to fix that one!
Here is my GSM variant of this ROM with the following changes:
apns-conf.xml preloaded
framework-res.apk fix pre-applied
"This sim is from an unknown source" error fixed
Verizon crud removed
Misc debloating
Part1: http://www.mediafire.com/?2tcisw2za29wrt7
Part2: http://www.mediafire.com/?m7dfoomkcojejpf
Click to expand...
Click to collapse
in order for a rom to work right the kernel driver parts and userspace driver parts for things like pvr and ducati need to be in sync.
ramdisk needs to be extracted and modified for safestrap. kernel modules need to be rebuilt for kexec kernel, frameworks hacks for keyboard need to be done, (there may well still be more of these to do) /system/lib/hw/* libraries need to match boardname. ie (lights.maserati.so instead of lights.spyder.so) build.prop needs to be edited...
it's not entirely trivial, but since i already had a kexec kernel around this only took me ~24 hours.
Edit: if you didn't want to kexec a kernel, you might be able to hack roms based on the same version as whatver your stock kernel is, so ics to ics, etc.
more of a pain to do it that way though.

Ahh, this is all probably somewhat beyond me then, though I am definitely interested in how to extract and modify the ramdisk as that's where I need to modify two files to get rid of the cdrom automount.
For now though, I think this ROM is going to be my daily one, even as I continue to fiddle with it.

Google 'android extract boot.img'
You'll need gunzip and cpio to take apart and mkbootfs and gzip to reassemble. Ramdisk is at /system/etc/kexec/ramdisk.img
Got Sym key working, ; and :, and caps light, just not all at the same time yet.
Sent from my DROID 4 using xda app-developers app

kfazz said:
Google 'android extract boot.img'
You'll need gunzip and cpio to take apart and mkbootfs and gzip to reassemble. Ramdisk is at /system/etc/kexec/ramdisk.img
Got Sym key working, ; and :, and caps light, just not all at the same time yet.
Click to expand...
Click to collapse
It was the location of the ramdisk that was defeating me. Thank you!

I gotta say this is the fastest and smoothest I have ever seen my droid 4 run.
I am far from current on how to install things and never got the framework-res.apk installed. If anyone can make a video on how to install the framework-res.apk I would greatly appreciate it.
Also wondering if there is any plans to use this to improve existing roms like "CM10.1 / Jellybean 4.2.2 for the Droid 4". I have fell in love with all the customization's in that rom.
Please forgive me if I used incorrect terms or said anything that is inappropriate. I really have no idea on how all this works.

[SCRIPT] ROMCleaner

Had some free time recently so finally got round to opening my OYUA and having a looksy.
ROMCleaner 3.5 works splendid with CWM and OUYA.
Why use it with the OUYA?
Its a fast and easy way to pre-install all your apps and games through a single zip flash in CWM.
No more sideloading Dropbox to download and install everytime you flash a new StockPlus or OTA, have them all ready and waiting for you upon the first boot of the ROM.
If your familiar with ROMCleaner on one of the many devices we ported it to, you'll feel right at home!
As certain design decisions were overlooked with the OUYA and it didt get the following it was expected, I didnt wont make a big deal aout the release but couldnt help playing about with to see what I could get working on it. It worked fine so here we are
Notes
More detaililed guides and instructions can be found in any of the device specific threads for ROMCleaner if you want to have a look at its features but for now Ill leave this little guide for us OUYA users.
I doubt there will be a Aroma version due to its reliance on touch input but will slowly be looking at going through the other individual tools we created before Patrics83 put the Aroma AIO toolkit together.
It starts at v3.5 as this was the last version before moving to Aroma and we kept that consistent across devices.
Any changes will only be visually to the updater-script and the default romcleaner.txt included in the zip as at its core, RC works. I will keep a dated chagelog for you though for any updates to the zip.
Basic Guide
Pre-Requisetes:ClockworkMod Recovery
On your on the root of /sdcard create a (case sensitive) folder structure as so:
Code:
/sdcard/ROMCleaner/FirstBoot/data/app/
/sdcard/ROMCleaner/FirstBoot/system/app/
Place any apks in these folders which you want installed after flashing in the relevent folders
After flashing the ROM, flash ROMCleaner 3.5.zip
Reboot as normal
First boot of the ROM will take extra time due to the apks being sorted by Android when its up and running you will find all the apps in the usual place all ready and waiting!
If you install another launcher I recommend loading OUYA Launcher first and following the setup (wifi, username etc) to get it all sorted before using your preferred launcher.
You can use RC to install other files such as bootanimation.zip (system/media/) as well and are not limited to just apks. I add TwitcyEye's KeyMap mod for example so the mapping is done with no copying files about.
It will set the correct permissions for all the files and folders so dont worry about that.
Cleaning
ROMCleaner has the ability to remove files from the system after the ROM has been flashed, but before first boot, using a text file in a simple user-friendly format.
The default list has not been optimized for OUYA and I have not got round to checking through it yet. I haven't noticed any thing important if it does but you have been warned Ill take a proper look when I get the time.
You have the ability to define a custom list for RC to use by creating a ROMCleaner_user.txt file in /sdcard/ROMCleaner/ and Ive attached a blank one with some detailed instructions on its layour and format. I recommend you use this file until I have time to cross reference the default list with the OUYA files to avoid anything being deleted.
All in all its an easy way to get your apps installed when flashing a ROM be it StockPlus or an official OTA. It requires no special access as its all done in recovery and uses its own busybox.
Anyway, Have a play and let me know how it works for you.
Like a lot of people on XDA I have very little free time these days due to my job and so-called life but will be keeping my eye on this thread and the OUYA in general

#probably for formatted guide

#just in case

Is ROMcleaner able to load any type of complete backups from Titanium Backup or Android Tuner? I'm sure the answer is on your site, but it is probably a question a lot of people will have.
Sent from my SCH-I535 using Tapatalk 4

TadeoNYC said:
Is ROMcleaner able to load any type of complete backups from Titanium Backup or Android Tuner? I'm sure the answer is on your site, but it is probably a question a lot of people will have.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
Unfortunately thats a completely different thing. All this is done in recovery where as TB etc are app specific done while the OS is up and running.
RC installs (and can remove) the apps before the OS has loaded for the first time.

[ ROM ] - Dhollmen LOLLIPOP 5.0.2

.
Highlights:
Android 5 - Lollipop
Integrates the latest Dhollmen Kernel.
Supports NTFS file system.
Supports EXFAT filesystem.
Supports F2FS filesystem.
Available configuration options for Dhollmen Kernel overclock.
Integration of Viper4 Audio FX as an equalizer, amplifier and sound effects manager.
Supports for Joystick and game controllers.
Supports for gestures on the keyboard.
First Installation:
Download the zip file from Rom as tablet model
Download the add-on with pre-settings Viper4 Convolver IRS
Download the add-on with Google applications (Gapps)
Boot the tablet in recovery mode
Make "wipe data / factory reset" at this time
Install the Rom file
Install the Viper4 IRS file
Install The Gapps file
Reboot
Subsequent installations:
Download the updated zip file
Reboot to recovery mode
Do NOT any kind of "wipes"
Install the updated zip file
Reboot
Information:
Frequently asked questions you must read.
Downloads:
Recovery TWRP
WARRANTY: You agree that this product is provided "as is" without any warranty, either expressed or implied, on its operation.
DISCLAIMER: Your assumes at your SOLE RESPONSIBILITY all results produced by the "software" and/or instructions in this thread.
XDA:DevDB Information
Dhollmen, ROM for the Samsung Galaxy Tab 2
Contributors
tuxafgmur
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: No Longer Updated
Current Beta Version: 5.0.2
Beta Release Date: 2015-02-09
Created 2015-02-03
Last Updated 2015-02-15

.
> Rom's Notes.
Who installs this Rom, accept it "as is".
Contains just the apps and options installed.
What you want to add will have to be obtained from Google-Play or any other sources.
Please, don't report bugs if you are not using the installed Dhollmen Kernel.
In case of questions or comments, you must indicate additional apps, tweaks or installed "optimizations".
if you insert images, do it in a 'hide' tag. This hide your image until an user click to show it.
I assume you has installed a suitable Recovery and know how to perform the required steps.
Keep in mind that Antutu and others related apps give you very similar values, regardless of the Rom used.
In such apps, OC influence on speed, but its goal is to evaluate the hardware, not the Rom.
Don't use any kind of overclock before three consecutive stability test in Antutu.
> Rom take a long time to boot after installing.
It is quite normal because ART is used and applications are self-compiled at first boot time, after installing a new Rom.
> Applications are slow to start after installing.
It is quite normal because ART is used and have self-compiled before first use.
Although it may seem at times, the Rom is not hung, just have to wait.
> Get Root access.
In Settings app, entering development option and select Root access.
If you don't see these items, we activate:
Touch repeatedly on About tablet > build number. From now on, initial setting screen show that option, plus Performance.
> Get Performance access.
If you don't see these items, we activate:
Touch repeatedly on About tablet > build number. From now on, initial setting screen show that option, plus Development option.
> Google Apps (Gapps).
All Gapps packages available are virtually identical.
Only differ, from each other, in the amount of installed applications.
Never two different packages must be installed as likely to cause Google applications FC.
The Dhollmen Gapps, being valid for any Rom, are specifically adapted for installation on it.
> Viper4 - Convolver - IRS.
This application controls the System Sound FX.
It also includes a number of advanced pre-equalizer settings (made by others) that are the IRS whose installation files requested.
Access to Convolver (manager of the IRS) is obtained by selecting the option Expert in Experience Settings.
Using another equalizer (provided by external applications) usually interfere with it.
You can only have one active equalizer in the system, but if you want to use another one, kindly Viper4 can be turned off.
> Restoring backups.
It is very common Titanium Backup (or similar) problems in Rom.
If backup /data partition are made and, after a change of Rom, restored, usually side effects will occur.
In this directory and subdirectories it contains, there are many configuration files and internal databases.
When it comes to a specific application should not be a problem as long as it is not part of the Rom.
When sub-directories containing settings are restored, the likelihood of problems increases exponentially.
For example, all Roms have a Settings application, but the content of his configurations differs between them and is not interchangeable.
Under no circumstances you should restore /system partition apps.
> Brick Bug.
Don't worry about.
No problems here
> Recovery.
In the wave of failures of equipment, widely discussed and until the problem is completely cleared
The user is strongly advised not to use another recovery than Dhollmen TWRP-2.8.0.5 or Andi TWRP-2.8.0.1

Seems very nice, will give it a try after i get back to home. Thanks!

AMAZING, i was wondering wich LP rom was the best option when this pops up, thanks again OP you are the best.
Installing right now, will post feedback.

cool, thx

Hassan 4 said:
Seems very nice, will give it a try after i get back to home. Thanks!
Click to expand...
Click to collapse
Everything is working except GPS.
When opening an app for the first time it's really slow, after reopening it's faster. Seems pretty good for initial release.
Keep up the good work.

look promising, shall give a try
btw no keyboard tng this time?

Marcos OC said:
AMAZING, i was wondering wich LP rom was the best option when this pops up, thanks again OP you are the best.
Installing right now, will post feedback.
Click to expand...
Click to collapse
Installed, i cant get the sound to work, checked driver status on equaliser menu and it says "abnormal"
p3110, fresh install, wiped everithing even internal storage.

Confirmed no sound on 3110. Looks like the audio.primary.default.so file in /system/lib/hw was omitted when compiling for 3110. Just for the heck of it, I downloaded the 3100 build and the .so file was present in that rom. So, I just took the audio.primary.default.so from the 3100 build and put it in the 3110 build, sound working fine now.
I archived the file in the 3110 zip, then flashed the rom but you can also push the file with a root file explorer. Just make sure to set proper permissions and then reboot for it to take effect.
Or, you can just wait for the OP to fix the 3110 build.
Mike T

webdroidmt said:
Confirmed no sound on 3110. Looks like the audio.primary.default.so file in /system/lib/hw was omitted when compiling for 3110. Just for the heck of it, I downloaded the 3100 build and the .so file was present in that rom. So, I just took the audio.primary.default.so from the 3100 build and put it in the 3110 build, sound working fine now.
I archived the file in the 3110 zip, then flashed the rom but you can also push the file with a root file explorer. Just make sure to set proper permissions and then reboot for it to take effect.
Or, you can just wait for the OP to fix the 3110 build.
Mike T
Click to expand...
Click to collapse
can you please upload the audio.primary.default.so for us
OP, is the rom running on Dhollmen kernel for LP ..

Thank you Tux for bringing lollipop to Dhollmen.
Everything works fine. Smoother than CM12.
Titanium backup has issues with stock Root. Hence flashed supersu 2.45 to fix it.

How does one switch from the samsung keyboard dock to the on screen keyboard? I went to settings, then to language and input and the choice was grayed out. Is this something where if I have the dock option installed, that I can only use a keyboard dock?

What this rom based on ... ???

Help 3G DATA NO WORK!!

quick setting panel is not working for my p3100. plz fix it

.
For all those who so kindly have tested this first beta: :good:
I've taken note of all comments and I am reviewing each and every one of them.
when I've prepared the corrections I'll upload a new version.
I'll try the beta status as short as possible.
:highfive:

tuxafgmur said:
.
For all those who so kindly have tested this first beta: :good:
I've taken note of all comments and I am reviewing each and every one of them.
when I've prepared the corrections I'll upload a new version.
I'll try the beta status as short as possible.
:highfive:
Click to expand...
Click to collapse
Can the cast screen option be working?
Also tried casting screen through Chromecast app, sound is coming but no video.

This is the audio.primary.default.so from the P3100 build for anyone who needs it.
Do not forget to set permissions to rw-r--r-- / chmod 644
http://www.mediafire.com/download/p63chas4hva17wm/audio.primary.default.so

By any chance is there app to SD card support?

By what I can see, yes. See screenshot.