yashsingh1/xdaforums huggingface dataset:
[Optimus One, P500 Android Development] ibub:
Installed CM-12-20150116-EXPERIMENTAL- P500.zip using TWRP-2.8.3.0-20141230-MULTI-F2FS-P500. >>>Bootloop at boot animation.

Next installed cm-12-20150117-EXPERIMENTAL- twrp2840- p500.zip (same recovery) >>>Black Screen. Next installed recovery.img from cm-12-20150117-EXPERIMENTAL- twrp2840-p500 eng build. Reboot recovery to Black Screen. Was able to access recovery via adb in Linux (Windows did not recognize device even after reinstalling drivers), and then adb reboot bootloader, and use fastboot to flash previous recovery.

;)
[Optimus One, P500 Android Development] Dovidhalevi:
This is OK. So where are all those odexes?

Probably for the best. Once set up, no longer need to jump through hoops, but no other recovery or ROMs either. I will wait.
[Optimus One, P500 Android Development] xu3sno:
in progress: Build cm_p500-eng-cm-12.0 (Jan 18, 2015 12:17:34 PM)

Surprisingly it's started by user HardLight :cool: :good:

As of posting, build has been executing for 58 min

http://jenkins.androidarmv6.org/view/Developers/job/cm-experimental/1327/

EDIT

It's successfully built! :good:

Flash it with CWM Recovery?

ROM: http://jenkins.androidarmv6.org/vie...hive/cm-12-20150118-EXPERIMENTAL-cwm-p500.zip

Can't download it due to my limited bandwidth :(
[Optimus One, P500 Android Development] HardLight:
No it's build for cwm but it has same issue as last twrp build- blank screen.

Also do not flash any eng builds their are for generating recovery.img that could fit to our recovery partition (some kernel parts are removed).

Could you post booting logcat of last userdebug build flashed with twrp 2.8.3.0 multi.
[Optimus One, P500 Android Development] xu3sno:
OT

Every time I tried to open: http://jenkins.androidarmv6.org/, it's directed to https://github.com/login?return_to=...=ffc025e35721a3ae9b33&scope=repo%2Cread%3Aorg :confused:

A description for this result is not available because of this site's robots.txt. Learn more ...

Never happened before.

No chance to try cm12-EXPERIMENTAL anymore? :(

End of OT

EDIT:

As [MENTION=4912093]ibub[/MENTION] hint, need login to Github (required sign up) in order to open Jenkins.

Thanks bro! :good:
[Optimus One, P500 Android Development] xu3sno:
Tried to install 20150120-EXPERIMENTAL-p500 userdebug:

http://jenkins.androidarmv6.org/view/Developers/job/cm-experimental/1329/

by using TWRP 2.8.3.0 OS2SD-MULTI.

Flashed successful > change data to f2fs > reboot system > blank screen :(
[Optimus One, P500 Android Development] ibub:
Just a heads up, Androidmeda has commited changes to fstab:

http://review.androidarmv6.org/#/c/7811/

I believe that any build including this commit will require converting to ext4 file systems before flashing.

Be careful out there.

;)
[Optimus One, P500 Android Development] xu3sno:
http://jenkins.androidarmv6.org

Access Denied

<user> is missing the Overall/Read permission :(

Tried to solve: http://stackoverflow.com/questions/...r-user-is-missing-the-overall-read-permission

Can't find $JENKINS_HOME ( linux ) .jenkins on my Slackware, find: `config.xml': No such file or directory
[Optimus One, P500 Android Development] ibub:
May need to sign in to gerrit using Google sign in, or open id. Have documentation link, but have not had time to read it all:

http://review.androidarmv6.org/Documentation/access-control.html
[Optimus One, P500 Android Development] xu3sno:
Signed in to gerrit > OK > jenkins > Access Denied

http://review.androidarmv6.org/#/c/7799/
[Optimus One, P500 Android Development] ibub:
The only way that I can figure to gain access would be to actually become an active participant by:

Init repo bla bla

Repo sync bla bla

Source env/setup sh

And then add gerrit to working_dir

So after two days of downloading to a 32-bit computer that won't even build cm-11, I might be able to verify that it will or will not work (I'm not downloading). Or we can wait until androidarmv6 decide that the builds are safe to post again (or whatever the reason for this), or to give us some form of access. I can't even download cm-11 RC14. :(

Edit: Other part of gaining access would be to become member of a group i.e. LGE. Group member would have access to dashboard (I believe).
[Optimus One, P500 Android Development] xu3sno:
[MENTION=4912093]ibub[/MENTION]

Thanks for the hint. Okay, better wait until the builds are safe to flash for ordinary users like me :)

