yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] stocovick:
Well I tried it anyways and it seems ok for now!

One other thing, I noticed that the blue color of the statusbar clock, wifi/phone signal and battery are not the same. Is it possible to fix this?
[Nexus 4 Original Android Development] Imppy:
How do I enable selinux? It says disabled in settings.. I'm using Franco kernel by the way
[Nexus 4 Original Android Development] sparksco:
The kernel your using doesn't support it...
[Nexus 4 Original Android Development] sparksco:
Delete
[Nexus 4 Original Android Development] sparksco:
Alright thread opened! Remain respectful. ROM bashing or other abusive behaviour won't be tolerated! Thanks!
[Nexus 4 Original Android Development] ocovarr112:
Google Airlines welcomes you on the ground in Android International Open Source Airport Project. The local time is exactly 4:30 pm. We will be taxiing for a few minutes to our gate JSS15J while ground support guides us to the public git server.

We hope that you had a pleasant flight and we welcome you to Jelly Bean, or that you have a conflict-free rebase while connecting to your final version.

Your source files will be delivered down the https://android.googlesource.com stairs, in hall jb-mr2-dev, on carousel android-4.3_r2.1. Oversize kernel source files will follow a few minutes later at the counter.

Customs forms are available at https://developers.google.com/android/nexus/drivers and need to be filled before starting a device build, even if this is not your first trip to Jelly Bean.

If you forgot to pack something in your luggage, pre-packed luggage is available at https://developers.google.com/android/nexus/images that contains everything you might need.

Should you have any questions, our agents are standing by at the android-building Google Group. Complaints and suggestions can be filed at http://b.android.com. Volunteers can head to the android-contrib Google Group, and job applicants to http://google.com/jobs

Even if you've visited Jelly Bean before, you will notice that our graphics public transportation is now smoother and more energy-efficient. The city is also safer for everyone, with an entire block dedicated to children. Location Hill was renovated, and the repaving of Bluetooth Avenue continued all the way to BTLE Street and AVRCP 1.3 Park. Our filesystem garbage collection service can now handle active households that generate a lot of trash.

On behalf of all of Google Airlines and of our Android ground crew, captain Conley and cabin chief JBQ wish you a pleasant experience with Android 4.3 and we hope to see you again soon.
[Nexus 4 Original Android Development] DontPushButtons:
How pleasant
[Nexus 4 Original Android Development] machoua:
I want to update soo bad but I think I'll wait until saberMOD updates with 4.3. Nothing to miss in 4.3 anyway..
[Nexus 4 Original Android Development] derekr44:
Yup, plus as far as I know, there is no TMobile audio fix for 4.3 yet... which is a killer for me.

This ROM far outshines. Can't wait to see what sparksco does with the new AOSP code.
[Nexus 4 Original Android Development] strapped365:
I think I'm going to get the full stock experience of 4.3 in a few minutes and then come get mind ****** by SaberMOD! LoL.

I just can't decide if I want to full unroot and start clean or what. I took Linux out so I'm running all Win7 now and I'm not sure how well it works
[Nexus 4 Original Android Development] sparksco:
There's nothing to update to yet...

https://android.googlesource.com/platform/manifest/+refs

Plus I have to wait for other things like a kernel source and binaries. Then I might have to make my own gapps. It's not going to be a quick process trust me. I will send updates out to some testers first.
[Nexus 4 Original Android Development] ctfrommn:
Deep sleep is the issue, it goes into a coma and requires a shot of epi (reboot) to wake up....lol
[Nexus 4 Original Android Development] kptnk:
Yeah, i meant it sleeps very well : flat line ; thing is to see at what point if goes into coma....;)
[Nexus 4 Original Android Development] ctfrommn:
Mine did within an hour.
[Nexus 4 Original Android Development] kptnk:
I set min to 486, for now it holds well.....
[Nexus 4 Original Android Development] mbh87:
are you guys leaving mpdecision enabled?
[Nexus 4 Original Android Development] ctfrommn:
Yes.
[Nexus 4 Original Android Development] sparksco:
Thanks, don't know how much good it'll do lol. We should just keep bumping when we feel the need I guess.
[Nexus 4 Original Android Development] sparksco:
Yeah that doesn't seem right lol.
[Nexus 4 Original Android Development] sparksco:
So the current default min for the kernel is 850mhz right? If that's the case 1ghz min doesn't seem like that much. And I can adjust the defaults accordingly.
[Nexus 4 Original Android Development] ctfrommn:
Default min is 384mhz
[Nexus 4 Original Android Development] sparksco:
Old don't flash
[Nexus 4 Original Android Development] ctfrommn:
Ok, I'll report back with results.

