yashsingh1/xdaforums huggingface dataset:
[Nexus S 4G Android Development] wickid_d:
bootloader recovery option mode? That could mean a couple of things.. If it's where you have the menu on the left and the little green android on the right, that's called fastboot, and what I ended up doing was getting the boot.img out of the zip, and flashing it through that.. I'm still trying to figure out why the updater script doesn't flash that by default.. but there's guides around for using adb and fastboot to do this.. if you're going to get into romming, this is an essential thing to learn..

---------- Post added at 02:24 AM ---------- Previous post was at 02:12 AM ----------

That doesn't really show that it's creating a persistent wake lock, that shows the phone app gets used a LOT.. I noticed you have airplane mode on in the screenshot, is that normally on? or did you just do that for the screenie? If you're on the phone a lot, that will drain the battery faster.. I can nearly kill a battery in a 45 min walk if I'm on the phone the whole time.. with nothing else on.. That's more Google's code than the rom.. I've noticed a bigger battery drain, since JB came out, from the phone app..
[Nexus S 4G Android Development] DarkEnd:
That's just it, I wasn't using the phone. At all.

I noticed in the performance settings that the time-in-state for deepsleep was 0. Then the battery stats pointed me at the phone. So I charged to 100%, switched on airplane mode, unplugged it and left it on the table without touching it for 6 hours. And then took this screenshot of the phone with a keep awake time of 6 hours (perhaps I should have clarified that better), and the time-in-state showed like 98% at 1000mhz.

I've since added xposed framework and wakelock terminator to block the phone from acquiring a wake lock at all. That's probably not a very good solution, but my battery life is great now (it actually puts the cpu in deep sleep), and the few phone calls I've gotten seemed fine.
[Nexus S 4G Android Development] wickid_d:
AAhhhh.. ok, yeah, that does clarify things. I may have to check into this xposed framework.. I've heard about it a couple of times now.. As for phone not taking a wake lock at all, I think you'll be ok. If you haven't missed any calls, then I wouldn't worry about it..
[Nexus S 4G Android Development] stealth658:
Anyone else having issues with root? Even after flashing SuperSU 2.00, I don't get any prompt for root processes. Btw the CM torch app works fine on this rom, it just doesn't work with the quick toggles torch button.
[Nexus S 4G Android Development] adityaxavier:
Thanks for the responses guys..

BTW i was trying to get OmniTorch running, and it seems it works only partially. Still got to work on it more..

Uploading the new build.

Build uploaded ! Try the torch app. It should be working just that it needs a long time for starting after boot. Try using camera with torch once to quicken it :)

Our kernel doesn't have /sys/class interface for Flash. So Torch app is utilising Camera interface. And it is known to be very slow.. Still i expected it to be working at least as fast as CM Torch, but alas its not :(
[Nexus S 4G Android Development] fathom614:
Thanks so much, downloading to try it out.
[Nexus S 4G Android Development] fathom614:
For some reason, it seems to break Netflix. Keep getting a timeout. Was having this issue with the 4.4.3 one as well. I've tried everything, but still a no go. Any suggestions? Also everything else seems good still going thru. There also is an issue with receiving voice mails.
[Nexus S 4G Android Development] adityaxavier:
Hmm, Sorry but i don't live in US to test Netflix. If you can provide me with the Logcat, i can check and let you know.
[Nexus S 4G Android Development] the1dynasty:
trying to flash this now... seems like its stuck in a bootloop... can't tell... is ART enabled by default? also, what kernel is everyone using on this?
[Nexus S 4G Android Development] Swamphound:
Working on flashing this for my son's device and have tried using both latest philZ and TWRP to no avail despite giving each boot 10 minutes and pulling battery and rebooting again. Downloaded and flashed Banks mini Gapps w/ google search and also flashed SuperSU 2.01 for good measure. Thank you for keeping crespo4g development alive and will stay tuned.
[Nexus S 4G Android Development] adityaxavier:
Guys without a logcat how am I supposed to find the issue?

However it is known that the first boot takes an incredibly long time. Mainly because the time taken to process the apps and framework.

Art is not the default in 4.4.4 and our rom. It is default in 5.0 which I would port once sources are out.
[Nexus S 4G Android Development] dwielunski:
I will definitely check that out if you are still working on this phone when 5.0 arrives. Thanks for all the work you've done.
[Nexus S 4G Android Development] adityaxavier:
I'll definitely work to port android 5.0 onto our nexus s 4g. The sources are well played out and would need quite few changes to make it adaptable for other versions. However I might need to work on syslinux being compatible.
[Nexus S 4G Android Development] the1dynasty:
thanks... i couldn't pull a log mainly because idk how to pull one when the phone is stuck in a loop... also, i left the phone for about 15mins and still never booted up... no worries... i'm running L on my N5 and i know ART is the default, i was wondering if you somehow made it the default on this ROM since i know my N5 took almost 10mins to boot the first time...
[Nexus S 4G Android Development] rsriram22:
long boot time fixed by flashing boot manually

