Atoto m4 /m4272/m4171 help identify possible roms etc - Android Auto General

Can any one shed any light on this unit (root roms etc)
Having recently bought because of its 2 sec boot time due to mcu unit
Having read through threads to identify it
I am none the wiser
Tried accessing Oem settings too but no passwords used or
Recommended in the forum seem to work
Is it possible to mod in any way
I have checked in settings /about
And no reference to mtcd or b etc can be found
Please help
Thanks
Ref
https://www.amazon.com/ATOTO-Touchs...?ie=UTF8&qid=1488239263&sr=8-1&keywords=Atoto
Ref
http://www.myatoto.com/index.php?m=content&c=index&a=show&catid=15&id=17

Did you figurw out anything on this device? Im gettin it 2day.
Sent from my A0001 using Tapatalk

R u able to use adb with it?

https://forum.xda-developers.com/an...d-units/stop-m4272-root-t3561066/post71458964

I have not tried adb
But looks like it works and root too
According to above posts
So now how do we go about identity of unit beyond atoto
To see if any roms are compatible
I recently contacted atoto about low mic volume/gain
They said they would release an app soon to control the mic better.but they are currently focused on a newer unit with
Androids 6.0 so that has delayed releases for current m4
They did say they had the sdk for android 5.1 for this unit
As I had a mic problem I did some digging with
Shortcut master
https://play.google.com/store/apps/details?id=org.vndnguyen.shortcutmaster.lite
And this gave access to hidden Oem settings
In audio then choose mic and then levels
Having changed level 1 to 240 (set) and all other levels up til 8
Are also changed to 240 ( max is 255 if you prefer)
My mic preformed much better now but could still do with a little tweaking.

Thanks for the info for the oem settings. Shortcut master got me into it. Just searched for oem...
I was able to get into engineer mode with apex launcher b4, but thanks though.
Also the bootanimation in the app section work on this unit. Just got to rename to bootanimation.zip and put it in /system/media/

Cant get usb debugging to work. Checked it in dev options and even edited the build.prop and default.prop with
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb,mass_storage
Then there was another setting in there that was
ro.sys.usb.storage.type=mtp,mass_storage
I changed it to
ro.sys.usb.storage.type=mtp,mass_storage,adb
And still cant adb through usb.. Can anybody help?

I have not tried usb debugging but just wondering if you tried each USB port as in the manual it says each port is designed for a specific device/ add on like camera phone etc
But I have no idea if this makes a difference
But anything is possible with android as I have learned over the years

I have the 2 long usb cables running to the front dash using, Rerii 1 Meter 3ft Dual USB Extension Flush, Dash, they both work with mass storage and charge my phone. Both work with a wireless keyboard and mouse also. Havent tryed the short cable, being i installed the unit b4 i got the rerii adapter, and its a pain takin the dash apart.
Think thats just how the other things get mounted, if u look at storage in the settings, the mounts r already there.
Really need to get usb adb to work. Default.prop keeps reverting back to stock.. Im gonna keep lookin for solutions.
Also. When reboot to Recovery it goes straight into installing update, no menu. Bootloader reboots after like 5-10sec.

Maken a nandroid backup now. Gonna try n make a recovery for it..

New firmware 8.0.3 was just posted
Have not had a chance to fully test it to see what's new
But easy connect now works with my phone
Nexus 6p 7.1.1 march pure nexus rom
So I am happy as it has not worked at all on 7.1.1 till now
Note unit m/4 must have an internet connection for 1st install of easy connect to phone
Or else it will fail to download needed services for success
Also needed to setup Bluetooth and wifi again after update
Note my phone will not connect with Bluetooth pin 0000
Change to 1234 and then it connects ok.

New email from atoto today
"Our engineer is working on release an microphone gain control app in the next 2-3 weeks, so I have to ask you wait for extra a few days."

downloading when i get the pass... Smh

Whats the password?

Password is atoto
Please read the install instructions in the extracted zip
Before proceeding
As it has a 2 part update

Thank u.

Installed the new update, its buggy as ****. The subwoofer settings wont stick, and dnt sound right.. And clock wont wont save. Soon as u turn the car off and back on, the clock is wrong.. Smh.

Supposed to be CPU: MTK Soc-based Quad-core 1.5Ghz. Mine only gets 1.3Ghz. What is yours running at?

Sent atoto an email about the bugs
Waiting on reply maybe Monday
Have had this clock problem on kitkat before
USA has set its clock back but Europe has not done it yet
During this window of difference some clocks act weird
Well at least last time this happened that's what it was
Have not checked cpu will get back to you on that
Also noticed firmware 8.0.3 reports as 8.0.2 in settings
Not sure why???

There is another update https://www.adrive.com/public/wtGBAn/ATOTO OS Update for M4 0318.rar
It fixed the clock issue. Change the subwoofer settings, but its still buggy.
Can you check the cpu with cpu-z? Thanks.
Did u get urs rooted yet? Its a pain in the butt, but i got it. I wander if any of the xposed mods will work.
Need to get usb debugging to work, so i can go about porting twrp.

Related

[Q] Endless QPST frustration, native tether

Hello geniuses. I almost never post on XDA because I do my best to search, read, try/fail instead of asking questions but now I have one and can't find the answer- hope someone can help.
I'm trying to SIMPLY change the tethered nai address on my brother's (bored visiting the family) motorola droid (unrooted, stock AFAIK) to get his native tethering to work. I've done this multiple times before on my htc (wm6.1, 6.5, androided touch) and new Fascinate phone but his is a complete PITA.
His stats are: androud 2.2.1, baseband c_01.43.01.P kernal 2.6.32.0-g68eeef5 android [email protected]#1
Thus far, I have installed the moto usb drivers, and installed HW virtual serial port to interface with QPST (192.168.16.2, port 11008) . I can read/ write to the phone without problem EXCEPT it keeps reverting the tethered nai to [phone#]@dun.vzw3g.com. Even when I add a whole new profile, the new profile changes to add the @dun, regardless of whether it is an active profile. At first, I thought it wasn't writing at all but then finally thought to try adding a new one and it writes everything correctly EXCEPT adds the @dun to the tethered nai address.
SO, what gives? Is motorola more tightly locked down then everything else I've played with?
I'm having the exact same issue that you are having. I have no idea what could be causing it. Some friend told me to try to find the file that actually stores this data, pull it out (using adb) edit it in notepad or something and then push it back.
It actually makes sense but...if it's possible, which file could this be!?
Let's see if someone replies with a solution. In the meantime i'll keep investigating.
Dumb question, but are you guys putting the phone in diag mode (power off, hold 'T', and plug in the USB cable: the phone shouldn't acknowledge the USB cable)?
Sent from my Droid using XDA App

[Q] Deactive Remote Sim Mode

Hi guys,
After many hours and days of searching google for a solution to this I'm still stumped.
I have a Galaxy S i9000 running Gingerbread 2.3.3 (had same problem with previous versions also) and I am trying to connect it to my Nokia 616 car kit in "hands free" mode, however, it keeps automatically connecting via "remote sim mode". I can confirm there is no way to disable rSAP (remote sim mode) through the nokia 616, nokia staff were not very helpful either.
There was an option in my old Samsung Jet (i think it was running touchwiz) bluetooth settings which allowed me to switch remote sim mode on and off. The only setting that exists on my SGS is after I connect to the nokia 616 i get the "Deactivate Remote Sim Mode?" option from the drop down bar... However, when I do so, the connection to the car kit is lost and upon reconnect it automatically connects using "Remote Sim Mode", regardless of how many times i try an "deactivate" it...
The only posts I could find about deactivating remote sim mode tell me to hit "Yes" to "Deactivate Remote Sim Mode", then to switch bluetooth off and then on. This does not solve my issue. Problem persists.
The only thing I can think of now is somehow finding perhaps a command line instruction that I can run from terminal to disable remote sim mode or even change a config file somewhere to deactivate it.
Does anybody have any idea how this can be done or maybe just give me a lead on where I can search next, I've hit a dead end with this now and im sure it can be done, somehow.
Thanks heaps for your help.
I'm sorry I cannot help you with this problem, but at least you're not the only one: I have exactly the same problem, but then with a Nokia 616 and a Galaxy S2.
I want it to connect with the normal HFP, so I do not loose the internet connectivity on my phone...
SOLVED Finally!
So after a while of searching then giving up, then contemplating ripping out my nokia 616 car kit and setting it on fire, I decided to revisit this issue and here is how I managed to disable/remove/deactivate remote sim mode or rsap... please note that I havnt really tested to see if this affects any other bluetooth functionality (i dont think it does though) so do at your own risk...
I ended up flashing my galaxy s with Darkys rom 10.2 extreme edition which gave me some nifty options of removing some stock bluetooth apps... I noticed there were a number of bluetooth related apps there, Bluetooth.apk , BluetoothOpp.apk, BluetoothPbap.apk, BluetoothTestMode.apk and the devil himself BrcmBluetoothServices.apk... at first i uninstalled them all except Bluetooth.apk, my phone starting throwing some bluetooth error which was expected, these errors disappeared after I rebooted the phone... I noticed that the 616 no longer connected using rSap (victory!), however, I was almost certain that not all of the apps i removed above would be causing the issue, and im sure that if anything having them removed would cause issues elsewhere so the process of elimination began... I reinstalled them all again, rebooted my phone, sure enough remote sim mode was back, then one by one i uninstalled, rebooted, tested, etc etc untill i came to the conclusion that the app responsible to rSap was in fact BrcmBluetoothServices.apk, after uninstalling it and rebooting Hands Free mode works a treat, I still get a "download error" when i try to download my contacts to the 616 but Im not to fussed about it, at least i can still use all the functionality of my phone in my car now, internet etc etc... as mentioned earlier I dont know if this will have any effect on the other uses for bluetooth so do be careful, not a huge issue because it can be easily reinstalled if nessecary using DarkysRom Tool...
Now I am sure this can be done on a stock firmware, you would most definitely need to root the phone and then find some sort of system app manager to hunt down BrcmBluetoothServices.apk and remove it...
Thats it! If anybody can work out how to successfully download contacts to the nokia 616 please post it here or pm me.

Allshare Cast dongle connection problems

Good news: I took adavantage of Samsung's 50% off special to pick up an Allshare dongle for $50.
Bad news: Can't get it working on my rooted TMO GNII.
This is what happens *every time* I try to connect (20-30 times)
Hooked up dongle to TV via HDMI. TV shows Allshare ready to connect on the screen.
With the red led flashing on dongle, I press the reset button and the led changes to solid blue.
On phone, try to connect with Allshare Cast utility.
Phone sees and connects to dongle.
Screen on TV changes to screen with black background and says connecting, but never gets any further and never shows the phone screen on the TV. (See attached image)
Connection is lost after 10 seconds and this message appears in a pop up on phone: "Current AllShare Cast connection will end."
Here's what I've tried so far. Each time getting the same result as described:
Updating Allshare Cast app from Play store.
In SuperSU app, unrooting phone by unchecking Enable Superuser.
Restoring stock T-Mobile rom from nandroid backup, with and without Superuser enabled.
Installing and running Triangle Away 3 times in a row. This got the flash counter down to 1, but not 0. Also shows Binary status: Custom.
In stock rom and with SU disabled, the phone downloaded and sent a firmware update to the dongle, but this update did not change results at all.
Hoping someone can give me something else to try. If not I may have to completely unroot and restore stock image to verify this works at all. Then go step by step through rooting, adding back Clockwork recovery, etc. to see where the Allshare connection gets broken.
Get the triangle away app. Reboot and enjoy. Theres a thread on getting this to work, and I can attest to it working cause im rooted custom rom and enjoying my allshare
Also try uninstalling triangle away and reinstalling. When you run the app does it reboot your phone for you? Mine does and thats when I know it works.
Sent from my SPH-L900 using Tapatalk 2
globen said:
Get the triangle away app. Reboot and enjoy. Theres a thread on getting this to work, and I can attest to it working cause im rooted custom rom and enjoying my allshare
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
Already tried this, 3 times. Yes, it rebooted my phone. I wish it had worked for me! Will try uninstall/reinstall of TA as you suggest. So what rom/recovery are you using? When you do a Vol down/Home/Power button boot up, what does it say for your Counter and Binary Status?
Yup I'm seeing the same problem but with Wanam RIM.
Sent from a Toaster using XDA App
Had same problem. I could almost cut and paste your post OP. Its not root status, nor does a custom rom necessarily bugger allcast function; its the kernal. You currently cannot run any custom kernal and have allcast function. Triangle Away is powerless in the face of this vial DRM kernel menace.
You can mix and match or use some modded roms and you can debloat and/ or freeze much of your junk. When using triangle away for the allcast dongle TA activation must be done in a paticular sequence...
Chainfire gives detailed info in his "triangle away" thread. ( you've propbably found this already but if you haven't, then it is a must read.)
Sent from my SAMSUNG-SGH-I317 using Xparent Blue Tapatalk 2
vizographic said:
Had same problem. I could almost cut and paste your post OP. Its not root status, nor does a custom rom necessarily bugger allcast function; its the kernal. You currently cannot run any custom kernal and have allcast function. Triangle Away is powerless in the face of this vial DRM kernel menace.
You can mix and match or use some modded roms and you can debloat and/ or freeze much of your junk. When using triangle away for the allcast dongle TA activation must be done in a paticular sequence...
Chainfire gives detailed info in his "triangle away" thread. ( you've propbably found this already but if you haven't, then it is a must read.)
Click to expand...
Click to collapse
So if I understand correctly, being rooted and having a custom ROM do *NOT* prevent the dongle connection from working. It's having a non-stock kernel that makes it not connect, is that correct? So in theory if I restore the stock rom from my nandroid backup, and correctly run TA, it should work fine? Now what about having a custom recovery? Does that have any effect on the Allshare dongle? I have Clockwork. Do I also need to restore the stock recovery?
Also, in the TA thread, I'm not seeing the part about "When using triangle away for the allcast dongle, TA activation must be done in a paticular sequence... " Could you please copy and paste that part into this thread? Thanks.
Yep, you got it right vouty. The kernal must be stock to connect allcast dongle. The rom can be modified stock or custom but your success may vary.
You can be rooted....and you can use custom recovery, I am using use twrp (cmw is said to also work).
[But if you use a custom recovery, my current understanding is that, your flash counter will be reset from 0 to 1 on a boot up. Take this with a grain of salt. ]
I refered to a sequence, sorry if I made it more complicated than necessary. Just reflash triangle away, and don't check the counter, if you do it will set counter back to one if you have a custom recovery. Hope this helps, the dongle works really well, you're going to like it.
Sent from my SAMSUNG-SGH-I317 using Xparent Blue Tapatalk 2
vizographic said:
Yep, you got it right vouty. The kernal must be stock to connect allcast dongle. The rom can be modified stock or custom but your success may vary.
You can be rooted....and you can use custom recovery, I am using use twrp (cmw is said to also work).
[But if you use a custom recovery, my current understanding is that, your flash counter will be reset from 0 to 1 on a boot up. Take this with a grain of salt. ]
I refered to a sequence, sorry if I made it more complicated than necessary. Just reflash triangle away, and don't check the counter, if you do it will set counter back to one if you have a custom recovery. Hope this helps, the dongle works really well, you're going to like it.
Click to expand...
Click to collapse
Thanks for getting back Vizo. So I got it working! I tried restoring the stock rom from nandroid, restoring the stock recovery, then running TA, but still didn't work. At that point I know I'm gonna have to do a full stock image restore and what I chose was this method from mrRobinson: http://forum.xda-developers.com/showthread.php?t=1975560
If you follow the simple steps, as written in the thread, this will fully restore stock ROM, recovery and wipe the Internal SD space putting your T-Mobile Note II back to perfect, out of box condition, with Device Status showing "Normal" and counter status as original... BUT PHONE IS ROOTED! And it does it all in just one easy step. Definitely owe mrRobinson a beer.
The dongle is now working with my phone and it is awesome! Already got Netflix streaming installed and working. Gotta hand it to Samsung. Allshare cast is a "Killer App"!!!
Only remaining issue is that I don't have a custom recovery, so no flashing any goodies like custom toggles, status bar mods, or 4.2 camera for now. Want to enjoy the Allshare goodness for awhile before I risk breaking it with Clockwork and TA not being able to fix it. Hoping Chainfire can work his magic on this issue and break the triangle's back permanently!
interesting to hear everyone's experiences with the dongle problem. i was having similar problems but had the luxury of testing out with my rooted t-mobile note II and wife's stock ATT note II. i was getting the exact same "connection will end message" on both phones. decided to change TV's and found that i was able to use the allsharecast dongle without any problems. didn't have to restore or change anything. worked right away after plugging in to different tv. i'm wondering if there may be some incompatibility with the HDMI signal or connection with the TV that could be contributing to dongle connection problems?
Disclaimer: troll post.
ok, here we go:
mochishiro said:
interesting to hear everyone's experiences with the dongle problem
Click to expand...
Click to collapse
Lmao. and
Super lmao:
Hi everyone. I get the same issue as Vouty.
vouty said:
This is what happens *every time* I try to connect (20-30 times) (...)
Click to expand...
Click to collapse
My phone has never been rooted or changed - it is totally original, straight out of the box. I can't do anything to connect to this Dongle thing. Please help me if you can.
Hmm have you tried a different tv. It has worked on all the tv's I've tried mine on but some have reported that this can work...also just to clarify things did u run the update from the play store?
Sent from my SAMSUNG-SGH-I317 using Xparent Blue Tapatalk 2
mjaz85 said:
Hi everyone. I get the same issue as Vouty.
My phone has never been rooted or changed - it is totally original, straight out of the box. I can't do anything to connect to this Dongle thing. Please help me if you can.
Click to expand...
Click to collapse
Things to check:
System settings>About device>Status - Scroll to last item, Device status. It should say "Normal." If it says anything else, like "modified," then it probably won't work.
Check everything is right with the dongle connections:
I would suggest using the HDMI cable that comes with the dongle, just to rule that out.
Ensure you are "pairing" correctly. The correct steps are to *FIRST* put the dongle in pairing mode. Start by unplugging the power and plug back in. Wait for the led on the dongle to start flashing red. Tap (do not long-press) the reset button. This should immediately make the led turn solid blue. It *will not* pair unless the led is solid blue. When the led is solid blue, the dongle is ready to pair. Now on the phone, pull down the notification bar and tap the Allshare toggle (it's way over on the right). It should see and connect to the dongle. Like bluetooth, you only need to pair the first time. After that, it will auto-connect everytime you toggle on Allshare and the dongle is in range.
Once I restored my GNII to factory stock, as I described, the pairing worked perfectly, the first time, and has been working ever since. Good luck!
vizographic said:
Hmm have you tried a different tv. It has worked on all the tv's I've tried mine on but some have reported that this can work...also just to clarify things did u run the update from the play store?
Sent from my SAMSUNG-SGH-I317 using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
I suppose anything is possible and that there could be TV's out there with old, non-compliant HDMI inputs. But if anyone was gonna have this issue, it would be me. My TV is a cruddy, 5 yr old Olevia 26" 720p hunk of junk from Frys. Yet every HDMI signal I've ever plugged in (Windows laptops, weird DVI-HDMI ebay media players, even my old HTC Sensation with an MHL adapter) have worked fine. Hoping Santa brings me a nice shiny new "ultra-thin" full HD resolution HDTV for XMAS!
Help Please
Got my Note 10.1 about a week ago along wıth AllShare Cast Dongle. Everything worked fine at first but after doıng a factory reset (which I was advısed to do by Samsung Support because of some dısappearing icons) I can connect but after about 2-5 minutes of video the pıcture freezes on both TV & Tablet . Get a message on tablet - Allshare connection is unstable - then - Current Allshare Cast Connection will end. The frozen pıcture on the screen then breaks up and goes to green screen.
If I try to connect at this stage Tablet cannot see the dongle (blue light on) & only way to get ıt seeıng ıt agaın ıs to take out power lead for a few minutes.
Unfortunately I am in Turkey at the moment so cannot go to Samsung Service Centre (language problems) so if anyone can give me any advice it would be much appreciated.
This is my fırst Android device and everything is stock. Still running ICS.
1st Have you applied the allshare cast update? There were a lot of reports of sketchy connection issues with the allshare dongle. The recent firmware update from the playstore seems to have fixed many of them.
2nd which phone are you on? You mention you are on ics. If its not the dongle it does complicate matters a bit, since I'm on jellybean. Still, If you can answer the first update question, and provide ,model ,make ,rooted and /or
non/stock plus kernel info, I'll do what I can to help.
3rd, Turkey! You traveling on business or pleasure? What are your impressions? Always wanted to travel out that way, find it a fascinating country as a serious history buff......
Sent from my SAMSUNG-SGH-I317 using Xparent Blue Tapatalk 2
vouty said:
System settings>About device>Status - Scroll to last item, Device status. It should say Normal.
I would suggest using the HDMI cable that comes with the dongle, just to rule that out.
Ensure you are "pairing" correctly.
Click to expand...
Click to collapse
Everything is just as described above. Can't connect to my home TV but I've connected without any problems to different TV. Can the problems relate to WiFi settings? How is data transmitted between dongle and TV?
Thanks for your time Vizographic
Did mention in my post usıng Samsung Galaxy Note 10.1 Tablet. Received an update to dongle last nıght just before I posted, did not appear to make any difference. Just tried again and video ran for just under 5 minutes before connection stopped and reported unstable. Everything stock (have not played with anything apart from factory reset) Android Version 4.0.4 as have not yet received the upgrade to JB.
I now live in Turkey and have no intentions of movıng again - beautiful country, very friendly people (now have a Turkish wife) and a nice climate. If you are a history buff Ephesus about 1.5 hours away and Troy about 5 hour drive. Did not buy tablet here as electronics about double the price of the States.
uzumlubay, its seems I missed this detail, in the first sentence of your post....
"Did mention in my post usıng Samsung Galaxy Note 10.1 Tablet."
How sad is that? Well, i sure can't blame you if you ignore any of my proffered advice! My bad..lol. Ok, I've come up with two things you can try.
1st download wifi analyser free from the market. The dongle has it's own wifi built in, it will show up along with all the surrounding wifi routers and the channels they use. The app will detect and suggest optimum channel settings and highlight crowded channels. If the dongles channel is crowded it would display the issues your describing. It would be best if you could moniter the connection with your tablet on a second device, but either way it might help with figuring this out.
2nd,There have been a few posts on power supply to the dongle being fickle. If you haven't already, try a different power supply, one that puts out 5 volts...it seems to have worked for a few.
3rd, substitute the suppied hdmi cable with another one known to work well.There is at least one case, displaying connection issues very similar to yours, that turned out to be caused by a bad allcast cable.
4th "I now live in Turkey and have no intentions of movıng again - beautiful country, very friendly people (now have a Turkish wife) and a nice climate. If you are a history buff Ephesus about 1.5 hours away and Troy about 5 hour drive." If any of my half baked ideas solve your problem, I fully expect you to invite me to stay with ya'll in Turkey. ..and does your wife have any sister's
Sent from my SAMSUNG-SGH-I317 using Xparent Blue Tapatalk 2
Ok, finally my dongle started to work. How? I don't really know I changed again HDMI ports on my tv ... and it started to work like magic. So as info for all the others - just try everything you can: different hdmi ports, another hdmi cable, power source, other tv etc
Wysyłane z mojego GT-N7100 za pomocą Tapatalk 2

MHL woes - how to fix?

So I had MHL working perfectly for nearly a year. Im on Android 5.1.1
Suddenly I plugged it in as usual and nothing happened. I thought it was the MHL cable so bought another. Same thing.
I started having a look around and in Smart Connect > TV > MHL I noticed under 'launch app' it said 'MISSING: com.sonyericsson.tvlauncher'
I searched and searched and searched online but could not find where to download this app. Only thing I found was http://forum.xda-developers.com/xperia-z1/themes-apps/sony-tv-launcher-time-tv-t2871060 and well...I just installed the apk's from that link. It still didnt work, but now under launch app it said MISSING: something else. To be honest I can't remember exactly what, but it was longer than the previous.
At this point I was getting pretty pissed off so didnt try anything again until I just went online to Sony Support and they advised to go to Apps > All > Smart Connect and press Clear Data.
I just did that and now.....under Smart Connect there is no more TV shown, nothing happens when I plug in the MHL. TV Launcher seems to be installed correctly now...but yea still nothing happens.
Next step I was advised was to connect to my computer and run 'Repair Experia device' which I will do as soon as my phone is 80% charged.
Anyone have an idea about whats happened, and what to do to fix??
Only thing I can think is every few days Im having to move stuff over from phone memory to sd card, and always select everything to move...pics..vids...apps...maybe it moved the tvlauncher app or something? Although last week it did say there was an error and it was unable to move 1 app...I didnt think much of it...
Thanks!
https://play.google.com/store/apps/details%3Fid%3Dcom.sony.tvsideview.phone%26hl%3Dde%26referrer%3Dutm_source%253Dgoogle%2526utm_medium%253Dorganic%2526utm_term%253Dsony%2Btv%2Bapps%26pcampaignid%3DAPPU_1_Ih5nVsXrGYmGzAOmyL-IDA&ved=0ahUKEwjFhMOc78zJAhUJA3MKHSbkD8EQ8oQBCCYwAA&usg=AFQjCNH4ErmJtArvv1f2a-FYLr85JzYFIw
It's this and maybe only got renamed?
Try to edit the package and app name to replace the link or make it work again
aldolino said:
So I had MHL working perfectly for nearly a year. Im on Android 5.1.1
Suddenly I plugged it in as usual and nothing happened. I thought it was the MHL cable so bought another. Same thing.
I started having a look around and in Smart Connect > TV > MHL I noticed under 'launch app' it said 'MISSING: com.sonyericsson.tvlauncher'
I searched
and searched and searched online but could not find where to download this app. Only thing I found was http://forum.xda-developers.com/xperia-z1/themes-apps/sony-tv-launcher-time-tv-t2871060 and well...I just installed the apk's from that link. It still didnt work, but now under launch app it said MISSING: something else. To be honest I can't remember exactly what, but it was longer than the previous.
At this point I was getting pretty pissed off so didnt try anything again until I just went online to Sony Support and they advised to go to Apps > All > Smart Connect and press Clear Data.
I just did that and now.....under Smart Connect there is no more TV shown, nothing happens when I plug in the MHL. TV Launcher seems to be installed correctly now...but yea still nothing happens.
Next step I was advised was to connect to my computer and run 'Repair Experia device' which I will do as soon as my phone is 80% charged.
Anyone have an idea about whats happened, and what to do to fix??
Only thing I can think is every few days Im having to move stuff over from phone memory to sd card, and always select everything to move...pics..vids...apps...maybe it moved the tvlauncher app or something? Although last week it did say there was an error and it was unable to move 1 app...I didnt think much of it
...
Thanks!
Click to expand...
Click to collapse
This apk is from stock .264 (latest) Z3C firmware.
try to install,
or better, move to /system/priv-app/SemcTvOut and set permissions to rw-r-r.
AMDFenics said:
This apk is from stock .264 (latest) Z3C firmware.
try to install,
or better, move to /system/priv-app/SemcTvOut and set permissions to rw-r-r.
Click to expand...
Click to collapse
jep, as i thought, its the same app i linked tnly got renamed So if it isnt compatible to your OS take the play link or have a look @ apkmirror

Wi-Fi stays off in Android Pi

Wi-Fi been working fine in Android 9 (Dirty Unicorn version), now it won't stay on at all and to top it off it show no MAC address. How do I get it back on?
thanks,
_dave said:
Wi-Fi been working fine in Android 9 (Dirty Unicorn version), now it won't stay on at all and to top it off it show no MAC address. How do I get it back on?
thanks,
Click to expand...
Click to collapse
Does it allows to turn WiFi on?
WiFi comes on and then turns off by itself?
[CLOSED] fixed -
re-installed "9", everything working again.
I've had this too. Sometimes wif-fi just refuses to re-enable after the TP goes to sleep. The toggle moves and then just slides back. The only way to re-enable is to reboot. I'll give a re-install a go when the next version is released as it is not a major problem for me. Just thought I'd mention it as it is not an isolated incident.
MikeN68 said:
I've had this too. Sometimes wif-fi just refuses to re-enable after the TP goes to sleep. The toggle moves and then just slides back. The only way to re-enable is to reboot. I'll give a re-install a go when the next version is released as it is not a major problem for me. Just thought I'd mention it as it is not an isolated incident.
Click to expand...
Click to collapse
I have not experience that "yet".
Make sure the WiFi connection is " Treat as unmetered" ( this is Android feature ) not ROM
Besides that, any settings or extra Apps that the user install could make WiFi work differently.
Also Android 9 must use a swap partition and the settings from the Guide.
I've not actually in stalled much as I still prefer to use webOS!! Hate me if you like but Android & iOS are now bringing in their own versions of gestures and 'cards' that webOS had nearly 10 years ago. On this basis I still have the Swap file so all is good there.
I'll check the Android settings later to make sure, however for the device to be working fine, put down (in the 6 year old wireless charger) and left for a couple of hours and then you cannot enable wifi does not sound like an issue with the basic Android settings. Either this in an install problem, a ROM problem or a hardware problem. As there just 2 of us with this and _dave reinstalled and it seems to be good for him I'll presume it is an install problem for now and just live with it until I get bored - or an updated ROM is released.
MikeN68 said:
I've not actually in stalled much as I still prefer to use webOS!! Hate me if you like but Android & iOS are now bringing in their own versions of gestures and 'cards' that webOS had nearly 10 years ago.
I do agree with you on the WebOS interface and we clearly see now how the others mobile OS have implemented the WebOS gestures and other things.
On this basis I still have the Swap file so all is good there.
WebOS was the first and truly a mobile operating system designed for a Tablet and the swap partition is part of that.
I'll check the Android settings later to make sure, however for the device to be working fine, put down (in the 6 year old wireless charger) and left for a couple of hours and then you cannot enable wifi does not sound like an issue with the basic Android settings.
I have been running youtube playing music since 8 am this morning and now is 3pm data usage for that tablet is over 2 GB and I have the Super variant install of Open Gapps, the maximum that can be flash. WiFi does not drop as is all working. I turn WiFi on and off, it reconnects. When dealing with WiFi there are two devices involved and two settings, router and tablet. I had issues with disconnects and it was due to my manual settings that I had on the router and there was interference. I mostly set up all settings to auto, selected channel 11 that does not have much interference "where I am" and all went away.
Either this in an install problem, a ROM problem or a hardware problem. As there just 2 of us with this and _dave reinstalled and it seems to be good for him I'll presume it is an install problem for now and just live with it until I get bored - or an updated ROM is released.
Click to expand...
Click to collapse
When describing an issue, it must be very specific.
1. WiFi does not reconnect to the same wireless network ( does not see it) WiFi icon is outline but not filled.
2. WiFi is completely off, does not see any network ( WiFi icon is not visible ) OFF
What is the graphical status of the WiFi icon next to the battery icon ( outline or filled )?
OK. As I just posted to show that _dave was not alone, I think (for me) this is getting out of hand. Whilst I do appreciate your time and knowledge, it is simply (again for me) not a significant problem.
However. If I use the TP it is not a problem so streaming music would be in the realms of using. The issue I have is that after using it I place it inthe dock and when I pick it up again hours later I sometimes find wifi is not enabled. I got to settings and toggle the 'slider' to ON and a second later the 'slider' moves back to the OFF position. I simply cannot make the 'slider' stay in the ON position. If I restart the TP everything is fine and dandy again.
So for me a quick reboot is sufficient to keep me using this ROM. I know I can roll back to an earlier ROM or even try Pie again like _dave did. As we seem to be the only two users that have voiced a problem here and he has fixed his I cannot ask you to look into this further - unless there are other users that are also affected.
RIP webOS
MikeN68;79445604
RIP webOS :([/QUOTE said:
What Kernel are you using or frequency from the guide?
WebOS is now LuneOS and also is on LG TV
https://pivotce.com/tag/luneos/
Click to expand...
Click to collapse
WiFi connection "feature"?
HP_TOUCHPAD said:
I have not experience that "yet".
Make sure the WiFi connection is " Treat as unmetered" ( this is Android feature ) not ROM
Besides that, any settings or extra Apps that the user install could make WiFi work differently.
Also Android 9 must use a swap partition and the settings from the Guide.
Click to expand...
Click to collapse
Where would I find the "Android feature" for the WiFi connection? Other then the ROM I don't know how to get to this feature.
_dave said:
Where would I find the "Android feature" for the WiFi connection? Other then the ROM I don't know how to get to this feature.
Click to expand...
Click to collapse
Settings --->> Network & Internet --->>WiFi ( connected WiFi is the first one ) to the right (the blue icon)
The last down (Advanced).
Also WiFi will take time to connect again after the Tablet comes out of standby (sleep)
What kernel speed did you flashed from the Guide?
HP_TOUCHPAD said:
Settings --->> Network & Internet --->>WiFi ( connected WiFi is the first one ) to the right (the blue icon)
The last down (Advanced).
Also WiFi will take time to connect again after the Tablet comes out of standby (sleep)
What kernel speed did you flashed from the Guide?
Click to expand...
Click to collapse
Thanks, got it
For some reason I did not installed any kernel speed-up, should I and can I just add it now (already setup)? I'm thinking of using the 1728000 version or should I go higher?
Thanks for all your support.:good:
_dave said:
Thanks, got it
For some reason I did not installed any kernel speed-up, should I and can I just add it now (already setup)? I'm thinking of using the 1728000 version or should I go higher?
It is a must and that is why the guide was created and those files fixes issues with the non working Bluetooth and the performance of the ROM, is not only to speed-up. It clearly state to flash in the specific order.
1. ROM
2. Kernel Boots optimize settings
3. Open gapps (Pico recommend)
Thanks for all your support.:good:
Click to expand...
Click to collapse
If you are not familiar or know the maximum CPU frequency your tablet can handle flash the 1728 if you experience reboots then try lower. If want to get better performance then try 1782 and 1836 if the tablet can handle it.
But always follows the instructions exactly as posted it, that is how the ROM was tested and guarantee to work.
You are welcome!
HP_TOUCHPAD said:
If you are not familiar or know the maximum CPU frequency your tablet can handle flash the 1728 if you experience reboots then try lower. If want to get better performance then try 1782 and 1836 if the tablet can handle it.
But always follows the instructions exactly as posted it, that is how the ROM was tested and guarantee to work.
You are welcome!
Click to expand...
Click to collapse
I started over again and flash the ROM then the 172 and pico app, didn't have a reboot problem but I lost WiFi again (keeps going off, even after rebooting). So, I dropped down to 1674 and everything working again. I'll stay with 1674 for now, at least until the next ROM update.
Again, thanks for your help.:good:
HP_TOUCHPAD said:
What Kernel are you using or frequency from the guide?
WebOS is now LuneOS and also is on LG TV
https://pivotce.com/tag/luneos/
Click to expand...
Click to collapse
Yeah, tried LuneOS (it's many iterations) and although it is moving in the right direction it is still not as polished as webOS was when it died (has it ever actually died?). I still use apps from the old app store but Android is just easier as it is up to date and works. If webOS development was restarted and brought fully up to date with a decent stocked store it would (and should have) been a great success. Oh well :crying:
I thought about a LG TV but can't justify the cost whilst my Sammy TV is working
_dave said:
I started over again and flash the ROM then the 172 and pico app, didn't have a reboot problem but I lost WiFi again (keeps going off, even after rebooting).
Also check your router settings if there are interference on the channels and is set to automatically change channels the Tablet may have issues updating to the new channel.
So, I dropped down to 1674 and everything working again. I'll stay with 1674 for now, at least until the next ROM update.
A higher frequency that the tablet can not handle will make it reboot or freeze, using the closer highest frequency for the Tablet will make it work better.
Again, thanks for your help.:good:
Click to expand...
Click to collapse
You are welcome, any other questions just post it !
---------- Post added at 02:39 PM ---------- Previous post was at 02:26 PM ----------
MikeN68 said:
Yeah, tried LuneOS (it's many iterations) and although it is moving in the right direction it is still not as polished as webOS was when it died (has it ever actually died?).
LuneOS is work in progress, but at least the built it browser works well. WebOS is alive on the LG TVS
I still use apps from the old app store but Android is just easier as it is up to date and works.
The most important on any OS is the Apps available that add functionality.
If webOS development was restarted and brought fully up to date with a decent stocked store it would (and should have) been a great success. Oh well :crying:
Developers support and willing to develop App for the platform is the key to a successful OS.
I thought about a LG TV but can't justify the cost whilst my Sammy TV is working
Click to expand...
Click to collapse
I think that the only thing that is need it is a Theme pack to cosmetically make Android 9 look like WebOS. The gestures are the same.
LOL you're forgetting QT web browser and QupZilla on the TP now
I have the theme and Fling settings on an old Experia but that didn't feel right (there was a tutorial a while back in Pivot). Palm had the interface/UX just about perfect but it was never loved by the public and HP didn't really give a sh*t.
MikeN68 said:
LOL you're forgetting QT web browser and QupZilla on the TP now
I have the theme and Fling settings on an old Experia but that didn't feel right (there was a tutorial a while back in Pivot). Palm had the interface/UX just about perfect but it was never loved by the public and HP didn't really give a sh*t.
Click to expand...
Click to collapse
To me Pie is very similar to WebOS, even the charging sound is very similar to the finished boot sound in WebOS.
All is changing and we must adapt to it, to be able to keep the Tablet updated and useful.
Android Q is already in Beta, who knows if it will boot in the HP TP and the developers will take the challenge.
Hi HP_TOUCHPAD, once again I cannot get my TP to see my WiFi (rest of my devices - no problem). And once again the "advance" section does not show up in "Network & Internet" section. So how do I get the "advance" section to show up again.
_dave said:
Hi HP_TOUCHPAD, once again I cannot get my TP to see my WiFi (rest of my devices - no problem). And once again the "advance" section does not show up in "Network & Internet" section. So how do I get the "advance" section to show up again.
Click to expand...
Click to collapse
@_dave sorry for the delay. Staring with Oreo 8.1 if any changes are done to the router the WiFi connection will be lost and the Tablet will not see the WiFi signal that was connected to and a reboot is required. If the router was changed then, select forget network and connect again. The same issue is present in Pie 9.

Categories

Resources