yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] sparksco:
Re: [ROM][JDQ39][AOSP][LINARO] 4.2.2 SaberMod - RC2

Thanks bro. I was having some audio issues and I thought maybe it was related to the new quite hours but it was some other stability issues in the ROM. New build will be up soon with some bug fixes and new features! Volume rocker wake is in even though it doesn't work on the nexus 7. Hope it works on the nexus 4 though.
[Nexus 4 Original Android Development] jarjar124:
Re: [ROM][JDQ39][AOSP][LINARO] 4.2.2 SaberMod - RC2

I have a feeling it will be like rasbean. It will work but it will conflict with volume skip.
[Nexus 4 Original Android Development] sparksco:
Re: [ROM][JDQ39][AOSP][LINARO] 4.2.2 SaberMod - RC2

How will it be like rasbean? I don't use the same implementation he does.. Maybe your right maybe I should remove it?
[Nexus 4 Original Android Development] johnson8cyl:
Re: [ROM][JDQ39][AOSP][LINARO] 4.2.2 SaberMod - RC2

Anyone else having system settings/security crash?
[Nexus 4 Original Android Development] jarjar124:
Re: [ROM][JDQ39][AOSP][LINARO] 4.2.2 SaberMod - RC2

I believe it was in general.
[Nexus 4 Original Android Development] sparksco:
Re: [ROM][JDQ39][AOSP][LINARO] 4.2.2 SaberMod - RC2

Oh OK. Is it like that on cm Roms too? Just wondering how general it is. It might just be a buggy feature.
[Nexus 4 Original Android Development] gabx:
Am I the only fool in town with a fancy device?

settings ---> security =====> Settings force close.

Thank you.
[Nexus 4 Original Android Development] johnson8cyl:
Re: [ROM][JDQ39][AOSP][LINARO] 4.2.2 SaberMod - RC2

Just mentioned that a few posts back. Log cat isn't telling me anything either. Also getting a toast to enable location services in Google maps when they are already enabled. Won't get my location
[Nexus 4 Original Android Development] jarjar124:
Re: [ROM][JDQ39][AOSP][LINARO] 4.2.2 SaberMod - RC2

It was. I'm not sure if it is still the case. Rascarlo fixed it but I forgot what he did. Need to check his git.
[Nexus 4 Original Android Development] gabx:
Ok. No issues here with maps, only the mentioned one with security settings.
[Nexus 4 Original Android Development] sparksco:
Re: [ROM][JDQ39][AOSP][LINARO] 4.2.2 SaberMod - RC2

Now I'm just confused. First you said it might be buggy with music control feature now you say it's fixed? He hasn't implemented anything new for volume rocker last I looked at his github. I've already discussed this with him in the past and we've already tried a bunch of different things and it still doesn't work the way it should.
[Nexus 4 Original Android Development] sparksco:
Re: [ROM][JDQ39][AOSP][LINARO] 4.2.2 SaberMod - RC2

With security settings might have just been a bad build. It doesn't make sense that it works fine on my nexus 7 but not on the nexus 4. Mostly since the app is a system app and should be compatible with all devices. About location I had the same thing. You have to enable it in the Google now app not in settings.
[Nexus 4 Original Android Development] johnson8cyl:
Re: [ROM][JDQ39][AOSP][LINARO] 4.2.2 SaberMod - RC2

Yeah. I don't know about the security deal. I'll try to catch a better log cat on the PC layer tonight when I get home and give it to you. Thanks bro
[Nexus 4 Original Android Development] sparksco:
Re: [ROM][JDQ39][AOSP][LINARO] 4.2.2 SaberMod - RC2

Thanks. A good full log would be really helpful.
[Nexus 4 Original Android Development] alen1901:
I know, but not everyone has time to search through forum, also there are noobs and people who doesnt develop etc, so they dont understand everything. I myself spent 45min searching for reason qs wasnt implemented and there is no real answer there, at least i didnt find it. Also it would be great to post in OP that qs customisation will never be there, that would reduce questions about it. That is the feature that every rom has, thats why people think its included even if its not there in changelogs. This thread is one of rare ones that are really development related, and directs people to try and develop on their owm, which is really great, more threads like that are needed. But, you guys dont have to be that negative and unfriendly to anyone who asks question which was answered allready, you answer to them in superior and rude way, ditch them. Dunno why is problem to answer normally and direct them to another rom in pleasent way.
[Nexus 4 Original Android Development] sparksco:
Whoa thanks for the beers! :)
[Nexus 4 Original Android Development] sandy-achar:
The tone of asking the question is also important. If someone politely just asks if it will be implemented, of course people are going to give a straight forward answer. Rather if a person demands why a feature hasent been added and bashes the rom for it, he is in for a bad time.
[Nexus 4 Original Android Development] alen1901:
Understand that, but not all people talks/asks the same, and with writing something can be interpreted in a wrong way (accents, the way of question etc). For some people is normal to ask demandly, its in their nature and they acts the same in real life. Now ill stop because its way offtopic. Cheers.

