yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] OfficerJimLahey:
It's possible. I wouldn't set it up so the ROM is on the SD card, rather the data partition. You are right about killing the microSD prematurely, although not as bad as say, setting up a swap partition on it. But doing it I think is easy as changing the fstab to have the /data line point to the microSD (and then it would the user's responsibility to have the second, ext4 partition and personal stuff copied over on it). I would be willing to try it out in a couple weeks time.

EDIT: I was able to tame the Link2SD beast once I got Link2SD Plus and linked internal data with the apps as well. Then again, the heaviest app I use is probably Chrome.

I wouldn't release another version (although that would be easier), rather I would have a flashable zip that reverts the file for you. This would run after flashing the ROM. This way I am not maintaining several different types of the same ROM (having CWM Edition seems daunting enough).

UPDATE: Check downloads section for the flashable zip.

I can share my PayPal donation email, thanks for the offer! :) I hemmed and hawed over having it attached to my profile and in the end I opted out. There are studies on morale for those who volunteer and those who are paid a small amount for what they do - turns out the volunteers had better satisfaction with the work they did. Also, I didn't want to make myself look like I'm out there for money - It's just a (at times, dominating) hobby. :cowboy:

Will PM shortly, anyone else interested, you can find my donation email if you go to the NeedROM page for this (or the other) ROM.
[Miscellaneous Android Development] steadfasterX:
or you could use AROMA for your ROM and let the user decide before installing ;) :D

I'm on the road the next 2 weeks so no real time - otherwise I could implement that for you. So maybe some day later if there is a need/wish to do so. Really not that hard.
[Miscellaneous Android Development] vordhosbn:
I never use stock messaging apps on any of my android devices ever. Third party SMS app is always my first install. Just to be clear, if the stock messaging app is completely disabled, the 10k limit doesn't apply?

Hope we can see Android 5 on this device one day :)
[Miscellaneous Android Development] ajoh99:
This phone I don't think is suited for 5. It is ok on 4.1 but doesn't have the processor or (more importantly I think) ram to do more. It is my daily driver, and it chugs along faithfully, albeit slowly sometimes.

Regarding texts, I currently have a 23k SMS db and it is fine with 3rd party apps AND stock messaging 'frozen' in Titanium Backup. EXCEPT, sometimes, when the phone is very stressed multitasking, very rarely, an incoming message will be 'missed'. In that it tells the cell network the message is received, but it is never written to the DB. I run Ghostly SMS in the background as a workaround at all times and it catches maybe 1 message a month. This is always during periods of many simultaneous incoming messages and while the phone is also doing something else (ie google maps AND playing an MP3). Still, you may want to run it to be on the safe side. Also note, I SMS a lot, probably more than anyone who uses this ROM here. Constant SMS back and forth with work / family / etc all day everyday - so my results may be skewed.
[Miscellaneous Android Development] steadfasterX:
Yes my friend thats why i test all my boot.img/kernel builds on the recovery partition and have the twrp on boot partition while doing those tests ;)

I believe you missing loki for your boot.img !

-----
[Miscellaneous Android Development] OfficerJimLahey:
Just read your PM. That's exactly what I'm missing! :o

Now that you see what I'm trying to do, I can either figure our how to lokify the boot.img, or you can lokify one for me (with the small modification made on my previous post - in the spoiler) and then I can test (or you can test if you have a spare MicroSD with a bulky second partition formatted ext4).

I am interested in the former option, since I want to try out this loki process anyway. ;)
[Miscellaneous Android Development] steadfasterX:
I can do that of course, no prob.

I can guide you for loki, too. Very easy. I would recommend to use the standard tools for unpack and pack, too. I will send you all the details by PM..

-----
[Miscellaneous Android Development] OfficerJimLahey:
Okay, this is where I got. Repacking the boot.img was a success (again) and I was able to get past the kernel this time. However, it could have been because I forgot to wipe before I proceeded, but the reboot produced a lot of System UI errors (as attached).

I had Xposed installed previously, which made things worse after wiping and rebooting a second time (boot-looped).

I have a logcat, but it's too big to post on pastebin (> 18,000 lines).

But this is the result (1.5GB was what I had allocated to my mmcblk1p2 partition, will have to allocate more at a later point):

