yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Carlos_Manuel:
Bad news!

Something is really wrong in the source files, i have reverted all my changes but still nexus reboots when i try to add pin code..

I have to delete and sync all sources again..

Including all the changes what i've made.

This will take a day!

No new updates today! :(

07-29 is enough stable for daily driver, ble needs testing!
[Samsung Galaxy Nexus] styr:
Revert this change and the pin code soft reboot will go away.
[Samsung Galaxy Nexus] Carlos_Manuel:
Thanks

Are you sure?

Because I had this issue at least 5 hours ago and if I remember that commit is the latest one which haven't caused that issue.. O.o

Anyway I already deleted the files and now my PC is syncing again. :)

Also I can't click thanks because of the limit, my Nexus isn't working right now, gotta flash my ROM back... ;P
[Samsung Galaxy Nexus] AbhishekS:
Can someone please help me on this? :)

http://xdaforums.com/showthread.php?p=44075083#post44075083
[Samsung Galaxy Nexus] Carlos_Manuel:
:rolleyes:

I'll help you later. :)
[Samsung Galaxy Nexus] hanschke:
this problem I know with every 10.1 nightly and is not your mistake. I dont use a pin anymore ;)
[Samsung Galaxy Nexus] Gafanhotz:
Well, I can make a tutorial, but will take a little time.

But if it helps:

Install Android SDK Tools (fastboot, adb, etc) on your PC.

Download Stock Android Factory Image, and run the "flash-all.bat" file

Eveything will be wiped, and bootloader, radio, etc, will be updated.

Boot up your phone, see if eveything is ok and reboot back to bootloader.

Download TWRP from it's website, rename it to 'twrp.img' and go to CMD and execute: fastboot flash recovery twrp.img (Assuming the CMD is set to be on the twrp file directory.)

And one.

To install Android SDK Tools and make it run universally is the part i said that needs a tutorial, you need to set a link to it in the environment variables.

Edit:

Oh well, there's one already: http://www.androidauthority.com/how-to-install-android-sdk-software-development-kit-21137/
[Samsung Galaxy Nexus] Carlos_Manuel:
Or;

Install Samsung Galaxy nexus Verizon USB driver.

Download only fastboot and adb files by googling them (then you don't have to install SDK tools nor java jdk)

Flash recovery, boot to recovery data factory reset, boot to fastboot mode and flash system and boot and bootloader by using fastboot flash ... .IMG command and then boot nexus then files will stay in the internal storage
[Samsung Galaxy Nexus] Stigy:
Going to convert this to toro package tonight and test BLE on my Fitbit unless its already been tested.

We still unsure of BLE on Galaxy Nexus right?
[Samsung Galaxy Nexus] CommanderROR:
Yes, BLE is still a mystery...
[Samsung Galaxy Nexus] Carlos_Manuel:
Currently my notebook is syncing the source files...

When it's done, then I add Estonian language support and my translations for it and then I'll check if there is any other language translations in AOSP repositories, but no support in the builds... Then I may add the Battery LED mod to enable Battery LED while charging (can be changed from settings..)

Also because CM have a new camera app 'Focal', I think they won't really add any features to CM10.2 camera (the modded AOSP camera...) and CM10.2 camera doesn't have any CM features, I check if I can put some features for that camera... :)

BLE support will be enabled again and I have to make more research about it to make it work correctly, if it isn't working... This needs a lot of testing to be sure it is really working!
[Samsung Galaxy Nexus] Stigy:
So does the 07-29-2013 build have BLE enabled for me to test or should I wait for next build?
[Samsung Galaxy Nexus] Sdobron:
We don't know. Test it and see.
[Samsung Galaxy Nexus] Stigy:
I meant to ask if it has the commits un-done that disabled BLE.

I will test it tonight with my Fitbit, just want to make sure what I download and flash has the commits to enable BLE.
[Samsung Galaxy Nexus] Carlos_Manuel:
The support for it is enabled! :) :good:
[Samsung Galaxy Nexus] Stigy:
Alright - I'll flash this and the converter script tonight and hopefully I can report back on some BLE tonight via the Fitbit app.
[Samsung Galaxy Nexus] Carlos_Manuel:
OK, Cool! :)
[Samsung Galaxy Nexus] razi914:
Root issue fixed? I mean TB works fine now?
[Samsung Galaxy Nexus] Carlos_Manuel:
Seriously? :D

