yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] n0w4y:
+1 to corrupted data.

governor: smartass
[Nexus One Android Development] momomok:
has been fine running with smartass for several weeks :D

one quick question to Mr. IR:

Will there be any update to the kernel?

there seems to be some kernel update to N1 on 19/6

http://review.cyanogenmod.com/#change,6201
[Nexus One Android Development] yermet:
I had to come back to version 2.6.38.7_AVS-CM7_CFS_20110527_2139, any 2.6.38.8 was corrupting my system whenever I used smartass, savagedzen or interactiveX after a few days of recovering a previous nandroid backup.

With 2.6.38.6 everything goes perfect, no matter I use the stable or any nightbuild... :S

My 2 cents.

Cheers!
[Nexus One Android Development] intersectRaven:
It's just the serial update I think so I don't think I'll be updating for that. It's too small. :p

As for the corruption issues, haven't experienced it so I can't do anything about it. :confused:
[Nexus One Android Development] Arrqh:
Is there anything we can do to help debug it or something? Or at least prove that we aren't hallucinating? :p
[Nexus One Android Development] phewizzo:
Im suprised no one has cooked up .39 yet.
[Nexus One Android Development] noisemonkey:
It's happening with me to. Fortunately I can just restore the affected apps in tb
[Nexus One Android Development] intersectRaven:
We're all waiting to go to 3.0. :p
[Nexus One Android Development] intersectRaven:
Just the usual kmsg would be nice. :)
[Nexus One Android Development] intersectRaven:
Update released by the way. Just some ARM stuff. :p
[Nexus One Android Development] noisemonkey:
All working fine and no weird behaviour :)
[Nexus One Android Development] jameztcc:
Working fine as usual, thanks!
[Nexus One Android Development] momomok:
The latest kernel is running fine, and smooth. Thanks!
[Nexus One Android Development] Lultima:
The same Here ... Thanks !!!
[Nexus One Android Development] greenleaves:
I'm new to this kernel but wanted to give a try together with SSN1 that I heard something good about it. There are three versions: NOBOOST, CAVS and AVS. Wonder what best to choose from?
[Nexus One Android Development] warren2781:
That would be CAVS.
[Nexus One Android Development] Arrqh:
I've been logging my kmsg and rebooting over and over again all day and my corruption issues are suddenly no where to be found. :p I'll keep at it...
[Nexus One Android Development] cyberon:
Hi guys, witch governor would you recommend for MIUI, daily use?

Data corrupted using smartass governor! :(
[Nexus One Android Development] phewizzo:
Is the data corruption in ext4 still present in your kernel? I know Wildmonks fixed this in his latest.
[Nexus One Android Development] intersectRaven:
I doubt it. I've PMed wildmonks for his fix as I do not use EXT4 so I cannot debug this. :)
[Nexus One Android Development] sir*mez:
I have ext4 with no corruption.
[Nexus One Android Development] temasek:
I've no corruption too with ext4 using smartass.
[Nexus One Android Development] puttytatko:
temasek could you tell if I need to flash your sqlite tweak each time I flash a nightly kernel??? also the SD card cache fix too???
[Nexus One Android Development] temasek:
1. I don't recommend sqlite tweak unless u are on DT A2SD (especially using datasd).

2. SD card cache fix has benefits and disadvantages (more of disadvantages) too. I recommend leave at CM's default of 128
[Nexus One Android Development] momomok:
So the 2MB read cache is not good?

Will it kill my card prematurely?
[Nexus One Android Development] phewizzo:
The corruption usuallly happens after a reboot, not exactly when you first install the kernel and boot it up, hut its running fine right now, thanks IR.
[Nexus One Android Development] puttytatko:
thank you temasek... also is it better having to use an ext partition on the SD card for apps??? because I just use the move apps to SD option from cyanogenmod settings and move them to the fat32 partitioned card ..are there differences in terms of better app performance or anything ??? i can't find anything through Google too..
[Nexus One Android Development] temasek:
This is a kernel thread. If u wish to know the answer, proceed to DT thread.

http://xdaforums.com/showthread.php?t=715940
[Nexus One Android Development] intersectRaven:
I just spoke with wildmonks and he said that the fix is already in my kernel so whatever is causing the EXT4 corruption on some phones, it's something to do with your setup or hardware. :cool:
[Nexus One Android Development] bobtentpeg:
Hmm, the SavagedZen governor is causing wakelocks like theres no tomorrow. Back to smartass
[Nexus One Android Development] phewizzo:
Ok sounds good.... i havent had any problems yet.
[Nexus One Android Development] noisemonkey:
Why is it when I flash your kernel all my contacts are wiped and I have to resync? Might be a

Noobish question.
[Nexus One Android Development] access9:
same issue here. and when I rebooted, everything was back to stock with all my databases corrupted.
[Nexus One Android Development] solidmac:
I.m curious to know how everyone that flashes does their order go

between people like us that get corrupt data and people like teamsek that doesn't have a problem...

My order is rom>DTa2sd>kernel
[Nexus One Android Development] noisemonkey:
Ah ok. I didn't do dta2sd
[Nexus One Android Development] sir*mez:
I don't use dta2sd cause its too unstable/hackish for me. I use S2e a2sd from the market cause its easy just set it and forget it.

So my order is Rom>Kernel>ss4n1 unless its a fresh reinstall then its rom>gapps>kernel>ss4n1. I never had data corrupt unless I was using clockwork recovery.
[Nexus One Android Development] intersectRaven:
I'm beginning to think it's DT2ASD (whatever) that is the source of the odd wipe thing. Anyways, I don't use it so no problems for me. :p
[Nexus One Android Development] temasek:
I'm using dt and your kernel. No issues whatsoever.
[Nexus One Android Development] cloversis:
may i have the link of sqlite tweak for n1, thx:)
[Nexus One Android Development] temasek:
In my mediafire folder.
[Nexus One Android Development] ferfecir:
Which one should I use more battery consumption?