1|root@android:/sdcard # df
Filesystem Size Used Free Blksize
/dev 402.89M 64.00K 402.83M 4096
/tmp 402.89M 84.00K 402.81M 4096
/system 1.19G 654.79M 559.89M 4096
/mnt/asec 402.89M 0.00K 402.89M 4096
/mnt/obb 402.89M 0.00K 402.89M 4096
/data 1.50G 855.23M 677.37M 4096
/sns 7.91M 4.11M 3.80M 4096
/mpt 31.54M 13.56M 17.98M 4096
/persist-lg 7.91M 4.14M 3.77M 4096
/cache 788.39M 14.39M 774.00M 4096
/persist 7.91M 4.10M 3.81M 4096
/firmware 63.95M 41.83M 22.12M 16384
/storage/sdcard0 1.50G 855.23M 677.37M 4096
/storage/external_SD 27.81G 25.99G 1.83G 16384
/mnt/secure/asec 27.81G 25.99G 1.83G 16384

I will need to build a ROM with this kernel (in the recovery spot), so I can really test this closer to a clean room state. But not tonight.
[Miscellaneous Android Development] steadfasterX:
Great so it seems my guide was a help ..

You always need to wipe dalvik cache when flashing new kernels but it could be that your problems have a different cause..

-----
[Miscellaneous Android Development] OfficerJimLahey:
Could be a different cause, but that's what I am going on for now. Sort of glad things were done as they were, as once I wiped cache (dalvik would have been "wiped" as /data/dalvik-cache was moved to a blank location), I got a bootloop (probably due to my XPosed modules no longer working). Had I wiped first, I would have been even more discouraged, and less likely to clue in that's (XPosed) the cause.
[Miscellaneous Android Development] OfficerJimLahey:
Had a major setback. While preparing the ROM for a cleaner state, I accidentally wiped an internal partition (blk0p2) as opposed to where the new data partition lives (blk1p2). This killed the bootloader on my phone. Thanks to [MENTION=5545101]xdajog[/MENTION] (and an old MicroSD card - 4GB will do), I was able to revive the device and restore my bootloader. Everything is flashed back to true stock right now, so it will probably be a few days before I can attempt to try the MicroSD-as-the-/data-partition experiment again (will have to re-root, add TWRP to boot partition, and reflash ROM).

I will note in my OP when(/if) this ROM is online, to remove the MicroSD and (partition and) format it using GParted (or similar) to avoid any future disastrous off-by-one errors.

UPDATE:

Got around to testing it, so far so good. Uploading the Boot version to Copy now (i know, it will be a slow download), but I didn't want to post it on the downloads section in case someone downloaded it without reading all considerations - and there are a few.

Link will be active when I get around to it - bed for me now. ;)
[Miscellaneous Android Development] OfficerJimLahey:
Working... ;)

I had 1.5GB on my Link2SD partition, and an unused swap of 500MB. I ended up deleting the unused swap and resizing the 1.5GB to make ~2.0GB. Tight I know, but it will do for this experiment.
[Miscellaneous Android Development] Artemis-kun:
Incredible news! Since I'm using my F3Q as my only device, that hasn't given me much opportunity to fiddle with it, since my i927 more or less kicked the bucket... what I'm hoping is that with this development, we can perhaps use the full 4gb of the phone's internal storage as app store, or at least most of it and keep a small amount for whatever downloads I might need to store before moving it off to my msd. I've found one of the less desirable issues of using link2sd has been that listening to music stored on my 32gb microsd and running apps that are linked there results in music stuttering and slow app usage, presumably due to limited bandwidth from the card or slot. Unless somehow directly mounting that partition for /data/ doesn't cause that problem, in which case, I'm 100% for this route.
[Miscellaneous Android Development] Kediil:
SO. I got the nandroid done, and the TWRP installed, and flashed sedi.

Now I'm trying to install this ROM, and am having a problem. If I don't have at least one issue with each step, the fire gods will become angry and lay waste to Hawaii and New Zealand. An no one wants that to happen.

I've attached a picture of what it's doing as it denies me this ROM.
[Miscellaneous Android Development] OfficerJimLahey:
Any reason to use the old version of TWRP (2.7) when 2.8.1.0 is available?

The ROM tries some tricks that the old version of TWRP (and likewise CWM) cannot handle.

If sticking with this version of TWRP (highly recommended that you upgrade), I suggest trying the CWM Edition (which has the patched updater-binary).

Hope this helps.
[Miscellaneous Android Development] Kediil:
>:c

Because I followed 'Bulletproof Method 1', for the average user. And it specifies '/twrp_X.X.X.X_recovery_FRoff/off.img'

