yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 10.1 Android Development] direwolf1:
Was this your first day using IOKP? I usually find that any ROM takes a charge cycle or two to really settle in--I think it's because the flashing process throws off the battery calibration, and a full cycle resets it. FWIW, I just switched from this ROM to CM 10.2. I had a similar experience on the first battery cycle--reduced battery life with CM compared to IOKP--but on my second cycle CM seems to be doing much better. My experience (with an 8013) was that IOKP has excellent battery life (10+ hours of screen-on time).
[Galaxy Note 10.1 Android Development] jcwilliams:
I don't like the halo. Is there a way to disable it? I can't find a setting for it.

Thanks
[Galaxy Note 10.1 Android Development] Specialp:
To disable halo: drag the circle out. Tap twice, holding the second press, now just drag to the remove x icon displayed when holding the halo circle. There's your notification bar back. Hope that clears it up for ya
[Galaxy Note 10.1 Android Development] hottweelz:
"Battery Calibration" is a Unicorn.

No matter what you read, where you read it.

I have a bridge to sell you that calibrates batteries.

Its a bug in this ROM :(
[Galaxy Note 10.1 Android Development] direwolf1:
Not quite. People may misuse the term "battery calibration," but it undoubtedly happens. It has to, in several ways, or your battery meter wouldn't work very well. Lithium-ion batteries decay over time. Say your phone has a 2100mAh battery (like the Nexus 4). After some months of use, the maximum charge it can hold will decline, say to 1900mAh or so. The software battery meter has to adjust to that decay, or the device would never charge to 100%. That's calibration. Some older phones didn't do this very well--for example, people often complained that my old Moto Atrix 4G wouldn't charge past 95% or 98% after a while. That's because the software didn't calibrate very well as the battery decayed. But unless the software does calibrate, it's simply impossible that you'd continually be able to charge your battery to 100%. I've had my Nexus 4 for over a year, and it still charges to 100%, so either the software has calibrated to the reduced capacity of the battery, or my battery defies the laws of physics.

Here's another example of what I call calibration (though of a different type): I was running IOKP on my 8013 until yesterday. With about 40% battery remaining, I booted into recovery, factory wiped, and installed CM 10.2. When I rebooted the system, I was down to 35%. In 34 minutes, the battery burned down to 12%. That's about 0.65% per minute. I recharged the tablet overnight, and today I've run the battery for 13 hours, with 66 minutes of screen on time. Even if we only count the screen on time, that's 0.15% per minute. Over four times better.

Every time I've flashed a ROM, and most times I've flashed a kernel, on any android device, the battery has drained significantly faster than it did before the flash. Without fail, battery life improved on the second or third charge cycle. Some people don't like using the term "battery calibration" to refer to what happens after you flash a new ROM, apparently including you. Fine. Call it a unicorn. Call it "settling in." Call it phone magic ninja wizardry. But it happens.

It seems unlikely that it's a bug in the ROM--lots of people have been using it happily for weeks, and no one else seems to have this problem. Google has been doing something strange with Google Play Services lately. Maybe that was the cause of your drain, if you don't want to blame it on a unicorn. But I doubt it's a bug in IOKP.
[Galaxy Note 10.1 Android Development] jcwilliams:
I can't get it to slide out. It's almost not responding. I cant even get it to move.... :/

---------- Post added at 01:31 PM ---------- Previous post was at 01:30 PM ----------

Also in looking to clear up some space and move some games to sdcard but it's not working. How can we do it? App2sd isn't working there no move button.
[Galaxy Note 10.1 Android Development] CyberCROC:
I installed the latest ROM available for the N8000. All went very smooth however it seems to be stuck on the boot screen. I can imagine it must initialize but after what period of time should this go through?

Thanks for the help.

Update: I got the booting sorted out. After a factory reset all boots fine. Only trouble I'm still having is that I can't make a 3G connection. It is as if mobile network is not supported. Is that correct or am I doing something wrong?
[Galaxy Note 10.1 Android Development] Greenion:
Crashing on Install

Just tried to install this rom. But it crashes as it starts to install.

It crashed with a bunch of lines of jibberish.

Was wondering if it might be the recovery which is still 6.0.1.1.

Sorry if this is not enough info.

Any suggestions would be fantastic.
[Galaxy Note 10.1 Android Development] hottweelz:
I like the idea that the software may not propery read the battery levels. That makes much more sense, I had just jumped the gun when I read "battery calibration" cuz of how often its misused.... just like unlimited web hosting....
[Galaxy Note 10.1 Android Development] lostgenius:
recommend a kernel

Can anybody recommend a kernel compatable with this ROM. I have tried a couple but they have not worked.

Any help would be appreciated.
[Galaxy Note 10.1 Android Development] niofar:
Good evening, I can't start Infamous tools on my n8000...i receive an error message "Unfortunately, Infamous Tools has stopped".
[Galaxy Note 10.1 Android Development] kimo_ig:
delete dalvik cache and restart:D
[Galaxy Note 10.1 Android Development] ©h®is:
yeah, it is a known issue

try first version of nov 10. working fine
[Galaxy Note 10.1 Android Development] WhitestSand:
kernel.....

1+ Is anyone using a different kernel?
[Galaxy Note 10.1 Android Development] DesignGrits:
For the users that are using this rom on the 8013, what rom did you come from when flashing this? And what recovery are you using? I've checked md5 and have tried 5 times with no luck. thanks
[Galaxy Note 10.1 Android Development] comatose1978:
I came from hyperdrive. I'm using cwm 6.0.3.6. Running flawlessly. ??
[Galaxy Note 10.1 Android Development] MoFosis:
Is There any was to disable the onscreen arrow that comes when using the Spen?

Searched through this thread and the local settings but cant seem to find the Option.

Thanks :)
[Galaxy Note 10.1 Android Development] DesignGrits:
That's what I was coming from too. Maybe has to do with Zeus kernel. Not sure, thanks though
[Galaxy Note 10.1 Android Development] xf69:
Some pages back:
[Galaxy Note 10.1 Android Development] Jamison904:
Forgot to tell you guys. Other kernels won't work at the moment. We had to introduce a 2nd frameworks.jar since the max code was reached for one. The ram disk needs to be modified to work with the 2nd framework.jar or it will not boot. Feel free to have your favorite kernel developer contact me or link them to this post and ask them to use our ramdisk for iokp compatible kernel. :cool:

Sent from my dark hole called an office.
[Galaxy Note 10.1 Android Development] kimo_ig:
what about the 4.4?
[Galaxy Note 10.1 Android Development] Kamairo:
Any change log for the build from 12/01 ?
[Galaxy Note 10.1 Android Development] Jamison904:
Minor bug fixes. No new features.

Sent from my dark hole called an office.
[Galaxy Note 10.1 Android Development] MoFosis:
Pain in the ass but it Worked. Thank you for quoting and thanks to Kamairo
[Galaxy Note 10.1 Android Development] Greenion:
Installed all good except I've lost ir. Is this part of iokp or is it an error? Has anybody had this issue?
[Galaxy Note 10.1 Android Development] doditpradipta:
issues

i was iokp build dec 1 but i have bug here

dialer fc and simcard not detected so i cant turn on my mobile networks
[Galaxy Note 10.1 Android Development] dvux:
hi,

i love the style of this rom, but i need multiuser and every time i add a new user and wanna configure/log in there the ROM Crash with "android.process.acore" and different GApps like Keyboard...

i tried the last 2 Versions and both links GApps...

Can someone help?
[Galaxy Note 10.1 Android Development] ©h®is:
yeah, the bug is still there

first version, from nov 10. is working fine
[Galaxy Note 10.1 Android Development] doditpradipta:
All working? Like dialer and sim?
[Galaxy Note 10.1 Android Development] ©h®is:
yes!