I have experienced the 'long boot time' with the omni logo showing up but not doing anything happen. tried clean install, formatted data system partitions/ factory reset nothing worked.

Finally, I went into fastboot and

flashed the boot.img manually

and the system booted up in matter of seconds. (The boot.img was extracted from the ROM's zip posted in OP).

After the phone booted up fine, I went back to TWRP 2.7.1.0 and flashed gapps-minimal and the reboot was a breeze too (matter of seconds).

I am coming from stock 4.1.2.

Thought this would help someone stuck at boot logo (omni).

and, thanks OP. its a day old that i am on the july 1 build and things seem to work okay so far!
[Nexus S 4G Android Development] JohnCorleone:
Let me try this method because I haven't gotten past the boot animation yet either.

I rolled all the way back to 4.1.1 so I could tether 4G with WifiTether app but since I barely see WiMax as it is I might as well get current

Sent from my Nexus S 4G using Xparent Gray Tapatalk 2
[Nexus S 4G Android Development] netjetman:
Wake Problems

My wife's phone running the newest build has the issue where it won't wake. If you leave it alone, you'll look over and see the keys are lit up dimly, and when you try to wake it, it doesn't do anything. It requires pulling the battery.

Any config changes I can make?

Scott
[Nexus S 4G Android Development] jamesadalpiaz:
Heya, decided to play around with my trusty old NS4G and installed your rom. No problems on my end. Just wanted to know if you had kernel sources available. I'd like play around with it and maybe add some stuff to it.

EDIT: Nevermind, just noticed it's CM11 sources.
[Nexus S 4G Android Development] mathuaerknedam:
I'd have posted more, but I just recently got over the 10-post noob threshold, and wasn't allowed. Your work is definitely appreciated, and I intend to make a few [hopefully non-noob] comments.
[Nexus S 4G Android Development] mathuaerknedam:
The OP now says:

Does this mean that if I'm patient enough, the torch should work? I've not been able to get Torch to work no matter ow long I wait. This isn't a big deal for me, but if it's supposed to work (eventually), I want to report that it isn't (for me).
[Nexus S 4G Android Development] Setting.Out:
I have a torch fix for you.. Give me a few hours to get home.. ;)

---------- Post added at 07:41 PM ---------- Previous post was at 06:43 PM ----------

I used this in my CyanAOSP rom to have a working torch..

DOWNLOAD

This is a flashable zip, but you will most likely need to remove the original torch apk (or you will have two icons)
[Nexus S 4G Android Development] mathuaerknedam:
I removed the original and installed the zip, but now I don't have any Torch. I installed it again (from CWM recovery), just in case. No dice.
[Nexus S 4G Android Development] Setting.Out:
I'll re-upload the zip, I missed a folder.. Give me a couple minutes.. ;)

---------- Post added at 10:16 PM ---------- Previous post was at 09:37 PM ----------

Okay, fixed.. sorry.. :)

DOWNLOAD
[Nexus S 4G Android Development] mathuaerknedam:
New Problem: "The file you requested has been blocked for a violation of our Terms of Service."
[Nexus S 4G Android Development] Setting.Out:
Change web browser..

---------- Post added at 10:37 PM ---------- Previous post was at 10:32 PM ----------

Okay, I just tried the link, and it is getting blocked because it's now "private".. and it won't let me change it's privacy??..

Here's a new link..

DOWNLOAD
[Nexus S 4G Android Development] mathuaerknedam:
I was just about to post that I'd tested in seven browsers on three platforms, but I checked for a new link. :)

It installed fine, and the torch app works. This is probably a noob question, but is it expected that Torch won't light up until ~5 minutes after boot? I can tap Torch right after boot and it will eventually light, or I can wait a while and then it lights as soon as I tap it. I know there's a lot still going on right after boot, but I don't see the delay when using flashlight apps from Google Play.
[Nexus S 4G Android Development] Setting.Out:
The "app" should be instant, but if you try a quick tile it'll never work, as it's not linked..

---------- Post added at 11:49 PM ---------- Previous post was at 11:46 PM ----------

