yashsingh1/xdaforums huggingface dataset:
[JASJAR, XDA Exec, MDA Pro Software Upgrading] vijay555:
[rumour control]

ai118: thanks for the support!

This release will happen, but given how long you guys have had to wait, I'd ask you to continue waiting quietly for a little while more... Buzz is currently coding this thing on my pc using remote desktop, with a remote connection to my Universal.

Now coding this stuff with the hardware in your hand is hard work, near impossible for most. With it in a different country, with no view or access to the phone - well, I'll leave it to your imagination, but it's not easy.

Now couple that with both of us also getting a bollocking from significant others as well, and you'll realise that when it is released, the code will be liberally splashed with our own blood :( I'm typing with one hand, crying baby in the other :evil:

It's unfortunate Buzz pre-announced, but he was so overjoyed when the alpha release worked, he couldn't contain himself. You guys try to be a bit calmer then him, m'kay?

It's coming, and it's one hell of an international collaboration. I hope Buzz isn't stealing my porn while he's connected :( And if he is, well, I was young and needed the money :oops:

It'll be days or less, but for any acts of God.

V
[JASJAR, XDA Exec, MDA Pro Software Upgrading] monakh:
FYI, I am very willing to support a 'Core Duo Laptop' for Buzz drive. I am all for it. We can get some great deals in the States, especially on Dells. Of course, it would have to have an international warranty so I guess Dells are out.

I think Buzz deserves a T60p for his efforts :)

In the meantime, I recommend, as I have done so before that all of us support not just buzzdev.net but this site. Heck, we should even donate a few bucks to Vijay555's site.

And folks who have waited patiently for so long, can wait a bit longer, I am certain. Anyone else who has a problem with the delay can take a hike. No one is compelled to deliver on time here. Everyone does stuff on their own and it's not like they get paid for it so stop your whining and get lost.

Oh, and trexysexy, you are clearly a troll who is jealous of Buzz and mamaich, so please 'buzz off'.
[JASJAR, XDA Exec, MDA Pro Software Upgrading] dmjass:
Agree.... but how can anybody donate if the paypal option is anavailable?
[JASJAR, XDA Exec, MDA Pro Software Upgrading] donkilluminati:
Re: come one buzz make us happy!

and one from austria
[JASJAR, XDA Exec, MDA Pro Software Upgrading] battletank:
Thanks for all your efforts Buzz, and everyone else who is making this possible.

I suspect those being critical of the delays are nothing more than Ebay scammers who rip people off by advertising an unlocking service for silly amounts of money, and are now about to lose their revenue stream... alternatively, they're people looking to make a quick buck off your hard work.

I've donated an amount equivalent to what I would have been prepared to pay for a commercial service, but I'm shocked by how few other donations there are - certainly not enough to buy a new laptop, sadly. I'd implore anyone reading this thread; if you're going to benefit from an unlocker, then you too should recompense Buzz for his hard work via the Paypal options on his website.
[JASJAR, XDA Exec, MDA Pro Software Upgrading] dmjass:
I live in the Eastern Europe and paypal does not accept members from my part of teh world.... :-(
[Atrix 4G Q&A, Help & Troubleshooting] pixut:
Hello everybody,

I wondering is there any way I can use my atrix without the touch screen?

Background information: My atrix is on stock rom with unlocked bootloader. Touch screen is dead but other functions are still good.
[Atrix 4G Q&A, Help & Troubleshooting] ravilov:
If it's rooted and you have USB debugging enabled, you can use the built-in UNIX shell.

Android has various built-in commands to manipulate the system and UI, with a bit of effort you can even simulate screen touches if you want.
[Atrix 4G Q&A, Help & Troubleshooting] andresrivas:
Plug it ibto the hd dock, plug a mouse to it and a cursor will appear on screen.

Enviado desde mi MB860 usando Tapatalk 2
[Atrix 4G Q&A, Help & Troubleshooting] pixut:
Thanks, I managed to use the mouse in my dead-touch screen atrix.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] improvius:
I finally gave up on using chrome on the hdx 8.9. Scrolling on most web pages was just too choppy and laggy, both before and after various modifications. I finally switched over to Dolphin, which so far is much smoother and faster. Anyone else having similar issues with chrome? I prefer it's features, but Dolphin is much more usable right now.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] jeryll:
Try other