Thanks
[Nexus 4 Original Android Development] sparksco:
Sounds good. A little off topic but my nexus 7 kernel runs at 51mhz and it's UV'd by about -125mv on each clock.

51mhz min 1400mhz max

I get battery all day long :)

I feel kind of bad for you guys having to run the min that high without sod's.
[Nexus 4 Original Android Development] ctfrommn:
I have no issues with other kernels, I can run Faux and Matr1x at sub 200mhz and 150mv UV so this is a unique situation. This kernel absolutely flies in comparison though so I want to help get it right.
[Nexus 4 Original Android Development] sparksco:
Yeah I though using faux kernel as a base but I always had issues on his kernel for my nexus 7. In all fairness though each device various with the kernel. I just chose Harsh because of the stockness of it. I'd like to get this worked out before the last jellybean stable ROM prior to launch of key lime pie in a month or two.
[Nexus 4 Original Android Development] kptnk:
yes but the kernel boots at min freq 1026

still running nicely with min at 486, no issue so far ; i'll keep this one, and will test the non uv one if i have SOD.

As you said sparks, talking about voltages, it is very subjective from a phone to another.
[Nexus 4 Original Android Development] ctfrommn:
This is Harsh based? That would explain a lot. Ive had SOD issues with his last few builds and that is why I quit using it even though it was my favorite.

Actually, IR would be my preferred base if I had my choice, he makes amazing stuff.

---------- Post added at 01:23 PM ---------- Previous post was at 01:22 PM ----------

Thats just mpdecision, the kernel downclocks to 384 by default after a couple seconds of non use.
[Nexus 4 Original Android Development] sparksco:
Well I've been told reverting the UV helps but I can't say for sure. Maybe that s why he hasn't been updating as much as he normally does.
[Nexus 4 Original Android Development] sparksco:
I have more than one branch of the kernel. One is UV and one is not. I'll probably have two versions of the kernel with non-uv stock in the ROMs. And post both in the first post.
[Nexus 4 Original Android Development] ctfrommn:
So far so good at stock voltages :)
[Nexus 4 Original Android Development] sparksco:
I plan on flashing the old factory images then upgrading to the ota once it hits. I want to make sure I get all the firmware updates and Google might not provide all of them in the factory images.
[Nexus 4 Original Android Development] derekr44:
You can revert back to factory 4.2.2 via a toolkit, even in your current recovery/rooted/rom state right? (mskip for example)
[Nexus 4 Original Android Development] sparksco:
You tap it three times. First time device should reboot or might even hard lockup. Unless you format your partitions in recovery before flashing (system,data,cache/dalvik-cache), using a recovery that includes the SELinux kernel. If it locks up, hard reboot. When it boots up it will switch back and forth to enforced and permissive.
[Nexus 4 Original Android Development] sparksco:
I might as well make a CWM recovery image that has STS kernel in it, :sigh:
[Nexus 4 Original Android Development] Yusei:
We can expect any build soon based on 4.3?

Don't get me wrong, I'm not asking for an eta, just curiosity.

I'm loving your rom.
[Nexus 4 Original Android Development] -viper-:
When OTA arrives notify me. :)

Sent from my Nexus⁴
[Nexus 4 Original Android Development] strapped365:
What I will most likely do is just turn the system.IMG and boot.IMG into a flash able and fastbooot the radio and boot loader.

That way its easier for me
[Nexus 4 Original Android Development] alen1901:
[MENTION=2394329]sparksco[/MENTION], all codes are pushed to aosp, now only binaries are missing?

http://i.imgur.com/6OCO9Ja.png

Sent from Sparkling Nexus 4
[Nexus 4 Original Android Development] Martin_Ro:
Paranoidandroid has the blobs allready online, also they have split it into to Repositories ???

https://github.com/ParanoidAndroid/proprietary_vendor_qcom

https://github.com/ParanoidAndroid/proprietary_vendor_lge
[Nexus 4 Original Android Development] sparksco:
I know. I have to finish the manifest first then start merging custom repos...

And also SaberMod has a lot more custom repos than other ROMs.
[Nexus 4 Original Android Development] eep2378:
Tester here :)

Sent from my Nexus 4
[Nexus 4 Original Android Development] strapped365:
You can abuse my Nexus [MENTION=2394329]sparksco[/MENTION].

I also used dsixda kitchen to make me a flash able, but the Mount points were different than what is in your updater, so I used your mount lines and I'll do a test flash of that once I get back home and figure out my mounting to ubuntu 12.10
[Nexus 4 Original Android Development] sparksco:
manifest is done. I need a changelog so I know what to merge.