Sent from Sparkling Nexus 4
[Nexus 4 Original Android Development] sparksco:
The QS has been discussed. [MENTION=4617326]jarjar124[/MENTION] and I wouldn't mind adding it but there's a lot of dependencies in cm's github for that. Its not a single change to cherry-pick and port over as easily like the halo from paranoid android was. Also we're both in school, so our time is limited. If we can do it and we think we can port it over without bugs, or we're confident that we can fix future bugs with a feature then we'll add it. Also keep in mind that each feature is a mini project in itself that has to be maintained. Like halo. Future updates, bug fixes ect. That's why I tell people to read the FAQ and OP, which should always be done before flashing any ROM.
[Nexus 4 Original Android Development] Martin_Ro:
Sorry, but that sounds like common "what goes around, comes around" or like we say in german "wie man in den Wald hineinruft, so schalt es wieder hinaus".

If somebody only asks, it's ok, but if he insists that the lack of a feature would make the rom worthless " Then what's the whole point of having them" is quiet an other thing. And yes, then the "fanboys" of the rom sometime can get a little bit rude :cowboy: ;)

But you don't go bleeding into a room full of lions either, did you ? ;)
[Nexus 4 Original Android Development] johnson8cyl:
Anyone care to share their settings in system tuner? Cpu and voltage
[Nexus 4 Original Android Development] torana355:
I'm new to android but I always read the op and the last 10 pages of a thread before asking questions. Why is this so hard to do for some people lol. Anyway love your work Sparksco and jarjar124. Just got 2 days and 12 hours standby on your awesome rom. :)
[Nexus 4 Original Android Development] Demonseye:
You're welcome ;)
[Nexus 4 Original Android Development] MagicalSword:
Q about HALO

I recall from my maguro that you could move the HALO thing around, so you could make it "disappear" anywhere in the perimeter of the screen, but with SM implementation I don't seem to be able to move it around (and it stays just in the place where you press for emoticons in Whatsapp when writing, lol). Is this somethign I am missing (in the configuration of in manual operation), due to what has been ported and how, or should we consider it a bug?

Also, informatively, I have had my first unexpected reboot, UV -50 with my 4.7.4 build... I have returned to stock volting, just in case that toolchain doesn't support -O3 optimizations and UV at the same time (I have a fast binned chip). Under your builds UV -50 has never given problems, so another benefit of the more modern toolchains... :)

Thanks for your help!
[Nexus 4 Original Android Development] sparksco:
Yup same here with the fast binding chip. I always get reboots if I go lower than the stock. I'm probably going to add back the frequencies that were removed so that might help with battery and UV. It's been on my todo list.

About HALO, it could be a bug, not sure if with this ROM's implementation of it, or with pa's bug fixes. I remember in my early stages of testing it did move around, so not sure what happened there.
[Nexus 4 Original Android Development] sandy-achar:
U must have used halo a long time back. Now halo has new gesture controls, to move the halo around double tap, hold and move. Also swiping up cancels the notification, swiping down puts the halo further inside the screen.

---------- Post added at 02:27 PM ---------- Previous post was at 02:25 PM ----------

Halo is working fine. Btw that's a great job of merging halo, it's working brilliantly without hiccups.
[Nexus 4 Original Android Development] eep2378:
I completely understand your point. I only responded that way because particular user in question (refers to "corn") had already posted about his own "issue" yesterday. There are a bunch of great people in this thread who help each other a lot. Then there was the tone of his question.

Sent from the Nodes of Ranvier
[Nexus 4 Original Android Development] MagicalSword:
Ah, yes, you are right... it was from the early 3.5 PA builds for maguro, it works nicely as you said, thanks a bunch!
[Nexus 4 Original Android Development] sparksco:
Kernel update BUG FIXES

