yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] xda111114:
i pleasant day to all. i'm new to this forum and i'm a noob as well. i got a problem with my android phone. i took out the SD card to transfer data faster but by the time i inserted it back, the phone undergoes boot-loop process. i reboot the phone several times, take out the battery and waited for few minutes but no success, so i followed the procedure online to back up the users data by pressing the volume up and power button. it provides an option to save data in SD card with an extension of .backup. i cleared and reset phone to factory default and be able to gain access my phone. the problem is, i tried to restore data from the back file but as soon as i restored it it undergoes boot-loop process again. i just need my contacts and important messages. my questions are:

1. ) Is there a way to extract contacts and messages from userdata.backup file by copying the file in computer ?

2.) If its possible to extract, what software i need to use to extract it?

3.) Is there a way to enable usb debugging in the phone using a computer through a data cable?

hoping for your generous reply and thanks in advance.
[Miscellaneous Android Development] OfficerJimLahey:
Other Info...

CHANGE LOG:

Nightly 20150527 (CWM Edition v2.3):

Changed Updater Binary to work with CWM

Updated Apex Launcher to 3.10

Nightly 20150516 (v2.2):

Keymappings (moved Ctrl key for introduction of Tab)

Default ringtone label changed

Majority of bloat (moved to another folder) now purged

Nightly 20150511 (v2.0):

Enhancements with sediKERNEL 2.0

Shutdown animation replaced with LG logo

Default ringtone changed

Nightly 20150416 (v1.8):

Replaced Write & Share keypress in favour of Ctrl key.

Nightly 20150228 (v1.6):

Updated Apex Launcher to latest version (v3.0.3)

Updated SuperSU to latest version (v2.46)

Nightly 20141222 (v1.4):

Updated Apex Launcher to latest version (v3.0.1)

Updated SuperSU to latest version (v2.40)

Nightly 20141203 (v1.2):

Update sediKERNEL to v1.5

Added newest SuperSU (v2.37) to updater-script

Nightly 20141125 (v1.0):

Replaced Keyboard

Replaced Launcher

Removed bloat normally installed on first boot

Nightly 20141120 (v0.8):

Initial upload, using sediKERNEL v1.2

Debloated apps (see below)

Removed boot-up and shutdown sounds

Replaced boot and shutdown animations

BLOATWARE REMOVED:

Lines commented out (starting with a #) have been left in.

# probably safe to be removed:

Dictionarybin.apk
FileManager*.apk
FileShare*.apk
PolarisViewer*.apk
QTranslator*.apk

LGBrowser*.apk
LGBackup*.apk
Lookout*.apk
tmo_highlight*.apk
TMobile*.apk
ECID*.apk
com.mobitv*.apk
VVM*.apk
# QMemo*.apk
SmartShare*.apk
IQ*.apk
Weather*.apk
WifiCall*.apk

/system/etc/csc_*.txt
/system/etc/hidden_apks_list_*.txt

# Google apps which are downloadable from the market

Videos.apk
PlayGames.apk
#ChromeWithBrowser.apk
#GMS_Maps.apk
#Gmail2.apk
#YouTube.apk
Hangouts.apk
GoogleDrive.apk
Drive.apk
PlusOne.apk
Books.apk
Street.apk
Music2.apk
Magazines.apk

#This needs a replacement (done):

LGHome3a.apk
LGHome3_Theme_Biz.apk
LGHome3_Theme_Optimus.apk
LGIMEbin.apk

IDEAS:

I am open for them...
[Miscellaneous Android Development] steadfasterX:
Ah ok I may understand what you meant. What have you done regarding the boot image when you used archikitchen? Is it the pure stock boot image that you included only or how do you included that?

Well it must be pure DD ' ed boot image or simply using sediKERNEL as mentioned already. Both should fix your issue here.
[Miscellaneous Android Development] steadfasterX:
Hi Joel,

as I need to setup my wife's device now I choosen your debloated ROM.

I may will work on the AROMA installer if you like ;) The problem is I cannot test/debug anymore so it may be not such smooth developing experience though..

Options would be:

- Boot or Recovery installation

- Full wipe or partial wipe

- Rooted or not

- ...
[Miscellaneous Android Development] OfficerJimLahey:
Great! I can host the next version later tonight if you like (~9PM GMT), just need to get the changes together. (Do you have the new boot.img so I can include that?)

