Yes, I know that this post is device specific, but deal with it! I am attempting to discover if there is/are any maintainer/developer working on this device? I have attempted to run the PAC rom for the expressatt a number of times, but the rom is not working with this device. It will run when connected to wifi, but away from wifi, there is no connectivity to AT&T systems. A while ago, CM11 had this problem, where one of the nightlys update broke the modem. This was found and fixed a few days later by the developer that works with this device. I don't know the exact code that was used, but I have been attempting to discover whether or not any devs are around. Doesn't appear so, just us users!! If any developer/maintainer is currently working on the PAC rom, let me know and I can supply more info.
thanks
Related
I have a stock, unrooted Galaxy Nexus GSM purchased new from Google currently running 4.3.
I have a FitBit Flex which will only sync with phones that have Bluetooth Low Energy support.
I can not find any information on any of the KitKat ROMs out there for Galaxy Nexus to see if I install it, will Bluetooth LE work?
If it does then work, my next concern would be if the FitBit app would recognize that the Bluetooth LE works and it would then be able to sync, or if it simply would still see it as a Galaxy Nexus which they do not list as a supported device: http://www.fitbit.com/devices
If anyone can offer me some advice here, I'd greatly apprecaite it!
Thanks.
(btw, sorry if this is in the wrong froum. please move it if it is)
adamwsh said:
I have a stock, unrooted Galaxy Nexus GSM purchased new from Google currently running 4.3.
I have a FitBit Flex which will only sync with phones that have Bluetooth Low Energy support.
I can not find any information on any of the KitKat ROMs out there for Galaxy Nexus to see if I install it, will Bluetooth LE work?
If it does then work, my next concern would be if the FitBit app would recognize that the Bluetooth LE works and it would then be able to sync, or if it simply would still see it as a Galaxy Nexus which they do not list as a supported device: http://www.fitbit.com/devices
If anyone can offer me some advice here, I'd greatly apprecaite it!
Thanks.
(btw, sorry if this is in the wrong froum. please move it if it is)
Click to expand...
Click to collapse
See here.
http://forum.xda-developers.com/showthread.php?t=2492436
With any kitkat rom I install only the modified apk from that thread and everything is ok!
Il you wanna stay with 4.3 you must install btle libraries as mentioned in the thread.
Gnex supports BLE with almost every KK rom.
(try BLE Checker on play store: on my Vanir says Supported!)
yes, and wrong place to ask this
caluz78 said:
See here.
http://forum.xda-developers.com/showthread.php?t=2492436
With any kitkat rom I install only the modified apk from that thread and everything is ok!
Il you wanna stay with 4.3 you must install btle libraries as mentioned in the thread.
Click to expand...
Click to collapse
THANK YOU, THANK YOU, THANK YOU!
I used The Nexus Root Toolkit (by WugFresh) to Unolock and Root my GNex. Then I used the link you gave me to get the BTLE files and the FitBit apk. I installed everything and it freakin' works!!! I'm so happy!
I'm so annoyed at Google for letting support of this device go after only 18 months. I bought it because they praised it as being thee flagship, unaltered, always up-to-date phone to have. I figured I'd be on the latest version of Android with this phone for many years. I wanted to keep it stock, but they've forced me to now go rooted. I suppose I could now flash a KK ROM, but I'm not sure what that would benefit me at this point.
Thank you again SO much for your help and fast reply! (Even if I did post this in the wrong place!)
Love XDA!
Ok, so I have to update what happened. Everything seemed to be working fine until I got into my car. My GPS has a bluetooth connection. It would connected, but then almost immediately the Bluetooth service would crash on my phone. Happened over and over again. Even after a reboot. Then when I got home, I tried it with my bluetooth speaker. Same exact thing. I figure the bluetooth binaries that I installed screwed up my connections that used to work. I even tried re-pairing them. Didn't help.
I gave up and decided to wipe everything and flash KK. I used CM11 nightly. Now everything, so far, is working as expected. GPS, speaker & fitbit. CM KK takes some getting used to over stock JB. I don't know what changes are KK and which are CM.
good night
a time ago, for curiosity I wanted to prove a rom kitkat of Cyanogenmod 11... good, only I her used approximately 2 weeks since the truth did not convince me,
so I decided to return to the firmware of Telcel (mexico) on having installed to him the firmware ... the Wifi did not work already, it was not activated, so I tried to put another firmware of mexico, and I mark myself a strange error, whole, end up by putting the emergency recovery that KIES has
and there I was put by a firmware that is
version of Baseband I9195LUBUAMF3 and compilation
JDQ39. I9195LUBUBNC2
but from there ... the NFC did not work already ... the active thing, and it is deactivated only to 3 seconds,
later the speaker trumped me, send the team to guarantee, and in technical service they always iron the most recent firm, and it continues without raising the NFC
will it be any problem in hardware, or in the change of rom and firmware??
greetings and thank you very much
hello, good day....
to do tests,install Cyanogenmod 11 again, only to see that there the NFC works
and in this custom rom, if it works correctly, the question is, because in that of stock it does not work:S
there is already a thread about the not working nfc issue and a solution to fix this. look into it
junkyde said:
there is already a thread about the not working nfc issue and a solution to fix this. look into it
Click to expand...
Click to collapse
thanks
http://forum.xda-developers.com/showthread.php?t=2562485&page=3
I found the solution to my problem
thank you
Hi Guys, I thought I would make a thread here as i can not seem to be able to find a solution. Rooted my device obviously, everything is fine until I installed a "Kernel" (cant remember author) to overclock mainly then encountered several problems. 1: Wi-Fi has become unstable. It seems to either crash my phone or signal disappears after my phone is on standby for a period of time (variable). 2: My Bluetooth just does not work. At all!! I have not done anything more to my device so the solution (hopefully). I forgot to mention that it is STOCK ROM. I do not wish to wipe my phone clean, i want to find a fix. Possibly a more stable kernel. Overclocking does not want to happen either but the "Governor's, I/O Scheduler's and Underclocking" do work. If there is anything more you guys need to know please ask!!
Looking forward to ideas
Kye
KyeWalker said:
Hi Guys, I thought I would make a thread here as i can not seem to be able to find a solution. Rooted my device obviously, everything is fine until I installed a "Kernel" (cant remember author) to overclock mainly then encountered several problems. 1: Wi-Fi has become unstable. It seems to either crash my phone or signal disappears after my phone is on standby for a period of time (variable). 2: My Bluetooth just does not work. At all!! I have not done anything more to my device so the solution (hopefully). I forgot to mention that it is STOCK ROM. I do not wish to wipe my phone clean, i want to find a fix. Possibly a more stable kernel. Overclocking does not want to happen either but the "Governor's, I/O Scheduler's and Underclocking" do work. If there is anything more you guys need to know please ask!!
Looking forward to ideas
Kye
Click to expand...
Click to collapse
It not the root that causing the issue, it the kernel that tried. If I remember correctly there's only two kernel for the S4 mini that allows overclcoking, and one of them has stopped developerment since last year. That leaves the F4k kernel.
He has two different kernels: one for the AOSP/CM (custom) ROM another is also a bit outdated for the default Samsung TouchWiz ROM. Are you sure you've download the correct kernel?
TNCS said:
It not the root that causing the issue, it the kernel that tried. If I remember correctly there's only two kernel for the S4 mini that allows overclcoking, and one of them has stopped developerment since last year. That leaves the F4k kernel.
He has two different kernels: one for the AOSP/CM (custom) ROM another is also a bit outdated for the default Samsung TouchWiz ROM. Are you sure you've download the correct kernel?
Click to expand...
Click to collapse
Well to my knowledge I had used the correct kernel....... I never used one from here but I did find a website claiming that F4k has a stock over clocking kernel...... Unfortunately for the life of me I can not find this website. I've managed to overclock with success using a apk. I found on here (performance control) brilliant tool!! Is there any chance you able to post a link to this stock kernel you talk about so I can test myself and report back? Everything else is working without a problem apart from Wi-Fi and bluetooth.
Kye
KyeWalker said:
Well to my knowledge I had used the correct kernel....... I never used one from here but I did find a website claiming that F4k has a stock over clocking kernel...... Unfortunately for the life of me I can not find this website. I've managed to overclock with success using a apk. I found on here (performance control) brilliant tool!! Is there any chance you able to post a link to this stock kernel you talk about so I can test myself and report back? Everything else is working without a problem apart from Wi-Fi and bluetooth.
Kye
Click to expand...
Click to collapse
For custom ROM - http://forum.xda-developers.com/showthread.php?t=2568479
For Samsung TW ROM - http://forum.xda-developers.com/showthread.php?t=2636890
summarise.....
TNCS said:
For custom ROM - http://forum.xda-developers.com/showthread.php?t=2568479
For Samsung TW ROM - http://forum.xda-developers.com/showthread.php?t=2636890
Click to expand...
Click to collapse
So I've come to a conclusion after many weeks of testing and searching........ Unfortunately the overclock kernel for "TouchWiz" roms is unstable........ looking through forums I can see that F4k has only realised a "test" version....... on the other hand I have found a kernel from Vikinger (if spelt correctly) that's has fixed my issue and is working great... shame it isn't overclocked nor under and has no additional governors..... any one with ideas please feel free to share..... many thanks.
Kye
Hi.
First of all, thanks for all you great people for working and developing for these phones.
Today, for the first time, I flashed my phone. Having android on Wave 2 feels great!
I installed CarbonRom but I'm not entirely satisfied with it and wanted to try to install some other ROM (like ZenDroKat, I heard good things about that one) and run into a problem. I noticed that my PC doesn't see the phone at all! There is no reaction, not sound when connecting the phone. I tried the front and the back usb-ports, and on our family laptop. The multiloader doesn't find the port either.
Although it did react in recovery mode (TWRP) and installed drivers for "Android Composite ADB Interface", whatever that is.
Or could I install a new ROM without trying to fix this?
Once i had a problem detecting my phone , i was so frustrated : what worked with me , maybe this sound silly but :
Does your phone charge with the USB cable :
if yes in mini USB port there is a tongue inside , trying raising it a little with a sharp metal
if no , maybe your cable is the problem .
between that and this , probable you can install Omni rom , by copying the rom to sdcard if you have external card reader , since you have already TWRP installed.
Thanks.
I did figure it out. Well, I didn't fix it on CarbonRom but I managed to install another ROM. The USB worked in Download Mode, so I just re-installed Bada and then installed ZenDroKat ROM. For now it seems to work fine.
Now, is there a way to delete your own threads?
I have Windows 8 on my computer, when I update my windows with connected phone it shows Acer updates in Microsoft update menu. I update all, and after my computer didn't recognize my phone. Then I delete Acer drivers and it recognize again
Sent from my GT-I9000 using XDA Free mobile app
DkayBlack said:
Thanks.
I did figure it out. Well, I didn't fix it on CarbonRom but I managed to install another ROM. The USB worked in Download Mode, so I just re-installed Bada and then installed ZenDroKat ROM. For now it seems to work fine.
Now, is there a way to delete your own threads?
Click to expand...
Click to collapse
i think Omni is better ,and stable ,try it
ice_ice said:
i think Omni is better ,and stable ,try it
Click to expand...
Click to collapse
Yeah, I'm having issues with ZenDroKat. Namely, it often refuses it go out of sleep mode, I missed phone call due to that.
I'm going to try Omni then, thanks for advice. There are so many roms, it is hard to determine which one is better at a first glance.
DkayBlack said:
Yeah, I'm having issues with ZenDroKat. Namely, it often refuses it go out of sleep mode, I missed phone call due to that.
I'm going to try Omni then, thanks for advice. There are so many roms, it is hard to determine which one is better at a first glance.
Click to expand...
Click to collapse
Short development history: by Rebellos
The project has been started by Oleg in March 2011 - development progress has been made rapidly by him, however, he had been using JTAG Riff Box to make Wave oneNAND memory organisation the same like in Samsung Galaxy S (SGS) I9000 - phone with very similiar hardware to Wave. The problem is it's very expensive and advanced stuff. In the meantime mijoma found security hole in Wave's Bootloader3 (BL3) FOTA loading code and made PoC-exploit for that. That allowed me to create, with help of srg.mstr, mijoma and b.kubica, simple Badadroid bootloader, loading kernel zImage from moviNAND flash memory - this is where port has been made bootable on literally any Wave phone. However, oneNAND layout still remains untouched and by default kernel is configured to use SGS oneNAND partitions. So nbates66 and anghelyi put all their efforts into making this method of booting operatible. It succeed after few days and ShadowAS1 had released unofficial tutorial explaining how to bring up pre-alpha Android into S8500 device. The problem was that only 1 bootloader version was supported this time, mijoma came up with idea of making our FOTA bootloader capable of supporting alot of bootloaders - he created "BL Univ Boot FOTA". Oleg became very busy with his real life stuff so kernel development practically stopped. Currently I'm the most active kernel developer, altough I'm not so experienced as Oleg is and I'm learning from scratch so it goes very, very slow.
December 2011 - KB_Jetdroid contacted me and we started to work on Jet&Wave modem driver.
April 2012 - mikegapinski has joined the project to get things together and make first really working ROM.
9 April 2012 - Mike got ICS platform booting.
Mike has stopped maintaining platform so I took it over.
Oleg has finally got S8530 in his hands and made SCLCD driver for it. Praise him!
Both S8500 and S8530 versions are semi operatible. The most complicated, annyoing, and needed driver is Modemctl+RIL.
March 2013 - World's first working non-AT commands based RIL for non-Android phone has been released. Most of the implementation was done by KB_Jetdroid, me and Volk204, basing on opensource Replicant's RIL for Samsung Galaxy S.
April 2013 I finally fixed S8530 display driver.
September 2013 - we've got working microphone recording, and shortly after Tigrouzen found a proper patch fixing voice communication during calls.
22 September 2013 - we released first version capable of multicalls.
~~October 2013 - GPRS connections are working
Currently most of the core work is done.
We are working hard with Volk204 on RIL interface, doing small progress day by day.
en very brief : there was one team , that did all the work since the start ,"the Badadroid team" , Badaroid developed by Rebellos and Volk204 was a base for Omnirom ported by volk204 which he is the main developer now , and all those rom you see is basically noob roms , they copy the work of Volk204 , they are actually no developers in the first place, if Volk204 doesn't fix the bugs in his roms , their roms has them . i would recommend
Nand - use Omni rom http://forum.xda-developers.com/showthread.php?t=2800014
u wanna keep bada - Badadroid 4.4 http://forum.xda-developers.com/showthread.php?t=2609560
Hero355 is also a good one but he has own bugs and he isn't around much this days , work on it stopped http://forum.xda-developers.com/samsung-tizen/bada-android/rom-carbonrom-s8500-s8530-t2840174
read this thread http://forum.xda-developers.com/showthread.php?t=1459391
Thanks, that's quite interesting.
It's amazing that you people are still developing for these phones. They are so outdated that I wouldn't have guessed that anyone bothered with them.
ice_ice said:
u wanna keep bada - Badadroid 4.4 http://forum.xda-developers.com/showthread.php?t=2609560
Click to expand...
Click to collapse
Why would anyone want to keep bada? Isn't the main reason to install android-based ROM to get rid of that awful system? :laugh:
DkayBlack said:
Thanks, that's quite interesting.
It's amazing that you people are still developing for these phones. They are so outdated that I wouldn't have guessed that anyone bothered with them.
Why would anyone want to keep bada? Isn't the main reason to install android-based ROM to get rid of that awful system? :laugh:
Click to expand...
Click to collapse
THIS IS AN ALPHA, RELEASED FOR YOU TO PLAY WITH AND GET A SENSE OF WHAT’S TO COME. AND SOME THINGS DOESN’T WORK. REALLY. IF YOU ARE EXPECTING ANYTHING CLOSE TO PERFECTION, WALK AWAY FROM YOUR COMPUTER, LOWER YOUR EXPECTATIONS FOR AN HOUR OR SO, THEN COME BACK. MORE EXCITING DISCLAIMERS/WARNINGS IN ALL CAPITAL LETTERS CAN BE FOUND BELOW. READ THEM.
KNOWN BUGS (what doesn't work):
- Modem in 2G mode work incorrect(Network registration don't work with some SIM cards, permanent full signal straight, problem is with audio in calls)
With 3G all is OK, Use this: Settings -> More.. in "wireless&network" category -> Mobile Network -> Preferred Network type -> 3G only
- Conference Calls
- Some problems with audio codec settings, but generally it should
For me : Call diverting , not working
GPS not fully working
Roms is amazing , fast , but not so fast when installing Gapps ,(i did install them , but i disable all of it)
Battery life
don't get me wrong Omni is my daily rom , but this could be a problem if talk to much on phone , battery drop out fast , with average use it won't last 10 hours
Thank g*d for XDA, anyone UK three users have any ideas why official three in touch apps doesn't work with official stock CyanognOS rom or mod nightlys , app will continually deactivate?.... thankfully @beroid 's port of Temasek' CM13 work just fine. I am thinking we will be able to gain a few clues there
Thank g*d for XDA, anyone UK three users have any ideas why official three in touch apps doesn't work with official stock CyanognOS rom or mod nightlys , app will continually deactivate?.... thankfully @beroid 's port of Temasek' CM13 work just fine. I am thinking we will be able to gain a few clues there
I don't think my app is deactivating with standard (nonmod) COS 12.1 and it will call out and receive. But the other person can't hear me -- or hardly hear me. Used to work fine with COS 11. I'm wonerding whether to try re-installing the app. I'm not a techy person! My phone isn't rooted. Any ideas where to get help on this with answers that I can understand?