yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] treefrog20012003:
Im going to try again when i get home. Who knows really with phones. Im no beginner at this but I've had phones that didnt like certain roms so if it wont boot to it after a fresh install ill just take it the phone dont like it. Ive had to sideload a few times due to me being in a hurry and sure do miss the sdcard sometimes but i love this phone.
[Nexus 4 Android Development] xsasuke:
Is the b6 available? I was busy last days and dont see b6 links at first page, and it seems some people is getting problems with root, right? Would like to test it and give my feedback.
[Nexus 4 Android Development] ph37rd:
Well, since you're unwilling to wait and you have the itch to flash, you're still going to have to be patient. You're either going to have to be patient and read the thread over the last day or two, or you're going to be patient and wait till it's released and listed on the OP (since you don't keep up in the thread). Not saying it's a bad thing either way... no condemnation... nothing personal... etc...
[Nexus 4 Android Development] f4ll3n:
Yes here is the link

Slim one i m using no FC no crash no freeze

For root solition up pages basicly reinstal busybox

https://www.androidfilehost.com/?w=files&flid=18546
[Nexus 4 Android Development] sykopompos:
For those who missed it the first time

I'm not at my computer yet to update the op
[Nexus 4 Android Development] sykopompos:
To those having issues with root working. That is either a bad flash or a dirty flash.

If you are coming in from a dirty flash from 5.9 or earlier, almost all the google apps have been swapped out including the core ones where possible so there is a good chance you will get force closes there.

Also almost every single proprietary file has been updated so that could be the issue too.

If you experience any of this funky behavior even on a clean flash. First check your md5 and ensure it is the same as afh to make sure it wasn't a bad download, second there might be some left over remnants of a kernel or the like still sitting around on your /data so try a clean flash again.

If you were using a custom kernel with different voltages, it might take a few reboots to get the the voltage table back to stock. The advised way to avoid the reboots is after you flash, reboot to the boot loader and then power off. Wait a minute and boot up, this resets the voltage table
[Nexus 4 Android Development] ramjet73:
Idea :)

If you need to do this again (make a temporary "OP") you could just replace the download link in the real OP with a link to your original post so you don't have to repeat it.

Or is editing the OP at all on your phone just too messy?

Doesn't the G3 have an "auto update" button?

ramjet73
[Nexus 4 Android Development] sykopompos:
Editing the op is very messy on the phone and I have messed it up a few time that I tried it :eek:

No auto update button that I know of but I'll be honest and say I haven't dug around the phone enough to see if there was
[Nexus 4 Android Development] sykopompos:
that version isn't done yet, there was some teething issues in it.
[Nexus 4 Android Development] xDroid4Lifex:
Link in first post, its all listed on github
[Nexus 4 Android Development] Kimbaroth:
Edit: My bad, thanks!!
[Nexus 4 Android Development] googleygoggles:
How is everyone else flashing in multirom?
[Nexus 4 Android Development] himzz0007:
https://github.com/Android-L-Porting-Team/Android-L-Mako/releases
[Nexus 4 Android Development] ramjet73:
That's the way the check is implemented. There's no message, the tethering functions just don't work.

If you check the OP I linked (twice now) with the flashable zip file you will see there is a link there for "older versions" under the current 1.5 update:

Edit: If it's still not clear read this article.

ramjet73
[Nexus 4 Android Development] rskyline:
The new build only fix WiFi? I don't have any issue with it...
[Nexus 4 Android Development] DRS2442:
Gonna dirty flash or "update" from Beta 2 to Beta 3 Preview 3.

Anyone did the same, any issues/advice besides the usual pre and post cache and dalvik wipe?
[Nexus 4 Android Development] ebart:
Which one of the old zips works on this port? Also I am allotted 5gb of tethering but it still doesn't work.
[Nexus 4 Android Development] dodgebizkit:
I just tried AK 300 - on beta 2 I t was perfect, on beta 3-2 it kills WiFi.

The Franco kernel mentioned earlier in the thread so far works well :)

--------------------------------------------

My house phone's better than your iPhone.
[Nexus 4 Android Development] Raiden350:
So it's okay to make a dirty flash or no ?
[Nexus 4 Android Development] ramjet73:
See the edit to my previous post. There are instructions in that article on how to make the changes manually.

Are you on the $80/month unlimited data plan? The tethering check shouldn't be an issue if you are since that does include 5GB of smartphone tethering. If you are on the $30/month 5GB data prepaid plan it includes no tethering at all.

I'll test tethering on this ROM with the SIM card from my other phone which has enough of a tethering allowance to do the test.

ramjet73
[Nexus 4 Android Development] ebart:
$80 plan.
[Nexus 4 Android Development] sandy7874:
Hells Core

Is Hells Core is working with this Bet 3 version? any idea? I kept Beta 3 for dnld and have left with 25 min.
[Nexus 4 Android Development] jayRokk:
Do this.

1st. Add beta3-3 to your list.

2nd. Wipe everything.

3rd. Go back to multirom and select beta3-3 that you added to the list.

4th. Flash it.

Wiping and flashing directly always gives me an error so maybe this is what you're doing.

Just trying to help :)

That's what I been doing so far and it works.
[Nexus 4 Android Development] johnb380:
I get tethering in my plan too and can't tether no matter what I try...
[Nexus 4 Android Development] [FOX]:
Just flashed over beta2 with dalvik and cache wipe, everything seems to be ok.

If you doubt, you can always make backup and try.
[Nexus 4 Android Development] Aoude.:
Sorry I think this has been stated but, are the devs working on squashing bugs withing the port as well those native to the preview? Not expecting, just curious.
[Nexus 4 Android Development] [FOX]:
Anyone having issues with standard alarm clock? It crashes UI when shows alarm. Is it port or dev preview bug?
[Nexus 4 Android Development] ramjet73:
Yea, I think the tethering may be a little buggy. I tried to setup the WiFi hotspot with my own SSID and passphrase and once I changed the SSID it wouldn't allow me to access the passphrase.

Has anyone accomplished any kind of tethering with this ROM yet? I'm still on beta 2 so I'm going to update to beta 3 pre 3 and do more testing.

ramjet73
[Nexus 4 Android Development] sykopompos:
0.0 were you able to find that SDK zip or do you need me to reupload it?

I think I might know why I'm running into the bad XML block on 81c

I believe in bunny stew/79, I only updated animations and colors and I think with trying to update the anim, might be the issue. One of the animation XML files is causing it though
[Nexus 4 Android Development] sstarlight:
Yeah my bbm works great now. Change it to Full installer. :D
[Nexus 4 Android Development] 0.0:
I didn't get a chance to look at it. I will later tonight. But if you ran into problems, I bet I will too, so I'm debating whether to try or not

Sent from my Nexus 4
[Nexus 4 Android Development] treefrog20012003:
Well I'm not sure what happened to my N4 but currently downloading the stock firmware and going to apply it, re-root and custom recovery to try it all over. I'm guessing there was a mistake on my part and the file structure was damaged. I probably deleted the wrong section or something not being used to CWM. I'll be using TWRP from now on as I have grown used to it even though I started with CWM on the OG Droid. Stupid me:laugh:
[Nexus 4 Android Development] ramjet73:
I don't think you will regret that decision. TWRP has so many advantages over CWM:

- Data compression for backup (NANDroid) files

- Built-in file manager (or file mangler for some:))

- OTG support for flash drives

- Sideload for updates using ADB

- More intuitive options for format, backup and restore

- and much more :good:

ramjet73
[Nexus 4 Android Development] tember1214:
Clean flashed slim and working great. Smooth!!!!!!! I actually traded my Moto X awhile back specifically so I could flash this. Been using it for quite a while
[Nexus 4 Android Development] treefrog20012003:
Only problem is I'm having trouble getting the adb to work in bootloader, sideload is working but I need to flash to stock and it won't accept a connection since my screw up. I'll keep searching for the answer and trying different things till I figure it out. Never borked a phone this bad before.
[Nexus 4 Android Development] ramjet73:
You should just bite the bullet and flash the KitKat 4.4.4 factory image. The instructions are on that page if you don't mind using the command line a bit, and if you prefer using a GUI the Nexus Root Toolkit is pretty cool.

Flashing the factory image will ensure that everything is 100% in sync again. :good:

ramjet73
[Nexus 4 Android Development] sykopompos:
There is a test build up for flo in the flo Dev thread [MENTION=2981094]bitstra[/MENTION] [MENTION=4756018]manueltts[/MENTION]
[Nexus 4 Android Development] treefrog20012003:
I'm no stranger to the command line that's for sure, I'm giving the tool kit a run as it is getting late and I just want to get back up and running again. If that fails I'll resort to command line and get it done.:fingers-crossed:

