yashsingh1/xdaforums huggingface dataset:
[G3 Themes and Apps] marcdw:
Oh yeah, completely forgot about the log file. Right now in BrokenOS there's only one line in it.

01-02-2009 05:00:00 AM Init.d successful, SELinux status is Permissive

Getting serious Setup Wizard FC issues with latest Resurrection Remix. Once I get that squared away I'll get the log from there.

LG G3 D851, BrokenOS MM ROM, Tapatalk 4.9.5
[G3 Themes and Apps] marcdw:
Resurrection Remix, after emulating init.d, has the same entries in the log.

Still no manufacturers listed in app.

LG G3 D851, Resurrection Remix-M ROM, Tapatalk 4.9.5

---------- Post added at 03:11 PM ---------- Previous post was at 02:58 PM ----------

Well here's something unexpected. In the init.d emulator app there's a feature to see last execution status. Seems there's an error somewhere. Looks like $country value isn't being determined/passed to setprop.

LG G3 D851, Resurrection Remix-M ROM, Tapatalk 4.9.5
[G3 Themes and Apps] Jc_master:
[MENTION=4842752]Eyalkn[/MENTION] if you don't have the log file, it means init.d is disabled in your rom, you have to enable it, emulated init.d wont work.

[MENTION=6046143]marcdw[/MENTION] emulated init.d wont work because the script runs after the system has booted, the script need to run at boot for when the apps start the right information is in the system, i have Resurrection Remix and emulated init.d did not work for me, i had to use Universal init.d from the play store for real init.d support
[G3 Themes and Apps] Eyalkn:
I know I have init.d support since I'm getting recent logs from other scripts I'm running in init.d using project skynet.
[G3 Themes and Apps] Jc_master:
[MENTION=4842752]Eyalkn[/MENTION] if the 10QuickRemote.sh file is working, you should see the Qremote.log, try manually copying 10QuickRemote.sh to /system/etc/init.d/ and give the right permissions rwxrwxrwx later i will provide you with another sh script it the previous does not work
[G3 Themes and Apps] marcdw:
Regardless of the init.d stuff I need confirmation on the setprop error mentioned earlier. Does the program work properly if there is no country returned? I don't know if it's a requirement.

#try to set target country
country="$(getprop persist.sys.country)"
setprop ro.build.target_country $country

The getprop returns nothing, even at a terminal. And nothing in build.prop.

Just trying to cover all the bases.
[G3 Themes and Apps] discplay:
does this method works on LG G3 D855 with CM12.1?
[G3 Themes and Apps] Eyalkn:
The reason is probably because I'm using skybox that is provided with the skynet mod to replace busybox. Is there a way to make this scrip recognise it?
[G3 Themes and Apps] Jc_master:
[MENTION=6046143]marcdw[/MENTION] it seems that the set target country command on the script is really not necessary, i cant find that option in my build.prop, and i get the same error if run the script manually, but it works anyways as you can see on my log screen capture, the only thing i can think is that you copy manually all the files to their places and set the permissions manually, wich i did twice for it to work, im going to make a nand backup and flash another rom on my phone to see if it was just luck or the file really is working

[MENTION=4842752]Eyalkn[/MENTION] that really goes beyond my knowledge, i dont know how to make the script to recognize skybox, but i will try to find out, i had a problem with another flashable zip trying to find busybox and i had to change the rout before the "busybox" line for it to look like

this "/sbin/busybox bla bla bla"

because it only had "busybox bla bla bla" but i dont know about this script
[G3 Themes and Apps] Eyalkn:
Thank you for your work and help.
[G3 Themes and Apps] Jc_master:
[MENTION=6046143]marcdw[/MENTION] so, i backed up my ROM and installed AICP wich is also MM 6.0, and i had some problems to make it work, but now it is working, i hope this helps.

First i flashed the zip, QuickRemote was in the app drawer but no manufacturers and no Qremote.log, init.d was disabled, so i installed Universal init.d from the play store and restarted, no Qremote.log and no manufacturers on QuickRemote, Universal init.d asked for SU permission, i granted them and restarted, now i do get Qremote.log wich showed successful Selinux set to Permissive but still no manufacturers, i cheked on the apps list and checked to show system apps and QuicksetSDK was not showing so i manually copied the apk to its respective folder in system and set the permissions, rebooted and still no manufacturers, i rebooted into recovery, copied the entire QuicksetSDK folder onto /system/app and chmod644 QuicksetSDK manually, rebooted and still no manufacturers and still no QuicksetSDK in the apps list (under settings menu) so i had a newer version of QuicksetSDK on my sd, i manually copied it to /system/app/QuicksetSDK and gave it the right permissions, i rebooted the system and now QuicksetSDK is showing in the apps list but still no manufacturers, so i force closed the app, deleted its data/cache and went to the Sdcard and deleted Quicksetsetup folder, manually copied the QuicksetSDK apk from the zip that [MENTION=3735359]syndre[/MENTION] provided and set the permissions, rebooted and voila, QuickRemote is working again.

