yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] social-design-concepts:
I think they might be looking at kernel building.

I'm working on a Baytrail build myself. Once I have a booting build on my tablet I hope to be able to provide a base for multiple targets.
[Miscellaneous Android Development] S5Sickness:
NICE! i'm glad to see this tablet is getting some attention.
[Miscellaneous Android Development] vampirefo:
Looks like he is trying to build a kernel, what does the current kernel need? I ask mainly cause I might try and build for Venue 8, I am just not sure what the kernel would need.

I don't want to waste my time setting up and compiling to later find out the kernel source requires something.

If I am understanding correctly, the kernel is simply being built with Selinux disabled? Or is thethere more to it?
[Miscellaneous Android Development] social-design-concepts:
you mean your tired of android device manufactures releasing broken kernel source that can't be built with out alot of work doesn't contain the commit history and that isnt 100% gpl complaint. lol

not sure if i've ever seen a manufacture (besides google and the nexus line) ever release kernel source that actually was gpl complaint.
[Miscellaneous Android Development] vampirefo:
No, not really, I can build the kernel, my tablet has ran from custom kernel since the day dell released the source. What I am asking is what needs to be added to kernel source for cm to work.

If cm worked on stock kernel then a kernel wouldn't need to be built, so something cm specific needs to be added to kernel source, what is that?

Perhaps I am not wording my question right, the stock kernel for ares 8 doesn't boot cm, so a custom kernel is needed, what is put into custom kernel that allows cm to boot, that doesn't exist in stock kernel?

I see people who port cm to their device, and have cm built kernel, what is cm built kernel? What is added to source code to make it cm? Rather than stock kernel.

If cm was compatible with stock kernel, custom kernel wouldn't be needed, so something in cm built kernel is different than stock kernel, what is the difference?

Let's say you and me both go to dell website download 3830 kernel source, each compile a kernel, My kernel is stock kernel yours is cm kernel, you did something different than I did, else we would both have same kernel which would be stock, so what did you do to make your stock kernel source a cm kernel? Instead of stock kernel like I built.
[Miscellaneous Android Development] social-design-concepts:
I've never been sure on cm specific kernel patches. The original venue 8 kernel source would never build for me WiFi and something else also complained of missing something but if I disabled them in the config yeah the kernel would build and boot fine. I haven't tried building it since the original 3/14 release.
[Miscellaneous Android Development] vampirefo:
I am able to build both kernels fully working with wifi and such, but they are really just stock kernels, so doesn't help toward building cm. So without knowing what needs to be added or removed from stock kernel source to make a cm kernel, building cm is just a waste of time.

Oh, well it is what it is.

Back to porting my 4th rom for my Blu Energy X Plus, I really love this phone.
[Miscellaneous Android Development] social-design-concepts:
I don't think the booting problem has anything to do with the kernel it's self, now that I have a new PSU for my build box and can build for my lenovo again I'm going to work on trying to get it to completely boot.

I've noticed most device trees have a static lib libhealthd.$(TARGET_DEVICE) I think this is needed so healthd can properly communicate with the charging / battery status information.
[Miscellaneous Android Development] S5Sickness:
Anything to test yet?
[Miscellaneous Android Development] yuweng:
[MENTION=2472806]vampirefo[/MENTION] as per request, attach is my twerp... :cowboy:
[Miscellaneous Android Development] vampirefo:
Thanks will look at it in the morning.
[Miscellaneous Android Development] vampirefo:
OK just tried it, works for a few seconds can get adb working, press some buttons, then it reboots to recovery. So your Intel is the similar to this Intel. I think with a few adjustments your recovery will be just fine.

This recovery in this thread would work on your device, you would need to pack with your kernel.

Anyway I will see if I can adjust recovery files to prevent your recovery from rebooting on this tablet.
[Miscellaneous Android Development] yuweng:
Don't really understand today's XDA n00bs/ newbies, not even one feedback my PhilZ Touch build, i don't even own that device myself...

While you help me out without me even asking for help, BIG Thanks to you bro for carrying out the test, i really appreciate it... :highfive:

More info, sorry for the OT

The thing with this 1st Gen Intel X3-C3130 KK is that the stock 3e recovery.img contains some sort of headers, without it, it won't boot, this info was found out by Invisibot... :good: Having said that, when i flash the stock 3e to boot partition, without those headers, it did boot up but only stock 3e, obviously it won't boot to Android... :laugh: With this i presume those headers are only required for the recovery. boot.img doesn't contain those headers.

On the 2nd Gen X3-C3230 LP, its just recovery.img, doesn't contain those headers, jemmini has built it & i port it here, it boots but again, nobody feedback whether it can actually do a full backup/ restore though i did check the recovery.fstab is correct.

Dees_Troy has given me some hints here... :cool: On my X3, my build & your build doesn't boot too, that leads me to presume that the stock 3e contains some required init statement or it needs certain stock 3e binary for TWRP to boot since you confirmed mine did boots on your device... :highfive:

Send me a pm if you have any idea in mind, Thanks again bro, you have helped to narrow down the problem, at least now i know its not my build that cause it not to boot or i will blame its TWRP source code problem... :laugh:
[Miscellaneous Android Development] social-design-concepts:
I'll have to download that stock recovery image when I get home? What's the end of the image look like?
[Miscellaneous Android Development] vampirefo:
Ok got it stable for you, I don't like the time out on your recovery, but it's your recovery.

Anyway your recovery sha1sum, you can compare to this one and see it's your recovery.

68204b28eefb3256353878da21b05076f47c0b6b /home/vampirefo/Desktop/intel_x3/tmp_boot_unpack/extracted_ramdisk/sbin/recovery

Ok what I did was build my own recovery for intel using twrp6, then I replaced my binary recovery with yours, this makes yours stable, you are missing some files, you can compare your /sbin to mine. None the less this is your recovery.

This is packed to install on ares 8, cause that's what I tested it on, unpack add your kernel and pack for your device.

https://www.androidfilehost.com/?fid=24385658843824249
[Miscellaneous Android Development] yuweng:
My build doesn't boot, my Master Shifu says it got nothing to do with the source & vampirefo has just confirmed it, whole detail story here... :o

Thank You so much for your effort, my friend... :highfive: i really do appreciate it... :good: The problem is that it just won't boot, just tested yours, its the same, it only boots when i manually push it to stock 3e & manually started it from there... This is getting way too OT, i don't wanna mess up your thread bro, in the past at my thread, it was like 3 to 4 pages of OT just bcos one user try to help another user but that was not the title for discussion, Eg. like now... :o However, pls do pm me if you guys got anything at all, i've really run out ideas... :cowboy:
[Miscellaneous Android Development] zerozed99:
The dream of some kind of optimized ROM for this device seems dead. :(
[Miscellaneous Android Development] S5Sickness:
You are right... Getting a samsung so don't really care... But i do feel for the one's who do have this tab and want a rom....:(
[Miscellaneous Android Development] restlessvagabond:
thanks for all the work you put in on this.
[Miscellaneous Android Development] zixxorb:
So apparently unjustified dev got sick and hasn't been on for a while and forgot to mention it to you guys.

I'm the one who asked him to work on this tablet and gave him certain files. I've also posted a bunch about this tablet on androidforums.

I'm willing to do whatever it takes to get this tablet a working CM version. I'll test whatever may be needed myself on my tablet if I need to.
[Miscellaneous Android Development] vampirefo:
It's [MENTION=4911249]Unjustified Dev[/MENTION] rom, you would need to contact him for any tests, beyond what he posted in this thread.
[Miscellaneous Android Development] vampirefo:
Took many hours, 1 hour just too walk dog and cool down, but I have finally installed 5.1, the rom seems to run just fine, the rom on the tablet is 5.0 and has a memory leak, this rom 5.1 is supposed to be patched, so should run better, does it? only time will tell.

I hate the 5.1 bootloader, you are warned each boot, that you are running modified boot.img and or recovery.img and must press volume up to continue the boot each time.
[Miscellaneous Android Development] social-design-concepts:
can i get the bootloader off of you please maybe a dump of the full esp partition?
[Miscellaneous Android Development] vampirefo:
Here you go.

https://www.androidfilehost.com/?fid=24415232478675637
[Miscellaneous Android Development] vampirefo:
Anyway to stop the nag on each boot? It's annoying but liveable, this tablet is running great on 5.1, Sound is way low, need head set to hear anything. That's the way I listen anyway so no big deal, no camera, I never used the camera that came with tablet in first place.

This this the first time, I been able to use tablet, needed to let charge, plus can't use while working on it, so far 5.1.1 is what this tablet needed. This ROM is from iview tablet i708Q.

I am getting ready to go to Florida for vacation, can't wait, be there a week or so.

ROM is from this tablet. ??????

http://www.iviewus.com/index.php/i-708q.html
[Miscellaneous Android Development] social-design-concepts:
oh your running that rom gotcha you actually might be interested in running the Trextor Android M rom, It's and ( IRDA ) device I've been working on porting the kernel to the now legacy / non-irda baytrail devices.
[Miscellaneous Android Development] S5Sickness:
OK the rom that you guys are talking about.... is this for the next book 8? If so I want in damit....
[Miscellaneous Android Development] vampirefo:
Never heard of that device, I would be interested in looking at it, The only downside of ares 8, or I guess I should say limitations of running roms on this device is touch screen.

You have to use it's 5.0 kernel, the kernel can be repacked of course, using different ramdisk but the 5.0 kernel is a must, as the touch screen drivers are built in, no source for these touch screens are available.

That killed my Linux project, this tablet ran Linux smooth, I was able to build WiFi, module, sound the works, but not touch screen.

If the 5.0 kernel can be adapted to the ROM you are referring to, send me link I and Will give it a shot.

For my ares 8 to run the i708Q ROM, I had to turn the tablet into a i708Q tablet, lots of work, had to repartition the device, flash all the parts, then use mouse to setup device, then unlock bootloader, modify boot.img to add 5.0 kernel, to get touch screen to work, this can only be done after unlocking 5.1 bootloader.

It's a lot of work, and only a few very few people will be able to do it, if I decide to post a guide, the otg cable and mouse is a must, all commands are done via command line.

Anyway time to get back to packing, talk more about these after my vacation.
[Miscellaneous Android Development] social-design-concepts:
What touch screen does it use?
[Miscellaneous Android Development] vampirefo:
vampirefo@vampirefo-GA-MA78GM-US2H:~/Desktop$ adb shell getevent

add device 1: /dev/input/event8

name: "accel_kxcj9"

add device 2: /dev/input/event0

name: "Power Button"

add device 3: /dev/input/event2

name: "Video Bus"

add device 4: /dev/input/event7

name: "baytrailaudio Intel MID Audio Jack"

add device 5: /dev/input/event4

name: "gpio-lesskey"

add device 6: /dev/input/event3

name: "gpio-lesskey"

add device 7: /dev/input/event6

name: "dollar_cove_power_button"

add device 8: /dev/input/event5

name: "gpio-keys"

add device 9: /dev/input/event1

name: "focal-touchscreen"

[Focal][Touch] ftxxxx_ts_init !

<4>[ 2.894968] [Focal][Touch] FT3417 prob process Start !

<6>[ 3.059792] mmc1: new high speed SDIO card at address 0001

<6>[ 3.154128] HidI2c_To_StdI2c ignore

<4>[ 3.154154] [Focal][Touch] ftxxxx_create_sysfs Start !

<7>[ 3.154249] ft3x17 4-0038: ftxxxx:ftxxxx_create_sysfs() - sysfs_create_group() succeeded.

<4>[ 3.154266] [Focal][Touch] ftxxxx_create_sysfs End !

<4>[ 3.154537] [FTS]ftxxxx_create_apk_debug_channel

<4>[ 3.155967] [FTS] Firmware version = 0x10

<4>[ 3.156882] [FTS] report rate is 100Hz.

<4>[ 3.157782] [FTS] touch threshold is 68.

<4>[ 3.158679] [FTS] VENDOR ID = 0x80

<4>[ 3.159656] [FTS]focaltech_get_upgrade_array chip_id = 55

<4>[ 3.160464] FTS:fts_ctpm_clb_chck: ignore

<6>[ 3.160804] input: focal-touchscreen as /devices/virtual/input/input3

<4>[ 3.161005] [Focal][Touch][INFO] client name = ft3x17 irq = 389

<4>[ 3.161030] [Focal][Touch] chip_id = 55, X-RES = 800, Y-RES = 1280, RST gpio = 128, gpio irq = 133, client irq = 389

<6>[ 3.161141] Successfully added driver ft3x17
[Miscellaneous Android Development] social-design-concepts:
config TOUCHSCREEN_FT3X17
tristate "FTS touchscreen driver for FT5X0X"
depends on I2C
default N
help
Say Y here to enable the driver for the touchscreen on the
development board.
If unsure, say N.
To compile this driver as a module, choose M here: the
module will be called ft5x0x.ko.

drivers/input/touchscreen/ftxxxx_ts.c

#include <linux/ft3x17.h>

looks like it might be included as part of one of the zenfone2 kernel sources :
[Miscellaneous Android Development] vampirefo:
well I think the windows batch file and Linux shell script should both perform equally, for the first part. Second part requires otg cable and mouse, then more manual command line.

For those interested in updating their ARES8 to i708Q, below is what's going to happen to your tablet. Your tablet's software is going to be completely replaced by the software of i708Q tablet, Can the ARES8 tablet be returned to ARES8? only you can say, as I have no intentions of returning to ARES8 firmware.

I am going on vacation, if there is enough interest in this project, I will post a guide when I come back, if not I won't.

This requires a lot of work, mouse, and otg cable.

The end results is a nicer tablet, battery lasts longer, tablet runs smooth, no camera, sound is so low for me requires head phones, but to be honest I always use head phones.

Linux script

#!/bin/bash
sudo fastboot oem wipe ESP
sudo fastboot oem wipe reserved
sudo fastboot oem start_partitioning
sudo fastboot flash /tmp/partition.tbl partition.tbl
sudo fastboot oem partition /tmp/partition.tbl
sudo fastboot format factory
sudo fastboot format system
sudo fastboot format cache
sudo fastboot format config
sudo fastboot format logs
sudo fastboot format data
sudo fastboot oem stop_partitioning
sudo fastboot flash ESP esp.img
sudo fastboot flash fastboot droidboot.img
sudo fastboot erase system
sudo fastboot flash esp_update esp.zip
sudo fastboot flash fastboot droidboot.img
sudo fastboot flash boot boot.img
sudo fastboot flash recovery recovery.img
sudo fastboot flash -S 200M system system.img
sudo fastboot continue

Windows batch

fastboot.exe oem wipe ESP
fastboot.exe oem wipe reserved
fastboot.exe oem start_partitioning
fastboot.exe flash /tmp/partition.tbl partition.tbl
fastboot.exe oem partition /tmp/partition.tbl
fastboot.exe format factory
fastboot.exe format system
fastboot.exe format cache
fastboot.exe format config
fastboot.exe format data
fastboot.exe format logs
fastboot.exe format factory
fastboot.exe oem stop_partitioning
fastboot.exe flash ESP esp.img
fastboot.exe flash fastboot droidboot.img
fastboot.exe erase system
fastboot.exe flash esp_update esp.zip
fastboot.exe flash fastboot droidboot.img
fastboot.exe flash boot boot.img
fastboot.exe flash recovery recovery.img
fastboot.exe flash -S 200M system system.img
fastboot.exe continue
[Miscellaneous Android Development] social-design-concepts:
You shouldn't have to do all of that, I don't see any reason to need to repartition or replace the bootloader if the device already supports booting unsigned .img files.

The requirement of the persistent partition can be removed from the rom that is being flashed.
[Miscellaneous Android Development] vampirefo:
That is the way I did it, I believe in completely replacing all, leaves no doubt, people are free to do as they wish, this way works, other ways I have no ideal, that will be up to who ever wishes to do it differently, to each their own.
[Miscellaneous Android Development] social-design-concepts:
Yeah but esp.img and esp.zip can contain uefi-bios updates and option ROMs that can brick tablets and on some devices certain partitions can have needed files.
[Miscellaneous Android Development] vampirefo:
This esp.img is clean, flashes smooth so flashing it or partitioning phone doesn't hurt anything, makes the transformation clean.

I do wonder when bootloader is unlocked where is that data kept? If possible to flash an unlocked bootloader and it remained unlocked, then mouse wouldn't be needed cause custom boot.img could be flashed instead of stock.
[Miscellaneous Android Development] social-design-concepts:
I'll post a link later to an article about it but there should be a new persistent-data partition that tells fastboot it's unlockable the actual lock state information is stored as a nv efi var. so in theory we could make a small program that sets the needed nv efi vars. Maybe I'll dig into it tonight.

Oh and I'm sorry I wasn't meaning to insist there was something wrong with the esp it was more of a PSA for users that might not be aware that the esp partition possibly could contain uefi-bios updates.
[Miscellaneous Android Development] Rls4ever12:
Will a guide be post?
[Miscellaneous Android Development] vampirefo:
Not while I am on vacation.
[Miscellaneous Android Development] vampirefo:
Is this ubuntu a new install? You haven't installed 32libs?

sudo apt-get install lib32z1 lib32ncurses5 lib32bz2-1.0 lib32stdc++6
[Miscellaneous Android Development] grimjeeper:


I've done everything with mine, still slow.
[Miscellaneous Android Development] ph37rd:
I am another step closer, thanks to you. I don't think you're local, so give me a vehicle to buy you a beer or coffee and it's yours.

I have a permanent recovery and root, but I am not able to get /data to mount in order to wipe it.

Any thoughts?

btw: Confirmation number: 3GP28767RR523300C
[Miscellaneous Android Development] vampirefo:
Have you flashed remove_encryption.zip? you don't need to mount data to wipe data.

Thanks for the donation.
[Miscellaneous Android Development] vampirefo:
If your tablet hasn't speed up could be it's defective, I have xposed with Fix Lollipop Memory Leak, greenify, gravitybox as well as kernel auditor low memory killer set to aggressive.

My tablet runs very well, but the main jump in performance was removing the encryption, xposed and the rest just smooth everything else out.
[Miscellaneous Android Development] grimjeeper:
The problem is, removing twrp and making it stock again.
[Miscellaneous Android Development] vampirefo:
Well that would be some work, but could be done, In theory of course, I haven't tried it, as I wouldn't want to return to stock tablet, first you would need to turn off superuser, that can be done from the app itself, then go into security and encrypt the tablet, reboot then boot into bootloader and flash stock recovery.img and boot.img
[Miscellaneous Android Development] grimjeeper:
Yeah, and finding the e stock .imgs. I mainly got this tablet for my kids to watch videos and to play around with. It's great enough for her.
[Miscellaneous Android Development] ph37rd:
Well, you won't retire on it, but you can definitely grab lunch.

Now to figure out what other messes I can get into with this thing.
[Miscellaneous Android Development] vampirefo:
Well it boots Linux via liveusb, and the bios looks cool, still playing with it myself.
[Miscellaneous Android Development] ph37rd:
Am I correct there are no sources available for this thing? Just had a wild thought that I might actually use this thing to learn a bit about custom ROMs and as an excuse to dig into the whole linux thing. Much easier to learn something when you can apply it to something interesting/fun.
[Miscellaneous Android Development] vampirefo:
Correct no source, I wrote nextbook and requested source code, they told me they wouldn't release any source code period.

What I need is touch screen source code, I got wifi working on Linux, but not touch screen, I need source code for that.
[Miscellaneous Android Development] ph37rd:
Hmmm. Might have to go on a search for a cheap used tablet with source available and at the same time not be so old that it's impractical. My past devices either don't work or have a dedicated use.
[Miscellaneous Android Development] freddy999:
I bought one of these tablets over the weekend and have not rooted it yet. But I noticed an issue with the stock firmware that is a bit alarming. I noticed each and every time the device comes back from a deep sleep the cpu governor does not allow a processor speed above the 498 mhz mark. When you reboot all is good again. As an individual who knows more about this device then anyone, are you seeing the same thing?

If I got a defective one I need to return it before I root it.

Thanks,

Freddy999
[Miscellaneous Android Development] vampirefo:
Mine isn't stock, I use apps to set my CPU speed, and governor.

I had never paid any attention, I rooted my device and adjusted the speed within an hour of getting the tablet.
[Miscellaneous Android Development] freddy999:
I guess I will return it and get another just in case. I talked with the Nextbook tech support who tells me they have not had that as a complaint and I should just get another. The only reason I even had time to find out is because I do not have a machine currently running 64bit Ubuntu. I will post info here if the second tablet has the same issue. By the way, did you copy the stock system from yours before you messed with it? I have not seen a copy of the factory ROM anywhere.

What apps do you recommend for CPU control after rooting?

Thanks,

Freddy999
[Miscellaneous Android Development] vampirefo:
Yes, I always make backups, before I modify anything.

I use no frills CPU control, to change governor and CPU speed.
[Miscellaneous Android Development] freddy999:
Well I grabbed another from Wally World last night, and although it did not have the wake-up issue it did have a screen with a big dead area right through the middle. It went back and I got a third one which so far appears OK from a hardware standpoint, and again no governor issues. I guess I should use it a few days before I void the warranty as quality control seems to be a bit of an issue, at least in the ones I have seen to date! :fingers-crossed:

But it is a fast machine with a lot of upside potential.
[Miscellaneous Android Development] lifestar53:
Will this work on the Ares 11 ?
[Miscellaneous Android Development] vampirefo:
You can use the tethered recovery to root your device, but don't flash the recovery or boot.img.
[Miscellaneous Android Development] Rls4ever12:
Thanks for the reply. Hope to see it soon.
[Miscellaneous Android Development] tamcdonald:
Anyone know if the Ares 11 is rootable?
[Miscellaneous Android Development] vampirefo:
Yes, http://xdaforums.com/showthread.php?t=3064164
[Miscellaneous Android Development] freddy999:
Does anyone know if this device suffers from the 5.0 memory leak issues?
[Miscellaneous Android Development] vampirefo:
Yes it does, badly.
[Miscellaneous Android Development] freddy999:
Does it solve with Xposed and do I need to flash it via twrp for my unencripted rooted device?