Related
SouthPaw Version 2.1 - Final Deodex
***Two Versions - Odex(to come soon) and Deodex***
Click to expand...
Click to collapse
Odex for pure speed, and Deodex for themes
Latest A2SD built right in. NO config needed -- Bloat removed for speed
Click to expand...
Click to collapse
No Longer a specific Cellular South based rom! Any carrier using a Hero can run this Rom!
Click to expand...
Click to collapse
{
"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"
}
Removed Apps:- AmazonMp3 - DiscoverCenter - Flickr - GoogleSkyMap - HTCFootprintsLayar - LearnMore - Movies - Stocks - Teeter - Textcs - Twitter - Various HTC Widgets (will have download links tonight)
Themes:
To use these you will need Metamorph.
Metamorph - Link to Market (go from phone browser) Metamorph
QRCode for Metamorph(use barcode scanner)
The Blue Echo
Made by Pappa Smurf, ported to our rom from Leadfoot
http://www.mediafire.com/?buacudiq2if9kti
Must install metamorph from market before using these themes.
NOT COMPATIBLE WITH ODEX VERSION!
"to apply. simply download then put on SD card in folder called AndroidThemes. then go to metamorph click "start checks" then "unzip new theme" click on "TheBlueEcho" zip file. then just do it like the other theme. it can go right over it no need to wipe or recover anything. thats the great thing bout metamorph just as always make sure you nand backup just in case." -leadfoot9281
Click to expand...
Click to collapse
Red Dawn Theme:
By Pappa Smurf, converted to our rom by Leadfoot:
http://www.mediafire.com/?tuc8xlwb61e98wm
after you metamorph this call sombody without a picture, if the little android guy is blue and you want him red metamorph this.
http://www.mediafire.com/?71tw4etfslasd96
for the market- NOT A METAMORPH FILE MUST BE PUSHED WITH ADB
**EDIT ... took market down til I can fix.
i would recommend doin a nand backup before pushing this. i pushed it 4 times to my phone. 3 of those times it worked fine. the one time it didnt work i have no idea why as i didnt do anything different.
to push this go to adb shell and type :
mount -o rm,remount -t yaffs2 /dev/block/mtdblock3 /system
now back put of shell and put the Vending.apk into the push folder. now you will type :
cd push
adb push HtcDialer.apk /system/app
....................now your done.
A majority of this theme is from papasmurfs RedDawn with a few tweaks of my own and some random icons i have ran across place to place. i cant take the credit for this other than i test each thing and make sure it functions and get it to work for a stock rom (like this one) and simply put it together.
BTW: no FC's for contacts or contact widgets on this one. thats what took so long lol.... only issue i know of is setting up speed dial. other than that, all of it works. been using it a few days now. If you run into anything let me know and i will see what i can come up with. - Leadfoot
Click to expand...
Click to collapse
Flipping Animations (Metamorph)
***If it messes up, you WILL bootloop. This MAY work with odex but not sure yet. BEST DO A NANDROID PRIOR TO USING THIS METAMORPH FILE!!!***
Download:
http://www.mediafire.com/?mn883l6v0i6nhaa
Click to expand...
Click to collapse
Alternative Weather Clock (Metamorph)
Download: http://www.mediafire.com/?3hajyxj1g9dpahe
***NOT A FLASHABLE ZIP!/NOT COMPATIBLE WITH ODEX ROM!!!***
Extract zip file to the AndroidThemes folder on your sdcard after installing metamorph, and use metamorph to apply it. It says to restart after applying, but no need to do so.
Click to expand...
Click to collapse
Black Haptic Dialer (Flashable Zip NOT a metamorph!)
http://www.mediafire.com/?2d1jewavnhytd9f
Click to expand...
Click to collapse
Where to download:
SouthPawV-2.1-Final
Deodex: http://www.mediafire.com/?n55a39vc4loetcl
MD5: 4892e91d8af0db765d74741be2db02cd
Bloat download: http://www.mediafire.com/?uo9oja1q7x6zb59
**Bloat download NOT flashable. Push via adb**
(SP-2.0 Final Links)
***Odex is FASTER than de-odex, but is NOT THEMABLE!***
http://www.mediafire.com/?jcl2i8mzlfw1glu
MD5 Sum:d2569d8b937266b2873251bfa556c6e2 SouthPawV2-Final-Odex.zip
***DeOdex is not quite as fast but still mighty fast, lightweight and best of all.. THEMEABLE!!!***
http://www.mediafire.com/?004a3qv0xw0jjat
MD5 Sum:6abe77ca31494cb314c8076117925e81 SouthPawV2-Deodex.zip
Click to expand...
Click to collapse
For Colin_ph users!
The bf/adnan kernels can't be used with the regular version of collin_ph battery mod. You have to use the edited version below and change your governer to the settings shown below.
http://github.com/Decad3nce/battery-...5d1156014134c2
"Recommended Settings for Tweak:
For BFS Kernel:
CPU Governor: Ondemand
I/O Scheduler: deadline/cfq
For CFS Kernel:
CPU Governor: Interactive
I/O Scheduler: deadline/noop"
To change the governor, look into the 2nd post for instructions.
Click to expand...
Click to collapse
For the future: For later updates you can find it all here in the SouthPaw folder:
http://www.mediafire.com/?ye6pbkdgps4b5
This is where the flashable add ons will be soon as well.
***Updaters***
Do not update over previous rom! Backup/Nandroid, and then wipe and flash!
***Thanks N Applause***
leadfoot - thank you for porting that theme!
dsixda - Without your kitchen this wouldn't be possible. F*ing clean software man.
Darchstar - For the Kernel. Awesome man awesome!
Collin_ph - Any extra battery life is great!
JsChiSurf - Love your dialer. Sry I didn't ask before adding it to this rom but didn't figure it would be a big deal.
MrDanger - Your rom is lookin' good. And thanks for helping my users out here and there too.
KyleIsTheBeast - For my first rom ever flashed. Bittersweet was good while it lasted and hope to see you dev'ing in the future.[/SIZE]
Reserved for the Red Corner!
***Issues found!***
none yet.
***How to check the MD5 Hash***
Windows (and mac) users:
1. download Hashtag, a free md5 file hash check utility from here: http://beeblebrox.org/hashtab/
2. After downloading and installing, just right click on any file. On Windows, select properties and you will see a new "File Hashes" tab. On Mac select "File Hashes" (on 10.5 the "File Hashes" menu item will be found under the "More" submenu). This is will start HashTab providing more or less the same view that you see on Windows. This File Hashes window displays all the hashes for the file.
3. Check the hash to make sure it's the same big jumble of numbers and letters as the hash above. If it is not the same, the download is bad and you should redownload the file.
Linux users:
1. go into your linux terminal or shell (not the adb shell)
2. navigate to the folder that contains the rom (mine is in downloads, so you would type 'cd Downloads')
3. for my rom, type 'md5sum SouthPawV1.5Final.zip
4. the output should look as shown:
Code:
OUTPUT_ZIP$ md5sum SouthPawV1.5Final.zip
F0D9E1F279FA7B0FA8636616499CD0C8 SouthPawV2.0-Beta.zip
[email protected]:~/Desktop/kitchen/OUTPUT_ZIP$
Installation:
***for newbies, see the second post under "How to root/maximizing my rom experience"***
1. Nandroid
2. Wipe
3. Flash
4. After install see configuring a2sd for more memory on the phone and JIT/Swap configuration in 2nd post! (and possibly a faster phone if you have a class 4 or higher memory card)
Bloated apps can be re-downloaded here: http://www.mediafire.com/?7ektxbiq0h65ftr
***Radio***
Also removed the Radio.img file. If you want the file you can download it here:http://www.mediafire.com/file/u2z11ar9ga6qn3a/CSouth_Radio_Signed.zip
MD5 Hash: 9157b63be585abef5812f71691cc4899
*You do not need to be flashing this file if it's already updated because that is the one file that CAN brick your phone if it's corrupted. ALSO if you ARE downloading this file, CHECK THE MD5 hash! Instructions above. It could mean the difference between a happy updated phone and a BRICKED phone.*
***How to root and Maximizing your rom experiance***
I hold no responsibility for any actions resulting from these links and/or this post.
How to root your CS Hero. Read first post, it describes everything
http://forum.xda-developers.com/showthread.php?t=581869
***How to flash any rom***
After rooting your phone to install any rom (not just mine)
1. backup everything if you have not already done so, you will lose EVERYTHING on the phone itself, (except for everything on the memory card)
1a. download my rom or another rom (as long as it's for your phone and radio)
1b. place the rom in the root directory (or the main directory rather) of your sdcard.
2. Turn the phone off
3. While holding the home button, press the power button until you see the recovery mode menu. (I am using clockwork mod 2.5.0.1 so depending on your recovery YMMV. You should use the instructions for your specific recovery system. They are using Darch's version of AmonRA's recovery, This is covered in the first post on that link as well.)
If you are using Clockwork Mod, you can use these instructions:
4. go to wipe data/factory reset and go to yes to start the wipe.
5. scroll down to wipe cache partition, and confirm
6. scroll down to advanced and wipe dalvik cache.
7. After that, scroll down to "install zip from sdcard"
8. select choose zip from sdcard
9. select the rom file from the memory card (mine will be SouthPAW!1.5-Final) and confirm to flash it.
10. Once the flash is done, reboot the phone. It's going to take between 5 and 10 minutes to boot the first time so be patient, and don't mess with it. After you get in you are golden, and nothing else is to be done. You have made it..
***how to maximize your battery performance***
This rom comes with an overclocked kernel that automatically sets itself to maximize battery life. But there are things you can set to make the kernel do what you want
***Kernel parameters***
You don't have to use any overclocking software to set the speed of the processor with this kernel Here is the parameters:
Syntax: echo "(speed in hz)" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
Example:
echo "768000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
Click to expand...
Click to collapse
Sets the cpu to max out at 768mhz
echo "710000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
Click to expand...
Click to collapse
Sets the cpu to max out at 710mhz
Also...
If your gps quit working for some reason do this:
mount -t debugfs none /sys/kernel/debug
echo "NORMALIZED_SLEEPER" > /sys/kernel/debug/sched_features
echo "NEW_FAIR_SLEEPERS" > /sys/kernel/debug/sched_features
Click to expand...
Click to collapse
To change the cpu governors for this kernel (the built in ones) here is how:
Type this to find the available governors:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors
Click to expand...
Click to collapse
The ones available are:
conservative
ondemand
userspace
powersave
performance
interactive
And then to change the governor, you type this:
echo "nameofgovernor" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
Click to expand...
Click to collapse
I haven't found full explanation on ALL the governors, but I guess it's a no brainer, however here is the info I pulled off of the kernel thread:
(For Interactive governor)
This governor is designed for latency sensitive workloads, UI interaction for
example.
Advantages:
+ significantly more responsive to ramp cpu up when required (UI interaction)
+ more consistent ramping, existing governors do their cpu load sampling in a
workqueue context, the 'interactive' governor does this in a timer context, which
gives more consistent cpu load sampling.
+ higher priority for cpu frequency increase, rt_workqueue is used for scaling
up, giving the remaining tasks the cpu performance benefit, unlike existing
governors which schedule rampup work to occur after your performance starved
tasks have completed.
Existing governors sample cpu load at a particular rate, typically
every X ms. Which can lead to under powering UI threads when the user has
interacted with an idle system until the next sample period happns.
The 'interactive' governor has a different approach. Instead of sampling the cpu
at a specified rate, the governor will scale the cpu frequency up when coming
out of idle. When the cpu comes out of idle, a timer is configured to fire
within 1-2 ticks. If the cpu is 100% busy from exiting idle to when the timer
fires then we assume the cpu is underpowered and ramp to MAX speed.
If the cpu was not 100% busy, then the governor evaluates the cpu load over the
last 'min_sample_rate' (default 50000 uS) to determine the cpu speed to ramp down
to.
There is only one tuneable for this governor:
/sys/devices/system/cpu/cpufreq/interactive/min_sample_rate:
The minimum ammount of time to spend at the current frequency before
ramping down. This is to ensure that the governor has seen enough
historic cpu load data to determine the appropriate workload.
Default is 5000 uS.
Click to expand...
Click to collapse
One last thing is that this kernel keeps logs. Even though they are hard to read if you want to see them, type this:
adb remount
adb pull /proc/last_kmsg last_kmesg.txt
Click to expand...
Click to collapse
***how to partition for apps2sd for Amon Ra's Recovery and Cyanogen's Clockwork Mod Recovery***
Instruction Source: http://www.villainrom.co.uk/wiki/index.php?title=Apps2SD#Normal_Installation
How to Setup SD card partitions from AmonRa's Recovery:
1. backup your stuff on your memory card. It is very possible that this will erase everything on your memory card.
2. Shut down the phone
3. Press and hold the home button while pressing the power button. Keep holding the home button until you get to the recovery menu.
4. Select Partition sdcard
5. Select Partition SD
6. Set the following partition sizes using the trackball or volume buttons:
-ext: 512MB - recommended. You will feel like you can install everything from the market.
-swap: none -not a prerequisite but recommended. use at least 30mb.
-fat: remaining
7. Reboot the phone. It may take a little while for boot to finish on this boot only.
How to Setup SD card partitions from Clockworkmod Recovery:
***Do not partition with Clockwork mod. There are some issues that I have read that will mess up your install***
There are alternative methods for this, but it's just easier to use Amon_Ra's image for this.
***How to setup a2sd/Swap/JIT***
A2SD is already enabled by default on this rom. However Swap and dalvik to sd is not!
To get swap working (if you made a swap partition on your sd card)
1. get to adb
2. adb remount
3. adb shell
4. a2sd reswap
To move Dalvik cache to sd -
5. a2sd cachesd
VOILA! 149MB free on the phone! *w00t*
Also there is more config you could do here. You can enable JIT *dunno if it works, so add at your own risk*
***More info for a2sd configuration***
Code:
Standard Apps2SD Commands:
--------------------------------------------------
reinstall
Moves free and paid apps to the ext2/ext3/ext4 partition on your secure digital card. Removes the No A2SD flag file.
This is used if you have already executed an a2sd remove command. Otherwise, this part is automatically performed when Apps2SD is started.
File removed: /data/.noa2sd
remove
Moves free and paid apps to the internal phone storage. Creates the No A2SD flag file.
File created: /data/.noa2sd
Swap Partition Commands:
--------------------------------------------------
reswap
Removes the No Swap flag. Allows A2SD to activate the swap partition.
This is used if you have already executed an a2sd noswap command. Otherwise, this part is automatically performed when Apps2SD is started. Note: This command has no effect on roms where the swap space is not built into the kernel.
File removed: /data/.noswap
noswap
Creates the No Swap flag. Prevents A2SD from activating the swap partition. Note: This command has no effect on roms where the swap space is not built into the kernel.
File created: /data/.noswap
swappyxx
Sets the swappiness setting for the swap file. xx sets the swappiness percentage used. (i.e. to set swappiness to 30%, type a2sd swappy30.
Dalvik Cache Commands:
--------------------------------------------------
cachesd
Moves Dalvik cache files to the ext2/ext3/ext4 partition on your secure digital card. Creates Dalvik Cache to SD flag.
Caution: If your phone fails to mount the ext2/ext3/ext4 partition and your dalvik-cache is pointed to the SD card, you will likely end up in a boot loop. Execute a2sd nocache from adb shell to rectify the issue.
File created: /data/.dalvikcacahe
File removed: /data/.dcpartition
cachesdreset
Same as cachesd above, but erases the contents of the dalvik-cache after move. This performs both the a2sd cachesd and a2sd resetcache all in one command.
File removed: /data/.dcpartition
cachepart
Moves Dalvik cache files to the /cache partition in your phone. Creates Dalvik Cache to Cache Partition flag.
Caution: Some phones do not have enough space to put the dalvik-cache on the cache partition. Also, some roms that have SenseUI installed may not work well with the dalvik-cache on the cache partition (although this issue appears to be fixed starting with Darktremor 2.7.5.1). If you experience issues such as force closes, try moving the dalvik-cache to the SD card (a2sd cachesd) or internal storage (a2sd nocache) instead.
File created: /data/.dcpartition
File removed: /data/.dalvikcache
cachepartreset
Same as cachepart above, but erases the contents of the dalvik-cache after move. This performs both the a2sd cachepart and a2sd resetcache all in one command.
File removed: /data/.dalvikcache
nocache
Moves Dalvik cache files to the internal phone storage. Removes all Dalvik Cache flags.
File removed: /data/.dcpartition, /data/.dalvikcache
nocachereset
Same as nocache above, but erases the contents of the dalvik-cache after move. This performs both the a2sd nocache and a2sd resetcache all in one command.
File removed: /data/.dcpartition. /data/.dalvikcache
resetcache
Clears the dalvik cache and restarts phone.
Apps2SD Diagnostic Commands:
--------------------------------------------------
check
Performs a symlink and flag file check on your setup. Outputs a report that shows you if
there are issues with your Apps2SD setup.
repair
Performs a repair of all symlinks based on flag file activation.
diskspace
Shows disk space statistics for the ext partition.
sysinfo
Displays information about your phone, partitions, swap, and more.
Also writes a dump file that has an entire profile of your phone. This is for troubleshooting only.
File Created: /data/dtsysdump.txt
swapspace
Shows swap space statistics for all swap space active on the phone. Note: This command has no effect on roms where the swap space is not built into the kernel.
ZipAlign Commands:
--------------------------------------------------
align
Performs a one-time zipalign on all APK files in /data/app and /data/app-private.
zipalign
Allows ZipAlign to execute during the boot process. Creates the ZipAlign flag file.
File Created: /data/.zipalign
nozipalign
Prevents ZipAlign from executing during the boot process. Removes the ZipAlign flag file.
File Removed: /data/.zipalign
Dalvik Setting Commands:
--------------------------------------------------
jit
Installs DalvikVM JIT.
WARNING: Do not run this command if your phone has NAND protection active.
nojit
Removes DalvikVM JIT.
WARNING: Do not run this command if your phone has NAND protection active.
defaultheap
Resets the Dalvik heap size to the default heap size.
File Removed: /data/.smallheap, /data/.largeheap, /data/.jumboheap
heapsizexx
Sets the dalvik heap size to xx. For example, to set the dalvik cache to 24mb, type a2sd heapsize24. To reset back to default, type a2sd heapsize0 (that's a zero, not the letter "o")
Low Memory Killer Commands:
----------------------------------------------------
lowmem-moderate
Sets the internal memory killer to the following settings:
Code:
Foreground Apps: 1536 pages / 6 MB
Visible Apps: 3072 pages / 12 MB
Secondary Server: 4096 pages / 16 MB
Hidden Apps: 7680 pages / 30 MB
Content Provider: 8960 pages / 35 MB
Empty App: 10240 pages / 40 MB
Create File: /data/.lmmoderate
Remove File: /data/.lmoptimum, /data/.lmstrict, /data/.lmaggressive, /data/.lmultimate, /data/.lmextreme
lowmem-optimum
Sets the internal memory killer to the following settings:
Code:
Foreground Apps: 1536 pages / 6 MB
Visible Apps: 2048 pages / 8 MB
Secondary Server: 4096 pages / 16 MB
Hidden Apps: 10240 pages / 40 MB
Content Provider: 12800 pages / 50 MB
Empty App: 15360 pages / 60 MB
Create File: /data/.lmoptimum
Remove File: /data/.lmmoderate, /data/.lmstrict, /data/.lmaggressive, /data/.lmultimate, /data/.lmextreme
lowmem-strict
Sets the internal memory killer to the following settings:
Code:
Foreground Apps: 1536 pages / 6 MB
Visible Apps: 2048 pages / 8 MB
Secondary Server: 4096 pages / 16 MB
Hidden Apps: 15360 pages / 60 MB
Content Provider: 17920 pages / 70 MB
Empty App: 20480 pages / 80 MB
Create File: /data/.lmstrict
Remove File: /data/.lmmoderate, /data/.lmoptimum, /data/.lmaggressive, /data/.lmultimate, /data/.lmextreme
lowmem-aggressive
Sets the internal memory killer to the following settings:
Code:
Foreground Apps: 1536 pages / 6 MB
Visible Apps: 3072 pages / 12 MB
Secondary Server: 4096 pages / 16 MB
Hidden Apps: 21000 pages / 82 MB
Content Provider: 23000 pages / 90 MB
Empty App: 25000 pages / 98 MB
Create File: /data/.lmaggressive
Remove File: /data/.lmmoderate, /data/.lmoptimum, /data/.lmstrict, /data/.lmextreme, /data/.lmultimate
lowmem-extreme
Sets the internal memory killer to the following settings:
Code:
Foreground Apps: 1536 pages / 6 MB
Visible Apps: 3072 pages / 12 MB
Secondary Server: 4096 pages / 16 MB
Hidden Apps: 38400 pages / 150 MB
Content Provider: 40960 pages / 160 MB
Empty App: 43520 pages / 170 MB
Create File: /data/.lmextreme
Remove File: /data/.lmmoderate, /data/.lmoptimum, /data/.lmstrict, /data/.lmaggressive, /data/.lmultimate
lowmem-ultimate
Sets the internal memory killer to the following settings:
Code:
Foreground Apps: 1536 pages / 6 MB
Visible Apps: 3072 pages / 12 MB
Secondary Server: 4096 pages / 16 MB
Hidden Apps: 51200 pages / 200 MB
Content Provider: 57600 pages / 225 MB
Empty App: 64000 pages / 250 MB
Create File: /data/.lmultimate
Remove File: /data/.lmmoderate, /data/.lmoptimum, /data/.lmstrict, /data/.lmaggressive, /data/.lmextreme
lowmem-default
Sets the internal memory killer back to phone default settings.
Remove File: /data/.lmmoderate, /data/.lmoptimum, /data/.lmstrict, /data/.lmaggressive, /data/.lmextreme, /data/.lmultimate
***How to push an apk file using adb***
*Of course you have to have a rooted phone to do this, if not check the ***how to root*** section first before getting this far.*
This tutorial is going to use the linked deleted files zip from the link in the first post.
1. Download the Android SDK for your appropriate Operating System from here: http://developer.android.com/sdk/index.html
2. Once downloaded, be sure to download the deleted files zip from the link in the first post.
3. Extract the Android SDK file to an easily findable folder
4. Extract the deleted files from the zip file, and copy the apk file you choose to the AndroidSdk\tools folder. For reference I will be using the Dialer.apk file in this tutorial (not included in the zip).
5. connect phone to computer and select "charge only" from the menu.
(*for windows Vista/7/XP*)
*prerequisite* - you must have the adb drivers installed to do this in windows.
6. Click Start, go to > All Programs > Accessories, and from there, right click 'command' (something like that), and click 'open as administrator' (XP users do not have to do this, just go to Start > Run, type cmd, and press enter)
7 .navigate to the android tools folder you put the apk file in (the command to change directories is 'cd' and then a space, and the name of the next folder, so to navigate to the 'android' folder, you would type 'cd android', and then you can use 'dir' to see the next directories till you get to the right folder.
8. type 'adb remount'. This is going to start the adb system, and then remount the phone in root mode.
9. to check to see if your phone is mounted and everything is kosher, type 'adb devices' and it should show something on the bottom that should be your device or serial of the device. If it says ??????????? then it's not working.
10. type 'adb push HtcDialer.apk /system/app'
11. DRINK A BEER! You have pushed an apk to your phone! To check if it is installed, simply click the call button (or press phone on the rosie), go to settings and select speed dial. Then see if you can change/add a number to speed dial #2. This could possibly require a reboot to actually start the new version of the installed software but you should just be able to go ahead and use it
(*for Linux*)
6. Once you extract the android-sdk-linux_x86 folder, go to the terminal, and navigate to the android folder pretty much the same way as windows, except instead of using dir (ubuntu users can use it), use 'ls'
7. type 'sudo ./adb remount' and when asked, type the administrator password for the linux system. This is going to start the adb system, and then remount the phone in root mode.
8. To check to see if your phone is mounted, type 'sudo ./adb devices' this should show your device.
9. To do that actual push, type 'sudo ./adb push HtcDialer.apk /system/app'
10.
DRINK A BEER! You have pushed an apk to your phone! To check if it is installed, simply click the call button (or press phone on the rosie), go to settings and select speed dial. Then see if you can change/add a number to speed dial #2. This could possibly require a reboot to actually start the new version of the installed software but you should just be able to go ahead and use it
***History***
(July 21st)v.0.1 - Dirteh_South-Krome_Knuggz #First Cellular South+Root 2.1 hero rom to hit XDA! Featured Full Stock 2.1 + root, tethering, and apps2SD. --issues-- had to remove various apps because of signing issues.
Download Link:http://www.mediafire.com/?15k8u28gy9f3vka
----------------------------------------------------------------------------------
(July 25)v.0.5 - Dirteh_South-Kleen_Thugz #Removed useless apps, added Live Wallpapers. --issues-- facebook update issue
Download Link:http://www.mediafire.com/?xx0d54pnj99tuyn
----------------------------------------------------------------------------------
(July 27)v.0.6 - Dirteh_South-Fast_Dubz! #Added vUV'd 710mhz overclocked kernel, added Home Switcher, Helix Launcher, and a few small programs.
Download Link:http://www.mediafire.com/?9ithfl65laxpf0y
----------------------------------------------------------------------------------
(August 6)v.1-Beta - South Paw!V1-Beta #Went back to scratch RUU file, Name changed to hide the guilty, completely overhauled, removed useless apps, facebook was fixed, updated A2SD, overclocked/undervolted kernel, google maps, signing issues fixed, added google parts, Old skool 1.5 hero bootscreen, added custom lockcreen *by me* and background, Dconfig, Collin_ph Battery Tweak, Fixed the black dialer w/o haptic feedback.
Download Link:http://www.mediafire.com/?ipf0oonwn9zq2y1
---------------------------------------------------------------------------------
(August 12)v.1.5-Final - SouthPaw!V1.5-Final #Downgraded to previous version of Apps2SD, and previous version of Root Permissions app, modified vUV2 - boot.img file to work properly with a2sd, removed android terminal because there was no way to fix it from fc'ing if you installed from rom flash, removed Dconfig because it was not compatible with this a2sd setup, added xda-developers app, updated facebook to newest version, updated collin_ph battery tweak to newest version.
Download Link:http://www.mediafire.com/?7ro6qczcoqcxtip
---------------------------------------------------------------------------------
(October 1 - October 28th)v.2.0-Betas
beta1 - had slowdown issues due to an unstable kernel added/various things missing
beta2 - still bad slowdown- other various things missing/not working
beta3 - Once more bad slowdown/added internal tweaks for speed but didnt work
beta4 - Fixed slowdown, has internal tweaks for stable brainfuct kernel #6, added misc. backgrounds
---------------------------------------------------------------------------------
(October 27)V.2.0-Final
Removed a bunch of stuff. First ever odex version added alongside the deodex version. No added extras at all besides root, busybox, a2sd, and wireless tethering. No longer a carrier specific rom.
---------------------------------------------------------------------------------
(October 28th)V2.1-Final(ish)
Based on newest update from cellular south. Vanilla with no extras just like 2.0 Final. Removed bloat. No kitchen signed apps AT ALL for smooth working with upgrading apps
Click to expand...
Click to collapse
Hell yeah! Although the neighbors didn't appreciate me running around in the front yard naked! Hmmm.... Maybe I will try the backyard next time.
Good job. I'm glad somebody finally got a CSouth Rom on here.
If you need any assistance let me know.
Ok I go to filedropper site but all I get to download is an empty folder, 66.7kb????. Has the file name but no data, or am I completely missing the right link? Do I need to join to download? Thanks, would really like to try this ROM out.
I got the download, followed all steps, it says that the zip is bad. I deleted the old one, transferred a fresh one to card, same story. I'm downloading the zip again just to make sure it didn't corrupt while downloading.
Anyone else run into this problem?
zip flashed fine for me. Just booting up
Can this be used in other non-sprint heros?
Also, I was wondering if it is possible to have like a stripped / universal version for non-sprint heros and then install CS’s or other carrier’s stuff apart like DarchDroid did with his naked rom with Google ****s apart.
Thanks for sharing it!
I downloaded it from the link with no problem. I did the following:
1.downloaded the zip
2.transferred it to the SD Card
3.HBoot
4.Created Nandroid
5. Wiped everything
6. flashed in zip file
It works pretty good. I can't get my yahoo account to work. I also can't get the new widgets to download to the phone and work. They download and then I don't get them. Hmmmm....
Anybody know how to change pri version? Mine is 1. Something but my non rooted phone is 2.51_013
Even though I am on AT&T with a Magic and Captivate it is good to see some Cell South love around here. I will be using your rom to flash to as many friend's Heroes I know.
Bring on the Incredible, Milestone, and Galaxy S now C South!
Kaisum said:
I got the download, followed all steps, it says that the zip is bad. I deleted the old one, transferred a fresh one to card, same story. I'm downloading the zip again just to make sure it didn't corrupt while downloading.
Anyone else run into this problem?
Click to expand...
Click to collapse
yeah i got the same problem
Redfox85 said:
Anybody know how to change pri version? Mine is 1. Something but my non rooted phone is 2.51_013
Click to expand...
Click to collapse
That is odd. I have no idea tbh, but I'll try to check it out.
From here on out, any questions asked will be answered in the 2nd post on this thread.
***link is fixed!! Any issues please report!***
And yes this rom should work for non-cs users, but always take caution and do like you do with sprint roms, and it should be ok (and for those who didn't get voicemail notifications, this should support it)
hexskrew said:
That is odd. I have no idea tbh, but I'll try to check it out.
From here on out, any questions asked will be answered in the 2nd post on this thread.
***link is fixed!! Any issues please report!***
And yes this rom should work for non-cs users, but always take caution and do like you do with sprint roms, and it should be ok (and for those who didn't get voicemail notifications, this should support it)
Click to expand...
Click to collapse
somethings up with the link again i got an error saying the the files is no longer there
Just want to say thanks, working well here!
Sent from my HERO200 using XDA App
Agpilot! said:
Just want to say thanks, working well here!
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
could you send me the file there appears to be a problem with the link
To Mr. Danger, yes I will need some help soon. I want to branch this rom out to a couple of different versions. 1. With no apps (well junk apps anyways) with helix launcher and no sense, 2. With no junk apps with sense, and 3. Just the full montey (like now but with no issues)
@pound24. I just tried the link. It's working fine (from mediafire, not the old link, I removed that one)
hexskrew said:
To Mr. Danger, yes I will need some help soon. I want to branch this rom out to a couple of different versions. 1. With no apps (well junk apps anyways) with helix launcher and no sense, 2. With no junk apps with sense, and 3. Just the full montey (like now but with no issues)
@pound24. I just tried the link. It's working fine (from mediafire, not the old link, I removed that one)
Click to expand...
Click to collapse
i used a different computer and it worked about to flash in a sec
This may be a dumb question, but you do need to root before applying this ROM, right?
Yes, the phone has to be rooted before loading anything except for the stock updates from the carriers.
[STOPPED][ROM ICS 15 Jul] slim rom for Desire [based on Sandvold .15 & K900 build 40]
These are a simple slim version of the original ICS ported rom for htc desire (aka bravo) provided by Sandvold and K900
Of course all credits must go to Sandvold & K900, I'm not a developer, simply I needed a lighter rom and due to many requests I decided to share my (small) work and dedicate to it a thread
They work just as original rom, I haven't changed a single bit, just removed all stuffs that can be downloaded later from google play (aka PhoneSky.apk). This thread is intended for "advanced users" but none can't stop you to make experiments
These rom are intended to work with cm7r2 hboot table & without the need of any ext3-4 partition (this means max 120-130 app)
IMPORTANT: as a2sd script we use as default for both roms 69a2sd script, more info here
CHANGELOG (15 Jul) :
- updated 98mydesireI script (modded minfree memory management)
- updated default Apex Launcher (anyway you can use whatever you prefer)
- updated OS fonts, I choose a ligther & smoother one
- Download here or Mirror here
CHANGELOG (06 Jul) :
- updated 98mydesireI script (reduced boot pause, it will stay only upon a fresh installation)
- updated MultiLing keyboard
- updated Music apk with JB release (moved backup to /system)
- moved LauncherApex from /system to /data (make an apex setting/icon backup before flash, you have to replace widget too)
CHANGELOG (04 Jul) :
- upgraded Sandolvd based ics rom (.15)
Some notes before starting:
before start I strongly suggest, if you are under MS Windows environment, to download the mini-sdk-android-windows.zip (look at 2nd post for details) from repository (aka known as diaduit), unzip the entire folder, without renaming it, where you prefer under your C: drive, this little zip contains some utilities and batch scripts to automate some recurrent actions useful to easily manage your device, such as for example radio flash, hboot flash, script injection, etc...
these slim rom will fit on cm7r2 partition table, if you don't know what is it you can start from alpharev.nl website, or simply download your .img copy from repository
I strongly suggest to use a modern and full functionally recovery, personally I use 4EXT: download from repository and flash trough _flash_recovery.bat batch script (from mini-sdk-android-windows.zip)
always in repository you can find a copy of the slim rom (named as rom-slim-etc...zip)
editing directly rom-slim-desireics-xyz_x.y.zip requires winrar (search in google)
this rom can work without any ext3-4 additional partition, I just move into sd-card ALL the games and not fundamental apps using default android behavior: Settings => Applications => Sd-card (tap correspondent app to move)
as a2sd script we use as default for both roms 69a2sd script, more info here
and now rom modded content:
removed all google applications (*) downloadable from google-play except QuickSearch and Vending (google-play app)
removed all tts lang (except for the service), they can be downloaded later from google-play because I suppose that own language should be enough for most of us
removed almost all sounds except one for alarm, one for ring and six for notifications, anyway you can create your own sounds repository in your sd-card, so you wont loose them never more: make a folder in your sd-card named /media/audio, then create under audio other 3 folders named: alarms, notifications, ringtones , then put your personal sounds under correspondent folders
removed default ics keyboard, the 1st reason because it's heavy and fat, the 2nd because has ton of languages when we really need just one... our own (I included as default MultiLing free keyboard, a light and highly configurable keyboard with downloadable single dictionary)
removed all customization and stock kernel is provided (eventually Tiamat kernel can be flashed separately), of course customization are included with best options/balance about my experience/opinion
default launcher is Apex Launcher
added 98mydesireI script (present under extra folder of mini-sdk-android-windows.zip), you can edit it as you prefer (use for this purpose pspad editor due to its ability to manipulate unix txt files), as default its primary goal is to manage cpu freq between sleep and awake states (245-245 when sleep, 960-1075when awake)
auto-adjust swap tuning (swappiness= 20 if zRam enabled, 0 if not)
installation instructions, starting from the beginning:
make a full backup before start, personally I don't use titanium due to its restoring issues probabilities, I prefer a full backup from recovery, for this purpose 4EXT is just perfect (from repository), it will backup eventually your ext3-4 partition too
download and copy rom-slim-desireics-xyz_x.y.zip file in your sd-card
if you don't have cm7r2 hboot you should upgrade to cm7r2, download the .img file from repository and use _flash_hboot.bat batch script (from mini-sdk-android-windows.zip) to easily flash the new hboot
reboot your device into recovery, pay attention that if you changed hboot table, for example from data+ to cm7r2, you have to force a full wipe (do it from recovery itself)
after rom flash & upon complete boot SetupWizard wont start (I removed it) so as 1st step I suggest you to configure a working wlan, then launch google-play and start registering your existing account...
download & configure all apps you intend to use (hint: search google inc to find all google stuffs such as maps, gmail, youtube, etc...)
post installation guide, another important step:
if you come from an upgrade/reflash remember that installer will format only /system folder, some previous related system app will still be under /data/app such as for example LatinIME.apk, so if you keep MultiLing keyboard (or whatever) remove from /app/data the LatinIME.apk (edit and use _remove batch script)
go under Settings => Evervol Toolbox => Performance => Memory management and activate "kernel samepage merging" (do not activate zRam, our device has enough ram and also because I noticed random FC under heavy usage)
as you know some video from gallery (using internal libs) are rendered badly, install instead MXPlayer (from google-play) and force it to use SW rendering (from MXPlayer settings)
removed almost all sounds except one for alarm, one for ring and six for notifications, anyway you can create your own sounds repository in your sd-card, so you wont loose them never more: make a folder in your sd-card named /media/audio, then create under audio other 3 folders named: alarms, notifications, ringtones , then put your personal sounds under correspondent folders
added 98mydesireI script, you can edit it as you prefer (use for this purpose pspad editor), as default its primary goal is to manage cpu freq between sleep and awake states (245-245 when sleep, 960-1075 when awake)
Other tips (I'll add step by step as I remember):
prevent unnecessary battery drainage by disabling auto-time update... device keeps date/time sync with connected cell tower every minute! (disable from Settings => Date & Time) and install instead ClockSync from google-play (setup auto-update every 3 days)
move ALL games or spare used app from nand to sd-card (Settings => Application => SD-card => tap on move able app)
to speed-up open/close phase disable animation from Settings => Developer options => Scale from 1x to 0,5x (or none)
(*) App list installed as default on /system:
Code:
ApplicationsProvider.apk
BackupRestoreConfirmation.apk
Bluetooth.apk
Browser.apk
Calendar.apk
CalendarProvider.apk
Camera.apk
CertInstaller.apk
Contacts.apk
ContactsProvider.apk
DefaultContainerService.apk
DeskClock.apk
DownloadProvider.apk
DownloadProviderUi.apk
DrmProvider.apk
EVToolbox.apk
EVWidgets.apk
Email.apk
Exchange.apk
Gallery2.apk
GenieWidget.apk
GoogleBackupTransport.apk
GoogleCalendarSyncAdapter.apk
GoogleContactsSyncAdapter.apk
GoogleLoginService.apk
GooglePackageVerifier.apk
GooglePackageVerifierUpdater.apk
GoogleQuickSearchBox.apk
GoogleServicesFramework.apk
GoogleTTS.apk
HTMLViewer.apk
KeyChain.apk
LauncherApex.apk
MarketUpdater.apk
MediaProvider.apk
MediaUploader.apk
Mms.apk
Music.apk
MusicFX.apk
NetworkLocation.apk
PackageInstaller.apk
Phone.apk
PicoTts.apk
Provision.apk
Settings.apk
SettingsProvider.apk
SharedStorageBackup.apk
SoundRecorder.apk
Stk.apk
Superuser.apk
SystemUI.apk
Talk.apk
TelephonyProvider.apk
UserDictionaryProvider.apk
Vending.apk
VoiceCommand.apk
VoiceSearch.apk
WAPPushManager.apk
df output on fresh installation:
Code:
Filesystem Size Used Free
/dev 202M 32K 202M
/mnt/asec 202M 0K 202M
/mnt/obb 202M 0K 202M
/system 145M 141M 3M
/data 287M 1M 285M
/cache 5M 784K 4M
screenshots below plus videos here 1/3 (installing) - 2/3 (average usage test) - 3/3 (game test)
mini-android-sdk-windows dedicated post
As explained few lines above this small zip downloadable from repository contains some batch scripts useful to automatize frequent operations, such as flashing radio, hboot, inject scripts, splash screen, etc...
simply unzip it on your physical hard drive ( C: ) in the folder you prefer, rename adb.ba_ as adb.bat, then move adb.bat under c:\windows folder, this to help you in recalling adb environment* (Start > adb > Run and it will open the folder plus a ready cmd shell)
*tested under Vista and 7, remember also if you intend to use adbWireless to edit IP.bat batch file and change IP (up 3) addresses matching the one of your device (useful for adbWireless)
let's take a tour on its content:
IP.bat => simple IP file configuration, write here your device IP list for connecting trough adbWireless (of course if you use it)
_flash_hboot.bat => this will flash hboot table, simply connect your device (without reboot in anything, just attach it) and provide in the same folder the hboot .img file named hboot.img (remember if you change hboot table to wipe before flash anything else)
_flash_radio.bat => as above but for radio, provide radio.img in the same folder, pay attention that radio flashing is really dangerous because in case of fault you'll probably brick your device, anyway latest radio provided for our device (on XDA or repository) is perfect so you shouldn't need to change it
_flash_recovery.bat => as above but for recovery, personally I use 4EXT (version 2.1.3 is faultless, download a copy from repository)
_flash_splash.bat => this is intended for flashing .bmp as splash screen (different from boot-animation, this is the 1st thing you see upon turn-on), provide splash1.bmp in the same folder ([email protected])
_push_98* => init script for control cpu freq (pay attention different version for different hardware, latest version already included in the slim rom)
_push_build.prop.bat => this will inject your personalized build.prop in your device (provide the file under extra folder)
_push_gps.conf.bat => as above, anyway the modded version is yet included in the slim rom
_push_hosts.bat => as above
_push_to_sdcard.abt => this batch script will copy under sd-card your drag'n dropped file (I use in conjunction with adbWireless)
_remove_stuff.bat => use this batch script with care, edit it to add removing actions
note: all .img file go under current folder, while all "extra" such as hosts, build.prop and init script go under extra folder
98mydesireI script dedicated post
1st part are just personal mods, you can keep, mod or remove, but the core of the script is the 2nd part, where the script itself creates a mini script named mycpu under /etc and will detach it in background (nohup /system/bin/sh /system/etc/mycpu&)
so in few words:
98mydesireI init script will be executed after complete boot (90 sec)
98mydesireI init script will write under /etc another script named mycpu (for managing cpu freq)
98mydesireI init script before exiting will launch mycpu control script
mycpu control script will stay in background looking for device state (sleep or wake) and applying relative properties
the annoying problem having a high cpu freq jump, for example from 245 to 1113 also with interactive/smartass governors, is that when your device wake up or when you don't put your fingers on it becomes a bit sluggish for a while
instead forcing freq matching display on/off states gives better results also if using conservative governor, in fact we don't need a "speedy" device when its screen is turned off... who use it in that state? while instead we want a speedy device when we actively use it, when its screen is turned on
so the most balanced setup is to have a really sleepy device when screen is off (99% of times not actively in use by user) and on the opposite a really speedy device when screen is on (99% of times in use by user)
the script will control also certain pid priority differently between sleep & wake states, during sleep state it will also recovery ram if under a critic level (right now fixed at 59Mb) by flushing caches
anyway is possible to specify min-max freq by editing 98mydesireI init script, look at these lines below they speak themselves :
Code:
echo 'MinFreqWake=960000;'>>/system/etc/mycpu
echo 'MaxFreqWake=1075200;'>>/system/etc/mycpu
echo 'MinFreqSleep=128000;'>>/system/etc/mycpu
echo 'MaxFreqSleep=384000;'>>/system/etc/mycpu
change values upon your needs, here below freq steps:
128000 245000 384000 422400 460800 499200 537600 576000 614400 652800 691200 729600 768000 806400 844800 883200 921600 960000 998400 1036800 1075200 1113600
to check correct behavior connect your device and open a shell (adb shell) then put commands:
cd /sys/devices/system/cpu/cpu0/cpufreq
turn off display (without detach of course)
cat scal*
last two numbers are current min-max frequencies, your freq min-max should be the lowest possible
turn on display and repeat step 3, your freq min-max should jump
if you turn off again your freq min-max should be lowered
downloading.. will report my experience after flashing
ill give this a go
good Idea Suiller ! - a comprehensive project !
I need to do a little home-work before I dip into this project....
Your repository is very familiar.
Ive taken things from there before
rraaka said:
good Idea Suiller ! - a comprehensive project !
I need to do a little home-work before I dip into this project....
Your repository is very familiar.
Ive taken things from there before
Click to expand...
Click to collapse
thank you friend... probably you used the repository during "diamond" era
added 98mydesireI script, you can edit it as you prefer (use for this purpose pspad editor), as default its primary goal is to manage cpu freq between sleep and awake states (245-245 when sleep, 900-1113 when awake)
This is not good idea.
k3lcior said:
added 98mydesireI script, you can edit it as you prefer (use for this purpose pspad editor), as default its primary goal is to manage cpu freq between sleep and awake states (245-245 when sleep, 900-1113 when awake)
This is not good idea.
Click to expand...
Click to collapse
why not? I use this setup from about 2 years... (from froyo/ginger) I prefer a really responsive device when I actively use it (screen on)
anyway it's easy to lower freqs, is enough to edit the script:
Code:
'MinFreqWake=960000;'>>/system/etc/mycpu
'MaxFreqWake=1113600;'>>/system/etc/mycpu
I'll put freq list on 3rd post
uploaded latest tested version at 12.00 (UTC/GMT time) - 14.00 (CET)
ps: no need to wipe again, just take a look of old apk still under /data/app such as LatinIME.apk (if you don't want default ics keyboard of course)
Does int boot also with stock hboot?? Or only with cm7r2??
gastrella said:
Does int boot also with stock hboot?? Or only with cm7r2??
Click to expand...
Click to collapse
sure, but you'll wast a lot of space... /system will take less than 140Mb
In one word: GREAT!!
I'll give it a try ASAP
P.S. already started to address your initiative onto ... Well, you know where!!
trinity1 said:
I'll give it a try ASAP
P.S. already started to address your initiative onto ... Well, you know where!!
Click to expand...
Click to collapse
thank you friend
tested latest slim version, I wiped everything to be sure & to simulate a complete new installation, all worked as expected so I'm going to publish (it will take few minutes), of course always in repository
ps: keep an eye on rom file date & time (on repository) to be sure you get the updated version
Hi..... Can I make a port request.....?
Sent from my HTC Desire using XDA
Miui ics v4 being developed for n1..... I hope its easy.... There is also a detailed porting guide on miui us. I tried many times but failed...:banghead:
Sent from my HTC Desire using XDA
no sorry, I don't have much time
I'll seek only this thread without beginning any new adventure
Yasir Javed Ansari said:
Miui ics v4 being developed for n1..... I hope its easy.... There is also a detailed porting guide on miui us. I tried many times but failed...:banghead:
Sent from my HTC Desire using XDA
Click to expand...
Click to collapse
I will try to port before end of May but I need people to test.
Sent from my HTC One V using XDA
Thanks
shubhamchamaria said:
I will try to port before end of May but I need people to test.
Sent from my HTC One V using XDA
Click to expand...
Click to collapse
Hi, thanks for response..... as i mentioned in your runny thread, i'm back on wmjan rom, but using ur framework files for swipe to clear, (thanks again), but im waiting for miui ics for desire as lenny has abandoned the project.... untill then, ill stay put at wmjan sense.
This package is designed to automate operations firmware update for the devices based on processor RK2918.
Important!
Use of this software package can cause damage to your device!
This software package is supplied "as is" and without warranty.
This software package may not meet your expectations.
ONLY FOR LINUX (and other *nix like OS)
You can:
- Unpack the firmware file consisting of one kind update.img (img mode, used RKBatchTool)
- Unpack the firmware file consisting of a set RK29xxLoader.bin Image/boot.img Image/system.img etc (Image mode, used RKTool)
- Change the name of the device and partition sizes (parameter file)
- Install su and superuser (root access)
- Install busybox in /system/xbin and create symlinks for the utilities that comes with busybox
- Choose and install/uninstall some system applications
- Change the file size system.img
- Create update.img
also
- Create their own plug-ins
- Create automated scripts based on an existing plugin library
- Modify the list of proposed system applications
- Plug-in to remove files from the "black list"
- some build.prop fixes
and
- dump current flash from device
Notes
The package runs on Linux operating systems (development and testing on OpenSUSE 11.4/12.2)
The user interface is implemented using utilities 'dialog'
Binary utilities (directory bin) can be compiled using:
# cd src /
# make && make install
Dependences: libusb-1.0, libusb-1.0-devel, libssl, libssl-devel, dialog, sudo, gcc
To work actively used sudo (you can set up password-less mode) - need to modify the partition 'system'
Use:
[full_or_partial_path/]menu.sh [workdir]
[full_or_partial_path/]batchImgRepack.sh [full_or_partial_path/]old.img
[full_or_partial_path/]batchImageRepack.sh [full_or_partial_path_to_Image]
flashdump
workdir may contain update.img (img mode) or set of files (Image mode)
Homepage
Latest version
Updates:
not use sudo if run as root
src/update.sh - update sources for used tools (start make && make install after update)
Whenever there's an over-the-air (OTA) update sent-out or made available (either leaked or official), there's always a large number of users that end-up reporting that their installations have failed with the infamous and dreaded "E:Error in /sdcard/xxx.zip (Status 7) installation aborted." error message. So, I decided to try to write an app that would help folks figure-out what the issues might be so that they can get their OTA update installed.
The OTA Verifier app can be used to evaluate an over-the-air (OTA) update.zip or other flashable .zip file before you attempt the install or afterwards to help you figure-out why the installation may have failed. OTA Verifier will point-out what files and conditions are being tested so that you can more easily attempt to correct these issues.
Play Market Link (free!): OTA Verifier (beta)
Do I have to be rooted to use this?
No, but rooted devices will have more conditions that the app will be able to test/evalute because it will have access to protected files that non-rooted devices don't.
Will the app actually do the installation or change anything on my device?
No. The app will only evaluate the expressions and conditions contained inside the updater-script file inside the .zip file that's trying to be installed. None of the functions or commands that try to modify your device (i.e., delete/patch/format/extract, etc.) will be evaluated or executed. The app basically operates in "read-only" mode with respect to the .zip file being evaluated.
Will this app work on older devices or flashable .zip files that use the amend update-script files?
No, this app evaluates and interprets the newer edify updater-script files (notice the "r" in "updater").
How do I use this app?
Install and launch the app
Click the "Select File" button and navigate to desired .zip file
Long-press (press and hold) the file entry for the desired .zip file
Click the "Verify OTA .zip" file pop-up
Wait for the app to process the file (should take under a minute, depending on your device)
View the displayed results (text will also be copied to the clipboard)
Miscellaneous info:
1. Savvy root users probably already know that after a failed .zip file installation, you should be able to view the /cache/recovery/log file to view the information about what might have failed. OTA Verifier will try to uncover all of the issues and not just the first one that causes the installation to fail.
2. While I wrote this app principally to evaluate OTA update.zip files, the edify updater-script files are used and written by ROM devs and others who created flashable .zip files. This app can be used to evaluate those file's updater-script files, too.
How does this all work?
Here's the basic outline/structure of what the app does:
1. the .zip file is selected by the user via the file selector
2. list of frozen system apps are identified for later reporting
3. the updater-script file is extracted from the META-INF/com/google/android folder in the .zip file
4. this updater-script file is parsed and converted into reverse polish notation (RPN) for execution
5. edify functions that might modify your device are NOT evaluated; these include apply_patch, delete, delete_recursive, format, mount, package_extract_dir/file, run_program, set_perm[_recursive], symlink, unmount, write_raw_image, etc.
6. note: the update-binary executable is not used by or involved in this app; the edify script interpreter that the app uses was written by me, in Java, specifically for this app
7. the remaining edify script functions that test conditions (such as apply_patch_check, apply_patch_space, assert, concat, file_exists, file_getprop, getprop, greater_than_int, if-then-else-endif, ifelse, is_substring, less_than_int, read_file, ui_print, and various operators (!, !=, &&, (, ), ;, ||, +, ==)) are evaluated using an operand/operator stack from the RPN expression parsed from the updater-script statements
8. expressions that fail (return a null-string) or are bypassed (usually because a resource (file/partition) is protected/secured against read-access) are reported for the user
9. after the entire script has been processed, the results are displayed in a pop-up window on the device and the text of those results are copied to the clipboard
Planned / future features:
- preferences / settings
- logging of the output to a file on the /sdcard
- test if .zip file is signed or not
- display more stats
- "explanation mode" to interpret, in English, what the edify commands are testing
Successfully tested on:
Samsung Galaxy Nexus (CDMA) 4.1.1
Samsung Galaxy Nexus (GSM) 4.1.2
Asus Nexus 7 tablet 4.1.2
Motorola Droid X 2.3.4
The following edify commands/functions/operators are supported:
Code:
[COLOR="blue"]apply_patch_check[/COLOR] // apply_patch_check ( <filepath>, <sha1-checksum> [ , <sha1-checksum> ... ] )
// apply_patch_check ( <compoundvalue> )
<compoundvalue> := [ EMMC : <filepath> : <sha1-size> : <sha1-checksum> [ <sha1-size> : <sha1-checksum> ... ]
[ MTD : <dev-block> : <sha1-size> : <sha1-checksum> [ <sha1-size> : <sha1-checksum> ... ]
[ vfat : <dev-block> : <sha1-size> : <sha1-checksum> [ <sha1-size> : <sha1-checksum> ... ]
<dev-block> := filename in /dev/block
[COLOR="Blue"]apply_patch_space[/COLOR] // apply_patch_space ( <bytes> )
[COLOR="blue"]assert[/COLOR] // assert ( <expression> )
[COLOR="blue"]concat[/COLOR] // conact ( <string> , <string> )
[COLOR="blue"]file_exists[/COLOR] // file_exists ( <filepath> )
[COLOR="blue"]file_getprop[/COLOR] // file_getprop ( <filepath>, <propertyname> )
[COLOR="blue"]getprop[/COLOR] // getprop ( <propertyname> )
[COLOR="blue"]greater_than_int[/COLOR] // greater_than_int ( <integer>, <integer> )
[COLOR="blue"]if then else endif[/COLOR] // if <condition> then <expression> [ else <expression> ] endif
[COLOR="blue"]ifelse[/COLOR] // ifelse ( <condition>, <then-expression> [ <else-expression> ] )
[COLOR="blue"]is_substring[/COLOR] // is_substring ( <string> , <string> )
[COLOR="blue"]less_than_int[/COLOR] // less_than_int ( <integer>, <integer> )
[COLOR="blue"]read_file[/COLOR] // read_file ( <filepath> )
[COLOR="blue"]ui_print[/COLOR] // ui_print ( <string> ) parsed & executed, but output not displayed
[COLOR="blue"]![/COLOR] // logical NOT operator
[COLOR="blue"]!=[/COLOR] // not equals operator
[COLOR="blue"]&&[/COLOR] // logical AND operator
[COLOR="blue"]([/COLOR] // open paren: precedence / grouping
[COLOR="blue"])[/COLOR] // close paren: precedence / grouping
[COLOR="blue"];[/COLOR] // sequence/imperative (terminates & separates statements)
[COLOR="blue"]||[/COLOR] // logical OR operator
[COLOR="blue"]+[/COLOR] // string concatenation operator
[COLOR="blue"]==[/COLOR] // equals operator
[COLOR="blue"]#[/COLOR] // comment line
The following edify functions are NOT supported (the majority of them because they are intended to modify your device):
Code:
[COLOR="blue"]apply_patch[/COLOR]
[COLOR="blue"]delete[/COLOR]
[COLOR="blue"]delete_recursive[/COLOR]
[COLOR="blue"]format[/COLOR]
[COLOR="blue"]mount[/COLOR]
[COLOR="blue"]package_extract_dir[/COLOR]
[COLOR="blue"]package_extract_file[/COLOR]
[COLOR="blue"]run_program[/COLOR]
[COLOR="blue"]set_perm[/COLOR]
[COLOR="blue"]set_perm_recursive[/COLOR]
[COLOR="blue"]symlink[/COLOR]
[COLOR="blue"]unmount[/COLOR]
[COLOR="blue"]write_raw_image[/COLOR]
[COLOR="blue"]is_mounted[/COLOR] // innocuous, but still not supported
[COLOR="blue"]stdout[/COLOR] // innocuous, but still not supported
[COLOR="blue"]show_progress[/COLOR] // innocuous, but still not supported
[COLOR="blue"]set_progress[/COLOR] // innocuous, but still not supported
Keywords:
OTA, over-the-air, updater-script, edify, amend
Screenshots:
updated 9-May-2014
updated to version 1.3
Updated app with root-enabled file browser for navigating to protected/secured directories like /cache to select OTA's update zip file.
Full change log to date:
[v1.3 - 04-Nov-2012]:
- for rooted devices, change file browser to allow navigating and selecting .zip files in protected directories (like /cache)
[v1.2 - 29-Oct-2012]:
- minor fix to handle two reports of null pointer exceptions
[v1.1 - 28-Oct-2012]:
- remove unused SD card write permission
[v1.0 - 28-Oct-2012]:
- initial Play Market release
This is pretty cool.
Any chance you could direct me to an explanation for sha1-size (for apply_patch_check) is though? I'm working on some edify scripting stuff and trying to incorporate some asserts for a specific bootloader (important to what I'm doing), and this is honestly the best reference I've found for it yet.
osm0sis said:
This is pretty cool.
Any chance you could direct me to an explanation for sha1-size (for apply_patch_check) is though? I'm working on some edify scripting stuff and trying to incorporate some asserts for a specific bootloader (important to what I'm doing), and this is honestly the best reference I've found for it yet.
Click to expand...
Click to collapse
You bet!
I'm heading home from work here soon and I'll dig-up the details for you .
(yeah, I scoured the internet for detailed information on Edify scripting as well as reviewed the actual Google/Android code--there's not a complete compendium, unfortunately).
I'll ping you back after a bit...
Cheers!
osm0sis said:
Any chance you could direct me to an explanation for sha1-size (for apply_patch_check) is though?
Click to expand...
Click to collapse
Okay, here's what I know about the apply_patch_check command:
There are basically two formats:
Code:
apply_patch_check // apply_patch_check ( <filepath>, <sha1-checksum> [ , <sha1-checksum> ... ] )
// apply_patch_check ( <compoundvalue> )
<compoundvalue> := [ EMMC : <filepath> : <sha1-size> : <sha1-checksum> [ <sha1-size> : <sha1-checksum> ... ]
[ MTD : <dev-block> : <sha1-size> : <sha1-checksum> [ <sha1-size> : <sha1-checksum> ... ]
[ vfat : <dev-block> : <sha1-size> : <sha1-checksum> [ <sha1-size> : <sha1-checksum> ... ]
The first of which is what I think you typically see in updater-script files where you have a filename, followed by one or more SHA1 digests. Here's an example:
assert(apply_patch_check("/system/app/ApplicationsProvider.apk", "41bb5aaaa2791e68b55622fcca13f0e4efa757b2", "fc845332ae7f706824de73f64ae47f93866ad245"));
The second format is what I call a compound value format, where the file or partition to be checked and the SHA1 digests to be compared, are all concatenated together in a single, colon-separated value. For example:
assert(apply_patch_check("EMMC:/dev/block/platform/omap/omap_hsmmc.0/by-name/boot:4247552:3f4d4f9549d307d152f8503983ee4ff5f46b0a43:4470784:fbd13c778b34fdb7917c1ccee6389aa9b13a92bd"));
In the above, I've colored the sizes in red of file/partition on which to compute the SHA1 checksum (colored in black). I figured this out and verified this by using dd to copy the portions of the partition in question and calculating the SHA1 checksums on it.
My app only supports parsing and evaluating two sets of lengths/SHA1s for the compound format at this time (that's all I've encountered so far in the scripts that I've viewed).
Does that help and/or answer your questions?
Cheers!
Thanks! Yeah that helps a lot, but unfortunately it doesn't seem to solve the problem I've been seeing..
Using dd to grab the partition img I can sha1sum that and that SHA1 doesn't allow it to pass the assert, or even a direct sha1_check of the partition.
Code:
run_program("/sbin/busybox", "dd", "if=/dev/block/platform/sdhci-tegra.3/by-name/USP"), "of=/tmp/bootloader.img")
ui_print(sha1_check(read_file("/tmp/bootloader.img"))); = 8c206a1a87599f532ce68675536f0b1546900d7a (also, bootloader.img is 2097152 in size)
ui_print(sha1_check(read_file("/dev/block/platform/sdhci-tegra.3/by-name/USP"))); = da39a3ee5e6b4b0d3255bfef95601890afd80709
assert(apply_patch_check("EMMC:/dev/block/platform/sdhci-tegra.3/by-name/USP:2097152:8c206a1a87599f532ce68675536f0b1546900d7a")); = Fail
They just don't match and I'm completely baffled by it. I can work around it by using dd to pull the img first and using that for my asserts but it's not as clean as I'd like it.
osm0sis said:
Yeah that helps but I guess unfortunately it doesn't entirely solve the problem I've been seeing.
Using dd to grab the partition img I can sha1sum that and that SHA1 doesn't allow it to pass the assert, or even a direct sha1_check of the partition.
They just don't match and I'm completely baffled by it. I can work around it by using dd to pull the img and using that for my asserts but it's not as clean as I'd like it.
Click to expand...
Click to collapse
Is it for the Gnex or the N7 (I have those same devices)?
I'd be happy to test something for you...just PM me or send me an email ([email protected]).
I don't know if you're using my app to test with, but you can also manually run the update-binary directly on/from your phone (i.e., you don't have to run it in recovery, but you obviously need to be careful what your updater-script does ).
I'm still looking for the exact syntax in my notes, but I'll edit this post when I find it...brb.
~ ~ ~
edit: http://wiki.opticaldelusion.org/wiki/Update-binary shows this:
update-binary <api> <pipefd> <zip>
Click to expand...
Click to collapse
I know I did this during my early testing, but I can't remember the exact syntax...I'll try it and re-re-edit .
Man thanks so much, PM sent.
Sorry for cluttering up your thread with this semi-OT stuff.
osm0sis said:
Man thanks so much, PM sent.
Sorry for cluttering up your thread with this semi-OT stuff.
Click to expand...
Click to collapse
LOL, not a problem...it's all Edify-related and updater-script related...I'm betting that's what'll lead most folks here.
Happy to help .
==================
Detailed Analysis
==================
- you have no frozen system apps (good!)
- there were 2 failed expressions; see below for the details about these tests that will cause your OTA install to fail
- there were no bypassed expressions (good!)
-------------------------------
statistics:
frozen system apps: 0
success count: 526
fail count: 2
ignore count: 1587
partition count: 2
protected count: 2
bypassed count: 0
-------------------------------
updater-script analysis details:
FAILED: line #268:
assert(apply_patch_check("/system/app/XT9IME.apk", "8aba56a4406128e78f5729753252c3d93bc21cb4", "965b437bce65018eeb31ff9a381c3687542099e0"));
----------------------
FAILED: line #1038:
assert(apply_patch_check("EMMC:/dev/block/platform/sdhci-tegra.3/by-name/LNX:5013504:c48f8e86c73fb2c2ba1794f5ec98e27c9e206ed5:5060608:319331fae14fec8a88063751475fce26bae328e0"));
So a question, could this failure above be causing my 32 GB nexus 7 to have system update issues? (Not necessarily XT9IME.apk (which I shouldn't have deleted), more the other one) Is there a fix?
Sent from my Nexus 7 using Tapatalk HD
---------- Post added at 10:44 AM ---------- Previous post was at 10:39 AM ----------
==================
Detailed Analysis
==================
- you have no frozen system apps (good!)
- there were 2 failed expressions; see below for the details about these tests that will cause your OTA install to fail
- there were no bypassed expressions (good!)
-------------------------------
statistics:
frozen system apps: 0
success count: 526
fail count: 2
ignore count: 1587
partition count: 2
protected count: 2
bypassed count: 0
-------------------------------
updater-script analysis details:
FAILED: line #268:
assert(apply_patch_check("/system/app/XT9IME.apk", "8aba56a4406128e78f5729753252c3d93bc21cb4", "965b437bce65018eeb31ff9a381c3687542099e0"));
----------------------
FAILED: line #1038:
assert(apply_patch_check("EMMC:/dev/block/platform/sdhci-tegra.3/by-name/LNX:5013504:c48f8e86c73fb2c2ba1794f5ec98e27c9e206ed5:5060608:319331fae14fec8a88063751475fce26bae328e0"));
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
So a question, could this failure above be causing my 32 GB nexus 7 to have system update issues? (Not necessarily XT9IME.apk (which I shouldn't have deleted), more the other one) Is there a fix?
modwilly said:
So a question, could this failure above be causing my 32 GB nexus 7 to have system update issues? (Not necessarily XT9IME.apk (which I shouldn't have deleted), more the other one) Is there a fix?
Click to expand...
Click to collapse
Looks like you've updated the boot (LNX) partition in addition to deleting (or renaming/moving) the XT9IMG.apk?
So yes, the OTA will not install until you've put both items back to their expected state.
The fix, of course, depends on exactly what you did to change them in the first place.
version 2.1 uploaded to Play Store
Major re-write of app done for version 2.0 and above.
Recent change log:
[version 2.1 - 6-May-2014]:
- fix issue w/identification of non-existent files
[version 2.0 - 5-May-2014]:
- major app update: edify parsing, RPN processing and execution engine completely re-written
- original core app behavior and functionality remain the same, but code cleanup and re-write should mean better and more robust handling of future OTA updater-script expressions
Click to expand...
Click to collapse
Thanks and let me know if you have any questions.
@scary alien could you please tell me how to get apply_patch_space bytes? i am making ota script and i got almost all, still need to generate:
apply_patch_space(bytes) || abort("Not enough free space on /cache to apply patches.");
Click to expand...
Click to collapse
i just dunno how
ZduneX25 said:
@scary alien could you please tell me how to get apply_patch_space bytes? i am making ota script and i got almost all, still need to generate:
i just dunno how
Click to expand...
Click to collapse
It's just the available space (in bytes) in the /cache partition that you want to make sure is available (i.e., free space) for any operations your updater-script file will do concerning /cache.
For example:
apply_patch_space(1000000) || abort("Not enough free space on /cache to apply patches.");
Click to expand...
Click to collapse
Would verify that there is at least 1MB (1,000,000) free bytes available in /cache.
Does that answer what you're asking?
Lemme know--happy to help if I can.
Cheers!
@scary alien not really, i mean i know how it works, just dunno how to generate proper size in updater, for example:
i create regular ota: multiple .p files and some images, zipped, signed OTA.zip size is 20mb, /patch size is 7 mb, images 10 mb and /system (new files) 3mb, how do i know how many bytes i should set to make this ota install in recovery?
should i summarize .p files size or target (patched apk, jar) files size (would be around 90mb) or what else?
I think the size would depend on when your patch files are cleaned-up...i.e., after each patching operation or at the end. If its at the end, you'll of course need to account to all of the space you might use in /cache.
I don't know of a good way to tell you what the high water mark would be other than testing and recording the output of a "df /cache" command at various points in your updater-script file.
I could do that however I don't see it universal or handy, each ota has different size so it would need more/less free space every time.
There is how Google gets this value : https://github.com/MiCode/patchrom_tools/blob/kitkat/releasetools/edify_generator.py#L131 maybe you will understand better.
ZduneX25 said:
I could do that however I don't see it universal or handy, each ota has different size so it would need more/less free space every time.
There is how Google gets this value : https://github.com/MiCode/patchrom_tools/blob/kitkat/releasetools/edify_generator.py#L131 maybe you will understand better.
Click to expand...
Click to collapse
I think I understood what you meant...there's no easy way to make this universal for each OTA except to evaluate each file that might need to use space resources from the /cache partition.
Even the edify-generator git that you referenced does this dynamically:
releasetools/ota_from_target_files:
Code:
for diff in diffs:
tf, sf, d = diff.GetPatch()
if d is None or len(d) > tf.size * OPTIONS.patch_threshold:
# patch is almost as big as the file; don't bother patching
tf.AddToZip(output_zip)
verbatim_targets.append((tf.name, tf.size))
else:
common.ZipWriteStr(output_zip, "patch/" + tf.name + ".p", d)
patch_list.append((tf.name, tf, sf, tf.size, common.sha1(d).hexdigest()))
[COLOR="Red"]largest_source_size[/COLOR] = max([COLOR="red"]largest_source_size[/COLOR], sf.size)
:
:
:
if patch_list or updating_recovery or updating_boot:
script.[COLOR="Blue"][B]CacheFreeSpaceCheck[/B][/COLOR]([COLOR="red"]largest_source_size[/COLOR])
I have seen it, but here comes largest_source_size:
Code:
largest_source_size = 0
https://github.com/MiCode/patchrom_tools/blob/kitkat/releasetools/ota_from_target_files#L532
ZduneX25 said:
I have seen it, but here comes largest_source_size:
Code:
largest_source_size = 0
https://github.com/MiCode/patchrom_tools/blob/kitkat/releasetools/ota_from_target_files#L532
Click to expand...
Click to collapse
Yeah, that's just the initialization of that variable...it gets updated in the for-loop that I included above.
(you know that's not my tool, software, right?)
Twister Team (Frenkie99999999&Spiderman1961) is glad to present:
TWISTER 2
Credits to:
almar (Marc)
bsbsbs (Sándor)
Egon
phj (János)
Voyteckst
Frenkie99999999999
kukafei
Linuxsigh
Argentinos
ROM is based on Android 2.2.2 Froyo. I applied code tweaks and improvements to make it more performant and smoothROM is free from malfunctions: the system is smooth; any lag will be due only with apps installation not fully compatible or incorrect installation procedureAndroid on OMNIAII is a safe bet won thanks to the efforts of many who have worked tirelessly and pure passion: to complain about minor inconveniences is misplaced. You can not expect perfection from our terminal that even natives Android devices have
Changelog:
General improvements:
-New Bootanimation by Twister Team-Trasparent Status Bar-JelMiBean Theme: new icons, new wallpaper, new buttons, new battery iconsa and so on...-Locked Launcher in memory by script (disable option in Spicagenmod settings and in launcher settings-New themed System Apps-Playstore updated v 4.1.10-Quick Pick update v. 2.9.4-AdAway: no ads-Camcorder shorthcut-FlashPlayer-Miui Music Player-MxPlayer-Toggle2G to save battery drain-GApps for CM6 (CarHome, Facebook, Gmail, Latitude, Luoghi, Maps, Navigatore, Genie Widget, GoogleSearch, VoiceSearch, Talk, Twitter)-Bravia Engine: increased video sharpness-Xloud Engine: increase loud sound and virtual effects-New progress bar colour-Jelly Bean font-New Kernel: 2.6.32.9 [email protected]-New Sound system-New Dialer-New and hacked MMS.apk: no automatic mms conversion after 4 sms; recipients up 200
Code improvements and Tweaks:
-Supercharged with adapted zeppellinrox script-Improved real Mutitasking with "Low Memory killer balanced script": DON'T USE TASK MANAGER TO KILL APP (ONLY IF REALLY NECESSARY)-Improved automatic detailing databases on boot: better speed and smoothness-Improved Zipalignin and fixpermission apps on boot: no FC, better battery drain and ram-Build.prop modified-Tweak battery for better drain-Improved VM Tweaks-Improved read ahead cache up 2048 kb: better speed access data-Cache flushing on boot-Better scrolling and touchscreen responsiveness-Disabled Zram compression: not friendly for our device-Tweaks for better smoothness-Network data tweaks for fastest 3G-Best Dialer responsiveness: fix delays and black screen issue-Improved photo and video recording-Kernel tweaks: better I/O and governor settings without random reboot-Ext4 smart mounting (noatime, disable barrier etc): better speed disk access-Sysctl tweaks: minor lags-Automatic screen state scaling-Better Network Throughput-GPS issue (only for any users): no thirdy part apps for fix! First fix on my moving car: 3 min. Other fix few seconds-Video Recording A/V Sync for CM6 removed: crashing video recording-Both Cameras and VideoCameras working: added VideoCamera shortcut. Use it for videocamera and your apps don't crash
Credits to:
Moonguy75
Costinuz32
knzo
ImbaWind
zeppellinrox
What's working:-Audio-Receiving and making calls-GPS-Compass-Proximity sensor-Wifi-Bluetooth-USB mass storage-CamerasPartially working:-Reset dataNot working-Update Binary Superuser-Theter wifi
SCREENSHOT PREVIEW
DOWNLOAD LINK
Part 1Part 2
After download unzip with 7zip: you will have a folder with all necessary for installation: rom, kernel, haret.exe, startup.txt...
ROM IS SET ON ITALIAN LANGUAGE: TO CHANGE IT GO TO "IMPOSTAZIONI/LINGUA E TASTIERA" AND CHOOSE YOUR LANGUAGE
Installation instructions
First some considerations:
A. Porting Android on Omnia (born for WinMobile 6.5) is a pure gamble: to complain of minor malfunctions, claiming a perfection that there is not even on the native device is totally out of place.
It's part of game: in almost all cases, these small hitches, which does not at all preclude the daily use of the terminal, are solved with a simple reboot.
B. Please follow the installation procedure to the letter, without neglecting any detail, otherwise block the installation or malfunction with lag and other troubles of the terminal.
C. The installation must be done with telephone SIM and microSD inserted!!!!!
D. It is recommended to install remaining disconnected from the Internet and with the antivirus disabled
INSTALLATION STEPS FOR OMNIAII WITH2GB OF INTERNAL MEMORY
LINK TO ILLUSTRATED INSTALLATION GUIDE
1. Connect device to PC through USB under WinMobile ("Settings Samsung / Usb Connection / "My Storage")
2. Open MiniToolPartition wizard
3. Delete all partitions in "My Storage".
4. Create three new partitions:
5. FIRST PARTITION: FAT32, LOGICAL, 500mb, label "DISK"
6. SECOND PARTITION: EXT4, LOGICAL, 1250mb, label "disk"
7. THIRD PARTITION: LINUX SWAP, LOGICAL, 200MB, no label
PARTITIONS FOR USERS WITH OMNIA 8GB (Credits to Lagunostrum)FIRST PARTITION: 6390 Gb, FAT32, LOGICAL, label "DISK"
SECOND PARTITION: 1250 Mb, EXT4, LOGICAL, label "disk"
THIRD PARTITION: 196 Mb, LINUX SWAP, LOGICAL, no label
IMPORTANT: For users with Omnia 8Gb, you must change the startup.txtAt line [Set CMDLINE "rootdelay = 2 root = / dev/mmcblk1p2 init = / init"] change as follows:
Set CMDLINE "rootdelay = 2 root = / dev/mmcblk1p6 init = / init"
DO NOT create Linux partitions SWAP MORE 'BIG 200 Mb,
ACCORDING TO MANY DEVELOPERS, SUCH DIMENSIONS SLOW THE DEVICE
8. Close MiniTool Partition Wizard
9. Start Ubuntu in Virtual Machine (those who have not can disconnect the phone from Windows and, after running Ubuntu, can connect with the procedure described below)
10. Click on the menu "Virtual Machine", select "Removable devices", select GTI8000, select "Connect" to connect Omnia to Ubuntu
11. Open "Gparted" or other utility Ubuntu to partition the disk
12. Right-click on "ext4" and "remove" the partition, right-click again to "ext4" and choose "Format as ext4" (with tests carried out, it is more snappy rom installed on a formatted partition from Ubuntu in "ext4 "with respect to a partition" ext4 "formatted by MiniTool)
13. Right-click on "linux-swap" and format as "linux-swap" (for the same reason as above)
14. Close "Gparted"
15. Click on the menu "Virtual machine / Removable devices / Disconnect" to disconnect and reconnect the phone automatically from Ubuntu to Windows (do not disconnect the USB cable!!!!)
16. Close Ubuntu
17. Set the date on the PC on September 2011 (if it does not work in September 2010)
18. Open Image For Windows and choose "Restore (Normal)"
19. Navigate to the folder where you saved the ROM and select it
20. Click "Next" and flag the ROM to be installed
21. Click again on "Next" and choose where to install the ROM: Of course it will be the EXT4 partition (Linux native)("disk"), 1250 Mb created with MiniTool and reformatted under Ubuntu
22. Click "Next" and continue until screen will warn you that all data on the target partition will be deleted and be replaced by those of the ROM: click OK and continue
23. On next screen, leave options settings as you find them
24. On next screen click "Start" and start the procedure.
25. After installation, close Image For Windows and set time PC correctly.
Copy the files "haret.exe", "startup.txt" and "zImage" in DISK. (ie the root of the "My storage" WinMobile).
These files must remain in DISK (ie the root of the "My storage" WinMobile).
26. From WinMobile, with a File Manager, navigate to "haret.exe" and click it to start Android.
27. After first boot of Android, DO NOT USE THE TELEPHONE, wait for SO fully started and RESTART the phone
At the end of the second boot you can enjoy Android on OMNIAII
28. Set Playstore on "do not automatically update applications"!!!!!!!
Choose carefully what to update because recent apps are the most greedy of ram (block the phone) and they bring very little improvement.
ESPECIALLY DO NOT UPDATE GAPPS (CarHome, Facebook, Gmail, Latitude, Places, Maps, Navigation, Genie Widget, GoogleSearch, VoiceSearch, Talk, Twitter), otherwise they will not be opened.WHILE I WRITE I HAVE JUST TESTED FACEBOOK: slow on GALAXY ADVANCE OF MY WIFE, but splinter on my old Omnia
Frequently Asked Question
During installation of our Rom you can present difficulties. Often they are the same and identical are solutions.
For this reason I group here most common issues with most appropriate solutions: all tested and working.
PLEASE READ THESE LINES CAREFULLY BEFORE POST QUESTIONS THAT HAVE ALREADY HERE 'FOUND REPLY
Installation Tweaks
1. Why 'install in "My Storage"?
'Cause it's 5 times more' fast!
Here's how: Copy files haret.exe, startup.txt and zImage in the Root of My Storage, the 2-Gb or 8 Gb.
2. Can I install in external MicroSD?
Recently many users have done: must comply with these conditions:
-Microsd must be at least class 10
File startup.txt-line [Set CMDLINE "rootdelay = 2 root = / dev/mmcblk1p6 init = / init"] should be changed as follows: Set CMDLINE "rootdelay = 2 root = / dev/mmcblk0p2 init = / init"
-File haret.exe, startup.txt and zImage must be copied on the external MicroSD
3. WinMobile is cleared or noised by Android installation?
Android does not cause, any "noise" to the Windows Mobile operating system installed natively on the phone. It will continue to work regularly: in fact we will have a phone with two operating systems fully functional.
4. What should I do just installed Android?
As soon as the phone has started completely must restart your phone to avoid any problems
5. Why on first boot phone remains locked on Android on Omnia II loading?
Possible answers:
a) Can 'have damaged some files in decompression: REINSTALL ALWAYS REPLACE ON ANY FAILURE
b) There may be some corrupt files in download: trying to re-download rom.
c) There may be a problem on disk address. The kernel has booted, the phone can not find the operating system and crashes.
In this case, proceed as follows:
-write disk address ext4 under Ubuntu ("disk") and change startup.txt (ONLY WITH NOTEPAD + +!!):
for example, if ext4 partition under Ubuntu is dev/sdb6 change the value: root = / dev/mmcblk1p6 init = / init "boot
6. If Ubuntu identifies the ext4 partition (disk) as / dev/sdc6 "(and not / dev/sdb6)" What should I do?
Open the file startup.txt and edit it as the "code" that appears in the format window under ubuntu:
change the last line of the file Startup set CMDLINE "rootdelay = 2 root = / dev/mmcblk1p6 init = / init" boot ----> mmcblk2p6.
7. What is the file startup.txt?
The file contains the parameters address of Android system.
The line we are interested in is the following: "Set CMDLINE" rootdelay = 2 root = / dev/mmcblk1p6 init = / init "
"1" is number disc (if you have inserted a microSD the value must be "1" if it is not inserted must be "0").
"6" is number partition "disk" (in most cases, by partitioning "disk" with MiniTool, is assigned the number 6 to the Linux partition).
If after installation, the phone hangs on Android on Omnia II Loading, 99% one or both of the values mentioned above are incorrect.
In most cases, if you install with microSD inserted, values to be inserted are "mmcblk1p6."
If problems occur the reason is constituted by 'physical address that has been assigned to the partition "disk", in which case we need to understand which the partition number your computer has assigned to "disk". To do this, just to see, when you format under ubuntu, on the top bar of the window formatting: here a code appears "sdbX" where X is the partition number: record it and edit it in the line of reported
8. For other installations have to repartition and format all over again?
No: once done partitioning procedure, next time that you install a future release of the rom, just install the image. TBI, with "ImageForWindows", without touching the partitions.
9. How can I replace the kernel?
Just copy the zImage in "My Storage" and "Storage", and start Android.
10. Why Image for Windows does not work?
You must set date pc on September 2011 (or 2010)
11. To install any update of Rom need to do the whole process all over again or just replace some files?
It should make the whole process all over again.
The kernel can be replaced individually, but the modded if copied at a later time inhibit the free wi-fi. You should clean the cache, delete a file .conf and anyway rom would be unstable.
12. My Omnia 8GB is: how should be large partitions?
Configuration tested and running on Omnia 8Gb (Credits to Lagunostrum):
1) 1st Partition FAT32, 6390 mb, Logical
2) 2nd partition 1250 mb EXT4, Logical
3) 3rd Linux swap partition 196 Logical
13. Can I increase size of Linux swap partition?
Many developers recommend not to exceed a size of 250 MB for partition in question: that instead of increasing the performance to slow down greatly.
14. Why I do not read anymore the external microSD?
For those who have problems with the microSD: Make sure that the SD is working and that is formatted Fat32 Primary and Active. use SDFormatter
15. How can I access the phone as a USB memory?
You have to go in Settings \ Applications \ Development and remove the flag on Debug USB.
16. Why, despite having removed flag on usb debugging phone is not recognized as USB storage?
-First of all, try restarting your computer and phone.
- If this is not enough the solution is the following:
under Windows, you can go to the "Computer Management", then "Disk Management" and there if Android appears without a letter assigned, assign one with the right button, "Change Drive Letter and Paths" and you're done
-Check if you are corrupt drivers of the phone and possibly reinstall
17. Why phone does not wake up after the screen is turned off?
Often it is sufficient to press the awakening and even if the screen does not light up, wait a few more seconds and everything will fall into place.
18. How does hardware buttons work?
HARDWARE KEYS WORKS LIKE ON WINDOWS MOBILE
19. Satellites Fix needs thirdy part application?
No, works perfectly by itself: the first fix is slow (takes several minutes), the following are faster (a few seconds)
20. Why the time is not exact and is always back an hour?
This problem can be solved permanently under WinMobile setting time zone of London / Dublin (with Italian correct time) and under Android time will be ok
21. If one day I do not want more android how do I delete it and only have windows?
Just delete the ext4 partition and expand the fat32 partition to the whole disk.
21. How should I set the Bluetooth?
1) make visible the device
2) under the heading "discoverable duration" set "infinite"
3) under "discoverable timeout" set "2 minute"
4) searches for available devices and match omnia
System tweaks
System tweaks
1. How can I "paint" notifications pull-down menu in the top bar?
Go to SpicagenMod settingS \ Interface \ Notification colors and choose a color for each entry in the "Statusbar notifications" and "Items notification"; "Notification bar" lets you make additional changes to the bar and colors.
2. How can I save battery power?
-from "System Settings" control which apps consume more battery and block them or set them so they suck less
-Then check with the app CPUSpy if the phone goes into DeepSleep: if there is there any app that runs in the background and consumes. Locate and disable
-use GPS, WiFi and Bluetooth only when needed, otherwise disable
-use 2G instead, switch to 3G only for data connections: it is preinstalled in the ROM Toggle2G that automatically manages the switch (but remember to disable it because otherwise you will not have data connection)
3. How do I see what's running in the background?
Go to Settings, Applications, Manage applications and check what apps are running, for safety always under applications, go to the Services running and check which services are run in the background
4. How can I speed up the execution of the app?
With the pro version of Titanium Pro go to / batch operations / manipulates data / activating "convert DB mode Wal" click it: system is much more responsive.
5. How can I save on the consumption of Ram?
-Not too heavy with both the home, with too many widgets, and the device with too many apps. The phone will have greater reactivity '.
6. How can I make a Nandroid Backup, because here we can not get into Recovery Mode?
With ImageForWindows, you can create a backup image of the Rom, crystallize it with all the settings and installed app. Simply make the backup procedure (full)
7. How to replace bootanimation?
With a file explorer with root access like Root Explorer go to / system / media and replace the bootanimation.zip file.
Or just remove the file, and we'll start the classic writing android that lights up.
9. How do I disable the apps that start up automatically?
Download app from the Play Store that makes access to the list of apps that start automatically on boot.
CAREFUL DO NOT DISABLE APPS SYSTEM, (ie text messages, phone, market, 'Android system, ... otherwise the system becomes unstable!)
System maintenance
SYSTEM MAINTENANCE
The following commands are all to be understood as to perform on a window Terminal Emulator pre-installed in ROM
To get more in-depth ram in case of remarkable system slowdowns type:
su (enter)
flush (enter)
-To compact database for faster access to the data type:
su (enter)
vac (enter)
-To realign app (especially if you installed new ones) in order to save on battery drain and ram type:
su (enter)
zepalign (enter)
-To Wipe Cache and Dalvik Cache (often used to prevent various malfunctions of the system) type:
su (enter)
sclean (enter)
-To make a Fix permission (needed to resolve issues of app Force Close) enter:
su (enter)
fixfc (enter)
System reboot, after typing these commands, in many cases it will be very, very, very long: do not worry if the bootanimation runs for a long time and the system does not seem to restart.
And 'quite normal. Android is performing the routines start from scratch without reading the previous (now deleted because it caused errors) and eventually will boot more agile than before.
Ubuntu installation method
UBUNTU METHODINSTALLATION STEPS FOR OMNIAII WITH 2GB OF INTERNAL MEMORYLINK TO ILLUSTRATED INSTALLATION GUIDE
1. 1. Connect device to the PC via USB under WinMobile ("Settings Samsung / Usb Connection / "My Storage")
2. Open MiniToolPartition wizard
3. Delete all partitions in "My Storage" of phone.
4. Create three new partitions
5. FIRST PARTITION: FAT32, LOGICAL, 500mb, label “DISK”
6. SECOND PARTITION: EXT4, LOGICAL, 1250mb, label “disk”
7. THIRD PARTITION: LINUX SWAP, LOGICAL, 200MB, no label
PARTITIONS FOR USERS WITH OMNIA 8GB (Credits to Lagunostrum)FIRST PARTITION: 6390 Gb, FAT32, LOGICAL, label "DISK"
SECOND PARTITION: 1250 Mb, EXT4, LOGICAL, label "disk"
THIRD PARTITION: 196 Mb, LINUX SWAP, LOGICAL, no label
IMPORTANT: For users with Omnia 8Gb, you must change the startup.txtAt line [Set CMDLINE "rootdelay = 2 root = / dev/mmcblk1p2 init = / init"] change as follows:
Set CMDLINE "rootdelay = 2 root = / dev/mmcblk1p6 init = / init"DO NOT CREATE LINUX PARTITIONS SWAP MORE 'BIG 200 Mb, ACCORDING TO MANY DEVELOPERS, SUCH DIMENSIONS GREATLY SLOW THE DEVICE8. Close MiniTool Partition Wizard
9. Open Ubuntu
10. Click on "Virtual Machine", select "Removable devices", select "GTI8000", select "Connect" to connect 1Omnia to Ubuntu: note "DISK" and "disk" that you have created with MiniTool
11. Open “Gparted” or other Ubuntu utility to partition disks
12. Right-click on "ext4" and "remove" partition, right-tap again to "ext4" and choose "Format as ext4" (with tests carried out, it is more snappy rom installed on a formatted partition from Ubuntu in "ext4 "with respect to a partition" ext4 "formatted by MiniTool)
13. Right-click on "linux-swap" and format as "linux-swap" (for same reason as above)
14. Close “Gparted”
15. Open Terminal window:
16. Write following command line: sudo cp /media/DISK/ext4.tar.gz /media/disk/
17. Press enter and wait for operation completion (blinking cursor)
18. Write following command line: cd /media/disk/
19. Press enter
20. Write following command line: sudo tar xzvf ext4.tar.gz -C /media/disk
21. Press enter. Start files decompressing on partition ext4. Wait for operation completion (blinking cursor)
22. Write following command line: sudo rm ext4.tar.gz
23. Press enter.
24. Write following command line: sudo chmod 777 /media/disk/
25. Click on "Virtual machine / Removable devices / Disconnect" to disconnect and reconnect phone automatically from Ubuntu to Windows (do not disconnect USB cable!!!!)
26. Copy files "haret.exe", "startup.txt" and "zImage" in DISK. (ie the root of "Memory personal" WinMobile).
These files MUST remain in DISK (ie the root of the "My Storage" WinMobile). Disconnect device from Pc
27. From WinMobile, with a File Manager, navigate to "haret.exe" and click on it to start Android.
28. After the first launch of Android, DO NOT USE TELEPHONE, wait for the S.O. it is fully started and RESTART phone
At the end of the second boot you can enjoy Android on OMNIAII
Link for download ROM -----------------------------------------------------------------> POST 7
Ubuntu installation method
DOWNLOAD
File ext4.tar.gz
reserved
Congratulations !!!
Yes, you finally made it. version2 is much better that version 1. almost no bugs. And it is much faster than frenkiedroid. especially your memory performance is excellent. i will install it and try to make it even more faster !!!!
one question. how to activate front camera ? i haven't managed to do it.
spkraul said:
Yes, you finally made it. version2 is much better that version 1. almost no bugs. And it is much faster than frenkiedroid. especially your memory performance is excellent. i will install it and try to make it even more faster !!!!
one question. how to activate front camera ? i haven't managed to do it.
Click to expand...
Click to collapse
Thanks!
It will be appreciated your suggestions about how make it even more faster...
About front camera no news for now: it will be necessary kernel modification...
spiderman1961 said:
Thanks!
It will be appreciated your suggestions about how make it even more faster...
About front camera no news for now: it will be necessary kernel modification...
Click to expand...
Click to collapse
You wrote
"Both Cameras and VideoCameras working"
so i thought you meant back and front camera....
ok my suggestions are
check my ROM's build.prop for code optimizations
also experiment with dalvik cache settings. it can make the ROM a lot faster
remove some services always running (ex is voice dialer that very few people use and makes system slower
remove unnecessary apps (example livewallpapers, geniewidget etc)
you can also set cpu performance settings as default without big loss on battery time, but with big affect on phone's responsiveness
remove some files on the system that make it heavier to load and handle (ex fewer ringtones to choose from ....)
uninstall downloaded apps from manage applications manu, clean /data/dalvik cache using root explorer, reboot system and install downloaded apps again
my recommendation is not to install optional apps on system as many users ignore how to erase them when they do not need them (ex if somebody does not use twitter or facebook doesn't need them
for faster gps i have discovered this solution try it and tell me the results
the biggest improvement you can see is by replacing the phone's framework with miui's one. you can find miui based on CM6. i know it looks a little chindish but very fast. you just port it to our ROM, and since working just keep it's engine (heart) and replace it's apps with the ones we prefer. MIUI gives us the fastest bases on android
to measure if your ROM improvements are working or not use antutu benchmark 2.5 (bugless working on my android 2.2.2), antutu cpu master 2.5.2 and benchmark and tuning from android market
bytheway. with my ROM installed on sd class 10 i got 1035 points on antutu. can you check yours to see if we have a new record and post the result ?
if you think i can help in anything specific just send me a pm or post here. we are all working on the same side to improve our phone
spkraul said:
You wrote "Both Cameras and VideoCameras working"so i thought you meant back and front camera....
Click to expand...
Click to collapse
No both apps cameras: many users denoted issues about one of them
spkraul said:
check my ROM's build.prop for code optimizations
also experiment with dalvik cache settings. it can make the ROM a lot faster
Click to expand...
Click to collapse
These suggestion and other are already inserted
spkraul said:
[*]remove some services always running (ex is voice dialer that very few people use and makes system slower
[*]remove unnecessary apps (example livewallpapers, geniewidget etc)
[*]you can also set cpu performance settings as default without big loss on battery time, but with big affect on phone's responsiveness
[*]remove some files on the system that make it heavier to load and handle (ex fewer ringtones to choose from ....)
Click to expand...
Click to collapse
Many, many users in my country want them and want better battery drain; so if other user want different configuration he can change himself.
They can use Titanium Backup or Link2SD.
However scripts in rom block automatic boot of these apps so they don't affect phone's responsiveness
spkraul said:
[*]uninstall downloaded apps from manage applications manu, clean /data/dalvik cache using root explorer, reboot system and install downloaded apps again
Click to expand...
Click to collapse
With terminal command "su" and "sclean" it's all automatic
spkraul said:
[*]my recommendation is not to install optional apps on system as many users ignore how to erase them when they do not need them (ex if somebody does not use twitter or facebook doesn't need them
Click to expand...
Click to collapse
We can do it
spkraul said:
[*]for faster gps i have discovered this solution try it and tell me the results
Click to expand...
Click to collapse
I read your efforts in many posts: in Twister it is not necessary (at least in my country) any modification for GPS: first fix with moving car about 4-5 minutes, second and other fixes 10 sec maximum
spkraul said:
[*]the biggest improvement you can see is by replacing the phone's framework with miui's one. you can find miui based on CM6. i know it looks a little chindish but very fast. you just port it to our ROM, and since working just keep it's engine (heart) and replace it's apps with the ones we prefer. MIUI gives us the fastest bases on android
Click to expand...
Click to collapse
Ok, can you link me something also in pm?
spkraul said:
[*]to measure if your ROM improvements are working or not use antutu benchmark 2.5 (bugless working on my android 2.2.2), antutu cpu master 2.5.2 and benchmark and tuning from android market
Click to expand...
Click to collapse
spkraul said:
bytheway. with my ROM installed on sd class 10 i got 1035 points on antutu. can you check yours to see if we have a new record and post the result ?
Click to expand...
Click to collapse
I agree with many developers that antutu it is not reliable: however score with antutu is 1033
Little curiosity: are you "argentinos" on modaco?
yes i am modaco's argentinos. i just had chosen different nickname here, but nothing to hide
about antutu maybe it is not the most accurate in the world, but it is one of the very few running on android 2.2. Vellamo, quadrant, geekbench etc demand android 2.3 or better or better gpu. But benchmarks are one of the best tools to measure ROMS speed, compare them and improve them. after all i haven't used cheats to achieve my 1035 score and you also the same for 1033 score. so since we are not cheating antutu it can show us quite reliable results.
About gps. standalone settings are nice for people using GPS very often. for people using it rarely maybe they need to wait 4-5 minutes every time. i had experienced this many times with both wm system and android system and this is why i decided to try and find ms-based settings.
but even with your standalone settings try to change accuracy from 50 to 19 and disable dynamic accuracy (samsung's recommended for i8000 chipset) and i believe you will see improvement on the locking times.
About MIUI based on CM6 download from here
http://www.mediafire.com/download/0q9ljaqmw0lyati/Miui_1.3.18v4_Formel-Cobrato.zip
consult here (but some info on CM7 based MIUI)
http://forum.xda-developers.com/showthread.php?t=1041524
http://forum.samdroid.net/f63/rom-miui-gb-6342/
http://forum.samdroid.net/f62/rom-miui-gb-6349/
p.s. if you have free time please check this thread
http://www.modaco.com/topic/363230-android-rom-needed-for-base/
after cm6 for i8000 will be considered complete and not beta and we are very close to name a version "complete" this can be our next step - project CM7 for i8000. if one person made incomplete CM7 to run on i8000 we can improve it and run better
spkraul said:
yes i am modaco's argentinos. i just had chosen different nickname here, but nothing to hide
about antutu maybe it is not the most accurate in the world, but it is one of the very few running on android 2.2. Vellamo, quadrant, geekbench etc demand android 2.3 or better or better gpu. But benchmarks are one of the best tools to measure ROMS speed, compare them and improve them. after all i haven't used cheats to achieve my 1035 score and you also the same for 1033 score. so since we are not cheating antutu it can show us quite reliable results.
About gps. standalone settings are nice for people using GPS very often. for people using it rarely maybe they need to wait 4-5 minutes every time. i had experienced this many times with both wm system and android system and this is why i decided to try and find ms-based settings.
but even with your standalone settings try to change accuracy from 50 to 19 and disable dynamic accuracy (samsung's recommended for i8000 chipset) and i believe you will see improvement on the locking times.
About MIUI based on CM6 download from here
http://www.mediafire.com/download/0q9ljaqmw0lyati/Miui_1.3.18v4_Formel-Cobrato.zip
consult here (but some info on CM7 based MIUI)
http://forum.xda-developers.com/showthread.php?t=1041524
http://forum.samdroid.net/f63/rom-miui-gb-6342/
http://forum.samdroid.net/f62/rom-miui-gb-6349/
p.s. if you have free time please check this thread
http://www.modaco.com/topic/363230-android-rom-needed-for-base/
after cm6 for i8000 will be considered complete and not beta and we are very close to name a version "complete" this can be our next step - project CM7 for i8000. if one person made incomplete CM7 to run on i8000 we can improve it and run better
Click to expand...
Click to collapse
Thank so much!!!
Very interesting: after my little holidays i will work on these informations and i will answer you. See you soon
Hi, I'm going to try installing this ROM for the Omnia 2. It will be used by my girlfriend so I hope she won't have a hard time using it (I mean bugs or some things not working)
First of all I want to thank you gusy for developing for this phone, it is a good phone but with a wrong OS.
Now I have a couple of questions:
1. There is no other way than to install Ubuntu and using it for the specified steps?
2. Could you please post the exact size of the files inside the 7zip files? I don't want to have any errors during the installation. I have attached a screenshot of the files that I got after I unzipped the 2 7zip files, please check it out and tell me if that's ok.
Thank you again!
sergio_sos said:
Hi, I'm going to try installing this ROM for the Omnia 2. It will be used by my girlfriend so I hope she won't have a hard time using it (I mean bugs or some things not working)
First of all I want to thank you gusy for developing for this phone, it is a good phone but with a wrong OS.
Now I have a couple of questions:
1. There is no other way than to install Ubuntu and using it for the specified steps?
2. Could you please post the exact size of the files inside the 7zip files? I don't want to have any errors during the installation. I have attached a screenshot of the files that I got after I unzipped the 2 7zip files, please check it out and tell me if that's ok.
Thank you again!
Click to expand...
Click to collapse
Hi,
you may not use Ubuntu, but the system would be slower and could create some problems (the ext4 file system created by MiniTool is not exactly the same as the one created by native Linux with Ubuntu).
I suggest, with respect to the guide to make a linux swap partition of 250mb (not 200): it should prevent incidents of freeze.
The size of the downloaded files are correct: good installation.
Enjoy
Hola,
no puede usar Ubuntu, pero el sistema sería más lento y puede crear algunos problemas (el sistema de archivos ext4 creado por MiniTool no es exactamente el mismo que el creado por Linux nativa con Ubuntu).
Sugiero, con respecto a la guía para hacer una partición de intercambio de Linux de 250 MB (no 200): debe evitar incidentes de congelación.
El tamaño de los archivos descargados son correctos: buena instalación.
:good:
spiderman1961 said:
Hi,
you may not use Ubuntu, but the system would be slower and could create some problems (the ext4 file system created by MiniTool is not exactly the same as the one created by native Linux with Ubuntu).
I suggest, with respect to the guide to make a linux swap partition of 250mb (not 200): it should prevent incidents of freeze.
The size of the downloaded files are correct: good installation.
Enjoy
Hola,
no puede usar Ubuntu, pero el sistema sería más lento y puede crear algunos problemas (el sistema de archivos ext4 creado por MiniTool no es exactamente el mismo que el creado por Linux nativa con Ubuntu).
Sugiero, con respecto a la guía para hacer una partición de intercambio de Linux de 250 MB (no 200): debe evitar incidentes de congelación.
El tamaño de los archivos descargados son correctos: buena instalación.
:good:
Click to expand...
Click to collapse
Thank you very much for your response. I will try to install the ROM today (hopefully)
And thank you for the spanish translation. I thought you were from Italy
I am from Argentina.
Saluti!
My phone hangs in "Jumping to Kernel..." what should i do?
eisdrachen said:
My phone hangs in "Jumping to Kernel..." what should i do?
Click to expand...
Click to collapse
Hi,
you posted on 2 thread same question: wich version are you installing?
spiderman1961 said:
Hi,
you posted on 2 thread same question: wich version are you installing?
Click to expand...
Click to collapse
Last time I tried the last Twister on my SGH-i900. Jumping to kernel... On every ROM