Daniel Menelkir

Preparing gentoo for building android

2013-01-03T14:40:00.001-02:00

That's right, I see lots of documentation for ubuntu and many other distributions and none exactly for gentoo, and seems I like to work with some crossdev, I'll post instructions for preparing your gentoo for that:

First of all, you need some packages (ok, if you already have some of these, you can skip them):

# emerge -pv git gnupg flex bison gperf libsdl wxGTK squashfs-tools curl ncurses zlib schedtool perl-Switch zip unzip

For 64bits systems, you need a little more

# emerge -pv emul-linux-x86-baselibs emul-linux-x86-compat emul-linux-x86-cpplibs

Note: I don' t know if cpplibs are really necessary, but I'll let here.

Make sure you' re using python 2.x instead of 3.x when you're about to compile

# eselect python list

Available Python interpreters:

[1] python2.7

[2] python3.2 *

# eselect python set 1

Download the repo utility. I'll install in /usr/local/bin, but you can use in ~/bin if you prefer:

# curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > /usr/local/bin/repo

# chmod 777 /usr/local/bin/repo

Now you're able to start syncing the source:

$ mkdir ~/Devel/Android && cd ~/Devel/Android

$ repo init -u https://android.googlesource.com/platform/manifest

$ repo sync

From here you'll know what to do. :)

Another dumb company

2012-07-10T13:16:00.000-03:00

As other companies (not only in Brazil, but in several countries), SMTek seems to not respect GPL. When I ask to Evertek about the kernel source, they said "We do not give this type of information".

Congratulations to all shitty companies that disrespect laws and licenses. Companies of this type (directed by children) must learn a lesson or two, and for fucks sake, disappear from market to dust.

And congratulations to all brazilians that makes this possible, to give your thumbs up for companies like this (isnt the first time I see brazilians giving support for this type of trash). Also, who cares? Since it's simple to read the big difference between brazillians that doesn't even care to read a shit and xda-developers.com for example?

Edit: Now I'm a proud owner of Galaxy Tab 2 7", and with him i'm able to even make my own kernel. That's all

CyanogenMod 9.0 Nightly and AOKP for GT-7200

2012-06-06T12:34:00.002-03:00

I know GT-7200 comes already with ICS, but with my long experience seeing manufacturers bloating the stock rom with unwanted and sometimes system applications you can't install (in fact, you can, but sometimes they're attached to some framework and if you uninstall, you can mess up everything), I search for a custom rom for this tablet.

Updated 2012/06/28 - This procedure now is AOKP Compatible too.

Read this first:

Disregard stupid people saying stupid things without the minimum necessary knowledge to judge, I'll put here some pro and cons to use cm9 instead the stock one:

Pro:
* REAL GOOGLE APPS EXPERIENCE. Because Genesis just cut off part of google apps without any reason (faceunlock and gtalk are good examples). I've tried to figure out how made it work with stock one, without a minimium success. And yes, even video chat in native google talk works. And no, I don't want to use any 3rd party applications, since I only use gtalk and the google one is a very good piece of software compared to the other solutions (memory use, etc).
* Better framework. If genesis provide the DAMN GPLed OPEN SOURCE KERNEL, I was able to tune, help fixing bugs or even more, but no, Genesis doesn't even answer the customers by mail when you ask for it. If you don't know what I'm talking about, read the license of the linux kernel.
* Specific tunings by Cyanogen. And I'm not talking about "overclocking" ANYTHING. You can tune a little, for example, the native governor installed doesn't have a decent scalation, so when you turn off your screen, you still wasting your battery. I have almost 2h more using CM9 than STOCK, if I had the kernel sources of this device, I'll be able to port smartassV2 governor, so will be another story, another performance and another battery life. But as I said before, Genesis doesn't give a fuck to licenses and doesn't even give a fuck to his customers (I've sended 10 mails, a friend of mine have sended 8, none has been answered), and the worse? Doesn't give a fuck to android community AT ALL, he just get the software, put in his devices and you must deal with this. Don't you believe, right? So wait for 4.1 for your device. Coby does exactly the same with his customers.
* ~~Some graphic tunings, because AFAIK Genesis doesn't know his device is 3D capable, cause most of 3D features of this gpu was disabled by default in stock rom~~. The last stock update activates the 3D, thats funny, its the only real update.
* The original ROM is against ALL TYPES of standards. For example: Busybox, AOSP, etc.

Cons:
Maybe you'll be off the official support using this, but you can always turn back using your backup or flashing back a stock rom, so, isn't a con at all.

Btw, you don't need to use if you don't want it, so just stop speaking bullshit when you don't have the little knowledge to know what the fuck you're talking about.

Pre-Requirements:

* You need A10 CWM Recovery (you use that little button for stock recovery to navigate in options and power button to choose one, and remember to nandroid backup)

Howto:

