Related
I take no credit for this, all I did was build it from the BravoC build tree and add in the latest kernel that Kali posted in the blitzrom thread.
NEW BUILD UP!! flashable over previous release.
What works:
- wifi (and wifi hotspot)
- back-light turns off
- optical joystick
- video camera mode is selectable (but doesn't record)
- USAA (maybe all protected?) app is in market and usable for deposit.
- Voice input using the IME_Mod keyboard
what's broken:
- video camera does not record
- MMS sending (this has been true of every AOSP rom I have used on both Hero and Desire)
Download it here: http://www.4shared.com/file/M6VjXyKg/update-cm-610-RC0-10082010-Des.html
flash this kernel to fix wifi: http://dl.dropbox.com/u/1694782/kern35-cdma-final.zip
get the google apps here: http://mirror.teamdouche.net/get/various/gapps-hdpi-20100930-signed.zip
Old version(s):
http://www.4shared.com/file/vdi43Lay/update-cm-610-RC0-DesireC-sign.html posted 10/07
IP
IPfreely, I LOVE your test build. I am getting the same errors that you said what happened. if you need a tester i will be freely to help out, or Blitz1290 test build also.
Kali -
Blitz -
IPFreely -
You guy's ROCK!!
Thanks for all that you have Done. -
Tom
Nice to see CM 6.1 finally surfacing, though my Desire is HSPA so I guess I'll wait (using nightly CM6 atm). Is this version using the HTC released kernel?
sookster54 said:
Nice to see CM 6.1 finally surfacing, though my Desire is HSPA so I guess I'll wait (using nightly CM6 atm). Is this version using the HTC released kernel?
Click to expand...
Click to collapse
this WILL NOT WORK ON HSPA DESIRES! this is ONLY for CDMA desires. (we need a cdma forum!) the kernel I'm using is the cyanogen-mod kernel with some patches by Kali that he based off the HTC source code.
The nightlies you are using are probably further along than this anyway, this was a quick and dirty test build I whipped up because I could find nothing in the way of cyanogen-mod for the CDMA desire, closest was Blitzrom but that was just plain AOSP and lacked the cool cyanogen features.
LOL that's why I said "I'll wait"
I could not get this to load. Am I missing something
what did you do exactly? any errors?
standard rom loading procedure that works for me is:
1. nandroid backup
2. wipe data/cache/dalvik
3. install rom.zip
4. install google apps.zip
5. reboot
dave0812 said:
I could not get this to load. Am I missing something
Click to expand...
Click to collapse
updated my first post with a patch for the roaming indicator. I put in my carrier ACS, if your on another carrier sorry but now you get to feel my pain as all the Hero roms I used said sprint
if you wish to customize for your carrier follow this:
http://www.droidforums.net/forum/droid-hacks/57078-how-edit-eri-xml.html
Hell ya its about time an aosp banner said ACS!!!!
Sent from my HERO200 using XDA App
I'm a little confused as to why the roaming fix didn't work for me. I flashed the "roaming-fixed.zip" archive, but I still see the roaming indicator. I'm on the same network, ACS, if that helps at all. I didn't get a boot loop, but my DesireC still thinks it's roaming. Any help would be appreciated. Thanks in advance!
New build is up!
http://www.4shared.com/file/M6VjXyKg/update-cm-610-RC0-10082010-Des.html
integrates latest kernel from Kali and my roaming patch. WIFI WORKS!
thanks for the good work i will give this a shot maybe tomorrow. just curious what cdma network are you running on in AK? i am on cellular south in alabama and can't wait to try this out.
I'm with Alaska Communications http://alaskacommunications.com/
They are an ACG member just like cellular south. same version of the hardware and same radio. the build.prop is setup like USCC but that doesn't really matter much. I ran CM6 on my ACS hero with a sprint build.prop just fine.
crackzattic said:
thanks for the good work i will give this a shot maybe tomorrow. just curious what cdma network are you running on in AK? i am on cellular south in alabama and can't wait to try this out.
Click to expand...
Click to collapse
Thanks for doing this. I've been wanting to test drive CM6 for a while now. Having some issues though. I'm still not getting wifi to work. So far the only thing that seems different from the first build is that the roaming indicator is off. When I tried to reboot using the reboot option from the power menu it got stuck in a boot loop. It started fine after I pulled the battery. After rebooting none of my widgets would load. I had to redo all of them. Also, when I was talking on the phone yesterday it got really hot. This doesn't make sense to me since I have it set to clock at 245 with the screen off. And is portable hotspot supposed to be working? It seems to react the same way as it does with wifi.
Gave this a whirl, and I am encountering a problem with my wifi not working, it's giving me an error. Everything else seems good though.
not sure what happened with the wifi, but if you flash this kernel it works (hotspot too) http://dl.dropbox.com/u/1694782/kern35-cdma-final.zip
i remember inserting that kernel into the build, but sure enough, didn't work until i flashed it separately.
i've noticed that my widgets seem to stretch oddly. anyone else having that issue?
psychache that's odd about the reboot boot loop. mine has rebooted fine both normally and recovery over a dozen times. I tried on a second desire i have access too and it worked fine as well.
Just so you guys know.. Kali- has built a fully working CM 6.1 for the CDMA Desire.
Get in #teamdesire
fully working as in video camera too?
i just popped into the channel and all i see are nightlies for the gsm desire. only cdma link is to unrevoked forever.
blkqi said:
Just so you guys know.. Kali- has built a fully working CM 6.1 for the CDMA Desire.
Get in #teamdesire
Click to expand...
Click to collapse
blkqi said:
Just so you guys know.. Kali- has built a fully working CM 6.1 for the CDMA Desire.
Get in #teamdesire
Click to expand...
Click to collapse
Did you have any issues after rebooting? I lost all my widgets when I did, meaning I can't use any of widgets other than the preinstalled stuff.
did you move any of the apps associated with those widgets to sd card? or perhaps set install location to sd card? you cannot store widgets on sd.
psychache said:
Did you have any issues after rebooting? I lost all my widgets when I did, meaning I can't use any of widgets other than the preinstalled stuff.
Click to expand...
Click to collapse
All credit goes the great mike1986. as this was taken from his thread.
Thanks to him Ive successfully been able to fix the bluetooth voice earpiece feature that was not working on the Rom in the signature.
Ive flashed my share of Froyo Roms and it seems that a lot of them have the same problem as well as some Gingerbread maybe.
The idea is to push the call/end button on your bluetooth connected earpiece to do various call related features without having to grab your phone, its all controlled via voice command.
Many people have been looking for a fix for this.. well here it is.
Directions:
Flash via CWM, reboot and you should have the feature fully functional.
*More information on what this does here: http://www.androidtapp.com/true-hands-free-driving-and-bluetooth-voice-dialing-is-in-android-2-2/
Additionally here is a video on the Voice Actions for Android, NOTE: This is different from the Bluetooth Voice Dialer as it has additional features
http://www.youtube.com/watch?v=tPPcTN5sdX4
and
http://www.youtube.com/watch?v=8Ml34vtrGwc
Wow, this is fantastic. I was following the info posted in that AR 3.2 thread, so I'm happy to see something posted.
I'll give this a try tonight.
legend221 said:
Thanks to him Ive successfully been able to fix the bluetooth voice earpiece feature that was not working on the Rom in the signature.
Click to expand...
Click to collapse
I'm running RCMix 5.3 and the BT voice dialer works alright for me. Do I need this fix? The one thing I'd really like from the current ROM for BT voice dialing is to have a tone to cue me when the applet is ready to listen.
BillTheCat said:
I'm running RCMix 5.3 and the BT voice dialer works alright for me. Do I need this fix? The one thing I'd really like from the current ROM for BT voice dialing is to have a tone to cue me when the applet is ready to listen.
Click to expand...
Click to collapse
Thats exactly what this does, install and you'll see this for yourself mate.
Sent from my fast / stable HTC Inspire 4G
I am running AR 5.1.3. Voice dial works fine from the phone but when I try to initiate it from my bluetooth headset I get a Force Close of processcom.android.voicedialer. I uninstalled voice dialer with TB and then installed the bluetooth voice dialer from this thread via CWM and I still get the force close when initiating from my bluetooth.
Any ideas on how I can fix this other than flashing a new rom?
Okay I just flashed to LeeDroid which claims to have fixed the Bluetooth Voice Dial Problem and I still get a force close when initiating it from my headset.
Anyone have any ideas please????
Wow this is cool to have. Im not having much accuracy though. Ive got a 2 year old Jawbone Prime so my bets are that its the problem. Looks cool but hasnt played nice since day one. Anyhow this does work if you got a decent headset
Did you ever figure this out?
toadleyb said:
Okay I just flashed to LeeDroid which claims to have fixed the Bluetooth Voice Dial Problem and I still get a force close when initiating it from my headset.
Anyone have any ideas please????
Click to expand...
Click to collapse
svarzaru said:
Did you ever figure this out?
Click to expand...
Click to collapse
I'm having the same problem and would really like to see this fixed. When I tap the voice dialer app on the phone, it works as it should. However, it always FC when pressing the bluetooth button. I think the settings file associated with connecting the bluetooth button to the app is the problem, but I don't know what file it is or how to make it better.
xperi said:
I'm having the same problem and would really like to see this fixed. When I tap the voice dialer app on the phone, it works as it should. However, it always FC when pressing the bluetooth button. I think the settings file associated with connecting the bluetooth button to the app is the problem, but I don't know what file it is or how to make it better.
Click to expand...
Click to collapse
Download Cyberon Voice from the market. It does cost a couple of bucks but it makes all problem go away on every rom you need BT with. At least for me it did!
Confirmed working with Virtuous Unity 1.24.0 Sense 3.0 based on Pyramid with Vlingo
Man just what I was looking for will give it a try.....Thanks
Sent from my Inspire 4g using XDA Premium App
missing voice dialer
I tried to flash it, and it didn't do anything. I'm using Virtuous Unity v1.27.0. I even tried to extract the app from the zip (which currently doesn't exist on my phone) and install that way, but it says "application not installed". Nothing happens at all when i hit the button on my bluetooth. With the stock rom, before installing VU, it would pull up the voice dialer. But i can't even install it now. Can anyone help me out? Thanks!
EDIT: Got it to install, but now it force closes when I try to use it, with or without a bluetooth headset.
awesome!!!!!
I'm running AHD 6.1 but it lacks the ability to let bluetooth headset to do voice command. but after i flashed this it worked out fine!!
and btw im using vlingo to do voice dialing, its an awesome app!!
legend221 said:
All credit goes the great mike1986. as this was taken from his thread.
Thanks to him Ive successfully been able to fix the bluetooth voice earpiece feature that was not working on the Rom in the signature.
Ive flashed my share of Froyo Roms and it seems that a lot of them have the same problem as well as some Gingerbread maybe.
The idea is to push the call/end button on your bluetooth connected earpiece to do various call related features without having to grab your phone, its all controlled via voice command.
Many people have been looking for a fix for this.. well here it is.
Directions:
Flash via CWM, reboot and you should have the feature fully functional.
*More information on what this does here: http://www.androidtapp.com/true-hands-free-driving-and-bluetooth-voice-dialing-is-in-android-2-2/
Click to expand...
Click to collapse
Will this work with Gingerbread ROMs? mike1986's current DHD/Inspire4G ROM does not support voice dialing via bluetooth. Kind of a pain in the rear not having it!
crypted said:
Will this work with Gingerbread ROMs? mike1986's current DHD/Inspire4G ROM does not support voice dialing via bluetooth. Kind of a pain in the rear not having it!
Click to expand...
Click to collapse
The post before yours says they're running "AHD" 6.1 with this dialer and it works fine. I'm assuming this was supposed to be ARHD 6.1 which is a GB ROM
homeslice976 said:
The post before yours says they're running "AHD" 6.1 with this dialer and it works fine. I'm assuming this was supposed to be ARHD 6.1 which is a GB ROM
Click to expand...
Click to collapse
Yeah, I wasn't clear. I figured it would work since it worked on the one before, but I wasn't sure if the previous post was confirming 6.1.0 or 6.1.1. So, I'm hoping for 6.1.1 support confirmation so I don't brick this puppy.
crypted said:
Yeah, I wasn't clear. I figured it would work since it worked on the one before, but I wasn't sure if the previous post was confirming 6.1.0 or 6.1.1. So, I'm hoping for 6.1.1 support confirmation so I don't brick this puppy.
Click to expand...
Click to collapse
6.1.0 was the first version of his new base (2.3.5GB based on HTC 3.06.405.1)
6.1.1 is the same base with updates/enhancements from mike1986. I can't imagine this would bork you. If you're too worried, make a backup. This isn't going to brick your phone to a point where you can't get to recovery and flash your backup
homeslice976 said:
6.1.0 was the first version of his new base (2.3.5GB based on HTC 3.06.405.1)
6.1.1 is the same base with updates/enhancements from mike1986. I can't imagine this would bork you. If you're too worried, make a backup. This isn't going to brick your phone to a point where you can't get to recovery and flash your backup
Click to expand...
Click to collapse
Right. That was my assumption and my plan once I got home tonight to do that assuming no-one confirmed it for me. Will flash after while and edit post with results.
I flashed this to arhd 6.1.1. It don't work. App did not appear to be installed. I tried installing the apk and it would just say application not installed.
So it appears to be a no go.
Sent from my HTC Inspire 4G using XDA App
FYI, there is an issue with pretty much all ICS ROMs and the BT stack included in them. I have a brand new, top of the line Jawbone BT that supports everything, works flawlessly in Cyanogen and non-ICS ROMs, but will barely work in ICS.
Basically, after a reboot, it connects and says Connected (no media), then switches to Connected. Everything works fine until I disconnect and reconnect again.
After that, it will work for only voice calls. Media will always go out the speaker. I have tried everything to fix it to no avail. The only resolution to get A2DP media streaming back is to reboot.
When it happens, the media checkbox is still there and checked, but it doesn't work. I switched back to HyperSensation (Cyanogen) and everything works as it is supposed to.
Apparently ICS bluetooth works fine for some BT headsets and not others. This also seems to be an ongoing problem for other phones as well, even non-ICS.
I am not well versed in reading the debug logs, but if anyone is interested I can post them here, provided they tell me which ones they want.
I'm having troubles to. My problem is I cannot start a call via the Bluetooth Dial button on my radio. It's as if the phone doesn't even recognize that you are pressing the button. Tried installing Vlingo, but the prompt doesn't even work anymore.
The old solution was to install the Voice_dialer.apk...but that doesn't seem to be compat either
I can confirm the issue with the virtuous ICS as well. I have bt stuff from Jawbones to BlueAnt's and all have the same issue. Prior to this was the issue of cutting out and now it's the off/on bt streaming. To "fix" the issue, is to reboot. Annoying yes. But ICS is still so sexy
I've got the same problem, ROM Elegancia ICS 1.0.6 and 1.1.0
After pairing with bluetooth headset, first time I play music everything is ok. after re-connecting, music controls works ok, but sound is thru phone's speakear not thru the headset.
After rebooting the phone the situation is the same- first connection everythings ok, another ones not.
Checked with SE MW600, Jabra extreme and car's bluetooth.
The problem occurs even with clear installation (before I restore backups).
Still can not find solution so I got back to GB.
So its not just me! I can confirm that my Beats Wireless acts exactly like described.. And with a reboot fixing it again!
I think the devs here might be able to fix it, but its properly not going to be an importent issue to fix.. Fingers crossed for a fix, or maybe the future leaks will have it done!
Sendt fra min HTC Sensation Z710e med Tapatalk
ftblstr2319 said:
I'm having troubles to. My problem is I cannot start a call via the Bluetooth Dial button on my radio. It's as if the phone doesn't even recognize that you are pressing the button. Tried installing Vlingo, but the prompt doesn't even work anymore.
The old solution was to install the Voice_dialer.apk...but that doesn't seem to be compat either
Click to expand...
Click to collapse
Vlingo has always been problematic for me... My solution (worked on ICS too) was to get it working on an older ROM (not sure which one anymore) then use titanium backup and back up APP+DATA on a ROM that it is working on. Then, restore APP+DATA on the new ROM.
The first time you hit the button on your headset it will ask you what app you want to use for voice dialing and give you Vlingo, Vlingo InCar, or Voice Search. Choose Vlingo and check the box to make it default and you are good to go.
Just make sure after you get it working on the new ROM to back it up again... then the next time you switch ROMs, restore whatever the latest backup is. I am not sure what it changes, but I have been through Cyanogen, all of the ARHD versions, all of the InsertCoin versions, and a few others (I can never make up my mind on ROMs) and this trick has worked in all of them.
IMPORTANT: Make sure in Titanium Backup to uncheck the option to restore system libraries in ROM (that can cause issues going between major versions of android), and make sure toenable the features in Titanium Backup for attempting to migrate data.
I also get the same issue when I try to connect my MW-600 with ARHD ICS 6.0.2.
Can anyone help?
You guys who just have to reboot your phone are getting off easy. When I lose Audio Streaming to my car head unit, I have to delete the device and re-pair it to my phone after a reboot.
Same here with mw600 on virtuous Inquisition 2.0.1. Only first connection plays music through headset.
I am sure that first 4.0.1 beta base was not affected. This bug came with 4.0.3
Sent from my HTC Sensation using Tapatalk
dante-fu said:
Same here with mw600 on virtuous Inquisition 2.0.1. Only first connection plays music through headset.
I am sure that first 4.0.1 beta base was not affected. This bug came with 4.0.3
Sent from my HTC Sensation using Tapatalk
Click to expand...
Click to collapse
really??.. Im gonna try an old backup then.
Edit:
Backup was removed sadly.. :/ cant test it, but maybe someone else can?
Well, the ROMs are still there to download
With 4.0.1 I was on radio version 10.59. I am not expert on radios and RILs but I guess these things affect also BT performance. Right?
Sent from my HTC Sensation using Tapatalk
Shidapu said:
really??.. Im gonna try an old backup then.
Edit:
Backup was removed sadly.. :/ cant test it, but maybe someone else can?
Click to expand...
Click to collapse
I reverted back to the virtuous 4.0.1 build from the most recent (having the new fw and radio) and has fixed the Bluetooth issue. Now I just have to live with messed up signal bars and a browser that randomly exits.
Sent from my HTC Sensation using xda premium
Hi,
Reporting this BT issue for me (SGS 2 with ICS 4.0.3, XXLP2 that can be found on XDA, originally from samfirmware):
I try to send files from my laptop to my SGS 2, 1 at a time and the transfer will suddendly halt some of the way through and ICS looks like it's rebooting but it's actually not, I mean not a full proper reboot; the phone does not switch off, the boot anim plays as if restarting, first BT is off then the icon come up in the top bar...
Hopefully, the Simple & Clean, ICS version, is round the corner ;o)
beng
using arhd 6.1.1 here on sensation XE with SE mw600 headset, no issues, calls and media working as normal
BT connectivity seems to be fixed in the latest leaked ICS + Sense RUU.
Is the sensation supposed to support any other remote control features than pause and play over BT?
I can confirm that on my Galaxy s2 using the 'official' ICS rom released yesterday still causes my phone to reboot.
This happens when bluetooth is paired with my car stereo and streaming audio or voice calls. It causes a reboot, usually happens after 10-15 minutes.
Never happened on gingerbread of any version. And has happened on all versions of ICS leading up to 'official' release.
I can confirm that bluetooth will cut off and be off completely quite randomly while listening to music or Pandora.
Only a reboot gets bluetooth to turn back on.
I have experienced this on two Motorola S9-HD headsets on various ICS roms
Sent from my HTC Sensation Z710e using Tapatalk
My adventures with the HTC One S just dont seem to end. Here is a short history:
First thing I did when I got the phone was flash over CM9 as I dont like Sense
All was good until the home button issue popped up, this was at that time my only issue and sync worked just fine
I flashed over CM10 when it was stable enough, this didnt fix the home button issue though
I then flashed over the new RUU with radio 2.21 and directly after that CM10 again (I still dont like Sense)
After the first flash I had a lot of grey signal bars (either bad signal or no connection with Google servers) so I flashed CM10 again.
The signal bars where blue after that and the new radio (2.21) has improved the signal a lot and therefor minimizing the home button issue
But since the new radio I'm experiencing a new problem, just as much annoying. My phone wont sync when the screen is off or wont sync at all unless I do it manually.
This is what I have tried so far:
First cleaned cache from Gmail, Google Services Framework and Market -> no fix
Rebooted the phone with airplane mode on and enabling data connection afterwards -> no fix
Factory reset from recovery, flash CM10 again and restore apps with TB -> no fix
Factory reset from recovery, flash CM10 again and no restore of apps but just vanilla CM10 -> no fix
I have ran out of options so I could use some help here. Why are emails not pushed to my phone when the screen is off?
I had all kinds of sync issues with that radio until I flashed Trickdroid 7.1 which is built off the base which included that radio. Can't figure out how, but it's like they work best together though my best guess is that TD just maintains more free memory, so whatever process syncs the phone doesn't get killed. You can even desense TD as part of the tweak pack if you want to try it
Sent from my HTC One S using xda app-developers app
el_smurfo said:
I had all kinds of sync issues with that radio until I flashed Trickdroid 7.1 which is built off the base which included that radio. Can't figure out how, but it's like they work best together though my best guess is that TD just maintains more free memory, so whatever process syncs the phone doesn't get killed. You can even desense TD as part of the tweak pack if you want to try it
Click to expand...
Click to collapse
Hmmm ... thanx for this info. I hoped the problem was not related to the radio and I missed something stupid. When I have some time I'll make a nandroid backup of CM10 and will give Trickdroid 7.1 a go, see if it fixes things.
Another solution I was thinking of was buying Tasker and schedule a sync job. When set up right it might even save me some battery juice.
el_smurfo said:
I had all kinds of sync issues with that radio until I flashed Trickdroid 7.1 which is built off the base which included that radio. Can't figure out how, but it's like they work best together though my best guess is that TD just maintains more free memory, so whatever process syncs the phone doesn't get killed. You can even desense TD as part of the tweak pack if you want to try it
Click to expand...
Click to collapse
I tried Trickdroid 7.1 today but spent no longer then 5 minutes on this ROM. Although I selected all options of going back to stock and removing anything related to Sense in the Trickdroid Tweaks it was no where near the AOSP feeling I like best. So I didnt like Trickdroid at all.
Didnt properly test the syncing but in the one test I did I received my email instantly. So I guess there is indeed a problem with the new radio and CM10. I'll report this in the CM10 support thread.
I'm working on adding support for a WiFi only build of CM-11 for the SM-T325.
I am making no attempt at this time to add cellular support because I don't own the device and it would be very painful to try to do that without the device. However, a WiFi only version seems possible and I want to use this thread to validate that.
As a first step, I'm looking for people to test that this recovery works for them on a SM-T325: cwmr-20140528-mondrianlte.
You'll need to unzip the file and then flash it in Odin. If you don't know how to do that, then a test build is probably not for you!
Yes..it works!!!
crpalmer said:
I'm working on adding support for a WiFi only build of CM-11 for the SM-T325.
I am making no attempt at this time to add cellular support because I don't own the device and it would be very painful to try to do that without the device. However, a WiFi only version seems possible and I want to use this thread to validate that.
As a first step, I'm looking for people to test that this recovery works for them on a SM-T325: cwmr-20140528-mondrianlte.
You'll need to unzip the file and then flash it in Odin. If you don't know how to do that, then a test build is probably not for you!
Click to expand...
Click to collapse
i can confirm that this recovery does indeed function as expected...i installed my rom (ran into a weird "android is upgrading" bootloop but it eventually loaded...that may be my experimental multiwindow mod i'm using or the fact that i have completely deleted the touchwiz launcher) as well as created a backup (didnt restore) & all seems to be in order. I may be overreaching a bit about my abilities but im sure if u get a working wifi version going for us then the least i can do is get the cellular working...on a sort of related note would u happen to know if its possible to output through hdmi while in recovery mode? As far as this build is conncerned...anything else u may need tested just give me a shout
edit: looked for the backup which is usually on the internal sd (read:accessible from pc) and although the folder is there its empty...finally found it in "data-media-clockworkmod" & just wanted to know is this normal?
THEDEVIOUS1 said:
i can confirm that this recovery does indeed function as expected...i installed my rom (ran into a weird "android is upgrading" bootloop but it eventually loaded...that may be my experimental multiwindow mod i'm using or the fact that i have completely deleted the touchwiz launcher) as well as created a backup (didnt restore) & all seems to be in order. I may be overreaching a bit about my abilities but im sure if u get a working wifi version going for us then the least i can do is get the cellular working...on a sort of related note would u happen to know if its possible to output through hdmi while in recovery mode? As far as this build is conncerned...anything else u may need tested just give me a shout
edit: looked for the backup which is usually on the internal sd (read:accessible from pc) and although the folder is there its empty...finally found it in "data-media-clockworkmod" & just wanted to know is this normal?
Click to expand...
Click to collapse
That is normal (it is independent of users and /sdcard is specific to user 0 of the tablet).
If you want to work on the radio, you'll need to be able to build sm-t320. If you get that to build, I'll push up my current repos for the sm-t325.
Would you mind booting into recovery and grabbing a dmesg (/proc/kmsg) for me?
Hopefully I can post a cm 11 build in a couple of hours and we can see how that works.
crpalmer said:
That is normal (it is independent of users and /sdcard is specific to user 0 of the tablet).
If you want to work on the radio, you'll need to be able to build sm-t320. If you get that to build, I'll push up my current repos for the sm-t325.
Would you mind booting into recovery and grabbing a dmesg (/proc/kmsg) for me?
Hopefully I can post a cm 11 build in a couple of hours and we can see how that works.
Click to expand...
Click to collapse
either i dont know what i'm doing or adb isnt working properly in cwm...when i connect i get a weird "usb recognized but there's a problem" sound instead of the usual "affirmative" noise if that makes sense (windows)
Here's a build to try: cm-11-20140528-UNOFFICIAL for the sm-t325.
crpalmer said:
Here's a build to try: cm-11-20140528-UNOFFICIAL for the sm-t325.
Click to expand...
Click to collapse
I will give it a try. No mobile Internet with this rom, right? Which gapps I should use? Or is gapps for every rom the same?
works perfectly...thx
crpalmer said:
Here's a build to try: cm-11-20140528-UNOFFICIAL for the sm-t325.
Click to expand...
Click to collapse
everything seems to be ok on my end although i cant test as thoroughly as i'd like to because my screen is screwed (broken lcd)...gps took a long time to track & still never redrew the map after it did but that was without high accuracy mode enabled & no data of course. Mic, camera, mhl/hdmi, sound, video playback, wifi, bluetooth (wait let me check...yep!), auto brightness, lid sensor are all working properly...so now i need your permission. Besides getting data working...i just want to know am i free to use this in a dual boot configuration with my rom & post it in my thread? Also...this is not important but do u know if screen mirroring works with the wifi version?
THEDEVIOUS1 said:
everything seems to be ok on my end although i cant test as thoroughly as i'd like to because my screen is screwed (broken lcd)...gps took a long time to track & still never redrew the map after it did but that was without high accuracy mode enabled & no data of course. Mic, camera, mhl/hdmi, sound, video playback, wifi, bluetooth (wait let me check...yep!), auto brightness, lid sensor are all working properly...so now i need your permission. Besides getting data working...i just want to know am i free to use this in a dual boot configuration with my rom & post it in my thread? Also...this is not important but do u know if screen mirroring works with the wifi version?
Click to expand...
Click to collapse
I don't know whether or not screen mirroring works. No one has complained but I don't have any way to test it.
You can (obviously) post a link to the thread. I would prefer that you didn't link to a specific version as I hope to post more test builds here (although so far only 3 people have downloaded it which shows either a lack of interest or a lack of early adopters).
crpalmer said:
I don't know whether or not screen mirroring works. No one has complained but I don't have any way to test it.
You can (obviously) post a link to the thread. I would prefer that you didn't link to a specific version as I hope to post more test builds here (although so far only 3 people have downloaded it which shows either a lack of interest or a lack of early adopters).
Click to expand...
Click to collapse
Hello, I will root my device and download the test build as well ! Will post back soon.
Thanks for trying to bring support for this device !
Bautinho88 said:
I will give it a try. No mobile Internet with this rom, right? Which gapps I should use? Or is gapps for every rom the same?
Click to expand...
Click to collapse
Sorry, I missed this post... Use the gapps from the sm-t320 thread.
crpalmer said:
Sorry, I missed this post... Use the gapps from the sm-t320 thread.
Click to expand...
Click to collapse
woohoo...well i got data working but calls are a no go as of right now. i can assure u the lack of activity in this thread is definitely not due to lack of intereset....more than likely its because its barely been a full day not to mention that there are not that many of us lte users but best believe once word gets round they'll come running. As far as my permission request...what i was thinking is that i'll just wait until the monthly releases start coming, make the proper changes for data (unless u actually make ours official also which would be awesome) & include it in a dualboot (hopefully multirom) setup. From what i've read ...alterations will need to be made to both kernels/roms which is why i was asking could i use it. I would definitely put a "use at your risk" disclaimer up as to not have the official thread flooded with issues not actually related to cm itself...let me know if u need anthing else on my end
edit: i do have one weird issue though...i copied the dialer app from another device with cm11 but it doesnt show up in the app drawer but is in fact found within the app manager in settings (i know i can just download another dialer but thought i would ask)
edit 2: calls not working yet & but i did get the phone app to appear & sms are also good to go (no mms at the moment)...got rid of the error message on outgoing calls (incoming wont even ring at all) but now it just force closes before it dials out (even with a different dialer)
THEDEVIOUS1 said:
woohoo...well i got data working but calls are a no go as of right now. i can assure u the lack of activity in this thread is definitely not due to lack of intereset....more than likely its because its barely been a full day not to mention that there are not that many of us lte users but best believe once word gets round they'll come running. As far as my permission request...what i was thinking is that i'll just wait until the monthly releases start coming, make the proper changes for data (unless u actually make ours official also which would be awesome) & include it in a dualboot (hopefully multirom) setup. From what i've read ...alterations will need to be made to both kernels/roms which is why i was asking could i use it. I would definitely put a "use at your risk" disclaimer up as to not have the official thread flooded with issues not actually related to cm itself...let me know if u need anthing else on my end
edit: i do have one weird issue though...i copied the dialer app from another device with cm11 but it doesnt show up in the app drawer but is in fact found within the app manager in settings (i know i can just download another dialer but thought i would ask)
edit 2: calls not working yet & but i did get the phone app to appear & sms are also good to go (no mms at the moment)...got rid of the error message on outgoing calls (incoming wont even ring at all) but now it just force closes before it dials out (even with a different dialer)
Click to expand...
Click to collapse
Here's a new build that has all of the telephony bits enabled. I haven't tried booting it (I'm at work, the tablet is at home) but it should have the dialer and all the other framework that is needed for telephony. Let me know if you get calls working with it:
cm-11-20140529-beta
crpalmer said:
Here's a new build that has all of the telephony bits enabled. I haven't tried booting it (I'm at work, the tablet is at home) but it should have the dialer and all the other framework that is needed for telephony. Let me know if you get calls working with it:
cm-11-20140529-beta
Click to expand...
Click to collapse
Can I use TWRP or must be done under recovery (cwmr-20140528-mondrianlte) from the first post?
megatooth said:
Can I use TWRP or must be done under recovery (cwmr-20140528-mondrianlte) from the first post?
Click to expand...
Click to collapse
twrp is fine. The recovery was just because the first step is to make sure that boots before bothering to get the whole system to boot..
I will install your latest build and return with impressions.
Edit: @crpalmer: Phone.apk/dialer is missing and I have no service.
megatooth said:
I will install your latest build and return with impressions.
Edit: @crpalmer: Phone.apk/dialer is missing and I have no service.
Click to expand...
Click to collapse
Yeah, I made no attempt to get the radio working, hence the title...
@THEDEVIOUS1, did you make any progress on modifying the build I posted to get voice working? If so, let me know what changes you've made and I'll see if I can incorporate them.
crpalmer said:
Yeah, I made no attempt to get the radio working, hence the title...
@THEDEVIOUS1, did you make any progress on modifying the build I posted to get voice working? If so, let me know what changes you've made and I'll see if I can incorporate them.
Click to expand...
Click to collapse
Long story short...still no voice. Now for the rest of it...i've gotten it to the point where i can dial out but neither the mic nor speaker works when the call is answered by the other party (i think this is due to the fact that it reports that the call ends as soon as it begins on my device). As far as receiving calls is concerned...NOTHING. I have even gone as far as flashing a note 3 modem (yeah i know...stupid :silly in an attempt to fix it & still no go...i just recently found the build prop edit to allow outgoing calls so hopefully the rest is as simple as editing the build prop. Speaking of which...getting data/phone working is NOT quite so simple but i've gotten it down to the bare minimum number of changes that need to be made. So far we need to add the "lib-qcril-hook-oem.so" from the n9005 cm11 rom & the "libsec-ril.so" as well "libril.so" from the stock T325 rom (which is enough by itself to get data working) as well as decompile the framework-res.apk & and change both the sms & voice config bools enable to true (which i'm sure there is a flag for in source)...this makes the phone app appear as well as allows u to send texts then we need to add the line "ro.telephony.ril.v3=newDialCode" to the prop which allows us to dial out. Well...thats where i'm at as of right now so its back to google for me to put together the rest of the pieces unless u have some insight from working on devices with radios that can be of some assistance
THEDEVIOUS1 said:
Long story short...still no voice. Now for the rest of it...i've gotten it to the point where i can dial out but neither the mic nor speaker works when the call is answered by the other party (i think this is due to the fact that it reports that the call ends as soon as it begins on my device). As far as receiving calls is concerned...NOTHING. I have even gone as far as flashing a note 3 modem (yeah i know...stupid :silly in an attempt to fix it & still no go...i just recently found the build prop edit to allow outgoing calls so hopefully the rest is as simple as editing the build prop. Speaking of which...getting data/phone working is NOT quite so simple but i've gotten it down to the bare minimum number of changes that need to be made. So far we need to add the "lib-qcril-hook-oem.so" from the n9005 cm11 rom & the "libsec-ril.so" as well "libril.so" from the stock T325 rom (which is enough by itself to get data working) as well as decompile the framework-res.apk & and change both the sms & voice config bools enable to true (which i'm sure there is a flag for in source)...this makes the phone app appear as well as allows u to send texts then we need to add the line "ro.telephony.ril.v3=newDialCode" to the prop which allows us to dial out. Well...thats where i'm at as of right now so its back to google for me to put together the rest of the pieces unless u have some insight from working on devices with radios that can be of some assistance
Click to expand...
Click to collapse
Can you send me a logcat of making a call?
crpalmer said:
Can you send me a logcat of making a call?
Click to expand...
Click to collapse
Keep an eye on this post...i just jumped off the deep in end & tried to install the hlte version as is (with kernel swap of course ) so it may take me a minute to get back (i have a nandroid but like to make the cjanges manually so i know the exact process & origin of files). Well i'll be damned...incoming calls work (complete with mic & speaker) with note 3 version of cm11! Outoing still seem to be an issue but this clears up a few gray areas i had concerning whether the ril files matched the modem & so on...i had the bright idea of swapping a few of the framework files then just thought they were so similar that the whole thing should boot. Anyway....shouldnt be long to figure out what the hold up is now bu tgive me a few & i'll post the log after i test a ouple of things then flash back to the other setup
edit: Aaaaaaannnnddd....done! added the line i spoke about in my previous post to the build.prop & now both incoming & outgoing calls are working with the N9005 version...just out of curiosity i'm about to go through & see whats broken the first of which i notice is rotation (i personally hate portrait) but seems like everything else is as well including wifi, camera, lid, bluetooth, & ironically speaker audio (video playback & apollo play no audio through loudspeaker...both work through wired headset). I will still get that logcat a lil later...at this point i dont think it has anything else to do with the build prop because i had already added most of the stuff i found missing in ours from the hlte & it didnt work. I'm thinking maybe another lib file that needs to be swapped...perhaps maybe something in framework
THEDEVIOUS1 said:
Keep an eye on this post...i just jumped off the deep in end & tried to install the hlte version as is (with kernel swap of course ) so it may take me a minute to get back (i have a nandroid but like to make the cjanges manually so i know the exact process & origin of files). Well i'll be damned...incoming calls work (complete with mic & speaker) with note 3 version of cm11! Outoing still seem to be an issue but this clears up a few gray areas i had concerning whether the ril files matched the modem & so on...i had the bright idea of swapping a few of the framework files then just thought they were so similar that the whole thing should boot. Anyway....shouldnt be long to figure out what the hold up is now bu tgive me a few & i'll post the log after i test a ouple of things then flash back to the other setup
edit: Aaaaaaannnnddd....done! added the line i spoke about in my previous post to the build.prop & now both incoming & outgoing calls are working with the N9005 version...just out of curiosity i'm about to go through & see whats broken the first of which i notice is rotation (i personally hate portrait) but seems like everything else is as well including wifi, camera, lid, bluetooth, & ironically speaker audio (video playback & apollo play no audio through loudspeaker...both work through wired headset). I will still get that logcat a lil later...at this point i dont think it has anything else to do with the build prop because i had already added most of the stuff i found missing in ours from the hlte & it didnt work. I'm thinking maybe another lib file that needs to be swapped...perhaps maybe something in framework
Click to expand...
Click to collapse
The outgoing call issue is likely just that the audio configuration is missing the use cases for voice calls. That's why I wanted the logcat because that should be easy to add.
When you're done with the hlte version (which is actually not a great idea for a daily driver as there are other things that are different that you may not notice (two biggest I can think of is that the hardware is different and several of the HAL libraries need to enable/disable different files in /sys/ and the networking configuration is different which may break some kernel/user-space interactions).
But if you can send me the logcat, the build.prop that you are happiest with and detailed information about anything else that you chnaged (e.g. exactly what you changed in frameworks so I'm not guessing) then I'll take a look at another test build.