Related
I know that I'm starting this thread in the wrong forum but I'm hoping to build a little bit more awareness among developers to see if there is a way to fix this issue.
A lot of people (even with stock) phone's are having issues going into the "My Downloads" folder in the Market and not seeing available updates for applications. I am not sure if this is something that even developers can fix or if Google needs to fix it, then we can send mass complaints to get it fixed, hehe.
It's not a huge issue, but an issue nonetheless. I hope this thread stays open for at least for a few days to direct more people to the existing thread in "Dream" forum.
Thanks in advance to everyone.
:::EDIT:::
Just wanted to let everyone know, as I am sure you've all have already noticed, that the issue mentioned above has been resolved by Google. I am not sure exactly what the initial issue was, I just want to thank everyone on their feedback during that time.
Mods, this thread is now free to close.
Use "atrackdog" app it does the update search for you!!
Glad it isn't only me who has had this problem..
Ditto. Annoying much - yes.
What's killing me is that DxTOP for one is not working with my setup (CyanoMod 3.2, Hero 1.3.5 theme, apps2sd)
But the thing that is the worst is the Market shows the available download for me as 1.0.9 when it should be 1.6.11 and the file size is 293k when it should be ~470k
cal3thousand said:
What's killing me is that DxTOP for one is not working with my setup (CyanoMod 3.2, Hero 1.3.5 theme, apps2sd)
But the thing that is the worst is the Market shows the available download for me as 1.0.9 when it should be 1.6.11 and the file size is 293k when it should be ~470k
Click to expand...
Click to collapse
I had a similar issue with a game I had purchased called Robo Defense. Oddly enough I think it was related to me not wiping before flashing. All I did was wipe and reflashed the ROM and it worked.
I have this same issue since upgraded google map app to 3.1.1 .
JF 1.5 rom.
Bratag said:
Ditto. Annoying much - yes.
Click to expand...
Click to collapse
You've got a paid app in the Market, Bratag (a very good one at that, Snap Photo PRO, buy it people). Doesn't google give you some sorta correspondence method so you can try and find out what's going on? I mean AtrackDog's great, but time consuming. Thanks if you try.
EDIT: Maybe this is my sinister way of trying to get a Snap Photo PRO update....not that I need one.
EDIT2: Seems I got my update (through AtrackDog of course). Sweet zooooom!! Thanks, Bratag!
At the risk of being a me too
Another user with this happening over here. Most of the time I "accidently" run across an update. Things seem to be a bit funky with the Market. Perhaps soon Google will HAVE to update it.
Yea same here so far I noticed 3 apps that had updates available but it didn't show in My Downloads so now I'm just using atrackdog until this issue is fixed, I'm wondering if this has anything to do with the ROM I'm using because I don't think I remember this happening before CyanogenMod 3.4.6.
_Kyros_ said:
Yea same here so far I noticed 3 apps that had updates available but it didn't show in My Downloads so now I'm just using atrackdog until this issue is fixed, I'm wondering if this has anything to do with the ROM I'm using because I don't think I remember this happening before CyanogenMod 3.4.6.
Click to expand...
Click to collapse
I really don't think it's a build issue. Google's got something screwy going on.
Hi,
I've found a way to solve the market issues and missing updates issue.
I'm running CyanogenMod-3.5.2.
These are the steps I recall I've done to fix the problem:
1) Open the Terminal and:
Code:
su
cd /data/system
mv packages.xml packages.xml.old
2) turn off and restart the phone,
packages.xml will be recreated
this can take a little time so be patient.
3) you have to enter your gmail account info again.
and some apps could forceclose.
4) turn off and turn on again.
5) I've run also the fix_permission script in the Terminal,
but maybe it is not necessary, so you can try to skip this step:
Code:
su
/system/bin/fix_permissions
6) run the Market app and you'll see Update available in My downloads,
if there are some updates for your apps, downloading and installing also
works again. (Sadly only initially then the problem of missing updates was there again)
7) You can delete packages.xml.old now if you want:
Code:
cd /data/system
su
rm packages.xml.old
That's it.
So far I've not noticed any malfunctioning, all my settings were retained
and all apps seem to work. Hope that I've not forgotten any important step,
(oops, I did..... ) so USE THIS AT YOUR OWN RISK.
Update:
Sadly the issues seemed to be fixed only initially in the sense that some Update available were shown in My downloads. It fixed downloading from the Market tough.
+1
I hope this issue gets fixed soon.
farmatito said:
[SOLVED]
Hi,
I've found a way to solve the market issues and missing updates issue.
I'm running CyanogenMod-3.5.2.
These are the steps I recall I've done to fix the problem:
1) Open the Terminal and:
Code:
cd /data/system
mv packages.xml packages.xml.old
2) reboot the phone,
packages.xml will be recreated
this may took a little time so be patient.
3) you have to enter your gmail account info again.
and some apps could forceclose.
4) reboot again
5) I've run also the fix_permission script in the Terminal,
but maybe it is not necessary, so you can try to skip this step:
Code:
/system/bin/fix_permissions
6) run the Market app and you'll see Update available in My downloads,
if there are some updates for your apps, downloading and installing also
works again.
7) You can delete packages.xml.old now if you want:
Code:
cd /data/system
rm packages.xml.old
That's it.
So far I've not noticed any malfunctioning, all my settings were retained
and all apps seem to work. Hope that I've not forgotten any important step,
so USE THIS AT YOUR OWN RISK.
Click to expand...
Click to collapse
Has anyone else been able to test this out yet? I am at work so I will not be able to test it until I get home. Please if anyone tests this and finds that it's working as well then we have a fix.
I tested it. Didnt have a great deal of success. Had to roll back to old package.xml. YMMV
A Little Good News
Checked "My Downloads" in the Market this morning, and at the top of the list was an "Update Available" for Pic Say Pro. I had not gotten that from the Market in about a week. No notification, however. Still, AtrackDog reports 5 updates available including that one so it's still not functioning properly.
biAji said:
I have this same issue since upgraded google map app to 3.1.1 .
JF 1.5 rom.
Click to expand...
Click to collapse
You know what, you may have hit the nail on the head. If I recall, I think I started having this same issue right about the time I upgraded my Google Maps application.
Is there anyone on this forum that may not have upgraded their Google Maps application, and can you confirm if you are still getting updates through My Downloads?
farmatito said:
[SOLVED]
Hi,
I've found a way to solve the market issues and missing updates issue.
I'm running CyanogenMod-3.5.2.
These are the steps I recall I've done to fix the problem:
1) Open the Terminal and:
Code:
cd /data/system
mv packages.xml packages.xml.old
2) reboot the phone,
packages.xml will be recreated
this may took a little time so be patient.
3) you have to enter your gmail account info again.
and some apps could forceclose.
4) reboot again
5) I've run also the fix_permission script in the Terminal,
but maybe it is not necessary, so you can try to skip this step:
Code:
/system/bin/fix_permissions
6) run the Market app and you'll see Update available in My downloads,
if there are some updates for your apps, downloading and installing also
works again.
7) You can delete packages.xml.old now if you want:
Code:
cd /data/system
rm packages.xml.old
That's it.
So far I've not noticed any malfunctioning, all my settings were retained
and all apps seem to work. Hope that I've not forgotten any important step,
so USE THIS AT YOUR OWN RISK.
Click to expand...
Click to collapse
i opened terminal emulator and tried the first step and right away it told me FAILED PERMISSIONS PACKAGES XML ACCESS DENIED
second step said to reboot so i assumed to do this while still inside the os. should i rebooted into recovery console and start from there...?
Good thinking on the Maps update. That's right about the time it started. Ironically (I'm sure you've seen) AtrackDog (AD from now on) reports a new version of maps, which is not available when you view it from the market. I'm sure there's a Google code page to check somewhere, though.
It's not google maps. I have the old version and still have new app versions not showing. Got to be a google server issue. The way the market is (overcrowded)... a better way of organizing apps is needed and seems to be on the way. My guess is on the next rc update. May have to wait until then for the my downloads fix too
Hi - NaN (not a noob) to software and hacking but new to this device.
I have a rooted TF101 and wonder if anyone's hacked the device so that the front camera becomes the rear and the rear camera becomes the front.
Really just curious before I go ahead and brick my device. I'm thinking about mv /dev/ov5640 and /dev/tegra_camera but that sounds far too easy (and dangerous)...
Why would You be interested in swapping the cameras anyways? Seems to be a biit pointless to me as every app ive used with cameras it had support to use front or back.
Sent from my Transformer TF101 using xda premium
I agree
kenshin1388 said:
Why would You be interested in swapping the cameras anyways? Seems to be a biit pointless to me as every app ive used with cameras it had support to use front or back.
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
I agree to this, there is no point to make the change.
Well for starters Opera 12, which includes support for getUserMedia() WebRTC extensions uses the first webcam it comes across, the rear. If I wanted to even make a mock up of a video call I would need the front camera (granted this is only good for the lab, not production).
But really I was trying to understand how the underlying media device capability works. If you simply exchange using mv /dev/mi1040 (the front camera device) and /dev/ov5640 (back camera) then it goofs the images to any app that uses cameras.
There must therefore be other layer(s) determining device capabilities, codecs, etc.
There's a file /etc/nvcamera.conf but that only seems to affect the main camera app. I swapped 1 and 0 and front and back tags, although admittedly haven't yet swapped the device ID whilst leaving the front/back tags the same.
And there's a whopping /etc/media_profiles.xml defining all the camera capabilities.
Do I need a reason? Isn't anyone even just curious doing something to push the device and learn more about the platform???
There was a point where Yahoo IM would use the back camera (when it was avaiable native to the TF). There was a member "droidx" he modified some files and got the front camera working with it. You're better off looking at modifying files as oppose to rewiring cameras.
More info here
http://forum.xda-developers.com/showthread.php?t=1087769
How to swap the cameras so Opera 12 uses front camera for getUserMedia()
Ok, here's how I did it.
Essentially you only need to swap the tags 'front' and 'back' in the file /etc/nvcamera.conf
The change is permanent across reboots, but messes the orientation/mirror image of the cameras, so the rear camera becomes a mirror image, not the front. This messes all portrait shots as the camera pic becomes upside down.
Device needs to be rooted.
Need to make /system directory read/write:
# mount -o rw,remount /system
# vi /etc/nvcamera.conf# format, cameraName=device,direction,orientation,type
This is the file before mods
# type can be 'stereo' for stereo capable, 'mono' for not stereo capable,
# 'usb' to enable searching for a usb device and where to put it in the list
# if found. Lines must be shorter then 256 characters
version=1
camera0=/dev/ov5640,back,0,mono
#camera1=/dev/ov5650,back,0,mono // 2nd camera for stereo once supported
camera1=/dev/mi1040,front,0,mono
#camera4=/dev/ov5650,back,0,stereo // virtual stereo device once supported
Change this line:
camera0=/dev/ov5640,back,0,mono
to:
camera0=/dev/ov5640,front,0,mono
And this line:
camera1=/dev/mi1040,front,0,mono
to:
camera1=/dev/mi1040,back,0,mono
Save and it works.
Please remove :/
No keep it, that's a good thing to have available to see or as a project. I love to learn things like this.
Thing O Doom said:
No keep it, that's a good thing to have available to see or as a project. I love to learn things like this.
Click to expand...
Click to collapse
I second doom. It's about pushing the limits of the device.
Good on ya for doing this.
Sent from my SCH-I500 using Tapatalk 2
I also agree. as some may not understand the reasoning, obviously oblonsky has a reason for doing this, just because everyone doesnt understand or agree with him is no reason to cut him off and remove his post... anything anyone learns or attempts to learn about android or the transformers code will progress understanding of the platform and the device. I vote let it stay and continue your endeavor fellow androidian.....
Yes, thanks guys. I'm already wondering now whether it may be possible to add new cameras, or disable cameras - do more useful stuff than swap cameras. Also I took the time to post the answer to my own question just in case it was useful to anyone else - so it would seem odd to want to remove the information that just *might* be useful to others at some point.
will this work on nougat......if not how to do it on nougat
Here is a reason to make the front camera the default camera: After getting in a terrible rain, my main camera on the back is not working anymore.
When starting a camera apps, it just quits with kind of a "connection to camera no possible" message.
Here's another reason to make the front camera as the default
I have a phone that's about 5 years old. It's been through heavy and rough usage. Hence, the connection between the motherboard and camera module are fried.
Now, when I have to login into WhatsApp Web or the WhatsApp App for Windows, I cannot because it needs a QR code scanned - which triggers the back camera.
So, I'm going to go ahead and try this, kudos!
Thanks for posting!
This was useful. Thanks. Please keep experimenting for no reasons.
SHUR1KEN said:
I have a phone that's about 5 years old. It's been through heavy and rough usage. Hence, the connection between the motherboard and camera module are fried.
Now, when I have to login into WhatsApp Web or the WhatsApp App for Windows, I cannot because it needs a QR code scanned - which triggers the back camera.
So, I'm going to go ahead and try this, kudos!
Click to expand...
Click to collapse
Uhm did it work?
Unfortunately, no, it didn't. Apparently, WhatsApp has gotten rid of the gate that used to allow for the "exploit" to happen before. I have heard of users doing it 2 years ago.
Anyway, what I had to do in my case was, I had to maintain pressure at the point on the camera module where it connects to the motherboard, while navigating to WhatsApp Web and scanning the QR code, all without even the most minute of movements. Otherwise the phone would fail to detect the camera module all over again, demanding me to repeat the whole thing again + a manual camera driver reset from my ROM settings.
Tried it like 20+ times. Succeeded in 1/20 of them... **** was tough, bro.
I finally managed to do this on my Redmi Note 5. This is probably applicable to most other devices as well.
Remount the system partition as writable:
Code:
$ su -c mount -o rw,remount /system
Edit /system/vendor/etc/camera/camera_config.xml and swap all
Code:
<Position>BACK</Position>
to
Code:
<Position>FRONT</Position>
and vice versa.
Reboot.
Do you think this will still work?
If I unroot after modifying the file, will the change persist?
Many thanks for your excellent work.
TheSnowpup said:
Do you think this will still work?
If I unroot after modifying the file, will the change persist?
Many thanks for your excellent work.
Click to expand...
Click to collapse
It still works for me at least. I think it will persist after unrooting, but I don't know how rooting works under the hood right now, so this may be incorrect.
If you try it, please report back your results!
Z1 (brand unknown) is wrist watch phone with Android OS. It was first released in 4/2012 and it is Android 2.2.1. It has WiFi, AGPS, GSM/EDGE, 2 MP camera, mic, speaker, loudspeaker, capacitive touchscreen, display of 320x240, SDHC & SIM card slots etc.
As most Chinese phones it has SoC from MediaTek, MT6516 (armv5).
See my Czech review for photos: http://hodinky.blog.mobilmania.cz/2012/06/z1-hodinko-telefon-s-androidem/
Tweaks/tips for stock ROM (2.2.1)
Market/Google Play is missing in stock rom but it cam be added if you follow instructions on the page: http://www.ibuygou.com/p-z1_smart_android_2_2_watch_phone_gps_wifi_bluetooth_html-3638-usd.html (included in Clean ROM)
Default DPI is 120 however most controls are too small. Change it to 160 which will make all icons sharp. (included in Clean ROM)
Typing on tiny QWERTY soft keyboard is a pain, Flit Keyboard makes entering text much easier. (included in Clean ROM)
To enter engineering mode, dial *#*#8787#*#*
ADWLauncher EX works even better if you (see):
Disable all animations including scrolling homescreen
Disable dockbar and use swipe up instead (included in Clean ROM)
4x3 icon layout for home screen and 5x2 for drawer (included in Clean ROM)
Use something like Extended controls for toggles
Use No Lock if you don't need swipe to unlock feature.
Remove alternative Chinese markets and Chinese network account/sync providers from /system/app (included in Clean ROM)
Creating flashable dump
Use MT6516 BackUpTool for dumping your stock rom.
Use MTK_Rom_Studio_1.0.0a for converting dump into flashable format.
Flashing
Basically you need the driver: "MT6516_YuSu_USB_VCOM.inf" and flashing tool: "SP Flash Tool v1.1110". All tools can be found on the internet when searching for "MT6516 flash tools". The only necessary tools reuploaded can be found also here. (I'm not sure about the legality of these tools though.)
You have to use 32 bit Windows (I only tried XP in both VirtualBox and VMware but it could work with 32 bit Vista or 7).
Power off the watch, connect it directly to PC (no USB hub or extention cable) - new device will connect for few seconds - use it to install the driver. Unplug watch. (You may retry that few times because the watch disconnect within few seconds) Open flashing tool and select files to flash (I would recommend not to flash anything other than boot/recovery/system/data/logo), hit start and quickly connect the watch - flashing will start automatically.
Recovery
First build of ClockworkMod 5.0.2.8 seems to be working however all its features were not tested yet!
Recovery can be flashed with "SP Flash Tool" (use provided scatter file).
Rebooting to recovery from launched Android using "reboot recovery" works but I wasn't able to find working button shortcut to launch recovery directly from cold start. Please help me if you find a way!
Custom Clean ROM based on stock 2.2.1
Features
Removed alternative Chinese markets and Chinese (social) network accounts
Integration of Google apps (sync, Google Play, setup wizard etc)
DPI changed to 160 which makes the watch easier to control and the icons sharper
Preconfigured ADW Launcher, Flit keyboard
Includes root with Superuser, Busybox binaries
Minor clean-ups
So far this ROM doesn't include anything power user from XDA wouldn't be able to customize but this ROM is afford to save other users time with experiments.
Important notes:
Backing up your current ROM + data is highly recommended (use the above listed MT6516 BackUpTool)
The seller says you shouldn't do factory reset because of IMEI lost - I can't confirmed that - IMEI is kept even during factory resets so it doesn't seem to be stored in user data partition. BUT backup your current ROM anyway cause I might be wrong.
Clean ROM notes:
The first boot is slow. After the first boot, I recommend not touching the watch for 5-10 minutes because dalvik cache is rebuilding in the background and the setup wizard may lag a lot.
The default ADW launcher is configured to not have app drawer button - swipe up to open drawer
Known issue (to be fixed later): Because of DPI change - Bottom row of button in Dialer is smaller, however all buttons can be pressed
Known issue (to be fixed later): Because of DPI change - Superuser (root) confirmation dialog buttons aren't readable however the buttons are partly visible and can be pressed (press bottom left button to allow root acces)
Known issue (to be fixed later): Because of DPI change - There is small graphical glitch on the lock screen which however doesn't break anything
Flashing recovery is not needed at all. Just make sure you flash both partitions (it will erase all your data on the watch but not on SD). Follow instructions above on how to flash.
ROM download: http://www.multiupload.nl/3LHJ33CW95
or http://www.multiupload.nl/JK6NOATJ57
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CM ROM
WIP, first build of CyanogenMod 7 (2.3.7) booted so I continue testing/evaluating. So far I only used stock kernel but I have source for MT6516 kernel.
Notes: WiFi chip - MediaTek MT5921 - no open source driver
Currently on hold.
Proofs
Flit Keyboard
moneytoo said:
Typing on tiny QWERTY soft keyboard is a pain, Flit Keyboard makes entering text much easier.
Click to expand...
Click to collapse
I actually have bought 3 Z1's and virtual keyboard is REALLY a pain..
Flit Keyboard makes entering text much easier ! !
Just Eight ( 8 ) >> Huge << Buttons Keyboard..
..that By Easily Sliding You Can Type:
>> All << Alphanumeric Characters And Symbols ! !
No More Accidentally Typing Wrong Characters ! !
Perfect 5..
(this Should Have Been THE Number One Android Keyboard..)
Thanks moneytoo ! !
ff
---------- Post added at 06:19 AM ---------- Previous post was at 06:16 AM ----------
Z1 Android Watch-Phone
From Wikipedia, the free encyclopedia:
http://en.wikipedia.org/wiki/Z1_Android_Watch-Phone
ff
Ive been thinking about buying the watch to use as a mp3 player, would you recomend it?
Sent from my NWZ-Z1000Series using xda app-developers app
Yes, I'm plugging my website, but hey, it's relevant.
I've just reviewed this device at:
http://linuxslate.com/Review_Z1_Android-2.2-Watch.html
Everything in this thread has been helpful, I just wanted to add my 2 cents.
DPI at 160 looks great. Unfortunately many apps will not fit, including keyboard, phone, and superuser prompt. Either find alternate keyboard and set superuser to auto-grant, or switch back and forth between 120 and 160 as necessary.
I like No Lock, but I find the phone wake-locking all the time until I turned No Lock off. I also like the fact that the time is there in big letters on the lock screen. It's very suitable for its watch functionality.
I did a manual backup without rooting (No need for Z4 Root)
Download and unrar MT6516 BackUpTool, but do not install anything.
On the Linux/Mac box, open the gscript folder, and open back22.sh in editor, or viewer.
Connect the watch via USB, and connect via adb shell
Cut, paste and execute each line from the back22.sh file
up to and including the last dd command in the first section - in other words
Code:
.
.
.
.
dd if=/dev/mtd/mtd11 of=/sdcard/backup_/expdb.img
Obviously, you don't do the comment lines.
exit the shell
Code:
exit
do:
Code:
adb remount
Install yaffs2image:
Code:
adb push <your_path_on_PC_to>/Install/BackUp/yaffs_back_2.2/gen/mkyaffs2image /system/bin/mkyaffs2image
Code:
adb shell chmod 4777 /system/bin/mkyaffs2image
(Again, the above is a cut and paste from the script)
Code:
adb remount
(for safety)
Code:
adb shell
Then cut and paste the remaining 3 mkyaffs2img commands.
Then:
Code:
exit
Copy the backup_ folder on the SD car to someplace safe.
If you want, you can remove mkyaffsimg:
Code:
adb remount
Code:
adb shell rm /system/bin/mkyaffs2image
Code:
adb remount
It's definitely more steps, but it leaves the system technically un-touched, un-rooted, and even returnable if you should have to.
Some more useful apps.
https://play.google.com/store/apps/details?id=com.coinsoft.android.orientcontrol
Orientation control to lock the screen in landscape mode; not free but worth it.
https://play.google.com/store/apps/details?id=itosisato.setsunasato.kokoroduyosato
Home button for soft home button in notification tray. Free.
https://play.google.com/store/apps/details?id=com.katecca.screenofflock
Off button in notification tray. Free.
https://play.google.com/store/apps/details?id=com.opera.mini.android
Opera mini has server side compression so makes best use of the slow 3g speed, but no multitouch so zooming is difficult.
m34n1ng said:
Ive been thinking about buying the watch to use as a mp3 player, would you recomend it?
Sent from my NWZ-Z1000Series using xda app-developers app
Click to expand...
Click to collapse
It can be done, but the MotoActv might be better, because the motoactv has a headphone jack so you can use any headphones you want. On the Z1, you have to use bluetooth headphones or a bluetooth headphone adapter.
I just ordered one of these last week, should have arrived today ... glad to see this exists!
Other than configuration/display-size issues, does everything work, i.e. all hardware? I noticed you had a note about the Wifi driver not being open source, but I assume that more effects if you try the MT6516 kernel. Even if it's a closed binary, I assume you could still load it and use it though. I'm not expecting any leaps and bounds in the kernel department.
As for CWM, is any part of it executed at cold boot? If so, I imagine you'd need to implement some kind of timeout menu that could optionally enter recovery before booting the watch. This is similar to what was implemented on the Kindle Fire which also doesn't have a normal stock recovery mode.
I assume you're still evaluating CM7 so you're not ready to distribute it ... but I do hope to see more from you soon, especially a HOWTO and download links!
I spent many nights trying to make GSM or WiFi working. Except few tweaks I only got the modem to start but nothing more. I have no experience with porting of binary drivers and this device has so many of them. Radio/modem and kernel modules - there are no problems with them but there are just too many dependencies on proprietary libs even from standard android native binaries.
So I'm giving up. At least for now cause I just don't have enough knowledge.
I consider making custom rom based on stock Android but I don't know if there would be any demand. Proper integration of Google apps, Chinese apps/account providers removed, tweaked launcher/drawer settings, tweaked global dpi/dpi of apps that not fit...
To have at least something, I give you very simple app "Z1 Backlight Toggle" apk (attached in 1st post) which can turn off completely display backlight. (Needs root) I use it on my bike when I have navigation running all the time cause it indeed saves battery and backlight isn't needed at all under direct sunlight, the display is readable the same.
moneytoo said:
I spent many nights trying to make GSM or WiFi working. Except few tweaks I only got the modem to start but nothing more. I have no experience with porting of binary drivers and this device has so many of them. Radio/modem and kernel modules - there are no problems with them but there are just too many dependencies on proprietary libs even from standard android native binaries.
So I'm giving up. At least for now cause I just don't have enough knowledge.
Click to expand...
Click to collapse
That's fine, I understand how frustrating these things can be. But still, can you post information about how to backup / restore the firmware and how to flash a custom ROM? I might try playing with it myself sometime and at least having the knowledge would enable further experimentation.
WTF!!!! a wrist phone with Android OS.... This is so freaking cool!!! :thumbup:
Awesome......
Sent from my GT-S7500 using xda premium
moneytoo said:
I spent many nights trying to make GSM or WiFi working. Except few tweaks I only got the modem to start but nothing more. I have no experience with porting of binary drivers and this device has so many of them. Radio/modem and kernel modules - there are no problems with them but there are just too many dependencies on proprietary libs even from standard android native binaries.
So I'm giving up. At least for now cause I just don't have enough knowledge.
Click to expand...
Click to collapse
I have an idea ... if we can get the MTK6516 kernel to build and boot, that's one step. If we can then get Android 2.2 stock to build, and then compare it against an image of the Z1's file system, we should, in theory, be able to identify all the unique areas of the watch's Android setup. If we at least know how to build an identical watch Android from source we should be able to extend that into making Cyanogen Mod work ... or something else. I think it's worth a shot anyway!
Also for an identical kernel, there shouldn't be any need to "port" binary drivers ... ideally they're built-in or load as modules, same as any other drivers.
I consider making custom rom based on stock Android but I don't know if there would be any demand.
Click to expand...
Click to collapse
You're probably right there will be very limited demand. So I ask again, if you can at least post steps about reflashing the watch, I'll give it my best shot. I just want to be sure I can restore the watch after messing around with it. Which I'm guessing you were able to since you didn't claim any permanent damage. It seems it should be able to go into a factory restore mode which I hope will override any messed up systems.
lokeshsaini94 said:
WTF!!!! a wrist phone with Android OS.... This is so freaking cool!!! :thumbup:
Awesome......
Click to expand...
Click to collapse
It really is neat. Kind of limited, but really neat. I think if we can get any amount of control over the kernel and Android version, we can really extend the abilities of the watch. It just needs a chance...
southbird said:
I have an idea ... if we can get the MTK6516 kernel to build and boot, that's one step. If we can then get Android 2.2 stock to build, and then compare it against an image of the Z1's file system, we should, in theory, be able to identify all the unique areas of the watch's Android setup. If we at least know how to build an identical watch Android from source we should be able to extend that into making Cyanogen Mod work ... or something else. I think it's worth a shot anyway!
Also for an identical kernel, there shouldn't be any need to "port" binary drivers ... ideally they're built-in or load as modules, same as any other drivers.
Click to expand...
Click to collapse
In my opinion there's no problem with kernel, modules or libraries, we can just reuse them. The real issue I think is native android binaries such as wpa_supplicant or rild. We can either use (original) already built binaries or build new ones - but this is the problem... Original binaries depend on proprietary libraries so they "do something" important with devices. Newly build binaries just don't have that unknown functionality. Yes, reusing stock binaries might work for 2.2 but my only target so far was 2.3 since that would be real benefit for us.
southbird said:
So I ask again, if you can at least post steps about reflashing the watch, I'll give it my best shot.
Click to expand...
Click to collapse
Have a look here: http://bm-smartphone-reviews.blogspot.cz/2011/02/mtk-hd2-hd9-flashing-tutorial.html
Basically you need the driver: "MT6516_YuSu_USB_VCOM.inf" and flashing tool: "SP Flash Tool v1.1110". You have to use 32 bit Windows (I only tried XP in both VirtualBox and VMware but it could work with 32 bit Vista or 7 as well).
Power off the watch, connect it directly to PC (no USB hub or extention cable) - new device will connect for few seconds - use it to install the driver. Unplug watch. Open flashing tool and select files to flash (I would recommend not to flash anything other than boot/recovery/system/data/logo), hit start and quickly connect the watch - flashing will start automatically.
moneytoo said:
To have at least something, I give you very simple app "Z1 Backlight Toggle" apk (attached in 1st post) which can turn off completely display backlight. (Needs root) I use it on my bike when I have navigation running all the time cause it indeed saves battery and backlight isn't needed at all under direct sunlight, the display is readable the same.
Click to expand...
Click to collapse
Which navigation software are you using?
adthor said:
Which navigation software are you using?
Click to expand...
Click to collapse
No idea what he's using, but I'll say that Sygic worked when NOT navigating (doing a route caused it to force close, I'm guessing possibly out of memory??) Using OsmAnd works pretty well ... of course, it's Open Street Map with all the usual limitations.
adthor said:
Which navigation software are you using?
Click to expand...
Click to collapse
I use RMaps (https://play.google.com/store/apps/details?id=com.robert.maps&hl=en) with collection of offline maps and prepared tracks for navigation.
southbird said:
No idea what he's using,
but I'll say that Sygic worked when NOT navigating
(doing a route caused it to force close, I'm guessing possibly out of memory??)
Using OsmAnd works pretty well ... of course, it's Open Street Map
with all the usual limitations.
Click to expand...
Click to collapse
Sygic 10 works nice with Z1 using 3D maps.
Sygic 12 works nice with Z1 using 2D maps.
When attempting to navigate Sygic 12 with 3D maps enabled,
the Sygic 12 crashes and Z1 returns to Home screen.
Correction..
Sygic 12 works nice with Z1 using 3D maps
only when Autozoom is turned off:
Settings > Map > Autozoom [untick]
ff
I consider making custom rom based on stock Android but I don't know if there would be any demand. Proper integration of Google apps, Chinese apps/account providers removed, tweaked launcher/drawer settings, tweaked global dpi/dpi of apps that not fit...
Click to expand...
Click to collapse
That is exactly what needs to be done! If porting the binaries is not possible at the moment, why not go ahead with building with stock android, with proper google account and apps, and removing the chinese accounts.
Once you have tweaked launcher/drawer, tweaked dpi of apps that not fit etc done, it would be almost as good as running CM7. Any improvement would be a big improvement
I sincerely hope that you continue development, the demand for a stock ROM is sure to come as the device becomes more popular, as of now, there is nobody developing for Z1, that i know of.
apurvasrishti said:
That is exactly what needs to be done! If porting the binaries is not possible at the moment, why not go ahead with building with stock android, with proper google account and apps, and removing the chinese accounts.
Once you have tweaked launcher/drawer, tweaked dpi of apps that not fit etc done, it would be almost as good as running CM7. Any improvement would be a big improvement
I sincerely hope that you continue development, the demand for a stock ROM is sure to come as the device becomes more popular, as of now, there is nobody developing for Z1, that i know of.
Click to expand...
Click to collapse
I started cooking custom ROM based on the stock two days ago and I'm very happy with it. Proper integration of setup wizard, google apps, keyboard, dpi, orientation, better preconfigured launcher, working voice search etc.
ROM:
http://www.mediafire.com/download/wkzcatpp7az4r5f/LS-KK-v3.2-2014-10-17-ovation.zip
MD5:
http://www.mediafire.com/download/piwirf8ee421dqv/LS-KK-v3.2-2014-10-17-ovation.zip.md5sum
A shoutout and thanks goes out to Rhyang for his help with the Slimkat rom, (to which this is somewhat similar).
Compiled with Sabermod toolchains. 4.8 for the rom and 4.7.4 for the kernel.
O3 optimized.
I made an attempt to fix 'OK Google'. Dunno if it's working or not (haven't tested). If it's still broken then it will be in the board files and will be a bear to try and find....
Dunno, it seems to work fairly well (ALMOST as good as Cyanogenmod 10.1 ) I kinda like it in a way (except it's KitKat).
I'll try and upload some source later. My internet connection has been giving me problems lately (took four hours or so to upload this). Even with source this is somewhat difficult to compile anyways (I fought with it some).
Cheers!
Great. I'll download now and try it out today :good::good:
Oh man I love LiquidSmooth! I am using it on my phone and have never looked back.
I guess I will have to give this a try. Thanks a lot for this. Is it also running on your yellow kernel or something different?
Which Gapps file is used with the rom please?
Yes it's using the same kernel as Slimkat except that /sound and /drivers/mfd folders have been swapped out with their CM11 kernel counterparts.
If you go into settings and 'about tablet', you will find download links to two types of gapps, full and minimal.
Things are running well. OK Google doors not appear to work too well
Jon Lee said:
Yes it's using the same kernel as Slimkat except that /sound and /drivers/mfd folders have been swapped out with their CM11 kernel counterparts.
If you go into settings and 'about tablet', you will find download links to two types of gapps, full and minimal.
Click to expand...
Click to collapse
Hey Jon, thanks for yet another new rom. :good: Looking pretty cool so far but as already mentioned, "Ok Google" is not working properly. I swapped out your yellow kernel with the stock CM11 kernel and Google Now is working as it should.
Since I lack the capability to compile a kernel, I simply replaced the yellow kernel boot image and the entire modules folder in /system/lib with the CM11 boot image and modules folder. I hated to lose the yellow kernel as I feel that it has better performance than stock CM11 but I love using OK Google. Btw, I did the same with your Slim rom with similar positive results.
Also, I see in the build prop that the density is set to 320DPI instead of the standard 240. I happen to prefer 320 but I would think that the masses might want the standard density and would be wondering why their desktop looks so big.
Anyway, thanks again for your contributions. It's appreciated.
Mike T
Ooh, nice!
Wow, is this fast!
So many ROMs, so little time.
I've been using CM 11 nightlies for a couple months now and didn't have many complaints. The usual CM 11 screen flicker problem when charging, some screen black outs (and crashes) on a certain screen in one of my aviation apps. That was about it. CM 11 was fairly fast and incrementally getting better all the time.
CM 11 doesn't have zRAM built in (yet), so I got a lot of app restarts when switching between my high memory aviation moving maps and other apps. But we're trying an experimental zRAM build that's helping with the HD+'s limited RAM.
But then I got a wild hair and decided to look around in the HD forum to see if perhaps Jon had an OC kernel for CM 11. Then I found his build of Liquidsmooth for the HD+. I didn't want to spend a half day wiping and installing a completely different ROM. But I'm glad I did. Wow.
I don't know if it's the overclocking or the other tweaks or all the above, but my AnTuTu score jumped from 17300 to 19100! Thanks, Jon!
(Hotplug governor seems to work best for me in both LS and CM 11. Too early to tell, but battery life doesn't seem any worse in LS.)
I assume that LS does not force the CPU to 100% when running AnTuTu, as CM 11 does. So the 19100 is probably a realistic reflection of performance.
(I haven't experimented with the I/O scheduler yet. I left it set at fiops for now. (Supposedly best for flash memory. Heretofore I've always used Deadline.) I lowered the SD cache to 512, which I found worked best in CM 11. (Using SD Booster to make that change.) FWIW, I enabled the GPU Acceleration and Super Tweaks in LS. )
[FWIW, the word "compiler" is misspelled (twice) in the "Just in Time Complier [sic]" setting.]
I'm happy to report that the screen flickering/crashes are gone when on that special page in my aviation moving map that always flickered - and sometimes crashed - in CM 11. (Requiring that I disabled HW overlays in Developer Options in CM11.) And since I set the "Low Memory Killer" to "Light" in LS, it doesn't kill my apps as aggressively as CM 11 did. (Not apples and oranges, because I was running ART in CM 11, whereas LS implies you shouldn't even try ART.) LS should be even better with zRAM. (And the boot animation is better than the frowning, scary CM alien face. )
(Speaking of zRAM, I noticed that someone in the Slimkat forum is running zRAM on Slimkat. I read here that Slim and LS are kinda the same. Is there a way to turn zRAM on it LS?)
I'd be curious to know what the major differences are between LiquidSmooth and Slimkat. Since Jon says LS is "similar" to Slimkat, why does LS exist?
Not much I could find on the web about it. I looked at the Slim home page. It's main advantage seems to be fancy interface stuff. (Although LS has PIE too.) Kinda like a toned down version of PAC? But the LS home page is silent about what makes it better/different.
Like I need to spend another half day wiping and flashing can customizing another ROM. (Titanium Backup is supposed to save data/settings. If it does, it doesn't seem to work for me. I have to reset the Settings on my apps when I restore from Titanium.)
---------- Post added at 10:34 AM ---------- Previous post was at 10:21 AM ----------
Every trying for that last bit of performance, some questions:
Q: On zip align apps on boot. Should I expect a toast or a notification if an app needed to be zip aligned?
Q: In CM 11, there's a Developer's Option to kill an app with a long press of the Back button. (Seems to be different from swiping "closed" in Recents, in that it completely shuts down the app.) Is there a similar trick in LS?
Q: I updated the host file for disable ads. I got a message that it worked, 0/4. Zero out of Four? That doesn't sound right. Is it?
Q: In CM's Launcher settings, you can disable transitions, stop scrolling wallpaper, etc. But I can't find a way to disable transitions - especially in the App drawer - in LS. (I see ways to change the transitions, but none of the options have "None.") Where are they or what's the trick to kill them?
Q: Last, and this is more of a Slimkat design element, but shouldn't there be a "Close All" button in the Slim Recent panel?
PMikeP said:
Q: Last, and this is more of a Slimkat design element, but shouldn't there be a "Close All" button in the Slim Recent panel?
Click to expand...
Click to collapse
For a while SlimROMs said they wouldn't support this, but now you can close all apps in the recents panel with a two-finger pinch. I think they might even have a youtube video of this ...
I like Slim because it's minimalist -- no bloated theme engine and its associated bugs. That said, their drivers tend to be a little more out of date than CM. The framework source is also slightly different. This makes sharing code between the two a PIA sometimes. I have no familiarity with LS, so I'm not sure how applicable these comments are to it.
Looks like you've been busy Jon
rhyang said:
For a while SlimROMs said they wouldn't support this, but now you can close all apps in the recents panel with a two-finger pinch. I think they might even have a youtube video of this ...
Click to expand...
Click to collapse
Thanks. I found the pinch gesture serendipitously while trying to swipe away a running app in Recents. Still, it's problematic trying to get it to 'close all' all the time. I went back to stock Recents for now. (Favorites implementation in LS Recents might be nice, as they've implemented in Slim, but I haven't figured out how to invoke it in LS if it's there.)
Here's the device and vendor source as promised:
http://www.mediafire.com/download/z3llb4mauxo8m16/liquidsmooth.tar.gz
Let me know if you need help or any other source to build.
I kept this one very much "original"/plain, meaning I didn't add the zram script (or anything else extra).
To add zram to it, just extract the attached 60ZRM script to /system/etc/init.d
(make sure it is executable & root:shell owned), and reboot.
I believe as far as 'ok google' is concerned, the next step would be to compile with the normal vanilla Cyanogenmod defconfig (sorry, but I refuse to install Gapps just to test). Microphone works, mixer values are the same, so... There's a reason I disabled some of that IPv6 stuff...
Behind the scenes I've been (rather unsuccessfully) attempting a port of ION CMA Heap.
http://pastebin.com/J1Ptxz3W
(Which is why I shared the first build without adding any extras, because I knew I was going to break it immediately following).
BTW, I'm still very new at compiling android and it will take me some time to become better acquainted with the build process.
A hack to fix auditd error "protocol not supported"
Jon Lee said:
To add zram to it, just extract the attached 60ZRM script to /system/etc/init.d (make sure it is executable & root:shell owned), and reboot.
Click to expand...
Click to collapse
Thanks again Jon! The Permissions for your script file were correct from the start. I don't know how to make sure it was root:shell owned, but it worked nevertheless.
Now, a hack to stop auditd errors:
After I got my apps reinstalled and set late last night, I decided to run catlog, just to see what I could see.
LiquidSmooth is definitely quieter than CM 11. (In the sense of less processes starting and stopping.) To be fair, not quite apples to apples because I'm back to running Dalvik on LS and was running ART on CM 11. (ART comes alive frequently to trim memory.)
But there was one process in LS, that I didn't notice in CM 11, auditd, that just kept starting and stopping with an Error, "Protocol not supported."
Despite that fact that auditd is constantly trying to run, it doesn't stop one of the CPU cores from shutting down (with Hotplug governor), nor does it prevent the CPU from dropping to its lowest freq. So, in practice, it doesn't seem to be a problem. Still, it can't be good to have this one thread constantly starting and stopping and it bugged me.
Now, maybe I caused the problem, because I typically uninstall a lot of Google junk and I disable a lot of Google services in the junk I can't remove. (Boy, Google just keeps pinging and pinging you!) And I hadn't run catlog with a virgin build of LS to see if the auditd Error was there at first.
Having said that, I did find a few other people on Google asking about the same auditd Error. (Apparently, auditd is a process from Sun.)
On the assumption you all get the same Error too, the best way to stop this would be to find out why it's trying to start. And to stop it. (Duh.) But that's WAY beyond me. So instead, I simply renamed the auditd file in /system/bin (it's a binary) to auditd.old.
I cringe when I think about it, but it worked anyway. (Worked in the sense that I don't get the auditd Error anymore.)
(As I write this, I wonder if the "d" at the end of audit is Unix convention to signal a daemon? If so, the I suppose there's probably a start up folder or file somewhere in Linux that's trying to start it? Or do daemons start themselves?)
When streaming video on any room using yellow kernel I get occasional freezes that require powering off my nook
Can I use Yellow Kernel in CM 11?
webdroidmt said:
I swapped out your yellow kernel with the stock CM11 kernel and Google Now is working as it should.
Since I lack the capability to compile a kernel, I simply replaced the yellow kernel boot image and the entire modules folder in /system/lib with the CM11 boot image and modules folder.
Click to expand...
Click to collapse
Clever! So, then, can I do this in reverse and swap Jon' s OC kernel into a CM 11 build?
PMikeP said:
Clever! So, then, can I do this in reverse and swap Jon' s OC kernel into a CM 11 build?
Click to expand...
Click to collapse
Never tried but in theory, it should work. Best way to find out is to make a nandroid and try it.
Mike T
webdroidmt said:
Never tried but in theory, it should work. Best way to find out is to make a nandroid and try it.
Click to expand...
Click to collapse
I tried it. Unfortunately on first boot, after immediately getting the CM set up screen, I got the message "Unfortunately, the process com.android.phone has stopped." (It didn't even go thru the process of updating apps like it normally does after a clean wipe, so something seems wrong. I re-did a second Factory Resent and /system wipe. Still no joy.)
So let's make sure I'm doing what you did. I downloaded the latest CM Nightly zip. I have Jon's LS zip. I opened both archives in 7zip.
I took Jon's boot.img from the LS zip and copied over (and replaced) CM's boot.img. I did the same with the modules folder in /system/lib. Then I closed up 7zip and tried installing the new hybrid CM 11 zip file.
But, since you said that you found that "Ok Google" didn't work for you on LS with Jon's kernel, it occurs to me that maybe you made these changes in a running install? That is, I would first install a "stock" CM 11 Nightly and then, after it's running, go in and change boot.img and modules? (I think changing the boot img in the partition would be a challenge for me.)
PMikeP said:
I tried it. Unfortunately on first boot, after immediately getting the CM set up screen, I got the message "Unfortunately, the process com.android.phone has stopped." (It didn't even go thru the process of updating apps like it normally does after a clean wipe, so something seems wrong. I re-did a Factory Resent and /system wipe. Still no joy.)
So let's make sure I'm doing what you did. I downloaded the latest CM Nightly zip. I have Jon's LS zip. I opened both archives in 7zip.
I took Jon's boot.img from the LS zip and copied over (and replaced) CM's boot.img. I did the same with the modules folder in /system/lib. Then I closed up 7zip and tried installing the new hybrid CM 11 zip file.
But, since you said that you found that "Ok Google" didn't work for you on LS with Jon's kernel, it occurs to me that maybe you made these changes in a running install? That is, I would first install a "stock" CM 11 Nightly and then, after it's running, go in and change boot.img and modules? (I think changing the boot img in the partition would be a challenge for me.)
Click to expand...
Click to collapse
You did it right. I did a total clean install of the Liquid rom with the newly "implanted" CM11 kernel. I wouldn't mess around with the partitions, dangerous territory. :laugh:
There's possibly some "hook" that Yellow is looking for that is not contained in CM11.
After reading your post, I just decided to see if it would work in reverse. I also got the same process phone has stopped error. With the ease of making nandroid backups, stuff like this is always worth a try when it's something you want or need. I'm thrilled that it works the other way, as I do use "Ok Google" a lot on all my devices and this Liquid rom runs nicely on the Nook.
In addition, with the introduction of Lollipop, Google has revamped GN and it's even better to use than before.
Mike T
webdroidmt said:
You did it right. . . .
After reading your post, I just decided to see if it would work in reverse. I also got the same process phone has stopped error.
Click to expand...
Click to collapse
Good to know I'm not alone then. Oh well, it was a promising experiment.
(Last night I tried experimenting (hacking) to get zRAM to point to a swap file on /cache. Not really a LS thing, but I might write about it later.)
I tried installing this today and it ran really nice and smoothly, but it doesnt seem to have the full HD+ screen resolution. Seemed more like 720p than 1080, large fonts and icons, just a lower resolution. Am I missing a setting or is it not working at full resolution?
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.