yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] Discostrings:
Thanks for the detailed reply, mateorod! I greatly appreciate the work you do for this important project. I agree that it doesn't make sense for CM to include this sort of controversial option out-of-the-box, especially at this point in time.

Let me steer my point back on track after I inadvertently took it a bit off course...

I think that, if possible, OpenPDroid architectural decisions should take into consideration that in the future, we may want the presence of OpenPDroid not to be obvious to other apps. If OpenPDroid announces itself as being installed on the system, devices with it will probably be blocked from the app stores shortly enough. I only provided the CM anecdote as evidence for this (as the team received some indication that they may be blocked from the app store for including a similar but less capable feature).

If it's as easy to block devices using OpenPDroid as a quick check for its presence when the app store is loaded, I imagine some hyperbolic article about PDroid's capabilities will be written soon enough, the story will make the rounds, and a check will be put in place. If this happens, many fewer people will be willing to make the sacrifice necessary to enjoy the privacy protection of OpenPDroid.

I suppose the decision in itself to make OpenPDroid hard to detect, if this defies system conventions, could be pretty controversial.

Let me explain my current thinking a bit. I think it's perfectly legitimate that app stores can block access if obviously bad data is being submitted when running the app store. There may be potential malicious uses of this software, and apps and the app store need to be able to prevent against that once data leaves the device. But I think they should have to do that by analyzing the data that is sent to the app store or the app, not by just looking for a flag of whether or not OpenPDroid is installed. If OpenPDroid itself is not detectable, it would be possible to detect and block a connection on the server side if one is providing invalid numbers, but it would not be possible to detect if one is submitting no phone number when the device actually has one.

I don't feel strongly at this point that other applications should not be able to detect OpenPDroid. I will use it either way. But I think the ability to do this is important to the general appeal of OpenPDroid to the average person who is looking for privacy protection but who also wants access to a wide variety of apps. Decisions about this definitely don't need to be made today, but, if possible, let's not make the option more difficult to implement in the future. This is likely one of the issues OpenPDroid will face as it grows in success, so unless decisions can be made today, it's good to keep options open!
[Android Software/Hacking General [Developers Only]] Lanchon:
oh... well google better not upset hackers or they r gonna get it. if they push in this direction, i suppose we will end up having even better pdroids that sandbox google apps out in disneyland, even if they appear to have root. entering into this cat and mouse chase will only make our tools better in the end. or we might just choose to sever google completely off our phones which would be a dissaster for them. already we can forgo playstore and go bl*ckm*rt. i think google will be wiser and wont mess with hackers. everybodys seen how sony got it for locking down the PS3. any move they do in this regard would bring publicity to the dangerously explosive subject of privacy or lack of thereof on the android platform and how google declared war on the people who worked to keep it. and with publicity they'll have more dissidents. i think that if pdroid ever threatens to enter mainstream use, at that point google will have to acknoledge the concerns of its users and respond and cater to them with privacy improvements.

they way to guard from pdroid is to improve the privacy of the platform. make pdroid less of a necessity, while still leaking some info. going against mainstream user demands is not what i expect of them. with pdroid i'd expect them to bite the bullet and keep the waters calm and their mouths shut. the less said about pdroid the better,

technical solutions exist for this: remote atestation. i would never buy a phone that does that, or be part of an echosystem that requires it. as long as we have no TPMs and the baseband processor doesnt snoop on us, we are ok.
[Android Software/Hacking General [Developers Only]] xtam:
Can i install it on D-WIZ 3.02 by dtrail ?

http://xdaforums.com/showthread.php?t=1964792
[Android Software/Hacking General [Developers Only]] californicated:
Search is unavailable atm, so here a question: When I used old versions of pdroid months ago there were several freezes and reboots because of denied permissions. Is it still an issue?
[Nexus 10 Original Android Development] franciscofranco:
Hey all. I hate bloated OP's so this is a simple one. I don't post changelogs in here, only when I released new versions so you'll have to search for it.

Just for general awareness this is compatible with CyanogenMod based roms.

Download:

4.4

http://192.241.177.15/Nexus10/4.4/

How to flash:

fastboot flash boot image_name

or

flash the zip in your custom recovery

Source:

https://github.com/franciscofranco/manta/tree/nightlies-4.4

Kernel changelog:

http://192.241.177.15/Nexus10/4.4/appfiles/changelog.xml

franco.Kernel updater Free apk: http://xdaforums.com/showthread.php?t=1867127

