yashsingh1/xdaforums huggingface dataset:
[HTC One X+] namelessrabbit:
Aaaand another finding:

I don't know how KitKat or your certain ROM handles the dreaded MTP-connection, but since I upgraded to your ROM, Windows keeps asking me whether I want to copy this .mp3-File to my phone, because it could be unplayable by the phone. Maybe the phone has to "tell the PC" it's capable of playing certain filetypes?
[HTC One X+] Lloir:
I assume this works on CM? (As this is what mokee is very very closely based on) Otherwise i have to fix it, for you guys to have the fix
[HTC One X+] namelessrabbit:
Actually I've come from Revolution HD, not CM. It worked quite well except for .flac files which could be played by Poweramp as well.
[HTC One X+] crusader727:
same message pops up on CM
[HTC One X+] chaikowsky:
Thanks! Next time I have to think twice then spamming here!
[HTC One X+] jizang:
Are there any plan for a android l rom from mokee for the one x+?
[HTC One X+] bmsk:
http://download.mokeedev.com/?device=enrc2b&type=release

Sent from my One X+
[HTC One X+] namelessrabbit:
I think he meant an Android "L" release ;)

Currently experiencing some freezes in standby, meaning I can't wakeup the phone. Resetting sometimes helps, but mostly the battery has been dried out by something wrong going on under the hood. This happens approximately every two days or so. Will try to reboot every night and see how it goes. Didn't install the last OTA because of people reporting errors.

Edit: Tried to install the latest (140912-140926-RELEASE)OTA update but keep getting errors. Tried it via MoKee Center and manually via Recovery to no avail. Re-downloaded the file and tried again. Still failing.

Do I have to install the earlier (but perhaps buggy) update (140912-140920-RELEASE) before? I beg your pardon in case this is a stupid question :o

Edit2: Manually downloaded the latest (140912-140926-RELEASE) OTA from your website and tried installing it manually via CWM v6.0.4.8. Didn't help, it says "Error in /data/media/0/OTA-MK44.4-enrc2b-140912-140926-RELEASE.zip (Status 7)"

Edit3: Downloaded and manually flashed the 140912-140920-RELEASE OTA. As expected it broke cellular and wifi. Downloaded and tried to manually flash 140920-140926-RELEASE OTA. Now it says "/system/bin/otasigchech.sh has unexpected contents. Error in...."

Restored to 140912-RELEASE, cellular still broken.

Edit4: Cellular miraculously recovered, but I'm still on 140912.
[HTC One X+] mackhenri:
Do we have any option to increase grid size cause the apps look too big in the drawer

Edit :managed to make the apps icon small...

Sent from my One X+

---------- Post added at 10:55 PM ---------- Previous post was at 10:38 PM ----------

Thanks Mokee for the great ROM

...

Sent from my One X+
[HTC One X+] Lloir:
Flash the boot.img in the rom, it's due to changes I made in CM.

I think it's awful that [MENTION=5172180]martincz[/MENTION] isn't even replying to you guys to try and resolve issues.
[HTC One X+] namelessrabbit:
Sorry for having to ask, but at which point am I supposed to flash the boot.img? Install 140912-140920-RELEASE OTA, then flash boot.img, then install 140912-140926-RELEASE?
[HTC One X+] Lloir:
either dude, doesn't matter.
[HTC One X+] namelessrabbit:
Thanks for helping with cellular!

Still can't update to 140926, though. It keeps giving me this "/system/bin/otasigchech.sh has unexpected contents." error.

By the way, I don't think it's a really big deal that martincz doesn't answer instantly. I mean, all you dev guys are sacrificing your spare time for others, so I guess we should appreciate any kind of attention and help we get from you ;)
[HTC One X+] namelessrabbit:
Any ideas on the failing update anyone?
[HTC One X+] namelessrabbit:
I surely don't mean to be rude, but it would be nice to get just some kind of feedback from [MENTION=5172180]martincz[/MENTION] :-/

What about you other users of this ROM? Don't you want to share some knowledge?
[HTC One X+] namelessrabbit:
Just updated OTA to 141009-RELEASE. Worked perfectly as opposed to 140926-RELEASE.

Everything fine so far, no instantly obvious bugs found. Will keep testing.
[HTC One X+] bmsk:
It also updated perfectly here unlike the 140926-Release.

Sent from my One X+
[HTC One X+] smartamazing:
Hi Guys its not clear to me the installation instructions....Do I still need to unlock bootloader thru htcdev and root my hox+ before I can flash this ROM? I'm on stock rom 4.2.2
[HTC One X+] bmsk:
Yes. Don't forget CWM

Sent from my One X+
[HTC One X+] smartamazing:
Thanks Mate for that im going to flash it today. And lastly from your experience which is better the OFFICIAL or NIGHTLY?
[HTC One X+] bmsk:
I am using the release and never had problems so far. Never tried the nightly.

Sent from my One X+
[HTC One X+] smartamazing:
Thanks for that info again bmsk that would help me a lot...But the RELEASE and NIGHTLY have the same FEATURES stated at the first post specially the UNIQUE POWER OPTIONS?
[HTC One X+] namelessrabbit:
I'm still experiencing some crackling and stuttering sound during music playback. Don't know if that's related to PowerAmp not cooperating with the MoKee ROM, but I think it's worth pointing out. Haven't updated to OTA-MK44.4-enrc2b-141009-141013-RELEASE yet to be fair.

Another issue is (at least for me) that sometimes it takes a few seconds (1-3s) to wake the screen. Buttons light up, but the screen is kinda delayed. Hasn't always been like this, occured after the previous OTA IIRC.

Battery life is okay for me, but could be better. Getting through a regular day I lose approx. 5% per hour standby.

Since I installed a few OTA updates I'm not sure whether all this could be fixed by flashing it clean. Will try in a few days.
[HTC One X+] shreyanshk:
I used to have this stuttering problem but then i switched to carbon... you should try it.
[HTC One X+] namelessrabbit:
Updated OTA to 141013-RELEASE and had just one recognizable stutter within 15 minutes since. Don't know what they changed, but it sure helped :victory:

How about battery life with you guys? Average day with a few calls, instant messaging around every 15 minutes and some light surfing leaves me with 30-40% remaining charge. Of course this isn't a scientifical approach but do you have significantly better battery life?

€: Stutter seems to be gone completely. Never noticed something since updating. :good:

Battery life is mediocre, especially when using as gps navigation in my car. Battery was pretty much dead after 1.5h. :( Project Volta to the rescue?

€²: Aaaaand stutter is back, but way better than before. Only once in a while.
[HTC One X+] namelessrabbit:
Currently experiencing freezes approximately every two days. In standby as well as during use. Rebooting every night prevents this. Anyone else?
[HTC One X+] resinis:
why is the ATT model such a bastard child? is it really that hard to change these roms over? or does the international versions have different chipsets that are actually updated to work with newer versions of android?
[HTC One X+] Lloir:
It's literally a bastard child. It has both tegra3 and qcom chipset because of the LTE, which makes it a complete ***** :/ in theory if you changed the fstab layout and modified the zip itself so it says it's an evitareul it would flash...boot? Maybe, usable as a phone? Far from it
[HTC One X+] namelessrabbit:
IIRC somebody wrote that Nvidia wouldn't provide drivers for Android 4.3+. Is that the reason for the battery drain seemingly being higher than with Stock ROM?

OTA to 141025-RELEASE went well, just had to reflash boot.img to get wireless and cellular working.

Btw, congratulations Lloir for having quit smoking! Best wishes for you to keep it that way ;)
[HTC One X+] namelessrabbit:
Actually I'm quite tempted to try Carbon since there is no response from [MENTION=5172180]martincz[/MENTION] to anything but unfortunately MoKee is pretty much the only 4.4.4-ROM :(
[HTC One X+] Lloir:
lol WUT? there's omni / CM / Carbon all @ 4.4.4
[HTC One X+] namelessrabbit:
Changed to ART today, no crashes yet. Scrolling displays some stutter, switching between apps is a joy now, though. Will report on battery life and overall stability.