Edit: Well the factory flash failed to finish and I'm not sure why??? BUT what it did flash through the toolkit fixed the phone enough that it boots to slimkat which is what I sideloaded after all of my problems diagnosing. I'll run this tonight to get me through the day tomorrow and then I'll do a factory image to start over. Fun Fun Fun! Thanks for all the help on this one and I can't wait to try this rom out.
[Nexus 4 Android Development] sykopompos:
you've been OP'ed :cool:
[Nexus 4 Android Development] treefrog20012003:
I'm going with human stupidity (if that's a word really) on my part for my trouble. Human error is 99% of the problem this time and I'm just accepting that and learning from it.:D
[Nexus 4 Android Development] sykopompos:
No problem, most of the time, most errors when only a few people here and there that are having them are usually related to human error but it happens to all of us.

But even I have been caught in that trap and there is times where I go to test something I'm working on and do the same thing and have to smack myself in the face
[Nexus 4 Android Development] ramjet73:
None of that was directed at you and it was just a coincidence that you happened to be posting about the same time. Believe it or not the problems are actually worse in the Nexus 5 thread because I think users with the latest devices need/want to believe that they know it all. :rolleyes:

BTW, I'm originally from Dayton which is not far from Wooster. I also lived in Massachusetts where it is spelled Worcester but pronounced almost the same way. :)

ramjet73
[Nexus 4 Android Development] sykopompos:
why not give it a try. I'm always jumping between something so it might have been a goof on my behalf
[Nexus 4 Android Development] justthefacts:
I had heating problems and heavy battery drains with Bricked kernel on all previous builds. So far there has been none of those issues on Bricked (may be I'm jumping the gun too soon). Took the phone for a ride with gps navigation and after that it's been tethering all day and has stayed cool all along. It also seems to be charging faster.

Another pleasant surprise was from one of my apps "Silent Time" which has a feature called "Exceptions" which will let the phone ring during the silent times for any preselected contacts. This feature has not been working on almost all kk roms and all previous L releases. It has somehow come to life on this build.

This build is in a class by itself.

Job well done. :good:
[Nexus 4 Android Development] sykopompos:
Thank [MENTION=3754150]psycho693[/MENTION] for tracking down some of the looping code and smashing those bugs
[Nexus 4 Android Development] treefrog20012003:
[MENTION=275009]ramjet73[/MENTION] I didn't think it was but simply wanted to let others know that it was my error and not a problem with the ROM. Sykopompos, yes a smack to my face is what I did. I definitely deserved a face palm for it! Lol, night all.

Edit: A blessing in disguise!!!! Apparently my phone was not formatted correctly when I bought it from the last person. Didn't really think about it but my storage went from 4gigs at best to 11+gigs of storage. Guess it was really a good thing.
[Nexus 4 Android Development] ramjet73:
Yea, that's a known problem with the Nexus 4.

Sometimes the 16GB models will show as 8GB and the standard fix for that is to do a factory reset in the "Backup & reset" section of the settings menu. By flashing at least part of the stock ROM you effectively did the same thing. :good:

ramjet73
[Nexus 4 Android Development] sykopompos:
Alright. Saved another 5mb so far by taking out the built in hard symlinks in /bin to toolbox that were already being symlinked by the updater script.

It isn't much but that stuff starts adding up
[Nexus 4 Android Development] gururoop:
All those who are fans of 'new' material design signal and wifi icons in statusbar, since [MENTION=1050103]sykopompos[/MENTION] has recommended against flashing systemui_modded-version_2.zip (because it belongs to an earlier version), I have modded the SystemUI.apk from bbw6 to have the same icons. All credit goes to the original modder.
[Nexus 4 Android Development] 3matthew3:
WiFi hotspot

Does anybody have the WiFi hotspot feature working on the build? Absolutely love the last version of the ROM b5.9, but couldn't share my LTE with my 5 yr old's N7 in the car. Just flashed a couple KitKat Roms tonight to get my hotspot back and am majorly depressed.
[Nexus 4 Android Development] Rohit02:
:crying: I wish you should have SEARCHED before posting this.
[Nexus 4 Android Development] sykopompos:
Toggle it twice and it works from what I hear on b6
[Nexus 4 Android Development] sykopompos:
[MENTION=275009]ramjet73[/MENTION] you were asking about furnace kernel earlier. That's by savoca and I know he worked with defconoi so I'm pretty sure his kernel is perfectly good to go here
[Nexus 4 Android Development] philowneus:
Reboot to boot loader. I did forget that. I was doing so well to remember after flashing over 100 updates of defcon's kernel.
[Nexus 4 Android Development] ramjet73:
This post from the old "rumors" thread pretty much sums up what needs to be done for T-Mobile USA. The real trick is to toggle the hotspot on/off/on a couple of times and make sure your APN protocol is IPv4 and not IPv6. You may or may not need the settings.db modification depending on how your carrier handles authorization for tethering.

It still works for me on B6 with T-Mobile with this ROM but not the one for the Nexus 5. :confused:

It looked like it already has some ramdisk mods and what surprised me was seeing Nexus 4 kernels labeled as "L".

Here's the directory containing the ones that were mentioned last night.

[MENTION=774400]ruicc[/MENTION] said that he is using the OC version with this ROM already.

ramjet73
[Nexus 4 Android Development] sykopompos:
He is making a special version from what I saw reading through his thread so most likely it is the ramdisk modifications from here for L support.

We still got at least a month to 2 for official L and from what we learned here, we can probably get a mod to use kk kernels going in official L when it comes out till devs get a chance to update their kernels
[Nexus 4 Android Development] ferrocene:
Loving b6 and 82u. Very fast and snappy!

One strangeness: I now get a dim red led notification light randomly for no reason (battery is full). I thought that was odd.
[Nexus 4 Android Development] sykopompos:
That is in synapse and is a led setting. From what I read in defconoi's kernel thread, that is a thermal light and can be configured through synapse
[Nexus 4 Android Development] ramjet73:
I thought we agreed that wan't necessary. Since there are now a lot of L-compatible kernels for the Nexus 5 that gives the other kernel developers more incentive to move to native L rather than try to get their KitKat kernels running on L. My guess is that the same thing will happen for the other devices supported by L when it is released.

Was anyone excited about getting JB kernels to run with KK ROM's?

ramjet73
[Nexus 4 Android Development] sykopompos:
I meant his modification was to the L ramdisk that we are using for his features and not to the kernel itself so he can support both kk and L kernels
[Nexus 4 Android Development] sykopompos:
Oh derp, I read it wrong.

As far as a mod, well since when the official images come out, they won't even be a working su yet most likely with the selinux lockdown coming, it will probably be several days till kernel devs get working kernels out for L since it is supposed to be a new version.

Since we will probably be the first custom L since it is just patchwork at that point to upgrade, we will be a bit of the trend setters so people will be asking for kernels and thing like that so maybe if a mod could be done while waiting on the kernel devs to patch up, wouldn't be a bad thing
[Nexus 4 Android Development] ramjet73:
I lost you there.

Whose modification(s) are you taking about and how does that relate to supporting KK and L kernels with ramdisk changes? My understanding is that source patches are required for kernels to support L on the Nexus 5. I think it was [MENTION=5334172]Gnome[/MENTION] that told us that because he started with a KitKat kernel but added github patches to make it L compatible. If you are talking about [MENTION=4316709]savoca[/MENTION] I have no idea what he did to his ramdisk and KitKat kernel to make it run with this ROM but we've already had several before that (Hellscore, Ultimate, AK) do pretty muich the same thing as long as they use anykernel installations. I think the "L" designation on [MENTION=4316709]savoca[/MENTION]'s kernels is pretty much marketing at this point. ;)

