Autodesk AutoCAD 2015 (32-64 bit) Full + Keygen and Key
Autodesk AutoCAD 2015 new version designed by Autodesk - The leading and best 2D and 3D design software for architectural drawings, virtually building constructions and infrastructures and 3D drafting and modelling. Download AutoCAD 2015 crack, it allows designers, engineers and architects to create stunning designs using professional 2D and 3D CAD tools and features. Essentially, you will be able to make CAD designs, view and edit designs, and share your DWG files to AutoCAD Cloud. --->AutoCAD 2015 Features:<--- The AutoCAD 2015 CAD program includes new Ribbon galleries. - AutoCAD documentation features include associative array functionality. - Access drawing content directly from the ribbon.
- 3D associative array - Define arrayed objects when designing in 3D. - Intelligent command lineGet - AutoCorrect and Adaptive Suggestions. - Command preview - Preview outcomes of frequently used commands. - AutoCAD 2015 includes the New Tab page. - Professional documentation tools - Share design details with precise documentation tools. - Help window (enhanced) - Easily find where tools are located. - Package Drawing - Compress, store, and distribute CAD for Mac files. - Refined interface - New interface helps improve the design process - AutoCAD documentation features include Section and Detail views. - PDF support - Share and reuse designs easily with PDF support. - New Tab page - Quickly open new and existing drawings. - AutoCAD documentation features include an enhanced Help window - Associative array functionality - Maintain relationships between arrayed objects. - Easily customize and expand the user interface. - Section and Detail views - Access tools for creating Section, Detail views. - Share and access customization preferences - Customizable and expandable ribbon UI. - Design feed (enhanced) - Now use design feed on an intranet. - AutoCAD documentation features help you capture the precise details of your design. --->How to Install AutoCAD 2015:<---
Step 1- Install the program - double click on "AutoCAD_2015_English_Win_32bit_dlm.sfx.exe". Step 2- Finish the installation & restart AutoCAD. Step 3- Turn off your Internet connection and select I have an activation code from Autodesk. Step 4- Once at the activation screen: Open Keygen 32bits or 64bits version. Step 5- Copy the request code into the keygen and press generate. Step 6- Apply the patch. Step 7- Now copy the activation code back to the activation screen and click Next. Step 8- Enjoy. You've AutoCAD Full Version.
Adobe Photoshop needs no introduction. It has been the world’s most popular app for optimizing and editing images for more than twenty years. The introduction of Adobe Photoshop CS6 further cements the program's dominant position in the market.
Adobe Photoshop’s newest release CS6 is no exception to the venerable rule of Adobe quality. It comes with numerous new tools and features that make your graphics work quicker and easier, streamlining the entire process and while still allowing you to develop amazing pictures.
If you are considering the idea of installing Adobe Photoshop CS6 have a look at some of the key features below.
Mercury Graphics Engine
Allows you to instantly see results when you are using the puppet warp, distortion and liquefy tools. Image changes can be seen in real time, allowing you to navigate all your Photoshop documents and workspace more fluidly.
Newest Crop Tool
The crop tool in Adobe Photoshop CS6 has changed dramatically from the older version. The tool automatically selects the complete image, offering a wide range of preset features and other popular picture composition tools. It lets you quickly and easily modify the image, along with providing access to the legacy controls.
Painless Video Creation
The Adobe Photoshop CS6 team has made efforts to make video more intensive and effective. This tool is available in both standard and expanded version allowing quick trimming, removal and addition of image management, audio and other export formats.
Adaptive Wide Angle
This tool helps you easily straighten the images in wide angle or panorama as well as fish eyed pictures.
It is possible to save pictures in the background while the user is working on another image. This means there is no slow down in work flow and you do not have to wait for big files to write on the disk, increasing your overall productivity.
Awesome Blur Effects
Adobe Photoshop CS6 provides an awesome blur gallery that allows you to choose a perfect blur effect for your image. This tool gives you the ability to blur the entire image or just a selected area, making it a great tool for retouching.
So if you are looking to edit your images with speed, power and productivity using the latest design tools, Photoshop CS6 is probably the best program out there.
Since many users have problems with laggy on Redmi Note 4G, so i make this tutorial for disabling thermal engine for maximal performance on Redmi Note 3G/4G. For my research about Thermal Engine in Redmi Note 4G. it may decrease max CPU Frequency to 300mhz when CPU Temperature reached to 60C, why it not throttling by thermal config ??? so for now thermal-config-8226.conf is obsolete.
NOTE:USE AT YOUR OWN RISK!!! I will not take responsibility for anything happen to your phone
Prerequisites for ROOTED devices: - Rooted devices - Any CPU freq control (SetCPU, No-frills, Device Control, Kernel Tweaks, etc) - Root Explorer or similar apps
Step-by-step to Disabling Thermal Engine for ROOTED devices: 1. Open Root Explorer 2. go to /system/bin 3. Rename thermal-engine to thermal-engine.bak 4. Reboot your devices (Optional) 5. After reboot, set your CPU to 1190 Mhz to prevent overheated device or maybe lower than that if you want to have better battery life. But if you want to max cpu freq (1.5 Ghz) just skip this step. but like i said before, USE AT YOUR OWN RISK!!!
Step-by-step for NON-ROOTED devices:I will make flashable zip soon
This method worked me without using updatesif I you update lava x1 this method won't work
A Pc (Xp or up) Vroot v1.7.8 drivers (adb Drivers or install using Pdanet) and lastly Lava iris x1
Steps :- 1. Make your phone ready beforehand by installing the required USB drivers for your phone, so that when you launch VRoot it connects with ease. 2. Enable USB Debugging. 3. Install and Run VRoot, one or two clicks, voila, its rooted. [ Mobile restarts couple of times so don't worry]
now you see Vroot app in your app drawer that is it you have successfullly rooted your lava iris x1 If you want SuperSU install it from play store and it replaces vroot and you done download now Without computer Dear all Lava Iris X1 users, good news for you all, Who want root him device without PC. Ready and follow the below instructions or pictures carefully and easily :- (1)First download Towelroot apk from here.Download Now!!!! (2)Install and open it. (3)Tap continues 3 times on Welcome to Towelroot V3. (4)Coming box with this numbers on screen :1337 0 1 0 4 0. (5)Edit in box and change only 1 & 4, put 0 at the place of 1 & 4.. Like 1337 0 0 0 0 0. (be carefully change and please maintain the spaces). (6)Now click on Make it ra1n. (7)Root successfully done. Enjoy and give me
Please follow below pictures for your reference ;-
Installation of touch recovey for karbonn a25 Requiement *Rooted device *Mobile uncle tool Ported recovery Download link here... Place to SD card(not in any folder) Step 1: open the mobile uncle tool
Step 2: Launch Mobile Uncle Tools >>> You will get a popup tab from SU app for root access permission >>> Now, tap on Grant for SU permission >>> Tap on Recovery Update. You will get lots of options on Mobile Uncle tools app >>> Tap on recovery update option.
Step 3: You will see your recovery.img file with the location information of storage on your SD Card >>> Tap on the recovery.img file that it shown >>> Now, apply it. It will ask to you for reboot or go to recovery mode. Thats all.
MediaTek introduces new SoCs in 4G supportive range
MTK has provided the most widely used SoCs to be used in the market. Talking basically about Chinese market, more than half of the mobile devices are released having MTKs System on chips. Reason- low price and high performance (neglecting durability, stability and a few other marks).
A few days ago, MTK published a new SoC online, namely MTK MT6753. It was announced earlier this year and will be released during the Q4 season. It is:
A 64-bit Octa-core Chipset using Cortex-A53 cores.
ARM Mali-T760 GPU
Supports 16M display Screens.
Support for TD/FDD LTE internet and a bunch of other networks.
It is MTK’s second 64-bit SoC since MTK MT6732. It is more of a gift to China Telecom supported devices. Coming with support for CDMA 2000 1x, it supports EVDO Rev.A as well as 3G and 4G networks. But, it fails in providing frequency range, i.e. upto only 1.3GHz-1.5GHz and with 1080p display screen only! It is targeted to power mid range, high end promising devices. MTK’s 4G Quad-core processors like MT6735 and MT6735M also uses A53 cores and have frequency of 1.3GHz-1.5GHz and 1.0GHz respectively. Worth noting that the Bo JiuTang( Insider analyst) himself posted about this, proving the truth about the existence of Mtk MT6735.
Karbonn a2+ Booster Script What is this script? This is a init.d script which will manage CPU frequencies, governors, IO scheduler, etc. based on the phone state.
Users are free to use this but ROM developers please DO NOT include this in your ROM. Please direct a link to this thread. This will make things at one place
Why I should use this script? I have observed annoying LAG in many (almost all) 4.0.4 ROMs. I did some investigation and figured out that if we set the proper CPU governor and frequency then the lags are reduced greatly. I am happy with MIUI rom with this script...I feel like 4.1 ROM smoothness.
Well, this is not a big thing. I can do it easily. What different specialty this script has? Its not a big thing to set the frequency and governor but if you do it, it will eat your battery a lot. Running your CPU at full speed and both cores active is gonna take battery down very fast. So I thought that what if the settings are applied ONLY WHEN phone is active. When phone is sleeping, go back to default power saving settings. So we will have performance when needed with good battery backup. So I decided to write a init.d script which will manage this.
But, let me declare this - This script is aimed to improve performance. Expect little more battery drain than normal. If you want performance, you have to bear this. Also properly setting governors and frequencies you can minimize the battery impact.
init.d script, no need any app
Sets CPU governor and freques depending on phone state - awake or sleeping
High performance when you need the phone
Battery saver when phone is not in use
Configurable settings - choose your favourite configuration with few simple steps
Sets ADJ and MINFREE parameters to get good RAM
Supports multiple profiles - like setcpu (coming soon)
Aroma installer to choose your suitable configuration.(coming soon)
Will this work only on 4.04 or other ROMS as well It will work on any ROM with proper kernel. In fact this can work on any device
The command output should change as you awake or sleep the phone.
How bsuhas is going to enhance this? Yes. I am planning to enhance the script further - adding condition that while charging, everything runs at full speed. some other setting which will make this script eventually a single point of performance boost of all times. You would not need anything else. I am also embedding this script in Suvi Tool.
mtk not released source till now, till they release, we have to totally depend on "reverse engineering".... my attempt here is to provide a directory (collection of mod) for mtk devices....share whatever you got fully working or beta mods & themes... mention your device, processor & android version at the end..you can discuss here regarding any mods..... op will be updated as soon as a new mod is found, providing link to that post....
Hey guys, I noticed that some porters are having some problems in porting MIUI to other devices. So here's a guide for those in need, hope it can be of some help. :)
The guide has been updated to help those who want to an OTA update file. Please find the download below. Enjoy. :)
Patchrom Developer Guide
1. Introduction Patchrom is a open-source project initiated and maintained by MIUI team. It mainly utilizes the assembler/disassembler technology to craft a MIUI ROM for an existing ROM. Although this project is for MIUI ROM, but the technology and tools is general for crafting any android ROM.
1.1 Setup Develop Environment
We recommend to use 32bit Debian 6+ or Ubuntu 10+ (64bit is also possible but you have to install some 32bit compatibility libs). Currently we have no plan to run patchrom project on Windows and Mac OS X.
Also you need: At least 32gb free for pathrom repo and project building. At least 2gb RAM without GUI (X Window enviroment) or 3gb+ with GUI.
1.1.1 Java Development Kit
Sun's Java 6+ JDK (or OpenJDK) is required for patchrom building.
sudo apt-get install java7-jdk for OpenJDK 7 (Debian/Ubuntu)
After ANDROID SDK installation is complete, modify the PATH environment variable to provide access to SDK's tools/ and platform-tools.
Edit your ~/.bash_profile or ~/.bashrc file. Look for a line that sets the PATH environment variable and add the full path to the tools/ and platform-tools/ directories to it. If you don't see a line setting the path, you can add one: <sdk> is your android SDK installation directory.
Patchrom doesn't require the android source code to build. But it will be better to understand and have the android source code for reference. See http://source.android.com/source/index.html for how to get and build the source code.
1.2 Download the source
$ mkdir patchrom $ cd patchrom $ repo init -u git://github.com/MiCode/patchrom.git -b jellybean (The value is $ repo init -u git://github.com/MiCode/patchrom.git -bjellybean42-mtk for mtk port) $ repo sync
Pachrom is used to craft MIUI ROM for android device. So for each specific device there is a standalone directory for this device. For example, currently we support Sumsung i9100, Huawei honor, Sony lt18i and HTC sensation.
And there are some directories which are common to all devices:
(1) android/: This directory contains all the stuff related to the baseline ics source code released by google. (2) build/: This directory contains all the makfile for build. (3) miui/: This directory contains all the APKs and 3 jars built from MIUI source code and also all the resources. (4) tools/: This directory contains all the scripts, apps used to build the project. Especially, we used the apktool and smali/baksmali. Thanks to those guys for contributing them.
Assume current directory is patchrom and we will build the ROM for Huawei Honor: $ . build/envsetup.sh $ cd honor $ make fullota After build completed, there will be a fullota.zip under out directory which is ready for flash into honor through recovery.
2. Preparation work
From now on, we want to clarify two concepts: recovery-ROM and ROM. When we talk about Recovery-ROM, we specifically mean a ROM which can be flashed into device in recovery mode. It is a zip file and conforms to the standard format required by recovery. When we talk about ROM, it is a general concept; for those file which can be flashed into your device to update the system is called a ROM. Also the flash method varies, e.g, Samsung's odin, Motorola's RSD, Sony uses fastboot etc.
The patchrom project only generates recovery-ROM, since this kind of ROM is most general and flexible.
In order to successfully and smoothly craft miui recovery-ROM for your own device, it is important do some preparation work. In one word, the critical point is to find a suitable ROM for your device.
2.1 Familiar with your device
The first step is to familiar with your device, includes how to flash ROM, how to root and try some ROMs aimed at your device. The main work of this step is to surf some android forums which have rich information for your device. Here is a forum you definitely should look at: http://forum.xda-developers.com/
2.2 Choose suitable ROM
After getting acquainted with your device, be prepared to choose a suitable ROM for patchrom project. How to decide if a ROM is suitable, here are some guidelines:
(1) Android version must be in minor difference. Currently, patchrom is based on the ics-4.0.3. The chosen ROM's version should be ics-4.0.1 to ics-4.0.3. The principle here is that the chosen ROM's android version's source code should be in minor change to the android version's source code used by patchrom.
(2) Stock ROM The stock ROM which is released by device manufacturer is preferred. Since the stock ROM is most stable.
(3) Root Generally speaking there are 2 kinds of root: root privilege and kernel root. The root privilege means that will be a Superuser app which will popup a dialog to ask if you approve the request when other apps require root privilege. The kernel root means you can directly manipulate this device in root privilege via adb. The kernel root is preferred.
(4) Recovery Since patchrom generates a recovery-ROM, So be sure that your device can enter recovery mode. The CWM recovery and ext4 recovery are good choices.
3. Craft miui recovery-ROM When a suitable ROM is found and has already been flashed into your device, we will start our crafting journey.
3.1 Generate base recovery-ROM
Firstly, we should create a standalone directory for the device. Let's use an imaginary device called xblade and assume current directory is patchrom. $ . build/envsetup.sh $mkdir xblade $ cd xblade
Secondly, we will run a tool to automatically generate a recovery-ROM from the running device. You may ask, why we bother to generate a recovery-ROM if we already find a suitable ROM. There are two reasons: (1) Sometimes we can't find a stock recovery-ROM. But we requires a recovery-ROM as the basis. (2) Most importantly, running this tool first is critical to automaticly generate miui recovery-ROM and incremental OTA which makes miui so special.
Now connect your device to PC, ensure the USB Debug mode is on. $ adb reboot recovery (if this command doesn't work, manually reboot into recovery mode) $ ../tools/ota_target_from_phone -r (-r means run this tool in recovery mode, we can also run this tool in normal mode, please refer to the source of this tool for more information)
This tool will generate a stockrom.zip and a metadata directory which will be used to generate our miui recovery-ROM.
We need a makefile to let make work. Here is a makefile to begin with:
We will explain some definitions in this file, for thorough understanding, you definitely should look at the whole build system.
local-zip-file: the recovery-ROM generated in previous section, must be specified for each device.
local-out-zip-file: the output recovery-ROM filename when you run "make zipfile"
local-miui-modified-apps: all the miui apps are listed in the file patchrom/build/miuiapps.mk. This variable defines those miui apps which we modified.
local-modified-apps: This variable defines those apps from local-zip-file which we modified.
local-miui-removed-apps: Normally not all the miui apps is suitable for our device(e.g. some device will not want Phone.apk). This variable defines those miui apps which we don't want.
local-phone-apps: This variable is used to remove some apps from local-zip-file. As you can see, we use blacklist for miui apps and whitelist for stock ROM apps. This variable defines those stock ROM apps which we want to keep.
local-zip-misc: This target permits you to do some customization before we generate the final recovery-ROM.
The first make command we will run is "make workspace". This will prepare the workspace for you. The operation is simple, it will extract framework/android.policy/services.jar and framework-res.apk from stockrom.zip and run apktool to disassemble them.
The second make command we will run is "make firstpatch". Before diving into this command, we need to talk about smali. We use apktool to disassemble the jar/apk which generates smali code. We will use framework.jar.out(which is the disassembled smali code from framework.jar) as an example to discuss this:
There are 3 smali code directories involved: (1) old framework.jar.out (2) new framework.jar.out (3) target framework.jar.out
At first time, the old framework.jar.out will be the disassembled framework.jar which is compiled from google released source code, the new framework.jar.out will be the disassembled framework.jar which is compiled from miui's source code. The target framework.jar.out will be the disassembled framework.jar from target device which is already prepared in "make workspace".
In order to facilitate this process, we try the best to make minimum change to the google released source code. You can see these change by compare miui/src and android/src. But most often there will be some conflicts when applying the patch.
After running this command, there will be a temp directory. There will be 5 child directories: (1) old_smali: the smali code from old framework.jar.out with .line removed (2) new_smali: the smali code from new framework.jar.out with .line removed (3) dst_smali_orig: the smali code from target framework.jar.out with .line removed (4) dst_smali_patched: the smali code after applying the patch into target framework.jar.out with .line removed (5) reject: the rejected patch. We should use this directory to resolve the conflicts.
You may raise a question: what if miui makes further change to the source code, how can we track these changes.
Firstly, please record the newest commit number of android/framework.jar.out when you run "make firstpatch". Assume the commit number is abcdefg.
Then at some time, the android/framework.jar.out will be updated and assume the newest commit number is hijklmn. run "tools/git.patch abcdefg..hijklmn > patch.file".
Finally at your device directory, run "tools/git.apply < ../android/patch.file". Now you can resolve any conflict.
After resolved the conflicts, you can run "make fullota" to build the final recovery-ROM. This command will generate fullota.zip under out directory. Flash this file in recovery mode. And now your device may boot successfully and see the miui lockscreen. But most often things are not going so well, don't worry. "adb logcat" will be the great tool to help us. From now on, there will be a problem-solving loop. Solve the problem or exception we encountered.
How to make OTA
Let’s say we’ve made fullota for 3.1.18, and there will be a file named target_files.zip under the out directory, rename it aslast_target_files.zip. For 3.1.25, we’ll make a new fullota, and now we have last_target_files.zip and target_files.zip under the out directory. And we’ll use these two files to make OTA.
Note: target_files.zip in the older version must be renamed, or it will be covered after you’ve made a new fullota.
Let’s say the current directory is /home/patcher/patchrom
-k recognizes signature key -i recognizes the last target_files out/target_files.zip refers to the new target_files ota_update.zip designate a name for the newly created OTA file
First of all, you should read the source code to understand the whole build system.
Secondly, you can refer to the devices we already finished, especially for the devices from same manufacturer.
Finally, please post your issue and we will try to answer it. It will be highly appreciate if you open source your device, you can use our server to release the ROM to users and enjoy the live MIUI through OTA update.