Related
Well I've doing alot of messing about with kernels and and custom roms and now my videos no longer sync with audio.
Somewhere in bewteen stock and my current settings my video stopped syncing with thier audio.
- When I dicovered this I was using the latest overcome rom with it's kernel.
- I then tried reverting back to ROTO JME v4 using a previous back up: no change
- then going back to modaco's ext4 kernel: no change either
- Finally tried doing a full re-install of overcome and no change there too
I've been testing with .h264 encoded files on both stock player and Mvideoplayer which previously played the files fine.
Anyone have any idea where I've stuffed up and can offer some advice?
edit: tested using rock player lite, files play fine under normal settings but after switching to hardware decoding i get the same audio sync problems. I hope this narrows down my problem.
edit 2: just tried reflashing roto jme v4 full clean install and also no go
Bump, I've really gotten used to the speed of the new roms so I would like to avoid going back to stock
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?
I have a problem with SDSL final rom, I installed it on Sunday, this would be the 3rd time installing it, first 2 times I did it by fastboot, and the last time by recovery, my system memory has 170 MB, after constant use of the phone, it restarts automatically, I don't get any error it just restarts, it only happens with this rom, previously I had PCF v. 5 and didn't had this problem, I changed back to SDSL do to a better battery management and speed, I have setcpu to 804 and swap of 400, even if I leave the CPU to 600 it restarts, I have smartassv2 governor, any idea why is this happening? Even if I don't use the phone it restarts, help please!
Sent from my GT540 using XDA
pahb22 said:
I have a problem with SDSL final rom, I installed it on Sunday, this would be the 3rd time installing it, first 2 times I did it by fastboot, and the last time by recovery, my system memory has 170 MB, after constant use of the phone, it restarts automatically, I don't get any error it just restarts, it only happens with this rom, previously I had PCF v. 5 and didn't had this problem, I changed back to SDSL do to a better battery management and speed, I have setcpu to 804 and swap of 400, even if I leave the CPU to 600 it restarts, I have smartassv2 governor, any idea why is this happening? Even if I don't use the phone it restarts, help please!
Sent from my GT540 using XDA
Click to expand...
Click to collapse
swappiness 400 ?? or 400 mb swap ?
andreas__ said:
swappiness 400 ?? or 400 mb swap ?
Click to expand...
Click to collapse
O_O yeah... that's what I had on PCF v5, 400mb
Sent from my GT540 using XDA
i got 632 swap and its good
Ok, a big problem with HD2, the speaker volume is low, with no apparent reason, with volume +:confused APK, all volumes appear in max. I'm using kernel 2.6.32.59 by dorimanx Rom - Nexus HD2 ICS CM9 HWA v. 2.3
and I increased internal memory with 40ad2sdx-a2Recovery, tried to fix permission and does not solve the problem.
Hi, I am not an expert, but I came across that problem. There was written, that when you use a2sd and you also move your dalvik cache, you get a bug of low sound.
So you should check where is dalvik cache. I cannot find forum where I read that, but I will try to find it and then put link.
Here is something - it is like guide how to move dalvik without bug low sound (I've never tried it).
http://forum.xda-developers.com/showthread.php?p=27005581
Sent from my HTC HD2 using XDA
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