yashsingh1/xdaforums huggingface dataset:
[Motorola Droid 4] Shplad:
Thanks. For some reason, the phone didn't want to go into AP Fast Mode until I tried again and again. Eventually, it did, though. I managed to restore Jelly Bean and I'm back at Square One. How sure are you folks that flashing LOS 13 again, this time with the proper Gapps and at the same time, will fix the problems I was experiencing?
[Motorola Droid 4] u.b.o.o.t:
If you follow the instructions _accurately_ and don't miss any details like "don't restart between flashing rom and gapps", it should work ;)

And, please, activate ROM-Slot 1 this time, just to be safe. Give it 900MB for system partition and at least 3000MB for data partition.

Regarding rooting vs. bootloader unlock - that's two different things. Bootloader cannot be unlocked on droid4. Bootloader is like BIOS on Computers. It is there to load the operating system AKA kernel. That's why the locked bootloader will always load stock kernel and just thereafter, safestrap will load the desired kernel via kexec mechanism.

Battery: 3,3V is almost dead! A full lithium battery should have 4.2-4.3V!
[Motorola Droid 4] Shplad:
uboot:

I followed one of the recommended videos for flashing. It was rootjunky's "How to install Android 5.0.2 Lollipop on the Motorola Droid Bionic, Droid 4 and Droid Razr" I'm not clear what I would do differently. The only difference was that I used LOS 13, instead of Android JB. I believe that video had me create ROM slot 1 and install in there, didn't it? What would I do differently?

W.R.T. the battery, do we mean short-term dead (just needs charging) or long-term worn out, as in, I need a new battery right away. I don't want to have more problems than I've had. Testing battery now, while it is still in phone after a good charge, it is measuring 4.19V. Is that okay?
[Motorola Droid 4] u.b.o.o.t:
I don't know that video, but despite what is said in the first post of this thread, there are no further "official" instructions anymore. There used to be a Droid4 page in Cyanogenmod Wiki, but it's gone since January 2017. Here seems to be a backup copy of it: https://zifnab.net/~zifnab/wiki_dump/Install_CM_for_maserati.html

Battery: I meant empty, not dead. You can't tell that from voltage. A dead battery will still charge to 4.2V but drain very quickly, i.e. its capacity is significantly reduced.
[Motorola Droid 4] Shplad:
Dang! So much for the idea that reflashing with proper gapps version would fix the problem. As soon as I got LOS 13 installed again, and I turned on WiFi...

"Connected, No Internet"

However, there does seem to be Internet access, in spite of this error.

Is this an Android issue?

There seem to be a lot of similar complaints on this forum page

"Wifi connected-no Internet"

https://forums.androidcentral.com/nexus-6p/629419-wifi-connected-no-internet.html

At least one person has reported it as a bug (but it was ignored due to not submitting logs) on the

Lineage Jira.

Does anyone know any solution to this?
[Motorola Droid 4] Shplad:
Oh, and I'm still unable to register as a user on the phone, so I'm guessing a whole bunch of things won't function at all?. Is this related to the "No Internet" thing, or is it a separate issue, cause this seems like a pretty serious issue to me. Can anyone tell me what things will fail to work properly if I can't register myself on the phone?
[Motorola Droid 4] u.b.o.o.t:
I never had any issues with Wifi. Are we talking about Wifi in your home? Do you have AFWall installed? Some public Wifis need browser authentification....
[Motorola Droid 4] Shplad:
uboot:

Thanks for chiming in again. I thought I had been forgotten. Yes, home Wifi. I'm using an Asus RT-N12 running TomatoUSB. This is known to be generally very reliable. And I've had not trouble with about 10 other devices connecting in the past.

No AFWall or any firewall installed, AFAICT. Whatever came stock with the gapps 6. The only other thing I've installed is Google Maps.

I see this post in Jira sounds similar to mine https://jira.lineageos.org/browse/BUGBASH-438

I also see what seems to be a multitude of other wireless issues. The problem with the error "Connected, No Internet" of course, is not nearly as important as the inability to register an email address/profile when trying to set up the phone. Anyone have any suggestions for that? It works fine in stock ROM (Jelly Bean).
[Motorola Droid 4] u.b.o.o.t:
How's your router configured? (Wifi encryption disabled, WPA, WPA2 or WEP? Channel? DHCP? Wifi standard B/G/N/A/AC?)

I never had issues with WPA2, nor with unencrypted Wifi.

