My friend got an AT&T SGS2 last night, and I helped her put CM7 (stable - not a nightly) onto her phone. She wanted to send me a screenshot of a theme she installed, but everytime she tries to take a screenshot she gets the following error:
error: /mnt/sdcard/tmpshot.bmp (permission denied)
Screenshot is saved at null
I did a few searches on XDA and Google, but couldn't find anything related to the SGS2. Could someone shed some light onto this for me?
First I would recommend AT LEAST going to the newest nightly that CM7 OFFICIALLY put out #181 as it is better than the rc1 which did not have as many fixes in it anyways. Or I ACTUALLY would recommend using the newest nightly from https://s3.amazonaws.com/cyanogenmodbuild.s3.mortimer.me.uk/index.html which is EVEN BETTER with more fixes than #181 and definatelly better than rc1.
Second she can just hold down the power button and when the onscreen popup comes up choose screenshot. This MAY have worked on rc1 but that is a VERY OLD release and I cannot remember if it even had scrrenshot on the power menu screen. The link I put is from Sam3000 and he is just building from source without adding/deleting anything that the CM TEAM is fixing.
Sent From My KickAss ATT SGS2 SPORTING CM7
I think I'm misunderstanding something. The latest official nightly I see for the ATT SGS2 is Nightly 20 which can be found here:
http://download.cyanogenmod.com/?type=nightly&device=galaxys2att
You said that the latest is 181?
I checked ou the Unofficial nightlies page you linked and had a few questions about those.
1. Are they safe to flash right over the stable 7.1 official CM7 release with a cache and dalvik wipe? Or do you have to wipe the entire phone?
2. Is there a specific unofficial nightly that you recommend? I know from running nightlies on my Atrix that some are amazingly stable and snappy, while others are most definately not. I'd like my friend to have a smooth experience on her phone. She's not tech savvy, and this is her first Android device. I'd like her to have the best experience possible, which is why I had her flash the stable instead of a nightly to begin with.
Also, I did more research into the error with screenshots. The Droid Incredible had the same issue which could be fixed by changing the permissions on some files in /system. I still can't find anything SGS2 related with the error though. So again, if anyone has any info for me about it I'd appreciate it. If its between running a line or two in ADB and experiencing with flashing various nightlies, I think I'd rather stick with the simple fix.
Thanks in advance!
You can flash the nightlies right over stable CM7 with just wiping Dalvik and cache. Also like RockRatt mentioned.. The newer nightlies are far better than the "stable" that was put out. I would just recommend grabbing one of the latest from sam3000's thread.
Not sure about the screenshot error. Try updating to a nightly and see if the problem is still present.
sent from my Galaxy SII
DeathKoil said:
I think I'm misunderstanding something. The latest official nightly I see for the ATT SGS2 is Nightly 20 which can be found here:
http://download.cyanogenmod.com/?type=nightly&device=galaxys2att
You said that the latest is 181?
I checked ou the Unofficial nightlies page you linked and had a few questions about those.
1. Are they safe to flash right over the stable 7.1 official CM7 release with a cache and dalvik wipe? Or do you have to wipe the entire phone?
2. Is there a specific unofficial nightly that you recommend? I know from running nightlies on my Atrix that some are amazingly stable and snappy, while others are most definately not. I'd like my friend to have a smooth experience on her phone. She's not tech savvy, and this is her first Android device. I'd like her to have the best experience possible, which is why I had her flash the stable instead of a nightly to begin with.
Also, I did more research into the error with screenshots. The Droid Incredible had the same issue which could be fixed by changing the permissions on some files in /system. I still can't find anything SGS2 related with the error though. So again, if anyone has any info for me about it I'd appreciate it. If its between running a line or two in ADB and experiencing with flashing various nightlies, I think I'd rather stick with the simple fix.
Thanks in advance!
Click to expand...
Click to collapse
Yes #20 was the last OFFICIAL nightly for the SGS2 sorry about that. I am still keeping up with my old captivate flashing CM7 and CM9 on it and its last OFFICIAL CM7 was #181 so sorry about the confusion.
I would go with the newest from the link I provided from Sam3000's site. I use it for mine and the wife and ONLY update hers knce I know it is stable enough so she doesnt have any issues either. So I would say go for his newest that came out on 02-15-2012 and it should be totally stable for her. I only ever wipe Dalvich Cache between builds but for you updating hers I would suggest to flash the newest unofficial nightly, then before rebooting flashing it a second time for good measure. This way only wiping Dalvich all her apps and everything else will still be there.
OR if you have any issues and or want to make sure just do a titanium backup of all her apps. Then wipe data/factory reset (will wipe out any and all parts of what she already had), then flash the newesr nightly twice before rebooting, then flash gapps before rebooting, then boot it up, then reinstall any apps from the market needed, then open tibu and restore USER APPS ONLY, She wont have any saved data for the apps this way but your starting her off clean again.
Sent From My KickAss ATT SGS2 SPORTING CM7
Well I had my friend install the nightly from the 15th like was suggested.
Sure enough, she still can't take screen shots, though this time it is a different error. It says....
Media Unmounted
Unable to save Screenshot: mBitmap = null
It appears CM7's default install requires that you have an SDCard in order to take screenshots, pictures, videos, or recieve text messages with pictures or videos. This is "fixed" by going into...
Settings > Cyanogenmod > Applications > Check off "Use Internal Storage".
After a reboot, your internal memory will be mounted as /mnt/sdcard instead of /mnt/emmc. This fixes the issue in the latest nightly. It should be noted though that I had her try this on the stable 7.1 release, and she was still unable to take screenshots.
Everything is fine now. I am a bit disappointed that CM ships "broken" to an average user if they don't have an SDCard. Some users (like me) know how to fix it right away. Your average user would have no clue. My friend Erika (above average user) is very computer literate, but has no linux experience and would have never figured out that the "media unmounted" errors she was getting were because the default setup requires an sdcard or that you toggle the "Use Internal Memory" checkbox.
Anyway, thank you for the responses!
Ian
Related
Q&A: [ROM-1.2/GRJ90] CM7Tab for the GTab (based on CM7 Nightlies) [Update: 08-15-11]
MOD EDIT: THIS IS THE Q&A SECTION FOR [ROM - 1.2] CyanogenMod 7 nightlies for the GTab
ALL Q&A FOR THIS ROM HAPPENS HERE.
Thanks.
---------------------------------------------------
As suggested, I have decided to make my own thread for the Cyanogenmod nightlies and other ROMs. It will make things a lot easier in the long run.
Disclaimer: as with the other Roms, Use at your own risk! Since the CM7 nightlies are basically an ongoing beta, you run the risk to brick your Gtab if you are not careful. Use to learn NxFlash first before attempting to flash ROMS. Also, do yourself a favor and get Titanium Backup! Always backup yours apps/settings and wipe data/cache/dalvik before flashing.
These will be using the bootloader's 1.2 Pershoot's kernel (2.6.32.43 / 1.4 ghz Kernel) for GB. This ROM works with the Gtab and should work with the ZPAD altough I have no confirmation of this yet.
Thanks goes out to: Team Douche/Cyanogenmod Devs for making a great ROM, Zyhong for showing me how to update to 1.2 and a few more tricks, Maxdamage for taking the time to compile the nightlies for 1.1 users, Pershoot for making such a great kernel and Roebeet for being the one that inspired me to take my journey down the Android rom lane.
1) latest version of CM7Tab: CM7Tab build 08082011 (Nightlies changelog)
2) Test CM7Tab with 4950 drivers: Test Build 08152011
Changes in modified version
1- replaced DSPmanager.apk with a previous version that is known to work (7.0.3) (if you open it, it FCs)
2- vold.fstab is setup as sdcard for internal storage & emmc for external card
3- using pershoot's 2.6.32.43 GB kernel for 1.2 bootloader (For more info, check his blog.
4- Read_ahead_kd increased from 128 to 2048.
5- Set up overclocking by default and battery saver script + cpu governors via userinit.sh (from Zyhong's ROM, based on Caulkin's scripts).
6- Replaced Camera libs & apk to stop the 8-bit pixelling.
7- Increased dalvik.vm.heapsize to 64m (07102011)
8- Set some values to improve video playback (07272011)
9- Changed values for lowmemorykiller minfree in init.rc (08072011).
10- changed EMMC to microsd (08072011)
11- updated ROM up to 2.3.5 (08072011)
12- Camera fix (08082011)
To-do list:
1- remove some apks (such as Rom manager) & create a removed apks folder.
--------------------------------
Issues:
1) Once you set up DSPmanager, it force crashes.
1) Vanilla CM7 nightly (only vold.fstab was modified): Latest build: Build 07262011 (Changelog)
If you have suggestions/ideas, do not hesitate to share them.
thank you.
Going to give it a try, tried cm7 a while ago and was great with it but seemed a bit slow. On Iluminate now do I have to flash back to stock?
Sent from my Android Illuminate using XDA Premium App
nelomen said:
Going to give it a try, tried cm7 a while ago and was great with it but seemed a bit slow. On Iluminate now do I have to flash back to stock?
Sent from my Android Illuminate using XDA Premium App
Click to expand...
Click to collapse
How long ago did you try it? I try to play areound with CM7 with the CM7tab ROM to see if I can speed it up a little as well. You can give it a try and tell me what you think.
Icewyng said:
As suggested, I have decided to make my own thread for the Cyanogenmod nightlies and other ROMs. It will make things a lot easier in the long run.
Disclaimer: as with the other Roms, Use at your own risk! Since the CM7 nightlies are basically an ongoing beta, you run the risk to brick your Gtab if you are not careful. Use to learn NxFlash first before attempting to flash ROMS. Also, do yourself a favor and get Titanium Backup! Always backup yours apps/settings and wipe data/cache/dalvik before flashing.
These will be using the bootloader's 1.2 Pershoot's kernel (2.6.32.42 / 1.4 ghz Kernel) for GB. This ROM works with the Gtab and should work with the ZPAD altough I have no confirmation of this yet.
Thanks goes out to: Team Douche/Cyanogenmod Devs for making a great ROM, Zyhong for showing me how to update to 1.2 and a few more tricks, Maxdamage for taking the time to compile the nightlies for 1.1 users, Pershoot for making such a great kernel and Roebeet for being the one that inspired me to take my journey down the Android rom lane.
Issues:
1) Once you set up DSPmanager, it force crashes.
1) Vanilla CM7 nightly (only vold.fstab was modified):
Latest build: Nightly build 07112011 (Changelog)
2) Modified version of the ROM: CM7Tab build 07102011
Changes in modified version
1) replaced DSPmanager.apk with a previous version that is known to work (7.0.3) (if you open it, it FCs)
2) vold.fstab is setup as sdcard for internal storage & emmc for external card
3) using pershoot's 2.6.32.42 GB kernel for 1.2 bootloader (For more info, check his blog.
4) Read_ahead_kd increased from 128 to 512.
5) Set up overclocking by default and battery saver script + cpu governors via userinit.sh (from Zyhong's ROM, based on Caulkin's scripts).
6) Replaced Camera libs & apk to stop the 8-bit pixelling.
7) Changed values for lowmemorykiller (07102011).
8- Increased dalvik.vm.heapsize to 64m (07102011)
RC1 version of the rom with changes: 7.1.0 RC1 with Pershoot 42 kernel
(Sorry if this is short but I will improve the thread as it goes)
To-do list:
1) remove some apks (such as Rom manager) & create a removed apks folder.
2) change the EMMC to Sdcard2
If you have suggestions/ideas, do not hesitate to share them.
Click to expand...
Click to collapse
personally I have been using your build for a while and quite happy with it except the market which sometime shows my apps and other time it doesn't. I have not tried any market fixes yet, so it is partiality my fault as well.
Icewyng said:
How long ago did you try it? I try to play areound with CM7 with the CM7tab ROM to see if I can speed it up a little as well. You can give it a try and tell me what you think.
Click to expand...
Click to collapse
I tried it today but was getting a lot of fc's, it did seem a little faster then I remember except the boot up was really slow as I remember. I did not give it a full try because I failed to wipe everything because I was at work and wasn't really supposed to be on it. I will do it again tonight with full wipe and see if it gives better results and let you know.
I just realized you have a tab build so I will try that one. The one thing I noticed right away with cm7 is that my tablet looked like a phone and I have been jumping around from HC roms and got used to a more tablet specific rom. I will give you update in a few hours I think.
Edit: have been trying for a couple of hours now but sent me in to boot loop had nvflash back to stock, will give it another shot once this silly Tap n Tap is finished loading.
Sent from my SAMSUNG-SGH-I997 using XDA Premium App
rob_z11 said:
personally I have been using your build for a while and quite happy with it except the market which sometime shows my apps and other time it doesn't. I have not tried any market fixes yet, so it is partiality my fault as well.
Click to expand...
Click to collapse
Dalingrin was kind enough to provide a fix that seems to resolve most of the problems with market (including buying apps). It was merged in build 07092011+ so give it a try and tell me how it goes.
nelomen said:
I tried it today but was getting a lot of fc's, it did seem a little faster then I remember except the boot up was really slow as I remember. I did not give it a full try because I failed to wipe everything because I was at work and wasn't really supposed to be on it. I will do it again tonight with full wipe and see if it gives better results and let you know.
I just realized you have a tab build so I will try that one. The one thing I noticed right away with cm7 is that my tablet looked like a phone and I have been jumping around from HC roms and got used to a more tablet specific rom. I will give you update in a few hours I think.
Click to expand...
Click to collapse
The FCs you were getting were probbly from DSPManager. It is a known issue that seems to come from a "broken pipe" in one of the libs. For now, it is best just to remove it.
For the bootup, someone suggested moving apps to the SD card. Apparently, it would speed up the process.
I am conscious that 2.3.4 is made with phones in mind but it is a step up from Froyo and having partial hardware acceleration helps.
Just tried again and got stuck on CM7 logo boot loop, this was with the CM7 tab build. did full wipe of cache, dalvik, and user data. Not sure what happened. Restoring to Illuminate rom if you have some ideas on how or what else I can do to try this rom let me know.
Hey there Ice.
First off, awesome work on this and thank you for taking the time.
I would recommend editing the build.prop file to set the Manufacturer to HTC. This fixes the playback issue with Netflix (Chipmunk). I tested this out fully on my gTab last night and it's the ONLY setting that needs to be modified. Aside from that, everything seems to work.
Good work!
Hi
Has anyone tried installing volume+ on this rom? I'm on BL1.1 CM7 rom but volume+ does not install. If this works, I'll take the bold step to upgrade to BL1.2.
I don't know if it's just my hardware. My gtab's speaker is very soft and I want to try cranking it up with volume+ (which works on my phone running cm7).
thanks a lot.
DroidTV phone size not full screen....Anyone have other apps that did that after....
I was using DroidTV, and it was full-screen and then rebuild my G Tab with the cm7tabl-0710200-1.2 and when I reinstalled DroidTV it is now phone size display on the G Tablet.
I used Titanium Backup to restore the app and the settings. Anyone have issues like this with an app that did that after re-installing after a full rebuild? Any build.prop setting or somewhere I could check?
Thanks. Steve.
Thanks everyone for your feedback.
@Mike: I have heard of this before and wasn't sure if anyone would be interested in it. I will change that on the CM7Tab version in the next few days.
@Vhend: Yes, Vol+ works on 1.2. You enter CWM and it works great here.
@Artful: I will look into this. It might just be that the rsolution isnÈt set right. I will let you know how it goes.
Icewyng said:
Thanks everyone for your feedback.
@Mike: I have heard of this before and wasn't sure if anyone would be interested in it. I will change that on the CM7Tab version in the next few days.
@Vhend: Yes, Vol+ works on 1.2. You enter CWM and it works great here.
@Artful: I will look into this. It might just be that the rsolution isnÈt set right. I will let you know how it goes.
Click to expand...
Click to collapse
Thanks Ice. Other than that I have yet to find any major issues that in the build.
Other than apps that open portrait only with the bottom on the side with the power button. Tried to say to not rotate 90 degrees but they still open that way Apps that open landscape then won't rotate to the 90 degree position but portrait apps still open that way
This is the most stable I have used and performance seems good. A co-workers has the same build, I installed it for them since they are techie-challenged, and theirs is turtle slow because I think they have Skype running all the time.
Icewyng said:
Thanks everyone for your feedback.
@Vhend: Yes, Vol+ works on 1.2. You enter CWM and it works great here.
Click to expand...
Click to collapse
sorry for not being clear. I did not mean pressing the volume+ button. i actually meant this app to boost the volume of gtablet.
http://forum.xda-developers.com/showthread.php?t=1023433
I guess the app has dependencies on dsp manager, that's why it did not work on my B1.1 cm7. Since you have replaced the dsp with a workable one in your rom, I would like to check if the volume+ app works here.
Appreciate your work on the rom!
vhendsume said:
sorry for not being clear. I did not mean pressing the volume+ button. i actually meant this app to boost the volume of gtablet.
http://forum.xda-developers.com/showthread.php?t=1023433
I guess the app has dependencies on dsp manager, that's why it did not work on my B1.1 cm7. Since you have replaced the dsp with a workable one in your rom, I would like to check if the volume+ app works here.
Appreciate your work on the rom!
Click to expand...
Click to collapse
Actually, I think it has more to do with a problem with one of the audio libraries. I did a logcat and it seems something called AudioFlinger can't set a parameter properly.
If anyone can fix this, I can send the logcat to help out.
I wanted to apologize for not being able to upload the new nightly today. I had to rebuild my computer and took the opportunity to switch to a new Linux distro. Just tested the new system and all is great.
I will post Build 07172011 later this morning.
Where are the nightly's getting posted now? Thanks and this is the most stable MOD I've had on my G Tab.
Do video apps work as far as no rotation with Oovoo, yahoo, reelportal, etc? Audio work okay with chatting?
mirrors:
http://dev-host.org/cops0ujuwmm0/update-cm-7.1.0-smb_a1002-07182011-1.2.zip
http://dev-host.org/8xjvaysomd1i/update-cm7tab-07102011-1.2.zip.zip
-deck
Hey, Just got a 32gb touchpad
I want to run Android 4 on it, but i see multiple roms there. Was wondering which one has the least bugs. Im hoping for a fully functional one, but not sure whats there. CM9 seems fairly broken.
Im looking for a fully functional non WEbOS if someone could poitn me to one
Thanks!
I'm not one to complain, but there have been quite a few of these threads started recently... such as:
http://forum.xda-developers.com/showthread.php?t=1618380
As far as CM9 goes, I have been running the Alpha 2 version and have absolutely no problems with it besides the camera and mic not working, and the sound issue while the screen is off. ClassicNerd and AOKP are some good alternatives and they have a lot of support, but there are more. Best place to start is the great sticky post by MindSplit : http://forum.xda-developers.com/showthread.php?t=1552196
If you see CM9 as "broken" then dont bother with Android on your TouchPad. All CM9 ROMs are about the same as far as how stable they are. And all CM9 ROMs just about have the same issues. They are all built from the same source.
It multiboots tho, so i assume i can install as many things as i want..
Rekzer said:
It multiboots tho, so i assume i can install as many things as i want..
Click to expand...
Click to collapse
You can only install one version of android.
I currently use ClassicNerd Rom and love it. Yes, like stated earlier they all are still a little buggy. However it is very cool to multi-boot(moboot) between webOS and android . On the Android side I'm able to download apps from the market and play a load of games. PM me and I will point you to the instructions I used.
Im running CM9 now! THis thing FLIES, only bug i really care about is the audio distortion when the screen is off one, but nbd really!
Question: If i want to Update CM, i just place it on the SD and install via CWM right. How does Moboot know its CM? If i installed another rom via CWM would Moboot properly boot into it?
AND
Is the storage shared? As in, if i boot into WebOS, will it see all the files on the 32gig storage that android sees?
Rekzer said:
Im running CM9 now! THis thing FLIES, only bug i really care about is the audio distortion when the screen is off one, but nbd really!
Question: If i want to Update CM, i just place it on the SD and install via CWM right. How does Moboot know its CM? If i installed another rom via CWM would Moboot properly boot into it?
AND
Is the storage shared? As in, if i boot into WebOS, will it see all the files on the 32gig storage that android sees?
Click to expand...
Click to collapse
Yes. just place it on your sd card and install in clockwork. It's wise to wipe cache and dalvik before you flash. There may be times when you get more than one android version show up on moboot if it is two completely different ROMs but you just need to delete the other listing. there are tutorials on how to do that. and your sd card is shared. it's structured a little differently in each OS but it all shares the same storage.
Thanks a bunch guys!
One last question
I have a bunch of apps backed up via Titanium off my GSII, can those be restored safely onto the touchpad(non system apps ofc)
*** CM9 nightlies have been discontinued.. see: http://forum.xda-developers.com/showthread.php?p=29135522#post29135522 ***
For those who have dabbled in the Nook Color or HP TouchPad scenes you may have seen unofficial CM9 nightlies from me.. so in the same fashion here are the Nook Tablet builds - these should be considered in Alpha status.
***The nightly builds are currently for the 1GB "Acclaim" Nook Tablets ONLY***
I take no credit for the work put in to get nook tablet CM9 running - all the credit there goes to chrmhoffmann, fattire, nemith and countless others I may not even know. Please be sure to thank them for their efforts. I'm just building ROMs from their source code.
I *strongly* recommend everyone look over fattire's guide for building and giving it a try to learn a little about how this all works, it's how I got started on the nook color with these unofficial builds. After clearing with fattire and chrmhoffmann I decided to provide these builds for people who don't have the hardware/ability to build themselves.
These builds are all straight sync with CM source along with the nook tablet device and kernel trees. They are *NOT* tested releases (I don't even have a Nook Tablet) so please be aware that the builds could be broken at any time, and are provided as-is. Please be comfortable with adb and/or using recovery to wipe/restore/nuke at any time.
Builds are sync'd at 9am UTC - they will be available to download approx 15 mins after that.
There is no official "changelog" for nightlies, you can reference the commits in the device tree, kernel tree and main CM gerrit. Note that the CM gerrit shows things that are merged for ALL official devices, not all of these will apply to the Nook Tablet, however, anything not referenced by a device name is also included in these builds.
The only addition I have made to these builds is the inclusion of "Goo Manager" as a system app. More on the reasons for this below...
Downloads
There are a few ways to get the builds:
1) Browse the hosted folder here: http://techerrata.com/browse/nightly_kangs/acclaim
2) Follow @CM_Acclaim on twitter for announcements of the builds as they hit the host (PLEASE NOTE: @CM_Acclaim IS A TWITTER BOT - don't bother tweeting at it)
3) Use the Goo Manager app to receive notifications of new builds and download them directly on your device.
Latest ICS gapps can be found here http://goo-inside.me/gapps or mirrored here http://techerrata.com/browse/gapps
Goo Manager - Notable features
1) Notification of new builds and gapps updates with one click - or auto-check frequency in settings. Goo Manager auto-checks the md5 for every download.
2) Automated flashing of downloaded roms/gapps/other files with TWRP
3) Install TWRP 2.1 with one click (menu - install openscript recovery) - TWRP is still experimental and will overwrite ClockworkMod on emmc.
4) *Incremental updates* (experimental) - if you like to stay on the bleeding edge and flash every night. Incremental updates are diff'd server side so you only download the changed files from the build the night before. These downloads average 30-40mb in size (vs ~120mb for the full rom), so you get faster downloads, updates and less wear on your device's flash memory. Incremental updates ONLY work from the previous night's build to the latest. When you check for updates in Goo Manager it will offer you an incremental if applicable.
Updates
For the latest updates/announcements follow me on twitter, or check back here.
Credit and Thanks
Thanks to chrmhoffmann, fattire, nemith and the rest of the CM acclaim team for making this possible. Thanks to fellow TeamWin members Kevank for providing the hosting and to s0up for the Goo Manager app.
Neat.
This should make things easier.
Again though-- until some changes are added to the 3.0 kernel, if you have a newer 512MB NookTablet, the nightlies won't work and you'll probably come up with a blackscreen and have to reflash. Chrmhoffman's latest 2.6.35 build though should work if you have the newer model and/or want the 2.6.35 kernel w/cm9.
* EXPERIMENTAL * EXPERIMENTAL * EXPERIMENTAL * EXPERIMENTAL *
Warning: This will overwrite the internal storage with CM9. The instructions below assume you have a rooted NT running stock, CM7, or CM9.
Requirements
1GB NT (the 512MB NTs are not yet supported by the 3.0 kernel.)
Software: Rooted stock, CM7, or CM9
A full battery
a formatted SD card in the slot
wifi connection
(something else?)
To install the experimental CM9 w/3.0 kernel on a 1GB NT:
(steps are from memory and are to be refined soon)
Use the Google Play Market or other method to install Goo Manager to your device.
Run Goo Manager. Select the menu, and chose "install openscript recovery". Click through the options to confirm. At some point you may be asked to give Goo Manager superuser permissions.
The above steps should now cause TWRP2 recovery to be installed to your device. (You only need to do steps 1-3 again when you want to update or reinstall the TWRP2 recovery image.)
Now you can browse compatible roms for your device. Under /devs/eyballer/nightly_kangs/acclaim/ you should see some nightly builds. Choose the one you wish to install. Wait for it to download.
Once it's downloaded successfully, you should be able to select the newly downloaded rom from the notification menu, and then request that it be installed. Alternately, you can go to the Flash ROMS menu to flash previously downloaded ROMS.
See elsewhere in this thread for any other update.zips that you may wish to download and install. You can put more than one update.zip in the queue.
When you are ready, select the order and flash selected button on the bottom right.
It is sometimes preferable to wipe the cache/dalvik cache partition when doing an upgrade. You also have the option to automate a backup (not a bad idea). If you are coming from stock BN software or for any other reason wish to clear all user information, you may also wish to wipe the /data. partition. This is not generally recommended as wiping /data will delete your personal information.
When you're done configuring your flash, choose Flash, and then confirm.
If all goes well, there will be a reboot, your choice(s) will be flashed, and then the system will restart into the new CM9. If it doesn't work (very possible, as this is still experimental), post below and let the devs know what went wrong.
* EXPERIMENTAL * EXPERIMENTAL * EXPERIMENTAL * EXPERIMENTAL *
This video has more information about TWRP2 and Goo Manager, although the device discussed is a HP Tablet. Some things like the boot menu will be different, but most other details will apply.
Good luck, and be sure NOT to do this with an 512MB Nook Tablet. If you screw up and do install it, you will need to re-flash a CM9 using 2.6.35.
fattire said:
This should make things easier.
Again though-- if you have a newer 512MB NookTablet, the nightlies won't work.
Click to expand...
Click to collapse
I'm assuming it's because it's using the newer kernel?
Hmmmm, so these will be sorta nice.....
Fattire, did you update the TWRP .zip to a non-totally-messed-up version?
If so I'll jump on these and try them.
Also are these builds the latest 0.04 for our tablet?
Sent from my Team A CM9 Alpha 0.03 Nook Tablet
Keithn said:
I'm assuming it's because it's using the newer kernel?
Click to expand...
Click to collapse
Yes, the 3.0 kernel has issues with 512MB-- the kindle fire had the same issues, and if you read the latter few posts in the kernel thread, you can read more about it. Hashcode apparently knows how to fix it, but until then, don't install this on a 512MB NT.
SilentStormer said:
Hmmmm, so these will be sorta nice.....
Fattire, did you update the TWRP .zip to a non-totally-messed-up version?
If so I'll jump on these and try them.
Also are these builds the latest 0.04 for our tablet?
Click to expand...
Click to collapse
No guarantees. eyeballer is using the latest experimental one from the twrp thread. It has the fix from arcon and has been successfully used by frustro. I of course have not ever run it, so I can't make any claim of success.... this is all experimental.
The builds are nightly, so right now they're about at par with chrmhoffmann's alpha .04 (which of course uses 2.6.35 kernel), but if I'm not mistaken, eyeballer builds 'em fresh every day from the cm9 repos plus whatever changes are made to the kernel and acclaim-specific repositories. That means they can be total crap in the future, and who knows if twrp2 is even any good either...
This is seriously guinea pig territory. So unless and until you're willing to take some risks, you might want to hold out for what others have to say.
I can confirm that this worked for me.
1. Intall goomanager from play.google.com
2. from menu choose install openrecovery script, it downloaded and installed openrecovery-twrp-2.1.4-acclaim.img
3 browse compatible roms, navigate to /devs/eyballer/nightly_kangs/acclaim/ and choose the first one
4 menu home
5 choose download gapps packages and choose gapps-ics-20120429-signed.zip
I had 2 download failures and had to repeat these steps till the download was correctly completed and then main menu flash roms select the 2 zips and I was done
very nice and smooth.
Can you add tun.ko and cifs.ko to the kernel config please?
Thanks
Do we have to use twrp to install this rom?
meghd00t said:
Can you add tun.ko and cifs.ko to the kernel config please?
Thanks
Click to expand...
Click to collapse
You're requesting tun.ko and cifs.ko compiled as modules?
Used Goo Manager to flash TWRP, had to pull the SD card and install it for it to mount.
Downloaded the first 900 build (I see there is 2 for some reason)
Clean install including /system wipe
Have had 2 or 3 "sleeps of death"
Screen wouldn't turn on with N button or power button.
Had to hold power for 10+ seconds to do a hard shut down.
Cranked my screen off timer to 10 minutes.
Keep up the great work.
Also Netflix loads and has audio no video but I'm sure you're aware of that.
Two other things I've noticed.
Can confirm the SD card mounts every time so far but the SD card did randomly unmount once.
Lastly, when trying to download Atorrent (for watching Game of Thrones) I get an error saying "Can not install to USB mass storage or SD card"
Sent from my Galaxy Nexus
great share!
Fattitire and or Eyeballer I have a very humble request that I think might help us help you.
I have been using Goo Manager for a few weeks and love it. It's a great tool. If you could add just a line or even two words to the Change Log tab in GM like "bug fix" "nothing major" "hardware acceleration working " it would be very helpful for us to decide if we should flash an update or skip it and wait for the next one.
Once again thank you, and great work.
Sent from my Galaxy Nexus
Helltoupee said:
Fattitire and or Eyeballer I have a very humble request that I think might help us help you.
I have been using Goo Manager for a few weeks and love it. It's a great tool. If you could add just a line or even two words to the Change Log tab in GM like "bug fix" "nothing major" "hardware acceleration working " it would be very helpful for us to decide if we should flash an update or skip it and wait for the next one.
Once again thank you, and great work.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
While this seems simple to add, it's not. My build system for these unofficial nightlies is completely automated so adding something to changelog would require me to go through the commits and then manually log into goo.im and update the rom info for every build. I don't do that for the devices I own, let alone the ones I don't
I posted links in the OP to all the source that is used to compile so it's up to the user to read and see if they would like to update. Of course as more people start running the builds, the discussion here usually will give you hints as to what's added too.
Updated the OP with another download notification method. We have a twitter system that will send out a tweet for every new build that hits our server with the link to the download and a QR code. You can follow CM_Acclaim for this.
Thank you for the explanation. I completely understand.
Sent from my Galaxy Nexus
Nighty change log blog thing I found for all CM9 builds. Enjoy.
http://changelog.bbqdroid.org/
Sent from my Galaxy Nexus
Do these nightly builds have an embedded expiration date like the chrmhoffmann's Alpha 0.0x builds?
Also, has anyone tried getting one of these builds to run off an SD card using succulent's method (http://forum.xda-developers.com/showthread.php?t=1545766)?
I kinda have a problem :\ I have lines running across half of my screen and its kinda freaking me out.. I'm not pointing fingers but it did happen after I installed this ROM
---------- Post added at 10:58 PM ---------- Previous post was at 10:52 PM ----------
My problem is solved... Oddly enough installing another rom makes the lines go away. I'm sorry for posting for no reason. lol have a great day
The 3.0 kernel still has problems. Hopefully these will be fixed in a later build.
digixmax said:
Do these nightly builds have an embedded expiration date like the chrmhoffmann's Alpha 0.0x builds?
Also, has anyone tried getting one of these builds to run off an SD card using succulent's method (http://forum.xda-developers.com/showthread.php?t=1545766)?
Click to expand...
Click to collapse
Don't try it. My modifications are for kernel 2.6.x version of CM9 not 3.0.x CM9.
I've build a bootable 3.0.x CM9 on sdcard. I wouldn't recommend this build yet due to LCD brightness and no sleep issue. LCD brightness will take 50% of the battery. This build is mainly testing.
I loaded recovery. Downloaded CM9 ics then gapps. When I go to flash roms nook reboots then I get the cynaboot image then nook boots back to cm7. What am I doing wrong?
The problem I was having is that cm7 did not mount my SD card on reboot. Had to load eyeballers first build through cwm. Then once in cm9 I could load through twrp. Running good so far.
I've recently installed AOKP(Jellybean 4.2.2) Task650 (http://forum.xda-developers.com/showthread.php?t=1808015) and the basic install seemed to go very well. I came from stock 4.0.4 (rooted) and for the record I'm using Recovery 6.0.3.0 and I did a full wipe including format system, data, cache, dalvik etc. I installed the new gapps after the ROM, and later restored apps using Titanium.
I have a few issues I can't quite sort out though, and I'm not sure if they are JB, Nova or AOKP related so I thought I'd start a new thread.
1) Lockscreen doesn't appear. At all. When I wake the tablet up, it just comes straight back on to the previously used screen. I've checked all the standard Security settings (unlock mode set to slide or pattern, lock on power button, etc) and also the fancier AOKP ones, but whatever I do the lockscreen just does not appear. I've re-cleared cache and dalvik.
2) Notifications are not showing in the Notifications area. I can see the AOKP 'Toggles' icons/tiles for wi-fi, bluetooth, GPS, etc; the clock; the battery level; the wi-fi SSID, etc - but no general Notifications at all (e.g. list of any updated apps, any download statuses, Poweramp mini controls, new emails/facebook messages, Samba active display, etc).
When these various notification are issued, I do see them appear briefly in the lower-right corner in a grey rectangular box which covers the clock/battery area of the status bar (so the notifications do appear to be triggering) but as soon as that brief message disappears, I can't see any of the notifications within the pop-up notifications area where they should be.
Does anyone familiar with JB, AOKP or this particular ROM have any suggestions, as I'm as a loss at the moment?
Andre
Ah, no-one with any ideas of where these issues might be coming from then?
I might have to try another full-wipe install, and if that fails just go back to stock 4.0.4 until (if ever) Samsung releases a JB update for the original 10.1 tab.
Andre
andrewilley said:
Ah, no-one with any ideas of where these issues might be coming from then?
I might have to try another full-wipe install, and if that fails just go back to stock 4.0.4 until (if ever) Samsung releases a JB update for the original 10.1 tab.
Andre
Click to expand...
Click to collapse
I'm not familiar with that rom, but there are a few things you can try.
1. Try posting in the development thread, it might be a known issue that has a quick fix.
2. If you really want to stick with that rom try the full wipe again. But since you already started with one I don't know if it will fix the problems.
3. If you want to stay with jb I would recommend Aopk build 6 by djmatt604. It runs smoothly and the dev is pretty active.
Hope this helps even a little.
kilometers4 said:
I'm not familiar with that rom, but there are a few things you can try.
1. Try posting in the development thread, it might be a known issue that has a quick fix.
2. If you really want to stick with that rom try the full wipe again. But since you already started with one I don't know if it will fix the problems.
3. If you want to stay with jb I would recommend Aopk build 6 by djmatt604. It runs smoothly and the dev is pretty active.
Click to expand...
Click to collapse
Many thanks for the reply. I have searched and asked in the dev's thread, but I get the very clear impression that if it works on his hardware and no one else has the same problem, his opinion is that it's 100% up to me to sort it out - which is entirely his prerogative, of course: his ROM, his thread, his rules.
Thanks for the recommendation of another AOPK option (I assume you mean [ROM][P7510][4.2.2][UNOFFICIAL] AOKP Build 6 :: MR1 :: Mar 29 Nightly). I think I might go down that route since, like you, I'm rather dubious that another full-wipe will be any different to the first one.
Andre
andrewilley said:
...
Thanks for the recommendation of another AOPK option (I assume you mean [ROM][P7510][4.2.2][UNOFFICIAL] AOKP Build 6 :: MR1 :: Mar 29 Nightly). I think I might go down that route since, like you, I'm rather dubious that another full-wipe will be any different to the first one.
Andre
Click to expand...
Click to collapse
Yup that's the one. I'd recommend doing a full wipe on the first install to avoid issues. Let me know if you have any other questions.
I went with [ROM][KERNEL][RECOVERY][JB4.2]Infamous AOKP 1.4 (14-Apr-13) in the end, from the same dev you suggested. I added Nova as my launcher and it all works like a charm (well, after I recovered myself from a stupid near-brick when I decided to format the user sdcard in order to clear out any remaining junk from old installs; it cleared out a lot more than I wanted!!!)
Andre
andrewilley said:
I went with [ROM][KERNEL][RECOVERY][JB4.2]Infamous AOKP 1.4 (14-Apr-13) in the end, from the same dev you suggested. I added Nova as my launcher and it all works like a charm (well, after I recovered myself from a stupid near-brick when I decided to format the user sdcard in order to clear out any remaining junk from old installs; it cleared out a lot more than I wanted!!!)
Andre
Click to expand...
Click to collapse
Yeah, I usually just wipe data / Factory reset when doing a full wipe and then go in manually and clean out folders that I don't need to clear space. SD maid is a good app for clearing unused space too.
kilometers4 said:
Yeah, I usually just wipe data / Factory reset when doing a full wipe and then go in manually and clean out folders that I don't need to clear space. SD maid is a good app for clearing unused space too.
Click to expand...
Click to collapse
Yeah, I'm normally the same but I thought I'd be nice and thorough for once and get rid of any remaining legacy ICS stuff which some JB updates shove into hidden folders when you upgrade. In hindsight, I shouldn't have bothered.
Still, at least when I finally did get the system recovered enough to install the new ROM, the free space was amazing!
Andre
I got the same problem...how to solve it bro....
srinuchry said:
I got the same problem...how to solve it bro....
Click to expand...
Click to collapse
I think the problem may have been with something that Titanium Backup restored from my previous setup, but I never found out what. I had to do a factory reset to clear it in the end (although not a full ROM reinstall).
As I'd already gone that far though, rather than risking re-installing apps again I actually chose another ROM anyway - Infamous (see above) - which I'm very happy with, and the devs there seem much happier to talk to you in general. Just my observation anyway, your experiences could well be quite different of course.
Andre
~EDIT~
Recently I rooted and flashed CM 11. Any time I try to go and play a video, whether it's from the internal storage, sd card, or stream from a website, I just get "Can't play video."
Does anyone know of any reasons why this would be happening and how how to fix it? Or any suggestions? Should I reflash?
Also, usually when you hold down the Droid Home button you get a list of all recent apps as well as a link to the Task Manager at the bottom. There is no such link now though. Is this an Android Kitkat thing or a CM thing? How do I get to the Task Manager?
varxtis said:
...
There seem to be pretty significant shortcuts/features missing and I can't tell if thats because it's kitkat, or because it's CM.
Example:
1.) Sound - ~EDIT~ Found "Sound" button. Wishing it had "vibrate" mode but at least now I can Toggle normal/mute.
2.) Brightness - On this one, there is a Button that takes you to a brightness bar, which is fine... but it won't let me select "Auto". It seems more like a glitch than anything when I tap it.
...
Click to expand...
Click to collapse
The NT hardware does not have vibration or light sensor capabilities.
digixmax said:
The NT hardware does not have vibration or light sensor capabilities.
Click to expand...
Click to collapse
Thank you ^_^ Fair enough, She can definitely live without them.
Now its just a matter of understanding why videos can't be played. It wouldn't have anything to do with which gApps I used would it?
varxtis said:
Thank you ^_^ Fair enough, She can definitely live without them.
Now its just a matter of understanding why videos can't be played. It wouldn't have anything to do with which gApps I used would it?
Click to expand...
Click to collapse
Videos cannot be played because of a kernel bug. The CM11 Official Nightlies have this issue fixed.
If you are running the official CM11 nightlies, what build number is it? Could be a regression.
I apologize,
Ive been checking for updates periodically, but Im not very familiar with what nightlies are. I figure these are updates/patches that are done on a nightly bases.
Right now my CyanogenMod Version is
11-20131220-UNOFFICIAL-acclaim
Build Number:
cm_acclaim-userdebug 4.4.2 KOT49H e9e3ba9b67 test-keys
Thanks to your post, I went ahead into "About Tablet" and then into CyanogenMod Updates to take a closer look. Since flashing CM11 Ive only been checking "New Versions (Stable only)", but I didn't even realize you can change which updates you can search for... so again I thanks to your suggestion I changed it to "Update types: New Versions (incl, Nightlies)"
Three options became available... so I downloaded cm-11-20140218-NIGHTLY.
Should I install?
I'd suggest trying the M3 snapshot: cm-11-20140210-SNAPSHOT-M3-acclaim.zip (http://download.cyanogenmod.org/get/jenkins/58498/cm-11-20140210-SNAPSHOT-M3-acclaim.zip).
Awesome,
As always, thank you very much
Now, Is that something I could just download and run straight from the tablet main UI? Or would I download it, put into same bootSD card I used to flash CM, reboot nook into recovery and then flash the snapshot zip? Either way isfine, just want to know which way to go.
varxtis said:
Awesome,
As always, thank you very much
Now, Is that something I could just download and run straight from the tablet main UI? Or would I download it, put into same bootSD card I used to flash CM, reboot nook into recovery and then flash the snapshot zip? Either way isfine, just want to know which way to go.
Click to expand...
Click to collapse
You have to flash the zip via recovery (either TWRP or CWM, depends on what you have installed).
Make sure to do these things while in recovery, before flashing the zip. Do *not* touch /rom, /factory, /recovery:
1. wipe cache partition;
2. wipe dalvik-cache;
3. wipe data partition;
4. wipe system partition;
5. NOW you can flash the zip.