yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] Setting.Out:
I was reading that Mokee ROM had multi-window, an option Omni used to have, is this feature available yet or capable on our device?.. I haven't been able to flash either ROM to test it, but if Mokee has it, could it get merged?
[Nexus S Android Development] notbrodie:
new build running fantastic. all apps install perfectly, art working, no apparent bugs.

Sent from my Nexus 5
[Nexus S Android Development] Rushabh22:
Found One Bug

First Your 10-1-2014 Build is running good starting with Forse close..

First Bug is Root is Not working ..So, i flashed two times latest CWM flashable Zip but does not help ..

After that i reroot My device Still it's give me this Message.. :confused:

Any other people are facing problem regarding Root..
[Nexus S Android Development] Rushabh22:
In developer options there are no any Root access ...
[Nexus S Android Development] teoserio:
Installed superSU without issue here

Inviato dal mio Nexus S
[Nexus S Android Development] Rushabh22:
Don't know What's a problem..??

Tried Many times but no luck So, i switch back to CM11..
[Nexus S Android Development] lagloose:
Don't know what you're doing.

Use LATEST CWM and...

- flash ROM

- flash Gapps

- reboot and set up your device

- reboot to recovery

- flash this: http://download.chainfire.eu/376/SuperSU/UPDATE-SuperSU-v1.89.zip?retrieve_file=1

- reboot

- look if you have a 'Supersu' app. If not, download it from Playstore (Supersu fron chainfire)

Greetz
[Nexus S Android Development] Rushabh22:
Hello,

O.k. root is working fine but in quick setting torch tile is not working..

Other things are working fine..

Thanks..
[Nexus S Android Development] Maxxd01:
Hi Guys,

How in the smoothness and stability when comparing to CM 10.2 (4.3) ?
[Nexus S Android Development] Maxxd01:
I flashed the SuperSU through CWM, and installed the 1.86 update through Play, but it says that I do not have the Su binaries installed. What can I do ?
[Nexus S Android Development] Maxxd01:
Hi,

Love this ROM, but Torch from Quick Settings don't work. Any idea?
[Nexus S Android Development] lagloose:
Seems that Torch in Quick Settings doesn't even trigger an event in logcat. So it might be a problem in Omni sources. Just wait until Friday. I will than release next build with hopefully working Torch in Quick Settings...
[Nexus S Android Development] Setting.Out:
...but I want to flash it now.. lol.. :)
[Nexus S Android Development] Maxxd01:
Thanks lagloose.

Also, it will be awesome to a have a 2g/3g toggle.
[Nexus S Android Development] lagloose:
:) As i said in my first post.... i won't implement any 'special' functions which are not part of original Omni-Rom functions. I'll only optimize some things to get it running better on our devices. So if you want a 2g/3g toggle ask the Omni-Dev's :)

For those who want to 'follow' what's going on at Omni, you can have a look here: https://gerrit.omnirom.org/#/q/status:merged,n,z Every addiition and fix which is not 'device' specific should find it's way to our release...

Greetz
[Nexus S Android Development] Maxxd01:
Yes, I was afraid that you were going to say that :P
[Nexus S Android Development] lagloose:
New build is up !

Greetz
[Nexus S Android Development] Setting.Out:
I lost USB connectivity.. :( it worked fine on CM based roms, it stopped on Illusion ROM, back again after I flashed CM, and gone again with Omni..

Other than this, very nice, fluid and fast... No other issues to report.. ;)

**Edit**

I had to pull the battery because it wouldn't wake up.. The soft keys would light up but the screen stayed black.. Waited five minutes and nothing..
[Nexus S Android Development] teoserio:
Everything ok here. Torch tile still not working. Thanks lagloose

Inviato dal mio Nexus S utilizzando Tapatalk
[Nexus S Android Development] Maxxd01:
The same happened to me with the old build..
[Nexus S Android Development] teoserio:
I9020 or i9023?