When enabling ART it said that ART was not supported by MoKee. Do you do that just as a precaution or do you actually develop for Dalvik as the main runtime?
[HTC One X+] clehcim:
only one cpu is working

it could be usefull for dev team

i try your rom on my onex+ cid 203 with 1.72 firmware (it works too with 1.3)

during antutu benchmark my score is almost 17000

with a 4.2.1 rom the score is 22000

during test ressource monitor mini pro says that onex+ use only 1 cpu.

with the revHD8 rom i cab see 4 cpu used

I hope it will be usefull for you

M
[HTC One X+] Lloir:
Mooke don't do anything with the device/kernel so this stuff is pointless to them.
[HTC One X+] namelessrabbit:
Still looks pretty good actually. I feel like scrolling got a bit better under ART with last update. Stability isn't worse compared to Dalvik, got some occasional freezes. But nothing too bad. Sometimes wireless (WLAN and mobile) stops working, can't access settings etc, reboot needed.

Sound stuttering isn't completely gone but WAAAY better than with Dalvik.

Battery life is okay for me, I'm left with 40-50% after a regular 12h-day. To be fair, I blocked almost half of all available wakelocks. Additionally I set a limit of 1,3Ghz for the processor, but I'm not sure whether the processor actually obeys that :P

Any thoughts on the only-one-core-used-issue by [MENTION=2272781]clehcim[/MENTION] ?
[HTC One X+] namelessrabbit:
OTA-package 141129-RELEASE on mokeedev is down.

€: Back online again, thank you.

Got a question though: Where would be a better place to leave feedback and get responses to questions? MoKee forum takes forever to load and to be honest...my chinese has become a little rusty ;)
[HTC One X+] croccodillo:
Hello all,

Just a quick (and stupid) question:

Right now I've installed "Android Revolution HD 8" with EliteKernel 4.2 on my HTC One X+, and I'd like to test Mokee.

So, please confirm I have understood how to proceed:

1. Flash the ROM via CWM recovery

2. Install Kernel (I need Elite Kernel 4.4, right? IS the ROM default Kernel shipped into the zip?) with fastboot, without rebooting the phone

3. Restart the phone

4. Flash the gapps via CWM recovery

OF course I omitted the needed backup steps.

Is it right?

Did I forgot anything?

Thank you in advance

Ciao,

Giovanni
[HTC One X+] morbvamp:
Make sure your CWM is the version compatible to flash 4.4.x ROMs also remember to make a FULL wipe before installing a new ROM.

You can use the boot.img that comes within the rom zip file but it isn't elite kernel, you'll have to download it from it's thread and flash via bootloader.

In my case I always flash the ROM first and then gapps, then I erase cache & dalvik cache, restart to bootloader, flash kernel and restart the phone.
[HTC One X+] namelessrabbit:
Are there any advantages in using elite kernel with this rom? Like better battery life or improved responsiveness?
[HTC One X+] morbvamp:
In my experience, elite kernel gave a bettery life in all 4.4.x ROM's I tried it. Also my phone runs very smooth with it. You can give it a shot and if you're not pleased with it, you can install the boot.img that comes inside the ROM .zip from Mokee.
[MDA III, XDA III, PDA2k, 9090 General] stevenk916:
This phone is solid, it has a large screen that is great for movies and gps. The keyboard feels tight. There is a scratch on top and at the bottom...other than that the phone is in mint condition. This phone has a screen protector. Its hard to part with this phone but is anyone is interested 300 obo. Pictures upon request. you can email me at stevenk916 at hotmail dot com.
[MDA III, XDA III, PDA2k, 9090 General] japa78:
where are u located? what price did you have in mind? Iam in India.

