yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] Starfox:
SYSTEM_LAST_KMSG@1313576908380:

[12842.996429] kernel BUG at drivers/char/tty_ldisc.c:199!

SYSTEM_LAST_KMSG@1313593086380

Normal shutdown

SYSTEM_LAST_KMSG@1313594073900

Kernel: Linux version 2.6.27.46-fox-01346-g8704c33 (starfox@ubuntu) (gcc version 4.4.5 (Ubuntu/Linaro 4.4.5-15ubuntu1) ) #2 PREEMPT Tue Aug 16 21:42:55 EDT 2011

[ 580.337097] SMD: ch 7 CLOSED -> CLOSING

[ 580.337249] SMD: ch 7 CLOSING -> OPENING

[ 580.337341] SMD: ch 7 OPENING -> OPENED

[ 580.338287] kernel BUG at arch/arm/mach-msm/smd.c:317!

[ 580.338348] Unable to handle kernel NULL pointer dereference at virtual address 00000000

SYSTEM_LAST_KMSG@1313598721380

Kernel: Linux version 2.6.27.46-fox-01346-g8704c33 (starfox@ubuntu) (gcc version 4.4.5 (Ubuntu/Linaro 4.4.5-15ubuntu1) ) #2 PREEMPT Tue Aug 16 21:42:55 EDT 2011

[ 291.394348] wake lock wlan_rx_wake, expired

[ 292.398101] suspend: enter suspend(2011-08-17 15:26:46.190000000 UTC)

[ 292.398132] PM: Syncing filesystems ...

Was this a SoD? Did you plug something in at that time?

SYSTEM_LAST_KMSG@1313608306340

This is a garbled. I notice you are OC'ing. Please try to reproduce it without the OC.

-- Starfox
[Touch Pro2, Tilt 2 Android Development] Tippfehler:
I think, I had plugged in the USB (PC).
[Touch Pro2, Tilt 2 Android Development] Tippfehler:
Reboot without OC:
[Touch Pro2, Tilt 2 Android Development] detule:
I am no expert, but I would be surprised if you don't get reboots with the kernel from the autobuild.

This seems to be a manifestation of a bug that may have to do with certain smd changes that were enacted back in June (and recently revised.) It seems to happen with the channel closes/opens, and I am not sure why but you seem to experience smd_close/open frequently (low service coverage? data intensive operations?)

I am just mouthing off here, but at least I am fairly certain your reboots don't have anything to do with the LED changes.
[Touch Pro2, Tilt 2 Android Development] mweirauch:
Wasn't there some mentioning in the changelogs that instant cable plug notification was re-established? Or at least mucking with the pending wake ints register? Dunno if Starfox re-enabled the interrupt service routine again in proc_comm_wince.c. That ISR caused a lot of SODs on .27. Fortunately this runs fine on .35 :P
[Touch Pro2, Tilt 2 Android Development] domoarigato:
been running the 8/15 version of this kernel... all i can say is, aside from not being able to run any wifi tether apps, this is the best kernel ive used. the battery life is amazing... i used to carry 2-3 batteries with me to last a day but with this kernel, i can make it through a full day without changing my phone usage patterns.

one small quirk... my phone is automatically setting itself back for 4 hours. it never did this until i restarted the phone one day. is there any way i can fix this without doing a fresh install?

i have 2 questions

1. if i want to use the updated kernel 8/16, do i just straight up replace it in the npkboot folder or is there some changes i have to make to other files?

2. is there any way to get wifi tether to work?

thanks again for this awesome kernel!
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
1. You only replace the kernel per Incremental Updates just as you would replace any other kernel... no clue what you mean by the npkboot folder.

2. Wifi tethering works great on FRX07. I use the built-in wifi tethering and it's fine.
[Touch Pro2, Tilt 2 Android Development] mgross029:
arrrghhh,

He is referring to a Neopeek boot folder, just like the andboot folder...