F.A.Q.

1. My tablet exploded, halp!

A: I don't answer to problems without a log. The log file is in /proc/last_kmsg. Retrieve it from your device and attach it to your post.

2. This kernel works on Y or X rom?

A: This is one of the worse questions you can ask on my threads. This is a Nexus, it works on every rom you can possibly imagine.

3. OMG BETTARY SUCKZ, IT DEAD IN 45 MINUTAS, HALP!

A: As you can imagine I don't build kernels to decrease battery life. All the battery life problems come from your apps, either Facebook, or Maps, or some Location Service being enabled etc etc. Check your damn wakelocks and fix them, the kernel is not responsible for them.

4. How do I flash this?

A: Reading the OP, theres a reason why I added instructions on it.
[Nexus 10 Original Android Development] TheGrayHatter:
What exactly does the thermal throttling patch do?
[Nexus 10 Original Android Development] crossen0:
First! Excited to see your kernel making its way here. Love your kernel on the Galaxy Nexus. Thanks again!
[Nexus 10 Original Android Development] franciscofranco:
Basically just ensures that after that constant is true the thermal_throttle function call is called.
[Nexus 10 Original Android Development] espionage724:
Hmm, if your phone explodes after trying a new kernel on a tablet, you might have bigger problems on your hands :p

Joking aside, awesome :D This was my kernel of choice on the Nexus 7.
[Nexus 10 Original Android Development] the1onewolf:
AW YEAH!
[Nexus 10 Original Android Development] springy:
Yea!!! Now I need to buy a Nexus 10. Thanks Franco for supporting the Nexus 10 ;)
[Nexus 10 Original Android Development] EniGmA1987:
What kind of features do you plan to try and add to this kernel?
[Nexus 10 Original Android Development] 404 ERROR:
omg
[Nexus 10 Original Android Development] franciscofranco:
We'll see, still too fresh and still need to get to know the Exynos5 arch.

Things that are NOT coming no matter how hard I get asked: overclock & undervolting.
[Nexus 10 Original Android Development] 404 ERROR:
Any reason why (just being curious)?
[Nexus 10 Original Android Development] Noobla_Khan:
Yes! Franco on all the Nexus!

Sent from my Nexus 10
[Nexus 10 Original Android Development] espionage724:
Looks like the Kernel updater app isn't compatible for now
[Nexus 10 Original Android Development] Blindi1985:
Waaaaargh....

Now is franco on all my Nexus :)

Nice Work - keep it up....Thanks Man

I see myself obliged to support you financially with a donation :D

rgds
[Nexus 10 Original Android Development] franciscofranco:
Because its useless in my opinion and bring all sorts of problems for me.

Not yet, I'm not a machine! :)
[Nexus 10 Original Android Development] 404 ERROR:
I see. Sounds good. Overclocking is pretty useless on the Nexus 10.

If you haven't already read around, thermal throttling is a big issue on the Nexus 10 which makes it seem a lot weaker than it is. So hopefully your kernel can cater around that issue.

Thanks!
[Nexus 10 Original Android Development] franciscofranco:
How? Throttles too much?
[Nexus 10 Original Android Development] wera750:
Won't boot on aokp. I know the op said cm, but I tried anyways. So for the others that will ask, aokp is a no go for now.
[Nexus 10 Original Android Development] freshlysqueezed:
Throttles too easily. Run stability test app on the stock kernel and you will see the clock drop from 1700 to 1500 after a minute or two.
[Nexus 10 Original Android Development] 404 ERROR:
Yeah. When playing games at stock speeds, it'll start to throttle and lag.

People have been fixing this by undervolting, underclocking to about 1.2 ghz, and raising the thermal throttle temperature.
[Nexus 10 Original Android Development] Patrik G:
ok then why do you complaining over framedrops in movies?

just use the "other" governor

i dont have this kernel yet(waiting for color control ;)) so i dont know what governors you can choose

but the only governor that stays at the same freq is "Performance"

use it instead of locking the min/max freq

as i said its the up/down CPU speed changes that causes framedrops.

other solution is to use another governor and check the CPU speed with CPU spy

if it stays at the same freq while you watching a movie its fine...problemo gone

Edit: to franco

if you will solve the color control mystery i have a hardware colormeter and calibration program ready :)

i have been calibrating displays for several years,so if you just bring me the right/enough settings i will make this tablet Rec.709 reference or close to it.

