Database Info

[ROM](Updated 10-28-10) SouthPaw! Version 2.1 - Final

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.

Multiboot Linux on Infinity tf700 v0.8.3 (project closed)

Hi, Guys
Currently I'm working on preparing Linux boot and rootfs image for tf700 device.
Project is based on Nexus 7 Ubuntu installer, Linaro distribution and Hundsbuah kernel.
Release version 0.8.3
Developers thread is here
Warning!
You can brick your device or loose all your data. I'm not to be held responsible if you damage or brick your device. Please, be careful.
This manual has been prepared for the advanced users. You are an advanced user?
You have linux experience
If there is a problem - you contact support and provide all the necessary information (devices info, steps to reproduce, logs)
Please, change password for ubuntu user at first login. Default password is "ubuntu".
Components:
This system consists of several components:
Installer (v0.8.3)
- is standart Android ZIP update file with Aroma interface.
Features:
Pretty simple touch interface
Installing and usage Linux without a keyboard or dock
Detailed localization of install process (rus, eng)
Any device to install rootfs (usb media, sdcards or internal virtual disk file)
You can skip rootfs preparation and install only bootimage (if dualboot has been replaced by another installation)
Data2sd option supported
Use android /data partition as /home directory for users
Autobackup of old virtual rootfs image file and ubuntu user
Select boot priority - you can select default system to boot (Basic or Linux)
Next release features:
Review of initrd options scheme
Install additional system to directory
Rootfs archive finder search maxdepth 3
Save log into internal memory
{
"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"
}
Bootimage (v0.8.3)
- contains Linux kernel (zImage) and initial ramdisk (initramfs). It is created during installation and stored in a special LNX partition on your device.
Features:
Support of many basic systems - Android (CleanROMv3.x, CleanROMv3.x+Data2SD, CM10.x) and Ubuntu-Touch
Any media booting - you can boot SDcard, microSD or usbdisk
Virtual Disk multiboot - possible to select need virtual disk (up to 9)
Android & Ubuntu-Touch booting - can boot android system init from media or virtual disks
File system checker - before mounting filesystem should be checked by fsck.
Hundsbuah kernel - v2.1 optimized kernel
Next release features:
Support for 4.2 android (CleanROMv4.x)
Run additional system from directory
RootFS archive
- compressed tar archive with root file system of OS. It is unpacked during installation to a prepared ext4 filesystem (in file or media device).
Ubuntu 12.10 (v0.8.0)
Archive contain prepared Ubuntu 12.10 environment with last updates, based on Unity (3d) with Cube Desktop. You can install any software (like lxdm or xfce) to improve desktop performance, but (for now) only Unity will be supported.
Features:
Pad-mode - you can use your device as pad without dock
Keyboard remapping - Special keys is replaced to default (Esc, F1-12, Ins, Print, Break, Del, Home->Alt, Search->Meta4) by evdev keymap.
WiFi - You can connect to internet or lan through wifi
Touchpad 2 fingers scrolling - Move 2 fingers up-down to scrolling. 2 finger tap - is mouse 3rd button.
Touchscreen - Supports right click by touch one finger and click by second finger.
OpenGL ES - 3D, games (eduke32, Jagged Alliance 2) and nice browsing by Chromium
Audio and Video up to 1080p - Use nvgstplayer to HW decoding FullHD video
nvgstplayer --sas="audioconvert ! pulsesink" -i <videofile> - Fullscreen mode
nvgstplayer --svs="nvxvimagesink" --sas="audioconvert ! pulsesink" -i <videofile> - Window mode
Problems:
Unity has some problems with performance and ram eating - this is place for optimizations.
Going to suspend is freezing device
HDMI FullHD is not working (but HD is ok)
Bluetooth not working
Disable speaker if headphones connected
Totem is not support nvidia gstreamer plugins
No flash player - only HTML5
Skype and any proprietary software (we need ARM binary, not x86)
Ubuntu-Touch preview (v0.5.2 2013/03/25)
Features:
Smooth touch interface
WiFi support (fixed)
Frontal Camera
Ubuntu 13.04 - development
First release features:
Packages for specific tf700t and tegra3 components (tf700 ppa)
Wayland + Weston + libhybris optional support
Install Manual:
For now installation is very simple)) No console operations needed!
Requirements:
Access to recovery & zip upgrade
> 3Gb free space in tf700 /sdcard folder or external storage
Process:
Get linux-install-0.8.3.zip (12 Mb), (mirror) MD5: 46e458791d232dafa7df49a7b506beca
Get need rootfs:
Ubuntu: rootfs-ubuntu-12.10-0.8.0.tar.lzma (687 Mb), (mirror) MD5: 6dbf50fe8623ceef3e5771e01ba52938
Ubuntu-Touch preview: rootfs-ubuntu-touch-tf700t-0.5.2_20130325.tar.lzma (444 Mb), (mirror) MD5: d50b7fe310f0feb23729e9f857e5c157
Arch (workdowg): arch linux thread
Copy linux-install-*.zip and rootfs-*.tar.lzma to your SDcard or /sdcard on your tf700
Reboot to recovery mode
Run linux-install-*.zip
Next, next, next ))
Wait, wait...
Done, now you can reboot and see four penguins!
If you have a problem with installation process - please, save install log and attach it to your help request message with good description.
Uninstall:
Really? I feel so sad
To complete uninstall multiboot & linux you need:
Reinstall your Android distributive or kernel part of it (this is replaces bootimage with multiboot)
Remove /data/media/linux directory with linux root file systems
Epilogue:
Currently we have basic linux environment with graphics and internet. For now, Android is more friendly to the user on a Tablet PC, but we can tilt the balance to Ubuntu advantage.
If you have any question about usage - please, post it here.

Really appreciate you effort! Why not post this in the developers forum, where you might get some good inputs from other brainy people like yourself.

rahulunni said:
Really appreciate you effort! Why not post this in the developers forum, where you might get some good inputs from other brainy people like yourself.
Click to expand...
Click to collapse
I would like to prepare this howto (after stabilization and fixing minor bugs) for general users. But thanx for you response - brainy people do not come here?

