[ROM][WIP]CM10.0.0-RC0-BobZ

I basically went into the lastest update (using winRAR), remove LatinIME.apk (the 24mb one), then replaced it with the 2mb one you packaged before and that does the trick in regards to saving space for gapps. Hopefully BobZ can push that in the next update. Zakman's medium jb gapps works great on this rom

EDIT: So is anyone else noticing when you get a text notification in the status bar, after the text animates out of the bar it leaves a white trail kinda like animation lag? Just wondering if it is just me

I basically went into the lastest update (using winRAR), remove LatinIME.apk (the 24mb one), then replaced it with the 2mb one you packaged before and that does the trick in regards to saving space for gapps. Hopefully BobZ can push that in the next update. Zakman's medium jb gapps works great on this rom

EDIT: So is anyone else noticing when you get a text notification in the status bar, after the text animates out of the bar it leaves a white trail kinda like animation lag? Just wondering if it is just me

For that lag, it may never be fixed. we need those openMAX drivers for ics and those they arnt releasing.

I don't know why I'm the only one with the problem of calls going straight to voicemail. I know it's not much help but I thought I'd say... I don't think it's a problem in the kernel. Just switched to Zakman's Jelly Alpha 7 and it works fine in that.

I was stating to write a long detailed explanation of the problems I was having flashing this ROM, replacing 85mb LatinIME with the 2mb LatinIME, flashing, blah blah blah, when i suddenly realized I forgot to disable signature verification in recovery. Now everything flashes with no problem and I have Gapps. If you're a ditz like me and having trouble flashing and getting Gapps, try disabling Signature Verification in recovery, then flash.

I'm switching back to my cold as ice ics rom , too many bugs for me i might switch back if u at least fix the play store and home key bugs.
It might be beacuse i dont have enough space on my sd card so ill probably get a new one. Aside from all the bugs , the rom is awsome.

On bobz release, menu works but home selects, I swapped input.so and now keys are s keys, I believe its a kernel problem

Sent from my LG-VM670 using Android Central Forums

Originally Posted by thewraith420

I haven't tried cm10 yet but if doing this gets you OS layout.. Then in /system/usr/keylayout if you swap keys 139 and 102 in the thunderc_keypad.kl and qwerty.kl you should have normal OV layout. Unless I'm way off and things are different in cm10

I don't change files...I alter source code to fix things. Example is the "boot to recovery fix", I made changes in android_frameworks_base/core/res/res/values/arrays.xml which when compiled ends up with changes in framework.

That being said, I'm not sure what I'm going to do about the lack of space. If I swap out keyboards, it become a port rather than a build...which I don't like to do. I was thinking about changing partition sizes and removing space from data and giving it to system...but I'm afraid that others or even myself may brick the phone. I'll have to do some more research on the matter.

Right now I feel ICS was the end of the line for this phone.
Ideas and suggestion are welcomed...

I don't change files...I alter source code to fix things. Example is the "boot to recovery fix", I made changes in android_frameworks_base/core/res/res/values/arrays.xml which when compiled ends up with changes in framework.

That being said, I'm not sure what I'm going to do about the lack of space. If I swap out keyboards, it become a port rather than a build...which I don't like to do. I was thinking about changing partition sizes and removing space from data and giving it to system...but I'm afraid that others or even myself may brick the phone. I'll have to do some more research on the matter.

Right now I feel ICS was the end of the line for this phone.
Ideas and suggestion are welcomed...

In scripting, could you set it to where /system is mostly installed to /sd-ext via symbolic link? Or can you not script that for recovery? People would have to have basically at least 512mb sd-ext to compensate system data and user apps, but this may be a method if possible.

Of course in the very least anyone wanting to use this rom has to have partitioned sd-ext space, but for newer roms that is practically needed anyways.

I'm guessing you've thought of this, but I believe the differences between the two keyboards is languages removed. Is it possible to just remove the languages at a source level?

I also somewhat agree with you. In my experience, ICS runs "smooth enough" on this phone most of the time. Running Jellybean at this moment just feels...sluggish, slow, etc. Not at the fault of anyone trying to get it going,I just agree that it is just too much for this device.

Of course, that is to be taken with a huge grain of salt, I am just a user and not a developer.

I also somewhat agree with you. In my experience, ICS runs "smooth enough" on this phone most of the time. Running Jellybean at this moment just feels...sluggish, slow, etc. Not at the fault of anyone trying to get it going,I just agree that it is just too much for this device.

Of course, that is to be taken with a huge grain of salt, I am just a user and not a developer.

Sent from my LG-VM670 using Tapatalk 2

JB does have it's slow down I admit that, but with egl patch its running pretty good for starting out.

Right now I feel ICS was the end of the line for this phone.
Ideas and suggestion are welcomed...

Don't say that its coming along well
Its OK if its a port everyone knows your roms are f'en amazing your doing good and so is zak and I think you are the best at this than anyone else so I say keep doing this
Ics is not the ending line...
That's quiting talk:thumbdown:

...
Right now I feel ICS was the end of the line for this phone.
Ideas and suggestion are welcomed...

I'm liking this better than ics so far.
fingers crossed that the browser is more functional in jb.
I'll bet i can find some stuff to remove from the build to reduce size a little...
now that i have a real internet connection I'll sync your source and poke at it. thanks for building and sharing.
interesting thing i never had happen before:
going from quattrimus ics to this, i wiped data, cache, and dalvik cache. the 4 apps stored on sd-ext all work with this (some old gingerbread quick settings app, sl4a, and Swype beta/Swype installer)
even Swype beta. before i always had to reinstall it after changing ROMs.
this time i only had to enable it in settings.
/edit/ i don't know about gapps, i only use them in secondary installs with multiRom so i can cherrypick apps out of /data downloaded from the market. then i don't get the battery drain and system resource reduction from the gapps on my nand install.

In scripting, could you set it to where /system is mostly installed to /sd-ext via symbolic link? Or can you not script that for recovery? People would have to have basically at least 512mb sd-ext to compensate system data and user apps, but this may be a method if possible.

I like that idea. I'm in favor of having just the essential Jellybean OS files in the phones memory and everything else being forced to sd-ext.

I'm guessing you've thought of this, but I believe the differences between the two keyboards is languages removed. Is it possible to just remove the languages at a source level?

I also somewhat agree with you. In my experience, ICS runs "smooth enough" on this phone most of the time. Running Jellybean at this moment just feels...sluggish, slow, etc. Not at the fault of anyone trying to get it going,I just agree that it is just too much for this device.

Of course, that is to be taken with a huge grain of salt, I am just a user and not a developer.

Sent from my LG-VM670 using Tapatalk 2

Your right, there's 71.9MB in dictionaries!
I'm going to compile it with only EN and ES to see how small it gets.

I don't change files...I alter source code to fix things. Example is the "boot to recovery fix", I made changes in android_frameworks_base/core/res/res/values/arrays.xml which when compiled ends up with changes in framework.

That being said, I'm not sure what I'm going to do about the lack of space. If I swap out keyboards, it become a port rather than a build...which I don't like to do. I was thinking about changing partition sizes and removing space from data and giving it to system...but I'm afraid that others or even myself may brick the phone. I'll have to do some more research on the matter.

Right now I feel ICS was the end of the line for this phone.
Ideas and suggestion are welcomed...

If there are sources for the keyboard from CM (pretty sure there are) just remove all of the images that arent mdpi and that could slim the keyboard. or see if there are sources up for the slimmed JB keyboard and throw them in there. It probably wouldnt be a good idea to change partition sizes, because of bricks, and because people already whine about it for ICS. Check wallpapers and everything and remove anything that isnt mdpi. those are my suggestions

I just want to say thanks Bob and it hit me pretty hard when I read your post about Ics being the end of the line. Then I thought hell ics is pretty damn awesome on this phone I pay 25 a month for and only paid 50 bucks brand new for the handset. I have confidence in you and this entire optimus community (the whole optimus line... p500, OS all of them). If there is someway or somehow I know you guys will be the ones to hack patch port or build it. I have the utmost respect to all of you guys as I'm sure most of this phones community does and even other phone communities do. No matter what happens just have fun

That being said, I'm not sure what I'm going to do about the lack of space. If I swap out keyboards, it become a port rather than a build...which I don't like to do. I was thinking about changing partition sizes and removing space from data and giving it to system...but I'm afraid that others or even myself may brick the phone. I'll have to do some more research on the matter.

Right now I feel ICS was the end of the line for this phone.
Ideas and suggestion are welcomed...

I have considered several options. Keep in mind this is all theory right now, as I haven't actually implemented any of it yet. I'm busy playing with the OMAP3 video processing pipeline in my Marquee right now to get the cameras working. But I've done a fair amount of thinking on the subject and I have a bit of experience under my belt.

I initially thought of changing partition sizes because it works so well on Samsung devices. But they have a single kernel for normal boot and recovery, which makes it easy. For our phones, short of rewriting the atag table (which I don't believe is possible), it would require a matching recovery and rom kernel. Users are sure to screw that up. Heck, I would probably screw it up. So I discarded this idea.

I settled on the idea of bind-mounting /system/app to /sd-ext/sysapp as the best solution. Now, /system/app doesn't have a huge amount of stuff in it. But it has enough that if it weren't there, the rest of the system should fit. It happens to contain LatinIME, most of gapps, and the crucial SwagPapers from AOKP that was tossed out in my build to make extra space. So this would provide enough space to support a full "small" language set, a full LatinIME dictionary, and other stuff as well.

The biggest problem I see with /sd-ext/sysapp is flashing stuff in recovery. Install scripts are at risk of getting rather confused. For example, flashing a "normal" gapps will delete some files under /system/app. But those files won't be in /system/app when running under recovery. Thankfully, gapps is easy to repackage and users shouldn't be flashing a whole lot of stuff to a running system anyway. Certainly not stuff that plays with /system/app (with the already noted exception of gapps). And if one were inclined, one could make an init.d script that moves anything in /system/app to /sd-ext/app before doing the bind mount. That would only fix half of the issue, and I'm not sure if that is better or worse than doing nothing.

Oh yeah... and it would also, technically, be the first setup to actually require the sdcard to boot. But that's a small price to pay for jellybeans, don'tcha think?

I don't change files...I alter source code to fix things. Example is the "boot to recovery fix", I made changes in android_frameworks_base/core/res/res/values/arrays.xml which when compiled ends up with changes in framework.

That being said, I'm not sure what I'm going to do about the lack of space. If I swap out keyboards, it become a port rather than a build...which I don't like to do. I was thinking about changing partition sizes and removing space from data and giving it to system...but I'm afraid that others or even myself may brick the phone. I'll have to do some more research on the matter.

Right now I feel ICS was the end of the line for this phone.
Ideas and suggestion are welcomed...

I, personally, would slim the large apps down as much as possible. Then I would move unimportant, but useful stuff to /cache. I dont know of many ov roms that actually use cache for anything. Kinda a waste.

Then flash my latest custom gapps. Now with partially working Google Now and Fully working google ears

This method worked for me (partially). All the Gapps i need are on there. The google now opens, but doesn't work. It just says it's initiallizing, then that it 'didn't catch that. Retry?' The voice search from the play store works from the app icon, but not the widget. Good enough for me.