That would be awesome! I think having a separate zip for the boot and recovery install would be preferable though, less chance of devastatingly hitting the wrong option. The rest of the options can be managed by AROMA.
[Miscellaneous Android Development] steadfasterX:
Hm the mentioned adb options are already included in sediKERNEL. I remember that I added them because I thought it could make sense ;)

The trick is to watch the existence of adb while booting up because the mentioned setting will start adb for a short time only!

I use this while booting up:

while [ 1=1 ];do sleep 2 && adb devices;done

When you see your device connect with adb and you should be there.

The following settings are made in default.prop

ro.secure=0
ro.adb.secure=0
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.lge.eula_agreement=true
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=mtp,adb

So there should be everything you need in place. I think the reason why it was not working for you was that you do not connect to adb while booting.

The kexec-patches removed sediKERNEL is not ready yet.. may come today or tomorrow..

really? I think that would makes life much easier.. I think about such a thing:

------------------------------------------------------------------------------------------------------------------------
Normal installation (default selected)
Advanced installation
|
|---> if the user selects this the following would appear:
|
|- Default installation method
| (if you're not sure select this one)
|
|- Recovery installation method
| (if you have TWRP installed at BOOT partition only!!! some more detail hints etc)
------------------------------------------------------------------------------------------------------------------------

That would avoid having 2 installation zips which both need to be maintained and it will be clear enough (or can be made more clear) I believe..
[Miscellaneous Android Development] OfficerJimLahey:
If adb is already configured in v1.2, I will roll with that.

Oh, that sounds great! I was avoiding the possibility where there is two (small) buttons that decide which route to go. Thus, mis-"clicking" on the wrong one would cause a lot of headaches for the user.

If we can have a summary page of the options before flashing, with the opportunity to go back, that would make it bulletproof!
[Miscellaneous Android Development] steadfasterX:
yeah its in there..

I would do it really near bulletproof:

The user would be asked at least 2 or 3 times when the advanced mode selected and get information about some background details what that special option means.

And yes you could step back to the very first selection when you decide that this was not the correct option you want. no problem sir ;)
[Miscellaneous Android Development] OfficerJimLahey:
November 25th nightly released. Please see OP for details/download. I think we are now in beta phase!
[Miscellaneous Android Development] steadfasterX:
One question regarding that:

I see that "Write & Share" thing now every time when opening the hw keyboard.

In my case it opens AK Notepad which is an app i installed.

I wish we could disable that behaviour completely somehow..
[Miscellaneous Android Development] OfficerJimLahey:
Does anything happen if you freeze AK Notepad and then press that button? It's possible another app will take it's place, but I am curious about it's function because I haven't looked at it yet. I didn't know where to start with this one, but it gives me a clue.

You on hLe Storm now?
[Miscellaneous Android Development] steadfasterX:
I try to do so when my wife is willing to give it to me ;)

yes latest hLe version but with sediKERNEL v1.5 because the kernel code is not kexec patched there.
[Miscellaneous Android Development] steadfasterX:
Cool idea :) yes when I freeze ak notepad it will do nothing when opening the keyboard! That could be some kind of workaround.

I wondering if the slide open is an action / android intent which could be catched.. adb logcat would also be interesting when that happens..

hm i would like to really have a develop device ;)

-----

---------- Post added at 10:43 PM ---------- Previous post was at 10:34 PM ----------

Ah and one another thing: the physical keyboard backlight is very low and too short on as it could be useful.

I would like to have that optimized :) I know that there was the same issue with my Samsung Captivate Glide and it was fixed by replacing the liblights module amongst some other things.

I think we could do the same with the F3Q.. I may look into that some day ;)

-----
[Miscellaneous Android Development] steadfasterX:
Hm could you do this:

adb shell

tail -f /proc/kmsg

Then open the keyboard and wait until the lights of the keyboard go off . cancel the tail command and use e.g pastebin for the output

-----
[Miscellaneous Android Development] OfficerJimLahey:
December 3rd nightly released (sediKERNEL and SuperSU updated). As usual, please see OP for details/download, and now second post for change log. :D
[Miscellaneous Android Development] OfficerJimLahey:
Unfortunately there is no output. I Ctrl+C'd when I realized I wasn't going to get anything (even after running as superuser). Also, interestingly enough (going back a few posts), my "Write and Share" button still brings up the appropriate app!
[Miscellaneous Android Development] steadfasterX:
oh I'm sorry tail will not work here, we must use cat instead

could you try:

adb shell
su

[B]cat[/B] /proc/kmsg > /tmp/dmesg.log

--> slide open, wait until lights going off, slide close

adb pull /tmp/dmesg.log

if the above does not work (only then):

adb shell
su

while true; do dmesg -c >> /tmp/dmesg.log && sleep 2 ;done
adb pull /tmp/dmesg.log

upload /tmp/dmesg.log

thx
[Miscellaneous Android Development] OfficerJimLahey:
Achieved.

http://pastebin.com/nCHnY2Qu

A bit modified though. Used method one (saving to /sdcard as it didn't like /tmp), opened keyboard, pressed the "write and share" button, closed keyboard.
[Miscellaneous Android Development] OfficerJimLahey:
v1.4 (aka Nightly 20141222) Released

Small update, in keeping the replaced apps current. If you have hLe Storm already installed this won't mean much (unless you want to keep as little as necessary on the userdata partition), as you can let those apps update via Google Play and then allow SuperSU to do it's thing (I chose the TWRP option when it came time to update the superuser binary).

CHANGE LOG:

Nightly 20141222 (v1.4):

Updated Apex Launcher to latest version (v3.0.1)

Updated SuperSU to latest version (v2.40)

Please see OP for download links.
[Miscellaneous Android Development] lameboyadvance:
Any change with the keyboard app/write&share issue? I'm waiting for that to be fixed before I attempt flashing my F3Q.

...Looking at the log joel.maxuel posted, the only things that stand out to me are the 's5712ACDL1_irq_handler' and 'hall_ic_report_event' lines. Does that mean the keyboard uses a hall effect sensor to detect when its opened/closed?

Can't see anything about the write & share keypress in that log (not that I can decipher much of it anyway since I don't know much about any of this stuff).
[Miscellaneous Android Development] OfficerJimLahey:
Nothing new. Any assumption I have had with this issue has been debunked. [MENTION=5545101]xdajog[/MENTION] was able to change his write and share app without even trying (another app took it's place), and i was not able to duplicate this as Write and Share is still somehow part of the ROM.

That's where I was last month, before I had hardware issues on my PC. A hard drive and power supply later, I have pretty much rebuilt my Linux PC to my liking.

We'll see if I can take another look at this in the next week.
[Miscellaneous Android Development] OfficerJimLahey:
v1.6 Released...

Detected a new version of SuperSU, so I have updated the ROM...

Please check OP for links, or NeedROM for downloads.
[Miscellaneous Android Development] OfficerJimLahey:
Thanks to [MENTION=6462551]Keth Tenderfoot[/MENTION] and his thread, I was successfully able to remap the Write and Share app key to something a little more benign. I chose a Ctrl key, since I do terminal work.

Should see a ROM update with this change in the next few days.
[Miscellaneous Android Development] lameboyadvance:
So does that mean we could map the WRITE_SHARE keypress to loading a custom app?
[Miscellaneous Android Development] OfficerJimLahey:
No, I never figured out that action beyond the keypress. But typing on a keyboard and having anything come up when the button was accidentally pressed was annoying. For me, mapping it to a Ctrl key made more sense.
[Miscellaneous Android Development] lameboyadvance:
...Do the 2 FN keys register as 2 different keys? That way I could use one for a Ctrl key while keeping the write/share key for other purposes.
[Miscellaneous Android Development] OfficerJimLahey:
Yes, ALT_LEFT and ALT_RIGHT. The configuration you mention is a lot like the way Keth had it set up, but because I don't want to call a separate app on the keyboard (for reasons explained above), I can leave the remapping to you.

With that (sorry for the late edit, was working on a ROM for another device):

Also uploaded on NeedROM as well.
[Miscellaneous Android Development] ajoh99:
A heads up for anyone using this rom: for me (on a clean flash, tested couple times), once I get above a certain number of SMS (10,000+), sometimes SMS fail to be written to the database if the stock messaging app is enabled at all. The phone will ring and vibrate, but no text will be shown in the stock SMS app or any third-party app. Ghostly SMS will catch them if you have it installed. For now, I have frozen the stock SMS app in titanium backup, and it has been working fine with GoSMS Pro and Yaata.
[Miscellaneous Android Development] OfficerJimLahey:
No wonder why I never ran into this wall - I've only went through 700 SMS's since November. :p

Do you know if this is the case for the stock ROM (LG factory version) as well?

Guess I should look for a setting (or an app) to delete/clean up the oldest of the messages, in case one is inclined to stick with the stock app.
[Miscellaneous Android Development] ajoh99:
There are many apps to delete old texts, and Android doesn't generally handle so many texts well. Stock SMS app is possibly set to delete msgs after the thread reaches 500, but I love having my whole text history available and easily searchable.

Honestly, not sure if it happens on stock rom too, but I bet that it does. Now that I have everything stable and perfect though, not going to mess with it just for the sake of testing.

The key way just freezing the stock messaging app so it can't muck it up. Then third party SMS apps work fine. Currently have about 21,000 messages, runs smooth but I do restart it at least once a day or so.
[Miscellaneous Android Development] OfficerJimLahey:
[MENTION=1427992]ajoh99[/MENTION], I had a moment to look. The settings option is "Storage". It is automatically set to delete old messages, keeping the newest 500 SMS, and 50 MMS, per conversation. Probably why my total was only 700, as my most frequent contact has a history starting in January (MMS) and March (SMS). So the auto-delete is working anyway (at least for the first beta build). I suppose you turned the auto-delete off...or have many conversations (at least 20) at capacity?

I'll mention it in the issues, as a warning of what will happen if the delete gets turned off. Thanks for the info!
[Miscellaneous Android Development] OfficerJimLahey:
v2.0 up!

Quick note:

Enjoy!
[Miscellaneous Android Development] ajoh99:
EDIT: This method seems to turn off ability to use FN key when enabled, searching for better solution

Stumbled across something useful for everyone: Custom map any keyboard key to open any application

XPosed Additions Pro works perfectly with our HW keyboard. Install the module, purchase the upgrade on Play store.

In settings, Buttons, Allow External, check Keyboard

Now click add new key, press the key (even Search and Write buttons work),

Click into newly created entry for the key, Add New Condition, Screen On, Load Application List, select the app you want to launch.

Now click into the newly created 'Screen On' entry, select the trigger action - can choose from lots of options ranging from single press, to double click, long press, etc.

Very useful, and very configurable.

Also: testing new ROM this weekend, keep up the great work!
[Miscellaneous Android Development] OfficerJimLahey:
Interesting find! Although the caveat turns me away from it...for now ;)