i use a X-Rite Display 3 meter and Chroma Pure program with patterns from AVSHD709

if i calibrate my N10 everyone can use those settings to get closer to reference.

that is IF the devices dont differ to much.

and i think they dont.

some yellow tones in the whites with a Gamma around 1.6 and washed out blue/red colors seems to be what everyone has right ?
[Nexus 10 Original Android Development] franciscofranco:
Re: [KERNEL][GPL] franco.Kernel - r3

I plan to work on the color control this weekend. Like I said before I dont promise anything, I have some driver code to read and learn first.

By the way someone asked for boostpulse support for Ondemand few pages ago - I just made it working on my local build. Since it also required editing the powerHAL source code I need to update my ramdisk and now I need to sleep so it comes tomorrow. Surprisingly enough Ondemand with boostpulse is marginally snappier than interactive, Im surprised.
[Nexus 10 Original Android Development] Endless7:
Yep,ondemand based govs work fine without constant freq changing that cause frame drop. All I just do here is to report the performance issue here. Not want to make meaningless argument with you,buddy.

Also want to mention you as you haven't used this kernel yet. This kernel only has interactive gov and I can't switch to other gov to solve the problem.

---------- Post added at 05:45 PM ---------- Previous post was at 05:37 PM ----------

Great.:good: Really missing ondemand gov.
[Nexus 10 Original Android Development] Patrik G:
you are going to bring in $ for it thats for sure :)

here is my wishlist :)

Brightness (Blacklevel) settings (the one we have now is only controlling backlight level)

Contrast (Whitelevel) settings

Gamma control for RED/GREEN/BLUE locked and unlocked sliders

Saturation and HUE settings for all primary colors red/green/blue/yellow/cyan/magenta.

Overkill if you have time over :

Brightness settings for the primary colors

independent Gamma adjustment from black (10 IRE) to white (100 IRE) in 3 or more steps.

(the gamma curve/line on the N10 isnt flat (1.4 high level and 1.8 low level) so thats why this is needed to smooth it out at 2.2 all the way from black to white )

also this will give a perfect grayscale
[Nexus 10 Original Android Development] kampfbestie:
Y have To wait only 11 months than its Christmas and y can wish what y want :laugh:
[Nexus 10 Original Android Development] Patrik G:
ok i will call santa and tell him to make color controll to the next christmas lol
[Nexus 10 Original Android Development] dust.:
Never got an answer for my question before... OP states that the kernel should function on any ROM but I'm on Schnip's and the kernel updater app (paid version) shows my device not compatible with the kernel... :confused:
[Nexus 10 Original Android Development] brGabriel:
So you were able to install the app, but once installed it gives you an error? Either way, it may be a bug in the ROM not properly identifying the device.
[Nexus 10 Original Android Development] dust.:
There's no error. When I open the app it literally says your device is NOT supported. But yeah I'm thinking it may be a bug in the ROM as well...
[Nexus 10 Original Android Development] franciscofranco:
Im sure the stupid rom changed your Device ID name or something, thats what I check in the app. Make sure it says Nexus 10 in the About Phone menu. If not you can change it on your build.prop and all is fine.
[Nexus 10 Original Android Development] dust.:
Yeah you're right lol the name of the device got replaced with something else.
[Nexus 10 Original Android Development] dalingrin:
You shouldn't be surprised. I'm not *completely* ignorant. :rolleyes:
[Nexus 10 Original Android Development] franciscofranco:
Im surprised because Interactive is pretty good and it works great on the Nexus 4 and the Galaxy Nexus - but Im actually remembering now that Interactive governor never did really great on Exynos devices (tried it on the SGS2, SGS3, Note and now this one). Get ready, I will release it in 10m.
[Nexus 10 Original Android Development] EniGmA1987:
My theory on that was because Exynos devices seem to have WAY more frequency steps than other chipsets. For instance the Galaxy Nexus has (somewhere around) 350, 700, 920, 1200. Only 4 steps to choose from and larger jumps between them so it can pick on and stay with it for a bit. This chipset has 16 different steps and only 100MHz between them. A governor like Interactive will be trying to jump between the steps much to often as load is changing, ever in pursuit of the "perfect" speed. This jumping around so much is what causes uneven rendering times of frames in games and either the same thing or dropping of frames in video playback. Im sure that if the chipset were to have 2/3 of its available frequency steps cut out then Interactive would work fine.
[Nexus 10 Original Android Development] dalingrin:
I think the many steps exacerbates the problem rather than being the sole source.
[Nexus 10 Original Android Development] duarian:
Re: [KERNEL][GPL] franco.Kernel - r3

Not sure if setcpu and this mix well. I tried a screen off profile of 400mhz max and got a couple SOD's. Don't really need that profile anyway so I'll just get rid of it :)
[Nexus 10 Original Android Development] dalingrin:
Don't forget Android 4.2 has a built in screen off profile.
[Nexus 10 Original Android Development] franciscofranco:
r4 is up

* Ondemand governor is default in conjunction with a new boostpulse function which ramps frequency to 700MHz when the screen is touched. It works in conjunction with the custom power.manta.so that I compiled from source. Its all set up automatically, just flash and forget.
[Nexus 10 Original Android Development] franciscofranco:
The powerHAL already sets 800MHz as max when the screen is off, no need for that.
[Nexus 10 Original Android Development] duarian:
Re: [KERNEL][GPL] franco.Kernel - r4

One less thing taking up memory

Thanks!
[Nexus 10 Original Android Development] Fasty12:
So hard

Man fastboot is so complicated please franco can you make a zip version? Im sitting here tearing out my hair trying to figure out how to make this fastboot thing work.
[Nexus 10 Original Android Development] espionage724:
I was about to say if you managed to get a custom recovery on your device, you would of already experienced how to use fastboot. I take it you used a toolkit though?

For starters, you need either Android SDK (free download from Google) or the platform-tools folder from that SDK. From there, you want to reboot the N10 to the bootloader, plug it into the computer, install the driver (if not done already), then open Command Prompt. cd into wherever the platform-tools folder from the SDK is, and then run the fastboot command in OP.

That's probably the simplest way anyway. I just add the platform-tools folder to PATH so I can run adb and fastboot from anywhere.
[Nexus 10 Original Android Development] CazeW:
Did you remember to set that it doesn't try to ramp up the frequency when it's already higher than 700MHz so that it doesn't throttle down?

I remember ktoonsec having this problem when he first implemented boostpulse into ktoonservative and pegasusq governors in KTManta.

I've also done some research on trying to implement mDNIe for the N10 so that if you need help with the color control, I'll be happy to help if I can.
[Nexus 10 Original Android Development] franciscofranco:
I will eventually, just too lazy to do it because takes some minutes to set it up. Just google how to setup fastboot, theres plenty guides.
[Nexus 10 Original Android Development] franciscofranco:
Nope I didn't do that. Why would that be useful?

Thanks for the offer :)
[Nexus 10 Original Android Development] Fasty12:
Yessir i used a toolkit but my nexus 10 drivers is bugged on this computer and im trying to figure out how to uninstall it. It wont let me copy any files from my pc to it. On my laptop i can transfer fine.
[Nexus 10 Original Android Development] CazeW:
Or you can just use the Nexus 10 Toolkit and select option 11.
[Nexus 10 Original Android Development] espionage724:
Uninstall any ADB drivers you have installed, and reinstall (I'd recommend using version 7 of the USB drivers from Android SDK; Toolkit driver "may" also work too, whatever version they are)
[Nexus 10 Original Android Development] CazeW:
Well, if you're already running the CPU at lets say 1000MHz, there's really no point for it to try boostpulsing the frequency to 700MHz. And I would imagine this could cause some slight irritations when gaming if it keeps lowering the frequency. :p

EDIT: Zip removed unless franco gives me the permission to post it again.
[Nexus 10 Original Android Development] Noobla_Khan:
Fanco likes to keep track of kernel downloads so you might want to take down your link...unless you asked him?
[Nexus 10 Original Android Development] CazeW:
Well he still can, all he needs to do is to look at the amount of downloads on that zip. I just made it so that people would stop pestering him about a zip but I'll remove it if that is what he wants.

EDIT: Ah, just noticed the previous post about the same thing. Remembered that it was in another thread...
[Nexus 10 Original Android Development] EniGmA1987:
What CazeW said. It was found that boostpulse would cause lag in heavy games unless it also had a few lines of code to ignore boostpulse if the frequency was already at or higher than the boostpulse frequency. The problem was that if a game required 1.5GHz to run smooth and you touched the screen while playing then the governor would activate it boost to 700MHz but since you were already at 1.5GHz it would actually jump way down to 700 which would cause lag. So all the needs to be added is for boostpulse to do a check for what the current frequency is and dont do anything if the speed is already 700MHz or higher.
[Nexus 10 Original Android Development] franciscofranco:
Can you reproduce that problem with r4 as well?
[Nexus 10 Original Android Development] EniGmA1987:
Yes I can. In NFW: Most Wanted I can be playing and have my CPU monitoring app open, I use PerfMon by Chainfire. It shows CPU @ 1600MHz for both cores. WHen I touch the screen CPU speed drops to 700MHz. Odly enough, it seems like it doesnt always drop the speed, only most of the time. Or maybe the PerfMon app isnt catching the drop sometimes because it happens so fast and then jumps up again. IDK. Ill take a video though so you can see.

EDIT:

Here is the video showing my CPU behavior during the game:

http://dl.dropbox.com/u/73615195/BoostpulseTest.mp4
[Nexus 10 Original Android Development] houseboatwayne:
Re: [KERNEL][GPL] franco.Kernel - r4

Das paid app all pooping frawden at fetching r4 :) (fake Deutsche)
[Nexus 10 Original Android Development] franciscofranco:
Thank you very much, will fix it tonight :)
[Nexus 10 Original Android Development] SpecRek9:
Re: [KERNEL][GPL] franco.Kernel - r4

