yashsingh1/xdaforums huggingface dataset:
[Android Software Development] HypoTurtle:
Stock RemixOS Beta, runs with a reported 4.4.2 kernel with as expected wifi not working, switching to the 4.4.0 kernel/modules/firmware we are currently using will work, but I'd rather wait until when/if the kernel source is released.

EDIT. Cube i7 Stylus kernel + modules attached. These are taken from RemixOS Alpha - so it's the kernel [MENTION=3468267]asplash[/MENTION] compiled. You need a rooted system.img or unpack/repack system.img within Windows/Linux. Just copy files over / and run the sh while running to set permissions. Then switch the kernel.

Too big to attach so available here
[Android Software Development] HypoTurtle:
Just a couple of screenshots, it's seems very few people have figured out how to get rotation to work, and I'm sure even fewer have found how to enable apps like Twilight, Lux or Tincore Keymapper...

I'll post procedure in a bit just making sure it doesn't irreversibly mess with anything.
[Android Software Development] KamaL:
Thanks.

Can you explain step by step how to do it?

Also, any improvements over the previous builds in terms of battery consumption and sleep mode?

Thanks
[Android Software Development] leo06:
<MOD EDIT - Non-English Quote Removed.>

Bluetooth not working (same with remix os) for me and I expand data.img with RMXtools but still in android I see 3gb,is there other way to expand?and i can see only 2678MB of ram
[Android Software Development] leo06:
Thanks,bt is working now,for data.img and ram?
[Android Software Development] asplash:
<MOD EDIT> data.img
[Android Software Development] HypoTurtle:
Download it and have a look it should be fairly clear simpilest way is to copy to somewhere you can mount in android (usb, sdcard etc.), then with root file browser copy over, then replace the kernel.

Alternatively use something like RMXTools to open the system.img, copy the files over then repack system, boot, fix module permissions, then switch kernel.

Jide have just released their 4.4.y sources, so going to compile (at least the wifi driver) asap unless [MENTION=3468267]asplash[/MENTION] is already setup for a compile. There is a benefit with it at least with exfat (my exfat partitioned sdcard auto mounts with 4.4.2 but not with 4.4.0).
[Android Software Development] leo06:
Do you know why i can't see usb stick and sd card in es file explorer?
[Android Software Development] leo06:
The usb i formated from inside android but still i can't see from es file explorer and sd card is ntfs,i can see both from settings
[Android Software Development] asplash:
/mnt/media_rw/****
[Android Software Development] leo06:
Can we install xposed framework in Android?
[Android Software Development] leo06:
I answer to myself for 3gb of ram, just realized that is x86 not x64
[Android Software Development] ariadnejro:
[MENTION=3468267]asplash[/MENTION]

Thank you for your great work on Android for the Cube.

About your latest CM13 ROM:

-Deep sleep seems to work (at last). After coming back from sleep brightness goes up and the device remains unresponsive for a while but after pressing the Windows button everything comes back to normal.

-My 128 GB NTFS formatted MicroSD card can be read from settings and from a file explorer using /mnt/media_rw, but it isn't easily accessible from many apps.

-Battery level isn't read properly, it shows 100% all the time.

-Built-in root doesn't remember a previously granted access, installing SuperSU solves the problem.

-The app GMD Gesture Control (a must have for me) doesn't recognize the touchscreen device. It worked on your Lollipop ROM.

-Only 3 Gb of RAM seem to be accessible, your Lollipop ROM aparently could see the full 4 GB.

-The device doesn't boot with the 8 Gb data.img, it gets stuck on the boot animation.

Speaking about your Lollipop ROM, it's been my Android choice for more than a month. Since its only drawback was the inability to enter deep sleep it would be lovely if you could post a new Lollipop ROM with that issue solved.
[Android Software Development] leo06:
For the battery it happens the same to me but after reboot is OK, drops by 4,5,8% and not by 1%,i mean now is 55% and after some time it shows 50%,for 3gb of ram self-test my previous post, it's 32bit Version of Android so only see 3gb,for data.img I use wootever 6gb data.img and it works
[Android Software Development] KamaL:
[MENTION=3468267]asplash[/MENTION]

Thanks for another android release! You're doing a great job!

I can second most reports from [MENTION=917500]ariadnejro[/MENTION]:

-Deep sleep works fine , but I couldn't find a way to shut it down. A long press of the power button leads to a restart.

-I have a 64GB NTFS formatted Kingstom MicroSD card , the device shows that the card is corrupt and suggests to fix it.

I can't access the files through a file explorer using /mnt/media_rw, as it shows an empty folder named "1234-567".

I don't intend to format the card as I want to share the data with Windows.

maybe [MENTION=4056517]HypoTurtle[/MENTION] can check this out? Does the previous script work to mount the SD card?

- Battery level is always at 100%, so I couldn't test whether battery consumption is still excessive as is the case with all previous Android builds.

Let's how for fixes for this release.

Keep up the great work!!
[Android Software Development] HypoTurtle:
I have the 4.4.y kernel building and booting; but the modules don't appear to be being picked up, will try again tomorrow. [MENTION=3468267]asplash[/MENTION] anything special needed to compile properly? I'm not running a full build, just the kernel (don't have the time/space for a full ROM build), is there a specific gcc needed (I figured not so am just using latest gcc on ubuntu) or something...

It's probably something to do with the modules.* files, I'll try a compile tomorrow with hid as internal kernel module, so I can at least 'use' it...

Edit. 4.4.2 kernel can be found here - specifically for cube i7 stylus; but might be of some use to devices using/needing rtl8723bu module - also added to #1
[Android Software Development] KamaL:
I can't seem to find the link to the latest CM13 release by [MENTION=3468267]asplash[/MENTION]. It seems that a moderator deleted it.

Can anyone post it once again please?

EDIT:

I found the link, here you go:

https://drive.google.com/uc?id=0B0WGrG69YnsySkJPdVR3VGlnR1k&export=download
[Android Software Development] HypoTurtle:
RemixOS Beta2 (1503 OTA applied) available here

It's stock with a custom 4.4.2 kernel; 8723bu added, iio fixed and touchscreen 'fix' added to init.sh

Stock kernel is 4.4.5, and will need to wait for Jide to publish this branch before updating custom kernel.
[Android Software Development] leo06:
can I keep data.img from previous beta?
[Android Software Development] HypoTurtle:
I have, and that's how the intended OTA is supposed to work.

If need be; clearing the data of system apps would more than suffice.

One thing I was waiting for with the OTA was a look at if there was anything non standard in it; and there appears not be.

The ota makes use of a x86update elf binary from within the initrd.img; which appears to be the (hopefully not too trimmed down) innerds of a recovery; will check tomorrow if the mechanic can be used simply as a way tk install update.zip's like SuperSU == that's one of the reasons the Beta2 I uploaded wasn't system rooted (stock ALT&F1 is a root shell and I've modified it so it has rw access to /system)
[Android Software Development] KamaL:
I've been using this release for a couple of days. Although I didn't test it thoroughly., I can say it works really well!

My impressions:

- release is very stable and fast

- battery indicator works

- wifi works

- HW acceleration in MX player works

- battery consumption seems to be better than previous releases

problems:

- no screen rotation!

- stand by - after coming back from standby, touch screen doesn't work and wifi disconnects. solution - press the windows key and the power button once again, and reset wifi connection.

- no Play Store and root access. I hope you can add these in future releases.

Keep up the awesome work!!
[Android Software Development] HypoTurtle:
Have a look here for root and rotation issues.

I'm using the systemless-root atm; it's should be painless.

Rotation is fine here; it's probably the forced landscape that you are getting - also Ithink I left the stock inverted libs -- there's a copy of the fixed libs in the same folder as the ROM,just copy those across once rooted.

Probably need [MENTION=4709667]Wootever[/MENTION] / [MENTION=3468267]asplash[/MENTION]'s take on the standby stuff or the best way to workaround it ; there are few things that need to be essentially replugged (rmmod/modprobe) rotaionand wifi being among them. I've looked through modinfo (not sure if wifi low_power andother modprobe argument are something we should look at)also tried to device a way of rmmod/modprobing all modules that are not builtin (haven't finished that yet -- I'd guess I'd simply need to use lsmod and modules.builtin

PlayStore is there (by default in stock; just disabled) == if you used a data.img that was running with Gapps they should be automatically usable. If you could download PlayStore from apkmirror, reboot and see if you have PlayStore and other gapps; I believe this should 'activate' the preinstalled system apks.
[Android Software Development] KamaL:
I tried the systemless-root, but I can't seem to be able to copy the su.img fle to the /data/ folder.

I pressy ALT and the F1, get into the command line, and then run this line: "#cp /data/media/0/Download/su.img /data/su.img", but nothing happens, the file doesn't get copied to the /data/ folder

I'll try that once I can get it rooted.

I tried the file you posted, but it didn't work.

I tried a gapps package installed I had earlier, now Google playstore works, but I can't download apps, just like the problems I initially had with 6.0 releases, I get the "can't connect to server" error message. I remember it got fixed by itself after a few trials, but well.... will keep trying
[Android Software Development] HypoTurtle:
Not sure if you typed a # or not? If you did, don't.

That's just to indicate you are in root shell; rather than non root ($)

If that's not the problem then ls /data/media/0/Download to check the su.img is there.

Thanks for trying the playstore app anyway, wiping the data of PlayStore and PlayServices might fix that server error. Or you could enable the disabled gapps
[Android Software Development] Random Username:
Could someone please post installation instructions? I have to idea what to do with zip files on Windows... Maybe I'm just too dumb.
[Android Software Development] HypoTurtle:
Which zip are you making reference to?

I'll fix up #2 in a minute; but in short unzip efi folder to root directory (i.e. C://efi or D://efi etc.) then use easyuefi to set boot order (or choose boot device from UEFI).
[Android Software Development] KamaL:
Remix OS is getting updated quite frequently, now it's version 2.0.202, release today 12/4/2016 [MENTION=4056517]HypoTurtle[/MENTION]

Anything new about it? Any plans for preparing a new custom image with root drivers for the i7 stylus??
[Android Software Development] HypoTurtle:
If your referring to this version. Then I'd say it's probably just the same as the latest OTA version 2.0.202 dated 20160405 -- that's the current custom version here with an additional 3mb OTA -- not sure what it changed though --- I'm not going to download just to check that though.

My update procedure if interested is, from stock ROM that needs to be updated.

1. Copy su.img to /data/su.img (using ALT&F1) --- only needs to be done once

2. Replace initrd.img and ramdisk.img with ones to give root and system rw

3. Copy 4.4.2-i7 kernel modules to /lib/modules/ and fix permissions (folders 755, files 644)

4. Switch kernels

5. Download OTA

6. Replace system.img, ramdisk.img, initrd.img and kernel with stock then boot

7. After OTA applies backup a copy of the above four files for future OTA

8. Repeat #2, #3, #4

9. Replace sensors.iio.so files and add touchscreen fix to init.sh (rmmod i2c_hid && modprobe i2c_hid)

Current OTA kernel is 4.4.6; but the source for this I don't think has been released so for now it's 4.4.2; unless someone else can find and compile one. I wouldn't mind trying out compiling with the Bash for Windows feature just released if anyone comes across the source.

EDITAs of version 2.0.205 - kernel has 8723bu (wifi) module included and mounts harddrive partitions by default

So ramdisk.img together with su.img; should be all that is needed to keep system.img as ro and OTA compatible. Making it a one file (ramdisk.img) switch between root and OTA.

I've had a bit of trouble uploading version 205 stock files; so may need to wait for jide to update the stock installer to 205.

I'll post the su.img and ramdisk.img for the i7 stylus here; and post a more generic setup elsewhere.

Any devs here [MENTION=3468267]asplash[/MENTION] / [MENTION=4709667]Wootever[/MENTION] -- I guess one of the things we need to fix is the thermal sensors; trip_points are setup correctly I think but reported temp is always 59oC; currently I'm just turning off turbo manually (keeping cpu at 800Hz); having a temp value to trip turbo off might be better.
[Android Software Development] hoangtnt:
some one pls post installation guide. i downloaded remix beta 2 but i dont know what can i do next. thx
[Android Software Development] hoangtnt:
[MENTION=4056517]HypoTurtle[/MENTION] how to turn off tubor when boot to remix os. I used many apps like setcpu, antutu cpu master to cpu run at 800mhz and set on boot but when boot app setting return default , not set on boot.
[Android Software Development] HypoTurtle:
I've included it as part of this as well as other i7 stylus needed stuff (touchscreen/rotation libs).

I'll add the scripts to that OP; but if you search for 'ubuntu disable turbo' you'll find it - it's echo 1 > no_turbo file somewhere within /sys/.
[Android Software Development] HypoTurtle:
For 2.0.205 onwards all you need is this.

The current su.img posted switches the iio.so libs for rotation; but the defaults libs can be used as jide have applied the updates from Ax86 in relation to rotation from property value, so will update that OP with directions.
[Android Software Development] dodongobongo:
Thank you very much [MENTION=4056517]HypoTurtle[/MENTION] for sharing all this. I've been testing RemixOS on my i7 Stylus today and it's working great, although battery life seems poor compared to Windows 10. Have you found any workaround for the touch screen issue on wake-up yet?
[Android Software Development] HypoTurtle:
Which issue?

Touchscreen seems to perform the same as with windows; i.e. after a certain amount of time (10-15minutes I think); the screen becomes unresponsive, but will wake by pressing and holding for a couple seconds - or pressing the windows button.

Personally I think this isn't an issue and it must save some battery power as well.

Or is this some other issue?

Yea battery time seems a bit poor; I have it forced to 800MHz i.e. no_boost which seems to help a bit...
[Android Software Development] dodongobongo:
After the device wakes from standby there is no response from touch screen, Wacom digitizer or Windows hardware button (it does vibrate on touch, but I think that's in the hardware). At this point I must press the power button a second time, and suddenly everything works again. Key press from a USB keyboard also seems to "finish" waking it if I have one connected.
[Android Software Development] HypoTurtle:
I get ya; but not sure on that one.

For me 1st screen after power button has increased screen brightness; second has decreased (the brightness I have selected I guess). I'll have a look to see if there's a prop value/setting for this behiour.

In the meantime: if you 'enable' Power Button by removing it from /system/etc/excluded_input_devices.xml you get different button behaviour - so check that and seevwhat you prefer.
[Android Software Development] dodongobongo:
With your suggested change I'm able to turn it on with one press of the power button, with touch input working afterwards. However I must now "double-click" the power button to make the device go to sleep. A single press only makes the screen flick into black for a split second. This behavior is very puzzling, although certainly preferable to how it was before...
[Android Software Development] HypoTurtle:
If you add a lock sreen (settings ==> security); you'll get different behaviour again. I.e. 1st button press will lock the device; still need a double click to turn screen off.
[Android Software Development] ssanjy:
I have a 11" Dell 3147 touch supported laptop... I tried your tweak by removing Power Button from the above xml and rebooted but nothing happened....I tried double-clicking the power button many times to see if the device goes on to sleep but did not work...Any other possibility?
[Android Software Development] HypoTurtle:
Just fyi this isn't a tweak to 'enable' sleep, that seems to be working fine on tablets either way. It just alters the behaviour (more on wakeup) of the button.

Sleep can be hardware dependant; as can the power button [does it do anything?]

via terminal you can check what power states are reported as supported: dmesg | grep -i acpi and/or cat /sys/power/state.

echo mem > /sys/power/state or echo freeze > /sys/power/state depending on what is supported

[I'll check this commands again in case they're wrong]
[Android Software Development] HypoTurtle:
Yea: <6>[ 0.124661] ACPI: (supports S0 S3 S5)

So sleep modes are picked up.

one of those is 'freeze' the other is 'mem' [S0 is On]

So 'echo mem > /sys/power/state' or replace mem with freeze and see if it 1. Sleeps and 2. Wakes up from sleep
[Android Software Development] ssanjy:
I haven't been able to make my device sleep... And I'm very very sorry but I did not understand what you are suggesting me....I do not know the code stuffs... Really sorry for that...I would be grateful if you could provide me with simpler explanation.... Thank you for your time and support....
[Android Software Development] HypoTurtle:
Just type it in like you did before:

root@remix_x86_64:/ # cat /sys/power/state
freeze mem

/sys/power/state is a special file; cat'ing it like you did before outputs the reported states: in your case 'freeze' and 'mem'.

Echo'ing/writing to the file tells the system to enter the echo'ed state; So:

root@remix_x86_64:/ # echo freeze > /sys/power/state

should enter one of the sleep modes.
[Android Software Development] ssanjy:
OK, so I tried your code and echo freeze did get into sleep though not ever time code was entered... But it did not wake from sleep.... The echo mem did not put device to sleep at all...
[Android Software Development] hacksterkrishna:
Good job
[Android Software Development] HypoTurtle:
Mem is probably the one you want. Try 'sync' first.

This is probably relevent: https://wiki.ubuntu.com/UnderstandingSuspend

What does 'cat /proc/acpi/wakeup' output?
[Android Software Development] ssanjy:
Sorry, couldn't understand what 'sync' means ????

Here's what the code output shows

u0_a29@localhost / $ su

root@remix_x86_64:/ # cat /proc/acpi/wakeup

Device S-state Status Sysfs node

XHC1 S0 *enabled pci:0000:00:14.0

RP01 S4 *disabled pci:0000:00:1c.0

PXSX S4 *disabled

RP02 S4 *disabled

PXSX S4 *disabled

RP03 S4 *disabled

PXSX S4 *disabled

RP04 S4 *disabled

PXSX S4 *disabled

EHC1 S0 *disabled

PWRB S4 *disabled

BRCM S0 *disabled

BRC3 S0 *disabled

LID0 S3 *enabled platform:PNP0C0D:00

root@remix_x86_64:/ # ,
[Android Software Development] HypoTurtle:
$su
#sync
#echo mem > /sys/power/state

Might as well try #echo RP01 > /proc/acpi/wakeup to see if that makes a difference.
[Android Software Development] ssanjy:
Even after enabling it, the device failed to wake from sleep and instead restarted.... however, power button did wake in my other device Sony Vaio in which I've installed the same version of remix os.. And the sleep was also good though I did get some battery drain...... Thank you for spoon feeding me.... ????
[Android Software Development] HypoTurtle:
Not a problem, it's actually my first time looking throught this too (beyond the mem/freeze stuff). The only real thing I can suggest is that ubuntu post mentioned above. Notably the dmesg stuff -- which might point to what is causing the sleep/wake issue.

I'm sure you can see the sort of issues the Ax86/Jide teams have in getting this sort of stuff working on such a wide variety of devices/hardware especially when you can't just add in another module after the fact to tweak stuff to the hardware.
[Android Software Development] ssanjy:
I'm very sure that the x86 and jide teams are working really great work to bring a very good android desktop experience.... Actually I'm loving it.... Just a few issues of android which is not possible for my office work but in my touch supported laptop, except for few hiccups and random reboot, I'm enjoying more than the default windows platform... Thanks for your support... I'll see what I can understand out of the help you've provided to me... Have a good day..
[Android Software Development] BTob:
Palm rejection

Is any of those version are supposed Palm rejection for stylus tablets?
[Android Software Development] ahmed1994:
i am searching for code but cant find

no one help me
[Galaxy Grand 2 Themes and Apps] andrei1412:
Original thread: http://xdaforums.com/note-4/themes-apps/howto-config-double-tap-to-launch-camera-t3203026

Only for motion ROM

In order to have the feature double tap to launch "anything", you just need root and an sql editor

in your sql editor:

1. Find Settings Storage (it's a different name for every language)

2. Tap on system

3. Tap on search icon and write "double"

4. in the entry named "double_tab_launch" place "1" in "value"

5. if you dont have a entry named "double_tab_launch_component", made it. In value place this:

Code:

com.sec.android.app.camera/com.sec.android.app.camera.Camera
[Galaxy Grand 2 Themes and Apps] Yuen.Jason22:
Great!!! I always wanted it!!! Thank you Bro :D
[Galaxy Grand 2 Themes and Apps] Kartik Pokar:
Works perfectly fine !!!! Thanks
[Galaxy Grand 2 Themes and Apps] Ibrat_safin:
is there any way to get double tap to wake up ?
[Galaxy Grand 2 Themes and Apps] Yuen.Jason22:
Very nice mod guide, even when the screen is locked, the camera app can be launched ;)
[Upgrading, Modifying and Unlocking] 9tendo:
Ensure you have drivers setup properly and are able to adb shell to your 410c

Install SuperSU 2.46 over adb or "Chainfire SuperSU" from Google Play if you have it installed

Download UPDATE-SuperSU-v2.46.zip and extract it to your microSD card that you use for your 410c

adb root

adb shell

cd /mnt/media_rw/sdcard1/UPDATE-SuperSU-v2.46/

cp ./arm/chattr.pie /data/local/tmp/chattr.pie

chmod 0755 /data/local/tmp/chattr.pie

mount -o rw,remount /system

cp /mnt/media_rw/sdcard1/UPDATE-SuperSU-v2.46/arm64/supolicy /system/xbin/supolicy

chmod 0755 /system/xbin/supolicy

cp /mnt/media_rw/sdcard1/UPDATE-SuperSU-v2.46/arm64/libsupol.so /system/lib64/libsupol.so

chmod 0755 /system/lib64/libsupol.so

cp /mnt/media_rw/sdcard1/UPDATE-SuperSU-v2.46/arm64/su /system/xbin/su

chmod 0755 /system/xbin/su

cp /mnt/media_rw/sdcard1/UPDATE-SuperSU-v2.46/arm64/su /system/xbin/daemonsu

chmod 0755 /system/xbin/daemonsu

/system/xbin/daemonsu –d

Exit but DO NOT restart your 410c yet

On your 410c, open the SuperSU app and select “Normal” to finish the process
[Upgrading, Modifying and Unlocking] neige2016:
I followed through all the steps in your post, but when I opened the SuperSU app in the end, it still shows the message that "There is no SU binary installed, and SuperSU cannot install it...". Do you have any idea what else I could try to fix it? Thanks!!
[Upgrading, Modifying and Unlocking] barni_kronos:
Root access is granted but once device reboots root access is denied. Also where is “Normal” in SuperSU?