yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Themes and Apps] tbonezx11:
Actually, the funny thing is I have added this mod. It doesn't rotate the time on the lock screen but you still swipe to the right to unlock ... (toward bottom if you were in portrait mode)...no dpi changes or any other mods needed. I'm on rooted, unlocked stock ROM.

What I really wanna know is where I can mod the home screen to scroll continuously...I haven't looked yet. I have the setting on my phone, but haven't played with the N7 enough to find it yet.
[Nexus 7 Themes and Apps] espionage724:
I use Apex. Paid for the Pro version of it, over Nova, since Apex offered... less features for the Pro version :p (in other words, Nova had a lot of stuff in Pro that was non-existent in the free, and I don't like feeling like I "have" to pay in order to use an app efficiently...)
[Nexus 7 Themes and Apps] jersonf:
I used launcher.force_enable_rotation=true inside a new local.prop file in /data. I always use portrait mode and a pin in the lock screen, so portrait only in lock screen is fine by me.

My biggest issue was when in landscape, if I went back into home I would have to rotate from landscape to portrait, then back into landscape and if I pressed a button by mistake again, back into portrait.

I tried the change build.prop dpi settings but didn't like tablet UI for this little thing..... and I don't want to squint.

Tried ultimate rotation control which works great, it also rotates the lockscreen, but costs something like £2 after a 7 trial vs what I use now.

So you paid for less features in general out of principal?

Or did Apex have more free features compared to Nova, and the Pro versions equalled things out on both sides?

Sent from my Nexus 7

Motorola Atrix (v1.10.436)

Nexus 7 (Vanilla root flavour)
[Nexus 7 Themes and Apps] R3dbeaver:
Yes, sorry for not being clear. That tweak to local.prop is to rotate the main desktop and app drawer, just not the lock screen.

The GUI dpi change tweak it's for a complete tablet ui
[Nexus 7 Themes and Apps] thebobp:
another launcher (because the default one doesn't have enough features for my taste anyway)

I don't know why some of your options are listed, like paranoidandroid rom, wtf.
[Nexus 7 Themes and Apps] player911:
Most custom roms include a landscape launcher. This shouldn't be that complicated. The stock launcher simply doesn't do landscape without tweaks. If you run stock, just download Nova or Apex.

I run EOS and its built in tablet mode with Apex.
[Nexus 7 Themes and Apps] uvz:
apex launcher, tablet mode at 160dpi :good:

IMHO apex (free) is the best ;)
[Nexus 7 Themes and Apps] SPreston2001:
Nova FTW!!!
[myTouch 3G Slide Q&A, Help & Troubleshooting] roxy1712:
Hey all-

I'm running CM 7.1.0 RC 1 (long story, but it's the only one where the SYM key still works... otherwise you have go back to 7.0.x) on my MT3GS.

Recently I've noticed that every time I pull out the keyboard, the display gets distorted -- as in, it sort of freezes and fractures along an x-y axis. I've tried all sorts of ways to avoid it, such as flipping it to show landscape and then sliding out the keyboard, but it still manages to break up the screen.

I've also noticed it will do it when you're sliding the keyboard back IN -- same sort of display distortion. The way to remedy it is fairly easy -- just hit the power button to shut the display off/on -- but it's still frustrating.

Anyone else have this issue? Will try to get a screenshot tonight. TIA!
[myTouch 3G Slide Q&A, Help & Troubleshooting] Saem persun:
I don't remember such glitches when I was on CM 7.2 so probably it was fixed later. But the sym button was corrupted. Try to keep keylayout files from the working-sym-setup, update to a recent nightly and try to put saved keyboard setup files back to device.
[myTouch 3G Slide Q&A, Help & Troubleshooting] DocHoliday77:
Could be the ribbon cable is loose or worn. I seem to remember several people with similar problems. Search through these forums. I know ive seen several threads on this in the past.
[myTouch 3G Slide Q&A, Help & Troubleshooting] roxy1712:
Hoping this helps someone else... Replaced the flex cable ribbon and everything works fine now. I think a replacement cable was <$5 on eBay. Only PITA was removing the sticker screw covers on the slider portion. :p
[Windows Phone 7 Q&A, Help & Troubleshooting] danielehk:
Hi, I'm Daniele, I have a HTC 7 pro with wp7.5 installed.

I have a problem: there is a way to always display on the top bar the information about battery status, 3g connection, wifi connection ecc?

Now appear and disappear all the time!

Thanks

Daniele
[Windows Phone 7 Q&A, Help & Troubleshooting] lordmago:
Try to have a look in this thread
[Windows Phone 7 Q&A, Help & Troubleshooting] danielehk:
I think you forgot the link!!
[Windows Phone 7 Q&A, Help & Troubleshooting] lordmago:
Ups... I think I need holidays again... :eek: :D :( :confused:

http://xdaforums.com/showthread.php?t=907971
[Windows Phone 7 Q&A, Help & Troubleshooting] LiFePo4:
I don't think this has been figured out. It was asked in the registry hack thread. Be aware this thread may get moved to Q&A.
[Windows Phone 7 Q&A, Help & Troubleshooting] Magpir:
i recall this has been done before.

cant remember why
[Windows Phone 7 Q&A, Help & Troubleshooting] lordmago:
http://xdaforums.com/showthread.php?t=1702513
[Galaxy Note 10.1 Android Development] brieuwers:
Here is a kernel build for the Samsung Galaxy Note 10.1.

Running on 1704Mhz. With extra 100, 50 and 25Mhz step. So it runs 25 to 1704 instead of 200 to 1400.

Custom bootanimation support. (Standard bootanimation wont work)

Triangle away support.

Update N8000BRV2 (ICS)

-better voltage settings

-better wifi drivers

-BFQ scheduler back

-updated linux version

-other minor tweaks

Update N8000Jelly_OC

-Build for JellyBean

edit.

N8013 and N8010 support pulled back because of the wifi problems

source https://github.com/brieuwers/N8000Kernel

Thanks to Gokhanmoral, Espenfjo, Entropy512 and Franciscofranco.

Flash tar with odin or zip with CWM.

Everything at your own risk.

Greetz Bas.
[Galaxy Note 10.1 Android Development] madsquabbles:
anyone test it on an n8013 yet?
[Galaxy Note 10.1 Android Development] dogfighter03:
n8013 support?

I am also curious to see if this works on the US version (N8013). Anyone willing to give it a shot?
[Galaxy Note 10.1 Android Development] LayZeeDK:
Has anyone tested this yet?
[Galaxy Note 10.1 Android Development] tbogunro:
Lol all these views and no one?
[Galaxy Note 10.1 Android Development] Flash1960:
I use this Kernel on my German N8000, no Problems so far.
[Galaxy Note 10.1 Android Development] kaipro:
I'm using. nothing much different so far.
[Galaxy Note 10.1 Android Development] dogfighter03:
Thanks for the replies, but im asking if this works for the N8013 model, NOT the N8000 model...
[Galaxy Note 10.1 Android Development] brieuwers:
XDA told me that I need to put my source code online to confirm with the gpl license.

So right now Im busy finding out how to work with github after that I will build a N8013 kernel.
[Galaxy Note 10.1 Android Development] Entropy512:
Check my sig for some git tips... which reminds me, Pulser asked me to write up a more detailed guide with more tips (such as how to handle branching and how to handle source releases for test kernels).

Once you've gotten familiar with git, github is as easy as "git push origin". :) Long-term, good git discipline will greatly improve your development workflow.
[Galaxy Note 10.1 Android Development] mitchellvii:
Not to seem greedy but is 1.6 the most we can squeeze out of this thing?
[Galaxy Note 10.1 Android Development] jamesheryanto:
Tested and its been 2days, working great,......fast
[Galaxy Note 10.1 Android Development] tbogunro:
For 8013?
[Galaxy Note 10.1 Android Development] brieuwers:
No this is just a start in fact 1600 isnt a real OC. The settings are already in the kernel made by Samsung they just locked it at 1400.
[Galaxy Note 10.1 Android Development] killjoy90210:
will this work on n8010, nobody seems to be working on the N8010 devise. cant wait for jellybean on my note :silly:
[Galaxy Note 10.1 Android Development] MintyTrebor:
Issue with 5GHz Wifi

After applying this Kernel I was unable to connect to any of my 5GHz WiFi networks. Upon reverting to stock Kernel, the problem resolved.

Kernel seemed stable in all other aspects.

Running Stock XXALI1 (Rooted)

Thanks
[Galaxy Note 10.1 Android Development] tmaurice:
OK - I took the plunge and tried this on a N8013. Only issue I have found is, as mentioned by MintyTrebor, with wifi. Both my 2.4 and 5Ghz work (as well as tether to the phone), but will occasionally disconnect - all I have to do to get it back is turn wifi on/off and things are good. Running at 1.6 on all cores (system tuner), very snappy (nova launcher). Benchmark tests really bumped up with this kernel. No problems with pen apps. Had one freeze, but that was after I'd installed twrp recovery.

Think I'll leave this kernel on for another day and see how the battery life is. Be great if someone could crank one of these out specifically for the N8013 to get rid of the wifi issue.
[Galaxy Note 10.1 Android Development] brieuwers:
Thanks for testing kernel. Im gonna build kernel for 8013 and 8010 within 24 hours.
[Galaxy Note 10.1 Android Development] killjoy90210:
tried my gt-n8010 and works ok upto now. not noticed anything with wireless, but theres still time lol :cowboy:
[Galaxy Note 10.1 Android Development] mitchellvii:
Thanks for the 8013 support. I'll wait for a braver soul to try it first :)

Do you notice improved performance at 1600? Quadrant?
[Galaxy Note 10.1 Android Development] globen:
So just to be clear this doesnt work on 8013? Cause I wanna try it but cautiously lurking.:)
[Galaxy Note 10.1 Android Development] ttreed07:
I'm personally running this on my 8013 on the revolution 4.0 ROM and it runs fine, just make sure you set gov to ondemand or you'll get crazy reboots on 8013.
[Galaxy Note 10.1 Android Development] mpegispg:
I am expecting problems with wifi: When turning wifi off I can not turn it on again!

device: N 8000 with 4.1.2 latest German version

Anyone else noticed this problem or has idea for solution?
[Galaxy Note 10.1 Android Development] monadzback:
I am running this on my 8013. Runs fine with on demand, however, restarts during my charging and requires a hard restart.
[Galaxy Note 10.1 Android Development] leonbarroso:
it is freezing after boot, on lockscreen

maybe becaus it is set at maximum clock
[Galaxy Note 10.1 Android Development] Kasha:
Just wanted to say that this kernel works great on latest Omega 2.1.

I've installed Xcstacy, but for some reason the tab kept rebooting at 1704 and freezing at 1800.

This one works just fine. Great job, developer!
[Galaxy Note 10.1 Android Development] LiMITZERO:
tnx works perfect on my note 10.1 (GT-N8000) stable at 1.7Ghz :laugh:
[Galaxy Note 10.1 Android Development] GDT:
I'd like to know source version base for JB version .

edit: I flashed zip but it keeps rebooting on Samsung Note 10.1 logo. I'm on latest Stocky Rom. What can I do?
[Galaxy Note 10.1 Android Development] LiMITZERO:
in recovery try to wipe the ff. cache partition, dalvic cache and data/factory reset.
[Galaxy Note 10.1 Android Development] kcrudup:
NO. Folks should stop telling people to Factory Reset (nor all those cache wipes)- that's never going to fix bootloops caused by flashing a kernel.

The issue is the overclocking- your Note just can't handle it.
[Galaxy Note 10.1 Android Development] GDT:
I haven't overclocked yet
[Galaxy Note 10.1 Android Development] kcrudup:
OC-able kernels usually have the OC turned on by default, and that's especially true with our GNotes, as Samsung has code in the TWiz base that ramps up the speed to the highest the kernel is capable of during boot.

Bottom line is if a kernel that otherwise works for others bootloops for you, it's a kernel issue, 99% due to OCing, and "wiping caches" and/or "factory resets" won't fix anything and only waste your time and ruin your setup.

Try this kernel and let me know what happens.
[Galaxy Note 10.1 Android Development] GDT:
this is stock mj3 kernel not overclocked, right? This works for me.
[Galaxy Note 10.1 Android Development] kcrudup:
Nope, that's my highly-refined custom kernel, but yes, non-OCed. Now try this kernel. This is the exact same kernel as the previous one, just OCed to 1.6GHz. Let me know if it bootloops on you.
[Galaxy Note 10.1 Android Development] GDT:
The OC version worked aswell
[Galaxy Note 10.1 Android Development] kcrudup:
That's likely because I only go up to 1.6GHz (snd don't change the voltages too much). Be on the lookout for any crashes.

But if it works for you, you're welcome to it.
[Galaxy Note 10.1 Android Development] esgie:
At last it works for me!

Thanks.

Any chance of exfat modules (or native support)?
[Galaxy Note 10.1 Android Development] esgie:
Sry for double post but maybe it'll help someone with 64gb sdcard to use it when running your kernel. (Tested on oc'ed version).

Not a native kernel module but it's working anyway...

First, I have flashed zip file from this topic (the newest one) under TWRP (CWM should be good aswell)

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

AftEr reboot, I have found out that there seem to be a strange incompatibility between cm and tw rom which caused the card to mount under /storage/extSdCard:/storage/UsbDriveA/storage/... (well, it was a path consisting of 20 subdirs or so...).

So, I have changed the contents of newly created init.d script (called "50fuse-mountsd") by deleting everything and inputting just simple:

#!/system/bin/sh
sleep 5
mount.exfat-fuse -o rw,dirsync,noatime,umask=0 /dev/block/mmcblk1p1 /storage/extSdCard
exit 0

Saved the file, rebooted again and... voila ;)

Everything working great, directory bind mounted external card dirs just as it was mounting it on stock kernel, etc.

Haven't tested if it's working with USB yet!!!

Well, if i may have a request: would it be a big problem to compile frandom.ko for your kernel?

It's an alternative entropy generator, as the tests say - a lot more efficient than seeder (and stock ofc).

However it has to be compiled as a module...

It would be great to bring it to our devices.

Please note that the source code is quite short and i suppose that it won't be hard to compile it, however i am not a very experienced programmer nor a programmer at all so i may be wrong.

Anyway thank u very much for your work, it shall be really appreciated :)

E dit:

Uhhh reboots, from time to time because of far too low voltage as for my device. And it is impossible to change the voltages.. ; (
[Galaxy Note 10.1 Android Development] kcrudup:
If you find me either source code or a relevant XDA/etc. thread, sure, I'll look into it. The jury is still out on the effects of entropy on Android lag, though- and I have a couple of patches from upstream already in my kernels that are supposed to help with that (yet I still lag from time-to-time, and that really does appear to be storage-based, as usual, more than any other effect).

(BTW, I'd tried playing with voltages to keep the OCed tablets from rebooting- and it did more harm than good, as the higher voltages tended (at least on the small sample size of 3 tablets I was able to test on) to make the CPU go into Thermal Throttle far more often, negating any benefit from the OC.)
[Galaxy Note 10.1 Android Development] kcrudup:
Huh ... so I'd added the "frandom" source to my kernel, then changed the init scripts so that Android would use that vs. the kernel's standard /dev/{u}random device. I was skeptical at first, but there might be something to this "frandom" device, after all ...!

Anyway, here's an "frandom"-enabled kernel, and here's a non-OC version of same. Tell me if you're seeing what I'm seeing.
[Galaxy Note 10.1 Android Development] esgie:
Well, my device hasn't got any issues when running 1600mhz at 1375mV, no throttling or temperature changes, and no reboot even after some stress tests ive made. It is working well using both xcstasy kernel and stock kernel+tegrak overclock app so i am completely sure anout what im saying.

Your 1300mV is just a little bit too small voltage for my CPU to work stable. As i discovered, differences between voltage settings of your kernel and my device are no longer visible in the range of 0 - 1200mhz, over 1200mhz and especially over 1400mhz my device needs significantly higher voltage setting than your; however it does not result in abnormal heating, thermal throtting, cpu core melting or other natural disasters ;)

In result, your kernel (even non-oced) is booting and is working well for a few minutes (both kernels never rebooted on boot sequence!!), however after launching some advanced tasks - it reboots or freezees because of staying too long in a frequencies which requires more voltage than it receiveso ; (

This truly makes testing hard and also impossible for everyday use, for me at least. As the default voltage values used by you are enough to boot the device, they are still not appropriate when it comes to heavy calculations. Desirable solution: to unlock the voltage table so users can modify voltages themselves if needeed, without modifying the default voltage values, as they are good enough to boot and work without reboot for long enough to let user change the hi-freqs voltages for - probably - every device...

Well is there any easy solution for locked voltages? Or (as i suppose) this feature has to be included in a kernel itself? Is it a lot of work to unlock it?

Good that youve interested in this frandom stuff, as it may be the near-ultimate solution for that crappy lagging issues we all hate... i am euphoric about possible testing, i must admit ;)

Thank you.
[Galaxy Note 10.1 Android Development] kcrudup:
I don't see how this can happen on my non-OC kernel- it has exactly the same voltages and frequencies as Samsung does for the range 1.4GHz-200MHz, and all I've done is add 100/50/25MHz. If you're getting reboots with my non-OCed kernel, there's gotta be something wrong with your device (I can't think of any other explanation).

Now, if you're using my OCed kernel, remember that Samsung has got code in TW that queries the kernel for its highest possible speed, then explicitly sets your device to use that speed, independent of any apps that might change the speed ("SetCPU", et al.). I couldn't do anything to prevent this (as we don't have TWiz source), which is why I make explicit non-OCed versions of my kernel too.

Yeah, but I'm probably not going to implement that.

I have to thank you for that hint! This has seriously speeded up my tablet noticably! I'll be modifying the kernel's character-device tables to use the "frandom" versions directly from /dev in an upcoming release (mostly so I won't have a possible race-condition that exists now when I flip the /dev entries in user-space in my boot scripts).
[Galaxy Note 10.1 Android Development] GDT:
[MENTION=451204]kcrudup[/MENTION]: don't you have a thread for your kernel? I'm very happy with it.
[Galaxy Note 10.1 Android Development] kcrudup:
No, and I probably won't (especially now that the 3.0 kernel has been End-of-Lifed at the -101 version and updates may be few and far-between unless I see something compeling from upstream). I don't have the patience for a seperate thread (unless all it is is updates).
[Galaxy Note 10.1 Android Development] sudisk:
[MENTION=451204]kcrudup[/MENTION]: does your kernel has exfat support?

I tried the frandom version and I couldn't see my ext sdcard anymore.
[Galaxy Note 10.1 Android Development] kcrudup:
OK, good to know- if the non-OCed version had still looped on you I'd've been worried.

If you can give me your 1.3 GHz+ voltages, I'll look into it. FWIW, the older voltages (before I'd normalized them) were:

+ /* ASV0, ASV1, ASV2, ASV3, ASV4, ASV5, ASV6, ASV7, ASV8, ASV9, ASV10, ASV11 */
+ { 1450000, 1425000, 1425000, 1400000, 1400000, 1400000, 1400000, 1375000, 1350000, 1350000, 1350000, 1325000 }, /* 1.7 Ghz */
+ { 1325000, 1312500, 1300000, 1287500, 1300000, 1287500, 1275000, 1250000, 1250000, 1237500, 1225000, 1212500 }, /* 1.6 GHz */
+ { 1325000, 1312500, 1300000, 1287500, 1300000, 1287500, 1275000, 1250000, 1250000, 1237500, 1225000, 1212500 }, /* 1.5 GHz */
+ { 1325000, 1312500, 1300000, 1287500, 1300000, 1287500, 1275000, 1250000, 1250000, 1237500, 1225000, 1212500 }, /* 1.4 GHz */
+ { 1300000, 1275000, 1237500, 1237500, 1250000, 1250000, 1237500, 1212500, 1200000, 1200000, 1187500, 1175000 }, /* 1.3 GHz */
<snip>

Thanks for this- I've had situations where I've also been hung up at the end of the boot sequence and have had to restore the entire /data directory.

I am really surprised how well it's working, especially since there's a lot of discussion as to whether any Entropy fixes are/n't placebo. What's nice about a kernel-based solution like "frandom" is it doesn't affect the system like the old "seeder" apps do.

I've also modified some of the kernel tunables using guidelines used in the "Supercharger V6" thread (w/o all the intrusive scripting used by that method, and ignoring some of the Low-Memory Killer changes and Dalvik VM Heap-size mods). I've been running it for a couple of days and seem to like it- I'll be pushing a kernel for that for people to try out soon.

I've also patched a potential kernel exploit listed here that'll be in my next kernel, too.

Do you have a site with source for it?
[Galaxy Note 10.1 Android Development] bucklee:
Hi Krudcup, was trying to use your kernels and my microSD (64GB) keeps getting ejected. Also all the Language is in Polish, this is probably something to do with ARHD 9.0 I am running. I'm also running 8013. Any ideas?

Now I'm just stuck in the samsung Logo.....:-\
[Galaxy Note 10.1 Android Development] sudisk:
I thanked your post by mistake.

The answer to your first question is in post #206.

For the second one, are you using super su v1.69? There is a bug in that version.
[Galaxy Note 10.1 Android Development] esgie:
Well, the problem is when you are getting this kind of error in 5 minutes before planned backup (after a month without doing it...) in a almost-perfectly-configured-device with 500+ apps installed :D

However, I hereby confirm again that this method IS WORKING and it let us to recover from corruption @ data partition...

Below is my profile (still working stable on your kernel, after dealing with the "change your voltages in 20 secs after boot or die" method!)

frequency=1600000,1500000,1400000,1300000,1200000,1100000,1000000,900000,800000,700000,600000,500000,400000,300000,200000,100000,50000,25000
core_voltage=1375,1325,1262,1212,1175,1125,1050,987,975,962,937,937,925,900,875,862,862,850
scaling_governor=pegasusq
scaling_min_freq=100000
scaling_max_freq=1600000

Please ignore two last settings (for 50k and 25k MHz) because those frequencies causes a reboot on my device after some time and it is no difference what voltage I have set for them.

Voltages for 1600 - 100 MHz had been measured experimentally (after a long night with 100+ crashes of the system hehe) long time ago. They shall be considered as an maximum undervoltage settings - every single setting will cause an unstability on my device if lowered, even a little bit (by "unstability" I mean crash when running 10 minute-full-stress-test, even if it happened as late as after a few mins... as you can see, I am well prepared :D )

As to the fiops scheduler:

https://github.com/DerTeufel/android_kernel_samsung_smdk4412/blob/dualboot/block/fiops-iosched.c

This is a repo of the kernel for N7100 (Note 2) which I am using at the moment and which offers a great performance, and a lot of features.

(incl. dual boot CyanogenMod up to 4.3.1 with Stock Samsung ROM), and as the dev is a very active person I am convinced that he has integrated all the essential patches/code updates until today...

I think that the CPU governor "devilq" (source should be available at the same git I suppose) is also something worth looking.

[MENTION=3965834]bucklee[/MENTION]

That's right, see the very beginning of my too-long post #206 for extFat solution

The second answer given to you by user sudisk is good too - today I woke up with greek language turned on, for example... It is not kernel related afaik. We should wait for an update...