yashsingh1/xdaforums huggingface dataset:
[Kindle Fire Android Development] Sblood86:
Only bug I actually know of is the reboot_recovery option in the advanced menu; it still has the old reboot wrapper and therefore initiates a standard reboot (obviously we can hold the power button to get back into recovery but it is obnoxious is the case of trying to wipe dalvik before flashing something). I wasn't sure what the current status was and I know it's a real ***** to test projects for devices you don't own hence my forking this recovery the other day lol; I used your reboot wrappers to fix reboot from recovery. Change found here

Full working versions are always great, TWRP is deprecated anyway and CWM is definitely my preferred choice lol.

I've been researching showing time and battery but have yet to properly implement this (DooMLoRD probably knows more; I'm still new to recovery).

I agree, personally I hate red; in fact whether you change the color or not I will be changing it in my fork for my manifest.
[Kindle Fire Android Development] airmaxx23:
So I'm a little confused about the easiest way to install this. Would someone mind telling me? Thanks in advance.
[Kindle Fire Android Development] smirkis:
there ya go.
[Kindle Fire Android Development] airmaxx23:
Thank you, it is appreciated.
[Kindle Fire Android Development] DooMLoRD:
so to summarize:

add compression/decompression support for backups <== havent done this before so will need some work

color change <== may be i will include themeing capability ;)

fix reboot in "advanced menu" <== i will remove it from here as it is no longer needed

battery percent <== easy to implement, i already have it on my other device recovery, just give me the output of: adb shell "find /sys/ | grep capacity"

show time <== can be easily implemented but is this really required?

anything else?
[Kindle Fire Android Development] smirkis:
Output of find /sys/

http://db.tt/E4Df6GU2
[Kindle Fire Android Development] xolanir:
From a noobs stand point, would it be possible to create a flashable zip so that it's easier to install. I managed to install using the gscript method and it was successful, but for future updates that people have requested, could you plus make the update .zip flashable? Thx in advance for your hard work.
[Kindle Fire Android Development] DooMLoRD:
first priority is to make everything work...

once that done anyone is free to package it whichever way is convenient to use/distribute...
[Kindle Fire Android Development] furtom:
You are right. TAR does not compress, it collects many files into one file for distribution or archiving, while preserving file system information.

Usually, compression is applied after the file is collected into a tar so the file becomes tar.gz (for example). But that doesn't yet seem to be the case for CWM.
[Kindle Fire Android Development] xolanir:
Thanks man!
[Kindle Fire Android Development] DooMLoRD:
TESTING RECOVERY (v01-FINAL-1)

about what u guys wanted:

add compression/decompression support for backups <== havent done this before and was busy so NOT implemented

color change <== not implemented, i like RED recovery :p

fix reboot in "advanced menu" <== fixed

battery percent <== implement, but not sure if its working as i dont have device to test

show time <== done

[ changelog/features ]

fixed "reboot into recovery" in "advanced menu"

shows battery percentage [based on generic sysfs interface] (not sure if this works as i dont have device to test)

shows current time (time when the recovery was entered/started)

uses new Roboto FONT (from latest CWM repo)

recovery build date/time is now shown

new "select update.zip menu": it will give u a new option - "show file details" - which will display the size (in bytes) and the MD5SUM of the selected file :)

new "advanced backup menu": it will allow the user to manually select which partitions to be backed up... supported partitions (/boot (kernel), /system, /data, /cache & /sd-ext)... THESE BACKUPs WILL BE DONE TO /sdcard

added prompt to display the "backup folder name" when user starts restoring a backup

added a warning and option to abort backup if space on sdcard is < 150 MB

increased on screen log/output display to 36 rows

[ download links ]

http://icxperia.com/doomlord/kindle-fire/KINDLE-FIRE-UtterChaos-CWM5-touch-v01-FINAL-1_recovery.img

MD5HASH: 980f152121afd5dcd12b732669e21b09

someone please test out and let me know...
[Kindle Fire Android Development] foxdog66:
Woot! I like the red also :D can't wait to test tonight when i get home
[Kindle Fire Android Development] smirkis:
1 more thing u should do, change the power button from select to "go_back" so nobody can get stuck in an option with no on screen buttons (like key test in advanced option).

Glad to see you back at it doom, ill test this in a bit.
[Kindle Fire Android Development] Sblood86:
Works as advertised; very nice as always. Smirkis is right however about getting stuck if you select keytest, being that there are no hard keys on the kindle I'm thinking the best solution would be to disable that option all together.
[Kindle Fire Android Development] DooMLoRD:
good idea... i will implement it...

does the battery capacity get shown properly?
[Kindle Fire Android Development] kinfauns:
Yes, the battery capacity shows the correct percentage.

I'm probably a little late in the game here and nobody asked me, but if somebody did ask me to restructure and rename the menu options, I would suggest something like the following.

backup / restore

- backup

- restore

- advanced backup

- advanced restore​

install zip

- choose zip from sdcard

- apply /sdcard/update.zip

- toggle signature verification

- toggle script asserts​

wipe / permissions / factory reset

- wipe cache partition

- wipe dalvik cache

- wipe battery stats

- fix permissions

- factory reset​

mount / format

- mount /system

- mount /data

- unmount /cache

- mount /splash

- unmount /sdcard

- mount USB storage

- format /system

- format /data

- format /cache

- format /splash

- format /sdcard​

advanced

- key test

- show log

- report error​

reboot / shutdown

- reboot system

- reboot recovery

- reboot fastboot mode

- shutdown​

This way, similar operations are grouped together, with more commonly used options up top and lesser used or used last items on the bottom. I think it would provide a cleaner interface and you wouldn't have to hunt and search for things that often go together.

They are just suggestions, so the dev can do with them as he pleases. If not for this version then maybe leave them on a shelf for consideration next time around. Thanks for the recovery.
[Kindle Fire Android Development] DooMLoRD:
ok so the last version i uploaded (FINAL-1) is the final version (for this recovery) from my side as i dont have much time to work on this...

it would be great if someone can send me screenshots of this so that i can update the one in the OP...

everyone is free to repackage/distribute it in whichever package they fell will best help users/make it easy for users to download/install this... BUT kindly send me a p.m. (here on XDA) informing me that u are going to repackage/distribute it...

as always, i am here to provide support, if at all required, for this recovery... latest sources for changes/modifications will be pushed to the git repo soon...

if i get time i will create a FULL touch version of this recovery as shown below (that one is for Xperia ARC/PLAY):

[youtube]7FN4toSbB5A[/youtube]

regards,

DooMLoRD
[Kindle Fire Android Development] smirkis:
everything looks great. is there any way to move the battery percent and date features somewhere stagnant? like near the top where it says utter chaos? also, there not live displays. they never change, and if I do a lot in recovery, they get pushed up off the screen til their gone.

either way awesome implimentations, hope u dont think im complaining lol, I think just finding the right place for them is all we need to do.
[Kindle Fire Android Development] foxdog66:
Should the buttons be the only touchable part? If I slide left it right it moves the selection down one. Up and down, the buttons seem to stretch across the screen... umm... I don't know how to explain that one. These aren't really issues but I thought I'd say something just in case the buttons were supposed to be the only interactive spots on the screen (they are not right now)
[Kindle Fire Android Development] paranoid android85:
wow...thank you for the hard work. that recovery is pretty awesome. i wish yall could dev for my epic 4g touch.
[Kindle Fire Android Development] smirkis:
the touch spans the whole screen. the button-icons are there to give you something to direct your touch. but there are 4 main touch points that span the whole view. its just how the touch input code ended up responding on our devices in recovery.
[Kindle Fire Android Development] Sblood86:
This has been answered on Napstars source thread; in short, call it fat finger friendly ;)
[Kindle Fire Android Development] DooMLoRD:
exactly ;)
[Kindle Fire Android Development] acax456:
Can u make a flashable zip for twrp???
[Kindle Fire Android Development] Sblood86:
I can't speak for DooMLoRD or most of the others on here but there is a common consensus among at least a fairly large group of us (this is one reason you will never see me packaging recovery in a zip), JerryScript said better than I could and he's quoting LeslieAnn: read.

Possibly use the Gscripts installation provided by Smirkis?

Edit: Link to gscripts, basically you just need to rename the recovery image from here to match the recovery image provided by Smirkis and swap them the two ;)
[Kindle Fire Android Development] foxdog66:
Cool cool. Just wanted to point it out just in case :D

