yashsingh1/xdaforums huggingface dataset:
[Optimus One, P500 Android Development] rharshit:
Beta 8 teaser :P

It's a bit buggy at the moment and theming isn't fully done yet.

It may take up some time
[Optimus One, P500 Android Development] xu3sno:
Android L Theme on cm-11-20140719-NIGHTLY (KTU84Q)

Navigation bar doesn't work :(
[Optimus One, P500 Android Development] rharshit:
There isn't any drawable for mdpi and hdpi in the theme. Only xhdpi and xxhdpi. So I took it from SDK and converted others. It shouldn't be an issue in omega :D
[Optimus One, P500 Android Development] xu3sno:
Did you successfully make dalvik.vmdexopt-data-only=0 script works on Omega? IMHO, as I posted before, the only disadvantage Omega is, that script doesn't work :(. Hence, only limited user apps can be installed in /data and linked to sdext2. Sorry, it's just my personal opinion :). Once it's fixed, Omega will be my primary daily driver :goods: Currently, I'm using cm-11-20140719-NIGHTLY.

What's I really like is the way Sprit FM (Nov16) works out of the box on Omega, no BT is required :cool:, while cm-11, even the latest 4.4.4_r2 (KTU84Q) failed. Thanks for your great jobs, rhar**** :good:
[Optimus One, P500 Android Development] Dovidhalevi:
Beta-7 has been my daily driver since ....

I can live without dalvik.vmdexopt-data-only=0, have enough space, but flashing new ROM remains an unholy pain in the ... because even if I remove a few apps so thing comes up on first boot, 2nd boot will again redo all dexes and will run out of space (why?). Several repeats has successfully recovered but still ... If data-only=0 will solve this, I'll greatfully take it!

Other bugs:

Split screen unstable (FCed in 7.1?), causes numerous failures if one and only foreground app gets launched in split screen.

Split screen launch from omniswitch?
[Optimus One, P500 Android Development] am486:
Just made a clean install of beta 7.1, but the phone didn't boot up. After the LG sign the screen remains only black. I left the phone for 15 min and nothing happend. Also a second install didn't change anything. I'm switching back to CM11.
[Optimus One, P500 Android Development] xu3sno:
Android L Theme on Beta-7.1

Navigation bar with L soft key icons works just fine :cool: , while it failed on cm-11 (KTU84P, KTU84Q) :(

Now, Split View's working as it should be, no FC. :good:

30dalvik2cache script failed, hence /data partition has limited free space, since system@*.dex still occupies /data/dalvik-cache.
[Optimus One, P500 Android Development] Dovidhalevi:
Cool. What did you install?
[Optimus One, P500 Android Development] Notonlyeyes:
What? Why?
[Optimus One, P500 Android Development] xu3sno:
Android L Theme from: http://xdaforums.com/xposed/modules/xposed-android-l-theme-t2803003

It's a module, so need Xposed.

---------- Post added at 06:08 PM ---------- Previous post was at 06:05 PM ----------

Just installed Android L Theme as a module in Xposed. Don't know why it doesn't work on cm-11 as yours.

Tell me what you did. TIA
[Optimus One, P500 Android Development] Notonlyeyes:
- build.prop > qemu.hw.mainkeys=0

- installed theme https://play.google.com/store/apps/details?id=com.koulis.theme.l_ready.mdark
[Optimus One, P500 Android Development] xu3sno:
I see. You grabbed it from Playstore with 15meg in size, while the modules just 6MB. Thanks anyway.
[Optimus One, P500 Android Development] rharshit:
Can anyone tell me why builds for cooper (Galaxy Ace) are smaller? Same apps, smaller in size. I want that in p500 too
[Optimus One, P500 Android Development] Dovidhalevi:
Might give it a try, but this is the type of Xposed module that I generally try to avoid. Had problems with these in the past.

This module itself corrected the splitscreen FCs? The splitscreen in beta-7 did not FC but is certainly less than stable. Could the whole thing be a resource problem? Anyway, presents a hint for fixing it.
[Optimus One, P500 Android Development] rharshit:
per-Beta 8

So pre-Beta 8 version is rolling out. Its not exactly the finalized Beta 8. Its just a preview of what the beta 8 is going to look like.

NOTE: There are layout bugs which will be rectified soo. However, this can be used as the daily driver too.

Changelog:

Android L makeover

Android L type Settings, StatusBar, Quick Settings, etc.

A few layout fixes
[Optimus One, P500 Android Development] Dovidhalevi:
Oooooooh!

Maybe try this or wait for Beta-8 "proper."

New-recents (from aosppa)?

Primary question: Which recovery? Does this need one of those new ones, exchanged /system and /data and all that rot? Or can I flash it with the same recovery as Beta-7 (hope-hope-...)?

Any news on dexopt-data-only=0? (As I said, I can live without this but might make getting these things up and running more than a bit easier).

BTW, the DocumentsUI also installs as a user app. Not all that large, but... This has also found its way in cm-11. What I do not like about it is the never-ending but long obsolete list of "recents." Ought to check for existence while stuffing the list, huh? Trimmed about 15meg off the zip, more than most folks would or need to trim.
[Optimus One, P500 Android Development] rharshit:
Can't get AOSPA's source for that release so no aospa recents.

This works with the normal recovery, as of now.

Didn't get any success on dexoptd

-data-only. Still working on it.

DocumentsUI n stuff like that will be moved in final release.

As I have said before, its a per-release. Not all drawables are perfect. Switch and stuff needs a makeover. Its usable though.

Please give me suggestions for it
[Optimus One, P500 Android Development] xdema:
i flashed this with mukulsoni's CWMod-6.4.0.6-Jan16 recovery :)
[Optimus One, P500 Android Development] rharshit:
It will work
[Optimus One, P500 Android Development] xdema:
:D sorry i did a mistake, was not a present verb in my last post, "i've flashed"
[Optimus One, P500 Android Development] xu3sno:
Well, actually expected to be 4.4.4_r2, but KTU48P

I flashed with TWRP2.7.0.0. 20140311 over Beta7.1 without wipe and it worked just fine:good:

IMHO, this is one of the disadvantage of OMNI. Once you fixed it, it will be the best ROM. Wish you luck :)

Replaced with RootExplorer :cool:

Look like L and using Material Design :cool:, Split View, much like it :cool: As on previous version, Spirit FM works out of the box! No need BT. :cool: However, battery drain faster than Beta7.1.

Occasionally, system hang and soft keys in navbar running not smoothly, a bit laggy :(

Anyway, thanks for your great jobs, bro.:highfive:

SuperSU may be included.

Dark not only light theme option, for Settings.

Plug and play, USB mass storage. No need CLI :)
[Optimus One, P500 Android Development] rharshit:
I think I have a lot of work to do now :P
[Optimus One, P500 Android Development] xu3sno:
I think I have a lot of work to do now :P[/QUOTE]

Haaahaaa. :D My apology.:) Have no intention overburden you, bro. :crying:
[Optimus One, P500 Android Development] rharshit:
Haaahaaa. :D My apology.:) Have no intention overburden you, bro. :crying:[/QUOTE]

Oh come on! There's nothing to apologise for.

In fact, I should thank you
[Optimus One, P500 Android Development] Dovidhalevi:
Pre-beta-8 up and running.

Removed some apps for a little "headroom," backed up ...

Attempt 1: Wiped dalvik and flashed over beta-7 (note: I remove the format /system for updater script). Came up fine with low storage warning and its usual consequences. Unfortunately, screen went out during link2sd's operation, reboot landed in boot-loop

After a valient attempt to get into recovery, attempt 2:

Recovered beta-7, simply flashed over. Came up fine with 18meg of storage which is plenty for near-normal operation. Link2sd relink dalvik cache recovered all the storage, clean reboot in just one try! Best I have done in ages.

Nice piece of work indeed. Main difference is the light-style instead of dark-style for notifications, setup, etc. I think many folks would prefer the option here. Most "material" interface needs wait for sources for framework implementing this. Have not had it up long enough to compare battery life with beta-7, but aside from dwelling on light-background screens, see little reason it should not be as good.

Will run with this and see ...
[Optimus One, P500 Android Development] chalo99:
Hey guys, a lot of time I don't check this project, one of my favorite. Just a question, which are the current bugs? I mean bluetooth, wifi, wifi theter, mobile hotspot, gps, etc. I don't think there are too much, but i want to know. I'm thinking about changing to this ad my daily rom in the next update maybe. Keep working on it, you are really doing magic, as well as other p500 devs. Thanks from now.
[Optimus One, P500 Android Development] rharshit:
Well, currently it is having the KitKat bugs for our phone like Bluetooth (in 4.4.4) WiFi tether once turned on, need to restart the phone to use WiFi. And battery drain.

It has the ARMv6 bugs too like gesture typing, Google Now voice, photosphere, etc.

And in preBeta 8, there are layout bugs, like switch and scrubber progress are larger than that required in mdpi.

So if you want to use it as a daily driver, either wait for Beta8 or use Beta7/7.1
[Optimus One, P500 Android Development] rharshit:
Guys, I got this weird problem today. Don't know why but its draining the battery like hell. I don't know if its the problem with my phone or ROM.

People using preBeta 8, please report!

EDIT: (pre)Beta 8 is fine. It doesn't have any dangerous battery issues
[Optimus One, P500 Android Development] Dovidhalevi:
Using pre-beta8 several days now, no problems, battery is fine.

So far.

Note: One must use something like 2battery, dsbatterysaver, or leandroid to schedule the data and WIFI usage. Keep them off while screen is off except a bit every time period. I also have tasker turn off the GPS but this might not be significant.
[Optimus One, P500 Android Development] rharshit:
Thanks for your report.

It was a kernel problem which arouse due the mods I made for extra overclocking. Well, it was a perfect fail :P

Won't ever try it again :P
[Optimus One, P500 Android Development] Dovidhalevi:
Overclocking is ... overrated :)

Run up to 691mhz, may 729mhz. No higher, at least in the summer. Phone will usually play at 787mhz, but I had it come out of my pocket smoked (screen messed up, frozen) one warm summer day. Luckily was fine after a reboot.

Playing with kernels, get together with sweetnsour. Maybe implement the smartassH3 governer and zen io which worked great in 4.2. But the current included kernel does the job.
[Optimus One, P500 Android Development] rharshit:
I have a major problem.

The HDD I used for compiling is dead. I revived it somehow but got a lot of bad sectors.

I don't know if I'll be able to recovery the data or not. As it is the only place where I have the source. Even the backup is in the same drive
[Optimus One, P500 Android Development] Dovidhalevi:
Just lost one as well. Actually, only one partition/filesystem was dead. The others are fine, so may still use the disk. Meanwhile, did a new 64-bit Debian installation on a new disk, a lot of work, pieces still "missing."

Is the backup on a different partition? Maybe it is still OK.

Meanwhile, read whatever is readable to something else.

Do you keep sources on a fork on git?

Does it seem that those older, smaller IDE clunkers go on forever while these huge new SATA's die very quickly? The Caviar-red I just bought has a three year guarantee. The previous one, black-two years, did not last longer than that. The old 80gig IDE runs without a hitch, many more years. Because of the ridiculous partitioning done by the Debian installer, I need to use it so hopefully it will keep on going and going ...
[Optimus One, P500 Android Development] xu3sno:
Oh no. It's bad news. Regret that you didn't backup in the cloud :(

Hope you can revive it, soon.

Wish you luck :good:
[Optimus One, P500 Android Development] xu3sno:
Enable USB mass storage in OMNI ROM

Just forward [MENTION=5884745]uns8816[/MENTION] message regarding USB mass storage,

Excerpt:

/*****************

To enable USB mass storage in OMNI ROM you need to add:

persist.sys.usb.config=mass_storage

in system/build.prop save and reboot the device,

or to add persist.sys.usb.config=mass_storage in system/build.prop in

omega-preBeta8-p500.zip (or another zip) and install the ROM.

I haven't 10 posts in the forum.xda, if it's good advice, write it, please, to this topic

http://xdaforums.com/show....php?t=2687063

***********************/

So, it it helped, thanks should go to uns8816 :) and not to me!
[Optimus One, P500 Android Development] chalo99:
Hey rar****, how's your hdd? Could you save some of the data?
[Optimus One, P500 Android Development] rharshit:
Nope. I had built it from beginning. And it's almost ready for release now :)
[Optimus One, P500 Android Development] chalo99:
Great. You are a crack. I was downloading your PA final, but if you say this is comming, i will wait for it. I will bother you a little, but can you put sone speed tweaks in build.prop? I always try to do it but get bootloops and stuffs like that.
[Optimus One, P500 Android Development] xdema:
i'm testing the pureperformance mod on the HardLight os2sd, you culd try on the omega, but i see this rom very smooth and fast as is (the 7.1 on my 2nd p500, no gapps)
[Optimus One, P500 Android Development] rharshit:
Sorry, but I cant do it in beta builds. Maybe in final build. I'm not sure.

BTW, what tweaks cause you bootloops?

Which pureperformance mod are you talking about?

Thanks for the complement
[Optimus One, P500 Android Development] chalo99:
Usually I try to put speed tweaks in the build.prop manually, there are a lot of guides here in xda, and tried to put the v6 supercharger. But i'm doing something wrong. As you can see, I'm a musician, my knowledge abou this kinds of things is limited. Anyway i get fun testing and trying to do some changes.

