Related
Before I ask my question, I just want to let everyone know that I have searched and searched and searched for the answer to this before posting. Please don't be a troll unless you have a link that helps me. There are thousands upon thousands of pages and unfortunately xda's search function leaves a lot to be desired.
Now, here is my setup:
emmc CM7
Kernel OC'd to 1.1 ghz
DSP equalizer enabled
MortPlayer Music
What I get is a fairly regular skip/pop whenever I play any song from my music collection (mp3/m4a, mostly). Sometimes it will go almost a whole song without skipping but very rarely. From my research I do know that this WAS an issue with CM7 pre-stable release, but now there seems to be no discussion about it. It's not listed in known issues as far as I can tell so I thought this issue was no longer, well, an issue.
Here's all the things I've tried to get the music to work.
1. I dropped the kernel down to 800 mhz, thinking it may be an issue of my Nook not handling the OC'd kernel. Same result.
2. Flashed back to CM7 stock kernel. Same result.
3. Changed music players (stock, Meridian, cubed). Same result.
4. Made sure the files were not corrupted by copying the files to my phone (EVO Shift) and playing them. They play perfectly on my phone.
5. Disabled DSP thinking perhaps I had the level set too high and it was peaking. Same result.
6. Moved music from external storage (sdcard) to internal storage (emmc/My Files/Music) thinking that my class 6 card wasn't being read properly. Seemed to fix it for the first song or two, then same result.
7. Flashed phiremod 4/13 version, which again, seemed to help at first, then I got the same result.
8. Added (then removed) Auto Killer Memory Optimizer thinking that perhaps memory was getting low while I was playing music. Removed it thinking that maybe it was constantly trying to kill the Music app. Same result with or without AKMO.
9. Disabled the keep home in memory option in CM Settings thinking it was straining the system. Same result.
10. Dropped performance settings in Launcher Pro thinking the same thing as #9. Same result.
11. Switched launchers. Cm Version ADW, ADW EX, LP, Launcher7, Zeam, the launcher I use makes absolutely no difference.
I'm sure I've tried a few other things that I can't think of, but that is about it. What bugs me about it is that even if I'm not doing anything else on it, i.e., I just let it set and play music, it still skips. Even if I'm not performing other tasks such as surfing the web or playing a game. The other strange thing is that youtube and even flash video in the browser work flawlessly, so I really don't understand what the problem could be. I do know that a while back when the video issues were being ironed out, DSP was broken, but I thought that was fixed by rc4. Flash would presumably take up WAY more resources than the music player, why don't I have any problems with it? Would it be a problem with the audio codecs for mp3/m4a?
I'm really stumped here guys. My hours of searching have proved fruitless, so hopefully someone will have the elusive link I'm looking for. Thanks in advance for any help I receive.
I have the same problem. Anyone found a solution for this?
Sent from my DROID2 using XDA App
Next nightly should mostly fix the problem.
Thank you dalingrin. I'll make sure to check it out. You and the other devs here are doing a great job. I'll be sure to donate the next time I get paid.
Sent from my PG06100 using Tapatalk
If you don't want to wait the DEV Kernel topic has a ALSA update as well as an experimental 4/13A kernel that together fix this problem. As well as give you quandrant scores close to 2500! =D
Sorry to ask this, but I've been poking around the forums here and over @ the CM site itself and I have not been able to find the thread with this kernel. Could some kind soul take pity on me and point me in the right direction?
Many thanks!
Yeah the 4/13a kernel was one of the things I tried but forgot to mention. Its a little better but the issue remains. I'll wait til the next nightly thanks for the input guys.
And you can find the 4/13a download in the test build folder linked in dalingrin's oc kernel thread.
tambourineman86 said:
Yeah the 4/13a kernel was one of the things I tried but forgot to mention. Its a little better but the issue remains. I'll wait til the next nightly thanks for the input guys.
And you can find the 4/13a download in the test build folder linked in dalingrin's oc kernel thread.
Click to expand...
Click to collapse
Then you did not install it with the ALSA update...
Kernel Thread
4/13A Test Kernel
Alsa Update - This fixes your issue, even with stock kernel. But works best with 4/13A for extra performance.
Yes I missed that. Thank you sooo much!
EDIT: That fixed it. Again thanks. I hate when I miss something small like that.
Sent from my NookColor using Tapatalk
Thanks for the fix! Just applied it and 4 songs in....the "snap, crackle, pop" is gone. Happy camper here. Also thanks to the OP for bringing this up in such a thorough way, surprised I had not heard of anyone else having this issue.
Dsp manager
I've noticed for a while now since Nightly 27ish, maybe prior, that my DSP manager doesnt work correctly. To modify the settings through my headset, I actually have to modify the Phone Speaker settings.
Is this a known issue, or am I missing something?
Not sure this is the correct thread, but any input would be helpful.
Hitting this again on CM-7.1.0-stable
First off, this is by far the best and most thorough description of the music playback problem that I keep running into, so kudos and thanks to the OP!
But sadly, I upgraded to CM-7.1.0 stable and this is still happening. I see the mention of installing dalingrin's update-alsa-041411.zip, but I can't find that anywhere.
I'm also surprised that this problem is still present in CM 7.1.0 stable. Does anyone know what the new solution for this problem is?
Hi,
yesterday, I successfully installed "official" CM9 on my GT-P7100 from get.cm. However, there are some issues which I hope can be fixed (or not, as the case may be).
- Camera is not working. Is that normal? In the other thread, I read that it should work with pershoot's image from androidbasement. What's the difference between the androidbasement version and the oficial one from get.cm, anyway? Which is more recent/stable/feature-complete?
- WhatsApp is not installable from Play Store. It says "Your device is not compatible with this version". Does anyone know a reason?
- GSM telephony doesn't work (messaging neither). It didn't with the original image, too, but I hoped to make it available with ICS - actually, that was the main reason for me, to flash the tab. Could flashing the modem driver help? At the moment, Baseband is still P7100BULB4. I read that some people flashed it to P7500XXKL3. What could be the reason for doing so?
I attached xome screenshots to give you some hints about my system config. Unfortunally they are in German but should be pretty self-explaning. I can help translating, if you can't understand it.
Thanks for helping, anyway!
Cheers
Chris~
Pershoot may not have uploaded his experimental code for the camera up to the cm repository yet. The new builds on droid basement are still experimental.
Whatsapp has never worked out of the box. If you search there are some people who found workarounds in the early days but I never tried them myself, gtalk works perfectly.
Gsm calling is a dream unrealised. Seo did at one stage have an experimental code to get call receiving working but never call making and he seems to have lost his code and I never saw any of it working on ICS. Messaging also doesnt work. Try textab, works well.Flashing the different modem won't fix this either.
If I were you, I'd flash the experimental cm9 or even cm10 at droid basement and enjoy.
Sent from my GT-I9100 using XDA Premium HD app
thanks for the comprehensive info! pitty that gsm/messaging doesn't work. At least I know now, that it's not worth bothering.
TexTab is cool, although I'd prefer not to use blutooth. Is there a similar app using email or another Internet-based protocol?
I found out how to install WhatsApp. Download the App from this Site: http://www.whatsapp.com/android/current/WhatsApp.apk
During installation it tries to send you an SMS for authentication. This fails, because the tablet can't receive SMSs, but don't worry, just wait five minutes until the progress bar reaches the end. After that you get the option to enter the pin manually (you can receive a phone call with the pin).
See Pon's thread for continued CM10 support.
http://forum.xda-developers.com/showthread.php?t=1882918
Thanks.
Cyanogenmod 10 for the Droid Incredible - Unofficial
The CM team has officially dropped support for the Droid Incredible with the last supported release being CM7.
Credit
First, all credit goes to the following, I simply benefit from their work
Team Evervolv - Donate
Evervolv is responsible for keeping the device tree and a lot of the hardware drivers up to date, without them, we'd most likely have no roms.
Cyanogenmod - Donate
Cyanogenmod is responsible for all the features of the rom, without them we'd be stock with AOSP.
Stripped
Due to the increasing size of the system files to run JellyBean and Google apps and our limited system partition, some things have to be removed from the rom, otherwise things don't work, you blame me, you're sad, I'm sad, and no one wants that. Some things are also removed as I don't use them and removing them each time I flash a rom is a bother. That's the real reason I made this rom anyway. You should be able to replace almost anything that's been removed by installing it as a user app, adding it to your SD Card, or adding it to the rom before you flash it. If in doubt, ask.
AOSP ring tones, CM ring tones still exist
Apollo
The AOSP Music Player app - Play Music replaced this long ago imo
CM Wallpapers
DSP Manager
Live Wallpapers
OpenVPN
Non-English Dictionaries (Only matters if you're using the AOSP keyboard)
Rom Manager
Video Editor App
What doesn't work
Camcorder - not working on any Inc rom atm
Video Playback - Something in CM10 is causing it to break and trying to find out which piece is difficult
Other things? You tell me. I don't use the phone the same way you do, so something else could be broke.
Source Code
Can be found at my github here. If you want to build it yourself, feel free to tweak it, but please read the instructions, as at the time of this writing, there are many reverts to be made. I have them setup so they apply automatically when I repo sync using a shell script, you can do the same.
Downloads
* Note feel free to post a mirror if you like, buyer beware though.
cm-10-20120912-UNOFFICIAL-inc.zip
Stock camera is no longer fuzzy and upstream commits from CM.
cm-10-20120909-UNOFFICIAL-inc.zip
Updates include working mms and upstream commits from CM.
cm-10-20120901-UNOFFICIAL-inc.zip
Upstream commits include: SMS popup, variable lockscreen pattern size (up to 6x6), advanced phone settings from CM9, and audio over bluetooth should work (thanks to EV). Also, the toggle LED flashlight option in the notification drawer works now.
Third party camera apps don't work in this building unless using Tiny's kernel. incredikernel-jb-beta2.zip - 2.63 MB
cm-10-20120830-UNOFFICIAL-inc-stable.zip
Main changes over 8/28 are upstream commits and updates to the stock kernel
Google Apps
Latest Evervolv Gapps is recommended due to their smaller size.
Goo.im Gapps also work, but are larger and you will need to watch your system space when flashing these.
Flashing
Cyanogenmod is designed to not need wipes between flashes. While this generally holds true, I've found occasionally flashing does solve an error or two. If something doesn't work after a dirty flash, clean flash before you report the problem. The download will say if a flash is required, otherwise follow what was just said.
Issues
If you're having issues follow this list of steps.
Check that you're on the latest build, if not, get on it
If you dirty flashed, clean install
If it's an issue with voice search or Google now, check system space, if it's full, free some and reflash gapps
If it's an issue with an app, try a clean install of said app
If it still doesn't work, search the thread, does someone have the same issue?
If no one has the issue, get a logcat and post in the thread, don't PM me. Logcats should be uploaded to a paste website, not directly posted on the forum.
Run around in circles until I or someone else posts a solution to your problem. If you get tired, take a break, then try to solve it yourself, if you do, post the results!
Thanks again to Team Evervolv and Cyanogenmod for making this rom possible.
Enjoy.
Haven't tried this yet but it's nice to see that it has found the light of day out of the Q&A section. Best of luck with this ROM as I know myself and many others will be following it.
Thank you for making this. It's good to see the Inc keep up.
I've recently come to the decision that having a working camcorder is more important than having the latest and greatest shiny, so I'm back down to CM7 for the time being.
Thanks for your efforts in making this available, it's great to have choice and I was beginning to miss the CM customization. I'm running a slightly older build now, but it's running great for me, and I'll be sure to be updating it to this newest when I get a chance.
Glad to see this thread in the Dev section now! So far this ROM is running great for me. I'll be installing the new 8/30 build soon.
Thanks for everything Zimeron
Thank you for this! Also, for some reason I thought the initial post was especially well written so props for that as well.
8/30 Working Well
I am running the 8/30 version with Evervolv's gapps and incredikernel. No new issues that I can find (just still konwn issues with camera and video). I don't have anything bluetooth so I can't test that. I was running Albinoman's but missed the CM addons.
Did CM9 ever get flashlight working in the notification widget? It is greyed out on CM10.
thanks Zimeron
Okay, I have to ask... How doe this compare to Albinoman's Jellybean Beta 3?
vrienduinen said:
I am running the 8/30 version with Evervolv's gapps and incredikernel. No new issues that I can find (just still konwn issues with camera and video). I don't have anything bluetooth so I can't test that. I was running Albinoman's but missed the CM addons.
Did CM9 ever get flashlight working in the notification widget? It is greyed out on CM10.
thanks Zimeron
Click to expand...
Click to collapse
Flashlight in the notification widget, never seen/used that before. I think I can get this turned on from some commits I saw today for other devices.
Anyone play words or scramble with friends while using this rom? It's a silly thing but I was wonder if you do, do you get updates when it's your turn?
It's really hit or miss on roms. Some ICS roms will notify, others will not.Evervolv's does not. I will flash anyways,just wondering.
Thanks for keeping this phone alive.
Any chance you could add in the offline voice dictation feature? I thought it was a standard feature of JB, but there's no ability to download the offline language pack in the voice search settings.
jpzsports said:
Any chance you could add in the offline voice dictation feature? I thought it was a standard feature of JB, but there's no ability to download the offline language pack in the voice search settings.
Click to expand...
Click to collapse
I'm not familiar with this, does it work on EV or Albino's with the same google apps?
Zimeron said:
I'm not familiar with this, does it work on EV or Albino's with the same google apps?
Click to expand...
Click to collapse
My bad! I should have tested it before posting haha. Your build fixed it actually. It didn't work on Albino's build, and I assumed it wouldn't work on this build either because it doesn't have the Offline Voice download setting. But I just tested it and it worked great! With no internet connection, I was able to dictate a text message
Loving this ROM!
On a side note, I just updated to 8-30 and noticed that I needed to reflash gapps after because my google program were missing. In the past with CM9, I didn't need to install gapps after a new nightly and relogin, etc. Is there any way to have it retain gapps when flashingover?
jpzsports said:
On a side note, I just updated to 8-30 and noticed that I needed to reflash gapps after because my google program were missing. In the past with CM9, I didn't need to install gapps after a new nightly and relogin, etc. Is there any way to have it retain gapps when flashingover?
Click to expand...
Click to collapse
The script is there to maintain gapps, but I've found it to work randomly. I have flash it everytime to be safe, my brother never flashes it and never needs to on his Inc, no idea what's different, and it's not worth it to me to dig into it when it takes two seconds to queue another zip to flash with TWRP.
k sounds good. Not sure why, but 8-30 is running amazing and noticeably smoother than 8-28. I'm also using Tiny's JB kernel and it seems to be working great. Best ROM out there.
100% the best JB I've used thus far. Crazy smooth and responsive.
Just me or are notification volumes really quiet?
chowner said:
Just me or are notification volumes really quiet?
Click to expand...
Click to collapse
Your phone/notification sounds might not be linked, meaning the sound is lower than you think it is.
[e]Hopefully new build today, CM merged in a lot of stuff, so testing takes longer.
New build: cm-10-20120901-UNOFFICIAL-inc.zip
Upstream commits include: SMS popup, variable lockscreen pattern size (up to 6x6), advanced phone settings from CM9, and audio over bluetooth should work (thanks to EV). Also, the toggle LED flashlight option in the notification drawer works now.
Enjoy.
Loving it! Thanks for the hard work on this!
New Builds - December 30 - I don't know if anything changed, I just sync'd repos and compiled it. But it's newer, eh!
MAKE SURE YOU WIPE DATA/CACHE AND SYSTEM AND INSTALL THIS ROM TO A FRESH ROM SLOT. Don't complain about non-working or strangely behaving apps if you flash over an old install without trying this first.
Based on the work of the All-Powerful Hashcode (source), here are fresh builds of AOKP JB and CM10.
Still no working camera. However, includes the sensor fix from Jarveson (Thanks!). HW codecs re-activated (thanks Hashcode!)
Updated repos, minor tweaks to get it to build correctly (Solana github repo doesn't build successfully as-is). See the posts ~ pg 153 of Hashcode's official thread.
Use gapps 20121011 available at your nearest filehost.
Download:
/mediafire/solana
For our friends on the other side of the Great Firewall:
CM10 Dec 15
These are ALPHA test builds (as noted by Hash) and a constant work in progress. I recommend flashing into a secondary ROM slot until you feel comfortable.
Thanks to Hashcode, dhacker, jonpry, jarveson, Google, AOKP, CM and everyone else who made this possible.
Kernel Included? version?
Gapps included?
Thanks for your work on the D3
Oh yeah, FIRST
Always wanted to do that
Thanks for this! I will finally test it today (didn't have time).
Maybe you're interested in including the fix I use for making the D3 wake with keyboard keys also.
For me at least, it was one of the first things I missed on kexec ICS/JB.
http://forum.xda-developers.com/showpost.php?p=33639782&postcount=1333
Will report back later today
If possible, could you please make a CM10 version?
AOPK has
1) No profiles
2) Brightness toggle is on separate row
3) Can't use 4x4 unlock slide
4) ....
I'm running it. So far so good.
Sent from my XT862 using xda app-developers app
DoubleYouPee said:
If possible, could you please make a CM10 version?
AOPK has
1) No profiles
2) Brightness toggle is on separate row
3) Can't use 4x4 unlock slide
4) ....
Click to expand...
Click to collapse
Awesome build, but I'm looking forward for a Cyanogenmod build as well.
CM build
I'll start a CM10 build tonight or tomorrow, depending on how I'm feeling. Been a busy weekend working and lots of late nights getting just AOKP to work cuz it's my primary.
In theory it shouldn't be too difficult, because AOKP is CM based. But I'm no professional, I just do this for the enjoyment.
Will keep you guys posted.
sylentprofet said:
I'll start a CM10 build tonight or tomorrow, depending on how I'm feeling. Been a busy weekend working and lots of late nights getting just AOKP to work cuz it's my primary.
In theory it shouldn't be too difficult, because AOKP is CM based. But I'm no professional, I just do this for the enjoyment.
Will keep you guys posted.
Click to expand...
Click to collapse
If it's CM based I wonder why they've removed so many features
Thanks!
DoubleYouPee said:
If it's CM based I wonder why they've removed so many features
Thanks!
Click to expand...
Click to collapse
... because... because... it's more... aerodynamic?
(CM10 building as we speak)
sweet!,
what about the bluetooth issue? all gone?
I do understand that you are working off of Hash codes work....
Just a heads up. I do believe you are required to list links to source for GLE standards. This includes link to source for ROM as well as Kernel.
Great work thus far and thank you for your efforts:thumbup:
Sent from my Galaxy Nexus using xda premium
Awesome CM 10 build, enjoying the proximity sensor fix, but didn't you say that MMS was fixed on Verizon? It still says "Invalid recipient" for me. Anyone else?
hilokilo said:
Awesome CM 10 build, enjoying the proximity sensor fix, but didn't you say that MMS was fixed on Verizon? It still says "Invalid recipient" for me. Anyone else?
Click to expand...
Click to collapse
I've been talking to another user about this. Turns out that the stock messaging app is still affected by the MMS bug. I've always used a third party app so I didn't notice when I did testing. Sorry everyone.
But it works with a third party messaging app definitely. GoSMS is my present choice. Used to be Handcent but it's gone down the drain IMO the past year.
Yes mms no workie in stock. Go sms seems to work though.
Sent from my XT862 using xda app-developers app
Hmm MMS works on the 883 radio from T-Mobile. Maybe it's something in build.prop? Maybe it's APN settings? I think CDMA carriers still use APNs.
Already went down the road of apn. Everything was correct in mine. Went ahead and deleted and re entered, no change in built in sms/mms app. Wouldn't know what to check in build.prop.
Sent from my XT862 using xda app-developers app
Installing CM10 version now.
Btw it baffles me you guys still use "MMS" :silly: that's like saying you still use CDs :laugh:
edit: flashed right over my old CM10 build..lets see what happens. It works for now
edit2: First thing I noticed, my generic.kl didn't work. Apparently, now I have to edit omap4-keypad.kl. No idea why:
http://dl.dropbox.com/u/22072961/Droid 3/omap4-keypad.kl
DoubleYouPee said:
Installing CM10 version now.
...
edit: flashed right over my old CM10 build..lets see what happens. It works for now
...
Click to expand...
Click to collapse
I did the same and it seems to be working well. I've only had one phone call and the phone app did crash when the call ended. I *think* the called party hung up first. The sensor fix is very nice - I was somehow regularly getting into the settings menu with my ear and changing stuff before it
I think the only thing I miss at this point is the audio out via the car dock special usb cable. I've thought about trying to help figure that one out, but the last programming I did was in the late 80's in C, so the learning curve is gonna be kinda steep. I have installed the sdk on my Fedora machine. We'll see if I can get motivated to figure out how to actually do anything with it.
djbolden said:
I did the same and it seems to be working well. I've only had one phone call and the phone app did crash when the call ended. I *think* the called party hung up first. The sensor fix is very nice - I was somehow regularly getting into the settings menu with my ear and changing stuff before it
I think the only thing I miss at this point is the audio out via the car dock special usb cable. I've thought about trying to help figure that one out, but the last programming I did was in the late 80's in C, so the learning curve is gonna be kinda steep. I have installed the sdk on my Fedora machine. We'll see if I can get motivated to figure out how to actually do anything with it.
Click to expand...
Click to collapse
If you understand C well, you might actually not have too hard a time, especially if Android is C++. I have no idea though.
set up
if anyone would like to get their machine going for development, i made a blog post (my first serious one ever) about setting up Ubuntu 12.10 properly to compile Android from source.
https://soupdawg.wordpress.com/2012...-for-building-android-jellybean-all-variants/
all the other guides i've seen are up to 12.04, and setting up the correct JDK is unique on 12.10
good luck everyone!
NOTE: my process.phone always crashes after calls. it doesnt seem to impact anything, i still run it day to day just fine. i'll try to track it down and see whats up. i think it's because of the hack i had to do to get the ROM to compile correctly. frameworks/base in its natural state from the repo causes build errors.
DOWNLOADs:
1.7 BETA - Any future releases:
http://d-h.st/users/tiny4579
1.0 - 1.6 are:
http://d-h.st/users/Tribulattifather/
WORKING in ver 1.7 BETA so far:
WiFi - Thanks to Tiny4579
Cell Service- Earpiece, Mic and Speaker phone all work.
SMS - Text send and receive
Dialer - calls out and works during call
Compass - works in Speedview app
Music /Sound
Touch
USB in ADB
USB via UMS
Capacitive Buttons
ScreenShot
Extended Menu
Camera
NOT WORKING:
BlueTooth (Connects but doesn't read)
Data
GPS
Video Recording
WORKING ON ATM:
Data
EGL and GUI
When we are finished with the Beta Releases we will numerate regularly again with 1.0 as the first release candidate.
THANKS:
Big Thanks to Tiny4579 for getting Wifi working and for supporting the project with his kernel.
Big thanks to Greeneyes2910 for making this possible.
Thanks to Devs PonsAsinorem, Flagmax, Ljjehl and Zachf for the time they spent helping me bounce ideas off of.
Also a thanks to invisiblek and cmlusco for the base files.
And of course HTC too.
SCREENSHOTS:
Greeneyes is the one I just hit up for a wifi fix TheRiseM does not know much
Your main error is
Code:
AndroidRuntime(11867): java.lang.RuntimeException: Unable to instantiate application com.android.htcdialer.DialerApp: java.lang.ClassNotFoundException: com.android.htcdialer.DialerApp
Do you have HTC Dialer in the ROM?
(since I haven't really seen you around, I'm going to assume you don't really know my situation. I can help troubleshoot and give you ideas, but it takes me 5-8 hours to download these ROMs, which I'm not going to do because they change so frequently).
And I completely understand that situation; I used to have an issue with my cable for a week while they were fixing it. My net was as slow as adsl.
I was actually here about a year ago actively. But got an Evo3D and did my thing there for a bit. Now, I want the same things for Inc as my Evo had.
PonsAsinorem said:
Your main error is
Code:
AndroidRuntime(11867): java.lang.RuntimeException: Unable to instantiate application com.android.htcdialer.DialerApp: java.lang.ClassNotFoundException: com.android.htcdialer.DialerApp
Do you have HTC Dialer in the ROM?
(since I haven't really seen you around, I'm going to assume you don't really know my situation. I can help troubleshoot and give you ideas, but it takes me 5-8 hours to download these ROMs, which I'm not going to do because they change so frequently).
Click to expand...
Click to collapse
I think the dialer is there .... if you want I can make a mirror as I am working on the project to that may have faster down speeds
So far, I've fixed the Camera and the acore issue and the dialer issue.
It's uploaded now also.
zachf714 said:
I think the dialer is there .... if you want I can make a mirror as I am working on the project to that may have faster down speeds
Click to expand...
Click to collapse
It's not your or his end, it's the fact that I'm on an advertised 256kbps halfway across the world. And I say advertised as in I don't believe it. It's probably a lot lower.
PonsAsinorem said:
It's not your or his end, it's the fact that I'm on an advertised 256kbps halfway across the world. And I say advertised as in I don't believe it. It's probably a lot lower.
Click to expand...
Click to collapse
Oh ok I getcha .... That is seriously like my upload speed so I can see where your problem comes in
What I did so far was I took wpa_suplicant, wifitools and wpa_cli from the cm9 and copied over to bin.
Then I added :
rild.libpath=/system/lib/libhtc_ril.so
ro.ril.def.preferred.network = 4
ro.telephony.default_network = 4
wifi.interface = wlan0
wifi.supplicant_scan_interval=45
mobiledata.interfaces=rmnet0
ro.com.android.dataroaming = trueto the build.prop
Then made sure eth0 was changed to wlan0 in the conf files.
And then lastly, I took the wifi permissions from etc and copied over.
Also, added the base gps.conf
As of right now I believe I have cell service and/or data.
But not sure because I don't have a carrier for this device.
But I believe I did because the timezones don't have to be set manually anymore.
So I need some help testing it if it works or not.
Wifi is still a no go but it is getting better.
I don't see the same error messages I was seeing as before in the logcat.
EDIT: Just fixed Sdcard mount indevice. Can listen to music and view pictures now
Uploading ver 1.4 now.
I was gonna test the cell/dialer but dev-host is down atm.
ver 1.4 is up now.
Ok it looks like dev-host is back.
EDIT: Ok thanks. I will post my findings in this post so not to clutter.
Flagmax said:
Ok it looks like dev-host is back.
EDIT: Ok thanks. I will post my findings in this post so not to clutter.
Click to expand...
Click to collapse
Ah, clutter away, lol. Almost done uploading.
I'm about to head to bed but i will be on a different Rom on my phone and keeping an eye on it.
I can't wait myself to find out or not if cell service, data, gps and bluetooth work.
Well I amazed to see the progress! I want to congratulate everyone who is involved.
Works:
Cell Service- Earpiece, Mic and Speaker phone all work. Sound very loud but a little noisy in my opinion.
SMS - Text send and receive
Dialer - calls out and works during call
Compass - works in Speedview app
Music - plays through speaker
Don't work:
WiFi - error
Data - can't turn on
Bluetooth - can't turn on
GPS - checked but still don't work
Camcorder - crashes
Sent from my ADR6300 using Tapatalk 2
That is pretty good ! Keep up the good work!
God Bless Your Work!
Sent using my jb android phone!
ALRIGHT AFTER SOME TIME AND GOOGLE SEARCHING I FOUND THIS N1 THREAD .... The RAMDISK is the problem http://forum.xda-developers.com/showthread.php?t=1995549&page=15
I also just sent that dev a PM because he knows exactly what to do with the modules and ramdisk
zachf714 said:
ALRIGHT AFTER SOME TIME AND GOOGLE SEARCHING I FOUND THIS N1 THREAD .... The RAMDISK is the problem http://forum.xda-developers.com/showthread.php?t=1995549&page=15
I also just sent that dev a PM because he knows exactly what to do with the modules and ramdisk
Click to expand...
Click to collapse
Just curious, what makes you think that?
I scanned the page, and all I found was...
Aca902 said:
Made ramdisk modification... Fixed wifi
Click to expand...
Click to collapse
Do you have any more information/ideas on why it's the ramdisk? That quote is not much to go on, and contains zero information on how this is relevant to the inc's problem.
Last night the Dialer showed up and worked just fine. I flashed ToB rom in morning for few hours then did a full wipe and put 1.4 back on and now Dialer not showing up.
Flagmax said:
Last night the Dialer showed up and worked just fine. I flashed ToB rom in morning for few hours then did a full wipe and put 1.4 back on and now Dialer not showing up. Attached logcat. Btw, is it safe to post logcats?
Click to expand...
Click to collapse
Just to make certain I would download again from my link and see if that happens again. Also, make sure to do a full wipe including dalvik-cache, system, all data and even the boot.
PonsAsinorem said:
Just curious, what makes you think that?
I scanned the page, and all I found was...
Do you have any more information/ideas on why it's the ramdisk? That quote is not much to go on, and contains zero information on how this is relevant to the inc's problem.
Click to expand...
Click to collapse
Yeah I had read a few pages before that to and everything pointing to WiFi and Bluetooth is related to the modules and the ramdisk
Sent from my Nexus 7 using Tapatalk HD