rgds

mukund
[MDA III, XDA III, PDA2k, 9090 General] GapBoyT:
Uh... his post says 300 O.B.O.

Since his profile says he has AT&T I am going to say he lives in the USA.

:-)
[Sprint Galaxy S 5 Q&A, Help & Troubleshooting] rleighska:
I have tried all of the below and am still stuck on the Galaxy S5 screen with "set warranty bit : kernel" in yellow at the top left. I've tried the stock firmware from the Samsung mobile site and cannot get it to go back to stock. Every time I go into download mode it still shows custom instead of original. When I've tried to flash the stock kernel I get a md5! binary error. I can get into download mode just fine, but can't get recovery to come up either. If anyone can help I would greatly appreciate it. I've tried everything I've seen in the forums and am very frustrated. My phone hasn't worked since Wednesday night. I'm fairly new at this, but have been doing things I've found in the forums but nothing has worked so far. Can anyone help?? Please....

Everything was fine with the phone until Wednesday when I pulled it out of my pocket and it was stuck on the screen with the kernel message. I think maybe an OTA update came up and somehow it was accepted when the phone was in my pocket. I'm not sure though because it had worked fine earlier that day.

Originally Posted by Joe0113 View Post

Some people seem to be having trouble, so I thought this might help you guys out.

1. DL Odin 3.09

2. DL this stock NCB tar. ----- Here is a faster/better DL mirror! Thanks to [MENTION=786971]ChaddyPaddy[/MENTION] ----- And yet another mirror! Thanks to [MENTION=2938835]roadrunnrr[/MENTION]

3. Make a backup of your apps/data (TiBu/Helium/etc). MAKE SURE THE APP/DATA BACKUPS ARE TO YOUR EXT SD CARD!!!

4. Take out your EXT SD Card (if you have one).

5. Flash the stock NCB tar (put it in "AP/PDA" in Odin).

6. Do a factory reset in the stock recovery after you flash the tar (not necessary but deff won't kill ya!).

7. Reboot into Download Mode and make sure it says ROM type= OFFICIAL! If it says custom you will not be able to take the OTA.

8. Reboot, check for the OTA to "ND2" and wait for it to complete.

9. Your baseband and software should now end in ND2. If it does not, then you did something wrong, go back to step 1 and try a redownload, and reflash of stock NCB tar.

10. Re-root.

Also if someone that has SuperSU PRO version, can check if "Survival Mode" works for the GS5, that'd be awesome!

One person tried and said that it does not work.

There is now an Odin flashable tar of 100% stock ND2, no need to even go back to NCB to take it. Just flash the ND2 tar in Odin and you have the full ND2 update!
[Sprint Galaxy S 5 Q&A, Help & Troubleshooting] Iceburn1:
Many different ways to tackle this 1.) flash recovery via odin, then restore nandroid, 2.) or go to sammobile get stock NCB firmware flash through odin, if you do this no worries it takes you back to complete stock but not rooted, your phone will be exactly the same as it was before restoring to stock...just not rooted lol mouth fullll. then reroot! By the way I don't think the phones can update unless you unroot, so jus flash stock NCB firmware take update then reroot if you want update, Its awesome its like dirty flashing! If you were trying ART instead of Dalvik before your phone took a poop, using ART causes the custom status everytime until you switch back to dalvik. Knox will always be 0x1 if you have rooted your S5 unless you haven't wait for an exploit, which is super not like gonna happen, cause S5 is locked up tighter then Fort Knox!
[Sprint Galaxy S 5 Q&A, Help & Troubleshooting] rleighska:
I did go get the stock NCB firmware from sammobile, flashed through odin and the Samsung Galaxy S5 screen came up with "recovery booting" in blue and then "Set warranty bit: kernel" in yellow right under it. It won't go off of this screen. I can go back to download mode, but if I try recovery mode it goes right back to this screen. So then I flashed a recovery, I was using philz_touch_6.42.6-klte.tar. When this was flashed it want to the Samsung screen but had "set warranty bit: kernel" at the top in yellow. I haven't been able to get past this point as every kernel file I've tried in odin either had a binary error or froze and closed odin. I also tried openrecovery-twrp, and governaa, but had the same outcome with both of those. I haven't once had a problem getting into download mode, but can't get it to go into recovery to even try a backup. Oh, and I've been doing all of this with the sd card taken out of the phone, don't know if that makes a difference or not. I did try it with it in at first, but had no luck there either. The one post I read said it should be taken out, so I figured, what could it hurt? I am beyond frustrated. I'm new to this, this is the first phone that I rooted by myself, but it's my second rooted phone. Previously I had a GS3 and never had this kind of problem with that phone.