I could live without the time, battery etc. the time isn't the correct time zone anyway. I do like it telling me that I'm low on space
[Kindle Fire Android Development] acax456:
Can u make a cyan color? The red color is too dark...
[Kindle Fire Android Development] smirkis:
Flash_image doesn't work on our devices. My scripts simply use the dd command. But I agree with the whole when to flash each for sure.
[Kindle Fire Android Development] Sblood86:
Yeah, sorry if I didn't make that clear, I wasn't saying use Jerry's command, more to point out the zip issue, thanks for pointing that out. I would hate to confuse someone with commands for another device lol
[Kindle Fire Android Development] Sblood86:
Screenshots per request (don't you just love screencast lol)
[Kindle Fire Android Development] chairshot215:
Just used the Gskript and it could not have been easier. Probably the easiest recovery instalation I have ever attempted, that's saying allot considering my phone came out the box with Sudo and an unlocked bootloader. Also very much digging the new FFF. My Kindle now feels much more like a traditional Android device. Big ups to everyone who has worked on getting this together.
[Kindle Fire Android Development] xolanir:
I couldn't agree more. Diggin the new FFF and updated recovery.
[Kindle Fire Android Development] chairshot215:
Quick question,

Could anyone explain why CWM takes longer to do things like a Nandroid backup? Not complaining, just curious as I have had a few issues with TWRP in that things would be missing after restoring a Nandroid. I noticed this with a few apps and would then wonder what else may be missing that was not noticed. I also noticed that flashing with TWRP did not always go so well either. I could flash the same zip and each time get a completely different bug like temperature or voltage not displaying in apps or the device acting like it has gone idle applying things like auto-killer screen off presets, setCPU screen off profiles or pausing 3d games in the middle of play every other minute because it thinks I just turned off my screen despite the fact that I am actively gunning down aliens. I have run a few tests now with CWM and have not yet noticed any of these glitches I would see when using TWRP. Sorry had meant this to be a quick question but is nice to vent my frustration with TWRP. Why I am at it I think the recovery reboot alone is a good reason to ditch TWRP. God only knows what it is doing to the longevity of many users’ power buttons.
[Kindle Fire Android Development] airmaxx23:
I've also noticed that the backup .zip files are a lot larger with CWM,. My average TWRP backup it's about 500mb, with CWM they are 800mb.
[Kindle Fire Android Development] drk.hd:
That's because TWRP compresses its backups, as well as backing up less of the system than CWM by default.
[Kindle Fire Android Development] podspi:
Compression is good. But TWRP also saves less?! Yikes :eek:

A backup should backup... everything you tell it to...
[Kindle Fire Android Development] Pkt_Lnt:
In TWRP, you have choices of what to save in a backup with check boxes. Default is only a few, I checked them all.
[Kindle Fire Android Development] NYCHitman1:
Does anyone have the CWM5.0.2.7 img file? For some unknown reason, my WinZip/7Zip/WinRAR won't extract the file cleanly.
[Kindle Fire Android Development] smirkis:
The download link in OP is the img file.
[Kindle Fire Android Development] Rodhargis:
How to install CWM when you have TWRP installed

I had to rebuild my kindel and only had access to TWPR so though I would see what that was like. Its OK but I would rather have CWM installed as I am more used to it.

In noob words that I can understand how can I install CWM on my kindel and get rid of TWPR.

Please keet in mind I have to take baby steps as I am still learning and don't understand all the terms.

thanks
[Kindle Fire Android Development] gett:
http://xdaforums.com/showthread.php?t=1500935
[Kindle Fire Android Development] Rodhargis:
Thanks. I was mainly worried that since I had TWRP installed if I tried to install CWM I would mess things up bad.

Used the instructions;) and it worked perfect...
[Kindle Fire Android Development] acax456:
Yup gscript is the shortest, easily to flash recovery
[Kindle Fire Android Development] gett:
glad to help :)
[Kindle Fire Android Development] Bazar617:
Hey guys, I'm trying to get past a few problems... Is there a flashable recovery of CWM? I think I need to reflash FFF, but I can't get in to fastboot thru TWRP.

When I power on the Fire, it pretty much goes straight to recovery, which I have TWRP installed right now. I've flashed many Roms, but it still won't boot normally (and Kindle Fire Utility won't recognize it since it's not in fastboot)... I know CWM has fastboot since I had it on there previously (I thought TWRP would as well)... So I need a .zip instead of a .img of the CWM... unless there's another way to get in to fastboot from a shutdown? I have no access to the android system at the moment.

Thanks for any help
[Kindle Fire Android Development] Sblood86:
Sounds like you selected reboot recovery from within a ROM while running TWRP. While in recovery connect in adb and reset your boot mode

