Hey Mongoose,
First of all, great job with the ROM. Installed both Alpha 2 and 3 and you are making fantastic progress!
Thanks also to all of the Eris DEVs (and all DEVs for that matter) out there, my first little Android has held its own for a few years now
A quick comment:
The keyboard consistently opens ALMOST all the way up. For me, it's been stopping in the middle of the last row - still able to use - but not fully visible.
I was in the Messaging app and I did something that made it jump up to fully visible, but now (of course) I can't replicate what I did.
Thanks again, looking forward to future iterations!!
Wanted to comment on what I've tested and is WORKING for me:
touchscreen (not having any of the reported issues)
physical & soft buttons
data
calls (sending and receiving, no mic)
earpiece audio
sms (sending and receiving)
vibration / haptic feedback
proximity sensor
google sync
root access
NOT WORKING:
microphone
speaker audio
wifi (scans fine, can enter text to connect, says it's connecting, then authenticates, then loops on connecting/authenticating)
gps
camera
bluetooth
trackball
light sensor
orientation sensor
accelerometer (downloaded an app that has opengl 3D using the accelerometer and it rebooted the phone when I tried to view the 3D model)
magnetic field sensor
sdcard
mms (when I choose attach a picture it says "No external storage available.")
Also, installation was a piece of cake!
Wiped data and dalvik and then let it boot. Obviously no boot animation, but first the screen illuminated, then the soft buttons lit, then the haptic feedback shook, and then I was at the Start screen.
Again, fantastic job!!
Hello all,
Just to clarify (since some people in the Dev forums are still having issues that I have not had with Alpha 3) my Eris model number is PB00100.
I believe this is the 2nd model number of Eris from Verizon (not 100% sure about this)? I did have my original Eris replaced after I was losing calls like crazy.
Hope this helps!
Thanks for the detailed feedback! With another post you'll be allowed to post in the section. Look forward to seeing you over there
No problem! Last night I was following the dev thread in the Hero forum talking about the audio issues. Looks like jaybob413, Shelnutt2, shed, you, and a couple others are very close to working that issue out.
Once this build has a working mic, I will be using it more extensively.
Related
Hi, this thread is here for posts that has no room in technical discussion related to this rom. From tech discussion, irrelevent posts will be deleted without excuse, without reason. So here's the correct place for them...
Well done
I just wanted to say well done for the new fast clean rom. I'm finally over 2.5!
Everything I need to work works and well and fast. Thankyou !
Now how do we get the touch interface on the Charmer as they seem to be getting working on the Prophet??? Maybe wrong place to ask, will wait. In the meantime, thankyou again.
the bt works fine with car set
"Now how do we get the touch interface on the Charmer as they seem to be getting working on the Prophet??? Maybe wrong place to ask, will wait. In the meantime, thankyou again."
it's available for wizards - search their forums: http://forum.xda-developers.com/showthread.php?t=313656
"the bt works fine with car set "
nice to hear...go on with testing
WIFI confirmed
WIFI SDIO function has been confirmed by beta tester, loskarlitos - with some limitations like control panel not working , WIFI connection has been confirmed as stable and able to survive standby mode
Thanks Loskarlitos!
Excellent, a new rom to try!!
I can't believe I have only just found this. I could have been playing with it this evening. Its a little late to start messing now!!!
Thanks for all the hard work Nocturne.
nocturne.op.15 said:
WIFI SDIO function has been confirmed by beta tester, loskarlitos - with some limitations like control panel not working , WIFI connection has been confirmed as stable and able to survive standby mode
Thanks Loskarlitos!
Click to expand...
Click to collapse
i think the wifi control panel only works with built in hardware. thats why its removed from the official charmer roms.
hope you are right. i wil think about removal of it for the next ver.
nocturne.op.15 said:
hope you are right. i wil think about removal of it for the next ver.
Click to expand...
Click to collapse
I dont know if that's such a good idea. Some people use SDIO wifi cards and find those wifi settings useful.
Cheers,
vlodeck
as reported from my beta man, loskarlitos, and as reported above, this wifi settings applet seems to be working only with built-in wifi modules, settings are inactive for sdio cards.
Wifi SDIO owners, please share your experineces - than i can build fully functional rom stripped down from useless parts
Hi,
first of all amazing rom. Really really fast. It syncs great under Vista. To flash from Vista you have to use the "Another Flash Method". I encountered no problems with the 12 apps running, alarm or landscape problem.
Only the Calender and Contact buttons are still hardcoded to Start and Back.
problem with alarm was solved - it was really caused by underclocking charmer down to 95mhz (I'm using BatteryStatus for dynamic overclocking. 95MHz is simply not enough power to bring alarm window up and system behaves strange)
problem with changing landscape/portrait disappeared and never came back - but will keep it in buglist until this is really confirmed
lagge number of running apps stil remains - if lot of apps running, softkeys are not working as they should...hope somebody could try this on another wm6 device?
Calendar and Contacts issue
Been testing this rom for a day or two - I get the problem where Calendar and contacts won't start (whether from soft keys or the Start menu) and I have to soft-reset to egt it working. I admit I have been using iContact as well so I will uninstall that for a few days and see if the problem goes away.
closing some apps does not help? it helps for me...
customization?
Hi, when i flash yours new rom and make HR system was start and customization from old wm5 was started. In rom 4.4 customization was not started after HR, is this was changed in this release?
sorry for my english....
This was reported and will be modyfied in next ver. Till then, just skip the customization after HR
Ring tone changes....
Hi, next thing is that my ring tone changes to default without my command. I've seen this before in previous roms but in 4.4 it was ok.
I installed this last night. Seems nice and fast.
I noticed that the phone pad SIP and MMS are missing. (Installed these manually)
Also, i'm afraid the Bluetooth A2DP appears to still be the older, poorer quality version.
Cheers
phonepad sip is missing because i don't like it - it is not necessary. everybody can install it easily manually. but it will not eat precious memmory for us who does not use it ,-)
MMS support is there - no problem with it, thing you report is a bit strange...
it's hard with A2DP. Some testers were reporting it's the best A2dp they have seen - you tell the opposite. The worst thing is that i cannot test it - i do not have a2dp device :-( is possible that transfer quality is also dependent on used HW?
regarding those ringtone changes - i was testing this today (about 10 calls, some restarts etc - no problem. aren't you using any 3rd party software for phone profiles or things like that? I saw this with pocket zen phone..if not, try please to search for some dependency of this behavior so i can repair it
Thanks Nocturne.
I'm really starting to think I've flashed the wrong ROM. I've got so many on my PC now.
Can you confirm what I should be seeing under Device Information?
Thanks
So, a few days ago I flashed to the 2.2.1 (and radio 3.27) release (thanks so much for all your work dcd!). I didn't really notice until today that the vibrate function isn't working. I hopped on here and searched around and came up with nada... other than 2.2.3 was released. Flashed up to that, same thing. Everything seems to work fine other than vibrate.
Anyone have any ideas?
Are you sure the vibration motor is functioning? For instance when you power it on does it vibrate for a split second?
it doesn't, that's actually how I noticed that it wasn't working.
Did you do any registry hacks or use any apps to disable the flashing LED? The vibrate function is tied to the LED flashing and disabling it in certain ways will kill the vibrate functionality with it.
negative... I have a clean install of 2.2.3 with no hacks or modifications applied to it. in my searching yesterday, I came across references to HKLM\SOFTWARE\OEM\VIB and \HKLM\Drivers\BuiltIn\AllLEDMgr but neither of these had any impact.
I had this same issue and the only workaround that I came across was to hit ok when closing the email program instead of closing it by tapping on the X. One other workaround is if you use programs like SPB Pocket Plus, add the tmail.exe to your close exceptions and vibrate will work as normal.
Hope this helps
No problems here with Vibrate
Only programs I have loaded other than the 2.2.3 rom are SPB Phone Suite and PointUI 1.02B.
I am really hoping this is something that can be fixed, I really don't want to have to flash back to stock and get a new one under warranty.
If you soft-reset your phone, does it do that quick vibrate? If so, hardware is intact
bimmerd00d said:
If you soft-reset your phone, does it do that quick vibrate? If so, hardware is intact
Click to expand...
Click to collapse
(see above) nope, no quick buzz
N715DP said:
(see above) nope, no quick buzz
Click to expand...
Click to collapse
aye, my fault. It's still early and I haven't started reading yet. That sucks about your vib, Has to be a hardware fault. i thought i had my first contribution to XDA with this one, thanks for shooting it down.
sorry about that, I am sure you'll get one soon
Hi all
I have got a new sony x10 mini pro, and have an odd issue that seems a design floor.
When on a call my ear constantly presses the mute button and mutes people.
any one know of a way to remove the mute button on the interface or another app that can be used for in call functions.
any advice would be much apreiciated.
thank you
Mat
Place rthe phone closer to the ear so that the proximity sensor disables rthe screen
Sent from my U20i using XDA App
i have d same issue n keep muting calls
I have posted the same issue here
I use hands free but it is still easy to press with the side of your hand if you are holding the phone...
I notice on my phone the touch still works outside the screen border. and it sometimes goes on speaker or mute
+1
Really need a fix for this. Mostly the mute button is the problem, but i have had the loudspeaker activated a few times too.
+1
This is really annoying.
+1
I really nead a solution for this.
I was also annoyed with this, so I made an app that launches it self after accepting the call to avoid the issue. The app can be found at my site on paxanima DOT net (can't post URLs yet, apparently)
I just made it, so not too much real life testing, but seems to do the trick.
paxanima said:
I was also annoyed with this, so I made an app that launches it self after accepting the call to avoid the issue. The app can be found at my site on paxanima DOT net (can't post URLs yet, apparently)
I just made it, so not too much real life testing, but seems to do the trick.
Click to expand...
Click to collapse
Good work on that, thats a start.
But can someone just remove the goddamn mute button? UHHH!
It's too complicated for me. I think i installed like 4-5 apps but still couldnt get to the point where you can get the apk from the phone.
True, this is very annoying. SE has received plenty of complaints so I hope they're working on a solution. I am wondering if installing any of the new custom roms would sort out the issue for me since waiting for SE updates is a nightmare.
My problems started when I first updated to 2.1 where it happened in more than half of calls and got better with the last update and now happens only occasionally.
i never had that problem but i think that costum rom will help for these prob.
sory for bad english
Yeah, you have to be careful. Hold your phone from the back to avoid touching the front sides and slowly approach it to your head (the proximity sensor is at the top left of the phone). I'm pretty sure I look like a retard while doing so but hey, better than having the person on the other end saying "hello? is there anybody here? hello?".
Same here
This issue has also been annoying me from the beginning, and on every release of the SE standard ROMS. I don't understand why some people have the issue and others don't. Maybe it has something to do with the shape of one's ears??
No seriously, when i do some tests, like calling to my voicemail and then holding the phone in my hand, on some occasions the phone goes black after covering the proximity sensor with my finger, and sometimes the phone does not react at all when covering the sensor. So maybe some processes that are running prevent the proximity sensor from working correctly.
Would it be possible to adjust the semcphone.apk to have no mute button at all? I never use this option anyway.
Or is it only possible to change the shape and color of the icons/images.
As far as I know. When ever you made a call or answering call, the screen will turn off, right after you place the phone on your ear... So there's should be no pproblem answering or making call and suddenly pressed the mute button with own ear. Im using the same phone, and making almost 20 to 30 calls a day. And never even once encounter the problem as stated.
Sent from my U20i using XDA Premium App
I get this problem once in awhile too. I have to bring the phone to my ear slowly.
can't we just replace the dailer APK with something from HTC or something?
I also hate the current contact list, theres no smart search.
Yes you can. But it has to be ported with some mod for it to work.
Sent from my U20i using XDA Premium App
I just bought a new car recently and when I try to pair my Fascinate with the car bluetooth, my phone slows down considerably, won't successfully complete calls, and eventually locks up, forcing me to do a hard reset. My car's bluetooth program locks up as well. One time I got an error message on my phone saying services.exe had to force close. At first I thought the problem was with the car, but my dad's Droid Incredible works beautifully on it.
My phone is rooted w/o lagfix, and has launcher pro. It's also been de-binged and has other basic bloatware removed. I don't use taskillers either. Any help or advice would be greatly appreciated, thanks!
I have been having this issue for a while now. I'm currently on stock ED01 and it is almost consistently happening when I end a call. After the call is over and I hang up, the phone does a silent FC with bluetooth being the cause (silent FC = 1 vibrate followed by 2 short vibrates).
When using the stock kernel, the FC is hit or miss. I can maybe get a FC after a 2nd call. When using ANY of the custom kernels built by the devs here, bluetooth will consistently crash after a call is over.
Just like the OP said, the phone will crash and will become very unresponsive. If the phone is responsive and I manage to turn bluetooth off then on again, it MIGHT connect back to the car.
It seems like no one else is experiencing this? Or maybe not a lot of people use bluetooth calling with their Fascinate? I went back to stock just to see if it was a kernel or ROM issue and while it works a bit better, it's still not 100% working. I'm hoping there is someone out there who has working bluetooth calling with their car. I had the T-Mobile G2x for a week and that phone worked perfectly (as far as bluetooth was concerned).
Anybody?
Bluetooth Crash After 1st Call is Ended
DeezNotes said:
I have been having this issue for a while now. I'm currently on stock ED01 and it is almost consistently happening when I end a call. After the call is over and I hang up, the phone does a silent FC with bluetooth being the cause (silent FC = 1 vibrate followed by 2 short vibrates).
When using the stock kernel, the FC is hit or miss. I can maybe get a FC after a 2nd call. When using ANY of the custom kernels built by the devs here, bluetooth will consistently crash after a call is over.
Just like the OP said, the phone will crash and will become very unresponsive. If the phone is responsive and I manage to turn bluetooth off then on again, it MIGHT connect back to the car.
It seems like no one else is experiencing this? Or maybe not a lot of people use bluetooth calling with their Fascinate? I went back to stock just to see if it was a kernel or ROM issue and while it works a bit better, it's still not 100% working. I'm hoping there is someone out there who has working bluetooth calling with their car. I had the T-Mobile G2x for a week and that phone worked perfectly (as far as bluetooth was concerned).
Anybody?
Click to expand...
Click to collapse
I'm also having this same problem with my Bluetooth crashing after my first call ends when using following:
ROM ComRom 1.3
Kernel TW with Voodoo Sound+BLN+UV+Misc tweaks 4/15 by jt1134
Radio ED04
2011 VW Jetta SEL (just purchased a few weeks ago)
I'm thinking to go back to stock as well but would prefer some kind of fix or even a workaround over doing that.
Yesterday I was able to make 3 calls with no crashes at all for the first time ever.
MIUIwiz 1.1
OTB kernel 1.6 - no mods in voltage control
ED04 modem
(No Longer Resolved) The ROM was the Problem with Bluetooth
DeezNotes said:
Yesterday I was able to make 3 calls with no crashes at all for the first time ever.
MIUIwiz 1.1
OTB kernel 1.6 - no mods in voltage control
ED04 modem
Click to expand...
Click to collapse
Excellent!!! Thank you for this! I already had the ED04 modem so that wasn't the problem. Last night I updated my kernel and this morning I tried again with no success so the kernel wasn't the problem. Later this morning, I loaded up the MIUIwiz 1.1 ROM and on the way home from work, I tested 4 calls and viola SUCCESS!!! ComRom 1.3 was the culprit and even though MIUIwiz is based on ComRom, somewhere along the line Bluetooth in the ROM was fixed.
Thanks again DeezNotes!
Edit: My problem is back as well now. Any ideas? Problem started last night when I attempted to make a second call while connected via bluetooth. I was able to make two calls this morning then upon ending the second call, I received the one long vibrate followed by two short indicating something crashed and then the phone would no longer connect.
On the same setup, the problem is back. Its actually a lot worse than before. I actually noticed crashes from Pandora when hanging up a call and Pandora wasn't even running (for days). Even after uninstalling Pandora, still get plenty of consistent crashes after hanging up a call. Interestingly enough, this is with an Audi, so hearing the issue is with a VW isn't far off from what I'm seeing since those cars are typically very identical.
I'm trying out a different phone on a different carrier [again] later this week. If all goes well, I'm going to chalk it up to Samsung and their lack of QC. I would say it's an Audi/VW issue, but I've successfully used the same features with a Blackberry and an LG G2x. Later this week I'll try the HTC Sensation and see how things go. Based on my experiences so far, this might be the last Samsung smart phone I'll ever get.
Bluetooth drivers issue - causing crashes.
Hello. found this thread whilst searching the internet for a related problem, just thought I'd add my experience on the matter.
The issue you are all experiencing is due to a bug in Broadcoms bluetooth stack. More specifically anything to do with listening for a bluetooth service then opening and closing a RFCOMM SPP connection to anything else (maybe a bluetooth OBD2 adapter) will cause either the BTLD process to consume 100% cpu (and make the device run slowly) or cause a kernel panic and reboot.
This is also related, but a slightly different bug (again Broadcoms drivers at fault):
http://code.google.com/p/android/is...rs&colspec=ID Type Status Owner Summary Stars
piemmmm said:
Hello. found this thread whilst searching the internet for a related problem, just thought I'd add my experience on the matter.
The issue you are all experiencing is due to a bug in Broadcoms bluetooth stack. More specifically anything to do with listening for a bluetooth service then opening and closing a RFCOMM SPP connection to anything else (maybe a bluetooth OBD2 adapter) will cause either the BTLD process to consume 100% cpu (and make the device run slowly) or cause a kernel panic and reboot.
This is also related, but a slightly different bug (again Broadcoms drivers at fault):
http://code.google.com/p/android/is...rs&colspec=ID Type Status Owner Summary Stars
Click to expand...
Click to collapse
that sounds really really technical. any ideas on what we can do to fix it?
Handsfree Bluetooth Problem is Back
My problem is back as well now. Any ideas? Problem started last night when I attempted to make a second call while connected via bluetooth. I was able to make two calls this morning then upon ending the second call, I received the one long vibrate followed by two short indicating something crashed and then the phone would no longer connect.
I have the same issue with ED05 de-bloated, stock kernel.
Has anybody found a solution?
Hi there!
First time I need to make a topic, as I don't find the answer anywhere..
Had my Touchpad since about two weeks.
However the accelerometer has not functioned at all since I got it.
First thing to check is the auto rotation lock -> it's turned off
Second thing I did was download a sensor visualizer app -> Seismograph.. This shows very weird results for the x-axis (see attached file), fyi, the Y and Z-axis functioned as expected..
Then the third thing I tried, Need For Speed Hot Persuit... A game that uses the X-axis accelerometer (right!?)
This works brilliant!
Other things I have done to troubleshoot this:
Restart the device.
Full reset the device.
Run HP doctor.
All have failed in resolving my problem.
As I've bought the touchpad from a french webstore (fnac.com), HP Netherlands (where I'm from) tells me I need to get back to them for a solution, as they don't offer worldwide repair (unlike ASUS for example).
Fnac.com has not answered to my request to exchange the product (2 days after I got it). And actually I just want to solve it myself if possible, bought it for fun anyways (and reading of course xD)
Any ideas how I can make the OS recognize the accelerometer?
Last thing, the auto rotation functions in the following way: Tablet is stuck in landscape, I turn to portrait, screen turns as well, but within the second the tablet is back in landscape. This behavior can be read from the seismograph screenshot.
Thanks!
Hello
I just started a new thread for a different accelerometer problem (it is just dead)
http://forum.xda-developers.com/showthread.php?t=1284760
Was wondering how you ended up fixing your problem.
thanks
Just wanted to ask you the same question...
I still have the same problem. Need to contact Fnac.fr, but my french sucks and my time is scarce. So have been postponing this. My unit actually came DOA.. however Fnac didn't respond to my request, and has now asked me to call them.. sucky service
You have no solution I guess?
Well this is odd..
Out of nothing the auto rotate function is working since today.. I noticed it while reading a PDF in Android. Booting back to WebOS didn't make a difference, the sensor is working again
I've got no clue what did the trick.. I have not updated the kernel or something like that lately.
I wonder if the sensor was kicked back into action by brute force (for instance my cat jumping on the tablet..)
Anyway, problem soved for now =D