You may download RC 14 through this link:

http://download.androidarmv6.org/_builds/p500/stable/
[Optimus One, P500 Android Development] ibub:
OT

Sorry guys, I guess I got a little upset at this situation.

/OT
[Optimus One, P500 Android Development] xu3sno:
OT

Read this: http://www.androidauthority.com/cyanogen-google-kirt-mcmaster-582373/

PA, OMNI will be an alternative? Time will tell! :)

End of OT
[Optimus One, P500 Android Development] Dovidhalevi:
OT?

CM seems off on its own tangent. I cannot even think of trying CM12 because if it is not my cup of tea (once it boots ...), I may well have no way back. To commit to something that does even boot yet is too problematic.

Without Xposed, PA may well be the alternative. With Xposed, might really want to stay with Omni. As said, time will tell!

End of OT?
[Optimus One, P500 Android Development] ibub:
Updated links in OP. Nothing new. Just getting organized. :)
[Optimus One, P500 Android Development] Notonlyeyes:
OT

Bootanimation CM12 in White or black ...by noe

OT
[Optimus One, P500 Android Development] ibub:
Black, I think. Like the dancing dots>Android. :)
[Optimus One, P500 Android Development] ibub:
I got onto Jenkins androidarmv6 dashboard without a log in. You may want to look at it:

http://jenkins.androidarmv6.org/
[Optimus One, P500 Android Development] xu3sno:
+1

Is that just a farewell for end-users?

Jenkins will be closed on 14 Feb 2015. For good?

As [MENTION=4912093]ibub[/MENTION] posted on mukulsoni's thread (4.4.2), androidmeda is building CM-11 final.

http://jenkins.androidarmv6.org/view/All/job/cm-experimental/1338/

Gerrit_Changes: 7815 7819

So, he might concentrate on porting CM-12 on armv6 devices (?). :)
[Optimus One, P500 Android Development] xu3sno:
OT

Gerrit rewiew 7815 7819

http://review.androidarmv6.org/#/c/7815/

http://review.androidarmv6.org/#/c/7819/

End of OT
[Optimus One, P500 Android Development] xu3sno:
Deleted
[Optimus One, P500 Android Development] ibub:
Okay, I just looked at gerrit, and it doesn't look good for cm-12, or armv6 in general. Expand the history at the bottom of the page, and read from January 31 to the present:

http://review.androidarmv6.org/#/c/7676/

Sorry brothers, I hate to tell bad news.

EDIT: As of this morning, androidarmv6 are trying last ditch efforts towards a working cm12. Pre-optimizing dexes and using sdext partition for the huge system and data images that will result.

Maybe there is still hope. :)
[Optimus One, P500 Android Development] ibub:
OT

Is this our next open source project?

http://dailynewstoyou.com/technolog...ll-set-for-sale-at-mwc-2015-h20150206206.html

/OT
[Optimus One, P500 Android Development] xu3sno:
OT

androidmeda created a new server androidmeda - ubuntu server

http://jenkins.androidarmv6.org/computer/androidmeda-server/

He tried to build CM12 for LG ...... but d855 (LG G3) :), although in several attempt it failed.

End of OT
[Optimus One, P500 Android Development] ibub:
Well the February 14 deadline has come and gone, and Jenkins is still online. So a sigh of relief. Also, in case anyone is wondering, androidarmv6 is still working on CM-12:

http://review.androidarmv6.org/#/c/7676/

Hopefully, they will succeed. :)
[Optimus One, P500 Android Development] xu3sno:
[MENTION=4912093]ibub[/MENTION]
[MENTION=4553005]Notonlyeyes[/MENTION]
[MENTION=4974969]HardLight[/MENTION]