Try "opera beta" or "chrome beta" from Play store, much better than original chrome browser. I use opera beta for web browsing and chrome beta for better video support.
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] improvius:
I tried both Chrome and Chrome beta, same thing. Very poor scrolling, both vertical and horizontal. I'll just stick with Dolphin for now, I guess.
[Off-topic] LibertyMarine:
What are your thoughs about this recent movement ?

Ukraine mobilises after Putin's 'declaration of war'

Ukrainian and Russian troops in standoff at Crimean military base - live updates

You this conflic can be solved without violence ?

Who can stop Russia ? What are the options ?

Just making a place for us to discuss this topic ;)

Edit: If this is not allowed in OT, pls remind me... I didn't see any rules that say this is not allowed

Edit_2: Since political threads are not allowed on XDA ... I kindly ask you not to answer with a political stamement such as "I hope A destroyes B with a nuclear strike".... So just try to discuss without saying you want someone to win or whatever... take the question "What are the options to solve this conflict without violence ?" as an example... I think this isn't too policital
[Off-topic] Deadpool:
It has been started with America and Syria

Sent from my bloody katana.
[Off-topic] wojt51:
I hope it will end without war. If not, Poland would be in centre of world war 3rd time from 1914. I'm definitely not happy because Poland (my country) borders with Russia, Belarus and Ukraine.

Wysłane z mojego LG-E610
[Off-topic] hanisod:
As long as there's a reason for war

It'll never end

It all caused by fear, greed, and mis-guided people

You can't simply remove those from the human nature

And history doesn't repeat it self, humanity repeat it's stupidity

Take that as a lesson for tomorrow

And yes, political topics are not allowed on XDA
[Off-topic] Christian Nothing:
the most "funny" thing is that my country has the borders with both countries , so i may get screwed up if this war continues :rolleyes:

let's hope that the situation won't get any worst that it is now...
[Off-topic] LoopDoGG79:
Merely discussing this topic at all is considered political discussion. Sorry, there is no way around the rule in this thread.

Sent from my Nexus 7 2013 edition.
[Off-topic] Clark Joseph Kent:
Thread closed as per Forum Rules.

2.4 Personal attacks, racial, political and / or religious discussions: XDA is a discussion forum about certain mobile phones. Mobile phones are not racial, political, religious or personally offensive and therefore, none of these types of discussions are permitted on XDA.
[Sony Xperia S, Acro S, Ion] Olivier:
Hi,

since many people asked me how I build my ROMs for locked bootloaders, I have decided to write a short guide.

Getting started

As always, you need to set up a build environment. Since I don’t want to elaborate on this, I suggest you to follow the building instructions on the CyanogenMod wiki. You can also use the AOKP website as a reference.

Initializing the repos

To start, you may want to initialize the repos that you will use later on. Just open a terminal and issue the following command:

repo init -u git://github.com/aosp-lb-nozomi/manifest.git -b <ROM>

Where <ROM> is the ROM you want to build. You have to choice between aokp, pac, slimbean and mokee.

So, let's say you want to build AOKP - this would be the command you would have to issue:

repo init -u git://github.com/aosp-lb-nozomi/manifest.git -b aokp

Syncing the code

Now that this is done, you can start syncing (this may take some time):

repo sync -jX

Replace the X with your core count (eventually +1 or -1). (e.g. If you have a dualcore processor, it can be -j2 or -j3)

Building

Start with:

. build/envsetup.sh

Now you should be good to go. Lunchtime!

lunch <ROM>_<device>-userdebug

(e.g. lunch aokp_nozomi-userdebug OR lunch slim_aoba-userdebug)

Finally, you are ready to build.

make -jX bacon

Patching the ROM to work with LB

If everything went right, you should find an AOKP build in your out folder. But this build is unpatched, so it can be flashed on UB devices only. To patch it, go to your root directory (type "cd"), clone my repo and navigate to it:

git clone git@github.com:aosp-lb-nozomi/rom_builder.git -b [B]<ROM>[/B] patcher;cd patcher

Again, you have to replace <ROM> by the ROM you want to build. Possible ROMs: aokp, pac, slimbean and mk.

NOTE: If you build for the Sony Xperia Ion (aoba), you have to add that. (e.g. git clone git@github.com:aosp-lb-nozomi/rom_builder.git -b aokp-aoba patcher;cd patcher)

Finally, execute the script (to patch the ROM):

sh makezip