This is the Omni torch from the non 4g crespo and it had no issues in any ROM I tried..
[Nexus S 4G Android Development] mathuaerknedam:
Curious. The tile works, and the app and tile have the same 5min delay.
[Nexus S 4G Android Development] Setting.Out:
But only on initial boot?.. After that it's normal?..
[Nexus S 4G Android Development] mathuaerknedam:
Yup. After that everything works as I'd expect. Well, the SOS button doesn't toggle OFF the SOS signal like I'd expect, but I suspect it functions as intended.
[Nexus S 4G Android Development] mathuaerknedam:
Did you every try different kernels with this rom?

Has *anyone* been able to demonstrate that some or all NS kernels (or all CM-based kernels for NS) are compatible with NS4g? I'll probably do some testing here, using Setting.Out's thread as a starting point, but I'd like to know what has or hasn't worked for anyone else.
[Nexus S 4G Android Development] mathuaerknedam:
Crespo kernels work

I've been able to use Marmite 10.6, Matr1x 25 cfs and bfs, and Devil Kernel 20131025_VC. When I flash Devil kernel I see the odd message "Making marmiteInstalling Devil kernel", but it seems to work. However, neither of the Devil kernel apps I tried would recognize that Devil was running.

I tried flashing Guru 1.0, but it fails with 'assert failed: getprop("ro.product.device")=="crespo" || getprop("ro.build.product") == "crespo"' and installation aborts. I guess this isn't surprising, since my values are "crespo4g". What I don't know is if this is overly restrictive and crespo4g *should* also work, and if so, how I would go about changing the checks in the kernel zip. Maybe I should just try to flash the .img using fastboot on my PC or flash_image in my phone's terminal.

I also tried the four Air Kernel Weekly r350 kernels. While they flash without error, there are problems. JBN_BlueColor_NHB_CM and JBN_VDColor_NHB_CM booted, but failed to save screenshots. JBN_BlueColor_CM and JBN_VDColor_CM got stuck in a bootloop at "Android is upgrading... Starting Apps". When flashing the kernels I noticed a message that they were writing to /system, so I tried restoring a nandroid of /system, and that worked for JBN_VDColor_CM (which also couldn't save a screenshot). However, after flashing JBN_BlueColor_CM, /system couldn't be mounted. A reformat and nandroid restore of /system didn't resolve the problem, so I gave up. Even the Air kernels that worked didn't seem to leave much usable memory, so I'm not planning to revisit them and figure out what's wrong. I still have four working kernels to try with OmniRom 4.4.4. :)

There are still a few aosp-based kernels that require an extra step or two, and I've probably missed a few easily-flashed kernels that are worth a try. I've seen new 4.4.x rom releases for Crespo (like cm11 m9), but I've not gotten far enough to figure out how to extract a flashable kernel..

It's only been 24 hours, so I've obviously not had much of a chance to see how these work for everyday use. That comes next.

