Hi guys i was wondering which cm or aosp was the first released for tablets im looking into porting for a device. what would be the minimum hardware requirement for instence 2.2 froyo.
gavster26 said:
Hi guys i was wondering which cm or aosp was the first released for tablets im looking into porting for a device. what would be the minimum hardware requirement for instence 2.2 froyo.
Click to expand...
Click to collapse
The first version of Cyanogenmod to run on tablets was Cyanogenmod 7 based on Android Gingerbread version 2.3.x. It ran on tablets such as the Advent Vega, Nook Color, HP Touchpad, Viewsonic G Tab, and ZTE V9. For AOSP, the first version of AOSP to run on tablets was Froyo Android version 2.2.x. It ran on tablets such as the Samsung Galaxy Tab. The main minimum requirements for Froyo Android 2.2.x are the device must have a touchscreen, gps, compass, accelerometer, camera, usb support and other sensor requirements. Additionally 92 MB of memory must be available to the kernel and the userspace, with a minimum of 150 MB available for the user's data (/data partition). For more information I would recommend checking out the Android compatibility definition for Froyo Android 2.2.x here.
Ok thankyou i got the info from your post. and the device is no where near capable for android. i was asked by a friend to look into it
Related
As I understand it, there is a linux kernel that android sits on. I thought the ROM was like a virtual machine running inside of android and then we loaded apps onto that. I read something that indicated that each custom ROM comes with a kernel. Then we can replace that kernel with another one if we wish. I understand that the kernel must be compatible (although I don't know how to tell) but that seems confusing. It would seem that if the ROM is running in android then as long as the kernel can run android, any kernel should suffice. Clearly that is not the case so what exactly is a ROM and why does it interact directly with the kernel?
A ROM in this case is a system image (full or partial) containing the Android operating system, drivers, applications, and/or kernel.
Like with regular PC OS not all kernels are compatible with the larger OS, primarily across major versions.
check this link
http://www.xda-developers.com/android/understanding-android-fr
Rom futures
does anyone know where roms are going? read somewhere 2.3 and 3.0 are forks. that makes sense if 2.3 continues focus on phones, small devices etc and 3.0 continues down the larger tablet track. I am currently running 2.3.3 on gtab and it runs great. it seems to be very tablet friendly. does 2.3 provide much of the functionality of 3.0 for the small screen. can we expect 3.0 to bring additional utility to tabs like the gtab? just curious where we might be headed. keep up the great work. i stay excited about the next build!
Rumbleweed said:
check this link
http://www.xda-developers.com/android/understanding-android-fr
Click to expand...
Click to collapse
This is a GREAT link! Thanks.
So I used NVFlash (necessary for me to use when I went from 2.2 to 2.3 code), and I have CM7 release on the GTab right now. I know Nvidia just said they will support the harmony platform, but I was wondering if CM 6.1 has all the video acceleration built in or not. Also, since 7.0 is stable and 6.1 remains in beta, where does that leave the two in terms of bugs? Haven't seen any yet on 7...there buglog somewhere?
Thanks,
6.1 is based off Froyo source and 7.0 is based off Gingerbread source.
I have no idea if 6.1 was developed enough to include some of the latest nvidia drivers and such....
6.1 did move to 6.2 but I think development on it dropped shortly after and all efforts were directed towards CM7 and Gingerbread.
tcrews said:
6.1 is based off Froyo source and 7.0 is based off Gingerbread source.
I have no idea if 6.1 was developed enough to include some of the latest nvidia drivers and such....
6.1 did move to 6.2 but I think development on it dropped shortly after and all efforts were directed towards CM7 and Gingerbread.
Click to expand...
Click to collapse
Yeah, 2.2=froyo, 2.3=gingerbread.
Any idea where I could look up the details for CM6?
cm6 was abandoned months ago. Try either CM7 or one of the many other roms available. There are several nice froyo roms and gingerbread roms
As of May 31 it looks like Notion Adam Ink users were upgraded to Android 2.3 Since the G-tablet and the Adam Ink kernel 1.2 are very similar, I was wondering if anyone was able to port GB to the G-tablet. I know that CM 7 is based from Android 2.3, but it does not have hardware acceleration built into it. Having Gingerbread with hardware acceleration would be amazing! Here is the source link, please correct me if I have interpreted this wrong.
http://notionink.wordpress.com/2011/05/31/sales-and-updates/
The gingerbread build they released is super buggy, so I don't know if it would be worth porting. However, someone might be able to pull the hardware acceleration code from it and incorporate it into a more stable ROM. Regardless, Notion Ink said they're focusing all their efforts on making a Honeycomb build, which I think would be a lot more worthwhile to port. You can see my post about it here.
The NI Adam GB build does not have full HW acceleration working. At this point CM7 or the Vanilla AOSP or other gingerbread roms here that are still updated (Is vegan ginger still updated?) are the way to go.
Hi I'm a newbie into android custom rom development. I'd like to know more about it and utilize a Notion Ink Adam as my test device. I want to port the latest version of android (maybe ubuntu or win 8 would also do) I just want to see that the Notion Ink Adam 1 works as a usable device and all peripherial devices work as well eg. Camera and the pixel Qi Screen etc. However I do not know where to start. I went through a youtube video which talks about android internals .. So far I have collected the below queries.
1) Why is it that installing android on devices is not the same as installing a regular operating system on a machine.?
2) Is my device really a paper weight if it gets hard bricked. It cannot be recovered Period ?
3) Since the Notion Ink Adam is based on a Tegra 2 process, would it be correct to assume that if a cyagenmod android os works on another device with a similar processor by some other company it will work on the Adam. Thanks.
Hello,
I'm very new to CyanogenMod and ROM development in general,
so I don't really know what I'm doing here, and would appreciate any help you can give me
If it helps, I run Linux Mint 17 (derived from ubuntu 14.04).
I've been having some trouble porting CM 11 to my device, and the specs are as follows:
It is a Versus Touchpad 7, based on an Allwinner A10 SoC that runs at 1GHz,
the display runs at 800x480, powered my a Mail 400 GPU,
it has 8GB storage (I can use only about 5GB),
1GB RAM,
Currently runs CM 10.2 (Android 4.2.2).
As Android 4.2.2 is getting a bit out of date, I decided I'd try and get 4.4.4 working on it, and seeing as someone got 4.2.2 to work on it I wouldn't have thought it'd be too difficult.
So, I've downloaded CM 11 to ~/android/system as per the instructions given on their website, but I've immediately run into a problem:
if I stick with the Nexus 7's basic configuration (I thought it might work because my 4.2.2 ROM is spoofed as a Nexus 7) I can successfully built a recovery image. After flashing it, the tablet shows the bootloader screen, and then black screens until I reset by holding the power button down.
The next thing I tried was using the devices vendor and codename as given from the stock (4.1.1) ROM's built.prop, but the codename has a hypen in it and isn't recognised (probably because it isn't supported).
I've managed to get hold of some basic info by extracting the stock recovery.img and boot.img, and copying files like /proc/partitions, /proc/cmdline as so on from the tablet, but I can't seem to get hold of kernel or previously built CM source for it, so I'm wondering if anyone can help me here.
Thanks in advance,
Hamish