• Announcements

    • Reminder - MoDaCo position on illegal content   07/30/15

      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 softwareNintendo 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 contain any illegal 3rd party software (this includes trial versions included without permission)ROMs must give full credit to the original authorISSUES If you have any issues with this policy, please contact PaulOBrien directly via PM.
    • Reminder: Selling items on the forum directly is not allowed   07/30/15

      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 / suspension / ban.

[2.6.35 kernel] Alpha: Call for testing (w/o camera)

20 posts in this topic

Posted (edited) · Report post

caf/android-msm-2.6.35 kernel builds for Acer A1 (Liquid, S100) compatible with 2.2 userspace.

Current status:

Alpha, most of the hardware pretends to work. The only known broken module is camera.

Tested only on 512Mb variant (hw_ver=6) for now.

CAUTION: This kernel is compatible with default partition layouts ONLY. If you have a kernel that overrides the partition information from atag then you can test this kernel only when you revert to the default partition layout. The filesystems will become corrupted if you run this kernel with a modified MTD layout on your device. In other words, use Malez recovery to flash the update archive.

Links:

Edited by errmsg
5

Share this post


Link to post
Share on other sites

Posted · Report post

Once again congratulations on your work, really amazing, I must admit I'm envious of your ability. I'm too ignorant to be able to base a new rom on this kernels, I hope someone more knowledgeable than me can make good use of them, maybe basing a new CM 7/9/10 around this.

1

Share this post


Link to post
Share on other sites

Posted · Report post

I'm too ignorant to be able to base a new rom on this kernels, I hope someone more knowledgeable than me can make good use of them, maybe basing a new CM 7/9/10 around this.

Well, the userspace is not really ready. Once I get the kernel to be stable enough I will start working on a compatible userspace and get Gingerbread CAF/AOSP version to run on the device. After that porting CM7 to Liquid would be much easier.

As always, no ETA.

5

Share this post


Link to post
Share on other sites

Posted · Report post

Great news, best of luck guys

0

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

3D - we need new userspace kgsl drivers (most likely from Liquid Metal)

we can use any drivers for gpu if they for andreno 200

here https://github.com/R...ree/cm10/kernel we use drivers for video and gpu from x10 with almost works of tripple buffering

Edited by RomzesRover_R
0

Share this post


Link to post
Share on other sites

Posted · Report post

we can use any drivers for gpu if they for andreno 200

here https://github.com/R...ree/cm10/kernel we use drivers for video and gpu from x10 with almost works of tripple buffering

Yes, I suppose there are two ways to get 3D working - one is to have Liquid Metal adreno 200 drivers bolted on, another one is to use Sony X10 libraries that are compatible with older 2.6.29 kgsl drivers and revert all the kgsl commit the same way I've done for 2.6.32 (before 2d/3d split - if the device has a /dev/kgsl-3d0 node then that's a newer kgsl driver).

0

Share this post


Link to post
Share on other sites

Posted · Report post

we can use any drivers for gpu if they for andreno 200

here https://github.com/R...ree/cm10/kernel we use drivers for video and gpu from x10 with almost works of tripple buffering

Yes, I suppose there are two ways to get 3D working - one is to have Liquid Metal adreno 200 drivers bolted on, another one is to use Sony X10 libraries that are compatible with older 2.6.29 kgsl drivers and revert all the kgsl commit the same way I've done for 2.6.32 (before 2d/3d split - if the device has a /dev/kgsl-3d0 node then that's a newer kgsl driver).

Why not use freedreno ones: http://freedreno.github.io/ ?

I'm just curious, why have you used 2.6.32 and now 2.6.35 kernel versions?

0

Share this post


Link to post
Share on other sites

Posted · Report post

Why not use freedreno ones: http://freedreno.github.io/ ?

For now it's just a matter of having less tasks on my plate. In case there are no other issues, switching to freedreno may be an option.

I'm just curious, why have you used 2.6.32 and now 2.6.35 kernel versions?

Acer Liquid had 2.6.29 as the only supported kernel version for ages, while FroYo was expected to be on 2.6.32.

During all these years multiple versions of 2.6.29 kernels with imported fixes/changes from newer versions appeared, but they all looked more like Frankenstein-monster types. Backporting new features/fixes from codeaurora was not an easy task.

Bringing relatively stable 2.6.32 version with clearly defined boundaries between codeaurora code and acer devices/hacks was a required condition to continue supporting the device with a newer upstream kernel. It's always easier to have smaller set of changes to maintain and I have already experienced a benefit of running a newer kernel - battery drain of 1% instead of 4-5% an hour when idle was definitely an improvement for me).

There are two versions (2.6.32 and 2.6.39) at once because the issues need to be ironed out first before moving to an unknown land of "2.6.35" for Liquid. FroYo libraries are working fine with 2.6.32 and with 2.6.35 we need a proper Gingerbread build, so that's not a drop-in replacement.

I hope this answers your question.

3

Share this post


Link to post
Share on other sites

Posted · Report post

Yes, I suppose there are two ways to get 3D working - one is to have Liquid Metal adreno 200 drivers bolted on ...

I don't know if the GPU driver is the same, but Acer liquid metal has an Adreno 205 and not an Adreno 200 ...

0

Share this post


Link to post
Share on other sites

Posted · Report post

I don't know if the GPU driver is the same, but Acer liquid metal has an Adreno 205 and not an Adreno 200 ...

As far as I know, all Adreno 2xx devices use the same driver.

Fun fact: "adreno" is actually an anagram for "radeon". Qualcomm has purchased the mobile radeon technology from ATi and named it this way.

2

Share this post


Link to post
Share on other sites

Posted · Report post

Just a quick heads-up - I got MDP composition working on FroYo with copybit from caf/gingerbread and continue to tackle the remaining issues. It looks like X10 drivers is indeed our only hope. I got Liquid MT OpenGL ES drivers to the point where they crash somewhere within the closed source binary and Nexus libraries are prelinked to 3G/1G VM split.

So now I actually run 2.6.35 on my device - my blog post but having no 3D, camera, WiFi, sensors, and top LEDs (the last one is really easy to fix but not there yet) is not much fun.

1

Share this post


Link to post
Share on other sites

Posted · Report post

Cool, hope you manage to fix all the bugs, you rock man.

0

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

Built a new version with 2.6.32 kgsl and sensors (updated the links in the first post). The only broken modules are wifi and camera, everything else pretends to be working.

Update: need to forward-port i2c recovery sequence. Either smb380 & ms-3c or isl29018 are breaking the bus so the screen stops responding and the phone appears to hang. Serial console still works but that's not really a solution. Liquid Metal has the gravity sensor/accelerometer replaced with ADXL346 and AK8975 so these are my suspects. Figuring out which one won't really help fixing this, though.

Edited by errmsg
0

Share this post


Link to post
Share on other sites

Posted · Report post

Alpha milestone reached. Updated the links in the first post.

1

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

Awesome... one question: did you test battery drain of these kernels compared to stock ones? Is it the same or is it more/less?

Edited by Master_T
1

Share this post


Link to post
Share on other sites

Posted · Report post

Alpha milestone reached. Updated the links in the first post.

I'm really interested to that project.. And i really like your approach!! Congratulations!!

I'd be happy to help so if you need something feel free to ask!

1

Share this post


Link to post
Share on other sites

Posted · Report post

Awesome... one question: did you test battery drain of these kernels compared to stock ones? Is it the same or is it more/less?

Hello, no real tests were performed for battery drain. While the kernel is working it is not yet as stable as I would like it to be, so any further optimization will be premature at this stage.

OTOH 2.6.32 builds allow me to get through 14 hours of occasional device usage (no wifi, 3G connection only), which was not that reachable with stock .29. With Wi-Fi enabled the drain is enormous on both .32 and .29.

0

Share this post


Link to post
Share on other sites

Posted · Report post

I'm really interested to that project.. And i really like your approach!! Congratulations!!

I'd be happy to help so if you need something feel free to ask!

Yay, thepasto! Hello!

For now I am concerned with Wi-Fi mmc card failure after reload, 3D lockups with .32 kgsl, being able to use 3D acceleration in GB (I guess i should use X10 kgsl sources, am I correct?) and camera module on FroYo.

Questions:

  • Sensors and camera module - was the userspace reverse-engineered or acer's libcamera keeps being used on newer ROMs?
  • Were there any known issues with acer rild not starting under GB+ - during my attempts to build a caf/GB ROM I had no luck bringing up rild even after reverting the relevant commits. It links the library but that's pretty much all it does.
  • Is there a canonical source of a CM7 for Liquid?

1

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

Tonight new kernel had crashed, I can't provide you additional info, just last_kmsg:

http://pastebin.com/NG17fMcr

BTW, top battery light doesn't blink on charging, only on full charge.

UPD:

Looks like device can fully freeze, for now I don't know conditions for this: first case I've reproduced on sleeped device, it was unable to awake; second case was with using gmail, it freezed completely, only removing battery helped

UPD2:

I'm experiencing "Error" message on the WiFi is turned on.

Kmsg: http://pastebin.com/EEQPrq4X

Logcat: http://pastebin.com/tRD6Djv7

UPD3:

Looks like the USB mass storage from the OS doesn't work. I tap "Turn on mass storage" it begins spinning and drive doesn't mount on the host PC.

Edited by zabulus
1

Share this post


Link to post
Share on other sites

Posted · Report post

Tonight new kernel had crashed, I can't provide you additional info, just last_kmsg:

http://pastebin.com/NG17fMcr

Bug #26 - camera does not work.

BTW, top battery light doesn't blink on charging, only on full charge.

Interesting, will check this.

UPD:

Looks like device can fully freeze, for now I don't know conditions for this: first case I've reproduced on sleeped device, it was unable to awake; second case was with using gmail, it freezed completely, only removing battery helped

I think that is related to 3D device - I can reproduce (bug #28 this reliably in Opera Mobile, but that's a complete lockup - the kernel no longer reacts to anything/prints anything. I will try to merge drivers from X10 instead of froyo ones, but I am afraid I am running out of time.

UPD2:

I'm experiencing "Error" message on the WiFi is turned on.

Kmsg: http://pastebin.com/EEQPrq4X

Logcat: http://pastebin.com/tRD6Djv7

MMC card interface bug (#29), not yet sure where to start.

UPD3:

Looks like the USB mass storage from the OS doesn't work. I tap "Turn on mass storage" it begins spinning and drive doesn't mount on the host PC.

Oh, this looks like a vold update is needed. Will look into this.

Re: the time is running out. I am starting to work full-time tomorrow and I believe I won't have enough time to devote to these kernels. I wish I had the serial debug cable built 2 months ago :), I would not have wasted a couple of weeks debugging the boot issues alone.

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.