yashsingh1/xdaforums huggingface dataset:
[Optimus One, P500, V Q&A, Help & Troubleshooting] rharshit:
Some things I'd like to ask/share

1. My play store isn't working. I've trimmed the ROM n installed gapps too n installed play services too. Bt when i open play store, it works fine. But i can only see spinner loading under 'My Apps' n when I install any app, it gives fc. Then i have to clear data to open it again. What to do? Is it something to do with dpi? Because I've changed the dpi.

2. How to change tiles? I can't get its settings.

3. Any other int2ext script working?

4. Screen record has a very low fps and after recording, the phone becomes unusable. Have to restart

5. I found this ROM more snappy than any other CM11. Thanks to performance controls. Its awesome!

6. Only if root worked, this would be the BEST KitKat ROM for our phone.

(I'm trying to fix it too)

This ROM can be used aa a daily driver if u don't use much apps and root isn't a big issue. Great work

:thumbup:

EDIT:

Link for root in Omni ROM:

http://xdaforums.com/showpost.php?p=50863602
[Optimus One, P500, V Q&A, Help & Troubleshooting] Dovidhalevi:
Tried again to get root:

I can, in adb shell, su --daemon.

This gets me root for this session. Link2sd will create its mount script!

Rebooted. Thought that the root could be magically persistent as someone posted on some thread somewhere (did a lot of searching! and there were two instances the last time when I used a init.d script to do this). It was not so did su --daemon. Tried to use Xposed. Chugged a while, permission denied. CWM superuser's UI does not work on cm-11, not on this either. But it did not FC!

So I adb pushed SuperSU to system (I have enough room!). It wanted to install its binary. So I rebooted into recovery and flashed that.

On reboot, the su daemon was indeed running It has an 'R' instead of an 'S' on the column before its name. SuperSU also had a process running so thought hey, OK (and it did not brick the phone this time!). Tried to run Xposed. Simply sat there. Tried to run SuperSU, said it needed its binary and could not install it. Yuk! Never did like this app. On cm-10.2, even if CWM superuser wants a new binary, its UI will work anyway. Tried to run that. FC this time.

I never did check free data space.This after several successful reboots with no alarms about it. Overlayed the SLW widget onto link2sd and ran it. Only had 20meg. Fact is I had never ran link2sd to clean up dalvik and such so tried it now. Relink all apps simply chugged along. This can take time, even if it reports nothing to do! Finally lost patience with it but could not kill link2sd with back key (My fault? Options do not take effect until setting run, even if they were checked, it seems). Have to consider the possibility that the "disappearing data space" bug may be in this ROM as well as cm-11 (which, if so, would place it in the AOSP code!). No real way to check it without working root so everything plays.

Rebooted recovery, back to cm-10.2. BTW: the su daemon here has the 'S'.
[Optimus One, P500, V Q&A, Help & Troubleshooting] Dovidhalevi:
Don't know. I only change DPI using Xposed which has not been enabled yet

I assume you mean those on the right-side pulldown. Have not found the interface either. Toggle to get that and enough of them are there.

Need root. I did get link2sd to create it mount script after su --daemon.

Never tried it. May also be DPI related?

Yeah. Since I can get link2sd mounts either by running the daemon once or placing my copy, I have all my apps available (root ones will not be very happy). I used Xposed and need one round of root for this but that, as opposed to link2sd, did not work.
[Optimus One, P500, V Q&A, Help & Troubleshooting] ibub:
I have to admit that I do not know much about how su works. But the same su file is present in /system/xbin and is listed in file_contexts. SU.apk or supersu.apk have not been included in /system/app for at least cm10.1+. :confused:
[Optimus One, P500, V Q&A, Help & Troubleshooting] xu3sno:
Is that su in /system/xbin is binary command to get root access on system file? You must run this command in terminal. However, Terminal.apk only can be launched if SU.apk or Superuser.apk present in /system/app.

So, in my opinion SU or Superuser is needed to run rooted apps (such as TB, Link2SD). Maybe Busybox is required too?
[Optimus One, P500, V Q&A, Help & Troubleshooting] Dovidhalevi:
System/xbin/su is the binary. One included on the ROM is tiny, barebones (no root). I replaced it with one from cm-11. When it is working right, I believe this gives you the dialog: Allow-Deny, Now-10min-always and such. It also has a daemon mode which services root access. I have not gotten the dialog on the Omni after manually starting the daemon.

That daemon needs be started early-on. Even an init.d script may not be good enough (Omni has real init.d capability as opposed to cm-11!). There is a "persistant-root" item in cm-11's build.prop. Maybe this will work here too the with cm-11 binary?

The apk is a user installable app (or gets placed on system by flashing zip). This gives access to the application-by-application permissions granted or denied in the above dialog, enabling changing them. SuperSU offers the most alternatives but is the most ticklish. CWM superuser is simpler, less finicky but seems not to work on 4.4.*. This is part of the problem. On cm-11, I have root, have the above dialog, superuser does not FC but no UI. On the Omni, since root was achieve manually after-the-boot, more problematic.

There are other apks around, superuser-elite, paid versions, etc. They are not exclusive--I had three of them around until I removed them and kept CWM. Any one of them good on cm-11? Should!!! work here too, he-he. The apk is not necessary to service root (i.e. mine is link2sd-symlinked and before link2sd gets its root, no mount script so no app seen).
[Optimus One, P500, V Q&A, Help & Troubleshooting] Dovidhalevi:
Busybox is there, we do not have gnutls like normal distros--most everything goes through included busybox.

Terminal will work without the apk on /system/app. Cannot judge from the Omni because of no or incorrect root
[Optimus One, P500, V Q&A, Help & Troubleshooting] ibub:
I just learned a new set of tricks. :)

