Hi All,
Firstly thanks to all the people here and at handhelds.org for Linux on my devices. Thanks for WM2005 on my Himalaya. Thanks for WM2005 for my Blue Angel. Thanks for custom ROMS. And thanks for all your hard work, time, dedication and skill. Long may you all excel.
So anyway, I have just managed to get GPE running on both my Himalaya and my Blue Angel after many startup.txt files, soldering up my own serial cable, and compiling the kernels many times over. At last! It works!
However, now I have another problem. I can't get the usbnet module to detect either of my PDAs when I cradle them to my Open SuSE 10 desktop.
Am I right in believing that all I should have to do is drop the device in the cradle, then "#modprobe usbnet" ?
Now you will have to bare with me as I have only been using Linux for 4-5 months, so I am still learning. If I run lsmod I can see a reference to an ipaq module under usbcore, but under usbnet there is nothing.
#lsmod
Module Size Used by
nls_iso8859_1 4096 0
nls_cp437 5760 0
vfat 12800 0
fat 49692 1 vfat
subfs 7552 0
sg 35744 0
sd_mod 18576 0
usb_storage 72640 0
scsi_mod 131304 3 sg,sd_mod,usb_storage
ipaq 31376 0
usbserial 28776 1 ipaq
ppdev 8964 0
ipt_pkttype 1664 1
ipt_LOG 6912 8
ipt_limit 2304 8
vmnet 35236 9
vmmon 110220 0
speedstep_lib 4228 0
freq_table 4612 0
snd_pcm_oss 59168 0
snd_mixer_oss 18944 1 snd_pcm_oss
snd_seq 51984 0
button 7056 0
battery 10244 0
ac 5252 0
af_packet 21384 0
edd 9824 0
usbhid 43616 0
ide_cd 39684 0
cdrom 36896 1 ide_cd
snd_via82xx 28096 1
gameport 14600 1 snd_via82xx
ip6t_REJECT 5504 3
snd_ac97_codec 91004 1 snd_via82xx
i2c_viapro 8080 0
i2c_core 20368 1 i2c_viapro
via_ircc 22164 0
irda 115000 1 via_ircc
crc_ccitt 2176 1 irda
ipt_REJECT 5632 3
ehci_hcd 32136 0
ipt_state 1920 12
via_rhine 22276 0
snd_ac97_bus 2432 1 snd_ac97_codec
snd_pcm 93064 3 snd_pcm_oss,snd_via82xx,snd_ac97_codec
snd_timer 24452 2 snd_seq,snd_pcm
snd_page_alloc 10632 2 snd_via82xx,snd_pcm
snd_mpu401_uart 7296 1 snd_via82xx
snd_rawmidi 24864 1 snd_mpu401_uart
snd_seq_device 8588 2 snd_seq,snd_rawmidi
via_agp 9472 1
agpgart 33096 1 via_agp
generic 4484 0 [permanent]
snd 60420 12 snd_pcm_oss,snd_mixer_oss,snd_seq,snd_via82xx,snd_ac97_codec,snd_pcm,snd_timer,snd_mpu401_uart,snd_rawmidi,snd_seq_device
soundcore 9184 1 snd
uhci_hcd 32016 0
shpchp 88676 0
pci_hotplug 26164 1 shpchp
iptable_mangle 2688 0
iptable_nat 22228 0
iptable_filter 2816 1
ip6table_mangle 2304 0
ip_conntrack 42168 2 ipt_state,iptable_nat
ip_tables 19456 8 ipt_pkttype,ipt_LOG,ipt_limit,ipt_REJECT,ipt_state,iptable_mangle,iptable_nat,iptable_filter
ip6table_filter 2688 1
ip6_tables 18176 3 ip6t_REJECT,ip6table_mangle,ip6table_filter
ipv6 242752 128 ip6t_REJECT
parport_pc 38980 1
lp 11460 0
parport 33864 3 ppdev,parport_pc,lp
usbnet 32648 0
usbcore 112512 8 usb_storage,ipaq,usbserial,usbhid,ehci_hcd,uhci_hcd,usbnet
mii 5504 2 via_rhine,usbnet
ext3 130440 1
jbd 59940 1 ext3
dm_mod 54972 0
reiserfs 250480 1
fan 4996 0
thermal 14472 0
processor 24512 1 thermal
via82cxxx 13212 0 [permanent]
it821x 8452 0 [permanent]
ide_disk 17152 5
ide_core 122380 6 usb_storage,ide_cd,generic,via82cxxx,it821x,ide_disk
I also know the device is there because if i run lsusb I get this
# lsusb
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 002: ID 045e:00b9 Microsoft Corp. Wireless Optical Mouse 3.0
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 011: ID 0bb4:0a02 High Tech Computer Corp. Himalaya GSM/GPRS Pocket PC
Bus 001 Device 003: ID 045e:0059 Microsoft Corp. Wireless IntelliMouse Explorer
Bus 001 Device 001: ID 0000:0000
I don't really understand what I need to do, and I am having a hard time googling up any info, everyone else for the most part seems to load it without any problems.
Any help would be more than welcome. Thanks again everyone
Alpha_Geek
Related
Hi there,
I am trying to get Linux running on a handheld which uses the HTC bootloader and it would be great if one of the gurus here could give me some hints about using IDA on the bootloader (to find out how buttons and USB are controlled).
The handheld is Dell Axim X50 (PXA270, big ASIC,some CPLD, beside that pretty standard)-for more hardware details take a look at: http://handhelds.org/moin/moin.cgi/DellAximX50
I already identified where the bootloader loads itself into RAM and configures and enables the MMU, I modified the available .idc script (for PXA2xx-regs) to show me nice synonymes instead of the raw register addresses. I traced a little bit through the code - but only seeing lots of operations on RAM addresses and very few (far too few IMO) and very general operations on processor registers doesn't help much. I expect that the register addresses are partly loaded from RAM instead of beeing hard coded.
So now to my question: is there a way to "copy" the into RAM loaded ROM parts in IDA? I mean so that IDA can actually find the data which is supposed to be in RAM right before MMU is enabled and that I can see references to the GPIO/ASIC/CPLD addresses and to the string data (which would greatly help in identifying the useful functions).
Thanks for any hints or advices!
pphoenixx said:
The handheld is Dell Axim X50 (PXA270, big ASIC,some CPLD, beside that pretty standard)-for more hardware details take a look at: http://handhelds.org/moin/moin.cgi/DellAximX50
Click to expand...
Click to collapse
Hi,
a lot of information can be obtained without any disassembling.
I'm curious, if have the "dump gpio" haret output somewhere ?
here you go:
http://www.bfamily.us/~richard/tmp/arm/gpio_map.xml
Code:
GPIO# D S A INTER | GPIO# D S A INTER | GPIO# D S A INTER | GPIO# D S A INTER
------------------+-------------------+-------------------+------------------
0 I 0 0 RE FE | 21 O 1 1 | 42 O 0 0 | 63 O 0 0
1 I 1 0 | 22 O 0 0 | 43 O 0 0 | 64 O 0 0
2 O 1 0 | 23 O 0 2 | 44 O 0 0 | 65 O 0 0
3 O 1 0 | 24 O 1 2 | 45 O 0 0 | 66 O 0 0
4 O 1 0 | 25 O 0 2 | 46 I 1 2 | 67 O 0 0
5 I 1 0 | 26 I 1 1 | 47 O 0 1 | 68 O 0 0
6 I 1 0 | 27 I 0 0 | 48 O 1 2 | 69 O 0 0
7 I 1 0 | 28 O 0 0 | 49 O 1 2 | 70 O 0 0
8 I 1 0 | 29 O 0 0 | 50 O 1 2 | 71 O 0 0
9 O 1 1 | 30 O 0 0 | 51 O 1 2 | 72 O 0 0
10 O 0 1 | 31 O 0 0 | 52 I 1 0 | 73 O 0 0
11 I 0 0 RE FE | 32 O 0 0 | 53 O 1 0 | 74 O 0 0
12 I 1 0 RE FE | 33 O 1 2 | 54 O 1 2 | 75 O 0 0
13 I 0 0 RE | 34 O 0 0 | 55 O 1 2 | 76 O 0 0
14 I 1 0 RE FE | 35 O 0 0 | 56 I 1 1 | 77 O 0 0
15 O 1 2 | 36 O 1 0 | 57 I 1 1 | 78 O 1 2
16 O 0 0 | 37 O 0 0 | 58 O 0 0 | 79 O 1 2
17 O 1 2 | 38 I 0 0 | 59 O 0 0 | 80 O 1 2
18 I 1 1 | 39 O 0 0 | 60 O 0 0 | 81 O 0 0
19 O 1 0 | 40 O 0 0 | 61 O 0 0 | 82 O 0 0
20 O 1 1 | 41 O 0 0 | 62 O 0 0 | 83 I 0 0 RE FE
There is already much accomplished - A 2.6.15-rc7 kernel boots without problem, working framebuffer and I can activate IRDA and use it for console.. everything directly connected to the PXA is no issue; the ASIC and CPLDs are my major problem right now - that's why I throw myself into disassembling.
pphoenixx said:
There is already much accomplished - A 2.6.15-rc7 kernel boots without problem, working framebuffer and I can activate IRDA and use it for console.. everything directly connected to the PXA is no issue; the ASIC and CPLDs are my major problem right now - that's why I throw myself into disassembling.
Click to expand...
Click to collapse
Ok. You are using PXA270 SDIO.
We are also moving forward, but have some problems with the framebuffer.
http://wiki.xda-developers.com/index.php?pagename=UniversalResearch
http://wiki.xda-developers.com/index.php?pagename=UniversalProgress
Do you know how the wifi chip is connected ? Is it on pcmcia ?
FYI, we have a weird CPLD too.
cr2 said:
Do you know how the wifi chip is connected ? Is it on pcmcia ?
FYI, we have a weird CPLD too.
Click to expand...
Click to collapse
well, looking at
Code:
HaRET(29)# pd 0x48000014 1
48000014 | 00000003 | ....
PC Card Is Present
This bit must be written by software when either PC Card is inserted into a
socket.
0 = No PC Card inserted
1 = PC Card inserted
0 R/W NOS
PC Card Interface Number of Sockets
0 = 1 socket
1 = 2 sockets
Click to expand...
Click to collapse
one could assume that at least something is sitting on pcmcia. and if I write a 0x0 in there - WIFI is suddenly gone while the device remains responsive (= hasn't crashed). So at least on the axim, I suppose it's on pcmcia.
pphoenixx said:
Code:
HaRET(29)# pd 0x48000014 1
48000014 | 00000003 | ....
Click to expand...
Click to collapse
The same here. But i can zero it while running over wlan.
Maybe you disabled something else and WIFI is connected via USB1.1 (try to disable USB)? or your WIFI chip is connected via socket 1 (which can't be disabled) - I tried to write a 0x1 in there (no PC CARD) and WIFI remained operational, it's only gone when I completly disabled socket2 (0x0).
It's pcmcia for sure on axim.
If you have the same driver, tiacxwln.dll Version: 2.0.53(NDIS)
Create an empty file: tiacxwln_testmode.txt and put it in your WINDOWS directory and soft-reboot -- on Axim, the driver looks for that file and if it exists the wifi hardware isn't claimed anymore (propably to easly test other drivers or launch special testmode drivers..). WinCE kicks in and recognizes an unknown networking device connected to PCMCIA socket 2.
pphoenixx said:
Create an empty file: tiacxwln_testmode.txt and put it in your WINDOWS directory and soft-reboot -- on Axim, the driver looks for that file and if it exists the wifi hardware isn't claimed anymore (propably to easly test other drivers or launch special testmode drivers..). WinCE kicks in and recognizes an unknown networking device connected to PCMCIA socket 2.
Click to expand...
Click to collapse
ACX100 is used by most PDAs through the PCMCIA (or SDIO) interface.
Unfortunately, the acx100.sf.net driver supports only pci and usb...
ACX100 could be partially initialized on HTC Blueangel, but it is not working yet.
-----
\Storage Card\tiacxwln_testmode.txt
\SD Card\tiacxwln_testmode.txt
\windows\tiacxwln_testmode.txt
Hi all,
View mins ago I setup linux on my HTC.
Well, it does work and i can connect to my device with ssh.
But I have some problems, it cant find the MMC Card (I format it as ext2) on my desktop (debian)
my dmesg
# dmesg
<5>Linux version 2.6.16.27-omap1 ([email protected]) (gcc version 4.1.1) #4 PREEMPT Fri Jan 5 16:56:42 CET 2007
<4>CPU: ARM926EJ-Sid(wb) [41069263] revision 3 (ARMv5TEJ)
<4>Machine: HTC Wizard
<4>Memory policy: ECC disabled, Data cache writeback
<7>On node 0 totalpages: 24576
<7> DMA zone: 24576 pages, LIFO batch:7
<7> DMA32 zone: 0 pages, LIFO batch:0
<7> Normal zone: 0 pages, LIFO batch:0
<7> HighMem zone: 0 pages, LIFO batch:0
<4>Unknown OMAP cpu type: 0x00
<4>OMAP0000 revision 1 handled as 00xx id: 0000000000000000
<6>SRAM: Mapped pa 0x20000000 to va 0xd0000000 size: 0x32000
<4>htc_wizard_map_io done.
<4>CPU0: D VIVT write-back cache
<4>CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
<4>CPU0: D cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets
<4>Built 1 zonelists
<5>Kernel command line: root=/dev/ram0 init=/linuxrc
<4>htc_wizard_init_irq.
<4>Clocks: ARM_SYSST: 0x1040 DPLL_CTL: 0x2793 ARM_CKCTL: 0x6506
<6>Clocking rate (xtal/DPLL1/MPU): 13.0/195.0/195.0 MHz
<4>Total of 96 interrupts in 3 interrupt banks
<6>OMAP730 GPIO hardware
<4>PID hash table entries: 512 (order: 9, 8192 bytes)
<4>Console: colour dummy device 80x30
<4>Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
<4>Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
<6>Memory: 96MB = 96MB total
<5>Memory: 92444KB available (1656K code, 403K data, 96K init)
<7>Calibrating delay loop... 89.70 BogoMIPS (lpj=448512)
<4>Mount-cache hash table entries: 512
<6>CPU: Testing write buffer coherency: ok
<6>checking if image is initramfs...it isn't (no cpio magic); looks like an initrd
<6>Freeing initrd memory: 2604K
<6>NET: Registered protocol family 16
<4>Tornado init.
<4>OMAP730 Watchdog seems to be activated, disabling it for now.
<4>trying to enable USB.
<4>USB_EN to 0 after 0 tries.
<4>MMC host reset done: remaining tries: 100
<6>OMAP DMA hardware version 1
<6>DMA capabilities: 000c0000:00000000:01ff:003f:007f
<4>Initializing OMAP McBSP system
<3>mcbsp: could not acquire dsp_ck handle.
<3>omapdsp: unsupported omap architecture.
<4>USB: hmc 4, usb0 2 wires (dev)
<4>NetWinder Floating Point Emulator V0.97 (double precision)
<6>io scheduler noop registered
<6>io scheduler deadline registered (default)
<4>HTC Tornado Backlight driver.
<4>VSFB Frame buffer driver for HTC OMAP Based Phones.
<6>vsfb: framebuffer at 0x20001020, mapped to 0xc6800020, size 150k
<4>Console: switching to colour frame buffer device 40x29
<6>TI OMAP Watchdog Timer for OMAP730
<4>RAMDISK driver initialized: 1 RAM disks of 8192K size 1024 blocksize
<6>udc: OMAP UDC driver, version: 4 October 2004 (iso)
<6>udc: OMAP UDC rev 3.6
<6>udc: hmc mode 4, integrated transceiver
<6>udc: fifo mode 3, 648 bytes not used
<6>usb0: Ethernet Gadget, version: May Day 2005
<6>usb0: using omap_udc, OUT ep2out-bulk IN ep1in-bulk STATUS ep3in-int
<6>usb0: MAC 9a:17:46:70:a0:3b
<6>usb0: HOST MAC c2:20:66:22:69:ae
<6>mice: PS/2 mouse device common for all mice
<6>OMAP Keypad Driver
<4>omap_kp_probe.
<6>input: omap-keypad as /class/input/input0
<6>NET: Registered protocol family 2
<3>MMC1: Command timeout, CMD0
<4>IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
<4>TCP established hash table entries: 4096 (order: 2, 16384 bytes)
<4>TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
<6>TCP: Hash tables configured (established 4096 bind 4096)
<6>udc: USB reset done, gadget ether
<6>TCP reno registered
<6>TCP bic registered
<6>NET: Registered protocol family 1
<6>NET: Registered protocol family 17
<6>NET: Registered protocol family 15
<5>RAMDISK: Compressed image found at block 0
<6>udc: USB reset done, gadget ether
<6>udc: USB reset done, gadget ether
<6>udc: USB reset done, gadget ether
<6>udc: USB reset done, gadget ether
<6>udc: USB reset done, gadget ether
<6>udc: USB reset done, gadget ether
<6>udc: USB reset done, gadget ether
<6>udc: USB reset done, gadget ether
<6>usb0: full speed config #1: 100 mA, Ethernet Gadget, using CDC Ethernet
<4>VFS: Mounted root (ext2 filesystem).
<6>Freeing init memory: 96K
<6>vsmmfb: ioctl helper driver for framebuffer 0.1.1, Copyright 2007 Thomas Reith
<6>vsmmfb: loaded, got minor 63
Click to expand...
Click to collapse
# df -h
Filesystem Size Used Available Use% Mounted on
/dev/ram0 5.8M 4.4M 1.4M 75% /
Click to expand...
Click to collapse
# mount
/dev/root on / type ext2 (rw,nogrpid)
proc on /proc type proc (rw)
devpts on /dev/pts type devpts (rw)
sysfs on /sys type sysfs (rw)
Click to expand...
Click to collapse
The problem is , even in /dev
mmcblk0
mmcblk0p1
mmcblk0p2
mmcblk0p3
mmcblk0p4
there isnt anything, so if i cant find my mmc, i cant fdisk so i wont have any os.
The next problem is, i dont have gcc?
Because it it not a debian system (i want to) apt wont work, no RPM, just nothing.
How de heck can i compile gcc without gcc? so i can start using my os?
the next thing, but the last one.
When i have my OS ready to play.
It is possible to write it to ram? so it will remove windows and replace it with my linux version?
Any help/tips would be helpfull
thx
MMC and NS.exe on HTC prophet
Hi:
You can activate your sd card using Nico's program sd.exe
Look the web of the linwizard project in sourceforge:
http://sourceforge.net/tracker/index.php?func=detail&aid=1593777&group_id=174107&atid=867988
Luck!!
Sesh maat setep n ra
I've gone from Typhoon CyanogenMod to HyperDroidGBX-v12 and it seems that Hyperdroid keeps connecting to wifi in intervals and waking up the phone which has taken a lot more battery over night than CyanogenMod did. I love the speed of Hyperdroid so I was wondering if there is anything I can do?
When I switched the phone on using Cyanogen I saw him switch off the mobile data connection and switch on wifi. Hyperdroid doesn't seem to manage it like that. Can I customize this?
edit: I found the option under wireless to switch if off when the phone is asleep but I don't think he's doing as he's told (my phone is male, in case you're wondering)...
I've attached a screen of my phone over night with HyperDroid. It kept waking up without the screen being on. I assume that's the root of all evil...
The only app that syncs on my phone atm is the GMail app, no facebook or others.
Any suggestions?
Thanks
edit:
I've searched some more and there were people who's wireless went to sleep when they didn't want it to, the opposite of my problem. I've done a clean install of HyperDroid again and the problem persists, at least the wireless not switching off. Since that worked with CyanogenMod I assume that's the root cause. I'm surprised this hasn't picked up on before, assuming other people have the same problem.
I guess I'd like to know if there are any simple file swaps I can perform like changing drivers between the two mods?
editv2:
Wireless seems to at least switch off now. I tried killing inactive apps. I'll see what happens from here.
Usually it's apps polling for updates.
This includes Facebook, Twitter etc. Are you using Google Latitude? That can wake the device every few minutes.
To check for wakelocks
Code:
cat /proc/wakelocks
It happened again last night that the phone appears awake for quite some time. I've got the wakelocks (which I don't know how to interpret). I'll post them and a screenshot of battery. I'm hoping to either hear a solution or that it's normal.
It seems like he had a much more quiet night tonight. I wish I had paid more attention to it while using Cyanogen. I've installed the battery current widget so that should be interesting as well.
Cheers.
Code:
name count expire_count wake_count active_since total_time sleep_time max_time last_cha
nge
"alarm" 957 0 0 0 23959014779 21546905463 384429936 9723528995498
"wlan_wake" 19027 0 49 0 86119018687 44324798717 1083984373 9683300205212
"main" 17 0 0 0 7736565871862 0 5511280593319 9680620426163
"event4-252" 34973 0 0 0 3475555677 0 6408692 9680155307754
"msmfb_idle_lock" 54032 0 0 0 4743530364 0 278686529 9680154453261
"ds2746-battery" 667 0 0 0 9070099039 8503753803 39886474 9679912631970
"alarm_rtc" 562 8 0 0 63026972383 63025843229 1034118654 8779276859239
"KeyEvents" 35993 0 0 0 4014678958 84869382 86914061 9679667270643
"event3-252" 216 0 0 0 124999996 73455813 16967773 9679666141493
"gpio_input" 52 0 9 0 528106698 122161869 10437012 9679665958387
"event5-252" 284 0 0 0 16235353 0 762939 9675881534557
"usb_mass_storage" 1 0 0 0 229509429930 0 229509429930 9228090579970
"power-supply" 135 0 0 0 70007320 41687016 2685547 9673667392715
"power-supply" 7 0 0 0 6774905 3875733 2532958 9673667209609
"power-supply" 7 0 0 0 10894774 2655028 5859375 9673667087539
"wlan_rx_wake" 1078 1078 0 0 1729369137961 185800921021 21577879641 9670940219862
"qmi" 17 17 0 0 8471907985 1995538327 509357909 9670940189344
"SMD_DATA5" 563 563 120 0 491717996183 412869000741 9329598383 9670940189344
"event0-252" 35776 0 0 0 2916259736 0 3112793 9603342624641
"gpio_kp" 83 0 2 0 14742034892 22491454 1275268561 9585008335097
"AudioHardwareQSDOut" 16 0 0 0 94738861105 704864502 20176086427 8977790592174
"audio_pcm_suspend" 14 0 0 0 211352722187 422058099 35328094487 8977790500621
"audio_pcm_idle" 14 0 0 0 211352630634 0 35328094487 8977790500621
"SMD_RPCCALL" 7382 0 555 0 636077998 468994259 26184081 8977783267956
"rpc_read" 214 0 0 0 6530761 457767 1831054 8977783237438
"ApmCommandThread" 56 0 0 0 1433898924 0 895629880 8825111423477
"radio-interface" 38 0 0 0 41765899679 4004455570 1961944580 8786906162243
"rpc_read" 4429 0 0 0 192779566 184631377 244141 8779275638536
"rpc-interface" 537 0 0 0 889831583 863678015 41290284 8239455598513
"rpc_read" 535 0 0 0 1028228754 170288083 348480225 8239453920046
"AudioHardwareQSDIn" 9 0 0 0 147654846199 0 32158020026 7760196196386
"proximity" 1 1 0 0 3892520753 0 3892520753 5763470148164
"event1-252" 8 0 0 0 274658 0 91552 5734318414763
"mmc_delayed_work" 3 2 0 0 13576922628 0 8541424561 5511892785725
"msm_camera" 2 0 0 0 12680633542 0 10539916988 5504792504962
"msm_camera_wake" 2 0 0 0 12680633542 0 10539916988 5504792504962
"s5k3e2fx" 2 0 0 0 12293823244 0 10387512209 5504791894611
"flashlight" 1 0 0 0 116271973 0 116271973 5472884484944
"rpc_read" 2 0 0 0 70556639 0 41900634 56937371906
"event2-252" 0 0 0 0 0 0 0 0
"SMD_DATA7" 0 0 0 0 0 0 0 0
"SMD_DATA6" 0 0 0 0 0 0 0 0
"port_list" 0 0 0 0 0 0 0 0
"vbus_present" 0 0 0 0 0 0 0 0
"msm_serial_hs_dma" 0 0 0 0 0 0 0 0
"msm_serial_hs_rx" 0 0 0 0 0 0 0 0
"audiojack" 0 0 0 0 0 0 0 0
"headset" 0 0 0 0 0 0 0 0
"microp_i2c_present" 0 0 0 0 0 0 0 0
"rpc_server" 0 0 0 0 0 0 0 0
"rpc_read" 0 0 0 0 0 0 0 0
"vdec_suspend" 0 0 0 0 0 0 0 0
"vdec_idle" 0 0 0 0 0 0 0 0
"i2c" 0 0 0 0 0 0 0 0
"unknown_wakeups" 0 0 0 0 0 0 0 0
"deleted_wake_locks" 193 0 0 0 117065426 0 32287599 0
"kgsl" 2981 0 0 1068695066 4845796179890 688535376655 128397308351 9725263797740
"PowerManagerService" 1061 0 0 52465057371 7525105867782 1338152315208 5239685516362 96738674
65953
"vbus_present" 2 1 0 740221282954 5984945089112 108139678944 5244723806158 8986111270887
"SMD_DS" 176 176 0 0 103807277355 31379227646 1803994144 9680271884899
#
[only mcc models
First flash ota 20110524 to return at original cwm and do wipe data and wipe partion cache
This will make clean instalation
unrar archivehttp://www.mediafire.com/?adu3kmqhxkb8hfi
run nv flash
go recovery
format system
wipe dalvik cache
mount usb
copy update
copy gapps
copy kernel
flash them with same way
done
lcd density at 120
Stable with pershoot tweaks preload
Major bug have been fixed
Sound improved with beats audio
external sdcard fixed
Sleep fixed
Hd video and mkv video format playable with external. Player like mx video
System improved with init.d tweks
new theme ics
camera work with skype
bravia engine drivers added
set 775 permission system/etc/be photo
set 775 permission system/etc/be movie
Kill app via long press choice will help you
To my daughter Jan
malata t8 unofficial cyanogenmod 7.2.0 RC nvflash mode for mcc device
congratulation goes whyberg for that wonderfull work
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Use at your own risk its not my responsibility if brick your device
download firmware
http://www.mediafire.com/?p66bpjp1qeug6vs
download latest gapps
http://www.mediafire.com/?zglnipcv34kdt49
Click to expand...
Click to collapse
unpacks the archive
includes device "-" + "power" (APX mode)
running the batch file download [1GB | 512MB]
after the device goes into overdrive long press power off
includes device "+" + "power" (recovery mode)
now you must input and export usb cable in & out with usb mount from recovery mode until computer regognize your tablet as storage
copy the update zip and gapps zip into
pour through recovery archive with firmware update-cm-7.2.0-RC0-smb_a9701-KANG-signed.zip & and latest gapps on SDCARD
set after "install from SDcard" both before reboot
Click to expand...
Click to collapse
libcamera.so.ziphttp://forum.xda-developers.com/attachment.php?attachmentid=896892&d=1328950465
Installetion via ADB
1. unzip libcamera.so.zip
2. adb remount
3. adb push libcamera.so /system/lib/libcamera.so
Manual
With root explorer paste libcamera.so into
System/lib and give read write permission as the other
Before reboot
Via recovery(libcamera.so-update.zip)http://forum.xda-developers.com/attachment.php?attachmentid=896903&d=1328951238
Skype 2.6.0.95 version worked!!!
Gtalk video not! but in`s not a camera problem...
Click to expand...
Click to collapse
not working
video accelerator
as all gtablet must install externall video code
like
mxvideo apk
Click to expand...
Click to collapse
Best flash player with this rom is 10.3
Working you tube like a charm
New google play without errors
http://i.minus.com/1331477283/iiYu2AW7DQxVWHgoI7qIbA/dJCxyuh2eNq0W.apk
Click to expand...
Click to collapse
you must be carefull
do not partion sd
do not fix permission
it may brick
enjoy
Click to expand...
Click to collapse
confirmed working!!!!!!!
Thanks geowolf........ youre the man
I'd go as far as to say.... Best Malata zpad t8 rom I've found and was easy to install (as per instructions above you need to install zip files BEFORE first boot)
Shame about no camera. Does anyone know of a fix?
I'm off to 4pda. ru to check for updates
camera fix found
hXXp://cyanogenmod.googlecode.com/issues/attachment?aid=44480005000&name=CM07CameraFix.zip&token=HIEuD7abnRfewkHvEaa8YkZSjZg%3A1328138144361
just copy .so files over /system/lib using root explorer and set permissions same as other files
reboot
install included camera.apk if needed
Happy days
Anything for us poor mcb owners?
Hello,
I have an evolio neura tablet, which I understand is the romanian version of malata zpad t8, how do I know which serial I have, because as for as I understand there are two types of models MCB and MCC.
-also because I am new to the android family can someone explain step by step how to upgrade the rom?
Thanks
cociuba said:
Hello,
I have an evolio neura tablet, which I understand is the romanian version of malata zpad t8, how do I know which serial I have, because as for as I understand there are two types of models MCB and MCC.
-also because I am new to the android family can someone explain step by step how to upgrade the rom?
Thanks
Click to expand...
Click to collapse
Hello
There three models mca. Which doesn't use interval memory and was the easy way to upgrade any ron
Mcb its little confuse what type of nand type are use in previous update of official firmware was problem to install mcc nand type sound errors and. Not compatible firmsware
Only if know what type of you use proceed to this
and mcc with interval memory the things are very dangerous .this nvflash regognize your interval memory as SD card and sdcatd turns as emcc folder
Ihave test it to emmc models.
Under the tap of sim card has the type of memory that you use
Open the tap. And has a specification note with numbers
Something like that ( emmc34567886)
i cant find the serial under the gsm tap, is there another posibility of finding it?
cociuba said:
i cant find the serial under the gsm tap, is there another posibility of finding it?
Click to expand...
Click to collapse
At settings
About option
Give a report
Hi geowolf,
Many thanks for what you're doing.
I also have an evolio neura - malata zpad t8 rebranded.
In the "about tablet" option I only have:
Model number - Evopad
Android version - 2.2
Baseband version - R2A11
Kernel version - 2.6.32.0-00252-gf1df521-dirty [email protected] #5
Build number - 20110712_EW
Hope it helps.
Also do you think that we could get ics on this?
Thank you!
this is the result from using one of the updates for the tablet, it seems that the update uses the emmc.bat
c:\neura\neura [email protected]>download_EMMC_1G.bat
c:\neura\neura [email protected]>"nvflash.exe" --bct Malata_a02_12Mhz_H5PS1G83EFR-S6C_ 333Mhz_1GB_emmc_THGBM1G6D4EBAI4_x8.bct --setbct --bl bootloader.bin --configfile android_fastboot_emmc_full_more.cfg --odmdata 0x3c0c0011 --create --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x171411c040a08297
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file:Malata_a02_12Mhz_H5PS1G83EFR-S6C_333Mhz_1GB_emmc_THGBM1G6D4EBAI4_x8.bct - 4080/4080 bytes sent
Malata_a02_12Mhz_H5PS1G83EFR-S6C_333Mhz_1GB_emmc_THGBM1G6D4EBAI4_x8.bct sent successfully
odm data: 0x3c0c0011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
945472/945472 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
Click to expand...
Click to collapse
EE
bungadudu said:
Hi geowolf,
Many thanks for what you're doing.
I also have an evolio neura - malata zpad t8 rebranded.
In the "about tablet" option I only have:
Model number - Evopad
Android version - 2.2
Baseband version - R2A11
Kernel version - 2.6.32.0-00252-gf1df521-dirty [email protected] #5
Build number - 20110712_EW
Hope it helps.
Also do you think that we could get ics on this?
Thank you!
Click to expand...
Click to collapse
One more
Is rooted ?
If open root directory with root explorer is any directory like emmc. emmb ....
China Malata 3g models are mmc
But Russian 3q models has been moderate with erricson 3g spare even are, or not 3g
Maybe and the Romanian models has been modified
With 3g
Try with root explorer to find mount points
And from market android system info has an option to find mount points
Check it out .
Its to early for ice cream
cant find the mount points but I attached diskstat and partition file
diskstat
7 0 loop0 0 0 0 0 0 0 0 0 0 0 0
7 1 loop1 0 0 0 0 0 0 0 0 0 0 0
7 2 loop2 0 0 0 0 0 0 0 0 0 0 0
7 3 loop3 0 0 0 0 0 0 0 0 0 0 0
7 4 loop4 0 0 0 0 0 0 0 0 0 0 0
7 5 loop5 0 0 0 0 0 0 0 0 0 0 0
7 6 loop6 0 0 0 0 0 0 0 0 0 0 0
7 7 loop7 0 0 0 0 0 0 0 0 0 0 0
179 48 mmcblk3 17433 44474 1532199 120670 136737 577806 3635982 18924640 0 1974930 19139480
179 49 mmcblk3p1 4495 282 286484 26080 3 0 6 20 0 15010 26080
179 50 mmcblk3p2 12 61 290 10 133 6864 27988 57350 0 11350 57360
179 51 mmcblk3p3 9 61 278 20 8 1 36 550 0 550 570
179 52 mmcblk3p4 0 0 0 0 0 0 0 0 0 0 0
179 53 mmcblk3p5 0 0 0 0 0 0 0 0 0 0 0
179 54 mmcblk3p6 9475 27970 846506 75240 115761 534552 2610508 14212670 0 1796540 14288720
179 55 mmcblk3p7 5 0 10 10 0 0 0 0 0 10 10
179 56 mmcblk3p8 3432 16100 398591 19310 20832 36389 997444 4654050 0 276190 4766740
254 0 dm-0 40 0 1066 340 0 0 0 0 0 130 340
254 1 dm-1 805 0 74867 14710 0 0 0 0 0 7710 14710
254 2 dm-2 34 0 478 30 0 0 0 0 0 30 30
254 3 dm-3 406 0 37090 4450 0 0 0 0 0 2180 4450
254 4 dm-4 80 0 6210 1040 0 0 0 0 0 330 1040
254 5 dm-5 118 0 6850 3190 0 0 0 0 0 810 3190
254 6 dm-6 635 0 47366 5750 0 0 0 0 0 2640 5750
Click to expand...
Click to collapse
partition
major minor #blocks name
7 0 2111 loop0
7 1 48888 loop1
7 2 2111 loop2
7 3 30177 loop3
7 4 4190 loop4
7 5 7308 loop5
7 6 24980 loop6
179 48 15648768 mmcblk3
179 49 327680 mmcblk3p1
179 50 65536 mmcblk3p2
179 51 32768 mmcblk3p3
179 52 1 mmcblk3p4
179 53 32768 mmcblk3p5
179 54 2097152 mmcblk3p6
179 55 8192 mmcblk3p7
179 56 13081600 mmcblk3p8
254 0 2110 dm-0
254 1 48888 dm-1
254 2 2110 dm-2
254 3 30177 dm-3
254 4 4189 dm-4
254 5 7308 dm-5
254 6 24979 dm-6
Click to expand...
Click to collapse
cociuba said:
cant find the mount points but I attached diskstat and partition file
diskstat
partition
Click to expand...
Click to collapse
The most important is that previous update you use was emmc
ok, so I can use your build?
if yes please explain one more time the steps, thanks.
also is it possible to use clockworkmod? or how can i make a backup of the rom that I am using
Hello All!
I build this rom from Cyanogen source +
1. kernel from Pershoot(MegaMonstr
2. MDM modems patch (my malata wifi version + F3607GW module with GPS)
3. Camera patch for Skype form toshiba ac100
4. /dev/hands
There are additional wishes?
Sorry for my english
@whyberg -does gsm work?
cociuba said:
@whyberg -does gsm work?
Click to expand...
Click to collapse
voice? i don't know, F3607gw can't support voice calls
gprs/edge/umts data worked well
whyberg said:
Hello All!
I build this rom from Cyanogen source +
1. kernel from Pershoot(MegaMonstr
2. MDM modems patch (my malata wifi version + F3607GW module with GPS)
3. Camera patch for Skype form toshiba ac100
4. /dev/hands
There are additional wishes?
Sorry for my english
Click to expand...
Click to collapse
thanks for all
great job
the post belong to you from now
it would greatfull if post your libcamera .so for working skype
thanks we wait for this long time
i hope for the next...
I will soon test your rom, but I would like to know if something goes wrong can I revert to the stock rom, and how?
thanks for your work.
ps: is it possible to install the rom from a linux machine (ubuntu)?
geowolf1000 said:
thanks for all
great job
the post belong to you from now
it would greatfull if post your libcamera .so for working skype
thanks we wait for this long time
i hope for the next...
Click to expand...
Click to collapse
View attachment libcamera.so.zip
Installetion via ADB
1. unzip libcamera.so.zip
2. adb remount
3. adb push libcamera.so /system/lib/libcamera.so
Via recovery(View attachment libcamera.so-update.zip)
Skype from market last version worked!!!
Gtalk video not! but in`s not a camera problem...
cociuba said:
I will soon test your rom, but I would like to know if something goes wrong can I revert to the stock rom, and how?
thanks for your work.
ps: is it possible to install the rom from a linux machine (ubuntu)?
Click to expand...
Click to collapse
Download stock rom from hardware developer website and reinstall it
What device you have?
My working computer under debian
There is a bug with the latest android N, only the little cores seems to work. You can check it with cpu-z and a stress test.
Also, more info here: https://code.google.com/p/android/i...porter Opened&groupby=&sort=-opened&id=206819
Do you think this will be a quick patch or stay like it until the next developer preview?
It's stil a beta, maybe there will be a patch or in the next preview...the performance overall isnt that affected. You can also change the kernel .
Enrolled in beta last night did OTA to N will check cpu z see if same battery life still sucks 6am - 1:30pm and 17% left ?
Sent from my Nexus 5X using Tapatalk
i don't have this bug i don't know why
i ceched it with elemental x app
I don't have this issue either. All six cores running properly.
took the OTA from DP2 to DP3 and can confirm its happening to me too. i'll try installing the system image and see if that fixes it.
I'm not sure this is a problem with N but rather a problem with the apps you're using to measure the CPU cores themselves.
There's a command: adb shell cat /proc/stat
Type that in terminal with your phone connected and check it out
Now i'm no wiz at android or anything, but the columns it gives back are readings of how long the cpu cores have spent in certain states.
The meanings of the columns are as follows, from left to right:
user: normal processes executing in user mode
nice: niced processes executing in user mode
system: processes executing in kernel mode
idle: twiddling thumbs
iowait: waiting for I/O to complete
irq: servicing interrupts
softirq: servicing softirqs
Tayos-Mac-Pro:~ TayoOnabule$ adb shell cat /proc/stat
cpu 29779 16626 40322 263858 3638 5754 3666 0 0 0
cpu0 11365 9362 17248 101562 2611 2185 1182 0 0 0
cpu1 6731 3452 9271 30395 319 846 700 0 0 0
cpu2 6258 2891 7887 31142 243 708 572 0 0 0
cpu3 1245 391 3335 33573 216 458 469 0 0 0
cpu4 2344 377 1433 33444 130 1422 299 0 0 0
cpu5 1834 150 1146 33740 116 133 440 0 0 0
intr 2777034 0 3 0 3 0 0 5 0 0 0 0 0 0 0 0 0 0 0 0 0 618895 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 96044 0 0 0 0 0 0 0 343 0 0 136 0 0 0 0 0 2236 2 5 0 0 0 0 0 12538 0 0 0 0 0 0 0 0 0 0 274 0 0 0 0 2 416 2 0 2 0 0 0 4 4 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 22521 0 0 0 0 0 0 0 0 0 0 0 0 26715 0 0 0 112 12660 0 346 0 25 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 381885 0 0 0 0 0 0 0 1413 0 0 0 0 0 0 1011 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 12595 0 6 0 0 0 0 20317 7011 0 0 0 121135 0 0 1141 0 0 0 0 0 0 0 0 1 0 0 14757 619 0 0 0 0 0 548 0 1839 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 6983 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 9189 0 0 0 0 52677 0 0 0 0 0 0 288 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 529 26 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 8 0 0 0 0 0 0 0 0 94 0 0 0 0 0 0 0 0 3 0 0 0 0 0 0 3 0 0 0 0 0 0 0 0 0 21 0 0 0 0 0 0 0 0 0 0 0 303 0 0 0 0 292 0 2147 3 66 509 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 341 3643 0 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 131 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 161 0 0 0 0 0 0 0
ctxt 5896731
btime 1463686046
processes 11422
procs_running 1
procs_blocked 0
softirq 1957987 1198 375954 3331 23764 1198 1198 288344 370196 1092 891712
Tayos-Mac-Pro:~ TayoOnabule$
Click to expand...
Click to collapse
Edit: I also can't see the big cores working in CPU-Z, but doing this command it is obvious that they are actually working... apart from anything else N is so buttery smooth they must be working
/proc/stat actually shows that the 2 big cores are working. Cpu-z or cpu-x seem slow (or even fail) to update core speed. Try same with Antutu's cpu info (Info > cpu info > more) or tinycore (cpu profil, system info) and run a cpu heavy task that doesn't get low priority or stops when in background. Both should show actual values while on cpu-z/-x the big cores are still marked sleeping/stopped.
Are you sure this isn't thermal throttling? After the image first installed the cores temp was too high so it throttled the large cores off... once temps stabilized the big cores came back online. I think this is just a CPUZ bug to be honest.
It's just CPU-Z.
You can't expect every application to function properly on developer previews.
What's best way to return to M flash factory image suppose will loose everything? as I did OTA update from M to N and didn't loose anything
Sent from my Nexus 5X using Tapatalk
DoobyDroid said:
What's best way to return to M flash factory image suppose will loose everything? as I did OTA update from M to N and didn't loose anything
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I can answer that one! just go back to the enrol page and click unroll device from beta your phone will receive a ota for latest build , unfortunately its a wipe so back up important tack first.........
Yeah my Android N is rooted i use kernel auditor with the stock supersu kernel and it shows cores working.
very low score in geekbench 3/antutu on n preview 3
the cores are definitely offline
meisking1 said:
very low score in geekbench 3/antutu on n preview 3
the cores are definitely offline
Click to expand...
Click to collapse
Nope they are not, CPUZ is just having hard time detecting the cores on N.
Those two benchmark tools are notoriously worthless and doesn't maximize all the cores of multi-core SoC.
Antutu used to be good until they changed the scoring system and gave favor to crippled phones like iCrap and some android with low resolution and fast graphics processor.
Geekbench only uses Core 1 at 100% and 2 a little bit lower and the rest are like 10-25% load.
{
"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"
}
Consider S820 vs A9
They are both head to head in single core IPC and yet the A9 manages to score 4.5K on multicore result while S820 only about 5.3K.
Joms_US said:
Nope they are not, CPUZ is just having hard time detecting the cores on N.
Those two benchmark tools are notoriously worthless and doesn't maximize all the cores of multi-core SoC.
Antutu used to be good until they changed the scoring system and gave favor to crippled phones like iCrap and some android with low resolution and fast graphics processor.
Geekbench only uses Core 1 at 100% and 2 a little bit lower and the rest are like 10-25% load.
Consider S820 vs A9
They are both head to head in single core IPC and yet the A9 manages to score 4.5K on multicore result while S820 only about 5.3K.
Click to expand...
Click to collapse
So is there any app that can detect if the cores are running?
playing asphalt 8 and its lagger than in mm
i am curious if the cores are really running
meisking1 said:
So is there any app that can detect if the cores are running?
playing asphalt 8 and its lagger than in mm
i am curious if the cores are really running
Click to expand...
Click to collapse
CPU stats does for me.
On stock system thermal throttling kicks in early and big cores are meant as short time boosts not permanent speed up. So you'll see relatively little use anyway
The animations of Android N in slowmotion
http://www.bitfeed.co/page/the-animations-of-android-n-in-slowmotion-video