yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] paxChristos:
Dang it! I'll just keep futzing with what i've got so once it's ready all i have to do is sync ;)

Pax
[Android Software/Hacking General [Developers Only]] medicjunKie:
Hello, my phones dpi is 240 (HDPI phone) do I just need to set the build.prop and prad.prop or do I need to mess with the framework as well?
[Android Software/Hacking General [Developers Only]] sgtkwol:
Leave pad.prop alone, if porting from GS2. build.prop DPI should be set to 128, the minimum to trigger tablet mode. framework-res.apk will more than likely need to be edited to get everything up and running.
[Android Software/Hacking General [Developers Only]] medicjunKie:
The HTC mytouch has same screen resolution and all as my phone.

Would framework-res.apk still needs to be edited?
[Android Software/Hacking General [Developers Only]] sgtkwol:
It will probably work without the edits, but ymmv. Epic 4g, for example, had no high charge indicator, no mounting sdcard as usb, no wimax, etc.
[Android Software/Hacking General [Developers Only]] medicjunKie:
I'll give it a shot and see what happens.
[Android Software/Hacking General [Developers Only]] mateorod:
You need to change the PRODUCT_NAME to match what is in your .mk file. So change the PRODUCT_MAKE line in the build/core/product_config.mk to what the error says, which is pa_galaxymtd I guess.

How about this, that inconsistency is what is causing the error. Making that entry match is what is usually called for, but since I am pretty sure your device isn't pa_galaxymtd, maybe you should change the lunch.

But hopefully this gets you closer to what you're trying to do.
[Android Software/Hacking General [Developers Only]] quentin330:
I ported 1.6 for galaxy s2 i9100g exactly like I did for 1.4 and 1.5 but this time I'm always getting bootloops... I used 20120710 cm9 but I don't know what doesn't work
[Android Software/Hacking General [Developers Only]] joydeep1985:
Hmm the same problem I also faced the same problems .

http://pastebin.com/xf1ekTdz . Here is my logcat for pastebin. I wd appreciate if someone can help me out . I am using motorola defy . Oh yes i forgot to mentioned ported from Galaxy S2 I9100 build from D4rKn3sSyS
[Android Software/Hacking General [Developers Only]] mateorod:
I am having the same problem with Nook. It worked fine with 1.5 but 1.6 has given me problems. I will update this post with more info as I figure stuff out, but I figure another report couldn't hurt, even though I don't have any logs yet.

Edit: Looks like a problem with a null point in the ServerThread going by the above logs. A problem with the services.jar, it looks like.

Oh and I ported from D4rKn3sSyS GalaxyS2.
[Android Software/Hacking General [Developers Only]] joydeep1985:
so any solution for that ? I couldnt figure which service is actually causing the trouble :(
[Android Software/Hacking General [Developers Only]] mateorod:
I don't know of a solution yet. I have a program I use that ports some software to CM9 through smali patches, and our patches have been breaking every other day. The CM repo is just turning over a bunch. And problems with the ServerThread is usually our first culprit.

So it could be just a result of the commits and when the nightlies were made. But that's just a guess. So far, I have tried nightlies from 9th and 10th as well as a new build I just made myself. I am going to try the 8th next, as well as possibly play around with patching it myself.
[Android Software/Hacking General [Developers Only]] quentin330:
I hope someone will find the solution soon
[Android Software/Hacking General [Developers Only]] Xylograph:
Try using the 'libandroid_runtime.so' from D4rKn3sSyS S2 build and it will bootup (at least it did for me..)

I suppose it has something to do with the below quote...

Besides the changed 'libandroid_runtime.so' I have no idea what other libs may have changed, because even after booting up I have quite some strange things going on (crashing browser/gmail stuff) though I don't know if this is PA or nightly related..

I hope D4 will jump in here to explain the things (libs) that are changed/needed to give other devices some stable PA fun..

Good luck all !
[Android Software/Hacking General [Developers Only]] D4rKn3sSyS:
Thanks for answering to all other porters, you're right, that lib must be copied in order to avoid "java.lang.UnsatisfiedLinkError: readFile", wich is on all of the logcats you made.

I'm also facing weid issues on camera with latest CM sources, seems they merged ISO settings, and it's being a pain in the ass. Besides that no crashes here, but some of my users experience crashes so I guess this version is a fullwipe one
[Android Software/Hacking General [Developers Only]] brajesh.sharma87:
Unforunately copying the libandroid_runtime.so from ur rom doesn't even let me get past the boot splash screen. My previous port of 1.5 on defy was running perfectly ok. :confused:
[Android Software/Hacking General [Developers Only]] scott.hart.bti:
Quick question... I saw on your 1.6 release it is titled "... Goodbye ICS!" Does that mean that your just going to be focusing on JB?
[Android Software/Hacking General [Developers Only]] mateorod:
After full wipe and moving the lib still isn't working for the Nook either...thanks for the response, though.
[Android Software/Hacking General [Developers Only]] D4rKn3sSyS:
For people having bootloops, be sure of a few things

You copied libandroid_runtime.so to /system/lib (from PA)

You're basing on a recent CyanogenMod nightly (No other bases)

Be sure that this line is present EXACTLY equal on your build.prop "ro.cm.version=PARANOIDANDROID" and this one aswell "ro.modversion=PARANOIDANDROID", something just slightly different will cause the bootloop
[Android Software/Hacking General [Developers Only]] brajesh.sharma87:
Copy libandroid_runtime.so - already DONE

Based on recent nightly - already DONE

PARANOIDANDROID lines in build.prop exactly how u mentioned - already DONE.

STILL NO SUCCESS. :-(

Sent from my defy
[Android Software/Hacking General [Developers Only]] D4rKn3sSyS:
Atleast post a log?
[Android Software/Hacking General [Developers Only]] brajesh.sharma87:
Oops, i m not at home at the moment.

Here is a logcat sent by my friend who tried without copying libandroid_runtime.so

http://pastebin.com/xf1ekTdz

By copying libandroid_runtime.so the phone doesn't even get past to bootlogo. Will send u a log for that too after I get to home.

To other porter: guyz we can not loose our hope. Discussion is the only way to get rid of this problem.

Sent from my defy
[Android Software/Hacking General [Developers Only]] kevdliu:
From past experience changing runtime.so will cause phone to be stuck on starting Net.d
[Android Software/Hacking General [Developers Only]] brajesh.sharma87:
Exactly

Sent from my defy
[Android Software/Hacking General [Developers Only]] DAGr8:
there is no way around it if runtime is needed PA wont work on all device ..

any device not able to run on the native runtime (before it was patched/modded ) wont be able to run the patched one . thats pure logic right there //

in my book its nearly perfect speed improvement is not gonna make it any better , may I ask what is there to speed up ? the delay the app takes in order to apply the changes ?

PA is before everythign else a mod that allows something no other roms will , the rest is all spices and flavors and some will prefer them others wont , I guess what im asking here is what missing exactly ?

Believe me I completely understand not wanting to have one 's work re-hashed by everyone else but all these efforts to make it work only on cm9 is a complete waste of time . keep in mind the big dog cannot prevent there proprietary OS from being ported and there launchers form being used on different flavors of android even on other devices ...
[Android Software/Hacking General [Developers Only]] tonyp:
Uh the last line is bad for me and the LG Optimus 2x world. If I change the ro.cm.version to something else then the default cm version I won't get any signal. Bummer.

If that's really the case I will try to change the build.prop at runtime, but I doubt that will work.
[Android Software/Hacking General [Developers Only]] Note2Frat:
Thanks, it's running beautifully :D 1.6 a
[Android Software/Hacking General [Developers Only]] D4rKn3sSyS:
Any device not able to run native runtime before they were "patched" as you call it (Is more like improved) wouldn't run apps, wouldn't be able to do any math calcs, wouldn't be able to use PackageManager, so in short wouldn't boot at all, android runtime is a VERY important part of frameworks present on all ROM's and is used by SDK operations, so it's some logic there, is perhaps the most global native lib. Speed improvement is nuts, no more lag when opening recent apps, or when swiping through trebuchet, is not just because we want to avoid the usage of custom bases (I don't lie that was the original idea) but also increase performance and reliability. So no, is not a waste of time, if somebody gets the native binary dissasembled and make it run over other base, that's excelent (Though I'd rather prefer if it don't), but that somebody will thank us for the speed improvement (Mostly on XHDPI must I say).
[Android Software/Hacking General [Developers Only]] DAGr8:
thx for taking the time to respond about speed improvement :good:

I either got misunderstood or I didtn explian myslef well , runtime.so , is not universal regardless of what you may think one made for a chipset will work on them chipset devices not on others , before I started hacking smali I have win zipped quite a few roms trying to port source roms to proprietary devices in the past ... it might work on gnex n7000 and sgs2 for the reason I mentionned above ( maybe sgs3 shares the same chipset im not sure ) but if you try to put that lib on another chipset .. not gonna work . I d be happy if proven wrong , if 1.6 will get ported to a device with different chipset then ill come back and say I was wrong . but for now I believe the assumptions that CM9 runing is the only thing needed for that lib to run on 'a' phone is wrong
[Android Software/Hacking General [Developers Only]] brajesh.sharma87:
@Dark3n3sys: I wud love ur initiative to make the new version which can be ported to all the devices. Like the version 1.5 was. In last few days PA got really popular only bcoz it got ported to many devices successfully. There's no point restricting the ROM to just some specific devices. Hope u understand. Most of the people are waiting desperately for the new version.

Thanks
[Android Software/Hacking General [Developers Only]] JamieD81:
150% agree,

quit this apple like behavior with locking ur ROM to select devices, u have more users thanks to us who have taken time to bring ur work to other phones, and ur doing ur best to screw those users out of updates. Hope ur happy about that :-P

My 2cents.
[Android Software/Hacking General [Developers Only]] D4rKn3sSyS:
Well if it causes issues then I guess you just should stay on v1.5, I'm not reverting the entire framework mods, and also ICS is abandoned now by us, we're working soon on JB, no difference between 1.5 and 1.6 except for the speed improvement, and a few more things and fixes, v1.5 must be stable enough while we find our way to JB. You may be right as there are some defines on boardconfig that affect runtime aswell (though is still weird why it got ported to Nexus S, wich is very different hardware, but atleast the same manufacturer), I may wrap this around on a specific independent native lib aswell. We're not locking our rom, just improving it, and we really want to speedup even if that involves issues like that. Anyway sources will be public, so this all will be probably over and native libraries may be built by user himself avoiding all this kind of bugs (So ports will be via building from sources)
[Android Software/Hacking General [Developers Only]] brajesh.sharma87:
Sad to read the quotes (Bold Parts). It was not expected to pull support so early from the developers. Not everybody can build from source. :-/

Ok. your ROM, your wish. You can do whatever you want. It was a very gud experience till 1.5 :)
[Android Software/Hacking General [Developers Only]] D4rKn3sSyS:
First, and biggest. Is not MY rom. Next you will be still able to base it on CM, so no problem at all. I just finished moving it from libandroid_runtime to a new library, so I may release a "porter" version of frameworks, and publish the library aswell. Needs further test anyway.
[Android Software/Hacking General [Developers Only]] tonyp:
I think what DAGr8 said is true. mateorod isn't able to port 1.6 on the Nook Color which runs a TI OMAP3621 iirc - and I'm unable to port it to the LG P99x line which runs a Nvidia Tegra 250 AP20H.

Sorry, I cannot agree with this statement. It may be true that not everybody can build from source but this isn't really a reason. (Hint: anyone can learn to build from source :good:)

It would mean more work for them to maintain two totally different builds (one on native, one on java code) - and thus they'd have less time to work on improving their (already great) build. Porting might get harder then, but I think a (drastic) speed increase will always be worth it.

If I understood it correctly version 1.6 doesn't really include new features and no important bug fixes anyways - then I'm totally fine with staying on 1.5 for now :)

That sounds even better! Thanks a lot!
[Android Software/Hacking General [Developers Only]] brajesh.sharma87:
Cool. Thanks. :)

Agreed to your point as well. :)
[Android Software/Hacking General [Developers Only]] mateorod:
I was just about to chime in and say this. When I swap in the runtime lib, the bootloader won't even start (which it did previously, only to bootloop) and tonyp has the chipset correct. So the runtime fix won't work for us.

I'd love a "porter's" version as well, but I respect anything you guys decide. I have some fixes I need to still get to for 1.5 lol. We'll be able to build from source soon enough, but I do agree that the help you guys have extended to us porters can only whet the appetite of the user base. I can say the response from my device forum has been overwhelmingly positive. So people like your work!

Thanks for the explanations on our difficulties!
[Android Software/Hacking General [Developers Only]] joydeep1985:
One quick question . If you are really shifting on JB . Would that be a porter version or it would be something like 1.6a ? :( :( please make it a porter version based on CM10 if you are likely to work on PA . Cause as far as my knowledge is concerned CM10 is just round the corner . atleast alpha build . So that might make sense that we can port something like PA for JB to CM10 .

And ofcourse waiting for a porter version for 1.6 . Would test it ASAP when its available :victory:
[Android Software/Hacking General [Developers Only]] D4rKn3sSyS:
Guys, moving the native bin outside libandroid_runtime didn't really work, Improvement is gone, lag comes back, I guess the speed is because runtime library is loaded on very early boot. So you should use framework.jar from v1.5 (You can use all other files from v1.6). Sorry about that :/

EDIT: Consideering that I may publish a "fallback version" of framework.jar for each version, with reverted native, for this time here you go it. I'll consideer later to add a native check (If native code exists, load through native, otherwise, go back to java slow hell. (For doing this I must get a confirmation that nobody is going to use the ROM with custom bases, untill sources are out).

If you guys make native interface working somehow, you will thank me SO much, but otherwise use the old slow method here
[Android Software/Hacking General [Developers Only]] quentin330:
We lost system ui in 1.6 so goodbye beautiful small lockscreen and nice numbers for pin code =(
[Android Software/Hacking General [Developers Only]] DAGr8:
all your work and efforts are really appreciated man , thx a lot .
[Android Software/Hacking General [Developers Only]] brajesh.sharma87:
+1

Thanks D4rKn3sSyS for all the support that you have provided.

And I guess, we wud like to wait for PA based on CM10 now. ;)
[Android Software/Hacking General [Developers Only]] molesarecoming:
jellybean is quite a nut to crack. much has changed, they have completely revvamped sysUI, it FINALLY works like every other app. that means you can switch it into tablet/phablet/phone mode by .mode=1/2/3 and it will switch without reboot. i think its important that we made PA independent of build.prop in 1.6 as JB seems to not like it so much if someone foofls around with it.

the weirdest thing right now is that phablet mode, it puzzles me. they dropped tablet mode to 720 short side dpi. so according to that formula on page one in the old PA nexus would need 160 dpi now to get into tab mode. good that its just a technicality now and we wont have to boot into any dpi anymore. still it needs new pad.prop definitions.

mine look like this now
[Android Software/Hacking General [Developers Only]] molesarecoming:
pheww, its running. :laugh:

JB is a HUGE change from ICS. so much is different, some things for the better some for the worse. but overall i think JB will be perfect for hybrid mode. all the info on page 1 is kinda obsolete now, i had to make quite some changes. when aosps got a clean rom out i will update this stuff, for now i leave it ICS related as im not done yet and it'll mean more things will be adapted to fit the new OS.
[Android Software/Hacking General [Developers Only]] D4rKn3sSyS:
I'm closing ICS repos now, no more updates, will start JB branches soon :)
[Android Software/Hacking General [Developers Only]] Note2Frat:
Looks awesome, cant wait.
[Android Software/Hacking General [Developers Only]] joydeep1985:
Cool looking forward for jellybean repos . I guess we can surely port it on as soon as we have a working JB on our motorola defy. I guess its just matter of weeks now we wd hav working Jellybean on our device :) ..... And this rom is just pure awsomeness . I am using it for my daily use . Just cant get better anyway than this :) :) . Thanks for your all hardware . Just make sure its likely to be portable like it was done for 1.5 . That easier when we do it for our defy keeping CM10 as base .

Thanks again . And thanks for gifting us with such a beautiful rom :) :highfive::fingers-crossed:
[Android Software/Hacking General [Developers Only]] b.huss2:
trying to port d4rk's sgsII 1.6a on the evo3d. We are all up and running. Anyone ever find out why gmail/browser force closes? that's my only issues. that 1.5 version framework.jar posted a few pages back did nothing but made it not boot at all. I'd be fine with staying with 1.5 version if someone knows where I could get it.

thanks guys!

Update: Seems that my port of both 1.5 and 1.6 result in gmail/mail/browser force close. its weird because I can open them up and they function, but swipe up and poof, force close. any ideas???

log when gmail FC:

07-14 22:33:51.100: E/AndroidRuntime(9796): FATAL EXCEPTION: WebViewCoreThread

07-14 22:33:51.100: E/AndroidRuntime(9796): java.lang.UnsatisfiedLinkError: native_cpu_setoptions

07-14 22:33:51.100: E/AndroidRuntime(9796):	at org.codeaurora.Performance.native_cpu_setoptions(Native Method)

07-14 22:33:51.100: E/AndroidRuntime(9796):	at org.codeaurora.Performance.cpuSetOptions(Performance.java:57)

07-14 22:33:51.100: E/AndroidRuntime(9796):	at android.webkit.WebViewCore$WebCoreThread$1.handleMessage(WebViewCore.java:728)

