195 replies to this topic

[ipaq3870]

louis xv, on 17 May 2012 - 01:10 AM, said:

okay, i'm waiting

See post above.

louis xv, on 17 May 2012 - 01:25 AM, said:

ipaq, could you provide just one more falvour (666 CPU /166 AHB /24bpp /128 RAM)
to avoid white squares and still have zram benefits ???

I do have a +13MB version that has the same amount of video memory as the original kernel that I guess would eliminate white squares - at least to the same level as the original kernel did. Do you want to try that first?

nikkotsoi, on 17 May 2012 - 01:13 PM, said:

hello,, i don't know if i did it wrong
can't see anything about "wifi"?
dmesg.txt

I can't see any libertas (the wifi driver name) your log. Instead I see something more alarming here:

[28390.703787](   com.whatsapp) EXT4-fs error (device mmcblk0p2): ext4_get_branch: invalid block reference 3795845132 in inode #415661
[28390.878472](   com.whatsapp) EXT4-fs error (device mmcblk0p2): file system corruption: inode #415661 logical block 524 mapped to 3795845132 (size 1)
[28390.910728](   com.whatsapp) EXT4-fs error (device mmcblk0p2): file system corruption: inode #415661 logical block 524 mapped to 3795845132 (size 1)
[28390.922473](   com.whatsapp) EXT4-fs error (device mmcblk0p2): file system corruption: inode #415661 logical block 525 mapped to 3851423744 (size 1)
[28390.935441](   com.whatsapp) EXT4-fs error (device mmcblk0p2): file system corruption: inode #415661 logical block 526 mapped to 3785420801 (size 1)
[28390.981375](   com.whatsapp) EXT4-fs error (device mmcblk0p2): file system corruption: inode #415661 logical block 527 mapped to 3810586624 (size 1)
[28391.000854](   com.whatsapp) attempt to access beyond end of device
[28391.001696](   com.whatsapp) mmcblk0p2: rw=0, want=7591690266, limit=2000351
[28391.009411](   com.whatsapp) Buffer I/O error on device mmcblk0p2, logical block 3795845132
--- rest snipped ---

Is mmcblk0p2 your root partition? If so, it may have corrupted the module file itself, in this case, libertasspi.ko. Filesystem corruption can't be anything good in any case. I'd suggest you evacuating your data immediately, and re-format the partition.

If you don't care about the data, you can verify driver loading by manually running:

insmod /modules/libertasspi.ko
lsmod

You can see a list of modules loaded, and you can do a dmesg again, and it will show up some messages regardless of whether it's successful or not.

Edited by ipaq3870, 17 May 2012 - 04:41 PM.

[ErcanPolat]

Hello ipaq.

After boot i write lsmod in terminal. It lists si4709_driver, s3c_camera, multipdp, dpram, vibrator. After insmod /modules/libertasspi.ko, I could see libertas. But wifi has still error. here is dmesg messages about libertas

[ 290.178729]( insmod) libertas_spi: Libertas SPI driver
[ 290.953246]( insmod) Sanya: Power On wlan
[ 290.954072]( insmod) libertas_spi spi1.0: firmware: requesting libertas/gspi8686_hlp.bin
[ 290.973311]( init) init: waitpid returned pid 2516, status = 00000000
[ 290.975312]( init) init: untracked pid 2516 exited
[ 291.369672]( insmod) libertas_spi spi1.0: firmware: requesting libertas/gspi8686.bin
[ 291.379245]( init) init: waitpid returned pid 2520, status = 00000000
[ 291.381199]( init) init: untracked pid 2520 exited
[ 291.885627]( insmod) libertas: 00:21:19:b2:38:b6, fw 9.70.10p0, cap 0x00000303
[ 291.893734]( insmod) txpower:18 min:4 max:20
[ 291.902770]( insmod) libertas: wlan0: Marvell WLAN 802.11 adapter

Edited by ErcanPolat, 17 May 2012 - 07:04 PM.

[ipaq3870]

ErcanPolat, on 17 May 2012 - 07:03 PM, said:

After boot i write lsmod in terminal. It lists si4709_driver, s3c_camera, multipdp, dpram, vibrator. After insmod /modules/libertasspi.ko, I could see libertas. But wifi has still error. here is dmesg messages about libertas

I suspect you are facing a different problem. The above manual procedure is used to verify if the kernel module is loaded properly after seeing the "Failed to load Wi-Fi driver" message in logcat, and no libertas message in dmesg.

Anyway, your dmesg looks reasonable, and you should do a logcat to see what exactly went wrong. You can also try if the following quick fix works:

Do a rmmod libertasspi in terminal (or simply reboot), and issue the following commands in terminal.

mv /data/misc/wifi/bcm_supp.conf /data/misc/wifi/bcm_supp.conf.bak
chmod g+w /data/misc/wifi/

Activate wifi again. If still error, you'll really have to dig up some logcat.

[jingang]

could   you explain zram？do it with terminal？？

[rom_omnia2]

jingang, on 18 May 2012 - 05:23 AM, said:

could   you explain zram？do it with terminal？？

I've copied the script on the first page and named it zr.sh, then put it where SDcard is mounted. So, with terminal:

su   (log in as root)
chmod 777 /sdcard/zr.sh   (make it executable)
sh /sdcard/zr.sh   (run the script)

Then terminal will show some errors but just type free on terminal and see if swap line isn't showing just zeros, if don't, then is working.

[jingang]

rom_omnia2, on 18 May 2012 - 07:02 PM, said:

I've copied the script on the first page and named it zr.sh, then put it where SDcard is mounted. So, with terminal:

su   (log in as root)
chmod 777 /sdcard/zr.sh   (make it executable)
sh /sdcard/zr.sh   (run the script)

Then terminal will show some errors but just type free on terminal and see if swap line isn't showing just zeros, if don't, then is working.

thanks it seems good

[jingang]

with 160m zimage，when opening pictures there are white and black lines all the time，it also happens with other apps？why？any solutions？

[louis xv]

jingang, on 19 May 2012 - 09:37 AM, said:

with 160m zimage，when opening pictures there are white and black lines all the time，it also happens with other apps？why？any solutions？

you need to raise the minimum cpu freq to 166 MHz , use "setcpu" it worked for me

[jingang]

you mean the problem is caused by low cpu？i will try，thanks

[ipaq3870]

jingang, on 20 May 2012 - 03:56 AM, said:

you mean the problem is caused by low cpu？i will try，thanks

It's kinda a combination of low cpu freq, low AHB bus freq, and choice of bpp. You see, our screens have a resolution of 800x480, a refresh rate of 60Hz, and with 24bpp+8bit alpha channel, you'll need at least 23+MHz of cpu/bus cycle to move the video data around. Normally the AHB bus runs @133MHz, but when the cpu is driven down to only 66MHz, the bus can only run @66Hz and such limited bandwidth is further shared among other sub-systems such as memory controller, etc. That's why when the cpu runs low in freq, you'll see screen flickering.

I actually have a fix in my local repo that alleviate this problem by tweaking the QoS register of the bus. It should eliminate the flickering for an overclock AHB @166MHz even when the cpu is running @83.25Mhz. Still it wouldn't solve the problem on a non-OC version (I didn't produce that build anyway.) Will release it together with more goodies after some testing.

[nikkotsoi]

s***
i got all my sms lost suddenly!!
i heard the vibrating sound of receiving sms just before i went bathing
after i finished bathing
all sms are goneee!!! No way to recover ?
by the way i will run the terminal again to check with modules are loading,, quite busy this week

[ipaq3870]

nikkotsoi, on 20 May 2012 - 02:52 PM, said:

i got all my sms lost suddenly!!

Hmm... you have filesystem corruption..... so funny things can happen as a result of data loss and files get trashed. If you have a linux or linux vm around, you can try to manually do a fsck after you reboot it back to WinMo. Believe if you ignore this problem - more strange things will happen until the fs is so corrupted that your phone will no longer boots to your home screen. Yes, it happened to me few months ago. It turned out to be my linux box automounted the same mounted root partition on phone when it's connected via USB, and thus creating a mess with the fs. Then I immediately turned off automount on my desktop, and turn on exporting lun0 on phone by commenting out the following line in init.rc:

#write /sys/devices/platform/s3c6410-usbgadget/gadget/lun0/file /dev/block/mmcblk0

[nikkotsoi]

