I have managed to compile (from source) and install CM7.2 on my HTC dream, but my questions below are related to Android:
1. Is there a way to find out which packages (.apk) were installed on my system and if so, how do I do that?
2. Is there a way to find out each package dependencies (I need to figure out this as I am bent on removing the vast amount of guff installed on the phone - I won't need 90% of this stuff)?
3. Similarly to 2 above - is there a way to look at dependencies of a package not yet installed on my system (i.e. the .apk file)?
4. How do I actually remove a package for good from the system?
5. Similarly to 3 above, how do I actually install a package from within the root system - I know I can do this via adb, but is there a way to do this inside the, say, command line terminal?
6. Is there a way to alter (understand remove) certain program permissions which I could see "granted" to a particular program/package? I know there are various ways to look at these, but I wish to remove permissions I am not happy being granted to that particular program/package.
And one last a bit more advanced query: I would like to build a single package from the source tree and then install the resulting .apk file on my system.
Basically, I will try to upgrade a package with a new revision and add a few patches to the package source of my own before compiling it and building it again.
I usually build the whole lot (all packages + the rootfs image itself) with "mke bacon", but if I want to alter the source and build a single package how do I do that?
I am not very familiar with the Android make system, so I don't want to go heads-first into something and make a real mess of it.
Thanks a lot for any assistance given.
Small addition as apparently I cannot post a reply (too few posts) in this thread: http://forum.xda-developers.com/showthread.php?p=9055790#post9055790
Question to ezTerry (if he is reading this!): the advice given in that post above was absolutely splendid! I followed it religiously and it worked an absolute treat!
There is one exception though - I've LOST all of my IMEI, IMEI SV and Baseband information after applying these fixes. As soon as I installed the radio updates and then installed my newly-compiled kernel + CM7.2 (successfully!) I then checked the above fields from Settings and they were all gone!
After a while, the baseband, IMEI and IMEI SV appeared, but the IMEI and IMEI SV stuff have now different values than what I've had previously (I've had T-Mobile IMEI, now it appears that I was "assigned" O2 IMEI & IMEI SV values - very bizarre!).
Is this something I need worry about and (I don't yet have a sim card, but I plan to get one soon after I fix my phone), more importantly, how the hell do these IMEI numbers appeared on my phone - where did they came from?!
josh36 said:
Small addition as apparently I cannot post a reply (too few posts) in this thread: http://forum.xda-developers.com/showthread.php?p=9055790#post9055790
Question to ezTerry (if he is reading this!): the advice given in that post above was absolutely splendid! I followed it religiously and it worked an absolute treat!
There is one exception though - I've LOST all of my IMEI, IMEI SV and Baseband information after applying these fixes. As soon as I installed the radio updates and then installed my newly-compiled kernel + CM7.2 (successfully!) I then checked the above fields from Settings and they were all gone!
After a while, the baseband, IMEI and IMEI SV appeared, but the IMEI and IMEI SV stuff have now different values than what I've had previously (I've had T-Mobile IMEI, now it appears that I was "assigned" O2 IMEI & IMEI SV values - very bizarre!).
Is this something I need worry about and (I don't yet have a sim card, but I plan to get one soon after I fix my phone), more importantly, how the hell do these IMEI numbers appeared on my phone - where did they came from?!
Click to expand...
Click to collapse
Any takers?
@1 Check out the respective directories, i.e. for system apps /system/app
@2 Trial and Error, or someone might have made such a list for your device already
@3 No simple way, you would have to look through the decompiled code i guess
@4 Remove the apk from the folder (for example /system/app) and reboot your device, after wards you might have to clean up some extra folders, i.e. settings of that app. (you can use SD Maid from my signature for that)
@5 Some can just be installed the usual way, by opening it. Some .apk files have to be put in the system folders, afterswards reboot and the app should be "installed". To put those apps there use a rootcapable file explorer of your choice. To edit /system you will need to remount it as it is read only by default, you can do that through command line, but most good file explorers have an option for that.
@6 Yes thats possible, there was an app to do that, just not sure what it was called... It is very likely though, that those apps will not work correctly or just FC.
For the make system, if you just change a package, and build again, it will most likely just rebuild the changed files. I'm not so sure either though... damn make system can be pretty messy... and get upset real fast if you change something ;-).
Dark3n said:
@1 Check out the respective directories, i.e. for system apps /system/app
Click to expand...
Click to collapse
Yep, that indeed helped - I didn't realise that the .apk files are "intact" and do not behave in the "standard" (in Linux terms) way a "package" behaves - the app is "installed" as soon as .apk is placed in /data/app or /system/app. The PacketManager does the rest on reboot.
It also cleans up the mess "automagically" if I delete .apk file and reboot, which is nice.
Dark3n said:
@2 Trial and Error, or someone might have made such a list for your device already
Click to expand...
Click to collapse
Yeah, that's a real bugger - I can't see a way of finding the dependencies, but I haven't looked properly at "pm" (the Package Manager command line tool) - maybe I could use something there.
Dark3n said:
@6 Yes thats possible, there was an app to do that, just not sure what it was called... It is very likely though, that those apps will not work correctly or just FC.
Click to expand...
Click to collapse
A very simple example will issustrate my point - my calendar application is installed and needs some sort of GOOGLE_MAIL and access to the internet permissions, neither of which I am happy to grant, because 1) I won't be using online calendars; and 2) I won't use (google) mail.
The truth is, I deliberately did not install any google apps as I won't be using any of them - ever!
Now, every time I boot up and look at my log files with logcat I see a bunch of error messages that this application (the calendar) needs a bunch of permissions which do not exist (naturally, as I haven't installed a single google app on my phone).
So, I wish to wipe out these permissions from the calendar so that logcat is not filled with junk every time I start my phone.
As I already pointed out above, there are also some installed apps who are listed to "need" permissions I am not happy to grant - like the internet access to calendar for example (there are more apps, but I think you get the point).
Dark3n said:
For the make system, if you just change a package, and build again, it will most likely just rebuild the changed files. I'm not so sure either though... damn make system can be pretty messy... and get upset real fast if you change something ;-).
Click to expand...
Click to collapse
Yeah, that was my plan B - there must be another - easier - way though.
I wish to update a lot of stuff (I will be recompiling/refreshing existing packages as well as adding new things I developed for "standard" Linux), but with this Android make system I am blind - it is very different to what I am used to in the Linux world.
To top it all off, I can't post in any of the devs forums yet as I do not have 10 posts!
Further to my previous post - I just found out a superb article about stripping out Android and removing unnecessary packages from it - http://wiki.cyanogenmod.com/wiki/Barebones
It lists various dependencies and shows what could be deleted and what cannot be - what I wanted really.
My only remaining problem - at least for now - is the making of specific packages without building the whole image.
Related
Hi to everybody, I come from the BADA subforum, and there is a new project trying to port Android to samsung Wave phone.
Devs have some issues, we are in the last steps and here is a summary
will want to note that the kernel has been confirmed as able to boot into android homescreen when flashed though JTAG
we're modifying the init scripts to boot it from sdcard
the device is accessible from adb how ever the Android system services such as zygote are restart looping
i *think* i managed to execute standard boot on init.rc with adb interface, zygote and android services appear to be stuck in a restart loop:
http://code.google.com/p/badadroid/source/detail?r=192
EDIT: would like to note that while "VIBETONZ" is appearing on the log, the phone is not vibrating, nothing is appearing on the display either. If possible i'd like a check on my kernel sources Oleg. EDIT AGAIN: the phone does actually vibrate, my bad
line 3150ish you can see the zygote service and various others getting killed and restarting.
EDIT2: another debug log extracted using "adb bugreport" (very large, will want to download in order to view)
http://code.google.com/p/badadroid/source/detail?r=193
http://badadroid.googlecode.com/svn/trunk/adb logs/bugreportnb190511.log
EDIT3: it's possible that the restart loop is caused by lack of memory, this could be caused by the memory mapping of the current bootloader we're using, will have to ask rebellos and srg about that.
added a log to googlecode for procedure to boot kernel using init.rc with adb interface working ( i'm not exactly sure why this works) i may upload the zImage i'm using for this, but it'll only work if you partition your memory card in the correct layout and format.
http://code.google.com/p/badadroid/source/detail?r=194
http://code.google.com/p/badadroid/d...511v2&can=2&q=
Click to expand...
Click to collapse
We need some ideas, or whatever you can provide with your knowledge to help us in this project.
more info: http://forum.xda-developers.com/showthread.php?t=1012856&page=100
Thanks to everybody.
hi to everybody
need help, please!
anybody?
I will take a look later on this evening and see if I can tell anything.
Your kernel seems to work, most of your issues in the log that was posted in my thread come from the ramdisk and system build. Until you work at those for a bit, I don't think you're going to know where to place the blame for issues until you're clean.
For the VM crash loop:
Take all of the non critical apps and gapps out of /system/apps (stuff like vending, maps, touchwiz and so on.)
And see what you get. If you can't solve it that way, then try to do:
adb pull /dbdata/databases/com.android.providers.settings/settings.db settings.db
And see what you get. If its there, it's corrupt. If it isn't, check to make sure the directory is getting created. You can also get someone to pull settings.db from a similar device (i9000?) and try to push it to yours.
But that's only the first of your problems. You have some bad lines in init.rc (your rild daemon isn't configured correctly amongst other things), and a few things missing in /system/bin and /system/lib (calls to missing things). If you aren't using an extract of system.img from the sdk, you probably should. Then you can load in libs one at a time in a clean and controlled environment.
BTW: What Android system are you using? What device did it come from? If you built it from source, seriously, try using an emulator image first.
spacemoose1 said:
Your kernel seems to work, most of your issues in the log that was posted in my thread come from the ramdisk and system build. Until you work at those for a bit, I don't think you're going to know where to place the blame for issues until you're clean.
For the VM crash loop:
Take all of the non critical apps and gapps out of /system/apps (stuff like vending, maps, touchwiz and so on.)
And see what you get. If you can't solve it that way, then try to do:
adb pull /dbdata/databases/com.android.providers.settings/settings.db settings.db
And see what you get. If its there, it's corrupt. If it isn't, check to make sure the directory is getting created. You can also get someone to pull settings.db from a similar device (i9000?) and try to push it to yours.
But that's only the first of your problems. You have some bad lines in init.rc (your rild daemon isn't configured correctly amongst other things), and a few things missing in /system/bin and /system/lib (calls to missing things). If you aren't using an extract of system.img from the sdk, you probably should. Then you can load in libs one at a time in a clean and controlled environment.
BTW: What Android system are you using? What device did it come from? If you built it from source, seriously, try using an emulator image first.
Click to expand...
Click to collapse
It is possible it was not made clear, its a 2.2 stock ROM being ported from the Samsung Galaxy S to the Samsung Wave (formerly a BadaOS device). It is also being booted off of SD as apposed to OneNand. It uses a patched version of the SBL from the galaxy S but when Android is flashed to Nand it can boot fine (although problems are had initializing the Modem).
sabianadmin said:
It is possible it was not made clear, its a 2.2 stock ROM being ported from the Samsung Galaxy S to the Samsung Wave (formerly a BadaOS device). It is also being booted off of SD as apposed to OneNand. It uses a patched version of the SBL from the galaxy S but when Android is flashed to Nand it can boot fine (although problems are had initializing the Modem).
Click to expand...
Click to collapse
You need to compare logs from system booted from nand and from sd. Whatever errors are the same don't matter. Its the different ones that will tell you more.
But you're crashing right now because some line of code somewhere in your build is looking for a database and can't find it. If it doesn't do that when installed to nand, then your problem is that directories that the system creates to host configs and module parts aren't getting created at boot.
The modem issue, (if the error in logcat is the same whether the system booted or not, haven't seen both) looks to be a radio interface layer problem, your rild daemon isn't loading (check /system/bin/ for "rild") and make sure the line in init rc that starts it is correct.
spacemoose1 said:
some line of code somewhere in your build is looking for a database and can't find it.
Click to expand...
Click to collapse
It's a strange problem, as using the extracted system.img from the Android emulator as filesystem the above error disappears - with the same kernel/initramfs/init.rc (obviously other errors appear but the services seems to be stable).
I think we can forget the ril related errors now (I commented out the service in my build together with the DR daemon) as we have no modem driver yet ...
hey, just testing out a few of the stripped down ICS 4.0.3 roms. theyre really great, but the devs always take out the htc_ime. i really like to have that cause of the language selection.
i know i saw somewhere a .zip to flash it back in, but i cant find it now that i need it! anyone know where it is??
thanks!
I heard that HTC_IME is not compatible with ICS...
It is compatible - im using it with no problems. Even HTC trace works fine.
What you need to do (sorry i cant make a flashable zip)
download the zip from HERE
Extract the zip file
Push the HTC_IME.apk (from app folder) to /system/app (I use ES file explorer) and change permissions to RW-R-R
Then push the libs (from lib folder) to /system/lib and change permission to RW-R-R - there should be 5 in total.
Then reboot. I also wiped cache & Dalvik cache just to be sure.
NOTE: if you are using virtuous inquision the lib files are already present. This is the rom im using and since it is based from the HTC leak, the dev has not removed the libs. So all you need is the HTC_IME.apk into /system/app and then you should be able to select the HTC touch input in the keyboard list.
I hope this helps
Doesn't work. Even after copying all the files to their proper folders, ensuring permissions are correct, and wiping cache and dalvik... It still force closes as soon as Touch Input is selected. Just tried it on CM7.
I'm going to try to investigate this problem and see what I can come up with. I know everybody used to say that Clicker.apk was needed. But if you look at most of the ROMs out there, you'll see that they somehow use the HTC_IME keyboard without having Clicker.apk. So what's missing?
Edit: I feel like I'm going to give myself a headache trying to figure this out. The logcat for the FC said (amongst other things) that there is a ClassNotFoundException for KeyboardSettings. There's also a lot of ActivityThread errors which don't really mean much to me. A Google search revealed that it may be related to the AndroidManifest.xml in the APK file, but unfortunately it's not a standard XML file (try opening it to see what I mean). Not to mention, the APK is obviously fine, because I pulled it right from the ROM.
So basically, we need to somehow figure out what other files are needed by HTC_IME.apk, besides the libraries mentioned already in this thread. I assume that it worked for beady_uk because the ROM he was using already had the rest of the required files without him knowing. I'm going to continue looking to see if I can find more information, but I would definitely appreciate if anybody has any technical input into this situation. I can provide logcat information if needed.
Gamesoul Master said:
Doesn't work. Even after copying all the files to their proper folders, ensuring permissions are correct, and wiping cache and dalvik... It still force closes as soon as Touch Input is selected. Just tried it on CM7.
I'm going to try to investigate this problem and see what I can come up with. I know everybody used to say that Clicker.apk was needed. But if you look at most of the ROMs out there, you'll see that they somehow use the HTC_IME keyboard without having Clicker.apk. So what's missing?
Edit: I feel like I'm going to give myself a headache trying to figure this out. The logcat for the FC said (amongst other things) that there is a ClassNotFoundException for KeyboardSettings. There's also a lot of ActivityThread errors which don't really mean much to me. A Google search revealed that it may be related to the AndroidManifest.xml in the APK file, but unfortunately it's not a standard XML file (try opening it to see what I mean). Not to mention, the APK is obviously fine, because I pulled it right from the ROM.
So basically, we need to somehow figure out what other files are needed by HTC_IME.apk, besides the libraries mentioned already in this thread. I assume that it worked for beady_uk because the ROM he was using already had the rest of the required files without him knowing. I'm going to continue looking to see if I can find more information, but I would definitely appreciate if anybody has any technical input into this situation. I can provide logcat information if needed.
Click to expand...
Click to collapse
I believe that you have mis-read the 1st post.
The OP asked how to re-add the HTC_IME to a stripped down rom that the dev had removed.
This is what i have done and it worked - possibly because the roms are sense-based framework.
You have tried to install this on CM7 with is CM based framework so i think you will need more 'files' but that is beyond my knowledge.
Sorry i cant help further
You are correct. I was in a deep search for anything revolving around installing it, so I missed that part. I saw your post (which is the only place I've seen anybody mention installing those lib files), and I guess that caused further oversight on my part.
I do imagine this may not work on all the stripped down ROMs though, if any of the cooks stripped their ROMs like I stripped my old Win98 PC that had a 1GB hard drive in it... that is to say, remove every possible file that wouldn't cause stability issues
I used the ROM from here. (LG Optimus T (P509): January 8: Build 7/Final)
I have no Google Play store icon anywhere. I see the Google Play process running in the background.
but have no way to get it to show up. This on a fresh ROM, all User data, Cache, and all that cleared.
Any help on this would be nice.
Would of asked on that post where I got the ROM. but I don't have the patience to or any thoughts about other post to make to meet the requirements to even post there.
Tried without flashing the Google Apps and with the google apps they list there.
Flashing Google Apps just crashes things like the browser. it wont even open.
Not flashing Google Apps I can use the browser just fine. but I still see "Google Play Services" Running. So that tells me google play is installed.
So don't have to flash it. but cant open it even if i did or not. no Icon anywhere no matter what I try. I been wanting to use CM10. but this issue keeps me going back to CM7.
Thanks in advance to the person with the answer.
TroyFoxxin said:
I used the ROM from here. (LG Optimus T (P509): January 8: Build 7/Final)
I have no Google Play store icon anywhere. I see the Google Play process running in the background.
but have no way to get it to show up. This on a fresh ROM, all User data, Cache, and all that cleared.
Any help on this would be nice.
Would of asked on that post where I got the ROM. but I don't have the patience to or any thoughts about other post to make to meet the requirements to even post there.
Tried without flashing the Google Apps and with the google apps they list there.
Flashing Google Apps just crashes things like the browser. it wont even open.
Not flashing Google Apps I can use the browser just fine. but I still see "Google Play Services" Running. So that tells me google play is installed.
So don't have to flash it. but cant open it even if i did or not. no Icon anywhere no matter what I try. I been wanting to use CM10. but this issue keeps me going back to CM7.
Thanks in advance to the person with the answer.
Click to expand...
Click to collapse
Are you sure you are using the right GApps package? That's Rasheds ROM you're referring to using. Build 7 is Android 4.1.2. Check this link here. And some of the problems you may be experiencing could be due to a faulty installation because of limited system space. You may want to review the LG Optimus One FAQ too.
shinobisoft said:
Are you sure you are using the right GApps package? That's Rasheds ROM you're referring to using. Build 7 is Android 4.1.2. Check this link here. And some of the problems you may be experiencing could be due to a faulty installation because of limited system space. You may want to review the LG Optimus One FAQ too.
Click to expand...
Click to collapse
There is more then enough internal space. (150MB Free after Gapps Flashed).
I tried again with the Gapps for 4.1.2. At the time my post I re flashed the ROM but left it out. I didn't flash it.
When I tried again. I got the Updating Android. but still no Play Store Icon. However it did not break my home or other buttons.
and browser still working. but again. no Play Store icon.
I checked the FAQ. Currently i see nothing there to give hints. I got more then enough free space. I've flashed ROMs on this phone dozens of times so I know the whole wiping of cache and data and all that between each ROM.
TroyFoxxin said:
There is more then enough internal space. (150MB Free after Gapps Flashed).
I tried again with the Gapps for 4.1.2. At the time my post I re flashed the ROM but left it out. I didn't flash it.
When I tried again. I got the Updating Android. but still no Play Store Icon. However it did not break my home or other buttons.
and browser still working. but again. no Play Store icon.
I checked the FAQ. Currently i see nothing there to give hints. I got more then enough free space. I've flashed ROMs on this phone dozens of times so I know the whole wiping of cache and data and all that between each ROM.
Click to expand...
Click to collapse
You have to trim the Rom, there's not enough SYSTEM space for the Rom and Gapps..this has been discussed time and time again on rashed thread(cm10)..There's a tool ( Oone Rom editor that will help you do this) This is why you have the bugs that your facing.
3ncrypt3d_Droid said:
You have to trim the Rom, there's not enough SYSTEM space for the Rom and Gapps..this has been discussed time and time again on rashed thread(cm10)..There's a tool ( Oone Rom editor that will help you do this) This is why you have the bugs that your facing.
Click to expand...
Click to collapse
I used that program already. looking at all that it would only show.
the math dont even come to half of what the phone memory is.
TroyFoxxin said:
I used that program already. looking at all that it would only show.
the math dont even come to half of what the phone memory is.
Click to expand...
Click to collapse
The system partition has nothing to do with the devices memory. These devices have a 190 MB system partition, this is where Android gets installed. What you are referring to is the user data partition which is 200 MB, while the device has 415 MB+- RAM ( memory ). Unless you are using Android 4.2.2, the only way to see how much space is on the system partition is with a third party app, with ADB, or with a Terminal Emulator app on the device. The math isn't adding up because you don't understand it, that's why I pointed you to the FAQ thread.
I wrote OOne ROM Editor. I haven't put hundreds, yes hundreds, of hours in to it's development just for general pleasure. It was written for a specific purpose, to trim ICS and newer ROMs for devices with small or limited system partitions.
shinobisoft said:
The system partition has nothing to do with the devices memory. These devices have a 190 MB system partition, this is where Android gets installed. What you are referring to is the user data partition which is 200 MB, while the device has 415 MB+- RAM ( memory ). Unless you are using Android 4.2.2, the only way to see how much space is on the system partition is with a third party app, with ADB, or with a Terminal Emulator app on the device. The math isn't adding up because you don't understand it, that's why I pointed you to the FAQ thread.
I wrote OOne ROM Editor. I haven't put hundreds, yes hundreds, of hours in to it's development just for general pleasure. It was written for a specific purpose, to trim ICS and newer ROMs for devices with small or limited system partitions.
Click to expand...
Click to collapse
I dont know what to try to trim with that program. i dont know what half them apps do.
Like Exchange2.apk. I don't know what that is. Which are some of the key things i can trim?
Also, Telling me how many hours you put into a program and that i dont understand something not going to be on my good side. So i missed something, big deal. I just got off a anxiety attack. and i was needing was a simple answer. doing a search for "LG P509 No Playstore Icon" was getting me no where and i didnt want to have to search page by page of the 487 pages of the ROMs post to find clues.
TroyFoxxin said:
I dont know what to try to trim with that program. i dont know what half them apps do.
Like Exchange2.apk. I don't know what that is. Which are some of the key things i can trim?
Click to expand...
Click to collapse
The help docs in OOne ROM Editor's thread list some of the known files that can be removed from and or moved around, ie; converted to user app, in the ROM.
shinobisoft said:
The help docs in OOne ROM Editor's thread list some of the known files that can be removed from and or moved around, ie; converted to user app, in the ROM.
Click to expand...
Click to collapse
just never mind. i dont need the stress right now, ill just stay with CM7.
Every time i try to Build the ROM and put it on the phone CWM just says its bad.
TroyFoxxin said:
just never mind. i dont need the stress right now, ill just stay with CM7.
Every time i try to Build the ROM and put it on the phone CWM just says its bad.
Click to expand...
Click to collapse
Are you getting an "assert() failed" message? If you are using CWM 5.0.2.7 Touch, it will only allow you to install P500 ROMs. OOne ROM Editor has the ability to remove the "assert()" statement from the ROM's updater-script to prevent that particular error from happening. Before building the ROM, go to the Tools->Build submenu and select the Build Options command. Check the checkbox for "Remove updater-script 'assert()' statement". Then build the ROM.
And stress... You call editing a ROM stress? Try writing the code for OOne ROM Editor Or better yet, play with live electricity :silly: - oh wait I do that already since I am an electrician... DOn't get frustrated by it. Sit back relax and soak in some of the knowledge around here.
shinobisoft said:
Are you getting an "assert() failed" message? If you are using CWM 5.0.2.7 Touch, it will only allow you to install P500 ROMs. OOne ROM Editor has the ability to remove the "assert()" statement from the ROM's updater-script to prevent that particular error from happening. Before building the ROM, go to the Tools->Build submenu and select the Build Options command. Check the checkbox for "Remove updater-script 'assert()' statement". Then build the ROM.
And stress... You call editing a ROM stress? Try writing the code for OOne ROM Editor Or better yet, play with live electricity :silly: - oh wait I do that already since I am an electrician... DOn't get frustrated by it. Sit back relax and soak in some of the knowledge around here.
Click to expand...
Click to collapse
Again bad, day. had a Anxiety attack. haven't slept. I havent played with Android as often as other things. I am also a Electronic person. Soldering Caps and so on on motherboards all the time. So please dont talk like that to people you dont know. they may have plenty of knowledge. but maybe having whats called a short fuse kinda day.
Also I did do "Remove updater-script 'assert()' statement". And i get no error from OOne ROM Editor it was in CWM it would just say it was bad, or say nothing at it would just restart CWM. Ill try again when Im better. Right now my phone has CWM 5.0.2.0, So ill change that as well when i try again.
but right im turning in for the night.
TroyFoxxin said:
Again bad, day. had a Anxiety attack. haven't slept. I havent played with Android as often as other things. I am also a Electronic person. Soldering Caps and so on on motherboards all the time. So please dont talk like that to people you dont know. they may have plenty of knowledge. but maybe having whats called a short fuse kinda day.
Also I did do "Remove updater-script 'assert()' statement". And i get no error from OOne ROM Editor it was in CWM it would just say it was bad, or say nothing at it would just restart CWM. Ill try again when Im better. Right now my phone has CWM 5.0.2.0, So ill change that as well when i try again.
but right im turning in for the night.
Click to expand...
Click to collapse
Sorry you're having a bad day. Rest assured, if I was talking down to you, there wouldn't be any smilies. I was just expressing that you weren't the only one out there with stress in their life, and some of us have loads of it. On that note, I'm not one of the many teenagers around here. So I'm not talking down to you, but out of experience. My teenage years were gone 23 years ago. Apparently it was take outta context, Sorry.
I think the issue I mentioned for CWM 5.0.2.7 is a shared issue with CWM 5.0.2.0, but I can't say for sure as I don't recall ever using CWM 5.0.2.0. I wasn't suggesting changing to the CWM I mentioned, was asking if that was the one you were/are using, which you've now stated you aren't. There error I was referring to would have been from CWM after flashing or trying to flash a ROM.
shinobisoft said:
Sorry you're having a bad day. Rest assured, if I was talking down to you, there wouldn't be any smilies. I was just expressing that you weren't the only one out there with stress in their life, and some of us have loads of it. On that note, I'm not one of the many teenagers around here. So I'm not talking down to you, but out of experience. My teenage years were gone 23 years ago. Apparently it was take outta context, Sorry.
I think the issue I mentioned for CWM 5.0.2.7 is a shared issue with CWM 5.0.2.0, but I can't say for sure as I don't recall ever using CWM 5.0.2.0. I wasn't suggesting changing to the CWM I mentioned, was asking if that was the one you were/are using, which you've now stated you aren't. There error I was referring to would have been from CWM after flashing or trying to flash a ROM.
Click to expand...
Click to collapse
Can that program add apps? If so or not. maybe I can edit the zip directly. but is it possible to port the old music player in Gingerbread to JB. I don't like Apollo. or would it just be better to remove Apollo and find something I like in Play store when i make this work?
And should i try to use CWM 5.0.2.7 instead, and try again?
EDIT: Says I have the latest according to this.
EDIT 2: just ROM Manger being a butt. going to the site directly. I see CWM 5.0.2.7 as the latest.
TroyFoxxin said:
Can that program add apps? If so or not. maybe I can edit the zip directly. but is it possible to port the old music player in Gingerbread to JB. I don't like Apollo. or would it just be better to remove Apollo and find something I like in Play store when i make this work?
And should i try to use CWM 5.0.2.7 instead, and try again?
EDIT: Says I have the latest according to this.
EDIT 2: just ROM Manger being a butt. going to the site directly. I see CWM 5.0.2.7 as the latest.
Click to expand...
Click to collapse
Yes apps can be added, but only as User Apps. Select "User Apps" in the treeview on the left. Then right click on the listview on the right and select the "Add apps" command item. A file dialog will appear. Multiple file selection is allowed.
You can remove Apollo. I prefer Google Play Music myself.
For your recovery. CWM 5.0.2.7 will only allow installing P500 ROMs. I do prefer the touch version of CWM, and since P509 is identical to P500, it's really not an issue other than baseband which is solved with a flashable patch. I really cannot recommend a recovery as we all have different likes/dislikes/usage patterns. I would recommend not using ROM Manager to install a recovery. It's been known to be faulty with our devices. Theres always ADB and fastboot or another one of my tools, Android Flash Recovery. There are several other apps around XDA that can do this also.
shinobisoft said:
Yes apps can be added, but only as User Apps. Select "User Apps" in the treeview on the left. Then right click on the listview on the right and select the "Add apps" command item. A file dialog will appear. Multiple file selection is allowed.
You can remove Apollo. I prefer Google Play Music myself.
For your recovery. CWM 5.0.2.7 will only allow installing P500 ROMs. I do prefer the touch version of CWM, and since P509 is identical to P500, it's really not an issue other than baseband which is solved with a flashable patch. I really cannot recommend a recovery as we all have different likes/dislikes/usage patterns. I would recommend not using ROM Manager to install a recovery. It's been known to be faulty with our devices. Theres always ADB and fastboot or another one of my tools, Android Flash Recovery. There are several other apps around XDA that can do this also.
Click to expand...
Click to collapse
Ill just leave it be then. Its always worked for me. if there was a problem it was with the ROM.
I haven't tried Google Play music before. but is it possible to port the music player from Gingerbread to JB?
but I'm getting the jiffs of that program. I just need to play with it. some things I converted to User apps never loaded at all.
So I need to play with what I can put in User data that will still work. but none the less i been getting the builds to install.
And even show Play Store again.
Just need to mess with what works and dont in User data.
-Edit-
I tried to Make LatinIME Smaller and convert it to Userdata in the build options but every build has no keyboard support.
TroyFoxxin said:
Ill just leave it be then. Its always worked for me. if there was a problem it was with the ROM.
I haven't tried Google Play music before. but is it possible to port the music player from Gingerbread to JB?
but I'm getting the jiffs of that program. I just need to play with it. some things I converted to User apps never loaded at all.
So I need to play with what I can put in User data that will still work. but none the less i been getting the builds to install.
And even show Play Store again.
Just need to mess with what works and dont in User data.
-Edit-
I tried to Make LatinIME Smaller and convert it to Userdata in the build options but every build has no keyboard support.
Click to expand...
Click to collapse
Is there anyway you can post the updater-scipt from one of the builds you've made with OOne ROM Editor where you've modified the LatinIME.apk and specified to install as a User App? The updater-script is located in the /META-INF/com/google/android folder in the output/build ROM.
One thing to note tho, build options are reset after every build.
shinobisoft said:
Is there anyway you can post the updater-scipt from one of the builds you've made with OOne ROM Editor where you've modified the LatinIME.apk and specified to install as a User App? The updater-script is located in the /META-INF/com/google/android folder in the output/build ROM.
One thing to note tho, build options are reset after every build.
Click to expand...
Click to collapse
I noticed that it resets everytime. so i been ontop of that. I check both boxes in the build options before I build them.
I did read also not to delete LatinME.apk. and use the editor. But i know the LatinME is a nice chunk of Memory.
So to make it smaller and usable in User apps is plus to make the important things I need working.
-Edit-
I haven't been saving the bad builds. that attachment was for a new build I haven't tried yet.
and I just did. now keyboard working. But I think that build I didn't tell it to put Latin in User apps that time.
But I did use the editor. So I don't know.
TroyFoxxin said:
I noticed that it resets everytime. so i been ontop of that. I check both boxes in the build options before I build them.
I did read also not to delete LatinME.apk. and use the editor. But i know the LatinME is a nice chunk of Memory.
So to make it smaller and usable in User apps is plus to make the important things I need working.
-Edit-
I haven't been saving the bad builds. that attachment was for a new build I haven't tried yet.
and I just did. now keyboard working. But I think that build I didn't tell it to put Latin in User apps that time.
But I did use the editor. So I don't know.
Click to expand...
Click to collapse
I can't tell what you installed as user apps from the updater-script, but there were apps installed to the user ( data ) partition. And the assert() statement is missing from the script, so I know that option was checked in the Build Options.
The reason I say not to manually move it is because the LatinIME Keyboard Editor should be used to edit it's dictionaries. Once you press the "Apply" button in the LatinIME Keyboard Editor, it removes the LatinIME.apk from System Apps and actually puts it in the apps Recycle Bin. I use the list of files in the Recycle Bin as a filter of files not to include when building the ROM. LatinIME Keyboard Editor also looks in the Recycle Bin for the LatinIME.apk if it can't find it in System Apps but it assumes that it's deleted so it won't do anything.
I am actually working on OOne ROM Editor right now. So you can be on the lookout for an update
shinobisoft said:
I can't tell what you installed as user apps from the updater-script, but there were apps installed to the user ( data ) partition. And the assert() statement is missing from the script, so I know that option was checked in the Build Options.
The reason I say not to manually move it is because the LatinIME Keyboard Editor should be used to edit it's dictionaries. Once you press the "Apply" button in the LatinIME Keyboard Editor, it removes the LatinIME.apk from System Apps and actually puts it in the apps Recycle Bin. I use the list of files in the Recycle Bin as a filter of files not to include when building the ROM. LatinIME Keyboard Editor also looks in the Recycle Bin for the LatinIME.apk if it can't find it in System Apps but it assumes that it's deleted so it won't do anything.
I am actually working on OOne ROM Editor right now. So you can be on the lookout for an update
Click to expand...
Click to collapse
Well I got everything to work. Keyboard, Play Store, etc. But not sure ill stick with trying to put JB on the phone.
Its really slow. Unless more free space on the system partition would allow it to run faster.
Would your OOne ROOM Editor work on Any rom Like a CM7 Rom? or just JB ones? if not would you consider support for other roms?
I haven't tried, but figure I would ask.
TroyFoxxin said:
Well I got everything to work. Keyboard, Play Store, etc. But not sure ill stick with trying to put JB on the phone.
Its really slow. Unless more free space on the system partition would allow it to run faster.
Would your OOne ROOM Editor work on Any rom Like a CM7 Rom? or just JB ones? if not would you consider support for other roms?
I haven't tried, but figure I would ask.
Click to expand...
Click to collapse
OOne ROM Editor is just for ICS and JB ROMs. It's really not needed for Android versions prior to 4.0.
Inspired by SimpleSU (I really love it), which is not so simple to use after all (mainly because it is intended for shipping in the ramdisk or the likes), and closed source, I made my own superuser implementation, µSuper.
I provide it to you, mainly so you can give me some feed back or just try it, whatever you prefer.
Just like SimpleSU it uses a text file.
Unlike SimpleSU this text file contains the UIDs of the apps, not their package names (which makes µSU less vulnerable to frauds). It is also not on the hard to access /system partition, but in the private data directory of µSU, and globally set to read-only.
With only 309 SLOC (app and binary combined) I think it is safe to say that it is really tiny.
The source code is publicly available on Github.
@MarcoToo I know this has been here for ages but I'm amazed this thread has less than 600 views and You've only got 3 thanks... It's my favourite SuperUser app as it uses next to no resources. The only thing wrong is that it won't work with anything above JellyBean 4.2.2 which is a shame; I don't supposed you plan to support further Android versions? or is it easy for me to build this to support further versions?
Thanks anyway, all the people not using this are missing out
HTCDreamOn said:
@MarcoToo I know this has been here for ages but I'm amazed this thread has less than 600 views and You've only got 3 thanks... It's my favourite SuperUser app as it uses next to no resources. The only thing wrong is that it won't work with anything above JellyBean 4.2.2 which is a shame; I don't supposed you plan to support further Android versions? or is it easy for me to build this to support further versions?
Thanks anyway, all the people not using this are missing out
Click to expand...
Click to collapse
theres a reason to it, because the developer hasn't kept the app updated, while supersu is updated almost weekly. The lastest SuperSU has way more support as to this because it is outdated, and in beta at that. Safer and more compatible alternative would be SuperSU
Aiko0923 said:
theres a reason to it, because the developer hasn't kept the app updated, while supersu is updated almost weekly. The lastest SuperSU has way more support as to this because it is outdated, and in beta at that. Safer and more compatible alternative would be SuperSU
Click to expand...
Click to collapse
I see your point but I still stick with this SU: SuperSU is closed source, and even Koush' open source Superuser app is theoretically less secure than this, due to the whole granting mechanism; with µSuper the user must explicitly select which apps gain su access whether they ask for it or not, and the code is so small there's little which could go wrong. Each to their own, though , I use this because the Desire Z is lacking in memory and CPU power so every little helps, but on a more powerful device it wouldn't bother me.
HTCDreamOn said:
I don't supposed you plan to support further Android versions? or is it easy for me to build this to support further versions?
Click to expand...
Click to collapse
I think the location for app files has changed from /data/data to something else. Since µSuper's su binary uses a hardcoded path to the permissions file (using an environment variable would be quite unsafe), the only things you would have to change are the targetSdkVersion in the app's AndroidManifest.xml and (if it did change) the path to the permissions file in su.c.
MarcoToo said:
I think the location for app files has changed from /data/data to something else. Since µSuper's su binary uses a hardcoded path to the permissions file (using an environment variable would be quite unsafe), the only things you would have to change are the targetSdkVersion in the app's AndroidManifest.xml and (if it did change) the path to the permissions file in su.c.
Click to expand...
Click to collapse
Forked and synced let's see if I can fix this for later versions I don't suppose you'd know how to implement this into a ROM (using source code)? From the README I assume I'm allowed to
Hello, i bring to you the QuickRemote app for your AOSP Marshmallow rom, CM13 or any rom based on CM13 (Resurrection Remix, Bliss, AICP), you may ask, "Why would i want QuickRemote on my AOSP rom if MM has native IR support and Peel or Anymote works without all this mambo jambo?
Well, even though what i just said is true, no remote controller app has the learning method enabled, even on a stock rom, only QuickRemote can enable the IR receiver to learn a controller that does not appear on the device/manufacturers list.
So, that's the reason we want QuickRemote to work on our AOSP rom.
So, before anything, i would like to thank @hikarisei23 because in a comment of his post HERE i found the files for QuickRemote to work on MM wich leads to the second person i want to thank wich is @syndre who on said comment, posted the files that worked on MM, also @KronicSkillz who helped a lot to troubleshoot and also confirmed that the method i'm posting here works.
Well, this is it, after personally testing with: Resurrection Remix, AICP and Bliss, all of them MM amd CM13 based, all of them with the stock kernel and Lambda Kernel i'm confident enough to post it here, days of testing and troubleshooting and 3 different roms later.
So first, the mandatory disclaimer, im not responsible for any problem that may result from using my method and the files i'm providing you, either with your phone or your self-esteem, it's your responsibility to read, re-read and only do what you are comfortable with.
What you will need:
1. - The phone, this only has been tested with Lg G2 and Lg G3, this may or may not work on another LG phone with IR, you can try, but at your own risk.
2. - The Rom, this only have been tested with AOSP roms either CM13 or CM13 based roms, again, you can try in another rom but at your own risk.
3. - Obviously a Custom Recovery (twrp, cwm, philz)
4. - The three zips im leaving at the end of the post, QRemote_AOSP_MM.zip Fix_Part1.zip and Fix_Part2.zip.
5. - Maybe necessary or not, depending on your rom, Universal init.d from Playstore HERE and Selinux Mode Changer from HERE.
6. - Root Access.
Ok, once you checked and have everything needed, we have to make a little prep on your Rom before starting to flash the zips.
Rom Preparation 100% Needed
You need to set Selinux to permissive, here is where you may or may not need Selinux Mode Changer, First go into "About Device" on your phone settings and in the bottom you will find an indicator for Selinux state, if its "Permissive" you are good to go, some Roms and Kernels have this set to Permissive by default, if it's Enforcing, search in your Rom or Kernel settings, some of them have an option to set it to Permissive, if your rom does not have any option to change it, you will need Selinux Mode Changer, you install it and set Selinux to permissive, after reboot you can check in About Device again to see if it succeded, if it does not work, try again and check the original post, most of the answers are there, i cant give support for this app, also, this app needs root rights, and preferably two reboots after setting Selinux to Permissive.
Next you need to have init.d support, again, some roms have it, but at least for the test that me and the other users did, even though you are pretty sure init.d is enabled it's better to just install Universal init.d from the Play Store and enable init.d manually after doing so, reboot the system at least two times and grant Root access.
Installation!
Now we are ready to start flashing, reboot into recovery and RECOMMENDED, do a Nandroid Backup just in case, but at the moment no boot loops or any other problems had raised from flashing this, but again, just in case. After that, flash the first file: QRemote_AOSP_MM.zip, reboot your system and let it settle for a bit, 1 minute at least.
Now is the part where almost everyone has problems, you have to check in your Sdcard root for a log file named Qremote.log, if the file is there, it means init.d is enabled and in the file it will say if Selinux is Ok, if you don't have the file, check back the first two prep steps and try again.
Now if everything is going ok, is time for the second file, Fix_Part1.zip, reboot and let the system settle again, you may have some force close errors from QuickRemote or QuicksetSDK, its ok, you can try and check if QuickRemote is working, in allmost every case it will not work just yet, but you may have some luck.
Now, is the time to flash the third file, Fix_Part2.zip, again, reboot and let the system settle, now, you should have a working QuickRemote app on you AOSP MM Rom.
This are the steps, if you need more information about what all of this is doing and why you need Selinux and init.d, also why you need to flash 3 files, you can read the troubleshooting section where i explain what i understand about it.
TROUBLESHOOTING
Well, if you are here, it means that this didn't work as planned, so lets make this like a FAQ so you just search your problem and get the answer for it.
P.- I can't see QuickRemote on my app drawer. A: be sure that QuickRemote.apk is not showing as "com.lge...." and has the default green Android icon on your app drawer, sometimes and for reasons unknown to me, this happens for the first day or so, it will automatically change to QuickRemote and it will have the correct icon at least 5 hours after you installed it, it can take more time. A2: Maybe the flashing proccess was not successful, re-flash the file, it will automatically delete previously flashed files and install a new copy of them.
P. - I get force close messages for QuickRemote or QuicksetSDK after completing the proccess. A: try to run QuickRemote after the system settled, most of the times is 1 minute, in some roms and for reasons unknown to me, this messages will appear at boot but after the system settled, you will be able to run QuickRemote without any problem.
P. - QuickRemote opens up but no manufacturers are showing and it also gets really slow. A: this problem shows when either QuicksetSDK is not correctly installed or Selinux is not set to permissive, the solution for the first problem is in my 2 part fix, the version of Selinux included in the first zip, works great with MM but for some reason it will not work out of the box, i dont know if it's missing some files but it may or may not even show under system apps list on your settings menu, what my 2 part fix does is that, deletes the version of QuicksetSDK that the first flash installs and installs a temporary copy of QuicksetSDK wich i believe, writes information needed for QuicksetSDK to work properly, but this newer temporary QuicksetSDK apk, will allmost never work on MM, you can try but allmost every time it will not work, it will constantly force close, so the second fix zip, will delete this temporary QuicksetSDK and the folder it creates in your Sdcard root and install the previous version of QuicksetSDK again, and now, if everything went well, it will work as it's supposed to, i really dont know why exactly, but it works.
A2: the first thing you will notice when you switch to MM is that allmost every app will ask for permission to your Sdcard or camera or microphone wich in LP was not doing, since 4.3 Google is taking extra steps to ensure that you and your information are better protected one of this steps is Selinux (Security Enhanced Linux) wich, for putting it in simple terms, is like a sandbox for your system, only some trust-signed apps can get out of that sandbox and copy files etc... Into your system, those not-so privileged apps cant output anything outside the sanbox and thats why you need to disable or "set to permissive" Selinux, so QuicksetSDK can make the changes necessary for QuickRemote to do its work, it's true that now your system is in a degree "more vulnerable" but if you are a user of this forum, the odds to install something that will damage your system or jeopardize your information are minimal, you need to be really silly to fall for those "your system has problems" or "your battery is gonna explode if you don't install this app" ads that appear on your phone on the daily basis, so, dont worry, but at the same time, just be carefull and have some common sense, if there is a way for this to work with Selinux set to Enforcing, i will update it in the same second.
P. - QuickRemote force closes whenever i try to open it. A: this is caused by either a bad zip flash, or problems with Selinux or init.d, follow the previous answer and the first installation steps again.
P. - I can see QuickRemote and QuicksetSDK on my apps list, no force closes but still no manufacturers. A: Be sure init.d is enabled, i had problems with Roms that had "native init.d support" and emulated init.d will not work, the only way i got no problems with this was with Universal init.d, install that even though you are "pretty sure" your rom supports init.d, the 10QuickRemote.sh script on your init.d tries to get your country to see if you will use the app in, either Korean or any other supported language, it will also give some permissions to a file and it will check if Selinux is Permissive and finally, it will log this to a file called Qremote.log on the root of your Sd, if you have problems and you cant see the file, the problem is 99% most of the time, init.d.
P.- I don't want to flash three files, isn't there a simpler way? A: Unfortunately no, at this moment and after A LOT of testing etc... This is the only effective way i found.
P. - I'm afraid to set Selinux to permissive and leave the door open for all kind of bad ju ju and stuff to invade my sacred Android system, what can i do? A: Skip this hole thing, at the moment, the only way to make this work on AOSP MM is by doing the previous, just be careful, get some common sense and everything will be just fine.
Well, thats all i can think of right now, if you have suggestions, problems or a better way to make this work, please tell me in the comments or PM me, i'm glad to help as far as i can, i hope this helps, i leave you with the needed files and proof that it works.
QRemote_AOSP_MM.zip - MEGA - DRIVE
nice you started a new thread!
Ive been messing around with this a lot the last few days and I have been seeing the same fix you were talking about by swapping the quickset apks back and forth. Ive put together a zip for flashing that I think would make things as easy as possible for people to get the list to show up.
The script in this one sets the correct permissions for everything on flash. It will instal;l the L version of Quickset, which doesnt show the manufactures list. The M quickset apk also gets flashed but i just put it in /system, so its there and can be moved easily. When you boot the first time after flashing, the the ROM uses the L version. All you should have to do then is use a file manager app to move the QuicksetSDK.apk from /system to /system/app/QuicksertAPK/ replacing the one thats there already. Set perms to 644 if necessary. Now wipe tjhe app data for quickset app, forcing the new one to restart, you dont even have to reboot.
Last thing is you have to delete the Quickset Settings folder made by the lollipop quickset. The Marshmallow version will make a working folder of its own the first time you start Quick Remote.
I like your idea to make fixes in separate flashes, that is probably easier
link to my 01262016.AOSP-6.x.x-M_LGQuickRemote_v4.50.19.zip on MEGA
it's working great!
tnx!
i just ran a nightly update on mokee6 which is cm13 similar and i had to reflash the fixes to get it working again and strange thing is i noticed lib folder is gone from quickset sdk folder but it's working
another thing i noticed is quickset sdk is not in my apps list so don't use that as a way to test if it's working either see if manufactures show up after waiting a bit or try the learning feature to test app functionality
im using d852 with stock mokee6 kernel btw of anyone's wondering and yes i have all apps selected
The mult-zip installation also worked out here on BrokenOS. Remote is working fine.
Originally I used "init.d scripts support" app to handle the init.d file. Worked just fine, BTW. Reason for that is I wasn't sure what would happen if I used Universal Init.d with Broken as it has a directory full of tweaks.
On later examination I see that each script needs to be enabled before it will run (via Settings. True/false values are then looked up in a cfg file).
So I reckon I can safely use Universal Init.d.
LG G3 D851, BrokenOS MM ROM, Tapatalk 4.9.5
can i delete universal init.d after enabling it?
@syndre well yes, i think that flashing zip it's pretty straight forward, your new method is simpler but i think that just flashing and not having to deal with system folders and permissions is better for the less tech savvy, but a little more hideous because of the various reboots
smolchy said:
it's working great!
tnx!
Click to expand...
Click to collapse
You're welcome
@marcdw yes, the thing with Universal init.d is that it really enables init.d at boot, Resurrection Remix and AICP also have their individual init.d scripts and they run, i don't know why the QuickRemote script does not run, and Universal init.d does not mess with the existing scripts, so it's not harmful for the system and runs the script at boot and thats what we want
@KronicSkillz well, I'm glad it works, i used the QuicksetSDK thingy because it seemed like it was the only consistent thing, sometimes the Quickset Setup folder would not show, or it will show with the first QuicksetSDK but at least at first QuicksetSDK would not show in the apps list, after the first fix it would and it would show again, i will put it in the post, thanks for the feedback
Roi007leaf said:
can i delete universal init.d after enabling it?
Click to expand...
Click to collapse
I think you can i but i have not tested that, if you do, tell me what that did to update the post, i keep Universal init.d for other scripts that i have installed so i need it, if you only use it for QuickRemote i dont think you'll have a problem
ok checked.. safe to uninstall...
---------- Post added at 04:56 PM ---------- Previous post was at 04:19 PM ----------
btw.. i did all the steps and i can see manufactures but the IR itself doesnt work.. the devices wont react to it..any solution?
Roi007leaf said:
ok checked.. safe to uninstall...
---------- Post added at 04:56 PM ---------- Previous post was at 04:19 PM ----------
btw.. i did all the steps and i can see manufactures but the IR itself doesnt work.. the devices wont react to it..any solution?
Click to expand...
Click to collapse
What variant/rom you have?
Jc_master said:
What variant/rom you have?
Click to expand...
Click to collapse
LG d855 32GB 3GBRAM RR 5.6.2 android 6.0.1
Roi007leaf said:
LG d855 32GB 3GBRAM RR 5.6.2 android 6.0.1
Click to expand...
Click to collapse
Try force closing QuicksetSDK and delete its data, re-flash the fix part 2 and see in that helps, also i think that you need Universal init.d again, the Qremote.log updates at every boot and it wont update if Universal init.d is not installed
Thanks for creating a new thread, I've been busy for a while and won't be able to do much androidy stuff for now.
I have seen an interesting changelog in cyanogenmod that creates selinux policies for QuicksetSDK, but they haven't merged it yet. So fingers crossed that it'll be merged ASAP so things will be easier for us
link: http://review.cyanogenmod.org/#/c/127449/
hikarisei23 said:
Thanks for creating a new thread, I've been busy for a while and won't be able to do much androidy stuff for now.
I have seen an interesting changelog in cyanogenmod that creates selinux policies for QuicksetSDK, but they haven't merged it yet. So fingers crossed that it'll be merged ASAP so things will be easier for us
link: http://review.cyanogenmod.org/#/c/127449/
Click to expand...
Click to collapse
I hop they do, and thank you for your work also
No quicksetsdk in apps but I saw its library in systrm/app and the permissions are correct.. Any idea ?
Roi007leaf said:
No quicksetsdk in apps but I saw its library in systrm/app and the permissions are correct.. Any idea ?
Click to expand...
Click to collapse
Did you flash both fix zips? The need for those 2 fix zips is because the QuicksetSDK that comes in the Qremote_AOSP_MM.zip works with Marshmallow but by itself it will not create some required files in the system and it will most likely not show in the apps list, the QuicksetSDK that comes in fix part1 most of the times wont work on Marshmallow but it will create some necessary files on the system it will show in the apps list but it force closes, and the QuicksetSDK in the fix part 2 is the same as in Qremote_AOSP_MM.zip but this time it has everything needed to work properly and it now should show in apps list allmost every time, so you need to follow the steps again closely and i recommend that before you flash the fix part 2, you go into your apps list and force close QuicksetSDK and delete its data, also report if you get Qremote.log on the root of your Sd and what this shows if its there
Jc_master said:
@KronicSkillz well, I'm glad it works, i used the QuicksetSDK thingy because it seemed like it was the only consistent thing, sometimes the Quickset Setup folder would not show, or it will show with the first QuicksetSDK but at least at first QuicksetSDK would not show in the apps list, after the first fix it would and it would show again, i will put it in the post, thanks for the feedback
Click to expand...
Click to collapse
ya i was using quickset sdk check (apps list) to see if it was working too until i realized it's working without showing up this time