Edit: think I found it.

http://www.funkyandroid.com/aosp-JDQ39-JWR66V.html
[Nexus 4 Original Android Development] Lownita:
This is really interesting. So you plan to flash 4.2.2. factory image, then ota to 4.3, then custom recovery and root? I thought flashing 4.3 factory image directly would include everything needed.

Tapatalked from my Nexus 4
[Nexus 4 Original Android Development] sparksco:
No. I looked and everything is in the factory images. I plan on flashing when I get home to get everything I need prepared. The main thing right now is gapps.
[Nexus 4 Original Android Development] tuan209:
Damnit Sparksco! Hurry up!

Jk bro! Take your time and thanks for all the hard work. I love your ROM :p
[Nexus 4 Original Android Development] strapped365:
Yeah gapps have changed so damn much or I would start throwing a set together. ( let me know what apps/libs/etc you want from the images and I can start )

I'm home now and gonna let my device charge till about 30% ( enough time to get mowed down ) and flash the radio and BL, then flash the rooted zip I made a bit ago just to feel 4.3.3

**EDIT**

ok so i downloaded Banks core gapps package and opened it up and im using it as reference for building the 4.3.3 gapps package. im currently deodexing the ROM so i can grab the framework and the system apps part of it, and the other parts ive grabbed from the zip made earlier. and i guess once all this is done ill def have enough charge to nand (for once) and flash 4.3.3.

i wont have any way to test the gapps package because ill be flashing bone stock ota rooted, but ill upload them for you [MENTION=2394329]sparksco[/MENTION] to test when SaberMOD makes its 4.3.3 debut.
[Nexus 4 Original Android Development] rustyjay:
On stock 4.3 for like an hour and miss Saber and in call audio for T-Mobile 4g. I told myself would stay on stock for a bit but don't know if I can, lol.
[Nexus 4 Original Android Development] strapped365:
Yeah I've been waiting all day to flash 4.3 to be honest, but I didn't have time till tonight.

I had so much to do on my laptop to even get ready for the update that I'm kinda pissed at myself for taking the Linux partition out.

But 4.3 seems solid I guess, the new camera looks cool, I just don't like the way the clutter is by the shutter button. I seen a couple of different settings or whatever, but nothing to major.

I'm really digging the dialer though (korny I know) but being an HTC user for so long I got used to the way Sense handled its dialer and this 4.3 one just makes more sense...although its ugly as heck.

*will continue to test stock while the devs are hard at work*
[Nexus 4 Original Android Development] ramgear:
You so nice, I can't use stock more than 30 min.
[Nexus 4 Original Android Development] sparksco:
It's a long process... Frameworks has a lot of conflicts and I don't know if they can be resolved or not.
[Nexus 4 Original Android Development] ahepas:
Are you already merging???
[Nexus 4 Original Android Development] -viper-:
Going to flash 4.3 factory now.... Then wait for sparksco...
[Nexus 4 Original Android Development] jyuuken:
Im on the same boat. Reflashed nandroid after half an hour.
[Nexus 4 Original Android Development] anirudh412:
One step ahead of you guys. Didn't even try flashing 4.3. Knew I couldn't do without Saber. My precious!! :silly:
[Nexus 4 Original Android Development] ruzkay:
no need to rush i will flash saber 4.3 when done and dev can take all time he wants :) he is doing this for free :D

hope in 4.3 random reboot i rarely get is gone
[Nexus 4 Original Android Development] -viper-:
On 4.3 now for an hour and i already miss sabermod....

Sent from my Nexus⁴
[Nexus 4 Original Android Development] Demonseye:
This, exactly :)

No need to rush on 4.3 without SaberMod :D
[Nexus 4 Original Android Development] sspyed:
Will there be another nightly before Saber moves up to 4.3?

EDIT: I'm asking because every time I flash 7/23 via CWM I get an error saying "Warning: no file_contexts"
[Nexus 4 Original Android Development] derekr44:
Those of you on 4.3 and experiencing the in-call audio issue for TMobile, there is a hybrid radio out there (.84/.33) that appears to have the issue fixed.

