yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] Apo11on:
@ netarchy

do you know what actually breaks the camera? Is it the overclocking/undervolting or the 30fps uncap or both?

If OC breaks the camera and fps uncap doesnt - i think many people would like to see a kernel with 60fps and fully functional cameras.
[EVO 4G Android Development] twigs187:
I've been using 3.7.8b with Baked Snack and have gotten great battery life...
[EVO 4G Android Development] smw6180:
Camera's been working fine for me aside from the 3mp glitch which was fixable by going to stock, switching to 8, then reflashing this kernel. I've read that's not working for everyone, but it seems to work for most. And I'd rather have the OC than the FPS fix, personally.
[EVO 4G Android Development] theothermillion:
The stock camera app works fine for me as well except for the 3MP glitch like everyone else but... I use Camera 360 and it crashes and gives me an error that it can't connect to the camera and that I need to adjust the settings every time I try to open it. Anyone else experience this and any ideas on how to correct it?
[EVO 4G Android Development] barnacles10:
Everything concerning the camera is functional here, as it is for many many many people.
[EVO 4G Android Development] Varo210:
Try changing your resilution in 360, and make damn sure the flash is off, or you'll never get it to run. What ever the issue is, its related to the flash and res. I'm fairly sure that Goggles is breaking due to the flash too.
[EVO 4G Android Development] EarlyMon:
netarchy, first and foremost I want to say thanks and you rock - I just began trying out the kernel last week.

Secondly - I've engaged in a discussion with a guy who claimed that his Vibrant's Tangent scores doubled merely moving the Dalvik cache to the SD card with a rooted stock kernel on his phone, no other changes. While skeptical, I am intrigued.

I googled it a little, and saw in this forum that that didn't work out so well for the Hero, as one example.

While the Hero thread mentioned that at least a class 4 SD card is required, this Vibrant guy with the ~1800 Tangent score (on a stock rooted 2.1) claimed:

Has this been tried for the EVO with a kernel such as yours?

Unless it's already known to be a non-starter, I'd be happy to give it a whack if it's not been tried. In such a case, I'd like to know if these are decent instructions for creating the ext2 partition - and is ext2+swap the right config to try with this sort of thing?

http://androidandme.com/2009/08/news/how-to-manually-partition-your-sd-card-for-android-apps2sd/

I'm using an earlier Clockworkmod Recovery rather than Amon Ra, so that's my path to an ext-type fs - and I'm more than comfy with Linux, I've been a unix guy since the '80s.

I monkeyed the script I've found into:

busybox cp -a /data/dalvik-cache /mnt/sdcard/dalvik-cache
rm -rf /data/dalvik-cache
ln -s /mnt/sdcard/dalvik-cache /data/dalvik-cache
reboot

Seemed to make sense to not bother jumping thru the sdcard softlink and just hit the mount point.

Any merit to this idea?

The only way that even begins to make sense to me personally would be if the handset maker cheaped out on the internal memory's data pathways (almost unpossible for me given that Samsung has pioneered 20 nm process memory for mobile) - or - if the memory ports for the Hummingbird are somehow so strangely parallelized so as to actually give benefit to using the SD card for that.

I'm obviously confused as to the actual memory hardware configurations supported by these modern handsets - I've only been using Android seriously since getting my EVO on 6/6 - with attempted use on a Moment before that.

So, I apologize in advance if the question itself is kinda a waste of time.

Cheers, thanks again for the naked bunny kernel - I'm holding off on mecha-bunny for now.

PS if anyone cares, I typically hit around 1300 on Tangent with the stock rooted 3.26.yadda.6 rom and the netarchy-toast 3.7.7 kernel. I know better results can be had by losing Sense, but I kinda like it so far, and if this works, it would be Snapdragon 8x50-specific and therefore of benefit with any rom.
[EVO 4G Android Development] nemesys504:
Is it possible to incorporate the network performance tweaks thats in CM-Snap v5. Heres alil description. Love your work by the way.

Additional network performance tweaks. Stock kernels do not enable any form of congestion control. v5 utilizes algorithms designed for wireless networks. You will not see overall throughput gains, but you should see a smoother overall feel in interactive applications like browsing and Facebook.
[EVO 4G Android Development] bigbiff:
I just wanted to let you guys know that if you take com.android.camera_preferences.xml from stock root and place it over you preferences file under this kernel, when you get the 3MP "issue" it reverts back to 8MP. At least for me... YMMV
[EVO 4G Android Development] Just_s:
Where is "com.android.camera_preferences.xml" located? I unzipped the OTA stock rooted ROM and can't seem to find it
[EVO 4G Android Development] bigbiff:
/data/data/com.android.camera/shared_prefs