adb shell idme bootmode 4000

Should boot back normally now assuming you system is still in tact.
[Kindle Fire Android Development] Bazar617:
I did the boot mode using the KFU 095, because before that it was stuck in fastboot lol ... I was able to get the stock Amazon rom flashed tho which reset everything, including the boot.img and recovery, so I'm out of the hell and all good thanks to the guys on KindleFire IRC. Thanks for that little bit of info tho, I'll be sure to remember that if it happens again.
[Kindle Fire Android Development] Sblood86:
No worries, if you are replacing your recovery with cwm that shouldn't be a problem anyway, the reboot wrappers in twrp are borked but they've been fixed in cwm.
[Kindle Fire Android Development] Roland Deschain:
You could also just open a terminal emulator on a rooted Kindle Fire (regardless of what ROM you're on, if any) and type:

su <enter>
idme bootmode 0x5001 <enter>
reboot <enter>

That'll reboot you into recovery. ROM Manager and jrummy's ROM Toolbox didn't reboot into recovery for me in CM9, but that works. I couldn't ADB to my KF at all from CM9. :(
[Kindle Fire Android Development] titusseid:
I've switched from twrp to cwm because of all the good things I hear about it, but I have no experience with it is there a good thread that is a tutorial for cwm. Just don't want to wipe a wrong thing and lose all of my SD card personal files
[Android Software Development] dswaggz:
selinuxproject.org/page/SEAndroid

Building for a Device

It is advisable to make a backup of your device prior to trying to install AOSP on it, typically using a recovery ROM such as ClockworkMod. Also note that you will erase your user data when you unlock the bootloader. Finally, keep in mind that AOSP does not include various proprietary apps such as the Google apps so you will not have them in your build unless you extract a copy from your device and re-package them for your build.

As in the emulator case, you will need to build a modified kernel with the necessary support for SELinux. Various kernels are available under the kernel/ directory. Use the right kernel and kernel configuration for your device; the defconfig files have been modified to enable the necessary options for SELinux. For example, to build for the Nexus S phone, you would do the following:

export PREFIX=/path/to/your/aospclone

cd $PREFIX/kernel/samsung

make ARCH=arm herring_defconfig

make ARCH=arm CROSS_COMPILE=$PREFIX/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-

For the device, you need your modified kernel to be included in the boot partition image (boot.img) rather than the prebuilt kernel. We have modified the device/samsung/crespo/device_base.mk file to refer to our kernel and wireless module rather than the prebuilt ones. You can alternatively unpack the boot image and repack it with your own kernel after building AOSP.

Otherwise, follow the AOSP instructions for building for your device as per http://source.android.com/source/building-devices.html.

via Dan swagger
[Android Software Development] dswaggz:
What it is: What is SE Android?

Security Enhanced (SE) Android is a project to identify and address critical gaps in the security of Android. Initially, the SE Android project is enabling the use of SELinux in Android in order to limit the damage that can be done by flawed or malicious apps and in order to enforce separation guarantees between apps. However, the scope of the SE Android project is not limited to SELinux.

SE Android also refers to the reference implementation produced by the SE Android project. The current SE Android reference implementation provides a worked example of how to enable and apply SELinux at the lower layers of the Android software stack and provides a working demonstration of the value provided by SELinux in confining various root exploits and application vulnerabilities.

SE Android was first publically described in a presentation at the Linux Security Summit 2011. The slides from that talk can be found at http://selinuxproject.org/~jmorris/lss2011_slides/caseforseandroid.pdf.

Some distinctive features of our SE Android reference implementation in comparison to prior efforts of which we are aware include:

Per-file security labeling support for yaffs2,

Filesystem images (yaffs2 and ext4) labeled at build time,

Kernel permission checks controlling Binder IPC,

Labeling of service sockets and socket files created by init,

Labeling of device nodes created by ueventd,

Flexible, configurable labeling of apps and app data directories,

Userspace permission checks controlling use of the Zygote socket commands,

Minimal port of SELinux userspace,

SELinux support for the Android toolbox,

Small TE policy written from scratch for Android,

Confined domains for system services and apps,

Use of MLS categories to isolate apps
[Samsung Galaxy Gio GT-S5660] pego149:
Is this phone supported tv out because this phone has 4 pin jack

Thank for your answers.:)
[Samsung Galaxy Gio GT-S5660] shiftyHungary:
No, and I don't really see any reason to connect the phone to TV, since it don't have an HDMI output, and it can't play DiVX videos.

Still, you can connect your phone to your sound system by a jack-jack cable, and the sound system's AUX plug. I'm using a 5.1 audio system like this, and it is great to listen to my music like this. You should give it a shot.
[Android Themes] SiccaGm:
moved thread
[Verizon Droid Charge] ferny_dx:
I noticed on opensource.samsung.com that there are 2 .zips that are available to download,

SCH-I510 Opensource.zip <---- EE4B

SCH-I510 Opensource.zip <----??

SCH-I510-VZW Opensource.zip <---EP4D

one clearly says its ep4d but the other one doesn't say anything and it has the same title as the one before it that says ee4b

did you guys already look into those files, i know there was a release you guys saw but i could never find out if those were it as they do not show release dates so i dont know if any of those are recent, i have read that the kernel source samsung released was not working, might they have released something else here?
[Verizon Droid Charge] kvswim:
Could be the one before EE4. You would have to wait for imnuts or jt's input.
[Verizon Droid Charge] imnuts:
The non-labeled one is for ED1/ED2, the original firmware from the device.
[Verizon Droid Charge] kvswim:
I was right!
[Verizon Droid Charge] ferny_dx:
Thanks for clarifying man, lately ive had spare time so I've been trying to be more active in the community, ive been trying to learn more advanced stuff but i didn't know where to start :P, i stumbled upon that firmware issue while eyeballing some threads
[Verizon Droid Charge] ferny_dx:
Hehehe yup
[Sony Ericsson XPERIA X10 Mini] simon_cbb:
Hi there, Xperia minix10, CM7-2.1.6

Left my phone on charge overnight to find it extremely hot in the morning.

It cooled down after a while, all good for the day. In the evening, suddenly, will not stay on for a full reboot.

I feel that it might be soft-ware specific because it will hold charge and run the phone for the entire time that I'm in recovery doing restore/back-up etc but as soon as I try and run re-boot, it will start up and then without warning, will turn off.

Have tried everything including re-installing CM7 and nothing works.

Anyone else? Advice?

Thanks.
[Epic 4G General] TeamERA:
Just sharing this for someone.

http://wtogami.blogspot.com/2012/01/hawaii-android-automatic-time-zone-bug.html

edit= I guess the link would help, sorry.

...Say goodbye to SOPA/PIPA and CiQ in 2012...
[Epic 4G General] k0nane:
Not sure what this is about, but SMS Time Fix is awesome for those places where Sprint is too lazy to set timestamps properly.
[Epic 4G General] TeamERA:
True, dont know the whole story, but I guess if you live in Hawaii it would be apparent lol.

Sent from a phone with kNOw CIQ ;)
[EVO 4G Accessories] SilverStone641:
http://www.amazon.com/Lexar-MicroSDHC-Memory-Reader-LSDMI32GBSBNAR/dp/B004AM610M/ref=sr_1_2?ie=UTF8&qid=1327004584&sr=8-2