Got competing demands these days, but will do! Also, I will either re-release 2.0 - or make a 3.0 - due to the aforementioned issues with the launcher. I have a replacement candidate (Atom Launcher), just have to test it myself and then ask permission to use for the ROM.

Small proposed changes would also include another keyboard remap (move ctrl key where the right alt/fn key currently is, to make way for a tab key), and get rid of the labelling for the default ringtone (the sound is different ATM, but the change made earlier was just a kludge).

Any other ideas are welcome. :cowboy:

EDIT: Atom doesn't fit my needs. :(

Mind you, I spent about 15 minutes with it, not really long enough, but I see I would have to rebuild the icon pack (as the theme that came with the launcher all blends in for me - not a good thing - and the icon pack designed for Apex decides to show the original LG icons instead). There were nice features, including widgets in lieu of persistent search bar, but I could not see how to restore the search bar. Also, you cannot hide apps in the app drawer. Finally, homescreen locking is buried in the settings.

Here is what I am looking for in a launcher:

Homescreen locking a must (with quick way to toggle is nice)

Persistent search bar

Ability to rename homescreen icons

Ability to hide app drawer icons without freezing them

Icon theming (to get rid of the LG originals - if it works with the existing icon pack, that's a bonus)

Nova is another option, but I am hesitant there. Any other suggestions?

http://www.androidcentral.com/best-android-launchers

By the way, poll is up for the next month to determine the future of Apex in this ROM.
[Miscellaneous Android Development] OfficerJimLahey:
2.2 up!

Another Quick note...

Link in the OP, NeedROM mirror to come.

Btw, there is now a poll going on. :cowboy:
[Miscellaneous Android Development] dub5a:
This is probably a dumb question, and I am probably missing something (because I am a newbie to this, even though I thought I did my research)... but I will ask anyway.

I am trying to get this ROM on my phone. Here is what I have done:

I downloaded the newest ROM .ZIP file from the first post

Put the ROM .ZIP file on my phone's external SD card

Downloaded the app for CWM (the OUD Hitsquad Manager app)

My phone is also rooted using "saferoot"

As per the instructions, I have tried to boot into recovery mode using the CWM app (Recovery Options -> Reboot to Recovery)... and I have also tried using ADB shell ("adb reboot recovery"). Neither option works... my phone just restarts and shows an image of an Android laying down with a red "X" warning... after about a minute of showing this image, the phone will restart normally.

If you know what I'm missing or doing wrong, please let me know.
[Miscellaneous Android Development] steadfasterX:
a probably dumb question back ;) :

You said you have downloaded the app but do you have executed the recovery installation within? :rolleyes:

if so: any error messages shown?

you could also try TWRP

greetings

xdajog.
[Miscellaneous Android Development] OfficerJimLahey:
You must be outside the USA as well. ;)

How did I know? The loki file didn't download for you withing the app. Seems you must be within US territory for the app to function properly.

Here's what you can do...download the file from this post, save it to your device, fire up the CWM installer again. Get it to the point where it has "downloaded" the file (in reality it will be an empty file), and all you need to do is flash it. Go to the home screen, open a file manager, and copy the proper flash to /sdcard/f3qutlities (folder will already be there), renaming it to the dummy file.

Close your file manager, switch back to the CWM app, and press that magical button. You should have CWM this time around. Note that the reboot button never worked for me, it always force closed, so woill probably need to "adb reboot recovery" when you want to get into CWM.

Hope this helps, and if it is too much of a bother, you can use TWRP instead (TBH, I never tried my ROM against CWM).

When I used it, error messages never shown, except for the force close when you use the reboot function, it errors out silently.
[Miscellaneous Android Development] dub5a:
Thank you for your response(s).

I am not outside of the USA. But, I do not have a SIM card in the phone yet. So, that may be why the CWM app did not fully install the recovery/LOKI app that you are referring to.

I am going to try uninstalling the CWM app... then, I will get my SIM card in the phone. I believe the phone is SIM unlocked, but I will obviously find out when I put my SIM in it... I will get it SIM unlocked if I have to, and then I will go from there and try again.

If it still doesn't work, I will try the solution that you posted. I have one question... if I need to manually put the LOKI file on to my device, where should I be putting it? (i.e. is there a particular folder or directory that I should put it in?)

Will update in the next day or so after trying everything again with a SIM card. Thanks.
[Miscellaneous Android Development] dub5a:
Just posting to see if this thread is working again... and to let anyone else out there know that this ROM will work via CWM (see first post for instructions). Great ROM!
[Miscellaneous Android Development] OfficerJimLahey:
Works in the app and Tapatalk, hopefully it is fixed in web as well.
[Miscellaneous Android Development] OfficerJimLahey:
First CWM Edition Up!

From the changelog:

This should work with TWRP as well, but I did not check. I plan to have CWM Editions every once in a while. If someone can verify that CWM editions work with TWRP as well, I may just make them all CWM Editions for full compatibility. :cowboy:
[Miscellaneous Android Development] ajoh99:
Thanks for working away on this. You and xdajog are the only ones keeping my QWERTY slider dream alive!

Wondering if there is any way we can get the ROM to install on a partition of the SD card. Using this phone as my daily driver has proved difficult due to limited storage. Even with link2sd and foldermount working properly, the system thinks it has no space, Google play refuses to download new apps and etc. If we could make a way to install to a partition of an SD card, I would invest in a super high speed one. I know running the system functions off an SD would destroy the SD in maybe 6 months to a year, but that is OK by me to have some freedom on my phone.

Second, can you release a version from now on without your custom keymappings? I like both of my FN keys where they are, and actually use the write and share app and its key pretty often. Or perhaps, make a script that I can run before I flash every new version to change the keymappings back?

Last, I want to donate a little extra cash towards your efforts. I helped xdajog get his dev phone, and wanna make sure you don't feel left out ;)

I wish I had the knowledge/time to help in some other way, but AT LEAST I can make sure you have enough Red Bull to keep you hacking away. PM a way to get $ to you.