yashsingh1/xdaforums huggingface dataset:
[HD2 Android NAND Development] dcos:
Hi guys,

I created (for my own use) Gapps installer for NativeSD install of this ROM. You can download it from following link.

gapps-jb-20121011_NPA_LEO.zip - 90.33 MB

Just flash from recovery after PA_LEO install, it will copy gapps to corresponding system.

---------- Post added at 03:08 PM ---------- Previous post was at 02:43 PM ----------

I checked properties.conf and permissions are fine as far as I can see.

Manually editing properties.conf seems to work, fine.
[HD2 Android NAND Development] shahul_555:
Thanks for the response. The black/blank screen was immediately after the HTC symbol but I got it working now. I chose not to odex and now its working.
[HD2 Android NAND Development] wwchang:
As just editing the ./etc/paranoid/properties.conf seems to work then the issue probably has easy resolve.

You know you might be able just to try a different ./app/ParanoidPreferences.apk because recently the PA team made that apk 'proprietary' to preserve their namesake, and that apk has more-or-less become a 'blob' that just gets copied over to /out/... during compile.

I suggest to try swapping in a ParanoidPreferences.apk from any pre-compiled PA 2.22 rom or greater. (Starting with PA 2.22 they made a big change on how they did the ./etc/paranoid/preferences and any ParanoidPreferences.apk before that will probably, definitely be incompatible in any case).
[HD2 Android NAND Development] dcos:
Actually I tried this using ParanoidPreferences.apk from PA-HD2 v2.54 - 2.8, but no luck. Settings keep crashing. I'll try to get my hands on .apk from 2.56.
[HD2 Android NAND Development] wwchang:
Actually building android for the HD2 is not easy and thus doing a tutorial is equally difficult.

As the HD2 is more-or-less a legacy device some source code has to be borrowed from Evervolv android sources, and also an updated, fully-tested & working device set doesn't really exist for HD2 except as you make it yourself.

With respect to sources for instance, the 'gpsshim' code, which creates the file 'gps.htcleo.so', a necessity for the gps to function, can only be gotten from Evervolv afaik - it doesn't exist at all in the main android sources.

Most of the build can be done in the space of your target rom but then some of the modules are more easily built in Evervolv's source space, by relying on the android's super-duper make system to build single modules.

Anyway these types of issues and many others make the compile much more difficult than being able to run like a pre-prep'ed 'turn-key compiling' that other android-native phones can offer, esp if you can follow other xda threads too that topic on compiling for your android phone and give helpful, step-by-step tutorials.

From all the process that I've been through to make the HD2 compile, I can kind of see it's probably beyond the scope of the HD2 threads to attempt such a tutorial.

But if you are really are trying to build android for HD2 please feel free to ask some questions if you need, and I'll try to give you some helpful advices from experience, or you can even PM if you wish.:)

In some spare time I've been doing some more test compiles of Android JellyBean 4.2.1.

This is one from a couple of days ago, of the Evervolv JB 4.2.1 sources, which made a very smooth and pleasant rom.

Lol, I'm really more & more liking these Evervolv guys, needless to mention.

The graphics system, interface works well - super-duper smooth which is characteristic of Evervolv builds...lights & sensors work too, but almost nothing else practical works now for this build - no phone, data, wifi, or sdcard.

So I just offer it as is, for those who want another different taste of JB 4.2.1 on HD2. You will experience some '-process.media' fc's, but just keep pressing through those until they finish.

Even for my own testing I put it in a NativeSD aroma-installer jacket and installed it only to NativeSD, though NAND or DataOnEXT installs will probably work too - it installs to /NativeSD/EV_LEO.

http://d-h.st/koo

.
[HD2 Android NAND Development] zagzag99:
This test rom is really interesting. I would very much like to see this become a ROM (and a thread) by itself.

I used to take CM7 builds of Bravo as is and mix match some files from Tytung's ROM to port latest nightlies like this.

EverVolv have a bravo nightly build for 4.2.1 but I have yet managed to make the ROM work on HD2. I got to similar state as you test rom (without compiling sources). Perhaps you have more experience on how to make a better port for 4.2.1
[HD2 Android NAND Development] wwchang:
I wish I could start a thread for these topics surely but these days due to some changed personal circumstances esp in this new year, even I'm finding it difficult to participate in the HD2 threads as it is.:crying:

(sigh) Honestly you know I'm not really that good of a porter, and perhaps if I were I wouldn't have made an effort to secure compiling. I could never quite find a 'systematic & sure' way to know exactly which dll / .so files one needed to borrow in from the donor rom, and that made porting a frustrating, trial-and-error task to face.

Compiling seems interesting as also it seems the whole android effort as open source is favoring to learn, compile, and do your own rom. Sometimes it's been almost more interesting to go through this process than actually to put out a rom - like the journey's itself is just as interesting as the destination.

Though compiling for JB 4.2.1 has had different issues than for JB 4.1.2 I've found.

For JB 4.1.2 of the entire compile being done to finish within the PA 4.1.2 sources for this rom, only a couple of .so though needed to be built within Evervolv's sources, those relating to sound modules - though by using HTC Passion as a target build rom entirely within the Evervolv sources this can be easily resolved.

For JB 4.2.1 it happens that qsd8k sound modules are no issue, but hwcomposer.qsd8k.so of the graphics system refuses to be built whether building for AOKP_LEO 4.2.1 or Evervolv_LEO 4.2.1 - though it builds easily for Evervolv HTC Passion and then you can just borrow over that as like a 'prebuilt', just like if you are porting or patching an .so for some rom.

And also ril system for 4.2.1 is proving a difficulty for leo builds, but I've asked of this issue in the Evervolv irc channel and one of the Evervolv team is in the process of giving some advices - having a problem almost exactly as in this thread, with Stk.apk not running to do some initialization in the ril system, which then prevents phone & data too:

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

I'm trying a different make configuration setting for ril too, which may resolve that, but I need to do some more test builds to see how it results.

Anyway, test compiles take too much time too, ~2+ hrs each for me now, and I'm waiting for an upgrade on motherboard, cpu, & esp more memory (I only happen to have 4g right now, and will probably upgrade to 32g), and that should help doing android builds drastically too, argh.

.
[Nook Color Q&A, Help & Troubleshooting] shawnbrown303:
I can not boot into recovery mode on nook color 1.4.3 model number BNTV250. I was able to boot intor recovery mode once I had flashed a rom that allows the nook to run side by android. I did a factory reset from the nook menu and could not boot android after that only nook. tried to boot from sd card afterwords and it would not boot recovery.
[Nook Color Q&A, Help & Troubleshooting] hwong96:
This is the nook color bnrv200 forum. You have a nook tablet. Please post to your issue in that forum. The ROMs in this forum are not compatible with bntv250.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] trifos:
I have the GT- i9305N 4.1.1

Baseband version:I9305NXXALI8

can make install rom from i9305 4.1.2 in mine ι9305Ν?

if I make installation from i9305 rom in i9305N it will work mobile?
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] vwbest16:
Yes.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] latousakis:
Are you 105% sure about that? Like many others, the phone came from a skroutz store, and it was the Swedish. Of course there is no difference with the only exception of the Tele2+ bloatware that can be easily removed. But the battery and response is not the same as with 4.1.2... On the other hand I need you to be absolutely sure, as I don't need a 560 euros brick :P
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] nateboi81:
Any I9305 ROM will work on any I9305. The letter at the end is irrelevant
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] Rekoil:
Yep, just not any radio, that one is region-specific (on the I9305).
[Android Software/Hacking General [Developers Only]] TheMisza97:
Hi guys i'm new on this forum and this is my fist post... I wanted to know is there any (working) way to root Mytab 7? I searched forum but didn't found it. I'll be thankful if someone could told me how...

(Sory if there are any language gaps)
[Android Software/Hacking General [Developers Only]] AndyFox2011:
Find SuperOneClick on google and try that...

edit: link to his ShortFuse's website: http://shortfuse.org/

Sent from my HTC Desire HD
[Android Software/Hacking General [Developers Only]] TheMisza97:
It told me that it's rooted but when i wanted to update super user it told me that i dont have admin previlages and even "Root Explorer" cant get su permission
[Android Software/Hacking General [Developers Only]] AndyFox2011:
Try doing a temp root first, then a full root, and make sure USB debugging is on
[T-Mobile Samsung Galaxy Note II] reft4u:
I TAKE NO CREDIT FOR THIS JUST REPOSTING and REROUTING USERS LIKEME TO THE RIGHT DIRECTION.

ALL credit to - developer - LegendK95

Thought of Informing other users -

See original Thread - http://xdaforums.com/showthread.php?t=2075916