root is fixed a long time ago... just enable developer options, choose root access and select "apps" or "apps and adb" if "TB" is not working then update it, because it should be updated for JB 4.3
[Samsung Galaxy Nexus] razi914:
Downloading ur latest build, will test and report!
[Samsung Galaxy Nexus] Carlos_Manuel:
Next build should be available in 12 hours...
[Samsung Galaxy Nexus] hanschke:
12 hours :o

TitaniumBackup 6.1.0-test1

https://twitter.com/TitaniumBackup/status/361582620468985856

can anyone can confirm that the notification from golauncher e.g. are there in the notification bar after restart the phone. I have disabled them and after restart it is there again.
[Samsung Galaxy Nexus] Carlos_Manuel:
http://mahadevangorti.blogspot.fi/2013/07/android-application-bluetooth-low.html?m=1
[Samsung Galaxy Nexus] christopherrrg:
Open app info and uncheck notifications its a 4.3 bug specific.
[Samsung Galaxy Nexus] Stigy:
It's not a bug, its intended behavior when an app tries to keep its app active without a notification icon.

http://www.androidpolice.com/2013/0...tifications-after-you-upgrade-to-android-4-3/
[Samsung Galaxy Nexus] madphone:
I think it's a bug introduced with Android 4.3. Unchecking doesn't help, after reboot the notifications of go launcher/ weather are back.

Gesendet von meinem Galaxy Nexus mit Tapatalk 4 Beta
[Samsung Galaxy Nexus] christopherrrg:
Yeah, thanks!
[Samsung Galaxy Nexus] Carlos_Manuel:
Just finished porting Voice trigger from CM's packages_apps_Camera to packages_apps_Gallery2 I'm sure that the build fails but I want to try it for fun.. ;P
[Samsung Galaxy Nexus] DoesntPostAThing:
Hi guys, I flashed the 07-29 build and tested on my Fitbit. I took a video of me connecting it as well: https://app.box.com/s/ab1wmjzcddunclhepze1

I'm considering going to a stock JSS15J build now, sorry about that. Since Stigy's also got a Fitbit, I think BLE testing will be fine. Thanks guys for making this build, it was fun to test out!
[Samsung Galaxy Nexus] CommanderROR:
Did BLE connection actually work?

UPDATE: Just watched the video. Looked like it works, but did you try to actually get data from it?
[Samsung Galaxy Nexus] madd0g:
Yes, this would be good to know :P Downloading the video now, sounds exciting.
[Samsung Galaxy Nexus] DoesntPostAThing:
I'll try it again. I'm not quite sure if I'm able to sync the fitbit as it's not mine, I just have access to it. I'll see what I can do.
[Samsung Galaxy Nexus] CommanderROR:
Thanks.

I rewatched the vid and it seemed that pairing failed although the BLE app showed it as connected...
[Samsung Galaxy Nexus] madd0g:
What's this BLE app you have there ? Is it part of the apps Carlos included ?

It looks kinda like Fitbit is trying to advertise something, but can't be read by the app properly ?

This would be great if you had a working BLE phone by hand and try the same with it :]

Thanks for the video btw.
[Samsung Galaxy Nexus] CommanderROR:
Go back to page 29, link is there. Carlos also includes it.
[Samsung Galaxy Nexus] madd0g:
If you mean BLEScanner, it doesn't look like it. It's probably one of the testing apps Carlos included.
[Samsung Galaxy Nexus] DoesntPostAThing:
Update: I logged into the fitbit account (got the password from the owner) and "connected" using the BLEsample app carlos included. However, it does not show any sync settings as it should: https://help.fitbit.com/customer/portal/articles/987832

I'm not sure if this is due to it detecting that my device is "unsupported", or because the system is telling it that it's unconnected. In any case, the bluetooth indicator in the notification bar is gray. If it was actually paired with anything it would show blue. If anyone has a BLE enabled device and a Fitbit, that'd be great. I don't though, so I don't have much to compare to.

