yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] explorer-10:
i have v21.5 bfs with the 3.0.35 kernel though...

---------- Post added at 01:56 AM ---------- Previous post was at 01:34 AM ----------

just curious, what do you usually mean options-wise when you say "raise voltages by +/- xx across the board"? do you mean that in NSTools under the voltages tab to raise ALL the voltage options by xx volts?

also, same for the LiveOC when you say "raise xx across the board", do you just mean raising the 'oc value' percentage?

one OTHER thing...why is it that at random times, my screen just stays frozen at a tinted dirty-yellow screen and can do nothing but do a battery pull? same goes for when sometimes i just close my screen, then seconds later, i cant turn the screen back on, so i have to pull the battery to boot it back up =(
[Nexus S Android Development] RicardoOneri:
Yes to all! Also you should update to 22.0 CFS, the version you have is a bit buggy and the freezes are fixed on newest version, update and you should be fine..:rolleyes:

Also here's some screenshots about baterry life, Aweasome! :D
[Nexus S Android Development] explorer-10:
this tends to happen to me at random times. sometimes after i use any app, i force stop it and then close its task window and then close my screen. then minutes after i attempt to turn the screen back on, it doesn't and just gets stuck at a blank screen as if it was off, so i have to pull the battery a couple seconds and power back on =(

---------- Post added at 11:23 AM ---------- Previous post was at 11:17 AM ----------

will v22.0 BFS be fine? i game on my phone from time to time, like the ones that use quite some cpu/gpu power
[Nexus S Android Development] SA-07:
Yeah go from v19.5/20.0 -> 22.0

v22.0 BFS should go well for you explorer-10
[Nexus S Android Development] explorer-10:
oh...im already on v21.5 though. should i just wipe both reg. cache and dalvik then flash v22.0?

originally, i think i started out with v19.0 CFS, then v19.5 BFS -> v20.0 BFS -> v21.5 BFS
[Nexus S Android Development] CrackerTeg:
Just flash v22 and you'll be fine. Don't wipe anything. It already has a wipe script in it.
[Nexus S Android Development] caliban2:
Ugh! Don't let some certain people read this. Oo

One always has to wipe caches BEFORE doing anything in recovery, plus spinning the phone 3 times counter-clockwise, pray to the gods of the great nexus and finally sacrifice an iPhone. Then, and only then, it's safe to do anything in recovery - even reboot.

:p
[Nexus S Android Development] CrackerTeg:
You ain't kidding. Lol
[Nexus S Android Development] SA-07:
Does one have to turn down a GS3? :p
[Nexus S Android Development] CrackerTeg:
In your case, yes. We need Matr1x for JB and you'd be the guy to do it.

J/K MK. If you want to move on and leave us poor saps behind, its your prerogative.

Did I make you feel guilty at all? :p
[Nexus S Android Development] SA-07:
Decisions, decisions, decisions :confused:

Sent from my Nexus S
[Nexus S Android Development] caliban2:
Told you before, and I tell you again: nexus is the only smart choice you can make. :)
[Nexus S Android Development] SA-07:
And wait a very long time? Lol dunno...

Sent from my Nexus S
[Nexus S Android Development] CrackerTeg:
You know as well as everyone here there's going to be a nexus the end of this year and that's the way I'm going. After having this phone,I wouldn't do it any other way. Besides, the s3 looks too much like the old iPhone with its rounded edges.
[Nexus S Android Development] nodstuff:
I wouldn't bet on there being a new nexus phone this year as we already had a nexus release and the release of the new version of android.

Historically the new version comes out on the new nexus phone but this year it came out on a tablet.

I wouldn't expect a new nexus phone to come out until the next version of android, and that will definitely not be this year.
[Nexus S Android Development] CrackerTeg:
True but this is also MK's kernel thread. We're going a bit OT with talks of the next nexus phone. I'd hate to derail this with that especially since people subscribe to this thread waiting for possibly another update.
[Nexus S Android Development] 309041291a:
Going to try 22.0 today :P

Sent from my Nexus S
[Nexus S Android Development] JokerAce:
Mathkid, or anyone, after looking at my settings, let me know why do I have at least one random reboot a day?

For CPU setup

Governor:
smartassV2

Min/Max CPU freq:
100mhz/1050mhz

[U]Live OC
[/U]
OC Value:
105%
OC Target Low:
800mhz
OC Target High:
?

