Related
https://wiki.ubuntu.com/ARM/TEGRA/AC100
"Adobe Flash
Dropping this library into ~/.mozilla/plugins allows flash playback. It warns though that it is out of date. http://kotelett.no/ac100/phh/Android2.2/libflashplayer.so"
Sounds great! =)
I did put this new Ubuntu Image on my AC100, however some things don't work:
* ppa ac100 produces error 404, package ac100-settings isn't found
* high background load, virtually unusable
* no shortcuts (old Imgae did support)
* no suspend (crashes), no sound yet
* did not get flash to work with above plugin
Anyone ha dmore success?
The flash plugin (even only playback) of this Ubuntu doesn't work for my Linux
Ubuntu 11.10 x Folio100?
Hi,
On http://cdimage.ubuntu.com/releases/oneiric/beta-2/ there is a "Preinstalled desktop filesystem archive" for Toshiba AC100. Is it possible to use drivers used in http://forum.xda-developers.com/showthread.php?t=907960 to prepare a version for Folio 100?
Thanks.
semonma said:
The flash plugin (even only playback) of this Ubuntu doesn't work for my Linux
Click to expand...
Click to collapse
I found a solution, now I have flash in Chromium. Doesn't work in Firefox (probably because I am running Version 7).
Instructions:
put the libflashplayer.so in the Chromium plugin directory (/usr/lib/chromium-browser/plugins), easiest way is by wget command:
sudo wget -O /usr/lib/chromium-browser/plugins/libflashplayer.so http://kotelett.no/ac100/phh/Android2.2/libflashplayer.so
install nvidea-tegra package
as it is not in the Oneiric repository yet I pulled this .deb and installed it via gdebi:
http://ppa.launchpad.net/ac100/ppa/...dia-tegra_12-0ubuntu1~alpha1monson6_armel.deb
I have no idea whether this is correct or latest, but it works to some extend.
Run chromium with
chromium-browser --allow-outdated-plugins
otherwise you get warning
360p Youtube runs smooth but when fullscreen has some slight lags, above resolutions do stutter.
Edit:
Here are some .deb packages of the main developer that seem to be newer. Did not test that. See the Readme: http://people.debian.org/~jak/ac100/README
Edit2:
With Beta 2 image and newest kernel (2.6.38-1000-ac100) the AC100 got quite usable now, sound via headphone works and performance bugs are largely reduced. Still some deadlocks by mmcd. Switching from ext4 to nilfs2 might yield some performance gain? And Debian hf, utilizing the Tegra FPU, also sounds promising.
Thank's a lot pibach, I'll try it this night =)
Brief update:
I added the developer ppa in sources list:
deb http://people.debian.org/~jak/ac100/ unreleased main non-free
and installed the package: xserver-xorg-video-tegra
it pulls in the package tegra-libraries
However I don't see any difference in video performace
nvidia-tegra package is not in there, package is stil unchanged
sudo apt-show-versions nvidia-tegra
nvidia-tegra 12-0ubuntu1~alpha1monson6 installed: No available version in archive
It is from this ppa: https://launchpad.net/~ac100/+archive/ppa
Seemingly this is for natty, does not seamlessly work with oneiric (Error 404 when added to sources.list as ):
"Changelog
nvidia-graphics-drivers-tegra (12-0ubuntu1~alpha1monson6) natty; urgency=low
* sigh, and build for the right release, oneiric doesnt work yet ...
-- Oliver Grawert <email address hidden> Tue, 05 Jul 2011 17:55:42 +0200"
However, it does work. Strange.
When I remove that nvidia-tegra package, I get some screen artefacts. Video then plays but very slow
Moreover, I can't find any xorg.conf file to set bit depth to 16 as mentioned in the Unbuntu Wiki.
So any chance to get better video (>360p) and maybe some HTML rendering boost?
Another hint: I got problems with Unity, Dash, Software Center bugging the CPU into performance problems, seems to be some memory lock with mmcd. Chromium 13 is also a lot faster, especially scrolling speed, than firefox 7 (both on smooth scrolling). But also runs into memory / CPU overload. Switching to lubuntu made all much snappier. It requires just 1 command:
sudo apt-get install lubuntu-desktop
and reboot into that one.
Maximus serves to undecorate the maximized windows -> more screen space
pibach said:
Moreover, I can't find any xorg.conf file to set bit depth to 16 as mentioned in the Unbuntu Wiki.
Click to expand...
Click to collapse
Thats probably because linux uses udev and dbus these days to detect your hardware on the fly when you start x.
Sent from my Folio 100 using xda premium
shidima_101 said:
Thats probably because linux uses udev and dbus these days to detect your hardware on the fly when you start x.
Click to expand...
Click to collapse
Yes, you're right. But that how it is described in the official ubuntu Wikipage. Strange. I have no glue how to do that nvidia tegra configuration.
When I launch Chromium-browser from terminal I get a lot of these errors:
ERROR:gl_surface_glx.cc(121)] glxQueryVersion failed
ERROR:gl_surface_linux.cc(73)] GLSurfaceGLX::InitializeOneOff failed.
So seemingly GLX Tegra hardware acceleration is not right.
BTW, the people at Arch Linux have more recent kernel and are on the status that suspend is working fine. Plus zram support there to come. See this thread. Don't know to what extend this will make the device snappier. Mine runs already quite snappy under LXDE.
I think with Linux on it the AC100 it is currently one of the best devices around. And you can get it quite cheap.
Edit:
On boot I usually get the error: unity support test closed unexpectedly
Probably something with GLX
Tegra shouldn't have any problems running Unity or Compiz.
Anybody got this to work propperly?
Edit2:
Launching Chromium in terminal:
chromium-browser --allow-outdated-plugins --use-gl=egl --ignore-gpu-blacklist
I get:
libEGL warning: GLX/DRI2 is not supported
To give you a brief status update:
I got suspend/resume to work
Flash works now in Firefox 7.0.1 (was already working in Chrome)
There seem to be a lot of work put into Ubuntu Oneiric and it's ARM version currently and it seems to be quite stable now.
On Folio100?
Is it usable on Folio 100?
The difference is only thouchscreen and Linux was already working (http://forum.xda-developers.com/showthread.php?t=907960).
Thanks.
gipposat said:
Is it usable on Folio 100?
The difference is only thouchscreen and Linux was already working (http://forum.xda-developers.com/showthread.php?t=907960).
Thanks.
Click to expand...
Click to collapse
but also Sound, Keyboard, NvEc, USB all might be slightly different. Isn't it?
pibach said:
but also Sound, Keyboard, NvEc, USB all might be slightly different. Isn't it?
Click to expand...
Click to collapse
No, I think everything is the same.
Bye
So, has anyone already tried it on Folio?
OK, I've given it a try and the boot image doesn't work, it definitely needs some porting.
hello pibach, thank you for your time testing stuff so we can make it work at the first time.
i installed drivers to make it work with flash, and its nice but sometimes i get a bug (probably due to graphic drivers making the screen get alot of artifacts, and only solution is a reboot, still a proble,m, probably due to alpha stage driver (nvidia could put something out that works decently....)
also, you say this version uses ext4? that should get it a lower performance comparing to nilfs (which i was using with phh's version) maybe disabling the journal? dont really know, will look into it.
how about changing the governor to performance instead of demand?
also...what about an SD card install? with a class 10 card should be fast? any info? worth buying a card to do it?
@Oinquer:
a) I got artifacts too, but only on Unity. I am on LXDE now and that works fine. Don't know why though.
b) I think you can choose ext4 or nilfs2 as you like. Can you point me to some links regarding performance comparisons and some more background info? I would give it a try then.
c) governor can be changed, sure.
d) the android bootloader cannot load from SD. But there might be some solution to do so, don't know. Meanwhile it should be no problem to have dual boot from internal MMC, for example Linux from partition 6 and android from partition 5 (SOS).
hello,
back to you, im using lxde now and installing the driver, hope artifacts go away.
EXT4 as far as i know has some benefits and some disavantages over ext3 and some other filesystems (checked yesterday after post), so performance might not change enough to notice.
governor , did it yesterday to performance, have to check flash playback now, but im not seeing big change except in boot time, that seems a few seconds less.
SD card, last version from phh's could be installed in SD card...and ubuntu wiki from AC100 says that if theres a blank SD card in slot at installation it will ask if you want to install there...im pretty sure its possible, but my sd card is in the trash bin, and cant buy one now...
here im hoping for the FPU stuff for the ac100...its getting there!!! quite usable, theres also a fix to have sound from internal speakers in ac100DOTgrandouDOTnet
will try it after i got everything sorted.
thank you for taking your time.
Sound is working in Ubuntu Oneiric Kernel that is in the proposed repository, works for me, but sound does not wake up after suspend yet.
SD card/USB boot does not work with Androib bootloader that is also used for Ubuntu Oneiric standard install. So you need to find one that can support that. Ccurrently there isn't any solution for that around, AFAIK. But you can put Linux on partition 6 and Android on Partition 5 and uses Android 2.1 bootloader.
A new release is ready the final Degu.
For both gen7/8 you will need to flash the latest zImage and initramfs included in the download links. <-- not needed if you already have flashed the latest with Crow. no changes in kernel or initramfs for Degu release.
Also to be sure you will need to delete your data.img and let it create a new one or copy your own if you use an image more then 256mb.
For setting up your device look here http://dev.openaos.org/wiki/AndroidInstall_CM7_Gingerbread
Links updated crow release 27-01-2013
For gen7:
http://www.openaos.org/wp-upload/gen7/2013-01-27/
For gen8:
http://www.openaos.org/wp-upload/gen8/2013-01-27/
If you have any issus post them by creating a new ticket see http://dev.openaos.org/wiki/IssueTracking on howto.
Known issues are here: http://dev.openaos.org/wiki/AndroidTicketsFor2.3
If it works well or you have issues you can also leave a reply.
BTW camera should partly work on gen8, tested on a 101IT taking photos. Video recording will freeze the app. Not tested with apps that use the cam only with the included camera app.
A43IT has a different camera, so I don't know if it will work.
Thanks,
divx118
Usefull links for setting up the devices:
Gen7 devices: http://dev.openaos.org/wiki/SettingUpMultiRootGen7
Gen8 devices: http://dev.openaos.org/wiki/SettingUpMultiRootGen8
General info: http://dev.openaos.org/wiki/AndroidInstall_CM7_Gingerbread
Building your own image: http://dev.openaos.org/wiki/AndroidBuildEnvironment
Degu final (27-01-2013)
------------------------------------------------------------------------------------------------------------------------------------
Changelog:
- Smoother youtube video playback for gen8
- More apps in the market available for gen7 and gen8 (also thanks to utopik for this)
- Internal storage should now properly display free available memory for gen7 and gen8
- Fixed bookmark for gapps in the browser for gen7 and gen8
- Overal speed improvement.
Unfortunately you will need a fresh data.img to let these fixes take effect.
Crow final (25-12-2012)
------------------------------------------------------------------------------------------------------------------------------------
First don't forget to flash he new zImage (kernel) and initramfs it is in the archive kernel_gen7_20120512_114451.tar.gz for gen7 and kernel_gen8_20120409_002900.tar.gz for gen8 unpack it (with winrar if you are on windows) and only use "zImage" and "initramfs.cpio.gz"
Changelog see http://www.openaos.org/archives/821
Bull final (09-04-2012)
------------------------------------------------------------------------------------------------------------------------------------
First don't forget to flash he new zImage (kernel) and initramfs it is in the archive kernel_gen7_20120512_114451.tar.gz for gen7 and kernel_gen8_20120409_002900.tar.gz for gen8 unpack it (with winrar if you are on windows) and only use "zImage" and "initramfs.cpio.gz"
Only for gen7: If you flash the new kernel and initramfs also delete the old menu.lst when it is there. If you have custom lines in there add them later after you first booted in the new menu.lst that is created.
Only for gen8: If you first boot the image it happens sometimes that omap_vout isn't loaded correctly this means it can't create the overlay for playback video and uses the software renderer. If you just reboot it is ok. It only happens atleast to me on the very first boot.
Some improvements first the kernel and initramfs:
- Correct orientation of the bootmenu for A101IT
- Updated the kernel with latest archos GPL release which means that the ones with broken USB host on their A101IT it gets working again when booting stock through the bootmenu.
- For gen7 updated initramfs to match the one from gen8
- Added unionfs support, so you can have root with rw access on stock android.
Improvements on Gingerbread:
- smoother camera because of using the overlay to display the stream. Known issues: - display is cropped so you don't see the whole camera - Recording still doesn't work.
- Youtube app works.
- Hardware accelerated video for atleast youtube app and some mp4 files, maybe more if someone can test some different formats that would be nice. Rotation does work for youtube app, there are still some issues when rotating playing a regular mp4.
- On gen8 you can also play hw accelerated flash videos in the browser now, of course not all pages will work.
- wifi location should work now. <-- same for gen7
- Fix not enough storage when installing apps by moving /cache also to the data.img. <-- same for gen7
- Update to latest CM code. <-- same for gen7
RC2 (24-12-2011)
------------------------------------------------------------------------------------------------------------------------------------
This will be the final Bull release or there must be some major bugs discovered in the next few days.
There is now a new feature added (thanks to illifant). The data is now in a separate image "data.img" if it is not there it will be auto created. 256 MB is standard. You can replace it with a bigger one from the download link gen8_data.img.tar.bz2.
If you unpack with for example winrar you see three images 256MB, 512MB, 1024MB just pick a size and copy that to the root of your archos. Rename it to "data.img"
As mentioned you don't have todo this if you want to use 256MB that will be created automaticly.
All your data, apps and gapps are in data.img. So on a next upgrade you won't have to reinstall everything again.
Also the size of the actual image is reduced, for gen7 it is 180MB and for gen8 256MB.
Don't forget to flash the new zImage (kernel) and initramfs it is in kernel_gen7_20111224_181411.tar.bz2 for gen7 and kernel_gen8_20111224_213037.tar.gz for gen8 unpack it with winrar and only use "zImage" and "initramfs.cpio.gz"
(if not specified otherwise the fixes are for gen7 and gen8)
Gingerbread Image:
- Deep sleep improved, however to work properly keep adb disabled. (it is now disabled by default.)
- Charging A43 for USB and wall charger is fixed (gen8)
- External sd-card is now mounted on /mnt/storage/sdcard (same as on archos firmware).
- Updated with latest CM code.
- New modules from updated kernel build (gen8)
- Other small fixes see the closed tickets.
zImage and initramfs.cpio.gz:
- Initramfs script updated, if it fails it will now display an error message instead of just rebooting.
- Kernel updated to latest archos firmware (2.4.81) kernel (gen8)
RC1 (06-11-2011)
------------------------------------------------------------------------------------------------------------------------------------
Somethings that are changed since anoa release:
(if not specified otherwise the fixes are for gen7 and gen8)
- Fixed headphone speaker switch
- partly camera working for atleast A101IT I think also A70, don't know for A43IT because it has a different cam. (gen8)
- Fixed permission errors when using ext3 formatted internal memory
- Fixed some browser crashes. Due to using v8 javascript engine again instead of jsc
- Fixed crash when going to browser settings
- Fixed deep sleep which should be working now.
- Fixed mounting/unmounting external sdcard.
- Calibration app included for A32 and A43. (Under settings)
- Updated to latest CM code
- Kernel updated to latest sources from archos firmware 2.4.65
- Fixed correct rotation for A101, only bootmenu is still upsidedown.
- GPS working for gen7 devices
- some other small things
Tips:
1) Playing youtube videos on CM fail with standard player http://pastebin.com/YAZc0z74 , but can be done with mobo player or mx player by using for example opera mobile and setting the user agent to desktop.
i'll give it a try now
The Bootmenu doesn't start. It hangs on the first Archos Screen (before OpenAOS).
It don't creates the menu.lst file also.
(Archos 101 G8)
airwolf1544 said:
The Bootmenu doesn't start. It hangs on the first Archos Screen (before OpenAOS).
It don't creates the menu.lst file also.
(Archos 101 G8)
Click to expand...
Click to collapse
I'm having the same issue.
(Archos 70 8GB)
airwolf1544 said:
The Bootmenu doesn't start. It hangs on the first Archos Screen (before OpenAOS).
It don't creates the menu.lst file also.
(Archos 101 G8)
Click to expand...
Click to collapse
You are right, something went wrong with the upload of the zImage, if you check md5sum it is wrong. I will post when it is fixed. Should be soon.
divx118
EDIT: zImage is fixed now if you already downloaded it just redownload
hey - great to hear about further development - sadly the gen8 links seems to be down ...
www.openaos.org/wp-upload/gen8/2011-11-06/ReleaseCandidate_UNSUPPORTED/
Error: Connection interrrupted
Perrhaps just partial - will try again later
EDIT: working now again
After choosing "Gingerbread-Entry" in Aos-Menu my 101 shortly shows the "openaos"- Bootlogo and then reboots in Archos-Standard.
What is wrong?? I used all files from the Link mentioned above.
Any ideas?
P.S: Reload of the files is not possible because it seems like openaos.org is down ;-(
We are having some issues with dev.openaos.org which will hopefully soon be solved.
The problem you have is a corrupted zImage. It should be fine now once you can redownload it.
Sorry for the inconvenience,
divx118
EDIT: wrote too soon, seems the links are accessible again
Hubelbert said:
After choosing "Gingerbread-Entry" in Aos-Menu my 101 shortly shows the "openaos"- Bootlogo and then reboots in Archos-Standard.
What is wrong?? I used all files from the Link mentioned above.
Any ideas?
P.S: Reload of the files is not possible because it seems like openaos.org is down ;-(
Click to expand...
Click to collapse
Is the name right? openaos-gingerbread.img.gz
airwolf1544 said:
Is the name right? openaos-gingerbread.img.gz
Click to expand...
Click to collapse
Yes that should be correct, just tested it myself. Just deleted my image, menu.lst flashed the initramfs and kernel and booted.
divx118
Oops sorry, need some more coffee this morning it was meant for Hubelbert.
Nice work..
Bugger - I sholdn't have installed UrukDroid yesterday (I read you can add Uruk to Mulitiboot, but what if its already installed?)
Whats the fixes/updates with this release please, or is it on the site?
SWFlyerUK said:
Bugger - I sholdn't have installed UrukDroid yesterday
Whats the fixes/updates with this release please, or is it on the site?
Click to expand...
Click to collapse
- Fixed headphone speaker switch
- partly camera working for atleast A101IT I think also A70, don't know for A43IT because it has a different cam.
- Fixed permission errors when using ext3 formatted internal memory
- Fixed some browser crashes. Due to using v8 javascript engine again instead of jsc
- Fixed crash when going to browser settings
- Fixed deep sleep which should be working now.
- Fixed mounting/unmounting external sdcard.
- Calibration app included for A32 and A43. (Under settings)
- Updated to latest CM code
- Kernel updated to latest sources from archos firmware 2.4.65
- some other small things
divx118
hey divx - do we have any working way of dualboot urukdroid and Cyanogen?
For me this is the major reason for less contribution on openAOS - as i need a working stable device for dialy use - but also really want to help u with cyanogen...
Searched for it some time ago already but due to the different kernels this was really hard to figure out...
anyway will try yours again now and check out the new release
FrEcP said:
hey divx - do we have any working way of dualboot urukdroid and Cyanogen?
For me this is the major reason for less contribution on openAOS - as i need a working stable device for dialy use - but also really want to help u with cyanogen...
Searched for it some time ago already but due to the different kernels this was really hard to figure out...
anyway will try yours again now and check out the new release
Click to expand...
Click to collapse
Unfortunately not, maybe in the future when we can boot different kernels. We just follow the archos kernel sources with some minor additions to also allow booting of other linux distros. We want however always be able to boot stock android with our kernel which gives you btw root access, because of using unionfs.
I don't know how much difference there is between the urukdroid kernel and ours never looked at it.
divx118
So far it is running smooth. Great job guys.
I noticed 3 things so far.
1) my speakers make a "pop" sound when the device goes into and comes out of sleep. They also did that in Anoa.
2) I can swipe between the different home screens OK, but if I try to use the desktop dots next to the dock then ADW force closes.
3) Camera worked great the first time, then the second time I went back in it, it is green and gray colored. Tried changing the color effect settings of the camera and it looks the same every time. Rebooting fixed the greenish look and I have been in it multiple times now and it is staying normal so not sure what caused it the first time.
marcusmarcus said:
So far it is running smooth. Great job guys.
I noticed 3 things so far.
1) my speakers make a "pop" sound when the device goes into and comes out of sleep. They also did that in Anoa.
2) I can swipe between the different home screens OK, but if I try to use the desktop dots next to the dock then ADW force closes.
3) Camera worked great the first time, then the second time I went back in it, it is green and gray colored. Tried changing the color effect settings of the camera and it looks the same every time. Rebooting fixed the greenish look and I have been in it multiple times now and it is staying normal so not sure what caused it the first time.
Click to expand...
Click to collapse
1) Yes I noticed that too, I will see if I can poke one of the archos guys to know what is causing this issue.
2) Yes, it is a known issue. If you go into ADWlauncher settings the dots will disappear. I know what is causing the problem just need some time to create a proper fix.
3) Never had this on the 101. What kind of device do you have? A101 A70 or A43
Thanks for reporting back,
divx118
BTW there are still some problems accessing dev.openaos.org if the downloadlink doesn't work try again later.
divx118 said:
1) Yes I noticed that too, I will see if I can poke one of the archos guys to know what is causing this issue.
2) Yes, it is a known issue. If you go into ADWlauncher settings the dots will disappear. I know what is causing the problem just need some time to create a proper fix.
3) Never had this on the 101. What kind of device do you have? A101 A70 or A43
Thanks for reporting back,
divx118
BTW there are still some problems accessing dev.openaos.org if the downloadlink doesn't work try again later.
Click to expand...
Click to collapse
1) I was incorrect about my speakers popping in Anoa, they crackled in that, so the pop I think is an improvement
2) that's good news. I don't use the dots as I prefer to swipe, I just accidentally click one and that is how I found out.
3)I have an A70 8GB. I'm not sure what would have caused it, I have not been able to reproduce it since rebooting the device.
marcusmarcus said:
3)I have an A70 8GB. I'm not sure what would have caused it, I have not been able to reproduce it since rebooting the device.
Click to expand...
Click to collapse
Good to know it works on the A70, it wasn't tested yet.
divx118
You are right. I forgot a 'dot' between img and gz
Now everything is fine and it works very smooth. Seems even smoother than Urukdroid.
Great job. I continue testing.
[ROM] CyanogenMod 10.2 Nightly Builds for Nook Color
The NookieDevs are pleased to announce CyanogenMod 10.2 nightly builds for the Nook Color!
These experimental builds contain the latest changes to CyanogenMod and to hardware support for the Nook Color. As the name suggests, new builds are made and posted (roughly) every day; these builds are fully automatic, with no testing done before posting. As CyanogenMod 10.2 is still under active development, regressions and general breakage are to be expected in nightly builds!
Highlights: (mostly not news if you've been keeping up with CM10/10.1 nightlies)
Linux kernel 3.0.8, plus hardware support from TI OmapZoom's android-omap3-3.0 branch and board support forward-ported from BN kernel releases.
All of the features of CyanogenMod 10.2, based on Android 4.3.
Full 2D and 3D graphics acceleration using the GPU, with improved performance over previous releases.
Known issues:
Current releases of Netflix do not work with CM10.2 -- version 1.8.1 is the last version known to work. If you want/need a newer release of Netflix, look into the Xposed mod, which provides a workaround for Netflix -- pastordl has done a nice writeup of the process here.
Download:
http://get.cm/?device=encore&type=nightly
Source code:
https://github.com/CyanogenMod/android_device_bn_encore/tree/cm-10.2 (device-specific source)
https://github.com/CyanogenMod/android_kernel_bn_encore (kernel)
https://github.com/CyanogenMod/android/tree/cm-10.2 (manifest for the rest of the CyanogenMod source)
Build instructions (discussion of build issues belongs in the development thread)
This release is the product of much effort by many people over a considerable period: many thanks to fattire, keyodi, eyeballer, krylon360, dalingrin, verygreen, iomonster, nemith, cicadaman, deeper-blue, thedude, mad-murdock, j4mm3r, unforgiven512, scepterr, rebellos, ryands, kmobs, tonsofquestions, hashcode, arcee, hacdan, drmarble, mateor, dhiru1602 and many more. Thanks are also due to the CyanogenMod project, upon which we are building, and Texas Instruments, which provides excellent support for its embedded platforms to the open-source hacking community. (TI's exit from the consumer electronics SOC market is a loss for all of us.)
XDA:DevDB Information
CyanogenMod 10.2 Nightly Builds, a ROM for the Barnes & Noble Nook Color
Contributors
steven676, keyodi, fattire, The CyanogenMod Project, NookieDevs, many others (see post)
ROM OS Version: 4.3.x Jellybean
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2013-09-07
Last Updated 2013-09-07
Google Apps; Other CyanogenMod Builds
Google Apps
http://goo.im/gapps
As of 2013/08/27, the latest release for CM10.2 is 20130813, but please check the linked page for updates.
Please make sure that you have the correct Google Apps flashed before reporting problems involving the Google Apps (Play Store, Google Keyboard, etc.).
Other CyanogenMod builds
This is the thread for CM10.2 nightly builds. There are other official CyanogenMod builds for Nook Color available:
CM10.1 stable releases -- these are the releases to use if you don't want to be on the bleeding edge.
Archived CM10.1 nightly builds -- these builds are based on CM10.1/Android 4.2. You may find these more stable than CM10.2 nightlies and faster than CM10.1.2.
Archived CM10 nightly builds -- these builds are based on CM10/Android 4.1.2. You may find the last CM10 nightly (20130421) faster than CM10.1 or 10.2, particularly during playback of HD 720p video.
Please check that your questions are in the appropriate thread. (If you're interested, there's lots of past discussion in those threads, as well as the development thread.)
Frequently Asked Questions and Troubleshooting
The soft keyboard keeps crashing!
The Play Store is acting up!
Did you flash the correct Google Apps?
How do I install this to an external SD card?
See this excellent guide by leapinlar for instructions.
What happened to the "Developer options" and "Performance" screens in Settings?
They're hidden by default now in CM10.1 and later. To show them, go into "About tablet" and tap the build number (for CM10.2 nightlies, JSS15Q) seven times.
How do I get the Honeycomb/ICS tablet UI?
You want to use the Auto-Patcher to modify your ROM for the tablet UI. (Don't forget to thank Caldair for maintaining the Tablet UI mod, and mateorod and the rest of the Auto-Patcher developers for building that tool.)
The lock screen doesn't rotate!
The screen doesn't rotate to the sides I want!
Particularly if you're upgrading from an existing install, you may find that the preferences for screen rotations are incorrectly set. Go to Settings->Display->Rotation and check that "Auto-rotate screen" and (if you want the lock screen to rotate) "Rotate lock screen" are set.
For the allowed screen orientations, selecting 0, 180 and 270 degrees will cover the rotations that you probably want. If you want details:
Android likes to think of the "natural" orientation (0 degrees rotation) as landscape with the N key on the right side of the screen. (This is a change from CM10 and earlier, when we were carrying a hack to change this.) The degrees of rotation are counted in the counterclockwise direction, so in essence, each of the rotation settings allows the following:
0 degrees: landscape orientation with the N key on the right side of the screen
90 degrees: portrait orientation with the N key on top ("upside down")
180 degrees: landscape orientation with the N key on the left side of the screen
270 degrees: portrait orientation with the N key on the bottom ("right side up")
I'm having a problem with my Nook Color running CM10.2.
That's not a question
Okay, I'm having a problem with my Nook Color running CM10.2 -- is there something I can do to troubleshoot?
Glad you asked! Please check the following:
Does the problem occur with a clean install of CM10.2? This means wiping /data and not restoring a Nandroid backup afterwards. Don't restore system apps and/or their data in Titanium Backup either (user apps/data are okay).
Are you overclocking? If so, does the problem occur when you set the maximum clock speed to 1000 MHz or below? To be clear, we are not interested at this point in bug reports of any kind that happen if you have the maximum CPU speed set above 1000 MHz. If you're experiencing system crashes or "sleep of death" (SOD), you may also wish to try capping the CPU clock speed to 800 MHz (but if this helps, please report your problem here and fill out the hardware survey).
Do you have any patches, custom kernels, or other tweaks applied? If you do, does the problem occur without those applied? (We're not necessarily going to ignore bug reports from patched or tweaked systems outright, but it can make our job harder, and we do need to know what changes you have applied to judge whether or not the change might be relevant to your problem.)
I'm having no luck with the suggestions above. What information should I include with my bug report?
When reporting a problem, please include the following information if at all possible:
Full description of the problem -- "it crashes" doesn't count. How do you trigger the problem (or does it occur by itself)? What exactly happens when the problem occurs? How often does it happen?
For problems with apps or specific pieces of the system software: we'll almost certainly ask for a logcat of the event, so you'll save everyone some time by including it.
For problems involving system freezes, crashes, or SOD: if you can connect to the tablet via adb while it's "unresponsive", please provide dmesg and logcat output from that time. If you cannot, try power-cycling it while it's still plugged into USB, and provide dmesg output from immediately after the reboot, plus the contents of /proc/last_kmsg if that file exists (let us know if it doesn't).
For unexpected reboots: provide the contents of /proc/last_kmsg from after the reboot.
First?
Sent from my Nexus 4 using Tapatalk 4
Awesome work!
Hi Steven,
Thanks for your great work and rest of the mentioned people:
fattire, keyodi, eyeballer, krylon360, dalingrin, verygreen, iomonster, nemith, cicadaman, deeper-blue, thedude, mad-murdock, j4mm3r, unforgiven512, scepterr, rebellos, ryands, kmobs, tonsofquestions, hashcode, arcee, hacdan, drmarble, mateor, dhiru1602 and many more,CyanogenMod project and Texas Instruments
I did a clean installation: wipe data, cache and Dalvik cache, flash the rom file *.zip and flash the gapps file *.zip. (maybe you should mention it in OP).
All working great and really smooth just some questions.
You mention the source of this kernel. This is the same as in 10.1 so to build the kernel separately for 10.2 we just need the encore_cm10.2_defconfig?
I see the changes are:
CONFIG_AUDIT=y (instead of # CONFIG_AUDIT is not set)
# CONFIG_NETFILTER_XT_TARGET_AUDIT is not set
CONFIG_FB_OMAP2_VSYNC_SYSFS=y
CONFIG_AUDIT_GENERIC=y
Is vsync the following?
Full 2D and 3D graphics acceleration using the GPU, with improved performance over previous releases.
Click to expand...
Click to collapse
Really good work , thanks again for everything!
EDIT:
I think vsync doesn't work, I get this from my logcat:
Code:
08-27 17:28:30.781 W/SurfaceFlinger( 1282): getting VSYNC period from fb HAL: 11111111
08-27 17:28:30.781 W/SurfaceFlinger( 1282): no suitable EGLConfig found, trying without EGL_FRAMEBUFFER_TARGET_ANDROID
08-27 17:28:30.781 W/SurfaceFlinger( 1282): no suitable EGLConfig found, trying without EGL_RECORDABLE_ANDROID
08-27 17:28:30.781 W/SurfaceFlinger( 1282): no suitable EGLConfig found, trying with 16-bit color allowed
Wow
33 days from release and a 3 year old tablet is running the latest android.
Dirty flashed 10.2 and 4.3 gapps and so far everything is running great. (over 100 apps to test out).
Thank you to everyone who worked so hard to make this possible. Video is great. The Netflix persist hack persisted through the 10.2 upgrade also.
Hi,
I have been using an SD install for all of 10.1 with no problem. I tried the 10.2 nightly and I cannot get it to boot to Android. I built the SD card the same way I did all the rest. It boots to CMW I have also installed the alternate. I load the nightly and gapps on to a freshly formatted SD card (as I did with 10.1 originally using Leapin' Lar's method). I have watched all the installs go bye. After it's all done the NC shuts down as it always has. When I restart I end up with a stock NC so it isn't booting off of the card to Android.
Any ideas?
Thanks,
V
volpo222 said:
Hi,
I have been using an SD install for all of 10.1 with no problem. I tried the 10.2 nightly and I cannot get it to boot to Android. I built the SD card the same way I did all the rest. It boots to CMW I have also installed the alternate. I load the nightly and gapps on to a freshly formatted SD card (as I did with 10.1 originally using Leapin' Lar's method). I have watched all the installs go bye. After it's all done the NC shuts down as it always has. When I restart I end up with a stock NC so it isn't booting off of the card to Android.
Any ideas?
Thanks,
V
Click to expand...
Click to collapse
Maybe the disk image is too small? The zip is 20mb bigger. Expand the partition and try again
bowguy said:
Maybe the disk image is too small? The zip is 20mb bigger. Expand the partition and try again
Click to expand...
Click to collapse
I don't think so. I watched it all expand and all of the zips finish without an error message. It all fits on the boot track without a problem.
As I understand the SD card gets 4 partitions written to it. #1 is the BOOT partition. 2 & 3 are where the OS and execution space live and #4 is another FAT 32 partition for media files etc. That all works as expected. I'm left with 2GB in partition #4 (it's a 4GB card).
Thanks,
V
Just flashed and it is working great. I would say a little smoother and faster than 10.1. It does look like we lost about 20MB of free RAM though, for me anyway.
volpo222 said:
Hi,
I have been using an SD install for all of 10.1 with no problem. I tried the 10.2 nightly and I cannot get it to boot to Android. I built the SD card the same way I did all the rest. It boots to CMW I have also installed the alternate. I load the nightly and gapps on to a freshly formatted SD card (as I did with 10.1 originally using Leapin' Lar's method). I have watched all the installs go bye. After it's all done the NC shuts down as it always has. When I restart I end up with a stock NC so it isn't booting off of the card to Android.
Any ideas?
Click to expand...
Click to collapse
Oh shoot, I'd forgotten that we changed the way we mount /system and /data in 4.3-based ROMs, so the SD card installer needs updating for 4.3. FAQ updated (I'll update it again once that installer's updated).
steven676 said:
Oh shoot, I'd forgotten that we changed the way we mount /system and /data in 4.3-based ROMs, so the SD card installer needs updating for 4.3. FAQ updated (I'll update it again once that installer's updated).
Click to expand...
Click to collapse
Thanks for the info.
I can't believe it,
Android 4.3 on my good old Nook Color!
Thank you very much @steven676!
Clean Installed it and it runs very, very smooth from first start...
Only one issue I've found: Pie control is not really useable - Pie can only be opened from time to time - in most cases it doesn't react on any screen position.
I would love to use Expanded Desktop with pie control...
But anyway - the very best ROM I've had installed on Nook Color!!!
kind regards
bitstra
Dirty flashed over 10.1 nightly last night, updated gapps. Took a long time to boot, but when it did, everything was fine.
As of this morning, I haven't noticed any fstrim messages in the logcat that I would expect. Maybe I haven't waited long enough or they are scrolling out before I see them? It was on the charger overnight so that should satisfy the conditions.
Edit: fstrim ran on /data and /cache when I checked a 2nd time.
Frank
steven676 said:
Oh shoot, I'd forgotten that we changed the way we mount /system and /data in 4.3-based ROMs, so the SD card installer needs updating for 4.3. FAQ updated (I'll update it again once that installer's updated).
Click to expand...
Click to collapse
Leapinlar's now updated the SD card installer to support CM10.2 -- head over there to grab the latest revision.
sziggins said:
Hi Steven,
All working great and really smooth just some questions.
You mention the source of this kernel. This is the same as in 10.1 so to build the kernel separately for 10.2 we just need the encore_cm10.2_defconfig?
Click to expand...
Click to collapse
Essentially, yes. We made a decision a while back to keep the same source branch for all releases where possible, to reduce our maintenance burden.
sziggins said:
I see the changes are:
CONFIG_AUDIT=y (instead of # CONFIG_AUDIT is not set)
# CONFIG_NETFILTER_XT_TARGET_AUDIT is not set
CONFIG_FB_OMAP2_VSYNC_SYSFS=y
CONFIG_AUDIT_GENERIC=y
Is vsync the following?
Click to expand...
Click to collapse
Not really. CONFIG_FB_OMAP2_VSYNC_SYSFS is a default-y option introduced by a patch checked in since the last time we updated the CM10.1 defconfig, so running "make encore_cm10.1_defconfig" would produce a build configuration with that option enabled as well. The commented-out (line starting with #) option obviously has no effect -- in this case, it's a reflection of an option that's only available for selection when CONFIG_AUDIT is enabled. CONFIG_AUDIT_GENERIC is an internal configuration option that the build system automatically enables when you select CONFIG_AUDIT on ARM systems.
"Improved display performance" mostly refers to a combination of Android 4.3's further graphics optimizations and the various display performance changes which were backported to CM10.1 nightlies a couple of weeks ago.
sziggins said:
EDIT:
I think vsync doesn't work, I get this from my logcat:
Code:
08-27 17:28:30.781 W/SurfaceFlinger( 1282): getting VSYNC period from fb HAL: 11111111
08-27 17:28:30.781 W/SurfaceFlinger( 1282): no suitable EGLConfig found, trying without EGL_FRAMEBUFFER_TARGET_ANDROID
08-27 17:28:30.781 W/SurfaceFlinger( 1282): no suitable EGLConfig found, trying without EGL_RECORDABLE_ANDROID
08-27 17:28:30.781 W/SurfaceFlinger( 1282): no suitable EGLConfig found, trying with 16-bit color allowed
Click to expand...
Click to collapse
That's actually normal. SurfaceFlinger is searching for a configuration that it's happy with -- it's not finding all the display features it wants in the graphics drivers, so it falls back. (You can actually see that first "no suitable EGLConfig found, trying without EGL_FRAMEBUFFER_TARGET_ANDROID" message when booting a Galaxy Nexus.)
steven676 said:
Leapinlar's now updated the SD card installer to support CM10.2 -- head over there to grab the latest revision.
Click to expand...
Click to collapse
I dont't want to make a fresh install. Can I change something before the upgrade from 10.1 and than install 10.2?
Thanks
mvsroot said:
I dont't want to make a fresh install. Can I change something before the upgrade from 10.1 and than install 10.2?
Thanks
Click to expand...
Click to collapse
Yes, see my edit in that referenced post.
Sent from my Nook HD+ running CM10.1 on emmc.
On a good note for me. Chromecast works with the latest Netflix on the NC - I do not watch Movies/TV on the device itself so this was at least a pleasant surprise..
Is anyone running Twonky Beam successfully with this ROM? I'm using it to beam content to a Roku box from my NC with a 10.1 emmc build. It doesn't work from a 10.2 08-22 SD build on an HD+.
Edit: In addition to Twonky Beam app on the NC, you need Twonky on your Roku (from Roku's channel store) to try it with a Roku box.
Sent from my Nook Color Running CM 10.1 from emmc
So I'm playing with this and I have to say how impressed I am. It's not smooth by any means and it is quite slow. Plus it has trouble with a lot of apps because of their UI's (too fancy with the effects). That being said, it works. I have no idea how this thing manages to stay alive, but I'm amazed that it works as well as it does. It's definitely usable and just so damn impressive.
Sent from my NookColor using xda app-developers app
I am trying to boot an AOSP-based ROM that I compiled the other day but it won't get past the "google" screen, it wouldn't even get to the splash screen of the ROM. I pulled a logcat and it shows "E/sdcard missing packages.list". I have googled, xda search, etc. but nothing really came up. Someone mentioned trying to enable VT-x but I already have that enabled so I don't really see that being the issue. I have included the pastebin of the logcat; when I copy/paste into pastebin it pasted all weird so sorry for that but the error is at the end.
http://pastebin.com/embed_js.php?i=V0NMawes
Any help would be greatly appreciated.
sdcard is not a serious problem (will be big problem later though). Your framework env may be incorrect, and you maybe got a wrong ramdisk. (ART is failing create boot.oat.) Also, your audioflinger is dead.(Big issue) It may be caused incompatible vendor lib, etc. Your paste is too hard to read. Get less line changes.
hi there
im trying to compile AOSP systemimage for android 7.1.2 r4 and i seem to have worked the first compilation errors due to flex being out of date and not maintained in the repo.
But now jack is destroying my memory. i read that nougat could be compiled with 4gb ram and im sure you can but how.
some of the things i have done....
export jack arguments
export java heap options
made a huge swapfile
using ccache
the build gets to 40% before the memory starts hemhoraging. I persistantly perform the jack tricks and hit make again but it will only go 20 more compilation counters before stopping again and theres no way i can keep that up.
short of buying and replacing the ddr ram in my laptop is there any thing else i can do?
I was able to finally figure out how to use mma and i am currently building the system.img one apk x library x binutil at a time. I also changed my device mk so it could make sparse images and made snod after compiling system/extra/ext4_utils. Its really time consuming and resetting jack rarely works but restarting the pc seems to get it farther. Of course this is only a problem when compiliing apks. My phone doesnt seem to have the same problem compiling apks when i can get the ide to do it. I have been trying to compile apks on android studio for a year and cant get past the java lang class not found error. I have it pointed to the right place and ive followed every forum fix i can find but no go
Can someone help me with adding a tunable extra partition. well maybe not tunable but static. i want to be able to mount and unmount a second partition on an sd card that could vary in size.
i have tried doing this with my fstab.cv1 in m6 boot.img but no go. i get boot loop or stuck on logo screen. Even messing around with init.rc screwed me up