So, im short, check your apps list to see if QuicksetSDK is there, if not, manually copy and set permission to the QuicksetSDK that im living here, reboot, check again, if its there, open QuickRemote and look for manufacturers, if still no manufacturers, force close QuicksetSDK, clean data and cache (only for QuicksetSDK) delete Quicksetsetup folder from Sd, manually copy and set permissions to the QuicksetSDK apk from the original zip (provided by syndre) and reboot, i hope this time it works.
[G3 Themes and Apps] Jc_master:
[MENTION=4842752]Eyalkn[/MENTION] so the script does not run at all? Even after manually running it you dont get the Qremote.log file on the sd? Because seeing the script, i think busybox is just needed to chmod666 ttyHSL1 on /dev/, check the file to see if permissions are

rw-rw-rw, if i'm correct thats the only thing for wich the script needs busybox
[G3 Themes and Apps] KronicSkillz:
thanks alot man im going to try this other version of quickset sdk because i tried everything you did with the other one and had no success, are you planning on making a new thread with a flashable that works for everyone? because alot of ppl have been looking for this if you aren't gonna setup a new thread i think i might once i'm sure everything is working for all (or most atleast) aosp mm roms, just so everyone can enjoy the collaborative work done here. let me know, thanks again i'll only take credit for the work i do obviously, which hopefully will be getting it working on my model and whichever roms i can test it on... right now starting with mokee 6 and cm13

i thought my problem was that universal init.d didn't run early enough in the boot process because i figured out init.d is disabled on cm13 so i was trying to find a kernel that supports it. thanks for all the info.

*edit* right now im getting no quickset sdk in the apps menu (with all apps showing) but when i try to open quick remote it lags like hell and then i get a "unfortunately quickset sdk has force closed" message.... lol so it seems like the system is trying to run it even when its not in the apps list... anyways gonna keep trying to stuff i'll get back to you.

---------- Post added at 01:18 AM ---------- Previous post was at 12:55 AM ----------

can i ask you if the file or files in /quicksetsdk/lib/arm/ folder contain anything, because all i have in that folder is libdummy_32.so and its an empty file.

---------- Post added at 01:24 AM ---------- Previous post was at 01:18 AM ----------

I decided i'll try this on aicp first, and see if that works on d852. then if it works ill switch to a clean install of cm13, then move to mokee if i get those working. that should help determine if its a rom issue or variant issue. also i have all kinds of mods so will probably help to run demos on fresh installs.
[G3 Themes and Apps] Jc_master:
[MENTION=5096904]KronicSkillz[/MENTION] you can enable init.d with Universal init.d from the playstore, also, if you dont get QuicksetSDK on the apps list, try what i told marcwd to do, the file on the libs folder is ok, is just a dummy, and about the post, at least i know how to make QuickRemote work on Resurrection Remix and AICP when we can make it work on your roms i want to get as much information possible so i can make a post for everyone who is searching dor this, but lets make this work on your roms first and later we speak about a thread, if you need more help or info, just ask for it
[G3 Themes and Apps] KronicSkillz:
k sounds good im trying all kinds of stuff ill report back and i already turned on universal init.d by the way and was getting log file in sdcard etc trust me ive tried everything i'm just happy to have a new quickset sdk to try.
[G3 Themes and Apps] smolchy:
doesn't work on Bliss 6.0, i tried with Syndre QiuckSDK
[G3 Themes and Apps] Jc_master:
What is the problem? Do you get QuickRemote on the app drawer? You have the Qremote.log on the sd? Have you read the previous comments? Have you troubleshooted anything? And if so, what? I need more info to help you
[G3 Themes and Apps] KronicSkillz:
it turns out that its something with the exact process you used. i'm still on mokee 6 which is cm13 based like aicp. i tried the new sdk and it didn't show up then i did what you did and deleted quickset sdk folder and rebooted and still nothing, then i tried going back to the original quickset sdk from flash file and thats when it started working. It seems as though the the quickset sdk you posted does something to initialize the app or something, then once you switch back to the other one it works.... doesn't make alot of sense, but it's working only when installing the newer sdk, then switching back to old one.

manufactures list is showing up and ir reciever is working for learning.

the solution may be to make 2 different flash files, one with the original one after he fixed the folder structure and init scripts, and then another flashable with just the quickset sdk that you posted.

the process would be

-make sure universal init.d is working

-flash original zip

-reboot and check if app is working if not continue

-flash second zip

-reboot

- try to run the quickremote app (i think thats when the quickset folder shows up on sdcard but we can test for this)(may not be needed)

-delete the quickset folder (may not be needed)

-flash original zip again

-reboot

? something along those lines unless there is a different reason why it worked that way for us
[G3 Themes and Apps] smolchy:
I enabled int.d, also I have permissive mode, I deleted QuickSDK and copied the one from Syndre and set permissions to 644...

and there is no Qermote.log
[G3 Themes and Apps] Jc_master:
Yes, try the new QuicksetSDK and maybe you need to revert to the old, that what i did to make it work,

About the other thing

The problem with me is that i use an ls980 (sprint g2) and i only have a handfull of roms to try, i got it working with Resurrection Remix on 5.1.1 and 6.0, and AICP, i havent tried CM but i guess that will be tomorrow's task, and blisspop later, also Crdroid and dirty unicorns wich are the main roms for the ls980, but as of now, it seems that the workaround is allmost the same, at least for the roms i've tried, also, even though i flash roms/recovery and customize smartphones since 2012, i have a limit for my knowledge, when it comes to scripts etc, i dont have too many knowledge, so, there are things that are beyond my reach and that may or may not be a problem with this because at least you three guys are really wise about this
[G3 Themes and Apps] KronicSkillz:
yeah we might not have to try that many if we find a process that seems to be working on most then just post it and we can work through issues as they come up.

in the process i suggested was just thinking thats easier for people then manually copying files and changing permits.

you may have to add to the script to change permits for sdk in the 2nd zip.
[G3 Themes and Apps] Jc_master:
Yes, that seems to be the more logic way to make this easy-to-use, or, if we can see what the newer QuicksetSDK does to the system that makes the older version work and include it in the zip, but that would be more difficult to make, i will make the two zips tomorrow and try it with blisspop to see how it works

---------- Post added at 08:49 AM ---------- Previous post was at 08:43 AM ----------

Ok, what it seems to be working is, using Universal init.d to really enable init.d, flash the zip that syndre posted, then copy and set permissions to the QuicksetSDK apk that i posted, reboot and see if it shows in the app list under settings menu, force close it and delete its data and cache also delete the Quicksetsetup folder on sd, copy the QuicksetSDK apk that is inside syndre's zip and set permissions, reboot and it should work, at least for me and KronicSkillz it worked

---------- Post added at 09:12 AM ---------- Previous post was at 08:49 AM ----------