That reminds me of asking about the usb mass storage stuff. Will you include the solution to put it in the settings? Because the last omni I tried didn't had it, so I had to move to another borrowed pc to transfer data between my phone and pc. I'm still using windows xp. And i don't have linux.
[Optimus One, P500 Android Development] rharshit:
Don't know about v6 supercharger. Maybe the dalvik thing is the problem.

And no, USB thing wouldn't be something in settings. But you can add it to build.prop for USB mass storage.

BTW, Windows xp should detect the storage without any mounting. You just need to connect your phone and it shows the contents of SD card. Yea, you need the SDK first

Just add the following at the end of build.prop

Or in terminal emulator, type
[Optimus One, P500 Android Development] chalo99:
Thanks, i will include it. And xp don't show the sd card in omni without that build.prop line. I think that I don't have the sdk (formatted my pc and installed XP again. But first, I have to put my hans in the rom.

I'm not putting you under pressure or asking for an ETA. Or maybe yes, but in a polite way.

(Just kidding)
[Optimus One, P500 Android Development] rharshit:
I won't give any exact date but expect beta8 to be out in 2-3 days
[Optimus One, P500 Android Development] xdema:
this has supercharger, crossbreeder etc..

i'm testing it on my first p500 (with Hardlight os2sd)

funny things: i forgot the 2nd p500 (with your omega 7.1) at home during my holidays,

aereo mode on, no alarm clock etc,... i thought "it should be dead, after all it's an old phone with an old battery"

when i came back home it was still alive and smile to me :D after 14 days, the battery was 45%

strangely i thought at my old nokia, when phones need only a charge after a week :o
[Optimus One, P500 Android Development] chalo99:
Intetesting, do you think it will work in omega project? Is omni based, so maybe yes.
[Optimus One, P500 Android Development] rharshit:
Beta 8

Finally Beta 8 has been done.

Update over preBeta8 only!

Changelog:

Fixed scrubber

Android L type of recents

Added DateView (partial)

Many many layout fixes
[Optimus One, P500 Android Development] Dovidhalevi:
Anybody want to try this -- do a backup first.

There is no real need for crossbreeder or its equivalents. An item can be added to a sysctl script to give one more minimum entropy without any background apps or fudges.

One can also try supercharger v6, etc, but I find its UI ridiculous.

I have an init.d script which does some tweaks, some battery saving stuff posted eons ago on XDA, but cannot vouch for it really doing any good except for the entropy. A search my yield zillions of such things on XDA, take them all with a grain of salt, always backup first!

---------- Post added at 12:25 PM ---------- Previous post was at 12:23 PM ----------

Great work, and thanks for the manageable upgrade!

Will try now. Backing up first, of course.
[Optimus One, P500 Android Development] Dovidhalevi:
Flashed the upgrade. Did not realize this would force a whole new dalvik update but it did, caught with pants (and free space) down. However, first try, got back to 90 meg, second try a few more to 112 meg and everything seemed OK.

However, it "upgrades" the Play store every reboot. It is still dutifully symlinked. This would not be the case were it really "upgraded" during optimizing apps. I thought that old phoneksy being around was the problem, got rid of it and found that I can now live with out it. Just fine with me, but it was not the offender. I still do not have all my 120meg back, but it might simply reappear, known to happen. Yes, back to 118 meg :). Only problem is starting off the a process.com wait message but I am using low_mem=false to keep my lockscreen widgets (got to be a better way--hint...) so that is my fault.

So what is best to do? I can:

1. Use it this way for a while. No real harm done, but I thought/hoped I was done with this bull... Is running really nicely!

2. Reinstall Play or restore from Titanium. Probably try this first. EDIT: worked.

3. Restore the preview, remove 4-5 large-dexed apps, reinstall the upgrade, etc., as before. Put apps back using Titanium after up and running. How I would have done it first off had I known ...

Tried the new "recents." First time, came up folded with only two recent apps, Play and Link2sd. Second time, looked more normal for just two recents around.

Sent one to splitview. Worked just fine. Tried to send the other, had that in splitview but the first app was "gone." Can always put one of them up but not both, apparently. Neither was in the foreground when I tried this, but in the past, the app sent to splitview covered half the foreground app rather than splitting it.
[Optimus One, P500 Android Development] chalo99:
Downloading, will write a feedback. From now, I'm going for a fresh install, like I always like to do. Thanks in advance rar**** for this work
[Optimus One, P500 Android Development] Dovidhalevi:
For a fresh install, install the preview as fresh. Then flash the update over it, no new wipes. The update replaces some framework and system apk's, is not a full ROM.