My speculation is that the BLEsample app somehow "connects" to it, and something is transmitted, but the system does not recognize it as connected. I'll try changing my build.prop device name to a supported device and try again.
[Samsung Galaxy Nexus] madd0g:
Hm, if they have to put a certain device on a whitelist, that's kinda lame.

About the BLE support: I guess it would be too easy if everything worked with just reverting the commits.
[Samsung Galaxy Nexus] CommanderROR:
Tbh, I don't really expect this to work. I think there is a reason why google went to all the trouble and had the Gnex recertified as BT3.0

What we are seeing might well be the "Bug" Google encountered.
[Samsung Galaxy Nexus] jon9314:
Gnex kernel is based on Linux e

3.0.xx and the blue enabled devices are on Linux 3.4.xx based kernels. Could there be some code or something that has to be back ported for blue to work correctly? Just a thought. I wouldn't know where to start looking. Just glad we have such great developers. Thanks for all your hard work.
[Samsung Galaxy Nexus] DoesntPostAThing:
Well, I can't seem to get root. Tried the superuser trick of disabling it and then enabling it again but it won't let me disable Superuser. I'll give this one last try, although I doubt it's gonna work.
[Samsung Galaxy Nexus] ledoweb:
Don't know if it's just me, but Crazy Taxy FCs as soon as I tap on its icon. It doesn't look like an app issue, but who knows. Some apps seem not to like Jellybean 4.3, as they became very slow or laggy (Reader+ is unusable, Nandroid Manager definetly slower).

But my point is that Google worked very hard in optimizing the overall speed and responsiveness of the system. The browser, app installing, everything feels more "solid", since you can perform several tasks together without getting freezes, black screens and loading times. On top of all, the SystemUI huge memory leak, that caused 4.2 to lag if you used a static wallpaper, seems finally solved. Wow!
[Samsung Galaxy Nexus] madd0g:
Also just remembered something: the Fitbit app probably didn't get the update yet to support the Android BLE api,so it can't sync the data properly.
[Samsung Galaxy Nexus] Molitro:
If you're trying to do it from the superuser app itself, you won't be able to.

You have to disable and enable again from the developer menu.

Swiftkey'd from my GNexus
[Samsung Galaxy Nexus] DoesntPostAThing:
Thanks, so that's what I was doing wrong. Anyways, I managed to root the device, change build.prop to fake an S4, and it still didn't work. We'll just have to wait, I guess.
[Samsung Galaxy Nexus] Carlos_Manuel:
Gallery2 building failed with voice trigger as expected... :D

Now my notebook is syncing the sources, next version will have INCLUDED CM's APP FOCAL (CAMERA)

I quickly read the new posts here. but let's make it clear:

Kernel 3.4 doesn't have any BLE commits (I quickly checked the commit history from Google's sources)

You can try to find the commits for BLE from 3.4+ kernels if you want..

As what I think about BLE:

It's working somehow, but not correctly and that's why maybe Nexus doesn't have this supported officially, we need great ROM / Kernel devs.to check out those and maybe they can do some "magic"!

Gotta build now CM10.2
[Samsung Galaxy Nexus] lovejoy777:
my new build is almost done:)

