MoDaCo is undergoing planned maintenance. Site functionality may be reduced - follow @modaco or @paulobrien on Twitter for updates.

  • Announcements

    • Reminder - MoDaCo position on illegal content

      ILLEGAL CONTENT I'd like to just reaffirm MoDaCo's position regarding piracy and illegal content in the light of some recent questions / postings. Posts will be censored by myself or my moderation team if the contain or link to: Illegal / pirated / cracked software or sites that host such software
      Nintendo emulators / ROMs or sites hosting them (in light of Nintendo's legal stance)


      CUSTOM ROMS

      You may discuss and post links to custom device ROMs on MoDaCo, provided the following rules are adhered to: ROMs must not be hosted directly in topic via the MoDaCo attachment system
      ROMs must not contain any illegal 3rd party software (this includes trial versions included without permission)
      ROMs must give full credit to the original author
      This decision has been taken in light of the huge amount of interest in this area of device customisation within the community, and member feedback! Please note that custom ROM discussion should be kept in specific device sub-areas, (e.g. Kaiser.MoDaCo.com for Kaiser based devices). ISSUES If you have any issues with this policy, please contact me directly via PM. P
    • Support MoDaCo by signing up to a MoDaCo Silver or Gold membership

      To sign up to an annual MoDaCo Silver subscription which will eliminate all ads from the site (as well as giving you access to the MoDaCo Online Kitchens for Android) for only £9.99 using PayPal, Credit or Debit Card, ensure you are logged in to the site, and then click the link below, which will take you directly to the subscription store! You can also sign up to an annual MoDaCo Gold subscription for £29.99, which adds the benefits listed below! PURCHASE A MODACO SUBSCRIPTION - FREE Titanium Backup Mobile for Android worth $5.99! - FREE 1 year PrivateInternetAccess.com worth $39.95! - FREE 1 year LastPass Premium worth $12! - FREE CalcConvert for Pocket PC from Binaryfish worth $17.95! - FREE Calendar Bar for Pocket PC from OmegaOne worth $9.99! - FREE CamerAware for Pocket PC and Smartphone from MoDaCo worth £19.99 / $30! - FREE Chronos for Pocket PC from ActiveKitten worth $14.95! - FREE CodeWallet Pro for Smartphone and Pocket PC from DeveloperOne worth up to $24.95! - FREE Concentrix for Pocket PC from eSoft Interactive worth $9.95! - FREE FlexMail for Pocket PC and Smartphone from WebIS worth up to $59.90! - FREE FTouchSL for Pocket PC from Vekoff s.r.o. worth 10 euro / $12.50! - FREE Jewel Challenge for Pocket PC from eSoft Interactive worth $9.95! - FREE John Cody's Alerts Pro for Smartphone from Omnisoft worth $14.95! - FREE LingvoSoft Talking Dictionary 2008 English <-> Dutch for Pocket PC from Lingvosoft worth $49.95! - FREE LingvoSoft Talking Dictionary 2008 English <-> French for Pocket PC from Lingvosoft worth $49.95! - FREE LingvoSoft Talking Dictionary 2008 English <-> German for Pocket PC from Lingvosoft worth $49.95! - FREE LingvoSoft Talking Dictionary 2008 English <-> Italian for Pocket PC from Lingvosoft worth $49.95! - FREE LingvoSoft Talking Dictionary 2008 English <-> Spanish for Pocket PC from Lingvosoft worth $49.95! - FREE LingvoSoft Dictionary English <-> Dutch for Smartphone from Lingvosoft worth $49.95! - FREE LingvoSoft Dictionary English <-> French for Smartphone from Lingvosoft worth $49.95! - FREE LingvoSoft Dictionary English <-> German for Smartphone from Lingvosoft worth $49.95! - FREE LingvoSoft Dictionary English <-> Russian for Smartphone from Lingvosoft worth $49.95! - FREE LingvoSoft Dictionary English <-> Turkish for Smartphone from Lingvosoft worth $49.95! - FREE Note2Self for Pocket PC and Smartphone from WebIS worth up to $19.90! - FREE Opera 8.60 for Pocket PC and Smartphone from Opera Software worth up to $48! - FREE Pocket Informant for Pocket PC and Smartphone from WebIS worth up to $59.90! - FREE Pocket Launcher for Pocket PC and Smartphone from Conduits worth $9.95! - FREE PTab for Pocket PC and Smartphone from z4soft worth up to $60! - FREE Resco Explorer for Pocket PC and Smartphone from Resco worth up to $49.90! - FREE Safemode for Pocket PC from monocube worth $12.95 - FREE SplashPhoto for Pocket PC and Smartphone from SplashData worth up to $59.90! - FREE Sprite Backup for Pocket PC and Smartphone from Sprite Software worth $29.95! - FREE Teksoft Glyphs UI for Pocket PC and Smartphone from Teksoft €9.95! - FREE Teksoft HeadsetRemote for Pocket PC and Smartphone from Teksoft €4.95! - FREE Traffic Jam for Pocket PC from eSoft Interactive worth $9.95! - FREE unlock (1 per year) from imei-check.co.uk - DISCOUNT of 10% at MoDaCo FairDeal - DISCOUNT of 10% at Semsons.com - FORUM - AD FREE SITE - FORUM - custom rank / title - FORUM - double competition entries - FORUM - double post attachment space - FORUM - no search flood control - FORUM - priority event registration - FORUM - triple PM space
    • Reminder: Selling items on the forum directly is not allowed

      Please note that selling items on the forum directly is not allowed by the forum rules. There is a forum for eBay auctions whereby you can list the items on eBay and link to them there. This is the ONLY forum for this type of activity. You may also advertise links to the eBay forum in your signature. Please note that selling directly in contravention of these rules will result in a warning / suspensions / ban.

Advent Vega kernel source code now available!

2862 posts in this topic

Posted (edited) · Report post

[quote name='ejtagle' timestamp='1361742927' post='2094421']
Debugging purposes, only... ;)
[/quote]