app_6@android:/ $ su -h

Usage: su [options] [--] [-] [LOGIN] [--] [args...]

Options:

-c, --command COMMAND pass COMMAND to the invoked shell

-h, --help display this help message and exit

-, -l, --login pretend the shell to be a login shell

-m, -p,

--preserve-environment do not change environment variables

-s, --shell SHELL use SHELL instead of the default /system/bin/sh

-v, --version display version number and exit

-V display version code and exit,

this is used almost exclusively by Superuser.apk

app_6@android:/ $
[Optimus One, P500, V Q&A, Help & Troubleshooting] Dovidhalevi:
Yes, this simply a root version of sh. The one on this ROM probably will not allow anything.

The one from cm-11 will check permissions, give the dialog to ask if root working correctly.
[Optimus One, P500, V Q&A, Help & Troubleshooting] xu3sno:
Latest build omni-4.4.2-20140227 is up, triggered by androidmeda :good:

http://jenkins.androidarmv6.org/job/omni/4/

Download here:

http://jenkins.androidarmv6.org/job/omni/4/artifact/archive/omni-4.4.2-20140227-p500-NIGHTLY.zip

Will try is that SU or Superuser included :)

EDIT:

Just flashed it with clean install.

1. System reboot took under 3 minutes :good:

2. su binary exist at /system/xbin but not link to busybox binary which is present also at /system/xbin.

3. Installed Terminal.apk, it works but denied to run su command line :(

4. Installed Root Explorer.apk, works fine but failed to access root, such to change permission R/W of /system folder.

5. Referring to 3 and 4, apps need root access failed to work.

6. Tried to install SuperSU flashable zip, it replaced su binary from stock and it caused apps which is need root access (in my case gooim manager, root explorer, and Link2SD) not responded and apps're getting hang :(

7. Installed Superuser, launched it, works but need su binary.

Do we need latest SuperSU or Superuser, hence su binary is compatible with Android 4.4.2 ?. The installed one is for Android 2 and 3.
[Optimus One, P500, V Q&A, Help & Troubleshooting] Dovidhalevi:
Do not know what has changed. There have been kernel merges, etc.

The /system/xbin/su included with this ROM is for no-root access allowed. A blocker.

I placed the su from a cm-11 ROM. This can run its daemon and get root access. Works for link2sd but nothing else (i.e. Xposed), apparently. According to some googled posts, that daemon must be started very early on (as I stated before). I had it in an init.d script. Started but had same negative results. May try the persist.sys.root_access=1 flag in build.prop. Maybe the internally buried code in boot.img will start the daemon as requested here (if it was not removed). There is no explicit script in the cm-11 ROMs to start that daemon.
[Optimus One, P500, V Q&A, Help & Troubleshooting] rharshit:
i have got an idea. But where is the source?

is this the source?

If yes, then where is settings?

EDIT:

Ok got it. Editing
[Optimus One, P500, V Q&A, Help & Troubleshooting] xu3sno:
Okay. Waiting for edited omni ROM (SuperSU included ?), as you did with cm-10.1.5-KITKAT-Update_3 :good:

Wish you luck :)
[Optimus One, P500, V Q&A, Help & Troubleshooting] Dovidhalevi:
Great. SuperSU itself is problematic but will suffer with it if it works. Would prefer generic like other ROMs.

