Jump to content
PaulOBrien

Advent Vega kernel source code now available!

Recommended Posts

No problems... I fear suspend will be a pain in the neck to debug... :S

Yeah unfortunately i tend to agree .. best i can think of just now is to put PM debug on in kernel and get kmesg dumping to sdcard so it maybe catches at least something on the way down, may give a clue as to where to look next ...

edit yeah seemingly not really helpful ... maybe ill try full debug mode in kernel and not just PM .. looks like my userland process is killed when suspend hits this part

<4>[ 49.564611] AR6000 disconnected from 00:3a:9a:00:41:01

<4>[ 49.564804] Disconnect Reason is 3

<4>[ 49.564975] Protocol Reason/Status Code is 0

<4>[ 49.565146] AssocResp Frame = NULL

<6>[ 110.683637] request_suspend_state: sleep (0->3) at 110609288002 (2012-01-04 15:48:33.809018001 UTC)

<6>[ 110.692938] Disabling touchscreen

<4>[ 110.709278] tegra_pwm tegra_pwm.0: pwm_disable called on disabled PWM

Though im not sure if the last line looks normal ...

edit :- managed to catch a suspend cycle when tee'ing a logcat to a file, it suspended then woke up some seconds, cant be sure i hit deep sleep but hey, its the most logs ive got yet out of it ... there's an error or 2 in there as well....

http://pastebin.com/xNkduNUG

Edited by Cass67

Share this post


Link to post
Share on other sites

Yeah unfortunately i tend to agree .. best i can think of just now is to put PM debug on in kernel and get kmesg dumping to sdcard so it maybe catches at least something on the way down, may give a clue as to where to look next ...

edit yeah seemingly not really helpful ... maybe ill try full debug mode in kernel and not just PM .. looks like my userland process is killed when suspend hits this part

<4>[ 49.564611] AR6000 disconnected from 00:3a:9a:00:41:01

<4>[ 49.564804] Disconnect Reason is 3

<4>[ 49.564975] Protocol Reason/Status Code is 0

<4>[ 49.565146] AssocResp Frame = NULL

<6>[ 110.683637] request_suspend_state: sleep (0->3) at 110609288002 (2012-01-04 15:48:33.809018001 UTC)

<6>[ 110.692938] Disabling touchscreen

<4>[ 110.709278] tegra_pwm tegra_pwm.0: pwm_disable called on disabled PWM

Though im not sure if the last line looks normal ...

I think we got that same last line on the .36 kernel when we had enabled both the framebuffer console and the reporting method to userland that screen was suspending... I will check the framebuffer suspend code...

Share this post


Link to post
Share on other sites

hi, me again, can you guys check something about the PPP. i ran the command pppd ttyUSB2 and it gives back,

"This system lacks kernel support for PPP. This could be because the PPP kernel module could not be loaded, or because PPP was not included in kernel configuration. If PPP was included as a module, try 'sbin/modprobe -v ppp'.... "

I suspect that PPP was not run to initiate the connection. I've read somewhere that rild will call pppd to make data connection..

Share this post


Link to post
Share on other sites
hi, me again, can you guys check something about the PPP. i ran the command pppd ttyUSB2 and it gives back,

"This system lacks kernel support for PPP. This could be because the PPP kernel module could not be loaded, or because PPP was not included in kernel configuration. If PPP was included as a module, try 'sbin/modprobe -v ppp'.... "

I suspect that PPP was not run to initiate the connection. I've read somewhere that rild will call pppd to make data connection..

Yeah that's probably right, can't remember adding ppp support.. IM sure it should be using rmnet though. This is much better supported than ppp last I looked. I'll add ppp next kernel I build.

Share this post


Link to post
Share on other sites

Yeah that's probably right, can't remember adding ppp support.. IM sure it should be using rmnet though. This is much better supported than ppp last I looked. I'll add ppp next kernel I build.

thank you Cass! was looking at the logs and found out ppp was not initiated. looking forward for the ppp support!

Share this post


Link to post
Share on other sites

I think we got that same last line on the .36 kernel when we had enabled both the framebuffer console and the reporting method to userland that screen was suspending... I will check the framebuffer suspend code...

in comparison to the pastebin of a dmesg earlier i posted this one actually appears to be from a suspended system which looked while at i was at work to be toast. Upon my return to it this evening 6 hrs later switches on with the power button from sleep only to present me with the following dmesg and logcat ... handy huh :)

http://pastebin.com/5rfHsffh

http://pastebin.com/ZUCQh6nD