Found this via AndroidPolice. Not sure how long it'll last. I've already ordered a pair. Enjoy!!
[EVO 4G Accessories] guitar jesus:
Back up to $51, damn't!
[EVO 4G Accessories] alil2cul4u:
Back down to $37.67 as of 11PM EDT April 17th
[Samsung Galaxy Nexus] ninjai117:
For whatever reason, all my photos I take look blurry. They seems slightly out of focus. Is this a known issue? Is this a software or hardware issue?

Currently I'm running 4.0.3 on the Kang ROM, GSM GN.
[Samsung Galaxy Nexus] droidmarc:
I noticed on my nexus the shutter speed is usually at 1/15. This is so slow that anything that moves will be blurry.

(i am not talking about shutter lag)
[Samsung Galaxy Nexus] RogerPodacter:
yes it's very common. here's the deal, on 4.0.1 camera you can hold the circle button which focuses center and takes superb crisp images. the touch to focus gives blurry images.

in 4.0.3 google removed that feature that existed in 4.0.1 so now its near impossible to get good crisp images anymore if you are on 4.0.3. ard compiled the 4.0.1 camera apk for 4.0.3 and you should try using that.

i'm still on 4.0.1 for this reason.
[Samsung Galaxy Nexus] ninjai117:
Weird, I was on 4.0.1 when I posted this. Since then I went to the open kang rom and it's been better and it's based on 4.0.3. Maybe they did something in this rom to fix it? I'm not sure.