Anyway, as in my OP, I would be looking for a dev to take this thread over as a dev thread (or open one).
[Optimus One, P500, V Q&A, Help & Troubleshooting] sumansur2008:
Another OMNI build

Another Omni build is released @ Jenkins, triggered by Androidmeda.Can d'load it from : http://jenkins.androidarmv6.org/view/All/job/omni-experimental/12/
[Optimus One, P500, V Q&A, Help & Troubleshooting] Dovidhalevi:
Labeled for commits about boot animation.

Anyway, downloading.
[Optimus One, P500, V Q&A, Help & Troubleshooting] xu3sno:
I prefer waiting for nightly build or one being prepared by rhars*** :)
[Optimus One, P500, V Q&A, Help & Troubleshooting] Dovidhalevi:
OK, more adventures:

I tried the "experimental" just to see what it looked like. New boot animation, a bit much, hoaky, flashes back and forth to white rectangle (why bother -- maybe there will be some progress report in it some day, who knows?). The only one of these winky animations I really liked was the 2.51 Paranoid which was cute and not overdone. Previous one was nothing to talk about either.

Anyway, came up just fine and not at all too slowly.

Once I had adb, I did all my surgeries: Mainly

1. KK link2sd script to /etc/init.d. I do not have to as I link2sd can get root after the su daemon is started.

2. Placed a script to start the daemon (lowest number prefix) in /etc/init.d.

Rebooted.

Everything is up, I have all my apps. And I have root (sort of) ... using /system/xbin/su from cm-11 -- ps | grep su shows two daemon instances and umteen others. There should be one and one, I believe. But ... I do have root.

Apps like sdmaid, titanium, all can get root ... except Xposed! Permission denied even if I set superuser to always allow. And yes, (CWM) superuser even comes up with its UI (after canceling the habituary choice to upgrade the binary). All the apps are there ... except Xposed,.no way to add it (SuperSU does have such an choice, I believe but might not get past the upgrade binary dialog).

Usual Kitkat problem -- Inactive home screen comes up first, then the lock screen is OK.

Screen timeout is active much sooner than cm-11. Background processes make it, I believe faster the in cm-11.

Internal storage is low, lower after reboot and link2sd finds nothing to clean up. However, storage creeps back up, slowly but surely. Did not get back up to the 90+ meg I have consistently on cm-10.2 but quite possibly might have gotten there with enough patience. Did not try another reboot to see how that effected this process, but there may indeed be a problem in AOSP code for our device causing the problem with reducing internal storage.
[Optimus One, P500, V Q&A, Help & Troubleshooting] rharshit:
I don't know how much time will it take. I'm getting unusual errors.

When i built it without ant edits, it worked fine. But after editing Settings, it gave me PerformanceControl and OmniGear errors based on Fremework. So deleted the whole thing and recompiling. If i still get the same error, I'll try removing PerformanceControl and OmniGear and try again.
[Optimus One, P500, V Q&A, Help & Troubleshooting] xu3sno:
Take your time :). I do believe you'll get success eventually as you did with cm-10.1.5-KitKat_Update3 :good:
[Optimus One, P500, V Q&A, Help & Troubleshooting] Dovidhalevi:
Please try this in cm-11.

The cm-10.2 version has a --daemon command which is what I used to test the cm-11 version I pasted on the ROM. The multiple instances I get may indicate that it is not running as a daemon. SuperSU's version has a different syntax, i.e. --auto-daemon or such, I believe.

Might not explain why Xposed does no get permission but might explain why the dialog does not come up for this. Maybe :)
[Optimus One, P500, V Q&A, Help & Troubleshooting] ibub:
I may find time to do that tomorrow. But I need to reconfigure adb in windows and in Linux (long story). :rolleyes:
[Optimus One, P500, V Q&A, Help & Troubleshooting] xu3sno:
Wish you luck and welcome to Linux. :good:
[Optimus One, P500, V Q&A, Help & Troubleshooting] xu3sno:
Autotest 20140305

http://jenkins.androidarmv6.org/view/Omnirom/job/omni-submission-test/103/

Trigerred by Gerrit: http://review.androidarmv6.org/#/c/6792/

Gerrit_change_subject : OpenDelta: Add support for Jenkins OTA

Download:

http://jenkins.androidarmv6.org/vie...archive/omni-4.4.2-20140305-p500-AUTOTEST.zip

Size: 119.08 MB

Worth to try? :). But I think merged SuperSU or Superuser into omni ROM is the most expecting one :)
[Optimus One, P500, V Q&A, Help & Troubleshooting] rharshit:
Root

Finally able to get ROOT! :victory: :highfive:

Uploading the ROM.

The only problem is that it take time for getting root permissions.

EDIT:

Link:

http://xdaforums.com/showpost.php?p=50863602
[Optimus One, P500, V Q&A, Help & Troubleshooting] Dovidhalevi:
A hearty congrats!!

I "had" root but no dialog so really looking forward to this one. It seems that 4.4.2, from AOSP, takes time for background services and processes to fully start up. This ROM may be better than cm-11 at this but the problem is there. So ouir favorite root daemon is one of these. So is getting the dialog to enable adb. And others. Biggest problem with these ROMs is the internal space problem which could ultimately keep me on cm-10.2.

Note that the "source tree" for omniarmv6 is very unstable (that is, numerous merges, not bugs!). So periodic syncing of this ROM version will be needed and ongoing. Question is whether root should be merged on the main git (omni is technically NOT rooted by default!) or would this be a fork. Can't argue with success :) but cannot simply walk away from it either :D ...
[Optimus One, P500, V Q&A, Help & Troubleshooting] xu3sno:
Great. Congrats. What's I said, finally you got it :good: :cool: :beer:

Link please. Thanks
[Optimus One, P500, V Q&A, Help & Troubleshooting] Dovidhalevi:
Everyone is awaiting that link!

While we are forking around :):

I have stated I am getting excellent battery life with cm-10.2 (note: using 2x or ds battersaver and wifi hotspot app such as whiz, Y5). After recent experiment with omni where I actually exercised settings (nothing gets saved until actually using settings) and recovering cm-10.2, I noticed reversion to "previous" battery life, akin to what I got on cm-11 trials. Why?

I am running an older cm-10.2 build with Sweetnsour's kernel (not recommened on more recent builds because now out-of-date). He has an added governer smartassh3. I found out the difference in battery life using this vs. smartassv2 can be 25%. Nothing to laugh at. (Note that results apply to how I use the phone, no gaming, lighter data/wifi usage, and that they might or might not carry over to 4.4.2 based ROMs.)

So ... it might be a good idea to include this governer in the kernel (get SnS's source and .config options) since once the ROM is up and running, everyone is going to post the usual complaints about its battery life and this might very well help!
[Optimus One, P500, V Q&A, Help & Troubleshooting] rharshit:
Here's the link:

http://xdaforums.com/showthread.php?p=50863573

Sorry for the delay. It took me some time to make a flashable zip
[Optimus One, P500, V Q&A, Help & Troubleshooting] xu3sno:
Many thanks. :good: Will download it asap. :)
[Optimus One, P500, V Q&A, Help & Troubleshooting] Dovidhalevi:
OK!

So, in the end, this is not a modified ROM so ignore everything about forking vs merging.

This is very very similar to a normal superuser or superSU zip flash-install. So why did those not work (I tried them)?
[Optimus One, P500, V Q&A, Help & Troubleshooting] Dovidhalevi:
Omni up and running!! It took ages, I mean ten minutes and freezes and what not until Xposed go its root dialog but ... going! Encouraging sign -- I think I have the internal storage free that I am supposed to have. Restoring my widgets and on the move.

Does have similar slow start with disabled home screen preceding lock screen as cm-11. This is the case after link2sd mount scripts so this might be a hint for fixing this. Screen dimming is also delayed (battery drain) but not as long as in cm-11.

So I will use omni for a bit, see how I like it. Smartassh3 would be nice, as I said.
[Optimus One, P500, V Q&A, Help & Troubleshooting] kprsnt:
you guys are too much talking about root..

but i got root on first omni build

u need to flash supersu

which was released by chainfire

and already mentioned in omnirom site and i posted it tooo

about ADB

its disabled in omni code

i already mentioned about this

if u unpack boot.img

in default.prop

ro.adb.secure=1

if u delete that code or 1 to 0

then

adb is working
[Optimus One, P500, V Q&A, Help & Troubleshooting] Dovidhalevi:
True, but it did not work for everyone. The zip offered looks most like chainfire's, actually. But it worked first try. Maybe because it does some garbage collection first and assures room on system for the surgery.