Bye .... bye

http://jenkins.androidarmv6.org/

End Of Life for Jenkins and Download - 28.FEB.2015

However, Gerrit review server will be alive.
[Optimus One, P500 Android Development] ibub:
Updated second post.
[Optimus One, P500 Android Development] Dovidhalevi:
Yes, a long and great ride. And I remember someone's statement about never-never supporting JellyBean. Hardware inadequate and not enough room. Hardware, o' well, did work decently in the end, and room ... solutions were found. Lollipop has problems with room! O2SD might solve that one one commits to that model. Armv6 coding problems may have in the end killed the idea. Don't know. (Sour grapes time: Numerous articles about battery drain and other problems warning do not upgrade to LP!)

Another codebase with Armv6 non-support and need for some fancy shoehorning. Ubuntu! (Ubuntu is based on Debian which DOES support Armv6!)

Maybe time for a real quantum-shift?
[Optimus One, P500 Android Development] Dovidhalevi:
More ...

There are a lot of inexpensive but more-than-decent phones around now such as the new Moto-e, etc. Maybe a CM12 or OEM LP will run on these.

As for our dinosaurs, I believe the main problem is space. Read somewhere that 800mb is needed. Our 200mb, even the way I trim ROMs, just will not do it. ARM and the new system directory structure are the problem. Needs be solved before any reason to have continued development on this.

Option 1 is O2SD. Requires commitment, no return, but could be worthwhile.

Option 2 is symlinking, like we never did before. I cannot try it myself because I am not running CM-11, have not gone over to their new partioning, TSL, etc. But here goes:

1. Flash the latest CM-12.

2. Still in recovery, fire up adb and run link2sd's script and make system-app and system-privapp folders on sdext.

3. Move contents of /system/app and /system/privapp to these folders.

4. Remove them from system and symlink to the new ones.

5. Likely need to set selinux to permissive or remove entirely at first.

6. Now try to boot it. If it ate it and ART can complete its run, there might still be hope.
[Optimus One, P500 Android Development] xu3sno:
+1K

Time to look after their child ....., give them Lollipop! :) which money can buy!

http://www.phonearena.com/news/Best-Chinese-Android-smartphones-2015-edition_id63180
[Optimus One, P500 Android Development] KAGE-008:
ARMv6 devices are no longer being sold nowadays. I had a BCM21553 device as a main driver, but it got the worst part since CM9 development for that device stopped and CM11 still has bugs on it. Buying an ARMv7-A/ARMv8-A device as a definitive replacement is the only solution here, those ones have 5 times more development than older devices.
[Optimus One, P500 Android Development] nomancoolboy:
Updates ??
[Optimus One, P500 Android Development] ibub:
Jenkins dashboard is closed.

Gerrit is closed.

Stable downloads closed.

Github is still online. Androidmeda has merged all commits to CM- 12 branch (just in case someone wants to try). I left this thread open on the off chance that someone might have some success, but I'm not optimistic. As I don't have the skills and knowledge of androidarmv6 team, I am not likely to try it myself. It might be time to close this thread. :(
[Optimus One, P500 Android Development] wilk.gr76:
Hmm... Works fine on mine. It's using KK with ART enabled from dev settings.
[Optimus One, P500 Android Development] Dovidhalevi:
I still see P500 being offered by providers. My wife's daughter got one, promptly ditched it for an iPhone!

I believe the Raspberry PI is Armv6.

Regardless, it s difference in floating point instructions. A compiler should be able to handle this stuff, just like compiling for an Atom instead of an Armv7 chip.

I would venture an assertion that selecting ART offered here did nothing at all. It is simply not there on the KK ROM. Sorry.

Update: So far, I have been unable to sync enough stuff to even try to build a new ROM, KK or L.
[Optimus One, P500 Android Development] thunder45:
Hi [MENTION=4708203]Dovidhalevi[/MENTION], could you share the building instructions for KK or L? I would like to give a try building with Uber toolchain, but I have never built P500 or any other CM. I have only built SlimRoms so far.

Thank you in advance
[Optimus One, P500 Android Development] ibub:
P500 device tree is here:

https://github.com/androidarmv6/android_device_lge_p500

Look at the readme at the bottom of the page.

EDIT: You may also find this useful:

http://xdaforums.com/showthread.php?t=2060017

EDIT: And this:

http://xdaforums.com/showthread.php?t=2329228

:)
[Optimus One, P500 Android Development] Dovidhalevi:
That github has the cm-11 and cm-12 trees. May try syncing from there.