Important kernel update with bug fixes in it.

https://sourceforge.net/p/stskernelmako/blog/

https://sourceforge.net/projects/stskernelmako/files/?
[Nexus 4 Original Android Development] ilamaan:
Halo's included now on this ROM? Is the exploit not a concern now? I would like to know before I give the ROM a try.

Thanks.
[Nexus 4 Original Android Development] Audioboxer:
Thanks!
[Nexus 4 Original Android Development] Demonseye:
Thanks for making this ROM, Nova launcher has never been this smooth before (even while scrolling through widgets!)

Gonna install the newest kernel right away.
[Nexus 4 Original Android Development] sparksco:
System tuner has been acting weird for me. I might change the OP to use trickstermod instead. I'm testing -50 more than stock right now on the new kernel. Here's my settings.
[Nexus 4 Original Android Development] eep2378:
Halo is included in [MENTION=4617326]jarjar124[/MENTION] build yesterday. At this point the exploit is not a major concern anymore.

Sent from the Nodes of Ranvier
[Nexus 4 Original Android Development] strapped365:
It's also in the build I did. But battery is acting very wonky this morning so I have to see what's causing that

Sent from my Nexus⁴
[Nexus 4 Original Android Development] ilamaan:
Can you tell me the reason why its not a concern anymore? I mean does the exploit work or not now? I want to be sure because its a security risk. Sorry to trouble.

Thank you.
[Nexus 4 Original Android Development] sparksco:
Could be HALO if you have it enabled. Is android system usage high?
[Nexus 4 Original Android Development] strapped365:
Yeah it and the OS was top battery hogs, then I flashed the new kernel and now my display is showing up top...so who knows.

Sent from my Nexus⁴
[Nexus 4 Original Android Development] sandy-achar:
Of course it's security risk. There is a master switch included by which u can disable halo completely. But, hey u got to take your chances if you want to be part of bleeding edge. Also download the build I made a couple of pages back, it has halo install button disable fix, sparksco will be adding the fix to his source soon though.
[Nexus 4 Original Android Development] Mantulis:
Interesting...

So i'm the only one who use this rom and kernel with faster blinded chip here?.

Or and here is my voltage table:
[Nexus 4 Original Android Development] sandy-achar:
No battery usage has been usual. I have been running with halo for the whole day and my OS battery usage is at 8%. But I use Franco kernel with updated prima drivers. So the battery drain could be because of kernel changes. Also would u consider updating the prima drivers in the kernel to fix wifi connection problems. Thanks.
[Nexus 4 Original Android Development] sparksco:
I'm hoping PA team can fix this high battery usage. It is a pretty huge process that runs inside of android system so idk what/if they can do about it.
[Nexus 4 Original Android Development] sparksco:
Well you can always fork the kernel and send pull request. The prima drivers were updated in harsh's changes early on in the kernel development stage...
[Nexus 4 Original Android Development] ilamaan:
Oh. So btw, the exploit works from pages opened on the browsers? Or is there any other way too?
[Nexus 4 Original Android Development] sparksco:
You can also blacklist apps such as browser.

Better yet you could switch to whitelist which means you have to explicitly allow HALO to apps of your choice for notifications. Meaning HALO won't have access unless you allow it.
[Nexus 4 Original Android Development] strapped365:
Yeah with the security threat it carries, having to disable another android security layer and battery drain I may ditch halo all together. Its just not worth it IMHO

Sent from my Nexus⁴
[Nexus 4 Original Android Development] ilamaan:
Oh thanks. I know about the blacklist. Just Dev can you tell me how this exactly works? The exploit? Because I want to be careful to not run over one.
[Nexus 4 Original Android Development] sparksco:
Well if you switch to whitelist in the halo settings then it won't have access to anything unless you go into app settings and allow halo notifications for certain apps ;)
[Nexus 4 Original Android Development] sandy-achar:
I have not advanced enough to do this nor do I know how to go about it. Also I am in the middle of my exams. Lol :P just thought I would try my luck and ask you. Also I think the battery drain is cause of the kernel changes, since I m using another kernel, battery usage seems normal to me.
[Nexus 4 Original Android Development] sparksco:
IDK I'm not the one who discovered any exploits or claimed there was any...
[Nexus 4 Original Android Development] sparksco:
No. The new kernel just came out an my android usage has been at 13% all day. Even before I flashed the kernel.
[Nexus 4 Original Android Development] rest0ck:
Either my Phone is "broken" or there's something wrong with this ROM.

