Related
Hello everyone!
Finally, I am satisfied with my chacha. I was constantly shifting between stock custom rom and cm roms. In stock rom everything works but automatic backlight settings are just terrible (especially dim threshold and keyboard light settings) and status bar is bigger than in cm roms (32px vs 25px). Cm roms have all of this but there are other things that still need improvement (front cam, some stability issues etc.). Therefore I decided to create my own mod of stock rom. It is based on Europe RUU 1.3.3 android 2.3.3. I couldn’t find anywhere 2.3.5 Europe rom but to be honest I don’t see any difference between the two. There are two versions:
1. Full sense rom: Link
What is different: rooted, added busybox, support init.d, dta2sd included (you need to partition your sd to ext2 or ext3 after installation and enter dta2sd commands from terminal emulator – google for the commands if you don’t know them), changed the ugly calculator app, added file explorer, added latest play store, Flash player 11 is working. I haven’t removed any apps because in this version I wanted to leave that to the user according to his/her own preferences. Status bar is smaller (more space on the screen) and I themed it a little, removed charging icon (I know that it is charging because phone’s led is orange ). Automatic brightness is tweaked (added lower brightness level, lowered the max brightness of the f button, and added one level for the keyboard lights (sometimes, in stock roms, I couldn’t see my keyboard clearly and the damn lights just wouldn’t turn on so I had to do this tweak as well). And rom is fully deodexed.
2. Stripped rom (no sense): Link
What is different: rooted, added busybox, support init.d, dta2sd included (you need to partition your sd to ext2 or ext3 after installation and enter dta2sd commands from terminal emulator – google for the commands if you don’t know them), changed the ugly calculator app, added file explorer, added latest play store, removed sense, added widget locker, holo launcher, removed a lot of bloatware (at least, bloatware for me), f button is not assigned (I’ll leave that to the user, I use it to turn my screen off but didn’t changed it to this since several people reported issues). Same automatic backlight and status bar tweaks like in the sense rom and it is also deodexed.
3. Stripped rom (odexed): Link
What is different: Same as in stripped rom with the exeption of these: odexed (now 120mb free out of the box), status bar icons have an ICS look and color (wifi, signal, data, bluetooth etc.), notification toggles app added (fully functional and works great, just in the settings set it as an on-going notification and as old in order to be always on top; it has many different icons and styles and colors are changable as well, really nice app), fb button is set to turn screen off, dta2sd not included, different backlight values.
Automatic backlight and status bar tweak for odexed version: Link
Automatic backlight and status bar tweak (sense and stripped deodexed): Link
Flash Player 11: Link
Instructions:
1. Reboot into recovery; wipe data/factory reset; mounts and storage/format system; install from sd card; choose and install your rom; reboot your phone; finish your first boot setup.
2. Reboot into recovery; install from sd card; choose and install backlight.zip; reboot your phone.
3. Install flash player apk; reboot phone.
That’s it. Hope that someone will like it.
Sorry for the poor screenshots.
Regards
P.S. I am not going to support these mods. Everyone is invited to use them and do with them whatever you want. So please don’t ask me does it support this, does it support that, can you do this, can you do that. For me, it is perfect and I don’t need to do or change anything. Everything is working for me. I just wanted to share it with you. I hope that you can understand this.
Edit: I used this guide (thanks kylon) to improve wifi signal range and it worked for me, so I am going to share these settings with you. Mke sure you do this with your WiFi off. Here is what you have to do:
1. Copy your calibration file (found in proc in the root of your phone) to the sd card (it is best to do all steps with root explorer) and download from the attachments framework.jar (here is a link for an odexed version - extract jar and odex files) and symlinkv2.zip.
2. Move the calibration file to system/etc and set permissions as they are set in the screenshot.
3. Reboot into recovery and install symlinkv2.zip.
4. Open calibration file in system/etc (again, best with root explorer) and change this line: rssi_offset=0 into this: rssi_offset=-30
Delete created bak file if you are using root explorer.
5. Copy downloaded framework.jar (I already modified it according to the offset - 30, and if you are using odexed version copy both jar and odex files) to system/framework and set permissions according to the screenshot. Reboot your phone.
6. Done.
This trick did wonders for me and my wifi, hope it will help you as well. If it doesn't, try different values both in calibration file and framework.jar according to the original thread.
Cheers.
Looks noice
Is it faster/smoother than the stock rom? I would go back to the stock rom if it wasn't so hard to configure and it wasn't so damn sluggish compared to CM7/CM9.
ethancottier said:
Looks noice
Is it faster/smoother than the stock rom? I would go back to the stock rom if it wasn't so hard to configure and it wasn't so damn sluggish compared to CM7/CM9.
Click to expand...
Click to collapse
Every rom that I use is fast enough for me. Even the unmodified stock. I just wanted to get rid of some apps that are obsolete for me, and I needed to improve backlight settings because when it is night the original settings don't dim the lights enough which really hurts my eyes and I hate that because I have to manually dim. In this rom I don't have that issue. Lights dim automatically.
Although, I found out today that there is an issue with the dta2sd, or maybe the kernel itself. DTa2sd moves my apps and dalvik to sd-ext, clockworkmod creates a backup of sd-ext in a backup folder, and when I restore it my rom just will not mount my sd-ext on boot after that, thus I need to do a fresh install. I would appreciate if someone has an idea why this happened? It is not an issue for me, since I am going to use this rom for a while, but I would like to fix it for the others. When I don't use dta2sd there are no issues. I looked in init.rc in ramdisk, but couldn't find anything unusual. This happened to me with Void rom as well, so I really don't know where to start regarding this.
Regards
Edit: I have been using recovery for a different phone. I just realized this and now, with the proper recovery, everything is restoring fine.
didije said:
Every rom that I use is fast enough for me. Even the unmodified stock. I just wanted to get rid of some apps that are obsolete for me, and I needed to improve backlight settings because when it is night the original settings don't dim the lights enough which really hurts my eyes and I hate that because I have to manually dim. In this rom I don't have that issue. Lights dim automatically.
Although, I found out today that there is an issue with the dta2sd, or maybe the kernel itself. DTa2sd moves my apps and dalvik to sd-ext, clockworkmod creates a backup of sd-ext in a backup folder, and when I restore it my rom just will not mount my sd-ext on boot after that, thus I need to do a fresh install. I would appreciate if someone has an idea why this happened? It is not an issue for me, since I am going to use this rom for a while, but I would like to fix it for the others. When I don't use dta2sd there are no issues. I looked in init.rc in ramdisk, but couldn't find anything unusual. This happened to me with Void rom as well, so I really don't know where to start regarding this.
Regards
Click to expand...
Click to collapse
I don't know about data2SD, but I use link2SD, and that works perfectly but with the stock rom, you have to format the sd-ext partition in ext2 rather than ext4, and you can't do it with clockworkmod either, cos it doesn't format it properly :/ you have to use a tool like gparted (if you're a linux user) or some windows/mac equivalent to format it properly
Wow that does look pretty nice.thanks man.
ethancottier said:
I don't know about data2SD, but I use link2SD, and that works perfectly but with the stock rom, you have to format the sd-ext partition in ext2 rather than ext4, and you can't do it with clockworkmod either, cos it doesn't format it properly :/ you have to use a tool like gparted (if you're a linux user) or some windows/mac equivalent to format it properly
Click to expand...
Click to collapse
Link2sd works well. Just tested it. Thanks! I don't have the time to look deeper into the issue with dta2sd..
john9 said:
Wow that does look pretty nice.thanks man.
Click to expand...
Click to collapse
Thank you. In a couple of weeks I will tweak the backlight settings little more, and maybe build a similar 2.3.5 rom (if I find a RUU).
Cheers
Stripped with full stock Facebook Button Functionallity
Great work. This is a solid setup. Thanks for the hard work.
I appreciate that you left the F-Button unassigned for the end user, but is there a way to get back to stock functionallity using your Stripped Rom?
Thank you.
maxwellsk said:
Great work. This is a solid setup. Thanks for the hard work.
I appreciate that you left the F-Button unassigned for the end user, but is there a way to get back to stock functionallity using your Stripped Rom?
Thank you.
Click to expand...
Click to collapse
Unzip Stripped Rom, add attached apks to system/app and attached chacha-keypad.kl (unzip the keypad file) to system/usr/keylayout. Zip it and flash it. Let me know if it works.
Cheers.
didije said:
Unzip Stripped Rom, add attached apks to system/app and attached chacha-keypad.kl (unzip the keypad file) to system/user/keylayout. Zip it and flash it. Let me know if it works.
Cheers.
Click to expand...
Click to collapse
Thank you so much for the exceptionally quick response. Unfortunately I ran into an error. Let me walk you through what I did.
1. Dowloaded Sripped Rom, and all the files in the previous post.
2. I unzipped the Rom on my desktop
3. I inserted each of the files in their respective folders
4. Zipped the Rom back up
5. Transferred to SD
6. Booted to Recovery mode and tried to flash.
Here is what I got ....
CWM-based Recovery v5.0.2.7
-- Installing: /sdcard/Stripped-Chacha_1-3-3.zip
Finding update package...
Opening update package...
Installing update ...
Installation aborted.
maxwellsk said:
Thank you so much for the exceptionally quick response. Unfortunately I ran into an error. Let me walk you through what I did.
1. Dowloaded Sripped Rom, and all the files in the previous post.
2. I unzipped the Rom on my desktop
3. I inserted each of the files in their respective folders
4. Zipped the Rom back up
5. Transferred to SD
6. Booted to Recovery mode and tried to flash.
Here is what I got ....
CWM-based Recovery v5.0.2.7
-- Installing: /sdcard/Stripped-Chacha_1-3-3.zip
Finding update package...
Opening update package...
Installing update ...
Installation aborted.
Click to expand...
Click to collapse
That is weird. I just tested it, and it worked for me. Maybe you zipped it with high compression or sth. Try with normal compression. If that doesn't work, I will upload zip for you later today. I use recovery 5.0.2.8, but I don't think that it matters.
Edit: Here is the link - Link
Flash Player Stopping
Stripped down ROM is great - now have more room for downloading apps.
One problem I've come across on this ChaCha is that Flash Player stops working (returns to home screen) after around 2 seconds of playing anything.
Anyone else had a similar problem?
didije said:
That is weird. I just tested it, and it worked for me. Maybe you zipped it with high compression or sth. Try with normal compression. If that doesn't work, I will upload zip for you later today. I use recovery 5.0.2.8, but I don't think that it matters.
Edit: Here is the link - Link
Click to expand...
Click to collapse
That got it! I'm sooooo happy!!! Thanks!! It is perfect!!
maxwellsk said:
That got it! I'm sooooo happy!!! Thanks!! It is perfect!!
Click to expand...
Click to collapse
That's great. Glad I could help.
Regards
scgellion said:
Stripped down ROM is great - now have more room for downloading apps.
One problem I've come across on this ChaCha is that Flash Player stops working (returns to home screen) after around 2 seconds of playing anything.
Anyone else had a similar problem?
Click to expand...
Click to collapse
As you can see from the screenshot below I don't have that issue. Try different flash player for armv6 devices. There are few, just google it.
dta2sd
Little suggestion. If you are planning to use this rom for a longer time, after your setup, copy your data from your sd card to your computer, go into clockworkmod recovery, in advanced options partition your sd card (I set sd-ext to 256, don't need more) and reboot. After that download terminal emulator from play store. In terminal type this:
su (then press enter and allow superuser permissions)
a2sd reinstall (enter and wait for your phone to reboot. It will take some time)
After it is booted enter this:
su (enter)
a2sd cachesd (press enter and wait for your phone to reboot. It will take some time).
The end result you can see in the attached screenshot. After installing all my apps I still have over 120mb free.
Of course, after everything is done copy your data back to sd card.
Regards
Added wifi tweak to the first post. It works for me, hopefully it will work for you as well.
Regards
languages included in europe rom
What languages are included in this ROM?
Thx!
Thanks for this rom, great daily use
Great Rom, Thank you!
This is the best ChaCha rom I have used so far. Everything works great super fast flash even works!
YouTube can play 240p with no lag, any higher and it will.
BBC iplayer crashes but I have yet to find a rom that bbc iplayer will work on when it comes to the ChaCha.
Perfect rom but can u create a RTL fix for arabic support ?
thanks.
I posted this in the I9300 forum but i got no responses....
I suppose this could work on all 1gb ram devices since these are non device specific tweaks,just optimised for the S3.
Intro:
Hi all...
I got a bit tired of restoring all of my build.prop and init.d tweaks every time i flashed i rom so i made a handpicked collection of the tweaks i use.
Since this may be useful to others aswell i though i need some testers to confirm everything goes ok after this...
Can anyone help me?
When it's confirmed working i'll update this to a full thread with how to and everything. [done already because of low demand.]
By the way,can't test myself because i already have those enabled.
I just want to see if the cwm file installs correctly and if values and permissions are set right.
Instructions
Flash through recovery and delete dalvik and cache.
Please do post back,I need feedback since this is the first flashable mod i created.
Also make a backup before installing,i don't know if this will work correctly on your S3.
Thanks!
Finally it is reccomended to use this to have full effect and eliminate redraws.
Fast.Simple.Working.
Just use the instructions and you're done.
http://forum.xda-developers.com/showthread.php?t=1869663
P.S. Nothing of this is mine,i just made the package becaue i don't want to install them manually every single time.
All credits go to their owners.
Anyone tested it?
Seems to make things a bit smoother.
Sent from my SGH-T999 using xda app-developers app
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
For those that want a rooted stock ROM, without having to use Kingoroot, here you go.
jy190_rooted.zip
This is the JY 1.90 ROM + SuperSU installed, no garbage, no Kingoroot or whatever. I took the 1.90 Joying image, unpacked it, manually installed SuperSU (basically duplicating what the SuperSU installation script does), and repackaged it. It is running on my Jeep HU right now and SuperSU is fully functional.
I've made two harmless changes to stock that you can change after flashing:
Default Bluetooth device name is "JoyingJeep" instead of "CAR-KIT" (tired of changing it manually to the name I want)
Default Timezone is America/Detroit instead of China/Shanghai (same reason as above)
Prerequisite: Probably you will want to get the JY1.90 ROM from Joying directly, and update your HU with it because Joying includes an updated MCU image. I am *not* including the MCU image here because one of you is going to flash it onto the wrong hardware and brick your HU. I am only providing the ROM image, just like Malaysk does.
1. To install, first extract dupdate.img from the zip.
2. Copy dupdate.img to the root directory of a USB stick or SD card
3. Enter recovery, flash. If coming from stock you can probably flash without clearing all. If coming from Malaysk you might want to clear all first.
Understand what you are doing. Read Malaysk's thread about flashing, and read all of his warnings, as they all apply here.
Thanks to Malaysk for his ROM and all of the other tweaks he's done. If you want something beyond stock, try his.
Thanks to Joying for making this unit, there is nothing else like it on the market. As long as continues to work, I'll continue to be very happy with it.
Thanks once more to Joying for being (so far) pretty friendly to the DIY/modding/hacking crowd. I've never seen a company so open with flashing and modding, and continuing to update their own firmware for their customers. It is nice to see, so let's not abuse it. Mod responsibly.
There won't be any additional support from me. This is a rooted stock ROM, that's it.
Edit 5-Nov-2016, some FAQ:
Unpacking and repacking a rockchip ROM
Adding root to the ROM
Make it easy on yourself: ROM kitchen by da_anton
it starts video playback on boot. its not your rom, its the original as well, but weird.
---------- Post added at 07:41 AM ---------- Previous post was at 07:28 AM ----------
What tool you use to unpack rom?
Hi!!! Thanks for your work I'm going to wipe my ROM (I think there's some garbage after deleting Kingoroot) and put your ROM into my unit.
Great work
wskelly said:
For those that want a rooted stock ROM, without having to use Kingoroot, here you go.
jy190_rooted.zip
This is the JY 1.90 ROM + SuperSU installed, no garbage, no Kingoroot or whatever. I took the 1.90 Joying image, unpacked it, manually installed SuperSU (basically duplicating what the SuperSU installation script does), and repackaged it. It is running on my Jeep HU right now and SuperSU is fully functional.
I've made two harmless changes to stock that you can change after flashing:
Default Bluetooth device name is "JoyingJeep" instead of "CAR-KIT" (tired of changing it manually to the name I want)
Default Timezone is America/Detroit instead of China/Shanghai (same reason as above)
Prerequisite: Probably you will want to get the JY1.90 ROM from Joying directly, and update your HU with it because Joying includes an updated MCU image. I am *not* including the MCU image here because one of you is going to flash it onto the wrong hardware and brick your HU. I am only providing the ROM image, just like Malaysk does.
1. To install, first extract dupdate.img from the zip.
2. Copy dupdate.img to the root directory of a USB stick or SD card
3. Enter recovery, flash. If coming from stock you can probably flash without clearing all. If coming from Malaysk you might want to clear all first.
Understand what you are doing. Read Malaysk's thread about flashing, and read all of his warnings, as they all apply here.
Thanks to Malaysk for his ROM and all of the other tweaks he's done. If you want something beyond stock, try his.
Thanks to Joying for making this unit, there is nothing else like it on the market. As long as continues to work, I'll continue to be very happy with it.
Thanks once more to Joying for being (so far) pretty friendly to the DIY/modding/hacking crowd. I've never seen a company so open with flashing and modding, and continuing to update their own firmware for their customers. It is nice to see, so let's not abuse it. Mod responsibly.
There won't be any additional support from me. This is a rooted stock ROM, that's it.
Click to expand...
Click to collapse
wskelly said:
This is the JY 1.90 ROM + SuperSU installed, no garbage, no Kingoroot or whatever. I took the 1.90 Joying image, unpacked it, manually installed SuperSU (basically duplicating what the SuperSU installation script does), and repackaged it. It is running on my Jeep HU right now and SuperSU is fully functional.
Click to expand...
Click to collapse
Great idea and thanks for the work! Thought of that myself! Could you perhaps tell me how you made that ROM? How did you manage to extract the img file and put everything back together? Did you use imgRePackerRK? Thanks!
da_anton said:
Great idea and thanks for the work! Thought of that myself! Could you perhaps tell me how you made that ROM? How did you manage to extract the img file and put everything back together? Did you use imgRePackerRK? Thanks!
Click to expand...
Click to collapse
Yes, I used imgrepackerrk on Linux. After dumping the contents you are left with more img files. These are all block storage. In Linux, it is possible to mount these img files and manipulate their contents just like any block device.
Afterward, you can repack everything again with imgrepackerrk.
Sent from my Moto G using Tapatalk
wskelly said:
[*]Default Bluetooth device name is "JoyingJeep" instead of "CAR-KIT" (tired of changing it manually to the name I want)
.
Click to expand...
Click to collapse
hey I also named my Joying that
This is great! If I hadn't install the Sept Joying image last weekend, I would have totally installed this. Thank so much!
One suggestion though, if you decide to make another one at some point, you might want to install the xposed framework (I did this via flashfire) and appsettings 1.13. I can provide a link to each, that are known good, as the 'regular' framework and App Settings 1.10 (from xposed directly) doesn't work. I know it's designed as 'stock' but at minimum the framework just makes sense, I think.
wskelly said:
Yes, I used imgrepackerrk on Linux. After dumping the contents you are left with more img files. These are all block storage. In Linux, it is possible to mount these img files and manipulate their contents just like any block device.
Afterward, you can repack everything again with imgrepackerrk.
Sent from my Moto G using Tapatalk
Click to expand...
Click to collapse
Thanks! Great work! Got it working today and made my first ROM based on yours. I removed some apps which are just wasting RAM and I don't need.
Greetings,
I am very new to these head units got my first one 2 months ago. been reading and learning a lot here. I have a KGL and installed this rom, its working great and its a bit visually different then the one's I have used for KGL. Glad to know we have options on roms and tweaking we can do.
I do have a small annoyance that I hope some one can help me with. I had hoped this rom would solve it but unfortunately not. The radio RDS feature, on all the roms I have used the problem stays the same. I am in the US and its set to Europe RDS PTY code. So I can see the all the station and song information but the Station genera is wrong. like country music stations listed as pop and rock stations listed as Drama. I figure their is a file that the radio ap references to know what label to use and display. I have searched for this file or ap location but have had no luck in finding were it would be located. Can anyone point me in the right direction on how to possible fix it so the radio displays the correct station type? Sorry to hijack a thread but my post count is not high enough to allow me to start my own. search has not helped. Thanks all.
da_anton said:
Thanks! Great work! Got it working today and made my first ROM based on yours. I removed some apps which are just wasting RAM and I don't need.
Click to expand...
Click to collapse
Awesome! Keep tinkering! This is how everyone gets started. ?
Sent from my Moto G using Tapatalk
Hi !, I'm not 100% sure but try to change radio reg at the Factory options.....
pinkpanther28 said:
Greetings,
I am very new to these head units got my first one 2 months ago. been reading and learning a lot here. I have a KGL and installed this rom, its working great and its a bit visually different then the one's I have used for KGL. Glad to know we have options on roms and tweaking we can do.
I do have a small annoyance that I hope some one can help me with. I had hoped this rom would solve it but unfortunately not. The radio RDS feature, on all the roms I have used the problem stays the same. I am in the US and its set to Europe RDS PTY code. So I can see the all the station and song information but the Station genera is wrong. like country music stations listed as pop and rock stations listed as Drama. I figure their is a file that the radio ap references to know what label to use and display. I have searched for this file or ap location but have had no luck in finding were it would be located. Can anyone point me in the right direction on how to possible fix it so the radio displays the correct station type? Sorry to hijack a thread but my post count is not high enough to allow me to start my own. search has not helped. Thanks all.
Click to expand...
Click to collapse
Thank you for the work!
Question, how did you extract the img file. the typical utilities i use for android seem to be incompatible with this system image.
Found!
http://forum.xda-developers.com/showthread.php?t=2257331
Yes. Earlier post
mlkemac said:
Thank you for the work!
Question, how did you extract the img file. the typical utilities i use for android seem to be incompatible with this system image.
Found!
http://forum.xda-developers.com/showthread.php?t=2257331
Click to expand...
Click to collapse
See post #5.
@wskelly could you maybe tell me exactly what you did to include SuperSU in ROM? I would like to integrate it into the ROM builder scripts here https://github.com/da-anton/MTCD_ROM-cooking. Would be great!
da_anton said:
@wskelly could you maybe tell me exactly what you did to include SuperSU in ROM? I would like to integrate it into the ROM builder scripts here https://github.com/da-anton/MTCD_ROM-cooking. Would be great!
Click to expand...
Click to collapse
Yes, I kind of did already. If you look into the SuperSU thread here in Xda, you can get the latest version. Inside the flashable zip, there is a dir
META-INF/com/google/android
Then you'll find install-binary, which is actually a shell script. (this directory structure is the actually standard format for recovery-flashable zips)
In the shell script the author goes into great detail about what his where and with what permissions.
The big caveat for your efforts is that we have sdk 22 (5.1.1) and things are different depending on which version of Android you have (some Joying units are KitKat). The installation script handles every version of Android so far and this is all detailed by the author in the script.
Another warning: the installation script runs another binary tool that will "convert" wine of the binaries to "pie" executables. Because the ones I want are compiled for ARMv7, and I'm on Intel modding the ROM, I'm not sure if I can run that tool with confidence. So, I took the su binary files from Malaysk's ROM, which I know work. This is why SuperSU tells you that the binary is out of date right away. You must follow the chaos and chcon instructions in the installation script exactly. (I think malaysk is missing some of those steps because his rom would always fail to update su via the app)
So my recommendation is to look at the installation script, and follow the instructions in the comments section which are very detailed about what goes where. Except instead of using SuperSU installation files, you should take the files from my ROM. **You may try to use the files from SuperSU, but likely you will get a bootloop (because of the pie format issue), worth trying though. Also worth trying the pie conversion on Intel.
I'm on my phone so hopefully spellings and the path names aren't too messed up.
I'm curious if removing the recovery.img and bootloader.img if it will still flash. Flashing those two partitions every time is asking for trouble eventually.
Sent from my Moto G using Tapatalk
pinkpanther28 said:
Greetings,
I am very new to these head units got my first one 2 months ago. been reading and learning a lot here. I have a KGL and installed this rom, its working great and its a bit visually different then the one's I have used for KGL. Glad to know we have options on roms and tweaking we can do.
I do have a small annoyance that I hope some one can help me with. I had hoped this rom would solve it but unfortunately not. The radio RDS feature, on all the roms I have used the problem stays the same. I am in the US and its set to Europe RDS PTY code. So I can see the all the station and song information but the Station genera is wrong. like country music stations listed as pop and rock stations listed as Drama. I figure their is a file that the radio ap references to know what label to use and display. I have searched for this file or ap location but have had no luck in finding were it would be located. Can anyone point me in the right direction on how to possible fix it so the radio displays the correct station type? Sorry to hijack a thread but my post count is not high enough to allow me to start my own. search has not helped. Thanks all.
Click to expand...
Click to collapse
Yea, this post is *completely* off topic and deserves its own thread. Maybe someone here will start a new thread for you.
Sent from my Moto G using Tapatalk
wskelly said:
So my recommendation is to look at the installation script, and follow the instructions in the comments section which are very detailed about what goes where. Except instead of using SuperSU installation files, you should take the files from my ROM. **You may try to use the files from SuperSU, but likely you will get a bootloop (because of the pie format issue), worth trying though. Also worth trying the pie conversion on Intel.
Click to expand...
Click to collapse
OK. I created a module in the MTCD ROM builder for that. How exactly did you set the links without chroot? Maybe you could have a look a my version and could tell me if anything is missing :angel:
https://github.com/da-anton/MTCD_ROM-cooking/blob/master/modules/install_supersu.sh
da_anton said:
OK. I created a module in the MTCD ROM builder for that. How exactly did you set the links without chroot? Maybe you could have a look a my version and could tell me if anything is missing :angel:
https://github.com/da-anton/MTCD_ROM-cooking/blob/master/modules/install_supersu.sh
Click to expand...
Click to collapse
Awesome script! I was way too lazy to do this but I wished I had it! ? I actually started to mod the SuperSU script to root the local ROM but I just got lazy.
To link without chrooting you can use the -f (force) option.
I am on my phone and didn't get to look at the whole script yet but you could just try to root stock and see if it works?
Nice job!
Sent from my Moto G using Tapatalk
wskelly said:
Awesome script! I was way too lazy to do this but I wished I had it! ? I actually started to mod the SuperSU script to root the local ROM but I just got lazy.
To link without chrooting you can use the -f (force) option.
I am on my phone and didn't get to look at the whole script yet but you could just try to root stock and see if it works?
Nice job!
Click to expand...
Click to collapse
Thanks! I already tried that and my unit is stuck in a boot loop now. Guess it's because I forgot to include the binary from Malaysk and used the official one instead will try the next days to fix my unit
So I'm trying to get Viper4Android running on my MTCE_WWW Android 8.0 headunit running the stock ROM. I've rooted the system via the adb "injection" method (SuperSU). Root access seems to work fine for everything I've tried.
So then I downloaded the Viper4Andrid files (Viper4Android_FX_v2505.zip) and installed the "Nougat_IO_test_fix.apk" version of the app. I run the app and tell it to load/update the Viper driver - it takes about 30 seconds and says that the driver was installed successfully and tells me to reboot. I reboot the device and try to run Viper4Android, but it goes back to the driver update/install prompt. The actual driver install doesn't seem to be working (even though it says it loaded successfully).
Any idea what I'm doing wrong here?
Thank you in advance!
Ok, I finally got Viper4Andorid working on my MTCE Android 8.0 head-unit... I ended up having to do everything manually (manually editing audio_effects.conf, manually putting the lib4a_fx_ics.so driver file into the proper directory, etc). Since there is no custom recovery available for these MTC? Android head-units, I couldn't just flash any of the flashable V4A .zip files I found online - so I basically did everything a flash would do - just did it manually via a file explorer.
Let me go back and figure out the *exact* steps that I took and then I'll come back here and make sure to document the exact steps I did - may help someone else in the future...
I do realize that I could have just installed one of the custom ROMs that have V4A built in, but they seem to run a lot hotter than stock (from what I've read) and I would rather only install mods that I acutally want to use - instead of installing a bunch of stuff that I will never use and will just make the system run hotter.
So far, from my VERY brief testing, V4A seems to work very well though.
Hello mate, where i can found the steps did you use?