There are no instructions for using the 'twrp_v2.8.1.0_build5_fx3q_FR-OFF.img.zip'. I don't even know what DD is.

Method 2, which uses the build5 file, claims 'developers only', and is rather beyond my ability to encompass. I had enough issues with the first one.

If there is any way someone CMD challenged like me to put 2.8 on it, I would happily do so.

Can I try to simply install 2.8 over 2.7, or do I need to stock and start over?
[Miscellaneous Android Development] OfficerJimLahey:
Method one instructions can be used for any of the three recoveries, and strongly points toward downloading 2.8 (especially post #3). That's why the version is X'ed out in the instruction.

Don't worry about DD for this exact moment (which is known as a "disk duplicator"), but be sure to back up your EFS via DD before installing my ROM (details in second post), to prevent permanent problems (has yet to happen).

No need to use method two - as said, it is for developers only. Also, you can re-do Method 1 to flash/install 2.8 over 2.7 - no need to go back to stock - just keep in mind the new TWRP file name. Hope this helps.
[Miscellaneous Android Development] Kediil:
I read that, but the files don't corroborate.

Where do I get recovery 2.8? The only files listed are 2.7 FRoff ; 2.7 FRon ; and 2.8 build5.
[Miscellaneous Android Development] OfficerJimLahey:
2.8 and 2.8 build5 is one-and-the-same. :cowboy:
[Miscellaneous Android Development] Kediil:
Dang. I never had any luck installing it. Is it installed the same way as Method 1?

And thank you for all the help!
[Miscellaneous Android Development] OfficerJimLahey:
Same method. All you change (fro the meat of it) is the file name.

So instead of...

adb shell
su
mount -o remount,rw /system
cp /PATH-WHERE-YOU-COPIED/loki_tool /system/bin/ && chmod 755 /system/bin/loki_tool
loki_tool flash recovery /PATH-WHERE-YOU-COPIED/twrp_2.7.1.0_recovery_FRoff.img.lok

...(which worked for you before,) this time, enter...

adb shell
su
loki_tool flash recovery /PATH-WHERE-YOU-COPIED/twrp_v2.8.1.0_build5_fx3q_FR-OFF.img

Why not the middle two lines you may ask? Because loki_tool has already been installed.

How does that sound? :)
[Miscellaneous Android Development] Kediil:
Deceptively simple. I turned the thing back on, and it won't leave TWRP. I tell it to reboot to system, and it just comes back to TWRP. It was working fine yesterday.

This is just frustrating.
[Miscellaneous Android Development] OfficerJimLahey:
Sounds like you took method two instead.

Try reboot to recovery. If TWRP still comes up, that means you have TWRP on both your boot and recovery partitions. If it boots normally, let me know first before doing below.

So to fix this...

Reflash the kernel, that will put the kernel back in the boot position. Then, redo Method 1.
[Miscellaneous Android Development] Kediil:
I had only done method 1, BUT, I went ahead and started back over at stock, since I've managed to smooth out my wrinkles.

And everything is working! Now I just have to finish setting up Link2SD. Boy it would be nice if that wasn't necessary.

Thank you so much for the help Joel!
[Miscellaneous Android Development] Artemis-kun:
Well, it sounds like that won't be necessary for too much longer, hopefully. I should get on setting up my recovery for testing purposes... been so busy lately, haven't even had a chance to fiddle around with things yet.
[Miscellaneous Android Development] OfficerJimLahey:
Yeah, with my F3Q no longer as my primary it allows me to fiddle with it more, but harder to find the time to stress test it. Hopefully I can check music playback load in the next couple weeks.

Coincidentally, I recorded a video with it earlier today, early checks showed no glitches but I will have to play it back fully to be confident of that.

Sent from my ASUS_Z00AD

UPDATE:

Been playing music using the stock app (although I like Vanilla Music, it is not installed at the moment), and have yet to get a stutter. Browsed apps, settings, turned the screen off and on, even installed an app from downloads (FDroid).

Video playback seemed fine as well - recorded audio was hollow - but after playing back something six months ago, that was always the case. ;)

So as long as you have a good MicroSD (I use a Lexar 32GB Class 10 300x), you should maintain a smooth experience, even if a little slower.
[Miscellaneous Android Development] Kediil:
I know, I know, I'm back, asking questions again. I got my secondary phone all set up pretty as my primary. And I'm trying to get my other setup as well, for my sister to use.

