apparently the time "fix" was switching from UTC to local.
guess what? I don't use windows. So of course my RTC is set to UTC not local.
so every time I boot remix it thinks local time is UTC.
anyone know how to switch it back to use UTC
the solution is not network time or manually change because that will reset my RTC.
update
default.prop contains persist.rtc_local_time=1
*gasp* you...you don't use windows? what *is* there else?
I use Arch, Solus, and Remix OS on my desktop.
And as this a subforum about Remix OS, a desktop-oriented version of Android, which in turn is based upon Linux, I'd say there is a lot beyond Windows.
moriel5 said:
I use Arch, Solus, and Remix OS on my desktop.
And as this a subforum about Remix OS, a desktop-oriented version of Android, which in turn is based upon Linux, I'd say there is a lot beyond Windows.
Click to expand...
Click to collapse
A desktop or laptop will use the time from your motherboard's BIOS before it gets the time from anywhere else. You could boot into ypur BIOS and see what the time is set to there.
I have Remix dual-booting on my laptop and in VirtualBox on my desktop, and Remix gets the time from the BIOS on both computers regardless of OS.
-BoneZ- said:
A desktop or laptop will use the time from your motherboard's BIOS before it gets the time from anywhere else. You could boot into ypur BIOS and see what the time is set to there.
I have Remix dual-booting on my laptop and in VirtualBox on my desktop, and Remix gets the time from the BIOS on both computers regardless of OS.
Click to expand...
Click to collapse
Same here about the BIOS.
-BoneZ- said:
A desktop or laptop will use the time from your motherboard's BIOS before it gets the time from anywhere else. You could boot into ypur BIOS and see what the time is set to there.
I have Remix dual-booting on my laptop and in VirtualBox on my desktop, and Remix gets the time from the BIOS on both computers regardless of OS.
Click to expand...
Click to collapse
I already said in the op it is set to UTC, changing it in the bios/uefi is not a solution because my 2/3 os's are using UTC which sets RTC to UTC. Remix doesn't use UTC it uses local now. Looks like nothing short of modify ramdisk will fix it
Maromi said:
I already said in the op it is set to UTC, changing it in the bios/uefi is not a solution because my 2/3 os's are using UTC which sets RTC to UTC. Remix doesn't use UTC it uses local now. Looks like nothing short of modify ramdisk will fix it
Click to expand...
Click to collapse
Does hwclock do what you need? Perhaps with setprop persist.rtc_local_time 0
HypoTurtle said:
Does hwclock do what you need? Perhaps with setprop persist.rtc_local_time 0
Click to expand...
Click to collapse
Hwclock is the same thing as changing it in bios/uefi menu. Its the system clock using local instead of UTC. Also it's default.prop so can't change it that way. Maybe the latest stable supersu? I noticed with the latest systemless xposed you don't need to modify ramdisk if using 2.76 systemless. Nvm about supersu
Maromi said:
Hwclock is the same thing as changing it in bios/uefi menu. Its the system clock using local instead of UTC. Also it's default.prop so can't change it that way. Maybe the latest stable supersu?
Click to expand...
Click to collapse
It can be changed that way. All persist.* entries - from default.prop/build.prop/local.prop etc. are saved to /data/property/* and they can be changed via setprop [or manually I guess]
HypoTurtle said:
It can be changed that way. All persist.* entries - from default.prop/build.prop/local.prop etc. are saved to /data/property/* and they can be changed via setprop [or manually I guess]
Click to expand...
Click to collapse
I did try it and /data/property value is 0 for it but it didn't change the clock. FYI I am using script to enforce it
Also found this
https://github.com/quanganh2627/and...47-Init-Setting-system-time-back-to-utc.patch
And source forge is down so I can't see the commit for it. I think something was removed
Update:
well i went ahead and changed persist.rtc_local_time=1 to 0 in the ramdisk.
no more rtc resetting when changing the time to local using network time settings now.
something must still be missing so i can change and save the time without network settings.
Also does anyone know how to disable the 4 finger touch minimize? The setting was removed and guess fast screen typing wasn't a concern?
Also screen brightness? Guess being a battery killer wasn't a concern either?
Related
I have been trying for a few weeks to install kali linux on my lg g3. So far with no luck I have tried every guide on the internet but all have failed me can someone give me a detailed walkthrough on how to do so? my sd card is formatted and partitioned to fat32. I wish to install kali to the second 14 gig partition I made and named ext2. my phone is rooted with busy box installed it is the lg g3 S990 runing stock rom 5.0.1
anyone have any experience with this?
Here are some screen shots
Here are some screen shots
I don't think that you can..... They don't offical support it and there is a lot of things you have to take into effect. For example kernel, arm version, and hardware, wifi chips, touch screen drivers and a WHOLE LOT MORE!.
What would you suggest then? I'm debating getting a nexus 7 and installing nethunter on it would that be better??? I've been able to get quite close to having it work
turatt said:
What would you suggest then? I'm debating getting a nexus 7 and installing nethunter on it would that be better??? I've been able to get quite close to having it work
Click to expand...
Click to collapse
You can try that
GOOD NEWS (maybe)
I am able to get kali running through the complete linux installer app BUT it appears to be missing all pentesting tools and has no gui because vnc viewer wont connect but it does at least behave the way the app makers say it should :/
turatt said:
I am able to get kali running through the complete linux installer app BUT it appears to be missing all pentesting tools and has no gui because vnc viewer wont connect but it does at least behave the way the app makers say it should :/
Click to expand...
Click to collapse
Well, that's a start...
You can try opening a terminal and running: sudo apt-get install aircrack-ng
It says files are corrupted and cannot be read :/ ithink I will try limbo pc emulator instead will post the results
turatt said:
It says files are corrupted and cannot be read :/ ithink I will try limbo pc emulator instead will post the results
Click to expand...
Click to collapse
OK
So after many weeks of working day and night I finally have time to sit and tinker will post updates in the coming days
turatt said:
So after many weeks of working day and night I finally have time to sit and tinker will post updates in the coming days
Click to expand...
Click to collapse
Have you just looked into installing it onto like raspberry pi or a Chromebook or something? It seems pretty easy..... Plusnit might work better then the phone.
If I can't get to work ill be switching to a nexus seven with nethunter. I found a guide on how to run kali in limbo pc emulator and it appears to work to some extent but I get no gui nothing. I fear the iso file may be corrupted. Ill post screenshots next
turatt said:
If I can't get to work ill be switching to a nexus seven with nethunter. I found a guide on how to run kali in limbo pc emulator and it appears to work to some extent but I get no gui nothing. I fear the iso file may be corrupted. Ill post screenshots next
Click to expand...
Click to collapse
Just install gnome fallback or something....
Or open a terminal and try running "startx"
Here are my screenshots.
http://ikrami.net/2014/05/26/kali-linux-android/
This is the guid I have been using^
Just tried again with a new iso and limbo stopped working I will try reinstalling and wipeing cache in recovery.
turatt said:
Just tried again with a new iso and limbo stopped working I will try reinstalling and wipeing cache in recovery.
Click to expand...
Click to collapse
It could just be the arm version of our phone.... What are you trying to do with Kali?
Just run it I have a pwn box for mobile hacking so I can bluesnarf and do alot of fun things. I'm doing freelance pin testing so I thought it would be nice to be able to do those things on my phone without having to lug my laptop out
turatt said:
Just run it I have a pwn box for mobile hacking so I can bluesnarf and do alot of fun things. I'm doing freelance pin testing so I thought it would be nice to be able to do those things on my phone without having to lug my laptop out
Click to expand...
Click to collapse
OK, cool
Then I guess the nexus 7 is your best guest unless you get something like a Samsung S2 and put it in monitor mode and use aircrack-ng. Also the raspberry pi thing is pretty good if your like pretty handy you can wire up a battery, pi, and screen then just use a wireless keyboard.
S2 link: https://www.google.com/url?sa=t&sou...mgJhCRpHtESmUYXTw&sig2=IeGml16hwDKXeV9V7JXwRg
You can install kali linux on linux deploy and run with android VNC
I am running with linux deploy it on my AT&T 3g.
Im pretty sure your problem is in your configuration on preferences. Generally the SD is formatted to FAT which has maximum image file size 4095 MB. So pretty much if you want kali tools then hypothetically you could reformat your SD or external to ext4. There is also a permissions problem because of the image location. Here's how I got around it for now, I just started altering this phone 2 days ago so I'll keep you updated if you want. I moved the environment location to a folder in SD and it has consistently held up to 6000MB which is plenty for the os, necessary additions and a few fun kali tools.
Here's my mini pictorial, it's only my second post so maybe this will help.
Just do the settings like mine, Wait forever while it installs then after it finishes hit reconfigure. It takes a couple of minutes to reconfigure then you press start and wait until it's finished loading, press your home button, open VNC, make sure your port is 5900 and default password is "change me"
Open up a terminal and type "sudo su" make a password, update and make sure you have fun.
When you're finished go back to linux deploy, press stop and then use the menu button to exit the app
Hello,
I have just installed remix os. (dual os though)
Problem is, bottom bar is solid black that means I can not use multitasking. I have to close one app to open another one. I can not also open setting etc.
What is this happening
At the first boot I had this problem too, then system automaticly rebooted and I had that bottom bar now It is again gone. I have really low notebook, has 2gigs of ram and 1.4ghz of cpi even linux freezes time to time. But so far, remix os running like a dream.
Btw, I am using 64bit version if it matters.
thanks in advance
Conixcit said:
Hello,
I have just installed remix os. (dual os though)
Problem is, bottom bar is solid black that means I can not use multitasking. I have to close one app to open another one. I can not also open setting etc.
What is this happening
At the first boot I had this problem too, then system automaticly rebooted and I had that bottom bar now It is again gone. I have really low notebook, has 2gigs of ram and 1.4ghz of cpi even linux freezes time to time. But so far, remix os running like a dream.
Btw, I am using 64bit version if it matters.
thanks in advance
Click to expand...
Click to collapse
Check the autohide settings. Settings ==> Display ==> Autohide (and right click on taskbar if you can)
HypoTurtle said:
Check the autohide settings. Settings ==> Display ==> Autohide (and right click on taskbar if you can)
Click to expand...
Click to collapse
First of all thanks for reply,
And it is not what you say, it isn't hidin problem is
Where running apps and stats should be covered with solid black, (same border)
Conixcit said:
First of all thanks for reply,
And it is not what you say, it isn't hidin problem is
Where running apps and stats should be covered with solid black, (same border)
Click to expand...
Click to collapse
I think I had what you're describing and toggling the autohide fixed it (i think there was a mismatch between the setting value and the right click value).
That being said it might be better to try the 32bit version on your device; it should be easier on resources.
I'll go one farther and say that you should not be running the 64-bit at all on that notebook. You don't have the hardware to properly support it. Upon initial installation you should have seen a pop-up telling you to make sure you are using the 32-bit version based on your hardware.
ZiQn3zZ said:
I'll go one farther and say that you should not be running the 64-bit at all on that notebook. You don't have the hardware to properly support it. Upon initial installation you should have seen a pop-up telling you to make sure you are using the 32-bit version based on your hardware.
Click to expand...
Click to collapse
I totally agree but 64 bit version is the only version that supports EFI ,
Conixcit said:
I totally agree but 64 bit version is the only version that supports EFI ,
Click to expand...
Click to collapse
I'm fairly sure replacing the system.img, kernel, initrd.img and ramdisk.img with the 32bit ones and removing the _64 from the grub.cfg will boot with efi grub... if you want to try
HypoTurtle said:
I'm fairly sure replacing the system.img, kernel, initrd.img and ramdisk.img with the 32bit ones and removing the _64 from the grub.cfg will boot with efi grub... if you want to try
Click to expand...
Click to collapse
What possibly can go wrong anyway?
It's my side OS anyway.
I'll try as soon as I reach home.
Conixcit said:
What possibly can go wrong anyway?
It's my side OS anyway.
I'll try as soon as I reach home.
Click to expand...
Click to collapse
I had the same problem, I fixed it by adding
ro.remixos.no_wallpaper=true
in build.prop where other ro.remixos options are configured
and also remove the 2 ffmpeg lines to remove blinking issue...
If you cannot open any application plug in any usb, es file explorer will appear then enable root explorer option
and navigate to /system to edit build.prop and finally edit it..
updesh94 said:
I had the same problem, I fixed it by adding
ro.remixos.no_wallpaper=true
in build.prop where other ro.remixos options are configured
and also remove the 2 ffmpeg lines to remove blinking issue...
If you cannot open any application plug in any usb, es file explorer will appear then enable root explorer option
and navigate to /system to edit build.prop and finally edit it..
Click to expand...
Click to collapse
where is exactly "build.prob" file.
I'm using Ubuntu
Conixcit said:
where is exactly "build.prob" file.
I'm using Ubuntu
Click to expand...
Click to collapse
It's within the system.img; within RemixOS it's at /system/build.prop.
But I don't think this is a fix per say - yes it seems to work for some people; but this could be due to some data hangover from a previous version with this line present.
What I would try first is simply clearing data from SystemUI (and Settings) app.
HypoTurtle said:
It's within the system.img; within RemixOS it's at /system/build.prop.
But I don't think this is a fix per say - yes it seems to work for some people; but this could be due to some data hangover from a previous version with this line present.
What I would try first is simply clearing data from SystemUI (and Settings) app.
Click to expand...
Click to collapse
Already done that. Not helps
Letme try that file editing thing
HypoTurtle said:
It's within the system.img; within RemixOS it's at /system/build.prop.
But I don't think this is a fix per say - yes it seems to work for some people; but this could be due to some data hangover from a previous version with this line present.
What I would try first is simply clearing data from SystemUI (and Settings) app.
Click to expand...
Click to collapse
Can't find that build.prob file....
Conixcit said:
Can't find that build.prob file....
Click to expand...
Click to collapse
You're dual booting with ubuntu, right?
If so then just mount the system.img and you'll see it righg there.
mkdir rossystem && mount -t ext4 system.img rossystem
or if your using a system folder then it should be just in there.
I had the same problem, I fixed it by adding in build.prop
ro.remixos.no_wallpaper=true
Hi all,
I have been given the task of turning 10x 'Fizzbook Spin' laptops into device a preschool could use.
I have windows 10 working but it is slow and have decided to look into the android route, this runs faster but also has many more apps for young children available. I installed Remix OS onto the laptop without issue (1.6Atom + 1Gb RAM) but have a couple of questions.
1. Can I install Remix OS without windows or any other operating system? I would like for them to turn the laptop on and it boots straight in to Remix.
2. As it is for pre-schoolers I would like to use this as a tablet type device, whereas tapping or swiping on the screen would act like an android tablet and not move the mouse cursor.
Is the above possible? If not does anyone have any recommendations for an android type operating system I could put on this device which would work in this manner?
Thank you very much for any advice
Darren
drunken_prozac said:
Hi all,
I have been given the task of turning 10x 'Fizzbook Spin' laptops into device a preschool could use.
I have windows 10 working but it is slow and have decided to look into the android route, this runs faster but also has many more apps for young children available. I installed Remix OS onto the laptop without issue (1.6Atom + 1Gb RAM) but have a couple of questions.
1. Can I install Remix OS without windows or any other operating system? I would like for them to turn the laptop on and it boots straight in to Remix.
2. As it is for pre-schoolers I would like to use this as a tablet type device, whereas tapping or swiping on the screen would act like an android tablet and not move the mouse cursor.
Is the above possible? If not does anyone have any recommendations for an android type operating system I could put on this device which would work in this manner?
Thank you very much for any advice
Darren
Click to expand...
Click to collapse
About #1: Yes, you could.
Instead of installing with the official installer, flash Remix OS with it to a flash drive, and from Grub, press tab and replace what is written with "install=1 debug=" (important: "debug=" has nothing following it), and follow the instructions (I recommend creating and installing to an ext4 partition).
About #2: I have no idea, perhaps there is something in build.prop, I remember people talking about a line set to false, with "box" in it.
By the way, don't you want to try Phoenix OS?
It's supposed to be more stable.
And you could always try the original Android-x86.
moriel5 said:
About #1: Yes, you could.
Instead of installing with the official installer, flash Remix OS with it to a flash drive, and from Grub, press tab and replace what is written with "install=1 debug=" (important: "debug=" has nothing following it), and follow the instructions (I recommend creating and installing to an ext4 partition).
About #2: I have no idea, perhaps there is something in build.prop, I remember people talking about a line set to false, with "box" in it.
By the way, don't you want to try Phoenix OS?
It's supposed to be more stable.
And you could always try the original Android-x86.
Click to expand...
Click to collapse
Thanks for the reply,
I'm kinda new to this so don't know much linux
Phonenix OS I've seen about but didn't know which was more stable, I will try it tonight.
I've been assigned as the 'dad who knows about computers' at my sons nursery so they offload all the technical stuff off to me and ask if I can "make it work"
Just need to make it simple and easy for a 3yr old to play colouring games and ABC learning games on
drunken_prozac said:
Thanks for the reply,
I'm kinda new to this so don't know much linux
Phonenix OS I've seen about but didn't know which was more stable, I will try it tonight.
I've been assigned as the 'dad who knows about computers' at my sons nursery so they offload all the technical stuff off to me and ask if I can "make it work"
Just need to make it simple and easy for a 3yr old to play colouring games and ABC learning games on
Click to expand...
Click to collapse
Don't worry, I know exactly what it feels like, except in my case, it is "the older brother who is an expert in computers" at my sister's school, althoigh I'm no expert, but a computer passionist.
However, I do use Linux on my desktop, since it's much better than Windows in almost every way.
Unfortunately, there are many day-to-day apps on Windows that don't have an up to par Linux equivalent, unless you only use Latin-based languages, and possibly(?) slavic ones as well, no idea about far-east ones, though.
1. Can I install Remix OS without windows or any other operating system? I would like for them to turn the laptop on and it boots straight in to Remix.
Suggestion:
Use Windows to install Remix
Use EasyBCD to modify the boot default to Remix and set timeout to 2 seconds. It appears to boot directly to Remix
2. As it is for pre-schoolers I would like to use this as a tablet type device, whereas tapping or swiping on the screen would act like an android tablet and not move the mouse cursor.
Suggestion:
Use this method to disable the touchpad
http://forum.xda-developers.com/remix/remix-os/root-how-to-deactivate-device-remix-os-t3358963
Worked for me in same situation
Sent from my on Z00A using XDA Labs
This is my first time posting on the website so I apologise ahead of time. I am trying to dual boot my laptop with Remix OS. It is the Asus ROG GL551JW-DS71 (i7 4720hq, 16 gb ram, 1 tb hdd, gtx 960m, windows 8.1, if anything else is needed, let me know). I've done some research and it seems that it might be an issue with my GPU. I've tried putting the "nouveau.modeset =" and what not but I can't get it to load past the "ANDROID [email protected]_x86_64:/ #" I put "DEBUG=1" in the Grub line thing and I took pictures of my screen. I'm not sure what site you guys would like me to use to upload so I'll upload them once someone lets me know. Thanks in advance!
Have you searched for a disable dedicated/discrete graphics in BIOS? You need to disable it, because Remix will not boot with your GTX960M enabled.
If you don't have that option, then I'm sorry but for now you will be able to boot only using software rendering; graphics handled by the CPU. This means a less stable experience and less performance, but it will work 100%
Add this in the kernel grub line:
Code:
androidboot.swrast=1
Sent from mobile
ethansky said:
This is my first time posting on the website so I apologise ahead of time. I am trying to dual boot my laptop with Remix OS. It is the Asus ROG GL551JW-DS71 (i7 4720hq, 16 gb ram, 1 tb hdd, gtx 960m, windows 8.1, if anything else is needed, let me know). I've done some research and it seems that it might be an issue with my GPU. I've tried putting the "nouveau.modeset =" and what not but I can't get it to load past the "ANDROID [email protected]_x86_64:/ #" I put "DEBUG=1" in the Grub line thing and I took pictures of my screen. I'm not sure what site you guys would like me to use to upload so I'll upload them once someone lets me know. Thanks in advance!
Click to expand...
Click to collapse
Try to add "nomodeset" instead of "nouveau.modeset =".
nomodeset might work, but it's highly unlikely.
I've made a guide for these kind of problems today: http://forum.xda-developers.com/remix/remix-os/solution-problems-booting-remix-os-dual-t3466027
Vioner said:
Have you searched for a disable dedicated/discrete graphics in BIOS? You need to disable it, because Remix will not boot with your GTX960M enabled.
If you don't have that option, then I'm sorry but for now you will be able to boot only using software rendering; graphics handled by the CPU. This means a less stable experience and less performance, but it will work 100%
Add this in the kernel grub line:
Code:
androidboot.swrast=1
Sent from mobile
Click to expand...
Click to collapse
I have looked for that option in my bios and I couldn't find it. I forgot to mention in my original posting that I had my Windows reinstalled with because the hard drive failed. I don't believe that I have the option to boot to the UEFI so I wonder if that has to do anything. I tried putting the "androidboot.swrast=1" code after the kernel line in the GRUB line editor thingy and I got it to boot. It's a bit unstable and the screen tends to tear when I move a large window around. The only problem now is how to make it permanent. I tried editing the file that was mentioned in some guides but it doesn't seem to stick.
tomekumb said:
Try to add "nomodeset" instead of "nouveau.modeset =".
Click to expand...
Click to collapse
I have tried both of the commands and it still hands at the Android root part. Are there any other commands or combination of commands that could work? I don't have an option in my bios to disable my gtx 960m and there isn't an option to boot to the UEFI. I wonder if the Windows reinstall due to a hard drive failure has something to do with it. Thanks in advance!
Hey guys,
I recently installed RemixOS 3.0.204 on an Acer Alpha Switch 12, and since I'm running it with Windows 10 but I intend to install some Linux flavor later on, I decided to go ahead and use rEFInd for multibooting (there's also the fact that RemixOS' GRUB wouldn't show up anywhere in my system).
My question at this point regards the default GRUB installed with RemixOS; I can't seem to find the configuration that's running anywhere. I found a couple of grub.cfg files on /EFI/RemixOS/efi/RemixOS (namely grub.cfg, grub32.cfg, grub64.cfg), but editing any or all of these had no impact whatsoever on my GRUB entries. Would anyone be able to help me either remove the GRUB menu altogether or customize it, at least?
Thanks in advance.
EDIT: if anyone's looking for a similar solution, you'll very likely need to mount your computer's EFI partition like I did - the one that would show up is probably the EFI folder on RemixOS installation files. To do that, I had to look into /dev/block and my partitions were listed as sdaX, so chances are you'll find a similar setup for your computer. Good luck!
UEFI boot uses EFI:/boot/grub/grub.cfg file for the menuentry details - edit this one.
Vioner said:
UEFI boot uses EFI:/boot/grub/grub.cfg file for the menuentry details - edit this one.
Click to expand...
Click to collapse
I finally managed to find out what I was doing wrong; I assumed a device listed in /storage was my EFI partition, but it turns out it was probably just the EFI folder from RemixOS original installation. I managed to find my EFI on /dev/block/sda1 and editing grub.cfg was spot on.
Thanks for the help, buddy!
GryphonBR said:
Hey guys,
I recently installed RemixOS 3.0.204 on an Acer Alpha Switch 12, and since I'm running it with Windows 10 but I intend to install some Linux flavor later on, I decided to go ahead and use rEFInd for multibooting (there's also the fact that RemixOS' GRUB wouldn't show up anywhere in my system).
My question at this point regards the default GRUB installed with RemixOS; I can't seem to find the configuration that's running anywhere. I found a couple of grub.cfg files on /EFI/RemixOS/efi/RemixOS (namely grub.cfg, grub32.cfg, grub64.cfg), but editing any or all of these had no impact whatsoever on my GRUB entries. Would anyone be able to help me either remove the GRUB menu altogether or customize it, at least?
Thanks in advance.
EDIT: if anyone's looking for a similar solution, you'll very likely need to mount your computer's EFI partition like I did - the one that would show up is probably the EFI folder on RemixOS installation files. To do that, I had to look into /dev/block and my partitions were listed as sdaX, so chances are you'll find a similar setup for your computer. Good luck!
Click to expand...
Click to collapse
How is Remix running on your switch 12; does everything work properly?
Ludespeed said:
How is Remix running on your switch 12; does everything work properly?
Click to expand...
Click to collapse
Yep, every little thing. The one gripe I've had is when I connect the charger with the computer on standby from Remix OS - not sure what is causing it, but it will reset and I have to do a cold start to get it back to work. But if I take the time to wake it up, connect the charger and then put it back to sleep, no problems.
But other than that, everything is great - sound, WiFi, every port... Oh, one more annoyance - the physical volume keys don't work out of the box. I might be able to get them to, but for now I don't care much about it. And one thing I haven't tried at all is the internal gyroscope, to see if the screen rotates automatically.