ipaq3870, on 20 May 2012 - 03:57 PM, said:

Hmm... you have filesystem corruption..... so funny things can happen as a result of data loss and files get trashed. If you have a linux or linux vm around, you can try to manually do a fsck after you reboot it back to WinMo. Believe if you ignore this problem - more strange things will happen until the fs is so corrupted that your phone will no longer boots to your home screen. Yes, it happened to me few months ago. It turned out to be my linux box automounted the same mounted root partition on phone when it's connected via USB, and thus creating a mess with the fs. Then I immediately turned off automount on my desktop, and turn on exporting lun0 on phone by commenting out the following line in init.rc:

#write /sys/devices/platform/s3c6410-usbgadget/gadget/lun0/file /dev/block/mmcblk0

ohthx
so i should do a chkdsk to fix the error
and run your line to prevent the same error occurs again ?

[ipaq3870]

nikkotsoi, on 20 May 2012 - 04:52 PM, said:

so i should do a chkdsk to fix the error
and run your line to prevent the same error occurs again ?

chkdsk is for FAT filesystem, and is of no use to Linux's ext4 partitions, which needs a command called fsck. Do you have a Linux box or virtual machine around? It would be much easier to fix things in a Linux box...

[ipaq3870]

3.0 Vanilla build (superseded)

CPU: 800Mhz / AHB: 133Mhz / 141MB free memory / 16bpp display
Build No: a3b8d7f-865

Note: always watch first post for latest builds in case this build has been superseded.

Attached Files

•  3.0-a3b8d7f-865-800mhz-133mhz-141mb-16bpp.part1.rar   1.91MB   75 downloads
•  3.0-a3b8d7f-865-800mhz-133mhz-141mb-16bpp.part2.rar   863.32K   66 downloads

Edited by ipaq3870, 28 May 2012 - 02:01 PM.

[ipaq3870]

3.0 AHB Overclocked & CPU Underclocked & 24bpp Framebuffer (superseded)

CPU: 667Mhz / AHB: 166Mhz / 141MB free memory / 24bpp display
Build No: a3b8d7f-866

Note: always watch first post for latest builds in case this build has been superseded.

Attached Files

•  3.0-a3b8d7f-866-667mhz-166mhz-141mb-24bpp.part1.rar   1.91MB   23 downloads
•  3.0-a3b8d7f-866-667mhz-166mhz-141mb-24bpp.part2.rar   863.63K   31 downloads

Edited by ipaq3870, 28 May 2012 - 02:01 PM.

[ipaq3870]

3.0 Even more memory (superseded)

CPU: 667Mhz / AHB: 166Mhz / 160MB free memory / 24bpp display
Build No: a3b8d7f-867

Note: always watch first post for latest builds in case this build has been superseded.

Attached Files

•  3.0-a3b8d7f-867-667mhz-166mhz-160mb-24bpp.part1.rar   1.91MB   66 downloads
•  3.0-a3b8d7f-867-667mhz-166mhz-160mb-24bpp.part2.rar   863.66K   63 downloads

Edited by ipaq3870, 28 May 2012 - 02:01 PM.

[nikkotsoi]

ipaq3870, on 21 May 2012 - 12:59 AM, said:

chkdsk is for FAT filesystem, and is of no use to Linux's ext4 partitions, which needs a command called fsck. Do you have a Linux box or virtual machine around? It would be much easier to fix things in a Linux box...

i have ubuntu only

[synescu]

ipaq3870, on 21 May 2012 - 02:16 PM, said:

3.0 Vanilla build
CPU: 800Mhz / AHB: 133Mhz / 141MB free memory / 16bpp display
Build No: a3b8d7f-865

Note: always watch first post for latest builds in case this build has been superseded.

Hi I tried version above but it seems to be the same story with wifi error.otherwise everything seems ok even faster I think it's just my impression good job I hope to not lose your enthusiasm. It seems that you have left only one on here with real knowledge that can continue devs work and give one more chance to our phones

Edited by synescu, 21 May 2012 - 05:44 PM.

[Pathwalker]

hi i was searching on google and i've found that jetdroid gingerbread (for samsung jet s800x) is working fine on our phones but it needs to be developed for i8000 users, could anyone give it a try??