yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] kldoc:
Well, the software is supporting it, but neither the kernel neither the SOC does, so basically, it'll always say slow charge, that's what it says on mine.

Forcing it might actually destroy your phone (physically), superior voltage than what the phone can handle etc ... I highly recommend NOT to force it.

es-file-explorer-updated-with-super-shady-speed-charging-adware
[Nexus 4 Original Android Development] schiznik:
It also says just 'charging' if you have a powerful enough charger. I believe it's 1A and under that are 'slow charging' ones. You're correct that it will never show up as fast charging - you need the hardware in the phone to do so.

(My 6P shows all three states, depending on which charger I'm using, and will never show a fast charge from an n4 compatible charger)
[Nexus 4 Original Android Development] kldoc:
I don't recommend beyond 1A, and 1 A is already a bit too much for Nexus 4, original charger was way bellow that ...
[Nexus 4 Original Android Development] schiznik:
My original (UK) LG charger is rated a 1.2A. Technically, a 100A charger will be fine, albeit massively overpowered! - the hardware in the charging circuits in the phone will only pull the maximum safe current.

I've had my Nexus 4 charging with a good quality 2.1A charger for years and never had any issues with it, or the battery in the phone.
[Nexus 4 Original Android Development] kldoc:
My original charger was a Hong Kong one (i'm in China), and it was way lower than that ;)
[Nexus 4 Original Android Development] 2LoT:
Install instructions from Kitkat?

Hi gentlemen,

Can you please give me a quick summary for installing Omni6? Currently using SlimKat. Is it OK to jump directly from Kitkat to Marshmallow base?

Here is what I plan to do to install Omni6, can you please let me know if it is correct?

1. Make a Nandroid backup of the current phone (SlimKat, based on Kitkat 4.44) using TRWP currently on the phone

2. Install latest TWRP (twrp-3.0.2-0-mako.img)

3. Full wipe: Dalvik, Cache, System, Data, Internal storage

4. Factory Reset

5. Wipe: Format Data

6. Copy into internal SD card (using adb push) Omni6, Open GApps arm 6.0 Mini, latest BETA-SuperSU-v2.72

7. Flash in the following order: Omni6, OpenGapps, SuperSU (select the 3 Zip in that order, and flash all 3 in one single operation)

8. Reboot to system

Thanks in advance for any advice.
[Nexus 4 Original Android Development] Fif_:
Looks good to me.
[Nexus 4 Original Android Development] saenanme:
For me too. It is not necessary to wipe internal data. Only if you don't mind to lose your personal files.

Also, there is a more recent version of the SuperSU and flash it in the second place, before the gapps.

Finally, if the SuperSU app asks to upgrade the binaries, don't let it do it during the reboot process.

Regards

Enviado desde mi A0001 mediante Tapatalk
[Nexus 4 Original Android Development] Fif_:
I believe the internal data wipe is necessary given that he's moving between ROMs.
[Nexus 4 Original Android Development] saenanme:
Recently I changed from cm13 to omnirom and I didn't wipe my internal data.

All went fine.

Regards

Enviado desde mi A0001 mediante Tapatalk
[Nexus 4 Original Android Development] kldoc:
Hi, you were very near, but since you were on a kitkat ROM, most likely your bootloader and radio are outdated, so you'll need to update those too, available from stock ROM, or some threads in Xda got those as well.
[Nexus 4 Original Android Development] 2LoT:
Does that mean I must flash a stock ROM first (which one? is there a stock Marshmallow for Nexus4?). Then reflash on top of it the Omni6 ROM?

In the page Factory Images for Nexus Devices (occam, Nexus4), the latest is 5.11. And I am afraid to flash it because the device name is "occam". I always used ROM for Nexus4 with "mako" as device name.
[Nexus 4 Original Android Development] kldoc:
No, no need to flash the whole rom, only bootloader is required, but those are available on Xda.

fastboot flash bootloader bootloader.img (not 100% sure about the syntaxt)

fastboot flash radio radio.img
[Nexus 4 Original Android Development] 2LoT:
Would that be OK if I do the following:

1. Download the latest Nexus4 Lollipop 5.11 stock image LMY48T

2. Uncompress to get the bootloader and radio image files (*.img)

3. Flash by: (inspired from this blog)

adb reboot bootloader
fastboot flash boot bootloader-mako-makoz30f.img
fastboot reboot bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.07.img
fastbpoot reboot bootloader

Question 1: please note: the bootloader and radio images are from LOLLIPOP, is it compatible with Marshmallow?

Question 2: Assuming Q1 answer is yes. Just after flashing bootloader and radio as above. Can I immediately continue to proceed with the installation steps described a few posts above?

Question 3: Assuming Q2 answer is yes. What good to flash bootloader and radio, then to immediately format the SD card (I do a Wipe Format Data before flashing Omni6) and reflash a brand new Omni6 ROM on top?

Sorry for the silly questions but I am rather confused. Thanks in advance for any help.
[Nexus 4 Original Android Development] kldoc:
Q1 and Q2, yes, bootloader from Lollipop is required to be able to boot Android 6 as far as I know, and you would end up with problems with the phone part if you don't update the modem firmware (radio).

You can freely proceed as you first intended by the time you did update bootloader and radio.

I'm not sure of the retro-compatibility of bootloader and radio with kitkat.
[Nexus 4 Original Android Development] mrk2815:
just checked the super su forums on XDA . super su has now ben updated to supersu beta 2.74.
[Nexus 4 Original Android Development] graylox:
Hi everyone,

I'm using omnirom 6 for some time now and haven't any problems so far. Except with Qi charging. When I place the phone on the Qi charger it's starts charging till it reach 100%, but rather than holding it, it discharges relative quickly down to around 75% to begin charging again. So in the morning I never have 100% load. Normally it's around 85 to 90%. I had the same problem with cm12 and 13. With lollipop stock rom and Fake-Rom (marshmallow) it works fine.

So I want to asked wether this is a bug, if others have the same problem or do I have to change something in the settings or do I have to use a diffrent charger (now it's 5V/1.5A)?
[Nexus 4 Original Android Development] kldoc:
Give me a logcat, so i can see what's going on when you use Qi charging, i don't have a Qi charger myself, so i can't test/reproduce this.

I'll try to see what was done in Fake-Rom on that side, but i need your logcat to know what I should be looking for.
[Nexus 4 Original Android Development] graylox:
Okay, thanks. Here is the logcat. I had to zip it, because the file is 850kb large, which exceeds the limit for a txt file here.

It seems there's a lot going on. But unfortunately I can't read it :eek:

Edit: I split the logcat and add it as well. If you feel it's more secure. ;)
[Nexus 4 Original Android Development] kldoc:
I've read the log, the only things that indicate some battery activities are those:

[ 05-29 04:50:50.762 1998: 2017 I/BatteryStatsImpl ]

Resetting battery stats: level=100 status=2 dischargeLevel=100 lowAmount=0 highAmount=0

Battery is charged, no no need to charge anymore.

What bothers me is that thing that seems to chain:

[ 05-29 04:50:50.774 1998: 2017 E/BatteryStatsImpl ]

Removed unknown observer: com.android.internal.os.BatteryStatsImpl$SamplingTimer@97537a4

Thing is i couldn't find the ROM sources for fake-rom, they only published device tree, no kernel tree either. Hard to find what they changed without the sources.

I've asked team if someone had a Qi charger, doesn't seem anyone got one. It's going to be tough to debug ...
[Nexus 4 Original Android Development] kldoc:
On a sidenote, don't expect miracles for Android N, hammerhead, flo will be both retired, I'll do what I can, but it will be very difficult to make it work without new drivers, and without blobs from flo, I don't really see how it'll be doable, with a bit of luck, kernel will work unchanged (or very few modifications), but that's very unlikely.

I'm myself preparing my Nexus 4 for retirement, heading towards future HTC Nexus. I'll support it as long as I can, but yeah, I don't have much faith for N right now ..
[Nexus 4 Original Android Development] saenanme:
Maybe a cm14[emoji20]

I prefer this one but I can live with cm

Enviado desde mi A0001 mediante Tapatalk
[Nexus 4 Original Android Development] kldoc:
CM or OmniROM or whatever other ROM will be the same problem, without Android N blobs, kernel won't boot, so until someone find a solution that works (if there's one), it might take a long time before ANY ROM manage to boot Android N on Nexus 4.

I wanted to make things clear since you had a misunderstanding, it's not a ROM issue, it's just that Nexus 4 is completely EOL, and we used Nexus flo blobs to have Marshmallow running. Flo won't get N, and Qcom already dropped our SOC a while ago, so not much resources from caf either. So it's really not a matter of who, but how ...

It's too early to predict what will happen, but given that we need newer adreno blobs for N, i can't think of a single device that use adreno 320 that will get Android N, and the problem is there ...

And ... This device is turning 4 years old, that's not too bad to have a device performing that well after 4 years.

Other problems will arise, system partition is getting too short too, so yeah, Nexus 4 bringup might be doable, now will it be usable, that's another question ...
[Nexus 4 Original Android Development] saenanme:
[MENTION=2604804]kldoc[/MENTION], I really appreciate your effort. I didn't want to criticize it.

For sure I full aware that our N4 is reaching its deadline, it's a petty for a device that I think is fully capable of ruining android N if we have the proper sw.

That's just my 2cents

Again, thanks for your work

Enviado desde mi A0001 mediante Tapatalk
[Nexus 4 Original Android Development] kldoc:
It's not dead yet :p

And i'll try my best to keep it breathing, but i have to be honest, loading apps tends to take more and more time, we're lacking ram, we're lacking space, system partition is too short, issues with larger gapps packages proves it.

My point, is even though i'll try my best for the bring up, and i'll try my best to get the device as near as possible to nightlies, it's time to think for a change, i've been waiting for a year for a suitable replacement, and NO phone has come that made me think it would be a nice replacement, i'm willing to buy a device with a s820, HTC 10 would be a good choice if it wasn't so expensive, and if they didn't bring a lowered version in China (****ty move HTC if you read this ...).

I was tempted by XiaoMI mi5, i've even received an unlock code, but without kernel sources, useless.

Then there is the one plus 3 that is coming soon that might be an option, or the HTC Nexus that is coming october/november, and given I was able to stay 4 years with that Nexus without much issues, it's really tempting. That's where I am in my choice decision.

I'll keep the Nexus 4 whatever happen to maintain it, until it effectively dies, but N will probably be the last version of Android i'll try to bring up in a timely manner.
[Nexus 4 Original Android Development] saenanme:
I'm thinking also in opo3 but today Asus has released some interesting devices. Maybe they deserved I take a look on them ...[emoji6]

Regards

Enviado desde mi A0001 mediante Tapatalk
[Nexus 4 Original Android Development] donz_Simon:
Is this rom have "volume rock wake" feature?
[Nexus 4 Original Android Development] kldoc:
Yes it does.
[Nexus 4 Original Android Development] graylox:
Thanks for looking at the problem. I'm used to use Qi charging, it's very handy. But if you can't fix it .... it's not a big deal. And like you said it the phone is getting old (despite the fact that it's running better with Android 6 than ever before). I was aware of that our beloved Nexus 4 will not getting Android N and I'm fine with it. I was just hoping to get the security patches for a couple of month more. And then hopefully google will bring some new Nexuses to the market that are closer to what the Nexus 4 is.
[Nexus 4 Original Android Development] mrk2815:
thanks for all of the efforts for maintaining nexus 4 on the latest .as long as it can get the security updates that's all that matters.

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

but can it at least be maintained with security patches .I don't mind keeping my nexus 4 on marshmellow till I figure out what i do with my next device.
[Nexus 4 Original Android Development] kldoc:
Security updates are mainly a ROM thing, very few changes in mako's kernel now, if Omni updates marshmallow once N is there, it'll get updated, but there will be an EOL on this.

I didn't say Nexus 4 won't get N, i'm saying it's very unlikely it'll get N as fast as it got M admitting there are problens with blobs. Now, everything could very well turn in our advantage, with very few changes to device tree and kernel tree to make it work, all hope isn't lost yet.

But I prefer to warn ahead that it won't be an easy task to do as problems rise, and since i'm the single maintainer on Omni for it, it might take a while for me to get things in order.

In other words, it might very well work perfectly, as it might not work at all, and I have zero C or disassembly knowledge to help with the blobs editing to fix that, so i'll have to wait someone has a working solution if current kernel/device tree doesn't work.

Only issues I can think of, is mainly adreno blobs, stl port dependencies are already solved, an i know a few commits that I didn't merge yet because not needed as of now that might be required for N. Now, blobs might work perfectly on N, it entirely depends on what changes they made in Android N in term of calls.
[Nexus 4 Original Android Development] kldoc:
As some of you might have noticed, Omni recently added Snapdragon camera to its ROM on Android 6.

Until now, didn't really have the time to test the app. But I just was able to find a bit of time and test it. Results are real nice, till the point i'm actually going to add it to Nexus 4 builds on Omni 6. Focusing really works a lot better, and options are real nice. I hope you'll like it as much as I do. Commits should be merged within the next 2 days.

Have fun with OmniROM

P.S: I don't intend to remove stock camera, it's just another option

EDIT: Merge done, also added a commit taken from CM to fix flash sync issue.
[Nexus 4 Original Android Development] mrk2815:
ZTE axon 7 is what I may end up looking at .I just need to know how easy are ZTE devices to root and install custom roms like Omni on to. Also looking also at the asus zen phone 3 deluxe as well. These are two phones that I am looking that both have 64 Bit snap dragon 820 processor with 4 or 6GB of ram , plus adreno 530 graphics, 64GB of storage plus micro sd card supporting up to 128GB, 20mp OIS rear camera with laser focus and 8 mp front camera on zTE Axon 7 and 23 MP OIS camera with laser focus on Asus Zen phone 3 Deluxe plus 8 mp front facing camera on Asus Zen phone 3 deluxe . so I would like to know what you guys think of these choices. Also may also see what the nexus phones also look like this year as well . my budget is $500 US dollars and these fit the bill, I don't know what a 64 GB nexus will run and so that is why I am looking at these two choices.
[Nexus 4 Original Android Development] kldoc:
ZTE device ? Not gonna happen for me :p I know this brand more than i'd like being in China, and those are never easy to root, bootloader really often locked, and no kernel source.

Asus, until i see proper kernel sources for their Zenphone 3, i'm out.

Only true devices that have any hope to run great on AOSP so far are HTC 10, future Oneplus 3 and future Nexuses.
[Nexus 4 Original Android Development] mrk2815:
thank for the information. I guess I have my choices narrowed down , keep the nexus 4, find a used nexus 6 or 6 p till I can afford to upgrade to a newe nexus device.i have always been a nexus user ever since the nexus 1.So I have all my choices thanks for the confirmation.

---------- Post added at 06:55 PM ---------- Previous post was at 06:45 PM ----------

so between the two nexus that I have mentioned as blow out deals on e-bay, nexus 6 and 6 p, 64GB versions , which one would bea a better choice . seeing that there is nothing major as far as android N as far as hardware goes, both nexus 6 and 6 p would get android n and 6 p would get android o , but I prefer on custom roms, and so that is why I am looking at either models. since money is tight that is why I have not bothered to look at anything newe and that is why I have been keeping my nexus 4 around for this long of a time. if I can get a good 4 or so years out of a nexus 6 or 6 p through AOSp roms , then that will be enough to get me out of my tight money situation.
[Nexus 4 Original Android Development] kldoc:
I recommend neither of those, going for a Nexus, wait a few more month to get a Nexus with a s820 SOC, those are really awesome in term of performance and power consumption, Nexus 6 is too old, and didn't have much success, going with Nexus 6 is a bad idea IMHO. Nexus 6p is based on s810, and yeah, i can't recommend a phone that uses that SOC.

It's urgent to wait :p Oneplus 3 should be rather cheap, and they publish all sources then it'll be easy to buy (no invite required anymore), depending on what's the next Nexus, i'll go for Oneplus 3 or new Nexus (really hoping for a nicely equipped HTC Nexus).
[Nexus 4 Original Android Development] mrk2815:
thanks for the information. I guess I will do what you suggest . I will wait till I can get my hands on either a nexus device or even better a 1 plus 3. I think I have my choices and will be keeping that nexus 4 running for a bit longer till I can get my hands on either .
[Nexus 4 Original Android Development] kldoc:
I'm going the same way, Nexus 4 didn't have much to envy to Nexus 5 (slightly better soc, slightly better cam, and 4g), and then there hasn't really been a very convincing device to put Nexus 4 to retirement, that is, until Snapdragon s820 came, and that's the new generation, my hope is that new SOC can last at least as long as Nexus 4 did, and things are looking good on that side.
[Nexus 4 Original Android Development] kldoc:
I made one little mistake, stock camera is indeed replaced by Snapdragon camera, but believe me, for the best :)

And the commit i did merge from CM to fix focusing when shooting without tapping first also worked, it's now focusing normally :)
[Nexus 4 Original Android Development] mrk2815:
so will this new camera be in the nightly for this week.
[Nexus 4 Original Android Development] kldoc:
It's already in :p I'm not going to revert, Snapdragon camera replaces camera, and Omni devs are working on improving it :)

Beware that it also replaces the stock gallery.
[Nexus 4 Original Android Development] mrk2815:
any way that the camera can be improved on nexus 4 , i'm all for it.
[Nexus 4 Original Android Development] mrk2815:
some one had gotten a s7 in my family and I got their nexus 6 and can keep that for a bit till I know what is going with the nexus devices. There are strong report that Huawei is building the next set of nexus devices and not htc.if its not htc I don't want to touch Huawei, as I have had bad experiences with Huawei devices.
[Nexus 4 Original Android Development] kldoc:
They will build one, now, nobody knows what model, bigger one, or smaller one, or tablet, which is also due for a refresh.

HTC is certainly doing one, Huawei just confirmed they were making a Nexus device, but that can be lower end, higher end, or tablet ...
[Nexus 4 Original Android Development] kldoc:
Sorry folks, camcorder is broken on the new camera, will be fixed in tomorrow's nightly, thanks to an selinux commit taken from CM-13, sorry for the inconvenience.
[Nexus 4 Original Android Development] Thrikiller18:
Is the new camera app snapdragon camera from qualcomm or snap camera from cm?
[Nexus 4 Original Android Development] kldoc:
It's the qualcomm one, Omni rarely takes features straight from CM ;)
[Nexus 4 Original Android Development] kldoc:
Camera is fixed, working as intended :)
[Nexus 4 Original Android Development] fishears:
Just flashed this because I was looking for a custom 6 ROM that android pay would work with. Haven't flashed Omni since before 5. It's very nice. Thanks for bringing this up for us.

