Guest hungary Posted May 20, 2010 Report Posted May 20, 2010 Here's the build.prop from working 2.2 Hero ROM: # begin build properties # autogenerated by buildinfo.sh ro.build.id=FRF42 ro.build.display.id=sdk-eng 2.2 FRF42 36942 test-keys ro.build.version.incremental=36942 ro.build.version.sdk=8 ro.build.version.codename=REL ro.build.version.release=2.2 ro.build.date=Wed May 12 20:05:55 PDT 2010 ro.build.date.utc=1273719955 ro.build.type=eng ro.build.user=android-build ro.build.host=android-test-1.mtv.corp.google.com ro.build.tags=test-keys ro.product.model=sdk ro.product.brand=generic ro.product.name=sdk ro.product.device=generic ro.product.board= ro.product.cpu.abi=armeabi ro.product.manufacturer=unknown ro.product.locale.language=ldpi ro.product.locale.region= ro.wifi.channels= ro.board.platform=msm7k # ro.build.product is obsolete; use ro.product.device ro.build.product=generic # Do not try to parse ro.build.description or .fingerprint ro.build.description=sdk-eng 2.2 FRF42 36942 test-keys ro.build.fingerprint=generic/sdk/generic/:2.2/FRF42/36942:eng/test-keys # end build properties # # system.prop for generic sdk # rild.libpath=/system/lib/libhtc_ril.so ro.telephony.default_network = 4 # # ADDITIONAL_BUILD_PROPERTIES # ro.config.notification_sound=OnTheHunt.ogg ro.config.alarm_alert=Alarm_Classic.ogg media.stagefright.enable-player=true media.stagefright.enable-meta=true media.stagefright.enable-scan=true media.stagefright.enable-http=true ro.kernel.android.checkjni=1 ro.setupwizard.mode=OPTIONAL xmpp.auto-presence=true ro.config.nocheckin=yes net.bt.name=Android dalvik.vm.stack-trace-file=/data/anr/traces.txt
Guest hungary Posted May 20, 2010 Report Posted May 20, 2010 Paul got 2.2 running on N1: http://twitpic.com/1ph9dz
Guest jmmL Posted May 20, 2010 Report Posted May 20, 2010 http://forum.huawei.com/jive4/thread.jspa?...&orderStr=9 Its a package out of 9 parts, 4 above the long lincense und 5 under it. Included are the Kernel itsself, driver, firmware build parts, bugreports etc, all stuff a dev needs. Greets :rolleyes: Mirrored here: http://rapidshare.com/files/389721363/kernelQMR.zip
Guest Josh04 Posted May 20, 2010 Report Posted May 20, 2010 Disclaimer: I'm a java / app / web guy, and know nothing about linux kernels, so I may be way off base... It seems like it ought to be possible to pinch the existing Huawei hardware drivers from a working ROM / kernel, and recompile them into a new kernel. After all, the kernel revisions between android 1.5 and 2.2 are only very minor version numbers, and I would have thought that the driver architecture would remain the same? Does anyone know if this is feasible, and if so, perhaps it might be possible to get vibration support in our current 2.1 builds by compiling the old driver into the new kernel? You've not met the linux kernel. They take twisted pride in breaking driver compatibility as often and as much as they can.
Guest mehall Posted May 20, 2010 Report Posted May 20, 2010 Is that really all the source stuff that we've been waiting for? If so, that's great news! I'm assuming someone sensible will set something up on launchpad or sourceforge or something and start a proper fork or something? I'd do it, but I can't code to save my life, haha
Guest Josh04 Posted May 20, 2010 Report Posted May 20, 2010 That's the 1.5 kernel source from last year. It's useless.
Guest mehall Posted May 20, 2010 Report Posted May 20, 2010 It's not useless if it's all the source including drivers and everything surely?
Guest Josh04 Posted May 20, 2010 Report Posted May 20, 2010 Unless you're a kernel dev talented enough to port them to the latest kernel, they kinda are. Even then, there are extra libraries for which we don't have the source.
Guest robot1000 Posted May 20, 2010 Report Posted May 20, 2010 Theoretically, would the pulse work better (less force closes) with the 2.2 then with 2.1?
Guest Josh04 Posted May 20, 2010 Report Posted May 20, 2010 Theoretically there shouldn't be any force closes in 2.1
Guest biron_w Posted May 20, 2010 Report Posted May 20, 2010 Theoretically, would the pulse work better (less force closes) with the 2.2 then with 2.1? I'm no expert but from what i've read 2.2 should be easier to get working on the pulse as it's smaller than 2.1 so should be easier to get on the pulses limited memory.
Guest robertopero Posted May 21, 2010 Report Posted May 21, 2010 @BigBearMDC: Is there any result with 2.2?
Guest BigBearMDC Posted May 21, 2010 Report Posted May 21, 2010 @BigBearMDC: Is there any result with 2.2? Not yet. That's the first thing I will try when I'm at home :rolleyes: Best regards, BigBear
Guest hungary Posted May 21, 2010 Report Posted May 21, 2010 Paul's N1 (Nexus One) 2.2: http://www.romraid.com/paul/nexusone/r15-emu-n1.zip DONT FLASH IT WITH PULSE!
Guest hungary Posted May 21, 2010 Report Posted May 21, 2010 "of course, booting it like that you have no drivers or anything.. but froyo boots without much modification as it is (i.e. easy work)" ????
Guest BigBearMDC Posted May 21, 2010 Report Posted May 21, 2010 Yay I will download the SDK now (although my school internet account will definetly be locked if I download such an amount :D) :rolleyes:
Guest BigBearMDC Posted May 21, 2010 Report Posted May 21, 2010 Yay I will download the SDK now (although my school internet account will definetly be locked if I download such an amount :() :D NO I can't download it ... damn proxy :rolleyes:
Guest pbacev Posted August 16, 2010 Report Posted August 16, 2010 can i help you with that that i've got a working pulse with 2.1 oficial
Guest JDMikey Posted October 22, 2011 Report Posted October 22, 2011 Thanks your guide worked well I'm am now making a current fix for the cam issue I will post this soon
Guest FunYeg Posted October 22, 2011 Report Posted October 22, 2011 Thanks your guide worked well I'm am now making a current fix for the cam issue I will post this soon Nice to heard it! Add oil!!!
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now