I actually had operational root with just an init.d.script to start the daemon using the cm-11 su. Everything worked but Xposed and this is a problem with the superSU method as well, it seems.

Adb is working. When connecting, one gets a dialog with some key for the computer and option to grant or always grant. Once granted, works 100%. As I found out, better not to check always because without the dialog, one might not get back in, possible bug.

Problem with this method is that be there a mishap and one cannot get the dialog, its time to take the battery out. The level of security gained by this paradigm is trivial, since even an unauthorized meddler can simply answer "yes." I should not need to unpack boot.img to use a ROM.
[Optimus One, P500, V Q&A, Help & Troubleshooting] Dovidhalevi:
So far, so good with Omni. I believe that battery life will not be up to what I had with cm-10.2 and smartassH3. But if it be almost as good, it is no slouch either.

In response to another post: How to edit the quick-setting panel? Tap the pencil icon and available icons will be shown. Tap the ones one wants, they will enlarge. Tap enlarged ones, will shrink back, to remove. Conspicuous by its absense is a sound on/off/vibration control. Maybe this is elsewhere. Goodies here are toggling auto-rotation, quite times and immersive mode. There is a volume icon as well.

Only repeated "bug," "clock as stopped."
[Optimus One, P500, V Q&A, Help & Troubleshooting] Dovidhalevi:
News Flash [SIC]:

New onmi nightly at http://jenkins.androidarmv6.org/job/omni-ota/1/artifact/archive/omni-4.4.2-20140306-p500-NIGHTLY.zip

These are called OTA project builds and will be upgraded incementally in the future. Says that a new TWRP recovery required for flashing these! Link is http://jenkins.androidarmv6.org/vie...experimental/15/artifact/archive/recovery.img

Dev says do NOT use other Jenkins builds (after going over to this?).

A lot of questions here. Yes, I like the idea of incremental upgrading, but our device is not a nexus:

1. Must trim the ROMs to fit them. How might that affect incremental upgrades?

2. Flashing whatever tiny-minimal gapps. Same question?

3. Flashing one or other version of superSU for root. Same question?

4. SuperSU can make a backup-script to preserve itself over future flashes. Same question again!?

I have never used TWRP but I guess it is OK. I believe that the questions need be answered before going over to the new build. If this be the only real change, it can certainly wait. Anyone with real information, please come into this!

There are/were utilities around to produce "upgrade.zip" between ROM versions and this is supported by CWM. Omni uses a new tool, OpenDelta. There have been commits about this last few days.
[Optimus One, P500, V Q&A, Help & Troubleshooting] kprsnt:
Incremental means we have to download whole rom again........??

Previously before this build

i got one update which was earlier build on jenkins OTA by hephappy

it downloaded whole rom

then i saw a new build in jenkins

then I stopped that one

after completion of this build

I checked for updates

I didnt got d update

because previous one server is jenkins.androidarmv6

but now hephappy changed to dl.androidarmv6

so i have to wait and see

and answers for ur questions

1. no need to trim

flash it delete useless apps using root explorer if u dont want

2. flashing of gapps is not necessary

I had flashed the gapps on cm 11 approx. 1 month ago

then i flashed every new rom on cm11

my playstore was working perfectly and contacts and other r in sync with google

I never flashed Gapps on cm11

3. old supersu works

no need to flash new one

i dunno about others

for me old one still working

4. i dunno about this

These are my observations

so may b this might not work for u

and i always flashed new roms

by wiping just cache
[Optimus One, P500, V Q&A, Help & Troubleshooting] Dovidhalevi:
The point is ... NO. A much smaller file with only differences. Eventually, OTA!

IF this be a binary or image system (I believe the older CWM was), then edits, customizations to ROM might be very very problematic. If it be this existing file is replaced this way ..., then should be OK. I know nothing about OpenDelta.

Do need to trim. Otherwise will never "see" root explorer.

I never wiped anything, never flashed any gapps, after the first cm9 install. After that, just flashed over and everything played. That was cm9.

Cm-10 seemed to always need cleared dalvik cache and fresh gapps. Actually, just some frameworks and phonesky.apk. Everything else I long installed as user apps which persist if I do not do full wipes!

Omni's install script formats system so the micro-gapps I had there and the superSU will be gone. If superSU's backup script restores this, fine, but over previous Omni builds, need to reflash the micro-gapps (everything else kept in user-space).

Supposed to! WIll it survive the new scheme?

Love to be able to do it this way once again.