rom: N1-CM7
[Nexus One Android Development] intersectRaven:
Frack that theory then! Maybe it's just AVS then with some CPUs. :/
[Nexus One Android Development] temasek:
I wouldn't be a loyal fan of your kernel if it gave me problems.

None whatsoever.

Cheers for IR. :)
[Nexus One Android Development] Lultima:
IR 28/06/2011 CAVS on CM7 RC1 with DTA2SD working flawless ...
[Nexus One Android Development] solidmac:
Yeah im using an avs kernel I haven't tempted into making my own custom one
[Nexus One Android Development] temasek:
I'm testing airplane mode on my N1.

3 days 4 hrs........

Display used 30 mins (on WIFI only)

Battery level 74%

WTF.......That is how great IR kernel is :)
[Nexus One Android Development] momomok:
running smartass?
[Nexus One Android Development] temasek:
Yes................
[Nexus One Android Development] intersectRaven:
I almost dropped off of my seat before I noticed that it was on airplane mode. :p
[Nexus One Android Development] temasek:
hehe :)

Still even on airplane mode its unbelievable.
[Nexus One Android Development] sir*mez:
I think its user error. I think they are forgetting to reflash dta2sd after every flash of the rom. That's why I use s2e a2sd because I always forgot to flash dta2sd and kept losing everything. I like the set it and forget it a2sd in s2e.
[Nexus One Android Development] Arrqh:
It is not user error, I previously had the data wipe problem despite not using DT2ASD. Even then, that wouldn't make sense because the problem happens after a reboot, not necessarily the first boot after flash.

On the other hand, in my attempts to figure out the cause, I did a lot of wipes and reflashes. I'm now running the lastest AVS with InteractiveX and no matter how many times I reboot I can no longer reproduce the problem. So my guess is that it's some odd configuration issue or conflict. I don't think it's hardware... I've been running with these AVS kernels since the beginning and I've never had any other issues.

I'd really like to help debug this though, so I'll keep trying to repro it...
[Nexus One Android Development] n0w4y:
Thanks to the post of sir*mez I probably have found a solution for the corrupted data error (at least for some of us).