How does this vary from the other Ubuntu effort? Why not combine resources?
http://forum.xda-developers.com/showthread.php?t=1988170

danger-rat said:
How does this vary from the other Ubuntu effort? Why not combine resources?
http://forum.xda-developers.com/showthread.php?t=1988170
Click to expand...
Click to collapse
That would be great! At the moment I'm trying to run their environment using fastboot and find differences. I already sent message to jaybob413 and we try to combine our resources.

rabits said:
I would like to prepare this howto (after stabilization and fixing minor bugs) for general users. But thanx for you response - brainy people do not come here?
Click to expand...
Click to collapse
I am sure they do. Just that the developers forum seemed more appropriate. Anyway, good luck and will wait for your work to finish!

rabits said:
fastboot boot boot.img
Click to expand...
Click to collapse
Good idea to boot via fastboot, that should save the hassle of permanent reflashing the kernel - however it doesn't work for me, at least with the kernel from the other Ubuntu project.
First try: use a raw kernel+ramdisk image (starting with "ANDROID!"):
Code:
[email protected] ~/android/tf700/ubuntu $ fastboot boot blob.LNX
downloading 'boot.img'...
OKAY [ 2.829s]
booting...
FAILED (remote: ()
finished. total time: 2.830s
Second try: use the complete blob:
Code:
[email protected] ~/android/tf700/ubuntu $ fastboot boot blob
creating boot image...
creating boot image - 6281216 bytes
downloading 'boot.img'...
OKAY [ 7.318s]
booting...
FAILED (remote: ()
finished. total time: 7.319s
Fastboot itself works, because after that I issued "continue" and it booted the installed Android kernel just fine:
Code:
[email protected] ~/android/tf700/ubuntu $ fastboot continue
resuming boot...
OKAY [ 0.000s]
finished. total time: 0.000s
Any idea?
What's also interesting is that last time I flashed stuff with fastboot some weeks ago, "fastboot devices" used to show all "??????" and I had to use the well-known "-i 0xb05" option. Today "fastboot devices" showed a proper serial number and I could omit the option (also tried specifying it anyway, but it did not make any difference). Maybe that was repaired with a recent bootloader.

You typically have to include the device ID in the fastboot command for this device... might be worth a try?
For example:
fastboot -i 0x0B05 flash recovery twrp.blob
Not quite sure what the syntax is to boot an image...

danger-rat said:
You typically have to include the device ID in the fastboot command for this device... might be worth a try?
Click to expand...
Click to collapse
Read my post to the end...

_that said:
Code:
[email protected] ~/android/tf700/ubuntu $ fastboot boot blob.LNX
downloading 'boot.img'...
OKAY [ 2.829s]
booting...
FAILED (remote: ()
finished. total time: 2.830s
Any idea?
Click to expand...
Click to collapse
I see - you use blob. It's wrong - you need to unpack blob (see the blobunpack on this forum). Fastboot can flash only images. Blob - is used from zip and sdcard.

_that said:
Read my post to the end...
Click to expand...
Click to collapse
Yes, sorry, saw that afterwards...

rabits said:
I see - you use blob. It's wrong - you need to unpack blob (see the blobunpack on this forum). Fastboot can flash only images. Blob - is used from zip and sdcard.
Click to expand...
Click to collapse
blob.LNX is actually the output of blobunpack, and it's a boot image starting with the "ANDROID!" magic. As you can see above, I tried both variants and neither worked.

rabits said:
I see - you use blob. It's wrong - you need to unpack blob (see the blobunpack on this forum). Fastboot can flash only images. Blob - is used from zip and sdcard.
Click to expand...
Click to collapse
I believe you can flash blobs - see my earlier post. I'm pretty sure that's how I flashed recovery...

Thank you for your work and this awesome project!! If this becomes stable and usable, I'll be buying the keyboard dock for my Infinity!! Congratulations on your progress thus far, and a big thank you!!! I was just thinking the other day how much I would love to have this capability!! Would give me a Ubuntu system for me to easier work on various Android phones
Sent from my EVO 4G LTE using xda premium

Nothing have ever excited me more than this. Thank you so much for all your work! Im not a big linux programmer, but iv been using it for the better part of my life. If i can help in any way, Im in!

Thanx for your response - now I prepare rootfs for publication and I'll do this in near time.

rabits said:
Thanx for your response - now I prepare rootfs for publication and I'll do this in near time.
Click to expand...
Click to collapse
Awesome!!!!!
Take your time man. We're in no rush and my Infinity will probably never leave me, especially if you get this going!!! Thanks again!!!
Sent from my EVO 4G LTE using xda premium

Looks like you're making good progress

rabits said:
Thanx for your response - now I prepare rootfs for publication and I'll do this in near time.
Click to expand...
Click to collapse
Great news really looking forward to this. :good:

Nice. Its always good to options when it comes operating systems.
Also, is this bloated at all? Because, Ubuntu for non-embedded systems has been very bloated since 11.04 and got worse with 11.10.

[TWEAK][APK][CWM][[Update 2.0.0]] Seeder entropy generator to provide lag reduction

Original Post | CWM
Guys check this out
Best result on Android 4.+
Description
Hey everyone,
So, I was experiencing significant lag as we all do from time to time, and decided I was going to get to the bottom of it.
After tracing and debugging for hours, I discovered the source of 90% of Android's lag. In a word, entropy (or lack thereof).
Google's JVM, like Sun's, reads from /dev/random. For all random data. Yes, the /dev/random that uses a very limited entropy pool.
Random data is used for all kinds of stuff.. UUID generation, session keys, SSL.. when we run out of entropy, the process blocks. That manifests itself as lag. The process cannot continue until the kernel generates more high quality random data.
So, I cross-compiled rngd, and used it to feed /dev/urandom into /dev/random at 1 second intervals.
Result? I have never used an Android device this fast.
It is literally five times faster in many cases. Chrome, maps, and other heavy applications load in about 1/2 a second, and map tiles populate as fast as I can scroll. Task switching is instantaneous. You know how sometimes when you hit the home button, it takes 5-10 seconds for the home screen to repopulate? Yeah. Blocking on read of /dev/random. Problem solved. But don't take my word for it .. give it a shot!
Update!
I've built a very simple Android app that bundles the binary, and starts/stops the service (on boot if selected). I'll be adding more instrumentation, but for now, give it a shot! This APK does not modify /system in any way, so should be perfectly safe.
This is my first userspace Android app, so bear with me!
Note that this APK is actually compatible with all Android versions, and all (armel) devices. It's not at all specific to the Captivate Glide.
Click to expand...
Click to collapse
Quote Original Post link - Click Here
UPDATE: Seeder_v7 is out, as suggested by pepoluan, it now detects for qrngd (built in rngd for Qualcomm Snapdragon-based devices), if it is there, then it will not start as rngd may conflict with it...the rngd binary is also using the latest version (it is turned off when screen is off)...users of previous versions can just flash it over...
INSTALLING
You need init.d support for this!
Download and flash:
http://www.androidfilehost.com/?fid=9390248398092764755
Here is a mirror... http://d-h.st/REX
How to use this script?:
After flashing, launch terminal emulator and type
Code:
su
seeder
You will get a menu like this:
{
"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"
}
NOTE: There will be NO app after flashing! This only installs the necessary binaries and scripts...
For those who cannot install via recovery:
You get a status 0 error -> replace the update-binary in Seeder_v6.zip with one from another zip that works with your device
OR
Use the new installation method!
Instructions:
1. Download Seeder_v7_non-CWM.zip from here:
http://www.androidfilehost.com/?fid=9390248398092764756
2. Extract the zip, you will get a folder named "install"
3. Place the folder in the root of your sdcard (/sdcard)
4. Launch terminal emulator, type:
Code:
su
cd /sdcard/install
sh install.sh
5. Ignore any error messages (those are only warnings, only happens to current users)
6. You are done! The script will auto-delete the "install" folder as it is not required anymore...
Sample output:
UNINSTALLING:
And now for the way to clean up Seeder_7:
Via recovery:
Flash Seeder_v6&7_Uninstall.zip:
http://www.androidfilehost.com/?fid=9390248398092764753
Via terminal:
1. Download Seeder_v6&7_Uninstall_non-CWM.zip:
http://www.androidfilehost.com/?fid=9390248398092764145
2. Extract it to the root of your sdcard (/sdcard), you should get a file named uninstall.sh
3. Launch terminal emulator and type this:
Code:
su
cd /sdcard
sh uninstall.sh
4. You are done! Everything gets cleaned up, including uninstall.sh...
Click to expand...
Click to collapse
Flash now works, you can now type in terminal to turn off/on and also easier remove. Up to u if ud like to try. Note" it may drain battery more" so please do not be going all against tweak. Thanks
FLASH THIS ON GINGERBREAD!?!?!(v1.4.0)
Thanks to Zen Arcade for making a flash for Gingerbread! His Post Here!
I took a look at the original CWM package and made the following changes:
1 - swapped in our update-binary
2 - changed the mount command in edify script (not really needed since system is already mounted in gb voodoo CWM recovery)
3 - removed all mount commands from init.d script (not required since you have to have /system mounted just to read the script)
Here's a link to the CWM flashable: http://d-h.st/Kaq
I'm running this on both my Infuses - no problems noted. At work now so will not have a chance to try with games for a couple more hours at least. Only down side I can note is that the rngd binary is about 1MB in size - a small sacrifice if it does eliminate lag events
Note that this package is for GB, but should work fine for 4.x roms as long as /system is mounted as part of recovery startup. Can someone test on a 4.x (CWM9/10) rom by flashing the zip and then checking /system/etc/init.d for a file named 91RNGD or /system/xbin for rngd? I've already tested on GB and it works fine there.
Thanks bradman for posting this - all credit and thanks to the original devs who posted this.
Click to expand...
Click to collapse

Sorry if this is a n00b question, but if you just install the .apk do you still need to change the permissions or does it take care of it for you?

dginsd said:
Sorry if this is a n00b question, but if you just install the .apk do you still need to change the permissions or does it take care of it for you?
Click to expand...
Click to collapse
Is best to just fix Perm to brr safe, easiest way to do so if you just install the app is to go to recovery/advanced/fix permissions and reboot
Sent from my SGH-I997 using xda premium

I stumbled upon this myself a few days ago and have been looking into it... I can easily implement it into my source builds, but want to see how it reacts first before doing so. And btw bradman... CM10.1 is smooth as **** with nothing needed... but if this makes it even better, then thats good to hear.

Anyone tried this on 2.3.6?

im aware its smooth good job! i was just testing it on infuse and i currently had ur rom so i just gave it a try to confirm it working on infuse

wawaweewa said:
Anyone tried this on 2.3.6?
Click to expand...
Click to collapse
ive heard it works on gingerbread. never tried. try a backup in recovery then flash. if anything goes wrong restore

bradman117 said:
ive heard it works on gingerbread. never tried. try a backup in recovery then flash. if anything goes wrong restore
Click to expand...
Click to collapse
I updated OP so that if flash doesn't work i have download files to manually do

bradman117 said:
ive heard it works on gingerbread. never tried. try a backup in recovery then flash. if anything goes wrong restore
Click to expand...
Click to collapse
that is what i am doing now! im on saurom jvu atm thanks for the quick reply ill let you know how it turns out
EDIT: i hope it works so my online game will run smoothly!

I must say, this relatively minor tweak provides a noticeable boost. I'm currently using Liquid Smooth RC9.11 with no further tweaks. After applying this tweak I've noticed faster loading times for a couple games, Google maps is much more responsive to massive view changes, web browsing is snappier, and as stated above almost no redraw delay when returning to the launcher after running a large app (like a game). I must say this under-powered and under-RAMmed little Infuse just keeps getting better and better thanks to all the work the devs here. Keep up the good work!

deathblade said:
Is best to just fix Perm to brr safe, easiest way to do so if you just install the app is to go to recovery/advanced/fix permissions and reboot
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
Thanks for the tip

dginsd said:
Thanks for the tip
Click to expand...
Click to collapse
so i just have to flash the zip in recovery then fix permission and that's it?

just flash it will do permission

Working CWM Flashable for Infuse GB
I took a look at the original CWM package and made the following changes:
1 - swapped in our update-binary
2 - changed the mount command in edify script (not really needed since system is already mounted in gb voodoo CWM recovery)
3 - removed all mount commands from init.d script (not required since you have to have /system mounted just to read the script)
Here's a link to the CWM flashable: http://d-h.st/Kaq
I'm running this on both my Infuses - no problems noted. At work now so will not have a chance to try with games for a couple more hours at least. Only down side I can note is that the rngd binary is about 1MB in size - a small sacrifice if it does eliminate lag events
Note that this package is for GB, but should work fine for 4.x roms as long as /system is mounted as part of recovery startup. Can someone test on a 4.x (CWM9/10) rom by flashing the zip and then checking /system/etc/init.d for a file named 91RNGD or /system/xbin for rngd? I've already tested on GB and it works fine there.
Thanks bradman for posting this - all credit and thanks to the original devs who posted this.
UPDATE - 2012/01/03
I've confirmed the documented improvement in speed at which Maps re-tiles the map display when making big location changes. Still testing other apps. Some games appear a big less laggy, although some disruptive lag events still occur (I suspect due to file system i/o scheduler delays rather than from lack of random/entropy data as addressed with this enhancement). I'll do some benchmarking over the weekend and report back with results.

Zen Arcade said:
I took a look at the original CWM package and made the following changes:
1 - swapped in our update-binary
2 - changed the mount command in edify script (not really needed since system is already mounted in gb voodoo CWM recovery)
3 - removed all mount commands from init.d script (not required since you have to have /system mounted just to read the script)
Here's a link to the CWM flashable: http://d-h.st/Kaq
I'm running this on both my Infuses - no problems noted. At work now so will not have a chance to try with games for a couple more hours at least. Only down side I can note is that the rngd binary is about 1MB in size - a small sacrifice if it does eliminate lag events
Note that this package is for GB, but should work fine for 4.x roms as long as /system is mounted as part of recovery startup. Can someone test by flashing the zip and then checking /system/etc/init.d for a file named 91RNGD or /system/xbin for rngd?
Click to expand...
Click to collapse
I currently cant test this but if it turns out to work ill put it on OP. i did hear from someone that the biggest difference on GB but i cant say that for y self because i have not tried yet

I gotta say, it's very smooth so far.

Works fine on Scott's CM10. PS shows the rngd process running. Thanks
Zen Arcade said:
Note that this package is for GB, but should work fine for 4.x roms as long as /system is mounted as part of recovery startup. Can someone test on a 4.x (CWM9/10) rom by flashing the zip and then checking /system/etc/init.d for a file named 91RNGD or /system/xbin for rngd? I've already tested on GB and it works fine there.
Thanks bradman for posting this - all credit and thanks to the original devs who posted this.
Click to expand...
Click to collapse
Sent from my SGH-I997 using xda premium

Heyyy Scott, check out this guys find
lordvincent 90 posted it..
Originally Posted by zeppelinrox
So I did a bit of digging and a bit of research and a bit of testing.
I really dunno if the tweak makes that big of an effect but I did discover a nice trick to have a nice fat entropy_avail with zero overhead.
One of the first pages I skimmed was http://linux.die.net/man/4/random which mentioned at the bottom these other files:
read_wakeup_threshold contains the number of bits of entropy required for waking up processes that sleep waiting for entropy from /dev/random.
write_wakeup_threshold contains the number of bits of entropy below which we wake up processes that do a select() or poll() for write access to /dev/random.
Normally, read_wakeup_threshold is 64 and write_wakeup_threshold is 128
I also wondered why most users report that their entropy_avail was by default in the 200ish range while mine was always by default over 300.
I had also found this page at linuxinsight. I had used that site alot when researching Kick Ass Kernelizer's sysctl tweaks.
So I thought, hey I wonder if I can use sysctl to set good values and low and behold, I looked in my script and I already have settings for both lol:
Code:
busybox sysctl -e -w kernel.random.read_wakeup_threshold=128;
busybox sysctl -e -w kernel.random.write_wakeup_threshold=256;
As you can see, I had doubled the default values - and that's why my entropy_avail was always over 300.
So I decided to mess with sysctl a bit.
Connected the phone to the laptop.
In one command prompt I watched the entropy_avail with this one liner:
Code:
while :; do cat /proc/sys/kernel/random/entropy_avail; sleep 1;done
In a second command prompt I did the sysctl thing...
I found that write_wakeup_threshold didn't effect entropy_avail at all.
But read_wakeup_threshold is a totally different story
I did
Code:
busybox sysctl -w kernel.random.read_wakeup_threshold=2048
The entropy_avail just started climbing....
All the way up to 3600+ and just stayed there. Never went down at all.
Actually, the more I did stuff with the phone, the faster the level would climb.
So it would never go down and would never get used.
I thought well maybe I should lower it so it does get used.
I kept lowering read_wakeup_threshold until it got down to 1200 and finally entropy_avail dropped to 2400+ and kept climbing until 3600 and then would drop to 2400 immediately and up again and so on...
I played with different values.
Setting it to 1000... entropy would go up to 3000 and then drop to 2000 and up to 3000 again....
Setting to 750.... entropy would go up to 2250 and drop to 1500 and up to 2250 again...
So the pattern is:
max entropy_avail=read_wakeup_threshold * 3
min. entropy_avail=read_wakeup_threshold * 2 (ie. read_wakeup_threshold * 3 - read_wakeup_threshold)
So it builds up 3 times the read_wakeup_threshold and then when it hits that limit, it drops the value of read_wakeup_threshold.
If you want to lock it it at the highest possible value (4096), you'd do:
Code:
echo 1366 > /proc/sys/kernel/random/read_wakeup_threshold
Or
Code:
busybox sysctl -w kernel.random.read_wakeup_threshold=1366
You can add either of those to any init.d script.
However, on my device, it won't go over 3600 so you can test for yourself how high yours will go.
If all you can get is 3600ish just go with 1200 (ie. 3600/3)
In Kick Ass Kernelizer I'm gonna make it like so:
Code:
busybox sysctl -e -w kernel.random.read_wakeup_threshold=1024;
busybox sysctl -e -w kernel.random.write_wakeup_threshold=2048;
That will make it bounce between 3072 max and 2048 min.
I'm making write_wakeup_threshold twice the amount of read_wakeup_threshold simply because that's what it is by default.
But hey, maybe I can save battery life if I make it 1280 just so it stays locked in at 3600+ and it doesn't have to keep rebuilding entropy_avail lol
So conclusion is: since there is a definite pattern on how entropy was being built up to a pre-determined level and dropped to a pre-determined level, it wasn't actually being used. That's just how it's programmed.
If the setting isn't there to "hold" all the entropy, it just drops/flushes it and force feeding it entropy won't make it not spit it out
So at least I found the setting that will make it hold it in lol
Maybe somebody would like to give it a try and test to see if it actually saves battery by setting read_wakeup_threshold to 1366.
Click to expand...
Click to collapse
lordvincent 90 posted it..
Just adding this, after reading the whole thread here it seems like this may be a simpler solution (and better on battery life)
Click to expand...
Click to collapse
Post Link -- http://forum.xda-developers.com/showpost.php?p=36208713&postcount=32

Zen Arcade said:
I took a look at the original CWM package and made the following changes:
1 - swapped in our update-binary
2 - changed the mount command in edify script (not really needed since system is already mounted in gb voodoo CWM recovery)
3 - removed all mount commands from init.d script (not required since you have to have /system mounted just to read the script)
Here's a link to the CWM flashable: http://d-h.st/Kaq
I'm running this on both my Infuses - no problems noted. At work now so will not have a chance to try with games for a couple more hours at least. Only down side I can note is that the rngd binary is about 1MB in size - a small sacrifice if it does eliminate lag events
Note that this package is for GB, but should work fine for 4.x roms as long as /system is mounted as part of recovery startup. Can someone test on a 4.x (CWM9/10) rom by flashing the zip and then checking /system/etc/init.d for a file named 91RNGD or /system/xbin for rngd? I've already tested on GB and it works fine there.
Thanks bradman for posting this - all credit and thanks to the original devs who posted this.
Click to expand...
Click to collapse
Anyone tried this?
Btw brad im on jvu saurom and flashed it fix permission but this is what i get

Tweak
This relatively minor tweak provides a noticeable boost. I'm currently using Liquid Smooth RC9.11 with no further tweaks. After applying this tweak I've noticed faster loading times for a couple games, Google maps is much more responsive to massive view changes, web browsing is snappier, and as stated above almost no redraw delay when returning to the launcher after running a large app (like a game). I must say this under-powered and under-RAMmed little Infuse just keeps getting better and better thanks to all the work the devs here. Keep up the good work!
BR

[ Q&A Troubleshooting ] Dirty Unicorns 4.4.4 [Falcon]

[SIZE=+2]This thread has been created
for
• Questions • Answers • Troubleshooting •[/SIZE]​
[SIZE=+2]Dealing with ► Dirty Unicorns ◄ ► Moto G Falcon ◄[/SIZE]
[SIZE=+2]Please feel free to share issues, questions and offer help[/SIZE]
{
"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"
}
[SIZE="+2"]
>> [ROM] [OFFICIAL] Thread: >> Link Here <<[/SIZE]
.
[SIZE=+2]Please Do not clutter the Development thread with non related development chatter[/SIZE]
[SIZE=+2]
Please read the OP in dev thread carefully, it has some very important info in it.[/SIZE]
​
[SIZE="+1"]Please keep discussion focused, on the topic described in the OP[/SIZE]
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------​

[SIZE=+3]
Please provide ► exact Version and Date ◄ of ROM
Please provide ► exact Version and Date ◄ of Recovery
Please provide ► exact Version and Date ◄ of Kernel
[/SIZE]​
Repost:::
[SIZE="+2"]How to report bugs, the proper way ![/SIZE]
http://therealmofu.com/wp/?p=644
Credit:: by TheRealMofu
Credits:
Indirect for his guide
FuzzyMeep Two for his Windows Logcat Tool
[SIZE="+2"]
Connecting your device through adb on Windows/Ubuntu:[/SIZE]​
▼▼▼▼▼▼▼▼▼▼▼▼▼▼▼▼▼▼▼▼
[SIZE="+1"]Windows:[/SIZE]
On your PC you need to be logged in as an administrator for doin this and make sure that you activated “USB Debugging” in Settings/Developer Options on your phone !!!
Connect your phone with the USB cable to the PC and select MTP mode
Open the Windows command prompt, which you also can open through pressing Win + R on your keyboard
Now type:
Code:
cmd
Now change into the folder you installed adb, for example:
cd c:\adb
Now were we are in the correct folder, type:
Code:
adb
Now you see a lot of commands appering, and when done, type:
Code:
adb devices
and your phone (Device-ID) should be listed in there, that’s it
[SIZE="+1"]Ubuntu:[/SIZE]
Make sure that you activated “USB Debugging” in Settings/Developer Options on your phone !!!
Connect your phone with the USB cable to the PC and select MTP mode
In terminal type:
Code:
cd (TOOLS_PATH)/android-tools
Then issue the following:
Code:
./adb devices
That’s it
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------​
[SIZE="+2"]These are the options for reporting a bug:[/SIZE]​
▼▼▼▼▼▼▼▼▼▼▼▼▼▼▼▼▼▼▼▼
[SIZE="+1"]Section 1 | Logcat:[/SIZE]
This log should almost always be included just because it provides more info than just saying something doesn’t work. It will essentially tell you which apps are crashing and why and it also gives output of what they’re doing. (Your system is running through apps, the dialer, wireless radio’s, etc are all ran through apps.) so, if something is general, like a system force close, please just include a logcat.
How to get a logcat:
Well, this is REALLY simple, all you need to do is just get adb up and running (google how to do that, I don’t feel like writing a ‘how to use adb’ tutorial for everyone’s phone.) and then type
Code:
adb logcat
then you just right click, select, and paste to
http://pastebin.com/
http://logcat.us/
http://paste.ubuntu.com/
and provide the link in the thread/post.
It’s really that simple!
For Windows users i found an self explaining noob friendly program called Windows Logcat tool 4.0
[SIZE="+1"]Section 2 | Dmesg:[/SIZE]
This is getting into issues such as wifi not working, sleep of death, etc. Basically, things that make us go “OH F***” when we use our devices. Note: You will need adb access for this to work, same as logcat.
What this will do is get us live kernel output so we can know things like “What driver is the kernel loading {or not loading for that matter}” and similar things. This is linux, so kernel output is important if a hardware aspect isn’t working right.
How to get a dmesg:
This is simple as well, no matter what operating system you’re on (mac, windows, linux) just type
Code:
adb shell dmesg > dmesg.txt
and then it will have written the output to a .txt file in your current directory. Either paste the contents to the thread, or attach it to your post.
You can also get the dmesg by using terminal emulator. Instead though, you dont type adb shell, you need to also include it to somewhere you will be able to save it. Like /sdcard so, the command goes
Code:
dmesg > /sdcard/dmesg.txt
Just get it off your sdcard and get the contents to the developer!
[SIZE="+1"]Section 3 | last_kmsg:[/SIZE]
Ok, the last thing is last_kmsg. When android kernels crash, they right to last_kmsg so then you can find out what’s going on. This is usually for issues such as random reboots and other various kernel panic symptoms. A kernel panic happens when the kernel tries to do something it can’t. It doesn’t mean wrong permissions, it could just have errored out on something and died which can cause a few things. Anyway, developers REALLY need this if debugging a kernel because it gives us a viable way to see WHAT it’s trying to do instead of trying to guess what it is trying to do
How to get a last_kmsg:
This is super simple and the same on all phones no matter what, what you need is adb up and running (or terminal emulator) and either in adb shell, or terminal emulator just type
Code:
cat /proc/last_kmsg > /sdcard/last_kmsg.txt
or you can do
Code:
adb shell cat /proc/last_kmsg > kmsg.txt
and that will write it to your current working directory from cmd.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------​
[SIZE="+2"]Here is another great instruction tutorial link:[/SIZE]
[SIZE="+2"][WIN][TUTORIAL]HOW TO USE ADB,DDMS AND TAKE A LOGCAT {pictorial explanation} [/SIZE]
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------​

It's been noticed that sometimes during the install of this it will take a long time to flash.
Just be aware of this known issue
It happens during the format /system of the device
it happens even on the current newest TWRP 2.8.0.1 or twrp-2.8.0.1-xt1032.zip
and sometimes it even happens if you have manually formatted /system in advanced mode
Normal install time ranges from :30 seconds to 1:00 Minute
longer times have ranged with older TWRP recoveries or CWM or Phil's anywhere from 3:00 minutes to 10:00 Minutes
TeamMex has reported that is is most likely an updater-binary issue
reversegear has tested and posted a workaround for those wishing to mod their copy of the ROM
or you can choose to wait out the extra time needed to install this awesome ROM.

one more to hold

Just wanted to say THANK YOU @hhp_211 for creating this thread so that the development thread could possibly level out and get back to where it original was headed

I get the first question. I finally decided to try this out. I'm using the latest official version of CWM; 6.0.4.7 touch. I can report that it did take maybe 5 min to flash the ROM from start to finish. After the first boot, i rebooted to recovery and I then flashed the GAPPs, DU_TBO_GAPPS. I noticed that upon reboot, and signing into my Google account, that the ROM didn't automagically start downloading all my apps from the play store. Is there a setting that I needed to have set?
I went ahead and restored my backup for the time being. The ROM looked nice and smooth.
Thank you.
Sent from my XT1034 using Tapatalk

alfick3 said:
I get the first question. I finally decided to try this out. I'm using the latest official version of CWM; 6.0.4.7 touch. I can report that it did take maybe 5 min to flash the ROM from start to finish. After the first boot, i rebooted to recovery and I then flashed the GAPPs, DU_TBO_GAPPS. I noticed that upon reboot, and signing into my Google account, that the ROM didn't automagically start downloading all my apps from the play store. Is there a setting that I needed to have set?
I went ahead and restored my backup for the time being. The ROM looked nice and smooth.
Thank you.
Sent from my XT1034 using Tapatalk
Click to expand...
Click to collapse
I believe that is a modded apk to be that way
to change go to
Play Store::Settings::Auto-update apps::
and choose your preferred method

@hhp_211, thanks. I didn't think about going into the play store and looking at the settings. I'm used to other GAPPs packages where it just automatically installs my apps from previous ROMs or phones.
Sent from my XT1034 using Tapatalk

I re-installed today, after flashing the latest TWRP (2.8.0.1). I wiped system, data, cache and dalvik cache. I did not wipe my internal SD card. This time I flashed the ROM, then flashed the GAPPs right away instead of booting into the ROM first. Upon reboot, it asked me to sign into my Google account, and then automagically started to download my apps. So far, so good; although it's constantly giving me a "Unfortunately, OmniSwitch has stopped". After all my apps have downloaded, I'll do a reboot and see.

Is it possible to have FM radio app? Zip? Or it is completely unsupported? I'd rather not to buy a third party app.
Thanks in advance

i have a problem with the BACK soft button in landscape, whenever i press it (and in landscape) it goes to "google now"
i dont know what causes this issue right now (it may be the Recents bttn ... i use inverted bttns)
The problem seems to be that the part avobe of the "home" button black part is for some reason usable??
its kind of wierd but right now i cant go "Back" in landscape because it goes to google now !
im on dirty 8.0 the last one Stock

Mao_anguita said:
i have a problem with the BACK soft button in landscape, whenever i press it (and in landscape) it goes to "google now"
i dont know what causes this issue right now (it may be the Recents bttn ... i use inverted bttns)
The problem seems to be that the part avobe of the "home" button black part is for some reason usable??
its kind of wierd but right now i cant go "Back" in landscape because it goes to google now !
im on dirty 8.0 the last one Stock
Click to expand...
Click to collapse
I'd say grab a Logcat
Maybe also include some screenshots of your layout in landscape
I'm still on the test 8.0 and back works OK,, but i also don't use Google now
.

[v1.2] Linux for Samsung Galaxy J120F

This thread is about Linux port for J120F. Test build is currently in beta state. But if you're a Linux user you can try it.
Status:
Display and touchscreen work
Hardware and software keyboards work
Wi-Fi works (and Firefox onboard )
USB works as OTG or serial gadget with a console (115200n8). UART JIG also works
Bluetooth. You can run hciattach (@115200) to get BT device but most tools don't see it
Known issues:
Touchscreen won't work if phone was started by attaching USB or charger. That's because Android can't start this way (phone shows battery status and goes off).
For same time after boot you can't click anything but cursor moves. Just wait ~30 sec.
This will be fixed in v1.3. Or you can execute:
Code:
rpm -ev --nodeps xinput-calibrator
Fixed:
Onscreen keyboard doesn't work. Sad but true
"Connect to Wi-Fi" button is out of screen. It's next to "DHCP" combobox in TAB order.
Display goes to sleep and can't be turned back on. You can restart X from SSH or USB console to turn it on again. (No timeout - no bug )
How to install:
Create 3 partitions on SD card. 1st is FAT for your Android data. 2nd for Link2SD (make it tiny if not needed). 3rd is ext2 for Linux (500 MB should be enough for now).
Extract rootfs.tar.xz contents to 3rd partition. It should be done as root and from terminal. GUI tools aren't good for this.
Flash kernel (boot.img) with heimdall. It can work as recovery too. In this case you will get dualboot.
Milestones:
1.0 Make it boot
1.1 Bring up major hardware
1.2 Make ROM easier for testing and building
1.3 Organize included software
My next major tasks:
Improve BSP. Make image recipe.
Make toggle screen on/off feature by power button.
Improve onscreen keyboard layout. Make keys bigger.
Done tasks:
Sort out all the patches I've made to FS. Make a BSP (OpenEmbedded machine layer).
Find a problem with USB serial gadget and make it work as console. For now I use UART JIG but only few people have such hardware.
Get Wi-Fi to work. Smartphone is not a smartphone without internet connectivity.
Make connman-gnome window usable with such small display. Currently you need to do blind TAB to connect to Wi-Fi.
Find a problem with on screen keyboard. The only way to input text now is USB keyboard over OTG.
Improve BSP. Integrate FS patches into it. Fix kernel so it can be built inside OE.
Fix screen timeout bug. (Timeout disabled so far)
Photos:
{
"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"
}
Link to my ROMs folder on MEGA.
Kernel source on GitHub.
OpenEmbedded Layer (BSP) source on GitHub.

Wi-Fi works!
dmesg from Android helped me to start Wi-Fi. To finish initialization you need to run
Code:
cat /proc/deferred_initcalls
Seriously!

Good news!
SSH is working over Wi-Fi.
USB gadget works after all!
To activate it do:
Code:
echo connect > /sys/class/udc/13580000.usb/soft_connect
Now I will try to make a build with all those things activated on boot

Version 1.1 released. It's MUCH more user-friendly but you still need some skills to install and use it.

It's possible to do this on Galaxy J120H?

jlfedmmc456 said:
It's possible to do this on Galaxy J120H?
Click to expand...
Click to collapse
OS image should start on J120H but you need a special kernel. So there are two answers on two kinds of questions:
1) No. This is impossible to [just] install kernel and OS from J120F to J120H because of different hardware.
2) Yes. This is possible to port this project to J120H. It's easy if you're ROM maker.

Good job. Thank you for this ROM.

Set up both keyboards.
To activate software one:
/etc/X11/Xsession.d/80matchboxkeyboard.sh
Code:
#!/bin/sh
. /etc/formfactor/config
CMD="matchbox-keyboard -d"
if [ "$CMD" ]; then
# Delay to make sure the window manager is active
# by waiting for the desktop to say its finished loading
dbus-wait org.matchbox_project.desktop Loaded && $CMD &
fi
To activate hardware one you need new kernel. It is on MEGA already (linux_1_2_boot.img).
Buttons:
RECENT -> Context menu
HOME -> My Computer
BACK -> Esc
Power and Vol keys are Power and Vol keys
To make HOME work as "show desktop" button add:
Code:
XF86MyComputer=desktop
to kbdconfig file.
That's all for now

Fixed Samsung kernel. Now it builds inside OE.
IIRC bitbake should be able now to build OS image without any "tricks".

BSP v1.2
Made proto BSP in a form of diffs. Changes are listed in fs_files.diff file. New files are in files folder. Patches are in diffs folder. New packages are in rpms folder.

Hey really great work; I have created 2 forks of your project for J120A here in the states... I haven't used bitbake before. I went and installed it, but not sure how to use it with the 2 projects you've uploaded. I tried "bitbake J120A" and "bitbake world" but that doesn't seem to be the thing to do. Can't seem to build the kernel manually with "make" either. Could you tell me what commands/config I need to do with bitbake to get this working? Thanks again for your hard work!

puargs said:
Hey really great work; I have created 2 forks of your project for J120A here in the states... I haven't used bitbake before. I went and installed it, but not sure how to use it with the 2 projects you've uploaded. I tried "bitbake J120A" and "bitbake world" but that doesn't seem to be the thing to do. Can't seem to build the kernel manually with "make" either. Could you tell me what commands/config I need to do with bitbake to get this working? Thanks again for your hard work!
Click to expand...
Click to collapse
You don't need bitbake. You need OpenEmbedded.
https://www.openembedded.org/wiki/Getting_started
https://www.openembedded.org/wiki/OE-Core_Standalone_Setup
Then add some layers. I have:
meta (oe-core)
meta-oe
meta-multimedia
meta-networking
meta-filesystems
meta-gnome
meta-initramfs
meta-perl
meta-python
meta-webserver
meta-xfce
meta-browser
meta-j120f
Setup a MACHINE to build for.
Code:
MACHINE ?= "j120f"
And allow non-free licenses
Code:
LICENSE_FLAGS_WHITELIST += "commercial"
Now you can try to build "core-image-sato". OE needs huge amount of free space and time to build! (~100GB)
You can also build packages: bitbake firefox
I doubt that F kernel will run on A version. So you need to port all my patches to the Samsung kernel source for J120A. It shouldn't be hard.
Then diff my linux defconfig with original one (for j120f) and add those changes to your (j120a) defconfig.
After that unpack stock boot.img for your device. And pack your zImage with original DT file.
This is how I do this:
Code:
android_img_repack_tools/mkbootimg --kernel zImage --ramdisk NONE --dt boot.img-dt --base 10000000 --pagesize 2048 --board SRPOI21A000RU -o new_boot.img
Now you can flash new_boot.img with heimdall
Code:
heimdall flash --BOOT new_boot.img
I think you should start with kernel. Patch, build, pack img and flash it. (Don't forget to unlock bootloader first!) Then you can install my OS build on SD card (replace /etc/wifi and /lib/firmware with your files). I hope v1.2 will be released already. And if it works you can start to build your own OS image

This is really great information, thank you so much for the assistance! I have gone through and started work on what you mention, but I realized I'm not sure which Kernel you originally downloaded for your device. There are a lot available for the J120F:
https://imgur.com/a/OeI9u
Do you remember which one you started with? It will make filtering down the diff a lot easier.
-W_O_L_F- said:
You don't need bitbake. You need OpenEmbedded.
https://www.openembedded.org/wiki/Getting_started
https://www.openembedded.org/wiki/OE-Core_Standalone_Setup
Then add some layers. I have:
meta (oe-core)
meta-oe
meta-multimedia
meta-networking
meta-filesystems
meta-gnome
meta-initramfs
meta-perl
meta-python
meta-webserver
meta-xfce
meta-browser
meta-j120f
Setup a MACHINE to build for.
Code:
MACHINE ?= "j120f"
And allow non-free licenses
Code:
LICENSE_FLAGS_WHITELIST += "commercial"
Now you can try to build "core-image-sato". OE needs huge amount of free space and time to build! (~100GB)
You can also build packages: bitbake firefox
I doubt that F kernel will run on A version. So you need to port all my patches to the Samsung kernel source for J120A. It shouldn't be hard.
Then diff my linux defconfig with original one (for j120f) and add those changes to your (j120a) defconfig.
After that unpack stock boot.img for your device. And pack your zImage with original DT file.
This is how I do this:
Code:
android_img_repack_tools/mkbootimg --kernel zImage --ramdisk NONE --dt boot.img-dt --base 10000000 --pagesize 2048 --board SRPOI21A000RU -o new_boot.img
Now you can flash new_boot.img with heimdall
Code:
heimdall flash --BOOT new_boot.img
I think you should start with kernel. Patch, build, pack img and flash it. (Don't forget to unlock bootloader first!) Then you can install my OS build on SD card (replace /etc/wifi and /lib/firmware with your files). I hope v1.2 will be released already. And if it works you can start to build your own OS image
Click to expand...
Click to collapse

puargs said:
This is really great information, thank you so much for the assistance! I have gone through and started work on what you mention, but I realized I'm not sure which Kernel you originally downloaded for your device. There are a lot available for the J120F:
https://imgur.com/a/OeI9u
Do you remember which one you started with? It will make filtering down the diff a lot easier.
Click to expand...
Click to collapse
You don't need to know it. Just take a look at commits: https://github.com/LONELY-WOLF/kernel-j120f/commits/master

Version 1.2 ready
ROM made more user friendly. Most patches are integrated in BSP. It's far more easier to test and build ROM now.
Fixes not included in 1.2:
xinput-calibrator should be removed as it's useless for modern touchscreens
keyboard layout was reworked but I still need to make keys bigger
removed "Ethernet" option from connman-gnome. This fix is available in proto_BSP_1.2 archive
Version 1.3 will be about included packages.
I want to delete and install some packages. Busybox will be replaced first!
BSP will get image recipe.

BSP builds without errors! My Ryzen 1700 (OC to 3800MHz) builds OS image in ~1 hour.

-W_O_L_F- thanks for leading work on a custom kernel and Linux userspace on SM-J120x. Great to see the improvements you've made on top of the vendor kernel to make it easier for developers to test (e.g. packaged boot.img, and userspace).
puargs: I'd also like to see a version for SM-J120A, however I expect we will be blocked running custom RECOVERY as the SM-J120A ships with a locked bootloader. So far I've been unable to find any bootloader unlock methods for SM-J120A.
Tried flashing linux_1_2_boot.img to RECOVERY with heimdall in "download mode" as a test, with no success.
The download mode recognizes an unexpected RECOVERY image, and reports "SECURE CHECK FAIL : (RECOVERY)" on the device.
Have you had any success? Perhaps you found a method that works?

Wow, this is some serious development going on for the SM-J120F! I'm surprised to see such projects for the Exynos platform.
Keep up the good work and may your project become successful!

Project moved to new hardware: Galaxy Note9.
https://forum.xda-developers.com/ga...linux-porting-native-linux-to-galaxy-t3936077