Hi guys,
First off, I used this forum 2-3 months ago to update from basic viewsonic g tab software to Vegan 7, thank you so so much for all the input. Could not have done it without the great posts.
In need of help again. I've researched my issues but haven't found an answer that was clear enough that made sense for me.
I have an issue of files deleting themselves, but I believe I found the answer from a poster named generosity, thank you I will try that.
My real issue now is that I have no sound for video. The speakers don't work until i plug in and unplug a headset. my research has indicated all the fixes are temporary, such as plug in headset to make it work. I want a permanent solution because I use this for my young daughter and she isn't capable of rolling headsets or pluggin them in yet lol.
So, my questions are.. is there a permanent fix in the software I am running now? Is there an update to the vegan software(i didn't see one) which caused me to look for a downgrade but all I saw was vegan 5.1 which was beta also. I dont see any reason why 5.1 wouldn't work if we know things run well on it??? I also saw a little bit newer kernel, will upgrading the kernel fix it absolutely? As I said, upgrade/downgrade, just a way to get to something stable.
If you have solutions to my question and it is an upgrade or downgrade of anything, please post the link to how to do it.
Thank you so much and I hope I didn't beat a topic that has already been covered.
Below is my build.
10" viewsonic g tablet
Mod Version Vegan-7.0.0-RC1 -Harmony
Build number GRI40
Kernel 2.6.32.36 cyanogenmod from pershoot
-jlocoxda
Related
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.
Hi guys, I have a rooted Bolt currently running 1.70.605.0. I rooted when i got it back in May and since then I installed a rooted update of Froyo. The phone has been dropping network connection a lot lately that it's very aggrevating. I am thinking it may help fix my problem if I update to Gingerbread with the new radio.
i downloaded the file 2.11.605.3.zip from the TeamBamF.net site last night but now I am sort stuck. It's been so long since I rooted this phone so I kinda need some help. I search everywhere but haven't found a thread where there is like a step by step direction. If someone can provide me some assistance or point me to the right thread I would so much appreciate it.
Vince
The data dropping out may be due to some work/upgrades in your area ... call VZW to see if they know anything.
As far as updating to GB, my advice is tread lightly ... especially if you're just wanting a stock version of it. There are bugs, the biggest being voice mail notifications not working, that may drive you nuts. That being said, there are several custom ROMs around that have fixes/tweaks that make this plagued GB build VZW & HTC released much more manageable. Look around and there are a few "stock" custom ROMs out there - or if you prefer a totally different look/feel there are several Sense 3.0 ports to choose from too.
As far as a how-to guide, the best one I've seen is THIS ONE. Read it and get knowledge my friend
Happy flashing!
2.11.605.3.zip is the [gb] patch - "It changes camera libs, and some insignificant
framework, and apks." as stated on teambamf.net, i did read it is running smooth,
increased battery life but,with issues pertaining to vm notification error and front facing camera
upside down. i agree with Yank talk with carrier, im currently running dasBAMF Forever
kernel 2.6.35.10 stock radios have had no issues.
vinny2006 said:
Hi guys, I have a rooted Bolt currently running 1.70.605.0. I rooted when i got it back in May and since then I installed a rooted update of Froyo. The phone has been dropping network connection a lot lately that it's very aggrevating. I am thinking it may help fix my problem if I update to Gingerbread with the new radio.
i downloaded the file 2.11.605.3.zip from the TeamBamF.net site last night but now I am sort stuck. It's been so long since I rooted this phone so I kinda need some help. I search everywhere but haven't found a thread where there is like a step by step direction. If someone can provide me some assistance or point me to the right thread I would so much appreciate it.
Vince
Click to expand...
Click to collapse
Can you link me to that download? I would like to see exactly what you are making reference to before I comment.
Some of those update .zips are the full unrooted rom. You wouldn't want to flash that. You want to make sure and look for something like...
"Rooted Debloat Blah Blah Blah"
The link provided by Yank is a good one. #3 for "Flashing a Rom".
Also another hint (just in case you are unfamiliar with recovery). the camera buttons toggle up/down and the power button is used to make a selection. you can select "go back" by toggling to it and selecting it or you can use the soft back key.
hope that helps.
As to the voicemail issue, Eris has fixed that. Took him 30 minutes, he said.
Sent from my ADR6400L using Tapatalk
Did you read this?
http://teambamf.net/showthread.php/718-How-to-flash-a-ROM
I've been having this issue since I first flashed a LiquidSmooth ROM a couple months back, but as I've installed official CM10.1 and AOKP roms, the issue has persisted across them. Currently I have Avatar 2.13b on slot 1, AOSP r6 on slot 2 and LiquidSmooth 2.4 in slot 3 and the problem exists on all 3. Bluetooth will work fine on an initial flash, but a some point later on, it disables itself, and the only way to get it back is to wipe dalvik and reboot. Is this simply an instability of the kexec kernel, or something more. I've seen a few posts related to this, but not enough that it seems like a common issue. Any one else having this problem or any thoughts on why its happening to my RAZR MAXX xt912? Wiping dalvik isn't a huge inconvenience, as I typically only use BT to and from work, but after a long day in the office, not being able to connect my headphones can just add to my frustrations. Any thoughts or help is greatly appreciated, thanks in advance!
Did you ever make any progress on this problem? I'm having a similar, tho not identical, BT problem . . . posted it, hoping to get some idea how to approach it. Thanks
Sorry, no luck yet. Happened today while sitting idle at my desk, no reboot, not even being used. If I run into a solution on another site, I'll update this post
Posted from along the edge of a straight Razr
psudeke said:
Sorry, no luck yet. Happened today while sitting idle at my desk, no reboot, not even being used. If I run into a solution on another site, I'll update this post
Posted from along the edge of a straight Razr
Click to expand...
Click to collapse
Too bad. I was hoping to piggyback, or at least get some insight.
I like to think I'm not an idiot, but short of changing hardware I can't think of anything new to even try.
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
Hi there, everyone. Relatively new to all this custom rom stuff, but I have been able to change roms and such with a usable level of success. A few months ago I ran into an issue that I can't seem to fix on my own, so I'm reaching out to see if someone more knowledgeable might have some experience and can point me in the right direction.
After test-driving a few different roms for a few months at a time, I ended up trying out ArrowOS. While I really enjoyed the rom itself, my phone would only ever use the speaker phone, even when it was set to use the regular ear speaker. Recently, I changed to LineageOS thinking the issue was with the Arrow rom, but the issue persists. I figured it was a firmware issue so today I flashed the firmware package and, to my surprise, the phone is still behaving the same way.
The firmware I flashed in was (fw_curtana_miui_CURTANAGlobal_V12.5.6.0.RJWMIXM_84796eb2cc_11.0.zip). It flashed with no errors, so I assume everything is fine there.
Anyone have any tips for me to follow? Much appreciated!
EDIT: This might be a newbie mistake, but the firmware I have flashed says it's for Android11 and the LineageOS I'm using is an Android 12 base. I wouldn't think it would make such a difference, but this is coming from a long-time Windows user who is used to getting by on old drivers when necessary. The ArrowOS I was using when the problem first popped up was Android 11, but I hadn't updated the firmware of the device so it may have still been on Android 10 (or even 9, I don't know).
Double posting for clarity. After trying multiple roms and firmwares, the problem still persists. The weirdest thing is that when using a hardware testing app, the earpiece speaker works fine. I've also tried using other dialer apps and they all act the same way. I am completely stumped on this. If anyone can help I would appreciate it, otherwise I guess I give up. This is way beyond me.