yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 10.1 Original Development] dsb9938:
How high did you go?

D

.
[Galaxy Note 10.1 Original Development] lm that guy:
Im currently on 1500mV @1.8mhz with the lulzactiveq govenor but it still crashes when playing games and running benchmarks. I even crash when trying to install an app 2 times :confused:
[Galaxy Note 10.1 Original Development] dsb9938:
Sounds like it's not meant to be.

D

.
[Galaxy Note 10.1 Original Development] lm that guy:
So again even at 1704mhz, I cant seem to install any app from the market without crashing. Anyone else experiencing this? I tried a full wipe of the rom and applied this kernel but still crashing. Also im just curious, what ROM are you guys using? I have been using omega as a N8000 selected in aroma even though I have the N8013 model. I will try switching roms and see if I have the same results.
[Galaxy Note 10.1 Original Development] RETIEF:
SD card problems

The kernel works great for me. However, my 64GB SD card will not mount. It gets to the error checking and then the "Your SD card is safe to remove" notification appears. Is there 64 gb support with this kernel?

Keep up the good work.
[Galaxy Note 10.1 Original Development] sbreen94:
This kernel is wonderful and battery life is a winner, thanks again for this bud!
[Galaxy Note 10.1 Original Development] Banwell13:
Will you fix 3g for N800?

Any plans to make this work on the n800? Thanks for your efforts.
[Galaxy Note 10.1 Original Development] JSale:
Has anybody got this working with an N8010?

Regards

Jack
[Galaxy Note 10.1 Original Development] iRhyiku:
Yes.

N8010 is the same as N8013 I believe. so if it works for one it works for the other.

Im running this kernel just fine :)
[Galaxy Note 10.1 Original Development] JSale:
Unfortunately I get random freeze and reboot loop within a minute of booting up, running ARHD 4.0 with the compatibility patch installed with the latest TWRP.

I would be happy to provide a log in the morning if necessary.

Regards

Jack

GT-N8010
[Galaxy Note 10.1 Original Development] lm that guy:
TO prevent that immediately turn on powersave mode at start up.
[Galaxy Note 10.1 Original Development] dsb9938:
I'm running mostly stock with a few tweaks.

I only have a 16GB card so I can't test a 64, but I did not change anything that should affect that if stock does it.

I have no plans to make any other versions.

D

.
[Galaxy Note 10.1 Original Development] ocelofil:
Stupid question...which app I can use for tweaking this kernel? If exist? :D Thx ;)
[Galaxy Note 10.1 Original Development] PurpleSh4rk:
I am having the same issue too.
[Galaxy Note 10.1 Original Development] beeboss:
Nice to see a new kernel! Any possibility to add gpu overclock?:)
[Galaxy Note 10.1 Original Development] lm that guy:
I use setcpu.
[Galaxy Note 10.1 Original Development] pimpmaneaton:
Hey DSB just wanted to verify if cubed supports init.d out of the box or does that need to be added?
[Galaxy Note 10.1 Original Development] dsb9938:
Should work if permissions are set right.

D

.

Sent from somewhere irrelevant.
[Galaxy Note 10.1 Original Development] nerobot:
I was able to install the 1.0.1 on my n8010 without any issues. However when I try to install 1.0.3 I get constant reboots (sometimes only seconds after starting up). So I reinstalled 1.0.1 and for the most part it is working ok.

However, I'm unable to change the votages. When I try to change any of the voltages using system tuner pro I get the following problem (see attached screenshot). This was the same for both versions.

I'm happy to send more details if you wish.
[Galaxy Note 10.1 Original Development] JSale:
Would you care to elaborate upon which parts are not working as you said "for the most part"

I'm still deciding whether or not to use this version.

Regards

Jack
[Galaxy Note 10.1 Original Development] nerobot:
Well really I haven't had any issues with 1.0.1 except the voltage issue mentioned. No fc or forced resets with this version. Can changed frequency to 1.6GHz without any resets to date. So the only part that isn't working for me is the ability to change the voltages.

But as I mentioned, the 1.0.3 version is just too unstable on my n8010.

Hope that helps.
[Galaxy Note 10.1 Original Development] cholywell:
I too kept kept getting reboots of death with 1.0.3. It would reboot within seconds of starting up. It didn't happen on 1.0.1. Had to restore to cwm backup I made before installing the kernel.
[Galaxy Note 10.1 Original Development] dsb9938:
Let's be clear here. I did not make this for the 8010. I made it for the 8013.

Being as I only have the 8013 that is all I can support.

D

.
[Galaxy Note 10.1 Original Development] cholywell:
The only difference between the 8010 and 8013 is the model number.
[Galaxy Note 10.1 Original Development] Banwell13:
Will this work for N800

Sorry for repeating the question.
[Galaxy Note 10.1 Original Development] dsb9938:
Apparently not. Since this seems to work just fine on the 8013.

D

.
[Galaxy Note 10.1 Original Development] Oh_wow:
Getting a reboot when starting antutu..
[Galaxy Note 10.1 Original Development] JSale:
Well, if you ever need a tester for an N8010 build just PM me.

Regards

Jack
[Galaxy Note 10.1 Original Development] eterno13:
Love thia kernel on my note...thanks
[Galaxy Note 10.1 Original Development] dsb9938:
Well folks, I hope this one lasts you a while.

I no longer have my tab and therefore will probably not be updating this.

Glad I could help though.

Enjoy!

D

.
[Galaxy Note 10.1 Original Development] :
Didn't like it? :P
[Galaxy Note 10.1 Original Development] dsb9938:
Not much of a tab guy.

D

.
[Galaxy Note 10.1 Original Development] :
Understandable, too bad, was hoping someone would do some kernel deving for it besides Humber cause I don't do kernels/android work anymore :P
[Galaxy Note 10.1 Original Development] scataldo721:
Does this work with aosp roms???
[Galaxy Note 10.1 Original Development] pimpmaneaton:
That sucks man. Was hoping to have you around for a bit. Glad you did what you did will you had it though and thanks.

---------- Post added at 11:39 PM ---------- Previous post was at 11:39 PM ----------

No it is only for tw based ROMs.
[Galaxy Note 10.1 Original Development] Dsmforlife92:
Well that was fast **** thanks though
[Galaxy Note 10.1 Original Development] demandarin:
I would think Trickster mod app would work fine. Its a kernel/rom tweaker based app. You could also try good ol System Tuner app. Both should be able to let you tweak voltages, CPU speeds, governors, etc.. trickster one is a newer one I use for my nexus7. It does alot. Should work with any device with a custom kernel.
[Galaxy Note 10.1 Original Development] LexusBrian400:
Not here.. I'm getting the same reboots as those other guys on 8013. It'll boot up for about five seconds and then just freezes and reboots over and over.

Thanks anyway though
[Galaxy Note 10.1 Original Development] PurpleSh4rk:
Just use 1.0.1 it works great besides the 64gb SD card support. It's the best performing kernel I've ever used.

Sent from my GT-N8013
[Galaxy Note 10.1 Original Development] lampz:
hoping to have this working on an N8000
[Galaxy Note 10.1 Original Development] Kenchinito:
They are both VERY similar, but not identical. The only difference I know of between the two, is the lack of IR port on the N8010, dunno about other stuff.
[Galaxy Note 10.1 Original Development] damonsmith666:
There is an ir port on the 8010 ...... I have it

xda premium hd is rubbish
[Galaxy Note 10.1 Original Development] aalupatti:
Is it possible to enable usb mass storage mod in this kernel..

This is a big feature missing in our beloved note...
[Galaxy Note 10.1 Original Development] aletheus:
Okay, so is 1.0.3 working or not for the 8013? Ive read the thread, and it seems to be a mixed bag. Im running 1.0.1 and its working fine. No 64gb sd card, so no huge deal, but if I wanted to get a new card....would I have to flash the 1.0.3 kernel to get it working properly?

---
[Galaxy Note 10.1 Original Development] LexusBrian400:
Doesn't work for me. Just reboots when it starts up. 1.01 works OK though.
[Galaxy Note 10.1 Original Development] leo5111:
64 gig microSD work with this kernal?
[Galaxy Note 10.1 Original Development] RETIEF:
64gb doesn't work

No.
[Galaxy Note 10.1 Original Development] kcrudup:
If anyone would like to try another OC kernel, I have one that I've detailed here.
[Galaxy Note 10.1 Original Development] mitchellvii:
Anyone respond that this is working on 8013? I have been having some issues getting cubed to work on 4.1.2 8013.
[Galaxy Note 10.1 Original Development] kcrudup:
At the time I'd started working on the 8000 kernel, Samsung only had one kernel-configuration file for the entire 80XX series of devices. Just recently they've split off the "3G" model configuration, but as of now that split is still logically the same.

I'd give it a shot, as from here it looks like it's a universal fit among (non-LTE) Galaxy Note 10.1 devices.
[Galaxy Note 10.1 Original Development] fishguts:
The first version works perfectly on my N8013, but the second version is where I run into problems. Give the first one a try if you haven't already.
[Galaxy Note 10.1 Original Development] RETIEF:
works.

Used mobile odin to flash this kernal. It is working well.
[Galaxy Note 10.1 Original Development] kcrudup:
Thank you for the feedback- be sure to let me know if you have any problems with it!

I'll be sure to update that thread to indicate that Mobile Odin can be used to flash it (I use an open-source program named "Heimdall" to flash on Linux, as I don't run Windows at all, so Odin and Kies are out). Were you able to just feed the boot.img file to Mobile Odin, or did it need to be repackaged in some way?

Also, which device are you running, and whose ROM?
[Galaxy Note 10.1 Original Development] RETIEF:
Mobile Odin

I am running 8013. I am using Omega 2.0 rom because I had problems with the 2.1.

Mobile Odin loads the boot.img directly so no packaging is necessary. I have tried a variety of apps and wifi connections. Everything is working well. I am running 25mHz-1600mHz.

It seems snappier at 1200 than the stock kernal, but this could be placebo effect.

Quadrant score of 5627 on first run.
[Galaxy Note 10.1 Original Development] argyk:
Finally work with n8010 correct yes or no ???
[Galaxy Note 10.1 Original Development] seshaz:
I dl the image but it doesn't show up in mobile odin, I don't get it
[Galaxy Note 10.1 Original Development] kcrudup:
I've released an update to my kernel.
[Galaxy Note 10.1 Original Development] JSale:
You need to rename the file to "Boot.img" then it will be found by mobile odin. :)
[Galaxy Note 10.1 Original Development] seshaz:
Thanks I just figured that out duh I'm apparently special needs today
[Galaxy Note 10.1 Original Development] Sarutobi:
have this kernel init.d support?
[Galaxy Note 10.1 Original Development] leo5111:
does that work with 8013 on Redemption and can it use a 64 gig sd? thanks
[Galaxy Note 10.1 Original Development] kcrudup:
It's based off the Android Revolution HD 5.0 ROM, which does have init.d support.

I've switched back to one of DarkMan's ROMs for a while and have a boot.img for my kernel that works with that ROM, too. I'll spend a little while longer testing that, then make a post in that thread as well.

---------- Post added at 04:47 PM ---------- Previous post was at 04:44 PM ----------

I can't imagine it wouldn't work with the Redeption ROM (I don't use it, and there's some changes in the ARHD ROM, but nothing that should prevent booting).

I'm assuming by "64GB SD" you really mean ExFAT support, but yes, my kernels support the ExFAT filesystem.
[Galaxy Note 10.1 Original Development] Sarutobi:
i've a problem to boot /sd-ext with mounts2sd, does the kernel support /sd-ext?

EDIT: OK kcrudup i have testet your kernel and tried to use mounts2sd and this app can't boot /sd-ext :(

I use now the Redemption-Kernel from the Redemption 4.1 and this one works with mounts2sd.:fingers-crossed:

The same issue is with the cubed-kernel 1.0.3 :(
[Galaxy Note 10.1 Original Development] kcrudup:
I'm sure that /sd-ext is just a mountpoint issue, and easily solved. If I get any other requests for it I can add it in (but as I don't use it (and really, don't know what it is, but I have an idea) it's not a feature that would normally go into my boot.img).
[Galaxy Note 10.1 Original Development] Sarutobi:
i looked in the threads from the available roms like the redemption or the collective edition and there are some request to use a2sd. in the thread from the colltection edition we are searching for a solution to use add2sd.

i think, when it is possible to integrate a routine that mounts /sd-ext on boot, if /sd-ext exists, was a good idea and app2sd should recognize the /sd-ext as a primary extended sd to use. the other point is, that the cooker from roms, doesn't push any script in the rom for app2sd-using(at the moment the scripts doesn't have any effect and nobody become a2sd or app2sd on running).

i'm not a programmer, but i think there is a way to integrate this feature like the recovery has it build in.
[Galaxy Note 10.1 Original Development] kcrudup:
"Request" here means "another request for including apps2sd in my boot.img", though.

I've merely put out the advanced and modified kernel that I personally use as a daily driver so that other people could use it if they wish- it was never intended to be a general, supported kernel with every kitchen-sink feature in it.
[Galaxy Note 10.1 Original Development] Sarutobi:
that's right, but i wrote this, because this is the thread from the cubed kernel and my idea is a general posted idea for kernels. ;)

it is ok, but you don't write in different threads to draw attention to your kernel, and then you would say only intended as personal use. when you do this, so people think it is a general new kernel for the note 10.1.:crying:
[Galaxy Note 10.1 Original Development] kcrudup:
Uh, the posts I've made about it have always stated it's my own personal kernel that others are merely invited to try; if it were a general kernel I would have started a new thread about it. Use it or not; it's up to you.
[Galaxy Note 10.1 Original Development] Sarutobi:
I've testet it and the Kernel is very good for overclocking and i will test it with some solutions i found here. I send you a PM if it works.

The problem should not occur at the kernel, but rather on the ROM or the correct set of access rights etc.

i'm sure that it is my fault to use your kernel right;)
[Galaxy Note 10.1 Original Development] Ghxoxst:
Doesn anyone have the stock kernel for the gt n8013 on 4.1.2?
[Galaxy Note 10.1 Original Development] kcrudup:
I've also answered your crosspost.
[Galaxy Note 10.1 Original Development] SharpBang:
This kernel works on ARHD 7.0??
[Galaxy Note 10.1 Original Development] chappatti:
Will this be OK on JB 4.3?
[Galaxy Note 10.1 Original Development] sbreen94:
No
[Galaxy Note 10.1 Original Development] ellamaebigmamma:
W will it working in a LG K20 mp260
[Galaxy Note 10.1 Original Development] JJEgan:
Search thread read post 2 .
[Nexus 4 Q&A, Help & Troubleshooting] bitojoe:
Hello, I recently signed up with Straight Talk via AT&T and am not able to get my Data services to connect or send/receive any MMS. I have configured my APN settings multiple times now and actually just got off the phone with straight talk about this issue as well. They were no help.

I am using Straight Talks at&t network and my phone reads this under settings>about phone>status...

Mobile Network Type: HSPA:10

Service State: In service (I have 4 bars)

Mobile Network state: Disconnected

Also when I go to the *#*#4636#*#* menu, It says this...

GPRS service: Disconnected

GSM disconnects: ========DATA=======

How can I fix this and get data and mms to work??

If you find anything out, please tell us! I'm starting to think its something that is wrong with the phone...
[Nexus 4 Q&A, Help & Troubleshooting] mclain1:
interesting... I just joined straight talk today using ATT micro sim and i have the same issue... I also have full bars.

I used the following APN and it didn't work for me.

Straight Talk

APN: att.mvno

Port: 80

Proxy: not set

MMSC: http://mmsc.cingular.com

MMS Proxy: 66.209.11.33

mms port: 80

MCC: 310

MNC: 410

I'm beginning to wonder if straight talk is starting block ATT micro sim activation..?

I was able to get on using their T-Mobile APN settings.

Straight Talk

APN: wap.tracfone

Port: 8080

Proxy: not set

MMSC: http://mmsc.tracfone.com

MMS Proxy: not set

mms port: not set

MCC: 310

MNC: 410
[Nexus 4 Q&A, Help & Troubleshooting] ketjr81:
On the AT&T on ST,

I didn't set the first Port you have listed after APN, I left it as "not set" instead of 80.

To the OP can you list what you set your APN to? Did you look at the Straight Talk thread in general area?

Also it might sound weird but check under Settings > Mobile Network Settings > Data enabled.

For some reason it wouldn't be checked for me when I was flashing a ROM or going back to stock ROM.

These are my settings:

Name: StraightTalk ATT

APN: att.mvno

Proxy: not set

Port: not set

Username: not set

Password: not set

Server: not set

MMSC: http://mmsc.cingular.com

MMS Proxy: 66.209.11.33

MMS Port: 80

MCC: 310

MNC: 410

Authentication type: not set

APN type: default,supl,mms

APN protocol: IPv4

Bearer: Unspecified
[Nexus 4 Q&A, Help & Troubleshooting] UberSlackr:
Here are the APN (Settings>Wireless & Networks.. More...>Mobile networks>Access Point Names) configuration I use to effectivly send/receive MMS:

APN: att.mvno

Proxy: Not set

Port: 80 (some report having better results not setting the Port, but It works for me this way)

Username: Not set

Password: Not set

Server: Not set

MMSC: http://mmsc.cingular.com

MMS proxy: 66.209.11.33

MMS Port: 80

MCC: 310

MNC: 410

Athentication type: PAP or CHAP

APN type: default,supl,mms (no spaces)

APN protocol: IPv4

APN roaming protocol: IPv4

Bearer: Unspecified

Be sure to Save, and Reboot after making changes.

(Also, delete the AT&T APN if its in the list... Click on it, then press menu discard)

Why would the block something they sell and offer service through.

Its also noted on their site, that MMS may not work on some devices

"Updating your APN settings does not guarantee MMS (Multimedia/Picture Messaging) will work." Quoted from StraightTalk.com
[Nexus 4 Q&A, Help & Troubleshooting] Jess813:
I just got off the phone with Straight Talk and I bought a new AT&T micro sim card from Walmart. I asked if they are still supporting it, and they said absolutely, they will continue to. Just FYI
[Nexus 4 Q&A, Help & Troubleshooting] ropesguru:
I had the same thing happen to me today and I am on ATT sim. I sent straight talk an email and they sent back a response asking me to call

855-222-2355. The agent had me make sure my data was on then I turned off the phone for 1 minute why she did something on her side. After that it started working again. I asked her what she did so the next time this happens I could just say this has happened before and this is how they fixed it. The agent stated to just call the number above and state that your data is not working and they will resolve the issue. No help, but that is what happened to me.
[Nexus 4 Q&A, Help & Troubleshooting] pjc123:
Same problem. Straight Talk has been working for months, and all of a sudden yesterday no data. I am lucky if I use data a handful of times a month, so I know I am not over any limits. I am glad I printed out Google maps before I left on my trip as a backup, because it was a 120 mile trek. I went to an AT&T store while on the road out of desperation and a person was kind enough to look at the phone and believes the hardware is OK and it is a Straight Talk issue. I am assuming the "Mobile Network State = Disconnected" I am getting is not a good thing. I will give them a call today.

EDIT: Just got off the phone with Straight Talk. They gave me new APN settings, and this is the first time since I have had Straight Talk (4 months) that I am able to get data at my house (It worked while on the road). It is also the first time I ever saw the little capital "H" near the signal icon, whatever that is. I am in quite a dead zone and previously could only use wifi. Yippee! I also see that "Mobile Network State = Disconnected" had nothing to do with getting data as it works now and it is still listed as Disconnected.

EDIT: These are the new settings that Straight Talk gave me:

Name: Straight Talk

APN: att.mvno

Proxy: not set

Port: not set

Username: not set

Password: not set

Server: not set

MMSC: http://mmsc.cingular.com

MMS Proxy: 66.209.11.33

MMS Port: 80

MCC: 310

MNC: 410

Authentication type: not set

APN type: not set

APN protocol: IPv4

APN roaming protocol: iPv4

Bearer: Unspecified

And these were my original settings

EDIT: As pointed out in a subsequent post below, these are the settings that the person in the AT&T store put in. He erased my original settings, which as I recall I got from the Straight Talk site or the sim card instructions.

Name: ATT WAP

APN: wap.cingular

Proxy: wireless.cingular.com

Port: 80

Username: not set

Password: not set

Server: cingulargprs.com

MMSC: http://mmsc.cingular.com

MMS Proxy: wireless.cingular.com

MMS Port: Not set

MCC: 310

MNC: 410

Authentication type: not set

APN type: default,supl.mms

APN protocol: IPv4

APN roaming protocol: iPv4

Bearer: Unspecified
[Nexus 4 Q&A, Help & Troubleshooting] kzoodroid:
Those original settings weren't for StraightTalk but for AT&T. Two totally different services.

---------- Post added at 10:00 AM ---------- Previous post was at 09:56 AM ----------

FYI the phone won't connect to mobile data until you are using it, its to save the battery. That's why it shows as disconnected in mobile network state. To verify this turn off wifi, if your connect to it, open a browser using your mobile data then check phone status.
[Nexus 4 Q&A, Help & Troubleshooting] pjc123:
Thanks for spotting that. Those are not the original settings I put into the phone; I thought they didn't look right. Apparently yesterday, instead of creating a new APN set, the guy in the AT&T store overwrote my Straight Talk settings while testing out my phone (Not too bright). It really doesn't matter, as neither settings worked properly anyway. I am only getting 1 Mpbs download and 0.10 Mpbs upload at my house now (better than the zero I was getting before), but I am going to have to take a drive later to see what improvement I get.

I see.

EDIT: The highest data speed I am getting is 1.09 Mbps no matter where I go, even running SpeedTest while staring at a several cell towers (Where the signal strength gets better). I gather that is bad from the numbers I see elsewhere?
[Galaxy S Advance I9070 Q&A, Help & Troubleshooting] schiavinato:
Hello there, im a noob here in Xda Forum, so dont be so rude on me.

So, i installed this mod for my notification bar:

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

Because of the blue icons (they are very cool)

Looking for more to mod in my phone i came across this one:

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

Pretty cool too.

Then i decide to join both of them in one

Blue icons+No Brightness control

Here is the result:

Cool ha?

Yes, except for one thing!

The Clock.

I couldnt find the file to edit the color of the clock...

So guys, im asking for you who have more knowledge than me to tell me what file i must edit to turn the clock into blue.

I know that in the first thread(first link) the clock is blue, but after i made de join the clock became white.

So, if anyone know how i edit to blue i will be grateful.
[Galaxy S Advance I9070 Q&A, Help & Troubleshooting] JoaoGuiPan:
That's pretty cool man, good job! :D I tried to do the same thing here but was unsuccesfull :/ All I wanted was tahapapun's great notification/status bar without the brightness slider. You happen to have an edited apk that you could share with us? :p Or a simple overall tutorial, that would be great!

Also, you should ask tahapapun, after all, he turned the clock to blue as well. Tell him about your work in his thread, he'll gladly help you :D