* Boot to CWM recovery (there's many ways to do that, google is your friend)
* Wipe everything
* Install the main cm9 nightlies or AOKP (If you have some problems with the last build, get the 20120607 from here).
* Install Gapps
* Install my patch (updated with lots of fixed 2012/06/28)
* Reboot

Update: If you have some problems and need help, please provide a logcat (it's impossible to understand what is happening without a logcat).

Android tunings

2012-05-29T18:47:00.001-03:00

If you don't know what this means, it's not for you.

/system/build.prop

1. Network

Sometimes you feel your device a little "clumsy" depending your connection. I really don't know why this happens. For example, at home my wifi is ok, but in some others is different (with same routers). Or even worse, some differences from carrier to carrier, and I'm not talking about latency (and don't start talking about android quality of connection because I've already feel the same using an iPad).
Sometimes.. you know.. if you doesn't use a custom rom because you really believe that the manufacturer knows what is the best for your phone, I'm really sorry for you.
This settings will give you a little more latency, you need a little test to see if fits for you.

net.tcp.buffersize.default=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.umts=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.gprs=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.edge=4096,87380,256960,4096,16384,256960

2. Image related

Some manufacturers thinks you like this type of garbage, you can optimize this:
This one give the full quality for jpeg images (yes, sometimes you're not using what your device is capable):

ro.media.enc.jpeg.quality=100

Disable this, unless you like the red borders for strict applications

persist.sys.strictmode.disable=1
Render UI with GPU (yes, sometimes isn't turned on)

debug.sf.hw = 1
Improve the scrolling response

windowsmgr.max_events_per_sec = 120
Disables the surface dithering (if enable will improve image quality, at cpu cost)

persist.sys.use_dithering = 0
Use hardware acceleration to render videos.

video.accelerate.hw=1

3. Battery Related

Do you know about governors right? I you know all manufacturers (including sw ones like google, unfortunately) thinks no one needs a DECENT governor on your device, so your battery will sucks big time.
There's some types of governors for almost all devices that you HUGE increase the battery life without making your device a garbage, like smartassV2, interactiveX and Drewi's ondemand. but… if you don't use a custom rom and thinks that your manufacturer is the god of devices, just stop reading already :D.
You have a custom kernel with a custom governor? Good! Did you use smartassV2? Very good. Now some minor tunings.

Decrease the scan time of the wifi (will not hurt):

wifi.supplicant_scan_interval=150
This will improve the "deep sleep", but depends on kernel in some way

ro.ril.disable.power.collapse=0

Increase battery saving

pm.sleep_mode = 1

/data/local.prop

Based on supercharger script (because not all supercharger script settings are good to everyone, Ive filtered the best compatible options):

Define the OOM adj values for the classes of processes that can be killed by kernel.

ro.FOREGROUND_APP_ADJ=0
ro.VISIBLE_APP_ADJ=3
ro.SECONDARY_SERVER_ADJ=5
ro.BACKUP_APP_ADJ=6
ro.HOME_APP_ADJ=1
ro.HIDDEN_APP_MIN_ADJ=7
ro.CONTENT_PROVIDER_ADJ=8
ro.EMPTY_APP_ADJ=15
Define the memory threesholds at which the above process classes will be killed

ro.FOREGROUND_APP_MEM=1536
ro.VISIBLE_APP_MEM=2048
ro.SECONDARY_SERVER_MEM=6144
ro.BACKUP_APP_MEM=6656
ro.HOME_APP_MEM=1024
ro.HIDDEN_APP_MEM=6656
ro.CONTENT_PROVIDER_MEM=7168
ro.EMPTY_APP_MEM=7680

init.d Scripts

Of course, your ROM must support init.d scripts

/etc/init.d/03kernel

#!/system/bin/sh
#
echo "3" > /proc/sys/vm/drop_caches
echo "20" > /proc/sys/vm/swappiness
echo "15" > /proc/sys/vm/dirty_ratio
echo "70" > /proc/sys/vm/vfs_cache_pressure
echo "3000" > /proc/sys/vm/dirty_expire_centisecs
echo "500" > /proc/sys/vm/dirty_writeback_centisecs
echo "3" > /proc/sys/vm/dirty_background_ratio
echo "2048,4096,51200,56320,61440,70400" > /sys/module/lowmemorykiller/parameters/minfree
echo "veno" > /proc/sys/net/ipv4/tcp_congestion_control

AIX Clone

2012-05-29T12:46:00.001-03:00

Many people will already know how to do this, since there's some (huge) machines you need lots of AIX Virtual Servers, and of course, you'll not make thousands of installs (will you?).

So a clone is the best option, you have two ways to do that:

1) alt_disk_install (recommended and supported)
2) VG Clone (only recommended to clone your vg, not supported, but works if alt_disk_install fails).

First method: alt_disk_install

Verify if you have all needed packages

# lslpp -l |grep bos.alt

Verify if all LVs have a copy in hdisk0

# for i in `lsvg -l rootvg |cut -f1 -d" "|grep -v rootvg|grep -v LV`; do lslv -l $i; done

Broke the mirror (if you have one)

# unmirrorvg rootvg hdisk1

# reducevg rootvg hdisk1

Turn off the Quorum

# chvg -a'y' -Q'n' rootvg

Set the bootlist

# bootlist -m normal -o hdisk0

Recreate the boot image

# bosboot -ad hdisk0

Verify

# lspv

Clone

# alt_disk_install -COB hdisk#

Verify the altinst_rootvg and remove the clone (you don't need to do that, but double check it)

# lspv
# rmdev -Rdl hdisk#

# exportvg altinst_rootvg

Mirror your vg again

# extendvg rootvg hdisk1
# mirrorvg -m rootvg hdisk1
# bosboot -a
# bootlist -m normal hdisk0 hdisk1

Second method: VG Clone

Broke the mirror (if you have one)

# unmirrorvg rootvg hdisk1

Turn off the Quorum

# chvg -a'y' -Q'n' rootvg

Set the bootlist

# bootlist -m normal -o hdisk0

Recreate the boot image

# bosboot -ad hdisk0

Verify

# lspv

Clone

# extendvg rootvg hdisk#
# mirrorvg -m rootvg hdisk#
# bosboot -a
# bootlist -m normal hdisk0 hdisk#

Remove the second disk from VG, I mean the device (yes, do it)

# rmdev -Rdl hdisk#

Now remove it from vg

# unmirrorvg rootvg hdisk#

# reducevg rootvg hdisk#

Remove physically the disk from the Virtual Server or the machine and redetect the device drivers

# cfgmgr

Recreate the rootvg mirror

# extendvg rootvg hdisk1
# mirrorvg -m rootvg hdisk1
# bosboot -a
# bootlist -m normal hdisk0 hdisk1

...and if the AIX boot partition fails?

2012-05-29T12:30:00.001-03:00

First, you need to boot with an AIX installation disk or Diagnostics disk (Virtual I/O bootdisk also works) and go to maintanence mode. Choose the option to give you a shell (mounting rootvg, of course).
Just in case, this is a quite dangerous process, so you need to know what you're doing (and so, if you destroy the world, it's your fault, not mine).

Now let's see what happens with boot partition:

# lslv -l hd5

If there's something wrong with your hd5 boot device, you should create the hd5 again. This process is dangerous, do you have IBM AIX Support ?? if so, please call them.

If not, then, because hd5 is seems not to be on disk but in ODM, you have to delete hd5 definitions from ODM, and then create a new boot device.

1) Look in ODM for references to hd5 object name (you get a list similar to this example)

# odmget -q name=hd5 CuAt

CuAt:
name = "hd5"
attribute = "lvserial_id"
value = "000439211138e3f6.1"
type = "R"
generic = "D"
rep = "n"
nls_index = 648

CuAt:
name = "hd5"
attribute = "inter"
value = "x"
type = "R"
generic = "DU"
rep = "l"
nls_index = 643

CuAt:
name = "hd5"
attribute = "type"
value = "boot"
type = "R"
generic = "DU"
rep = "s"
nls_index = 639

CuAt:
name = "hd5"
attribute = "size"
value = "2"
type = "R"
generic = "DU"
rep = "r"
nls_index = 647

2) Now, se the objects you have and use odmget, like this:

