yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] daedelus82:
I've been using this pretty solidly for around 4-5 hours now..

Every app I have works, although I have noticed a few bugs.

the HTC Desire Camera app sometimes force closes when loading

OSMonitor was initially hanging and force closing, however seems fine now

Titanium Backup force closed a couple times, but seems to be fine now

Linpack reports 17.7 MFLOPS, but the phone doesn't really feel any faster.

I guess the user experience doesn't really improve with the extra MFLOPS :p

I have had two random reboots. First time I was sending an MMS in Handcent, second time I was using xScope and run the Sunspider Benchmark. The benchmark completed but crashed shortly after.

Everything aside I'm definitely going to run it for another few days before I make any decisions.

Battery life is great, I've only lost around 10% in 4 hours. I did a complete cycle of my battery the other day and deleted the battery stats, using undervolted kernel I've been getting nearly 2 days on a single charge, this JIT mod doesn't seem to have affected this at all.
[Nexus One Android Development] Nemphys:
Been running it totally stable for a few hours with cm5.0.5.3 + oc-uv kernel...

It rocks! Cyanogen, please reconsider it for your next release ! (at least the option to enable it)
[Nexus One Android Development] DocRambone:
Wow, this this Rocks, got 870 ms at superpi :)
[Nexus One Android Development] hotweiss:
I've tested almost every single app of mine and after 8 hours of use I have no problems to report. I also down clocked my phone to 345 MHz to save on battery power. Battery life now seems to be also improved!
[Nexus One Android Development] rheza02:
Thanks for posting this, i downclock it, and run linpack, i get 6.7 mflops.

Phone slightly slow, but it is worth it, to save battery.
[Nexus One Android Development] DocRambone:
The screen and radio is the main battery eaters, underclocking will have minor impact.

Use a dark wallpaper will help more.
[Nexus One Android Development] Ivan Dimkovic:
I can confirm that the Desire ROM problems are >not< due to JIT.

Even no-JIT dalvik libraries from CM source will not work. I assume it is a library mismatch.

I guess the best way for Desire ROMs would be to wait until HTC publishes their sources and then recompile their ROM with JIT support.

I'd rather not put the "update.zip" on the first post as this is not really tested well yet, we don't want too many people complaining to the wrong person (Cyanogen) while their problems are caused by JIT
[Nexus One Android Development] denimjunkie82:
This is exciting...will be watching this thread closely. Can anyone report actual functionality improvements? It's great to have a high benchmark, but what about real-life use? When I run a live wallpaper the app drawer stutters during opening, does JIT solve that? What about anything else?
[Nexus One Android Development] hotweiss:
The best thing about JIT is that it allows you to down clock your CPU. And yes, the whole UI is smoother over all. Certain things have shown no real functional improvement, i.e. - playing XVID movies with yxflash. Give it a try, I've had no problems with it.
[Nexus One Android Development] jblazea50:
Ok I installed it last night, everything was going fine. This morning my alarm went off and then after coupler of minutes, the phone rebooted. After phone came back on, it was unable to connect to wifi. Rebooted again and wifi is back on.

Also, is it possible to run jit on enom's rom?
[Nexus One Android Development] hotweiss:
Did you wipe your dalvik cache?
[Nexus One Android Development] big_adventure:
I enabled it on my phone, running CM 5.0.5.1 with the Desire camera mod. Benchmark PI dropped to 1100ms (from 2750) and Linpack jumped to 17.4 Mflops, both at stock clocks.

Every single app I tried worked perfectly. As another poster mentioned, the Desire camera app FCs sometimes immediately when opened, but opening it again is fine.

However, I had two random reboots - once playing Robo Defense and once when the phone was sitting on the counter, untouched. So I went back to stock interpreted mode, until I have a chance to keep a logcat going until I catch a failure.
[Nexus One Android Development] jblazea50:
yeah, i had cleared the dalvik cache after i edited the build.prop to include the jit
[Nexus One Android Development] markimar:
What ever happened to dalvik turn?
[Nexus One Android Development] Worsty:
After using it for 3 hrs, this is what i observed thus far :

1) Desire camera FC-ed once on me. Nothing major, could open the app almost instantly.

2) Have issues with rebooting when i'm streaming Last.FM. Rebooted 3-4 times in 3 hrs. Again, nothing major but could be irritating having your tunes cut off.

3) Batt life not affected (in my opinion from historical usage) even when JIT is enabled.

