Related
Hi. My daughter has an SGS Note 10.1 - completely stock firmware since we purchased it in December. We just updated it to Jelly Bean 2 days ago and everything went fine. However, there is a JB demo video that must've been installed with the update showing the added features of JB. However, we can't stop the video from starting to run every time the Note is started or put into sleep. As soon as the sleep button is pushed the video starts. There is not a pause or play button - if you touch the screen the video disappears and the lock screen appears (where one would enter their code or "connect the dots" diagram to enter the device). We can unlock the device and everything works fine. But if you press the sleep button the device goes into sleep for about 1 second and then the demo video pops up and starts to play again. The only way to stop the video from playing is to power down the device. But, once you turn it back on the video starts to play and you must touch the screen to stop it.
I've searched all over the web and can't find anything on this. My guess is this is too new and not enough people are experiencing this problem. Any thoughts? THANKYOU!
maybe not a JB update issue??
we just updated my son's SGS Note 10.1 and he does NOT have the same issue. so maybe it is a demo video my daughter downloaded from the web?? Either way, not sure how to stop this from playing. Is there a folder on the Note where I can delete a system video? Any other ideas? THANKS AGAIN.
kmuddzy said:
we just updated my son's SGS Note 10.1 and he does NOT have the same issue. so maybe it is a demo video my daughter downloaded from the web?? Either way, not sure how to stop this from playing. Is there a folder on the Note where I can delete a system video? Any other ideas? THANKS AGAIN.
Click to expand...
Click to collapse
Hey now that sounds annoying. I've never heard of a video launching after hitting the power button. But we should be able to find it and delete it. Its been a while since I've used stock but I'm pretty sure our device came with a file explorer stock. If you go to the app drawer you should see it there. There are plenty of options in the play store which don't require root if not, just search file explorer and that should take care of that. Now launch a file manager and look for sdcard, select that and look for a folder called Samsung. In there will be another folder called video. I'm guessing the jB demo video is located here but it may not be. If you see it then a long press will give you the option to delete. If it doesn't show up there you could use the search button in the file browser if you know the file name. Also what video player is being launched? You could find the video in that app and that should give you a way to delete as well. Actually that sounds a lot simpler. Lol good luck and if you don't find it post back here. No reason to be terrorized by some rogue video when your ready to put the tab down.
If you've ever flashed the PAP firmware it does the same sort of thing. I believe that it's the special SCS for some sort of store demo.
So it's definitely not a bug, but a mode that can be enabled. I seem to recall that it was not easy to get rid of either
I'll try to remember how I finally got rid of it - it was some sort of settings file that I had to modify I think.
Its Demo mode .
Likewise i don't have it and don't remember except possible when running settings turn off .
Best is freeze with Titanium Backup or remove the app .
jje
If it really is demo or retail mode, I found that it was impossible to change a few settings.
You can't enable the lock screen at all.
You should find that it's impossible to change the screen timeout values. It will change, but when you exit settings and re-enter it will have ignored the change.
It happened on my Daughter's N8010 - I was experimenting with some stock ROMS cos I'd had an issue.
I flashed it to German JB 4.11 and then realised I couldn't find the UAE Stock ROM - whoops.
So I flashed a few other ICS multi CSC ROMS and tried to get my way back to stock. One of these was the PAP rom. I've since flashed it back to JB
So tell me, how did you do the upgrade to JB?
Bulbous said:
If it really is demo or retail mode, I found that it was impossible to change a few settings.
You can't enable the lock screen at all.
You should find that it's impossible to change the screen timeout values. It will change, but when you exit settings and re-enter it will have ignored the change.
It happened on my Daughter's N8010 - I was experimenting with some stock ROMS cos I'd had an issue.
I flashed it to German JB 4.11 and then realised I couldn't find the UAE Stock ROM - whoops.
So I flashed a few other ICS multi CSC ROMS and tried to get my way back to stock. One of these was the PAP rom. I've since flashed it back to JB
So tell me, how did you do the upgrade to JB?
Click to expand...
Click to collapse
we simply received the OTA notification that JB was available and selected update. Went quickly and when it was done the home lock screen was on. We entered as we usually do through the lock screen and everything was fine and all of the new features were there. As soon as we hit the power button to put it into sleep the video came on and the rest is history. Thanks for everyone's help on this...it is frustrating for my daughter and now for me!!
Specialp said:
Hey now that sounds annoying. I've never heard of a video launching after hitting the power button. But we should be able to find it and delete it. Its been a while since I've used stock but I'm pretty sure our device came with a file explorer stock. If you go to the app drawer you should see it there. There are plenty of options in the play store which don't require root if not, just search file explorer and that should take care of that. Now launch a file manager and look for sdcard, select that and look for a folder called Samsung. In there will be another folder called video. I'm guessing the jB demo video is located here but it may not be. If you see it then a long press will give you the option to delete. If it doesn't show up there you could use the search button in the file browser if you know the file name. Also what video player is being launched? You could find the video in that app and that should give you a way to delete as well. Actually that sounds a lot simpler. Lol good luck and if you don't find it post back here. No reason to be terrorized by some rogue video when your ready to put the tab down.
Click to expand...
Click to collapse
Thanks for the ideas. I've done as you've suggested and I can't find a video file that matches. I don't know the name of the video and there isn't any indication as to what type of video player is playing this. this video only runs full screen and I can't resize it or pause it. As soon as I touch the screen the video disappears. I don't even know what type of video file android plays so I can't do a wildcard search, either (windows reference - if android has such a thing). I'm the opposite of an expert regarding android or the note so I can't say I'm doing the right thing here.
JJEgan said:
Its Demo mode .
Likewise i don't have it and don't remember except possible when running settings turn off .
Best is freeze with Titanium Backup or remove the app .
jje
Click to expand...
Click to collapse
thanks. Not sure how to remove the app since I don't know what app is playing it. I will look into Titanium Backup but, again, not sure what I'm looking for.
Bulbous said:
If you've ever flashed the PAP firmware it does the same sort of thing. I believe that it's the special SCS for some sort of store demo.
So it's definitely not a bug, but a mode that can be enabled. I seem to recall that it was not easy to get rid of either
I'll try to remember how I finally got rid of it - it was some sort of settings file that I had to modify I think.
Click to expand...
Click to collapse
If you can remember that would be great!
The store demo app appears in the Samsung App store (not the Google Play one) and should probably be removable as an app unless of course it does "special" things.
Found it, it's called "Retailmode for Galaxy Note 10.1" - see if you can find and remove it?
I tried a few things to get rid of it, and I definately remember looking through my installed apps & uninstalling something
Sorry, I can't remember what it was though.
Sent from my GT-N8000 using XDA Premium HD app
Peter Galbavy said:
The store demo app appears in the Samsung App store (not the Google Play one) and should probably be removable as an app unless of course it does "special" things.
Found it, it's called "Retailmode for Galaxy Note 10.1" - see if you can find and remove it?
Click to expand...
Click to collapse
thanks for your reply. There isn't an app listed like that in the Samsung App store nor the Google play store. I don't see any apps in either that have anything to do with the Note or a demo.
I did notice something else. Now when I power on the device from complete shutdown (or restart) the lock screen appears as normal and the video does NOT play. On the lock screen there isn't any time showing. When I unlock the Note the time appears in the lower right corner and everything works fine (maybe this is normal)
BUT...when I go to put the Note into sleep mode, the video appears as described above. The time shows (even though the device hasn't been unlocked) and a NEW icon that looks like a gray eye with 3 eyebrows appears in the lower right notification bar (or maybe it is supposed to look like a timer). This eye now stays on until I turn off (or restart) the Note and unlock it.
EDIT: I just researched what this gray eye is for and found out it is for "smart stay", which keeps the device on as long as you are looking at it. I turned it off in settings:display and unfortunately the video still comes on when I try to put it into sleep (or if the device enters sleep by itself). The weird thing is the smart stay icon only shows in the notification bar once the video starts to play even though it is turned on in the settings.
If you have any additional thoughts please let me know.
It should be found in SYSTEM/ APPS or SYSTEM/Data /Data/apps
jje
Are you sure you aren't just seeing the screen saver program? Think I had a similar problem after JB upgrade. In your applications menu, you should have a "screensaver" program that you can open and disable the function. That is what I did. Unless we're talking apples and oranges here??
zagleft1 said:
Are you sure you aren't just seeing the screen saver program? Think I had a similar problem after JB upgrade. In your applications menu, you should have a "screensaver" program that you can open and disable the function. That is what I did. Unless we're talking apples and oranges here??
Click to expand...
Click to collapse
Nope their is a demo app that runs on some stock firmware . Had it on my initial stock firmware .
jje
JJEgan said:
Nope their is a demo app that runs on some stock firmware . Had it on my initial stock firmware .
jje
Click to expand...
Click to collapse
correct. This isn't screen saver but good idea.
jje QUOTE:" It should be found in SYSTEM/ APPS or SYSTEM/Data /Data/apps"
I downloaded "FILE MANAGER HD" and looked all over the unit, especially where you pointed above. I sorted by date and by size (figuring a movie would be rather large). The problem is I don't know what I'm looking for. I didn't see anything with the words "Demo" or "Retail" or "Jelly Bean" in them and I don't know what the file extension would be.
I searched SYSTEM folder using keywords
"demo" (only found a font file),
"retail", "Jelly", "movie", "intro", "*.mp4"
"feature" (found a bunch of .xml , .jar and .odex files),
"clip" (found .apk and .odex files)
"mp4" (found only 2 .so files but I know daughter has made more of these which are in the GALLERY/Camera folder)
"tablet" (found 43 .odex and .apk files. couldn't run apk files from the folder as security precaution)
Is there any type of history log I can start to tell me what is running?
This is getting really frustrating but I THANK YOU for all of your suggestions!!!!
video of demo movie
I uploaded a video showing what is happening - it didn't let me upload a .3gp file from my SGS1 phone so I put it into a .zip file. View attachment 1667754 Just to clarify, this video shows the video I'm trying to get rid of - it is a demo JB showing the new features - I don't know...maybe seeing what it is doing will help in some way.
I can also take screen shots/videos of the folders/files search.
Flashed stock ICS with retail mode .
One task manager kills it .
Two open Icon code is 5444.
Three settings service Enable OFF.
Location of app is via root System / app folder .
jje
solved
zagleft1 said:
Are you sure you aren't just seeing the screen saver program? Think I had a similar problem after JB upgrade. In your applications menu, you should have a "screensaver" program that you can open and disable the function. That is what I did. Unless we're talking apples and oranges here??
Click to expand...
Click to collapse
All right...I feel like an idiot (I am an idiot) and I am posting this to prevent anyone else from doing what I did and wasting hours of time. Even though my daughter said my she didn't download any screen savers (another reason for me to be crowned an idiot for thinking my pre-teen always knows what she is doing) AND my initial search for screen savers came up empty, I finally found one when I was looking for the task killer (which disappeared from the center app bar since JB was installed?). The screen saver was THE VIDEO!!! Zagleft1 wins. Why anyone would want a screen saver to come on when they press the power button is beyond me but even if that is a bug I wish I had found this dam program a lot sooner.
I really can't believe it turned out to be this simple and I really apologize to all those if you feel I wasted your time. You have all been great - I learned a lot about the Note 10.1 and jelly bean. I even found out my son is using my daughter's note to look up "boobs" and "truth or dare sex games". Now onto parental controls. I'm sure the PC process will dwarf the amount of hours I "wasted" on trying to solve this video problem.
Thanks again everyone!!!!!
So I just wanted to make a thread for these units where people can ask/answer questions specific to these devices. May help others as the info online isn't the best, including their own forum site which I have unable to access with a few weeks due to persistent ads...... ?
To get the ball rolling;
I have updated to the new official firmware with the new widget launcher, I like the launcher, well the fact that I have large icons and can have widgets on the home screen.
My issues are,
1) when I start the car (dormancy mode) I am trying to get tasks to run automatically (open rocket player, play audio etc.) Problem is there seems to be a built in task killer that kills macrodroid (which I'm using for my tasks). I have tried autostart apps but these don't trigger as the HU is coming out of dormancy mode and not actually booting. Anyone have a work around for this? If I could get Macrodroid to run I could solve the rest using macros (tasks)
2) Since the new update with the new launcher i no longer have Voice to text, i installed the google app but this caused the launcher to crash and only left me with the recent apps screen, luckily I was able to get back into play store from here and uninstall google app again which brought all back working again.
3) When playing a podcast (Bluetooth streaming from phone) and I want to change to rocket player to play music, if I just tap play on the rocket widget the media starts playing but I get no sound until I open the app, kind of defeats the purpose of the widget being there!
4) when I first installed the unit I had no problems with the illuminate function (headlights dim screen and turn on button lights) this worked for about a month and then for no reason just stopped, now if I turn on my lights the button lights flick on for about half a second and then turn off again, its not an issue with the lights as they work fine when I chose the timed option. I haven't checked my 12v feed yet as I'm guessing its OK due to the flicker, it will happen every time I turn the lights on.
I have tried reset, reflash combos about 6 times at this stage but always with the same results.
I know there are options to change the ROM but I would like to keep it stock for now just in case I need to return it.
fado5ster said:
So I just wanted to make a thread for these units where people can ask/answer questions specific to these devices. May help others as the info online isn't the best, including their own forum site which I have unable to access with a few weeks due to persistent ads...... ?
Click to expand...
Click to collapse
I assume you mean the http://forum.carjoying.com/ forum? If so, mention that. Be concrete.
That is indeed annoying, but there are many hundredths of users on that forum without issues. Maybe your ISP doing something weird.
fado5ster said:
To get the ball rolling;
I have updated to the new official firmware with the new widget launcher, I like the launcher, well the fact that I have large icons and can have widgets on the home screen.
Click to expand...
Click to collapse
The new official ROM?? Which one? The 5 March version? And did you pick the right one of the two? And which unit do you have?
Mention all that! This makes your remark/question useless as people trying to help first need to ask you that.
fado5ster said:
My issues are,
1) when I start the car (dormancy mode) I am trying to get tasks to run automatically (open rocket player, play audio etc.) Problem is there seems to be a built in task killer that kills macrodroid (which I'm using for my tasks). I have tried autostart apps but these don't trigger as the HU is coming out of dormancy mode and not actually booting. Anyone have a work around for this? If I could get Macrodroid to run I could solve the rest using macros (tasks)
Click to expand...
Click to collapse
Search the forum. already many time mentioned. You need the NoKill app. Can be downloaded from here and mentioned here.
fado5ster said:
2) Since the new update with the new launcher i no longer have Voice to text, i installed the google app but this caused the launcher to crash and only left me with the recent apps screen, luckily I was able to get back into play store from here and uninstall google app again which brought all back working again.
Click to expand...
Click to collapse
Don't you search at all? Also known issue and mentioned here on the forum.
fado5ster said:
3) When playing a podcast (Bluetooth streaming from phone) and I want to change to rocket player to play music, if I just tap play on the rocket widget the media starts playing but I get no sound until I open the app, kind of defeats the purpose of the widget being there!
4) when I first installed the unit I had no problems with the illuminate function (headlights dim screen and turn on button lights) this worked for about a month and then for no reason just stopped, now if I turn on my lights the button lights flick on for about half a second and then turn off again, its not an issue with the lights as they work fine when I chose the timed option. I haven't checked my 12v feed yet as I'm guessing its OK due to the flicker, it will happen every time I turn the lights on.
I have tried reset, reflash combos about 6 times at this stage but always with the same results.
I know there are options to change the ROM but I would like to keep it stock for now just in case I need to return it.
Click to expand...
Click to collapse
Again: which ROM are you on? You should mention that. ROMS before 2017 contain bugs, so do they in 2017 but at least a lot less. So make sure you are on a newer ROM. If you already are, like you mentioned above, mention the version. That saves people from asking for the obvious. Before you post read the rules.
Look at this thread and this thread
First of all: Search the forum.
And secondly: Search the forum.
And third: Be concrete. Mention versions, forums, etc. You don't even mention which head unit you have.
I was looking but could only find info on the 1gb model and the thread about the release of the 2gb model.
Thanks for the info but you don't have to be a **** about it.
I missed stuff when searching, I couldn't access the joying forum, I thought saying "their own forum site" would have cleared that. I couldnt access the site to find out if there had been updates, at the time i was on the ONLY UPDATED ROM with the new launcher with customizable widgets.
When i found NoKill I thought it was for steering wheel controls which I don't have so I moved on.
When I asked about model numbers on the joying forum (when I could access it) I was made out to be an idiot too because "They are all the same thing" so forgive me for thinking that. Mine is the JY-UL135N2
Again, Thanks for the info but you don't have to be a cranky prick about it, this is a forum isn't it? Used for discussion and help?
I was only saying something like this with info in one place would be good, if its out there already then sorry, mods can delete and ill crawl back into my hole of idiotness
Yes, I was annoyed but I did give you a number of helpful links and be honest: you were not very exact in your phrasing.
And w.r.t. the roms: They are on the joying blog59 page which is also mentioned several times on several postitions in this forum, and you could also have found it from the "normal" joying website carjoying.com
Even though I was annoyed I tried to help you. If your phrasing was more concrete that would have been a lot faster. And you still don't mention which ROM you are currently using, so nobody can give you an exact answer.
You can be angry with me, but clear communication would have prevented my irritated reply.
I am on the 2017222 rom but will be updating to latest tomorrow, have downloaded just need to do the HU side of it. I can get access to the Joying site using your link and only your link, not sure why or whats going on as this includes the main joying site too.
I plan on updating, attempting root then install NoKill.
I am giving the info I have, I don't know a lot about these devices and although I have rooted phones and tablets before I have never done anything like this.
You did give me helpful links and I thank you for that but please don't be too angry with people asking questions. I realise you know how this works but others don't and are afraid of damaging the device. Before your link which I used to access the updates page I had no way of checking for updates as I couldn't get onto the page
fado5ster said:
I plan on updating, attempting root then install NoKill.
Click to expand...
Click to collapse
There is no real need to update to the March 5 ROM if you already have the 22 Feb ROM.
The ROM is rooted. What you mean is that you want to install a SuperUser app like SuperSU or Kingroot or the like.
You don't need to SuperSU your ROM. You can install the NoKill version just like that as the ROM is rooted. You simply don't have the nice, userfriendly superuser apk on the system.
surfer63 said:
There is no real need to update to the March 5 ROM if you already have the 22 Feb ROM.
The ROM is rooted. What you mean is that you want to install a SuperUser app like SuperSU or Kingroot or the like.
You don't need to SuperSU your ROM. You can install the NoKill version just like that as the ROM is rooted. You simply don't have the nice, userfriendly superuser apk on the system.
Click to expand...
Click to collapse
So there is no real advantage to the March 5 ROM?
Oh, I didn't know it was rooted still, thought they stopped that on the 2gb devices.. I'm not even sure if I need root for anything, all I wanted it for was to get to the /system... folder to copy NoKill to. Can I get there without SuperSU app using ES file explorer? Am I safe to delete the existing nokill.apk in there 1st and then copy in the new file? It won't cause any issues not having the apk for the few seconds? (Probably a stupid question)
fado5ster said:
So there is no real advantage to the March 5 ROM?
Oh, I didn't know it was rooted still, thought they stopped that on the 2gb devices.. I'm not even sure if I need root for anything, all I wanted it for was to get to the /system... folder to copy NoKill to. Can I get there without SuperSU app using ES file explorer? Am I safe to delete the existing nokill.apk in there 1st and then copy in the new file? It won't cause any issues not having the apk for the few seconds? (Probably a stupid question)
Click to expand...
Click to collapse
The Sofia server is loaded upon boot and stays in memory. So no problem there.
Best thing to do via adb.
Code:
adb push Sofia-1-C9-Server-V1.0.apk /sdcard/
adb shell "su -c mount -o remount,rw /system"
adb shell "su -c cp /system/app/Sofia-1-C9-Server-V1.0/Sofia-1-C9-Server-V1.0.apk /system/app/Sofia-1-C9-Server-V1.0/Sofia-1-C9-Server-V1.0.apk.old"
adb shell "su -c cp /sdcard/Sofia-1-C9-Server-V1.0.apk /system/app/Sofia-1-C9-Server-V1.0"
adb shell "su -c chmod 644 /system/app/Sofia-1-C9-Server-V1.0/Sofia-1-C9-Server-V1.0.apk"
adb shell "su -c ls -l /system/app/Sofia-1-C9-Server-V1.0"
last command does nothing toyour system. It should only list the new apk and the old apk.old.
and then reboot your unit.
I know you are going to hate me for this but any time I've tried pushing files using adb I end up messing it up and bricking it.
Looks like the illumination problem was due to the car.. The illumination wire was in a different place to the joying connector, I repinned it and working now but still doesn't explain how I had it working fine for a month.. Really weird, had issues with 12v switched and constant 12v too.. Had to swap them around.. Seems to be Kia's doing and not joying.. Very strange
Macrodroid not running in background FIXED
Hey there! You probably fixed the issue with macrodroid by now but I had the same issue and I fixed it by installing Macrodroid as a system app. That did the job for me. Just did a reboot and waited for macrodroid to come up.
Hello,
I'm looking to edit the vehicle status app,
I don't like the generic car image for open door status.
Can somebody send me the apk file? Mine is corrupted, and have no backup.
Anbei sollte eine normale App sein die noch nicht veränder wurde.
Sorry just noticed it was an english thread.
This should be an unmodified CAN BUs app.
A while ago i made the same. That for me the effort wasn´t worth the result.
Hey, thanks.
But that's not the app I was looking for, it must have "vehicle" in the name of the app.
Why it wasn't worth of effort, you were not satisfied or it didn't work?
Ah shut.
Sorry should be more patient while readinsg the whole text.
But this time it should be the wright app.
It worked on the car which is shown in the pdc but i wans´t stattisfied with an car special picture and it just won´t fit right so yeah i steped beak to the original app.
Thanks, that's it
I'll let you know what I did with it.
?
I managed to do it, I also changed the canbus app so my car now shows up every time I open the door.
I would NOT want to do it again, the App graphics are terribly composed. It tok me 2 days/around 8 hours.
stanjkof said:
I managed to do it, I also changed the canbus app so my car now shows up every time I open the door.
I would NOT want to do it again, the App graphics are terribly composed. It tok me 2 days/around 8 hours.
Click to expand...
Click to collapse
Uh looks pretty sweet.
But that is what im talking about. You need a lot of work for an poor result.
Gesendet von meinem G8341 mit Tapatalk
stanjkof said:
I managed to do it, I also changed the canbus app so my car now shows up every time I open the door.
I would NOT want to do it again, the App graphics are terribly composed. It tok me 2 days/around 8 hours.
Click to expand...
Click to collapse
This is nice... probably it can be modified to have more options... I mean, OEM TPMS show, OEM Parking Sensors, etc. and solve also some bugs
I.E. , in my 2010 Jeep Grand Cherokee I have the Panel LED lighting up only if I use the "Manual Headlights On". In "Auto" mode it will not work. I assume that the canbus app cannot decode the "Auto" message. Also in the "Veichle" I don't see anything.
Well, you can only edit graphics, other stuff is encoded, so...
Nobody has source code.
Here are both canbus and controlinfo apk's, edited to show red Seat Leon instead that generic white car.
controlinfo app goes to system/app/MTCcontrolinfo/ folder
canbus app goes to system/private-app/MTCcanbus/ folder (or something like that, I don't remember)
stanjkof said:
Here are both canbus and controlinfo apk's, edited to show red Seat Leon instead that generic white car.
controlinfo app goes to system/app/MTCcontrolinfo/ folder
canbus app goes to system/private-app/MTCcanbus/ folder (or something like that, I don't remember)
Click to expand...
Click to collapse
I just looked at you app and thought you made a great job.
Where did you get these great carmodel?
Or did you do it on your own?
9_Mad-Max_5 said:
I just looked at you app and thought you made a great job.
Where did you get these great carmodel?
Or did you do it on your own?
Click to expand...
Click to collapse
Thanks man.
I found the top-down view of the car on google, tinted the glass, changed the color, did a lot of editing in photoshop (made opened door graphics from scratch ...it had none of that).
A lot of sweat and going up and down to my car to test it.
Original graphic elements in the app are terribly missaligned and just plain sloppy. I couldn't stand it.
Also, where is that bluetooth app located? I can't find the apk that contains the graphics (dialer, numbers, etc)?
I need to rework that to look less tacky.
To change the image for when the doors open, what apk of the two do I have to install or is it necessary to replace the two?
stanjkof said:
I managed to do it, I also changed the canbus app so my car now shows up every time I open the door.
I would NOT want to do it again, the App graphics are terribly composed. It tok me 2 days/around 8 hours.
Click to expand...
Click to collapse
Hi mate,
this reminded me that old CarO pro prog.. correct?
2016/05/06/caroo-pro-dashcam-obd-v3-1-0-07-apk
((( if the link is not allowed? please remove it. )))
I see you have some experience with vehicle/Controlinfo/MTCanbus thus i will ask a question
In my Unit there is no vehicle/Controlinfo/MTCanbus application installed thus i have no info regarding doors open and other like fuel, voltage etc..
I am struggling for a long time to find a solution without any luck. Installing the apk fails and even copying to /system/app/ is not working. I have a canbus decoder that came with the unit and the steering wheel buttons are working. I recently upgrade to Hal9k Rom (which is awesome) from Malaysk but still those apps are not included.
Any idea ?
Car : Mercedes W164
Unit : PX5 / MTCE_GS_V3.00_3
ROM: Hal9k Mod v3.1
Canbus decoder : GS 20180514 HW:V2 SW:V3 (for B200/W211/Viano/R350/W209/S320)
ale_kons said:
I see you have some experience with vehicle/Controlinfo/MTCanbus thus i will ask a question
In my Unit there is no vehicle/Controlinfo/MTCanbus application installed thus i have no info regarding doors open and other like fuel, voltage etc..
I am struggling for a long time to find a solution without any luck. Installing the apk fails and even copying to /system/app/ is not working. I have a canbus decoder that came with the unit and the steering wheel buttons are working. I recently upgrade to Hal9k Rom (which is awesome) from Malaysk but still those apps are not included.
Any idea ?
Car : Mercedes W164
Unit : PX5 / MTCE_GS_V3.00_3
ROM: Hal9k Mod v3.1
Canbus decoder : GS 20180514 HW:V2 SW:V3 (for B200/W211/Viano/R350/W209/S320)
Click to expand...
Click to collapse
Hi,
I maybe wrong but..
it depends on your car and the year of construction of the vehicle plus the pc-unit of the car or it allows.. so it is not as easy as you thought.
My car is a Mercedes 2009 model therefore it should work based on comments from other people with older cars.
ale_kons said:
My car is a Mercedes 2009 model therefore it should work based on comments from other people with older cars.
Click to expand...
Click to collapse
Hi,
if you are really sure about that? then it is the used canbus, it is not well programmed, the chinese little guys could not program everything as it had to be.. or, there is an expensive canbus (blue of color, if i'm not wrong) for sale, only I had the name of it long forgotten, if one (buyer) has some problem with his car options, he mail to them the problem back and they make it working with a newer sw update etc.. costs +/- 100 €.. if I still remember it.. so a very expensive canbus indeed.
Edit:
https://www.google.com/search?safe=...KHW4WDCgQsAR6BAgFEAE&biw=1280&bih=726&dpr=1.5
In my app when you have a wheel with low pressure, a door comes out, is this going well?
On Joying headunits with CAN Bus, it is not possibile to use resistor based USWC: this thread aims to overcome the limitation by using an Arduino MICRO connected to the receiving unit of the USWC and to the headunit via USB to simulate a hardware keyboard.
reserved 1
Github repository: https://github.com/MobeedoM-opensource/android-auto
reserved 2
reserved 3
surfer63 said:
In your code you also use the BOOT_COMPLETED broadcast. You know that with the Joying deep-sleep option, you will see that only on rare occasions? This is: only on reboots or power (dis)connects?
Click to expand...
Click to collapse
Yes i know thank you, i noticed that for some strange reason the firmware deactivates the accessibility service even at reboot (at true boot not only with ACC_OFF).
You use the "com.fyt.boot.ACCON" intent filter in your services. If it doesn't have serious consequences please also add the "com.glsx.boot.ACCON" for those users on Sofia that might want to start using your app as well. But this in turn would also require the "minSdkVersion 23" instead of "minSdkVersion 24" like you have now. My PX5 is on 8 so I have api level 26, but my old Sofia on the bench is on 6.0.1 and it would be handy to test there first. (I tried to build your code, but there are many "hurdles" in your app/build.gradle, so I need to dive a little deeper into it)
Click to expand...
Click to collapse
Yes of course i'll add the intent filter, but please note that the current version of the app doesn't use those intents on api level 26+ (my headunit), because of the background execution limits (the implicit intent is simply not received).
The only intent that i was able to trap, but i still need to investigate because it doesn't always work and I haven't figured out why yet, is the android.hardware.usb.action.USB_DEVICE_ATTACHED.
For the build.gradle, if you tell me what are the hurdles maybe i can help, also via PM if you prefere.
You have the method startAccessibilityService with the rooted system call: What does that actually do? Is it for the user to give access? Or the system to give access (as it is rooted)? Is it for the root_preference "OnlyBroadcast"?
Click to expand...
Click to collapse
An accessibility service cannot be started programmatically in android, the user must manually activate it with the switch in the accessibility services section.
That command is used to simulate the behavior of the user who changes the state of the switch, it requires root and it is not granted to work on all roms.
You use the "getCurrentForegroundPackage()". I guess this still works if your have (for example) your navi app in the foreground and your media player in the background and you want to skip to the NEXT, as you automatically come to the last "if" statement in your MediaKeysMapper. But does this also work when your navi app is the foreground program and you are listening to the radio or some "generic_syu" program in the background?
Click to expand...
Click to collapse
Yes you are right, the last use case is not covered. To manage it correctly you need to know which app is currently playing, maybe it is possbile to distinguish syu apps by non syu apps by checking the android AudioManager which i think is only used by non-syu apps.
bambapin said:
Yes of course i'll add the intent filter, but please note that the current version of the app doesn't use those intents on api level 26+ (my headunit), because of the background execution limits (the implicit intent is simply not received).
The only intent that i was able to trap, but i still need to investigate because it doesn't always work and I haven't figured out why yet, is the android.hardware.usb.action.USB_DEVICE_ATTACHED.
For the build.gradle, if you tell me what are the hurdles maybe i can help, also via PM if you prefer.
Click to expand...
Click to collapse
I know about the implicit intents, but on a Sofia on Android 6.0.1 (api level 23) they should still work.
W.r.t. the build.gradle.
I had to remove the private.gradle import statement, some signing statements, defProd and the like, and finally (also literally in time) upgrade my sdk from 27 to 29 to be able to do a simple "./gradlew assembleDebug".
So no issues anymore.
(Of course I had set compile version to 27 in the build.gradle, but I ran into "missing" xmls, which I first blamed on being not committed to the repo (your fault, not mine of course ), but which turned out to be part of sdk 28 and up, so still my fault ).
surfer63 said:
W.r.t. the build.gradle.
I had to remove the private.gradle import statement, some signing statements, defProd and the like, and finally (also literally in time) upgrade my sdk from 27 to 29 to be able to do a simple "./gradlew assembleDebug".
Click to expand...
Click to collapse
Ah yes, the private.gradle... it contains my private keys passwords so i preferred not to publish them on the internet .
Indeed that file must be placed next to the app build.gradle with this content:
Code:
ext {
my_keyAlias = 'YOUR_KEY_ALIAS'
my_keyPassword = 'YOUR_KEY_PASSWORD'
my_storeFileName = 'YOUR_KEYSTORE_FILEPATH'
my_storePassword = 'YOUR_KEYSTORE_PASSWORD'
}
bambapin said:
Yes you are right, the last use case is not covered. To manage it correctly you need to know which app is currently playing, maybe it is possbile to distinguish syu apps by non syu apps by checking the android AudioManager which i think is only used by non-syu apps.
Click to expand...
Click to collapse
Maybe I insult you with providing this link , but anyway: here it is: https://developer.android.com/guide/topics/media-apps/mediabuttons
And the image in post #1. How is red and black connected, and to what?
surfer63 said:
Maybe I insult you with providing this link , but anyway: here it is: https://developer.android.com/guide/topics/media-apps/mediabuttons
And the image in post #1. How is red and black connected, and to what?
Click to expand...
Click to collapse
No insults at all don't worry and even if it were i hardly get offended
Actually i'm not expert on this particular topic, at the beginning i tried to use the standard Android MediaControllers but it seemed to me that when it came to "syu" APPS everything was bypassed, but if you think it's a viable way i'll try again.
The photo is the final version that is now installed in the car.
I noticed that there was enough room inside the SWC receiver to insert the arduino, i made a little hole for the usb socket and i connected the arduino directly (yes i admit, i soldered to save the space of dupont ).
What you see is the inside of the receiver + the arduino. The black and red cables are the power supply of the receiver, the orange and blue are KEY1 and KEY2 (the white and gray of the video). The arduino is simply glued with a removable glue (patafix).
@surfer63 i was thinking again about the autostart after the ACCON.
In the end i managed to make the intent android.hardware.usb.action.USB_DEVICE_ATTACHED always work so the accessibility service is always restarted, but i'm still looking for a better alternative (using the navi app would work but it interfere with the audio mixing level).
I looked again at the code of syu.ms and saw that when the unit wakes up, a series of apps are always launched with hard-coded package names: eg. "com.yh.devicehelper" and "com.cpsdna.mirror" which i don't seem to find installed in the headunit.
Do you have any idea what they are?
If they are never installed, perhaps it is enough to create an app with one of those package names and the system will take care of starting it at ACCON.
bambapin said:
No insults at all don't worry and even if it were i hardly get offended
Actually i'm not expert on this particular topic, at the beginning i tried to use the standard Android MediaControllers but it seemed to me that when it came to "syu" APPS everything was bypassed, but if you think it's a viable way i'll try again.
The photo is the final version that is now installed in the car.
I noticed that there was enough room inside the SWC receiver to insert the arduino, i made a little hole for the usb socket and i connected the arduino directly (yes i admit, i soldered to save the space of dupont ).
What you see is the inside of the receiver + the arduino. The black and red cables are the power supply of the receiver, the orange and blue are KEY1 and KEY2 (the white and gray of the video). The arduino is simply glued with a removable glue (patafix).
Click to expand...
Click to collapse
I do indeed think that the SYU apps do nothing according standard Android rules, so the MediaController would only be helpful for any other app. I do think you need to check if "some" SYU app is active by using something like "this" or by checking the com.syu.ms apk (via jadx(-gui)) or so, because that one also checks on several places whether one of its own SYU app is active or not, and on top or not.
So the bottom side of of the plate with the red led and condensator (or so), is the bottom of the SWC controller circuit?? If so, the image now makes sense.
surfer63 said:
So the bottom side of of the plate with the red led and condensator (or so), is the bottom of the SWC controller circuit?? If so, the image now makes sense.
Click to expand...
Click to collapse
Yes, it is the bottom, when it is inserted it rests on the 4 pillars and leaves enough space below, there will be almost 1cm from the arduino.
The only negative thing i noticed is that with the arduino so close to the antenna the reception distance of the buttons is a little lower than before, but they still work.
bambapin said:
@surfer63 i was thinking again about the autostart after the ACCON.
In the end i managed to make the intent android.hardware.usb.action.USB_DEVICE_ATTACHED always work so the accessibility service is always restarted, but i'm still looking for a better alternative (using the navi app would work but it interfere with the audio mixing level).
I looked again at the code of syu.ms and saw that when the unit wakes up, a series of apps are always launched with hard-coded package names: eg. "com.yh.devicehelper" and "com.cpsdna.mirror" which i don't seem to find installed in the headunit.
Do you have any idea what they are?
If they are never installed, perhaps it is enough to create an app with one of those package names and the system will take care of starting it at ACCON.
Click to expand...
Click to collapse
It worked!!! :laugh:
The app attached is automatically launched by the syu.ms at ACC_ON.
I used the package name "com.cpsdna.mirror", i have no idea what the original app was supposed to do, but now we have a real autorunner at our disposal.
bambapin said:
It worked!!! :laugh:
The app attached is automatically launched by the syu.ms at ACC_ON.
I used the package name "com.cpsdna.mirror", i have no idea what the original app was supposed to do, but now we have a real autorunner at our disposal.
Click to expand...
Click to collapse
:good: Very nice.
There are many apps in this ms.apk that no longer exist. Some are hardcoded called inside the app, some are called via the text files in the assets/property, but no longer exist.
I assume it is related to http://www.cpsdna.com/solutions1.html and a previous "mirrorlink" application. zlink is now by another company.
What I would do (and did in the past) is making a "micro starter app" (11~16Kb) , that only starts the app you want. So the "com.cpsdna.mirror" started by ACC_ON, starts your "com.mobeedom.android.auto.jyhuremote".
If Joying/FYT updates their list of started apps, you can simply take another "old" app and still call your own app without having to rewrite all the packages inside your own code.
(And please don't use the appcompat for such a microstarter . It explodes your code from ~11-16Kb to 1.5MB. I really hate how Studio always adds that to your project even if you target APIs that don't need it, or your app as such doesn't need it)
It would only need something like:
Code:
PackageManager pManager = context.getPackageManager();
Intent intent = pManager.getLaunchIntentForPackage("com.mobeedom.android.auto.jyhuremote");
if (intent != null) {
context.startActivity(intent);
}
surfer63 said:
:good: Very nice.
There are many apps in this ms.apk that no longer exist. Some are hardcoded called inside the app, some are called via the text files in the assets/property, but no longer exist.
I assume it is related to http://www.cpsdna.com/solutions1.html and a previous "mirrorlink" application. zlink is now by another company.
What I would do (and did in the past) is making a "micro starter app" (11~16Kb) , that only starts the app you want. So the "com.cpsdna.mirror" started by ACC_ON, starts your "com.mobeedom.android.auto.jyhuremote".
If Joying/FYT updates their list of started apps, you can simply take another "old" app and still call your own app without having to rewrite all the packages inside your own code.
(And please don't use the appcompat for such a microstarter . It explodes your code from ~11-16Kb to 1.5MB. I really hate how Studio always adds that to your project even if you target APIs that don't need it, or your app as such doesn't need it)
It would only need something like:
Code:
PackageManager pManager = context.getPackageManager();
Intent intent = pManager.getLaunchIntentForPackage("com.mobeedom.android.auto.jyhuremote");
if (intent != null) {
context.startActivity(intent);
}
Click to expand...
Click to collapse
Ok ok, no AppCompat
Maybe i could also put a minimum of parameterization with the ability to choose what to launch, maybe even more than one app.
Do you think something like this could be useful in your JET?
bambapin said:
Ok ok, no AppCompat
Maybe i could also put a minimum of parameterization with the ability to choose what to launch, maybe even more than one app.
Do you think something like this could be useful in your JET?
Click to expand...
Click to collapse
I don't see it yet. What would be useful to start from my Jet apk? Can you explain?
Please also note that when I started the JET apk I knew absolutely nothing about java (and didn't want to know anything about java) and started in appinventor/thunkable, as that was easy enough. But it is a big mess of all kind of shell scripts called from my app using the "rootexec" plugin, because that was the only way to make it work.
If I would start again I would rewrite it immediately in java.
So perhaps your own app would be a much better basis than my JET apk.
Please don't think I'm against it, but I do not understand (yet?) why that would be useful.
surfer63 said:
I don't see it yet. What would be useful to start from my Jet apk? Can you explain?
Please also note that when I started the JET apk I knew absolutely nothing about java (and didn't want to know anything about java) and started in appinventor/thunkable, as that was easy enough. But it is a big mess of all kind of shell scripts called from my app using the "rootexec" plugin, because that was the only way to make it work.
If I would start again I would rewrite it immediately in java.
So perhaps your own app would be a much better basis than my JET apk.
Please don't think I'm against it, but I do not understand (yet?) why that would be useful.
Click to expand...
Click to collapse
Don't know, i thought of your JET because i see it as a great collection of tools dedicated to Joying head units.
Given that on android 8 the intents ACC_ON and ACC_OFF are not usable, it could be an additional tool that allows you to schedule actions to be performed on wakeup without without the need to set Tasker as an NAVI app and without Xposed, since it still doesn't work on SC9853i.
BTW about Xposed i am also afraid, but i really hope i'm wrong, that with the code obfuscation of the firmwware, the maintenance of the Xposed modules will become increasingly difficult.
However, i will make a mini app with a list of apps to launch at ACC_ON (in my case the Accessibility Service, Poweramp and the NAVI), the code will be available if you change your mind .
bambapin said:
Given that on android 8 the intents ACC_ON and ACC_OFF are not usable, ...
Click to expand...
Click to collapse
Based on your work on USB, I also started to work on that idea again and built a "UsbReceiver" in my FytHWOneKey. It works great on my old sofia (6.0.1), but the usb event (""android.hardware.usb.action.USB_DEVICE_ATTACHED"") is never triggered on my 8.0.0 PX5. It doesn't work there.
Does this USB still work for you on 8.1.0?
bambapin said:
BTW about Xposed i am also afraid, but i really hope i'm wrong, that with the code obfuscation of the firmwware, the maintenance of the Xposed modules will become increasingly difficult.
However, i will make a mini app with a list of apps to launch at ACC_ON (in my case the Accessibility Service, Poweramp and the NAVI), the code will be available if you change your mind .
Click to expand...
Click to collapse
Xposed will no longer be feasible indeed when you look at the code obfuscation.
Your list of apps to be started: An internal list or external list (ascii config/ini file?), or preferences list?
surfer63 said:
Based on your work on USB, I also started to work on that idea again and built a "UsbReceiver" in my FytHWOneKey. It works great on my old sofia (6.0.1), but the usb event (""android.hardware.usb.action.USB_DEVICE_ATTACHED"") is never triggered on my 8.0.0 PX5. It doesn't work there.
Does this USB still work for you on 8.1.0?
Click to expand...
Click to collapse
Yes, it's the intent i'm still using to re-activate the accessibility service. It seems strange to me that it is not triggered at all, do you have any other app installed that could "steal" it? Torque for example?
EDIT: did you fetch the last version from github? i added a .xml with the filtered devices, it could be required (it depends on the firmware implementation)
Xposed will no longer be feasible indeed when you look at the code obfuscation.
Your list of apps to be started: An internal list or external list (ascii config/ini file?), or preferences list?
Click to expand...
Click to collapse
Internal, stored in the shared preferences.
bambapin said:
Yes, it's the intent i'm still using to re-activate the accessibility service. It seems strange to me that it is not triggered at all, do you have any other app installed that could "steal" it? Torque for example?
EDIT: did you fetch the last version from github? i added a .xml with the filtered devices, it could be required (it depends on the firmware implementation)
Click to expand...
Click to collapse
No other apps, only my own FytHWOneKey.
I did see the xml, but did not understand it and wanted to ask later. Those vendor id's / product id's: Are those from your usb devices or are they from (internal) Joying devices?
I can only find one vendor-id in the USB device database.
I've installed I think around 7 android headunits and every single one has had a Bluetooth phone app that was bad to use.
Last year I tried to find a better one, without luck.
Any recommendations?
Nope but is it an FYT based headunit - post Android system information including MCU version to understand what variant the unit might be and what bluetooth your device has.
FYI - Bluetooth is not standard in these units.
marchnz said:
Nope but is it an FYT based headunit
Click to expand...
Click to collapse
One that I'll insult tomorrow is, yes.
Edit: I'm also "installing" it tomorrow.
spludgey said:
I've installed I think around 7 android headunits and every single one has had a Bluetooth phone app that was bad to use.
Last year I tried to find a better one, without luck.
Any recommendations?
Click to expand...
Click to collapse
I don't have any bluetooth issue with mine after the aug update. (finally)
spludgey said:
One that I'll insult tomorrow is, yes.
Edit: I'm also "installing" it tomorrow.
Click to expand...
Click to collapse
Oh that poster had no intention of helping you, they just couldn't wait to tell you that you had posted in the wrong forum.
As for bluetooth implimentation, other than changing the variable in config.txt's sys.fyt.bluetooth_type= entry. They may not be any more you can do.
spludgey said:
I've installed I think around 7 android headunits and every single one has had a Bluetooth phone app that was bad to use.
Last year I tried to find a better one, without luck.
Any recommendations?
Click to expand...
Click to collapse
Not sure what exact function you are missing, but I used this one to install my OBD scanner (Vlinker) that the head unit would not connect to.
Bluetooth Finder, Scanner Pair - Apps on Google Play
Find and pair your bt device. Find your headset, smart band or earphone easily
play.google.com
ludditefornow said:
Oh that poster had no intention of helping you, they just couldn't wait to tell you that you had posted in the wrong forum.
As for bluetooth implimentation, other than changing the variable in config.txt's sys.fyt.bluetooth_type= entry. They may not be any more you can do.
Click to expand...
Click to collapse
No one could establish the unit to be FYT based on this post.
without that info recommending a configuration setting which is applicable only to FYT based units is just as useless. I request you stop making assumptions about my posts as you might be lacking prerequisite knowledge.
Knowing what the unit is, is everything. A cursory read thorough MTCD forums show just how misunderstood it is, and without my posts and reporting to moderators the forums quickly fill up with out of topic posts and the real development falling off.
If every new post started with, my unit is "ANDROID SYSTEM INFORMATION + MCU version" then those that actually know could recommend and not enter a tool like guessing game.
Would be great if you begun assisting too, if not, not a problem and if you don't like a post the report button is always available to you.
This is my last post on the matter with you.
spludgey said:
I've installed I think around 7 android headunits and every single one has had a Bluetooth phone app that was bad to use.
Last year I tried to find a better one, without luck.
Any recommendations?
Click to expand...
Click to collapse
For a hands-free bluetooth dialing app that works with FYT 7862 head units, I recommend the free "Voice Call Dialer" by ArtostoLab, which is available on the Google Play store. It allows you to say the name of the person in your contacts list that you want to call on your cell phone over the Bluetooth connection, and it confirms the contact's name by displaying it as it counts down from 3 seconds (you can configure this value) before it initiates the Bluetooth phone call.
Previously I used the Google Assistant to make calls, but when I upgraded my old PX5 to the Joying 7862 10.5 inch 1280x720 head unit I found that the only way I could get Google Assistant to make call using my voice was by setting the "Smallest Width" DPI value in the "Developers options" to a value of 596 or less, and using an older dialing app called "GVC Callhandlert 4 Joying" which is described here:
Joying forward dial requests from Google Voice
By replacing the old GVC dialing app with the Voice Call Dialer, I am now able to set my screen to full resolution, with the "Smallest Width" DPI value set to 720 DPI. I am not able to make a voice call _directly_ from Google Assistant, but I can tell Google Assistant "Voice Dialing", and then I can just say the name of the person I want it to call.
Edit: I had a typo in the open command, and the word "open" is optional.