yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] Ansanen:
Anyone can help

I want. To fix lte on l preview for nexus 7 2013 LTE

Nexus 7 2013 LTE
[Nexus 4 Android Development] bitstra:
... name it thankful - not generous!

I want to give it away for all ports - ATM I'm checking the OS-fingerprint for device-sig (i.e. Flo, Mako) + String "LPV" in fingerprint...

That works in the test on my two devices - but right now I'm searching for a universal Fingerprint Method...

How about, you put an unique string into every Port's OS-fingerprint (like i.e. 'by-L-Porting-Team', this is what I see on github subtitle, or so)?
[Nexus 4 Android Development] ramjet73:
I don't think the 2013 LTE version (deb) is fully supported by the official preview or the ports to date. You may have to wait for the release of L to get the cellular features fully operational.

ramjet73
[Nexus 4 Android Development] bitstra:
The second story for bubble launcher on L-ports will be his full power for multitasking, if I could find a way to hack a multiwindow port into the AOSP stuff.

The bubble launcher was born, when paranoid-team started with HALO-floating window mode and xMultiwindow for Xposed were born...

The last 3 days I trieded to prepare a port of (OmniROM's)-Multiwindow integration - but till now now luck with my concept :(
[Nexus 4 Android Development] sykopompos:
Its gonna be done tonight. I already got my boot image together and build.prop made, just need to see what I need to add for it tonight.

I already had it booting but that was back on the old series so I just need to see exactly what is needed for it

Sent from my LG-D851
[Nexus 4 Android Development] ramjet73:
Does that include LTE? I thought LTE would require radio update(s) and possibly other binaries that Google hasn't provided for L yet. Are the KitKat versions working for L?

ramjet73
[Nexus 4 Android Development] sykopompos:
I will have to see what I can add without breaking something. The fingerprint probably won't work because there are other things that look at that string and we could possibly break something in the process.

Maybe just look for L and device name? If we go on lpv81c it will break as soon as we get official L then. Maybe a key that can be posted in the op for the device?

Sent from my LG-D851
[Nexus 4 Android Development] bitstra:
- but in sykopompos Flo_Test6 I saw the full stuff for telephony - don't work the HW-binaries of Mako for telephony for deb :confused:
[Nexus 4 Android Development] sykopompos:
We have deb preview binaries, I just gotta track down what is specifically needed for the LTE stuff. The lines in the init just turn off the gsm radio so the differences are minor in the inits and the fstab needs the radio partition.

Besides that I think it might be a system apk or 2 needed to work

Sent from my LG-D851
[Nexus 4 Android Development] sykopompos:
That's because we were porting a port, this time it is the straight up preview image base of flo that I will port over. The other stuff from my initial tests for deb are good though

Sent from my LG-D851
[Nexus 4 Android Development] bitstra:
That's it - search for deviceName + search for "/" after deviceName + search for "L" after this "/"

Will have a look into...

thanx

Edit: Seems, that I can define a universal pattern:) for String-search...
[Nexus 4 Android Development] sykopompos:
But will it break when official L comes out?

Sent from my LG-D851
[Nexus 4 Android Development] ibanez89:
Thanks man, probably my flash have some problems I try to reflash all :)
[Nexus 4 Android Development] Hikari:
About the issues, I had created a google code page and added syko and Ben as owners. I thought it would be best for its purpose as anyone would be able to post but only a select group of people would be able to make changes. I think using google code would make more sense than docs but whatever decision is made it's alright.

Issues page: https://code.google.com/p/l-developer-preview-n4/issues/list
[Nexus 4 Android Development] WoodroweBones:
I have had this on and off through various ROMs. I think its a Chrome issue. Actually now that I think of it I usually have it happen in Chrome Beta but normal Chrome usually plays it ok... cant think of any examples offhand right now but next time I run into it I'll post. I dont think its related to L
[Nexus 4 Android Development] DRS2442:
I know custom kernels work. I guess in a way I contradicted myself, but I just thought that there was more behind volta that couldn't be ported
[Nexus 4 Android Development] kingracer:
Used 1 beta, then updated to the second and having the same issue - after unlocking the device systemui reloads and lockscreen appears again and it's cycle...
[Nexus 4 Android Development] sykopompos:
That was the rest of the team's idea so we can get some versioning control in and they are still working on a lot right now so it is incomplete. there are more bug fixes in what is up there already though but more is being worked on along with tools to help other developers port a port of a developer preview to other devices. We already pointed the htc one m7 team working on it in the general direction in the mean time and they already got boot.