You have to mount rw to overwrite. I used SUBFS with no problems.
[EVO 4G Android Development] Just_s:
Not familiar with SUBFS, but in lieu of that, would I:

1) revert back to stock rooted OTA rom

2) mount rw

3) pull this xml file to my sd card

4) reflash EViO

5) mount rw and overlay the pulled file from my sd?
[EVO 4G Android Development] bigbiff:
You can just flash the stock kernel for your ROM, then change the settings to 8MP in the camera app. Then copy the file to your SDCARD. Should have 8MP settings inside the xml file. Next flash back netarchy's kernel, and you should get 8MP at first. If not, copy this file over to the appropriate directory after making /system RW via adb, or favorite file manager.

It seems to revert if you go into the settings under netarchy's kernel. So I would make all changes you need under the stock kernel to get a good xml configuration file.
[EVO 4G Android Development] Doward:
This has not worked for me. I posted the camera_preferences file earlier in this thread.
[EVO 4G Android Development] bigbiff:
Not sure why it didn't work for you. It worked for me after the camera was taking 3MP pictures. All I can think of is making sure that you remounted /system read-write.
[EVO 4G Android Development] BAleR:
I am on fresh3.1. 0. 1 and flashed the fresh 3. 7. 8b and for some reason overclock widgit wont stick. I have it set to 1075mhz and checked start at boot, then hit save. But when i reboot it sits on 998mhz, untill i go back into it and reset it to 1075mhz. What gives?
[EVO 4G Android Development] Apo11on:
to you, and several those who took the liberty to reply to a question, directled at netarchy:

We have very different definitions about "functional camera" and what it means "camera is working fine". Having to see 3mp max resolution in camera settings (even though it takes 8mp pictures), missing other camera resolutions, which should be available, such as 5mp, and having many other "minor" issues, reported in this thread, such as mistimed flash, force closing camcoder, issues with 720p recording is NOT considered "fine". And it is this way "for many many people".

I've read every single post in this thread, the 3mp camera working at 8mp has been stated literally a 100 times and those who consider it fine - I'm overjoyed for you and there is no need to say it again.

Now, I'm sure all the people who want to see the camera actually working fine, as it does in official ROM, would be interested to see netarchy answering my question

:mad::mad::mad::mad::mad:
[EVO 4G Android Development] Apo11on:
I think you're missing the point of my post - it's not about personal preferences what you or I or others prefer to keep OC or fps fix - it's about what breaks the camera.

I'm saying if 1 of the 2 doesnt affect the camera, for example fps fix, many people would like to see a kernel with only 1 fix implemented, gaining fully functional camera/camcoder in the process
[EVO 4G Android Development] wfrandy:
I doubt if it is either one, I would guess that these modifications have nothing to do with how the camera works and more to do with the fact that this isn't a Froyo kernel. The problem seems to me to be that he does not have the kernel source for this version of 2.2 Froyo, so how would he know what to fix in this 2.1 kernel to get the camera working properly. After all the trouble they had getting cameras working in 2.1, it amazes me that the camera works at all.
[EVO 4G Android Development] Apo11on:
As we discussed earlier in this thread - Google has released froyo sources a while ago. The problem is that it's Android 2.2 sources, which are not device specific and do not contain Evo specific drivers. Camera and all the other drivers for Evo will come from HTC when they release the firmware sources.

To answer your question "how would he know" - the old trial & error method comes to mind. I mean, netarchy knows what was kernel change done to overclock/undervolt and he also knows what was done to remove 30fps limit. So, creating 2 kernels, one with OC and the other with fps fix and trying them out should give the answer on how they affect the camera
[EVO 4G Android Development] cjaydb:
Sprint NFL app

Hey guys, I'm new to the forums. I flashed my EVO successfully to FRESH 3.1.0.1 and everything works great except when I try to use the Sprint NFL app. I found the apk file and installed it but when it opens up, it just force closes. Someone else was having the same issue but as of this moment I don't think it's been solved or answered yet? I did a search and came up with nothing also.

If anyone could help me out I'd greatly appreciate it. Thanks!