Will do more testing on other apps extensively over the next few days.
[Nexus One Android Development] Ivan Dimkovic:
Just recompiled plain AOSP code with JIT, and tried it on MoDaCo's Desire ROM for N1

It is a bit more stable than if using libdvm.so from CM source, but it is still too unstable for anything useful - HTC Sense launcher just keeps crashing.
[Nexus One Android Development] jblazea50:
i'm having trouble running the desire camera; when i update from recovery the desire camera, i get forced closes all the time; i have flashed cyan's 5.0.5.3, then flashed desire camera, wiped dalvik yet it force closes all the time

maybe i should wipe everything and then start the process again; will try the complete wipe later in the day

EDIT: Ivan, is it possible to run jit on Enom's 1.8.1 rom?
[Nexus One Android Development] Ivan Dimkovic:
If the ROM is based on the same AOSP snapshot as Cyanogen's one, I guess there is no reason why it shouldn't work.

Now, these random reboots are exactly the problem with JIT... it appears that it is just not really stable enough.
[Nexus One Android Development] hotweiss:
I just had my first crash a after a gmail notification. I cannot wait for this to become stable. Stability is more important than speed, so I went back to stock.
[Nexus One Android Development] martin0285:
I ran JIT back in the day with BETA3 and had no significant problems during "regular" operation. Once you start pushing the envelop and actually make the phone work, reboots everytime. I would just hold off people, do we really want our phones "faster"? Will you actually notice?

Froyo is apparently god. Heard around the internet and a special private source that it will definitely be a game changer. Be patient and be happy with our 1GHz Overclocked and UnderVoltaged.

Just my .02.....We don't "need" JIT, we "want" JIT......
[Nexus One Android Development] Ivan Dimkovic:
Obviously, some people will notice.

The fact of the matter is - JIT does speed up code execution. It does not necessarily speed up the GUI, but execution of complex algorithms is, indeed, faster.

So, why not having it, then :)

I also agree that the best option is to wait for FroYo, which will probably have JIT as well. At the current stage, JIT is still not stable enough.
[Nexus One Android Development] amniberlin:
My Nexus One runs for more than 12 hours with JIT activated and I had just one reboot and one FC of Desire Camera.

I think this is not that bad :)
[Nexus One Android Development] tokyomonster:
I just saw you on reddit :P
[Nexus One Android Development] pernik:
how to disable jit after we apply it ? Could we remark dalvik.vm.execution-mode=int:jit in build.prop and reboot handset to disable it ?
[Nexus One Android Development] Ivan Dimkovic:
You can either restore the old libraries,

Or replace the build.prop line with this one:

dalvik.vm.execution-mode=int:fast

(or remove it, it looks like "fast" is the default execution model for Dalvik in CM ROMs)
[Nexus One Android Development] jroid:
using jit and oc-uv and the desire cam works fine for me.. no fc's so far
[Nexus One Android Development] pernik:
Thanks ivan, I've test it.
[Nexus One Android Development] spyz88:
I've been running it for 4 hours and havent had a single reboot. I had Appbrain crash a couple of times but I used the fix_permissions script in the terminal and all is good. Will report back again if I get a random reboot. Also, I never had a problem with JIT at all on cm5-beta3 either.
[Nexus One Android Development] martin0285:
push the phone.....
[Nexus One Android Development] spyz88:
Yup that did it. Random reboots FTW!!!
[Nexus One Android Development] irishrally:
Phone reboots after doing benchmarkpi five times in a row. I'm going to keep playing around with it though.
[Nexus One Android Development] jlevy73:
I've pushed it pretty hard and no FC's as of yet.

For those asking if this works on Enom's ROM, no it does not. I tried it and could not get it to work
[Nexus One Android Development] claritoz:
yeah got 5 random reboots while browsing the web and listening to pandora. reverted to a nandroid backup. it was fun playing with it tho! :D
[Nexus One Android Development] DocRambone:
I have bit strange behaviour; pushing the files and setting chmod by shell gives stable system ( at least for hours...) no reboots, using the update zip ( posted here ) on the same nandroid backup gives reboots within 10 min.

...??
[Nexus One Android Development] seanowns:
I used the update.zip, and after 7 hours I still have yet to see a reboot. I have not held off doing anything as of yet. Web browsing, some games, Titanium backup "backup", phone is entirely stable still.
[Nexus One Android Development] RaistlinMaje:
installed last night on a base Cyanogen 5.0.5.3 rom, runs great, linpack benchmark is getting around 17MFLOPS. I get a random restart every once in awhile but its not to bad.
[Nexus One Android Development] Ivan Dimkovic:
By the way,