Also, you might want to check wifi power saving modes and wifi country configuration. The latter affects available channels / frequencies.

But you say: connected, no internet - hence, wifi connection should be ok and it sounds more like a routing, DNS or DHCP issue.

There is a nice app called Fing which will tell you more about your wifi network (routes / gateways / network neighbourhood).
[Motorola Droid 4] Shplad:
WPA2 with AES. DHCP. Tried with no security, there is no improvement. Tried different channels. No improvement. Tried static IP, guess what result?

Like I said, it worked perfectly on the stock ROM, why should this be any different. Also, these things have been tried by others who report the same problem, and they made no difference. I'll try them if we run out of other options.

I think it's an Android issue. Like I said, Tomato is known for its stability.

Guess what? Now, late this afternoon, the phone started working on its own. It connects to email and allowed me to create my profile. Wha? Am still testing it to see what works and what doesn't. WiFi seems to be a bit flaky. Uber intermittently complains it can't talk to the network. Will test some more and get back to you.
[Motorola Droid 4] u.b.o.o.t:
Which LOS13 build do you have? I had no Wifi issues with any nightly build from last year up to 20170520. After that, I switched to unofficial LOS14.1., so I can't tell about newer LOS13 builds.
[Motorola Droid 4] Shplad:
I installed LOS 13 ver. 20170603 .
[Motorola Droid 4] belrei:
installed the latest LOS 13, can't turn on bluetooth. :(

Please help, has any body succeeded in using bluetooth?

Many thanks!
[Motorola Droid 4] Septfox:
I haven't read back in the thread much, just poked my head in to see if the ol' D4 was alive and kicking. What you have here is a flawed assumption.

The Droid 4 shipped with Gingerbread and was only ever officially updated to Jellybean. Or to put it another way, Motorola only ever built drivers for this device up to Jellybean.

To get it functioning with KitKat and beyond required increasing amounts of scraping together drivers from other OMAP4 devices, ingenious and likely fairly hacky approaches, and copious amounts of spackle.

That it functions with Marshmallow and even Nougat is nothing short of a miracle and indicative of [MENTION=3457922]stargo[/MENTION]'s sheer unyielding determination to keep the Droid 4 a usable and relevant device.

For those not keeping count, that's 7 major iterations of Android that the Droid 4 has successfully run, 4 of them without a single bit of help from Motorola. Very few other devices, if any, can boast such undying support from their devs.

Frankly, I would be surprised if a situation like yours didn't pop up every now and then.

...I have no idea how to actually fix your problem, just wanted to say all that.

I will say, though, that assuming Tomato wasn't/isn't the issue may also be a flawed assumption. I previously used a pair of WRT54g routers loaded with Tomato, and my D4 had intermittent difficulties staying connected while asleep. I don't remember ever fixing it for sure, I just took it for granted that a bit of my data would go towards syncing email and other maintenance that Google insists on running if it decided to act up.
[Motorola Droid 4] Shplad:
Well I certainly didn't meant to sound ungrateful. I very much appreciate the work done here. But I had no idea that this was the case. This was simply what was recommended here when I asked which version was best to try for the Droid 4. In fact, if I can get this phone to work as a phone, I wouldn't mind making a donation.

If the problem is my Tomato firmware, I can't find any similar anecdotes on the Web. Also, as I said, I am not having trouble with other devices (I've probably tried, in conjunction with other people here, at least 20 devices). If it's a problem with Tomato, why did the same phone work perfectly fine prior to the ROM upgrade? If you're saying there's a complex compatibility issue that involves both Tomato and the phone, then I would certainly concede that's very possible.

Do you have anything else concrete to try? I'm willing to do some testing to narrow down the problem. BTW, will this device now work on all the various GSM bands in Canada, or it still limited to only working on CDMA, like with the original ICS firmware?
[Motorola Droid 4] Septfox:
And I didn't mean to make you feel that you were sounding that way. I was just correcting the assumption that "it worked in X, it should work in Z" :)

This is part of the reason I couldn't fix mine. The thing of it is, while there are plenty of similar situations, both having to do with Tomato and not, finding one that's exactly the same is...unlikely. While the Droid 4 is still usable, it was never popular in the first place, let alone now. The odds of finding someone using the same phone, on Tomato, using the same router are rather bad, I think.

And yea, that's what I'm getting at. Probably a subtle bug or limitation in the phone's wlan drivers, triggering or aggravating a problem in Tomato.

I doubt it's going to make a difference, since I think it still goes through some routing, but: if you're still having intermittent trouble with it not being able to reach the internet, have you tried pointing the router's DMZ to the phone?

There's a GSM patch uhhhh....here, but I don't know if it still works for L and beyond. My understanding is that it works fine as a GSM phone once you get it that way.

You might be able to add any missing bands using CDMA Workshop or similar, but keep in mind that 1) the radio is a Motorola part that predates global LTE ones like Qualcomm produces, so there probably isn't hardware support for non-Verizon LTE bands in particular and 2) even if there's hardware support, the antenna geometry and a lack of calibration data will probably mean a flaky connection for unlocked bands.
[Motorola Droid 4] schmatzler:
At least in Europe, there is no GSM patch needed anymore with Android 6.

It will switch to it automatically.
[Motorola Droid 4] Shplad:
Thanks schmatzler. It did work so far. I only made one incoming and one outgoing call, but both times it seemed to work fine. The volume is a bit low. Is that a known issue or ?
[Motorola Droid 4] Careless_:
any way to improve the speed or response of this rom?

I just did a fresh install with gapps nano, and the screen hangs all the time on various screens, superSU doesn't launch, and the overall interface is abysmally slow.

is there a set of kernel aduitor settings I can tweak? this is practically unusable in its current state as far as my installation goes- but I didn't tweak anything or have any apps installed.
[Motorola Droid 4] u.b.o.o.t:
Try increasing extrafree to 16..32MB in VM settings via Kernel Aduitor.
[Motorola Droid 4] OGdroidster:
go to virtual memory in kernel auditor and change the the min free bytes to 3884 and then change extra free bytes to 34075. then change zram from 400 to 250. These values work for me. Also change both your proximity lines in build prop to a value of 25. Now for low memory killer I am using foreground app 72, visible app 90, secondary server 108, hiddin applications 126, content providers 144, empty applications 180 but low memory killer values you might need to lower some or increase depending how you use your device.
[Motorola Droid 4] Careless_:
both very helpful posts, uboot and OGdroidster.

thank you!

anyone having issues with the installation of the latest rom saying SU is not installed, and TWRP asking to install it before boot?

SuperSU did not load after the first time, and just showed me a black screen and locked the device up with a force close dialog.

I enabled root access in the dev menu twice, and still nothing.

UPDATE: nevermind, installed su addon and it's fine now.

can the original post have the "SU Addon" emboldened and placed under the link to the official builds download page? perhaps a "CAUTION: " or "NOTE:" prefix.
[Motorola Droid 4] Careless_:
mot.proximity.distance and mot.proximity.delay @ 25, right?
[Motorola Droid 4] OGdroidster:
Yea that's right.
[Motorola Droid 4] Careless_:
phone has been pretty snappy since the install.

thanks peeps!
[Motorola Droid 4] OGdroidster:
Your welcome :svetius:. I generally change build prop values within the zip before I flash then flash then install kernal auditor and set my settings.
[Motorola Droid 4] K_Meleon:
Very sad: I was more or less satisfied with LineageOS 13.0 in stock slot, had a stable system with all important settings I've done over weeks. After approx. 3 weeks of using it, it gets slower and slower. So, once in a month I updated the system via recovery (might be that wiping the cache is enough as well, but I like using the latest version), downloaded by the LineageOS updater. Last week it was time again for an update. I just looked at the date "2017-06-15", was happy, that it's quite new and triggered the download. For some reason I have to install it manually in safestrap but I already know the process, so I triggered everything...yes...without noticing that it's LineageOS 14.1 which is being flashed. ****! Without thinking I refused to install the root command and rebooted into 14.1 . Even without gapps LineageOS 14.1 is very slow. So I read about downgrading it. The bad thing is, that safestrap seems to be deleted for some reason. I had the same effect in some flash combination in March 2017. So now I can't do any backups, can't install safestrap (no root), can't install root and can't go back to 13.0 without flashing the stock ROM thus wiping everything. That's really bad!

Does anyone know a simple solution for it beside flashing the stockROM? Why is safestrap automatically deleted after flashing LineageOS 14.1 ?

Thank you for your help!
[Motorola Droid 4] Shplad:
Hi again everyone:

Forget my earlier statement that things were working fine. I'm having multiple problems.

1. The biggest problem is I can't even answer incoming calls. It rings, I see the flashing "ripple" pattern or whatever you might call it, but when I press the button in the middle, it doesn't pick up the call. That's a pretty basic problem.

2. When make outgoing calls, (can't tell if it happens with incoming, as that's not working yet) the volume (speakerphone or not) seems very weak. Is this an known issue?

3. Is there a way to make it so the keypad is ALWAYS showing when in phone mode? Having it constantly switch back and forth is seriously annoying. When I click on the dialer, I just want to make phone calls, not pop popcorn.

4. I keep getting a popup telling me that I have 0.00 minutes (or dollars, I forget which) left in my cellular account.

I have plenty of funds/airtime left.

EDIT: Changed last item to something more important

Thanks
[Motorola Droid 4] Careless_:
I can offer some suggestions to your concerns:

1. I haven't had an issue where I can't answer the call via the button press, but I have always had the issues with almost every android phone that is way passed its life cycle taking forever to show the actual incoming call screens, long after the ringer has begun. sometimes up to 7 or so seconds.

The only solution or way to mitigate the problem that I've found is to increase the LOWEST cpu frequency/mhz that the phone can be in during screen off or idle... if it's at 280mHz, bump it up to 320 or 380. This will allow the phone and screen to recover from a lower power state faster and be more responsive on incoming calls and associated interactions with the screen.

2. haven't experienced this yet. will investigate tomorrow.

3. Is this what you're referring to?:

- click the phone icon to enter the phone mode app.

- in the name search bar at the top, there are the 3 vertical sub menu dots, click there and hit settings

- choose display options

- check "show dialpad at start" to on

- close the app

The first time I did this, it didn't take effect until reboot. Not sure why. But now it works if I change back and forth.

4. No Idea, not a pre-paid user.
[Motorola Droid 4] Shplad:
[/COLOR]

Well, the behaviour has now changed. Now, when a call arrives, instead of getting the flashing button in the middle of the screen, I get a small status bar at the top of the screen. The right icon is answer call. It works, but it's so dang tiny there's no way I would pickup the call under stress, in a hurry, on the move, etc.

Thanks. I appreciate that.

No, I don't think so. I want the dialer to keep the dialpad on the screen, and not mimimize it, or put up something else.

I don't like all kinds of things flashing, moving, etc when I'm on a call.

---------- Post added at 11:36 PM ---------- Previous post was at 11:34 PM ----------

Okay, add one more problem. Motorola Device Manager is not working properly with Lineage 13. I can't seem to get it to talk to the phone properly. First, no popup comes up asking me which USB mode I want to use to connect the phone (are those popups still supposed to happen with LOS 13?)

Then, if I go into USB Debug options in Settings and select MTP, I can't really tell if it is connecting with the phone. I hear that badam badamm sound in Windows, Windows shows driver install, but no drive icons show up in Windows Explorer for the phones. I wanted to post a screenshot, but can't easily because I can't get files off the phone to the PC. GRRRR!

This is using Motorola Device Manager 2.5.4

Any suggestions?
[Motorola Droid 4] Careless_:
are you using a different dialer or phone app from the app store? There is nothing moving or flashing on the screen during an ongoing call. not sure what you're referring to.

And as for the white top-bar, that only shows up when you are using the phone, or when it is not in screen-lock or screen-off mode. If you have it locked or are not using the phone, the full dialer will show.
[Motorola Droid 4] Shplad:
I'm using whatever came stock with LOS 13 and/or Gapps I was recommended to install. Well, on my phone, there was originally a screen somewhat (but maybe not exactly) like the one attached here.
[Motorola Droid 4] Careless_:
that should only come up when you're not using another app or when your phone is locked/screen-off.

otherwise the white call bar is shown so as to not interrupt what you're doing.
[Motorola Droid 4] Shplad:
Okay. Is there a way to enlarge whatever icon/bar comes up. I'm not what you'd call nimble with my hands.

And how do I answer the call when that other screen (in the attachment) shows up? I tried pressing/swiping, nothing seemed to work.
[Motorola Droid 4] Careless_:
not sure, never tried.