Also, on the 8/16 Test Kernel I notice the wifi wouldn't enable on that kernel. I would get an error on wifi when attempted. That was the only thing I think was not working on that kernel though... I ran it for two days and it was great...

Just moved over to StarFox's Vanilla kernel to test that out for him... So far so good... And wifi enables on that kernel...
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I know what it is, what I didn't get is what it has to do with this kernel. My point was replace this kernel just like you would any other.
[Touch Pro2, Tilt 2 Android Development] domoarigato:
sorry i guess i should have been a little more clear...

i am running this with NEOfroyo v0.1, and i cant get wifi tether to work :(

thanks for the halp guys
[Touch Pro2, Tilt 2 Android Development] muziling:
About 2011/8/19 7:10, when I enable data connection, phone auto reboot.

seems there is one method called RMNET ,which can instead of pppd
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Does it work on NeoFroYo on autobuild kernels?

Not sure that configurations like yours can be supported on these testing kernels. At least I don't really want to support many configurations, and somehow I doubt Starfox wants to either.

I do know that it works fine on FRX07 on my RHOD400 with this kernel.

Most native Android devices use RMNET (at least from HTC) but we cannot use it. we have to use PPP....
[Touch Pro2, Tilt 2 Android Development] muziling:
http://xdaforums.com/showpost.php?p=8029932&postcount=7

OOPS, so this is why sometimes, i enable data connection, screen freeze...
[Touch Pro2, Tilt 2 Android Development] Daved+:
With the new lights.msm7k.so lib, my phone reboots itself when it's supposed to notify me of something.

:(
[Touch Pro2, Tilt 2 Android Development] detule:
Can't help you unless you post logs.

Did the previous iteration of the kernel work for you? (One without the mounted library, and with only solid green/amber notification) If you haven't tried it yet, I would rollback to that kernel and see if you experience similar behavior - this will help us narrow down the problem.

You can get dmesg following the instructions a page or two back.

A logcat would also be nice. To do this, set up a running logcat in a terminal

# logcat -v time > /sdcard/log.txt

Then send yourself a text message causing the phone to reboot.

Please post both the logcat (from /sdcard/log.txt) and the dmesg.
[Touch Pro2, Tilt 2 Android Development] mgross029:
WIFI / WIFI Tether does work on the 8/16 kernel

Just wanted to provide an update on the 8/16 kernel... I had to inadvertantly delete my data.ext4 file and recreate... After doing so I am now able to get wifi up and running on this kernel...
[Touch Pro2, Tilt 2 Android Development] großa:
I've done almost everything (test kernel, ext4, memory management, etc) but I'm still not sure, if it is enough to install the patch for compcache and enable it in the froyo.user.conf or if there's something else to do (adb push)?

Is it better to enable swapfile?
[Touch Pro2, Tilt 2 Android Development] Starfox:
This is what I have in my froyo.user.conf. Yours will be a bit different.

mknod /dev/block/loop9 b 7 9

mknod /dev/ramzswap0 b 253 0

losetup /dev/block/loop9 /sdcard/swapfile

insmod /lib/modules/xvmalloc.ko

insmod /lib/modules/ramzswap.ko backing_swap=/dev/block/loop9

swapon /dev/ramzswap0

I've disabled support in froyo.user.conf for the built-in one because there's a few bugs in it. Mainly, it sets up ramzswap0 as block major 254, when it should be 253. I also use a "backing swap" which is a mkswap'ed 32M file on /sdcard/swapfile, which must then be loop-mounted because ramzswap only allows block device as backing swap. If you don't have one you can take stuff about /dev/block/loop9 out.

-- Starfox
[Touch Pro2, Tilt 2 Android Development] Starfox:
The only thing I fixed, only in the -test kernel (which isn't what he was running when he SoD'ed) was the bug (which I was told was a bug by 2 ppl) overwriting msm_proc_comm_wince_pending_ints in msm_proc_comm_wince_exit_sleep(). I changed it to:

msm_proc_comm_wince_pending_ints &= ~DEX_INT_VBUS;

-- Starfox
[Touch Pro2, Tilt 2 Android Development] Starfox:
Upstream updated to build 1348, which includes the official liblights. Not sure if any of the commands in froyo.user.conf has changed. Will update my froyo.user.conf page once that's done.

-- Starfox
[Touch Pro2, Tilt 2 Android Development] fortunz:
Late to the party, but I finally got around to checking out the blinking notifications and they seem to work charmingly.
[Touch Pro2, Tilt 2 Android Development] großa:
I made a swapfile, mkswaped it and added the commands in the froyo user conf. Deleted the old compcache and swap conf lines.

Working fine so far. Is there a way to verify that compcache is working now?

EDIT:

System feels smoother now. So I suppose comcache is working. Testing it since 2 days.

Did somebody notice the strange behavior from the display brightness slider?

Also the display is very bright at startup, but after the first sleep, the display will definetly never be so bright again.
[Touch Pro2, Tilt 2 Android Development] mgross029:
Radio Loss?

Since I've put the 1348 Test kernel on I've had problems with my radio dropping out and an attempt to switch to airplane mode just leaves my phone hanging... The last time even a full reboot would not correct the issue, so what I did was go into WM enable the radio, updated Quick GPS just to send some data, disabled the radio and then rebooted, booted into Android and so far all seems fine. I just found it quite weird that it was happening... I'm pulling a logcat and dmesg. I will post them up shortly... Plus I wasn't sure if anyone else has seen this problem...

Also, during this time my APN settings were gone and I could not add or save anything to the APN... Just thought I should mention that too...

Rhod500

FRX07 w/1348 Fox Test Kernel

8/16 Rootfs

Edit: Attached logs...
[Touch Pro2, Tilt 2 Android Development] mgross029:
lcd.density=240

I was parsing through my dmesg file and saw this error.

Unknown boot option `lcd.density=240': ignoring

After doing some searching I found a thread over at PPCGreeks for the Blackstone which used lcd_res instead of lcd.density... After adjusting the item on my set cmdline in startup.txt to lcd_res=240 I now notice a little more real estate on my display... I actually get an additional icon on my launcher at the bottom of the screen and the text on my display is a little different now.

I have posted some screen shots to show the difference.

Also, not sure if it's the placebo effect or not but I seem to get better response out to the touch screen.
[Touch Pro2, Tilt 2 Android Development] großa:
O

Good find!! Higher resolution :) I like it!

Found this entry in the build.prop:

# density in DPI of the LCD of this board. This is used to scale the UI

# appropriately. If this property is not defined, the default value is 160 dpi.

ro.sf.lcd_density = 210

So I guess that lcd_res=240 overwrites ro.sf.lcd_density=210. Hmm I'm trying it -> No it doesn't :)
[Touch Pro2, Tilt 2 Android Development] teemo:
Perfect. That fixed the position of workspace icons and hopefully widget sizes of Zeam. Thanks a lot :)
[Touch Pro2, Tilt 2 Android Development] ACoolGuy:
GREAT FIND! I dont see any more speed and im sure that due to the increased resolution that its SLIGHTLY slower, if at all, but it does look alot better! Thanks for the tip.
[Touch Pro2, Tilt 2 Android Development] Starfox:
No, you're now running at 210dpi mode, which is why you have more icons. By default, without lcd.density, XDAndroid defaults to 210. The only reason why you see that message is because the kernel probably tries to parse anything with a ., and it cannot find a handler. /init is the file that does the actual parsing.

I actually prefer 210 for my device, so I don't have lcd.density on my startup.

-- Starfox
[Touch Pro2, Tilt 2 Android Development] vinceweis:
Wow, Starfox, you just keep coming up with more and more clues and hints to optimize this build. Thanks and please keep active in the thread.

I am running the ext4 file system, along with the speed tweaks in the other thread and I have never seen such stability and speed out of XDAndroid.

I thank all the devs for the hard work and you for bringing it to the TP2 earlier than waiting for the official builds. Are there other tricks up your sleeve?
[Touch Pro2, Tilt 2 Android Development] mgross029:
I stand corrected... Thanks for pointing that out StarFox... I took the lcd_res statement out of my startup and I do get the same resolution if it were in place.

I've had the lcd.density statement in there since it was suggested a while back in other FROYO versions. Looks like the kernel has been developed well enough to no longer need it...
[Touch Pro2, Tilt 2 Android Development] helicopter88:
It's not kernel related,it's rootfs related,so probably in the past it was kernel related,now init reads it..
[Touch Pro2, Tilt 2 Android Development] teemo:
...and how does this DPI translate to my display ?

The display is 2" high, giving me 420 dots. So one pixel=0.525 dots ...?
[Touch Pro2, Tilt 2 Android Development] Starfox:
This is basic algebra+geometry. Rhodium has a 3.6" display.

sqrt(800^2+480^2)/3.6=~259dpi

800/259=3.0", btw.

Android uses dpi to determine which resources to display. If you have an identical size display, but say one at 800x480 and another at 480x320, if you use a icon that is 64 pixel high to display, the screen with the lower display is going to take up a larger portion of screen estate to show that icon. That's why lcd.density is supposed to be based on screen resolution (640x480=210dpi, 800x480=240dpi) than "actual" display size.

-- Starfox
[Touch Pro2, Tilt 2 Android Development] großa:
Did you try to adjust the backlight, after deleting lcd.density=240?

It's just on or off :) Bright or dark :)

Hmm nevermind. After a reboot it's working fine.

Sent from my TP2.
[Touch Pro2, Tilt 2 Android Development] jamtoday:
thanks

i found , some program can't use recording voice . :confused:
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Can you tell us more, like say which program you're talking about? I'm assuming it worked before on autobuild kernels?!!?

What build are you running?

Have you taken any logs?
[Touch Pro2, Tilt 2 Android Development] jamtoday:
(1) i used (8/20) Kernel for RHOD , FRX07 , rootfs is 20110816

(2) Apps: "Talking Tom" , and http://weixin.qq.com .

Note: i use a earphone with microphone , the program run ok .

sorry i don't know how to get Logs .

:)

my stratup.txt code :

set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set initrd_offset 0x00a00000
set cmdline "lcd.density=240 acpuclock.oc_freq_khz=710400 acpuclock.force_turbo=2 msmsdcc_fmax=48000000 msmvkeyb_toggle=off force_cdma=0 pm.sleep_mode=1 physkeyboard=rhod100_uk"
boot
[Touch Pro2, Tilt 2 Android Development] muziling:
system auto reboot this morning
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
Easiest way to get logs... use get logs ;). IIRC it's included in the FRX07 build in the android apps folder, and if not or you want instructions, here's the link

http://xdaforums.com/showthread.php?t=1123129
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Talking Tom doesn't work on our port. Lots of people complain about this app not working, so I'd say it doesn't work. I don't really care for the app myself, so I'm not going to spend the time to figure out 'why' it doesn't work. Some things are worth my time even if I don't use it often (MMS for example) but apps like this... I don't think are worth my time.

If you do figure out how to get it working, more power to you. I suggested to someone else that they do the call voicemail before booting trick, to see if it's an audio routing issue. No guarantees that will resolve it, but it might help... Never know.

What I mean by call voicemail before booting trick is you call some number - say voicemail so the call stays up - and boot HaRET while that call stays up. The call will end during the boot process. It might help.

I have no clue what that other app is, but there's a lot of symbols so I'm guessing it's not for me :p.
[Touch Pro2, Tilt 2 Android Development] domoarigato:
what is the best version of android to run this with?

Ive been using NEOfroyo v.1 and I've been getting amazing battery life with this kernel. I used to have to carry 2-3 batteries with me to last me through the day, but with this kernel I can easily last a full day without having to charge or switch batteries. My usage patterns have not changed at all. :D

also, are there any plans on bringing this kernel out of the testing phase?
[Touch Pro2, Tilt 2 Android Development] detule:
Hey, if you are still suffering from these SMD induced kernel panics, I may have a patched kernel for you to test. Shoot me a message either here, or on #xdandroid.
[Touch Pro2, Tilt 2 Android Development] Dinky:
Darn... I've been on this kernel for three days. With the BT routing work-around and new RIL, I thought this kernel is stable enough for my daily use. But it rebooted itself this morning, then got a SOD two hours later... :-(
[Touch Pro2, Tilt 2 Android Development] anish88:
how do i clear the old modules that were installed on to the system?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Searched this thread for "modules":

http://xdaforums.com/showpost.php?p=16616048&postcount=70
[Touch Pro2, Tilt 2 Android Development] anish88:
thanks bro
[Touch Pro2, Tilt 2 Android Development] schlei:
Any news on a new Kernel with rhod100 camera fix inside ?

It works perfect on my rhod100_de my wife is using it now 2days.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
This is a test kernel thread, has nothing to do with the main kernels...

Until the guy who actually fixed the issue submits a patch, nothing will happen. Autobuild or otherwise, no kernel will get the fix without his patches getting submitted...
[Touch Pro2, Tilt 2 Android Development] [ACL]:
do you know if there was a test kernel released to make sure no other devices are broken? This was jb's concern and why this patch prob wont get commited. Even my prox patch is pending testing on gsm or until someone sends me that damn dll, so its just the way it is. :eek:
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Yes, see here:

http://xdaforums.com/showpost.php?p=17612078&postcount=1052

It didn't break my phone, but JB responded to his patch with some suggestions. AFAIK JB and brinka123 are sorting out the patch, and hopefully will commit soon...

I think RHOD-only users have tested tho. Probably should try to get some other devices to test to ensure it won't break them as well.
[Touch Pro2, Tilt 2 Android Development] [ACL]:
I have faith in you bro.. If emwe is busy so i can commit this as soon as testing is done. Just let me know.. if nothing is broken :-)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
hah, someone does at least :p.

But I digress - JB will hopefully submit an updated patch. That initial one isn't as clean as JB would like it, and he's the man when it comes to the cam code.
[Touch Pro2, Tilt 2 Android Development] großa:
Deleted...
[Touch Pro2, Tilt 2 Android Development] großa:
Starfox where are you? We need a new test-turbo-kernel ;) :)
[Touch Pro2, Tilt 2 Android Development] FaluSeyi:
Hi Starfox, is there a layman term for "Open a terminal window" I really don't understand that.

Thanks

Seyii
[Touch Pro2, Tilt 2 Android Development] teemo:
Install Android Terminal Emulator

But somehow I think you are better off with FRX07.1 with improvements from Arrrghhhs Speed thread.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
ConnectBot is one I like :D.
[Hero CDMA Q&A, Help & Troubleshooting] joeyh44:
Sorry, for posting here but i cant post in the developement section. Was running wildheroc some a few days, and suddenly i would loose all data connection. Ciould still use phone and text pust not data. Im on alltel if that helps anyone, just wondering if there is a fix.
[Hero CDMA Q&A, Help & Troubleshooting] Drunkpilot:
When is the last time that you updated your PRL? You might want to nandroid and go back to a Sense Rom and update the PRL, PRI and then restore your nandroid of WildHeroc.

There is a thread about PRL's as well in the Heroc section too.
[Hero CDMA Q&A, Help & Troubleshooting] Kumetto:
Drunkp-you beat me to it just did it for my cousin.

This is Q&A so you better damn well be sorry I mean really "c'mon man" haha

I'd also browse thru the ROM's main thread to see if others encountered that same issue.
[Nexus One Q&A, Help & Troubleshooting] kuljit55:
possible to recalibrate soft keys accuracy?

i ask this because my accuracy is starting to become sloppy eg having to press a cm above the soft key at times.

thanks
[Nexus One Q&A, Help & Troubleshooting] evilkorn:
Nope, just always aim higher than the graphic.
[XPERIA X10 Q&A, Help & Troubleshooting] Tone503773:
Okay I am an HTC user and the rooting process is pretty much the same across all HTC devices. So when my girlfriend wanted to take her phone to tmobile I tried to root it for her, and now I am lost so can someone solve my problem?
[XPERIA X10 Q&A, Help & Troubleshooting] geordie 34:
What firmware you running
[XPERIA X10 Q&A, Help & Troubleshooting] Tone503773:
For ATT it is 2.1-update1
[XPERIA X10 Q&A, Help & Troubleshooting] geordie 34:
To root you need to use flashtool and click on root will install busybox and xrecovery well that how I rooted mine but im sim free in uk
[XPERIA X10 Q&A, Help & Troubleshooting] Tone503773:
Yeah that is what I am trying to do also. My girlfriend is making the move from ATT to tmobile so I need the sim freed.
[XPERIA X10 Q&A, Help & Troubleshooting] geordie 34:
Im afraid cant help with the unlocking you may need to use a website dont do what I seen on another thread on here that was ppl posting there imei numbers for all to see
[XPERIA X10 Q&A, Help & Troubleshooting] oalf170892:
Well I say for sure rooting will not unlock the network on the x10... So as geordie 34 said, you will need to buy an unlocking code to use with T-mobile...

Hope to help.
[XPERIA X10 Q&A, Help & Troubleshooting] Tone503773:
LOL yeah I know better than that.
[XPERIA X10 Q&A, Help & Troubleshooting] silentknight16:
flashing help

I have flashed the latest rom by wb with speedfix v3.0............to flash speedfix v3.1, should i flash the main rom again.........please help
[XPERIA X10 Q&A, Help & Troubleshooting] Tone503773:
Okay, so where can I buy one and do you know how much unlocking codes go for?
[XPERIA X10 Q&A, Help & Troubleshooting] geordie 34:
There is a newer speed fix than that I would flash his latest Rom with speed fix 7
[XPERIA X10 Q&A, Help & Troubleshooting] geordie 34:
Just search on Google unlock codes for xperia x10a it will ask for your imei number think in UK anything between 5 and 20 pounds
[XPERIA X10 Q&A, Help & Troubleshooting] silentknight16:
i dd not see the post of the new speedfix but coming back to my earlier doubt, should i just flash the fix or the whole thing? thanks....
[XPERIA X10 Q&A, Help & Troubleshooting] geordie 34:
I would flash everything at least everything will be upto date
[XPERIA X10 Q&A, Help & Troubleshooting] silentknight16:
could you let me know the link for v7 because the following link shows the last speedfix:

http://xdaforums.com/showpost.php?p=16188210&postcount=950
[XPERIA X10 Q&A, Help & Troubleshooting] geordie 34:
My apologies that is the upto date version for that Rom
[XPERIA X10 Q&A, Help & Troubleshooting] BingoRingo:
You do know that AT&T and T-Mobile do not use the same frequencies right?

On T-Mobile with her AT&T X10a your girlfriend will only get GSM and Edge (2G) speeds.
[XPERIA X10 Q&A, Help & Troubleshooting] geordie 34:
Not sure how your networks work in us
[XPERIA X10 Q&A, Help & Troubleshooting] silentknight16:
But do i have to flash the whole thing or just flash the speedfix? i have speedfix v3.0....

sorry for the noob question
[XPERIA X10 Q&A, Help & Troubleshooting] geordie 34:
On wb thread it tells you to flash the Rom then the fix you best thing to do is do a back up of your current Rom then flash the fix if anything goes wrong then you will have your back up then you can flash everything if needs be
[XPERIA X10 Q&A, Help & Troubleshooting] Tone503773:
Yeah i know that but she is not a heavy user so she probably will not be able to tell