running daily since release.. :)

uups, sorry.. dialer fc too.. (never used)

but 3g is working
[Galaxy Note 10.1 Android Development] kevincop:
N8013 - 2013-12-11 stuck on facemask loading screen

Hello,

I was trying to see what 4.3.1 looks like, this is my first rodeo, but I think I got the hang of it. So I flashed your 2013-12-11 version and it's stuck on the loading screen with the facemask and the two things spinning. It's not frozen, it just doesn't go past that. I'll try an earlier version. It seems another person had the same issue and posted in this thread and the reply was "known issue, use november something". Maybe it would help if you posted the known issues on the first thread...

Thanks.

Update: Re-download the file, check MD5, copy the zip to your device/sd card and check MD5 again, and of course, wipe to factory. I used TWRP to flash the ROM to my device.
[Galaxy Note 10.1 Android Development] Specialp:
I don't think any builds fail to boot. The first thing you should check is the md5 of your rom zip. If the md5s match then you should be OK to flash again. Also what recovery are you using? How long did it sit at the boot animation? The first boot of any rom takes a little while. I usually wait at least 10 minutes before deciding there's a problem.
[Galaxy Note 10.1 Android Development] kevincop:
I didn't get a chance to check MD5 but I did re-download the same and then a few more, to test them out. I was able to get the latest one running. It's a lot smoother than I had anticipated. The only oddities in this build are the OS X mouse as the pointer for the digitizer (is there a way to change that? yes, someone posted that already on the forum here and also, for the developer, source code can be changed like so), and the nav bar/nav ring acting up - I'm having the hardest time activating the ring, or restoring the bar from the bottom icon.

Otherwise, great job!
[Galaxy Note 10.1 Android Development] Jamison904:
I was looking into adding code to allow you to toggle it on and off. Unfortunately I have been busy trying to get 4.4 ready to release for all of our supported devices as well as port over all of our features. Very very time consuming since there really is only myself and [MENTION=5001866]Mr Impossible[/MENTION] who work on the code and not just build from the repo.

Sent from my dark hole called an office.
[Galaxy Note 10.1 Android Development] Jamison904:
Oh and be sure to thank [MENTION=3050937]©h®is[/MENTION] as he is helping me figure the FCs for the n8000

Sent from my dark hole called an office.
[Galaxy Note 10.1 Android Development] kevincop:
I understand. Extremely good job, once again. I managed to set up my device to my liking, and boy is it fast! It's smoother than stock, that's what I can't comprehend. Awesome. Gotta at least buy you a coffee :)

For those people who don't know/want to fiddle with framework-res.apk, here's a link to a modified pointer that only displays a black dot directly under the pen tip. It's for N8013, not sure if it makes a difference... but I'm willing to nudge the dot over for those of you with other devices:

framework-res.apk with a dot as the pointer instead of the arrow

To be able to overwrite that, you need to mount /system as read/write (rw). To do so, first run mount in a terminal to see which /dev/block/?? has your /system:

/dev/block/mmcblk0p9 /system ext4 ro,seclabel,relatime,user_xattr,barrier=1,data=ordered 0 0

For me it's mmcblk0p9, I'll use the following command to remount it read/write instead of read only:

mount -o remount,rw -t yaffs2 /dev/block/[B]mmcblk0p9[/B] /system

** Remember to change the bolded part, your device might name it differently.

Then use your favorite file manager or ssh to drop the file inside /system/framework. I would backup the original file first if I were you:

cp /system/framework/framework-res.apk /system/framework/framework-res.apk-original