Rhar****'s tree has omni but I get no sources from it. May need to make another, composite, to get them. Not a git expert.
[Optimus One, P500 Android Development] KAGE-008:
ART simply doesn't work on ARMv6. I have an old S5830M with CM11 and tried the runtime switch but kept going back to Dalvik.

Also, Raspberry Pi is ARMv6 too (the 2nd gen model is ARMv7 though). Now I'm just waiting for a CM rom on my ARMv7 potatoes (I8200L and S6310L, the latter uses a Qualcomm MSM7227A CPU.)
[Optimus One, P500 Android Development] wilk.gr76:
1st: My RP is ARMv6

2nd: It does work. (But that might be a placebo effect)

3rd: I used the prebuilt one by MukulSoni
[Optimus One, P500 Android Development] ibub:
When ART is working on KK, every time you reboot you get the " Android is upgrading" message, as it pre-compiles all the user apps. I've never seen it do that on CM-11 for p500. Only during first boot of the ROM, as it is building the normal dalvik cache. Also, as I stated previously, the pre-compiled dexes (ART) are huge, and will quickly use up what little internal storage that you have left on a non-OS2SD ROM. This would render the OS inoperable. So even if it did work...it couldn't work...but it doesn't work even with os2sd. Sorry brother, but Google has finally programmed us out of the game.
[Optimus One, P500 Android Development] Dovidhalevi:
Goes back to dalvik because the runtime lib is simply not there.

See above. It is not there.

Who would want this whole recompile thing at every bootup? That would not be correct or desirable behavior.

OS2SD is maybe the best solution, but I might try symlinking the /system/app as I suggested.
[Optimus One, P500 Android Development] thunder45:
Thank you very much [MENTION=4912093]ibub[/MENTION]