Deep Idle:
Off (because I don't use apps when phone is sleeping)
[U]
SMARTASS V2[/U]

Awake ideal freq:
768000Hz
Sleep ideal freq:
245000HZ
Sleep wakeup freq:
768000HZ
Min/Max CPU load:
25%/90%
Ramp Down step/Ramp Up step:
256000Hz
Down Rate:
99000 us
Up rate:
48000 us

For Voltages Setup

[U]ARM Voltage[/U]

Max ARM Volt:
1500 mV

1460mhz = 1450mV
1300mhz = 1400mV
1200mhz = 1325mV
1000mhz = 1250mV
800mhz = 1200mV
400mhz = 1025mV
200mhz = 950mV
100mhz = 950mV

[U]INT Voltage[/U]

Max INT Volt:
1325 mV

1460mhz = 1225mV
1300mhz = 1175mV
1200mhz = 1125mV
1000mhz = 1125mV
800mhz = 1075mV
400mhz = 1025mV
200mhz = 975mV
100mhz = 925mV

I added 25mV across most of the voltage after OC to 105%..

I am using latest 22.0 CFS. I/O:noop
[Nexus S Android Development] apatal:
Try it without Live OC, or put a value in the High OC Target.
[Nexus S Android Development] SA-07:
LiveOC adjusts your bus speeds too so yes, try it without liveoc

Sent from my Nexus S
[Nexus S Android Development] caliban2:
What tells you there won't be a new nexus phone with 4.2 in December? Galaxy nexus certainly won't be the lead device until 2013, it's too old for that already.
[Nexus S Android Development] apatal:
I'm tempting fate and playing with live OC (even though I don't really know how to use it..). let's see how it goes. ;)

Sent from my Nexus S
[Nexus S Android Development] caliban2:
@JokerAce:

Instead of noop, try deadline as scheduler. And for the future: If you encounter freezes/reboots, overclock is the first thing to disable. :)
[Nexus S Android Development] JokerAce:
What value should I put? I don't want to brick my device. Have seen some SGS2 poster bricked their device when playing with live OC.

Then should I remove the 25mV I added? I added them becuz I enabled live OC. Also, can you see the cpu setup? Are my variables okay?