Hey guys is there a way to flash img files without using the computer? I'm curious because I'm mostly afk when a new img is released and I realize there's nothing I can do to flash it :confused:
[Nexus 10 Original Android Development] dreitzell78:
Yes, you can buy Franco's app, and it will download and flash the file for you. It isn't very much, and it is well done. Makes life easy. Cheers!
[Nexus 10 Original Android Development] dajogejr:
Re: [KERNEL][GPL] franco.Kernel - r4

Bought the app... makes things much easier and better yet, supports those that help us. Thx Franco
[Nexus 10 Original Android Development] toricred:
I'll by the app, but what is the name or is there a link?
[Nexus 10 Original Android Development] 1BadHEMI:
Search for "Franco" on the Play Store
[Nexus 10 Original Android Development] Bataga:
Re: [KERNEL][GPL] franco.Kernel - r4

You don't search for Franco, he allows himself to be found :)
[Nexus 10 Original Android Development] PhilDX:
Here you go: https://play.google.com/store/apps/...t=W251bGwsMSwxLDMsImNvbS5mcmFuY28ua2VybmVsIl0.
[Nexus 10 Original Android Development] TheHobbyist:
Re: [KERNEL][GPL] franco.Kernel - r4

Lol! Thank you for that. Hahaha
[Nexus 10 Original Android Development] osm0sis:
franco.Kernel Updater Emergency Settings Reset Zip

Hey guys, I posted this in the GN forum and linked from Franco's N4 and N7 threads awhile back, so now it's time for the new N10 thread so everyone's covered. :)

Here's something that's been requested for awhile by f.K users.

I wrote it up recently with Franco's stamp of approval, so I'm posting it here now so hopefully he can add it to the OP at some point when he gets the chance. Until then, please direct people back to this post.

This can/should be everyone's go-to when experiencing problems after updating to a new kernel build, since likely some leftover settings (voltages, etc.) are at fault. This should work on any device franco.Kernel and f.Ku support, but is only really for f.Ku, so if you use some other conflicting app to set things (SetCPU or TricksterMOD) then this won't help you much, and really, you should be using f.Ku anyway so you'll just have to figure that out for yourself. ;)

Flashing this via custom recovery of your choice will delete the f.Ku settings file, disable init.d scripts by moving them to a subfolder (/system/etc/init.d/off/) and wipe cache and dalvik-cache for good measure.

Hopefully it helps!

Original Post & Download: cwm-franco.Kernel-Emergency.Settings.Reset.zip
[Nexus 10 Original Android Development] jdog2115:
Re: [KERNEL][GPL] franco.Kernel - r4

https://play.google.com/store/apps/details?id=com.franco.kernel&hl=en
[Nexus 10 Original Android Development] SpecRek9:
Re: [KERNEL][GPL] franco.Kernel - r4

Yes I have bought it for my n4, I just haven't bought it yet for my n10, is there a way to flash it without computer nor the app?

---------- Post added at 03:12 PM ---------- Previous post was at 02:31 PM ----------

Franco what does that updater binary do? I see within the zip file there's a updater script with a command 'extract' to a location where a symlink is, if I want to do that manually, how should I do it? Thanks
[Nexus 10 Original Android Development] Fidelator:
Hey Franco have you been able to do anything about the display?