Hi,
I have tried the official roms, villainrom 12 (excellent!) and cronos 2.1.3 (also excellent!). All have the horrible bluetooth problem of skips in the music, then a speed up/slow down that results in pitch changes.
I saw that Darchdroid got it fixed in the CDMA version and wondered if there are any roms for the GSM version that have it fixed too? Just in case I missed it!
Thanks
nobody in this forum seems to know how to fix it. I've asked but nobody knows, i believe the only sense rom that i never had the skipping was behnaam's legend port.
I am not experiencing this with VillainROM 12. Didn't have it with CyanogenMOD by Elemag either...
none of the Aosp based roms have this problem it seems to be only sense related. I've had this problem with villain,cronos,chocolateeclair,etc and nobody had any idea when i asked the same question. I actually am going to try to move the bluetooth firmware and files from the legend rom i mentioned above into another newer sense rom I just have to read up on resigning the zip, I'm a super noob to all that is linux.
Moved to Q&A as not development. Temporary redirect put in place.
ggrammer said:
nobody in this forum seems to know how to fix it. I've asked but nobody knows, i believe the only sense rom that i never had the skipping was behnaam's legend port.
Click to expand...
Click to collapse
Thanks, although I have also tried Cronos 2.2 (Froyo) that doesn't have sense and it still did the pitch/speed change.
kosmiq said:
I am not experiencing this with VillainROM 12. Didn't have it with CyanogenMOD by Elemag either...
Click to expand...
Click to collapse
Can I ask what car head unit or bluetooth headset you were using? It definitely does it with my Sony BT2600 car unit and both Cronos & Villainrom.
ggrammer said:
none of the Aosp based roms have this problem it seems to be only sense related. I've had this problem with villain,cronos,chocolateeclair,etc and nobody had any idea when i asked the same question. I actually am going to try to move the bluetooth firmware and files from the legend rom i mentioned above into another newer sense rom I just have to read up on resigning the zip, I'm a super noob to all that is linux.
Click to expand...
Click to collapse
Could you let me know an AOSP rom to try that you know it works in please? - although I really like sense, I hate this issue and could live without it to get it fixed.
I'm pretty much a noob at this too but I'll help as much as I can!
like kosmiq mentioned Elemag's CMH rom doesn't seem to have this issue (I've used this rom alot and I have a 2010 Mazda3 and the bluetooth in the mazda is wonky at best and this rom works perfectly with it). As far as cronos froyo I haven't tried the bluetooth in that yet in my car but that is still an alpha development so if you need something more stable and complete then stay away from it, It is a great rom and the one I am running now but I am probably going to flash over to Maxisma's newest legend+WWE combo rom.
Good to see Maxisma back.
Related
HI ALL,
On modaco 3.2 the GPS is not working at least for google map but meteo is ok?!
And for All 2.1 ROMS we have the green effects problem on recording video and photos?!
And also, not working playback videos for some of them!!
Plz guyz tell me i m not crazy lol cause i dont find any solution and I dont know now which rom is definitively really stable and full working.
mcr3.1 is stable and everything that is in there works. same goes for 3.2, but it lacks a few things since it is an operator tailored rom (namely there would be the "2g only" switch in settings, not sure about others). gps is working fine in both, if you have problems reflash your radio.
there is no bugfree 2.1 rom yet, as we are still waiting for the official release from htc.
if i say that this is the wrong category i will get bashed, so i'm not gonna say it. just gonna point out to you that there is a q&a subforum, which might be the better place for these types of posts.
Going from a 2.1 ROM to a 1.5 ROM appears to break GPS in some cases.
This can be fixed by reflashing the radio.
FunkTrooper said:
Going from a 2.1 ROM to a 1.5 ROM appears to break GPS in some cases.
This can be fixed by reflashing the radio.
Click to expand...
Click to collapse
THX a lot
i didnt say it is working lol cause i didn t try yet but i mean if you say so, so it is working and i ll try like that.
If you just coul imagine how many times i changed roms on hero looool within 5 days!!!! you ld become crazy.
BYE
hello new here i followed all the directions to a tee got everything install very easy as im not new to flashing roms. i have a rhod400 (sprint tp2) and i have the issue of no sound from the rear speaker when receiving phone calls or anything really. it all comes from the front earpiece speaker. is there a update to flash to fix this? or any easy way to get it working. ive tried numerous times thinking about a bad flash with no luck and yes i have task29'ed it after each to make sure. however the gbx0 3.3.x kernal works perfectly with sound but i like the normal omgb rom better personally for some reason the gbx0 nand rom on my phone seems much slower to respond and much slower going through menus etc for some reason and ive flashed it a few times to make sure
also im running the newest verizon .37 radio as well.
sorry for asking here and not in the thread i needed more posts and really hope someone can help with that. ill be posting more so hopefully will be able to ask there soon but i really wanted to get this fixed asap since i use this phone daily.
Never heard of that before, but I had to move the thread. Sorry.
Good luck & post logs. I doubt it's an issue with the ROM tho, as I run that same ROM myself. Same phone, same radio (assuming you're on the 2.37VZ radio), etc.
You're using the latest OMGB and the latest CWM recovery - not AOSP?
I know that OMGB is using the older kernel, and I want to say that the 3.x kernels got a serious audio code re-write. That could account for the difference. Unfortunately as it seems there is no more development happening in the OMGB rom there will not be support of the newer kernels. Perhaps you should consider using the GBX nand version rather than the OMGB.
wizardknight said:
I know that OMGB is using the older kernel, and I want to say that the 3.x kernels got a serious audio code re-write. That could account for the difference. Unfortunately as it seems there is no more development happening in the OMGB rom there will not be support of the newer kernels. Perhaps you should consider using the GBX nand version rather than the OMGB.
Click to expand...
Click to collapse
I guess I assumed the OP was using the kernel from OMGB.
Is that the case OP? Please stick to the kernel provided with OMGB and report back.
arrrghhh said:
I guess I assumed the OP was using the kernel from OMGB.
Is that the case OP? Please stick to the kernel provided with OMGB and report back.
Click to expand...
Click to collapse
The way I read his post was that he tried GBX w/3.x kernel and OMGB, but only saw the sound issue in OMGB. However he wanted to use OMGB as it seemed to have a better performance. It sounds like his issue might be related to using the older kernel in OMGB. Not necessarily so much that he was swapping bits and parts around.
wizardknight said:
The way I read his post was that he tried GBX w/3.x kernel and OMGB, but only saw the sound issue in OMGB. However he wanted to use OMGB as it seemed to have a better performance. It sounds like his issue might be related to using the older kernel in OMGB. Not necessarily so much that he was swapping bits and parts around.
Click to expand...
Click to collapse
I've just never heard of any sound issues with OMGB. I did a quick search, can't find anyone with sound issues on OMGB at all, whatsoever...
OP has been PMing me and said the same issue is present on another RHOD400. I have to think he's doing something wrong, but I have no clue what he could do wrong that would cause everything BUT sound to work...
arrrghhh said:
I've just never heard of any sound issues with OMGB. I did a quick search, can't find anyone with sound issues on OMGB at all, whatsoever...
OP has been PMing me and said the same issue is present on another RHOD400. I have to think he's doing something wrong, but I have no clue what he could do wrong that would cause everything BUT sound to work...
Click to expand...
Click to collapse
That is an odd issue. I have to agree with all your points.
wizardknight said:
That is an odd issue. I have to agree with all your points.
Click to expand...
Click to collapse
ive heard of this with really old sdcard builds... i seem to recall if you set the volume to one step below max the audio kinda worked the way its supposed to. let us know if your still having issues.
Me Too
I can confirm I'm having this issue as well on OMGB on my RHOD400. Can't hear notification tones or incoming ringer. Volume level "beeps" when you hit the buttons are also very quiet (at all levels) and come from earpiece instead of speaker.
Logcat with unanswered call and poor volume attached. Also, attaching logcat with info from startup.
I too am still using this as my daily phone...I'm missing calls and pissing people off (not that I care) due to this. It used to fix after a reboot, but now it's just stuck like this.
I'm seeing permissions issues trying to access the audio*.csv files from the SD Card, it looks like it finds a default instead. I'm not sure if this is normal.
NeoMatrixJR said:
I can confirm I'm having this issue as well on OMGB on my RHOD400. Can't hear notification tones or incoming ringer. Volume level "beeps" when you hit the buttons are also very quiet (at all levels) and come from earpiece instead of speaker.
Logcat with unanswered call and poor volume attached. Also, attaching logcat with info from startup.
I too am still using this as my daily phone...I'm missing calls and pissing people off (not that I care) due to this. It used to fix after a reboot, but now it's just stuck like this.
I'm seeing permissions issues trying to access the audio*.csv files from the SD Card, it looks like it finds a default instead. I'm not sure if this is normal.
Click to expand...
Click to collapse
Do you have this issue with the GBX Nand build?
wizardknight said:
Do you have this issue with the GBX Nand build?
Click to expand...
Click to collapse
Just got it installed. Ringer works fine on GBX0* + 3.3.6
NeoMatrixJR said:
Just got it installed. Ringer works fine on GBX0* + 3.3.6
Click to expand...
Click to collapse
Makes me think there's some acoustic patch that's missing in the OMGB .27 kernel...
That's a bummer. Strange only some experience the bug...
First, I am currently s-off and running NeoMax v2.0 with what I believe are the newest firmware and radios. I also have Sebastian's overclock kernel. While reading the AOKP-Neo thread, I noticed that it doesn't support custom kernals. Will I be okay just doing a wipe and flashing the Rom, or do I need to do something else because of the kernel I'm currently running?
Next, I understand that there are some bluetooth issues with voice and audio, but does anyone know of any problems when connecting peripherals such as bt keyboards or game controllers? I should be receiving the new Nyko Gamepad soon and am anxious to try it out.
Lastly, I know that It's been previously discussed but I haven't seen an answer that satisfies my needs yet. The AOKP camera qualitly is just plain lousy. I understand that the sense camera is incompatible because it is based on sense. Is it the sense firmware that makes the sense camera so great, or is it the program itself? Would it be difficult to reverse-engineer the program to run on AOKP? Admittedly, if It's not already obvious, I know next to nothing about writing programs and give major props to all the devs here, but is anyone working on this, or should I stop holding my breath?
aftafoya said:
First, I am currently s-off and running NeoMax v2.0 with what I believe are the newest firmware and radios. I also have Sebastian's overclock kernel. While reading the AOKP-Neo thread, I noticed that it doesn't support custom kernals. Will I be okay just doing a wipe and flashing the Rom, or do I need to do something else because of the kernel I'm currently running?
Next, I understand that there are some bluetooth issues with voice and audio, but does anyone know of any problems when connecting peripherals such as bt keyboards or game controllers? I should be receiving the new Nyko Gamepad soon and am anxious to try it out.
Lastly, I know that It's been previously discussed but I haven't seen an answer that satisfies my needs yet. The AOKP camera qualitly is just plain lousy. I understand that the sense camera is incompatible because it is based on sense. Is it the sense firmware that makes the sense camera so great, or is it the program itself? Would it be difficult to reverse-engineer the program to run on AOKP? Admittedly, if It's not already obvious, I know next to nothing about writing programs and give major props to all the devs here, but is anyone working on this, or should I stop holding my breath?
Click to expand...
Click to collapse
1. I believe that since you are s-off you can simply flash through recovery and the kernel will install itself. If not you can always do what s-on people like myself do and flash the boot.img through fastboot before booting into the rom for the first time.
2. Not sure.
3. From what I have heard the Devs talk about or how they react, it is not possible to run the sense camera on AOSP or AOKP roms since the app runs on the sense framework that is obviously absent in AOSP or AOKP. From what I understand there is no way to get the sense camera to work without the framework, and I am assuming the Devs that have the knowledge to work around something like that are busy with other, larger issues.
hope this helps
You should be fine just flashing things through the recovery, since Sense and AOSP roms use different kernels it should overwrite it. If you want to be completely sure nothing screws up you can always wipe the boot partition if you are using the latest version of TWRP.
aftafoya said:
First, I am currently s-off and running NeoMax v2.0 with what I believe are the newest firmware and radios. I also have Sebastian's overclock kernel. While reading the AOKP-Neo thread, I noticed that it doesn't support custom kernals. Will I be okay just doing a wipe and flashing the Rom, or do I need to do something else because of the kernel I'm currently running?
Next, I understand that there are some bluetooth issues with voice and audio, but does anyone know of any problems when connecting peripherals such as bt keyboards or game controllers? I should be receiving the new Nyko Gamepad soon and am anxious to try it out.
Lastly, I know that It's been previously discussed but I haven't seen an answer that satisfies my needs yet. The AOKP camera qualitly is just plain lousy. I understand that the sense camera is incompatible because it is based on sense. Is it the sense firmware that makes the sense camera so great, or is it the program itself? Would it be difficult to reverse-engineer the program to run on AOKP? Admittedly, if It's not already obvious, I know next to nothing about writing programs and give major props to all the devs here, but is anyone working on this, or should I stop holding my breath?
Click to expand...
Click to collapse
if you flash AOKP and have s-off you will get a custom kernel installed. There are a couple of kernels for AOSP right now. Snuzzo has the most customized one for AOSP
only BT issue that is left is BT calling
camera quality is the same from aosp to sense. only difference is sense cam can do 1080p video recording and aosp can only do 720p
any hope of getting FM radio support on roms (I'm mainly using cyanogenmod, usually sportsstar's). I've tried the port of the apk for the fm radio (wouldn't run) and some spirit radio apk (loud static all channels). Thanks.
I'm using spirit and it works fine. You do need to have a headset plugged in though for an antenna
Sent from my HTC_Amaze_4G using xda app-developers app
yeah. ok thanks, I guess I will try again.
your welcome
reebokhcfr said:
yeah. ok thanks, I guess I will try again.
Click to expand...
Click to collapse
Are you using the feb 3rd beta version of spirit?
The stock FM radio is probably going to need to be rebuilt to make it work. Or there is just some strange file that is missing or not configured right.
chevycowboyusa said:
Are you using the feb 3rd beta version of spirit?
The stock FM radio is probably going to need to be rebuilt to make it work. Or there is just some strange file that is missing or not configured right.
Click to expand...
Click to collapse
Sense Apps do not work on AOSP roms. And can't be made to work...
FM Radio
dcacklam said:
Sense Apps do not work on AOSP roms. And can't be made to work...
Click to expand...
Click to collapse
Hi Dave! Thanks for the response
I thought there was an FM radio app in the CM Builds??
There are people using Spirit on CM10 (other devices) and I have got Spirit working on Sense 4 (even though the built in one doesn't work)
I have tried my darndest to get Spirit radio to work. All I get is white noise.
What am I missing or not configured? I did search the site, but wasn't able to
find the answer.
Thanks.
mgp53 said:
I have tried my darndest to get Spirit radio to work. All I get is white noise.
What am I missing or not configured? I did search the site, but wasn't able to
find the answer.
Thanks.
Click to expand...
Click to collapse
I couldn't get it to work either on the PacMan rom
I just flashed SpeedRom 9.0 Beta 1 and the FM Radio app works because SpeedROM is still a sense based ROM but looks like JellyBean.
Viper Radio
chevycowboyusa said:
I'm using spirit and it works fine. You do need to have a headset plugged in though for an antenna
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
I have used viper from version 1.6.6, 1.7.0.1 and 1.7.0.2, the fm radio never worked. even when i used spirit FM it only just make noise as if no station is working.
kodunmit said:
I have used viper from version 1.6.6, 1.7.0.1 and 1.7.0.2, the fm radio never worked. even when i used spirit FM it only just make noise as if no station is working.
Click to expand...
Click to collapse
That's strange. Where are you located?
I'm in California.
Not much proof, but this is it working.
Sent from my HTC_Amaze_4G using xda app-developers app
chevycowboyusa said:
That's strange. Where are you located?
I'm in California.
Not much proof, but this is it working.
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
I have the same issue with Sportsstar's CM10.1. Sprit FM just gives me static (though I can occasionally hear the slightest bit of an actual station). I think I read in his thread that radio firmware is missing from CM10.1. Is that something one can flash after the fact?
Firmware
JimDandy68 said:
I have the same issue with Sportsstar's CM10.1. Sprit FM just gives me static (though I can occasionally hear the slightest bit of an actual station). I think I read in his thread that radio firmware is missing from CM10.1. Is that something one can flash after the fact?
Click to expand...
Click to collapse
There is a difference Between the Radio firmware for the hardware (flashed thru hboot) and possibly radio drivers in the ROM.
You can flash the ICS Radio update, link in my Viper thread or ARHD thread, that will update you to the most recent radio "Firmware"
You do need to have an antenna (wired headset) and you have to manually tune the radio station.
I'll test it on CM10.1 later this weekend and I'll let you know what I can figure out!
chevycowboyusa said:
There is a difference Between the Radio firmware for the hardware (flashed thru hboot) and possibly radio drivers in the ROM.
You can flash the ICS Radio update, link in my Viper thread or ARHD thread, that will update you to the most recent radio "Firmware"
You do need to have an antenna (wired headset) and you have to manually tune the radio station.
I'll test it on CM10.1 later this weekend and I'll let you know what I can figure out!
Click to expand...
Click to collapse
Thanks, Chevy
I can't find the reference I was talking about, but here's a reference to missing drivers: http://forum.xda-developers.com/showthread.php?t=2010901
And if this is what you're talking about for a radio update - http://forum.xda-developers.com/showthread.php?p=42317972&highlight=radio+update#post42317972 - that matches my current baseband version.
FM radio works on ICS ROMs, like ARHD and SpeedRom, I know. I also know I need a headset attached - only way it ever worked. I've seen other threads about Spirit FM just producing static, so I don't know if it's that app and this device. Anyway, thanks for whatever you can figure out. My thought was that flashing anything ICS on JB wouldn't work, but I don't know.
JimDandy68 said:
Thanks, Chevy
I can't find the reference I was talking about, but here's a reference to missing drivers: http://forum.xda-developers.com/showthread.php?t=2010901
And if this is what you're talking about for a radio update - http://forum.xda-developers.com/showthread.php?p=42317972&highlight=radio+update#post42317972 - that matches my current baseband version.
FM radio works on ICS ROMs, like ARHD and SpeedRom, I know. I also know I need a headset attached - only way it ever worked. I've seen other threads about Spirit FM just producing static, so I don't know if it's that app and this device. Anyway, thanks for whatever you can figure out. My thought was that flashing anything ICS on JB wouldn't work, but I don't know.
Click to expand...
Click to collapse
Just want to ask again on this thread, has anyone ever gotten Spirit FM or another FM radio apk to work on a JB ROM (non-sense-based)? Chevy mentioned the Spirit FM 3rd beta, but not sure whether he was talking about having it work on a JB ROM or on Viper. ICS ROMs mostly have the stock radio app working, so not an issue there.
Thanks.
There is code in the CM base sources allowing for radio apps like spirit FM, now whether the devs working on it here have enabled it or gone through the task of debugging to ensure it works is a different story. Tytung has it working well in his CM ROMs for the HD2. I purchased it (spirit) to use on his ROMs so I do know it can work with CM if the developer chooses to. Frankly, for me this capability isn't as important as resolving the other outstanding issues which are keeping JellyBean from being fully functional and truly stable on our devices.
Odysseus1962 said:
There is code in the CM base sources allowing for radio apps like spirit FM, now whether the devs working on it here have enabled it or gone through the task of debugging to ensure it works is a different story. Tytung has it working well in his CM ROMs for the HD2. I purchased it (spirit) to use on his ROMs so I do know it can work with CM if the developer chooses to. Frankly, for me this capability isn't as important as resolving the other outstanding issues which are keeping JellyBean from being fully functional and truly stable on our devices.
Click to expand...
Click to collapse
Yeah, I'm really just trying to find out if anyone has gotten something working on the Amaze, not any other device. For me, the showstoppers on CM10.1 were uncontrolled in-call volume (evidently working in Evervolv), audio drop-outs when listening to music, and lack of FM radio. Otherwise, it seemed really solid. I'm kinda tired of laggy ICS ROMS, but everything works.
Thanks
JimDandy68 said:
Yeah, I'm really just trying to find out if anyone has gotten something working on the Amaze, not any other device. For me, the showstoppers on CM10.1 were uncontrolled in-call volume (evidently working in Evervolv), audio drop-outs when listening to music, and lack of FM radio. Otherwise, it seemed really solid. I'm kinda tired of laggy ICS ROMS, but everything works.
Thanks
Click to expand...
Click to collapse
I know what you're talking about. I think many here, myself included, wish that development was further along. Frankly, I find it sad and ironic that my old HD2, which was a Windows phone, has had fully functional usable stable Jellybean ROMs for a well over a year and it never had any sources released to develop from.
The sad truth is that the Amaze is a great device that wasn't marketed well, so few units were sold. Too few at least for it to have developed a devoted loyal following. If you follow the threads you see that there was never a large volume of development for it and that most of the early adopters have long since moved on to other devices. I'm just glad that we're now experiencing a second wave with new folks stepping up and trying.
I'm optimistic that the issues currently afflicting these builds can be resolved and that our Amazes will get a new lease on life. We just need to have a bit more patience, they're getting closer to nailing it. Once one gets it right the others will learn and use in their development. Then we'll have all kinds of jellybean and KitKat flavors to choose from.
Odysseus1962 said:
I'm optimistic that the issues currently afflicting these builds can be resolved and that our Amazes will get a new lease on life. We just need to have a bit more patience, they're getting closer to nailing it. Once one gets it right the others will learn and use in their development. Then we'll have all kinds of jellybean and KitKat flavors to choose from.
Click to expand...
Click to collapse
Hope your optimism proves right. It's amazing (no pun intended) that anyone spends there time doing this kind of dev work at all. Pretty sure I'll never buy another HTC device, too.
JimDandy68 said:
Hope your optimism proves right. It's amazing (no pun intended) that anyone spends there time doing this kind of dev work at all. Pretty sure I'll never buy another HTC device, too.
Click to expand...
Click to collapse
I wouldn't be so down on HTC. They may not have been the most supportive manufacturer when it comes to outside development, but they've also produced some of the most groundbreaking innovative products. They're in financial trouble now, as their market share has eroded, and haven't had a breakout device in some time. They realize this and have begun making incremental improvements within the development community in an attempt to improve it's perception. The thing is who are you going to jump ship to? Samsung is already undermining android by developing Its own market place for apps that can only run on their devices and has announced It's developing its own proprietary OS. Since they're the biggest player in this device market, they could easily splinter Android and force other manufacturers to do the same to compete.
The point is, if there's one thing I've learned from my 50 years on this planet is to never say never about anything.
Odysseus1962 said:
The point is, if there's one thing I've learned from my 50 years on this planet is to never say never about anything.
Click to expand...
Click to collapse
Point taken. I'm 45 and evidently haven't learned anything. :cyclops:
Time to go back to a landline.
Hello, I recently found a TP2 taking care of my dust and I was wondering if there are any Android ROMs for the phone. I know there are some, but I wanna know what's the ROM with the newest version of Android.
Thanks.
speakerstick said:
Hello, I recently found a TP2 taking care of my dust and I was wondering if there are any Android ROMs for the phone. I know there are some, but I wanna know what's the ROM with the newest version of Android.
Thanks.
Click to expand...
Click to collapse
the newest android version you can get is 2.3.7 gingerbread
thanks to xdandroid
http://xdandroid.com/wiki/Main_Page
battery indicator is kinda broken and also my phone used to overheat.... alot. there's also the froyo build (2.2 version), which might be more stable.
you have to find out for yourself which one works the best.
there's also an android 4 rom, but lots of features are not working. check it out yourself.
http://forum.xda-developers.com/showthread.php?t=1636005
CM7 for rhodium is interesting too, tho i couldn't get it to work somehow (difficulties flashing)
http://forum.xda-developers.com/showthread.php?t=1566955
plrusek said:
the newest android version you can get is 2.3.7 gingerbread
thanks to xdandroid
http://xdandroid.com/wiki/Main_Page
battery indicator is kinda broken and also my phone used to overheat.... alot. there's also the froyo build (2.2 version), which might be more stable.
you have to find out for yourself which one works the best.
there's also an android 4 rom, but lots of features are not working. check it out yourself.
http://forum.xda-developers.com/showthread.php?t=1636005
CM7 for rhodium is interesting too, tho i couldn't get it to work somehow (difficulties flashing)
http://forum.xda-developers.com/showthread.php?t=1566955
Click to expand...
Click to collapse
Ok, I did it, I used XDAndroid, but, is there a way to boot into android without Windows Mobile?
Thanks
speakerstick said:
Ok, I did it, I used XDAndroid, but, is there a way to boot into android without Windows Mobile?
Thanks
Click to expand...
Click to collapse
OMGB on NAND
http://forum.xda-developers.com/showthread.php?t=1347321
http://forum.xda-developers.com/showthread.php?t=1965459
Ok... I tried to install xdandroid GBX0, but wifi doesn't work, and then I went back to FRX0 and wifi doesn't work either... What do I do?
Help!
Thanks
wifi problems?
speakerstick said:
Ok... I tried to install xdandroid GBX0, but wifi doesn't work, and then I went back to FRX0 and wifi doesn't work either... What do I do?
Help!
Thanks
Click to expand...
Click to collapse
Why do you say the wifi doesn't work? I've been using Android on my Rhodium since June 2012 and I don't have problems with wifi--bluetooth, yes, but not wifi.
What makes you say it doesn't work? Is it not showing any wireless networks?
what version of the rhodium do you have? RHOD100? RHOD400? I have a RHOD400, and the devs are also using RHOD400's. They don't guarantee complete functionality on non-RHOD400's (that's actually mentioned somewhat by wizardknight at the end of post #1 of the GBX0* thread that wizardknight linked above
Hello, I too am having lots of troubles with finding a ROM that will work on my RHOD300. I started the whole install with a GBX_3.4.35_Full, then the GBX_3.4.26.13_FULL then the OMGB 1.2.3 May 4 and finally the OMGB Jan 16, and all of them have given me a non-working wi-fi. When I enable the bluetooth it actually turns on ok.
I've been using my HTC TP2 for 4 years as a WinMO phone and finally decided that I'd give this Android thing a try. The wi-fi has been working for me all along.
When I first installed the GBX it was giving me Wi-Fi error (viewing in Wireless & network settings). After I switched to the OMGB ROM I'm now getting a Wi-Fi turning on... and the option is grayed out.
I've been searching around and reading through these forums and I'm trying to find solutions, but nothing seems to work. The wifi-nvram-generic.txt file option I wish I could try but unfortunately I don't know the phones mac address without booting back into a WinMo phone.
I would be grateful if somebody could help me sort this out as I really do need to have wifi on my phone, otherwise my smart phone isn't so smart after all...
I've taken my RHOD100 out of the dust, and fired it up to NAND flash it with te 2.3.7 xda ROM. I used the GBX0*+3.4.26.13 Full for my device. Although it's not very snappy, it's acceptable after recalibrating the touch screen. Don't expect miracles. Wifi is working fine. Haven't tested BT yet.
The 3.4.35 version did boot a bit, but didn't get past the bootscreen, which seemed to be in an unending loop.
I doubt the GPS is working.. GPS test didn't get a fix in 15 minutes and did not see any satelites. Also no support for front camera... but hey.. who cares