Related
Introducing...
Darktremor Apps2SD 2.7.5.3 Beta 04
Date of Release: January 29, 2011
Download Current Version
Instructions - Change Log - Commands - ROM List - Developer's Guide
Darktremor Apps2SD Fan Page ----
Darktremor Apps2SD Development Group
Are you installing Darktremor Apps2SD on your phone? Here are the instructions to help you: Facebook
Are you a developer wanting to include Darktremor Apps2SD in your latest ROM? Here is the Developer Guide: Facebook
Click to expand...
Click to collapse
Update on Beta 4
It seems I'm getting mixed results with these betas. I'm not sure why this is occurring, some people have been able to get this working right while others have had a hard time with it.
Currently, I'm rebuilding the entire program. This takes a while because I have to figure out how to pack all these options into the program but make it small enough to where it will run correctly.
I will say that some of the beta features are coming back out...one of them is the search for a partition code. I suspect that code may be leading me into issues with certain platforms, so I'm going back to the 2.7.5.2 method of mounting (mmcblk0p2 or mmcblk1p2).
Also, parts of the code will use Busybox Ash (the only code that won't will be starta2sd, which will still use Bash for the time being). The startup code will definitely use Busybox Ash.
Until then, here are the links to the the last two betas and the last official release:
Version 2.7.5.3 Beta 04 - http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.3-beta04-signed.zip
Version 2.7.5.3 Beta 03 - http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.3-beta03-signed.zip
Version 2.7.5.2-1 - http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.2-1-signed.zip
And, if you want past versions, you can view the repository: ftp://dtuser:[email protected] (ignore the smiley face...that's XDA doing that.)
Click to expand...
Click to collapse
Beta 04 took longer than I expected to release. I have done major changes to the code:
1. New commands: convert-ext4 - This will convert your EXT3 partition into EXT4. Just a friendly reminder on this command: Not every rom supports EXT4, so it is possible to go into a boot loop if you switch roms. Use with caution.
2. Reworked convert-ext3 (convert-ext4 gets similar code)...now a flag file is set before the reboot (no conversion is done before the reboot). At load time, the conversion is performed. This takes longer in the reboot process and you may think your phone has locked up...wait about five minutes before doing anything with the phone.
3. Repair is rebuilt...now it uses existing commands to repair the setup (reinstall, remove, cachesd, cachepart, nocache, datasd, nodata). Definitely shrinks the code.
4. Added fix_permissions program to the package. This may help with Superuser issues when using the datasd feature. It is used in reinstall, remove, datasd and nodata.
5. a2sd install is back!!! Both a2sd install and a2sd reinstall do the exact same thing.
6. Dalvik heap code has been shrunk and now creates a file called dalvikheap. Actually, the code has been doing this all along (since about 2.7.5.2, I think), but I never put the code in to use the file.
7. Low Memory Killer code has also been shrunk and uses a file caled dtset_lowmem to set the low memory killer parameter.
8. Replaced Busybox PS function with Toolbox PS. The issue with Busybox PS is that it gives a false reading when I look for android.process.acore (which is the main program when the GUI starts up). If that is present, the program thinks you are trying to run Darktremor without any command line parameters. This was because Busybox would report the process was there when, in reality, it wasn't (validated this when my phone was boot looping.) Toolbox's PS reports the correct setting. This should fix the bootlooping issues some people are experiencing.
9. New commands: usedtbusybox and usedefaultbusybox - these commands may help in diagnosing issues that is may be related to the native Busybox on your rom. a2sd usedtbusybox will use the Busybox that is packaged with Darktremor. a2sd usedefaultbusybox will turn back on the scan behavior of the program introduced in Beta 03.
10. Support for Darktremor Apps2SD version 2.7 and earlier has been discontinued. To upgrade correctly from one of those versions, use version 2.7.5.3 Beta 03b or earlier.
11. Finally fixed stalled boot issues (or at least my tests with several roms says so.)
See the change log for additional details.
You will notice that if the program runs repair and finds a problem, it will correct the issue and reboot. You will see a second reboot when the dalvik-cache clears (this is to fix timing issues with CyanogenMod...I can't control that startup as well as I can other roms). This only happens if repair is ran or you flash a new rom (as repair will realign all data). If you are upgrading from a previous version of Darktremor, you should not see the reboots.
Click to expand...
Click to collapse
This is Darktremor Apps2SD, a multipurpose program that primarily allows a user to execute applications created for the Android OS on their Secure Digital card (with the proper setup...more on that later). But, Darktremor Apps2SD is all about stability. The goal is to be able for all users of the Android OS to be able to take advantage of a method to run their applications from a secure digital card.
But just because the Darktremor Apps2SD is all about stability, doesn't mean it isn't packed with features:
- Move applications (both free and paid) to the Secure Digital card.
- Move Dalvik Cache to run either from your Secure Digital card or from your cache partition and clears the cache on demand.
- Boot Loop Protection: prevents the phone from boot looping in the event the SD card could not be mounted.
- Dalvik JIT for faster performance on Roms which support it.
- User selectable sizes for the Dalvik heap sizes, allowing a user to freely optimize their system.
- Activate a swap partition on your SD card and sets how often the swap partition is utilized.
- Automatically fixes configuration issues.
- Users can check the free space on their SD card and check the installation to make sure all is setup correctly.
- Runs ZipAlign on demand...this makes your programs load faster.
- Built in help system for easy reference of commands.
- All features can also be reversed without repartitioning your Secure Digital card.
- New logging features assists in troubleshooting issues.
- Commands to set the Low Memory Killer feature at boot time. Great for those people who are the "set it and forget it" type.
- And more...
Darktremor Apps2SD is not the same as Froyo Apps2SD. Froyo Apps2SD creates a secure folder on the FAT32 section of your SD card (this is the section that you see when you mount your phone to your computer) and stores the programs there. This is nice as you don't have to do anything special with the phone, but it isn't backwards compatible with older versions of Android (Cupcake, Donut, Eclair) and, because of the way Froyo works, older programs not designed for Froyo will automatically stay on your internal storage (unless you install a program that forces the move to your SD card).
Darktremor Apps2SD takes a different approach. Based on the original CyanogenMod works, Darktremor Apps2SD uses symbolic linking to force Android into moving your applications to the SD card. Because Android will not allow anything to be ran from the FAT32 partition on your SD card (and, in Froyo, it will only allow you to run programs from a special folder), Darktremor utilizes filesystems called EXT2, EXT3 and EXT4. Each one of these filesystems is native to Linux (the operating system running Android), which allows you to run programs from them (same as, say, a computer running Ubuntu). This method is completely compatible with all versions of Android, including Froyo. In fact, you can run both the Darktremor Apps2SD and Froyo Apps2SD at the same time.
Check out the list of Roms that either have Darktremor Apps2SD installed or are compatible with Darktremor Apps2SD. Click on the link labeled ROM List at the top of this message.
Darktremor Apps2SD Installation Instructions
For the list of people that helped me test this on the various roms that use or can use Darktremor Apps2SD and the changelog: http://forum.xda-developers.com/showpost.php?p=7034326&postcount=3
Click to expand...
Click to collapse
The installation instructions can be found here: http://forum.xda-developers.com/showpost.php?p=7021325&postcount=2
Click to expand...
Click to collapse
If you want a list of commands for Apps2SD, type a2sd help.
Reserved...
Thank you so much!!! Can I flash this with ClockworkMod Recovery? I saw that you recommend Amon's but just thought I would ask before I flash back to Amon's.
Since we only have Amon's and Darch's recoveries, those were the only ones I could test with. It's possible you may be able to use ClockworkMod (I didn't ask my testers what recovery they were using).
Do a backup of your phone, then try it. If it works, let me know and I'll update the post.
THATTON said:
Thank you so much!!! Can I flash this with ClockworkMod Recovery? I saw that you recommend Amon's but just thought I would ask before I flash back to Amon's.
Click to expand...
Click to collapse
tkirton said:
Since we only have Amon's and Darch's recoveries, those were the only ones I could test with. It's possible you may be able to use ClockworkMod (I didn't ask my testers what recovery they were using).
Do a backup of your phone, then try it. If it works, let me know and I'll update the post.
Click to expand...
Click to collapse
Everything went well and I'm up an running. Thanks.
Ps-proud to be a test subject. Lol
As a reward for being the test subject, I have updated both the install post to include Clockworks Recovery and added your name on the Credits post as the tester.
THATTON said:
Everything went well and I'm up an running. Thanks.
Ps-proud to be a test subject. Lol
Click to expand...
Click to collapse
tkirton said:
As a reward for being the test subject, I have updated both the install post to include Clockworks Recovery and added your name on the Credits post as the tester.
Click to expand...
Click to collapse
Hey, that works for me! Thank you!
Add Apps2SD support in your Rom
I created a guide in my main thread on how to add Apps2SD into roms that don't have it.
http://forum.xda-developers.com/showthread.php?t=715116
Bump....New version 2.7.5 Preview Fix 4 is out (and there was a PF3, but it was only released to Desire users to try to work through the NAND protection on their device...their changes are part of PF4).
Has anyone tried this on the latest CM6 nightly build?
Chahk said:
Has anyone tried this on the latest CM6 nightly build?
Click to expand...
Click to collapse
I was going to, but the nightly are so often that I would hate to keep having to do it every update...well the nightlies have slowed down....I might try it out! Will report back if works!
djdarkknight96 said:
I was going to, but the nightly are so often that I would hate to keep having to do it every update...well the nightlies have slowed down....I might try it out! Will report back if works!
Click to expand...
Click to collapse
Cool, let us know here and in the CM thread. I would love to know as well.
THATTON said:
Cool, let us know here and in the CM thread. I would love to know as well.
Click to expand...
Click to collapse
I flashed the zip in recovery using CM6 and it did not work. The zip flashed without error but my apps did not move to the EXT partition
I'll check it out and see what's going on.
EDIT: It's possible that Busybox Run-Parts won't process two files with the same name. Since I can't run it, can you run a logcat so I can see what's going on. Send it to [email protected] and I'll take a look at it.
mightykc said:
I flashed the zip in recovery using CM6 and it did not work. The zip flashed without error but my apps did not move to the EXT partition
Click to expand...
Click to collapse
mightykc said:
I flashed the zip in recovery using CM6 and it did not work. The zip flashed without error but my apps did not move to the EXT partition
Click to expand...
Click to collapse
It works on CM6. All you need to do is flash boot from Modaco's (Paul's) Froyo R21 with a2sd.
I'm eager to try this -- but I noticed that in the update.zip, there's a "new" copy of Vending.apk. Why is the Market app being replaced? How does this one differ from the stock FRF91 copy? It makes me a bit nervous to be replacing the app. Previous apps2sd approaches haven't needed to modify this. Can you explain a bit what's going on under the covers?
I would have thought that just an init script, an ext3 partition and a few symlinks would be all that was required...
Thanks
Don't worry about it. It only replaces the app when you execute a2sd fixmarket. This was to address an issue with a disappearing market, but since then the problem has been pointed to zipalign (which is why zipalign won't run automatically at boot).
I think PF4a doesn't even have the command anymore, so, unless you manually push it from /data/a2sd, it won't replace anything.
The upcoming RC1 version will have that removed, as it is no longer needed.
Here's how Darktremor Apps2SD works:
1. First thing it does is transfer control to launcha2sd, which is ran by using bash instead of sh (bash seems to be more stable).
2. Once launcha2sd is running, it performs a quick test to see if you are asking for help (a2sd help). If so, it displays the contents of the help file and exits.
3. Next, it checks to see if the following properties are in the init.rc:
- cm.filesystem.ready or dc.filesystem.ready (only one has to be present)
If so, it can run the more advanced boota2sd. If not, it will run a basic version of Apps2SD (FYI, these properties actually are used to stop the init.rc until Apps2SD [and any other script the rom developer deems necessary to run] are complete. This prevents dalvikvm from interferring, preventing a race condition).
4. Next, it runs starta2sd unless you don't have the properties stated before, then it continues by moving the /data/app and /data/app-private to SD card (if needed and after attempting to mount the ext partition). Then it activates swap (if available) then it exits.
5. Under starta2sd, it checks to see if a command was requested (install, remove, cachesd, cachepart, jit, nojit, etc...). If so, it runs the appropriate commands for the command requested.
6. If no command was given, it checks to see if apps2sd is being ran for the first time. If so, it transfers control to boota2sd. If not, it displays a message stating you need to supply a command and promptly exits.
7. In boota2sd, it checks for the old flag files (from version 2.5 - 2.7) and moves them to the /data directory.
8. Next, boota2sd attempts to mount the ext partition. If that fails, it will engage Boot Loop Protection, which puts your /data/app, /data/app-private and /data/dalvik-cache (if it is stored on the SD card) back to internal storage and sets the No Apps2SD flag file. This can be reversed by executing a2sd install once the issue with the ext partition is fixed.
9. Next, it checks for flag files and whether the correct setup exists. If not (say you have the Dalvik to SD cache flag file active but your dalvik-cache is being stored on your internal storage), the program initiates auto-repair.
10. Once that is complete, it checks to see if it needs to move applications to the SD card and moves them, unless the No Apps2SD flag file is present.
11. Next, it looks to see if the user has activated ZipAlign on boot (a2sd zipalign) and, if so, will proceed to zipalign the /data/app and /data/app-private directories.
12. Next, it activates the swap partition, unless the swap partition isn't present or the No Swap flag file is set.
13. The program then ends.
This is the automated boot sequence. You can control the behavior of apps2sd by using commands (a2sd install, a2sd cachepart, a2sd align...)
System files are only modified if there is a need to (i.e. JIT) and only if the user activates the correct command (i.e. a2sd jit, a2sd nojit). In fact, the only time the /system partition is changed to a read-write state is during the JIT installation (and that is changed back to read-only when the setup is complete)...otherwise, the /system partition is read-only through the entire Apps2SD run.
mlevin said:
I'm eager to try this -- but I noticed that in the update.zip, there's a "new" copy of Vending.apk. Why is the Market app being replaced? How does this one differ from the stock FRF91 copy? It makes me a bit nervous to be replacing the app. Previous apps2sd approaches haven't needed to modify this. Can you explain a bit what's going on under the covers?
I would have thought that just an init script, an ext3 partition and a few symlinks would be all that was required...
Thanks
Click to expand...
Click to collapse
tkirton said:
Don't worry about it. It only replaces the app when you execute a2sd fixmarket. This was to address an issue with a disappearing market, but since then the problem has been pointed to zipalign (which is why zipalign won't run automatically at boot).
I think PF4a doesn't even have the command anymore, so, unless you manually push it from /data/a2sd, it won't replace anything.
The upcoming RC1 version will have that removed, as it is no longer needed.
Click to expand...
Click to collapse
Awesome! Thanks so much for the quick and detailed reply!
Just read through the code. Nice work!
I see that one of the options is to put dalvik-cache in /cache. Any reason apps can't be put into this partition as well? On a rooted device, /cache is mostly wasted space. Or does /cache get wiped on reboot like /tmp?
Nookie Froyo 0.6.8
is a development build of Froyo 2.2.1 for the Nook Color.
ClockworkMod flashable! - info below, please *read carefully* before flashing!
This build is near-AOSP and contains almost no extra software not deemed required for the device to function normally.
It is pre-rooted with SuperUser, busybox, SoftKeys v3.07, and ROM Manager 3.0.0.5 however.
The eventual intention will be a build that other devs and users can easily fork and create their own custom builds, themes, roms, etc.
** THIS IS A DEVELOPMENT BUILD **
Use this at your own risk! Myself, XDA, and NookDevs are *NOT RESPONSIBLE* for anything that happens directly or indirectly related to this software!
We're approaching a daily driver! Most things work now, including mp3 and video playback. Post any bugs you find here!
I'd like to thank all the nook color devs involved in getting to this state, testing, documenting, etc. We've got an amazing group of minds behind this device!
INFO
The microSD card image contains 4 partitions:
/dev/block/mmcblk1p1 : boot (fat32)
/dev/block/mmcblk1p2 : system (ext2)
/dev/block/mmcblk1p3 : data (ext3)
/dev/block/mmcblk1p4 : sdcard (fat32)
Use these partition IDs when following guides that require mounting/remounting filesystems.
What's Working:
MP3 playback
Video playback
Youtube, Pandora and other mp4 streaming apps (apps not included)
Accelerometer!
Wifi (adhoc + infrastructure!)
Graphics acceleration (LWP!)
Sound
Browser
Mostly working
Lockscreen is wrong size - REBOOT to fix
Not included / Not working
gapps ( gmail, youtube, maps, etc ) - can be installed, youtube fixed!
Bluetooth
FM radio
This build was created using the B&N kernel sources for 1.0.0, Omappedia's Froyo source ( currently RLS27.9.0.RC0 ), and binary drivers from TI for wireless, SGX530 acceleration, and DSP codecs.
Download:
This SD image requires a 2GB microSD card! Bigger is OK, smaller is not ok!
Note: if you wish to use a larger microSD card, you can use a partition editor to increase the size of the /sdcard partition (partition 4, fat32) *after* writing the image to your card.
Simply unzip this image and dd the file to your (empty) SD card, just like nooter.
nookie-froyo-SDIMAGE_2GB-0.5.1.gz 76459ec18fd32885257a3c8b7dbb2b76
nookie-froyo-SDIMAGE_2GB-0.5.6.img.gz 74e5310bcc21edf326bdc73a5652c124
nookie-froyo-SDIMAGE_2GB-0.5.8.img.gz 15158e735517c209a8f2ed14683a589c
nookie-froyo-SDIMAGE_2GB-0.5.9.img.gz 7d30f56eeede98ee1e99a0766f69dea3
nookie-froyo-SDIMAGE_2GB-0.6.6.img.gz fc58aa06fcfe1f46939ab72e38292abe
nookie-froyo-SDIMAGE_2GB-0.6.7.img.gz 92ef91dbac7a7baad3999256597b7920
nookie-froyo-SDIMAGE_2GB-0.6.8.img.gz
MD5: 18e7cc8393681ec590f698b7a671e859
If you want to customize your SD card, upgrade an already burned Nookie Froyo SD, live on the edge and burn it into your eMMC, or just want to poke around, download the base filesystem:
nookie-froyo-base-0.5.1.tar.gz 3e95a33e3926bc88011e66a724dccf8f
nookie-froyo-base-0.5.6.tar.gz 4419b21dd8eb56f6a6537345aa1c8ba1
nookie-froyo-base-0.5.8.tar.gz 2c279dbdaa6aad480590d55e48abf8ca
nookie-froyo-base-0.5.9.tar.gz 093a964685f0cbea2ef1aa8f6f0d7581
nookie-froyo-base-0.6.6.tar.gz 2304e337c351c667f27eb9aa4c3791b8
nookie-froyo-base-0.6.7.tar.gz 99b6a9d991951c368cf1f6b3429be958
nookie-froyo-base-0.6.8.tar.gz
MD5 c3c7aea7cdf8a3dde32acc1694f633aa
This archive also contains an uncompressed ramdisk image which you can easily edit, package, and copy to your boot partition.
ClockworkMod Flashable ZIP!
*IMPORTANT*
- please wipe data/factory reset if you're coming from B&N stock firmware or another rom!!
- please see other threads about installing and using CWM recovery - keep this thread to NF issues please
- this has been tested only using CWM 3.0.0.5 downloaded from market, be warned it may not work with IOMonster's kit or other versions. Let us know if you try and it does!
- replaces kernel and ramdisk - if you were using an alternate kernel you'll need to reflash it.
- This will irrevocably erase and replace the software on your eMMC! MAKE BACKUPS BEFORE FLASHING, you have been warned.
If you're upgrading from an older version of Nookie Froyo, you should not have to wipe - however if you do have problems *wipe data* and try again.
*IMPORTANT* - this zip does not require any extra steps such as formatting /boot, changing system permissions, and does not replace or remove CWM. If you are coming from a ROM that required these extra steps and are having issues, *please post your questions there* so the dev can be prompted to correct those issues properly.
If you're coming from a rom that doesn't support CWM properly see the following thread:
http://forum.xda-developers.com/showthread.php?p=11437545
Installing /system will take some time, and the progress bar doesn't update in realtime; you haven't 'locked up', just be patient as it may take a few minutes.
nookie-froyo-flashable-0.6.6.zip 6f61a464483ecf45d6e6e2d199b44d6c
nookie-froyo-flashable-0.6.7.zip 9bd13877addbad725a5bfe1eb13412df
nookie-froyo-flashable-0.6.8.zip
MD5: 03544d6a5a52eebdb468c89a5a2581e9
Please do not PM me for help, that's what this forum and the IRC rooms are for - I simply do not have the time to answer all of your questions, and asking them in a public forum will allow others with the same issue to help or learn from your experience!
CHANGELOG
v 0.5.6
permissions corrected on /system/bin/input for SoftKeys
corrected default cpu governor to conservative
added SuperUser
added busybox 1.17.2
added SoftKeys 3.00 ( thanks bpk! )
AdHoc WIFI support enabled
crypto/cryptofs added in kernel for ASEC support (required for installing some apks such as Angry Birds)
v 0.5.8
uses the /cache partition on eMMC instead of combining with data
replaces u-boot.bin to remove the 'touch the future..' splash (trademark)
increased refresh rate to improve responsiveness and reduce flicker (see tips in the next post)
added sensors lib - accelerometer works!
v 0.5.9
default web browser FC fix - no longer dies on location requests!
v 0.6.6
Youtube, Pandora, and other streaming media should now work.
added codecs for more media formats - including hw accelerated mp3 and video
vold reverted - no more broken SD card message
flashable zip!
updated SoftKeys to 3.07
fixed a /cache issue which sometimes prevented market downloads
v 0.6.7
SD card mount fixed - please post if you continue to have issues
Added back Mms, Phone, Camera, Telephony apks to resolve missing apps in Market - more apps should be available
Modified CWM zip reliability
v 0.6.8
Corrected improper handling of Format SD Card option - no longer formats /boot!
Touchscreen enhancements - no need to toggle screen on boot and better responsiveness around the edges - thanks deeper-blue!
Please see the updated issues/workarounds list in the following post
For more information, sources, and install instructions, please see:
http://nookdevs.com/NookColor:_Nookie_Froyo
Need help? Want to contribute? Join us in IRC! irc.freenode.net
#nookcolor - general chat, questions, ask for help here
#nookie - development
Do not try to Format SD card from Settings -> SD & Phone storage!
- there is currently a bug that causes the system to format the /boot partition instead of /sdcard when this option is used, leaving your NC unbootable. Format your SD card in your PC or another device if you need to! - fixed in 0.6.8!
FIRST BOOT TIPS -
On first boot, Launcher and SoftKeys will fight for control of the home intent - that is, when you boot the first time, your NC will ask you to pick your home activity.
*CHOOSE LAUNCHER* at first (DO NOT select 'always use this action'), and let the system boot and stabilize (3-4 minutes).
Hit Home (the N button). You'll be asked to choose your activity again, this time choose SoftKeys.
Try using one of the SU-required buttons (back or menu), and after a few moments SuperUser will prompt you to accept the action.
SoftKeys 3.06+ now prompt for SU permission at startup, just accept the superuser prompt when it pops, you'll still want to let the system stabilize for a minute or two.
If SoftKeys fails to ask for SU permissions, "Unable to execute as root":
Go to Settings -> Applications -> Manage Applications -> 'All'
Select SoftKeys from the list
'Force close' Softkeys if it's running, then 'Clear defaults'
Hit the N button, choose SoftKeys when prompted to choose your home action, accept the SU prompt when it pops.
Workarounds for some known bugs/issues:
(default in 0.5.8+) Improved Refresh-rate (no flicker! thanks [mbm]!): this should set the refresh rate to 68hz, the supposed default for the Nook Color's LCD panel -
Code:
adb shell echo 68000,1024/70/200/40,600/10/11/10 > /sys/devices/omapdss/display0/timings
Browser: force closes when opening a website that tries to use location services, due to the missing GPS. Try browsing to a url by typing in the google search box, and if you can get into the browser menu changing your homepage away from google will stop it from FC'ing on open.
Lockscreen wrong size: Simply reboot to correct this.
Touchscreen is slow/unresponsive:
Turn your screen off and then back on.
Disable Haptic Feedback in Settings -> Sounds.
Also, see this page for a possible calibration fix: http://nookdevs.com/Recalibrate_the_NookColor_touch_screen
(fixed in 0.5.6 w/included SoftKeys 3.00) No buttons! Try: http://forum.xda-developers.com/showthread.php?t=860153
(fixed in 0.5.6) SoftKeys - in 0.5.1 softkeys' buttons do not work due to a permissions issue. To fix, do:
Code:
adb shell mount -o remount,rw /dev/block/mmcblk1p2 /system
adb shell chmod 0755 /system/bin/input
Please post issues/workarounds/bugs in this thread, I'll try to keep this list updated.
To answer from the other thread...
Timeframe-- well, this isn't me doing this. But I think the devs just want to take the edges off, so be patient... I'm just the messenger on the news that it's been done. This is other people's accomplishment.
In fact, froyo was done weeks ago, though not entirely from open-source/freely distributed components like this (as far as I know).
To answer some questions--
BT not working, FM not working, accellerometer not working. Softkeys should work... dont' see why not anyway. It's stock froyo. No gapps, no Superuser.apk, no nothing over and above AOSP. Overclocking not in but should be possible... video playback hasn't been tried (it's early still!).... battery life who knows I haven't even had a chance to let it run down... I posted because the news was "out" anyway. I also can't compare to stock because I've never run stock, believe it or not. But it's based on the same kernel 2.6.29. It boots off a SD partitioned for system, data, cache, and sdcard. Only thing (I think) it touches on the internal storage is resetting that boot counter, otherwise you'd only get 7 boots at a time. Doesn't need much space. 2GB should be enough. That's what phones have anyway. Guess it depends what you want to do with it. Performance is decent, not steller compared to my g2 at least. Will benefit from OC.
devis said:
@fattire
Questions on everyone's (well, mine at least) mind... please answer as much as you can, and a big big thank you!!!
1. Is BT working?
2. Is FM working?
3. Can we still use SoftKeys for hardware key emulation?
4. Can we overclock the processor?
5. How's the video playback?
6. How's the battery life compared to stock?
7. Since you're booting from SD, does that mean the internal memory of the NC remains untouched, should we need to boot stock?
and
8. How does the device feel overall?
Click to expand...
Click to collapse
Nice stuff guys keep up the stellar work
Sent from my LogicPD Zoom2 using XDA App
So awesome, looking forward to the progression of this!
I got my SD to boot tonight!
It defiantly isn't for the faint of heart but it seems to work well enough as a good base to start on. Pretty snappy to boot.
I would like to emphasize that this is VERY rough around the edges and if you aren't planning on hacking with the kernel, or code, or attempting to make your own rom then this is NOT for you.
http://i.imgur.com/WRyNV.jpg
http://i.imgur.com/H4ahM.jpg
Defiantly awesome work (and pure AOSP + TI drivers) which means no propritary B&N bits
Thanks for releasing such and early build to the public. It's not often you see that.
(I won't even consider playing with this build)
As a humble Analysts I grovel at the feet of your magnificent tech prowess.
(thanks)
Does this include a working JIT or is that one of the things in progress?
That seems to be one of the more compelling things from froyo (at least for a device with more internal storage than a nexus one). I would expect (well, hope anyway) that the froyo JIT would have a noticeable impact on the speed...
Mods, can we please stickie this?
Very awesome... Will try it out later today!
Since this runs off the sdcard can you power down the NC and remove the sdcard and boot normally?
Novarider said:
Since this runs off the sdcard can you power down the NC and remove the sdcard and boot normally?
Click to expand...
Click to collapse
Read: http://nookdevs.com/NookColor:_Nookie_Froyo#After_you_have_burned_the_uSD_card
To get back to stock, just remove the uSD card and reboot.
Click to expand...
Click to collapse
It has all the info you want, and is mentioned in the first post.
cicada said:
Workarounds for some known bugs:
No buttons! Try: http://forum.xda-developers.com/showthread.php?t=860153
Click to expand...
Click to collapse
You also have the option of converting the volume buttons to back/menu as well. It is documented in this thread, but the filenames have changed in this build. You will need to modify the following files..
/system/usr/keylayout/qwerty.kl
/system/usr/keylayout/twl4030-keypad.kl
I am not a developer.
I am not likely to become one at this stage of the game...
I am, however, either brave or stupid because I am downloading the image and will see if it will boot on my NC.
I do this because:
A) I want to SEE froyo running on my NC, and
2) If I have any problems, feedback might help the devs
I love seeing all the progress that has been made on these things.
Is flash supported in the browser with this initial froyo build?
jay084 said:
Is flash supported in the browser with this initial froyo build?
Click to expand...
Click to collapse
I tested flash and it does work.. The flash plugin is not included in the build however, I had to find it and install it via ADB.
Just rebooted back to my regular rooted NC system after pulling the sdcard and can only say-
Marvelous.
Yes, it is slow, no keyboard and all of the other things that were spoken of in the initial posts, but IT WORKS.
I don't have time to do much else with it right at the moment, but I will mess with it more later.
BertoJG said:
I tested flash and it does work.. The flash plugin is not included in the build however, I had to find it and install it via ADB.
Click to expand...
Click to collapse
Could you post the flash plugin you used? I would really appreciate it. Could you also comment on the quality of flash videos online. I'd like to watch espn3 on the nook...in bed...lol
OK, so I booted the rom, and followed the instructions at nookdevs...
Installing superuser.apk and pushing su seemed to work just fine!!!
Softkeys installed and got superuser permissions and works as well.
Installed astro file manager, and that works fine too...
At that point, I wanted to mount the usb storage and move over a bunch of APK files... mounted the nook and could only see the mlo, img file etc... no problem creating an apk folder and putting files in there, but then I can't see that folder when I look for it in astro....
Any info on simply copying files via USB using this build?
Also, thanks to all the devs for the awesome work... looking forward to playing around with this more!!!
[ROM] CM7 8GB &16GB Compatible Beta for the Nook Tablet.., Updated 7th July to Beta
***** DISCLAIMER ******
Please note this software is still classed as experimental and you use this at your own risk. We have done some in house testing and all has worked fine but we cannot guarantee the exact same results for everyone. We accept no responsibility for any damage or loss of information with your Nook Tablet. You use this software at your own risk. By choosing to download and install this software on your device you accept that you are willing to risk your own device and that any damage and or total loss is your own responsibility.
FOR PROGRESS AND UPDATES CONTINUE TO READ THIS THREAD. FOR KNOWN BUGS AND ISSUES PLEASE SEE THIS THREAD
Below you will find Internal release of our Nook tablet CM7. This has been rebuilt from the most recent CM7 stable source. I'll update the 2nd posts with release information asap.
Please feel free to base your rom on ours, I believe it is now tested well enough and is sufficiently stable to use.
The Source for the CM7 android device folder, the kernel and meghd00ts Improved recovery can be found here Here
For information on what you can and can't do and reasons for this please visit HERE
INTERNAL VERSION 8GB & 16GB COMPATIBLE
Download HERE MD5 95043b08484aa218ccf93b5ef4785825
For the internal version you need have access to CWM either internally installed as your recovery or from an SD card. I'm not going to reinvent the wheel telling people how to do that. Just have a look through the development thread and you'll se numerous threads showing you how to do this.
This version has the ability to reboot to recovery added to the reboot option in the power menu. It does not however come with a recovery image, this was already released by lavero.burgos and can be downloaded from http://forum.xda-developers.com/showthread.php?t=1640958
PLEASE BACK EVERYTHING UP BEFORE YOUR BEGIN!!!!
Once you have CWM on screen with the downloaded update zip archive on your sd card, Follow these simple steps
1. Goto install zip from sdcard
2. Choose zip from sdcard ( if CWM hasn't recognized your SD card you need to eject it and re insert it once or twice, sometimes you need to go to mounts and unmount SD, pop it out and back in then select mount sd)
3. choose the CM7-TEAM-B-BETA1-signed.zip
4. scroll down and select Yes - Install CM7-TEAM-B-BETA1-signed.zip
5. sit back for a couple of minutes while the installation is carried out
That’s CM7 installed, next you need to prepare the rest of the device
1. press your power button once
2. ***OPTIONAL*** scroll down and select wipe data / factory reset, this is optional but if you are coming from a different OS it is recommended, if you don't it can sometimes causes force closes and various other issues.
3. you're ready to roll! scroll up and select reboot system, initial boot can take a while and does pause for a short while on the black screen between flash page and CM7 Animation, enjoy CM7 For Nook Tablet!
if you were already running a version of CM7 it is possible you may be able to skip the wipe data bit and just select wipe cache instead but it's best if you can wipe data and know that you have a clean install without any bugs remaining from a previous install. By all means try just clear cache and see how you go, if you seems to have lots of bugs we recommend doing a clear data and trying again.
SD VERSION IMAGE ***UPDATE NOT YET AVAILABLE this is the Alpha final version***
Download HERE
I've done the SD version a little different this time, it's as a 4gb SD image (the last partition is used as SDcard in CM7 so you can resize this partition to fill up your whole card if your card is bigger than 4gb). The image can be burn using windows Image writer or dd command in linux / OSX
The window software is available HERE.
To write the image on linux / osx do the following
WITHOUT your sd in the machine go to a terminal window and type
Code:
mount
Notice the drives that are showing they will be something like dev/sda. Now insert your SD and give it a moment to recognise it. Once again terminal type
Code:
mount
and you should have an extra device such as /dev/sdc showing which is your sdcard (it may say dev/sdc1 or something but you aren't interested in the number)
Once you have the SD device id use following code exchanging sdc for your device id
Code:
dd if=/location/of/SDfile.img of=/dev/sdc
Then sit back and wait, it will appear to be doing nothing and will take a long time but once done the command will complete and you have a nice new SD version of CM7 to run
Power off the nook, insert the sd and then power it on to enjoy your new CM7. If it done'st boot try completely powering of and ten connect power cable and wait for it to turn on and hopefully boot form SD. The first boot WILL take a few minutes. Consecutive boots will be faster
We've been asked a number of times for a donation link so I set one up you can click HERE. Or if you prefer to donate directly to myself or Goncezila by clicking on the donate buttons under our names. We thank you in advance for your generosity
***** DISCLAIMER ******
Please note this software is still classed as experimental and you use this at your own risk. We have done some in house testing and all has worked fine but we cannot guarantee the exact same results for everyone. We accept no responsibility for any damage or loss on information with you Nook Tablet. You use this software at your own risk.
First boot can take a little while. once in you will be requested to enter your Google account details, because your wifi is not yet connected you will be better of skipping these steps, you will be asked again as soon as you try to open Google Market anyway.
Tap the menu button and select settings (not adwsettings) go to wifi and setup your wifi connection, if for some reason wifi networks do not show, just toggle wifi off and on and it will sort it's self out
Feedback thread HERE so please make sure you post any questions and / or feedback in there and keep this thread for development only. Thank you!
Thanks and mentions
All those that support the new release, I'm sure you all know who you are
Quid246 - for his skills in photoshop to make our new splash screen (Alpha release)
Bauwks - Without him we would not be here. He blew the top off the bootloader and his thanks bar is no where near what it should be. Also a thank you for him agreeing to allow us to change his box image on the bootloader when we asked. Please find some of his posts and hit Thanks!
Loglud - again for helping us out with our research
AdamOutler - His guide was used to help us with kernel issues and build our SDcard version
succulent for pointing out that although we had commented out a file in the build, it was was still possible it was effecting up our new build. Also thanks to succulent for creating a build script that automatically added the 2nd boot onto the boot.img during source build. Thank Succulent! You’re a star, it just wasn't happening when I tried to do it
The Cyanogen Mod team for the initial build of Cyanogen mod that we ported over
Generally every other member of XDA - For being so supportive and throwing out ideas and experience!
Know issues, Hints and Tips
keyboard numbers layout when you hold a letter doesn't initially work, to fix just change keyboard language to your local setting e.g. US english
PROGRESS UPDATES
7th July 2012
Released beta update built on latest Stable CM7 source
Made some changes which will hopefully help with wifi issues
added some stability fixes
Added reboot to recovery in the reboot menu
Other minor issues tweaked to improve general overall performance and response
MARCH 20th{/I]
build.prop update zip added to support thread to cure mounting on USB issues
MARCH 9th
CM7 Final Alpha released
A complete relbuild of CM7 for the Nook Tablet. The new version is based on Gingerbread 2.3.7 CM7.2
All software updated to latest CM7.2 version and all files rebuilt to match
Full hardware video decoding for h264 encoded videos
Hardware acceleration for gfx
Wifi issues fixed so now connection should work without crashing
GAPPS removed as per Google requests and GAPPS download link added to OP
Many general system bugs fixed
Much much more that ill post here when home from vacation
MARCH 7th 2012
SD version of CM7 re-released
MARCH 5th 2012
Sorry for the lack of updates recently, Gonc and I have been really busy but we're happy to say a new build has been getting tested personally by us and has now been passed on to the testing team.
Bit more about it is HERE
FEB 19th 2012
2nd public release of CM7 for Nook Tablet.
Changes since original version are:
Format bricking issue fixed
Boot count issue where it resets your device to standard after 8 boots fixed
Market should now install any software you can get on there without the SD / USB issue
Browser should now happily play videos from mobile youtube
Graphics driver update allows playing of YouTube videos a720p without issue
Previous issues updating BusyBox should now be cured
Many games and applications that crashed on intro video will now work flawlessly
Internal media partition now fully accessible
internal media and sdcard now show when connected to USB on computer
more things which I'll add here when I remember them!
Feb 12th 2012
The new build which is alpha 8 is now ready and testing will begin in the next day or two.
Thanks to all members of the team for volunteering and to xIndirect for setting up the application forms online that everyone filled out to become members and the bug report forms he's also set up.
Goncezilla and I haven't really discussed a length of time for testing but generally Testing will continue until we believe that the remaining bugs do not cause severe problems for the end user. Once we are at that stage the donators will then get their copies which will allow us to gradually increase the testing coverage before finally being released as a beta to all member of XDA.
Myself and Goncezilla would like to take this opportunity to thank everyone for their support and understanding while we build you a version of CM7 for your Nook Tablets that we can be proud of
Feb 10th 2012
Following bugs have been fixed
SD format and bricking issue,
Market app install problem
Various software crashing when it tried to play video (even browser in mobile youtube)
Internal Media partition not mounting
Media partition not connecting to USB host when plugged in
Further information on updates and release are available HERE
Difference
Sorry for this question. What are the differences between internal and external? Does internal completely wipe and remove all Nook software, and external only boots CM7 with the card in and boots Nook style without?
For those on Windows machines (like me!), the free Mini Partition Wizard Home Edition can be used to create the SD card partitions. In this case just make the first partition Primary and Active; that will allow it to be seen as a bootable partition.
joeras said:
Sorry for this question. What are the differences between internal and external? Does internal completely wipe and remove all Nook software, and external only boots CM7 with the card in and boots Nook style without?
Click to expand...
Click to collapse
For Internal you need to have CWM running (either from SDcard or internally) and it WILL wipe your stock setup.
External runs purely from the SDCard and will not mess with your internal data.
Remember that Celtic and I are the only ones who have tested this as of yet so there may be unfound bugs! This is Beta after all
Please report all bugs here, do not PM us. We will try to validate and then correct them.
Enjoy everyone!
tonyp22 said:
For those on Windows machines (like me!), the free Mini Partition Wizard Home Edition can be used to create the SD card partitions. In this case just make the first partition Primary and Active; that will allow it to be seen as a bootable partition.
Click to expand...
Click to collapse
Yes sure just shrink the partitions a little to fit
We'll be adding a small modification to allow SDCard simulation when booting form card which will require adding a 4th partition later to act as the SDCard
Just thought to release as was to get it to everyone
I take it there is a way to go back to stock 1.4.0 just in case?
Unit is rebooting into cm7 as we speak. Looking great, speed is awesome. Great job guys.
arclite00 said:
I take it there is a way to go back to stock 1.4.0 just in case?
Click to expand...
Click to collapse
Yes you can flash a stock image the same way
did internal version. Downloaded to PC, unpacked, copied directly to directory via usb mount, restored. The restore went fast, and the initial boot-up was faster than my G2's backup restores...lol Connected to wifi, signed in, and up and running.. Fantastic!!! kudos!! and i used the "Thank You" button so i'm not thanking you in this reply...<snicker> Over all, everything done in less than 5 minutes. Now to tweak/customize/play with.
For those of us who don't know/have ubuntu, can you point to a good resource/post for creating the SD card under Windows 7 to run the SD card version of CM7?
Thanks!
If I don't see a clockworkmod folder I assume it installed wrong or I create the folder?
offlimitz said:
If I don't see a clockworkmod folder I assume it installed wrong or I create the folder?
Click to expand...
Click to collapse
I'm pretty sure Clockworkmod makes it as standard, as long as you have clockworkmod installed you should be able to just create the folders and drop your files in, do a backup from CWM and the folder should appear anyway
Thanks man. downloading sd release now. this doesn't affect the stock NT rom, right? the SD release ofc.
Celtic,
You may want to mention that the user may need to eject/reinsert the SD card for CWM recovery to recognize it.
Thanks for the good work!
darthvince said:
Celtic,
You may want to mention that the user may need to eject/reinsert the SD card for CWM recovery to recognize it.
Thanks for the good work!
Click to expand...
Click to collapse
I'll post that in first thread now.
Know-Fear said:
Unit is rebooting into cm7 as we speak. Looking great, speed is awesome. Great job guys.
Click to expand...
Click to collapse
After it's first boot it's a lot quicker than stock
In fact I think even the SD version is faster than stock, stock really is poor!
Just an FYI to everyone. We mounted the internal B&N partition (the 11 GB that used to locked out) to /data/media and the 1GB you used to have access to to /mnt/media.
Both fully rw!
Holy **** people!! 200 downloads already and only 20 of clicks of thanks on the first thread :s
I think my server bandwidth is going to get a hammering, I best check it's ok!
Sorry for the basic question, but when we go to CWM -> Advanced restore -> NTCM7, do we want to restore boot? system? data? cache? sd-ext? all?
Thanks!
URGENT UPDATE: THIS KERNEL COULD BREAK YOUR ROM. It re-orders the mtd block order, this causes some custom scripts (e.g. in init.d) to break. Please don't use it for the moment unless the ROM is specifically updated to use it. You are free to test it, but be sure to backup first. Please report if the ROM works, and if possible check if there are any init.d/sh scripts with static mtdblock# mounting too (see post #13 for details).
Info For ROM Devs: To make your ROM compatible with this, any scripts you have that (re)mount partitions need to be updated. Please see post #13 for details.
If you use a ROM and want to use this kernel but it doesn't work, feel free to let me know and I'll see if I can make a patch to update it in case the original ROM builder doesn't for some reason.
----------------
Unlocked Bootloader only obviously, don't ask about locked bootloader support. I don't take any credit for this kernel. This is a mod of Championswimmer's kCernel v01 (the new 'test' ones, which are the best kernel yet IMO), I only started a new thread incase this kernel has issues whereas champs' original one doesn't (you can report them here). Additional credits go to DoomLorD (got some code from his old kernel for FXP, i.e. DoomKernel v05) and of course J and the FXP Team.
Hope you guys don't mind Championswimmer and DooMLorD, you are Gods :highfive:
This kernel is made for CosmicUI ROM but it should work with any FXP-CM7 based ROM. If you are not using CosmicUI, be aware of these two warnings:
1) /system only has 190MB. If your ROM installation is bigger, you can't use this. You can check the size of system with apps like Titanium Backup and Link2SD.
2) /cache only has 8MB (it was 4MB but this ran out of space when doing stuff in Recovery) and as such you will need a 'bind-mount script for download cache' which links /cache/download to /data so that large Play Store downloads will work. All good FXP-based ROM's should already have it since it's been built in to Cyanogenmod for a long time. Check init.d for "06mountdl" file to be sure (might be different name, on CosmicUI it's 05mountdl for example).
Tested ROM's working with this kernel (please report if it works but not in the list):
- CM7-FXP125 and later
- CosmicUI v0.6.x and later
Changelog
Code:
Based directly on championswimmer's kCernel "test-release-v01" (the new one after v05)
v03
- Fixed gradual pixel shift bug in Aroma installer
- Changed handset max-gain to 600 (was 1000). I noticed no difference in volume, this also fixes distortion for some X10's
- Unlocked more mhz (1152, 1190, 1228). Be careful with the higher ones, though CM7/CosmicUI will revert to safe clock if it crashes.
- Compiled a second version with a different "safe" partition map for huge ROM's (system @ 285MB, userdata @ 608MB, cache @ 35MB)
- Optimized smartass governor for better sleep and wake (thanks to DooMLorD and FXP)
- Optimized smartassv2 governor for better sleep and wake (thanks to DooMLorD and FXP)
- Default governor changed to smartassv2 (bit more battery friendly than SavagedZen)
v02
- "kcernel" and "cosmicmod" appended to version string
- custom mtdparts config ( system @ 190MB, userdata @ 730MB, cache @ 8mb )
- compiled with O4 optimization
- (over)clock speeds added (up to 1113) and voltages tweaked (thanks to DooMLorD)
- improved in-call volume (thanks to DooMLorD)
- Default governor set to SavagedZen
- Compiled with performance governor available (useful for stress testing max clock)
v01
- Based on kCernel "test" v01
- Changed bootlogo to CosmicUI one with kCernel for FXP branding
- Removed Bootmanager (I don't use it) and replaced with Doom's Touch Recovery (more stable backup/restore than FXP Recovery)
Installation
1) Make a Nandroid backup (if you want to keep your ROM)
2) Flash the kernel in latest FlashTool
3) Boot to recovery and format cache, data and system
4) Restore Nandroid backup
5) Reboot. Let me know if you have any issues.
6) In my experience I've had to perform a Factory Reset and reinstall the ROM when switching from another kernel.
If you are not already using kCernel, you might need to do a factory reset - I don't know.
Requests
If you want some other partition layout or have any other suggestion please let me know and I'll think about it.
Download
v3 MaxMTD (/data = 730MB version) - recommended for CosmicUI
http://www.mediafire.com/?d4fenoosqeeryyk
v3 SafeMTD (/data = 608MB, /system = 285MB) - recommended for large ROM's
http://www.mediafire.com/?tuu7b07kptb32pb
Source
http://www.mediafire.com/download.php?nunrktw96q58eof
Detailed Info (for devs)
I am surprised how easy it was to create a custom partition map and I have no idea why nobody else has done this before. All I had to do was edit the default build config and edit the CONFIG_CMDLINE value:
Code:
CONFIG_CMDLINE="console=ttyMSM0 mtdparts=msm_nand:[email protected](boot),190m(system),730m(userdata),8m(cache),4m(appslog)"
...the other changes were taken from DoomKernel v05 in a basic tree-diff method.
Special thanks for Championswimmer and his guides, tips, kernels, etc. You are the best
Could you make a version without the volume boost mod? Because the boost mod causes my earpiece to crackle, and there's no ULBL kernel that doesn't have the volume boost mod.
Thanks a bunch
Sent from my X10i using XDA
Prodigy said:
Could you make a version without the volume boost mod? Because the boost mod causes my earpiece to crackle, and there's no ULBL kernel that doesn't have the volume boost mod.
Thanks a bunch
Sent from my X10i using XDA
Click to expand...
Click to collapse
I'm not sure I know what you mean. The "in-call volume enhance" in the changelog was taken from DoomKernel v05, it's not there in kCernel. So it's something different and I don't know where to find that. The change raises the minimum gain value, it doesn't actually "boost" volume but stops it from going too low.
I don't get any crackle on mine, I just tested it. Sounds like (no pun intended) your earpiece is damaged....
...I would be willing to do it, but I don't know where to look. Find me a kernel with public sourcecode without this volume boost for me and I'll check it out.
CosmicDan said:
I'm not sure I know what you mean. The "in-call volume enhance" in the changelog was taken from DoomKernel v05, it's not there in kCernel. So it's something different and I don't know where to find that. The change raises the minimum gain value, it doesn't actually "boost" volume but stops it from going too low.
I don't get any crackle on mine, I just tested it. Sounds like (no pun intended) your earpiece is damaged....
...I would be willing to do it, but I don't know where to look. Find me a kernel with public sourcecode without this volume boost for me and I'll check it out.
Click to expand...
Click to collapse
Hi,
The earpiece crackling started back on wolf's v7b6 doomkernel version, and it wasn't just me, a couple of users reported that their earpiece started crackling as a result of using wolf's rom. IDK what caused it, either a problem with the ROM or doomkernel, but DK seemed fine on any other ROM other than wolf's.
Anyway yeah the crackling was almost non-existent with stock kernels, which by the way, did not conyain the mod. Sorry for confusing you, this mod was incorporated in kernels back when kernel development just started. Tkygmr mentions that he forgot to include the volume boost mod here. That kernel is here. Yeah its for locked bl, I'm not sure if thay helps. But the kernels before that, many did not have the volume boost mod.
Hope this helps, and thanks for your time much appreciated.
Sent from my X10i using XDA
Prodigy said:
Hi,
The earpiece crackling started back on wolf's v7b6 doomkernel version, and it wasn't just me, a couple of users reported that their earpiece started crackling as a result of using wolf's rom. IDK what caused it, either a problem with the ROM or doomkernel, but DK seemed fine on any other ROM other than wolf's.
Anyway yeah the crackling was almost non-existent with stock kernels, which by the way, did not conyain the mod. Sorry for confusing you, this mod was incorporated in kernels back when kernel development just started. Tkygmr mentions that he forgot to include the volume boost mod here. That kernel is here. Yeah its for locked bl, I'm not sure if thay helps. But the kernels before that, many did not have the volume boost mod.
Hope this helps, and thanks for your time much appreciated.
Sent from my X10i using XDA
Click to expand...
Click to collapse
Hmm maybe it was xLoud that damaged the earpiece, who knows.
I checked out that post and crawled their GitHub, unfortunately they didn't use GitHub version management until a few months after adding the call-volume hack he mentions. So I won't be able to find it in that source =\
Guess the only thing to do is PM a veteran x10 kernel dev, but I'm not sure who. They all seem to have moved on since. If there is any other custom kernel (even for stock-based or locked bootloader) that you can find without any volume hacks, do let me know.
Although with the minimum-gain tweak I merged into this (which, as a mentioned, was from DoomKernel and not in original kCernel), I could compare the code from that to the stock kernel sources. But that will take a bit of time and I might not be able to find it, depends how much these custom kernels have changed from stock.
EDIT: Hang on, I just found an older repo from that thread "FreeKernel" (before it was 3Kernel). Maybe I'll find it.
EDIT2: Found it. https://github.com/tkymgr/semc-qsd8x50/commit/6c3c316b69ce7177cd08c73895406c94fd72db32 Yeah, I could have guessed that but now I'm sure so it's OK haha. If you look at that page you can see the ".min_gain = -900" which is what I changed to -400, but the max is changed here too.
OK, so the stock kernel (I think) has max set to 600, in this kernel, kCernel and DK though it's on 1000. I will create a version with 600.
This kernel is made for CosmicUI ROM but it should work with any FXP-CM7 based ROM. If you are not using CosmicUI, be aware of these two warnings:
1) /system only has 190MB. If your ROM installation is bigger, you can't use this. You can check the size of system with apps like Titanium Backup and Link2SD.
2) /cache only has 8MB (it was 4MB but this ran out of space when doing stuff in Recovery) and as such you will need a 'bind-mount script for download cache' which links /cache/download to /data so that large Play Store downloads will work. All good FXP-based ROM's should already have it since it's been built in to Cyanogenmod for a long time. Check init.d for "06mountdl" file to be sure (might be different name, on CosmicUI it's 05mountdl for example).
Tested ROM's working with this kernel (please report if it works but not in the list):
- FXP125 CM7 (official)
- CosmicUI v0.5.x and later
Changelog
Code:
Based directly on championswimmer's kCernel "test-release-v01" (the new one after v05)
- "kcernel" and "cosmicmod" appended to version string
- custom mtdparts config ( system @ 190MB, userdata @ 730MB, cache @ 8mb )
- compiled with O4 optimization
- (over)clock speeds added (up to 1113) and voltages tweaked (thanks to DooMLorD)
- improved in-call volume (thanks to DooMLorD)
- Default governor set to SavagedZen
- Compiled with performance governor available (useful for stress testing max clock)
Installation
1) Make a Nandroid backup (if you want to keep your ROM)
2) Flash the kernel in latest FlashTool
3) Boot to recovery and format cache, data and system
4) Restore Nandroid backup
5) Reboot. Let me know if you have any issues.
If you are not already using kCernel, you might need to do a factory reset - I don't know.
Requests
If you want some other partition layout or have any other suggestion please let me know and I'll think about it.
Hello,
That was a Good Idea of yours. Since many roms are quite a bit larger than 190MB; for instance the one I am using is taking up almost 250MB of system, could you make a version with say 285MB for system and 35MB for cache which would still leave about 609MB for data. And 1190MHz as many X10's will handle it. :good:
Prodigy, give this a try. I tested it and noticed no difference at all? Very strange.... either the max-gain 1000 does nothing (or barely anything) or I did something wrong. Please try it though, if it works this will be included in any future releases.
http://www.mediafire.com/download.php?p8pxnlv658y6bdf
EDIT: For some reason when I flashed this, some of my UI fonts (clock, operator text, some others) turned into italic. Wtf? I actually like it but that makes no sense LOL. Last night during testing, winamp would also skip tracks twice when i only pressed it once (a clear data for the app fixed that). I think a factory reset might be needed if things go strange after flashing a kernel.
TAL333 said:
Hello,
That was a Good Idea of yours. Since many roms are quite a bit larger than 190MB; for instance the one I am using is taking up almost 250MB of system, could you make a version with say 285MB for system and 35MB for cache which would still leave about 609MB for data. And 1190MHz as many X10's will handle it. :good:
Click to expand...
Click to collapse
OK, the clock speeds I can do. Would you prefer a version of 260MB on system? There really is no need whatsoever to have space free on /system, unless you want to integrate some apps with TB for example. But even if you have 249MB on /system, it work work fine with 1MB free on a 250MB size. So having ~10MB free on system should be enough?
Is there a reason you want 35MB on cache? There is no need to have more than 8MB, with the CM7 bind-mount script the only thing that uses cache is CWM-Recovery for log files. I guess some custom scripts might use cache... is that why?
CosmicDan said:
Prodigy, give this a try. I tested it and noticed no difference at all? Very strange.... either the max-gain 1000 does nothing (or barely anything) or I did something wrong. Please try it though, if it works this will be included in any future releases.
http://www.mediafire.com/download.php?p8pxnlv658y6bdf
EDIT: For some reason when I flashed this, some of my UI fonts (clock, operator text, some others) turned into italic. Wtf? I actually like it but that makes no sense LOL. Last night during testing, winamp would also skip tracks twice when i only pressed it once (a clear data for the app fixed that). I think a factory reset might be needed if things go strange after flashing a kernel.
OK, the clock speeds I can do. Would you prefer a version of 260MB on system? There really is no need whatsoever to have space free on /system, unless you want to integrate some apps with TB for example. But even if you have 249MB on /system, it work work fine with 1MB free on a 250MB size. So having ~10MB free on system should be enough?
Is there a reason you want 35MB on cache? There is no need to have more than 8MB, with the CM7 bind-mount script the only thing that uses cache is CWM-Recovery for log files. I guess some custom scripts might use cache... is that why?
Click to expand...
Click to collapse
The reason I thought 285MB would be good was that I remember the last CM7 by Achotjan I used was a big ass rom, around 270 installed as I recall and I'm sure its bigger now. Just in case someone wants to try this with a big rom. The cache suggestion was just for extra margin as the most I've seen used on my phone was a little under 6MB. Back in the day, when I built a 550HP Poncho motor, I made sure the bottom end was good for at least 700HP. Gotta have margin.
TAL333 said:
The reason I thought 285MB would be good was that I remember the last CM7 by Achotjan I used was a big ass rom, around 270 installed as I recall and I'm sure its bigger now. Just in case someone wants to try this with a big rom. The cache suggestion was just for extra margin as the most I've seen used on my phone was a little under 6MB. Back in the day, when I built a 550HP Poncho motor, I made sure the bottom end was good for at least 700HP. Gotta have margin.
Click to expand...
Click to collapse
OK, good call. I don't know why 35MB on cache will be needed with the download cache redirected to /data, but OK I'll do one with 285MB on system and 35MB on cache and that'll be marked as the "safest" mod. Then I might make one in-between if asks for it. But there will be a limit to how many I can maintain
Cheers mate thanks heaps for your effort, that was really quick!
Sent from my X10i using Tapatalk 2
Prodigy said:
Cheers mate thanks heaps for your effort, that was really quick!
Sent from my X10i using Tapatalk 2
Click to expand...
Click to collapse
No worries. Let me know if it helps though? Next version will keep it, as I already mentioned that my test showed that it was not quieter at all putting the gain back to 600.
Info for ROM makers
Code like this in any sh scripts (e.g. init.d, hw_config.sh, etc) will not work with this kernel...
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock2 /system;
...because it assumes a standard MTD map. This kernel has however modified the order. We could just change it to mtdblock1, but then that ROM would only work with this kernel. So, we use a function to parse the /dev/mtd file to find the correct mtd device to be mounted.
Add this helper function to the top of your script(s):
Code:
get_mtd() {
local DEV="$(grep "\"$1\"" /proc/mtd | awk -F: '{print $1}')"
local PATH=/dev/mtdblock
DEV="${DEV##mtd}"
echo "${DEV:+$PATH$DEV}"
}
...then later, when you need to assign the right mtdblock, do this...
Code:
mtd_system="$(get_mtd system)"
...changing 'system' to whatever you want to find. This will populate the variable with /dev/mtdblock1 in kCernel-CosmicMod, or in other kernels with /dev/mtdblock2. All good.
So then after that you can use it in a line like this...
Code:
mount -o rw,remount -t yaffs2 $mtd_system /system;
...and that's pretty much it.
...I realize that I could correct the kernel to use the "original" mtd map order, but this is a good habit for a developer to get in to. A developer should not tie themselves down with device-specific habits. Besides, my changes to the mtd order make more sense and other Android devices that I know of seem to follow this same order.
Hi,
First thanks for this Kernel, i've been looking for a partition table like this forever, and now can take it with the overclock as well, this is awesome, and based on your last comment a just figured out out most scripts doesn't seem to work on my init.d
Well as i'm not that good with Linux scripts, (to not say very bad in this area of expertise), can you help me to translate to a working script the script below:
mount -o noatime,nodiratime,barrior=1 -t ext3 /dev/block/mmcblk0p2 /sd-ext;
I understand that this also should be placed:
chown 1000:1000 /sd-ext;
chmod 771 /sd-ext;
#swap mount:
swapon /dev/block/mmcblk0p3;
My mSD card was formatted using the recovery built in and the mapping is correct as in this way the script is already working but i have to run them from inside script manager app and not from init.d, from init so far nothing seems to work, or it's just me that can't figure how to do it.
TheRuan said:
Hi,
First thanks for this Kernel, i've been looking for a partition table like this forever, and now can take it with the overclock as well, this is awesome, and based on your last comment a just figured out out most scripts doesn't seem to work on my init.d
Well as i'm not that good with Linux scripts, (to not say very bad in this area of expertise), can you help me to translate to a working script the script below:
mount -o noatime,nodiratime,barrior=1 -t ext3 /dev/block/mmcblk0p2 /sd-ext;
I understand that this also should be placed:
chown 1000:1000 /sd-ext;
chmod 771 /sd-ext;
#swap mount:
swapon /dev/block/mmcblk0p3;
My mSD card was formatted using the recovery built in and the mapping is correct as in this way the script is already working but i have to run them from inside script manager app and not from init.d, from init so far nothing seems to work, or it's just me that can't figure how to do it.
Click to expand...
Click to collapse
You are saying this script works with other kernels but not with this one? I don't understand why, the mmc blocks are untouched - only the MTD blocks (internal partitions) have a changed order in this kernel.
Try it with original kCernel, I don't know if it has swap support enabled.
CosmicDan said:
You are saying this script works with other kernels but not with this one? I don't understand why, the mmc blocks are untouched - only the MTD blocks (internal partitions) have a changed order in this kernel.
Try it with original kCernel, I don't know if it has swap support enabled.
Click to expand...
Click to collapse
No no, what i'm saying is that this doesn't work with the Kcernel, i couldn't try your modified one since i've been working a lot this week and didn't have the time to format the phone again, the weird thing is that as far as i know the fxp has a default script in which it should always search the sd-ext partition and mount it, not sure about the swap partition, but pretty sure it would mount it too, but so far everything indicates that nothing inside the init.d directory is running, since i've tried many variations i got from the web and none worked.
I'm using the last 125 FXP and the Kcernel test1.
Will try tonight to format the phone in the work, but can't promise anything since i've almost no tools here and also i'm very sick, shouldn't be working neither, hehehe, but I'm workaholic.
TheRuan said:
No no, what i'm saying is that this doesn't work with the Kcernel
Click to expand...
Click to collapse
Well you should probably ask in original kCernel thread or the thread for your ROM... what is the ROM you are using? I could take a look when I have time if you can't give me a logcat.
TheRuan said:
the weird thing is that as far as i know the fxp has a default script in which it should always search the sd-ext partition and mount it
Click to expand...
Click to collapse
No, it doesn't have any function to mount sd-ext. You have to use a third-party method to get sd-ext access such as A2SD scripts (can be buggy) or the Link2SD app (recommended, most stable and more powerful).
TheRuan said:
but so far everything indicates that nothing inside the init.d directory is running, since i've tried many variations i got from the web and none worked.
I'm using the last 125 FXP and the Kcernel test1.
Click to expand...
Click to collapse
Hmm all I can suggest is to reflash kernel with latest flashtool, factory reset, and reinstall the ROM. If no init.d scripts are running it must be a bad kernel flash, which happens fairly often with the X10.
I reflashed now with your kernel and FXP, and no, init.D isn't working, I think this error is on Kcernel or on last builds from FXP kernel, that, being the source for kcernel could be the reason for the errors, and also I'm pretty sure that no start script are running.
Also for some reason on your kernel i can't undervolt the phone anymore, this was available using Kcernel.
tried to flash original fxp 124 kernel, and i get wlods all the time, it wont boot into recovery, anyone has ideas how to fix?? i saw something about flashing the fxp 124 rom and kernel directly from flashtool but i cant find it cause i forgot the threads name, please help as quickly as possible, cause i was thinking of flashing that, i could boot into recovery and restore my fxp 125 rom that i had now..
TheRuan said:
I reflashed now with your kernel and FXP, and no, init.D isn't working, I think this error is on Kcernel or on last builds from FXP kernel, that, being the source for kcernel could be the reason for the errors, and also I'm pretty sure that no start script are running.
Also for some reason on your kernel i can't undervolt the phone anymore, this was available using Kcernel.
Click to expand...
Click to collapse
Well I don't know what to say, init.d executes fine for FXP kernel, kCernel original and this kCernel mod. I find it hard to believe that init.d isn't working at all, because then sysctl wouldn't even be running. It's more likely that it's crashing out because of something you added or changed. You'll need to logcat it.
And sorry, I was wrong - the 05mountsd script handles sd-ext mounting. But that never did anything in my experience, it depends on your configuration. Link2SD works 100% for me and it creates an init.d script when you first run it and select your sd-ext partition type.
I noticed the undervolt thing and it's the only thing holding me off releasing the next version, I think I need to enable that sysfs interface somewhere. Changing clock voltages is done at /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels - same as every other custom kernel for x10 that has it.
[email protected] said:
tried to flash original fxp 124 kernel, and i get wlods all the time, it wont boot into recovery, anyone has ideas how to fix?? i saw something about flashing the fxp 124 rom and kernel directly from flashtool but i cant find it cause i forgot the threads name, please help as quickly as possible, cause i was thinking of flashing that, i could boot into recovery and restore my fxp 125 rom that i had now..
Click to expand...
Click to collapse
Try flashing stock gingerbread FTF, and please take those questions to the Questions forum - this has nothing to do with this kernel.
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
What's new in 2.7.0.0:
-Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
-Allow sideloading from /tmp on encrypted devices
-Check for a crypto footer before asking for a password to prevent user confusion
-Additional checks for validity to auto generated backup names
-Text wrap in the console output
-Proper caps lock support in the keyboard
-Mouse support via USB OTG for devices with a broken digitizer
-Improve scanning of storage locations for OpenRecoveryScript
-Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions thanks to Samer Diab
-Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
-Update SuperSU to 1.93 and improve installation process
-Added selinux contexts restoration to fix permissions
-Load RTC offset on Qualcomm devices to fix the date/time in recovery
-USB Mass Storage fixes Add SELinux support checking
-Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
-Add 4.4 decrypt support
-Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
-Various SELinux fixes and bug fixes
Note: 2.7 marks the first time that we are dropping support for older devices. We are doing this because of the SELinux support needed to install 4.4 Kit Kat ROMs. The non-TWRP parts of the recovery image have to be built in at least a 4.1 tree and the kernel that is included in the recovery image has to support writing SELinux contexts. We don't own most of the devices that we support so we depend on outside testers and developers to help us update devices. In many cases we can't find someone readily. Come to #twrp on Freenode if you want to help bring your device up to date. You can tell right away if your device will support 4.4 ROMs in 2.7. Boot TWRP and press the console button (the square-ish button either in the bottom middle or upper right) to view the console output. If it doesn't say "Full SELinux support" in the console, then your device still needs some work. Help us help you.
What's new in 2.6.3.0:
Proper backup and restore of SELinux contexts (thanks to Tassadar)
Pull in some ROM information for backup name generation
Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
Add 1200x1920 theme (thanks to Tassadar)
A few other fixes and tweaks
What's new in 2.6.1.0:
Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
Initial support for f2fs file system formatting (Moto X)
Update SuperSU install for 4.3 ROMs
Fixed a permissions bug on files created during backup
Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
Ignore lost+found folder during backup and size calculations
Various other minor bug fixes and tweaks
Downloadhttp://techerrata.com/browse/twrp2/m8
Huge shoutouts go specifically to
@Flemmard @bigbiff @Dees_Troy
I learned how to properly deal with DTB from these guys....
Known Issues:
No known issues anymore
No exFAT support. Need kernel source to investigate. This is only temporary. FAT32 works perfectly fine.
Random segfaults when starting actions. i.e. flashing restoring, backing up. Just makes you redo what you were trying to do. Dees_troy deems this nearly impossible to trace.
hmm wondering if this will work for the ATT variant since the DTB is variant specific usually, at least thats how it was on the G2.
Just wondering about off mode charging. Is it ok? I know there were issues with 2.7 on the m7. I was just wondering are the same issues present in the m8?
Whenever I finish flashing a ROM the screen goes off immediately, doesn't give me the chance to reboot. Doesn't seem right?
nice one thanks i can backup to ext sd now
djkinetic said:
hmm wondering if this will work for the ATT variant since the DTB is variant specific usually, at least thats how it was on the G2.
Click to expand...
Click to collapse
im using it on ATT version just fine
Ghost said:
Just wondering about off mode charging. Is it ok? I know there were issues with 2.7 on the m7. I was just wondering are the same issues present in the m8?
Click to expand...
Click to collapse
off mode charging works just fine.
guywithdesire1992 said:
Whenever I finish flashing a ROM the screen goes off immediately, doesn't give me the chance to reboot. Doesn't seem right?
Click to expand...
Click to collapse
In the second post, it talks about this.
jmz said:
im using it on ATT version just fine
off mode charging works just fine.
In the second post, it talks about this.
Click to expand...
Click to collapse
Excellent just wanted to make sure as DTB can be kind of a pain, when it comes to different variants.
djkinetic said:
Excellent just wanted to make sure as DTB can be kind of a pain, when it comes to different variants.
Click to expand...
Click to collapse
From the experimenting that has been done all the GSM DTBs are compatible with each other. And all the CDMA DTBs are compatible with each other. But not between GSM and CDMA.
Well i just tried on my m8 att variant and i get stuck at the teamwin curtain screen go figure lol
djkinetic said:
Well i just tried on my m8 att variant and i get stuck at the teamwin curtain screen go figure lol
Click to expand...
Click to collapse
Thats very odd. I have the ATT variant and using this
Try 2 things for me. Reflash but do fastboot erase cache before doing it. Then if it still doesn't work see if you have ADB when at the splash
jmz said:
Thats very odd. I have the ATT variant and using this
Try 2 things for me. Reflash but do fastboot erase cache before doing it. Then if it still doesn't work see if you have ADB when at the splash
Click to expand...
Click to collapse
i did that and it didnt work, i do have working adb which is how i was able to get back in hboot/fastboot.
Ok i was able to fix the hang, deleted my twrp theme folder and twrp settings from the other 2.6.3.3 version of twrp.
djkinetic said:
i did that and it didnt work, i do have working adb which is how i was able to get back in hboot/fastboot.
Ok i was able to fix the hang, deleted my twrp theme folder and twrp settings from the other 2.6.3.3 version of twrp.
Click to expand...
Click to collapse
ah yeah. that will do it.
should this be supporting ext sd card for rom installations? when i browse to External SD, my rom.zip isn't seen, folder looks empty.
nugzo said:
should this be supporting ext sd card for rom installations? when i browse to External SD, my rom.zip isn't seen, folder looks empty.
Click to expand...
Click to collapse
Did you check internal sd it might of saved it there
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Jarheadflip said:
Did you check internal sd it might of saved it there
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
yes i know it on my internal, i had to put it there to install it. but i would like to have my rom install files on my external and save my internal space for apps etc.
nugzo said:
yes i know it on my internal, i had to put it there to install it. but i would like to have my rom install files on my external and save my internal space for apps etc.
Click to expand...
Click to collapse
Is your sdcard in exFAT format? If so check second post
Sent from my HTC One_M8 using Tapatalk
Finally some good recovery
jmz said:
Is your sdcard in exFAT format? If so check second post
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
I'll check. I formatted it with my phone, shouldn't that format it correctly?
Will this work with the Sprint version?