07-14 22:33:51.100: E/AndroidRuntime(9796):	at android.os.Handler.dispatchMessage(Handler.java:99)

07-14 22:33:51.100: E/AndroidRuntime(9796):	at android.os.Looper.loop(Looper.java:137)

07-14 22:33:51.100: E/AndroidRuntime(9796):	at android.webkit.WebViewCore$WebCoreThread.run(WebViewCore.java:789)

07-14 22:33:51.100: E/AndroidRuntime(9796):	at java.lang.Thread.run(Thread.java:856)
[Android Software/Hacking General [Developers Only]] DAGr8:
Use paste bin and give us at least 30 lines before and after the fatal
[Android Software/Hacking General [Developers Only]] b.huss2:
thanks for the response. here's the log.

http://pastebin.com/2zJd0buc
[Android Software/Hacking General [Developers Only]] tonyp:
For me the xda app force closes when it's set to a DPI different than 240.

Logcat: http://screencast.com/t/nsQGtbKPU

Does anyone have an idea?
[Android Software/Hacking General [Developers Only]] DAGr8:
07-15 01:04:38.833: W/dalvikvm(4383): No implementation found for native Lorg/codeaurora/Performance;.native_cpu_setoptions (II)I

this is what triggers the FC . I dont have code aurora stuff in my build so I wouldnt know
[Android Software/Hacking General [Developers Only]] sgtkwol:
Just got my first build of CM10 compiled, really see what features are missed from AOSP to CM. Are you going to merge sources back with CM10 instead of going AOSP as the base? Also, since ICS source has been essentially closed for PA, does this mean that ICS PA source will remain closed?
[Android Software/Hacking General [Developers Only]] Looki75:
Let me ask a stupid question...

Is there a chance to port ParnoidAndroid per-app dpi functions into Gingerbread?

Did anybody try and/or did it?

I'm certainly not competent to do it... but I'm willing to help if someone wants to try it!
[Android Software/Hacking General [Developers Only]] tonyp:
No it is not, sorry. Android 4 introduced the tablet hybrid mode you'd need to completely write it from scratch for Android 2.3 - and no one will do that.
[Android Software/Hacking General [Developers Only]] swapnilraj:
I am having issues with PA 1.6 when I try to port it to my SL my phone does not show the option for mass storage

http://paste.ubuntu.com/1094957/

I think the problem can be seen towards the end.
[Android Software/Hacking General [Developers Only]] dswaggz:
Hey will there be a official build for the US GALAXY TAB2 :D

swaggedout GT-P3113
[Android Software/Hacking General [Developers Only]] tonyp:
@PA devs:

Would it be possible to build a 1.5 version of the ROM with the PDroid patch included?

CM9 Source patch is here: http://xdaforums.com/showthread.php?t=1554960
[Android Software/Hacking General [Developers Only]] benjamin.j.goodwin:
http://xdaforums.com/showthread.php?t=1775322 - One X At&T build I have done.

Main issue I am facing is backlights not working on both my builds :(
[Android Software/Hacking General [Developers Only]] Duarte777:
Hi ;)

I´ve ported PARANOIDANDROID Rom for LG optimus black, it´s working almost fully.

Here: http://xdaforums.com/showthread.php?p=28643600#post28643600

It´s a great ROM ;)
[Android Software/Hacking General [Developers Only]] sgtkwol:
Check your phones overlay settings in CM9 source.

overlay/frameworks/base/res/res

Decompile framework-res.apk and use your CM9 source as a guide.
[Android Software/Hacking General [Developers Only]] benjamin.j.goodwin:
Wish I had read this earlier. Just did that tonight and fixed it on one s. Need to sort it on one x at&t the same method now. At least I was following the correct lines. :)

Thanks.
[Android Software/Hacking General [Developers Only]] DnickDominic:
should of done this a while ago but heres my port thread http://xdaforums.com/showthread.php?p=28938700 for Galaxy S 4G
[Android Software/Hacking General [Developers Only]] sgtkwol:
From your 1.7a thread.

"New hybrid codebase, won't touch build.prop and changing build.prop wont ever be necessary"

Does this include ro.pa.version, or are you just referring to DPI changes?