to answer the call there is a phone icon and an sms icon. if you hit the phone icon it will answer the call.
[Motorola Droid 4] Shplad:
Actually, I only got (now I don't get this screen) a phone icon in the middle. No text or phone icons to the left

and right. But again, now, I'm just getting the status bar with those choices.

Any suggestions for my other problems?
[Motorola Droid 4] Careless_:
as I said, i only get the white incoming call bar when I'm using the phone and a call is coming in.

turn your lock screen on if it's not on.

turn your display off when you're not using the phone.

start looking at your phone app settings and your notification bar settings.

i've never had the same issue you're having, so that's all I can advise. start tinkering with settings.
[Motorola Droid 4] Shplad:
Careless:

Why would Turn your lock screen on....why would that help? I prefer to avoid the lockscreen. I find it a pain. I might use it if I had to.

Turning off the display when you're not using the phone. I'm not clear how that would help either. Would you please clarify for me?
[Motorola Droid 4] Shplad:
Hey Careless:

How do I do that frequency bump-up. Is this a quick procedure or does it involve something complex/lengthy?
[Motorola Droid 4] Careless_:
download "Kernel Aduitor" from the play store, there's a CPU frequency menu somewhere in there. pretty easy to figure out.
[Motorola Droid 4] kr3pt:
Hey guys, thanks for your work to keep this phone alive and updated. I have recently flashed 13.0-20170610-Nightly-masarati.

I have had 2 problems come up.

Firstly, Wi-Fi. When I try to connect to wifi at home or work I get 2 glyphs that pop up. The first saying "failed to save network", the second saying "failed to connect to network". If I keep trying to reconnect, sometimes it will succeed and say "connected, no internet" but then when switching networks, the information is not saved and I have to start all over again.

The second is media volume. I cannot get media volume to work, regardless of sound level. I have turned up all types of volume to test, and still cannot hear games, videos, or music.... alarms, ringtones, in-call, vibrate, system sounds, etc work. Just no media sounds.

Edit:

Figured this issue out. It was absolutely my fault. When I was experimenting with taking the battery out, i also removed a screw that apparently affects the speaker and I forgot to put it back in. What a stupid mistake to make....

Any insight would be appreciated. Thanks again.

Edit:

is there another OS or revision that I should flash instead? I'm not terrible knowledgeable with this stuff and I'd like to use this as my daily. My primary uses are texting, music via bluetooth, and snapchat(which works terribly, but I suspect that due to processing power). I did try Stargo's 14.1 but like many others, could not fit gapps
[Motorola Droid 4] Shplad:
kr3pt:

I'm a newbie at this too, just flashed LOS 13 (20170604-NIGHTLY-MASERATI) a week or two ago. But if you look at my earlier post, I reported experiencing the "Connected, No Internet" problem too. BTW, have you TRIED connecting? Because on my phone, in spite of the error, I still get an Internet connection.

Someone had already reported it on the Lineage OS bug tracker:

https://jira.lineageos.org/browse/BUGBASH-438

However, that person's bug report was not taken seriously cause he didn't include a log. I don't quite understand the log process, but I'm gonna try. Maybe if you also submit it a log and a bug report, with three bug reports, it might get fixed soon

How to Capture Logs:

https://wiki.lineageos.org/logcat.html

Lineage bug tracker login (to report bugs) is here:

https://jira.lineageos.org/login.jsp

That reminds me...I have no idea if I have ADB installed on my PC. Is it installed by, for example, the Motorola Drivers and Moto Device Manager? Not that I have that working properly, but...

Oh, Snap! I can't get the ADB to work, because my phone is not consistently cconnecting via Motorola Device Manager. So I'm in a catch-22. Can't report bugs cause can't create bug report. Can't create bug report cause Moto Device Manager is not staying connected. Anyone else have this problem. PLEEEEASE can someone look at this? Obviously I am unable to do so, unless someone can suggest otherwise.

Hope this helps.
[Motorola Droid 4] Shplad:
Okay, I wanted to add more to this, but I didn't want to make my last post any bigger, so here's another post.

First, part of what I've experienced with my USB connectivity problems is that I've been experiencing these:

MtpService restarting over and over again with USB connected to PC

https://jira.lineageos.org/browse/BUGBASH-417?

jql=text%20~%20%22usb%22

MTP Problems Nexus4, workaround

https://jira.lineageos.org/browse/BUGBASH-343?jql=text%20~%20%22usb%22

On the brighter side, I managed to install ADB and generate a log. Since I could not do this via standard USB, I enabled RNDIS (USB Ethernet) and that seemed to allow ADB to communicate with the phone. That being said, I'd love to see some of the above problems get fixed, if they haven't been fixed already.

Before I decide to post a logcat log, does it include any private info?
[Motorola Droid 4] Careless_:
[deleted]