yashsingh1/xdaforums huggingface dataset:
[Desire HD General] Crithian:
I've ported JoyOS on the inspire, same thing basically(unfortunately their site was down last I checked so no more updates on their end), it has a CM7.2 base. Its seems to be completely stable. Please keep in mind I've tried a few other times, this has only been because i wanted to make my own ROM for my personal use. I am by no means to the caliber of development or debugging as some of the awesome groups Ive seen over the past year. And I am trying to learn as quickly as possible about the in's and out's (coding, build prop edits, troubleshooting the whole nine as it were to keeping a rom up and stable).

So with that said, I would like to put out the port on the development forums, but am kinda weary as I am new to doing this, I may not be able to solve or answer all questions. Should I release it with what i have, keep learning, and simply state that in my intro? I saw one release of this port a long time ago, SeaPathJoyOS was the name I believe, liked it so much, that after it was stopped on dev, I made my own.

any feed back would be awesome, thanks in advance.
[Desire HD General] Reinaldo33897:
You can release it and see what people think of it. There may be some who can help with any issues. That's what we are all here for just remember to warn flash at your own risk.
[Desire HD General] Crithian:
Ill put it up for dhd tomorrow. I have it on the Inspire side tonight. Hope folks like it.
[Desire HD General] imdecoding:
can u port webOS? it would be awesome if you do :)
[Desire HD General] Crithian:
Certainly can look into it. ;)
[Desire HD General] festisen:
sounds interesting. maybe i have a try.
[Desire HD General] imdecoding:
maybe this can help a bit:

http://webos-ports.org/wiki/Galaxy_Nexus_Build_Setup

:laugh:
[Desire HD General] Dbugger:
Give it a try!
[Nexus 4 Android Development] jellybellys:
I just decided to cook up some clockworkmod recovery for the nexus 4. Build it using the stock kernel that came in the JOP40C factory image.

Here's the linky:

http://goo.im/devs/jellybellys/mako/recovery/cwm/cwm6-jellybellys-mako-bld2.img

Also, I don't have my nexus 4 yet to test on, so if you are lucky enough to have yours already, flash at your own risk. I would reccomend using "fastboot boot recovery.img" first to test. And if you screw up anyhow, here's the stock recovery: (I didn't make this one)

http://goo.im/devs/jellybellys/mako/recovery/stock/recovery.img
[Nexus 4 Android Development] revealthecat4:
recovery

May i know how to boot to stock recovery on N4? Thanks.
[Nexus 4 Android Development] jellybellys:
adb reboot recovery
[Nexus 4 Android Development] Ranguvar:
Thanks. Is this CWM 6.0.1.5?
[Nexus 4 Android Development] tgtoys:
Shouldn't it be "fastboot flash boot recovery.img" to send recovery to the phone?
[Nexus 4 Android Development] krarvind:
fastboot flash recovery recovery.img to send recovery to the phone.
[Nexus 4 Android Development] Ranguvar:
He's recommending using that command to just run the image first without flashing it to see if it works right..
[Nexus 4 Android Development] Unconn:
Yeah, but that was to test boot to it, not flash it.
[Nexus 4 Android Development] jellybellys:
fastboot boot recovery.img to test it, fastboot flash recovery recovery.img to install it.
[Nexus 4 Android Development] randomblame:
I usually package recovery.img's as boot.imgs for testing that way you just reboot recovery to recovery - get it? Makes testing simple for the inevitable broken button mapping bad lun path and derpdy derps that are bound to happen
[Nexus 4 Android Development] KidCarter93:
Anyone tested this yet?

''Absolute power corrupts absolutely, but absolute powerlessness does the same''
[Nexus 4 Android Development] tgtoys:
Gotcha..i misunderstood. Thanks all around ;)
[Nexus 4 Android Development] spences10:
No that would flash the recovery image to the boot partition

---------- Post added at 01:11 PM ---------- Previous post was at 01:10 PM ----------

Thanks for these OP

I'll give them a go if/when my N4 arrives
[Nexus 4 Android Development] Egooktamuck:
Test is fine but flashing is not working...
[Nexus 4 Android Development] USSENTERNCC1701E:
Try mounting /system through the menu. See if that errors out.

Also, did you try making a nandroid and restoring? I'd do data only for starters, just to be safe.
[Nexus 4 Android Development] smirkis:
no offense, but why does everyone wanna be the first every time a device comes out. wait til you get it, test it, then release it.. but thanks anyway
[Nexus 4 Android Development] Egooktamuck:
I think the problem is, that this Version is based on JB 4.1.2!