# odmget -q name=hd5 CuDv
# odmget -q value3=hd5 CuDvDr
# odmget -q name=hd5 CuDep
# odmget -q name=hd5 CuVPD
3) Take a backup of /etc/objrepos:

# odmget CuAt > /backupdir/CuAt.txt
# odmget CuDv > /backupdir/CuDv.txt
and so on....

4) After identifying which ODM DB has references you have to delete any reference with odmdelete:

# odmdelete -q name=hd5 -o CuAt
# odmdelete -q name=hd5 -o CuDv
# odmdelete -q value3=hd5 -o CuDvDr
# odmdelete -q name=hd5 -o CuDep
# odmdelete -q name=hd5 -o CuVPD
4) If you were lucky enough your system is still running, determine the PP size of the disk you want to be hd5. Now use the following command to recreate the boot partition:

# mklv -t boot -y hd5 -a e rootvg 1 hdiskXX

5) This means create a hd5 boot logical volume on hdiskXX belonging to rootvg size 1 PP. Once you have created hd5 boot partition, you need to reinstate the kernel:

# bosboot -ad /dev/ipldevice
# bootlist -m normal hdiskXX
# syncvg
6) Reboot the server, sacrifice a goat and pray.

MenelkirMIUI for Nexus One

2011-09-26T01:00:00.002-03:00

Custom MIUI for Nexus One.

What we have?
* Juwe11's memory optimization script
* Updated IntersectRaven kernel
* SmartassV2 Default Governor
* Custom Boot Animation (I dont know the author, post me a comment if you know)
* Latest MIUI.us build (1.9.23)

All updates goes to this folder:

http://minus.com/mbkyw3ZcVd

Also, this ROM are available at ROM Manager

MenelkirCM7 for Nexus One

2011-09-26T00:57:00.002-03:00

Custom CyanogenMOD for Nexus One.

What we have?
* Juwe11's memory optimization script
* Updated base apps
* S2E for an easily apps2ext management
* Updated IntersectRaven kernel
* SmartassV2 Default Governor
* Custom Boot Animation (I dont know the author, post me a comment if you know)
* Latest CyanogenMod 7 Nightly build (build 202)

All updates goes to this folder:

http://minus.com/mbrpWFOxzM

Also, this ROM are available at ROM Manager

Menelkir Sense 1.3 for Nexus One

2011-08-25T22:04:00.003-03:00

This is my first attempt to make a perfect Sense 1.8 for daily use. It's primary based on
eViL NXSense HD v.1.1_BETA (Official Desire HD Port) from eViL D:
Since this is my first release, there's nothing much significant (yet), only some cleaning, tweaks and updates.

SPECS (from eViL NXSense HD v1.1 BETA):
Desire HD build 1.15.405.1, 1.24.405.1, 1.28.405.1, 1.32.405.3, 1.32.405.6, 1.72.405.3
Quick boot from hibernation & built in reboot from power menu
Flip Clock
Blocked Callers
New Car Panel
BT & FM radio
HTC Hub & Likes
Updated Google apps
HTC Skins
HTC E-reader
HTC Power & DATA Control widget
Unified Mailbox.

TODO:
Music Change via Volume Button when screen is turned off for general music players (Don't know how)
Better memory management (WIP)
Better battery management (WIP, still testing some kernels, mine included)
Screen suddenly on sometimes (I have the same issue in evil rom)

WORKING:
Nothing reported (yet) in 1.2

REQUIREMENTS:
Partition: 768MB SD-EXT Minimum / 0 SWAP **Recommended 1GB SD-EXT / 0 SWAP

INSTRUCTIONS:
First install:
Install RA Recovery
Boot to Recovery
FULL-WIPE
Flash Alignment tool from coolexe (recomended) link: http://www.multiupload.com/J8SJ8TRH2G
Flash ROM
Reboot
Wait

Updating from eViL NXSense HD or old versions (in the future):
Install RA Recovery
Boot to Recovery
Flash ROM
Reboot
Wait

CHANGELOG:

1.3:
Some bug fixes
Internal memory optimization

1.2:
Added sysro/sysrw scripts
Fixed DSP Manager
Adobe Flash updated
Wireless Tether removed (by now)(doesn't work)
Stocks removed (by now)(doesn't work)
Other fixes and tunings I don't remember

1.1:
Added:
DSP Manager (there's a bug here, I'll fix in next release)
Changed governor for userspace (when awake) and powersave (when sleeping) script by
FloHimself. Btw, I recomend SetCPU to personalize your own use.
Juwe11's memory optimization script

1.0:
Added:
Kernel: 2.6.35.6-eViL--10-7--1-wmcfg http://dl.dropbox.com/u/6809682/eViL-35--10-07--1-720p-ir-svs-wmcfg.zip
Some tweaks I forgot..

Removed apps:
Amazon MP3
Chrome to Phone
Google Voice
Titanium Backup
Rom Manager
APN Backup and Rstore
Twitter
Facebook

DOWNLOADS:
1.3: http://min.us/mbhtO1Z8ei
1.2: http://www.multiupload.com/DWYNERE2YN
1.1: http://www.multiupload.com/532L7EG05Z
1.0: http://www.multiupload.com/EEK747S9KL

OFFICIAL THREAD:
http://forum.xda-developers.com/showthread.php?t=1235296

Service Processor Codes

2011-08-17T10:50:00.002-03:00

All the Service processor codes.

Table 1. (C1xx) Service processor progress codes (checkpoints)

Progress Code	Description/Action Perform all actions before exchanging Failing Items	Failing Items
C10010xx	Pre-standby	FSPSPC1
C1001014	Pre-standby	FSPSPC1
C1001020	Pre-standby	FSPSPC1
C1001F00	Pre-standby: starting initial transition file	FSPSPC1
C1001F0D	Pre-standby: discovery completed in initial transition file. While this system displays this checkpoint, the service processor card reads the system vital product data (VPD). The service processor must complete reading the system VPD before the system displays the next progress code (checkpoint). Reading the system VPD might take as long as 15 minutes on systems with maximum configurations or many disk drives. Wait at least 15 minutes for this checkpoint to change before you decide that the system is hung. If you determine that the system is hung at this checkpoint, do the following: On model 285, 520, or 9131-52A, reseat the VPD card. See Exchanging the VPD card in the model 520 and 285 for more information. On all other models (or if the preceding action did not resolve the problem), use the specified action in the Failing Item column.	FSPSPC1
C1001F0F	Pre-standby: waiting for standby synchronization from initial transition file	FSPSPC1
C1001FFF	Pre-standby: completed initial transition file	FSPSPC1
C1009x02	Hardware object manager: (HOM): build cards IPL step in progress	FSPSPC1
C1009x04	Hardware object manager: (HOM): build processors IPL step in progress	FSPSPC1
C1009x06	Hardware object manager: (HOM): build chips IPL step in progress	FSPSPC1
C1009x08	Hardware object manager: (HOM): build HOM IPL step in progress	FSPSPC1
C1009x10	Hardware object manager: (HOM): configure HOM IPL step in progress	FSPSPC1
C1009x12	Hardware object manager: (HOM): initialize HOM IPL step in progress	FSPSPC1
C1009x18	Hardware object manager: (HOM): validate HOM IPL step in progress	FSPSPC1
C1009x1B	GARD IPL step in progress	FSPSPC1
C1009x20	Get LBIST values IPL step in progress	FSPSPC1
C1009x23	Clock test IPL step in progress	FSPSPC1
C1009x28	Frequency control IPL step in progress	FSPSPC1
C1009x30	Initalize JTAG IPL step in progress	FSPSPC1
C1009x38	Mask attentions IPL step in progress	FSPSPC1
C1009x40	CEC flush IPL step in progress	FSPSPC1
C1009x48	Scan interface basic assurance tests (SIBATs) IPL step in progress	FSPSPC1
C1009x50	LBIST IPL step in progress	FSPSPC1
C1009x58	ABIST IPL step in progress	FSPSPC1
C1009x60	Asset protection IPL step in progress	FSPSPC1
C1009x68	Wire test IPL step in progress	FSPSPC1
C1009x70	Memory size IPL step in progress	FSPSPC1
C1009x78	Long scan initialization IPL step in progress	FSPSPC1
C1009x80	Start clocks IPL step in progress	FSPSPC1
C1009x88	SCOM initialization IPL step in progress	FSPSPC1
C1009x90	Run interface alignment procedure IPL step in progress	FSPSPC1
C1009x98	DRAM initialization IPL step in progress	FSPSPC1
C1009x9B	Random data test IPL step in progress	FSPSPC1
C1009xA0	Memory diagnostic IPL step in progress	FSPSPC1
C1009xA8	Dump initialization IPL step in progress	FSPSPC1
C1009xB0	Processor runtime diagnostics (PRD) IPL step in progress	FSPSPC1
C1009xB8	Enable machine check IPL step in progress	FSPSPC1
C1009xC0	Message passing wait in progress	FSPSPC1
C1009xC8	Message passing start in progress	FSPSPC1
C100C1xx	Power control	FSPSPC1
C100D009	Licensed Internal Code (system) running initialization
C1011F00	Pre-standby: starting independent initial transition file (primary/secondary)	FSPSPC1
C1011FFF	Pre-standby: completed independent initial transition file (primary/secondary)	FSPSPC1
C1021F00	Pre-standby: starting primaryInitial transition file (primary)	FSPSPC1
C1021FFF	Pre-standby: completed primaryInitial transition file (primary)	FSPSPC1
C1031F00	Pre-standby: starting secondaryInitial transition file (secondary)	FSPSPC1
C1031FFF	Pre-standby: completed secondaryInitial transition file (secondary)	FSPSPC1
C103A1xx	Hypervisor code modules are being transferred to system storage	FSPSPC1
C103A2xx	Hypervisor data areas are being built in system storage	FSPSPC1
C103A3xx	Hypervisor data structures are being transferred to system storage	FSPSPC1
C103A400	Special purpose registers are loaded and instructions are started on the system processors	FSPSPC1
C103A401	Instructions have been started on the system processors	FSPSPC1
C103C2xx	The service processor is waiting for the batteries in the uninterruptible power supply (UPS) to charge prior to automatic power on-IPL. The last byte (xx) will increment while waiting on the UPS batteries.	FSPSPC1
C1041F00	Pre-standby: starting GardedInitial transition file (secondary)	FSPSPC1
C1041FFF	Pre-standby: completed GardedInitial transition file (secondary)	FSPSPC1
C104550x	The system reboot is waiting until the sibling service processor reaches the termination state. The last nibble (x) will toggle between 0 and 1.
C10F2000	Halt: starting halt transition file
C10F20FF	Halt: completing halt transition file
C1112000	Power on: starting Standby-PowerOnTransition transition file (primary)	FSPSPC1
C11120FF	Power on: completed Standby-PowerOnTransition transition file (primary)	FSPSPC1
C1122000	Power on: starting PowerOnTransition-PoweredOn transition file (primary)	FSPSPC1
C11220FF	Power on: completed PowerOnTransition-PoweredOn transition file (primary)	FSPSPC1
C1132000	Power on: starting PoweredOn-IplTransition transition file (primary)	FSPSPC1
C11320FF	Power on: completed PoweredOn-IplTransition transition file (primary)	FSPSPC1
C116C2xx	System power interface is listening for power fault events from SPCN. The last byte (xx) will increment up from 00 to 1F every second while it waits.	FSPSPC1
C1202000	IPL transition: starting PowerOn/IplTransition-Ipl transition file (primary)	FSPSPC1
C12020FF	IPL transition: completed PowerOn/IplTransition-Ipl transition file (primary)	FSPSPC1
C12040xx	IPL lock time left until expiration. The last byte (xx) will count down as the IPL lock time runs out (FF-00).	FSPSPC1
C1212000	IPL transition: starting Standard/IplTransition-Ipl transition file (primary)	FSPSPC1
C12120FF	IPL transition: completed Standard/IplTransition-Ipl transition file (primary)	FSPSPC1
C1222000	IPL transition: starting Flash/IplTransition-Ipl transition file (primary)	FSPSPC1
C12220FF	IPL transition: completed Flash/IplTransition-Ipl transition file (primary)	FSPSPC1
C1232000	IPL transition: starting PostDump/IplTransition-Ipl transition file (primary)	FSPSPC1
C12320FF	IPL transition: completed PostDump/IplTransition-Ipl transition file (primary)	FSPSPC1
C1242000	IPL transition: starting Idle/IplTransition-Ipl transition file (secondary)	FSPSPC1
C12420FF	IPL transition: completed Idle/IplTransition-Ipl transition file (secondary)	FSPSPC1
C1252000	IPL transition: starting Standby/IplTransition-Ipl transition file (secondary)	FSPSPC1
C12520FF	IPL transition: completed Standby/IplTransition-Ipl transition file (secondary)	FSPSPC1
C1382000	IPL: starting HostStarted-BcuSwitched transition file (primary)	FSPSPC1
C13820FF	IPL: completed HostStarted-BcuSwitched transition file (primary)	FSPSPC1
C1392000	IPL: starting BcuSwitched-Runtime transition file (primary)	FSPSPC1
C13920FF	IPL: completed BcuSwitched-Runtime transition file (primary)	FSPSPC1
C1402000	IPL: starting Normal/fast/Ipl-HostStarted transition file (primary)	FSPSPC1
C14020FF	IPL: completed Normal/fast/Ipl-HostStarted transition file (primary)	FSPSPC1
C1412000	IPL: starting Normal/slow/Ipl-HostStarted transition file (primary)	FSPSPC1
C14120FF	IPL: completed Normal/slow/Ipl-HostStarted transition file (primary)	FSPSPC1
C1422000	IPL: starting PostDump/Ipl-HostStarted transition file (primary)	FSPSPC1
C14220FF	IPL: completed PostDump/Ipl-HostStarted transition file (primary)	FSPSPC1
C1432000	IPL: starting Ipl-IdleTransition transition file (secondary)	FSPSPC1
C14320FF	IPL: completed Ipl-IdleTransition transition file (secondary)	FSPSPC1
C1442000	IPL: starting IdleTransition-Idle transition file (secondary)	FSPSPC1
C14420FF	IPL: completed IdleTransition-Idle transition file (secondary)	FSPSPC1
C1452000	IPL: starting Ipl-StandbyVerificationTransition transition file (secondary)	FSPSPC1
C14520FF	IPL: completed Ipl-StandbyVerificationTransition transition file (secondary)	FSPSPC1
C1462000	IPL: starting StandbyVerificationTransition-Standby transition file (secondary)	FSPSPC1
C14620FF	IPL: completed StandbyVerificationTransition-Standby transition file (secondary)	FSPSPC1
C1472000	IPL: starting normal/ipl-hoststarted transition file (master)	FSPSPC1
C14720FF	IPL: completing normal/ipl-hoststarted transition file (master)	FSPSPC1
C1482000	IPL: starting normal/backup/ipl-hoststarted transition file (secondary)	FSPSPC1
C14820FF	IPL: completing normal/backup/ipl-hoststarted transition file (secondary)	FSPSPC1
C162E402	If the system hangs on this checkpoint, the service processor is unable to collect VPD from the service processor.	SVCPROC
C162E403	If the system hangs on this checkpoint, the service processor is unable to collect VPD from the operator panel.	CTLNPL
C162E405	If the system hangs on this checkpoint, the service processor is unable to collect VPD from the VPD card.	CAPACTY
C162E408	If the system hangs on this checkpoint, the service processor is unable to collect VPD from the system backplane.	SYSBKPL
C162E410	If the system hangs on this checkpoint, the service processor is unable to collect VPD from a processor.	ANYPROC
C162E41C	If the system hangs on this checkpoint, the service processor is unable to collect VPD from the system.	CAPACTY
C162E41E	If the system hangs on this checkpoint, the service processor is unable to collect VPD from the enclosure.	SYSBKPL
C162E420	If the system hangs on this checkpoint, the service processor is unable to collect VPD from the IO backplane.	IO_HUB
C162E421	If the system hangs on this checkpoint, the service processor is unable to collect VPD from the IO hub.	IO_HUB
C162E430	If the system hangs on this checkpoint, the service processor is unable to collect VPD from SPCN.	SVCPROC
C162E4A0	If the system hangs on this checkpoint, the service processor is unable to collect VPD from the VSBP Starting Point.	CAPACTY
C162E4D0	If the system hangs on this checkpoint, the service processor is unable to collect VPD from memory DIMM.	MEMDIMM
C1645300	Starting a data synchronization operation between the primary service processor and the secondary service processor.	FSPSPC1
C1645301	Completed a data synchronization operation between the primary service processor and the secondary service processor.	FSPSPC1
C16453xx	A large data synchronization operation from the primary service processor to the secondary service processor is taking place. The last nibble (x) will toggle between 2 and 3.	FSPSPC1
C1802000	Termination: starting TerminationTransition-Termination transition file (primary)	FSPSPC1
C18020FF	Termination: completed TerminationTransition-Termination transition file (primary)	FSPSPC1
C1902000	Power off: starting Any-Dpo transition file (primary)	FSPSPC1
C19020FF	Power off: completed Any-Dpo transition file (primary)	FSPSPC1
C1912000	Power off: starting Any-PowerOffTransition transition file (primary)	FSPSPC1
C19120FF	Power off: completed Any-PowerOffTransition transition file (primary)	FSPSPC1
C1922000	Power off: starting PowerOffTransition-PoweredOff transition file (primary)	FSPSPC1
C19220FF	Power off: completed PowerOffTransition-PoweredOff transition file (primary)	FSPSPC1
C1C02000	Secondary VERIFICATION: starting Standby-StandbyVerification transition file (primary)	FSPSPC1
C1C020FF	Secondary verification: completed Standby-StandbyVerification transition file (primary)	FSPSPC1
C1C12000	Secondary verification: starting StandbyVerification-Standby transition file (primary)	FSPSPC1
C1C120FF	Secondary verification: completed StandbyVerification-Standby transition file (primary)	FSPSPC1
C1C22000	Secondary verification: starting Runtime-secondaryVerification transition file (primary)	FSPSPC1
C1C220FF	Secondary verification: completed Runtime-secondaryVerification transition file (primary)	FSPSPC1
C1C32000	Secondary verification: starting secondaryVerification-Runtime transition file (primary)	FSPSPC1
C1C320FF	Secondary verification: completed secondaryVerification-Runtime transition file (primary)	FSPSPC1
C1C42000	Failover: starting failover/failover-termination transition file (master)	FSPSPC1
C1C420FF	Failover: completed failover/failover-termination transition file (master)	FSPSPC1
C1C52000	Failover: starting failover/backup/failover-termination transition file (secondary)	FSPSPC1
C1C520FF	Failover: completed failover/backup/failover-termination transition file (secondary)	FSPSPC1
C1C62000	Failover: starting failover/failover-standby transition file (master)	FSPSPC1
C1C620FF	Failover: completed failover/failover-standby transition file (master)	FSPSPC1
C1C72000	Failover: starting failover/backup/failover-standby transition file (secondary)	FSPSPC1
C1C720FF	Failover: completed failover/backup/failover-standby transition file (secondary)	FSPSPC1
C1CA2000	Connection monitoring failover: starting survfailover/backup/failover-runtime transition file (secondary)	FSPSPC1
C1CA20FF	Connection monitoring failover: completed survfailover/backup/failover-runtime transition file (secondary)	FSPSPC1
C1CB2000	Connection monitoring failover: starting survfailover/backup/failover-termination transition file (secondary)	FSPSPC1
C1CB20FF	Connection monitoring failover: completed survfailover/backup/failover-termination transition file (secondary)	FSPSPC1
C1CC2000	Connection monitoring failover: starting survfailover/backup/failover-standby transition file (secondary)	FSPSPC1
C1CC20FF	Connection monitoring failover: completed survfailover/backup/failover-standby transition file (secondary)	FSPSPC1
C1D22000	Dump: starting DumpTransition-Dump transition file (primary)	FSPSPC1
C1D2200D	Dump: calling hardware dump from DumpTransition-Dump transition file (master)	FSPSPC1
C1D2200F	Dump: calling main store dump from DumpTransition-Dump transition file (master)	FSPSPC1
C1D220FF	Dump: completed DumpTransition-Dump transition file (primary)	FSPSPC1
C1E82000	Exit error: starting ExitError/Ipl transition file (primary)	FSPSPC1
C1E820FF	Exit error: completed ExitError/Ipl transition file (primary)	FSPSPC1
C1E92000	Extract exit error: starting ExtractExitError/ipl transition file (master)
C1E920FF	Extract exit error: completed ExtractExitError/ipl transition file (master)
C1EA2000	Extract exit error: starting ExtractExitError/Backup/ipl transition file (secondary)
C1EA20FF	Extract exit error: completed ExtractExitError/Backup/ipl transition file (secondary)
C1F22000	Reset/reload: starting Reset/Ipl-LimitedRuntime transition file (primary)	FSPSPC1
C1F220FF	Reset/reload: completed Reset/Ipl-LimitedRuntime transition file (primary)	FSPSPC1
C1F32000	Reset/reload: starting Reset/Ipl-Runtime transition file (primary)	FSPSPC1
C1F320FF	Reset/reload: completed Reset/Ipl-Runtime transition file (primary)	FSPSPC1
C1F42000	Reset/reload: starting Reset/Ipl-TermTransition transition file (primary)	FSPSPC1
C1F420FF	Reset/reload: completed Reset/Ipl-TermTransition transition file (primary)	FSPSPC1

Must have android applications

2011-07-19T19:01:00.003-03:00

Yeah I know that thousand of sites and people already write one of this lists. So why Im writing this? Because I see thousand of pages talking about thousand of apps not so necessary, so I made my own. Let's go

Titanium Backup
The "must have" backup software for android. You MUST have root access to use it, cause he can make backup to system applications (with configurations), very useful if you like testing some roms. There's a free version and a paid version with nice features.

Seekdroid
There's loads of apps that do this job. You can track your cellphone, get info, last calls, remote lock, remote wipe (internal and sdcard) and alarm. The differrence from the others is that one only costs 0,99 USD (one time only, and it works).

Camera360 / Camera360 Ultimate
A nice camera application with lots of nice features, such effects, plugins, etc. Isn't VERY NECESSARY, but if you like to take some shots, give a try. There's a free and a paid version with some features.

Tasker
An automated task scheduler, with him you can, for example: "I want my GPS only working with applications X and Y", "I want my wifi on only when Im at home", and so on. Of course, its an advanced application, you need some time to learn how it works but its perfect. There's no free version.

Tapatalk
If you are addicted to forums (like me), this is the best you can have. You can test the "feel" using the XDA-Developers Forum application.

SwitchPro Widget
Its the same widget buttons app from native android, but this one you can customize with thousands of options.

ADB Shell using PuTTy

2011-06-21T16:27:00.000-03:00

Every time I need to use a windows machine to fix something in my android experiments, its a frustrating experience, specially when you need to work with shells more sofisticated like the HTC ones. Everything is messy using command prompt or any other shell (csh from subsystem for unix applications, etc).

After lurking XDA, I find this post about using PuTTy as ADB Shell, its perfect.

EXT4 Optimization for daily use

2011-06-07T21:39:00.000-03:00

Since all major distros use the default options for ext4, I learn some safe tricks:

/dev/sda3 / ext4 noatime,commit=100,nouser_xattr,errors=remount-ro 0 1

noatime - Deactivates the file access time modification. If you don't need to know, or don't use it, you can disable it.

commit=100 - Increases the write interval between data and meta-data (the regular sync operation). Just keep in mind that if you doesn't have a power supply, this can be dangerous. If you're unsure, just skip this option.

nouser_xattr - No user extendend attributes, it safe to disable this (if you don't use it).

errors=remount-ro - For saffety reasons, make the partition remount RO if something wrong occurs.

Intel ICH7 HDA Audio Controller (VIA4397)

2011-05-31T14:10:00.002-03:00

It's known that HDA-Audio based codecs are the worst audio problems in Linux World since Soundblaster native driver (back to 1996, I've suffered a lot to configure this little bastard).

After trying a lot of configurations and even trying use OSS4 (worst than OSS native kernel driver, don't use it unless you really need it), the solution is weirdo and simple.

If you have a VIA based codec card like this one:

menelkir@Battlestation:~$ cat /proc/asound/card0/codec#0 | grep Codec
Codec: VIA ID 4397

You have two ways of solution.

1) Using generic model
New alsa-drivers have a lot of fixes to Intel-HDA codecs, not all are working perfect (but better solutions will come with time). If you have a brand new and updated distribution (until today 30/Aug/2011), you need to specify the model of your board in /etc/modprobe.d/alsa-base.conf, in this case, generic:

# Intel-HDA module options
options snd-hda-intel probe_mask=1 model=generic

2) Simple, last stand: Blacklisting

If the first method doesn't work or you're using an old alsa drivers, you MUST blacklist the via codec. Ssounds strange, but it works. Add this line in your /etc/modprobe.d/blacklist.conf (or whatever place that your distro hide this configuration):

# Disable VIA Codec
blacklist snd_hda_codec_via

Reboot, and everything will works.

(Updated the post because alsa fixed this old bug, and I want this information to be accurate).

Motorola Milestone Boot Chain

2011-03-06T20:45:00.001-03:00

xvilka @ #milestone-modding ask to someone making a graphic of Motorola Milestone's boot process, so I get into the work. With his help about the necessary steps, I make this diagram.

The red ones is what is locked inside the phone.

Click here to see in a better quality: http://dl.dropbox.com/u/8863098/Milestone-visio.png

Here's the source-code: http://dl.dropbox.com/u/8863098/Milestone_Boot_Diagram.vsd

Published under MIT License

Howto use an OpenVPN connection using Android 2.2/2.3

2011-02-16T02:53:00.003-02:00

I'll guess you have a vpn server fully functional and some certifications and a ROM with OpenVPN integrated (like CyanogenMOD).

First, get your certs and lets generate a PKCS12:

openssl pkcs12 -export -in [ClientCert] -inkey [Key] -certfile [CAcert] -name [RandomName] -out [certname.pl2]

He asks to make a password and will generate a file certname.pl2 (or whatever you choose), copy this file to the root of your SDCard.

Go to Settings -> Location and Security -> Credential Storage to install your PKCS12 file into Android System. Put your password, set a friendly name and set a new password for your Internal Android Certificates.

Go to Wireless & Networks -> VPN Settings -> Add VPN -> Add OpenVPN VPN and configure your VPN options like name, ip and choose the certifications.

You're good to go. :)

Dingux New Home

2011-02-16T02:53:00.002-02:00

Dingux Development has a new home

https://code.google.com/p/menelkir4dingux/

Menelkir LocalBR for Dingux 0.13

2010-09-10T19:23:00.000-03:00

  Removed: Menelkir Dingux Kernel
  Removed: TV-OUT Controls for Menelkir Dingux Kernel
  Added: SiENcE kernel (included kernel for A330)
  Updated: nuPDF 0.3
  Updated: gmu 0.7.1
  Updated: snes9x 20100828
  Updated: Opentyrian
  Added: Abuse 0.1
  Added: GnuBoy4D 1.2
  Added: Cooldown
  Added: Exult svn6317
  Added: Faraway beta
  Added: Freenger 0.9
  Added: OpenJazz R1
  Added: Profanation DeLuxe
  Added: Quake R2 20100906
  Added: Vorton Beta2

Download: Menelkir LocalBR for Dingux 0.13

Auto connect/identify with irssi

2010-09-10T12:09:00.000-03:00

This is very very VERY annoying, specially if you let your irc client open in your home and go to somewhere else.

First of all, connect in your favorite network, I'll use freenode as an example. And then, use the following commands:

/server add -auto -network freenode irc.freenode.net 6667
/network add -autosendcmd "/^msg Nickserv idenify ;wait 2000"

Now you can add your favorite channels after the identify procedure:

/channel add -auto #somechannel freenode

TV OUT Fix

2010-06-23T21:05:00.001-03:00

I've messed up some confs in my last local, so here is the fix.

1) Delete /local/gmenu2x/sections/applications/tvout*
2) Copy the contents of this files to /local/gmenu2x/sections/settings/
3) Done