That's what I thought thanks :)

EDIT: I'm attempting to figure out where the libcamera drivers you guys are using originated from. If you could point me to them it would be a great help. Thanks!

EDIT2: Does the vega have hdmi and how is that working? I switched over to your libs yesterday and I lost the video portion of hdmi (I still have audio over hdmi).
EDIT3: After renaming hwcomposer.tegra_v0.so to hwcomposer.tegra.so hdmi is back and working. I'm wondering if you guys have that lib named incorrectly (just a heads up) Edited by fosser2
0

Share this post


Link to post
Share on other sites

Posted · Report post

[quote name='fosser2' timestamp='1361743315' post='2094425']
That's what I thought thanks :)

EDIT: I'm attempting to figure out where the libcamera drivers you guys are using originated from. If you could point me to them it would be a great help. Thanks!

EDIT2: Does the vega have hdmi and how is that working? I switched over to your libs yesterday and I lost the video portion of hdmi (I still have audio over hdmi).
EDIT3: After renaming hwcomposer.tegra_v0.so to hwcomposer.tegra.so hdmi is back and working. I'm wondering if you guys have that lib named incorrectly (just a heads up)
[/quote]

libcamera originated from android 2.2. Was severely modified by me to port it to android 3.0, then 4.0/4.1/4.2 ... In the way, I added some code taken from luvview, spcaview... Refactored out everything several times to make it more compatible...


- luvcview: Sdl video Usb Video Class grabber
(C) 2005,2006,2007 Laurent Pinchart && Michel Xhaard

- spcaview
(C) 2003,2004,2005,2006 Michel Xhaard
- JPEG decoder from http://www.bootsplash.org/
(C) August 2001 by Michael Schroeder, <[email protected]>

- libcamera V4L for Android 2.2
(C) 2009 0xlab.org - http://0xlab.org/
(C) 2010 SpectraCore Technologies
Author: Venkat Raju <[email protected]>
Based on a code from http://code.google.com/p/android-m912/downloads/detail?name=v4l2_camera_v2.patch
- guvcview: http://guvcview.berlios.de
Paulo Assis <[email protected]>
Nobuhiro Iwamatsu <[email protected]>