Sorry this is so long, I wanted to include enough detail for anyone who wanted to address the problems I've seen, for anyone else who wanted to try other kernels with this rom, and for my own future reference.
[Nexus S 4G Android Development] Setting.Out:
Use my guide in flashing boot.IMG and you can flash guru/cm/Slim's kernels without the device error..
[Nexus S 4G Android Development] mathuaerknedam:
Yup. That's where I learned about the option to use flash_image in a terminal. Those kernels will be in the next wave.
[Nexus S 4G Android Development] the1dynasty:
parents came over and i had time to try this and THIS method worked perfectly!!
[Nexus S 4G Android Development] mathuaerknedam:
I ended up using Matr1x and Marmite 10.6 only for a day or two because of general stability issues. Most significantly, the camera would crash, which seems to be fairly common on bigmem kernels. I was able to use [URL="http://xdaforums.com/showpost.php?p=54215134&postcount=8512]Marmite 10.3[/URL] for much longer, but I ended up switching to Devil kernel because I saw less FCs and less occasional weirdness.

Unfortunately, when I attempted to use flash_image to try the just released Guru 1.0.1, It returned write errors. I got the same errors with flash_image on the kernel bundled with this ROM. After booting into recovery and reflashing this ROM, the phone would boot directly into recovery. CWM logged badblocks when formatting /boot, and I got write errors with fastboot. Unsurprisingly, the latest TWRP doesn't help. As far as I can tell, my phone is now toast, though it seems odd that the boot partition is the only problem. I guess I'll soon be buying another Nexus S on eBay. Good thing they're relatively cheap, I got less than 6 months out of my first. :)
[Nexus S 4G Android Development] SpaceFuzz:
Build 12 /4.4.4 Looking great

I just flashed Build 12 and so far everything is perfect--even torch (speedy and responsive). I love that there's still a few of us pushing our old Nexus S 4G well beyond their expected lifespan--much like the Spirit and Opportunity rovers on Mars...well at least Opportunity (still going strong). Anyway, that's the way I look at it.

Many thanks to adityaxavier for his extensive work and to those of you contributing and supporting!
[Nexus S 4G Android Development] mathuaerknedam:
I finally picked up another Nexus S. After a factory reset and flashing this rom, I was stuck in a bootloop. I ended up leaving it for at least 15 hours, so I don't think I was just being impatient for the first boot. :) After trying several different things it worked with: Factory reset, flash this rom, flash Guru 1.0.1. Having done that, I do remember needing to manually flash the boot.img in the past (It's suggested in post #48). Someone suggested maybe this was a CWM problem and wasn't necessary with TWRP, but I can confirm it didn't work with either.

Surprisingly, Torch worked out of the box, from the app or tile, and without any delay. This time I have a new TWRP, SuperSU, and PA-GApps Pico, but I wouldn't expect any of those to make Torch work better than before.

[MENTION=3245977]adityaxavier[/MENTION], Now that BaNkS GApps have been officially "transitioned" to PA-GApps Pico, you may want to update the First Post. Thanks for all your work!
[Nexus S 4G Android Development] mathuaerknedam:
It would probably also be good for the FP to mention the (possible) need to manually flash boot.img.
[Nexus S 4G Android Development] dwielunski:
Hey man are you still around?
[Nexus S 4G Android Development] mathuaerknedam:
lockscreen widgets?

Does anyone else have Dashclock or other lockscreen widgets working?

I can get Dashclock to work in daydream mode, but not on the lockscreen. As far as I can tell, I should be able to select "enable widgets" in "Settings -> Security", but that doesn't exist for me. I have a vague recollection of seeing that before, but maybe that was in stock before I flashed the rom. If it works for anyone else, maybe I've disabled/frozen/etc something important, but it seems odd that the setting would be missing entirely.
[Nexus S 4G Android Development] mathuaerknedam:
I've dropped Guru 1.0.1 for Devil. I was having problems with all communication (calls/text/data/wifi) silently failing even though it claimed to be be connected. A reboot and I'd start receiving notifications of everything I'd missed. I also had a few occasions with whole phone locking up, or with spontaneous reboots.
[Nexus S 4G Android Development] mgreene613:
Could someone please post an archive of this crespo4g rom? I can't find any 4.4.4 roms still online anywhere. Thanks in advance!
[Nexus S 4G Android Development] hauckk@sfreserves.org:
best spot to find custom roms with working download links for this device is here https://plus.google.com/u/0/communities/118078408170605236116

i have links to afh mega google drive couple other hosting sites on this google plus page i made couple months ago
[Nexus S 4G Android Development] mgreene613:
And thank you once again!

In addition, I would also appreciate if anyone has access to the OmniRom 4.4.4 Unofficial Nexus S 4G build in this thread.
[Nexus S 4G Android Development] jksyankeesrock:
Google+ is dead :( Do you think you could find another way to host the files?
[General Paranoid Android Discussion] dakoellis:
Hello all,

I am trying to get voice+ working, and I am almost there I believe. Cherry-picking from gerrit gives build errors, so I put the changes in by hand, and made a few more changes I found in the cm11.0 branch for SMS middleware, and got it to build. At first, if I installed the voice+ apk, I was getting permission unavailable: INTERCEPT_SMS, but now i get CANCEL_NOTIFICATIONS. The only reference to that permission I have seen anywhere is in the babel apk, so I'm wondering if it is necessary anymore in 4.4. anyone have any insight?

TIA
[General Paranoid Android Discussion] TOWWTC:
Shameless bump
[General Paranoid Android Discussion] Pirateghost:
Bumping a thread from a year and a half ago? That doesn't even relate to paranoid Android?
[About XDA developers] natan69:
can some one here please help me this is driving me mad for days now i have been looking thro the forums at some of the posts how to set up tomtom 5 and how to setup the gps bluetooth receiver i have followed all instructions how to but iam not getting any where tomtom is installed Ok the gps control panel is installed but i cant seem to get any blue tooth com ports to show up in tomtom apart from

qct data interface

RIL on com6

com7

serial cable on com1

Ir on com3

if i rember when i had it installed on my xda2i when i went to tomtom and

bluetooth other then com ports i could pick from tow bluetooth coms 5 & 6

this really is getting to me now i do believe it possible to do it there guys selling the info on ebay with pictures of it running on the XDA exec but i just cant seem to do it

please i would be so greatfull for any help i only got the phone last week i like it
[About XDA developers] sidd:
TomTom & Bluetooth GPS

Hi there,

I am just guessing but give it a try, as i am using a cradle based GPS device bcs i wanna use the bluetooth headset as well during drive.

1. Try to first pair your Bluetooth GPS device with ur phone.

2. Once pairing is done, start TomTom

3. Goto ""ChangePreference->ShowGPS Status->Configure->Other Bluetooth GPS.

(Com1 is for the wired NMEA GPS device)

Your phone must within the connection of ur Bluetooth GPS device, now try BLUETOOTH SERIAL PORT Com5.

Try if its help

Sidd
[About XDA developers] natan69:
Re: TomTom & Bluetooth GPS

Hi Sidd,

I have tried that. The problem is that the phone won't allow me to connect to any other port than 8, 4 and 0 and in the Tom Tom menu there is no option of chosing those ports.

Thanks for advice anyway.

Rob
[About XDA developers] sidd:
Hi Rob,

Make sure ur Beam is OFF

Start->Settings->Connection->Beam

MUST be UN-TICKED.

(By the way I am in London, where r u?)
[About XDA developers] sidd:
One more idea :idea:

1. Pair ur GPS

2. Once pairing is done, switch OFF ur phone's bluetooth (bcs ur phone is engaging the com ports), do not switch OFF ur GPS.

3. Now soft reset ur phone, make sure the Bluetooth is still ON

4. Start TomTom, see if there are more ports now. Try 5 or 6

GoodLuck

Sidd
[About XDA developers] natan69:
Hi Sidd,

Thanks for another piece of advice but unfortunately that did not help either :( My Beam is OFF and I've tried the way with soft reset but that did not work either. I am getting desperate here :)

My device is XDA Exec and I am using (or at least trying to use) a BT GPS receiver with it. After pairing devices everything seems to be all right except the fact that I am not able to assign any other ports than 0, 4 and 8 to be used with GPS receiver. As I mentioned earlier there is no option of choosing any of these ports in TomTom5 software with the only options as follows:

qct data interface

RIL on com6

com7

serial cable on com1

Ir on com3

Maybe you know any ComPort Manager software I could use to assign the Bluetooth connection to a specific port?

As far as my location is concerned I am in Hayes - that's Zone5 near Heathrow airport.

Cheers,

Rob
[About XDA developers] sidd:
Which TomTom u using, is it the legal version or ****. Do u wanna meet, so we can try my version?

I am in Pinner, do u drive?

Sidd
[About XDA developers] malghamdi5:
Hi all,

I have exactaly the same message and problem.

Natan69

Please if you found a solution help me. i installed my tom tom today so I expect that you may solved your problem by now.

please help me you have been in this situation and you know what i am through.

Thanks
[About XDA developers] bizao:
Hi all,

I had exactly the same problem than you guys...

But first of all I couldn't even install tomtom5.

The version 5.0 crashed in every attempt to install and version 5.21, simply crashed when choosing the map.

Well, I'll try to put every step I did to get it working.

First of all, had the BT GPS paired with K-JAM and set new outgoing port COM6 to it. (in my case I only had COM6 or COM7).

1 - With the full copy of 5.0 version on HDD, replaced setup.exe with the one from the 5.21 update (this allowed the setup for 5.0 to run, and is the one that has the gps.cab file);

2 - Updated with version 5.21;

3 - Copied the map to \Storage Card\

4 - In Windows created the file CurrentMap.dat using Notepad containing: & \Storage Card\XXXX-Map\ (where XXXX is the map name. the final \ is mandatory);

5 - Copied the voiceXX.cab to device and run it;

At this point I was having the same problem (both COM6 nor COM7 appears in tomtom)

6 - Downloaded the GPSInfo_WM5.zip attached here and installed it;

7 - Executed this program, configured it to COM6 (port I had configured BT GPS to work with) selected the correct baud rate (very important, it's on the user's manual of the BT GPS) and click Start GPS to check it's response to the program;

8 - Click Close GPS so that the COM port was not in use;

9 - Started tomtom, edit the settings and chose Other Bluetooth GPS.

Now the ports COM6 and COM7 was there!!!!

10 - Chose COM6 and in 10 seconds tomtom was trying to aquire satelites.

I hope this helps you all. I spent weeks trying to make tomtom work and I got it working yesterday.

BTW, excellent forum. If it wasn't this forum (and another one only in portuguese :D I was still mad with this thing.

Good luck in your adventures.

Cheers,

Nuno.