Running very nicely.
[Optimus One, P500 Android Development] chalo99:
Yes I did it, in the meanwhile, where is the root? Should we flash ir separately? I'm having problems with it. And what about the gapps? Because I tried to sign up with google account and said it was a problem with the conecction with the server.

I tried to download and flash the SU chainfire from it's page, and it says that it flashed well, but when reboot there is no SU installed, maybe a lack of space in the system partition, will trim the rom and repoting soon.

EDIT: Deleted Apollo apk from the ZIP to make space for SuperSU. Worked perfectly. A little detail: I make a full wipe, then flash 1-Omega prebeta8, 2-Beta8 update, 3- SuperSU. And after that, all goes well, but I don't see the "Quick setting button access" next to the HALO button in the notification drawer. But when I make a Fresh install with the full prebeta8 is OK. The only difference is that I took out the Apollo APK.

I can live witohut that button of quick setting access, but I'm trying to understand what I did wrong

The procedure to delete Apollo is unzip the ROM, delete it, and rezip (maybe this primitive metod is making something wrong).

Despite this "isues" (they are not real issues):

- Working very smooth

- No FC, no trouble at all

- Everything seems working fine, the L layout is well done, very interesting.

- Tried a little with few app, waiting for the quick settings to reapear again.

- Will give further report when I have used it for more days with more app

My advice:

Update the opening post with this information:

-Gapps (They aren't needed, but is better to say it)

-Trim the ROM to leave a little space for the root

And keep working, is a very good project and i'll stick to this ROM.

The pureperfomance mod posted above doens't flash, even with the SU. I don't know why. Maybe is a lack of space in system, because breaks the SU. And says Install Aborted Error 7.
[Optimus One, P500 Android Development] rharshit:
You made a full wipe, right? But still, did you wipe system partition specifically? Because quick settings button is a sign of low space.

That 'problem connecting with the server' is due to play services. You might not have installed it, did you?

Yea, I think I should write about gapps and SuperSU in the OP.

Well, pureperformance worked for me. But I didn't like it because it stopped the animations. Like app transition, etc.

Again, thanks for the review
[Optimus One, P500 Android Development] Dovidhalevi:
Must, must trim the ROM first. Not just Apollo. See my posts about this on the general forum and threads here about all I take out. Can get along with less taken out but need to trim. Do not need a load of space of the system, but a few mbytes is necessary.

Might have spoken too soon about that old Phonesky. Play would not upgrade anything and started crashing. Restored that and trying again. (Often enough, the problems are on Google's servers, though, but no harm in it being around.

Some users have reported that "gapps" are not necessary, but I have kept contents of GAPPSlight.apk around (I do not wipe, and remove the format of /system from the updater script. Some gapps stuff apparently replaced by the ROM). BTW, I have > 10meg on /system, but I trim to the extreme.
[Optimus One, P500 Android Development] rharshit:
So, would a new simplified gapps be a better option?
[Optimus One, P500 Android Development] Dovidhalevi:
The only things really be used from GAPPSlight are the various frameworks and services and the Phonesky--the question is, since this is many-times-over upgraded and superseded, why it seems to still be needed at all?

The first-time widget may be useful for full-wipers.

Which (if any) items here are included in the ROM? Since I neither wipe nor format /system, I have the (heavily trimmed) GAPPSlight with anything supplied in the ROM overwriting the GAPPSlight versions. Some folks have used even smaller gapps versions successfully which would indicate that only a part of this is needed.

My rule-of-thumb is: Anything operable as a user-app should be done this way, preferably from Play. ROM and gapps much smaller and Play auto-upgrades the versions of its items. Others, side-loaded, must be tracked by the user, since one rarely sees a change-item like: Apollo has been upgraded with ...
[Optimus One, P500 Android Development] rharshit:
Exactly! That's why I was planning for a gapps package with required packages in /system and others as user apps, all via a flashable zip
[Optimus One, P500 Android Development] Dovidhalevi:
Good, but be careful. Most of us (unless we wipe everything which I do not) will be short of /data space and the thing will not work. These need be installed after ROM is up and running, link2sd or whatever has stabilized and gained space and available to treat these items.

Once supersu is back up and running, go into its UI and choose the create script option. Then, on reboot from recovery, there will be an option to re-enable root. That is, unless a total wipe has been done.
[Optimus One, P500 Android Development] rharshit:
What about cache then? :P