That’s it! Find your build in the folder “patcher” and flash it. :D
[AT&T HTC One (M7)] psicobelico:
Hi, does anyone know how to enable wifi tethering outside of USA?

Terhering was possible on Jelly Bean, but not on KitKat..

HTC One AT&T Stock Rom Rooted KitKat
[Micromax A116] MatrixGuy:
Working Nokia store...

Link -https://www.dropbox.com/s/tsbmt2dpcai8e4c/N.apk

Hit thanks if i helped you... :D:D
[Micromax A116] darshan dazzGeEk:
what's d use? will it b normal playstore or..
[Micromax A116] MatrixGuy:
Its nokia store ported from Nokia X(Android)...it is Different from play store :)
[Micromax A116] Rishabh-The Developer:
Not Working :(

Dude its not working in my Canvas HD.

I tried more than 10 times bt it doesn't run.

Every time it shows -"Installation Completed. Close to finish Installation.

Or when i close nothing will happen or i always do this same process again and again.
[Micromax A116] Yvan12:
Is it working please?
[Micromax A116] MatrixGuy:
It is working for me... :D
[Micromax A116] HatRiGt:
wrking awesome in Ma chd. 8......
[Micromax A116] MatrixGuy:
Press thanks if i helped you.. :D
[Micromax A116] pankajpadra:
Not working. When start it says update available. When we update and finish installation. Again update sceern comes.
[Micromax A116] iamthedroid:
Working fine..!!:good:

But when I tried downloading Nokia Here, no luck- unable to install:(
[Micromax A116] kevalthakkar:
not working..........:crying:
[Micromax A116] Indranilbanerjee010:
Its not working....asking for updates all the time...only if I open it and then connect the net...then only it works.... :-B
[Project Ara General] Poke_N_PDA:
So for years I've loved sliding keyboards. However, I've been driven away from them by the lack of decent phones. I long for the day of a high end qwerty slider again and it seems I may finally have my chance with Project Ara.

That being said, I'm wondering if I should try to get involved and be a part of the initial movement by partnering with others to make one. I'm also considering an attempt to travel out to the conference to find like minded people to make this vision a reality. I'm posting here to see if there are any others who might share this vision.

I don't have any experience in this specific field, but I am an electrical engineer and I am just about to complete my MBA with an entrepreneurial focus.
[Project Ara General] davidgro:
I just found this thread via a search engine, don't know who you are, and I have nothing to contribute except a mighty strong desire for you to succeed. Please, go forth on behalf of us forgotten keyboard lovers and bring back a little of the glory days!

I admit I am still skeptical of the ARA thing, but on the other hand it seems to be the only likely chance we have get a phone that is both good and has a physical slider keyboard.
[Project Ara General] Goodeman:
I'm having trouble understanding how you expect a qwerty slider on ARA. I currently use a Droid 4 and enjoy the extra screen space and ease of use it allows. Are you suggesting that the keyboard could be part of a module? Would it be the whole length of the phone? Would it cover or extend across multiple modules? Or would it be more of a case-like accessory that could be easily removed for convenience or customization? I would just like to know what you had in mind.
[Project Ara General] crutchcorn:
Idea on how to implament.

What about if it was a case for the back only, which has a module on the bottom of it. Kinda hard to explain so I'll just open up paint and show a ploopy rendition of it. I LOVE the idea and was thinking the same thing! Included picture explains a little better. I'd love to help and I am a electronic designer myself! I also do lots of Android code and such and would love to help implament this. PM me! :D
[Project Ara General] dsfdfsdfs:
That is an option, but I guess it would have to be an "unofficial" (i.e. not in Google's module store) module if it covers other modules. Alternatively you could have connector between the module and the keyboard case, but then you'd need to attach the case to the phone in a different way.

Another downside of doing it that way is that it covers the camera. If it can be made to not cover the camera when the keyboard is retracted, I guess that would be quite OK.

Another option is to put it on the display module:

############################
# display # The keyboard and the display
#--------------------------# would be on the same module.
# keyboard #
############################
# endo #
############################

############################
# display #
#################----------#################
# keyboard #
############################
# endo #
############################

To avoid the awkward edges on the left/right of the keyboard, the module could be made slightly thicker to drown them, if necessary (I don't think the edges would get into my way the way I hold my qwerty slider, but might be different for others - also, the keyboard module might already be thick enough to drown them enough without added articifial thickness).

Note that the MDK allows endos to have a single front module (type G, section 2.2.2 in the MDK PDF), so there may not be a second module "in the way" (but if there is, again I don't see it is a huge issue, could be mitigated with thickness if needed).

The downside of doing it this way is that it has to be integrated with a display, otherwise this seems better than other options I've seen imho.
[Project Ara General] crutchcorn:
Yeah no, I hear you. This was pre MDK and a lack of thought that lead me to suggest that. Another issue is that the MDK states that a module can only go above the endo if and only if it is on the top or bottom; no side expansion. I'm sure there's a way to design it so that it doesn't conflict with the camera but *shrug*. I like your ideas and you seem to know what to do
[Project Ara General] TheTrueScythe:
Ok so i was thinking. Since the concept I've seen to far has to do with the modules going on the back why not build it like and extension then build another module board on the back of the keyboard making it a bit bulkier but allowing for the keyboard.
[Project Ara General] riahc3:
The only possible way Ara is going to allow this is your standard "BlackBerry" type of keyboard. No Desire Z. No G1.

Personally I don't mind or care. As long as I get a keyboard on my Android, Im happy.
[Project Ara General] bones420la:
Why not a case with a built in desire z style keyboard? Hell it could be Bluetooth. And need no hard connection to the device
[Project Ara General] riahc3:
Bluetooth keyboards completely suck.
[Project Ara General] dsfdfsdfs:
Why wouldn't a slider module be allowed? I mean, I understand that that may be the case, but I wouldn't say it is certain yet.

Looking at the MDK v0.10 specification PDF:

3.1.4 - Envelope Violation Limitations - A slider in the front module could be interpreted as violating the envelope as the display will fall partially outside of the standard envelope in X direction (which is a violation as per Table 3.10) when extended. However, I'm not convinced this is intended to prevent modules that still fall within the valid dimensions in resting position (sure, it might be, but it is not 100% clear to me). Note that the maximum length in Z direction is 2.5 cm, so one should be able to fit a keyboard+slider+screen in this space.

3.1.2 - Front Module Sub-assemblies - Rear modules are limited to having a Base, PCB, Safety Shield, and a Shell (3.1.1.1). However, front modules only require a Base and a PCB, and other sub-assemblies are module-specific, so this would not affect a keyboard+slider+screen module AFAICS.

Am I missing something else? (I admit I haven't read the MDK document cover-to-cover)
[Project Ara General] riahc3:
Physically I don't see it possible using snap-on modules.
[Project Ara General] dsfdfsdfs:
OK, maybe I wasn't clear enough with my earlier post :)

Here's what I had in my mind in quickly-done image form:

Can you clarify what is impossible with doing it like that?
[Project Ara General] MGREX:
That makes sense however it's going to be a little bulky and Ara as-is now it's already pretty thick.

I do remember seeing a bb style display+keyboard module among the official concepts
[Project Ara General] i_takeitall:
Laser keyboard?
[Project Ara General] MGREX:
Nah the projector is also big and it will drain the battery incredibly fast
[Project Ara General] dsfdfsdfs:
Right. However, standard Ara module thickness is 4mm and the endo thickness looks like about 1mm, making thickness 9mm total. My Photon Q is 13.7mm, so there is quite a lot of margin to make the module thicker (if needed) without making the phone more bulky than current QWERTY sliders (and I have currently no problem with their thickness).

(the pictured module was 8mm in thickness)
[Project Ara General] zeroibis:
I pray that there is a sliding keyboard b/c I will not buy a phone without one (or removable storage, battery, unlocked bootloader mind you (hence still on D1))

I assume it would mount up under the display and then have the display mount in it as that would be the most accessible option as to prevent it from blocking access to modules.

One thing I can say right away is please if your going to make one have the keyboard work like the d1 for symbols! the d1 was able to make all symbols without needing the screen but the later models force you to use stupid screen selection for <> for example. All symbols should be possible via an alt key. there should never be a need to touch the screen EVER when using a physical keyboard no matter what symbol you want as long as said symbol exists on a normal full size keyboard.
[Project Ara General] riahc3:
Where would the rest of the modules go on your design?

BTW, Im not really sure about the rest of you caring about how bulky/thick the phone is. I could give a flying **** how thick it is as long as it has functionality (QWERTY keyboard)
[Project Ara General] crutchcorn:
That would make sense. But if it were on the back panel it wouldn't be allowed. They only allow a certain headroom for modules protruding from the base on the back panel, therefore you're right - we would have to use front panel (as stated by original idea) and it'd most likely work just fine.

Sent from my MetroPCS LG L70

---------- Post added at 12:34 AM ---------- Previous post was at 12:32 AM ----------

This is the screen module. This would connect with the base which could also have the modules on the back. It'd be the only way possible.

I don't care about thickness either

Sent from my MetroPCS LG L70

---------- Post added at 12:38 AM ---------- Previous post was at 12:34 AM ----------

Hey guys, I was thinking. Sense we're at it making a front display. I say that we could get together a group of guys who know how to make MDK modules and we create different screens (different front facing speakers/camera, just make it customizable!) and perhaps kickstart it or invest in it ourselves...

Sent from my MetroPCS LG L70
[Project Ara General] AndroidQWERTY:
The Return of the QWERTY-Slider!!!!

I couldn't agree with you enough--and my years-long rants about OEM's neglecting this very under-represented, though potentially immensely profitable, sector have rung hollow so far. I am an avid Android fan who will not part with a QWERTY slider at any cost. I've owned nearly every QWERTY-slider Android under the sun, and even with my newest acquisition, my first non-QWERTY phone, I find myself sacrificing and going back to my older devices because the satisfaction, efficiency, and speed with typing on physical keys simply cannot be duplicated on a virtual keyboard, regardless of what the masses say. SWYPE and all the software in the world cannot change this reality.

I like productivity-focused devices with premium, bleeding-edge specs. Back in the day, this was common. Now, whenever an OEM releases a QWERTY-slider (almost never), it's garbage with dated specs and poor build quality. I want an LG G-3 QWERTY-slider or an HTC M8 QWERTY-slider with no compromises on specs, whatsoever (I don't care about the added weight--that's not a spec, as far as I'm concerned). A fully-integrated, premium QWERTY-slider phablet, that is--NOT a blue-tooth case or some other removable attachment that has its own headaches.

I have searched high and low for a device like this, and, like many in this forum, was salivating when Project Ara was announced and I've been following it since the day it became a real possibility that we will soon be able to build the phones we want, the way we want them--assuming the third-party developers make the modules we want.

I also have a love for electronics, but no "real" hands-on engineering experience. I'm an attorney by profession, but I'm actually transitioning out of law practice and into the tech industry and would love to work on something like this. Would love to help out in any way I can, and I'm ecstatic that you started this thread!
[Project Ara General] ajbiz11:
What I could see is the keyboard having a slot with a network pass through for the display

This would (AFAIK) pass the MDK and allow for custom screens

Sent from my m7spr

---------- Post added at 10:15 PM ---------- Previous post was at 10:13 PM ----------

Also, has anyone noticed that Google spotlighted a flip out gamepad module design?

Sent from my m7spr
[Project Ara General] crutchcorn:
No way! They did? Do you have a link to that???
[Project Ara General] ajbiz11:
I don't, but it was in a video, iirc

They showed a split second of the picture of the concept in a large group ...don't remember where it was

Sent from my m7spr
[Project Ara General] crutchcorn:
If ya ever come across it again, could ya link it?
[Project Ara General] riahc3:
The problem with the slider is (besides physical limitations) that on the slider connectors would have to be on the bottom of the slider to connect to the phone and on top of the slider to connect to the display.

That's why there I see it difficult unless it is BlackBerry style.
[Project Ara General] ajbiz11:
In the sliding bracket, you could have extremely long pins that always line up with the display, no matter where it is in the sliding motion (on the mount for the display's back) and then still have the network pass through at some point on the top of the keyboard

Sent from my m7spr
[Project Ara General] peoriapoit:
I love the idea of being able to try different qwerty keyboards. Plus, if they make those hopefully you could attach a game pad as well.
[Project Ara General] ften:
http://aethertechnician.tumblr.com/post/83141448363/flippypad-for-project-ara-have-you-heard-about
[Project Ara General] crutchcorn:
Interesting. Thank you.
[Project Ara General] ajbiz11:
That was the original post of the concept

Breaks all of the MDK rules, but Google highlighted it at some point on a YT video

Sent from my m7spr
[Project Ara General] crutchcorn:
That's cause it's all about hacking and breaking the rules. :cool: