Related
PLEASE NOTE: If you are using a Canadian handset, I recommend switching over to my JL2 based ROM. It's the same speed (if not quicker), and I will be providing much more updates for it. The ROM can be found here: http://forum.xda-developers.com/showthread.php?t=906977
News
12/23/10 - v0.2 released! Includes an error-checking script to prevent possible errors from occuring, new Steam recovery, wipe and non-wipe versions and more! Check the changelog for more info.
12/22/10 - v0.1, initial beta release
Hey everyone,
This is a rom which aims to provide the absolute best user experience by being extremely quick without sacrificing any necessary features. The majority of Samsung bloatware is removed, however a good portion of the pre-installed apps are left untouched. This ROM is based on XXJPY (Froyo 2.2.1).
If you have any questions prior, while, or after installing this ROM, please read the first few posts, as I'll try to address every possible (major) problem which can occur. If, after reading the posts, you are still encountering a problem, please reply to this thread being as detailed as possible. This allows me to fix problems quickly and easily.
Now, this is my first ROM, so there are bound to be a handful of bugs. However, I've been using this ROM for a few days and have yet to encounter any major problems.
Note: Please don't complain about Quadrant, Linpack, or any other pointless benchmark scores. If you've used the ROM and it's sluggish, by all means tell me, but don't base your opinion of the speed merely on a benchmark.
Okay, so what now?
1. Download and Install Instructions
2. Changelog, To-Do
3. FAQ and Problems
4. Screenshots, Media, User Comments
Features
Based on XXJPY (Froyo 2.2.1)
Patched Speedmod kernel, version K12 hz=256(allows you to mount on computer without problems)
Steam multi-touch recovery: update.zip on SD card
Added an error-checking script which prevents errors when installing [thanks Darkyy!]
All-black Gingerbread theme (saves battery)
Fully deodexed
Fully zipaligned
Fully updated Google Apps (YouTube, Flash, Market, Gmail, Maps)
Latest Su and Busybox
All protected apps in market - modified build.prop
Big APN list, which allows instant internet + MMS access
Integrated ClockworkMod Recovery
Stock AOSP Lockscreen
Bell UGJK3 Modem
Backlight Notifications
Added Applications:
Nexus S Live Wallpapers
Swype v 2.15 (Newest)
Launcher Pro
Optional: Gingerbread Keyboard (install from SD Card)
Removed Applications:
AllShare
Diary
Aldiko Reader
Press Reader
Layar
Thinkdroid
Write and Go
Credits (in no particular order)
-Hardcore for the kernel
-santiemanuel for the Nexus S Live Wallpapers
-vukandric for the theme
-Darkyy for help on the update script, and for generally being awesome
Download and Install Instructions
Downloads
Latest and Greatest
-v0.2: seeARMS XXJPY (12/23/10)
Wipe: http://www.multiupload.com/L9SUOBKO88
No Wipe: http://www.multiupload.com/9F5E89AYTP
-v0.1: seeARMS XXJPY (12/22/10)
http://multiupload.com/G6XTJF07MO
Modems
To flash these modems, use Odin and select the "modem.bin" file in the PHONE box. Go to Settings -> About on your phone after flashing and look at Baseband to ensure it flashed correctly.
JL2: http://www.multiupload.com/TC1ME8VB20
JK4: http://www.multiupload.com/3HOKWMBHO2
Installation Instructions
Before installing, disable any lagfixes (which can typically be done by booting into recovery mode and selecting "Disable Lagfix").
Also, if you wish, backup everything! Perform a NANDROID backup in recovery, backup your music, files, etc. In case something goes wrong (it will eventually), you'll have peace of mind.
Please note: this rom will wipe all your data. It will not, however, format your internal or external SD cards. This means you'll lose apps and settings, but not music, movies, etc.
Lastly, I recommend performing a factory reset before installing any new rom.
If you're running a previous version of my ROM, feel free to install the non-wiping version. However, if you're switching roms, I recommend running the standard version, which will erase all data.
1. Download and copy this file to your internal memory card.
2. Boot into recovery, and select "Install zip from sdcard".
3. Select "Choose zip from sdcard", and scroll to the ROM.
4. Select OK, and wait for the file to flash.
5. Reboot. This reboot will take a while (upwards of 2-5 minutes), so be patient and don't shut off your phone!
Congratulations, you've successfully flashed!
After it boots, I'd recommend doing a few things in order to allow your phone to be as quick as possible:
1. Boot back into recovery, select "Advanced SpeedMod ULK Features". Choose "LAGFIX options", then "Faster: EXT4 ALL". This applies a lagfix, and converts the partitions into the faster EXT4 filesystem.
2. In recovery, go back to the Advanced SpeedMod ULK Features menu. Choose "TWEAK options", and enable every tweak. For more information about these tweaks, see HERE.
Also, window animations are disabled by default. You can enable them by going into settings -> Display, and selecting Animations.
3. If you'd like the Gingerbread Keyboard, open up the My Files application and navigate to the directory "Gingerbread_Keyboard". Open up the .APK file and install as usual.
Changelog And To-Do
Changelog
v0.2
-Google Voice Search updated
-Added option to install gingerbread keyboard
-Updated kernel version to K12
-Added error checking script - with help from Darkyys rom (This prevents possible errors when installing)
-added nowipe and wipe versions
-Modified build.prop to allow all protected market apps
-Added Steam recovery - check FAQ for info on how to access it
v0.1 - Initial beta release
To-Do
-Gingerbread Keyboard
-Extended Power menu
-Support for different themes
-Stock application pack (available for flashing through CWM)
-Better modem (JL2? JK4?)
-Faster browser
-Modded SMS Application
-Modded Camera Application
If there's anything else you'd like to see in this ROM, just ask.
FAQ And Problems
FAQ
I'm on stock Froyo and I have 3e recovery!
Click to expand...
Click to collapse
No worries. Follow these steps:
1. Download Odin from here.
2. Download the Speedmod kernel for whichever Android version you're running. Make sure to download the Odin kernel, not the CWM one!
3. After downloading, extract the .TAR file from the file you just downloaded.
4. Open Odin, and turn off your phone. Connect your phone to your PC via USB, and enter download mode by holding volume down + home + power.
5. Odin should detect your phone. Load up the .TAR file in the "PDA" box in Odin. Make sure the other boxes are left blank. Untick "Repartition". Start flashing.
6. Your phone should automatically reboot with the new kernel! To double check, shut it off and boot into recovery. If you see CWM recovery, you're successful!
7. Now you're required to download the patch for the Speedmod kernel, which will allow you to copy the ROM over to your internal SD card. If you don't install this patch, the internal SD card will be detected as a CD drive, and will be read-only. The patch is able to be downloaded from HERE. Simply copy this patch to your SD card, boot into CWM, and flash it using "install zip from sdcard". After doing this, follow the normal steps to install this rom!
I'm encountering force-close issues, and general app issues right after installation.
Click to expand...
Click to collapse
Simply perform a factory reset. Clear the cache + Dalvik cache in recovery as well, if you'd like.
What's this steam recovery and how do I access it?
Click to expand...
Click to collapse
Steam recovery is a new, semi-functional multi-touch recovery created by sztupy. This recovery has all the features the standard CWM one has and more. Check his thread for more info.
Please note: Because (currently) the only Steam-compatible kernel is based on a much older base version (ie: not XXJPY), a small amount of features are incompatible, such as lagfix options, kernel options, etc. However, the majority of features (such as mounting, wiping, etc) are working just fine. I'm working on getting everything working; as soon as it is, it will fully replace CWM on this ROM.
To enable it, just boot into CWM and go to "Apply sdcard: update.zip". After doing this, it will boot into the new Steam recovery. You must do this every time you want to access it.
My GPS isn't working! It takes forever to lock and displays my position inaccurately!
Click to expand...
Click to collapse
Try clearing the GPS data on your phone. Do the following: (Original poster unknown. Reposted by dpvu.)
1) Enter *#3214789650# into the dialpad.
2) Under "Application Settings" set the Start Mode to Coldstart.
3) At the main menu "Delete GPS Data".
4) At the main menu "Get Position Test".
If you're still not finding many satellites try setting Operation Mode to "MS Based" in the "Application Settings". I did all of this then set the GPS back to hot start.
Screenshots, Media, User Comments
Screenshots
Click for a larger image.
User Comments
°Dexter° said:
Impressive rom seeArms, really really fast...faster than others, indeed.
...
Very good work,no major issues by now,i'm eagerly waiting for next release
Click to expand...
Click to collapse
Existence. said:
it's runnin great, thanks seeARMS. can't wait for the JL2 version. i really dont wnt to brick my phone and i think the JL2 version fixes the SD dying problem so i cant wait!
Click to expand...
Click to collapse
hi. looks good. i will test it now and give feedback after.
thanks for your work and keep going.
btw: why are using this modem?
gonna try this ROM out!
Quadrant score? I will try it, looks good.
gonna try this release soon, good job
fenerbuuh said:
hi. looks good. i will test it now and give feedback after.
thanks for your work and keep going.
btw: why are using this modem?
Click to expand...
Click to collapse
I'm using this modem because I need the Canadian band, because, well, I'm located in Canada. And, according to this guide, this modem is very good on battery life and reception.
In later versions of this ROM I'll most likely include a different modem (or a flashable modem). Something like that.
Any modem you'd prefer to see included?
Place this zip into PDA on Odin and upload it.
Any chance to work this?
I would like to try this rom,but I've 3e and I can't do it the way been described...
Hey man, to bad i flashed Docs jpy rom just yesterday evening, and dont want to change rom on a daily base. But ill test it for sure just because id not have to change kernel afterwards...
so thanx for your work and keep it coming man...
Mparmpa-Nikos said:
Place this zip into PDA on Odin and upload it.
Any chance to work this?
I would like to try this rom,but I've 3e and I can't do it the way been described...
Click to expand...
Click to collapse
Flash the SpeedMod kernel (or any kernel which supports froyo and has integrated Clockworkmod Recovery).
I'll add a guide to do this in the FAQ.
seeARMS said:
Flash the SpeedMod kernel (or any kernel which supports froyo and has integrated Clockworkmod Recovery).
I'll add a guide to do this in the FAQ.
Click to expand...
Click to collapse
I'm looking forward to this,man!Thank's
Mparmpa-Nikos said:
Place this zip into PDA on Odin and upload it.
Any chance to work this?
I would like to try this rom,but I've 3e and I can't do it the way been described...
Click to expand...
Click to collapse
No way man, but you could get hardcores kernel as an odin package, it comes with cwm recovery, flash that first and then use cwm to install this rom.
Mparmpa-Nikos said:
I'm looking forward to this,man!Thank's
Click to expand...
Click to collapse
Done. See the FAQ.
Welcome new devinteresting rom,gonna try it...
Thank you
Welcome seeARM!
Nice to see another dev helping the SGS Community.
Feel free to PM me if you have a question or anything else
- darkyy.
Sounds good
Will likely give this a try as the XXJPX modem causes me to lose my 850 WCDMA connection all too frequently (even though I've enabled it). Just curious if there are any problems with Market, or will it come updated to 2.2.7 already?
Cheers mate!
Darkyy said:
Welcome seeARM!
Nice to see another dev helping the SGS Community.
Feel free to PM me if you have a question or anything else
- darkyy.
Click to expand...
Click to collapse
Will do Darky, thanks.
canad1an said:
Will likely give this a try as the XXJPX modem causes me to lose my 850 WCDMA connection all too frequently (even though I've enabled it). Just curious if there are any problems with Market, or will it come updated to 2.2.7 already?
Cheers mate!
Click to expand...
Click to collapse
Market comes updated to version 2.2.7 already. I haven't had any problems with it at all.
This thread is reserved for nightly builds of CyanogenMod Rom for Samsung Galaxy S.
All Samsung Roms are running ontop of BML/RFS, CyanogenMod 7 does NOT.
It runs on MTD/yaffs2 (like Nexus One) which means you're not able to flash any kernel or run any filesystem you want. Use it as it is.
Only data partition, which is on movinand, is ext4 like on speedmod or voodoo ("lagfix").
CyanogenMod is a free, community built distribution of Android 2.3 (Gingerbread) which greatly extends the capabilities of your phone.
Code:
** These CyanogenMod builds are highly experimental and unsupported.
**
** Please refrain from submitting bug reports for any issues
** you may encounter while running one of these builds.
**
** Submitting bug reports on nightly builds is the leading
** cause of male impotence.
What are Nightly builds? Auto compiled builds of the latest CyanogenMod source from github. This version change each night and aren't officialy supported.
If you find bugs/issues you can/must discuss here (do not submit nightlies bug on CyanogenMod issue tracker).
INSTRUCTIONS:
- First time flashing CM 7 to your Galaxy S (or coming from another ROM)?
Root your device and install ClockworkMod Recovery.
Reboot into Recovery using 3-button-combo
Do a Nandroid backup!
WIPE (wipe data/factory reset + wipe cache partition)
Install the ROM from internal sdcard using ClockworkMod Recovery
Optionally install the Google Addon
- Upgrading from earlier CM7?
Do a Nandroid Backup!
Install the ROM (your Google apps will be backed up automatically)
There are no Google Apps bundled with CM ROMs, because Google asked Cyanogen to remove copyrighted apps, after flashing rom don't forget to flash Google Addon package if you want it.
Latest version: http://download.cyanogenmod.com/?device=galaxysmtd
Compatible Radio Images (>= Nightly 15): http://codeworkx.de/download/cyanogenmod/
Supported devices: GT-I9000, GT-I9000M, GT-I9000T
before flash is recommended to check the md5sum
FREQUENTLY ASKED QUESTIONS:
http://forum.cyanogenmod.com/topic/24169-faq-cm7-on-the-samsung-galaxy-s/
CYANOGENMOD WIKI:
http://wiki.cyanogenmod.com/index.php?title=Samsung_Galaxy_S
HOWTO BUILD FROM SOURCES:
http://wiki.cyanogenmod.com/index.php?title=Compile_CyanogenMod_for_GalaxySMTD
ADDITIONAL INFORMATIONS:
Maintainers:
- atinm - http://twitter.com/atinm
- codeworkx - http://twitter.com/codeworkx
- coolya - http://twitter.com/dumdidum
- guiperpt - http://twitter.com/guiperpt
- unhelpful - http://twitter.com/unhelpfulone
Irc:
- Host: irc.freenode.net:6667
- Channels: #cyanogenmod, #cyanogenmod-dev, #cmsgs
Changelog:
- Generic Changelog
- CyanogenMod Source Twitter
- Device specific Changelog by igor.tonky
Please visit the CyanogenMod Wiki for step-by-step installation walkthroughs and tons of other useful information.
Thank you to EVERYONE involved in helping with testing, coding, debugging and documenting! Enjoy!
If You Have Any Questions, Please Refer To This
CM7 QUESTIONS & ANSWERS XDA THREAD
http://forum.xda-developers.com/showthread.php?t=1067074
Regards,
~drz
have i ever told you i love you? i'm pretty sure i have but i'd just like to tell you again. i'm sorry for this offtopic post but i'll edit it later to something useful. just wanted to show my affection.
This should be it since the beginning.
Clean thread. That's how I like it
Excited for the Coming Soon patch!
Reboot Recovery
Woah! Can't wait to try this.
The quick troubleshooting post.
This post contains a compilation of problems/issues and answers provided in this thread and earlier threads. Not all answers are tested by me and I will in no way guarantee that this wont mess up your phone.
You know, watch your kittens. They might be eaten by following the advice written down here.
DETAILED INSTALLATION INSTRUCTIONS CAN BE FOUND HERE.
rschenck wrote a very nice (and updated) guide for how you install CM7 on your SGS these days.
Things have changed quite a bit recently, so even if you installed it two weeks ago, you may want to check this one again.
What do people mean with "correct" bootloader? How can I make sure I have the right one?
Do NOT install directly on top of existing Samsung 2.3.3 firmwares or other firmwares based on this (like Darky's 10). Similarly, don't install directly on top of Eclair.
See this very easy guide on the android soul for flashing XXJPU, which is Froyo with the correct bootloaders needed..
I'm not sure I understand these procedures. Can you draw it out for me?
Anticipating this very question, rschenck actually did draw out a flow-chart for you.
See here.
But I'm not using the I9000, I'm using something else...
codeworkx provided a reference list you can check to ensure you are getting the right files.
After flashing the initial CM kernel I can't get CWM Recovery to work. It just displays some weird image
CWM Recovery might have different keymappings from the ones you are used to.
- Volume keys: Naviagte up and down in menus
- Power button: Select item
- Home key: Show/hide menus
If you are only seeing a weird image, chances are you've hidden the menu by pressing the home key. Try pressing it again
I can't find Cyanogenmod nightlies in ROM Manager
Yes. CM7 for the SGS is now mainlined and supports ROM Manager for nightlies, should you have the premium version. If you have the Premium version, follow these very graphic instructions to configure ROM Manager for nightlies.
To install from MIUI (courtesy of runedrune)
- Reboot into recovery using 3-button-combo
- Choose "mounts & storage" and format system, data, cache, datadata
- Do not apply the initial-file.
- Apply the latest update
- Apply the latest gapps (which can be obtained here. You want the one with -gb- in the name )
- Done. Reboot
Odin doesn't recognize my phone anymore and I want this fixed in case I mess something up
You will probably need the Nexus S drivers (which supposedly is really just some updated Galaxy S drivers).
If Odin for some reason don't see your device when connected, make sure the old Galaxy S drivers are uninstalled and removed. Bilboa1 gives some good hints about how to make sure your drivers are actually fully removed. Do check this before proceeding to install the Nexus S drivers.
After you have installed the Nexus S drivers, plug in your phone. Windows should now install some drivers, but you are not done yet. When using download-mode your phone will show up a little differently to Windows, so put your phone in download-mode and plug it in, with neither Kies nor Odin running. You will probably see Windows installing some more drivers.
After doing this, Odin should hopefully be able to recognize (and flash) your phone.
IS THIS "FOR EVERYDAY USE" NOW?
It depends. If you have to ask, it probably isn't.
I've flashed this and decided it is not ready for me. How do I flash back to stock ROMs?
Get the appropriate firmware you are interested in, flash as usual using Odin, but check re-partition and use the 512 pit-file.
For pre-rooted stock-images, you can use EZBase as shown here (also includes download links).
OTHER STUFF / KNOWN ISSUES AND SOLUTIONS
Please take a look here to see if your issue is mentioned and has a known solution before posting.
After flashing CM7 I get strange colours on my screen during boot
You do not have the correct bootloaders. Basically flash 2.2.1 following this article and then redo the CM7 installation. All should be fine.
Guys! Guys! I cannot find Android Market!
Google stuff is not included in CM7 by default. Download and apply latest gapps from CWM. You want the "universal" one with "-gb-" in the name.
But I want the latest gtalk with video and all that fancy stuff
got_milk was nice and uploaded some stuff. Beware though that lots of people are reporting this to force-close a lot, and that's not just on SGS CM7.
Can I run Samsung apps like Memo, Camera etc on this firmware?
No. Sorry. All Samsung apps depend on TouchWiz libraries which can only be found in Samsung firmwares.
How do I get additional themes for CM7 themes chooser?
Check the themes forum here on XDA or search for "CM7 themes" on Android market.
Once installed, the themes will be available in the themes chooser yes. According to the devs should reboot to fully apply the theme, but if you want to avoid reboots Android market might have something for you.
Things used to work, I applied a nightly update and now everything force-closes
Try wiping cache and dalvik cache in CWM. You should do this every time you install a new update.
Does CM7 need a lagfix?
CM7 uses ext4 (for /data) and yaffs2 (for everything else). CM7 does not use Samsung's RFS which was the main cause of poor performance on Samsung firmwares.
So no, your system is already lagfixed, you don't need to apply a lagfix and according to the developers very bad things will happen if you try to apply one anyway.
My current ROM has a lagfix. Do I need to disable that?
Probably not.
If you have a 2.3.3 ROM with 2.3.3 bootloaders, you will want to do a full wipe to stock 2.2.1. See above. In this case you no longer have a lagfix anyway and don't have to worry about it.
If you have a non-2.3.3 ROM with a lagfix, you don't have to disable it. All your partitions will get wiped by the installer anyway and so will your lagfix.
For whatever reason, I want to flash a custom kernel
You can use custom-kernels, but CM7 is a work in progress with new kernel-revisions popping out with every release. Make sure you flash a kernel which is compatible with the nightly you are running. Also: Do NOT flash via Odin, flash via CWM.
rschenck has a very good post on this.
If all you want is a "voodoo kernel" for voodoo sound, just (buy and) install Voodoo Control Plus from the market. It will load the required kernel-modules while you can stay on the stock kernel, making the lives of the developers much easier should you encounter bugs.
Is it possible to flash my own CSC from recovery after installing cm7?
According to the devs, this should not be needed.
Flashing other modems/radios
(Courtesy of GrimVarg: http://forum.xda-developers.com/showpost.php?p=13399590&postcount=8117 )
Odin will not work and it might **** **** up. The reason is that Odin and heimdal does not understand the CM partition layout and will just write the modem where it thinks is should be. Overwriting other stuff in the process.. So you need to use the specific update zipfiles on teamhacksungs sourceforge page
Click to expand...
Click to collapse
Instead of using Odin, download radio-packages from the following link, transfer to your phone and flash via CWM:
http://sourceforge.net/projects/teamhacksung/files/galaxys/
I want to keep my 850 band, and I don't recognize any of the modems on the sourceforge page
Lorssoth says "use KC1" and robbiev80 posted some download links you might be interested in.
Does external SD card work with cm7? Thanks!
It does. Make sure you have the proper bootloaders before installing as mentioned in the first part of this post. EZBase can be used for this.
External SD card will get mounted as /mnt/emmc. This may not be visible to all apps. If you desperately need the contents visible to apps only looking in /mnt/sdcard, create an empty directory there and remount the /mnt/emmc there as well:
Using either the terminal emulator or adb shell:
Code:
su
mkdir -p /mnt/sdcard/external_sd
mount /dev/block/vold/179:9 /mnt/sdcard/external_sd
Note: This is only a temporary fix for when needed. It will cause issues when you try to use USB sharing later. Write the following to get things back to normal:
Code:
umount /mnt/sdcard/external_sd
USB sharing doesn't work
Try installing the Nexus S drivers, instead of the Samsung ones.
After installing this camera doesn't work
Try locking and unlocking your phone. No really.
After installing this I cannot get any data-connections apart from wifi
There is a problem with RIL (radio interface layer)-polling. Lock and unlock and you should be OK.
If this sounds cumbersome, mobilescooby claims that installing Juicedefender somehow fixes this for him and that he no longer needs any lock and unluck boot-rituals.
This issue should now be resolved.
After doing this I still cannot get any data-connection apart from wifi
You might need to configure APN settings. Normally your network-provider will have this information on their homepages and some even offer to send them to you over the network.
After installing this I cannot send and/or receive MMSes
See above: You might need to configure APN settings. Check your provider.
After installing CM7 I cannot connect to my wifi-network
It might be related to what channels you have enabled on your phone. If your wifi network is using channel 12 or higher, you may need to enable those channels on your phone.
Go to Settings/Wifi & Network/Wifi settings/Advanced/Regulatory domain. And try not to be in violation of local laws with regard to channel usage
After installing CM7 I cannot connect to 802.1x EAP Wifi networks
This is seemingly an issue with lots of custom kernels and even some of the Samsung Firmwares. Yours truly can't get it to work at all, not on CM7 nor Samsung's JVB firmware.
Other people have reported that forgetting the network and adding it manually, by entering the SSID (with correct casing) and filling in all the details themselves have solved their problems.
YMMV
After installing CM7 I cannot charge my phone to 100%. WTH
No actual firmwares allows you to charge the battery to 100%, but stops a little bit before it reaches that point. This is to protect the battery from overcharging and should (in the long run) give you much better battery-life.
While stock firmwares from Samsung shows that the phone is 100% charged, this simply isn't true and is just UI-candy to make you all feel comfy. It's really charged to something around 94-98 percent.
So if your phone stops charging around that point, everything is normal, and the only new thing is that your phone is no longer lying to you
My GPS performance is terrible
Welcome to the world of Samsung Galaxy S GPS flux. Things you can try to improve on this includes the following:
- Install faster fix from Android market. Ensure you have the best time-server for your area chosen.
- You can also try AngryGPS, which siberian tiger was nice enough to upload.
- If all else fails, you can also try to flash a radio with a good GPS reputation. For flashing radios, see the appropriate section of this post. For some detailed post about the different radios eeyunopper posted this link and this link. (With ZSJPG I am getting decent result, YMMV)
Auto brigthness is kinda not-worky
You can try the presets outlined by Arkymedes right here.
How do I configure proxy settings?
(Thanks to runedrune)
If you are used to looking for proxy settings under Settings/Wifi & Network/Wifi settings/Advanced, you wont find it there.
Using either Launcher pro/ADW Launcher or another launcher which lets you create shortcuts to activities:
* Long hold on some open space on your launcher
* Select (Custom) Shortcut
* Select Pick your activity/Activities
* Scroll down to settings and click this
* Scroll down the long list and you should find proxy settings
You now have a shortcut to configure proxies as usual.
This "headphones mic on mute + instant music after call bug" is really irritating
If you are using Samsung or Nokia headsets, this is due to a problem on their part. See Arkanius' post right here.
Other things I should be aware of?
- Don't use 2G/3G data-switching. Period. At least not while the data-connection is active.
Not trough widgets, tasker or any other means. Seriously. Should you do this, you might end up having to restore nandroid backups or doing factory resets.
This report has details on more sophisticated ways of cleaning up which may lead to less data-loss, although not everyone can get it to work.
*subscribes*
nice work with the GPIOs, camera and other parts !
Lol, having two threads will confuse a lot of people. I look forward to all the questions relating thus...
sent via potential brick...
eeyunopper said:
Lol, having two threads will confuse a lot of people. I look forward to all the questions relating thus...
sent via potential brick...
Click to expand...
Click to collapse
I've already notified the mods to close / lock the other one ...
Good job on the clean house, everything is working great on my phone and very speedy
Mortify1 said:
Good job on the clean house, everything is working great on my phone and very speedy
Click to expand...
Click to collapse
The same for me My phone is working so great and very very speedy
Probably a stupid question but to switch from MIUI to cyano that steps should I follow?
Only this ? :
-Reboot into recovery using 3-button-combo
-Choose "mounts & storage" and format system, data, cache
-Apply zip from sdcard: cm7-DEVICE-initial-XXXXXXXX.zip
-Do a factory reset / data wipe!
-Reboot
-Install the latest update after a reboot!
Tantrico I said:
Probably a stupid question but to switch from MIUI to cyano that steps should I follow?
Only this ? :
-Reboot into recovery using 3-button-combo
-Choose "mounts & storage" and format system, data, cache
-Apply zip from sdcard: cm7-DEVICE-initial-XXXXXXXX.zip
-Do a factory reset / data wipe!
-Reboot
-Install the latest update after a reboot!
Click to expand...
Click to collapse
format /system /data /cache /datadata and then flash the latest update and the latest gapps.
I'm waiting the upcoming improves on camera in great expectation.
Tantrico I said:
Probably a stupid question but to switch from MIUI to cyano that steps should I follow?
Only this ? :
-Reboot into recovery using 3-button-combo
-Choose "mounts & storage" and format system, data, cache
-Apply zip from sdcard: cm7-DEVICE-initial-XXXXXXXX.zip
-Do a factory reset / data wipe!
-Reboot
-Install the latest update after a reboot!
Click to expand...
Click to collapse
no
after format system/data/cache
just apply the last update
runedrune said:
format /system /data /cache /datadata and then flash the latest update and the latest gapps.
Click to expand...
Click to collapse
Only this file ?
update-cm-7-05012011-NIGHTLY-GalaxyS-signed.zip
I do not have first place this
cm7-galaxys-initial-20110410.zip
and after the update ?
Nice things are comming... I hope for battery improvemant and radio FM. Since we got GPS, Compass is not so important but nice additional that save battery/make quicker fix.
Codeworks, do you got any rodemap?
Tantrico I said:
Only this file ?
update-cm-7-05012011-NIGHTLY-GalaxyS-signed.zip
I do not have first place this
cm7-galaxys-initial-20110410.zip
and after the update ?
Click to expand...
Click to collapse
nope. just flash that file. i made the same switch from miui to cm7 two days ago
@codeworkx , if reboot in recovery works = nightlys updates for ROM Manager? !
Enviado desde mi GT-I9000 usando Tapatalk
I did this for the EVO 4G so I'm going to do it for the E4GT. After watching people ask and sometimes search and ask again for the same things over and over, I thought it would be a good idea to have one thread to hold all of these valuable resources, basic tips and tricks. Many of these links will be found in multiple locations, forums, threads and posts and I will try to keep this single thread updated with links to as many resources as we can come up with.
There are already several great posts like this. Barnacles has the incredibly informative E4GT Wiki stickied in General (hopefully this can contribute to that wiki), Qbking has his threads with links to his excellent video tutorials, and sfhub posts up all sorts of goodness with his Auto Root and stock tar threads. But I didn't really find a thread devoted to just basic methods and problem solving. This thread strives to provide a collective space for learned knowledge, quick tips and fixes for common issues.
If this isn't needed or wanted, it will surely fall to the XDA basement no harm no foul If it has any value, then hopefully it will help a few people in their endeavor to create the best personal Android experience possible!
I take no credit for many of these items, I have only gathered and edited most of them for a one-stop easy shop opportunity. All fixes have been edited for clarity and efficiency with links wherever possible. Please let me know of any broken/missing links or errors. Links to the original source are provided when possible. I have not run all of these fixes personally, but try and confirm fixes I don't test by finding at least three user corroborations for each.
If you have questions on a specific fix with a Source listed, I recommend directing questions/issues to the original source for best results. Otherwise feel free to ask here and we may be able to assist. ~js
Like my EVO Owner's Toolkit, this is a work in progress and a living document. I try to keep it up to date and appreciate new information, suggestions and knowledge which can be added to the OP's. I always provide credit when possible/applicable.
Epic 4G Touch Owner's ToolkitUpdated: January 6, 2011
Always make a NANDROID before you do anything!
If you have any questions/needs that are not listed here, I recommend starting with a Search and reviewing ☞ ☆.☆. [WIKI] ROOT, ROMs, KERNELS, MODEMs, HOW-TOs
If you still have questions/concerns, post 'em!
E4GT HOWTO's
How to make a nandroid backup (as requested)
Make sure you have your setup where you want it (I usually update all my apps in the market and do a Titanium Backup before my Nandroid as well.)
Boot into recovery (Hold [Power]+[Vol. Up] or just Hold [Power] if your ROM supports boot menu)
Navigate to Backup and Restore and press [Power] (or [Home] soft key depending on your recovery version)
On next screen select Backup and let it do it's thing
Reboot and you are good to go.
*The backup will look something like 2011-12-26.03.00.15 and likely be in /sdcard/external_sd/clockworkmod/backup.
If you decide to rename the backup, make sure that there are no spaces in the name. (I.e. 2011-12-09_Calk_2.0_EG31 would be fine, while 2011-12-09 Calk 2.0 EG31 would be a no-no.)
Hands Free Activation A way to improve data speed and stability, address data or wifi issues, etc. (especially after flashing a new modem):
Make sure you are not roaming (WiFi is fine, even a poor signal is fine, but roaming can mess with things.)
Make sure you don't have system updates removed or frozen in titanium backup
Get your Master Subsidy Lock (MSL) code (Use Terminal Emulator and type "su" then "getprop ril.MSL" (case sensitive and if using swype make sure the "i" in "ril" doesn't auto capitalize. Use another kb if necessary.) **alternate method below.
Go to dialer and enter ##72786#
Enter your MSL and hit OK
On the SCRTN screen select yes
Phone will auto reboot and take you to Hands Free Activation
If you have an SD card, media scanner will do its thing first.
Re-activation will initiate, let it run (DO NOT TOUCH THE SCREEN, no need to Press OK it will continue on its own)
Phone will then update Profile, then PRL, (you can select cancel when it searches for Firmware update if you want)
Phone will reboot again
Also a good idea to pop out your battery for a few seconds (many have reported this helping and Sprint usually has you do this during the process.)
That should improve things.
**Alternate Method for obtaining MSL for those having trouble with original method after upgrading to ICS
Download the alogcat app from Market
Open alogcat. Press the hourglass and type "msl" and wait while it filters. The screen should go blank.
Press your Home button
Go to your dialer and enter ##3282#
When the menu pops up choose Edit and when it asks for your msl, enter 6 random numbers. You will get an error message.
Long press the home button to bring up recent apps and choose the alogcat app.
At the bottom of the list it will say "MSL result : XXXXXXX" where xxxxxx is your MSL number.
That's it.
(*Unfortunately MSL Reader app in market only works on HTC CDMA phones.)
Click to expand...
Click to collapse
How to boot into 'Safe Mode' should you need to for any reason
Hold Home softkey while rebooting
That's it you are in 'Safe Mode' (I don't know exactly what you can do in safe mode, but probably similar to Windows safe mode.)
Click to expand...
Click to collapse
How to extract an apk from a ROM/zip (you'll need a program like 7-zip, winrar, etc.)
Download the ROM/zip that contains the desired apk(s)
Double click the zip and it will open in your default zip program
Navigate to system/app and drag the desired apk(s) to an easy to remember location. (I use Dropbox or Minus, which makes the apk available on my phone without any further desktop steps.)
If not using a cloud storage option, connect your phone to your desktop and copy apk(s) to your SD
That's it, you now have the apk(s) on your phone and can proceed with double clicking and installing the app or if a system app to the next tutorial for installing a system apk.
Click to expand...
Click to collapse
How to remove a system apk w/Root Explorer (ROM Toolbox can also be used, but slightly different process):
Open Root Explorer (or ROM Toolbox Root Browser) and navigate to system>app
Mount R/W (top right in Root Explorer, R/W is on by default in ROM Toolbox)
If this is a system app, long press existing apk and either move (if you want to keep it) or delete (if you don't care)
Hit OK and your free of the undesired app.
CAUTION: make sure you research before randomly removing things or you are likely to bork something. A good list of items that have/can be removed successfully in naerok's incredibly streamlined ROM can be found in Post #3 here.
Click to expand...
Click to collapse
How to install a system apk w/Root Explorer (ROM Toolbox can also be used, but slightly different process):
Download or extract the desired app apk and place it somewhere on your SD where you can find it (I highly recommend Dropbox for this)
Open Root Explorer (or ROM Toolbox Root Browser or ES or Other) and navigate to /system/app
Mount R/W (top right in Root Explorer, R/W is on by default in ROM Toolbox)
If this is a system app, long press existing apk and either move (if you want to keep it) or delete (if you don't care)
If moving, navigate to the place you want to store the original apk using the Parent Folder line at the top
Paste to the desired location then go to the place with the new/replacement system apk
Longpress the replacement apk and choose copy or move
Navigate back to /system/app (should still be mounted) and paste the replacement apk
Longpress the replaced apk and select permissions
On the permissions pop-up leave all three in the first column (Read) checked, only the top item in the middle column (Write) checked and none in the third column, (Execute) and nothing else checked.
Hit OK and enjoy! Your permissions should now read (rw-r--r--)
Click to expand...
Click to collapse
How to extract a bootanimation from a ROM (you'll need a program like 7-zip, winrar, etc.)
Download the ROM/zip that contains the desired bootanimation.zip
Double click the zip and it will open in your default zip program
Navigate to system/media and drag the bootanimation to an easy to remember location. (I use Dropbox or Minus, which makes the apk available on my phone without any further desktop steps.)
If not using a cloud storage option, connect your phone to your desktop and copy bootanimation.zip to your SD
That's it, you now have the bootanimation zip on your phone and can proceed to the next tutorial for installing/replacing a bootanimation
Click to expand...
Click to collapse
How to replace/add a boot animation
Download or extract a bootanimation.zip
Place the bootanimation.zip on root of your SD card (or use a cloud app i.e. Dropbox, Minus, Box, etc.)
Make a copy of the bootanimation and name it sanim.zip and move that to your SD card as well
Open a root manager app (I prefer Root Explorer)
Navigate to system/media
Select Mount R/W (top right in Root Explorer, on by defauly in ROM Toolbox) then either delete, or move existing bootanimation.zip and sanim.zip
Navigate back to sdcard, then copy or move bootanimation.zip to system/media and then repeat with sanim.zip
Some people replace only the bootanimation.zip and others only the sanim.zip, but I find each of those methods seem to create issues if the kernel you are running does not support custom bootanimations by default. So I replace both zips and it has worked well on multiple ROMs/Kernels. If this doesn't work for you, try replacing each individually. One of the three methods will definitely work for your ROM/Kernel combo.
User 12MaNy has created a thread with several bootanimations available as well some methods for install
Boot animation sounds can be found/added at /system/etc/poweron.wav and /system/etc/1_Power_on.ogg (may be listed as /system/etc/poweron.bak and /system/etc/1_Power_on.bak if these have been "muted".)
Also make sure to check and see if your dev has already moded the boot ani setup as nerys71 discovered here.
Click to expand...
Click to collapse
How to hack custom bootanimation support (Via chris41g) Only works with source built kernels. Thanks dtm_stretch.
Rename /system/bin/samsungani to something else... (eg samsungani.old)
Rename /system/bin/bootanimation to /system/bin/samsungani
After that it will load whatever bootanimation is at /system/media/sanim.zip
Click to expand...
Click to collapse
How to add/restore/change bootanimation sounds (you'll need a program like 7-zip, winrar, etc.)
Open the ROM zip that you want to run
Navigate to /system/etc/ and look for poweron and 1_Power_on
If they appear as poweron.wav and 1_Power_on.ogg you are good to go
If they appear as poweron.bak and 1_Power_on.bak you need to rename them as above
If they don't exist, you will need to add them to this location or replace them with similar sized sound files of your choice. Make sure to keep the filenames and formats as above
Click to expand...
Click to collapse
Stuck at a black screen, bootanimation, etc
No need to jump through all sorts of hoops. Simply download and flash a different CWM Kernel. You can try it first by holding down [Power] + [Vol. Up] until it takes you to recovery (it may reboot once or twice, just keep holding.) If it never does take you into recovery, you can flash a kernel via Odin. Once you have the kernel flashed you will either be up and running on your new ROM or you can now go into recovery and flash the ROM of your choice.
*Assumes you were rooted to begin with as you are in this thread and have previously flashed the ROM.
Click to expand...
Click to collapse
Lockscreen/Reboot Issues
If you are having issues with reboots and resets and are using a 3rd party lockscreen or the native lock pattern, make sure that the selected custom lockscreen is "None"
Settings>Lockscreen Settings>Lockscreen Settings>Lockscreen style>None
Click to expand...
Click to collapse
SOME HOT LINKS TO OTHER GREAT HACKS, MODS AND FIXES
[How To] Upload a custom PRL to your Epic Touch 4G by R1ptide Thanks to TonyTurboII for the recommendation
I used to use a similar hack from Techknowfile back on the EVO 4G and it did work well, just make sure to be aware of the risks if you overuse data while roaming.
Click to expand...
Click to collapse
Always make a NANDROID before you do anything!
► New Modems - First, do not run out and flash the latest modem just for the hell of it. Use some restraint and think before you act. There are sometimes unknown hazards, such as the issue of no return from the EG31 modem to EG30 a few weeks back. Consider why you want the new modem. Are you having legitimate issues or do you just want the latest stuff? It's your phone, do as you please, just remember that you had a choice if something bad happens, like being stuck on an unofficial build.
► LoS issues - LoS issues really should be a thing of the past since the EK02 and EL13 modems emerged, but if for some reason you have not moved to those modems and you are having LoS issues flash a stock kernel! I prefer Rogue *STOCK* kernels, but pretty much any kernel listed as "stock" should help.
► Data/signal Issues - If you are having data/signal issues after flashing a modem, perform a Hands Free Activation, if that doesn't work, try pulling the battery for a few seconds (thanks Guillo1). If that still doesn't work you may need to call Sprint.
► Poor Battery Life - If you have poor battery life make sure you have calibrated your battery and given yourself several full charging cycles. And use either Battery Repair (Doctor Boost) ($2.69) or Battery Calibration (FREE). User evolart passed on this method as well: Best way to calibrate S2 Battery. I'm not quite ready to believe that calibration does nothing for us, but this is an alternative method to try for those who feel compelled. I sent messages to both app developers. I'll test and keep an eye out for other user's opinions and update this as necessary.
► Bootloops? -
Make sure that you have a default launcher selected and if using a 3rd party launcher that it is NOT set to auto update in the market as an update overnight would leave you without a default selected. (Thanks to 1BadHEMI, rickyq12 and playya for jogging my memory.)
If that didn't solve it and you are absolutely sure you wiped properly, you probably didn't so you might want to try that again. Recovery > Wipe Cache + Dalvik cache > Reboot (see Issues Flashing ROM below re: wiping)
If that doesn't work, flash a stock kernel via recovery or odin and start from fresh ROM again. This time let everything settle in before applying any changes (voltage tweaks, themes, mods, new apps, restoring settings, etc.)
► Issues Flashing ROM - If you are having issues flashing a ROM or an update here are some tips.
With some ROMs like Calkulin's ROMs, you generally do not need to wipe anything when going from one version to another. Just boot into recovery and apply the zip, his wipes for you. I have had the most success doing this and the Dev will note otherwise if the process changes. (It doesn't hurt to wipe cache + dalvik cache, so do that if you are fearful of not wiping anything.)
If coming from one ROM to another, you should wipe everything. I do it manually and use the Format_All zip, but you can do it anyway you like so long as everything (cache, dalvik, system, battery stats) gets wiped at least once. Some format system for good measure, I don't. Your choice.
If you have done either of these processes and are having issues it could be anything from a bad download to wiping issue to bad luck. Do it again and take a look at the Bootloops note above.
► Google Voice - when I answer my phone I get a recording where I have to press 1 to answer
Open Google Voice > Options (gear icon top right) > Voice Settings > Calls > Call Screening > toggle to "Off"
► Apps Issues - Apps missing, not working, acting strangely?
Reboot your phone
Reboot your phone
Reboot your phone
Fix permissions (ROM Manager > Fix Permissions or boot into recovery > Advanced > Fix permissions)
Clear app data (Settings> Applications > Manage applications > All > [the app] > Clear data)
Uninstall and reinstall the app
If it is something like Google music, Amazon Appstore, Spotify, etc. you may need to go to the web and clear some connected/authorized devices from the settings, there is a limit.
► Fresh Start - If you've tried everything else, try flashing the STOCK EG30 TAR or Stock EL13 TAR via Odin. Either will help you start fresh.
► More Links And a whole bunch more useful links in qbking77's thread.
► Post Logs - Super easy way to grab logs and post them for review. Install a log collector such as aLogcat and Pastebin from the market. Then run alogcat after the event, click share from the log and select Pastebin from the popup list. Copy the URL it provides you and send that or post it here.
GPS Fixes
Various fixes. If one doesn't work, try another. More posted as they come. Unfortunately, everything I have posted in this GPS fix section is sketchy at best, working for some not for others. Right now it is the best we have so it doesn't hurt to try, but remember, YMMV.
Using the Supersonic GPS Driver Thanks
Download one of the drivers below. (CM7 version shared by ebuechler3 and daryelv and "flash3" version shared by colorado_al, thanks to lunchboxVA for pointing it out.
Download GPS Status and Toolbox App from the Market.
Boot into Recovery (Hold [Power]+[Vol. Up] or just Hold [Power] if your ROM supports boot menu)
Wipe cache + dalvik cache
Flash the zip
Connect to GPS
Turn on GPS Status and Toolbox and let it get a fix
Turn on the map/nav app of your choice and let it get a lock
*Lock should be significantly faster than before the flash (mine went from just under 5 min. to about 11 seconds.)
You'll want to come back and try again later in the day to make sure it's still working. You may have to flash again when changing ROM's making mods. Good thing it's easy
UPDATE: user adma84 brings up a good point in that this driver does not appear in /system/lib/hw after flashing and I am actually unable to locate the driver anywhere in /system at all. I am going to see if I can get any sort of explanation, but as of now the jury is out in if/how this fix actually works. I can confirm that I did extensive controlled testing on this process and I definitively experienced a quantifiable improvement in lock time and duration, however whether the improvement was coincidence or a result of flashing the zip is unconfirmed. I can also confirm that flashing the zip does nothing bad so that you should have nothing to lose by flashing it irrespective of whether it is actually proven to work or not. I will update if I learn anything new on this.
Click to expand...
Click to collapse
GPS Status & Toolbox Fix
Download GPS Status & Toolbox from Market
Enable GPS
Open GPS Status & Toolbox
Menu > Tools > Manage A-GPS state > Reset
Menu > Tools > Manage A-GPS state > Download
Menu > Tools > Compass calibration > follow popup directions
Other app options that I've had occasional success with are:
All FREE and found in the Market, Faster Fix, GPS Fix and GPS Test Each of these just seem to act as a catalyst to get things moving. I haven't had consistent success with any of them, but in a pinch these are three that I use.
Click to expand...
Click to collapse
GPS EPST (##GPSCLRX#) Fix
Get your Master Subsidy Lock (MSL) code (Use Terminal Emulator and type "su" then "getprop ril.MSL" (case sensitive and don't use stock swype as the "I" malfunctions.)
Launch phone dialer and dial ##GPSCLRX# (##4772579#)
Enter the MSL Number from above as the password
Your phone will automatically reboot
Once booted back in the ROM open Maps or Navigation and obtain a GPS fix (This is an important step!)
Click to expand...
Click to collapse
GPS Configuration tweaks post by Xenova
These tweaks have been around for a long time. I used them on MIUI on the EVO 4G and they seemed to work really well for some and not for others. This is definitely work a look if nothing else is working for you.
Click to expand...
Click to collapse
Exchange the Phone
Sadly the other option is to take your phone back to Sprint and see if you can get a new one. Several people have claimed to get better signal on a new handset. That wasn't the case for me, but my exchange was very early on after release of the phone, so who knows what hardware changes may have occurred since then.
Click to expand...
Click to collapse
Get Free Storage and Mount it as a Virtual Drive
This is how to get a ton of free storage space and then mount it as a virtual drive on your Windows PC (sorry, haven't tested the Linux method personally and don't have a mac, but I'm sure someone slick can figure out a method based on my post.) The free storage is from Box.net and GMail. These are both workarounds/mods and neither method is sanctioned by Box.net nor Google. These have worked for me for quite awhile, but I am in no way responsible should either entity decide to penalize your accounts for use of these methods. Use at your own risk.
Box.net 50GB Promotion (there are several great tutorials on this hack here at XDA, I used tomcat420m's as I felt is was really clear)
This is a limited time promotion offered by Box.net for a free 50GB account upgrade for owners of LG PHONES. Some slick users came up with a method of modifying the build prop in order for any Android user to take advantage of the offer. It's a free 50gb Account and raised upload limit from 25mb to 100mb. The promotion ends 3/30/2012, but the 50GB is free forever. Here is the official promotion page Box.net.
Now hit the link to tomcat420m's tutorial and grab you some free space, then come back here to learn how to mount it as a drag and drop virtual drive!!
=========================================================================================
Mount Box.net Account(s) as Virtual Drives on Windows 7 (XP and Vista may works as well.)
Install MS Software Update for Web Folders or (\Downloads \MSWebfldrs-KB907306-ENU)
Open Windows Explorer
Right click on Network
Select Map Network Drive
Click on link (Connect to a Web site…)
Click Next
Click Choose custom network location, then Next
In the address bar paste http://box.net/dav
Click Next, then enter your box.net user name and password and click OK
Name your drive and drag it to link to the Favorites bar
Repeat the process with a second Box.net and so on for a whopping 50GB of storage per virtual drive!!
*Alternately, there are many services that let you mount multiple accounts such as Otixo which is free and Gladinet which is limited for free.
=========================================================================================
Mount Box.net Account(s) as Virtual Drives on Linux Thanks to Benjamin Kerensa for his howto on this.
What you are going to do is mount a WebDAV filesystem on Linux so that you can access the files like you do with any other folder on your desktop.
Open a Terminal window and install davfs2 by typing:
Code:
sudo apt-get install davfs2
Create the mount directory by typing:
Code:
sudo mkdir /media/box.net
Mount the WebDAV system:
Code:
mount -t davfs https://www.box.net/dav /media/box.net
(Note: The HTTPS should create a secure connection so your authentication will be safe)
Add your username and password:
Code:
sudo nano /etc/davfs2/secrets
echo “https://www.box.net/dav username password” >> /etc/davfs2/secrets
Benjamin notes you can access Box.net via Nautilus using WebDAV:
Just use Connect to Server to dav://www.box.net/dav and make sure to select Secure WebDAV.
A slightly different method by Andrew Martin can be found here.
======================================================================================
Mount GMail Storage as a Virtual Drive on Windows 7 (7.48GB per account)
DL and Install Gmail Drive Shell extension
Double click on the new mounted drive "GMail Drive"
Enter the credentials for one of your GMail accounts
Sign in and let it authorize
Download Gmail Drive Config utility from Convivea
Right-click the gmail_drive_config file and 'Run as administrator'
Click Add Drive
Enter a unique Label and another GMail user account name
You should receive a pop-up confirmation that reads:
DllRegisterServer in
C:\Windows\system32\ShellExt\GMFS004.dll succeeded.
Click to expand...
Click to collapse
Close all explorer windows
Re-open an explorer window
The new drive will appear under Computer after the last drive
Double-click this new drive to enter the password and login
Close all explorer windows...
Repeat steps 6-12 to add up 999 Gmail accounts
An neat little trick to Gmail Drive is that every file that shows up in your Gmail Drive is visible in your Gmail account with GMAILFS: somewhere in the subject. Gmail Drive can even organize files into folders based on the subject.
For example, sending yourself an empty email with a subject of GMAILFS: /music/ should create a music folder in your Gmail Drive. Then sending an email with an attached file called my_song.mp3 with the subject GMAILFS: /music/my_song.mp3 should place my_song.mp3 into your music folder in Gmail Drive, browsable with Windows Explorer.
I also setup filters to automatically label and archive any message with GMAILFS with my label of choice GMail Drive which keeps these all together and keeps my inbox tidy.
Warning: Be aware that if you upload too much too soon Google is likely to temporarily freeze your account for "Unusual Usage". Also, there's still a number of limitations of the file-system (such as total filename size must be less than 65 characters). Since the tool hooks up with the free Gmail Service provided by Google, changes in the Gmail system may break the tool's ability to function so there is no guarantee that files stored in this manner will be accessible in the future. The file size is limited to the same restrictions as Gmail attachment size, which I believe is 25mb.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Just because.
Can we just sticky this right now please? Nice job!!! If I didn't wait long enough, just let me know Just_s. Thanks!
Sent from my SPH-D710 using xda premium
JohnCorleone said:
Can we just sticky this right now please? Nice job!!! If I didn't wait long enough, just let me know Just_s. Thanks!
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Lol, thanks. This is just a rough draft. It will be much more complete when I can get to it.
As far as sticky, I'm going to see if I can get it in Barnacles wiki. Jerdog wants to keep that first page clean, which is a good thing. I'll bump it from time to time as I keep it updated.
Sent from my SPH-D710 using xda premium
Wow! Definitely some good info for the newbies. Nice work man
Sent from my E4GT
One word. Awesome! Thanks for this. Hopefully it'll save alot of future questions.
Sent from my SPH-D710 using Tapatalk
Great job with this.
qbking77 should be dropping in soon
Awesome guide. Just a few notes:
-For some reason the "How to hack custom bootanimation support" does not work on stock pulled kernels, but does work on source built kernels, it will just send the phone into boot animation loops on stock pulled.
-For the "Stuck at a black screen, bootanimation, etc" you really could flash any kernel that has the appropriate recovery(CWM), it doesn't have to be that specific kernel.
Again great job.
dtm_stretch said:
Awesome guide. Just a few notes:
-For some reason the "How to hack custom bootanimation support" does not work on stock pulled kernels, but does work on source built kernels, it will just send the phone into boot animation loops on stock pulled.
-For the "Stuck at a black screen, bootanimation, etc" you really could flash any kernel that has the appropriate recovery(CWM), it doesn't have to be that specific kernel.
Again great job.
Click to expand...
Click to collapse
Thanks! Alot of these are a couple of months old and most were in relation to Starburst ROM, so I am in the process of updating everything now. Hopefully others will follow your lead and let me know of any quirks such as the bootanimation hack.
Looks awesome, you and qbking77 would be a great how to team
Thanks for your time and work.
cds0699 said:
Looks awesome, you and qbking77 would be a great how to team
Thanks for your time and work.
Click to expand...
Click to collapse
Thanks. Gotta respect qbking's work. He puts in some serious time making those awesome videos. There are some definite high powered users here and I think the more users that can contribute the better.
I'm hopeful that between qb's vids, Barnacles wiki, contributions like sfhub's and this thread, we can help the devs focus on dev'ing ROMs and Kernels rather than wasting time answering the same old played out questions over and over.
Thanks so much for doing this. I think this is a great resource for everyone.
Just FYI, I followed the steps in the Hands Free Activation section and while the phone rebooted, it never ran the hands free activation. Tried it three times. Am I missing something?
FYI, I am running Calkulins 2.6 ROM
Awesome guide !
I would like to suggest adding instructions for making a Nandroid backup.
this is a fantastic guide! made it in my top 10 bookmark bar in Chrome
curious though. i want a VERY specific font flashed to my system and its not available in rom toolbox pro. does anyone have a link to a guide on how to get one into the system? im asking here because im assuming its very similar to what you posted for pushing/pulling apks, boot animations, and sounds? please slap me silly if this isnt the case
This thread is lame and posted by a lame person!
LOL
Love you bro! Great idea on this, we know that your tool kit on our MIUI.US forum was super helpful and popular
Sent from my SPH-D710 using xda premium
dr_gibberish said:
Thanks so much for doing this. I think this is a great resource for everyone.
Just FYI, I followed the steps in the Hands Free Activation section and while the phone rebooted, it never ran the hands free activation. Tried it three times. Am I missing something?
FYI, I am running Calkulins 2.6 ROM
Click to expand...
Click to collapse
Yes, definitely missing something. Are you following each step exactly? What happens after it reboots?
Drumrocker said:
Awesome guide !
I would like to suggest adding instructions for making a Nandroid backup.
Click to expand...
Click to collapse
Done.
JasonK75 said:
This thread is lame and posted by a lame person!
LOL
Love you bro! Great idea on this, we know that your tool kit on our MIUI.US forum was super helpful and popular
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Don't listen to this guy, he moved to MI willingly LOL Where you been?
stretchwookie said:
this is a fantastic guide! made it in my top 10 bookmark bar in Chrome
curious though. i want a VERY specific font flashed to my system and its not available in rom toolbox pro. does anyone have a link to a guide on how to get one into the system? im asking here because im assuming its very similar to what you posted for pushing/pulling apks, boot animations, and sounds? please slap me silly if this isnt the case
Click to expand...
Click to collapse
Really easy to do.
Download font apk
Install font apk
Go to Settings > Display > Screen display > Font style > choose the font you want
That's it
You can start with this FlipFonts. Also, a collection of font apk's you should be able to use here and a how to create your own thread here.
If you got ANY questions? Feel free to ask here..
[HELP THREAD]Any Questions? Anyone Can Ask here [GT-5360/5510/5512/6102]
VERY LENGTHY THREAD?? Difficult to read in app? Yes I know friends!! That's why added hide/spoiler button to each post & link to first post in every posts end
Hi, Everyone, This is a GUIDE to NEW / EXISTING users.. There are guides below for advanced users too.. So i have shared my experience at XDA with you all to make others understand and help each other.
If you want to know something/ want me to include a topic here, please PM me.. I will see if i can help with that and write about it.
Hopefully this will help many of you, Now READ ON.. Click On "SHOW CONTENT" Button to See the content on each posts below!
DIFFICULTY LEVELS: It tells you how much difficult it is for you to do the task described below. See the headings of guides in every post to see difficulty of that task.
* --> Very Easy
** --> Easy
*** --> Moderate
**** --> Difficult
***** --> Very DifficultINDEX OF THIS THREAD:
* Abbreviations/Acronyms used in XDA (Android language) [SEE 2ND POST]
* Simple methods to get LOGCAT, DMESG [SEE 3RD POST]
* CWM MD5SUM mismatch error while restoring? Solution for this: [SEE 4TH POST]
* How to use SDCARD instead of internal storage for apps[LINK2SD] [SEE 5TH POST]
* Detailed steps to install Stock rom/Firmware through ODIN [SEE 6TH POST]
* ROM installations instructions [IN GENERAL] [SEE 7TH POST]
* Kernel installations instructions [IN GENERAL] [SEE 8TH POST]
* How to deodex a stock rom in easy way using DSIXDA Kitchen [SEE 9TH POST]
* USEFUL LINKS TO THREADS/GUIDES SECTION [SEE 11TH POST/1ST POST OF 2ND PAGE]
MISCELLANEOUS: [SEE 10TH POST]
* Thread Title tags confusing? Its explained here!
* Why give "Thanks"? Thanks meter explained!
* Stars, User Titles: Junior, Member, Senior Member........? Read to know more!
* XDA/TAPATALK app image uploading problems??
* Make your Thread/Post Aligned(Neat) by using BBCODE TAGS
* Battery Drain?? Read these tips to avoid it.
* Enable Whatsapp *AUTO DOWNLOAD IMAGE OPTION* in new versions [TRICK]
PLANNED GUIDES ARE:[12th POST]
How to make a kernel--Writing in progress
How to get 10 without spamming / complaining!!
How to modify apps background,looks etc.
CREDITS :
To all my friends and xda members who gave me info to learn about these things.
To anmolsharma1293, deathnotice01, jaison thomas, kidcarter93, lavadepa, MNgez, nikufellow, tjsgy, wcypierre who gave suggestions and info and tips to improve this guide.
To The-Captain our moderator for helping us to improve ourselves, learn more and being kind to new users too.
Credits are added to respective people in the posts related to them whenever i have taken info / used their work[if not done, i will do it soon]. Informations obtained from other threads have been added in the posts related to it and i have done it with the permission of the thread OP. If i have forgotten someone's name please do let me know, and i will add it ASAP..
And please tell me any suggestions to improve this guide to help newbies/noobs as this guide should help all of us to get better at things we can do with an android. PLEASE REPORT ME ANY MISTAKES IF I HAVE MADE IN WRITING THE GUIDE/ IF THERE IS A WRONG INFORMATION.. I WILL CORRECT IT ASAP..
If i missed anyones credit, please forgive me and let me know.. and i will add it as soon as i can, promise!
Thank you.
Abbreviations/Acronyms used in XDA (Android language)
The reason for this guide is that many new users would have difficulty to understand what are these short forms.. everyone says cwm, rom, cm, etc.. but no one says what it is.. and you may feel a bit shy/embarrassed to ask them what it is. So here is my attempt to cover them..
Please do let me know in PM if some words are missing and you want them to be covered.. i will gladly add them, thank you.
This Post is an inspiration from mrhaley30705's thread & Diablo67 thread.
Use CTRL+F to find a specific term.Difficulty --> *
XDA RELATED ACRONYMS
DEV: Developer
ERD: Elite Recognized Developer
FM/FSM: Forum Moderator/Forum Specific Moderator
RC: Recognized Contributor
RD: Recognized Developer
RT: Recognized Themer
SM: Senior Moderator
GENERAL
AFAIK: As Far As I Know
ATM - At the moment
BTDT - Been there done that
CRACK: The password / product key / license key illegally used for unauthorized usage are known as a crack of the software . Also please read the warning posted at warez meaning below. The same applies to cracks
ETA - Estimated time of arrival.. Note: Asking ETA in dev section is a big NO NO..!!
FTFY: Fixed that for you
FTW - For the win
FWIW: For what it's worth
FYI: For Your Information
IBTL/IB4L - In before the lock / In Before Lock
IDK: I Dont Know (Thats what it means and i am not saying i dont know about IDK!!)
IIRC - If I recall / remember correctly
IRC - Internet Relay Chat
LOL - Laugh out loud
NEWBIE: Someone who is new to this field/ forum and wants to learn how to do it rather than say "NOT WORKING! FIX IT!".
NOOB: Someone who is new and doesn't want to learn "HOW" its done, just want to "USE" the end product. So, please guys dont be a noob, be a newbie!
OP: Short for Original Poster, or the person who originally started the thread.
OT - Off Topic
PM: Short for Private Message. Allows users of XDA to send and receive non-public messages. Accessed from USER CP.
P.S: stands for Post Script. It is used when u wrote a message on a postcard and u forgot to mention an important information.*
ROFL - Roll on floor laughing
RTL: Right To Left support (In Some languages you have to start reading from right and end towards left side.. as against to usual method of reading from left to right)
SMH: Shake my head
STH: Something
TBH: To Be Honest
TIA: Thanks In Advance
THREAD: An individual issue page on the forum. This thing you're reading is a thread.
TLDR: Too long to read
TM: stands for Trademark.
USER CP: Short for User Control Panel. This button near the top of the XDA page allows users to update their avatar, personal information, and signature. PMs and subscribed threads can also be checked in this location.
WARES/WAREZ: Warez refers primarily to copyrighted works distributed without fees or royalties, and may be traded, in general violation of copyright law. To make it simple, it is any app/software which has to be paid to use them, but are used without paying any money.. PLEASE NOTE: THIS IS NOT TOLERATED AT XDA. SO PLEASE DONT POST WARES ANYWHERE ON XDA FORUMS. YOU WILL GET BANS/INFRACTIONS IF YOU DO SO!
ANDROID DEVICE RELATED:
ADB: Android Debug Bridge, a utility to run on a PC to allow connection to and control of an Android device. Part of the Android Software Development Kit (SDK), it allows for ROOT-level access to the Android device from a computer.
AOSP: Short for Android Open Source Project. The open-sourced code from which individuals can build new distributions of Android.
APK: An Android executable file, similar to the .exe file in Windows. Most programs will install with a .apk file.
Apps2SD:A method of storing applications and cache on the device's microSD card.
Bloatware: Software or 'apps' that you don't need, but come preinstalled to a device's /system partition, meaning that you cannot remove them unless the device has been rooted
Boot Animation: Boot animation is a term for a graphical representation of the boot process of the operating system. After you switch on / reboot phone you see this.
BOOTLOADER: There are two of these; the primary and secondary bootloaders. These programs tell the Android device how to start up, and are critical to its functionality.
Bootloop: When your system recycles over and over without entering the main OS.
BRICK/(HARD BRICK): An Android device that is completely non-responsive, i.e. nothing lights up, the screen does nothing, no combination of button presses cause any reaction. Can only be restored by JTAG or warranty service.
BUILD.PROP: A plain text file which contains environmental variables for the system to use during operation. Can be hacked to fake a different model for increased functionality, among many other operations. It is also used to make tweaks to boost speed/performance, etc.
BUSYBOX: An application that contains many standard Unix tools.
BUTTON COMBO/THREE BUTTON COMBO: The act of pressing several buttons at the same time to produce a desired result (e.g. press and hold volume up+home button+power button for 10 seconds will reboot into the RECOVERY menu at any movement when phone is on or Press and hold volume down+power button+home button to get into ODIN mode/DOWNLOAD mode).
Cache:A component that transparently stores data so that future requests for that data can be served faster.
CM: Short for CyanogenMod. CyanogenMod is an Android build built from the Android Open Source Project, and its builds are usable on multiple different Android Devices.
CPU: It stands for Central Processing Unit and handles all the complex mathematical formulas necessary to do everyday things like surfing the Internet.
CSC - File with Carrier Customizations
Custom bin counter: A line of code in several Samsung Galaxy devices' bootloaders that counts the number of times a user uses ODIN to flash ROMS/KERNELS to the device. Commonly used to detect software modification. This is called custom bin down in ODIN mode and it should be 0 to claim warranty. Can be reset with GALAXY TOOLBOX APP by Doky73
Custom: Independent developers who like to customize their devices beyond the standard options provided often tend to release the fruits of their labor for the rest to enjoy, in form of custom ROMs.
CWM: Short for ClockWorkMod Recovery Menu. This is a program that allows you to install custom ROMS/KERNELS as well as do many other customizations. Often referred to as the "RECOVERY MENU"/"CWM"
DALVIK CACHE: The collection of program information stored for use by the DALVIK program. This can be cleared from the RECOVERY menu to resolve issues with the Android OS.
DALVIK: The Android operating system's memory management tool. This program handles which other programs are running and assigns memory to them
DEODEXED: Removing the .odex files from an APK file. The .odex files contain a list of dependencies for the associated file, and if something changes, the .odex (and similarly, the associated file) not longer function correctly.
DMESG: dmesg (for "display message") is a command on some Unix-like operating systems that prints the message buffer of the kernel..
DOWNLOAD MODE: Read Button combo to know about this.
EFS: The directory /efs on the Android device's internal storage. Contains files with the Android device's IMEI, wireless devices MAC addresses, product code, and other information..
EMMC: Short for Embedded MultiMediaCard. A chip architecture consisting of an embedded storage solution with MMC interface, flash memory and controller, all in a small ball grid array package.
EXT4: A journaling file system (e.g. NTFS, FAT32 are file systems) often used by Linux distributions. Can be used with Android.
EXTERNAL SD: A micro SD card that has been inserted in the micro SD slot in the Android device. Can be removed.
FACTORY RESET: This will remove all user customizations in the Android OS, returning it to a factory state. Note: This will not wipe the Internal SD card. It will just make it as a phone just bought from the store state.
FC/FORCE CLOSE: When a program on the Android device becomes unstable/gets an error, the DALVIK program will force it to terminate to prevent further system instability which appears as a Force Close message usually in phone.
FLASHING: The act of writing code to the Android device. ROMs, MODEMs, KERNELs, and BOOTLOADERs can all be flashed. Independent from, and having nothing to do with, Adobe's Flash product.
FREEZE: Specific to LINK2SD/TITANIUM BACKUP. Using these 2 apps, the user changes a program into a non-functional, but still installed, state. Useful for identifying problem and FCs.
gapps - Google Applications, like GMail, Calendar, Maps, G+, etc
GB - Gingerbread, AKA Android OS 2.3.X
GOVERNOR: A program that interacts with the device hardware to increase or decrease the processor's clock speed (e.g. at low usage, it will set the processor speed to 400 MHz, but as usage increases, it would scale up to 1000 MHz).
HSUPA/HSDPA: Short for High Speed (Up/Down) Packet Access. This is 3G+, and is the Android device's internet speed level between 3G and 4G.
ICS: Short for Ice Cream Sandwich, the Android OS version 4.0.x.
IMEI: Short for International Mobile Equipment Identity. A unique number to identify GSM, WCDMA, and iDEN phones. Used by GSM networks to identify valid devices.
INTERNAL SD: The internal storage memory of the Android device. Not a physical SD card that can be removed.
JB: Short for Jelly Bean, the Android OS version 4.1.x.
JIG: A piece of hardware that makes a physical connection between pins of the USB slot to force the Android device into DOWNLOAD mode.
JTAG: A process of connecting directly to the main board of the Android device to rewrite corrupted BOOTLOADERS.
KERNEL: The kernel is a program that constitutes the central core of a computer operating system. It has complete control over everything that occurs in the system.
LAST_KMESG: last_kmsg is a dump of the printk statements from the kernel before the operating system itself crashed.
LAUNCHER: A program that launches programs in Android. Examples are Touchwiz (Samsung), HOLO Launcher, Launcher Pro, ADW Launcher, and Go Launcher EX.
LCD Density: Pixel density is a measurement of the resolution of devices in various contexts; typically computer displays, image scanners, and digital camera image sensors.
LOGCAT: A command to view messages in one of the system logs. See Android logger.
LTE: Stands for Long Term Evolution. It is based on the GSM/EDGE and UMTS/HSPA network technologies, increasing the capacity and speed using a different radio interface together with core network improvements.
MAI77 method: Its only known here. So dont say this out of SGY forum. This is a method to flash kernel through CWM using Kernel flasher tool made by MAI77. Its basically you have kernel flasher tool and boot.img file in SDCARD root and you select kernel flasher tool in CWM and it will install boot.img file which is the kernel you selected.
MD5 CHECKSUM: A 32-digit (128-bit) hash number generated by a cryptographic program to ensure that a downloaded file matches the original file. The original file is run through the MD5 generator program, which creates the 32-bit number. This number is checked against the md5 number created with the file the end user receives to ensure file integrity.
MIUI: A Chinese built-from-source ROM. Short for "Mobile Internet User Interface". Also can refer to the MIUI music player, which has been included in other ROMs.
Mod: The act of modifying a piece of hardware or software or anything else for that matter, to perform a function not originally conceived or intended by the designer.
MODEM: The software that interfaces with the phone's radio hardware to connect to cell phone towers.
NANDROID BACKUP: A complete system image backup of the Android device except for the MODEM and KERNEL. Can be accessed from CWM.
ODEX: A file that is associated with an APK file, containing a list of the dependencies for the program. See also DEODEXED.
ODIN: A Samsung proprietary program that allows the Android device to be flashed back to stock or with custom software.
OVERCLOCKING/OC: Setting the processor's clock speed to run faster than its default setting, i.e. 1248 MHz (1.2 GHz) vs 832 MHz (Default)
OTA - Over-the-Air (usually used as "OTA update" for firmware updates that can be installed directly via 3G/4G/Wi-Fi without the need of an PC)
PIT FILE: Short for Partition Information Table file. One of the possible file types used while flashing with ODIN or HEIMDALL.
Port: To Take a rom or app from one phone and program it to work on a different one.
Ram: (Random Access Memory) A group of memory chips, typically of the dynamic RAM (DRAM) type, which function as the computer's primary workspace.
RECOVERY: The menu that allows a user to do many low-level operations on the Android Device. This menu can either be the stock Samsung menu, or the CLOCKWORKMOD RECOVERY MENU (CWM). See also CWM.
RFS: A Samsung-proprietary file system (e.g. NTFS, FAT32 are file systems) used on some Android devices. Stands for Robust File System.
RIL - Radio Interface Layer
ROM: The collection of programs, themes, and settings that create the general look-and-feel of your Android device. This is what most users will initially be wanting to change. Or custom ROM firmware file, Can also refer to a Read-only memory.
ROOT: Changing the permission level of the Android system to its most powerful level, the root user, allowing full access to the file system. More like Administrator permission in Windows OS.
SGY /SGYD /SGYP /SGYPD : Samsung Galaxy Y / Samsung Galaxy Y Duos / Samsung Galaxy Y Pro/ Samsung Galaxy Y Pro Duos
Sideloading: It means installing applications without using the official Android Market.
SOFT BRICK: A device that is not functioning correctly, but still shows some signs of operation. See also BRICK.
STOCK: The Android software version that comes installed on new devices, prior to sale to the user. Can also be used to refer to the Android software issued from Samsung or the carrier.
Superuser/SU: On many computer operating systems, the superuser is a special user account used for system administration. Depending on the operating system, the actual name of this account might be: root, administrator or supervisor.
TETHER: Connecting the Android device to a computer via a wired or wireless connection to allow the transfer of data through the Android device's internet connection. Commonly used to provide internet access to a laptop or desktop computer when other methods are not desired or available.
THEME: A collection of images, backgrounds, colors, font types, and other visual items to change the Android device's look and feel. Separate from LAUNCHER, and is usually FLASHed in CWM.
TWRP2 - an alternate recovery mode for your phone
UNDERVOLTING/UV: Setting the voltage levels drawn by the Android device to a lower level to reduce overall battery usage.
Updater Script: When Android devices install updates via CWM/recovery mode they have to perform a wide range of functions on files and permissions. The scripting language is called Edify and is defined primarily in the bootable/recovery/{edify,edifyscripting,updater} directories of the Android source-code tree.
WCDMA: Short for Wideband Code Division Multiple Access. An air interface standard in 3G mobile communications networks that allows higher speeds and more users.
ZIPALIGNED: An archive alignment tool that provides important optimization to APK files. The purpose is to ensure that all uncompressed data starts with a particular alignment relative to the start of the file. Reduces RAM consumption.
Simple methods to get LOGCAT, DMESG
Devs asking you to get a logcat and give?? Yes it helps a lot for devs if you give logcat to solve problem. So dont wait till devs ask you to get a logcat! Just give them a logcat when you tell them this/that doesnt work. This way theirs and yours time will be saved and unnecessary posts will be avoided. Now i will give you simple steps to do it. There are two main ways to do a logcat, 1. within android device, and 2. through adb using PC.WITHIN ANDROID DEVICE METHOD:
This i learnt from paxChristos from his thread.
1. Logcat within android device can be done in one of two ways, through a Logcat app: Difficulty --> *
Here are two good apps: aLogcat or Catlog
Both of these programs can dump their logs to a text file, which is very useful for debugging. Or, you can do it in terminal emulator (same rules as running through adb(see below))
2. Through Terminal method: Difficulty --> **
Install Android Terminal Emulator app from Play Store..
Open terminal app you just installed..
Enter these commands:
After every command press ENTER/SUBMIT button
Code:
su
then accept the superuser popup message[it comes only first time if you select checkbox "remember the choice"]
Code:
logcat -v long > /sdcard/test.log
Or use this command:
The -v long puts the text in a nice format that is more easily readable. The *:W will search for all warnings, errors, and fatals, while the *:S will silence everything else.
So essentially, u will have a .txt file that has a log of all warnings and up, nothing else, and it'll look pretty too!
Code:
logcat -v long *:W*:S > /sdcard/filename.txt
now press home button to minimize the terminal..
and do the task which is giving problems/ whichever task log you need to give to dev..
then drag the notification bar..
select terminal app in it..
now press and hold "Volume down button" and touch c button on keyboard.
This will stop the command..
now use this command twice
Code:
exit
Now app will get closed. go to sdcard to find test.log file.. upload it to here so that dev can access it..
Thank you for reading it with patience hope you can get logcat now..
Note: if you are stuck in boot and want to take logcat.. READ LOGCAT FROM ADB METHOD BELOW.. the above one is simple method for these tasks for eg.. if you are having some force close of app/lag etc.. then after entering second command press enter and then use home button to minimize terminal.. dont worry it will take log.. now open that app and once it gives force close then click on it and then open terminal again and press volume down button + c to terminate command.. then use exit command two times... done.. now go to sdcard and find a.txt file
From PC[i.e, ADB] LOGCAT METHOD :Difficulty --> ***
There is an advantage here. As doing this way, you can start using logcat when your device boots. There are 2 ways here again..
PREPARATION:
In your android device, go to settings --> applications --> development -->
Check USB Debugging
Make sure your device driver is already installed otherwise install kies software which will install drivers too.. Get kies from This LINK
You need to download this ADB.zip file i made to your system.. Download link
Extract the ADB.zip file from any applications like IZarc/7Zip/winzip/winrar.
ADB USAGE INSTRUCTIONS:
Then go to Android folder.. inside that you should find 3 files.. Now open a command prompt or terminal in that path..(wherever you extracted it.. use cd command)
Then inside that path.. type
Code:
adb logcat > filename.txt
Or
Code:
logcat -v long > /sdcard/test.log
Or
Code:
logcat -v long *:W*:S > /sdcard/filename.txt
Now perform tasks in android device of which you need to give logcat for the devs. Then use CTRL+C to end the command.
Now find the filename.txt inside the Android folder which has logcat. Upload this file and give link to dev..
Or There is another method called All in one logger tool by wcypierre which can get you logcat and dmesg. I have not tested it myself. But i am sure it will work and you can go to that thread and ask your queries about that tool if you want to use that. The dev will help you gladly. So, please thank him for his nice work.The full list of options that can be used with logcat command is as follows:
V — Verbose (lowest priority)
D — Debug
I — Info (default priority)
W — Warning
E — Error
F — Fatal
S — Silent (highest priority, on which nothing is ever printed)
You can replace the *:W with any other letter from above to get more info.
From PC[i.e, ADB] GET DMESG:Difficulty --> ***
Note: You will need adb access for this to work, same as logcat. Read PREPARATIONS above to find adb files required and related setup.
What this will do is get us live kernel output so we can know things like "What driver is the kernel loading {or not loading for that matter}" and similar things.
Go to Android folder.. inside that you should find 3 files.. Now open a command prompt or terminal in that path..(wherever you extracted it.. use cd command)
Then inside that path.. type
Code:
adb shell dmesg > dmesg.txt
To get last_kmsg:
Code:
adb shell cat /proc/last_kmsg > kmsg.txt
From Android Device GET DMESG:Difficulty --> **
You can also get the dmesg by using terminal emulator.
Code:
dmesg > /sdcard/dmesg.txt
To get last_kmsg:
Code:
cat /proc/last_kmsg > /sdcard/last_kmsg.txt
FOR APP DEVS / ADVANCED USERS ONLY! LOGCAT INSTRUCTIONS:
Thanks to jaison thomas for this method! NOTE: I have not tested this. sorry. But it will definitely work. I edited the quoted message to make it simple.
jaison thomas said:
log cat using eclipse, i thought it will be simple for advanced users who are into app development.
I will guide how it works
1) install samsung kies in your pc
2) turn on usb debugging in phone.
3) install android plugin for eclipse .
4) now on eclipse click on "window" --> "show view" --> "other" --> "android" --> "log cat". Then click "ok".
Thats it .logcat window will be shown in lower bottom side of eclipse.it is having a green color icon. Also there may be a chance of logcat window minimised in eclipse.do look for a green icon.
5) now conect ur phone using datacable u can see all the things happening inside the phone in log cat window in eclipse.
NOTE: if you couldnt find android under other option.. Do this:
u didnt install android plugin for eclipse do as follows to install android plugin for eclipse.
1) click on help
2)click on install new software
3) then click on add.
4)then you will get a text box with name and location. in name text box type android or any thing,
in the location copy paste this
https://dl-ssl.google.com/android/eclipse/ and press ok,
5)In the Available Software dialog, select all check boxes and click Next.
6)In the next window, you'll see a list of the tools to be downloaded. Click Next.
7)Read and accept the license agreements, then click Finish.
8)If you get a security warning saying that the authenticity or validity of the software can't be established, click OK.
9)When the installation completes, restart Eclipse.
Click to expand...
Click to collapse
CWM MD5SUM mismatch error while restoring? Solution for this:
Difficulty --> **
If you have made a nandroid backup and we never actually test whether it works/not.. So, some day when you need to restore it.. you get an error while restoring that "md5sum mismatch" restore aborted!! Then you are in a really bad situation right?? Wrong.. Do this.. and the problem should be solved..
You need to edit nandroid.md5 file stored in /sdcard/clockworkmod/backup/"backup name"/nandroid.md5
NOTE: backup name is usually date and time of your backup/ you could have renamed it to some name.
You need terminal emulator app. Download from play store (android terminal emulator)
Open terminal emulator app and input these commands..
Code:
cd sdcard/clockworkmod/backup/2012-09-30.03.18.47
NOTE: Change 2012-09-30.03.18.47 to the name of your folder
To See what file extensions need to be included. type
Code:
ls
( lowercase "L") and hit enter.
This will list everything inside your current directory (backup files of that particular backup)
To make sure there is no nandroid.md5 file existing already, enter this command:
Code:
rm nandroid.md5
Now to make a new nandroid.md5 file
Code:
md5sum *tar > nandroid.md5
Now its ready to be used in restore inside CWM..
NOTE: USE this procedure to repair nandroid md5sum mismatch error if you are getting this on a backup which has not been modified. If you have opened the backup files to modify the files inside. Its not advised to do this. So, please take note of this.
Special Thanks to cynnar for this idea. i tweaked it to our device from his post.
CLICK HERE TO GO TO FIRST POST
How to use SDCARD instead of internal storage for apps[LINK2SD]
Difficulty --> **
Welcome to LINK2SD app friends!
Easiest app to install and use to extend your internal memory.
What it does?
It creates a symbolic link file(more like shortcut in windows) for apps in internal memory which will point to the real app which will be saved in your sdcard second partition! It mounts the second partition of your SD card as /data/sdext2 and makes OS mounts it at boot time.
It can also move user apps to SD card (force move), with batch moving (multiple apps moving at once) capability.
That feature uses Android's standard SD-card installation feature and does not require a second partition. It can break some apps if they are not meant to be moved to the SD card (Such as Widgets).Preparations:
* You need to have root permission/access[Rooted phone]
* A second partition on your SD card. You should have two partitions on SD card and both should be primary.
* The second partition is used for application files and can be ext2, ext3, ext4 or FAT32 (I prefer FAT32 and no issues i have seen, see note below to know why?).
Note:
1. The second partition will not be accessible through windows OS as it recognises only first partition on removable devices. In Linux you can access second partition too!
2. ext4 is the latest ext format but several ROMs/Kernels have issues with it while fewer have issues with ext3 and ext2. FAT works on all ROMs.
Steps to make 2nd Partition in SDCARD:
Connect phone to PC using USB Cable. Make sure your device driver is already installed otherwise install kies software which will install drivers too.. Get kies from This LINK
Now drag the notification bar from status bar in phone and select "USB Connected" messasge.
Then select "Connect USB storage" button.
Once it is connected, Make a backup of sdcard first to PC(Copy all files inside sdcard to any fodler in PC). Otherwise you will loose data in sdcard.
Now open "MiniTool Partition Wizard Home Edition" download it from This LINK
This tool is compatible with Windows 2000/XP/Vista & Windows 7. Or Use "Gparted" tool for linux users Or "iPartiton" for Mac users.
Note: this partition manager QUEUES the operations. So nothing is deleted and changed UNTIL you click "APPLY" and then confirm by clicking "OK".
Make sure you are deleting partition on SD card! (not your hard disk for example). Dont be afraid, just read everything and think twice before selecting correct drive. Do you see three gray icons on the bottom? Under each of them the capacity of each drive is listed, and SD CARD has slightly different icon. Check the sdcard capacity given in the window to select the proper one.
select "Create As": PRIMARY on the sdcard partition. Choose whatever size(leave some space which we will use for apps partition) you want for sdcard( to have your music, personal files, etc.).
Select "File System:" FAT32
select the second partition below the one you just created which will have the space left when partitioning the first partition.
Select "File System:" FAT32 (YOU can use Ext2, Ext3, Ext4 also.) But my suggestion is please use FAT32. You wont have problems as all ROMS/KERNELS support fat32 by default!
Click "apply" button on top left corner. Partitions will be created and card will be formatted.
Now put your files back to sdcard and disconnect from PC.
NOTE: You can also use CWM partition option. If you want to use CWM partition method to partition your sdcard then see here. I have never tried this method. So i cannot help you with that.Steps to install and use link2sd[2.2.3 version]:
Let the media scanner finish the scanning process, then open link2sd app and you will see a pop up menu "Select the file system of your SD card's second partition"
Choose your partition type for "second partition" you created while partitioning, say you choose "FAT32/FAT16" then your sdcard second partition should be FAT32/FAT16 which is nothing but FAT or vFAT.
Now Press OK. After 2-10 seconds you will see another pop up menu "Restart your phone" Press "OK" (message goes like this "Mount script created, please restart your phone to mount the second partition of your SD card.")
Now do a reboot of your phone.
Link2SD successfully installed.
To make space inside internal memory-->
* Now open LINK2SD app and you will see three buttons on top bar. click on the first button from left side. you will see:* All --> It will show you all the apk/app files in your phone (130+/- apps)
* System --> It will show you all the system apps in phone (100+/- apps)(stored in system memory)
* User --> It will show you all the User apps(i.e, installed by you) in your phone (30+/- apps)(stored in internal & sdcard & second partition memory)
* Linked --> It will show you all the linked apps in your phone (it wont show any now)(stored in your sdcard second partition memory)
* On SD card --> It will show you all the user apps (10+/- apps)(stored in your sdcard first partition. usual sdcard method)
* On internal --> It will show you all the user apps (10+/- apps)(stored in your sdcard first partition. usual sdcard method)
* Frozen --> It will show you all the apps that have been stopped. This is a method same as Titanium backup app "freeze" method. It makes your app invisible to phone. I.e, it will be installed and ready to use.. but you wont see it anywhere in launcher and if you click on a shortcut of such "frozen" app it will say "app not installed" or such message.* Now select options button in phone, then select "Multi-Select". Now press "select all" option.
* Now press "Actions" button. In new pop up window select "Create link"
* Now in new page which appears, select all 3 options to link application, dalvik-cache, library files. Then press "ok" button and wait till the process ends. It will take time depending upon how many apps you have. around say 5 minutes.
* Now go to linked option from top bar first button from left side. and see al the apps having linked->sdacrd tag on them which means they are now in sdcard second partition..
*Long press on any app to view more options.
NOTE: 1. you cannot move link2sd app from internal memory. It is better to keep it there.
2. System applications should not be linked to SD card. Link2SD does not allow these applications to be linked.
3. Link2SD does not move application's private data directory; it moves apk, dex (dalvik-cache) and lib files.
4. Do not move keyboard apps to system memory. they wont work.
Advantages:
1. When you connect your phone to PC as mass storage, Android unmounts FAT partition but the second partition remains mounted in phone. Therefore linked applications are not affected and can be run without problems even when you have access through pc to sdcard.
2. You can use this app to uninstall system apps, move user apps to system apps or system apps to user apps.
3. You can integrate new updates of system apps which will be stored in internal memory to system apps. But please note: You should free the app first and then move them to/from system always for safety of apps so that they wont give FC. If some apps did gave FC after moving please restart the phone.
4. You can use clear cache, dalvik-cache, 2nd partition options. They wont harm your apps, they will remove only unwanted files.
Troubleshooting / Error occurance chances:
Question : When I click on "Move to SD card", I see a progress bar for 2-3 seconds and then:
pkg:/data/app/com.mobisystems.editor.office_registrered-1.apk Failure
[INSTALL_FAILED_INSUFFICIENT_STORAGE]
Answer : Your problem is a simple one.. your internal memory is low..
What link2sd actually does is.. first it moves the files to internal memory and then it sends to 2nd partition.. so you are having issues because.. say the apk file is 20 MB.. and your internal memory is around 20/less MB free.. So, it will give that error even if the second partition is totally empty..
For a work around to this.. you can make backup from titanium or just backup with any app.. then uninstall some apps.. then move that big app.. then reinstall these..
Hope your doubts are solved.. Enjoy the awesome app!
Apps Original thread link and the credit goes to RD bakpinar. So do thank him for this awesome app. You can also donate the dev by visiting his original thread.
CLICK HERE TO GO TO FIRST POST
Detailed steps to install Stock rom/Firmware through ODIN
Difficulty --> **
NOTE: Please dont install/flash FIRMWARE of OTHER DEVICES for your phones! through odin! Make double check before downloading whether its the right firmware for your phone!
Visit the threads respective to your devices to see the latest available firmware.. Links given below.
Samsung Galaxy Y --> [Stock][ROM][Odin] FIRMWARE THREAD BY DOKY73
Samsung Galaxy Y DUOS--> [Stock][ROM][Odin] FIRMWARE THREAD BY MANORANJAN2050
Samsung Galaxy Y PRO --> [Stock][ROM][Odin] FIRMWARE THREAD BY GianniDPC
Samsung Galaxy Y PRO DUOS --> [Stock][ROM][Odin] FIRMWARE THREAD BY MANORANJAN2050
To check the current version your mobile has.. Type this code in Dialer Tab which is where you type phone numbers to call..
Code:
*#*#1234#*#*
and check EX. PHONE: S6102DDLG1. See whether it is the latest by visiting samfirmware.com site and type your mobile no. for ex. 5360 in search box in right side of that site page and see whether any new update has come.
PREPARATION:
Switch on PC to windows OS and Login to your account. Make sure your device driver is already installed and your device got detected.. otherwise install kies software which will install drivers too.. Get kies from This LINK
Now connect your device to PC using USB Cable..
Open ODIN software from extracting the file you downloaded from using any of these applications like IZarc/ 7ZIP/ Winzip/ Winrar..
Note:
If you did above instruction and still device not detected? Then do this..
Unplug the usb cable..
Restart both PC and phone..
Then let the PC log in.. and give 5 mins time to it to load everything..
Then connect usb cable to phone and pc..
Open task manager in PC using CTRL+ALT+DELETE..
end process of adb.exe if its existing and kies too... do this end process only once..
Now open odin..
Instructions to install this through Odin:1. Restart your mobile by holding three buttons... Volume up+home button+power button.. Now when you see Samsung logo release the buttons... After few seconds you will see 4 options written in red text.. Which is stock recovery (Android system recovery)... select first option there.. ("reboot system now").. It will say "Rebooting..." in green colour..
2. Now when screen gets black.. immediately press and hold volume down+home button+power button..
you will see a page saying "Warning"
A custom OS can cause critical problems in your phone and installed applications.. and it will say some more in next paragraph..
Dont worry about it.. Now press "Volume up" to continue to odin mode..
3.you will see ODIN MODE written on top of screen in red..
Now make sure you are connected to your pc through usb cable and pc is logged in and open odin file..
4. Note: In Odin you will see a yellow/blue color in one box below "ID:COM" section.. If you are not seeing yellow/blue box restart your mobile and do same process from step 2. also restart your pc if its still not showing yellow. If it is showing then good.
5. Now select "PDA" button under "Files [Download]" section.. select "PDA_S****_(your firmware version no.).tar.md5" file
Now select "PHONE" button below "PDA" button in "Files [Download]" section.. select "MODEM_S****_(your firmware version no.).tar.md5" file
Now select "CSC" button below "PHONE" button in "Files [Download]" section.. select "CSC_S****_(your firmware version no.).tar.md5" file
Note: **** --> Your device model number. 5360 --> Samsung Galaxy Y, 6102 --> Samsung Galaxy Y Duos, 5512 --> Samsung Galaxy Y Pro Duos, 5510 --> Samsung Galaxy Y Pro.
6. Now remember!! Only "Auto Reboot" "F. Reset Time" options should be selected..
PDA, PHONE, MODEM also should be selected..
7. Now you are ready to flash through odin.. Just press "Start" button.. and wait around 10 minutes until odin finishes and the "yellow" box should show green... It will usually finish within 52 seconds to be precise..
8. Now your phone will reboot. If it starts showing Samsung logo again after few minutes.. Restart your mobile by holding three buttons... Volume up+home button+power button.. Now when you see Samsung logo release the buttons... After few seconds you will see 4 options written in red text.. Which is stock recovery (Android system recovery)...and select "wipe data/factory" and select first option there.. ("reboot system now").. It will say "Rebooting..." in green colour..
9. Now enjoy your brand new stock rom.. Hope this helps you!!NOTE: IF YOU CANT GO TO ODIN/DOWNLOAD MODE.. YOU NEED AN USB JIG to force phone to Odin mode automatically.. [REF] BORROW A USB JIG NEAR YOU..
CLICK HERE TO GO TO FIRST POST
ROM installations instructions [IN GENERAL]
Difficulty --> *
OK.. so I assume you have latest firmware.. Because its always good to have latest firmware update to avoid unnecessary problems as usually updates will have bug fixes and stability improvements.. If not, then First follow the guide I have given in this thread to install the firmware update if you are not on latest version..
OK, now that we have latest firmware update installed, lets proceed to ROM installation process!
* If you dont have these files Download and keep these files in sdcard (outside all folders / root of sdcard)..
1. Rom.zip file.. link is provided in first page of the ROM thread..
2. CWM file..
Now go to stock recovery by doing this..
Restart your mobile by holding three buttons...
Volume up+home button+power button..
Now when you see Samsung logo release the buttons..
After few seconds you will see 4 options written in red text..
Which is stock recovery (Android system recovery)...
* Select 2nd option in there.. "apply update from sdcard"
* Select "CWM.zip" file u have..
* In cwm(clockworkmod) which is with yellow text..
* Now go to backup and restore option.. make a backup first.. you need to have atleast 250-400 MB of free space in sdcard to do backup...if you dont care about your data/contacts/messages currently existing in phone then no need to make backup.
* Select "wipe data / reset" and then "wipe cache Partition"..
* select "install zip from sd"
* Select "Choose zip from sdca" first option now..
* Scroll down.. and select rom.zip file..
* Then select yes option.. and wait for few minutes for it to finish.. then come bak to previous screen using power button..
* Now select "reboot system now"
* Good, Now you have successfully installed the rom.. First boot takes time.. So wait till atleast 5-10 mins.. It will vibrate onec and then it will boot to your home screen.. This guide is in general. But usually all roms have installation guide..NOTE: THIS IS A GENERAL METHOD.. SHOULD WORK FOR MOST OF THE ROMS.. BUT IF THERE WAS ANY PROBLEM LET ME KNOW.. I WILL EXCLUDE IT FROM THIS GUIDE.. IF YOU CANT UNDERSTAND INSTRUCTIONS IN ROM THREADS THEN ONLY TRY THIS.. I HAVE WRITTEN THIS ASSUMING YOU ARE ON STOCK KERNEL/ YOUR KERNEL DOESNT HAVE CWM INBUILT. If it has.. then ignore stock recovery instructions mentioned in above instructions.. and directly start from CWM instructions..
CLICK HERE TO GO TO FIRST POST
Kernel installations instructions [IN GENERAL]
INSTALLATION PROCEDURE FOR KERNELS THROUGH CWM METHOD:Difficulty --> *
* First Download all the files required [from the kernel thread first page of whichever one you want to install]
* Copy these files inside SDCard.. Kernel.zip (kernel), CWM.zip (ClockWorkMod Recovery tool)
Note: Don't keep these files inside any "FOLDERS".. Just copy it to SDCard root (parent) folder (Outside of all folders)..
* Switch off your mobile.
After a small vibration (switch off confirmation) PRESS and HOLD 3 BUTTONS (VOLUME UP+HOME BUTTON+POWER BUTTON)
when samsung galaxy logo appears, release the 3 pressed keys..
* After few seconds.. You will see Android system recovery (red text with 4 options lines)..
Select "apply update from sdcard"
Note: (Volume up+down for "scrolling" through options or selection of files, home button for "select" any option.. in CWM only: power button for "back" option)
Then Select "CWM.zip".
* ClockworkMod Recovery v5.0.2.6 is loaded now.
Select "install zip from sdcard"
Select "choose zip from sdcard"
Scroll and Select "Kernel.zip" and select "Yes"
Wait till the menu appears again.. Now Go back
* Select "Reboot system now" and you have successfully installed Kernel.INSTALLATION PROCEDURE FOR KERNELS THROUGH ODIN METHOD:Difficulty --> **
* First Download all the files required [from the kernel thread first page of whichever one you want to install]
* Restart your mobile by holding three buttons... Volume up+home button+power button.. Now when you see Samsung logo release the buttons... After few seconds you will see 4 options written in red text.. Which is stock recovery (Android system recovery)... select first option there.. ("reboot system now").. It will say "Rebooting..." in green colour..
* Now when screen gets black.. immediately press and hold volume down+home button+power button..
you will see a page saying "Warning"
A custom OS can cause critical problems in your phone and installed applications.. and it will say some more in next paragraph..
Dont worry about it.. Now press "Volume up" to continue to odin mode..
* you will see ODIN MODE written on top of screen in red..
Now make sure you are connected to your pc through usb cable and pc is logged in and open odin file..
*NOTE: In Odin you will see a yellow/blue color in one box below "ID:COM" section.. If you are not seeing yellow/blue restart your mobile and do same process from step 2. also restart your pc if its still not showing yellow. If it is showing then good.
* Now select "PDA" button under "Files [Download]" section.. A new window to browse files will get opened.. Locate the file boot.tar/boot.tar.md5 file you want to install.. select "boot.tar.md5"/"boot.tar" file..
* Now remember!! Only "PDA" "Auto Reboot" "F. Reset Time" options should be selected..
* Now you are ready to flash through odin.. Just press "Start" button.. and wait around 1 minute until odin finishes and the "yellow" box should show green... It will usually finish within 15 seconds to be precise..
* Now enjoy your brand new stock kernel.. Hope this helps you!!INSTALLATION PROCEDURE FOR KERNELS THROUGH KERNEL FLASHER TOOL[MAI77 METHOD] IN CWM:Difficulty --> *
* First Download all the files required ["boot.img" from the kernel thread first page of whichever one you want to install] and kernel flasher tool
* Copy these files inside SDCard.. boot.img (kernel), KernelUpdate.zip (Kernel Installer tool), CWM.zip (CLOCKWORKMOD)
Note: Don't keep these files inside any "FOLDERS".. Just copy it to SDCard root (parent) folder (Outside of all folders)..
* Switch off your mobile.
After a small vibration (switch off confirmation) PRESS and HOLD 3 BUTTONS (VOLUME UP+HOME BUTTON+POWER BUTTON)
when samsung galaxy logo appears, release the 3 pressed keys..
* After few seconds.. You will see Android system recovery (red text with 4 options lines)..
Select "apply update from sdcard"
Note: (Volume up+down for "scrolling" through options or selection of files, home button for "select" any option.. in CWM only: power button for "back" option)
Then Select "CWM.zip".
* ClockworkMod Recovery v5.0.2.6 is loaded now.
Select "install zip from sdcard"
Select "choose zip from sdcard"
Scroll and Select "KernelUpdate.zip" and select "Yes"
Wait till the menu appears again.. Now Go back
* Select "Reboot system now" and you have successfully installed Kernel.NOTE: THIS IS A GENERAL METHOD.. SHOULD WORK FOR MOST OF THE KERNELS.. BUT IF THERE WAS ANY PROBLEM LET ME KNOW.. I WILL EXCLUDE IT FROM THIS GUIDE.. IF YOU CANT UNDERSTAND INSTRUCTIONS IN KERNEL THREADS THEN ONLY TRY THIS.. YOU CAN CHOOSE TO USE ANY OF 3 INSTRUCTIONS TO INSTALL.. I HAVE WRITTEN THIS ASSUMING YOU ARE ON STOCK KERNEL/ YOUR KERNEL DOESNT HAVE CWM INBUILT. If it has.. then ignore stock recovery instructions mentioned in above instructions.. and directly start from CWM instructions..
CLICK HERE TO GO TO FIRST POST
How to deodex a stock rom in easy way using DSIXDA Kitchen
SPECIAL Thanks to dsixda Recognized Developer / Retired Senior Moderator who has made an all in one ROM kitchen. So thanks to him there are many custom roms are there in xda.
Difficulty --> **** IF YOU ARE NEW TO PC & ANDROID. This is not for you. If you are good with either one then you can try this.
PREPARATIONS:I Recommend you to use linux if you have it.
Kitchen by Dsixda [KITCHEN] Android Kitchen, v0.214 [Linux / Mac / Windows]
You need to have java installed in system to use the kitchen. All the steps for how to setup in windows/linux/mac has been explained well by dsixda in thread link. So i am not going to explain it here again. I assume your kitchen is set up and you are ready to work.
Make a backup in cwm and transfer the system.rfs.tar or system.ext4.tar file and boot.img file inside /sdcard/clockworkmod/backup/"dateofbackup"/ into PC.
Now go to the "/dsixda-Android-Kitchen/" folder and you should see these in that folder:
3 files & 3 folders it should contain:
- menu(file)
- Readme(file)
- .gitignore(file)
- original_update(folder)
- tools(folder)
- scripts(folder)
For Windows users--> Now open command prompt (If you installed Cygwin, then click on the Cygwin shortcut on your desktop to start it) and make sure you get to the path of that folder.. Ex. if folder is in c:\cygwin\home\"username"\dsixda-Android-Kitchen.. Then type this in command prompt..
Code:
cd dsixda-Android-Kitchen
Note: the capital letters should be in capital only when you type it... Note: Dont use space in folder names as cygwin wont work properly with space in folder names.
Or For Linux Users--> Now open terminal(Use CTRL+ALT+T). and make sure you get to the path of that folder.. Ex. if folder is in /home/"username"/Desktop/dsixda-Android-Kitchen.. Then you will be at /home/"username"/ . So type this in terminal.
Code:
cd Desktop/dsixda-Android-Kitchen
Note: the capital letters should be in capital only when you type it.
Now find that system.rfs.tar or system.ext4.tar file and boot.img file and paste it inside original_update folder. You will also find a file "put_rom_here_" Please ignore that file. Its just to tell you he has created that file.
Ok.. Now that you are at the right path.. just type ./menu in terminal or command prompt. From now on i am just going to say type this. It means you should type that and press "enter" to execute the command. If a menu didnt appear then type
Code:
pwd
You should see in which directory you are currently in. Try to get to the folder where kitchen folder is. Or follow steps again to get to there.
Now then, you should see this menu:
Code:
============================================================
Android Kitchen 0.214 - by dsixda (xda-developers.com)
============================================================
> MAIN MENU
1 - Set up working folder from ROM
2 - Add root permissions
3 - Add BusyBox
4 - Disable boot screen sounds
5 - Zipalign all *.apk files to optimize RAM usage
6 - Change wipe status of ROM
7 - Change name of ROM
8 - Show working folder information
0 - ADVANCED OPTIONS
00 - LEGACY OPTIONS (old and rarely used)
99 - Build ROM from working folder
u - Kitchen Info/Update/Donate
x - Exit
Enter option:
Enter option: 1
Press "Enter"
[CODE}Available ROMs:
(1) system.rfs.tar
Enter selection number (default=1, cancel=0, r=refresh):1[/CODE]
It will ask you this:
Code:
The new working folder will be named WORKING_111212_132324
Change the name (y/n)? (default: n):y
Give a name if you want to identify it easily next time.. for ex. i gave this "Enter a new name (using this prefix): WORKING_DDLJ1" as it is from DDLJ1 firmware update.. you can choose not to give name.
Now it will ask this:
Code:
Would you like to view this ROM's info (y/n)? (default: y):y
Give y as yes as i gave.
It would appear like this if it is stock roms backup:
Code:
Working folder information
Android OS version : 2.3.6
Device : GT-S6102
Model : GT-S6102
ROM Name : GINGERBREAD.DDLJ1
CSC version : S6102ODDLJ1
Rooted (Superuser app + su) : NO
Rooted (unsecured boot.img) : UNKNOWN
BusyBox installed : NO
BusyBox run-parts support : UNKNOWN
Apps2SD (Apps to EXT) enabled : NO
/data/app enabled : NO
Custom boot animation allowed : NO
Nano text editor installed : NO
Bash shell support : NO
/system/framework is deodexed : NO
/system/app is deodexed : NO
radio.img found : NO
ROM will wipe all data : NO
Press Enter to continue
Now press "Enter" to continue.
Setting up working directory complete.. You can close it anytime if you want when you are at main screen just type x and press "Enter". You can open it again and continue without making the above steps again..
Enter option:0 in main menu for "Advanced options"
Enter option:11
It will show like this:
Code:
NOTE: Reversing the de-odexing process by getting back the odex
files ('re-odexing') is not supported in the kitchen and would
be impossible to implement.
----------------------------------------------------------------
Found 23 *.odex files in system/framework
Found 110 *.odex files in system/app
Enter a choice:
bb = Back up both folders (do first!)
v = Set Android OS version (Current API level = 10)
IMPORTANT: Ensure you set the correct API level
f = Deodex /system/framework
a = Deodex /system/app
b = Deodex both folders (recommended)
s = Deodex a single file
x = Exit
?
Now type bb and press enter. (For safety, backup apks.. you can skip it if you want) Press "Enter" to continue.
Now type v and
Code:
Change the current API level (y/n)? (default: n):y
Please enter the new level number (currently: 15): 10
Press "Enter to continue.
Now type b to deodex your rom. Press "Enter" when this is asked,
Code:
Enable logging to file (y/n)? (default: y):
It will take some time depending upon your computer configuration. So take a small nap It takes 20 minutes in mine usually.
At the end if its successful.. you should see this:
Code:
Finished system/app
A summary of the deodexing has been logged in deodex_111212_133710.log
0 *.odex files remain in system/app
0 *.odex files remain in system/framework
Press Enter to continue
Now press "Enter" to get back to "Advanced options"
Now to make this as cwm flashable zip.. Then type 99 and press "Enter"
[CODE}Select a build option:
Number (default: 1):1
Would you like to optimize the APK files by zipaligning them (y/n)? (default: y):y
Use updater-script in ROM's ZIP file (y/n)? (default: y):y [/CODE]
Now it will show this:
Code:
An updater-script has been created under META-INF/com/google/android of
your working folder. Please review it and make any necessary changes. An
update-binary has also been added.
DO NOT delete any of the files under META-INF/com/google/android.
Proceed with the change (y/n)?
y = Proceed; updater-script and update-binary will be used in the ZIP
file; update-script will remain in working folder.
n = Cancel; updater-script and update-binary will be deleted and not
used.
? (default: y):
Now go to that "META-INF/com/google/android." folder.. And replace the "updater-script" with the file i have given in the attachment to this post. rename the "updater-script.txt" file i have given to "updater-script" and delete "update-script" file. Now after replacing the file type y in menu.
It will ask this:
Code:
It is recommended that you sign your ROM.
Sign it (y/n)? (default: y): y
The new ROM will be named GT-S6102_signed_111212_141640.zip
Change the name (y/n)? (default: n):y
and type new file name whatever you want and press enter
You will find the zip file inside OUTPUT_ZIP/"given name".zip
Now its ready to flash the zip file in CWM.
I will write about other options if any users/readers ask me to write it.. otherwise i may update it when i feel there is a need for that.
CLICK HERE TO GO TO FIRST POST
Miscellaneous section
THREAD TITLES CONFUSING? ITS EXPLAINED HERE!Difficulty --> *
[TAGS] --. Use these below tags on your title, So that people can identify it more easily and what the thread is for! Add it in front of the thread for better recognition of thread purpose.
[SOLVED] - for issues that have been fixed or [Q] that have been answered THIS IS A MUST TAG FOR SOLVED THREADS! IT WILL SAVE LOTS OF TIME FOR EVERYONE! PLEASE DO THIS WITHOUT FAIL ALWAYS!
[Q] or [QUESTION] - All Questions thread should have this.
[REQ] - Requests topics for ROM ports, INFO, THEME, MOD, etc.
[TUTORIAL] or [GUIDE] or [HOWTO] - How to do or Guides for some task or info for users/devs.
[UITIL] or [UTILITY] or [TOOL] -- Any kit or tool made for some specific task.
[APP/ 2.2+] -- Apps thread which contains apps made / ported / modded. 2.2+ such tag is also a must which tells what android os or above versions are supported.
[ROM] / [KERNEL] -- As name suggests its a rom development or kernel development thread.
[DEV] -- Developers related thread
[MOD} -- Modded ROM/KERNEL/APP etc thread
[ROOT] or [CWM] -- Rooting thread or root related to thread. CWM related thread.
[AROMA] -- Tool used in recovery. This means the thread for any ROM ? KERNEL ? OTHER WORKS has aroma to flash it.
[TWEAK] -- Tweaks to boost system performance speed etc thread.
[WIP] -- Work In Progress thread.
Also, please do add tags to your threads. See "TAGS" button above your "Quick reply option".. Now see right end of that line to find "EDIT TAGS" button. Click on it and words there.
Code:
Thread owners and others should add relevant words there
So that the thread gets added to searches which have those words
WHY GIVE THANKS? THANKS METER EXPLAINED!Difficulty --> *
Why to Give Thanks?
Giving thanks is important. It lets people know that their work or answer is appreciated. It is a faster method of feedback than posting a reply like "Thanks for your answer!" You must have made one post to give thanks,
You get 8 thanks per day, and they renew after 24 hours or so. Each thanks is independent of the others, so if you give someone a thanks at 3, and then another at 4, those will renew at 3 and 4 the next day. If you run out of thanks, then save that page in a new tab and give thanks later when you have one available. (Or if you are an app user then you can thank them through the app "Just tap on the post and touch thanks button on pop up bar which appears") If you use them all every day you are doing it correctly.
Thanks Meter:
You will see that everyone here has a Thanks Meter above their avatar.
Here are the counts needed to get to the next bar.
1st bar - 26
2nd bar - 51
3rd bar - 101
4th bar - 201
bug here, never gets to 5 bars, probably 501 if fixed.
6th bar - 1001
7th bar - 2001
8th bar - 5001
9th bar - 8001
10th! - 10000+
Not that thanks are an indication of a user's status or stature on XDA. Thanks don't really count for anything other than as a potentially wildly inaccurate measure of a member's ability to answer your question correctly. Some of the most important people here have a lot fewer thanks than you might guess. But it is a nice gesture to hit thanks button to those who helped you as they are not gaining anything in return!
STARS, USER TITLES: JUNIOR, MEMBER, SENIOR MEMBER........? READ TO KNOW MORE!Difficulty --> *
0 to 29 posts - Junior Member
30 to 99 posts - Member
100 + posts - Senior Member
Here is what our Senior Moderator said,
juzz86 said:
There are Junior Members, Members, Senior Members first. These make up the vast majority of XDAs userbase.
Recognised Contributors are nominated by other users and/or Mods/Developers. They are recognised for their contributions which are not specifically Development, such as detailed guides, one-click utilities and other tools/mods.
Recognised Themers are also nominated by users/Mods/Developers, for their work themeing custom ROMs and providing standalone themes for flashing.
Recognised Developers are nominated and approved by the Developer Committee, for their work in Development whether it be ROMs, Root methods, bootloader unlocks etc.
Elite Recognised Developers are again assessed by the Developer Committee, and are deemed to have gone above-and-beyond in providing knowledge/hacks/tools/apps/ROMs for the XDA community.
Forum Moderators are appointed by the Moderator Committee, after submitting an application (see the 'sticky' at the top of this forum - currently applications are not open). They are the first-line of keeping the forums tidy, friendly and orderly.
Senior Moderators are the next step up the ladder, providing site-wide support for Forum Mods and looking after the nitty-gritty issues, as well as areas of XDA not policed by FSMs, such as the Marketplace.
Administrators are next. There are several Admins - each look after a specific part of XDA such as the Portal, the Members and the User Experience of XDA as a whole.
At the top is Mike Channon, who is overall Forum Administrator.
Other titles you may come across:
Moderator Committee - sits on the Mod Committee
Developer Committee - as above, but for Developer Committee
XDA Newswriter - publishes articles for the Portal (front page)
Retired xxxx - have since officially 'left' their XDA position
Hopefully that clears most of them up for you
Contrary to what a lot of people expect, the thanks-meter does not figure at all in determining a users tag.
Click to expand...
Click to collapse
Wondering what those stars below the thanks meter mean?
It means that they've donated money directly to XDA.
A star = €10 euro donation.
A star with 10 written within it = €100 euros, as it represents 10 individual stars.
XDA/TAPATALK APP IMAGE UPLOADING PROBLEMS?? Difficulty --> *
Use Imgur Mushroom app.. its available at play store..
Its app size is very small.. Its a great app for multiple pictute uploads at once..
Whatsmore u can configure prefix and suffix text in settings to add [img] and [/img]..
After uploadingthe pics, it will save all links with prefix and suffix code in clipboard. ready made for you to paste it in the desired post using the XDA/TAPATALK app..
So all u need to do is paste it in post.. very easy and handy.. How to do it? Instructions below!
open imgur mushroom app. Select button right side to upload button which has this "..." button.
now select "settings" in the newly opened pop up menu.
now scroll down and select "output type" in URL settings section.
select "URL to direct image"
select "prefix text" and add [img]
select "suffix text" and add [/img]
now go back and select "pick" button and choose your pics to upload. Alternatively you can multi select in a file browser and share them to this app to upload too! Hope this helps!
MAKE YOUR THREAD/POST NEAT BY USING BBCODE [Bulletin Board Codes]: Difficulty --> *
You see in many Threads and posts people using something to make it look cool / formatted to make it more readable?
And you wish to make your threads/posts the same way??
Then look at this link provided by XDA.. I know many wont know about this..
BBCODE EXPLAINED WITH EX. BY XDA.. CHECK THIS LINK
I will add other info that are not informed there soon..
BATTERY DRAIN?? READ THESE TIPS TO AVOID IT! Difficulty --> *
Are you using live wallpaper? it takes more battery!
Go to Settings-->Accounts and Sync-->Auto-sync option-->uncheck it to save more battery.
If you keep using 3g/wifi it will use more battery.. Use 3g only when u download something..
If you are using widgets, it does drain battery faster.. If you want your battery to last longer, remove them or keep it to minimum 1 or 2. I dont use any widgets.
You have to pay attention to your apps running in the background. Try "Quick system info pro" or "ES Task manager" or "some other apps which shows detailed info on processes running. Stop those processes.
If you are using too many notifications features types of apps it will drain battery as they run in the background all the time..
Keep the screen brightness to as low as possible and readable still. Brightness does takes battery a lot.
Playing games does drain battery faster.
If you have custom kernel, and keep minimum freq higher then it will drain faster too
When u sleep at night and wake up at morning how much battery u lose? I loose around 1 percent.. If its more than 2-10% may be your deep sleep feature is not working.. Check it with CPU SPY app available at play store.
[DUOS ONLY]Do you keep both sims alive? I switch off 1 in sim manager.. Do it if you don't need it all time..
Inspired by a.cid and mf2112 threads.
Enable Whatsapp *AUTO DOWNLOAD IMAGE OPTION* in new versions [TRICK] (2.9.**** versions and above)Difficulty --> *
If you have lost "Auto-download images" option.. Then you are not able to disable the auto download of images. So, to get back that option in Settings-->Chat Settings. You need to do these steps below:
Note: Make sure you have a working Whatsapp already before attempting this. That is you should have already passed the verification process etc and able to chat with others.
Step 1 : Make sure you have "Ticked" option "Unknown sources" under Settings-->Application Settings.
Step 2 : Download this old version Whatsapp and transfer it to click on the downloaded file. It will ask "Replace application"
Press "OK". Then, Press "Install" button. After install press "done".
Step 3 : Now, switch on "Airplane Mode" to "ON" by lidroid toggle or in Settings-->Wireless & network settings--> Flight mode "ON"
Step 4 : Go to Settings-->Date & Time.. Change date to any date/ November/ 2012. Now, open the Whatsapp.. You should see a old Whatsapp.
Inside Whatsapp, Go to settings-->Chat settings and now turn off "Auto-download mages" option by "unchecking" the tick box.
Step 5 : Now, install the new Whatsapp if you have a backup of the app and turn off "Airplane mode" and now you can also update from play store if you dont have a backup of latest version of Whatsapp.
Now open the new Whatsapp and see the option "Auto-download image" option.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CLICK HERE TO GO TO FIRST POST
Useful links to threads/guides section
NOTE: I am not adding any SGY forum threads here.. as we all can look into it easily.. I am adding only other forums thread links of XDA which are very useful to us. So please dont ask me to add SGY forum thread links here. And if you find any useful threads which are not similar to already mentioned thread.. Then PM me the link.. I will add it if its good. Thank you for reading!Thread Titles with links and info about it are below:
****XDA SITE RELATED THREADS****[All XDA Members] Requests to Moderators and Admins --> Rather than sending a PM to an individual Moderator, please see this thread in need of Moderator or Admin assistance. They will all be monitoring this thread, and someone will reply without much delay.
XDA Android App - Problems / Bugs / Feature Requests etc. --> Report any faults you find with XDA app in this thread. You can also ask for new features, but cannot promise they will ever be delivered.
SPAM Users --> Any user Spamming in forums / threads? If you feel yes, then do go to this thread and report the user. Please give direct link to the users profile/posts which were spam so that it will help moderators.
[HOW TO]Make The Most Of The XDA App --> This is for all of you who use the app instead of desktop, but may not know how to do certain things.
I Will Post Your Question In The Dev Thread If.. --> Newbies not able to post in dev thread? Some report you want to get it there? Then check this thread to do exactly that!
Help Your Threads Get More Search Hits with Better Titles and Thread Tags! --> I have noticed that many threads do not have thread tags so I think most users don't know about them. This only works with
the XDA website, not the XDA app. Please read this thread to know more about tags which is a very useful method to get your thread popular!
Time Frame/Tell your story here on xda![Archive] --> Where we could talk about our years here at XDA. Lets see who is the oldest and what we have given to this forums.
Share your sig code please --> Very helpful to make your Signature look neat. Read this thread to make your signature better or if you have cool signature then post there.****GENERAL INFO THREADS****[MOD][2.56] AROMA Installer :: 121004-031 :: Open Source --> The World's First ANDROID Touch And Customizable ROM/KERNEL/MODS Installer
List of devices: ARMv7, ARMv6, ARMv5 --> I found a really nice thread that will maybe, help some developers who need to port Roms or for another Reason.
[v6.13] Online Nandroid Backup / Nandroid Backup without re-booting
[HOW-TO] Set up SDK/ADB on Ubuntu 11.10 | 32 & 64 bits
[TUTORIAL]How to make your own Live Wallpaper
[Tutorial/How-To][GB] Make Your Own Custom Rom & Kernel (Last Updated 30/07/2012)****ROM RELATED/INFO THREADS****
ROM DEVELOPMENT THREADS:
[HOW TO] Beginners Guide to Android ROM Development
[Guide]Complete Android ROM development and essential tutorials ~~ By Nero Young ~~
[KITCHEN] Android Kitchen, v0.213 [Linux / Mac / Windows]
[Ultimate Guide][Part 10 released][12/11/2011]Android App Development - From Scratch
ROM MOD THREADS:
[UTILITY] Android Utility - [apktool|dex2jar|smali|more][Mac & Linux][Feb13, 2012]
[MOD][HOW-TO]To disable signature checks
[GUIDE] How to add TABS to Settings with swipe gesture... \m/
[GUIDE] ICS Style 'Settings.apk' - Make it yourself !! !!
[UTIL][Sept 2 2012] Apktool v1.5.0 - a tool for reverse engineering apk files
[IDE][M10] Virtuous Ten Studio - The next level of editing apps
[KITCHEN][01/22] UOT Kitchen (Ultimate Online Theme Kitchen) version 4.0
[MOD][15 Toggles] How to mod Lidroid framework
[APP][DEV] Update me [ROM MAKER] - 2.0.3 - PUSH NOTIFICATION - (updated 2012-09-13)****KERNEL RELATED/INFO THREADS****
KERNEL DEVELOPMENT THREADS:
[KITCHEN]Android Kernel Kitchen 0.2.3 (Linux / Windows)
[Tutorial] Building Your First Kernel
HOWTO: Compile your own kernel from source (WIP)
[Tutorial] How to compile a kernel module outside the kernel
KERNEL MOD THREADS:
[REF][TWEAKS] Kernel Governors, Modules, I/O Schedulers, CPU Tweaks, AIO App Configs
[KERNEL MODULE] Extra modules pack v0.1.3 (feat. overclock) [OMAP4 kernel 3.0.8]****RARE/COOL APPS THREADS****[APP] Updated: 31/10/12 - PIT Magic v1.3.10 - Samsung PIT Creator, Editor, Analyzer!
[APP][DEV] ZipInstaller 2.4.2 for CWM-based + TWRP + 4EXT Recoveries
[APP][2.1+] Gidder - Git server for Android
[APP/5 NOV/2.2+]Turn screen off while MHL/HDMI mirroring WITH TOUCHPAD! [v1.96B11]
[APP][2.1+] FTP Server Ultimate - FTP, SFTP, FTPS server with multi-user, no-root
[App] WifiKill - disable internet for network hoggers (Android 4.x) [31/10/2012]
[App]Mediafire App for Android
[App][2.2+]LauncherWP8[6nov][v1.1.1]
[APP 2.2+] Android Tuner [BETA TESTING]
[APP]DroidSheep : ARP-Spoofing App for Android****MISCELLANEOUS THREADS****[TWEAKS][SCRIPTS] Collection of 'em all - build.prop; init.d; etc.
☠ [Add-on][Tweaks\\Mods]█ PIMP MY ROM █ v2.1.2 {Any Device // Any Rom}[AROMA][WIP] ☠
[Tool][Windows Only][Root] Android Reverse Tethering 2.30 --> surf on your phone using the ADSL of your PC.This work only for rooted users !
[ICON PACKS] mrFenyx's Icons - 8 packs, 800+ Icons, more to come
[Rooted][Guide]Wifi Reverse Tether - Windows and Ubuntu - Ad Hoc Networks CLICK HERE TO GO TO FIRST POST
Well, even though there are 2 kernel guides in our section.. Both are not complete.. So i thought of writing this.. a complete guide to make a kernel.
So, i'll keep updating this post as and when i get time to make it as good as possible..
Files Required:
You need to have Ubuntu or any other Linux distros.. But i recommend Ubuntu 11.10 32 bit as I'm using this version.
Kernel source from http://opensource.samsung.com . Search for 5360 and download "GT-S5360_GB_Opensource_Update3.zip"
Download Sourcery G++ Lite 2009q3-68 toolchain for ARM EABI from http://www.codesourcery.com/
Note: It should be Linux version without installer arm-2009q3-68-arm-none-eabi-i686-pc-linux-gnu.tar.bz2. Extract this file & you need to extract the file you got again to get "arm-2009q3" folder.
Download mkbootimg_src.zip from http://d-h.st/xnT
split_bootimg.pl is a perl script required to extract ramdisk from boot.img file. Or use dsixda or championswimmer's kitchen to extract it.
Get ncurses-5.9 lib if you want to work with menuconfig..Link
stock "boot.img" to extract ramdisk for your kernel.
Now that we have all the files required. Lets move on to next step of creating a Build Environment.
Build Environment Setup:
Make a folder. I'll call it "Kernel" folder here. You can name it whatever you want. Now, move the "arm-2009q3" folder inside this "kernel" folder. Extract mkbootimg_src.zip file and move "mkbootimg_src" folder inside "kernel" folder. Move "split_bootimg.pl" file under "kernel" folder too.
CLICK HERE TO GO TO FIRST POST
nice initiative but dont repeat any tuts which we already hav.. good luck!
hell_lock said:
nice initiative but dont repeat any tuts which we already hav.. good luck!
Click to expand...
Click to collapse
lol.. i know mate.. thats y i didnt write till today even though i wanted to write.. see the index page.. almost all are my own findings.. but whenever if i added from others.. then i will add credits as always..
do tell me / crrect me if i am wrong anywhere lol
nice guide...waiting for guide on building custom rom...
Sent from my GT-S5360 using xda app-developers app
anmolsharma1293 said:
nice guide...waiting for guide on building custom rom...
Sent from my GT-S5360 using xda app-developers app
Click to expand...
Click to collapse
My sign has it already..
Sent from my GT-S5360 using XDA
Hi, maybe you would like to incorporate my tool(AIOlog) in the retrieving logcat using computer as it works for Windows out of the box(provided that the driver is installed)
wcypierre said:
Hi, maybe you would like to incorporate my tool(AIOlog) in the retrieving logcat using computer as it works for Windows out of the box(provided that the driver is installed)
Click to expand...
Click to collapse
OK.. thanks for the heads up.. I will see.. I don't know about your tool yet.. so I have to see how it works.. and I still have to write about PC log too..
Thanks for the heads up..
Sent from the MUST have app!
nitubhaskar said:
OK.. thanks for the heads up.. I will see.. I don't know about your tool yet.. so I have to see how it works.. and I still have to write about PC log too..
Thanks for the heads up..
Sent from the MUST have app!
Click to expand...
Click to collapse
Basically for now its more or less the same as the ones in the market, but if you try the latest dev version, it has multiple device support(able to do logging even if there's more than one device, usually the logging would fail if there's more than one device) and many other features that are to be implemented
:good: :highfive:
This guide explains how to install and update CyanogenMod 11 (CM11) and SlimKat roms (aftermarket firmwares of Android 4.4) on your Motorola Defy (MB525) or Defy+ (MB526). Neither the CyanogenMod development team nor the Slim Roms development team officially support the Defy. Thankfully, a number of independent developers (listed below) are working hard to port those roms to the Defy, and the present versions are mostly (but not completely) bug-free and stable.
Please note: The latest CM11 and SlimKat roms for the Defy still have a few bugs, most of which are explained in a bug list that is frequently updated by okij. Although okij's bug list concerns the CM11 roms built by Quarx, most of these bugs also apply to TJKV's SlimKat roms, which are based partly on Quarx's sources.
If you just want a perfectly stable, bug-free phone, and don't care about having the latest and coolest features of Android, CM11 and SlimKat are not for you. I recommend installing CyanogenMod 7 (CM7) instead: it's very fast and perfectly stable. However, CM11 and SlimKat are continually becoming more stable, and are already usable as daily drivers if you can live with the few remaining bugs.
How to install Android 4.4 SlimKat or CM11 on the Motorola Defy or Defy+
Step 1: Download the correct files for installation.
If installing SlimKat, download the rom (Slim-mb526-4.4.2.build.4-UNOFFICIAL-20140407-2344.zip) and Google Apps package (minimal_Slim_AIO_gapps.4.4.2.build.4.zip) here.
If installing CM11, download the rom here (or here) and the minimal Google Apps package here (or here or here). (You want the file called "GApps_Minimal_4.4.4_signed.zip". Do NOT try to install the "Standard" Google Apps package, as there is not enough room on the Defy's system partition.)
Customize the rom file if desired. (See "Tips for customizing & improving performance," below.) Then put both files on your phone's SD card. Also download defy_twrp_recovery_2.6.3.0.zip and safewipe.zip, and put those files on the SD card too.
Note: SlimKat build 4 is very stable, but it does have a bug that causes the phone to reboot into recovery mode automatically if the phone encounters a telephony error, instead of rebooting normally. To fix this issue, download DefyParts.apk here and replace the old DefyParts.apk by following the instructions in this post.
Step 2: Install Team Win Recovery (TWRP) version 2.6.3.0 (or newer).
If you have already installed a custom recovery on your phone (e.g. ClockWorkMod or an earlier version of TWRP) and you know how to use it, just flash defy_twrp_recovery_2.6.3.0.zip and proceed to step 3. If you've never used a custom recovery, keep reading.
If you're using a stock rom from Motorola, you first need to root the phone (I recommend using either Framaroot or SuperOneClick), then install 2ndInit. Run the 2ndInit app and use it to install the custom recovery (ClockworkMod Recovery). Then reboot the phone, and watch the small LED light at the top of your phone. If the recovery was installed properly, the LED will light up with a blue color for a few seconds during startup. Allow the phone to fully boot up, then reboot the phone again and watch for the blue light. As soon as you see the blue light, press the volume down button to enter the bootmenu. Use the volume buttons to navigate the menu and the power button to select an option. Select Recovery > Custom Recovery > Backup and restore > Backup (all), and wait for the backup process to complete. This will create a backup of your system on your SD card, so you can revert to the stock rom later if needed. Next, select Go Back > install zip from sdcard > choose zip from sdcard, and install defy_twrp_recovery_2.6.3.0.zip.
Step 3: Install CM11 or SlimKat, and the corresponding Google Apps package.
After installing TWRP 2.6.3.0, reboot the phone and enter the bootmenu again by pressing the volume down button when you see the blue LED. (Note: If you're updating from a recent version of SlimKat or CM11, you won't see any blue light. Instead you'll see a screen that tells you to either press the menu button to enter recovery or the search button to continue with normal bootup.)
Enter TeamWin Recovery, which you can navigate with the touchscreen rather than the volume buttons. Wait 30 seconds before proceeding, to make sure the recovery is behaving in a stable way. (If the phone spontaneously reboots, just try again.)
Select Install, choose safewipe.zip, then swipe to confirm the flash.
In the same way, flash the rom of your choice (either SlimKat or CM11), followed by the Google Apps package.
Reboot the phone. The first boot will take a while (typically 5-10 minutes), since the phone has to build the Dalvik Cache.
Step 4: Set the correct baseband, and adjust performance settings.
Go to System settings > Advanced options > Device > Baseband selection, and make sure that the correct baseband is selected for your region and carrier. (Note: This step is not necessary if you already changed the default baseband in the zip file. See "Tips for customizing & improving performance," below.)
I also strongly recommend configuring the rom for better performance, by following the tips listed below. (See especially the tips about using Aero Kernel Control. This will help with many problems, for example the infamous call wakeup delay issue.)
Step 5: Thank our awesome developers, and donate to them if you can.
You can find donation links under any post by the developers. (Just look for the button that says "donate to me.") Here's the donation link for Quarx.
How to update SlimKat or CM11 to newer versions (or downgrade to older versions)
Step 1: Backup your current rom, apps, and settings.
I recommend using Online Nandroid Backup to create TWRP-compatible backups, for the reasons mentioned here (see bug #36). In the Online Nandroid Backup app, select Custom Backup > Backup Type > TWRP. Then select Backup Mode > Selective, and select the "system" and "data" partitions to backup. Make sure the Save Location is set to /sdcard, and also check the box to "Exclude Dalvik Cache." Then press the blue arrow (looks like a "play" button) at the top right corner of the screen to begin the backup.
Also back up your apps and settings with Titanium Backup.
Step 2: Download the updated rom.
Customize the rom file if desired. (See "Tips for customizing & improving performance," below.) Then place it on your phone's SD card along with the appropriate Google Apps package. [Note: if using CM updater, you don't have to download the rom ahead of time.]
Step 3: Install the updated rom using one of the following three methods:
Note: If switching from SlimKat to CM11 or vice versa, you must use the clean install method.
"Clean" install (recommended)
- Boot into TWRP by pressing the menu button when you see the bootstrap image (the screen that tells you to either press the menu button to enter recovery or the search button to continue with normal bootup), which should appear just after the Motorola logo disappears and before the boot animation begins.
- Select "Install" and flash safewipe.zip, then flash the updated rom, followed by Google Apps.
- After rebooting the phone, you'll have to restore your apps and settings using Titanium Backup. Don't restore settings for system apps unless necessary, as that may lead to problems.
"Dirty" flash (easier, but may cause problems)
- Boot into TWRP and select Wipe > Advanced Wipe, and select Dalvik Cache, Cache, and System (not Data), then swipe to wipe. (WARNING: Wiping the system partition also deletes the custom recovery, so you must either flash a rom or restore a backup before rebooting the phone. If the phone is rebooted before a new system is installed, it will be "soft bricked" and you'll have to flash a stock sbf with RSD Lite to recover it.) Then press the back button to return to the main menu and select Install. Flash the updated rom, followed by Google Apps. Now it is safe to reboot the phone.
- Since this method does not affect the /data partition, you won't have to restore all of your apps and settings, but you may still need to switch the baseband. If you encounter any bugs or problems after updating the firmware by this method, do not report them. First try a "clean" install, and check whether that solves the issue.
CM updater method (easiest, but may cause problems)
- If you're using CM11, you can update via the built-in CM updater located under Settings > About Phone > CyanogenMod Updates. (Obviously this won't work on SlimKat.)
- If you encounter any bugs or problems after updating the firmware by this method, do not report them. First try a "clean" install, and check whether that solves the issue.
Tips for customizing & improving performance
How to customize the rom before installation:
Install 7-zip on your PC.
Right-click on the CM11 or SlimKat zip file and select 7-zip > Open archive. (Don't extract it; just open it.) Now you can:
Remove unnecessary files to save space on the system partition. For example, you can navigate to system > media > audio, and delete any ringtones you don't use. You can also delete unused apps from system > app. See @x53's post here for a list of system apps that are safe to remove; see also here and here for more info. Here's a list of system apps that I removed before installing SlimKat: BasicDreams (live wallpaper), Browser (I use Next Browser instead), Calendar, Dashclock, Deskclock, Email (I just use Gmail app), Exchange2, Gallery2, Livewallpaperspicker, PhaseBeam (live wallpaper), PhotoTable, PicoTTS, Slimcenter, SlimFileManager, SlimIRC, SoundRecorder, VisualizationWallpapers.
Replace the default bootanimation in system > media. (Just drag and drop your custom bootanimation to replace the original.)
Replace the default bootstrap image in system > bootstrap > images.
Change the default baseband. To do this, navigate to system > etc > motorola > basebands, and find the zip file that corresponds to your region and carrier. Drag that file out to a folder on your PC, and extract (unzip) it. Then drag and drop those extracted baseband files into system > etc > motorola > bp_nvm_default, replacing the default baseband files in the rom.
Edit build properties. To do this, find the build.prop file in the system directory, and drag it out to a folder on your PC. Open the file in Notepad++, and edit the build properties as desired. (For example, you can change the LCD screen density by editing the line that says "ro.sf.lcd_density=". The default density in CM11 is 240, and the default in SlimKat is 213. Larger numbers make icons appear larger on your screen.) After making any desired changes, save the file and drag it back into the rom zip file where you found it, replacing the original.
After installation, configure the rom for better performance:
Install Aero Kernel Control from the Google Play store, which will allow you to tweak many settings to improve the performance of your phone. For starters, I recommend the following: In the Aero Control app, go to CPU Performance > Governor Settings, and select “ondemand”. The default is Interactive governor, which may be able to deliver slightly better performance if you know how to tweak its settings, but its default settings aren’t very good, so I recommend using On Demand at least initially.
If you want to try using Interactive governor, I recommend the following settings: open Aero Kernel Control, go to CPU Performance, select Interactive governor, then tap the little phone icon at the top right corner of the screen to open the settings for the Interactive governor. Set suspend_enabled to 0. That should help to reduce the call wakeup delay. Changing hispeed_freq and input_boost_freq to your maximum value (e.g. 1200000 if you've overclocked to 1200 MHz) will also boost performance, though you may see a slight drop in battery life. Note: Interactive governor is not recommended for CM11 builds prior to the 06-10 nightly, because the suspend/resume handler was missing. (See okij's note on bug #26 for more info.)
Open the HWA Settings app (which is already installed as part of the rom) and disable HWA for all apps except ones that really need it. (Explanation: HWA requires more RAM, and the Defy is already short on RAM, so enabling HWA usually does more harm than good. That's why it's best to disable it whenever it's not really needed for an app to function properly.)
The following apps require HWA: Camera, Dialer (on CM11 only), Google Maps (version 7+), Chrome browser. Other apps may also require HWA. If an app doesn't display properly, try enabling HWA again to see if that solves the problem.
Install Greenify, which you can use to “hibernate” any apps that you don’t want to run automatically at startup.
Other tips & suggestions:
You may wish to install Google Camera instead of the stock camera, for the reasons mentioned here.
For offline voice recognition, see here.
For better GPS performance, you may want to try flashing this zip and/or using this app. (Thanks to @Male_zvire and @okij for recommending these solutions.)
FAQ & what to do if something goes wrong
A freshly installed rom takes some time to "settle" while various services run in the background, so the phone may be a bit unstable at first. If you're still encountering errors or other problems after a few hours, first check the bug list and use the XDA forum search feature to see if the issue you are having has already been reported.
If you think you've found a new bug, don't just complain about it; try to help solve it by taking logs. @measel has provided a very helpful guide for taking logs.
What if the phone doesn't boot up properly?
If you can still access the custom recovery, just flash safewipe again and re-install the rom, or restore a backup. (To enter TeamWin recovery after installing SlimKat or CM11, press the menu button when you see the screen that tells you to either press the menu button to enter recovery or the search button to continue with normal bootup. That screen should appear just after the Motorola logo disappears, and before the boot animation begins.)
If you can't access the recovery, you may need to flash an sbf file using RSD Lite. Be careful! Flashing an sbf file improperly is one of the few things that can actually hard-brick the Defy, and if you flash the wrong sbf file for your phone, it may be impossible to restore your phone back to its original firmware. Read the All-in-One Defy Beginner's guide for more information about sbfs and RSD Lite. You can also check out the Motorola Defy wiki page for other tips and tutorials.
A special thanks to @Quarx, who has been faithfully updating our phone to newer and better firmwares since the beginning of Defy history, and has undoubtedly put more work into this project than anyone else. Thanks also to our many other developers, past and present: @TJKV (who uses Quarx's kernel sources to port SlimKat to the Defy), @Blechd0se (who has made significant contributions to the kernel development for the Defy and also developed the Aero Control app that we use to fine-tune the performance of our phones), @SlugZero, @YetAnotherForumUser, @struq, @htto, @Epsylon3, @maniac103, @walter79, @czechop, @kabaldan, and @Kayant. Many thanks to all of them, and to anyone I may have forgotten. Thanks also to @okij and other Defy users who have helped with testing new builds and identifying bugs for the developers to solve.
suggestion for improvement
Thanks for the guide. I'm pretty sure it is very useful for beginners!
I would suggest to try to get rid of as much text as possible and make it more step-by-step-y, you know what I mean? People (at least I recognized that on me) tend to give up quickly when it comes to reading. Right now it looks really difficult!
Just a suggestions. People will still appreciate your work as is. Thanks.
CM 7 and SBFS
Proverbs2 said:
The following is a guide that I wrote for one of my family members, and I decided to post it here so that others may benefit. I know there are numerous similar guides already in the forums, but they have not been updated recently. I intend to keep this guide updated for as long as I own a Defy (and I have no plans to get rid of my beloved phone anytime soon).
This guide explains how to install either CyanogenMod 11 (CM11) or SlimKat roms (aftermarket firmwares of Android 4.4) on your Motorola Defy (MB525) or Defy+ (MB526). Please note that neither the CyanogenMod development team nor the Slim Roms development team officially support the Defy. Thankfully, a number of independent developers are working hard to port those roms to the Defy, and the present versions are mostly (but not completely) bug-free and stable. A special thanks to @Quarx, who has been faithfully updating our phone to newer and better firmwares since the beginning of Defy history, and has undoubtedly put more work into this project than anyone else. Thanks also to our many other developers, past and present: @TJKV (who uses Quarx's kernel sources to port SlimKat to the Defy), @Blechd0se (who has made significant contributions to the kernel development for the Defy and also developed the Aero Control app that we use to fine-tune the performance of our phones), @SlugZero, @YetAnotherForumUser, @struq, @htto, @Epsylon3, @maniac103, @walter79, @czechop, @kabaldan, and @Kayant. Many thanks to all of them, and to anyone I may have forgotten. Thanks also to @okij and other Defy users who have helped with testing new builds and identifying bugs for the developers to solve.
Please note: The latest CM11 and SlimKat roms for the Defy still have a few bugs, most of which are explained in a bug list that is frequently updated by okij. Although okij's bug list concerns the CM11 roms built by Quarx, most of these bugs also apply to TJKV's SlimKat roms, which are based partly on Quarx's sources.
If you just want a perfectly stable, bug-free phone, and don't care about having the latest and coolest features of Android, CM11 and SlimKat are not for you. I recommend installing CyanogenMod 7 (CM7) instead: it's very fast and perfectly stable. However, CM11 and SlimKat are continually becoming more stable, and are already usable as daily drivers if you can live with the few remaining bugs.
Installation instructions for Android 4.4 SlimKat or CM11 on the Motorola Defy or Defy+
Step 1: Make sure you've downloaded the correct files for installation.
If installing SlimKat, download the rom (Slim-mb526-4.4.2.build.4-UNOFFICIAL-20140407-2344.zip) and Google Apps package (minimal_Slim_AIO_gapps.4.4.2.build.4.zip) here.
If installing CM11, download the rom here and the minimal Google Apps package (4-16_GApps_Minimal_4.4.2_signed.zip) here.
Put both files on your phone's SD card. Also download defy_twrp_recovery_2.6.3.0.zip and safewipe.zip, and put those files on the SD card too.
Step 2: Install Team Win Recovery (TWRP) version 2.6.3.0 or newer.
If you have already installed a custom recovery on your phone (e.g. ClockWorkMod or an earlier version of TWRP) and you know how to use it, just flash defy_twrp_recovery_2.6.3.0.zip and proceed to the next step. If you've never used a custom recovery, keep reading.
If you're using a stock rom from Motorola, you first need to root the phone and install 2ndInit. Run the 2ndInit app and use it to install the custom recovery (ClockworkMod Recovery). Then reboot the phone, and watch the small led light at the top of your phone. If the LED lights up with a blue color for a few seconds during startup, the custom recovery was installed properly, but you still need to upgrade the recovery to TWRP 2.6.3.0. Reboot the phone again and watch for the blue LED light. As soon as you see the blue light, press the volume down button to enter the bootmenu. Use the volume buttons to navigate the menu and the power button to select an option. Select Recovery > Custom Recovery > Backup and restore > Backup (all), and wait for the backup process to complete. This will create a backup of your system on your SD card, so you can revert to the stock rom later if needed. Next, select Go Back > install zip from sdcard > choose zip from sdcard, and install defy_twrp_recovery_2.6.3.0.zip.
Step 3: Installing CM11 or SlimKat
After installing TWRP 2.6.3.0, reboot the phone and enter the bootmenu again by pressing the volume down button when you see the blue LED. (Note: If you're updating from a recent version of SlimKat or CM11, you won't see any blue light, instead you'll see a screen that tells you to either press the menu button to enter recovery or the search button to continue with normal bootup.)
Enter the newly installed TeamWin Recovery, which you can navigate with the touchscreen rather than the volume buttons. Wait 30 seconds before proceeding, to make sure the recovery is behaving in a stable way. (If the phone spontaneously reboots, just try again.) Then select Install, choose safewipe.zip, then swipe to confirm the flash. In the same way, flash the rom of your choice (either SlimKat or CM11).
If you installed SlimKat, you can now install the minimal_Slim_AIO_gapps file in the same way, then reboot the phone.
If you installed installed CM11, don't flash the Google Apps package yet, or it will conflict with the Cyanogenmod setup and cause an error. You must first reboot the phone and allow it to fully boot up. Then reboot the phone once more and go into TWRP recovery again. (Note: This time, you won't see the blue LED light; instead you'll see a screen indicating that you can press the menu button to enter the recovery.) Select Wipe > Advanced Wipe > and wipe the Dalvik Cache and the Cache. Then press the back button twice to return to the main menu and select Install, then install the GApps_Minimal_4.4.2 zip file, and reboot the phone.
Note: The first boot will take a while (typically 5-10 minutes), since the phone has to build the Dalvik Cache.
Step 4: Configure the Rom.
Go to System settings > Advanced options > Device > Baseband selection, and make sure that the correct baseband is selected for your region and carrier.
Open the HWA Settings app (which is already installed as part of the rom) and disable HWA for all apps except ones that really need it. (I disable HWA for everything except the camera. The latest version of Google Maps also requires HWA, but I’m using an older version that doesn’t.)
I recommend installing Aero Control from the Google Play store, which will allow you to tweak many settings to improve the performance of your phone. I'll post some suggested settings when I have time later; but for starters, I recommend the following: In the Aero Control app, go to CPU Performance > Governor Settings, and select “ondemand”. The default is Interactive governor, which may be able to deliver slightly better performance if you know how to tweak its settings, but its default settings aren’t very good, so I recommend using On Demand at least initially.
I also recommend installing Greenify, which you can use to “hibernate” any apps that you don’t want to run automatically at startup.
Step 5: Thank our awesome developers, and donate to them if you can.
Click to expand...
Click to collapse
Hey
very usefull guide, thank you for it.
Two suggestions
Can you add how to switch back to CM7 from CM11 for those that installed and did not liked it?
and SBFS this Guide is intented for those who already know alot of topics like TWRP
can you insert a referneces to guide explaining how to root?
Thanks @measel and @yosef_a for your suggestions. I'll try to implement these ideas as soon as I have time.
Nice Guide
Thanks @Proverbs2 for this great guide.
For the sake of completeness, I would suggest you to add a section in the post on How to safely update from one nightly to a another newer/older nightly.
Iloveyou and thanks for that guide I've made my first succeded rom install ever
MelaPL said:
Iloveyou and thanks for that guide I've made my first succeded rom install ever
Click to expand...
Click to collapse
Congratulations! :laugh:
Aero kernel on SlimKat
Hello, first of all great guide, big thanks.
Did anyone have this problem using Aero Kernel (which is still awesome app :good on SK, every time i instal Aero k. and start to using it phone display become so dark that only in total dark place (brightnes is set to auto) is posible to read (relly hard), and after uninstaling AK every is fine
Did I miss something? tx
Mislav12 said:
Hello, first of all great guide, big thanks.
Did anyone have this problem using Aero Kernel (which is still awesome app :good on SK, every time i instal Aero k. and start to using it phone display become so dark that only in total dark place (brightnes is set to auto) is posible to read (relly hard), and after uninstaling AK every is fine
Did I miss something? tx
Click to expand...
Click to collapse
That's a strange bug. I'm using Aero Control on SlimKat 4.0, and I've never had that problem. Which SlimKat version are you using? Are you using the latest version of Aero Control from the Play store?
Proverbs2 said:
That's a strange bug. I'm using Aero Control on SlimKat 4.0, and I've never had that problem. Which SlimKat version are you using? Are you using the latest version of Aero Control from the Play store?
Click to expand...
Click to collapse
Firs of all thaks for reply.
I'm got one device on SK 3.85 (20140323) and other on 4.0 (didn't try to use aero kernel because of problems with first one-stupid me), eveythig working great, (first time I instal it, SK take my breath, really can't searching for more with that old and hardware limited device like Defy is). Used Aero Kernel from Play store, these days was the latest (about month ago), take a chance 3-4 times during 10 days but allways with same result - start to using AK, about 5-10 hours having no issue and then darknes
Another thing that I notice (forgive me if i'm on wrong thread, can't make post on dev section), when my devices was on stock ROM after installing 2nd booth app (nothing else) the phones start to have screen wake up delay, just like now, 2-3 sec. Is it possible to exist some connection or is just coincidence!?
Mislav12 said:
start to using AK, about 5-10 hours having no issue and then darknes
Click to expand...
Click to collapse
In Aero Control settings, try going to GPU Control > Display Color, and make sure "Energy Saver" is not selected.
after installing 2nd booth app (nothing else) the phones start to have screen wake up delay, just like now, 2-3 sec. Is it possible to exist some connection or is just coincidence!?
Click to expand...
Click to collapse
Do you mean 2nd Boot (not Booth)? What exactly are you installing, and where did you get it?
Have you tried changing your governor settings for better wake-up performance? The default governor (Interactive) is set to limit the CPU frequency to 600 MHz when the screen is off, which can cause slow wakeup. In Aero Control, try changing the governor to OnDemand (or set suspend_enabled to 0 for Interactive governor). That might help.
Proverbs2 said:
In Aero Control settings, try going to GPU Control > Display Color, and make sure "Energy Saver" is not selected.
Do you mean 2nd Boot (not Booth)? What exactly are you installing, and where did you get it?
Click to expand...
Click to collapse
You're wright, there is no left or right boot for Defy :silly:, i was thinking about 2ndInitDefy app, just didn't read well before posted. Defy on stock ROM with this app (only rooted, and 2ndInit installed!) became lagy when call is reciving.
Have you tried changing your governor settings for better wake-up performance? The default governor (Interactive) is set to limit the CPU frequency to 600 MHz when the screen is off, which can cause slow wakeup. In Aero Control, try changing the governor to OnDemand (or set suspend_enabled to 0 for Interactive governor). That might help.
Click to expand...
Click to collapse
Will try tomorrow and report.
Thanks a lott.
Mislav12 said:
i was thinking about 2ndInitDefy app, just didn't read well before posted. Defy on stock ROM with this app (only rooted, and 2ndInit installed!) became lagy when call is reciving.
Click to expand...
Click to collapse
That's very strange. I wonder if the SndInitDefy app is somehow conflicting with another app that you use. Try taking logs with CatLog and see if that provides any clues.
Proverbs2 said:
That's very strange. I wonder if the SndInitDefy app is somehow conflicting with another app that you use. Try taking logs with CatLog and see if that provides any clues.
Click to expand...
Click to collapse
To late for log taking, won't go back on stock rom. Beside, settings for Aero K. you recommend are super, no problem annymore. Got my voice on presidential elections!:good:
Thanks for compiling this guide. I've been using OmniRom for some weeks on both my Defys and it's worked with very few problems. I wanted to give Quarx latest build a try though, so followed your guide, as previously when I've flashed Quarx CM11, I've had problems with the 4 lower buttons not working. However after attempting to install Safewipe from TWRP, my phone froze on the Moto logo and I had to flash the stock rom and start again. I'm running CM7.2 on my spare phone. Strange that Safewipe caused the very problem that it's meant to avoid on my phone.
Snugglehog said:
Thanks for compiling this guide. I've been using OmniRom for some weeks on both my Defys and it's worked with very few problems. I wanted to give Quarx latest build a try though, so followed your guide, as previously when I've flashed Quarx CM11, I've had problems with the 4 lower buttons not working. However after attempting to install Safewipe from TWRP, my phone froze on the Moto logo and I had to flash the stock rom and start again. I'm running CM7.2 on my spare phone. Strange that Safewipe caused the very problem that it's meant to avoid on my phone.
Click to expand...
Click to collapse
That's unusual. Did you remember to flash defy_twrp_recovery_2.6.3.0, reboot into TWRP version 2.6.3.0, and wait 30 seconds before flashing safewipe?
Proverbs2 said:
That's unusual. Did you remember to flash defy_twrp_recovery_2.6.3.0, reboot into TWRP version 2.6.3.0, and wait 30 seconds before flashing safewipe?
Click to expand...
Click to collapse
The TWRP version was integral to OmniRom, so I think it was v2.7.0.0. However after booting into TWRP I doubt I waited 30 seconds before flashing Safewipe. Why the need to wait?
Snugglehog said:
The TWRP version was integral to OmniRom, so I think it was v2.7.0.0. However after booting into TWRP I doubt I waited 30 seconds before flashing Safewipe. Why the need to wait?
Click to expand...
Click to collapse
TWRP is unstable, and sometimes causes random reboots within the first 20 seconds. I'm guessing your phone rebooted while flashing safewipe.
Home buuton stopped working
After a couple of months of using slimkat v.3.85 today home button stopped working. There is also problem with notification, and telephony (not able to reach the phone, but making calls from device is possible). I found that someone has similar symptoms in Quarks kk4.4 thread:
Sounds like the device got 'unprovisioned', this sometimes happens and leads to at least some of the effects you listed: status bar problems, home button, settings. If you haven't nuked the thing yet you might try to manually set the provisioning bits:
Code:
#!/system/bin/sh
db=/data/data/com.android.providers.settings/databases/settings.db
prv_dev="INSERT INTO secure (name,value) VALUES ('device_provisioned','1'); INSERT INTO global (name,value) VALUES ('device_provisioned','1'); INSERT INTO secure (name,value) VALUES ('user_setup_complete','1');"
/system/xbin/sqlite3 "$db" "$prv_dev"
Click to expand...
Click to collapse
I'v tried tu run that script but with no luck, i am getting errors. It is probably becaouse this script is for Quarq KK not SLimkat.
Any Help? (Sorry for posting this question here, but i am unable to post in dev section.)
ktwist said:
After a couple of months of using slimkat v.3.85 today home button stopped working. There is also problem with notification, and telephony (not able to reach the phone, but making calls from device is possible). I found that someone has similar symptoms in Quarks kk4.4 thread:
I'v tried tu run that script but with no luck, i am getting errors. It is probably becaouse this script is for Quarq KK not SLimkat.
Any Help? (Sorry for posting this question here, but i am unable to post in dev section.)
Click to expand...
Click to collapse
I've never run into that problem, and I don't know if there's any easy way to fix it, but you could try just wiping data then restoring your apps and settings with Titanium Backup. Make a nandroid backup (so if wiping data doesn't help you can restore all your data easily), then wipe data, cache, and dalvik. If that doesn't work, you may have to do a clean install.