my last one did the same as yours. as soon as you touched the screen it rebooted:(.

hopefully i synced the fix..
[Samsung Galaxy Nexus] Stigy:
Nope, it already syncs with Galaxy S3, S4, etc so it has to support BLE in some form.

Since you said (downloading video now) that it won't actually sync I think that either the app knows what devices its running on and only tries to sync there or BLE is really not working on Galaxy Nexus. I will test tonight myself though just to see.
[Samsung Galaxy Nexus] DoesntPostAThing:
I doubt the app does a device check. Even if it does, I changed any build.prop value that could hint at a GNex to S4 values. I doubt the app can have any other way to determine my device.
[Samsung Galaxy Nexus] Carlos_Manuel:
On the next build is the BLE include lines included but I changed those b from false disabled to true enabled hopefully it does something amazing.

I don't feel so good so I gotta go to sleep, my notebook will compile this ROM whole night and morning.... :)
[Samsung Galaxy Nexus] Stigy:
I thought the current build had those lines changed to TRUE, no?
[Samsung Galaxy Nexus] Carlos_Manuel:
I deleted the lines. Even n4's .h file doesn't have those lines. :D

Both methods seems to be working
[Samsung Galaxy Nexus] Stigy:
So the 07/29 build has the lines deleted and the one building now has those values set to TRUE?

Sorry just want to make sure I know what I am testing for when I end up building my own ROM - thanks!
[Samsung Galaxy Nexus] Gafanhotz:
May I ask, Carlos, can you build Focal stand-alone so it can be installed on any other device? I tried my self, but ended with a lot of errors.
[Samsung Galaxy Nexus] X_N_:
Saw someone else post the APK earlier, I installed it on my Galaxy Nexus and it's working perfectly. http://d-h.st/OtT
[Samsung Galaxy Nexus] styr:
Quite sure, there was a bug for not-QCOM hardware introduced in that squash and it was fixed here.
[Samsung Galaxy Nexus] Sdobron:
Anyone have a workaround for this root explorer bug?

I did a dirty flash and hoping I can get by without factory reset. This occurs when trying to paste into /system/app and probably elsewhere.

It has root access granted.
[Samsung Galaxy Nexus] koelspy:
Maybe this is interessting for you: http://review.cyanogenmod.org/#/c/46446/
[Samsung Galaxy Nexus] lovejoy777:
good find

---------- Post added at 10:55 AM ---------- Previous post was at 10:54 AM ----------

im sure when the wizard wakes he will get a build going with those commits:)
[Samsung Galaxy Nexus] CommanderROR:
He's sleeping the sleep of the just right now... ;)

I hope it won't take another 12 hours to build with these changes added... :)
[Samsung Galaxy Nexus] Carlos_Manuel:
Yeah, I checked it and the comments.. :)

Thanks :)
[Samsung Galaxy Nexus] Carlos_Manuel:
Nothing new
[Samsung Galaxy Nexus] Carlos_Manuel:
Off topic like this is a bit annoying!

What you can to do;

Check that you have root access, try ES file manaer

contact to the app developer and the developer may update that app for JB 4.3
[Samsung Galaxy Nexus] CommanderROR:
[MENTION=218176]Carlos[/MENTION]

From the comments there ot aeems like at least Grouper has working BLE
[Samsung Galaxy Nexus] Carlos_Manuel:
I'll double check the comments right away..
[Samsung Galaxy Nexus] Carlos_Manuel:
I'm not sure, but both should work, deleting the lines works. Also editing the lines to force it enable those things...

:confused:

I haven't checked all the ble files from external/bluetooth/bluedroid, but both of those should be okay.
[Samsung Galaxy Nexus] madd0g:
Yeah, but they made the S devices work with the Samsung BLE API, not Androids one, because it didn't exist yet. So, Samsung BLE API doesn't work with the Nexus.
[Samsung Galaxy Nexus] Carlos_Manuel:
Why it took so long to build this ROM:

1. I tried to include features to gallery2 since, CM have disabled camera building on it to use Gallery2 camera, I used nice make without -jx so building was SLOW!

2. I tried to build Focal app, required some framework and lib files, notebook froze...

3. I was too sleepy, I have to get my sleeping habits in shape because of School!

4. I'm not a machine, my math isn't good, so I can't give 100% sure time of that how long building would take..

5. my Notebook is slow for Android building which takes time to build..

6. I have to test my ROMs before releasing them

:cool:
[Samsung Galaxy Nexus] razi914:
[QUOTEhearlos_Manuel;44079735]:) :good:[/QUOTE]

Sorry bro, but it was a really bad experience using this ROM, the home key wasn't working, quick k settings not working ( can't open them) , and im stuck here now , http://xdaforums.com/showthread.php?p=44101260#post44101260 please help when u r free!
[Samsung Galaxy Nexus] Carlos_Manuel:
1. Factory reset

2. Clean flash

3. Don't never report issues which are caused by dirty flash

To fix boot loop or stuck to Google logo thing:

Use fastboot to flash stock Google JB factory images

I am using my ROMs all the time so I know if something isn't working...
[Samsung Galaxy Nexus] lovejoy777:
Sorry bro, but it was a really bad experience using this ROM, the home key wasn't working, quick k settings not working ( can't open them) , and im stuck here now , http://xdaforums.com/showthread.php?p=44101260#post44101260 please help when u r free![/QUOTE]