EDIT: oops, realized wrong I posted in the wrong thread. I thought I was in the Fresh thread, did a search for the problem and I guess someone posted the same problem here and I followed suit. My bad.
[EVO 4G Android Development] Rippley05:
I'm sure some people would use a kernel that didn't OC and had a 100% working camera..or the same with one that didn't unlock FPS. I'm not sure there would be a big enough demand for it tho as everything is functional with an 8mp camera even tho it is glitched.

Really tho, it is ultimately up to netarchy to decide if he wants to create 2 more custom kernels that may or may not fix these issues...what if he does and the source gets released? Kind of a waste...

So yea, until he is on someones payroll here...it's ultimately up to him. Right now I have OC, FPS unlock and 8mp on my camera...that is completely fine for now until the source gets released. It may not be fine for everyone but if they can't create the kernel then they should really just relax a little until one is created IMO
[EVO 4G Android Development] Varo210:
Very well said!
[EVO 4G Android Development] wfrandy:
I understand what your saying but was just trying to point out that your assumption may be off, your original question was,

And all I am saying is that I doubt if either one "breaks the camera". The most likely reason the camera doesn't work is that the code to make it work properly, with The HTC Evo version of Android 2.2, was never in this 2.1 kernel to begin with. And unless someone gets lucky, with trial and error, as you said, or until HTC releases the kernel source for 2.2, I doubt if an easy fix is possible.
[EVO 4G Android Development] Apo11on:
The disclaimer in the first post says:

"3.7.x Froyoized netarchy-toastmod kernels are very experimental. They are 2.6.29 based kernels

being made to work on a version of android designed for 2.6.32."

Therefore I dont think your assumption these froyo OC kernels netarchy is baking are based of 2.1 is correct. 2.1 kernels are 1.47.XX.

However, unfortunately for us, you most likely have a valid point there - if I remember correctly this 2.6.29 kernel was ripped from another device, which obviously has different cameras.
[EVO 4G Android Development] finsmaniac02:
I think someone mentioned this in here but said "oops wrong thread" lol... but maybe its not the wrong thread.

Does anyone in here have Sprint NFL app working on their phone after doing this kernel? If the answer is YES, then I am very sorry for wasting your time lol.

I am on Baked Snacks 1.2.5 and no one on there has ever talked about Sprint NFL not working, but that rom doesn't come with the newest version of this kernel. Therefore since no one has talked about it there, and a major deviation I have from "stock" baked snacks rom is this kernel, I figured I would ask.

Thank you so much for any responses!
[EVO 4G Android Development] :
So when will the Japanese finish Bunnytron? I'm looking forward to seeing it in action. ;)

~Jasecloud4
[EVO 4G Android Development] tpeazy:
Here is a question for the group. Has anyone tried backing up their camera using Titanium Backup and then flashed netarchy's kernel and then restored the camera using TI? I will try this and see if I keep the 8MP.

Tp
[EVO 4G Android Development] Yager:
Market download Issues

I am having a issue with the Fresh 3.1.01 and netarch3.7.8b and the market.

I reparation the SD card with RA and install Fresh. Everything works fine (including the market), I then restart and install netarch3.7.8b and it works great for OC and FPS. I go to the market to download any app, the market starts the download does nothing for about 30 seconds and then says download unsuccessful. The data connection works fine in everything else(browser, games, FB, etc)

I am sorry if this has been asked before i have down multiple searches for any combination of "download, unsuccessful, not working, etc)

Thanks ahead of time for any help!

Update: I have tried clearing the data and cache under the settings/applications/ that did not seem to fix it.
[EVO 4G Android Development] korrin84:
which one?

Sorry to ask something that I'm sure has been answered several times already but...

Which version of this kernel is the most current? / Which one should I use?

Currently I am running Fresh 3.1 with updated radio and wimax, and what I assume is the stock kernel.

Revision 3.7.8b - Froyoized

Revision 3.7.8b - Froyoized - Fresh3 Compatible

Revision 3.7.8b - Froyoized - Damage Control 3.5 Compatible (Remember DC users, if you use the battery saver configurations in dconfig, it will impact your framerates as a tradeoff for saving more battery)

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

Revision 3.7.8 - Froyoized

Revision 3.7.8 - Froyoized - Fresh3 Compatible

Revision 3.7.8 - Froyoized - Damage Control 3.5 Compatible

Revision 3.7.7 - Froyoized

Revision 3.7.7 - Froyoized - Fresh 3 compatible package

Revision 3.7.6c - Froyoized Note: In the rush to get this release out, I forgot to update the version it reports, so it will show up as 3.7.6b #8 ;D
[EVO 4G Android Development] bluefire808:
I know you get all kinds of people requesting all sorts of things for free. Netarchy if you could just add a higher clock speed to the 7.8b i would pay you for it. I know most phones cant oc over 1151 very often but when using other kernels ( not ones i like however ) i can oc in the 1.2 mhz area. Pm me and i pay paypal money and you could e-mail me the rom... idk just thought id ask. Mahalo!
[EVO 4G Android Development] bwtl1000r:
How about 3.7.8b for fresh... I think it's the obvious answer
[EVO 4G Android Development] korrin84:
I'm also wondering if the kernel doesn't work well for me or I don't like it, How do I revert back to the stock kernel?
[EVO 4G Android Development] infamousjax:
Are you illiterate or just lazy? Everything you've asked is in the OP.
[EVO 4G Android Development] Apo11on:
any supporting evidence to back up this claim? I believe it's incorrect - based on user responses in evo overclocking threads (this one and others) only certain number of people cant overclock to 1.2Ghz or higher, I think it does work for most

+1 to the request for higher OC kernel
[EVO 4G Android Development] korrin84:
Theres no need to be a prick about it! I have done several searches and quite a bit of reading, and have not been able to find the answer. That's why I asked. (forgive med fort not reading a few hundred pages to find the answer) Jackass.

Still searching for an answer if anyone else can be of assistance. Thanks.

And anyone with smartass comments please just keep them to yourselves. Thanks.
[EVO 4G Android Development] rain91:
All the info you need is in the first post.
[EVO 4G Android Development] korrin84:
So I can just re flash the stock kernel over the netarchy/toastmod to revert?
[EVO 4G Android Development] infamousjax:
Maybe you shouldn't be such a douche and read the FIRST POST.

Good day citizen.
[EVO 4G Android Development] korrin84:
Actually that's exactly what I did. Thats why I knew I could revert back to stock. I am however fairly new to rom flashing,etc. That's why if you look at my question I asked HOW to revert to the stock kernel. I didn't ask IF I could, or WHERE to get the kernel. I asked HOW!

And now I say good day to you too.
[EVO 4G Android Development] felacio:
Not to sound like a **** or anything.... but...

how did you flash Netarchy's ROM?

Ok, now.. do that with the HTCKernel.

that's all there is to it..... :rolleyes:
[EVO 4G Android Development] Biofall:
So I'm about to buy SetCpu, but I was wondering about a couple of things. What limits the CPU, the kernal or the ROM? Also, where can I go to see what numbers work for certain ROMs? I will most likely always be using Fresh so I guess I'm asking what works for Fresh with net's newest Fresh kernal.

Thanks for any legitimate responses, and I'm sorry to everyone who I may have possible offended somehow with my post (Someone always gets mad n_n )
[EVO 4G Android Development] felacio:
You can actually get it free here in the forums, legit even. I bought anyways to support the cause.. ya know? lol.

The kernel sets the limits for the most part. Hero's Kernels for BakedSnack are undervolted, which can cause issue at higher clock speeds. While Netarchy's kernels are slightly less undervolted, so they handle the higher speeds. both are set speeds within the kernel to safe guard accidentally pushing the CPU too far and breaking something. the HTC kernel is locked at it's default and can't be overclocked. in 2.1 it could be underclocked, as of 2.2, SetCPU can't do anything with the default kernel. you have to use Baked or Netarchy... or another custom ROM.

I think CM6 Snap can go up higher than both of them.. I haven't tried it though. But wth 3.7.8b you should hit it's limit at 1150 with no problem.
[EVO 4G Android Development] bluefire808:
Uh crap i didnt mean to say my phone cant over clock to 1152 i ment it can. I have had it up to almost 1.2 mhz. Sorry that didnt make sense before. Thats why i wanted this kernel to be able to clock higher. Id still pay for it
[EVO 4G Android Development] bkofman:
akmd draining battery

I'm seeing akmd constantly using 1-3% of the CPU, according to OSMonitor. I killed it by turning off "Auto-rotate screen" and the battery life improved noticeably. Is anyone else seeing the same with this kernel? It's possible I just didn't notice it with the older kernel...
[EVO 4G Android Development] zone23:
Thats great except photo gallery wont rotate.
[EVO 4G Android Development] halmo20:
720p Video

I'm on 3.7.8b and 720p video option is gone still. I'm on caulk's EViO 2.2... could this be the rom. Netarchy said 3.7.8b had 720p video fix but still no go for me....
[EVO 4G Android Development] masbirdies:
Since flashing the latest kernel....

I've jumped in Fps2d STDEV marks from low to mid 6 all the way up to over 10. Is there a way to control this?
[EVO 4G Android Development] RTC88:
You could try using evoswitch. That seems to work for me.
[EVO 4G Android Development] Biofall:
Thanks for the nice, educated response. I really appreciate it. Us there any way someone could post a link to the free setcpu- and will the fee one accept market updates?
[EVO 4G Android Development] meatgel:
I'm using that ROM and this kernel and I DO have the 720p video option, so I don't know why you are missing that setting. Maybe something else you installed?
[EVO 4G Android Development] halmo20:
Nothing unusual I can think of.... I may try wipe abd reinstall.
[EVO 4G Android Development] finsmaniac02:
here is the thread for SetCPU.

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

To my knowledge The APKs there are the same version that you would have to pay for on the market. Unfortunately you cannot update from the market and need to keep checking for an update on that thread.
[EVO 4G Android Development] yubby:
Anyway to get HDMI fixed?
[EVO 4G Android Development] Biofall:
Thanks so much. I'm very intimidated by all the settings, I kind of need some sort of tutorial lol
[EVO 4G Android Development] Estimated Prophet:
Okay, so the camera will take 8MP pics even though it says 3MP... at first. If you change the resolution at all, you can't go back to 8 since it's not an available option and if you select 3 then your pictures will all be 3MP. Anybody know of a way to go back? Config file somewhere I can edit?
[EVO 4G Android Development] masbirdies:
Where do I find it?

Search is not bringing it up.
[EVO 4G Android Development] TERmp77:
Sorry for the quick hijack....

It is called Sprint Football Live now, and I have it working. It is actually a hell of a lot better than it was before. It has Pro and college, odds, fantasy, twitter, and alot more. The version I have on my phone is 2.2.32

I had to install the Sprint NFL apk, then it asked me if I wanted to update. Or go here
[EVO 4G Android Development] davebu:
Confirmed 8MP works in Camera 360, just tested it. It does not work in FX Zoom. Though we got 8MP in it, note that flash does not work in Camera 360. It wont open if you turn your LED on before launching the app and when turning flash or autoflash on it will turn your camera off.
[EVO 4G Android Development] Biofall:
I read all the SetCPU pages, so I think I understand everything, I just got all my profiles set up. So I was in the process of calibrating my battery. I charged it all the way, powered off, wiped battery stats, turned on, unplugged, and let die. (Took 18 hours) Then just now when I plugged it in and turned it on, it had 18 percent battery.. Is that because setCPU affected the predicted battery levels or something?
[EVO 4G Android Development] daving313:
Anyone having partial wake issues on 3.7.8.b? I am running rooted stock froyo .6. I have tested against stock kernel as well. After 10 hours of boot I am about an hour of partial wake due to "Android". When I run stock kernel, I get little to no partial wake at all. Only reason I noticed is the battery seemed a bit more hungry for a sip than on stock. I don't remember that from a few revisions back.

I don't run any task killing or over/under clocking. No random app installs either.
[EVO 4G Android Development] unvivid:
Any chance of an updated tun.ko for the latest 2.2 version?
[EVO 4G Android Development] JackDaniels7:
the source is out if he is on maybe he will whip up a batch of OCed froyo kernel tonight
[EVO 4G Android Development] Vandam500:
Now that HTC released the Froyo Kernel Source this kernel is gonna be epic again :)
[EVO 4G Android Development] PlankLongBeard:
+1 on this.. netarchy please please create wonders with rabid baby bunnies.

Sent From Your Grandmothers HTC Evo via Telepathic 4G
[EVO 4G Android Development] rjmjr69:
OMG I Would kill for a new kernal

To go with my new UNREvOkOKED FOREVER
[EVO 4G Android Development] JackDaniels7:
the only reason i am interested in unrevoked forever is cause it may give me full updates that i can apply engboot and roms over
[EVO 4G Android Development] zone23:
Were is Bunnytron when you need him?? Can't wait to get my 54fps HDMI and OC on the FroYo 2.2 its gonna be sweet. I see a donation in a certain members future.
[EVO 4G Android Development] zone23:
Wait before everyone gets all up in arms over the new unrevoked. Who sad that there would be any more updates anyway? Think about it for a second we are on 2.2 why would HTC/Sprint release anymore updates? I personally don't think they will.

And this is with wrong thread for unrevoked talk. I will take the rest of this over to the proper thread.