If anyone is interested, here is the kernel I use. Basically it is latest Cyanogen's 5.0.5.3 source +

- Heavy undervolting (heavier than CM's or pershoot's)

- 1.1 GHz enabled

- Removed some debugging options from kernel config

- Added more code optimization compilation options (everything used in -O3 level, except forced inlining, as this breaks the compilation of some modules due to frame size overflow)

Note, it is stable with my N1's CPU, but it can be instable with other CPU samples.

You need to push bcm4329.ko to /system/lib/modules/bcm4329.ko as well

Anyway, it should be slightly faster and cooler running... but, if you are unlucky with the CPU quality, it might generate VDD errors.

@edit - included audio boost code :)
[Nexus One Android Development] hotweiss:
So do you think that Dalvik will be more stable with your kernel?
[Nexus One Android Development] Ivan Dimkovic:
Don't think so...

Instability of JIT is due to AOSP JIT code alone being not mature enough. No level of kernel tweaking would help that :( I just posted the kernel I use as I am also trying to squeeze every bit of performance :)
[Nexus One Android Development] jblazea50:
Can I install your kernel via recovery out do I need to flash zimage by fastboot then adb to push the ko file?

Also, does this include the audio boost?
[Nexus One Android Development] Ivan Dimkovic:
You will need to update it via fastboot... Sorry, I am just not comfortable with releasing such experimental things for "easy update :)

As for the audio boost - It is based on today's CM codebase... But I will check if audioboost is in.
[Nexus One Android Development] hotweiss:
Well, I like what you did with your kernel. It will be my kernel of choice now... It would be nice if you would make a separate thread just for the kernel. With this kernel, I got a Linpack score of 20.2 Mflops when overclcocked. Once again, thanks.
[Nexus One Android Development] denimjunkie82:
I just gave this a try on a fresh virgin CM5053. Everything seemed good until I flashed pershoot's latest ocuv kernel. My phone then had a very, very, very hard time finding any data network. Voice was okay but I could not locate any edge or 3G. I have the ATT version of the phone. Edge came for a little bit, and 3G for a little bit, but only once and I could not get it to come back after playing with various network settings and reboots.

Will revert back to pre-ocuv and see how it goes.
[Nexus One Android Development] hotweiss:
Why don't you try Ivan's kernel?
[Nexus One Android Development] Ivan Dimkovic:
I think before posting this in a new thread I will definitely need to do some more testing. I am new to the Android kernel tweaking so I don't wish to make something that will make things explode :)

I am rebuilding the kernel with audio tweaks now....

Also, it looks like there is a limited space for zImage - so some more aggressive optimizations might render the zImage unusable for the stock N1 phones. For example, enabling loop unrolling produces zImage of 2.5 MB, and if you try flashing this - it fails :(
[Nexus One Android Development] pershoot:
has nothing to do with the kernel. this happens with the n1 at times on first boot. wait a bit, and it will catch.

that or a flash went a miss.
[Nexus One Android Development] denimjunkie82:
will do that next :) hopefully i'll have time before my gf comes over, then i'll have to put my phone fun on pause.

Reverting back to stock CM kernel has gotten my data back.

On another note, as far as function-wise, I did notice a few improvements with my brief time with this on (keep in mind my whole ROM is still bare bones at the moment too)

- No more stutter when opening app drawer while a live wallpaper runs at the same time, including live earth (I dont have many apps installed yet, and this is my first time using CM5053 too so those might be factor as well)

- Installing apps is super fast. It was fast before, but it's like almost instant now.

- When loading the default gallery for the first time, all the thumbnails load up much faster and smoother than it did pre-JIT.

- Setting a wallpaper from the gallery is much faster than pre-JIT.

- Soft reboots are slightly faster.

I'll give it another try later. Maybe before Ivan's kernel because his "heavy" undervolting is a little scary for me right now, but I'm very familiar with your ocuv kernels.
[Nexus One Android Development] k0mpresd:
this is awesome. im getting consistent 19's on linpack and the phone is a lot snappier. thanks for the post.
[Nexus One Android Development] pershoot:
thx for this ivan.

was nice for a while, but just receieved a lockup upon first boot of flashing an update (after unlocking the screen with radio not enabling, etc.), so maybe things became misaligned, so to speak.

will wait for JIT to mature.

