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.
Related
I was really getting tired of my carrier name showing up twice on the lockscreen and taking up extra real estate on my notification drop-down so I figured out how to disable the SPN from showing and how to customize the PLMN to say whatever I want.
KEY FILES TO EDIT
/data/data/com.android.providers.telephony/optable.db
/system/etc/apns-conf.xml
/system/etc/spn-conf.xml
In the apns-conf.xml make sure your provider is listed with a numeric value.
Here's an example: numeric="311370" mcc="311" mnc="370"
* As you can see the numeric is the MCC plus the MNC.
In the spn-conf.xml make sure your provider is listed with an spnOverride.
Here's an example: <spnOverride numeric="311370" spn_display_rule="SPN_RULE_SHOW_PLMN" spn_override_only_on="310,311"/>
The optable.db needs to be edited with SQLite Database Browser to add your numeric and the text to display.
Here are a few pre-configured downloads:
PLMN: CyanogenMod
http://www.4shared.com/file/BawWWTpv/cm7_plmn_gsm_crespo.html
PLMN: The Ultimate Droid
http://www.4shared.com/file/jo0455rx/tud_plmn_gsm_crespo.html
PLMN: GCI Wireless
http://www.4shared.com/file/l3fZUzGu/gci-apns-plmn.html
PLMN: B*** I Got An Android (with no asterisks)
http://www.4shared.com/file/Vkz6poYC/*****_plmn_gsm_crespo.html
NSFW YouTube Video - B*** I Got An Android
Flash these files AFTER you have flashed a ROM and booted up at least once! I tested all four files on TUD 3.0.0 Beta, CM7 A3, and various CM7 Crackflasher builds.
*Screenshots are from CM7 Crackflasher build #54 with the Jungle Waterfall livewallpaper
Very cool mod. I will try this out when I have the time!
thank you
Love this, it worked great on Bionix with 1.3 kernel. For some reason running the same rom with the new 1.4b kernel it no longer works and yes I tried reflashing and wiping a few times. Any ideas?
Hey could you make me one and either PM me or post it up?
I'm on CM7 on a Nexus S, and I don't see a '/system/etc/spn-conf.xml' file. It doesn't seem to exist on mine. I'm on the latest nightly (#8) and have updated everything. Am I missing something?
How exactly did you get these files? I'm having all sorts of trouble with this. First off, the optable.db file is zero K, even when I extract it through ASTRO or Root Explorer with R/W permissions. Secondly, as I mentioned in the last post, the 3rd file is missing from the stated directory.
I'm really confused, as it seems that none of these instructions add up for a Nexus S. I'd like my T-Mobile message to instead display "Nexus S: Pure Android, Pure Google"
Did not work on Modaco R9, CM7 or The Cracker builds...
nickmv said:
I'm on CM7 on a Nexus S, and I don't see a '/system/etc/spn-conf.xml' file. It doesn't seem to exist on mine. I'm on the latest nightly (#8) and have updated everything. Am I missing something?
Click to expand...
Click to collapse
spns-conf.xml does not exist on the Nexus S originally, but if you place it in /system/etc/ the OS knows to use it.
nickmv said:
How exactly did you get these files? I'm having all sorts of trouble with this. First off, the optable.db file is zero K, even when I extract it through ASTRO or Root Explorer with R/W permissions. Secondly, as I mentioned in the last post, the 3rd file is missing from the stated directory.
Use the optable.db from my zip and just edit it as you see fit.
I'm really confused, as it seems that none of these instructions add up for a Nexus S. I'd like my T-Mobile message to instead display "Nexus S: Pure Android, Pure Google"
Click to expand...
Click to collapse
I'm not sure what the character limit is but that might be too long.
I have all the files in the proper folders but it still doesn't work. Modaco R9
for those having problems getting this to work try using clockwork and press mount/storage then mount/system. hope this works.
tsalate said:
for those having problems getting this to work try using clockwork and press mount/storage then mount/system. hope this works.
Click to expand...
Click to collapse
You might be on to something, it worked for about 3 seconds then went right back to T-Mobile.
Still doesn't work. Mounted /system and /data. Does it only work for certain carriers? I'm using a&t
Is there a way to apply this to ALL carriers, rather than selecting one manually.
thanks
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!
Hi,
When I got my Droid, I couldn't believe all the stuff that came preinstalled with the phone, so I started deleting everything that seemed unnecessary. Given the fact that I already reflashed the phone 20 times in the last week, I made a little script to help me out. I thought I would share it with you in case it comes handy to someone.
BIG NOTE 0: There's a system part that Motorola uses to get stuff from your phone. It's called Data Collector. Whenever any app crashes, it makes quite a big dump, with your network carrier, signal level, applications installed, applications running and a lot of stuff that isn't opt-in. In fact, one of the scripts (/system/bin/bugtogo.sh) can take screenshots of your phone. I don't like being spied, so I tried to remove it all. Cannot be certain though, but I would recommend you to remove, if you like your privacy, at least, the DataCollector apks, and to empty the bugtogo.sh script from /system/bin
BIG NOTE 1: I don't use this phone in the US, so I don't know if I'm breaking part of the CDMA support. It still shows up in every settings and I don't have any reason to think it won't work, but since I can't test it in anything except GSM/UMTS, I can't know it for sure.
BIG NOTE 2: The script will install Apollo (Music Player), Nova Launcher (homescreen replacement), and Cyanogenmod's Gallery app. If you don't want them and want to keep Blur and the default gallery (the script doesn't remove the music player just in case it's needed by some other app), then don't use this script, or modify it as you wish.
BIG NOTE 3: I am not responsible for anything if this causes a mess. Worst case scenario you'll need to flash back the system partition (fastboot flash system system.img), and then reroot your phone. You have been warned.
This is what it removes:
Code:
/system/app/DataCollection.apk
/system/app/DataCollection.odex
/system/app/DataCollectorProvider.apk
/system/app/DataCollectorProvider.odex
/system/app/DataCollectorService.apk
/system/app/DataCollectorService.odex
/system/app/blur-services.apk
/system/app/blur-services.odex
/system/app/blur_facebook.apk
/system/app/blur_facebook.odex
/system/app/blur_flickr.apk
/system/app/blur_flickr.odex
/system/app/blur_kaixin001.apk
/system/app/blur_kaixin001.odex
/system/app/blur_lastfm.apk
/system/app/blur_lastfm.odex
/system/app/blur_orkut.apk
/system/app/blur_orkut.odex
/system/app/blur_photobucket.apk
/system/app/blur_photobucket.odex
/system/app/blur_picasa.apk
/system/app/blur_picasa.odex
/system/app/blur_youtube.apk
/system/app/blur_youtube.odex
/system/app/vzw_vnav_DROID4.apk
/system/app/vzwapnpermission.apk
/system/app/MyVerizon.apk
/system/app/VerizonSSOEngine.apk
/system/app/MotoVzwAtCmdPlugin.apk
/system/app/MotoVzwAtCmdPlugin.odex
/system/app/VzwController.apk
/system/app/VzwController.odex
/system/app/VzwDeviceSetup.apk
/system/app/VzwDeviceSetup.odex
/system/app/VzwEntitlementService.apk
/system/app/VzwEntitlementService.odex
/system/app/VzwPhoneService.apk
/system/app/VzwPhoneService.odex
/system/app/VCast.apk
/system/app/VCastStub.apk
/system/app/VCastTones.apk
/system/app/VCASTVideo.apk
/system/app/VmmGallery.apk
/system/app/com.motorola.android.server.ims.apk
/system/app/com.motorola.android.server.ims.odex
/system/app/com.motorola.android.settings.aplogd.apk
/system/app/com.motorola.android.settings.aplogd.odex
/system/app/VmmBackupManager.apk
/system/app/VmmBackupManager.odex
/system/app/VmmGallery.odex
/system/app/SmartActionFW.apk
/system/app/SmartActionFW.odex
/system/app/SmartActions.apk
/system/app/SmartCarDock.apk
/system/app/SmartDock.apk
/system/app/ZumoService.odex
/system/app/ZumoService.apk
/system/app/WelcomeWebtop.odex
/system/app/WelcomeWebtop.apk
/system/app/WeatherWidget.apk
/system/app/VZWInstaller.apk
/system/app/Vvm.odex
/system/app/Vvm.apk
/system/app/VSuiteApp.apk
/system/app/VRDClient.apk
/system/app/VMMServiceInterface.odex
/system/app/VMMServiceInterface.apk
/system/app/VideoSurf.apk
/system/app/Videos.apk
/system/app/VideoCalling.apk
/system/app/Swype.apk
/system/app/SocialShare.odex
/system/app/SlingBox.apk
/system/app/SocialShare.apk
/system/app/SlackerRadio.apk
/system/app/RichLocationVzW.apk
/system/app/Protips.odex
/system/app/Protips.apk
/system/app/PlusOne.apk
/system/app/PhotoEditor.odex
/system/app/PhotoEditor.apk
/system/app/OnlineAlbum.odex
/system/app/OnlineAlbum.apk
/system/app/NflMobile.apk
/system/app/Netflix.apk
/system/app/MusicStore.apk
/system/app/MotorolaAccountSetup.apk
/system/app/MotorolaAccountSetup.odex
/system/app/MotoEmailConfig.apk
/system/app/MotoDockHelperService.odex
/system/app/MotoDockHelperService.apk
/system/app/MotoConnect.odex
/system/app/MotoConnect.apk
/system/app/MotoCastDashboard.odex
/system/app/MotoCastDashboard.apk
/system/app/motoactv.apk
/system/app/MotMusic.apk
/system/app/MotGallery.apk
/system/app/MCDownloadManager.odex
/system/app/MCDownloadManager.apk
/system/app/Kindle.apk
/system/app/JunosPulsePlaceholder.apk
/system/app/IlsVzW.apk
/system/app/HuxVmmSetting.odex
/system/app/HuxVmmSetting.apk
/system/app/HuxSnCClient.odex
/system/app/HuxSnCClient.apk
/system/app/GuidedTours.apk
/system/app/GuidedTours.odex
/system/app/HelpCenter.apk
/system/app/FileManager.apk
/system/app/FileManager.odex
/system/app/Facebook.apk
/system/app/DockService.odex
/system/app/DockService.apk
/system/app/DlnaSystemService.odex
/system/app/DlnaSystemService.apk
/system/app/DLNA.odex
/system/app/DLNA.apk
/system/app/DemoMode.odex
/system/app/DemoMode.apk
/system/app/ContactIce.odex
/system/app/ContactIce.apk
/system/app/Cmas.odex
/system/app/Cmas.apk
/system/app/BuaContactAdapter.odex
/system/app/BuaContactAdapter.apk
/system/app/BlurUpdater_VZW.odex
/system/app/BlurUpdater_VZW.apk
/system/app/BlurChooser.odex
/system/app/BlurChooser.apk
/system/app/BackupRestoreConfirmation.odex
/system/app/BackupRestoreConfirmation.apk
/system/app/BackupAssistanceClient.odex
/system/app/BackupAssistanceClient.apk
/system/app/ArcVideoEditorLite.apk
/system/app/android-syncservice-app.apk
/system/app/OutOfBox.odex
/system/app/OutOfBox.apk
/system/app/FriendFeed.apk
/system/app/FriendFeed.odex
/system/framework/com.motorola.MCDownloadLibrary.services_lib.jar
/system/framework/com.motorola.MCDownloadLibrary.services_lib.odex
/system/framework/com.motorola.motoconnect_lib.jar
/system/framework/com.motorola.motoconnect_lib.odex
/system/framework/com.motorola.vzw.vmm.helper.jar
/system/framework/com.motorola.vzw.vmm.helper.odex
/system/framework/com.motorola.vzw.vmm.util.jar
/system/framework/com.motorola.vzw.vmm.util.odex
/system/framework/com.scalado.android.photoeditor.jar
/system/framework/com.scalado.caps.jar
/system/framework/com.verizon.phone.jar
/system/framework/com.verizon.phone.odex
/system/framework/com.vzw.android.gex.jar
/system/framework/com.vzw.android.gex.odex
/system/framework/com.vzw.android.hux.jar
/system/framework/com.vzw.android.hux.odex
/system/framework/com.vzw.android.jar
/system/framework/com.vzw.android.odex
/system/framework/com.vzw.android.smart.jar
/system/framework/com.vzw.android.smart.odex
Instructions:
1. Root your phone if you haven't already
2. Install Busybox from Google Play if you haven't already
2. Uncompress the zip into your internal sdcard. You should get this:
Code:
/sdcard/removecrap/Apollo.apk
/sdcard/removecrap/Gallery2.apk
/sdcard/removecrap/com.teslacoilsw.launcher-1.apk
/sdcard/removecrap/remover.sh
3. Run from a terminal on the phone, or from adb (always as root)
sh /sdcard/removecrap/remover.sh
4. Wait until the phone reboots
5. 200 extra Mb of system and a lot more free ram for your apps. Oh, and Motorola won't get another bug report from you
EDIT: Ooops, Reupdated the zip file, it was deleting one extra file (motosignature inside the framework folder)
EDIT2: Didn't catch Carrier IQ's qer binary on /xbin. Unfortunately we can't touch those binaries since they're in the randisk, so I updated the script so it removes the logfile qe generates and replaces it with a folder so it can never write the scan results again (thank you bofh.bug for the links!)
That's great, but you'll probably have trouble installing whatever official update comes next, since the updates generally expect certain apps to exist (with correct checksums too) so that they can be updated.
Sent from my DROID4 using Tapatalk
highlandsun said:
That's great, but you'll probably have trouble installing whatever official update comes next, since the updates generally expect certain apps to exist (with correct checksums too) so that they can be updated.
Sent from my DROID4 using Tapatalk
Click to expand...
Click to collapse
Probably OTAs will fail after running the script, but fixing it is as easy as reinstalling the system partition with fastboot and then applying the OTA
Sent from my DROID4 using xda app-developers app
This does disable all data connectivity (3G/4G) for CDMA users, you can still receive texts and calls, but will not be able to get data services.
When I have time I will make update this script to work with CDMA users.
arleslie said:
This does disable all data connectivity (3G/4G) for CDMA users, you can still receive texts and calls, but will not be able to get data services.
When I have time I will make update this script to work with CDMA users.
Click to expand...
Click to collapse
Were you able to fix the script so it works for CDMA users? Or, do you know what apps breaks it?
Very nice script, thanks. Easy way to run it by using Root Browser: open as script. But as for me QuickPick is better than ICS Galerry
Sent from my DROID4 using xda app-developers app
Hi biktor_gj , could you make a similar script for Android 4.1.2? Very grateful in advance
Tanzior said:
Hi biktor_gj , could you make a similar script for Android 4.1.2? Very grateful in advance
Click to expand...
Click to collapse
I did again the script for the jelly bean update. This time it removes less crap, since it seems Motorola left a bit less than on previous versions. This will remove the annoying "Foreign card" warning when you boot the phone with some non-verizon sim, the acoustic warning when you turn up the volume, smart actions and so on.
IT WON'T REMOVE THE APPS. It will leave them here:
Apps: /system/app/oldapps
system binaries: /system/bin/oldbin
Framework: /system/framework/oldframework
If you encounter any problem, you can simply move back the files through adb and the phone will be like before applying the script.
NOTE: Only tested on GSM. Probably won't work on CMDA since it's missing most of the Verizon stuff. If you can identify which apps are needed for CDMA to wokr again tell me and I'll update the script accordingly.
I run the script from ADB and worked like a charm. Been using it for 24hours and no problems so far, but you never know, so use at your own risk
Code:
[email protected]:~/Documents# adb push removecrap2.sh /sdcard/removecrap2.sh
[email protected]:~/Documents# adb shell
[email protected]_maserati:/ $ su
[email protected]_maserati:/ # sh /sdcard/removecrap2.sh
It works great, thank you. Good work.
Sent from my DROID4 using xda app-developers app
Hi to all, i found two app : ModemPanicReporter.apk and ModemStatsService.apk. What they are doing ? Maybe it is necessary to remove they too ? Removing these applications will improve battery life.
Sent from my DROID4 using xda app-developers app
Looking around in various threads I found numerous gps fixes. In some (most) the files are not original T959 files. While they may work, since they are not T959 KB5 files the possibility of 911 working diminishes. I set out to find any gps fix out there and build a flash-able package that would reset everything back to the proper (or as close to) files for our phones (T959).
Also I have found some ROMs utilized the SUPL port of 7276. This port was found to create gps log-spam and the "fix" was to reset the port to 7275. This IMO also resulted in quicker locks.
See HERE and HERE for more info.
For the 911 info go HERE (or just click it in FaultException's signature)
What this tells me is you want matched GPS libraries with the proper T959 RIL.
So I have searched a few threads and found 1 GPS fix so far and built mine to reset or undo any possible mismatched files flashed. If you find any GPS fix that some might use for CM10.1 please post it an I shall try to adapt mine to reset it to the proper files.
I have made:
North American version (NA)
Europe Version (EU)
Global Version (GL)
USA Version (US)
Asia Version (AS)
YMMV between USA and North America if you live in the states.
2nd post I will also post my custom version with some extra advice and good signal locks. What I need is for people to nanadroid first and test it. Also to post / link and GPS fixes they may have come across so I can check them. Point to note is I am attempting to fix non T959 GPS fixes as much as make a good GPS fix for our phones. Posting links to other "fixes" will help. Thanks
With any JB / ICS ROM you have taken the responsibility of possible breaking 911. No difference here. Flash at own risk.
NANDROID FIRST!!!
Big thanks to FaultException for the time, info, and files required for our phones.
Original version may mute calls > Revert to nanadroid if the case. V2 shouldn't effect calls. Please test.
Checking original Froyo gps files here is the the MD5's Ive found so far:
JFD (558kb)
0F3376A81E85AE6044D2BF68D63E2A55
JI6 (554kb)
4761E7B01E0A71A048458F50DE64BC62
KB1 (554kb)
870A5D6F3542FD7421B215FCB37D884C
KB5 (554kb)
870A5D6F3542FD7421B215FCB37D884C
(KB5 is what is in CM10.1 also)
Ok here is the file for my custom GPS setup. I have not had and deep-sleep issues (DS). Some of the following may work, or not. Its just some tips and stuff I do.
Zip file attached. NTP is set to north america so you can edit as needed.
This will also install Angrygps app for you. When you boot up open the app and set the following:
Settings > General Settings > Operation Mode = "MSBASED"
Settings > SUPL Settings > Server = supl.sonyericsson.com and PORT = 7275
Also I suggest you install an app called LeoAGPS injector. Found HERE
Install it like any normal app (no push), open the app and select "Pop-up message". After that go to your home screen and app the LeoAGPS widget. Click the widget to inject AGPS data. Wait a few seconds then reboot.
Try out the GPS and see how it goes.
Version 1 broke sound on the RemICS ROMs so I pulled the RIL files out. Now just custom gps files / fixes
Change log:
Added a USA version. May or may not work better than the North America version.
1/10/2013 - Since it appears the version 1 broke phone sound on the RemICS builds I removed the RIL files. Now v2 will only fix / replace gps files and not RIL files.
1/18/2014 - Added some MD5's of gpsd/agpsd files Ive extracted from Samsung dumps.
GPS fixes reset:
http://forum.xda-developers.com/showpost.php?p=33575684&postcount=504
If you want to try and adapt it to your specific country:
Open in a text editor: /system/etc/gps.conf
Change the NTP server line (top line) to your country. Country list found HERE
Edit / reboot / check
I do suggest the LeoAGPS app in post #2. It has seemed to work well for me.
Moped_Ryder said:
Ok here is the file for my custom GPS setup. I have not had and deep-sleep issues (DS). Some of the following may work, or not. Its just some tips and stuff I do.
Click to expand...
Click to collapse
Thanks for this awesome post! I know I'm suppose to test these files before asking but you might already have the answer: with these fixes, in your experience, do you still need to get a lock before DS in order to prevent issues after DS? Or after you reboot and getting into DS before locking first, you are able to get GPS to lock after DS?
Thanks for all your help!
davidgs said:
Thanks for this awesome post! I know I'm suppose to test these files before asking but you might already have the answer: with these fixes, in your experience, do you still need to get a lock before DS in order to prevent issues after DS? Or after you reboot and getting into DS before locking first, you are able to get GPS to lock after DS?
Thanks for all your help!
Click to expand...
Click to collapse
It was not addressed to me, my 5 cents anyway. I think it's more a kernel issue, at least it was so on ICS until the great SubZero came into play. You should try his GPS-wrapper, I think it could help (preventing the GPSD getting incidentally corrupted) - find the flashable zip in the "3 files fix" post of Jrafael (see post No 3 above).
I am also very interested in getting our Vibrant's GPS as much functional as it can be. My own "fix" (check for Igps.zip) was giving me best results for accuracy (down to 3 m!) on some ROMs (JB 4.1 and 4.1.2, but not 4.2.1). I found out that there are many useless files (such as gps.xml or secgps.conf), and that GPS will still lock and pretty quickly even without gps.conf tweaks (and even without this file). However I don't have coding skills to organize my empirical findings.
@ MR - where did you get your RIL files from, with the Europe fix file I have no sound on phone call (I use instead the MP's RIL files, working fine for me).
Got the RIL from KB5 / CM10.1 - same boat here about sound. Gonna pull the downloads and check on it. If anything Ill re-up without the RIL and just GPS files and try again. Im getting what looks to by Bluetooth errors when trying to connect. Even when BT is turned off with the RemICS ROMs.
Whenever able CM10.1 use the Froyo KB5 RIL / Drivers and such. Some times it just doesn't work. The RIL and AGPS files from Froyo KB5 match the CM10.1 ROMS.
Testing my original fixes - the following so far are the outcomes:
RemICS-JB: Breaks sound. Version 1 RIL and GPS doesnt match CM10.1 / KB5.
Slimbean: No issues - Sound works fine. Confirmed the base RIL / AGPS files in ROM match CM10.1
HellyBean: No issues - Sound works fine. Confirmed the base RIL / AGPS files in ROM match CM10.1
CM10.1: No issues - Sound works fine. Confirmed the base RIL / AGPS files in ROM match CM10.1
FIRST
I will apologize to those who flash the original version on RemICS ROMs. It broke your call sound. Return to your nandroid and all should be well. For those on Slim / Helly / CM10.1 you are fine.
The RemICS ROM is very smooth but the RIL / GPS files don't match the Samsung T959 KB5 (also in CM10.1) files. Replacing 3 of the RIL files with the proper KB5 ones broke the sound. Ill keep at it.
For now - Version2 no longer replaces and RIL files. All the above GPS fixes will replace gps files / remove un-needed gps files.
First I want to thanks Mr. Moped for jb GPS fix great job.I am using remics jb 4.2 and moped GPS files NA-Version 2 it works good, I lost signal than it reconnect so that issue is fixed in Version 2 and sound is working also thanks .
Sent from my SGH-T959 using xda app-developers app
Gps works good sound also ,only sound is bad when I put on speaker when i am on phone call to much noise . we used to control mic from in call volume control feature in advance setting and now we are missing that feature in 4.2.
Sent from my SGH-T959 using xda app-developers app
Moped_Ryder, I just flashed 4.2.1 and flashed your USA version GPS fix after flashing GAPPs. I'm coming from 4.1.2, and only got locks down to 30m intermittently. The norm was 800 m accuracy (vik5 responded to some of my posts). More importantly, thank you for doing this post (clicked the Thanks) and appreciate you explaining the reasoning behind your updates as well.
*Update* First lock in GPS Checker occurred after 31s with 8 "fixed satellites". Marked improvement over GPS performance on Team RemICS 4.1.2 (highest I ever got was 3 satellites, lock took 242 s). Thanks Moped!!
Cap'nO said:
Moped_Ryder, I just flashed 4.2.1 and flashed your USA version GPS fix after flashing GAPPs. I'm coming from 4.1.2, and only got locks down to 30m intermittently. The norm was 800 m accuracy (vik5 responded to some of my posts). More importantly, thank you for doing this post (clicked the Thanks) and appreciate you explaining the reasoning behind your updates as well.
*Update* First lock in GPS Checker occurred after 31s with 8 "fixed satellites". Marked improvement over GPS performance on Team RemICS 4.1.2 (highest I ever got was 3 satellites, lock took 242 s). Thanks Moped!!
Click to expand...
Click to collapse
Do me a favor if you have time. Do a Nandroid and try my Custom fix in post #2 (to include AngryGPS settings). Also combine that with the LeoGPS I linked as well.
See if that works any better for you. Revet back to your Nandroid after if you wish.
Moped_Ryder said:
Do me a favor if you have time. Do a Nandroid and try my Custom fix in post #2 (to include AngryGPS settings). Also combine that with the LeoGPS I linked as well.
See if that works any better for you. Revet back to your Nandroid after if you wish.
Click to expand...
Click to collapse
Will do
Sent from my SGH-T959 using xda app-developers app
Moped_Ryder said:
If you want to try and adapt it to your specific country:
Open in a text editor: /system/etc/gps.conf
Change the NTP server line (top line) to your country. Country list found HERE
Edit / reboot / check
I do suggest the LeoAGPS app in post #2. It has seemed to work well for me.
Click to expand...
Click to collapse
Hi, I tried to edit gps.conf file as mentioned. But whether I changed the supl_port to 7275 it remains 7276 it asks me to save the changes but doesnt save
Probably /system is not set for read/write.
Ill make ya a Flashable zip tonight if you give me the country you want from that list.
Moped_Ryder said:
Probably /system is not set for read/write.
Ill make ya a Flashable zip tonight if you give me the country you want from that list.
Click to expand...
Click to collapse
I don't suppose I could request a flashable zip for New Zealand (Oceania) gps settings?
I flashed from 2.3 to Cyanogen 10 then 10.1 and now have no gps when I did initially have it working in 2.3
Moped_Ryder said:
Probably /system is not set for read/write.
Ill make ya a Flashable zip tonight if you give me the country you want from that list.
Click to expand...
Click to collapse
Hi,
Thanx for the reply Moped I am using root explorer and set the r/o to r/w and opened the conf file in text editor.. I can edit the file but changes wont stick
I am living in sri lanka which comes under Asia — asia.pool.ntp.org Sri Lanka — lk.pool.ntp.org
Thank you again.
EDIT: I edited the gps.conf file using the es explorer (with root access enabled). there is a new file created inside root explorer gps.conf.bak and theres nothing inside gps.conf file (inside root explorer).
BUT gps.conf file (inside es explorer) has the changes I made. I rebooted but still the same
EDIT (update): Set the permission READ for all USER, GROUP, OTHERS and voila gps.conf file has the changes
Hope these info will help anyone having this issue
I can take care of it tonight.
If anyone wants to do it themselves its not hard.
1. Download and install a program called 7zip
2.. Download any of my GPS fixes
3. Right click on it (GPS fix). Browse thru 7zip to the /system/etc folder and drag the gps.conf file out to desktop (or somewhere).
4. Dont close the 7zip yet
5. Open the gps.conf file you just extracted and edit the NTP line to suit your needs. Save it.
6. With the archive still open in 7zip drag the edited gps.conf file into the /system/etc folder in 7zip. Overright old file.
7. Close zip. Its ready to transfer to your phone and flash it.
...You may be abnle to edit the gps.conf file right from 7zip (cant test Im at work right now)
I can always help someone with it. Just though peopl would like to try it out themselves too.
Moped_Ryder said:
I can take care of it tonight.
If anyone wants to do it themselves its not hard.
1. Download and install a program called 7zip
2.. Download any of my GPS fixes
3. Right click on it (GPS fix). Browse thru 7zip to the /system/etc folder and drag the gps.conf file out to desktop (or somewhere).
4. Dont close the 7zip yet
5. Open the gps.conf file you just extracted and edit the NTP line to suit your needs. Save it.
6. With the archive still open in 7zip drag the edited gps.conf file into the /system/etc folder in 7zip. Overright old file.
7. Close zip. Its ready to transfer to your phone and flash it.
...You may be abnle to edit the gps.conf file right from 7zip (cant test Im at work right now)
I can always help someone with it. Just though peopl would like to try it out themselves too.
Click to expand...
Click to collapse
One can make a custom flashable zip right on his/her phone.
1. Use a file explorer which has archiving function (I have Solid Explorer) and unzip any flashable zip you want to change.
2. Make your changes.
3. Compress to zip again. IMPORTANT: you must ONLY include the content itself and NOT the uppest folder (if your zip has two folders, META-INF and System, first select the two and compress these two in a single archive). Otherwise it won't be cwm flashable.
To change the gps.conf file on the go use Faster GPS (NOT Faster fix) free in Playstore.
Moped...i tried the other zip; No good lock on this one. Flashed Custom zip file and changed settings in Angry GPS as instructed. No lock..no satellite signals. Reverting back to old setup..using your US version, which worked perfect.
Sent from my SGH-T959 using xda app-developers app
Hello everybody. After spending hours trying to figure out what I could delete from the system to make room for Gapps on CM10, I even tried to resize partitions, I came to the conclusion that the Gapps will have to be stored elsewhere. So, I came up with a solution, by installing the apps to /data/Gapps and then symlinking the files to /system. So since there are so many people trying to get Goggle Now on CM9, I figured I would make modified Gapps zips for both CM9 and CM10.
These are complete Gapp packages, they actually free up space on the /system partition, and are completely functional. Most of the files are installed to data/Gapps, this way the devs will not have to worry about trimming the ROMs, except to fit on the partition.
I'm sure this will help a bunch of other devices that have smaller system partitions also.
Note: Facelock requires you to log in to an account, to even show up in lockscreen options.
I don't think Google should have any issues with this as I haven't changed any files that where in the zip just moved them around and modified the updater-script.
Installation for fresh install:
1. Boot to your favorite custom recovery
2. Factory reset, wipe cache and dalvik cache
3. Flash CM9/CM10
4. Flash these Gapps
5. Reboot
Installation for previous install:
If you are already setup , you will need to wipe the cache and reinstall the ROM to format system to remove any Gapps already installed. As long as you don't wipe data/factory reset you should be right back where you started.
1. Boot to your favorite custom recovery
2. Wipe cache and dalvik cache
3. Flash CM9/CM10
4. Flash these Gapps
5. Reboot
Google Now Installation for CM9:
Google Now Installation for CM9 (fresh install):
1. Boot to your favorite custom recovery
2. Factory reset, wipe cache and dalvik cache
3. Flash CM9
4. Flash Google Now (online)
5. Flash these Gapps
6. Reboot
Google Now Installation for CM9 (previous install):
1. Boot to your favorite custom recovery
2. Wipe cache and dalvik cache
3. Flash CM9
4. Flash Google Now (online)
5. Flash these Gapps
6. Reboot
[MOD][ICS] The Google Now for ICS Project [ARMv6 & v7]
Symlinked Gapps for ICS Ver3:
Fixed Facelock.
Note: Facelock requires you to log in to an account, to even show up in lockscreen options.
Had to add placeholders in system/vendor for the symlinks to be created, but vendor is still 0 bytes
symlinked-gapps-ics-20120429-signed-Ver3.zip
Symlinked Gapps for JB Ver2:
Fixed Facelock.
Note: Facelock requires you to log in to an account, to even show up in lockscreen options.
Had to add placeholders in system/vendor for the symlinks to be created, but vendor is still 0 bytes.
symlinked-gapps-jb-20121011-Ver2.zip
thank you very much
this reduces the pain while trimming the rom for matching system partition
in this same way can we get google offline voice..?
reversegear said:
thank you very much
this reduces the pain while trimming the rom for matching system partition
in this same way can we get google offline voice..?
Click to expand...
Click to collapse
GNow offline for ICS still requires about 60mb. So it will depend on the ROM. But, it works with our Triumph ICS ROMs. And they should be almost identical, as far as I've seen. I use GNow offline with my PA ICS ROM, with no issues. I haven't spent much time on any of the X6 ROMs, as we can't use the newer kernel and still use our phone service.
Let me know how it goes.
Sent from my WX435 using Tapatalk 2
This is great way of freeing up system partition..! So can our device be repartitioned? And make some internal memory available as internal sdcard?
bandukia said:
This is great way of freeing up system partition..! So can our device be repartitioned? And make some internal memory available as internal sdcard?
Click to expand...
Click to collapse
Already we have a enough internal memory 1gb. What we need is system partition which is 245 mb needs expansion may be additional 100 mb from internal memory. that is where the pain area.
"Fixed Facelock.
Note: Facelock requires you to log in to an
account, to even show up in lockscreen
options."
what do you mean by this sir?
thanks.
^_^
It is okey to flash this gapps when already some gapps (gmail, voice etc) in our rom? ....
Or we just force to uninstall before flash this? ..
Btw thx dude, great job.... :thumbup:
Ps:im using jb rom by dr.rush
Sent from my Andro-Id using Pulsa
reversegear said:
Already we have a enough internal memory 1gb. What we need is system partition which is 245 mb needs expansion may be additional 100 mb from internal memory. that is where the pain area.
Click to expand...
Click to collapse
thats not what i meant.. i was saying that partitioning our phone with what u said and also with some 100-200 mb to make internal memory detect it as sdcard?
bandukia said:
This is great way of freeing up system partition..! So can our device be repartitioned? And make some internal memory available as internal sdcard?
Click to expand...
Click to collapse
Thanks, our partitions can not be repartitioned/resized, I tried everything except deleting the extended partition(4) that holds 5 - 17. That is why I made these.
This is the breakdown of the partitions on our phone:
BSydz said:
So, this is what I have found so far about the partitions on the Triumph, I can't guarantee that this is all correct, but if anybody has any input feel free to chime in.
WARNING, THE INFORMATION PROVIDED BELOW IS SPECULATIVE AND COMES WITH NO WARRANTY. IF YOU MESS WITH THIS STUFF, I AM NOT RESPONSIBLE IF YOU DAMAGE YOUR PHONE.
Partitions:
1 (FAT) Mobile Partition containing image folder, which is very well documented around the forums.
2 (crypt/QNX4.x) Primary Boot Loader (PBL) I believe that this is what the SOC uses to boot.
3 (crypt) Secondary Boot Loader I believe this is where the hardware layout is contained, as it changes button configuration and was key to getting back to normal after I flashed the wrong nb0. It is linked to the mobile partition, as the phone will not boot properly without the correct amss.mbn
4 (extended) Just an extended partition containing partitions 5 - 17.
5 (Boot) This is where the boot img is extracted.
6 (OnTrack DM) I think this manages and verifies integrity of partitions 13-17.
7 (ext3) This is where the system/rom is located. This is what you see in root explorer as "system", containing the build.prop and other stuff.
8 (ext3) This is the "data" folder .
9 (ext) This partition holds CDA info, with OEM apks, ringtones, and wallpapers, it seems to be mounted inside partition 10 (hidden) when the phone is on you can find the information merged into "hidden/data" using root explorer.
10 (ext3) This is the hidden partition containing boot images and CDA info. This can be found in "hidden" using root explorer.
11 (ext3) This is the cache partition.
12 (ext3) This is the Caivs, can't find too much info on this.
13-17 (unknown) I believe this is where the phone specific data is stored, including but not limited to MEID, ESN, and PRL.
Click to expand...
Click to collapse
reversegear said:
bandukia said:
This is great way of freeing up system partition..! So can our device be repartitioned? And make some internal memory available as internal sdcard?
Click to expand...
Click to collapse
Already we have a enough internal memory 1gb. What we need is system partition which is 245 mb needs expansion may be additional 100 mb from internal memory. that is where the pain area.
Click to expand...
Click to collapse
Since there is no way to resize any partitions, that is why I made these. Data is the only partition that we can really use that won't require us to heavily modify the phone and be user friendly. Because not everybody who installs custom ROMs is gonna be able to do those types of modifications. This is the simplest way to fix the issue and won't impact anybody who wants to change ROMs.
aeoi said:
"Fixed Facelock.
Note: Facelock requires you to log in to an
account, to even show up in lockscreen
options."
what do you mean by this sir?
thanks.
^_^
Click to expand...
Click to collapse
I have had this posted in another forum for a while, the original tread is below. We (Triumph users) did not have camera working in ICS, and still don't on JB, So when I first released these, the optional script that installs facelock was not correct. Now that I have fixed the front camera, I got feedback that facelock was not working. While trying to fix it, I spent a few hours, never even getting the option in lockscreen settings, and finally added an acount one time so I could get some apps from google to figure out what was happening. Then I went in to the settings and it was there. So the hours I wasted was because I hadn't added an account. So face lock will not even show up in lockscreen settings until an account has been added to the phone. I think it has to do with having to have a second unlock option if facelock can't work, like low light situations.
http://androidforums.com/triumph-al...-w-google-now-ics-instructions-09may2013.html
adonwenas said:
It is okey to flash this gapps when already some gapps (gmail, voice etc) in our rom? ....
Or we just force to uninstall before flash this? ..
Btw thx dude, great job.... :thumbup:
Ps:im using jb rom by dr.rush
Sent from my Andro-Id using Pulsa
Click to expand...
Click to collapse
It may work, one of the issues I had was the script was putting the optional files in system (the wrong place) and then the symlinks would overwrite the files. So this leads me to believe it may work, but I can't promise anything. If it doesn't work I can add some stuff to delete specific files in the updater-script, or you can remove the files from the ROM zip before flashing. You will want to at least wipe cache before you try these. I hate to say it, but you may have to be the tester.
Now that you guys are aware of these Gapps, you should ask your dev to remove Gapps from the ROM if possible. That would probably be the best route to go.
bandukia said:
reversegear said:
Already we have a enough internal memory 1gb. What we need is system partition which is 245 mb needs expansion may be additional 100 mb from internal memory. that is where the pain area.
Click to expand...
Click to collapse
thats not what i meant.. i was saying that partitioning our phone with what u said and also with some 100-200 mb to make internal memory detect it as sdcard?
Click to expand...
Click to collapse
Sorry, as I explained above, this is not an option. Big SD cards are cheap now, and how would a couple hundred MB help anyway? If it is for swap, then it would be better to wear out your SD rather than your internal HD. Plus a good SD would be faster.
If anybody has any other questions feel free to ask.;
Thank you Bsydz for throwing light on the so far untouched topic in our forum
Lots of useful information.
Off topic question
Can you please let us know how do we port JB ROMs from triumph to ideos x6. Especially PA Rom
reversegear said:
Thank you Bsydz for throwing light on the so far untouched topic in our forum
Lots of useful information.
Off topic question
Can you please let us know how do we port JB ROMs from triumph to ideos x6. Especially PA Rom
Click to expand...
Click to collapse
Thanks. If I had another dev phone I would just build one for you guys. It is a pain switching over cause we never got an nb0, I have to manually swap out the partitions to get it back. That's where I got the info about the partitions. My PA JB is built on CM10, so it would be just like any other CM port except the headphones and most everything else should work. It is older since PA went to aosp instead of CM based. Are any of your CM10 ROMs built from source or just ports? It would be nice to see some of the edits made for our phone. The only thing that's not working on ours is 3G, video/camera preview, and HDMI. But you guys use sim cards so I don't think you would have 3G issues and your kernel should fix the previews.
I'll build a PA JB ROM if you are willing to test it. I have the device files and the kernels except ck's kernel. Let me know, cause I hate releasing something I can't test first.
Sent from my WX435 using Tapatalk 2
im ready to test the rom.
we have both the CM10. I.e built from source and port rom
This one built from source by master abenaigle
http://forum.xda-developers.com/showthread.php?t=2158624
This one is stable CM10 by Dr.Rush
http://forum.xda-developers.com/showthread.php?t=2160913
V0.2 is stable ROM presently.
I've uploaded my modded kernel source, sorry... not in github.
reversegear said:
im ready to test the rom.
we have both the CM10. I.e built from source and port rom
This one built from source by master abenaigle
http://forum.xda-developers.com/showthread.php?t=2158624
This one is stable CM10 by Dr.Rush
http://forum.xda-developers.com/showthread.php?t=2160913
V0.2 is stable ROM presently.
Click to expand...
Click to collapse
CacingKalung said:
I've uploaded my modded kernel source, sorry... not in github.
Click to expand...
Click to collapse
Thank you, I am building it right now, just working through the errors from the ICS device files. CK, I got your kernel source, so we will see how it goes. I'll start new thread when it is done building.
BSydz said:
Thank you, I am building it right now, just working through the errors from the ICS device files. CK, I got your kernel source, so we will see how it goes. I'll start new thread when it is done building.
Click to expand...
Click to collapse
Ready to test your ROM.. All the best.
visit Techlions.in for latest tech news..
reversegear said:
im ready to test the rom.
we have both the CM10. I.e built from source and port rom
This one built from source by master abenaigle
http://forum.xda-developers.com/showthread.php?t=2158624
This one is stable CM10 by Dr.Rush
http://forum.xda-developers.com/showthread.php?t=2160913
V0.2 is stable ROM presently.
Click to expand...
Click to collapse
Firmware and kernel of our devices are compatible, I checked when flashing CM 9 from Motorola TRIUMPH, running everything except the data and the camera upside down
Sory for my english
Dr. Rush said:
Firmware and kernel of our devices are compatible, I checked when flashing CM 9 from Motorola TRIUMPH, running everything except the data and the camera upside down
Sory for my english
Click to expand...
Click to collapse
No need to apologize for language barriers. Do you think, you could put together a zip of the files in /lib and /bin that are for fb0? I just need the files that you put in to get it working, not all of them. It will make it easier to setup a device files for building from source. I have built the ROM and it boots, but no display, with copybit errors. I think I can get past those errors but once it fully boots, I'm sure things will have to be fixed.
Also, yes our phones are almost identical. Our amss.mbn is not compatible with the new kernel so we can't use our phone after the update. Just like you can't install the newer ROMs unless you flash the sharp nb0. I have it installed on my dev phone right now so i can get this working. I can install the nb0 and everything works perfectly except phone and 3g. It sucks, cause we are stuck.
Sent from my WX435 using Tapatalk 2
How much, I realized you're talking about the incompatibility of your phone with our 35 kernel, 32 kernel but your compatible with our device, in MTDEV M9 worked even mobile network, except 3g that prevents replace the kernel to fix the library and enjoy the new firmware
BSydz said:
Thank you, I am building it right now, just working through the errors from the ICS device files. CK, I got your kernel source, so we will see how it goes. I'll start new thread when it is done building.
Click to expand...
Click to collapse
any update on status...?