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!
Related
Hey all,
I've been an xda stalker for a while and have been using all sorts of roms for a while now, but now I am in need of my own question.
For a while now, my mother's G1 has been acting up, whether it be her own fault or a bug. But this one has me confused. Over the past three roms i flashed (dwang, cm, superd) this same problem is always around. Everytime I touch browser, dolphin, etc the page begins loading and then i see the home screen.
Everything else works as it should, which confuses me. Everytime I flash a rom, i wipe, wipe ext, repair ext, wipe, flash.
I'd be happy to post a logcat if someone would be so kind as to inform me how to dump to a txt file.
Hopefully this is something extremely easy so I can get her off my back hah
erkmasterflex said:
Hopefully this is something extremely easy so I can get her off my back hah
Click to expand...
Click to collapse
sure its easy, if its your mom's phone, dont have a unsupported non-factory rom on it... the REAL awnser is: wipe EVERYTHING, even your ext partition, and reinstall base, then CM... I'm guessing its something you mucked up by going between builds without wiping, or not fixing permissions between builds, or some app on your ext didnt play nicely.
*oh yeah, wrong section, read stickys, or DIAF, your choice*
jmhalder said:
sure its easy, if its your mom's phone, dont have a unsupported non-factory rom on it... the REAL awnser is: wipe EVERYTHING, even your ext partition, and reinstall base, then CM...
Click to expand...
Click to collapse
Nah I think he should install the RC29...just kiddin you should use Super-D or Enom's official. I kinda assumed this thread was about some kind of fix for browser problems.
Ace42 said:
Nah I think he should install the RC29...
Click to expand...
Click to collapse
well, the RC29 might actually force a wipe... and would update itself and have OTA keys... honestly probably not a bad way to go... Super-D is good, but honestly dont notice a huge difference between that and CM.
it was even not working when i reverted to complete stock. could this be a problem with the phone itself? Maybe revert to stock again and take it in to t-mo?
There should not be any problem with leftovers from previous roms, since i completely wipe data and ext as i mentioned in my first post.
Moderators, please move this to correct section. this seemed like the correct section since this seems to be more involved in the development side of things. Definately not Accessories but more involved than Q&A. Thank you
Phone ><---USB--->< PC/Laptop/Mac
adb logcat
watch text fly up screen ... make browser crash
quick !!!!! take a picture of that text.............
if you don't have a usb cable handy, a PC or the time to figure out how to get adb installed
go to terminal emulator on phone, and type
logcat|tee /sdcard/logcat.txt
( get the pipe "|" with alt then s )
make browser crash
go back to terminal press ball then C
Edit : the ball can be a bit of a pain, when in term do menu --> preferences --> control key , and set to which key you prefer, I like left alt as ctrl[\i]
now have a look at the logcat.txt file, it
less /sdcard/logcat.txt
you could just do logcat > /sdcard/logcat.txt
but it doesn't look as geeky
NB use >> instead of > to append > will make new file >> will add to file
to append to file with tee use tee -a file.txt[\i]
and yeah, wrong section
thank you very much for your assistance and the little linux command briefing ha
i decided to try every sort of wipe, repair, etc and do it multiple times. probably didn't do anythin, but worth a shot ha.
Ended up working! I removed the ext and swap partitions, wiped anything i could multiple times, flashed super d, didn't work, wiped a bunch, flashed htc recovery image, then cyan, and presto. For whatever reason it finally worked.
Shoulda done the logcat and posted it so y'all could see whatever was going on and hopefully help someone out later. but all is resolved for now.
If there is a next time, I will post in Q&A. I want to thank everyone for their input and wish all a good night.
-Eric
Moved as not Android Development.
Note: Please keep this thread restricted to Atrix-specific and general issues. Threads for other devices are referenced at the top of the main webtop2sd thread.
Discuss webtop2sd here (the other thread will be kept clean for announcements, FAQs, etc.).
Before you report an issue:
Make sure it's not on the Known Issues list first!.
Basic debugging, since these are going to be questions I ask anyways:
If you hit problems with the Android webtop2sd application, you'll need to tell me the error, and give me the last few lines of adb logcat. Run this adb command, which will filter out most of the unimportant lines:
adb logcat ActivityManager:i AndroidRuntime:i webtop2sd:i *:s
Are you actually booting from your SD card? You can find this out by checking the Diagnostics tab in webtop2sd, under "Currently mounted webtops". If mmcblk1p12 isn't listed, you're not booted from your SD card. If this is the case, report what ROM you're running from.
Is the webtop configurator application showing, but not running successfully? If so, plug your device into your dock and run a terminal (either locally or adbWireless + adb shell) and run the following:
su
/usr/bin/sudo -H -u adas bash
export DISPLAY=:0
python /usr/local/bin/webtop-configurator.pyc
I'll need whatever output shows up.
great! thanks for making it so much easier.
haven't actually tested it b/c i sort of figured out how to do that a few days back, but still need to manually install it.
maybe i'll test your app next time i decide to reinstall my ubuntu.
btw, which script are you using to mount /osh? for me only /data/logging.sh works (it's safer anyway).
I suspect that what I'm doing isn't rocket science by any means. But, what I do seem to be pretty good at is packaging semi-complex things up for people into a manageable form with a fairly solid level of reliability. You couldn't imagine the things I'm happy that I managed to accomplish with this app, because they're so... quirky.
Anyways, I've been using /system/bin/mountosh since the beginning. I need to tweak the copy I'm using right now, since my goals have expanded beyond what I initially wrote it for. On the other hand, it'll mean that I can separate out my "personal" Ubuntu versus my "debugging" one, and that should be quite helpful.
These advances with linux customization in webtop have turned me on to Ubuntu in general. I just dumped windows xp on my desktop server and now run ubuntu super OS and studio. This takes a phone to a new level. Thanks OP!
i would love to try this out but i'm on a mac.. can you partition through disk utility?
I would complain that you beat me to it, my initial post here, except it looks like what you created is way more advanced and polished than anything I could do.
I will check it out right now. Oops, i see it is only a shell at the moment. Well I am very eager to try it.
A few questions then:
1. I assume this is similar to your last mod, in that you have just moved the Motorola environment onto the SD card, no chroot or other tricks?
2. Is the dependency problem better? Are we able to replace the motorola packages?
3. Are we still stuck with jaunty or is there a possibility to upgrade to a supported version of ubuntu?
I know this might seem like a useless question (installing regardless), but your previous work was based off the 1.5.7 firmware, would this app be supported/functional on the current 1.8.3 firmware?
Oh, and...
Thank you!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! XD
-djazin
Yes I believe the most important questions here are:
1 - which version will it work for? .83? .57? or just up to .52?
2 - If the Ubuntu version could be upgraded to, say, 11? Probably not, but hey...
Regardless, your work is the only reason why I'm buying myself a lapdock and replacing my netbook, so thank you very much for this hobby of yours =)
Looks great, thanks for the hard work
Sweet!! I just bought a 32 GB card the other day. Happy Fathers day to me.
Looks like no sleep week.
n1ckr0th said:
i would love to try this out but i'm on a mac.. can you partition through disk utility?
Click to expand...
Click to collapse
Possibly; I'm not sure. At least one person I talked to said that it should be possible via command line utilities, but I'm not the best person to ask about this particular issue, not having convenient access to Mac OS X...
krkeegan said:
I would complain that you beat me to it, my initial post here, except it looks like what you created is way more advanced and polished than anything I could do.
I will check it out right now. Oops, i see it is only a shell at the moment. Well I am very eager to try it.
A few questions then:
1. I assume this is similar to your last mod, in that you have just moved the Motorola environment onto the SD card, no chroot or other tricks?
2. Is the dependency problem better? Are we able to replace the motorola packages?
3. Are we still stuck with jaunty or is there a possibility to upgrade to a supported version of ubuntu?
Click to expand...
Click to collapse
Heh. I've actually been planning this for over a month, after some pointers from eval- - I had a rough version running, but I wanted to make something that users would be able to take advantage of easily. Oddly, it's the UI that's been the difficult part - actually having it do stuff is (relatively speaking) the easy part.
1. Yes, this is moving the Motorola environment to the SD card. Nothing special otherwise.
2. Not really - nothing's changed on that front. I'll be tweaking some of the package states on the filesystem to make upgrades less liable to completely blow up, but if we want to keep some of the niceties that Motorola added, I'll need to port those changes forward (which I have no particular problem with doing).
3. We're stuck with Jaunty for now. Unfortunately, it looks like information I had previously in regards to a version upgrade for Ubuntu don't apply to our phone, so I'll likely start working on an upgrade to 10.04 LTS after this stabilizes.
Djazin said:
I know this might seem like a useless question (installing regardless), but your previous work was based off the 1.5.7 firmware, would this app be supported/functional on the current 1.8.3 firmware?
Click to expand...
Click to collapse
Viamonte said:
Yes I believe the most important questions here are:
1 - which version will it work for? .83? .57? or just up to .52?
2 - If the Ubuntu version could be upgraded to, say, 11? Probably not, but hey...
Click to expand...
Click to collapse
This is the fun part. Since this is an Android application and not a script, this part should work with any version. I'm currently running 4.1.57 on my phone (I never did get around to upgrading), but once I verify it works there properly, I'll be upgrading to 4.1.83 and testing there as well. There are no issues that I'm aware of that would prevent this first application from running, and the second application (the Python/Gtk one I have planned) should be able to handle any differences between the various ROMs out there.
And the Ubuntu version upgrade question, I answered just above this.
everything is greyed out when i try to use the app..
Epic Sogarth
The ui looks nice though can't wait to test it on 1.8.3 been on 1.5.7 with v2 awhile now updated to 1.8.3 installed the app played with the setting everything looks sweet cant wait for the go ahead XD wouldnt mind testing anything.
-Djazin
dicksteele said:
Sweet!! I just bought a 32 GB card the other day. Happy Fathers day to me.
Looks like no sleep week.
Click to expand...
Click to collapse
32g class 10 has proven to fail on the atrix
it corrupts. Lets hope you didn't spend the extra money for the class 10
n1ckr0th said:
everything is greyed out when i try to use the app..
Click to expand...
Click to collapse
Greyed out? I know that the "Go!" and "Uninstall" buttons tell you that it's not implemented yet, but nothing should be grayed out?
PAulyhoffman said:
32g class 10 has proven to fail on the atrix
it corrupts. Lets hope you didn't spend the extra money for the class 10
Click to expand...
Click to collapse
That's good to know. Luckily they were out of 10's, and I got a four. Already formatted 16 GB fat32 the rest ext3.
Sogarth said:
Greyed out? I know that the "Go!" and "Uninstall" buttons tell you that it's not implemented yet, but nothing should be grayed out?
Click to expand...
Click to collapse
Now that I really look at it mine is also. So I'm guessing that's due to 1.83, or GladiAtrix. That's what I'm using.
I'll post a screenshot if you need.
I could go to stock 1.57 upgrade to 1.83 but not until tomorrow night
Thanks for the answers, Sogarth. And congratulations on your gift man, because your sum of intelligence and dedication sure is one. I'll be installing this on my Atrix as soon as it has been stabilized (and, well, actually made useful xD)
I am on Gingerblur 4.5 only things greyed out are Partitioning section, both 'Device to partition' and 'Webtop partition size' items if "Partition ext. storage" is not selected. Also under "Locations" 'Delete filesystem file' is grey if 'Source webtop' is set to 'internal storage'.
All of these being grey makes sense if you read what they are doing......
_Dennis_ said:
I am on Gingerblur 4.5 only things greyed out are Partitioning section, both 'Device to partition' and 'Webtop partition size' items if "Partition ext. storage" is not selected. Also under "Locations" 'Delete filesystem file' is grey if 'Source webtop' is set to 'internal storage'.
All of these being grey makes sense if you read what they are doing......
Click to expand...
Click to collapse
Unchecking the Partition ext. storage option "ungreyed" the Locations options and Advanced options. Didn't think about doing that since that was one of the goals of this app.
Since I manually partitioned already I should have thought of that.
** Edited: Instructions at the bottom **
I have the Nexus S, and when I upgraded to ICS I found that opening the recent app dialog could take a while.
I wanted the ability to quickly switch to recent apps, so I thought the power and volume up/down buttons combination could be used to do this.
Quickly tapping on the power and volume up/down buttons together brings the previous/next recent app to the front
I prepared a short video to demonstrate (sorry for the lack of interesting audio in the video):
http://youtube.com/watch?v=ndGd2y9ro14
I created this and tested it for about a week.
It works fine, but still needs a bit tweaking and maybe some configuration through the settings screen (enable/disable completely, tapping time, cycle/don't cycle apps).
One major issue is that I believe it is only comfortable when the power and volume keys are located on opposite sides, like on the Nexus S.
This is a small modification to CM9, so I have a few questions maybe you could help:
Is there a way to include features per devices? I saw that the code checks for devices with or without the search button. Is there a way to know which device has the power button on the right? Or do I need to map it before-hand? Which brings me to..
Do you think this is this something worth uploading to CMGerrit for review to be included in CM, maybe enabled as an advanced feature in the settings section?
Do you know any ROM maintainer that would want this feature?
Any suggestions to improve (or drop) this are appreciated, maybe adding an indication of the app switching.
** INSTRUCTION **
Please follow one of the next instructions to get it (whatever suits you):
Install using a flashable zip
Download the attached flashable zip file (quick-switch-0.01-signed.zip), and flash it from recovery.
This is compiled from CM9 RC1. While it may work with later nightlies or other similar ROMs, I cannot guarantee that it does.
To revert, flash your ROM over it.
Install the jar file manually
I've also attached the JAR file so that you could install it manually.
The JAR should replace /system/framework/android.policy.jar
Backup the current one, copy the one from this post over it, clear the dalvik cache, and reboot.
You'll probably need to remount the /system folder so you could write over it (adb remount).
Note: You cannot do this from recovery because recovery doesn't mount /system automatically. To mount /system from recovery just type "mount /system" from "adb shell".
To revert, just copy the JAR from the backup and clear the dalvik cache.
Get the source (Advanced)
I forked the relevant project (android_frameworks_base) on github.
The commit is: https://github.com/lightpriest/andr...mmit/28e2caa1459d9be287d5e0b68b6ca04fee45970d, and it is present both on ics and ics-release branches.
An important note
While this is a nice thing to play around with, I've noticed that the power button started to wear on my device. I'm not 100% sure it's related, but I'll take a "wild" guess that it does. Not to say that the power button doesn't work at all, but I noticed that now sometimes it's enough to just slide a finger on it to actually press it. So, you've been warned
I'll probably make another build for JB, once it gets stable.
Attached files checksum:
quick-switch-0.01-signed.zip - 474e5d53cff57a163f9c24ec8301b2a7
android.policy.jar - eba03024571866fc0161e19484dc200a
youtube.com/watch?v=ndGd2y9ro14
That feature actually looks quite interesting, and usable. Would love it, myself.
I'm not sure whether or not it'd be accepted in CM, since they want their builds to be much more streamlined and easy to understand than GB builds. Who knows though, as I said, it's an interesting feature. There's also the problem with power- and volume keys that wear out. And this mod would no doubt accelerate that.
With that said, I would absolutely love a smali-version guide for this.
Edit: evilisto created a guide on how to map the multitasking button the the search key, which helps a lot. I recommend you check that out.
It is also possible to map the GB taskswitcher to search button. The gb is imo faster than the ics one
yeah its a cooool feature.. but the thing is...jelly bean has got super speedy task switchin even on our nexus s...
I'm not sure on what's the best way.
I can generate a diff of the smali files, and then maybe create a guide out of it.
I also created a signed update zip file, with the JAR that needs to be replaced.
The flashable zip was created from CM9 RC1, do you prefer the zip or the smali?
I'm not yet sure on how to provide this kind of guide smali, because the diff looks quite large.
Updated the post with instructions and notes (at the end).
Amazing work . Though they removed the lag in displaying recent applications in Jelly Bean. Its very snappy now.
Thanks!
I thought it was just a matter of time until the recent app overlay would work faster. From the beginning I considered this as an experiment.
This was just a nice thing to work with (and create), experimenting with the Android building environment and creating a flashable zip..
Learned a lot actually.
Actually, it is a great mod! I like it very much, makes simple two-task switching a breeze (like chatting on GTalk and writing an email simultaneously). Would you consider porting this to JB releases? AdamG's JB-Oxygen will be for sure a popular, stable release. I also think that AOKP team would love to implement your idea in their releases, since they offer feature rich roms.
Here's link to Adam's JB Oxygen : AdamG's JB Oxygen release
Great job lightpriest!
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.
I have a rooted Nexus 6 and wanted to edit my build.prop file in order to enable Wifi sharing. I made a backup first, and then when I saved build.prop after editing it was 0 bytes. Then I saw the backup was 0 bytes. First I crapped myself, then I copied in a N6 specific build.prop I downloaded off the net to /system, but no matter what I did, that new file was 0 bytes even though the original was 5k. 'df' showed I was not out of space in /system (had about 1.5 meg free). I even tried mounting /system RW just in case it was RO.
I finally decided after 3 hours of this that perhaps the whole thing was RO and a reboot would clear everything (based on a couple of other posts I read).
I held my breath, rebooted..... and as I feared I just get the black screen that says Google with a lock.
I can't shut off the phone (to reboot into recovery mode), the Nexus doesn't have an off button. I hold power down and it reboots. I give it a short press and it does nothing. I hold them all down and it reboots.
Can I get a pointer please to a thread that might help bail me out?
As a side note, I'm having problems connecting to my phone in debug mode with adb (even before the reboot), so if I need to use those tools, that's another hurdle I'll have to figure out.
Hold the power button + volume down to get to the bootloader. Go to recovery and reflash whatever rom you were on . A dirty flash should suffice.
Hit thanks if this solve your problem.
Getting a little further. Managed to boot into TWRP. Got into terminal, tried to copy in the build.prop file to /system that way but am being told I'm out of space.
Found a similar thread here I'm digging through.
http://forum.xda-developers.com/nexus-6/help/nexus-6-bootloops-build-prop-edit-6-0-1-t3473306
Just saw post #2, thanks. Thought I had it. I freed up some space in /system/app by deleting a couple of foreign keyboard files. Then copied in the build.prop file and this time it was the correct file size. Rebooted, but no change. I really thought that would have fixed things.
As an aside, df lies, there really was no space in /system
Looks like what I found was not a stock build.prop. I have no idea how much it differs but it contains this line:
ro.build.display.id=NexZen by VECTUS V07
Ha! Also it's for 5.1.1. Darn! I should have looked at this first.
Does anybody happen to have a pointer to a stock Nexus 6 6.0.1 build.prop? Google has failed me on this one.
Your original problem was, as you've found, that you had no space in your system partition. The reported 1.5 mb is way to little space to do any kind of system mods... I've found i need at least 50-60 mb free.
Stock build.prop is easiest found in the factory images, in system.img. If you're pushing it to your phone in recovery, don't forget to set the correct permissions (chmod 644).
Thanks, I did pull the file out of the stock ROM, but I must have gone wrong somewhere because it didn't work. I then looked at the /system directory and it was empty other than /system/bin. No idea how the heck I could have deleted the other files in there. That would have been a nice clean fix. But now I'm forced to do a flash. What a waste of a night! Thought it would be nice and simple to turn on wifi sharing. Ha!
I figured 1.5MB would be more than enough to add a single line to a file, the file system block size I'm guessing is in the 2-4K neighborhood. Regardless, it clearly wasn't enough for whatever reason.
I was on a stock ROM. Since I can't easily do a dirty flash of a stock rom, and I can't connect with adb, I need to try to find a TWRP version of a stock 6.0.1 or something really close. I'm pulling off whatever data I can save now just in case I have to wipe this.
If your /system is empty in TWRP it means you haven't mounted system. Under "Mount", make sure "system" is checked.
Sounds like the easiest thing for you would be just to fastboot flash the system.img from the factory image. That'll get you back on track.
It was a really late night but I'm back in business this morning. I used this stock ROM image with TWRP and did a dirty flash.
http://forum.xda-developers.com/nexus-6/development/rom-stock-rooted-6-0-1-mmb29k-t3279185
Now I still need to update my friggin build.prop!!!
robroth said:
It was a really late night but I'm back in business this morning. I used this stock ROM image with TWRP and did a dirty flash.
http://forum.xda-developers.com/nexus-6/development/rom-stock-rooted-6-0-1-mmb29k-t3279185
Now I still need to update my friggin build.prop!!!
Click to expand...
Click to collapse
Use adb and pull it to PC,edit it and push it back easiest way with newer Android versions
i have encountered this on my newer nexus 6. whereas my older nexus 6 seems to be void of these characteristics.(i have started to believe it is because the older one was moved through the API levels smoother....19-20-21-22-23-24-25....as my new one has gone from 18--------to 25. THAT IS TOTAL PROCESS OF ELIMINATION. no idea if thats what it is.) i was able to to push a reboot and temp. flash into twrp from adb/nrt. i dirty flashed my ROM and GApps and seemed to quick fix.
---------- Post added at 03:54 PM ---------- Previous post was at 03:47 PM ----------
there are a few key issues i have witnessed (as a whole) with a young and older sibling too..... which is not the subject of this issue but i think what i have come to learn can shed light on situational(from time to time) issue that i have to deal with when consistent flashing. the RO/RW is now a part of my routine for the newer phone(cause it will randomly drop its RW for no reason and prevent proper filing for busybox or in my case nethunter libraries)
whew. I was gritting my teeth on reboot tonight after editing build.prop again, but this time it went without a hitch. It sucks how you can find all these great articles about how to do stuff, but invariably I own the one phone where there's a gotcha that one doesn't think to look for
I'll keep an eye out for if/when it'll let persist.root. or the .....persist.dun. Will set =1 without breaking selinux.