thx for your efforts:)
[Nexus One Android Development] jblazea50:
Ok thanks. Just wanted to make sure. Hopefully the audio boost is in it
[Nexus One Android Development] Ivan Dimkovic:
Okay audioboost is now in:

http://xdaforums.com/showpost.php?p=6012313&postcount=111

Will test this in few more days... if it is stable enough I'll definitely post it in a separate topic with update.zip
[Nexus One Android Development] jblazea50:
thanks, about to try it out

btw, you wrote "You need to push bcm4329.ko to /system/lib/modules/bcm4329.ko as well." Don't you push the bcm4329.ko to system/lib/modules/
[Nexus One Android Development] seanowns:
K testing both your kernel/JIT. All seems good thus far.

I had first freeze with JIT enabled before flashing kernel, but was in middle of a game. May have been from other circumstances.
[Nexus One Android Development] jblazea50:
Ivan, for your kernel, i noticed that when i got to SetCPU and try to change the voltage, it jumps from 883200 to 1075200Mhz without any choices in the 90s, so can you change the interval for more options in voltage selection

thanks
[Nexus One Android Development] Ivan Dimkovic:
Will try... I did enable the following voltages above 998 MHz, though:

1036800 Hz

1075200 Hz

1113600 Hz

Maybe it is the behavior of the built-in "ondemand" governor. Did you try with SetCPU's "userspace" governor?

Tomorrow, I will try to peel some more unnecessary stuff out... gotta go to sleep now :)
[Nexus One Android Development] hotweiss:
Your kernel is great, looking forward to tomorrow's update.
[Nexus One Android Development] jblazea50:
tried with "userspace" governor, but still the same; yeah, i saw the overclocking voltages and so far it works great; just wanted to have option to pick in the 90s as well

will be waiting for your next release tomorrow;

btw, the temperature is working very well, staying pretty constant at 24.5
[Nexus One Android Development] Eclair~:
I don't like asking questions because I don't like seeming stupid, and I don't like appearing as a noob. Exactly how do I edit the build.prop at the end of my system.. blah. I can do the rest of the stuff, just don't know how to do that :/
[Nexus One Android Development] jblazea50:
i edited build.prop that's in the phone already by using Root Explorer app; once you open Root Explorer, hit the Mount button on the top to R/O; then go into system folder, and you'll see build.prop, long press on it and then hit Open in Text Editer, and the text will open and you can scroll to the bottom of the page and add the line to activate jit

or

you can just extract the build.prop from cyan's 5.0.5.3 rom onto your computer and edit it, then push the build.prop to /system/build.prop
[Nexus One Android Development] hotweiss:
Probably the easiest way is to edit on your computer and then push it. You can just extract it from the ROM that youu are using.

adb remount

adb push build.prop /system/build.prop
[Nexus One Android Development] jblazea50:
JIT isn't stable, had about 3-4 reboots in the last couple of hours
[Nexus One Android Development] b1337:
Shocker!!!;)
[Nexus One Android Development] spyz88:
Hey Ivan I just want to say that your kernel run's GREAT on my Nexus, thanks. Great power savings. I removed JIT due to crashes but I'm still running your kernel. Nice work man, keep us updated ;)
[Nexus One Android Development] irishrally:
Is anyone having trouble using Google Navigation? It could not find my directions.

Do I have to flash gapps again?
[Nexus One Android Development] jlevy73:
I haven't flashed the new kernel yet so I don't know but I would think not. THe kernel shouldn't overwrite that.

Google nav works fine. So perhaps a reflash of gapps might help
[Nexus One Android Development] jlevy73:
Definitely not seeing 998mhz as an option but hardly a big deal. Your kernel is fantastic. And after running jit for almost 24 hours straight with heavy use only had one reboot while use google navigation. Also noticed that email notifications don't alway show. BUt the phone is blazing. Time to buy you a beer :)
[Nexus One Android Development] Eclair~:
Yep, this has been pretty good for me. No reboots or anything, blazing fast as said.
[Nexus One Android Development] jlevy73:
Have you gotten the Desire camera to work with this?
[Nexus One Android Development] Eclair~:
I haven't tried, but if it doesn't work for anyone else, dont think I would have any special luck..

Edit: don't know what I was taking about, it works.. Lol
[Nexus One Android Development] denimjunkie82:
I've been using jit all day now. A random reboot here and there but for the most part it feels stable. Reboots happened once when I opened the gallery app, another time while setting up setcpu, and another time exiting linpack for, and that's it. They haven't repeated.