Since I was using [MENTION=4974969]HardLight[/MENTION] OS2SD already, I then decided to give a try at OS2SD fork from AndroidArmV6 (https://github.com/os2sd) . It builds ok, but I miss root in that build. I have checked /system/xbin and there is no su binary there. Would you know what I have missed?

Thank you in advance

----------------------------------------------------

Nevermind, the problem is with os2sd (I don't know where). I just build the plain androidarmv6 base and su is there.

I'll review the changes made by os2sd to find out what is wrong.

Thanks
[Optimus One, P500 Android Development] Dovidhalevi:
Can you flash a supersu binary before going any farther? Which ROM have you built?
[Optimus One, P500 Android Development] ibub:
Since [MENTION=4974969]HardLight[/MENTION] instructions said to first init repo as androidarmv6, and then git clone os2sd/roomservice/roomservice.xml to .repo/local manifests, then roomservice.xml would be the expected source of the missing su binary. But there is not a "remove project" statement listed for external/ koush/Superuser. So I think that at the time of your initial repo sync, the server must not have been able to produce the source. Try a make clean, or a make clobber, and then try to build os2sd again.
[Optimus One, P500 Android Development] thunder45:
Didn't try to. I tried only to install SuperSu from PlayStore, but it failed of course. I'm still build a KK. Didn't try L yet, since I'm still verifying my building setup. thanks!

You are right [MENTION=4912093]ibub[/MENTION] . I created a new folders and I have followed [MENTION=4974969]HardLight[/MENTION] instructions again from the beginning (init androidamrv6 and then clone his roomservice.xml before repo sync) and then I built this new folder using the default 4.7 toolchain: all is working fine., su was built and packaged.

The sources for Koush Superuser were there on my other repo sync. So It was not a sync issue. Probably the changes I made to 4.8 toolchain are causing the build to skip external/koush/Superuser. I'll investigate further.

By the way, sorry for hijacking the thread.

Regards
[Optimus One, P500 Android Development] ibub:
No problem. At least this thread is serving some purpose now. :)
[Optimus One, P500 Android Development] thunder45:
Thanks you very much guys. It has built ok now. I think I was building as "user" and not "userdebug". Actually there were lots of other things missing:

add-property-tag_intermediates
bdt_intermediates
check-lost+found_intermediates
corrupt_gdt_free_blocks_intermediates
cpustats_intermediates
dhdutil_intermediates
keystore_cli_intermediates
ksminfo_intermediates
l2test_ertm_intermediates
latencytop_intermediates
libc_test_intermediates
libc_test_static_intermediates
librank_intermediates
memtrack_intermediates
memtrack_share_intermediates
micro_bench_static_intermediates
opcontrol_intermediates
pngtest_intermediates
procmem_intermediates
procrank_intermediates
radiooptions_intermediates
rawbu_intermediates
sane_schedstat_intermediates
set_ext4_err_bit_intermediates
showlease_intermediates
showmap_intermediates
showslab_intermediates
su_intermediates
wpa_cli_intermediates

I'll now give a try on L builds. Let's see how far it gets.

Cheers
[Optimus One, P500 Android Development] thunder45:
CM12 built but failed to flash. I think cm12.0 branch in androindarmv6 might not be os2sd ready yet. I'll investigate.

Regards
[Optimus One, P500 Android Development] ibub:
I'm thinking it might be caused by one or two things in twrp MULTI recovery. Make sure that you are in OS2SD Mode (advanced menu). Also go to wipe >advanced wipe and see if your data partition(sdcard) is listed as f2fs or ext4. I believe that the last changes by [MENTION=4974969]HardLight[/MENTION] (or was it Androidmeda? ) requires it to be ext4. If it isn't the correct format then the updater script will not allow it to flash. You can change the format while in that menu.
[Optimus One, P500 Android Development] ywor1:
Hey where you can download your file firmware would like to try
[Optimus One, P500 Android Development] thunder45:
Thanks [MENTION=4912093]ibub[/MENTION] . I think I'm on OS2SD mode since my cm11 build is OS2SD and that is flashing fine. When I get to Advanced menu, I see an option to switch to "Internal Mode", it means I'm on OS2SD mode right?

I could not double check my partition type (it didn't list anything in front of /data), but I'm 99% sure that it ext4.

I'll see if I find some time this weekend to give another try and read the error message properly.

Thanks again.

I'm trying to upload that, but it is really slow. I'll let you know when ready.

Thanks
[Optimus One, P500 Android Development] ibub:
[MENTION=5103629]thunder45[/MENTION]

I found some time to investigate. Seems that recovery.fstab in CM 11 branch of os2sd has /data (sdcard) in ext4 format.

But in the CM 12 branch, /data (sdcard) needs to be in f2fs format:

https://github.com/os2sd/android_device_lge_p500/commit/9f94d4e17bba5ae55bdde8521ddfe2ce99d5e8ef

So to convert the data partition in twrp MULTI, go to wipe >advanced wipe, and select data (DON'T SWIPE). Just above the swipe bar is a soft button that says "repair or change file system". Select that, and it will show partition information and two more soft buttons. Select "change file system". Now select f2fs, and then swipe to change. Now back out to home and flash CM 12.

;)
[Optimus One, P500 Android Development] thunder45:
Thank you [MENTION=4912093]ibub[/MENTION]

I'll give a try as soon as possible.

For the ones that would like to try as well, please get my build here:

https://www.androidfilehost.com/?fid=23991606952614890

https://www.androidfilehost.com/?fid=23991606952614891

Regards
[Optimus One, P500 Android Development] thunder45:
Apparently it fails to flash boot image:

Installing '/sdcard/AAA/cm-12-20150602-UNOFFICIAL-p500.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
I:Legacy property environment initialized.
minzip: Extracted 3 file(s)
detected filesystem ext4 for /dev/block/mmcblk0p2
about to run program [/tmp/install/bin/backuptool.sh] with 2 args
grep: /system/build.prop: No such file or directory
Not backing up files from incompatible version: 12
run_program: child exited with status 127
detected filesystem f2fs for /dev/block/mmcblk0p4
about to run program [/tmp/install/bin/otasigcheck.sh] with 1 args
Creating filesystem with parameters:
Size: 833617920
Block size: 4096
Blocks per group: 32768
Inodes per group: 7280
Inode size: 256
Journal blocks: 3180
Label:
Blocks: 203520
Block groups: 7
Reserved block group size: 55
Created filesystem with 11/50960 inodes and 6610/203520 blocks
warning: wipe_block_device: Wipe via secure discard failed, used discard instead

detected filesystem ext4 for /dev/block/mmcblk0p2
minzip: Extracted 0 file(s)
I:TWFunc::Set_Brightness: Setting brightness control to 5
I:TWFunc::Set_Brightness: Setting brightness control to 0
I:TWFunc::Set_Brightness: Setting brightness control to 255
I:TWFunc::Set_Brightness: Setting brightness control to 5
I:TWFunc::Set_Brightness: Setting brightness control to 0
I:TWFunc::Set_Brightness: Setting brightness control to 255
minzip: Extracted 1067 file(s)
created [/system/app/Bluetooth/lib]
created [/system/app/Bluetooth/lib/arm]
created [/system/priv-app/DefaultContainerService/lib]
created [/system/priv-app/DefaultContainerService/lib/arm]
created [/system/app/Gallery2/lib]
created [/system/app/Gallery2/lib/arm]
created [/system/app/Camera2/lib]
created [/system/app/Camera2/lib/arm]
created [/system/app/LatinIME/lib]
created [/system/app/LatinIME/lib/arm]
created [/system/app/PacProcessor/lib]
created [/system/app/PacProcessor/lib/arm]
created [/system/app/Terminal/lib]
created [/system/app/Terminal/lib/arm]
created [/system/app/PrintSpooler/lib]
created [/system/app/PrintSpooler/lib/arm]
created [/system/app/PicoTts/lib]
created [/system/app/PicoTts/lib/arm]
about to run program [/tmp/install/bin/backuptool.sh] with 2 args
/tmp/install/bin/backuptool.sh: cd: line 102: can't cd to /tmp/addon.d/
md5sum: can't open '*sh': No such file or directory
find: /tmp/addon.d/: No such file or directory
find: /tmp/addon.d/: No such file or directory
find: /tmp/addon.d/: No such file or directory
cp: can't stat '/tmp/addon.d/*': No such file or directory
can't find boot partitionscript aborted: assert failed: write_raw_image("/tmp/boot.img", "boot")
assert failed: write_raw_image("/tmp/boot.img", "boot")
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/sdcard/AAA/cm-12-20150602-UNOFFICIAL-p500.zip'
Error flashing zip '/sdcard/AAA/cm-12-20150602-UNOFFICIAL-p500.zip'
Updating partition details...
I:TWFunc::Set_Brightness: Setting brightness control to 5
...done

I need to review my build (roomservice.xml).

Thanks
[Optimus One, P500 Android Development] ibub:
Yeah, I got the same thing. Rebooting CM 9 internal. Gonna look at updater script again.
[Optimus One, P500 Android Development] kprsnt:
[MENTION=4912093]ibub[/MENTION] and [MENTION=5103629]thunder45[/MENTION]

I got one doubt...!

How u guys flashed 350mb system size of cm 12 build on 192mb size system partition...??

U will get the same log when u have insufficient storage space on system partition while flashing..

U can try to remove some apks but it won't work, because art files occupies almost 100mb in framework folder..

The best option to flash system partition on SD card system partition by editing updater script ....!

I don't had d device to test.. But surely it works
[Optimus One, P500 Android Development] ibub:
This is os2sd, so it does flash system to 2nd partition of sdcard. Still trying to get the boot.img to flash though. I can boot to internal system (cm-9) and look at /data/sdext2, which contains all the cm-12 system files. So at least the system flash succeeds. But without the kernel it doesn't even try to boot os2sd.