TV OUT FIX

Menelkir LocalBR for Dingux 0.12

2010-06-14T21:00:00.000-03:00

Added: nupdf
Updated: d1x-rebirth #2
Added: d2x-rebirth #1
Added: MDF Preview
Added: Midpath 0.3
Updated: Snes9x4D 20100429
Added: OldPlay 1.12
Added: DosBox Alpha (with DOS Navigator from http://www.ritlabs.com/en/products/dn/)
Added: Menelkir Dingux Kernel 0.4 (for testing)
Updated: Openmsx 0.8.0
Added: TV-OUT Controls (ONLY WORKS WITH MENELKIR DINGUX KERNEL)

Download: Menelkir LocalBR for Dingux 0.12

New Portage Repository

2010-05-31T10:02:00.001-03:00

I just started a new Portage repository (git based). If someone are interested, here's the link:

http://github.com/menelkir/menelkir

Menelkir Kernel 0.3

2010-05-28T14:53:00.001-03:00

This is a test kernel, I don’t tested enough, but works for me (and maybe doesn’t work for you).

Changelog:

0.1:
   Initial release, based on Main Dingux Kernel
   Optimized for size
   Release for test only (things may broke)

0.2:
Internal optimizations
Some hardware testing

0.3:
   Swap Support
   Removing unused debug and governors from CPU frequency scalling
   Adding Ingenic RTC SoC (from bkc_a320 @ Dingoonity)
   Removing unused logic from Kernel Hacking

http://www.4shared.com/file/mD-BKX3u/Menelkir_Kernel_03.html

Gentoo CrossDev MIPsel entry in gentoo-wiki.com

2010-05-27T11:15:00.001-03:00

I’m working on a simple entry in gentoo-wiki.com for MIPsel and related.

At this point I have a proper configured environment for cross-compile stuff for my dingux.

Here.

Comments and sugestions are welcome.

Funtoo + Paludis

2010-05-18T19:53:00.002-03:00

A good tutorial about using funtoo with paludis

http://wiki.github.com/thewtex/portage/funtoo-paludis