Begin issue.

The KDZ stock program isn't detecting the phone.

The phone *does* show up in My Comp, and is detected by ADB.

ADB commands do work, I was able to flash sediKERNAL fine, as a test.

Secondarily, it started doing this a bit ago. It would claim 'not enough space for installation' on anything, and everything, even if the internal showed 400+mb free.

I factory reset, it's showing the 600/mb free, and says not enough space.

I don't know if that's related at all.

Any thoughts?
[Miscellaneous Android Development] Artemis-kun:
Yeah, my experience so far has taught me that the device seems to start thinking it's full at near the 8 or 900mb point, presumably since the 1.2gb is shows as total space is also shared as the internal phone storage, so I guess it starts assuming its full sooner in case you try to download things and the like. Though, post-factory reset does seem a bit odd... do you have much of anything stored on the internal storage? If so, I'd highly recommend offloading everything you can to an external sd. It's really a shame that there seems to be a massive rift between the spec for the phone and what storage seems to actually be on it... even allowing for the ROM itself, it seems to me that almost 2gb is missing from what's said to be on the device. Hopefully, we'll be able to unlock this mystery eventually.

As for the first bit, I believe it only shows up in the program when you've got the LG USB drivers installed as well as with the phone in the emergency recovery mode. If you've got ADB working properly, I'd be willing to bet that the ADB drivers are hampering your device from being detected in the KDZ program.
[Miscellaneous Android Development] Kediil:
Thanks, but I've had this phone for a while, so I am indeed aware of the storage issues. And I've actually stocked and rom'ed both of these phones without issue before. No idea why KDZ isn't detecting that the phones are plugged in and register everywhere else.
[Miscellaneous Android Development] Artemis-kun:
The only other things I can think of are the typical troubleshooting steps of isolating the issue as much as possible, so, new usb cable, different usb port, different computer altogether, hold your breath and hop on one foot while facing south by south west, etc etc. Not sure what further to suggest, as it is very strange that, as you say, it works in everything else but LGZ. Best of luck, though.
[Miscellaneous Android Development] ajoh99:
Has anyone else tried to install MicroSD edition? I have been eagerly awaiting it. Finally tried to install, I am having issues. I formatted the SD card as partition 1 fat32 (24gb) and partition 2 ext4 (6gb). I wiped, flashed, wiped davlik, and booted. But the phone never boots. It gets stuck indefinitely on the LG logo.

Any thoughts / reasons why?

Is there a way to make sure my Sd is properly formatted from within TWRP?
[Miscellaneous Android Development] OfficerJimLahey:
Yikes, that should work, as it looks like you got the steps down right.

I would suggest turning the phone off, pulling the microSD out of the phone, inserting it into the PC to double check the partitions and formats, and see if anything was actually saved.

And...was the second partition a primary or logical? It may make a difference. Can do:

cat /proc/partitions

...to find out, see if it ends in a 2 (primary) or a 5 (logical).

My example (last line before the prompt again is the one of interest):

joel@cybaryme:~$ cat /proc/partitions
major minor #blocks name

11 0 1048575 sr0
8 16 976762584 sdb
8 17 39061504 sdb1
8 18 1 sdb2
8 21 9764864 sdb5
8 22 9764864 sdb6
8 23 5858304 sdb7
8 24 912307200 sdb8
8 0 58615704 sda
8 1 58613760 sda1
8 32 31276032 sdc
8 33 29179904 sdc1
8 34 2091008 sdc2
joel@cybaryme:~$

I know, I have a lot of partitions. ;)
[Miscellaneous Android Development] ajoh99:
Got it working! Turned out my EXT4 was marked as logical instead of primary. I deleted, reformatted as primary (both partitions now marked primary). Booted fast and now in Settings -> Storage I have just under 6gb free. Thank you for truly breathing new life into this phone with this hack.

For reference: when the SD edition install failed to boot the first, the phone was unable to boot into recovery with the magic keys, just hard freeze on boot. I managed to get into TWRP via the factory reset combo (pull battery, hold vol down + power, insert battery). From there, I flashed TWRP on both the boot and recovery slots. Rebooted, TWRP came up, but a nandroid restore failed as it could not find /data. I ended up flashing the original rom, letting it boot the first time, rebooting into recovery slot twrp, flashing the sedirom again for good measure. After this, the phone behaved normally. From here, I tried the SD version flash again after wiping and setting EXT4 as primary on partition table. Worked perfect.
[Miscellaneous Android Development] OfficerJimLahey:
Probably didn't have to do all that. :cowboy: Glad you got it working though. :)