You don't need to reboot the device if you're doing this via SSH, just make sure it is running and the screen is on. It will temporarily display the face mask, and get back to normal, at which point you should see a different pointer for your active pen/s-pen/digitizer.
[Galaxy Note 10.1 Android Development] flipper2006:
I only have one minor issue and not really what causes it.. Nov 1 I started, but now using the latest dec 2 build. when clicking anything on the screen i always need to go and press everything 2 times like it doesn't get it the first time. Really no other issues, that make any sense?

PS. Big fan of Alpha on S4.
[Galaxy Note 10.1 Android Development] MohamadAli:
Guys can anyone tell me what will i be losing if i switch to this rom, like S Pen functionality, what are the major differences betwen touchwiz and this, tweakes, samsung stuff? Anyome please
[Galaxy Note 10.1 Android Development] darkhandsome18:
First, that question has been asked a billion times on this forum. Learn to search. Secondly, how hard can it be to do a nandroid backup, test the rom, if you don't like it, restore.

Facepalm
[Galaxy Note 10.1 Android Development] ©h®is:
You loose all the Samsung stuff..

You get a fast 4.3 AOKP based rom without the Samsung bloat and tons of tweaks

Gesendet von meinem Nexus 4 mit Tapatalk
[Galaxy Note 10.1 Android Development] kkae70:
Hi..

I tried up this your Rom for my N8000

But when I finish do it, My N8000 have not signal for my phone.

I tried for do it 2-3 times,but it still same at first time.

Can u teach me for up your Rom step by step?

thanks

............

(sorry for my bad English)
[Galaxy Note 10.1 Android Development] Kamairo:
No offense, but would you guys mind reading at least the last 2 pages? There's the same questions every 4 posts...
[Galaxy Note 10.1 Android Development] zulu888:
+1
[Galaxy Note 10.1 Android Development] kkae70:
Sorry, I readed its but i can not fine the answer .. can u help me? Thanks
[Galaxy Note 10.1 Android Development] Kamairo:
--> last 2 pages
[Galaxy Note 10.1 Android Development] kkae70:
Thanks.

so I use for version 10.11.2513

The signal phone is coming for my device.

But iI found some problem, when i use dialer it is not working .my device show me that "Unfortunately, Dialer has stopped."...

Can u help again please? Thanks

---------- Post added at 06:10 AM ---------- Previous post was at 06:09 AM ----------

Thanks.

so I use for version 10.11.2513

The signal phone is coming for my device.

But iI found some problem, when i use dialer it is not working .my device show me that "Unfortunately, Dialer has stopped."...

Can u help again please? Thanks
[Galaxy Note 10.1 Android Development] 47kt:
Yes. Read the last quote of Kamairo's post. (two posts up)

Another thing. Is "swiping" with the standard aosp keyboard working for you guys?
[Galaxy Note 10.1 Android Development] ©h®is:
yes, works for me (version nov 10 / N8000)
[Galaxy Note 10.1 Android Development] kkae70:
---------- Post added at 08:14 AM ---------- Previous post was at 08:13 AM ----------

[/COLOR]

How can I do it..

swiping" with the standard aosp keyboard

?

please teach me..Thanks
[Galaxy Note 10.1 Android Development] ©h®is:
hm

?

normally i use SwiftKey, but to check i changed to aosp keyboard and it worked immediately..

maybe look in settings and you've got the language pack you need installed
[Galaxy Note 10.1 Android Development] dbodom:
Just installed the 12/1 zip of IOKP on my 8013 coming from Revolution ROM. The speed of this ROM is really good. Everything seems to be working (so far) except GPS which does not lock on anything. I was wondering if anyone had a quick fix for the GPS?

I really like the ROM's speed and look and feel. Great job development team!
[Galaxy Note 10.1 Android Development] Greenion:
Is there a link for the Dec 1st build? Interested in giving it a try.

I am currently running the Nov 10th build, coming from ARHD rom. This is a great rom a few little issues to get use to. Only thing I really miss is the IR Blaster. I had it running as remote for Al out all home devices.