Inviato dal mio Nexus S utilizzando Tapatalk
[Nexus S Android Development] Maxxd01:
I9023

---------- Post added at 10:55 AM ---------- Previous post was at 10:33 AM ----------

Any ideias to prevent this from SOD?

Maybe another kernel?
[Nexus S Android Development] Setting.Out:
I've been trying to prevent SOD (System of a Down) for a while.. http://www.youtube.com/watch?v=CSvFpBOe8eY

;)
[Nexus S Android Development] lagloose:
Own kernel seems to still have some problems. Probably goin to make an update release with CM kernel again...

Gesendet von meinem Nexus S mit Tapatalk
[Nexus S Android Development] lagloose:
Just did a test build with prebuilt CM kernel...

For some reason, switching to Art runtime doesn't work anymore. Regardless of compiled or prebuilt kernel. I'll watch Omni developement and have a look if this is a known problem. As soon as this is fixed, i'll create a new release.

Greetz
[Nexus S Android Development] Setting.Out:
Take a look at Slim's kernel.. It is aosp, but based on cm
[Nexus S Android Development] lagloose:
Thanx for the hint, but i don't think this will help. My guess is that it's related to permission changes in Omni Vendor tree...

Greetz
[Nexus S Android Development] Maxxd01:
There's any other bug-free kernel that we could use in the meantime?
[Nexus S Android Development] Setting.Out:
Follow the link in my signature.. I just posted a section on KitKat kernels and how to install them.. :)

But I don't know if a new kernel will fix it??
[Nexus S Android Development] teoserio:
Battery life record for me on KitKat and since ICS rom at all:

Interactive / ROW - 200/1000 (Devilkernel)

1d 2h with 2h and nuts of screen ON (Auto Brightness)

36% remaining when charged to full again.

Normal use, not intensive but texting and browsing in the 2hours of ON screen. No call at all and GPS on "Battery" under Geo settings
[Nexus S Android Development] lagloose:
As promised, new 'in between' build5 because Omni added the 'OmniSwitch' App. ART runtime should work again.

Greetz
[Nexus S Android Development] Maxxd01:
Thanks.

Can we do a dirty install?
[Nexus S Android Development] lagloose:
Looks like there are now problems with camera...

Concerning gerrit, Omni team has definitely changed some things in libcamera. I'll watch what they are doing and create a new build as soon as i see commits, which should fix camera problems.

Greetz
[Nexus S Android Development] teoserio:
No camera problem here on your latest version. Dirty flashed, everything working also omniswitch

Inviato dal mio Nexus S utilizzando Tapatalk
[Nexus S Android Development] lagloose:
Ok, thanx for info.

Anyone with camera problems in latest build ?

Greetz
[Nexus S Android Development] lagloose:
build 6 is up.

Next release in 2 weeks...
[Nexus S Android Development] Setting.Out:
That was quick.. ;)
[Nexus S Android Development] tricampeao23:
Screens please?
[Nexus S Android Development] notbrodie:
it's vanilla omni, which looks like stock 4.4.2. if you still require some screens, check out any official omni thread
[Nexus S Android Development] teoserio:
Little thing here, omniswitch doesn't stick On when enabled. I dirty flashed over a previous version so could be me

Inviato dal mio Nexus S utilizzando Tapatalk
[Nexus S Android Development] lagloose:
Guess it's either a problem with Android memory management killing Omniswitch or Omniswitch itself. Did you configure High Mem mode ? Than try reverting back to:

ro.config.low_ram=true

ro.config.max_recent_tasks=10

ro.config.max_cached_apps=24

ro.config.max_starting_bg=1

and look if autostart of Omniswitch works...

Greetz
[Nexus S Android Development] teoserio:
I'm already with this setting, build prop is set this way but no luck.

I'll wait for your next version, hopefully this feature will have better management also for low ram devices in further Omni sources.
[Nexus S Android Development] lagloose:
Did a new build today. Unfortunately problems with boot loop. Will wait until tomorrow, sync latest Omni sources and make a new clean build.

Will release ASAP...

Greetz
[Nexus S Android Development] lagloose:
No luck...

Problem seems to be more serious than thought. I've no idea at the moment. Obviously this is a general problem with more devices. I already wrote in Omni forums. So let's see if they have an answer to the problem.

That means: New release delayed for unknown time period, Sorry...

Greetz
[Nexus S Android Development] teoserio:
Hopefully this will be fixed soon. Take the time that you need

Inviato dal mio SM-T211 utilizzando Tapatalk
[Nexus S Android Development] lagloose:
Problem found. New release is out !

Believe it or not, the problem was the new bootanimation. Never thougth that a wrong or defect bootanimation can have such an impact. But Hey!, you can learn as long until you have eleven fingers :)

Greetz
[Nexus S Android Development] teoserio:
No that's a shame! New boot animation is wonderful! :p Build 7 in download now

Edit: wow! everything ok after a dirty flash (only wipe cache and dalvik).

Many many update from sources in this build.

Updated Omni-Switch (with new App icon), center clock, date on status bar, back to kill button (maybe this were already there)
[Nexus S Android Development] Setting.Out:
Downloaded.. Check

Installed........ Check

Booting......... Check

Awesome...... Check

Great work on this.. :)

I'm very glad that you help support our phone.. :)
[Nexus S Android Development] Maxxd01:
When someone calls the screen takes a lot of time to turn on (more than usual on all other roms).

Is this a configurable setting?
[Nexus S Android Development] DarkShadow69:
I'm also having the same issue.
[Nexus S Android Development] lagloose:
http://xdaforums.com/showpost.php?p=50582983&postcount=8

As soon as this is merged, i'll create a new release.

Greetz
[Nexus S Android Development] lagloose:
Commit was merged. build 8 is out. This build was created 'blind' because i don't have my Nexus S here at the moment. So do a backup before flashing. Just in case...

Have Fun
[Nexus S Android Development] Setting.Out:
..Sorry, took me a bit to get a chance to try it.. Really like the new bootanimation,.. It booted just fine,.. The camera keeps F.C.ing.. everything else looks good.. :)

Fixed the camera.. with a wipe and reboot.. :)
[Nexus S Android Development] tricampeao23:
Do you use the stock kernel with this ROM?
[Nexus S Android Development] Setting.Out:
Only for the first test... Then I use Devil..
[Nexus S Android Development] lagloose:
Expect new build on Monday...
[Nexus S Android Development] lagloose:
Build 9 is up.

Compiled and only checked installation and booting. But it should be ok.

(@jack.ba.so: You should train yourself in patience :) ... )

Greetz
[Nexus S Android Development] notbrodie:
so, i've been running the omni builds on my legacy devices (crespo and wingray). i just updated to build 9, and after finishing restoring all my backups, and rebooting, everything came up peachy. i then activated art and now my device is boot looping.

this is less of a bug report and more of a warning to anyone else who may be contemplating art on crespo. don't do it.
[Nexus S Android Development] tricampeao23:
Amazing rom! But...it is possible BLN working in this rom? Thanks!
[Nexus S Android Development] lagloose:
New build next Monday....
[Nexus S Android Development] lagloose:
build 10 is out...
[Nexus S Android Development] tricampeao23:
How I can install the last update?

Enviado do meu Nexus S através de Tapatalk
[Nexus S Android Development] teoserio:
I'm dirty flashing over and over, since build 2 or 3, without creating issue or bug.

Inviato dal mio SM-T211 utilizzando Tapatalk
[Nexus S Android Development] Setting.Out:
I was wondering if I could get a copy of the kernel you built based off Devil that was in one of your first builds.. :) thanks
[Nexus S Android Development] lagloose:
Expect new build at end of April...