I always tried to flash the kernel through the newest CWM. The only custom kernel which worked correctly was the one from pershoot (don't ask me why).

So after reading the above post, I flashed the CR from Amon_RA.

to cut a long story short:

yes, it worked and i didn't had any misbehaving so far!

Some more info:

I'm not using DTA2SD.

Flashing Amon_RA's through ROM Manager didn't worked for me, so i flashed it manually with terminal. Putting the recovery.img into root of my SD, hitting the following:

sh
cd /sdcard
flash_image recovery recovery.img
[Nexus One Android Development] noisemonkey:
Thus was occurring even though I wasn't using data 2sd. It was fine in versions of intersect ravens kernel prior to the.8, version
[Nexus One Android Development] sir*mez:
If its not dta2sd then its clockwork recovery 3.xx+, if its not the recovery its wifi calling if its not that then its low /system memory, lol.

If you want to use clockwork recovery use 2.5 and below or use the new clockwork recovery 4.0 compiled by zyonee that I helped debug so that data doesn't corrupt. Or to be safe use amon_ra 2.2.1. Other than that the kernel has always worked great for me.
[Nexus One Android Development] makelegs:
I agree completely.
[Nexus One Android Development] intersectRaven:
So recovery can actually affect it? Odd one that... :/
[Nexus One Android Development] noisemonkey:
I'll give that a go, cheers
[Nexus One Android Development] Arrqh:
I hate to keep saying "no" to everything, but I had the problem when using Amon_ra...
[Nexus One Android Development] bimasakti85:
What's the problem? I'm using DT datasd with IR kernel too. No problem. Only sometimes it get stuck in the X logo. It"s solved by wiping dalvik cache.

Sent from my Nexus One
[Nexus One Android Development] sir*mez:
What else are you doing/adding? What gapps do you flash? Are you using gtalk with video chat? Because that also adds a lot to the /system partition. Help us out we're trying to help you and your not providing anything to help us help you. Atleast a last kmsg or logcat something anything instead of saying, "no data still corrupts". We're not magicians here.
[Nexus One Android Development] solidmac:
This is my setup right now:

ROM: CM7 nightly

MISC: DTA2SD

Gapps: Temasek's Gapps (dont remember the date but it was the Gtalk mod one)

Kernel : IR .38.8

I flash everything excluding Gapps, i still lose all my data. Raven, can you create a test version with AVS version that doesnt scale so low to make it much more stable or similar to '.38.7'... There is something missing that didnt carry over from that previous version that is causing this problem.

[Q] anyone with .38.8 CAVS having this data corruption problem?
[Nexus One Android Development] sir*mez:
Can you tell me how much mem is left in your /system partition? Can you try to flash a gapps without the gtalk mod. Like an official gapps and see what happens.
[Nexus One Android Development] solidmac:
dont see how gapps would affect this... it worked on 38.7.....

Are you on cavs kernel?
[Nexus One Android Development] bimasakti85:
I'm using the CAVS without no problem...

Sent from my Nexus One
[Nexus One Android Development] sir*mez:
Gapps with modified Gtalk and libtalk_jni.so are significantly bigger than the official gapps in /system partition. Therefore not having enough space in /system cause errors since everything on the rom can't fit.

Yes I am using CAVS. How low are you customizing your voltages in the cavs kernel? What are you using to lower the voltage? Are you even lowering the voltages, if not then why are you using a cavs kernel. I can keep assuming if you'd like...

I've answered your questions, how about you answer mine as I'm beginning to think that you don't want to be helped or be helped specifically by me which is ok by me. I wont have to waste my time asking away to help you out. Just sayin'.
[Nexus One Android Development] intersectRaven:
True. CAVS without any voltage setting (either manual or the script thing) is just plain SVS voltage like all of those non-AVS kernels.
[Nexus One Android Development] ultra99:
I'm really confused. Which one should I use for my setup?

Setup:

Fitsnugly's Gigglebread CM7

Data2ext aosp script

6gb fat32

1gb ext4

300mb ext4

128mb swap
[Nexus One Android Development] temasek:
Anti-confusing kernel ...... AVS-CFS

Edit: I'm serious not joking. I am a user who like just flash a kernel and forget about tweaking it. Reason - that kernel already solid enough for me.
[Nexus One Android Development] ultra99:
thanks, but NO BOOST or the other one? :D
[Nexus One Android Development] temasek:
Since day 1 I use IR kernel I just use AVS CFS. I don't use others.
[Nexus One Android Development] ultra99:
but there's AVS CFS NO BOOST and just AVS CFS, what does NO BOOST do?
[Nexus One Android Development] temasek:
Why don't u try it and test it? Its more practical than others telling u. Reason - our ears tolerence are different. If I think is loud, you may think is normal volume.
[Nexus One Android Development] sir*mez:
Noboost - no audio gain

CAVS - user can customize voltage table to their liking

AVS - has audio gain

If you don't customize your voltage table use AVS. Then you have to choose with audio gain no not.

Why are you using a swap partition? That was only needed for the G1/Dream days, there's no real advantages for the Nexus One.
[Nexus One Android Development] solidmac:
Already answered your question... and if 49mb of system storage isn't enough let me know....
[Nexus One Android Development] daveid:
What have you removed from the rom to get 49mb free on /system? Or are you confusing your available system memory as reported by the storage settings screen? Cause that is the /data partition, and irrelevant to this conversation.

If it is /system, what have you removed from the rom, and what is your removal method - pre or post flash?
[Nexus One Android Development] makelegs:
I'm betting that's 49mb in /data...not /system.

Try flashing Temasek's system app removal script after flashing ROM, but before kernel and DT
[Nexus One Android Development] sir*mez:
What else are you doing/adding/deleting? How low are you customizing your voltages in the cavs kernel? What are you using to lower the voltage? Are you even lowering the voltages? What recovery are you using? I fail to find these questions answered... I'm not going to waste my time anymore. I feel like I have to pull so much to get answers from you.
[Nexus One Android Development] Arrqh:
On the contrary, I have given all that information previously upthread, I don't have a lot of posts here so a quick search would have showed you that. The problem on my phone seems to have solved itself, but I spent several days trying to repro it to produce a relavent kmsg log without success. I'm doing my best to try and help here, but there isn't much point if no one is going to pay attention to it...

But for the sake of completeness, here is everything I can recall about the issue.

I first had issues when flashing the first .38.8 AVS kernel, around the time of CM7 nightly 96. On first boot after flashing, the Google Music beta app had vanished from my phone which was when I first noticed the issue. I believe I had about 8mb free on /system at the time, but I had flashed several previous versions of the kernel with that amount free and had no problems. I was not using DTa2sd at the time and my recovery was the latest amon_ra. The problem continued consistently after every reboot, characterized by missing data for apps... contacts would vanish, sms's would vanish, etc. When I restored to an older nandroid with the 38.7 kernel, the problem went away and everything returned to normal (demonstrating that it wasn't a hardware fault in my phone's internal memory, which was my first theory).

I did several wipes/reflashes and the problem seemed to persist. I cleared some apk's out of /system to get me to about 15mb before flashing and the problem seemed to persist. It seemed as though using the InteractiveX or Smartass governors was the source of the problem, but I can't confirm that. Somewhere along the line of wipes and reflashes, however, the problem on my phone seemed to resolve itself. I believe that the solution in my case involved not restoring my system data with TB, but I'm not sure. Unfortunately, it didn't occur to me to start dumping my logs until this point so I don't have any logs showing the problem occurring. I'll certainly keep trying to repro and log the issue, but I don't feel that it is a hardware problem relating to AVS (I've been using iR's AVS kernels for months and months without any issues) and I don't think it's recovery either since I've never used anything but amon_ra. My guess is that there is some sort of CM7 configuration issue that is causing a conflict with something in the kernel, possibly relating to the CPU governor or other performance settings. TB wiped my old settings backups so I can't restore them to confirm.

I'd be happy to answer any other questions about the nature of this issue, but I can't produce logs that were never recorded! Hopefully someone else who is still experiencing the issue would be able to do some log dumps.
[Nexus One Android Development] sir*mez:
I'm thinking people should flash cm7 rom>gapps(if its a fresh install)>dta2sd(if your using dta2sd only) then reboot. Check to see if everything is ok with the N1 running cm7 stock. Reboot, then flash kernel and any other add-on you use then diagnose from there.
[Nexus One Android Development] sir*mez:
Im using smartass gov and its been stable for me. Did you have to reformat your sdcard at anytime that you had a data corrupt?

To me this sounds like you didn't have enough /system memory because I've had those same exact symptoms when I went and flashed wifi calling add-on and I lost contacts, apps, etc.. I'm not saying you flashed any add-ons but that's what happened to me when there wasn't enough /system mem. 8mb in /system is pretty low, I suggest having above 10mb. I haven't looked at the sagagezen and interactivex give code to make any conclusions there. I know I didn't answer anything here but I'm going to look into it even though I don't see it.
[Nexus One Android Development] solidmac:
I'm not using a CAVS kernel if you look at the quote I had so instantly half your questions are answered. I'm using amon's RA recovery 2.2.1, temaseks Gapps, dt a2sd, and ir kernel

EDIT : also I have 7 MB. System data left
[Nexus One Android Development] pen²:
To throw in some more data points : been using cm 7.1.0 with rc1 with stock kernel, s2e for apps on ext3 and I manually deleted system apps like wallpapers, themes and latinime. My n1 has slcd and latest amon ra. Everything fine.

Did a nandroid backup, flashed Ir avs from 28th of June. Wiped Cache, dalvik-cache and vipermod. Rebooted, everything fine for 2 hrs (although vipermod was flashed, i didn't use it at that time). Then I restored my saved undervolting voltages, rebooted and was stuck at the X. (my undervolting settings were from about three weeks ago, and whatever Ir avs kernel was recent at that time).

I entered recovery and deleted my voltage file. Rebooted and got the green android.

Restored my nandroid backup and everything was still borked (about 8 fcs directly after reboot). Used temaseks format.zip, restored nandroid again, everything fine again
[Nexus One Android Development] Arrqh:
I haven't had to reformat my sdcard or anything like that, no. The data corrupt seems to leave everything on there alone.

I reflashed everything again tonight without cleaning out /system like I usually do and I somehow seem to be down to 4mb! :eek: I flashed CM7, Gapps (from may), DT and then the latest 38.8 AVS in that order. I'll run with this for a bit, if the problem happens again I'll capture whatever logs I can!
[Nexus One Android Development] solidmac:
So apparently the problem has fixed its self, at least for now.
[Nexus One Android Development] kgp700:
Hi there

thanks your advice before

i'm successful compile your kernel(2.6.38.8) with gcc4.4.0

i hope compile with gcc4.6.0 (https://github.com/redstar3894/Manifest)

but i don't know that how to use .c and .h files

i'm only possible to use available /bin/arm-eabi-gcc file

(sorry my bad english, do you know what mean?:confused: sorry again)

anyway, i'm compiled successful your kernel

but usb transfer speed too slow

your original kernel - average 1.7MB/S

my compile kernel(intersect-raven 2.6.38.8 source) - average 227~256KB/S

it's same as savaged-zen kernel

how to fix it?

how to usb transfer speed up?

thanks
[Nexus One Android Development] rickh925:
Same order. Dta2sd beta 4. No corrupt data and nightly flashes between CM and occasional other ROMs.

Sent from my Nexus One
[Nexus One Android Development] noisemonkey:
Successfully flashed and no data corruption issues. All working smoothly :)
[Nexus One Android Development] puttytatko:
the newest update is sweet!!!!! smooth and fluid cm7...and low battery consumption too :) :) whatever you did iR, its awesome!!!!
[Nexus One Android Development] kgp700:
thanks !

