Related
Hi there,
as anounced her is my first Umbrella Themed Android Rom. It is a mixture of several vogue, dream and saphire roms.
V1+V2:
Here the things i added:
Some apps:
-proPaint Camera (fully working)
-RockOn
-LastFM app
-Custom boot animation and sound (just on first boot so loud)
-Umbrella Themed (more to come, if some graphical advanced people could help me i would be pleased)
-Latest Libs
-Shazaam
-New default ringtone and notification tone
-Kaiser wifi fix
V3:
-new base
-added homeswitcher
-added normal homescreen
-some more fixes and tweaks
Working:
Kaiser (tested by me:
-Data
-WiFi
-Camera (proPaint)
-Audio
-Phone (very responsive)
Vogue: Please tell me and i will add infos!!!
-Data ??
-WiFi ??
-Camera (proPaint) ??
-Audio ??
-Phone (very responsive) ??
I'm no developer i only wanted to give something back to this great community. Thanks goes to: dzo, Zenulator, mssmission, enatefox, pmos, vilord, craig0r, and all the others i forget taht make android on our devices possible
Download Link: Umbrella Corporation v2, with working media ROM
Download Link: Umbrella Corporation v3, Sense od Default Homescreen, fixed one
OPTIONAL:
Here my startup.txt (Change for your carrier to get data!!!)
#alloctest 0x2000
set RAMSIZE 0x07000000
set RAMADDR 0x10000000
#set FBDURINGBOOT 0
set MTYPE 1553
set KERNEL zImage
#set initrd "initrd.gz"
set initrd "\Storage Card\initrd.gz"
#set initrd "\Storage Card\initrd-console.gz"
#set initrd "\Storage Card\android.bin"
#
# The following kernel parameters are useful
# ppp.username - The username used to connect to the network when dialing #777
# ppp.password - The password used to connect to the network when dialing #777
# msm_sdcc.msmsdcc_fmax - The maximum frequency (in Hz) used by the SD controller
# pm.sleep_mode - The mode used when the phone is off
# 0=Power Collapse Suspend, 1=Power Collapse, 2=Apps Sleep,
# 3=Slow Clock and Wait for Interrupt 4=Wait for Interrupt
# Default is 1, use 1 for best power savings
# board-htckaiser.panel_type - Panel type used to power the panel off and on
# 0=Don't power off the panel (Default)
# 1=Sony 2=Topoly 3=Topoly (probably just the same as 2)
#
set cmdline "clock-7x00.ahb_div=3 clock_7x00.slow=1 elevator=noop ppp.nostart=0 board-htckaiser.panel_type=1 ppp.apn=internet.t-mobile ppp.username=tm ppp.password=tm pm.sleep_mode=1 mddi.width=320 mddi.height=480 msm_sdcc.msmsdcc_fmax=32000000 no_console_suspend board-kaiser-keypad.atttilt=0"
boot
Click to expand...
Click to collapse
and my custom.hero.conf: !!just works if your card is partitioned!!
Klick
Have fun!!!!
Changelog:
v1: initial release
v2: fixed no media problem
wow! sounds really great!
any drawbacks?
could you post some screenshots please?
and maybe a small step by step tutorial how to install? (or point me to an existing one - i am a total android noob!)
thank you for sharing!
br,krz
Thanks
Very Very Very nice surprise! Thanksssssssssssssssssss
Just copy all the files to the root of your sd card and download the basefiles from http://code.google.com/p/vogue-hero/downloads/detail?name=basefiles-20091009.zip&can=2&q= (cause i forget to add the conf files from the conf folder) just copy the conf folder from the basefiles zip to the root of your sd card, cause rootfs an zimage from my archive are newer.
Copy the startup.txt fom first post and create a file named startup.txt on your sd card. Then launch Haret.
Enjoy...
Thanx, for all you effort....
custom.hero.conf: !!just works if your card is partitioned!!
What partitions do I have to create for best performance?
oh my god i cant belive this got it running, the startup scared the crap outta me.we are not worthy, my sincere thanks to all the people working on porting android to kaiser, without u none of this would be possible. Thank you JeckyllHavok for maing this awesome design and rom
I got the best performance when i had a secon partition as ext2 and a third partition with linux-swap. Make the first around 100MB and the second one around 80MB
JeckyllHavok, when its all booted up, is it just a blank space with top bar info, or have i done summat wrong
Give it some time first start can take a while. Was the boot animation coming?
i got to the point where if i pressed green answer button, the phone pad would appear, and left and right soft keys control volume, but nothin on home screen
Did the startup setup apears? (I'm testing a new build with working media)
im new to this so bare with me, i get the loading system, with umbrella corp logo, when does this setup come
oh its come up now
Try if a restart helps. For me the black screen apears for 1-2 minutes then it continues Umbrella Boot ani-->Umbrella Logo-->UmbrellaLoading Screen-->BlackScreen-->Setup
just intalled this rom on my kaiser, works good except the LCD colours look a bit strange, its the first rom I get the colours messed up
any solution?
its working, its alive, its alive. Thanx man for all da help
just intalled this rom on my kaiser, works good except the LCD colours look a bit strange, its the first rom I get the colours messed up
any solution?
Click to expand...
Click to collapse
Can you post your default.txt
JeckyllHavok said:
Can you post your default.txt
Click to expand...
Click to collapse
I'v used the one on te first post, just changed the APN
#alloctest 0x2000
set RAMSIZE 0x07000000
set RAMADDR 0x10000000
#set FBDURINGBOOT 0
set MTYPE 1553
set KERNEL zImage
#set initrd "initrd.gz"
set initrd "\Storage Card\initrd.gz"
#set initrd "\Storage Card\initrd-console.gz"
#set initrd "\Storage Card\android.bin"
#
# The following kernel parameters are useful
# ppp.username - The username used to connect to the network when dialing #777
# ppp.password - The password used to connect to the network when dialing #777
# msm_sdcc.msmsdcc_fmax - The maximum frequency (in Hz) used by the SD controller
# pm.sleep_mode - The mode used when the phone is off
# 0=Power Collapse Suspend, 1=Power Collapse, 2=Apps Sleep,
# 3=Slow Clock and Wait for Interrupt 4=Wait for Interrupt
# Default is 1, use 1 for best power savings
# board-htckaiser.panel_type - Panel type used to power the panel off and on
# 0=Don't power off the panel (Default)
# 1=Sony 2=Topoly 3=Topoly (probably just the same as 2)
#
set cmdline "clock-7x00.ahb_div=3 clock_7x00.slow=1 elevator=noop ppp.nostart=0 board-htckaiser.panel_type=1 ppp.apn=internet ppp.username=tm ppp.password= pm.sleep_mode=1 mddi.width=320 mddi.height=480 msm_sdcc.msmsdcc_fmax=32000000 no_console_suspend board-kaiser-keypad.atttilt=0"
boot
Click to expand...
Click to collapse
board-htckaiser.panel_type=1
Try to change this to 2 or 3 and look if it helps
erm you was talkin abt partitioning sd card to give better performance could you give me some more info and instructions on what to do, Thank you
changed it to 2, it works like a charm
Thanks a lot!
The only thing i dot like is the startup sound, animation, but that is the less
Checkout:
http://forum.xda-developers.com/showthread.php?t=625014
Download http://sourceforge.net/projects/androidhtc/files/
confirm working data and testing 3d now
For newer build this should work ALOT better
____________________________________________________________________
Tin boot has now been ported thanks to DZO.
Latest Builds [from me(22/1/10)]:
http://www.megaupload.com/?f=SA71F1MT
Quiet Builds (Doesnt display kernel text):
http://www.megaupload.com/?f=04HIVHK7
The easiest way to test is to download this:
http://www.mediafire.com/?zldjhfnkzk2
and copy androidinstall.tar to your sd card before flashing.
Working:
Calls,Data,Camera
Not Working:
Bluetooth,wireless,google audio search/dial
If you have a different panel type you can always change it after it's booted by doing "echo 1 > /sys/module/board_htckaiser/parameters/panel_type" from adb or /init
It currently doesn't seem to boot from a soft reset, just pull the battery to reboot.
**FLASH at your own risk***
Please remember to donate:
dzo donation link
Thanks also to:
rzk333
_____________________________________________________
After looking into dzo's code for tinboot its seems possible to port it to kaiser. has anyone started porting it over?
i presume the initial steps should be mapping the kaiser nand, then expanding the kernel to boot initialize the hardware correctly. Since im sure serveral people must be working on this i thought a thread here would help maximize our efforts.
Any help you can offer dzo would be grateful.
Added link to tinboot code:
Tin boot git
mainly for reference:
An example Vogue rom payload MBR:
Part1: 0100 203f 0118 0200 0000 3e06 0000 0000
Part2: 0119 233f 0133 4006 0000 c006 0000 0000
Part3: 0134 253f 41d4 000d 0000 0068 0000 0000
Part4: 41d4 043f c13f 0075 0000 005b 0100 55aa
An Example Kaiser rom payload MBR:
Part1: 0100 203f 0100 0200 0000 3e00 0000 0000
Part2: 0101 233f 0116 4000 0000 8005 0000 0000
Part3: 0117 253f 81de c005 0000 00b2 0000 0000
Part4: 81df 043f 81a9 c0b7 0000 c0f2 0000 55aa
Tin Boot MBR:
Part1: 0100 233F 0118 0200 0000 be05 0000 0000 : LBA: 00000002 (2) Sectors: 05be(1470) FS:RAWFS
Part2: 0119 233f 0133 c005 0000 0000 0000 0000 : LBA: 000005c0 (1472) Sectors: 0000 (0) FS:RAWFS
Part3: 0134 253f 0134 c005 0000 4000 0000 0000 : LBA: 000005c0(1472) Sectors: 0040 (64) FS:IMGFS
Part4: 0135 043f c13f 0006 0000 0000 0000 55aa : LBA: 00000600(1536) Sectors: 0000 (0) FS:Unknown
first attempts have resulted in phone just rebooting, anyone able to help with this?
Man, I would love to help but I have too many projects on my plate right now. I do really appreciate your efforts! I'm not sure I can beta test, as my Kaiser is my main phone...
not even up to the stage of beta testing yet. just help with porting :
Code:
@
@ Tinboot V 1.0
@ Very simple bootloader for HTC Vogue
@ Martin Johnson - [email protected]
@
.equ MTYPE, 1553
.equ RAM_START, 0x10000000
.equ RAM_SIZE, 0x08000000
.equ INITRD_START, RAM_START+0x00800000
.equ KERNEL_OFFSET, 0x8000
.equ XIP_END, 0x2ff000
.org 0
b boot
.org 0x40
.word 0x43454345
.word romhdr+0x80000000 @ location of wince romhdr
.word romhdr
.org 0x100
tags: .word 5,0x54410001,1,0x1000,0 @ ATAG_CORE, pagesize=4K
.word 4,0x54410002,RAM_SIZE,RAM_START @ ATAG_MEM
.word 4,0x54420005,INITRD_START,fin-initrd @ ATAG_INITRD2
cmdline_start: .word (cmdline_end-cmdline_start)/4,0x54410009 @ ATAG_CMDLINE
.ifdef x428
.asciz "mddi.width=320 mddi.height=428 mtdparts=msm_nand:[email protected](boot),[email protected](root),[email protected](system),[email protected](userdata)"
.endif
.ifdef x480
.asciz "mddi.width=320 mddi.height=480 mtdparts=msm_nand:[email protected](boot),[email protected](root),[email protected](system),[email protected](userdata)"
.endif
.ifdef x320
.asciz "mddi.width=240 mddi.height=320 mtdparts=msm_nand:[email protected](boot),[email protected](root),[email protected](system),[email protected](userdata)"
.endif
.align
cmdline_end: .word 0,0 @ ATAG_END
.org 0x00001000
boot: ldr r0,initrd_ptr
ldr r3,fin_ptr
ldr r1,ird_start_ptr
copyinitrd: ldr r2,[r0],#4
str r2,[r1],#4
cmp r0,r3
blo copyinitrd
mov r0,#0
ldr r1,mtype
ldr r2,tags_addr
ldr pc,kernel_start
mtype: .word MTYPE
initrd_ptr: .word initrd+RAM_START
fin_ptr: .word fin+RAM_START
ird_start_ptr: .word INITRD_START
kernel_start: .word 0x10008000
tags_addr: .word 0x10000100
romhdr:
.word 0x0 @ dllfirst
.word 0x0 @ dlllast
.word 0x80000000 @ physfirst
.word 0x80000000+fin @ physlast
.word 0 @ num mods
.word 0x80000000+fin @ ramstart
.word 0x80000000 @ ramfree
.word 0x88000000 @ ramend
.word 0 @ copyentries
.word 0x80000000 @ copyoffset
.word 0 @ profilelen
.word 0 @ profileoffset
.word 0 @ numfiles
.word 0 @ flags
.word 0x20 @ fsrampercent
.word 0 @ drvglobstart
.word 0 @ drvgloblen
.word 0x201c2 @ cputype/flags
.word 0x80000000 @ pextensions
.word 0 @ trackingstart
.word 0 @ trackinglen
.org KERNEL_OFFSET
kernel:
.incbin "../arch/arm/boot/zImage"
initrd:
.incbin "../../bootenv/initrd-mini.gz"
.align
fin:
.org XIP_END-0x20000,0xff
.incbin "emptyimgfs"
@rootfs:
@.incbin "../../bootenv/rootfs.yaffs"
@.org rootfs + 0xd80000
Ive check the partition sizes and they should be ok for the kaiser? so must be something im missing in here?
Ive check the partition sizes and they should be ok for the kaiser?
Click to expand...
Click to collapse
check bootloader log from mtty, it must say something like this
Code:
OEMTranslateBaseAddress 23 80000000 80000000
IPLMSG:0x8:INFO: Loading image ...
IPLMSG:0x9:INFO: Jumping to image...
OEMLaunchImage 80000000
Jump to Physical Address 10300000
*Disconnect*
0x10300000 is your RAM_START,
0x00300000 is shift from Vogue addresses, that dzo catched from logs.
all you need is shift RAM_START, kernel_start and tag_addr addresses in bootloader and change MTYPE, then change prompt to yang to make capable nbh for kaiser.
I now working on tinboot for Nike, it have similar hardware to kaiser. Kernel boots, but now stops on some rpc_call, but that I think I can fix.
sorry for bad english and good luck with tinboot on kaiser
Wow thanks for your help, wouldnt have thought of looking there. Thanks
rzk333 said:
check bootloader log from mtty, it must say something like this
Code:
OEMTranslateBaseAddress 23 80000000 80000000
IPLMSG:0x8:INFO: Loading image ...
IPLMSG:0x9:INFO: Jumping to image...
OEMLaunchImage 80000000
Jump to Physical Address 10300000
*Disconnect*
0x10300000 is your RAM_START,
0x00300000 is shift from Vogue addresses, that dzo catched from logs.
all you need is shift RAM_START, kernel_start and tag_addr addresses in bootloader and change MTYPE, then change prompt to yang to make capable nbh for kaiser.
I now working on tinboot for Nike, it have similar hardware to kaiser. Kernel boots, but now stops on some rpc_call, but that I think I can fix.
sorry for bad english and good luck with tinboot on kaiser
Click to expand...
Click to collapse
how did you find the tag_addr and kernel_start address for the Nike? - Nerver mind , got it to boot upto the same RPC_Write error now, thank you
managed to get past the rpc_write error, commented it out, now invalid root device, presume a kernel driver problem. thought you might want to know for the nike? /kernel/drivers/ contains the error.
now we must dump a whole NAND and find there a partiton table. there we must find a XIP start address, for vogue it is 0x1600000. we need this to map NAND for this command from cmdline
Code:
mtdparts=msm_nand:[email protected](boot),[email protected](root),[email protected](system),[email protected](userdata)
this is means: 3MB on x1600000 for kernel, 13.5M for rootfs on 0x01900000 and etc, without that, kernel will panic/freeze due to inaccessible root device in memory.
hello,
great explain. If you want, i was to posssibility to flash my nand kaiser.
Just write me and i trying your work and report it.
Willou
i beleieve there is also a problem with:
Code:
.equ INITRD_START, RAM_START+0x00800000
it should load the initrd before trying to switch to rootfs, and it doesnt?
Also the partition data is stored in the generated output.nb.payload so that should actually be the same as starting point
Thats great news, am able to do beta tests for you guys, as my Kaiser is my secondary phone nowadays. am able to help trouble shoot and search for problems. pm me if you want my gtalk account.
Great initiative
Great initiative! I wish I was able to help, but unfortunately my abilities leave much to desire. so all I am able to offer is words of encouragement ...
it should load the initrd before trying to switch to rootfs, and it doesnt?
Click to expand...
Click to collapse
yup, kernel skips it, because initrd is on wrong shift in rom, that is because RAM_START/NAND start are wrong, I guess.
Do you have the same problem on the nike?
yes, everything are equal on this stage of loading kernel, due to same hardware. I have no progress now.
Excellent work. I'm no expert by any means but I'll see if I can help at least port the code over. Yet another bookmarked thread to the list
I there, my Kaiser is just only for personal tests (flashing, testing betas and android)
I can help you with my phone, but i don't writing any code... just for test!
Sorry for my bad english, i'm french
Excellent work.
Click to expand...
Click to collapse
excellent work of dzo thanks go to him.
tinboot repo updated for some changes related to kaiser, now pointers are calculated dynamicly and kaiser have own compile script. nand loading turned off cuz we don't now know start address. this should help to pass bug with initrd.
After compiling a zImage from dzo's git, I then created the NBH files. The only problem is setting the panel type seems to have no effect below is an extract from my tinboot.s file for setting the panel type. Could someone please point me in the right direction.
Panel Type 1:
Code:
.ifdef kaiser
.asciz "mddi.width=240 mddi.height=320 board-htckaiser.panel_type=1 pm.sleep_mode=1 hw3d.version=1 mtdparts=msm_nand:[email protected](boot),[email protected](root),[email protected](system),[email protected](userdata)"
.endif
Panel Type 2:
Code:
.ifdef kaiser
.asciz "mddi.width=240 mddi.height=320 board-htckaiser.panel_type=2 pm.sleep_mode=1 hw3d.version=1 mtdparts=msm_nand:[email protected](boot),[email protected](root),[email protected](system),[email protected](userdata)"
.endif
etc.
good look
i use panal 1 nbh this good screen
...deleted...
Hi Gentlemen,
I'm new to this forum, and recently installed Android on my TP2 (which I've been using for couple of years with WM6 then Win7).
My XD Android (FRX07) works fine [BTW: congrats & thanks to the great developers !!]
Physical keyboard on OS is "qwerty" though (ie, US/UK based), whereas it's "azerty" on my hardware (ie, French).
Does anybody know how to change this ? Thanks !
I went through the parameters and changing language to French didn't work out (must be the digital keyboard, not the physical one), nor did I find any solution on the Forum.
So, Thanks in advance...
Did you try changing the keyboard setting in the start up text?
Browse your SD Card and find startup.txt file
Open it with your favorite text editor
You will find this line looking like this (depending to your model):
[ set cmdline "lcd.density=240 msmvkeyb_toggle=off gsensor_axis=2,1,3 pm.sleep_mode=1 physkeyboard=rhod100_uk" ]
Just replace by :
[ set cmdline "lcd.density=240 msmvkeyb_toggle=off gsensor_axis=2,1,3 pm.sleep_mode=1 physkeyboard=rhod100_fr" ]
without the hooks of course
Hi, after some ideas in my mind about true Ubuntu server on my phone I have done full changes to the kernel needed for Ubuntu touch but never tried Ubuntu touch on my phone, only have tried Ubuntu server which I want to use for my home environment, I have done only kernel so if somebody need kernel you can try this one from here! Curently everyhing is patched and enabled needed for latest Ubuntu touch (vivid) except CONFIG_ARM_UNWIND since android display stop working if I disable these configuration, everything other is enabled as you see in this:
Checking config file for Ubuntu Touch specific config options.
CONFIG_IKCONFIG is already set
CONFIG_IKCONFIG_PROC is already set
CONFIG_SYSVIPC is already set
CONFIG_CGROUP_FREEZER is already set
CONFIG_NAMESPACES is already set
CONFIG_UTS_NS is already set
CONFIG_IPC_NS is already set
CONFIG_USER_NS is already set
CONFIG_PID_NS is already set
CONFIG_NET_NS is already set
CONFIG_AUDIT is already set
CONFIG_AUDITSYSCALL is already set
CONFIG_AUDIT_TREE is already set
CONFIG_AUDIT_WATCH is already set
CONFIG_CC_STACKPROTECTOR is already set
CONFIG_DEBUG_RODATA is already set
CONFIG_DEVTMPFS is already set
CONFIG_DEVTMPFS_MOUNT is already set
CONFIG_DEVPTS_MULTIPLE_INSTANCES is already set
CONFIG_ECRYPT_FS is already set
CONFIG_ECRYPT_FS_MESSAGING is already set
CONFIG_ENCRYPTED_KEYS is already set
CONFIG_EXT4_FS_POSIX_ACL is already set
CONFIG_EXT4_FS_SECURITY is already set
CONFIG_FSNOTIFY is already set
CONFIG_DNOTIFY is already set
CONFIG_INOTIFY_USER is already set
CONFIG_FANOTIFY is already set
CONFIG_FANOTIFY_ACCESS_PERMISSIONS is already set
CONFIG_KEYS is already set
CONFIG_SWAP is already set
CONFIG_VT is already set
CONFIG_VT_CONSOLE is already set
CONFIG_SECCOMP is already set
CONFIG_SECURITY is already set
CONFIG_SECURITYFS is already set
CONFIG_SECURITY_NETWORK is already set
CONFIG_NETLABEL is already set
CONFIG_SECURITY_PATH is already set
CONFIG_SECURITY_SELINUX is already set
CONFIG_SECURITY_SELINUX_BOOTPARAM is already set
CONFIG_SECURITY_SELINUX_DISABLE is already set
CONFIG_SECURITY_SELINUX_DEVELOP is already set
CONFIG_SECURITY_SELINUX_AVC_STATS is already set
CONFIG_SECURITY_SMACK is already set
CONFIG_SECURITY_TOMOYO is already set
CONFIG_DEFAULT_SECURITY_APPARMOR is already set
CONFIG_SECURITY_APPARMOR is already set
CONFIG_SECURITY_APPARMOR_HASH is already set
CONFIG_SECURITY_APPARMOR_UNCONFINED_INIT is already set
CONFIG_SECURITY_YAMA is already set
CONFIG_SECURITY_YAMA_STACKED is already set
CONFIG_STRICT_DEVMEM is already set
CONFIG_SYN_COOKIES is already set
CONFIG_BT is already set
CONFIG_BT_RFCOMM is already set
CONFIG_BT_RFCOMM_TTY is already set
CONFIG_BT_BNEP is already set
CONFIG_BT_BNEP_MC_FILTER is already set
CONFIG_BT_BNEP_PROTO_FILTER is already set
CONFIG_BT_HIDP is already set
CONFIG_XFRM_USER is already set
CONFIG_NET_KEY is already set
CONFIG_INET is already set
CONFIG_IP_ADVANCED_ROUTER is already set
CONFIG_IP_MULTIPLE_TABLES is already set
CONFIG_INET_AH is already set
CONFIG_INET_ESP is already set
CONFIG_INET_IPCOMP is already set
CONFIG_INET_XFRM_MODE_TRANSPORT is already set
CONFIG_INET_XFRM_MODE_TUNNEL is already set
CONFIG_INET_XFRM_MODE_BEET is already set
CONFIG_IPV6 is already set
CONFIG_INET6_AH is already set
CONFIG_INET6_ESP is already set
CONFIG_INET6_IPCOMP is already set
CONFIG_INET6_XFRM_MODE_TRANSPORT is already set
CONFIG_INET6_XFRM_MODE_TUNNEL is already set
CONFIG_INET6_XFRM_MODE_BEET is already set
CONFIG_IPV6_MULTIPLE_TABLES is already set
CONFIG_NETFILTER is already set
CONFIG_NETFILTER_ADVANCED is already set
CONFIG_NETFILTER_NETLINK is already set
CONFIG_NETFILTER_NETLINK_ACCT is already set
CONFIG_NETFILTER_NETLINK_LOG is already set
CONFIG_NETFILTER_NETLINK_QUEUE is already set
CONFIG_NETFILTER_TPROXY is already set
CONFIG_NETFILTER_XTABLES is already set
CONFIG_NETFILTER_XT_CONNMARK is already set
CONFIG_NETFILTER_XT_MARK is already set
CONFIG_NETFILTER_XT_MATCH_ADDRTYPE is already set
CONFIG_NETFILTER_XT_MATCH_CLUSTER is already set
CONFIG_NETFILTER_XT_MATCH_COMMENT is already set
CONFIG_NETFILTER_XT_MATCH_CONNBYTES is already set
CONFIG_NETFILTER_XT_MATCH_CONNLIMIT is already set
CONFIG_NETFILTER_XT_MATCH_CONNMARK is already set
CONFIG_NETFILTER_XT_MATCH_CONNTRACK is already set
CONFIG_NETFILTER_XT_MATCH_CPU is already set
CONFIG_NETFILTER_XT_MATCH_DCCP is already set
CONFIG_NETFILTER_XT_MATCH_DEVGROUP is already set
CONFIG_NETFILTER_XT_MATCH_DSCP is already set
CONFIG_NETFILTER_XT_MATCH_ECN is already set
CONFIG_NETFILTER_XT_MATCH_ESP is already set
CONFIG_NETFILTER_XT_MATCH_HASHLIMIT is already set
CONFIG_NETFILTER_XT_MATCH_HELPER is already set
CONFIG_NETFILTER_XT_MATCH_HL is already set
CONFIG_NETFILTER_XT_MATCH_IPRANGE is already set
CONFIG_NETFILTER_XT_MATCH_LENGTH is already set
CONFIG_NETFILTER_XT_MATCH_LIMIT is already set
CONFIG_NETFILTER_XT_MATCH_MAC is already set
CONFIG_NETFILTER_XT_MATCH_MARK is already set
CONFIG_NETFILTER_XT_MATCH_MULTIPORT is already set
CONFIG_NETFILTER_XT_MATCH_NFACCT is already set
CONFIG_NETFILTER_XT_MATCH_OSF is already set
CONFIG_NETFILTER_XT_MATCH_OWNER is already set
CONFIG_NETFILTER_XT_MATCH_PKTTYPE is already set
CONFIG_NETFILTER_XT_MATCH_POLICY is already set
CONFIG_NETFILTER_XT_MATCH_QUOTA is already set
CONFIG_NETFILTER_XT_MATCH_QUOTA2 is already set
CONFIG_NETFILTER_XT_MATCH_RATEEST is already set
CONFIG_NETFILTER_XT_MATCH_REALM is already set
CONFIG_NETFILTER_XT_MATCH_RECENT is already set
CONFIG_NETFILTER_XT_MATCH_SCTP is already set
CONFIG_NETFILTER_XT_MATCH_SOCKET is already set
CONFIG_NETFILTER_XT_MATCH_STATE is already set
CONFIG_NETFILTER_XT_MATCH_STATISTIC is already set
CONFIG_NETFILTER_XT_MATCH_STRING is already set
CONFIG_NETFILTER_XT_MATCH_TCPMSS is already set
CONFIG_NETFILTER_XT_MATCH_TIME is already set
CONFIG_NETFILTER_XT_MATCH_U32 is already set
CONFIG_NETFILTER_XT_TARGET_AUDIT is already set
CONFIG_NETFILTER_XT_TARGET_CHECKSUM is already set
CONFIG_NETFILTER_XT_TARGET_CLASSIFY is already set
CONFIG_NETFILTER_XT_TARGET_CONNMARK is already set
CONFIG_NETFILTER_XT_TARGET_CONNSECMARK is already set
CONFIG_NETFILTER_XT_TARGET_CT is already set
CONFIG_NETFILTER_XT_TARGET_DSCP is already set
CONFIG_NETFILTER_XT_TARGET_HL is already set
CONFIG_NETFILTER_XT_TARGET_IDLETIMER is already set
CONFIG_NETFILTER_XT_TARGET_LED is already set
CONFIG_NETFILTER_XT_TARGET_LOG is already set
CONFIG_NETFILTER_XT_TARGET_MARK is already set
CONFIG_NETFILTER_XT_TARGET_NFLOG is already set
CONFIG_NETFILTER_XT_TARGET_NFQUEUE is already set
CONFIG_NETFILTER_XT_TARGET_NOTRACK is already set
CONFIG_NETFILTER_XT_TARGET_RATEEST is already set
CONFIG_NETFILTER_XT_TARGET_SECMARK is already set
CONFIG_NETFILTER_XT_TARGET_TCPMSS is already set
CONFIG_NETFILTER_XT_TARGET_TCPOPTSTRIP is already set
CONFIG_NETFILTER_XT_TARGET_TEE is already set
CONFIG_NETFILTER_XT_TARGET_TPROXY is already set
CONFIG_NETFILTER_XT_TARGET_TRACE is already set
CONFIG_NF_CONNTRACK_ZONES is already set
CONFIG_IP6_NF_FILTER is already set
CONFIG_IP6_NF_IPTABLES is already set
CONFIG_IP6_NF_MANGLE is already set
CONFIG_IP6_NF_MATCH_AH is already set
CONFIG_IP6_NF_MATCH_EUI64 is already set
CONFIG_IP6_NF_MATCH_FRAG is already set
CONFIG_IP6_NF_MATCH_HL is already set
CONFIG_IP6_NF_MATCH_IPV6HEADER is already set
CONFIG_IP6_NF_MATCH_MH is already set
CONFIG_IP6_NF_MATCH_OPTS is already set
CONFIG_IP6_NF_MATCH_RPFILTER is already set
CONFIG_IP6_NF_MATCH_RT is already set
CONFIG_IP6_NF_QUEUE is already set
CONFIG_IP6_NF_RAW is already set
CONFIG_IP6_NF_SECURITY is already set
CONFIG_IP6_NF_TARGET_HL is already set
CONFIG_IP6_NF_TARGET_REJECT is already set
CONFIG_IP6_NF_TARGET_REJECT_SKERR is already set
CONFIG_DNS_RESOLVER is already set
CONFIG_IOSCHED_DEADLINE is already set
CONFIG_SUSPEND_TIME is already set
CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS is already set
CONFIG_CONSOLE_TRANSLATIONS is already set
CONFIG_EVM is already set
CONFIG_INTEGRITY_SIGNATURE is already set
CONFIG_FHANDLE is already set
CONFIG_DEFAULT_SECURITY="apparmor" is already set
CONFIG_SECURITY_APPARMOR_BOOTPARAM_VALUE=1 is already set
CONFIG_SECURITY_SELINUX_BOOTPARAM_VALUE=0 is already set
CONFIG_SECURITY_SELINUX_CHECKREQPROT_VALUE=1 is already set
CONFIG_SECURITY_TOMOYO_MAX_ACCEPT_ENTRY=2048 is already set
CONFIG_SECURITY_TOMOYO_MAX_AUDIT_LOG=1024 is already set
CONFIG_SECURITY_TOMOYO_POLICY_LOADER="/sbin/tomoyo-init" is already set
CONFIG_SECURITY_TOMOYO_ACTIVATION_TRIGGER="/sbin/init" is already set
CONFIG_SECURITY_APPARMOR_BOOTPARAM_VALUE=1 is already set
CONFIG_DEFAULT_MMAP_MIN_ADDR=32768 is already set
CONFIG_DEFAULT_IOSCHED="deadline" is already set
CONFIG_EVM_HMAC_VERSION=2 is already set
CONFIG_ANDROID_PARANOID_NETWORK is already unset
CONFIG_DEFAULT_SECURITY_DAC is already unset
CONFIG_DEFAULT_SECURITY_SELINUX is already unset
CONFIG_DEFAULT_SECURITY_TOMOYO is already unset
CONFIG_DEFAULT_SECURITY_YAMA is already unset
CONFIG_DEFAULT_SECURITY_SMACK is already unset
CONFIG_SECURITY_APPARMOR_STATS is already unset
CONFIG_SECURITY_SELINUX_POLICYDB_VERSION_MAX is already unset
CONFIG_SECURITY_TOMOYO_OMIT_USERSPACE_LOADER is already unset
CONFIG_BT_HCIBTUSB is already unset
CONFIG_BT_HCIBTSDIO is already unset
CONFIG_BT_HCIUART is already unset
CONFIG_BT_HCIBCM203X is already unset
CONFIG_BT_HCIBPA10X is already unset
CONFIG_BT_HCIBFUSB is already unset
CONFIG_BT_HCIVHCI is already unset
CONFIG_BT_MRVL is already unset
CONFIG_AF_RXRPC is already unset
CONFIG_KEYS_DEBUG_PROC_KEYS is already unset
CONFIG_XFRM_MIGRATE is already unset
CONFIG_XFRM_STATISTICS is already unset
CONFIG_XFRM_SUB_POLICY is already unset
CONFIG_COMPAT_BRK is already unset
CONFIG_DEVKMEM is already unset
CONFIG_NETFILTER_DEBUG is already unset
CONFIG_IP_SET is already unset
CONFIG_IP_VS is already unset
CONFIG_RT_GROUP_SCHED is already unset
CONFIG_ARM_UNWIND is set, unset it
CONFIG_VT_HW_CONSOLE_BINDING is already unset
CONFIG_FRAMEBUFFER_CONSOLE is already unset
CONFIG_SPEAKUP is already unset
CONFIG_CIFS_UPCALL is already unset
CONFIG_CIFS_DFS_UPCALL is already unset
CONFIG_KGDB is already unset
Config file checked, found 1 errors that I did not fix.
Click to expand...
Click to collapse
I going to share kernel and kernel modules with you in hope you get something usefull from all of them, at least hope somebody get Ubuntu touch working on our device, I never tried and probably will not try until somebody get initial port. Things coming without ramdisk so only kernel and modules! Enjoy!
Curent kernel have fully ported latest Apparmor version 3, so before you going to try Ubuntu touch you can disable apparmor by adding apparmor=0 parameter to the kernel cmdline inside boot.img since if something is not configured coreclty in your Ubuntu port related to the apparmor it will not boot, so disable apparmor until you get initial port of the Ubuntu working.
Base kernel source code: https://github.com/sonyxperiadev/kernel-copyleft/tree/14.4.A.0.xxx
Patches in attachment!
Complete things related to kernel for Ubuntu touch you can download from here -> http://forum.xda-developers.com/showpost.php?p=59159143&postcount=8
You can post here everything related to Ubuntu Touch since our thread is not DEV thread so everytbody can post here!
Have you tried doing this with unified kernel? Maybe it's a caf kernel problem so let's use a version with a newer caf tag
I tried nothing! Only backported newer apparmor and other dependent things, than enabled all needed builtin modules needed for Ubuntu. Our kernel is from stock source...
Only which I have tried is chroot of the latest ubuntu but it was not Touch one, have installed gnome desktop environment and vncserver for remote connection, must say its running realy solid on our device Thinking to try real ubuntu without desktop environment and without android stufs but for that I will need to setup everything before make new ramdisk which will start everything, startup services, networking... etc, do not know if it is possible by now since our phone reguire some things on boot like TAD and friends (maybe not need since maybe I can modify recovery ramdisk and use them in combination with ubuntu ramdisk)... but it will be realy great having real ubuntu server on an small phone, just idea
Allso will be great having ubuntu touch, at least initial port
Anybody know is any open source dispaly driver exist for arm? I had seen them in htc hd2 forum, it was ported to the htc hd2 sucesfully and it was open source, but I have no luck finding these posts, maybe somebody help me finding these source code?
Edit:
found another https://freedreno.github.io/ seems interesting
Edit 2:
Freedreno is not working
xorg log:
[ 7019.636] (II) LoadModule: "freedreno"
[ 7019.637] (II) Loading /usr/lib/xorg/modules/drivers/freedreno_drv.so
[ 7019.645] (II) Module freedreno: vendor="X.Org Foundation"
[ 7019.645] compiled for 1.14.1, module version = 0.0.1
[ 7019.645] ABI class: X.Org Video Driver, version 14.1
[ 7019.645] (EE) module ABI major version (14) doesn't match the server's version (18)
[ 7019.645] (II) UnloadModule: "freedreno"
[ 7019.645] (II) Unloading freedreno
[ 7019.645] (EE) Failed to load module "freedreno" (module requirement mismatch, 0)
Click to expand...
Click to collapse
Edit 3:
Seems fb0 will work:
[ 7465.346] (II) Module evdev: vendor="X.Org Foundation"
[ 7465.346] compiled for 1.16.0, module version = 2.9.0
[ 7465.346] Module class: X.Org XInput Driver
[ 7465.346] ABI class: X.Org XInput driver, version 21.0
[ 7465.346] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 7465.346] (II) FBDEV: driver for framebuffer: fbdev
[ 7465.347] (--) using VT number 1
[ 7465.347] (WW) Falling back to old probe method for modesetting
[ 7465.347] (EE) open /dev/dri/card0: No such file or directory
[ 7465.347] (WW) Falling back to old probe method for fbdev
[ 7465.347] (II) Loading sub module "fbdevhw"
[ 7465.347] (II) LoadModule: "fbdevhw"
[ 7465.347] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 7465.348] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 7465.348] compiled for 1.16.0, module version = 0.0.2
[ 7465.348] ABI class: X.Org Video Driver, version 18.0
[ 7465.348] (II) FBDEV(0): using default device
[ 7465.348] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[ 7465.348] (II) FBDEV(0): Creating default Display subsection in Screen section
"Screen" for depth/fbbpp 24/32
[ 7465.348] (==) FBDEV(0): Depth 24, (==) framebuffer bpp 32
[ 7465.348] (==) FBDEV(0): RGB weight 888
[ 7465.348] (==) FBDEV(0): Default visual is TrueColor
[ 7465.348] (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0)
[ 7465.348] (II) FBDEV(0): hardware: mdssfb_90000 (video memory: 8192kB)
[ 7465.348] (II) FBDEV(0): checking modes against framebuffer device...
[ 7465.348] (II) FBDEV(0): checking modes against monitor...
[ 7465.348] (--) FBDEV(0): Virtual size is 720x1280 (pitch 720)
[ 7465.348] (**) FBDEV(0): Built-in mode "current": 2.3 MHz, 2.7 kHz, 2.0 Hz
[ 7465.348] (II) FBDEV(0): Modeline "current"x0.0 2.34 720 768 816 864 1280 1312 1344 1376 -hsync -vsync -csync (2.7 kHz b)
[ 7465.348] (==) FBDEV(0): DPI set to (96, 96)
[ 7465.348] (II) Loading sub module "fb"
[ 7465.348] (II) LoadModule: "fb"
[ 7465.349] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 7465.357] (II) Module fb: vendor="X.Org Foundation"
[ 7465.357] compiled for 1.16.0, module version = 1.0.0
[ 7465.357] ABI class: X.Org ANSI C Emulation, version 0.4
[ 7465.357] (**) FBDEV(0): using shadow framebuffer
[ 7465.357] (II) Loading sub module "shadow"
[ 7465.357] (II) LoadModule: "shadow"
[ 7465.357] (II) Loading /usr/lib/xorg/modules/libshadow.so
[ 7465.359] (II) Module shadow: vendor="X.Org Foundation"
[ 7465.359] compiled for 1.16.0, module version = 1.1.0
[ 7465.359] ABI class: X.Org ANSI C Emulation, version 0.4
[ 7465.359] (II) UnloadModule: "modesetting"
[ 7465.359] (II) Unloading modesetting
[ 7465.359] (==) Depth 24 pixmap format is 32 bpp
[ 7465.628] (==) FBDEV(0): Backing store enabled
[ 7465.630] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[ 7465.630] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[ 7465.630] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[ 7465.631] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[ 7465.631] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[ 7465.631] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[ 7465.631] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[ 7465.631] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[ 7465.632] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[ 7465.632] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
Click to expand...
Click to collapse
Edit 4:
We can compile byself lol http://dri.freedesktop.org/libdrm/
In case somebody need abi file which is missing, I have made small php script which will convert Module.symvers into for example abi-3.4.0-perf-g200b2e0
Code:
<?php
$aa = file('Module.symvers');
$bb = fopen("abi-3.4.0-perf-g200b2e0", "wb");
$patterns = array("/\s+/", "/\s([?.!])/");
$replacer = array(" ", "$1");
for ($i=0; $i < count($aa); $i++) {
$aa[$i] = preg_replace($patterns, $replacer, trim($aa[$i]));
list($a, $b, $c, $d) = explode(' ', $aa[$i]);
$aa[$i] = "$b $d $a $c";
}
$array_lowercase = array_map('strtolower', $aa);
array_multisort($array_lowercase, SORT_ASC, SORT_STRING, $aa);
for ($i=0; $i < count($aa); $i++) {
list($a, $b, $c, $d) = explode(' ', $aa[$i]);
fwrite($bb, "$b $d $c $a\n");
}
fclose($bb);
echo "file <b style='color: red'>abi-3.4.0-perf-g200b2e0</b> created.";
?>
And here is a complete boot deb package of the curent kernel + abi file (put them into boot folder) needed for Ubuntu touch, you can use them for building from UT repo.
for_boot_img.zip (zImahe and dtb) is files needed for boot.img
What is need for building Ubuntu touch? You need:
1. Ubuntu machive, I sugesting Utopic 14.04 or 14.10
2. you need gcc 4.8 since you will get error at start of compilation, so install gcc 4.8 first:
Code:
sudo apt-get install python-software-properties
sudo add-apt-repository ppa:ubuntu-toolchain-r/test
sudo apt-get update
sudo apt-get install gcc-4.8
3. update the rest:
Code:
sudo apt-get install git gnupg flex bison gperf build-essential \
zip bzr curl libc6-dev libncurses5-dev:i386 x11proto-core-dev \
libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-glx:i386 \
libgl1-mesa-dev g++-multilib mingw32 tofrodos \
python-markdown libxml2-utils xsltproc zlib1g-dev:i386 schedtool g++-4.8-multilib
4. sudo add-apt-repository ppa:ubuntu-sdk-team/ppa && apt-get update
5. sudo apt-get install ubuntu-device-flash
6. sudo apt-get install phablet-tools
7. download main repository:
Code:
mkdir -p /path/to/phablet; cd /path/to/phablet
repo init -u https://code-review.phablet.ubuntu.com/p/aosp/platform/manifest.git -b phablet-4.4.2_r1
repo sync -j 8
after this go to devices/lge/mako and look what need to be implemented or removed
8. since our device never had ubuntu touch port we probably can use things from nexus 4 (mako) which is very similar to our phone
9. modify mako source and add/remove all things needed for our device (of corse using and comparing working device tree source code from AOSP for our phone)
10. build
I tried but only tried, nothing more, to build mako and it was sucesfully built! I am lazy to start doing modification for z1c but hope somebody do this and make things initialy ported and booted, after that I will try to get more, I am lazy by now sorry
munjeni said:
8. since our device never had ubuntu touch port we probably can use things from nexus 4 (mako) which is very similar to our phone
Click to expand...
Click to collapse
Isn't it easier to use nexus 5 (hammerhead) sources? It has same CPU and GPU.
Casserole said:
Isn't it easier to use nexus 5 (hammerhead) sources? It has same CPU and GPU.
Click to expand...
Click to collapse
Probably yes, but not sure about screen resolution. If we use mako Ubuntu touch prebuilt, it have the same screen resolution. I don't know realy what is a best choice
munjeni said:
it have the same screen resolution
Click to expand...
Click to collapse
Nope. Z1c has 720x1280 rersolution and nexus 4 has 768x1280.
Are there any chances for us to get an Ubuntu Touch build with working cellular-Parts?
In short, if you expect that from me than no since I have no free time and I am lazy to start working on device tree based on mako, if you realy want ubuntu touch you must do an initial port and I will continue on your initial port, by now I don't see interesents for ubuntu touch here. Maybe I am wrong but I think here nobody is interesting for ubuntu?
0090
munjeni said:
In short, if you expect that from me than no since I have no free time and I am lazy to start working on device tree based on mako, if you realy want ubuntu touch you must do an initial port and I will continue on your initial port, by now I don't see interesents for ubuntu touch here. Maybe I am wrong but I think here nobody is interesting for ubuntu?
Click to expand...
Click to collapse
this thread already have 900 views. I think there's interest in ubuntu touch, but the real thing is that aren't much developers in this community except for u and OmarEinea as i can tell. i really like ur work and i'm very grateful for it, so i hope that u can keep contributing to this community. :good: :highfive: (i'm not asking for anything)
Greetings from Chile.
Thats realy sad. I lost my will on everything on this device and I am now totaly lazy for everything probably I will buy ubuntu phone like old nexus 4 Not only z1c, booth z2 and z3 line have low development and team development activity, stil have no idea why its happening. Today I have played with kernel, wanted to enable framebufer console, enabled them and was not suprised, it was not working. Googled and found that there is nothing about mdss_fb device related to sucesfully enabled framebufer console, seems mdss devices have no luck getting them working. So my idea for having native ubuntu on our device disapointed me since I don't know how to debug initial port when it won't boot. Having working framebufer console and realtime dmesg on screen will be of main help in making initial port, without them I no want to waste my time, so if anybody realy want to contribute and help than I am here and waiting
Definitely something strange happening on fb0, I can blank them but can not display anything on screen by writing to fb0, seems an wakelock happening here?
Testing "cat /dev/urandom > /dev/graphics/fb0" on android not working, but in recovery mode its working sometimes
munjeni said:
Testing "cat /dev/urandom > /dev/graphics/fb0" on android not working, but in recovery mode its working sometimes
Click to expand...
Click to collapse
Why are you writing random to the framebuffer? Lol.
Rekoil said:
Why are you writing random to the framebuffer? Lol.
Click to expand...
Click to collapse
I am using urandom, not random, just for seeing random data on screen, its working now and I want to let you know guys that I have done initial port built from source code!
Screenshoots: