Database Info

[ROM][6.35] Sanpei's HERO Sense, OCed version/almost everything like HTC official ROM

FOR 32A, RADIO 6.35 and SPL 1.76
this port only have very little modification from original official ROM, some kernel driver tweaks, camera libs replacement, our bt firmware, sensors files and root.
first boot could be not very smooth. screen may go blank, if you would encounter this problem, just wait for a while, and press some keys. when you make all your settings done, a reboot is highly recommended. I have used it daily now.
download:
latest update [Jun 26]::
OC: http://forum.xda-developers.com/attachment.php?attachmentid=349885&d=1277499752
non-OC: http://forum.xda-developers.com/attachment.php?attachmentid=350638&d=1277631885 , under testing, plz report bugs.
changes:
HTC's battery driver
a new driver extension to support default USB netshare *
a newer sanpei helper which is reimplement **
non-OC version: screen on 528/352, screen off 240/176 ***
OC version: screen on 576/384, screen off 245/176 (4.0 in Linpack with JIT)
other fixes, many error reports in aosp kernel (which version > 2.6.29) have gone, we have a clean dmesg now
ROM itself:
apply update after you flash the ROM:
http://www.4shared.com/file/XHlI-Kdl/3pei_hero_21_alpha.html
mirror: http://www.multiupload.com/RRWFEYLPP1 , by malachaskos, thank you
wipe and flash in recovery, and you should delete the generated files (by android) in your sd card.
please make sure that you have installed driver properly. a little more details: http://forum.xda-developers.com/showpost.php?p=6180261&postcount=986
addition:
for JIT, download this: http://forum.xda-developers.com/attachment.php?attachmentid=345213&stc=1&d=1276842897
you have to set your Home Wallpaper and Lockscreen Wallpaper to something on sdcard before the first boot with JIT enabled, (and you can set them back after that: I have tried other HTC wallpapers except default). the workaround is found by klothius, thx .
if you encountered any trouble, and want it disabled, flash this: http://forum.xda-developers.com/attachment.php?attachmentid=345214&stc=1&d=1276842897
for Gallery3D, download this version: http://forum.xda-developers.com/attachment.php?attachmentid=338391&d=1275828997 , it could work with HTC Camera app in most HTC's ROM.
known issues and workaround:
keyboard light and some other led features : flash update plz
gps may need to boot with gps setting on, or you could try capychimp's gps files
official USB netsharing: flash update plz
if you find infinite logs about database queries which are generated by bt components, what I know is a reboot, or kill the bluetooth process
APN list shows nothing (unless your mobile operator is Chungwa in Taiwan), plz manually add your APN
* it could work under windows, but you must enable netshare in settings, and not in notification area. and you must disable netshare in settings if you want to use DiskDrive.
plz don't turn mobile network setting off when wifi is on. HTC's software will disable netsharing and uninstall the driver when you turn off mobile network.
** dev could set the button led timeout now.
just setprop sanpei.buttonlight.delay 20 (in sec) when phone is running, or set it in build.prop. plz report any issues.
*** I don't test the non-OC version myself yet, if you encountered any problem plz tell me, since it have lower frequency when you don't touch the phone.
and if the screen doesn't turn on during boot with OC version, plz press red button to close screen then press any other button to active the screen.
this issues happened once when first time I used this ROM after it was ported, though we don't have a kernel OCed that time. so I had said "first boot could be not very smooth" before. now I found that with higher CPU freq, it will happen more frequently.
so I won't support higher frequency at current. they are not so stable as I considered before. maybe you think that we could boot it with a lower frequency then use higher after boot. but I think if it have troubles when booting, it will have more troubles in heavily usage.
old changes:
some new commits to aosp kernel are included
qdsp driver changed to htc 2.6.29 version with some hacks
other little tweaks, not very important
for developers, many modules are included, you could check the modules folder. but I don't enable things like compcache by default. OC is not included, my phone is heated and I don't want to take a risk before I could have time to verify it carefully.
HTC Sync will work with with version 2.0.25, you can find it here (thank paultoan): http://www.htc.com/us/support/magic-rogers/downloads/ .
other pure ports:
you can find them here: http://forum.xda-developers.com/showthread.php?t=642125 .
legend port is a bit slow, but it have more features: the new way of select text、copy、wiki、translate and dictionary, etc.eris port may be faster then this one, and has been tested for a long time, but with old looks.
could someone test for us, if the new kernel binary and boot.img (in update.zip) could work with legend/eris ports? then we could use it to upgrade these ports too.

sanpei,好久不见啊，这个是基于昨天hero官方发布2.1移植的版本吗？

wuguohui109 said:
sanpei,好久不见啊，这个是基于昨天hero官方发布2.1移植的版本吗？
Click to expand...
Click to collapse
是。在这最好说英文，不然版主说不定对咱们有意见了...
yes, please write in English here, otherwise moderator may have some thoughts...

ok，Download now，thanks，haha

Can You check what languages does it have?

i think both “繁体中文&english”，thats all

sanpei how about rc e100 ? does it work?

Welcome back Sanpei!

Great thanks to sanpei

thanks
Bug ：
Footprints cam Preview no work (photo OK after shooting)
edit---
First Preview rotating, right and bottom Flicker
Second Preview rotating

looking forward to a more stable version

Nice to see you back sanpei.
Would there be any point in trying to throw your new kernel build into one of the older roms (like the legend or eris)?

@Sanpei
are you using your own kernel? cause i think bluetooth drain battery issue still exists on this rom

account1 said:
@Sanpei
are you using your own kernel? cause i think bluetooth drain battery issue still exists on this rom
Click to expand...
Click to collapse
you should turn off bt after using it. a component of bt will prevent the phone going to sleep when bt is turned on. I will try to find a solution when I have time.
I don't want to use HTC's kernel. because they have some other bugs too. fixing bugs in HTC's kernel is less valuable than our current way. and you know, maybe we should try android 2.2 later.
so we must stay at aosp kernel and adapt it to run both AOSP and HTC's ROM. and I think these jobs could be done. all the problems are just time, time and time.
btw, it's not "my own kernel", it is the aosp kernel, I just did some repairing for our purpose
and to others:
sorry, I couldn't do works which would take a lot of time at current. but I won't stop.

sanpei, there's an ongoing effort on porting the 2.6.33 kernel to the new radio, with some work already done. Maybe you could give some help to the people doing that job

sanpei said:
you should turn off bt after using it. a component of bt will prevent the phone going to sleep when bt is turned on. I will try to find a solution when I have time.
I don't want to use HTC's kernel. because they have some other bugs too. fixing bugs in HTC's kernel is less valuable than our current way. and you know, maybe we should try android 2.2 later.
so we must stay at aosp kernel and adapt it to run both AOSP and HTC's ROM. and I think these jobs could be done. all the problems are just time, time and time.
btw, it's not "my own kernel", it is the aosp kernel, I just did some repairing for our purpose
and to others:
sorry, I couldn't do works which would take a lot of time at current. but I won't stop.
Click to expand...
Click to collapse
we thank you all for your effort Sanpei
but by saying "turn off bluetooth after using it" makes me quit of trying all those custom roms with this particular kernel
bluetooth, its a feature i use all the time, every day, so i personally quit flashing until problem is solved
again, thank you for your great work here

Re: [ROM][6.35] a very pure HERO 2.1, new look and eris ...
Sanpei, can we use the cpu clock on some later phase of your rom/kernel ?
-------------------------------------
Sent via the XDA Tapatalk App

helderp said:
sanpei, there's an ongoing effort on porting the 2.6.33 kernel to the new radio, with some work already done. Maybe you could give some help to the people doing that job
Click to expand...
Click to collapse
.33 is a experimental project by Google, and our device won't get benefits from the increased digit. I will only work on kernels which will be chosen by Google and other manufacturers. and sadly, for some nonsense reason, I and some people couldn't work together.
account1 said:
we thank you all for your effort Sanpei
but by saying "turn off bluetooth after using it" makes me quit of trying all those custom roms with this particular kernel
bluetooth, its a feature i use all the time, every day, so i personally quit flashing until problem is solved
again, thank you for your great work here
Click to expand...
Click to collapse
i am really sorry for that. when I was fixing the battery drains, I don't know much about the right behaviors that bt features should have. so I just leave the prevent-sleep mechanism there because I think it is necessary.
and now I don't have enough time as before. but from you and others, I know what the right behaviors are. I will try to fix it in next release, for people who use bt heavily.

Bladyle said:
Sanpei, can we use the cpu clock on some later phase of your rom/kernel ?
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
yes (we should make more things could be controlled by users in the long run), but not now.
we still have some issues that are important to other users, though personally, I don't use those features heavily.
my order:
1. lights in Sense ROM for other devices and battery drains when bt is on
2. android 2.2 or big improvements in android 2.2 (port them to daily usable ROM)
3. default USB netsharing, netsharing under windows and other features like this
4. other hardware supports and features like CPU freq control.
5. some hidden bugs in aosp sources or htc drivers we used (though they don't affect anything in most cases)
hope I could get enough time end of this month and next month, then I could repair/add one or two of them.

I only referenced the .33 kernel since that's what's used on cyanogen 5 series mod, and if it could be adapted to the new radio it would be a good way for us to have CM5 with the modifications cyanogen and otheres sometimes do to the kernel. Just my 2 cents

[KERNEL] GoDm0dE-2.6.38.8 [ZOMFG A ZIP THAT FLASHES]

BACK FROM THE DEAD​
This kernel is intended to be stable yet fast. has many goods (OC UV ect.) but yet its main goal is to be stable. THIS KERNEL IS INTENDED FOR USE ON CYANOGENMOD (but if u would like to try on other aosp roms feel free)
i decided to bump my old thread to give testers a place to discuss the kernel and point out possible issues. before its moved into CyanogenMod.
u can get the kernel via Kernel Manager in the android market.
direct link: http://kernels.teamw.in/files.php?fid=565&kid=237
all source can be found on my link in my signature.
thanx for the support and please leave feedback
as of v9:
-edid code and hdmi driver bug fixes
-bump minor version
-config changes
as of v8:
revert edid code that borked audio in HDMI
as of v7:
minor version change, staying up to date with linux stable release
as of v6:
minor version change, keepin us up tEh date
as of v5:
-updated minor version to .5
-misc other changes
as of v4:
-fixed issue in atmel touch driver
-updated usb gadget driver
-add platform data for USB accessory function
-update config
as of v3:
-updated EDID code via tEh #teamwin
-changed config
-fixed light sensor
known issues:
-hdmi audio out not working
-possible bug switching cams (needs tetsing and debugging works for some while some seem to have issues)
faq:
q: does this kernel have SBC?
a: no
q: will this kernel ever have SBC?
a: no
q: kernel manager gives error when updating, what do i do?
a: make sure you have the latest version of the app. if you do, clear the app data and try again
q: after flashing the ladies look at me more, how do i make it stop?
a: flash another kernel
q: can i discuss other kernels in this thread?
a: no... post only posts that are on the topic of this kernel.
q: i cant feel my legs, any way to fix?
a: get off the toilet and stand up naowz
q: what is GoDm0dE?
a: http://forum.xda-developers.com/showpost.php?p=13405012&postcount=204

Awesome! can't wait to try this

we can just flash on top of Fresh right?

want to install now!

guys, it's a source, not a flashable kernel yet. it's for other people to make changes to and improve on at the moment.

justinisyoung said:
guys, it's a source, not a flashable kernel yet. it's for other people to make changes to and improve on at the moment.
Click to expand...
Click to collapse
that's what I thought, but was making sure... thanks

Could we please have epson panel fix (30 fps, touch lag) implemented asap?
Thanks.

great love to see community kernel.
going to be forking soon

TrevE said:
great love to see community kernel.
going to be forking soon
Click to expand...
Click to collapse
thats the spirit welcome aboard lol
once first commit finishes, ill start doing the normal magic. OC,compcacheaand such. ill prolly fork for BFS for now. im gonna try and forward port to .34 here in a bit once i get some of this up
ps first commit is up finally. pull away

yeah prolly best to keep bfs sepearate havent played yet myself but from pokin around on n1 boards read its not too stable but like i said havent touched it myslef.
29 - 34 shoudlnt be too bad, not like 27 - 29 :|
just finishin up a movie then ill fork away thanks ofr getting this goin toast id love to see 1 community kernel instead of 3029849203842093 like the n1 has

TrevE said:
yeah prolly best to keep bfs sepearate havent played yet myself but from pokin around on n1 boards read its not too stable but like i said havent touched it myslef.
29 - 34 shoudlnt be too bad, not like 27 - 29 :|
just finishin up a movie then ill fork away thanks ofr getting this goin toast id love to see 1 community kernel instead of 3029849203842093 like the n1 has
Click to expand...
Click to collapse
Any forking in the movie you are watching? haha -

instead of BFS di like to try playing around with this
http://lwn.net/Articles/352889/
> [...]
> # echo NO_NEW_FAIR_SLEEPERS> /debug/sched_features
>
> Btw., NO_NEW_FAIR_SLEEPERS is something that will turn the scheduler
> into a more classic fair scheduler (like BFS is too).
Click to expand...
Click to collapse
>> (mainline)
>> Averages:
>> ------------------------------
>> Max 50 usec
>> Avg 12 usec
>> Stdev 3 usec
>>
>>
>> (BFS)
>> Averages:
>> ------------------------------
>> Max 474 usec
>> Avg 11 usec
>> Stdev 16 usec
Click to expand...
Click to collapse
In fact, I liked this setting so much that I went to
kernel/sched_features.h of kernel 2.6.30.5 (the kernel I use normally right
now) and set SCHED_FEAT(NEW_FAIR_SLEEPERS, 0) (default is 1) with
absolutely no other tweaks (like sched_latency_ns,
sched_wakeup_granularity_ns, etc.). It pretty much behaves like BFS now
from an interactivity point of view. But I've used it only for about an
hour or so, so I don't know if any ill effects will appear later on.
Click to expand...
Click to collapse
just need to get debugfs enabled.
and no no forking in the movie pandorum on netflix

TrevE said:
instead of BFS di like to try playing around with cfs
http://lwn.net/Articles/352889/
and no no forking in the movie pandorum on netflix
Click to expand...
Click to collapse
may be promising. i did some work with Con the creator of BFS on the HeroC had him look over my dirty backport to .27 and then used his suggestions on my .29 heroC port. i only had like one or two issues that came about from BFS in the end. mostly app related at that. i really never had time to look further into the issues because of other projects and the awesome sauce EVO's arrival. but yeah im gonna go with a fork and work out the bugs. i like the idea behind BFS and feel its best suited for devices like ours. that said... .34 has a major CFS overhaul, which many have said fixes a lot of issues CFS had in previous kernel versions. so getting to .34 and playing around i guess is the goal i have ATM.
ps. look at this lol
http://pastebin.com/h7TQiv5a
htc is some dirty coders lol

probably not the place to ask, but what the heck..
does anyone have any idea why touch input is broken on froyo when using this kernel?

ffolkes said:
probably not the place to ask, but what the heck..
does anyone have any idea why touch input is broken on froyo when using this kernel?
Click to expand...
Click to collapse
oh do i need to fix that? htc prolly destroyed it again. i can look at it here in a bit. i bet i know the issue.

A proper backport of BFS and i really want to test SIO I think the results will be very good.

toastcfh said:
oh do i need to fix that? htc prolly destroyed it again. i can look at it here in a bit. i bet i know the issue.
Click to expand...
Click to collapse
awesome!

What's BFS? I remember always hearing about it on the HTC dream boards but never came across an actual explanation to what it actually is/does

madunix said:
What's BFS? I remember always hearing about it on the HTC dream boards but never came across an actual explanation to what it actually is/does
Click to expand...
Click to collapse
Brain **** Scheduler

madunix said:
What's BFS? I remember always hearing about it on the HTC dream boards but never came across an actual explanation to what it actually is/does
Click to expand...
Click to collapse
It's the Brain F**k Scheduler
http://en.wikipedia.org/wiki/Brain_Fuck_Scheduler

[ROM-FroYo AOSP] FroYo-Desire 0.4b[FRF91] WIFI SLEEP | LED | UV-KERNEL

Hi everyone
I've managed to get a fairly good working build now of FRF91 from AOSP. I was inspired mainly by both AdamG and meLIanTQ for there excellent work on both there AOSP built ROM's, so thought I'd have a go at it myself, so here is the result
I'm building this ROM to suit my own personal needs, with various little things thrown in for good measure, but it will remain 100% AOSP source. No APK's will be modified *after* the build, all customisation on my part will be done via the overlay.
THIS IS NOT A SENSE-BASED ROM
ROM Details
Built from latest AOSP source. (FRF-91 2.2-r1.1)
2.1Mb Kernel Image Size so hopefully no problems for people with Bad Blocks
Kernel Base - 2.6.32.9 configured and compiled by myself (UV Support, no OC)
Self-modded Kernel Fix to keep phone charged at 100% while plugged in (used to drop to 89% and charge) (details >here<)
ext2, ext3 and ext4 support
cifs.ko, tun.ko and openvpn
Classic A2SD+ from my original dalvik-cache mod from Rooted 2.1 Eclair for Desire (details >here<) Copies Apps, App-Private and Dalvik-Cache to SD.
A2SD Fixed to help prevent White Screen Hangs (working with ext2 and ext3 partitions, needs testing with ext4)
Latest BusyBox (1.16.2)
Rooted with latest SuperUser 2.2 apk
Massive APN List
h264 Camcorder
Latest FRF91 Google Apps
3G/H Icon Fix to display H during HSDPA connection.
Default Launcher is LauncherPro Beta
WaveSecure installed to /system/app
setcpu.txt copied to sdcard JUST incase you want to use SetCPU to ramp down the CPU Speeds to help conserve battery life (remember, no OC or UV support in kernel, but I do intend to patch UV support in future releases)
The following items have also been removed:
Facebook (Installable from Market)
Twitter (Installable from Market)
Original Android Launcher
Amazon MP3 (Installable from Market)
Whats Working (currently from what I can tell as its what I use)
Facebook Sync (including profile pictures displaying in Phone App and Message App)
WiFi
USB & WiFi Teather
Notification LED's
Camera
NO ECHO
I've also not included items such as SpareParts, or LeoParts... SpareParts and LeoParts can be had from the Market.
Please refer to the 2nd post for a breakdown of changes/fixes/known issues with the ROM
Installation
Fresh Install
I recommend you do a FULL WIPE before you install this ROM if you are coming from another ROM.
Future Upgrades
No wipe is explicitly required in order to use this ROM, however if you do encounter issues of any kind, it is recommended that you wipe your device and reproduce the issue before raising it here.
Just to say. Whenever I release a new Update, I always just "flash over" the existing one without a Wipe and go from there. I'm building each release with this ethos in mind, as its pretty annoying having to do a Wipe on each update!
DOWNLOAD
YOU WILL NEED THE 5.xx RADIO ROM FLASHED TO USE THIS ROM - 4.xx RADIOS ARE NOT, AND WILL NOT BE SUPPORTED SORRY!!
Get the latest RADIO's >HERE<
Also, remember this is a ROM I'm making for myself and a few friends, so I will try to sort out bugs as-and-when they are found, but as I'm still learning how to do this well, it may take a little time for me to sort!
Also during the FIRST initial boot after a fresh install, it can take about 30 seconds for LauncherPro to start responding. THIS IS NORMAL. Any further reboots by yourself, or upgrades in future (without wipes) don't have this issue.
FroYo-Desire 0.4b
Thanks & Credits
st0kes for all the info and tips in the Building Android from AOSP thread.
deovferreira/Kali- for the vendors which make all of this possible.
meLIanTQ for the invaluable help when I ran into a few issues during my initial build
AdamG & meLIanTQ for there inspiration
IntersectRaven for his HAVS Kernel Modifications
Anyone and everyone else who I've forgot to mention
Want to buy me a Toastie?? Can if you want But I'm not in it for the food

Future Additions
Add support to dynamically check and change the keys binded for unlocking the phone
Current Known Issues
Auto Brightness may not be to everyones taste.
Version History & Changelog
0.4b
Kernel UV Values tweaked to 925mV min, 1225mV max.
Conservative Power Governor now set on boot. (can be changed using SetCPU)
Updated LauncherPro to latest release
0.4a
Removed HAVS Additions from Kernel - caused problems with Trackpad & Light Sensor (CM3602).
New Kernel UV-Only based on Pershoots N1 Modifications. 950mV - 1275mV (for stability)
0.4
Recompiled Kernel with HAVS Support (925mV MIN, 1250mV MAX) - Credit >IntersectRaven<
0.3
Added SIM Toolkit
Final 100% Battery Charging Modification in place (keeps battery at 100% while plugged in)
WiFi Sleep now fixed (using own method based loosely on the official Google patch)
WiFi Sleep also fixed in respect to extremely high pings and regular dropped packets still compared to being in a Woken state (pings and packet consistency will remain constant regardless of screen being on or off)
AutoBrightness now set back to original FroYo values. Sense values used in 0.2 were draining the battery and keeping the screen far too bright in dark conditions.
0.2
Re-synced against latest AOSP Release & Kernel_MSM
Further-optimised Charging functions in Kernel
Fixed button backlight (full brightness)
Fixed Notification LED
Fixed Auto-Brightness
0.1b
Re-compiled Kernel enabling "Conservative" mode for (hopefully) better battery saving! (use SetCPU to enable this)
Added fixes to try get 3G working on Orange networks (for those who are fully unlocked with latest Radio's ONLY)
Corrected the order at which kernel modules load. Also sorted out module issue with FileSystem modules loading in the proper order.
No longer clear Vendor cache from Market (causes slowdown on initial use after flashing as upgrade)
0.1a
Initial Public Release
0.1-prerelease
First Initial Build
Fixed LED's
Added Camera Profiles
Fixed Facebook Sync
Fixed Teather

i dont suppose you can tell me where i can get the kernel fix that stops the battery from draining while charging? that is a HUGE problem for me
i will flash your ROM asap but i dont have enough time atm
thanks very much for your ROM looks really good

cgrec92 said:
i dont suppose you can tell me where i can get the kernel fix that stops the battery from draining while charging? that is a HUGE problem for me
i will flash your ROM asap but i dont have enough time atm
thanks very much for your ROM looks really good
Click to expand...
Click to collapse
Updated first post with a link to the modified source file

You sir are an absolute saint
Thanks so so much
5 STARS!

very very nice work.. good job.. i love AOSP rom.. i'll try it tomorrow.. one question. the biggest problem is wifi on OD and AOSPDesire (sleep mode). wifi is working on this rom when goes to sleep? Thanks

How would we go about manually installing the kernel fix? do we flash it?
Thanks again and sorry for my ignorance

cenkaan - What exactly is the WiFi sleep problem? I go into Settings -> Wireless & Networks -> Wi-Fi Settings.
Press Menu key, choose Advanced
Set Wi-Fi sleep policy to Never... Doesn't disconnect for me, but it does run in a low-power mode.
I've noticed using something like SpareParts, has *no* effect on this setting what-so-ever. It only works for me by doing it this way.
cgrec92 - thats the source file for the battery driver which must be compiled in with the kernel from source. As far as I know, the boot.img (my kernel) is compatible with OpenDesire (used it on there myself). It is already included in DeFrost, AOSPDesire, and I think AdamG might be adding it to his future updates as he did ask me where he could obtain the mod

i use wifi policy and set to never but this is not solution for me on other AOSP mods. Thanks for the quick reply

Well I've had the desire running all night and it kept its connection But if it is an issue, please let me know what you do for the issue to show (any other apps used to manage it) and I'll see what I can do

can't wait and i'll try it now

Last question I promise
So the boot.img contains the kernel (you have modified this)
I can use your boot.img on other ROMs such as AdamG's seeing that yours is based on this?

no it's not working...full wipe and later set to never but it's not working..
-sleep mode-
Destination address 192.168.1.86
Packets sent 10
Packets received 0
Average round-trip time 0.000 ms
in the meantime rom is very nice. great job.. Pls help me.. I want to use this rom. i loved it

cgrec92 said:
Last question I promise
So the boot.img contains the kernel (you have modified this)
I can use your boot.img on other ROMs such as AdamG's seeing that yours is based on this?
Click to expand...
Click to collapse
I modified the *source* at which the kernel is compiled and built from. I then configured the base options for the kernel, compiled it, modified the various init scripts (which are supplied via the AOSP source build), and made the ramdisk, packed the boot.img... etc etc
If you wish to use this kernel on another rom (such as OpenDesire), then you will also need to copy the folder /system/lib/modules from my ROM to OpenDesire also. You will also need to manually edit /system/etc/init.d/**** script (whatever it is loading modules) or if there isn't one, create one to load ext2, ext3, ext4 and ipv6...
Bit more involving than I first made out really lol! Sorry...

cenkaan said:
no it's not working...full wipe and later set to never but it's not working..
-sleep mode-
Destination address 192.168.1.86
Packets sent 10
Packets received 0
Average round-trip time 0.000 ms
in the meantime rom is very nice. great job.. Pls help me.. I use this rom. i loved it
Click to expand...
Click to collapse
Strange indeed...
I've been reading a bit in other threads, does your WiFi MAC start with something other than 00:23?? As from what I read in AOSPDesire thread, it occurs to phones whose MAC starts with different numbers to that... Again, sorry its not working for you...
Did some digging, looks like a fault which is also apparent on other HTC devices, including the N1
http://code.google.com/p/android/issues/detail?id=9781
According to that (or so I think it makes out) it's also dependant on the make/model/type of Router which you also use...
So us Desire owners are most definitely not alone...

Ok that's enough hassle for you
Thanks so much for all your help
Fantastic developer will download your ROM as soon as i get home, thanks

thanks for the help and great rom.. and yes, what a pitty my wifi mac address is begin with 38:E7..

PaulW21781 said:
Strange indeed...
I've been reading a bit in other threads, does your WiFi MAC start with something other than 00:23?? As from what I read in AOSPDesire thread, it occurs to phones whose MAC starts with different numbers to that... Again, sorry its not working for you...
Did some digging, looks like a fault which is also apparent on other HTC devices, including the N1
http://code.google.com/p/android/issues/detail?id=9781
According to that (or so I think it makes out) it's also dependant on the make/model/type of Router which you also use...
So us Desire owners are most definitely not alone...
Click to expand...
Click to collapse
The same issue does NOT occur on any HTC ROMs so am wondering what HTC has done specifically to address the problem...

hello sorrry i'm new.... (sorry for my bad english)
in this rom is not sense installed? Can someone upload pictures.

bobo26 said:
hello sorrry i'm new.... (sorry for my bad english)
in this rom is not sense installed? Can someone upload pictures.
Click to expand...
Click to collapse
Sense is not installed, no...
Pictures - couple are in the first post of this thread (at the bottom of it)
*update*
Updated to v0.1b, enabled new "Conservative" power governor for the CPU in the Kernel. Use SetCPU to enable this in the phone itself, will hopefully improve battery life, but will have a slight effect on performance when this option is enabled.

[ROM] Megatron v1 (experimental, performance-oriented, beta kernel)

Announcement: I highly suggest you flash void. - http://forum.xda-developers.com/showthread.php?t=887281
Well, here's one more ROM for you guys: Megatron.
Why the name? Seemed only logical considering the name of our device, Optimus One.
It's basically a ROM tweaked for performance while retaining a decent battery usage. Also, with this ROM, you won't need to flash any other tweaks.
I daresay it's so far the speediest ROM for LG P500.
Features:
v2:
to be updated
v1:
root + superuser + busybox
APKs deodexed + zipaligned + png-optimized
apps2sd + dalvik2sd [1]
performance tweaks: (JIT, hardware acceleration, etc) [2]
includes drellisdee's custom kernel [3]
kernel repacked to set onboot the scheduler to interactive (tweak)
applications removed: App Advisor, Layar, Twitter, Facebook, LG Home, Think Office, Update notifications and Twitter [4]
applications changed: Genie widget (now transparent), Music (imported from CM)
applications added: Titanium backup, File Manager (imported from CM) and the awesome LauncherPro [5]
ringtones, notification and alarm sounds added (including iPhone ones)
changed boot animation to a more cute one
auto-overclock to 728Mhz and possibility to easily revert (minitron tweak) [6]
[1] Rather than move_cache_sd program used in another ROMs, I use another method for moving dalvik-cache to SDcard since sometimes using the aforementioned program won't work successfully. It's a known issue of Dsixda's kitchen.
[2] Heapsize: 32MB; without a doubt the best value.
[3] Check the original thread here and if you can, buy him some beer.
[4] I left CarHome due to popular demand.
[5] Titanium backup will allow you to uninstall any system application and to backup the ones you install. LauncherPro is in my opinion, way better (performance-wise) than ADW.
[6] As far as I've read, 728Mhz is stable for everyone til now.
Click to expand...
Click to collapse
Requirements:
In order to flash this ROM, you'll need on your device:
Having read the feature list and notes above
Root (check thread)
Drellisdee's custom recovery (check thread)
Class 4 SDcard or higher (bench it with h2testw)
Megatron (download it here)
How to flash:
First, reboot into recovery via 3-button-combo, ADB, terminal, w/e.
Partition SDcard (swap: 0, ext: 512), ext2-ext3, then ext3-ext4 it.
Wipe data (data,cache,dalvik-cache,ext).
Connect the device to PC, copy Megatron over to the SDcard, disconnect.
Flash it via "flash zip from sdcard"
Reboot
Read important notes below
That's it.
Important notes:
* There were some reports on other ROMs that battery usage was very high, especially on standby. While this ROM should perform better, it won't still have as good battery usage as stock ROM mainly due to the scaling governor being set to interactive. Also because of this reason, benchmarks could be slightly lower. I however promise that the overall experience and snappiness will be quite satisfying.
* I've made an easy and friendly way to decrease the clock back to stock 600Mhz. Instead of needing to use SetCPU, you just need to create a folder in your SDcard called "minitron" (without the ""), then reboot your phone. Your clock will be now back to 600Mhz. If you wish to revert it to the default 728Mhz, just delete the folder and reboot your phone again. Since the voltage is the same for both clocks, battery consumption should be around the same too. If for some odd reason, you get a boot loop, it means your phone doesn't support (*gasp*) a 728Mhz clock. To avoid a boot loop, go back to the custom recovery, toggle sdcard-pc connection and create the "minitron" (without the "") folder. Reboot, should be fine.
* Remember, you won't need to flash anything else. Everything's here.
As you already know, I cannot be held responsible for any damage you may cause to your phone by following these instructions. Every step taken is of your entire responsability.
Testimonials:
* "I noticed that the phone was another! much better performance! I did all the tests and there are no problems!"
* "This Rom is just... Amazing!!!"
* "Feedback: working nicely untill now. So far so good - the best ROM yet"
* "Great work , phone is workin faster and booting 2times better now great work."
* "So far I can say it is arguably fast. Phone is super snappy and responsive."
Time to see for yourself.
Just remember, it's still an experimental ROM.

-reserved-

Thanks for the work, though I think I'll be passing for right now.
Auto OCd kernel with way to revert is a bad idea at this point in that kernel. I would do it the other way around. Let it be a "MegatronMax" (or something like that) folder to ENABLE the OC, but leave it at 600MHz till more testing has been done. Just because the volt is the same doesn't mean its going to perform as well long run. Not even sure Interactive will be better than say conservative because of the excessive ramping up and down in freq. I have seen in interactive. I guess bottom line is, you shouldn't include a beta kernel yet in your ROM and default it OCd. At this point in development I think you should let the users decide if they want to test out these kernel features themselves because it is easy enough for flash the kernel back and forth.
http://forum.xda-developers.com/showthread.php?t=866774
Plus the author of the kernel requested that you DO NOT include it in ROMs, but rather point users to that thread.
Other than the kernel issues, seems like it will work well for those who want those features.
Just my 2 cents, seems like a decent enough ROM, like to see how it works for people.

eigokyoukan said:
Auto OCd kernel with way to revert is a bad idea at this point in that kernel. I would do it the other way around. Let it be a "MegatronMax" (or something like that) folder to ENABLE the OC, but leave it at 600MHz till more testing has been done. Just because the volt is the same doesn't mean its going to perform as well long run. Not even sure Interactive will be better than say conservative because of the excessive ramping up and down in freq. I have seen in interactive. I guess bottom line is, you shouldn't include a beta kernel yet in your ROM and default it OCd. At this point in development I think you should let the users decide if they want to test out these kernel features themselves because it is easy enough for flash the kernel back and forth.
Click to expand...
Click to collapse
Been using it for days and no complaint.
Like I said, it's a performance-oriented ROM. Default OC makes sense to me.
If people are scared of long-term effects, they should Minitron-it then.
Anyway, I'll update the thread's title.
And interactive is way better than anything to be honest. It will even be the next default scheduler in CyanogenMOD.
eigokyoukan said:
Plus the author of the kernel requested that you DO NOT include it in ROMs, but rather point users to that thread.
Click to expand...
Click to collapse
Didn't read that and it's the first request of the kind I've seen.
For user's comfort, custom kernels often tag along with custom ROMs. Protocol has always been to credit the author, point to original thread and urge for a donation. At least to what I'm used to. However, if he insists on this and contacts me directly stating he really doesn't want his kernel included on a ROM, I will abide and remove the whole ROM since it loses its raison d'être.

Definitely not trying to flame or troll man
That was just my opinion on the matter. I am sure there are many people who will install and enjoy your work.
It is not uncommon to not want your work bundled, but at least you gave credit. I see too often credit not even given for others discoveries and hard work.
I still say default OC is a bad idea until we understand the full long term effects of having this hardware 700+MHz, but then again, this will start getting it tested.

Have installed the ROM. Works Great, No problems so far. Like the LP. But I would like to have an option to install themes and so one. That would be fantastic.
Thanks!
EDIT: Solved

There is a reason I set max freq on boot to 600mhz in kernel as its to prevent users from getting stuck in a boot loop at a speed thats too great for their device. If you kernel panic it will reboot back to stock max as as had it set up. I did also have in my post not to repack kernel in rom and posted source so rom makers could build their own variant to use. I'm not going to ask for you to pull rom however as I see no reason for that. I just made it so it would reach as broad an audience as possible even those that don't want to overclock as its optional as I had it setup. Also, by using koush's any kernel its compatible with virtually any rom.
Noejn, I've learned the hard way just because your phone runs ok at xxx freq doesn't mean others will.

hello Noejn be honest, I have updated this roms just because I had the famous problem "reboot (reset) the phone" as soon as I put everything, I noticed that the phone was another! much better performance! I did all the tests and there are no problems!
the only thing, there is more and reset!
is a week that I bought, and I can not figure out how to solve this problem you know anything Noejn
However good the ROM recommend it!

eigokyoukan said:
Definitely not trying to flame or troll man
That was just my opinion on the matter. I am sure there are many people who will install and enjoy your work..
Click to expand...
Click to collapse
Yea, no worries. Sorry if I seemed harsh in my reply, not my intention.
I do have a different opinion though, slightly more optimist.
Since the voltage is the same for both clocks and the cpu only peaks if called, I don't think there will be much overheating. Also, I've never heard of any MSM7227 that toasted itself or his hardware neighbours.
That being said, you may think it's a leap of faith but I find it perfectly safe to use a 728Mhz clock as default. I may be wrong but let's hope not.
drellisdee said:
Noejn, I've learned the hard way just because your phone runs ok at xxx freq doesn't mean others will.
Click to expand...
Click to collapse
I understand that.
So far, the least stable clock that someone had on your awesome kernel was 748. Even so, as a safety measure, I've set it @ ~728. If for some reason there's someone out there that gets a boot loop, he just have to go to the custom recovery, toggle the sdcard-pc and create "minitron" folder. Done, 600Mhz!
Also, thanks for officially letting me use your kernel on this ROM.
fr4nkr0c said:
hello Noejn be honest, I have updated this roms just because I had the famous problem "reboot (reset) the phone" as soon as I put everything, I noticed that the phone was another! much better performance! I did all the tests and there are no problems!
the only thing, there is more and reset!
is a week that I bought, and I can not figure out how to solve this problem you know anything Noejn
However good the ROM recommend it!
Click to expand...
Click to collapse
I'm glad you found it speedy!
Regarding your reboot problem that happened before, even on other ROMs, sounds to me it is a phone matter. Shouldn't you allege malfunctioning to your carrier and get the phone switched?

* Quadrant (w/ default options) attached to main post
* Forgot to add to features a different boot animation

i say thumbs up just for the name , not to mention the rom

I know there are some differences, but would this work on an Optimus T (P509)? I've been looking around for a rom and can't seem to find anything as promising as this. Any help is always appreciated.

Optimus T = O1 for T-mobile

gemarc said:
Optimus T = O1 for T-mobile
Click to expand...
Click to collapse
Yes, I know, but that wasn't my question. I understand that the processor in the O1 is MSM7627 and the Optimus T has a MSM7227. Since the kernel was made for the O1 would I need to find a different compatible kernel for this rom on the Optimus T or would this OC'd kernel work? I'm willing to test it, but I just wanted an opinion before I started.

Can you add an option on this ROM ? I would really like the softkeys to be always on.
Congratulations for your work !
Sent from my LG-P500 using XDA App

This Rom is just... Amazing!!!
Congrats

l30r0 said:
I know there are some differences, but would this work on an Optimus T (P509)? I've been looking around for a rom and can't seem to find anything as promising as this. Any help is always appreciated.
Click to expand...
Click to collapse
i think there is a ThundeROM version (originaly for optimus S) being adjusted for optimus T (not optimus one tho )
try checking androidcentral if i remember right

Nice job

xilw3r said:
i think there is a ThundeROM version (originaly for optimus S) being adjusted for optimus T (not optimus one tho )
try checking androidcentral if i remember right
Click to expand...
Click to collapse
thanks for the tip.

do games run better with this rom?

[Project] 2708 kernels for Legacy Builds (ezterry look, or anyone w/ 2708 experience)

Introduction:
Two questions.
1: should they be renamed to be 2825 kernels?
2: I need some help. I have realized that 1.5 hero roms provide an amazing experience with the extra ram; when swap and cc are disabled, while still leaving sense running, I can switch freely between clock, browser, messaging, and rosie (sense homescreen) without any of them quitting. App launch times are phenomenal, and I really would like to use a 1.5 hero as a daily rom.
Unfortunately, SD card, ringtones, and other features don't work. My only explanation for this is because historically, hero 1.5 roms always had a seperate modules.sqf in /system/modules/modules.sqf.
I think this is the reason, because when I try a 1.5 non-hero rom with a 2708 kernel, the result is all of these functions working perfectly.
Some comments:
I find it amazing that these newer kernels work so well with the older roms.
I will update this thread as progress occurs.
CURRENT PROGRESS
The only progress I know of is this:
ezterry has posted an "OLDBUILDS" kernel that enables only 8 of the available 14 megs so that camera works.
Download: http://sandbox.devnull.name/android/ezOldBuildsKernel-2708_S.zip
Please help. This can be an amazing project.

Beawtifull thread.
I love sense roms (1.5 is ok ) and also vanilla donut.
With some mb of ram more would be amazing !
I have used 1.6 vanilla with 14mb ram more, but camera don't works.

update:
I can't find any 1.5 sense roms for g1 that DONT have the modules.sqf, but rather have them somewhere else.
Could people please:
1. provide me with information about what modules.sqf is, and how it can be extracted/ combined/moved/ etc so that anykernel will pick up those modules.
2. find a 1.5 sense hero rom without the modules.sqf, but with the necessary files to allow SD access and ringtone selection to work.
known not to work
mightymax hero 1.9
maxisma sense 2.0.1
qteknology 3.05 cupcake sense
sensehero 1.4
3. These problems could also be caused by xbin.sqf, as in the proper xbins aren't able to be accessed that allow sd card and ringtone selection... but both of those are conrolled by mediaserver which is in bin (afaik).
Smart people please input.

nobody? at least post your thoughts here about what you think i'm doing, is it stupid, is it blatantly obvious, etc?
Essentially what i'm asking for is a 1.5 kernel that works with 2708.

jcarrz1 said:
3. These problems could also be caused by xbin.sqf, as in the proper xbins aren't able to be accessed that allow sd card and ringtone selection... but both of those are conrolled by mediaserver which is in bin (afaik).
Smart people please input.
Click to expand...
Click to collapse
Um. The sqf files are just squash fs disk images (mount them via loop).. there is no reason my kernel will have an issue with this.
If /system/xbin isn't mounted check logcat/dmesg.
Make sure losetup is finding the loop device.. you may need some shortcuts to be added in init.rc to adjust the loop device location.. that or pull losetup or toolbox from a newer build and see if it helps.
If the screen isn't black its mostly just updating the core version of linux to behave I think.

No news? I would really love sense 1.5 with 14mb ram hack, or vanilla 1.6 with more 14mb

bumpidibump
jcarrz:
did you try the zx 1.5 hero (zachattack xillius thing)? dont know how it is called correctly

id go for sensehero 1.4 with the extra ram!
still the most stable/usable sense rom i ever flashed.

nagash91 said:
No news? I would really love sense 1.5 with 14mb ram hack, or vanilla 1.6 with more 14mb
Click to expand...
Click to collapse
Both Amon_RA ION1.6 and the ZX_Donut (and more) will run with ezterry's 2708 kernel. you will need to set the camera's rez to 1mb to take pictures. An if i remember correctly the wlan.ko from a CM or CM builds such as the biffmod is needed to make the wifi work.
I ran donut with ezterry's kernel for a long time, and finally switched to CM 6.1 due lots of new apps i want to try are 2.1+ only.

sleepyfu said:
Both Amon_RA ION1.6 and the ZX_Donut (and more) will run with ezterry's 2708 kernel. you will need to set the camera's rez to 1mb to take pictures. An if i remember correctly the wlan.ko from a CM or CM builds such as the biffmod is needed to make the wifi work.
I ran donut with ezterry's kernel for a long time, and finally switched to CM 6.1 due lots of new apps i want to try are 2.1+ only.
Click to expand...
Click to collapse
Thanks!
"set camera's rez to 1mb" ? you mean 1mpx?

nagash91 said:
Thanks!
"set camera's rez to 1mb" ? you mean 1mpx?
Click to expand...
Click to collapse
If you use the kernel in the op you get 12 extra mb of ram and camera will likely work as usual..

nagash91 said:
Thanks!
"set camera's rez to 1mb" ? you mean 1mpx?
Click to expand...
Click to collapse
Oops, yup 1m pixel
ezterry said:
If you use the kernel in the op you get 12 extra mb of ram and camera will likely work as usual..
Click to expand...
Click to collapse
yup, IIRC i tried it awhile ago and camera worked in high rez.
phone pictures are generally for a quick share on social networking sites anyways, 1mp was the setting i've always used.

sleepyfu said:
Oops, yup 1m pixel
yup, IIRC i tried it awhile ago and camera worked in high rez.
phone pictures are generally for a quick share on social networking sites anyways, 1mp was the setting i've always used.
Click to expand...
Click to collapse
Glad to still see an interest in this. I've been fooling around, and made some progress.
first, Beav_35 has made a donut 2708 kernel that has had mixed results for me so far. He nor I are responsible for any damage to your phone. it is not guaranteed to work at all. use at your own risk.
http://www.multiupload.com/0YROAJ4IDY
Second, I am working on getting a nice 1.5 sense working 100% on the g1. I will update this thread periodically.

thanks jcarzz1! il watch this thread!

Are there any complete, stable , ready-made Donut ROMs that has a 2708 kernel? Preferably AOSP.