Gesendet von meinem Nexus S mit Tapatalk
[Nexus S Android Development] lagloose:
New Google camera crashes Herr when switching to Video. Anyone with same problem ?

Gesendet von meinem Nexus S mit Tapatalk
[Nexus S Android Development] Setting.Out:
Yes, its very buggy..
[Nexus S Android Development] teoserio:
Is it hw related?

Inviato dal mio SM-T211 utilizzando Tapatalk
[Nexus S Android Development] lagloose:
Dunno... Don't have much time at the moment. Hopefully Omni team fixes that...

Gesendet von meinem Nexus S mit Tapatalk
[Nexus S Android Development] lagloose:
Build 11 is up...

Again a 'blind' build. So do a backup before flashing. Please report back here if there are problems..

Greetz
[Nexus S Android Development] R-TEAM:
Hi,

nice ROM - use it on my old handy (in use by my girlfriend ;) ) and have an question ...

I used before Devils ROM - but it looks the development is stoped ... and i need to try an KK ROM ...

It is a bit unclear - if you use the devils kernel on this ROM as base ?

And if this "yes" - if the kernel you use newer than devils kernel from 25.10.2013 ?

Or would you suggest Devils kernel as an replacement over the ROM kernel ....?

As i dont know, if you use an newer version of devils kernel, the same version as 25.10.2013 but modified, an older version modified or an other kernel ..

(i dont need to flash an kernel who is older/an bad decision ....)

Regards

R-TEAM
[Nexus S Android Development] teoserio:
Another perfect dirty flash

Inviato dal mio SM-T211 utilizzando Tapatalk
[Nexus S Android Development] Basti667:
I Love this Rom!!!! The Rom is better than CM11!!! I hope for more Updates :D
[Nexus S Android Development] lagloose:
Just here to say, i'm still there...

Omni team is working on some new features at the moment. Will wait until they are ready because it doesn't make really sense to update on a 14 day period now. However, probably new build in mid of June...

Greetz
[Nexus S Android Development] lagloose:
Good news for the next release. http://www.xda-developers.com/android/todays-omnirom-nightlies-now-based-on-android-4-4-3/

Unfortunately i've to tell you that i will probably switch over to a Moto E in the next month. So one or two more new builds and than there won't be any more from my side....

Greetz
[Nexus S Android Development] Setting.Out:
NOOOOOOO!!!! :( I hope you enjoy your new phone, though you could keep the NS and build for us.. ;)
[Nexus S Android Development] Basti667:
PLZ more NS builds.

Gesendet von meinem Nexus S mit Tapatalk
[Nexus S Android Development] lagloose:
After some compilation problems build 12 is up now.

Report back here for any problems.

Enjoy 4.4.3 ;)
[Nexus S Android Development] g33k0 b3lk0w:
Tested the rom, indeed it's a fast rom with a several extra options, I just miss the theme engine from cm11 and it would be perfect :D definitively one to watch :D
[Nexus S Android Development] Setting.Out:
Nice job on this... ;) even stock it's quite smooth, and is amazing modded..!! I changed to Slim's kernel, odexed it and added a few tweaks and it really flies now.. ;)
[Nexus S Android Development] g33k0 b3lk0w:
Can you post that one :D
[JAM, MDA Compact, S100 General] emil73:
Hi,

does anybody have any recommendations abt bluetooth gps reciever?

Example: http://www.oncoursenavigator.com/item.aspx?itemid=6009

What is important to think abt when you buy a GPS reciever?
[JAM, MDA Compact, S100 General] mrwell:
Royaltek RBT-2010...

SirfIII, 17 hrs battery, small, light and cheap.... marvellous! :D

A week with it and I'm still astonished about the skills of this GPS.

Look for reviews of it and check it!
[JAM, MDA Compact, S100 General] emil73:
Thanks for the tip!

Googled but only got results in: spanish, italian, russian or german sites!!! Don´t know any of these languages.

My guess is that it´s called something else in other countries. Anyone knows?
[JAM, MDA Compact, S100 General] oltp:
I've got one like this Oasis Media Bluetooth GPS Receiver: € 79,-

www.pdashop.nl probably in others shop as well

M
[JAM, MDA Compact, S100 General] borgs:
I can recommend the Holux GPSlim 236. It lasts about 10 hours, is small, light and very good at acquiring and keeping a signal (it's SirfStar III).

Generally you should go for a SirfStar III these days, especially if you want to use it in cities with tall buildings or out hiking in woods.

There is one slight problem with them however. For car mode you should really engage static navigation mode (this prevents the map rotating or recalculating when you are travellig very slowly or stopped). But for hiking and geocaching you really need to have static navigation turned off. There is a windows app that can switch it on or off but I've found that the pda app to do the same doesn't seem to work on my setup. I therefore use mine with static navigation turned off and get the occasional recalculation and map spins.
[JAM, MDA Compact, S100 General] emil73:
Thanks for your reply!

Are there differences between recievers considering static navigation mode? What I mean is if it´s in the software you do the setting or if you change directly at the reciever unit?

Been looking at this one;

http://www.dustin.se/DustinPictures/PDF/G/5010079858.pdf
[JAM, MDA Compact, S100 General] oltp:
Nice one, how about the price?
[JAM, MDA Compact, S100 General] emil73:
In Sweden the best price is abt 125 euro. Plus delivery costs.
[JAM, MDA Compact, S100 General] oltp:
Hmm,

That's about the same price I paid 8 months ago for my GPS, simular to the Oasis one I posted. A collegue of me bought a SirfStar III GPS 2 months ago for around €160, you're deal is much better (depending on the shipping costs). We tested both devices & his device got a lock on more satellites & quicker as well.

So it's up to you whether you want to pay twice the price for the better GPS. Usually my GPS works fine even in cities, but I guess a SirfStar III chipset will be much more capable with tall buildings. I'd go for a SirfStar III chipset, when I had to buy one now & knowing my own experiences.

Regards, M
[JAM, MDA Compact, S100 General] borgs:
Some manufacturers of SirfStar III GPS may provide their own software for switching between modes - but they may not. The software I use on the PC is provided by someone at SirfStar I think. As I said it works fine on the PC but obviously you really need it on your pocketPC. So far I haven't found any software that will change modes on the pocketPC - I have software but it doesn't seem to work. Maybe someone here can suggest pocketPC software for switching modes?

At the moment I leave mine with static navigation off and it doesn't have too much of an effect on car navigation where I drive.

The PC software seems to allow you to also alter the signal strength at which a satellite's data is disregarded. Upping this a little may help with the problem at the slight disadvantage of making the receiver a little less sensitive. I think you could lower it a reasonable amount and still have a sensitive receiver - mine works fine in the glovebox and I can get a fix in the middle of my house - that's how sensitive they are!
[JAM, MDA Compact, S100 General] mrwell:
Look on manufacter page http://www.royaltek.com/content/view/97/27/

about the Royaltek. It's in english (or Chinesse :lol: ) and you can search there for a distributor in Sweden.

Good luck!
[Moto X General] jideay:
Has anyone simplified the root process yet for 4.4?
[Moto X General] MaKTaiL:
For Locked Bootloaders: No.

For Unlocked Bootloaders: TWRP + SuperSU, can't be more simple then that.
[Moto X General] jideay:
OK thanks. I asume unlocking the bootloader is part of this thread? It's a bit much for me.

http://xdaforums.com/showthread.php?t=2538896

I used wugs on my Nexus 10, and it was a breeze.
[Moto X General] Darth:
That's the problem with tool kits... They automate everything, you don't learn anything, and you're putting your device in their hands.... Just hoping all goes well.

I recommend doing everything yourself... The hard way I guess.. . And stay away from tool kits. ;)

After you get through the steps, and again... And again... It all becomes a breeze... And you know exactly what you are doing to your device.

Sent from my Moto X cell phone telephone...
[Moto X General] KidJoe:
No. that thread is for rooting with a LOCKED boot loader. Has nothing to do with unlocking the boot loader.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] N3OMOD:
Good evening everyone,

I have recently bought (and bricked) a Kindle Fire HD from Amazon with the statement “Previous Generation” in the title.

Now, after spending a week reading this forum with guides, tutorials and referenced articles I have concluded that there is a “huge mess” out there in identifying and naming each Kindle version.

As far as I can tell my Kindle should be a 2nd Generation of the HD series, also called “2012 Version” in some threads but although an extensive reading I could not figure out if there is a way to clearly identify a model from its hardware serial number / features.

The next logical question would be “Which guide/tutorial should I follow in order to Root and customize my Kindle thus transforming it in a full-featured Android tablet?”

If I suppose that my model is correctly identified by the definition above, than I should follow this guide (http://xdaforums.com/showthread.php?t=2128848) although there is no mention about generation in the title.

I would be glad If anyone with a bit of “field experience” might help me clarifying this thoughts and avoiding bricking another device.

Thank you in advance for your time, your courtesy, and the great job you provide maintaining this board.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] stunts513:
If it has a camera it is a 2012 model. If it was 2013 then all you could do is root it. Anyways if it is indeed the 2012 model then use this to root it: http://xdaforums.com/showthread.php?t=1886460

And I suggest this to get recovery and 2nd boot loader installed: http://xdaforums.com/showthread.php?t=2271909

Just remember to check the first checlbox about downgrading the bootloader, I should be followed with a warning in red, if you don't do this you will need a fastboot cable to fix it afterwards. Oh and make sure to put a ROM and its corresponding gapps on ahead of time because it will boot loop and only let you go into recovery once you install 2nd bootloader + twrp.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] N3OMOD:
Dear stunts513,

firstly thank you for your kind and complete answer!

My kindle has a front-facing camera, so thanks to your detailed description I can say It is a 2012 model.

Thank you for the tutorial links, especially for the tips about downgrading bootloader and correctly preparing for the 2nd bootloader + twrp.

Your help has been really precious.
[Sprint Samsung Galaxy S III] smartguy10:
Is there a modded YouTube which will allow me to listen to YouTube after the screen is locked
[Sprint Samsung Galaxy S III] jdelano:
will this work for you?

[APK Teardown: YouTube 5.2.27] Hallelujah ... - Android Police

http://www.androidpolice.com/2013/1...dio-is-finally-coming-to-youtube-for-android/
[Sprint Samsung Galaxy S III] smartguy10:
Thats in the future , I was looking for something in present..
[Sprint Samsung Galaxy S III] CNexus:
Use xposed
[Sprint Samsung Galaxy S III] romeoh:
Me too I was looking for a the same feature so I tried this but it's not working with me I don't know why!!!! I'm running 4.3 fully stock rooted rom.
[Sprint Samsung Galaxy S III] beezie42:
http://xdaforums.com/showthread.php?t=1529715

That's what I use. It's a older YouTube app but gets the job done. Plays music after you lock the screen , as well as HD video play back.
[Sprint Samsung Galaxy S III] romeoh:
Thanks bro, That will help until google release the official youtube app that supports audio playback in background:thumbup:.
[Sprint Samsung Galaxy S III] beezie42:
For sure anytime. You might also be interested in this app as well.

http://xdaforums.com/showthread.php?t=2413078

It's about the same thing but it also has floating window and also works great.
[Sprint Samsung Galaxy S III] romeoh:
:eek: Oh man that app is way better than the moded youtube. That's exaxtly what I was looking for the floating window is a great feature too. Thanks again bro you are the best :D.