Instead of startpoint I should have used the word "offset" as in size@offset see board-shuttle-nand.c in kernel for what the default values were these are then overriden by the command line.
For example in flash.cfg for system.img size=158720000 if you divide this by 1024 you get 155000 now the value in command line for size is 155008 (divide size values in flash.cfg by 1024 to give command line values).
For the offset value of system in command line is 23680 now that is calculated from the size and offset value of the boot + 512 eg 8192@14976 = 23168 + 512 = 23680, so you add the size and offset value of each partition plus add 512 to get the next offset value.
So if you make system size 200000 multiply by 1024 = 204800000 would be the size of system in flash.cfg, in command line make system 200008k@23680k(system), 32768k@224200k(cache), 4096k@228808k(staging), 261688k@233416k(userdata) (misc,recovery,boot stays the same) - everything size should total up to 513920 (513920 / 1024 = 501.875 we have 512mb).
The only size thats changed is the system.img in flash.cfg and command line which then means you have to then change the offset values in "cache, staging, userdata") (also userdata size with whats left)
Hopefully this allows you to calculate what ever values you want to use (if I have got this wrong I am sure Eduardo will explain if he has time)
Think you need to amend the size value in flash.cfg file thats part of the nvflash structure, find the one named APP and increase value which should then reduce data(UDA) automatically as this has no set size.
Second you have to amend the partition sizes of your create boot.img command line to fit your new size/structure (ie partition size and start points of each partition 2048k@6784k(misc) these entries if you get what I mean) so when you create the boot.img it fits the new structure you created when the nvflash was done.
re. bluetooth yeah they modified it check the asus/grouper(nexus7) and samsung/manta(nexus10) they added a bluetooth folder which seems to be used, they also modified all the wifi files ie. softapcontroller.cpp, wpa_supplicant8 and the libhardware_legacy/wifi files we previously amended as part of 4.1 these will probably need updating for wifi to work as well.
Just to confirm what Eduardo has said I am using the old libs and played hd youtube in browser and app both worked fine, also playing bbc iplayer in browser fullscreen with no issues in picture or sound that I have seen mentioned in tabletroms, hopefully the libs Eduardo posted will fix your roms issue if not I will post the ones I am using but I think they are probably the same.
Also seen mention of issues at 160 dpi (took a break for a couple of days so may have missed that they have now disappeared) but I have not seen issues at this dpi but its not one I use for very long (and with the portrait mode fix its like having a slightly bigger nexus7), have attached my slightly modified overlay dir for you to do a comparison - it removes the old launcher2 dirs in packages/apps and frameworks/packages/apps and adds a new launcher2/config overlay means you get full rotation at 160, also adds an extra option in frameworks/core config the I mentioned before for navigation buttons. edit - yes it looks like browser has issues at 160 playing full screen and iplayer but play fine at 120 - if you use 160 try firefox beta both iplayer and youtube hd will work in it but only full screen, small window picture quality is not good overlay_jb666.rar
Just to confirm Eduardo's thought - if you turn off hardware accel on the launcher2 app the portrait mode is displayed correctly.
The settings app also has hardware accelerated set to true which is why that and any other app that has it set to true will probably display wrong.
edit - if launcher is set to false portrait will display correctly, if you then force gpu for 2d in developer options then it returns to displaying graphics halfway down screen
edit 2 - IF you want good news on this portrait mode issue, try using the old libs/gralloc/egl (original ics libs and used currently in vegacream I think) not the ones that were tested before and probably you have also been using that caused issues in ics that seemed to work fine in jb but have been causing this issue (ie the newer ones linked to previously in derartems git).
Need to test if these libs will cause other issues but you can try them and see (although I have tried flash and youtube HD and they seemed to work as before the only things that seems slower is the redraw of screen when you rotate from landscape to portrait).
edit 3 - re. MikhailM comment no.8 on tabletroms re. skype I have tested these libs and can confirm that you get video in both directions using them something he said did not happen so maybe the libs used in alpha2 caused this issue although using the old libs again will probably remove his "special thank you" on point 3.
Also to confirm the new audio_hw works, but did you not get the loud (depends on volume setting) click/pop/static when you first get sound from speakers (only happens first time audio plays then does not happen again until you boot/reboot) (using 25jul-11am kernel sound codec/driver) ?
The pop can also be heard if you reboot tablet when it is restarting.
Also re. portrait mode I have also been looking at this, changing the aapt settings (from tvdpi to mdpi) in device.mk messing round with overlay dir and have not been able to figure a fix out yet its a strange one.
Just for info as Eduaros looking at audio_hw but if you set ctl_name = INTERNAL_SPEAKER_SWITCH intval to 1 instead of zero in the route_setting defaults struct, you will get audio output from speakers without having to plug/unplug headphones.
Does not fix the right channel only output but atleast gets audio from speakers without needing headphones and once headphones plugged in if you want to use them route switching carries on as normal between headphones/speakers.
edit - What I have noticed after doing this is you get a click/static when the speaker is first initialised when you play something for the first time via speakers, also get a click via headphones when started for the first time
Ok performed same test as last audio_hw so soundhound/skype/voice recorder and all 3 worked the same with new version.
Now onto voice search, it now no longer crashes and seems to pick up the word but does nothing else have attached a log for you to look at see mic3 it has displayed text after some time but nothing like the word I spoke (this could just be highlighting another issue with my rom as I have tried it again and it did recognize the word test but then errored out).
Also attached a mic3 which is using voice search in youtube app, this does not seem to pick up or search for anything, and attached a mic4 this is using voice for keyboard entry this picks up mic and is nearly accurate (on all three tests the one word I spoke was test keyboard entered text) log3_mic666gv.txt log4_mic666yt.txt log5_mic666key.txt
Re. mic my initial test as I was logging off (should have waited to test more before posting) was a voicesearch using new jb apk now that starts and stops with didn't catch that try speaking again where as with old audio_hw it sat at the initial screen like it was listening - attached 2 logs for this 1 is the new audio_hw and 2 is the old ver.
This may just be a voicesearch issue as I have tried the new audio_hw with soundhound and it recognised the audio well enough via mic that it reported the correct song, also using easy voice recorder (I set it at 44100) it recorded my voice although a slight background noise (humming/static). - so from these 2 tests the mic is working. log1_mic666.txt log2_mic666.txt
Quick answer I don't have time for much else just now is no it does not fix mic or youtube issues - will try to get log info later tonight.
Mic just opens then closes in a second app saying unable to hear anything where as before it would stay open, youtube was no change crashed if you let browser video play but played fine if you changed video res at start (this is on old kernel audio codec/driver).
Been testing new audio fix and as Scanno has found boot loops caused.
The only info I can give is it is a change to the alc5624 codec code that is causing the boot loop, I have booted a kernel with the new audio_hw.c and the tegra_alc5624 with an old codec and it booted (no audio but booted) also booted old audio kernel with new audio_hw for a test and still got sound via headphones.