as far as beta 3, more and more and more fixes being worked on. We try to get as many bugs fixed between each release and not just a whole new version for one or 2 fixes unless they are major bugs

sorry, double posted it
[Nexus 4 Android Development] txuki2005:
then can you check this bug?... quote my last messge..

"I noticed if you use app to see battery capacity, you can see 2300 mah (nexus 5) not 2100 mah (nexus 4) so battery stats may be wrong "
[Nexus 4 Android Development] oxxshadow:
titanium backup works fine, but it cannot uninstall apps or reload app data. Koush;s Superuser does not play nice with this app that is all.
[Nexus 4 Android Development] ramjet73:
Since beta 2 comes rooted you can use QuickBoot from the Play Store. That's working for me.

ramjet73
[Nexus 4 Android Development] Tak3r07:
Try ondemand gpu governor of it was not already set
[Nexus 4 Android Development] icu64:
Does anyone know if normal Franco kernel works?
[Nexus 4 Android Development] v3n3:
Do a barell roll... no wait, full wipe, thats what I meant to say.

Full wipe = system, Dalvik/cache and data (not internal storage) and flash Beta 2
[Nexus 4 Android Development] Targaeryan:
I uninstalled an app just now with no problems..
[Nexus 4 Android Development] Connor Baker:
I don't believe so unless he made the switch to anykernel format recently. Flashing the whole boot.img would overwrite the hacked ramdisk required for this port to boot.

- Connor Baker
[Nexus 4 Android Development] kad3t:
Thanks a lot guys! As some of you suggested the issue was with the old Recovery version. After updating it the installation went just fine. :)

I'm going to test the living crap out of this ROM now. ;)
[Nexus 4 Android Development] djsubterrain:
That'll do for now thanks ! :)
[Nexus 4 Android Development] pirigu:
Hi guys...i use The beta 2 with hellsdoctor r20 and tardis...do you think it's more good use The stock kernel or leave this One??i think it's good but not so good battery life...sorry for bad english!
[Nexus 4 Android Development] sykopompos:
I think somone is looking into it
[Nexus 4 Android Development] oxxshadow:
hmm it does not work for me... the app never actually gets uninstalled even though I get a notification
[Nexus 4 Android Development] kingracer:
I'll do both :) anyway after installing first beta this bug was too, and there i've done full wipe
[Nexus 4 Android Development] bitstra:
could be - but not if you'll support it as a custom ROM:laugh:

... thinking twice about that future problem::cool:

BTW:

Today i had an inquiry by a compny, if I could make an android-KIOSK-mode app that should be secured on SElinux basis :

They found your xda-thread and asked, if every future ROM could be made PERMISSIVE as your's :)

My precaution answer was: maybe!
[Nexus 4 Android Development] sykopompos:
How about a small companion app that I can put in the ports with a sign up that a user can sign up for a license key for when it goes to official L and you could just email them the license for future L use?

Sent from my LG-D851
[Nexus 4 Android Development] bitstra:
for such a scenario I have a promotion key routine in the app already - but I find an OS-fingerprint routine a kind of smart and easily...

A combo of both could generate a promokey automaticaly for future use of L + M :)

---------- Post added at 02:55 PM ---------- Previous post was at 02:47 PM ----------

Oh, I like the last scenario, the more I think about!
[Nexus 4 Android Development] sykopompos:
Can you lock it to a specific gmail account from there? I'd hate to see you get pirated for doing a promotion for us.

Maybe just record the device name on the ports instead of restricting it to just current devices? I'm thinking about when more ports come online, this way you don't have to add those in when they come online

Sent from my LG-D851
[Nexus 4 Android Development] elegos:
and is it a Google's or a kernel's problem?

Also I've noticed that the kernel supports the double tap to wake (DoubleTap2Wake), though it doesn't seem to work "out of the box". Is there any setting I have to turn?

And how does the Sweep2Sleep work?

Thanks :)
[Nexus 4 Android Development] googleygoggles:
What if some idiot released his email to the public (so others would use it)... You would have to put a device limit too. STUPID COMPLICATED PIRACY!!!
[Nexus 4 Android Development] sykopompos:
Damn, that is a good point that I didn't think about. Damn googley, u are on point right now....

Sent from my LG-D851
[Nexus 4 Android Development] googleygoggles:
I know... All of this on-topic stuff is getting to my head.
[Nexus 4 Android Development] sykopompos:
Hey now, I'm getting a bit scared