Can't wait to see this rom progress even more be it 4.3.1 or 4.4(0.1.2).
[Galaxy Note 10.1 Android Development] ©h®is:
the link is in the first post.. ;)
[Galaxy Note 10.1 Android Development] diggedy:
Couldnt see if this had been mentioned before. I set this rom up (1/12/13 version) on my 8010 and when I tried to create a new user profile I got a whole load of process stopped working messages. I rebooted and it wiped my apps and settings completely on my main profile. Im still getting the messages now on both profiles.

Is this a known bug?
[Galaxy Note 10.1 Android Development] mercator54:
DEVs, can you enable multiwindow in this ROM?.. you just have to recompile it with http://d-h.st/ISk this... hope you'll not neglect my post!.. :D
[Galaxy Note 10.1 Android Development] cwbeasley:
Getting a force close when trying to use Dashclock like someone else. I'm on the 12/01 release.

Edit: wiped dalvaik and cache, now have the WiFi bug. And attempts to toggle NFC from status bar gives force close.
[Galaxy Note 10.1 Android Development] pranto:
help, help. help....I just installed that does not make me call, there is no GSM network.
[Galaxy Note 10.1 Android Development] ©h®is:
yeah, it's a kown issue

just read a few sides back.. ;)

with first version (11.10) you have working network (but also dialer fc) :)
[Galaxy Note 10.1 Android Development] shan1188:
N8000 stuck at boot animation

im trying to flash this rom but it is stuck at the boot animation... i tried other rom also the same... i tried using twrp bt cant as it says assert failed getprop... tried using cwm 6.0.4.4 it flashed bt stucks at boot animation...help pls...
[Galaxy Note 10.1 Android Development] xX_Nexus_Xx:
Re: [ROM][4.2.2] AOKP MR1 Kang Project [n8000/10/13] 20130218

FC when changing the navigation bar ring content!

I tried to change the number of nav ring targets and to assign apps... But from this onward I get ongoing UI FC's ...I was not able to reset to original setting ...and had to reinstall the entire ROM
[Galaxy Note 10.1 Android Development] Jamison904:
Re: [ROM][4.2.2] AOKP MR1 Kang Project [n8000/10/13] 20130218

Good to know. Ill look into it tonight. I also noticed the assigning targets does not stick. I am looking at this as well. As for tethering I know the S3 series is having issues as well. I am testing a cherry pick and it seems to have fixed it but not sure if I can apply it here. Will have to modify it and it is also kernel based so there it that... the kernel that builds with this has a bug that I am trying to find that causes it to stick at 200 MHz and won't let you change the frequency. So since I ported AOKP to these devices there isn't anyone else working on it so it might take a few for me to figure it out alone.

Sent from my dark hole called an office.
[Galaxy Note 10.1 Android Development] TweakerL:
Read the instructions: Noozxoide is supposed to be flashed, not just installed...
[Galaxy Note 10.1 Android Development] TexasRules777:
Re: [ROM][4.2.2] AOKP MR1 Kang Project [n8000/10/13] 20130218

Yea but it works perfectly by just installing the apk, delete DSP manager in root explorer and rebooting. Bass adjusts properly as well as the eq. Maybe it has something to do with the leftover audio lib files from DSP manager? I'll give the other version a shot and see if that works. Thanks
[Galaxy Note 10.1 Android Development] Dsmforlife92:
Re: [ROM][4.2.2] AOKP MR1 Kang Project [n8000/10/13] 20130218

Is there any way to turn speaker volume up it lower then stock for me thanks
[Galaxy Note 10.1 Android Development] xX_Nexus_Xx:
Re: [ROM][4.2.2] AOKP MR1 Kang Project [n8000/10/13] 20130218

Sounds promising! ... Looking forward to get the tethering and navbar rings working.. Thank you for the help!!

