After playing around with kernels and roms, running numerous benchmarks... I found that my N7's write speed is 2-3Mb/s ; read 20-30Mb/s depending on kernels/roms/settings...
My question is, what is the average write speed for N7, i've read reviews where the write was 8Mb/s at least... is mine normal?
Setteled with paranoidandroid + franco kernel btw... all other kernels/rom make not much a difference as it is always in between 2-3Mb/s
I recently read that the 3G version got a better memory.
So which N7 version do you have?
(Or was it the 32GB version? Not sure about that atm..)
Sorry for not stating earlier, its a 16GB WiFi only version...
http://arstechnica.com/gadgets/2012/11/googles-nexus-7-gets-a-fresh-coat-of-paint-for-the-holidays/
So this article says that the 32GB version has a better flash memory built in.
I just benchmarked mine using the "A1 SD Benchmark" (using SlimBean 4.2.2 on N7 3G 32GB) and I got 44,13MB/s (Read) and 12,12MB/s (Write), so it's pretty fast^^
You might try another rom or just another tool for benchmarking, but it is proved that your version uses a slower flash storage.
Same here, you might be able to see my result in the list. I just saw yours... With A1 SD Bench mine is R:307.82MB/s W:2.26MB/s ... ridiculous isnt it? *headache*
Take a look here:
http://productforums.google.com/forum/#!topic/mobile/loqbCbKVMWE%5B1-25-false%5D
There seem to be some more people with the same problem.
Is your rom a fresh install or do you already use it for some time now?
Yep, i've seen that one too but there's quite some differences here. Mine is a fairly clean storage with about 10GB free, it would be about 12GB because i just transfered a movie earlier to test practical senario speeds. Fairly clean install too, just factory reset + wipe cache & dalvik + install rom & kernel, this was 12 hours ago...
Have repeated that process for about 6 times n tried many kernels... Maybe last resort will be wipe storage, reformat from TWRP and push the files thru usb? I'm not confident on this total wipe and reflash kernel & rom zips.
Will TWRP still be there after a full wipe? Can i just copy paste the kernel & rom zips from my lappy and install from TWRP?
---------------------------
Problem fixed by reseting and then flashing faux's 'reset kernel', now using faux's latest kernel. My first kernel was franco's and since then the 2MB/s problem surfaced even after reverting to full-factory and reflashing everything, but i always went franco first, then others. In my non expert opinion this reset kernel helped in my problem... Thanks!
Thats more like it
Completely normal.
Writing is always slower in flash memory. This is due to the fact that the data can't just be "written": the data must first be read out of an entire "eraseblock" (group of pages) region into the cache, and then the whole eraseblock is erased, the changed data is merged into the data in the cache, and finally, the contents of the cache corresponding to the entire eraseblock are written. Even though the basic page size is a little bit more than 2k, the eraseblocks can be quite large. I'm not sure of what it is for the Nexus 7 but in previous devices I've owned it was 128 kb. (64 basic pages)
In modern flash devices that support TRIM, it is possible that the controller has a pool of already-erased eraseblocks to work with; this is certainly better than the above case, but it doesn't change the fact that if you want to write a 2kb file, you will be actually writing perhaps 128k or 256k of data.
On top of this the eMMC controller is also doing "wear leveling" in the background - even more writing. Look up "write amplification" - it is a phenomenon which is specific to flash memory that has no analog in other media such as disk drives or RAM.
So, the results a given benchmark will report depend on whether the writes are contiguous, and also their size. Androbench reports only ~ 0.2 to 0.3 MB/sec for random small writes, but substantially higher for contiguous writes. But even when the benchmark write size is the same size as the eraseblock group, writing is still going to be slower in flash memory than reading.
I'm skeptical that your kernel switching did anything other than elicit a quirk in a particular benchmark.
cheers
Hmm i'm aware that writing is slower than reading in most media, block sizes and intelligent data writes, quantum tunneling effects whatnot... but for it to be that slow was puzzling, plus the performance hit can be felt when compared to open box since i just the N7 about a month ago, there were microstutters when running games, video, even when playing music or doing anything... not sure how to put it but it wasnt 'butterly smooth' & felt like it was on a kind of powersafe governer, even after a full warranty purpose stock restore... My college gives out N7for it's students so i could compare between & mine was definitely off.
About TRIM i have used LagFree to TRIM the SD/Partitions in the kernels i used, i do know that since my first root and flash i was stuck at 2MB/s +/- write in AnTuTu, even today after discovering A1 SD Bench, it also reported a figure 2-3MB/s with franco & leankernel. Only after this 'reset kernel' and reflash it shot up to >10MB/s... will continue testing with a reflash again later n report if it regressed, but let me enjoy the speed i was deprived for the time being =D
I'm no expert in android/unix/linux so i will never conclude that the kernel was the cause, but the case is this reset and reflash helped after a week of shooting around kernels and roms... definitely luck too.lol. N thank you for the information on the bench apps! Hope this is just a one-off thing... Cheers :highfive:
Ok, i hate keeping things hanging so i took the jump...this time the right way with stock clockspeed kernels
Just wiped cache & dalvik > flashed franco r48 > wipe again> 1st boot, restart to 2nd boot > antutu bench > a1 sd bench w/ longer-test option on
poor write speeds
Then, wipe cache & dalvik > flash straight to faux enhanced stock > wipe again > 1st boot, to 2nd boot > antutu > a1 sd bench w/ long test on
poor write speeds
Next, wipe > flash 'stock/reset kernel' > wipe > boot once with reset kernel
Re-wipe > now flash faux enchanced stock >wipe > antutu > a1 sd bench w/long test on... wallah
600% increase in write speeds?
Idk what else i can deduce here except franco has poor disk performance n somehow affected following kernels till the 'reset kernel'...
Since i always went franco first (r47/48) even after a full stock restore, it explains why all the other kernels after the franco kernel were affected...
Anyone able to reproduce this? If so, can someone kindly inform franco since i'm new and unable to post in dev-related forums?
Yes i know general performance franco is higher but i feel 'butter smooth' on faux after the reset and totally no microstutter.
Not trying to create a war here but just saying that for a person like me, copying HD movies to my N7 for viewing on a daily basis i will need the faster write speeds or it'll take hours...perhaps take this as a bench/guide too to recover from the issue if it affects anyone
Related
This is a quick walkthrough of how to apply my variant of "Mimicans speedfix" using my kernels on the Captivate. The speedfix essentially consists of making an ext3 or ext4 filesystem on an sdcard, and using that as our /data directory. This method is different from the original method in many of the details, but the underlying basis is that the stock /data partition is slow as molasses so we replace it.
This method should be pretty safe. As you will notice we dont copy around stuff and create a symlink mess. We just mount a partition over the current one. Yes we still mount the old one as well, even though it wont be used unless you take your card out. If that happens the phone will mount your old /data (that will probably be very out of date at the time) but itll get you up and running right away.
Right now there are two kernels, these mount the default partition, ext3 or ext4 on the second sdcard partition, the two options are:
Stock clock speed and Overclocked.
The overclocked kernel will clock from 100 to 800 Mhz as stock, then skippinig 1Ghz going to 1.2 Ghz.
Also, before we begin make sure you have this version of Odin. I used Samsung windows drivers that I found here.
You'll also want to read this thread about download mode. here you'll learn that you will have to try real hard to actually brick these phones, and even then it may still boot.
Ofcourse you also want to have root on your captivate.
You'll also need the android sdk.
If you are on Windows or Mac you will need some software to partition and format the sdcard, this live cd will work. You could also just get an ubuntu live cd or similar.
So, now we have the necessary tools and our new kernels and can get started.
Partition the disk:
There were reports from the modaco forums when mimocan first released his fix that ext3/4 partitions larger than 2gb were a problem, so keep your 2nd partition 2gb or smaller.
Use your favorite partitioning sofware to create 2 partitions on your sdcard. the first one will be formated FAT32 (vfat), and the second one ext3 or ext4. Make sure both are 'primary partitions'. You may want to make the second partition have partition type 83 (linux native).
Copy data files to sdcard:
If you are coming from stock, (eg without an existing a2sd /data partition on your sdcard) boot the phone without your formatted card and hotplug it before starting this process.
Using the sdk you need to connect the phone and use 'adb shell' to get a prompt on the phone.
Then follow these steps:
Code:
$
$ su -
# mkdir /sdcard/mnt
# mount -t ext4 /dev/block/mmcblk1p2 /sdcard/mnt
# busybox cp -a /data/* /sdcard/mnt
# umount /sdcard/mnt
# exit
$ exit
Flashing the kernel
1) Disconnect USB cable.
2) Open up odin.
3) Put your phone into download mode.
4) Connect USB cable, wait a second Odin should detect your phone, if not fiddle about with your drivers and reboot windows or something. This can be a real PITA.
5) In Odin load the kernel tarfile as "CSC"
6) Click "Start" in Odin, flashing should only take a few seconds.
You may run into issues here randomly and have a phone with the phone-!-computer image (I did!). Just go read up on the 'download mode' thread linked above it tells you how to proceed.
7) When you have booted your new kernel and /data partition you may have some issues with a few widgets/apps. Reinstalling or waiting/fiddeling with them seems to solve the issue. Maps was slow to open the first time after a new /data partition was mounted for me a few times, but subsequent launches were snappy.
If you want you may donate to my beer fund. It is not necessary but much appreciated
Didn't work for me. I partitioned my external SD card, flashed the speedup2 kernel, then ran the commands you posted, replacing 'ext3' with 'ext4'. My quadrant score is still in the low 900's.
Can you explain exactly what those commands do? The mimocan fix makes a lot more sense to me. Why did you decide to take a different approach?
Thanks for your help and effort!
I get 1716 scores in quadrant, but with real world running tests Touchdown and Dolphin HD browser still lag like holy hell.
I originally had the "method 2" hack (moving apps to the NAND) and that worked wonders, especially with these apps.
Can anyone test these two applications and see if there is lag for you?
Dolphin - try opening a new tab, closing it, and goto a large page and scroll with the volume buttons - it should all be smooth and quick
Touchdown - It should be very quick going between emails, I get a 5+ second delay before showing the email
Also in Quadrant, even though I get 1700 scores, do you guys get stuck at I/O Database writes for a good 3+ minutes?
The captivate speedup kernel link is dead. Can soneone please post a mirror? Thanks
Worked great for me using ext4 partition/kernel. It brought my quadrant to 1817! Thats with a poor little 4gig, class 2 micro sd card. Im also running the i9000 JM2 firmware with Samset 1.6.
Thank you for all your hard work!!!! My phone is now complete (for now lol).
andy2na said:
I get 1716 scores in quadrant, but with real world running tests Touchdown and Dolphin HD browser still lag like holy hell.
I originally had the "method 2" hack (moving apps to the NAND) and that worked wonders, especially with these apps.
Can anyone test these two applications and see if there is lag for you?
Dolphin - try opening a new tab, closing it, and goto a large page and scroll with the volume buttons - it should all be smooth and quick
Touchdown - It should be very quick going between emails, I get a 5+ second delay before showing the email
Also in Quadrant, even though I get 1700 scores, do you guys get stuck at I/O Database writes for a good 3+ minutes?
Click to expand...
Click to collapse
Might be tome for you to pick up a new SD card. I have used both fix's and find this fix to be way better. I get no lag in Dolphin HD.
_Opiate_ said:
Might be tome for you to pick up a new SD card. I have used both fix's and find this fix to be way better. I get no lag in Dolphin HD.
Click to expand...
Click to collapse
Its a brand new Kingston 8gb class 4 card, havent used it before applying this hack
Postal76 said:
Didn't work for me. I partitioned my external SD card, flashed the speedup2 kernel, then ran the commands you posted, replacing 'ext3' with 'ext4'. My quadrant score is still in the low 900's.
Can you explain exactly what those commands do? The mimocan fix makes a lot more sense to me. Why did you decide to take a different approach?
Thanks for your help and effort!
Click to expand...
Click to collapse
All you do is copy the files from your original /data partition onto the root of your ext{3|4} partition on the sdcard. Then that is mounted on reboot ontop of /data so you can use the new data partition from your card.
I feel this is a MUCH cleaner method than the original Mimocan fix, that copis a full copy of data into the root of the device (unnecessary backup since you still have your original /data partition as well), then it mounts your sdcard on /disk and symlinks that to /data.
I just don't see the need for the symlinks and stuff and honestly I thought this was a simpler method, no symlinks or anything.
If you arent seeing any speedups I'm betting something didn't go right, you are probably still running of the old /data partition. Are you sure you are running the speedup2 kernel and not the ext4 only kernel?
spyz88 said:
The captivate speedup kernel link is dead. Can soneone please post a mirror? Thanks
Click to expand...
Click to collapse
It seems to work from here...
_Opiate_ said:
Might be tome for you to pick up a new SD card. I have used both fix's and find this fix to be way better. I get no lag in Dolphin HD.
Click to expand...
Click to collapse
Except the Quadrant scores do you notice any real speed boost?
andy2na said:
.....
Also in Quadrant, even though I get 1700 scores, do you guys get stuck at I/O Database writes for a good 3+ minutes?
Click to expand...
Click to collapse
yeah database I/O takes forever still.
Like I said in the other thread, try to reinstall the apps, Dolphin is very very fast here (thanks for getting me a new browser btw.)
I'm still a complete failure and now i get stuck at the galaxy s boot screen
Nuke, after doing the ext4 only method, I only get quadrant scores of 900.
Am I doing something wrong? I go through all the steps fine and everything seems like it went well but it seems like I'm doing something wrong down the line.
one thing I do notice is that I have A LOT MORE AVAILABLE MEMORY in advanced task killer. I use to only have 100 now I have 180MB.
Is it crucial to have to flash the Speedfix2?
after i put in
busybox cp -a /data/*
nothing happens it just sits there
igm503 said:
after i put in
busybox cp -a /data/*
nothing happens it just sits there
Click to expand...
Click to collapse
that part took like 15 min for me since I have a lot of application and app data
but there is no trailing dot it just repeats what i typed and then leaves a blank space
same thing it just repeats it
igm503 said:
but there is no trailing dot it just repeats what i typed and then leaves a blank space
Click to expand...
Click to collapse
What do you mean by "there is no trailing dot" ? Did you type it in? You need to include the trailing dot in your command; based on what you posted it appears you did not do that.
WOW! Okay... So now I'm getting 1756...
You just have to leave Quadrant on for like 15 minutes sometimes! This is very strange!
Notice the period after the asterisk. In the old forum, someone had a problem with that.
I did this fix last night after countless times of my messing up and figuring out how to partition with my phone still being able to read the card, flash problems with Odin, etc etc. I'm using an 8gb Classic 6 and just got an 1805 in Quadrant, and the phone is incredibly, noticeably faster. Did have some weird app problems when it was first applied, but some reinstalls fixed it. Thanks again Nuka!
Sent from my SAMSUNG-SGH-I897 using XDA App
Im using pzafroyo 2.2 that comes with data2sd. When I installed charge offline zip, it made the data2sd not work and when I rebooted it I had the rom back to fresh install. After recovering system everything went back to normal again, I dont get it. Isnt the image file in xrecovery folder all thats needed? it wasnt missing after the charge offline install. Also, even tho I was getting 2500+ benchmark w/data2sd I went ahead and ran it without it working and only got 1300 but the phone feels way faster and smoother, with data2sd (8gb class4) I was getting lags everywhere so its not worth it unless Im doing something wrong? I also noticed theres 2 charge offline files floating around, Im using the one labeled "proper fix", maybe that hindered the data2sd operation.
The offline charge fix should be implemented in all custom ROMs already so there was no reason to install it and that likely caused your problems. Data2SD isn't going to do anything but improve your quadrant score and cause lag especially with only a class 4 card.
Sent From My *Super Fly X10*
If I (or anyone for that matter!) help you, dont be afraid to press THANKS!
First of all I would like to give credit where credit is due and say thank you to SamHaLeKe for all the work he put into this port and all the other Developers involved to bring ICS to the SGS
If you would like a full run down of this ROM and what is included as any new developments, please visit the ROM thread
Now off to the good bits ...
Install
I AM NOT RESPONSIBLE IF SOMETHING GOES WRONG AND YOUR PHONE CEASES TO WORK. THIS IS NOT A DETAILED WALK THROUGH BY ANY MEANS. I AM ASSUMING YOU READ ONE OF THE MANY OTHER TELUS THREADS THAT HAVE THE FULL INSTRUCTIONS INCLUDED TO PERFORM THE BELOW STEPS.
Note: I am not going to post all the links to files as I do not have the time to update them everyday when something changes. I will however post links to the ROM and Kernel threads for your reference.
I decided to start fresh (and I mean fresh) from stock FROYO with a full SD format and the works.
Step 1
Flashed back to stock with ODIN. Again I used FROYO but I am sure GB would work. If you want to start fresh as I did, go to options storage and format the internal SD (13 GB).
Step 2
Download the ROM and Glitch V13 kernel (what I used) and copy them to the SD card of the phone. I suggest removing any external SD as not to copy the files to the wrong spot (guess what I did LOL).
Step 3
Flash voodoo kernel from ODIN to root and install clockwork recovery making sure that you do not repartition in ODIN
Step 4 - Note: The older voodoo kernel gave an "assert failed" error trying to flash the ROM through recovery)
Boot into recovery and wipe cache and dalvik then flash the Glitch V13 kernel from zip and reboot. At this point you will most likely be boot looping but no worries everything is OK
Step 4
Pull the battery and then boot into recovery with volume up + volume down +power. Wipe cache and dalvik and flash the ROM from the ZIP
Let the ROM boot and then again boot to recovery and flash the essentials zip.
Voila you should be running S.U.R.F.A.C.E ICS, aint it beautiful?
I continued and flashed add on packs 1 and 2 but that is up to you
Now for my findings thus far ...
I am in no way a power user when it comes to my phone but I do play with it a lot. I have to say that this ROM seems to be the one of the smoothest to date and seems to take to our device nicely.
Battery has been nothing short of great for me. Through the week I can easily get 2 days out of it (work all day). Now I also try to minimize the drain by turning off whatever I don't need like WIFI seeing as there is none where I work.
I flashed the JL3 modem and it seems to work good for me but then I don't live where you do so you may have better luck with another.
The kernel included in the ROM (if you read the ROM post) is Glitch V14 pre which runs amazing as usual although still in the development stage. This kernel has a lot of new features that I will let you read up on yourself here
The ROM also includes supercharger and thunderbolt scripts (I admit I have little to no experience with these but I do know they help).
No FC's with this ROM other then the video camera but I have seen some posts regarding this and have not got around to working on it but will be I am sure very soon. It looks like just a file update maybe but too soon to tell.
Live overclock seems to work if I leave the voltage settings alone but that could just be a lack of experience in this area but it never hurts to try. If anyone has settings that are working for them I would love to know what they are. I have set the live overclock to 120% or 1.2ghz and it runs fine again if I do not change the voltage.
It's only been about 3 days since the install but this is what I got so far. I would recommend giving it a try for sure.
I know there are a few of us on this ROM so post up your findings here.
Thank you
Buck
Similar but running Glitch v14
Thanks for the write up Buck. I have been running this rom (Surface) for a few days also but I came from cm7 to this one. I have also been toying around with it over the last few days which has gotten me in a few tight spots lol. I have my Volt control set to 1304, no voltage changes and it runs flawlessly. The modem I put on was the JVT which also seems to work well.
What I have learn about Live OC:
First you set your clock speed in Volt control, then flip over to NStools (that is the easy part)
IMPORTANT.... If you choose to mess with this, make sure settings in NStools is NOT set to apply on boot or make sure you have a good recovery to go back to. Found this out the hard way
Click on live oc and you can make changes here... If you read the articale from Glitch on this it will help alot (found in the OP for T959D).
Live oc clocks up the cpu AND bus so it affects the gpu and memory along with the cpu (very important).
Findings... some settings work fine, 105, 106,110, 114, 116. 115 seems to have issues and provides lower performance considerably lower.
I use AnTuTu to check how things are working. That being said, if you apply set at boot and you hit a setting that first craps out the phone, causes a reboot then your going to be in a bootloop or it will start reboot start reboot. This is why you DON'T do this or like I said earlier have a good recovery handy.
Right now I am only running 1304 and 100% and everything is fine except the prior mentioned FC on video cam. Oh I should mention also I am running the Lazy governor atm which also seems to work fine (default is on demand).
Anyways
Well I think we may have broken the record for the longest 2 posts on the first page in xda history lol. Happy flash year everyone
Sent from my GT-I9000 using XDA App
Didn't notice you guys mention this, but Glitch V14 has an option in CWM to clear NSTools settings. It's right above the option to clear voltage settings under the Glitch Menu.
It works well, believe me!!
-Maniac
I'm on ICS!
Thanks bucky!!
I'm on ICS now, with Glitch v14 but I have a few questions I'm hoping you can help with:
- The screen layout / icons seem shrunken to me? As well as the notification bar. General text and keyboards are fine. Is there a fix I can apply?
- With further versions from Surface can I just flash over top of what I'm on now or do I need to go back to stock?
- Do I need to use TI to bring all my apps back up (I get "App X has stopped working"), or is there a quicker way?
Thanks again.
baino said:
Thanks bucky!!
I'm on ICS now, with Glitch v14 but I have a few questions I'm hoping you can help with:
- The screen layout / icons seem shrunken to me? As well as the notification bar. General text and keyboards are fine. Is there a fix I can apply?
- With further versions from Surface can I just flash over top of what I'm on now or do I need to go back to stock?
- Do I need to use TI to bring all my apps back up (I get "App X has stopped working"), or is there a quicker way?
Thanks again.
Click to expand...
Click to collapse
Well the shrunken icons are because of the DPI setting in the build.prop file. You can change it with a text editor (I use root explorer) to the default value of 240. It is listed as LCD Density.
To flash another version you should be fine to flash over what you have with a factory reset and wipe cache
Apps well I usually just re-download from the market. I have used TI and found I get the best result if I restore without data. Remember not all apps are compatible with ICS yet so that could cause issues as well.
Enjoy the ICS I know I do.
bucknetbucky said:
Well the shrunken icons are because of the DPI setting in the build.prop file. You can change it with a text editor (I use root explorer) to the default value of 240. It is listed as LCD Density.
To flash another version you should be fine to flash over what you have with a factory reset and wipe cache
Apps well I usually just re-download from the market. I have used TI and found I get the best result if I restore without data. Remember not all apps are compatible with ICS yet so that could cause issues as well.
Enjoy the ICS I know I do.
Click to expand...
Click to collapse
Hey Guys,
Why not just use rom toolbox? the build.prop tweaks give ya a niffty slider... no hackin involved...
Anyone got the files for stock GB?
cowvun said:
Anyone got the files for stock GB?
Click to expand...
Click to collapse
you looking for T959D?
Yes
Sent from my T959D on Darky's Rom 10.3.
Rom toolbox worked for me, it's looking beauty now. Everything seems to be working well, except I get the occasional crash on dialer / contacts. Anyone else having the same?
I'm running LauncherPro, what are you guys running?
baino said:
Rom toolbox worked for me, it's looking beauty now. Everything seems to be working well, except I get the occasional crash on dialer / contacts. Anyone else having the same?
I'm running LauncherPro, what are you guys running?
Click to expand...
Click to collapse
Nothing like that here maybe the way it was flashed I am not sure. Have you added anything?
Sent from my GT-I9000 using XDA App
Only flashed the add-ons, and the launcher pack. Changed the LCD density and that's about it. I'm thinking it might be because I didn't wipe the sd card and start clean.
baino said:
Only flashed the add-ons, and the launcher pack. Changed the LCD density and that's about it. I'm thinking it might be because I didn't wipe the sd card and start clean.
Click to expand...
Click to collapse
Depends what you did before flashing. I had issues after flashing a lot and never deleting anything lol
Sent from my GT-I9000 using XDA App
Working NSTools values for OC and UV
CPU:
Governor = Lazy
Min CPU = 100 (109 after live OC)
Max CPU = 1200 (1308 after live OC)
OC Value = 109%
Deep Idle = On
Custom Voltage
Arm:
1400 = unchanged
1304 = 1375
1200 = 1325
1000 = 1225
800 = 1150
400 = 975
200 = 875
100 = 875
Int Voltage
1400 = Unchanged
1304 = 1150
1200 = 1125
1000 = 1075
800 = 1050
400 = 1025
200 = 1025
100 = 925
Just set these values tonight and so far all is good and no crashes or reboots. See if it helps the battery as the days go by. Give it a shot or post your working values for others to try.
AND NO I NEVER SLEEP
bucknetbucky said:
Working NSTools values for OC and UV
Click to expand...
Click to collapse
Thanks for posting your OC and UV values. I'll give those a try.
I've been experiencing random crashes and reboots (woke up this morning to a dead phone). It was plugged in overnight but crashed at some point and did not charge. Battery voltage dropped down to almost nothing.
Anyone else experiencing random reboots?
I was using an OC value of 1304 (no live OC). UV values left stock. Ondemand governor, Deep idle ON, noop IO scheduler.
I did not format my sdcard prior to install. Just did a data wipe/factory reset, format cache and dalvik then installed according to the instructions. Installed Add-on Essentials and Add-on Pack One. All other apps were reinstalled from the market (after using market enabler and changing DPI back to 240 using ROM manager).
Everything works great except for the random crashes and reboots. I'll probably start from scratch again when v1.3 comes out (except I will format the SD card). Maybe even start from stock Froyo as recommended in the OP.
EDIT:
Tried the settings and my phone was not happy. It froze when setting the UV values. My phone seems to have a problem with any live OC value other than 100%. As soon as I increase it I lose all stability.
1.3 released and I am running it.
Sent from my GT-I9000 using XDA App
Settings
I'm on Glitch v14 pre5 and I just clocked it up to 1300 and added 104% live OC for a stable 1352, no undervolting battery sitting @ 68% 1 day 22hrs. I did turn off some stuff I dont use and had data running on and off for the whole time.
For the guys that are having problems with flashes, I generally wipe everything I know its a pain but I don't experience any problems either. I also wait until i have a full battery too. It seems to pay off in the long run...
Happy Flashing!!!
Phone and contacts are working well now, but I can't get app data to save. For example some apps t's&c's keep asking for approval everytime I open the app. Also beautiful widgets skins keep reverting back to default. I'm going to wipe, format the SD card and install 1.3 from stock Froyo. here's hoping.
bucknetbucky said:
1.3 released and I am running it.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Just wiped and running 1.3 now. So far seems much better and faster than my last flash. You guys know of any way to change the haptic feedback intensity in ics?
XENON Kernel​
For ICS [any ROM]​
Features:
Code:
*Overclocked CPU to 1.5ghz
*SWAP Space Enabled
*ath6kl WiFi driver from compat-wireless
*Memory Compaction
*Adaptive Voltage Scaling
*Memory Management based on Device State
*NWFPE Floating Point Emulation
*Support for Extended Precision
*Integrated Services Digital Network (ISDN) Support
*Watchdog Timer Corrective Services Support
*Direct Memory Access (DMA) Support
*Maintain devtmpfs filesystem to mount at /dev
*Automount devtmpfs at /dev
*Detect Soft Lockups
*Detect Hung Tasks
*Kernel Memory Leak Detector
*Checks for Stalled CPUs
*Sysctl Checks
*Securityfs Filesystem Support
*Reiserfs Filesystem Support
*JFS Filesystem Support
*XFS Filesystem Support
*GFS2 Filesystem Support
*OCFS2 Filesystem Support
*Advanced Partition Selection
*Acorn Partition Support
*Cumana Partition Support
*EESOX Partition Support
*ICS Partition Support
*Native Partition Support
*PowerTec Partition Support
*RISCiX Partition Support
*Alpha OSF Partition Support
*Macintosh Partition Map Support
*PC BIOS (MSDOS Partition Tables) Support
*BSD Disklabel (FreeBSD Partition Tables) Support
*Minix Subpartition Support
*Solaris (x86) Partition Table Support
*Unixware Slices Support
*Windows Logical Disk Manager (Dynamic Disk) Support
*SGI Partition Support
*Ultrix Partition Support
*Sun Partition Tables Support
*Karma Partition Support
*EFI GUID Partition Support
*SYSV68 Partition Table Support
The Xenon Kernel is a project for myself to learn more about Linux and Android Kernel developing. I am a sophmore in High School and I haven't had much developing experience, so this is a learning experience. If you want to use this Kernel, you can show your support by thanking me! Right now all I need is words of encouragement and a new phone (I still have an old Symbian S60v3 phone haha). The Touchpad is my first Android device. Also, this is my second work for the Touchpad, my first is the SUPREME Modpack. I hope to make this my primary development project and improve as much as I can. Thanks for checking this out!
Download:
http://goo.im/devs/rohan/tenderloin/XENON
There are 2 versions, one that retains the CM9 kernel as a backup, and one that deletes the CM9 kernel and only uses Xenon.
Saves CM9: xenon-kernel-v1.1-tenderloin-rohan-WITHCM9.zip
Deletes CM9: xenon-kernel-v1.1-tenderloin-rohan-WITHOUTCM9.zip
Current version is v1.1
Click to expand...
Click to collapse
Instructions:
How to Install:
FIRST, MAKE A NANDROID BACKUP! This can cause serious harm to your system. I am not responsible for anything that may occur to your Touchpad, but everything should be fine.
1. Download the respective installer zip from the above link.
2. Install the zip in ClockWorkMod.
3. Wipe your dalvik-cache
4. Reboot and hope for the best!
IF YOU ARE HAVING SOD ISSUES try setting your CPU Governor to "ondemand"
How to Uninstall:
1. Restore from your backup you were supposed to make
or... if you didn't listen (shame on you... you should always make a backup)
1. Download the XENON Uninstaller from my goo-inside.me profile. This zip deletes the Xenon Kernel and adds back the default CyanogenMod 9 Kernel. It will not, however, delete the ath6kl WiFi drivers (you really don't need to unless you are having WiFi woes). To uninstall the ath6kl drivers you need to reinstall Android.
2. Install it in ClockWorkMod.
3. Wipe your dalvik-cache
4. Reboot!
Contact:
Contact me via Twitter (preferred) here: http://twitter.com/rohanXm
Or PM me
Credits:
*jcsullins for originally getting me interested in kernel development, aiding me through the process in IRC, creating moboot, and helping out the CM9 team in this port
*lintz (helped with getting the ath6kl drivers working and solving my ignorance )
*The ENTIRE CM9 team (dalingrin, verygreen/green, Dees_Troy, Flemmard, and everyone else who has contributed to this port. It is truly an honor to witness what you guys have created.
Changelog:
4/03: Version 1.1
Code:
*Removed the support for the following partitions:
-Amiga Partitions
-Atari Partitions
*Bumped CPU Minimum up to 384mhz to combat against SOD issues
*Battery drain should now be significantly lower than before
Thanks for sharing! Will give this go and provide feedback.
Very cool, I love kernel options! You rock. Now I'm jealous that you have time to develop on a kernel. Been wanting to try that side of the house, just no time.
Sent from my android touchpad.
Don't have the time now, but I will try it and get back to you.
Thank you so much for working on this! Always glad to see more Touchpad love.
works good for me,but the new wifi driver is sucks,got authentication problem ,and then disconnect every one minute,but thanks and good luck
Can you add gpu oc in next build please
evanbigfan said:
works good for me,but the new wifi driver is sucks,got authentication problem ,and then disconnect every one minute,but thanks and good luck
Click to expand...
Click to collapse
Hmmm, I had issues with the nightly build WiFi. Using this kernel fixed that. I haven't been disconnected at all. It did seem to want to connect to my neighbor's WiFi at one point. I've never connected to it before or saved the settings, but during the ICS setup, it kept repeating "Obtaining IP address" until I tapped it and hit Forget, then connected to mine. Everything has been fine since then.
Will this affect the supreme mod script in any way? I have the latest mod pack for the 4.0.4 build for official nightly. Will I need to reflash and run terminal again for mod pack after flashing this kernel?
Thanks
SUTHRNFRIED said:
Will this affect the supreme mod script in any way? I have the latest mod pack for the 4.0.4 build for official nightly. Will I need to reflash and run terminal again for mod pack after flashing this kernel?
Thanks
Click to expand...
Click to collapse
Nope, it will not affect that at all. So no need to worry about reflashing.
And just a side note, for those of you experiencing sleep of deaths, try setting your CPU minimum to 384mhz using a CPU control app. I will make this the default minimum in the next release.
sahhar1993 said:
Can you add gpu oc in next build please
Click to expand...
Click to collapse
That's definitely high on the new features list. I hope to have another release out soon with bug fixes and probably this if I can figure out how to do it.
This is really nice but I'm wondering what all of this filesystem support will do? Don't get me wrong, any work on the TP is good work, I'm just wondering the utility of having "Amiga Partition Support" when the Amiga is 20-30 years old haha?
cajunflavoredbob said:
Hmmm, I had issues with the nightly build WiFi. Using this kernel fixed that. I haven't been disconnected at all. It did seem to want to connect to my neighbor's WiFi at one point. I've never connected to it before or saved the settings, but during the ICS setup, it kept repeating "Obtaining IP address" until I tapped it and hit Forget, then connected to mine. Everything has been fine since then.
Click to expand...
Click to collapse
It seems some devices suit best with the old driver,and some are best with the new one,for me the new driver is killing my wifi
Sent from my Desire HD using xda premium
Smith7018 said:
This is really nice but I'm wondering what all of this filesystem support will do? Don't get me wrong, any work on the TP is good work, I'm just wondering the utility of having "Amiga Partition Support" when the Amiga is 20-30 years old haha?
Click to expand...
Click to collapse
I dont know I decided to just throw it in there haha. I'll probably remove support for some of them that are crazy.
Are any of you guys having any bugs? For myself personally I'm actually getting a lot of SODs and battery drain. Are you guys experiencing the same thing or is it just my funky Touchpad?
Not really any out of the ordinary battery drain with new kernel vs stock. I has noticed using a screen off profile and setting it to power save with 384 or 432 values that the TP has issues waking back up. So I just use interactive at 384 min and that works just fine.
Edit: I have no screen off profiles enabled. Interactive is set as main.
New release v1.1 with bug fixes now! Just download and install the new CWM file.
Changelog:
Code:
*Removed the support for the following partitions:
-Amiga Partitions
-Atari Partitions
*Bumped CPU Minimum up to 384mhz to combat against SOD issues
*Battery drain should now be significantly lower than before
Doesn't work on my TP
Followed instructions from OP.
After reboot, my TP showed "XEON" as one of the boot option. I selected that. My TP displays "Wrong file size" and did not boot.
Not sure what happened.
sprice26 said:
Followed instructions from OP.
After reboot, my TP showed "XEON" as one of the boot option. I selected that. My TP displays "Wrong file size" and did not boot.
Not sure what happened.
Click to expand...
Click to collapse
Your /boot partition is too full
What other kernels do you have installed?
Even setting 384 as minimum I still receive SOD with 1.0. I'll try 1.1 and see if things improve.
SUTHRNFRIED said:
Even setting 384 as minimum I still receive SOD with 1.0. I'll try 1.1 and see if things improve.
Click to expand...
Click to collapse
Yeah try out 1.1
I was getting SODs on 1.0 and the SODs were everywhere. 1.1 fixed this for me.
For Mods : this is my first post, forgive me if I am doing something wrong by posting this here, i'm not able to post in the development section yet.
Also, the purpose of this thread is simple, I see so many people struggling with failed flashes in the kingdroid thread, I just want to give them a proper step by step tutorial.
Also, If someone could link this with the Kingdroid thread, that would help more
Note: Some of the stuff (maybe most of it) is familiar to the more experienced users here, but it took me sometime to search and find everything when I started flashing for the first time, so I want to put every little detail here, so that even beginners wont have to look elsewhere..
Hello everyone
I will tell you the method I use to install Kingdroid, CWM method, its nothing new, but I have consolidated everything spread around android development section into this one thread so everyone has better access..so lets start.
1) Keep these inside your external sd card all the time, for quick access and just general convenience.
- Abyss Kernel
- Kingdroid_ics_notemania V7
- Sybr_kernel_cleaning Script
- GL_NOTECORE Kernel
- SpeedMod Kernel
- Franco Kernel
(make a folder , lets call it 'flashaholic', in your external sd card, and put all of the above in it)
2) Use titanium backup (free version sufficient enough) to backup all ur data..
3) Switch off your phone, reboot into recovery, you can do this by pressing the volume up + home + power button .
4) Inside the recovery, you can navigate with the volume keys acting as direction (up and down) and the power key working as an 'enter' key.
5)from recovery -> install zip from sdcard ->choose zip from sd card -> flashaholic -> abyss kernel -> install it
again from recovery -> go into advanced -> reboot into recovery
6) from recovery -> wipe cache partition
Go to advanced -> wipe dalvik cache.
7) The new recovery is a touch interface, navigate to the flashaholic folder, and install Kingdroid V7
8)Aroma installer will start, it is pretty straightforward from here, keep clicking next, you will come to without wipe/full wipe, I always choose full wipe,
In KD v7, there is another option screen in aroma that says ' with mods- or something like that' i always go for the second option in that,it worked fine for me .
9) kernel (go for cf-root) , modem ( I opted LDK)
10) Now you get to choose what ever applications you wish to remove, I remove almost all of it, most of it is useless as far as i see it, but its upto you.
11) next window , you can see what mods you wish to install , like bravia engine, beats audio etc.
12) next one you can install some apps that team kingdroid has set up with the rom.
13) finish install.
14) Now wait for the installation to get over, when you are back in recovery, click on reboot system.
15) dont panic , it will take sometime for the phone to start.
16) Now you show see the start up screen, set up your phone . Now its time for the kernel installation.
17) Kernels - always a tricky topic, i used all the above mentioned kernels and I will give my vote on which one is best for whom.
- Notecore, the current favorite,
positive : it gives really good battery life, and a relatively smooth performance, and an awesome quadrant benchmark score.
main reason for the score seems to be the i/o mark.
negative : Some serious lag on games , especially dead trigger on high, and please dont tell me this is just for me, a bunch of other people had the same issue hence i am putting it here.
verdict : Go for it if you need a good smooth performance with a really good battery life.
- SpeedMod
positive : Good battery life, not as much as notecore from my experience, good performance.
negative : little lag on game aswell, not as much as on notecore, these lags are most noticeable on games like templerun.
verdict : if u need something that is a little less positive and a little less negative than notecore, go for this.
- Franco
positve : Good performance on games, everything runs smoothly.
negative : battery life not as good as the previous two, benchmark score awful, mainly due to the i/o score.
Note : benchmark scores are good for showing off your phone, but not really a mark of your phones effect
Hope you can decide on which kernel to choose from above, else I am sure the more experienced devs here will lead the way for you
My personal fav, franco kernel, and as a good news, franco is back developing for galaxy note.
18) To install the kernel, reboot into recovery, go to the flashaholics folder, first run the sybr_kernel_cleaning script.
19) Now please DONT reboot the system, navigate to the flashaholics folder again , and install your desired kernel.
20) Now reboot your system and voila , you are running the new kingdroid V7 on your galaxy note
21) Use titanium backup to restore all your apps and stuff
Q/A
* source of above information : multiple threads in this website
* my experience : reading, reading, and more reading of everything put up here since the note was released, then practicing on my phone.
Special thanks to all the awesome ROM devs, Kernel Devs and Script Devs for making our phone more awesome
Links ( I hope connecting threads is not a problem, sorry if it is )
ROM : http://forum.xda-developers.com/showthread.php?t=1652831
KERNEL : http://forum.xda-developers.com/showthread.php?t=1789397
CLEANING SCRIPT : http://forum.xda-developers.com/showthread.php?t=1473622
ps: If I helped , hit thanks
You have done a good work here. However, I would not recommend doing a wipe (Step 5) if you are presently on a unsafe kernel, like stock ICS, which you should add, to prevent anyone from bricking their device.
Yin-Yang said:
You have done a good work here. However, I would not recommend doing a wipe (Step 5) if you are presently on a unsafe kernel, like stock ICS, which you should add, to prevent anyone from bricking their device.
Click to expand...
Click to collapse
The cache partion wipe, and dalvik cache wipe never caused a brick for me, and it was always followed up with installing the abyss kernel, which seems 100% safe when used properly I came from stock ICS myself, with the above mentioned method. But thank you for the input, I will look into it and make an edit if necessary
EDIT: made the necessary change thank you