Sometimes when I unlock my phone (just had it 2 times in a row while outside) the Touchscreen won't respond anymore and I have to reboot. I don't know what could cause that but it is really annyoing :/

I'm not using Touch Control btw

Thanks in advance

rest0ck
[Nexus 4 Original Android Development] sandy-achar:
Here is my battery usage.
[Nexus 4 Original Android Development] strapped365:
That's to much. Its the overlay setting being disabled that I dont like to. Because now not only could halo request and grant SU behind itself ...you can now install apps while an overlay is present. Which is something Google didnt want.

For a while the PA guys seemed as if they had Googles best interest along with users, but now it seems their just trying to market themselves. And fill other ROMs with it. I'm going to laugh if/when this becomes another corner stone.

Sent from my Nexus⁴
[Nexus 4 Original Android Development] sparksco:
Yeah but Google didn't do anything about it with samsung. Also I think this is similar to cornerstone but not so much in a lot of ways. They explain that on the commit change so its been documented. I don't think we should allow app installing when halo is enabled until a better fix is found.
[Nexus 4 Original Android Development] strapped365:
Just because they didnt stop a phone manufacturer, don't meant they won't stop a tiny group of devs. But that's my opinion.

I just hope that Halo isn't included in every ROM here, so I'll have something to use lol