Sent from my LG-D851
[Nexus 4 Android Development] googleygoggles:
Me too... I know! Let's talk about pie!

https://www.youtube.com/watch?v=Z-kvd4zGLlo&app=desktop
[Nexus 4 Android Development] sykopompos:
Cheesecake ftw

Sent from my LG-D851
[Nexus 4 Android Development] ph37rd:
Key lime... Not the fake green stuff.

Now I'm hungry while standing in line waiting for my new driver's license.
[Nexus 4 Android Development] sidnoit22:
So what's up guys? Can't follow the thread recently. Explain me in brief guys. :cool:
[Nexus 4 Android Development] bitstra:
I have poppy seed cake right now...
[Nexus 4 Android Development] pables123:
Its odd that when i install first MC5 i cant install Asphalt and vice versa. Maybe there is something wrong with my apps or set up thats causing it.
[Nexus 4 Android Development] sykopompos:
I just pm'ed the kernel Dev of code blue for the n5 left over bunny stew and going forward to make a version of his kernel for the n5 port or allow me to do it and host it to make it available to users. Let's see what he says

Sent from my LG-D851
[Nexus 4 Android Development] sykopompos:
There

Sent from my LG-D851
[Nexus 4 Android Development] Aashuk Mehta:
Been away for a while after bunny stew released. Got a hundred pages to read. Someone can inform me whats cooking ?
[Nexus 4 Android Development] sykopompos:
I once again decided that the next update will be 5.9 and just called breadcrumbs and bunnies. I'm gonna get everyone up to the same point then release in a single swoop all the builds. Then I will go back and do the tedious merging in new res files, making proper updater scripts, crafting new sepolicies and updating to the latest binaries in 6.0 - breadcrumbs, bunnies and witches.

Breadcrumbs is the restructuring based on 81c and fresh and clean so the changes can be seen from the beginning.

Bunny is of course bunny stew, getting everyone at the same point. Mako users will experience a clean out and cleaned up version here since all the excess crap will be gone.

Witches is the final touch and will take us into 6.0.

With the new clean bases, I will not be hitting my stumbling points as I was on the previous base which was a complete hybrid and the merge in with more current aosp should go a lot smoother

Sent from my LG-D851
[Nexus 4 Android Development] sykopompos:
Look above and below you, lol

Sent from my LG-D851
[Nexus 4 Android Development] opee:
Can you give me a link for the flo rom?
[Nexus 4 Android Development] sykopompos:
I'm mobile right now so I would have to dig back pages but if you go on android file host and search me, you will find for the n7, left over bunny stew. That's the current base 81c with the aosp ramdisk and permissive sepolicy

Sent from my LG-D851

Edit. Here is the link https://www.androidfilehost.com/?fid=23622183712458385
[Nexus 4 Android Development] eluspo:
hope you dont use his color profile, better go with stock colors and let user choose what they like. I like the direction that you are going now, i will report bug if there is any, since im already using your n5 rom at the moment. Seems like my battery drain is way better that official preview. Thanks for the effort as always.
[Nexus 4 Android Development] sykopompos:
Does his color profile come through in the kernel itself? I didn't make any mods to his kernel besides repacking his boot image with my ramdisk instead of his

Sent from my LG-D851
[Nexus 4 Android Development] opee:
Okay thank you! Is it stable to use as daily driver? What do you think?
[Nexus 4 Android Development] sykopompos:
It is a lot more stable than the official 81c according to [MENTION=2981094]bitstra[/MENTION] [MENTION=275009]ramjet73[/MENTION] and others that are on left over bunny stew right now

Sent from my LG-D851
[Nexus 4 Android Development] eluspo:
I think so, but i cant confirm since im not using code blue. Lets wait for ramjet to verify that.
[Nexus 4 Android Development] sykopompos:
Yeah, I can't say myself either. Maybe once I get breadcrumbs and bunnies up, some kernel devs might update their kernels for L since there will be a more stable L out for the next 2 months till google releases L officially

Sent from my LG-D851
[Nexus 4 Android Development] eluspo:
That would be great news!
[Nexus 4 Android Development] sidnoit22:
Here. At home. Ckum fast.
[Nexus 4 Android Development] bitstra:
It's definitiv my daily driver since the first install - flashed, connected, updated and restored - that's it. It's smooth, cool and runs and runs and runs and...