Once the official L comes out for the N4 I'm sure source patches will be required to make KitKat kernels compatible with L, just like the Nexus 5.

Unless I'm missing something. :confused:

The developers who currently have kernels for both the Nexus 4 and Nexus 5 with an L compatible kernel on the N5 will get the jump on everyone else since they will pretty much know the changes required for the Nexus 4 already. And IMO they deserve that jump for supporting L early. The rest of the Nexus 4 kernel developers can try to get help from them. :rolleyes:

ramjet73
[Nexus 4 Android Development] V_tunes:
GUYS, Is there a screen record app work for L ? i tried some apps but it doesn't work for L.
[Nexus 4 Android Development] ramjet73:
Haven't looked for one myself but you might get better feedback in the Nexus 5 official preview app compatibility thread.

I would tell them what you've tried that hasn't worked and ask if anyone has suggestions.

AFAIK there is no way to record a cast screen to a Chromecast (yet).

ramjet73
[Nexus 4 Android Development] sykopompos:
[MENTION=275009]ramjet73[/MENTION]

Nope, you aren't missing anything. I'm just half retarded right now. The lack of sleep is catching up again
[Nexus 4 Android Development] hazwheel:
Worcester is how we would spell it in England, in fact we have a town by that name and spelling. And Worcestershire sauce [emoji12]

