Related
l have trying to find a android rom that Bluetooth and earpiece dose work for our touchpro2 and no answer so far.could someone tell me whether i can find it in roms from xda or neopeek now, or we have to wait?
sharemoon55 said:
l have trying to find a android rom that Bluetooth and earpiece dose work for our touchpro2 and no answer so far.could someone tell me whether i can find it in roms from xda or neopeek now, or we have to wait?
Click to expand...
Click to collapse
BT doesn't work currently on the RHOD. Hopefully soon, just don't hold your breath.
This isn't meant to replace WinMo at this stage. Read, have fun with it, read some more... Pretty much every single major issue has been reported.
..........
I want to contribute to this thread, I am a longtime user of Android on the TP2, I donated to the project when we got sound working.
Basically, I am keeping my fingers crossed for bluetooth to be the next working feature. I can get by without the camera, and the power management, for me at least is fine because I can plug my phone in all the time.
However, my job requires me to be on a bluetooth headset a lot, especially while driving, so that is my only hangup for not using Android 24/7 .
I will reiterate.
This isn't meant to replace WinMo at this stage (maybe never). Don't expect it to be able to.
arrrghhh said:
I will reiterate.
This isn't meant to replace WinMo at this stage (maybe never). Don't expect it to be able to.
Click to expand...
Click to collapse
I have more issues with WinMo than I do with Android, it has replaced WinMo for me personally. The only time I run WinMo is if I need a hands free device.
sizeth3 said:
i have more issues with winmo than i do with android, it has replaced winmo for me personally. The only time i run winmo is if i need a hands free device.
Click to expand...
Click to collapse
then go buy a vibrant or hd2
arrrghhh said:
BT doesn't work currently on the RHOD. Hopefully soon, just don't hold your breath.
This isn't meant to replace WinMo at this stage. Read, have fun with it, read some more... Pretty much every single major issue has been reported.
Click to expand...
Click to collapse
Hi aarrrghhh
Is there an idea when BT would be available/ready?
jonners59 said:
Hi aarrrghhh
Is there an idea when BT would be available/ready?
Click to expand...
Click to collapse
When it's fixed? Until someone with the knowledge steps up and takes the time to troubleshoot it...
Problem is, devs are just like us - they want to work on things that interest them. So until BT is a priority for a dev, it won't get a lot of attention. Seems a lot of focus right now is on framebuffer/graphics performance and battery life (panel init).
There was a lot of work on the camera as well, not sure where that stands - someone was able to get a functional preview on their phone tho.
Basically if you don't have the knowledge to fix it, don't ask when it's going to be fixed. These things don't just happen... Someone has to work at it to get it up and running.
New XDAndroid user, first time poster,
I've been searching through all these threads like mad, and I've discovered that there is NOT, nor is there likely ever to be, a BT working build for Rhodium. I get that, and view the XDAndroid builds as a godsend anyway. Android kicks WinMo's ass, BT or no.
I've also found that there's a buggy headset workaround (that I haven't gotten working yet) but I plan to keep trying. My question is (and I keep searching the threads but I can't find it answered) - does the headset workaround let you use a wired headset to make phone calls? I mean can I both hear and speak through the headset?
Thanks!
bndtdog said:
New XDAndroid user, first time poster,
I've been searching through all these threads like mad, and I've discovered that there is NOT, nor is there likely ever to be, a BT working build for Rhodium. I get that, and view the XDAndroid builds as a godsend anyway. Android kicks WinMo's ass, BT or no.
I've also found that there's a buggy headset workaround (that I haven't gotten working yet) but I plan to keep trying. My question is (and I keep searching the threads but I can't find it answered) - does the headset workaround let you use a wired headset to make phone calls? I mean can I both hear and speak through the headset?
Thanks!
Click to expand...
Click to collapse
Kinda OT for this thread, but try it out - let us know if it does work. I want to say it does, but I don't have a wired headset to test with.
I also never meant to give the impression that BT will never work. Just that it's not actively being worked on (to my knowledge) and won't really get the attention it deserves until a lot of the other work going on right now settles down. It's one of those things, devs work on what they want to work on... sure it sounds selfish but they're doing this for their own personal interest - not because someone else really wants the feature.
So that's the unfortunate truth. Until a dev takes an interest in fixing BT, it's not going to get fixed. Either you can gripe about it not working (which really isn't useful, and I'm not saying you are or you're the only one complaining....), or jump in and try to help!
Doesn't sound selfish at all. Devs needs to do what they're interested in doing. Devs donate their time and skills for fun and for the good of this community, not for some guy who complains that they didn't magically turn his winmo phone into a fully functional android. You want android, buy an android. Anyone who complains about the lack of BT doesn't get this.
Still can't get the damn headset working, but that's my issue. I'll keep reading and working on it.
bndtdog said:
Doesn't sound selfish at all. Devs needs to do what they're interested in doing. Devs donate their time and skills for fun and for the good of this community, not for some guy who complains that they didn't magically turn his winmo phone into a fully functional android. You want android, buy an android. Anyone who complains about the lack of BT doesn't get this.
Still can't get the damn headset working, but that's my issue. I'll keep reading and working on it.
Click to expand...
Click to collapse
if you want the headset to work, put "snd.force_headset=X" into the startup file and replace the x with a 1 for the usb headset and a 2 for the 3.5mm headset. After that, go to you phone in wm and call your voice mail with the headset in the phone. While still in the call, boot into android. It should work for music but i haven't tested calling. Unfortunately, if you do this, then the speaker wont work.
kdub94 said:
if you want the headset to work, put "snd.force_headset=X" into the startup file and replace the x with a 1 for the usb headset and a 2 for the 3.5mm headset. After that, go to you phone in wm and call your voice mail with the headset in the phone. While still in the call, boot into android. It should work for music but i haven't tested calling. Unfortunately, if you do this, then the speaker wont work.
Click to expand...
Click to collapse
Thanks kdub! I've been trying this with 3.5mm headphones, but can't seem to get it working. What's weird is, every time I go back to the startup.txt the snd.force_headset=2 line is gone, and I know I put it within the quotes.
It may have something to do with the advanced settings I put in when I boot XDAndroid. The startup.txt also seems to be different depending on those features, so maybe it rewrites it or something?
bndtdog said:
Thanks kdub! I've been trying this with 3.5mm headphones, but can't seem to get it working. What's weird is, every time I go back to the startup.txt the snd.force_headset=2 line is gone, and I know I put it within the quotes.
It may have something to do with the advanced settings I put in when I boot XDAndroid. The startup.txt also seems to be different depending on those features, so maybe it rewrites it or something?
Click to expand...
Click to collapse
If you use the startup utility, it will rebuild your startup.txt every single time. I think there's a checkbox somewheres in there to enable a manual startup.txt...
arrrghhh said:
If you use the startup utility, it will rebuild your startup.txt every single time. I think there's a checkbox somewheres in there to enable a manual startup.txt...
Click to expand...
Click to collapse
Ah, I suspected as much. Will report back if I get this thing working...
Success! Thanks everyone. By the way, by using this workaround and a cheap piece of hardware called a Bluetooth Adapter (Cardo BTA II), I was able to get Bluetooth on my Rhodium with XDAndroid running. Awesome!
Edited to clarify - the headset workaround DOES work both ways, so you get audio out and audio in.
bndtdog said:
Success! Thanks everyone. By the way, by using this workaround and a cheap piece of hardware called a Bluetooth Adapter (Cardo BTA II), I was able to get Bluetooth on my Rhodium with XDAndroid running. Awesome!
Click to expand...
Click to collapse
Ha, I guess those that really need BT now have a workaround... even if it does involve an additional piece of hardware, haha. Seem actual BT is just around the corner (no promises )
Sounds good but on my rhod100_de i'm not able to activate bluetooth. When i hit it in the settings it only grays out, says "Activating..." for some time and than goes back to previous view (white text and not checked). So there seems to be a little more work for me . I think in about a half year we have a real good android running on our Devices and can kick winmos ass
@Bieka
Nobody said that BT is working. He used an "Klinke Bluetooth Adapter". ^^
Hey all,
This is a shiny new test kernel from none other than WisTilt2 and jonpry.
***NOTE***
The new acoustic code is in this kernel. If you're not running a system image that supports the new acoustic code, you will lose all sounds! This includes in call audio, speakerphone, everything!!
***********
They have been working hard on getting a new codebase out, and this is a result of their work.
Note - things are going to be broken in this kernel. Most things from .27 will work, the second post will serve as a list of confirmed broken things & workarounds if they exist. Initially I'd like to see what people report, so let me know! If you report a issue that is listed in the next post, put your flamesuit on, you're asking for it.
This kernel is RHOD only. It may boot other devices, but they are untested. Run at your own risk!
This kernel also requires some changes to haret & the startup.txt, which I will outline below.
Steps:
1. Download the alternate haret version (attached). I have found that this alternate version will boot other 'normal' kernels, but you must use this haret to boot this kernel.
2. Add this line to your startup.txt (I added it after the set initrd line):
Code:
set initrd_offset 0x00a00000
3. Download the kernel from the .39 (autobuild service), replace as you normally would, and boot!
Broken Things
The additional modules are now provided, however wifi is still broken...
adb now works, but the usual indicator in the notification bar is missing...
BT obviously won't work, as the new audio routing code is not in this kernel. It has the standard audio routing from the autobuild.
user.conf files don't seem to be getting processed... Help on this would be appreciated, I'm honestly baffled that the kernel would affect this, but it seems to be.
Overclocking hasn't worked for anyone as of yet. WisTilt2 was thinking the statement is ignored currently.
End call seems to be failing. It's related to the new zoombar enhancements unfortunately... **These are going to be temporarily pulled until the issue is resolved**
Booting on the new HaRET may fail completely. See this post!
Wifi does not work. There's a fix! Thanks to detule & jonpry for it!
DEVELOPERS ONLY
Now that's out of the way...
There is a public git repo for .39, assuming you want to see the action live!
no wifi no camera...how is this better than other versions? just curious
prexzone said:
no wifi no camera...how is this better than other versions? just curious
Click to expand...
Click to collapse
Newer code base, so presumably old bugs are fixed, new bugs are present.
prexzone said:
no wifi no camera...how is this better than other versions? just curious
Click to expand...
Click to collapse
The .39 kernel is the future, off which all future updates will presumably be based. However, work has just started on it, which is why it's got a lot broken still.
The .27 kernel which we've been using to date is a hacked together mess that is woefully outdated. Froyo and Gingerbread were never designed to work with this old kernel, and as a result, hacks had to be hacked together, and the whole thing is creaky and hard to improve upon.
I personally was looking at developing a driver for the zoom bar to emulate multitouch pinch-to-zoom for Rhodium/Topaz. However, multitouch wasn't added to the Linux kernel until I think .31, so I gave that up for now.
I was also looking at switching our file systems to the much faster ext4 filesystem, but support was not added for that until .28.
So it may not be better now, but it's pretty much our only hope for progress. There are also crashing and other stability bugs that were fixed in newer kernels, that we simply don't have. I also understand that the .39 kernel is faster.
Thank you all! First impressions with my RHOD100/AUO with FRX06:
Instant sleep and wakeup! It seems that the intermediate sleep state led (blinking green) is not available in this kernel, so amber=awake and green=sleeping. Trying to wake up the phone while freezing applications (screen off, amber -- former blinking green) brings up the backlight but not the panel, touching the screen brings up the panel. This is 100% reproducable.
Data works great with hyc's ril2.
In-call audio did not work correctly, but this was also the same with the .27 kernels, a problem which seems to be specific to my phone. Only JB's audio routing code solved this problem completely, I can only hope that this will be integrated sometime in the future.
However, FB and overall android interface did not get faster (which was discussed in IRC). I can say that it is just about the same as in .27. Don't know exactly if the android interface is hardware accelerated, I am going to try the updated GLES library.
prexzone said:
no wifi no camera...how is this better than other versions? just curious
Click to expand...
Click to collapse
Cam does work (sorry about that!), and wifi is being worked on. With modules I've heard it scans, but doesn't connect.
xanathar said:
Thank you all! First impressions with my RHOD100/AUO with FRX06:
Instant sleep and wakeup! It seems that the intermediate sleep state led (blinking green) is not available in this kernel, so amber=awake and green=sleeping. Trying to wake up the phone while freezing applications (screen off, amber -- former blinking green) brings up the backlight but not the panel, touching the screen brings up the panel. This is 100% reproducable.
Data works great with hyc's ril2.
In-call audio did not work correctly, but this was also the same with the .27 kernels, a problem which seems to be specific to my phone. Only JB's audio routing code solved this problem completely, I can only hope that this will be integrated sometime in the future.
However, FB and overall android interface did not get faster (which was discussed in IRC). I can say that it is just about the same as in .27. Don't know exactly if the android interface is hardware accelerated, I am going to try the updated GLES library.
Click to expand...
Click to collapse
Thanks for the feedback! Interesting that you didn't feel any speed boost. I've been having some oddities with severe slowdowns, but when those aren't happening it seems very fast .
You're right about the rest too, I can confirm that I've had some issues where it won't wake properly when the LED is orange - and you're also right that there's not intermediate blinking state, just solid orange or solid green. I need to flesh out the first post .
when boot up, windows found an unknown device "ethernet gadget", where can I found this driver
When SMS in , phone auto reboot
muziling said:
when boot up, windows found an unknown device "ethernet gadget", where can I found this driver
When SMS in , phone auto reboot
Click to expand...
Click to collapse
I said adb doesn't work... I guess I should refine that and say "nothing USB works".
No clue on your SMS issue, sounds wacky. Post logs.
arrrghhh said:
I said adb doesn't work... I guess I should refine that and say "nothing USB works".
No clue on your SMS issue, sounds wacky. Post logs.
Click to expand...
Click to collapse
not USB works ,how to use dmesg to get logs?
May be wifi is the only way
Command in file /sdcard/conf/froyo.user.conf seems not be executed, I add "rm -f /sdcard/fsck*.rec", file not deleted, switch back to .27 kernel , work normal.
muziling said:
not USB works ,how to use dmesg to get logs?
May be wifi is the only way
Click to expand...
Click to collapse
But don't forget wifi doesn't work
I noticed a decent speed up and no stability problems with my short testing. Will do some more testing tomorrow.
Took it out for a little spin on my semi-retired RHOD400. Keyboard repeat bug is still there it seems. I'll post a dmesg dump if it's useful.
http://db.tt/YP4kMo5
-- Starfox
Test in my RHOD100 with my daily working CWM1.8 plus froyo blue :
Sleep and Wakeup works well just like WisTilt2's 4/15 test kernel.
EDGE works.
Still have no incall but outcall works well.
Also i didn't feel faster since i still get some lag when go into drawer of adw, but it is good to see a .39 working in our phone!
Looking forward to wifi!
muziling said:
not USB works ,how to use dmesg to get logs?
May be wifi is the only way
Command in file /sdcard/conf/froyo.user.conf seems not be executed, I add "rm -f /sdcard/fsck*.rec", file not deleted, switch back to .27 kernel , work normal.
Click to expand...
Click to collapse
Hrm, that's interesting the kernel would affect whether or not that file is processed...
Anyways, you can always just pull up a command line and pull logs there, dump 'em to the SD card. C'mon, this thread kinda assumes you know what you're doing. If you don't, you probably shouldn't be mucking with such an advanced things... Thanks!
hmmm phone does not reboot when receiving a sms but it just goes to sleep
else booting is way faster then the previous kernels.
data connection works . wifi idd not.
nothing else noticed yet
Do I need the modules for bluetooth? My BT does not start.
the new...
...kernel .39 killed my wifi, i now get an error
latinohot said:
...kernel .39 killed my wifi, i now get an error
Click to expand...
Click to collapse
Um, did you bother to read the second post (known issues) at all?
I installed [ROM] CM7 T989 Kang R1 Update and I am unable to make a phone call. It keeps freezing up, or I can't hear anything. Anyone else have this issue?
After some reading I got it figured out. Wifi has to be off and gps on when you reboot.
Jesse_01 said:
After some reading I got it figured out. Wifi has to be off and gps on when you reboot.
Click to expand...
Click to collapse
Amazing what that can do
Noone else has this issue. Just you.
Sorry for asking this, but: When you reboot after first boot? and Do they have to stay that way?
Jesse_01 said:
After some reading I got it figured out. Wifi has to be off and gps on when you reboot.
Click to expand...
Click to collapse
Wifi can be on or off.... However!
GPS Must be ON at every reboot, or..... well, take a wild guess
once booted you can turn off gps without it effecting the audio.
Thanks! I didn't figure out how to fix it so I had to go to FoxStar even though CM7 is my personal favorite.
---------- Post added at 01:46 AM ---------- Previous post was at 01:29 AM ----------
What if I miss one reboot? Will I have to reflash?
eugene373 said:
Wifi can be on or off.... However!
GPS Must be ON at every reboot, or..... well, take a wild guess
once booted you can turn off gps without it effecting the audio.
Click to expand...
Click to collapse
Ah thanks a lot for summing it all up. And I AM SO GLAD someone is actually working on CM7, thank you.
Sent from my SGH-T989
Hi Guys,
I recently buyed an android headunit for my BMW e46.
I do have some trouble with my headunit. The first time I booted it up, the bluetooth and wifi wasnt working properly. After a Factoryreset it worked, so everything was fine for me.
Then again, I had to unplug the radio for refitting it. After the next Boot, wifi and bluetooth again nor working. The slider for wifi could not be moved, when I tried to slide it over to "on", it immedieatly turned to off again. The bluetooth settings didnt show a PIN or device name.
Again, a Factoryreset. So far so good. 3 Days everyhting worked fine, excerpt for some sound bugs with "blitzer.de" (an app for traffic camera warnings) and music playing at the same time. I really hope I can get rid of this too.
But anyway, yesterday morning, I started my car, and wifi again, could not be turned on. The slider always goes back to off. I tried the factory reset password for deactivating wifi (sonotech), but its only saying "wrong password". Frustrated from that, I just started my ride and about 10 minutes later a call arrived me, and the bluetooth was suddenly working. So was the wifi too. I dont know why and I am curious what it could be. Is my unit broken?
About the sound issue. As far as I can tell, its hapenning when 2 apps are trying to produce sound at the same time. Maybe this could be resolved with hal9k oder malaysk rom, but I dont wanna try this, before im not sure that my unit is not faulty.
Hope someone can help me. Thank you very much.
Hej, sometimes it also happend at my unit. Its enough when you do a reboot with the terminal command: reboot. I think it is because the power button makes just a hot reboot.
Hi crazybird, i was searching for a method for rebooting. Do I need a thirdparty app for terminal, or is this anywhere, where i didnt found it so far?
Did you try to flash a custom rom? e.g. Hal9k or malaysk?
Greetings.
crazybird82 said:
Hej, sometimes it also happend at my unit. Its enough when you do a reboot with the terminal command: reboot. I think it is because the power button makes just a hot reboot.
Click to expand...
Click to collapse
PeterPi1 said:
Hi crazybird, i was searching for a method for rebooting. Do I need a thirdparty app for terminal, or is this anywhere, where i didnt found it so far?
Did you try to flash a custom rom? e.g. Hal9k or malaysk?
Greetings.
Click to expand...
Click to collapse
I switched two days ago to hal9k and its awesome, but it didn´t fix it... The solution for me is the usb-hub-sleep-fix: https://forum.xda-developers.com/showpost.php?p=78204931&postcount=70
crazybird82 said:
I switched two days ago to hal9k and its awesome, but it didn´t fix it... The solution for me is the usb-hub-sleep-fix: https://forum.xda-developers.com/showpost.php?p=78204931&postcount=70
Click to expand...
Click to collapse
Hi crazybird, that really sounds like a solution to this problem. But it general it is interesting, that the manufacturers are not able to getting it working permanently.
Are all of us affected with this problem? Or maybe just guys with a XRC MCU? Don't know if you got one.
Anyway: thanks in advance for your help!
PeterPi1 said:
Hi crazybird, that really sounds like a solution to this problem. But it general it is interesting, that the manufacturers are not able to getting it working permanently.
Are all of us affected with this problem? Or maybe just guys with a XRC MCU? Don't know if you got one.
Anyway: thanks in advance for your help!
Click to expand...
Click to collapse
Hi PeterPi, Have you tried this solution? when i got through, it seemed to me quite complicated, if this is really working, i´ll jump on it straight away and will hope that i can manage it , because it looks like only one possible solution, to solve this terrible issue.
Thanks for reply
---------- Post added at 10:25 AM ---------- Previous post was at 10:06 AM ----------
crazybird82 said:
I switched two days ago to hal9k and its awesome, but it didn´t fix it... The solution for me is the usb-hub-sleep-fix: https://forum.xda-developers.com/showpost.php?p=78204931&postcount=70
Click to expand...
Click to collapse
Hi Crazybird, I´m running on hal9k second day, and also still experiencing BT and wifi issue, after wake up.
Thanks for your provided solution, will try it to fix it according to your provided post. I saw that you posted it 1 day ago, so can you confirm that you are not experiencing this issue anymore? I´m running out of ideas, i´m really disappointed about this on my, one week old radio and it´s really time consuming and stressful to finally get working solution. I´m still in touch with the seller, but he is not such a helpful, so i hope you´ll be my hero ! thank you in advance
mr.bena said:
Hi PeterPi, Have you tried this solution? when i got through, it seemed to me quite complicated, if this is really working, i´ll jump on it straight away and will hope that i can manage it , because it looks like only one possible solution, to solve this terrible issue.
Thanks for reply
---------- Post added at 10:25 AM ---------- Previous post was at 10:06 AM ----------
Hi Crazybird, I´m running on hal9k second day, and also still experiencing BT and wifi issue, after wake up.
Thanks for your provided solution, will try it to fix it according to your provided post. I saw that you posted it 1 day ago, so can you confirm that you are not experiencing this issue anymore? I´m running out of ideas, i´m really disappointed about this on my, one week old radio and it´s really time consuming and stressful to finally get working solution. I´m still in touch with the seller, but he is not such a helpful, so i hope you´ll be my hero ! thank you in advance
Click to expand...
Click to collapse
Yes, I can. I tried it five times and allways was it working. After some secounds when it start, there comes the alert and than its working. Its not so difficult. It just seems to be ... But if you have the hal9k rom you have to do the tasker to the whitelist for the sleep in the mod-menu!
Good luck!
PS: I love the hal9k-Rom, I can do what I wish to do! So now its nearly perfect to me.
---------- Post added at 11:23 AM ---------- Previous post was at 11:04 AM ----------
I send the solution to the seller of the xrc devices. So I hope, they will give it to XRC and than they will fix it!
crazybird82 said:
Yes, I can. I tried it five times and allways was it working. After some secounds when it start, there comes the alert and than its working. Its not so difficult. It just seems to be ... But if you have the hal9k rom you have to do the tasker to the whitelist for the sleep in the mod-menu!
Good luck!
PS: I love the hal9k-Rom, I can do what I wish to do! So now its nearly perfect to me.
---------- Post added at 11:23 AM ---------- Previous post was at 11:04 AM ----------
I send the solution to the seller of the xrc devices. So I hope, they will give it to XRC and than they will fix it!
Click to expand...
Click to collapse
Hello my friend, can you help me with one thing ? How can i get into PX5's internal storage (/storage/emulated/0) where i have to storo text document and of course i have to type this folder path to the Tasker. On hul9k are folders are differently named, how did you solve it please, thank you
Use the total commander - ist free. Give the total commander root - it will ask in hal9k. It's a file commander, maybe, the best for Android. With this you cann go into the inernal storage. Give the sh file the chmod 755 -> Right click in the total commander -> properties.
PS: /storage/emulated/0/Downloads <- /storage/emulated/0 -> So, ist like your home-dir.
crazybird82 said:
Use the total commander - ist free. Give the total commander root - it will ask in hal9k. It's a file commander, maybe, the best for Android. With this you cann go into the inernal storage. Give the sh file the chmod 755 -> Right click in the total commander -> properties.
PS: /storage/emulated/0/Downloads <- /storage/emulated/0 -> So, ist like your home-dir.
Click to expand...
Click to collapse
Thank you, later on that day i found a way.. same as you i used total commander. All went smooth until to the point 11.) Tap the check box where it says "Use Root". THIS STEP IS CRUCIAL!
There when i ticked the box, pop-up showed me, that my device is not rooted.. Today will proceed with next try, where i proceed the rooting too. Thanks for your continually help
Just to let you guys know, I will return my unit. Don't get me wrong, this fix is really a good choice for people who have no chance turning it back (e.g. Aliexpress buyers). But i buyed mine from ebay in germany. So they need to take it back. The seller says he is sending me a return label and is sending me a unit which, I hope, does not have this failure. But I am also thinking about sending this one back, and buying from another seller. This Unit was from the seller "A-Sure" (Asure).
This could also be just a fix for a couple of weeks/month. Maybe this works forever, but it's a fact that this is only necessary because of a hardware failure, therefore i take a new one without this.
Just curious at the moment which unit I will take. I thought maybe i can guess the MCU manufacturer from the launcher displayed at the ebay pictures. But maybe thats random. A HA MCU would be nice. Do you guys have a tip for me? Only buying "dispatched from germany".
Greets
this wifi problem is only with the CPU coreboard is not fixed properly
take out the coreboard and put it properly
Update,, i saw in youtube that his headunit will loose internet when time isnt correct, am not sure but my time is set right but i still went to settings and changed from gps auto time adjustment to network time adjustment and somehow i get to make net working
When I got my device, the vibration was strong. Now I have no vibration whatsoever. All settings are good. I can't even get haptic feedback. I searched in Google and saw a couple others with this problem. Sounds like a hardware issue to me. Anyone else experiencing this yet? SM-N975F/DS
Dial *#0*# and run vibration test. That should tell you if it's hardware. If it works I would reset it, if it doesn't I would sent back.
pete4k said:
Dial *#0*# and run vibration test. That should tell you if it's hardware. If it works I would reset it, if it doesn't I would sent back.
Click to expand...
Click to collapse
Neat trick. No it doesn't work. I've been hearing many more cases of this popping up. I suspect there'll be many more to come.
Yeah, same to me. I was so convinced that mine is an isolated case that I did not even thought to search for similar threads.
Mine does not work either when running Samsung test trick (*#0*#)
---------- Post added at 12:29 PM ---------- Previous post was at 12:23 PM ----------
awakener777 said:
Neat trick. No it doesn't work. I've been hearing many more cases of this popping up. I suspect there'll be many more to come.
Click to expand...
Click to collapse
You mention "hearing" about many more cases... Where?
big_ipaq said:
Yeah, same to me. I was so convinced that mine is an isolated case that I did not even thought to search for similar threads.
Mine does not work either when running Samsung test trick (*#0*#)
---------- Post added at 12:29 PM ---------- Previous post was at 12:23 PM ----------
You mention "hearing" about many more cases... Where?
Click to expand...
Click to collapse
There's a lot of you look through here
https://us.community.samsung.com/t5/Note10/bd-p/Note10
Any answers?
So my note 10+ started doing this this morning. I do the phone test and it vibrates, but is weaker. Keyboard vibrate doesn't work. Notification vibrate doesn't work, nothing else vibrates. Not sure what is going on.
Edit: looks like something turned my vibration sensitivity way down. Working now!
No problem on my N975F/DS with vibration after official Android 10 update. Vibration test, keyboard feedback, vibrate on phone call also work as before...
@OnnoJ same problem, after update, vibration stop working... altough it could be that it didnt work before i am not 100% sure