An additional issue I realized is when using the pen (e.g with papyrus) I have to keep my hand of the screen...as soon the hand lays in the screen no more pen writing is possible.... This was possible with cm10.1 based versions
[Galaxy Note 10.1 Android Development] Jamison904:
Re: [ROM][4.2.2] AOKP MR1 Kang Project [n8000/10/13] 20130218

This would be the exact reason. DSP doesn't come with this ROM as of yet. (Not sure if I am going to add it yet or not.) That being said, the required libs are nit included with the ROM to make it work. This is why other times when you deleted DSP and just installed the apk it worked just fine. Have you tried flashing the zip?

let me know

I saw an open commit that says it fixes this. Ill cherry pick in and test it out.

Left me tab at home so I will try and recreate it and go from there. Sounds like adjusting the driver should take care of that but won't know until I try.

Sent from my dark hole called an office.
[Galaxy Note 10.1 Android Development] TexasRules777:
Yea the zip from the xda thread actually seemed to work. I've only ever used the one from the market so i didn't know the other one installed it's own lib files.
[Galaxy Note 10.1 Android Development] Jamison904:
No worries man, trial and error. That is how we all learn. Oh and today's build is up. No major fixes yet. :cool:
[Galaxy Note 10.1 Android Development] xX_Nexus_Xx:
Re: [ROM][4.2.2] AOKP MR1 Kang Project [n8000/10/13] 20130218

The selection of tiles for the quick settings is different from cm10.1... Lot of useful tiles are missing ..is there a reason for that?
[Galaxy Note 10.1 Android Development] dayr:
I just discovered that multiwindow project for AOSP. I really need multiwindow, but I love AOKP (all my other devices use it ). If they work on it and you add it, this will be my next rom :D
[Galaxy Note 10.1 Android Development] Eric-Mod:
Where did you found that? :)
[Galaxy Note 10.1 Android Development] Jamison904:
Are you talking about cornerstone? If so it has been around for longer the Samsung has had multi window capabilities. It is open source and I have been thinking about attempting to add it. But if I do it will part of a long time stable build instead of dailies. It all depends, if this project really takes off then yes I will
[Galaxy Note 10.1 Android Development] dayr:
It is NOT finished, and there is NOT a version with works. There are some builds for some android versions. It's called Cornerstone (and there are some comments in this thread). It is not really new (they had some problems with google, so it was on pause).
[Galaxy Note 10.1 Android Development] Jamison904:
Re: [ROM][4.2.2] AOKP MR1 Kang Project [n8000/10/13] 20130218

Yes there is a working build. Go over to Robs Tenderloin (HP touch pad) AOKP build. But it is something you have to add to your source and then build it. You are right that it isn't complete so if anyone was to attempt to get it to work a lot of manual code will be needed. That's why I am not making any promises

Sent from my dark hole called an office.
[Galaxy Note 10.1 Android Development] dayr:
Didn't know there was already a working build :)

It's not like I am trying to put presure on you. I know it's new, not finished, delicate, and not easy to introduce in the rom. Just that last time I check it, it did'nt work yet on Android 4.x and it seemed abandoned. And since I got my Note 10.1, I was missing AOKP :P So when I read the news about it in this topic, it was a "OMG!!! Maybe, in a future, Note+MultiWindow+AOKP :fingers-crossed: :highfive::highfive::highfive::highfive::fingers-crossed::highfive::victory::laugh:"

hahaha
[Galaxy Note 10.1 Android Development] Jamison904:
Re: [ROM][4.2.2] AOKP MR1 Kang Project [n8000/10/13] 20130218

lmao. Good to go :cool:

Sent from my dark hole called an office.
[Galaxy Note 10.1 Android Development] xX_Nexus_Xx:
Re: [ROM][4.2.2] AOKP MR1 Kang Project [n8000/10/13] 20130218

I support Note+MultiWindow+AOKP +handwriting recognition:fingers-crossed: :highfive::highfive::highfive::highfive::fingers-crossed::highfive::victory::laugh: