yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab  Android Development] mike2nl:
Possible what i have found is old and everybody knows it ???

Has someone seen the both eastereggs from CM when you...

1. goto Settings -> About tablet

- and touch very fast multiple times the entry: Android version 4.4.2

a screen with the letter 'K' will be visible. Touch this multiple times

too and see what comes up

2. goto Settings -> About tablet

- and touch very fast multiple times the entry: CyanogenMod version 11-.....

a screen with the letter 'CM' will be visible. Touch this multiple times

too and see what comes up

And now the question: who has seen this before me?

Is that an old info or it is me that is possible to old :D
[Galaxy Tab  Android Development] Ichijoe:
Google have been doing that for yonks now. it really isn't anything new. But, its still cool to point out. 'cause there's always some n00b out there that doesn't know about it. I guess.

More ticked off at the moment that I have no real safe way to unmount my Micro SDHC Card w/o having to shut my phablet off first!

Looks like I'll be back on CM10 again soon enough. This is a major deal breaker! I just burnt out one crappy SanDisk Card a few months back. I was able to get an RMA. So I'm not about to go yanking on this Card when I don't have to. But for the times I do...

I NEED TO BE ABLE TO UNMOUNT THE FECKING THING!
[Galaxy Tab  Android Development] mike2nl:
Hi Ichijoe,

the NooB can tell you how it works. :confused:

You have terminal emulator?

- start it

- type su <ENTER>

- allow superuser to do so

- type mount <ENTER>

- search for sdcard1 (on my site it is: /mnt/media_rw/sdcard1)

- type umount /mnt/media_rw/sdcard1 <ENTER>

- type mount <ENTER> again and search for it (that entry must be no longer visible)

- now search for /storage/sdcard1 (so on my site)

- type umount /storage/sdcard1 <ENTER>

- type mount and search for anything for sdcard1, oops she is away

....now you can remove the sdcard

To mount it again write down all devices that are conected to sdcard1, or reboot your tablet

before you umont anything...

It is easy to use (Unix and Linux knowhow) 'cause there's always some n00b out there that

doesn't know about it. I guess.
[Galaxy Tab  Android Development] Ichijoe:
lol or someone can... And should fix the option to mount, and unmount from the "Settings" -> "Storage" ya know like the way its always been?

BTW: Thanks for the explanation above! but, it this is how it is on 4.2.2 at the moment I'm reverting back to the last working CM10. END!

Everything in this ROM has been exceptional, up to this point. But having to go though a zillion hoops to do something that only took Three Clicks. Is quite frankly unacceptable.

I pray this gets the attention it deserves. Then I'll look forward to reinstalling this again.

I know that this isn't anyones direct fault here, and that this um, Bug is affecting CM11 directly. Or so a Google search would have me believe. So I'm not out here trying to diss any ones work here. 'cause I'm not.

I'll will continue to monitoring this Site, in the hopes that this gets fixed.

But for now C'ya!
[Galaxy Tab  Android Development] mike2nl:
Why you cry here on XDA in the fantastic thread from storm?

Goto the website of Cyanogen.org and pull a request or a bug...

Why you won't learn in that case. Only shouting (the big letters)...

Gerneric BTW:

I don't understand that behavior here on XDA. In the past times

of XDA was that a point that the one gets trouble with the admins

or at least with the OP. I knew why i am more often away from XDA.
[Galaxy Tab  Android Development] w.sukiyaki:
Thanks... Manage to flash cm11....

---------- Post added at 02:25 AM ---------- Previous post was at 02:22 AM ----------

Hi.. Is it possible to increase p1 total ram using extcard.. Any idea guys..
[Galaxy Tab  Android Development] Ichijoe:
My guess Android happened... Like it or not, this place has turned into the Grand Central Station of Device ROMs.

Perhaps it was wrong for me to expect a working ROM. 'cause I really wasn't I know how this Site should work, and I do respect it.

As to filing a bug report others have already posted about it. I added my Mustard in such Threads there already, as well.

I'm NOT some 1337 hacker, and I most certainly don't play One on Television either. I'm just some schmuck looking to update his tablets to something newer then CM10. That can have the missing (secret driver FM Radio), and as many broken Cameras as, needs be. But I must be able to both quickly and, moreover safely be able to unmount my SD Cards on any given whim. And CM11 is making that impossible at the moment. And I have no clue as to why? Perhaps they all use Nexus stuff over there?

In any case I'm back on CM10.1.3 currently, and lol I can mount and, unmount the SD Card again! Well that's gonna have to good enough then.

If I seemed kinda shouty then I beg your leave. But this is kinda of a big deal for me. And you can't expect me to explain that to an 80 year old Mom who has never even heard of Linux. Much less knows how to use the command line.
[Galaxy Tab  Android Development] Mjoelnir77:
Will you copy partition changes from humberos in the future?
[Galaxy Tab  Android Development] storm31:
Guys, i think it is enought. [MENTION=421631]Ichijoe[/MENTION] thank you for reporting the bug with sd card: i have tried the last cm nightly (051214) - you cannot unmount sd card here also - i think i've found the commit in Settings. I will post later Settings.apk if i can fix this.

If i merge this in this rom we have incompatibility with cm nightlies. Galaxy s has this layout a long time already (data/data, system partition 600 MB), but i don't know if it brings benefits..
[Galaxy Tab  Android Development] metterschling:
If you dont't remove/change your sdext, you might try to create a swap partition on it. To do so, iirc CWM can repartition accordingly ... of course with data loss. I don't use this with my P1000, but swap on sdext worked well to get more RAM for CM10 on an ancient LG phone whixh is still in use ...
[Galaxy Tab  Android Development] Mjoelnir77:
According to humberos it brings some speed improvement, but i did not try a recent omni build and cannot tell a first hand experience.

How relevant is compatibility with CM nightlies anyway? You cherry pick quite a lot of stuff so people probably do not jump over to CM nightlies after being here ...
[Galaxy Tab  Android Development] RogerG:
thanks for the post on enabling the advanced features metterschling! can you please confirm that panorama mode is working for you? photo-, focus- and photosphere-modes work fine for me, but panorama always either FCs, displays a completely black screen, or becomes unresponsive when trying to take a pic.
[Galaxy Tab  Android Development] Ichijoe:
Front or Back? I tried this on my P1000... IIRC everything was working bar the ability of the Front Video Recording Camera. So yeah I know for fact that Panorama was working for the Rear Camera at lest. I think on the front Camera too... But, TBH I can't recall that so clearly at the moment. As due to the much banged on (by yours truly), disability to remove the SD Card. I've since downgraded back to CM10 again T_T.

So I don't have a way to give you a better answer. FTM.

I really hope that this Bug can get quashed soon. As I really did like that ROM otherwise.
[Galaxy Tab  Android Development] metterschling:
Panorama (rear cam only) is working here, just checked with storm31's latest (20140512) build. You might try to clear Camera app data and/or flash the latest gapps: http://goo.im/devs/BaNkS/GApps/4.4.2
[Galaxy Tab  Android Development] ulev:
switching off/on zram

[MENTION=3380725]storm31[/MENTION]: I still had a lot of memory related time lags in my admittedly heavily loaded set up with the 0502 ROM which caused me again to revert to 0405 where this problem never existed. I do suspect, the "stuttering" is related to the zram feature. So my question: would it be possible to have a switch in the settings to turn zram on/off like in the older CM days?

Alternatively, at least for testing, I would also be happy to change the necessary flags in any configuration files, if that is a possibility.
[Galaxy Tab  Android Development] storm31:
If something goes wrong i can test nightlies - then there are 2 options: my commits are bad or cm commits have changes that don't work with our device:). Of course system size with 600 MB is sublime, but i would wait a while. We can wait or not?

I have found the commits and have one build with option for sd card unmounting. But i have current another problem: media server (in the build) goes crazy. I must test it. Next build will have sd card unmounting.

You can try "Trickster Mod" app from play store. This app have posibility to disable ZRAM. I don't know if it does work really...
[Galaxy Tab  Android Development] mike2nl:
@storm31:

i have tested again my apk's AndroidSensors & Sensor Kinetics from the app store.

What i have found is: (possible known as issues in CM?)

- Accelerometer (NOT working)

- Gyroscope (working)

- Magnetometer (NOT working)

- Gravity Sensor (NOT working)

- Linaer Acceleration (NOT working)

- Rotation Sensor (NOT working)

- Light Sensor (working)

More in the file i have uploaded here: LINK. You know about it?

I will search on CM.org too....
[Galaxy Tab  Android Development] storm31:
Not really..I hope someone ([MENTION=5641077]booogle[/MENTION], [MENTION=5395790]Ukitaki[/MENTION]?) can test current omni builds with this app. If we have same result on omni then we have a problem. I haven't debug cable for kernel debugging and haven't knowledge about kernel. But i will try my best...
[Galaxy Tab  Android Development] mike2nl:
@storm31:

good to hear that you are noticed it. So i hope we have aproblem ;), then we will have a solution, possible..

I will take a look in your GitHub about the drivers in the kernel

UPDATE:

right now i am in:

android_kernel_samsung_aries / drivers / staging / iio / magnetometer /

on github i can't find the Magnetometer sensor AK8973.

What there is:

SENSORS_AK8975 & SENSORS_HMC5843

When that place is right (???) on GitHub, we miss things.

OOPS, found it in: android_kernel_samsung_aries / drivers / misc / ak8973.c

Upodate 2:

The half of the sensors i coud not find with the search function.

- Gravity Sensor

- Linaer Acceleration Sensor

- Rotation Vector Sensor

The rest i have found...
[Galaxy Tab  Android Development] storm31:
:), current branch is cm-11.0-google2. If you have time, you can search in omni/humberos repo also: https://github.com/omnirom/android_kernel_samsung_aries. If we miss things, then i can commit these
[Galaxy Tab  Android Development] storm31:
newer rom: cm-20140516, Google Cam recording does work now --> thanks to pawitp, Sd card Unmounting fixed..., newer cm commits
[Galaxy Tab  Android Development] mike2nl:
Thank You storm for the info, will check it 100% sure...

But a little and very promising update about cm-11-20140512-UNOFFICIAL-p1:

I have test it again with Android Sensors & Sensor Kinetics:

- Accelerometer (NOT working) NOW working

- Gyroscope (working) Still working

- Magnetometer (NOT working) NOW working

- Gravity Sensor (NOT working) Still NOT working

- Linaer Acceleration (NOT working) Still NOT working

- Rotation Sensor (NOT working) Still NOT working

- Light Sensor (working) Still working

So that means that the last update has fixed some sensors.

2 more then with cm-11-20140502-UNOFFICIAL-p1.

I have not tested version cm-11-20140516-UNOFFICIAL-p1.

That i will do today with the next update ;).

I will make a google document (public) to write down the needed

information. Possible as a little help for the CM devs and for you too.

So everyone can take a look to check things. I will publish all tests

and the used apk's. Hints and tips for testing are allways welcome.

BTW:

I do that because i am very interested in sensors and the technic

behind them. So i wish to have all of them running on my tab.
[Galaxy Tab  Android Development] Ukitaki:
Hi! here is my Omni Rom Test
[Galaxy Tab  Android Development] mike2nl:
Hi Ukitaki,

thanks for the information. So as i see all sensors on your site

are working well.

It is very helpfull for the search on issues....

UPDATE: @storm31:

- the file with information grows fast. A lot of sensors, code

and info links. Will upload that file shortly today....

Update 2:

file is updated LINK
[Galaxy Tab  Android Development] Ukitaki:
i used Sensor Kinetics from Google Play Store
[Galaxy Tab  Android Development] mike2nl:
;), i had must read better first before i had asked. But Thank you in any way.

My screenshot with Sensor Kinetics on ROM: cm-11-20140512-UNOFFICIAL-p1

And the 2nd & the 3rd one is with AndroSensor. The very strange thing is that after a

reboot ,in the very early morning, i get all sensors running. Really strange issue.

Will reboot again. Possible some drivers/code in Sensor Kinetics are very different

then in AndroSensor. I had tested Sensor Kinetics first a half hour ago. Mhhh, have to look deeper.

What i have seen is that AndroSensor needs around 1..4 minutes to get all values (2nd srceeny).

Will test it with the updated ROM too. Also i will reflash the ROM from 02/05 to see

was that a wrong flash with the first test. Hope it was false issue (puuuh)
[Galaxy Tab  Android Development] Ukitaki:
here is my AndroSensor sensor test.
[Galaxy Tab  Android Development] mike2nl:
Mhh, now i am a little bit in the war. My readings were even good.

Now after a reboot only 4 sensors are working. If there something wrong

with my flash that i miss things or they have mistakes?

Will flash again today and will report later. Possible it was an issuye

with the version 02/05. Good question...
[Galaxy Tab  Android Development] ulev:
Tried Trickster Mod with ZRAM partition off on a backup of the 2014.05.02. ROM (with low mem switch on false) and for a few minutes also on a fresh 2014.05.12. upgrade until the battery went off (Africa & electricity don't like each other!). It seems to work. Switching occurs during start up, so the result seems a bit unclear, but the ZRAM partition is obviously unmounted after some initial use(?) during start up.

So far things are more smooth in the "off" state for me. Will do more testing also with the latest ROM once it gets to Africa :)

I am also planning an OMNI test over the weekend which should get exciting.

Sensors: I see sensors on an off all the time, especially magnetic, acceleration and gravity. That problem has been around for a very long time, probably since leaving GB... Usually a reboot fixes things until they come back again. Will do some tests too this weekend.

Addition:

All sensors working for me on AndroSensor. I am on 2014.05.12.
[Galaxy Tab  Android Development] Ichijoe:
Ok I just installed the last update cm-11-20140516, and I can now safely unmount my SD Card. THANK YOU VERY MUCH!! lol! :victory:

Now it seems I have a new problem with this ROM, One that I hold almost as dear in fact, and that is AdAway.

I'd assume that this unlike say OmniROM which isn't rooted, was. And I'm not to disapointed to see Superuser pop up either asking me to give it its privileges either. However, even after installing it. It does not do its job. When I try to set it to disable blocking I'm greeted by some unknown error. Inside AdAway saying that something had failed.

I had tried to wipe the Cache, and Dalvik - didn't work.

I also tried to locate the fix permission(s) in CWR - not there.

I even tried to install SuperSU from Market Oddly this to does NOT WORK as it always want to mod / flash the CWR with its code.

Not sure whats wrong here. But, this is the first time I've ever had this type of problem with AdAway on my Device.

*EDIT* Ok I see that, I might be running an out of date version of AdAway. So I'm gonna clean my stuff up and try again with the newer version now.

*Second Edit* Ok I managed to wipe my Phablet, and run a clean install of this ROM again. Having installed the most recent AdAway 2.8.1 (From Feb 2014), its all good again.

Thank you so very much for having cooked up this ROM for us! Now come the real test how does it get on with a few days of use? ....Lets find out :)
[Galaxy Tab  Android Development] mike2nl:
Hi Ichijoe,

thanks for the info about AdAway. I was aking myself will it work because

some issues, i have seen, with the AdAway source code i have found after

re-engineering. Thanks from the n00b ;).

BTW: @storm31:

after installing cm-11-20140516-UNOFFICIAL-p1 i have different sensor issues.

They will run but with different delays after restarting the apps. Also after a reboot

they first working, then after restarting the apps they get that delay.

About my postings i got a really very interesting PM and a lot others about that issue.

What i can't understand is why the users do that in PM's. It is ok but it is better here

or in the other threads with all these new roms. I think all devs have an issue with

the base code. Found things in OMNI rom drivers and kernel, but yeah who i am....

when is ask one of the ?gurus?, so i have done yesterday, they tell me that noobs don't

understand anything in that way (i make everyday my own stuff in UNIX & LINUX(gentoo)).

Is that the way of XDA?

But storm i will PM you with an idea. I will do that in that way because i will not flood

any longer your own thread with the issues from me or better with all that sensor stuff.
[Galaxy Tab  Android Development] storm31:
[MENTION=1916507]mike2nl[/MENTION],

saidly i have only very basic knowledge about linux internals. It isn't possible for me to debug kernel (no cable and knowledge). In real life/work i use c#/JS for web and bussines apps. I have tried to read some advanced books for kernel/linux developing - but the writer of books says that the way to kernel developing is very difficult and it will be more difficult with each newer kernel release. However, i will try my best and any help is welcome. If i have some free time, i will fork omni or older humberos kernel and probably will release one build with this kernel. Perhaps it brings us further
[Galaxy Tab  Android Development] Ichijoe:
I have to say i was full of crap yesterday about getting it to work. I thought I had it working when in fact I had not.

I'm no great hacker but, with what eyes with which I can see. It seems to be a problem with SELinux, not allowing us to symlink directly to /data/data. I tryed reseting all the "Permissions", I've even gone as far to set the symlink myself. It seems to be applied. But, its just not sticking for some reason. Again from what I can understand of it. This doesn't happen so long as you can write into /system/etc. Unfortunatly this is not possible currently for this ROM, as there is "Not enough space" in /system/etc.

So, and I'd hate to sound like a needy arse, but is it possible to boost the /system/etc partition up a notch to cover this?

I've tried other CM11 builds before + Omni, and I'm sure that this was the only ROM I had ever ran into that had this issue.

I had mentioned that I was on an older version (unbeknownst to me), of Adaway. v2.8.0. Updating to v2.8.1 however has not fixed my problem though.

If you could somehow address this I'd think you'd have 99.99999% of nailed up tight.

Just outta interest does any of your work filter back into the Official Nightlys? Cause. to me they seem as constantly broken as ever.

Again thank you so much for all your effort.
[Galaxy Tab  Android Development] storm31:
System partition has in 4.4 builds /system/priv-app folder for some apps. These apps have more rights as other /system/app apps. I think it has to do with selinux.

About not enought space: i use banks gapps minimal and have about 80 MB free in system partition. By switching from other roms i would format system and wipe data. The best way is restocking. Humberos has changed the layout for omni now: system has 600 MB (my rom/cm about 430 MB), data has 1,5 GB (cm /my rom 2 GB). Perhaps i commit the omni layout later...

"My work" isn't really my work. I collect commits from omni/cm (p1 and galaxy s) and try to get best with my, objectively, small knowledge about android platform/linux kernel. I'm not android/linux developer and i think this work doesn't interest cm developer: nothing from this rom filter back into the official nightlies.
[Galaxy Tab  Android Development] metterschling:
There is no /system/etc partition. Open a terminal and use the mount and df commands to verify. The mount command will show that /system is mounted read-only, therefore you cannot write to it unless you re-mount it r/w (mount -o remount,rw /system or use the CM file manager in su mode and click on the lock icon).

On my GT the df command shows 62 MB free on the /system partition for storm31s latest build...I always format /system before updating the ROM...
[Galaxy Tab  Android Development] ulev:
What are the facts here? All Adaway is doing is to write to the hosts file which is located in system/etc. That is not a partition, but a folder within the /system partition. That's why Adaway needs SU rights...:p

BTW, this only happens once every time new host files are downloaded.

If Adaway can't write to system, it doesn't have SU rights or you have installed extra applications there, otherwise, like others have said before, there are about 80MB free which is way enough for an increased hosts file. Use any partition tool to check your free space.

I am using Adaway 2.7 for ages on every new ROM. Up to the current 05.16. no problem at all...

---------- Post added at 03:42 PM ---------- Previous post was at 03:36 PM ----------

Adaway is working well for me for ages. Don't see the issues.

All sensors are doing well for me in 2014.05.16. Tested with AndroSensor after several reboots. Always ok so far. Maybe you want to have a closer look at your hardware...
[Galaxy Tab  Android Development] metterschling:
Same here ... BUT as I wrote in this or another SGT thread some time ago, failing sensors is an intermittent problem that happens to others and me from time to time since at least CM10 (I started with CM9) ... Although a little inconvenient, I can live with the fact that a re-boot always gets the sensors back to operational state.

Now some experiences that may help here. The last time I experienced the issue, I was navigating with GPS and at the same time rotating the Tab. After stopping the navigation, the sensors were gone. Another way is to play a game that uses rotation sensors while enforcing landscape mode (I normally operate the Tab in vertical/phone mode).

I roughly remember a post from Humberto where he mentioned that GPS and other sensors are closely related from a kernel code perspective, so this could be the area of investigation. Unfortunately I don't find the time to dig into the code + it is years ago I programmed for the Linux kernel...
[Galaxy Tab  Android Development] ulev:
Same experience here.

My "retired IT manager" gut feel is that this is a problem beyond the ROM that simply has to be accepted.

In the old Overcome days I couldn't get 3G back anymore after switching to 2G. Lasted for more than 6 months whatever I tried. Endless reinstalls, tried all modems. Finally I gave in. Guess what: suddenly with CM9 it came back. No problem ever since.
[Galaxy Tab  Android Development] mike2nl:
I did not say there is an issue, i have seen things after re-engineering.

So i see and it works so far....

When i use GPS first in a different app, as sample ISS position,

close that app, stop GPS and start AndroSensor again, the sensors

that i have posted are not working.

And that on two tabs p-1000. Also i can provide all the user names

from which i had the PM's with the same issue. So there must be

anything. Not more and not less...

Until a year ago i have made my own kernels and have provided my

own roms for myself. All that was working very fine and smooth.

So i know some things about roms and kernels. I know not all

things about the CM11 rom, but enough that there are some small issues.

And i am busy to get the needed knowhow over the OMNI base code

as Sample.

At all it is a hobby for me, but when others mean that all is OK,

i wake up very fast to see is that right.

I have seen too many horses to puke in front of a pharmacy. ;)