I only set to 1000mhz :( Not even overclocking :( Only enabled live OC which made my max cpu to 1050 (+5%)
[Nexus S Android Development] caliban2:
LiveOC is also overclocking. But granted, it's not that high in your case. Still, never report any freezes without disabling OC first, some phones just can't take it.

Try deadline. My phone always gets unstable with noop. Maybe you're affected as well?

Edit:

Btw, with your setup, 105 live oc means 800->840 MHz as well. Not just 1000->1050.
[Nexus S Android Development] JokerAce:
Just wants better speed/performance and decent battery life. Will take the suggestion on i/o in view.
[Nexus S Android Development] explorer-10:
I've been stuck in ICS bootanimation for 5 mins now after wiping cache and dalvik, flashed v22.0 and wiped battery stats

I know that this phone or maybe just my phone, tends to get a lot of problems from time to time, but I will stick to its side no matter what, ONLY until nexus no longer gets anymore updates, maybe THEN I will change to a new phone

These kernels are somewhat preventing my phone from waking up from an ice cream-filled fantasy..

Been doing quite a few battery pulls here and there, probably 4-5 times so far and nothing. I even tried doing a fix permissions, still nothing. Every reboot and getting to recovery, I always did wipe cache and wipe dalvik flashed kernel, and once or twice, wiped batt. stats
[Nexus S Android Development] micha3lvd:
Try doing complete wipe.. first BACKUP then wipe everything then install rom then reboot then flash kernel then reboot and hopefully enjoy =]
[Nexus S Android Development] N@th_OC:
Why wipping battery stats????

It will not help you on anyway...

If you try everything, try to reflash your recovery... Maybe it will help. :confused:
[Nexus S Android Development] apatal:
@explorer: never really had these issues before. can you post here your phone setup - what rom, radio, etc.

Sent from my Nexus S
[Nexus S Android Development] granets:
I am also having troubles with smartassv2. Random freezes and reboots. I now use on demand. It's slower a bit but far more stable in a long term use
[Nexus S Android Development] jayjay3333:
I almost always run smartassV2, noop, 100-1200 and never have issues with the new V22. MK and testers worked that kernel to the bone. :D
[Nexus S Android Development] explorer-10:
it's in my sig..

and even if i look for other info in the settings menu, i cant, so...=(

how do i reflash recovery if i cant even gain access to rom manager?

will i lose my text msgs and usb storage files after a complete wipe? i used to have a phone that had microsd storage so i already knew everything would still be intact, but since usb storage is part of the phone, im not sure...
[Nexus S Android Development] 309041291a:
USB storage and all your folders will be safe. Texts will not be safe. But you can do a NANDROID and restore them and other settings after then ROM is installed.
[Nexus S Android Development] explorer-10:
i havent done a nandroid in a while, but by doing so, will it save my texts and it mms?
[Nexus S Android Development] micha3lvd:
try using titanium backup, then backup data of the messaging app, that should do the trick (Works with me for Viber and Whatsapp(Though I prefer doing clean install with Whatsapp and just restore from SD card))
[Nexus S Android Development] chronophase1:
Wiping stats doesn't help with anything. Maybe a bad download or flash? I've had bootloops before but a reflash has always fixed my problem.

Sent by pocket technology.
[Nexus S Android Development] flyers2114:
Please help

Ok, so I ran this on my newest JB rom that I made....but the issue is your kernel is acting funky, I need you to look into this ASAP Mathkid....if you are going to make a kernel please make sure that all the voltages are correct....you have them too high in some instances which is causing issues....I have my car app that I use...it will start the car, but because the voltages are too high it broke the glass on my drivers side window....I honestly feel that you should pay for this, but I am not going to pursue it.....but can you please get the kernel to run correctly and add a disclaimer if not , so that others are not having issues....the other thing is it continues to blow the fuse on my microwave that I hooked up inside my vehicle also....but because that is not standard on the car, its really not you issue...

.oh btw pic of my car attached with window broken...:crying::crying:
[Nexus S Android Development] caliban2:
Don't drink and post... :screwy: :p
[Nexus S Android Development] mixtapes08:
You on crack?

Sent from my Nexus S™
[Nexus S Android Development] explorer-10:
like i said before, i cant gain access to anything, but just the recovery and bootloader. i am stuck in a bootloop animation

i even left my phone alone for an hour during the boot-up process and when i came back, it was still in the boot animation! ='(
[Nexus S Android Development] flyers2114:
Just because innovation is above you, no need to insult if you cannot help,....my post was for the dev, not the trolls. So please move past it, this is highly advanced technology, not for the average user. The car app was developed by myself and a friend, the op here has his kernel inoperable in the state it is.....

Sent from my S3
[Nexus S Android Development] CrackerTeg:
Um yeah... Sarcasm is hard to convey through the intarwebz.
[Nexus S Android Development] explorer-10:
If some of my contacts weren't saved to google, then will, for example, the new contacts disappear after doing a wipe?
[Nexus S Android Development] :
I'm pretty sure you can force a sync in sync settings. Do that before wiping
[Nexus S Android Development] explorer-10:
not to be rude or anything, but for the 2nd/3rd time, i cant access the sync, just the stuff i added right now, noted below

----------------------------------------------------------------------------------------------------------------------

will posting a logcat help? its quite a long list, but i captured like 7+ seconds of it

edit: i also tried doing a device dump, but i couldnt save because it was grayed out[using the dalvik debug monitor]
[Nexus S Android Development] explorer-10:
--oops, i thought it was going to merge as a double-post--
[Nexus S Android Development] mixtapes08:
Really? then act nice not ****. The kernel is for.phones not for your app your not paying the dev to do it for you dumbass.

If you don't want to be criticize here create your own kernel then.

Sent from my Nexus S™
[Nexus S Android Development] explorer-10:
just attempted to create a nandroid and at the end of the process, it gave me a "Error while making a backup image of /data!"
[Nexus S Android Development] flyers2114:
See I told you there is a problem.

Sent from my S3
[Nexus S Android Development] flyers2114:
Actually you are incorrect, I paid him a great amount of money to achieve this. He gets the 2nd half upon completion, he still has to tie the kernel into the built in generator. Then him and I will both make even more money, imagine making popcorn right in the backseat!:$

Sent from my S3
[Nexus S Android Development] shabbypenguin:
flyers2114 you are in the wrong section, this is for the gsm SGS3, you have the sprint one. you need to refer to here

click thanks if i solved your issue :)
[Nexus S Android Development] flyers2114:
Oh ****! I am an idiot, my bad all, thx Shabby. Guys stay tuned though, the car with app and kernel is going to be featured on MTV in August, when completed. Thx again.

Sent from my S3
[Nexus S Android Development] SA-07:
Hellll yeahhhh

Sent from my Nexus S
[Nexus S Android Development] apatal:
dude, something is seriously wrong with your phone.

can somebody help this guy on how to flash a new recovery to his phone?

Sent from my Nexus S
[Nexus S Android Development] explorer-10:
"Error while making a backup image of /data!" during nandroid process! =(

*re-posted to the current page just in case*
[Nexus S Android Development] SA-07:
alright download a new cwm recovery from the official website.

Type these commands:

fastboot erase recovery

fastboot flash recovery _____.img

Boot back into recovery and try again

Sent from my Nexus S
[Nexus S Android Development] explorer-10:
before i go on and do so, i backed up my "error'd" nandroid to my laptop in hopes of trying to re-make a successful backup, only to find out that i can't find the new clockworkmod folder that it created again and that it just ate up 700mb+ of my space

i even went into USB-storage mode in hopes of trying to find it from my laptop, but nope, same thing

edit: i had 2.53 gb space left, and after attempting to hopefully create a 2nd successful backup, no go, but a weird "empty" set of files just ate away ~700mb of my space. i just looked through every possible folders containing at least 700mb worth of files to find nothing. its like a ghost hunt here O_O *x-files theme song plays*
[Nexus S Android Development] mixtapes08:
Facepalm:thumbdown:

Sent from my Nexus S™
[Nexus S Android Development] explorer-10:
how many files are created when a nandroid is made?
[Nexus S Android Development] micha3lvd:
Files ain't got a clue but my backups are a bit less than 900MB each.. if you performed a backup before just check your clockworkmod folder on your SD card.
[Nexus S Android Development] explorer-10:
this is gonna sound funny, but apparently i cant find it. ive made a 2nd attempt and 700mb[size of backup] just got eaten away when it isnt even visible, not like its a hidden folder or anything. in the first folder created, i had 4 files[recovery.img, boot.img, data.ext4.tar and system.ext4.tar. dunno if theres supposed to be 1 or 2 more files
[Nexus S Android Development] caliban2:
Nah, this stopped being funny some time ago, you're posting in the wrong thread. This ain't kernel related. If I had to guess, I'd say you wiped the wrong partition when flashing matr1x.

Try reflashing your rom without wiping anything. If you're lucky, it will boot again. If not, stop fiddling around and do a full wipe, then set it up from scratch.

Forget making a backup now, what good will come from a backup of a broken system?! :confused: You should've made one while it was still working!

EDIT:

My mistake, when flashing the rom-zip, wipe cache and dalvik-cache. But nothing else. And then pray you're lucky. ^^
[Nexus S Android Development] JokerAce:
Actually, for a really thorough wipe, he should go to "advance" and perform "format system, format data, format cache" Flash ROM and try to boot it up. Seriously, it's a hard lesson to learn, but when you don't faithfully do nandroid, you are just playing with hell-fire.
[Nexus S Android Development] caliban2:
Yes, we all know that. That's the second option, called full wipe. My edit was for trying to flash rom only to see if it boots again. There it's only cache and dalvik. After all, he's trying to keep his data.

And btw, you forgot to mention /boot.
[Nexus S Android Development] JokerAce:
Yeap, format boot too. Heh. Haven't done that for a long time. Such thorough wipe are only used as last resort for me.
[Nexus S Android Development] obscure.detour:
I'm getting green lines on the camera with pictures being half gray or fully gray. This has happened on two full wipes (factory, /system). With installs of CM9 RC1 and AOKP build 40.

All settings default except BLN was activated.

Anyone else?
[Nexus S Android Development] apatal:
Nope. don't have that here. Can you please check your voodoo color settings if you have it, and try setting to default values?

Sent from my Nexus S
[Nexus S Android Development] mixtapes08:
Read the faq in the op sir

Sent from my Nexus S™
[Nexus S Android Development] jasonmaloney:
Have you dropped your phone?
[Nexus S Android Development] explorer-10:
my rom is from a stock rom OTA update though...and its been a clean install since, but idk why its been acting up after flashing v22.0

what kind of info is contained in /boot anyway? what will happen if i format it and will it possibly fix my problem?
[Nexus S Android Development] obscure.detour:
I have tried changing the screen v1 gamma settings to 2.3.3 settings and rebooted. Camera works great now! Thank you for the suggestions. The above was tested on AOKP build 40. And no I have not dropped my phone. :)

This combination of matr1x v22 and AOKP build 40 might be the smoothest and quickest setup I've ran in awhile. Thanks for all your work mathkid95.
[Nexus S Android Development] apatal:
Dude, seriously, stop blaming the kernel! If it's possible to get the type of problem you're getting just by flashing a kernel, I'll be scared ****less every time I flash a new one, but I've been switching between v22 bfs and cfs and my phone is doing fine. obviously, you did something horribly wrong with your phone, may it be during wiping or something else, but it isn't the kernel's fault. I wish we could help you more, man, but at the moment, you're just stinking up the thread and not really helping anyone, least of all, yourself.

Sent from my Nexus S
[Nexus S Android Development] :
Don't format your boot!

If you look you can find a totally stock ROM to flash. (Format your system first.) Next, flash kernel, then reboot. Reapply root if needed.
[Nexus S Android Development] caliban2:
As long as he's trying to preserve his data he shouldn't wipe anything except caches. Just flash stockrom over and hope it boots again.

If this doesn't work, data is lost anyway and it's time for a full wipe in cwm:

- factory reset (formats data, cache & android.secure)

- format system

- format boot

Then flash rom.
[Nexus S Android Development] :
He won't lose data by formatting system, but will need to download updates for system apps, or flash a recent gapps. User data is held in a separate partition.
[Nexus S Android Development] caliban2:
Yeah, it's stored in data.

Anyhoo, his sys is bonkers anyway, should've wiped a long time ago. And it never belonged I this thread. ^^
[Nexus S Android Development] JokerAce:
Boot can be formatted as a thorough wipe if all else fails. Flashing a ROM over, will replace the /boot content, so formatting boot is not an issue after all else fails - last resort.
[Nexus S Android Development] KreAch3R:
Sorry, wrong post.
[Nexus S Android Development] explorer-10:
is there a stock rom 4.0.4? i only see 4.0.3...

so okay, let me get this straight. first, format /system, re-flash stock rom, wipe both cache and dalvik, boot it up, then reroot if needed?

edit: would the stock rom happen to be this? https://developers.google.com/android/nexus/images#soju [2nd 'link']
[Nexus S Android Development] azrealsoh:
There is ics 4.0.4 rooted stock rom. You u wont need to reroot. Can found in nexus s android development category
[Nexus S Android Development] DaX05:
Well Mathkid & fellow Nexus S users.. I just purchased a Galaxy Nexus via the Play Store. Hopefully I'll see you guys over there sooner than later. Consider it "entering the grid" from the film Tron. :) It was a pleasure learning from all of you guys in the year & a half I had here.

Beamed from my Nexus S using Tapatalk 2.
[Nexus S Android Development] explorer-10:
would this be the one you're talking about?

http://xdaforums.com/showthread.php?t=1569509&highlight=stock
[Nexus S Android Development] LibertyMonger:
WOW What has happened to this thread??? Absolutely nothing Matr1x related in the last 10 pages it seems! And I get *****ed at for my posts LMAO
[Nexus S Android Development] apatal:
Same **** that has been happening ever since. Why, what's up with you?

Absolutely nothing for the least 10 pages? As in zero/zilch/nada/null/wala?

These are pretty solid statistics your alluding to. Remember, even a single mention of the kernel in the last 10 pages will blow your rant completely out of the water. Are you absolutely sure that there is no freakin' mention of the kernel in the last 10 pages? You have to be sure because if it's true, I will personally go to mathkid's house and say to his face what a ****ty thread he has and he better do his utmost in maintaining the sanctity of the nexus S matr1x kernel thread, or I will clean it up for him!

So...are you sure you want to go down this road?
[Nexus S Android Development] LibertyMonger:
Get a life dude. If this is what worries you so much. This thread does need cleaned up. And I say he starts a new one for Jelly Bean which he probably will.

***Reading your post again, you got major issues dude.
[Nexus S Android Development] apatal:
LOL. i know. don't worry, dude. I'm just messing with you. :D

As for mk making another thread for JB, I'm not too sure about that but one thing I can tell you is this: he is also eagerly awaiting for the JB source to drop. ;)
[Nexus S Android Development] sdhanjal15:
Mk has got a few things under his sleeve since the last time we talked.
[Nexus S Android Development] Rjevon:
I was having the same issue and I switched the gamma hack to default 2.3.3 and that got rid of the lines while in camera mode. Well after charging overnight my phone rebooted into the ugly pink T-Mobile color and I had to pull the battery. So now I'm trying punchy settings and getting reboots. I'm running dax's remix rom. My min max is set at 200-1000 cause my phone can't handle uv. Anybody got any other suggestions that might help?
[Nexus S Android Development] chronophase1:
Have you actually changed the voltages? Just changing the frequencies isn't doing anything.

Sent by pocket technology.
[Nexus S Android Development] mixtapes08:
Read the faq dude

Sent from my Nexus S™
[Nexus S Android Development] Rjevon:
I read the FAQ dude. By the way the faq says nothing bout the camera having green and gray lines through it. I have tried upping the voltage also by 25 also. I've only had one reboot since changing to punchy settings. I'll try the voltage again if I keep getting random reboots. So far only one reboot since this morning.