No way way back here!
[Nexus 4 Android Development] x.0ni.x:
Well hey guys I'm coming from the T989 and wow for a 2 year old device this nexus 4 is incredible. I've been looking forward to using this ROM. Digggging it!!! Only thing as I'm sure is well know at this point is the "can't connect to camera" bug. Running with the defcon 66 then 72u kernels, ran very smoothly. Just the camera glitch is all i saw. I don't run many RAM hungry apps on my phones. But all in all i can't wait to see this next build. Thanx@sykopompos:highfive:
[Nexus 4 Android Development] bitstra:
Did you made a clean flash of ROM(?) - no camera bug here!

I've forgotten to point out to the disable nuplayer use in dev settings - syko was faster:good:
[Nexus 4 Android Development] sykopompos:
Did you disable nuplayer as mentioned in the second post?

Sent from my LG-D851
[Nexus 4 Android Development] justthefacts:
"can't connect to camera" bug on Nexus 4? I've tried every build and non of them had that issue.
[Nexus 4 Android Development] x.0ni.x:
Ohhhhh no shiz??? Brother my apologies!! I didn't see that!! But it solved the issue!! Thank you!!!
[Nexus 4 Android Development] sykopompos:
[MENTION=2981094]bitstra[/MENTION] can you help [MENTION=4998531]opee[/MENTION] out? He is having some fc on the flo build.

Said it is not multiboot and he did a full wipe

Sent from my LG-D851
[Nexus 4 Android Development] bitstra:
of course!

[MENTION=4998531]opee[/MENTION] - can contact me via hangouts ( sent you a PM...)

---------- Post added at 09:39 PM ---------- Previous post was at 09:04 PM ----------

Hi [MENTION=1050103]sykopompos[/MENTION],

I had a small chat with [MENTION=4998531]opee[/MENTION],

It seems the problem was:

He came from official LPV81c - fullwiped - installed mod-flo-81c and rebooted immediately from recovery to system.

I think in that state, there was an enforced SElinux active ?! Right?!

I would suggest, that we give the hint, that it is important in that scenario (coming from official lpv with an enforced SELinux), that the user after the flash step should reboot from recovery to bootloader - then power off from bootloader - then power button to boot.

So the past enforced SElinux should be deactivated right?

Hope, my english is understandable for this???

As for now [MENTION=4998531]opee[/MENTION] will be happy with a running mod-flo81c, arnt you?!
[Nexus 4 Android Development] sykopompos:
Well the init itself should have set it right to permissive at first thing on powering up before anything else really happens each and every boot so I'm not sure what was going screwy there but it does give a work around for people coming from the official preview build. Remember that [MENTION=4756018]manueltts[/MENTION] also had the same problem on one build when you didn't?

Maybe that is what was happening here and he hit this same bug.

I'm curious if some how it can be replicated so we know the exact reason for this.

I knew you would be able to help him out

Sent from my LG-D851
[Nexus 4 Android Development] ramjet73:
I never play around with the color profiles. How can I tell?

ramjet73
[Nexus 4 Android Development] bitstra:
[MENTION=4998531]opee[/MENTION] helped himself - after some reboots the FCs were gone... So he was OK already, when we started the chat.

But remembered that I had the same issue, when I started flashing Test 5 over LPV81c stock...

And at this point I've forgotten to boot from recovery to boot loader.

Actually I force that 'reboot-to-bootloader' every time, when flashing new ROM...

And I never ran into problems like FCing system apps this way in the past...

ATM I have no time for forcing to reproduce the prob after flash scenario 'with immediately reboot to system from recovery' - but maybe, there is someone out there, who can test both flash variants to be sure, if it is a root of getting problems after flashing this ROM over official LPV on Flo or Hammerhead...
[Nexus 4 Android Development] ramjet73:
Speaking of MultiROM, the OP for the Nexus 5 "L" version of Code Blue lists "Kexec (multirom) full support by [MENTION=3418703]Tasssadar[/MENTION]" as one of the features so it should work in that mode. I don't know if the default kernel for the hammerhead port has that support yet or not. If it does, that would be another feature that the official preview doesn't have.

I've never used MultiROM so I don't know if it's possible to load a ROM into it only after a custom kernel has been flashed. :confused:

ramjet73
[Nexus 4 Android Development] sykopompos:
Actually that boot image I sent you does have multirom and is the stock mod kernel, It is now the included kernel in the builds going forward, I just didn't get a chance to put it in before

