Related
So just getting into the whole rooting and custom ROM install thing, still trying to fully understand what everything means.
So I figured WiMax refers to 4G, hopefully right about that.
What is a Kernel?
What are the Radios and what is included in them?
Feel free to use computer analogies, I'm pretty tech savvy with that.
Sent from my PC36100 using XDA App
kernels types: bridges hardware and softwares processes.
Radio: Also referred as GSM (see below) - commonly used in the form `upgrading the Radio/GSM` - in the field of ROM upgrading. The `Radio` is essentially a ROM that controls the phone function part (as oppose to PDA function part) of your phone. Upgrading this `Radio` software may have effect on your phone reception quality, battery life (optimized phone function), signal strength, etc.
GSM: A system of mobile radio communications. Most common 2G standard. Often used on xda-developers somewhat confusingly to refer to the radio protocol stack or `Radio` in XDA devices. This is slightly misleading as 3G HTC phones use a W-CDMA stack for the 3G communications, and GSM for 2G. In some languages, GSM also refers to the mobile phone itself.
wiki wiki
The kernel, in very non-technical terms, is basically the lower level operating system of the phone. So many things run through the kernel that it's important to choose a kernel that is compatible with the rom you are using. For example, using the wrong kernel on an AOSP rom like MIUI will cause you to lose bluetooth, wifi, or many other things.
Kernels can control how your processor works too. With the right kernel you can overclock, underclock your phone for performance, or better battery life. My personal favorite is SavagedZen if you are using an AOSP rom. They do a great job of taking every request from every rom/app developer and putting the tweaks in their kernel. They support all the HDMI apps out there, they support Wimax (4G), and they are really well optimized.
As far as radios, that is the software that helps your phone connect to things like Wifi, bluetooth, 4G, 3G, GPS, and anything else that requires data come to your phone wirelessly.
Hope that answers your question in simple terms.
hi,
well i'm against that policy, not able to post at developer threads under 10 posts, else I would have question that directly,...
I've tried several roms and ended at slim beam, first to 4.2.1 which states at stable but also tested the new one 4.2.2 build 2.5
actually i'm fine with the roms, also slim bean but I do have a 3 major issues with all of them which may be related to S3 and asop/cm:
1.) problem using my apple iphone earbuds (yes I'm a iphone user too)
sometimes after mute the microphone, it won't work after de-mute, keep on muted !
microphone not working after re-connecting earbud on a running call, sometimes no audio on earbuds too, sometimes audio even do not work for the whole device -> reboot etc,...
I've found several possible solutions, non of them has worked.
why android doesn't work with that kind of TRRS earbuds, are they incompatible from hardware point of view, do I need special ones which will work on S3.
2.) problem with direct dialing from calendar, not respecting RFC2806
i really need this very often to join conference calls, sometimes the host creates an conf call and including a number with pin as the location.
well almost every mobile os recognizes this and i'm able to direct dial in on selecting the string: iphone, win, even blackberry, but not android.
i know there might be additional apps which can handle this, but it should be implemented into core apps as this is a well known standard and specified in a RFC.
3.) not recognize AP with highest signal strengh within same SSID
it seems that android devices are not able to seamless switch over to different AP within a wifi network with same SSID.
if moving out of range of AP1 and into range of AP2, android devices for some reason are not able to switch to AP2 (with higher signal strengh), therefore it states at AP1 without beeing able to establish any connectivity (because AP1 out of range). as workaround users needs to disable/enable wifi ;-(
this is also something where I have to find a workaround in my current project (creating huge wifi network over europe), because market share of androids is that high and it still have this serious annoying bug.
thanks,
nean
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
10 post rule is there to protect developers from spam and users not knowing what belongs in a development thread and what belongs in Q&A
1. Headphones > Most likely thats just an issue with roms that are version > 4.1.2. Not all the bugs have been worked out, see if you can replicate it with another pair of headphones.
2. I suspect the same thing is going on here, or you would need some more powerful calendar sort of app.
3. This isnt because it doesnt recognize, its because Android is still connected to the last network and says to itself "no need to scan again, I'm already connected". This has to do with how the OS is implemented, not because its a bug with Android. I'm also fairly sure that most other devices do the same thing
CNexus said:
1. Headphones > Most likely thats just an issue with roms that are version > 4.1.2. Not all the bugs have been worked out, see if you can replicate it with another pair of headphones.
2. I suspect the same thing is going on here, or you would need some more powerful calendar sort of app.
3. This isnt because it doesnt recognize, its because Android is still connected to the last network and says to itself "no need to scan again, I'm already connected". This has to do with how the OS is implemented, not because its a bug with Android. I'm also fairly sure that most other devices do the same thing
Click to expand...
Click to collapse
thanks for the reply.
ad 1,2,3.) hmmm, is this working on googles stock os and eg on nexus?
ad 3.) this is only related to android devices, as tested in the lab with several other handheld devices with different kind of os'es. ios, blackberry, windows mobile, etc, all work and do seamless switchover except android. well the last known network and the new one is actually the same wifi network which is specified due SSID, so if android's rescan logic is related to that kind of info it may be wise to consider acces point strength as well, just like all the other os'ses,....
nean24 said:
ad 3.) this is only related to android devices, as tested in the lab with several other handheld devices with different kind of os'es. ios, blackberry, windows mobile, etc, all work and do seamless switchover except android. well the last known network and the new one is actually the same wifi network which is specified due SSID, so if android's rescan logic is related to that kind of info it may be wise to consider acces point strength as well, just like all the other os'ses,....
Click to expand...
Click to collapse
Did you test using stock os and not a AOSP rom like stated in the OP? You can't blame the OS for a issue if it is moded in any shape or form. Try using straight up stock TW and see if it works. AOSP and CM are not 100% designed to work on this phone flawlessly.
tazfanatic said:
Did you test using stock os and not a AOSP rom like stated in the OP? You can't blame the OS for a issue if it is moded in any shape or form. Try using straight up stock TW and see if it works. AOSP and CM are not 100% designed to work on this phone flawlessly.
Click to expand...
Click to collapse
thats correct, but it doesn't work on galaxy stock os either, that's why I've tried custom roms just to find out if its related to samsung stock rom or if its a general android behavior. well the outcome was that it works on aosp/cm a bit "better" (shorter timeout) but not seamless.
my intention is not about to blame anyone, just like to find out where I can adress this issue, or do I need to get in contact with google?
rgrds
Trying to find a kitkat ROM that supports Voice dialling via Bluetooth on my note II sgh-i317m. If I role back to 4.3 it works fine (like DN3). I am currently testing CM11 and it does not work (unless somebody has a work around)
Most bluetooth functions work fine except voice dial. I hit voice commands on my Jabra and it does hear my commands. I also tried a Motorla bluetooth device and experienced the same.
Moved to Q&A.
Based my personal research, there is no known workaround. None of the operating systems, except those based on stock Samsung kernels, properly support bluetooth. They all have issues reliably initializing an audio and microphone connection to the headset after a voice command button press.
This includes ALL of the CyanogenMod releases.
It is a fairly underreported issue, and when it is reported, noone much cares - evidently, very few people actually use bluetooth to voice command their phone. So, it doesn't get any dev time. Anyone who tries to use their phone intelligently in their car, on a bicycle, or, in my case, on their motorcycle integrated with helmet comms should STRONGLY disagree. But, not everyone can sit about comfortably all day in horn rimmed glasses and ironic facial hair in a starbucks.
In my opinion, this relegates all of these releases to mere "toy" status, since this is an elementary feature of a modern phone - but as I understand it, the problem isn't particularly curable in any case due to somewhat hostile engineering and documentation practices by everyone's favorite, Samsung.
I have done as much work as I could do in researching the problem, reporting the problem and even studying how to collect logging information and eventually, a few attempts to roll my own modified kernel to attempt to solve the problem, to no avail - keep in mind I am not an android developer by any means, and have gone to some effort to learn what I could so as not to be merely a complainer.
My advice, if you insist on departing from the vendor operating system release series, is to seek the Samsung kernel-based mods, such as Ditto Note, as you have been doing. These have a higher chance of properly supporting the headset natively. They have recently moved to a kitkat release (that I haven't tested yet,) so that may satisfy.
As for myself, I will likely leave Samsung behind for my next phone, for something a little more open source friendly, hardware-wise. Being at the mercy of vendor updates and the S-voice for something I need to use more than 3 hours a day on the road has made me feel quite a fool.
FYI, over the last few days, I installed both Official AT&T / Samsung KitKat 4.4.2 and Ditto Note 3 v5.2 (based on 4.4.2) and they both properly support Bluetooth audio and microphone for voice command after a button press.
AT&T / Samsung Official:
Unfortunately comes with a version of Google Search (v.3.6) that provides the terrible Google Voice Dialer in response to a bluetooth button press, so if you were planning on using that, be prepared to root, move it from /system/ to /user/, uninstall, and then go find and install Google Search v.3.4.
S-Voice works fine, but you may need to switch your APN from "phone" to "nxtgenphone," if you haven't done so already. Else, S-voice may only work on wi-fi, not mobile data. Check out the thread on doing so here:
http://forum.xda-developers.com/note-3-att/general/psa-s-voice-stops-volte-markets-using-t2848929
Ditto Note 3 v5.2:
Comes with Google Search 3.4 which gives correct "Listening.." when bluetooth button pressed. Be sure to uncheck auto update in google play store until Google gets their crap figured out. Phone will flash as N7105, so download and use the build.prop for i317 from their extra files and turn on the telephony.lteOnCdmaDevice=1 setting. Set also ro.product.locale.language=en_US and ro.product.locale.region=US since you're an AT&T customer. You'll also need to add the nxtgenphone APN as above, I'm afraid. It's not rooted as it comes - use your recovery to flash the SuperSU binary of choice from your SD card after installation if you want root. It all works, though, and is my OS now.
rmzalbar said:
Based my personal research, there is no known workaround. None of the operating systems, except those based on stock Samsung kernels, properly support bluetooth. They all have issues reliably initializing an audio and microphone connection to the headset after a voice command button press.
This includes ALL of the CyanogenMod releases.
It is a fairly underreported issue, and when it is reported, noone much cares - evidently, very few people actually use bluetooth to voice command their phone. So, it doesn't get any dev time. Anyone who tries to use their phone intelligently in their car, on a bicycle, or, in my case, on their motorcycle integrated with helmet comms should STRONGLY disagree. But, not everyone can sit about comfortably all day in horn rimmed glasses and ironic facial hair in a starbucks.
In my opinion, this relegates all of these releases to mere "toy" status, since this is an elementary feature of a modern phone - but as I understand it, the problem isn't particularly curable in any case due to somewhat hostile engineering and documentation practices by everyone's favorite, Samsung.
I have done as much work as I could do in researching the problem, reporting the problem and even studying how to collect logging information and eventually, a few attempts to roll my own modified kernel to attempt to solve the problem, to no avail - keep in mind I am not an android developer by any means, and have gone to some effort to learn what I could so as not to be merely a complainer.
My advice, if you insist on departing from the vendor operating system release series, is to seek the Samsung kernel-based mods, such as Ditto Note, as you have been doing. These have a higher chance of properly supporting the headset natively. They have recently moved to a kitkat release (that I haven't tested yet,) so that may satisfy.
As for myself, I will likely leave Samsung behind for my next phone, for something a little more open source friendly, hardware-wise. Being at the mercy of vendor updates and the S-voice for something I need to use more than 3 hours a day on the road has made me feel quite a fool.
Click to expand...
Click to collapse
Disclosure: I own nothing hereI am not an expert romolgist. Just a guy that hates when buttons don't do anything.
Without a working US csc folder in the Rom it's all pretty much temporary.
Since support in current threads is non existent I'll do my best to show what I've done to get data and texting. It's still a bandaid for a weak design but it's enough to get things working for a couple hours.
Results will vary and this will be updated multiple times in the next week. I'm forgetting some details.
List of apps used.
SetEdit pro - helps remove bloated junk that's greyed out.
Radio Switcher - needs to be turned to cdma-auto and lte-cdma every time signal is lost
Region changer - gets the phone labeled as US but it's incomplete. More on that later
Root essentials - easiest way to get can and build prop in one place
Partitions backup - backup-/restore efs and radio
Aurora settings - adds necessary settings that rom builders left out
APNs backup - obvious reasons
Phone info+ - get into prl enable all LTE frequencies/ disable gsm band
They're pretty much necessary for every n7 port listed today.
Step one:
Backup efs/radio/apn from WORKING rom like MOAR or stock
Download with ADM. Speed was not a priority with these ports including downloads
Pick a Rom that you like the pictures of because words don't mean anything at this point. A 928p Rom doesn't mean it will work on a 928p so don't be afraid to experiment. Had better results from 930 and R4 Roms and kernels.
Hopefully you'll see the activation screen. If not you're gonna have a bad time.
Speaking of kernels use sky but uncheck the prop and other junk box on last setup page. These ports need extra junk just to stay running. I'll post a link to another kernel I like as well as some newer clones.
Step 2
Delete everything. Seriously. Data/system/whatever
Pull your flash drive after install or it tries to write there as well.
These things seem to write anywhere they want and old data has effected startup or install times.
Flash what you liked and hope for the best.
Pick whatever country is your favorite. Means nothing to US Sprint customers
Install as a 920.
Don't take the 928 option.
Install the note5 camera
Install whatever audio driver they added. Stock hasn't worked for me
If you don't see a restart at the Samsung splash screen or blue light stays on after restart it's a bad file. You want to see a jogging pace with the dimming of the logo. Anything less than that and it's going to crash sooner than later. For US Sprint customers it's usually at the connection check.
Step 3
Be patient. These are as temperamental as the builders and require constant maintenance to avoid memory leaks and signal loss. When you read claims about battery life it's because it's missing basic functions necessary to run reliably on us Sprint towers.
Step 4
Hopefully it's showing signal. If not the only workaround is injecting a US csc to the Rom itself as well as 90% of someone else's build props and csc files. I'll show what were used once the owner gives permission.
Restore apn/efs/radio
Root explorer systen/csc/sales_code mount as rw and edit to say XAS
Change region to US
Restart
From there I'll use radio switcher and connect to cdma-auto and wait for signal. Once signal is established and you see your phone number switch it to cdma/LTE auto and restart. Verify the settings stuck. If they didn't try playing with different connections. This sometimes works. Also needed for signal loss and probably every restart.
Once data is working try editing csc until it matches a good Rom.
*added xposed that works with lam7.3
https://mega.nz/#!tdF0FKjR Aurora apk
Reserved for download links
Here's what I like. Results will vary
https://mega.nz/#!oUVxSSKb Lamlazy 7.3
https://mega.nz/#!0EFCGAob duelbootgraceux kernel
https://mega.nz/#!tBNBXCgY hidden menu
https://mega.nz/#!wM0V2LyT some beta crap that gets good LTE but needs dialers or it it comes unglued
https://mega.nz/#F!oA9Q0QyS More links including 925 and 920 combo files
Reserved for cat pictures
Got synapse to load this morning. Day and night difference after cleanup and adjustments to little cores. Loaded a MOAR profile for shiggles and both roms freeze. Knew results would probably go that way but it's fun to try and break these things instead of the usual self destruct.
Testing with this phone might be done. Charging port is pretty lose and I don't want it fixed. If anyone can add to this please do I'll keep the links alive.
My Note4 died (broke the screen and the phone was kinda beat anyway), so I bought a refurbed one. I had a full TWRP backup of my old one, so I have tried to put the new one together exactly like the old one. QC1 stock ROM, rooted (SU), deodexed, Xposed, TWRP 3.2.3 recovery, 128 GB sdcard with 80 GB as portable storage, and 35.xx GB as adopted storage. Pretty basic stuff. Two odd problems, both occurring on reboot, and a problem with data connectivity.
1. When I change the GPS mode to High Accuracy, all my GPS based apps are happy. But when I reboot the phone, the setting changes back to GPS only. I am assuming there is an XML or conf file somewhere with the wrong permissions. Anyone know where the GPS mode settings are stored, or know a way to fix this?
2. I can move apps to adoptable storage and they work great. I have used the native app2sd, Apps2SD Pro, All-in-One Tools. The apps move, and they run well. However, after a reboot, the moved app is gone. Pieces of it remain, but the apps will not run and must be re-installed. Can anyone point me towards a solution or any ideas?
I live in a rural area, and sometimes I have problems with voice and even sms service at my house. with the new phone, if i switch off WIFI, I get a solid 3G data connection and, while it is slow, it does work reliably. If I drive to where I know there is a really fast LTE connection (20-25 mbps down), about 6 miles away, I cannot get a data connection of any kind. Even if I switch the phone to CDMA only, I cannot get even a 3G connection. I don't understand why I cannot even make a 3G connection. I do have a 10 year old Airave at my house, and maybe that is where the 3G connection comes from. But I would think that would work anywhere. Anyone have a clue on this one?
Thanks very much for reading through this, and for any and all suggestions you may have!