when apply your 7/6/2011 kernel source on github?

and sometimes can not working mic

Is it fixed?
[Nexus One Android Development] intersectRaven:
Not working mic? :confused:
[Nexus One Android Development] kgp700:
yes many people problem mic(telephone state) on your kernel(not 7/6/2011 ver, before version)

(not all time, sometimes)

if do not use a2sd , that will be fine

i think intersect-raven kernel don't like a2sd ^^;;

and i hope see your 7/6/2011 kernel source on your github

thanks
[Nexus One Android Development] nmesisca:
Hi there mate,

thanks for your work.

I have installed this latest release this morning on my nightly CM7 121 and I have been getting reboots every 10 minutes, until the device actually got stuck at the X screen.

Have then pulled battery and went back to previous version of your kernel.. but it still hangs at the X screen..

In any case, thanks again and keep up the great work you're doing for the community!

N

Update : went into recovery and wiped cache + Dalvik, now boots fine. next step I will give another shot to your latest creation together with cache wipe again..

Update 2 : reflashed your latest and greatest, then wiped cache and dalvik and everything seems ok now.
[Nexus One Android Development] kgp700:
A2SD+ working fine on 7/6/2011 kernel thanks

and mic has no problem

but sound recorder apps(cm7 app and market sound recorder apps)