Using this myself and works awesome. !!!! :good:
[T-Mobile Samsung Galaxy Note II] Gwanatu:
What keyboards do you use with what? I've never thought of trying to use the S-Pen to type, too difficult. Would love to see a good solution. Thanks for this changer link!
[T-Mobile Samsung Galaxy Note II] moSess:
Confirmed working. Awesome mod
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] jee'sgalaxy:
So i hard bricked my phone a month ago and git it resurrected. I flashed the aosp based roms but every week, the mic in the phone stopped working and i have to reflash the roms to get the mic back then work. What is wrong here?
[T-Mobile Samsung Galaxy S II SGH-T989] ayyeeallen:
what's the best combo for pure battery life? everyone's been saying smartassv2 with sio but its not really giving me great battery life. what do you guys use?
[T-Mobile Samsung Galaxy S II SGH-T989] ayyeeallen:
oh and can you guys please state the amount of battery life you get with the combo you're using. thanks :)
[T-Mobile Samsung Galaxy S II SGH-T989] FineTalent:
I've been using smartassV2 in combination with SIO scheduler for general use on my T989 and my old Captivate, it has helped my phone last a day or usually longer.

I don't really look at my 'battery usage' as it varies with what I'm doing in the day, for the most part it did make a big difference compared to the defaults.

Also, if you're looking for better battery results underclocking/undervolting and have certain governors turn on during different phone usage will definitely make a huge impact with your battery results.

You can do this with many apps, but the one that has been working for me is usually between Pimp My CPU and SetCPU. Cheers!
[Captivate Q&A, Help & Troubleshooting] rogleete:
I replaced the speaker in my i897 and now I get no signal for WiFi, Bluetooth and cellular service. I pulled the case back off and noticed the smaller gold spring loop that makes contact with the inside of the case in the corner near the camera is broken off. Would this be causing my issue or is the new speaker or something else to blame. Where do I start diagnosing and is there a DYI to fix the broken gold spring piece. (Identical to the one that touches the battery cover but smaller and under the case.

Thanks, I'm not ready to give up this phone.
[Captivate Q&A, Help & Troubleshooting] BWolf56:
I haven't opened mine in a while but if I remember it right, the connections are right beside the speaker so you most likely damaged it. I can't help you much myself on how to repair it but mobiletechvideo.com might be able to (or even repair it for you). Good luck!
[Captivate Q&A, Help & Troubleshooting] rogleete:
The white antenna cable near the speaker appears fine, the new speaker works fine, WiFi works withing 8' of the router. Leads me to believe there is some antenna connection servicing BT/WiFi/cell in one not making a solid connection. Its not the large white cable though.
[Captivate Q&A, Help & Troubleshooting] BWolf56:
Our phone is known to have bad signal (Wifi, GPS and such) when there's something covering the top of the phone so perhaps there's something interfering near the antenna?
[Android Apps and Games] PhilPrado:
I've found a great reading app for my 4 year old. It's called A Day at the Zoo. It's an interactive story where the child can make decisions (which are always the right one). The voices are male and female and are very pleasant to listen to. You can also make pictures of the animals :) My kid loves it and it's much better for them than just sitting and watching TV as they get to read and interact with this app. Try it out: https://play.google.com/store/apps/details?id=com.sorcerygames.adatz
[Samsung Galaxy Nexus] maaartins:
bootlop

BOOTLOOP ON CM10.1

I liked the idea that punishment did not work
[Samsung Galaxy Nexus] Mikey:
Deodexed Stock JOP40D ;)
[Samsung Galaxy Nexus] maaartins:
yes I saw, only tried in cm by stubbornness unfortunately not worked do not intend to go back to stock ...
[Samsung Galaxy Nexus] mixtapes08:
Will this change the position of the navbar depending on the screen rotation or it will just stay at the bottom even if your using it in portrait mode?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] waallace:
Bootloop on Deodexed Stock JOP40D ;/
[Samsung Galaxy Nexus] mixtapes08:
I think this is for stock aosp rom.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] maaartins:
work on kalo aospa ;) great !
[Samsung Galaxy Nexus] evilisto:
It won't change portrait navbar at all. just change landscape layout only.. :)

Sorry for the inconvenience... but.. I'm using deodexed stock rom too and this mod works well on my phone..
[Samsung Galaxy Nexus] retskrad:
Will this work on stock 4.2.1. but only rooted?
[Samsung Galaxy Nexus] GuestK00230:
So let me get this straight, the portrait mode doesn't change AT ALL, but in landscape mode, nav bar is on the bottom? We have a similar implementation on Paranoid Android, but it makes the nav bar in portrait mode smaller :(
[Samsung Galaxy Nexus] exb0:
The patch asks me to specify file to patch. What do I do?
[Samsung Galaxy Nexus] AbhishekS:
Can you please tell how did you do it? I wanna try it on a custom ROM. :)
[Samsung Galaxy Nexus] evilisto:
No.. it won't work on odexed stock rom..

