Related
Modifications To The System And Structure Of A Himalaya's Part.1
Hello from the fact that my work on OS-em-and the Himalaya, have been suspended, I decided to write about cooking light kursik to our old, but the active device. All the tools and commands tyczą only that device. If you do not, although basically in that you do not know, do not start the following modifications to the memory ROM. Let's say that the tutorial is intended for advanced users, or young kuchcików. Starting kuchcenie, we must bear in mind the reasonable thinking, and before any wgramy ROM, our authorship, we must be sure that the changes made responsible. Let's start! :
Compatible:
O2 XDA II, T-Mobile MDA II, Qtek 2020, iMate Phone Edition, TSM500, and other variants PH10
1) Cookware:
To facilitate the work, the light we create an application based on the console (command line).
So, we open any text editor, which uses a record format in a text file -> *. Bat, *. cmd, *. nt (U me it's Notepad + +)
Open the editor and we enter a string of commands:
Code:
@ echo off
: Intro
cls
echo.
echo.
echo.
echo. Designed for Models:
echo. O2 XDA II, T-Mobile MDA II, Qtek 2020,
echo. iMate Phone Edition, TSM500, and other PH10 device
echo.
echo.
echo.
echo.
pause
cls
: phone
echo.
echo.
echo. [1] - This ROM dump
echo. [2] - REGISTRY. Dv To. Rgu
echo. [3] - Change Initflashfiles
echo. [4] - Dump ROM to NK.NBF
echo.
echo.
echo.
echo.
Set / P Choice = Choose:
IF '% Choice %'==' 1' GOTO: 1
IF '% Choice %'==' 2' GOTO 2
IF '% Choice %'==' 3' GOTO: 3
IF '% Choice %'==' 4' GOTO: 4
IF '% Choice %'=='' GOTO: EXIT
set choice =
GOTO: Intro
====================================================================
: 1
cls
echo.
set choice =
echo. in the course of his work ...
title Convert Image System .....
TOOLS \ xda2nbftool-x nk.nbf nk.nba 0x20040304
echo.
pause
title Preparation of system files .....
TOOLS \ prepare_imgfs.exe nk.nba
echo.
pause
title Dump System ..............
TOOLS \ viewimgfs.exe imgfs_raw_data.bin
pause
set compatible = yes
echo. Done!
GOTO: PHONE
====================================================================
: 2
cls
echo.
set choice =
echo.
echo.
set _FLATRELEASEDIR =. \ dump
TOOLS \ rgucomp.exe-nologo-o dump \ default.hv> default.rgu
TOOLS \ rgucomp.exe-nologo-o dump \ user.hv> user.rgu
echo.
echo.
echo.
echo.
echo.
echo.
echo ...
echo.
pause
copy default.rgu TOOLS \ For default.hv \ boot.rgu
TOOLS \ For default.hv \ boot_rgu__default_hv.bat
move TOOLS \ For default.hv \ default.hv dump \ default.hv
set compatible = yes
echo. Done!
GOTO: PHONE
==================================================================================
: 3
cls
echo.
set choice =
mkdir INITFLASHFILES
copy dump \ initflashfiles.dat initflashfiles.dat.txt
initflashfiles.dat.txt
echo.Change this txt.
echo. Save to ....
pause
attrib dump \ initflashfiles.dat-r-h
the dump \ initflashfiles.dat
copy initflashfiles.dat.txt dump \ initflashfiles.dat
attrib dump \ initflashfiles.dat + r
echo.
set compatible = yes
echo. Done!
GOTO: PHONE
==================================================================================
4
cls
echo.
set choice =
title Image Filing System ....
echo. in the course of his work ...
echo.
TOOLS \ BuildImgfs.exe
TOOLS \ make_imgfs.exe nk.nba
TOOLS \ xda2nbftool.exe-c-u nk.nba
TOOLS \ xda2nbftool.exe-x nk.nba nk.nbf 0x20040304
@ move nk.nbf Upgrade \ nk.nbf
@ CD. \ Upgrade \
@ HimaUpgradeUt_noID.exe
Upgrade DEL \ nk.nbf
set compatible = yes
echo. Done!
GOTO: PHONE
Save the file in a format -> *. bat - for example, something called Cook_Rom
* Remember that this process will be repeated in order to build the \ in the line ..
Info:
-> [1] - This ROM dump - spread your ROM - the file nk.nbf on parts (Files and Modules)
-> [2] - REGISTRY. dv To. rgu - default.hv extract the files and registry user.hv, compiles to. rgu, which gives us the freedom of its readability and modification
* IMPORTANT: we need to remember that each of these files:
- In the first line had entered the name "REGEDIT4"
- Between each row, you must free at least one line
- All the registry files must be encoded in Unicode - the aforementioned editor has such a function
-> [3] - Change Initflashfiles - this file is compiled with. dat to. txt, mainly used for relocation and arrangement of folders on your system
-> [4] - Dump ROM to NK.NBF - Our modified, or ported ROM together, that is, the file nk.nbf
After:
Spread shell ROM into:
• Create a directory eg Hima_Cook
• Copy to the:
- The basis of our work, namely the file -> nk.nbf
- We created above Create_Rom
• In Hima_Cook, create a subfolder:
- TOOLS
The subfolder Tools , we copy the necessary tools:
• xda2nbftool.exe
• prepare_imgfs.exe
• viewimgfs.exe
• BuildImgfs.exe
• make_imgfs.exe
• RecMod.exe
• rgucomp.exe
• cereg400.dll
• cecompr_nt.dll
• HimaUpgradeUt_noID.exe - this is one of the applications that our upgrade snapshot of the phone in Bootloader mode
Create another subfolder called "Upgrade" - Copy to him HimaUpgradeUt_noID.exe
In a further process, find out why some of the commands and the names of folders and tools are the essential, only to say that we need to carefully watch all of our lines *. bat . In this file there are commands to copy, move, modify, and run different applications and files.
Over time, understand the functionality and capabilities, which gives us this form of cooking.
Features:
The --title gives us the ability to change the information in the process of the upper beam on the console
Outro:
Everything described above gives us mainly TRADE dump folder and open all sorts. All tools and folders are arranged in an appropriate manner, so we can be sure of our small stoves that can not cause any error, when pichceniu. Another positive side, this is well and that our system consists in a single whole
In the following parts of the course, we'll include as a basis to modify, add applications, etc. I invite you to Part Two ...
Next part of the course coming soon....
just ask for sumthin,,,
this is good post(best i think)
but i wanna i ask you sumthin,, can u share what software are u use for,,coz for me learning by doing was better than just watch...thanx for your hard works...
THX, for the beginner is the science .... to better understand the whole principle of subsidies. I will finish this course, as soon as possible ....
This is a good service...
This is a good service to my friends thank you very much.
Very please
i m done with
USER.HV
DEFAULT.HV
still cant find BOOT.RGU in dump folder...
i've also checked the hidden files....
where to get TOOLS FROM?
CAN ANYONE GIVE A LINK
CANNOT FIND =
The subfolder Tools , we copy the necessary tools:
• xda2nbftool.exe
• prepare_imgfs.exe
• viewimgfs.exe
• BuildImgfs.exe
• make_imgfs.exe
• RecMod.exe
• rgucomp.exe
• cereg400.dll
• cecompr_nt.dll
all ok now found files in many himalaya kitchens...
I invite you to Part Two ...
hey nosker ...
any news or will it happen-I invite you to Part Two ...
will you do a part two ???
would be good for himalaya users!
Nokser no longer have a himalaya.
advanced15 said:
hey nosker ...
any news or will it happen-I invite you to Part Two ...
will you do a part two ???
would be good for himalaya users!
Click to expand...
Click to collapse
try and pm him.
MODIFICATIONS
In this part of the course, as a general rule, we modify our system.
It connects to the addition and removal of various types: application, file or even substitutions skins and overlays system. But we must remember not to reload the ROM to us, because when it comes to our device is limited to 32 MB.
Let's start now, modify the presentation of the sample. This applies in particular for new cooks. In this process, we can breathe lightly and not to think that somehow our uwalimy device. It is rare that the phone is not included in the substitution or deletion of a program.
Remember - all the changes shown in this article are just an example. The need to know (for this example) which add and remove what ... .. To do the work ....
First what we need in our oven, and a folder to obtain "dump"
Open kitchen, based on the command line, which is created in the first part of this course:
We viewed the 4 position, select:
[1] - This ROM dump
I wait until the process is complete ... ... ..
Upon completion, we can see each other, exactly the folder.
Then, for the subsequent work click on:
[2] - REGISTRY. dv To. rgu
In the root, we have established the following two files:
-default.hv
-user.hv
Both files opened with - Notepad + + . See a string, something like this:
Code:
REGEDIT4
[HKEY_CLASSES_ROOT \. Zip]
@ = "zipfile"
[HKEY_CLASSES_ROOT \. Rar]
@ = "PocketRAR"
[HKEY_CLASSES_ROOT \ SimToolkit.UI]
@ = "UI Toolkit"
[HKEY_CLASSES_ROOT \ SimToolkit.UI \ CLSID]
@ = "(7B58F1D9-1C13-440f-894B-B90680570A2D)"
[HKEY_CLASSES_ROOT \ ExSMime.MimeReader.1]
@ = "MIME Reader"
Important:
-> In the beginning we have to enter the registry:REGEDIT4
-> Also, see if between each key is at least one blank line, ie there is no entry
-> All files. Rgu save in UNICODE, so we have opened such as default.rgu in Notepad + + click File> Encoding> Unicode
-> New keys entered by us, can not double the old
In this way we have prepared a record, we can now freely edit.
Now, we'll file Initflashfiles.dat
With this file we will not have in total, no problems. The only thing we will be interested to add or remove tracks, of course, they are dependent on the arrangement of folders and applications, or the peaks appearing in them.
For a deeper understanding of an application to add a ROM, but it must be in OEM format, how to do this? This is described at some length on the Internet. The second of the output, are designed for the software, which of the files. Cab form OEM
Insert into the application:
Consider, for example, the Pocket RAR in OEM format. Open the folder, we are interested in it:
- inietflaszfiles.txt,
- *. rgu - Registry File
- PocketRAR.exe - program
- PocketRAR.lnk - shortcut
In the first instance, to copy the folder dump: - PocketRAR.exe - software
I PocketRAR.lnk - shortcut
Open your file initflaszfiles.txt to the OEM:
Code:
Directory ( "\ Windows \ Start Menu \ Programs"):-Directory ( "Accessories")
Directory ( "\ Windows \ Start Menu \ Programs \ Accessories"):-File ( "Pocket RAR.lnk", "\ Windows \ RAR.lnk Pocket")
copy its contents to the main Initflashfiles.dat from the dump. This is to look like this.
This is the end of the passage of this file:
Code:
......
;================================================= =========================
; SAP MASD customization settings
;================================================= =========================
Directory ( "\ Windows \ AppButtons"):-File ( "Calendar.lnk", "\ Windows \ calendar.lnk")
Directory ( "\ Windows \ AppButtons"):-File ( "Contacts.lnk", "\ Windows \ addrbook.lnk")
Directory ( "\ Windows \ AppButtons"):-File ( "Tasks.lnk", "\ Windows \ tasks.lnk")
Directory ( "\ Windows \ AppButtons"):-File ( "Record.lnk", "\ Windows \ voice.lnk")
Directory ( "\ Windows \ AppButtons"):-File ( "Camera.lnk", "\ Windows \ camera.lnk")
Directory ( "\ Windows \ AppButtons"):-File ( "Messaging.lnk", "\ Windows \ tmail.lnk")
Directory ( "\ Windows \ AppButtons"):-File ( "Camera.lnk", "\ Windows \ Camera.lnk")
Directory ( "\ Windows \ AppButtons"):-File ( "Comm Manager.lnk", "\ Windows \ CommManager.lnk")
Directory ( "\ Windows \ StartUp"):-File ( "BPInsert.lnk", "\ Windows \ BPInsert.lnk")
Directory ( "\ Windows \ StartUp"):-File ( "coldinit.lnk", "\ Windows \ coldinit.lnk")
Directory ( "\ Windows \ StartUp"):-File ( "bugtrap.lnk", "\ Windows \ bugtrap.lnk");
Directory ( "\ Windows \ StartUp"):-File ( "poutlook.lnk", "\ Windows \ poutlook.lnk")
Directory ( "\ Windows \ StartUp"):-File ( "HandsFree.lnk", "\ Windows \ HandsFree.lnk")
Directory ( "\ Windows \ StartUp"):-File ( "Welcome.lnk", "\ Windows \ welcome.lnk")
Directory ( "\ Windows \ StartUp"):-File ( "ScreenRotate.lnk", "\ Windows \ ScreenRotate.lnk")
;================================================= =========================
; End - SAP MASD customization settings
;================================================= =========================
;================================================= ================================================
; Pocket RAR Home
;================================================= ================================================
Directory ( "\ Windows \ Start Menu \ Programs"):-Directory ( "System")
Directory ( "\ Windows \ Start Menu \ Programs \ System"):-File ( "Pocket RAR.lnk", "\ Windows \ RAR.lnk Pocket")
;================================================= ================================================
; Pocket RAR End
;================================================= ================================================
Then, open *.rgu and copy its contents to default.rgu or user.rgu.
Writing kluchy, is dependent on its path. Each new path has to be in this part of the registry where the key begins in the same way.
An example of a registry entry for PocketRAR:
Code:
[HKEY_CLASSES_ROOT \. zip]
@ = "PocketRAR"
[HKEY_CLASSES_ROOT \. Rar]
@ = "PocketRAR"
So we have to place it where keys start with:
Code:
[HKEY_CLASSES_ROOT]
If the operation completed successfully, that the application will work poprawnie.Do modify the registry, are the various outputs, my way is not a last resort. This type of keys, and their removal also save our memory, which is extremely low.
We can also replace the driver or a new version of the program such as File Explore - in this case, replace the virtual memory address and the address of relocation, because otherwise this application does not start. Saved as a module, which is different from the file? Look up to our dump, you can see the difference at first glance, the content is located in the directory.
The fact is that the conversion module, with the newer ROM version, we also need to replace these two values as described above. Podmieniając file, we do not have the obligation to relocate, even under the old addresses.
Welcome to Part three of this Course
To translate the system - the relationship and functionality of files and modules ....
Direct link to the precompiled ROM: http://www.filefactory.com/file/cfe8147/GWK74-buzz-20111111.zip (please hit thanks if you find this ROM useful )
Setting up the development environment
Install the current stable Debian: squeeze (6.0) amd64 (not the i386 version, and not the testing/unstable version). Do not ask me for a working Ubuntu version -- I don't know. Use Debian instead
Code:
apt-get install python git bzip2 zip unzip lzma patch bison flex \
make gcc g++ gcc-multilib g++-multilib gperf libz-dev lib32z-dev curl \
libncurses5-dev lib32ncurses5-dev libx11-dev openjdk-6-jdk
Downloading the sources and other packages
AOSP 2.3.7r1 (GWK74) is the current version of the AOSP
arco's 2.6.35 kernel is the base for the kernel we will build
koush's vendor files contain the HTC proprietary blobs for buzz
CyanogenMod's device/htc/buzz
Code:
git clone https://github.com/arco/buzz-kernel-2.6.35.git
git clone https://github.com/koush/proprietary_vendor_htc
git clone https://github.com/CyanogenMod/android_device_htc_buzz.git -b gingerbread-release
Code:
mkdir ~/bin
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
chmod +x ~/bin/repo
export PATH=~/bin:$PATH
Code:
mkdir 2.3.7_r1; cd 2.3.7_r1
repo init -u https://android.googlesource.com/platform/manifest -b android-2.3.7_r1
repo sync
mkdir -p vendor/htc
cp -r ../proprietary_vendor_htc/buzz vendor/htc
cp -r ../android_device_htc_buzz device/htc/buzz
The "repo sync" may take a while, so please be patient
Compiling the kernel
Code:
cd ../buzz-kernel-2.6.35
make ARCH=arm buzz_defconfig
At this point you can edit .config and change CONFIG_MSM_CPU_FREQ_ONDEMAND_MAX to overclock the CPU, for example setting it to 700 MHz.
Code:
make ARCH=arm -j4 CROSS_COMPILE=../2.3.7_r1/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-
cp arch/arm/boot/zImage ../2.3.7_r1/device/htc/buzz/prebuilt/kernel
cp drivers/net/wireless/bcm4329/bcm4329.ko ../2.3.7_r1/device/htc/buzz/prebuilt/bcm4329.ko
Patching the sources
Several files must be patched. The following patches are from CyanogenMod 7:
armv6j.mk.patch: adds a new architecture (ARMv6J) which targets the MSM7225
browser.patch: provides a small fix to prevent the Browser from crashing
camera.patch: enables the use of Froyo (2.2) libcamera.so
dalvik-armv6j.patch: adds a new ARMv6J target for JIT compilation by the Dalvik runtime environment
gpsshim.patch: enables the use of Froyo (2.2) libgps.so
libagl.patch: enables the use of copybit to make software OpenGL support a bit faster (I think)
surfaceflinger.patch: another cool patch from CM7 when transparency is not supported
The following patches were made by myself:
config.xml.patch: several values which are present in CM7 but not AOSP must be disabled
LOCAL_MODULE_TAGS.patch: a bunch of Android.mk in hardware/msm7k lack this variable
ota-no-recovery.patch: prevent ota_from_target_files from flashing the recovery (we like our ClockworkMod better )
vendork-blobs.mk.patch: adds library libOmxCore.so which is needed by mediaserver
The following patches are from Google:
apns-conf.xml.patch: adds a bunch of APNs that are not present in the default AOSP file
For your convenience, I have included all the patches in a single file, which is attached to this post (patch-buzz.zip).
Code:
cd ../2.3.7_r1
wget -O patch-buzz.zip "http://forum.xda-developers.com/attachment.php?attachmentid=779411"
unzip patch-buzz.zip; ./patch-buzz/apply.sh
ln -s full.mk build/target/product/full_base.mk
rm -rf device/htc/buzz/overlay/packages
Setting up a custom vendor
At this point you may want to add a number of custom additions, for example:
a simple boot animation: http://forum.cyanogenmod.com/topic/19198-simple-generic-boot-animation/
Superuser root package: http://forum.xda-developers.com/showthread.php?t=682828
Torch from CyanogenMod: http://download.cyanogenmod.com/?type=stable&device=buzz
Talk and Android Market: http://wiki.cyanogenmod.com/wiki/Latest_Version
Google Maps for WildFire: http://forum.xda-developers.com/showpost.php?p=15218646&postcount=4
Code:
mkdir vendor/xdbg; cd vendor/xdbg
wget http://duck.at.shangtai.net/files/android/bootanimation.zip
wget -O su-2.3.6.1-ef-signed.zip http://dl.dropbox.com/u/6408470/su-releases/su-2.3.6.1-ef-signed.zip
wget http://download.cyanogenmod.com/get/update-cm-7.1.0-buzz-signed.zip
Also download gapps from http://goo-inside.me/gapps/gapps-gb-20110828-signed.zip , put it in 2.3.7_r1/vendor/xdbg and run:
Code:
unzip su-2.3.6.1-ef-signed.zip
wget -O system/app/Maps.apk http://forum.xda-developers.com/attachment.php?attachmentid=641716
unzip update-cm-7.1.0-buzz-signed.zip system/lib/libOmxCore.so
unzip update-cm-7.1.0-buzz-signed.zip system/app/Torch.apk
unzip -o gapps-gb-20110828-signed.zip
mv system/lib/libOmxCore.so ../htc/buzz/proprietary
I haven't tried it, but you can try to include the LatinIME.apk from CM7 in order to get the dictionaries (not included by default in AOSP).
Now we'll create the Makefile that specifies which files are to be copied in the ROM. Be careful when copy-pasting to not truncate the last line which is quite long:
Code:
echo "\$(call inherit-product, vendor/xdbg/xdbg.mk)" >>../../device/htc/buzz/buzz.mk
cat >xdbg.mk <<"EOF"
PRODUCT_COPY_FILES += \
vendor/xdbg/bootanimation.zip:system/media/bootanimation.zip \
vendor/xdbg/system/bin/su:system/xbin/su \
vendor/xdbg/system/lib/libvoicesearch.so:system/lib/libvoicesearch.so \
vendor/xdbg/system/app/Superuser.apk:system/app/Superuser.apk \
vendor/xdbg/system/app/Torch.apk:system/app/Torch.apk \
vendor/xdbg/system/app/Talk.apk:system/app/Talk.apk \
vendor/xdbg/system/app/Vending.apk:system/app/Vending.apk \
vendor/xdbg/system/app/GenieWidget.apk:system/app/GenieWidget.apk \
vendor/xdbg/system/app/Maps.apk:system/app/Maps.apk \
vendor/xdbg/system/app/NetworkLocation.apk:system/app/NetworkLocation.apk \
vendor/xdbg/system/app/GoogleServicesFramework.apk:system/app/GoogleServicesFramework.apk \
vendor/xdbg/system/app/GoogleContactsSyncAdapter.apk:system/app/GoogleContactsSyncAdapter.apk \
vendor/xdbg/system/app/GoogleCalendarSyncAdapter.apk:system/app/GoogleCalendarSyncAdapter.apk \
vendor/xdbg/system/framework/com.google.android.maps.jar:system/framework/com.google.android.maps.jar \
vendor/xdbg/system/etc/permissions/com.google.android.maps.xml:system/etc/permissions/com.google.android.maps.xml
EOF
Building the ROM
Code:
cd ../..
. build/envsetup.sh
lunch [I](choose htc_buzz-userdebug)[/I]
make -j5 otapackage WITH_DEXPREOPT=true[I]
(5 is for a quad-core with 4GB of RAM. you can decrease it if you have less RAM)[/I]
Remove WITH_DEXPREOPT=true above to generate a de-odexed ROM.
Advantage of a de-odexed ROM: you can easily replace APKs or JARs in /system.
Disadvantages: the first boot takes a while because all APKs must be odexed. Also the dalkvik cache takes a significant amount of space (up to 50 MB) in /data (CM7 uses /cache so this is not a problem).
Note that you will not need the Android SDK since adb and other tools will be present in the PATH after you run lunch and the out/host part is compiled.
The generated ROM is out/target/product/buzz/htc_buzz-ota-*.zip. Wiping the whole data partition in ClockworkMod is required if your previous ROM was built with different signing keys.
Finally, I'd like to thank everyone who made this possible: cyanogen, arco, koush, HDCRJacob, schiznik, _thalamus & AdamG, ben1066, nhnt11 and everyone else who contributed on porting the AOSP on the WildFire. You guys are awesome
reserved
also reserved for future use
wow
Thats a very comprehensive guide )
I think you may be overcomplicating things though - if you run "make -jX otapackage" instead of just make, the build process will create a flashable zip for you.
Further to this, you can create your own vendor_blah repo, which will allow you to remove things like the recovery from the otapackage, and set a custom modversion during the build
schiznik said:
Thats a very comprehensive guide )
I think you may be overcomplicating things though - if you run "make -jX otapackage" instead of just make, the build process will create a flashable zip for you.
Further to this, you can create your own vendor_blah repo, which will allow you to remove things like the recovery from the otapackage, and set a custom modversion during the build
Click to expand...
Click to collapse
Super cool! I'll add your suggestions in a later release I need to get back my WildFire to test it all, so far I have great hope to fix the graphics with the patches from arco68. BTW, in your testing, would you recomment the 2.6.32 (htc-kernel-buzz) or 2.6.35 from arco's GitHub? Both seem fairly similar to me although the 2.6.35 get updated more often.
schiznik said:
I think you may be overcomplicating things though - if you run "make -jX otapackage" instead of just make, the build process will create a flashable zip for you.
Click to expand...
Click to collapse
I prefer making bacon myself. Then it compiles, squishes and zips in one process.
arco68 said:
I prefer making bacon myself. Then it compiles, squishes and zips in one process.
Click to expand...
Click to collapse
Hey arco68 Any comment on the 2.6.32.41 vs 2.6.35.10 kernels? I'd say the 2.6.35 should be more fitted to GR* (like 2.6.32 was for FR*), but I'd really like to hear your opinion on this.
I prefer 2.6.35 for gingerbread, as it's easier to keep up to date and patch with stuff from CAF and Google's kernels.
arco68 said:
I prefer 2.6.35 for gingerbread, as it's easier to keep up to date and patch with stuff from CAF and Google's kernels.
Click to expand...
Click to collapse
Yea 2.6.35 is the gb kernel. I can't use make bacon as I don't use cm's vendor, make devnull does the same though
Many thanks for the input arco68
Sent from my HTC Desire using XDA App
Do you know what would be so nice? It would be really nice is someone could update this to the newest source so that it could actually be relivant
Minor thread hijack...
If you want to build Oxygen for buzz - you can do the below:
Code:
mkdir android ; cd android/
repo init -u [email protected]:schiznik/oxygen_manifest.git -b gingerbread
repo sync
. build/envsetup.sh
lunch 8
make oxygen
You can optionally use "repo -j20 sync" to sync 20 of the repo's at once, and make -jX oxygen, where X is the number of CPU cores that you are using to build.
Once completed, there is a update-oxygen-*.zip file in out/target/product/buzz/ that can be flashed.
Nice !Very interisting
Thanks a lot, schiznik. I'll update the main thread.
EDIT: main thread updated. the sources compile, although I haven't tested the resulting ROM yet.
schiznik said:
Minor thread hijack...
If you want to build Oxygen for buzz - you can do the below:
Code:
mkdir android ; cd android/
repo init -u [email protected]:schiznik/oxygen_manifest.git -b gingerbread
repo sync
. build/envsetup.sh
lunch 8
make oxygen
You can optionally use "repo -j20 sync" to sync 20 of the repo's at once, and make -jX oxygen, where X is the number of CPU cores that you are using to build.
Once completed, there is a update-oxygen-*.zip file in out/target/product/buzz/ that can be flashed.
Click to expand...
Click to collapse
For those who have tried this and get the reply "public key error". Try editing the repo init line to read "repo init -u https://github.com/schiznik/oxygen_manifest -b gingerbread" this works for me. I'm busy report syncing now, will inform you further, when it completes.
Sent from my HTC Wildfire using xda premium
Gandolff said:
For those who have tried this and get the reply "public key error". Try editing the repo init line to read "repo init -u https;//github.com/schiznik/oxygen_manifest -b gingerbread" this works for me. I'm busy report syncing now, will inform you further, when it completes.
Sent from my HTC Wildfire using xda premium
Click to expand...
Click to collapse
Update, repo sync complete, but to many errors to create software package. I'm looking onto it.
Sent from my HTC Wildfire using xda premium
xdbg said:
Link to prebuilt ROM: http://www.filefactory.com/file/cfe8147/n/GWK74-buzz-20111111.zip
Setting up the development environment
Install the current stable Debian: squeeze (6.0) amd64 (not the i386 version, and not the testing/unstable version). Do not ask me for a working Ubuntu version -- I don't know. Use Debian instead
Code:
apt-get install python git bzip2 zip unzip lzma patch bison flex \
make gcc g++ gcc-multilib g++-multilib gperf libz-dev lib32z-dev curl \
libncurses5-dev lib32ncurses5-dev libx11-dev openjdk-6-jdk
Downloading the sources and other packages
AOSP 2.3.7r1 (GWK74) is the current version of the AOSP
arco's 2.6.35 kernel is the base for the kernel we will build
koush's vendor files contain the HTC proprietary blobs for buzz
CyanogenMod's device/htc/buzz
Code:
git clone https://github.com/arco/buzz-kernel-2.6.35.git
git clone https://github.com/koush/proprietary_vendor_htc
git clone https://github.com/CyanogenMod/android_device_htc_buzz.git -b gingerbread-release
Code:
mkdir ~/bin
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
chmod +x ~/bin/repo
export PATH=~/bin:$PATH
Code:
mkdir 2.3.7_r1; cd 2.3.7_r1
repo init -u https://android.googlesource.com/platform/manifest -b android-2.3.7_r1
repo sync
mkdir -p vendor/htc
cp -r ../proprietary_vendor_htc/buzz vendor/htc
cp -r ../android_device_htc_buzz device/htc/buzz
The "repo sync" may take a while, so please be patient
Compiling the kernel
Code:
cd ../buzz-kernel-2.6.35
make ARCH=arm buzz_defconfig
At this point you can edit .config and change CONFIG_MSM_CPU_FREQ_ONDEMAND_MAX to overclock the CPU, for example setting it to 700 MHz.
Code:
make ARCH=arm -j4 CROSS_COMPILE=../2.3.7_r1/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-
cp arch/arm/boot/zImage ../2.3.7_r1/device/htc/buzz/prebuilt/kernel
cp drivers/net/wireless/bcm4329/bcm4329.ko ../2.3.7_r1/device/htc/buzz/prebuilt/bcm4329.ko
Patching the sources
Several files must be patched. The following patches are from CyanogenMod 7:
armv6j.mk.patch: adds a new architecture (ARMv6J) which targets the MSM7225
browser.patch: provides a small fix to prevent the Browser from crashing
camera.patch: enables the use of Froyo (2.2) libcamera.so
dalvik-armv6j.patch: adds a new ARMv6J target for JIT compilation by the Dalvik runtime environment
gpsshim.patch: enables the use of Froyo (2.2) libgps.so
libagl.patch: enables the use of copybit to make software OpenGL support a bit faster (I think)
surfaceflinger.patch: another cool patch from CM7 when transparency is not supported
The following patches were made by myself:
config.xml.patch: several values which are present in CM7 but not AOSP must be disabled
LOCAL_MODULE_TAGS.patch: a bunch of Android.mk in hardware/msm7k lack this variable
ota-no-recovery.patch: prevent ota_from_target_files from flashing the recovery (we like our ClockworkMod better )
vendork-blobs.mk.patch: adds library libOmxCore.so which is needed by mediaserver
The following patches are from Google:
apns-conf.xml.patch: adds a bunch of APNs that are not present in the default AOSP file
For your convenience, I have included all the patches in a single file, which is attached to this post (patch-buzz.zip).
Code:
cd ../2.3.7_r1
wget -O patch-buzz.zip "http://forum.xda-developers.com/attachment.php?attachmentid=779411"
unzip patch-buzz.zip; ./patch-buzz/apply.sh
ln -s full.mk build/target/product/full_base.mk
rm -rf device/htc/buzz/overlay/packages
Setting up a custom vendor
At this point you may want to add a number of custom additions, for example:
a simple boot animation: http://forum.cyanogenmod.com/topic/19198-simple-generic-boot-animation/
Superuser root package: http://forum.xda-developers.com/showthread.php?t=682828
Torch from CyanogenMod: http://download.cyanogenmod.com/?type=stable&device=buzz
Talk and Android Market: http://wiki.cyanogenmod.com/wiki/Latest_Version
Google Maps for WildFire: http://forum.xda-developers.com/showpost.php?p=15218646&postcount=4
Code:
mkdir vendor/xdbg; cd vendor/xdbg
wget http://duck.at.shangtai.net/files/android/bootanimation.zip
wget -O su-2.3.6.1-ef-signed.zip http://dl.dropbox.com/u/6408470/su-releases/su-2.3.6.1-ef-signed.zip
wget http://download.cyanogenmod.com/get/update-cm-7.1.0-buzz-signed.zip
Also download gapps from http://goo-inside.me/gapps/gapps-gb-20110828-signed.zip , put it in 2.3.7_r1/vendor/xdbg and run:
Code:
unzip su-2.3.6.1-ef-signed.zip
wget -O system/app/Maps.apk http://forum.xda-developers.com/attachment.php?attachmentid=641716
unzip update-cm-7.1.0-buzz-signed.zip system/lib/libOmxCore.so
unzip update-cm-7.1.0-buzz-signed.zip system/app/Torch.apk
unzip -o gapps-gb-20110828-signed.zip
mv system/lib/libOmxCore.so ../htc/buzz/proprietary
I haven't tried it, but you can try to include the LatinIME.apk from CM7 in order to get the dictionaries (not included by default in AOSP).
Now we'll create the Makefile that specifies which files are to be copied in the ROM. Be careful when copy-pasting to not truncate the last line which is quite long:
Code:
echo "\$(call inherit-product, vendor/xdbg/xdbg.mk)" >>../../device/htc/buzz/buzz.mk
cat >xdbg.mk <<"EOF"
PRODUCT_COPY_FILES += \
vendor/xdbg/bootanimation.zip:system/media/bootanimation.zip \
vendor/xdbg/system/bin/su:system/xbin/su \
vendor/xdbg/system/lib/libvoicesearch.so:system/lib/libvoicesearch.so \
vendor/xdbg/system/app/Superuser.apk:system/app/Superuser.apk \
vendor/xdbg/system/app/Torch.apk:system/app/Torch.apk \
vendor/xdbg/system/app/Talk.apk:system/app/Talk.apk \
vendor/xdbg/system/app/Vending.apk:system/app/Vending.apk \
vendor/xdbg/system/app/GenieWidget.apk:system/app/GenieWidget.apk \
vendor/xdbg/system/app/Maps.apk:system/app/Maps.apk \
vendor/xdbg/system/app/NetworkLocation.apk:system/app/NetworkLocation.apk \
vendor/xdbg/system/app/GoogleServicesFramework.apk:system/app/GoogleServicesFramework.apk \
vendor/xdbg/system/app/GoogleContactsSyncAdapter.apk:system/app/GoogleContactsSyncAdapter.apk \
vendor/xdbg/system/app/GoogleCalendarSyncAdapter.apk:system/app/GoogleCalendarSyncAdapter.apk \
vendor/xdbg/system/framework/com.google.android.maps.jar:system/framework/com.google.android.maps.jar \
vendor/xdbg/system/etc/permissions/com.google.android.maps.xml:system/etc/permissions/com.google.android.maps.xml
EOF
Building the ROM
Code:
cd ../..
. build/envsetup.sh
lunch [I](choose htc_buzz-userdebug)[/I]
make -j5 otapackage WITH_DEXPREOPT=true[I]
(5 is for a quad-core with 4GB of RAM. you can decrease it if you have less RAM)[/I]
Remove WITH_DEXPREOPT=true above to generate a de-odexed ROM.
Advantage of a de-odexed ROM: you can easily replace APKs or JARs in /system.
Disadvantages: the first boot takes a while because all APKs must be odexed. Also the dalkvik cache takes a significant amount of space (up to 50 MB) in /data (CM7 uses /cache so this is not a problem).
Note that you will not need the Android SDK since adb and other tools will be present in the PATH after you run lunch and the out/host part is compiled.
The generated ROM is out/target/product/buzz/htc_buzz-ota-*.zip. Wiping the whole data partition in ClockworkMod is required if your previous ROM was built with different signing keys.
Finally, I'd like to thank everyone who made this possible: cyanogen, arco, koush, HDCRJacob, schiznik, _thalamus & AdamG, ben1066, nhnt11 and everyone else who contributed on porting the AOSP on the WildFire. You guys are awesome
Click to expand...
Click to collapse
Plessis guys there is there problem with this download link. I'm not able to download the file.
Sent from my HTC Wildfire using xda premium
Gandolff said:
Plessis guys there is there problem with this download link. I'm not able to download the file.
Sent from my HTC Wildfire using xda premium
Click to expand...
Click to collapse
Did you *really* need to quote the entire post?
I'm assuming you meant the GWK74-buzz-20111111.zip from filefactory - I cant seem to download it either.
No I was trying for just the 1st paragraph, but, sorry mistakes do happen.
Sent from my HTC Wildfire using xda premium
Building CM9 from Sources for O2X
This Guide is a Step by Step Guide to Build CM9 from official CM9 Sources.
It based on:
aMpeX`s [TUTORIAL] The Step-By-Step guide to build Cyanogenmod7 for the LG Optimus 2X
loganmc10`s [GUIDE] Building CM9 for G2X
I only change to P990, respectively CM9 and add the fix for working Baseband
You need:
- a installed Linux, (I use Ubuntu 11.10, 64 Bit)
- a fast PC or Notebook is recommended
- a fast internet-connections is recommended, (you have to download several GBs)
There are 10 Steps, (8 for building, and 2 optionals ):
1. Installing Build-Packages
2. Install and setup Android-SDK
3. Update path
4. Create directories
5. Install repository and download CM9 Sources
6. Fix for non working camera
6a. Fix the known issues
7. Compiling Unofficial CM9 Build
8. Fix unknown Baseband
9. Extended building
10. Optional changes
Some infos before start:
- read the whole Guide carefully, (possibly you have to read it a few times, untill you understand all steps)
- if you do it exactly as explained, there should be no problems, and the result is a working Unofficial CM9-Build
- don`t login to Linux as root
- if you get problems, feel free to PM me, if you can`t post in Dev-Forum
lets start,
1. Installing Build-Packages
install this for 32 bit and 64 bit:
Terminal:
type:
Code:
sudo apt-get install git-core gnupg flex bison gperf libsdl1.2-dev libesd0-dev libwxgtk2.6-dev squashfs-tools build-essential zip curl libncurses5-dev zlib1g-dev openjdk-6-jdk pngcrush schedtool
NOTE:
this will install Open-JDK instead of Sun-JDK,
(Sun-JDK isn`t longer official available for Ubuntu)
this will result in an error message at the beginning of compiling,
just ignore it, compiling will working fine.
If you want to install Sun-JDK instead of Open-JDK,
the user tonyp has made a tutorial.
use this line instead of above one
Terminal:
type:
Code:
sudo apt-get install git-core gnupg flex bison gperf libsdl1.2-dev libesd0-dev libwxgtk2.6-dev squashfs-tools build-essential zip curl libncurses5-dev zlib1g-dev pngcrush schedtool
than go to this tutorial
for me the tutorial above doesn`t work (Ubuntu 11.10 64 Bit)
this is working for me:
open terminal:
Code:
sudo add-apt-repository ppa:ferramroberto/java
Code:
sudo apt-get update
Code:
sudo apt-get install sun-java6-jdk sun-java6-plugin
Code:
sudo update-alternatives --config java
(note: you have to press the tab button to be able to press ok, after the last command )
install this for 64 bit also:
Terminal:
type:
Code:
sudo apt-get install g++-multilib lib32z1-dev lib32ncurses5-dev lib32readline-gplv2-dev gcc-4.4-multilib g++-4.4-multilib
2. Install and setup Android-SDK
Download newest Android-SDK from here (Linux (i386) )
Extract the Zip-Package to a directory of your choice
Terminal:
navigate to the tools-folder of Android-SDK and type:
Code:
./android
this will launch the AVD-Manager
check repository, select newest repository, and click install packages
3. Update path
go to your Home-Directory, and press CTRL + H to show hidden files,
open .bashrc
and add this:
Code:
export PATH="/home/<yourusername>/<path to the android SDK >/platform-tools/:${PATH}"
export PATH="/home/<yourusername>/bin/:${PATH}"
now you have to log out and in again for the changes take effect.
now check if changes are working,
Terminal:
type:
Code:
adb devices
you should see something like this:
[email protected]:~$ adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
Click to expand...
Click to collapse
4. Create directories
Terminal:
type:
Code:
mkdir -p ~/bin
Code:
mkdir -p ~/android/system
5. Install repository and download CM9 Sources
Install repository
Terminal:
type:
Code:
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
Code:
chmod a+x ~/bin/repo
Code:
cd ~/android/system/
Code:
repo init -u git://github.com/CyanogenMod/android.git -b ics
enter name, email adress, and choose if you want colors or not
Download CM9 Sources:
Terminal:
type:
Code:
cd ~/android/system/
Code:
repo sync
depending on your internet connection speed this can take several hours
press CTRL + H
go to :
/android/system/.repo/
create:
local_manifest.xml
paste into local_manifest.xml:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="device/lge/p990" name="CyanogenMod/android_device_lge_p990" />
<project path="device/lge/star-common" name="CyanogenMod/android_device_lge_star-common" />
<project path="vendor/lge" name="Owain94/proprietary_vendor_lge.git" remote="github" />
</manifest>
Terminal:
type:
Code:
cd ~/android/system/
Code:
repo sync
6. Fix for non working camera
download this zip-package MediaFire SolidFiles.
(I don`t make this patch, and don`t know who had made it, if you made it PM me and I`ll give credit for your work)
Extract the Zip-Package to a directory of your choice.
Terminal:
type:
Code:
cd ~/android/system
Code:
patch -p1 <
NOTE: after "<" there has to be a "blank space" (press spacebar)
now drop the first ...diff file from extracted package into terminal, the path will be automatically added,
run the created command,
the same procedure for the other 4 files
6a. Fix the known issues
for broken building:
open:
device/lge/p990/BoardConfig.mk
delete line:
Code:
BOARD_TOUCH_RECOVERY := true
For mobile data fix:
place this file to android/system/system/core/init/ (overwrite excisting file),
7. Compiling Unofficial CM9 Build
Terminal:
type:
Code:
~/android/system/vendor/cm/get-prebuilts
Code:
cd ~/android/system/
Code:
. build/envsetup.sh
Code:
brunch p990
depending on your PC or Notebooks specs compiling will take from 30 minutes to several hours
you can find your Rom-Zip-Package at:
/android/system/out/target/product/p990/
Click to expand...
Click to collapse
8. Fix unknown Baseband
open your Rom-Zip-Package and extract /system/build.prop
(don`t close Archivmanager)
open build.prop:
delete line:
ro.modversion=9-...-UNOFFICIAL-p990
Click to expand...
Click to collapse
(thanks to owain94 for deleting line info)
find line:
ro.cm.version=9-...-UNOFFICIAL-p990
Click to expand...
Click to collapse
replace this line with:
ro.cm.version=9.0.0-RC1-p990-UNOFFICIAL
Click to expand...
Click to collapse
save build.prop
drop modded build.prop into Archivemanager (/system, overwrite existing file)
Now your Unofficial CM9 Build is ready to install
------------------------------------------------------------------------------------------------------------------------------------------------------------
9. Extended building:
I decided to make a optional 9. Step to have a better building experience
(all tipps by owain94, thanks)
This Step is a replacement for Step 7!
Terminal:
type:
Code:
cd ~/android/system && clear && cd vendor/cm && ./get-prebuilts && cd ../../ && clear && . build/envsetup.sh && brunch p990 2> warn.log
this command downloads the cm-prebuilds,
sets up the build environment,
start the building,
exports all warnings and errors to a text file
and cleans the Terminal.
open another Terminal
type:
Code:
cd ~/android/system && clear && tail -f warn.log
this command cleans the terminal,
shows the warnings and errors in this second Terminal,
and keep the focus on it,
first terminal only shows the building process,
so it`s much easier to catch problems while compiling.
If you have connected two screens to your PC or Notebook,
you can also place second Terminal on second screen.
you can find your Rom-Zip-Package also at:
/android/system/out/target/product/p990/
Click to expand...
Click to collapse
10. Optional changes:
Fix for working torch and torch power-widget:
"activate" torch and power-widget:
open:
/android/system/packages/apps/Torch/res/values/config.xml
add or change to:
Code:
<bool name="useCameraInterface">true</bool>
open:
/android/system/packages/apps/Settings/res/values
add or change to:
Code:
<bool name="has_led_flash">true</bool>
add Torch.apk to the package:
open:
/android/system/device/lge/star-common/star.mk
change:
Code:
## LGE stuffs
PRODUCT_PACKAGES += \
LGEServices \
bridgeutil \
libbridges \
libbridge \
libbridge_jni \
secureclockd \
libsecureclock \
screencap \
hwprops \
com.android.future.usb.accessory
to:
Code:
## LGE stuffs
PRODUCT_PACKAGES += \
LGEServices \
bridgeutil \
libbridges \
libbridge \
libbridge_jni \
secureclockd \
libsecureclock \
screencap \
hwprops \
com.android.future.usb.accessory \
Torch
Credits:
aMpeX, loganmc10, pastime1971, owain94, tonyp, temasek
The -j part isn't needed anymore the build script figure it out on their own
and for the vendor files you can ad this to the local manifest
<project name="koush/proprietary_vendor_lge.git" path="vendor/lge" remote="github" />
it is less work we don't want to do to much
also this is maybe a nice addition
Code:
clear && cd vendor/cm && ./get-prebuilts && cd ../../ && clear && . build/envsetup.sh && brunch p990 2> warn.log
i use this build line
clear - make my terminal nice and empty
cd vendor/cm && ./get-prebuilts && cd ../../ - get the cm prebuilts
clear - make the terminal clean again
. build/envsetup.sh - set up the build env
brunch p990 - lunch and bacon for the p990
2> warn.log - exports al the warnings and errors to a text file to keep the terminal clean
i have three screens attached to my pc
on one screen i run the above command (clear && cd vendor/cm && ./get-prebuilts && cd ../../ && clear && . build/envsetup.sh && brunch p990 2> warn.log)
on another screen i run this command (clear && tail -f warn.log) this will print (and keep track of) the warn.log file with all the errors and warnings
and on the other screen i do useless stuff hehe
anyway i really like to use 2 terminals it is just easier to catch problems
Nice tut mate!
Sent from my HTC One X using xda premium
reserved
great guide bro.
Edit:
If anyone wants to install the SUN JDK instead of Open JDK you can install it from the partner repository:
Code:
sudo add-apt-repository "deb http://archive.canonical.com/ lucid partner"
sudo apt-get update
sudo apt-get install sun-java6-jdk
Thanks, for your replies, I'll change my Guide at the evening.
Gesendet von meinem HTC One S mit Tapatalk 2
Great! Maybe I will stay building
Sent from LG 2X using Tapatalk 2 Elite
Thanks a lot !!
The Guide is updated, (big thanks to owain94).
I`ll add a new Step or Section (lets see, atm I don`t know) for extended Build-Line and possibly multiscreen using, I`ll test it while compiling for my One-S.
i am getting an error
make: *** No rule to make target `out/target/product/p990/obj/lib/libnvdispmgr_d.so', needed by `out/target/product/p990/obj/SHARED_LIBRARIES/libsurfaceflinger_intermediates/LINKED/libsurfaceflinger.so'. Stop.
plz help me..
thanks for the tutorial.
podanimesh said:
i am getting an error
make: *** No rule to make target `out/target/product/p990/obj/lib/libnvdispmgr_d.so', needed by `out/target/product/p990/obj/SHARED_LIBRARIES/libsurfaceflinger_intermediates/LINKED/libsurfaceflinger.so'. Stop.
plz help me..
Click to expand...
Click to collapse
did you sync the vendor files?
libnvdispmgr_d.so is a vendor file that cannot be build because we don't have the sources
you need to sync them from koush his github or extract the vendor files using the script in the device folder
good luck
owain94 said:
did you sync the vendor files?
libnvdispmgr_d.so is a vendor file that cannot be build because we don't have the sources
you need to sync them from koush his github or extract the vendor files using the script in the device folder
good luck
Click to expand...
Click to collapse
ok now compiled successfully..
ROM booted but no wi-fi and camera..
podanimesh said:
ok now compiled successfully..
ROM booted but no wi-fi and camera..
Click to expand...
Click to collapse
Wifi working fine for me, but I'll add a step for camera fix, thanks for reporting
Gesendet von meinem HTC VLE_U mit Tapatalk 2
If anyone wants to have SUN JDK instead of Open JDK it's still possible:
Code:
sudo add-apt-repository "deb http://archive.canonical.com/ lucid partner"
sudo apt-get update
sudo apt-get install sun-java6-jdk
I also put that in "my" post 3.
thanks for reporting, but as far as I know, sun has many security risks, isn`t it?
XXMrHyde said:
thanks for reporting, but as far as I know, sun has many security risks, isn`t it?
Click to expand...
Click to collapse
Hm I don't think so. As far as I know the reason why Open JDK is used in Ubuntu instead of Sun JDK is that Open JDK is fully open sourced while Sun JDK still uses some pre compiled closed source binaries. Some open source fanatics might call this a security risk as they can't check the source themselves, but apart from that their shouldn't be any risks.
Sent from my LG-P990 using xda app-developers app
this procedure did not make .zip file, but normal folder
tonyp said:
Hm I don't think so. As far as I know the reason why Open JDK is used in Ubuntu instead of Sun JDK is that Open JDK is fully open sourced while Sun JDK still uses some pre compiled closed source binaries. Some open source fanatics might call this a security risk as they can't check the source themselves, but apart from that their shouldn't be any risks.
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
Ok, nice to know, I`ll change the Guide, so users can decide, which JDK they want to install
tomsi91 said:
this procedure did not make .zip file, but normal folder
Click to expand...
Click to collapse
Then you make a mistake, if so, my Rom wouldn`t excist
Please upload camera fix tutorial....
Sorry, I was a little bit busy today, I`ll ad the camera fix to the guide now
added camera fix to the Guide
edit:
now it can be choosen if you want to install Sun- or Open-JDK
You will need to enable USB debugging on your phone through developer settings.
** I am not responsible for anything that happens to your device as a result of doing this, but I have tested this out for a week with no issues, so I thought to share it with you guys.
IMPORTANT NOTES:
Make sure to set your desired refresh rate (Settings > Display > Refresh rate) before running this script, as it will cause this menu to be greyed out afterwards. I set it to 120 Hz permanently.
This script disables the stock camera. I personally use GCam, but if you do need the stock camera app, just remove the line with 'com.asus.camera' before running the script.
Code:
# You must enter an ADB shell to run the below.
# Make sure your device is connected.
adb shell
# Speed up animations for a smoother experience.
settings put global window_animation_scale 0.7
settings put global transition_animation_scale 0.7
settings put global animator_duration_scale 0.7
# List the packages to remove for the default user.
debloat_list="\
com.android.apps.tag \
com.android.backupconfirm \
com.android.bips \
com.android.bluetoothmidiservice \
com.android.carrierconfig \
com.android.cts.ctsshim \
com.android.cts.priv.ctsshim \
com.android.dreams.basic \
com.android.dynsystem \
com.android.egg \
com.android.hotwordenrollment.okgoogle \
com.android.hotwordenrollment.xgoogle \
com.android.managedprovisioning \
com.android.printspooler \
com.android.statementservice \
com.android.wallpaper.livepicker \
com.android.wallpaperbackup \
com.asus.atd.deviceproperty \
com.asus.atd.smmitest \
com.asus.benchmarkblocker \
com.asus.calculator \
com.asus.camera \
com.asus.contacts \
com.asus.deskclock \
com.asus.dialer \
com.asus.ephotoburst \
com.asus.faceunlockservice \
com.asus.filemanager \
com.asus.focusapplistener \
com.asus.gallery \
com.asus.gamewidget \
com.asus.gamewidget.service \
com.asus.hardwarestub \
com.asus.hbm \
com.asus.ia.asusapp \
com.asus.imagesearch \
com.asus.ims.brightnessservice \
com.asus.ims.devicepolicymanager \
com.asus.ims.extdispctrl \
com.asus.ims.forcedark \
com.asus.ims.freeform \
com.asus.ims.packageinstallerproxy \
com.asus.ims.phykeyctrl \
com.asus.ims.pointerproxy \
com.asus.launcher.twinviewmode \
com.asus.livedemo \
com.asus.livedemoservice \
com.asus.livewallpaper.zf8livewallpaper \
com.asus.loguploader \
com.asus.loguploaderproxy \
com.asus.nextapp \
com.asus.nextappcore \
com.asus.openbeta2 \
com.asus.setupwizard \
com.asus.soundrecorder \
com.asus.sysdiagnostic \
com.asus.sysmonitor \
com.asus.twinapps \
com.asus.twinappsservice \
com.asus.weathertime \
com.dsi.ant.server \
com.facebook.appmanager \
com.facebook.appmanager \
com.facebook.katana \
com.facebook.orca \
com.facebook.services \
com.facebook.system \
com.futuredial.asusdatatransfer \
com.futuredial.asuslocalbackup \
com.google.android.apps.setupwizard.searchselector \
com.google.android.apps.walletnfcrel \
com.google.android.apps.wellbeing \
com.google.android.apps.youtube.music \
com.google.android.feedback \
com.google.android.googlequicksearchbox \
com.google.android.ims
com.google.android.marvin.talkback \
com.google.android.printservice.recommendation \
com.google.android.setupwizard \
com.google.android.tts \
com.google.android.youtube \
com.google.ar.core \
com.google.ar.lens \
com.instagram.android \
com.netflix.mediaclient \
com.netflix.partner.activation \
com.qti.dpmserviceapp \
com.qti.qualcomm.datastatusnotification \
com.qti.qualcomm.deviceinfo \
com.qti.service.colorservice \
com.qti.xdivert \
com.qualcomm.qti.devicestatisticsservice \
com.qualcomm.qti.dynamicddsservice \
com.qualcomm.qti.poweroffalarm \
com.qualcomm.qti.services.secureui \
com.qualcomm.qti.services.systemhelper \
com.qualcomm.qti.uimGbaApp \
com.qualcomm.qti.workloadclassifier \
se.dirac.acs \
"
# Go through each package and disable it.
#
# To re-enable all apps in the list:
# -- Replace "disable-user" with "enable"
# then run the below 'for' loop again.
#
# To re-enable only one app from the list:
# -- Run this command: pm enable <package_name>
#
for i in $debloat_list; do pm disable-user $i; done
?
Smrurbo said:
?
Click to expand...
Click to collapse
Any questions?
TikiThePug said:
Any questions?
Click to expand...
Click to collapse
and where is the file itself?
Smrurbo said:
and where is the file itself?
Click to expand...
Click to collapse
You don't need a file. It's through ADB. You just copy and paste those commands into command prompt.
For example:
com.asus.calculator \
com.asus.camera \
com.asus.contacts \
com.asus.deskclock \
com.asus.dialer \
Why is this Bloatware?
I think Bloatware are unnecessary Apps they show Ads etc.
PC295 said:
For example:
com.asus.calculator \
com.asus.camera \
com.asus.contacts \
com.asus.deskclock \
com.asus.dialer \
Why is this Bloatware?
I think Bloatware are unnecessary Apps they show Ads etc.
Click to expand...
Click to collapse
Exactly, maybe it depends on region but my Zenfone 8 in Poland came literately with maybe two unnecessary apps that could be deleted normally. Most of the unwanted google apps can be disabled.
There is not even one bloatware, adware, game nor social app on my phone I'd wouldn't like to have.
Do you get more apps in other regions???
If not I think this post is just dangerous as it disables/deletes default or system apps.
PC295 said:
For example:
com.asus.calculator \
com.asus.camera \
com.asus.contacts \
com.asus.deskclock \
com.asus.dialer \
Why is this Bloatware?
I think Bloatware are unnecessary Apps they show Ads etc.
Click to expand...
Click to collapse
These are unnecessary apps for me, which is why I removed them. I don't need these because I use the subjectively better alternatives provided by Google. If you want these apps, by all means keep them. Just delete these lines in the script before running it. Very simple.
Kemez said:
Exactly, maybe it depends on region but my Zenfone 8 in Poland came literately with maybe two unnecessary apps that could be deleted normally. Most of the unwanted google apps can be disabled.
There is not even one bloatware, adware, game nor social app on my phone I'd wouldn't like to have.
Do you get more apps in other regions???
If not I think this post is just dangerous as it disables/deletes default or system apps.
Click to expand...
Click to collapse
I spent a lot of my time testing things out myself before I posted this. If this script was dangerous, then I would not have shared it. As I stated in the OP, I ran this script on my own phone which is my daily driver, and I have not had any issues at all. On the contrary, I noticed slightly better battery life and less RAM usage.
So maybe be a little considerate of people who are openly trying to contribute to the community? If not, feel free to move along.
dont suppose you took an battery life measures before and after? Interested in anything that shaves some much needed hours off drain time cheers
majorwedgy said:
dont suppose you took an battery life measures before and after? Interested in anything that shaves some much needed hours off drain time cheers
Click to expand...
Click to collapse
Hey, thanks for your interest.
Unfortunately, I did not record exact numbers, but I noticed it took a little longer before I had to recharge the phone under normal use (maybe 1 hour?). Though this is with mixed usage, including leaving the phone idle.
Does Netflix still work?
HyperCriSiS said:
Does Netflix still work?
Click to expand...
Click to collapse
I'm not sure, as I don't use Netflix on my phone.
First - much, much thanks for your work with this list. It's absolutly awful how much Bloatware ASUS packs in it's firmwares.
One question - I didn't set refresh rate and now it seems to stuck at 60 and settings also greyed out (I didn't read carefully enough your instructions). Is there a way to reanable the option without doing a fresh install? When I reenable all the apps does the option come back?
T3chDelicious said:
First - much, much thanks for your work with this list. It's absolutly awful how much Bloatware ASUS packs in it's firmwares.
One question - I didn't set refresh rate and now it seems to stuck at 60 and settings also greyed out (I didn't read carefully enough your instructions). Is there a way to reanable the option without doing a fresh install? When I reenable all the apps does the option come back?
Click to expand...
Click to collapse
No problem!
Yes, the option will come back if you enable everything again.
Thanks for this quick answer!
Again, much thanks for this list. Helps a lot.
Anyone tried this with Android 12?