@KronicSkillz im messing around with the system and in /data/data/com.uei.lg.quicksetsdk.maxq616/app_assets/ there is a file named "brands.xml" wich contains the complete manufacturer list, maybe this folder has something to do with the problems, tomorrow i will check if there is a difference in this folder before and after making the QuicksetSDK mambo jambo, it's the only other place so far in wich i found QuicksetSDK and QuickRemote data
[G3 Themes and Apps] smolchy:
so I had int.d Toggler installed and this app was always said that int.d is enabled...now I uninstalled it and installed Unversal init.d...and this app said that there is no support for init.d on this ROM :(
[G3 Themes and Apps] KronicSkillz:
that means you can use the original init.d process, just turn universal init.d on at the top (there is a switch) and then reboot and itll say you have init.d support

---------- Post added at 03:42 AM ---------- Previous post was at 03:39 AM ----------

so it worked a little diff when i tried on my cm13 backup. this one has xposed and a bunch of other mods and i did get it to work eventually. this time the same thing happened as with my mokee 6 install except i didn't get a quickset sdk force close until after i had put the original sdk back and fixed permissions then reboot and i had to reopen the app a few times then it started working... very strange
[G3 Themes and Apps] smolchy:
ok, I'm out of ideas...try everything...still no manufacture list...

qremote.log init.d successful, selinux is permissive
[G3 Themes and Apps] KronicSkillz:
did u try swapping back and fourth between quickset sdk's like we mentioned above, i was in ur shoes until i tried that.
[G3 Themes and Apps] smolchy:
nope, I didn't...so if I get this right...First I do flash zip...try it...if not working, I swap the files ...and if still not working, I put the old one back?

are permissions 644 OK?

so I swapped a couple of times between the files and reboot...still the same...

if I use the original QuickSDK, I can't see it under sys-apps
[G3 Themes and Apps] Eyalkn:
After I run it manually log was created

I also changed the permissions of the qremote app like you said and rebooted. The buttons are still not working inside my remotes.
[G3 Themes and Apps] Jc_master:
[MENTION=4108604]smolchy[/MENTION] yes, i recommend that you use Es File Explorer with root access to do all the file copying, once you have syndres flash installed and you rebooted and you are sure that Qremote.log shows that Selinux is permissive, you overwrite QuicksetSDK apk on /system/app/QuicksetSDK and set permissions to rw-r--r--, you reboot and check if QuicksetSDK shows in the apps list (you have to select "show system" under the 3 dot menu) if it shows, you force close it and delete data/cache in that same menu, you go to your sdcard and delete the folder named QuickSetup, now you switch back to QuicksetSDK with the one on syndres zip, just the QuicksetSDK apk, you copy it in system/app/QuicksetSDK and set the permissions again to rw-r--r-- do this exactly as i said, today i will have two modified zips to simplify this process

[MENTION=4842752]Eyalkn[/MENTION] try doing what i just described to smolchy to see if that works, it did for me and KronicSkillz
[G3 Themes and Apps] Jc_master:
[MENTION=4108604]smolchy[/MENTION] [MENTION=4842752]Eyalkn[/MENTION] [MENTION=6046143]marcdw[/MENTION] and everyone having trouble with this, you can visit my new thread HERE where i explain in my opinion, a better way to do this, now you wont be needing to set permissions or copy files manually, i made extra flashable zips to fix all that, i hope it helps
[G3 Themes and Apps] smolchy:
it's working like a charm!

thank you!
[G3 Themes and Apps] Eyalkn:
Thank you for all your help and patience, it worked even with using skybox instead of busybox.
[G3 Themes and Apps] Jc_master:
You're welcome, I'm glad i could help
[G3 Themes and Apps] Necromancer3:
Is there an updated apk? or quickset?

On my MM device i get a remote thats missing from my lollipop one (which is downloaded from this thread).
[G3 Themes and Apps] marcdw:
Would that be Sceptre? That one I know is missing from the MM remote.

No updated apk that I know of.

LG G3 D851, Mahdi KitKat ROM, microG Project (NoGapps), Tapatalk 4.9.5
[G3 Themes and Apps] Necromancer3:
Its for xtreamer.

My MM G3 has 2 remotes for it, the apk in this thread has only one (which doesn't work)
[8525, TyTN, MDA Vario II, JasJam General] trjons:
Not sure why but my u key requires a hard press that other keys don't.

I tried compressed air but it didn't help.

Its the only button I have trouble with.

Pressing it lots of times doesn't help either.

Suggestions?
[8525, TyTN, MDA Vario II, JasJam General] Neverwork:
i have the same problem with my "E" Key

if anyone has a fix for it thatd be wonderful

because im so accustomed to pressing a key, and hearing the click, so i go on to hit the next one

just to realize my E didnt hit

:(
[8525, TyTN, MDA Vario II, JasJam General] joao.miguel:
I have the same problem with "O" key lol

Still havent found a solution.
[8525, TyTN, MDA Vario II, JasJam General] KHB:
I am having the same problem with "u" key. Tried running the cingular keyboard fix. Didn't work:(
[8525, TyTN, MDA Vario II, JasJam General] trjons:
Never occurred to me that it might be software related. I just assumed it was hardware.
[8525, TyTN, MDA Vario II, JasJam General] Neverwork:
lol the cingular keyboard fix doesnt fix that

its for if you install say, the official Dopod WM6 Rom to your Cingular 8525, the key layout isnt the same, so the fix puts the right layout number into the registry

no software can correct a hardware problem
[8525, TyTN, MDA Vario II, JasJam General] Neverwork:
Its not software related

it seems to happen on the keys that you press the most

U E O -- all vowels used quite often
[8525, TyTN, MDA Vario II, JasJam General] Neverwork:
well i guess ill take one for the team

ill be the b*tch to disassemble it haha

ill get back to ya in a few
[8525, TyTN, MDA Vario II, JasJam General] trjons:
crap.

oh well...if my phone is toast I may as well upgrade to the kaiser...
[8525, TyTN, MDA Vario II, JasJam General] Neverwork:
so yeah f*ck that lol

i tried to get the back face plate off...

and now the slider thingy to the battery cover is stuck in place?

anyone have that problem? and how can i get that completely closed? coz it looks like the back just didnt close all the way?
[8525, TyTN, MDA Vario II, JasJam General] Neverwork:
UPDATE :)

i took it completely apart - took the keyboard out - the circuit board and the membrane - blew on it

put my phone back together

and viola! the E works FINE! =)

theres a fix...but no more warranty lol
[8525, TyTN, MDA Vario II, JasJam General] joao.miguel:
i'm gonna waint another year so my warranty voids and then take it apart lol

Thanks for the info :D
[8525, TyTN, MDA Vario II, JasJam General] Neverwork:
Correction

it was working perfectly for a few hours

and right back to the harder presses...grr

ive already taken it apart 5 times since yesterday lmao

because first the PTT button didnt line up right

then the Camera MACRO adjustment wasnt aligned

then the back cover release didnt line up

then the bottom clip wouldnt snap into place...but that was because of the back cover release

so yeah now ive got it working as if i had never touched it....lmao

buuttt...im thinking of taking it all apart and spraypainting it Flat Black? :)

i think thatd look pretty dayumm sweeet
[8525, TyTN, MDA Vario II, JasJam General] trjons:
interesting...

the entire keypad is a single strand.

I thought about popping up a single key but they are connected.
[8525, TyTN, MDA Vario II, JasJam General] Neverwork:
yepp - one large membranee
[8525, TyTN, MDA Vario II, JasJam General] MikeChannon:
This practical solution applies only to those situations where one or a few keys are unresponsive.

It DOES NOT apply to a general unresponsiveness of the keyboard where all keys are slow to respond or "laggy" (this would more likely be a software related problem/low memory/too many running progs etc).

Right...... for a long time I have meant to investigate the keyboard and its problem keys.

It has all become clear.

The keyboard does NOT use a conductive rubber membrane - Which would in my view have been better, though would not have the key press clicks.

The Keyboard does use small isolated concave metal disks, stuck on a white plastic film that in turn sticks to the board.

The major problem with metal is the oxidation layer that forms on the surface. Repeated pressing of the keys may keep the oxides away but not reliably.

So if you are brave you can peel back the sticky white film with the disks on it - at least until you get to the problem key and clean the disk. A wipe will not be enough, you will need to use something more abrasive and be careful not to get greasy fingers on the sticky film. A fiddly and rather tricky job - but possible.

I advise you NOT to peel the white plastic layer completely off. If you do you may find it difficult to line it up accurately after cleaning!!

I suggest cleanning the contacts (including the disks with a small piece of steel wool.

I will not supply a dismantling guide here. There are plenty around. See my signature website for links to some and the Service Manual.

Mike
[8525, TyTN, MDA Vario II, JasJam General] trjons:
Screw it.

i'll just buy a Kaiser.
[8525, TyTN, MDA Vario II, JasJam General] sumdiv:
What happens when my space bar V,G,T key don't work. I have replaced both the keyboard and the membrain. The same keys are still not working. I was wondering if it could be the ribbon cable, so I replaced that to. Same story, no keys working. Now where should I start looking? It has not gotten wet nor have I dropped it.

Thanks
[8525, TyTN, MDA Vario II, JasJam General] trjons:
Does opening up the phone void the warranty?

How would HTC know?
[8525, TyTN, MDA Vario II, JasJam General] ultramag69:
Yes, there is a "Void if removed" sticker covering a screw you need to remove. Check out the HTC service manual (use the search function) or go to Mike Channon's web page. You'll find HOW to take your Hermes apart and put back together again, and as a bonus, it may still work....:p

Cheers...:D
[Android Q&A, Help & Troubleshooting] PauloHmendes:
Olá galera, já instalei várias roms estrangeiras do LG p715 no meu p716, se alguém estiver um link "válido" da rom p716 ORIGINAL v10_00.kdz peço que me mandem. **Muito Obrigado**:)

Translation:

Hello guys, have already installed several foreign roms LG p715 p716 in my if anyone is a link "valid" the rom p716 ORIGINAL v10_00.kdz ask you to send me. **Thank you so much**

4. Use o idioma Inglês.

Entendemos que com todas as diferentes nacionalidades, nem todo mundo fala Inglês bem, mas por favor tente. Se você for realmente incapaz de postar em Inglês, use um tradutor online. Você é livre para incluir sua mensagem original em sua própria língua, abaixo a tradução em Inglês. (Essa regra abrange as suas mensagens, entradas de perfil e assinatura). Por favor, também postar no fórum correto. Obrigado.