Yes, this mod won't change portrait navbar layout at all. I'm not sure but I think PA rom's feature is related to changing UI to small tablet mode(shortSizeDp < 720, like Nexus 7). But this mod is just change navbar position only in phone UI's landscape mode. So they are basically different things..

I'm not sure what you trying to do exactly but... If you want to make this mod for other custom roms, you'd better to apply my patch manually..

Use my patch in OP. I think you'd better to apply it manually... See this link : http://drupal.org/node/534548

And this simple guide could be helpful to you too... : http://xdaforums.com/showpost.php?p=32424247&postcount=17
[Samsung Galaxy Nexus] exb0:
Yeah I was applying your .patch file to my source. I went to /frameworks/base, pasted the file there and executed "patch -p2 filename.patch" . its asking me for a file name or directory to patch..
[Samsung Galaxy Nexus] evilisto:
You have to type..

patch -p2 [B][COLOR="Blue"]<[/COLOR][/B] (patchfile_name).patch

And if it doesn't work, you have to apply it manually one by one.
[Samsung Galaxy Nexus] P500:
Could someone using Bigxie's JOP40C ROM make this mod? I don't have access to Linux and AOSP sources to do it on myself. Or would that one work, too? The changes from C to D weren't that much.
[Samsung Galaxy Nexus] J-Hop2o6:
Name of the last game (below NFS)?
[Samsung Galaxy Nexus] evilisto:
That is Wild Blood by gameloft.
[Samsung Galaxy Nexus] cyhamada:
Does this mod effect the "expanded desktop" feature that is in most custom roms?

thanks in advance.
[HTC Droid DNA] Seth Turner:
Ubuntu just announced Ubuntu for Phones. I would love to install this when its available. Can we get a folder for Ubuntu development?
[HTC Droid DNA] utkaar099:
just saw it too. its sick, they should have one for every phone lol

the HTC HD2 already has one since the desktop Ubuntu was ported a long time ago
[HTC Droid DNA] MustafaHadaKing:
you can run ubuntu on any android. I found a guide on youtube

http://www.youtube.com/watch?v=I0PNsnNe3E0

Note its the same ubuntu as the one on a computer not one optimized for a phone
[HTC Droid DNA] Seth Turner:
Yes, I have known about Ubuntu for Android for a while. I am talking about Ubuntu for Phones. It uses a new, amazing button-free touch GUI. Using this would eliminate the dumb menu button that's taking screen space on my DNA.

Ubuntu is now an open-source touch-based OS for smartphones and tablets that is also a full-fledged desktop OS. This is amazing!

I just can't figure out how they support ARM and x86 architectures with the same kernel.

Check it out at http://ubuntu.com

Sent from my HTC6435LVW
[HTC Droid DNA] madzozs:
You could also use one of the roms, or flash Nitsuj's mod to get rid of the menu button on the bottom.
[HTC Droid DNA] jonah1234:
I would really love to have this ubuntu for android that linux themselves are releasing and have the ease of flashing it as a Rom. But I don't think they will release a version for every single device. I guess we will just have to hope someone to port it for us.

Sent from my HTC Droid DNA
[Samsung Galaxy Nexus] franciscofranco:
Hey everyone, lets get this thing started.

One of the big problems in this device is the Smartreflex calibration on higher than stock frequencies (because thats what we hackers do here at XDA). I haven't tried to improve the algorithm just yet but I would be very happy to start discussion on this matter and if anyone has ideas, code snippets. Just bring it so we can discuss it properly. I will be contributing with code soon when I have time to take a deep look on the driver.

I won't tolerate off-topic, or questions like "My dog ate my kitten, is that kernel's fault?", so this will be VERY heavily moderated.
[Samsung Galaxy Nexus] simms22:
honestly, id rather just have smart reflex gone. i feel more comfortable being in control then letting an algorithm decide.
[Samsung Galaxy Nexus] franciscofranco:
Why? That way we would have to hardcode all the voltages and we would have to set the values a little bit higher than what SR usually calibrates to prevent **** going haywire with some poor hardware devices. SR does a good job and mostly never misses a good sweet spot between stability and battery savings.