and voice search not working on cm7 nightly119build

launch sound recoder app or voice search -> automatically reboot

other kernel working fine

but fast and smooth

and stable(exclude sound recorder apps and voice search)
[Nexus One Android Development] momomok:
Confirmed on fit's CM7 Nightly build
[Nexus One Android Development] schizophrenia:
same for me.. click on voice search and the phone rebooted.

froze on sound recorder too
[Nexus One Android Development] momomok:
Now reverting back to 0628 ;)
[Nexus One Android Development] erikclaw:
Just flashed last update, lost everything phone booted up to the screen where it gives you instructions on how to use it. And I am on the latest nightly.
[Nexus One Android Development] temasek:
Latest IR kernel no issues.
[Nexus One Android Development] schizophrenia:
i was on 7.1.0 RC1 with 20110706_0918 IR Kernel with voice search and sound recorder issue.

now reverted back to the previous version with no more issue

Temasek you have no voice search and sound recorder issues even with 20110706_0918?
[Nexus One Android Development] sietepasosalsol:
Same for me
[Nexus One Android Development] temasek:
I'll check that when I reach home. Usually I don't use voice search and sound recorder.

Edit: oh oh....same. Voice search and it reboots. Lolz

It may not be IR kernel issue. Probably not but I'll try stock cm kernel see if it reboots.

Edit: seems that stock cm kernel is ok. :(