http://www.mediafire.com/download/w04m08571nrt4fi/LTEhybrid33-84.zip
[Nexus 4 Original Android Development] nycelitemaster:
i just use the kernel from Sparksco. Hopefully he can shed some light stating that it is compatible with 4.3.
[Nexus 4 Original Android Development] Logi_Ca1:
For some reason, updating to the 0723 nightly results in me losing all connection, either 3/3.5G or Wifi. I dug around and found that my baseband was stated as "Unknown". I did a search and strangely I'm the only one with this issue... I updated from RC4 I believe, and I'm running Trinity TF150 and the 0.54 radio. Any ideas on how to fix this issue?
[Nexus 4 Original Android Development] sellers86:
That happened to me once, I just reflashed my radio with the CWM zip and all was fine.
[Nexus 4 Original Android Development] Logi_Ca1:
I did that with same result. I'm going to try the new .84 radio that was released with 4.3 Thanks for the reply!
[Nexus 4 Original Android Development] jtwlbz:
84 radio feels really good
[Nexus 4 Original Android Development] derekr44:
Sparksco spoiled me. I went back to sabermod after about 30 mins. I can wait for a 4.3 saber.
[Nexus 4 Original Android Development] rustyjay:
Now that I got 4g back, stock is bearable. My battery would drain fast on H/H+ for some reason. Been reading the kernel changes in 4.3 are ridiculous, glad I can just sit back and wait. Smoking one right now for ya Sparksco, sending the good vibes.
[Nexus 4 Original Android Development] sparksco:
You guys can check out the progress on github sm-jb-mr2 branches. frameworks/base and settings needs rebased for sure and maybe some other things. They also changed the way the gcc works. I think I finally got the gcc 4.9.0 toolchain implemented correctly.
[Nexus 4 Original Android Development] strapped365:
Last I seen git was very very late last night. It looked like it had been a few hours since your last "push" or whatever so I figured everything was synced and you were going through with a hammer mashing out all the conflicts.

I've never built before now so the whole process of a ROM source getting an update is just foreign to me and thus I wait.
[Nexus 4 Original Android Development] sparksco:
Yup I resolved as many conflicts as possible but some things like frameworks, settings and a few other things looked like a lot of work. I'm still trying to decide if I should just revert the commits that cause conflicts for now and try to reinpliment later on or just start over from scratch which might be even harder to do... It looks like cm privacy guard might get left our for awhile.

I thought this was going to be a minor update but it's not Lol

Cc: [MENTION=4429892]Martin_Ro[/MENTION] [MENTION=4617326]jarjar124[/MENTION] [MENTION=3124065]rascarlo[/MENTION]
[Nexus 4 Original Android Development] DontPushButtons:
Privacy guard might need to be rebuilt anyway looking at the stock permissions manager: http://t.co/6rmIkxSsss
[Nexus 4 Original Android Development] strapped365:
I'd lose CM privacy guard for a 4.3.3 SaberMOD :) any day.

I also got the gapps done their on dev-host for whenever your ready.

I'm also setup to build again from Ubuntu 13.04 I just have to repo sync...( I wonder if I could call home and have someone start the sync ( cause there is no repo yet....just a blank install )
[Nexus 4 Original Android Development] sparksco:
Cool thanks! Did you manually download the latest smali and baksmali from jesusfreke? I always deodex the apps manually with the api level set and all that.

Same here. I don't think I'll start over on the repos. Most likely I'll revert some things for now just to get the development going :)
[Nexus 4 Original Android Development] strapped365:
No I don't have anything individual setup or anything, I used the dsixda kitchen and the api of 17 I think...or 19 to deodex the whole ROM. I'll have to look when I get to my laptop.

If I need to do it manually, it wasn't but like 7 apks and that can be done in like 2 hours when I make it to the station
[Nexus 4 Original Android Development] Martin_Ro:
Yeah, I allready decided to start from scratch with plain 4.3 and then implement what I like. Also I would love to do that with 4.9 tool chain but I fear that's a little bit over my head....

Gesendet von meinem Nexus 4 mit Tapatalk 4 Beta
[Nexus 4 Original Android Development] sparksco:
If your starting over just cherry pick commits from build repo since I did that repo fresh. You just need to add a variable in vendor somewhere. I put it in common.mk

https://github.com/SaberMod/android_vendor_sm/commit/827b67c69b13daeeb046e43f1d8dea22311a6de7

Also oprofile

https://github.com/SaberMod/android...mmit/6c6a91fe1b23a5e99a6ca734ea0600b42f7514f0

For the other repos like frameworks/base and settings I'm not starting over though. Too much work for me. I reverted the things that are causing major conflicts and the rest of the conflicts look minor even though there's a lot of them. I think I've managed to keep most of the features. I won't know more til later when I get home to start of resolving the conflicts though.
[Nexus 4 Original Android Development] Yusei:
Take your time pal

We can wait :)
[Nexus 4 Original Android Development] machoua:
Anyone else notice that when breathing sms and missed call is on, any downloaded app from the Google play also breathes? It's cool haha
[Nexus 4 Original Android Development] Martin_Ro:
Wow, thank you very much !

So if I get you right, I can fetch the aosp 4.3 repros from Google source + the 4.9 tool chain from your repo, pick this two commits and that's it? A vanilla 4.3 with 4.9 GCC as a start point sounds like fun :)

Will try that for sure :)

Gesendet von meinem Nexus 4 mit Tapatalk 4 Beta
[Nexus 4 Original Android Development] ..Cory..:
Omg, a vanilla 4.3 with 4.9 GCC would be amazing....
[Nexus 4 Original Android Development] edwardeutsch:
+1 would be a clean and good start point..
[Nexus 4 Original Android Development] benrees21:
Got a problem! Out of the blue I keep getting a System UI Force Close constantly popping up! The Navbar and Status Bar have disappeared so it's hard to find out what's going on especially with the constant pop up! I have cleared cache/dalvik cache and fixed permissions and still no luck fixing it. Weird thing is that I've been running the ROM fine for weeks, so what has happened? So strange.
[Nexus 4 Original Android Development] yankeeornovember:
I mean, I'll be the first of many to suggest this, but maybe it was something on the user side, not something inherently wrong with the ROM.
[Nexus 4 Original Android Development] sparksco:
Turn off selinux?
[Nexus 4 Original Android Development] sparksco:
Guys like I said I'm not starting over from scratch... Too much work :silly:

I might have to start over from scratch on a couple repositories like frameworks/base and settings. But the whole ROM source? Nah. Sorry but it won't be vanilla. SaberMod was never vanilla and probably never will be...
[Nexus 4 Original Android Development] benrees21:
How? Phone was fine, was left alone for about an hour and then went to unlock it and it started with the constant pop up System UI FC. I have wiped system, cache/dalvik cache and re-installed the ROM again and it is still happening! I'm beginning to think it's a new app update that has caused it as my apps are on auto update. It's a case of what one though? So strange for it to happen out of the blue and the only thing I can think of what might have changed while the phone was locked was an app update. Will probably just wipe completely later if I can't get it to work.

---------- Post added at 06:35 PM ---------- Previous post was at 06:32 PM ----------

I was not outright blaming the ROM, like I said, The ROM has been fine and I was using my phone an hour before it all went wrong! My phone sat there doing nothing for an hour and then I unlock it to a constant pop up of System UI FC. It could only be from an auto updated app, but which one? And why would an app bug out the System UI?
[Nexus 4 Original Android Development] DontPushButtons:
I would consider a fresh flash like you're already talking about. Unless you want to try and sort through your apps to determine the culprit..

When I tried 4.3 I was getting constant "this app has crashed, but a log has been sent to the developer". Nobody else seemed to have the problem, so it had to be something unique to me. Turns out it was Sophos security. Kept trying to run itself as a background process.. So, check any apps that run constantly in the background if you can manage. Otherwise just wipe it all and start over.

Sometimes I find restoring back to full stock and starting over clears up all sorts of finicky issues.
[Nexus 4 Original Android Development] sparksco:
FYI I'm around 75% done with the second pass on frameworks/base. Some of these files can takes hours while others can take a few seconds :screwy:

But I haven't given up yet :thumbup:
[Nexus 4 Original Android Development] benrees21:
Cool, keep going mate! I am just going to wait it out for your 4.3 update and then do a complete wipe and flash it. I'm not in the mood to do a full wipe now and then another for the 4.3 update, might as well just wait it out. :good:

Thanks for this ROM, it's amazing!
[Nexus 4 Original Android Development] -viper-:
Ok sparksco, morphin time! Go Go SaberRanger

Sent from my Nexus⁴
[Nexus 4 Original Android Development] kptnk:
You're not alone, we're with you mate ! :highfive:
[Nexus 4 Original Android Development] sparksco:
Thanks guys. Sorry my time is limited, and there's no eta. I want to make sure everything is done right.
[Nexus 4 Original Android Development] eep2378:
No worries bro. We know this stuff isn't easy and you want it done the right way. When its done its done. No rush :)

Sent from the Nodes of Ranvier
[Nexus 4 Original Android Development] jyuuken:
We can wait! We appreciate d hard work!
[Nexus 4 Original Android Development] jtwlbz:
No pressure. I'm still very happy with the latest nightly.
[Nexus 4 Original Android Development] nycelitemaster:
Take your time brotha.. I love your kernel.

Sent via Google N4
[Nexus 4 Original Android Development] reicute789:
does the latest download link contain the new kernel? im going back 4.2.2 until saber has 4.3. stock just isnt enough. :D