Do you have any set of voltage values you would recommend that would work on 99% of the devices?
[Samsung Galaxy Nexus] simms22:
true.

since all of our devices seem to like different values, i guess there isnt a value that would work on 99% of our devices, unfortunately. so it would have to be a range of values. i guess i was looking at it from a users point of view, and not from the developers side.
[Samsung Galaxy Nexus] franciscofranco:
Maybe we can try both, trying to hardcore them and let users find their own sweet spot and at the same time perfect the algorithm, I believe theres margin for improvement. If you find some good values feel free to share here.

I also hope some other good developers come here and throw out their ideas.

Small off-topic but related to this new forum, can you create a new topic about your SoD experience (the email you sent us how you could reproduce the issue) would be very nice we could discuss that as well in a specific topic.
[Samsung Galaxy Nexus] ak:
smartreflex

I do not know if the code is optimized or not I have no basis to evaluate.

From my experience I have seen that in order to avoid problems related to the various soc, I decided to let users tinker with voltages and smartreflex.

This is why in some cases I raised the voltages.

From that day problems with my kernel is greatly decreased. :fingers-crossed:
[Samsung Galaxy Nexus] franciscofranco:
What do you mean by tinkering with voltages and smartreflex? Thats what I have in my kernel at the moment: custom voltage interface (from Ezekeel) and SR is also active, so I dunno what you mean.
[Samsung Galaxy Nexus] zillinder:
Franco, would you mind sharing the code of SR in here and let us have a look at it?

I haven't seen it so far plus I am in no way a kernel dev, but I'd like to see it and throw something at the thread whichever comes to my mind, always ontopic of course :laugh:
[Samsung Galaxy Nexus] supernova_00:
I might be pointing out the obvious here but sometimes the obvious isn't so obvious...has anyone contacted Nishanth Menon that is named in the code header to see if TI has a latest and greatest SR? I would assume they would since phones are coming out now with higher CPU speeds then what the current SR could handle around two years ago. I see the guy is pretty active online with posting stuff to open source sites and still deals with smart reflex related things as this site shows: http://marc.info/?a=124043331500007&r=1&w=2

I dunno what that site is or know what any of that stuff means but I just stumbled upon it and just wanted to show he is active with TI and smart reflex work, among other things
[Samsung Galaxy Nexus] osm0sis:
As I've always seen it, the limitations/problems with SmartReflex are as follows:

- Can't calibrate to a lower voltage than 830mV (problematic when 384MHz generally does fine at 775mV and 192MHz generally does fine at 725mV).

- Does not handle frequencies above 1305 well at all (calibrates them the same as 1228, so it must be an upper limit to its bracketing/range, almost as though it sees it as the same as 1228).

- Could definitely be a bit more aggressive safely when everyone can UV the SR values by another 50-100mV (so I'd say another 50mV safely across the board).

No idea how to proceed on any of those, but I thought it might help to make the limitations a bit more clear. I'm looking forward to following the progress of this thread. Great idea, Francisco. :)
[Samsung Galaxy Nexus] Ashtrix:
Smartreflex improvement

So you mean the Lean's 1.6Ghz SR does also do the same, 1.6GHz calibrates as 1.2GHz range instead of the real application :rolleyes: ??

and it would be great if we could overcome the 2nd limitation ;) .
[Samsung Galaxy Nexus] osm0sis:
Most kernels (probably all but I haven't personally checked) disable SR for frequencies above 1305, but yes I believe that's why it doesn't work. Franco used to have the cutoff for SR be voltage based and on my device 1536 UV's by 100mV stably, so if I left SR on and lowered it too much (75mV) SR would act on it and calibrate it to the same voltage as 1228, which of course was too low and froze and crashed. So yeah, its as though it needs new brackets/ranges added for higher voltages.
[Samsung Galaxy Nexus] blackhand1001:
Has amazon released the kernel source for the kindle fire hd 8.9? That uses a ti omap clocked at 1.5ghz stock. Maybe a look at the smart reflex code on that would shed some light.
[Samsung Galaxy Nexus] osm0sis:
Both good ideas!
[Samsung Galaxy Nexus] Ashtrix:
According to SR v1 by Imoseyon & his explanation says he had modified the SR code to override the below limits ;)

1) VDDMIN - 830mV for all three domains,

2) VDDMAX - 1410mV for MPU, 1260mV for IVA, and 1200mV for CORE.

So, i think do already have a better version of SR over the TI's stock SR from Lean but only a few phones can handle the SR calibration for the 1.5+ GHz freq :rolleyes: .