I will update my OP about the primary partition imperative. EDIT: Done. :good:
[Miscellaneous Android Development] ajoh99:
Yeah pretty much the only thing I overlooked was that Link2SD is perfectly fine with a logical partition, so I assumed I would be good to go. But it makes sense, since any logical partition is encapsulated in an extended partition, that the ROM wouldn't be able to access the logical.
[Miscellaneous Android Development] Artemis-kun:
Where is this microSD edition? Is it what I think it is?
[Miscellaneous Android Development] OfficerJimLahey:
First post, under special download.

It will allow you to leverage your MicroSD as your user data [emoji6]

Sent from my ASUS_Z00AD
[Miscellaneous Android Development] Artemis-kun:
Ack, I missed that. I was looking at the last edit date, which was back in May, so I discounted the first post as not having the requisite info, and yet, there it is. Thank you ever so much for finishing that up! I'm gonna get around to flashing it on the weekend, I think, because having no app storage has really been getting on my nerves... and, I think in the process, I'll look at a new card, perhaps get a UHS-1 one or something to help mitigate access speed slowdowns while reading music from the card at the same time (as this is definitely noticeable using link2sd with my current class 10 card) and even if it doesn't happen with your ROM, it'll still be better for me to start with a new card anyway. This one's a few years old, now.
[Miscellaneous Android Development] OfficerJimLahey:
If at all possible, make sure the new card the same size (easy if the old card is already 32GB) so if the new card dies prematurely (which I am hearing more as an old wives tale) and you made regular/semi-regular/at-least-once dd backups of the MicroSD, you could just restore the data on your old MicroSD (to not be temporarily out of a phone - should it occur).
[Miscellaneous Android Development] jloh1963:
WHAT DOES NOT WORK:

Soft reboot (often invoked optionally via XPosed) tends to lead to bootloop. If stuck in this situation, pull battery, reinsert, and power on normally.

This happens in the stock rom too. But you can press the power key for I think 10-20 seconds and that will force it to reboot. So I don't think this is because of your new rom.
[Miscellaneous Android Development] jloh1963:
WHAT DOES NOT WORK:

Home Screen in Setting forsce closes. This is because I removed the stock launcher. Oops.

Do you need the stock launcher? I have both the odex version and the deodexed version.
[Miscellaneous Android Development] jloh1963:
the deodexed one looks like it works just fine in your rom.
[Miscellaneous Android Development] OfficerJimLahey:
You only need the stock launcher insofar as avoiding the Settings FC (when pressing that exact option). I always disliked that stock launcher (top two memories of it was that it was ugly, and the app drawer didn't auto-sort), so I was never compelled to fix the FC (i.e. reinstalling the stock app).

But if that's a concern for you, the apk is still in a bloat folder (like a couple other things), so you can always move/copy it back to the system's app folder. :)

Just make a system backup first, in case something goes wrong (it may require the themes apps and stock keyboard too).
[Miscellaneous Android Development] ajoh99:
Hey, has anyone else been heavily using the MicroSD version of the rom? I have been using for about 2 months and want to compare experiences.

SD Card: SanDisk Ultra Plus 32gb HC class 1

The good: For the first time since I got this phone, it actually works the way I want it to. I can install all my necessary apps at once without out of space errors. Prior to this, the phone was nearly unusable. Even with Link2SD, I could not download from the play store due to out of memory errors and there was not enough space to install just my 4 most commonly used apps at once. Now I can actually use the phone as intended.

A++++++!!!!!!

The bad:

- It lags. Not too bad, but when I open a large app that has a list of messages or images, it can often take 10-20 seconds to populate, instead of 1 second or so on most other phones. This causes a few finicky apps (that I unfortunately use daily) to give up as the timeout is exceeded and never populate, but usually works on 2nd or 3rd time.

-I get FCs on apex launcher often if the phone is under stress. It always auto reloads, but the FC msgs get annoying. I got these messages occasionally before MicroSD rom, but now it is more often.

Other than that, it has been SMOOTH SAILING. This mod really enabled me to use my phone as a daily driver and not be frustrated by it's limitations.

Some questions: is there a better SD card I could / should be using that will respond quicker, or are this issues simply a symptom of the lag inherent in the microsd interface in the hardware?

Is anyone else using this rom that can share some their experience / tips?