Sent from my Nexus⁴
[Nexus 4 Original Android Development] Sukhi:
Anytime
[Nexus 4 Original Android Development] sandy-achar:
Yes its is a security risk as of now, i am sure someone figure out a fix for it soon. And isnt android being a part of open source so that we get to do what we want with it as long as we understand the consequences of our deviation from the stock android. Also i think we can mange the security risk by blacklisting stuff we dont need to be notified about by halo and by using trusted apps from playstore and not use some hacked/cracked app. Also halo has been incredibly useful so far, for example to reply to texts while watching a youtube video, this would have been impossible otherwise.
[Nexus 4 Original Android Development] sparksco:
Well I just heard back about the package installer hack (which I don't plan on including in my builds).

"Well, it's unlikely someone would target this "security hole" imo, as it's just enabled at android by default and only a tiny percentage of the users who use the custom halo roms is affected. And those custom roms can way easier be targeted by some apps which ask for root access I think, as those are usually granted by lots of people without a second thought.

Still.. this shouldn't stay this way!

A better workaround for now might really be to disable the halo overlay while installing an app (with a toast message telling the users).

Then after pressing on "Install" (or Cancel) the halo overlay gets re-enabled again.

This wouldn't be hard to implement. Hacking into the framework to exclude halo (see my last comment) would be the best alternative I think, but that's a lot more complex.

At my current build I didn't cherry-pick this commit, so people who are installing an apk need to drag the halo button onto the X to close it prior to installing, then re-open it via the notification drawer."
[Nexus 4 Original Android Development] sandy-achar:
Is that the reason you havent committed it yet ?

Edit : LOL never mind you just answered it. :P
[Nexus 4 Original Android Development] strapped365:
Yeah i built whatever you asked...

The user shouldn't have to compensate for no one caring about a security breach only to promote halo.

For some halo could be what they have always needed. Or at least seem that way on the surface. But does YouTube play while replying to your message? Last I checked it paused so what's wrong with going to the notification from the shade, then using multitasking as Google intended? Halo is new, its shiny....reminds me of a infomercial. Great on the surface, but underneath its nothing more than recycled ideas and code.

Sent from my Nexus⁴
[Nexus 4 Original Android Development] sandy-achar:
Absolutely the users shouldn't compensate security for it. And most of the users of the rom are aware or it is their job to be aware of what they are getting into when they decide to flash a rom or update it. Security risk is introduced as soon as a person decides to unlock his/her boot loader and install a custom recovery. Closed source roms such as MIUI is also a potential security risk, that does not stop people from flashing and using it. It ultimately boils down to the preference of the dev making the rom, cause uploading on xda is sharing with community, but most importantly it is building for oneself.

And yes the youtube video keeps playing in the background and does not get paused. So i am happy i am watching a video and my girlfriend is happy i am replying to her texts. lol :D :silly:
[Nexus 4 Original Android Development] strapped365:
That is super nice about YouTube... glad they changed coding because before it seemed more like how iOS pauses tasks.

And yeah there are always dangers when installing something custom so I understand all the points you've made. And agree it's up to the user to stay as safe as possible, but having to go three extra mile to stay safe is scary

Sent from my Nexus⁴
[Nexus 4 Original Android Development] sparksco:
In all honesty I have to agree with PA that there's lots of other more security risk than HALO. Having unlocked bootloader is a risk. You can re-lock it on a custom ROM but you'll be stuck on it until you unlock it again. Having root is a risk, but from what I've seen, embedding superuser into the system and koush adding security bug fixes to his code makes superuser more secure than it ever had been before. Having "unknown sources" and "adb debugging" always checked are both security risk (both things that can be done on stock android). So to me HALO being a [/B]major[/B] security risk kind of makes me LOL. The risk are very minimal, and anytime a dev comes out and says RED FLAG SECURITY RISK, people flip out like it's the end of the world.
[Nexus 4 Original Android Development] sandy-achar:
Yes I m blacklisting all the unneeded apps too. Lol. PA comes up with real nice innovations, never really appreciated hybrid engine and pie due to its lack of functionality for me, but halo has been an amazing experience so far.
[Nexus 4 Original Android Development] Austin Ag06:
Something similar happened to me as well, but I'm using rassaber with sts kernel. I was able to unlock my phone, but the screen was non responsive. I was able to turn the screen off and back on again a couple times and the problem went away though. Hth
[Nexus 4 Original Android Development] sparksco:
And this happened on the kernel that was just released today with the bug fixes or a older kernel version?
[Nexus 4 Original Android Development] Demonseye:
[MENTION=2394329]sparksco[/MENTION], flashed the new kernel and suddenly Google Now always FCs. :/ Can these be related?
[Nexus 4 Original Android Development] sparksco:
Nope. I'm on the kernel right now and Google now working fine.
[Nexus 4 Original Android Development] sparksco:
No, if you read my post I clearly said I have a faster bin chip...

Edit: just realized I posted "fast" instead of "faster".
[Nexus 4 Original Android Development] Austin Ag06:
Sorry, should have said that I haven't updated the kernel yet... I'm still on the 6/12 build
[Nexus 4 Original Android Development] sandy-achar:
okay, my network started to act all weird all of a sudden that made me look into the bands. I have flashed the latest .54 radio that doesnt have LTE, but in the service menu info , it shows option for LTE ? Any clue ?
[Nexus 4 Original Android Development] alen1901:
If i remember correctly, two latest radios doesnt support lte, google removed it.

Sent from Sparkling Nexus 4
[Nexus 4 Original Android Development] sparksco:
Must be the radio or the area your in cause I'm on .48 radio and I don't have those options when selecting band.
[Nexus 4 Original Android Development] sparksco:
Oops never mind. The options are there. The ROM just has all the generic options as far as I know. It doesn't know what your radio supports or doesn't support...

Probably the area your in.
[Nexus 4 Original Android Development] Demonseye:
Well, I don't know ... maybe reflashing the ROM with wiping Cache and Dalvik? Restoring a backup of Google Now doesn't do anything, and I can't reinstall it from the Play store.

When I click on the bar, it just shows the white screen, and then back to desktop.

I also tried reflashing the Gapps package, it didn't help.

Is the "normal-sized" package compatible with your ROM?
[Nexus 4 Original Android Development] sparksco:
[MENTION=3614363]sandy-achar[/MENTION] I just switched to GSM auto (PRL)

My signal seems a little better now than before.
[Nexus 4 Original Android Development] sandy-achar:
Yes i think the area matters. Also in the band selection, why are there only that 4 options ? shouldn't there be a lot more options ? I remember seeing so many band selection choices in the commit to fix network band selection fix.

---------- Post added at 06:49 PM ---------- Previous post was at 06:43 PM ----------

GSM only signals are indeed better :good:

My network is acting up, when i am on HSPA+ and connect to a wifi network it randomly connects and disconnects from mobile network over and over, if i disable data that doesnt happen. If this happens again i ll try to take a video of it. I have a strong feeling its something to do with network band selection, but when i dont connect to wifi that doesnt happen, so i am really confused :rolleyes:
[Nexus 4 Original Android Development] sparksco:
There's none missing for me besides Japan and a couple others probably because of the area I'm in. But like I said I switched to GSM auto (PRL)