Calling any PMID4311 owners

[elektrik]

I am looking at expanding my (as yet vaporware but soon to be worked upon) ROMS past my PMID 701C and PMID701I to the PMID4311 (my daughter has an 'Emerson' branded one), and would like to in the not-too-distant future consult with someone who can assist me in getting information so as to create a custom (and or modified stock) ROM for these little devices.

Like I said, this will be in the future-currently I have plenty to keep me busy with the PMID 700 series

Anyone interested?

[dolorespark]

I am looking at expanding my ROMs... to the PMID4311 ... and would like to in the not-too-distant future consult with someone who can assist me in getting information so as to create a custom (and or modified stock) ROM for these little devices. Like I said, this will be in the future-currently I have plenty to keep me busy with the PMID 700 series.

Anyone interested?

Sure - just be ready for some MAJOR challenges! I've been trying to upgrade to JB for almost a month with no success. I've even resorted to creating my own ROMs (and I'm a complete newbie to Android) but no joy I can build 'em but don't know enough to debug them (in most cases, it's 'netd' that dies).

On the bright side, I have learned quite a lot:

• the /system partition ('nandd') is only 256mb which is way too small for CM10 without pruning a whole lot of ..um.. stuff. I'd love to find a generic/stock version of JB without any of that.
• the loadable kernel modules (*.ko in lib/modules or vendor/modules) provided in the stock ROM for the 4311 and some other Polaroid models are actually debug builds. They contain the names of every variable and every source file used which bulks them up by a factor of 10. I found a copy of the standard gcc 'strip' utility which runs on Windows and handles ARM binaries. After using it, they went from over 50mb to under 6mb.
• the 'su' binary that's included in CM builds comes from Superuser and appears to be useless unless the app is up and running. Consequently, you can't do a 'dmesg' if you get stuck in a boot loop. To get around this, I've been renaming it, then copying in the version that comes with the stock ROM (and of course, 'chmod'-ing it). That version never says "no".
• etc, etc, etc, the list goes on and on...

If you're the intrepid sort, have at it. I'll be glad to help.

[dolorespark]

Eureka!

I've been trying to upgrade to JB for almost a month with no success.

I finally figured it out In JB, the mount points for the SD cards have changed but the compatibility zip's 'etc/vold.fstab' hadn't been updated. Consequently, the mount-service process crashed when it tried to mount the internal SD card and couldn't find it.

I now have a working CM10 but there are a few problems to be fixed: the tab's buttons aren't mapped correctly and the gsensor doesn't work (i.e. no rotation). Once that's done, I want to try something that may work around the limitations imposed by a 256mb system partition.

[elektrik]

I finally figured it out In JB, the mount points for the SD cards have changed but the compatibility zip's 'etc/vold.fstab' hadn't been updated. Consequently, the mount-service process crashed when it tried to mount the internal SD card and couldn't find it.

I now have a working CM10 but there are a few problems to be fixed: the tab's buttons aren't mapped correctly and the gsensor doesn't work (i.e. no rotation). Once that's done, I want to try something that may work around the limitations imposed by a 256mb system partition.

I remember a previous post (by jtintle perhaps) in the Polaroid forums here about remapping the tab buttons-you (and I) can do a quick search to find it-it's a simple matter of changing the vales in (default.prop???) a file.

[dolorespark]

I remember a previous post (by jtintle perhaps) in the Polaroid forums here about remapping the tab buttons-you (and I) can do a quick search to find it-it's a simple matter of changing the vales in (default.prop???) a file.

It was even simpler: I just copied in /system/usr/keylayout/sw_keyboard.tl from my copy of the stock ROM. I can't remember if it was in the output from dmesg or in logcat.log, but one of these identifies the file being used. The gsensor still doesn't work but I have an idea where the problem may be.

[elektrik]

It was even simpler: I just copied in /system/usr/keylayout/sw_keyboard.tl from my copy of the stock ROM. I can't remember if it was in the output from dmesg or in logcat.log, but one of these identifies the file being used. The gsensor still doesn't work but I have an idea where the problem may be.

search on here-there was a post dealing with the g-sensor too

[jtintle]

Re: Calling any PMID4311 owners

search on here-there was a post dealing with the g-sensor too

Just be sure it's the same g-sensor, the one in the 701c was a mma7660.

I think drywall just replaced the a couple of *.so and *.ko files from ICS into the CM10 build.

Tapatalked

[dolorespark]

Just be sure it's the same g-sensor, the one in the 701c was a mma7660.
I think drywall just replaced the a couple of *.so and *.ko files from ICS into the CM10 build.

Thanks, that was the ticket. I replaced /system/lib/hw/sensors.exDroid.so with a copy from the stock ROM and that fixed it.

I had already determined that the 4311 uses an mma7660 and that it was fully operational. For 4311 (and probably other similar devices), you can enter this at a command prompt and read the current value:

adb shell cat /sys/devices/virtual/input/input3/value

returns (e.g.)

x= -13 y= 8 z= -14

In this case, I was holding it in portrait mode, angled back a bit and cocked slightly to the right. If the device is asleep, you'll get all zeroes.

(BTW... if you replace 'value' with 'name', it will identify the device - in this case "mma7660".)

[bbsux]

I have both a pmid4311 and an emerson em543.

I'll help you beta test roms if you need help.

Just give me a yell.

[elektrik]

I have both a pmid4311 and an emerson em543.

I'll help you beta test roms if you need help.

Just give me a yell.

sounds good...

[bbsux]

hey guys, have you popped one of these open and checked the chipsets? The board has an unpopulated Bluetooth antenna header (the WiFi is a chip antenna so would the Bluetooth unless you moved it.)

I've heard of tablets and phones having Bluetooth capability, but it just being disabled.. So I was just wondering.

plus the WiFi antenna is in a sucky place. Its under the screen so the signal is blocked by the PCB on the bottom and the screen on the top!

it may be worth it to try to solder a laptop antenna and tape it to the back. Battery is 1400mah. I'll snap pics when I get home.

[elektrik]

Interested to know how this turns out.

[bbsux]

Some chips:

2x hynix h5tq2g83cfr

Realtek 8188ctv on its own daughterboard that is soldered on (may be able to solder 2nd antenna?)

(M) 29e32g08cbaca

Sitronix st1530-n4d

Axp209

board is held by three screws. There are numerous testpads. Including two by the usb that are marked "UBOOT"

[joshumax]

I just got a "polaroid" branded PMID4311 from Biglots and would be happy to try out the roms. (assuming it hasn't been bricked beforehand.)

[dolorespark]

I just got a "polaroid" branded PMID4311 from Biglots and would be happy to try out the roms. (assuming it hasn't been bricked beforehand.)

See http://www.freaktab.com/showthread.p...Store-and-more