Now i wait until Koushik is finished with his work and CWM is ready for 4.2
[Nexus 4 Android Development] m11kkaa:
offtopic: why occam? I thought Nexus4 has the codename "mako"
[Nexus 4 Android Development] USSENTERNCC1701E:
Check the google source page, listed as occam
[Nexus 4 Android Development] IINexusII:
the software build is named occam. the hardware name should be mako.
[Nexus 4 Android Development] USSENTERNCC1701E:
Ah, you are correct.
[Nexus 4 Android Development] tgtoys:
Coincidentally, Occam = Macco backwards. Macco/Mako...hhmmmmm....... :cyclops:

Sorry to go off topic. Had to mention it.
[Nexus 4 Android Development] jellybellys:
Symlinked a directory called mako on my goo.im to prevent any confusion. I don't really care what it's called.
[Nexus 4 Android Development] jellybellys:
Made a new build that should fix the flashing problems... check the goo.im:

http://goo.im/devs/jellybellys/mako/recovery/cwm
[Nexus 4 Android Development] randomblame:
I remember you from the a500 forums you kanged our source and presented it as your own work - so you have a history of trolling and releasing an untested recovery to the notoriously bad at reading masses is fairly stupid. packaging it as a boot.img allows you to boot to the untested recovery in a way that's safer or you could just wait till you got a device in your hands to start releasing ****. I have a zimage that's completely untested who wants it? no one. anyways I'm out gfys
[Nexus 4 Android Development] fkrone:
Thanks for this hint. The strange thing is, that I published the recovery.fstab a few minutes before this recovery was published (-> http://xdaforums.com/showpost.php?p=34085293&postcount=10).

Don't know if he used it but if he used it it would be nice to give credits.
[Nexus 4 Android Development] jellybellys:
Kanged your source and presented it as my on work? I did provide attribution and a link to your source so you could see who commited to it. If you don't want people using your source, then don't release it. (not saying that I encourage that)

The zImage is from google's factory images that they released. I am fairly sure they tested it.

...there is a reason I wrote flash at your own risk in bold. Hopefully the people of this world are capable of reading directions and following them.
[Nexus 4 Android Development] jellybellys:
I actually pulled the recovery.fstab file from google's stock recovery, using these instructions --> http://xdaforums.com/showthread.php?t=443994
[Nexus 4 Android Development] randomblame:
Only after you were called out for it did you give any sort of credit. That was the issue.

I was saying that I have one that I've compiled that's untested but I'm not releasing it for those reasons

few are that's why I was offering an alternative but the quality of your character shows through with every post you make.
[Nexus 4 Android Development] smirkis:
same stuff happened in the N7 forums. don't release untested recoveries... there is a big difference in the 4.1.2 and 4.2 recoveries. telling people flash at your own risk or not is not enough. build a recovery, test all its features, and release it. noone on here signed up to be your beta tester. lock this ish up lol. a real recovery should be coming soon enough
[Nexus 4 Android Development] KidCarter93:
Guys, this is a development thread, not a playground for your disputes with each other or what not.

This kind of discussion either shouldn't happen, or at least happen via PM.

''Absolute power corrupts absolutely, but absolute powerlessness does the same''
[Nexus 4 Android Development] MadCobbler:
+1 ... and so it starts... get ready for loads more of this guys lol ;)
[Nexus 4 Android Development] eep2378:
Just because google releases new code(i.e 4.2), doesn't mean people should start putting out untested, unproven, recoveries, images, etc.

At least wait to get the device and fully test before releasing. Simply saying flash at your own risk is not enough in this instance. If anyone has spent enough time here knows, people don't take the time to read and understand what they are doing. Then they'll be crying foul when things go awry.
[Nexus 4 Android Development] Stryder5:
Is this the stock recovery? Or stock boot image?
[Nexus 4 Android Development] shabbypenguin:
while i agree until a tested and true recovery has been made there shouldnt be a thread as it will only lead to confusion, an example being lets say koush steps in and makes this himself, he isnt gunna post in here about it.

but i have one tiny issue with what you posted. you said no one signed up here to be a beta tester, and that is partially correct. this is a development oriented forum, where like minded people can share ideas and improve on things. anyone here shouldnt be flashing anything unless they are willing to take the inherit risks and hopefully common sense.

this stuff is way to easy for people to not be able to take 5 mins to read a very well guide someone somewhere put together and figure it out. instead we end up with people who want the finished product and dont care about the road there.
[Nexus 4 Android Development] smirkis:
yes shabby, both me and you know and understand how android works. but not every person poking around the developer section knows as much as say, us. lots of people get excited with new devices, and new devices bring new users to our world. we've been around for years, others are just starting to come around. yes they "should" read about how android works but you know this just isn't the case most of the time.

what i meant by "noone signed up to be YOUR beta tester" was pretty much what i posted. ask for a few individuals to PM you to test it out, run some backups, restores, flashes, fix user permissions, and report back. if all is well, release it to the public. hell even im down to test it out and will when i get off of work as i have my nexus4 sitting here in my lap. but atleast i have it, and will test it before i suggest anyone else even try to play with the image. he built it, without a device on hand. and posts it saying use at your own risk.
[Nexus 4 Android Development] shabbypenguin:
i understand your argument. and i agree with it :P

i tend to work on a lot of prepaids with my team as such we get a lot of new users and i have no problems helping them learn and guiding them. however you will always have idiots who just want to do something cuz they saw a youtube video of some dudes brother for a phone they once saw at a mall kind of thing.

IMO people like that should be left to their own devices :P. i had a guy swear he bricked his phone because he double clicked on adb.exe, i spent 20 mins trying to convince him otherwise before banning him from the irc because he was just so dead set on it :/

in any event im just waiting on good cwm images for the new nexus devices so i can add support for my nexus one click scripts :)
[Nexus 4 Android Development] jellybellys:
Wrong. Here is the original version of the post, with the credit in it: http://xdaforums.com/posthistory.php?do=compare&p=29280871

I'm pretty sure that google tested their precompiled kernel. :)

[QOUTE]few are that's why I was offering an alternative but the quality of your character shows through with every post you make.[/QUOTE]

You remind me too much of Wes Lanning.
[Nexus 4 Android Development] jellybellys:
I don't believe in the theory of "testers."

I made it clear in the OP that this has not been tested and that you should make sure it works first by using "fastboot boot recovery.img"

Let me dissect the statement "flash at your own risk":

You better know what you are doing if you flash this, because if you break your device, I don't care.

I know that sounds a bit harsh, but that is what it means.

--------------------------------------------

From now on let's keep disscusion related to the following:

1. Development

2. Questions

3. Useful information

Let's keep discussion away from other things I have made in the past and annoying complaints.
[Nexus 4 Android Development] Stryder5:
I booted your recovery image but it didn't let me flash anything.

I ran fastboot boot recovery.img, which got me into Clockworkmod recovery. I tried to flash a zip but got an error saying that the path of /sdcard could not be found.
[Nexus 4 Android Development] jellybellys:
Did you use build 1 or 2? I messed up on the recovery.fstab in build 1, it might be the problem.
[Nexus 4 Android Development] Stryder5:
I'm guessing build 1 since your build 2 link isn't working at the moment.
[Nexus 4 Android Development] mskip:
@Jellybellys I have changed the title of the thread to Untested until it is proven to work without problems. As soon as the recovery is working properly then you can change the title as you wish.

@Everyone This is a thread in a Development Forum. As such please try to keep posts proactive and take any *****ing private.

Posts that don't contribute to the thread may be deleted.

Mark.
[Nexus 4 Android Development] Stryder5:
Ah, I assume this is the proper link to your build 2:

http://goo.im/devs/jellybellys/mako/recovery/cwm/cwmt6-jellybellys-mako-bld2.img

If that is the correct link, then it has the same error not mounting /sdcard to flash any zips.
[Nexus 4 Android Development] jellybellys:
That is the second build with the fixed recovery.fstab. I think it may be an android 4.1/4.2 thing and we may just have to wait for koush to update to 4.2. That being said, I will tinker with it once I get my nexus 4 (hopefully very soon, it's in the mail.)
[Nexus 4 Android Development] :
Had to give this thread 5 stars to bring it up from its low rating. To whoever rated this thread 3 stars, I'm pretty sure you have nothing to offer to development. At least someone stepped up early to try and get us an early working recovery.
[Nexus 4 Android Development] evaradar:
So when will CWM be releasing their recovery for the Nexus 4? http://www.clockworkmod.com/rommanager
[Nexus 4 Android Development] Stryder5:
Ask Koush, not us lol.
[Nexus 4 Android Development] evaradar:
Heh. How do I contact him?
[Nexus 4 Android Development] a5ehren:
Koush said on Google+ that Rom Manager is broken in 4.2 and he's working on fixing it. He thinks he's going to have to rebuild CWM on 4.2 to fix it.
[Nexus 4 Android Development] evaradar:
Hmmm then it will be uploaded on the CWM's website right with the Nexus 4/7/10 beside it?
[Nexus 4 Android Development] smirkis:
he doesn't have the phone yet, and isn't like the OP in this thread. when he gets it, he's gonna build one and fully test it. and you will be able to download it from rommanager or that website for manual flashing. koush should have one some time next week maybe. there are barely a few hundred people who have the phone so far, wait til it hits the masses.
[Nexus 4 Android Development] jellybellys:
I read somewhere on Twitter that there has been some changes to twrp that enables 4.2 support, I will look at it when I get home tonight.
[Nexus 4 Android Development] smirkis:
its been updated

http://teamw.in/project/twrp2

no release for n4 yet tho
[Nexus 4 Android Development] shabbypenguin:
there is no release because no one has made it. dees_troy does an amazing job with the recovery as it is. he maintains a lot of devices and has a lot of people cry in the irc when roms fail etc and they think the guy who wrote teh recovery they used to flash said crap rom should fix it...

anyways if im bored tomorrow and no one has done it ill whip up a beta twrp for yall hopefully it will have no bugs/issues
[Nexus 4 Android Development] KidCarter93:
I've just been told by Stryder5 that a working CWM can be found here. He's confirmed it working as tested by himself.
[Nexus 4 Android Development] mskip:
As there is an official cwm touch recovery there is no need for this thread.

Thread closed.

Mark.
[Nexus 7 Q&A, Help & Troubleshooting] vtmike:
I used an ota file some one posted to update to 4.2 and ran into a problem. I have a 16gb model and now only have the 8gb storage available. It seems the ota posted was for a 8 GB nexus and it possibly repartitioned my nexus to match the 8 GB nexus. I tried to search for a solution and couldn't find anything. Anybody know how to fix this.
[Nexus 7 Q&A, Help & Troubleshooting] khaytsus:
Nope, it didn't happen.
[Nexus 7 Q&A, Help & Troubleshooting] Omar04:
That have nothing to do with the OTA. Mine is a 32GB and used the OTA posted all fine. OTAs are universal (Nasaki) regardless of emmc capacity.
[Nexus 7 Q&A, Help & Troubleshooting] phonic:
What they said.

First, a non-compatible OTA would not work since it would fail checksum validation. Second, the updates are universal for the model (ie: same for 8,16 or 32). Third, the only low level flashing this update does is on bootloader and boot. It simply patches the files in /system and leaves userdata alone. So it's highly unlikely what you're saying happened. Or if it did, it was most likely due to something else. If your system's filesystem is really that messed up, you might need to reflash it to stock to get fixed. But I would suggest triple checking to make sure you aren't wrong.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ptizzl:
Hello,

I was wondering if there are any advantages or disadvantages to using FoxFi over the built in tethering option for CyanogenMod 10. I love how easy the built in option is with CM10 but if it's more likely to be detected I'll keep with FoxFi. I've been using FoxFi for quite a while and just re-upped to CM10 today and am curious about this since the default ROM blocks WiFi tethering without a data plan through ATT.

Thanks!
[Samsung Galaxy Nexus] karttv:
Hello Everyone

I'm a user from China. I have updated my Galaxy Nexus to Android 4.2 through OTA.When I touch the different icons ，I got FC（Unfortunately，Switch Pro Widget has stopped）。Can anyone help me？ Thx lots!

My Switch Pro VERSION is the latest : v2.2.0

UPdate：I reinstall it，all the icons works except the ”Data Connection“ icon。
[Xperia Arc Q&A, Help & Troubleshooting] Sogat:
I did a backup of my phone today using SE's Backup and Restore app an app which makes a bakcup as a .sdf file.

When I restored it, it gave me an error. Knowing that Sprite Restore also deals with .sdf file, I tried it too. However, it game me the error that the files aren't readable.

I really need my contacts back.. Anyone can help me?

Thanks
[LG Optimus Black] logannz:
What is the fastest but stable overclock and undervolting for LG Optimus Black on Zeus v7.04?
[LG Optimus Black] sekhar13515:
Fastest mean 1350 Mhz available in Zeus, but on safeside...1100 is preferrable of most users and is recommended.

In view of voltage (0) default is good.

InteractiveX is the latest and gives better battery backup..
[LG Optimus Black] JaredMLG:
For me,Best overclock is 1300MHz(you can put 1350 if you'd like)governor is smartass v2 and i/o scheduler is deadline.That is good enough for gaming and other stuff.For undervolt,go as" under" as you want;)
[LG Optimus Black] nicholaschw:
After studying on all Sources, Undervolting renders little or no use to saving power. It also reduces your performance. Take note.
[LG Optimus Black] logannz:
I overclocked to 1350Mhz and my phone constantly restarted so I put it down to 1200Mhz and it seems to be fine for now
[LG Optimus Black] xonar_:
You can't OC that much without pushing voltage up aswel.
[LG Optimus Black] logannz:
What do you recommend changing the voltage to if I'm going to overclock to 1350Mhz?
[LG Optimus Black] xonar_:
Push it up one unit at a time until it reaches a stable point (Just watch out for heat) . It's better to leave it at 1.2Ghz since I don't think you'll experience any lag at 1.2.
[LG Optimus Black] logannz:
I put it up to 1350Mhz and voltage on the maximum of 5 and so far it's been really smooth without restarting. I'm not too worried about heat as my old Motorola Defy would get to about 60 degrees Celsius and I just played a couple of games and my phone is sitting around 30-40 degrees Celsius
[LG Optimus Black] sekhar13515:
Why don't you take serious the BATTERY HEAT, it will cost life sometimes..
[Samsung Galaxy Nexus] troyster89:
Does anyone else have lag when rotating the new camera in 4.2? Its really annoying and it seems ridiculous that google would release it like this.
[Samsung Galaxy Nexus] shahrukhraza:
Yep. I see it. Its honestly really annoying...
[Samsung Galaxy Nexus] Loureiro:
They only had to rotate 2 little icons... can't understand why they had to apply fullscreen rotation to camera.
[Samsung Galaxy Nexus] troyster89:
Exactly, i thought it was just a bug when i tried the 4.2 apk. I just figured it was due to it being for the nexus 4, i was pissed when i saw that it carried over to the official release.
[Samsung Galaxy Nexus] AlaneCzeQ:
Please star this issue in to get it recognized by Google:

http://code.google.com/p/android/is...rs&colspec=ID Type Status Owner Summary Stars

it is quite annoying ...
[Samsung Galaxy Nexus] feneksi:
Stared it! Hope they'll fix it soon:fingers-crossed:
[Samsung Galaxy Nexus] jesusice:
Everyone make sure you're just starring. No comments. Comments spam everyone that has starred it.
[Samsung Galaxy Nexus] thomstrack:
Android Dev about this:

"Unfortunately this is working correctly. The new app has to let the system rotate so that when you swipe over to view recently taken pictures the status bar, action bar, and navigation bar are in the correct orientation. Otherwise you have the bad transition into/out of camera that was in 4.1. We will try to make it faster and more responsive, certainly, but currently this is a "lesser of two evils" sort of thing."
[Samsung Galaxy Nexus] vbauer86:
Well lets hope the magic google devs make the animation faster without seeing laggy animation.
[Samsung Galaxy Nexus] d0g:
This is extremely boneheaded and annoying. The stock Samsung camera -- and every other intelligently coded camera -- only rotates the HUD, not the damn preview image.

Just. Plain. Stupid.

Maybe the new boss of Android will realize this...
[Samsung Galaxy Nexus] otaconc:
Yeah, its the first thing i noticed.

Can i just flash the camera apk from JB 4.1 on 4.2.2?
[Samsung Galaxy Nexus] jsgraphicart:
I turned off auto rotation and it fixes the laggy camera rotation problem. But if you want to view your photo in landscape you have to turn the Auto Rotation back on. I dont use my phone in landscape very often, if at all. So leaving the auto rotation off hasnt been a big deal for me. If there was a way to just turn the rotation off in the camera only, that would be nice.
[Samsung Galaxy Nexus] kpoverdorf:
Glad I'm not the only one noticing this.
[Samsung Galaxy Nexus] snsnselaoyeye:
turn off auto rotation,me too.
[Samsung Galaxy Nexus] akira02rex:
This is stupid, how the hell can you take landscape photos?
[Samsung Galaxy Nexus] !!11oneone:
I always have auto-rotation off.

I can confirm 100% that the camera still takes landscape photos, as it still senses which way is down. But you don't get the rotation animation which slows the app.
[Samsung Galaxy Nexus] Theme Ishere:
The worst thing is that it doesn't need to lag that badly. The nexus 4 is quite quick in rotating the camera app. Thought it is just raw procwssor power at first,but my nexus 10 also is slow as hell in that category. Well,guess we will have to hope that key lime pie will not end in the 4.2 fiasco...
[Samsung Galaxy Nexus] akira02rex:
Different graphics processors handle drawing calls differently.
[Samsung Galaxy Nexus] t1.8matt:
nexus 7 rotates pretty damn quick even though it's just the front camera. that's odd the N10 is slow.
[Samsung Galaxy Nexus] Simer03:
Is it just me or the animation a lot quicker and more odd looking?

Sent from my Nexus Prime