Sent from my LG-D851
[Nexus 4 Android Development] d3xt3r:
Can any one please tell me how do I change the kernel to hellscore? Just flash the zip or have to change something in the inject boot sector thingy?? And I got a strange problem

Play store doesn't work on WiFi. Every thing works on the WiFi. Except play store. Have to switch back to data to access. But if the download started, I can switch back to WiFi and the download would be done
[Nexus 4 Android Development] ramjet73:
Just flash the zip if you are using the default kernel for B5, otherwise you need to dirty flash the ROM (wipe cache and dalvik only) before flashing Hellscore to clear out the init.d script(s) and possibly additional remnants of other kernels.

You might find Hellscore Kernel Manager from the Play Store helpful for configuring Hellscore after it's installed.

ramjet73
[Nexus 4 Android Development] psycho693:
[MENTION=1050103]sykopompos[/MENTION] I can say your version of code blue kernel does not have the custom gamma config but the kernel he built does
[Nexus 4 Android Development] eluspo:
that a good thing, im gonna try it out. Can you post a mirror for the kernel bro?
[Nexus 4 Android Development] NEXUSg4:
Yup you can install it. Its stable and I am using this as my daily driver.
[Nexus 4 Android Development] ramjet73:
Are you having problems downloading from the Google drive link that [MENTION=1050103]sykopompos[/MENTION] provided?

ramjet73
[Nexus 4 Android Development] eluspo:
Downloaded it, i was just missing root explorer thats why it cant download the whole thing.

---------- Post added at 11:11 PM ---------- Previous post was at 11:09 PM ----------

Any feedback about the modified code blue bro? How is it running on L?
[Nexus 4 Android Development] psycho693:
Nvm he got it.

---------- Post added at 06:17 PM ---------- Previous post was at 06:14 PM ----------

I've been running it all day and so far so good
[Nexus 4 Android Development] eluspo:
Thanks anyway bro ?

---------- Post added at 11:31 PM ---------- Previous post was at 11:18 PM ----------

Lets see how the ramdisk changes plays with code blue and L.
[Nexus 4 Android Development] sykopompos:
Yeah... I didn't care for the code blue's Dev response even though I offered to do the work but he seems he cares more about his thread and download counter then anything else so I'm not gonna support his project one bit.

Guess you nexus 5 users are **** out luck when it comes to a custom kernel.

Sent from my LG-D851
[Nexus 4 Android Development] psycho693:
That's really unfortunate. I will ask around and see if we can get some help.
[Nexus 4 Android Development] sykopompos:
It's up to you guys to mod it to make it work, you just gotta replace his ramdisk in the boot.IMG with mine. I offered to do the work and send him the modified boot images when I update and all he has to do is host them since they are still his but he didn't seem to get the point. Nor did I like his attitude about it has to go through his thread and his downloads through his website when I offered to send them to him.

He said I can have it modified after they download from him and flash his zip when I sent him his zip with his ramdisk replaced to work with his kernel. I'm not going through the work of modifying it after the fact and I don't like that blow off attitude when I basically offered to do the work for him and let him take credit.

Oh well, his loss and I will be taking down the link for the modified boot.img then

Sent from my LG-D851
[Nexus 4 Android Development] psycho693:
I understand man no worries. I will look into how to modify the kernel and make it work.
[Nexus 4 Android Development] ramjet73:
I have no previous experience with that developer but that seemed to be his attitude about the touch wake options too. He made it clear in the thread that it's his kernel and he'll decide what's included.

Too bad. :(

ramjet73
[Nexus 4 Android Development] sykopompos:
All that needs to be done is split his boot image, take the kernel out and match it with my boot image and pack it back up but he doesn't want any modified binaries outside of his thread's op. So that's fine

Yeah, I don't like that attitude at all. This is supposed to be a community and when someone else even offers to do the work and send it back to you so you get full credit and you turn it down then that is counter productive. I'm the ROM Dev and wanna make sure that his kernel works with my ROM as intended but oh well, guess no blue for you guys

Sent from my LG-D851
[Nexus 4 Android Development] criminalzen:
someone should fork his kernel make it work.. happens all the time... usually makes devs happy when peeps adapt their work and give them props...
[Nexus 4 Android Development] sykopompos:
Nothing has to be modified in the kernel at all for it to work. It is just distributed in a boot image format. The boot image has it's own ramdisk that would overwrite mine. If he provides a any kernel version that doesn't modify the ramdisk (like what we are using here on mako) then nothing would need to be done other then flash the any kernel zip

Sent from my LG-D851