i think its something you are doing matey. this rom is smoother than most 4.2's.

also for the chap who has root explorer issues, mine works fine on 4.3 roms. including copy/paste.

i have focal installed but it fc's when you touch the screen, a little while longer needed i think:)
[Samsung Galaxy Nexus] Carlos_Manuel:
New version seems to be working well, including Focal.

I'll upload this new build soon, then I update this to get the latest changes.

Also there is like some people who don't really appreciate my work... As what I want to say that this is not that easy as you THINK...

Also I need more free time. ;P
[Samsung Galaxy Nexus] elia222:
I know how hard is dealing with build errors and working with sources that aren't stable yet, you're really doing an amazing work. Keep it up! ;)
[Samsung Galaxy Nexus] lovejoy777:
i agree. i have been building every night for 2 months and still can only change a few strings and png's you guys that alter code/insert new features are magicians. lots of people do understand but its the odd one that doesn't that pis#es you off:) just ignor them mate:)

and as for more free time... get back in your cage and keep building or i will call the android police. :)
[Samsung Galaxy Nexus] Carlos_Manuel:
New build: 2013-07-30:

http://mbqonxda.net/manumanfred/CM10.2/

- Add back the BLE lines but intead of disabling, force enable them (another working method to enable BLE)

- Add Estonian language support, add my Estonian translations:

- Settings: values-et, xml-et

- SystemUI: values-et-large

- frameworks/base/core/res/res/ raw-et, raw-et-xlarge, values-et-rEE

- build: locale and language .mk files

- Torch

- CMWallpaper

- CMUpdater

- Apollo

Settings: Fix some aapt warnings!

Latest CM changes, including CM's Camera Focal

Nb. the translations are mine and I am not going to open source all of them, my old translations are already in my Github... ;P
[Samsung Galaxy Nexus] Carlos_Manuel:
:)

Thanks man! :)

:)

Actually editing strings and mk files is pretty easy, but editing .java or other files is pretty confusing and most of them must be edited correctly and carefully.. :laugh:

:good: :D

New build is coming really soon. :)
[Samsung Galaxy Nexus] Carlos_Manuel:
Ready for new build? :cool:
[Samsung Galaxy Nexus] castaway1:
isnt cm-10.2-20130730-UNOFFICIAL-maguro.zip new enought? :)
[Samsung Galaxy Nexus] lovejoy777:
always ready:) it just stops the shakes. :)
[Samsung Galaxy Nexus] Carlos_Manuel:
Not really! :)

This explains why:

carlos@Bad:~/android/system$ repo sync
Fetching projects: 0% (1/388) remote: Counting objects: 10, done.
remote: Compressing objects: 100% (2/2), done.
remote: Total 6 (delta 4), reused 6 (delta 4)
Unpacking objects: 100% (6/6), done.
From git://github.com/CyanogenMod/android_packages_apps_Focal
022f648..f92d834 cm-10.2 -> github/cm-10.2
Fetching projects: 4% (16/388) remote: Counting objects: 287, done.
remote: Compressing objects: 100% (153/153), done.
remote: Total 210 (delta 167), reused 76 (delta 55)
Receiving objects: 100% (210/210), 66.16 KiB, done.
remote: Counting objects: 19, done.
remote: Compressing objects: 100% (4/4), done.
remote: Total 10 (delta 4), reused 8 (delta 2)
Unpacking objects: 100% (10/10), done.
From git://github.com/CyanogenMod/android_frameworks_opt_telephony
4b2e2a2..7cc4b70 cm-10.2 -> github/cm-10.2
Resolving deltas: 100% (167/167), completed with 74 local objects.
From git://github.com/CyanogenMod/android_frameworks_av
fec99cc..6487892 cm-10.2 -> github/cm-10.2
Fetching projects: 6% (24/388) remote: Counting objects: 470, done.
remote: Compressing objects: 100% (333/333), done.
Fetching projects: 7% (28/388) Receiving objects: 33% (149/451), 108.00 KiB remote: Total 451 (delta 141), reused 408 (delta 111)
Receiving objects: 100% (451/451), 376.29 KiB | 187 KiB/s, done.
Resolving deltas: 100% (141/141), completed with 4 local objects.
From git://github.com/CyanogenMod/android_hardware_qcom_audio-caf
11b343e..f36a5e9 cm-10.2 -> github/cm-10.2
Fetching projects: 15% (59/388) remote: Counting objects: 40, done.
remote: Compressing objects: 100% (21/21), done.
remote: Total 30 (delta 17), reused 21 (delta 9)
Unpacking objects: 100% (30/30), done.
From git://github.com/CyanogenMod/android_bootable_recovery
d56d0fd..ab43813 cm-10.2 -> github/cm-10.2
Fetching projects: 19% (74/388) remote: Counting objects: 54, done.
remote: Compressing objects: 100% (21/21), done.
remote: Total 28 (delta 23), reused 9 (delta 5)
Unpacking objects: 100% (28/28), done.
From git://github.com/CyanogenMod/android_packages_apps_Apollo
48d4693..eafb7f6 cm-10.2 -> github/cm-10.2
Fetching projects: 28% (109/388) remote: Counting objects: 94, done.
remote: Compressing objects: 100% (36/36), done.
remote: Total 66 (delta 49), reused 40 (delta 23)
Unpacking objects: 100% (66/66), done.
From git://github.com/CyanogenMod/Superuser
984ec08..5ba79e6 cm-10.2 -> github/cm-10.2
Fetching projects: 32% (125/388) remote: Counting objects: 39, done.
remote: Compressing objects: 100% (5/5), done.
remote: Total 26 (delta 21), reused 26 (delta 21)
Unpacking objects: 100% (26/26), done.acking objects: 96% (25/26)
From git://github.com/CyanogenMod/android_hardware_qcom_display-caf
957cdb4..db2fb0e cm-10.2 -> github/cm-10.2
Fetching projects: 39% (152/388) remote: Counting objects: 7, done.
remote: Compressing objects: 100% (2/2), done.
remote: Total 4 (delta 3), reused 3 (delta 2)
Unpacking objects: 100% (4/4), done.
From git://github.com/CyanogenMod/android_system_extras
485308e..397d03c cm-10.2 -> github/cm-10.2
[Samsung Galaxy Nexus] CommanderROR:
Hey everyone...

Do we have somebody with a fitbit one here who is willing to get serious anout BLE testing?

Best scenario would be:

Find a Nexus 4 with Android 4.3 on it an check if it pairs. Then we'd knowvit works.

If possible try to sync with tje Nexus4 to see if the API works.

Then test the same with the GNex. It does not necceasarily have to be the same person of course... ;)
[Samsung Galaxy Nexus] Carlos_Manuel:
Someone with 2 or more Nexus devices, on JB 4.3 or custom JB 4.3 is needed! ;P

Also recorded logcat from two nexus devices at the same time would be nice... :)
[Samsung Galaxy Nexus] madd0g:
This would be the best way yes. As for an app/service that already supports the Android API, the best bet for now is Runtastic (which was also demoed on the event). So I guess this will need some time for people with hardware to pick it up and test it. Might happen soon if the question now exists in the CM gerrit.
[Samsung Galaxy Nexus] CommanderROR:
[MENTION=4410674]lovejoy777[/MENTION]

You have a Nexus7 and a GNex... Do you have acces to a BLE gadget?

Since the Nexus7 apparently has BLE support working in CM10.2...

[MENTION=218176]Carlos[/MENTION]

Only one of those Nexus devices has tu be running custom 4.3 if the other has native BLE support... ;)
[Samsung Galaxy Nexus] madd0g:
Seems that removing those lines is the proper way to do (like N4 has it) : https://github.com/manuelnaranjo/an...mmit/31756f3c0f364c9c7d07e8813a8b806ec0ddaded

He said he tried it on a test device and it worked on the N7. So my proposition is to use this commit and then wait for someone here to try it out, at least when Fitbit gets around and adds support for the 4.3 API.
[Samsung Galaxy Nexus] Carlos_Manuel:
I've already tried that, it makes no difference... So I keep it the way how I have edited the files. ;P
[Samsung Galaxy Nexus] CommanderROR:
Does the "old" N7 have the same BT Chip? What Kernel does it use?