Sent from L

---------- Post added at 07:31 AM ---------- Previous post was at 07:28 AM ----------

JB kernels worked on KK? [emoji12] no, that did not excite me.

Sent from L
[Nexus 4 Android Development] V_tunes:
thanks a lot, i have tried "Rec. (Screen Recorder)" which is work for KK.
[Nexus 4 Android Development] psycho693:
Wow that was really nice of you! Thank you very much! I will test it out and report back you. ;) and just so you know you have helped a lot more then you think!
[Nexus 4 Android Development] blacknikname:
Thank God that the guys at Google do not think so ...
[Nexus 4 Android Development] KrisMurdrum:
This is so generous of you, thank you very much [emoji33]

Also, you may wanna go through your post and edit out the pic name out of the IMG brackets as in [ IMG ] URL [/] and not [IMG "file name"] URL [/im]

Og and here is a little something for you

Sent from my Nexus⁴ L[icorice]
[Nexus 4 Android Development] ruicc:
Many, many thanks mate.

Any change to add a feature like a customizable sidebar?
[Nexus 4 Android Development] bitstra:
Have a look into BL-Settings-> Themes / Icon-Size / Hide/show App Names (That's all for now...)
[Nexus 4 Android Development] KrisMurdrum:
Yay! I got thanks[emoji33] [emoji94] !

Now I've only gotta square my total thanks and I'll have half of what sykopompos has [emoji12] lol

Sent from my Nexus⁴ L[icorice]
[Nexus 4 Android Development] bitstra:
and of course BL-Settings->Text color (forgotten that:))
[Nexus 4 Android Development] mati1414:
Hi!

Anyone tried to install Order and Chaos on this port? Game shuts down for me while connecting to server. Any ideas?
[Nexus 4 Android Development] bart.found:
Hi sikopompos.. Yesterday I had a misbehaviour of the rom.. While i was opening google maps (with lots of recent apps) the phone became laggy and then froze.. No kernel panic in kmsg.. I tried to turn off the phone, but popup didn't appear.. After a while it selfrebooted, but in kmsg last reboot reason was "reboot"
[Nexus 4 Android Development] sykopompos:
That could be a case of so many things I'm not even sure where to even start on diagnosing it. It could be anything from a incompatible app with looping code (we see how much cleaning that kind of stuff out sped of the system so imagine it going the other way) to a possible memory leak inherent in the system, to bad memory management by a custom kernel (the lmkd shouldn't allow this but if it's functions were replaced, it could be an issue) to so many other things
[Nexus 4 Android Development] 0.0:
Would I have to decompile the framework-res.apk? if so, what do you use? apktool doesn't work
[Nexus 4 Android Development] Micoolef:
What radio are you using for the LTE with this ROM?
[Nexus 4 Android Development] sykopompos:
Nope, you are just replacing out res files which can be done with handling the apk as a zip
[Nexus 4 Android Development] bitstra:
_deleted_

using no lte (german provider) here - sorry
[Nexus 4 Android Development] CamoGeko:
most likely a hybrid radio.
[Nexus 4 Android Development] Roboffabike:
Just chipping in to say b6 running fine here.

(Dirty flash from 5.9)

In fact, apart from the 'Bluetooth in car' problem, I haven't had a single issue since b3p5.

How dull...
[Nexus 4 Android Development] bart.found:
Thanks for the reply! For the future, hoping that it don't happens again, which log could help to debug this issue?
[Nexus 4 Android Development] sykopompos:
It would come down to trying to identify where the issue came from.

Dirty flash, clean flash, what 3rd party apps are installed, what apps where in use when in happened, are you using a custom kernel, is it tweaked using something like synapse, if so, are you under clocked, undervolted.

That kind of stuff, there is so many variables that even where to look in the log to try to isolate it would be difficult
[Nexus 4 Android Development] 0.0:
I must have done something wrong. I replaced the files in the anim and animator folder. My phone only bootloops :(

sent from my Nexus 7
[Nexus 4 Android Development] CamoGeko:
BTW has anyone tried running latest Franco kernel?
[Nexus 4 Android Development] sykopompos:
Yeah, that is the bad XML block. I think it is one of the anim XML files doing it and I can't remember exactly which ones were good to use in bunny stew.

You could try merging in the res files though and see where that gets you. That will be a bit tedious though since some of the folder names are renamed differently in the SDK
[Nexus 4 Android Development] opee:
I have Wi-Fi issues with the latest build! What can I do? Random aborts...