Is it known that the NFC tile won't show on QS? It's the only problem I've found. Not a big deal though, everything else is solid.
[Nexus 4 Original Android Development] kldoc:
I would guess it's a layout issue, QS screen being too large for our display, not much I can do about it actually ... But I'll ask about it, I have NFC always on actually, not a feature I really use, but it doesn't eat battery, it wouldn't change much having the possibility to disable it in QS screen IMHO
[Nexus 4 Original Android Development] fishears:
It's not important to me, just something I noticed. BTW it still doesn't show if i drag the tile to the first position so it seems to be something other than screen size...
[Nexus 4 Original Android Development] kldoc:
Ok, good to know, didn't test till that point, will check it out with team.
[Nexus 4 Original Android Development] kldoc:
Ok, found the culprit, got a fix, will merge it when i can find the time, somewhere this week :)
[Nexus 4 Original Android Development] kldoc:
I've just merged a commit to add a rule to sepolicy to allow the NFC tile, hopefully, this will be enough
[Nexus 4 Original Android Development] I.P:
It won't be a problem to edit an image, thanks for your explanations !
[Nexus 4 Original Android Development] I.P:
So, I did what you told me, I indeed have now a Google Now icon in my apps, then I installed the Now Launcher from Play Store but I still can't select it as default launcher, only Launcher 3 is there.
[Nexus 4 Original Android Development] herna:
Reboot your device, on the next boot, press home button and it will ask you to choose the main launcher.
[Nexus 4 Original Android Development] I.P:
For some unknown reason it's working now, thanks all !
[Nexus 4 Original Android Development] kldoc:
Hello folks, new update from AOSP is being merged, because of that, device tree and/or kernel tree might be broken, I'll make a test build ASAP to see what's going on, but in the meanwhile, unless you can help debugging, you should wait to build by yourself and stay either on an older build you did, or the latest build that is available in this thread.

Tank you for your understanding :)
[Nexus 4 Original Android Development] I.P:
BTW, I noticed that EAP/SIM seems to be available, I can't test it right now but it's a very good news for french people.
[Nexus 4 Original Android Development] kldoc:
Oh you're french ? I am as well (although not living in France). Using Free ? I am not sure EAP will work, radio can't change, worth the try, but not sure whether or not radio need some changes.
[Nexus 4 Original Android Development] I.P:
I knew you were :)

Anyway, I can't connect to Freewifi-secure so unfortunately this is not working out of the box :crying:
[Nexus 4 Original Android Development] kldoc:
Probably never will, it requires a lot more to work, including updated radio that we won't have ...
[Nexus 4 Original Android Development] I.P:
At least we now have a definitive answer to this question and we know there is nothing to expect from any ROM regarding this issue.

Thanks.
[Nexus 4 Original Android Development] kldoc:
To be honest, support on this from AOSP is totally unexpected, OEM do integrate it to some of their phones, but it would require a lot of work on the radio to enable this, and that means disassembling, only a few devs in Xda could do that, and on an already three years old phone, doubt one will give it a shot. I might be wrong, you never know, but I wouldn't place any hope on that ;)