Regarding HDMI and the hwcomposer, i wrote a wrapper to be able to use the old hwcomposer with the 4.2 series. That is why you found the _v0.so file. That module is loaded by our wrapper. Another way to do it is to forward port the old hwcomposer support from 4.1 to 4.2...
1

Share this post


Link to post
Share on other sites

Posted · Report post

ejtagle,

I'm wondering what happens when you guys have hdmi plugged into your tablet and you try to sleep it. Our tablet surfaceflinger crashes because of gralloc.tegra.so. Was gralloc patched also for 4.2? Below is the crash.

ADB: http://pastebin.com/v15a0WGP
SERIAL: http://pastebin.com/dx0Xb23Y

I believe it is a lib issue related to the gralloc. As for the IRQ issue in the serial file, I believe this is caused from some i2c settings. I'm not overly concerned about that right now because I'm pretty sure they are 2 separate issues. Lastly HDMI does output as well as hdmi audio. Just likes to crash when someone attempts to sleep w/ hdmi plugged in.
0

Share this post


Link to post
Share on other sites

Posted · Report post

[quote name='fosser2' timestamp='1362083645' post='2096264']
ejtagle,

I'm wondering what happens when you guys have hdmi plugged into your tablet and you try to sleep it. Our tablet surfaceflinger crashes because of gralloc.tegra.so. Was gralloc patched also for 4.2? Below is the crash.

ADB: [url="http://pastebin.com/v15a0WGP"]http://pastebin.com/v15a0WGP[/url]
SERIAL: [url="http://pastebin.com/dx0Xb23Y"]http://pastebin.com/dx0Xb23Y[/url]

I believe it is a lib issue related to the gralloc. As for the IRQ issue in the serial file, I believe this is caused from some i2c settings. I'm not overly concerned about that right now because I'm pretty sure they are 2 separate issues. Lastly HDMI does output as well as hdmi audio. Just likes to crash when someone attempts to sleep w/ hdmi plugged in.
[/quote]

[color=#000000][font=Consolas, Menlo, Monaco, 'Lucida Console', 'Liberation Mono', 'DejaVu Sans Mono', 'Bitstream Vera Sans Mono', monospace, serif][size=3]tegra_fb_blank , called from [/size][/font][/color][color=#000000][font=Consolas, Menlo, Monaco, 'Lucida Console', 'Liberation Mono', 'DejaVu Sans Mono', 'Bitstream Vera Sans Mono', monospace, serif][size=3]fb_blank, called from [/size][/font][/color][color=#000000][font=Consolas, Menlo, Monaco, 'Lucida Console', 'Liberation Mono', 'DejaVu Sans Mono', 'Bitstream Vera Sans Mono', monospace, serif][size=3]sys_ioctl ... I think, just guessing here, that from userspace we are getting a [/size][/font][/color]

ioctl(fd, FBIOBLANK, fb_blank);

If you are using the hwcomposer wrapper i wrote, comment out all the contents of the tegra2_blank function, and just leave the
return 0; last line

Seems something is trying to blank the hdmi output.... and seems the operation is unsupported. That crashes the kernel video subsystem, that in turn crashes gralloc...
0

Share this post


Link to post
Share on other sites

Posted · Report post

Regarding video, I found out that the hwcomposer wrapper i wrote was causing some trouble when screen is turned off. Specifically, it did not disable vsync interrupts, so the linux kernel tegra video subsystem started to complain about syncpoints timing out... I have fixed the hwcomposer module so now it disables vsync while screen is off. I do suspect that this could also be the cause of some SODs... Please, test and report. At least, works for me and removes all errors related to syncpoints and most errors related to gralloc.
0

Share this post


Link to post
Share on other sites

Posted · Report post

[quote name='ejtagle' timestamp='1362198539' post='2096789']
Regarding video, I found out that the hwcomposer wrapper i wrote was causing some trouble when screen is turned off. Specifically, it did not disable vsync interrupts, so the linux kernel tegra video subsystem started to complain about syncpoints timing out... I have fixed the hwcomposer module so now it disables vsync while screen is off. I do suspect that this could also be the cause of some SODs... Please, test and report. At least, works for me and removes all errors related to syncpoints and most errors related to gralloc.
[/quote]

I left the p10an01 on, so it tries to enter lp1 suspend mode. It did, as expected. 10 hours later, i pressed the physical back button, and the tablet did not wake up (this is expected behaviour, the tablet should not wake up with the back button, as that would mean it is not in deep sleep. The only physical button that is able to wake from deep sleep is the power button.

Now i pressed the power button and the tablet woke up without issues. The kernel log confirms the device was in deep sleep :) -- So, maybe we have fixed the SOD issues...
0

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

[quote name='ejtagle' timestamp='1362234802' post='2096932']
I left the p10an01 on, so it tries to enter lp1 suspend mode. It did, as expected. 10 hours later, i pressed the physical back button, and the tablet did not wake up (this is expected behaviour, the tablet should not wake up with the back button, as that would mean it is not in deep sleep. The only physical button that is able to wake from deep sleep is the power button.

Now i pressed the power button and the tablet woke up without issues. The kernel log confirms the device was in deep sleep :) -- So, maybe we have fixed the SOD issues...
[/quote]

Thanks,

I am building a new version of CM10.1 with the new hwc.
I will post it as alpha13 (lucky number hopefully). Edited by Scanno
0

Share this post


Link to post
Share on other sites

Posted · Report post

Sadly the new hwcomposer did not solve the SOD problem
0

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

Ejtagle,

I tried out the new HWC and although hardware decoding still works I'm having the same issues with HDMI.

ADB: [url="http://pastebin.com/wJkasPxp"]http://pastebin.com/wJkasPxp[/url] (at 16:10:01.341 I pushed sleep button)
Serial: [url="http://pastebin.com/t11uHjiw"]http://pastebin.com/t11uHjiw[/url]

Scanno: we seem to have sleep working (without HDMI) on our tablet. From this [url="http://pastebin.com/nbZcUceZ"]log[/url] you can see that my tablet enters and exits LP1 as it should. We are having other users tablets SOD though. Their last_kmsg files look similar to the following.
[url="http://pastebin.com/9xd96dVz"]http://pastebin.com/9xd96dVz[/url] Edited by fosser2
0

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

Well, here we go again trying to fix the SoD...

Added to the previous hwc fixes (that also seem to have fixed issues on screen not repainting), there was a problem with the wifi driver (ar6002) and our configuration and handling of the sdhci slot where it is connected.

I found out that the chipset was being powered down by one of our drivers (at the linux kernel level) while the system was entering deep suspend. Also, the driver itself was resseting the chipset when the system returned from deep sleep.. And the sdhci linux kernel component was powering down the sdhci bus.

All the above thing resulted in a complete reinitialization of the wifi card at resume, but that sometimes clashed with the ar6002 driver, that was expecting the card to remain powered ... Result: sometimes the system just crashed at resume... Because the ar6002 driver was sending commands to a dead bus and card, and waiting for responses...

The proper thing to do was (and that is exactly what is done on other platforms):
-Keep the wifi card in WoW mode (powered up), WoW mode will wake the device if some traffic targeting the device is received
-Keep the sdhci bus powered, othewise, the card cant wake the system
-Do not implement workarounds at the wifi driver level for things that are already fixed in the kernel
-Do not remove power to the card while suspended.

Android, if asked to, will load and unload the driver when enabling and disabling wifi. When the driver is unloaded, the wifi card is powered down

I am including the patched kernel, with the required .config file... Some changes were required, some configs were missing...
Also included de patched ar6002 driver sources (i removed the workarounds that are not required anymore) Edited by ejtagle
0

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

[quote name='fosser2' timestamp='1362348764' post='2097554']
Ejtagle,

I tried out the new HWC and although hardware decoding still works I'm having the same issues with HDMI.

ADB: [url="http://pastebin.com/wJkasPxp"]http://pastebin.com/wJkasPxp[/url] (at 16:10:01.341 I pushed sleep button)
Serial: [url="http://pastebin.com/t11uHjiw"]http://pastebin.com/t11uHjiw[/url]

Scanno: we seem to have sleep working (without HDMI) on our tablet. From this [url="http://pastebin.com/nbZcUceZ"]log[/url] you can see that my tablet enters and exits LP1 as it should. We are having other users tablets SOD though. Their last_kmsg files look similar to the following.
[url="http://pastebin.com/9xd96dVz"]http://pastebin.com/9xd96dVz[/url]
[/quote]

This seems to be a bug in the gralloc and/or surfaceflinger. I am guessing here, but seems gralloc is returning bogus values when asked tor the HDMI screen resolution, when it still not read from the display. That seems to be causing a division by 0 exception on surfaceflinger...

I guess that to fix this problem, a patch to surfaceflinger is required (or a wrapper to gralloc)

PD: After further investigation, the problem seems to be a race condition between gralloc and linux kernel video subsystem. When resuming, all HDMI displays are autodetected. But, that takes some time. Gralloc tries to read and set capabilities before the HDMI display is detected, and so, it gets an error and a 0x0 display. Then it tries to use that display... and crashes... This seems to be an actual tegra video subsystem bug... Edited by ejtagle
0

Share this post


Link to post
Share on other sites

Posted · Report post

I will also post here my latest bluetooth attempts. On the ui, everything seems to work, but, i was unable to make a bt connection, so guessing something is still missing... Nevertheless, it will be interesting to know if someone is able to actually use the bluetooth...

I am attaching 2 archives:
>The first one contains my latest libbt-vendor, that is required so bluedroid knows how to talk to the hci layer of the linux kernel
>The 2nd one is the required files that must be installed in /etc/bluetooth so the the libbtvendor is able to properly configure the bluetooth chipset
0

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

[quote name='ejtagle' timestamp='1362352104' post='2097588']
This seems to be a bug in the gralloc and/or surfaceflinger. I am guessing here, but seems gralloc is returning bogus values when asked tor the HDMI screen resolution, when it still not read from the display. That seems to be causing a division by 0 exception on surfaceflinger...

I guess that to fix this problem, a patch to surfaceflinger is required (or a wrapper to gralloc)[/quote]
Does this crash happen on the vega too like I posted?

[quote name='ejtagle' timestamp='1362352104' post='2097588']
PD: After further investigation, the problem seems to be a race condition between gralloc and linux kernel video subsystem. When resuming, all HDMI displays are autodetected. But, that takes some time. Gralloc tries to read and set capabilities before the HDMI display is detected, and so, it gets an error and a 0x0 display. Then it tries to use that display... and crashes... This seems to be an actual tegra video subsystem bug...[/quote]
I don't actually try to resume my tablet when this crash happens. As soon as I put it to sleep while on hdmi is when everything errors. It never makes it into LP1 while on hdmi. Edited by fosser2
0

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

[quote name='fosser2' timestamp='1362366374' post='2097629']
Does this crash happen on the vega too like I posted?


I don't actually try to resume my tablet when this crash happens. As soon as I put it to sleep while on hdmi is when everything errors. It never makes it into LP1 while on hdmi.
[/quote]

Yes, i get exactly the same error... If HDMI is enabled and the tablet tries to enter suspend, i get the same crashing gralloc.... Logcat is very similar to yours. I have tracked the issue to /drivers/video/tegra/dc/ext/dev.c ... They disable dcs on suspend, and reenable them on resume. The problem is that gralloc is unaware of those disablings, so, when they try to redetect hdmi, and the dcs are disabled, they get 0 values and that crashes gralloc...

It is a plain race condition between android framework and the suspend mechanism... Not synced at all...

This message is the one giving some clues...
NvGrPost: Failed, TEGRA_DC_EXT_FLIP 6

6= ENXIO . I partially reverse engineered gralloc, and found out this ioctl is a part of a secuence that tries to get hdmi resolution, copies output to hdmi, flips dcs to display into main ... I dont know why, but android is accessing the screen even when it is suspended...

gralloc should be discarding all screen access when the video subsystem is suspended... but it does not. And that seems to be the cause of gralloc crashes... Seems the only way to fix this is to also create a gralloc wrapper... Edited by ejtagle
0

Share this post


Link to post
Share on other sites

Posted · Report post

[quote name='ejtagle' timestamp='1362360102' post='2097620']I will also post here my latest bluetooth attempts. On the ui, everything seems to work, but, i was unable to make a bt connection, so guessing something is still missing... Nevertheless, it will be interesting to know if someone is able to actually use the bluetooth...

I am attaching 2 archives:
>The first one contains my latest libbt-vendor, that is required so bluedroid knows how to talk to the hci layer of the linux kernel
>The 2nd one is the required files that must be installed in /etc/bluetooth so the the libbtvendor is able to properly configure the bluetooth chipset[/quote]

Great I will have a go at this. The old Bluetooth stuff is that still needed or can in remove that?
I mean the hciattach. Is that now included?
0

Share this post


Link to post
Share on other sites

Posted · Report post

[quote name='Scanno' timestamp='1362385615' post='2097658']
Great I will have a go at this. The old Bluetooth stuff is that still needed or can in remove that?
I mean the hciattach. Is that now included?
[/quote]

The hciattach functionality is now included in libbt-vendor, We should need no part of bluez...
1

Share this post


Link to post
Share on other sites

Posted · Report post

[quote name='ejtagle' timestamp='1362398494' post='2097770']

The hciattach functionality is now included in libbt-vendor, We should need no part of bluez...[/quote]

OK i will remove all the old stuff and implement lbbt-vendor and put the files you posted in /etc/bluetooth

Lets see how far we can get. Do not know when i have time for this hopefully i can get some stuff done tonight.
1

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

[quote name='fosser2' timestamp='1362366374' post='2097629']
Does this crash happen on the vega too like I posted?


I don't actually try to resume my tablet when this crash happens. As soon as I put it to sleep while on hdmi is when everything errors. It never makes it into LP1 while on hdmi.
[/quote]

fosser2: Could you please try the attached hwc to see if the hdmi crashes continue ? - What i did was to disable the hwc when the screen is turned off. This seems to cure the crashes. At the same time, i get a "Cannot lock buffer" error on gralloc, but, it does not crash, and, as soon as screen is turned on again, it resumes working without issues... or at least, that is what i believe...

To all the other people... Please do not integrate this hwc to any rom.. not yet... It still does not work properly. The problem i see is that when the system is turning off the screen, it still tries to render to a turned off video subsystem. When there is no hdmi connection, besides getting some flip errors, no other strange or harmful thing happens.

But, when HDMI is plugged in, there is an extra thing causing trouble... The mirroring operation that copies framebuffer to HDMI bombs gralloc. I still have to figure out if the problem is that we are turning off the screen (something that was not implemented in the original hwc), our interrupt emulation, or just the something that was changed by Google at the framework level.

I think it can be fixed, though. The attached hwc simply rejects calls when the screen is turned off (that is the difference to the previous hwc... This provents the crashes, but causes other issues... One of them is polluting logcat with hwc errors... But, at least, no more crashes... Really would appreciate testing of this hwc with and without hdmi plugged in...

Edit2: the new hwc seems to be working pretty well, at least, it does not crash gralloc when the tablet suspends and HDMI is plugged in.. I am testing it right now... Prper HDMI output, proper video decoding, no crashes and tablet continues resuming from deep sleep without issues.. If today tablet kees waking without issues, i think we could integrate it... :) Edited by ejtagle
2

Share this post


Link to post
Share on other sites

Posted · Report post

ejtagle,

Sorry, I should get around to testing this soon. I am mid-move as I just got a new job. Thanks for the work and I'm looking forward to testing it!

fosser2
1

Share this post


Link to post
Share on other sites

Posted · Report post

[quote name='fosser2' timestamp='1362592807' post='2098830']
ejtagle,

Sorry, I should get around to testing this soon. I am mid-move as I just got a new job. Thanks for the work and I'm looking forward to testing it!

fosser2
[/quote]

No problems... I am testing it myself, but i thought it could also solve the problems you have with your port .. ;)
1

Share this post


Link to post
Share on other sites

Posted · Report post

[quote name='ejtagle' timestamp='1362594695' post='2098850']
No problems... I am testing it myself, but i thought it could also solve the problems you have with your port .. ;)
[/quote]

Well from my tests the "crash" seems to have been cured. Great job with that! I'm not sure if all the i2c issues are lib related or kernel related, my guess is the latter. I guess I'll have to mess w/ my i2c even more... I was able to get display and it slept fine though as you can see from the logs.

ADB: http://pastebin.com/deXcMUA6
SERIAL: http://pastebin.com/ZWNEM4k5
1

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

Scanno,

Just wondering if you have built CM10.1 recently, and if so has your system ui crashed? It seems like CM pushed something new that has broken Xoom and similar tegra2 tablets.

fosser2

EDIT: nvm I got the issue fixed. You will have to patch your CM10.1 build if you did not already do so.
https://github.com/redeyedjedi/android_device_smba_common/commit/e1c3e25c2f19235c7ae8fc7da74aacdd49b739f8 Edited by fosser2
1

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

[quote name='fosser2' timestamp='1362970068' post='2100621']
Well from my tests the "crash" seems to have been cured. Great job with that! I'm not sure if all the i2c issues are lib related or kernel related, my guess is the latter. I guess I'll have to mess w/ my i2c even more... I was able to get display and it slept fine though as you can see from the logs.

ADB: [url="http://pastebin.com/deXcMUA6"]http://pastebin.com/deXcMUA6[/url]
SERIAL: [url="http://pastebin.com/ZWNEM4k5"]http://pastebin.com/ZWNEM4k5[/url]
[/quote]


What i don't like about your SERIAL log is the unbalanced enable IRQ ... That means something is pretty wrong. I don't have them. It is something related to the screen blanking. I seem to remember that it could be caused by something trying to blank the HDMI output, or perhaps you have enabled console autoblanking at the same time as android managed autoblanking... Disable console autoblanking, just let android manage it.

Also, check platform_pwm_backlight_data, specifically the .check_fb function. You MUST ONLY blank the default framebuffer, NOT the HDMI framebuffer.... As it can cause this thing related to unbalanced irqs...

Also check your earlysuspend routines for the framebuffers. You dont want to power down the hdmi panel... Edited by ejtagle
2

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

[quote name='ejtagle' timestamp='1363133640' post='2101619']
What i don't like about your SERIAL log is the unbalanced enable IRQ ... That means something is pretty wrong. I don't have them. It is something related to the screen blanking. I seem to remember that it could be caused by something trying to blank the HDMI output, or perhaps you have enabled console autoblanking at the same time as android managed autoblanking... Disable console autoblanking, just let android manage it.

Also, check platform_pwm_backlight_data, specifically the .check_fb function. You MUST ONLY blank the default framebuffer, NOT the HDMI framebuffer.... As it can cause this thing related to unbalanced irqs...

Also check your earlysuspend routines for the framebuffers. You dont want to power down the hdmi panel...
[/quote]

I'm pretty sure I am only blanking FB1 not FB2 which is hdmi. Our panel file is [url="https://github.com/fosser2/android-tegra-nv-3.1.10-rel-15r7/blob/experimental/arch/arm/mach-tegra/board-smba1002-panel.c"]here[/url]. I am hoping you can point me to the "console autoblanking." I would like to make sure I do not have that enabled. I will dig into the pwm backlight data also and report back if that fixes anything. Thanks for the help.

fosser2

EDIT: from the looks of it my ".check_fb" function is the same as yours. Edited by fosser2
1

Share this post


Link to post
Share on other sites

Posted · Report post

[quote name='fosser2' timestamp='1363131752' post='2101610']Scanno,

Just wondering if you have built CM10.1 recently, and if so has your system ui crashed? It seems like CM pushed something new that has broken Xoom and similar tegra2 tablets.

fosser2

EDIT: nvm I got the issue fixed. You will have to patch your CM10.1 build if you did not already do so.
https://github.com/redeyedjedi/android_device_smba_common/commit/e1c3e25c2f19235c7ae8fc7da74aacdd49b739f8[/quote]

I have build it and i had the same problem. I have not had time to investigate the issue. But thanks a lot for the signal and the solution.
1

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

MoDaCo is part of the MoDaCo.network, © Paul O'Brien 2002-2015. MoDaCo uses IntelliTxt technology.