Custom ROM creation mentoring

[elektrik]

Congratz man. Maybe your next step could be install the custom boot animation. I think I would do small steps to begin with.

Good job.

Sent from my Polaroid 701c tablet running Cm10

Thanks! I've already created the factory rom without the preinstall and root by default-the next step I'm going to take is getting the Google Play integrated...The custom boot animation's simple (simply bootanimation.zip) and I've noticed by dumping the bootfs that the custom startup graphic (currently the 'polaroid' bitmap) is easily replaceable too, but they're smaller fish to fry at this point.

[elektrik]

Thanks again 900supersport for all the help thus far. I'd like to ask another question for direction-If I wanted to make a system.img of the tablet based on what is *currently on the device* where would I go about starting to do that? I'm assuming that's possible. Would that be 'less complicated' than modifying a stock system.img and/or learning to build/compile one?

What would you suggest?

[900supersport]

Re: Custom ROM creation mentoring

You may be able to copy the system hierarchy preserving links to a new location and then copy this off the tablet. You would then need to copy this into an appropriate file image. All in all I'd say work a fresh system on your pc.

[elektrik]

You may be able to copy the system hierarchy preserving links to a new location and then copy this off the tablet. You would then need to copy this into an appropriate file image. All in all I'd say work a fresh system on your pc.

Cool. thanks :-)

[JonChance]

https://www.miniand.com/wiki/Allwinner/Unpacking+and+building+LiveSuit+images

Eletrik : The above link is a walkthrough of what you accomplished along with a few helpful hints.
The mk802 is a stick android device that uses the allwinner processor along with livesuit images. The concepts are the same as the polaroid images.

Sorry about the late addition to the thread. I didn't come across this thread until just today and read through it all.

One addition: As far as the recovery.img I might suggest that you take the recovery.img from the cwr recovery zip and replace the recovery.img from the stock rom. This will add in the cwr recovery with out having to add it later. I have done this with the stock 702/703c roms and it works rather well.

[elektrik]

https://www.miniand.com/wiki/Allwinn...iveSuit+images

Eletrik : The above link is a walkthrough of what you accomplished along with a few helpful hints.
The mk802 is a stick android device that uses the allwinner processor along with livesuit images. The concepts are the same as the polaroid images.

Sorry about the late addition to the thread. I didn't come across this thread until just today and read through it all.

One addition: As far as the recovery.img I might suggest that you take the recovery.img from the cwr recovery zip and replace the recovery.img from the stock rom. This will add in the cwr recovery with out having to add it later. I have done this with the stock 702/703c roms and it works rather well.

Haha! Great minds must think alike-this is the exact guide I found when I was working through this process-glad to know I was on the right track! As for the recovery.img, you said the 'cwr recovery'-did you mean CWM (clockwork Mod) recovery? If so, I didn' realize I could just drop it in and replace it-that would be awesome! Rooted, google play, super user AND CWM

[JonChance]

Haha! Great minds must think alike-this is the exact guide I found when I was working through this process-glad to know I was on the right track! As for the recovery.img, you said the 'cwr recovery'-did you mean CWM (clockwork Mod) recovery? If so, I didn' realize I could just drop it in and replace it-that would be awesome! Rooted, google play, super user AND CWM

yes I ment the cwm .... * grumble fat fingers* I took the CWM recovery image from the 702C recovery zip and dropped it in to a stock polaroid rom and rebuilt the image. I originally found the thread because I wanted to see if it was possible to compile a 3.2 kernel and have it work as a drop in replacement for the 3.08+ kernel that the polaroid uses. Also I wanted to recompile the 3.08 kernel using the gnuabihf toolchain instead of the generic gnuabi toolchain. the gnuabihf toolchain is a hard float toolchain and should allow for a faster kernel when it comes to floating point numbers by using the math co-processer in the armv7 neon core that the polaroid uses.

From Wikipedia :

The Advanced SIMD extension (aka NEON or "MPE" Media Processing Engine)

 is a combined 64- and 128-bit [URL="http://en.wikipedia.org/wiki/SIMD"]single instruction multiple data[/URL]  (SIMD) instruction set that provides standardised acceleration for  media and signal processing applications. NEON is included in all  Cortex-A8 devices but is optional in Cortex-A9 devices.[SUP][URL="http://en.wikipedia.org/wiki/ARM_architecture#cite_note-32"][33][/URL][/SUP] NEON can execute MP3 audio decoding on CPUs running at 10 MHz and can run the [URL="http://en.wikipedia.org/wiki/GSM"]GSM[/URL] [URL="http://en.wikipedia.org/wiki/Adaptive_multi-rate_compression"]adaptive multi-rate[/URL] (AMR) speech [URL="http://en.wikipedia.org/wiki/Codec"]codec[/URL]  at no more than 13 MHz. It features a comprehensive instruction set,  separate register files and independent execution hardware.[SUP][URL="http://en.wikipedia.org/wiki/ARM_architecture#cite_note-33"][34][/URL][/SUP]  NEON supports 8-, 16-, 32- and 64-bit integer and single-precision  (32-bit) floating-point data and SIMD operations for handling audio and  video processing as well as graphics and gaming processing. In NEON, the  SIMD supports up to 16 operations at the same time. The NEON hardware  shares the same floating-point registers as used in VFP. Devices such as  the ARM Cortex-A8 and Cortex-A9 support 128-bit vectors but will  execute with just 64 bits at a time,[SUP][URL="http://en.wikipedia.org/wiki/ARM_architecture#cite_note-cortex_a9-31"][32][/URL][/SUP] whereas newer Cortex-A15 devices can execute 128 bits at once.

[elektrik]

yes I ment the cwm .... * grumble fat fingers* I took the CWM recovery image from the 702C recovery zip and dropped it in to a stock polaroid rom and rebuilt the image. I originally found the thread because I wanted to see if it was possible to compile a 3.2 kernel and have it work as a drop in replacement for the 3.08+ kernel that the polaroid uses. Also I wanted to recompile the 3.08 kernel using the gnuabihf toolchain instead of the generic gnuabi toolchain. the gnuabihf toolchain is a hard float toolchain and should allow for a faster kernel when it comes to floating point numbers by using the math co-processer in the armv7 neon core that the polaroid uses.

From Wikipedia :

The Advanced SIMD extension (aka NEON or "MPE" Media Processing Engine)

 is a combined 64- and 128-bit [URL="http://en.wikipedia.org/wiki/SIMD"]single instruction multiple data[/URL]  (SIMD) instruction set that provides standardised acceleration for  media and signal processing applications. NEON is included in all  Cortex-A8 devices but is optional in Cortex-A9 devices.[SUP][URL="http://en.wikipedia.org/wiki/ARM_architecture#cite_note-32"][33][/URL][/SUP] NEON can execute MP3 audio decoding on CPUs running at 10 MHz and can run the [URL="http://en.wikipedia.org/wiki/GSM"]GSM[/URL] [URL="http://en.wikipedia.org/wiki/Adaptive_multi-rate_compression"]adaptive multi-rate[/URL] (AMR) speech [URL="http://en.wikipedia.org/wiki/Codec"]codec[/URL]  at no more than 13 MHz. It features a comprehensive instruction set,  separate register files and independent execution hardware.[SUP][URL="http://en.wikipedia.org/wiki/ARM_architecture#cite_note-33"][34][/URL][/SUP]  NEON supports 8-, 16-, 32- and 64-bit integer and single-precision  (32-bit) floating-point data and SIMD operations for handling audio and  video processing as well as graphics and gaming processing. In NEON, the  SIMD supports up to 16 operations at the same time. The NEON hardware  shares the same floating-point registers as used in VFP. Devices such as  the ARM Cortex-A8 and Cortex-A9 support 128-bit vectors but will  execute with just 64 bits at a time,[SUP][URL="http://en.wikipedia.org/wiki/ARM_architecture#cite_note-cortex_a9-31"][32][/URL][/SUP] whereas newer Cortex-A15 devices can execute 128 bits at once.

whoa! I'm not anywhere near compiling the kernel.....yet ;-) that's awesome about cwm though. thanks! as for compiling, maybe I could hit you up when I'm ready. I still wanna deconstruct/learn about boot.img first (& how to add init.d support)

[elektrik]

Ok, so I thought I had root (assuming I needed to change the /system and /system/app folder to RW), but apparently the properties aren't being preserved when I repack/reflash. Can Anyone clue me in why this isn't happening...?

[elektrik]

yes I ment the cwm .... * grumble fat fingers* I took the CWM recovery image from the 702C recovery zip and dropped it in to a stock polaroid rom and rebuilt the image. I originally found the thread because I wanted to see if it was possible to compile a 3.2 kernel and have it work as a drop in replacement for the 3.08+ kernel that the polaroid uses.

BTW, thatnks for the tip. I used the recovery.img from the kkromkit apk to make sure our CWM worked (not saying the 702C recovery zip didn't work, just decided to try something 'safe').

I don't suppose there's any key combo that boots straight into recovery? (or for that matter, which 'shutdown' app you would recommend to include other than the kkromkit apk to boot into it. I'm using 'quick boot' and it has an option to boot into either bootloader or recovery but it doesn't work...)?

[jtintle]

I went looking for something to boot into recovery, it looks like advanced power menu is the way to go, and I haven't found a good guide yet but I'm pretty sure the 2 files that need to be edited are:

/system/framework/framework-res.apk

/system/framework/android.policy.jar

but maybe if we compare these files from the stock ICS with the files from CM9/10 we might be able to figure it out

[elektrik]

I went looking for something to boot into recovery, it looks like advanced power menu is the way to go, and I haven't found a good guide yet but I'm pretty sure the 2 files that need to be edited are:

/system/framework/framework-res.apk

/system/framework/android.policy.jar

but maybe if we compare these files from the stock ICS with the files from CM9/10 we might be able to figure it out

Good idea-get on it

[jtintle]

I'm trying something else, but I think I found a guide that might help with the advanced power menu:

http://forum.xda-developers.com/showthread.php?t=1573032

[elektrik]

I'm trying something else, but I think I found a guide that might help with the advanced power menu:
http://forum.xda-developers.com/show....php?t=1573032

Ooh! I like the look of that too!

[JonChance]

whoa! I'm not anywhere near compiling the kernel.....yet ;-) that's awesome about cwm though. thanks! as for compiling, maybe I could hit you up when I'm ready. I still wanna deconstruct/learn about boot.img first (& how to add init.d support)

found something about implementing an init.d using the post-boot.sh script.

in your post_boot.sh script insert the following line :
/system/etc/init.d/*
The original thread is located at http://forum.xda-developers.com/show....php?t=1710980

From there you can add and remove scripts that will run at boot time.

As far as compiling a kernel is reasonably easy: most of the time it is just setting up your cross compiler that you want to have the code compile to and typing in make and let the computer do the rest. Adding in drivers and modules also very easy. the tough part is to make mods to the source and with out any new bugs lol.