Also, how would I tell if I was using ART? Before the phone "died" I was playing a game on it. I closed out of the game, turned off the screen, and put it in my pocket. When I took it out of my pocket about an hour later it was on the Samsung Galaxy S5 screen with set warranty bit: kernel.

I just tried re-flashing the stock firmware and it's currently reading set warranty bit: recovery (in yellow) under the "recovery booting....." (in blue).
[Sprint Galaxy S 5 Q&A, Help & Troubleshooting] Iceburn1:
recovery

Did you try to flash recovery bro? Its on a separate partition, if you flash a recovery tar through odin maybe you can restore a nandroid. then go to developer settings in settings check to see if your using art or dalvik

damn need to stop skimming I see you tried, at a loss bro tryin!

Maybe your phone did update and you are using the wrong firmware, could b on nd2?

Did you try to use cf-auto root again just see what happens?
[Sprint Galaxy S 5 Q&A, Help & Troubleshooting] rleighska:
Any help is appreciated!!! I have no idea what to do next. I've done and re-done everything possible. For whatever reason it won't let me boot into recovery. It just goes straight to the Samsung screen with the warranty bit kernel at the top. I just reflashed the stock firmware and it booted up to the samsung screen showing "recovery booting" and "set warranty bit : recovery" at the top. If I flash a recovery (through odin, the same way I flashed the firmware) it will boot to the same screen, but will say "set warranty bit: kernel" instead, but will not go past that screen. I've tried several recoveries, all of them take me to the same screen when flashed. I feel like I'm in a boot loop myself with the things that I've been trying to get this thing to work.

A friend of mine said when I'm at the point that I'm on the samsung screen with the "set warranty bit: kernel" I should be able to boot to download and flash a stock kernel through odin. I haven't found one kernel file that worked. Every one I've tried either gives a md5 binary error or makes odin freeze and close.

I don't think I was using ART. When I got the phone all I did was root it, didn't even get a good ROM on it yet, but then again, I'm not exactly sure what "ART" is because I'm not 100% familiar with all of the terminology just yet, but I'm learning (or trying to).

At this point all I want to do is get it back to stock and re-root it.

Or, if there was a way to reinstate my warranty with Sprint, I'd take it back to them and get a new one.
[Sprint Galaxy S 5 Q&A, Help & Troubleshooting] Iceburn1:
s5 fix

Maybe your phone did update and you are using the wrong firmware, could b on nd2?

Did you try to use cf-auto root again just see what happens?

---------- Post added at 02:37 PM ---------- Previous post was at 02:13 PM ----------

Just flash custom recovery then use cf-auto root.
[Sprint Galaxy S 5 Q&A, Help & Troubleshooting] rleighska:
I reflashed the stock firmware again, flashed philz recovery, and then did cf-auto root and got this...

recovery booting.... (in blue)

recovery is not seandroid enforcing (in red)

set warranty bit: recovery (in yellow)

When I got the phone all I did was root it. How am I able to tell if I'm using ND2 or something else? I can't boot to recovery. I wasn't even trying to update anything on it when it started giving the message set warranty bit: kernel. I was using it, turned the screen off, put it in my pocket for about an hour, and when I took it out it's been stuck on that screen ever since. That was Wednesday. Since then I've tried everything I could find and nothing has worked yet. I'm starting to think that this is un-fixable and now I have a very expensive paperweight. I have a variety of files I've downloaded, so if anyone has any idea, step-by-step what I can do to fix this, I'd be so grateful.

The stock files I got were from Sammobile's site, but I can't seem to get them to work correctly. I flash the stock firmware, then it gives me the set warranty bit recovery message, so I flash recovery (tried twrp, philz, cwm), and then it will boot as far as the Samsung screen, but changes to set warranty bit: kernel. I've tried flashing a new kernel, but can't find any that don't have md5 binary errors or freeze odin. Is there a certain "magic" order of flashing that I should do, like should the firmware be first, then recovery, then kernel (if it'd work), then root? Or firmware, then recovery, root, kernel? I think I've tried every combination imaginable.
[Sprint Galaxy S 5 Q&A, Help & Troubleshooting] Iceburn1:
xposed installed or gravity?

do you have xposed or gravity installed maybe that's whats causing bootloop, try safe mode. Turn phone off hold down volume down button and restart phone it will reboot into safe mode! uninstall mod.

---------- Post added at 06:21 PM ---------- Previous post was at 06:15 PM ----------

Are you 100% sure you were on ncb, I really want to know I mean as far as it goes now theres no coming back, might as well try to download the stock nd2 file and flash that it wont hurt that update can fix some bigs with phone like cameran stuff and you can still root!
[Sprint Galaxy S 5 Q&A, Help & Troubleshooting] rleighska:
I think I did have xposed installed and gravity come to think of it. I tried holding volume down and power and it went to the samsung screen with:

recovery booting.....

recovery is not seandroid enforcing

set warranty bit : recovery

If I turn off, go back to download mode, flash recovery, let it reboot, it will then still be stuck on the samsung screen, but will have:

set warranty bit: kernel

I have not yet found a kernel that will flash successfully and I can't get it to go into recovery at all, just download. It keeps getting stuck on the samsung screen with either the set warranty bit : recovery, until I flash recovery, then it says set warranty bit : kernel.
[Sprint Galaxy S 5 Q&A, Help & Troubleshooting] rleighska:
I'm not sure if I was on ncb or nd2. How do I tell? When I got it I rooted it with CF- auto root, but I didn't do anything else to it that I can recall. I was going to install a rom, but the file wouldn't transfer for me, so I gave up on that until there were other roms to try. The only other thing I did once rooted was download titanium backup, did a backup of everything, downloaded xposed, and was using some of the modules from there. I was using twrp recovery and now I can't get anything to come up that even says twrp.
[Sprint Galaxy S 5 Q&A, Help & Troubleshooting] Nyc1231:
Try using another USB. For example if you are using the USB 3.0 then us the 2.0. Reason why is people from the T-mobile variant where having problem flashing files via odin with the USB 3.0. But damn this is one troubling problem :(

Try using this TAR filehttp://xdaforums.com/showthread.php?t=2737112
[Sprint Galaxy S 5 Q&A, Help & Troubleshooting] rleighska:
I have tried that TAR file, numerous times, same results as previously described. I didn't think to try a different USB cable, was using 3.0 as it came with the phone, but just now switched to the 2.0 and am also getting the same results. :(
[Sprint Galaxy S 5 Q&A, Help & Troubleshooting] Iceburn1:
safemode

I had seen you said u held volume down and power button to get into safe mode, you only hold down volume down and hit power button to turn on, let go power button continue hold volume down.
[Sprint Galaxy S 5 Q&A, Help & Troubleshooting] Nyc1231:
:crying: Let me give it a search on google and see what i can find.

Still nothing; all i can find is to restore to stock