1. You can change to newer Kernel 2.6.32 or
2. You can change to older wlan.ko (compiled for 2.6.25)
how do i go about doing either of these things? if someone can link me or provide me with some simple step by step instructions that would be great. ive searched around and been waiting but i cant find n e thing that i understand easily
The HTC Vogue does not have wifi.
Use one of the latest nbh (2.6.25 or 2.6.32) released by me and the update.
Haret users please stop using dzo initrd to solve the problem, use the updated version.
read this post for more info
Related
Hi,
great site........
I'm trying to get my 2.1 software upgraded HTC hero back to 2.0. My phone worked great with my in car blue tooth system before the stoopid 2.1 update and I just need it working again.
please help...
Thanks guys........
-J
There is no 2.0. It's either the original 1.5 or the current 2.1. You can root your device and install a custom ROM of whatever you can find here if you choose. There is a really nice version of 2.2 in the Dev section if you want to go that way. If you do some searching you'll find all the info you need to accomplish this.
gorbisloth said:
There is no 2.0. It's either the original 1.5 or the current 2.1. You can root your device and install a custom ROM of whatever you can find here if you choose. There is a really nice version of 2.2 in the Dev section if you want to go that way. If you do some searching you'll find all the info you need to accomplish this.
Click to expand...
Click to collapse
hummm? it must have had the 1.5 then prior..........
I wonder if the 2.2 would fix my issue.....
let me see if i can find the threads your talking about...
Thank you,
-J
2.2 has a rc1 and nightly builds. May or may not work with your Bluetooth better, it does not have sense. I prefer that, its quick and zippy.
Otherwise I'd suggest trying the custom 2.1 roms and if they don't work and you want to go back to 1.5 I highly suggest digging up an old custom 1.5 rom rather than go stock.
You might even get some help figuring out how to get the drivers from 1.5 into a custom 2.1 or maybe 2.2 if you're patient.
Sent from my HERO200 using XDA App
Follow this thread
Soon you will be able to revert to anything you can imagine
http://forum.xda-developers.com/showthread.php?t=759955
I don't know if another 2.1 would help you, don't they all use the same bluetooth stack?
Do 2.2 ROMs use the same bluetooth stack?
derekwilkinson said:
I don't know if another 2.1 would help you, don't they all use the same bluetooth stack?
Do 2.2 ROMs use the same bluetooth stack?
Click to expand...
Click to collapse
Not positive but worth a try. If 1.5 stack worked I thought maybe it could be merged or swapped into a 2.1 if he wanted to do the work. I could be wrong
Sent from my HERO200 using XDA App
2.1 bluetooth drivers were pretty broken. I highly recommend trying 2.2, as it is much improved
Sent from my HERO200 using XDA App
Loading the xml files to Tasker
I am a new just a few weeks into Tasker and I see all of these great xml files people have created, however, I do not know how to execute them once I have loaded them into my tasker directory in my phone. I have created a few simple things and I am reading some articles called Pocketables and other things about Tasker. But I have seen all this xml files that are already built and "ready to go" but I can not load and execute them in Tasker and can not find any material where it defines "how to."
I have tried various ways unsuccessfully and if some gentle soul would like to give me a hand I would appreciate it. It would appear you would create a Task and select a category, then file, but this is where I am really hung up at this point. I have tried various different ways and so far nothing works. Gary
Hi, I am running 2.2 froyo build on my HTC pure (runs almost flawlessly with no slowdown and no dropped calls to date) but I was wondering how to update it, do i just replace the Zimage or is there another way?
Yes, just update zImage, initrd.gz, rootfs.img and system.ext2 whenever newer versions of either of these are available.
Links to the autobuild services and new system versions and answers to your question should all be found in the XDANDROID project thread in this forum. No need to open up a new thread every time.
Tyvm I won't do it again
http://forum.xda-developers.com/showthread.php?t=772795
Apparently it is possible to run the PSFreedom Jailbreak App on all MSM72x CPU, and considering the Tattoo has one, then theoretically it should be able to run it right?
But in it's current state, will it work on our Tattoo's and how in the freaking hell does it work anyway? xD
Anyways, just wanted to drop this here.
It would be wonderful *______*
I was thing of that.. lol
Well we just have to give it a try...
KezraPlanes said:
http://forum.xda-developers.com/showthread.php?t=772795
Apparently it is possible to run the PSFreedom Jailbreak App on all MSM72x CPU, and considering the Tattoo has one, then theoretically it should be able to run it right?
But in it's current state, will it work on our Tattoo's and how in the freaking hell does it work anyway? xD
Anyways, just wanted to drop this here.
Click to expand...
Click to collapse
Is confirmed the porting on android and psp. But we don't know what will need to run. A new kernel, sure. Maybe the terminal emulator (or a gui) to start/stop the deamon.
francians said:
Is confirmed the porting on android and psp. But we don't know what will need to run. A new kernel, sure. Maybe the terminal emulator (or a gui) to start/stop the deamon.
Click to expand...
Click to collapse
As far as I've heard, you need to not have USB at all (only charging works) to be able to run this.
So either as someone said on the original thread, someone makes a recovery image that we can flash for that same purpose OR dual-boot from SD.
To be honest I don't see the second one happening on the Tattoo
To run this hack you'll need a non-senseUI 2.2 rom.
https://spreadsheets.google.com/lv?key=tarAC83Wjsq2QZvP4iR5mlw&toomany=true
At least on kernel 2.6.29 (spqrom 0.4), the tattoo uses the msm_hsusb driver instead of the MSM72K, so i don't think it will work without porting it. But the hero and dream use msm_hsusb on 2.6.2x kernel and MSM72K on 2.6.3x. Maybe a kernel update could fix this for us (hear that, rom cookers? update the kernel of your froyo roms!)
blackkn1ght said:
To run this hack you'll need a non-senseUI 2.2 rom.
https://spreadsheets.google.com/lv?key=tarAC83Wjsq2QZvP4iR5mlw&toomany=true
At least on kernel 2.6.29 (spqrom 0.4), the tattoo uses the msm_hsusb driver instead of the MSM72K, so i don't think it will work without porting it. But the hero and dream use msm_hsusb on 2.6.2x kernel and MSM72K on 2.6.3x. Maybe a kernel update could fix this for us (hear that, rom cookers? update the kernel of your froyo roms!)
Click to expand...
Click to collapse
Hi,
In eclair kernel for tattoo there are the drivers for MSM72K! Later i ll try to
compile a kernel with MSM72K support for tattoo and publish it here to test
it.
Seg.
Nice already some progress
Well were we go... for Desire and G1...
h**p://forum.xda-developers.com/showpost.php?p=8025826&postcount=52
h**p://www.ps3-hacks.com/2010/09/06/hack-your-ps3-with-your-androiddesire/
it works?
Im going to try this now :0
already try, does not work((( at spqrom 0.4
I tried flashing the zip and it said error in /sdcard/PS3-signed.zip (Status 0)
That's because they weren't made for the Tattoo
Tattoo appeared in the list http://psfreedom.com/wiki/index.php?title=Device_compatibility_list. waiting ...
It works on HTC Wildfire : http://www.ps3underground.net/esclusiva-port-del-psfreedom-su-htc-wildfire/
tibob33 said:
It works on HTC Wildfire : http://www.ps3underground.net/esclusiva-port-del-psfreedom-su-htc-wildfire/
Click to expand...
Click to collapse
The wildfire uses the same msm_hsusb as shown in the graph, so maybe the ball is now rolling?
Edit:
I flashed the wildfire zip and it returned no errors like the other zip, but failed to go past the tattoo logo on SPQRom 0.4.1?
Incorrect boot.img I guess
Wildfire kernel 2.6.32
Tattoo kernel 2.6.29
so probably if you use segway's experimental .32 kernel it is going to work . try it.I don't have a ps3.
rwmanos said:
so probably if you use segway's experimental .32 kernel it is going to work . try it.I don't have a ps3.
Click to expand...
Click to collapse
Im pretty noobish at android stuff, seen the thread and gone to the link and there is loads of files... please guide
I have the latest Cyanongemod (Android 2.3.4) and i wish to know if it is compatible with Android Open Accessory Development Kit (ADK).
ADK is compatible only with Android 2.3.4 and 3.1 but im not sure if Cyanomgemod include the required libraries.
Hi!
I´ve been searching this for a while, and yes, cyanogenmod (at least nightly builds) support - you might have trouble getting other customs roms.
You need 2.3.4+ and 2.6.35+ kernel with CONFIG_USB_ANDROID_ACCESSORY flag set. Instructions about xml, permissions, here (sorry, cant post full urls):
github.com/ezterry/manifest-gingerbread-DS/issues/32
Push nexus files from here:
forum.cyanogenmod.com/topic/26339-usb-accessory-mode-is-adk-supported-in-cm-7/
And upload demokit via eclipse.
Regards
Robson
robsondantas said:
You need 2.3.4+ and 2.6.35+ kernel with CONFIG_USB_ANDROID_ACCESSORY flag set. Instructions about xml, permissions, here (sorry, cant post full urls):
github.com/ezterry/manifest-gingerbread-DS/issues/32
Click to expand...
Click to collapse
There is one problem - you cannot flash custom kernel on Milestone that is not signed by Motorola (locked bootloader). And the latest kernel that we have is 2.6.32.9, so that will not work.
If you want custom kernel (but without radio) you can try to have a fun with 2nd boot - http://droid-developers.org/wiki/2ndboot
Hi,
I'm trying to build cyanogenmod 6 (froyo) from sources on github for G1.
Sidenote. The reason I'm trying to do this is i'd like to modify kernel parameters. I'm trying to make the phone talk to external device using built in serial port. I can do it with my current CM6, but it looks like serial debugger engages and starts responding to the device and also steals some of the data being sent to phone.
To build I used instruction posted at cyanogen wiki "HTC Dream & Magic: Compile CyanogenMod (OS X)" which covers gingerbread but checked out froyo-stable branch at first. I know that gingerbread version stopped supporting G1 at some point last year.
Without much success even after fixing manifest to point to updated repo urls from kernel.org to googles repo etc. The problem is that apache-http seems incompatible with old sources and it is referenced by head.
I also tried froyo branch, but it doesn't build as well because something seem to be broken for dream_sapphire, and it is not present in the devices anymore.
I've tried searching for compilation errors, and general build questions/instructions here and on cyanogen's forum, but looks like CM6 is not very active these days.
Can someone point me into right direction where to search for relevant info on building it? Would getting a proper revision help or should I combine stuff from several branches to make it work?
I've already spent quite a lot of time figuring out how build is being configured and how things stitch together but without much progress on the actual build.
And with times required to sync a whole repo and build it, it is becoming frustrating.
Any help would be muchly appreciated!
Regards,
Oleg
It's dead.
I also wanted to make a cm6 rom, but I couldn't get anything to work.
I got the addresses all updated but it looks like a bunch of the files have completely dissappeared. You may be able to make it skip those, but then it may not work completely.
Go for AOSP?
Now that's a shame. I wanted to build CM because I'm familiar with it and the other thing is that they have reasonable instructions about building it. But at least I don't need to waste my time trying to figure out how to fix it.
In fact I don't need any extras they provide, a bare android would suffice to me if all the sensors and connectivity would be available. But I'm not familiar with internals of building vendor specific stuff. My understanding was that I need proprietary parts together with AOSP to build a working ROM and that's one of the things CM guys did. Correct me if I'm wrong.
aliher1911 said:
Now that's a shame. I wanted to build CM because I'm familiar with it and the other thing is that they have reasonable instructions about building it. But at least I don't need to waste my time trying to figure out how to fix it.
In fact I don't need any extras they provide, a bare android would suffice to me if all the sensors and connectivity would be available. But I'm not familiar with internals of building vendor specific stuff. My understanding was that I need proprietary parts together with AOSP to build a working ROM and that's one of the things CM guys did. Correct me if I'm wrong.
Click to expand...
Click to collapse
Nope AOSP is as easy to build now
Go to the android site and follow directions
Google for "build android"
At the part when doing repo init you need to get the right branch
Go to "build for devices" then scroll down for recommended branches and look for the dream
One thing you'll need to do differently is do "make otapackage" instead of plain "make"
And once that's done you'll need to tweak the zip and get rid of the "recovery" folder and tweak the updater-script
Oh yeah, and I don't know exactly how you would do this part, but you'll need to get the source for a newer kernel in there, like ezterry kernel and use it with 2708+ radio/spl
Unless you wanna use the AOSP kernel & spl & radio which is old
What I did is just flash his kernel after the rom, but you want to do kernel stuff so yeah...
Sent from my HTC Dream using Tapatalk