Judging by these files and the time that gone past it seems sleep was never really fully achieved, but the screen does switch off and not come back on demand... until some time later .. battery had lost 25% too ...

edit :- the ar6000 stuff seems a red herring as suspend fails when the ar6000.ko is not in play .. just thought id add that !

edit 2;- interestingly .. the Adam guys appear to be in the same boat ... no suspend with no usb plugged in ...

Cass

Edited by Cass67

Share this post


Link to post
Share on other sites

in comparison to the pastebin of a dmesg earlier i posted this one actually appears to be from a suspended system which looked while at i was at work to be toast. Upon my return to it this evening 6 hrs later switches on with the power button from sleep only to present me with the following dmesg and logcat ... handy huh :)

http://pastebin.com/5rfHsffh

http://pastebin.com/ZUCQh6nD

Judging by these files and the time that gone past it seems sleep was never really fully achieved, but the screen does switch off and not come back on demand... until some time later .. battery had lost 25% too ...

edit :- the ar6000 stuff seems a red herring as suspend fails when the ar6000.ko is not in play .. just thought id add that !

edit 2;- interestingly .. the Adam guys appear to be in the same boat ... no suspend with no usb plugged in ...

Cass

Believe it or not, the thing preventing the device to suspend seems to be a wakelock ... There is an "easy" way to cause the tablet to reset. Just add a call to emergency_restart() function in the interrupt handling routine of the gpio-long-short key driver. So, pressing the "back"button will reset the system without losing the ram contents, and that means getting the previous log using ram-console :)

Now i have to find out the exact wakelock causing this problem...

This seems to still apply... http://kzjblog.appsp...suspend-en.html ... wakelock debugging...

edit1: Take a look at this piece of log while trying to make the device go into sleep... :)

597.856118] initcall arm-pmu.0_i+ returned 0 after 1 usecs

[ 597.856152] calling reg-virtual-adj-voltage.4+ @ 59, parent: platform

[ 597.856188] initcall reg-virtual-adj-voltage.4_i+ returned 0 after 1 usecs

[ 597.856223] calling reg-fixed-voltage.3+ @ 59, parent: platform

[ 597.856259] initcall reg-fixed-voltage.3_i+ returned 0 after 1 usecs

[ 597.856293] calling tegra-i2c.3+ @ 59, parent: platform

[ 597.856331] initcall tegra-i2c.3_i+ returned 0 after 5 usecs

[ 597.856364] calling tegra-i2c.1+ @ 59, parent: platform

[ 597.856399] initcall tegra-i2c.1_i+ returned 0 after 3 usecs

[ 597.856432] calling tegra-i2c.0+ @ 59, parent: platform

[ 597.856467] initcall tegra-i2c.0_i+ returned 0 after 3 usecs

[ 597.856507] calling reg-dummy+ @ 59, parent: platform

[ 597.856539] initcall reg-dummy_i+ returned 0 after 1 usecs

[ 597.856572] calling power.0+ @ 59, parent: platform

[ 597.856602] active wake lock mmc_delayed_work

[ 597.856628] power_suspend_late return -11

[ 597.856702] pm_noirq_op(): platform_pm_suspend_noirq+0x0/0x38 returns -11

[ 597.856740] initcall power.0_i+ returned -11 after 132 usecs

[ 597.856775] PM: Device power.0 failed to suspend late: error -11

[ 597.856811] calling reg-dummy+ @ 59, parent: platform

[ 597.856844] initcall reg-dummy_i+ returned 0 after 1 usecs

[ 597.856881] calling tegra-i2c.0+ @ 59, parent: platform

[ 597.857960] initcall tegra-i2c.0_i+ returned 0 after 1019 usecs

[ 597.857994] calling tegra-i2c.1+ @ 59, parent: platform

[ 597.859065] initcall tegra-i2c.1_i+ returned 0 after 1012 usecs

[ 597.859099] calling tegra-i2c.3+ @ 59, parent: platform

[ 597.860166] initcall tegra-i2c.3_i+ returned 0 after 1009 usecs

[ 597.860200] calling reg-fixed-voltage.3+ @ 59, parent: platform

[ 597.860235] initcall reg-fixed-voltage.3_i+ returned 0 after 0 usecs

[ 597.860270] calling reg-virtual-adj-voltage.4+ @ 59, parent: platform

[ 597.860306] initcall reg-virtual-adj-voltage.4_i+ returned 0 after 1 usecs

There it is the answer... active wake lock mmc_delayed_work

So, it is the mmc driver the problem... Take into accounf i didn't have the mmc mounted or the wifi module loaded...