In the other hand, the phone flies. It really is incredible. The biggest evidence of this is with the game Asphalt. Loading times are significantly shorter and menu transitions are quick and smooth, but best of all gameplay is pretty much lag free. It is very smooth and feels like how the game is meant to be played. choppiness is nearly all gone.
[Nexus One Android Development] irishrally:
I've been playing with JIT for a full day now. In general it has been fairly stable, I had a few reboots when running benchmarkpi 20 times in a row. I also had trouble with Google Navigation. I am still using Pershoot's UV/OC kernal. I will try the one in this thread now.

While I am getting crazy results on benchmark tests, I feel like scrolling between home screens, opening the app drawer and during basic use, the system is slower with JIT than with stock CM5.0.5.3 with UV/OC kernal.

My best benchmarkpi was 997ms, and 19.4MFlops on linpack.

EDIT: I tried the kernal posted in this thread and the launcher was very unstable. Sounds like others had a different experience.
[Nexus One Android Development] b1337:
desire camera works fine so far for me, uv kernel cm 5.0.5.3 , only one random reboot total with handcent
[Nexus One Android Development] leonardusjeff:
Anyone here who had enabled jit and using smartkeyboard pro ? My nexus had random reboot when I using smartkeyboard pro.. when I disabled smartkeyboard pro random reboot wasn't happened again..
[Nexus One Android Development] Worsty:
After another day's worth of testing, here's my additional observations

1) Stock Music app will stop playing music randomly. The phone doesn't reboot though, just a stop in the present track. At least once per song. (Not too pleased with this. Didn't have this issue yesterday though. Will subject it to more testing.)

2) Batt life improved by a fair % if i underclocked to 500mhz but obviously the window transistion isn't as smooth as if at 1113mhz. Desire Live wallpaper is still not running as smoothly as i like even when JIT is enabled.

3) Played Final Fantasy 5 on GameBoid for an hour, no issues with random rebooting. The frame rate is pretty good. Might be placebo effect but i reckon it's much smoother than before.

4) No random reboots when i'm in my office besides the music tracks stopping.

Using pershoot's OC-UV kernel, may try the kernel posted here tomorrow.
[Nexus One Android Development] seanowns:
Are OpenGL or Pending GL any kind of errors to worry about? Have both JIT and Ivan's Kernel enabled.

I have had relatively no issues over last 2 days with either outside of these errors.

Thx
[Nexus One Android Development] Ivan Dimkovic:
I posted the kernel in the separate thread:

http://xdaforums.com/showthread.php?t=654416

I managed to cram-in loop unrolling, by kicking out some debug options in kernel config which saved approx ~400 KB of compressed zimage. Which was just enough for loop-unrolled code.
[Nexus One Android Development] GlenH:
100% stable for me so far (5 hours, standard CM 5.0.5.3 kernal). :-)

No reboots, even when repeatedly running Linpack benchmark (although I'm only getting about 17Mflops, which is a little less than some are reporting here).
[Nexus One Android Development] Markdental:
Those that are reporting 20 are using the OC kernel. Are you as well?
[Nexus One Android Development] GlenH:
Nope, not overclocked.

p.s. Works fine with desire camera too.
[Nexus One Android Development] Gr8gorilla:
I went online with JITT at 10:15 Am today, will repost if and when I get my first crash! OC kernel from this thread highest linpack so far is 19.33!
[Nexus One Android Development] jblazea50:
so far i've had about 4-5 reboots and couple of complete freezes, which required battery pull (been on it for about 30-40hours)
[Nexus One Android Development] Gr8gorilla:
first reboot 11:15. But since then it has been ok.
[Nexus One Android Development] jlevy73:
I was using the OC/UV kernel that Ivan posted the other day (which is heavily undervolted and running at 1.1ghz) and got 20.1

However, I had to get off of it as it became unstable. Starting crashing quite a bit. Within a one hour period last night it crashed about 5 times. When it becomes more stable will definitely give it a go again
[Nexus One Android Development] rekrapg:
so far 24hrs, no crash. cm 5.0.5.3, latest UV kernal, 17.8 highest linpac - but extremely happy with speed! When cm was running JIT on his builds previously it used o crash up to 15 times a day with it enabled, so I dont know what's changed, but lovin it!
[Nexus One Android Development] jblazea50:
i think you're right about Ivan's kernel from last night is not very stable; i was using it from last night til today and had about 6 reboots with 4 of them within couple of hours

i switched to pershoot's oc-uv kernel and so far no reboots