Edit2: Seems to be a bug in the mmc tegra2 driver...

Edited by ejtagle

Share this post


Link to post
Share on other sites

Believe it or not, the thing preventing the device to suspend seems to be a wakelock ... There is an "easy" way to cause the tablet to reset. Just add a call to emergency_restart() function in the interrupt handling routine of the gpio-long-short key driver. So, pressing the "back"button will reset the system without losing the ram contents, and that means getting the previous log using ram-console

Now i have to find out the exact wakelock causing this problem...

This seems to still apply... http://kzjblog.appsp...suspend-en.html ... wakelock debugging...

edit1: Take a look at this piece of log while trying to make the device go into sleep...

There it is the answer... active wake lock mmc_delayed_work

So, it is the mmc driver the problem... Take into accounf i didn't have the mmc mounted or the wifi module loaded...

Edit2: Seems to be a bug in the mmc tegra2 driver...

Funnily enough I did read that doc :-)

Didn't know about the emergency restart function, every day is a school day as they say :-)

Nice work

Share this post


Link to post
Share on other sites

There it is the answer... active wake lock mmc_delayed_work

So, it is the mmc driver the problem... Take into accounf i didn't have the mmc mounted or the wifi module loaded...

Edit2: Seems to be a bug in the mmc tegra2 driver...

Firstly,

Fantastic work both of you Cass & Ed, the two of you at moment are the backbone of the Vega/Shuttle global development!!!!

I was looking at this last night after Cass posted the log files and I noticed that you a problem with the mounting of the SD Card. Cass I think hinted that the Vega will recover from sleep if the USB is plugged in but wont if there is no external attachments.

Android/ICS has allocated SD Card as “internal storage” and emulated external as part of the MountService.java.

In your Logcat it shows:

• 01-04 17:19:55.390 I/SystemServer( 148): Mount Service

• 01-04 17:19:55.390 D/MountService( 148): got storage path: /mnt/sdcard description: Internal Storage primary: true removable: false emulated: true mtpReserve: 100 allowMassStorage: false maxFileSize: 0

• 01-04 17:19:55.390 D/MountService( 148): using emulated external storage

public MountService(Context context) {

mContext = context;

Resources resources = context.getResources();

readStorageList(resources);

if (mPrimaryVolume != null) {

mExternalStoragePath = mPrimaryVolume.getPath();

mEmulateExternalStorage = mPrimaryVolume.isEmulated();

if (mEmulateExternalStorage) {

Slog.d(TAG, "using emulated external storage");

mVolumeStates.put(mExternalStoragePath, Environment.MEDIA_MOUNTED);

}

}

The mountservice get the resource list from the storage_list.xml included in the build. To solve this I think you need to have a look at the storage_list.xml in the overlays and set the emmc as the initial storage point.

As for the Wifi, there is a setting in advanced: “Keep Wi-Fi on during sleep” – set this to never and see how you get on.

Billy..

Share this post


Link to post
Share on other sites

Firstly,

Fantastic work both of you Cass & Ed, the two of you at moment are the backbone of the Vega/Shuttle global development!!!!

I was looking at this last night after Cass posted the log files and I noticed that you a problem with the mounting of the SD Card. Cass I think hinted that the Vega will recover from sleep if the USB is plugged in but wont if there is no external attachments.

Android/ICS has allocated SD Card as “internal storage” and emulated external as part of the MountService.java.

In your Logcat it shows:

• 01-04 17:19:55.390 I/SystemServer( 148): Mount Service

• 01-04 17:19:55.390 D/MountService( 148): got storage path: /mnt/sdcard description: Internal Storage primary: true removable: false emulated: true mtpReserve: 100 allowMassStorage: false maxFileSize: 0

• 01-04 17:19:55.390 D/MountService( 148): using emulated external storage

public MountService(Context context) {

mContext = context;

Resources resources = context.getResources();

readStorageList(resources);

if (mPrimaryVolume != null) {

mExternalStoragePath = mPrimaryVolume.getPath();

mEmulateExternalStorage = mPrimaryVolume.isEmulated();

if (mEmulateExternalStorage) {

Slog.d(TAG, "using emulated external storage");

mVolumeStates.put(mExternalStoragePath, Environment.MEDIA_MOUNTED);

}

}

The mountservice get the resource list from the storage_list.xml included in the build. To solve this I think you need to have a look at the storage_list.xml in the overlays and set the emmc as the initial storage point.

As for the Wifi, there is a setting in advanced: “Keep Wi-Fi on during sleep” – set this to never and see how you get on.

Billy..

Hi Billy,

The wifi workaround does not work for us I tried it last night, it seems to work for the Adam dev guys though :-)

I also know about the sdcard being wrongly configured in Android, it's one more thing on the list to resolve, just could not be bothered compiling it again right now. I'll be surprised though it that was the root cause of the sleep problem ;-) Cheers Cass

Edited by Cass67

Share this post


Link to post
Share on other sites

Hi,

Great work on ICS guys, sorry to interrupt that work (I know I am annoying like alwaysrolleyes.gif)

I have a question, I can't get the APN settings to save on HoneyIce, I don't know if it previously worked on VegaComb but a member of tabletroms gave me a log of it, so I tried a few things I could think of but it did not work.

If you magicians could work it out, I would again be in your debt!

Here is the log:

01-03 21:41:48.010 D/dalvikvm(3285): GC_CONCURRENT freed 15K, 37% free 8560K/13383K, paused 1ms+3ms

01-03 21:41:48.850 I/TabletStatusBar(186): DISABLE_BACK: no

01-03 21:41:48.860 D/AndroidRuntime(3313): Shutting down VM

01-03 21:41:48.860 W/dalvikvm(3313): threadid=1: thread exiting with uncaught exception (group=0x40037760)

01-03 21:41:48.860 E/AndroidRuntime(3313): FATAL EXCEPTION: main

01-03 21:41:48.860 E/AndroidRuntime(3313): java.lang.RuntimeException: Unable to resume activity {com.android.settings/com.android.settings.ApnSettings}: java.lang.IllegalStateException: trying to requery an already closed cursor android.content.ContentResolver$CursorWrapperInner @4063f0e8

01-03 21:41:48.860 E/AndroidRuntime(3313): at android.app.ActivityThread.performResumeActivity(A ctivityThread.java:2288)

01-03 21:41:48.860 E/AndroidRuntime(3313): at android.app.ActivityThread.handleResumeActivity(Ac tivityThread.java:2316)

01-03 21:41:48.860 E/AndroidRuntime(3313): at android.app.ActivityThread$H.handleMessage(Activit yThread.java:1050)

01-03 21:41:48.860 E/AndroidRuntime(3313): at android.os.Handler.dispatchMessage(Handler.java:99 )

01-03 21:41:48.860 E/AndroidRuntime(3313): at android.os.Looper.loop(Looper.java:132)

01-03 21:41:48.860 E/AndroidRuntime(3313): at android.app.ActivityThread.main(ActivityThread.jav a:4123)

01-03 21:41:48.860 E/AndroidRuntime(3313): at java.lang.reflect.Method.invokeNative(Native Method)

01-03 21:41:48.860 E/AndroidRuntime(3313): at java.lang.reflect.Method.invoke(Method.java:491)

01-03 21:41:48.860 E/AndroidRuntime(3313): at com.android.internal.os.ZygoteInit$MethodAndArgsCa ller.run(ZygoteInit.java:841)

01-03 21:41:48.860 E/AndroidRuntime(3313): at com.android.internal.os.ZygoteInit.main(ZygoteInit .java:599)

01-03 21:41:48.860 E/AndroidRuntime(3313): at dalvik.system.NativeStart.main(Native Method)

01-03 21:41:48.860 E/AndroidRuntime(3313): Caused by: java.lang.IllegalStateException: trying to requery an already closed cursor android.content.ContentResolver$CursorWrapperInner @4063f0e8

01-03 21:41:48.860 E/AndroidRuntime(3313): at android.app.Activity.performRestart(Activity.java: 4438)

01-03 21:41:48.860 E/AndroidRuntime(3313): at android.app.Activity.performResume(Activity.java:4 460)

01-03 21:41:48.860 E/AndroidRuntime(3313): at android.app.ActivityThread.performResumeActivity(A ctivityThread.java:2278)

01-03 21:41:48.860 E/AndroidRuntime(3313): ... 10 more

01-03 21:41:48.870 W/ActivityManager(136): Force finishing activity com.android.settings/.ApnSettings

01-03 21:41:49.170 D/dalvikvm(186): GC_FOR_ALLOC freed 1121K, 20% free 9431K/11655K, paused 31ms

01-03 21:41:49.370 W/ActivityManager(136): Activity pause timeout for ActivityRecord{4073c078 com.android.settings/.ApnSettings}

01-03 21:41:50.330 I/Process (3313): Sending signal. PID: 3313 SIG: 9

01-03 21:41:50.360 E/InputDispatcher(136): channel '4097bef8 com.android.settings/com.android.settings.Settings (server)' ~ Consumer closed input channel or an error occurred. events=0x8

01-03 21:41:50.360 E/InputDispatcher(136): channel '4097bef8 com.android.settings/com.android.settings.Settings (server)' ~ Channel is unrecoverably broken and will be disposed!

01-03 21:41:50.360 I/ActivityManager(136): Process com.android.settings (pid 3313) has died.

01-03 21:41:50.360 I/WindowManager(136): WIN DEATH: Window{4097bef8 com.android.settings/com.android.settings.Settings paused=false}

Kind Regards,

Areo

Edited by Areo

Share this post


Link to post
Share on other sites

Hi,

Great work on ICS guys, sorry to interrupt that work (I know I am annoying like alwaysrolleyes.gif)

I have a question, I can't get the APN settings to save on HoneyIce, I don't know if it previously worked on VegaComb but a member of tabletroms gave me a log of it, so I tried a few things I could think of but it did not work.

If you magicians could work it out, I would again be in your debt!

Here is the log:

01-03 21:41:48.010 D/dalvikvm(3285): GC_CONCURRENT freed 15K, 37% free 8560K/13383K, paused 1ms+3ms<br style=color: rgb(72, 72, 72); font-family: Verdana, Arial, Tahoma, Calibri, Geneva, sans-serif; font-size: 13px; background-color: rgb(250, 250, 250); ">01-03 21:41:48.850 I/TabletStatusBar(186): DISABLE_BACK: no<br style=color: rgb(72, 72, 72); font-family: Verdana, Arial, Tahoma, Calibri, Geneva, sans-serif; font-size: 13px; background-color: rgb(250, 250, 250); ">01-03 21:41:48.860 D/AndroidRuntime(3313): Shutting down VM<br style=color: rgb(72, 72, 72); font-family: Verdana, Arial, Tahoma, Calibri, Geneva, sans-serif; font-size: 13px; background-color: rgb(250, 250, 250); ">01-03 21:41:48.860 W/dalvikvm(3313): threadid=1: thread exiting with uncaught exception (group=0x40037760)<br style=color: rgb(72, 72, 72); font-family: Verdana, Arial, Tahoma, Calibri, Geneva, sans-serif; font-size: 13px; background-color: rgb(250, 250, 250); ">01-03 21:41:48.860 E/AndroidRuntime(3313): FATAL EXCEPTION: main<br style=color: rgb(72, 72, 72); font-family: Verdana, Arial, Tahoma, Calibri, Geneva, sans-serif; font-size: 13px; background-color: rgb(250, 250, 250); ">01-03 21:41:48.860 E/AndroidRuntime(3313): java.lang.RuntimeException: Unable to resume activity {com.android.settings/com.android.settings.ApnSettings}: java.lang.IllegalStateException: trying to requery an already closed cursor android.content.ContentResolver$CursorWrapperInner @4063f0e8<br style=color: rgb(72, 72, 72); font-family: Verdana, Arial, Tahoma, Calibri, Geneva, sans-serif; font-size: 13px; background-color: rgb(250, 250, 250); ">01-03 21:41:48.860 E/AndroidRuntime(3313): at android.app.ActivityThread.performResumeActivity(A ctivityThread.java:2288)<br style=color: rgb(72, 72, 72); font-family: Verdana, Arial, Tahoma, Calibri, Geneva, sans-serif; font-size: 13px; background-color: rgb(250, 250, 250); ">01-03 21:41:48.860 E/AndroidRuntime(3313): at android.app.ActivityThread.handleResumeActivity(Ac tivityThread.java:2316)<br style=color: rgb(72, 72, 72); font-family: Verdana, Arial, Tahoma, Calibri, Geneva, sans-serif; font-size: 13px; background-color: rgb(250, 250, 250); ">01-03 21:41:48.860 E/AndroidRuntime(3313): at android.app.ActivityThread$H.handleMessage(Activit yThread.java:1050)<br style=color: rgb(72, 72, 72); font-family: Verdana, Arial, Tahoma, Calibri, Geneva, sans-serif; font-size: 13px; background-color: rgb(250, 250, 250); ">01-03 21:41:48.860 E/AndroidRuntime(3313): at android.os.Handler.dispatchMessage(Handler.java:99 )<br style=color: rgb(72, 72, 72); font-family: Verdana, Arial, Tahoma, Calibri, Geneva, sans-serif; font-size: 13px; background-color: rgb(250, 250, 250); ">01-03 21:41:48.860 E/AndroidRuntime(3313): at android.os.Looper.loop(Looper.java:132)<br style=color: rgb(72, 72, 72); font-family: Verdana, Arial, Tahoma, Calibri, Geneva, sans-serif; font-size: 13px; background-color: rgb(250, 250, 250); ">01-03 21:41:48.860 E/AndroidRuntime(3313): at android.app.ActivityThread.main(ActivityThread.jav a:4123)<br style=color: rgb(72, 72, 72); font-family: Verdana, Arial, Tahoma, Calibri, Geneva, sans-serif; font-size: 13px; background-color: rgb(250, 250, 250); ">01-03 21:41:48.860 E/AndroidRuntime(3313): at java.lang.reflect.Method.invokeNative(Native Method)<br style=color: rgb(72, 72, 72); font-family: Verdana, Arial, Tahoma, Calibri, Geneva, sans-serif; font-size: 13px; background-color: rgb(250, 250, 250); ">01-03 21:41:48.860 E/AndroidRuntime(3313): at java.lang.reflect.Method.invoke(Method.java:491)<br style=color: rgb(72, 72, 72); font-family: Verdana, Arial, Tahoma, Calibri, Geneva, sans-serif; font-size: 13px; background-color: rgb(250, 250, 250); ">01-03 21:41:48.860 E/AndroidRuntime(3313): at com.android.internal.os.ZygoteInit$MethodAndArgsCa ller.run(ZygoteInit.java:841)<br style=color: rgb(72, 72, 72); font-family: Verdana, Arial, Tahoma, Calibri, Geneva, sans-serif; font-size: 13px; background-color: rgb(250, 250, 250); ">01-03 21:41:48.860 E/AndroidRuntime(3313): at com.android.internal.os.ZygoteInit.main(ZygoteInit .java:599)<br style=color: rgb(72, 72, 72); font-family: Verdana, Arial, Tahoma, Calibri, Geneva, sans-serif; font-size: 13px; background-color: rgb(250, 250, 250); ">01-03 21:41:48.860 E/AndroidRuntime(3313): at dalvik.system.NativeStart.main(Native Method)<br style=color: rgb(72, 72, 72); font-family: Verdana, Arial, Tahoma, Calibri, Geneva, sans-serif; font-size: 13px; background-color: rgb(250, 250, 250); ">01-03 21:41:48.860 E/AndroidRuntime(3313): Caused by: java.lang.IllegalStateException: trying to requery an already closed cursor android.content.ContentResolver$CursorWrapperInner @4063f0e8<br style=color: rgb(72, 72, 72); font-family: Verdana, Arial, Tahoma, Calibri, Geneva, sans-serif; font-size: 13px; background-color: rgb(250, 250, 250); ">01-03 21:41:48.860 E/AndroidRuntime(3313): at android.app.Activity.performRestart(Activity.java: 4438)<br style=color: rgb(72, 72, 72); font-family: Verdana, Arial, Tahoma, Calibri, Geneva, sans-serif; font-size: 13px; background-color: rgb(250, 250, 250); ">01-03 21:41:48.860 E/AndroidRuntime(3313): at android.app.Activity.performResume(Activity.java:4 460)<br style=color: rgb(72, 72, 72); font-family: Verdana, Arial, Tahoma, Calibri, Geneva, sans-serif; font-size: 13px; background-color: rgb(250, 250, 250); ">01-03 21:41:48.860 E/AndroidRuntime(3313): at android.app.ActivityThread.performResumeActivity(A ctivityThread.java:2278)<br style=color: rgb(72, 72, 72); font-family: Verdana, Arial, Tahoma, Calibri, Geneva, sans-serif; font-size: 13px; background-color: rgb(250, 250, 250); ">01-03 21:41:48.860 E/AndroidRuntime(3313): ... 10 more<br style=color: rgb(72, 72, 72); font-family: Verdana, Arial, Tahoma, Calibri, Geneva, sans-serif; font-size: 13px; background-color: rgb(250, 250, 250); ">01-03 21:41:48.870 W/ActivityManager(136): Force finishing activity com.android.settings/.ApnSettings<br style=color: rgb(72, 72, 72); font-family: Verdana, Arial, Tahoma, Calibri, Geneva, sans-serif; font-size: 13px; background-color: rgb(250, 250, 250); ">01-03 21:41:49.170 D/dalvikvm(186): GC_FOR_ALLOC freed 1121K, 20% free 9431K/11655K, paused 31ms<br style=color: rgb(72, 72, 72); font-family: Verdana, Arial, Tahoma, Calibri, Geneva, sans-serif; font-size: 13px; background-color: rgb(250, 250, 250); ">01-03 21:41:49.370 W/ActivityManager(136): Activity pause timeout for ActivityRecord{4073c078 com.android.settings/.ApnSettings}<br style=color: rgb(72, 72, 72); font-family: Verdana, Arial, Tahoma, Calibri, Geneva, sans-serif; font-size: 13px; background-color: rgb(250, 250, 250); ">01-03 21:41:50.330 I/Process (3313): Sending signal. PID: 3313 SIG: 9<br style=color: rgb(72, 72, 72); font-family: Verdana, Arial, Tahoma, Calibri, Geneva, sans-serif; font-size: 13px; background-color: rgb(250, 250, 250); ">01-03 21:41:50.360 E/InputDispatcher(136): channel '4097bef8 com.android.settings/com.android.settings.Settings (server)' ~ Consumer closed input channel or an error occurred. events=0x8<br style=color: rgb(72, 72, 72); font-family: Verdana, Arial, Tahoma, Calibri, Geneva, sans-serif; font-size: 13px; background-color: rgb(250, 250, 250); ">01-03 21:41:50.360 E/InputDispatcher(136): channel '4097bef8 com.android.settings/com.android.settings.Settings (server)' ~ Channel is unrecoverably broken and will be disposed!<br style=color: rgb(72, 72, 72); font-family: Verdana, Arial, Tahoma, Calibri, Geneva, sans-serif; font-size: 13px; background-color: rgb(250, 250, 250); ">01-03 21:41:50.360 I/ActivityManager(136): Process com.android.settings (pid 3313) has died.<br style=color: rgb(72, 72, 72); font-family: Verdana, Arial, Tahoma, Calibri, Geneva, sans-serif; font-size: 13px; background-color: rgb(250, 250, 250); ">01-03 21:41:50.360 I/WindowManager(136): WIN DEATH: Window{4097bef8 com.android.settings/com.android.settings.Settings paused=false}

Kind Regards,

Areo

WTF's up with modaco these days, been seeing a lot of that markup in my posts ... can you repost .. thats too hard to read ...

edit .. lol done just as i posted this :)

Cheers

Edited by Cass67

Share this post


Link to post
Share on other sites

WTF's up with modaco these days, been seeing a lot of that markup in my posts ... can you repost .. thats too hard to read ...

Cheers

I edited it, also noticed it after I posted.

Areo

Edit:

So any idea how to fix it?

It isn't a bad flash because more users have it and I also experienced it

Edited by Areo

Share this post


Link to post
Share on other sites

I edited it, also noticed it after I posted.

Areo

So your trying to add and APN by hand ? have you tried to just add the details into an apns.conf file ? ... id say judging by what ive seen on googling that error that app is using a deprecated function to query the db . honeycomb apparently changed things up from prior versions. Not sure there will be a solution if thats the stock HC framework and not custom app ...

Share this post


Link to post
Share on other sites

So your trying to add and APN by hand ? have you tried to just add the details into an apns.conf file ? ... id say judging by what ive seen on googling that error that app is using a deprecated function to query the db . honeycomb apparently changed things up from prior versions. Not sure there will be a solution if thats the stock HC framework and not custom app ...

I tried by hand first.

Then with apns.conf, then reboot but it woudn't show up. I also read that people with Xoom also had the issue, but then there were several reports it was gone, so I compared the xml files in settings.apk to get started (no diffrence). Then I read that the problems still persisted. Could it really be a HC bug? I also tried a edited patch which should solve it on the samsung galaxy tab and sometimes works on xoom. Also no diffrence and then I ran out of time.

Areo

Edited by Areo

Share this post


Link to post
Share on other sites

I tried by hand first.

Then with apns.conf, then reboot but it woudn't show up. I also read that people with Xoom also had the issue, but then there were several reports it was gone, so I compared the xml files in settings.apk to get started (no diffrence). Then I read that the problems still persisted. Could it really be a HC bug? I also tried a edited patch which should solve it on the samsung galaxy tab and sometimes works on xoom. Also no diffrence and then I ran out of time.

Areo

Would not surprise me if it were an HC bug .. probably things like this prevented G from releasing the source as it has many issues ..

http://stackoverflow.com/questions/6171359/honeycomb-and-cursors-frustrated

Share this post


Link to post
Share on other sites

Would not surprise me if it were an HC bug .. probably things like this prevented G from releasing the source as it has many issues ..

http://stackoverflow...sors-frustrated

So if I understand correctly it would be fixed by this:

Cursor oldCursor = mAdapter.getCursor(); mAdapter.changeCursor(newCursor);

stopManagingCursor(oldCursor);

or this:

if (Build.VERSION.SDK_INT < VersionUtil.HONEYCOMB) {

super.startManagingCursor©;

Won't it produce more/other errors with other system components then?

Areo

Share this post


Link to post
Share on other sites

So if I understand correctly it would be fixed by this:

Cursor oldCursor = mAdapter.getCursor(); mAdapter.changeCursor(newCursor);

stopManagingCursor(oldCursor);

or this:

if (Build.VERSION.SDK_INT < VersionUtil.HONEYCOMB) {

super.startManagingCursor©;

Won't it produce more/other errors with other system components then?

Areo

seems so ..

No idea mate ... just reading what it says there.. could be not much use that functionality or at least if so it may be better coded or id have expected more errors :)

Edited by Cass67

Share this post


Link to post
Share on other sites

seems so ..

No idea mate ... just reading what it says there.. could be not much use that functionality or at least if so it may be better coded or id have expected more errors :)

I don't think it will fix it...

Because it can't even see the apn in apns-conf.xml.

Will give it a shot later.

Thanks for the help.

About something else:

I have never been the best in C, but I want to learn some more about kernel development (which is in C if I saw it correctly).

Any chance you could teach me the basics ? :P

Areo

Share this post


Link to post
Share on other sites

I don't think it will fix it...

Because it can't even see the apn in apns-conf.xml.

Will give it a shot later.

Thanks for the help.

About something else:

I have never been the best in C, but I want to learn some more about kernel development (which is in C if I saw it correctly).

Any chance you could teach me the basics ? :P

Areo

Id be more interested in finding out why the apn addition you make is not read by the system ...

wrt to kernel dev .. google is your friend .. im not a kernel dev by any stretch of the imagination or real coder for that matter .. i can get around source but im not the man to give lessons or teach... sorry, And yes kernel is mostly C

Edited by Cass67

Share this post


Link to post
Share on other sites

Id be more interested in finding out why the apn addition you make is not read by the system ...

wrt to kernel dev .. google is your friend .. im not a kernel dev by any stretch of the imagination or real coder for that matter .. i can get around source but im not the man to give lessons or teach... sorry, And yes kernel is mostly C

I may have found the problem, will let you know later.

Same here, I also can get around with most of source but kernel is a whole diffrent story :P

Luckily we have Eduardo :)

Areo

Share this post


Link to post
Share on other sites

@cass & eduardo

Putting the ppp thingy aside, in our ICS build, was it built using LTE based network or GSM? because, if it was GSM, the messaging apps MMS.apk should be able to send out sms and receive call. I did not manage to send out sms even when i got the tablet to register to network. I dont know if i read correctly but i read somewhere that the RILD binary have 2 different version. one for LTE and one for GSM. From the log also, i see some LTE logs being recorded.

Share this post


Link to post
Share on other sites
Believe it or not, the thing preventing the device to suspend seems to be a wakelock ... There is an "easy" way to cause the tablet to reset. Just add a call to emergency_restart() function in the interrupt handling routine of the gpio-long-short key driver. So, pressing the "back"button will reset the system without losing the ram contents, and that means getting the previous log using ram-console :)Now i have to find out the exact wakelock causing this problem...This seems to still apply... http://kzjblog.appsp...suspend-en.html ... wakelock debugging...edit1: Take a look at this piece of log while trying to make the device go into sleep... :)There it is the answer... active wake lock mmc_delayed_workSo, it is the mmc driver the problem... Take into accounf i didn't have the mmc mounted or the wifi module loaded...Edit2: Seems to be a bug in the mmc tegra2 driver...
Seems someone else found that problem before... ;) -- http://lists.linaro.org/pipermail/linaro-dev/2011-July/005809.html

So, following that explanation, i wrote the required patch. Let's hope it will finally fix the suspend issues ... I will try it later, when i return home ;)

Regards,

Eduardo

suspendv2.rar

Edited by ejtagle

Share this post


Link to post
Share on other sites

Eduardo,

The suspend problem does seem familiar; maybe this may help as a reminder.

Billy..

Not suggesting this is the answer, just you have been here before.

Posted 24 July 2011 - 12:11 PM

Hi Eduardo , great work.

1. wlan under android solved

2. pwm issue solved.

3. battery status works under android

When CONFIG_CONSOLE_EARLYSUSPEND is set, pwm backlight control doesn´t work Set instead CONFIG_FB_EARLYSUSPEND , then pwm control works as expected

The git repo is up to date.

This post has been edited by rebel1: 24 July 2011 - 04:40 PM

Edited by BillyBobJoe

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.